Re: [PEPr] Comment on Mail::Mail_Admin
| From: | till | Date: | Tue, 11 Sep 2007 14:41:18 +0000 |
| Subject: | Re: [PEPr] Comment on Mail::Mail_Admin | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-47974@lists.php.net to get a copy of this message | ||
On 11 Sep 2007 08:03:54 -0000, Christian Weiske <cweiske@php.net> wrote:
> (...)
> 4) Do you mean putting Mail/Admin/Driver/Base.php into Mail/Admin/?
Maybe that too - I was more after, if the Postfix "driver" would be a
seperate package later on, but I guess your other replies made that
obvious now. :)
> (...)
> My problems so far:
>
> - Anyone who has ever setup any mail server with user account data stored
> in a RDBMS/LDAP: Is the distinction into Alias, Mailbox and Domain common?
> (Mailboxes and aliases belong to domains, and aliases redirect to either a
> mail box or a different email address not on this server)
I think the distinction is common, but it does not really make any
sense. ;-) At least in my opinion, it makes more sense from a user
perspective to just say "mailboxes" and then your mailbox can be
forwarded (alias, forward) or picked up (-> to mbox/maildir).
But of course you need to implement the magic to do everything in the
background.
CGPro works the same way, atmail as well. Exim, Qmail etc.. too. CGPro
and atmail are the only commercial packages I have experience with.
> - The package uses a driver-based approach. A driver potentially comprises
> multiple classes. Should the class names have the same "base name" like
> Mail_Admin_Driver_Postfix resulting in class names like
> Mail_Admin_Driver_Postfix_Alias - or should I extend the names of classes I
> extend to get names like
>
> Mail_Admin_Alias_Postfix
>
> Mail_Admin_Mailbox_Postfix
I like to have things on Mail_Admin_Driver_Postfix_* - but that's my
personal preference. Is your question regarding "looks" or more in
regard to implementation?
Cheers,
Till