Answered by:
Email Router - attachment names are incorrect and have an ID appended to the beginning.

Question
-
We're seeing an issue where attachments that are created through the Email Router have a weird ID appended to the front.
{cid6159DA28CE043D4F918B304E4EC581DC@company.com}test.pdf
This does not happen when you track emails through Outlook.
Any ideas? I'm guessing it might have something to do with email forwarding.
System information:
- CRM 2011
- Email Router with forwarding mailbox for incoming.
- Update Rollup 11
Monday, January 7, 2013 4:35 PM
Answers
-
Funny you should ask. We just resolved this on Friday accidentally. It was resolved after we uninstalled and reinstalled the email router. We had to reinstall because of an issue with diskspace and the email router being corrupted.
Hope that helps.
- Marked as answer by nrodriEditor Tuesday, February 19, 2013 1:16 PM
Monday, February 18, 2013 2:48 PM
All replies
-
I have exactly the same problem! No ideas??Monday, January 21, 2013 2:35 PM
-
We're currently working with Microsoft Support. It's leaning towards a bug, but they are getting me more details as for the cause of the bug. I'll keep this topic updated.Wednesday, January 23, 2013 3:24 PM
-
Same problem here...Tuesday, January 29, 2013 2:23 PM
-
Microsoft Support is still working on this issue. I'll post the solution when one is found.
Tuesday, January 29, 2013 2:25 PM -
Thanks!
Tuesday, January 29, 2013 2:27 PM -
Are there any news regarding this problem?
I've got a customer with the same behavior with UR 11.
But they are not using a forwarding mailbox.
The e-mail router is configured to access directly the mailbox of the queue.Monday, February 18, 2013 2:45 PM -
Funny you should ask. We just resolved this on Friday accidentally. It was resolved after we uninstalled and reinstalled the email router. We had to reinstall because of an issue with diskspace and the email router being corrupted.
Hope that helps.
- Marked as answer by nrodriEditor Tuesday, February 19, 2013 1:16 PM
Monday, February 18, 2013 2:48 PM -
Thank you for your response.
Yes, this fixed this problem on both environments (test and productive). Thank you!
Friday, February 22, 2013 1:51 PM