HylaFAX The world's
most advanced open source fax server
|
|
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
[hylafax-users] questioning the sense of RETURNFILETYPE
Looking at the code again I have to question the whole process of
regenerating the files when the user requested them with the
notification.
Nobody wants to explicitly set RETURNFILETYPE to a specific file format.
My users just dont trust hylafax and want to see the data that was sent
to the recipient, which turns out to be a tif. From what I understand
the email2fax gateway already converts a file to tif before feeding it
to hylafax. THAT is the file the user wants to receive via email,
because he wants to know if the content was readable enough ...
regenerating the file kind of defeats the purpose of sending the file
back to the user.
opinions?
so long
Jörn
-
Jörn Friedrich Dreyer
Tel. +49 (0)561 - 574 32 77 - 41
Email dreyer@xxxxxxxxxxxxxxxxxxx
Yatta Solutions GmbH
Sitz der Gesellschaft: Kassel
Amtsgericht Kassel, HRB 14720
USt-IdNr DE263191529
Geschäftsführung:
Johannes Jacop,
Dr. Christian Schneider
Anschrift:
Ludwig-Erhard-Straße 12
34131 Kassel
Kontakt:
Tel. +49 (0)561 - 574 32 77 - 0
Fax +49 (0)3221 - 1321 - 586
Email info@xxxxxxxxxxxxxxxxxxx
Bankverbindung:
Kasseler Bank eG
BLZ: 520 900 00
Kto.-Nr.: 158 305
____________________ 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*