Bug 49801

Summary:	VCards are sent with wrong mimetype text/x-vcard instead of text/directory (violation against standards: RFC 2425, RFC 2426)
Product:	[Unmaintained] kmail	Reporter:	Christian Wolfgang Hujer <Christian.Hujer>
Component:	mime	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED FIXED
Severity:	wishlist	CC:	psychonaut, tuju
Priority:	NOR
Version First Reported In:	1.4.3
Target Milestone:	---
Platform:	openSUSE
OS:	FreeBSD
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Christian Wolfgang Hujer 2002-10-27 23:00:55 UTC

Version:           1.4.3 (using KDE KDE 3.0.4)
Installed from:    SuSE RPMs
OS:          Linux

VCards are described in RFC 2425 and RFC 2426.
These state text/directory as the correct mime type for vCards.
But kmail / KDE use text/x-vcard instead.

Comment 1 Christian Wolfgang Hujer 2003-04-10 18:34:01 UTC

From RFC 2425, section 8.2.  Example 2:

   The next example illustrates the use of the Quoted-Printable transfer
   encoding defined in [RFC 2045] to include non-ASCII character in some
   of the information returned, and the use of the optional "name" and
   "source" types. It also illustrates the use of an "encoding" type
   parameter to encode a certificate value in "b".  A "vCard" profile
   [MIME- VCARD] is used for the example.

Content-Type: text/directory;
        charset="iso-8859-1";
        profile="vCard"
Content-ID: <id3@host.com>
Content-Transfer-Encoding: Quoted-Printable

begin:VCARD
source:ldap://cn=bjorn%20Jensen, o=university%20of%20Michigan, c=US
name:Bjorn Jensen
fn:Bj=F8rn Jensen
n:Jensen;Bj=F8rn
email;type=internet:bjorn@umich.edu
tel;type=work,voice,msg:+1 313 747-4454
key;type=x509;encoding=B:dGhpcyBjb3VsZCBiZSAKbXkgY2VydGlmaWNhdGUK
end:VCARD


So kMail should use Content-Type: text/directory;profile="vCard" instead of
Content-Type: text/x-vCard.


Bye

Comment 2 Cornelius Schumacher 2003-04-11 00:04:13 UTC

RFCs 2425/2426 describe vCard 3.0. For vCard 2.1 the text/x-vCard is the correct 
mime type. I suppose version 2.1 is still the more widely used format for attaching 
contact information to an email.

Comment 3 Christian Wolfgang Hujer 2003-07-01 01:26:39 UTC

What about letting the user choose wether to use vCard 2.1 with text/x-vCard or vCard 3.0 with 
text/directory;profile="vCard"?

Comment 4 Ingo Klöcker 2003-07-01 02:11:45 UTC

Subject: Re:  VCards are sent with wrong mimetype =?iso-8859-1?q?text=2Fx-vcard=09instead=20of=20text=2Fdirectory?= (violation against standards: RFC 2425, RFC 2426)

The user doesn't care for the version of the vCard unless it works. We 
won't bother him with this.

Comment 5 Stephan Kulow 2003-09-24 16:17:54 UTC

so it's a wishlist, right?

Comment 6 Tristan Miller 2005-12-14 00:27:46 UTC

Related to Bug 118287.

Comment 7 Tristan Miller 2009-04-25 23:42:56 UTC

KDE 4.2.2 is now using Content-Type: text/directory for vCards.  Is this enough for this bug to be closed as FIXED, or does the header actually need to be Content-Type: text/directory;profile="vCard" ?

Comment 8 Juha Tuomala 2009-07-05 18:35:57 UTC

My friend commented this bug with following:
> The OMA registered text/directory;profile=vCard for vCard 3.0.
> Additionally text/vcard is widely used. text/directory only is
> definitely the wrong content type for vCard 3.0.
>
> Please see here:
>
> http://www.openmobilealliance.org/tech/omna/omna-wsp-content-type.aspx

Could someone re-check this issue?

Comment 9 Thomas McGuire 2009-07-05 19:09:05 UTC

Fixed in the KDE4 version, as the mimetype handling of kdelibs was changed, and as a side effect of that we use text/directory instead of text/x-vcard now.