stan wrote: > On Tue, 27 Mar 2018 17:27:40 -0400 > Todd Zullinger <tmz@xxxxxxxxx> wrote: >> As we've discussed in this thread and others recently, >> messages from subscribers @yahoo.com do not reach >> subscribers @gmail.com (among others). This is due to an >> aggressive policy set by Yahoo which breaks mail sent via >> the mailing list. >> >> The mitigation enabled should change the From: address of >> the outgoing mail to the list address. This should only >> apply to users of @yahoo.com and other domains which set a >> similar DMARC policy. Subscribers at other domains should >> see no change to the From: address of mail they send to the >> list. >> >> I believe that only the email address will be changed, and >> not the sender's name, but I am not certain of that yet. >> >> Hopefully this mitigation will work well and provide an >> overall improvement to the list. If not, we'll revert it. > > Would this change be why I'm suddenly seeing oodles of old messages > showing up on the list? Messages that I've already seen, since I don't > have a problem with messages from yahoo addresses being invisible. This shouldn't be related to that. All it does is change the From: field of messages sent from domains with very strict DMARC policies, so that they use the list address. The sender name is kept, with 'via $list_name' appended. > I'm not sure what this will do to any messages I've saved > - will they be deleted when I delete these old messages > that are showing up as if they are new? No change we make to the list settings could affect your saved messages. (I'm presuming that you're referring to messages saved in your email client.) -- Todd ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dope will get you through times of no money better than money will get you through times of no dope. -- Freewheelin' Franklin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx