HYLAFAX-INFO(5)
π HYLAFAX-INFO(5) π
okay bestie, this is the File Formats Manual page for HYLAFAX-INFO(5) and honestly? it's giving the little black book of fax machines. let's get into it π
β¨ NAME β¨
info β the remote device capability database πΈ
π¦ DESCRIPTION π¦
so there's this info subdirectory inside the HylaFAX spooling area, right? it's where all the ~tea~ about devices that have been called gets stored: their capabilities, their status, everything. one file per device, and the filename is literally made out of the remote device's fully-qualified phone number. iconic. no cap.
the files themselves are plain ASCII. simple. every line looks like this:
[&]tag: value
where a tag names some capability and a value is a string, a number, or a boolean. and here's the cute part β if you slap an optional `&' at the front of the line, that tag's value is locked down and the server will not update it. this is so useful for restricting which capabilities get used with a particular machine. π
here's everything that gets recorded:
calledBeforeβ boolean β device has previously answered at this numberdialFailuresβ number β count of consecutive failed dial operationshasV34Troubleβ boolean β there is difficulty sending to this destination with V.34hasV17Troubleβ boolean β there is difficulty sending to this destination with V.17lastDialFailureβ string β reason for last failed dial operationlastSendFailureβ string β reason for last failed send attemptmaxPageWidthβ number β maximum page width in pixels in normal resolutionmaxPageLengthβ number β maximum page length in millimetersmaxSignallingRateβ string β maximum signalling rate (bits/sec) to useminScanlineTimeβ string β minimum scanline timepagerMaxMsgLengthβ number β length of longest allowed text messagepagerPasswordβ string β password string send to service providerpagerSetupCmdsβ string β commands for setting up modem for a specific service providerpagerTTYParityβ string β parity & # bits configuration for IXO/TAP communicationpageSourceβ string β parameter to tell the paging central who we arepagingProtocolβ string β protocol (IXO or UCP) for this providerremoteCSIβ string β remote device Called Subscriber IdentificationremoteNSFβ string β remote equipment Non-Standard Facilities informationremoteDISβ string β remote Digital Identification Signal: capabilitiessendFailuresβ number β count of consecutive failed send attemptssupportsBatchingβ boolean β accepts batching protocolsupportsHighResβ boolean β accepts 196 line/inch images (obsolete)supportsVResβ number β vertical resolution support bitmasksupports2DEncodingβ boolean β accepts Group 3 2D encodingsupportsMMRβ boolean β accepts Group 4 encodingsupportsPostScriptβ boolean β accepts Adobe POSTSCRIPT transfer protocol
the HylaFAX scheduler, faxq(8), reads all this when it's deciding whether a call should even happen and when it's prepping documents to send. if the remote device's capabilities are known, document prep gets constrained and/or optimized to match them. if they're not known? documents get prepared with zero regard for the remote's capabilities, and if a capability mismatch shows up, the session gets terminated and the documents get reformatted using whatever capabilities were just discovered. messy but it works π
the calledBefore item is what faxsend checks to decide whether to redial a number when it hits certain errors. like β if a dialing command comes back with a `NO CARRIER' result, the number won't be retried unless it's been dialed successfully before. so basically, don't expect a retry on a stranger β¨
the minScanlineTime item is the minimum scanline time parameter used for facsimile transmissions. acceptable values are: `0ms', `5ms', `10ms/5ms', `10ms', `20ms/10ms', `20ms', `40ms/20ms', and `40ms'. (and if you see a value shaped like X/Y, that means use X for 98 lpi images and Y for 196 lpi images. iykyk π«)
the pagerTTYParity item sets the communication parameters for talking to the IXO/TAP service provider. acceptable values: `even' (7 bits, even parity), `odd' (7 bits, odd parity), and `none' (8 bits, no parity). specify nothing at all and you get `even', per the standard. default behavior, we love her π
the pagerMaxMsgLength, pagerPassword, and pagerTTYParity items can be set up to match whatever a pager service provider requires β and they typically get locked down so their values don't get lost during updates. protect the info, bestie π«Ά
pagerSetupCmds lets you define AT commands for setting up the modem for a specific service provider. heads up though: this value overwrites the settings defined in hylafax-config(5). it does not play nice, it just wins π₯
pageSource can be used to tell the paging central who we are. it usually holds a SMS answerable mobile number. it's only used for the UCP part of sendpage(8). Note: this parameter should be used from user-land sendpage(1) and will be removed later. (rip, she's on her way out π)
pagingProtocol defines which protocol β UCP or IXO β gets used to send the message to the service provider. it defaults to `ixo'; for UCP, set `ucp'.
π NOTES π
faxsend, pagesend, and faxq automatically create and update entries in the info directory as required. no manual labor, they just do it π
the data in this directory is simply a cache of remote capabilities, and β except for locked down items β it can be safely purged at any time. the faxcron(8) script, for example, periodically purges unlocked entries in this directory that have not been accessed in 30 days. spring cleaning, scheduled β¨
when the first batching attempt fails, supportsBatching gets set to false. it must be manually altered to re-enable batching to the destination. no take-backs, you have to do it yourself π€
β οΈ restricting the capabilities used with a particular machine to a value other than those that are mandatory can cause documents to be sent outside of an acceptable range for the receiver. like, for real for real β be careful with this one.
πΈ SEE ALSO πΈ
and that's the whole page, bestie π this version dropped February 10, 1996 and lives in the HYLAFAX-INFO(5) manual β go forth and fax responsibly, you absolute icon πππ¦
π¦ where this page comes from
- debian bookworm: hylafax-server 3:6.0.7-5
- debian trixie: hylafax-server 3:6.0.7-11.1
- ubuntu jammy: hylafax-server 3:6.0.7-3.1
- ubuntu noble: hylafax-server 3:6.0.7-7
- ubuntu questing: hylafax-server 3:6.0.7-13
- ubuntu resolute: hylafax-server 3:6.0.7-13build1
- ubuntu stonking: hylafax-server 3:6.0.7-13build1
- Copyright (c) 1990-1996 Sam Leffler
- Copyright (c) 1991-1996 Silicon Graphics, Inc
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms