Cloudron Forum

@girish Mailgun. It hasn't happened again (so far). BTW, the notification error listed only two out of ten domains (all using Mailgun).

@TechoutDev To debug, open the mail logs window. Mail -> Logs button in top right. And then there is another logs button inside it. Keep that browser window open. Then, use the send test mail button - https://docs.cloudron.io/email/#send-test-email . Can you please post what's in the logs?

@hollosch

We didn't get to the bottom of this but the user solved it by moving to sendgrid.

@girish Wow that worked perfectly, thank you so much!

@nebulon Thanks for helping me work through this!

This got sorted out by @ntnsndr by contacting linode support. The VM had to be rebooted after linode unblocked port 25.

I updated the email relay page with newer screenshots of the SES console - https://docs.cloudron.io/email/#amazon-ses

@d19dotca thank you, I appreciate your quick response and correcting on the wrong topic! I did the search indeed, but I guess it was a wrong search query

@subtlecourage said in Outbound SMTP not working on my External Relay: It says it should be coming from noreplay@domain.com, but instead it is coming from imanalias@domain.com Can you clarify what you mean by "it says"? Is there some error/warning somewhere? Also, I assume that you have put a custom domain in fastmail and also fastmail is able to relay mail as any email address i.e <anything>@domain.com ?

@girish said in Email into apps - DNS/MX/CNAME/TXT: You have to setup the CNAME/TXT for the root domain and not for my.example.com. You don't have to set it up for each app individually Thank you. That was my main issue.

Nevermind, I did not realize sendgrid setup was only for sending email, I see the other parts to setup for receiving email now. Please disregard.

@dantheman https://mxtoolbox.com/emailhealth is another good one.

The root cause for this was the Cloudron server had the hostname as "box.domain.com" (same as the relay). Debian/Ubuntu has a quirk that it will put the hostname in /etc/hosts to resolve as 127.0.1.1. This meant that when we try to set it as relay, it resolves to 127.0.1.1 instead of the actual IP. To add to the confusion, I suggested using the host command which does not use /etc/hosts (i.e the nsswitch mechanisms) and uses only the DNS. If I had suggested using ping then we would have narrowed down the issue more quickly... Anyway, the fix is simply to hostnamectl set-hostname somethingelse.domain.com and also edit /etc/hosts (for some reason, hostnamectl doesn't change hosts file even after reboot, ).

@drpaneas said in gmail blocks my server?: @jdaviescoates I have cloudron installed at home. Ah, right.

@girish Awesome thanks.

@msbt thanks! I will try to see if I can make this just "work" in the next release.

@girish I originally tried that with no success, I figured that the Ghost CLI command initiated some other process or method

@marcusquinn I think DNS automation (provider specific) atleast needs to come from elasticemail itself ideally. It's not possible to keep track of all the DNS records each provider wants to set and if it's even available with API. It's basically impossible to test on our side atleast.

@Mastadamus said in Seeking recommendations based on experience for Sendmail Relays: Mailgun seems like a better deal for those not using a massive amount of emails a month. Yeah, they are the only one I've tried because you have to use it for Ghost newsletters. But I've never paid anything for it because you can send up to 5000 emails a month for free and I don't send anywhere like that amount.