On 7/7/14 6:23 AM, Notes Jonny wrote:
> Have you thought about adding [svn users] to prefix the subject of emails?
>
> It would make my mailbox simpler to prioritise all emails.. Currently
> I need to read the subjects.. or implement some complex filtering to
> folder of svn users emails..
Modifying mail going to mailing lists is a very bad idea these days. It's
becoming increasingly common for mail providers to sign mail and then publish
DNS records that tell receivers that they can reject mail that is not properly
signed. Modifying the mail then means these signatures no longer validate and
the mail may be rejected.
Yahoo changed their DMARC settings in April of this year to tell receivers that
they should start rejecting mail that was not signed. This caused many mailing
lists that are doing exactly what you suggest to start dropping mail coming
from Yahoo users.
The solutions for this as outlined here are not great:
http://www.dmarc.org/faq.html#s_3
http://wiki.asrg.sp.am/wiki/Mitigating_DMARC_damage_to_third_party_mail
It basically comes down to:
1) Don't modify mail.
2) Start modifying the mail in more intrusive ways.
At the Apache Software Foundation for lists that don't follow the first option
they've adopted the .invalid option:
http://wiki.asrg.sp.am/wiki/Mitigating_DMARC_damage_to_third_party_mail#Add_fixed_string_such_as_.invalid_to_addresses
Which means for domains where DMARC configuration would break the mail the
sender mail is changed to have a .invalid postfix on the sender's address. For
example in the case of Yahoo user_at_yahoo.com.invalid
This would be particularly problematic for our users@ list because often we
have posters who are not subscribed to the list and would like to receive the
responses back. Responders would have to pay attention to the addresses and
fix them manually in all these cases.
I don't think munging the email subject is worth dealing with that.
Received on 2014-07-09 22:10:58 CEST