0.2 NO_REAL_NAME From: does not include a real name
0.0 HTML_MESSAGE BODY: HTML included in message
0.5 HTML_20_30 BODY: Message is 20% to 30% HTML
1.4 INVALID_MSGID Message-Id is not valid, according to RFC
2822
from where did u take these msgs?
0.2 - it doesnt recognize my name as a real name?
0.0 - is it a problem?
0.5 - so?
1.4 - i will check this, 10x
________________________________
On 17/05/06, Amos <[EMAIL PROTECTED]> wrote:
yes, i mean synapse :)
and im talking about everythig
subject, from, part filesnames
all the string stuff, should be widestring in order to support
unicode
You don't need widestring to support unicode. For emails, Subject, From
etc. can all be in any character set you want, as long as it is 8 bit
safe. If it's unicode you want then that means either UTF-7 or UTF-8, or
double byte character sets encoded in some other way;
Base64/Quoted-Printable.
The HTML part of the message you sent was in unicode (UTF-8), though
strangely the text part was 'ISO-8859-1'.
BTW: You should make your mail client more spamassasin friendly, it as
tagged with the following:
0.2 NO_REAL_NAME From: does not include a real name
0.0 HTML_MESSAGE BODY: HTML included in message
0.5 HTML_20_30 BODY: Message is 20% to 30% HTML
1.4 INVALID_MSGID Message-Id is not valid, according to RFC
2822
נשלח ע"י דואר נענע
http://mail.nana.co.il
