![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
![]()
Hi everyone,
I have user that cannot send faxes from his Outlook 2003. I checked with the vendor and they say it's an encoding problem (TNEF): Content-Type: application/ms-tnef; name="winmail.dat" It cannot be sent in this format. According to what I've read, this has to do with Rich Text, however sending as Plain Text or HTML has the same results. Under "Internet Format" the option "Convert to HTML" is also active. What can I do to make sure the message is not sent in TNEF? Thanks, David |
Ads |
#2
|
|||
|
|||
![]()
You did not provide any information. Fax software and sending method would
be a minimum. -- Russ Valentine [MVP-Outlook] "David" wrote in message ... Hi everyone, I have user that cannot send faxes from his Outlook 2003. I checked with the vendor and they say it's an encoding problem (TNEF): Content-Type: application/ms-tnef; name="winmail.dat" It cannot be sent in this format. According to what I've read, this has to do with Rich Text, however sending as Plain Text or HTML has the same results. Under "Internet Format" the option "Convert to HTML" is also active. What can I do to make sure the message is not sent in TNEF? Thanks, David |
#3
|
|||
|
|||
![]()
Thank you for replying and sorry for the lack of info.
The fax solution is provided by Wirefast and there is no additional software, faxes are sent and received via a shared mailbox. To send they just need to type the number followed by @fax.company.com in a new e-mail message. Only this one user has this problem. David "Russ Valentine [MVP-Outlook]" wrote: You did not provide any information. Fax software and sending method would be a minimum. -- Russ Valentine [MVP-Outlook] "David" wrote in message ... Hi everyone, I have user that cannot send faxes from his Outlook 2003. I checked with the vendor and they say it's an encoding problem (TNEF): Content-Type: application/ms-tnef; name="winmail.dat" It cannot be sent in this format. According to what I've read, this has to do with Rich Text, however sending as Plain Text or HTML has the same results. Under "Internet Format" the option "Convert to HTML" is also active. What can I do to make sure the message is not sent in TNEF? Thanks, David |
#4
|
|||
|
|||
![]()
This is probably not an Outlook issue, then. You need to look at the form
this service uses to collect the fax request from Outlook and why it is not in plain text. Or see what your user is doing to create a message that is not in plain text. -- Russ Valentine [MVP-Outlook] "David" wrote in message ... Thank you for replying and sorry for the lack of info. The fax solution is provided by Wirefast and there is no additional software, faxes are sent and received via a shared mailbox. To send they just need to type the number followed by @fax.company.com in a new e-mail message. Only this one user has this problem. David "Russ Valentine [MVP-Outlook]" wrote: You did not provide any information. Fax software and sending method would be a minimum. -- Russ Valentine [MVP-Outlook] "David" wrote in message ... Hi everyone, I have user that cannot send faxes from his Outlook 2003. I checked with the vendor and they say it's an encoding problem (TNEF): Content-Type: application/ms-tnef; name="winmail.dat" It cannot be sent in this format. According to what I've read, this has to do with Rich Text, however sending as Plain Text or HTML has the same results. Under "Internet Format" the option "Convert to HTML" is also active. What can I do to make sure the message is not sent in TNEF? Thanks, David |
#5
|
|||
|
|||
![]()
Ok, I'll see what I can find out.
Thank you Russ. David "Russ Valentine [MVP-Outlook]" wrote: This is probably not an Outlook issue, then. You need to look at the form this service uses to collect the fax request from Outlook and why it is not in plain text. Or see what your user is doing to create a message that is not in plain text. -- Russ Valentine [MVP-Outlook] "David" wrote in message ... Thank you for replying and sorry for the lack of info. The fax solution is provided by Wirefast and there is no additional software, faxes are sent and received via a shared mailbox. To send they just need to type the number followed by @fax.company.com in a new e-mail message. Only this one user has this problem. David "Russ Valentine [MVP-Outlook]" wrote: You did not provide any information. Fax software and sending method would be a minimum. -- Russ Valentine [MVP-Outlook] "David" wrote in message ... Hi everyone, I have user that cannot send faxes from his Outlook 2003. I checked with the vendor and they say it's an encoding problem (TNEF): Content-Type: application/ms-tnef; name="winmail.dat" It cannot be sent in this format. According to what I've read, this has to do with Rich Text, however sending as Plain Text or HTML has the same results. Under "Internet Format" the option "Convert to HTML" is also active. What can I do to make sure the message is not sent in TNEF? Thanks, David |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
SP2 removing TNEF attachment | [email protected] | Add-ins for Outlook | 0 | March 5th 07 04:24 PM |
OE6 - cannot open/decode MS-TNEF | Ah Koh | Outlook Express | 2 | July 25th 06 08:39 PM |
TNEF stripped | [email protected] | Outlook - Using Forms | 2 | June 20th 06 05:55 PM |
Sending mails not using TNEF | Ingmar Bauer | Outlook and VBA | 1 | February 22nd 06 11:30 PM |
Outlook to Outlook TNEF Problem | Paud | Outlook - General Queries | 0 | February 13th 06 01:16 PM |