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

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/13650
------------------------------------------------------------------------------
  Ticket             | 13650
  Updated By         | software-horde at interfasys.ch
  Summary            | iOS device can't find recipient certificate
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


software-horde at interfasys.ch (2014-10-27 16:32) wrote:

> 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 at 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.