ietf-tools / postconfirm

BSD 3-Clause "New" or "Revised" License
3 stars 9 forks source link

"email authors" violates DMARC #34

Closed jschauma closed 1 year ago

jschauma commented 1 year ago

Describe the issue

If you utilize the "Email Authors" address on an ID to contact the authers, it looks like at some point your email is re-sent from a different mail server, leading to SPF / DKIM failures on the receiving end.

For example:

<schneier@schneier.com> (expanded from
    <expand-draft-farrell-tenyearsafter@virtual.ietf.org>): host
    mx1.emailsrvr.com[184.106.54.1] said: 550 5.7.1 Email rejected per DMARC
    policy for netmeister.org (G15) (in reply to end of DATA command)

<farzaneh.badii@gmail.com> (expanded from
    <expand-draft-farrell-tenyearsafter@virtual.ietf.org>): host
    gmail-smtp-in.l.google.com[142.251.2.26] said: 550-5.7.26 The MAIL FROM
    domain [netmeister.org] has an SPF record with a hard 550-5.7.26 fail
    policy (-all) but it fails to pass SPF checks with the ip: 550-5.7.26
    [50.223.129.194]. To best protect our users from spam and phishing,
    550-5.7.26 the message has been blocked. Please visit 550-5.7.26
    https://support.google.com/mail/answer/81126#authentication for more 550
    5.7.26 information. 21-20020a170902c21500b001a8d80c7bb1si4630857pll.128 -
    gsmtp (in reply to end of DATA command)

My domain has a strict DMARC reject policy, which is why gmail and others will reject mail that purports to originate from my domain but comes from unauthorized IPs (50.223.129.194 / mail.ietf.org, in this case).

Code of Conduct

richsalz commented 1 year ago

This is a known issue, the mail aliases do not go through the DMARC hacks that the mailing lists do. The plan is to fix this when the IETF moves to mailman3. (I thought there already as an issue for this, but I couldn't find one.)

rjsparks commented 1 year ago

You should be looking at https://github.com/ietf-tools/postconfirm/issues. I'll move this issue there, and mark it as a duplicate of #33 in that project.