Hi all, Consider this setup: Exchange (2010) On-Premise (Version 14.2 (Build 247.5)) organization mailbox1 has a rule (created in OWA), that forwards as attachment some emails to another mailbox2 in this organization. Everything works well, source emails that came to mailbox1 appears in another mailbox2 as "email" attachments inside new generated emails with (FW: <source_subject>) form. We can open "email" attachment in new view window (Outlook, OWA) or view it inline (using preview feature of Outlook) - and successfully get the source email, using mailbox2 connection session (via Outlook or OWA or EWS), we can see and access (open, save) "file" attachments in source email, but ... Consider this problem: ... if source email has one of "file" attachments, that has empty (zero sized (0 bytes) file) content, (attachment object in email has a name (e.g. file1.txt) and shows itself as 64B in Outlook and in OWA) - attempt to access this "file" attachment in any way is leading us to this errors: Outlook inline preview: double click - (Not found) Save As - (Cannot save the attachment. Not found) Outlook new window: single click - (This file cannot be previewed because of an error with the following previewer: Windows TXT previewer) double click - (The operation failed) Save As or Save all attachments - (Cannot save the attachment) OWA: single click or Download all attachments - (The item you tried to access no longer exists. The item wasn't found. You or a delegate might have moved or deleted it using another computer or a mobile phone.) Save Target As - (Unable to download attachment.ashx from <server>. The file could not be written to the cache) CRM 2011 Email Router: EWS polling provider: -- Microsoft.Crm.Tools.Email.Providers.EmailException: Error: The specified object was not found in the store. at Microsoft.Crm.Tools.Email.Providers.ExchangeWSConnector.LogEwsResponseErrorWarning(ResponseMessageType responseMessageType) at Microsoft.Crm.Tools.Email.Providers.ExchangeWSConnector.RetrieveAttachments(ExchangeEmailMessage emailMessage, ArrayList& attachmentList) at Microsoft.Crm.Tools.Email.Providers.ExchangeEmailMessage.GetAttachments() at Microsoft.Crm.Tools.Email.Providers.ExchangeEmailMessage.ValidateMessage(Boolean isForwardMailbox) at Microsoft.Crm.Tools.Email.Providers.ExchangePollingMailboxProvider.ValidateMessageInternal(EmailMessage emailMessage) at Microsoft.Crm.Tools.Email.Providers.CrmPollingMailboxProvider.Run() -- What I have already tried: from mailbox1, problematic source email with one empty attachment was processed manually (Forward as attachment)+(Send) - result is perfect, no errors when accessing this empty attachment (e.g. file1.txt): opened as empty notepad window saved as 0 bytes size file, in filesystem folder or in (*.zip) when OWA (Download all attachments) used. I suppose, that server-side rule processing algorithm - is not storing (or not linking properly) empty "file" attachment inside (forwarded as attachment) "email" attachment. Can anyone help to solve/workaround this server-side rule behavior?

Hello, How about using the journaling rule to forward the copies of messages? Thanks, Simon

Hi, Simon Does journal rule deliver source emails (that came to mailbox1) as "email" attachments in new generated messages to Inbox of journaling mailbox? (forward-as-attachment technique)? I haven't find such info in technet docs. I you tested JRule - tell me, how source messages appears in JMBox ...

Hello, Yes, the email is enclosed as an attachment. Please see: Thanks, Simon

Thanks, Simon! It works, empty attachment is accessible from copy of source email, attached as "email" attachment, in new message generated by Journal Rule to Inbox of in mailbox2. It's a workaround.

Besides, when I create, in mailbox1, the same mailbox rule with (forward as attachment) technique, but with Outlook (2007) also - behaviour is the same: empty "file" attachments is not accessible in source email, acquired from "email" attachment, in new (FW: ...) message generated by this rule to Inbox of mailbox2. So, I think, it's definitely a server-side rule processing algorithm bug, independing of particular client (OL/OWA) rule creation channel.