Why should email signatures be four lines or less?

No.042 · Added 2026-10-29

Trivia No.042

It was a netiquette rule of thumb to keep messages short and reduce recipients’ connection costs, not an email protocol limit.

A recommendation with a reason

The four-line signature rule appears explicitly in RFC 1855, the Netiquette Guidelines published in 1995. Its advice was to keep a signature short, with four lines as a rule of thumb. The reason followed immediately: some recipients paid for connectivity by the minute, so a longer message could cost them more.

That was advice about behaviour on a shared network. The document identifies itself as Informational and states that it does not specify an Internet standard. A fifth line did not make a message technically invalid. The recommendation asked the sender to consider a cost borne at the receiving end.

Contact details had a limited job

Elsewhere, the guidelines explain why a signature file was useful. Mail software could remove return-address information, so a line or two of contact details helped recipients identify the sender. A prepared .sig file could be appended to messages, automatically in some programs. It served as a small contact card.

The document also notes that mail consumes bandwidth, disk space and processing resources. Its concern was broader than the price of one telephone connection. An automatically repeated block became part of every message it accompanied. Keeping that block compact was consistent with the same economy applied to other network traffic.

The separator is a different convention

RFC 3676, published in 2004, describes another signature convention inherited from Usenet: a line containing two dashes followed by a space separates the message from its signature. That marker is about recognising a boundary in plain text. It does not prescribe how many lines may follow it.

The distinction matters in the document’s treatment of text that can be rewrapped for different display widths. A signature separator ends in a space, but needs special handling instead of being treated as an ordinary line eligible for that text-flow processing. Software has a formatting reason to recognise it.

The length recommendation and the separator therefore solve different problems. One limits the burden placed on a correspondent; the other identifies the signature in a text format. Neither should be confused with a cryptographic digital signature, which RFC 3676 discusses separately. The familiar four-line advice was a matter of network manners, with an explicit economic explanation.

Try it on your break

Word Counter Count mixed Chinese, Japanese and English text as you type. Check a selection or set a word goal; input stays in the page.

Sources

  1. RFC 1855: Netiquette Guidelines — IETF
  2. RFC 3676: The Text/Plain Format and DelSp Parameters — IETF

Included in

More from this collection

Trivia No.024

How did T9 predictive text work?

Trivia No.024

For alphabetic text, T9 matched one keypress per letter against a dictionary, ranked matching words and let the user choose alternatives.

Read more →
Trivia No.038

Where does the Nokia ringtone come from?

Trivia No.038

It comes from a phrase in Gran vals, a solo-guitar waltz by Spanish composer Francisco Tárrega, adapted into a phone ringtone.

Read more →
Trivia No.006

Why did dial-up modems make that noise?

Trivia No.006

The sounds were connection signals: two modems identified compatible modes and tested the phone line. A speaker let you hear the exchange.

Read more →

Also in: 中文 日本語