[Kde-pim] Akonadi outbox & dispatcher agent [tentative design]

[Thomas McGuire]

Hi,

On Sunday 03 May 2009 01:11:31 Kevin Krammer wrote:
> On Sunday, 2009-05-03, Constantin Berzan wrote:
> > * The outbox and send-mail folders will be maildirs on the local machine
> > (e.g. in ~/.local/share/mail/{outbox,sent-mail}).  Does it make sense to
> > have two separate resources (outbox and sent-mail), or a single resource
> > managing both these directories?
>
> I would keep them separated.
> Depending on the setup one might not be needed, there could even be setup
> where neither is needed.

I would keep them in once resource, otherwise we have so many processes. We 
can create those folders (and maybe even the resource) on-demand, so that the 
folders are not created when not needed.

> > * Applications can put messages in the outbox collection.  If this is
> > done via Akonadi, then the items will already have a send_with_transport
> > attribute.  If not (e.g. a plain file is created in that maildir), then
> > should the dispatcher ask the user for which transport to use?
>
> Or one "out" directory for each transport

For my own use, I prefer one directory, otherwise the folder tree is too 
cluttered with outboxes. Could be a configure option if someone _really_ 
prefers multiple outboxes.

> > * The dispatcher agent will monitor the outbox collection, and when it
> > finds a new message there it:
> > - passes it to mailtransport (see below)
> > - when/if sending has succeeded, moves the message to the sent-mail
> > collection.  If the message contains a special
> > after_sending_move_to_collection attribute, move it to that collection
> > instead of sent-mail.  (This last bit is useful for things like
> > keep-replies-in- current-dir).
>
> Right, and for sent-mail folders on servers.
>
> > * mailtransport needs a way to find all the resources (like groupware)
> > that can send mail.  Resources could provide dbus methods like
> > canSendMail() and sendMail(msgID), and mailtransport can query each of
> > them and if it canSendMail then put it into the combo box.  When asked to
> > send a message using one of these transports, mailtransport simply calls
> > the appropriate method for the appropriate resource, passing it the ID of
> > the message in the outbox collection.
>
> Hmm.
> How about having a special collection attribute for marking such
> collections?

Don't understand what that is needed for. Mailtransport already knows the id 
of the outbox collection and the id of the messages in it, and only passes the 
item ID to the nntp/groupwise/etc resource, which should be enough for the 
resource to handle the sending.

Regards,
Thomas

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20090503/c881490a/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/