
Hello everybody,
I have a CRM 2013 SP1 (V: 6.1.1.132 , DB-V: 6.1.0.581) on-premise installation with an Exchange Server 2010. Im trying to get a service structure up and running. For this purpose I have a distribution group for several external e-mail adresses which forwards the incoming e-mails to a user mailbox.
This mailbox, let's call this 'support.inbox', is configured as a forwarding mailbox within CRM. The incoming e-mails are fetched via server-side synchronization. Everything up to this point works well.
When it comes to the CRM task 'create an e-mail for the system out of that forward mailbox' I always get the error 'An error occured while creating the incoming email for the mailbox'.
I already disabled all workflow rules und double checked that there is no other user/mailbox uses the forwarding mail adress.
UPDATE
After reading the log files i found the folowing error message:
... rejected because the email was not a valid forwarded mail item
Ok, I started a new approach. I created a new user mailbox at the exchange server and made it a member of the distribution group (...and removed the support.inbox). In exchange owa I set up a 'forward as attachement' rule from my temporary mailbox to the support.inbox.
It ended up like the solution before...
Email for Forward Mailbox {570CED84-DBA2-E411-A0E7-00155DC86D02} was rejected because the email was not a valid forwarded mail item.
Logging response headers in: ExchangeIncomingEmailProvider for AsyncEvent: 10e4ce2e-9eb8-479b-bd75-2d8a3fe16a3f, Mailbox: 570ced84-dba2-e411-a0e7-00155dc86d02 -- Transfer-Encoding: chunked, Persistent-Auth: true, Cache-Control: private, Content-Type: text/xml; charset=utf-8, Date: Fri, 23 Jan 2015 09:46:14 GMT, Server: Microsoft-IIS/7.5, X-AspNet-Version: 2.0.50727, X-Powered-By: ASP.NET,
Please, can anybody help me?
Felix
*This post is locked for comments
I have the same question (0)Felix ... Did you ever sort this out? I'm running into the same issue for a CRM 2015 installation. It worked fine for months and then started throwing the same trace error just a few days ago.