Matthias Andree wrote:
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 must say the logic is quite sound; from the perspective of maintaining
maildrop itself I can see where you might not want this to happen. From
the perspective of a generic mail admin however, this seems like a good
idea.
May I perhaps suggest a hand-off program that acts as qmail-local would
but without the .qmail-... lookups? If it handled the setting of the
correct environment variables and then exec'd a minimally patched
maildrop executable, it should work correctly.
3 messages in net.sourceforge.lists.courier-maildropRe: (fwd) Re: [maildropl] Replacing q...
