5 ms·
It's already pretty trivial to set up a standard IMAP client and sync all your mail to your desktop. Some clients even support GMail's labels so you don't have
by sp332 14y ago
It's already pretty trivial to set up a standard IMAP client and sync all your mail to your desktop. Some clients even support GMail's labels so you don't have to deal with that. (Each "label" shows up as a different IMAP folder, so normally you end up with a copy of each email for each label you give it.)
- sneak 14y ago> It's already pretty trivial to set up a standard IMAP client and sync all your mail to your desktop. No, not by any means. What magicalist is describing is "pretty trivial". What you are describing is a big pain in the ass.
- recuter 14y agogmvault.org or if you hate the command line, most desktop mail clients (Apple Mail, Mozilla Thunderbird).
- sp332 14y agoWhat, just setting up an email client? Most mainstream apps now have presets for major services so you don't have to pick port numbers or figure out what authentication methods to use. Just type your address and it looks up the server settings for you, one click and you're done.
- jlarocco 14y agoWhere is the pain in the ass? Launching the client, clicking on the Google icon and entering your username/password? Is it really so difficult?
- stevewilhelm 14y agoCurrently have over 90,000 emails (~9 GB worth) archived in my GMail account. Any idea how long it would take to transfer it all to my desktop via IMAP?
- nodata 14y agoIt'll take a little over 2 hours on a 10 mbit line.
- skorgu 14y agoUnscientifically I've seen between 1-3 messages per second via imapsync so ~a day. The bottleneck seems to be the IMAP protocol or rate limiting on google's side, I've certainly never seen it approach wire speed.
- 3825 14y agoGoogle has published total "bandwidth limits" where they say[1] "To address migration needs, you can download your entire mailbox approximately 3 times per month." [1] https://support.google.com/a/bin/answer.py?hl=en&answer=1071518 https://support.google.com/a/bin/answer.py?hl=en&answer=...
- droopyEyelids 14y agoFurthermore, you have to jump through several difficult-to-recognize hoops to get that 9GB on your disk. IMAP will only sync what the sever feels are recent emails, and envelope information for the rest.
- nodata 14y agoofflineimap will do it without hoops.
- ramblerman 14y agoIf you are capable of storing a backup more safely than the countless google datacenters, I would assume setting up an SMTP server is the easy part.
- gutnor 14y agoWe are talking about migration plan here - eg: moving from gmail to hotmail without losing your data, or better transferring them to your new provider. In any case, your data may be physically safe in Google datacenter but you are still one Google policy breach away from losing your access to it.
- magicalist 14y agoYes, I should clarify that I think it's great that IMAP support exists, that you can certainly backup your email relatively easily today, and that the Data Liberation/Takeout thing is great in general. I'm using email sync as the example here, but the benefits would really come from a universal (or more universal than today) sync, not just an easy email sync. I just think Drive would be a great way to unify backup methods across the Data Liberation options. Gmail backup is already relatively easy, but some of the others are less so, and being able to turn them all on with a few clicks (rather than remembering to visit the web interface and exporting every few weeks) would seem to be a better solution. Ideally IMAP support would continue, and, even more ideally, the hypothetical Drive backup format for a gmail account would be some typical email client save format for IMAP accounts so you could (at least somewhat) transparently open the backup in a major email client. All of this is certainly not trivial, and less so now that I thought through the above. If you treat the local "backup" as a first-class version of your mail by actually opening it in a client and then altering emails in there, drive could then in theory sync it back with the gmail account just with IMAP. Some account data you'd probably have to specify is a read-only backup and not as read/write. For instance, exporting your Reader data gives you a whole json format export, as does exporting your g+ data, and I'm sure other products as well. I'd imagine it wouldn't be worth the extra engineering effort (and possibly a recipe for disaster) to support random changes to that json being synced back up to the cloud (if it was even data you had permissions to change in the first place...for instance, if you edited the text of a post you commented on, but it wasn't your post). You could probably get around those by just explicitly labeling the subfolders as "Google+ backup" or something, so there's no expectation of changes there being synced back to your account. Should it overwrite any changes you made locally next time it syncs, though? Luckily I don't have to figure those things out. Still a good idea though :)