Mailgun Setup Issues

[girish]

The dkim selector is set in the database. You have to update it manually like this:

mysql -uroot -ppassword -e "SELECT * FROM box.mail"

The above output will show dkimSelector. It will be line cloudron-<yourdomain-nodots>. You can update it like this (be sure to replace the domain.com with the domain name (first column in above output) and currentdomain-nodots with your dashboard domain:

mysql -uroot -ppassword -e "UPDATE box.mail SET dkimSelector='cloudron-currentdomain-nodots' WHERE domain='domain.com'"

For example, if your current dashboard is at my.dashboard.com then the dkimSelector is cloudron-dashboardcom (this is just a convention).

Then systemctl restart box should be it. In the email status view, you can also click on re-setup DNS records to push the change to the DNS.

[will]

Much appreciated!

[A Former User]

Hi, having the same issue. Not sure what you said helps. I've set up a new domain, mg.example.com, with cloudron being hosted on example.com (and my.example.com). I wonder whether the difference between Cloudron using STARTTLS vs Mailgun using SSL/TLS is the problem?

Not really sure.

[girish]

@edapm What error are you seeing? Any screenshots or error messages will help.

[A Former User]

@girish

[A Former User]

@edapm Also not sure IMAP is working, how do I check?

[girish]

@edapm said in Mailgun Setup Issues:

@edapm Also not sure IMAP is working, how do I check?

How did you check if IMAP is working or not? Are you not able to connect with your mail client?

[A Former User]

@girish I sent an email via another email to the address and it timed out after 44 hours.

[girish]

@edapm Ah, incoming mail is still SMTP. IMAP is used just by mail clients to get emails for users.

I see that I cannot connect to port 25. This is why incoming mail does not work. Where is your server hosted? Do you have a cloud firewall in the front? If so, you have to open up incoming port 25. Please see https://docs.cloudron.io/security/#inbound-ports for the various ports you need to open in the firewall.

root@my:~# telnet my.forgenst.com 25
Trying 51.140.109.177...

[A Former User]

Hi @girish, yes I'm using Azure so port 25 is blocked, I cannot unblock it.

[girish]

@edapm Outbound port 25 is usually blocked (this is why you need a mailgun relay). But incoming port 25 is usually not blocked and this is something you setup in your azure firewall. This is the same as what you did for port 22/80/443. Just put 25 there as well.

[girish]

@edapm https://docs.microsoft.com/en-us/answers/questions/4059/azure-vm-smtp-inbound-port-25-is-blocked.html

[marcusquinn]

I'd seriously consider anything other than Azure / AWS / GCP if you value your costs and time. So many faster, easier and cheaper solutions. Let us know if you have specific requirements as there's a ton of alternative and happier hosting experience among this community.

[A Former User]

Hi @marcusquinn, yeah I only use Azure because I get free credits via the GitHub Developer Pack. Do you know any good (preferably free) alternatives?

[marcusquinn]

@edapm Personally, I'm all-in with Hetzner, not free but the best value for features I've found, particularly having network DDoS protection as standard. Others recommended include Contabo and Scaleway.

If you're getting free (inclusive) stuff from Microsoft then I suppose that's decent. Personally, I'm all GitLab, so anything GitHub is second-choice.

I guess there's nothing truly free, including your time, but those are the options I recommend, otherwise it's support tickets to Azure and hope for their ability to allow for port needs.