I have a bit of a problem with my (inherited) RT installation, and I don’t
think even upgrading it to 3.2.2 from 3.0.10 will help it, from the look
of the various modules that control email ticket creation.
If I have a user whose uid is “foo”, they have 3 legal company email
addresses: the main one, the corporate subdomain, and the one at our
parent company, like so:
Email RT tickets can be spawned from any one of the three email addresses,
depending on what mail client/mailbox they’re in at the moment, plus the
user can have a web account with RT as well.
I want them to have the one “foo” account as the requester instead,
regardless of where the ticket is launched from.
I have found no other configuration parameters that affect this. We do
have LDAP running on our network, so the application could look up the
user name to see if they were real, and then assign the LDAP canonical
email address, but that wouldn’t cross reference the other addresses, only
the user name portion.
Is there any tidy way to tell the thing to:
a) whack off the stuff after the “@”,
b) use the remaining username as the account requester, and
c) assign that requester the address listed in LDAP?
Any accounts that did not exist already would be created using just the
username and the LDAP email. Thus one person, lots of email addresses,
one RT account.
I could go digging into the modules and hacking them up until I had a
heavily customized, and not upgradable, version, but that is not my
preferred route. It’s bad enough that I may have to hand abuse the
database to get rid of the cruft accounts. Is there a simple, clean way
to get around this? Or even a known hack that has been tested elsewhere?