can I disable the TNEF format in journaling?

Thursday, May 17, 2007 4:05 PMcRRRum

0
Sign In to Vote
Hello all,

Hope this is possible. It looks like journaling in Exchange 2007 makes the journaled message into a TNEF attachment. Is there any way to not turn the attachment into a TNEF?

Several things I've noticed about this which are BAD and possibly not compliant.

1. TNEFs are bigger than the original message.
2. Plain text messages are transformed into RTF.
3. Downloading messages via Pop3 is missing the message body.

The journaling process claims to attach the original message "unaltered". Transforming the message into TNEF is not leaving it "unaltered". I hope someone here can help me out on this!

Regards,
Roy
- Reply
- Quote

All Replies

Monday, May 21, 2007 3:20 AMDavid StromeMSFT

0
Sign In to Vote
hi Roy.

I'm not sure what your configuration is. Specifically, where you're sending your journal reports. We are correcting an issue with message conversion when the messages are sent to a non-Exchange mailbox. They remain as TNEF. In SP1, messages sent outside of Exchange will be downconverted to MIME unless explicitly configured otherwise.

However I spoke with the dev, and he mentioned that if the *attached* message is TNEF, that's what it really was.

hope this helps,

david.
- Reply
- Quote
Wednesday, May 23, 2007 3:03 PMMichael Myers

0
Sign In to Vote
Is there a more detailed description of this particular issue available? I believe that we are seeing some of the same behavior, where messages that are not otherwise sent outside of Exchange are being sent in TNEF format to the journaling contact, where that journaling contact is a mailbox outside of the Exchange.

You mention the fix being available in SP1 - is there a chance for a hotfix? Also, the TNEF format that the messages are being sent in does not appear to match the usual format, as the common third-party parsers indicate a format error in the winmail.dat - likely just a format change, but still one that makes the mails unparsable.

With this fix, will there also be a way to re-parse the messages that were sent originally in TNEF to get them back into MIME? Organizations are sending out their required compliance data in this format, and it will really need to be read.
- Reply
- Quote
Friday, May 25, 2007 9:37 AMMerlinBee

0
Sign In to Vote
I am also very keen to get this fixed.

Is there any information on the changes to the TNEF format in Exchange 2007. It seems that our existing TNEF parser now breaks, as do all others that we tried.
- Reply
- Quote
Saturday, June 23, 2007 2:19 AMelephantoutlook

0
Sign In to Vote

Journaling in Exchange 2007 stores the journal report message into a TNEF ( http://en.wikipedia.org/wiki/TNEF ) attachment. When sending to a remote SMTP address (non exchange) this format needs to be formated to converted to MIME format.

Is there a work around for this message conversion for messages sent to non Exchange mailboxes?

Is it true this is fixed in Exchange 2007 SP1?
- Reply
- Quote
Wednesday, July 11, 2007 5:30 PMelephantoutlook

0
Sign In to Vote

The enterprise journaling in Exchange 2007 envelope journals the messages with the attached original. But the attached original attached message is TNEF encoded (winmail.dat). Exchange 2007 doesn’t convert attached messages from TNEF to MIME encoding even if the message is delivered to a local mailbox or a remote SMTP address. Attachments are just not converted. So even if you POP the email from the local mailbox the attachment is still TNEF encoded.

There is a setting (http://technet.microsoft.com/en-us/library/bb310786.aspx) to force MIME encoding on internal mailboxes or external contacts, but since the message attachment is encoded TNEF and not the original message, this doesnt change the behavior of the attachment. This is referred in a post above about SP1 including this change, but since the message is still "attached" then the encoding will not change on attachments only the original messagae.

Could someone at Microsoft please clarify the issue, workarounds, or possible updates/fixes for this solution.
- Reply
- Quote
Tuesday, September 18, 2007 7:07 PMDuke2

0
Sign In to Vote
Just wanted to bring this thread to the top since no response was received for the above message from elephant.

I'm currently stuck with the same issue. I wish Microsoft releases a hot fix for this, since waiting for SP1 release is too much a time waste for me.

Thanks

Duke
- Reply
- Quote
Monday, October 08, 2007 7:45 PMRkd80

0
Sign In to Vote
I am going to echo that sentiment, I am surprised by the lack of search results on this.

We just tried the new SP that supposedly implements a fix for this and seeing the exact same results. the most pressing issue is:

Journalized messages contain no bodies when viewing in Outlook Express.

Processing them in Java with our custom code reveals that the body is now nestled deep inside the TNEF in a different location from where it used to be in 2003. This appears to be a bug clearly, yet there is virtually no documentation on the matter.
- Reply
- Quote
Monday, October 08, 2007 11:07 PMDuke2

0
Sign In to Vote
It looks like there's not going be a hotfix for this. Microsoft is currently working on releasing SP1 which has this problem fixed but that's only going to be available for 64 bit production version and not 32 bit developer version. However we havent still got a concrete date on the release date but it's going to be somewhere in this quarter. Until then you have to use 64 bit beta2 version that has the TNEF problem solved.

I'm still stuck with the same issue and am currently experimenting with Microsoft's TNEF reader class. However it's not very user-friendly.

Another useful hint for you: Try development thread instead of compliance thread next time on this topic. There are more Microsoft guys to help in that thread than in compliance. You'll get more info there than here on the same topic.

GL

Duke
- Reply
- Quote
Tuesday, October 20, 2009 5:23 PMDevin - Utopia Systems

0
Sign In to Vote
Any progress with this issue? I just heard back from Global Relay an apparently we've had an issue sending them TNEF attachments since we implemented Exchange 2007. All solutions implied here do not help as outlined by ElephantOutlook because it is the journaled envelope attachment that is the problem and not the actual journaled message formatting to that is delivered to the external contact at global Relay which is always sent as plain text. So changing our default remote domain encoding options and setting the contact to never use RTF is not helping any at all because it's the attachment that is the issue and being encoded during internal transport.

Also we have had Exchange 2007 SP1 installed for some time now and it has not helped on any level. RTF is disabled on every level . The issue is, the original journaled MAPI messages transported from the 2007 Mailbox server through to our SMTP servers stamped as TNEF as shown below. Is there a switch that can be run on your built in 2007 connectors to supress the MS TNEF Correletion stamp when messages are intially sent? This is not just affecting one sender or even one domain, it's affecting all of our journaled messaging Exchange 2007. Exchange 2003 mailboxes all work fine using the very same 2007 journaling mailbox.

- 
X-MS-Has-Attach:

X-MS-Exchange-Organization-SCL: -1

X-MS-TNEF-Correlator: <CBC98232-3006-4C7B-BD2B-2D6B0ED21D43@aa.org >

MIME-Version: 1.0
- Reply
- Quote