There have been a few different blog posts, Linkedin posts, and email newsletters talking about DKIM2 lately. And oof, most of them seem to get one or more of the details wrong. People mean well, so let's forgive them -- this is a complex thing, and it's easy to misunderstand what's going on. But I think we need a bit of better info out there.
So, here I am, opening my own big mouth, explaining what DKIM2 is. The difference is, I'm actually one of the folks participating in the IETF working group process. I'm a little bit out on the edges in that I'm not necessarily writing code to define or unwind message-instance-tracked message modifications, but I'm observing what's going on, and doing so through the eyes of somebody with a strong email sender background.
In this short (5 minute) video (embedded above or find it on Youtube), for the latest episode of Valimail's "Your Email Authentication and Deliverability Questions Answered" video series, I focus on what senders need to know and care about when it comes to DKIM2. Keys aren't changing (at least not so far), and email senders might actually not need to make any significant changes at all. Let me walk you through what I know so far.
Super smart nerd friends may want to complain that I'm significantly oversimplifying things here and there in my description of intent and current state. If so, they're probably right! There's a lot of complex stuff here going on, and it is tough to condense it down to a short explanation. Forgive me in advance if I seem to gloss over something important.
And keep in mind that the specification is not yet finalized. Things are subject to change.
So keep that all in mind as you watch or listen to my explanation, and my email address is in the video, if you've got any feedback or additional questions that you'd like to bring to my inbox.
There have been a few different blog posts, Linkedin posts, and email newsletters talking about DKIM2 lately. And oof, most of them seem to get one or more of the details wrong. People mean well, so let's forgive them -- this is a complex thing, and it's easy to misunderstand what's going on. But I think we need a bit of better info out there.
So, here I am, opening my own big mouth, explaining what DKIM2 is. The difference is, I'm actually one of the folks participating in the IETF working group process. I'm a little bit out on the edges in that I'm not necessarily writing code to define or unwind message-instance-tracked message modifications, but I'm observing what's going on, and doing so through the eyes of somebody with a strong email sender background.
In this short (5 minute) video (embedded above or find it on Youtube), for the latest episode of Valimail's "Your Email Authentication and Deliverability Questions Answered" video series, I focus on what senders need to know and care about when it comes to DKIM2. Keys aren't changing (at least not so far), and email senders might actually not need to make any significant changes at all. Let me walk you through what I know so far.
Super smart nerd friends may want to complain that I'm significantly oversimplifying things here and there in my description of intent and current state. If so, they're probably right! There's a lot of complex stuff here going on, and it is tough to condense it down to a short explanation. Forgive me in advance if I seem to gloss over something important.
And keep in mind that the specification is not yet finalized. Things are subject to change.
So keep that all in mind as you watch or listen to my explanation, and my email address is in the video, if you've got any feedback or additional questions that you'd like to bring to my inbox.
Comments
Post a Comment
Comments policy: Al is always right. Kidding, mostly. Be polite, please and thank you.