Thread View: comp.sys.mac.oop.macapp3
1 messages
1 total messages
Started by Navarrete, Ed
Sat, 19 Dec 1992 00:02
EMail etiquette proposal
Author: Navarrete, Ed
Date: Sat, 19 Dec 1992 00:02
Date: Sat, 19 Dec 1992 00:02
54 lines
2865 bytes
2865 bytes
hello,
Due to the tremendous number of e-mails I get everyday I would like to suggest
some guides that could be used on MacAppTech$ when sending links. Maybe this
could come up for discussion at the MADA meeting at SF MacWorld. I think the
reason most people leave Tech$ is due to the load and losing private E-mails.
By following some guidelines I think this would help decrease this frustration
level.
Ed Navarrete/DTS
Apple Computer, Inc.
This is from a set of guidelines proposed at Apple:
===================================
E-mail overload faces all of us, and a great number of messages do not directly
contribute to the ongoing successful of our jobs. In addition it is often
difficult to determine the content of an e-mail from the title alone.
And in order to maintain a high level of responsiveness we need to be able to
filter the highest priority e-mails by scanning the titles/subject heading.
o Here are the guidelines:
When addressing an e-mail message please begin the title/subject line with one
of the following prefixes...
Prefix Meaning
FYI: For Your information, non-essential info, but of possible interest
PI: Personal information directed to an individual, no response req'd
R: This e-mail requires a direct response and is required reading
If you send an e-mail message to more than one person, add a "$" to the prefix
to indicate that the e-mail is being broadcast to a group.
In addition, if the e-mail involves a deadline, please include that date. If
you see a date in the title/subject line of an e-mail, always consider it to be
the deadline, schedule or due date.
Examples: FYI$: Local MADA meeting
PI$: Thank you for your response
R$: How do I ...
Finally, please consider these 'e-mail etiquette' ideas when creating mail:
o One-minute-emails! - develop the practice of writing e-mails that fit on one
page and can be read in under a minute. Enclosed longer documents if needed.
o Intelligible titles - make sure the title makes sense and gives a hint at the
content of the link (i.e. "I'm at Comdex till 1/22", _not just_ "Outta here!").
o Assume appreciation - respond to e-mails with _content_ only; simple "thank
you for your reply" messages are not needed (unless really called for).
o Compress wisely - do not compress small files (i.e. under 100k) as this
requires several extra steps for the reader to download, decompress and read.
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads