[Evolution] Automatic timezone setting in Exchange
Outlook updates the timezone setting automatically in Exchange. Could Evolution do the same? Lots of Evo users here has the wrong timezone. Jocke ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Automatic timezone setting in Exchange
On Thu, 2015-02-26 at 10:27 +, Joakim Tjernlund wrote: > Outlook updates the timezone setting automatically in Exchange. > Could Evolution do the same? > Lots of Evo users here has the wrong timezone. Not sure I understand what you mean as I don't use Outlook or Exchange and never have. Evo uses the system timezone. Why should it do anything different? Also, you don't say what version of Evo you're talking about. poc ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] [ews] 'Listen for server change notifications' stops working
Hi, On Fri, Feb 20, 2015 at 9:29 AM, Milan Crha wrote: > On Thu, 2015-02-19 at 15:19 +0200, Robert Munteanu wrote: >> >> I can try EWS_DEBUG=1 for instance, but that will dump everything >> and I'd like to avoid that ; it's much easier to spot problems when >> reading debug output just for my issue. > > Hi, > it's EWS_DEBUG=2, which gives you everything EWS related in detail. Does that do anything more than log all requests and responses? I've routed Evolution throw a HTTPS proxy and I capture the traffic there. Also, what request/response types should I look for when debugging the 'listen for change notifications' issue? > The thing is that your problem is EWS related, and the EWS_DEBUG=2 is > the only way how to debug what the evolution-ews does. There is no > more fine-grained debugging for evolution-ews than this. It's about > looking into the log and try to find out why the notification thread > stopped, or just got disconnected, or basically what happened. I see some strange occurrences during normal operation, not 100% sure if they're related, but ... Most of the HTTP calls succeed ( 200 OK ) but from time to time I see groups of 3 request failing with status 401. The calls which work fine have Basic Auth with username and password set. The calls which fail either have NTLM authentication set or basic auth without a password. All failing calls were 'GetFolder' invocations for inbox. And they're always in groups of three, in the same order: NTML, Basic Auth without password, NTLM. The value of the Authorization: NTLM ... header is always the same. The basic auth calls also have a 'ClientId=...' cookie, which seems to change after a successful re-authentication. Thanks, Robert ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
[Evolution] Cannot delete CalDAV calendars
Hoping to get some help cleaning up my Evolution installation (3.12.11 under Fedora 21 / GNOME 3.14). I manually modified a password in GNOME keyring, and thereafter Evolution has been unable to open the ownCloud calendars associated with that password. I am informed of this every time I start Evolution: Error loading calendar 'Default calendar (owncloudu...@www.owncloudserver.tld/ownCloud)' Unable to connect to 'Default calendar': Cannot open calendar: Error parsing result obtained from the keyring: 0-1:unknown keyword I worked around this by recreating the calendars. They now appear under the collapsible "CalDAV" heading and appear to work, but I'm unable to delete the old instances, which appear under a different heading in the Evolution calendars list. This heading is in the form: owncloudu...@www.owncloudserver.tld/ownCloud Right-clicking on these calendar accounts presents no "Delete" option. How can I get rid of them? Thanks! ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Cannot delete CalDAV calendars
> > I worked around this by recreating the calendars. They now appear under > the collapsible "CalDAV" heading and appear to work, but I'm unable to > delete the old instances, which appear under a different heading in the > Evolution calendars list. This heading is in the form: > > owncloudu...@www.owncloudserver.tld/ownCloud > > Right-clicking on these calendar accounts presents no "Delete" option. > > How can I get rid of them? > They are from the Gnome Online Accounts thing. In the Gnome Shell (i.e. not Evolution) go into Settings -> Online Accounts. You can either delete your ownCloud account or just turn off the Calendar function. P. ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Cannot delete CalDAV calendars
Thanks, that did it. I deleted the new CalDAV calendars and fixed the authentication in Online Accounts for the old calendars. On Thu, 2015-02-26 at 17:52 +, Pete Biggs wrote: > > > > I worked around this by recreating the calendars. They now appear under > > the collapsible "CalDAV" heading and appear to work, but I'm unable to > > delete the old instances, which appear under a different heading in the > > Evolution calendars list. This heading is in the form: > > > > owncloudu...@www.owncloudserver.tld/ownCloud > > > > Right-clicking on these calendar accounts presents no "Delete" option. > > > > How can I get rid of them? > > > > They are from the Gnome Online Accounts thing. In the Gnome Shell (i.e. > not Evolution) go into Settings -> Online Accounts. You can either > delete your ownCloud account or just turn off the Calendar function. > > P. > > ___ > evolution-list mailing list > evolution-list@gnome.org > To change your list options or unsubscribe, visit ... > https://mail.gnome.org/mailman/listinfo/evolution-list ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] [ews] 'Listen for server change notifications' stops working
On Thu, 2015-02-26 at 16:03 +0200, Robert Munteanu wrote: > Hi, > > On Fri, Feb 20, 2015 at 9:29 AM, Milan Crha wrote: > > On Thu, 2015-02-19 at 15:19 +0200, Robert Munteanu wrote: > > > > > > I can try EWS_DEBUG=1 for instance, but that will dump > > > everything and I'd like to avoid that ; it's much easier to spot > > > problems when reading debug output just for my issue. > > > > Hi, > > it's EWS_DEBUG=2, which gives you everything EWS related in detail. > > Does that do anything more than log all requests and responses? I've > routed Evolution throw a HTTPS proxy and I capture the traffic > there. Also, what request/response types should I look for when > debugging the 'listen for change notifications' issue? Hi, it doesn't, though it let's any user to look on the log without setting proxy or anything like that, in a "well known" format, instead of packet capture or anything similar. Nonetheless, whatever works the best for you. The notifications are using streaming, that means, evolution-ews runs a thread called e_ews_notification_get_events_thread() and that is just waiting for response from the server, with occasional "reconnect", because the connection can timeout during the time. If this thread is not in your evolution, then you won't get any notifications. The reason can be also that the server doesn't report new-enough version, but I guess that's not your case. The notification listening is started with GetStreamingEvents "call" to the server. > Most of the HTTP calls succeed ( 200 OK ) but from time to time I > see groups of 3 request failing with status 401. The calls which > work fine have Basic Auth with username and password set. The calls > which fail either have NTLM authentication set or basic auth without > a password. I'd say it's normal, just the way libsoup works. It tries to get some page, the server returns "no, authentication needed" (libsoup doesn't have many options to realize that without trying first). Then it asks evolution-ews for a password and if given, then it is tried. How it works with respect of changing authentication methods (Basic versus NTLM) I'm not that sure. It may also depend on your libsoup version, there had been dropped an automatic downgrade from NTLM to Basic in some not so distant past version. But it's possible that it is not related to what you see at all. Bye, Milan ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
