Elastic mail account SMTP configuration for git send-email

Elastic mail account SMTP configuration for git send-email

[Roberto A. Foglietta]

Hi all,

 due to the problems related to bypassing my gmail multifactors
account authentication, I decided to use a 3rd party SMTP service like
elastic mail. Here is the configuration. Note: the first e-mail that I
sent with this service has been tagged as SPAM immediately after gmail
reception. Possibly, also the one sent to the m-list with the in-line
patch could have been dealt with as it were spam. Moreover at the end
of the mail has been added an URL.

 == CONFIGURATION HOW TO ==

Elastic mail account SMTP configuration

1. elastic mail - free API account - login with gmail

2. settings - SMTP - Create SMTP credentials

3. use your gmail e-mail address as username

4. copy the password and save in a secure place

5. server name is smtp.elasticemail.com:2525

6. configure and/or use the git send-email

# ~/.config/git/config
[sendemail]
  confirm = auto
  smtpServer = smtp.elasticemail.com
  smtpServerPort = 2525
  smtpEncryption = tls
  smtpUser = <gmail email address>

OR

gmaddr="roberto.foglietta@gmail.com"
isarml="isar-users@googlegroups.com"
git send-email --from $gmaddr --to $isarml --cc $gmaddr --subject
"${mysubject}" --smtp-server smtp.elasticemail.com:2525 --smtp-pass
"${mypasswd}" --smtp-user $gmaddr --smtp-encryption tls
${git-format.patch}

 Best regards, R-

Re: Elastic mail account SMTP configuration for git send-email

[Roberto A. Foglietta]

On Thu, 3 Nov 2022 at 17:11, Roberto A. Foglietta
<roberto.foglietta@gmail.com> wrote:
>
> Hi all,
>
>  due to the problems related to bypassing my gmail multifactors
> account authentication, I decided to use a 3rd party SMTP service like
> elastic mail. Here is the configuration. Note: the first e-mail that I
> sent with this service has been tagged as SPAM immediately after gmail
> reception. Possibly, also the one sent to the m-list with the in-line
> patch could have been dealt with as it were spam. Moreover at the end
> of the mail has been added an URL.

Hi all,

 I have verified in the web interface of google groups

https://groups.google.com/g/isar-users

 and the e-mail sent through the elastic SMTP has not been delivered
to the group.

 Probably to allow this approach to work the group admin have to
authorise this kind of sending by from-by or by mail-to

from:roberto.foglietta@gmail.com via bounces.elasticemail.net
reply-to:roberto.foglietta@gmail.com
to:isar-users@googlegroups.com
cc:roberto.foglietta@gmail.com
date:3 Nov 2022, 16:55
subject:[PATCH] linux install.tmpl: added CONFIG_HAVE_OBJTOOL in OR for objtool
mailed-by:bounces.elasticemail.net

 IMHO, I wish to have this kind of service managed by github. With the
same authentication we do 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 to write a brief technical document that
describes the problem and proposing a solution like an RFC. Then, we
can submit it to the Microsoft people that deal with github.

Best regards, R-

Re: Elastic mail account SMTP configuration for git send-email

[Roberto A. Foglietta]

On Thu, 3 Nov 2022 at 17:50, Roberto A. Foglietta
<roberto.foglietta@gmail.com> wrote:
>
> On Thu, 3 Nov 2022 at 17:11, Roberto A. Foglietta
> <roberto.foglietta@gmail.com> wrote:
> >
> > Hi all,
> >
> >  due to the problems related to bypassing my gmail multifactors
> > account authentication, I decided to use a 3rd party SMTP service like
> > elastic mail. Here is the configuration. Note: the first e-mail that I
> > sent with this service has been tagged as SPAM immediately after gmail
> > reception. Possibly, also the one sent to the m-list with the in-line
> > patch could have been dealt with as it were spam. Moreover at the end
> > of the mail has been added an URL.
>
> Hi all,
>
>  I have verified in the web interface of google groups
>
> https://groups.google.com/g/isar-users
>
>  and the e-mail sent through the elastic SMTP has not been delivered
> to the group.
>
>  Probably to allow this approach to work the group admin have to
> authorise this kind of sending by from-by or by mail-to
>
> from:roberto.foglietta@gmail.com via bounces.elasticemail.net
> reply-to:roberto.foglietta@gmail.com
> to:isar-users@googlegroups.com
> cc:roberto.foglietta@gmail.com
> date:3 Nov 2022, 16:55
> subject:[PATCH] linux install.tmpl: added CONFIG_HAVE_OBJTOOL in OR for objtool
> mailed-by:bounces.elasticemail.net

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?

Best regards, R-

Re: Elastic mail account SMTP configuration for git send-email

[Baurzhan Ismagulov]

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,
Baurzhan

Re: Elastic mail account SMTP configuration for git send-email

[Roberto A. Foglietta]

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-