[Kolab-devel] universal inbox? outlook outgoing transport

[Bernhard Reiter]

On Monday 01 November 2004 08:53, Steffen Hansen wrote:
> On Tuesday 26 October 2004 18:01, Bernhard Herzog wrote:
> > Bernhard Reiter <bernhard at intevation.de> writes:
> > > 	a) sieve to on the server to transport spool(inbox) to
> > > mailbox(inbox) then there is nothing to download via pop
> > > 	(a.1 if done it would need to be one sieve script, affecting
> > > 	all other sieve scripts that Kolab webadmin and KDE client can
> > > handle.) (a.2 imap move cannot do a move like spool(inbox) ->
> > > mailbox(inbox) so it is not an option.)
> >
> > Another variant of this (from Bernhard Reiter via Phone): Instead of
> > using sieve, extend the resource handler to put all normal mail into
> > the mailbox.  This would avoid potential problems with clients
> > manipulating the sieve scripts for other purposes such as vacation
> > mails.
>
> I don't think that'll work. The resource handler script is a postfix
> content filter and knows nothing about IMAP -- unless I let it act as
> an IMAP client that stores messages in some folder for the user. This
> means that the mail is not delivered to Cyrus over the normal channel
> (LMTP), so
>
> 1) The content filter needs write access to the user's folder(s)
> 2) Sieve scripts for incoming mail will not be run
> 3) Flags will probably look funny.

Okay, what is the solution you propose?
There must be a way to make a script configurable
that transports email from spool to the default "inbox" imap folder.
-------------- 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/devel/attachments/20041101/c8850ae4/attachment.p7s>