bgware: SRS / what next after vmailmgr ?


Previous by date: 15 Jun 2020 18:41:02 -0000 SRS / what next after vmailmgr ?, Olivier Mueller
Next by date: 15 Jun 2020 18:41:02 -0000 multilog ignores 2nd filter when using the 't' flag, zoot
Previous in thread: 15 Jun 2020 18:41:02 -0000 SRS / what next after vmailmgr ?, Olivier Mueller
Next in thread:

Subject: Re: [bgware] SRS / what next after vmailmgr ?
From: Olivier Mueller ####@####.####
Date: 15 Jun 2020 18:41:02 -0000
Message-Id: <2a0e11ca-b308-e8ca-cea8-0dde76be445a@omx.ch>

Le 15.06.20 à 18:12, John R. Levine a écrit :
> Those servers are pretty badly broken.  Gmail's SPF record ends with 
> ~all, and all of their mail has DKIM signatures which forwards shouldn't 
> break.

Thanks for your reply John!  gmail.com was just a first example, there 
are many others, and telling my users that the other servers are broken 
will not really impress them, unfortunately, and they will leave to 
gmail, outlook.com, or others.

Another live example from the current mail queue:  twitter or facebook 
notifications with:
   Return-path: ####@####.####  or
   Return-path: ####@####.####

-> my server -> @gmail.com  (or other big mail providers) -> fail 
(usually with a "UnsolicitedRateLimitError" message), as both of them 
have a nice SPF "-all".


Best regards from Switzerland,
Olivier

Previous by date: 15 Jun 2020 18:41:02 -0000 SRS / what next after vmailmgr ?, Olivier Mueller
Next by date: 15 Jun 2020 18:41:02 -0000 multilog ignores 2nd filter when using the 't' flag, zoot
Previous in thread: 15 Jun 2020 18:41:02 -0000 SRS / what next after vmailmgr ?, Olivier Mueller
Next in thread:


Powered by ezmlm-browse 0.21.