>It takes approximately 6 hours for the script to complete, each
>message invokes a separate qmail-inject process as the mails are
>customised with the persons name / details etc. The concurrency only
>seems to hit about 30- 40 while the script is still pumping messages
>into qmail-inject.
I would definitely call qmail-remote directly, then fall back to
qmail-queue if the qmail-remote fails. Since you know that each
message has a single recipient and you can assume that all the
recipients are remote, you can skip all of the overhead of queueing
and dequeueing all message that get delivered on the first try. (Even
if a few of them are local, they'll still get delivered by looping
back to the local SMTP daemon.)
The interface to qmail-remote is pretty simple; I've driven it from a
68 line perl script, although it'd take a few extra lines to manage a
pool of qmail-remotes to keep up the concurrency you'd want for an
application like this.
I believe that Russ Nelson has done this sort of thing in the past
with great success.
--
John R. Levine, IECC, POB 727, Trumansburg NY 14886 +1 607 387 6869
[EMAIL PROTECTED], Village Trustee and Sewer Commissioner, http://iecc.com/johnl,
Member, Provisional board, Coalition Against Unsolicited Commercial E-mail
