♥Vger Posted December 6, 2005 Posted December 6, 2005 Okay, here's the problem. Many osCommerce sites on the same server all working fine. On one site the e-mail the customer receives when they sign up by creating an account is being encoded and just appears as lines of code. E-mail headers from the site months ago show this: MIME-Version: 1.0X-Mailer: osCommerce Mailer Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit E-mail headers from the site now show this: MIME-Version: 1.0X-Mailer: osCommerce Mailer Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: BASE64 It seems to be declaring the Mime Version, Content Type, and Content Transfer Encoding twice - the second time being encoded. All other mail functions are working fine, and I have used File Compare to check this sites files against others and they are identical. Has anyone come across this before?? Vger
Guest Posted December 6, 2005 Posted December 6, 2005 what happans on other servers? sounds like mim compliance went out the window . . .
♥Vger Posted December 6, 2005 Author Posted December 6, 2005 Other servers are all fine, and all the other sites on this one server (have checked). Vger
Guest Posted December 11, 2007 Posted December 11, 2007 It seems to be declaring the Mime Version, Content Type, and Content Transfer Encoding twice - the second time being encoded. All other mail functions are working fine, and I have used File Compare to check this sites files against others and they are identical. Has anyone come across this before?? A recent update to my server also caused emails to come in either blank, or base64 encoded (but only in outlook/oe or windows mail). Putting this in my .htaccess file fixed it for me: PHP_VALUE mbstring.func_overload 0 After further investigation, the web server has a setting of mbstring.func_overload=3 in it's php.ini file to support other character sets for other sites on the same box. Around 20 sites were affected for me and each was solved with the above addition to my .htaccess file for each account. Won't hurt to give it a try. You can always remove the extra line from your .htaccess file if it doesn't solve it for you. :)
Recommended Posts
Archived
This topic is now archived and is closed to further replies.