> > The qmail architecture does not lend itself well to this though does
> > it? qmail-remote is the only code that knows how to remotely deliver a
> > message and qmail-smtpd would have to be (extensively) modified to
> > call that instead of qmail-queue.
>
> You are missing the point. We are just saying that a program invoked
> by qmail-local should have a way to communicate back to qmail 'change
> the address to blah', instead of having to reinject it. This would
> then still happen for every recipient like it does now.
Ug. That's even harder and it saves less than half of your queuing
costs!
That approach means that the message changes from a local to a remote
delivery - the queue structure does not lend itself to making this
change easily without incurring most of the cost of a queue
injection. It also likely that the length of the recipient address
will change - again the queue structure is poorly suited to this for
multiple recipient emails as recipients are stored as a series of \0
terminated strings.
It'll be interesting to see how you propose to atomically make such
queue changes while incurring a worthwhile queueing cost saving.
Regards.
