On Tue, May 2, 2006 3:45 pm, John Nichel wrote: > Richard Lynch wrote: >> On Tue, May 2, 2006 6:16 am, Ryan A wrote: >>> The problem is the host is limiting the amount of >>> emails that can go from the site per minute, and we >>> need to email all the members (a modest 700 or so) a >>> newsletter/update...any suggestions on how to do that? >> >> The main problem with using mail() for mass emails is that every >> call >> to mail() fires up sendmail, and you can easily swamp your machine. > <snip> > > Okay, this is not what I understand of mail() if the path to sendmail > (or sendmail wrapper) is given (vs a smtp server). I might be wrong, > and I hope I'm not, but if the path is set, doesn't it just inject the > message into the queue? As I understand it: It fires up 'sendmail' process (your sendmail_path) with correct flags to inject the mail into the queue. 'sendmail' is big. very big. Shoving the message into the queue is "fast" once sendmail is up-and-running... But firing up the process 'sendmail' is relatively expensive in the first place. Later, 'sendmail' runs to process the queue, or some portion of the queue, dependong on how you have configured sendmail, assuming you have it running to send outgoing email in the first place... Now that, obviously, involves serious internet lag time and whatnot, and is really really slow. So, in comparison, firing up sendmail to queue the email is "fast" But that doesn't make it "fast", if you know what I mean. Also, I THINK it actually forks off a sendmail process and returns -- which means that you can get a hell of a lot of "little" sendmail processes running, all trying to queue up one email each... This is probably dependent on the flags you have in your sendmail path, as I recall, and if I understand things correctly. -- Like Music? http://l-i-e.com/artists.htm -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
