[Greylist-users] Greylisting status

[Evan Harris]

> > > On the down side, I noticed today that I'm seeing delays on mail injected
> > > locally, even though I have the whitelist configured.  This seems to be
> > > preventing the occasional mail from being delivered.
> >
> > I'm not sure what you you mean.  Can you get a little more specific about
> > this problem?
>
> Jul  9 14:13:08 agora sendmail[57343]: STARTTLS=server, relay=2076 at localhost [127.0.0.1], version=TLSv1/SSLv3, verify=NOT, cipher=DHE-RSA-AES256-SHA, bits=256/256
> Jul  9 14:13:08 agora sendmail[57343]: h69LD82E057343: Milter: to=<xxxx at agora.rdrop.com>, reject=451 4.7.1 Please try again later
> Jul  9 14:13:08 agora sendmail[57343]: h69LD82E057343: Milter: to=<xxxx at agora.rdrop.com>, reject=451 4.7.1 Please try again later
> Jul  9 14:13:08 agora sendmail[57343]: h69LD82E057343: from=<xxxx at agora.rdrop.com>, size=1012, class=0, nrcpts=0, proto=ESMTP, daemon=MTA, relay=2076 at localhost [127.0.0.1]

Hmmm, if you're using my stock milter, there is no "(TEMPFAIL)" suffix in
those loglines, which suggests that either you have another milter
configured that is returning a tempfail, or there's some problem with the
milter, like it can't connect to the db.

If you are running another milter, check that.  If not, what do you get if
you run the milter in foreground with $verbose = 1?

> >    define(`confMAX_DAEMON_CHILDREN', `40')dnl
>
> I've been wishing for that for a long time, but it's also been a long
> time since I looked for something like that.  Thanks!
>
> But it doesn't explain why the number of database threads never seems to
> go down.  I suspect it's because I'm unwisely using mysql 4.1.0-alpha
> though.

With the milter, I have it set never to kill off children, since
Sendmail::Milter seems to start throwing errors if you try to have it
recycle children.  So each copy of the milter that is running will consume a
db connection, and those connections will never go away until the whole
milter is stopped.

Evan