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

    Zimbra and Hylafax integration

    You can setup Zimbra CS as a gateway for HylaFax users to send fax out using the scheme <fax number>@fax.our.domain, following these steps:

    1. Edit file /opt/zimbra/postfix/conf/master.cf, append this line:
    2. fax       unix  -       n       n       -       1       pipe
          flags= user=uucp argv=/usr/bin/faxmail -d -n ${user}
    3. Edit file /opt/zimbra/postfix/conf/transport, append this line:
    4. fax.your.domain   fax:localhost

      And then use this command to regenerate the transport.db file:

      /opt/zimbra/postfix/sbin/postmap /opt/zimbra/postfix/conf/transport
    5. Edit file /opt/zimbra/postfix/conf/main.cf, append this line:
    6. fax_destination_recipient_limit = 1

      Note: the process limit of 1 in the master.cf file is necessary with fax software that cannot handle multiple requests at the same time.

    7. Edit file /opt/zimbra/conf/localconfig.xml, modify the entry “postfix_transport_maps” as follow:
    8. <key name="postfix_transport_maps">
          <value>proxy:ldap:/opt/zimbra/conf/ldap-transport.cf, hash:/opt/zimbra/postfix/conf/transport</value>

      Note: specify dbm instead of hash if your system uses dbm files instead of db files. To find out what map types Postfix supports, use the command postconf -m.

    9. Then of course, restart the Zimbra MTA service with command (as zimbra user):
    10. zmmtactl stop
      zmmtactl start

    Note: be sure to not advertise fax.your.domain in the DNS 🙂

    This process has been tested on Zimbra CS Open Source edition 5.0.9 and HylaFax 4.4.4 running on the same Linux CentOS 5 machine.