Using all @, e-mail rudeness. Why not to send e-mail to the whole address book.
Recently a user of a Livejournal community put up a bitch post about someone being rude to her after she sent an all @ e-mail that didn't apply to all @. The argument devolved into a 'best practise' versus 'user perception' mud slinging match that went no where.
The good thing is it gave me the opportunity to think about and explain why IT departments have the policy they do.
You may think it's a small thing to simply delete an advertisement for a car or an announcement about the baby. But the cost is much higher than simply clicking a mouse button and here are my 5 main reasons as to why:
1. It wastes time. I read somewhere that a person has a maid because he can always make more money but can never make more time. Your individual mail might take 30 seconds of reading and deletion time but the others that are encouraged by your abuse of the mailing system will also do the same thing. Remember, behavior is often reinforced by peer groups. Be the better person.
2. It wastes storage space. Each of those tiny little e-mails you send will hide themselves on the server and possibly in forwarded mail boxes. Much like option 1, 2kb of data isn't much in itself but can stack rather highly after say 1,000 of the same. Especially considering the 2kb copy is generated for 20 to 20,000 people. That adds up.
3. It's rude. It might be easier for you to send out this one e-mail to everyone but would you also take a disabled parking space? I mean it's closer to the doors of the supermarket. You're putting someone out because it's easier for you.
4. It wastes your IT department's time. Similar again to option 1 instead we have to then enforce rules about our policies and when it's appropriate. Want that new faster Internet access installed and wonder why it's taking so long? It's because we're spending time sorting out little things like reprimanding people for advertising their phones on the All @ list.
5. It wastes bandwidth. Those messages must travel over the network and the effect is, again, cumulative. Wondering why the network is so slow at 9:00 am? It's because you're all sending messages to all @ and those messages are being read. That data has to be transferred via the existing infrastructure which is limited.
So, you now know why it's not appropriate to send out all @ mails. When is it and why?
1. When the information really is pertinent to all employees. In the past when managing mail servers I sent out mails to let people know about scheduled downtime. I sent them to let them know about issues, or to document certain changes so everyone had a reference point. I sent them for commonly asked questions regarding the network (common meaning 20+ people had asked the question.) I sent them to explain outages. In sum, I sent e-mails to all @ when everyone either wanted or needed to know the answer and resolution to a question or problem.
In other non-technical cases this would be for year end profit announcements or company wide celebrations.
2. When there's a possibility of work diversion or questions being asked. For example, when a branch office loses it's phones or e-mail access. There's a possibility that information will need to be passed on to provide a good service.
Overall, as I tried to get across to random Internet user, it's a matter of consideration. You can give all the statistics you like about storage, bandwidth and time but it's really a matter of taking the time to make your messages pertinent. People might not even realize how good you're being.... but you'll know and the techies will quietly love you for it.


