Extra Header field

Bernhard Reiter bernhard at intevation.de
Mon Jul 12 18:18:47 CEST 2004


On Monday 12 July 2004 16:40, Joon Radley wrote:
> > -----Original Message-----
> > From: kolab-format-bounces at kolab.org
> > [mailto:kolab-format-bounces at kolab.org] On Behalf Of Bernhard Reiter
> > Sent: Monday, July 12, 2004 4:35 PM
> > To: kolab-format at kolab.org
> > Subject: Re: Extra Header field
> >
> > On Thursday 08 July 2004 16:14, Joon Radley wrote:
> > > Could we add a extra header to the mails containing the
> >
> > kolab format?
> >
> > > This will help me to determine if the message is a kolab
> >
> > format or a
> >
> > > normal mail without parsing the object twice in multipart
> >
> > mime encoded messages.
> >
> > It seems that everyone understand that remark, can someone
> > explain to me why this is the case?
> > If did not find anything in the format specs that we need to
> > use multi-part emails. Why not just having the mime-type set
> > in the header for the whole email?
> >
> > > It would look something like this:
> > > X-KOLAB-TYPE: application/x-vnd.kolab.note
>
> A Kolab object can have any number of attachments associated with it. This
> will create a multipart mail message.

Fine with me as opposed to having our kolab mimetype allowing attachments.
The question is why do you necessarily need to parse it twice in that case?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2145 bytes
Desc: signature
URL: <http://lists.kolab.org/pipermail/format/attachments/20040712/2ae12e43/attachment.p7s>


More information about the format mailing list