aerc/worker/imap, branch master Mirror of https://git.sr.ht/~sircmpwn/aerc remove the dirInfoUpdateRequest functionality 2020-02-29T18:16:33+00:00 Reto Brunner reto@labrat.space 2020-02-29T13:40:52+00:00 f3dbecaaea16fe8956af2bbd29472243f0496995 The notmuch worker followed suit in handling the dirInfo submission manually. That removes the last user so we might as well remove the functionality. 
The notmuch worker followed suit in handling the dirInfo submission manually.
That removes the last user so we might as well remove the functionality.
lib/msgstore: debounce directoryUpdateRequests 2020-02-25T16:05:26+00:00 Reto Brunner reto@labrat.space 2020-02-24T19:18:31+00:00 5dd0f454c197ccbce369ee88d47d5be8cd5e8265 Apparently sending an event for every incoming messageInfo slows down the application significantly. Therefore this slows down the emmision rate, on the cost of being out of date in some cases. 
Apparently sending an event for every incoming messageInfo slows down
the application significantly.

Therefore this slows down the emmision rate, on the cost of being out of date
in some cases.
imap: fix double closing idleStop 2020-02-16T15:41:11+00:00 Reto Brunner reto@labrat.space 2020-02-15T11:37:18+00:00 30c0a9fba471bcd023c8aeebb3901803bb35d31f The idle restart code is at the end of handleMessage in the worker. However if an unsupported msg comes in, we returned early, skipping the re-init. That lead to a crash due to double closing idleStop in the next iteration. 
The idle restart code is at the end of handleMessage in the worker.
However if an unsupported msg comes in, we returned early, skipping the re-init.
That lead to a crash due to double closing idleStop in the next iteration.
imap: emit messageinfo when changing read state. 2020-01-24T15:51:09+00:00 Reto Brunner reto@labrat.space 2020-01-24T11:10:00+00:00 df5d9a3ec7564f0d95e3f92afc0e59588de3c4ce We need to emit the changed msgInfo whenever we modify the state 
We need to emit the changed msgInfo whenever we modify the state
worker/imap: don't decode in FetchFullMessage. 2020-01-19T00:00:02+00:00 Reto Brunner reto@labrat.space 2020-01-18T23:59:20+00:00 472c421e85fafbd2905e785852d04a7c0ab1e60a Doing that breaks `git am` as it expected the encoded variant. Same is probably true for any sort of signature validation (gpg / dkim) 
Doing that breaks `git am` as it expected the encoded variant.
Same is probably true for any sort of signature validation (gpg / dkim)
imap: decode reader prior to returning them 2020-01-05T21:02:45+00:00 Reto Brunner reto@labrat.space 2020-01-04T20:13:52+00:00 3d85f75d9c38d2ddd34325ea4343423c9f3431fb 






decode(RFC 2047) imap headers to fix encoding in subject & filenames
2019-12-07T19:30:33+00:00

Leszek Cimała
ernierasta@zori.cz

2019-12-06T23:06:29+00:00

e84e402e489569b2ab1636ae04016464ec6d46c3

Me again,
this time fixing encoding of subjects and attachments. It was problem in
IMAP backend. While other backends user MessageInfo() function which
generates MessageInfo decoded via go-message methodes, IMAP worker is
creating MessageInfo directly, so all non-utf8 subjects and filenames
were in raw form.

This patch fixes it. Not sure if we should care about errors (if
DecodeHeader fails it returns raw string back).

>From what I see, this should solve all encoding problem (tested only
IMAP). So, now I can focus on features. ;-)

Have a great weekend!
Leszek





Me again,
this time fixing encoding of subjects and attachments. It was problem in
IMAP backend. While other backends user MessageInfo() function which
generates MessageInfo decoded via go-message methodes, IMAP worker is
creating MessageInfo directly, so all non-utf8 subjects and filenames
were in raw form.

This patch fixes it. Not sure if we should care about errors (if
DecodeHeader fails it returns raw string back).

>From what I see, this should solve all encoding problem (tested only
IMAP). So, now I can focus on features. ;-)

Have a great weekend!
Leszek







worker/imap: Fix seqMap race condition
2019-11-10T22:19:23+00:00

Kevin Kuehler
keur@xcf.berkeley.edu

2019-11-10T22:17:55+00:00

8a848303fe0f19fde02793024299356bcdb06048

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>





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>







Fix: oauthbearer runtime error
2019-10-16T15:04:41+00:00

Frode Aannevik
frode.aa@gmail.com

2019-10-13T18:01:16+00:00

550ef0bc1f21dfaeb1bf216b28c3fce9a816cb73

Configure an oauthbearer source without a token_endpoint
parameter would panic due to nil pointer dereference

  Example
    source=imaps+oauthbearer://frode.aa%40gmail.com@imap.gmail.com:993
    source-cred-cmd=pass oatuh2 frode.aa@gmail.com

token_endpoint is not required as it will use the provided
password as access_token when it is not set





Configure an oauthbearer source without a token_endpoint
parameter would panic due to nil pointer dereference

  Example
    source=imaps+oauthbearer://frode.aa%40gmail.com@imap.gmail.com:993
    source-cred-cmd=pass oatuh2 frode.aa@gmail.com

token_endpoint is not required as it will use the provided
password as access_token when it is not set







Change search flags
2019-09-20T19:06:54+00:00

Jeffas
dev@jeffas.io

2019-09-20T16:26:17+00:00

d2a18e267c5d8908377d5a73172bd4313edc4891

This changes the search flags for maildir and imap backends.

They now no longer use -t for searching all text. This seems to make
more sense as being the targeted recipient. I have similarly added Cc
for -c. The text search now resides under -a for all text.





This changes the search flags for maildir and imap backends.

They now no longer use -t for searching all text. This seems to make
more sense as being the targeted recipient. I have similarly added Cc
for -c. The text search now resides under -a for all text.