>Hey Tom! > >I think everyone's missed one detail here. Ryan... You said that you found >a file in the spool that was causing this problem... Was is zero bytes? If >not, this is a different problem.
No, it was not a zero byte file. >You said you "copied" the undeliverable message from the undelivr folder >into the spool? Did you rename it? What if it failed to get delivered >again (CF probably checks the spool at service startup), it fails again, and >when CF tries to move the file into the undelivr folder, whoops, a file by >that name already exists. I was thinking that the fact that I copied it instead of moving it might have been the problem. Before I removed the file from spool to get my server working again I made a copy of it. So later I copied this copy back into spool (the undelivr folder is empty now), and it still caused the same problem. So think it might have something to do with that specific message. Maybe there is a permission's issue? The file may have been owned by root when I copied it in there. I just tried it again and this time made sure the permissions on the file were the same as another file I saw that got dropped into the spool directory. It worked fine this time. So the the problem all along was the permissions on the file I copied into spool. My bad. Thanks for the good discussion. -Ryan ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com ------------------------------------------------------------------------------ Archives: http://www.mail-archive.com/cf-linux%40houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_linux or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
