On Fri, 7 Nov 2003, Matt Kettler wrote:
> At 01:58 PM 11/7/2003, [EMAIL PROTECTED] wrote: > >Dear All, > > > >I have been running spamassassin + razor for quite some time and no > >problems until recently. Recently mail has been getting backlogged and > >after getting some spamassassin debug output, the biggest delay appears to > >be after the following: > > > >Checking with Razor Discovery Server 216.52.3.2 > >No port specified, using 2703 > >Connecting to 216.52.3.2... > > I'd suggest forcing a full discovery at the DNS level.. it sounds like the > discovery server you have is outdated.. my client is using 66.151.150.11 as > a discovery server. > > Run the following command as the user that runs SA (usualy root) to force a > full "from scratch" discovery: > > razor-admin -d -discover > > Strange - I've done this definitely as the user that runs SA and I'm still setting the same IP show up... is there a way I can search for the various razor conf files to see where the culprit is? > > ------------------------------------------------------- > 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 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
