i just think the administrator should have more control over pop usernames.
if your email address was [EMAIL PROTECTED] with the current naming
convention, your pop username would be brad%theinternet.com. but if you had
control over the naming system you could shorten it to something like 'bfp'
or 'bfp1' if 'bfp' is already taken. you tell me which is easier on the
user. not to mention how many email clients would choke on the previous. why
should i have to tell a client, "well, if you're using netscape messenger,
use this delimiter, and if your using hotmail use this delimiter, and if
your using outlook express version facafooey, use this delimiter."
-----Original Message-----
From: Chris Fankhauser [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 25, 2000 9:11 AM
To: Mark Chesney
Cc: vpopmail; qmailadmin
Subject: Re: feature request
I think that is even more obscure than the user%somedomain.com naming
scheme. Imagine how much trouble you'd have telling users "you receive
email at [EMAIL PROTECTED], but when you login, use the pop account name
'bjs4$2.00'.." What kind of problems are you having with the current
naming scheme (besides that hotmail seems to hate it)?
------------------------------
Chris "CryptoMasta" Fankhauser
Bitstream Underground
bomb internet anarchy weaver hacker pentagon china violent
On Fri, 25 Aug 2000, 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
>
>
