Sent dist list or vcard arrive as dat files
A client using Outlook 2003 sends distribution lists weekly to all staff - they delete the existing one and update with the new one. This week no one could access them, they all arrived as dat files. Both 'ends' have Outlook set to send in html, sender has tried sending using Outlook as editor and Word. I had her send me a test as well (I use Outlook 2003 as well), same problem. The problem is also happening when she attaches a single contact as a vcard - it arrives as a dat file. Has anyone had a similar experience and figured it out?
ASKER
I wondered if that was the problem myself, but both the sender and her office mate, and my own copy for that matter, are set to use html.
ASKER
The attachment comes up on my machine named Untitled Attac.dat
ASKER
The attachment comes up on my machine named Untitled Attac.dat
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Both places, that I know of, in Outlook 2003 are set to use html format. Compose message is set to html, Rich Text Options in Internet Format is set to use html. Is there another setting somewhere that I'm missing yet?
onsquirrel,
I thought there was an option as well to turn on and off RTF, but if you have that off (Internet format for HTML), then I think it should be all good.
I wondered if the header or coding within the vcard is causing it to not be recognized and thus it defaults to WINMAIL.DOT. Do you have an old version that still works?
If so, can you open the old version and the new version, copy the text to a notepad and see if something is damaged in the coding. Or use an older one to create a new message? Also, will the older ones, when resent, still cause the issue?
Kevin
I thought there was an option as well to turn on and off RTF, but if you have that off (Internet format for HTML), then I think it should be all good.
I wondered if the header or coding within the vcard is causing it to not be recognized and thus it defaults to WINMAIL.DOT. Do you have an old version that still works?
If so, can you open the old version and the new version, copy the text to a notepad and see if something is damaged in the coding. Or use an older one to create a new message? Also, will the older ones, when resent, still cause the issue?
Kevin
ASKER
It doesn't seem to matter whether we send a new one or an old one, the result is still a .dat file. When I send a dist list from my own copy of Outlook 2003 to the client, it is received as a .dat file. When I send it to myself, it arrives in a form that I can use - still a dist list. The problem definitely seems to be at their end.
Would there have been any updates (other than from MS as they are not automatic) that would have happened in the last 2-3 weeks that might have changed something? Nothing else has changed!
Would there have been any updates (other than from MS as they are not automatic) that would have happened in the last 2-3 weeks that might have changed something? Nothing else has changed!
How are you doing?
The option to use Rich Text Format (RTF) is probably selected in the Outlook of the sender and Outlook then tries to attach it as a WINMAIL.DAT file. The reason that this changed from working to all of a sudden not is probably "this weeks" message had some formatting that caused the RTF to "trigger" and thus it "wrapped" it up as a .DAT file.
See this:
http://help.lockergnome.com/windows2/access-vCard-forwarded-ftopict489033.html
If that doesn't do it, see this:
http://www.zimbra.com/forums/users/7118-vcard-vcf-attachments.html
Hope this helps,
Kevin