The HylaFAX development team is pleased to announce our 4.1.2 patch-level release! The release represents many hours of work and testing by developers and contributors, and our thanks goes to all who participate and provide feedback. The source code for the 4.1.2 release can be downloaded from: ftp://ftp.hylafax.org/source/hylafax-4.1.2.tar.gz (md5: b10225bbbda1f02c07258621d0ceb819 1,259,364 bytes) The README file from this release follows. Please read it carefully. * * * This document is intended to describe the significant differences between hylafax-4.1.2 and older releases, point out any known incompatibilites and issues, and provide the reader with directions to further resources regarding HylaFAX. * NEW FEATURES * * improved modem recognition routine (ignores firmware rev. data in ATI0) * enhanced support for building on MacOS X and Digital Unix * more descriptive messaging for timedout/failed jobs, and T.4 protocol errors * enhanced support for Topic modems * adopt safer defaults for modem rates and dial commands * repaired an error which caused faxqclean to segfault under heavy load * fixed a problem with faxcron which could reset sequence numbers * KNOWN ISSUES * * Specific support for fax classes 1.0 and 2.1 are not yet implemented. * Server-based fax archival support is still unimplemented (although documented). * When running in Class 2/2.0, NSF can be parsed incorrectly. * Copy quality checking by cqtest is imperfect. * sendfax use of ~/.hylarc differs from its use of hyla.conf * faxrm and faxalter contain format string vulnerabilities. ** Please refer to HylaFAX Bugzilla for a detailed list of issues. * INCOMPATIBILITIES * * The popular faxrcvd-mail scripts have been deprecated by FILETYPE use in FaxDispatch, and unchanged, will not work with faxgetty in 4.1.2. See 'man faxrcvd' for details. * Failed faxes now have status "F" instead of "D". Most client programs which display/report job status will need some alteration to accomodate this. * HylaFAX 4.1.2 may not compile with gcc-3.0 * WHO SHOULD UPGRADE? * If you've installed 4.1.1 and: a) are not seeing faxqclean dying because of segmentation faults, and b) don't have an unusually high rate of fax communication errors, and c) send at least one fax per month an upgrade is probably not essential at the present time. Users who don't meet one of the above criteria, and users of all other versions should upgrade as soon as practical. * HYLAFAX BINARY PACKAGES * Binary packages for some operating systems and platforms are available. Please see ftp://ftp.hylafax.org/binary/ and http://www.hylafax.org/howto/install.html#ss2.3.3 If you are able and willing to produce a binary package of HylaFAX for general distribution, then you are invited to join hylafax-devel@hylafax.org and solicit your binary package. * COMMERCIAL SUPPORT * HylaFAX.org has partnered with iFax Solutions, Inc. to provide commercial support to HylaFAX users. Single-incident and annual support options are available, as well as a variety of consulting services. Contact HylaFAX Sales for more information. * FREE SUPPORT * 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: * join and participate in a HylaFAX mailing list See: http://www.hylafax.org/mailing-lists.html 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: http://www.hylafax.org and http://www.hylafax.org/howto * review HylaFAX CVS See: http://www.hylafax.org/cvs.html * report confirmed bugs, feature requests, and submit patches See: http://bugs.hylafax.org/bugzilla Thanks, The HylaFAX development team ------------------------------------------------------------------- And now, a note from HylaFAX's original author ;-) Silicon Graphics has seen fit to allow me to give this work away. It is free. There is no support or guarantee of any sort as to its operations, correctness, or whatever. If you do anything useful with all or parts of it you need to honor the copyright notices. I would also be interested in knowing about it and, hopefully, be acknowledged. Finally, note that this software is called ``HylaFAX'', not ``Hylafax'', ``hylafax'', and certainly not ``FlexFAX'' (the old name which someone else has a copyright on). If you want to refer to this software use ``HylaFAX (tm)'' and be sure to honor the Silicon Graphics trademark. Sam Leffler Use and Copyright ----------------- Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc. HylaFAX is a trademark of Silicon Graphics Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that (i) the above copyright notices and this permission notice appear in all copies of the software and related documentation, and (ii) the names of Sam Leffler and Silicon Graphics may not be used in any advertising or publicity relating to the software without the specific, prior written permission of Sam Leffler and Silicon Graphics. THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.