You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Kushal J (JIRA)" <ji...@apache.org> on 2015/10/14 12:18:05 UTC

[jira] [Created] (EMAIL-159) Parse exception when parsing the email content

Kushal J created EMAIL-159:
------------------------------

             Summary: Parse exception when parsing the email content
                 Key: EMAIL-159
                 URL: https://issues.apache.org/jira/browse/EMAIL-159
             Project: Commons Email
          Issue Type: Bug
    Affects Versions: 1.4
            Reporter: Kushal J
            Priority: Critical


Hi Team,
We have an application that reads the email and extracts the attachment from the email. For certain emails we are seeing below issue, can you please check if anything  missed out from our side or is it the bug.

javax.mail-api Version : 1.5.3
commons-email Version : 1.4

Email Header information for failure

Subject: =?utf-8?q?YYYY?=
=?utf-8?Q?=C3=A9p=C3=B4t_ZZZ_ZZZ_41/2015_-_PPP_XXX?=
Message-Id: <20...@htm-group.com>
X-Priority: 3
Importance: Normal
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=_NextPart_03254=_=63839"
Content-Transfer-Encoding: 7bit

Email Header information for Success


Subject: PPP : Stocks XXX 41/2015 -ZZZZ
Message-Id: <20...@htm-group.com>
X-Priority: 3
Importance: Normal
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=_NextPart_09373=_=37676"
Content-Transfer-Encoding: 7bit

These 2 emails are sent from the same email ID, but we are getting ParseException when we are trying to parse the above 1st header.


Exception trace

javax.mail.internet.ParseException: Expected parameter value, got "="
        at javax.mail.internet.ParameterList.<init>(ParameterList.java:256)
        at javax.mail.internet.ContentDisposition.<init>(ContentDisposition.java:100)
        at javax.mail.internet.MimeBodyPart.getDisposition(MimeBodyPart.java:1085)
        at javax.mail.internet.MimeBodyPart.getDisposition(MimeBodyPart.java:318)




Please help us in fixing this issue.


Regards,
Kushal J



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)