In light of all the chatter around the new Microsoft sender requirements, I’ve started to capture and catalog the various questions I’m getting from senders as they work toward ensuring that they fully comply with this updated guidance.
The one question I’ve received the most often so far, by far, is this: What exactly does it mean to have a compliant P2 sender address? And what does it mean to have a sender address that can accept replies? What about no-reply addresses? What about mail routing, DNS, etc.?
In Microsoft’s announcement of the new requirements, when you scroll down to the comments, you’ll find helpful clarification from someone at Microsoft, providing more detail on this point. (Search for “regarding RFC compliance.”) But if you’re not interested in sussing this out on your own, check out my latest Valimail video, where I break down exactly what it means to have a compliant sender address (and what are P1 and P2 addresses, anyway)?
Find it embedded above or click here to check it out on Youtube.
In Microsoft’s announcement of the new requirements, when you scroll down to the comments, you’ll find helpful clarification from someone at Microsoft, providing more detail on this point. (Search for “regarding RFC compliance.”) But if you’re not interested in sussing this out on your own, check out my latest Valimail video, where I break down exactly what it means to have a compliant sender address (and what are P1 and P2 addresses, anyway)?
Find it embedded above or click here to check it out on Youtube.
Got more questions? Keep 'em coming! Helping to spread the understanding of modern email sender requirements is something that I truly enjoy doing.
1
Comments
Hi Al! Thank you for this. You say that in your opinion both an A and MX is needed. Do you see issues if the subdomain (used for a Header From) does not have an A record, even if the A record exists for the root/primary/parent domain and the MX record exists for the subdomain? Thanks, Steve.
ReplyDelete