SMTP Server

[Bill.Bowen]

Our SMTP server handles approximately 750 messages per day to/from the Internet. Many of these are from spammers attempting to "harvest" names from our Exchange Server (which the SMTP server forwards internal mail). For example, when the spammer sends a message to an invalid user, the SMTP server will return an undeliverable message to the sender, thus providing the spammer a method of delivery confirmation. Is there a way to disable the non-deliverable message? Or is there another way to combat these scumbags? We use three ORDB services. I've been culling the SMTP log daily for domain addresses to block via a policy (SMTP Sender/Recipient contains "@example.") but it seems this effort is not worth the meager returns. Is there a better way to wage this war? Any reasonable suggestions would be greatly appreciated. Thanks.

[Pascal]

Hi Bill,

I can't see a way to prevent the undeliverable message from going out, but perhaps the answer would be to setup a catch-all email account. If it doesn't match any of your legitimate users, simply let it fall into the catchall, which you can purge / delete whenever you see fit.

The SMTP Server will still be accepting the messages though, but at least you won't be sending them the 'non deliverable' messages.

[labull]

Try checking "Block Blank Return Path" on the WinGate SMTP server.

Gatekeeper - Mail Server - Receiving


I think this is how it will work:

NDRs are sent with no return path to prevent looping. WG SMTP will reject the message from Exchange.

All these rejections will end up in whatever your Dead Mail inbox is but they should be easy to manage.

Let us know if this works.

Larry