Inter-Domain Aliases is great
but I feel one piece is still missing
what about having a catchall@ aliases
I'll try to explain
my mail email is: email@example.com
which catch all for the domain.tld
I also make alias firstname.lastname@example.org and email@example.com
but those 2 domains (firstname.lastname@example.org and email@example.com) can't have a catchall unless I configure a mailbox for it.
I believe it would be nice a have the possibility to have a catchall@* or at least to be able to configure the catchall@ with another domain such as firstname.lastname@example.org redirected to email@example.com
👍 Internally, there is already a way to set custom env vars (you can do this only in the CLI currently, cloudron env). So, we have to update the manifest and the UI to use those fields and set env vars.
@scooke i understand the problem and suffer the same issue : "what have I done already?"
So I've started using a wiki from Cloudron store to document my setup. Settled on Dokuwiki. But I changed the app display icon to personalise it (and because I hate Dokuwiki's default icon even though the app is good). So just now had to do what you described to find out what I had actually done.
Might be a niche request, but you're not alone.
@humptydumpty that's correct, this feature didn't get implemented. The 2FA is only implemented on the Cloudron side and not for the apps. There was a parallel discussion going on about how to show what kind of auth is being used in an app in the dashboard. I think we need to show some indication to the user about how to log in before implementing this feature.
Just an FYI - I recently found (thanks to @girish for setting the wheels in motion for me to dig into this) that there is some form of whitelisting/allowlisting in SpamAssassin via Cloudron's UI. It's not perfectly matching what we are looking for in this feature request, but should help buy some time for those who need this capability right away. Here's the goods on it:
The pros: you can use this right away!
The cons: It's not a true "whitelist" since spam processing still proceeds (a true whitelist/allowlist in my mind means it completely skips spam processing completely), but setting the score to be incredibly low should effectively force all messages that may have otherwise been "spam" into the inbox for the user (and onwards for mailing lists too), it basically achieves the same result as we're wanting for the most part. I don't think it can be done by IP, but will work for domain. The values also accept wildcard characters to help "whitelist" an entire domain.
From the other post I made (pasting it here for convenience):
I can confirm through testing that if I add a section to the SpamAssassin rules such as the following, this works! 🙂 So this is a great workaround to not having direct whitelisting capabilities, using the whitelist_to rule and score.
# whitelisting addresses
score USER_IN_WHITELIST_TO -100
Using the above (but of course substituting the actual email addresses) worked in my testing.
Similarly, the whitelist_from will work too on the opposite end of the equation... that will apply to who sent the message rather than who the message was directed to.
@robi I don't touch dashboard code. I wouldn't mind doing a PR for the Wordpress (Developer) project to add this but to be applicable to all users dashboard code would be needed since "admin urls" are technically changeable.
I don't think @girish should accept anything less than me doing a PR for making the fields customizable. And...okay, now that I've thought about it, if Girish isn't against the PR for the dashboard change, then I'm down to code it.
@atrilahiji I definitely like this idea! I know I've had to delete an app the odd time that I'm not sure if I will need later or not. My workarounds so far are to change the URL of the app to something like "app-old" or to make sure I download the backup info file first before deleting the app. Your idea is much cleaner and would be an awesome addition! It will allow for extra redundancy if for example we delete an app so it can be replaced by a new app at the same URL and something goes wrong, we can quickly revert back in such a case.