New Socket Error

2024-11-02 Thread 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 full. Probably protocol error.

thanks for any hints!

/Henrik
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel


Re: Socket error

2024-05-16 Thread Henrik Frisk
Den tis 16 apr. 2024 kl 21:13 skrev Henrik Frisk :

>
>
> 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, that I get socket errors. The basic connection
>> through
>> > Davmail works becuase running mbsync triggers a successful login to the
>> > server.
>> >
>> > Best,
>> > Henrik
>>
>> I can offer a working config with an account that uses SSO:
>>
>>
>> https://github.com/ferdinandyb/dotfiles/blob/master/.config/davmail/davmail.properties
>>
>> It 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 this is a davmail
problem or mbsync? To recap, here's the context:

- I have Davmail setup with 2FA against my work office 365, it works fine
with msmtp
- Running mbsync results in a the error: Socket error on 127.0.0.1 (
127.0.0.1:1143): timeout.

My mbsyncrc is:
IMAPAccount kmh
Host 127.0.0.1
Port 1143
User 
Pass ""
TLSType None
AuthMechs LOGIN

I know too little about these things to tell if it works with msmtp, it
should work with mbsync. I'm on a macos and will be happy to pass on the
log if that would be useful.

Any suggestions apart from the very kind help above are woelcome!
/Henrik
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel


Re: Socket error

2024-04-16 Thread Henrik Frisk
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, that I get socket errors. The basic connection through
> > Davmail works becuase running mbsync triggers a successful login to the
> > server.
> >
> > Best,
> > Henrik
>
> I can offer a working config with an account that uses SSO:
>
>
> https://github.com/ferdinandyb/dotfiles/blob/master/.config/davmail/davmail.properties
>
> It may not help you though ...
>
> Thanks! I will try and see if it helps!

/Henrik
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel


Re: Socket error

2024-04-14 Thread Henrik Frisk
Den mån 1 apr. 2024 kl 19:26 skrev Bence Ferdinandy :

> 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 127.0.0.1 (127.0.0.1:1143): timeout.
> > Processed 1 box(es) in 1 channel(s),
> > pulled 0 new message(s) and 0 flag update(s),
> > expunged 0 message(s) from near side,
> > expunged 0 message(s) from far side.
> >
> > This is my mbsyncrc (I likely cause of the error)
> > IMAPAccount kmh
> > Host 127.0.0.1
> > Port 1143
> > User >username>
> > PassCmd "security find-generic-password ..."
> > TLSType None
> > AuthMechs LOGIN
> >
> > IMAPStore kmh-remote
> > Account kmh
> >
> > MaildirStore kmh-local
> > SubFolders Verbatim
> > Path ~/.maildir/kmh/
> > Inbox ~/.maildir/kmh/INBOX
> >
> > Channel kmh
> > Far :kmh-remote:
> > Near :kmh-local:
> > Patterns *
> > Create Near
> > Sync Pull
> > Expunge Both
> > Remove None
> >
> > Any suggestions?
> > /Henrik
>
> the aerc wiki has an entry on davmail with isync:
>
> https://man.sr.ht/~rjarry/aerc/providers/microsoft.md#office365-with-imap-disabled
>
> I think the main thing would be to pass an empty password maybe?
>
> Best,
> Bence
>

Sorry for replying in the wrong order, Bence's reply had ended up in the
spamfolder.
/h
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel


Re: Socket error

2024-04-14 Thread Henrik Frisk
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 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 0 flag update(s),
> expunged 0 message(s) from near side,
> expunged 0 message(s) from far side.
>
> This is my mbsyncrc (I likely cause of the error)
> IMAPAccount kmh
> Host 127.0.0.1
> Port 1143
> User >username>
> PassCmd "security find-generic-password ..."
> TLSType None
> AuthMechs LOGIN
>
> Any suggestions?
> /Henrik
>

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 becuase running mbsync triggers a successful login to the
server.

Best,
Henrik
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel


Socket error

2024-04-01 Thread 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 127.0.0.1 (127.0.0.1:1143): timeout.
Processed 1 box(es) in 1 channel(s),
pulled 0 new message(s) and 0 flag update(s),
expunged 0 message(s) from near side,
expunged 0 message(s) from far side.

This is my mbsyncrc (I likely cause of the error)
IMAPAccount kmh
Host 127.0.0.1
Port 1143
User >username>
PassCmd "security find-generic-password ..."
TLSType None
AuthMechs LOGIN

IMAPStore kmh-remote
Account kmh

MaildirStore kmh-local
SubFolders Verbatim
Path ~/.maildir/kmh/
Inbox ~/.maildir/kmh/INBOX

Channel kmh
Far :kmh-remote:
Near :kmh-local:
Patterns *
Create Near
Sync Pull
Expunge Both
Remove None

Any suggestions?
/Henrik
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel


Re: mbsync skips certain messages

2024-04-01 Thread Henrik Frisk
Den lör 23 mars 2024 kl 09:19 skrev Oswald Buddenhagen via isync-devel <
isync-devel@lists.sourceforge.net>:

> On Fri, Mar 22, 2024 at 01:09:58PM +0100, Henrik Frisk wrote:
> > Sorry for my lack of knowledge here, but based on what information do
> > I best identify the message in the debugging output ?
> >
> i presume that any message being skipped is a problem, so that's the
> only thing to look for in the log. if it turns out that the message
> contents matter, using -DN will probably help.
>
> you are not expected to do that yourself. just send me the log along
> with the config.
>
> I realize that part of the problem was elsewhere and while starting to
stream line that other aspect I suspect the current problem will find a
solution. Ran into another one however, but will start a new thread.

Thank you!
/Henrik
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel


Re: mbsync skips certain messages

2024-03-22 Thread Henrik Frisk
Den fre 22 mars 2024 kl 11:48 skrev Oswald Buddenhagen via isync-devel <
isync-devel@lists.sourceforge.net>:

> On Fri, Mar 22, 2024 at 10:29:28AM +0100, Henrik Frisk wrote:
> >After a long time of working flawlessly my sync process now skips certain
> >messages. I have not been able to see how/if the skipped messages relate.
> >
> it's pretty hopeless to figure this out unless you can catch it in the
> act with debugging enabled (-D option).
>
> Sorry for my lack of knowledge here, but based on what information do I
best identify the message in the debugging output ?

you can force it to re-attenpt messages it has already given up on by
> hacking MaxPulledUID in the sync state file; several of the most recent
> threads on this list had mentions of that.
>
> Ok, I should look into that.

Thanks!
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel


mbsync skips certain messages

2024-03-22 Thread Henrik Frisk
After a long time of working flawlessly my sync process now skips certain
messages. I have not been able to see how/if the skipped messages relate.
Not sure if it helps but here's the beginning of one of these sikpped
messaged:

Received: from GVZP280MB0410.SWEP280.PROD.OUTLOOK.COM
(2603:10a6:150:41::18) by GV3P280MB0211.SWEP280.PROD.OUTLOOK.COM with
HTTPS; Thu, 21 Mar 2024 22:53:54 + Received: from
AM9P195CA0017.EURP195.PROD.OUTLOOK.COM (2603:10a6:20b:21f::22) by
GVZP280MB0410.SWEP280.PROD.OUTLOOK.COM (2603:10a6:150:41::18) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7386.35; Thu, 21 Mar
2024 22:53:50 + Received: from AMS1EPF0049.eurprd04.prod.outlook.com
(2603:10a6:20b:21f:cafe::8) by AM9P195CA0017.outlook.office365.com
(2603:10a6:20b:21f::22) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7386.28 via Frontend
Transport; Thu, 21 Mar 2024 22:53:49 + Authentication-Results: spf=pass
(sender IP is 93.188.3.37)

Thanks for any inputs!
/henrik
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel


Re: Sudden UTHENTICATE failed.

2024-01-29 Thread Henrik Frisk
Den mån 29 jan. 2024 kl 10:58 skrev Bence Ferdinandy :

> Hi Henrik,
>
>
> On Mon Jan 29, 2024 at 10:47, Henrik Frisk  wrote:
> > Hi,
> >
> > Thanks for your reply, and apologies for my messy subject field.
> >
> > It's still odd, since the problem only started Friday afternoon. Anyway,
> I
> > fought hard to setup OAuth2 on my system a year or so ago and in the end
> I
> > found another solution (forwarding all email to a free office365
> account).
> > I'm guessing this is now not allowing the AuthMechs PLAIN anymore.
>
> I would suggest trying mailctl, it usually works:
> https://github.com/pdobsan/mailctl
>
> I have a bit written up on it for getting it working with O365:
>
> https://bence.ferdinandy.com/2023/07/20/email-in-the-terminal-a-complete-guide-to-the-unix-way-of-email/#oauth-mailctl
>
> Alternatively, if all else fails, davmail might be a solution, the aerc
> wiki
> has some stuff about setting it up:
> https://man.sr.ht/~rjarry/aerc/providers/microsoft.md
>
> Thanks a lot Bence, I will try that!

/Henrik
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel


Re: Sudden UTHENTICATE failed.

2024-01-29 Thread Henrik Frisk
Hi,

Thanks for your reply, and apologies for my messy subject field.

It's still odd, since the problem only started Friday afternoon. Anyway, I
fought hard to setup OAuth2 on my system a year or so ago and in the end I
found another solution (forwarding all email to a free office365 account).
I'm guessing this is now not allowing the AuthMechs PLAIN anymore.

The top hits of "mbsync office365" are a year old or more and I have read
most. I'm on a Macbook M1, using mbsync with mu4e and if someone has a hint
I would be happy! I have followed this, among others
https://sites.uw.edu/bxf4/2022/09/01/getting-uw-outlook-365-oauth2-to-work-with-emacs-mu4e-mbsync-and-msmtp/
but it doesn't work since I don't have Office 365 admin priveleges.

Thanks!
/Henrik

Den mån 29 jan. 2024 kl 09:46 skrev Peter P. :

> Henrik,
>
> what is your authentication method? Microsoft only allows
> AuthMechs XOAUTH2
> since a few months. A startpage.com search for "mbsync office365" might
> yield additional hints.
>
> best, P
>
> * Henrik Frisk  [2024-01-29 08:50]:
> > Hi,
> >
> > Well aware this is not a question for the devel list I'm taking my
> chances.
> > After no configuration change my mbsync command started returning this
> > error (not every time, but farily often):
> >
> > IMAP command 'AUTHENTICATE PLAIN ' returned an error:
> > AUTHENTICATE failed.
> >
> > Any ideas that might have caused this? The server is an Office365.
> >
> > Best,
> > Henrik
>
>
> > ___
> > isync-devel mailing list
> > isync-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/isync-devel
>
>
>
> ___
> isync-devel mailing list
> isync-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/isync-devel
>
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel


Sudden UTHENTICATE failed.

2024-01-28 Thread Henrik Frisk
Hi,

Well aware this is not a question for the devel list I'm taking my chances.
After no configuration change my mbsync command started returning this
error (not every time, but farily often):

IMAP command 'AUTHENTICATE PLAIN ' returned an error:
AUTHENTICATE failed.

Any ideas that might have caused this? The server is an Office365.

Best,
Henrik
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel


Re: Humble question

2023-03-19 Thread Henrik Frisk
Den sön 19 mars 2023 kl 12:04 skrev Henrik Frisk :

>
>
> Den lör 18 mars 2023 kl 21:55 skrev Oswald Buddenhagen <
> oswald.buddenha...@gmx.de>:
>
>> On Sat, Mar 18, 2023 at 07:00:27PM +0100, Henrik Frisk wrote:
>> >sync.c:1207:8: error: implicit declaration of function 'fdatasync'
>> >[-Werror,-Wimplicit-function-declaration]
>> >
>> >Do you have a workaround for that?
>> >
>> --- a/src/common.h
>> +++ b/src/common.h
>> @@ -172,7 +172,7 @@ void flushn( void );
>>   char *xvasprintf( const char *fmt, va_list ap );
>>   void xprintf( const char *fmt, ... );
>>
>> -#if !defined(_POSIX_SYNCHRONIZED_IO) || _POSIX_SYNCHRONIZED_IO <= 0
>> +#if 1 //!defined(_POSIX_SYNCHRONIZED_IO) || _POSIX_SYNCHRONIZED_IO <= 0
>>   # define fdatasync fsync
>>   #endif
>>
>> should do, but i wonder what the reason for the misdetection is. either
>> the macos headers are botched, or the documentation, or i misinterpreted
>> something.
>>
>> I think it's that the headers are botched, you can read about it here:
>
> https://trac.macports.org/ticket/62838
>
> Anyway, it works now and it seems to have resolved the issue too!
>

That is, it almost works. Not sure if this is an mbsync issue, or a
configuration issue. It appears to connect to the service but it doens't
retrieve/see and mail:

Processed 19 box(es) in 1 channel(s),
pulled 0 new message(s) and 0 flag update(s),
expunged 0 message(s) from near side,
pushed 0 new message(s) and 0 flag update(s),
expunged 0 message(s) from far side.

although there are new email. I have a setup with two outlook accounts and
the other one works fine.

any hints are welcome.

/h

>
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel


Re: Humble question

2023-03-19 Thread Henrik Frisk
Den lör 18 mars 2023 kl 21:55 skrev Oswald Buddenhagen <
oswald.buddenha...@gmx.de>:

> On Sat, Mar 18, 2023 at 07:00:27PM +0100, Henrik Frisk wrote:
> >sync.c:1207:8: error: implicit declaration of function 'fdatasync'
> >[-Werror,-Wimplicit-function-declaration]
> >
> >Do you have a workaround for that?
> >
> --- a/src/common.h
> +++ b/src/common.h
> @@ -172,7 +172,7 @@ void flushn( void );
>   char *xvasprintf( const char *fmt, va_list ap );
>   void xprintf( const char *fmt, ... );
>
> -#if !defined(_POSIX_SYNCHRONIZED_IO) || _POSIX_SYNCHRONIZED_IO <= 0
> +#if 1 //!defined(_POSIX_SYNCHRONIZED_IO) || _POSIX_SYNCHRONIZED_IO <= 0
>   # define fdatasync fsync
>   #endif
>
> should do, but i wonder what the reason for the misdetection is. either
> the macos headers are botched, or the documentation, or i misinterpreted
> something.
>
> I think it's that the headers are botched, you can read about it here:

https://trac.macports.org/ticket/62838

Anyway, it works now and it seems to have resolved the issue too!

Thanks!

/Henrik
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel


Re: Humble question

2023-03-18 Thread Henrik Frisk
>
> you could try mbsync master to see whether it works better (it contains
> two known bugs, but is otherwise stable (i don't remember what they are;
> the project currently has no priority. but i use it every day). note
> that running the new version upgrades the store in a
> backwards-incompatible way, so you should make a copy first, so you can
> roll back).
>

Unfortunately I ran into a bug I'm not sure how to resolve. Trying to
compile isync on MacOs fails due to an odd situation that MacOs reports
fdatasync exists when running the configure but in fact it doesn't exist
giving me

sync.c:45:62: error: implicit declaration of function 'fdatasync'
[-Werror,-Wimplicit-function-declaration]

and

sync.c:1207:8: error: implicit declaration of function 'fdatasync'
[-Werror,-Wimplicit-function-declaration]

Do you have a workaround for that?

/henrik
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel


Re: Humble question

2023-03-16 Thread Henrik Frisk
Den tors 16 mars 2023 kl 20:41 skrev Oswald Buddenhagen <
oswald.buddenha...@gmx.de>:

> On Thu, Mar 16, 2023 at 04:38:27PM +0100, Henrik Frisk wrote:
> >and finally this
> >
> >116 UID STORE 8910 +FLA8 OK STORE completed.
> >
> well, this is just more garbage.
> it appears that some bytes from the data stream are just dropped, but it
> will be tough to figure out where that happens - could be somewhere in
> the server, or in mbsync at any point.
>
> you can try limiting PipelineDepth as a workaround.
>
> if you post the -Dn log from the connection setup i might see more
> options for workarounds.
>
> Thanks! It's attached to this mail


> you could try mbsync master to see whether it works better (it contains
> two known bugs, but is otherwise stable (i don't remember what they are;
> the project currently has no priority. but i use it every day). note
> that running the new version upgrades the store in a
> backwards-incompatible way, so you should make a copy first, so you can
> roll back).
>
> Ok, I will try that tomorrow. I've just recently moved to a mac from linux
so I have mbsync currently installed via brew, but I will try to compile it
tomorrow and see it that makes a difference.

Thanks again!
/Henrik
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel


Re: Humble question

2023-03-16 Thread Henrik Frisk
Den tors 16 mars 2023 kl 15:20 skrev Oswald Buddenhagen <
oswald.buddenha...@gmx.de>:

> On Thu, Mar 16, 2023 at 02:39:24PM +0100, Henrik Frisk wrote:
> >IMAP command 'UID STORE 9154 +FLAGS.SILENT (\Deleted)' returned an error:
> >UID STORE 9154 +FLAG516 UID STORE 9290 +FLAG12 OK STORE completed.
> >
> looks like a garbage response from the server.
> try adding -Dn to the command line for some more context.
>
> Ah, thanks! This is the result:

There are 5000+ of similar to these:
* 1 FETCH (UID 6612 FLAGS (\Seen \Deleted))
* 2 FETCH (UID 6622 FLAGS (\Deleted))

5000 of these:

 (5019 in progress) >>> 5026 UID STORE 14618 +FLAGS.SILENT (\Deleted)

and ending with this a few of these lines

(5057 in progress) >>> 5064 UID FETCH 14662 (BODY.PEEK[])

and finally this

116 UID STORE 8910 +FLA8 OK STORE completed.

The Deleted directory on the server is empty by the way.

/Henrik
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel


Humble question

2023-03-16 Thread Henrik Frisk
Hi,

I realize this is the devel list and that my question is misplced here, but
since I couldn't find anything else I post my question here. On the IMAP
account below I get the error:

I first get the worning:
Warning: lost track of 36 pulled message(s)

and then:
C: 0/1  B: 0/19  F: +0/0 *0/5109 #0/0  N: +0/36 *0/0 #0/0
IMAP command 'UID STORE 9154 +FLAGS.SILENT (\Deleted)' returned an error:
UID STORE 9154 +FLAG516 UID STORE 9290 +FLAG12 OK STORE completed.

The local maildir is not updated. This is on a MacOS M1 and isync 1.4.4
uinstalled with brew. I have another account on the same machine that works
fine.

Thanks for any suggestions.
/H

IMAPAccount fsdata
Host imap.fsdata.se
User xxx
PassCmd "security find-generic-password -s fsdata -a xxx -w"
Port 993
SSLType IMAPS
SSLVersions TLSv1.2
AuthMechs PLAIN
SystemCertificates no
CertificateFile ~/.maildir/certificates/root-certificates.pem

IMAPStore fsdata-remote
Account fsdata

MaildirStore fsdata-local
SubFolders Verbatim
Path ~/.maildir/fsdata/
Inbox ~/.maildir/fsdata/INBOX

Channel fsdata
Far :fsdata-remote:
Near :fsdata-local:
Patterns *
Create Near
Sync All
Expunge Both
Remove None
SyncState *
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel