Why are there 397 queues in Exchange 2003 on SBS 2003?

The other day this client called me claiming that no emails were going out. I noticed they had Exchange configured to send mail out to a smart host. What is a smart host anyway? I changed it to send mail out using DNS and that seemed to get mail flowing again. I do realize that there are other consequences of me changing that setting - in fact I've dealt with this very same problem but it's been so long ago that I don't recall the exact sequence of steps required to clean up Exchange and get their mail flow secure and healthy again.  

I just completed the test to see if their server was an open relay and it passed the test. I don't know what new features Exchange 2003 has over 2000 but I just need to know how to get these queues cleaned up. Right now I don't know how many of these email message are bogus but I'm guessing most of them are. Thanks for any help - they're breathing down my neck now.....   :)
WineGeekAsked:
Who is Participating?
 
baconyiConnect With a Mentor Commented:
virtual smtp server, right click, properties, access tab,

just make sure you note what the settings are currently, but try changing the relay security on the bottom there.  dont change the outbound security actually, im not sure if that part is necessary or even if it can be done, has to do with ISP also.  but i do know the relay option is important.
Billy
0
 
baconyiCommented:
check the outgoing permissions and make sure only the server has rights to relay messages.  we had a client that was hit, domain password was hacked and they were able to send out with our server because we had allow authenticated users checked... changed the domain password and it was fine since then...

Billy
0
 
WineGeekAuthor Commented:
where is that done in the server properties or int he properties of the virtual smpt server or.....?
0
 
WineGeekAuthor Commented:
right now I"m following the instructions in this document but thank you for yoru input so far...

http://www.amset.info/exchange/spam-cleanup.asp

0
 
baconyiCommented:
no prob, it just happens that my particular client had this problem, so we had to actually change the domain admins pw... but the relaying part was also changed for this client which did have something to do with that.  let me know what happens or if you find the right solution.
Billy
0
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.