Cloudron Forum

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?

Ok, I understand that. The case which you're saying is different. If anyhow the user doesn't have access to the Admin and just the user account is compromised then he can send emails from that account only and if admin has setup limits over that then the spammer can't go beyond the limits. Limits should be setup in any case and should be controlled by Admin. This is a very important and good feature that needs to be implemented. I hope you understand. Thanks!

@JohnBee said in email server broken after update...: snapshots to fall back-on You restored the entire server to a previous working state?

@osobo the power of the forum, thanks are due to @jdaviescoates and all those who went before on this issue.

@joseph said in Frequent Email is not configured properly notice: Maybe DNS is periodically failing on your servers. Do you know which DNS servers your server is using? You can use resolvectl to figure this. Thanks for the explanation! my DNS servers are : Current DNS Server: 1.1.1.1 DNS Servers: 1.1.1.1 9.9.9.9

Looks like this part does fix it (instructions for root server): [image: 1737492462373-9fbbe904-6e2e-4deb-8d7d-5d2812a54c83-image.png] Thanks to you both for the pointers!

working now. thx

I use netcup too, I disabled IPv6 on the server entirely and since everything has been working with no issues. Though disabling IPv6 persistently on reboot was not straightforward and had to be done modifying netplan config, see above on the thread (https://forum.cloudron.io/post/102554).