Mark Chesney wrote:
>
> currently, in order to avoid the %domain pop user naming scheme, the only
> choice is ip aliasing, which requires an ip for each and every domain.
> sometimes this is unrealistic or unachievable. why not create a system where
> pop usernames can be unique, but not so clunky. there are many ways to do
> this, but it should be left up to the administrator. i can think of several
> examples:
>
> pop name email address
>
> pop0001 [EMAIL PROTECTED]
> pop0002 [EMAIL PROTECTED]
> ...
> pop9999 [EMAIL PROTECTED]
>
> or
>
> bgs [EMAIL PROTECTED] (brad g. smith)
> bgs1 [EMAIL PROTECTED] (bert g. simeone)
> bgs2 ...
> jks [EMAIL PROTECTED] (jud k. smith)
> jks1 ...
> ...
>
> etc...
>
> most of these changes would have to take place in vpopmail but some would be
> required in qmailadmin to remain compatible. here is how i see vpopmail
> changing:
>
> vadduser accepts an extra argument, popname.
> vadduser creates a symbolic link from domains/somedomain.com/realname to
> users/popname or vice versa.
> vadduser updates users/vpasswd and users/vpasswd.cdb.
>
> hopefully this could be intermingled with ip aliasing to allow some domains
> to have realname equal to popname and some domains with unique popnames.
> just a thought. feedback appreciated!
>
> mark
You can already do this:
1) Add domain to store all emails under
vadddomain <domain1.com> <postmaster pasword>
2) Add all other virtual domains
vaddaliasdomain <vdomain1.com> <domain1.com>
vaddaliasdomain <vdomain2.com> <domain1.com>
etc...
3) add users to primary domain
vadduser <user>@domain1.com <user1 password>
NOTE: this assumes you did --enable-default-domain="domain1.com"
when you configured vpopmail
What this does is create a system where users can just use
"username" to log in and not need to use "user@domain".
And all user names must be unique.
Ken Jones
