faxspool and fax-id

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

Paul Sand wrote:
> It appears that faxspool ignores the port specific fax-id settings
> in sendfax.config.  I have found that faxspool uses the default
> FAX_STATION_ID="49 89 xxxxxxxx" if there is not a global fax-id
> specified in sendfax.config.  All other aspects of mgetty+sendfax
> seem to honor the port specific fax-id.  

Faxspool has no idea what serial port "faxrunq / sendfax" will use later
on, so it *must not* honour the port specific settings.

> The symptom is, the faxheader ends up with "49 89 xxxxxxxx" if there is
> not a global fax-id.  The sendfax.log shows that the port specific
> fax-id was put into the modem.  The problem seems only to be with
> faxspool and the faxheader.

It's not really a "bug", but more a misconception of the way it works
together... actually, I took quite some effort to make sure faxspool does
*not* read the port-specific stuff.

> I realize the manuals at 
> http://www.leo.org/~doering/mgetty/mgetty_25.html#SEC25 state the
> following, but faxspool does read sendfax.config.
> 
> fax-id [-I] your fax phone 
>      Watch out: the faxspool program does not read sendfax' 
>      config file, so the fax id it puts on the header
>      might not be the same as the one transmitted by sendfax, 
>      if you change it only in one place. 

Bug in the docs. Will be fixed.

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-3545980                         gert.doering@physik.tu-muenchen.de