Setup mailjet as mailserver does not work

[Fabix]

Hello!

I try to set up my mailjet account as smtp server.

I get the following error: getaddrinfo ENOTFOUND in-v3-mailjet.com

Username and API Key is correct (I use this in another app, too)

SPF setup is correct, as I can see in the mailjet console.

Any ideas?

Thank you!

[msbt]

@Fabix not sure about the missing username, but your SMTP host has a - instead of a . (should be in-v3.mailjet.com)

[Fabix]

@msbt

oh man so sorry..

yes it was the wrong smtp host...

In mailjet it was not possible to copy the host.

[saikarthik]

I still get the error: getaddrinfo EAI_AGAIN in-v3.mailjet.com
Additionally, just saw that my cloudron server is not able to access anything outside, including AWS Route53 for MX record verification.
Also, when I try to ping www.google.com I get the error: ping: www.google.com: Temporary failure in name resolution

Any ideas?

[girish]

@saikarthik Can you check if unbound is running? Under Services -> unbound . Otherwise, restart it. We use unbound as the DNS server and it looks like DNS resolution is not working on your server.

[saikarthik]

@girish yes, that was the issue.
These links helped:
https://docs.cloudron.io/troubleshooting/#unbound
https://forum.cloudron.io/topic/2106/dns-status-tool-reports-null-on-all-records?

[luckym]

Hey, re-using this thread as I am having some issues setting up mailjet as a relay mail provider.

I followed Mailjets instructions to set up SPF and DKIM records and validated the domain, everything looked good. Unfortunately triggering a test email does not deliver it even though the event log for mail says it was delivered. An email from Vaultwarden was delivered, though it was sent to an email address from the same domain. The Mailjet analytics dashboard says 0 delivered emails. Would be great if anybody can point me at a potential solution.

I created a new subaccount API key in Mailjet and used the API key as the username and the Secret key as the password in Cloudron's relay settings.

[luckym]

I was able to resolve this. I created a subaccount API key that I used for authentication before generating a secret key for the primary API key (by default Mailjet creates a key but not a secret for that key, which is a manual action). Now I just generated a secret key for the primary API key and used this instead of the subaccount key and it worked.