@d19dotca Inspecting a few mail servers that I can ssh into it seems all the sieve files are -rw------- and all the mailboxes are drwx------. Was this server restored from a backup by any chance? If so, that would maybe explain the discrepancy. But even then I am not sure why some of the mailbox folders have pretty bizzare permissions like "r-x" for group/others. I think you can safely change the permissions to the ones I listed above.
@d19dotca Just got around to looking into this. This doesn't work because the mail server processes spam messages using dovecot's sieve_before flag - https://doc.dovecot.org/settings/pigeonhole/#plugin-sieve-setting-sieve-before . You can check the /app/dovecot-config/sieve_before/spam-move.sieve script in the mail container which is moving X-Spam-Flag into the Spam folder. Because the filter below is run before user messages, your filters don't work. This also makes it easy for the end user to not worry about processing spam messages when writing filters, so I think the default behavior is good.
require ["fileinto","mailbox"];
if header :contains "X-Spam-Flag" "YES" {
fileinto "Spam";
stop;
}
For the original use case of discarding all spam for forwarding mailboxes, this is the default behavior in next release.
This doesn't answer the question but the multi-server feature is intended to distribute the apps over multiple servers/nodes. The design is not for providing HA functionality.
@svallory If I understanding correctly, you want to specify the setting names like S3/SITE_NAME/SITE_DESCRIPTION etc and then these variables can then be configured by UI ? Also, I guess you are expecting these variables to become exposed as environment variables to the app?
Haven't tried but echo "yes" | ./cloudron-setup probably works as well to automate reboot.
[1.3.0]
@eddowding usually when you install an app and then click on the app grid icon of the installed app the first time, it shows a dialog with those details, which you have to explicitly acknowledge.
@alexsunny123 ok there are quite a few variables in the mix here it seems. For a start, can you connect to the Cloudron setup view using the public IP address from your ISP on port 80 and 443?
To rule out some other maybe interfering parts, disable the Cloudflare proxying.
Since you mentioned email, on a residential connection you will most likely require a mail relay to work properly, anyways port 25 will most likely be blocked by your ISP. Cloudron as mail relay support for various providers though.
Lastly for Cloudron it doesn't really matter if bare-metal or VM, so there are no special docs about this. You should be fine as long as you have vanilla Ubuntu 20.04 server installed.
[1.10.11]
[1.7.8]