Hello Gerry, Gerry Demaret wrote:
Well for example there is the spamSubjectPrefix setting, which I would like to let the user decide. We do virtual hosting, and our customers like to have as much control as possible, so being able to set that would be nice. Another option they might want to change is the kill level which seems to be represented by spamOverallLimit and spaminessOblivionLimit. Also whether or not to use anti-spam and anti-virus should be a user-definable option in our setup. On the other hand, I don't want them to enable training mode etc, but we'll make sure out user interface doesn't allow for this at all.
Ok, I see. You need some options being available to your users.
I see, but like for us, all management of user profiles is done through a custom developed front-end, which can pretty much shield off anything we don't want to expose. So if we know what options are "dangerous", we can simply not bring them to the user. :)
Then I recommend you to create a form with a limited set of features of your choice, and let your users define their settings.
No I probably won't need 2K policies. If it isn't possible to fix it within clapf, we'll code it so that if a user chooses a combination of
The current webui does not allow regular users to change the policy settings, and I'm not sure at the moment how easily a complex permission scheme could be implemented. You mentioned that you are working on extending roundcube to access the quarantine, so I recommend you to add another page dedicated to these settings.
options that isn't in a profile yet, a profile will be automatically created. That way we limit the number of options, as well as allowing the customer to change whatever he wants. Of course, to make this work nicely, we would need to know what the performance killers are.
This sounds good: create a reasonable default policy suitable for the majority of users, then present these settings to them. And if someone modifies it, create a new policy group for him, and change his policy group in the background. The attributes you mentioned don't affect the performance, just make sure they remain within some reasonable boundaries, eg. spaminessOblivionLimit >= spamOverallLimit.
Also, in the LDAP properties list, I don't see an option to enable or disable virus filtering in a policy. Say that a user just wants to keep spam out of his mailbox but doesn't care about getting viruses, how would I do that?
deliverInfectedEmail is the attribute you need. Best regards, Janos
