[rt-users] After upgrade to RT 4.2, can only access Self Service
Hi, I just upgraded my RT 4.0.7 installation to 4.2.8, and while the upgrade seems to have gone off correctly, I am no longer able to access anything other than the "Self Service" portal using either of my configured accounts. If I punch in a ticket number manually I can view the basics of the ticket, but cannot take any action, view any queues, etc. I can confirm that the database migrations were run and did not report any errors. Any idea on where I might begin in order to troubleshoot this? Thanks, Shane
[rt-users] Determine Requestor Email from Reply-to instead of From
Hi, I am using RT to pick up website-generated support tickets as well as incoming emails from the outside world. We are using Amazon SES as a SMTP provider, and they restrict the "From" header to our own domain, so we are unable to masquerade the emails as the actual users, and must use the Reply-to header to store their actual email. So for example, a generated email might look like: To: supp...@company.com From: "User Name " Reply-to: userem...@address.com In the default configuration it seems that RT reads these tickets as each requestor being at "webs...@company.com". Is there a way to make it take the Reply-to address as the requestor rather than the From address, if and only if it exists? If there is no easy configuration option for this, where might I look in the code to modify this? Thanks, Shane Final RT training for 2012 in Atlanta, GA - October 23 & 24 http://bestpractical.com/training We're hiring! http://bestpractical.com/jobs
[rt-users] Configuring RT to use Amazon SES Despite Non-standard Headers
Hi, I am attempting to get Request Tracker 4.0.5 to work with Amazon SES and have not been able to find much documentation on it. Amazon SES will reject any messages sent by RT due to the RT-Ticket and Managed-by headers, and possibly others, although those are the ones I have seen so far. One option is to edit the code to set those headers to, for example, X-RT-Ticket and X-Managed-by (this one is really non-essential). Is this a good solution? Is there maybe a better one? Does RT plan to have support for Amazon SES in the future or are there any other workarounds? Thanks, Shane Final RT training for 2012 in Atlanta, GA - October 23 & 24 http://bestpractical.com/training We're hiring! http://bestpractical.com/jobs
