The referecne was that neither the smtp nor the quemanager are using large amounts of cpu, nothing is using 100% of the cpu when this happened.
The only sympton is that people can not SEND email they can still receive without a problem
It's important to be precise. Although everyone make gramatical error [even I.], it's a problem when they interfere with the context of your E-mail. If instead of "no one can send a receive" and "the quemanager nor smtp are using enormous amounts of process time", you had used "no one can send but they can receive" and "neither the quemanager nor smtp are using enormous amounts of process time", you would have saved the time that several people put into responding. This isn't an attack, but if you look at both of those quotes, you'll see two key pieces of information that could be taken two different ways.
Can anyone any suggestions, as of now the server appears to be stable and has been for almost 18 hrs.
That's another very important clue.
In this case, I would check the IMail SMTP log files during the time that this was happening. Look for a sample E-mail that you tried to send, and follow the log file entries to see what happened to it.
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers.
Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection.
Find out what you have been missing: Ask for a free 30-day evaluation.
--- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
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/
