Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×
Google IT Technology

Google Increases Gmail Attachment Limit To 50MB For Recipients (betanews.com) 51

Mark Wilson, writing for BetaNews: With Gmail you can now receive attachments up to 50MB in size. It's important to note that the new attachment limit only applies to incoming email. Google would much rather you make use of Google Drive if you want to send large files to people. When it comes to sending files, you are limited to attaching up to 25MB of data in the form of one or many files. If you try to attach files that go over this limit, you'll be prompted to go down the Google Drive route instead. Not much useful, then.
This discussion has been archived. No new comments can be posted.

Google Increases Gmail Attachment Limit To 50MB For Recipients

Comments Filter:
  • by sexconker ( 1179573 ) on Thursday March 02, 2017 @04:07PM (#53964941)

    Not much editor good.

    • by AvitarX ( 172628 )

      It's a weird claim to make too.

      They make it really easy to send where the link gets the file (which in theory is as secure as an e-mail), the real issue is someone sending me something and getting a bounce.

    • Really not useful since, like Google, most other mail services limit the size of attachments too.
    • by WallyL ( 4154209 )

      Such doge! Such wow.

  • by sremick ( 91371 ) on Thursday March 02, 2017 @04:19PM (#53965023)

    If you're trying to use email to transfer files that large, you're doing it wrong.

    • Re: (Score:3, Informative)

      by Anonymous Coward

      I don't normally do this, but... oblig xkcd [xkcd.com]

    • Not if it works. Pretty simple.

      Obviously, it doesn't work with Gmail, so you're kind of right, too.

    • by ls671 ( 1122017 ) on Thursday March 02, 2017 @05:51PM (#53965813) Homepage

      True enough, a 640K limit should be plenty for everybody. If nobody should ever need more than 640K...

    • If you're trying to use email to transfer files that large, you're doing it wrong.

      Why?

      • Multiple reasons:

        1) Most people won't accept "large*" email (admittedly the definition of large has shifted as capacity has shifted)
        2) Binary files have to be encoded as 7bit text for transmission which means your 50Mb email file can take a file that is ~37.5Mb
        2a) Your /sending/ email server may well let you upload ALL of a 500Mb file, dump it to /dev/null THEN tell you it's not taking files over 50Mb
        2b) When you split the file into 50Mb chunks it will then let you upload those too, and then tell you it's n

        • and you stopped reading.

          No, I read the all.

          Question about 2d though. My understanding might be stale, but I thought that one of the ways that Google was able to save on costs, was by making all of their services use the same storage backend. So uploading to Google Drive, should take the same amount of time as uploading to GMail.

          • 2d) supposes you're one of the people who can't learn a new method of transferring files and are still using Outlook or some other "thick" email client.

      • by Lehk228 ( 705449 )
        because unfortunately, despite being something that people regularly want to do, moving an arbitrary size file from computer A to computer B has always been more complicated than it needs to be.
    • by Anonymous Coward

      When transferring pictures from my Android tablet to my PC, I've found e-mail to be the easiest route. Sure it may be the wrong way, but it's still the easiest way.

      USB? Requires plugging in the cable, and figuring out the adb command line to transfer the files - or researching which other tool can do the transfer. On other devices I've always used USB mass storage, which is not supported on Android (for good reasons). The e-mail will be done transferring before I even find the cable, so why bother researchi

    • Back when I was doing tech support for an ISP, people would complain about the 5MB mailbox limit. My answer was you don't use the postal service when you move houses.

  • by Vegan Cyclist ( 1650427 ) on Thursday March 02, 2017 @04:26PM (#53965099) Homepage

    I might be an old fuddy-duddy, but is it odd that I'm still irked when people email more than 1-2mb? Especially given how many file-share options exist? Until a few years ago I'd be fine with uploading a larger file to my own FTP site and sending a link to a URL, and it's so much easier now with GoogleDocs, Dropbox, etc...maybe I'm just old.

    • by networkBoy ( 774728 ) on Thursday March 02, 2017 @04:30PM (#53965135) Journal

      you're old.

      but so am I, and I agree with you.

    • by Anonymous Coward

      Eh, I just sent probably around 30 megs of attachments in an email. I was sending pictures and it's a hell of a lot easier to just drag and drop rather than upload to file share site, grab link and paste into email.

    • by tlhIngan ( 30335 )

      I might be an old fuddy-duddy, but is it odd that I'm still irked when people email more than 1-2mb? Especially given how many file-share options exist? Until a few years ago I'd be fine with uploading a larger file to my own FTP site and sending a link to a URL, and it's so much easier now with GoogleDocs, Dropbox, etc...maybe I'm just old.

      What irked me more were people who used the old RapidShare etc. to do this, back when those file services gave you barely any speed and made it take hours to download a

    • I guess things would be better if people knew how email works. First you inflate the file size by some funky encoding, then you store and forward the message on all those servers. But who cares in an age where email = webmail anyway...
    • If you had mentioned posting a file to usenet, we would know you really are old.
    • Note: I'm generally a fan of sending a link, but here's the counter argument. The advantages of the attachment over the link is that the sender no longer needs to worry about hosting the data. What if the sender needs to clear up their storage space? They might delete the data that a receiver will end up relying on. As the sender, you might fret about cleaning up data you may or may not have sent links out to. With the attachment there's kind of a built in expiration of the data. In addition, the receiver m
  • by 93 Escort Wagon ( 326346 ) on Thursday March 02, 2017 @04:26PM (#53965105)

    Dear Google: When a Gmail user attaches a 20+ MB file to an email and types the name of a mailing list into the "To:" field, is it too much to ask that a painful jolt of electricity be sent through the keyboard and into their body?

    I know a lot of sysadmins who would upvote that RFE, if given the chance.

    • by gmacd ( 181857 )

      In the old days I remember discussing missing assembler commands. One of them was LVK or something similar. The purpose was to provide "line voltage to keyboard" as direct user feedback...

      • But the highest voltage in my laptop is around 30 volts for the LCD backlight

      • I remember, in the late 70s, a teacher talking about the "HCF" assembly command - Halt and Catch Fire.

    • Or that it automatically use google drive and send a link to it instead? That way you don't have to waste time thinking about file size in 2017 and beyond.
  • Not much useful, then

    You do know there are other email services, right? Services that might not have a cap on send file sizes. In other words, just because Gmail limits sending files over 25 MB, doesn't mean a 50 MB cap couldn't be useful to receive files from other senders.

  • You don't get to choose the limits for sending to recipients. The receiving server is the one that decides what they'll accept.

    Why don't know invent a way to teach Joe Six Pack about appropriate resolution and quality of photos. I'm sick of dealing with people who want to know why they can't send 20 photos, each much larger than they will ever really need thanks to the megapixel race, through email.

    They don't seem to get why someone would not want to down a huge batch of files they will likely look at only

    • Re: (Score:3, Insightful)

      by Anonymous Coward

      If this was 2008 maybe. I can download gigabytes worth of data a day on my phone let alone my cable internet so why the hell do we have bizarrely tiny limits on email size? Who in this day an age is going "hmmm 30 megs is way too big for me and my internet connection"?

      • Because of the way email works.
        Servers have to store and forward messages they're delivering.
        Messages usually go through multiple servers, each of them has to store the entire message, sometimes for days while it attempts delivery.

        • by tsqr ( 808554 )

          Just another tragedy of the commons. It works fine for me; who cares if it tears up the infrastructure?

        • Because of the way email works.

          And you don't think Google knows how email works? If a system can't handle a message size, it'll reject the message. As far as the fact that multiple servers will need to hold onto their copy of the message for days, big friggin' deal. It's the database that holds the message at rest which is the one that's more at risk of being overwhelmed with years of large messages. Not the en-route servers which only hold onto it for a short period of time.

          • OK, let's say I send an email with a 100MB attachment.

            I put 100 email addresses, all at different domains in the To field.

            The server now has to send out 10GB of data.

            Meanwhile, it has to send everyone else's email too, in a reasonable time.

  • When nobody else will accept an attachment over 10MB, how useful is the ability to send them? There's a reason Google directs people to Google Drive.
  • This is an improvement for mail bombers: it now takes 300 messages to fill a Gmail account.

I've noticed several design suggestions in your code.

Working...