In article <4f942ff2cfantispam@xxxxxxxxx>, Frank de Bruijn <antispam@xxxxxxxxx> wrote: > The strange thing is, two or three people have mentioned this since > DNSBL testing was added to AntiSpam, but I've never seen it happen > myself. I've only seen it once before and thought it was something I'd done just beforehand. In this instance the problem started at a few minutes past midnight and I noticed the beep of the error when I got up (who switches computers off anyway?) A restart of Antispam didn't cure things so I looked at the NSQ module and noted it was left active after Antispam had been shutdown. What I think would cure the problem is an RMKill in the Antispam shutdown and the restart will then load a newly initialised instance.