Got it!
The Content-type for WHOLE conversion result should be message/rfc822, not
multipart/mixed. Tested with Pegasus Mail and Mozilla readers; OK. Tre clue was "X-
Mailer" header, natural for nested message and innatural for "mixed" part.
See right structure prodiced by patched tnef2multipart; tnef2multipart.diff is in
attachment. Next step is to add informative subject to this message, "Converted from..."
Alexey
--Message-Boundary-26099
Content-Type: message/rfc822; name="mime-24566"; type="message/rfc822"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="mime-24566"
Content-Type: multipart/mixed; boundary="----------=_1053518443-24566-0"
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.411 (Entity 5.404)
X-Sanitizer: 81055@xyz.molar.is
This is a multi-part message in MIME format...
------------=_1053518443-24566-0
Content-Type: application/msword; name="1997ap2.doc"
Attachments:
+ http://mailtools.anomy.net/archives/anomy-list//10/04/3ecb6f94/01.tnef2multipart.rfc822.patch