@nebulon Correct, but I just realised that in copying and pasting I appear to have missed something.
That's embarassing. In any case it has now worked and this is resolved. Thanks for the quick reply.
Is it maybe possible to change the order in which incoming mails are filtered? With sieve you can tell the server to discard mails that match certain criteria, but that only works for mails that have not already been classified as SPAM. i suspect this is not that trivial though because the sieve filters work at the mailbox level.
@ccfu The quarantine plugin only dumps the messages into a directory which is not overly useful because there is no UI to manage the quarantine.
because Cloudron does not provide a way to block or quarantine mails altogether based on central SPAMAssassin rules or sender addresses, as this can only be done using filters on individual mailboxes
We have global SpamAssassin rules - https://docs.cloudron.io/email/#custom-spam-filtering-rules .
I want to understand the use case better though. Is the issue here that spam is slipping through the SA filters?
@ccfu are you able to install it on the demo so I can try to understand what is different ? https://my.demo.cloudron.io (username / password: cloudron)
Apologies for forgetting to reply again in this thread and confirm the problem still existed. Thanks for reporting it upstream. Looks like it could in fact be reproduced and has been fixed.
The group account solution is what I had been using up to now but this had to be reset every time there was an update or the app was restarted.
No technical reason as far as I can tell, just apparently no interest on the part of the provider! It is probably a very infrequent need and in our case this only affects a subdomain of one domain that is currently hosted by the same provider of the DNS. Ultimately the website will be moved but I need the subdomain for staging.
@nebulon I also think plain database apps would be the way to go here. Patching the app code is complicated in this particular case, so for now I I will just go with an external database.
@nebulon I have identified that it is an issue with multisite and the setting
define( 'DOMAIN_CURRENT_SITE', 'xxx.de' );
in the wp-config file. This does not seem to be getting updated automatically and hence the change needs to be made manually (and also in the database).
Sorry, I didn't mention that it was a mutlisite installation before because I couldn't see any reason for that to affect the smtp plugin settings.
