On 2014-02-26 23:12, John Levine wrote:
If you blindly followed Linkedin's p=reject advice, you'd find
yourself bounced off this list.
show an sample on that
if you forward dmarc protected mails you have to add the forwarding
mailserver ip into opendmarc ignorehost to prevent you from being
disconnected, its same with spf checking
and i think its sign of this maillist here is not supporting dmarc, not
linkedin that sooks :=)
i have not seen linkedin fail here, only fail linkedin do is to have a
ipv6 only hostname in mx
postfix logs this as a warning
and i begin to see more hosts that have mx hostnames with hostname in
mx, but no ip on that hostnames a or aaaa was missing
postfix logs this as a warning
Paypal realized that and fixed it,
good, if paypal stops adding https links into there campain emails
aswell, and only using https for custommers it would not be the most
phished site on phishtank
Linkedin knows about if and chooses not to fix it.
fix what ?
So nobody sensible
trusts Linkedin's advice unless they have elaborate meta-advice about
when DMARC advice is credible and when it isn't.
lol, you must show a sample here
_______________________________________________
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)
