Extra Header field

Bernhard Reiter bernhard at intevation.de
Mon Jul 12 16:41:12 CEST 2004


On Monday 12 July 2004 14:40, Joon Radley wrote:

> Three storage use cases:
> 1) Single body part mail, where content-type is set to
> application/x-vnd.kolab.*.
> 2) Multipart mail, where content-type is set to multipart/*

> Case (2) is the problem. Here you have to parse the entire message, look if
> any one of the body parts are application/x-vnd.kolab.* type and only then
> can you decide on the course of action. This can lead to double parsing of
> the same message.
>
> By adding a X-KOLAB-OBJECT header field to the header all use cases are
> satisfied by looking only at the header of the message. This header will
> only be stored on the IMAP4 server for kolab formatted messages and should
> never pass through a SMTP/LMTP gateway.
>
> By making the header optional you will have to parse all messages anyway
> before you can make the final decision, which totally negates the purpose
> of adding the header to the specification in the first place.

Not completely as when you find the header you know that you do not need
to start parsing and when the header is missing you might think about
doing the parsing anyway.
(Or add a X-KOLAB-OBJECT: No in the header once you did that.)
-------------- 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/58d1f3fc/attachment.p7s>


More information about the format mailing list