How to approach this depends on if you willing to force your users to
fudge their POP/IMAP login names or not.
By forcing them to modify their login name to not be identical to their
email username then you can do purely "soft" virtual POP/IMAP accounts
where you only need to make a trival modification on the MTA side. So,
you would have Postfix, Sendmail or etc use a virtual alias table which
would do something along the lines of user@one gets delivered to the
"userone" account and user@other gets delivered to the "userother"
account. The advantages of this is you only need to configure on instance
of the POP/IMAP servers and only one IP address for the machine. The
disadvantage is that the users need to understand that the login name is
not just "user"
You can allow for both login of "user" with a POP/IMAP server address
set to one_domain and allow a different login of "user" with a POP/IMAP
server address set to other_domain if you do "hard" virtual hosting. In
that configuration you need to assign multiple IP addresses to the
machine. You then set up different configuration files that are bound to
the different IP addresses. With the U of W POP/IMAP daemons that RH
continues to distribute, this would be done by using the "interface"
option in xinetd and then have it call differently configured POP/IMAP
daemons accordingly. But configuring hard virtual hosting becomes very
messy and tends not to scale as well.
It would be easier to go into more specifics if we knew if you are
looking to do soft or hard virtual hosting for the POP/IMAP accounts.
Personally, I would do soft virtual hosting using postfix and cyrus or
using courier. BSD Sendmail is an alright MTA but I have run into
problems when the machine is administrated by multiple people and there
are misconceptions as to how the Sendmail configuration files work. Those
misconceptions seem to be much less when using Postfix. Also, I have run
into scalablity problems with the UofW IMAP daemon and the licensing terms
for the UofW IMAP daemon flat out suck. Both cyrus and courier are
clearly better done packages for non-shell account email systems. It is
too bad that RH choose to kill the Powertools distribution that provided
them. I have been maintaining my own spec file for building latest cyrus
imapd packages as RPM and courier provides instuctions on building their
package as RPM but there is no longer any updates as to known issues in
the RH bugzilla database. If you need a cyrus or courier system
that is supported by the GNU/Linux distributor then you will need to
presently go with something other than RH.
On Sat, 28 Dec 2002, Ashley M. Kirchner wrote:
>
> What are people using for virtual pop/imap accounts? In other
> words, accounts that can receive mail, but that don't have a physical
> log in to the server. I need something I can roll out that can work
> across multiple domains (hosted on the same server), and that will
> (hopefully) allow me to create user@one_domain and user@other_domain
> without 'user' conflicting. ('user' in this case is the same)
>
> Running RH7.3 w/ Sendmail.
>
>
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
