View Single Post
  #26 (permalink)  
Old July 15th 08, 09:03 PM posted to microsoft.public.windows.vista.mail
Moritz
external usenet poster
 
Posts: 3
Default The message could not be sent. There is not enough memory-

Thanks for your fast answers, Robert and Gary.

First, yes, it is of academic interest. It's a bug and I like bugs to be
fixed.

But there are mail servers configured to allow mails of this size and if you
directly connect to it to exchange emails of this size with other users this
actually works without problems.
You have to consider, that there are very many people out there how do not
have access to any web space to store such data or only to web space with say
250 MB. Such people may see mail as an appropriate way to send larger files
to someone else.
And when they try, they will find their systems very, very unresponsive for
several minutes, because of this bug in WinMail.

I just tested it without a Virus Scanner running (which should have no
influence of the memory used by the WinMail process), and I got the same
result. Looking at the "Commit Size" it even reached more than 3 GB for the
468 MB file.

But thanks for the hint on breaking a message into many pieces. Although I
am not interested in such a workaround (I address exactly that bug), this
might be useful for others.


" wrote:

Why do you want Windows Mail to be able to try to send messages so
large that most email providers will reject them? A typical limit is
10 MB per message.

If you want Windows Mail to at least try to break it up into pieces,
click on Tools, then Accounts, then your email account, then
Properties, then Advanced. If there is no checkmark in the box
before Break apart messages larger than, click on this box, then
Apply; then adjust the allowed size until it is close to your email
provider's limit, but not quite that high, then click Apply again.
Click on OK, then Close.

Note that whoever you're trying to send the video to may have an
even lower limit on the size of incoming messages.

Also note that when Windows Mail complains about not having
enough memory, the actual problem is often interference from an
antivirus program, which Windows Mail seldom seems to be able
to report correctly. What if any antivirus programs do you have, and
have you ever had a Norton or McAfee antivirus program on that
computer, even one of the free trial versions that often come already
installed on new computers?

You could always try uploading the video to a web site meant for
storing videos, then email a much shorter message saying how to
download it from that site.

"Moritz" wrote in message
...
I just had the same problem when trying to mail a 468 MB file via Windows
Mail on Vista 64 Business with 2 GB RAM.
First, this has nothing to do with any restrictions of any ISP! It never
gets this far as to send anything!

When I press the send button, the message window will not go away to start
sending. Windows Mail obviously first tries to read the whole file into
memory and then encode it. Actually it does so bad at this, that it
allocates
1,5 GB of memory and seems to try to get even more. With Base-64 encoding
the
file should get no larger than 624 MB. Still it wouldn't make any sense to
load the file into memory, it should just be streamed in small blocks to
the
mail server!
Windows will try to get more memory by moving as much as possible to the
page file but eventually gives up. Then Windows Mail shows this error
message.
Of course it takes quite some time until Windows gives up, and Windows is
very unresponsive during this time (even on a quad core CPU).

So I consider this issue to be a bug in Windows Mail. There is really no
need to keep the attachment in memory. It just has to make sure, nobody is
allowed to write to the file, while sending it.


"Gunny" wrote:

Hey there. I just recorded a short video message and try to send it to
my
brother'e gmail account and I keep getting the above message!

The video ext is an .AVI (187mb)

Any ideas?
--
Guns


"Gary VanderMolen" wrote:

Email was never meant for sending files that large.
Even if you can find a mail client that would not choke on the initial
encoding process, it would be refused by the outgoing mail server.
So, your concern is of academic interest only.

--
Gary VanderMolen, MS-MVP (Mail)