[hylafax-users] Notify attachments missing in Hylafax+ 5.1.4

["Marcello Golfieri" <golfieri@xxxxxxxxx>]

Hi folks,

I have some troubles with fax attachments when getting notifications.  Problem is that you get the email subject and body right, you can even see the attachment avalaible.  But once you click on it for saving or viewing, you get (on a Tomcat  installation, but doesnt' matter):

type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

java.io.IOException
: Unknown encoding: 
	javax.mail.internet.MimePartDataSource.getInputStream(MimePartDataSource.java:106)
	javax.activation.DataHandler.getInputStream(DataHandler.java:237)
	javax.mail.internet.MimeBodyPart.getInputStream
(MimeBodyPart.java:554)
	com.zimbra.cs.service.formatter.NativeFormatter.sendbackOriginalDoc(NativeFormatter.java:173)
	com.zimbra.cs.service.formatter.NativeFormatter.handleMessagePart(NativeFormatter.java:145)

	com.zimbra.cs.service.formatter.NativeFormatter.handleMessage(NativeFormatter.java:110)
	com.zimbra.cs.service.formatter.NativeFormatter.formatCallback(NativeFormatter.java:86)
	com.zimbra.cs.service.formatter.Formatter$FormatOperation.callback
(Formatter.java:246)
	com.zimbra.cs.operation.Operation.schedule(Operation.java:190)
	com.zimbra.cs.service.formatter.Formatter.format(Formatter.java:87)
	com.zimbra.cs.service.UserServlet.doAuthGet(UserServlet.java
:368)
	com.zimbra.cs.service.UserServlet.doGet(UserServlet.java:271)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
	com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:162)
	javax.servlet.http.HttpServlet.service
(HttpServlet.java:802)

note The full stack trace of the root cause is available in the Apache Tomcat/5.5.15 logs.

In fact when you check the original source of the mail message: 


Received: from blackbox.mydomain.it (localhost.localdomain [127.0.0.1])
	by blackbox.mydomain.it
 (Postfix) with ESMTP id C713F3B07ED
	for <admin@xxxxxxxxxxxxxxxxxxxx>; Mon, 21 May 2007 10:53:55 +0200 (CEST)
Received: (from uucp@localhost)
	by 
blackbox.mydomain.it (8.13.1/8.13.1/Submit) id l4L8rt6O004743;
	Mon, 21 May 2007 10:53:55 +0200
Date: Mon, 21 May 2007 10:53:55 +0200
From: fax@xxxxxxxxxxxxxxxxxxxx
Message-Id: <200705210853.l4L8rt6O004743@xxxxxxxxxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart4500"
Content-Transfer-Encoding: 7bit
To: admin@xxxxxxxxxxxxxxxxxxxx
Subject: fax 19 per 495 completato

This is a multi-part message in MIME format.

--NextPart4500
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Il fax per 495 è stato completato con successo.

            Destinatario: 495
                Mittente: admin
                  E-mail: admin@xxxxxxxxxxxxxxxxxxxx
                  Pagine: 1
               Ricevente: +39532xxxxxx
                 Qualità: Normale
        Larghezza pagina: 209 (mm)
          Altezza pagina: 296 (mm)
Velocità di trasmissione: 14400 bit/s
            Formato dati: 2-D MMR
      Dispositivo remoto: Brother MFC-3100C/MFC-8600
                   Modem: ttyIAX0
              Inviato da: 
localhost.localdomain
                   JobID: 19
                 GroupID: 19
                  CommID: c000000019

Il tempo di elaborazione è stato 0:56.

    ---- Documenti accodati per l\'invio ----

I seguenti documenti erano stati accodati per l'invio e sono
disponibili sul server per essere riutilizzati finché non saranno automaticamente
eliminati quando questo lavoro sarà rimosso. I documenti possono anche essere manualmente
eliminati con il comando faxrm; consultare faxrm(1) per maggiori informazioni.

Nome file            Dimensione Tipo
docq/doc20.ps            3762 PostScript

--NextPart4500
Content-Type: image/tiff; name="
495-1.tif"
Content-Description: FAX document
Content-Transfer-Encoding: 
Content-Disposition: attachment; filename="495-1.tif"


--NextPart4500--

You can see the problem:    Content-Transfer-Encoding: is not set, and the attachment itself is missing.  note that whatever kind of RETURNFILETYPE you request in FaxNotify, you always  get the same  error message and mail source.

Any idea?

Thanks in advance!

-- 
Marcello Golfieri