It was very curious. I could see in the logs lines like this: 2007-09-06 15:04:18.705745500 13257 greylisting plugin: key 68.180.197.125:[EMAIL PROTECTED]:[EMAIL PROTECTED] initial DENYSOFT, unknown
but when I looked in the db file, there'd be no entry for this triplet
"68.180.197.125:[EMAIL PROTECTED]:[EMAIL PROTECTED]", so the
message would never get through.
I can't see how the code could do that unless something was wrong with the tie
to the db or maybe the filelocking wasn't working.
I then realized that I have no idea how an error would get reported if there
were a problem with the tie to the DB other than an error while opening the
file. It may be a problem on my system, but I can't diagnose it.
Anyway, now that it's been explained to me that the included greylisting
plugin isn't "recommended" per se, but is considered example code, I'm curious
what other plugins are out there that do greylisting? Peter Holzer sent me
a pointer to his implementation when I was having problem with the
whitelisting in this plugin. I'll take a look at that. Are there any others
worth looking at?
Going to sleep last night, I realized that I could write something that uses a
djbesque approach of putting the hashes in a filesystem thereby not using tie
and in a way that would not require me to lock anything. It would also be
simpler than the one I was using and I'd be able to see what was in the
database from the command line. Before I start writing code, however, I
really should look at what else is out there first.
Chris
--
Chris Garrigues Trinsic Solutions
President 710-B West 14th Street
Austin, TX 78701-1798
http://www.trinsics.com/blog
http://www.trinsics.com 512-322-0180
Would you rather proactively pay for
uptime or reactively pay for downtime?
Trinsic Solutions
Your Trusted Friends in Proactive IT.
pgp8rZXg4fdJD.pgp
Description: PGP signature
