554 5.6.0 STOREDRV.Deliver; Corrupt message content
Hello,
I am using Windows Server 2003 Standard x64 Service Pack 2, and Exchange Server 2007 Version: 08.03.0083.000 (SP3 installed).
Sometimes I get 554 5.6.0 STOREDRV.Deliver; Corrupt message content errormessage in Message Tracing, I do not have antivirus installed on that server.
Get-TransportAgent gives me:
Identity
Enabled Priority
--------
------- --------
Transport Rule Agent True
1
Journaling Agent True
2
AD RMS Prelicensing Agent False 3
Resending the mail usually helps, but it's not a solution.
August 24th, 2010 2:12pm
These can be difficult to track down. YOu may want to enable pipeline tracing per:
http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/d1673ad3-0706-4045-94f3-d6948e4f728f
to see if there is any pattern. If you get stuck, I suggest opening a ticket with Microsoft support.
Free Windows Admin Tool Kit Click here and download it now
August 24th, 2010 4:39pm
Hi,
Some Troubleshooting steps:
1. Is
problematic sender using Thunderbird to send message? In some circumstance, the Thunderbird client may send attachment with the incorrect Mime-Encoding as “Application/Applefile”, which can cause same symptom. If that’s the case, please ask
problematic sender to remove “mimeTypes.rdf” file as the third F&A in this
article, or replace the file with a good one as in this
case
2. If
problematic sender don’t use Thunderbird, please go on
3. Please
use “Get-TransportAgent” cmdlet on the Edge or Hub server, confirm which agents are on the server, like “Transport Rule Agent”, “Journaling Agent”
4. Please
reproduce the issue on problematic sender side, and then usepipeline
tracing to capture test message’s diagnose info as it
encounters transport agents
a. On
the server that logged that 5.6.0 error info, please activate the pipeline tracing
b. Launch
EMS, please run the cmdlets below
Set-TransportServer ServerName -PipelineTracingSenderAddressExtSenderAddress
Set-TransportServer ServerName -PipelineTracingPath
"C:\traceLogs"
Set-TransportServer ServerName -PipelineTracingEnabled
$True
Notes:
Please change ServerName to Hub or Edge server’s name; and also change ExtSenderAddress to that problematic external sender who can reproduce the problem
c. After
collecting the verbose log file for test message from that external sender, please disable the pipeline tracing, the files can accumulate quickly
Set-TransportServer ServerName -PipelineTracingEnabled
$False
d. Please
check the log file [Reference]
Resource:
MIME Encapsulation of Macintosh files - MacMIME
Ripu Daman Mina | MCSE 2003 & MCSA Messaging
August 24th, 2010 4:53pm
1. He is using Lotus Notes
2. -
3. I did paste te result to first post.
4. I enabled pipeline tracing, and the same problem occured. I have found the message tracelogs, it contains 6 files,
Original.eml
Routing0001.eml
Routing0002.eml
Routing0003.eml
Routing0004.eml
Routing0005.eml
All the files have exact same size.
What information should i find from these logs?
Free Windows Admin Tool Kit Click here and download it now
August 27th, 2010 3:22pm