nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Incoming SMTP Mail works but Outgoing doesn't

Varun Suresh

Hi All,

We're running Jira version 7.8.1, JIRA Service Desk 3.11.1

Using Google Apps for Business.

When we try to use the Email notifications for e.g, with the service desk, incoming emails to the configured account successfully get converted into tickets. But, outgoing notifications aren't working. When I test under Outgoing, I get the following error:

com.atlassian.mail.MailException: com.sun.mail.util.MailConnectException: Couldn't connect to host, port: smtp.gmail.com, 465; timeout 10000;
 nested exception is:
 java.net.ConnectException: Connection refused
 at com.atlassian.mail.server.impl.SMTPMailServerImpl.sendWithMessageId(SMTPMailServerImpl.java:225) [atlassian-mail-2.8.6.jar:?]
 at com.atlassian.mail.queue.SingleMailQueueItem.send(SingleMailQueueItem.java:44) [atlassian-mail-2.8.6.jar:?]
 at com.atlassian.mail.queue.MailQueueImpl.sendBufferUnderLock(MailQueueImpl.java:103) [atlassian-mail-2.8.6.jar:?]
 at com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:56) [atlassian-mail-2.8.6.jar:?]
 at com.atlassian.jira.mail.JiraMailQueue$1.apply(JiraMailQueue.java:51) [classes/:?]
 at com.atlassian.jira.mail.JiraMailQueue$1.apply(JiraMailQueue.java:48) [classes/:?]
 at com.atlassian.jira.util.velocity.DefaultVelocityRequestContextFactory.runWithStaticBaseUrl(DefaultVelocityRequestContextFactory.java:110) [classes/:?]
 at com.atlassian.jira.util.DefaultBaseUrl.runWithStaticBaseUrl(DefaultBaseUrl.java:50) [classes/:?]
 at com.atlassian.jira.mail.JiraMailQueue.sendBuffer(JiraMailQueue.java:48) [classes/:?]
 at com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:21) [classes/:?]
 at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:68) [classes/:?]
 at com.atlassian.jira.service.ServiceRunner.runService(ServiceRunner.java:62) [classes/:?]
 at com.atlassian.jira.service.ServiceRunner.runServiceId(ServiceRunner.java:44) [classes/:?]
 at com.atlassian.jira.service.ServiceRunner.runJob(ServiceRunner.java:32) [classes/:?]
 at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:153) [atlassian-scheduler-core-1.7.0.jar:?]
 at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:118) [atlassian-scheduler-core-1.7.0.jar:?]
 at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:97) [atlassian-scheduler-core-1.7.0.jar:?]
 at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:443) [atlassian-scheduler-caesium-1.3.3.jar:?]
 at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeLocalJob(CaesiumSchedulerService.java:410) [atlassian-scheduler-caesium-1.3.3.jar:?]
 at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:388) [atlassian-scheduler-caesium-1.3.3.jar:?]
 at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:285) [atlassian-scheduler-caesium-1.3.3.jar:?]
 at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:282) [atlassian-scheduler-caesium-1.3.3.jar:?]
 at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:65) [atlassian-scheduler-caesium-1.3.3.jar:?]
 at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:59) [atlassian-scheduler-caesium-1.3.3.jar:?]
 at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:34) [atlassian-scheduler-caesium-1.3.3.jar:?]

Attaching the configs

Accepted answers

Varun Suresh

Hi All,

Looks like I completely had a brain aneurysm and totally overlooked the fact that we aren't on https currently. It's working now that I changed Outgoing settings to SMTP and changed port to 25. Thank you for your responses. Cheers!

All comments

Elifcan Cakmak

Hello,

Have you tried using TLS option with port 587? For yandex we use this configuration, it may be helpful for you too.

Regards,

JP _AC Bielefeld Leader_

Hi,

you might have to allow from the Google admin pages to grant third-party access to Jira.

https://support.google.com/plus/answer/2485911?hl=en

Best

Varun Suresh

Hi Elifcan,

Thank you for your reply. But we aren't using https. Hence the following message when I tried your recommendation.

Varun Suresh

Hi JP,

Thank you for your reply. Please correct me if I'm wrong, but I believe that I've already given access to less secure apps, if that is what you are referring to.

If you look at the OP, you can see that Jira is able to access and read emails, i.e, incoming SMTP server access works fine. It's only the outgoing SMTP server that has issues connecting. Can you please point me in the right direction if I'm missing something?

Admin account has already allowed users to manage their own access for 3rd party apps and the test account that I'm using for email integration also allows access as shown above.

Varun Suresh

Hi All,

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-service-desk

jira-software

jira-software-server