-Wed Mar 15 14:20:20 2000 Dan Harkless <dan-nmh@dilvish.speed.net>
+Tue Mar 28 16:17:39 2000 Doug Morris <doug@mhost.com>
+
+ * applied Todd Miller's <Todd.Miller@courtesan.com> patch to
+ dropsbr.c to prevent core dumping on packf. Here's the note
+ from his message:
+
+ Since sizeof(buffer) == sizeof(tmpbuffer) packf will dump
+ core on a file w/o a From line with a line >= BUFSIZ.
+ I noticed this because I had a junk file in my mail
+ spool somehow.
+
+Fri Mar 17 11:59:33 2000 Dan Harkless <dan-nmh@dilvish.speed.net>
+
+ * wesley.craig@umich.edu did not document his previous KPOP patch,
+ so I did so, and asked him to check what I wrote. Unfortunately
+ he didn't notice my misunderstanding of his patch. I wrote that
+ if you #define POPSERVICE "kpop", inc and msgchk will use KPOP
+ exclusively, but if you leave it as "pop3", you can use Wesley's
+ new -kpop switch on a given invocation. Instead, however, -kpop
+ turned out to be necessary on every invocation, and a KPOP user
+ complained. Applied Wesley's new patch, which makes things work
+ like I thought his original patch did. After that, did one more
+ clarifying pass to the documentation in inc.man and msgchk.man.
+
+Wed Mar 15 18:45:45 2000 Dan Harkless <dan-nmh@dilvish.speed.net>
* When I fixed the long-standing makedir() bugs in January, I had
the code call strtoul(..., 0), which I believed to be safe as all
"Folder-Protect:" example in the man page to something more
interesting than a duplication of the default.
+ * When I added my --enable-masquerade option, you'll note that I
+ didn't make it --enable-nmh-masquerade. I find the --enable-nmh-*
+ options too wordy and I'm not sure why Richard went that route.
+ I've renamed them to just --enable-*, but the old versions will
+ still work as well (they just aren't advertised).
+
+ * Added a line to the "nmh configuration" output saying whether
+ POP is enabled.
+
+ * Added a new README.developers file. From the file:
+
+ This file is intended to provide a few tips for anyone doing
+ development on nmh. Developers who learn things "the hard
+ way" about the nmh codebase (as opposed to local info best
+ encoded in a comment) are encouraged to share their wisdom
+ here.
+
+ Currently the topics are "autoconf files" and "directory structure".
+
Tue Mar 14 12:41:48 2000 Dan Harkless <dan-nmh@dilvish.speed.net>
* Applied, after some finessing,
projects / mmh / blobdiff