Hello, I have run into a problem that I am having trouble resolving. I am running Exchange 2003 SP2 on Windows Server 2003 SP2. The problem I am having is certain mailboxes are unable to send attachments internally. At first there was only one mailbox with the problem and it was only when they forwarded attachments. If they saved the attachment and sent a new message it would go fine. Then other mailboxes started having the same problem, at this point I would sayabout 30 of the mailboxes have thisproblem. Also, now some mailboxes can no longer send attachments internally at all, even from a new message. I do not have any virus software installed on the server to scan email and I run GFI anti-spam. I have looked through all the GFI settings and Ido notthink it is the problem, especially since the problem is mailbox specific. I have tried txt, doc, pdf attachments which are formats outlook should not block and I downloaded a COM add-on for Outlook to check which attachments it was blocking. I have also tried using outlook 2000, 2003 and 2007 clients as well as web access to send and recieve the emails. If anyone has any suggestions I would appreciate it! Thanks for your time! Michael

Exchange Server itself is pretty much message content agnostic. It really does not care what type of attachments you send or receive. It will not let one mailbox send a certain type of attachment, but another mailbox cannot. Outlook and Outlook Web Access, of course, can filter/prevent attachments from being opened. However, this does not sound like a client-side problem since it started with one mailbox and spread. Does GFI record any typeof log that might indicate that it is doing this? This does not sound likely since this is just happening to a few mailboxes. Now, here is the more ominous possibility. Since the problem is spreading, do you see anything in the Application event log when one of these mailboxes tries to send an attachment? It is remotely possible that the attachment table in the database is screwed up and the only way you might be able to fix this is to run an ISINTEG. One possibility is that if you are running E2K3 Enterprise and you can create another store. Then, move a few mailboxes to another store and see if the problem follows the mailbox to the other store.

Hi, Firstly, Exchange stores the attachments with single instance, so email sent to users in the same Store will refer to the same attachments. If the mailboxes are in the same store, the problem should be caused that the mailbox or attachment table one one of the mailbox is corrupted. Currently, please enable Diagnostic logging for Exchange: a. Open ESM b. Go to the UserA home server node. c. Open the property window of the server node and go to Diagnostics Logging tab. d. Change the following categories to maximum: MSExchangeIS\System\General MSExchangeIS\System\Virus Scanning MSExchangeIS\Mailbox\General MSExchangeIS\Mailbox\Rules When the problem reoccurs, please send us the event log. Generally troubleshooting steps: If we could take offline the users home mailbox store for a long time: a. Take offline the mailbox store in ESM b. To check the database, run the following command and select the offline mailbox store: C:\exchsrvr\bin\isinteg.exe -s <servername> -test alltests > isinteg_test.txt c. Check the isinteg_test.txt, if the warning or error count is not zero, we need to run the following command to repair the database: C:\exchsrvr\bin\isinteg.exe -s <servername> -fix -test alltests > isinteg_fix1.txt d. Check the fixed count in the output isinteg_fix1.txt, if the fixed count is not zero, we need to takestep bagain until the fixed count reach zero or not change. e. Take a full backup of the database. Note: Based on the database size and problem in the database, the steps might take long time, like 5-10G/hr. If we cannot take offline the mailbox store for a long time, we could try to move the mailbox to another store. As you see, the steps for troubleshooting this issue is the same as Jim. You can try it. Thanks Allen