Thanks for the quick response (and accepting the patch too). The client is going to be SOGo (http://www.sogo.nu/) which I'm using to do shared calendar and, for mobile devices, email too.
Everything was nice and clean until I started adding the mobile device which is using ActiveSync. Not my preferred approach but it seemed quick way to test things. I suspect either SOGo does some bad behaviour itself or it is passing along bad behaviour from the ActiveSync device (which is a fairly old Android device). A quick grep round the code for that has a smoking gun : ~/SOGo-2.2.6# grep -ri annota * SoObjects/Mailer/SOGoMailAccount.m: result = [client annotation: @"*" entryName: @"/comment" attributeName: @"value.priv"]; SoObjects/Mailer/SOGoMailAccount.m: nresult = [client annotation: [object substringFromIndex: 1] entryName: @"/comment" attributeName: @"value.priv" attributeValue: guid]; I'll need to flag this on the SOGo list I guess; just so I'm clear, how is this different from annotate (which is supported) ? What would be involved in adding support ? (i.e. best left to the professionals or could something be used as a starting point to get this going?) Meantime, I suspect ActiveSync is for the trash can. Thanks Jim On 03/07/2014 17:51, Abhijit Menon-Sen wrote: > At 2014-07-03 17:19:36 +0100, [email protected] wrote: >> I made a small change and rebuilt and that seemed to resolve the issue >> (it was logged frequently before and stopped right away after putting >> this change live) : > Thanks for your patch. I've applied it. > >> Jul 3 16:17:18 messaging Archiveopteryx: 29924/2/13 Unknown command. >> Line: "22 getannotation \"*\" \"/comment\" \"value.priv\"" > Souds like you're using a client that uses the ANNOTATEMORE extension > against a server that doesn't advertise support for it. That seems > rather poor behaviour. What client is it? > > I'm not sure what to do about it, though. > > -- ams
