Bug #720943 - vFolder does not refresh automatically
Update Chinese simplified translation
[Esource] Do not set properties on load which did not change

When calling g_object_set(), g_object_set_property() and similar
set functions, the GObject itself notifies about the property change,
even if the value didn't change at all. This was exhibited by false
notifications when (re)loading ESource on a change on all its saved
properties, which, in particular, was causing bug #722399.
imapx_write_flags: Fix a typo which flag to skip

The code was surely trying to avoid writing CAMEL_IMAPX_MESSAGE_RECENT
flag back to the server, but the actual behaviour was that each flag
had been ignored, if the CAMEL_IMAPX_MESSAGE_RECENT was set.
This could have an effect of copied read message being marked as unread
in the destination IMAPx folder.
camel_flag_list_copy: Avoid false 'changed' notifications

The function, as written, returned that the destination list
changed even in cases where both flag lists were empty. This
made for example IMAPx report that each message in a folder
hanged, even there did not change any.
Bug #721286 - IMAPx: read messages become unread when reopening Evolution

Couple things changed here:

a) the camel_folder_summary_get_changed() could return list of changed
   messages only if they were loaded in memory, which is not correct - I
   think it's part of the issue why it failed

b) it could happen that imapx_server_sync_changes() was called to save some
   changes, but then didn't change anything; in such cases, messages marked
   as locally changed were never unmarked, which led to false tests; I added
   a function to unmark the messages as locally changed (this can cause slow
   close of evolution for the first time, due to unsetting of the flag, but
   later ends are fine)

c) state of the message flags on the server is the master state, except of
   the state where locally stored info is marked as locally changed. This
   allows to show proper state of messages on the server (it is influenced
   by a) and b) too, so it might take up to two evolution starts to get
   the same view in evolution as is the state on the server).
Bug #721286 - IMAPx: read messages become unread when reopening Evolution ][

Found one more issue when testing the same change for gnome-3-10:

d) do not use CamelOperation in the parser thread, because it can be
   cancelled at an application end with camel_operation_cancel_all() call,
   which is done too early, before any pending jobs are properly finished
   (it can be IDLE job, or save of folder changes back to the server)