From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: Baurzhan Ismagulov <ibr@radix50.net>
Cc: isar-users@googlegroups.com
Subject: Re: Elastic mail account SMTP configuration for git send-email
Date: Wed, 9 Nov 2022 07:10:15 +0100 [thread overview]
Message-ID: <CAJGKYO4mzH7JKOGjX9657LGG95hia3RezSE39ky-E2cw87FawQ@mail.gmail.com> (raw)
In-Reply-To: <Y2ptYKRh2FRXgQkf@ilbers.de>
On Tue, 8 Nov 2022 at 15:53, Baurzhan Ismagulov <ibr@radix50.net> wrote:
>
> On Sat, Nov 05, 2022 at 10:29:04AM +0100, Roberto A. Foglietta wrote:
> > Today the e-mail arrived probably because ISAR google group admin authorised it
> >
> > https://groups.google.com/g/isar-users/c/BQJuOzwqMb0
> >
> > Could you give me some more information about this?
> > Using elastic SMTP could be an acceptable solution?
>
> Yes, I approved the message.
>
> The policy is to allow posting by non-members to keep the communication barrier
> low. To prevent spam, we quarantine new submissions from non-member email
> addresses.
>
> If sending unmangled patches to the list works with elastic, I'm not aware of
> any disadvantages.
>
> Hope this helps -- I'm not sure whether this is the info you requested.
>
> With kind regards,
Hi Baurzhan,
I am not convinced that using a marketing tool would be the right
general approach, in fact you need to authorize my e-mail even if I am
subscribed here. This is because a marketing tool SHOULD not
impersonate the real sender and they also would not want that because
otherwise the real sender might be blacklisted. The second reason is
the link added at the end of the mail which becomes available to
everybody when the m-list has a public record. I did not try but I
have the sensation that could affect my ability to send future e-mail
to the m-list address and everyone can trigger it.
== MY SUGGESTION IS ==
IMHO, I wish to have this kind of service managed by github. With the
same authentication we do "git push" we could send e-mail from github.
The github account is associated with an e-mail address and it would
be a duty of github to connect the proper domain SMTP to send the mail
or at least from-by (via) github could be accepted as a trustworthy
way to receive emails. What about writing a brief technical document
that
describes the problem and proposes a solution like an RFC. Then, we
can submit it to the Microsoft people that deal with github.
What do you think about it? Wouldn't it be great to use
smtp.github.com for git send-email?
Best regards, R-
prev parent reply other threads:[~2022-11-09 6:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 16:11 Roberto A. Foglietta
2022-11-03 16:50 ` Roberto A. Foglietta
2022-11-05 9:29 ` Roberto A. Foglietta
2022-11-08 14:53 ` Baurzhan Ismagulov
2022-11-09 6:10 ` Roberto A. Foglietta [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJGKYO4mzH7JKOGjX9657LGG95hia3RezSE39ky-E2cw87FawQ@mail.gmail.com \
--to=roberto.foglietta@gmail.com \
--cc=ibr@radix50.net \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox