On 4/26/20 7:07 AM, Peter wrote: > On 26/04/20 10:47 pm, Benny Pedersen wrote: >> talk to postmas...@almogavers.net ask for aspf not being set to >> strict, also possible make fo tag on dmarc more relaxed > > Except that this is a thread about what messages coming from the > *list* go to spam and what the *list* can do about it. It is not > reasonable for the mailing list owner to ask every person who's > messages go to spam because of a bad DMARC policy to change the policy.
Except that if the sender is sending from a domain with an email policy that effectively says, "This domain is intended to send sensitive information, please do not accept messages that do not come directly from us", then it is reasonable to tell the sender that they are sending messages outside their domains (implied) terms of service, and either they need to use a different service that is compatible with a mailing list, or have the domain fix its implied declaration of usage. This is exactly what DMARC is intended to indicate. Configuring a domain with DMARC says that it is intended that message only be accepted if they come directly from the sender. It was designed for things like Banks to be able to send out messages that the recipients can trust came from them and not a scammer. (A scammer could fake this out with a 'look-alike' domain, but that leaves a strong back trail to the scammer, who tend to want to hid in the darkness of the web. -- Richard Damon
