From owner-freebsd-isp Fri Jul 28 12:41:45 2000 Delivered-To: freebsd-isp@freebsd.org Received: from qmail.corpex.net (qmail.corpex.net [195.153.247.40]) by hub.freebsd.org (Postfix) with SMTP id 663E237BC18 for ; Fri, 28 Jul 2000 12:41:41 -0700 (PDT) (envelope-from jonathan@corpex.com) Received: (qmail 33493 invoked from network); 28 Jul 2000 19:40:13 -0000 Received: from perseus.corpex.net (HELO perseus) (195.153.247.226) by qmail.corpex.net with SMTP; 28 Jul 2000 19:40:13 -0000 From: "Jonathan Defries" To: "Freebsd-Isp@Freebsd. Org" Subject: RE: Password Distribution / Email Date: Fri, 28 Jul 2000 20:41:36 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20000728165343.53332.qmail@staff.nyi.net> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Agreed, I'm running with over 3k virtual domains and a some /etc/passwd ones as well and it works brilliantly. No more R?$$$ stuff either :) (I know you don't have to get your hands dirty in sendmail.cf anymore, but that was a scary experience a few years back! The only thing I am lacking, if anyone can help, is a simple way of parsing the message ID from a message for the qmail-command options. I really don't want to have to spool standard input to a file or memory to do this and there is no variable in the environment to log the message ID. TIA Jonathan > -----Original Message----- > From: owner-freebsd-isp@FreeBSD.ORG > [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of javier > Sent: 28 July 2000 17:54 > To: Michael Barnett > Cc: freebsd-isp@FreeBSD.org > Subject: Re: Password Distribution / Email > > > > Have you thought of migrating off of sendmail? > > Qmail + VPopmail would be a greta solution. > > Not only do you get rid of the hasle, and security risks of having > so many system accounts, but you get speed an reliability thrown in. > > www.inter7.com/vpopmail/ > > As far as scalability... the main maintainer has developed systems > with over 50K users per domain, and i have setup the system on isp's > with over 2K virtual domains at about 50 accounts per domain. > > Take a look at it. > > > > Michael Barnett writes: > > > > > Everyone, > > > > We are redesigning our email scheme, and I am looking for an > alternative > > to pushing passwords around on dozens of machines. Right now, > we have 10 > > mail machines for mail exchanging/pop access for our domain. > (5 for mx .. > > 5 for pop .. both setup on a VIP behind a Foundry load > balancing switch). > > > > The 11th machine exports an nfs file system that all 10 machines mount > > (deliver and cucipop have been hacked to look in the nfs mounted file > > system as opposed to /var/mail) > > > > It also generates and pushes across the aliases, and creates the > > master.passwd file and has each of the 10 individual machines rebuild > > their local password file using the command > > > > /usr/sbin/pwd_mkdb -p -s 15 /etc/master.passwd > > > > There are currently 24054 entries in the master.passwd file, so this > > process is going to be unmanageable very soon. > > > > We have a few ideas for getting pop to authenticate off of the > database, > > but even if we do this, we will still have to maintain the > password files > > for local delivery. Has anyone been successful in running a > mail server > > that does not contain the authoritative list of users, but gets this > > information from some central location? (preferably from an sql > > database). > > > > > > Thanks for any insights. > > > > -Michael Barnett > > CAIS Internet > > > > > > > > > > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message