Disable user creation

Hello, I was wondering if anyone has been able to find a way to disable
the creation of a user when they submit a ticket or just in general. We
recieve a lot of out side e-mail but do not want to allow them access to
the system at all. Also this will help keep the users table smaller for
our purposes. Using the newest release of rt 2.0.14 I believe

Thank you,

Michael Goldman
Advanced Services
Charter Communications

“The information transmitted is intended only for the person or entity
to which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you
received this in error, please contact the sender and delete the
material from all computers.”

Michael Goldman wrote:

Hello, I was wondering if anyone has been able to find a way to
disable the creation of a user when they submit a ticket or just in
general.

It isn’t clear whether you want to prevent the ticket from being
created or just not add the user to the system.

When a ticket is to be created from an e-mail that e-mail message must
be stored in the database and must have a valid user associated with it
so as to mentain referential integrity.

If you don’t want anybody to be able to create tickets, then remove
the group rights for ‘Everybody’, and simply gives these rights to the
group of people you do want creating tickets. This will cause mail from
’outsiders’ to bounce back to them with a ‘permission denied’ message.

If you want anybody to be able to create tickets then anybody could end
up in your user table. That’s the way ‘RT’ works.

We recieve a lot of out side e-mail but do not want to allow them
access to the system at all.

By definition creating a ticket (or being mailed correspondence) is
accessing the system. If you merely mean that you don’t want them to
have web access, then that’s simple enough: just don’t give them
passwords (which by default ‘RT’ doesn’t do anyway).

Also this will help keep the users table smaller for our purposes.

Do you have a particular reason for wanting a small users table?

If you really want to have anybody able to create tickets but don’t want
them in the user table I guess you could use CanonicalizeAddress in
config.pm to rewrite all non-allowed addresses to the same
pseudo-address. That would only take up one row in the table. But I
can’t think why you’d want to.

For a start, you wouldn’t be able to tell who’d submitted a request.

Smylers
GBdirect

I guess I’m just use to the RT 1 way of handleing things, where anybody
would submit a ticket but they wouldn’t actually be placed into the
users table. Basically the idea for having a small user table, is so we
can search through it very quickly to add users and remove users as that
becomes required.

We are going to be using this for a ticket program for
postmaster/hostmaster issues where we get around 10,000 e-mails a day
(mostly spam, but none-the-less).

Thank you.

Michael

I guess I’m just use to the RT 1 way of handleing things, where anybody
would submit a ticket but they wouldn’t actually be placed into the
users table. Basically the idea for having a small user table, is so we
can search through it very quickly to add users and remove users as that
becomes required.

We are going to be using this for a ticket program for
postmaster/hostmaster issues where we get around 10,000 e-mails a day
(mostly spam, but none-the-less).

But that’s how it’s meant to work, with users being created
automatically. They don’t get any extra privileges – a record of
requestors has to go somewhere. Privileged users are always listed
separately where possible to make management easy. You don’t have
to add users and remove users from the 10,000 if you don’t want to.

In other words, I don’t understand why you think what RT does is
incorrect (and I lean heavily toward it being correct).

Perhaps you’re solving the wrong problem, and need to put spamassassin
or similar in front of RT?

-Rich

Rich Lafferty --------------±----------------------------------------------
Ottawa, Ontario, Canada | Save the Pacific Northwest Tree Octopus!
http://www.lafferty.ca/ | http://zapatopi.net/treeoctopus.html
rich@lafferty.ca -----------±----------------------------------------------