[ HOME ] [ BACK ] [ NEXT ]
One of the many reasons for using HylaFAX is for the ability to submit faxes from any networked
computer, in any order, and in any quantity. HylaFAX will work away at them without anyone ever
walking to a fax machine, and better yet, nobody will be wasting their time watching paper pass through
it... page after page after boring page. If there's a busy signal or no answer, HylaFAX will try later, no need
to remember in a few minutes. HylaFAX remembers its job well.
HylaFAX server must interact with a client program of some kind to receive its faxing instructions.
These client programs may reside on another computer, on the same system as HylaFAX server, or (as
in most cases) a combination of client programs both on the HylaFAX system and off work together for
proper fax sending.
This section deals with several different approaches to this task. However, it is advisable to
at least understand the basics of the HylaFAX client programs themselves, as sent-fax problem debugging and troubleshooting
is best done at that level first. The essential HylaFAX client programs with which to be familiar
and especially sendfax(1). A good reading
would also include hylafax-client(1).
For another HylaFAX client list, see http://www.hylafax.org/links.html#clients.
- HylaFAX itself, of course! Read sendfax(1).
Typical usage would be something like:
sendfax -f "email@example.com" -R -r "faxsubject" -c "coverpage comments" -x "Recipient's company" -d "Recipient@1234567" tofax.ps'
where firstname.lastname@example.org is a valid e-mail address for the sender, 1234567 is the number where to fax, and tofax.ps is the image file to be faxed.
Standard HylaFAX-compatible file formats are ASCII, TIFF, PostScript, and PDF (in versions newer than 4.1beta2).
Be aware that sendfax is capable of handling multiple -d options and that only the options that precede it apply to that instance of the -d. In
most cases the -d option is the last option that should be used.
- SuSEFax - See the printed SuSE manual for SuSEFax information.
- tkhylafax is a popular Unix/X11 tcl/tk interface to HylaFAX.
Get it at ftp://ftp.hylafax.org/contrib/tkhylafax.
See a screen shot here.
- ksendfax - http://www.sad.it/~jug/ksendfax/. RPMs are
available at RedHat's ftp, also.
- GFax - http://www.cowlug.org/gfax/.
Front End Gnome Fax Software For Linux.
Requires Gnome 1.2 or newer such as the Helix release.
- faxmail - faxmail is a HylaFAX client program which takes an electronic mail message
on standard input and converts it to PostScript in a form that is suitable for transmission as a
facsimile. Read the man page: faxmail(1). In order to use faxmail as an email-to-fax gateway, typically some degree of "sendmail
mangling" must be done. See
and http://www.hylafax.org/howto/clients/faxmail-nonrandom-host.html for more information.
- email-to-fax with procmail - If procmail is your mail delivery agent (MDA), then you can easily
configure it to handle outbound faxes by setting up a dedicated user account for faxing out and placing
appropriate recipes in that user's $HOME/.procmailrc file. Outbound faxes are then e-mailed to this user account.
This is how the above-mentioned RelayFax client
works, which already has a simple generic email-to-fax capability built-in.
It is possible to send a (Hyla)FAX by printing to
a Samba-defined fax-printer using a Windows client. This is the recipe:
If there are any difficulties or questions, do not hesitate to contact
Ignace Suy email@example.com
He has provided a sambafax web-site at:
please refer to it for the most up-to-date information.
If you (re team) are working with it, drop him a line.
Sambafax is now suited to run under the printing systems lpd, LPRng and CUPS.
For CUPS the installation is somewhat different. Refer to the website above.
Although a true HylaFAX client for AS/400 is not available (more
tests with the gnu-hylafax java client are scheduled), you can send facsimiles as
print jobs to the HylaFAX server. To do this, some things have to be done but for now
a little note.
I tested this with Red Hat Linux but using a different distros will not present to much
difficulties. The feedback that I received from earlier version of this howto is that most
of the people are not AS/400 experts wich is not a problem but some language that I use in
the steps for AS/400 setup make sense in that plattaform. Ask if you needed any explanation.
- AS/400 procedures:
1. Create an output queue like is presented here outq.txt
and be sure that LPD package is installed and running.
Note: In outq.txt you will find the follow line Workstation costumization object....: LINUXOUTQ2
This applys only for specific national character map like portuguese, italian ,etc,etc.
AS/400 use EBCDIC internally and needed a little help to know that linux use ASCII ;-). Any table can be
modified but I sugest changing the 860 map table.
1. Check if you have enscript installed.
2. Check if lpr is installed and running.
3. Add a printer.
4. Modify the entry for that printer in printcap to match the script as400pscript
where the job from AS/400 is redirected to create the fax and hylafax is called. Read carefully
the script, you will save yourself time and headashes. Here is my printcap for guidance,
Note: The PATHs applies to RH7.x. Don't forget to restart lpd deamon.
Last notes:If you want more control accessing lpd services in the linux box, use LPRng package.
The as400script, by default, merge the text from AS/400 with a file where is stored the company logo.
If you only want send text, disable the merge text+companylogo process (read carefully the as400script).
When merging logos with text, remember, you MUST create the logo file in EPS, Encapsulated Postscript, format.
This was done with Red Hat 7.0, lprng 3.7.4, kernel 2.2.16-22, keyboard pt-latin1,
- Improvement: Rob Sherman changed the as400script to enable multi-page faxing,i e,if you needed same
fixed text(only) in every page. If you are good in postscrip, doing this for graphics it will be easy.
Read carefully the script and place the ACKFORM.hdr file in $PATH/enscript/. Pay attention
that in AS/400 you must specifie your job as ACKFORM. In the as400script2 the ACKFORM.hdr file is invoqued here
/usr/bin/enscript --fancy-header=$FNAME where in FNAME is stored the hdr name file, ACKFORM.
This section was contributed by
Pedro Roçadas firstname.lastname@example.org
Pedro thanks Giulio Orsero for his assistance on this task.
[ HOME ] [ BACK ] [ NEXT ]
Last updated $Date: 2005/06/17 03:01:35 $.