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

Difference between revisions of "Beta Versions"

(Changelog)
(Current release candidate (4.3.0rc2))
Line 11: Line 11:
 
ftp://ftp.hylafax.org/source/BETA/hylafax-4.3.0rc2.tar.gz
 
ftp://ftp.hylafax.org/source/BETA/hylafax-4.3.0rc2.tar.gz
  
A source RPM will be announced shortly - watch this space!
+
Please refer to our [[Red_Hat_Packages]] page for a source RPM that should build on most Red Hat, Fedora and SuSE distributions.
  
 
==New features of particular note==
 
==New features of particular note==

Revision as of 23:21, 1 May 2006

The HylaFAX development team often asks other developers and interested HylaFAX users to test upcoming software releases. As these are beta versions of software they may contain more bugs than usual, and should probably not be used on production servers if your job depends on the performance of that server!

Reporting Bugs

The HylaFAX Bugzilla is located at http://bugs.hylafax.org/. Please file a bug report there if you can. If you prefer to send a message to the mailing lists to discuss the problem, we encourage you to subscribe to hylafax-devel@hylafax.org and post it there. The hylafax-users mailing list will also reach many of the right people, and is the next best thing if subscribing to -devel and filing a bug report seem like too much trouble. Bottom line - we want your bugs!!


Current release candidate (4.3.0rc2)

The source can be downloaded from:

ftp://ftp.hylafax.org/source/BETA/hylafax-4.3.0rc2.tar.gz

Please refer to our Red_Hat_Packages page for a source RPM that should build on most Red Hat, Fedora and SuSE distributions.

New features of particular note

Internationalization

HylaFAX can now send emails in your native language! It presently supports:

  1. Polish
  2. French
  3. Italian
  4. Portugese
  5. Spanish
  6. German

and can be easily extended to support many others.

The translation of emails is carried out by the new bin/dictionary shell script. Remember that relative paths like this are relative to the fax spool directory, which in many cases means you will find this in /var/spool/hylafax/bin/dictionary. Check it out, ... you can see it's basically just a file where the strings HylaFAX uses when sending email are defined for each of the supported languages.

Many of the scripts in HylaFAX's bin directory are designed so that you place local customizations into a separate file (usually in etc/) that gets 'sourced' by the script as it executes. This protects local changes from being overwritten during an upgrade, and helps separate code that you maintain locally from that of the standard HylaFAX core. For the bin/faxrcvd script this local file is etc/FaxDispatch, for bin/notify it's etc/FaxNotify and for bin/pollrcvd it's etc/PollDispatch. To activate translation in faxrcvd, notify or pollrcvd, you simply add the following lines to FaxDispatch, FaxNotify, or PollDispatch:

CHARSET=ISO-8859-1
LANG=es_MX

The bin/dictionary script will look at the value of $LANG and set the various texts used in faxrcvd, notify, and pollrcvd accordingly.

As with each of the other scripts mentioned above, bin/dictionary also has a local customizations file in the etc/ directory, called etc/FaxDictionary. This is to allow administrators to further customize particular phrases to their liking. If there is a phrase in bin/dictionary that you wish to reword or for it to say something custom for your installation or company, for example:

 DICTRECEIVEAGENT="The HylaFAX Receive Agent";

Simply add a similar entry in etc/FaxDictionary such as:

 DICTRECEIVEAGENT="My Company Fax Server";

and the custom string should now appear in all emails from HylaFAX.

JobControl

JobControl is a feature that many people have wanted, in a round-about way, for quite some time.

JobControl gives HylaFAX servers the ability to "virtualize" the sending configuration in a standard way. Many users want to use different TSI or calling_party numbers for different users who submit jobs. JobControl gives them the abilty to do so.

The administrator can configure/setup a JobControlCmd that can assign these types of settings, and these values can be based on arbitrary job values, instead of being limited only to the destination number.

This means that parameters can be changed/set based on the client (IP) of the job submitter, the owner of the job, the email address of the sender, etc, as well as the destination, etc.

Some possible uses include:

  • Specifying a different ModemGroup set for each owner/submitter
  • Specifying a different ModemGroup based on the email address of the sender
  • Specifying MaxSendPages/MaxDials/MaxTries on a per "owner" basis to override/force specific maximums.
  • Specifying TimeOfDay restrictions for certain senders
  • Rejecting jobs based on the submitters requested ModemGroup
  • Setting the TSI based on the sender
  • Setting the DialRules/ModemDialCmd basd on the details of the submitted job owner/email and destination modemgroups.

Some samples can be found at http://people.ifax.com/~aidan/jobcontrol/

Changelog

A complete list of changes from 4.2.5 is as follows:

  • Re-work fix for hfaxd's time handling (BUG 723) (28 Apr 2006)
  • Don't let users kill each other's jobs (BUG 752) (28 Apr 2006)
  • Use areBatchable() to make sure batching doesn't ignore job modems (28 Apr 2006)
  • Enhance Italian translation (BUG 758) (26 Apr 2006)
  • Fix faxq sleepq concurrency problem (BUG 745) (26 Apr 2006)
  • Fix runSchedule() concurrency problem (BUG 745) (26 Apr 2006)
  • Fix some of the error paths in the setReadyToRun jobcontrol pipe, fork, and exec calls (BUG 745) (25 Apr 2006)
  • Fix unblocking job problem (BUG 733) (24 Apr 2006)
  • back out flush modem I/O (BUG 756) (24 Apr 2006)
  • Make sure hfaxd returns JBIG faxes in recvq list (BUG 731) (23 Apr 2006)
  • Resolve Solaris bus error under native compiler (BUG 769) (23 Apr 2006)
  • Fix quoted-printable MIME encoding in faxrcvd (BUG 760) (21 Apr 2006)
  • Fix sendfax to accept both destination and user subaddresses(BUG 762) (21 Apr 2006)
  • Repair broken MMR from some Multitech modems (BUG 763) (21 Apr 2006)
  • Add JobControlWait to allow faxq to wait for JobControlCmd to finish synchronously (4 Apr 2006)
  • flush modem I/O on receptions before sending any data (03 Apr 2006)
  • fix incorrect "Fax protocol error" in ECM mode (03 Apr 2006)
  • add German NSFs and correct HylaFAX NSF bit order (03 Apr 2006)
  • set Class1RMPersistence to 0 in digi config prototype (03 Apr 2006)
  • extend V.21 HDLC frame reception timeout to 10 sec (03 Apr 2006)
  • ignore MESSAGE-WAITING response after dialing (02 Apr 2006)
  • Correctly remove EOFB at the end of MMR images (02 Apr 2006)
  • set minimum of 4800 for V.34 primary rate renegotiations (02 Apr 2006)
  • improve handling of V.34 control channel retrain (02 Apr 2006)
  • Add isdn4linux modem config prototype (02 Apr 2006)
  • Add IAXmodem config prototype (02 Apr 2006)
  • Update config.guess & config.sub (27 Mar 2006)
  • Add JobControl (obsoletes DestControl) (27 Mar 2006)
  • Fix hfaxd SNPP login code to 250 (Bug 732) (27 Mar 2006)
  • Fix hfaxd timezone handling on new GLIBC (BUG 723) (24 Mar 2006)
  • Fix locking of recvq tiff files (BUG 739) (23 Mar 2006)
  • fix batching of page jobs (23 Mar 2006)
  • expand Class1JBIGSupport to allow for differentiation between full, none, send, and receive support (17 Mar 2006)
  • remove QualifyCID in lieu of DynamicConfig RejectCall (15 Mar 2006)
  • fix buffer overrun in NSF parsing (21 Feb 2006)
  • add dictionary for notify, faxrcvd, and pollrcvd internationalization support (21 Feb 2006)
  • add CHARSET config option for mailing scripts (21 Feb 2006)
  • use To-Company and To-Name coverpage entries in the notification message if they are available to use (21 Feb 2006)
  • add support for libtiff-3.8 (31 Jan 2006)
  • use PDF in q-files when appropriate (30 Jan 2006)
  • fix configure in vsnprintf detection (30 Jan 2006)
  • fix segfault on some compilers where the rare occassion of receiving CTC instead of PPS occurs (30 Jan 2006)
  • fix rare occassion where TCF fails following an unexpected receipt of prologue frames (30 Jan 2006)


Powered by MediaWiki
Attribution-ShareAlike 2.5

Project hosted by iFAX Solutions