[PATCH] encode mail address when passing via KApplication::invokeMailer

[Ingo Klöcker]

On Saturday 08 January 2005 17:38, Oswald Buddenhagen wrote:
> On Sat, Jan 08, 2005 at 05:18:39PM +0100, Ingo Klöcker wrote:
> > > the changed composer does not permit multiple to=s, a thing i do
> > > pretty often (not in urls, though, but that's because i don't do
> > > much html).
> >
> > I didn't touch the code which rips mailto: URLs apart (and thus
> > it's irrelevant that I didn't test with multiple to/cc/bcc). I just
> > changed the code of invokeMailer( to, cc, bcc, ... ), i.e. the code
> > which creates a new mailto URL from the given to, cc and bcc.
> > According to the above mentioned RFC the value after to=, cc= or
> > bcc= has to be the value of a RFC 822 message header encoded as
> > URL. In particular, multiple addresses are allowed per to=, cc= or
> > bcc=.
>
> yes, but to: is special: the first element (and only the fist one)
> happens to be the "core address". you removed this code without
> replacement. i don't think we can get around this problem without
> properly splitting the list.

Nope, you should really scan over RFC 2368 before trying to argue with 
me:

     mailtoURL  =  "mailto:" [ to ] [ headers ]
     to         =  #mailbox
 
   "#mailbox" is as specified in RFC 822 [RFC822]. This means that it
   consists of zero or more comma-separated mail addresses, possibly
   including "phrase" and "comment" components. Note that all URL
   reserved characters in "to" must be encoded: in particular,
   parentheses, commas, and the percent sign ("%"), which commonly occur
   in the "mailbox" syntax.

There's no such thing as a "core address".

Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20050108/922e21a0/attachment.sig>