Incoming mail fails with "javax.mail.AuthenticationFailedException: EOF on socket" while connecting to Microsoft Exchange using POP3

Still need help?

The Atlassian Community is here for you.

Ask the community

 

Platform Notice: Server and Data Center Only - This article only applies to Atlassian products on the server and data center platforms.

 

 

Problem

Issues and comments are no longer able to be created via email. The following appears in the atlassian-jira.log file.

2017-08-11 15:47:00,069 Caesium-1-3 WARN anonymous    Xxx Xxxx [c.a.mail.incoming.mailfetcherservice] Xxx Xxxx[10200]: javax.mail.AuthenticationFailedException: EOF on socket while connecting to host 'xxxxxxx.xxxxx.com' as user 'xxxxxxx' via protocol 'pop3': javax.mail.AuthenticationFailedException: EOF on socket
javax.mail.AuthenticationFailedException: EOF on socket
	at com.sun.mail.pop3.POP3Store.protocolConnect(POP3Store.java:213)
	at javax.mail.Service.connect(Service.java:366)
	at com.atlassian.jira.service.services.mail.MailFetcherService$MessageProviderImpl.getAndProcessMail(MailFetcherService.java:182)
	at com.atlassian.jira.service.services.mail.MailFetcherService.runImpl(MailFetcherService.java:366)
	at com.atlassian.jira.service.services.file.AbstractMessageHandlingService.run(AbstractMessageHandlingService.java:229)
	at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
	at com.atlassian.jira.service.ServiceRunner.runService(ServiceRunner.java:62)
	at com.atlassian.jira.service.ServiceRunner.runServiceId(ServiceRunner.java:44)
	at com.atlassian.jira.service.ServiceRunner.runJob(ServiceRunner.java:32)
	at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:153)
	at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:118)
	at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:97)
	at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:443)
	at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJob(CaesiumSchedulerService.java:438)
	at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJobWithRecoveryGuard(CaesiumSchedulerService.java:462)
	at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:390)
	at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:285)
	at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:282)
	at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:65)
	at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:59)
	at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:34)
	at java.lang.Thread.run(Thread.java:745)
2017-08-11 15:47:11,991 Finalizer DEBUG      [c.atlassian.mail.incoming] QUIT
2017-08-11 15:47:11,991 Finalizer DEBUG      [c.atlassian.mail.incoming] <EOF>

Diagnosis

Environment

  • JIRA Software or Core using the standard JIRA mail handler
  • Connecting via POP3
  • Microsoft Exchange

Cause

PopProxy is inactive. This sometimes happens after an Exchange server restart, but the reasons why it becomes inactive are not necessarily known.

Resolution

Ensure that PopProxy is active and can be reached externally by JIRA.

  1. Check to ensure that port 110 is open on the Exchange server.
    1. Server must be listening on port 110 (use netstat on the server to verify)
    2. Check that an outside server can see that port 110 is open. (Note: It may be necessary to use nmap or a similar tool to detect port 110 availability.)
    3. Attempt a telnet session to port 110 on the server. You may see something like "+OK The Microsoft Exchange POP3 service is ready."
  2. Check to ensure that PopProxy is enabled.
    1. Open Exchange Admin PowerShell on the Exchange server.
    2. Run the command: Get-ServerComponentState - Identify <SERVER_NAME> (where SERVER_NAME is the machine name of the Exchange server).
    3. Look for the PopProxy component and check the State column. It should say 'Active.'
  3. If PopProxy is 'Inactive,' then attempt to activate it with this command: Set-ServerComponentState -State Active -Requester HealthAPI -Component PopProxy -Identity <SERVER_NAME> 

 

 

Last modified on Aug 21, 2017

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.