Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Message

termination after rcpt flood

2008-03-15 by netbrain2003

I have a problem with a terminating daemon after a flood via SMTP. I'm
afraid I can not give much debug output but just the mail server log
of this happening (see below). If I can turn on some switches to give
more output please let me know. The system is a debian one running
sendmail 8.14.2-3. After restart the greylist service it is working
again. This happens more often these days, I'm afraid spammer know
this already?

Thank you
Thomas

PS: This software rocks like hell. Please keep going.

Package: milter-greylist
Priority: extra
Section: mail
Installed-Size: 296
Maintainer: Cord Beermann <cord@...>
Architecture: i386
Version: 3.0-3
Depends: libc6 (>= 2.5-5), libmilter1, libspf2-2 (>= 1.2.5), adduser
(>= 3.11)
Recommends: sendmail
Filename: pool/main/m/milter-greylist/milter-greylist_3.0-3_i386.deb
Size: 85748
MD5sum: e5d18e06984a3a1dc263dad6061db5bb


Mar 14 12:39:18 delphin sm-mta[12124]: m2EBdG5R012124:
dyn-89.136.83.248.upcnet.ro [89.136.83.248] (may be forged): Possible
SMTP RCPT flood, thro
ttling.
Mar 14 12:39:19 delphin sm-mta[12115]: m2EBdAWN012115:
milter_sys_read(greylist): cmd read returned 0, expecting 5
Mar 14 12:39:19 delphin sm-mta[12115]: m2EBdAWN012115: Milter
(greylist): to error state
Mar 14 12:39:19 delphin sm-mta[12124]: m2EBdG5R012124: Milter
(greylist): write(D) returned -1, expected 6: Broken pipe
Mar 14 12:39:19 delphin sm-mta[12124]: m2EBdG5R012124: Milter
(greylist): to error state
Mar 14 12:39:19 delphin sm-mta[12120]: m2EBdIpm012120: Milter
(greylist): write(D) returned -1, expected 6: Broken pipe
Mar 14 12:39:19 delphin sm-mta[12120]: m2EBdIpm012120: Milter
(greylist): to error state
Mar 14 12:39:19 delphin sm-mta[12123]: m2EBdJOB012123: Milter
(greylist): error connecting to filter: Connection refused by
/var/run/milter-greyli
st/milter-greylist.sock

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.