On Fri, Apr 19, 2024 at 03:41:40PM -0400, Derek Martin wrote:
On Fri, Apr 19, 2024 at 09:05:23AM -0700, Will Yardley wrote:
It's odd to me that, since OpenPGP and S/MIME both support MIME
encapsulation that the draft standard wouldn't use a separate MIME part
to handle the protected headers vs.
On Thu, Apr 18, 2024 at 06:37:50PM +0200, Alejandro Colomar wrote:
I reported around a month ago a couple of security vulnerabilities to
neomutt(1), but which are also present in mutt(1) and every MUA
So the main security vulnerability is that a recipient can tamper with
header fields, and th
On Wed, May 24, 2023 at 06:29:31PM +0200, Olaf Hering wrote:
I just had the case "Message-Id: something" in one email, and
"References/In-Reply-To: " in replies.
As a result mutt failed to recognize that both mails are indeed one
single thread.
I just looked at the current Mutt source (rele
On Sun, Jul 31, 2022 at 01:47:06PM -0400, Kurt Hackenberg wrote:
>I agree there should not be a space after the '>'. The trouble is,
>that space is ambiguous: software can't tell whether it's part of the
>quoting or part of the original message.
I spoke too s
On Mon, Aug 01, 2022 at 04:08:27PM +0200, ilf wrote:
>IMHO both "> > foo" and ">> foo" are bad, it should be ">> foo".
What? The last two are the same.
On Sun, Jul 31, 2022 at 06:09:56PM +0200, Thomas Wei??schuh wrote:
>currently mutt always prepends `$indent_string` verbatim to each line when
>quoting messages.
>When quoting parts of messages that themselves already were quoted this leads
>to additional space characters in addition to the quote
I agree with the proposed change, to reply to an empty Subject: with
just "Re:" (or whatever, if that reply-marking string is configurable).
My taste says that an empty or absent Subject: is valid, and should not
be forbidden or "corrected".
On 2020-05-06 15:32, Claus Assmann wrote:
On Wed, May 06, 2020, Kevin J. McCarthy wrote:
I suspect this is the contention point for opensmtpd. When invoking
$sendmail directly the headers and delimeter are all just LF. Is this
expectation that the MSP perform conversion documented anywhere?
On 2019-06-23 06:31, Vincent Lefevre wrote:
...the provided "Lines:" header is not necessarily reliable.
Right. I've seen it wrong many times.
Not from Mutt--when Mutt writes a message to an mbox file, it generates
Lines: and Content-Length:, both correctly. But Mutt is not the only
program
On 2019-06-22 16:47, Vincent Lefevre wrote:
The manual says:
%l number of lines in the message
(does not work with maildir, mh,
and possibly IMAP folders)
Seems not very useful if it
10 matches
Mail list logo
