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
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
Henry Kwan wrote:
Doc Schneider wrote:
Not sure how you're using SA but I commented out every reference to
CIALIS2 and just committed 1.00.11 so should be available within the hour.
Also running CentOS 4.4 you know you can upgrade to perl 5.8.8 by doing
a 'yum --enablerepo=centosplus update
Doc Schneider wrote:
I just now committed more fixes for 70_sare_obfu.cf, obfu0 and obfu1.
These should be available within the hour.
Please folks if you have a problem with a rule set from SARE please let
us know what rule it is and what rule set it is in.
Hi Doc,
I just updated my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henry Kwan wrote:
Doc Schneider wrote:
I just now committed more fixes for 70_sare_obfu.cf, obfu0 and obfu1.
These should be available within the hour.
Please folks if you have a problem with a rule set from SARE please let
us know what rule
Doc Schneider wrote:
Not sure how you're using SA but I commented out every reference to
CIALIS2 and just committed 1.00.11 so should be available within the hour.
Also running CentOS 4.4 you know you can upgrade to perl 5.8.8 by doing
a 'yum --enablerepo=centosplus update perl' as
Loren Wilton lwilton at 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_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
-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 committed
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
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
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
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 byte
13 matches
Mail list logo
