[rt-users] RT features and RT database

[Carl Makin]

Hi Again, :)

Tomas A. P. Olaj wrote:

>1)
>If I want to update users in the RT database (in our case a
>PostgreSQL database) using a script (e.g. Python with Postgres
>functions) internally in the database, can I do it without affecting other
>parts of the RT system?
>
>E.g. using LDAP authentication (if the user doesn't exist, the RT
>creates a new account with the correct username)  and incomming requests
>from valid users through e-mail (also creates a default user in RT if the
>user doesn't exist - but with the e-mail address as the username instead
>of the given university unix account username).
>  
>
See http://wiki.bestpractical.com/index.cgi?Contributions

>3)
>Can a user have multiple e-mail addresses? E.g. an existing user can send
>requests from different e-mail accounts. It could be necessary to collect
>and "bind" e-mail addresses to the same user, to prevent double accounts
>to appear.
>  
>
No.  There is only 1 email address per user.  You can use the 
canonicalise address function in RT_SiteConfig.pm to do simple address 
rewriting.  You could also do some magic inside sendmail if you were 
desperate.  See http://www.sendmail.org/m4/features.html and the 
"genericstable" feature.

>4)
>Good referenses to deal with spam in RT (that would say after externally
>filtered out spam in the e-mail system). A spam e-mail will trigger an
>automatic answer to the sender. That's not preferred.
>  
>
Have a look at;

http://wiki.bestpractical.com/index.cgi?SpamFiltering

>5)
>Closing requests: is there a soft close/hard close support in RT? A user
>can re-open a case which has been closed with a simple message like:
>"thanks for helping!".
>  
>
No.  This annoys me a little too but our userbase is moderately small 
(100 or so) and so can be trained. :)


Carl.