HylaFAX Software. Contribute to ifax/HylaFAX development by creating an account on GitHub. NOTIFY. Section: Misc. Reference Manual Pages (1m) Updated: May 8, Index Return to Main Contents. Chris Baechle wrote: > Thanks for the prompt response! I guess I’m a little unfarmiliar with > the arch of hylafax. I’m sending from a windows box.
|Published (Last):||4 October 2010|
|PDF File Size:||7.70 Mb|
|ePub File Size:||3.59 Mb|
|Price:||Free* [*Free Regsitration Required]|
However, I do not want to know that it requed it 8 times.
Re: [hylafax-users] notify
It has “always”, “never”, and “when delivered”. WHY is identical to why mentioned above and can be useful in determining under what conditions various settings should take effect. However, winprint hylafax is much simplier. LANG controls the localization of the text of the job notification messages. The default notification script sends the user electronic mail describing the event or action. We’ll probably use WHFC once people get addicted to faxing from their desk. I’m looking more along the lines of “Final status”.
We can show them how notiify use winprint hylafax in notfiy 10 seconds.
Some users get scared when faced with too much. HylaFAX The world’s most advanced open source fax server.
Re: [hylafax-users] notify
Or if it’s a binary, its config file. This is useful in allowing the administrator to be aware of any problems before those problems are reported by the users. Whether it failed or worked. FaxNotify is sourced after notiry q-file is parsed and all default values are preset.
Project hosted by iFAX Solutions. For now, I think winprint hylafax is the best fit. If set, this causes notify to return a copy of the submitted documents to the SENDER address along with the notification message. Useful settings for FaxNotify are: It is designed to be customizable by the administrator.
However, we still want them to know when it’s been successful. We only one them to get one possible email for each fax. Multiple values may be specified by separating them with whitespace. Admittedly, WHFC is a superior client.
If it’s too difficult, we found that they’ll get up and use the paper fax. WHFC can be accidently exited too easy. The only possible options to the user are the fax number and return email and to save that fax number in the address book. I want to know if it failed completely. In that case a separate attachment is created for each filetype.
notify(8) — hylafax-server — Debian testing — Debian Manpages
This is really a convience to our users. So I’m not sending directly using sendfax.
Also, it gives them too many options. We don’t want to spam their inboxes when the fax is undeliverable. Ideally this is done by creating a customized notify script in a different filename or by copying the default script to a different notifj, customizing that new file, and then using NotifyCmd in the scheduler config file to point faxq 8C at the customized script.