From: Tom C. <to...@to...> - 2005-01-04 02:00:30
|
On Jan 3, 2005, at 4:53 PM, John Peacock wrote: > Yes, but the changes are all in the html files, not in C files, so it > is a little more complicated than that. It's probably just as easy to > provide two copies of mod_user.html and just copy the correct one into > place based on the configure option. Patches welcome... ;) > > In my mind, I cannot see any reason to allow an ordinary user the > ability to disable their own e-mail account (it encourages > carbon-based errors), so I have applied the patch on a site-wide > basis. Being a BOFH in a corporate environment has its benefits! ;) I think that ultimately what we'll want are flags to enable/disable the blackhole and forward features on the modify-user page. Maybe something for the .qmailadmin-limits file? No access, admin-only or user access to each? Include vacation in that? I think we could accomplish it with lots of ##t tags and some more code (e.g., only show this section if the user is allowed to enable forward). My only concern is that we make sure .qmail files aren't hosed up due to the rendered page not matching the actual file (e.g., if the user has forwarding enabled, but can't modify it themselves, what happens if they edit their config? When I get around to releasing the simple change-password interface, it should simplify things a bit. -- Tom Collins - to...@to... QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ Info on the Sniffter hand-held Network Tester: http://sniffter.com/ |