---
name: Mail Art
slug: mail-art
type: distributed creative protocol
status: running
version: 0.0.∞
released: "1962-04-01"
maintainer: the global postal system (unwitting)
dependencies:
  - postage stamp
  - envelope
  - human desire to be witnessed
  - scissors
  - low expectations of delivery time
license: Anti-Copyright (fork freely, always)
tags:
  - art
  - communication
  - networks
  - fluxus
  - subversion
  - slow internet
---

Mail Art

What it actually is

A conspiracy between creativity and bureaucracy in which artists use postal infrastructure as both medium and gallery.

How it works

Someone makes something small enough to mail. They address it to a stranger or a friend. The postal system, designed for bills and parcels, carries it anyway. The recipient opens it expecting nothing interesting and gets something interesting instead.

That is the entire architecture. It has run continuously since the early 1960s when Ray Johnson started mailing collages to people who had not asked for them and calling the resulting network the New York Correspondence School. The name was a joke. The network was real.

Features

Open participation: no jury, no application, no residency requirement. A stamp is the only access token
Anti-market by design: originals travel point to point, unpriced, often unsigned
Slow latency: delivery measured in days or weeks. Considered a feature by most maintainers
Physical persistence: unlike email, a mail art piece exists as an object that can be held, smelled, and accidentally lost behind a radiator
Rubberstamp subculture: entire sub-ecosystem of hand-carved stamps, ink pads, and obsessive cataloguers
Zine adjacency: shares approximately 60% of its dependency tree with zine culture

Known bugs

Return address optional, which means conversations sometimes terminate unexpectedly
Postal damage occasionally improves the work
Hoarders who receive but never send create memory leaks in the network
customs may flag assemblages containing hair, seeds, or suspicious collage elements
"Eternal networks" can fork without notice and lose sync

Configuration

# ~/.mailart/config.yml

send_without_expectation: true
accept_everything: true
document_before_sending: recommended
use_found_materials: encouraged
charge_for_participation: false   # hardcoded, do not override
care_about_postage_rates: sometimes

Error codes

Code	Meaning
`RETURN_TO_SENDER`	recipient moved, work returned, now doubly interesting
`LOST_IN_TRANSIT`	accepted outcome, not an error
`NO_REPLY`	normal. not personal. probably.
`POSTAGE_DUE`	sender miscalculated, recipient must decide if it's worth it
`DAMAGED_IN_TRANSIT`	see Known Bugs re: accidental improvement

Changelog

1962: Johnson ships first objects. No documentation. No release notes.
1970s: Fluxus adopts protocol. Ray Johnson refuses credit for founding anything.
1980s: Rubberstamp subculture peaks. Ink everywhere.
1990s: email launches. Predicted to deprecate mail art. Did not.
2020s: Pandemic drives unexpected spike in usage. People remember that objects are real.

FAQ

Is it art if no one sees it? Someone sees it. That is the point.

Do I need to be an artist? The network has never checked.

What if no one writes back? You have still altered someone's Tuesday. That is more than most software manages.

drafting spec…