On Tue, 1 Jun 2010, Chris Conn wrote:
John Hardin wrote:
On Tue, 1 Jun 2010, Chris Conn wrote:
> I upgraded to SA 3.3.1 on a CentOS system using Perl 5.8.5 and I
> occasionally get this error;
>
> Malformed UTF-8 character (unexpected non-continuation byte 0x00,
> im
John Hardin wrote:
On Tue, 1 Jun 2010, Chris Conn wrote:
I upgraded to SA 3.3.1 on a CentOS system using Perl 5.8.5 and I
occasionally get this error;
Malformed UTF-8 character (unexpected non-continuation byte 0x00,
immediately after start byte 0xc3) in pattern match (m//) at
/var/lib
On Tue, 2010-06-01 at 12:31 -0400, Michael Scheidell wrote:
> I believe the minimum recommended is 5.8.8 with 5.10.1 STRONGLY
> recommended.
>
> there was even talk on this list of disabling anything user 5.8.8, or
> strongly warning against it.
>
> (and I think there was some talk about requi
On Tue, 1 Jun 2010, Chris Conn wrote:
I upgraded to SA 3.3.1 on a CentOS system using Perl 5.8.5 and I occasionally
get this error;
Malformed UTF-8 character (unexpected non-continuation byte 0x00, immediately
after start byte 0xc3) in pattern match (m//) at
/var/lib/spamassassin/3.003001
On 6/1/10 11:56 AM, Chris Conn wrote:
Hello,
I upgraded to SA 3.3.1 on a CentOS system using Perl 5.8.5 and I
occasionally get this error;
I believe the minimum recommended is 5.8.8 with 5.10.1 STRONGLY
recommended.
there was even talk on this list of disabling anything user 5.8.8, or
st
On Tue, 2010-06-01 at 11:56 -0400, Chris Conn wrote:
> I upgraded to SA 3.3.1 on a CentOS system using Perl 5.8.5 and I
> occasionally get this error;
> I built a rpm using rpmbuild on the system in question, is my
> installation broken? I have found similar instances in previous versions
>
>
Hello,
I upgraded to SA 3.3.1 on a CentOS system using Perl 5.8.5 and I
occasionally get this error;
Malformed UTF-8 character (unexpected non-continuation byte 0x00,
immediately after start byte 0xc3) in pattern match (m//) at
/var/lib/spamassassin/3.003001/updates_spamassassin_org
Hi! Mark,
Many thanks for your reply.
I also have similar WARN error
Jan 9 09:20:02 smtpext2 amavis[20636]: (20636-16) _WARN: Malformed
UTF-8 character (unexpected continuation byte 0xba, with no preceding
start byte) in pattern match (m//) at
/usr/lib/perl5/site_perl/5.8.5/Mail
Mark Martinec wrote:
Our log file contains many:
amavis[19738]: (19738-05) _WARN: Malformed UTF-8 character (unexpected
continuation byte 0x8e, with no preceding start byte) in pattern match
(m//) at
/var/lib/spamassassin/3.002005/70_sare_specific_cf_sare_sa-update_dostech_n
et/200605280300
> academic server.
>
> amavisd-new-2.6.2 (20081215), Unicode aware, LANG="fr"
> with spamassassin 3.2.5
>
> Our log file contains many:
> amavis[19738]: (19738-05) _WARN: Malformed UTF-8 character (unexpected
> continuation byte 0x8e, with no preceding start byte)
avisd-new-2.6.2 (20081215), Unicode aware, LANG="fr"
with spamassassin 3.2.5
Our log file contains many:
amavis[19738]: (19738-05) _WARN: Malformed UTF-8 character (unexpected
continuation byte 0x8e, with no preceding start byte) in pattern match
(m//) at
/var/lib/spamas
Got about 110k worth of this in my hourly syslog snip today:
Sep 8 05:47:06 localhost spamd[13261]: Malformed UTF-8 character (unexpected
continuation byte 0x8e, with no preceding start byte) in pattern match (m//)
at
/var/lib/spamassassin/3.002005/70_sare_specific_cf_sare_sa
> running on Perl version 5.8.5
upgrade, and let us know problem later
if i remember unicode was a problem before 5.8.8
While investigating why a couple of emails took over 500 seconds to
scan, I found a bunch of these errors in the log file:
spamd[7586]: Malformed UTF-8 character (unexpected continuation byte 0x8e,
with no preceding start byte) in pattern match (m//) at
/var/lib/spamassassin/3.002004
lus update perl' as this issue isn't a
problem with 5.8.8
Hi Doc,
I'll look into updating to Perl 5.8.8 then.
Also, it looks like the ruleset still has a couple of gremlins. Still
getting these on 01.00.11 (2007-05-29).
"spamd[17302]: Malformed UTF-8 character (un
ablerepo=centosplus update perl' as this issue isn't a
> problem with 5.8.8
>
>
Hi Doc,
I'll look into updating to Perl 5.8.8 then.
Also, it looks like the ruleset still has a couple of gremlins. Still
getting these on 01.00.11 (2007-05-29).
"spamd[17302]: Malf
rom SARE please let
>> us know what rule it is and what rule set it is in.
>>
>
> Hi Doc,
>
> I just updated my 70_sare_obfu.cf to 01.00.10 (2007-05-28) and tried 3.20
> with it again but almost immediately, I got these errors:
>
> Malformed UTF-8 character (u
gt;
Hi Doc,
I just updated my 70_sare_obfu.cf to 01.00.10 (2007-05-28) and tried 3.20
with it again but almost immediately, I got these errors:
Malformed UTF-8 character (unexpected non-continuation byte 0x00,
immediately after start byte 0xc4) in pattern match (m//) at
/etc/mail/spamassassin/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Loren Wilton wrote:
>> (sare_obfu1.cf seems to have been updated though). Do you know if Doc
>> plans to
>> update sare_obfu.cf soon?
>
> He's working on it. Said it was a bit of a bear to fix up the regexes
> in it.
>
>Loren
>
I just now
(sare_obfu1.cf seems to have been updated though). Do you know if Doc
plans to
update sare_obfu.cf soon?
He's working on it. Said it was a bit of a bear to fix up the regexes in
it.
Loren
Loren Wilton earthlink.net> writes:
> Perhaps a third answer would be to get the latest versions of the rules
> files?
> Doc fixed those errors about 5-6 days ago.
Hmmm... Thanks for the heads up. I guess sare_adult.cf got updated after my
last RulesDuJour run. But it seems that sare_obfu.cf
At 17:06 25-05-2007, 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
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?
Perhaps a third answer would be to get the latest versions of the rules
files?
Doc fixed those errors a
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
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
Bayes ?
-Message d'origine-
De : Martin.Hepworth [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 16 mai 2007 11:38
À : Hamel Gilles - Brandt Appliances; users@spamassassin.apache.org
Objet : RE: Upgrade to 3.2.0 failed => Malformed UTF-8 character
@Bayes.pm line 362
Hi
Common prob
> -Original Message-
> From: Hamel Gilles - Brandt Appliances
> [mailto:[EMAIL PROTECTED]
> Sent: 16 May 2007 10:25
> To: users@spamassassin.apache.org
> Subject: Upgrade to 3.2.0 failed => Malformed UTF-8 character
@Bayes.pm
> line 362
>
> Hello,
>
> We ha
Hello,
We have upgraded from 3.1.7 to 3.2.0. Now we get a lot of errors like this :
May 16 10:45:01 mimedefang-multiplexor[22448]: Slave 2 stderr: art byte)
in substitution iterator at /u
sr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Bayes.pm line 362. Malformed
UTF-8 character
On Wed, May 9, 2007 6:20 pm, Jerry Durand wrote:
> I've been checking all the archives of this list as well as bugzilla and
> google searches, can't find anything about this. Obviously I'm looking in
> the wrong place.
Found it, Loren added an "s" to the file name, that's why I couldn't find it!
On Wed, May 9, 2007 5:10 pm, Loren Wilton wrote:
>> What do I put in the messages.pm and where do I put it?
>
> Its 'use bytes;' YOu'll have to search back in the archives for a message
> describing exactly where it goes.
>
> Note this isn't a FIX, this is a tempoary WORKAROUND.
>
I've been check
What do I put in the messages.pm and where do I put it?
Its 'use bytes;' YOu'll have to search back in the archives for a message
describing exactly where it goes.
Note this isn't a FIX, this is a tempoary WORKAROUND.
Loren
What do I put in the messages.pm and where do I put it?
Thanks.
=
Kevin W. Gagel
Network Administrator
Information Technology Services
(250) 562-2131 local 448
My Blog:
http://mail.cnc.bc.ca/blogs/gagel
-
Chris wrote:
Thanks Loren, I doubt then that this accounts for the strange sa-update run I
had this morning which I've posted the cron output here:
http://mediasafe.embarq.com/chris1948/Hosted/saupdate0507.tar.bz2
I don't see anything strange at all in that output.
Yesterdays update was a
On Monday 07 May 2007 8:51 pm, Loren Wilton wrote:
> > rule SARE_OBFUMONEY1, line 1.
> >
> > I saw the same thing earlier this weekend but passed it off to possibly
> > something I didn't have configured right.
>
> No. Its a combination of a perl bug and a change in SA to allow rules in
> other th
rule SARE_OBFUMONEY1, line 1.
I saw the same thing earlier this weekend but passed it off to possibly
something I didn't have configured right.
No. Its a combination of a perl bug and a change in SA to allow rules in
other than the ascii character set.
Previous versions of SA had 'use bytes
The entire error line reads:
Malformed UTF-8 character (unexpected non-continuation byte 0x00, immediately
after start byte 0xce) in pattern match (m//)
at
/var/lib/spamassassin/3.002000/72_sare_bml_post25x_cf_sare_sa-update_dostech_net/20050602.cf,
rule SARE_OBFUMONEY1, line 1.
I saw
36 matches
Mail list logo
