Eric Wong wrote:
> > -fmt = "<%z@%f>";
> > +fmt = "<%Y%02m%02d_%02H%02M%02S_%r%r@%f>";
>
> Kinda shocked that the %02's are necessary for a user-facing
> config file, but yes, it's a much more reasonable default with
> t
Sebastian Andrzej Siewior wrote:
> On 2023-03-07 08:43:38 [+], Eric Wong wrote:
> > Thanks Kevin. Any chance you can restore the %Y%m%d%H%M%S prefix?
> >
> > I brought this up here in a patch <20210110213922.iqTO594q5DM@dcvr>.
>
> couldn't fine this
"Kevin J. McCarthy" wrote:
> On Sat, Mar 04, 2023 at 06:33:33PM +0100, Sebastian Andrzej Siewior wrote:
> > #2 of this mini series uses the safe dictionary for base64 encoding to
> > use for message-id generation. This bothered me for a while and then I
> > stumbled uppon issie #400 so it appears
ilf wrote:
> Eric Wong:
> > Without opening the above URLs, you can immediately tell it's from April
> > 6, 2016.
>
> Message-IDs are not supposed to be human-meaningful:
> https://tools.ietf.org/html/rfc5322#section-3.6.4
That does not change the fact that
Derek Martin wrote:
> On Sat, Jan 09, 2021 at 10:54:28PM +0000, Eric Wong wrote:
> > Hi Remco,
> >
> > So I'm looking at 9da4e6e11e7037668d0ca7e8f5d6773d26e379ac
> > (I noticed this in mutt 2.0.2 on FreeBSD)
> >
> > This is a bad change
>
>
When citing URLs for messages in public mail archives,
the mmddHHMMSS provides crucial information to readers
which can be useful without having to open the cited URL.
Since these messages are cited by others from a public mail
archive (e.g. in commit messages), they are likely legitimate
and
Remco Rijnders wrote:
> On Sat, Jan 09, 2021 at 10:54:28PM +, Eric wrote in
> <20210109225428.GA27462@dcvr>:
> > This is a bad change for public mail archives which use
> > https://$SOMETHING_SOMETHING/$MSGID for robustness across
> > different public mail archives and hosts.
>
> > Having the
Hi Remco,
So I'm looking at 9da4e6e11e7037668d0ca7e8f5d6773d26e379ac
(I noticed this in mutt 2.0.2 on FreeBSD)
This is a bad change for public mail archives which use
https://$SOMETHING_SOMETHING/$MSGID for robustness across
different public mail archives and hosts.
Encoding mmddHHMMSS into
"Kevin J. McCarthy" wrote:
> On Mon, Jun 08, 2020 at 08:23:37PM +0000, Eric Wong wrote:
> > Subject: why does mutt still use MSNs for IMAP?
>
> Well, we use MSNs to handle EXPUNGE and EXISTS responses. They are used to
> fetch non-cached message headers when opening
Hey all,
I'm a long-time mutt user and I'm implementing a read-only IMAP
server for public-inbox. It's my first time writing an IMAP
server.
I'm seeing mutt still issues plain (MSN) "FETCH" for
"BODY.PEEK[HEADER.FIELDS" and it does something with MSNs for
its header cache.
This is a bit confusi
Thomas Roessler wrote:
> If I think about the single most critical feature that makes today's
> mail volume manageable for me (other than priority inbox), then it's
> conversation view: The ability to page through an entire mail thread
> quickly without having to go back to the index view, and wit
11 matches
Mail list logo
