Re: [PATCH] dpkg class sbuild allows extra arguments by vars

["Roberto A. Foglietta" <roberto.foglietta@gmail.com>]

On Thu, 5 Jan 2023 at 19:31, Henning Schild <henning.schild@siemens.com> wrote:
>
> Am Thu, 5 Jan 2023 18:43:40 +0100
> schrieb "Roberto A. Foglietta" <roberto.foglietta@gmail.com>:
>
> > On Wed, 4 Jan 2023 at 08:54, Henning Schild
> > <henning.schild@siemens.com> wrote:
> > >
> > > Am Tue, 3 Jan 2023 22:39:55 +0100
> > > schrieb "Roberto A. Foglietta" <roberto.foglietta@gmail.com>:
> > >
> > > > On Tue, 3 Jan 2023 at 21:26, Henning Schild
> > > > <henning.schild@siemens.com> wrote:
> > > > >
> > > > > Again can you please send you patches in a way that they can
> > > > > actually be reviewed in a mail based workflow.
> > > >
> > > > I send the patches with git-send but they went in moderation and
> > > > usually remain there.
> > > > Tomorrow, I will search for another open SMTP server hoping that
> > > > the m-list will accept it but I am desperate to find one that
> > > > suits the stringent anti-spam rules of google.
> > >
> > > Maybe we start with your problem here and help you use the SMTP
> > > servers from google. My guess is that you might be struggling with
> > > 2FA. And doing an internet search on how to use plain SMTP on gmail
> > > might also give you the solution.
> > >
> >
> > It is not possible to authenticate on SMTP with 2FA. In the past there
> > was the option to create an app credential to send e-mail but this
> > option has been removed. So, all the how-to like this would simply not
> > work anymore
> >
> > https://blog.revathskumar.com/2019/08/git-send-patch-using-send-email-and-gmail.html
> >
> > > Using any other SMTP server you will likely get problems with SPF,
> > > DKIM, DMARC forcing you to send emails "From" the domain of that
> > > other server. In which case git-send-email would put a secondary
> > > "From" into the commit message so that git-am on the other side
> > > will get the real author email.
> >
> > In fact, Google Groups intercept such a e-mail and tag it as SPAM both
> > in the web application (on the reader side) and in the m-list incoming
> > rules.
> >
> > >
> > > But best try to use googles SMTP servers, that is for sure possible
> > > and not too hard once you found the solution.
> > >
> >
> > Finally, I used a regular SMTP from an internet provider. However, It
> > costs me a domain name fee.
>
> you could try msmtp and google again, if application credentials do not
> work anymore ... you need to dance the oauth2 dance ...
>
> Or you stay with a provider that does not enforce so much security on
> you that in the end you can not send mail from the campfire in the cave
> ;)
>

The problem has been solved as you can see here:

Message ID<20230104185604.2542129-1-roberto.foglietta@gmail.com>
Created on:4 January 2023 at 19:56 (Delivered after 5 seconds)
From:roberto.foglietta@gmail.com Using git-send-email 2.34.1
To:isar-users@googlegroups.com
Subject:[PATCH] rootfs class lock undefined in corner cases fix
DKIM:'PASS' with domain googlegroups.com Learn more

It was a very simple problem to solve but it required a smart internet
provider that gives domain names for a reasonable price and allows
users to do magic with the SMTP mangling rules.

The key information is "what is the name of that internet provider?"

If you take a look at that e-mail, can you discover it? LOL

Best regards, R-