CURRENTLY KNOWN PROBLEMS OUTSTANDING:
- reply-to address in Pine is WRONG and MUST be fixed (see below for fix hints)
RESOLVED PROBLEMS:
- ThinClient (SunRay) users may find their session screensaver lock does not respond to the password. This requires (unfortunately) your session to be terminated and then you can login again (and the problem doesn't come back). Please contact Tim to take care of locked sessions.
- Solaris 10 workstations mounting NFS exports from anchor require tweak in order to work. Failure to fix means NFS mounts fail. Email Tim to have arrange to have this fixed on your desktop if required.
- Printing on Anchor and "ThinClient" - is working only for the PHASER Colour Laser. HP printer is disabled for now, will fix this later.
FIX ADDRESS IN PINE:
It seems the new version of pine has different default behaviour, and may announce a "from" address on your sent emails in the form, "UserName@anchor.phys.ocean.dal.ca". This address will NOT work from the outside world(*) and people won't be able to send you email if they reply to any message with this "from" address.
To fix this problem:
- Start a new PINE session
- select S (SETUP)
- select C (Config)
- type W (Where is) after which you will be prompted for a word to find
- type "customized" and press return. You will be taken to an entry reading, "Customized-hdrs="
- Press ENTER and then update the customized header to suit your taste / thus:
customized-hdrs=From: "John Doe" <John.Doe@Dal.Ca>
Then, exit / save changes. You are done.
Direct Fix Method:
- Open new SSH session on anchor
- While in your home directory, edit the file, ".pinerc"
- Locate the line entitled ""
- Revise it to appear as follows:
customized-hdrs=From: "John Doe" <John.Doe@Dal.Ca> (Clearly, substitute exactly the name / address that you want)
(*) Nov-8-07 update: I've updated configuration on our mail server, so that mail intended for user@anchor.phys.ocean.dal.ca is successfully delivered to user@mail.phys.ocean.dal.ca - so this problem is "less of a big deal" but still is best to fix using the workaround described above.