[Kolab-devel] universal inbox? outlook outgoing transport

[Bernhard Reiter]

Here an attempt of the summary of what was discussed in irc
about the universal inbox and the related problems.
-------------- next part --------------
Summary of IRC Chat about universal inbox on #kolab.
Participants: Till, Joon, Bernhad
(20041025ber)

The problem on outlook is: 
In order to have an outgoing transport with pop, 
you also need to download everything.

There are two proposed solutions:

	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.)

	b) make a fake pop server that never gives out a mail,
	but mimicks authentification. Then the spool(inbox) part 
	could also be synced with toltec.

	(A local pop3 proxy would be difficult as some anti-virus software
	does dirty things with the pop transport, intercepting the port
	or the transport itself.)
	
In both cases outlook would need to take up the emails from
the mailbox(inbox) or other folders and if they are invitations
mangel them into a mapi/object. 
This would require new iTIP code for outlook.

Not that no matter how we create the mapi/object it can only
affect the default folder. This leads to a second problem:
How to we model the secretary case?
We do want to enable a secretary to accept (and send) notifications
for the folders of the boss. This seem to be impossible with Toltec
and Outlook currently as there is no way to hook into the appointment 
notification handling.

-------------- 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/20041025/a95b4354/attachment.p7s>