On Mon, 2008-02-18 at 09:36 +1300, Michael Hutchinson wrote:
> > > We don't want to "only allow" the English locale, because we (here at
> > > my work) do not want our international clients (non Russian) to be
> > > denied email service.
> >
> > ok_locales en ja ko th zh
> >
> > This will allow
Hmm, let me see. I use the below in user_prefs. Hope that helps.
header J_CHSET3 Subject:raw =~
/\s=\?(windows-(125[0125]|874)|koi8-r|iso-8859-[28])\?/i
score J_CHSET3 5
ifplugin Mail::SpamAssassin::Plugin::TextCat
#ok_languages en zh.big5
#http://issues.apache.org/SpamAssassin/show_bug.cgi?id=569
> -Original Message-
> For the most part you can match any character by the appearance of the
> character. Any character with special meaning needs to be escaped in
some
> way. The easiest way is usually with a backslash, but in some cases
you
> can
> also do it by making it a member of
-Original Message-
> > We don't want to "only allow" the English locale, because we (here
at
> > my work) do not want our international clients (non Russian) to be
> > denied email service.
>
> ok_locales en ja ko th zh
>
> This will allow anything but Cyrillic char sets. Please note tha
On Fri, 2008-02-15 at 11:49 -0500, Rosenbaum, Larry M. wrote:
> > From: Karsten Bräckelmann [mailto:[EMAIL PROTECTED]
> >
> > I've pointed it out before. Just use ok_locales, which is all about
> > these char sets. No REs, almost no thinking required, no headache. A
> > single line, and you're done
On Sat, 2008-02-16 at 04:26 +0800, [EMAIL PROTECTED] wrote:
> KB> If you want to trigger on Russian only, list all but ru.
> What if to catch Ms. Ba'loney Margar'ine, airport security had to keep a
> current list of all the other people in the world. So this is the
> wrong approach, as we've been
KB> If you want to trigger on Russian only, list all but ru.
What if to catch Ms. Ba'loney Margar'ine, airport security had to keep a
current list of all the other people in the world. So this is the
wrong approach, as we've been thru before. OK, bye.
On Fri, 2008-02-15 at 11:04 -0800, Paul Douglas Franklin wrote:
> I believe that what you are asking for is
> meta RUSSIAN_AND_BADTEXT (CHARSET_FARAWAY && __OTHER_RULE)
> That requires first that you have set up ok_locales.
If you have TextCat enabled, then the X-Language: meta header will be
add
I believe that what you are asking for is
meta RUSSIAN_AND_BADTEXT (CHARSET_FARAWAY && __OTHER_RULE)
That requires first that you have set up ok_locales.
--Paul
Rosenbaum, Larry M. wrote:
From: Karsten Bräckelmann [mailto:[EMAIL PROTECTED]
I've pointed it out before. Just use ok_locales, which
> From: Karsten Bräckelmann [mailto:[EMAIL PROTECTED]
>
> I've pointed it out before. Just use ok_locales, which is all about
> these char sets. No REs, almost no thinking required, no headache. A
> single line, and you're done.
What's the best way to test the character set for use in a meta rule?
On Fri, 2008-02-15 at 17:10 +1300, Michael Hutchinson wrote:
> > From: Karsten Bräckelmann [mailto:[EMAIL PROTECTED]
> > Why are you guys now trying to re-invent the wheel in the special case
> > of a gray asphalt street? What about a dirt track, grass, and anything
> > else a wheel works on?
> >
Ok fair enough. I've noticed that having the \ doesn't hurt for a dash.
Now what about matching a question mark and an equals sign?
If you read perlre closely you will find it says that it never hurts to put
a backslash before a special character that you want to match as a
character. So this
> -Original Message-
> From: Karsten Bräckelmann [mailto:[EMAIL PROTECTED]
> Sent: Friday, 15 February 2008 3:43 p.m.
> To: users@spamassassin.apache.org
> Subject: RE: Rule for Russian character sets
>
> On Fri, 2008-02-15 at 12:19 +1300, Michael Hutchinson wrote:
&g
On Fri, 2008-02-15 at 12:19 +1300, Michael Hutchinson wrote:
[...]
> Does anyone have suggestions for matching question marks and equals
> signs in one line? I would like to match everything exactly between the
> double quotes:
Apart from neither equal nor minus being any special in an RE (outside
> -Original Message-
> From: John Hardin [mailto:[EMAIL PROTECTED]
> Sent: Friday, 15 February 2008 3:07 p.m.
> To: Michael Hutchinson
> Subject: RE: Rule for Russian character sets
>
> On Fri, 15 Feb 2008, Michael Hutchinson wrote:
>
> > Now what about m
-Original Message-
From: John Hardin [mailto:[EMAIL PROTECTED]
Sent: Friday, 15 February 2008 3:07 p.m.
To: Michael Hutchinson
Subject: RE: Rule for Russian character sets
On Fri, 15 Feb 2008, Michael Hutchinson wrote:
> Now what about matching a question mark and an equals sign?
> -Original Message-
> From: John Hardin [mailto:[EMAIL PROTECTED]
> Sent: Friday, 15 February 2008 2:19 p.m.
> To: Michael Hutchinson
> Cc: users@spamassassin.apache.org
> Subject: RE: Rule for Russian character sets
>
> On Fri, 15 Feb 2008, Michael Hutchinson
On Fri, 15 Feb 2008, Michael Hutchinson wrote:
Are we not meant to delimit characters like a minus sign?
Ex:
header SUBJ_RUSS_CHAR Subject:raw =~ /koi8\-r/i
Only where they have special meaning, and a dash is only "special" in a
character set, e.g. [A-Z]. I have found the s
> -Original Message-
> > > We're suddenly getting a ton of spam with koi8-r encoding...I
tried to
> > > do a custom rule for it like this:
> > >
> > > header SUBJ_RUSS_CHAR Subject =~/koi8-r/i
> > > describe SUBJ_RUSS_CHAR has Russian char encoding
> > > score SUBJ_RUSS_C
On Thu, 14 Feb 2008, Per Jessen wrote:
> [EMAIL PROTECTED] wrote:
>
> >
> > We're suddenly getting a ton of spam with koi8-r encoding...I tried to
> > do a custom rule for it like this:
> >
> > header SUBJ_RUSS_CHAR Subject =~/koi8-r/i
> > describe SUBJ_RUSS_CHAR has Russian char
On Thu, 2008-02-14 at 10:17 -0500, [EMAIL PROTECTED] wrote:
> We're suddenly getting a ton of spam with koi8-r encoding...I tried to do
> a custom rule for it like this:
>
> header SUBJ_RUSS_CHAR Subject =~/koi8-r/i
> describe SUBJ_RUSS_CHAR has Russian char encoding
> score SUBJ
[EMAIL PROTECTED] wrote:
>
> We're suddenly getting a ton of spam with koi8-r encoding...I tried to
> do a custom rule for it like this:
>
> header SUBJ_RUSS_CHAR Subject =~/koi8-r/i
> describe SUBJ_RUSS_CHAR has Russian char encoding
> score SUBJ_RUSS_CHAR3.5
>
>
We're suddenly getting a ton of spam with koi8-r encoding...I tried to do
a custom rule for it like this:
header SUBJ_RUSS_CHAR Subject =~/koi8-r/i
describe SUBJ_RUSS_CHAR has Russian char encoding
score SUBJ_RUSS_CHAR3.5
The short headers for these spams look like
23 matches
Mail list logo
