Mail queue filling up on Windows SBS 2003 server

I have a Windows Small Business Server 2003 server with the mail queue filling up and depleting hard disk space on the server.  The exchange server logs grow to more than 1GB.  I have verified that the server is not an SMTP relay.  One thing I noticed is that in the ESM Queues, every Queue shows the sender as "Standardbank.co.za"<ibsupport@standardban.co.za".  How do I prevent this constant mass emailing? I have checked each PC and server on the network for viruses/spyware and confirmed that we are clean.  Does this sound like it is malware related?

Thanks,
Rick Ferreira
RickFerrAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

schlueterCommented:
I think there will be some malware on your clients, because it's easy to find out if you have an open relay. If you want to just give me your IP and I'll check.
I'd suggest to find out which computer opens SMTP connections to your server (http://support.microsoft.com/kb/282497).

If you've not enabled anonymous mailing, you should be able to find out who sends out your mass mails (normally, a SBS sends statistics each day/week).
0
dhruvarajpCommented:
here is what you might want to do:
http://support.microsoft.com/kb/886208
0
sunnyc7Commented:
What anti spam software are you using

This is definitely spam attack

Go to www.mxtoolbox.com and test if you are open relay

Thanks
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Alan HardistyCo-OwnerCommented:
If the sender is a 3rd party on your server then you are an Authenticated Relay.
Please have a read of my article for what to do and how to identify the user / password that has been compromised, change the password, restart the SMTP service and then empty your queues.
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2556-Why-are-my-outbound-queues-filling-up-with-mail-I-didn't-send.html 
You will also need to get yourself off the Blacklists after you have solved the problem.
www.mxtoolbox.com/blacklists.aspx
You should then instigate Account Lockouts on your server to prevent accoutns from being brute forced and then force regular password changes to stop this sort of attack from happening again,
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Barry GillChief of StaffCommented:
this is part of a phishing attack.
Phishers usually use botnets to deliver because the banks (like Standard Bank) pay investigators to track them down (I would send a mail to secure@standardbank.co.za and ask them what variants you should be looking for - not guaranteed response) - so you need to be looking for trojans/infections, not open relays.

standardban.co.za belongs to Standard Bank (checked it on the ZA registar, http://co.za/cgi-bin/whois.sh?Domain=standardban&Enter=Enter) and they usually have SPF in place
(Received-SPF:       fail (google.com: domain of ibsupport@standardbank.co.za does not designate 194.201.253.112 as permitted sender) client-ip=194.201.253.112;

Authentication-Results:       mx.google.com; spf=hardfail (google.com: domain of ibsupport@standardbank.co.za does not designate 194.201.253.112 as permitted sender) smtp.mail=ibsupport@standardbank.co.za)

So there is NO WAY they would have any application that would be trying to send this out.

Definitely an infection.
0
Barry GillChief of StaffCommented:
lol, just checked the spf on standardban.co.za and they have not set it... but their messages come from standardbanK.co.za usually - they must have purchased the domain to prevent phishers from using it... I have sent them a mail rectify.
0
Alan HardistyCo-OwnerCommented:
You won't be an open relay - but you will be an authenticated relay.
I have seen this time and time again recently.  Probaly about 30 servers compromised in this way, including two clients and my own Exchange 2010 server!
My article will assist you in resolving the problem.
0
RickFerrAuthor Commented:
I have enabled Sender Filtering in ESM and added the sender's email address (ibsupport@standardbank.co.za) to the list of senders to block.  This seemed to resolve the problem for about a day and half.  The problem of the mail queue started up again.  But now when I look at the sender's email address in the message stuck in the mail queue they are "nlpostcode4@hotmail.com" and "info@ls.org".    I am getting a bunch of 7004 and 3015 events in app log.  Here are two samples:

7004
This is an SMTP protocol error log for virtual server ID 1, connection #16. The remote host "207.115.20.23", responded to the SMTP command "mail" with "553 5.3.0 flpd121 DNSBL:ATTRBL 521< 69.68.136.156 >_is_blocked.__For_information_see_http://att.net/blocks  ". The full command sent was "MAIL FROM:<nlpostcode4@hotmail.com>  ".  This will probably cause the connection to fail.

3015
A non-delivery report with a status code of 5.3.0 was generated for recipient rfc822;shurefyre@prodigy.net (Message-ID <34745SERVER013FB1Fx0000106e@ocfta.com>).  
Causes: Exchange mistakenly attempted mail delivery to an incorrect MTA route.  

If feel like if I add the two new email addresses to the sender filter list that I am just applying a temporary fix.  How do I get to the root of where the spam is starting.  Should I look at the PCs on the network again.  I have already gone through and cleaned any spyware/viruses detected.
Thanks
0
Alan HardistyCo-OwnerCommented:
Please download and install Vamsoft ORF 30 day trial from www.vamsoft.com and set the software to log mode only.

Then stop the smtp service on your server.

Load up the Vamsoft logs, start the SMTP service and refresh the logs (F5).  Check the logs for the first entry with a sender that is not a sender on your domain and then cross reference the date / time to your security event log and just before the exact time in the Vamsoft logs, you should see a corresponding login event.

Check the username in the login event and then change the password for that account.  Restart the smtp service again and then keep refreshing the Vamsoft logs.

Hopefully the problem will be gone, but if not, repeat until it does stop.
0
RickFerrAuthor Commented:
Thank you. I did find that there was a user account named Admin that someone may have created at some point with a nonsecure password.  As soon as I reset the passwork on this account the bogus emails stopped being sent.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.