Question about Domain Settings
I got a new working Mailpiler Setup on Centos7 and I am trying to figure out the best way to use it. According to the documentation you are supposed to create a user with a certain e-mail address and when you log into piler this user can view his own mails. With the group settings it is possible to give the user shared access to more e-mail address.
Is there a way to create sort of an auditor or regular user account that simply has access to any generic e-mail address of only a certain domain without actually listing those in a group?
At first I thought the domain field in the user settings fulfills that purpose, but I actually couldn't see any effect at all when adding or removing domains to that list. This was tested with a regular user account. From my understanding auditor accounts always have access to all domains and e-mail addresses by definition?
This ticket is not supposed to be a compaint or anything like that. I am just trying to figure out how the domain field works and if I actually have to list all addresses in a group I am also fine with that. Could not find any hints in the documentation, but maybe I am just not good enough at searching. :)
Thanks for creating this awesome open source product!
There aren't many options left in that area.
Comments (5)
-
repo owner -
repo owner -
assigned issue to
-
assigned issue to
-
reporter So the domain list in the user settings is just a relict from the discontinued SAAS feature and essentially can be ignored?
-
repo owner Well, not quite, but regarding your use case you might say that.
-
repo owner - changed status to wontfix
- Log in to comment
Well, what you ask for is some sort of multitenant feature. I started to add some to piler, but at a point I've decided to discontinue it. However, I didn't remove what already is in the product, so try setting $config['ENABLE_SAAS'] =1; in config-site.php. It should allow you to create per domain auditors.
Perhaps one day I come up with a complete multitenant version of piler, though in that case it wouldn't be open source, rather similar to nginx vs. nginx plus.