Hi Sam,
On Tue, Mar 23, 2004 at 01:46:24PM -0600, Sam Laffere wrote:
> Here is a paste of parts of my log, edited for space considerations. On
> message 16306, I left in about anything somebody might want to see, and just
> show the relevant lines on the following messages. You can see that it
> "initial DENYSOFT" a few times. Then after deleting the dbm, it went through
> like it should.
>
>
> 2004-03-22 14:06:11.376379500 tcpserver: pid 16306 from 205.153.245.74
> 2004-03-22 14:06:11.382508500 tcpserver: ok 16306
> nospam1.tri.net:205.153.246.173:25 gw-repco.sasnak.net:205.153.245.74::32227
> 2004-03-22 14:06:27.467172500 16306 250-nospam2.tri.net Hi
> gw-repco.sasnak.net [205.153.245.74]
> .....
> 2004-03-22 14:06:27.767254500 16306 running plugin denysoft_greylist
> 2004-03-22 14:06:27.767980500 16306 denysoft_greylist plugin: using
> ./config/denysoft_greylist.dbm as greylisting database
> 2004-03-22 14:06:28.291187500 16306 denysoft_greylist plugin: key
> 205.153.245.74 initial DENYSOFT, unknown
> 2004-03-22 14:06:28.291999500 16306 denysoft mail from
> [EMAIL PROTECTED] (This mail is temporarily denied)
> 2004-03-22 14:06:28.292220500 16306 450 This mail is temporarily denied
> 2004-03-22 14:06:28.292722500 16306 dispatching RCPT TO:<[EMAIL PROTECTED]>
> 2004-03-22 14:06:28.293225500 16306 503 Use MAIL before RCPT
> 2004-03-22 14:06:28.293500500 16306 dispatching DATA
> 2004-03-22 14:06:28.293867500 16306 503 MAIL first
> 2004-03-22 14:06:28.328542500 16306 dispatching RSET
> 2004-03-22 14:06:28.329204500 16306 250 OK
> 2004-03-22 14:06:28.350679500 16306 dispatching QUIT
> 2004-03-22 14:06:28.351390500 16306 221 nospam2.tri.net closing connection.
> Have a wonderful day.
> 2004-03-22 14:06:28.351833500 16306 running plugin dnsbl
> 2004-03-22 14:06:28.364678500 tcpserver: end 16306 status 0
>
> 2004-03-22 14:07:06.274111500 tcpserver: pid 16452 from 205.153.245.74
> 2004-03-22 14:07:06.274117500 tcpserver: ok 16452
> nospam1.tri.net:205.153.246.173:25 gw-repco.sasnak.net:205.153.245.74::32229
> 2004-03-22 14:07:16.454139500 16452 250-nospam2.tri.net Hi
> gw-repco.sasnak.net [205.153.245.74]
> 2004-03-22 14:07:17.179841500 16452 denysoft_greylist plugin: key
> 205.153.245.74 initial DENYSOFT, unknown
>
> ********The .dbm file was deleted here. The blacklist-time was lowered to 2
> minutes prior to this ************
The rest of your log seems to be doing the right thing. Here in the first part,
the plugin's clearly recognising this is a new ip address, but it looks as if
the write to the db is failing somehow. It's not a locking issue - the lock is
already held at this point.
So I'm not sure why this is failing - could you have been out of disk space or
something? What's the expected behaviour on a dbm tied write in this kind of
situation (e.g. out of disk space)? Should it die or does it just fail via
return code? Line in question is:
$db{$key} = sprintf $fmt, time, ++$new, $black, 0;
Cheers,
Gavin
