CamelStoreClass bumps the settings_type to CAMEL_TYPE_STORE_SETTINGS,
which has a filter-inbox property. But we don't want ANY settings in
a CamelNullStore, so revert the settings_type to CAMEL_TYPE_SETTINGS.
GNOME has included libnotify 0.7.x since GNOME 3.0. It's still an
optional dependency for Evolution, but if you're gonna use it you'll
need a GNOME3-era release.
If the mail account is part of a collection of sources, we want to read
the enabled state from the top-level "collection" source instead of the
mail account source.
Addendum: Same deal in mail_ui_session_source_changed_cb().
If the mail account is part of a collection of sources, we want to
enable or disable the top-level "collection" source instead of the
mail account source.
audio-inline, itip-formatter, prefer-plain, tnef-attachments
and vcard-inline plugins were converted to modules so that they
can fit into concept of the new formatter.
Every module still installs .eplug file, because there is no
suitable API at the moment to register plugins to the plugins dialog
and to extend the Preferences dialog.
All mail-parsing and formatting code has been moved to em-format.
Parsing is handeled by EMailParser class, formatting by EMailFormatter.
Both classes have registry which hold extensions - simple classes
that do actual parsing and formatting. Each supported mime-type
has it's own parser and formatter extension class.
Use e_source_camel_generate_subtype() to register an ESourceCamelNone
class based on the newly-registered "none" CamelProvider.
e_source_camel_register_types() won't pick up the new provider if it was
already called prior to the provider being registered. That might be a
bug... I'm not sure yet. The Camel/ESource integration is kinda messy.
We're using version 1.1 of Mozilla's ClientConfig format now. These
files are all version 1.0. But even aside from that, offline autoconfig
is not compelling enough to warrant maintaining two copies of this data.
This breaks a good chunk of logic out of EMAccountEditor and hopefully
makes it less brittle. Because honestly, every time I fix one thing in
EMAccountEditor it breaks three other things. It's unmaintainable.
Milan Crha