Re: [hylafax-users] errors while accessing faxserver:4559

["Clay Daniels" <clay_1@airmail.net>]

Othmar

The web interface on port 4559 is a modified FTP protocol, not HTTP. I never
had much luck with it either. I can see the files, but not seem to access
them, with FTP. I ended up creating a Samba share so I can share my Linux
faxes in /var/spool/fax/recvq with the Windows clients using good old
netbios on ports 137 & 139. Now I can browse them in Windows
Explorer/Network Nieghborhood or get them through WHFC. I modified the
/var/spool/fax/bin/faxrcvd file a little so that the notification email
sends a netbios file link, not the default ftp link.
...
#echo "$FILE (ftp://$HOSTNAME:$PORT/$FILE):"; $INFO -n $FILE
echo "$FILE (file://messenger/$FILE):"; $INFO -n $FILE
...

Richard Lucassen had a similar suggestion that will work for Linux clients
too if you modify it to match your path:
...
echo -e "file for win: file://server1/c/docs/fax/$FILENAME\n"
echo -e "file for unix: file:///mnt/fax/$FILENAME\n"; $INFO -n $FILE
...

I tried out the modifications to faxrcvd that sends the recieved fax by
email, but since it removes the recieved fax from the server, I decided
against this option. See the How-To:
http://www.hylafax.org/howto/delivery.html

Also, it is essential to have a line in the hosts.hfaxd file for any clients
that will be given access. I have my server and clients networked on a class
C network, 192.168.1.x , so I added a third line to the hosts.hfaxd file
that allows all clients to access the server without having to list each one
separately (note the dot at the end):

192.168.1.

Hope this helps,
clay
----- Original Message -----
From: "Lee Howard" <faxguy@deanox.com>
To: "Othmar Pasteka" <op@atnet.at>; <hylafax-users@hylafax.org>
Sent: Sunday, November 26, 2000 10:44 PM
Subject: Re: [hylafax-users] errors while accessing faxserver:4559


> At 11:06 PM 11/12/00 +0100, Othmar Pasteka wrote:
> >hi,
> >
> >while i was trying to access the received faxes over the
> >webinterfaces i get an error message:command:
> >GET /log/ HTTP/1.0
> >500 GET: Command not recognized.
> >
> >well, i set RecvFileMode to 0644 and etc/hosts.faxd is also there
> >with two lines:
> >localhost
> >127.0.0.1
>
> I don't use remote file retreival, so I'm not an expert at this, but I
> think that you need to have the remote IP number in that hosts.hfaxd file
> included with the local loopback.
>
> Lee.
>
> >ok, it should work or did i oversee something? anyway, it
> >doesn't, do i have to enable something that it understand the
> >HTTP commands?
> >
> >so long
> >Othmar

In order to view the recieved faxes
you should have a Samba share configured for the /var/spool/fax/recvq
directory. The Samba rpm's were installed by default on my RedHat 6.2 server
install, but double check by doing:
    rpm -q samba
and then look at /etc/smb.conf

Look at Ulrich Eckhardt's page:
http://www.transcom.de/whfc/doku/inst_view.html
for configuration info.

Richard Lucassen had a similar share in his good advice to me:

[fax]
   comment = received faxes
   browsable = yes
   path = /var/spool/fax/recvq
   valid users = user1 user2 (if you want to restrict access)
   public = no
   read only = yes (or not)

My share reads as follows, which works great for me:

# HylaFax
[recvq]
   comment = HylaFax Receive Queue
   browsable = yes
   path = /var/spool/fax/recvq
   public = yes
   writable = no

Another easy trick that works for me is to set in smb.conf:
[global]
...
    security = share    # user security is much more difficult to configure
...

Also read the 'man smb.conf' pages. Samba is a neat tool for sharing Unix
files to Windows clients.

Hope this helps,
Clay