Good news and bad news.

    The good news:
    	MAILCK and MAIDIR have been updated to make more sense with VMS V4.

    The bad news:
    	They only work as good as before (no known bugs fixed...network
access still is not feasible).

    It now uses the logical name MAIL$LOGIN as the default for where to
look instead of SYS$LOGIN.  MAIL$LOGIN will translate to SYS$LOGIN if you
don't override it.  If you told mail to SET MAIL_DIRECTORY somewhere-else,
you broke MAILCK.  Here's how to fix it:

    In your LOGIN.COM, before you use either MAILCK or MAIDIR, do
    	$ ASSIGN SYS$USERDISK:[username.maildir] MAIL$LOGIN:
where [username.maildir] is where you told MAIL to put your stuff.

    You can delete the old DIR.MAI file in SYS$LOGIN.

    There aren't any new features other than that.  If you try to tell
mailck to check ANYWHERE IN PARTICULAR, it knows you are looking to see
if another user (your pen name maybe?) got mail, and that you can't
read it.  So it won't even try.  The logical name (mail$login) is the
only way to get MAILCK to automatically invoke mail.  Incidentally,
if you want to check your own mail, but don't want to automatically
invoke it, do a $CHECK MAIL$LOGIN: and it will just announce that you
have new mail (but VMS does that already).

    To recap how to use them:  (my mail directory is [SUTTLES.MAIL])
    	$ ASSIGN SYS$USERDISK:[SUTTLES.MAIL] MAIL$LOGIN:
    	$ MAI*L :== @SYS$SYSDEVICE:[UTILITIES.COM]MAIDIR
    	$ CHECK :== @SYS$SYSDEVICE:[UTILITIES.COM]MAILCK
    	$ CHECK		! go into mail if I have any
    	$ CHECK SYS$USERDISK:[SHEPPERD.MAIL]	! spy on my boss
    	$ CHECK SYS$USERDISK:[OBRIEN.JUNK]	! her mail is in this directory
    Remember you have to know where they set their MAIL_DIRECTORY to.

sas