On Mon, 2020-05-25 at 16:12 +0200, Milan Crha via evolution-list wrote:
> On Mon, 2020-05-25 at 15:01 +0100, Pete Biggs wrote:
> > Do you think that not being able to subscribe to non-GAL accounts
> > would be considered a bug?
>
> Hi,
> I do not recall why I made there the need to have the
On Mon, 2020-05-25 at 15:01 +0100, Pete Biggs wrote:
> Do you think that not being able to subscribe to non-GAL accounts
> would be considered a bug?
Hi,
I do not recall why I made there the need to have the contact known in
GAL. If it's not a requirement on the server side (anymore?),
On Mon, 2020-05-25 at 15:17 +0200, Milan Crha via evolution-list wrote:
> On Mon, 2020-05-25 at 13:58 +0100, Pete Biggs wrote:
> > Can I just copy that file to my home machine?
>
> Hi,
> yes, but make sure the Parent=. at the top will match the Parent
> from the other .source files in
On Mon, 2020-05-25 at 13:58 +0100, Pete Biggs wrote:
> Can I just copy that file to my home machine?
Hi,
yes, but make sure the Parent=. at the top will match the Parent
from the other .source files in that "destination" directory. That's
how it knows to which account it belongs.
>
On Mon, 2020-05-25 at 11:30 +0200, Milan Crha via evolution-list wrote:
> On Fri, 2020-05-22 at 12:10 +0100, Pete Biggs wrote:
> > Does the subscription process check for the user in the GAL before
> > subscribing? Can I tell it not to?
>
> Hi,
> evolution-ews searches for the contact, to
On Fri, 2020-05-22 at 12:10 +0100, Pete Biggs wrote:
> Does the subscription process check for the user in the GAL before
> subscribing? Can I tell it not to?
Hi,
evolution-ews searches for the contact, to verify it exists. The only
way to not let it do it is to pick the user from the
Evolution 3.36.2 - EWS/Office365 account
I've recently had to configure my home copy of Evolution to talk to our
Office365 tenancy (for obvious reasons!). It was not pain free, but I
don't think it was totally an issue with Evolution. The only thing
left is to connect to a shared calendar, but
