Never mind - I found it:
The solution L-Soft has developed for LISTSERV does not require anyone to make compromises or lose any functionality - not even the Yahoo and AOL subscribers. "Once you install the update, everything works just like it did before the DMARC debacle; incoming Yahoo and AOL addresses are automatically rewritten to local addresses that can receive private replies and forward them to the original poster," Thomas said. http://www.lsoft.com/news/2014/listserv160-2014a-us.asp Scott Bonacker CPA - McCullough and Associates LLC - Springfield, MO -----Original Message----- From: Scott Bonacker [mailto:[email protected]] Sent: Wednesday, April 06, 2016 3:32 PM To: [email protected] Subject: dmarc-request Occasionally a message will come through lsoft list management showing that the sender was something like this: "on behalf of 000004d5988cbc6e-dmarc-request [at] HOME.EASE.LSOFT.COM" List members can receive messages sent back to an addy like that, and when they reply outside of LSOFT things are fine. Did find this in another study group from about a year ago: > Now that my list is upgraded to version 16, and > we've licked the dmarc issue, some of my AOL > subscribers addresses are showing up like this, > and they're none too happy about it. > > <0000000511c5b3ae-dmarc-request> > > So their identity is pretty much erased unless > they beef up their signature. Can't tell yet if this has anything to do with Yahoo dmarc changes or not - but curious about it. Scott Bonacker CPA - McCullough and Associates LLC - Springfield, MO
_______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
