I have a K6/2 400 running RedHat 6.1 with Qmail. The box has 160mb RAM and a
cheapo IDE 4gb disk (was once a workstation). We have a 2Mb/s ADSL
connection. It's running as a POP3/SMTP server for a small internal network
for 15 users.
All works great, however every so often (bi-weekly) I need to
John P wrote:
I have a K6/2 400 running RedHat 6.1 with Qmail. The box has 160mb RAM and a
cheapo IDE 4gb disk (was once a workstation). We have a 2Mb/s ADSL
connection. It's running as a POP3/SMTP server for a small internal network
for 15 users.
All works great, however every so often
John P wrote:
All works great, however every so often (bi-weekly) I need to send an
e-mail to 40,000 customers (different e-mail for each one), generated
using MySQL and PHP's mail() command.
On Sun, 18 Feb 2001, Lukasz Felsztukier wrote:
I am here facing the same problem myself. We have
[EMAIL PROTECTED] wrote:
John P wrote:
All works great, however every so often (bi-weekly) I need to send an
e-mail to 40,000 customers (different e-mail for each one), generated
using MySQL and PHP's mail() command.
On Sun, 18 Feb 2001, Lukasz Felsztukier wrote:
I am here facing
In this way you'll make the first delivery attempt yourself for each
recipient; avoiding any overhead in the qmail-send process or the queue
management. if the first attempt fails then the message is passed off to
qmail-send to handle, which should be a much lower volume of mail.
I
On Mon, 19 Feb 2001, Lukasz Felsztukier wrote:
I understand this code has to be executed in a loop for each
recipient...Can you explain what advantages I get doing it this way ?
the code will spawn upto maxchildren processes all trying to deliver mail
in parallel; it will try and keep that
pass the message off to qmail to deliver. As most message get delivered on
the first attempt you'll save the overhead of writing the message to disk,
And this is a large caveat. If, eg, your network happens to be down at
the time you attempt delivery, you'll inject a huge number of emails
into
