Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

gibberish font when replying or forwarding

  • 1 antwurd
  • 1 hat dit probleem
  • 1 werjefte
  • Lêste antwurd fan Toad-Hall

carltonlaw
carltonlaw
more options

Whenever a message is replied to or forwarded, the recipient gets gibberish characters in the prior messages on that thread. Like this: ��������������� J. These characters appear randomly and makes reading the thread nearly impossible. Thanks for any help! Graham

Whenever a message is replied to or forwarded, the recipient gets gibberish characters in the prior messages on that thread. Like this: ��������������� J. These characters appear randomly and makes reading the thread nearly impossible. Thanks for any help! Graham

Alle antwurden (1)

Toad-Hall
Toad-Hall
  • Top 25 Contributor
more options

What server are you sending via eg: yahoo, comcast, att

Sadly some US ISP's like AT&T and Bellsouth have started *corrupting* their customers' e-mail.

If the customer sends in windows-1252 and includes for example special punctuation characters or a non-break space xA0, the ISP doesn't correctly interpret the the message as windows-1252 but as UTF-8. In UTF-8, xA0 is not valid and gets replaced by the so-called replacement character, � (0xEF 0xBF 0xBD).

Since the e-mail is still windows-1252 encoded, the recipient's client displays �.

Try this first: Set preference mail.strictly_mime to true.

  • Menu app icon > Options > Options >Advanced > 'General' tab
  • click on 'Config Editor' button - it will say be careful :)
  • in top search type : mime
  • look for this line: mail.strictly_mime
  • If set to false, double click on line to toggle value to true.
  • close window - top x

If still a problem then try: If still using version 68

  • Menu app icon > Options > Options > Display > 'Formatting' tab
  • click on 'Advanced' to see encoding
  • Set 'Unicode' on both Outgoing and Incoming
  • Select Check box "When possible, use the default text encoding in replies"