Hi, all,
I just converted my greylisting implementation to a SQLite backend. I
created a web page with the code and basic install instructions:
http://www.bl.org/~jpk/md-greylist/
My code is a derivation of work that was done by others in this mailing
list... the most significant contribution h
ight, and if it looks good in the morning, I'll post the
code changes.
Thanks for finding this! It's a real bummer... there's even a patch on
CPAN to fix the wait time issue in the DBD module, but it's not yet in the
distribution.
Best Regards,
John Kirkland
On Thu, 24 Jun 2
The mysql version of the greylisting backend has been running fine
overnight, so here is the new code:
http://www.bl.org/~jpk/md-greylist/
Regards,
John
___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
On Tue, 10 Aug 2004, Rich West wrote:
Just curious, but what, exactly, does the --trim option do? The
documentation states that it cuts out old data from the SummaryDB, but
doesn't that defeat the purpose of graphdefang when looking for
longer-term trends and such?
You should use the "--trim" opti
> To my inexperienced eye it seems extremely elegant/sensible to
> separate this functionality out of MimeDefang - gives MimeDefang less
> to do, simplifies filters, etc. Does anyone know better?
The very first greylisting implementation that I used was
milter-greylist, but I found that some virus
> I have the same graphdefang-config and index.pl files on 2 different
> machines. One puts it in the order that they are in the
graphdefang-config
> and the other doesn't.
> HELP
>
> James
Sorry about the last SUBJECT line... I hit send a tad too soon.
I have always found that if
> I have the same graphdefang-config and index.pl files on 2 different
> machines. One puts it in the order that they are in the
graphdefang-config
> and the other doesn't.
> HELP
>
> James
I have always found that if I delete all of the png files in the output
directory, and then ru
7 matches
Mail list logo