[Kolab-devel] universal inbox? outlook outgoing transport

[Bernhard Reiter]

On Tuesday 02 November 2004 22:50, Steffen Hansen wrote:
> On Tuesday 02 November 2004 13:00, Bernhard Reiter wrote:
> > > We cannot traverse mime parts directly in Sieve (not implemented in
> > > Cyrus it seems), but we can add a mime_header_check to postfix that
> > > adds a header if the message contains a text/calendar part:
> > >
> > > /^content-type:\s+text\/calendar/ PREPEND X-Kolab-Schedulemsg: TRUE
> >
> > So you do that with the resources management script?
> > Maybe even the other way around: Like mark the ones that should be
> > moved which would make that movement configurable?
>
> I was just thinking using the postfix built in mime_header_checks, but
> that might not be capable of adding a header to the mail (matches
> inside the contents can't add headers). So we'll have to use a
> content-filter to mark the mail with a header.

Yes, again: Can't we use the resources script
and then use another setting to make this marking configurable?

> > > and then we can check for that header in Sieve. If we send the
> > > text/calendar in the body of the mail, we can just do a header
> > > check right away with Sieve:
> > >
> > > if( header :contains "Content-Type" "text/calendar" ) {
> > > 	keep; # Keep in INBOX
> > > 	stop;
> > > }
> > > fileinto "INBOX/Inbox"; # Copy everything else
> >
> > How hard is it to get this integrated with the vacation and
> > forwarding sieve we do? BTW: I have openend issue506 for this, so
> > when we have a conclusion we can register it their and then you can
> > implement it.
>
> Quite doable. Both the vacation script and the forward script should
> just have the above Sieve snippet appended (for the forward script only
> in the case where it's set up to leave a copy on the server).

Okay, can you start doing it. ;)
-------------- 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/20041103/fdf43928/attachment.p7s>