Re: [Evolution] [ews] Listen for server change notifications vs check for new messages
- From: Robert Munteanu <robert munteanu gmail com>
- To: Fabiano Fidêncio <fabiano fidencio org>
- Cc: evolution-list gnome org
- Subject: Re: [Evolution] [ews] Listen for server change notifications vs check for new messages
- Date: Mon, 26 May 2014 10:26:22 +0300
On Thu, May 15, 2014 at 11:08 AM, Robert Munteanu
<robert munteanu gmail com> wrote:
On Wed, May 14, 2014 at 6:16 PM, Fabiano Fidêncio <fabiano fidencio org> wrote:
Hello Robert,
On Wed, May 14, 2014 at 2:57 PM, Robert Munteanu <robert munteanu gmail com>
wrote:
Hi,
I see that with evolution-ews 3.12.1 I can configure my EWS account to
listen to server change notifications, which is pretty cool. I enabled
that and still see that all my folders are periodically refreshed.
Listen for server change notification and Check for new messages every X
minutes are options that can be enabled simultaneously, although doesn't
make sense to. :-) So, it's up to you to disable or not the "Check for new
messages every X minutes".
Just keep in mind one thing, "Listen for server change notifications" only
works for Exchange Servers newer than 2010 SP2. So, if you're connected to
an older server, it will not work.
Right, got it. I think the version is new enough, I'm using
outlook.com hosting ( outlook.office365.com ) . Can I validate somehow
that this is enough?
Are there any caveats when doing that? I have server-side filters
enabled so messages typically arrive in any of 50+ folders.
Not that I can remember.
One thing that is not clear from your email is if you have the notifications
working for you or not.
Considering it's not working, please, could you start your evolution using:
EWS_DEBUG=2 evolution &> ews_log.txt
Then, please, remove any personal information from the file and send to the
list.
I'll do that, thanks. However, it's a bit hard right now to get valid
information due to
730134: Segmentation fault: camel-ews-store.c: No such file or directory
https://bugzilla.gnome.org/show_bug.cgi?id=730134
so expect some delays.
So after the update to 3.12.2 the referenced bug is fixed, so that's nice.
I see that updates are working, but with a minor caveat: it seems that
whenever evolution is started it listens for updates, but it does not
sync the current state from the server. So updates will work only for
messages which arrive after I've opened evolution, which makes me
think that we still need a full sync somehow.
Doing a manual send/receive fixes this.
My settings are
[ ] Check for messages every X minutes
[x] Check for new messages in all folders
[x] Listen for server change notifications
Thanks,
Robert
Robert
Best Regards,
--
Fabiano Fidêncio
--
http://robert.muntea.nu/
--
http://robert.muntea.nu/
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]