I run my own smtp mail server with a plugin of opendmarc. I've noticed since the datacenter move (did not check before the move) that opendarc is labeling email from the redhat.com domain as failed in the journal.
I am unsure if this is a redhat infrastructure issue or my local opendmarc issue.
Well, we have no control over redhat.com emails... unless they are somehow coming via our servers ( mailing list posts? )
Can you share some of the errors you are seeing and we can try and isolate it?
Kevin, I get this error when my smtp server (Postfix) attempts to accept mail from any of the fedora mailing list. From my journal log: Aug 20 06:53:01 dubby.jlhimpel.net opendmarc[1801]: AF59FFA7F52: SPF(mailfrom): lists.fedoraproject.org pass Aug 20 06:52:15 dubby.jlhimpel.net opendmarc[1801]: 304A1FA7F51: jlhimpel.net none Aug 20 06:52:15 dubby.jlhimpel.net opendmarc[1801]: 304A1FA7F51: SPF(mailfrom): dubby.jlhimpel.net tempfail Aug 20 06:52:15 dubby.jlhimpel.net opendmarc[1801]: CDC9AFA7F4F: redhat.com faill Aug 20 06:52:15 dubby.jlhimpel.net opendmarc[1801]: CDC9AFA7F4F: SPF(mailfrom): lists.fedoraproject.org pass Aug 20 06:35:02 dubby.jlhimpel.net opendmarc[1801]: 22A70FA7F4D: triviaconnect.com fail Aug 20 06:35:02 dubby.jlhimpel.net opendmarc[1801]: 22A70FA7F4D: SPF(mailfrom): tec35.com pass Aug 20 06:25:00 dubby.jlhimpel.net opendmarc[1801]: ED4A5FA7F4A: mail.deepstatetribunal.com fail Aug 20 06:25:00 dubby.jlhimpel.net opendmarc[1801]: ED4A5FA7F4A: SPF(mailfrom): track.mail.deepstatetribunal.com tempfail Aug 20 06:19:56 dubby.jlhimpel.net opendmarc[1801]: F2483FA7F49: briskstonezn.us pass Aug 20 06:19:56 dubby.jlhimpel.net opendmarc[1801]: F2483FA7F49: SPF(mailfrom): briskstonezn.us pass
Metadata Update from @james: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: Needs investigation, low-gain, low-trouble
So, this is the same thing I found out in https://pagure.io/fedora-infrastructure/issue/12487#comment-983575
basically, internally, redhat.com doesn't show a dmarc record, so mailman doesn't do the mitigations for it.
we need to upgrade mailman to the latest version and then we can set it so it always mitigates redhat.com.
Lets track this over in #12487
Metadata Update from @kevin: - Issue close_status updated to: Duplicate - Issue status updated to: Closed (was: Open)