I now have got this working successfully, and I believe it was
accomplished in as clean, flexible, and functional a manner as
possible.
For anybody who is interested in what I was asking about in this
thread, I've begun documenting what I've done in the wiki here:
http://wiki.bestpractical.com/vi
On Fri, Oct 2, 2009 at 1:10 PM, Jerrad Pierce
wrote:
>> 2. If an email is from an email address that does not match any
>> user, a ticket is created with a special 'email user' as the requestor
> Doable with a custom Interface::Email extension
That's one of the things I was looking at. I'll see
> 1. If an email is from an email address that matches an existing
> user that exists in RT, a ticket is created with that user as the
> requestor.
Out of the box.
> 2. If an email is from an email address that does not match any
> user, a ticket is created with a special 'email user' as the req
I've looked extensively through the mailing list archives and searched
google but I feel like I have not found a definitive answer for what
it is I want to do.
We have an old instance of RT (2.0.14) that creates tickets when
customers send email and this has resulted in over 400,000 user
records i