From owner-freebsd-isp Thu Jun 1 11:41:50 2000 Delivered-To: freebsd-isp@freebsd.org Received: from durango.picus.com (durango.picus.com [209.100.20.19]) by hub.freebsd.org (Postfix) with ESMTP id CF1FF37B97A for ; Thu, 1 Jun 2000 11:41:42 -0700 (PDT) (envelope-from troy@picus.com) Received: from arcadia [209.100.20.198] by durango.picus.com (SMTPD32-5.05) id AE0011B0170; Thu, 01 Jun 2000 14:40:00 -0400 From: "Troy Settle" To: "spork" , "Sumbry][" Cc: , Subject: RE: Cucipop port/source Date: Thu, 1 Jun 2000 14:44:12 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 In-Reply-To: Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Charles, Not to throw a wrench in your wheels, but have you considered changing around your whole back-end system? It's too late for me (we just switched to Imail *YUCK*), but if I had everything to do over again, I think that Cyrus would be the obvious choice. It's got support for both POP3, IMAP, and quotas. It's got all the popper features that you're used to (maybe not bulletins, I've never used those), and with the IMAP support, webmail would be a breeze (much better than doing it through POP3). About the only disadvantage I've seen with Cyrus, is that it's designed to work on a closed system. You would need to treat your mail server as a remote server, even if you're running a client on the local machine. Anyways, I thought I'd comment, -Troy PS: When I did switch from Qpopper to Cucipop some years ago, there were a few problems initially, but they went away quickly. When implementing webmail, I switched (rather stupidly) to the UW Imapd and popper. ** -----Original Message----- ** From: owner-freebsd-isp@FreeBSD.ORG ** [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of spork ** Sent: Thursday, June 01, 2000 1:46 PM ** To: Sumbry][ ** Cc: lambert@cswnet.com; freebsd-isp@FreeBSD.ORG ** Subject: Re: Cucipop port/source ** ** ** I just gave cucipop a quick trial and it just about cut the load on the ** machine in half. Response in my pop client was quite zippy. ** ** I did run into a few problems, the most annoying being the difference in ** UIDLs returned between Qpopper and cucipop: ** ** cucipop - UIDL 1 ** +OK 1 982b3d94590d0000 ** ** Qpopper - uidl 1 ** +OK 1 7717bd7ef97667003d730748e3987af1 ** ** This basically made everyone download all mail again as if it were new. ** It also doesn't seem to play well with our webmail interface... ** ** Anyone have any tips on this or understand a bit more how the ** UIDL feature ** is implemented? Has anyone ever found a cucipop mailing list? ** ** Thanks, ** ** Charles ** ** On Tue, 30 May 2000, Sumbry][ wrote: ** ** > > 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. ** > ** > Re my previous message, we also are running cucipop on a Dual ** P3 processor ** > box, running 3.3. No problems at all. ** > ** > ----- ** > Sumbry][ | Affinity Internet Inc | http://affinity.net | ** sumbry@affinity.net ** > I'll believe psychics when one phones me, just in the nick of time, ** > yelling, "Duck!" ** > ** > ** > ** > 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