On Thu, 20 Jan 2022, Patrick Ohly wrote:
Max Pyziur <p...@brama.com> writes:
#####################
these seem to be the relevant lines from the logfile:
–
[2022-01-19 17:03:24.293] 'processStatus' - Processing incoming Status
[--][++] [->end] [->enclosing]
[2022-01-19 17:03:24.293] Started processing Command 'Status'
(incoming MsgID=4, CmdID=5)
[2022-01-19 17:03:24.293] WARNING: RECEIVED NON-OK STATUS 400 for
command 'Add' (outgoing MsgID=4, CmdID=5)
[2022-01-19 17:03:24.293] - SourceRef (localID) =
'pas-id-0bb48ef3ca252ea80c8d07fd720d9818b357a2e6'
[2022-01-19 17:03:24.293] Found matching command 'Add' for Status
[2022-01-19 17:03:24.293] Status: 400: originator exception
As you seem to have KeepContact's attention, perhaps share this log file
with them? Further up there's the message that was sent to the
server. If you ran with a high enough log level, it will contain your
data - this is good for debugging, but beware of your privacy.
Yes, I shared it.
And I understand the concerns about privacy.
M
My guess is that SyncEvolution sends data that the server doesn't like,
but that's speculation. KeepContacts should know what this 400 status
means.
_______________________________________________
SyncEvolution mailing list -- syncevolution@syncevolution.org
To unsubscribe send an email to syncevolution-le...@syncevolution.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
