Hi,
We keep receving from one customer a C.DAT attachent when they keep insisting that their sending an Excel file. They are using an Exchange server and were using Notes 6.0.3. Does anybody know what the reason for this might be.
They say it’s our Notes system, but I believe it’s something to do with the conversion of mime to notes.
Any ideas
Thanks
Subject: Recieving C.Dat attachment should be excel file
I can’t believe that ANY mail router changes c.xls to c.dat!
If you want to be 100% certain that attachmenbts make it intact through a mail router, zip the file first. The zip format maintains a 32bit crc checksum, that ensures that every bit makes it intact to the recipient.
Subject: RE: Recieving C.Dat attachment should be excel file
Apprently it’s not all email attachment that does this, only a select few users. Some emails come through as normal XLS attachments.
Subject: RE: Recieving C.Dat attachment should be excel file
Have you got access to the KnowledgeBase.The following is an extract:
Problem:
Messages sent from Outlook 98 or Outlook 2000 that contain an attachment are received in Notes with a C.DTF or ATTXXX.DAT attachment. Messages that contain no attachments from Outlook are received with no problems.
Solution:
Check to make sure the person sending the message from the Outlook client is not using Microsoft Exchange Rich Text Format. If the user’s address is in the Personal Address Book, deselect the checkbox labeled: “Always send to this recipient using Microsoft Exchange rich text format” in the Personal Name & Address Book (see sample bitmap below) (on the SMTP - General tab).
Also, check the outgoing email message from Outlook to see if the message was addressed to more than one recipient. If one recipient message is formatted using Outlook rich text and the other is not; the recipient receiving the message using Outlook Rich Text will not receive the message correctly while the recipient not using the Outlook Rich Text format will receive the message fine.
Hope this helps
John
Subject: RE: Recieving C.Dat attachment should be excel file
I thought this was something that Exchange does from time to time?
For example, a colleague uses Exchange, and every now and again attachments through as either “Winmail.dat” or “c.dat”.
I’m sure I read a technote about this somewhere…
–
Subject: RE: Recieving C.Dat attachment should be excel file
From Microsoft knowledgebase on this subject: http://support.microsoft.com/default.aspx?scid=KB;en-us;q138053
and a posting explaining how to prevent Outlook from sending native richtext: http://notes.crg.net/ibr/doc.nsf/0/eeff94f8a7b7cca4c1256dda0067fc0c?OpenDocument
Subject: RE: Recieving C.Dat attachment should be excel file
Try this website, just drag your .dat file onto the executable (when you have downloaded it!) and it should decode it for you. I have only used it a few times but it has worked every time (with winmail.dat anyway).
That should help stop people from blaming Notes for everything!
Subject: it’s a setting in the senders’ personal address book
The sender is probably sending Microsoft RichText (TNEF). In the Outlook clients’ personal address book, users can set the option to ‘always send to this user as MS Richtext’ or something similar. This option should be deselected. Seethis document at http://www.lotus.com/support for more info
Microsoft also has a technote on this issue, Technet Q articles Q138053 and Q259065 according to the Lotus KB.
Subject: Recieving C.Dat attachment should be excel file
Have the sender check the address book entry for the recipient. In the email address field, click with the right, and select properties. There’s a check box, that basically says they are sending to an outlook client (of course everyone in the world is microsoft centric). Have them uncheck the box, and remember this for next year when it happens all over again (mysteriously).
It’s just Microsoft’s version of the internet standard. ie. doesn’t work with anything else.
Subject: Recieving C.Dat attachment should be excel file
Open it in a hex editor (or Wordpad). Does it look like raw MIME? They often do. If so see
http://chris-linfoot.net/plinks/CWLT-5VGG8V
[Edited by author 10 Dec 2004]
Alternatively see this:
http://chris-linfoot.net/plinks/CWLT-66JGJ7
HTH