Amazon SES SMTP Rely - Emails Not Going Out

I recently installed Hestiacp and I am using Amazon SES as the SMTP rely. I have verified the domain but I am still unable to send emails externally. I can receive from external senders and can send emails internally but just not getting out.

Looked at other posts but not seeing a solution or good recommendation to troubleshoot.

Thanks in advance.

check exim mainlog, first step for debugging mail troubles.

1 Like

Thank you. Anything I should be looking for? It’s a pretty big log. Don’t want to post the whole thing here.

Sorry. Brain fog.

So it appears that the messages are “frozen”. Here’s a the log:

2023-02-22 17:02:03 1pUjJC-001DSN-Ie Message is frozen
2023-02-22 17:02:03 1pUrtS-001W3h-Fc == [email protected] R=send_via_smtp_relay T=smtp_relay_smtp defer (-53): retry time not reached for any host for 'gmail.com'
2023-02-22 17:02:03 1pUrtS-001W3h-Fc == [email protected] R=send_via_smtp_relay T=smtp_relay_smtp defer (-53): retry time not reached for any host for 'gmail.com'
2023-02-22 17:04:14 1pUVj7-000hBE-ID H=alt1.gmail-smtp-in.l.google.com [108.177.104.27] Connection timed out
2023-02-22 17:04:14 1pUVj7-000hBE-ID == [email protected] R=dnslookup T=remote_smtp defer (110): Connection timed out
2023-02-22 17:04:14 1pUsXO-001ZTb-13 <= <> R=1pUVj7-000hBE-ID U=Debian-exim P=local S=2393
2023-02-22 17:04:14 1pUsXO-001ZTb-13 remote host address is the local host: www.imammarc.com
2023-02-22 17:04:14 1pUsXO-001ZTb-13 == [email protected] R=dnslookup defer (-1): remote host address is the local host
2023-02-22 17:04:14 1pUsXO-001ZTb-13 Frozen
2023-02-22 17:04:14 1pUIJl-0003PL-2c == [email protected] R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host for 'gmail.com'
2023-02-22 17:04:14 1pUVp7-000hJQ-04 == [email protected] R=send_via_smtp_relay T=smtp_relay_smtp defer (-53): retry time not reached for any host for 'gmail.com'
2023-02-22 17:04:14 1pUVeZ-000gW7-56 == [email protected] R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host for 'gmail.com'
2023-02-22 17:04:14 1pUIVc-0003zX-CD Message is frozen
2023-02-22 17:04:14 1pUHxl-0000ma-IG Message is frozen
2023-02-22 17:04:14 1pUVlF-000hG6-Pg == [email protected] R=send_via_smtp_relay T=smtp_relay_smtp defer (-53): retry time not reached for any host for 'gmail.com'
2023-02-22 17:04:14 1pUHkq-000EZV-TR == [email protected] R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host for 'gmail.com'
2023-02-22 17:04:14 1pUhIb-0016c4-Gj Message is frozen
2023-02-22 17:04:14 1pUfrl-0012Zc-Uc == [email protected] R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host for 'gmail.com'
2023-02-22 17:04:14 1pUJyD-0008QN-Ac == [email protected] R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host for 'gmail.com'
2023-02-22 17:04:14 End queue run: pid=374116

How did you set it up?

Ubuntu 20.04LTS

Using Amazon SES for SMTP Rely. Here’s a couple of screenshots. Any other details you’d like to have?

I am using the username/pw from the SES console.

Image 2-22-23 at 10.43 AM (1)

Also not sure if this will help but I saw this in the log and asked ChatGPT to help me understand what the issue is and it said:

The error message "sender verify fail" indicates that Exim was unable to verify the sender's email address. In this case, the sender's email address was "[email protected]". The error message "all relevant MX records point to non-existent hosts" indicates that there was an issue with the MX records for the domain, which could be causing the sender verification to fail.

I used an MX tool to help analyze what’s going on. I have this for my DNS records:

It seems to me you are not using your smtp relay, but trying a direct connection to google.

1 Like

that’s just part of the pathway of my domain trying to contact Google.

Things have gone from bad to worse. Now I can’t even receive email from outside. Completely stuck in the mud.

Why would you contact Google if you want to use an SMTP relay?

Should your MX record not point to the hestia server? It currently points to amazonaws.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.