I've encountered a problem regarding CFMail.  This is most likely nothing
new to a lot of you.  For some reason, a 0 byte .cfmail file is being
generated in the \cfusion\mail\spool directory (using CF 4.5.1 SP2).  From
what I can tell, this causes two things:

1) Processor jumps to 100% utilization
2) Subsequent .cfmail spool files are not sent

My fix is to stop the CF application service, clear the directory of 0 byte
files, and restart the service.  Things work from that point until another 0
byte file pops up.  It's not a terribly frequent occurance, but enough to
warrant attention.  

Here's where things get interesting.  The release notes for ColdFusion 5
indicate that...
"An improperly formatted file in the ColdFusion Server mail spool file no
longer causes all spooled mail to remain in the spool file and never be
sent. (21649)"
I migrated a server from 4.5.1 SP2 to 5.0 hoping that this problem would
dissapear.  No luck.  Same thing happens.  Try it out if you have a test
server.  Make a text file with a single space, give it a filename like
c45.cfmail, and throw it in the \cfusion\mail\spool directory.  The only
thing I'm wondering is if I would get different results from a clean install
of 5 rather than upgrading.  Regardless, this should have been corrected in
an upgrade. :P
Any ideas?  I'm stuck on this one.  I can't replace CFMail because I can't
find a replacement that has all of the attributes of CFMail (there are
hundreds of templates using CFMail, all using different combinations of
attributes).  I'm going to call MM next, but wanted to ask here before I
spent the money for a support call.
        Thanks,
        Eric Carlisle
        ColdFusion 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

Reply via email to