Here are some changes to nmh I've made over the past couple of days which
may be of interest:

  Wed Jan 26 02:22:00 2000 Dan Harkless <[EMAIL PROTECTED]>

          * Added documentation on both types of masquerading to post's man
          page.

  Tue Jan 25 22:58:12 2000 Dan Harkless <[EMAIL PROTECTED]>

          * Doug's portability fix of my setgid inc autodetection had a
          caching bug -- if you re-ran configure, uip/Makefile would be
          corrupted, and installation would bomb out on OSes where inc needs
          to be setgid.

          * Implemented a new kind of email address masquerading.  When a
          user writes a custom "From:" header in a draft, nmh uses it rather
          than generating one.  However, the user's true address is used in
          the SMTP envelope "From:" and is revealed in the "Sender:" header.
          Now, when mmailid is set to non-zero, the envelope "From:" uses
          the address specified in the draft "From:" header, and there is no
          "Sender:" header.  This is useful when sending on behalf of a
          remote POP3 account or when remote mail robots incorrectly use the
          envelope "From:" in preference to the body "From:".  This
          processing has only been implemented for post, not for the
          undocumented spost (which was already missing some "From:"
          processing that post has).

  Mon Jan 24 22:26:06 2000 Dan Harkless <[EMAIL PROTECTED]>

          * Got rid of the rest of the gcc -Wall warnings that I didn't have
          time for on 1999-07-15 (and, it would seem, some new ones people
          introduced since then).  The primary ones were the warnings that
          default prototypes were being used for [v]snprintf() and
          str[n]casecmp().  As of right now, there are _no_ compilation
          warnings except on dtimep.c-lexed (at least under AIX 4.1.5 and
          Solaris 2.6).

The configure bug (which went out in 1.0.2) is kind of worrisome.  It took
me a lot of head-scratching to figure out what was going on, and without a
basic understanding of autoconf, it would have taken a lot longer.  We
should probably think about releasing a 1.0.3 before too long.

-----------------------------------------------------------------------
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.     

Reply via email to