Defect #23604

Parsing Attachments in Emails Structured with Content-Disposition: inline Does Not Create New Issue Containing Email File Attachment(s)

Added by Ben Roberts over 6 years ago. Updated almost 4 years ago.

Status:ConfirmedStart date:
Priority:NormalDue date:
Assignee:-% Done:


Category:Email receiving
Target version:-
Resolution: Affected version:3.1.1


Expected: Core Redmine (3.1.1) should parse incoming emails structured with only inline attachment(s) that satisfy all requirements of the user configuration (e.g "Maximum attachment size", "Exclude attachments by name", etc.) to create a new issue with attachments consisting of those attached to the email. Alternatively or in addition, if any attachment(s) are discarded, some indication of this is included in the Redmine log such as the name of the file attachment discarded and the reason discarded.

Observed: Core Redmine (3.1.1) creates a new issue, but does not include (i.e. it discards) the inline attachment(s) in the email and does not represent any issue parsing the email in the log.

Details: The problematic email construction is...

Content-Type: audio/wav; name="VoiceMessage.wav"
Content-Transfer-Encoding: Base64
Content-Disposition: inline; filename="VoiceMessage.wav"; voice=Voice-Message

The Redmine log does not indicate a problem processing the email making the following entry in the log:

MailHandler: issue #5776 created by test test

An example of a raw email with these characteristics is attached to the issue.

Raw Email Redacted & Anonymized.txt Magnifier (46.8 KB) Ben Roberts, 2016-08-17 18:10


#1 Updated by Go MAEDA almost 4 years ago

  • Status changed from New to Confirmed

Also available in: Atom PDF