I did not see the easy way through this maze, because I forgot that a default Linux setup root protects a lot of services. Since by default mgetty runs as root, what I had to do was type [alt]+[F2] and then type:
In gwenview, I just opened my .tiff file (which had owner deekbeek, group user permissions; not root permissions). I printed it with the to fax option. I accepted the dialog box option to shrink it to fit the page, and KdeprintFax automatically popped open with the correctly formatted .tif fax already listed in the upper files scroller; ready to take the fax number. I could then go to /var/spool/fax/outgoing/F000008 and view the ready-to-send .tif fax with KFax (an mgetty header line gets pwanged right in, which I still have to configure).
I have the good fortune of having a Windows XP home system, on a different phone number, upstairs in the house. The fax sent, and both my Linux system and the other Windows XP system logged errors (the Windows system error dialog claimed not all pages were sent). This was strange because the sent fax LOOKED PERFECT. My linux system logged this in faxrunq (with phone and username disguises applied):
Code:
deekbeek@linux-aaga:~> su root
Password:
linux-aaga:/home/deekbeek # faxrunq
processing F000008/JOB...
/usr/sbin/sendfax -v 9999999 f1.g3
Trying fax device '/dev/ttyS1'... OK.
Dialing 9999999... OK.
sending 'f1.g3'...
/usr/sbin/sendfax: FAILED to transmit 'f1.g3'.
Transmission error: +FHNG:-5 (Unexpected hangup / read() error / write() error (int.))
command exited with status 12
linux-aaga:/home/deekbeek #
Since the received fax looked perfect, I am puzzled by the errors. If I hadn't been able to see the received fax (which is the norm), I would have to consider it failed.
Incidentally, don't ever think that those RCA wireless modem jacks will work; the Windows XP fax receiving machine was on those. I had to replace them with a straight-through phone cord for faxing to work. I am using U.S. Robotics Performance Pro 56k modems.