Этот сайт имеет ограниченную функциональность, пока мы проводим техническое обслуживание для улучшения его работы. Если какая-либо статья не решила вашу проблему и вы хотите задать вопрос, наше сообщество поддержки ждёт вас: @FirefoxSupport в Твиттере и /r/firefox на Reddit.

Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

Fax server doesn't like Thunderbird-composed emails

  • 1 ответ
  • 1 имеет эту проблему
  • 9 просмотров
  • Последний ответ от 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.
Приложенные скриншоты

Все ответы (1)

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.