-
Bug
-
Resolution: Obsolete
-
High (View bug fix roadmap)
-
None
-
None
If JIRA is configured to create/comment issues from email, and encounters a mixed HTML/image email with a MIME part:
Content-Type: multipart/related; type="text/html"
Then JIRA will fail to parse the HTML part of the email, and logs this:
2006-08-10 14:43:50,452 WARN [jira.issue.managers.DefaultAttachmentManager] Creating attachment without a file. Aborting
Here are the headers from an email:
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0^M MIME-Version: 1.0^M Content-Type: multipart/related;^M type="text/html";^M boundary="----_=_NextPart_001_01C6BB93.375A48EB"^M ..... This is a multi-part message in MIME format.^M ^M ------_=_NextPart_001_01C6BB93.375A48EB^M Content-Type: text/html;^M charset="iso-8859-1"^M Content-Transfer-Encoding: quoted-printable^M ^M <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =^M ....
- causes
-
JRASERVER-12525 Emails containing attachments with non-ASCII names lost
-
- Closed
-
-
JRASERVER-12530 Renamed email attachments lose extension
-
- Closed
-
- is related to
-
JRASERVER-12534 JIRA fails to add attachments with long filenames from RFC 2231-compliant mail clients
- Closed
-
JRASERVER-6094 Email created task with email attachments.
- Gathering Interest
- was cloned as
-
JRASERVER-15133 "message" type attachments get lost when creating issues from emails
-
- Closed
-
-
JRASERVER-10827 Improve parsing of multipart (HTML) emails
- Gathering Interest
After investigating this issue further, I have identified several distinct issues that have over time stemmed from the original issue - the original issue being: the loss of one or more parts of an email message (content or attachments) when trying to create JIRA issues from emails. The original issue has been resolved in part by Jeff, but under certain situations, JIRA logs may still report the following warning:
It should be known that this is largely benign - it simply means that while processing the email message, some parts of it were flagged as being required to be attached to the JIRA issue, but no filename for the attachment could be determined. The most common scenario of this happening is when you have an email message in both plain and rich text format; JIRA attempts attach the rich text part, but it does not have a filename, and so this fails. In this case, the effect is minimal, as the meaning of the message is usually conveyed through the plain text part anyway.
If however, you are finding that JIRA is still losing important parts of your messages, as what appeared to be the case for Bruno, please feel free to raise a support case at http://support.atlassian.com, providing examples of email messages that will reproduce the issue.
The following are the known and reproducible issues that stemmed from this issue that are still open:
JRA-12525- Emails containing attachments with non-ASCII names lostJRA-12534- JIRA fails to add attachments with long filenames from RFC 2231-compliant mail clientsThe following have been resolved:
JRA-12530- Renamed email attachments lose extensionJRA-15133- "message" type attachments get lost when creating issues from emailsCheers,
Michael Tokar [Atlassian]