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

[Tom Albers]

Hi,

> * 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?

Single resource, two folders imho.

> * 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?

Could be usefull for third party application. Just dump it in there and it will be taken care of. With the transpart combo it is easy to implement too I guess.

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

I would like to see some more info about how that works on the mailtransport side. It somehow needs to remember that it should pass it back to the resource, so it needs to store that somehow.

> * A LocalFolders class takes care of creating the outbox and sent-mail 
> collections for the first time, and can be used later to access these 
> collections.  It will also have an Inbox folder for POP3, but that is 
> unrelated to this project.  The class will reside in kdepimlibs/akonadi/kmime 
> unless someone suggests a better location (perhaps in kdepim/akonadi/resources 
> somewhere?)

Yes, it has nothing to do with kmime and it is a resource so the kdepim/akonadi/resources makes a lot more sense to me. 

I don't think the inbox needs to be in this specialised resource, the power of akonadi is that it seperates all this functionality, let's not polute it. Mailody does not need an Inbox there. I would vote for a separate pop3 resource which might link in the items from the outbox or sent-items if the application uses that.

Hope this helps.

Best.

Toma
-- 
KDE Developer
-------------- 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/