On Mon, Jan 08, 2001 at 10:48:26AM -0500, Alex Pennace wrote:
>
> Or imagine:
>
> - I have a stock qmail server with smtproutes,
> - I decide that I want to use QMTP,
> - I setup an appropriate mailroutes file,
> - It doesn't work, because I forgot to patch qmail.
That's not a problem with the patch :) That's a problem with qmail,
not having support for qmtp builtin :)
> > Why? Is is that much trouble to have Johan patch read smtproutes first
> > and then mailroutes (or qmtproutes), and giving precedence to the
> > first?
>
> Why give smtproutes priority? If mailroutes doesn't exist than
> smtproutes will be used anyway, if smtproutes support is kept.
Johan patch, as far as I've read, does not read smtproutes anymore.
> Why must every outdated configuration be supported because some people
> can reconcile using patch -p1 < johans-patch but can't reconcile mv
> onecontrolfile anothercontrolfile? People should be following
> directions in README, INSTALL, and UPGRADE.
Because the patch is not official qmail. A patch that is not official
qmail, should not be incompatible with previous working configuration of
qmail. Even a big patch like qmail-ldap did that. It added several
features (the patch is 1/3 of qmail in size....) and a normal
configuration of qmail still works.
> > My view: patches should add funcionality. They should make their best
> > not to force changes on a working situation.
>
> Patches always change a working situation, by definition.
"working situation" no. they change features available.
Best regards,
--
Pedro Melo Cunha - <[EMAIL PROTECTED]>
Novis - Dir. Rede - ISP - Infraes. Portal <http://www.novis.pt/>
Ed. Atrium Saldanha - Pça. Dq. Saldanha, 1 - 7º / 1050-094 Lisboa
tel: +351 21 0104340 - Fax: +351 21 0104301
