Bug #106911 for MIME-tools: MIME::Parser cannot extract nested "message/global" message

Sun Sep 06 00:23:49 2015 hatuka [...] nezumi.nu - Ticket created

Subject:

MIME::Parser cannot extract nested "message/global" message

Hi, MIME::Parser cannot extract nested "message/global" message (RFC6532), even if extract_nested_message() is true. Though I don't know if authors of MIME-tools are planning support of "internationalized" messages, I look for it. --- nezumi

Sun Sep 06 08:51:29 2015 dfs+pause [...] roaringpenguin.com - Taken

Sun Sep 06 08:54:41 2015 dfs [...] roaringpenguin.com - Correspondence added

Subject:	Re: [rt.cpan.org #106911] MIME::Parser cannot extract nested "message/global" message
Date:	Sun, 6 Sep 2015 08:54:28 -0400
To:	bug-MIME-tools [...] rt.cpan.org
From:	Dianne Skoll <dfs [...] roaringpenguin.com>

Hi, Show quoted text

> MIME::Parser cannot extract nested "message/global" message > (RFC6532), even if extract_nested_message() is true.

Sorry, there's insufficient information for me to even begin to diagnose this. Please post a sample message along with a short program that attempts to parse it; please also post the actual results and what you expect the results should be. Regards, Dianne.

Sun Sep 06 08:54:42 2015 The RT System itself - Status changed from 'new' to 'open'

Sun Sep 06 10:39:30 2015 dfs [...] roaringpenguin.com - Correspondence added

Subject:	Re: [rt.cpan.org #106911] MIME::Parser cannot extract nested "message/global" message
Date:	Sun, 6 Sep 2015 10:39:18 -0400
To:	bug-MIME-tools [...] rt.cpan.org
From:	Dianne Skoll <dfs [...] roaringpenguin.com>

Hi, again, OK, I read RFC 6532. Supporting those types of messages will be extremely difficult and require extensive changes to MIME::tools. So no ETA on that. [I can't believe that's a standards-track RFC. :( ] Regards, Dianne.

Mon Sep 07 01:11:26 2015 nezumi [...] cpan.org - Correspondence added

Subject:	Re: [rt.cpan.org #106911] MIME::Parser cannot extract nested "message/global" message
Date:	Mon, 7 Sep 2015 14:10:58 +0900
To:	bug-MIME-tools [...] rt.cpan.org
From:	Hatuka*nezumi - IKEDA Soji <nezumi [...] cpan.org>

Hi, On Sun, 6 Sep 2015 10:39:31 -0400 "Dianne Skoll via RT" <bug-MIME-tools@rt.cpan.org> wrote: Show quoted text

> <URL: https://rt.cpan.org/Ticket/Display.html?id=106911 > > > Hi, again, > > OK, I read RFC 6532. Supporting those types of messages will be extremely > difficult and require extensive changes to MIME::tools. So no ETA > on that.

I didn't think so. MIME::Parser itself seems not taking care of encoding of header fields. So when the header contains no encoded-words but UTF-8 strings, it seems successfully parsed. So I guessed needed change is essentially to add one line: elsif (("$type/$subtype" eq "message/rfc822" || "$type/$subtype" eq "message/external-body" || + "$type/$subtype" eq "message/global" || ("$type/$subtype" eq "message/partial" && defined($head->mime_attr("content-type.number")) && $head->mime_attr("content-type.number") == 1)) && $self->extract_nested_messages) { $self->debug("attempting to process a nested message"); return undef unless defined($self->process_message($in, $rdr, $ent)); } I will prepare samples when I can. But you can close this ticket anytime you prefer. Regards, -- nezumi Show quoted text

> Regards, > > Dianne. >

-- Hatuka*nezumi - IKEDA Soji <nezumi@cpan.org>