Editing Sender Policy Framework (section)

=== Header limitations ===
As SPF increasingly prevents [[Email spoofing|spammers from spoofing]] the envelope-from address, many have moved to only spoof the address in the From field of the mail header, which is actually displayed to the recipient rather than only processed by the recipient's [[message transfer agent]] (MTA). SPF (or [[DKIM]]) can be used together with [[DMARC]] though, to also check the From field of the mail header. This is called 'identifier alignment'. 

Custom proprietary implementations are required to protect against such display name spoofing and cannot utilize SPF.<ref>{{cite web|title=Create an MIMECAST inbound lockout policy to STOP Email SPOOFING|url=https://community.mimecast.com/groups/administrators/blog/2016/02/05/create-an-mimecast-inbound-lockout-policy-to-stop-email-spoofing|archive-url=https://web.archive.org/web/20170826072027/https://community.mimecast.com/groups/administrators/blog/2016/02/05/create-an-mimecast-inbound-lockout-policy-to-stop-email-spoofing|archive-date=26 August 2017|access-date=25 August 2017}}</ref><ref>{{cite news|title=Prevent spoofed messages with spoofed senders detection|url=https://knowledge.broadcom.com/external/article?legacyId=HOWTO119230|access-date=25 August 2017}}</ref><ref>{{cite web|title=How antispoofing protection works in Office 365|date=23 February 2016 |url=https://blogs.msdn.microsoft.com/tzink/2016/02/23/how-antispoofing-protection-works-in-office-365/|access-date=25 August 2017}}</ref>