From owner-freebsd-isp Tue May 30 13:27: 0 2000 Delivered-To: freebsd-isp@freebsd.org Received: from troi.csw.net (troi.csw.net [209.136.192.23]) by hub.freebsd.org (Postfix) with ESMTP id 10F7637B91B for ; Tue, 30 May 2000 13:26:54 -0700 (PDT) (envelope-from lambert@cswnet.com) Received: from ssaos2 (ssaos2.csw.net [209.136.201.13]) by troi.csw.net (8.9.3/8.9.3) with SMTP id PAA06858 for ; Tue, 30 May 2000 15:26:51 -0500 (CDT) (envelope-from lambert@cswnet.com) Message-Id: <200005302026.PAA06858@troi.csw.net> From: lambert@cswnet.com Date: Tue, 30 May 2000 15:24:19 -0500 To: freebsd-isp@FreeBSD.ORG In-Reply-To: <20000530161256.A17694@setzer.chocobo.cx> Subject: Re: Cucipop port/source X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v2.10a c10 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In <20000530161256.A17694@setzer.chocobo.cx>, on 05/30/2000 at 04:12 PM, Chip Marshall said: >On May 30, 2000, spork sent me the following: >> With yet another QPopper bug, we're thinking of moving to cucipop. I have >> a few questions for anyone who may be using it: >> >> -how do you like it? >> -any gotchas or incompatibilities in your userbase when you made the move? >> -did you get db support working? >We switched over to it a while back after we had a break in involving one >of the older versions of qpopper, and it seems to be doing quite well. We >had no problem moving over at all, just killed qpopper, started cucipop, >and everything worked fine. We tried Cucipop on our 3.2-STABLE mail server. It worked until we added a second CPU. At that point Cucipop would work fine for a couple of days and then just quit. We didn't have time to debug it so we just went back to QPopper. I would be interested in hearing from people with SMP systems and Cucipop. -- Scott Lambert lambert@cswnet.com Systems and Security Administrator CSW Net, Inc. ================================================================ Written: Tuesday, May 30, 2000 - 03:24 PM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message