Fromn my point of view its crasy to implement greylisting in qmail whith mysql. it just takes to mutch time to create and tear down the connection to the database, and it aint any complex querys to the database. So, i made a lite C-hack who uses postgrey for greylisting. I have bin running it on devel machines for a couple of months now and one month ago i started testing on my production machines, and it just works great. Postgrey gets angry somtimes because i don't include all that postfix does in the conversation, but it just generates some errors in logs, nothing serious.
I modified the patch somewhat to more flexible point. It users a env-variable to control what program to be run as greylisting or if any at all shoud be done. try it out, i recomed. //anton On 25 February, 2006 - ElusiveMind wrote: > Okay! I was about to ask about that. I just found this however: > > #define DEFAULT_BLOCK_EXPIRE 55 /* minutes until email is accepted */ > > I assume by setting this to 1 or 5 I can reduce the time my email > sits waiting to be accepted. > > Thanks; > > Michael Bagnall > ElusiveMind > [EMAIL PROTECTED] > http://elusivemind.net > > On Feb 25, 2006, at 8:03 AM, Rick Macdougall wrote: > > >ElusiveMind wrote: > >>Has anyone had luck in implementing the graylisting patch into the > >>toaster? > >>I've patched it, and compiled it in (along with the qmailtap > >>patch) and mail seems to not be getting through. This is a > >>development system so I'm going to let it sit a while and see if > >>it just takes longer than the hour or so I've given it. > >>I just was curious as to how many have implemented it into the > >>toaster and what your results were. > > > >Hi, > > > >I run it on a few servers but I changed the default second attempt > >time to 1, so as soon as a server tries again, it is allowed through. > > > >Rick > > > > -- Anton Lundin +46702-161604 #!/usr/bin/perl print map chr(ord$_^1<<6),split//,"SRQPOY\',!.#\%YOPQRS";
pgp4XX0f2mvby.pgp
Description: PGP signature
