Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Kevin Wood]

and never be away from your inbox.

I am increasingly unsure that this is actually a good thing!

With a suitable procmail filter it's fine. He says, from the airfield, having given up on work for the day to go flying.

[aaronjb]

  Ah, memories.. I used to run my own mailserver and manage everything locally - these days I just ship everything to gmail. Laziness > data security 

[TheBoy]

The PST file format was never designed for that type of use, and was never designed for that size.  MS have been gradually increasing what its maximum recommendation is, from 20Mb a few years back to I believe 2Gb now. 

"In Outlook 2003 and Outlook 2007, the maximum size of a Unicode pst-file has been limited to 20GB. In Outlook 2010, 2013 and 2016, this limit has been set to 50GB. You can increase (but also decrease) this limit via the Registry or via Group Policies."
https://www.msoutlook.info/question/increase-pst-file-size-limit

also https://support.microsoft.com/en-gb/help/982577/the-file-size-limits-of-.pst-and-.ost-files-are-larger-in-outlook-2010

The maximum sizes are enforced to stop them growing too big, because they will corrupt.

OST's by their nature will be local. PSTs need to be local as well, or moderately sized ones can be on fast local LAN.  PSTs are really not that much refined from the MMF files of Microsoft Mail, and in a former life when I looked after one of the largest MS Mail systems globally, I can assure you, even locally, you could guarantee corruption after about 20Mb.  "Exchange" (as in the client) and "Inbox" (the mail client in consumer Windows 95) also had the same limitations - not a hard limit, but a "if you go over this, you will bugger it" limit.  Incidentally, both Exchange and Inbox would also corrupt an MS Mail Postoffice under similar scenarios. Bless them.

[TheBoy]

As I found, back in the dark ages before I ditched outlook, even putting the PST file on a network drive ends in tears. It really is a product that belongs in the bin these days.

Outlook is fine. As long as you understand what it is. Its an email client for MS Exchange mail servers. Works really well in that scenario.  Completely useless for non MS Exchange servers.

Under MS Exchange, there is no need for PST files (as if you have half an ounce of intelligence, you will have all your mail on the server, not local), so the problem goes away. Completely.

[Kevin Wood]

MS exchange being another thing I wouldn't touch with a barge pole. Got that T shirt.

[TheBoy]

MS exchange being another thing I wouldn't touch with a barge pole. Got that T shirt.

Well, yes, it has a place in life, but ain't for everyone.  And doesn't work too well if you don't use an ActiveSync client like Outlook.  And server side, its a memory hog. A proper memory hog.

But it does have a place in life

[Viral_Jim]

As a user, of a constant 10yrs or so, I have found outlook with M$ Exchange to work very well. TBH the biggest downer of those 10yrs was being moved from blackberry to apple for my personal communication device.

I love my personal iPhone and loved my iPad until I sold it (to buy a stained glass window). But as a tool for email, messaging and telephony, the blackberry was far superior.

[TheBoy]

As a user, of a constant 10yrs or so, I have found outlook with M$ Exchange to work very well. TBH the biggest downer of those 10yrs was being moved from blackberry to apple for my personal communication device.

I love my personal iPhone and loved my iPad until I sold it (to buy a stained glass window). But as a tool for email, messaging and telephony, the blackberry was far superior.

That's weird, as I found opposite, with Gooseberry being cumbersome (yes, we did use BES (unreliable piece of junk)), with crApple being near seamless, except Mail, Calendar, Notes and Tasks all being separate apps on iDevice.

We now have to use Win8/10 phones. Wow, what a step backwards in usability.

[Viral_Jim]

We now have to use Win8/10 phones. Wow, what a step backwards in usability.

Thankfully I've not been subjected to that. I understand it's a real dog egg!

That said I've just installed windows 10 on my new/old laptop and I rather like it. I took against it on my work device but it transpires that that's because whoever chose the default setup and layout made a real pigs ear of it and prevented users from changing it.

[Doctor Gollum]

We now have to use Win8/10 phones. Wow, what a step backwards in usability.

Thankfully I've not been subjected to that. I understand it's a real dog egg!

That said I've just installed windows 10 on my new/old laptop and I rather like it. I took against it on my work device but it transpires that that's because whoever chose the default setup and layout made a real pigs ear of it and prevented users from changing it.

Hell hath no fury like an IT manager scorned

[TheBoy]

We now have to use Win8/10 phones. Wow, what a step backwards in usability.

Thankfully I've not been subjected to that. I understand it's a real dog egg!

That said I've just installed windows 10 on my new/old laptop and I rather like it. I took against it on my work device but it transpires that that's because whoever chose the default setup and layout made a real pigs ear of it and prevented users from changing it.

Desktop Win8 was a great OS with a piss-poor interface.  Win10 is a much better interface, but a not so great underlying OS (particularly last years version).

Windows Phone 8 or 10 is just plain, errr, crap.

[zirk]

have any suppliers cracked the problem of backing up a largish (9GB) outlook pst file to the cloud while it is in use? didn't work with google drive last time i looked

Your struggle uploading a single file that size up to the cloud, it will probably crap out half way through and fail or want to retry from the beginning again.

If its purely for back up purposes, you could try breaking the file size into segments ie, 100mb or so then uploading, that way if it does crap out it will retry from the last failed segment, but bit of a pain as your have to recreate the file size again on download or recovery. Also remember what the Max File Upload size is for each Cloud Account ie, OneDrive is 10GB max.

Another option is to use a File Uploader that breaks the File size then reconstructs it again once in the Cloud, theres a few around but one I would recommend is Zoom Uploader, its Freeware and works really well, works on just about every Cloud Storage out there. Bit of a pain to set up for each Cloud Account but once done does its job perfectly. It also allows Pause Stop and Resumable Uploading, even between PC Reboots which is really handy for Large Files

http://z-o-o-m.eu/  or  http://z-o-o-m.eu/down.htm

Tip with Zoom, once youve set your Cloud Account up, go to Tools/Settings/Connection/HTTP Buffer Size = and set this to the same size or just under your ISP Upload throughput speed (in kB). This will give the fastest upload speed.

ie, Say your ISP upload speed is 5Mb, then 5 divide 8 is 625kB so set the Buffer to 512kB not 1024kB. 

[Strangechap]

Google Drive is excellent. I use that for my work stuff - I pay a couple of quid a month for 100gb. I've used it for years and never had any problems.

I use Crashplan for my archive stuff. It's $60 a year for unlimited storage. I'm currently uploading about 1gb to it.

The way I read google drive info, you have a folder on your desktop, and anything in that folder is synced between google and your machine automatically. Is that correct?

If so then it's just what I'm looking for . But, that being the case, what do you use crashplan for?

Sorry for all the questions. This is all new to me

Sorry, been away a couple of days.

I use Google for my business stuff, I have a 100gb plan. I have a Google drive folder on my HDD, and folders inside that. Used that for a few years, no issues whatsoever.

The crashplan is for my personal stuff, because I have a lot of video and photos which add up to around 1TB. Google is too expensive for that kind of storage, so I went with CrashPlan for that. Hope that clarifies it a bit.