Isn't it suggested to use btree style databases for that? I've got my address_verify set to this: # "sender address verification" feature address_verify_map = btree:/var/log/address_verify address_verify_positive_expire_time = 31d address_verify_positive_refresh_time = 7d address_verify_negative_cache = yes address_verify_negative_expire_time = 3h address_verify_negative_refresh_time = 1h
Current size is around 139Mb. -Mitch ias.net -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Len Conrad Sent: Thursday, January 27, 2005 2:25 PM To: [email protected] Subject: [IMGate] Re: Problem with reject_unverified_recipient 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
