Hi all, for ~every message posted to this list, some email clients display an error, in my case "This email has failed its domain's authentication requirements. It may be spoofed or improperly forwarded." These are the authentication results for a recent message from the list: Authentication-Results: mailin008.protonmail.ch; arc=none smtp.remote-ip=8.43.85.227 Authentication-Results: mailin008.protonmail.ch; dkim=none Authentication-Results: mailin008.protonmail.ch; spf=none smtp.mailfrom=lists.podman.io Authentication-Results: mailin008.protonmail.ch; dmarc=fail (p=none dis=none) header.from=redhat.com If I understand correctly, Mailman has an option[1] to change the From: header in the email and add the original sender's name and address to the Reply-To: header, which leads to a slightly worse user experience, but is better for security because it reduces the number of false positives we get exposed to. So my question is, could we enable DMARC mitigation to reduce warning fatigue? Regards, Joost Molenaar [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers... _______________________________________________ Podman mailing list -- podman(a)lists.podman.io To unsubscribe send an email to podman-leave(a)lists.podman.io

Hi Tom, As per your previous message, this is a reminder that this issue is still happening. Have you (or anyone with access to the mail server) got a chance to investigate it? I'm facing a situation similar to the one described by Joost. In my case, most of the emails sent to this mailing list end up in my client's junk folder due to this problem. Regards, François On 8/17/22 00:18, Tom Sweeney wrote: > Joost, > > Thanks a bunch for the heads up.  I know just enough about the mail > server to be dangeruous, but I'll see if I can figure that out and > correct it.  Please ping me in a couple of weeks if you don't hear back, > it's slipped off my stack. > > t > > On 8/16/22 03:39, Joost Molenaar wrote: >> Hi all, for ~every message posted to this list, some email clients >> display an error, in my case "This email has failed its domain's >> authentication requirements. It may be spoofed or improperly >> forwarded." >> >> These are the authentication results for a recent message from the >> list: >> >>      Authentication-Results: mailin008.protonmail.ch; arc=none >> smtp.remote-ip=8.43.85.227 >>      Authentication-Results: mailin008.protonmail.ch; dkim=none >>      Authentication-Results: mailin008.protonmail.ch; spf=none >> smtp.mailfrom=lists.podman.io >>      Authentication-Results: mailin008.protonmail.ch; dmarc=fail >> (p=none dis=none) header.from=redhat.com >> >> If I understand correctly, Mailman has an option[1] to change the >> From: header in the email and add the original sender's name and >> address to the Reply-To: header, which leads to a slightly worse user >> experience, but is better for security because it reduces the number >> of false positives we get exposed to. >> >> So my question is, could we enable DMARC mitigation to reduce >> warning fatigue? >> >> Regards, >> Joost Molenaar >> >> [1]: >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers... >> _______________________________________________ >> Podman mailing list -- podman(a)lists.podman.io >> To unsubscribe send an email to podman-leave(a)lists.podman.io > _______________________________________________ > Podman mailing list -- podman(a)lists.podman.io > To unsubscribe send an email to podman-leave(a)lists.podman.io _______________________________________________ Podman mailing list -- podman(a)lists.podman.io To unsubscribe send an email to podman-leave(a)lists.podman.io