Virtual domains is a tricky service.
you may want to go the way of virtfs (url in freshmeat), which has a
chrooted subdir for all the services (smtp, pop, imap, mailstore), and
runs sendmail, uw-imap and uw-pop. This is a good setup for a one box
solution for as many virtual domains (and IPs) your disk can afford.
Usually setups like these are secondary or primary corporate MXs, with
several users to a virtual domain, and this is free of the name-clash
problem of the second solution below.
if you go the postfix virtual users in one physical mailstore, you either
have to:
- map each virtual user address to a "local" username which he uses when
he logs on; aside from this being a helpdesk problem, teaching the user
that when he logs on the pop server, it's not his username he types in but
actually the 'aliased user', this is a maintenance nightmare, unless you
are ready to make a system that takes care of keeping track of
names/aliases to actual customers, and re-generates the postfix alias
file/or ldap directory/or sql table based on it...
- deal with the name clash issue by accepting it as a limitation. Problem
with this is that [EMAIL PROTECTED] can also receive email at the
address [EMAIL PROTECTED]
On Wed, 21 Feb 2001, Reynald I. Ngo wrote:
> At 12:18 PM 2/21/01 +0800, you wrote:
>
> Ian,
>
> I was choosing between ldap and sql based db for this purpose. How is it
> with handling virtual domains on your setup?
>
> ---
> Reynald I. Ngo
> Express Internet, Inc.
> Express Telecoms Co., Inc.
>
> _
> Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
> To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
>
_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
