Re: [hylafax-users] Problem with TIFF attachment

["Anthony Engelbrecht" <anthonye@attunetech.com>]

Great suggestion about using logger, I must admit I dod not even think of
this one.

So you do not even have a etc/FaxDispatch?

Anthony

-----Original Message-----
From: Adam Smith [mailto:adam.smith@sageautomation.com]
Sent: 31 January 2003 04:24 AM
To: Anthony Engelbrecht
Cc: hylafax-users@hylafax.org
Subject: Re: [hylafax-users] Problem with TIFF attachment


By Anthony Engelbrecht, on Fri, Jan 31, 2003 at 04:04:40AM +0200:
> Via etc/FaxDispatch
> ----------------
> FILETYPE=tif;
> SENDTO=FaxMaster;
> MIMENCODE=bin/uuencode_it;
> ----------------

Mine is identical except for the MIMENCODE part.

If the default delivery type is tif, why have you changed to uuencode?

> Then I have bin/uuencode_it
> ----------------
> #!/bin/sh
> uuencode -m $1 $1 | grep -E -v "^begin|^====$" 2>/dev/null
> ----------------

If this is the correct way, I have not done it the correct way, but what I
have done worked for me.

Sometimes I've found the 'logger' utility is very helpful in shell scripts.
place a line under your uuencode command that reads:

logger uuencode just ran:
logger uuencode -m $1 $1 | grep -E -v "^begin|^====$" 2>/dev/null

That will log the command to syslog and the variables will be output there
aswell.  Then just have a look at /var/log/messages and make sure the
command line is not missing any variables.

Adam


____________________ HylaFAX(tm) Users Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
 On UNIX: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*