I've identified the problem although I'm not sure where it is coming from. there appears to be a feature in Rails 3 that auto-detects UTF-8 characaters somewhere in your email and encodes your headers appropriately.
When I started with a fresh Rails 3.0.7 project, I'm able to do the most simple html/plain email and get a content-type header that looks like this: Content-Type: multipart/alternative; boundary="-- ==_mimepart_4dc1cf5d84985_1fc7800d21b0517aa"; charset=UTF-8 I notice that these emails -- which work find in Gmail -- don't have odd-looking =?UTF8?Q? symbols scattered throughout the headers Then, on my project which is already started, when I go to generate an email with what looks like is the exact same settings & content, I get this: Content-Type: multipart/alternative; boundary*="utf8'en'--==_mimepart_4dc1d4f8459fb_22ab800d21b083558"; charset*=utf8'en'UTF-8 It appears that something is malformed here, and Gmail is hiccuping on that weird-looking boundary marker I think. The trouble is, I'm not sure how to turn off the UTF-8 encoding thing or to keep it from kicking in. Actually I'm not sure what is making it kick in here and not on a brand new, from-scratch project. Still investigating, but is it these UTF markers inside the headers that seems to be causing the problem. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
