You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Theodosios Andreou (Jira)" <ji...@apache.org> on 2021/10/07 06:26:00 UTC
[jira] [Updated] (EMAIL-199) MimeMessageParser.parse() throws
"Missing start boundary" exception
[ https://issues.apache.org/jira/browse/EMAIL-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Theodosios Andreou updated EMAIL-199:
-------------------------------------
Description:
h4. Description
I have a MIME header file generated by `ripmime` that should reflect an attachment within it's boundaries:
{code:java}
Content-Type: multipart/alternative; boundary="Apple-Mail=_571FC31E-29ED-47D3-99F6-3B28CF3047AD"
Mime-Version: 1.0 (Mac OS X Mail 14.0 (3654.120.0.1.13))
Content-Type: multipart/mixed; boundary="Apple-Mail=_673A962B-4761-43C3-A4F0-CE3B065D412B"
--Apple-Mail=_673A962B-4761-43C3-A4F0-CE3B065D412B
Content-Transfer-Encoding: 7bit
Content-Type: text/html; charset=us-ascii
Content-Disposition: inline; filename=3529636.pdf
Content-Type: application/pdf; x-mac-hide-extension=yes; x-unix-mode=0644; name="3529636.pdf"
Content-Transfer-Encoding: base64
-Apple-Mail=_673A962B-4761-43C3-A4F0-CE3B065D412B
Content-Transfer-Encoding: 7bit
Content-Type: text/html; charset=us-ascii
-Apple-Mail=_571FC31E-29ED-47D3-99F6-3B28CF3047AD-
{code}
*Expected behavio**r*: The parser should be able to complete and return back ` 3529636.pdf` when we call `getAttachmentList()` on it.
*Workaround*: I haven't found one. It seems that the Mime header is corrupted but `ripmime` reports it as valid.
*Optimal solution*: Be able to process such Mime headers.
was:
h4. Description
I have a MIME header file generated by `ripmime` that should reflect an attachment within it's boundaries:
```
Content-Type: multipart/alternative; boundary="Apple-Mail=_571FC31E-29ED-47D3-99F6-3B28CF3047AD"
Mime-Version: 1.0 (Mac OS X Mail 14.0 (3654.120.0.1.13))
Content-Type: multipart/mixed; boundary="Apple-Mail=_673A962B-4761-43C3-A4F0-CE3B065D412B"
--Apple-Mail=_673A962B-4761-43C3-A4F0-CE3B065D412B
Content-Transfer-Encoding: 7bit
Content-Type: text/html; charset=us-ascii
Content-Disposition: inline; filename=3529636.pdf
Content-Type: application/pdf; x-mac-hide-extension=yes; x-unix-mode=0644; name="3529636.pdf"
Content-Transfer-Encoding: base64
-Apple-Mail=_673A962B-4761-43C3-A4F0-CE3B065D412B
Content-Transfer-Encoding: 7bit
Content-Type: text/html; charset=us-ascii
--Apple-Mail=_571FC31E-29ED-47D3-99F6-3B28CF3047AD--
```
*Expected behavio**r*: The parser should be able to complete and return back ` 3529636.pdf` when we call `getAttachmentList()` on it.
*Workaround*: I haven't found one. It seems that the Mime header is corrupted but `ripmime` reports it as valid.
*Optimal solution*: Be able to process such Mime headers.
> MimeMessageParser.parse() throws "Missing start boundary" exception
> -------------------------------------------------------------------
>
> Key: EMAIL-199
> URL: https://issues.apache.org/jira/browse/EMAIL-199
> Project: Commons Email
> Issue Type: Bug
> Affects Versions: 1.5
> Reporter: Theodosios Andreou
> Priority: Major
>
> h4. Description
> I have a MIME header file generated by `ripmime` that should reflect an attachment within it's boundaries:
>
>
> {code:java}
> Content-Type: multipart/alternative; boundary="Apple-Mail=_571FC31E-29ED-47D3-99F6-3B28CF3047AD"
> Mime-Version: 1.0 (Mac OS X Mail 14.0 (3654.120.0.1.13))
> Content-Type: multipart/mixed; boundary="Apple-Mail=_673A962B-4761-43C3-A4F0-CE3B065D412B"
> --Apple-Mail=_673A962B-4761-43C3-A4F0-CE3B065D412B
> Content-Transfer-Encoding: 7bit
> Content-Type: text/html; charset=us-ascii
> Content-Disposition: inline; filename=3529636.pdf
> Content-Type: application/pdf; x-mac-hide-extension=yes; x-unix-mode=0644; name="3529636.pdf"
> Content-Transfer-Encoding: base64
> -Apple-Mail=_673A962B-4761-43C3-A4F0-CE3B065D412B
> Content-Transfer-Encoding: 7bit
> Content-Type: text/html; charset=us-ascii
> -Apple-Mail=_571FC31E-29ED-47D3-99F6-3B28CF3047AD-
>
> {code}
>
>
> *Expected behavio**r*: The parser should be able to complete and return back ` 3529636.pdf` when we call `getAttachmentList()` on it.
>
> *Workaround*: I haven't found one. It seems that the Mime header is corrupted but `ripmime` reports it as valid.
>
> *Optimal solution*: Be able to process such Mime headers.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)