norman, sorry for the late response; i didn't find any time for nmh until now...
On Mon, 20 Jan 2020 10:43:19 -0500, Norman Ramsey writes: >I tried forwarding message using `forw -mi`, then telling whatnow to send. >I expected mh_build to be run, as it would have been had I typed >`mime` to whatnow. (This is an improvement that was made a few >versions back.) > The feature worked as expected under Debian 9.11, but stopped >working after a fresh install of Debian 10.2. (A fresh install >was necessary, not an upgrade, because I was migrating from x86 to amd64.) 9 had nmh 1.6.something, 10 has 1.7.something. the NEWS file states that for 1.7 various bugs were fixed, e.g. "mhbuild no longer parses lines that start with # as directives with -nodirectives." in addition to that, automimeproc was removed in 1.6. the man page for forw (and others) was changed to say 'Note that nmh will not invoke mhbuild automatically; you must specifically give the command What now? mime prior to sending the draft.' before it mentioned automimeproc as alternative setup. your profile still sets automimeproc. i do concur that forw -mime, with a plain 'send' at the whatnowproc prompt does not translate #forw... directives; i just tried it with a trivial .mh_profile. however: as far as i can tell that is working as designed! man mh-mime says "All messages sent by send(1) will automatically be processed by mhbuild(1) before being passed to post(1) for message submission." followed by this crucial bit "It is important to note that when using mhbuild directives the user must run mhbuild outside of send to have it process directives; when being run by send, mhbuild is configured to not process directives so normal user text is not mistaken for a directive. When using directives a user typically uses the mime command at the “What now?” prompt to process them." this is related to the removal of automimeproc, which your mh_profile still refers to; and forw -mime, which does indeed generate mhbuild directives; the send manpage mentions that mhbuild is run with -auto, and the mhbuild manpage says that -auto implies -nodirectives. so, in 1.6 this worked because -nodirectives in mhbuild wasn't honored. in 1.7 -nodirectives wins. as far as i can tell from digging through the source, forw -mime will not work unless an explicit 'mime' step is given at the whatnowproc prompt. i cannot see a way anymore to convince whatnow to automate that step - the relevant source commit comment from before the 1.6 release states 'Remove automimeproc functionality; it's redundant now.' but it seems that's not quite the case in the forw -mime scenario. regards az -- Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + http://snafu.priv.at/ The social dynamics of the net are a direct consequence of the fact that nobody has yet developed a Remote Strangulation Protocol. -- Larry Wall
signature.asc
Description: Digital Signature
