[Bug 345771] New: Discrepancy regarding file FaxDispatch in HylaFAX
https://bugzilla.novell.com/show_bug.cgi?id=345771 Summary: Discrepancy regarding file FaxDispatch in HylaFAX Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: SuSE Linux 10.0 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: robin.listas@telefonica.net QAContact: qa@suse.de Found By: --- (From a conversation we were having in the opensuse-es@opensuse.org mail list) The man page for hylafax "FAXRCVD(8C)" says: ] This script can route facsimile directly to the intended receipient. ] To do this create a shell script bin/FaxDispatch in the spooling area ] that sets SENDTO to the receiver's electronic mail address. For example, However, in http://www.hylafax.org/man/4.4.0/faxrcvd.1m.html it says: ] This script can route facsimile directly to the intended receipient. ] To do this create a shell script etc/FaxDispatch in the spooling area ] that sets SENDTO to the receiver’s electronic mail address. For example, Notice that the first one says "bin/FaxDispatch" and the second says "etc/FaxDispatch". Which one is correct? Investigating, I find that two scripts contains references to "FaxDispatch". One is "/var/spool/fax/bin/wedged", which imports "etc/FaxDispatch", and the other is ".../faxrcvd", which imports "bin/FaxDispatch". It may be that the man page is correct and the web page is not. Or it might be a confusion somewhere, because both "FaxDispatch" configuration files have similar purposes and the same name, which is quite confusing for the user. And for the user, having to edit a file in "bin/" which might be later overwritten by an upgrade, instead of doing so in "etc/" is also problematic and could be an usability issue. Which is why I classify this bugzilla as "other" initially, for you to decide ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=345771
Martin Mrazik
https://bugzilla.novell.com/show_bug.cgi?id=345771
User kkeil@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=345771#c1
Karsten Keil
https://bugzilla.novell.com/show_bug.cgi?id=345771
User noelamac@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=345771#c2
--- Comment #2 from Camaleon --
https://bugzilla.novell.com/show_bug.cgi?id=345771
User robin.listas@telefonica.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=345771#c3
--- Comment #3 from Carlos Robinson
As I ask the hylafax developers about some fixes in the http documentation, they claim, that it is outdated and should be removed, so man page is correct. In all SUSE versions we have a bin/FaxDispatch which dispatch faxes based on the called number. The admin has to edit etc/users to link numbers with mail addresses.
Does this mean that during an upgrade, the user modified file "/var/spool/fax/bin/FaxDispatch" will be not overwritten? It is a script, but it is also a user customizable configuration file, per the manual. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=345771
User kkeil@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=345771#c4
--- Comment #4 from Karsten Keil
https://bugzilla.novell.com/show_bug.cgi?id=345771
User robin.listas@telefonica.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=345771#c5
--- Comment #5 from Carlos Robinson
You only need to write your own /var/spool/fax/bin/FaxDispatch for special cases, and yes this file is currently not protected against updates, it maybe could get config status, but I do not see a real usecase where you need to modify it.
Well, the man page (FAXRCVD(8C) ) talks about creating/modifying it, and gives samples. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=345771
User robin.listas@telefonica.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=345771#c6
--- Comment #6 from Carlos Robinson
but I do not see a real usecase where you need to modify it.
I'll give you one: a user does not want to receive the attachment in the default .ps format, but in .tiff format. For this, the admin has to necessarily edit bin/FaxDispatch (or bin/faxrcvd) directly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=345771
User noelamac@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=345771#c7
--- Comment #7 from Camaleon --
You do not need that, it should work without modify anything. All you need is a mail alias FaxMaster, it get all incoming faxes.
Making an alias to achieve this is not mentioned anywhere in the docs :-(. Man page of "faxrcvd" just say about using SENDTO variable in order to get the fax delivered to users, not just FaxMaster.
Only if you have equipment which can handle multiple Faxnumbers, you need to edit /var/spool/fax/etc/users. You only need to write your own /var/spool/fax/bin/FaxDispatch for special cases, and yes this file is currently not protected against updates, it maybe could get config status, but I do not see a real usecase where you need to modify it.
Well, I can see some scenarios where editing FaxDispatch is a "must". For example, if the e-mail has to be sent to several recipients with different formats based on users preferences (one likes pdf and others prefer tif). Another case for editing this file could be the use of html templates (a new feature of this HylaFAX release)... and there are many cases where this option is needed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com