about summary refs log tree commit diff stats
path: root/worker/imap/fetch.go
Commit message (Collapse)AuthorAgeFilesLines
* Update our message flags when server updates themDrew DeVault2019-06-091-2/+22
|
* Fetch headers w/peek to leave emails unreadYash Srivastav2019-06-081-0/+1
|
* implements ability to view headers in message viewYash Srivastav2019-06-071-1/+20
|
* Don't send Done until finished fetching messagesDrew DeVault2019-06-021-0/+3
|
* Flesh out multipart switcherDrew DeVault2019-05-201-1/+1
|
* s/aerc2/aerc/gDrew DeVault2019-05-171-1/+1
|
* worker/imap: use the IMAP connection from a single goroutineSimon Ser2019-04-291-41/+37
| | | | | | | | | | | | | 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.
* Make message viewer real, part twoDrew DeVault2019-03-311-11/+14
|
* Rename FetchMessageBodies to FetchFullMessagesDrew DeVault2019-03-311-10/+10
|
* Make the message viewer real, part oneDrew DeVault2019-03-311-6/+26
|
* Don't parse mail in worker; send a reader insteadDrew DeVault2019-03-311-10/+2
|
* Pull BodyStructure up from IMAP workerDrew DeVault2019-03-311-4/+6
|
* Add body fetching support codeDrew DeVault2019-03-291-15/+46
|
* Implement :delete-messageDrew DeVault2019-03-201-0/+1
|
* Display message subjects in message listDrew DeVault2019-03-141-0/+46