From owner-freebsd-isp Tue Dec 31 13:06:46 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA21394 for isp-outgoing; Tue, 31 Dec 1996 13:06:46 -0800 (PST) Received: from pinky.junction.net (pinky.junction.net [199.166.227.12]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA21389 for ; Tue, 31 Dec 1996 13:06:45 -0800 (PST) Received: from sidhe.memra.com (sidhe.memra.com [199.166.227.105]) by pinky.junction.net (8.6.12/8.6.12) with ESMTP id NAA24318 for ; Tue, 31 Dec 1996 13:23:51 -0800 Received: from localhost (michael@localhost) by sidhe.memra.com (8.6.12/8.6.12) with SMTP id NAA01242 for ; Tue, 31 Dec 1996 13:02:00 -0800 Date: Tue, 31 Dec 1996 13:01:59 -0800 (PST) From: Michael Dillon To: freebsd-isp@freebsd.org Subject: Re: Usernames (was Sendmail, POP3 & RADIUS, etc.) In-Reply-To: <199612312029.MAA08525@syzygy.zytek.com> Message-ID: Organization: Memra Software Inc. - Internet consulting MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 31 Dec 1996, Samara McCord wrote: > not available because company B has already used it? Only by making > the POP user name (and hence the /etc/password name) so ugly that they > don't confuse it with an email address (and in fact, not useable as an > email address), and then training them to use POP user names as strictly > internal and then we can map whatever domain-specific email name (i.e. > return address) they want into that 8-character ugly name. Rather than calling it an ugly name, call it an Account ID and give customers a configuration form that clearly distinguishes the Account ID from the email address. Michael Dillon - Internet & ISP Consulting Memra Software Inc. - Fax: +1-604-546-3049 http://www.memra.com - E-mail: michael@memra.com