|
Thanks for the reply, Sean. Comments inline... > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx / Sean Porterfield > Sent: Monday, August 09, 2004 7:41 PM > > Dan Bale wrote: > > > We're using MAIL MANager (Rel 2.50) and are having a problem > > when new users are added to the system. User message queues > > are created with a default *PUBLIC authority of *USE. > > Our new users have *PUBLIC *CHANGE by default. I wonder if you've > changed a parameter somewhere? Or a security setting perhaps? Is there something that would change how the system creates the authority on the user msgq when the user profile is created? Although, I have to wonder. If users' message queues are set to *PUBLIC:*CHANGE, doesn't that mean that anyone can delete messages from someone else's message queue? That could not be a good thing. > > MailMan chokes on this with CPF2408 / CPF2469 (Not > > authorized to message queue USERNAME). > > See help on SNDMSG: > > 1. The user must have object operational and add authorities to > the message queue. > > *USE does not provide add authority. MAIL_MANN sends a message to the > recipient which requires that authority just as any user using the > SNDMSG command (or SysRq 5). Actually, after I posted to the list yesterday, I finally received a call back from support on this problem. According to support, MAIL_MANN uses SNDPGMMSG, and the help on SNDPGMMSG does not show any of the authority requirements as SNDMSG. I created two new *USER test profiles, TEST1 & TEST2, with no special authorities; user *MSGQ set to *PUBLIC:*USE. I signed on as TEST1, and ran this program: Pgm SNDPGMMSG MSG('this is just a test') + TOMSGQ(QUSRSYS/TEST2) Endpgm It ran fine, and sent the message to TEST2. db
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.