head 1.2; access; symbols; locks ahuxley:1.2; strict; comment @# @; 1.2 date 97.08.14.10.01.59; author ahuxley; state Exp; branches; next 1.1; 1.1 date 97.06.13.12.34.34; author ahuxley; state Exp; branches; next ; desc @@ 1.2 log @*** empty log message *** @ text @
Check poisson:/var/aliases/forward.list to ensure the user has one *AND ONLY ONE* entry in the file and note the name of their mail server.
Login to the user's mail server and run:
$ /usr/ucb/mail -v problem_user_name
Expect:
problem_user_name...
Connecting to local...
Sent
If you get sent then verify that the test message has been appended to the bottom of the mail file.
If it has, then on the mail server, in the mail spool directory, run:
# ls -al | grep problem_user_name
check for lock files, but it's probably best to call the user and check that things aren't working again already.
If things aren't working again and there are lock files present then ask the user to close all mail readers/writers and when they've done this refer to the section on locked mail boxes.
If everything looks okay, then check reading mail from the particular client machine that the user is reading mail from; there may be a problem with the automounting of the mail directory.
$Header$
@ 1.1 log @Initial revision @ text @d5 1 a5 1 d15 1 a15 1Check mc5:/var/aliases/forward.list to ensure the user has one *AND @