| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | worker/imap: Fix seqMap race condition | Kevin Kuehler | 2019-11-10 | 1 | -1/+3 |
| | | | | | | | | | | | When deleting a message, sometimes FetchDirectoryContents will fire. FetchDirectoryContents will return a smaller set of UIDs since messages have been deleted. This operation races with fetching from the seqMap in client.ExpungeUpdate. Only recreate the seqMap if it can grow so that messages will continue to be expunged. Signed-off-by: Kevin Kuehler <keur@xcf.berkeley.edu> | ||||
| * | s/aerc2/aerc/g | Drew DeVault | 2019-05-17 | 1 | -1/+1 |
| | | |||||
| * | Handle incoming emails gracefully | Drew DeVault | 2019-05-13 | 1 | -0/+3 |
| | | |||||
| * | worker/imap: use the IMAP connection from a single goroutine | Simon Ser | 2019-04-29 | 1 | -32/+29 |
| | | | | | | | | | | | | | | 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. | ||||
| * | Implement :delete-message | Drew DeVault | 2019-03-20 | 1 | -0/+1 |
| | | |||||
| * | Implement message store side of message fetching | Drew DeVault | 2019-03-14 | 1 | -7/+2 |
| | | |||||
| * | Fetch valid UIDs from server after opening dir | Drew DeVault | 2019-03-10 | 1 | -0/+34 |
| | | |||||
| * | Issue IMAP SELECT command | Drew DeVault | 2019-01-13 | 1 | -0/+20 |