<html dir="ltr"><head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="text-align:left; direction:ltr;"><div>Hello and many thanks for your quick reply.</div><div><br></div><div>After your answers I realized that the connection to my server was interrupted.</div><div><br></div><div>After restarting the server it is working again as before!</div><div><br></div><div>No bug after the update. :-)</div><div><br></div><div>Kind regards</div><div><br></div><div>Christian</div><div><br></div><div>On Thu, 2019-05-16 at 14:46 +0200, Patrick Ohly wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><pre>Roth <</pre><a href="mailto:xy@roth.biz"><pre>xy@roth.biz</pre></a><pre>> writes:</pre><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><pre>Hello,</pre><pre>since two weeks, I guess it is since I've updated syncevolution I</pre><pre>experience problems connecting the server (see logfile).I get a 511</pre><pre>error.</pre><pre>I'm using Debian Testing with syncevolution 1.5.3-2</pre><pre>Any hint is very appreciated.</pre></blockquote><pre><br></pre><pre>The log shows that you connect to Funambol and that the server returns</pre><pre>this 511 error. I've not tested against that server (or any server, to</pre><pre>be honest) in a while, so I can't say whether that is a regression at</pre><pre>their end. It might also be specific to the one item that SyncEvolution</pre><pre>is trying to store on the server.</pre><pre><br></pre><pre>The log itself doesn't show what item that is. You can try to run at a</pre><pre>higher log level and then perhaps temporarily remove that item</pre><pre>locally. If it was because of that item, then the sync might complete.</pre><pre><br></pre><pre>Bye, Patrick</pre><pre><br></pre></blockquote></body></html>