On Sun, Feb 12, 2017 at 10:10:05PM +0100, richard lucassen wrote:
> host -t txt _dmarc.artifact-software.com
> "v=DMARC1; pct=100; p=quarantine; adkim=r; aspf=r"
>
> And as this mail is sent by cloud9, opendmarc does what it is supposed
> to do.
Say no to DMARC. Don't make the mistake of outsourcing your inbound
email policy to random strangers who either don't understand all
the ways in which DMARC is flawed, or don't care about collateral
damage.
There are good reasons why RFC7489 is an "informational" rather
than a "standards track" RFC. While DMARC may reduce Yahoo's abuse
desk costs, we don't have to play along. Though DMARC may reject
some forged Yahoo email, there's still plenty of 419 email from
the real Yahoo.
DO NOT publish DMARC policy. DO NOT check DMARC policy, except
perhaps as a small bump in a composite spam score.
--
Viktor.
