Qmail-LDAP
[Top] [All Lists]

Delayed Mail

To: qmail-ldap@qmail-ldap.org
Subject: Delayed Mail
From: Matt <mhoppes@gmail.com>
Date: Fri, 23 Mar 2007 09:47:07 -0400
Delivered-to: sp-com-lists@consult.net
Delivered-to: qmail-ldap-list@securepoint.com
Delivered-to: mailing list qmail-ldap@qmail-ldap.org
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=hmvT7cEXZQ4ZIRGRYee5OSlvTMNQv0ZLvBie/UYxmasc2i2JNDZ6YEeFY6FT5nEBFheMWyw/liju+qFW93WtBxaOooeBqDr/TkSh/VgmtnJAuGIHMrcq0kTd4JUnn6ldDhIx5/gG/gda9g5gnolVubSK0b+npBk5LgeNleiaMMk=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=TDzpenh06+Wp3d5SA7bjY+t1kHpDEoGeSaiF0xQEWwDtDsyEf96OdTzBy8KgBH3B/gh1Uteq+0ntycm3MRPMG9dCnug1TCXG7jw/Xe6cJas4LcW+kmU66Jc0y/nsB6lyelPgZimnidPe+lF0UPtrM7sZmtlsDXeW0mX9Se4t0sc=
Mailing-list: contact qmail-ldap-help@qmail-ldap.org; run by ezmlm
Hi List,
I have 9 mail servers, using ldap as the backend authentication system.  They all deliver to a NAS unit.     Out of the 6 system, 3 are old machines (500-800mhz), 2 are dual core xeons, and 1 is a P3 2.8Ghz.   All have 1.5GB of memory, with the P3 and xeons having 2GB of memory.

Here's my question... what would cause a high level of unprocessed messages?    On the 3 old machines I never see this problem (odd!), yet the P3 will often end up grinding and slowing down, maxing out its connections, and then finally start getting unprocessed messages.   At that point, I firewall off port 25 and let us deliver.

I have checked and I am running the same version of SPAMD, CLAMAV on all the systems.    My guess is that a spam run is triggering spamd to do some extensive scanning on the mail.... but then why would the older machines not have the same issue?  Even when/if they get totally bogged down, they have never ended up with unprocessed messages.


TO BE RESOLVED:
1 - What might be causing these unprocessed messages?  Is it a bottle neck?
2 - How do others adjust their concurrencyincomming?   It seems that even 40msg concurrent can swamp the P3 2.8GHz , depending on the incoming mail... yet it will be fine for weeks... likewise, I've seen the Xeons go fine with a max of 254, but that can easily kill them if a huge spam run comes in.

Thoughts?
<Prev in Thread] Current Thread [Next in Thread>