Certain Mail Messages Fail to Import
Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
Clicking on the Fetch mail now button showed success, however there are no results shown in Confluence.
This warning shows up in the log file:
2009-12-19 10:17:00,803 WARN [DefaultQuartzScheduler_Worker-2] [atlassian.confluence.mail.DefaultMailContentManager] storeIncomingMail Could not store mail message Expected ';', got ","
javax.mail.internet.ParseException: Expected ';', got ","
at javax.mail.internet.ParameterList.<init>(ParameterList.java:281)
at javax.mail.internet.ContentDisposition.<init>(ContentDisposition.java:100)
at javax.mail.internet.MimeBodyPart.getDisposition(MimeBodyPart.java:1085)
at javax.mail.internet.MimeBodyPart.getDisposition(MimeBodyPart.java:318)
at com.atlassian.mail.MailUtils.getBodyFromMultipart(MailUtils.java:469)
Cause
Some mail messages may contain an SMIME signature that does not follow RFC 2183 convention and contains a header like this:
Content-Disposition: attachment;
size=362586;
creation-date=Wed, 23 Sep 2009 15:07:22 GMT;
modification-date=Wed, 09 Dec 2009 16:17:06 GMT;
filename="documentName.doc"
In this case, the creation-date and modification-date fields are not encapsulated in quotes.
Resolution
The problem is caused by the program that creates the SMIME signature. If RFC 2183 is followed, the header should have the dates encapsulated in quotes:
Content-Disposition: attachment;
size=362586;
creation-date="Wed, 23 Sep 2009 15:07:22 GMT";
modification-date="Wed, 09 Dec 2009 16:17:06 GMT";
filename="documentName.doc"