Hi! W dniu 2021-08-05 o 09:51, Dave Warren pisze: > There are two other things you can do to avoid hitting limits. > > Maybe the obvious one: Contact the DNSBL.
It's better to fix it in one place, in masscheck because this fix will be spread over all masscheckers. Why every masschecker should bother dnsbl admins? [...] > I also already ran my own wrbldnsd installation on my live mail server, > and therefore was in a position to accept rsync based rbldnsd formatted > files. Workarround as above. > The other thing I did on my masscheck box was to configure my DNS > resolver with a minimum TTL of some hours. Since we are checking mail > that is relatively ancient anyway, who cares if a particular DNS request > is 5 minutes or 3 hours old? This reduced the number of DNS queries > hitting "the world" considerably and was probably sufficient to stay > under limits. Be sure to increase the negative TTL cache as well. But long TTL doesn't help when masscheck will be checking 2 month old emails. Henrik mentioned to use "--reuse" but I don't use header X-Spam-Status :/ Anyway, where is a problem, why masscheck have to query all uribl/dnsbl? It needs a lot of time for devs? Regards! Marcin
