Slashdot Mirror


You've Got Mail -- Tons Of It

Daniel Goldman writes "The Baltimore Sun has an article about the City of Baltimore's email problem." A snippet: "Millions of old e-mail messages are clogging Baltimore's municipal computers, so the city is going to start automatically deleting any messages older than 90 days. A common practice in private business, the move raises questions when made by a municipality, which has a responsibility to retain certain public records." Goldman points out "Just think about all the potential law suits; 'if it's not there, they can't subpoena it.'"

69 of 249 comments (clear)

  1. Simple... by Anonymous Coward · · Score: 5, Funny

    Outsource each employees email to GMail. Problem solved.

    1. Re:Simple... by hype7 · · Score: 3, Funny
      Outsource each employees email to GMail. Problem solved.


      yeah, and if the budget's looking a bit bad for that year, they could always put a few of the email accounts up on ebay.

      -- james
    2. Re:Simple... by Simon+Lyngshede · · Score: 3, Insightful

      Gmail wouldn't solve problems like this, they only offer one 1GB. I work with secretaries who would use up 1GB of storage a year if they didn't delete any emails. The organisation I do systems administration for isn't even that big, so I could easily imagine that other people running into problems earlier.

    3. Re:Simple... by stilwebm · · Score: 2, Funny

      Yes, but people don't send one page, 100KB Word Documents as attachements to the Evolution mailing list. Secretaries do.

    4. Re:Simple... by BasilBrush · · Score: 3, Insightful

      That's fine. Disk storage is cheap. Certainly cheaper than paying hundreds of staff for the time taken to go through all their old mail sorting the wheat from the chaff. The right solution to running out of disk space for email is to add more disks.

    5. Re:Simple... by Lord+Apathy · · Score: 3, Funny

      I can beat that. A few years ago this bitch at work clogged up the mail system with a 50 mb zip file containing pictures from the corp. picnic. She sent it to every employee in the company.

      Stupid bitch

      --

      Supporting World Peace Through Nuclear Pacification

    6. Re:Simple... by Doppler00 · · Score: 2, Insightful

      How to save 90% of disk space:

      Sort all users e-mail recieved by size for a given year.

      Delete 5% of the largest e-mails. These will probably account for around 90% of all disk usage. They probably represent file attachments which should have been stored on a server instead of in an e-mail account anyway.

      Just think, when you mail a 2MB attachment to 3,000 people in a division, that could use quite a bit of disk space.

    7. Re:Simple... by devilspgd · · Score: 4, Insightful

      With a properly designed mail system, only one copy of the message would be stored on disk, with pointers from each mailbox to the single central copy.

      *shrugs*

      --
      Give a man a fish, he'll eat for a day, but teach a man to phish...
  2. Beowulf cluster by b0lt · · Score: 2, Insightful

    This might be a practical use of one, determine which emails are valid, and which aren't, like a spam filter. Allow users to flag 25% or so emails as important, and archive those.

    --
    got sig?
  3. Just load them into Google or the Archive by Animats · · Score: 2, Funny

    Either Google or the Internet Archive would be happy to archive that data for the City of Baltimore and keep it available for public reference.

  4. Bayesian Filter to Identify Officail Mail by Dave419 · · Score: 5, Interesting

    Since they need to delete tons of old messages spam included, but want to save official email, why don't they train a Bayesian Filter to sort through and save as much as possible. Since they can't rely on their employees actually saving each message which was official to their hard drives.

    --
    ~ there are 10 types of people in this world, those that can read binary and those that can't
    1. Re:Bayesian Filter to Identify Officail Mail by Kenja · · Score: 5, Insightful

      because even one false positive can get them in trouble?

      --

      "Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
    2. Re:Bayesian Filter to Identify Officail Mail by llamaguy · · Score: 2, Insightful

      You could have a manual meta-check on all the positives to make sure they aren't anything vital. Computers don't make mistakes, they just don't think like we do so sometimes it's necessary to sort through it all.

      --
      HAH! I just wasted a second of your life making you read this, but I wasted a minute of mine thinking it up. DAMN.
    3. Re:Bayesian Filter to Identify Officail Mail by abhisarda · · Score: 2, Insightful

      "because even one false positive can get them in trouble?"

      You should probably go take a class on probability. When you're dealing with millions of email, there are going to be some false positives.
      What's the alternative, hand sort them?
      Yeah, that's a good idea right? But with bayesian filtering, you can do a lot of refining when you're dealing with millions of email.
      And who says that you need to use the same filters for the health dept and the transport dept.

      Jesus christ, there are lots of companies that already do this. Its not like Baltimore's the only city with millions of old email.
      This is not a mars mission, this is judicious use of existing technology- bayesian filters(or whatever fits the profile) and enterprise storage solutions.
      Its better off spending a few hundred thousand(or less) on archiving the mails than spend a million or two on lawyers and court 5 years later defending the decision to delete the data after some citizen sues them for records etc.

    4. Re:Bayesian Filter to Identify Officail Mail by asit+ler · · Score: 3, Interesting

      Won't work. The point of purging the 90+ day old messages is so that noone has to meta-check them for importance. Unless you want to hire a cadre of Trained Monkeys to look at the positives. It'd be a 1-banana job, and would have to pay bargain-basement peanuts.

      --
      This is not the sig you're looking for.
    5. Re:Bayesian Filter to Identify Officail Mail by Raven42rac · · Score: 4, Insightful

      Five points for excellent use of buzzwords. I would say compress messages older than 90 days and save them. The government is not supposed to just willy nilly throw things away. I would invest in more hard drive space to hedge against lawsuits.

      --
      I hate sigs.
  5. Why not... by Izago909 · · Score: 4, Insightful

    figure out what percentage is spam, and sue spammers to recover damages for lost resources.

    1. Re:Why not... by AvantLegion · · Score: 4, Funny
      Maybe just figure out what percentage is spam, and delete that percentage of mail. Ehh, that was probably the right 30% to delete....

  6. so? buy some storage, stick them in there. by Anonymous Coward · · Score: 4, Insightful

    can't they, like, just buy a big hard drive and stuff?

    If the average message is 10kib (10,000 bytes, make the math easier), and compresses down to 3kib (probably even better if you compress a bunch together), then you'd need roughly 30gib to store 10 million of them. Can you even buy hard drives that small any more?

    Add some search index, throw a crappy web interface on it, and call it a day. Never delete an email again!

    1. Re:so? buy some storage, stick them in there. by ThisIsFred · · Score: 3, Insightful
      can't they, like, just buy a big hard drive and stuff?
      Here's the problem with this: The longer the stuff is retained, the more expensive it gets to hold on to it. IT is usually a very low budget priority to government agencies, so it's going to be hard to purchase high-reliabilitly mass storage devices every couple of years. Since the goal is permanent archival, cheap, high-cap ATAPI fixed disks are going to be the last thing you want to store the stuff on. The other issue is that the user of the mailbox has complete control over the contents, so retaining everything is going to be really difficult to do, and accidental deletion will be a very credible alibi.

      There are rumblings about FOI and permanent archival among my Governmental Overlords, so I'm thinking hard about potential solutions to the problem. Trust me, it's very complicated issue, more so than I care to illustrate here (especially considering my habit of rambling on).

      The simplest solution is responsibility. If it's official policy, it's on dead-trees and filed away.
      --
      Fred

      "A fool and his freedom are soon parted"
      -RMS
    2. Re:so? buy some storage, stick them in there. by name773 · · Score: 2, Interesting

      what about cds as archival media?
      something about breaking down, but is that real?

      then there's dvds and magneto-optical (my personal favourite)

    3. Re:so? buy some storage, stick them in there. by wired_parrot · · Score: 3, Insightful

      The problem is, the average e-mail is not necessarily 10kb. While HTML can be part of the problem by making e-mails several times bigger than need be, my experience is that large attachments are generally the biggest culprits. A 20Mb powerpoint presentation sent by pointy-haired manager to all his minions can easily swamp the system. And trust me, there are plenty of clueless managers out there sending out Very Large Attachments. I've received 50Mb Excel spreadsheet once, which contained nothing but a single image of a chart scanned at a ridiculously high resolution. It's crap like this that swamps mail servers, not the two paragraph responses.

  7. IMHO this sounds perfectly reasonable by Richard_L_James · · Score: 5, Insightful
    You wouldn't expect a public office to hang onto every piece of paper, so why should they be expected to hang onto every email they have ever received?

    There are always going to be things like replies to an original question and subsequent follow up questions going back and forth, so normally hanging onto the latest/final reply would be sufficient (providing it had the previous history - clearly showed the conclusion).

    Now if they were to use this as an excuse to accidently lose records that would be a different matter. This however is where auditors should be playing a role to ensure that they are keeping the right records and discarding the rubbish.

  8. incremental backup by Anonymous Coward · · Score: 5, Insightful

    "Baltimore officials, who approved the new e-mail policy at a Board of Estimates meeting last month, say they have no choice but to delete old messages, which are slowing city computers to a crawl. They say the system is so overburdened that creating a daily backup has become impossible; there is so much data that it takes more than 24 hours to copy it."

    What?!? What's wrong with an incremental backup? Surely all those millions of messages aren't *changing* every day?!?

    Think of all the children that will suffer from this!!!

    1. Re:incremental backup by Piquan · · Score: 3, Insightful

      What?!? What's wrong with an incremental backup? Surely all those millions of messages aren't *changing* every day?!?

      That depends on how their email system works. If it stores each user in a single file, then that file is changing every day. If they're using a file-based backup system...

    2. Re:incremental backup by HermanAB · · Score: 2, Insightful

      Sure, but saving the user's copies of the e-mail is friggen retarded. It is much easier to store the incoming and outgoing streams of e-mail on the server and use logrotate to create a new file every week, or every day even. As soon logrotate moves a file to backup, it won't change anymore - ever.
      With Postfix, use always_bcc to forward all outgoing mail to a user called outlog, then use procmail to save all outgoing mail to a log file.
      Likewise, procmail can save all incoming mail - after the crap filters - to an incoming log file called inlog.
      Finally, use logrotate to archive the logs periodically.
      Then you don't have to worry about the users and they can do with their copies of the mail whatever they damnwell please.

      --
      Oh well, what the hell...
    3. Re:incremental backup by surprise_audit · · Score: 2, Funny

      Just print the damn things out and file them. Anyone who wants to subpoena them had better have a fleet of trucks and hundreds of spare staff...

  9. Blame On-Line Storage by buelba · · Score: 5, Interesting

    There are two technical culprits here:

    1. On-line storage. There's no reason to keep all of everyone's mail on-line on the server (a la IMAP or proprietary MS Exchange) instead of offline on their PC's (a la POP, most often seen with Eudora for non-techies). With offline storage, the servers don't clog, and you can keep as much mail as you like.

    The biggest rap agains off-line storage is that you can't control what people do with their mail or how they store it. My old job had a neat solution for this: Eudora downloaded your mail, but stored it on a file server. Each employee had 100 GB or something very large. It worked great; the SMTP/POP servers were never full, and everyone could keep their email.

    2. Ridiculous stupid bullshit HTML rich-text mail crap. Can you tell I have a bias here? Aside from being annoying, HTML mail can take up to ten times the size of plain old text. Some of the HTML generated by common email programs is just terrible; filled with repeating tags for every line, and just wasting an incredible amount of space for absolutely zero benefit. (Outlook is bad, but there are others that are just as bad.)

    There's no excuse for not fixing these problems. Someday someone's going to tell a court they had to delete mail for these reasons, and someone else is going to explain exactly why they're wrong. Until then, people who want to delete mail for legal reasons will hide behind false technical reasons.

    1. Re:Blame On-Line Storage by Anonymous Coward · · Score: 4, Informative

      1. On-line storage.
      Actually, storing the messages on local computers in an organization is about the worst thing to do. Most/all user computers are not backed up the way the servers are.

      For legal requirements for some organizations, various backups must be maintained. Just because the active mailstore does not maintain messages older then X days in it does not mean that the data is lost forever (and thus, subpoena-able).

      To do this right, first, the City needs to create a policy that establishes that active e-mail messages will not be retained in the "inboxes" more than 30 days. They should also set up mailstores for everyone in a different area on the same or different server (but NOT to user PCs. they need to define a policy against this, also, because user computers can be subpoenae'd, so if a user has been retaining e-mail messages on their own computer, this could undermine the overriding policy, aka "Smoking Gun").

      HTML/Rich-text e-mail messages
      No argument there!

      It is LEGAL to not retain e-mail messages past a reasonable amount of time as long as there is an organization-wide POLICY in place and reasonably applied over the entire organization, but the policy has to be in place first.

      There is lots of information on the net about this already. I would maybe google for "email retention policy"...

    2. Re:Blame On-Line Storage by vladj · · Score: 2

      Eudora downloaded your mail, but stored it on a file server. Each employee had 100 GB or something very large. It worked great; the SMTP/POP servers were never full, and everyone could keep their email. Why couldn't you have a 100GB account for each employee on the mail server instead? - what is the bloody point to get mail from one network server and move it to another one?

    3. Re:Blame On-Line Storage by buelba · · Score: 2

      Why couldn't you have a 100GB account for each employee on the mail server instead? - what is the bloody point to get mail from one network server and move it to another one?

      Lots of reasons. First, mail servers just don't work very well when storing large quantities of mail for large quantities of people. I've never seen one that works well. If I'm wrong, please tell me. Second, the file server model is much more flexible: you can spread the accounts out across lots of file servers, but still have one email server for foo.com or whatever. I'd rather be able to store everything on one email server and have everyone have quick access to it, but I've never seen a solution that works.

    4. Re:Blame On-Line Storage by imroy · · Score: 2, Informative

      Check out project Cyrus. I haven't used it for large projects, but I notice it does support distributing mailboxes across multiple backend servers (The Murder stuff).

    5. Re:Blame On-Line Storage by vladj · · Score: 2, Informative

      Try CommunigatePro: it's not open source but extremely reliable and flexible and can handle huge volumes of mail, and can do clustering over multiple servers too. I've had experience with it on couple of large-scale installations, 50K accounts+ with millions of msgs per day.

  10. wrong approach by yppiz · · Score: 5, Insightful

    This has to be the stupidest approach to the problem. Their networks are too slow, so instead, they're going to have each employee go through their old email and save individually important messages to their local hard disk? Not only are they going to tie up employees with this manual effort, they're also going to lose key documents and a key service - the ability to centrally search and reply to requests for information. In the future, each department will have to search their local hard drives for this information.

    They've taken a simple problem of old or improperly speced equipment and turned it into a manual labor solution instead. That's an insane waste of time and salary. They should just upgrade their network and storage. If I can build a 4 terabyte RAIDed PC for a few thousand dollars, they can centralize their mailserver and back it up for say a hundred thousand, even with extra redundancy and inefficiencies and admin costs.

    By contrast, forcing every current employee to perform a task that would eat up weeks of time per employee per year, in a city of Baltimore's size, will cost tens of millions of dollars.

    Dumb, dumb, dumb.

    --Pat / zippy@cs.brandeis.edu

  11. Re:Great way to ignore your customers by ePhil_One · · Score: 2

    If they haven't read it in 90 days, they've already ignored it.

    --
    You are in a maze of twisted little posts, all alike.
  12. Temporary Fix by Rie+Beam · · Score: 5, Insightful

    Backup all e-mails from the last 4½ years into permanent storage, and then from there, get organized. Put spam filters on, force people to sort any important mail or else it gets deleted after, say, two weeks. People always seem to want to "start from scratch". without looking at the situation rationally. Five years of documents, gone overnight. How can anyone not be at least outraged by that?

  13. Old e-mail - it's a resource by Anonymous Coward · · Score: 2, Funny

    I'm posting anonymously because this may risk my relationship with my employer.

    We see old e-mails as a resource to be harnessed and turned into profit. Thanks to old e-mails we can ensure that no employee leaves with a spotless record since everyone always e-mails something incriminating sooner or later from the company e-mail address.

    We also find that the e-mails are great for data repositories; we fill all of our databases with text and when our clients come in, we tell them that those data warehouses contain terabytes of information.

  14. Millons of old spam, most likely. by jafo · · Score: 5, Interesting

    The spam problem is unlikely to go away until people start treating it like the attack on the Internet that it is.

    I've noticed an annoying trend lately that e-mail sent to businesses is frequently getting just ignored. Certainly it seems much more frequent this year than in the past. I've wondered if this is simply because so many e-mail boxes are getting filled up as fast as the spammers can send.

    I'd suspect that the city of Baltimore wouldn't be having any problems if spam weren't such a problem. If the number of messages they had to deal with dropped by 5 to 20 times (depending on which estimates of current spam levels you believe), they could probably just leave the mail where it is.

    This is all something I've been struggling with, being a small business owner doing business on the net. My company of 5 people gets between 4,000 and 20,000 borderline spams per day. By borderline, I mean that we throw away obvious viruses and things which score above a certain score in SpamAssasin (I think it's 9). So, that doesn't count the super spammy messages.

    If it weren't for our fairly strict and complicated spam blocker setup, and a very powerful machine, we couldn't get the few hundred messages per day that are of interest to us. Spam is killing e-mail. I'm not sure why more people aren't treating it as an attack, but it's really hard to get anyone's interest to take some action. Canceling accounts doesn't even begin to solve the problem.

    In the mean time, the City of Baltimore is suffering...

    Sean

    1. Re:Millons of old spam, most likely. by Tony+Hoyle · · Score: 2, Insightful

      Spam is easily recognized by the subject line? Boy I wish I was getting your spam instead of mine!

      Mine's full of:

      hi
      how are you?
      Please Complete and Return
      I miss you
      Fwd: I need your help
      Re: Your Account

      etc... etc...

      Any one of these could be legitimate (occasionally you get a headline that's so inocuous I think the spam filter has got it wrong... until I actually read the email).

  15. Dude, you'd think they would have the sense... by DAQ42 · · Score: 2, Interesting

    to dump it off to tape and then just store the tapes instead of just deleting it. Though they are probably running an Exchange server so offloading data stores wouldn't be the easiest thing to do. If they were using something with a simple mbox store, they could easily just parse it through a date filter and dump the older than 90 day stuff to tape. At least then it could be retrieved at a later date.

    Oh, wait, let me guess, they aren't using tape backups...

    --
    Don't Ask Questions. I don't know the answers and even if I did I wouldn't tell you.
  16. Deleting older than 90 days common? by swb · · Score: 3, Interesting

    OMFG, we nearly had a lynch mob attack us when we began deleting mail older than *two years* -- it eventually took the intervention of the CFO and a faked mail system "crash" to make 2-year max retention work, and even then there are people still pissed about it, or who claim that "the client" requires them to retain all correspondence (nope, sorry, we checked the contract).

    90 days seems both unrealistic to implement and way too much reliance on .PST files, which often max out at 2 gig and can get corrupted way too easily, not to mention being fdisked into eternity by clueless helpdesk people.

  17. Some gov't org do this on purpose by Anonymous Coward · · Score: 2, Interesting
    Where I work, which is government, we only keep backups for about a week, since they are public records.

    We don't want someone to be able to request something from backups that the user thinks is gone.

    This way it's up to the user to decide if they want their data archived. And the onus is on the user to comply with however long the data is supposed to be kept before being destroyed.

  18. Problem with email by sydbarrett74 · · Score: 2, Insightful

    This highlights a fundamental problem with email -- many people pass documents as attachments, or in the body of the email, instead of using email as a sort of metadata describing their works in progress. Documents shouldn't be passed around in email; they should be stored on a network share, where proper controls for mutual exclusion and such can be employed.

    --
    'He who has to break a thing to find out what it is, has left the path of wisdom.' -- Gandalf to Saruman
  19. Email == offical documents ? by drgonzo59 · · Score: 2, Insightful

    I am not sure if they can use email as official communication? There would be problems with repudiation ("we never received it"), privacy ("someone intercepted it who was not supposed to") and authentication ("it wasn't me who sent it, it was my dog"). Can they use an email in the court then? What would have to be done is to have all the messages signed and encrypted with a public key, and perhaps have some way for the sender to get a receipt back when reciever reads the message.

  20. Re:Client-side storage is not a good solution by Donny+Smith · · Score: 4, Insightful

    >A better idea would be to write a script to go through each user's mailboxes every month, export any old emails to text, store the files on a server that uses a journaling filesystem, index the emails, and compress them.

    No file system will save you from multiple HDD failures; they should save old (>12 months) data to DVD burners and/or tapes or cheap SATA storage. One can buy 1TB of external SATA space for couple thousand dollars.

    >One or two XServe G5s could do the trick quite well.

    What do XServe boxes have to do with generic application like email? Besides, they're more expensive than comparable Intel+Linux servers (especially considering the fact that CPU perormance is unimportant for most mail servers).

  21. Try 30 days by Anonymous Coward · · Score: 2, Informative

    Though I don't work in the auditors office in my state, here is what they implemented. Any document (digital or not) over 30 days must be made public. Solution, any e-mail over 30 days is deleted. It allows them to not worry about keeping all e-mail till the end-of-time and not worry about making e-mail public. Great solution in that scenario.

  22. Did they even Look for offline soultions? by Ohm2k · · Score: 5, Informative

    Working at a law firm we have to keep everything for 7 years. We have a system in place that takes all mail over 90 days old pulls it out of exchange and move it to the SAN. As a plus it puts a link back into the information store to make it look like the message is still there. User wants a Old message he can still get it himself w/o a IT person having to do dig up a tame, restore the file and the e-mailing it to him (Thus creating MORE mail). The messages are still searchable and it makes retrival when needed a snap.

    Mind you, we are only a 700 user shop. But nothing gets deleted. If it gets buy the spam filter it gets saved.

    --
    People find it strange that I don't know how to juggle or tap dance.
  23. This issue isn't limited to the City of Baltimore by Flounder · · Score: 4, Interesting
    I work in the IT department of a county close to Baltimore. Our server can retain e-mail indefinitely (there is a space limit per mailbox, but not a time limit). However, our backups only go back 30 days. This is stipulated by the county lawyers.

    As far as I've been able to figure out, this arose from a lawsuit against the county where an e-mail retrived from two years previous proved a county commissioner to be taking bribes in a zoning issue.

    Rather than fix the corruption, just ensure that it's covered up more efficiently. Gotta love local governments.

    --

    No boom today. Boom tomorrow. There's always a boom tomorrow. - Cmdr. Susan Ivanova

  24. A mark or procedure for official business by jhines · · Score: 4, Insightful

    Once an actual human person has read and acted on the mail, they should be able to mark it "official business" and/or move the email into an "official business" folder which does get kept as required.

    Better procedures and training goes a long way here. These same folks have no problems with snail mail.

  25. Re:Great way to ignore your customers by No.+24601 · · Score: 4, Insightful
    If they haven't read it in 90 days, they've already ignored it.

    I don't know what business you work in, but if they haven't read it in 3 days, they've lost my business.

  26. Why is there a problem with retention? by phr1 · · Score: 2, Interesting

    Just dump the old email to DVD-R and archive it somewhere. If someone wants to subpoena it, burn off copies and wish 'em luck. Even if the city is getting a million pieces of spam a day, at 5kb each after data compression, that's just one DVD-R per day at a buck or so each, peanuts compared to what the city already must spend xeroxing memos for records retention purposes.

  27. Removing old messages isn't the best option by crimoid · · Score: 5, Insightful

    A better option would be to archive old messages rather than remove them entirely. From the article it sounds like they are keeping ALL messages active all the time. For example:

    "They say the system is so overburdened that creating a daily backup has become impossible; there is so much data that it takes more than 24 hours to copy it."

    So, it seems like the solution would be to periodically lop off old messages to offline storage (tape, spare drives, whatever). In the event of a lawsuit the old messages could be reasonably recovered and the cost for such a system would be extremely minimal.

  28. Complying with Public Records Acts by EconomyGuy · · Score: 4, Insightful

    Unlike a legal office where communications are governed by extensive regulation, governments are really only required to keep records of official documents and decisions. The myriad of e-mails leading up to a decision are not generally protected under such an act, nor are snail mail or phone conversations. In fact, the whole idea of there being a digital trail to follow for governmental decision making is really very new. Does it makes sense to change that practice? Do we really think our government officials should be so closely watched that EVERY e-mail/phone conversation/smoke signal should be recorded and exposed to public scrutiny? Talk about making an unattractive job even less inticing.

    In responce to the posters question about all those subpoenas: welcome to the world of civil litigation, where the first one to destroy the evidence wins!

    --
    Only 120 characters... who can summarize their entire world understanding in 120 characters?!
    1. Re:Complying with Public Records Acts by gerardrj · · Score: 2, Insightful

      Yes. When a government official is supposed to be acting in the best interest of the people they should be subject to scrutiny at any level that is reasonably available.
      Storing older emails is a rather trivial issue of collecting, compressing and copying to an inexpensive tape or hard drive which can be archived. A 250GB IDE drive is quite inexpensive and could probably archive several hundred million emails, many more than the city is claiming it will delete.

      In a time when the government is fading further from the ideal of a democracy, or even the republic which it's supposed to be, I think that accountability of the elected and non-elected government workers is critical.

      In this particular case, it seems that all of the city's email is in one central location, otherwise how could they just delete it without putting that responsibility in the hands of users, or sending support people to each and every desk.

      Pick a day, halt all email access inbound and outbound (government usually doesn't work on Sunday), copy all the existing email to a drive, then start the deleting process.

      --
      Article X: The powers not delegated... by the Constitution...are reserved...to the people
  29. Re:HTML in email? Forbidden! by Hatta · · Score: 4, Insightful

    I'll handle these in reverse order.

    Word attachments are acceptable when they are just a means of moving files around, and not the entire content of the email. What is not acceptable is expecting me to load a large word processor just so you can use the company letterhead. In my experience the latter type is far more common. Besides the security implications (macro viruses, etc), I do not have a gui on the computer I read my email. Nor should I need one.

    As for HTML email, I'm simply not going to render strange IMG tags. They could lead to goatse, or back to a spammer's site, and now they know my email is active. HTML email generally looks like it was designed by an 8 year old with downs syndrome anyway. Plain text is just more readable for nearly every email. Check out HTML email is STILL evil!!! for more.

    --
    Give me Classic Slashdot or give me death!
  30. Re:That's what a personal folder is for... by jwcorder · · Score: 2, Interesting
    A personal folder isn't just for "personal" messages. I am talking about a Personal Folder. As in a *.pst file. As in a place, where you can store messages in an archived format in a file that Outlook treats like that file cabinet that can be saved locally on hard disk and backed up to the server at the end users leisure.

    Any of these so called "important governement documents" shouldn't be stores in an email archive anyway. They should be on a network drive getting backed up.

    My point is that a better solution is to put the email storage in the end user's hands. Set file size limits on their accounts and have them move all important mail off of their server mailbox and into a Microsoft PST file...aka Personal folder.

    I work for Fortune 50 company, running in an exchange environment and this is the method we use for about 4000 corporate employees. They have 10 MB mailbox limitations that will not allow them to send any email when their account reaches 10 MB. We then shut the accounts off when they reach 50 MB and kick messages back to the sender.

    Users who have important email setup Personal folders in Outlook and move messages from their inbox to their PST file. This file is stored locally on laptops (for travel purposes) and on the user's network home drive for desktop PCs.

    We run standard incremental backups daily and full backups once a week. The only problem we have with this is that MS's PST files have a 1 gb limitation before they get corrupt so some of the legal and credit employees have three or four personal folders normally sorted by year. So you would have one file for 2004, one for 2003, etc etc. Works for us, has to work for the government.

    --
    http://jayceecorder.blogspot.com
  31. Saving to local drives? by Gonoff · · Score: 4, Informative

    We have to spend a lot of time telling people to **NOT** save to local drives. If it is important or confidential, or may be in the future, this should not be saved locally unless you want to loose it or explain to an enquiry why it was found on sale in a car boot sale after a break in. This is what a network is for.

    The answer to the problem in the article is quotas. *nix has them, Novell has them and even Windows has them. Our email quota works as follows
    Limit 1 - email user once per day marked high importance that they are getting close.
    Limit 2 - disable sending and continue with (2k) warning message.
    Limit 3 - disable receiving apart from one final message saying that it would all start working again when the user clears some space

    When they can't send/receive, they get a dialogue box reminding them when they try and when they can't receive, the sender gets a messge.

    This does make for support calls like...

    "Why does my computer tell me that the email is full up and I can't send any more?"
    "Because your email is full up. You have a message explaining this to you."

    "X tried to send me an email and it bounced saying that my mailbox was full up. Why?"
    "Because your mailbox is full up."

    --
    I'll see your Constitution and raise you a Queen.
    1. Re:Saving to local drives? by Grell · · Score: 3, Informative

      3 warnings?

      Must be nice.

      I field 250-320 emails a week.

      All replys are "reply with history" often with screenshots as company policy and due to the complexity of the job. (3rd level insurance support w/ story problems galore)

      I have a personal storage quota of 75 megs,
      the mailbox I save to has a personal storage quota
      of 75 megs. (personal space? about 7% and holding, corporate box? 90-100% at all times)

      They cannot share, or transfer any storage quota from one user or resource to another.

      They will not buy *any* new drive space.

      They will not examine *any* redistribution of present drive shares. (like oh I dunno, *USAGE*)

      And the first warning we get that the drive is
      filling (about 3-4X a week) is the cannot write to
      drive warning.

      We delete somewhere in the neighborhood of 90 megs a week of pontentially subpeonable documentation and there is no plans in place, or even spoken of
      to correct this. (don't ask, don't tell)

      Save it to a local drive? No that would violate security protocols.

      Grell

      --
      ...when it gets down to fundamentals, do what you have to do and shed no tears. Dr. Matson in Tunnel in the Sky
  32. Re:And there are no privacy concerns? by innocent_white_lamb · · Score: 3, Funny

    The question comes -- should all of it be public?

    They are public records. So, yes it should all be public.

    Simple, no?

    --
    If you're a zombie and you know it, bite your friend!
  33. Information Lifecycle Management by bolix · · Score: 4, Insightful

    ILM is the next big thing. Its the logical extension to the ever increasing SAN/NAS Server/Workstation exponentially-increasing-data problem (go google for pretenders to the law).

    You can't oversee growing data storage without a parallel increase in administration costs. Instead, the idea is to build automatic archiving into your storage architecture.

    In practice this means you build tiers of storage/archive methods. Tier 1 is a high tkt Shark SAN etc, Tier 2 is lower priced SATA RAID and Tier 3 is a DAS Tape Library. Build retention guidelines into the storage management playform (Tivoli etc). Older items are automatically moved to the Tier corresponding to that retention/access policy. Really old items "live" on Tape. Frequently accessed data lives on the high speed boxes near to the users/application. You snapshot updates to a DR replica offsite or burn periodic Tape sets etc. Its a good idea to team this with storage virtualization (virtual LUNS/ Metadata directory servers) and you can add/rotate/modify the storage tiers when necessary without any downtime.

    From a user perspective, you click on the link and if applicable, get notified the item is being retrieved from media x (its mostly transparent). Worse case - access times are in the minutes.

    Of course, all this comes with a high price. Enterprise Storage systems are not cheap. Recent legislated policy (Sarbanes Oxley etc) enforces the retention of some media (e.g. email). You cannot rely on end users to enforce data retention. This lets you mandate tiers of protection and is highly configurable to support per application monitoring.

    Nothing is foolproof. Its still being finessed but if you can afford it - its truly a thing of beauty.

  34. Re:Simple... (not) by Zen · · Score: 4, Informative

    There comes a point where that, too, gets very expensive. At my company (large US healthcare provider, with governmental and private contracts both HMO and PPO), after saying 3, 5, and 7 years, our lawyers have told us we have to archive all email potentially forever that the end user doesn't specifically delete. They may do an end-run around the deletion and archive those, too, but I don't know. Anyway, our email system (Lotus Notes, which is an extreme HOG) eats somewhere between 100GB - 1TB/week. I was told it was well over 1TB, but I don't believe them. This is of course due to older Notes versions inability to store attachments in public directories and simply sending a copy to each and every recipient (and the stupidity of no size limits on internal email). There is a point to how many drives you can add to a SAN, and then you have to get a whole extra chassis, which is where the expensive part comes in. To keep buying new SAN units every 6 months or so, as well as the harddrives to put in them (plus the maintenance contracts, 24/7 support, etc) could easily add up to $1million/year or more. Which is definitely more costly than 10 average low-mid level administrator's salaries.

  35. Re:Simple... (not) by BasilBrush · · Score: 2, Insightful

    The 10 secretaries in question were only using 1 GB each per year. 10GB per year in total. If your company is as large as you imply, the amount of work hours involved in sorting though old emails will be larger than that. Each person (or their PA) would need to do their own. That's a lot of hours.

  36. Screw the Lawyers by Detritus · · Score: 3, Interesting

    At one company that I worked for, they got the brilliant idea to delete all email older than 30 days. They also didn't want employees to make backups of their personal mailboxes. They intentionally wanted all traces of old email to disappear. While I'm sure that it made the lawyers happy, it caused a lot of grief for the people actually doing work for the customer. Many design decisions, bug reports and other important things were only documented in email messages. This is supposed to be the age of the paperless office, right? When you are involved in a multi-year project, you often need to refer to old messages. It also had the effect of making old policy memos disappear, whose existence had proved to be very inconvenient to management on several notable occasions.

    --
    Mea navis aericumbens anguillis abundat
    1. Re:Screw the Lawyers by geekoid · · Score: 2, Interesting

      I worked at a company with that policy.
      Then one day, in a meeting with VP's, a manager tried to put me on the spot, and use me as a scapegoat with some bold face lies.
      I'll never forget the look on his face when I produced hard copies of our email exchange...
      ahh, memories.
      I also got the VP to change the email policy.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  37. Outsourcing garbage collection... by mikael · · Score: 3, Funny

    When I heard my city were outsourcing their garbage collection services, I imagined office blocks of staff in India sifting through online hex editors looking for spare memory blocks to delete.

    --
    Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
  38. Re:Simple... (not) by Zen · · Score: 3, Interesting

    Right. Our company originally tried to instate size limits when we went to Notes (only 3 years ago), but then the lawyers said we need to keep everything anyway (HIPAA requirements). So even with the exorbitant expense of the system, it is probably still cheaper to keep expanding every couple months rather than pay people to sit there and sort through their own email. Anything from an external party must be kept, and anything remotely regarding a customer must be kept as well. It's a huge pain, and they took the easy way out by archiving every single email. But neither option is very cost effective. There are four people that I know of in my department alone that have email boxes (extensively categorized with dozens or up to hundreds of folders) with up to 20GB each. It's crazy. But even without the ever looming threat of a lawsuit, they claim that they have been able to disprove what other people were badmouthing them about by being able to produce an email from that person stating the exact opposite a year or two previously. I've witnessed it once, and it is pretty funny watching somebody turn beet red in a room with 25 supervisor's and above.

  39. I work for a government office... by Anonymous Coward · · Score: 2, Interesting

    Probably too late in the thread for this to catch much attention...

    However, I work for a local Government office, close to Charlotte, NC. It is our stated policy to remove all e-mail older than two weeks except for e-mail that is crucial to job performance. This is less to save space then it is to keep the news media from finding dirt. We really don't care that our e-mail is public record. We really have nothing to hide. However, the local newspaper (in Charlotte) is constantly asking for _ALL_ of the County Manager's e-mail. They aren't looking for anything specific, they are just on a fishing trip, trying to see what trouble they can stir up. They rely on the Freedom of Information act to, hopefully, generate some news, instead of doing some real investigative work. *sigh*

    Anonymity enabled for self-protection. Wouldn't want the powers that be see my e-mail...

  40. Re:Great way to ignore your customers by NetGyver · · Score: 2, Insightful

    I hate it when people associate taxpayers + government with customers + business. The two relationships are very different.

    There are no laws I know of that tell me I have to pay Company X for products. If I don't want any products from Company X, I won't buy anything from them. I'm not going to be breaking any laws because of it. However, if I don't pay my taxes I'll get hounded to death with the possibly of being tossed in jail.

    See the difference?

    --
    A Penny for my thoughts? Here's my two cents. I got ripped off!
  41. Re:Great way to ignore your customers by Kjella · · Score: 2, Insightful

    I don't know what business you work in, but if they haven't read it in 3 days, they've lost my business.

    Let me guess.... you're emigrating a lot, yes? Otherwise you might have to have "business" with the government. Good luck getting a reply in three days there.

    Kjella

    --
    Live today, because you never know what tomorrow brings