
scheidell at secnap
Sep 27, 2009, 6:39 PM
Post #3 of 6
(475 views)
Permalink
|
MySQL Student wrote: > Hi, > > I posted bug 6198 a few weeks ago, and there have been no comments or > fixes on it in two weeks, and I'm unsure what to do next. It's either > not a bug and I'm doing something wrong or it's not significant enough > to bother with the focus on v3.3. > > Thought someone might have some ideas here? I'm using perl-5.6. Anyone > else using perl-5.6 with the sought rules? > Can't use \x{} without 'use utf8' declaration comments here: <http://www.perlmonks.org/index.pl?node_id=424745> suggest moving to perl 5.8x since it does a better job of unicode. so, don't use perl 5.6, with is not supportable anymore, go to 5.10. > > [13204] dbg: config: read file /var/lib/spamassassin/3.002005/sought_rules_yerp_ > org/20_sought.cf > [13204] warn: config: invalid regexp for rule __SEEK_D52BRW: / Don\'t want to > lose your potential of a lover\? Lucky you are, in 21th century all bed-related > male problems can be solved by the powerful remedy, the all-mighty blue caplet\! > This solution will give you the right support for 50\(\!\) hours\. Rock-like and > ready to go\. more\x{bb}/: / Don\'t want to lose your potential of a lover\? > Lucky you are, in 21th century all bed-related male problems can be solved by /: > Can't use \x{} without 'use utf8' declaration > > Maybe it's a perl module that's incompatible? > > Ideas greatly appreciated. > Thanks, > Alex > _________________________________________________________________________ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.spammertrap.com _________________________________________________________________________
|