I pretty much concluded from the docs that verify managed the file, but
waited for confirmation from you.
The script should prove very helpful.
Thanks Len
Len Conrad wrote:
>the .db file gets too big. 1.1 GB is about the limit in fbsd.
>
>Run this address_verify_watchdog.sh once a day, and set the size to suit.
>
>positive/negative caching values can be shortened to keep the file smaller.
>
>#!/bin/sh
>
>AVMAXFSIZE="900000000"
>AVFNAME="/var/log/address_verify.map.db"
>AVFSIZE="`ls -al $AVFNAME | awk '{ print $5}'`"
>
>if [ $AVFSIZE -gt "$AVMAXFSIZE" ] ; then
>
> mv $AVFNAME $AVFNAME.save
> mail < /dev/null -s "`hostname` $AVFNAME exceeded $AVMAXFSIZE bytes and
>has been zeroed" [EMAIL PROTECTED] [EMAIL PROTECTED]
>[EMAIL PROTECTED]
> /usr/sbin/postfix stop
> /usr/sbin/postfix start
>fi
>
>exit 0
>
>
>
>
>>the address_verify.map.db file. The file size was about 643MB. I have
>>temporarily turned off reject_unverified_recipient which is allowing
>>mail to flow again. Not being the person to set this up, I have no idea
>>what needs to go into this .map file.
>>
>>
>
>it's manually maintained by the verify service.
>
>
>
>> The current address_verify.map is
>>empty
>>
>>
>
>verify service write directly to the .map.db file, never to the .map file
>
>
>
>> and doing a postmap of it obviously created a new
>>address_verify.map.db, but it isn't verifying correctly once I turn
>>reject_unverified_recipient back on.
>>
>>
>
>zero the .db file, postfix will re-create it
>
>rm /var/log/address_verify.map.db
>
>Len
>
>
>
>
>
>
--
Thank You
Ten Forward Customer Support
