Hi Mark, We created a chinese-devotion mailman list. The list was created with English as the default language and "en" as the only supported language. We then created three files in the "en/" directory associated with the list: verify.txt, unsub.txt and subscribeack.txt. These files contain a mixture of Chinese and English characters including mailman substitution variables.
When Mailman sends these emails to Windows 7/Chrome/Gmail, iPad & iPhone everything works as expected. When the emails are received on a Mac, the emails are corrupted. Here are the steps we took so far: 1. We verified that the characters in the files are all valid UTF-8. They passed using four different validation techniques. 2. I copied template/zh-CH/verify.txt into the "en/" directory of our list. Please note this file is also a mixture of Chinese and English characters including mailman substitution variables. We ran the test again and got the same results. Please find below a sample of the email received on the Mac usings Mailman's original verify.txt file. Subject:confirm f75bab69c4dca204575d5ee50c54e770d573cf99Date:Tue, 11 Nov 2014 13:43:28 -0600From:chinese-devotion-request@RayStedman.orgReply-To: chinese-devotion-request@RayStedman.orgTo:f...@baz.com 订é é®ä»¶å表 Chinese-Devotion ç确认éç¥ æä»¬ä» from xxx.yyy.191.121 æ¥æ¶å°ä¸ä¸ªè¦ææ¨çä¿¡ç®±å°åï¼"f...@baz.com" <f...@baz.com>å å ¥å°é®ä»¶å表 chinese-devot...@raystedman.orgçè¯·æ± ã为äºç¡®è®¤æ¨ç¡®å®æ³è®¢é æ¤å表ï¼è¯·å夿¤ä¿¡ä»¶ï¼ä¿æåä¿¡ç 主é¢ä¸åãæè 访é®ä¸é¢çç½é¡µï¼ It seems that all the Chinese characters are corrupted. This test was run by a friend that owns a Mac -- I changed the email and ip addresses as a result. Does Mailman do something different when it sends a "zh-CH" email than an "en" email? If so, I need to configure the list with zh-CH as the default and only language. I hope this will not change all the screens to Chinese as I will not be able to maintain the list as the admin. I did see "Mailman as used by Mac users" in the archive where Macs were having problems with digest emails being corrupted. I'm not sure how it applies in our case as we are dealing with the subscription subsystem of Mailman. The one similarity is digest was configured as text in that case -- subscribe is also using text emails in our case. I need to use someone elses computer to debug this issue as I do not have a Mac. What would you like us to do to help isolate the problem? Thanks again, Greg ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org