From owner-freebsd-chat Sat Apr 3 14:43:15 1999 Delivered-To: freebsd-chat@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id 0C23014E5A for ; Sat, 3 Apr 1999 14:43:13 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id PAA18508; Sat, 3 Apr 1999 15:41:07 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp02.primenet.com, id smtpd018493; Sat Apr 3 15:41:04 1999 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id PAA14402; Sat, 3 Apr 1999 15:41:04 -0700 (MST) From: Terry Lambert Message-Id: <199904032241.PAA14402@usr04.primenet.com> Subject: Re: pop & sendmail and more To: gmarco@giovannelli.it (Gianmarco Giovannelli) Date: Sat, 3 Apr 1999 22:41:03 +0000 (GMT) Cc: chat@FreeBSD.ORG In-Reply-To: <4.1.19990403124424.00a501a0@194.184.65.4> from "Gianmarco Giovannelli" at Apr 3, 99 12:53:29 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The silly question is : Is there a pop3d/imapd that can read the > /etc/mail/virtualusertable to allow user to get their mail with their pop > account and not with their real account ? > > I.e > > Virtual domain : virtual.com > Real box: box.real.com > > real account1 : user1@real.com virtual account : virtualuser@virtual.com > > When user1 send mail can obviusly send it as virtualuser@virtual.com > (sendmail permitting), but when it have to get it he has to used > user1@real.com > Now what I looking for is a patch/hack or an existing pop3d/imapd that can > use the virtualtable to associate the account with the username... The problem here is the authentication database. You probably have the authentication database tied to the real UNIX password file, instead of a seperate authentication database. It's rather trivial to retarget the Cyrus and Qualcomm server code to use a different authentication database. You can also do it with the University of Washington code, but it's a bit harder. The main point is: you *can't* use the UNIX password database if you want to support POP3 APOP, anyway, so if you support this, you are already have a database in which you can create your virtual users. This is because the server has to know the cleartext of the shared secret in order to MD5 it with the generated timestamp to match the client software's hash. So my suggestion is to create the virtual user in your alternate authentication database, instead of relying on the virtuser table contents (where would you store the password? There's no field for a password in the virtusertable!). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message