Wierd behavior, error #554-5.3.4 Content conversion limit(s) exceeded

Question

Hello
My customer have a local Exchange 2010 SP3 installation. 
They use a 3-party line of business application that tries to send an email with an attachment to another internal user.
The applications uses API to open a new mail in Outlook 2010 where the email is ready to send with the recipient, body and attachment. 
If the user presses send. They get a NDR right away. But if they remove the recipient address and type it manually again it works. 
The NDR says 
Diagnoseinformasjon for systemansvarlige:
Genererende server: FS1.mydomain.local
[email protected]
#554-5.3.4 Content conversion limit(s) exceeded 554 5.3.4 STOREDRV.Submit.Exception:ConversionFailedException; Failed to process message due to a permanent exception with message The content conversion limit has been exceeded. ConversionFailedException: The content conversion limit has been exceeded. ##
Opprinnelige meldingshoder:
Received: from FS1.mydomain.local ([fe80::39d4:621:4758:d99]) by
FS1.domain.local ([fe80::39d4:621:4758:d99%13]) with mapi id 14.03.0123.003;
Fri, 20 Sep 2013 11:29:04 +0200
MIME-Version: 1.0
Content-Type: text/plain
Date: Fri, 20 Sep 2013 11:29:04 +0200
Message-ID: <[email protected]>
Subject: =?iso-8859-1?Q?P=E5minnelse?=
Ive read up on Content conversion limit(s) and tried setting different limits on my transportconfig, transportserver, receiveconnector, sendconnector etc. Without any luck.
I see that alot of other users that get a similar NDR. Have descriptions that specify more detailed error reasons. Like for example to many attachments or to large header. But mine don't.
So i activated Pipeline tracing and content conversation tracing. 
This is my output
Microsoft.Exchange.Data.Storage.ConversionFailedException: The content conversion limit has been exceeded.
at Microsoft.Exchange.Data.Storage.ConversionAddressCollection.CreateResolutionList()
at Microsoft.Exchange.Data.Storage.ConversionAddressCache.Resolve()
at Microsoft.Exchange.Data.Storage.ItemToMimeConverter.get_AddressCache()
at Microsoft.Exchange.Data.Storage.ItemToMimeConverter.WriteFromHeader()
at Microsoft.Exchange.Data.Storage.ItemToMimeConverter.WriteMimeHeaders(MimeFlags flags)
at Microsoft.Exchange.Data.Storage.ItemToMimeConverter.ConvertItemToSummaryTnef(MimeStreamWriter writer, ConversionLimitsTracker limits, Boolean base64Encode)
at Microsoft.Exchange.Data.Storage.ItemConversion.<>c__DisplayClassc.<InternalConvertItemToSummaryTnef>b__b()
at Microsoft.Exchange.Data.Storage.ConvertUtils.CallCts(Trace tracer, String methodName, LocalizedString exceptionString, CtsCall ctsCall)
at Microsoft.Exchange.Data.Storage.ItemConversion.InternalConvertItemToSummaryTnef(Item itemIn, Stream mimeOut, OutboundConversionOptions options)
at Microsoft.Exchange.Data.Storage.ItemConversion.ConvertItemToSummaryTnef(Item itemIn, Stream mimeOut, OutboundConversionOptions options)
OutboundConversionOptions:
- detectionOptions: CharsetDetectionOptions:
- preferredInternetCodePageForShiftJis: 50222
- requiredCoverage: 100
- preferredCharset: null
- encodeAttachmentsAsBinhex: False
- suppressDisplayName: False
- internetMessageFormat: Mime
- internetTextFormat: HtmlAndTextAlternative
- imceaEncapsulationDomain: mydomain.no
- preserveReportBody: True
- byteEncoderTypeFor7BitCharsets: UseQP
- clearCategories: True
- owaServer:
- logDirectoryPath: C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\PipelineTracing
- isSenderTrusted: True
- dsnWriter: Microsoft.Exchange.Extensibility.Internal.DsnHumanReadableWriter
- userADSession: Microsoft.Exchange.Data.Directory.Recipient.ADRecipientSession
- useRFC2231Encoding: False
- recipientCache: Microsoft.Exchange.Data.Directory.Recipient.ADRecipientCache
- demoteBcc: False
- useSimpleDisplayName: False
- partialStnefConversion: False
- resolveRecipientsInAttachedMessages: True
- quoteDisplayNameBeforeRfc2047Encoding: False
- filterOutPredecessorChangeList: False
ConversionLimits:
- maxMimeTextHeaderLength: 2000
- maxMimeSubjectLength: 255
- maxSize: 2147483647
- maxMimeRecipients: 12288
- maxBodyPartsTotal: 250
- maxEmbeddedMessageDepth: 100
- exemptPFReplicationMessages: True
It is worth mentioning that the email only has 3 lines of text and the attachment is a 72 KB .tif file. Their is only one recipient. It doesn't matter what the recipient is. As long as he is the recipient from the line of business application.
The total .msg message size is 89 KB in total. 
Im completely stuck and appreciate every input.  

Answer 1

Really sorry to say Rob that we didnt find a solution. Our client just accepted it. Both Microsoft and the application provider pointed the finger at each other. And we hope to move this customer to Office 365 instead in time. 
Kinds regards
Karl Jørgen Weme
MCP
Please remember to click “Mark as Answer” on the post that helps you, and to click
“Unmark as Answer” if a marked post does not actually answer your question. Please
VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread.