From owner-freebsd-isp Fri Nov 6 22:11:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29828 for freebsd-isp-outgoing; Fri, 6 Nov 1998 22:11:42 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from phoenix (phoenix.aye.net [206.185.8.134]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA29823 for ; Fri, 6 Nov 1998 22:11:40 -0800 (PST) (envelope-from ratbert@phoenix.aye.net) Received: (qmail 16975 invoked by uid 2800); 7 Nov 1998 06:10:03 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Nov 1998 06:10:03 -0000 Date: Sat, 7 Nov 1998 01:10:03 -0500 (EST) From: To: Terry Ewing cc: freebsd-isp@FreeBSD.ORG Subject: Re: Mail In-Reply-To: <4.1.19981106135151.009c12b0@mail1.dcomm.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org If the authentication info for post.office is stored in a text file and if a DES or MD5 password scheme is used you may be able to do some awking and grepping and create a master.passwd formatted type file from the info in it (or an /etc/poppasswd if you use checklocalpwd.c and go the virtual pop route). - Barrett On Fri, 6 Nov 1998, Terry Ewing wrote: > Hi, > > We are currently running post.office as our mail server. We'd like to > migrate to qmail, but we can't find a way to extract the passwords > associated with the pop3 accounts. We've thought of a few ways to do this, > including writing a perl script that actually sits on the pop3 port and > proxies the requests saving the username and password as their mail clients > send them over. > > Somehow I think that something would crash the proxy script and our > production mail server would go down. Can anyone suggest a better way of > moving everyone en masse? > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message