The ColdFusion Mail Spool Encountered An Invalid Spool File In The Spool Directory
Posted May 21, 2008 at 11:11 AM by Ben Nadel
I just realized that a bunch of people have commented on a post and I wasn't getting any email notifications for it (as I usually do). So, I went into my server and sure enough, there were dozens of emails in my undeliverable mail folder. I then went into my ColdFusion Administrator and viewed my mail logs and saw this error many times in a row for CFMail:
The ColdFusion Mail Spool Encountered An Invalid Spool File In The Spool Directory. The invalid file MailXXXXXX.cfmail was moved to the undeliverable directory.
What's strange is that I am getting some of the emails, but not all. After doing some quick Googling, I came across a post on MXimize.com. In the comments of that post, Gary Fenton points out that this is a known problem with ColdFusion 8.0.1. Apparently, there is a hotfix for it, but as of May 16th, 2008, it was not yet released publicly. I checked the latest hotfix, but none of the issues address are CFMail related.
The end result of this, though, is that I just got dozens of emails (after moving cfmail files into the Spool folder); so, sorry if I didn't get back to you yet.
What Other People Are Searching For
- Wanted: Full-Time ColdFusion Developer at Intoria Internet Architects
- Cold Fusion Senior Developer at Edge Information Management
- Back-End Web Developer-Information Technologist at Michigan State University
- ColdFusion Developer at Nonfat Media
- Mid-to-Senior Level Web Application Developer at SiteVision, Inc.
It looks like this is only a problem for mail with an attachment?
From what I gather, it's an attachment problem. All my emails have attachments due to the logo. Perhaps I should remove the logo... but I really like it :)
Yep, there's a lot of it about. We first spotted it at the end of April, but haven't managed to chase it down yet because it doesn't always fail. Meh. I'll give that dropTheAttachment idea a try and see if it helps.
Good luck getting to the bottom of it!
The hotfix is out already, I just failed at finding it..
It's linked to from this thread:
Awesome!! It worked like a charm.