Richard Russon

Results 317 comments of Richard Russon

**Merged**: - https://github.com/neomutt/upstream-mutt/commit/4cec4b63 mutt_parse_content_type: work around annoying charset behaviour from Outlook - https://github.com/neomutt/upstream-mutt/commit/ab9b7b08 Ensure APP_PGP flag is enabled for autocrypt - https://github.com/neomutt/upstream-mutt/commit/ef7e5e42 Fix sigwinch race in the index and menu...

Hi @orglube. In your config, you're using two different abbreviations: (see [Mailbox Shortcuts](https://neomutt.org/guide/advancedusage.html#shortcuts)) - `!` which is replaced with the value of `$spoolfile` - `+` / `=` which are both...

hmm... strange For Maildir mailboxes, NeoMutt is looking for `cur`, `new` and `tmp` subdirs. Can you check they exist

Hmm... That seems reasonble. As you've no doubt discovered, all the pieces are already in place for IMAP: - `postpone_message()` - `mutt_write_fcc(draft)` - `mx_msg_open_new(MUTT_SET_DRAFT)` - `mx_msg_commit()` - `imap_msg_commit()` This uses...

> Sender is part of rfc2822 as far as I'm aware Yep: 3.6.2. Originator fields https://datatracker.ietf.org/doc/html/rfc2822#section-3.6.2 We store the sender: https://github.com/neomutt/neomutt/blob/010b06f30a0335d32ec78101a9e4ea548a96cf1c/email/envelope.h#L61 And though we talk about the 'sender' in `hdrline.c`...

After a bit of discussion on IRC... It seems that `%f` prints all of the from addresses, whereas `%F` prints a single address. Altering `make_from()` will probably work. https://github.com/neomutt/neomutt/blob/d97a9700899b80eb3a89f996d0d3dbf5a0dbc834/hdrline.c#L223

Hmm... this isn't looking good. The problem goes back a long way. I've made a quick, inconclusive, attempt to bisect. | Bisect | Hash | Description | | :----- |...

> Meanwhile `mutt` already uses gsasl. Just sayin' Yeah, it's new and not well tested. > This should make it easier to backport I've merged the upstream GNU SASL support....

~**Note**: some of the builds are failing because the Docker image doesn't have gsasl installed~ Fixed

> I'll dig into it. Thanks! I'll have another look over the code too (and compare it to upstream)