Skip to main content Accessibility help
×
Hostname: page-component-76fb5796d-22dnz Total loading time: 0 Render date: 2024-04-26T13:59:12.594Z Has data issue: false hasContentIssue false

4 - Sending emails

Published online by Cambridge University Press:  21 January 2021

Get access

Summary

There is no unsend

You cannot ‘unsend’ an email. That is the big problem. Mixing up the contents of the Cc-header and the Bcc-header can result in having made enemies forever. With some email clients you can postpone the actual sending of emails. This queuing can be very handy. The queued emails can be checked later, when you are less emotional for instance.

Formatting of your message

Avoid sending styled text as much as possible.

So no accents, diacritics, ligatures etc. Sending styled text (rtf or even more proprietary) is against the philosophy of the internet. Even sending html files (web pages) should be avoided whenever possible.

ASCII

The crucial communication rule on the internet is:

“Send information as plain text (ASCII) whenever possible”.

So do not use styled text with varying font size, italic, bold and colored fonts, and try to avoid sending attachments.

Many email clients allow the user to add formatting to their text. Popular formatting standards are html and rtf.

ASCII styling

Even with plain ASCII there is still a lot you can do to structure your emails.

You can use uppercase and lowercase. Do not use uppercase in the middle of a sentence to indicate emphasized text: it will give the impression you are shouting. “You have to do this before MONDAY” is insulting. Be creative, like “You have to do this before *Monday*”.

Underline text like this: “_This is very important_”.

You can use strings of asterisks “*” as text separators. Software developers have to stick to plain ASCII when writing computer code. They are very creative in using all kinds of ASCII characters to have text comments stand out, like:

“/////////////////////////// ////// RESULTS ///////// ///////////////////////////”.

Rtf

In principle, the idea behind Microsoft's rtf (Rich text format) is appealing: a general cross-platform encoded 7-bit ASCII. The problem is that Microsoft is continuously changing its proprietary rtf-standard, making it very difficult for independent software vendors to develop software with backward compatibility. In addition rtf-files tend to be bulky. You need a viewer (which many email clients have) to be able to read the formatted text

Type
Chapter
Information
Survival Guide for Scientists
Writing - Presentation - Email
, pp. 212 - 228
Publisher: Amsterdam University Press
Print publication year: 2009

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure coreplatform@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

  • Sending emails
  • Ad Lagendijk
  • Book: Survival Guide for Scientists
  • Online publication: 21 January 2021
  • Chapter DOI: https://doi.org/10.1017/9789048506255.029
Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

  • Sending emails
  • Ad Lagendijk
  • Book: Survival Guide for Scientists
  • Online publication: 21 January 2021
  • Chapter DOI: https://doi.org/10.1017/9789048506255.029
Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

  • Sending emails
  • Ad Lagendijk
  • Book: Survival Guide for Scientists
  • Online publication: 21 January 2021
  • Chapter DOI: https://doi.org/10.1017/9789048506255.029
Available formats
×