Re: Attachment sent becomes winmail.dat?

Paul Berkowitz wrote: 
On 11/21/05 12:12 PM, in article 43822A4A.2040705@xxxxxxxxxxxxxxxxxx, "Tim
Lapin" <timl@xxxxxxxxxxxxxxxxxx> wrote:

I don't know if that worked for you but here is hopefully a more helpful
answer.


You don't know if what worked? Why don't you think that Matt's suggestion of
people learning how to find things out for themselves is a good thing?

Nothing is wrong with learning more. However, this is a "help" forum and I consider it bad form when the resident experts who actually know the answer tell people in need to RTFM - politely or no - without at least providing some direction on finding the fix.

Of course, that's just my opinion.


I wasn't aware that Entourage was similarly affected.  It is after all,
a Microsoft product just like Outlook.


So bloody what? It's a separate application, made for the Mac. It has
nothing to do with Outlook, and as you can see for yourself, does not have
RTF format, Only plain text and HTML.

I had merely assumed that as part of in-house testing, such file format compatibility issues would have been addressed. No need to get testy.

I did not know that Entourage lacked RTF. Again, see my assumption above for products coming out of the same company. It is obviously a false assumption on my part.


A final note:  All email text should be Plain Text, whether or not you
are sending attachments.  Having the body in most commonly accepted,
smallest and least dangerous format practically guarantees smooth email
flow.


All email can be in whatever format you want. HTML works just fine - from
Outlook to Entourage, and otherwise.

It's a question of both style and larger compatibility. For instance, my company (a university) supplied Blackberry is basically a text only device when it comes to email. Yes, it can handle HTML but not consistently. I've received many an email with tags showing so the result is a morass of HTML gibberish with a bit of actual message mixed in. In short, unreadable. Many other people here use plain text emailers on UNIX boxes or similar packages. This dichotomy between regular "office" type users and the others is an unfortunate reality in a university.

You can ask your regular Outlook correspondents to set your contact to
receive plain text by default. (You cannot set it to receive HTML by
default.) In versions of Outlook up to 2002, hat will solve the problem. In
2003 there is usually no problem, but if there is (sender still uses RTF)
that will do the trick too.
Hope this helps! 

A little bit. But a little knowledge is a dangerous thing...


Coupled with a little guidance, it is a great thing.


--
Tim Lapin
timl@xxxxxxxxxxxxxxxxxx
.

Relevant Pages

  • Re: html email - pdf and images - OE Bug??
    ... for users of Outlook only). ... so OE can't read Outlook's html format? ... > I could certainly use plain text when creating my own emails (a little ... Forwarding the pdf ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: Exchange 2003 communication differences
    ... you're correct that Entourage and Outlook connect to Exchange ... messages in HTML, RTF and Plain text. ... HTML, however, old mail stores still have RTF as the default. ...
    (microsoft.public.mac.office.entourage)
  • Plain text replies - Should be easy enough
    ... I would like to set up Outlook such that when I want to reply to an HTML, ... plain text, or any kind of email for that matter, Outlook automatically ... an HTML email, it sets up the reply in HTML format, with the previous ...
    (microsoft.public.outlook)
  • Re: Outlook 2003 andf Word 2003
    ... > other Outlook users on your exchange server. ... > disable RTf to the internet, forcing everything to html or plain text. ...
    (microsoft.public.outlook)
  • Re: winmail.dat problems
    ... Plain text works, I spoke incorrectly before, but HTML still sends ... The address I'm testing with has "Let Outlook decide the best ... make sure it isn't marked to send in Outlook Rich Text. ...
    (microsoft.public.outlook.general)
Loading