[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fw: Undelivered Mail Returned to Sender

From: John W. Eaton
Subject: Re: Fw: Undelivered Mail Returned to Sender
Date: Wed, 15 Jul 2020 06:12:23 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0

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[] said: 550-[SPF] 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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]