Cloudron Forum

@girish Would be amazing to have this feature yes

@girish Perfect, that solved it. Thanks!

Fixed in https://git.cloudron.io/cloudron/box/-/commit/ce426808889cb4c3dee8b64f6964311bce964cfa

@aqeelzakir-com said in SPF DNS record (TXT) did not match.: Relay error: Connect to port25check.cloudron.io timed out. Check if port 25 (outbound) is blocked Email Status is checked every 30 minutes. See the troubleshooting docs for more information. See https://docs.cloudron.io/email/#outbound-ports . Basically, your server is unable to send mail because outbound port 25 is blocked. You have to either get it unblocked by talking to your VPS provider or you can set up a relay. Expected: v=spf1 a:my.example.company include:_spf.google.com ~all Actual: v=spf1 include:_spf.google.com ~all If you are going to use a relay, the error above will go away automatically. Otherwise , you have to add a:my.example.company into the SPF record in the DNS.

After quite some time - almost two years - I would like to know if this improvement can be considered for some future release in 9.X ?

@paradoxbound if I enable Dane, should I enable MTA-STS?

@girish Ah okay... Thanks.

Closed due to inactivity

There are some hard coded rate limits - https://docs.cloudron.io/security/#rate-limits

@ccfu I think that would be the best idea.

@alexm said in Spamhouse blacklist: I am kind of struggle to understand is it the problem of OVH or the way Cloudron uses this Spamhous open relays? VPS providers have a block of IP addresses and they cycle these IP addresses across their customers as VMs keep getting created and destroyed. This means that your IP was used by someone else previously and maybe they sent a lot of spam (an unfortunately common situation). When this happens, spam watchlists like SpamHaus place the IP address in their email blocklist . In some cases, people will wholesale block the entire VPS provider IP address range since the VPS provider is not responding to spam appropriately. There is a lot of unknowns here since all this handling is not "transparent" - an email receiver can use all sorts of blocklist providers and unknown criteria to determine if your email is "spam" or not. They might even block emails by domain name etc. Your best bet for reliable email is to sign up and use a relay - https://docs.cloudron.io/email/#relay-outbound-mails . If you don't want to use a relay, you have to be "patient" to give your IP and domain a good reputation . You have to also get your IP/domain whitelisted from the various email block list providers. Most of the email blocklist providers have an online form that you can fill up to prove your reputation.

Thank you @laurent I'll try something like that.

@necrevistonnezr said in MXtoolbox: Which site? Sorry, I forgot to include the link. I have updated the post now. mxtoolbox

Setting up the sieve rule means I have to have the password and set all of that up. Using the "mailing list" settings means I don't have to do any of that, don't need to create an inbox, and it doesn't need to be owned by any accounts (and cloudron users with email admin / admin / superadmin can modify as needed). [image: Screen Shot 2023-12-15 at 5.08.26 PM.png] So I guess I answered my own question I'll write it up. for people who ask in the future. "How do I set up email forwarding to external accounts without having to provision Cloudron accounts" == mailing list. @luckow thanks for the SoGo -- looks like that does take care of everything.

@cylon usually, you can request your VPS provider to open that port and they might if they trust to now spam Alternative is to setup a relay - https://docs.cloudron.io/email/#relay-outbound-mails

@foliovision it's in https://docs.cloudron.io/apps/#email See the note. But to be fair, it's hard to read through all the docs in detail.

OK, I finally worked on this AGAIN and remembered how messed up this is conceptually. username: groupname@domain password: (any one of the passwords of the people that have access) This is also makes Freescout work for me https://forum.cloudron.io/topic/12976/connection-could-not-be-established-with-host-mail-domain-com-connection-timed-out-110/43 A single "username" having multiple passwords is what messes me up every time.

Thank you, gentlemen! This worked. I hope that a summary of this explanation is included in the documentation.

I will mark this as solved but feel free to open a feature request post.

@eddowding this is a feature request I don't think you're the first to say it either.