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!

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Forwarding an email fails with Line length exceeded

  • 1 回覆
  • 1 有這個問題
  • 3 次檢視
  • 最近回覆由 Zenos

more options

I'm forwarding emails as attachments, but I get an error: An error occurred while sending mail. The mail server responded: Line length exceeded. See RFC 2821 #4.5.3.1.. Please check the message and try again. The emails appear to be based on HTML forms.

I'm forwarding emails as attachments, but I get an error: An error occurred while sending mail. The mail server responded: Line length exceeded. See RFC 2821 #4.5.3.1.. Please check the message and try again. The emails appear to be based on HTML forms.

所有回覆 (1)

more options

There is a report on bugzilla about this: https://bugzilla.mozilla.org/show_bug.cgi?id=300937

However, looking at that RFC, there are several factors that might generate this error, and it isn't at all clear from the error message you've shown us quite which part of the message has offended the smtp server.

https://tools.ietf.org/html/rfc2821#section-4.5.3.1

I wouldn't be surprised that this happens in association with html. An html encoded document could well be presented as a single long line of text, since its own logical line ends are encoded into it and don't bear any relationship to the "physical" line ends that the smtp server is concerned with.

As an example, the two paragraphs above could be encoded as one long line:

https://tools.ietf.org/html/rfc2821#section‑4.5.3.1 <br>I wouldn't be surprised that this happens in association with html. An html encoded document could well be presented as a single long line of text, since its own logical line ends are encoded into it and don't bear any relationship to the "physical" line ends that the smtp server is concerned with.<br>
But I'm not sure if that's relevant. We can't tell which kind of line has given rise to the error message. :-( It might be the subject or the To: line and nothing to do with the message body.

Can you send these messages via a different smtp server to test if this is an idiosyncrasy of the particular smtp server you have been using?