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.

Fax server doesn't like Thunderbird-composed emails

  • 1 Antwort
  • 1 hat dieses Problem
  • 9 Aufrufe
  • Letzte Antwort von mark333

mark333
mark333
more options

My VoIP provider offers an email to fax service; you send it an attachment with a phone number in the address and it will fax the attachment. When I send messages to this server using Thunderbird, the server ignores them, as if the message had no attachment. If I send using any other client than Thunderbird, the server functions normally.

One significant difference I've noticed is that Thunderbird begins multipart encoding at the top of the message, whereas other clients do some headers first. See screenshots. I don't know if that's significant or if it's a red herring but TB seems to behave differently than others in this way.

My VoIP provider offers an email to fax service; you send it an attachment with a phone number in the address and it will fax the attachment. When I send messages to this server using Thunderbird, the server ignores them, as if the message had no attachment. If I send using any other client than Thunderbird, the server functions normally. One significant difference I've noticed is that Thunderbird begins multipart encoding at the top of the message, whereas other clients do some headers first. See screenshots. I don't know if that's significant or if it's a red herring but TB seems to behave differently than others in this way.
Angefügte Screenshots

Alle Antworten (1)

mark333
mark333 Fragesteller
more options

It's worth noting that the last time I used this capability was in 2019 with Thunderbird 60 and it worked. Back then, the messages were formatted more like my second example, with plain text headers before the multipart encoding starts.