When a user sends us an email with attachment from a certain email system (that I don't have control over), the mailhandler creates an issue (as it is supposed to), but if there are any attachments, they are lost.

We get this one in the log when such an email arrives:

2010-02-01 12:40:10,679 JiraQuartzScheduler_Worker-3 WARN [com.atlassian.mail.MailUtils] Unable to extract text from MIME part with Content-Type 'multipart/mixed;
boundary="----_=_NextPart_001_01CAA333.314BAB2B"
2010-02-01 12:40:10,679 JiraQuartzScheduler_Worker-3 WARN [com.atlassian.mail.MailUtils] Unable to extract text from MIME part with Content-Type 'application/ms-tnef;
name="winmail.dat"

I have spoken with the guy in charge of the customer's mailsystem, where the mail lands before it is being forwarded to the jira mail POP boxes. When they receive the email, they apparently encode it in TNEF and forwards it to a internal domain where it is relayed to the Jira mail SMTP->POP boxes. Exchange 2003 does not support re-formatting the email to a different format when it forwards emails. My guess is, that sometime back in the days, Exchange for some reason was set to TNEF for this specific customer and HTML for our other customers. BUT, this is a production system in the banking world, so people are very reluctant to change anything that is in production and running unless one can prove the change will not break anything else in the systems. Which I can't. Roadblock.

So for now, the only option is to get Jira to eat TNEF encoded emails. Perhaps some kind of preprocesser that is initiated by the mail handler before it actually tries to parse the email?