Home Forums Newsletter Plugin Support Mails charset is enforced to “us_ascii” regardless the encoding global option

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #339618
    bfu0123
    Participant

    Good day, the plugin sends all mails with Content-Type: text/html; charcode=us_ascii header regardless if I use the SMTP plugin or not. That’s causing wrongly displayed international letters. How can that be fixed?

    #339631
    Stefano
    Keymaster

    Do you use wp mail smtp pro and that plugin has the tracking option active?

    #339632
    bfu0123
    Participant

    Probably no if you mean

    Click Link Tracking
    Open Email Tracking

    Those options are not used. The mails I sent by Newsletter were not processed by WP Mail smtp anyway as I don’t find them in it’s log.

    #339633
    Stefano
    Keymaster

    Hi, if the emails generated by Newsletter are not sent by wp mail smtp, you probably have one of our delivery addon, please check for it. Anyway, the charset is set by some external code since we set the charset to utf8.

    #339634
    Stefano
    Keymaster

    If possible send a test email to test@thenewsletterplugin.com so I can check the source to see if something can be identified.

    #339783
    bfu0123
    Participant

    Now it gets clearer. I was falsely suspecting the plugin to insert wrong charset header but now it seems if the HTML body is already encoded to only low ascii characters, the us-latin is selected adequately. I was able to receive a mail with international latin body and us-ascii charset which displays correctly. The bug causing the mail body broken is revealed by newsletter subject having characters using diacritics. I have made multiple tests having identical email body, differing only in subject. In cases when subject contained international latin, the subject was still encoded correctly, but the body encoding was all broken.

    #339785
    Stefano
    Keymaster

    Hi, there is still a possible problem, since the plugin always set the charset to utf8. If you receive the message with another encoding, another plugin or the mail service is reencoding it. That’s not a problem IF the message is actually re-encoded correctly. About the subject, the encoding of the subject is not connected to the encoding of the content, it is specified in the subscjet itself.

    #339863
    bfu0123
    Participant

    I think the issue was resolved by removing newsletter message hook which has rebuilt the HTML entirely. Now the code page seems be correct in testing.

Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.