pyzor-users — general discussion of Pyzor and Pyzor-related topics

Re: Pyzor 0.5 Released

[Matus U. - f. <uh...@fa...>]

Hello,

On 07.05.09 20:59, Tony Meyer wrote:
> The Pyzor team is pleased to announce release 0.5 of Pyzor.

nice, thank you.

> Pyzor initially started out to be merely a Python implementation of
> Razor, but due to the protocol and the fact that Razor's server is not
> Open Source or software libre, Frank Tobin decided to implement Pyzor
> with a new protocol and release the entire system as Open Source and
> software libre.

which reminds me of a question: iz PYZOR yet compatible with RAZOR or
already not?

-- 
Matus UHLAR - fantomas, uh...@fa... ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
   One OS to rule them all, One OS to find them, 
One OS to bring them all and into darkness bind them 

Pyzor 0.5 Released

[Tony M. <to...@sp...>]

The Pyzor team is pleased to announce release 0.5 of Pyzor.

The previous release was made in September of 2002, so it has
obviously been a while!  With this release, we have aimed to resolve
all the outstanding reported bugs and incorporate submitted patches
(many of which are also from some time ago).  The hope is that this,
along with the recent improvements to the public Pyzor server,
revitalises the Pyzor project.

We are aiming to release the next version of Pyzor, which will include
new features, around the end of June (2009!).  If you'd like to have
input into that release, please subscribe to the pyzor-users mailing
list, or monitor the SourceForge tickets for the Pyzor project.  We
are very keen to have as much input from the user-base as possible.

The majority of the improvements in the 0.5 release were submitted
from the Debian Pyzor package.  Many thanks to them for pushing these
back 'upstream' - if you have any improvements that you are running
locally, please consider doing the same and contributing these as
patches to the main Pyzor package (open a ticket on the SourceForge
site).

Main changes include:

       *       Man pages for pyzor and pyzord.

       *       Changing back to signals for database locking,
               rather than threads.  It is likely that signals
               will be removed again in the future, but the
               existing threading changes caused problems.

       *       Basic checks on the results of "discover".

       *       Extended mbox support throughout the library.

       *       Better handling on unknown encodings.

       *       Added a --log option to log to a file.

       *       Better handling of command-line options.

       *       Improved error handling.

You can get the release (via the 'download' link on the left), as well
as information about the mailing lists and other news, at:

   http://pyzor.org

Enjoy the new release and your reduced spam mail :)

As always, thanks to everyone involved in this release!

Tony.
(on behalf of the Pyzor team)

--- What is Pyzor? ---

Pyzor is a collaborative, networked system to detect and block spam
using identifying digests of messages.

Pyzor initially started out to be merely a Python implementation of
Razor, but due to the protocol and the fact that Razor's server is not
Open Source or software libre, Frank Tobin decided to implement Pyzor
with a new protocol and release the entire system as Open Source and
software libre.

Since the entire system is released under the GPL, people are free to
host their own independent servers, although there is a
well-maintained public server available (public.pyzor.org), which
anyone is welcome to use.

Re: deprecationwarning

[Tony M. <to...@sp...>]

>> > Anyway, when trying to install from source I get the below
>> >
>> > error: invalid Python installation: unable to
>> > open /usr/lib/python2.6/config/Makefile (No such file or directory)
>>
>> What exactly did you run to get this?  'python setup.py install' or
>> something else?
>
> Sorry for the late reply, been working on this Mandriva 2009.0 > .1
> upgrade. Yes it was per the docs for 0.4.0:
>
> To install this distribution, simply run the following:
>        python setup.py build
>        python setup.py install

It works for me on Debian, so it must be something specific to the
distro.  It's the standard "distutils" way of installing a Python
package, so in theory it ought to work wherever, but I guess here it
expects something else.

I would say that it's probably best to just stick to the
distro-provided package.  I'll be releasing 0.5 tomorrow, so you could
try that, but my guess is that it'll have the same effect.

If you'd really like installing from source to work, please open a bug
on SF (http://sf.net/projects/pyzor) so that I don't lose track of
this, and I'll track down the changes that are made in the
distro-package version and see if those can be incorporated into the
main distribution without breaking anything else.

Cheers,
Tony

Re: deprecationwarning

[Chris <cpo...@em...>]

On Sun, 2009-05-03 at 16:06 +1200, Tony Meyer wrote:
> > Anyway, when trying to install from source I get the below
> >
> > error: invalid Python installation: unable to
> > open /usr/lib/python2.6/config/Makefile (No such file or directory)
> 
> What exactly did you run to get this?  'python setup.py install' or
> something else?

Sorry for the late reply, been working on this Mandriva 2009.0 > .1
upgrade. Yes it was per the docs for 0.4.0:

To install this distribution, simply run the following:
	python setup.py build
	python setup.py install


> > [chris@localhost pyzor-0.4.0]$ pyzor discover
> > /usr/lib/python2.6/site-packages/pyzor/__init__.py:11:
> > DeprecationWarning: the sha module is deprecated; use the hashlib module
> > instead
> >  import sha
> > downloading servers from
> > http://pyzor.sourceforge.net/cgi-bin/inform-servers-0-3-x
> > [chris@localhost pyzor-0.4.0]$ pyzor ping
> > /usr/lib/python2.6/site-packages/pyzor/__init__.py:11:
> > DeprecationWarning: the sha module is deprecated; use the hashlib module
> > instead
> >  import sha
> > /usr/lib/python2.6/site-packages/pyzor/__init__.py:429:
> > DeprecationWarning: object.__init__() takes no parameters
> >  super(ThreadId, self).__init__(i)
> > public.pyzor.org:24441  (200, 'OK')
> 
> This is the correct response: (200, 'OK').  The rest are deprecation
> warnings, because pyzor supports versions of Python much older than
> 2.6, and Python 2.6 has deprecated quite a lot of older Python
> features (for the transition to Python 3.0).
> 
> These aren't errors - depending on how you're using Pyzor, you might
> be able to just ignore them.  If you want to silence them, the Python
> warnings module will let you customise the warnings that you see.
> 
Thanks, it seems to be working great with SA:

X-spam-pyzor: Reported 3 times

-- 
KeyID 0xE372A7DA98E6705C

Re: pyzor automatic submission

[Tony M. <to...@sp...>]

> the problem might be counting with hit/whitelist. Maybe a whitelist could
> have value of 5 listings. Or maybe an algorithm is needed to count the
> accuracy, to avoid whitelistings by spammers, automatic listings etc.

The automatic listing and listing by spammers goes back to having some
sort of trust value for users, I think.

I'm not sure what Frank originally intended when designing this
feature (it looks like he felt it should be up to the user).  When I
have a chance, I'll try and see if he wrote anything that outlined the
reasoning.

Returning the two raw values is optimal for users that want complete
control, because they can decide how to use them.  If they want to
have X whitelist values overrule any number of hits, or use the
difference, or a weighted difference, or a percentage, or the lower
bound of Wilson score confidence interval for a Bernoulli parameter,
then they can do that.

However, returning two raw values is sub-optimal for users that just
want pyzor to say whether it looks like a message is spam or not, and
I suspect most users are in this group.  For this, we need to choose
something appropriate, rather than leave it up to the user.

Although I'm not new to development, or open-source development, or
spam filtering, or hash-based classifiers, I am still new to Pyzor
development.  Unfortunately, because of the long inactive period,
there aren't really any other developers around who have the
historical knowledge to explain why things work the way they do.

As such, I'm reluctant to make fundamental changes to how pyzor works
just yet.  That's not to say that such changes can't be made, just
that I'd like to spend a bit more time working with the code before
doing anything like that.  So for now, I'm concentrating on bug fixes,
and non-fundamental changes (improving performance, Python version
issues, site-wide configuration, etc), while I think about how other
things might be able to change.

I suspect that the best way to go about this might be to add a new
command (e.g. "score") that gave a single-value score (however that
might be calculated).  Users could then move (at their own pace) to
that command, or continue to use "check" if they wanted the raw
values.  That would maintain backwards compatibility, which I think is
quite important here.

> I think that could be something similar to:
> http://www.evanmiller.org/how-not-to-sort-by-average-rating.html

Thanks for the link - an interesting read.

Cheers,
Tony

Re: pyzor automatic submission

[Tony M. <to...@sp...>]

> After discussing this with a SpamAssassin developer (Justin Mason) I've
> posted a feature request at
> https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6108 . Would be
> great if someone on this list could actually write a working patch
> (plugin code is available at
> http://cpansearch.perl.org/src/JMASON/Mail-SpamAssassin-3.2.5/lib/Mail/SpamAssassin/Plugin/Pyzor.pm).

BTW, I took a look at the source, and even my poor Perl skills can see
that the whitelist value is retrieved and calculated, so it would
mostly be a case of using it (e.g. adding an additional option for the
number of whitelist counts that were required to override the hit
count, and then code to do that), however the implementer decided the
value was best used.

Cheers,
Tony

Re: Pyzor 0.5.0 release candidate

[Tony M. <to...@sp...>]

[Matus UHLAR - fantomas]
>> Please, give us site-wide config directory :-)

[Dreas van Donselaar]
> After this bugfix release new features will be considered.  Since you
> have already posted this request (at
> http://sourceforge.net/tracker/?func=detail&aid=2786577&group_id=50000&atid=458245),
> it will be taken into account when further developing the Pyzor client.

As Dreas said, the 0.5 release is meant to be very conservative
(because it has been so long since there has been a release, and
because I am still new to Pyzor (although not development, filtering,
or hashed classifiers)).  So it's just bug-fixes and some
documentation patches, and even those changes should be fairly safe,
because they already exist in the Debian Pyzor package.

FWIW, I do think there is value in a site-wide config directory, so it
will probably be in the next release, since it's fairly simple to do.
Not so much for the reason given in the SF ticket (the server
location), since the idea is that "discover" be deprecated/removed in
favour of using DNS (which really does the same job much more simply,
with existing infrastructure).  However, the AccountsFile and Timeout
config values would be reasonable site-wide settings.

Cheers,
Tony

Re: Pyzor 0.5.0 release candidate

[Dreas v. D. <dr...@sp...>]

Benny Pedersen wrote:
> On Mon, May 4, 2009 15:31, Dreas van Donselaar wrote:
>   
>> it will be taken into account when further developing the Pyzor client.
>>     
>
> changing the --homedir just changes the problem, it does not solve it
>   
I didn't say it would actually be implemented ;) Leaving that up to the 
developer.

Regards,

Dreas

Re: Pyzor 0.5.0 release candidate

[Benny P. <me...@ju...>]

On Mon, May 4, 2009 15:31, Dreas van Donselaar wrote:
> it will be taken into account when further developing the Pyzor client.

changing the --homedir just changes the problem, it does not solve it

-- 
http://localhost/ 100% uptime and 100% mirrored :)

Re: Pyzor 0.5.0 release candidate

[Benny P. <me...@ju...>]

On Mon, May 4, 2009 15:06, Matus UHLAR - fantomas wrote:
> Please, give us site-wide config directory :-)

it already works here, pyzord uses its homedir, pyzor use its homedir, why
change it ?

pyzord does not need to run as root remember ?, if you want to bith just
ignore me :)

-- 
http://localhost/ 100% uptime and 100% mirrored :)

Re: pyzor automatic submission

[Dreas v. D. <dr...@sp...>]

Tony Meyer wrote:
> I'd be happier if someone else did (I'm assuming that it's in Perl,
> like most of SA, and my Perl is not great).  I would be happy to help
> someone more suited to doing it, though.  Does anyone know who
> maintains the SA plug-in?
>   
After discussing this with a SpamAssassin developer (Justin Mason) I've 
posted a feature request at 
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6108 . Would be 
great if someone on this list could actually write a working patch 
(plugin code is available at 
http://cpansearch.perl.org/src/JMASON/Mail-SpamAssassin-3.2.5/lib/Mail/SpamAssassin/Plugin/Pyzor.pm). 
Please inform me if you like to work on this so I can try to help where 
possible.

Regards,

Dreas

Re: Pyzor 0.5.0 release candidate

[Dreas v. D. <dr...@sp...>]

Matus UHLAR - fantomas wrote:
> On 30.04.09 09:03, Tony Meyer wrote:
>   
>> I believe pyzor 0.5 is all ready to go.  This is a bugfix release,
>> mostly patches contributed from the Debian pyzor package.  The purpose
>> of the release is basically to clear up old issues, so that we can
>> continue to bring pyzor back to a more active project.
>>     
>
> Please, give us site-wide config directory :-)
>   
After this bugfix release new features will be considered.  Since you 
have already posted this request (at 
http://sourceforge.net/tracker/?func=detail&aid=2786577&group_id=50000&atid=458245), 
it will be taken into account when further developing the Pyzor client. 
Thanks for that.

Regards,

Dreas

Re: Pyzor 0.5.0 release candidate

[Matus U. - f. <uh...@fa...>]

On 30.04.09 09:03, Tony Meyer wrote:
> I believe pyzor 0.5 is all ready to go.  This is a bugfix release,
> mostly patches contributed from the Debian pyzor package.  The purpose
> of the release is basically to clear up old issues, so that we can
> continue to bring pyzor back to a more active project.

Please, give us site-wide config directory :-)

-- 
Matus UHLAR - fantomas, uh...@fa... ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Windows found: (R)emove, (E)rase, (D)elete

Re: pyzor automatic submission

[Matus U. - f. <uh...@fa...>]

> > I know users are stupid. But does pyzor need stupid users? ;-)
> > A trust system like RAZOR's would be nice.
> 
> I've wondered about that.  It does complicate a very simple process,
> but if there are too many incorrect submissions, then something like
> that really is needed.
> 
> > How does "pyzor whitelist" affect the listing? Is that purely local or
> > does it remove the listing at all?

On 03.05.09 10:24, Tony Meyer wrote:
> The database has two values for each digest - one "hit count" and one
> "whitelist count".  You get both of those back from a pyzor check
> command, so basically it's up to you to decide what you do with them
> (I believe SpamAssassin ignores the whitelist value, for example).

the problem might be counting with hit/whitelist. Maybe a whitelist could
have value of 5 listings. Or maybe an algorithm is needed to count the
accuracy, to avoid whitelistings by spammers, automatic listings etc.

I think that could be something similar to:
http://www.evanmiller.org/how-not-to-sort-by-average-rating.html

-- 
Matus UHLAR - fantomas, uh...@fa... ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
LSD will make your ECS screen display 16.7 million colors

Re: pyzor automatic submission

[Tony M. <to...@sp...>]

>> The database has two values for each digest - one "hit count" and one
>> "whitelist count".  You get both of those back from a pyzor check
>> command, so basically it's up to you to decide what you do with them
>> (I believe SpamAssassin ignores the whitelist value, for example).
>
> would it make sense to change that plugin to only report spam when scores
> in spamassassin is high ? and try whitelist when the score is low ?

IMO the plug-in should use the whitelist value, yes.  I think possibly
it was added to SA before Pyzor had any whitelisting, and has just
never been updated.  The SA configuration does allow you, from what I
can see, to select the number of 'hits' that are required for the
plug-in to consider the message spam.

> would you rework the sa plugin for this ?

I'd be happier if someone else did (I'm assuming that it's in Perl,
like most of SA, and my Perl is not great).  I would be happy to help
someone more suited to doing it, though.  Does anyone know who
maintains the SA plug-in?

Cheers,
Tony

Re: deprecationwarning

[Tony M. <to...@sp...>]

> Anyway, when trying to install from source I get the below
>
> error: invalid Python installation: unable to
> open /usr/lib/python2.6/config/Makefile (No such file or directory)

What exactly did you run to get this?  'python setup.py install' or
something else?

> [chris@localhost pyzor-0.4.0]$ pyzor discover
> /usr/lib/python2.6/site-packages/pyzor/__init__.py:11:
> DeprecationWarning: the sha module is deprecated; use the hashlib module
> instead
>  import sha
> downloading servers from
> http://pyzor.sourceforge.net/cgi-bin/inform-servers-0-3-x
> [chris@localhost pyzor-0.4.0]$ pyzor ping
> /usr/lib/python2.6/site-packages/pyzor/__init__.py:11:
> DeprecationWarning: the sha module is deprecated; use the hashlib module
> instead
>  import sha
> /usr/lib/python2.6/site-packages/pyzor/__init__.py:429:
> DeprecationWarning: object.__init__() takes no parameters
>  super(ThreadId, self).__init__(i)
> public.pyzor.org:24441  (200, 'OK')

This is the correct response: (200, 'OK').  The rest are deprecation
warnings, because pyzor supports versions of Python much older than
2.6, and Python 2.6 has deprecated quite a lot of older Python
features (for the transition to Python 3.0).

These aren't errors - depending on how you're using Pyzor, you might
be able to just ignore them.  If you want to silence them, the Python
warnings module will let you customise the warnings that you see.

In the version of Pyzor after the upcoming 0.5, I'll make sure that
there aren't any warnings with Python 2.6 (and, hopefully, using 3.0
is easy), but this will mean increasing the minimum version as well
(to 2.4 or 2.5 probably).  I'm hoping to get a 0.6 release out in
mid-June.

Cheers,
Tony

deprecationwarning

[Chris <cpo...@em...>]

I'm working on getting my system back again after an 'upgrade' from
Mandrive 2009.0 to .1, what a pain. Anyway, when trying to install from
source I get the below

error: invalid Python installation: unable to
open /usr/lib/python2.6/config/Makefile (No such file or directory)

looking at the /usr/lib/python2.6 dir there is no /config/directory so I
decided to just install the mandriva rpm and got the below

[chris@localhost pyzor-0.4.0]$ pyzor discover
/usr/lib/python2.6/site-packages/pyzor/__init__.py:11:
DeprecationWarning: the sha module is deprecated; use the hashlib module
instead
  import sha
downloading servers from
http://pyzor.sourceforge.net/cgi-bin/inform-servers-0-3-x
[chris@localhost pyzor-0.4.0]$ pyzor ping
/usr/lib/python2.6/site-packages/pyzor/__init__.py:11:
DeprecationWarning: the sha module is deprecated; use the hashlib module
instead
  import sha
/usr/lib/python2.6/site-packages/pyzor/__init__.py:429:
DeprecationWarning: object.__init__() takes no parameters
  super(ThreadId, self).__init__(i)
public.pyzor.org:24441	(200, 'OK')

I find this in my python folder:

/usr/lib/python2.6/hashlib.py
/usr/lib/python2.6/hashlib.pyc
/usr/lib/python2.6/hashlib.pyo
/usr/lib/python2.6/lib-dynload/_hashlib.so


-- 
KeyID 0xE372A7DA98E6705C

Re: pyzor automatic submission

[Benny P. <me...@ju...>]

On Sun, May 3, 2009 00:24, Tony Meyer wrote:

> The database has two values for each digest - one "hit count" and one
> "whitelist count".  You get both of those back from a pyzor check
> command, so basically it's up to you to decide what you do with them
> (I believe SpamAssassin ignores the whitelist value, for example).

would it make sense to change that plugin to only report spam when scores
in spamassassin is high ? and try whitelist when the score is low ?

in a distrubed system it would be nice imho it was so

i think something like bayes autolearn scores

would you rework the sa plugin for this ?

-- 
http://localhost/ 100% uptime and 100% mirrored :)

Re: pyzor automatic submission

[Tony M. <to...@sp...>]

> I know users are stupid. But does pyzor need stupid users? ;-)
> A trust system like RAZOR's would be nice.

I've wondered about that.  It does complicate a very simple process,
but if there are too many incorrect submissions, then something like
that really is needed.

> How does "pyzor whitelist" affect the listing? Is that purely local or does
> it remove the listing at all?

The database has two values for each digest - one "hit count" and one
"whitelist count".  You get both of those back from a pyzor check
command, so basically it's up to you to decide what you do with them
(I believe SpamAssassin ignores the whitelist value, for example).

Cheers,
Tony

Re: pyzor automatic submission

[Matus U. - f. <uh...@fa...>]

> > Some time ago I have noticed that mails like monthly mailing list reports
> > are listed in pyzor. I strongly doubt that such mails are feed to pyzor
> > manually and I guess someone has implemented automatic submission for
> > detected spam.
> >
> > Is this correct? Razor docs say that only manual submissions should be done
> > and I'd expect the same from pyzor, however I haven't found any reference...

On 30.04.09 08:33, Tony Meyer wrote:
> At the moment, there's no restriction over who can submit, so there's
> effectively no way of controlling what is submitted - we have to trust
> that people are only submitting true spam.  It's quite possible that
> there are people that are automatically submitting, but there isn't
> much that can be done about that, as far as I can see.  It's also
> possible that people are submitting these as spam manually - end-users
> have a bad habit of submitting as spam things that they legitimately
> signed up for, but no longer have interest in, and are too lazy to
> unsubscribe from.  There's not much that can be done about that,
> either, unfortunately.

I know users are stupid. But does pyzor need stupid users? ;-)
A trust system like RAZOR's would be nice.

> My best suggestion is that I would guess that messages like this have
> a reasonably low hit count (e.g. instead of a hundred reports, there
> are fewer than 10).  By adjusting the threshold that you use for a
> Pyzor result to be considered spam, you might be able to avoid
> triggering on these messages.

IIRC the hit count was pretty high. Let's see tomorrow.

How does "pyzor whitelist" affect the listing? Is that purely local or does
it remove the listing at all?

-- 
Matus UHLAR - fantomas, uh...@fa... ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
   One OS to rule them all, One OS to find them, 
One OS to bring them all and into darkness bind them 

Re: pyzor reporting failing since change to new server

[Dreas v. D. <dr...@sp...>]

Mark Fisher wrote:
> No, the test should work as shown.  I would suggest checking that you
> are configured to communicate with public.pyzor.com.
Note that this should be public.pyzor.ORG

Regards,

Dreas

Re: pyzor reporting failing since change to new server

[Mark F. <mar...@na...>]

On Fri, 2009-05-01 at 09:16 +0200, Andreas Fuchs wrote:
> Hi
> 
> Im testing with the following test (from 
> http://wiki.apache.org/spamassassin/UsingPyzor):
> 
> echo "test" | spamassassin -D pyzor 2>&1 | less
> 
> and get the following output:
> 
> [935] dbg: pyzor: network tests on, attempting Pyzor
> [935] dbg: pyzor: pyzor is available: /usr/local/bin/pyzor
> [935] dbg: pyzor: opening pipe: /usr/local/bin/pyzor check < 
> /tmp/.spamassassin935TAIZ9Ttmp
> [935] dbg: pyzor: [947] finished: exit=0x0100
> [935] dbg: pyzor: got response: Traceback (most recent call last):\n 
> File "/usr/local/bin/pyzor", l
> ine 4, in ?\n pyzor.client.run()\n File 
> "/usr/local/lib/python2.4/site-packages/pyzor/client.py", l
> ine 934, in run\n ExecCall().run()\n File 
> "/usr/local/lib/python2.4/site-packages/pyzor/client.py",
>  line 188, in run\n if not apply(dispatch, (self, args)):\n File 
> "/usr/local/lib/python2.4/site-pac
> kages/pyzor/client.py", line 264, in check\n response = 
> runner.run(server, (digest, server))\n File
>  "/usr/local/lib/python2.4/site-packages/pyzor/client.py", line 725, in 
> run\n response = apply(self
> .routine, varargs, kwargs)\n File 
> "/usr/local/lib/python2.4/site-packages/pyzor/client.py", line 57
> , in check\n msg = CheckRequest(digest)\n File 
> "/usr/local/lib/python2.4/site-packages/pyzor/__init
> __.py", line 381, in __init__\n typecheck(digest, str)\n File 
> "/usr/local/lib/python2.4/site-packag
> es/pyzor/__init__.py", line 494, in typecheck\n raise TypeError\nTypeError
> [935] warn: pyzor: check failed: internal error
> 
> 
> Is there something wrong or is it cause i'm not testing with a valid 
> email? 

No, the test should work as shown.  I would suggest checking that you
are configured to communicate with public.pyzor.com.  For me that is set
in /etc/spamassassin/servers but it looks like you may have compiled
your install from source so I'm not sure where that setting might be for
you, sorry.

> How can i test with a valid email, as i'm in a maildir 
> environment i'm not shure how to save a single mail in the correct 
> format in a file? Or what else could be wrong?

With maildir each email is a separate file, usually ~/.maildir/ or
~/Maildir/, or do you mean mbox which is a single file for the entire
mailbox?

Thanks,

--
  Mark Fisher

Re: pyzor reporting failing since change to new server

[Mark F. <mar...@na...>]

On Thu, 2009-04-30 at 22:21 +0100, Dave Walker wrote:
> Tony Meyer wrote:  
> >
> > Thanks Mark, Dave & Bobby, and many apologies for the inconvenience.
> >
> > I've updated the test script to test "report" as well, and fixed the
> > error.  It works fine for me now, but please let me know if you have
> > any more issues and I'll fix them ASAP (although I'm in UTC+1200, so
> > there may be some delay).
> >
> > Thanks,
> > Tony
> >
> >   
> <SNIP>
> 
> 
> Hi Tony,
> 
> Many thanks, I can confirm it is now working.

It's working for me too now.

Thanks,

--
  Mark Fisher

Re: pyzor reporting failing since change to new server

[Andreas F. <fo...@tc...>]

Hi

Im testing with the following test (from 
http://wiki.apache.org/spamassassin/UsingPyzor):

echo "test" | spamassassin -D pyzor 2>&1 | less

and get the following output:

[935] dbg: pyzor: network tests on, attempting Pyzor
[935] dbg: pyzor: pyzor is available: /usr/local/bin/pyzor
[935] dbg: pyzor: opening pipe: /usr/local/bin/pyzor check < 
/tmp/.spamassassin935TAIZ9Ttmp
[935] dbg: pyzor: [947] finished: exit=0x0100
[935] dbg: pyzor: got response: Traceback (most recent call last):\n 
File "/usr/local/bin/pyzor", l
ine 4, in ?\n pyzor.client.run()\n File 
"/usr/local/lib/python2.4/site-packages/pyzor/client.py", l
ine 934, in run\n ExecCall().run()\n File 
"/usr/local/lib/python2.4/site-packages/pyzor/client.py",
 line 188, in run\n if not apply(dispatch, (self, args)):\n File 
"/usr/local/lib/python2.4/site-pac
kages/pyzor/client.py", line 264, in check\n response = 
runner.run(server, (digest, server))\n File
 "/usr/local/lib/python2.4/site-packages/pyzor/client.py", line 725, in 
run\n response = apply(self
.routine, varargs, kwargs)\n File 
"/usr/local/lib/python2.4/site-packages/pyzor/client.py", line 57
, in check\n msg = CheckRequest(digest)\n File 
"/usr/local/lib/python2.4/site-packages/pyzor/__init
__.py", line 381, in __init__\n typecheck(digest, str)\n File 
"/usr/local/lib/python2.4/site-packag
es/pyzor/__init__.py", line 494, in typecheck\n raise TypeError\nTypeError
[935] warn: pyzor: check failed: internal error


Is there something wrong or is it cause i'm not testing with a valid 
email? How can i test with a valid email, as i'm in a maildir 
environment i'm not shure how to save a single mail in the correct 
format in a file? Or what else could be wrong?

thanks
Andi

Re: pyzor reporting failing since change to new server

[Dave W. <Dav...@ub...>]

Tony Meyer wrote:
>> Since the move to the new pyzor server (at least, these errors started
>> happening on the 28th April) my script to pick mail from the Spam IMAP
>> folder and report & delete has began to report errors.
>>     
>
> Thanks Mark, Dave & Bobby, and many apologies for the inconvenience.
>
> I've updated the test script to test "report" as well, and fixed the
> error.  It works fine for me now, but please let me know if you have
> any more issues and I'll fix them ASAP (although I'm in UTC+1200, so
> there may be some delay).
>
> Thanks,
> Tony
>
>   
<SNIP>


Hi Tony,

Many thanks, I can confirm it is now working.

Kind Regards,
Dave Walker