Tickets :: [#10699] no subject displayed when viewing a mailman mailing list e-mail

6.0.0-beta1

7/7/25

Summary	no subject displayed when viewing a mailman mailing list e-mail
Queue	IMP
Queue Version	5.0.13
Type	Bug
State	Not A Bug
Priority	1. Low
Owners
Requester	lslawski (at) physnet (dot) uni-hamburg (dot) de
Created	11/01/2011 (4997 days ago)
Due
Updated	11/03/2011 (4995 days ago)
Assigned	11/01/2011 (4997 days ago)
Resolved	11/02/2011 (4996 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

11/03/2011 04:22:40 PM	lslawski (at) physnet (dot) uni-hamburg (dot) de	Comment #12	Reply to this comment
[Show Quoted Text - 11 lines][Hide Quoted Text] Never mind. This wasn't an issue with the Subject header. It is an issue with the X-Spam-Report: header. That header contains blank lines. The first blank line in a mail message is taken to be the separation between the headers and the message body. Since the subject line appears after the X-Spam-Report, it is not parsed as a header and therefore that message is correctly reported as having no Subject. There is no workaround for this - it is a broken RFC 822/2822/5322 message. And there can be no workaround, since the header/subject parsing is done on the IMAP server anyway. Dear horde developers, thank you very much for your help! Our workaround is to make exim not insert the X-Spam-Report unless the spamscore is very high. Probably this will be solved for us after updating to a more recent version of spamassasin.

11/02/2011 02:33:23 AM	Michael Slusarz	Comment #11 State ⇒ Not A Bug	Reply to this comment
Never mind. This wasn't an issue with the Subject header. It is an issue with the X-Spam-Report: header. That header contains blank lines. The first blank line in a mail message is taken to be the separation between the headers and the message body. Since the subject line appears after the X-Spam-Report, it is not parsed as a header and therefore that message is correctly reported as having no Subject. There is no workaround for this - it is a broken RFC 822/2822/5322 message. And there can be no workaround, since the header/subject parsing is done on the IMAP server anyway.

11/02/2011 12:05:12 AM	Michael Slusarz	Comment #10	Reply to this comment
Confirmed, though the message is broken. It contains non-ascii characters in the message header which is strictly forbidden. Not sure if we can work around this. This is the whole point of the 'default_msg_charset' preference.

11/01/2011 11:45:40 PM	Jan Schneider	Comment #9	Reply to this comment
Confirmed, though the message is broken. It contains non-ascii characters in the message header which is strictly forbidden. Not sure if we can work around this.

11/01/2011 11:41:22 PM	Jan Schneider	Deleted Original Message

11/01/2011 11:27:47 PM	lslawski (at) physnet (dot) uni-hamburg (dot) de	Comment #8 New Attachment: TEST1_ test Jan Schneider II.eml	Reply to this comment
That's a PDF file, not a message source. As I was only able to upload a single attachment I thought this might be more clearly. I will attach the message sources in the next two comments. This message did not show the subject. Sorry, caption problem... This one was alright.

11/01/2011 11:27:02 PM	lslawski (at) physnet (dot) uni-hamburg (dot) de	Comment #7 New Attachment: saved_message.eml	Reply to this comment
That's a PDF file, not a message source. As I was only able to upload a single attachment I thought this might be more clearly. I will attach the message sources in the next two comments. This message did not show the subject. Sorry, caption problem...

11/01/2011 11:26:23 PM	lslawski (at) physnet (dot) uni-hamburg (dot) de	Comment #6	Reply to this comment
That's a PDF file, not a message source. As I was only able to upload a single attachment I thought this might be more clearly. I will attach the message sources in the next two comments. This message did not show the subject.

11/01/2011 11:25:26 PM	lslawski (at) physnet (dot) uni-hamburg (dot) de	Comment #5	Reply to this comment
That's a PDF file, not a message source. As I was only able to upload a single attachment I thought this might be more clearly. I will attach the message sources in the next two comments.

11/01/2011 10:53:58 PM	Jan Schneider	Comment #4	Reply to this comment
That's a PDF file, not a message source.

11/01/2011 10:33:11 PM	lslawski (at) physnet (dot) uni-hamburg (dot) de	Comment #3 New Attachment: mailman_problem.pdf	Reply to this comment
I get tons of mailman messages and they all are fine. If you want you can provide an example message that triggers that behavior for you. Hallo Jan, I attached the source I took from Imp of a message in which the subject is missing and one which is displayed properly. I believe it must be some stupid configuration mistake I made. Thank you very much for your help!

11/01/2011 10:04:59 PM	Jan Schneider	Comment #2 State ⇒ Feedback	Reply to this comment
I get tons of mailman messages and they all are fine. If you want you can provide an example message that triggers that behavior for you.

11/01/2011 08:13:51 PM	lslawski (at) physnet (dot) uni-hamburg (dot) de	Comment #1 (Private) Priority ⇒ 1. Low State ⇒ Unconfirmed Patch ⇒ No Milestone ⇒ Queue ⇒ IMP Summary ⇒ no subject displayed when viewing a mailman mailing list e-mail Type ⇒ Bug
[Hidden]