Matt Yahna
2004-03-24 16:46:02 UTC
We currently use the following configuration for blocking Spam:
Solaris 8
Mimedefang 2.41
SpamAssassin 2.63
Perl 5.8
Sendmail 8.12.11
Over the weekend, I noticed several message in the syslog that the milter
timed out, and that some messages were taking several hours to finally get
through the system. We were still blocking spam, but it was taking a long
time. I was getting reports from users that they were not getting messages
from clients, and would see in the log that their message was refused
because the milter was too busy to accept it. This never used to happen, we
would get emails right away even after they went through SA. I have tried
adding more mimedefang instances to the multiplexor, but they just get used
and get busy. I have 20 running right now, and all are busy. Does anyone
have any idea why this just started happening? I thought maybe it was
because of some of the new rules that I installed, but even after turning
most of them off, I still have the problem! I have the following rules
installed (all downloaded recently):
99_FVGT_Tripwire.cf airmax.cf random.current.cf antidrug.cf
backhair.cf sa-blacklist.cf bigevil.cf
sa-blacklist.current.uri.cf bogus-virus-warnings.cf
chickenpox.cf
evilnumbers.cf weeds.cf
I ran a spamassassin -d --lint and receive no errors.
Here are some of the errors in my syslog:
Mar 24 09:33:42 spawn mimedefang-multiplexor: [ID 316382 mail.info] Killing
busy slave 17 (pid 23428): Busy timeout
Mar 24 09:33:42 spawn mimedefang[5240]: [ID 847421 mail.error] Error from
multiplexor: ERR Filter timed out - system may be overloaded (consider
increasing busy timeout)Mar 24 09:33:44 spawn mimedefang-multiplexor: [ID
364399 mail.info] Slave status: Stopped=0 Idle=0 Busy=20 Killed=0 Queued=0
Msgs=3193 Activations=3183Mar 24 09:33:44 spawn sm-mta[23419]: [ID 801593
mail.error] i2OGSDCS023419: Milter (mimedefang): timeout before data read
Mar 24 09:33:45 spawn sm-mta[23419]: [ID 801593 mail.info] i2OGSDCS023419:
Milter (mimedefang): to error state
Mar 24 09:32:10 spawn sm-mta[23532]: [ID 801593 mail.info] i2OGW3iQ023532:
Milter: data, reject=451 4.7.1 Please try again later
Any help would be greatly appreciated.
- Matt
Solaris 8
Mimedefang 2.41
SpamAssassin 2.63
Perl 5.8
Sendmail 8.12.11
Over the weekend, I noticed several message in the syslog that the milter
timed out, and that some messages were taking several hours to finally get
through the system. We were still blocking spam, but it was taking a long
time. I was getting reports from users that they were not getting messages
from clients, and would see in the log that their message was refused
because the milter was too busy to accept it. This never used to happen, we
would get emails right away even after they went through SA. I have tried
adding more mimedefang instances to the multiplexor, but they just get used
and get busy. I have 20 running right now, and all are busy. Does anyone
have any idea why this just started happening? I thought maybe it was
because of some of the new rules that I installed, but even after turning
most of them off, I still have the problem! I have the following rules
installed (all downloaded recently):
99_FVGT_Tripwire.cf airmax.cf random.current.cf antidrug.cf
backhair.cf sa-blacklist.cf bigevil.cf
sa-blacklist.current.uri.cf bogus-virus-warnings.cf
chickenpox.cf
evilnumbers.cf weeds.cf
I ran a spamassassin -d --lint and receive no errors.
Here are some of the errors in my syslog:
Mar 24 09:33:42 spawn mimedefang-multiplexor: [ID 316382 mail.info] Killing
busy slave 17 (pid 23428): Busy timeout
Mar 24 09:33:42 spawn mimedefang[5240]: [ID 847421 mail.error] Error from
multiplexor: ERR Filter timed out - system may be overloaded (consider
increasing busy timeout)Mar 24 09:33:44 spawn mimedefang-multiplexor: [ID
364399 mail.info] Slave status: Stopped=0 Idle=0 Busy=20 Killed=0 Queued=0
Msgs=3193 Activations=3183Mar 24 09:33:44 spawn sm-mta[23419]: [ID 801593
mail.error] i2OGSDCS023419: Milter (mimedefang): timeout before data read
Mar 24 09:33:45 spawn sm-mta[23419]: [ID 801593 mail.info] i2OGSDCS023419:
Milter (mimedefang): to error state
Mar 24 09:32:10 spawn sm-mta[23532]: [ID 801593 mail.info] i2OGW3iQ023532:
Milter: data, reject=451 4.7.1 Please try again later
Any help would be greatly appreciated.
- Matt