The topic of the status of nmh has come up a few times in the last
several months. I'd like to bring it up again, because it doesn't
appear that its going anywhere.
My motivation is that I've come across a few things I'd like to see
fixed in nmh, and I've had some free time recently, so I'm ready to
work on some of them. However, I don't want to waste my effort, if
nmh development is truly dead.
Here's what I'd like to work on:
- msh doesn't support mbox files, only mmdf. Its in the todo file,
and looks like a relatively simple feature
- I got an email this week that nmh can't parse. First time I've
seen that in the several years I've used nmh. The problem is that
the email has some corrupt headers:
-Envelope-From: [EMAIL PROTECTED]
-Envelope-To: <[EMAIL PROTECTED]>
(ie, missing X... very strange) nmh stops parsing the headers at
this point, and scan shows it like:
3 05/01*
I think there was one more issue I wanted to look at, but its escaped
me right now.
In any case, who has CVS access to mhost? Does anyone have access to
the actual CVSROOT? Someone (ken maybe) mentioned that he was having
openssh issues getting to the repository... maybe we can help you get
that resolved? If we can get access to the cvsroot, I don't see why
this can't be maintained by committee for a while, until a natural
maintainer steps forward.
Scott
PS: this didn't go through the first time - I posted using the wrong email
address. Since then, I got another corrupt email (with the -Envelope
headers). I don't know what is corrupting them, but both are from the same
sender, to two different mailing lists (SPAM-L and nanog) He appears to be
using pine, judging from the message-id.
