Fun with Mail -- Flame Manual
Date: Wed, 27 Dec 89 19:11 EST
From: Leonard N. Foner <Foner@YUKON.SCRC.Symbolics.COM>
Subject: Fun with mail (from five years ago!)
Proposed Symbolics guidelines for mail messages
It is impermissible to use the term "EMAIL".
Mail should be at least a mixture of upper and lower case. Devising
your own font (Devanagari, pinhead graphics, etc.) and using it in the
mail is a good entertainment tactic, as is finding some way to use
existing obscure fonts.
Sending the mail from
is frowned upon (although this has gotten much better).
It is customary to attack the someone by including his or her message,
indented (unless you are using MM), and replying point by point, as
someone debating someone they are watching on TV, or hearing on the
It is considered artful to append many messages on a subject, leaving
only the most inflammatory lines from each, and reply to all in one
swift blow. The choice of lines to support your argument can make or
break your case.
Replying to one's own message is a rarely-exposed technique for
switching positions once you have thought about something only after
State opinions in the syntax of fact: "...as well as the bug in LMFS
where you have to expunge directories to get rid of files....."
If you have nothing to say on a subject, replying with a line such as,
"I agree with this." puts you in the TO:'s for all future messages, and
establishes you as "one who really cares", if not an actual expert, on
the topic at hand.
Inclusion of very old messages from others makes for an impressive
The choice of a subject line is of supreme importance. It should be
concise and witty. The subject line has to survive once the discussion
has diverged far past the original subject. Remember "Hewitt AP0"?
Oblique allusion to past famous subject lines is one of the best
techniques for generating subjects. So is any reference to drawings of
People can be set wondering by loading obscure personal patchable
systems, and sending bug reports. Who would not stop and wonder upon
seeing "Experimental TD80-TAPE 1.17, MegaDeath 2.5..."? The same for
provocatively-named functions and variables in stack traces.
Know the list of "large, chronic problems". If there is any problem
with the window system, blame it on the activity system. Any lack of
user functionality should be attributed to the lack of a command
processor. A suprisingly large number of people will believe that you
have thought in depth about the issue to which you are alluding when you
Know how to blow any problem up into insolubility. Know how to use the
phrase "The new ~A system" to insult its argument, e.g., "I guess this
destructuring LET thing is fixed in the new Lisp system", or better yet,
Never hit someone head on, always sideswipe. Never say, "Foo's last
patch was brain-damaged", but rather, "While fixing the miscellaneous
bugs in 243.xyz [foo's patch], I found...."
You get 3 opportunities to advertise your Rock band, no more.
Idiosyncratic indentations, double-spacing, capitalization, etc., while
stamps of individuality, leave one an easy target for parody.
Strong language gets results. "The reloader is completely broken in
242" will open a lot more eyes than "The reloader doesn't load files
with intermixed spaces, asterisks, and <'s in their names that are
bigger than 64K". You can always say the latter in a later paragraph.
The entire life, times, collected works, expressions, and modalities of
Zippy the Pinhead are a common ground for much of the metaphor,
rhetoric, and invective which pass daily through the mail. An
occasional parenthetical "yow" CORRECTLY USED will endear one to the
senior systems staff. So will puns and other remarks addressed directly
to the point.
MLB volunteered the following, 4/13/84
This exchange between Eric Weaver and Mike McMahon ensued:
Including a destination in the CC list that will cause the recipients'
mailer to blow out is a good way to stifle dissent.
When replying, it is often possible to cleverly edit the original
message in such a way as to subtly alter its meaning or tone to your
advantage while appearing that you are taking pains to preserve the
author's intent. As a bonus, it will seem that your superior
intellect is cutting through all the excess verbiage to the very heart
of the matter.
Referring to undocumented private communications allows one to claim
virtually anything: "we discussed this idea in our working group last
year, and concluded that it was totally brain-damaged".
Points are awarded for getting the last word in. Drawing the
conversation out so long that the original message disappears due to
being indented off the right hand edge of the screen is one way to do
this. Another is to imply that anyone replying further is a hopeless
cretin and is wasting everyone's valuable time.
Keeping a secret "Hall Of Flame" file of people's mail indiscretions,
or copying messages to private mailing lists for subsequent derision,
is good fun and also a worthwhile investment in case you need to
blackmail the senders later.
Users should cultivate an ability to make the simplest molehill into a
mountain by finding controversial interpretations of innocuous
sounding statements that the sender never intended or imagined.
Obversely, a lot of verbal mileage can also be gotten by sending out
incomprehensible, cryptic, confusing or unintelligible messages, and
then iteratively "correcting" the "mistaken interpretations" in the
Electronic mail is an indispensible component of the automated office.
Besides providing entertainment, it gives one the appearance of
engaging in industrious and technically sophisticated activity. By
flaming constantly on numerous mailing lists, one can be assured of a
ready supply of makework as well as an opportunity to establish one's
reputation amongst the "litterati" [sic].
Date: Monday, 2 April 1984, 22:41-PST
From: Eric Weaver <Weaver at SWW-WHITE>
Send messages calling for fonts not available to the
recipient(s). This can (in the case of Zmail) totally disable
the user's machine and mail system for up to a whole day in some
Date: Friday, 13 April 1984, 20:07-EST
From: Mike McMahon <MMcM at SCRC-TENEX>
Subject: Mail Style Addendum
To: Eric Weaver <Weaver at SWW-WHITE>
Trivialize a user's bug report by pointing out that it was fixed
independently long ago in a system that hasn't been released yet.
Further suggestions along these lines welcomed.