Hi, In the 3.x qpopper era, I would post a patchfile to the list of all my additions, including additions to the documentation, for the developers at Qpopper Central to pick up and add to the next release. Nothing, not even a "we'll look at it and get back to you". Then 4.x came out and I realized they had made some major changes to the "p" structure and other code rearrangement, so that rolling all of my customizations in would be a major effort. At that point I picked out the one mod I absolutely need (a ten line change to the mailbox directory hashing), tested 4.x otherwise, and decided to live with what was there. Server mode in 4.x (plus moving my mail server from HP to Sun) helped solve most of my performance problems.
Yea verily, local customizations are a pain in the arse. The Qpopper maintainers didn't help matters any. ----------------------------------- Jeff A. Earickson, Ph.D Senior UNIX Sysadmin and Email Guru Information Technology Services Colby College, 4214 Mayflower Hill, Waterville ME, 04901-8842 phone: 207-872-3659 (fax = 3076) ----------------------------------- On Sat, 2 Nov 2002, John Rudd wrote: > Date: Sat, 2 Nov 2002 03:49:12 -0800 > From: John Rudd <[EMAIL PROTECTED]> > To: Jeff A. Earickson <[EMAIL PROTECTED]> > Cc: Simon May <[EMAIL PROTECTED]>, > Subscribers of Qpopper <[EMAIL PROTECTED]> > Subject: Re: Users popping to often > > > It'd be nice if this worked its way into the standard distribution. > I'd love to have something like that. > > Btw: your story is exactly why I avoid local code customizations. > Unless the project developer is willing to take my proposed changes > into the main code base, I don't bother. Local source code changes == > long term software maintenance nightmares. >
