aerc/worker/imap, branch shivesh A pretty good email client (shivesh branch) Implement interface for my custom IMAP flags 2021-10-23T17:37:06+00:00 Shivesh Mandalia mail@shivesh.org 2021-10-23T17:37:06+00:00 5c7d4873908f28dde33013d10543e4cf1417525b 






imap: strip <> from message-ids
2020-11-14T14:40:13+00:00

Reto Brunner
reto@labrat.space

2020-11-08T13:18:14+00:00

daf214a1f8b9ee1f8eabff9b1a2485eceb19cbd0












remove models.Address in favor of go-message Address
2020-11-14T14:40:13+00:00

Reto Brunner
reto@labrat.space

2020-11-10T18:57:09+00:00

fc9ccc30008e564c1dea23b3bfe480ca5a10c070

We made a new type out of go-message/mail.Address without any real reason.
This suddenly made it necessary to convert from one to the other without actually
having any benefit whatsoever.
This commit gets rid of the additional type





We made a new type out of go-message/mail.Address without any real reason.
This suddenly made it necessary to convert from one to the other without actually
having any benefit whatsoever.
This commit gets rid of the additional type







imap: add sort support
2020-10-11T07:18:45+00:00

Reto Brunner
reto@labrat.space

2020-09-12T13:05:02+00:00

b6bcf89784605aa8baa982677de9d8d8ddbaa404












base models.Address on the mail.Address type
2020-08-20T17:18:57+00:00

Reto Brunner
reto@labrat.space

2020-08-19T10:01:45+00:00

c84630714405a1e93766a6a6c023801302a3ea66

This allows us to hook into the std libs implementation of parsing related stuff.
For this, we need to get rid of the distinction between a mailbox and a host
to just a single "address" field.

However this is already the common case. All but one users immediately
concatenated the mbox/domain to a single address.

So this in effects makes it simpler for most cases and we simply do the
transformation in the special case.





This allows us to hook into the std libs implementation of parsing related stuff.
For this, we need to get rid of the distinction between a mailbox and a host
to just a single "address" field.

However this is already the common case. All but one users immediately
concatenated the mbox/domain to a single address.

So this in effects makes it simpler for most cases and we simply do the
transformation in the special case.







Add support for :rmdir
2020-08-19T09:38:57+00:00

ARaspiK
araspik@protonmail.com

2020-08-18T20:27:23+00:00

fe1cabb077cf6c6cb3de122b3f5532acbeba8c85

The `:rmdir` command removes the current directory (`-f` is required if
the directory is not empty).

This is not supported on the notmuch backend.

An issue with the maildir backend is that some sync programs (e.g.
offlineimap) may recover the directory after it is deleted.  They need
to specifically be configured to accept deletions, or special commands
need to be executed (e.g. `offlineimap --delete-folder`) to properly
delete folders.

A danger of using this on the IMAP backend is that it is possible for a
new message to be added to the directory and for aerc to not show it
immediately (due to a slow connection) - using `:rmdir` at this moment
(with `-f` if the directory already contains messages) would delete the
directory and the new message that just arrived (and all other
contents).  This is documented in aerc(1) so that users are aware of
possible risks.





The `:rmdir` command removes the current directory (`-f` is required if
the directory is not empty).

This is not supported on the notmuch backend.

An issue with the maildir backend is that some sync programs (e.g.
offlineimap) may recover the directory after it is deleted.  They need
to specifically be configured to accept deletions, or special commands
need to be executed (e.g. `offlineimap --delete-folder`) to properly
delete folders.

A danger of using this on the IMAP backend is that it is possible for a
new message to be added to the directory and for aerc to not show it
immediately (due to a slow connection) - using `:rmdir` at this moment
(with `-f` if the directory already contains messages) would delete the
directory and the new message that just arrived (and all other
contents).  This is documented in aerc(1) so that users are aware of
possible risks.







Add flag based search options
2020-07-25T06:08:08+00:00

Tobias Wölfel
tobias.woelfel@mailbox.org

2020-07-24T08:36:19+00:00

494bd674a98bc9f2889acad0fda3ff4c77c641b5

Provide search and filter with the option to specify more flag based
conditions.
Use '-x <flag>' to search for messages with a flag (seen, answered,
flagged) and '-X <flag>' to search for messages without a flag.





Provide search and filter with the option to specify more flag based
conditions.
Use '-x <flag>' to search for messages with a flag (seen, answered,
flagged) and '-X <flag>' to search for messages without a flag.







Add additional flagging functionality
2020-07-08T07:13:03+00:00

ARaspiK
araspik@protonmail.com

2020-07-05T14:29:52+00:00

0535f6333f2f5d13469fc315a65c53ff8a5e83f3

More mail flags can now be set, unset, and toggled, not just the
read/seen flag.

This functionality is implemented with a new `:flag` and `:unflag`
command, which are extensions to the matching `:read` and `:unread`
commands, adding support for different flags.  In fact, the
`read`/`unread` commands are now recognized aliases to `flag`/`unflag`.
The new commands are also well documented in aerc(1).

The change mostly extends the previous read/unread setting functionality
by adding a selection for the flag to change.





More mail flags can now be set, unset, and toggled, not just the
read/seen flag.

This functionality is implemented with a new `:flag` and `:unflag`
command, which are extensions to the matching `:read` and `:unread`
commands, adding support for different flags.  In fact, the
`read`/`unread` commands are now recognized aliases to `flag`/`unflag`.
The new commands are also well documented in aerc(1).

The change mostly extends the previous read/unread setting functionality
by adding a selection for the flag to change.







Set AnsweredFlag on successful reply
2020-05-25T15:29:53+00:00

Srivathsan Murali
sri@vathsan.com

2020-05-25T14:59:48+00:00

b1eb7ad18d2e0bbeecaf61a58825bbc794ceb40c












imap: Remove FetchMessageBodyPart.{Encoding,Charset}
2020-05-16T18:03:42+00:00

Reto Brunner
reto@labrat.space

2020-05-16T18:03:42+00:00

bae678e8f20605b64596c9e976623f2a37247adb

Fixes https://todo.sr.ht/~sircmpwn/aerc2/352 exactly as suggested by emersion.





Fixes https://todo.sr.ht/~sircmpwn/aerc2/352 exactly as suggested by emersion.