Varac

I get the same, using todays master and python 3: ``` DEBUG:__init__:ARGS: ['reply', '--all'] DEBUG:__init__:cmd parms {'all': True, 'listreply': None, 'spawn': None} DEBUG:envelope:TEMPLATE: None DEBUG:utils:unquoted header: |Re: ...| DEBUG:thread:candidate addresses:...

This is possible a duplicate of #1300

`export PYTHONIOENCODING=utf8` indeed fixed at least my issue I posted earlier (https://github.com/pazz/alot/issues/725#issuecomment-420663653).

> export PYTHONIOENCODING=utf8 indeed fixed at least my issue I posted earlier (#725 (comment)). Oh noes, I was wrong - it did not fix it :/

I could reproduce the `UnicodeEncodeError: 'ascii' codec can't encode character '\xe4' in position 2: ordinal not in range(128)` error by sending this mail to myself, and them trying to group-reply...

@lucc I could reproduce the error with this mail: ``` From: Varac To: Varac Cc: "Värac " Subject: Hello MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Hi! ``` This is...

Once I replace `Cc: "Värac "` with `Cc: "Varac "` the error is gone.

Similar issue with a mail containing a gpg signature from a key that is missing in the keyring: ``` DEBUG:utils:Content-Transfer-Encoding: "7bit" DEBUG:utils:assuming Content-Transfer-Encoding: 7bit DEBUG:utils:Content-Transfer-Encoding: "7bit" DEBUG:utils:assuming Content-Transfer-Encoding: 7bit DEBUG:utils:Content-Transfer-Encoding:...

Just as a reference, msgs with garbled Umlauts in alot display fine with k9mail on android.

Another msg with Umlauts, which displays fine with notmuch but shows garbled Umlauts in alot. I grepped for Content headers: ```  ~ $ notmuch show --format=raw id:[email protected] | grep -i...