Upgrade from 2.64 to 3.0.3

[Mick Szucs <mi...@magma.ca>]

Hello,

Two questions that I didn't find an answer to while hunting through the 
archives.

1)  Is there a replacement for the defang_mime configuration option from 
2.x in the 3.x series?

2)  Possibly not related to the upgrade specifically, I'm getting the 
following error from Pyzor 0.4.0:

spamd[877]: debug: Pyzor: couldn't grok response "Traceback (most recent 
call last):"

but when I run:

# pyzor check < spammail
66.250.40.33:24441      (200, 'OK')     0       0

Assistance would be greatly appreciated!

Regards,

Mick

Re: Upgrade from 2.64 to 3.0.3

[Matt Kettler <mk...@comcast.net>]

At 10:05 AM 5/11/2005, Mick Szucs wrote:
>Hello,
>
>Two questions that I didn't find an answer to while hunting through the 
>archives.
>
>1)  Is there a replacement for the defang_mime configuration option from 
>2.x in the 3.x series?

defang_mime isn't even supported by 2.60, so you're currently not using 
that option. It's just silently ignored as being leftover garbage from 
older versions.

Look at report_safe with option 2. This is supported in both 2.6x and 3.0.x


>2)  Possibly not related to the upgrade specifically, I'm getting the 
>following error from Pyzor 0.4.0:

I can't help you there, as I don't use pyzor.. maybe someone else can..

All I can tell you is that message indicates SA couldn't parse the response 
that pyzor gave it. 

Re: Upgrade from 2.64 to 3.0.3 - Pyzor issues resolved

[Mick Szucs <mi...@magma.ca>]

Mick Szucs wrote:

>> 2)  Possibly not related to the upgrade specifically, I'm getting the 
>> following error from Pyzor 0.4.0:
>>
>> spamd[877]: debug: Pyzor: couldn't grok response "Traceback (most 
>> recent call last):"
>
> I should add that when I run spammassassin -D --lint Pyzor works 
> fine.  The problem seems to be specifically when its called from 
> spamc/spamd.

Pyzor is happier now that I've specified -H /var/spool/spamassassin in 
my options to spamd. 

Running spamassassin -D --lint as the user it created .pyzor directory 
in the home directory. 

Seems that it doesn't get a $HOME variable when called from spamd (spamc 
-u.)

Forced one and all is well.

Mick

Re: Upgrade from 2.64 to 3.0.3

[Mick Szucs <mi...@magma.ca>]

Mick Szucs wrote:

> 2)  Possibly not related to the upgrade specifically, I'm getting the 
> following error from Pyzor 0.4.0:
>
> spamd[877]: debug: Pyzor: couldn't grok response "Traceback (most 
> recent call last):"

I should add that when I run spammassassin -D --lint Pyzor works fine.  
The problem seems to be specifically when its called from spamc/spamd.

Thanks in advance.

Mick