Well, if you can reproduce it locally it would be helpful to actually debug the code (and then fixing it ;) )
If you don't want to do that, you can get logs by redirecting stdout to a file
aerc > aerc.log
Does this always happen or only sometimes?
You can always remap a key to
Aerc does do the right thing (setting the delete flag and expunging) for imap.
Which backend do you use and which email provider if it's IMAP?
Outlook's exchange server has various issues
~mmf you can already hide folders, although currently it's only a whitelist. We should extend this in a way that also has negation (say!archive).
The dirlist is worker agnostic so there's no need to go deeply into that.
To be fair, adapting a notmuch based workflow means you'll have to change your habits quite a bit.
But as far as aerc is concerned
man aerc-notmuchThe rest, google notmuch
Your issue is that in order for things like sorting to work aerc parses all mails in the folder and this, well, takes a while for 200k mails.
You should see a similar effect in say neomutt
You really should set up notmuch and limit by time.... there's no way you'd ever want to look at that many messages at the same time
On Sat, Nov 16, 2019 at 01:46:50PM -0000, ~tmplt wrote:
Would that be just
outgoing = /path/to/msmtp?
Well, depends on what you want to do. I've set mine to
outgoing = /bin/msmtp --read-envelope-from
Am I missing something?
msmtp already works,
Also you can probably hack up a script and plug it into
outgoing-cred-cmdthat does the token exchange
I was under the impression that most, if not all, MUAs set it.
That's the second thing I turn off. Right after the $#@& signatures likesent from my iPhoneand the like
I'd rather not have that on by default... I hate it if tools do that.
Instead of that, I'd rather see the capability to add arbitrary header to outgoing emails (maybe via the templates?)
So that allows people to set such a header if they really want to do that