At the end of this message are all the entries from 2 seconds of my maillog from a crash today, starting with the last greylist action and ending with the error message. Prior to the crash, the connecting site ( tried to connect 18 times over a period of 60 seconds. The last 9 attempts were made three at a time during 1 second intervals. The last triple occurred 2 seconds before the failure. The connected site was h66-201-246-167.gtcust.grouptelecom.net [66.201.246.167]. Can multiple dropped connections cause a problem with milter-greylist? The last triple connection attempt look like this: Aug 21 15:22:31 host sm-acceptingconnections[21836]: k7LKMOSD021836: lost input channel f rom h66-201-246-167.gtcust.grouptelecom.net [66.201.246.167] to MTA after data Aug 21 15:22:31 host sm-acceptingconnections[21836]: k7LKMOvX021836: lost input channel f rom h66-201-246-167.gtcust.grouptelecom.net [66.201.246.167] to MTA after data Aug 21 15:22:31 host sm-acceptingconnections[21836]: k7LKMHbB021836: lost input channel f rom h66-201-246-167.gtcust.grouptelecom.net [66.201.246.167] to MTA after data Here are the 2 seconds of maillog: Aug 21 15:22:32 host milter-greylist: k7LKMOLk021836: addr 66.201.246.167 from <Marshbuzzing@roteiroturismo .com.br> to <webmaster@...> delayed for 00:06:00 Aug 21 15:22:32 host sm-acceptingconnections[21836]: k7LKMOLk021836: Milter: to=<webmaster@...>, rej ect=451 4.7.1 Greylisting in action, please come back in 00:06:00 Aug 21 15:22:32 host milter-greylist: k7LKMVTt021836: skipping greylist because this is the default action, (from=<>, rcpt=<ucm@...>, addr=153.91.3.98) Aug 21 15:22:32 host ipop3d[21826]: Logout user=dre@... host=63-231-157-157.mpls.qwes t.net [63.231.157.157] nmsgs=0 ndele=0 Aug 21 15:22:32 host sm-acceptingconnections[21836]: k7LKMVTt021836: from=<>, size=939, class=0, nrcpts=1, msgid=<s4e9cf30.005@...>, proto=ESMTP, daemon=MTA, relay=cmsu1gate.cmsu.edu [153.91.3.98] Aug 21 15:22:32 host sm-acceptingconnections[21836]: k7LKMVTt021836: to=<ucm@...>, delay=00:00:00, mailer=virthostmail, pri=30939, stat=queued Aug 21 15:22:33 host ipop3d[21812]: Login user=uuce@... host=adsl-75-2-75-139.dsl.chcgil.sbcglobal.net [75.2.75.139] nmsgs=0/0 Aug 21 15:22:33 host ipop3d[21812]: Logout user=uuce@... host=adsl-75-2-75-139.dsl.chcgil.sbcglobal.ne t [75.2.75.139] nmsgs=0 ndele=0 Aug 21 15:22:33 host sm-acceptingconnections[21836]: k7LKMXud021836: Milter (greylist): read returned -1: C onnection reset by h66-201-246-167.gtcust.grouptelecom.net Aug 21 15:22:33 host sm-acceptingconnections[21836]: k7LKMXud021836: Milter (greylist): to error state Aug 21 15:22:33 host sm-acceptingconnections[21836]: k7LKMXud021836: Milter (greylist): init failed to open Aug 21 15:22:33 host sm-acceptingconnections[21836]: k7LKMXud021836: Milter (greylist): to error state Aug 21 15:22:33 host sm-acceptingconnections[21836]: k7LKMX6x021836: Milter (greylist): error connecting to filter: Connection refused by /var/milter-greylist/milter-greylist.sock Aug 21 15:22:33 host sm-acceptingconnections[21836]: k7LKMX6x021836: Milter (greylist): to error state Aug 21 15:22:33 host sm-acceptingconnections[21836]: k7LKMX6x021836: akk142.internetdsl.tpnet.pl [83.17.14. 142] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA Aug 21 15:22:33 host sm-acceptingconnections[21836]: k7LKMOLk021836: Milter (greylist): write(Q) returned - 1, expected 5: Broken pipe Aug 21 15:22:33 host sm-acceptingconnections[21836]: k7LKMOLk021836: Milter (greylist): to error state Aug 21 15:22:33 host sm-acceptingconnections[21836]: k7LKMOLk021836: lost input channel from h66-201-246-16 7.gtcust.grouptelecom.net [66.201.246.167] to MTA after data _____ From: milter-greylist@yahoogroups.com [mailto:milter-greylist@yahoogroups.com] On Behalf Of Fabien Tassin Sent: Saturday, August 19, 2006 12:23 PM To: milter-greylist@yahoogroups.com Subject: Re: [milter-greylist] milter-greylist 2.02 crashes According to manu@netbsd. <mailto:manu%40netbsd.org> org: > > > What do these log entired indicate about my problems with milter-greylist. > > I am running Sendmail 8.13 or Fedora 2. > > > > Aug 17 10:14:02 host sm-acceptingconnections[15057]: k7HFE2lN015057: Milter > > (greylist): read returned -1: Connection reset by > > ppp-124.120.137.59.revip2.asianet.co.th > > A usual issue is that it ran out of memory. You may have to increase > allocatable memory with ulimit before starting up milter-greylist. hmm, all *alloc()/*dup() calls seem to be assigned with a syslog in case of failure. Should be visible in the error logs then. What about running through valgrind or something similar. Whatever the problem is, it will be loggued for sure, maybe even faster than in real life as those tools usually allocate more memory than requested in order to check for over&underflows. /Fabien -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.3/423 - Release Date: 08/18/06
Message
RE: [milter-greylist] milter-greylist 2.02 crashes
2006-08-22 by Jim Hermann - UUN Hostmaster
Attachments
- No local attachments were found for this message.