Milter-greylist

Andreas Unterkircher wrote:
> milter-greylist? Isn't it MIMEDefang which died according your logs?
> 
> Am Freitag, den 29.07.2005, 14:16 +0000 schrieb cruiskeenconsulting:
> 
>>We just put milter-greylist into production here.  It ran fine in
>>testing, but overnight it died
>>
>>Jul 28 21:35:18 eric.servers.uwrf.edu sm-mta[19644]: j6T2ZFng019644:
>>milter_read(greylist): cmd read returned 0, expecting 5
>>Jul 28 21:35:18 eric.servers.uwrf.edu sm-mta[19644]: j6T2ZFng019644:
>>Milter (greylist): to error state
>>Jul 28 21:35:18 eric.servers.uwrf.edu mimedefang[2267]: envfrom:
>>Unable to obtain private data from milter context
>>Jul 28 21:35:18 eric.servers.uwrf.edu sm-mta[19644]: j6T2ZFng019644:
>>Milter: from=<rdaily@...>, reject=451 4.3.2 Please try
>>again later
>>Jul 28 21:35:19 eric.servers.uwrf.edu sm-mta[19644]: j6T2ZFng019644:
>>from=<rdaily@...>, size=0, class=0, nrcpts=0, proto=SMTP,
>>daemon=MTA, relay=pacific54.youroptinmail.com [130.94.133.60]
>>Jul 28 21:35:19 eric.servers.uwrf.edu sm-mta[19644]: j6T2ZFnh019644:
>>ldap dustin.i.williams@... => w1001702@...
>>Jul 28 21:35:29 eric.servers.uwrf.edu sm-mta[19647]: j6T2ZTkZ019647:
>>Milter (greylist): error connecting to filter: Connection refused by
>>/var/spool/MIMEDefang/milter-greylist.sock
>>Jul 28 21:35:29 eric.servers.uwrf.edu sm-mta[19647]: j6T2ZTkZ019647:
>>Milter (greylist): to error state
>>

After looking at this somewhat and cranking up the logging, it APPEARS
that what happens is that I have marked

youroptinmail.com DISCARD

in the access database.  Whenever we get an email from risquemail.com,
which is served through a youroptinmail.com mail server I get a series
of log messages that look more or less like this:
Jul 31 05:32:23 eric.servers.uwrf.edu sm-mta[24207]:
ruleset=check_relay, arg1=pacific26.youroptinmail.com,
arg2=130.94.133.249, relay=pacific26.youroptinmail.com [130.94.133.249],
discard
Jul 31 05:32:23 eric.servers.uwrf.edu sm-mta[24207]: j6VAWNkh024207:
Milter (greylist): init success to negotiate
Jul 31 05:32:23 eric.servers.uwrf.edu sm-mta[24207]: j6VAWNkh024207:
Milter (mimedefang): init success to negotiate
Jul 31 05:32:26 eric.servers.uwrf.edu sm-mta[24207]: j6VAWNkh024207:
from=<rdaily@...>, size=15311, class=0, nrcpts=1,
msgid=<406801274311882274christopher.j.koren@...>,
proto=SMTP, daemon=MTA, relay=pacific26.youroptinmail.com [130.94.133.249]
Jul 31 05:32:26 eric.servers.uwrf.edu sm-mta[24207]: j6VAWNkh024207:
Milter accept: message
Jul 31 05:32:26 eric.servers.uwrf.edu sm-mta[24207]: j6VAWNkh024207:
discarded
Jul 31 05:32:26 eric.servers.uwrf.edu sm-mta[24207]: j6VAWNki024207:
milter_read(greylist): cmd read returned 0, expecting 5
Jul 31 05:32:26 eric.servers.uwrf.edu sm-mta[24207]: j6VAWNki024207:
Milter (greylist): to error state
Jul 31 05:32:26 eric.servers.uwrf.edu sm-mta[24207]: j6VAWNki024207:
Milter: from=<rdaily@...>, reject=451 4.3.2 Please try again
later
Jul 31 05:32:28 eric.servers.uwrf.edu sm-mta[24211]: j6VAWSM7024211:
Milter (greylist): open /var/spool/MIMEDefang/milter-greylist.sock
failed: Connection refused by /var/spool/MIMEDefang/milter-greylist.sock
Jul 31 05:32:28 eric.servers.uwrf.edu sm-mta[24211]: j6VAWSM7024211:
Milter (greylist): error connecting to filter: Connection refused by
/var/spool/MIMEDefang/milter-greylist.sock


It appears that it is the access entry that is making milter-greylist fail.

I'm finding that we really can't use milter-greylist in production
because of this - it crashes some times several times in an hour.

Is it just impossible to blacklist anything in access and use
milter-greylist as well?

Also - I have tried a few times to set up milter-greylist so that I can
whitelist in the Access database as well-  but I cannot get that to
work.  The docs really don't explain very well how to do this.  And if
you really follow the instructions as written, it will break your other
milters because if you really set the macro entries explicitly to just
the macros that milter -greylist needs, then it removes the default
macros that your other milters needed.  Okay, so I figured that out, but
I still cannot tell what I am supposed to put into an access entry to
actually be able to whitelist something for milter-greylist.

I eventually took the macross for access out of the m4 sendmail config,
since I was afraid that was what was making milter-greylist crash, but
that seems not to help.

This is the second greylisting milter I've tried that doesn't seem
stable in production - milter-gris was much worse, crashing any time
there was any particular load on the server. Greylisting really seems to
make a huge difference in our spam levels, but I can't seem to find a
stable implementation to use.



>>
>>
>>
>> 
>>Yahoo! Groups Links
>>
>>
>>
>> 
>>
>>
>>
>>
> 
> 
> 
> 
> 
>  
> Yahoo! Groups Links
> 
> 
> 
>  
> 
>