On Tue, 2012-08-21 at 17:13:44 +0200, DTNX Postmaster wrote: > For example, when an existing account is deleted on the backend server, > Postfix will have the positive result, and maintain it for quite some > time using the default settings; > > $ /usr/sbin/postconf -d |grep address_verify_positive_ > address_verify_positive_expire_time = 31d > address_verify_positive_refresh_time = 7d > > We tried setting 'address_verify_positive_refresh_time' to a low value > to test with, but that does not update the cache. This is apparently by > design, no doubt for good reasons. > > How do others deal with this? Set 'address_verify_positive_expire_time' > to a value significantly lower than the default?
I have lowered the expire time but, to avoid backscattering during the interim, I add a transport entry on the front-end MX that directs mail for deleted accounts to the error(8) delivery agent. I understand that may seem kludgy and too manual, but it works for us. > Force expiry from the cache manually, somehow? AFAIK, that is not possible. > Also, what purpose does the refresh timer serve if there is no update > done due to optimistic caching? My understanding of this parameter is that a _successful_ refresh probe updates the timestamp of an address verification result; positive expire time is measured from that revised timestamp. -- Sahil Tandon
