Re: Humble question
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
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
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. ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
Re: Humble question
> > 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
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
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. 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). ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
Re: Humble question
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
Re: Humble question
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. ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
