Milter-greylist

Emmanuel Dreyfus wrote:


> On Mon, Oct 11, 2004 at 03:21:03PM +0200, Klas Heggemann wrote:
>> we received approx 47000 letter a day. Now this is down to 18000 a
>> day...
>
> After you starte greylisting, you usually still get a lot of spam
> sent from regular mail servers. Removal requests and/or blacklisting
> cures it.

I think a lot of this is legitimate letters (to our approx 15000 users 
...)
I myself receive very little spam after the greylisting was implemented.
People here wish there was a Noble Prize for spam fighting ....

>
>> The major thing is that when a autowhitelisted entry is renewed, this
>> information does notseem to  propagate to the other mx-host which will
>> loose this entry when it times out.
>
> True. I never thought about it, but we can call it a bug.

Tnx.


>
>> A config file that can be  shared between the mx-hosts, i e you
>> would be permitted to have a 'peer'-line that includes
>> the machine on which the milter is running. This would be detected
>> at startup and no sync information should be sent that way.
>
> Yes, that makes sense. I use a workaround for this problem:
> On the machines I run milter-greylist on, I build the config file
> from a common part and a local part. The local part contains the
> peer statements.


Yeah we do approx the same here (just commenting the relevent lines).


>>
>> The database should be dumped when the milter is stopped/killed.
>
> I recall implementing that.

Yes, I can se this now in the code. It does not seem to work here (on 
Solaris 9)


>
> -- 
> Emmanuel Dreyfus
> manu@...
>


Really nice work.  Both the users  here + administrators are realy 
happy...


/klas