upgrade tls timeout from inbound gmail

[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.