Filing this per this request by Kevin. https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/GITUMNYZJLC4DBF6PHONT6IIV7TCIOV2/
This email goes to spam for me on gmail: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/SDADAKNHDZP56GE773OZZETFJNWQRO52/
Attaching the eml file that is downloaded when I: - click the email in spam - choose "Show Original" - click on the Download Original button
file:///home/chris/Downloads/Stale%20packages%20in%20Fedora%2030.eml
OK let's try attaching it as a txt file...
<img alt="Stale_packages_in_Fedora_30.txt" src="/fedora-infrastructure/issue/raw/files/cecede144e82e6ac944b00ac5a1863b3440a90a2efd95cc171ff8b5dc89cb886-Stale_packages_in_Fedora_30.txt" />
There does seem to be something going on with gmail as I don't even get his emails showing up in my SPAM folder. As far as I can tell they are just being rejected outright somewhere in the system.
The failure they are listing looks to be something mentioning nist.gov which I am guessing is: X-OriginatorOrg: nist.gov
that outlook is putting in there.
Metadata Update from @smooge: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: lists
Metadata Update from @smooge: - Issue marked as depending on: #8455
Metadata Update from @smooge: - Issue assigned to smooge
Metadata Update from @smooge: - Assignee reset
I've got another example for kernel@ list.
<img alt="Have_the_5.6_kernels_dropped_support_for_user_input_of_entropy_to_the_kernel_.txt" src="/fedora-infrastructure/issue/raw/files/eb9d7ddf8d26a3da46e0b189f8b37c5a618ec7c78f559009a9e61e7cb1a6612e-Have_the_5.6_kernels_dropped_support_for_user_input_of_entropy_to_the_kernel_.txt" />
@smooge made some changes recently (like yesterday) to dmarc. Does this address this issue?
I'm not seeing any Fedora emails moved to spam in the last day. I'll try to remember to keep an eye on it.
So far so good, I'm not seeing any Fedora emails in gmail spam.
Great. Lets close this then and if you see it again, please open a new issue...
Metadata Update from @kevin: - Issue unmarked as depending on: #8455
Metadata Update from @chrismurphy: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.