Some one asked me recently about an interesting scenario on which emails are send on behalf of another party, and how Exchange Online Protection (EOP) will act in this case.
There are two FROM values in the SMTP world:
- RFC 5321 (MailFrom)
- RFC 5322 (From)
Outlook displays the RDC 5322 From address to end users, and this is the address that is used in the user’s safe sender list.
EOP inspects both values for blocked and allowed senders and domains. Exchange Online Protection EOP and outlook handle safe sender lists differently.
In most cases, those two values are the same which is normal. Things become interesting when someone is sending emails on behalf of another party. Let us take a simple example:
- Contoso corporation is trying to send email to their customers and they contracted with third party to send their news emails.
- The contractor company sends the news email on behalf of contoso.
- The email that was sent has the following values:
- RFC 5321 MailFrom: firstname.lastname@example.org
- RFC 5322 From: email@example.com
- One of the customers who are using EOP receives the news email, and in Outlook, he can see that the sender is firstname.lastname@example.org.
- The user added this address to the safe list senders.
- Because EOP inspect both RFC from addresses, the next time an email was sent by the contractor, EOP will white-list that email respecting the user’s safe list.
Usually the RFC5321 address is the one used by EOP to do SPF checks and send NDR or bounced messages.