You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2007/01/26 00:59:24 UTC
[Bug 5310] New: X-Spam-Report broken in Evolution
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5310
Summary: X-Spam-Report broken in Evolution
Product: Spamassassin
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: spamassassin
AssignedTo: dev@spamassassin.apache.org
ReportedBy: raul@dias.com.br
Evolution (in any version), when dealing with headers with multiple lines,
rearrange the lines.
This has a terrible problem with SpamAssassin as it makes difficult to analise
the rules triggered by ham/spam.
For example, the header:
X-Spam-Report: * 4.2 bla bla blabla blabla bla
* -1.0 bla bla blabla blabla bla
* 3.1 foo fo ofoo bla bar bar bar
will be changed to something like:
X-Spam-Report: * 4.2 bla bla blabla blabla bla * -1.0
bla bla blabla blabla bla * 3.1 foo fo ofoo bla
bar bar bar
To make things even worse, evolution is not completly wrong in doing this. This
is not common, but it is not forbidden in the RFCs.
So, to solve this problem I have updated a patch to insert a new option to SA:
header_report_multiline
if set to 1 (defaults to 0), will insert each line of X-Spam-Report as a new
header, making it readable in clients such as evolution.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 5310] X-Spam-Report broken in Evolution
Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5310
------- Additional Comments From craig@microtron.org.uk 2007-10-28 01:55 -------
Created an attachment (id=4178)
--> (http://issues.apache.org/SpamAssassin/attachment.cgi?id=4178&action=view)
Preserve headers in evolution-data-server
This patch enables the PRESERVE_HEADERS option in camel/camel-mime-parser.c,
and fixes a bug in the end of headers detection that otherwise prevented this
option from working properly.
This tidies up the display of headers such as X-Spam-Report which are otherwise
difficult to read without the PRESERVE_HEADERS option enabled.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 5310] X-Spam-Report broken in Evolution
Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5310
craig@microtron.org.uk changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |craig@microtron.org.uk
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 5310] X-Spam-Report broken in Evolution
Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5310
------- Additional Comments From raul@dias.com.br 2007-01-25 16:01 -------
Created an attachment (id=3843)
--> (http://issues.apache.org/SpamAssassin/attachment.cgi?id=3843&action=view)
header_report_multiline option patch
This is the patch that inserts the option header_report_multiline for "broken"
MUAs.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 5310] X-Spam-Report broken in Evolution
Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5310
------- Additional Comments From craig@microtron.org.uk 2007-10-28 02:40 -------
This is actually caused by an issue within camel in evolution-data-server, not
spamassassin.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 5310] X-Spam-Report broken in Evolution
Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5310
raul@dias.com.br changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|unspecified |3.1.7
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.