Hello,
We have been using Message.Download() to download the full message, including the one text/plain attachment that comes with the messages we're processing.
This worked like a charm for months, but suddenly stopped working today. The call to Download() just fails now. Attachment.Download() still works, but our compiled, deployed code uses Message.Download().
Our email provider (Rackspace) said they did make some changes to their system between yesterday and today, but they seem clueless to help me with this subtlety. What would cause Message.Download() to suddenly fail when an email has a single, text/plain attachment (under 2K bytes), but which would still work with Attachment.Download()?
I'm really hoping to find a solution that doesn't involve redeployment! :-)
-Tim
We have been using Message.Download() to download the full message, including the one text/plain attachment that comes with the messages we're processing.
This worked like a charm for months, but suddenly stopped working today. The call to Download() just fails now. Attachment.Download() still works, but our compiled, deployed code uses Message.Download().
Our email provider (Rackspace) said they did make some changes to their system between yesterday and today, but they seem clueless to help me with this subtlety. What would cause Message.Download() to suddenly fail when an email has a single, text/plain attachment (under 2K bytes), but which would still work with Attachment.Download()?
I'm really hoping to find a solution that doesn't involve redeployment! :-)
-Tim