Forwarded at Mark's request, he meant to send the mail to the list but
sent it to my private mailbox.
I am omitting some headers and the advertisement.
Matthias
----- Forwarded message from "Mark ." <mg12...@hotmail.com> -----
From: "Mark ." <mg12...@hotmail.com>
Subject: Re: [maildropl] Replacing qmail-local
Date: Thu, 22 May 2003 01:11:08 +1200
I'd oppose the inclusion. I wouldn't want maildrop infested with
MTA-specific code.
Hm, I don't believe it would be an overly intrusive patch, it could very
well be implemented like the LDAP, userdb or MySQL lookups which are
optional and need to be turned on at compile time (thereby adding no
overhead for those people not using those interfaces).
These user lookups only take a minor part of the processing, it's _way_
more expensive to actually deliver the mail (if it's not, your
configuration is hosed or you're delivering into RAM disk).
Indeed, the actual delivery is always going to be more expensive, but the
problem I'm trying to solve is integration with qmail and/or potential
other MTAs.
What prevents you from teaching your /var/qmail/rc to use maildrop?
What if I want to remove the need to run qmail-local at all, and use
maildrop exclusively as my LDA? From what I understand all current
interfaces rely on qmail-local handing off the content to maildrop either
using .qmail or defining a default delivery mechanism. Call me crazy, but
I don't see what the extra exec or fork&exec gives me (other than perhaps
robustness if maildrop doesn't return qmail/MTA understandable exit codes
in the face of errors). Feel free to point out anything if I've
misunderstood.
If my MTA already does my lookup and fetches all the information required
what benefit is there having to reimplement this logic within maildrop?
I would be looking to implement this as a "drop-in" replacement for
qmail-local and also a generic mode for more configurable MTAs.
I really want to use maildrop, it looks like excellent software, and it
looks very much as though it will solve many problems I currently have, but
in order to use maildrop I must do so in an efficient manner.
Perhaps it would be more constructive if I go away and come back with a
patch, and have people comment on the patch itself?
----- End forwarded message -----
3 messages in net.sourceforge.lists.courier-maildrop(fwd) Re: [maildropl] Replacing qmail...
