On Mon, 4 Mar 2019, Zdenek Wagner wrote: > I am afraid that the subject prefix is just one of several reasons. I > have just examined the recent reply by Norbert Preining. Gmail > reports: > SPF: PASS, DKIM: FAIL, DMARC: FAIL.
If SPF passes, then DMARC ought to pass. DMARC is only supposed to require one of these, not necessarily both. The reason the message hasn't passed DMARC is that it has not really passed SPF here. The list is allowed by SPF to send things from tug.org, which is in the "envelope sender" of the message, but DMARC looks at the From: header, which under the current config is the original author. Although there are complexities involved, basically these checks will fail for many recipients if the list rewrites the Subject: header, or rewrites any other signed material (such as adding a footer to the message body), and doesn't rewrite the From: header to something for which it's authorized. Many lists don't want to rewrite the From: header because they want replies to go to the original author instead of the list... but that doesn't seem to be the case here because the list is setting Reply-To: to the list anyway. So that's not a reason to avoid rewriting From:. If it's desired to keep the original author's name prominent in the headers, it could either go into a custom field, or the text "real name" part of the rewritten From: header. -- Matthew Skala msk...@ansuz.sooke.bc.ca People before tribes. https://ansuz.sooke.bc.ca/
