Hi,
I've completely unified my mutt config for several accounts and while
it works very well, I cannot easily tell which account I'm connected
to at the moment, and might not remember (yet) which macro switches to
which account. The imap accounts generally just show "=INBOX" in the
index status
> You could try something like:
>
> folder-hook . 'set status_format="-%r-Mutt: [$folder] %f [Msgs:%?M?%M/?%m%?n?
> New:%n?%?o? Old:%o?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b?
> Inc:%b?%?B? Back:%B?%?l? %l?]---(%s/%?T?%T/?%S)-%>-(%P)---"
>
> This technique also allows using
Hi all,
I've come across what I believe is an inconsistency in message forwarding.
It seems that encrypted and non-encrypted messages are treated differently.
When I forward a full message as "message/rfc822", I expect the same result,
regardless of encryption status.
With current settings,
set
Kevin J. McCarthy writes:
> On Thu, Jun 09, 2022 at 09:05:47AM -0700, Kevin J. McCarthy wrote:
> >I won't have time to investigate until this weekend, but it looks like
> >this is an issue with encrypted S/MIME. The forward handler is always
> >specifying to decode.
> >
> >There *is* code to
> I recently hit a similar issue on Gentoo when I tried building Mutt
> using GnuTLS (forgot to note down the versions, but I think it was Mutt
> 2.2.3 and GnuTLS 3.7.8 according to Portage logs). I backed out when I
> saw the "accept cert" prompt, though, since I wasn't sure how to
> proceed,
This is more of a heads-up as the problem isn't in mutt per se.
A while back, mutt stopped working correctly for me on OpenBSD, and of
course, I completely failed to take notice at which point and with which
release exactly ...
What is the problem? When you connect to a server for the first
