mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-26 21:30:55 +08:00
选题[tech]: 20210127 3 email mistakes and how to avoid them
sources/tech/20210127 3 email mistakes and how to avoid them.md
This commit is contained in:
parent
f6d9c799f6
commit
0ca1e9bd4c
@ -0,0 +1,81 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (3 email mistakes and how to avoid them)
|
||||
[#]: via: (https://opensource.com/article/21/1/email-mistakes)
|
||||
[#]: author: (Kevin Sonney https://opensource.com/users/ksonney)
|
||||
|
||||
3 email mistakes and how to avoid them
|
||||
======
|
||||
Automation is wonderful, except when it's not. Be sure your email
|
||||
auto-responds and CCs are properly configured so you don't waste
|
||||
everyone else's time.
|
||||
![Computer screen with files or windows open][1]
|
||||
|
||||
In prior years, this annual series covered individual apps. This year, we are looking at all-in-one solutions in addition to strategies to help in 2021. Welcome to day 17 of 21 Days of Productivity in 2021.
|
||||
|
||||
OK, so we've talked about some things we should do with our email - [Stop treating it as an instant messenger][2], [Prioritize things][3], [trying to reach Inbox Zero][4], and [filtering it effectively][5]. But what things SHOULDN'T we do?
|
||||
|
||||
|
||||
|
||||
![Automated email reply][6]
|
||||
|
||||
Lucky you (Kevin Sonney, [CC BY-SA 4.0][7])
|
||||
|
||||
### 1\. Please do not Auto-respond to _everything_
|
||||
|
||||
There is always that one person on any mailing list. They have gone on vacation and set up an "I'm on vacation" auto-reply message. However, they didn't set it up correctly, so it responds to every email on the list with "I'm on vacation" until an admin mutes or unsubscribes them.
|
||||
|
||||
We have all felt this pain, and I'll admit that at least once in the past, I was that person.
|
||||
|
||||
Learn from my mistakes, and make sure that your auto-responders or vacation messages have limits on who they will respond to and how often.
|
||||
|
||||
![An actual email with lots of CC'd recipients][8]
|
||||
|
||||
This is a real email (Kevin Sonney, [CC BY-SA 4.0][7])
|
||||
|
||||
### 2\. Please do not CC everyone and the world
|
||||
|
||||
We've all done it at least once. There is that big list of people we need to send an email to, so we just carbon copy (CC) _all_ of them. Sometimes this is warranted, but most of the time, it isn't. Sure, it's nice that you invited everyone to have birthday cake in the atrium, or that your cousin twice removed is getting married, or that the company just got a big account. Please, use a mailing list if you have one, or blind carbon copy (BCC) everyone if you don't. Seriously, BCC is your friend.
|
||||
|
||||
### 3\. Reply All is NOT your friend
|
||||
|
||||
![Reply options in Kmail][9]
|
||||
|
||||
This one goes hand-in-hand with the previous item. I do not know how many times I have seen someone send a message to a list (or just a big group of people) that was meant to go a single person. I have seen the relatively benign emails that have been sent that way and resulting disciplinary action emails that followed.
|
||||
|
||||
Seriously, do not use "Reply All" button unless you have to. And even then, make sure you _really_ have to.
|
||||
|
||||
Some email applications manage this better than others. Kmail, the email component of [KDE Kontact][10], has several different reply options available in a sub-menu of the **Reply** toolbar button. You can choose to just reply to whatever entity is in the **From** field (usually a person, but sometimes a mailing list), or to the author (dropping anyone in CC or BCC), just to a mailing list, or to _all_ (don't do this). Seeing the options listed explicitly can really help you understand who's going to get a copy of an email you're about to send, which is sometimes more thought-provoking than you might expect. I've caught myself changing the recipient of an email to just the author instead of to an entire list upon realizing that a comment doesn't necessarily add to the end goal of a complex discussion.
|
||||
|
||||
(Also, if you write an email that could get you in trouble with HR or your company, think about it for a long time before hitting Send.)
|
||||
|
||||
Hopefully, these are things you are already _not_ doing with email. And if someone you know is? Feel free to share this with them.
|
||||
|
||||
Ditch Outlook and check out six of the best open source desktop email applications.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/21/1/email-mistakes
|
||||
|
||||
作者:[Kevin Sonney][a]
|
||||
选题:[lujun9972][b]
|
||||
译者:[译者ID](https://github.com/译者ID)
|
||||
校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/ksonney
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/browser_screen_windows_files.png?itok=kLTeQUbY (Computer screen with files or windows open)
|
||||
[2]: https://opensource.com/article/21/1/email-rules
|
||||
[3]: https://opensource.com/article/21/1/prioritize-tasks
|
||||
[4]: https://opensource.com/article/21/1/inbox-zero
|
||||
[5]: https://opensource.com/article/21/1/email-filter
|
||||
[6]: https://opensource.com/sites/default/files/day17-image1.png
|
||||
[7]: https://creativecommons.org/licenses/by-sa/4.0/
|
||||
[8]: https://opensource.com/sites/default/files/day17-image2.png
|
||||
[9]: https://opensource.com/sites/default/files/kmail-replies.jpg (Reply options in Kmail)
|
||||
[10]: https://opensource.com/article/21/1/kde-kontact
|
Loading…
Reference in New Issue
Block a user