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.
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)?
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.
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?
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
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
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.
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.
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
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.
Quote