Real News. Real Funny.

Comments

  • No, if you're not smart enough to fix that by now you deserve what you get comin' to ya.
  • No. I use it all the time - it's my default. Work would be much more annoying without it.
  • I use "Reply All" all the time. If you can't figure it out - are you really cut out for office work?

    A few years back I was working for a fairly large company (~4000 employees) and someone got fired for a 'reply-all.' The players were: Jeff (sender), Ken (IT director), and Mark (CEO). The email was this:

    "Ken, I'd suck your dick if Mark's tongue wasn't already in your ass."

    Jeff undoubtedly meant this as some kind of backhanded compliment, but since Mark was on the list, he got fired.
  • IT used to rearrange Outlook so the Reply-All was far away from Reply. To give them that extra half second to think about it. Some still did of course, but at least they had to push that mouse all the way over to do it.
  • Microsoft (MSFT) introduced a plug-in option on its Outlook program called NoReplyAll, which allows senders to prevent recipients from Replying All to their messages.

    I was about to compliment Microsoft. Then I realized they were undoing their own mistake so it doesn't count as a good deed.
  • ZAZ: Microsoft (MSFT) introduced a plug-in option on its Outlook program called NoReplyAll, which allows senders to prevent recipients from Replying All to their messages.

    I was about to compliment Microsoft. Then I realized they were undoing their own mistake so it doesn't count as a good deed.


    You do realize that email clients predate Microsoft Outlook by at least 10 years, and all had a reply-all feature, right? You do realize that? But it was Outlook's mistake for including it.

    How about, it was the modern email user's mistake for misusing the feature.
  • Generation_D

    I was doing

    % repl -cc all

    a decade before Outlook. Extra effort required to use the not-only-to-sender option.
  • You are all replying to everyone. Please stop it hitting reply all with requests to be removed from the mail list.

    /bcc, that is all
  • So, is this the thread where all the geniuses who never make mistakes talk about how dumb people who make mistakes are?
    Yep - it's that thread - again.

    i18.photobucket.comView Full Size
  • Reply all is useful.
    I've never accidentally hit it, but can see how it is easy to do. I view this as an ergonomics issue.

    And to all the haters here saying people deserve to be fired for what amounts to a tiny mistake: you are assholes. The only difference between you and any of the people who have hit reply all is that you have yet to make the mistake, or your errors have luckily occurred in ways that didn't create a problem.

    mistakes: everybody makes them. EVERYBODY.
  • MSFT Exchange environments can deploy Information Rights Management (IRM). When IRM's in use, you can block certain actions on messages you send; prohibit reply all, prohibit forwarding, disable the ability to take screenshots, disable printing, things like that. The rules you set are applied transitively to every copy you send, so if you send to User A with reply-all blocked, and User A forwards to User B, User B still can't reply-all. No plug-ins required, though you do have some back-end work to do if you want to deploy that option.

    It's a handy feature for enterprise orgs. It's also not foolproof, since users have to remember to set options on messages with restricted rights, and because some features (disabling screenshots) are easily defeated (take a picture with your phone; retyping the content into Word; etc).

    Sensitive communications from upper management always came with IRM protection. But past that, most folks used it to block 'reply all' if they were sending to a large distro list. Even if it's a company full of technical people there's always somebody who doesn't understand the prevailing software metaphors.
  • Office Rule #4:

    Do not send the email if you're not comfortable with it being sent to everybody in the company! This isn't just about Reply to All, but message threads that end up being forwarded, or add-ons to message threads, etc. Also, quit using email like a chat protocol. IM is there for a reason. (And that also means you don't start using the corporate IM for vulgar comments, either.)
  • ChubbyTiger: You are all replying to everyone. Please stop it hitting reply all with requests to be removed from the mail list.

    /bcc, that is all


    Don't use Reply All to tell other people to stop using Reply All. It just makes more people use Reply All.

    Don't reply to this.
  • What people really need to learn is when to move some or all other people on the original email chain to the BCC list so they know the issue is being handled and are dropped out of the chain after that. People at my office are usually pretty good about this; although there are sometimes amusing occurrences, usually with new hires.

    However, I wish there was an option to Forward but automatically copy in some or all of the original recipients. People use Reply to All to add people all the time when there are attachments, but only Forward includes the original attachments.
  • SineSwiper: IM is there for a reason. (And that also means you don't start using the corporate IM for vulgar comments, either.)


    Wise advice, since every corporate IM product I know of has back-end logging. Google your software of choice along with the word 'logging', or to go one better, 'compliance'. Quite a few packages use SQL back-ends, others use custom logging based on their server software, but all of them store histories for review.

    IM logging is one of those things that people "don't have time to look at" in the same way they "don't have time to look at" what's going through your routers or proxy servers. Everybody's busy, nobody looks, right? That stuff's still there for review if you run afoul of someone higher up than you. And it pays to remember that even busy techs tend to snoop when they're bored. (Can it get them fired? Yeah. Doesn't stop all of them, though.)

    Don't believe in privacy if you aren't the admin. And if you are, be advised that other folks with rights may have done things you aren't aware of.
  • Pet peeve time.

    And why the fark the minimize and restore down right next to the close window button?

    And why are the save or copy selection so close to the delete selection on so many drop downs? Why would you not put a dead space between them to guard against inadvertent clicking?

    Yes I know, "key-binds" but sometimes you just gotta use the mouse because you are going between several different environments.
  • Wingchild: Information Rights Management

    The description reminds me of the job I had working on Compartmented Mode Workstation software. It was based on Unix but had security classification built in. Everything had a security label. If you tried to cut and paste it would either deny you or change the classification of the destination to match the source.

    It could be defeated the same ways as Exchange. Take a picture (but cameras were bigger in the 1990s). Retype (some people could type fast back then). Hack into the network (these systems required physically secure networks).
  • Dear Everyone:

    The whole reason I love Fark is that every comment is a Reply-All.
  • Hahaha good posts in here. Especially the reply all telling people not to reply all.

    As for the article, sorry, it's your fault. And no it's not that you don't have two brain cells that can rub together to not press reply all, it's that you think offensive joking or non-joking emails are acceptable in a work environment. They aren't. You use your personal email for that if you're that much of a dickbag that you need to attack friend-coworkers.

    It's called professionalism. If you don't have it, you don't deserve a profession.
  • Rising_Zan_Samurai_Gunman: However, I wish there was an option to Forward but automatically copy in some or all of the original recipients. People use Reply to All to add people all the time when there are attachments, but only Forward includes the original attachments.


    Reply All, copy recipient list, close mail. Forward, paste recipient list. Inconvenient but fairly quick.


    Dropping attachments on replies is almost mandatory. Consider an Exchange 2010 example:

    1) You send a message with a 10MB attachment to a list of 20 people.
    - that hits your transport server's queue as a single 10MB message, then bifurcates into 20 copies each with a 10MB attachment
    - 200MB on the wire as it clears the queue.

    2) The thread is lively and people enjoy the reply-all feature. Each reply contains the attachment. In a few minutes, 10 replies go back and forth.
    - every reply splits into 20 copies as it clears the queue
    - 10 replies x 20 copies each = 200 copies x 10MB attachment = ~2GB of traffic in a few minutes from one email thread

    In E2k10 single instance storage no longer exists; everybody on a database receiving that email gets a unique copy of the attachment. The original and replies don't account for just ~2.2GB of network traffic; they're ~2.2GB of storage that's being consumed on the back-end, all from the work of a few minutes.

    Will your admin notice? Depends how many databases there are, how much storage there is, what kind of NICs your servers are using (1Gb/sec are common), etc. Short answer is "probably not". But the problem isn't one message or one thread; it's the ability to generate significant content in a very short order by anybody in the organization. Yours might not be the only thread with an attachment that people are replying-all to at any given time.

    Scale the problem up to a thousand people sharing a server. The odds of people eating needless space go up quite a bit.

    Scale it to 50,000 users in the US and UK, and distro lists that have global reach. How many extra gigs are going across your undersea WAN link every time reply-all gets hit? Is the pipe big enough to tolerate the casual mis-use that your users are going to put it through?

    Scale the problem for an environment that (foolishly) didn't use attachment size limits. Ever see someone try to stuff a DVD .iso through an SMTP send queue to a group of recipients? Positively joyful, I assure you.


    tl,dr; attachments get dropped to help people avoid the wrath of unstable administrators.
  • ZAZ: The description reminds me of the job I had working on Compartmented Mode Workstation software. It was based on Unix but had security classification built in. Everything had a security label. If you tried to cut and paste it would either deny you or change the classification of the destination to match the source.

    It could be defeated the same ways as Exchange. Take a picture (but cameras were bigger in the 1990s). Retype (some people could type fast back then). Hack into the network (these systems required physically secure networks).


    Yup. The TS/SCI shops I deployed Exchange for were both physically isolated and ran full fiber from desktop to server to cut down on what someone could theoretically lift with TEMPEST gear. I always thought that was a cool threat to worry about. (I never heard of anybody actually getting useful data via TEMPEST but the theory was neat.)

    As worried as we always were about technical leaks (particularly with the number of intrusions China executed), the biggest source of leaked information was always people. Sometimes due to social engineering; sometimes because folks who work in SCIFs are lonely (they don't get out much) and will talk to anybody who'll listen; sometimes just because people forget that compartmentalization has to happen in your head as well as at your job site. Compared to computers, people leak like sieves.
  • Wingchild: Rising_Zan_Samurai_Gunman: However, I wish there was an option to Forward but automatically copy in some or all of the original recipients. People use Reply to All to add people all the time when there are attachments, but only Forward includes the original attachments.

    Reply All, copy recipient list, close mail. Forward, paste recipient list. Inconvenient but fairly quick.


    Dropping attachments on replies is almost mandatory. Consider an Exchange 2010 example:

    1) You send a message with a 10MB attachment to a list of 20 people.
    - that hits your transport server's queue as a single 10MB message, then bifurcates into 20 copies each with a 10MB attachment
    - 200MB on the wire as it clears the queue.

    2) The thread is lively and people enjoy the reply-all feature. Each reply contains the attachment. In a few minutes, 10 replies go back and forth.
    - every reply splits into 20 copies as it clears the queue
    - 10 replies x 20 copies each = 200 copies x 10MB attachment = ~2GB of traffic in a few minutes from one email thread

    In E2k10 single instance storage no longer exists; everybody on a database receiving that email gets a unique copy of the attachment. The original and replies don't account for just ~2.2GB of network traffic; they're ~2.2GB of storage that's being consumed on the back-end, all from the work of a few minutes.

    Will your admin notice? Depends how many databases there are, how much storage there is, what kind of NICs your servers are using (1Gb/sec are common), etc. Short answer is "probably not". But the problem isn't one message or one thread; it's the ability to generate significant content in a very short order by anybody in the organization. Yours might not be the only thread with an attachment that people are replying-all to at any given time.

    Scale the problem up to a thousand people sharing a server. The odds of people eating needless space go up quite a bit.

    Scale it to 50,000 users in the US and UK, and distro lists that have global rea ...


    I was an email admin for 10 years (SunOne, Exchange, and Groupwise), and I thank God every day we moved to Google at my latest job. Let someone else deal with the headache.
  • www.vibe.comView Full Size


    Oh no, Rod, you sent this email reply all. You hit reply all!

    www.adrants.comView Full Size
  • Load 25 of 43 newer comments

This thread is closed to new comments.