![]() |
Thanks for the response. Unfortunately, the thing is that I don't really have the time to do the implementation. I have about a million ways to improve the functionality/reliablility of the software I wrote for fax management, just don't have the time to do them. I was thinking of writing my own Hylafax client in Python using Tk for the gui, but again, I just don't have the time necessary to do it. Guess I'll continue to work with my mgetty+sendfax/php solution. Thanks again. Rich Lee Howard wrote: > >I've looked through the docs and it sppears that it is possible to > >archive outgoing faxes, but I don't see any mention of archiving > >incoming faxes. > > By default, archiving is not done in either case, but simple modifications > to faxrcvd (for received faxes) and notify.awk (for sent faxes) or > faxqclean could do it for you. And usually this type of customization is > expected in any implementation. > > >Also, one of the things that my clients want is the ability to know if a > >fax has been viewed and/or printed, but I haven't really seen any > >mention of hylafax flagging when and who did these things. > > This is a logging feature that you'd need to build into the > viewing/printing client. HylaFAX doesn't come with a fax viewer. You > could create a script that invokes Ghostview (or whatever it's called) and > logs the actions somewhere specific, but chances are good that your clients > aren't *NIX. > > >Yet another feature they really like, and I agree is convenient, is to > >be able to comment on faxes and have the comments displayed with the > >rest of the fax info. That way they know what it is and who it's from > >without having to do any extra work. > > Again, I think this is a viewing/printing/editing client's job. > > >Let me know if Hylafax supports these things of if it will anytime > >soon. I appreciate any help. Thanks > > Most of this seems like customization features rather than standardization. > Those who are like me *don't* want faxes archived because of the bulk I > receive (lotsa spammers). I receive them delivered by e-mail, and I stash > them away if I think I'll need it later. > > As for the logging, and such, I'm not really the one to say, but it appears > that HylaFAX has kept itself free from incorporating a > viewing/printing/editing/logging client intentionally. Given the number of > platforms and OSes that it would have to support, I think that this is > good... not to mention the work that needs to be done on the existing code > without entangling yet another element. Anyway, my point is that I don't > think that your wishes will become part of HylaFAX on their own any time soon. > > This is open-source software, though. Feel free to do your part... ;-) > > Lee. ____________________ HylaFAX(tm) Users Mailing List _______________________ To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null