[Info-vax] %MAIL-E-UAFGETERR, error reading user authorization file

[Phillip Helbig---undress to reply]

In article
<fa264fec-6aed-4f33-8649-df8af4e40758 at g10g2000vbc.googlegroups.com>,
Hein RMS van den Heuvel <heinvandenheuvel at gmail.com> writes: 

> > Right.  Submitted to SYS$BATCH, and it ended up on a VAX.
> 
> Stop doing that. Submit to a queue served only by Alphas or
> better. :-)

In progress.  I'm collecting a cable today which will allow me to 
replace some VAXes with ALPHAs in the cluster.  (I could do so without 
the cable, but with the fast wide ALPHA controller, I want to make use 
of a fast wide shelf and disks.)

> > Doing SET FORWARD within MAIL (within the proper context) seems to be the most
> > efficient way to get an incoming post redirected to a "random"  moderator

> You got it working, so it is a moot point, but sometimes using LOGICAL
> NAMES for USERNAMES is more efficient. MAIL will try to translate
> usernames as logical names allowing you to redirect that way. It
> honors the leading underscore  ( _xxxx )convention to NOT translate
> those.

Yes, MAIL and logical names is a nice combination.  (Also, the leading 
underscore on a username will cause VMS MAIL-level forwarding to be 
ignored.)  However, IIRC it wants them in the SYSTEM table (maybe even 
EXEC), so on a cluster I need to do that on all nodes.  With MAIL SET 
FORWARD, just once is enough.  OK, there is more overhead, but the 
overhead of SYSMAN would probably be even more.