Yahoo Groups archive

Milter-greylist

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

Message

Re: [milter-greylist] sendmail Milter (greylist): to error state

2010-12-17 by Michael Mansour

Hi Emmanuel,

You're spot on, I modified sendmail.cf to add:

Xgreylist, S=local:/var/milter-greylist/milter-greylist.sock, T=S:1m;R:1m

The Timeouts at the end were empty.

This seems to have occurred on the sendmail version upgrade performed recently.

Adding the greylist feature into sendmail.mc, running make, would produce the
above in sendmail.cf automatically with other milters.

With this newer sendmail, it doesn't do that but leaves it as:

Xgreylist, S=local:/var/milter-greylist/milter-greylist.sock,

which fails to run due to the last ",".

With the last comma removed, it runs but defaults to timeouts of 10 seconds.
Adding the timeout values fixes it, but there's an underlying problem still to
work out with the sendmail make.

I've checked the file:

/usr/share/sendmail-cf/feature/milter-greylist.m4

and it looks OK to me, with the confGREYLIST_OPTIONS meant to be populating
the sendmail.cf

Basically it doesn't do it while the earlier sendmail I'm sure did. Strange.

Thanks again.

Michael.

> Michael Mansour <mic@...> wrote:
> 
> > I've recently noticed I get a lot of these errors on mail servers:
> > Dec 17 17:00:14 server sendmail[29303]: oBH6011k029303: Milter (greylist):
> > timeout before data read
> > Dec 17 17:00:14 server sendmail[29303]: oBH6011k029303: Milter (greylist): to
> > error state
> 
> That happens if the milter dies, or if sendmail decides the request 
> to the milter has timed out. The later can easily happen when milter-
> greylist perfoms DNS queries.
> 
> Upgrade the timeout in sendmail.cf to fix the problem.
> 
> -- 
> Emmanuel Dreyfus
> http://hcpnet.free.fr/pubz
> manu@...
> 
> ------------------------------------
> 
> Yahoo! Groups Links
> 
> 
>

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.