Re: Support for flat MH mailboxes

--ZcM+7j7D1yUr3yDf
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jul 13, 2026 at 10:37:46AM +0200, Olaf Hering via Mutt-dev wrote:
>Recently Claws Mail stopped to maintain ".mh_sequences" per default.
>As a result a mailbox became just a flat directory with individual
>numbered messages in it. There is a knob to restore the old behavior.
>
>I wonder what it would take to support also that flat MH format.
>Currently mx_is_mh() checks for certain file names, and assumes
>the given directory is of format MH. Other functions write to a fixed
>sequence file name, even if mx_is_mh() found some other name.

Hmmm... I haven't really spent much time in the mh code since I became=20
maintainer.  It's "just worked" and hasn't been problematic.  :-/ So,=20
I'm not sure how much work it would take.

A fair amount of code is devoted to reading and updating the=20
=2Emh_sequences file, though, so I don't think it's an easy swap.  Aren't=
=20
some flags stored in the .mh_sequences file too?

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

--ZcM+7j7D1yUr3yDf
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEiXWpszqjeRA4XFMIre92hIAxa9oFAmpVpNsACgkQre92hIAx
a9oz7g//Ygv40EhDtveGXNI8DuLXu/U0xx9hnqJI1INcXcgXrS1JtmO8OcHxtrHz
Smj7zJYtiAtfA+iC50aEhzuZ2RWCSU+bHGyB5x5zZD36ZyNIMexAR297GrRtJOo+
9Wbrc8VKiD9oRO2KVzjbRwAFAi5+PdygUWcM1JBUiLU8kIBB3oSh2bORBA36SAeq
OfGGe28iJmsjbFtjCPMgDKffkCpHiXyx7BJfYGarM2/Ac2lP65LD37Cr5iYRtXOq
kYBwZjzPKKQm4j7UoCYSkZdIVsMg1gvbI4BsEyThaFb4wcf59IbUzb4yCgr/HV3S
5SSDzk/+nXzx1v3B0c+wkM6sV9x57X3W3DfOJV+zxzT6rKl07TI00zVf/hIGpPSb
pmHEbMqIqmYureF6Wjb0hsEExHkj/A5I+9cZELJ/mGzxIJ/S0lL0AWs6Z5e6Pw0L
hPHdEGHchLm6iEziA8EP+Bx3u21g+Ny729NkamEXXARY/F3pranXx4SgLeOsih0K
7RrqDXpgnj34AkwfNpJroDvF41fNHKBf1/N7y9w3w89oY5SK/bT5oJQ3naUO7uUy
+kJ2tuQ7j2SO//vCPCBEeWYhG7WPou7PrDAyp776jCI7P1qdVW29vtW9m+85TVb8
LHdJ59mjibvAVqQ0KUl00bDNOHs6p48gGkQwj3sbLbdBkASGaVk=
=bSgT
-----END PGP SIGNATURE-----

--ZcM+7j7D1yUr3yDf--