On Fri, Sep 07, 2007 at 02:10:34PM -0500, Chris Garrigues wrote:
> 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.
And how did you look at the db file?
> 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.
If you think the write itself is failing you could try checking the return code
of the $db{$key} assignments statements. Maybe those should be tested
explicitly;
I'm not sure if a failure there will just die or not.
> Anyway, now that it's been explained to me that the included greylisting
> plugin isn't "recommended" per se, but is considered example code,
That's a curious statement. The greylisting plugin is no less recommended
than any of the other plugins, and it's being used in production lots of
places.
If you mean that you may need to make code changes to do whatever it is you're
trying to do, then yes, that's generally true - that's the qpsmtpd way.
Cheers,
Gavin
