+1

I can't reproduce this on the master branch.

In case it helps, here is an example log of a move Archive command:

2022/03/24 12:33:44 (ui)=> *types.CopyMessages
2022/03/24 12:33:44 <-(ui) *types.CopyMessages(1115)
DONE
2022/03/24 12:33:44 ThreadBuilder: 10 threads created in 540.16µs
W4e0_w OK Idle completed (0.001 + 17.463 + 17.462 secs).
TRXjEg UID COPY 3954 "Archive"
TRXjEg OK No messages found (0.001 + 0.000 secs).
2022/03/24 12:33:44 ->(ui) *types.Done:*types.CopyMessages
J6v4aA IDLE
+ idling
2022/03/24 12:33:44 (ui)<= *types.Done(1116):*types.CopyMessages(1115)
2022/03/24 12:33:44 (ui)=> *types.DeleteMessages
2022/03/24 12:33:44 <-(ui) *types.DeleteMessages(1117)
DONE
J6v4aA OK Idle completed (0.001 + 0.014 + 0.013 secs).
iMWagQ UID STORE 3954 +FLAGS.SILENT (\Deleted)
iMWagQ OK Store completed (0.001 + 0.000 secs).
xtK_UQ EXPUNGE
xtK_UQ OK Expunge completed (0.001 + 0.000 secs).
2022/03/24 12:33:44 ->(ui) *types.MessagesDeleted:*types.DeleteMessages
2022/03/24 12:33:44 ->(ui) *types.Done:*types.DeleteMessages
v1GOEg IDLE
+ idling
2022/03/24 12:33:44 (ui)<= *types.MessagesDeleted(1118):*types.DeleteMessages(1117)
2022/03/24 12:33:44 ThreadBuilder: 10 threads created in 691.208µs
2022/03/24 12:33:44 (ui)<= *types.Done(1119):*types.DeleteMessages(1117)

Log of the mark+move Archive command:

2022/03/24 12:34:04 (ui)=> *types.CopyMessages
2022/03/24 12:34:04 <-(ui) *types.CopyMessages(1120)
DONE
2022/03/24 12:34:04 ThreadBuilder: 10 threads created in 6.44146ms
v1GOEg OK Idle completed (0.001 + 19.979 + 19.979 secs).
0NKOeA UID COPY 3954,3957 "Archive"
0NKOeA OK [COPYUID 1551717226 3957 957] Copy completed (1.700 + 0.000 + 1.699 secs).
2022/03/24 12:34:05 ->(ui) *types.Done:*types.CopyMessages
nPnieA IDLE
2022/03/24 12:34:05 (ui)<= *types.Done(1121):*types.CopyMessages(1120)
2022/03/24 12:34:05 (ui)=> *types.DeleteMessages
2022/03/24 12:34:05 <-(ui) *types.DeleteMessages(1122)
+ idling
DONE
nPnieA OK Idle completed (0.001 + 0.011 + 0.010 secs).
FC461g UID STORE 3954,3957 +FLAGS.SILENT (\Deleted)
FC461g OK Store completed (0.001 + 0.000 secs).
A5mt7A EXPUNGE
* 23 EXPUNGE
* 1 RECENT
A5mt7A OK Expunge completed (0.001 + 0.000 secs).
2022/03/24 12:34:06 ->(ui) *types.MessagesDeleted:*types.DeleteMessages
2022/03/24 12:34:06 ->(ui) *types.Done:*types.DeleteMessages
2022/03/24 12:34:06 (= *client.MailboxUpdate
2022/03/24 12:34:06 ->(ui) *types.DirectoryInfo
8D3Wyg IDLE
2022/03/24 12:34:06 (ui)<= *types.MessagesDeleted(1123):*types.DeleteMessages(1122)
2022/03/24 12:34:06 ThreadBuilder: 9 threads created in 395.358µs
2022/03/24 12:34:06 (ui)<= *types.Done(1124):*types.DeleteMessages(1122)
2022/03/24 12:34:06 (ui)<= *types.DirectoryInfo(1125)
2022/03/24 12:34:06 (ui)=> *types.FetchDirectoryContents
2022/03/24 12:34:06 <-(ui) *types.FetchDirectoryContents(1126)
2022/03/24 12:34:06 ThreadBuilder: 9 threads created in 400.164µs
+ idling
DONE
8D3Wyg OK Idle completed (0.001 + 0.012 + 0.011 secs).
2022/03/24 12:34:06 Fetching UID list
2XflXA UID SORT (REVERSE DATE REVERSE ARRIVAL) "UTF-8" 1:*
* SORT 3959 3931 3929 3928 3927 3925 3924 3923 3920 3906 3902 3904 3901 3895 3803 3801 3799 3794 3710 2912 2903 2899 2893
2XflXA OK Sort completed (0.001 + 0.000 secs).
2022/03/24 12:34:06 Found 23 UIDs
2022/03/24 12:34:06 ->(ui) *types.DirectoryContents:*types.FetchDirectoryContents
2022/03/24 12:34:06 ->(ui) *types.Done:*types.FetchDirectoryContents
uCM0sw IDLE
+ idling
2022/03/24 12:34:06 (ui)<= *types.DirectoryContents(1127):*types.FetchDirectoryContents(1126)
2022/03/24 12:34:06 ThreadBuilder: 9 threads created in 457.765µs
2022/03/24 12:34:06 (ui)<= *types.Done(1128):*types.FetchDirectoryContents(1126)

If I'm not mistaken (please excuse me if I am), by default, ticket creators cannot close them. This is a problem if a ticket is created by mistake or for the wrong reasons, since the intervention of a mantainer is required. Afaik, the current granularity of the permissions allow to grant permissions to edit by name or to everyone, but I don't see how to activate edit permissions just for ticket creators.

The observed behaviour was not due to any bug, but to the fact that the duplicated messages were coming from two different lists but had the same message-id, so toggle-threading identifies them as the same message.

For some reason, aerc is showing duplicated messages when the threading functionality is not activated.

As an example, see this list upon launching aerc: https://transfer.sh/pnSsTu/withoutThreading.png

And this one after issuing toggle-threads: https://transfer.sh/lk7Bg1/withThreading.png

You can see how a message from Moritz Poldrack with date Tue 22:00 is repeated in the first capture and not in the second (weirdly, one copy is marked as read, the other isn't). The same thing happens with a message from Robert Winkler.

When a terminal is opened by using a defined binding (i.e. having S = terminal<Enter> defined in the binding config and effectively typing S), aerc crashes with "panic: runtime error: invalid memory address or nil pointer dereference". The terminal command works fine when manually called.

After a long disconnection (suspend through the night, for example), sometimes the move command gets broken and doesn't affect the list of messages anymore. However, if one uses mark and then move, it sort-of works: messages get moved, although sometimens the list does not update properly.

XOAUTHBEARER is supported, but that's not the case for XOAUTH2 [0]. Gmail uses the former, O365 the later.

[0] https://github.com/emersion/go-sasl/issues/18

Maybe this is unrelated, but I'm also experiencing long delays in Maildir (over 20s for a folder with ~20.000 messages). In the logs, I'm getting a lot of errors "could not get flags: maildir: invalid mailfile format". My file names are set by mbsync (and do have flags properly declared, afaik). The same problem affects the notmuch interface too.

EDIT: the errors were due to a faulty patch that has now been solved. However, the long times are still there and I still get other error messages as in https://github.com/emersion/go-maildir/issues/12