- If we change the "number of recipients per message" to 25 instead of 5, we have 5 SMTP processes hogging all the processor instead of 20 SMTP processes hogging all the processor. If we change the number to 50, we have 2 SMTP processes each using 40% processor for between 1 and 2 minutes.
This is very useful information. This helps prove that the problem is definitely in the delivery of the E-mail.
When changing the number to 50 (so you have 2 SMTP processes), can you tell if they finish delivery of all the 100-or-so mailing list messages in those 1-2 minutes, or whether it takes longer than that? If it is able to finish delivery in those 1-2 minutes, it's averaging about a second or two per E-mail, which is very good (and could possibly account for 100% CPU usage, as it is doing a lot of work).
On the other hand, it sounds like it may be taking longer to deliver the E-mails, in which case that 100% CPU usage may be associated with just one of the recipients, and could indicate a bug of some sort (such as the DNS engine getting an NS record that points back to itself, causing an infinite loop that times out after X seconds).
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers.
Declude Virus: Catches both viruses and vulnerabilities in E-mail, with no annual licensing fees.
--- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
--- [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/
