> >I have it working fine, here is the idea:
> >1. Most of the documentation is out of date! One needs do absolutely
> >nothing.
>
> Not true. It may function, but if you do nothing razor has to try and
> discover the servers for every message. This creates unnecessary traffic
> and processing power on both ends. You need to run
> razor-admin -create (twice for good measure - and then make sure it
worked)
> as the user that will be calling razor (or every user that calls razor).
> This makes the available server data available locally. You also need to
> disable logging or eventually your disk will fill up with razor logs.
You
> can do this globally if you like by configuring the site wide config
file
> in the /etc/razor directory.
I did do this. This is what failed before changing the firewall.
Right, it would fail if the port is blocked.
SA does not
require this stuff but Razor works better with it done. About out-of-date
documentation, suggested three steps. Running the first one said it was
obselete and the Razor works by default.
Is this what you are refering to?
http://marc.theaimsgroup.com/?l=razor-users&m=111962049416855
There have been some changes in versions, and when you run the deprecated
command the error message is misleading and innacurate. I don't use sid, but
from what you describe it looks like the documentation doesn't fit the
version (that is if it asks you to run razor-client). If so, I would submit
a bug report the the Debian maintainer.
The second was the discover and the
third was to get a registration ID. Now, how do I use that to report spam?
spamassassin -r <message
(for example) as the Bayes user in question (this will to report to other
stuff as well as razor).
also see:
man razor-agents
>
> >SA tests for an will use Razor, Phyzor, etc., if they be installed.
> >2. All this is of no avail if TCP to port 2703 be not allowed by the
> >firewall.
> >This was buried in a email thread and not present in the documentation.
> > (It is not sufficient to enable from Razors main site in a DMZ since
> > other IPs are involved as well.)
>
> http://razor.sourceforge.net/docs/doc.php?type=text&name=FAQ
>
OK. When I install off Debian Sid, nothing refers me to sourceforge and
neither the docs in the package nor the programs (could say discovery
failed--cannot connect port 2703--check your firewall) suggested enabling
stuff in the firewall.
No doubt, that *would* be nice.
Gary V
_________________________________________________________________
Try the next generation of search with Windows Live Search today!
http://imagine-windowslive.com/minisites/searchlaunch/?locale=en-us&source=hmtagline
