[hylafax-users] HylaFax ftp on port 4559

Clay Daniels

unread,

Nov 7, 2000, 3:00:00 AM11/7/00

to hylafa...@hylafax.org

I'm setting up a HylaFax server on a RedHat 6.2 machine here on an internal
class C network. I receive faxes just fine using the RocketModems on the
RedHat machine, and the FaxMaster gets an email, which I retrieve on a
Windows client on the network. I will probably change to having the fax
attached to the email, but for now it gives an ftp link,
ftp://192.168.1.1:4559/recvq/ which sort of works but not very well. I had
to add entries in the hosts.hfaxd to avoid getting the password windows, and
now I can see the files but cannot download them. Also, I can move up to the
top directory, ftp://192.168.1.1:4559/ , where I can see everything but the
size and date listings are not correct. I'm trying this with Internet
Explorer 5.5, but when I drop to a dos command line ftp, I get Unknown Host.

I can ftp to the regular port 21 using browser, dos command line, or WSFtp.
What I do notice is that the files have owner.group of uucp.wheel and that
to have permission to download, I must copy the file to another name and
chown it to me.me .

For my hosts.hfaxd, I'm was just calling out the ip of the client box,
192.168.1.5, although I discovered that an entry of 192.168.1. works just as
well and would be handy in that all client machines on the local network can
be specified with just one entry.

Also, I've been playing with WHFC from Transcom as a Windows client. I'm
able to see the faxs in the recvq, but not much else. Apparently no option
for download, but there is a view option that requires setting up Samba on
the server, which I may very well do. Would a Samba share of recvq help my
ftp on port 4559? Would Samba allow me to share recvq as a windows network
folder? Any ideas?

Obviously I'm missing some things here.

Clay Daniels

____________________ HylaFAX(tm) Users Mailing List _______________________
To unsub: mail -s unsubscribe hylafax-us...@hylafax.org < /dev/null

richard lucassen

unread,

Nov 7, 2000, 3:00:00 AM11/7/00

to Clay Daniels

Clay Daniels wrote:
>
[ftp problems]

All you get is -rw-rw---- huh? I played with that ftp option but
unfortunately I didn't find a solution for this on the internet. I only
found some answers saying that this part of Hylafax doesn't work for one
or another reason (I can't remember what that was). But what I did is
adapt the file /var/spool/fax/bin/faxrcvd:

[..]
SENDER="`$INFO $FILE | $AWK -F: '/Sender/ { print $2 }'
2>/dev/null`"
FILENAME=`echo "$SENDER" | sed -e 's/ /-/g'`.tif
FILENAME="$COMMID-$FILENAME"
SENDTO=
if [ -f etc/FaxDispatch ]; then
. etc/FaxDispatch # NB: FaxDispatch sets SENDTO based on
$SENDER
fi
(echo "To: $TOADDR"
echo "From: The HylaFAX Receive Agent <fax>"
echo "Subject: facsimile received from $SENDER";
echo ""
mv $FILE recvq/$FILENAME
FILE=recvq/$FILENAME
echo `/bin/cat $FAXDIR/recvq/seqf`
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
echo -e "\nReceived on $DEVICE\n"
[..]

Just to give you an idea. All I do is click on the link and under linux
Netscape is starting "kfax" and under win "imaging" is started. In the
filename I entered the telephonenumber/name of the sender + the
communication-id to keep the filename unique.

Of course you'll have to adapt the paths.

> Also, I've been playing with WHFC from Transcom as a Windows client. I'm
> able to see the faxs in the recvq, but not much else. Apparently no option
> for download, but there is a view option that requires setting up Samba on
> the server, which I may very well do.

change the /var/spool/fax/etc/config.ttySx and change the faxpermissions
to 666 or 644 (default is 600) if you want anybody to delete and read
the faxfiles. There is an option in whfc to start "imaging" or any other
program when clicking "view". I can't remember what it was but it was
something with "c:\windows\imaging %s" that you have to fill in. But I
prefer the links in the mail that hylafax sends to me. Whenever I use
windows (I almost never do) I only use whfc for sending faxes.

> Would a Samba share of recvq help my
> ftp on port 4559? Would Samba allow me to share recvq as a windows network
> folder? Any ideas?

Samba will share the faxfiles, but you have to change the permissions to
666 or 664. In /etc/smb.conf add an entry like this:

[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)

--
________________________
recursion: see recursion

Lee Howard

unread,

Nov 7, 2000, 3:00:00 AM11/7/00

to Clay Daniels, hylafa...@hylafax.org

At 02:32 AM 11/7/00 -0600, Clay Daniels wrote:

>I can ftp to the regular port 21 using browser, dos command line, or WSFtp.
>What I do notice is that the files have owner.group of uucp.wheel and that
>to have permission to download, I must copy the file to another name and
>chown it to me.me .

I'm not sure that you should chown it to anything other than what it is,
but you do want to change the permissions on the received faxes. You do
that in the etc/config.<devid> file... (see man config)

LogFileMode
The file protection mode that should be used when
creating files to hold session logs. Note that
this value is given in octal. The default value of
0600 implies that the log files are not generally
accessible, which is important if sensitive infor
mation such as calling card access codes are
logged. If log files are to be publicly accessi
ble, this value may be set, for example, to 0644.
See also chmod(2).

RecvFileMode
The file protection mode that should be used when
creating files to hold incoming facsimile. Note
that this value is given in octal. The default
value of 0600 implies that only the facsimile user
can read received facsimile. If incoming facsimile
are to be publicly accessible, this value may be
set, for example, to 0644. See also chmod(2).

I don't view faxes via the hfaxd "ftp" protocol, so I can't help a lot with
it, but I can say that the last time I tried it (a few months ago) I didn't
have any problems other than the file names appearing funky in IE or
Netscape... which may or may not be a bug. If there are bugs with regard
to this, they definately haven't been made known to me.

>For my hosts.hfaxd, I'm was just calling out the ip of the client box,

>192.168.1.5, although I discovered that an entry of 192.168.1. works just=
as
>well and would be handy in that all client machines on the local network=

can
>be specified with just one entry.
>

>Also, I've been playing with WHFC from Transcom as a Windows client. I'm
>able to see the faxs in the recvq, but not much else. Apparently no option
>for download, but there is a view option that requires setting up Samba on

>the server, which I may very well do. Would a Samba share of recvq help my

>ftp on port 4559? Would Samba allow me to share recvq as a windows network
>folder? Any ideas?

A Samba share for the recvq directory may be easier for Windows clients to
access, but the permissions will still need to be adjusted as noted above.

Lee.

>Obviously I'm missing some things here.
>
>Clay Daniels
>

____________________ HylaFAX(tm) Users Mailing List _______________________

Clay Daniels

unread,

Nov 9, 2000, 2:18:33 AM11/9/00

to hylafa...@hylafax.org

Richard Lucassen and Lee Howard:

Thanks for the help. I gave up on the HylaFax 'ftp' and decided to just use
Samba shared files. After installing and configuring Samba, I did this:

Configured /var/spool/fax/bin/faxrcvd to point to the file , not the ftp
link, so that when I get the email, I just click and go there. [
file://192.168.1.1/recvq/fax00002.tif gives \\192.168.1.1\recvq\fax00002.tif
in the browser ]

Configured /var/spool/fax/etc/config.ttyR0 for RecvFileMode of 644 so that
the files are readable by all.

Also, with the Samba share, I can use WHFC and just click View File, and it
opens.

Thanks again,

richard lucassen

unread,

Nov 12, 2000, 3:00:00 AM11/12/00

to Clay Daniels

Clay Daniels wrote:
>
> Also, with the Samba share, I can use WHFC and just click View File, and it
> opens.

You can also say to windoze that "imaging" should open any *.tif file
(it's the default I think). Just create a directory of the faxshare on
your desktop and that's it. You do not need to start whfc for that. The
advantage of "imaging" is that you can rotate faxes when you receive
them upside down.

--
________________________
recursion: see recursion