Re: [hylafax-users] receipt as pdf gets only empty file

[Josef Ender <dsniff@xxxxxxx>]

Hello Martin

Many thanks for your help!

> First of all, you made the pdf/pfd typo two out of three times in this
> e-mail.  Are you sure you didn't make the same mistake in your

Yup, sorry mistyped....

> Second, as recommended when you joined the list
> (http://www.hylafax.org/mailing-lists.html) you should give your

Uuuuh, again sorry for that. Here is my data:
HylaFAX Version 4.2.0
OS Linux Debian Sarge Kernel 2.4.27
Modem: Zyxel U1496E/V 6.21 M


You are cool! exactly the base64 was missing in my email..... but
I applied your suggestion. Now I get Content-Transfer-Encoding: base64 
but still no file data. Here is an example:

---snip---
This is a multi-part message in MIME format.

--NextPart14688
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Your facsimile job to 00498121900002255 was completed successfully.

         Pages: 2
       Quality: Normal
    Page Width: 209 (mm)
   Page Length: 296 (mm)
   Signal Rate: 14400 bit/s
   Data Format: 2-D MR
         Calls: 4 (total phone calls placed)
Submitted From: localhost.localdomain
         JobID: 58
       GroupID: 58
        CommID: c000000090

Processing time was 0:50.

--NextPart14688
Content-Type: application/pdf; name="00498121900002255-2.pdf"
Content-Description: FAX document
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="00498121900002255-2.pdf"


--NextPart14688--

--------------040406080803020503030607--

---snip---

> Apparently /var/spool/hylafax/etc/notify has the following lines:

do you mean: /var/spool/hylafax/etc/FaxNotify? or is it the same?

> The cause of this, I believe, is doing an upgrade but failing to run
> faxsetup again after the upgrade.  Is this what you did?

This is a newly installed system. AFAIR there was no upgrade.

I rerun faxsetup and added some lines to FaxNotify. My complete 
FaxNotify is now:
RETURNFILETYPE=pdf;
ENCODING=base64
. etc/setup.cache
ENCODING=base64

But still the same:
No Attachment data: like in the example above.

any more ideas?

many thanks!

Josi

--
Josef Ender, Bitspot AG
http://www.bitspot.com

marthter wrote:
> Josef Ender wrote  on 14/12/04 04:55 AM:
>
> > Hello
> >
> > I'm sending Faxes with sendfax over hylafax and get receipts by email 
> > (-R).
> >
> > According to the documentation you should get the fax attached as PDF 
> > if you add the line "RETURNFILETYPE=pfd;" in 
> > /var/spool/hylafax/FaxNotify.
> > But I get only an empty pfd file attached.
> >
> > Any help would be greatly appreciated.
> >
> > Josi
>
>
> First of all, you made the pdf/pfd typo two out of three times in this
> e-mail.  Are you sure you didn't make the same mistake in your FaxNotify?
>
> Second, as recommended when you joined the list
> (http://www.hylafax.org/mailing-lists.html) you should give your
> Hylafax version, OS/distribution, and (if it seems remotely modem
> related) your modem model and firmware.
>
> So, making some guesses, if you upgraded from an earlier version to
> 4.2.0, it sounds like the "base64 issue". To check if this is the case,
> do view-source on the e-mail in your e-mail client program. Just before
> the big block of letters and numbers (your encoded document), you should
> see:
>
> Content-Type: application/pdf; name="fax000000863.pdf"
> Content-Description: FAX document
> Content-Transfer-Encoding: base64
> Content-Disposition: attachment; filename="fax000000863.pdf"
>
>
> If you are missing the "base64" there, then this is probably your problem.
>
> Apparently /var/spool/hylafax/etc/notify has the following lines:
>
> ENCODING=base64
> . etc/setup.cache
>
>
> But if you check inside your setup.cache, it probably has ENCODING=""
> setting back it to the empty string, which is in effect when the e-mail
> is generated.
>
> The cause of this, I believe, is doing an upgrade but failing to run
> faxsetup again after the upgrade.  Is this what you did?
>
> Either run faxsetup, or add another ENCODING=base64 line in etc/notify,
> below the setup.cache line and it should work fine after that.
>
> Hope that helps.
>
> Martin
>
> P.S. To someone at hylafax.org with website access:  Can we add this to
> the FAQ?
>
>
> ____________________ 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*


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