From owner-freebsd-isp Tue May 30 14: 5:44 2000 Delivered-To: freebsd-isp@freebsd.org Received: from aspenworks.com (netdev.aspenworks.com [192.94.236.1]) by hub.freebsd.org (Postfix) with ESMTP id 5B57737B766 for ; Tue, 30 May 2000 14:05:39 -0700 (PDT) (envelope-from alex@aspenworks.com) Received: from aspenworks.com (s29-g-lv4.sopris.net [208.47.129.189]) by aspenworks.com (8.9.3/8.9.3) with ESMTP id PAA38222; Tue, 30 May 2000 15:05:25 -0600 (MDT) (envelope-from alex@aspenworks.com) Message-ID: <39342CFC.7065E720@aspenworks.com> Date: Tue, 30 May 2000 15:05:00 -0600 From: Alex Reply-To: alex@aspenworks.com X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Robert Hough Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Cucipop port/source References: <4.3.1.2.20000530152814.01faa3f0@qserve.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Robert, It is faster. cucipop does not copy the mail file to a tmp file like qpopper does. The trade off to consider is that cucipop will not re-synch after abnormal disconnects as well qpopper does. It appears that the temp file qpopper uses keeps better track of the individual mail messages downloaded. I settled on cucipop for speed once our system needed to support more than 2,000 mailboxes. We never did much with DB files, but the control aspects of cucipop turned out easier to manage. -Alex Robert Hough wrote: > > At 04:06 PM 5/30/00 -0400, you wrote: > >With yet another QPopper bug, we're thinking of moving to cucipop. > > I did the same thing yesterday... > > >-how do you like it? > > So far, it's been great (The whole 24 hours we've had it running). In fact, > it's already proven to me that it's faster under heavier loads. It also > seems to be faster if the mail has large file attachments as well. Though, > it could just be that "new toy syndrome" I tend to get when I install > something with little to no problems in the process. :) > > >-any gotchas or incompatibilities in your userbase when you made the move? > > I just replaced the proper lines in my inetd.conf, restarted inetd, and > away it went. Haven't had any problems as of yet. > > >-did you get db support working? > > No. I got the same error you got. I didn't play with this too much though, > as this really didn't seem to add any serious benefits that I needed. > > All said and done, I think this was a pretty good move on my part, and I'm > still wondering why I've allowed qpopper to infest my system for so long. > > -- > Robert Hough (rch@qserve.net) Qserve Internet, Inc. > http://www.qserve.net/ Ph: (317)802-3036 > > 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