Bug 4428 - extremely long subject breaking subject re_write
Summary: extremely long subject breaking subject re_write
Status: RESOLVED INVALID
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamc/spamd (show other bugs)
Version: 3.0.4
Hardware: PC Linux
: P5 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-24 08:44 UTC by Clay Campbell
Modified: 2005-06-26 05:00 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
NDR and spamassassin logs text/plain None Clay Campbell [NoCLA]
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Clay Campbell 2005-06-24 08:44:17 UTC 
I've seen this type of spam cause a non-delivery twice now, so I know its not a
fluke.  The message is marked spam, but the re_write is botched because of the
subject header length ( i think ? )

I'll be pasting in some attachments to this bug, that will clear this terribly
vague desc. up a bit
Comment 1 Clay Campbell 2005-06-24 08:53:29 UTC 
Created attachment 2955 [details]
NDR and spamassassin logs

Thanks SpamAssassins
Comment 2 Michael Parker 2005-06-24 09:03:44 UTC 
Subject: Re:  extremely long subject breaking subject re_write

Perhaps I'm missing something.

It looks like SpamAssassin handled this message just fine and you
Exchange server just rejected it.  The rejection appears to have the
subject rewritten and the log shows that it was processed, with no errors.

Do you have the whole message and output from spamassassin -D <
themsg.txt that shows this failure?

Michael
Comment 3 Clay Campbell 2005-06-24 09:18:20 UTC 
Michael believes Exchange rejected this message, and SpamAssassin handled it
properly.  I'm sure he is correct.  Trying to track down the reason for the
rejection now.  

Looking here too

http://www.microsoft.com/technet/prodtechnol/exchange/guides/E2k3SecHardGuide/8dbcf27a-d5f8-4340-a3fc-c62f2151eb80.mspx

Sorry for the false alarm
Comment 4 Michael Parker 2005-06-24 11:55:15 UTC 
Looks like it's something with Exchange
Comment 5 Clay Campbell 2005-06-26 10:08:00 UTC 
I hoped SpamAssassin would "handle" this email so Exchange would accept it, and
deliver it as Spam like normal.  Is there anything in the works to truncate
Subject headers, or deal with too many nested attachments.  If this
functionality already exists I'll accept a RTFM 

Flame on, and again thanks for your excellent work,

C
Comment 6 Justin Mason 2005-06-26 13:00:01 UTC 
SA never modifies the formatting of a message, apart from adding its own headers
and possibly creating a new MIME structure to "defang" it if report_safe is on.
 so cutting down long headers is something we cannot do, since that would result
in loss of data on other platforms.

If this modification of the message is required to deal with a platform-specific
issue, it makes a lot more sense for the platform-specific glue code that's
calling SA to do that.

in particular, this would be quite a bad thing to do on platforms where long
subject lines are not an issue (like any of the UNIX mtas).