gaspar@ALMSA-1.ARPA (Al Gaspar) (12/06/88)
I just figured it out. If I rmm messages at the shell mh gets rid of them. However, I often scan my messages and pipe the output through less. If I enter '!rmm n', mh places a '#' sign in front of n. Apparently, mh knows that rmm is being invoked in a subshell or that message n is still being scanned. Cheers-- Al -- Al Gaspar <gaspar@almsa-1.arpa> USAMC CSDA, ATTN: AMXAL-OW, Box 1578, St. Louis, MO 63188-1578 COMMERCIAL: (314) 263-5118 AUTOVON: 693-5118 uunet.uu.net!almsa-1.arpa!gaspar