Sorry for the noise. Found it. One of my custom scripts was printing the response of an HTTP POST (to Slack), and apparently that finds its way into the response to postfix.
-A On Mon, Jun 1, 2015 at 11:30 PM, Aaron C. de Bruyn <[email protected]> wrote: > Tickets are coming into the system multiple times. > > When I look at the Postfix queue, I see messages queued up for retry like: > > -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient------- > 64A8227 1915 Mon Jun 1 22:48:12 [email protected] > (temporary failure. Command output: RT server error. The RT server > which handled your email did not behave as expected. It said: > HTTP::Response=HASH(0xb1b9b68)okok Ticket: 1118 Queue: support Owner: > Nobody Status: new Subject: test Requestor: [email protected]) > [email protected] > > -- 2 Kbytes in 1 Request. > > The response from rt-mailgate looks like it successfully created the > ticket (and I can see ticket 1118 in RT). > > Looking through the rt-mailgate code around line 238, it checks for > the response 'ok' or 'not ok' starting at the beginning of the > response. In this case, it looks like there is > 'HTTP::Response-HASH....' at the beginning of the response. Any idea > where that's coming from? > > -A
