From:	MERC::"uunet!CRVAX.SRI.COM!RELAY-INFO-VAX" 14-JUL-1992 17:02:09.79
To:	"info-vax@kl.sri.com,egger@id.unibe.ch"%SUNMAN.decnet@sunman.nwc.navy.mil
CC:	
Subj:	re: example of menu based VMS mail interface 

>Hi,
>
>we are looking for a menu based interface to VMS mail, which does support
>VT100, VT220 etc terminals. Does anybody know something about such a
>program?
>
>Thanks, Martin
>
>*******************************************************************************
>  Martin Egger, Ph.D., Computing Services - System and User Support Group
>  University of Bern, P.O. Box, Laenggassstrasse 51, CH-3012 Bern, Switzerland
>  Phone: ++41 (0)31 65 38 45, Fax: ++41 (0)31 65 38 65, Telex: 753 112 unib ch
>  RFC: egger@id.unibe.ch, X.400: S=egger;OU=id;O=unibe;P=switch;A=arcom;C=ch;
>  HEPNET/SPAN: 20579::49203::egger, DECnet (Switzerland): 49203::egger
>*******************************************************************************
	I have 2 menu driven programs which do menu driven VMS mail 
interfaceing. Both use SMG and need only be compiled and linked.
	mail_profile_edit allows a manager to modify/delete entries in
			the mail profile data file. If run with no arguments,
			reads in the records of all users, or if invoked
			mm :== $'f$environment("default")'mail_profile_edit.exe
			mm username [username....]
			will only edit the specified user entries.
			user names followed by a "*" indicate users with
			no corresponding entry in sysuaf.dat.

	s_mail	is for individuals to read/send etc their own mail. It is
		menu driven but I have never put it in use. It turned out
		to be slow and cumbersum. I am passing it on as an example
		only of programming VMS mail interface.

The two programs follow in 11 parts in VMS Share format


Michael N. LeVine  Naval Air Weapons Station, China Lake, Ca 93555, USA
Internet: levine%fidler.decnet@nwc.navy.mil
(619) 939-2614  avn  437-2614 

 "Waiter, there's a bug in my soup!"        
 "No, Sir, it's not a bug, it's a feature!"