08-11-2016 04:08 AM
Hi,
With a view to helping reduce inbound spoofed mail I recently enabled reverse PTR & forward 'A' checking against our 'suspectlist' sender group which behaved fine however having then also created an additional sender group 'Unverified' along with a new more strict throttle policy 'throttlemore' began to see issues with test emails not coming through when enabling the 'check for PTR record not existing'. When checking inbound message headers each hop inbound looks fine with dns/ip entries as expected. Has anyone experience a similar issue and was there a straight forward resolution ?
many thanks
08-11-2016 04:23 AM
Hi Sandy,
Give the following articles a read, they have multiple methods to deal with spoofing emails, hope they help!
Regards,
Raed
08-11-2016 04:54 AM
HI Raed,
Many thanks for this, I should also add that we are attempting to target those senders also pretending to be from a domain they are sending from hence following the steps in the ESA_9-7 User guide to implement sender verfication'
Chapter 7 Defining Which Hosts Are Allowed to Connect Using the Host Access Table (HAT)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide