On 2019-01-04T17:37:26-0700, Oswald Buddenhagen <oswald.buddenha...@gmx.de> wrote: > yes, it clearly gets upset when uploading the first message, which > has a whopping 9.3 megs, which you presumably don't have in the other > clones.
> the default timeout of 20 secs is a bit tight, so you may just > increase it, and at some point it will work. > the underlying issue is that mbsync resets the timeout only when it > receives data from the server, which it doesn't do while it uploads > lots of stuff to the server over a connection that isn't blazingly > fast. > a way to get around that would be relying on the kernel's knowledge > of TCP ACK packets during the upload, which can be apparently > achieved with setsockopt(fd, SOL_TCP, TCP_USER_TIMEOUT, &timeout_ms, > sizeof(timeout_ms)) in as far the option is available. Yes, changing the timeout seems to fix it. Thanks! I was thinking it was timing out on the gmail side. It's odd, because that machine has a hardline connection to fast internet, and I've certainly pushed around messages larger than 9.3 megs on all of my machines before. -- Benjamin Slade - https://babbagefiles.xyz `(pgp_fp: ,(21BA 2AE1 28F6 DF36 110A 0E9C A320 BBE8 2B52 EE19)) '(sent by mu4e on Emacs running under GNU/Linux . https://gnu.org ) `(Choose Linux ,(Choose Freedom) . https://linux.com ) _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
