HylaFAX 6.0.0 released


The HylaFAX development team is pleased to announce the first release of HylaFAX 6.0.  HylaFAX 6.0 contains lots of new development and features that have accumulated in CVS for the past year since HylaFAX 4.4 was branched off for stable maintenance.

Our sincerest thanks go to all who participate in the development and testing process.

The source code for this release is available from our FTP site: ftp://ftp.hylafax.org/source/testing/hylafax-6.0.0.tar.gz

MD5SUM: 716de4f44b2a18205b4b24135f307e23  hylafax-6.0.0.tar.gz

SHA1SUM: f8020efcd48d17f5728d5bb0e6b46df2cd4b8ad2  hylafax-6.0.0.tar.gz

HylaFAX 6.0 introduces several new features for HylaFAX:

  • PCL Support
  • hfaxd can sort list output (like sendq) arbitrarily for clients
  • I18n: HylaFAX client strings are now translated and available in different languages
  • IPv6 support
  • New permissions in hfaxd to allow for more admin control on who can see/modify jobs/faxes (see PublicJobQ/JobProtection/PublicRecvQ)
  • Powerful page range handling capabilities
  • Better faxq/notify integration as well as many improvements to the T.30 protocol code.

There are only 2 differences to note if you’re upgrading from HylaFAX 4.4 or older, neither of which are likely to affect many users:

  1. If you have clients that still use the old protocol (not the common FTP style protocol), they will no longer work with the new hfaxd daemon.
  2. The notification email mechanism no longer sends “blocked” emails by default, as the jobs are not being requeued, or done.  To continue receiving them, you’ll need to configure it accordingly in FaxNotify.

The full set of release notes is browsable: http://git.hylafax.org/HylaFAX?a=blob;f=doc/RELEASENOTES-6.0.txt;hb=HYLAFAX-6_0_0


Binary packages for some operating systems and platforms are available. Please see:


If you are able and willing to produce a binary package of HylaFAX for general distribution and one is not already available for your platform/OS, then you are invited to add it to the Binary_Packages wiki page above.


HylaFAX has numerous public support resources available.  The user is encouraged to utilize the manpage documentation before turning to other support arenas.  However, if other support is desired, or if you would like to actively take part in the HylaFAX community, you are invited to:

– what version of HylaFAX you have,
– what system you’re running on (if it is Linux please name the distribution),
– if the problem is modem-related, identify it and the firmware rev For example: “HylaFAX 6.0.0 under CentOS 5.3 with gcc 4.3.1; ZyXEL 1496E with 6.11a firmware.”


    The HylaFAX development team

    Sendmail backup mx relay

    I have used sendmail for a number of years. We use it on our main mail server and on our backup mx servers.

    Up until recently we simply allowed the backup mx servers to relay all mail to the domains they serve. Unfortunately spammers tend to target backup mx servers in the belief they are less well protected.

    One of the side effects of this is that you end up accepting mail for lots of invalid addresses, which not only results in more spam (as the spammer thinks the address is valid) but also means you then end up trying to send non delivery receipts to some random reply address when the backup mx tries to deliver the mail to the main server and gets refused as the address doesn’t exist.

    I finally worked out that there is a nice feature in sendmail to only relay certain addresses thus refusing all the other junk and preventing the erroneous non delivery receipts.

    By default we used to add the following to out access database

    TO:iwayvietnam.com RELAY

    which simply means relay all email addressed to the domain iwayvietnam.com

    It is possible to be more selective but first you have to add the following to your sendmail configuration (sendmail.mc). Suggest you save a copy of sendmail.cf first for later comparison.

    dnl #
    dnl #Use access db with undocumented feature
    dnl #
    define(`_RELAY_FULL_ADDR_', `1')

    Then do a make. Compare your new sendmail.cf with your old one just to ensure you’ve not lost anything.

    You can now specify specific email addresses in the TO field rather than just the domain.

    It means you have to remember to update your backup mx servers whenever you add or remove an email account but that is a small price to pay for the empty mail queues. I guess you could easily automate it.

    Don’t for get to rebuild your access database once you’ve edited the text file.

    # hash /etc/mail/access.db < /etc/mail/access

    PS. I also set DoubleBounceAddress to nothing (O DoubleBounceAddress=) to get rid of all those non delivery receipts of non delivery receipts!