Fixing txNewsletters Encoding and Mail Delivery Problems on cp1251 Sites

Newsletter modules become especially fragile on older sites that still run in cp1251. You can get the backend partially working, only to discover that the frontend subscription page renders gibberish and outgoing messages never arrive.

The two separate problems

• Encoding: the module, templates, and language files must all agree on the same character set.
• Mail transport: a sender address alone is not enough if the server mail configuration is incomplete or invalid.

What usually helps

1. keep all module files, templates, and language files in the same encoding
2. avoid mixing UTF-8 assumptions into a cp1251 project unless you are migrating the whole site
3. verify the actual mail transport path used by the host, not just the from-address
4. test delivery with a minimal script before blaming the newsletter module

When a newsletter tool reports partial or failed delivery without a clear error, the real problem is often server mail configuration. Treat transport verification as a separate task from content encoding.