#10332 EPEL-devel list doesn't handle sender domains with DMARC policy set (while devel list does)
Closed: Fixed with Explanation 2 years ago by kevin. Opened 2 years ago by salimma.

Describe what you would like us to do:


Please make the DMARC handling policy that applies to the devel@ list also apply to other Fedora mailing lists, including epel-devel

e.g. for this email
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/TGPN4J334S4JNXX5I7A3IOXFMCBSD35V/

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/6DXACTD4WNGYSVRQATHOMAYIXIMB7WKY/

the EPEL one is delivered with this header:

From: Michel Alexandre Salim michel@michel-slm.name

which breaks the DMARC policy I set for my domain, so spam filters would flag it

X-Proofpoint-Dmarc-Result: quarantine
X-Proofpoint-Dmarc-Record: v=DMARC1;p=quarantine;rua=mailto:postmaster@michel-slm.name;ruf=mailto:admin@michel-slm.name

The devel list copy is fine:

From: Michel Alexandre Salim via devel devel@lists.fedoraproject.org

When do you need this to be done by? (YYYY/MM/DD)


2021/12/31


Same as https://pagure.io/fedora-infrastructure/issue/9434 but worryingly, our mailing lists are not behaving consistently, so we should probably at least do the same thing across them.

I'm switching back my DMARC setting to p=none so I can audit the errors for now, since even if fp.o lists are all fixed, looks like CentOS lists also do not do this properly

This was actually discussed a while back and we decided to leave it up to each list how they wanted to deal with it. I suppose we could revisit.

Metadata Update from @mohanboddu:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-gain, low-trouble, ops

2 years ago

I've changed the epel-devel list to use the same DMARC mitigation as devel list.

We could look at changing the default, but I think it's best to just let each list handle it.

Let us know if there's other lists you hit this with.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog