Despite what everyone said, I'm excited specifically for DKIM2. As someone that had managed a mailing list, that one is probably the hardest thing to juggle around and DKIM2 layering seems to fix that issue neatly. I hope postfix has a guide proto.
Aw hell. How many things do I have to set up just so that I can send e-mails from my own domain?<p>The effect of all this seems to be less "making e-mail secure" and more "making it so that only Google, Apple, and Microsoft can send e-mail successfully"
And sometimes if you do everything right, it still doesn’t work.<p>Recently I checked the IP against blacklists, waited a few months, did all of the other things, and then found out Microsoft bounces my entire VPS’s IP range. Appealing did not help.<p>They intermittently block Cloudflare email routing IPs too. All of these security measures and still it comes down to the IP address of your sender.
Eh, I read the article, and at most you only have to wait for your MTA to update to add the required headers and update your DNS records and you are golden. It still uses the same key you generated as far I'm aware.
I really don't understand what the original DKIM was not sufficient. Can someone ELI5? If you can verify that a message was signed by the outgoing server, then why isn't that the end of the story? Who cares how or why it got forwarded, or whatever else?
Sounds pretty cool! I wonder if it closes enough holes that we could finally stop using SPF at all?
Can someone distill this down to how it will be used by the big three email providers to make it impossible to use email except through them?
If anything, this moves it towards anyone having more access to everything. For example, reject isn't going to be treated anymore as a bounce. Now, provider policies still can and would be BS, but the standard doesn't tell them to do it certain way.
> by the big three<p>Which big three?<p>Gmail has something like 1.8 billion users. iCloud mail around 1 billion.<p>Microsoft with 400 million users of its email is closer to Yahoo! Mail (225 million users) than to the big two.
First time I'm reading about this, I'm glad there's progress in this area.<p>The JSON DSL for rewriting emails feels like a spammer/exploit vector waiting to happen. Some product is going to spam filter before applying reconstruction rules, or get tricked into applying reconstruction rules when it shouldn't, and spammers and scammer are going to abuse it.<p>Until either Google or Microsoft will adopt these standards, they'll remain effectively meaningless most likely. But even so, it's good to know people haven't given up on fixing email's spam problem entirely.
Anyone migrated from exchange to stalwart? Curious about results
well done<p>you're among the first few who have done it:<p><a href="https://github.com/mjl-/mox/issues/404#issuecomment-4362749809" rel="nofollow">https://github.com/mjl-/mox/issues/404#issuecomment-43627498...</a>
[flagged]