Re: Fw: Undelivered Mail Returned to Sender

[John W. Eaton]

On 7/10/20 1:04 PM, Przemek Klosowski via Octave-maintainers wrote:
> On 7/10/20 11:34 AM, chloros wrote:
> > Hi Markus,
> >
> > the same thing happened to me on wednesday when I replied to one of the
> > jsondecode emails. I got the same error:
> >
> > DreamHost Email Support
> > <octave-maintainers@gnu.org> (expanded from <maintainers@octave.org>):
> > host eggs.gnu.org[209.51.188.92] said: 550-[SPF] 64.90.62.163 is not
> > allowed to send mail from gmx.de.
> >
> > Yet another gmx feature ...
>
>
> So typically what happens is that either an email listserver or 
> someone's forwarding results in an email that claims to be from you but 
> actually coming from gmx. The email headers specify SPF checks, and the 
> gnu.org MTA obediently verifies them and balks. That's why modern 
> listservers say things like From: listserver.us on behalf of 
> jane@doe.com--the SPF is correct wrt. the actual sender, and yet you can 
> still see who actually originated the email.

Dreamhost, which is handling the @octave.org mail, is just forwarding 
the message to an @gnu.org address that is processed by the mailman 
mailing list software.

Is there something that can be changed in mailman to allow the messages 
to go through, or are the messages rejected before mailman even sees 
them?  I recall a problem with gmail subscribers in the past and that we 
made some change to the mailman config so that messages to them would 
not bounce.

If messages can't be forwarded to list servers without special treatment 
on the system that does the forwarding, then maybe we should phase out 
the forwarding addresses.

jwe