Badmail directory is bad news

I manage many Exchange boxes for various clients. This past year the badmail directory has become a cronic problem because it is filling up and wreaking havoc on server performance and even causing the backup jobs to fail.

The question is how to best deal with this. Just deleting this badmail folder full of files is not the answer, because it just keeps filling back up. I would like to have a solution that deals with the cause of all this "badmail", which I assume is just lost spam. I have written batch files that automatically delete the badmail contents by executing a couple of times a day to keep it from building up, but I'd really like to see this stuff bounced from the server before it became "badmail".
Some of my clients use a server based spam software that keeps the folder manageable, but they too would allow the badmail directory to  grow if it wasn't monitored.
Who is Participating?

I believe this is one of those 'this behavior is by design' MS things that we'll just have to deal with in this version of Exchange. I too use scripts to delete the contents of the folder on a daily basis (with task scheduler). See the following for a better explanation:

Also, the following excerpt is from:

Handling Nondelivery, Bad Mail, and Unresolved Recipients

When a message is undeliverable or a fatal error occurs during delivery, Exchange Server generates a nondelivery report and attempts to deliver it to the sender. SMTP virtual server options provide several ways that you can configure how Exchange Server handles nondelivery.

For tracking purposes, you can send a copy of all nondelivery reports to a specific e-mail address, such as the organization's postmaster account. The e-mail address specified is also placed in the Reply-To field of the nondelivery report. This allows users to respond to the error message and potentially reach someone who can help resolve the problem.

If a nondelivery report can't be delivered to the sender, a copy of the original message is placed in the "bad" mail directory. Messages placed in the bad mail directory can't be delivered or returned. You can use the bad mail directory to track potential abuse of your messaging system. By default, the bad mail directory is located at root:\Exchsrvr\Mailroot\vsi#\BadMail, where root is the install drive for Exchange Server and # is the number of the SMTP virtual server, such as C:\Exchsrvr\Mailroot\vsi 1\BadMail. You can change the location of the bad mail directory at any time, but you should never place the directory on the M: drive, which is reserved for other types of Exchange Server data.

When I was having this problem I found out that m exchange server was bein gused as a mail relay. You most likel have already looked into this but here is a acrticle at Microsoft just in case.;en-us;321825&Product=exchange

Once I did this  the amount of bad mail slowed.

Good luck.
fi8224Author Commented:
Thanks for the reply. I used to do this, but I found that there were actually hackers out there that must have been guessing user accounts and passwords, because the bad mail spam was still filtering through and filling up the "badmail" directory. It was only when I explicity entered the mail domain name and the server ip address in the relay restrictions button. To do this, I checked off "Allow only the list below", and clicked the "add" button and entered the email domain name and the email server's ip address (seperately). You can't get any more explicit than this. This way nobody besides the server and the email domain can relay. At least that's what I was thinking when I did this.
Now here's the rub. This directory still gets email filtered into it, though it's much more manageable. And that's what I don't understand....HOW, and how do I keep it from happening. So I now make a batch file to run everyday and delete the contents to keep it from growing. That's a work arround, not a fix.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Okay I've done all of the above.  I have created scripts to dump bad mail, I've updated all the patches on my server, I have worked with symantec on updating my SMSMSE to the latest version, I made everyone create complex passwords, I have created in excess of 25 dummy accounts with complex passwords and disabled them, I have reapplied service packs, I have restricted the smtp relays down to very specific computers and only our domain and I am still up to 20,000 emails in my badmail directory a day.  Anything else??????  I am doing all of this on a windows 2k with exchange 2k.
I forgot to add to my comment above that I have also added another exchange box with more horsepower in the hopes of retiring the original box that seems to have been stricken with the explosive smtp queue.  I am trying to retire the original box, change my IP settings on my zone file to the new server all in the hopes of alluding the smtp pirates.  Good Idea???
WOW!! Yeah the Ip settings on the Zone will work for what you said.
If the stuff in your badmail directory is spoofed then I'm not sure this will help as you'll still have the same domain name. Considered any anti-spam software?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.