Kelson wrote on Fri, 12 May 2006 14:23:55 -0700:
I count two: The ü in für and the ´ in MODEL´S, which is different from
the ASCII single quote/apostrophe: '
Ah, you are right, I missed the ü, it's too natural for me.
Nevertheless too many implies a bit more than *two* for me. I can't
Theo Van Dinter wrote on Thu, 11 May 2006 13:49:11 -0400:
fwiw, the 8-bit characters ought to be encoded in base64 or quoted-printable.
then the rule wouldn't hit.
I just found the same problem here with a whole bunch of messages coming from
the same source. It seems the rule hits on *one*
Kai Schaetzl wrote:
The subject line hitting in the case of our customer was:
Bewerbung für INS-2006-05-4, MODEL´S GESUCHT!!!
I can identify only one character that is outside the ASCII range.
I count two: The ü in für and the ´ in MODEL´S, which is different from
the ASCII single
From: Kai Schaetzl [EMAIL PROTECTED]
Theo Van Dinter wrote on Thu, 11 May 2006 13:49:11 -0400:
fwiw, the 8-bit characters ought to be encoded in base64 or quoted-printable.
then the rule wouldn't hit.
I just found the same problem here with a whole bunch of messages coming from
the same
* 4.3 SUBJ_ILLEGAL_CHARS Subject: has too many raw illegal characters
* 0.0 DK_SIGNED Domain Keys: message has an unverified signature
* -0.0 DK_VERIFIED Domain Keys: signature passes verification
* 0.5 HTML_40_50 BODY: Message is 40% to 50% HTML
* 0.0 HTML_MESSAGE
On Thu, May 11, 2006 at 07:47:15PM +0200, Keith Dunnett wrote:
I've recently had a couple of false positives caused by this rule, and think
it may be scored too highly for a single check. The e-mails in question were
in Spanish, and the Spanish word for linguistics has two accented characters
Matt Kettler написа:
Note that SUBJ_ILLEGAL_CHARS is NOT concerned with what language or character
set is used. It is concerned about it not being encoded properly.
Per RFC specifications, all characters in email-headers that aren't in the
normal ascii ranges must be QP encoded. This rule
Can You please point which RFC is this and what exactly 'QP encoding'
means.
Someone else can doubtless point to the RFC, but as an example, your name in
the From address is encoded in Quoted Printable encoding. I've added some
spaces to it below so that your mail client doesn't turn it back
Милен Панков wrote:
Matt Kettler написа:
Note that SUBJ_ILLEGAL_CHARS is NOT concerned with what language or
character
set is used. It is concerned about it not being encoded properly.
Per RFC specifications, all characters in email-headers that aren't in
the
normal ascii ranges must be QP
To: users@spamassassin.apache.org
Cc: Matt Kettler
Subject: Re: SUBJ_ILLEGAL_CHARS
Matt Kettler написа:
Note that SUBJ_ILLEGAL_CHARS is NOT concerned with what language or
character set is used. It is concerned about it not being
encoded properly.
Per RFC specifications, all characters
: SUBJ_ILLEGAL_CHARS
Милен Панков wrote:
Matt Kettler написа:
Note that SUBJ_ILLEGAL_CHARS is NOT concerned with what
language or
character set is used. It is concerned about it not being encoded
properly.
Per RFC specifications, all characters in email-headers
that aren't
in the normal
On Wed, Mar 15, 2006 at 03:29:45PM -, Randal, Phil wrote:
Can You please point which RFC is this and what exactly 'QP
encoding' means.
http://www.faqs.org/rfcs/rfc2822.html
Refer to Section 3.2.2 for information on quoted-pairs.
QP in this case does not mean quoted pairs, it means
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philip Prindeville wrote:
[snip]
I mean it's not X.400, right? ;-)
Thank the Gods...
C.
- --
Craig McLeanhttp://fukka.co.uk
[EMAIL PROTECTED] Where the fun never starts
Powered by FreeBSD, and GIN!
-BEGIN PGP
Hi to all,
I'm using spamassassin for years without any serious problems.
Except for one. My users write messages mostly in bulgarian and the
'SUBJ_ILLEGAL_CHARS' rule very often stops good mail.
I have put in my local.cf the line 'ok_languages bg en', but it doesn't fix
the problem. For now I
and the
'SUBJ_ILLEGAL_CHARS' rule very often stops good mail.
I have put in my local.cf the line 'ok_languages bg en', but it doesn't
fix the problem.
No, if anything that will make your problem WORSE. The default here is all. By
declaring an ok_languages you're limiting the number of acceptable languages.
Also note
messages mostly in bulgarian and the
'SUBJ_ILLEGAL_CHARS' rule very often stops good mail.
I have put in my local.cf the line 'ok_languages bg en', but it doesn't
fix the problem.
No, if anything that will make your problem WORSE. The default here is all. By
declaring an ok_languages you're limiting
score SUBJ_ILLEGAL_CHARS 0 to your local.cf.
Well this happens mostly when we receive mail from some webmails for
example Yahoo, so I'm stuck with the second option, which I'm already using.
Thanks,
Milen
It's an issue, to be sure. And people need to be edumacated.
I recently pointed
17 matches
Mail list logo
