public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: isar-users@googlegroups.com
Subject: Re: Elastic mail account SMTP configuration for git send-email
Date: Thu, 3 Nov 2022 17:50:48 +0100	[thread overview]
Message-ID: <CAJGKYO6Ea51qdrY82U_Ap5Ao0=Ti7C+1SfAHt6v8Njhx6YPLPg@mail.gmail.com> (raw)
In-Reply-To: <CAJGKYO5ki+DX0QZcw75irsEYvxgeJib+1L6wO_b+Ac51X3kmjw@mail.gmail.com>

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-

  reply	other threads:[~2022-11-03 16:51 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 [this message]
2022-11-05  9:29   ` Roberto A. Foglietta
2022-11-08 14:53     ` Baurzhan Ismagulov
2022-11-09  6:10       ` Roberto A. Foglietta

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='CAJGKYO6Ea51qdrY82U_Ap5Ao0=Ti7C+1SfAHt6v8Njhx6YPLPg@mail.gmail.com' \
    --to=roberto.foglietta@gmail.com \
    --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