Package: hylafax-server
Version: 1:4.2.1-1
Severity: normal
I received the attached email delivery failure notice after sending a
fax (successfully, I think). It was reported to me in my postmaster
capacity for undelivered mail. Notice that the To: field is blank.
There is also little information about the job itself. I don't know
if that's an additional problem, or a result of the first.
This is my first fax since upgrading from 1:4.2.0-16, I see no sign
I've changed my config files.
Perhaps this is triggered by the unusual sendfax line, which is
executed on one account but pretends to be from another. It is that
other account that should receive the notification. The command line
executed on account boylan was
sendfax -f "Ross Boylan <[EMAIL PROTECTED]>" -m -R -n -d "..." ....
That command, which is in a shell script, used to work fine.
ross is my regular account.
Another peculiarity of my system is that it is known by a number of
names that don't have any real existence on the internet. I've told
the mail program to use one of those names.
The notification appears to be the responsibility of
/var/spool/hylafax/bin/notify, and that script seems to have changed
very recently. I suspect there may be a problem there, probably
upstream. I haven't traced through it, partly because I don't know
exactly how, and with what arguments, it is called.
Previous hylafax notifications did involve MIME; probably the MIME is
from the mail system (exim3) while delivering the failure notice.
(That is, the notice of failed delivery. The message to be delivered
appears to report success on the fax).
In the short run, is there a way I kind determine for sure if the fax
went out?
While reading the docs for hylafax-server I noticed repeated
references to the faxq configuration file. I see no such file.
Possibilities:
1) It's missing, and is causing the above problem (I'd be surprised);
2) Configuration files for hylafax have changed since the man page was
written;
3) "faxq configuration file" is a generic reference to a file whose
name I should know. I don't!
In case 2 or 3, some update of the man page would be a good thing.
Thanks.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.27advncdfs
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages hylafax-server depends on:
ii debconf 1.4.30.11 Debian configuration management sy
ii gs 8.01-5 Transitional package
ii gs-esp [gs] 7.07.1-9 The Ghostscript PostScript interpr
ii gs-gpl [gs] 8.01-5 The GPL Ghostscript PostScript int
ii hylafax-client 1:4.2.1-1 Flexible client/server fax softwar
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii libgcc1 1:3.4.3-6 GCC support library
ii libpam0g 0.76-22 Pluggable Authentication Modules l
ii libstdc++5 1:3.3.5-5 The GNU Standard C++ Library v3
ii libtiff-tools 3.7.1-2 TIFF manipulation and conversion t
ii libtiff4 3.7.1-2 Tag Image File Format (TIFF) libra
ii mailx 1:8.1.2-0.20040524cvs-4 A simple mail user agent
ii mime-codecs 7.19-2 Fast Quoted-Printable and BASE64 M
ii psmisc 21.5-1 Utilities that use the proc filesy
ii sed 4.1.2-8 The GNU sed stream editor
ii zlib1g 1:1.2.2-3 compression library - runtime
-- debconf information:
* hylafax-server/configure_note:
hylafax-server/start_now: true
>From MAILER-DAEMON Mon Feb 07 14:30:25 2005
Received: from mail by wheat.dslnorthwest.net with local (Exim 3.36 #1 (Debian))
id 1CyHOj-0006wz-00
for <[EMAIL PROTECTED]>; Mon, 07 Feb 2005 14:30:25 -0800
From: Mail Delivery System <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Mail failure - no recipient addresses
Message-Id: <[EMAIL PROTECTED]>
Date: Mon, 07 Feb 2005 14:30:25 -0800
Status: RO
Content-Length: 994
Lines: 35
A message that you sent contained no recipient addresses, and therefore no
delivery could be attempted.
------ This is a copy of your message, including all the headers. ------
Received: from uucp by wheat.dslnorthwest.net with local (Exim 3.36 #1 (Debian))
id 1CyHOj-0006wx-00; Mon, 07 Feb 2005 14:30:25 -0800
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart26714"
Content-Transfer-Encoding: 7bit
To:
Subject: job to completed
Message-Id: <[EMAIL PROTECTED]>
From: uucp <[EMAIL PROTECTED]>
Date: Mon, 07 Feb 2005 14:30:25 -0800
This is a multi-part message in MIME format.
--NextPart26714
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Your job to was completed successfully.
Dialogs: (exchanges with remote device)
Calls: (total phone calls placed)
Modem:
Submitted From:
JobID:
GroupID:
CommID: c
Processing time was 1:06.
--NextPart26714--
