Hi, Michael
So what do you suggest we do?
I think something like the following will not have the same problem:
IETF discussion list on behalf of Michael Richardson
<ietf(_at_)ietf(_dot_)org <mailto:ietf(_at_)ietf(_dot_)org>>
But that just saves us from data leakage. It doesn’t get the right value into
the address book.
Yoav
On 14 Dec 2016, at 16:25, Michael Richardson <mcr(_at_)sandelman(_dot_)ca>
wrote:
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(_at_)example(_dot_)com>
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.
From: Jo-Philipp Wich <jo(_at_)mein(_dot_)io>
Subject: [LEDE-DEV] DMARC related mass bounces / disabled subscriptions
Date: 13 December 2016 at 22:50:32 GMT+2
To: LEDE Development List <lede-dev(_at_)lists(_dot_)infradead(_dot_)org>
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-544
_______________________________________________
Lede-dev mailing list
Lede-dev(_at_)lists(_dot_)infradead(_dot_)org
http://lists.infradead.org/mailman/listinfo/lede-dev
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr(_at_)sandelman(_dot_)ca http://www.sandelman.ca/ | ruby
on rails [