RE: [Mimedefang] timeout before data read?
Aleksandar Milivojevic wrote:
> Rich West wrote:
> > Now, if I bring down both mimedefang and sendmail and bring
> > it back up
> > again, I can get some mail to come through, but very little
> > before it
> > starts spitting out these errors again.
> ...
> Oh, BTW, multiplexor timeout is controlled in
> /etc/sysconfig/mimedefang
> (well, at least on RedHat type systems):
>
> MX_BUSY=1740 # (29 minutes, we give up before sendmail does)
>
> sendmail timeouts are defined in sendmail.mc:
>
> INPUT_MAIL_FILTER(`mimedefang',
> `S=unix:/var/spool/MIMEDefang/mimedefang.sock, F=T,
> T=S:30m;R:30m;E:30m')
Also consider adding a line like this to your sendmail.mc:
define(`confMAX_MESSAGE_SIZE', `52428800')dnl
The number is in bytes: I have it set to 50 MB
50MB * 1024 KB/MB * 1024 B/KB = 52428800 B
Matthew.van.Eerde (at) hbinc.com 805.964.4554 x902
Hispanic Business Inc./HireDiversity.com Software Engineer
perl -e"map{y/a-z/l-za-k/;print}shift" "Jjhi pcdiwtg Ptga wprztg,"
___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] timeout before data read?
Rich West wrote: Quite suddenly, and consistently, today at around noon, I started seeing the following messages in my maillog, and the load average on the system went through the roof (load average shot up beyond 22!) shortly afterwards. Nov 17 15:02:51 cranium sm-mta[24072]: iAHK1XJR024072: Milter (mimedefang): timeout before data read Nov 17 15:02:51 cranium sm-mta[24072]: iAHK1XJR024072: Milter (mimedefang): to error state Nov 17 15:02:51 cranium sm-mta[24072]: iAHK1XJR024072: Milter: data, reject=451 4.3.2 Please try again later Nov 17 15:02:51 cranium sm-mta[24072]: iAHK1XJR024072: to=<[EMAIL PROTECTED]>, delay=00:01:01, pri=32062, stat=Please try again later Now, if I bring down both mimedefang and sendmail and bring it back up again, I can get some mail to come through, but very little before it starts spitting out these errors again. And, it seems, that mimedefang keeps being forced to spawn a new process, leaving the old one around to spin its wheels, and the new process will generate the same error, and then spawn a new process because of the failure, and so on and so on, becoming a very fast and sick cycle. :( There were some discussions on the list about this recently. Basically what happens is that you either configured mimedfang-multiplexor or sendmail or both with too short timeouts. Because of this either multiplexor or sendmail or both are not waiting long enough for filtering to finish. By your description, I'd say somebody sent you *very* large email, and sendmail is the one that got impatient. Mail is rejected with tempfail, old process is still spinning, remote side tries to redeliver (probaby too agressivly), new process starts, and you end up going in circles, and your load average hits the roof. The first timeout is in mimedefang-multiplexor. It controls for how long multiplexor will let the child to run before killing it. The second timeout is in sendmail. It controlls for how long sendmail will wait for MIMEDefang to do its job. You should set this two timeouts to aprox. same value (maybe setting multiplexor timeout minute or two shorter). That way, old process will be terminated by multiplexor at about same time as sendmail gives up. It really doesn't make any sense to have them set differently (the first that you hit will couase tempfail). How long should the timeout be. Depends on how large emails you are allowing (and the speed of your machine). If you limit the size of email in sendmail to say 1-10MB, around 15 minutes should suffice on reasonable fast machine. If you limit it to anything larger, values as large as 1 hour should be considered. Small hint, do not run SpamAssassin on large emails. If mail is larger than say 100kB, skip SpamAssassin checks. They will take forever to complete. Oh, BTW, multiplexor timeout is controlled in /etc/sysconfig/mimedefang (well, at least on RedHat type systems): MX_BUSY=1740 # (29 minutes, we give up before sendmail does) sendmail timeouts are defined in sendmail.mc: INPUT_MAIL_FILTER(`mimedefang', `S=unix:/var/spool/MIMEDefang/mimedefang.sock, F=T, T=S:30m;R:30m;E:30m') -- Aleksandar Milivojevic <[EMAIL PROTECTED]>Pollard Banknote Limited Systems Administrator 1499 Buffalo Place Tel: (204) 474-2323 ext 276 Winnipeg, MB R3T 1L7 ___ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] timeout before data read?
I had a similiar issue quite a while back to this. I had to increase the timers in the filter definitions line in sendmail.cf ..snip.. Xmimedefang, S=unix:/Defang/mimedefang.sock, F=T, T=S:10m;R:10m ..snip... It looks like sendmail it issueing a timeout when this timer expires and mimedefang is not finished yet.. This permits a 10 minute scan.. I have some very large attachments so your numbers my vary.. -Keith Rich West wrote: Quite suddenly, and consistently, today at around noon, I started seeing the following messages in my maillog, and the load average on the system went through the roof (load average shot up beyond 22!) shortly afterwards. Nov 17 15:02:51 cranium sm-mta[24072]: iAHK1XJR024072: Milter (mimedefang): timeout before data read Nov 17 15:02:51 cranium sm-mta[24072]: iAHK1XJR024072: Milter (mimedefang): to error state Nov 17 15:02:51 cranium sm-mta[24072]: iAHK1XJR024072: Milter: data, reject=451 4.3.2 Please try again later Nov 17 15:02:51 cranium sm-mta[24072]: iAHK1XJR024072: to=<[EMAIL PROTECTED]>, delay=00:01:01, pri=32062, stat=Please try again later Now, if I bring down both mimedefang and sendmail and bring it back up again, I can get some mail to come through, but very little before it starts spitting out these errors again. And, it seems, that mimedefang keeps being forced to spawn a new process, leaving the old one around to spin its wheels, and the new process will generate the same error, and then spawn a new process because of the failure, and so on and so on, becoming a very fast and sick cycle. :( I'm pretty much at a loss as to what could be the cause since neither mimedefang nor sendmail have been rebuilt in quite a while (I am running the latest mimedefang and the latest sendmail, of course). And no changes have been put in to place in the mimedefang-filter either. :( Right now, I am limping by only by watching the maillog, seeing a failure of a slave, and restarting mimedefang as a whole... Of course, I can't keep that up forever.. -Rich ___ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang ___ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
[Mimedefang] timeout before data read?
Quite suddenly, and consistently, today at around noon, I started seeing the following messages in my maillog, and the load average on the system went through the roof (load average shot up beyond 22!) shortly afterwards. Nov 17 15:02:51 cranium sm-mta[24072]: iAHK1XJR024072: Milter (mimedefang): timeout before data read Nov 17 15:02:51 cranium sm-mta[24072]: iAHK1XJR024072: Milter (mimedefang): to error state Nov 17 15:02:51 cranium sm-mta[24072]: iAHK1XJR024072: Milter: data, reject=451 4.3.2 Please try again later Nov 17 15:02:51 cranium sm-mta[24072]: iAHK1XJR024072: to=<[EMAIL PROTECTED]>, delay=00:01:01, pri=32062, stat=Please try again later Now, if I bring down both mimedefang and sendmail and bring it back up again, I can get some mail to come through, but very little before it starts spitting out these errors again. And, it seems, that mimedefang keeps being forced to spawn a new process, leaving the old one around to spin its wheels, and the new process will generate the same error, and then spawn a new process because of the failure, and so on and so on, becoming a very fast and sick cycle. :( I'm pretty much at a loss as to what could be the cause since neither mimedefang nor sendmail have been rebuilt in quite a while (I am running the latest mimedefang and the latest sendmail, of course). And no changes have been put in to place in the mimedefang-filter either. :( Right now, I am limping by only by watching the maillog, seeing a failure of a slave, and restarting mimedefang as a whole... Of course, I can't keep that up forever.. -Rich ___ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
[Mimedefang] Error message..
Anyone getting this error from mimedefang.. Going from 2.43 to 2.48 mimedefang.. Looks good, however occasionally I get the following error in /var/log/mail Nov 16 16:17:29 taboo mimedefang-multiplexor[5517]: Slave 0 stderr: Can't locate object method "init" via package "MIME::Decoder::QuotedPrint" at /usr/lib/perl5/site_perl/5.8.3/MIME/Decoder.pm line 179. Nov 16 16:17:29 taboo mimedefang-multiplexor[5517]: Slave 0 died prematurely -- check your filter rules Nov 16 16:17:29 taboo mimedefang[5531]: Error from multiplexor: ERR No response from slave Nov 16 16:17:29 taboo mimedefang-multiplexor[5517]: Reap: Idle slave 0 (pid 5608) exited normally with status 25 (SLAVE DIED UNEXPECTEDLY) Nov 16 16:17:29 taboo mimedefang-multiplexor[5517]: Slave 0 resource usage: req=25, scans=6, user=3.023, sys=0.462, nswap=0, majflt=0, minflt=29138, maxrss=0, bi=0, bo=0 thanks, Keith ___ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
[Mimedefang] test
I seem to have lost access to the list and sending a test message, please ignore ___ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
