|
At 03:58 05/22/2000 , John Earl wrote: >A user needs *opr and *add to place messages on the queue, and *opr, *read & >*add (rather than *upd) to answer messages. It turns out that when you >answer a >message you are actually adding a new message to the queue that answers >the old >message (that's why we see inquiry messages show up twice in the >queue). You're >not actually (or directly?) changing the old message. Weird, but that is >the way >it is. Ok. What's the magic combo then, that will allow *public to put messages on the queue, but not allow *public to answer them? I know I got this to work once. I'm just not sure exactly what the solution was. Granted you need add data authority to add a reply message, but don't you also need update? Replying does modify the original message status, does it not? I'm really not sure. I wish I could test it, but alas, I don't have the authority... Pete Hall pbhall@execpc.com http://www.execpc.com/~pbhall +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.