Qmail
[Top] [All Lists]

Re: [djb@koobera.math.uic.edu: qmail 1.00 available]

To: qmail@list.cr.yp.to
Subject: Re: [djb@koobera.math.uic.edu: qmail 1.00 available]
From: Kyle Wheeler <kyle-qmail@memoryhole.net>
Date: Fri, 23 Feb 2007 12:43:25 -0700
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
Delivered-to: sp-com-lists@consult.net
Delivered-to: gmail-qmail@securepoint.com
Delivered-to: sp.com.list@gmail.com
Delivered-to: mailing list qmail@list.cr.yp.to
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=cEBBr2blZn/RgJ0QFB4mp6W5br6ESYSxEdwp/P1Pj3gVTZ9wf3OQh8IhSQITI+igGNKrna71qR+uJBmv0UWdB3Qax2/czwd+UAiWiTucSWI3MOZmIKEiaaoDse9Dmds7aPzYnbIWm75P9KGEHzcWxhpGxTait3n3GJS2HICDfMw= ;
Domainkey-status: good
In-reply-to: <20070223125441.1eb6d4bb.seth@cql.com>
Mail-followup-to: qmail@list.cr.yp.to
Mailing-list: contact qmail-help@list.cr.yp.to; run by ezmlm
References: <5.1.0.14.2.20070222151110.03804210@mail.30below.com> <20070222140051.76cdabb9.sasa@admin-networks.org> <20070222042303.GA74985@lizzy.catnook.local> <20070222140051.76cdabb9.sasa@admin-networks.org> <5.1.0.14.2.20070222151110.03804210@mail.30below.com> <3.0.6.32.20070222231359.01865900@192.168.192.1> <5.1.0.14.2.20070223103051.012bb010@mail.30below.com> <20070223181756.18807bd4.sasa@admin-networks.org> <20070223172643.GB16039@discworld.dyndns.org> <20070223125441.1eb6d4bb.seth@cql.com>
User-agent: Mutt/1.5.13 (2007-02-12)
On Friday, February 23 at 12:54 PM, quoth Seth Kurtzberg:
On Fri, 23 Feb 2007 11:26:43 -0600 Charles Cazabon <qmail@discworld.dyndns.org> wrote: To me, it's preferable to have a small set of core functionality to add additional features I need using patches, for a number of reasons. I like to know what optional features are in use. I can apply a patch to test a feature, and if I find that I don't like the results, I can easily remove it. If a better way of handling a feature becomes available, I know what needs to be changed to use it.

I completely agree. If I don't want a regex engine in my mail server, by gum I shouldn't have to waste memory footprint putting one in there.

If anything, what is lacking in the qmail world is a centralized collection of supported, maintained, tested patches, that can be treated similarly to the LWQ (i.e. "if you need feature X and don't use the patch and/or method from the Qmail Patch Repository, then good luck, but it's probably smarter to use the QPR patch."). The qmail.org website serves that function to some extent, but it could be done (organization, presentation, etc.) better. At the moment it's more of a "well, if you wanted extra features, you should have searched qmail.org" rather than "the patches on qmail.org are known to work, and are known to work well together, and are the most recent, bug-fixed versions of said patches." Instead, for the most part, we have an occasionally updated list of patches that strike Russ's fancy (meaning no disrespect), in no particular order, with some duplication (do we really need links to three different ways of making qmailanalog work with the default multilog timestamps? or three different, incompatible SMTP-AUTH patches?) and even outdated (the TLS patch, marked "updated" was last updated in January of 2006), unreachable links (to Matt Ranney's delayed mail notifier, for example) as well. Anyone seeking to maintain a given patch generally makes their own website that you have to go find on google (and know just the right keywords to search for).

This vision of a Qmail Patch Repository is probably, of course, an unattainable pipe-dream. But it would still be awfully nice.

~Kyle
--
Nonsense. Space is blue and birds fly through it.
                                                        -- Heisenberg

Attachment: pgpknbj7S8giE.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>