HylaFAX HylaFAX+ Code Repository

This makes faxsetup fix blind references in Fontmap.HylaFAX.

Apparently Ghostscript is okay with Fontmap.GS when it references named fonts whose files are not explicitly given elsewhere. However, this does not work for us.

So, this fix follows an approach similar to what Chris Severance did in "fmfix.pl" file in his archlinux aur "hylafaxplus" repository... but we don't (and can't) use perl.

It shouldn't be necessary to keep proxy server clocks synchronized with each other.
We have been specifying SENDTIME and LASTTIME based on our own clock, but that can be problematic especially if the two servers' clocks are quite out-of-sync.
If we just don't specify SENDTIME then the remote will default to "now" (on its clock) which is what we want, anyway. And, LASTTIME is given as a relative value, anyway. We just need a means to interface with that.

So these changes resolve this issue by simply not specifying SENDTIME and by providing LASTTIME without referencing our own clock.

Passwords created by faxadduser and "SITE ADDUSER" only supported 8 characters.

Characters after the 8th were ignored and unused. This change allows those two user-adding features to support secure passwords longer than 8 characters.

This adds the admin login option for faxstat.

This adds the ProxyJobTag jobcontrol feature.

The calculation for Class1RestrictPoor[Destinations/Senders] was grossly incorrect.

The result of the problem was that restrictions were placed on good-quality senders and not on poor-quality ones... which is completely wrong.

Addresses a documentation deficiency raised by hylafax.org's Bugzilla #960.

This adds the application/binary MIMEConverter.

Microsoft Oultook apparently uses application/octet-stream and application/binary interchangeably.

These files were not properly added to the SVN repository in Commit [r2344].

They were present in the 5.5.6 release tarball, however.

DynamicConfig assignment of Class 1 modem data format support has never worked properly.

The pokeConfig() function was properly *adding* support for the various formats, but it was not properly *removing* support for them... which ultimately made them not take effect until the subsequent call handled by the modem.

These changes explicity add *and* remove support for the various data formats (MMR, JBIG, JPEG) as instructed by DynamicConfig.

[This commit was originally made to the Sourceforge SVN repository on Thu Jul 16 2015 05:06:49 GMT+0000 (UTC), however, it was lost by the storage fault at Sourceforge later that day and was not present in the back-up.]