Winmail.dat - Revision history

Admin: 8 revisions imported

2016-04-06T20:39:42Z

8 revisions imported

← Older revision		Revision as of 16:39, 6 April 2016
(No difference)

63.239.86.1: fixed typos

2013-11-26T20:09:34Z

fixed typos

← Older revision		Revision as of 16:09, 26 November 2013
Line 1:		Line 1:
	Exchange sends attachments embedded in a winmail.dat archive, which RT doesn't handle.		Exchange sends attachments embedded in a winmail.dat archive, which RT doesn't handle.

	~~General~~ this is an Exchange misconfiguration because winmail.dat is an proprietary attachment format used by Microsoft and should only be used internally. If Exchange sends an email outside to the world it always ~~should~~ convert the winmail.dat attachment back in the native format because you ~~could~~ not expect that on the other side is always an Exchange server that ~~understand~~ winmail.dat. ;-)		Generally, this is an Exchange misconfiguration because winmail.dat is a proprietary attachment format used by Microsoft and should only be used internally. If Exchange sends an email outside to the world, it should always convert the winmail.dat attachment back to the native format because you should not expect that the other side is always an Exchange server that understands winmail.dat. ;-)

	== Solutions ==		== Solutions ==

	In Exchange 2010, disable "Use MAPI rich text format" on the General tab of the RT contact.		In Exchange 2010, disable "Use MAPI rich text format" in the General tab of the RT contact.

	In Exchange 2007, set "Use MAPI-RTF-Format" to "never" on the General tab of the RT contact.		In Exchange 2007, set "Use MAPI-RTF-Format" to "never" in the General tab of the RT contact.

	From ~~the~~ RT server side, you can pipe mail through /usr/bin/tnef (after installing it) and then through rt-mailgate. This may not always work, and configuring it is left as an exercise for the reader.		From RT server-side, you can pipe mail through /usr/bin/tnef (after installing it) and then through rt-mailgate. This may not always work, and configuring it is left as an exercise for the reader.

	== More information ==		== More information ==

63.239.86.1: fixed typo

2013-11-26T20:03:30Z

fixed typo

New page

Exchange sends attachments embedded in a winmail.dat archive, which RT doesn't handle.

General this is an Exchange misconfiguration because winmail.dat is an proprietary attachment format used by Microsoft and should only be used internally. If Exchange sends an email outside to the world it always should convert the winmail.dat attachment back in the native format because you could not expect that on the other side is always an Exchange server that understand winmail.dat. ;-)

== Solutions ==

In Exchange 2010, disable "Use MAPI rich text format" on the General tab of the RT contact.

In Exchange 2007, set "Use MAPI-RTF-Format" to "never" on the General tab of the RT contact.

From the RT server side, you can pipe mail through /usr/bin/tnef (after installing it) and then through rt-mailgate. This may not always work, and configuring it is left as an exercise for the reader.

== More information ==

http://support.microsoft.com/kb/241538

http://support.microsoft.com/kb/138053/

http://issues.bestpractical.com/Ticket/Display.html?id=9073

http://www.gossamer-threads.com/lists/rt/users/93866

http://en.wikipedia.org/wiki/Transport_Neutral_Encapsulation_Format