----- Original Message -----
From: "Michel Verbist" <[EMAIL PROTECTED]>
> >From a database point of view (I'm more a database guy than a mail guy),
> typically, if you are working with a DB user repository, you
> would have two tables for the user repository.
> One for the domains and one for the users, with a one-to-many relationship
> between them.
> Incoming mail would be checked for domain name and username (belonging to
> that domain!!)
How do you intend to determine "belonging to that domain!!" ?
> Or for file-based repositories, like you suggest, something like
> "user1.domain1" would work, I think.
The storage method is irrelevant.
Say you tell Sandy to retrieve her mail from mail.domain1.com with the
username "user1" and you tell someone else to Joe to retrieve his mail from
mail.domain2.com with the username "user1". Well, if mail.domain1.com and
mail.domain2.com point to the same IP address, they're going to be accessing
the same account. You can't figure out what domain name the user thinks he
or she is accessing with POP3 or IMAP4.
So do you tell Sandy that her username is "user1.domain1" and Joe that his
is "user1.domain2"? Or do we just alias all the accounts from different
domains into a single list of accounts, or what?
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
