Tickets :: Comment on [#13650] iOS device can't find recipient certificate

* Your Email Address
* Spam protection	Enter the letters below: .__ \ /. ,.__..___ \| \ >< \./ \| \|[__ \|__// \ \| \|__\|[___
Comment	>> This works for me without any issue. Does the Horde log show the >> expected turba queries for the user you are looking up? > > I dug deeper and here is what I found. > > I have 2 sources in Turba. > > The connector returns 2 sources, however one of them is empty. That's > what is used for the query and there is no public cert, so that part > of the behaviour is correct. > > I've checked the turba tables and there are 3 sources (owner_id) in > turba_objects. > The 2 first ones (seens by the connector) have a randomised name, but > the 3rd one is named user@domain.tld. > That source does not exist in turba_sharesng > That source is the main one being used by turba and that's where the > cert has been saved. > > It could be that something is broken here, but how come Turba is > using something which does not exist in sharesng as its main source? > > It's been partially filled with some data from a phone, so it must > have been syncing at some point as well. >
Attachment
Watch this ticket