| 2011-11-04 21:07:45 |
John Hein |
description |
I am seeing the following header on a vcard from outlook:
Content-Type: text/directory; charset="utf-8"; profile=vCard
Content-Description:
Content-Disposition: attachment; filename="default.vcf";
creation-date="Fri, 04 Nov 2011 15:39:28 GMT";
modification-date="Fri, 04 Nov 2011 15:39:28 GMT"
Content-Transfer-Encoding: quoted-printable
Editing the raw message and changing "directory" to x-vard gets it decoded and displayed in pretty format.
Otherwise, I just see the raw vcard text:
BEGIN:VCARD
PROFILE:VCARD
VERSION:3.0
MAILER:Microsoft Exchange
PRODID:Microsoft Exchange
.
.
etc.
According to wikipedia (not really authoritative, I know), text/directory and another variant are valid mime types - not to mention mail clients out there that probably just set application/octet-stream and rely on receiving clients to guess what to do based on filename extension (.vcf or .vcard) (similar to the common issue with application/octet-stream and .pdf filenames). |
I am seeing the following header on a vcard from outlook:
Content-Type: text/directory; charset="utf-8"; profile=vCard
Content-Description:
Content-Disposition: attachment; filename="default.vcf";
creation-date="Fri, 04 Nov 2011 15:39:28 GMT";
modification-date="Fri, 04 Nov 2011 15:39:28 GMT"
Content-Transfer-Encoding: quoted-printable
Editing the raw message and changing "directory" to x-vcard gets it decoded and displayed in pretty format.
Otherwise, I just see the raw vcard text:
BEGIN:VCARD
PROFILE:VCARD
VERSION:3.0
MAILER:Microsoft Exchange
PRODID:Microsoft Exchange
.
.
etc.
According to wikipedia (not really authoritative, I know), text/directory and another variant are valid mime types - not to mention mail clients out there that probably just set application/octet-stream and rely on receiving clients to guess what to do based on filename extension (.vcf or .vcard) (similar to the common issue with application/octet-stream and .pdf filenames). |
|
