Need Help with Spam Prob 4

[spook007]

I'm running Small Business Server 2003. Recently I've been receiving email notification from the server that we have a large volume of emails on our SMTP Queue. I've taken a look at the emails and they are all these Chinese advertisement. The emails that I've got in the queue are emails that my server can't find a recipient for, so they sit in the queue and it tries again until it can find someone or it expires. I've disconnected all users from the server to see if the emails were originating from one of our clients, but they were still being generated long after the clients were removed. Any suggestions are welcomed! Thanks.

 

[devastator]

More than likely you are just suffering from NDR's (Non Deliverable Receipients). If your exchange is set to accept all email address sent to yourdomain then the ones that don't exist like spam@yourdomain.com the Exchange server tries to send an NDR back and since the SPAM or email was forged and can't be resolved it just sits in your Exchange que.

You can turn off NDR's to the Internet through SBS under Server Management, under Advanced Management DOMAIN (Exchange), Global Settings, Internet Message Format, on the right side right click and go into properties for "Default", and go to Advanced and turn off "Allow Non Delivery Reports".

I don’t know half of you half as well as I should like, and I like less than half of you half as well as you deserve. ~ Baggins

 

[spook007]

Is there any way that I can configure exchange to not send all mail sent to my domain in that case? I don't want to be contributing to the spam problem out there!

 

[devastator]

Your not really contributing since they all sit in your que though some forged addresses do get delivered back to the spoofed address. Try the above solution or get a 3rd party filter like X-Wall spam filter that allows you to import you GAL (global address list) and verifys emails sent to your domain exist. If they don't x-wall drops the connection / email at the SMTP level, which is the top level so your Exchange server never gets hit.

Either solution will work but the first solution still consumes bandwidth since exchange excepts the original message. Incorporting SPAM filters helps such as the ones offered by Microsoft for Exchange 2003.

I don’t know half of you half as well as I should like, and I like less than half of you half as well as you deserve. ~ Baggins

 

[forbsy]

Exchange 2003 natively has the ability to check Active Directory for a vailid user before attempting to deliver an email:

http://weblogs.asp.net/dlemson/archive/2003/10/17/52019.aspx

Forbsy

 

[devastator]

Forbsy,

Yeah i do remember seeing that option availible in Exchange 2003.

Star for the article / reminder.





I don’t know half of you half as well as I should like, and I like less than half of you half as well as you deserve. ~ Baggins

 

[spook007]

Thanks guys... Your explanations helped me understand what is really happening here. I appreciate your responses!