I got the impression that multiple instances of smtp32.exe was normal.
it is. Scott's queue kicker causes more of them to wake up, up to a limit of something like 30, go look in queue for someting to pickup and deliver.
but once they have delivered a msg (or can't find any to deliver), they should terminate.
Is this not the case? Or is it the extent of the multiplication that is out of whack?
What could have caused smtp32.exe to "get zombied" if that is the problem?
SMTP32 "input" is something its picks up from the queue. If a file has a busted format that disagrees with SMTPD trying to understand, the process goes zombie.
How about using isplcln?
If the killer msg is older than what you set as oldest in isplcln, then the killer msg will be daid, mon, and zombies be gone.
If the message has been in the spool for weeks causing the problem would you think that isplcln would get rid of it?
yes, ispcln doesn't read the msg as msg, it just kills it as a file.
For what it's worth, I did run isplcln the first day I noticed the problem and I have rebooted the server three times now. It occurs to me that if that was really the first day that the "killer message" was in the spool, my parameters for isplcln wouldn't have gotten it (I set it for 3 days).
yep, that's why ispcln isn't the tool to fix the problem today.
Len
_____________________________________________________________________ http://MenAndMice.com/DNS-training: New York; Seattle; Chicago IMGate.MEIway.com: anti-spam gateway, effective on 1000's of sites, free
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
