Jorge =?iso-8859-1?q?F=E1bregas?= <[EMAIL PROTECTED]> wrote:
I'll just keep watching the spam reprots regularly and If I see
something strange with Pyzor I now probably know what it is.
Better yet, subscribe to pyzor-announce. People on the list got notified
ahead of time.
It's very low traffic:
On Wednesday 18 June 2003 5:14 am, Brian Read wrote:
> Thanks for this. When is "pyzor discover" normally run?
You're welcome. I didn't know the "discover" argument existed at all !
I thought they had a better|elegant way of doing this switch but that's not
the case. I've been thinking about
I noticed I wasn't hitting the Pyzor rule for a couple of days...When I ran
spamassassin in debug mode I had:
66.47.67.162:24441 TimeoutError
It tuns out their public server changed its address. You need to run:
pyzor discover
...in order to get the new address. Check their page:
http://p
On Tue, 2003-06-17 at 18:25, Jorge Fábregas wrote:
> Hello all,
>
> I noticed I wasn't hitting the Pyzor rule for a couple of days...When I ran
> spamassassin in debug mode I had:
>
> 66.47.67.162:24441 TimeoutError
>
> It tuns out their public server changed its address. You need to run:
Hello all,
I noticed I wasn't hitting the Pyzor rule for a couple of days...When I ran
spamassassin in debug mode I had:
66.47.67.162:24441 TimeoutError
It tuns out their public server changed its address. You need to run:
pyzor discover
...in order to get the new address. Check their
