Personal tools
HylaFAX The world's most advanced open source fax server

HylaFAX 4.2.0 release

Revision as of 15:43, 22 December 2005 by Paul (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The HylaFAX development team is pleased to announce a major milestone in the HylaFAX development roadmap - our 4.2.0 feature release! As always, our sincerest thanks go to all who participate and provide feedback.

The source code for the 4.2.0 release can be downloaded from:

(md5: 463726ed21cfdac730c5d6915e0840cf 1,351,870 bytes)

This document is intended to describe the significant differences between hylafax-4.2.0 and older releases, point out any known incompatibilites and issues, and provide the reader with directions to further resources regarding HylaFAX.


  • added Class 1 ECM and MMR support
  • added Class 1.0 V.34-Fax (SuperG3) Support
  • added software-driven real-time format compression conversion
  • added extended resolution support
  • removed the requirement for a case-sensitive filesystem to build
  • unified the queue file numbering mechanism
  • integrated Caller-ID/DID support throughout the software
  • numerous other enhancements and bugfixes (see CHANGES)


  • A low-priority job can block a high priority job to the same destination.

Please refer to HylaFAX Bugzilla for a detailed list of issues.


  • Due to tighter adherance to ITU-T T.32 and the older Class 2 specifications, HylaFAX copy-quality checking and ECM support now operates slightly different in Class 2/2.0/2.1 than in previous versions. This change will not effect users of most modems, but because the Eicon Diva Server follows T.32 yet uses the older Class 2 command interface, Diva Server users will probably need to add: Class2ECMType: 2.0 Class2CQQueryCmd: !3 Class2CQCmd: AT to their respective modem config files.
  • libtiff-3.6.1 is fatally flawed when dealing with Group 3 images. Don't use it as-is. See:


This release includes nearly a year's worth of truly exceptional contributions from HylaFAX developers and users alike, and everyone should consider migrating to a HylaFAX-4.2.x release as soon as possible. While every attempt has been made to retain backwards compatibility with the 4.1.x series, it's possible that assumptions your local installation depends upon may no longer be true. Whenever possible, test test test before upgrading a production server!!

HylaFAX-4.2.0 will be of particular benefit to anyone running their modems in Class 1 due to the addition of native ECM and V.34 support (useful features that were previously available only in the notoriously buggy Class 2 firmware of modem manufacturers).


Binary packages for some operating systems and platforms are available. Please see and If you are able and willing to produce a binary package of HylaFAX for general distribution, then you are invited to join and solicit your binary package.


iFAX Solutions, Inc. ( provides commercial support to HylaFAX users. Single-incident and annual support options are available, as well as a variety of consulting services. Contact for more information.


HylaFAX has numerous 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:

Join and participate in a HylaFAX mailing list


When corresponding about this software, please always specify:

  • 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 v4.0pl2 under RedHat Linux 4.2 with gcc 2.7.2; ZyXEL 1496E with 6.11a firmware."

Read the on-line documentation and resources

See: and

Review HylaFAX CVS


Report confirmed bugs, feature requests, and submit patches



The HylaFAX development team

This page was last edited on 22 December 2005, at 15:43.

Powered by MediaWiki
Attribution-ShareAlike 2.5

Project hosted by iFAX Solutions