OpenBSD Handbook

Current snapshot · amd64 · Generated 2026-09-16

hylafax-7.0.11p0-a4

send/receive faxes and share modems

Back to search · Project homepage

Other branch: OpenBSD 7.9 release package details

Description

HylaFAX is an enterprise-class system for sending and receiving facsimiles as well as for sending alpha-numeric pages. The software is designed around a client-server architecture. Fax modems may reside on a single machine on a network and clients can submit an outbound job from any other machine on the network. Client software is designed to be lightweight and easy to port. HylaFAX is designed to be very robust and reliable. The fax server is designed to guard against unexpected failures in the software, in the configuration, in the hardware and in general use. HylaFAX can support multiple modems and a heavy traffic load. If you expect to send more than a few facsimiles a day, then HylaFAX is the fax package for you!!

Package information

Ports path
comms/hylafax,a4
Package architecture
amd64
Maintainer
The OpenBSD ports mailing-list <ports@openbsd.org>
Categories
comms
Available flavors
a4
Only for architectures
aarch64, amd64, arm, i386, mips64, mips64el, powerpc, powerpc64, riscv64, sparc64, alpha, hppa, m88k, sh

These are ports metadata. Binary availability depends on the release, architecture and mirror. Build and test dependencies are not an installation checklist.

Direct dependencies

Library

Runtime

Build

OpenBSD README

This README contains unresolved ports variables. It is source documentation; commands containing these variables require adjustment.

+-----------------------------------------------------------------------
| Running hylafax on OpenBSD
+-----------------------------------------------------------------------

Post-installation steps
=======================
Hylafax needs some manual configuration before it is usable.

If you have upgraded HylaFAX on a system which was using the legacy UUCP
account, please see the section below to update ownership of files.

Make sure that you have configured HylaFAX before running faxq:
	server: ${TRUEPREFIX}/sbin/faxsetup
	modems: ${TRUEPREFIX}/sbin/faxaddmodem
	incoming calls: /etc/ttys

When you are asked to specify the name of tty device, use a tty device
existing on your architecture instead of "ttyd1".

For accepting incoming FAX/data calls, modify /etc/ttys(5) to contain
something like this:

    tty00	"${TRUEPREFIX}/sbin/faxgetty"	dialup	on

and send a SIGHUP to init(8).


Updating file ownership to use the new _hylafax account
=======================================================
To update the ownership of directories and files in the HylaFAX spool directory,
perform one of the following.

If the legacy UUCP account is still registerd;

    find ${TRUEPREFIX}/libdata/hylafax -user uucp -exec /sbin/chown 902 {} \;
or
    find ${TRUEPREFIX}/libdata/hylafax -user uucp -exec /sbin/chown _hylafax {} \;

Alternatively, if you have removed the legacy UUCP account, and assuming its uid
was 66;

    find ${TRUEPREFIX}/libdata/hylafax -user 66 -exec /sbin/chown _hylafax {} \;


References
==========
Additional documentation at https://hylafax.sourceforge.io/.

Installing and updating packages · Package details as JSON