aboutsummaryrefslogtreecommitdiffstats
path: root/worker/imap/open.go
Commit message (Collapse)AuthorAgeFilesLines
* imap: add sort supportReto Brunner2020-10-111-2/+47
|
* worker/imap: Fix seqMap race conditionKevin Kuehler2019-11-101-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/gDrew DeVault2019-05-171-1/+1
|
* Handle incoming emails gracefullyDrew DeVault2019-05-131-0/+3
|
* worker/imap: use the IMAP connection from a single goroutineSimon Ser2019-04-291-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-messageDrew DeVault2019-03-201-0/+1
|
* Implement message store side of message fetchingDrew DeVault2019-03-141-7/+2
|
* Fetch valid UIDs from server after opening dirDrew DeVault2019-03-101-0/+34
|
* Issue IMAP SELECT commandDrew DeVault2019-01-131-0/+20