pagermap(5) [linux man page]
PAGERMAP(5) File Formats Manual PAGERMAP(5) NAME
pagermap - SNPP pager identifier mapping file DESCRIPTION
The file etc/pagermap (by default) is used by the SNPP support in hfaxd(8) to map pager identifiers specified with the PAGE directive to IXO/TAP or SMS service providers and optionally a Pager Identification Number (PIN). (The ability to specify a PIN makes it possible to define aliases for pagers.) Note that etc/pagermap may be called a different name; the filename is specified with the PagerIDMapFile con- figuration parameter read by hfaxd(8). The pagermap file is comprised of one or more lines of the following format: <pattern> <dialstring>[/<pin>] Each line specifies a <pattern> that is matched against a client-specified pager identifier string. A pattern may be a plain string or a POSIX 1003.2 extended regular expression; plain strings must compare exactly while regular expressions are unanchored and any substring match constitutes a ``hit''. Regular expressions are distinguished from plain strings by the presence of one or more of the magic charac- ters ``[]*.^$-+{}()''. The <dialstring> identifies the IXO/TAP or SMS service provider to contact for delivery or, if <dialstring> is the string ``reject'' (case insensitive) then the pager identifier is rejected. If the optional <pin> is specified then it used to deliver the page instead of the client-specified identifier. If the matching expression is a regular expression the optional <pin> may reference the entire string matched by the regular expression with the ``&'' character. Substrings matched with the ``(...)'' constructs may be referenced by using `` '' where n is a single numeric digit between 1 and 9 that refers to the n-th matched substring; c.f. re_format(7), sed(1), etc. hfaxd processes lines in the mapping file sequentially; the first line with a pattern that matches the pager identifier is used to deliver or reject the page. Lines that begin with a ``#'' are treated as comments and discarded. Leading whitespace on a line is also ignored. EXAMPLES
The following defines an alias for ``sam'', submits all destinations with a leading ``Sky'' to a particular IXO/TAP service provider, and otherwise rejects the pager ID. (Note that using alphabetics in dial strings requires a dialstring rules file that understands how to map alphabetics to key codes--or one that passes them through verbatim.) # a simple mapping example sam 5551212/99 Sky(.*) 1800SkyTel/1 .* reject SEE ALSO
hfaxd(8), hylafax-server(5) May 8, 1996 PAGERMAP(5)
Check Out this Related Man Page
HOSTS.HFAXD(5) File Formats Manual HOSTS.HFAXD(5) NAME
hosts.hfaxd - HylaFAX client access control list DESCRIPTION
The ASCII file etc/hosts.hfaxd in the HylaFAX spooling area specifies the hosts and users that are permitted to access services through the hfaxd(8) process. This file must exist for client access; if it is not present then hfaxd will deny all requests for service. Note also that this file must be readable only by the ``fax'' user; i.e. it should have mode 600 and be owned by ``fax''. Each newline-terminated entry is a set of colon (:) separated fields, all but the first of which are optional. Trailing null fields and their separators may be omitted. The most general form is: client:uid:passwd:adminwd client is a regular expression to be matched against a string ``user@host'' that is formed from the user string passed to hfaxd with the USER command and the official host name or the DARPA Internet address, specified in ``dot notation''. If client does not contain an ``@'' then, for backwards compatibility, it is treated as a host for which any user may have access; i.e. it is automatically converted to the regular expression ``^.*@client$''. Comments are introduced with the ``#'' character and extend to the end of the line. Any whitespace immediately preceding a comment is also ignored. If client has a leading ``!'', then it is interpreted as a class of hosts and users to which access is to be disallowed. That is, if the pattern matches the client information, then access is denied. Note that regular expressions are not anchored. That is, a regular expression may match a substring of the ``user@host'' string. Thus `pb@.*.cl.cam.ac.uk' matches `cpb@mc.cl.cam.ac.uk.esd.sgi.com'. Use ``^'' to match the start of the string and ``$'' to match the end. Fields following client are optional and specify the following: uid The numerical user ID to assign to clients that use the entry for access. hfaxd uses the uid to control access to server resources such as jobs and documents (the value is used to set the group ID of files created by a client). Multiple clients/users may share the same uid or unique IDs may be created for each client. User IDs may be any number in the range [0..60002] with 60002 used, by convention, for entries that do not have a uid specified. passwd The encrypted password. If this field is empty (null) then no password will be demanded when a client logs in; i.e. the USER command does not need to be followed by a PASS command. adminwd The encrypted password for this user to gain administrative privileges. If this field is empty (null) then the user is not per- mitted to have administrative privileges. EXAMPLE
The following is a sample hosts.hfaxd file. Note that the first entry that matches is taken, so more-specific entries should be placed first. ^pb@[^.]*.cl.cam.ac.uk$:::hFy8zXq2KaG8s # pb on a machine directly in cl.cam.ac.uk can # administer if an admin pw is given 127.0.0.1 # anyone on local host uses the default uid ^sam@flake.*sgi.com$ # Sam on his work machine ^sam@oxford.*Berkeley.*# Sam on any machine starting oxford and containing # Berkeley, e.g. sam@oxfordberkeley.cl.cam.ac.uk ^.*@.*..esd. # anyone in an esd domain !^tom@ # Tom Davis is denied access .*.sgi.com$ # but anyone else at sgi is ok SEE ALSO
sendfax(1), hfaxd(8), hylafax-server(5) January 18, 1996 HOSTS.HFAXD(5)