ANNOTATEMORE problems

[Joon Radley]

Hi David,

The "/comment" field is a generic field that can be written to by any client
that wants to add 'n comment to the mailbox.

We must use a specific/registered field else other clients can unknowingly (
and within their rights ) overwrite crucial information for our clients. The
clients may not overwrite a vendor registered tag that do not belong to
them.

Regards

Joon Radley
Radley Network Technologies CC
Cell: +27 (0)83 368 8557
Fax: +27 (0)12 998 4346
E-mail: joon at radleys.co.za
  

> -----Original Message-----
> From: kolab-format-bounces at kolab.org 
> [mailto:kolab-format-bounces at kolab.org] On Behalf Of David Faure
> Sent: Saturday, June 19, 2004 1:23 AM
> To: kolab-format at kolab.org
> Subject: Re: ANNOTATEMORE problems
> 
> On Friday 18 June 2004 16:59, David Faure wrote:
> > > I certainly agree with the fact that we can't use 
> "/comment" going 
> > > forward, and that we need to get a Kolab-specific annotation.
> > Yes.
> 
> Actually, Steffen made me rethink this.
> Given that cyrus-imapd doesn't support vendor entries, how 
> about using /comment with a kolab-specific string in it in 
> order to have something that works with the current 
> cyrus-imapd version? We could use the value /comment only if 
> it starts with "kolab.folder-type="  or something.
> 
> Does anyone know what other imap clients use /comment for? If 
> it's mostly unused, or something that users can set freely, 
> then this should be safe enough (if someone removes it 
> manually, he can expect trouble...)
> 
> --
> David Faure -- faure at kde.org, dfaure at klaralvdalens-datakonsult.se
> Qt/KDE/KOffice developer
> Klarälvdalens Datakonsult AB, Platform-independent software solutions
> 
> _______________________________________________
> Kolab-format mailing list
> Kolab-format at kolab.org
> https://kolab.org/mailman/listinfo/kolab-format