aboutsummaryrefslogtreecommitdiff
path: root/worker/imap/open.go
AgeCommit message (Collapse)Author
2019-10-29Add manual threading to the pipelineKevin Kuehler
Signed-off-by: Kevin Kuehler <keur@xcf.berkeley.edu>
2019-10-29Rework threading and add REFERENCESKevin Kuehler
* Implement a simplified version of the REFERENCES algorithm * Remove FormatThreads function * Instead of acting on all threads, handle each thread independently Signed-off-by: Kevin Kuehler <keur@xcf.berkeley.edu>
2019-10-29worker/imap: Add threading extensionKevin 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-17s/aerc2/aerc/gDrew DeVault
2019-05-13Handle incoming emails gracefullyDrew DeVault
2019-04-29worker/imap: use the IMAP connection from a single goroutineSimon 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-20Implement :delete-messageDrew DeVault
2019-03-14Implement message store side of message fetchingDrew DeVault
2019-03-10Fetch valid UIDs from server after opening dirDrew DeVault
2019-01-13Issue IMAP SELECT commandDrew DeVault