Re: abook add email from mutt with name containing accent

[Xu Wang]

On Sat, Mar 5, 2016 at 2:26 PM, Andreas Doll  wrote:
> On 2016-03-05 at 01:16, Xu Wang wrote:
>> Does anyone else have a problem to use "A" to call abook to add the
>> sender's name and email as an entry if that name has an accent? For me
>> the name receives a strange questionmark and some gibberish. The name
>> displays fine in mutt so It think I have utf8 configured.
>
> Yes, I can confirm this. However, the "gibberish" is the encoding of non-ascii
> characters, compare [1], so this affects also names containing e.g. Umlaute 
> [2].
>
> Example: =?utf-8?B?Q2zDoXVkaW8gR2ls?=
>
>$ python
>>>> from base64 import *
>>>> sender = 'Q2zDoXVkaW8gR2ls'
>>>> print b64decode(sender).decode('utf-8')
>
> should give you the correct sender name with accents.
>
> Thus I'd say the fault is on abooks side, which doesn't perform the necessary
> decodings.  Maybe you want to file an issue there.

Thank you for this analysis! It is good to know I am not the only one.
I am not planning to make bug report because I do not know how to make
minimal example. I think minimal example would only use abook but I
only use abook through mutt.

Kind regards,

Xu

Re: gpgme: ambiguous specification of secret key

[Gregor Zattler]

Hi Kevin, mutt users,
* Kevin J. McCarthy  [02. Mar. 2016]:
> On Wed, Mar 02, 2016 at 11:52:22PM +0100, Gregor Zattler wrote:
>> * Kevin J. McCarthy  [01. Mar. 2016]:
>>> Mutt is seeing more than one result when querying for secret keys
>>> matching that fingerprint.  When it gets the second result back from
>>> gpgme, it's aborting with that error.
>>> 
>>> What does `gpg2 --list-secret-keys 0xB55` show?
> 
> [output from two different keyrings]
> 
>> Urghs! The secret key is in public keyring!?
> 
> I believe that's normal for gpg2 output (although is certainly
> confusing).
> 
> What's probably causing the problem is the matches in both "pubring.gpg"
> and "import-zu-sortieren-keyring.gpg".  Are you intentionally using both
> keyrings?  If so, one solution would be to (carefully) remove your key
> from one of those keyrings.

Thanks a lot, I did as you said and now it works again.  


Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-

Re: abook add email from mutt with name containing accent

[Andreas Doll]

On 2016-03-05 at 01:16, Xu Wang wrote:
> Does anyone else have a problem to use "A" to call abook to add the
> sender's name and email as an entry if that name has an accent? For me
> the name receives a strange questionmark and some gibberish. The name
> displays fine in mutt so It think I have utf8 configured.

Yes, I can confirm this. However, the "gibberish" is the encoding of non-ascii
characters, compare [1], so this affects also names containing e.g. Umlaute [2].

Example: =?utf-8?B?Q2zDoXVkaW8gR2ls?=

   $ python
   >>> from base64 import *
   >>> sender = 'Q2zDoXVkaW8gR2ls'
   >>> print b64decode(sender).decode('utf-8')

should give you the correct sender name with accents.

Thus I'd say the fault is on abooks side, which doesn't perform the necessary
decodings.  Maybe you want to file an issue there.

Best regards,
Andreas

[1]http://stackoverflow.com/a/454848
[2]https://en.wikipedia.org/wiki/Germanic_umlaut

Re: using Mutt to read mail server

[Erik Christiansen]

On 04.03.16 22:21, James Freer wrote:
> Most email clients don't allow this reading the imap server without
> downloading headers. Does Mutt and how easy is it to set up? I've
> downloaded the Woodnotes Guide to Mutt... and I must admit I am
> finding it hard going.

Leaving mail on the server is not something that I have ever tried,
but I am finding it difficult to imagine how mutt (or any MUA) could
provide the index if it did not at least fetch headers.

Are you looking for an MUA which presents only one line of interface:

Number of unread emails: 472 NEXT

It would certainly be quick, and simple to use, but being unable to see
what the inbox contains, or read out of sequence, seems a high price to
pay.

So long as one is not so delinquent as to leave anything but today's
mail in the inbox (plus maybe one or two from yesterday, not yet
handled), it would take a very large daily flood to make starting slow,
I suggest.

Erik