Not used by Evolution and not clear what this mode even means.

Removing it makes a bunch of confusing complexity drop out, which is
justication enough for me.

Was tied to "mobile mode", no longer used.

Not used by Evolution and not clear what this mode even means.

Removing it makes a bunch of confusing complexity drop out, which is
justification enough for me.

The method is not used by Evolution and was partially broken anyway.
The boolean return value was overloaded to mean both whether an error
occurred AND whether there were more messages to fetch.  That's more
than two possible states and would have required an additional "out"
parameter to clarify, but I'm not going to bother with it.

This replaces the interactive "alert_user()" method since the
interactive aspect is no longer used and proved difficult for
applications to handle correctly.

New functions:

  camel_session_user_alert()

Removed functions:

  camel_session_alert_user()

Evolution uses it but Camel doesn't.  Move it to Evolution.

Just wrappers g_network_monitor_can_reach() using the service's own
GSocketConnectable, but also updates the "host-reachable" property.
External callers can use this to synchronously update the property,
in case they need an up-to-date result to make a decision.

Also adds equivalent asynchronous functions:

  camel_network_service_can_reach()
  camel_network_service_can_reach_finish()

- Remove trailing tabs.
- Add terminators to multi-line lists.