We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

ابحث في الدعم

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Fax server doesn't like Thunderbird-composed emails

  • 1 (رد واحد)
  • 1 has this problem
  • 9 views
  • آخر ردّ كتبه 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.
Attached screenshots

All Replies (1)

mark333
mark333 صاحب السؤال
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.