Authentication-Results: iecc.com; spf=pass
[email protected]
spf.helo=dragon.trusteddomain.org;
dkim=fail (bad signature) header.d=forged.junc.eu header.b="OI+bj08L";
dmarc=fail.none header.from=forged.junc.eu policy=none
its still my hope a maillist that is created for showing how dmarc works
should stop create false alarms on domains that use p=reject where users say
its a problem with it, when its not
if this maillist here would change i bet it would be more understandelble on
what not to do
The advice hasn't changed: don't set a DMARC policy other than p=none on
domains used by human users. We know that some large domains have
disregarded that advice, but it doesn't make it any less correct.
Regards,
John Levine, [email protected], Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.
_______________________________________________
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)
