I just wrote:
> Finally, inspired by your idea, I added an --enable-masquerade option to
> configure. Any subset of "draft_from mmailid username_extension" may be
> specified, and the values will be written to the "masquerade:" line of
> mts.conf. As a shortcut, --enable-masquerade can be specified without any
> values to enable all three types.
I forgot to point out that I didn't call my option --enable-nmh-masquerade.
I fail to see the value in putting "-nmh" in every --enable option and I'm
not sure why Richard went that route. I'd almost be in favor of renaming
the old options to --enable-debug --enable-mhe --enable-pop, but I'm sure a
lot of people already have their brains hardwired to type --enable-nmh-*.
And of course autoconf'd configure scripts have that annoying bug/feature
where you don't even get a warning if you specify nonexistent commandline
options, so renaming the options could cause a lot of gnashing of teeth
before people got used to the new versions...
I may have caused some heartache by not calling my option
--enable-nmh-masquerade, in fact. Even though the option is new, people may
type --enable-nmh out of habit.
If anyone has any good reasons why all the --enable options should be
--enable-nmh-*, please post.
-----------------------------------------------------------------------
Dan Harkless | To prevent SPAM contamination, please
[EMAIL PROTECTED] | do not post this private email address
SpeedGate Communications, Inc. | to the USENET or WWW. Thank you.
