Tickets :: [#11718] Imp does not always create a valid subtype

6.0.0-beta1

11/29/25

Summary	Imp does not always create a valid subtype
Queue	IMP
Queue Version	5.0.23
Type	Bug
State	Resolved
Priority	1. Low
Owners
Requester	peter.meier+horde (at) immerda (dot) ch
Created	11/17/2012 (4760 days ago)
Due
Updated	11/20/2012 (4757 days ago)
Assigned	11/19/2012 (4758 days ago)
Resolved	11/20/2012 (4757 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

11/20/2012 08:18:09 PM	Michael Slusarz	Comment #5 State ⇒ Resolved	Reply to this comment
Can't reproduce in IMP 6 so closing.

11/19/2012 09:47:07 PM	Michael Slusarz	Comment #4	Reply to this comment
According to RFC1521 [1] a value of a subtype must be specified, so IMP produces here imho an invalid message. This RFC is obsolete. The controlling RFC is 2046. It states that in the absence of any and/or a valid charset, it must be rendered in US-ASCII. So this is not a critical issue. I can reproduce it if I try to open an E-Mail I can't decrypt (because I don't have the right OpenPGP key for it) and reply to that e-mail. -> The e-mail sent does not specifiy a value for the charset subtype of the Content-Type header field. This is almost certainly fixed in IMP 6. I don't see a need to fix this in IMP 5 as it is not a critical bug.

11/19/2012 04:58:18 PM	peter (dot) meier+horde (at) immerda (dot) ch	Comment #3	Reply to this comment
Do you still see this in IMP H5? IMP with Horde 5? I do not yet have an installation to test that.

11/19/2012 12:01:10 PM	Jan Schneider	Comment #2 State ⇒ Feedback	Reply to this comment
Do you still see this in IMP H5?

11/17/2012 11:50:55 AM	peter (dot) meier+horde (at) immerda (dot) ch	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Imp does not always create a valid subtype Queue ⇒ IMP Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
The following part is an excerpt of a Mail Header sent by IMP, where the charset in the content-type is empty. ---- User-Agent: Internet Messaging Program (IMP) H4 (5.0.23) Content-Type: text/plain; charset=; format=flowed; DelSp=Yes MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable --- This happened when somebody replies to a message she could not decrypt. According to RFC1521 [1] a value of a subtype must be specified, so IMP produces here imho an invalid message. I can reproduce it if I try to open an E-Mail I can't decrypt (because I don't have the right OpenPGP key for it) and reply to that e-mail. -> The e-mail sent does not specifiy a value for the charset subtype of the Content-Type header field. Also various e-mail parsing tools detect such a header as invalid. [1] https://datatracker.ietf.org/doc/rfc1521/