uuxqt and remote mail

[Alexis Rosen]

J.Purchase at cs.ucl.ac.uk (Jan Purchase) writes:
>A colleague and I have been trying to setup a uucp connection between
>our A/UX (2.0.1) systems and are having serious and unexpected
>problems. I know that many people out there have got A/UX UUCP to work
>and I would really appreciate some tips.
>
>We have followed all the instructions in the A/UX manual and have
>achieved successful file transfers using uuto and uucp. However, we
>seem unable to persuade uux, remote email, or indeed any function which
>relies on uuxqt, to work at all. In all cases, uuxqt refuses to execute
>the command as if the originator of the command were not authorized.
>All commands whether they are listed in /usr/lib/uucp/L.cmds or not
>are refused. The same error message occurs even if a rubbish command
>(i.e. zzzzzz) is requested by uux.
>[etc.]
>
>I have checked that all the uucp configuration files exist, have the
>correct permissions and contain the required information.  FWDFILE and
>ORIGFILE both contain the name of the remote system (mickey), USERFILE
>has the line:
>
>	Umickey,mickey	/usr/spool/uucppublic
>
>Any ideas where we are going wrong? We could really use some help on this one.

Well, I answered this by mail, but I'm not sure I got through. Also, I had
another idea. First, what I wrote by mail:

I believe you want something like this in front of the rest of your USERFILE:
uucp,           /usr/spool/uucppublic
,               /usr/spool/uucppublic
 
....to be honest, I'm not sure that USERFILE works exactly the way it should.
But we've managed to make things work here. And what I wrote above is standard
(as much as any UUCP-related thing is standard).
 
I also seem to recall something about having a line at the beginning of your
L.cmds which specifies permissible paths. Something like:
PATH=/bin:/usr/bin:/usr/local/bin
but that certainly isn't necessary. And it may not work in A/UX. We don't
have it in our setup (which I built over a long time by trial and error).

--
In addition to that, it occurs to me that if L.cmds were protected so that
uucp didn't have read access to it, the symptoms described might happen.

---
Alexis Rosen
Owner/Sysadmin, PANIX Public Access Unix, NY
alexis at panix.com
{cmcl2,apple}!panix!alexis