Re: [Evolution] suggestion: mail fetch daemon

[Ruchir Brahmbhatt <ruchir brahmbhatt ecosmob com>]

I think this is good idea. Downloading mails in background with enhanced mechanism will make it faster also. I think kmail and thunderbird are already doing it. I already filed a bug long ago regarding evolution performance. 
http://bugzilla.gnome.org/show_bug.cgi?id=541487

Thanks,
Ruchir

-----Original Message-----
Date: Fri, 06 Mar 2009 17:26:42 +0100
From: Andr? Wyrwa <a wyrwa gmx de>
Subject: [Evolution] suggestion: mail fetch daemon
To: evolution-list gnome org
Message-ID: <1236356802 18679 9 camel localhost>
Content-Type: text/plain; charset="us-ascii"

Hei,

how about implementing an independent mail fetch daemon or an option to
start evolution in such a mode? How about combining that with a
notification applet?

Currently, there are basically two notification
applets...mail-notification and evolutions plugin.

The former is able to check all kinds of accounts.
The latter only notifies me when evolution itself is already running.

The problem is that using the former duplicates both configuration
efforts and at least mail header fetching.

The second requires me to have my full blown evolution started already.
Meaning to have an automated notification constantly running, i'd have
to start evolution on every system startup.

Why not create a userspace daemon / applet that uses evolutions mailbox
configurations to actually periodically fetch my mail and store it in
evolution-data-server? Notify me that new email has been fetched if the
case.

From a technical view, wouldn't that just mean separating the mail
fetching core out of the evo app into a separate app and then creating a
simple dbus interface to enable evolution to tell that app what to do?

With probably a little more effort this concept should be extendable to
syncing remote calendars and so on.

Are there any efforts like that underway?
If not...is it a bad idea or did just no-one have the time to start it,
yet?

Thanks,
Andre.