A signature block (often abbreviated as signature, sig block, sig file, .sig, dot sig, siggy, or just sig) is a block of text automatically appended at the bottom of an email message, Usenet article, or forum post.
Email and Usenet
An email signature is a block of text appended to the end of an email message often containing the sender's name, address, phone number, disclaimer or other contact information.
"Traditional" internet cultural .sig practices assume the use of monospaced ASCII text because they pre-date MIME and the use of HTML in email. In this tradition, it is common practice for a signature block to consist of one or more lines containing some brief information on the author of the message such as phone number and email address, URLs for sites owned or favoured by the author - but also often a quotation (occasionally automatically generated by such tools as fortune), or an ASCII art picture. Among some groups of people it has been common to include self-classification codes.
|\_/| **************************** (\_/) / @ @ \ * "Purrrfectly pleasant" * (='.'=) ( > º < ) * Poppy Prinz * (")_(") `>>x<<´ * (firstname.lastname@example.org) * / O \ ****************************
Most email clients, including Mozilla Thunderbird, the built-in mail tool of the web browser Opera, Microsoft Outlook and Outlook Express, and Eudora, can be configured to automatically append an email signature with each new message. A shortened form of a signature block (sometimes called a "signature line"), only including one's name, often with some distinguishing prefix, can be used to simply indicate the end of a post or response. Most email servers can be configured to append email signatures to all outgoing mail as well.
Signatures in Usenet postings
Signature blocks are also used in the Usenet discussion system.
...orist it's an unnecessary optimization and a (to use your words) "performance hack", but I'm interested in a Real operating system --- not a research toy. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Theodore Ts'o bloom-beacon!mit-athena!tytso 308 High St., Medford, MA 02155 ty...@athena.mit.edu Everybody's playing the game, but nobody's rules are the same!
The Usenet standards specify that a signature block should be displayed as plain text in a fixed-width font (no HTML, images, or other rich text), and should be delimited from the body of the message by a single line consisting of exactly two hyphens, followed by a space, followed by the end of line (i.e.,
"-- \n"). This latter prescription, which goes by many names, including "sig dashes", "signature cut line", "sig-marker", "sig separator" and "signature delimiter", allows software to automatically mark or remove the sig block as the receiver desires.
-- Brad Templeton, publisher, ClariNet Communications Corp. in...@clari.net The net's #1 E-Newspaper (1,160,000 paid sbscrbrs.) http://www.clari.net/brad/
Email signatures in business
While signature blocks exist in business email, the culture is very different. Emails and their signatures are generally in HTML, so fonts and colors are common in both the body of the email and the signature. There is no tradition of ASCII art, pithy quotes, or the sig dash.
Businesses do often automatically append signatures blocks to messages - or have policies mandating a certain style. Generally they resemble standard business cards in their content - and often in their presentation - with company logos and sometimes even the exact appearance of a business card. In some cases a vCard is automatically attached.
In addition to these standard items, email disclaimers of various sorts are often automatically appended. These are typically couched in legal jargon, but it is unclear what weight they have in law, and they are routinely lampooned.
Business emails may also be some signature block elements mandated by local laws:
- Germany requires companies to disclose their company name, registration number, place of registration etc. in email signatures, in any business-related emails.
- Ireland's Director of Corporate Enforcement requires all limited companies operating websites to disclose such information in their emails.
- The UK's ECommerce Regulations require this information in all emails from limited companies as well.
While criticized by some as overly bureaucratic, these regulations only extend existing laws for paper business correspondence to email.
On web forums, the rules are often less strict on how a signature block is formatted, as Web browsers typically are not operated within the same constraints as text interface applications. Users will typically define their signature as part of their profile. Depending on the board's capabilities, signatures may range from a simple line or two of text to an elaborately-constructed HTML piece. Images are often allowed as well, including dynamically updated images usually hosted remotely and modified by a server-side script. In some cases avatars or hackergotchis take over some of the role of signatures.
With FidoNet, echomail and netmail software would often add an origin line at the end of a message. This would indicate the FidoNet address and name of the originating system (not the user). The user posting the message would generally not have any control over the origin line. However, single-line taglines, added under user control, would often contain a humorous or witty saying. Multi-line user signature blocks were rare.
Notes and references
- "LINUX is obsolete", comp.os.minix
- Note that the email address has been automatically obfuscated by Google Groups
- See Charles H. Lindsey: Usenet Best Practice, 2005, and also RFC 3676: The Text/Plain Format and DelSp Parameters, section 4.3, 2004, and RFC 1849: “Son of 1036”: News Article Format and Transmission, section 4.3.2, 2010 (first circulated in 1994).
- "Admin: "Internet Jokebook" price reduced to $9.95", 02/12/1995, rec.humor.funny
- "Spare us the e-mail yada-yada", The Economist, April 9, 2011: 73
- Lester Haines (18 May 2001), "The Email Disclaimer Awards 2001", The Register
- "German bureaucracy, coming to your e-mail now"
- "Irish ODCE Information Notice I/2007/2 - Disclosure of Company Particulars in E-Communications and on Websites"
- "ECommerce Regulations"
- "FidoNet EchoMail Specification"
- "A Proposed Replacement For FTS-0004"
- RFC 1855, "Netiquette Guidelines" (section 2.1.1 contains guidelines on mail)
- RFC 3676, (4.3 Usenet Signature Convention)