I have pushed out 1.4.2. Note that the package is a "major" version upgrade since the UI is kinda different (so you have to click update manually in the Cloudron dashboard, it won't auto update).

My point of the 443 port issue was so ya'll could fix the docs. I have manually setup SRV records, that's why I thought it'd be nice to automatically set them up. Also, I meant to put this under discussion, not sure how it ended up in support. Thanks.

@subven I use sendgrid with great success

@d19dotca Indeed, there was a typo in the eventlog code. I have fixed it for the next release - https://git.cloudron.io/cloudron/box/commit/ae5722a7d4865a1924737a7e7d1697c6c9b94d6e

yes, that tag-input component has several other small bugs and we should really replace it. If anyone knows a good angular1 based component to replace it, ideas welcome

@rfg Agree that Cloudron should not accept emails from spoofed sources. We do have code and configuration in place to block this. Let me investigate.

Also, note that changing the nameserver sometimes takes a bit of time. So, you might have to wait a bit between step 2 and step 3.

@d19dotca Currently, there is no way. The SA settings are set in stone. I can open up our mail addon git repo tomorrow so you can get a better idea of how we have implemented it. But overall, our idea was that customers don't have to deal with implementation details like SA (for example, maybe we use rspamd later) and that spam detection should just work. If you have SA expertise, I am happy to incorporate your suggestions into the default settings.

@murgero No, I came from hardware/mailserver docker containers, which is located here for reference: https://github.com/hardware/mailserver It was one of the best mail server suites I had hosted. I moved to Cloudron for saving money as I no longer wanted to have a dedicated mail server when I had to have one for Cloudron too, and while it's been a good experience overall I can't seem to get the spam filtering to work at all off my marked spam messages from the spam folder. It seems to block some at the SMTP level when it receives a message that's on the blacklist, however it seems like it's completely not capable of learning anything from my spam folder. Most messages are very similar in subject, content, format, etc. There are 193 messages in my Spam folder right now since just July 12th, so just over half a month. Almost every single one of those originally ended up in my inbox, several a day, that I have to manually move over to the Spam folder in hopes of it learning it. It's always possible something is wrong in my install maybe, and I'm happy to troubleshoot that, but in my personal experience SpamAssassin really isn't as effective as Rspamd from the different mail servers I've hosted over the years. Once I moved to Rspamd, it was as if it caught 98% of my spam and they showed up in the Spam folder as desired. Right now I'd say maybe 5% show up in my spam folder under the Cloudron mail server.

@dustinddotca If you add a CNAME record manually from mail.example.com to my.example.com that should work. Your email client might complain about certificate hostname mismatch but this is unlikely.

@girish Thanks for your response!

@girish Just as a quick add-on, if you have Comcast business class, port 25 may be allowed by calling the business support line. Same with ATT.

Another option is to simply Disable mail and then Enable mail for the domain. This will effectively end up copying the certs.

@rfg This was a bug in our previous version. You can fix this by going to services -> mail -> restart. You have to do this only once, future certificates will be setup correctly.