Daniel Quinlan wrote:
Jesse Houwing <[EMAIL PROTECTED]> writes:
I'm using MDaemon as mailserver under windows. They're shipping with a custom compiled version of Spamassassin 2.63 (compiled with the PerlDevKit by activestate and activestate perl 5.8). They added some specific eval tests for addressbook whitelisting etc.
With this version of spamassassin the NO_DNS_FOR_FROM and other DNS related rules fail after a random interval. Restarting the spamfiltering service fixes the problem.
I contacted their support and got in touch with the developers and they say they haven't altered the DNS lookup code. So this might be a problem in spamassassin itself.
Any leads would be helpful.
Remotely debugging closed binary code that someone got paid for and the person isn't me? No further comment needed. :-)
Yups it sucks ;) but I've been in close contact with them. It seems I'm the only one having these problems at the moment.
It would be nice if the dns_available test would force a retest at a certain interval, in that case I don't get a lot of FP's to this rule.
Net::DNS problems/versioning is the best lead I can do given the situation.
I'll ask them which version they're using and see if there is something more they can do. The version they're using right now had problems finding out which DNS server to use, so I had to set the RES_NAMESERVERS env variable. I think they're using an old version.
Jesse
