Re: [Mailzu-users] Overview of MailZu

[Ron G. <rg...@sh...>]

Brian Wong wrote:

>>Question number two:
>>
>>Is mail administrators 'global only' or is it possable to have different
>>administrators for different (sub)domains handling 'ther' mail from a
>>common quarantine?
>>
>>    
>>
>
>Administrators are global only. But I like the sound of this idea.
>Large ISPs would definitely appreciate the distribution of work over
>several domains. This would require more configuration options and
>more fine-grained SQL SELECT queries, but I think this is possible
>without too much effort.
>
>  
>
I'd also like to see this - with 15,000 Spam messages a day, I can't see 
one administrator trying to handle it. <grin>

I was planning on making a local fork to handle virtual domains that 
would work with my existing LDAP based Amavis Policy interface and Mail 
Domain management system (which also runs Postfix, Courier-imap and 
Squirrelmail, as well as handling Virtual Servers, DNS, CRM, Trouble 
Ticketing, Billing, Provisioning and Take-Out Food ordering, so no, I'm 
not going to switch to something else). One of the things I like about 
MailZu is that it seems to follow the major UNIX design principles of 
"do one thing well" and "play well with others" (principles, I'll 
confess, that my own software apparently ignores...)

I think that "permissions" in general should be handled by the same 
authentication method as is used for logins - i.e. if you use LDAP for 
authentication, you should use it for granting "admin" permissions, too. 
Perhaps in the same area as "is the user allowed to logon?", there could 
be a "is the user allowed to release their own content?" and "is the 
user an administrator for their domain?" query. These could just be LDAP 
attributes, or SQL fields, in the Auth database (fields/attributes 
defined by a setting in config.php). This would preclude the other types 
of authentication (i.e. Exchange, IMAP), but perhaps the system could 
fall back to using the built-in arrays from config.php in those cases.

Then, as you say, it would just require a finer-grained SQL SELECT 
statement to find the messages destined for users in a particular 
domain, rather than all users.