MAN page from Old RedHat 5.X mgetty-sendfax-1.1.14-5.i386.rpm

faxqueue

Section: mgetty+sendfax manual (5)
Updated: 18 Oct 94
Index

NAME

faxqueue - sendfax fax spool queue control files

SYNOPSIS

/var/spool/fax/outgoing/F*/JOB

DESCRIPTION

TheJOBfiles in the subdirectories of the outgoing fax spool directory, /var/spool/fax/outgoingbuild up a queue of faxes to be sent by faxrunq(1). They are created byfaxspool(1), can be viewed with faxq(1), and be deleted by faxrm(1).

FORMAT

The format of the JOB file is as follows:

Each line consists of a leading keyword and associated data (rest of theline). Some are required, some others are optional. The currentlyimplemented keywords are:

phone <number>

The telephone number to send the fax to. Required.

user <user>

The originating user name (on the local machine). If no "mail" field ispresent, this user will get the status mail about the fax. Required.

mail <email>

If this field is present, faxrunq(1) will send its status mail to theaddress given here. If not, faxrunq(1) will use the "user" field.Optional.

input <file(s)>

The file names passed to faxspool(1). Optional, used only by faxq(1).

pages <file(s)>

The file names, relative to the directory where the JOB file is found,that are to be sent with sendfax(8). The files have to exist, and bereadable by the user that runs faxrunq(1). Required, except if "poll" isused, then it's optional.

priority <0-9>

This can be used to set the priority for this job in the fax queue (higherpriority jobs get sent before all lower-pri jobs). So far, onlyfaxrunqduses this field, faxrunqdoes NOT. 9 is the highest, 0 the lowest priority. 5 is the default.

Status <message>

Automatically appended by faxrunq(1) after each run, tells the readerabout successful and unsuccessful tries to send this job. If more thanfive "FATAL" errors are listed, the fax job is removed from the queue.

verbose_to <blurb>

A plain-text description of the receiver of the fax. Is returned, ifpresent, in the mail messages "your fax to <blurb>". Optional.

time <hhmm>

If present, faxrunqwon't send this job before the given time. The format must be exactly"hhmm", in 24-hr-format, otherwise faxrunq won't understand it. Optional.

poll

Flag token. If present, faxrunq will try to poll the given phonenumber for documents (see "sendfax -p").

normal_res

Flag token. If present, faxrunq will transmit all pages using normalresolution (see "sendfax -n").

acct_handle <arbitrary string>

This is a pure comment field, but sendfax(8) will log it intoits transaction log file. So this can be used as a customer handle,a job number, whatever you need to get the phone bills charged to thecustomer (the programs won't look at it, just pass it through). Optional.

subject <arbitrary string>

This is also a pure comment field, used only for informational purposes.faxrunqwill return it in the sucess/failure mail. If you use faxspool -s <subj>,it will put this string on the cover page and in the JOB file.

PROCESSING

While a given JOB file is processed by faxrunq(1), it's locked againstsending it multiple times by temporarily renaming it toJOB.locked,thus it may happen that a faxq(1) command doesn't show this job.

When a job is successfully sent, it's not deleted but the JOB file isrenamed toJOB.done.Because of this, you can still see old jobs with "faxq -o". You shouldregularly clean up the outgoing fax directory, removing old faxes. If youdon't want this behaviour, look into the faxrunq shell script, and removethe comment signs before the code to delete the job files.

When a job cannot be sent after several tries (excluding normaldifficulties like the called number being busy or the modem being inuse), the JOB file is renamed toJOB.suspended.To re-queue this job, rename the JOB file back and remove all the"Status" lines in it.

This document was created byman2html,using the manual pages.