[Mailman3-dev] Problem with the schema
jpr at uab.edu
Fri Apr 1 19:28:09 CEST 2005
If the account is the object that is subscribed to a list, then it seems
one could view an account as a form of a roster. That is, an account is a
named collection of email addresses where each address could have specific
delivery settings (ordinarily it would be just one address that gets the
message for a specific list). The account roster would also ordinarily
just be a roster with a single administrator, the user/owner.
I'm not sure if this improves anything or is reasonable in the
implementation, but the relationship comes to mind.
On Thu, 31 Mar 2005, J C Lawrence wrote:
> On Thu, 31 Mar 2005 11:20:35 -0600 (CST)
> John-Paul Robinson <jpr at uab.edu> wrote:
> > The options you mention seem to be attributes of accounts, addresses,
> > rosters, and lists. Owners, admins, users can set the attributes and
> > then as the message "moves" through the delivery net
> > (list->roster->address->account)...
> Why is an address subscribed to a list? Why isn't it the account which
> then specialised delivery to one of its addresses?
More information about the Mailman3-Dev