Cloudron Forum

@affinity @girish as in set them a global profile which then get picked up by any apps via ENV VARs? Then you'd just need an app restart.

@girish Oh that is interesting, I didn’t realize we could customize the DNS server. This is helpful. Thanks so much!

Hi @fbartels You're right, double checked and it always defaults to smtp. instead of .my When manually changing on both PC and Mobile, the SMTP accounts can be added without the certificate error! Thanks Everyone!

@flaxxain RainLoop app is long deprecated . Consider using SnappyMail , Roundcube or SOGo

I changed the mail server here. The DNS was updated and no SSL errors.

Could you please convert that thread into a request to remove 'Cloudron' from the mail templates as well as from translation files, please?

One idea, to get more insight, you can use the following command to see which ciphers openssl would use, while you can control what it offers: openssl s_client -starttls smtp -connect my.YOURCLOUDRON.DOMAIN:587 -cipher 'ECDHE:!aNULL' -tls1_2 So ECDHE:!aNULL can be replaced with a cipher you are certain that other server supports.

Hi, did you check this, this and this? I got the similar errors when trying to run the indexing but after a few retry it works. I tried to index email mailbox separately (by running the command inside the rebuild-index.sh for each mailbox separately) and identified which one caused the problem, then I had to open/read the problematic folders with a mail client, and then the index worked. Given this feels like another duplicate, @staff, there might be something up / to improve with how the indexing is handled.

Yeah can confirm, and thanks for the help diagnosing. I wasn't given any advanced notice of the SMTP block, it was hidden in release notes somewhere. This is now unblocked.

@BrutalBirdie Ok fixed. The Cloudron did not even show me that. I have fixed the issue now.

Maybe. But I think I'll just take the extra GB into account and see dynamically if and when issues arise. So far, nothing has been missed.

@jdaviescoates Everywhere, basically. Would it be possible to setup Nextcloud so that people could inhabit and use it without ever seeing each other's emails? If you are on a nextcloud and you look at the Users list, even as a regular user, you will probably see everybody's email listed there. There might be some environments where you would not wish participants to have their emails disclosed to the rest of the nextcloud.

@girish Thanks for renaming. It appears that SPAM mails are showing up even if not selected in the filter though.

You can also follow this great guide and set up an automated blocklist update: https://forum.cloudron.io/topic/3795/firewall-spamassassin-automatic-list-update/41?_=1740739173375 Might mitigate some (few) of these annoying spam attacks.

@neki The misconfiguration warning is for your IP and has no relevance for incoming mails. That warning is being shown because Spamhaus is not reponding correctly to the request from Cloudron and Cloudron is incorrectly interpreting that as your IP being blocklisted. It is nothing more than a display error though and should be fixed in the next release. If you are seeing incoming mails rejected due to Spamhaus listing then this is due to the DNSBL checking. The error may well be with Cloudron and how Spamhaus reports are interpreted, but that will be resolved if you deactivate the checks. @SansGuidon Had you removed Spamhaus from the DNSBL checks? I think the issue is (at least partly) to do with changes in the way Spamhaus processes queries (I noticed a lot of errors in the logs before deactivating Spamhaus altogether) and the way Cloudron interprets the results when errors are thrown. I have two Cloudron servers, both running version 8.3.2, but one on Ubuntu 22.04, the other on Ubuntu 24.04. Interestingly, the server running on 24.04 does not show the (false) email configuration error, but the one on 22.04. regularly does. As already mentioned, however, that is just an icorrect message and has no affect at all on deliverability as that will depend only on the receiving mailserver.

@IniBudi @nebulon I can confirm that problem is not related to Cloudron, after I did some sending tests.

@scooke if you have an account, can you are share a screenshot so we can copy get inspiration from?