On 19/10/14 20:04, Patrick Ohly wrote:
On Sat, 2014-10-18 at 15:36 +0100, Graham Cobb wrote:
> The (new in this release, I think) checking for mixing shared/unshared
> properties is causing me some logical confusion.
That's the expected behavior, and hasn't changed in the
candidate. The new terminology did not change the implementation, just
Ah, OK. I thought you had tightened some checks to reduce user errors
by disallowing some combinations that had previously been accepted but
might not have had the effect the user expected. I was probably
confused (I had been hacking my scripts along with the earlier
discussions around naming).
In this case the problem is that "@Exchange" refers to a context, not a
sync config, and only sync configs have a username property. You could
use "databaseUsername" instead (however, I am not 100% sure whether the
ActiveSync backend supports that - WebDAV does), if you don't mind
repeating that for each source, ahem, datastore.
I now have a recollection that I had raised something similar to this
question before. I think the answer then was also "if you are more
comfortable, use databaseUsername". I will look into whether activesync
It would be nice, one day, to make configuration of Exchange, Google and
Owncloud servers look, as far as possible, the same. They all need
similar information (server contact details, auth info and folder names)
but the configuration for activesync is done very differently.
> The only way I can get it to work is if I bring step 3 to be in
> step 2. That works, but feels wrong (it also breaks my scripts in a
> hard to fix way, but that is my problem).
Are you sure it used to work?
No. I was probably confused about that. The easiest fix to my scripts
seems to actually be to just configure the target-context before the
Thanks for the help.