I said: >> We had a similar problem and got around it by making our code smart enough >> to only spool mail if there is less than 200 files in the spool directory. >> Otherwise, it waits a minute and tries again. Sure, you may not be getting >> optimal efficiency out of your mail spool, but you're also not crashing the >> server. :)
Bryant Tyson asked: > Now that sounds like the perfect good fix. How easy was it to code and did > you use any custom tags? I'm wondering if it's something that's within my > coding capabilities. It was actually pretty simple. We have a script that uses CFSCHEDULE to enable/disable a job that runs once a minute. It calls a script that does the following things: 1. Check the mail spool. If the FileCount GT 250 (or some number) just CFABORT and wait for the next call. 2. Process the queue, which is just a db table full of the outgoing mail. If there are any entries, throw about 1000 into the spool. (You can write to the spool with CFFILE, or use CFMAIL. Both work.) Bail Out. 3. If the queue is empty, use CFSCHEDULE to delete the job. You may want to turn off HTTP logging for the directory that script is in. :) -R Rick Osborne Certified Advanced ColdFusion 5 Developer ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
