From owner-freebsd-questions@FreeBSD.ORG Sun Apr 10 21:34:20 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3690616A4CE for ; Sun, 10 Apr 2005 21:34:20 +0000 (GMT) Received: from green.rahul.net (green.rahul.net [192.160.13.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9F7743D48 for ; Sun, 10 Apr 2005 21:34:19 +0000 (GMT) (envelope-from conover@rahul.net) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by green.rahul.net (Postfix) with SMTP id 93C71BE8BF for ; Sun, 10 Apr 2005 14:34:19 -0700 (PDT) Received: (qmail 7656 invoked by uid 4199); 10 Apr 2005 21:34:13 -0000 Resent-Message-ID: <20050410213413.7655.qmail@rahul.net> Resent-From: conover@rahul.net Resent-Date: Sun, 10 Apr 2005 14:34:13 -0700 Resent-To: freebsd-questions@freebsd.org Received: (qmail 2988 invoked by uid 4199); 10 Apr 2005 20:47:01 -0000 Received: (qmail 2970 invoked by uid 4199); 10 Apr 2005 20:47:01 -0000 Message-ID: <20050410204701.2969.qmail@rahul.net> In-Reply-To: References: <4259856C.5040604@makeworld.com> X-Mailer: VM 6.99 under Emacs 20.7.2 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Loop: conover-bcc@johncon.com From: conover@rahul.net (John Conover) To: freebsd-questions@freebsd.org Date: Sun, 10 Apr 2005 13:47:00 -0700 Subject: Re: fax4CUPS X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John Conover List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Apr 2005 21:34:20 -0000 Gert Cuykens writes: > On Apr 10, 2005 9:58 PM, Chris wrote: > > Gert Cuykens wrote: > > > Can we have this in ports ? > > > > > > http://vigna.dsi.unimi.it/fax4CUPS/ > > > > Are you volunteering? > > > > Anything is possible, but nothing is easy. > > > > How do you mean ? > > I did not install it yet but it sounds useful if cups could handle a > serial fax like a printer :) > > Aldo i think the script can only send faxes and not handle incoming > faxes like printing them or sending them to a mailbox directory. But i > am sure you can add some magic faxing features to it :) > > 10$ its going to be a popular port and for people like you not that > hart to add some fax incomming features :) With a little bit of luck > you don't have to compile anything :) It does work well, (as per the sparse docs in the tar file.) You can use efax for incoming faxes, (or better, hylafax, if you can talk root@heaven.org into coming down and configuring it for you,) and the fax4CUPS does appear as a printer according to lpstat -a, and does send faxes, (saved as a postscript file out of openoffice.org, etc.) You will have to use cup's lpr -j option to tell it the "fax printer" what number to send the fax to, (so you will probably have to configure a printer in everyone's openoffice.org, etc.) The lpadmin command to install the cups/efax printer is: lpadmin -p efax -L machine -D fax -E -v efax:/dev/ttyXX -m efax.ppd Where efax.ppd is installed in probably /usr/share/cups/model/, and the efax script, (with the first 8 lines modified for your configuration,) installed in probably /usr/lib/cups/backend/. Note: if "efax answer" is running on /dev/ttyXX from /etc/inittab, it may be necessary to disable "efax answer" for the lpadmin command, but only to install the "fax printer," (apparently, lpadmin doesn't like other things listening on its serial printer ports when it installs the printer.) If you use efax or hylafax for incoming, enable MIME e-mailing of the fax to a faxmaster, who distributes the file to the appropriate machine-its default for hylafax. For efax, configure /etc/efax.rc and /usr/bin/fax, (these are some script changes,) to send the fax attachment as a postscript file so they can be read with gv/ghostscript, (which probably came with your cups installation.) The efax/tiff file formats come out half size if a low resolution fax is received, which is corrected if postscript is used. Recommendation: YMMV, but hylafax is a bit difficult to configure, but is very robust once running; efax is probably preferable for non-industrial strength applications. FWIW ... John -- John Conover, conover@rahul.net, http://www.johncon.com/