"munge" is what we use for our own mailing lists when we send outbound so we ensure it passes DMARC. Mailing lists are very popular in higher education. Inbound - I use a series of reg-ex to try to exclude other universities legitimate mailing lists based on email address patterns. It's not 100% effective, but then I can do mainly over-rides if needed with our gateway for ones that fall outside these patterns.
Jason Carter IT Manager Collaboration Services Infrastructure and Security Information Technology Services | Florida State University p 850.645.8069 | w its.fsu.edu<https://its.fsu.edu/> ________________________________ From: mailop <mailop-boun...@mailop.org> on behalf of Gene Hightower via mailop <mailop@mailop.org> Sent: Monday, July 12, 2021 9:13 PM To: Mark Fletcher <ma...@corp.groups.io>; Lena from Kiev <l...@lena.kiev.ua> Cc: mailop@mailop.org <mailop@mailop.org> Subject: Re: [mailop] mail.ru broke mailing lists On 12/07/2021 14:07, Mark Fletcher via mailop wrote: > For others here running mailing lists that pay attention to DMARC > settings, do you treat p=none differently than reject/quarantine? I'm involved with a privacy-focused relay service. We "munge" (rewrite the RFC5322.From to use our own domain) when the DMARC policy is reject or quarantine, and for some specific mailbox providers.
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
