TNEF

[David]

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

 

[Russ Valentine [MVP-Outlook]]

You did not provide any information. Fax software and sending method would
be a minimum.

 

[David]

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

You did not provide any information. Fax software and sending method would
be a minimum.
--
Russ Valentine
[MVP-Outlook]

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

 

[Russ Valentine [MVP-Outlook]]

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]

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

You did not provide any information. Fax software and sending method
would
be a minimum.
--
Russ Valentine
[MVP-Outlook]

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

 

[David]

Ok, I'll see what I can find out.
Thank you Russ.

David

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]

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

You did not provide any information. Fax software and sending method
would
be a minimum.
--
Russ Valentine
[MVP-Outlook]
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