To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=68098
User jobin changed the following:
What |Old value |New value
================================================================================
Status|STARTED |RESOLVED
--------------------------------------------------------------------------------
Resolution| |WONTFIX
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Wed Oct 11 04:10:23 -0700
2006 -------
I dont think this is something which we could much about have been reading the
RFC documents and feel what we are following is correct and exactly as stated in
RFC 2047
<snip>
The following are examples of message headers containing 'encoded-
word's:
From: =?US-ASCII?Q?Keith_Moore?= <moore@cs.utk.edu>
To: =?ISO-8859-1?Q?Keld_J=F8rn_Simonsen?= <[EMAIL PROTECTED]>
CC: =?ISO-8859-1?Q?Andr=E9?= Pirard <[EMAIL PROTECTED]>
Subject: =?ISO-8859-1?B?SWYgeW91IGNhbiByZWFkIHRoaXMgeW8=?=
=?ISO-8859-2?B?dSB1bmRlcnN0YW5kIHRoZSBleGFtcGxlLg==?=
Note: In the first 'encoded-word' of the Subject field above, the
last "=" at the end of the 'encoded-text' is necessary because each
'encoded-word' must be self-contained (the "=" character completes a
group of 4 base64 characters representing 2 octets). An additional
octet could have been encoded in the first 'encoded-word' (so that
the encoded-word would contain an exact multiple of 3 encoded
octets), except that the second 'encoded-word' uses a different
'charset' than the first one.
</snip>
Please have a look at this link for more details on this respect
http://aspn.activestate.com/ASPN/Mail/Message/spamassassin-users/3107435
Here is the details provided for an issue reported in the apache site for this
kind of problem and the workaround or suggestion provided .
http://www.mail-archive.com/dev@spamassassin.apache.org/msg15778.html
<snip>
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5026
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
------- Additional Comments From [EMAIL PROTECTED] 2006-08-04 17:34 -------
Hi,
Thanks for the ticket. What you're reporting is commonly referred to as a
"false positive" (aka: FP). The rule is actually doing the right thing -- the
subject does have two encodings in it, and so the rule is triggered.
It appears that this is more common now than it was before:
old: 1.047 1.4619 0.0792 0.949 0.58 0.89 SUBJECT_ENCODED_TWICE
new: 0.597 0.6926 0.1444 0.827 0.65 0.89 SUBJECT_ENCODED_TWICE
which basically means that the spam hits have decreased by ~50% while the ham
hits increased by ~50%. So the next time the scores are generated, I would
expect this rule's score to drop a bit. In the mean time, you can lower the
score on your installation as you see fit.
Hope this helps. :)
As for the ticket, since the rule is doing the right thing, I'm closing as WFM.
</snip>
I would like to close this issue as wontfix . Hence i am going ahead and closing
as the same . Please reopen if you feel otherwise .
Thanks
Jobin.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
