Email Confiig Error

[Alexandre Oliveira]

I'm trying to config the Service Desk email but I always received an error message :

SOCKS: TTL Expired

[brnpimentel]

same here!

[Fahad Siddiqui]

Plz explain u r issue

[PHC Admin]

Why are there never simple answers to the many many many configuration challenges with Jira? Atlassian's products just keep getting more and more convoluted.

[Mark Newell]

Alexandre Oliveira,

Did you ever get this issue resolved? I am having the same issue and was wondering what the resolution was for you.

Thanks

[monkeytronics]

Exact Same issue here. Identical conditions and results. 

[Fahad Siddiqui]

@monkeytronics can you send a test email through jira system and provide me the logs

[Fahad Siddiqui]

@Alexandre Oliveira 

This can be related to your Network. You need to contact them.

Also please check the below link related to email.

https://confluence.atlassian.com/adminjiraserver075/configuring-an-smtp-mail-server-to-send-notifications-947188089.html

https://confluence.atlassian.com/jirakb/unable-to-send-email-with-smtp-server-via-ssl-530-5-7-0-must-issue-a-starttls-command-first-due-to-mail-smtp-starttls-enable-property-218269287.html

[Alexandre Oliveira]

Hi @Fahad Siddiqui , my maining problem it's inside IMAP email config inside Service Desk.

Projects -> Service Desk -> Config -> Email Setting

When I set the host and IMAPS : 993 I received this error message.

[Fahad Siddiqui]

what protocol are you using? 

can you please share the screen shot of email settings

[Alexandre Oliveira]

I tried IMAP / IMAPS / POP / POPS and I received the same error message.

but inside my system (writed in Java) I changed all parameters and it's working. And inside my email client too.

HOST: mail.chameleon.global

[Fahad Siddiqui]

Good to know this your issue got fixed....

Please inform if anything else required from my side.

[Alexandre Oliveira]

No, the email problem it's not working inside Jira

The problem still inside Jira config.

[Fahad Siddiqui]

Are you able to ping the Ip address?

can you share the configuration page with screen shot

[Alexandre Oliveira]

Yes! I used inside my email client without problem , bit inside jira service desk I can't connect on server

[Alexandre Oliveira]

I tried to reconfigure and keep receiving the same error message "Socket Time out" and "SOCKS: TTL Expired", I think that Service Desk email config have a big problem to configure an external email.

[Alexandre Oliveira]

This is my config options

[Satyendra Narwane]

@Alexandre Oliveira@Fahad Siddiqui  This is related to network issue, You need to contact your network team

Please go in Run command.

Type CMD

Then type: Ping -a mail.chameleon.global -t

Monitor the reply status... there will be request time out i believe as there is issue in network connection

[Alexandre Oliveira]

@Fahad Siddiqui, I did it and it's working without problem

ping -a mail.chameleon.global -t

Pinging mail.chameleon.global [67.20.76.205] with 32 bytes of data:
Reply from 67.20.76.205: bytes=32 time=199ms TTL=51
Reply from 67.20.76.205: bytes=32 time=199ms TTL=51
Reply from 67.20.76.205: bytes=32 time=199ms TTL=51
Reply from 67.20.76.205: bytes=32 time=200ms TTL=51
Reply from 67.20.76.205: bytes=32 time=200ms TTL=51
Reply from 67.20.76.205: bytes=32 time=199ms TTL=51
Reply from 67.20.76.205: bytes=32 time=199ms TTL=51
Reply from 67.20.76.205: bytes=32 time=200ms TTL=51
Reply from 67.20.76.205: bytes=32 time=200ms TTL=51
Reply from 67.20.76.205: bytes=32 time=201ms TTL=51
Reply from 67.20.76.205: bytes=32 time=199ms TTL=51
Reply from 67.20.76.205: bytes=32 time=200ms TTL=51
Reply from 67.20.76.205: bytes=32 time=200ms TTL=51
Reply from 67.20.76.205: bytes=32 time=200ms TTL=51
Reply from 67.20.76.205: bytes=32 time=200ms TTL=51
Reply from 67.20.76.205: bytes=32 time=199ms TTL=51
Reply from 67.20.76.205: bytes=32 time=199ms TTL=51

Ping statistics for 67.20.76.205:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 199ms, Maximum = 201ms, Average = 199ms
Control-C

[Mikhail Iofik]

Got same error (SOCKS: TTL Expired)

[Ross Morrissey]

Me too. 

I have verified the IMAP settings with other tools and our provider (Bluehost).  I see a couple of "SOCKS: TTL Expired" threads out there that just go silent.  Is there a fix?  Thanks!

[Wiehan Aucamp]

Experiencing exact same issue now for no apparent reason. Network and mail server working fine with all other clients, only JIRA reporting this issue and we're unable to receive any incoming issues.

[Evan Nixon]

Same here!

[Ruben Lopez Z.]

me too

[Ruben]

Same here! If someone knows how to fix this, please post. Migrating to cloud didn't help.

[David Biagini]

Same issue here, neither IMAP or POP3 work with zoho email account 

[Muhammad Atif Lone]

Has anyone found a solution? This seems to be a simple configuration with Gmail but almost everyone getting the same error.