Támogatás keresése

Kerülje el a támogatási csalásokat. Sosem kérjük arra, hogy hívjon fel egy telefonszámot vagy osszon meg személyes információkat. Jelentse a gyanús tevékenységeket a „Visszaélés bejelentése” lehetőséggel.

További tudnivalók

A témacsoportot lezárták és archiválták. Tegyen fel új kérdést, ha segítségre van szüksége.

problem sending message, temporary size limit of server

  • 4 válasz
  • 2 embernek van ilyen problémája
  • 7 megtekintés
  • Utolsó üzenet ettől: snitzerperio.com

more options

I get this message when I try to send mail with attachments of less than 365 KB. "The size of the message you are trying to send exceeds a temporary size limit of the server. The message was not sent; try to reduce the message size or wait some time and try again. The server responded: 4.1.1...temporary failure." This just started happening. I've e-mailed files with much larger attachments and never had an issue. I tried e-mailing smaller attachments with the same results. I also tried waiting until the next business day hoping that the issue would resolve itself to no avail.

Please Help!

Kim

I get this message when I try to send mail with attachments of less than 365 KB. "The size of the message you are trying to send exceeds a temporary size limit of the server. The message was not sent; try to reduce the message size or wait some time and try again. The server responded: 4.1.1...temporary failure." This just started happening. I've e-mailed files with much larger attachments and never had an issue. I tried e-mailing smaller attachments with the same results. I also tried waiting until the next business day hoping that the issue would resolve itself to no avail. Please Help! Kim

Összes válasz (4)

more options

The error message is coming from your email providers server. What do they say when you ask them what is wrong with their equipment?

more options

They say it is not their server. It must be a limitation or bug in Thunderbird.

more options

Thunderbird does not make up fake server messages. It is your providers server that issued the message.

more options

Thanks for your insight...just trying to get the facts, not suggesting anyone's at fault here...