Cloudron Forum

Did you check both ipv4 and ipv6? is there anything in the box logs? edit: i was wrong, cloudron does not check ipv6 (cc @girish maybe you can try host -t A <reverse-ip-address>.zen.spamhaus.org 127.0.0.150 on your server . This is what Cloudron does to determine if it's listed or not. If your IP is say 1.2.3.4, then reverse-ip is you have to look up 4.3.2.1.zen.spamhaus.org . If listed, it will return some loopback address

@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

@humptydumpty said in Email sending broken after updating to 8.2.x (due to IPv6 issues): Hetzner doesn't save the entry? This. Hetzner just says it's invalid.

Omg, for whatever reason the TLD did change from .de to .com (I have .de but not .com) so the failure was totally correct. No problems, nothing to see here, please close the case Happy holidays!

Well, the thing is that I can obviously rename folders in my own account(s) in order to work around this, but when migrating accounts for other family members, colleagues or clients it's harder since I will be asking them to change their folder naming habits just because the mailsystem can't handle it. To be honest I never ran into this with other mailsystems and I've used / tried a considerable amount of them in the meantime: Google (Gmail/workspace), Microsoft (hotmail/365), Zoho, Mailcow just to name a few and they all accept periods in folder names. As a result we got used to use periods in our folder names. I'm fine if the default stays as it is in order to not break anything for other people, but being able to change it when needed would be nice. And yes, there are possible collisions with the internal folders (new, cur, tmp) when switching to FS, but this can be anticipated by setting the DIRNAME variable to something unique. In regards with testing, I'm not sure this has a huge impact since the working of dovecot shouldn't change in any way when switching to FS.

That's great, thanks @girish! It seems to work now. I enabled it and followed the steps in the new documentation you linked to, and then ran doveadm -c /run/dovecot.conf index -A '*' from the mail container which started indexing everything. Just waiting for the indexing to finish to confirm it'll be good.

@LoudLemur You could do that. No problem. You can specify the mail server location to be any SUB and pick any of the domains you have set up in Cloudron. To make things even wackier, you could use multiple subdomains like sub.sub.domain.com as the mail server.

OK, https://support.google.com/a/answer/81126?hl=en has even more information. "ARC checks the previous authentication status of forwarded messages. If a forwarded message passes SPF or DKIM authentication, but ARC shows it previously failed authentication, Gmail treats the message as unauthenticated." Have to investigate https://github.com/postalsys/haraka-plugin-mailauth . But long story short, @vadim unfortunately the situation is gmail forwarding is probably not going to work until we implement this. I have no ETA to implement this feature.

nice i eventually figure it out thanks

Ok weird, this worked, I backed up apps and updated to Cloudron 8 but it's not working again. that file didn't change. I set it to google's public DNS and it was fine - I reinstalled tailscale and set override DNS to true which I think should fix it and let me keep using TS

Ah yes, you were quicker than me, all green again, so I guess that was just a temporary minor glitch Thanks for checking though!

@brettjhonson that looks like quite a clumsy service advertising. But thank you for the idea.

@Beardmancer said in Failed backups and email config issue since 8.0.3 upgrade: I decided to go ahead and try adding this to /etc/systemd/resolved.conf since it's easy enough to comment out. DNS=8.8.8.8 1.1.1.1 After doing that and restarting the service with systemctl restart systemd-resolved, things seem to be working correctly. The file /etc/resolv.conf lists nameservers now and a manually-initiated backup just completed successfully. Thanks for the hlep @nebulon ! In the future, is there anything I should look out for to avoid this? I don't know what caused it. Maybe it was the 8.0.3 upgrade, or maybe it was an Ubuntu update? I think I rebooted Cloudron for the latter recently. If there's a configuration I might have setup wrong, I'd love to correct it.