
On 12/8/20 4:04 PM, Per Jessen wrote:
Michael Ströder wrote:
On 12/8/20 3:43 PM, Per Jessen wrote:
Peter Simons wrote:
AFAICT, mailman offers only two (marginally useful) options, per list - replace from with list address or wrap message in an outer message. Neither is of much use to us, we don't want the From: address to change.
you realize, though, that it's impossible to keep "From:" as-is if you want to deliver postings reliably to all recipients?
Well, for at least the last four years, it has not caused us any problems. (i.e. I haven't seen any tickets nor have I heard anyone complain).
That's not a real argument because MTA admins just began to implement SPF/DKIM/DMARC during the last two years.
Hmm, I'm not to sure about that estimate. Looking at e.g. our internal SPF whitelist, the earliest entries are eight years old.
Again: This issue is not caused by SPF alone. IIRC classic SPF checks only covered envelope sender. It's caused by DMARC which mandates checking the From: header. And DMARC adoption is increasingly used for being able to deliver to big players like GMail, Yahoo and Microsoft. As said: This is a moving target anyway and this issue will rather increase instead of going away. Ciao, Michael