Skip Menu |

This queue is for tickets about the MIME-tools CPAN distribution.

Report information
The Basics
Id: 7269
Status: rejected
Priority: 0/
Queue: MIME-tools

Owner: Nobody in particular
Requestors: christian.jaeger-rtcpanorg [...]

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.411 (Entity 5.404)
X-RT-Original-Encoding: iso-8859-1
Content-Length: 801
Download (untitled) / with headers
text/plain 801b
using MIME::Parser 5.406 I've noticed emails with In-Reply-To/References headers with messageid's that are broken up into pieces with a newline, like here: ... Message-Id: <p0602040bbd3860aeca63@[]> In-Reply-To: <8FB07C0AB746224C82B15C250958123B036B41@irongiant.nano.covalentmaterials.c Show quoted text
References: <8FB07C0AB746224C82B15C250958123B036B41@irongiant.nano.covalentmaterials.c Show quoted text
... (note the newline and spaces between '..terials.c' and 'om>') MIME::Parser->parse(..)->head->get("references") gives this back still with the newline [and maybe spaces] in it. It thus doesn't match the original messageid anymore. Is this a bug in MIME::Parser, the MUA (which I don't know, would have to ask), or is it a deficiency in the specs? (I've not read the specs)? Cheers, Christian.
MIME-Version: 1.0
X-Mailer: MIME-tools 5.418 (Entity 5.418)
Content-Disposition: inline
Message-Id: <rt-3.6.HEAD-16171-1188421807-1543.7269-0-0 [...]>
Content-Type: text/plain; charset="utf8"
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8
Content-Length: 15
Not enough info

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to