Or, I don't know, recipients that are enforcing DMARC could simply follow the steps from the previous section. The mailing list doesn't own the messages sent to it (we don't see "From: clamav-users").
Recipients should whitelist the mailing list per: https://dmarc.org/wiki/FAQ#Is_there_special_handling_required_to_receive_DMARC_email_from_mailing_lists.3F On Wed, Oct 31, 2018 at 8:16 AM Alessandro Vesely <ves...@tana.it> wrote: > On Wed 31/Oct/2018 10:47:34 +0100 Al Varnell wrote: > > > I'm not sure it's even possible to be compliant given the currently used > > list software. > > Yes, it is: > > https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/dmarc-mitigations.html > > The most commonly used workaround is bullet #3 of that FAQ; > 3. Take ownership of the email message by changing the RFC5322.From address > > > On Wed, Oct 31, 2018 at 02:27 AM, Giuseppe Ravasio wrote: > >> > >> For the mailing list admins here there is a FAQ link about ML and DMARC > >> https://dmarc.org/wiki/FAQ#senders > > > There are elaborate variants. For example, one can register a domain like > dmarc.fail and rewrite From: in such a way that reply-to-author will work > for a > limited period of time. See: > http://lists.dmarc.org/pipermail/dmarc-discuss/2018-October/004193.html > > > Best > Ale > -- > > > > > > > > > > _______________________________________________ > clamav-users mailing list > clamav-users@lists.clamav.net > http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users > > > Help us build a comprehensive ClamAV guide: > https://github.com/vrtadmin/clamav-faq > > http://www.clamav.net/contact.html#ml >
_______________________________________________ clamav-users mailing list clamav-users@lists.clamav.net http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
