Jump to content

ivanp74

Members
  • Posts

    4
  • Joined

  • Last visited

About ivanp74

  • Rank
    Newbie
    Newbie

Profile Information

  • Gender
    Not Telling
  • Location
    USA
  1. I'm starting to think blocking Failed RDNS is not such a good idea "..from NAM02-BL2-obe.outbound.protection.outlook.com ([104.47.38.42] RDNS failed) by..." RDNS is failing in from those server and a few more legit senders. I was hoping to trap the spammers, but the net is too wide, need something smaller.
  2. Awesome! Upgraded. SPF enabled didn't stop Failed RDNS emails. I had to add a rule under Rules / Mail Transport Protection It works as expected now. Thanks a lot!
  3. ESET Mail Security Version 4.5 for old Exchange Server I don't see an option to add rules for headers...just message body.
  4. Spam emails getting through with this headers:Received: from [171.234.173.26] ([171.234.173.26] RDNS failed) by mx.mail........com with Microsoft SMTPSVC(6.0.3790.4675); I can't find a setting on Eset Mail Security / Antispam engine setup, or any other place, to deny path to failed reverse-dns domains. Does it exist within this product? Or is it part of the mail server?
×
×
  • Create New...