On Sat, Aug 18, 2012 at 8:31 PM, Todd And Margo Chester
<[log in to unmask]> wrote:
> Hi All,
>
> SL 6.3, x64
>
> Anyone come up with a way to print to Hylafax through CUPS?
>
> -T

This is not really a Scientific Linux question: it really belongs over
in the HylaFAX mailing lists. But you happen to have lucked out with
me around. I *wrote* the SunOS ports, and some of the early RPM's, for
HylaFAX and am still on the mailing lists.

Note that there are two major forks now: the original HylaFAX at
www.hylafax.org, but where the mailing list seems to be dead, and the
HylaFAX+ fork over at hylafax.sourceforge.net, where development is
ongoing and some of the original developers are still active. (Just
glanced back at my old mailing list at www.hylafax.org, that's scary
old!!) I'd recommend using HylaFAX+.

All that said, CUPS, and the much older LPD toolkits, don't have a
graceful way to wrap the extra information such as the fax target's
phone number, into a print job after you've fired the print document
off to CUPS. The RFC's for the "lp" protocol are pretty specific, and
don't include this sort of thing. It's not like the Windows
environment where the print queues are a customized and individualized
mass of settings and front end drivers to pre-process print requests
before feeding them to the print queues, it's he actual print queue.

By the time the print job gets handed to CUPS, it's supposed to be an
actual print job. In *theory*, I suppose you could do a wrapper to
deduce who the sender was, what X session or tty they're running from,
and do a pop-up. But then that would fail for scheduled fax jobs,
which would have to use something else. And you'd have to specify
print requests to hit that particular printer. If you're going to all
that work of setting the particular printer, why not go to the extra
wrap of piping the print job to a pre-processor that will set up the
fax?