Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

Inline styling gets deleted when sending an HTML template

  • 1 Antwort
  • 1 hat dieses Problem
  • 10 Aufrufe
  • Letzte Antwort von Matt

JS12345
JS12345
more options

I use an HTML signature template in Thunderbird, but when sending out an e-mail to a recipient who uses Gmail or Inbox it loses the font-family inline styling and defaults to Times New Roman or Helvetica.

Outlook does not remove the font-family so it seems to be happening only when sending from Thunderbird to Gmail.

I have Calibri Light, 11pt specified as the font in HTML and in Thunderbird Settings.

Allow messages to use different fonts checkbox doesn't seem to affect anything.

Any ideas on how to bypass or fix this problem?

I use an HTML signature template in Thunderbird, but when sending out an e-mail to a recipient who uses Gmail or Inbox it loses the font-family inline styling and defaults to Times New Roman or Helvetica. Outlook does not remove the font-family so it seems to be happening only when sending from Thunderbird to Gmail. I have Calibri Light, 11pt specified as the font in HTML and in Thunderbird Settings. Allow messages to use different fonts checkbox doesn't seem to affect anything. Any ideas on how to bypass or fix this problem?

Alle Antworten (1)

Matt
Matt
  • Moderator
  • Top 10 Contributor
more options

A signature template, most of those we see originate in Microsoft office and are so full of Microsoft office objects as to be indecipherable. However you appear to be able to get in there to read it.

I just filed a bug about fonts showing as uninstalled if the font family contains alternate fonts.. Do you have the same issue if font family tag is reduced to a single font name, with no substitutes? The two things might be related.