Larry,
Since it takes two to tango, er "reject", it is too bad Google & L-Soft
don't also cache which receiving systems bounce such messages. Then they
wouldn't have to rewrite the From for everyone, and users of ESPs which
never did or have backed off of full "reject" implementation wouldn't
have the ugliness to deal with.
I say that naively, having no idea how much trouble it would be to split
the outbound stream like that, some with original From and some with
DMARC-shielded From. Nor to maintain the cache of which ESPs bounce them
(which does imply letting some test messages get bounced periodically).
I cite as hopeful signs the fact that Gmail and Yahoo Mail seem to be
passing into the Spam folder list messages that otherwise would be
subject to the "reject" setting of Yahoo Mail and AOL. Better, when they
user consistently marks them "Not Spam" then the go back to the inbox.
At least this seems true based on some testing of messages through a
Yahoo Group (which does not rewrite the From).
https://groups.yahoo.com/neo/groups/GroupManagersForum/conversations/messages/52045
Of course, that testing was a couple of days ago and the situation is fluid.
Oh well. I guess I'll not so easily keep the ugliness out of my inbox.
-- Shal
On 4/25/2014 4:49 PM, Larry Finch wrote:
I have some insight into what is happening here. L-Soft just updated
listserv v 16 to do exactly what you describe (I belong to L-Soft’s site
manager and list owner groups). The patch causes listserv to check for a
DMARC DNS record, and if one exists with p=reject it rewrites the FROM
field in the header with what you describe. If the originating IP does
not have a DMARC record or has one and does not have p=reject listserv
ignores it. So either Google uses listserv or they read the listserv
lists also and copied it.
Either way, it is a very ugly workaround.
best,
Larry
_______________________________________________
dmarc-discuss mailing list
[email protected]
http://www.dmarc.org/mailman/listinfo/dmarc-discuss
NOTE: Participating in this list means you agree to the DMARC Note Well terms
(http://www.dmarc.org/note_well.html)
