Question
cfpop falls over with attachments with %'s in the name
Hi there,
We are running CF 7.02 MX on a Windows 2003 Server.
We have a scheduled process that runs which collects mail using cfpop, modifies it and forwards it on.
If any of the downloaded mails contains an attachment with an unusual character in it's name e.g..
AFU%image.JPG
..then the task falls over and doesn't complete. I've had a look in the application logs and this is accompanied by entries like...
"The resource D:\codepath\htdocs\attachment\ AFU%imge.JPG was not found.The root cause was: . The specific sequence of files included or processed is: D:\wwwroot\website\wwwroot\schedule\schedtask.cfm, line: 1254 "
Notice the % seems to have got it confused as to what the attachment name is. It seems to have lost the " a" somehow. So the failure is simply down to the fact that, having confused itself over what the filename actually is, it can no longer find the true path to the file.
If the attachments dont contain odd characters it works fine.
Any ideas? We're really struggling.
What I'm after is a workaround or a solution to the corruption of the filename since I'm guessing if it keeps the filename intact then all will be well (as it will still be able to find the file).
Tem
We are running CF 7.02 MX on a Windows 2003 Server.
We have a scheduled process that runs which collects mail using cfpop, modifies it and forwards it on.
If any of the downloaded mails contains an attachment with an unusual character in it's name e.g..
AFU%image.JPG
..then the task falls over and doesn't complete. I've had a look in the application logs and this is accompanied by entries like...
"The resource D:\codepath\htdocs\attachment\ AFU%imge.JPG was not found.The root cause was: . The specific sequence of files included or processed is: D:\wwwroot\website\wwwroot\schedule\schedtask.cfm, line: 1254 "
Notice the % seems to have got it confused as to what the attachment name is. It seems to have lost the " a" somehow. So the failure is simply down to the fact that, having confused itself over what the filename actually is, it can no longer find the true path to the file.
If the attachments dont contain odd characters it works fine.
Any ideas? We're really struggling.
What I'm after is a workaround or a solution to the corruption of the filename since I'm guessing if it keeps the filename intact then all will be well (as it will still be able to find the file).
Tem