[9121] in Athena Bugs
Re: [Roger A. Roach : Multiple Bug Lists]
daemon@ATHENA.MIT.EDU (Jeffrey I. Schiller)
Tue Mar 24 23:08:00 1992
Date: Tue, 24 Mar 92 23:07:26 -0500
From: Jeffrey I. Schiller <jis@MIT.EDU>
To: mlc@MIT.EDU
Cc: techmail@MIT.EDU, bugs@Athena.MIT.EDU, rar@MIT.EDU, mar@MIT.EDU,
In-Reply-To: Mark Curby's message of Mon, 23 Mar 92 17:56:58 EST <9203232256.AA25141@MIT.EDU>
Date: Mon, 23 Mar 92 17:56:58 EST
From: mlc@MIT.EDU (Mark Curby)
Greetings -
...
I recommend that the following be added to the TechMail wish list to be
addressed as resources permit after TechMail-S 2.0 is released.
- investigate the problem to confirm that the above understanding of the
problem is accurate, and nothing else is also going on. (If you know of
flaws in the above understanding please send comments and corrections to
techmail@mit.edu).
- if there is a easy fix in TechMail which does not appear likely to
break anything else then we should add this to a future version of
TechMail. An obvious candidate is to have the de-binhexing code look
for "- -" at the beginning of a line and convert it to "-" before
proceeding with the decoding. An alternative would be, as Roger
suggests, to modify the mh and xmh forwarding commands to allow the user
some way to turn off the "-" to "- -" conversion.
Not to get dogmatic.. but. I believe the "correct" fix to this problem is
to add a "undigestify" command to TechMail. The above solutions only work
for the simple case of one enclosure in a message. However if the message
contains two enclosures (one within the forwarded message and one standalone)
then it become ambiguous as to which one should be unBinhexed.
The undigestify command would take a message and break it into separate
messages, one for each RFC934 enclosed message.
User interface: We could make the undigestify command a button which
appears in the message window (and it can also be accessible from the
menu bar) that is grayed accept when a message which contains encapsulated
messages is encountered.
My two bits...
-Jeff
