Summary

  • DEC used ARPANET mail to invite a selected research-network audience to product demonstrations; the preserved recipient list overflowed the message fields, and a contemporary participant said some intended recipients never received it.
  • DCA called the advertisement a breach of the network’s official-use rule, while participants debated unequal access, commercial advantage and censorship. The record shows an announced response, not a verified sanction.

The address list was part of the story

The message promoted DEC’s DECSYSTEM-20 family and pointed to its ARPANET support under TOPS-20. It invited readers to two California demonstrations. In a forwarded copy preserved in the May 1978 MSGGroup archive, the To list runs for pages and continues into the body. The surviving header fields do not establish a clean audience count or a successful delivery total.

Einar Stefferud, one of the network’s participants, later explained that SNDMSG had limited To, Cc and subject space. The addresses overflowed from one field to another and into the body, and some intended recipients—including him—did not receive the advertisement. That account is useful evidence of the mail client’s practical limits, but it is not a delivery log. Nor does the episode prove that every person listed received the same message.

The dates in the surviving record also resist a single neat anniversary. The forwarded DEC header is dated 1 May 1978 and says the message was received at DEC-Marlboro on 3 May. A DCA note embedded in the correspondence refers to a message sent on 2 May; the archive’s later narrative says it was sent on 3 May. The evidence supports “May 1978,” not a settled send date.

Enforcement depended on the network around the network

The Defense Communications Agency (DCA) response called the advertisement a violation of ARPANET’s official-government-business-only use rule. It said action was being taken to prevent a repeat, then named the enforcement dependency: ARPANET sponsors, host contacts and TIP liaisons. This is a description of an administrative chain, not proof that a particular penalty followed.

Jake Feinler’s 7 May response made access itself the issue. Companies without ARPANET access could not reach the same selected audience; a connected firm could gain a market advantage unavailable to competitors. She extended the same logic to employment messages. The rule was therefore about more than bandwidth or etiquette: it governed how a scarce network privilege could be used.

Mark Crispin agreed that bulk advertising did not belong on ARPANET, yet warned against confusing that rule with censorship on other networks. He described ARPANET mail as closer to an internal memo than a public trade journal and imagined that commercial systems might need to leave unwanted mail to the recipient’s own delete command. Richard Stallman first said the ad would not have bothered him; after seeing its unusually long header, he objected to the message’s size. Their replies show disagreement, not a settled community vote.

A network-level refusal is a different control

Jon Postel’s 1975 RFC 706 described a host/IMP interface that could not selectively refuse traffic from a source host. It proposed a technical refusal mechanism to limit traffic from a malfunctioning or unwanted host. That proposal was about where network traffic could be stopped; it was not an email filter or a rule against commercial content. The DEC exchange addressed a separate control surface: who could use ARPANET mail and which local institutions were expected to enforce the use policy.

The episode’s value is not a claim that one message invented spam. It shows the gap between a directory that made a selected community reachable and a rule that tried to keep that reach within its stated purpose.

Sources