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

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?

It’s not a great solution since you’ll need to redo those edits whenever
you upgrade RT. Another option is setting up your own simple filter at
the MTA level between RT and SES to tweak headers as necessary. This
assumes you’re not delivering directly from RT → SES, but delivering to
a local MTA which relays to SES.

Does RT plan to have support for Amazon SES in the future or are there
any other workarounds?

There is an existing report about this:
http://issues.bestpractical.com/Ticket/Display.html?id=20691

See my latest reply on that ticket.