Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Ko téma oñeñongatúma. Ejapo porandu pyahu eikotevẽramo pytyvõ.

Cannot forward emails over c. 200K as attachments

  • 4 Mbohovái
  • 0 oguereko ko apañuãi
  • 1 Hecha
  • Mbohovái ipaháva Toad-Hall

Lt. Commander Data
Lt. Commander Data
more options

When I try to forward emails over c. 200K, I get the following error message:

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.

I have researched this error, and it seems it comes from a line length in the email code being >999 characters long without a space. Now, I get my messages from Yahoo imported into Thunderbird; I can forward such messages as attachments in Yahoo, but not in Thunderbird. Whatever the issue, is there a way to change, alter, or override the RFC setting so I can send larger attachments as emails without encountering this error? I've seen hints on the Web that it might be doable given this or that add-on or by something called GWAVA, but I can't effect a solution myself. Any help would be appreciated. Thanks, John- :)

When I try to forward emails over c. 200K, I get the following error message: 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. I have researched this error, and it seems it comes from a line length in the email code being >999 characters long without a space. Now, I get my messages from Yahoo imported into Thunderbird; I can forward such messages as attachments in Yahoo, but not in Thunderbird. Whatever the issue, is there a way to change, alter, or override the RFC setting so I can send larger attachments as emails without encountering this error? I've seen hints on the Web that it might be doable given this or that add-on or by something called GWAVA, but I can't effect a solution myself. Any help would be appreciated. Thanks, John- :)

Opaite Mbohovái (4)

Toad-Hall
Toad-Hall
  • Top 10 Contributor
more options

If you select email so viewing in Message Pane - click on 'More' and select 'View source'

Is Content-Transfer-Encoding: set as 7bit or 8bit or base 64? eg:

  • Content-Type: text/html; charset=UTF-8
  • Content-Transfer-Encoding: base64

OR

  • Content-Type: text/html; charset=UTF-8
  • Content-Transfer-Encoding: 7bit or 8bit

Does the email you want to forward contain any attachments ?

Toad-Hall
Toad-Hall
  • Top 10 Contributor
more options

How long is the 'Subject' line?

In 'View Source' do you notice if there are any parts of header data that exceed line length ?

Moambuepyre Toad-Hall rupive

Lt. Commander Data
Lt. Commander Data Porandu apoha
more options

The source code doesn't contain anything about 7bit, 8bit, or base64. The content type is "Content-Type: text/html; charset=UTF-8". And it doesn't contain attachments-

Toad-Hall
Toad-Hall
  • Top 10 Contributor
more options

Lt. Commander Data said
The source code doesn't contain anything about 7bit, 8bit, or base64. The content type is "Content-Type: text/html; charset=UTF-8". And it doesn't contain attachments-

Below : Content-Type: text/html; charset=UTF-8 You should see info: Content-Transfer-Encoding: ?

If you see the actual content of the email in the view source then it will not be base64.

You could post an image which shows the View Source. You can blank out email addresses and anything sensitive.