Github messages for mblaze
 help / color / mirror / Atom feed
* [ISSUE] Unresolved entries in sequence with mthread
@ 2021-11-20  2:45 fagg
  2021-11-20 10:38 ` Duncaen
                   ` (5 more replies)
  0 siblings, 6 replies; 7+ messages in thread
From: fagg @ 2021-11-20  2:45 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]

New issue by fagg on mblaze repository

https://github.com/leahneukirchen/mblaze/issues/218

Description:
Hello,

Firstly, thank you for mblaze. It's terrific.

I am however having a slight issue, which I cannot explain.

I am using isync to sync my mail to my laptop from my server which is running dovecot. I have verified that this occurs both locally and on the maildir that dovecot serves. 

Sometimes, I notice unresolved messages in sequences when I use mthread.

See this output, which was generated using this command:

> mlist -s $MAILDIR | mthread | mseq -S

You'll notice between 6 and 8, there is a weird entry in the thread that doesn't actually exist:

![mblaze-w-mthread](https://user-images.githubusercontent.com/1742468/142711808-e53f77e3-577a-4e8f-a0db-5763cfe87a61.png)

> moon$ mshow 7
> mshow: <CAKoxK+44JA+EtHk_FbLqh1RxfkCURs=mHDpyj61XJpWRwy-hfw@mail.gmail.com>: No such file or directory

But, when I omit mthread, and just run:

> mlist -s $MAILDIR | mseq -S

![mblaze-no-mthread](https://user-images.githubusercontent.com/1742468/142711816-a61102a2-0d70-4166-b6f9-a98022329aee.png)

I do not see this issue, and 62 messages in the sequence are shown correctly. In the first sequence, there's 62 valid messages but 63 total (if you assume the unresolved message counts).

Is this a bug or am I doing something wrong? Please let me know if there's anything else I can provide to help to resolve this.

Thanks!

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Unresolved entries in sequence with mthread
  2021-11-20  2:45 [ISSUE] Unresolved entries in sequence with mthread fagg
@ 2021-11-20 10:38 ` Duncaen
  2021-11-20 10:39 ` Duncaen
                   ` (4 subsequent siblings)
  5 siblings, 0 replies; 7+ messages in thread
From: Duncaen @ 2021-11-20 10:38 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 372 bytes --]

New comment by Duncaen on mblaze repository

https://github.com/leahneukirchen/mblaze/issues/218#issuecomment-974629671

Comment:
This happens if there is a mail with "In-Reply-To" header to a message id that is not part of the mails passed to `mthread`.
Sequences that are not threaded don't look at the "In-Reply-To" header so they don't add those missing message ids.

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Unresolved entries in sequence with mthread
  2021-11-20  2:45 [ISSUE] Unresolved entries in sequence with mthread fagg
  2021-11-20 10:38 ` Duncaen
@ 2021-11-20 10:39 ` Duncaen
  2021-11-20 10:45 ` Duncaen
                   ` (3 subsequent siblings)
  5 siblings, 0 replies; 7+ messages in thread
From: Duncaen @ 2021-11-20 10:39 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 460 bytes --]

New comment by Duncaen on mblaze repository

https://github.com/leahneukirchen/mblaze/issues/218#issuecomment-974629671

Comment:
This happens if there is a mail with "In-Reply-To" header to a message id that is not part of the mails passed to `mthread`, so instead of silently ignoring this, it prints the message id and uses that as parent.
Sequences that are not threaded don't look at the "In-Reply-To" header so they don't add those missing message ids.

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Unresolved entries in sequence with mthread
  2021-11-20  2:45 [ISSUE] Unresolved entries in sequence with mthread fagg
  2021-11-20 10:38 ` Duncaen
  2021-11-20 10:39 ` Duncaen
@ 2021-11-20 10:45 ` Duncaen
  2021-11-20 10:45 ` Duncaen
                   ` (2 subsequent siblings)
  5 siblings, 0 replies; 7+ messages in thread
From: Duncaen @ 2021-11-20 10:45 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 944 bytes --]

New comment by Duncaen on mblaze repository

https://github.com/leahneukirchen/mblaze/issues/218#issuecomment-974629671

Comment:
This happens if there is a mail with `In-Reply-To` header to a message id that is not part of the mails passed to `mthread`, so instead of silently ignoring this, it prints the message id and uses that as parent.
Sequences that are not threaded don't look at the `In-Reply-To` header so they don't add those missing message ids.

This could have been either someone mailing the person replying to the non-existing message-id directly instead of the list who then replies back to the mailing list.
Another possibility is that the message ends up in spam filter/folder and is not part of the sequence passed to `mthread`.
Some automatic mails, like from github threads will just put a non-existing message id into `In-Reply-To` to group mails about issue comments into a thread which are not actually threaded.

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Unresolved entries in sequence with mthread
  2021-11-20  2:45 [ISSUE] Unresolved entries in sequence with mthread fagg
                   ` (2 preceding siblings ...)
  2021-11-20 10:45 ` Duncaen
@ 2021-11-20 10:45 ` Duncaen
  2021-11-20 18:02 ` fagg
  2021-11-20 18:02 ` [ISSUE] [CLOSED] " fagg
  5 siblings, 0 replies; 7+ messages in thread
From: Duncaen @ 2021-11-20 10:45 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 943 bytes --]

New comment by Duncaen on mblaze repository

https://github.com/leahneukirchen/mblaze/issues/218#issuecomment-974629671

Comment:
This happens if there is a mail with `In-Reply-To` header to a message id that is not part of the mails passed to `mthread`, so instead of silently ignoring this, it prints the message id and uses that as parent.
Sequences that are not threaded don't look at the `In-Reply-To` header so they don't add those missing message ids.

This could have been either someone mailing the person replying to the non-existing message-id directly instead of the list who then replies back to the mailing list.
Another possibility is that the message ends up in spam filter/folder and is not part of the sequence passed to `mthread`.
Some automatic mails, like from github issues will just put a non-existing message id into `In-Reply-To` to group mails about issue comments into a thread which are not actually threaded.

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Unresolved entries in sequence with mthread
  2021-11-20  2:45 [ISSUE] Unresolved entries in sequence with mthread fagg
                   ` (3 preceding siblings ...)
  2021-11-20 10:45 ` Duncaen
@ 2021-11-20 18:02 ` fagg
  2021-11-20 18:02 ` [ISSUE] [CLOSED] " fagg
  5 siblings, 0 replies; 7+ messages in thread
From: fagg @ 2021-11-20 18:02 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 177 bytes --]

New comment by fagg on mblaze repository

https://github.com/leahneukirchen/mblaze/issues/218#issuecomment-974688159

Comment:
Thank you for the explanation. That makes sense. 

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ISSUE] [CLOSED] Unresolved entries in sequence with mthread
  2021-11-20  2:45 [ISSUE] Unresolved entries in sequence with mthread fagg
                   ` (4 preceding siblings ...)
  2021-11-20 18:02 ` fagg
@ 2021-11-20 18:02 ` fagg
  5 siblings, 0 replies; 7+ messages in thread
From: fagg @ 2021-11-20 18:02 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]

Closed issue by fagg on mblaze repository

https://github.com/leahneukirchen/mblaze/issues/218

Description:
Hello,

Firstly, thank you for mblaze. It's terrific.

I am however having a slight issue, which I cannot explain.

I am using isync to sync my mail to my laptop from my server which is running dovecot. I have verified that this occurs both locally and on the maildir that dovecot serves. 

Sometimes, I notice unresolved messages in sequences when I use mthread.

See this output, which was generated using this command:

> mlist -s $MAILDIR | mthread | mseq -S

You'll notice between 6 and 8, there is a weird entry in the thread that doesn't actually exist:

![mblaze-w-mthread](https://user-images.githubusercontent.com/1742468/142711808-e53f77e3-577a-4e8f-a0db-5763cfe87a61.png)

> moon$ mshow 7
> mshow: <CAKoxK+44JA+EtHk_FbLqh1RxfkCURs=mHDpyj61XJpWRwy-hfw@mail.gmail.com>: No such file or directory

But, when I omit mthread, and just run:

> mlist -s $MAILDIR | mseq -S

![mblaze-no-mthread](https://user-images.githubusercontent.com/1742468/142711816-a61102a2-0d70-4166-b6f9-a98022329aee.png)

I do not see this issue, and 62 messages in the sequence are shown correctly. In the first sequence, there's 62 valid messages but 63 total (if you assume the unresolved message counts).

Is this a bug or am I doing something wrong? Please let me know if there's anything else I can provide to help to resolve this.

Thanks!

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2021-11-20 18:02 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-11-20  2:45 [ISSUE] Unresolved entries in sequence with mthread fagg
2021-11-20 10:38 ` Duncaen
2021-11-20 10:39 ` Duncaen
2021-11-20 10:45 ` Duncaen
2021-11-20 10:45 ` Duncaen
2021-11-20 18:02 ` fagg
2021-11-20 18:02 ` [ISSUE] [CLOSED] " fagg

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).