![]() |
There would be a trust and authentication problem. I've been thinking about this for a while. Basically, if we have servers forwarding fax jobs around you get something like the email model. We all know how broken that is. In a closed, single admin group it could work. Otherwise you're trusting the admin of the forwarding server to have properly configured (secured) his machine or the whole network suffers. You'd definitely want this stuff disabled in the default install. -joe On Thu, Mar 21, 2002 at 12:43:37PM +0200, Sedat Yilmazer wrote: > > Good point. That also brings up the question of faxmaster. In hylafax > there is no such acount that can kill/alter other jobs. I think there is > such a need ( I mean an account to control other jobs) > > So after some looking around I thing the way is to submit a new job at > the dest. Host ( via a sendfax ....-f my_local_user -h ttyS1@remotehost > ....) and remove the queue file from sendq. Maybe alitle bit dirty but > may work) > We can get the my_local_user, number to dial ...etc from the queue > file. Dest host should accept all job submitions from myhost (so that we > do not need password). > > There is still the question of how the user will see/remove/control his > job after it is transfered to the remote host. > > > Sedat YILMAZER -- Innovation Software Group, LLC - http://www.innovationsw.com Custom Internet and Computer Solutions Linux, UNIX, Java Training ____________________ HylaFAX(tm) Users Mailing List _______________________ To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null