mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-26 21:30:55 +08:00
geekpi
GitHub
commit
bcb489c6ab
@ -1,81 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (geekpi)
|
||||
[#]: 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
|
||||
@ -0,0 +1,77 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (geekpi)
|
||||
[#]: 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 个电子邮件错误以及如何避免它们
|
||||
======
|
||||
自动化是美好的，除非不是那样。确保你的电子邮件自动回复和抄送配置正确，这样你就不会浪费大家的时间。
|
||||
![Computer screen with files or windows open][1]
|
||||
|
||||
在前几年，这个年度系列涵盖了单个的应用。今年，我们除了关注 2021 年的策略外，还将关注一体化解决方案。欢迎来到 2021 年 21 天生产力的第十七天。
|
||||
|
||||
好了，我们已经谈到了一些我们应该对电子邮件做的事情：[不要再把它当作即时通讯工具][2]、[优先处理事情][3]、[努力达到收件箱 0 新邮件][4]，以及[有效过滤][5]。但哪些事情是我们不应该做的呢？
|
||||
|
||||
|
||||
|
||||
![Automated email reply][6]
|
||||
|
||||
你真幸运 （Kevin Sonney, [CC BY-SA 4.0][7]）
|
||||
|
||||
### 1\. 请不要对_所有事情_自动回复
|
||||
|
||||
任何邮件列表中总有些人，他们去度假了，并设置了一个“我在度假”的自动回复信息。然而，他们没有正确地设置，所以它对列表上的每一封邮件都会回复“我在度假”，直到管理员将其屏蔽或取消订阅。
|
||||
|
||||
我们都感受到了这种痛苦，我承认过去至少有一次，我就是那个人。
|
||||
|
||||
从我的错误中吸取教训，并确保你的自动回复器或假期信息对它们将回复谁和多久回复一次有限制。
|
||||
|
||||
![An actual email with lots of CC'd recipients][8]
|
||||
|
||||
这是一封真实的电子邮件 （Kevin Sonney, [CC BY-SA 4.0][7]）
|
||||
|
||||
### 2\. 请不要抄送给所有人
|
||||
|
||||
我们都至少做过一次。我们需要发送邮件的人员众多，因此我们只需抄送他们_所有人_。有时这是有必要的，但大多数时候，它并不是。当然，你邀请每个人在庭院吃生日蛋糕，或者你的表姐要结婚了，或者公司刚拿到一个大客户，这都是好事。如果你有邮件列表的话，请用邮件列表，如果没有的话，请给每个人密送。说真的，密送是你的朋友。
|
||||
|
||||
### 3\. 回复所有人不是你的朋友
|
||||
|
||||
![Reply options in Kmail][9]
|
||||
|
||||
这一条与上一条是相辅相成的。我不知道有多少次看到有人向一个名单（或者是一个大群的人）发送信息，而这个信息本来是要发给一个人的。我见过这样发送的相对好的邮件，以及随之而来的纪律处分邮件。
|
||||
|
||||
认真地说，除非必须，不要使用“回复全部”按钮。即使是这样，也要确保你_真的_需要这样做。
|
||||
|
||||
有些电子邮件应用比其他应用管理得更好。Kmail，[KDE Kontact][10] 的电子邮件组件，在**回复**工具栏按钮的子菜单中，有几个不同的回复选项。你可以选择只回复给**发件人**字段中的任何实体（通常是一个人，但有时是一个邮件列表），或者回复给作者（在抄送或密送中去除任何一个人），只回复给一个邮件列表，或者回复_所有人_（不要这样做）。看到明确列出的选项，的确可以帮助你了解谁会收到你要发送的邮件副本，这有时比你想象的更发人深省。我曾经发现，当我意识到一个评论并不一定会对一个复杂的讨论的最终目标有所帮助时，我就会把邮件的收件人改为只收作者，而不是整个列表。
|
||||
|
||||
(另外，如果你写的邮件可能会给你的 HR 或公司带来麻烦，请在点击发送之前多考虑下。)
|
||||
|
||||
希望你已经_不再_电子邮件中这么做了。如果你认识的人是这样的呢？欢迎与他们分享。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/21/1/email-mistakes
|
||||
|
||||
作者：[Kevin Sonney][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者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