[Evolution] Calendar update

[Hans-Christoph Paul]

SUSE 12.3, Gnome, Evolution 3.22.6

I use Evolution as my main mail, professional. I rely on it why failures are 
difficult - critical.
I use 3 calendars parallel in Evolution towards Exchange.


Systems:
- windows Exchange in different version
- web Exchange
- iPhone
- SUSE SLED
- SUSE SLES


A) company mail Vestas: Exchange server 365.
Syncronize fine on all systems

- windows Outlook in different version
- web Exchange
- iPhone
- SUSE SLED
- SUSE SLES


B) private mail on provider mail Exchange 2010
do not syncronize on all sytems

- windows Exchange in different version - fine
- web Exchange - fine
- iPhone - fine
- SUSE SLED - no
- SUSE SLES - no

I can make an appointment in SLED and it will be visible in
- iPhone
- webexchange
- windows outlook
- not in SLES

In general, it does not syncronise towards evolution from Exchange 2010.
The problem came up when changing from SLED / SLES 12.2 to 12.3.


--

Med venlig hilsen / mit freundlichen Grüssen / best regards
HCP innovation
Hans-Christoph Paul
T: +45 22171410
h...@hcpi.dk
___
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] open

[Gottfried]

Hi all,

one last time. I did not believe it, but I tried now several times and 
it was only confirmed. Once the password is saved in keyrings, evolution 
works smart.


Thank you for all the work you put into this. I look at this thread now 
from my side as closed.


Have a blessed 2018


On 03/01/18 14:02, Milan Crha wrote:

On Wed, 2018-01-03 at 12:43 +0100, Ralf Mardorf wrote:

so an equivalent to

   evolution --force-shutdown

while sidestepping usage of "evolution" would be

Hi,
depending where you distribution installs it:

$ /usr/libexec/evolution/killev

which is what the 'evolution --force-shutdown` more or less does.

But I do not think it's a good idea to make things overcomplicated when
you've tools which are provided by the application, thus which are
supposed to do things right (and if they do not, then it's a bug and
should be fixed).

On Wed, 2018-01-03 at 12:51 +0100, Ralf Mardorf wrote:

No output by running "pgrep -a evolution" means that everything is
terminated, IOW "evolution --force-shutdown" did shutdown everything.

That's not accurate. Consider a situation when the GNOME managed to
restart the background processes between the two commands.

Nonetheless, we are far from the original issue. Let's stop discussing
details which are not needed to be learned by the regular users.
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



___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list