aerc/commands/compose, branch shivesh A pretty good email client (shivesh branch) send: fix missing error return 2021-02-28T01:05:12+00:00 Reto Brunner reto@labrat.space 2021-02-28T01:04:58+00:00 8cd2485170e97867321fac2f26ba876f377d5d8e 






send: fix crash if invalid password is given
2021-02-05T20:20:17+00:00

Reto Brunner
reto@labrat.space

2021-02-05T20:20:17+00:00

2d2010fd42708885f0da85835ce368dd1329e844












Get rid of the aerc.PushError(" " + $string) idiom
2021-01-30T13:04:23+00:00

Reto Brunner
reto@labrat.space

2021-01-30T12:51:32+00:00

8ea86cea41aa038a25a8fee9cd540a7336869dae

The individual callers should not be responsible for padding





The individual callers should not be responsible for padding







send: don't block the UI thread during the sending
2021-01-24T17:00:23+00:00

Reto Brunner
reto@labrat.space

2021-01-24T17:00:23+00:00

9385827cae7bab6534933718d21eeb489448c476












Refactor send command
2020-11-21T14:40:50+00:00

Reto Brunner
reto@labrat.space

2020-11-11T22:50:35+00:00

67923707ffd826ad1d02c0a5b5ebd75ffbc71364












allow the loading of existing headers
2020-11-14T14:40:13+00:00

Reto Brunner
reto@labrat.space

2020-11-08T12:39:25+00:00

256af6322b1c219b56997b37a0c69070b53bcc86












format: remove parse methods, use the one from go-message
2020-11-14T14:40:13+00:00

Reto Brunner
reto@labrat.space

2020-11-10T19:35:47+00:00

24f1c575ae7941fa4239ec60bd86aef2f6641364












compose: use a proper header instead of a string map
2020-11-14T14:40:13+00:00

Reto Brunner
reto@labrat.space

2020-11-10T19:27:30+00:00

20ec2c8eeb2e071f28358814935a0f56672a9f49

Prior to this commit, the composer was based on a map[string]string.
While this approach was very versatile, it lead to a constant encoding / decoding
of addresses and other headers.

This commit switches to a different model, where the composer is based on a header.
Commands which want to interact with it can simply set some defaults they would
like to have. Users can overwrite them however they like.

In order to get access to the functions generating / getting the msgid go-message
was upgraded.





Prior to this commit, the composer was based on a map[string]string.
While this approach was very versatile, it lead to a constant encoding / decoding
of addresses and other headers.

This commit switches to a different model, where the composer is based on a header.
Commands which want to interact with it can simply set some defaults they would
like to have. Users can overwrite them however they like.

In order to get access to the functions generating / getting the msgid go-message
was upgraded.







propagate error from sendmail
2020-09-22T06:12:38+00:00

y0ast
joost@joo.st

2020-09-20T21:53:44+00:00

42ce6b41ff7ff56f89de25e4807ab30c6eef4662












Add `oauthbearer` support for SMTP
2020-08-13T05:44:43+00:00

R Chowdhury
necaris@gmail.com

2020-05-26T11:29:58+00:00

f4dc7e1f746582d42462ec56347dd354756203b0

This piggybacks on the existing IMAP support, and uses the same
configuration format (my local testing example has the IMAP and SMTP
lines almost copy-pasted from one another).

It's a little clumsy in that a new token is negotiated for every
`Send()` command, but it's a start...





This piggybacks on the existing IMAP support, and uses the same
configuration format (my local testing example has the IMAP and SMTP
lines almost copy-pasted from one another).

It's a little clumsy in that a new token is negotiated for every
`Send()` command, but it's a start...