hi Benoit > >Thanks for pointing DMarc out! > >That would be great if someone find a bit of time to have a quick write >up on how to setup DMarc with James. Also it could be great to have >integrations for James retrieving, understanding, and complying with >DMarc policies.
It's not really a James issue at least not in the sense that you're wanting to get your email into an inbox rather than a spam folder. Rather it's a DNS issue, as with SPF - you just need an appropriate text record. DKIM differs, in that it's a two part thing, you need a public key in your DNS, but also James must sign the email with the appropriate private key. If you wanted to check the DMARC of incoming mail, then it would become a James issue, but I don't believe it's worth the pain as checking an online blocklist is straight forward and adequate on it's own - maybe with a bit of spamassassin as backup. Didn't the write ups you linked originate from my own one? Months/a year ago someone from the James community asked me if they could base something on them. I said I was entirely happy for that and remain entirely happy if that was done and if you want to add a DMARC article based on what's at dmatthews.org, just go ahead. I should say that my James foo is out of date as after investigating it, I decided to stick with exim4 as the devil I know being better than the devil I don't. As I've already said though, for SPF and DMARC, it makes no difference if your fighting with James/exim4/postfix etc - these are DNS issues rather mail exchanger issues. Incidentally, if anyone can explain to me why DMARC, which seems to just duplicate DKIM and SPF, is not a stupid technology, I'd be pleased to read that -- David Matthews m...@dmatthews.org --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
