On Sun, Jul 01, 2001 at 03:15:43PM -0400, Dan Melomedman wrote:
> I've been thinking about the uid attribute a little bit, and it seems
> completely redundant. If pop3d was modified to lookup mail=uid@domain,
> we wouldn't have the uniqueness problem, and wouldn't have to invent
> stupid uid value schemes like user-domain for the uid attribute value.
> The @domain part could be determined by the IP range that the client
> is in, or by simply running a different pop3d server per every virtual
> domain. Just like Apache does it for virtual domains.
> So the pop3 client submits uid to the pop3 server, pop3 server looks at
> the ip address of the client. If an address matches a range of particular
> virtual server in pop3d's configuration file (this could be a cdb database),
> then an ldap search is done with uid@domain that's read from the config
> file. The configuration file is simply bunch of range=domain keys and
> values.
Well, this is much to complicated and error-prone IMHO. I don't like the
idea of "virtual pop3 servers". Our mail machines have 2 to 5 IPs each while
the webhosting ones have a few hundred.
I thought about adding "(|(mail=[supplied
uid])(mailalternateaddress=[supplied uid]))" to the search string. This way
users could just login using their email address. We all know that there are
lients out not allowing @ in the username - they are stupid, ignore them,
kick them, burn them, whatever ;-)) they can still log in using their "real"
uid. the modification should be fairly easy.
--
* Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de *
* Roedingsmarkt 14, 20459 Hamburg, Germany *
Unix is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)
