Re: [hylafax-users] Email to Fax Gateway on Etch problem

[Mirko Grava <mg@xxxxxxx>]

Riccardo Magliocchetti ha scritto:
> Mirko Grava ha scritto:
>> I have some problem on this subject.
>> Ihave read all this thread
>> http://www.hylafax.org/archive/2008-01/threads.php#00286
>>
>> but I need some help.
>>
>> I use etch (oldstable now) with hylafax from etch-backports.
>>
>> I want use a Brother MFC 8860DN to send mail with PDF or TIFF attachment
>> and after this send a fax in conjunction with postfix.
>>
>> This is the row in the master.cf that works well
>>
>> # Per hylafax Mirko 20090218
>> fax       unix  -       n       n       -       1       pipe
>>   flags= user=uucp argv=/usr/bin/faxmail -N -T -n ${user}
>>
>> My problem is that from this MFP i receive this header:
>>
>> for PDF
>> -----------------------------------------------
>> Subject: Invio Scansione
>> Date: Fri, 13 Feb 2009 11:07:06 +0100
>> Message-Id: <00000029.36c6ae5a.1.00@BRN_941130>
>> Mime-Version: 1.0
>> Content-Type: multipart/mixed; boundary="RS1tYWlsIENsaWVudA=="
>> X-Mailer: E-mail Client
>>
>> This is multipart message.
>>
>> --RS1tYWlsIENsaWVudA==
>> Content-Type: text/plain; charset=iso-8859-1
>> Content-Transfer-Encoding: quoted-printable
>>
>> Il file immagine in formato PDF =E8 stato allegato.
>> --RS1tYWlsIENsaWVudA==
>> Content-Type: image/pdf; name="image.pdf"
>> Content-Transfer-Encoding: base64
>> -----------------------------------------------
>>
>> for TIFF
>> -----------------------------------------------
>> Subject: Invio Scansione
>> Date: Thu, 19 Feb 2009 11:04:05 +0100
>> Message-Id: <00000007.36ce96a5.1.00@BRN_941130>
>> Mime-Version: 1.0
>> Content-Type: multipart/mixed; boundary="RS1tYWlsIENsaWVudA=="
>> X-Mailer: E-mail Client
>>
>> This is multipart message.
>>
>> --RS1tYWlsIENsaWVudA==
>> Content-Type: text/plain; charset=iso-8859-1
>> Content-Transfer-Encoding: quoted-printable
>>
>> Il file immagine in formato TIFF-F =E8 stato allegato.
>> --RS1tYWlsIENsaWVudA==
>> Content-Type: image/tiff; name="image.tif"
>> Content-Transfer-Encoding: base64
>> -----------------------------------------------
>>
>> In both case all we send is the attach in base64 like a text-file.
>>
>> Is it possible that faxmail need Content-Disposition in header field?
>> But Content-Disposition (RFC2183) is a MAY attribute.
>>
>> Am I wrong?
>> Thanks for any help
> 
> If you add -v to faxmail what does it say? if you are not already doing
> that i suggest you to just dump the email from postfix and cat it to
> faxmail from the hylafax machine.
Right this is a good idea.
I'll try and post the output.
Thanks


____________________ 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*