Cloudron Forum

I also hope that this feature will be implemented soon to prevent servers from ending up on blacklists. It will also help prevent users from sending mass emails without coordination. Virtually every mail provider has enabled this feature for good reason.

See this - https://docs.cloudron.io/email/#ptr-record

@macone see https://docs.cloudron.io/email/#firewall

@jdaviescoates totally confusing for sure. Not cloudron's fault completely as TLS is just an update to SSL. The problem comes from old software I think where SSL (the verb) is still being used where TLS should be. Both are technically the same, one is just newer. Or at least that is what google would suggest lol. Either way, you can never have too many docs so an update to specifically call this out when working with SMTP ports would be useful.

@SansGuidon you are absolutely welcome

@girish Perfect, thank you!!

@girish it worked quite smoothly in the end but decided to upgrade my hosting and then have everything on one server again. Backup time and size are an issue though. Especially having to wait until one is done before editing/adding or removing apps. Having a fast local disk to backup to helps though

@andreasdueren said in How can I block email addresses in catch all?: I thought these addresses are only checked for in the from fiel not the to? No, to the best of my knowledge it applies to any addresses in the mail. In any case this is how I prevent these kind mails from popping up in my mailbox. @subven said in How can I block email addresses in catch all?: via a mail sieve filter That could work as well, but another mailbox is not necessary. You can just filter on the recipient address.

@girish It is working now! I've found a good doc from Namecheap themselves: Namecheap DOC about Sendgrid It's important to not add the domain part in the CNAME entries! Hopefully this helps someone else in the future Thank you for your commitment @girish

I have made the slider start from 500M for a start.

Thanks a lot @girish ! We're running mattermost under the indicated domain. I have disabled the outbound, since we have an external SMTP server running - it works now! I didn't know that Cloudron overwrites configs, but well: Lessons learned

@Grienauer I think Services -> Mail -> Restart. This updates the mail server certs. Can you check if it works after that?

@RazielKanos said in can't send mails to gmail: The IP you're using to send mail is not authorized to send email directly to our servers. Please use the SMTP relay at your service provider instead. Learn more at https://support.google.com/mail/?p=NotAuthorizedError f13-20020a05600c4e8d00b003c6f97b761esi8416758wmq.104 - gsmtp Oh, I missed this. See https://support.google.com/mail/answer/10336?hl=en . Basically, google does not like your IP. Maybe they have blocked the whole IP range of your VPS provider . You have to use a relay - https://docs.cloudron.io/email/#relay-outbound-mails

@LoudLemur said in After self-hosting my email for twenty-three years I have thrown in the towel. The oligopoly has won.: @necrevistonnezr said in After self-hosting my email for twenty-three years I have thrown in the towel. The oligopoly has won.: @humptydumpty said in After self-hosting my email for twenty-three years I have thrown in the towel. The oligopoly has won.: Well, I host Cloudron in my home office with dynamic IPs on a NUC. Outbound email gateway is my very privacy conscious mail provider mailbox.org. For a small family, that’s more than sufficient. This is the coolest way to run Cloudron, the way that, I think, could bring Cloudron to the masses. If you ever have time and the inclination and could create some sort of "how-to" video explaining how to solve the tricky parts of accomplishing your setup, I think that could be massive for Cloudron. @girish @nebulon what do you think? The cool thing: it’s all already building into cloudron! Dynamic IPs DNS (in the network settings) and support for email gateways. The only thing you have to do on your side is to report your current IP regularly to the domain provider. This happens via ddclient, most commercial routers have a similar function build-in.

@girish with help from vps and hosting it is been solved. thank you for replying here

@BrutalBirdie So I figured this out, and it's definitely NOT a Cloudron issue. Actually, it's a Thunderbird issue... so I'll probably go write a quick report on Bugzilla at some point. It turns out that when you hook up two emails for Thunderbird that (1) go the same mail server and (2) share the same password, that causes Thunderbird to ignore the username. What this means: Let's say you set up two mailboxes in Cloudron, your.name@company.com and service@company.com. While your.name@company.com is accessible to you, service@company.com is instead accessible to a group you are a part of. You can use user account password to log into both. Let's say you first add your.name@compay.com to Thunderbird. It will work fine. However when you add service@company.com, outgoing will be messed up (though incoming will work). Rather than outgoing being registered for service@company.com, it'll go out through your.name@company.com, which is not the correct behavior. You can fix this by going into Outgoing Servers in Thunderbird, but it's a big pain it doesn't need to be, and I'm sure it's something that can be fixed on the Thunderbird end. Anyways, that was a fun dive into some email issues... hopefully I can get this fixed and jump back into using groups, as that helps make security issues with emails a little easier to deal with (no having to reset everybody's shared password). Hope you all have an awesome day!

@roofboard did you get this sorted out?

@foliovision Cloudron should create the DKIM records if you're using the DO API for your domains. Cloudron does not delete existing records so if you add something in manually, rest assured it won't get wiped by Cloudron. https://docs.cloudron.io/email/#dkim BTW, if you go to your Cloudron dashboard --> Email --> Status --> and click on "Redo DNS Setup", that should add in the required records. It should be listed as a TXT record in DO's DNS. Example: TXT cloudron._domainkey "v=DKIM1; t=s; p=TIDfKL7GCS...