ROODE@BIONET-20.ARPA.UUCP (09/14/87)
mkhaw@teknowledge cites several specifics of Unix MM-32 which I agree are points which could stand improvement or clarification. Many mail programs seem to keep mail in their own format so this concern is common. I wasn't alluding to incompatibility with Unix or similarity to TOPS-20 as the basis for suggesting taking a look at MM-32. Specifically, the features in MM-32 that I think recommend it as an improvement over other Unix mail agents are: a) a ? feature for all commands and command options The user need not know the options in advance to select them; nor need he depart from command interaction to consult separate help text for the command. b) a distinct top level; i.e. the individual mail commands are not merged in with the Unix shell commands. I think this is a plus for user understanding. c) a mode change between the top level of the mail program and the level under which a particular message is being processed. Again, I think clarity is enhanced when distinctions are made as to context of user interaction. d) profile capability including the ability to suppress display of selected headers when they appear in messages e) flexible specification of message sequences, i.e. to perform an action on sequences specified by compound conditions such as 'from joe' and 'since 15 May 1987'; the mere ability to identify messages to include in a sequence by one attribute of the messages intended let alone ability to compound them f) capability to search with messages with a certain text string in the message body Characteristics which I would find highly valuable but which MM-32 does not have are as follows: A mode when reading messages to allow display of only the first n lines of message body. At that point a one keystroke selection should allow for continuation; otherwise all other message disposition options ought to be valid. Ability to specify automatic disposition with optional confirmation, i.e. "when reading messages addressed to 'SPECIAL-COMMITTEE' by default save them in file 'SPECIAL-COMMITTEE.FILE'"; "when reading messages from Joe, by default place them in file Joe.mail but confirm first"; when reading messages addressed to 'announcements' delete them after reading; when reading all other messages not addressed directly to myself, place them in file 'LIST.MAIL'" I think the last set of mail processing capabilities is very simple yet provide a very powerful tool for managing a history of online EMAIL. -------
howie@cunixc.columbia.edu (Howie Kaye) (09/14/87)
Another version of MM is currently being written at Columbia University, under a User interface package called CCMD. This is an expanded Tops-20 like interface, as described in the message about MM-32. This MM program will be mostly compatible with the TOPS20 version, though it will support several mail file types, and will eventually run as a POP client. CCMD currently runs under Berkeley and sysV UNIX, and MSDOS. MM will also run on all of these (Only as a POP client under MSDOS though.) Mail to info-topsux-request@cu20b.columbia.edu, or info-ccmd-request@cu20b.columbia.edu for more information.] ------------------------------------------------------------ Howie Kaye howie@columbia.edu Columbia University hlkcu@cuvma.bitnet Systems Group ...!rutgers!columbia!howie