----- Original Message ----- From: <[EMAIL PROTECTED]> To: "Matt Kettler" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, November 07, 2003 10:55 PM Subject: Re: [Razor-users] URGENT: difficulties with razor + spamassassin
> > 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... I'd suggest running "razor-admin -d -discover" NOT as the user that runs SA (almost never root), but as root. SA really should not run as root, and probably does not, even. In that case, running "razor-admin -d -discover" as the SA user may not have sufficient privileges to alter the discover files. I run this from my crontab for root: 15 7 3 * * /usr/local/bin/razor-admin -discover >/dev/null Thay way, you will not accidentally forget to update either. :) - Mark ------------------------------------------------------- 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
