Comment Respond & mgetty+sendfax worked out well for me... (Score 2) 79
I find this strangely ironic - this is what I spent the morning wrestling with at work - finding and installing a suitable Linux-based network faxing system! (or at least what morning was left after I finally crawled out of bed on a Sunday to go into work...)
Have to admit, there seems to be a lot of support here for Hylafax, and while I looked at it briefly, I admit I haven't really played with it much. The solution I found that fit our needs (I work for a small firm with about 30 WinNT workstations and, of course, my Linux box running the show...) came from a Respond, which someone mentioned earlier. It's available from http://www.boerde.de/~horstf/. What it consists of is a Win32 client that sits and listens on a TCP port and a set of perl scripts running on the server. The actual "fax printer" is set up under Samba as a normal print share, from which Samba invokes one of the perl scripts. This script contacts the client machine that queued the print job, and the little Respond TCP client pops up and requests a phone number. From there, it will interface to either Hylafax's sendfax or standard mgetty+sendfax, judging by the config sections. I chose to use go with the mgetty option. Either way, everything was very much a drop-in install, and I had it found, installed, and working on all clients in less than two hours total. That's my two bits...
Have to admit, there seems to be a lot of support here for Hylafax, and while I looked at it briefly, I admit I haven't really played with it much. The solution I found that fit our needs (I work for a small firm with about 30 WinNT workstations and, of course, my Linux box running the show...) came from a Respond, which someone mentioned earlier. It's available from http://www.boerde.de/~horstf/. What it consists of is a Win32 client that sits and listens on a TCP port and a set of perl scripts running on the server. The actual "fax printer" is set up under Samba as a normal print share, from which Samba invokes one of the perl scripts. This script contacts the client machine that queued the print job, and the little Respond TCP client pops up and requests a phone number. From there, it will interface to either Hylafax's sendfax or standard mgetty+sendfax, judging by the config sections. I chose to use go with the mgetty option. Either way, everything was very much a drop-in install, and I had it found, installed, and working on all clients in less than two hours total. That's my two bits...
