Email without attachment but size indicates attachment?

[Walter Cohen]

Someone sent me an email with an attachment (family-related newsletter) but
when I go to my Inbox it does not show the attachment as the paperclip.
The size of the email does indeed indicate an attachment at about 6 MB.

If I go to the email's Properties => Details, I click on Message Source and
get this huge amount of data starting with:

--Boundary_(ID_4RQkoLrkg5p876R5KArYGQ)
Content-type: application/ms-tnef; name=winmail.dat
Content-transfer-encoding: base64
Content-disposition: attachment; filename=winmail.dat
....
....

Why did the data not come across as an attachment and is there a way to
somehow make the data a real attachment?

Thanks,
W

 

[Guest]

Someone sent me an email with an attachment (family-related newsletter)
but when I go to my Inbox it does not show the attachment as the
paperclip.
The size of the email does indeed indicate an attachment at about 6 MB.

If I go to the email's Properties => Details, I click on Message Source
and get this huge amount of data starting with:

--Boundary_(ID_4RQkoLrkg5p876R5KArYGQ)
Content-type: application/ms-tnef; name=winmail.dat
Content-transfer-encoding: base64
Content-disposition: attachment; filename=winmail.dat
...
...

Why did the data not come across as an attachment and is there a way to
somehow make the data a real attachment?

Thanks,
W

Sounds like you don't have a decoder for base64 installed, so Windows
Mail can't decode it and make it an attachment. Sorry, I'm not aware of
where to get one.

 

[Frank Saunders MS-MVP IE,OE/WM]

Someone sent me an email with an attachment (family-related newsletter)
but when I go to my Inbox it does not show the attachment as the
paperclip.
The size of the email does indeed indicate an attachment at about 6 MB.

If I go to the email's Properties => Details, I click on Message Source
and get this huge amount of data starting with:

--Boundary_(ID_4RQkoLrkg5p876R5KArYGQ)
Content-type: application/ms-tnef; name=winmail.dat
Content-transfer-encoding: base64
Content-disposition: attachment; filename=winmail.dat
...
...

Why did the data not come across as an attachment and is there a way to
somehow make the data a real attachment?

Thanks,
W

The mail was sent from Outlook, using Outlook's RTF format. Outlook is the
only program I know or that can decoder that format. Ask the sender to
please use plain text when sending to people who do not have Outlook.

 

[Hal Hostetler [MVP P/I]]

As Frank says, this email was sent from Office Outlook in Rich Text Format.
The ONLY program able to read RTF formatting is Outlook, ALL other email
clients will either get a "Winmail.dat" attachment that can't be opened, or
no attachment at all. The fix is to NOT use RTF and use either HTML or
Plain Text as the default message format.

http://support.microsoft.com/?kbid=287720
OL2002: Attachments Are Not Visible to Some Recipients When You Use TNEF
http://support.microsoft.com/?kbid=290809
OL2002: How Message Formats Affect Internet Mail
http://support.microsoft.com/?kbid=197064
OL2000: (CW) Winmail.dat Attachments Included in Received Messages
http://support.microsoft.com/?kbid=224817
OL2000: Transport Neutral Encapsulation Format (TNEF) Basics

Decoder programs to read a WINMAIL.DAT file are here:

http://www.slipstick.com/addins/decoders.htm
Decoder Tools

Hal
--
Hal Hostetler, CPBE -- (e-mail address removed)
Senior Engineer/MIS -- MS MVP-Print/Imaging -- WA7BGX
http://www.kvoa.com -- "When News breaks, we fix it!"
KVOA Television, Tucson, AZ. NBC Channel 4
Live at Hot Licks - www.badnewsbluesband.com

 

[Walter Cohen]

Thanks.
The sender said he zipped it before sending (which doesn't sound right
according to what you guys have just said).
The sender has since just sent as-is (non-zipped) and it did come across as
an attachment and readable.

W

 

[Frank Saunders MS-MVP IE,OE/WM]

It's still an attachment and Outlook screws up any attachment when using its
RTF format.

 

[Walter Cohen]

Ok, thanks Frank!

It's still an attachment and Outlook screws up any attachment when using
its RTF format.