Re: flexfax: Hylafax - fax user defined in passwd

[Nico Garcia <raoul@cirl.meei.harvard.edu>]

-----BEGIN PGP SIGNED MESSAGE-----

On Thu, 13 Nov 1997, Eddie Reed wrote:

> Yup, I darn killed it. And then erased all configuration files created
> during install, then reinstalled hylafax from the distribution.
> Ran faxsetup, ran faxmodem, back to abnormal:
> 
> Can't use sendfax from command prompt without a password.

OK. This is a separate problem, methinks. Did you re-run faxsetup?
Does "faxstat" work? Is your $SPOOL/etc/hosts file for HylaFAX
permissions set up correctly, which may be the problem?

> The strange thing is that I had this working with the very first install!!
> What threw me off is that snnp takes the same port as stronghold.  So I
> reinstalled hylafax without the snnp and moved stronghold to another port.

Oof!. That's a potetntial problem for the rest of us: thanks for the
heads up. Is 444 the default port for stronghold?

> When I look at the dir with the faxes that went out previously, they
> report as being sent as "nobody@myhostname.com".  Which tells me there is
> some kind of permissions problem here with some of the dirs and files
> owned by "fax".

Umm. No. hfaxd sits on the port 4559, and answers requests for service
from the sendfax or faxstat command. They correspond, the user's name
gets associated by hfaxd with the service request (using permissions
in the hosts file to verify their authority to send faxes) and an
email address gets generated from that data (as I understand it). The
data gets fed to the hfaxd by sendfax, and it handles the fax job.  No
ownership or file permissions involved there.

			Nico Garcia
			Engineer, CIRL 
			Mass. Eye and Ear Infirmary
			raoul@cirl.meei.harvard.edu

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBNGty1D/+ItycgIJRAQEaWAP/YQ+0m/L9oaiLx6IB/6Az2tTcm3rezDrH
zz4PTg6OVAle6VrfkwFKRA1gqsLPuUtfk7wB5q8bj14pqRXpoBtvB/CB9q3zAmd7
WVdxs8sc818l1TOSjA6Huw8goZCFRp6Yxne8mRRr1X6Z+moI8cJkcYdRYalHF82m
x+056fJ5FsA=
=/uvk
-----END PGP SIGNATURE-----