Revision as of 20:19, 10 February 2007

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.2rc1)

The source can be downloaded from:

ftp://ftp.hylafax.org/source/BETA/hylafax-4.3.2rc1.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

Template-based email notifications

In the past, there has been discussion about both customizing and translating the e-mails that faxrcvd and notify send. In this version of HylaFAX, we've done some work to make faxrcvd and notify use "templates" for their e-mail messages.

This means that faxrcvd and notify no longer use the "bin/dictionary" and eval "echo $..." everywhere when creating their e-mails, but now directly use a template file.

These versions continue the tradition of sourcing etc/FaxDispatch (for faxrcvd) and etc/FaxNotify (for notify) to get "command" variables that influence what they do. Of course, these shell scripts can continue to do whatever else they were doing (including calling exit to terminate normal faxrcvd/notify handling if desired).

These shell scripts can now also set the TEMPLATE variable to control the source of template files that faxrcvd/notify use to generate their e-mails. Templates are taken from (relative $SPOOL, where notify/faxrcvd are run from):

etc/templates/$TEMPLATE/<template name>

So, with TEMPLATES unset, you get the default templates. If TEMPLATES=fr, you would use the templates in:

etc/templates/fr/<template name>

We've created a basic set of templates, and a set of translations of them, based on our reading and knowledge of the current faxrcvd and notify scripts. We're sure there are problems with some of the templates, so corrections are welcome.

Templates are of the format:

	From: FAX Agent <$FROMADDR>
	Subject: Fax received from "$SENDER"
	Content-type: text/plain; charset=us-ascii

	$FILE (ftp://$HOSTNAME:4559/$FILE):                                  
		  Sender: $SENDER
		   Pages: $PAGES
		 Quality: $QUALITY
		    Size: $PAGE
		Received: $RECEIVED
	 Time To Receive: $TIMETORECV
	     Signal Rate: $SIGNALRATE
	     Data Format: $DATAFORMAT
	   Error Correct: $ERRCORRECT
		 CallID1: $CALLID1
		 CallID2: $CALLID2
	     Received On: $DEVICE
		  CommID: $COMMID (ftp://$HOSTNAME:4559/log/$COMMID)

Templates are 2 sections, separated by a blank line. The "header" section is included in the headers of the e-mail. So the template can actually specify the content-type it is, including any charset, etc.

This means that you *can* make your template something like:

	From: ...
	Subject: ...
	Content-type: text/html

	<html>
	 <body>
	  <table>
	   <tr><td>Sender:</td><td>$SENDER</td></tr>
	   ....
	 </body>
	</html>

Changelog

A complete list of changes since 4.3.1 is as follows:

Added sample HTML templates to demonstrate templating features (9 Feb 2007)
Added error exit codes to faxinfo (7 Feb 2007)
PAM reworked to use complete sessions independantly (25 Jan 2007)
Added debian/ directory with rules to create a simple Debian package (21 Jan 2007)
Simplify/Unify mime encoder selection and use (9 Jan 2007/29 Jan 2007)
Add the Include: option for Config file options (8 Jan 2007)
Redirected unwanted output from pd2pdf while running notify (24 Dec 2006)
Use @SCRIPT_SH@ for bin/ scripts to allow configure selection (23 Dec 2006)
Updated pollrcvd to use templates (22 Dec 2006)
Moved default templates to etc/tempates/en/ to clean up etc/templates/ (22 Dec 2006)

@@ Line 5: / Line 5: @@
-=Current beta (4.3.2beta2)=
+=Current release candidate (4.3.2rc1)=
 The source can be downloaded from:
-ftp://ftp.hylafax.org/source/BETA/hylafax-4.3.2beta2.tar.gz
+ftp://ftp.hylafax.org/source/BETA/hylafax-4.3.2rc1.tar.gz
@@ Line 79: / Line 79: @@
 ==Changelog==
-A complete list of changes from 4.3.2 is as follows:
+A complete list of changes since 4.3.1 is as follows:
+* Added sample HTML templates to demonstrate templating features (9 Feb 2007)
+* Added error exit codes to faxinfo (7 Feb 2007)
 * PAM reworked to use complete sessions independantly (25 Jan 2007)
 * Added debian/ directory with rules to create a simple Debian package (21 Jan 2007)

Personal tools

Difference between revisions of "Beta Versions"