From: John Capo (no email)
Date: Mon Sep 01 2003 - 11:50:57 EDT
Quoting Jim Seymour ():
> (Wietse Venema) wrote:
> >
> [snip]
> >
> > Earlier this day the greylister was broken because PERL pissed
> > over its own database.
>
> Hmmm... That happened to me twice during the two weeks I was
> experimenting with that code. I had planned to look into it, but other
> matters arose which required I abandon those experiments for the
> time-being. I didn't mention it because I had nothing firm to go on.
> "The database became corrupted" didn't seem to be the kind of bug
> report that would be welcome ;).
>
I too had problems with the DB file being corrupted. I use perl
DB stuff for a lot of tasks and I have not run into this before.
I have to use a database in production to share data across MX
servers so I stopped testing with the perl DB and coded up database
storage.
Greylisting works very well but as Wietse has pointed out, selective
use and/or whitelisting is needed. I have greylisting on a bunch
of very productive spamtrap addresses with no other restrictions
and 85% of the machines try once and never come back. I greylist
if the helo has no dot, if the client has no rDNS, if rDNS looks
like cable, dsl, dhcp, ppp, etc. or in 200/8, and envelope senders
in the monkeys.com free email list.
John Capo
|
|
|