On Tue, Jan 27, 2026 at 08:01:46PM -0500, Kurt Hackenberg wrote:
On Tue, Jan 27, 2026 at 08:41:57PM +0800, Kevin J. McCarthy wrote:

This version accepts any From line that starts with "From " (as long as it has something afterwards.)

I don't know Mutt's code that reads mbox, so I'm probably missing something, but...does something else keep that from accepting an unescaped message line that starts with "From "?

I know of two variants of mbox that don't use Lines: or Content-Length:, and do ">From " escaping of only some message lines, not all of them.

Thanks for the information, Kurt. Previously Mutt just used a strict-ish From line parser to avoid the problem. This patch set definitely opens us up to problems in the cases you mention, and so seems unwise.

I added some code that keeps track of mbox separators in the just committed fix for #415. However that case was trying to improve compatibility when the separator lines were missing. For now it just warns if one is missing, but doesn't error out or make other use of the information.

Maybe this brings us full circle, to either leaving things as they are, or trying out the reverse line scanner to compensate for verbose return paths, and not worrying about the crazier example given. Thoughts, everyone?

--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA

Attachment: signature.asc
Description: PGP signature

Reply via email to