* Cam Ellison ([EMAIL PROTECTED]) wrote:
> I have Razor 2.22 and spamassassin 2.55 on a Debian box. When I run
> razor-report, it goes on through the routine until the point below:
SORRY! Wrong list!
I wasn't thinking while I was typing.
Cam
--
Cam Ellison Ph.D. R.Psych.
From Ro
(which I don't have, unless I haven't
noticed) that triggers this, or is it not being reported at all?
Cam
--
Cam Ellison Ph.D. R.Psych.
From Roberts Creek on B.C.'s incomparable Sunshine Coast
cam(at)ellisonet(dot)ca
camellison(at)dccnet(dot)com
cam(at)fleuryass
e run the spam below against a vanilla ruleset, 2.5[45]
> and/or 2.6, and let me know if this spam should have been caught under
> 2.54?
>
The above should tell you. I'm running 2.55 with razor 2.22.
Cam
--
Cam Ellison Ph.D. R.Psych.
From Roberts Creek on B.C.'s incomp
* Oliver Egginger ([EMAIL PROTECTED]) wrote:
> Try restarting spamd.
>
Thanks, but that turns out not to be necessary. I re-ran razor-admin
-discover on Kelson's suggestion, and things are fine now.
Cam
--
Cam Ellison Ph.D. R.Psych.
From Roberts Creek on B.C.'s incomparable Su
azor2 check skipped: Timed
out! at /usr/share/perl/5.8.0/Net/Ping.pm line 484, line 1.
I assume something changed in (a) perl, (b) spamassassin, or (c)
razor2 and I missed it, but what was it?
Any suggestions gratefully received.
Cam
--
Cam Ellison Ph.D. R.Psych.
From Roberts Creek on B