Hi all,
...the story continues...
As a part of our project, we need to support TPM hardware as certificate
source for client-authentication against client-auth-enabled services. Within
Kolab context, these are mainly IMAPS, SMTPS, LDAPS and HTTPS. The tpm-tools
suite and openCryptoki will
Hi all,
...still continuing...
Kolab makes use of RFC5464 - The IMAP METADATA Extension IMAP folder
annotations to differentiate between the various folder types which are
handled by Kolab. Remember, anything (Email and PIM data) is stored as Email
messages with XML attachments in IMAP
On tuesday 20 July 2010 Christian Hilberg wrote:
[...]
From within Evolution, *only* the IMAP folder which is annotated Email
^^
the IMAP folders which are annotated, this is.
Best regards,
Christian
--
kernel
On Tue, 2010-07-20 at 11:21 +0530, chen wrote:
Is it required ? Having it in ECalBackendStore simplifies the backend
code to form the path based on the type (calendar,tasks,memos) at a
single place rather than every backend doing it..
Forming the path at a single place instead of all the
On Tue, 2010-07-20 at 12:20 +0200, Christian Hilberg wrote:
Hi all,
...still continuing...
Kolab makes use of RFC5464 - The IMAP METADATA Extension IMAP folder
annotations to differentiate between the various folder types which are
handled by Kolab. Remember, anything (Email and PIM
On Tue, 2010-07-20 at 12:41 +0200, Milan Crha wrote:
On Tue, 2010-07-20 at 12:20 +0200, Christian Hilberg wrote:
Is it possible to define certain IMAP folders as hidden from within our
plugin's EPlugin part? Or is it possible to hide certain IMAP folders (and
their subfolders) in any
Hi there,
thanks Milan for your reply.
On Tuesday 20 Juli 2010 Milan Crha wrote:
On Tue, 2010-07-20 at 12:20 +0200, Christian Hilberg wrote:
Is it possible to define certain IMAP folders as hidden from within
our plugin's EPlugin part? Or is it possible to hide certain IMAP
folders
On Tue, 2010-07-20 at 06:34 -0400, Matthew Barnes wrote:
On Tue, 2010-07-20 at 11:21 +0530, chen wrote:
Is it required ? Having it in ECalBackendStore simplifies the backend
code to form the path based on the type (calendar,tasks,memos) at a
single place rather than every backend doing it..
On Tue, 2010-07-20 at 11:21 +0530, chen wrote:
On Mon, 2010-07-19 at 17:27 -0400, Matthew Barnes wrote:
Backends using these classes can easily construct a suitable cache file
or directory name from e_cal_backend_get_cache_dir().
get_cache_dir can simply return e_cal_backend_store_get_path.
Hi there,
On Tuesday 20 July 2010 chen wrote:
On Tue, 2010-07-20 at 12:20 +0200, Christian Hilberg wrote:
[...]
Is it possible to define certain IMAP folders as hidden from within
our plugin's EPlugin part? Or is it possible to hide certain IMAP
folders (and their subfolders) in
---BeginMessage---
Migration has been done and I'll submit the patch soon.
Regards
Punit
On Tue, 2010-07-20 at 16:56 +0530, chen wrote:
On Tue, 2010-07-20 at 06:34 -0400, Matthew Barnes wrote:
On Tue, 2010-07-20 at 11:21 +0530, chen wrote:
Is it required ? Having it in ECalBackendStore
On Tue, 2010-07-20 at 13:18 +0200, Christian Hilberg wrote:
Hm. Maybe I'm still missing some parts here on how Evolution
internally works.
Subclassing the Camel Provider in our backends and overloading
get_folder_info() will work for the backend part, i.e. PIM data wich
is accessed and
12 matches
Mail list logo
