Outlook 2010 message size limit

[cokewithvanilla]

Ever since office 2010, its required a registry edit to send files larger than 25mb.... well, I tried using the reg edit and it isn't working any longer (at least not for me).

Anyone have a fix for this?

And this is on any email account, I know it is not a limit on the server.

 

[WebMattR]

Two questions:
The registry edit did work for you, but now isn't?
And why are you emailing such large files, rather than sending them via FTP, or just storing them on a server (if it's all internal)?

 

[cokewithvanilla]

I have used this edit on one or more of my computers before (probably this one, and my HTPC) with success. I have since reloaded both of these computers. I have not had the need until now to use the edit,,, and when I tried it, it didn't work.

So, I know the edit used to work, I've used it myself... now it isn't.

Why send such large files? 25mb is real small.... one picture as a tiff will bust that limit. It is dumb for outlook to have this limit built in... aside from that, I don't send large files often, but sometimes it is necessary.

 

[WebMattR]

After making the change, did you reboot your machine? Not technically necessary, but I always do as a precautionary measure after rebooting machines.

That's either a high resolution or huge tiff. Are you sending whole documentations in tiff format? And have you tried packing them into archives?

 

[sygnus21]

Be aware that some ISP's may limit e-mail size. In other words, no matter the hack you try, If your ISP has set a limit, you ain't sending it. With that said, you may want to find out from them if such a limit exists.

BTW..... "Attachment size exceeds the allowable limit" error when you add a large attachment to an email message in Outlook 2010

 

[cokewithvanilla]

Yes, I always reboot after registry changes. I tried using '0' and '10000000' with no luck.

10.1mp tiffs... not very high res. LZW compression is an option, archives are usually a waste of time. Besides, I am not trying to put a band-aid on the problem by sending off one tiff at a time... I want to send 4..5..6..

Being able to send the files and being able to try to send them in outlook are two different things. Besides, I have two emails, one on my own website, and one university account. I know I have no limits on mine. Outlook doesn't even let me load the attachment.

I've seen that KB article, and my problem happens on POP, IMAP, Exchange.. it just can't be the servers.... especially with the pop

 

[WebMattR]

Archives aren't a waste of time. They're actually very good at compression. Try something like 7zip, and compress it into a RAR or similar archive.

What's the back-end for your email account on your website? Is it provided by the web site hoster, or by an exchange server? If the latter, the limit would be something you'd configure in Transport Settings Properties on the Exchange Server itself.

 

[cokewithvanilla]

The reason I don't waste time with archives, especially those like .7z: Many times I am sending files to people who are too stupid to deal with those archives. Also, the best archives will not allow me to accomplish what I want to accomplish (sending 100 mb with an outlook limit of 20). I do not like wasting time with compressing and uncompressing, I'd rather have to download a little more.

Now I know my server can support this file, this is not my issue. Outlook is NOT reporting what the server says. AFAIK, the pop server does not communicate with outlook, so outlook won't know if there is a limit. Not only that, but I have sent files this large before using the method mentioned on the server I am trying to send them.

I am trying to solve an outlook problem... not a server issue and not a one time issue. I can send the file from my webmail account on my server, which actually specifies a limit of 100mb. However, I cannot end the same file from outlook. Obviously, this is not a server issue.

 

[Kari]

I do not like wasting time with compressing and uncompressing, I'd rather have to download a little more.

You need a pretty fast upload speed to save time sending uncompressed over 20 MB images.

Let's say you have a really fast 100/10 Mbps connection, 100 Mbps down and 10 Mbps up. This of course is only achieved in optimal conditions, but we assume you get always the full UL speed. In this case, the uploading of a 25 MB file (sending it as attachment) would take 21 seconds.

A 10/1 Mbps connection would need in optimal conditions 3 minutes 25 seconds to send that file. Compressing this file would take a few seconds, but would automatically save more time it took to compress it when finally sending.

Kari

 

[WebMattR]

The reason I don't waste time with archives, especially those like .7z: Many times I am sending files to people who are too stupid to deal with those archives. Also, the best archives will not allow me to accomplish what I want to accomplish (sending 100 mb with an outlook limit of 20). I do not like wasting time with compressing and uncompressing, I'd rather have to download a little more.

Now I know my server can support this file, this is not my issue. Outlook is NOT reporting what the server says. AFAIK, the pop server does not communicate with outlook, so outlook won't know if there is a limit. Not only that, but I have sent files this large before using the method mentioned on the server I am trying to send them.

I am trying to solve an outlook problem... not a server issue and not a one time issue. I can send the file from my webmail account on my server, which actually specifies a limit of 100mb. However, I cannot end the same file from outlook. Obviously, this is not a server issue.

Well, I can appreciate the honesty, even if it doesn't speak well of your clientel.

Well, in that case, I would try running the FixIt on this kb article. It worked for me on my machine.

 

[cokewithvanilla]

You need a pretty fast upload speed to save time sending uncompressed over 20 MB images.

Let's say you have a really fast 100/10 Mbps connection, 100 Mbps down and 10 Mbps up. This of course is only achieved in optimal conditions, but we assume you get always the full UL speed. In this case, the uploading of a 25 MB file (sending it as attachment) would take 21 seconds.

A 10/1 Mbps connection would need in optimal conditions 3 minutes 25 seconds to send that file. Compressing this file would take a few seconds, but would automatically save more time it took to compress it when finally sending.

Kari

I appreciate you trying to educate me on this issue, but I have already explained my reasons for not using an archive, which your post does not address. I do not have time to explain to everyone I send files to that they need WinRAR or 7zip to extract my file (not to mention having to educate them on how to get download the program and install it without somehow managing to get a virus). On top of that, with no modification (simply, right click, add to rar or 7z) files are the sizes as follows: 40.1 uncompressed, 38.4 rar, 38.5 7z. I might be able to achieve better compression, but even if I could, again, this will not even get me NEAR the 20mb limit. On top of that, the hassle of compressing/uncompressing is more difficult than me clicking send, and going about by business while the file sends. In the end, I'll never achieve my 100mb goal on a 20mb limit with an archive, plain and simple.

Well, I can appreciate the honesty, even if it doesn't speak well of your clientel.

Well, in that case, I would try running the FixIt on this kb article. It worked for me on my machine.

Thanks for the info. I tried the fixit, which i assume adds the proper registry entry, and it did not work

This is getting really frustrating. I've fixed this before with the simple edit, I wonder what could have changed in the last 6mo-yr since I did it,

 

[WebMattR]

If you dig into your registry after running that fix, are the keys there?

 

[cokewithvanilla]

If you dig into your registry after running that fix, are the keys there?

Yep, they still show up and with the same values I saved them as

 

[WebMattR]

Okay. Let's start digging.

Firstly, you're positive you were in Office\14.0\outlook ? Sorry for doubting you, but I'm trying to be precise as possible, and if you had/have an older version of office installed, the possibility the key is simply in the wrong place does exist.

Next, let's do a sfc, just to cover our bases.
> Start
> All Programs
> Accessories
> right click on "command prompt" and select run as an administrator
> type in sfc /scannow
> If it reports errors, re-run it.
> Tell us if there's still errors.

If there *are* errors, try running outlook again after the second run of sfc.

Next, I would start with deleting your registry keys you added. Then try that Microsoft utility again.

If that doesn't fix it, I'd do a repair of Office (I'm afraid I can't recall how to do that, and am no longer on a machine with Office 2010, so I cannot tell you. When you reply next with how the previous steps went, I'll add a reply on how to do this if you'd like).

 

[cokewithvanilla]

I have never had another version of outlook installed here. I checked, and yes it was in the right place.

I ran sfc twice, said it couldn't fix all issues... I checked the log and it couldn't delete some files in WinSxS... I don't think this is an issue.

Deleted the keys, ran fix it.

repaired office.

Checked it after each step... still, same issue

 

[WebMattR]

You said you had two accounts... do you access them both through Outlook, and does it not work for both of them?

 

[cokewithvanilla]

I have three accounts on there

Google Apps Imap
Microsoft exchange through UTK, provided by MS
POP3 my server

All of them have the same issue. while trying to add an attachment, it is immediately rejected due to size

 

[WebMattR]

I stole this from somewhere else. We've already done the first bit, but the second bit is new, I believe. Perhaps try this?

1. Run regedit on the outlook client computer that has the issue.
2. Locate the following registry key:
[HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook]
3. On the Edit menu, click Add Value, and then add the following registry value:

Value name: DisableBGSave
Data type: REG_DWORD
Radix: Hexadecimal
Value data: 1

Note: You will see the Policies key if policies are deployed in your environment. If so, add the registry key under the following registry key:
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Outlook]

4. Restart Outlook and test the issue again.

 

[cokewithvanilla]

I do not have a 'policies'

Mine would go HKCU>Software>Microsoft>office>14>outlook

so I tried putting that key in that location

still noting

 

[WebMattR]

Interesting. I'm thinking it put it in a subdirectory of outlook for me, but I'm afraid I'm no longer at work, and lack a machine with Office 2010 to check. I'll try to take a look in the morning, and let you know what I find, alright?