aboutsummaryrefslogtreecommitdiffstats
path: root/mail/e-mail-account-manager.h
diff options
context:
space:
mode:
authorMatthew Barnes <mbarnes@redhat.com>2012-07-07 03:34:39 +0800
committerMatthew Barnes <mbarnes@redhat.com>2012-07-07 03:35:41 +0800
commit749b49e5079aaaf171a282f33deb0b12818ba11d (patch)
tree74a5b593eed428cb8b11c9d2da4e228e13c48e61 /mail/e-mail-account-manager.h
parent8eae40f7e895782fae19d289090edbb102b01bfd (diff)
downloadgsoc2013-evolution-749b49e5079aaaf171a282f33deb0b12818ba11d.tar
gsoc2013-evolution-749b49e5079aaaf171a282f33deb0b12818ba11d.tar.gz
gsoc2013-evolution-749b49e5079aaaf171a282f33deb0b12818ba11d.tar.bz2
gsoc2013-evolution-749b49e5079aaaf171a282f33deb0b12818ba11d.tar.lz
gsoc2013-evolution-749b49e5079aaaf171a282f33deb0b12818ba11d.tar.xz
gsoc2013-evolution-749b49e5079aaaf171a282f33deb0b12818ba11d.tar.zst
gsoc2013-evolution-749b49e5079aaaf171a282f33deb0b12818ba11d.zip
Disconnect a CamelService after editing its settings.
This will force Evolution to reconnect to the service using the current settings. However this is not a complete solution. If the new settings now point to a completely different mail account, we leave behind cached messages and database tables from the previous account such that you end up with some weird hybrid of the previous account and current account. I guess for now the answer is "don't do that", but we should try to handle that more gracefully in the future -- more for architectural correctness than it being a common real world use case.
Diffstat (limited to 'mail/e-mail-account-manager.h')
0 files changed, 0 insertions, 0 deletions