Tickets :: [#3510] Stripping attachments creates bare newlines again

6.0.0-beta1

7/26/25

Summary	Stripping attachments creates bare newlines again
Queue	IMP
Queue Version	HEAD
Type	Bug
State	Resolved
Priority	3. High
Owners	slusarz (at) horde (dot) org
Requester	jan (at) horde (dot) org
Created	02/20/2006 (7096 days ago)
Due
Updated	03/24/2006 (7064 days ago)
Assigned	03/23/2006 (7065 days ago)
Resolved	03/24/2006 (7064 days ago)
Github Issue Link
Github Pull Request
Milestone	4.1
Patch	No

03/24/2006 09:54:33 AM	Jan Schneider	State ⇒ Resolved

03/24/2006 09:54:12 AM	Jan Schneider	Comment #11	Reply to this comment
This fixed but broke something else. I'll create another ticket for that.

03/24/2006 04:40:40 AM	Michael Slusarz	Comment #10	Reply to this comment
How about this? http://lists.horde.org/archives/cvs/Week-of-Mon-20060320/056149.html

03/23/2006 10:45:42 AM	leena (dot) heino (at) uta (dot) fi	Comment #9	Reply to this comment
No, the same error message. This error message seems to happen because Imp H3 4.1 does not send headers with append command. It only sends the new body. 00000005 FETCH 733,734 (ENVELOPE BODY.PEEK[HEADER.FIELDS (Newsgroups Content-MD5 Content-Disposition Content-Language Content-Location Followup-To R eferences)] BODYSTRUCTURE INTERNALDATE RFC822.SIZE FLAGS) 00000006 FETCH 733 BODY.PEEK[HEADER] 00000007 FETCH 733 BODY.PEEK[1] 00000008 FETCH 733 BODY.PEEK[2] 00000009 NOOP 00000009 OK Completed 0000000a SELECT "{localhost:143/imap/notls/novalidate-cert}INBOX" 0000000a NO Mailbox does not exist 0000000b STATUS INBOX (UIDNEXT) 0000000c APPEND INBOX (\SEEN) {685} + go ahead This message is in MIME format. ... 0000000c NO Message contains invalid header 0000000d NOOP 0000000d OK Completed

03/23/2006 09:23:43 AM	Jan Schneider	Comment #8	Reply to this comment
No, the same error message.

03/23/2006 05:33:31 AM	Michael Slusarz	Comment #7 State ⇒ Feedback	Reply to this comment
How about now?

03/18/2006 04:49:51 PM	Jan Schneider	Comment #6 State ⇒ Assigned	Reply to this comment
No, this time I get "Message contains invalid headers". And it doesn't happen in FW3 btw, so there shouldn't have been the need to merge it. This is happening in FW3 now, HEAD is working fine.

02/22/2006 11:57:08 PM	Jan Schneider	Comment #5 State ⇒ Resolved	Reply to this comment
Try again. And just for (my own) therapy sake: It is so frustrating to try to fix something that isn't broken on your local system. So I apologize in advance if my fixes don't work as expected. Yep, that fixed it. And I know what you are talking about. And it is bizarre that you weren't seeing this in F_3, since the code used to create the new message was identical in HEAD and F_3. That's indeed weird. OTOH, this only started with a change in HEAD recently, so it's probably some other part of the code that caused this.

02/22/2006 11:53:00 PM	Michael Slusarz	Comment #4 State ⇒ Feedback	Reply to this comment
Try again. And just for (my own) therapy sake: It is so frustrating to try to fix something that isn't broken on your local system. So I apologize in advance if my fixes don't work as expected. And it is bizarre that you weren't seeing this in F_3, since the code used to create the new message was identical in HEAD and F_3.

02/22/2006 11:30:16 PM	Jan Schneider	Comment #3 State ⇒ Assigned	Reply to this comment
No, this time I get "Message contains invalid headers". And it doesn't happen in FW3 btw, so there shouldn't have been the need to merge it.

02/22/2006 11:24:39 PM	Michael Slusarz	Comment #2 State ⇒ Resolved	Reply to this comment
Should be fixed now.

02/21/2006 03:34:19 AM	Michael Slusarz	Priority ⇒ 3. High

02/20/2006 11:34:03 AM	Jan Schneider	Comment #1 Priority ⇒ 2. Medium State ⇒ Assigned Assigned to Michael Slusarz Queue ⇒ IMP Summary ⇒ Stripping attachments creates bare newlines again Type ⇒ Bug	Reply to this comment
When stripping attachments I get the following error message again: Message contains bare newlines