Hi,
I was wondering whether its possible to allow everybody with an address
like me@mycompany.com to create tickets, and reject everyone else.
(rather than give everyone the create ticket permission)
Thanks,
Tom
Hi,
I was wondering whether its possible to allow everybody with an address
like me@mycompany.com to create tickets, and reject everyone else.
(rather than give everyone the create ticket permission)
Thanks,
Tom
Hi Tom,
I don’t think RT lets you do permissions that way. The way I handle a
similar situation is I use the OnCreate scrip to check the address (in the
Prep Action code) and then delete the ticket
(“$self->TicketObj->SetStatus(‘deleted’);”) and return 0 if it’s not an
allowed address.
Regards,
Gene
At 12:45 PM 12/4/2007, Tom H wrote:
Hi,
I was wondering whether its possible to allow everybody with an address
like me@mycompany.com to create tickets, and reject everyone else.
(rather than give everyone the create ticket permission)Thanks,
Tom
Gene LeDuc, GSEC
Security Analyst
San Diego State University
At Tuesday 12/4/2007 04:01 PM, Gene LeDuc wrote:
Hi Tom,
I don’t think RT lets you do permissions that way. The way I handle
a similar situation is I use the OnCreate scrip to check the address
(in the Prep Action code) and then delete the ticket
(“$self->TicketObj->SetStatus(‘deleted’);”) and return 0 if it’s not
an allowed address.Regards,
GeneAt 12:45 PM 12/4/2007, Tom H wrote:
Hi,
I was wondering whether its possible to allow everybody with an address
like me@mycompany.com to create tickets, and reject everyone else.
(rather than give everyone the create ticket permission)Thanks,
Tom
Another way would be to create a custom email filter (goes into
lib/RT/Interface/Email/Filter). This is more complicated that a
scrip, but it has the advantage that no tickets will be created for
the unwanted messages.
Or you could do similar filtering outside of RT, I suppose.
Steve
It may be worth doing it in the mail system before the ticket is
logged to RT. Then you do not have a ticket you need to delete.
KenOn Tue, Dec 04, 2007 at 01:01:33PM -0800, Gene LeDuc wrote:
Hi Tom,
I don’t think RT lets you do permissions that way. The way I handle a
similar situation is I use the OnCreate scrip to check the address (in the
Prep Action code) and then delete the ticket
(“$self->TicketObj->SetStatus(‘deleted’);”) and return 0 if it’s not an
allowed address.Regards,
GeneAt 12:45 PM 12/4/2007, Tom H wrote:
Hi,
I was wondering whether its possible to allow everybody with an address
like me@mycompany.com to create tickets, and reject everyone else.
(rather than give everyone the create ticket permission)Thanks,
Tom
–
Gene LeDuc, GSEC
Security Analyst
San Diego State University
SAVE THOUSANDS OF DOLLARS ON RT SUPPORT:
If you sign up for a new RT support contract before December 31, we’ll take
up to 20 percent off the price. This sale won’t last long, so get in touch
today. Email us at sales@bestpractical.com or call us at +1 617 812
0745.Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.comDiscover RT’s hidden secrets with RT Essentials from O’Reilly Media. Buy a
copy at http://rtbook.bestpractical.com
Depending on how seriously you take that idea, I have a filter for the
Courier MTA that does exactly that:
http://phantom.dragonsdawn.net/~gordon/courier-pythonfilter/latest/filters/privateaddr.py
Kenneth Marshall wrote: