Please create an account to participate in the Slashdot moderation system

 


Forgot your password?
Close
typodupeerror
×
Linux Software

Ask Slashdot: Linux Fax Servers w/ WinTel Clients? 79

Posted by Cliff from the just-da-fax-ma'am dept.
JimMcc asks: "We are planning a new network installation with a Linux server running Samba and WinTel clients. One of the issues yet to be resolved is providing the users the ability to fax directly. We would like to offer a solution which provides shared fax modem(s) accessed through the network instead of a fax modem / analog line per user. The customer is a non-profit and is cost sensitive. Has anybody heard of a possible solution? Thank you for any pointers/ideas you may have. "
This discussion has been archived. No new comments can be posted.

Fax Server Software for WinTel Clients? More

Fax Server Software for WinTel Clients?

Comments Filter:

  • SuSEFax Win32 (Score:1)

    by Anonymous Coward
    You may want to have a look at
    ftp://ftp.suse.com/pub/SuSE-Linux/suse_update/Su SEFax_WIN32/

  • Fax Solution (Score:1)

    by Anonymous Coward
    mgetty+sendfax is your answer. We use it exclusively and with good
    results. I even fax from my workstation at home which is on a dialup
    connection with a Linux box as the router. It also allows client login
    with secure shell. Check it out

    http://www.leo.org/~doering/mgetty/

  • You can do that w/ sendfax, its pretty easy, and works. Look in the sendfax docs (dont remember which file in /usr/doc/sendfax it is) but there is a pointer to a web page that tells you how to use this program called respond? (grep respond /usr/doc/sendfax/) that allows you to print to a special printer in windows that is actually a fax, then respond opens and asks for the phone number etc. Works nicely, and its all free software I believe --nrl
  • Depending on the amount of faxing that goes on, faxaway might not be cost-effective. My previous employer used Faxaway and we found it to have a lot of hidden costs, such as fees if a certain percentage of faxes were not delivered. We ended up settling on an in-house NT based system though, so I'm not much use for alternatives.

    Depending on how much you're faxing, and what your LD rate is, faxaway can end up being quite a bit more expensive than a fax server. (we ended up saving about 4 cents a fax by not using Faxaway)

    btw: the faxaway webpage currently shows $.11/minute as the going rate.
  • You could use VSI*Fax. They now have a Linux server. http://www.vsi.com [vsi.com] The Windows client has a print driver that sends the data directly to the linux server. I've used this software on a AIX server and it worked pretty slick. A bit of a problem to setup, but once it's going it's a snap.
  • This is just to add to all the stuff already mentioned: NT has per-seat licencing. That means if you have 100 people using NT server you need to buy 100 client licenses. (last I checked they were somewhere around $50 each). You also need to buy Zetafax client licenses. Add to that the base price of NT and Zetafax, and you get a pretty large sum.
    I'm sure you had some kind of special deal so that the $100 you mentioned covers all the costs, didn't you? Or did you accidentally misplace the decimal point? Obviously you are not pirating, are you?
  • According to the WHFC FAQ [transcom.de]
    Is the sourcecode for WHFC available.

    Currently the sourcecode is not available. I have currently no permissions to release it, because I use some code from internal projects.

    Seems like a fake reason to me since you could put the internal code in a seperate DLL or whatever. The only source released is for language DLL creation. I suspect the author is working towards a non-free (as in free beer) version, if you ask me.

    On the other hand, nothing stops you from using Respond (which comes with source code) because it also supports Hylafax, according to the docs.

  • I am really glad to see good and affordable commercial fax solutions for Unix/Linux! Open source fax software can be a little bit more difficult to install and use than your average open source software. I guess this is because of the analog component :-).

    However, there is also a solution in between. What if you can get support for Hylafax/sendfax/efax etc. from an individual or a company? Then you have the free software, no licencing problems and you don't need to spend that much time (the individual/company does that) in case your time is worth something.
  • We still have a Ghostscript/Postscript conversion problem. Sometimes documents (Word97 etc.) can't get converted to Postscript. Have to dig into this. Glad to have the source code!
    Office97 bastardized the Postscript language. M$ Office97 produces incorrect Postscript in some instances. You obviously found them. Find another program to generate Postscript in Win as M$ doesn't follow the Postscript standards.

    I was not precise enough: the Postscript could actually be converted to facsimile (G3 TIFF) on the server but Hylafax's 3 second timeout kicked in immediately so it thought the conversion had failed. It turned out that Hylafax really gets confused timingwise when it had been stopped and started from an "at" job, as we did to have it reread its configuration files. Somehow this "at" job screws up Hylafax alarms/signals/timers.

    I'm not a hard-core Unix systems programmer, but again, I'm glad I had the Hylafax source which helped me find the trouble spot! Your point about the MS dialect of Postscript is right though for another thing I mentioned. Cover pages are difficult to create. End-users tend to create their cover pages in Word. The MS Postscript is very difficult to adapt for Hylafax cover pages because you don't know where to put the Hylafax Postscript macro's (From:, To:, Regarding:, etc.).

    We ended up export the Word document to HTML and converting it to Postscript under Linux!

    • Don't cut cost on the modem. There really is crap outthere. We got a Multitech. Multitechs are approved on the Hylafax list, although not this particular model. We used the standard Multitech config entry. Unfortunately, in a few cases the faxes got garbled. When we added standard Class 2 config lines, the problem went away.
    • With a line speed of 57600 bps, faxes got garbled as well. Dropping to 38400 bps solved the problem. I have no idea why this happened.
    • Get a recent version of Ghostscript. This is not a problem anymore with current distributions.
    • We still have a Ghostscript/Postscript conversion problems. Sometimes documents (Word97 etc.) can't get converted to Postscript. Have to dig into this. Glad to have the source code!
    • We chose to resize incoming faxes which happen to be too big for a page (A4). However, short faxes which are too wide are being "stretched" beyond recognition. Fortunately, with the source, I was able to make a patch for libtiff so that incoming pages are only scaled down, not up.
    • Fax cover sheets are a chore to create (by non -experts)
    • Security problems in Hylafax were mentioned but I have no idea what the writer is thinking of. There has been an issue a long time ago, but this one has been fixed.

  • yeah right (Score:1)

    by BB ( 5050 )
    That sounds great, since time is expensive. However, you fail to mention 34 of the 35 possible fax server solutions. Not only that, but the cost of Zetafax (as found at http://www.tmcnet.com/articles/ctimag/0498/review0 03.htm) is $525 for a 5 user version or $2,250 for 50 users.

    I think that this means Hylafax looks much better, especially considering that you will get all your upgrades for free (both the application and the OS). If it takes a few hours to understand and install, hey, at least you'll be able to maintain the software better too.

    Do you work for Zetafax? Micro$oft? You certainly aren't able to provide much helpful advice.

    How does your NT box seem for stability anyway? Perhaps that might be important too?
  • Sounds like a great area for one of the developers or even a consultant that has a lot of experience with hylafax, etc., to make a living out of working with free software.

    This is certainly something I would consider once I finish school with (insert your free software project here), if Linux and Open Source is at least as big as it is now.

  • Just curious... how can you print to PostScript from Win9x? Is there a generic PostScript driver? I looked, but didn't see anything like that.

    Steve

  • Hylafax and WHFC (Score:3)

    by Goner ( 5704 ) <nutate@@@hotmail...com> on Sunday August 01, 1999 @05:27PM (#1771451) Homepage
    I just set up a similiar system at work with one old AMD k5 and three microso~ win95 boxes. The AMD linux box is a samba server, gateway, and fax server. It runs hylafax [hylafax.org] which isn't too hard to install. The sucky machines which crash alot run WHFC [transcom.de]. This works like a charm, you can print from WordPerfect and it brings up a little window asking you what the number is. You hit send, and it emails you if the fax went through (or if it didn't). It really put my boss over the edge with enthusiasm for Linux. Email me if you have specific questions on how to get this to work.
  • I have installed Hylafax and have no problems with it, but I have never used the Windows client(s), not having any Windows machines around to try it on. All I know is that I have read of it, probably in the hylafax documentation. So I'm not really helping much, am I? :-(

    --
  • I sat down last week and had it up and running within 20 minutes, including relocating the box after testing. Run faxsetup, add your clients to /var/spool/fax/etc/hosts and make sure faxgetty is running, 'faxgetty ttySwhatever' even if you're only doing outbound faxes, they just seem to want to sit in the queue otherwise.

    Yeah the whfc driver for the win clients is kinda funky, but it does works.

    Good luck.....
  • Some years ago I used such combination on a LAN to send and receive faxes. It was still time of the first Slackware, RedHat had just come in and everyone flamed them.

    The scheme was quite simple but the realization gave some trouble. However this thing worked for nearly two years without having serious problems.

    We had a telephone line only dedicated to faxes. mgetty was answering for the line 24 hours a day. Every fax that came in was converted and dispatched to a network printer. Meanwhile stations working on Windows sent faxes through a fake network printer in postscript. On Linux box a few scripts on perl converted the the stuff and sended it to mgetty.

    There were some problems with realization of this scheme. First some features exist on fax format that "spoiled" its conversion on the printer. So there was some need to rewrite the stuff. Besides there was the problem for mgetty to know where to send the fax. We made it through a "hack" on the printer. In reality on the spool directory entered the postscript file and a small file with the telephone number.

    Anyway after three monthes of relatively hard work (well then Linux was a headache to costumize) we managed to have an automatical system that solved a lot of problems. One remarkable thing was that "lost faxes by the staff" were almost gone.

    As I said the thing worked for two years. It didn't work longer because I quit and the replacement loved other OSes ;) After a few monthes the company went bankrupt :)

  • Hylafax / Perl / Postscript (Score:3)

    by peril ( 11405 ) on Sunday August 01, 1999 @05:59PM (#1771455)
    I actually spent about a week working on a similar project, (creating a method for a workgroup to send faxes via a web page...) WHFC was REALLY shaky for me, it worked spotty on NT.

    The basic interface was a web page with an upload of a postscript file from the client machine (with the necessary attributes to send to the sendfax command line), then sendfax is invoked from a perl script that calls sendfax with proper arguments.

    I used the Apple Laserwriter PS printer drivers installed as file printers. DON'T TRY AND USE THE HP DRIVERS. It appears that they encapsulate the postscript in PCL, and that just won't work. (Hylafax chokes on this.)

    Step 1, Get Hylafax, install it, become good friends. (I have been told that there are numerous security holes in Hylafax; please take that into consideration.)

    Step 2, Write the cgi's, they are not long or complicated, I'll be happy to send you the tarfiles of what I did, however I am not responsible if you get burned using them. Email me if you are interested.

    Step 3, test test test, figure out the real needs of your clients and make sure your solution is workable for them.

    The more interesting problem to solve would be how to fax office documents by uploading thru some (web/other) interface. I was working with the applixware office suite to create a .doc/.xls -> .ps converter, and it was working fair/poor depending on the input file type. RTF worked great, Word 97 with lotsa pictures ended up looking significantly different from the original, so I gave up. Applixware may be up to the task now, if anyone knows any other methods I would LOVE to hear about them.

    Another neat idea would be to have an interface to the incoming faxes and have some administrative person be able to email them to the correct party. Kinda like efax for the small office situation. This would be really easy to do, just that I got busy with other stuff and couldn't get to this.

    peril@nospam.u_de_l.edu
    get rid of the nospam and the underscores for email.
  • The solution I'm using is: mgetty+sendfax, samba and X-Deep/32 (a X Server for Win32). I install a simple PS printer on Windows (Apple LaserWriter) and point it to a Samba queue that is configured to pop-up a Gtk+ application on the sender of the job, asking for fax information. A cron job that calls faxrunq do the rest.

    You can find XDeep32 on http://www.pexus.com
  • you could also take a look at tcp-int for cheap long distance faxing. you ship your fax via e-mail to a fax machine that can deliver your fax with a local call. Otherwise, I've heard hylafax is a real good solution as well.
    -earl
  • I've heard some good things about halyfax and mgetty+sendfax and respond, but the one thing that neither of them seems to support is DID routing. Where I work, I'd love to use a linux fax server, but we had to go with something else (in our case Optus FacSys, which generally works, but occasionaly really sucks) because we wanted to do DID fax routing with 100+ users. There was one package that I saw that would not only do DID routing, but would OCR faxes, look for a To: field and route based on the name in that field. Does anyone know if there is a linux product that deals with DID's, or if any work is being done on programming drivers for DID boards (the only ones I know about are Brooktrout and Dialogic Gammalink boards)?


  • Besides saying me too I also have an URL for respond (the page also has some docs):


    http://kulichki-lat .rambler.ru/moshkow/PC/faxserver/horsthp.txt [rambler.ru]


    Let me just say that we are using it here and it really works well. Users can just print to a special printer and after one second (or so) respond comes up and asks for the phone number and some other information. Very easy to set up too.


    And it it is very cost effective :-))


    Ciao Jens.

  • With all of the readers weighing in with Hylafax, I thought I'd just add that mgetty+sendfax and respond works great.
  • (Linux would work just as well, by the way) It was a bit hard to set up, but with the new Samba features I could even get it recognized and browsed under the domain. I orignally tried WHFC but it does not work well with machines that have multiple ethernet ports. (AARGH!) I also set up the local CD-R drive on the box, for added value. :)
  • We are running a hylafax server with 30 (multitech) modems, and hundreds of faxes/day. We use the WHFC client.

    It has worked great for us, and replaced 3 unreliable windows-based fax servers.

    I also patched tiff2ps to fix the scaling problems with long/short pages. My patch is available at hylafax.org.
  • As easy as printer? Hmmm....

    let me put it this way:

    If you want simple, straightforward, unflexible fax software, do NOT choose hylafax.

    If you want flexible, reliable fax server software that can handle very high loads and very complex configurations, then hylafax will probably be a good choice.

    It sounds to me like hylafax is *definitely* not for you.
  • Well, you got one thing right - hylafax isn't simple. It is, however, very powerful and extremely reliable. We've been running it on a linux box with 5 modems for a couple of years with absolutely no problems. It is rock solid. We send over 200 faxes each day and receive over 100 every day. It is the core of the operation here (a relatively prestigious scientific journal). Most of the communications in and out of the office are via fax (a lot of signed forms and letters - they never let me finish the web-based stuff).

    Because hylafax is so flexible and easy to use, we were able to very easily add logging of incoming and outgoing faxes in MySQL and make all of that accessible via a set of web pages. Users can view the status of their faxes, find out why there were errors, view incoming and ougoing faxes, etc.

    If you have a decent fax modem and are willing to configure it and the software correctly, you will love it. If you are an ignorant fool and expect plug-and-pray functionality, give up now and go buy something from microsoft.

    Why is there a list of crappy fax modems? ummm...let's see...I guess that would be because they suck. You should be glad that there's a resource that isn't afraid to tell the truth about crappy hardware.

    You expect fax server software to be as simple as a terminal program? You are an idiot.
  • Yes.

    use the "QMS PS 810" driver which gets installed with every win9x/NT base system.

    this is a completely generic Postscript driver that samba /lp/lpr understands, and you don't need to install any extra software on the PC, and you shouldn't even need the windows CDROMs.
  • $1000 != a good programmer for two weeks.
    do the math 52 weeks a year $500 a week comes to $26,000 a year before taxes. And you are not talking about any fringe benifits. you might get a brilliant student programmer that thinks this is a majore cool project and get him for that. BTW I am pro LINUX but the math is wrong.
    However any good programmer out there that thinks $26000 is good pay let me know I can find you something to do.
  • Just a note: licensing schemes that lock software
    to a particular host are a royal nuisance.

    I was going to download your software and try it out, but have decided not to as I refuse to be forced to identify my hosts in order to evaluate
    software.
  • "...The customer is a non-profit and is cost sensitive..."


    NT server costs more than $1000 (dfl 2579,--). That's not what I call cost-sensitive. You could hire a real GOOD programmer for 2 weeks with $1000 that could write you a custom fax-server for Linux/BSD and windows-drivers (GPLed offcourse). I'd not use NT just because it's way too expensive.

  • I'm in a similar situation, I think. I was going to experiment with HylaFax. Would a hylafax/samba combination be enough?
  • The original Respond is on http://www.boerde.de/~horstf/ [boerde.de]. It's in german, but you see the link to the software.


    Respond is a Great Thing (TM) and works very fine with mgetty+sendfax and samba.

  • I've configured HylaFax on an old 486 box running RH Linux 5.0. There were some configuration issues with the Fax/Modem (US Robotics Sportster 56k x2 upgraded to v.90), but those were easily resolved. (It was a flow-control issue).

    I can now effortlessly support faxing from both Win* clients (using WHFC) on the network and the Mac clients. To support the Mac clients currently you need to enable the older Hylafax protocol which is seriously insecure. If you do that, be sure that the box is well inside your network's borders. The author of the Macintosh Hylafax client said that a newer version is coming that supports the new HylaFax 4 protocol, but there is no time frame.

    All links for both HylaFax and the clients can be found from HylaFax's homepage (http://www.hylafax.org/).
  • Samba comes with a printing FAQ that documents a neat way to have it detect the number the FAX should go to without any software on the client side. Basically you prefix the number with something (say, "FAX #:") on the cover sheet (where you want to put the recipient's fax number anyway), and make sure you format the leading string and the fax number all the same. Then generate postscript and hand off to samba. Since postscript uses 7-bit ASCII, it looks through the file to find the leading string, then determines the number to fax it to. Pretty cool.
  • As I understand it, the best Win32 client for Hylafax is not free software. Something to think about if you are sensitive to that kind of thing. Not that I have a better idea..

  • A pretty generic solution I've used with success in the past is to use the COMT serial port-to-telnet redirector (which has grown up to be "Dialout/IP", from Tactical Software) with a homegrown telnet-to-modem server on the server side (there's apparently an open-source server side solution called sredird available now that would handle the server side of this).

    This gives the WinTel client a virtual modem to play with. Then you can use any fax/communications software with it (WinFax Pro worked fine).
  • G'day,
    I agree - I've just set up Hylafax myself... looking pretty damned good! and it has a nice email2fax gateway interface that runs through sendmail.
    HylaFax URL --> http://www.hylafax.org [hylafax.org]
    Very good software :-)
    Regards,
    Andrew
  • I know that setting up a rebust Linux fax server is a total bitch and a half. We tryed hylafax but the time it spent on setting it up was not worth the effort. We paid less than 100.00 for ZetaFax server software for NT and clients for win9x boxes and it all worked right out of the box. There are about 35 different Fax server software packages for NT that does not cost that much. but will save you money in the time spent to set everything up. But that is if your time is worth something.
  • 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...
  • tcp-int is nice if you're faxing in the areas they cover, but their coverage is spotty. I've been using Faxaway [faxaway.com] for all my faxing; their rates are fairly reasonable ($.10/minute, and a 2-page fax is typically 1 minute), and zero fax hassle (no fax machine, no fax line, no modem sharing) since like tcp-int, you just e-mail your documents to get them faxed.

    Actually I'm not hassling with fax machines for receiving, either, since I got a free fax number from eFax.com [efax.com]. The faxaway/efax combination has been downright convenient, not to mention cheap. My understanding is that efax now offers fax send capabilities as well, but I haven't checked out the details.
  • The Faximum Messaging Server [faximum.com] mentioned earlier in this thread handles DID under Linux. We do it using MultiTech modems and a special black box that converts the DID signals (and line levels) into DTMF and line levels equivalent to a POTS line. Although we support Dialogic/Gammalink fax boards under SCO, neither of the major fax board vendors support Linux yet and so that is not an option (unfortunately).

    P.S. - OCR on fax resolution images (not to mention handwritten coversheets) is so hit and miss that it is probably not even worth trying. Manually routing faxes using a browser to view the fax (see our manual routing demo [faximum.com]) is very speedy and much much more reliable.

  • We agree entirely with your comment "the ideal solution is to have no client components on the Windows boxes".

    The approach you outline with Samba is one we are considering for a future release of the Faximum Messaging Server [faximum.com]. Your proposal of using a web page to provide the fax addressing information is a good one and one we have thought of. The only problem is that it is a two-step process: (1) the user prints to the special Samba fax pseudo-printer and (2) the user hits the appropriate page on the fax server to provide the addressing information. And if the user forgets the second step his fax languishes on the fax server forever.

    The approach we take with FMS [faximum.com] is, IMHO, easier for the user.

    The FMS Print Driver enables users to "print to fax" (in the same manner as your Samba approach) but then a dialog box pops up asking for the addressing information (name, company, fax number). This info is converted into an email address of the form (Person_Name/Company_Name/Phone_Number@fax.your.co m) and then MAPI is used to invoke your email client of choice with the above address already in the To: field and the TIFF produced by the FMS Print Driver already attached.

    This requires almost the same amount of software on the client side as your Samba approach (i.e. FMS Print Driver as compared to a PostScript print driver) but has the added benefit of (a) doing the print-to-fax conversion on the client side so it can be previewed, and (b) popping up a dialog box so the user need not remember and manually invoke the second step of running a web browser to specify the addressing information.

  • Agreed, "licensing schemes that lock software to a particular host are a royal nuisance". Indeed, any mechanisms that are used to enforce licence terms are a pain both for the developer and the user.

    But unfortunately software piracy continues to be a significant problem and one has to try to walk the fine line between protecting the fruits of one's labour and making the software too difficult to install/evaluate.

    Another approach taken by some packages is to deposit hidden files or data in various places in the file system to be able to detect an attempt to run an eval on a machine that has already had an eval. Some people object more vehemently to such file system "pollution" than to software that is tied to a machine ID (be it IP number or node name).

    And in the final analysis, the software is worth something (IMHO) and the eval is being offered free. The quid pro quo is we provide the eval (which is not crippled) at no charge, you identify yourself and your machine.

    With that said, your point is a valid one and is something we consider every time we launch a new release of the software.

    Thanks for your feedback. It will be circulated amongst those here who make the decisions.

  • If I might be so bold as to suggest you try our company's product: the Faximum Messaging Server (FMS) [faximum.com].


    Consider:

    • Its architecture is a generation ahead of traditional Client/Server fax products. Rather than requiring its own proprietary client for Windows it utilises your existing email infrastructure. Received faxes are converted by FMS into email messages and delivered to the same inbox as your email messages. Outbound faxes are merely email messages addressed to (for example) Jane_Doe/ACME_Company/1-604-926-8182@fax.your.com


      If you want to fax from something like Microsoft Word you can use the FMS Print Driver which allows you to "print to fax" which creates a TIFF file and uses MAPI to invoke your favourite email client with the TIFF file already attached.

    • Although FMS is commercial software it is free to individuals for personal non-commercial use and for organizational or commercial use it starts as low as $149 for a two-user licence ($1,295 for a 50-user licence). That compares very favourably with the commercial alternatives. And as for the "free" fax software out there, what is your time worth (witness the comments elsewhere about the challenges surrounding some of the "free" packages)?


    Thank you for your tolerance of this commercial message and please visit http://www.faximum.com/fms/ [faximum.com] for more details.

  • Correct. You cannot cut costs on modems. There is a modem cost threshold though. If don't think twice about spending the dough for the modem in your hand, it's too cheap. If you think 3 times about it in the checkout line, it's too expensive. If you think about spending the $$ twice and can still afford to eat, you have the right modem and it'll prolly work fine.

    Remember, the fax standards (last time I heard) was at 14.4. Most fax machines cannot connect faster than this. Having a rockin 56k modem will do you absolutely no good sending faxes faster. A good well supported 14.4 will do just fine.

    Office97 bastardized the Postscript language. M$ Office97 produces incorrect Postscript in some instances. You obviously found them. Find another program to generate Postscript in Win as M$ doesn't follow the Postscript standards. You cannot expect other applications to break the language just because M$ does.

    -mwe
  • Guess that's why I left the Netherlands and now live in the US. You'd get me for about a day and a half for that kind of money and short commitment. (Longer projects drop the price though...)
    Hey; I have a family to maintain while I work on neat stuff in my free time.
    Hajo
  • Hi, "uplink" is a free complete solution for a
    fax/email/http/other gateway. It supports
    faxing from windows using a samba print queue.
    The URL is

    http://www.ime.usp.br/~ueda/uplink/

    "uplink" is currently beta software, but the fax
    features are under heavy usage in more than
    one installation. Cheers,

    Ricardo Ueda.

  • Respond (Score:1)

    by foo ( 143650 )
    If you use mgetty+sendfax, there is a "Respond" package that you can use. It isn't a very elegant solution Windows-wise, but it basically works. It requires the Windows client to run a daemon (the "Respond" program).

Slashdot Top Deals

The explanation requiring the fewest assumptions is the most likely to be correct. -- William of Occam

Close