Bug#499795: SSL Fax - HylaFAX+ 7.0.0

With the HylaFAX+ 7.0.0 release earlier this month there is now another significant feature missing from the Debian HylaFAX package. Debian users who wish to use SSL Fax or any of the other myriad fax features features found in HylaFAX+ that have been listed here before continue to be forced to

Bug#499795: HylaFAX+

On 09/06/2015 07:34 PM, Chris Coleman wrote: As promised, here is a page with the list of bugfixes and performance improvements that HylaFAX+ has over HylaFAX: http://hylafax.sourceforge.net/docs/hylafax-differences.php That is an old list - more than a few years old now. During these years

Bug#682824: hylafax-server: creates world writable directory

The default install from source code (tarball) doesn't do this. Observe /var/spool/hylafax/tmp on such an installation: drwx-- 2 uucp uucp69632 Aug 14 10:48 tmp So it seems to be unique to Debian package. Thanks, Lee. -- To UNSUBSCRIBE, email to

Bug#434310: /usr/share/gs-gpl/fonts does not exist

Package: gs-gpl Version: 8.54.dfsg.1-5 Run 'gs -h' and you'll get the following in the output... Search path: . : /usr/share/gs-gpl/8.54/lib : /usr/share/gs-gpl/8.54/Resource : /usr/share/gs-gpl/fonts : /var/lib/defoma/gs.d/dirs/fonts : /usr/share/ghostscript/fonts :

Bug#363464: getting typerules to catch non-ASCII text

Here's the typetest output for the attachment... [EMAIL PROTECTED] hylafax]# typetest fax.txt match against (..., 439) rule: offset 0 ascii = -- failed (unprintable char 0xc3) no match fax.txt: Can not determine file type HylaFAX uses isprint() to determine whether or not the ascii (which

Bug#369759: killtime referring to time-in-queue and not time since first attempt

The killtime is designed to prevent the job from being in the queue, unsent too long. It's not designed to assist in the control of how many attempts there should be or how much time is allowed between attempts. Let's say that I have an important fax that needs to get sent urgently. I

Bug#122459: xferfaxstats/recvstats date+time information

The xferfaxlog does have the time and date information for each activity it records, so the information *is* available to the system. xferfaxstats and recvstats, however, were designed to be statistical tools giving sums and averages and such... so looking to them to provide a historical

Bug#309684: MaxConcurrent calls not working

MaxConcurrentCalls works for me. Are you sure that you're not noticing the effects of batching and misinterpreting them? Lee. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]