On Mon, 2017-03-20 at 10:54 +0000, Pete Biggs wrote:
> What sort of distracted me was that calendar notifications/alarms don't
> need Evo to be running.
Hi,
that's evolution-alarm-notify, which is automatically started after
login (by default) and when you run evolution itself, it also makes
sure that this background service is running. It runs other parts of
evolution-data-server as a consequence, namely evolution-source-
registry and evolution-calendar-factory, eventually also evolution-
addressbook-factory, it depends. These evolution-data-server services
are there for cooperation for any "clients" of the address book and
calendar sources ('calendar' here means also tasks and memos).
The GNOME Shell itself runs evolution-calendar-factory to know about
events in the clock "applet" (it's not called 'applet' these days).
Once upon a time, there was an idea to provide the third factory, for
mail. The plan was to have it running in the background, just like the
calendar and address book factories, with provided D-Bus interface and
any "client" would connect to it and show accounts, folders and mails
provided by it. Then a similar evolution-mail-notify (similar to
evolution-alarm-notify) service could be running in the background and
notify about new mails without evolution itself being running. It has
its pros and cons, as it uses to be.
Srini begun the work on it some time ago, but the project is currently
frozen, as far as I know.
Anyway, the current situation is that if you want to receive
notification from evolution, then evolution itself should be left
running in the background. Once the evolution is closed, the new mail
notifications (provided by it) are not working.
Bye,
Milan
_______________________________________________
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
