2006-11-27 11:42:59,480 WARN [jira.issue.managers.DefaultAttachmentManager] Creating attachment without a file. Aborting

Anyway - IMHO it is an improvement, since an attachment is usually a .doc or .jpg file, not another e-mail. I often get emails that contain an .eml attachment which I have to open (in Outlook express), and then that is an email with its own .eml attachment, which when you open that one has an attachment of a .jpg. Yikes! How is JIRA gonna do all that?

To illustrate, if I make up a file name "blah-blah.random", attach it to an email and sent it to myself... no email client would ignore the fact that "blah-blah.random" file was attached and essentially throw it away which is what jira's email handler is doing.

I am not looking for jira to recursively look into an attached file and pull out data. If there is an email with an attached email file (email.msg) and within this email file a test.jpg file. All that needs to be done is save 'email.msg' and nothing more.

I would consider it an improvement request if jira took the attached email and made it into a comment or something (or even create a new issue for it). In either of these cases, jira is retaining the data as is and we don't lose any information. I consider it a bug because the email handler is throwing away a piece of the email.

Thanks.

I searched for this issue but couldn't find anything relevant in the first few pages of the results so I submitted a support request and Kay turned my attention to this request.

JRA-3668

JIRA currently recursively traverses the whole tree of nested e-mails and any attachments (other than e-mails) are attached to the issue being created.

Do you have any suggestions about how to handle the attached e-mails?

Cheers,
Dushan

From when I did testing of this, an email (lets call it email #1) that was sent to a jira pop3 with an attached email (*.msg file, lets call this email #2), the email #2 was not attached as a file to the issue created. I honestly have no idea where it went, the contents of the attached email were nowhere to be found within jira - not as an attachment or as a comment.

To explain again, when I send an email with another email attached as an *.msg file, I am sending this so that whoever the recipient is, gets a copy of that email.

With that said, when I send an email with an attached TESTEMAIL.MSG file to a jira linked POP3 account, I would like jira to create a new issue (JIRA-1000 for example) with the body of the email (not the file) as the description AND more importantly, within this issue, there should be one file labeled "TESTEMAIL.MSG" as an attachment. So, when I look at this issue in jira and click on the link to TESTEMAIL.MSG, it would open up the email file.

Let me know if what I am saying makes sense, I thought I was pretty clear in my comment made on [29/Nov/06 03:13 PM] but I guess I wasn't. I don't want jira to recursively traverse through a whole tree of nested emails. I just want it to store it as one file (which may include other mime-type files) as an attachment to an issue.

Thanks!