6.0.0-beta1
10/17/25

[#1770] multipart/mixed messages results in "invalid mail header" on Cyrus
Summary multipart/mixed messages results in "invalid mail header" on Cyrus
Queue IMP
Queue Version 4.0.3
Type Bug
State Resolved
Priority 2. Medium
Owners slusarz (at) horde (dot) org
Requester worf (at) 4uchat (dot) de
Created 04/12/2005 (7493 days ago)
Due
Updated 04/14/2005 (7491 days ago)
Assigned 04/12/2005 (7493 days ago)
Resolved 04/14/2005 (7491 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
04/14/2005 06:11:56 AM Michael Slusarz Comment #6
State ⇒ Resolved
Reply to this comment
I changed the code (HEAD, IMP 4.0.4) so it now ignores any blank lines 
in header.txt.
04/13/2005 06:53:06 PM worf (at) 4uchat (dot) de Comment #5 Reply to this comment
That is a solution for Cyrus :-) It would be a good idea to reference 
that problem in a readme file. Because there is a workaround, priority 
could be set to low.

Thank you for that advice
04/13/2005 04:11:16 PM Michael Slusarz Priority ⇒ 2. Medium
 
04/13/2005 04:11:02 PM Michael Slusarz Comment #4 Reply to this comment
Make sure you do not have empty lines or extra lines at the end of 
imp/config/headers.txt.
04/13/2005 03:22:51 PM worf (at) 4uchat (dot) de Comment #3 Reply to this comment
I am sorry, but more in depth investigation of that problem was 
necessary. I found following lines in message generated by imp4:



X-Originating-IP: 10.0.0.1

X-Remote-Browser: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.6)

         Gecko/20050322 Firefox/1.0.2

:

Sender:  <www@local>



After removing lines

X-Remote-Browser...

and

:

message was accepted by Cyrus. I made an additional test by removing 
line break in X-Remote-Browser line. : (colon) also removed. Messages 
was also accepted. Problem is obviously caused by 2 items:



1. A header line with a single colon and space

2. Linebreak in X-Remote-Browser.



Problem is *not* caused by line break in Content-Type


04/12/2005 09:22:47 PM Chuck Hagenbuch Comment #2
Assigned to Michael Slusarz
State ⇒ Feedback
Reply to this comment
That's a perfectly valid way of folding header lines. Are you *sure* 
that's what cyrus doesn't like? What about the kind of linebreak 
that's there, etc.?
04/12/2005 05:47:34 PM worf (at) 4uchat (dot) de Comment #1
State ⇒ Unconfirmed
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ multipart/mixed messages results in "invalid mail header" on Cyrus
Queue ⇒ IMP
Reply to this comment
Hello,



IMP-H3-4.0.3 has a nasty bug in multipart/mixed mime processing:



How to reproduce the bug:



Write a mail with binary attachment or a GPG signed mail.



Cyrus denies to process mail with error:

LMTP error after DATA: 554 5.6.0 Message contains invalid header



IMP creates a strange line break after "multipart/mixed;"



Subject: afasfasfasffsaf

MIME-Version: 1.0

Content-Type: multipart/mixed;

        boundary="=_3cbrxxfxr2rk"

Content-Transfer-Encoding: 7bit

User-Agent: Internet Messaging Program (IMP) H3 (4.0.3)



IMP version 3.2.6 does not create such a line break, so these mails 
are processed correctly:

Subject: test

MIME-Version: 1.0

Content-Type: multipart/mixed; 
boundary="-MOQ1113327216054d5ddc0079b2dbbc447f2712baa3f9"

User-Agent: Internet Messaging Program (IMP) 3.2.6



That is really a show stopper in Cyrus environments.



regards

Christian


Saved Queries