Dave Sill <[EMAIL PROTECTED]> wrote:
> >
> >I don't think it was quite this bad.  He described his problem, and it
> >was agreed that qmail would require a patch to give him the cleanest
> >possible solution.  He then said that patching qmail was not an option
> >to solve his problem.
> 
> Patching qmail is not just "not clean", it's a nightmare. If you were
> managing a system and a user requested that you apply a patch to a
> major subsystem so they could use some particular utility, how would
> you take that?

If it was something that I didn't think would be useful for at least a
significant subset of my users, or I wasn't happy with some aspect of
the patch, then I would refuse, of course.
 
> Another suggested fix is parsing virtualdomains. How would you feel if
> a user wanted you to change the mode on virtualdomains? What if you
> don't want all users on the system to know everything about your
> virtual domain setup?

Personally, I do keep virtualdomains world readable -- there's nothing
in there on my machines that I need to keep secret.

However, this all boils down to one nagging tidbit:  various addons for
qmail (such as TMDA) are only truly usable by people who administer
their own mailservers, or who can direct the administrators of their
mail service (i.e. paid-for hosting).  Random users will have very
little luck getting any sort of addon added just for their use with an
ISP or other mailhost who doesn't have a vested interest in satisfying
their customers.  Note that this includes vmailmgr, vpopmail, etc. as
well.
 
> In short, we should have handled this as if we had respect for the
> person to whom we were replying, not like we're gods tossing the
> mortals occasional gems of wisdom.

I, personally, did not intend to come across in this manner.  Jason, if
I did, I apologize.

Charles
-- 
-----------------------------------------------------------------------
Charles Cazabon                            <[EMAIL PROTECTED]>
GPL'ed software available at:  http://www.qcc.sk.ca/~charlesc/software/
-----------------------------------------------------------------------

Reply via email to