@girish thank you for explaining. In my case it is easier to:
spin up my old server
modify my (local) host file to point the dashboard domain to the old IP
use the Cloudron web terminal to access MySQL and apply the fixes
press the apps backup button and download to backup config afterwards
revert host entries and import the apps backup config on my new Cloudron
This way I am only using tools that are already shipped with Cloudron without the need of other software.
This is fixed for next release with https://git.cloudron.io/cloudron/box/-/commit/3477cf474f32a51c62aef65015e615db62bca4f7
For the other feature request about domains, please make a separate thread there, but I can already say that Cloudron is still designed to work for a setup of one Cloudron per organization and not many maintaining isolated organizations on one Cloudron. This will add all kinds of complexities for the 99% use-cases Cloudron is currently used for.
@humptydumpty sounds reasonable. "Send copy to" using SRS could fail depending on SMTP features and "forward to" (not using SRS?) should work. I don't think its an real issue but I also did not find any helpful documentation regarding Cloudron and this constelation. Also bad UX in the end ^^
@peterle Yes, sure. We need to bring up the package at https://github.com/M-arcus/friendica-docker-image up to speed. It was packaged 3 years ago, so it probably won't work now.
@msbt hmm you are right and I was wrong! I'll test if it works and report back
EDIT: Okay it works but only for new accounts (at first login with LDAP or local accounts).
The part in my homeserver.yaml looks like this:
auto_join_rooms:
- '#discuss:yourdomain.com'
- '#feedback:yourdomain.com'
- '#help:yourdomain.com'
- '#info:yourdomain.com'
Actually, it seems a better way to confirm this is the apt package version and not the dovecot version. The latest one (i.e one which will be in next release) shows this:
root@e4d2eb1cba0b:/app/haraka# apt list --installed 2>/dev/null | grep dovecot-core
dovecot-core/bionic-updates,bionic-security,now 1:2.2.33.2-1ubuntu4.7 amd64 [installed]
The current cloudron container has 1:2.2.33.2-1ubuntu4.6
@subven Have you read https://docs.microsoft.com/en-us/office365/securitycompliance/use-the-delist-portal-to-remove-yourself-from-the-office-365-blocked-senders-lis ?
You should be able to get your specific IP delisted.
Okay I think my request is already solved since I did not read the documentation. I will check the "is an external EXT4 Disk" checkbox for the future Maybe I did not think it through when I made the setting. On the other hand, the description might be clearer. Thanks in any case for the documentation.
PS: Haha thank you @nebulon I solved it myself while you where typing. Yes the Checkbox could be more obvious.
Changed As it is the default configuration for Roundcube it is working like intended and we could leave it like this? I don't think its a rare use case but maybe it could be added to the documentation (which I always found very helpful).