jira incoming mail handler

We have a jira 5.2.2. A mail server was configured in jira to to talk to our exchange via imap. uid/pwd were correct. When a mail handler was created, we got the error below during its creation. Has anybody run into this before?

2013-01-08 08:48:50,141 QuartzWorker-1 ERROR ServiceRunner PLM email Generated Issues [atlassian.mail.incoming.mailfetcherservice] PLM email Generated Issues[10100]: Error connecting to host 'mail.mspot.com' as user 'plm.jira' via protocol 'imap': javax.mail.MessagingException: socks;
nested exception is:
java.net.SocketException: socks
javax.mail.MessagingException: socks;
nested exception is:
java.net.SocketException: socks
at com.sun.mail.imap.IMAPStore.protocolConnect(IMAPStore.java:670)
at javax.mail.Service.connect(Service.java:295)
at com.atlassian.jira.service.services.mail.MailFetcherService$MessageProviderImpl.getAndProcessMail(MailFetcherService.java:201)
at com.atlassian.jira.service.services.mail.MailFetcherService.runImpl(MailFetcherService.java:356)
at com.atlassian.jira.service.services.file.AbstractMessageHandlingService.run(AbstractMessageHandlingService.java:252)
at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
Caused by: java.net.SocketException: socks
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:405)

2 answers

0 votes
Daryl Chuah Atlassian Team Jan 08, 2013

Hi Ming Ho

I found a knowledge base article that could be quite useful in diagnosing mail handler issues, you might want to have a read on this : https://confluence.atlassian.com/display/JIRAKB/Diagnosing+Mail+and+Mail+Handlers+Issues

Hope it does helps a little


This kind of error implies something outside of JIRA, i.e. network. In addition to the above, using a simple telnet check to verify TCP connectivity with the server would be a start:

telnet <span>mail.mspot.com [port, eg 993]

You could also code up a mock client to validate connectivity, as per: http://stackoverflow.com/questions/10008947/javax-mail-messagingexception-connection-reset-while-trying-to-access-gmail-usi

0 votes
Renjith Pillai Community Champion Jan 08, 2013

Exception appears to be that the JIRA server is not able to connect to the IMAP server port. Can you try a direct telnet to the IMAP port from the JIRA server to check whether it is reachable?

i was able to retreat emails using fetchmail on the same server. so, connection should be fine. it goes through non-ssl port 143. so certs are not the issue. one thing to note w/ fetchmail is that I had to enable NTLM. I wonder if that is the cause of the problem. perhaps jira use plaintext when authenticating over none secure port.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,101 views 13 19
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot