Re: Which milter t/o generates 'timeout before data read' error? was: Re: [Mimedefang] milter timing out.
Quoting Jon R. Kibler [EMAIL PROTECTED]: Jon R. Kibler wrote: Jan 31 20:51:03 norm sm-mta[27815]: i112jv3O027815: Milter (mimedefang): timeout before data read Jan 31 20:51:03 norm sm-mta[27815]: i112jv3O027815: Milter (mimedefang): to error state I asked this question earlier, but I think it got lost in other parts of the discussion and never got answered: Regarding the above error messages... which milter timeout value (C,S,R, or E) effects the 'timeout before data read' error? That is, which ones should be increased to eliminate this error? Jon, I don't recall seeing an answer to this posted, so here goes a try. The timeout before data read appears to be controlled by the R setting; in sendmail/milter.c that error appears in the function milter_read(). The fourth argument to that function is to (timeout). Everywhere that milter_read is called in milter.c the fourth argument is m-mf_timeout[SMFTO_READ] which is parsed from the R option (line 1360 of milter.c, sendmail 8.12.10). However, remember that you might also be bumping into the E setting, which is the overall timeout. Hopefully you have already solved your problem, but just in case you were still waiting, I hope this helps. I've had good luck with the settings below for another email scanner (Sopho's PureMessage) - even messages that are too large for email (IMO) make it through. Cheers. -- Andrew C:5m == timeout for connecting to filter is 5 minutes E:8m == overall timeout from start to finish is 8 minutes R:4m == timeout for reading reply from filter is 4 minutes S:2m == Timeout for sending data from MTA to filter is 2 minutes ___ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Which milter t/o generates 'timeout before data read' error? was: Re: [Mimedefang] milter timing out.
Jon R. Kibler wrote: Jan 31 20:51:03 norm sm-mta[27815]: i112jv3O027815: Milter (mimedefang): timeout before data read Jan 31 20:51:03 norm sm-mta[27815]: i112jv3O027815: Milter (mimedefang): to error state I asked this question earlier, but I think it got lost in other parts of the discussion and never got answered: Regarding the above error messages... which milter timeout value (C,S,R, or E) effects the 'timeout before data read' error? That is, which ones should be increased to eliminate this error? -- Jon R. Kibler Chief Technical Officer A.S.E.T., Inc. Charleston, SC USA (843) 849-8214 == Filtered by: TRUSTEM.COM's Email Filtering Service http://www.trustem.com/ No Spam. No Viruses. Just Good Clean Email. ___ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] milter timing out.
On Thu, 5 Feb 2004, Lucas Albers wrote: Justin said: On Wed, 4 Feb 2004, Edmund wrote: I'm having the same problem here. A co-worker was trying to send a big file to another co-worker and the mail server kept on throwing a Error 451. Unfortunately, I don't know how big the file is. then returns a 451. I'm going to inquire with the list about this under separate cover tomorrow, after I test a few more things. I've had to disable MD in the mean time. It's very odd. I run sendmail on a 7.3 box, mimedefang 2.33, sendmail 8.12.8, and it has never had timeout issues from large file size. I handle 15 meg files routinelly. I turned off spam checking for authenticated and internally sent mail, as some clients were suffering timeouts. you can just swatch your log, and only restart mimedefang/sendmail when it is suffering a timeout. My guess is something in your filter is taking a long time to process the email. Thanks for the reply. These messages weren't of any abnormal length. In fact the majority of them weren't as long as this message is. MD did regularly temp fail mail to my usenet alias. The only mail I ever received there was infected mail. It temp failed just about anything though regardless of size. I still have that box and the installation intact. It doesn't however handle mail anymore and it wouldn't be easy to set it up to handle mail at the present time either. Perhaps after I move I can revive that machine and try to figure out what went wrong. My current server is what I'm focusing on at the moment though. Thanks Justin ___ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] milter timing out.
Jon R. Kibler wrote: Up your sendmail logging option (10 will log inbound, 12 will log both inbound and outbound) and you will get a log entry for every connection that occurs. Look at how many connections you have in a given period of time, and that will give you your rate. You don't want to run with a high logging option value for a long period of time, or your log will grow huge and VERY fast! Oh yeah, I left out an important detail... be sure you have syslog.conf configured to be able to log at the info or debug levels. Logging at levels 10 and 12 log as 'mail.info'. -- Jon R. Kibler Chief Technical Officer A.S.E.T., Inc. Charleston, SC USA (843) 849-8214 == Filtered by: TRUSTEM.COM's Email Filtering Service http://www.trustem.com/ No Spam. No Viruses. Just Good Clean Email. ___ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] milter timing out.
On Wed, 4 Feb 2004, Edmund wrote: I'm having the same problem here. A co-worker was trying to send a big file to another co-worker and the mail server kept on throwing a Error 451. Unfortunately, I don't know how big the file is. I read on this thread that by resetting MD it should return to normal. I did that, and it seems to have worked. But I'm certain that it'd do that again sooner or later. The problem I used to have on my RH 7.3 box was fixed in the same way. I had a cronjob restart sendmail and MD every 5 minutes just to keep things mostly working. I never did find the cause of that problem. My current problem is with MD going completely brain dead after receiving a message. I mean it accepts the message (and any new messages) for processing but it will do nothing. It simply waits for sendmail to time it out and sendmail then returns a 451. I'm going to inquire with the list about this under separate cover tomorrow, after I test a few more things. I've had to disable MD in the mean time. It's very odd. Justin ___ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] milter timing out.
On Mon, 2 Feb 2004, Jon R. Kibler wrote: a) Set the ConnectionRateThrottle option to a low value (4) so that sendmail will not accept more than 4 connections per second. Connections are not refused, sendmail just delays responding to them. (With MyDoom, we have seen connection rate bursts 100 new connections/sec/MTA.) Dumb question, but how are you determining your ConnectionRate? I'm hesitant to throttle it before i know what a good number for our system is. thanks. ray -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Ray DeJean http://www.r-a-y.org Systems EngineerSoutheastern Louisiana University IBM Certified Specialist AIX Administration, AIX Support =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ___ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] milter timing out.
-ray said: Dumb question, but how are you determining your ConnectionRate? I'm hesitant to throttle it before i know what a good number for our system is. thanks. Depends on your mail load. Pick the same connection throttle as someone who gets the same message volume. For DOS support just set it to 10, imo. Assuming you don't have really high load. Luke Computer Science System Administrator ___ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] milter timing out.
Did more troubleshooting today. I think this is a multiplexor problem. I started logging the # of sendmail and MD processes. At some point it appears the multiplexor decides to stop spawning new slaves, and sendmail processes start backing up. Log created with: echo `date`: Sendmail `ps aux | grep sendmail: -c` | mimedefang `ps -efl | grep fang | grep pid -c` /log2/proclog sleep 5 Tue Feb 3 17:21:09 CST 2004: Sendmail 45 | mimedefang 24 Tue Feb 3 17:21:14 CST 2004: Sendmail 43 | mimedefang 26 Tue Feb 3 17:21:20 CST 2004: Sendmail 49 | mimedefang 31 Tue Feb 3 17:21:25 CST 2004: Sendmail 49 | mimedefang 31 Tue Feb 3 17:21:30 CST 2004: Sendmail 46 | mimedefang 28 Tue Feb 3 17:21:35 CST 2004: Sendmail 54 | mimedefang 36 Tue Feb 3 17:21:41 CST 2004: Sendmail 53 | mimedefang 36 Tue Feb 3 17:21:46 CST 2004: Sendmail 45 | mimedefang 27 Tue Feb 3 17:21:51 CST 2004: Sendmail 43 | mimedefang 1 Tue Feb 3 17:21:56 CST 2004: Sendmail 44 | mimedefang 1 Tue Feb 3 17:22:01 CST 2004: Sendmail 44 | mimedefang 1 Tue Feb 3 17:22:07 CST 2004: Sendmail 45 | mimedefang 1 Tue Feb 3 17:22:12 CST 2004: Sendmail 49 | mimedefang 1 Tue Feb 3 17:22:17 CST 2004: Sendmail 51 | mimedefang 1 Tue Feb 3 17:22:22 CST 2004: Sendmail 57 | mimedefang 1 Tue Feb 3 17:22:27 CST 2004: Sendmail 62 | mimedefang 1 Tue Feb 3 17:22:33 CST 2004: Sendmail 68 | mimedefang 1 Tue Feb 3 17:22:38 CST 2004: Sendmail 74 | mimedefang 1 Tue Feb 3 17:22:43 CST 2004: Sendmail 78 | mimedefang 1 Tue Feb 3 17:22:48 CST 2004: Sendmail 88 | mimedefang 1 Tue Feb 3 17:22:53 CST 2004: Sendmail 97 | mimedefang 1 Tue Feb 3 17:22:59 CST 2004: Sendmail 102 | mimedefang 1 Tue Feb 3 17:23:04 CST 2004: Sendmail 111 | mimedefang 1 Tue Feb 3 17:23:09 CST 2004: Sendmail 115 | mimedefang 1 Tue Feb 3 17:23:14 CST 2004: Sendmail 120 | mimedefang 1 Tue Feb 3 17:23:19 CST 2004: Sendmail 131 | mimedefang 1 Tue Feb 3 17:23:32 CST 2004: Sendmail 145 | mimedefang 1 Tue Feb 3 17:23:45 CST 2004: Sendmail 172 | mimedefang 1 Tue Feb 3 17:23:55 CST 2004: Sendmail 184 | mimedefang 1 Tue Feb 3 17:24:00 CST 2004: Sendmail 191 | mimedefang 1 Tue Feb 3 17:24:06 CST 2004: Sendmail 197 | mimedefang 1 Tue Feb 3 17:24:11 CST 2004: Sendmail 204 | mimedefang 1 Tue Feb 3 17:24:16 CST 2004: Sendmail 209 | mimedefang 1 Tue Feb 3 17:24:21 CST 2004: Sendmail 213 | mimedefang 1 Tue Feb 3 17:24:27 CST 2004: Sendmail 220 | mimedefang 1 Tue Feb 3 17:24:32 CST 2004: Sendmail 225 | mimedefang 1 Tue Feb 3 17:24:37 CST 2004: Sendmail 228 | mimedefang 1 Tue Feb 3 17:24:42 CST 2004: Sendmail 237 | mimedefang 1 Tue Feb 3 17:24:48 CST 2004: Sendmail 239 | mimedefang 1 Tue Feb 3 17:24:53 CST 2004: Sendmail 243 | mimedefang 1 Tue Feb 3 17:24:58 CST 2004: Sendmail 253 | mimedefang 1 Tue Feb 3 17:25:04 CST 2004: Sendmail 261 | mimedefang 1 Tue Feb 3 17:25:09 CST 2004: Sendmail 264 | mimedefang 1 Tue Feb 3 17:25:14 CST 2004: Sendmail 266 | mimedefang 1 Tue Feb 3 17:25:20 CST 2004: Sendmail 266 | mimedefang 1 Tue Feb 3 17:25:25 CST 2004: Sendmail 266 | mimedefang 1 Tue Feb 3 17:25:30 CST 2004: Sendmail 266 | mimedefang 1 Tue Feb 3 17:25:35 CST 2004: Sendmail 266 | mimedefang 1 Tue Feb 3 17:25:41 CST 2004: Sendmail 266 | mimedefang 1 Tue Feb 3 17:25:46 CST 2004: Sendmail 266 | mimedefang 1 Tue Feb 3 17:25:57 CST 2004: Sendmail 266 | mimedefang 1 Tue Feb 3 17:26:03 CST 2004: Sendmail 265 | mimedefang 1 Tue Feb 3 17:26:09 CST 2004: Sendmail 265 | mimedefang 1 Tue Feb 3 17:26:14 CST 2004: Sendmail 266 | mimedefang 1 Tue Feb 3 17:26:19 CST 2004: Sendmail 266 | mimedefang 1 Tue Feb 3 17:26:29 CST 2004: Sendmail 266 | mimedefang 1 Tue Feb 3 17:26:44 CST 2004: Sendmail 264 | mimedefang 1 Tue Feb 3 17:26:58 CST 2004: Sendmail 260 | mimedefang 1 Tue Feb 3 17:27:03 CST 2004: Sendmail 264 | mimedefang 1 Tue Feb 3 17:27:19 CST 2004: Sendmail 257 | mimedefang 1 Tue Feb 3 17:27:26 CST 2004: Sendmail 261 | mimedefang 1 Tue Feb 3 17:27:42 CST 2004: Sendmail 250 | mimedefang 1 Tue Feb 3 17:27:50 CST 2004: Sendmail 251 | mimedefang 1 Tue Feb 3 17:28:02 CST 2004: Sendmail 256 | mimedefang 1 Tue Feb 3 17:28:14 CST 2004: Sendmail 261 | mimedefang 1 Tue Feb 3 17:28:29 CST 2004: Sendmail 247 | mimedefang 1 Tue Feb 3 17:28:35 CST 2004: Sendmail 248 | mimedefang 1 Tue Feb 3 17:28:45 CST 2004: Sendmail 246 | mimedefang 1 Tue Feb 3 17:28:55 CST 2004: Sendmail 244 | mimedefang 1 Tue Feb 3 17:29:00 CST 2004: Sendmail 255 | mimedefang 1 Tue Feb 3 17:29:15 CST 2004: Sendmail 262 | mimedefang 1 Tue Feb 3 17:29:31 CST 2004: Sendmail 265 | mimedefang 1 Tue Feb 3 17:29:49 CST 2004: Sendmail 253 | mimedefang 1 Tue Feb 3 17:30:06 CST 2004: Sendmail 266 | mimedefang 1 Tue Feb 3 17:30:11 CST 2004: Sendmail 261 | mimedefang 1 Tue Feb 3 17:30:17 CST 2004: Sendmail 261 | mimedefang 1 Tue Feb 3 17:30:22 CST 2004: Sendmail 261 | mimedefang 1 Tue Feb 3 17:30:27 CST 2004: Sendmail 266 | mimedefang 1 Tue Feb 3 17:30:33 CST 2004: Sendmail 51 | mimedefang 0 Tue Feb 3 17:30:38 CST 2004:
Re: [Mimedefang] milter timing out.
On Tue, 3 Feb 2004, -ray wrote: appears the multiplexor decides to stop spawning new slaves, and sendmail processes start backing up. When that happens, what does: md-mx-ctrl status say? Regards, David. ___ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] milter timing out.
Having a weird milter timeout on my server as well. Mail flows fine then for no apparent reason, the milters start timing out. Sendmail reaches MaxDaemon (currently 250) and starts rejecting connections. Even after that, mimedefang never seems to recover. Restarting sendmail and mimedefang fixes it. This has been happening once every day or two. Right now i'm looking for ideas on where to troubleshoot next. I tried upping MaxDaemon to 500 and 1000 but the problem still occurs. I've increased milter timeouts to F=T, T=S:5m;R:5m;E:10m. Trying to determine if this is a sendmail or a MD (or spamassassing or clamav) problem. Is sendmail reaching MaxDaemon because the milters start backing up, or vice versa? I tried turning on mimedefang debugging, but the load was too great and the system couldn't keep up. Any other ideas? ray Jan 31 20:51:03 norm sm-mta[27815]: i112jv3O027815: Milter (mimedefang): timeout before data read Jan 31 20:51:03 norm sm-mta[27815]: i112jv3O027815: Milter (mimedefang): to error state Jan 31 20:51:03 norm sm-mta[27815]: i112jv3O027815: Milter: data, reject=451 4.7.1 Please try again later Jan 31 20:51:03 norm sm-mta[27815]: i112jv3O027815: [EMAIL PROTECTED], delay=00:05:04, pri=30313, stat=Please try again later Jan 31 20:51:04 norm sm-mta[28251]: i112k43N028251: Milter (mimedefang): timeout before data read Jan 31 20:51:04 norm sm-mta[28251]: i112k43N028251: Milter (mimedefang): to error state Jan 31 20:51:04 norm sm-mta[28251]: i112k43N028251: Milter (mimedefang): init failed to open Jan 31 20:51:04 norm sm-mta[28251]: i112k43N028251: Milter (mimedefang): to error state Jan 31 20:51:04 norm sm-mta[28251]: i112k43N028251: Milter: initialization failed, temp failing commands Jan 31 20:51:04 norm sm-mta[28251]: i112k43N028251: 12-215-185-211.client.mchsi.com [12.215.185.211] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA Jan 31 20:51:05 norm sm-mta[3100]: rejecting connections on daemon MTA: 250 children, max 250 Jan 31 20:51:05 norm sendmail[12687]: i0VBUTU7019879: to=[EMAIL PROTECTED], delay=15:20:36, xdelay=00:00:22, mailer=esmtp, pri=3725131, relay=mail.polarwax.com. [211.167.73.20], dsn=4.0.0, stat=Deferred: Connection refused by mail.polarwax.com. Jan 31 20:51:05 norm sm-mta[28253]: i112k53N028253: Milter (mimedefang): timeout before data read Jan 31 20:51:05 norm sm-mta[28253]: i112k53N028253: Milter (mimedefang): to error state Jan 31 20:51:05 norm sm-mta[28253]: i112k53N028253: Milter (mimedefang): init failed to open Jan 31 20:51:05 norm sm-mta[28253]: i112k53N028253: Milter (mimedefang): to error state Jan 31 20:51:05 norm sm-mta[28253]: i112k53N028253: Milter: initialization failed, temp failing commands Jan 31 20:51:05 norm sm-mta[28253]: i112k53N028253: mta13.classmates.com [65.243.133.33] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA Jan 31 20:51:06 norm sm-mta[28254]: i112k63N028254: Milter (mimedefang): timeout before data read Jan 31 20:51:06 norm sm-mta[28254]: i112k63N028254: Milter (mimedefang): to error state Jan 31 20:51:06 norm sm-mta[28254]: i112k63N028254: Milter (mimedefang): init failed to open Jan 31 20:51:06 norm sm-mta[28254]: i112k63N028254: Milter (mimedefang): to error state Jan 31 20:51:06 norm sm-mta[28254]: i112k63N028254: Milter: initialization failed, temp failing commands Jan 31 20:51:06 norm sm-mta[28254]: i112k63N028254: 08.opn08.com [69.6.27.127] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA ___ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
