This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Block emails spoofed p2 headers

I am looking to block emails where the FROM in the P2 header is being spoofed using our email addresses.  I can kill these off at the exchange server by removing the ms-exch-smtp-accept-authoritative-domain-sender on the Internet facing domain connector.  Is there a way to kill these via "Email Protection"?  If I add our domain in the "Sender Blacklist" does this look at the P2 header or only the P1 like SPF?

P1 header
mail from: someone@someotherdomain.com
rcpt to: user1@mydomain.com
data

P2 header
from: user1@mydomain.com (problem)
to: user2@mydomain.com
Subject: P1 and P2 headers are different
The P1 and P2 headers will be different in this message.

Thanks,
                 Jim


This thread was automatically locked due to age.
Parents
  • Hey Jim, 

    I'm having the same issue with spoofed emails using the FROM in the P2 header, so I decided to kill them by removing the ms-exch-smtp-accept-authoritative-domain-sender permissions on my receive connector. But now UTM is not able to send Quarantine reports, as UTM sends the reports to that receive connector using one of our email addresses and Exchange is rejecting them now.

    How are you handling the Quarantine reports after changing those permissions on the Exchange receive connector?

    Thanks!

  • Wouldn't enabling SPF help with this?

Reply Children
  • I have SPF enabled on UTM and have SPF records set up for my domain. The thing is UTM uses SPF to check only the MAIL FROM field on the P1 headers of an email. Emails can still be spoofed by altering the FROM field on the P2 headers of an email. Unfortunately, UTM does not check P2 headers of emails, thus allowing spoofed emails to still come through. 

  • See my posts above from 21,22 Sep 2015.  The problem is that the From field comes after the DATA command.  Only the Sender field is considered for email-address blacklists, DKIM and SPF.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • By design, SPF is checked during the HELO.   No compliant SPF implementation will detect what you want.

    It seems lime a regular expression pattern match might achieve your objective.