On Friday 25 May 2007 7:06 pm, Henry Kwan wrote: > Just updated to 3.20 this week and because everything seem to be working > fine, I didn't notice my log files getting bloated (up to 8GB!) by errors > like this: > > Malformed UTF-8 character (unexpected non-continuation byte 0x00, > immediately after start byte 0xd > 2) in pattern match (m//) at /etc/mail/spamassassin/70_sare_adult.cf, rule > SARE_OBFUFCK1, line 1. > > After googling, it seems the common answers are to either upgrade to Perl > 5.88 (I'm running 5.85) or stop using the SARE rules. Is there a third > choice? Perhaps an uncoming patch for 3.20? > > Thanks.
The below was posted back on 9 May -------------------------------------------------------------------- Thanks for straightening me out on that Vincent. Folks - for completeness here are some instructions for the WORKAROUND. Locate your Message.pm module and edit the section in the begining as indicated below. I have been running this now for a couple of hours with no adverse affects (that I can see at the moment). PS Thanks [EMAIL PROTECTED] for your help. I'm up and running without any further errors. ----- Forwarded Message ----- > Vincent, > > Where in the Message.pm module do I but "use bytes"? Right here (below) > and do I just add it below the warnings line with a ";" ending it? Yes, you are right, after "use warnings;". I ran SA3.2 on my site with "use bytes;" added, no problem so far. But it seems SA developers did not mention this, they might have their reasons (break normalize_charset for one reason). > ---paste--- > package Mail::SpamAssassin::Message; > > use strict; > use warnings; > > use Mail::SpamAssassin; > use Mail::SpamAssassin::Message::Node; > use Mail::SpamAssassin::Message::Metadata; > use Mail::SpamAssassin::Constants qw(:sa); > use Mail::SpamAssassin::Logger; > > use vars qw(@ISA); > ---end paste--- > > ================================= -- Chris KeyID 0xE372A7DA98E6705C
pgpmP4edgcSFc.pgp
Description: PGP signature
