{"issue":{"state":"open","created_at":"2011-11-14T13:26:17Z","updated_at":"2011-12-12T09:02:17Z","comments":4,"user":{"gravatar_id":"75b8a2d888dc5bd09d227f2ab4f5ade2","id":798969,"url":"https://api.github.com/users/jonatrey","login":"jonatrey","avatar_url":"https://secure.gravatar.com/avatar/75b8a2d888dc5bd09d227f2ab4f5ade2?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"body":"Hello,\r\n\r\nThanks for this transport layer, that's very useful.\r\n\r\nI'm using it in a symphony task with the basic implementation as described in the doc...\r\nWhen sending HTML messages (Content type header is defined as text/html), I get the following response:\r\n\r\n```xml\r\n<ErrorResponse xmlns=\"http://ses.amazonaws.com/doc/2010-12-01/\">\r\n  <Error>\r\n    <Type>Sender</Type>\r\n    <Code>InvalidParameterValue</Code>\r\n    <Message>Illegal header '&lt;!DOCTYPE html PUBLIC &quot;-//W3C//DTD XHTML 1.0 Transitional//EN&quot; &quot;http'.</Message>\r\n  </Error>\r\n  <RequestId>f3f322f2-0ec1-11e1-b20f-3fffda72cbb3</RequestId>\r\n</ErrorResponse>\r\n```\r\n\r\nAfter investigation, I realized, what is **before a colon** is interpreted by amazon as the header name. Looks like this error is pretty common, but I haven't find any case where the body was interpreted as a header.\r\n\r\nI tried adding (did not work):\r\n```PHP\r\n$headers = $message->getHeaders();\r\n$headers->addTextHeader(\"Content-Disposition\", \"inline\");\r\n```\r\n\r\n\r\n","assignee":null,"id":2230427,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"labels":[],"number":13,"title":"InvalidParameterValue : Illegal header","html_url":"https://github.com/jmhobbs/Swiftmailer-Transport--AWS-SES/issues/13","closed_at":null,"url":"https://api.github.com/repos/jmhobbs/Swiftmailer-Transport--AWS-SES/issues/13","milestone":null},"action":"created","comment":{"created_at":"2011-12-12T09:02:17Z","updated_at":"2011-12-12T09:02:17Z","user":{"gravatar_id":"75b8a2d888dc5bd09d227f2ab4f5ade2","id":798969,"url":"https://api.github.com/users/jonatrey","login":"jonatrey","avatar_url":"https://secure.gravatar.com/avatar/75b8a2d888dc5bd09d227f2ab4f5ade2?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"body":"Hey Faz,\r\n\r\nI couldn't get emails accuratly sent with this transport layer.\r\nI tried using another one based on Amazon SDK, and as a result (see comment from 21st of Nov), Yahoo was fine whereas Gmail wasn't working anymore. After updating the swift mailer lib to 4.1.3, emails were delivered accurately.\r\n\r\nI'd suggest you to try to update swift mailer lib first, I'm not sure the problem is on the transport layer.\r\n","id":3103530,"url":"https://api.github.com/repos/jmhobbs/Swiftmailer-Transport--AWS-SES/issues/comments/3103530"}}