Re: Avoiding TNEF encoding / winmail.dat
- From: Ashutosh Bhawasinka <tech-talk@xxxxxxxxxxx>
- Date: Mon, 23 Jun 2008 20:20:59 +0530
If you are using extended MAPI you can TRY setting this property to false for the recipient
#define PR_SEND_RICH_INFO PROP_TAG( PT_BOOLEAN, 0x3A40)
Regards,
Ashutosh
jblum2000@xxxxxxxxx wrote:
Probably a newbie question, but I haven't been able to find the.
answer...
A program I'm working on has been using Simple MAPI to generate an
email, attach a file, and mail them to clients... some of whom can't
read the attachment because it shows up as winmail.dat. I've tried
disabling Rich Text in both Outlook and Exchange, but no matter what I
do it still seems to be forcing the attachments into TNEF format.
Is there anything I can do either in Simple or Extended MAPI to force
the attachments to be encoded in a readable format?
(Interestingly, when the message shows up in the Outlook outbox, I can
successfully forward it to the client, and then the attachment shows
up correctly. I also get good results if I have Outlook display the
message before sending, and retype the address -- which suggests that
it the problem has something to do with address resolution, and MAPI
handling it differently than Outlook. Any ideas?)
Cheers,
Jon Blum
- Follow-Ups:
- Re: Avoiding TNEF encoding / winmail.dat
- From: jblum2000
- Re: Avoiding TNEF encoding / winmail.dat
- References:
- Avoiding TNEF encoding / winmail.dat
- From: jblum2000
- Avoiding TNEF encoding / winmail.dat
- Prev by Date: Re: Access to IOlkAccountManager::EnumerateAccounts function
- Next by Date: Re: Access to IOlkAccountManager::EnumerateAccounts function
- Previous by thread: Avoiding TNEF encoding / winmail.dat
- Next by thread: Re: Avoiding TNEF encoding / winmail.dat
- Index(es):
Relevant Pages
|