I don’t think Exchange has this capability. You should implement an email security product or service to filter the mail and look for those kinds of signals. Most antispam products like Exchange Online Protection should catch it.
]]>Most spammer, phishing email, the “from address ” using friendly email addresses ,looks like customer,boss,etc
and the envelope sender , spammer can send email via SPF pass email service provider.
some users may get trapped in this kind of emails.
So i want to indicate user about possible spam if envelope sender vs “from address” are different.
I check external email gateway, and exchange server 2013 does not have this feature.
Do you have any idea?
all users of SPF records must (to be received correctly by systems running exchange/sender-id) have a null sender-id policy also (or their correct spf policy will be mis-used as a sender-id policy
the sender-id policy is thus
“spf2.0/pra ?all”
meaning if checking from: header (sender-id) return neutral
and their normal spf
“v=spf1 ip4:xx.xx.xx.xx ip4:xx.xx.xx.xx ip4:xx.xx.xx.xx ip4:xx.xx.xx.xx -all”
also note when testing a new spf policy the terminator should only ever be ?all (aka ignore failures)
]]>I recommend looking at it. I haven’t spent enough time with it to give a thorough pros/cons view of it.
]]>Thanks. Lee
]]>I’m going to assume your send connector has both servers as a source transport server.
In that case, you need the same DNS, PTR, SPF requirements for both servers’ public IP addresses.
]]>What is the recommended way to setup PTR records if I have 2 X Exchange servers in a DAG?
The public IP’s are set in the SPF record already and hard fail has been setup.
However each exchange server has its own public IP for example:
Server 1 1.2.3.4
Server 2 1.2.3.5
mail.domain.com resolves to 1.2.3.4 and reverse lookups work ok
Scenario is a client sends from Server 2 1.2.3.5 and gets a bounce back
Client host rejected: cannot find your hostname, [1.2.3.5]
This is because the PRT is not setup and the destination server is running a PRT check and 1.2.3.5 does not resove back to mail.domain.com.
So the answer is to ask my ISP to setup PTR records? Does this sound correct?
]]>