[EMAIL PROTECTED] wrote:
>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.
You could get a large performance boost by attempting to deliver the
messages yourself via qmail-remote and passing them to qmail-inject
only if the qmail-remote attempt fails. There's a lot of overhead
involved in queueing that's unnecessary if the message is immediately
deliverable. However, since sending a message via SMTP is so slow,
you'll need to massively parallelize this process--e.g., split the
list into 300-500 pieces and spawn as many jobs to send the messages.
Alternatively, you could install the bigconcurrency patch and up your
concurrencyremote to 500 or so, but the gains will be much more
modest.
>> Are you running a local caching DNS server? Can I recommend djdns :>
>
>No Im using our colo's nameserver which is only a hop away , but that
>is a good point I hadnt thought of.
Yes, dnscache from djbdns is what you need.
-Dave
