upgrade tls timeout from inbound gmail

[natzilla]

I am really baffled by this problem I am having. Every email from gmail to the inbox can't be received because of a timeout after it's trying to upgrade the tls

Oct 04 09:24:17 [INFO] [B2ED6280-367A-4095-95EE-B6D2484234B8] [spf] scope: helo, result: None, domain: mail-pl1-f171.google.com
Oct 04 09:24:17 [DEBUG] [B2ED6280-367A-4095-95EE-B6D2484234B8] [core] hook=ehlo plugin=spf function=helo_spf params=mail-pl1-f171.google.com retval=CONT msg=""
Oct 04 09:24:17 [DEBUG] [B2ED6280-367A-4095-95EE-B6D2484234B8] [core] running ehlo hook in limit plugin
Oct 04 09:24:17 [DEBUG] [B2ED6280-367A-4095-95EE-B6D2484234B8] [core] hook=ehlo plugin=limit function=max_errors params=mail-pl1-f171.google.com retval=CONT msg=""
Oct 04 09:24:17 [DEBUG] [B2ED6280-367A-4095-95EE-B6D2484234B8] [core] running capabilities hooks
Oct 04 09:24:17 [DEBUG] [B2ED6280-367A-4095-95EE-B6D2484234B8] [core] running capabilities hook in tls plugin
Oct 04 09:24:17 [DEBUG] [B2ED6280-367A-4095-95EE-B6D2484234B8] [core] hook=capabilities plugin=tls function=advertise_starttls params="" retval=CONT msg=""
Oct 04 09:24:17 [DEBUG] [B2ED6280-367A-4095-95EE-B6D2484234B8] [core] running capabilities hook in cloudron plugin
Oct 04 09:24:17 [DEBUG] [B2ED6280-367A-4095-95EE-B6D2484234B8] [core] hook=capabilities plugin=cloudron function=hook_capabilities params="" retval=CONT msg=""
Oct 04 09:24:17 [DEBUG] [B2ED6280-367A-4095-95EE-B6D2484234B8] [core] running unrecognized_command hooks
Oct 04 09:24:17 [DEBUG] [B2ED6280-367A-4095-95EE-B6D2484234B8] [core] running unrecognized_command hook in tls plugin

[core] Upgrading to TLS

[core] SNI servername:

my.xxxxxxx.com
Oct 04 09:24:46 [NOTICE] [B2ED6280-367A-4095-95EE-B6D2484234B8] [tls] timeout setting up TLS
Oct 04 09:24:46 [INFO] [B2ED6280-367A-4095-95EE-B6D2484234B8] [core] hook=unrecognized_command plugin=tls function=upgrade_connection params=STARTTLS retval=DENYSOFTDISCONNECT msg=""

I can't figure out if gmail is causing this or the cloudron mailbox. Any guidance towards the right direction would be so helpful.

Current version is v7.3.0

[girish]

@natzilla so, sending email to gmail works but just not receiving?

Do you think you can send a test email to test@cloudron.io from gmail and drop me a note? I can check from our side if our server's are dropping gmail as well. FWIW, I tried with my personal gmail and it works fine.

[natzilla]

@girish I have sent a test email from the gmail account addressed to you.

[girish]

@natzilla thanks, received the email (CALqQHLt454OY4dCnAPhKNm4n6Pb3sYV4uejeE++wCzH_L+hjqg@mail.gmail.com) .

Just to get a few more things out of the way: are other servers able to send email? I have replied to your test email, did you get it?

[natzilla]

@girish I did get your email. I've also had the same outcome when I send from the cloudron email. I will get them just fine.

I've tried sending from an outlook account from my work and I never get that either. If I test from AmazonSES using my gmail in the verified identity it comes in

[girish]

@natzilla Can you try this:

• Go to Services view, Email -> Configure -> Enable Recovery Mode . This essentially creates the mail container but does not actually run it.

• Now, SSH into the server and docker exec -ti mail /bin/bash . In the shell, run /app/code/start.sh . This will start the mail server and will also show all sorts of debug logs.

• Now, send email from gmail. Would be good to see what the logs say. Can you please send it to support@cloudron.io and I can take a look.

Thanks!

[girish]

Forgot to mention that once you collect the logs, you can disable the Recovery mode and the mail server will start again automatically.

[natzilla]

@girish I will get on that right away and send it over email. Should I reply to the one you sent me or send a new one?

[girish]

@natzilla Either should work, whatever is convenient for you.

[natzilla]

@girish I'm getting a unable to find image 'mail:latest' locally followed by a docker error.

sudo docker run -ti mail /bin/bash
Unable to find image 'mail:latest' locally
docker: Error response from daemon: pull access denied for mail, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See 'docker run --help'.

[girish]

@natzilla whoops sorry, I meant docker exec and not docker run. I have fixed my original comment.

[natzilla]

@girish i have sent you the ssh session to you in the email.

[girish]

@natzilla Did you get this sorted out? Sorry, test@cloudron.io emails get cleaned up periodically and I might have lost your email. Can you send it to support@cloudron.io if this is not resolved yet?

[natzilla]

@girish Thanks for getting back. Yea I was able to sort this out. It appears it might have been related to the route I had established for internet traffic.

Strange that it would only effect gmail, but this new route is simpler, and testing shows all mails being delivered without issue.