| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
we check whether a key is
- revoked
- expired
- invalid
- unable to encrypt
- unable to sign
|
| |
|
|
|
|
|
| |
sometimes if gpgme doesn't find a key it gives INVALID_VAL sometimes EOF, we now
handle both
|
|
|
|
|
| |
If all the encryption keys are deleted from the encryption list set the encrypt
flag in the enveleope to false
|
|
|
|
|
| |
if the user doesn't supply encrypt with a list of encryption keys, the email
addresses of the email recipients are used
|
|
|
|
|
| |
We use an own has function for that, since pygpgme doesn't implement __cmp__()
or similar
|
|
|
|
|
|
|
|
| |
Multiple recipient-keys can be specified. They are shown in the envelope buffer.
A new command is introduced: 'rmencrypt' do remove a key from the encryption
lsit. Unfortunately pygpgme doesn't implement __cmp__() so we have to either
write something similar on our own or use this solution (index of the key in
encryption list)
|
|
|
|
|
| |
It is more useful if we check wether the key is available directly when the user
ask for encryption, rather than doing it before sending it
|
| |
|
| |
|
| |
|
|
|
|
|
| |
We now can define the key, we want to encrypt with as parameter of the encrypt
command
|
|
|
|
|
| |
The encrypt command sets the encrypt flag of an envelope, which we will use to
later encrypt a message
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
... after external processes terminate.
fixes #566
|
| |
|
|
|
|
|
|
| |
by keeping a "was locked" flag in the UI.
Once changes are successfully flushed, we use a single "all clear"
notification.
|
|\
| |
| |
| |
| | |
Conflicts:
alot/commands/thread.py
|
| |
| |
| |
| | |
... which has been accidentally removed before
|
| | |
|
| |
| |
| |
| |
| |
| | |
these now support an `--all` parameter that allows to tag
all messages in the (search) result set instead of just
all in the selected thread.
|
| | |
|
| |
| |
| |
| |
| | |
- tries to omit code dupication,
- refresh issue
|
| |
| |
| |
| |
| | |
The user can only ever set the target string via a command parameter,
which is sanitizd by argparse as we use choices..
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
... and rename it to determine_sender:
This repects the previously introduced new config flags
for reply/forward/bounce.
The respective commands now use this helper accordingly.
|
| | |
| | |
| | |
| | | |
cf issue #524
|
| | |
| | |
| | |
| | | |
... being a string/email.message.Message.
|
| |/
| |
| |
| |
| | |
... to directly send a mail without the need for
an envelope buffer to be open.
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
... when replying/forwarding mails.
This now respects the new reply_force_realname and reply_force_address
config options and uses regex to match recipients with ones own addresses.
This way one can define aliases matching "plussed" recipient addresses
like this:
[accounts]
[[gmail]]
realname = Patrick Totzke
address = patricktotzke@gmail.com
aliases = patricktotzke@googlemail.com, patricktotzke\+.*@gmail.com
cf issue #515
|
|
|
|
|
| |
This also adds a new config option `compose_ask_tags`
that defaults to False.
|
|
|
|
| |
that contains tagstrings to add to message after successful sendout
|
|
|
|
|
| |
instead of only completing addresses and afterwards looking up a
matching account
|
| |
|
|
|
|
|
|
|
| |
... in CallCommand.
This makes it possible to use `call "hooks.myfunc()"`,
where my_func makes use of the UI instance (and settings)
by referencing to `ui` (and `settings`).
|
|\ |
|
| |
| |
| |
| |
| | |
.. after external commands that reuse the terminal.
cf issue #506
|
| | |
|