Email sent from yahoo to amo-admins@mozilla.org always ends up as spam

RESOLVED FIXED

Status

Infrastructure & Operations
Infrastructure: Mail
RESOLVED FIXED
a year ago
7 months ago

People

(Reporter: Fallen, Unassigned)

Tracking

Details

Attachments

(1 attachment)

(Reporter)

Description

a year ago
Created attachment 8766411 [details]
Headers of failing email

It turns out mail sent to amo-admins@mozilla.org is forwarded to mailman, which then sends back email to the list recipients. Yahoo mail always ends up as spam because dmarc/dkim is used and the headers don't check out when sending back to gmail.

Is there some way this can be fixed? I've attached the headers, sender is scrubbed.

Comment 1

a year ago
Well there is an option on the mailing list, its under privacy options > sender filters > dmarc_moderation_option. You would want to set this to "Munge from"[1], note that doing this does cause the email to be non rfc compliant[2] although only for domains that have a dmarc policy.

This is a setting that can be enabled by the list administrator, so I'm adding them to this bug to decide if thats the route that they want to go.


[1]: https://wiki.list.org/DEV/DMARC
[2]: https://wiki.list.org/DOC/What%20can%20I%20do%20about%20members%20being%20unsubscribed%20by%20bounces%20of%20Yahoo%20user's%20posts%20for%20DMARC%20policy%20reasons%3F
(Reporter)

Comment 2

a year ago
(In reply to Ed Lim [:limed] from comment #1)
> Well there is an option on the mailing list, its under privacy options >
> sender filters > dmarc_moderation_option. You would want to set this to
> "Munge from"[1], note that doing this does cause the email to be non rfc
> compliant[2] although only for domains that have a dmarc policy.
Wouldn't a non-compliant email be something similarly caught by Google's spam filters on the way back to the list recipient's accounts?
I'm open to giving that a try, but I'd like to understand the implications of changing that setting.

Comment 4

7 months ago
I've set this to munge from already, so should be good here
Status: NEW → RESOLVED
Last Resolved: 7 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.