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):||18 March 2015|
|PDF File Size:||14.72 Mb|
|ePub File Size:||11.64 Mb|
|Price:||Free* [*Free Regsitration Required]|
HylaFAX The world’s most advanced open source fax server. So I’m not sending directly using sendfax. Or if it’s a binary, its config file. It has “always”, notifyy, and “when delivered”.
I’m looking more along the lines of “Final status”. I want to know if it failed completely.
Re: [hylafax-users] notify
However, I do not want to know that it requed it 8 times. This is really a convience to our users. We don’t want to spam their inboxes when the fax is undeliverable.
However, we still want them to know when it’s been successful. We only one them to get one possible email for each fax. Whether it failed or worked. Admittedly, WHFC is a notidy client.
notify(8) — hylafax-server — Debian testing — Debian Manpages
However, winprint hylafax is much simplier. We can show them how to use winprint hylafax in about 10 seconds. WHFC can be accidently exited too notufy. Also, it gives them too many options.
Some users get scared when faced with too much. The only possible options to the user are the fax number and return email and to save that fax number in the address book. If it’s too difficult, we found that they’ll get up and hylafwx the paper fax.
We’ll probably use WHFC once people get addicted to faxing from their desk. For now, I think winprint hylafax is the best fit.
Project hosted by iFAX Solutions.