> > 1) Getting a separate server dedicated to handling SMTP spooling, then use > > CFFILE to write the messages directly to the spooler pickup directory > > instead of using CFMAIL. > > Hmm i'm wondering why you think CFFILE would be any better. If the > corruption comes from writing the email message to the drive over and over > again, I don't see how the situation would change. Hmmmm. A different > drive would get corrupted that way? :)
Using CFFILE to write the message directly to the SMTP spool for direct pickup saves CF from having to pass the message from its own spool directory over to the mail server (which would likely re-write the file into its own spool). It saves on processing time, speeds up delivery, and if your SMTP server is on the same physical server, it saves some disk access in the process. We've found that CF isn't all that quick about getting messages out of its spool, and with the naming system CF uses, the number of files that can exist in it's spool is limited to about 60,000 or so. If the spooler can't keep up, or if a file gets zero-byted and it dies completely, you'll have some serious problems on your hands. In our situation, we write the messages directly into the IIS SMTP service's pickup directory, naming the files with CreateUUID() and it works like a charm for up to about 80,000 messages a day, then IIS starts having problems keeping up. -Justin Scott, Lead Developer Sceiron Internet Services, Inc. http://www.sceiron.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com 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
