IPBlock cronjob doesn't clear blocked IP's in 4.25-14 - resolved

[Dan Williamson]

After scrutinizing the cronjob I noticed I had made a typo on my $Refusal
line... oops.
Thanks for this great feature it is proving extremely valuable for us.

regards,
-dan


-----Original Message-----
From: MailScanner mailing list [mailto:MAILSCANNER at JISCMAIL.AC.UK]On
Behalf Of Julian Field
Sent: January 24, 2004 4:51 AM
To: MAILSCANNER at JISCMAIL.AC.UK
Subject: Re: IPBlock cronjob doesn't clear blocked IP's in 4.25-14


The block removal is done by the cron job.
Please can you diff the old cron job (that works) and the new one (that
doesn't) to see if there are any differences.

At 22:49 23/01/2004, you wrote:
>After upgrading one of my mail servers to 4.25-14 and enabling IPBlock I
>have noticed that blocked IP addresses are not being cleared from sendmails
>rules.
>
>When I run makemap on the IPBlock.db file I can see the IP being removed
>after the cronjob runs.
>
>I use deny.db rather than access.db.
>
>I changed the IPBlock.pl cron to,
>         my $AccessDB     = '/etc/mail/deny.db';
>As well, I modified the CustomConfig.pm file to,
>         my $AccessDB       = '/etc/mail/deny.db';
>
>After the cronjob runs I can see that the deny.db has been altered by the
>date change, but the offending IP is still in the deny.db file.  If I run
>makemap manually on the deny database the IP address is once again allowed
>to relay.
>
>I have another server that runs 4.24-5, although quite a different set-up
it
>works flawless using the deny.db.
>
>Any ideas what I may have missed?
>
>regards,
>-dan

--
Julian Field
www.MailScanner.info
Professional Support Services at www.MailScanner.biz
MailScanner thanks transtec Computers for their support
PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654