esquaredc
asked on
Drop failed Spam SMTP connectors Exchange 2003
Hello,
Here is the problem, we are running Exchange 2003 sp2 with GFI spam filtering, and reverse dns turned on. We just enabled allowed auto-office reply in exchange. Some spam that gets through and they trigger the auto reply and that reply stays in the exchange queue because the domain name is invalid and or does not exist. Is an easy way to have exchange drop the connection? Or a way to stop this from happening?
Thank you
Here is the problem, we are running Exchange 2003 sp2 with GFI spam filtering, and reverse dns turned on. We just enabled allowed auto-office reply in exchange. Some spam that gets through and they trigger the auto reply and that reply stays in the exchange queue because the domain name is invalid and or does not exist. Is an easy way to have exchange drop the connection? Or a way to stop this from happening?
Thank you
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I know you closed this recently, but I just found something you may be interested in;
http://www.ivasoft.biz/selectiveoof.html
Selective Out Of Office replies - you can choose which domains or senders receive your OOF message
-red
http://www.ivasoft.biz/selectiveoof.html
Selective Out Of Office replies - you can choose which domains or senders receive your OOF message
-red
That's what I was suggesting, an event sink. Didn't have time to write one for this application however.
Your suggestion for an event sink was to delete ALL oubound OOTO message though wasnt it?
"Sinking" is not really my specialty, but I do appreciate how effective it can be. Ivasoft have a bucketload of create stuff ready to go, and it is priced OK (IMHO)
-red
"Sinking" is not really my specialty, but I do appreciate how effective it can be. Ivasoft have a bucketload of create stuff ready to go, and it is priced OK (IMHO)
-red
The great thing about a sink is that it is either VB or C#. Therefore the rules can be as loose or as stringent as you desire. I disable system messages by connector. Our affiliates have a special connector and they can get those, everyone else, tough luck. :)
Ahhhh I get you now, per connector.
Unfortunately, not being a zen master of code-fu myself, I just block them all -OR- have them very vague (some people will get offended by them anyway) - it is a major security violation at the best of times
-red
Unfortunately, not being a zen master of code-fu myself, I just block them all -OR- have them very vague (some people will get offended by them anyway) - it is a major security violation at the best of times
-red
Another option is to create an event sink that checks for a message going out and that is an out of office message and deleted it.