If you have access to the DNS server(s), you can always set the TTL down to 5 minutes or so, if that cached value is a problem, and once clear, set it back up to a reasonable value.
Simon Hobson wrote: > =?UTF-8?Q?J=C3=B3n_Ragnarsson?= wrote: >> Hello everybody, please bear with me, I'm a bit wet behind the ears when it >> comes to policyd. >> >> Here is an interesting record from my maillog: >> >> Mar 1 12:00:57 blue postfix/smtpd[13542]: NOQUEUE: reject: RCPT from >> fg-out-1718.google.com[72.14.220.155]: 554 Service unavailable; Client host >> [72.14.220.155] blocked using dnsbl.burnt-tech.com; >> http://dnsbl.burnt-tech.com/lookup.php?ip=72.14.220.155; from=<[email protected]> >> to=<[email protected]> proto=ESMTP helo=<fg-out-1718.google.com> >> >> Now, when I follow that link to dnsbl.burnt-tech.com in the log, it tells >> me that this IP was previously listed in the DNSBL. But for some reason, >> policyd is blocking it. >> >> What could I be doing wrong? Or am I missing something obvious? > > Chances are that it's been cached in the DNS - give it a few hours > and it will probably clear itself. > _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
