itted)
> >=== (100000 bytes omitted)
> >Socket error: receive buffer full. Probably protocol error.
> >
> are you _sure_ you're running the actual 1.5.0 release?
> i know from the excessively large log that didn't make it to the list
> that you are _not_ runn
On Wed, Nov 06, 2024 at 06:50:39PM +0100, Henrik Frisk wrote:
* 126 FETCH (UID 37160 BODY[] {2012973}
=== (10 bytes omitted)
=== (10 bytes omitted)
=== (10 bytes omitted)
Socket error: receive buffer full. Probably protocol error.
are you _sure_ you're running the actual
nt and mbsync. One of the
> >> accounts work fine, the other not.
> >>
> >> The error I am now getting is this:
> >>
> >> Socket error: receive buffer full. Probably protocol error.
> >
> tracking such errors requires the -Dn log. only the end of it, starti
l.com/#msg58755349
I'm using Davmail to connect to a OAuth2 account and mbsync. One of the
accounts work fine, the other not.
The error I am now getting is this:
Socket error: receive buffer full. Probably protocol error.
tracking such errors requires the -Dn log. only the end of it, startin
2024. nov. 2. 11:11:53 Henrik Frisk :
hi,
I decided to give this a try again (see my message from April 1).
I'm using Davmail to connect to a OAuth2 account and mbsync. One of the
accounts work fine, the other not.
The error I am now getting is this:
Socket error: receive buffer
hi,
I decided to give this a try again (see my message from April 1).
I'm using Davmail to connect to a OAuth2 account and mbsync. One of the
accounts work fine, the other not.
The error I am now getting is this:
Socket error: receive buffer full. Probably protocol error.
thanks for any
On Wed, Jul 31, 2024 at 07:20:38PM +0200, Oswald Buddenhagen wrote:
> so, after not even two years after i received the logs (:'-D), i finally
> analyzed them. posting for posterity.
Thanks for following this up!
For what it's worth, I haven't seen these problems again since our original
exchange
log in private.
so, after not even two years after i received the logs (:'-D), i finally
analyzed them. posting for posterity.
Socket error on imap.gmail.com (142.251.5.109:993): timeout.
for unclear reasons, mbsync was pushing out the entire 25 meg message
within a second, while of cour
On Mon, Jun 10, 2024 at 09:45:37AM +0200, Henrik Frisk wrote:
So sorry this dragged out.
well, _i_ am in no hurry ...
I would be so happy if you have the time to take
a look at these files attached which are the logs from mbsync and
DavMail.
somewhat guessing here, but this seems to be a ge
On Thu, May 16, 2024 at 12:18:36PM +0200, Henrik Frisk wrote:
Despite my best efforts, trying the things suggested here and a bunch
of
other stuff to do with the configuration of davmail and mbsync I can't get
this to work. I guess my main question to this list is if this is a davmail
problem or
may not help you though ...
>>
>> Thanks! I will try and see if it helps!
>
Despite my best efforts, trying the things suggested here and a bunch of
other stuff to do with the configuration of davmail and mbsync I can't get
this to work. I guess my main question to this list is if thi
Den mån 15 apr. 2024 kl 12:19 skrev Bence Ferdinandy :
>
> On Sun Apr 14, 2024 at 12:08, Henrik Frisk wrote:
> >
> > Hi, posted this a couple of weeks abo and received a sugesstion from
> Bence
> > to remove the PassCmd which I replaced with Pass "". This didn't resolve
> > the issue however, th
On Sun Apr 14, 2024 at 12:08, Henrik Frisk wrote:
>
> Hi, posted this a couple of weeks abo and received a sugesstion from Bence
> to remove the PassCmd which I replaced with Pass "". This didn't resolve
> the issue however, that I get socket errors. The basic connection through
> Davmail works
works fine but I can'
> > seem
> > to get mbsynch to want to sync:
> >
> > This is the error I'm getting:
> >
> > Socket error on 127.0.0.1 (127.0.0.1:1143): timeout.
> > Processed 1 box(es) in 1 channel(s),
> > pulled 0 new message(s) and
Den mån 1 apr. 2024 kl 18:54 skrev Henrik Frisk :
> Hi,
>
> I just changed my setup using davmail for syncing and sending my work
> email which just changed to 2F authentication. Sending works fine but I
> can' seem to get mbsynch to want to sync:
>
> This is the err
Hey,
2024. ápr. 1. 18:55:44 Henrik Frisk :
Hi,
I just changed my setup using davmail for syncing and sending my work
email
which just changed to 2F authentication. Sending works fine but I can'
seem
to get mbsynch to want to sync:
This is the error I'm getting:
Socket error on
Hi,
I just changed my setup using davmail for syncing and sending my work email
which just changed to 2F authentication. Sending works fine but I can' seem
to get mbsynch to want to sync:
This is the error I'm getting:
Socket error on 127.0.0.1 (127.0.0.1:1143): timeout.
Processed 1
Result of bisect:
859b7dd7f2dc5d8396488700e0ab35d207188ed9 is the first bad commit
commit 859b7dd7f2dc5d8396488700e0ab35d207188ed9
Author: Oswald Buddenhagen
Date: Thu Jun 9 13:32:16 2022 +0200
try to avoid extra syscalls when reading sockets
so far we shifted down the buffered data o
On Wed Jan 10, 2024 at 12:22, Oswald Buddenhagen via isync-devel
wrote:
> this doesn't look like a data incompatibility, so clearing won't do
> anything useful.
> try running with -D to see whether it's doing something obviously
> stupid. the next level would be strace'ing it.
> anyway, my firs
On Wed, Jan 10, 2024 at 09:59:07AM +0100, Bence Ferdinandy wrote:
On Thu Aug 17, 2023 at 14:45, Oswald Buddenhagen
wrote:
On Thu, Aug 17, 2023 at 07:59:09AM -0400, brittanderson--- via isync-devel
wrote:
>The error has reoccured. It is:
>
>Socket error: receive buffer full. Probably
Hi all,
On Thu Aug 17, 2023 at 14:45, Oswald Buddenhagen
wrote:
> On Thu, Aug 17, 2023 at 07:59:09AM -0400, brittanderson--- via isync-devel
> wrote:
> >The error has reoccured. It is:
> >
> >Socket error: receive buffer full. Probably protocol error.
I also ran into
On Fri, Aug 18, 2023 at 08:37:52AM -0400, brittanderson--- via isync-devel
wrote:
Thank you for the follow-up. I just had another message that provoked
this error. This one from protonmail, so it is not a microsoft exchange
specific issues, and I do not use davmail for the protonmail account.
related to the error?
Regards,
Oswald Buddenhagen writes:
> DuckDuckGo was unable to verify sender identity
>
> On Thu, Aug 17, 2023 at 07:59:09AM -0400, brittanderson--- via isync-devel
> wrote:
>>The error has reoccured. It is:
>>
>>Socket error: receive buffer
On Thu, Aug 17, 2023 at 07:59:09AM -0400, brittanderson--- via isync-devel
wrote:
The error has reoccured. It is:
Socket error: receive buffer full. Probably protocol error.
hmm, this might in fact be one of the two regressions that prevent me
from releasing 1.5.0 - i honestly don't rem
The error has reoccured. It is:
Socket error: receive buffer full. Probably protocol error.
running =mbsync -D university=
Gives an output that includes this snippet:
#+Begin_quote
N: Called get_uidnext, ret=1273
-> log: F 1 1273 (save UIDNEXT of near side)
-> log: # 192877 0 yMXnDc
ds as well, and their
pairings with remote (far-side) ones.
I saw the pairs, but there was no element with the same UID as the error
message about the socket error. Do the UID in the error reports come
from elsewhere as well?
you'd need to show some logs for me to have a clue what you're
; pairings with remote (far-side) ones.
I saw the pairs, but there was no element with the same UID as the error
message about the socket error. Do the UID in the error reports come
from elsewhere as well? For example, something related to davmail or the
microsoft exchange server I am talking to?
On Tue, Aug 15, 2023 at 10:47:12AM -0400, Britt Anderson via isync-devel wrote:
Because of the "fetch" issue I upgraded from 1.4.4 to master,
which "fetch" issue in particular are you referring to?
which was been running well when I got a non-zero exit code because of
Because of the "fetch" issue I upgraded from 1.4.4 to master, which was
been running well when I got a non-zero exit code because of
socket error with a statement about a possible protocol violation. I
downgraded to 1.4.4 and the error went away. After awhile of dealing
with the &qu
10 UID FETCH 110231 (BODY.PEEK[])
Oct 28 15:17:36 (2 in progress) >>> 11 UID FETCH 110283 (BODY.PEEK[])
Oct 28 15:17:36 (3 in progress) >>> 12 UID FETCH 110284 (BODY.PEEK[])
Oct 28 15:17:56 Socket error on imap.gmail.com (74.125.140.109:993): timeout.
```
that may mean that less
))
...
```
> > Changing the pipeline depth from 4 to 1, it becomes:
> > ```
> > far side: 41156 messages, 0 recent
> > Warning: lost track of 1 pushed message(s)
> > Synchronizing...
> > > > > 8 APPEND "INBOX" (\Seen) {29056725}
> > + go a
e: 41156 messages, 0 recent
Warning: lost track of 1 pushed message(s)
Synchronizing...
8 APPEND "INBOX" (\Seen) {29056725}
+ go ahead
Socket error on imap.gmail.com (64.233.184.108:993): timeout.
```
that's weird - this was supposed to be fixed since v1.3.2.
running
mbsync
ral advice is "don't worry about it".
Problem is, the message doesn't go away when you re-run mbsync.
In the past I think I've just nuked the whole maildir and re-synced from
scratch, but that does seem like a sledge hammer solution.
I also notice:
```
Socket error o
On 2022-07-03 at 00:42 -07, Oswald Buddenhagen
wrote:
> On Sat, Jul 02, 2022 at 06:57:41AM -0700, Ken Mankoff wrote:
>>Socket error: secure connect to imap.gmail.com (74.125.20.109:993):
>>error:0ABF:SSL routines::no protocols available
>>
> i suppose you have SS
On Sat, Jul 02, 2022 at 06:57:41AM -0700, Ken Mankoff wrote:
Socket error: secure connect to imap.gmail.com (74.125.20.109:993):
error:0ABF:SSL routines::no protocols available
i suppose you have SSLVersions set and didn't adjust it to include
anything recent.
git master conta
Hello,
I've just set up a clean computer using ubuntu 22.04. I moved over my old
mbsyncrc which was from v1.2.X I think. I got error messages about
master/slave being deprecated, changed to near/far, and tried to run
mbsync. I am getting this error:
Socket error: secure connect to imap.gmai
On Sun, Dec 19, 2021 at 09:32:03AM -0500, David Denton wrote:
Can issues with lost messages be cause by deleting messages on another
device connected to the gmail account? Or from the same computer using
another email program such as Thunderbird? Is best practice to only
flag messages from with
As a result of a major system problem, I was obliged to reinstall
Ubuntu 21.10. Now on isync is working perfectly for me with gmail
so no need to pursue this.
Can issues with lost messages be cause by deleting messages on
another device connected to the gmail account? Or from the same
compute
On Thu, Dec 16, 2021 at 07:36:26PM -0500, David Denton wrote:
Okay, I was able to direct -D to a file, but it is 6MB. Will the list
permit an attachment of that size?
no, mail it to me privately.
___
isync-devel mailing list
isync-devel@lists.sour
Okay, I was able to direct -D to a file, but it is 6MB. Will the
list permit an attachment of that size?
Oswald Buddenhagen writes:
On Thu, Dec 16, 2021 at 03:52:24PM -0500, David Denton wrote:
See attached file with portion of mbsync.log using the -Ds
option
that's unfortunately not p
On Thu, Dec 16, 2021 at 03:52:24PM -0500, David Denton wrote:
See attached file with portion of mbsync.log using the -Ds option
that's unfortunately not particularly useful.
(I don't seem to be able to use the -D option without errors.)
what kind of errors?
have you tried redirecting to a f
before the
error / timeout message. Very annoying! ]
C: 2/5 B: 2/5 M: +0/1 *3/3 #0/0 S: +1/9 *0/0 #0/0
Socket error on imap.gmail.com (172.253.62.109:993): timeout.
See attached file with portion of mbsync.log using the -Ds option
(I don't seem to be able to use the -D option without e
On Tue, Mar 23, 2021 at 03:48:58PM +0100, Oswald Buddenhagen wrote:
> On Mon, Mar 22, 2021 at 11:19:24PM +0100, Joel Granados wrote:
> > On Thu, Mar 18, 2021 at 11:03:00PM +0100, Oswald Buddenhagen wrote:
> > > On Thu, Mar 18, 2021 at 09:09:53PM +0100, Joel Granados wrote:
> > > > I indeed went ba
On Mon, Mar 22, 2021 at 11:19:24PM +0100, Joel Granados wrote:
On Thu, Mar 18, 2021 at 11:03:00PM +0100, Oswald Buddenhagen wrote:
On Thu, Mar 18, 2021 at 09:09:53PM +0100, Joel Granados wrote:
> I indeed went back to my original comment and restarted from there. I
> notcied that there is a link
Hello
On Thu, Mar 18, 2021 at 11:03:00PM +0100, Oswald Buddenhagen wrote:
> On Thu, Mar 18, 2021 at 09:09:53PM +0100, Joel Granados wrote:
> > I indeed went back to my original comment and restarted from there. I
> > notcied that there is a link that is created when openssl is installed
> > in de
On Thu, Mar 18, 2021 at 09:09:53PM +0100, Joel Granados wrote:
I indeed went back to my original comment and restarted from there. I
notcied that there is a link that is created when openssl is installed
in debian bullseye /lib/ssl/openssl.cnf -> /etc/ssl/openssl.cnf.
fwiw, it's /usr/lib/ssl/op
I indeed went back to my original comment and restarted from there. I
notcied that there is a link that is created when openssl is installed
in debian bullseye /lib/ssl/openssl.cnf -> /etc/ssl/openssl.cnf.
If I change the name of this link, mbsync (the one installed by debian)
works again.
I'm not
On Fri, Mar 12, 2021 at 09:29:06AM +0100, Joel Granados wrote:
The systems are actually quite different (I forgot to mention it).
well, that kind of defeats the configuration difference based approach.
but that working second system seems to be a side track anyway. you
started out with this:
On Fri, Mar 12, 2021 at 09:29:06AM +0100, Joel Granados wrote:
> This is good to know (not to focus too much on the resolv thing). The
> systems are actually quite different (I forgot to mention it).
Try a fresh Debian installation (container, hosting, etc).
It can confirm mbsync works fine on D
On Thu, Mar 11, 2021 at 03:23:59PM +0100, Oswald Buddenhagen wrote:
> On Thu, Mar 11, 2021 at 02:11:53PM +0100, Joel Granados wrote:
> > /lib -> usr/lib
> > /lib32 -> usr/lib32
> > /lib64 -> usr/lib64
> > /libx32 -> usr/libx32
> > /usr/lib
> > /usr/lib32
> > /usr/lib64
> > /usr/libx32
> >
> ok, th
On Thu, Mar 11, 2021 at 02:11:53PM +0100, Joel Granados wrote:
/lib -> usr/lib
/lib32 -> usr/lib32
/lib64 -> usr/lib64
/libx32 -> usr/libx32
/usr/lib
/usr/lib32
/usr/lib64
/usr/libx32
ok, the system simply aliases /lib* to /usr/lib* (i think that's the new
debian policy), so the "duplicate" fil
On Mon, Mar 08, 2021 at 11:22:31PM +0100, Oswald Buddenhagen wrote:
> On Mon, Mar 08, 2021 at 09:30:07PM +0100, Joel Granados wrote:
> > Clearly there are several links for the libraries on the box that does
> > not work,
> >
> yeah, that seems like a likely problem source.
>
> > question is. How
On Mon, Mar 08, 2021 at 09:30:07PM +0100, Joel Granados wrote:
Clearly there are several links for the libraries on the box that does
not work,
yeah, that seems like a likely problem source.
question is. How can I work around this without fiddling around with my
systems configuration?
that
Hello Oswald
Thx for the response and sorry for taking so long to get back.
On Fri, Feb 05, 2021 at 10:44:12PM +0100, Oswald Buddenhagen wrote:
> On Fri, Feb 05, 2021 at 10:03:46PM +0100, Joel Granados wrote:
> > Any ideas?
> >
> not really. check with ldd what mbsync is linking in both cases.
>
On Fri, Feb 05, 2021 at 10:03:46PM +0100, Joel Granados wrote:
Any ideas?
not really. check with ldd what mbsync is linking in both cases.
ls -l these libraries; i wouldn't be surprised if symlinks are involved.
you could use ltrace to see if there is a difference (also strace, but
that's a lo
Hey fine ppl
My subject is the same as a mail sent by fwoodhead back in 2020-02-11. I
used the same Subject because I got the same message. I did not answer
that thread because I just joined.
My problem is that I get the error in the subject. The (very) freaky
thing is that when I uninstall opens
On Tue, Feb 11, 2020 at 02:49:40PM +, fwoodh...@doctors.org.uk wrote:
I would be very grateful for any pointers.
use the 1.3 branch from git, that should give you clearer ssl errors.
anyway, the output from openssl suggests that the tunnel is botched.
maybe you forwarded to somewhere els
:Work-remote:
Slave :Work-local:
Create Slave
Sync Pull
SyncState *
-
The original output from mbsync Work is
C: 0/1 B: 0/1 M: +0/0 *0/0 #0/0 S: +0/0 *0/0 #0/0
Socket error: secure connect to 127.0.0.1 (127.0.0.1:1993): Success
C: 1/1 B: 0/1 M: +0/0 *0/0 #0/0 S: +0/0 *0/0 #
On Thu, Aug 01, 2019 at 06:12:28PM +0530, Pankaj Jangid wrote:
> Is this of any use? ->
>
it doesn't tell us anything except that no reply came when one was
expected.
that's why i suggested strace - then you'll see whether there is
*actually* no reply, or mbsync just doesn't see it due to some bu
BODY.PEEK[])
(9 in progress) M: >>> 21 UID FETCH 316927 (BODY.PEEK[])
(10 in progress) M: >>> 22 UID FETCH 316965 (BODY.PEEK[])
(11 in progress) M: >>> 23 UID FETCH 317041 (BODY.PEEK[])
(12 in progress) M: >>> 24 UID FETCH 317073 (BODY.PEEK[])
(13 in progress) M: >>
check for more logs and the revert. I am
getting this in emails
> Warning: lost track of 6 pulled message(s)
> Warning: lost track of 1 pushed message(s)
> Socket error on imap.gmail.com (74.125.68.109:993): timeout.
--
Pankaj
Planet Earth.
""
Q: How much does it cost t
> =
> [stuff here]
> Subject: Cron /usr/local/bin/mbsync -c
> /Users/pankaj/.mbsyncrc -a
> [more stuff here]
>
> Warning: lost track of 4 pulled message(s)
> Warning: lost track of 1 pushed message(s)
> Socket error on imap.gmail.com (74.125.24.109:993): timeout.
&g
0190731134709.09B862034F5C9C@Pankajs-MacBook-Pro.local>
Date: Wed, 31 Jul 2019 19:15:06 +0530 (IST)
Warning: lost track of 4 pulled message(s)
Warning: lost track of 1 pushed message(s)
Socket error on imap.gmail.com (74.125.24.109:993): timeout.
=
)
9 OK Success
>>> 10 C
On Wed, Jul 31, 2019 at 01:06:13PM +0200, Oswald Buddenhagen wrote:
> On Wed, Jul 31, 2019 at 03:36:16PM +0530, Pankaj Jangid wrote:
> > Socket error on imap.gmail.com (74.125.24.108:993): timeout.
> >
> that might be a case for strace.
> you may also try mbsync's -
On Wed, Jul 31, 2019 at 03:36:16PM +0530, Pankaj Jangid wrote:
> Socket error on imap.gmail.com (74.125.24.108:993): timeout.
>
that might be a case for strace.
you may also try mbsync's -Dn (and -DN) options.
it would also be possible to use Tunnel with openssl s_client -quiet
-connec
+0/0 *0/0 #0/0 S: +2/2 *0/0 #0/0
> Warning: lost track of 1 pulled message(s)
> Warning: lost track of 1 pushed message(s)
> C: 4/12 B: 4/12 M: +0/1 *0/0 #0/0 S: +2/3 *0/0 #0/0
> Socket error on imap.gmail.com (74.125.24.108:993): timeout.
> C: 12/12 B: 12/12 M: +0/1 *0/0
commit 0b7cfa35242ff40409c53735c21447a88f20a202
Author: Oswald Buddenhagen
Date: Fri Mar 29 18:22:40 2013 +0100
improve socket error reporting
always use getsockopt() to query the meaning of POLLERR, rather than
reporting "Unidentified socket error".
this is u
67 matches
Mail list logo
