Debian Bug report logs - #499795
Hylafax+

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Philipp Kempgen <philipp.kempgen@amooma.de>

To: submit@bugs.debian.org

Subject: Hylafax+

Date: Mon, 22 Sep 2008 14:33:18 +0200

Package: hylafax-server
Severity: wishlist

Ist there a reason not to switch to HylaFax+?
( http://hylafax.sourceforge.net/ )

Should hylafax+ go into a separate package?


   Philipp Kempgen

Message #10 received at 499795@bugs.debian.org (full text, mbox, reply):

From: "Giuseppe Sacco" <giuseppe@eppesuigoccas.homedns.org>

To: "Philipp Kempgen" <philipp.kempgen@amooma.de>, 499795@bugs.debian.org

Subject: Re: Bug#499795: Hylafax+

Date: Mon, 22 Sep 2008 14:44:17 +0200 (CEST)

Hi Philipp,

> Ist there a reason not to switch to HylaFax+?
> ( http://hylafax.sourceforge.net/ )
>
> Should hylafax+ go into a separate package?
[...]

There is no specific reason to prohibit hylafax+ to get packaged in Debian. Anyway,
it will not be hylafax package: it should be a different package that will probably
conflict with this package sice they share a large list of pathnames.

What would you get with hylafax+ that you are missing with hylafax?

Bye,
Giuseppe

Message #15 received at 499795@bugs.debian.org (full text, mbox, reply):

From: Philipp Kempgen <philipp.kempgen@amooma.de>

To: 499795@bugs.debian.org

Cc: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>

Subject: Re: Bug#499795: Hylafax+

Date: Mon, 22 Sep 2008 15:19:41 +0200

Giuseppe Sacco schrieb:
> There is no specific reason to prohibit hylafax+ to get packaged in Debian. Anyway,
> it will not be hylafax package: it should be a different package that will probably
> conflict with this package sice they share a large list of pathnames.

Sure.

> What would you get with hylafax+ that you are missing with hylafax?

Good question. :-)
We're using HylaFax+ to receive faxes via IaxModem from Asterisk
(a lot of people do that) and a GUI which talks to the HylaFax+
server via the FTP-like protocol (sending, job management etc.).
We tested both HylaFax 4.4.x and HylaFax+ 5.x. As far as I can
remember the latter supports an extended protocol (more "jparm"s
or something) which is required to store meta-data for multi-user
setups.

   Philipp Kempgen

Message #20 received at 499795-maintonly@bugs.debian.org (full text, mbox, reply):

From: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>

To: Philipp Kempgen <philipp.kempgen@amooma.de>

Cc: 499795-maintonly@bugs.debian.org

Subject: Re: Bug#499795: Hylafax+

Date: Mon, 22 Sep 2008 15:37:50 +0200

Il giorno lun, 22/09/2008 alle 15.19 +0200, Philipp Kempgen ha scritto:
> Giuseppe Sacco schrieb:
[...]
> > What would you get with hylafax+ that you are missing with hylafax?
> 
> Good question. :-)
> We're using HylaFax+ to receive faxes via IaxModem from Asterisk
> (a lot of people do that) and a GUI which talks to the HylaFax+
> server via the FTP-like protocol (sending, job management etc.).
[...]

I am wondering what client you are using, so that I may better check
what is missing. Is it an open source software?
Hylafax upstream maintainers are preparing a new release. There has been
a short thread, one or two weeks ago, on the hylafax-users mailing list,
about what people would like to see included in next hylafax release. If
you have specific request, you may try to ask there.

Bye,
Giuseppe

Message #25 received at 499795@bugs.debian.org (full text, mbox, reply):

From: Philipp Kempgen <philipp.kempgen@amooma.de>

To: 499795@bugs.debian.org

Subject: Re: Bug#499795: Hylafax+

Date: Mon, 22 Sep 2008 16:41:20 +0200

Giuseppe Sacco schrieb:

> I am wondering what client you are using, so that I may better check
> what is missing. Is it an open source software?

It's a really simple custom client. Open source and GNU GPL.
https://svn.amooma.com/gemeinschaft/trunk/opt/gemeinschaft/inc/cn_hylafax.php
(the SSL certificate belongs to a different domain but don't worry)

> Hylafax upstream maintainers are preparing a new release. There has been
> a short thread, one or two weeks ago, on the hylafax-users mailing list,
> about what people would like to see included in next hylafax release. If
> you have specific request, you may try to ask there.

If I could remember what it was exactly I could ask for it. :-)
All I can tell is that HylaFax+ worked but HylaFax didn't.
(There must be a reason for the HylaFax+ folks to continue the
project after all.)
Never mind.

   Philipp Kempgen

Message #30 received at 499795@bugs.debian.org (full text, mbox, reply):

From: Rémi Letot <hobbes@poukram.net>

To: 499795@bugs.debian.org

Subject: feature in hylafax+ only

Date: Thu, 15 Jan 2009 00:07:45 +0100

Hello,

here is a feature found in hylafax+ that hylafax in debian don't have : 
passive mode network transfer.

I use an internet hosted fax server. With debian's hylafax-client, a 
simple internet router like I find in most small companies is a major 
PITA because of the active transfer mode. Hylafax+ has a PassiveMode 
option that works around that problem in most cases.

Hylafax is a great software, and I think the development version has 
passive transfers, but their release schedule is dead slow :-(

Thanks for your work,
-- 
Rémi

Message #35 received at 499795@bugs.debian.org (full text, mbox, reply):

From: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>

To: Rémi Letot <hobbes@poukram.net>, 499795@bugs.debian.org

Subject: Re: Bug#499795: feature in hylafax+ only

Date: Mon, 09 Feb 2009 13:32:41 +0100

Hi Rémi,

Il giorno gio, 15/01/2009 alle 00.07 +0100, Rémi Letot ha scritto:
> Hello,
> 
> here is a feature found in hylafax+ that hylafax in debian don't have : 
> passive mode network transfer.
[...]
> Hylafax is a great software, and I think the development version has 
> passive transfers, but their release schedule is dead slow :-(

That's true: PASV has been included in hylafax when ipv6 has been added,
a few weeks ago. Moreover, I do not have any idea about when the next
release will happen. I think Hylafax releases should happen in a more
short timeframe, but I have to admit that Debian usually release more
slowly than hylafax :-)

So, if hylafax would release more often, we could have in Debian an
hylafax 6 months old, instead of one year old. Moreover we could have
more frequently an update version in testing.

I'll try to see what I might do. I'll start asking about next schedules
on hylafax-devel list.

Bye,
Giuseppe

Message #42 received at 499795@bugs.debian.org (full text, mbox, reply):

From: Lee Howard <faxguy@howardsilvan.com>

To: Chris Coleman <chris@espacenetworks.com>

Cc: 499795@bugs.debian.org, Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>, Rémi Letot <hobbes@poukram.net>, lists@kempgen.net

Subject: Re: HylaFAX+

Date: Sun, 06 Sep 2015 20:04:02 -0700

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 
the list has only grown even more.  Consider this one simple feature in 
HylaFAX+: the ability for faxq to relay (or "proxy") jobs to other 
HylaFAX servers treating those other servers as "virtual modems" of a 
sort.  Hence, a network of HylaFAX+ servers can "load balance" and 
"least-cost route" jobs between them in very inventive and imaginative 
ways to accomplish better throughput, deliverability, and so forth.

Consider a deployment of a HylaFAX+ server at an office that can route 
it's outbound faxes out through multiple on-line fax services all based 
on various bits of intelligent decision-making.

Anyway, that's just one of the features in HylaFAX+ that came about 
after that "differences" page was last updated.

Take a look at the ChangeLogs for the HylaFAX+ releases and then look at 
the same for the hylafax.org releases for the same period of time.  It 
should be very telling.

Thanks,

Lee.

Message #47 received at 499795@bugs.debian.org (full text, mbox, reply):

From: Chris Coleman <chris@espacenetworks.com>

To: 499795@bugs.debian.org, Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>, Rémi Letot <hobbes@poukram.net>, lists@kempgen.net

Cc: Lee Howard <faxguy@howardsilvan.com>

Subject: HylaFAX+

Date: Sun, 6 Sep 2015 22:34:22 -0400

[Message part 1 (text/plain, inline)]

package: hylafax-server
severity: serious (Chris intends to upgrade it from wishlist to serious, 
for reasons, see below)

Giuseppe, Remi, Phillipp,
I'm writing you about this excellent Bug that Phillip Kempgen filed in 
2008, why isn't HylaFAX+ included in debian?
Giuseppe you had question about what makes HylaFAX+ so much better, and 
I've got the answers for you...
Short version: I nominate you Giuseppe to make HylaFAX+ 5.5.6 available 
as a deb package in the main debian repo.
Long version:
The most recent version 5.5.6 was released April 2015, existing since 
2005 as free open source code available on sourceforce.
HylaFAX+ has more up to date features, performance improvements, and 
bugs fixes than the Hylafax 6.0.6 (released 2012) that you currently offer.
The projects are probably 95% similar, they forked in 2005, but in 2012 
Hylafax got into a leapfrog race on version numbers vs Hylafax+ 5.5.6.
HylaFAX+ is superior because of many enhancements and bug fixes.
For example it solves a longstanding issue of incompatibility with color 
and grayscale faxes.  It produces compatible tiff and pdf pages, while 
Hylafax 6.0.6 can't (due to a complicated bug about ITULab colorspace 
unable to be understood/converted by libtiff and libjpeg, and those 2 
package developers despite receiving patches, unable to change their 
code without causing breakage elsewhere, thus forcing a manual patch and 
recompile from source of not only libtiff and libjpeg but also of many 
other dependent packages on the system, which is totally 
ridiculous/unfeasible, and this has been stuck that way in hylafax for 
about ten years since 2005.).
HylaFAX+ solved this bug by enlisting LittleCMS developer Marti Maria to 
solve this problem without the image degradation from having to 
decompress and re-compress the jpeg image of the page.
Everyone who is aware of the two packages, installs Hylafax+.
You should at least offer both Hylafax, and Hylafax+, packages, and let 
either be installed, obviously marked as conflicts with the other one, 
as you'd mentioned.
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

 * 1. support for sending and receiving color faxes (without patching
   libraries)
   <http://hylafax.sourceforge.net/docs/hylafax-differences.php#colorfaxes>

 * 2. simplified default faxrcvd, notify, and pollrcvd scripts for
   easier customization
   <http://hylafax.sourceforge.net/docs/hylafax-differences.php#mailscripts>

 * 3. faxq batching support was not needlessly rewritten and includes
   greater protection against resource overutilization
   <http://hylafax.sourceforge.net/docs/hylafax-differences.php#nofaxqrewrite>

 * 4. extended presentation of CallID
   <http://hylafax.sourceforge.net/docs/hylafax-differences.php#callidpresentation>

 * 5. intelligent real-time format compression conversion (RTFCC)
   <http://hylafax.sourceforge.net/docs/hylafax-differences.php#intelligentrtfcc>

 * 6. ModemSetOriginCmd, ModemDialCmd, FAXNAME job parameter, and -e
   "name" and -u "number" sendfax options
   <http://hylafax.sourceforge.net/docs/hylafax-differences.php#modemsetorigincmd>

 * 7. enhanced and improved fax image preparation
   <http://hylafax.sourceforge.net/docs/hylafax-differences.php#faximage>
 * 8. numerous faxmail enhancements
   <http://hylafax.sourceforge.net/docs/hylafax-differences.php#faxmail>
 * 9. etc/FaxAccounting reliable event hook, particularly for adding
   xferfaxlog data to a database
   <http://hylafax.sourceforge.net/docs/hylafax-differences.php#faxaccounting>

 * 10. xferfaxlog extensions (SUBMIT records and jobinfo field)
   <http://hylafax.sourceforge.net/docs/hylafax-differences.php#xferfaxlog>

 * 11. inbound faxes can be configured to utilize info files for
   automated fax parameters configuration
   <http://hylafax.sourceforge.net/docs/hylafax-differences.php#inbounduseofinfo>

 * 12. support for taglines using UTF-8 fonts
   <http://hylafax.sourceforge.net/docs/hylafax-differences.php#utf8taglines>

 * 13. More feature support (i.e. JBIG, JPEG) in the Class 2/2.0/2.1
   driver
   <http://hylafax.sourceforge.net/docs/hylafax-differences.php#class2featuresupport>
 * 14. StaggerCalls feature for faxq
   <http://hylafax.sourceforge.net/docs/hylafax-differences.php#staggercalls>

 * 15. place non-ready ModemReadyState onto modem status string and add
   "exempt" option
   <http://hylafax.sourceforge.net/docs/hylafax-differences.php#modemreadystate>

 * 16. direct LDAP authentication support (without PAM)
   <http://hylafax.sourceforge.net/docs/hylafax-differences.php#ldapauth>
 * 17. -nointeractive option for faxsetup and faxaddmodem (like
   configure)
   <http://hylafax.sourceforge.net/docs/hylafax-differences.php#nointeractive>

 * 18. no JobControlWait option
   <http://hylafax.sourceforge.net/docs/hylafax-differences.php#jobcontrolwait>


-Chris Coleman

[Message part 2 (text/html, inline)]

Message #52 received at 499795@bugs.debian.org (full text, mbox, reply):

From: Lee Howard <faxguy@howardsilvan.com>

To: 499795@bugs.debian.org

Cc: Chris Coleman <chris@espacenetworks.com>, Giuseppe Sacco <eppesuig@debian.org>, Joachim Wiedorn <joodebian@joonet.de>

Subject: SSL Fax - HylaFAX+ 7.0.0

Date: Wed, 24 Apr 2019 15:07:01 -0700

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 either install HylaFAX+ from source or to
switch distributions.  My observations are that users are doing both of
those in roughly equal measures.

It would take very little effort to simply change the source tarball in
the package build and make whatever needed modifications are required
(probably very few) to the patches.

Message #57 received at 499795@bugs.debian.org (full text, mbox, reply):

From: Joachim Wiedorn <joodebian@joonet.de>

To: Lee Howard <faxguy@howardsilvan.com>

Cc: 499795@bugs.debian.org, Chris Coleman <chris@espacenetworks.com>, Giuseppe Sacco <eppesuig@debian.org>

Subject: Re: SSL Fax - HylaFAX+ 7.0.0

Date: Sat, 11 May 2019 10:31:30 +0200

[Message part 1 (text/plain, inline)]

Hello Lee,

In the past I tried moving to hylafax+ on my local server. I use hylafax
on my server with ISDN card (germany). So I have to use the package
capi4hylafax, too:  http://www.joonet.de/sources/capi4hylafax/

I have tried it with the config of the old hylafax package and without
this config. Until now I haven't any success using FAX together with
hylafax+. Perhaps it is a problem with the package capi4hylafax? But I can
only test it with my ISDN card.

Do you have optimized configuration for hylafax+ on a Debian system, which
run without errors?

---
Have a nice day.

Joachim (Germany)

[Message part 2 (application/pgp-signature, inline)]

Send a report that this bug log contains spam.