> From: "Leonard Burton" <[EMAIL PROTECTED]> > > What about making the log a .txt file and not a database? Wouldnt that be > quicker?
[snip] >> Thanks, Kevin. I've put a counter in place within my mail loop. It seems to >> slow the process, but perhaps not too much. And thanks to Mark McCulligh for >> describing a system for sending about 1500 messages that's called with a >> cron tab and writes to a db after each mail. And thanks to Chris Hayes for >> pointing to relevant list archives. My system seems to be working, but it's >> so slow that I'm going to look at using a cron tab and saving everything to >> a database for easier reference in case of failure mid-list. I'm not sure how the speed of flat file access compares to MySQL access; I assume for simple stuff flat file reading/writing is faster. Currently my system does use .txt files to store/record standard message intro text, standard exit text, reply-to name, reply-to address, list of addresses that failed, the actual contact list (which is pulled from a remote MSSQL server each time email is sent), and a counter of mail attempts generated while looping through the email list (thanks, Kevin). But if I do a version with a cron tab I'll store in MySQL instead, since speed really wouldn't be much of a factor for a process without user involvement, and for me it would be easier to manage. -- Lowell Allen -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
