|
From: SourceForge.net <no...@so...> - 2011-04-28 09:16:55
|
Feature Requests item #2882264, was opened at 2009-10-20 12:24 Message generated for change (Comment added) made by nidla You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2882264&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface Improvements (example) Group: None Status: Closed Resolution: Out of Date Priority: 5 Private: No Submitted By: Aldin Kapetanovic (nidla) Assigned to: Nobody/Anonymous (nobody) Summary: Lock editing for default mail aliases Initial Comment: When "super admin" is adding new domain, there is option "Add default mail aliases:", ok i do that always for RFC reasons :), but problem is when i give some user admin account for that newly created domain, and he deletes default aliases, the point is that i want to restrict him to do that. For example, when creating new domain it would be useful to have these steps: "1. Add default mail aliases" "2. Forbid editing default aliases". 'alias' table structure |address|goto|domain|created|modified|active| alter add column 'edit' default 't' |address|goto|domain|created|modified|active||edit| *forbid editing might be colored different in web interface or being non clickable ---------------------------------------------------------------------- Comment By: Aldin Kapetanovic (nidla) Date: 2011-04-28 11:16 Message: Thats fine, does what i need, thanks. ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2011-03-09 22:42 Message: That was before I started working on PostfixAdmin ;-) ---------------------------------------------------------------------- Comment By: Aldin Kapetanovic (nidla) Date: 2011-01-18 09:02 Message: I found it ;) since 2.1.0 CHANGELOG.TXT Version 2.1.0 -- 2005/01/07 - Added: $CONF['special_alias_control'] variable. (Thanx Mihau) ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2011-01-17 13:05 Message: Maybe, however I don't remember a change in this area (except a fix I did in SVN trunk for what will be the 2.4 release). Nevertheless: thanks for confirming that it does what you need ;-) ---------------------------------------------------------------------- Comment By: Aldin Kapetanovic (nidla) Date: 2011-01-17 09:27 Message: Just tested, now it works, and it is by default set to "NO". Perhaps because it is newer version since report? >>Submitted: >>Aldin Kapetanovic ( nidla ) - 2009-10-20 12:24:06 CEST however, since it works, you can "close" this feature request ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2011-01-05 19:45 Message: I assume you talk about aliases you defined in $CONF['default_aliases']. You can protect them by setting $CONF['special_alias_control'] = 'NO'. With this setting, domain admins will no longer be able to edit or delete those aliases. (Superadmin still can.) Does that do what you need or do you have a usecase where per-alias locking would be needed? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2882264&group_id=191583 |
