Upgrade from 2.64 to 3.0.3

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: spam

Re: Upgrade from 2.64 to 3.0.3

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

Re: Upgrade from 2.64 to 3.0.3 - Pyzor issues resolved

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

SA 3.0.3 SURBL problem

Hello, SpamAssassin 3.0.3 on Fedora Core 2. I'm trying to set up SURBL from the instructions at www.surbl.org I've added: urirhssub URIBL_JP_SURBL multi.surbl.org.A 64 body URIBL_JP_SURBL eval:check_uridnsbl('URIBL_JP_SURBL') describe URIBL_JP_SURBL Has URI in JP at http://www.su

Re: SA 3.0.3 SURBL problem - resolved

Mick Szucs wrote: SpamAssassin 3.0.3 on Fedora Core 2. I'm trying to set up SURBL from the instructions at www.surbl.org Thank you to Martin Hepworth who pointed out that the plugin needs to be loaded via /etc/mail/spamassassin/init.pre: $ cat /etc/mail/spamassassin/init.pre # URIDNSBL -

SpamAssassin 3.0.3 errors - connect(AF_INET) to spamd at 127.0.0.1 failed

I'm running spamassassin 3.0.3 as a "proxy" on three mail servers. This morning at 2am one of the three (but not the other two) started spewing a lot of spamc[8000]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1 of 3) and did not identify any messages as spam until a user compl

SpamAssassin 3.0.3 errors - connect(AF_INET) to spamd at 127.0.0.1 failed - attempt 2

I sent this in on Friday last week and didn't attract any responses. Any insight would be appreciated. I've seen this behaviour once since then, despite my cronjob restarting spamd every 4 hours. Should I just open a bug report? I'm running spamassassin 3.0.3 as a "proxy" on three mail ser

Re: setup spamassassin on Fedora 2

Kenneth Porter wrote: website, http://www.firstpr.com.au/web-mail/Postfix-SA-Anomy-Maildrop/ I'm setting up SpamAssassin by following the instructions on this You're using FC2, which is RPM-based, so use the SpamAssassin RPM to ins

Good way to get spammed?

I'm trying to get some spam delivered to my filter boxes so I can gauge their effectiveness on a day to day basis. Though it seems that I've got no trouble getting spam I don't want, I'm not having a lot of luck getting spam now that I do want it. Ideas, anyone? Spammer bait? Thanks, Mick