It is unfortunate that the IETF hasn't shown more leadership here.
Auto-learning address books are going to have a problem with From lines that
say:
First Last Name Via LISTNAME <listaddress@xxxxxxxxxxx>
since this will hijack "First Last" to point to the list, which is going to
cause all manner of email leaks. Maybe we can do better there.
--- Begin Message ---
- To: LEDE Development List <lede-dev@xxxxxxxxxxxxxxxxxxx>
- Subject: [LEDE-DEV] DMARC related mass bounces / disabled subscriptions
- From: Jo-Philipp Wich <jo@xxxxxxx>
- Date: Tue, 13 Dec 2016 21:50:32 +0100
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
Hi list, a recent mailing list post from a DMARC enabled domain caused a large flood of bounces from various mail providers, causing an automatic disabling of about 190 subscriptions [1]. I re-enabled those subscriptions manually so there is no need for further action on your side. In order to mitigate this problem in the future, I configured this list to wrap mails from DMARC enabled domains into an outer mail using the mailing list itself as sender [2]. Please excuse the inconvenience caused by this issue. Regards, Jo 1: http://thehackernews.com/2014/04/yahoos-new-dmarc-policy-destroys-every.html 2: https://wiki.list.org/DOC/Mailman%202.1%20List%20Administrators%20Manual#line-544Attachment: signature.asc
Description: OpenPGP digital signature_______________________________________________ Lede-dev mailing list Lede-dev@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/lede-dev
--- End Message ---
-- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | network architect [ ] mcr@xxxxxxxxxxxx http://www.sandelman.ca/ | ruby on rails [