E-Mail Encoding
Page: 1
Recent posts in this topic
If I put two spaces in an object the e-mail inserts an A with an accent over it for the first space. If I look at the source code for the message I see =C2=A0. The object shows up fine in aC and the database. This didn't happen with version 1.0.0 but I'm not sure which upgrade introduced the problem. We're on 1.0.4 now.
J.R.
cbtrussell
on Dec 5. 2007. 10:03 pm
We have the same problem - also running 1.0.4. This is a particular problem because the RTEC seems to want to add a lot of extra spaces, at least for us in FireFox.
Since the database is clean I think it has something to do with the SwiftMail module aC is using to send e-mail notifications. I have not been able to track it down though.
J.R.
Ilija Studen
on Dec 6. 2007. 7:20 pm
Hi JR,
In v1.0.4 activeCollab forces 8-bit email encoding and that might cause the problem. Can you please try adding this line into config/config.php (in definition block):
Please let me know how it went.
In v1.0.4 activeCollab forces 8-bit email encoding and that might cause the problem. Can you please try adding this line into config/config.php (in definition block):
define('EMAIL_ENCODING', null);Please let me know how it went.
activeCollab team member | LinkedIn
Ilija Studen
on Dec 6. 2007. 8:26 pm
Ok, forgot about this directive too. Add this:
Forced charset and encoding are the only mailing things changed in v1.0.4.
define('EMAIL_ENCODING', null);
define('EMAIL_CHARSET', null); Forced charset and encoding are the only mailing things changed in v1.0.4.
activeCollab team member | LinkedIn
I had the same problem. I *THINK* I have corrected it.
In defaults.php, EMAIL_CHARSET should be set to "utf-8" (with a hypen) instead of "utf8" without the hyphen.
When I changed that, my mail reader (Outlook) recognized the correct character set, whereas before it was defaulting to Western European
In defaults.php, EMAIL_CHARSET should be set to "utf-8" (with a hypen) instead of "utf8" without the hyphen.
When I changed that, my mail reader (Outlook) recognized the correct character set, whereas before it was defaulting to Western European
I have verified that changing "utf8" to "utf-8" has corrected this problem and we are no longer getting garbage characters embedded in our emails.
Ilija Studen
on Jan 16. 2008. 12:36 pm
Thank you very much for the info!
We'll have it tested and if it really fixes the problems this fix will be included in the next release.
We'll have it tested and if it really fixes the problems this fix will be included in the next release.
activeCollab team member | LinkedIn
