-
Suggestion
-
Resolution: Unresolved
-
3
-
26
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Problem Definition
Currently if you forward a mail as an attachment, for example using Microsoft Outlook or Thunderbird, it shows up in a JIRA issue as a file with no extension containing a MIME formatted file containing xhtml with MS Office's extensions. Because there is no extension, clicking on the file does not open it in the appropriate way.
Suggested Solution
Adding a check to rename such a file to be called .eml or .msg would give the necessary hint required for a mail program to successfully open such an attachment.
Cause
Attaching an email in a client such as gmail will provide a filename for the attachment, for example:
Content-Type: message/rfc822; name="test.eml" Content-Disposition: attachment; filename="test.eml" Content-Transfer-Encoding: base64 ...
Attaching an email in Outlook provides no name or filename for the attachment:
Content-type: message/rfc822 Content-disposition: attachment
As a result JIRA doesn't know what to name this file.
Workaround
- This has previously been suggested and implemented in JEMH as per https://thepluginpeople.atlassian.net/browse/JEMH-1376, so seems like it's possible to do this.
- Remove the "In-Reply-To:" header mail
- is related to
-
JRASERVER-40477 Allow forwarded email attachments to be detected by JIRA mail handler and renamed to .eml or .msg
- Gathering Interest
- supersedes
-
JRACLOUD-34220 Emails with attached emails is saved without eml extension
-
- Closed
-