Ron, After reading this thread today, I decided to check out amavisd-debug on my two servers. Sure enough, I had the exact same problem you did. Both of these were using Razor fine last week. The only thing I changed on the two boxes was adding a couple of domains to the amavisd-new blacklist file.
I also ended up manually setting the IP address and now Razor works again. So, it wasn't just you that this happened to. Thanks, Mark -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Ron E. Sent: Monday, November 10, 2003 11:54 AM To: [EMAIL PROTECTED] Subject: [Razor-users] Resolution of URGENT: difficulties with razor + spamassassin Thanks to all who helped on this - I finally did get it working by manually updating the IP of the server - discovery simply wasn't working whether I ran it as root or the spamassassin user. The discover did work on another server, however, but both have dns access so the puzzle remains. Will be reconfiguring a new machine, though, and I will retest this. Regards, Ron ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ Razor-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/razor-users --- [This E-mail scanned for viruses by Declude Virus] --- [This E-mail scanned for viruses by Declude Virus] ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ Razor-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/razor-users
