Massive email boxess
-
I definitely understand how they came to be here - doesn't mean it's right.
80% of my users have been limited to 300 megs - yeah I'm pretty much a tyrant on this. But the reality is that they don't use it except for cat pictures and other non work related junk, so those users don't need to keep any email.
Management and a few others have more reasonable limits, 1 GB. -
@JaredBusch said:
@scottalanmiller said:
Office 365.... Dont use PSTs, keep it all in Exchange. 50GB is the starter mailbox size before you add archiving.
50GB isn't so big today.
Some of these people need to be sued and have a discovery notice sent to them to help encourage them to delete old crap in the future. I know Office 365 allows it, but sheesh, that is a LOT of email.
Having worked in several environments that generate thousands and tens of thousands of emails to each person per day and require that email conversations be able to be recalled for easily a decade or more, it's easier to have happen than you think.
-
Thousands, to tens of thousands? If that's real (and I know it is - log servers anyone) what's the point? no one can honestly go though thousands - tens of thousands of emails a day, and get any other work done - there's just not enough time in the day! Assuming an eight hour day, that's 28800 seconds in that work day - if they spent just 1 second on each email, at 10,000 messages they'd blow nearly their entire day just looking at the emails, not counting acting on any of them.
It's crap like this why I've heard of some companies doing away with internal email altogether. I'm not sure why but I think a hosted (and saved) chat server would be more appropriate than email.
-
I have various log files e-mailed to me constantly and I've created Outlook rules to process those logs. For example, if a certain log file contains the word 'failed' in the e-mail body then the e-mail will appear in my Inbox, but if it contains the word 'success' it will be moved to a subfolder and marked as read. So I only really see log files that I need to see.
Basically, I've found Outlook rules a really quick and simple way of processing text, and that's why I use e-mail for so many of my automated tasks.
-
@Dashrender said:
Thousands, to tens of thousands? If that's real (and I know it is - log servers anyone) what's the point? no one can honestly go though thousands - tens of thousands of emails a day, and get any other work done - there's just not enough time in the day! Assuming an eight hour day, that's 28800 seconds in that work day - if they spent just 1 second on each email, at 10,000 messages they'd blow nearly their entire day just looking at the emails, not counting acting on any of them.
It's crap like this why I've heard of some companies doing away with internal email altogether. I'm not sure why but I think a hosted (and saved) chat server would be more appropriate than email.
Email and chats are not the same. I think email is better suited most of the time.
Big companies tend to send a lot of email and require it be kept to recreate conversations. You learn to filter. Is it ideal? Of course not. But in the real world email is heavily used and lots of people have to archive it.
-
@Carnival-Boy said:
I have various log files e-mailed to me constantly and I've created Outlook rules to process those logs. For example, if a certain log file contains the word 'failed' in the e-mail body then the e-mail will appear in my Inbox, but if it contains the word 'success' it will be moved to a subfolder and marked as read. So I only really see log files that I need to see.
Basically, I've found Outlook rules a really quick and simple way of processing text, and that's why I use e-mail for so many of my automated tasks.
I do that too. Tons if rules keeps my inbox pretty clear.
-
Sure, but why keep the log files form the successes in email at all? Presumably you could have a Syslog server that has all the logs on it.
You could change your rule to delete the logs that are only success, and keep the failed ones in your inbox for review.
In an environment where there are thousands, tens of thousands, plus, emails coming in.. why don't you have a dedicated person looking at those - well maybe you do? or do they really need to be emails, and instead you have some sort of console in a NOC that's watching for errors that the console should be flagging you for.
But we've kinda gone off topic.
-
@Dashrender said:
Sure, but why keep the log files form the successes in email at all? Presumably you could have a Syslog server that has all the logs on it.
You could change your rule to delete the logs that are only success, and keep the failed ones in your inbox for review.
In an environment where there are thousands, tens of thousands, plus, emails coming in.. why don't you have a dedicated person looking at those - well maybe you do? or do they really need to be emails, and instead you have some sort of console in a NOC that's watching for errors that the console should be flagging you for.
But we've kinda gone off topic.
That's based on the assumption that you control the log source. What if email is all you get.
Email because of loose coupling is often the interface of choice.
-
what do you mean by loose coupling?
For those devices that don't have another option - just ug!
-
@JaredBusch said:
@scottalanmiller said:
Office 365.... Dont use PSTs, keep it all in Exchange. 50GB is the starter mailbox size before you add archiving.
50GB isn't so big today.
Some of these people need to be sued and have a discovery notice sent to them to help encourage them to delete old crap in the future. I know Office 365 allows it, but sheesh, that is a LOT of email.
Some regulations require that companies keep every email for x number of years. This is where services like Mimecast come into play. They can enforce retention yet allow users to purge their mail as desired/needed.
-
@Dashrender said:
what do you mean by loose coupling?
For those devices that don't have another option - just ug!
Not tightly integrated. Often needed when you don't have full control if all systems involved or have to interface with outside companies.
Like why ticketing systems use email as an API.
-
@scottalanmiller
OK thanks.
