Had a bit of a strange one on a recent Exchange 2010 migration from Exchange 2003.  Email sent from a Hotmail account with two PDFs but the attachments did not show in Outlook (2010 or 2013, 2003 untested).  When viewing the properties of the email it reported the correct size of the total of the attachments, but no paper clip icon.  If the user logged into OWA the paper clip attachment icon shows and the two attachments were present.

When the same email was sent to a user whose mailbox was still on 2003 the attachments were visible in Outlook. At this stage incoming email was still on the original Exchange 2003 server as it had not been moved to the new Exchange 2010 server.  So it is clear that the two Exchange servers were handling this problematic email differently.

A quick scour of the web found this very useful post, but it was difficult to find.  Here is a précis of the post:

Solution to Outlook Attachments Not Showing

More »

I recently did an Exchange 2003 to Exchange 2010 migration and one of the Mac users reported a problem when trying to send large (~20MB) emails.  Even though I had removed all transport settings, mailbox settings, organisation settings which might be interfering, after further digging I found the Mac version of Outlook connects via EWS (Exchange Web Services) and this has a separate email limit.  There are many other references of this on the web with various commands and files to edit which people claim solve the problem.  There appears some confusion over the value of the numbers to enter in the web.config – in some versions of Exchange they are in bytes, in others they are in kilobytes.  Here is my fix:

Symptoms

Error seen on user’s computer:

Could not synchronize record: xxxxx to Exchange server: server

With the Error Code: -18493

More »

I have completed an Exchange 2003 –> Exchange 2010 migration and there is a problem mailbox which fails to move with a local move request.
It exists in ADUC, but the following error is logged on the Exchange 2010 server when moving:

Process powershell.exe (PID=6324). Object [CN=CONTROL,CN=Users,DC=domain,DC=co,DC=uk]. Property [HomeMTA] is set to value [domain.co.uk/Configuration/Deleted Objects/Microsoft MTA
DEL:da68e6fd-35b1-442a-ae0f-a05327bfc8b4], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible.

Also the Exchange Management Console would return ‘User xxx doesn’t have a primary mailbox’.  I tried running the Update-Recipient Powershell command and received the following output:

[PS] C:\Windows\system32>Get-Mailbox CONTROL | Update-Recipient
WARNING: The object domain.co.uk/Users/CONTROL has been corrupted, and it's in an inconsistent state. The
following validation errors happened:
WARNING: Database is mandatory on UserMailbox.
WARNING: Database is mandatory on UserMailbox.
Property RoleAssignmentPolicy can't be set on this object because it requires the object to have version 0.10 (14.0.100
.0) or later. The object's current version is 0.0 (6.5.6500.0).
 + CategoryInfo : NotSpecified: (0:Int32) [Update-Recipient], InvalidObjectOperationException
 + FullyQualifiedErrorId : 648D0DCE,Microsoft.Exchange.Management.RecipientTasks.UpdateRecipient

I could not find a way of fixing this – the user had a LegacyDN value set correctly, but as we did not need the user I was able to simply delete from EMC and it removed the AD object.