Re: Flags not syncing after moving email
On 2024-04-02 16:02:06, Oswald Buddenhagen via isync-devel wrote:
> On Mon, Apr 01, 2024 at 09:09:16PM +0200, Oswald Buddenhagen via isync-devel
> wrote:
> > [...] mail me the logs.
> >
> so with the logs at hand it really looks like the imap server is acting
> up:
>
> first run:
> F: >>> 10 APPEND "Folders/Test2" (\Seen) {6229}
> F: + Ready
> F: * 1 EXISTS
> F: * 1 RECENT
> F: 10 OK [APPENDUID 36790870 1] APPEND
>
> second run:
> F: >>> 7 UID FETCH 1:1 (UID FLAGS)
> F: * 1 FETCH (UID 1 FLAGS ())
> F: 7 OK command completed in 243 microsec.
>
> the \seen flag is obviously *just gone*. huh?
>
> as an experiment, see whether the same happens with \flagged.
>
> of course it would be a funny coincidence if both the proton mail bridge
> and gmail were affected in the same way. or maybe the underlying
> mechanism is actually different - you'd need to repeat the experiments
> with gmail to tell.
I was looking at some more logs yesterday where I also tried it with
flagged, and it's the same result.
F: >>> 10 APPEND "Folders/Test2" (\Flagged \Seen) {6229}
F: [ 15] Leave store_msg
N: [ 14] Callback leave fetch_msg
N: [ 14] Leave fetch_msg
N: [ 13] Callback leave load_box
N: [ 13] Leave load_box
F: [ 10] Callback leave open_box
F: + Ready
And then for the second run it says it's going to update the flags.
Quite frustrating, but it does indeed seem to be a problem with both
Gmail and Protonmail. I'm thinking of creating an email address at
another provider to see if the problem exists there too.
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
Re: Flags not syncing after moving email
On Mon, Apr 01, 2024 at 09:09:16PM +0200, Oswald Buddenhagen via isync-devel
wrote:
[...] mail me the logs.
so with the logs at hand it really looks like the imap server is acting
up:
first run:
F: >>> 10 APPEND "Folders/Test2" (\Seen) {6229}
F: + Ready
F: * 1 EXISTS
F: * 1 RECENT
F: 10 OK [APPENDUID 36790870 1] APPEND
second run:
F: >>> 7 UID FETCH 1:1 (UID FLAGS)
F: * 1 FETCH (UID 1 FLAGS ())
F: 7 OK command completed in 243 microsec.
the \seen flag is obviously *just gone*. huh?
as an experiment, see whether the same happens with \flagged.
of course it would be a funny coincidence if both the proton mail bridge
and gmail were affected in the same way. or maybe the underlying
mechanism is actually different - you'd need to repeat the experiments
with gmail to tell.
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
Re: Flags not syncing after moving email
On Mon, Apr 01, 2024 at 08:03:22PM +0200, laburnumT wrote: When I look at my settings in Gmail it is set to Auto-Expunge off - Wait for the client to update the server. that's weird, because the log shows somewhat clearly that a message is expunged before an expunge or close command is issued. I can also supply the log for a protonmail account where the same issue exists. well, at least that would avoid the confounder of gmail's virtual folders. to keep the amount of data manageable, yet useful, proceed like that: isolate a test mail into a test folder (possibly via a server-side copy using thunderbird - whatever is necessary to create the actual starting state), and already create the target folder, but don't put anything into it yet. when you sync, specify the two involved folders. like chan:fol1,fol2. sync it repeatedly, to make sure that the situation is stable. keep the log of the last such "null run". then do the move. then sync repeatedly, until nothing is happening. mail me the logs. ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
Re: Flags not syncing after moving email
On 2024-04-01 18:43:12, Oswald Buddenhagen via isync-devel wrote: > On Mon, Apr 01, 2024 at 01:37:57PM +0200, laburnumT wrote: > > Sorry that the file is in a 7z format. It was the first compression > > format I had the could get the file below the size limit for sending to > > this mailing list. > > > that's fine, though i guess i should have been more specific - when you > send an entire log, just mail it to me privately. > > from a first look, you have auto-expunge activated in gmail's imap > settings. such server behavior is on the fringe of what the spec allows, > and mightily confuses isync. When I look at my settings in Gmail it is set to Auto-Expunge off - Wait for the client to update the server. I can also supply the log for a protonmail account where the same issue exists. ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
Re: Flags not syncing after moving email
On Mon, Apr 01, 2024 at 01:37:57PM +0200, laburnumT wrote: Sorry that the file is in a 7z format. It was the first compression format I had the could get the file below the size limit for sending to this mailing list. that's fine, though i guess i should have been more specific - when you send an entire log, just mail it to me privately. from a first look, you have auto-expunge activated in gmail's imap settings. such server behavior is on the fringe of what the spec allows, and mightily confuses isync. ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
Re: Flags not syncing after moving email
Sorry that the file is in a 7z format. It was the first compression format I had the could get the file below the size limit for sending to this mailing list. The mbsync command was run with the -V and --debug flags. isync.7z Description: application/7z-compressed ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
Re: Flags not syncing after moving email
On Sat, Mar 30, 2024 at 09:32:02PM +0100, laburnumT wrote: I have looked at the logs if run with --debug-sync, --debug-net would be likely more helpful in this case, but usually it's actually better to just not limit the debug categories at all. but couldn't figure out what I had done wrong. possibly nothing. i don't see anything wrong in your config or description. the server may be acting up, or maybe isync is even buggy. we'll see. But I can supply it if that would help. yes, please. ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
