bug removed by ~srivathsan on ~sircmpwn/aerc2
maildir removed by ~srivathsan on ~sircmpwn/aerc2
Comment by ~srivathsan on ~sircmpwn/aerc2
Sorry turns out, It was due to some rogue mail that was failing. Not because of utf-8 encoding.
REPORTED RESOLVED INVALID
maildir added by ~srivathsan on ~sircmpwn/aerc2
bug added by ~srivathsan on ~sircmpwn/aerc2
Comment by ~srivathsan on ~sircmpwn/aerc2
I used the IMAP worker to test, the error doesn't occur. I think the error is specific to the maildir worker. Will dig a bit deeper on how to fix this.
Ticket created by ~srivathsan on ~sircmpwn/aerc2
Searching a mail directory fails with the following error: ''' 2019/11/19 08:41:06 could not get envelope: could not read from address: mail: unclosed angle-addr '''
Searching through, it seems like the problem is unicode normalization. Some From addresses are utf-8 encoded and net/mail package doesn't do unicode normalization.
It would great to implement unicode normalization from aerc's side. I would like to take a stab at this but I am unsure, I would need to make these changes. Would it be part of the search function of the worker as, the message viewer properly decodes the encoded addresses.
I use mbsync to sync my outlook IMAP server and use the maildir worker in aerc.
Comment by ~srivathsan on ~sircmpwn/aerc2
Great. Will take a look into it when I have some time. Maybe I can work on the list view for completion as the mechanism is availble from your patch.
Comment by ~srivathsan on ~sircmpwn/aerc2
Is the plan for this ticket to add Carddav support to Aerc or itergrate with an existing tool.
Personally, I would like to have an integration with external tools to access the address book, either through CardDav or abook which stores the addresses locally.
I seem to be looking into old tickets, I am not sure if this is already resolved through some other means.
Comment by ~srivathsan on ~sircmpwn/aerc2
I would like to take a stab at implementing this as this would be quite useful for me :D So I have two ways I can think of implementing this: 1) Implement this as part of buildBody in commands/account/compose.go. 2) Implement it as part of the composer in widget/compose.go similar to the signature file. This would make it available for reply and forward too. Any comments on which method to go for?