BAD Command Argument Error when creating issue via email with Microsoft Exchange
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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
Email are not created as an issue from the IMAP server (Microsoft Exchange). Errors appear such as:
1
2
3
4
5
6
7
8
9
10
11
12
JiraQuartzScheduler_Worker-3 ERROR [service.services.mail.MailFetcherService] Create Issue/Comment Service - ...[...]: Exception: A4 BAD Command Argument Error. 11;
nested exception is:
com.sun.mail.iap.BadCommandException: A4 BAD Command Argument Error. 11
javax.mail.MessagingException: A4 BAD Command Argument Error. 11;
nested exception is:
com.sun.mail.iap.BadCommandException: A4 BAD Command Argument Error. 11
at com.sun.mail.imap.IMAPMessage.getHeader(IMAPMessage.java:624)
at com.atlassian.jira.service.services.mail.MailFetcherService.run(MailFetcherService.java:175)
at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:56)
at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:61)
at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)
Cause
The Microsoft Exchange server is installed with Turkish Regional Settings. The uppercase/lowercase conversion from the Microsoft Exchange server to JIRA is not working.
Resolution
Update the Exchange server with English Regional Setting
Was this helpful?