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

Phillip Helbig---undress to reply helbig at astro.multiCLOTHESvax.de
Fri Nov 5 20:41:44 EDT 2010


In article
<8c74153f-a6ec-4abb-a073-fc58048a0716 at x7g2000prj.googlegroups.com>, Hein
RMS van den Heuvel <heinvandenheuvel at gmail.com> writes: 

> The UAFGETERR is reported for any error other then RNF (record not
> found) but only for the Original VAXMAIL code.

Right.  Submitted to SYS$BATCH, and it ended up on a VAX.  By the end of 
the year I should have an all-ALPHA cluster.

> MAIL does not update the UAF record nor has any business dealnig with
> record locks for it. It should read with RRL (Read Regardless of Lock)
> or better still NQL (No Query Lock) since that became available a
> decade ago... right when the RLF retry code was added. Odd! (Stupid?).

VMS 7.3 VAX must be about 10 years old by now, methinks.

> Phillip>> MAIL> SET FORWARD commands every few seconds  (long
> story).
> 
> Pray tell!

One of the other hats I wear is a co-moderator of the newsgroup
sci.physics.research.  When the old moderation relay stopped working, I
volunteered to set one up, on my VMS cluster of course.  It has all the
features of the old relay and then some and is quite efficient.  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.  For myself, I like HEADERS in the SMTP configuration (so 
they are at the bottom), but for redirected posts all should stay at the 
top (to make processing easier for other moderators, not on VMS).  So, 
there were some unexpected problems, but I got it working.




More information about the Info-vax mailing list