What I have done in the past is to setup a table in my database called Queue that had basically this structure
emailID To From Fail-to Subject textBody HTMLBody threadID dateSent I write to that table, which is dramatically faster then a cfmail, then just have a scheduled task that starts out by creating a theadID UUID pulling from the database a set of emails, say 1000, stamping them with the UUID and then as they get sent just stamp the dateSent. This way if for some reason something dies you can go back and "clean up" anything that uas a UUID but no dateSent. The next processed scheduled task comes along pulls anything that doesn't have a threadID stamped in the field and doesn't step on anyones toes. J.J. On 9/25/07, Andrew Peterson <[EMAIL PROTECTED]> wrote: > Hello, I have a mass email which times out due to our shared server's timeout > of 60,000 ms. (It takes longer than that to process the page.) I could loop > through and send out 2000 emails at a time, but I am still stuck with having > the client wait and click on "Send the next 1000 emails" button until > they're all sent out. Looking for a more elegant solution - something behind > the scenes. Any ideas? TIA. > > Sincerely, > > Andy > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Enterprise web applications, build robust, secure scalable apps today - Try it now ColdFusion Today ColdFusion 8 beta - Build next generation apps Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:289478 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
