Age | Commit message (Collapse) | Author | |
---|---|---|---|
2019-10-12 | Add thread deletion | Kevin Kuehler | |
Signed-off-by: Kevin Kuehler <keur@xcf.berkeley.edu> | |||
2019-10-12 | worker/imap: Add threading extension | Kevin Kuehler | |
* Import the go-imap-sortthread library * Add sortthread client to imapClient in worker * Add handleDirectoryThreaded, which uses the go-imap-sortthread, and converts the results to the aerc thread type Signed-off-by: Kevin Kuehler <keur@xcf.berkeley.edu> | |||
2019-05-17 | s/aerc2/aerc/g | Drew DeVault | |
2019-05-13 | Handle incoming emails gracefully | Drew DeVault | |
2019-04-29 | worker/imap: use the IMAP connection from a single goroutine | Simon Ser | |
Unfortunately, the IMAP protocol hasn't been designed to be used from multiple goroutines at the same time. For instance, if you fetch twice the same message from two different goroutines, it's not possible to tell whether the response is for one receiver or the other. For this reason, go-imap clients aren't safe to use from multiple goroutines. This commit changes the IMAP workers to be synchronous again (a command is executed only after the previous one has completed). To use IMAP from different threads, popular clients (e.g. Thunderbird) typically open multiple connections. | |||
2019-03-20 | Implement :delete-message | Drew DeVault | |
2019-03-14 | Implement message store side of message fetching | Drew DeVault | |
2019-03-10 | Fetch valid UIDs from server after opening dir | Drew DeVault | |
2019-01-13 | Issue IMAP SELECT command | Drew DeVault | |