Re: [hylafax-users] tiff file not attached

[Razvan Cosma <razvan.cosma@xxxxxxxxxxxx>]

Apparently it wasn't a problem of mimencode, encoding type, libtiff or
configuration. I corrected the line with "base64", tried uuencode,
mimencode and bin/uuencode_it - nothing. Now I just installed hylafax
ver. 4.2.3 on the same machine and with the same config (overwriting
4.2.5), and the faxes are attached OK. Very weird.

Razvan Cosma wrote:
> After some further digging on the missing attachment, looks like the
> fault is in the line MIMENCODE='base64-encode'. I don't have such an
> executable in the system.
> If I comment this line or replace it with
> MIMENCODE='/usr/bin/mimencode', I receive an attached file which looks
> like this:
>
> Content-Type: image/tiff; name="fax000000110.tif"
> Content-Transfer-Encoding: 
> Content-Disposition: attachment; filename="fax000000110.tif"
> Content-Description: FAX document
>
> SUkqAK4rAAAAKJsVAGWzAqBsVgCUzQqAslkBUDYrAMogsA4CgAkB34iy1UQEVHZBngRnEmyP
> PiV4HXaFJBGsrpCClsDELQyznQXZFxUCTscAYELAN8aHgpEnhg99ZCCPHvKo3T1WgtcBUUbA
> etcetcetc
>
> Does this look like a valid encoded file? And - shouldn't there be something specified in the 
> Content-Transfer-Encoding: line?
>
> Cheers,
> R
>
>
>
>
>
>
>   

____________________ 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@xxxxxxxxxxx < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*