Hubbry Logo
Signature blockSignature blockMain
Open search
Signature block
Community hub
Signature block
logo
8 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Signature block
Signature block
Signature block
View on Wikipedia
from Wikipedia
An email signature block example, using a female variant of the Alan Smithee pseudonym.

A signature block (often abbreviated as signature, sig block, sig file, .sig, dot sig, siggy, or just sig) is a personalized block of text automatically appended at the bottom of an email message, Usenet article, or forum post.

Email and Usenet

[edit]

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<<´       *   (pprinz@example.com)   *
 /  O  \       ****************************

Example of a signature block using ASCII art.

Most email clients, including Mozilla Thunderbird, Opera Mail, Microsoft Outlook, 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.

Email signature generator

[edit]

An email signature generator is an app or an online web app that allows users to create a designed email signature using a pre-made template (with no need for HTML coding skills).

Signatures in Usenet postings

[edit]

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!

— a real example from Theodore Ts'o during the Tanenbaum–Torvalds debate[1][2]

Email signatures in business

[edit]

Businesses often automatically append signature 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.[3][4]

Business emails may also use 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.[5]
  • Ireland's Director of Corporate Enforcement requires all limited companies operating websites to disclose such information in their emails.[6]
  • The UK's ECommerce Regulations (reflecting EU law) require this information in all emails from limited companies.[7] In England and Wales the case of Mehta v J Pereira Fernandes clarified that an email address header added to an email by the email application did not count as a signature for legal purposes, but

    A party can sign a document for the purposes of Section 4 [of the Statute of Frauds] by using his full name or his last name prefixed by some or all of his initials or using his initials, and possibly by using a pseudonym or a combination of letters and numbers (as can happen for example with a Lloyds slip scratch), providing always that whatever was used was inserted into the document in order to give, and with the intention of giving, authenticity to it.[8]

While criticized by some [who?] as overly bureaucratic, these regulations only extend existing laws for paper business correspondence to email.

Standard delimiter

[edit]

The Usenet news system standards say that a signature block is conventionally 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., in C-notation: "-- \n").[9][10][11] This latter prescription goes by many names, including “dash dash space”, "sig dashes", "signature cut line", "sig-marker", "sig separator" and "signature delimiter". It 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/

— a real example from Brad Templeton posting in rec.humor.funny in 1995 showing sig dashes.[2][12]

Most Usenet clients (including, for example, Mozilla Thunderbird) will recognize the signature block delimiter in a news article and will cut off the signature below it when inserting a quote of the original message into the composition window for a reply. Although the Usenet standards strictly apply only to Usenet news articles, this same delimiter convention is widely used in email messages as well, and email clients (such as K-9, Opera Mail, and Gmail[13] commonly use it for recognition and special handling of signatures in email.

Internet forums

[edit]
Main article: Signature tag

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.

FidoNet

[edit]

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.

However, a tearline standard for FidoNet was included in FTS-0004[14] and clarified in FSC-0068[15] as three dashes optionally followed by a space optionally followed by text.

See also

[edit]

Notes and references

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Signature block

View on Grokipedia
from Grokipedia
A signature block (often abbreviated as sig or sig block) is a block of text automatically appended at the bottom of an message, article, forum post, or other online communication. It typically includes the author's name, contact information, and may contain additional elements such as disclaimers, quotes, , or links to personal websites, serving to identify the sender and provide context in digital discussions. Signature blocks originated as a convention in early online systems to personalize messages in otherwise anonymous environments, promoting and facilitating replies without requiring full headers. In professional and community settings, they function as a digital equivalent of a , appended automatically by clients or forum software to maintain consistency and . Common components include the full name, , affiliation or location, and sometimes a horizontal rule or separator line. For and , the standard delimiter is "-- " (two hyphens followed by a space) on a line by itself, signaling the start of the to parsers and readers. Variations may include legal disclaimers in emails or creative elements in hobbyist forums, but they are kept brief—typically 4-7 lines—to avoid cluttering threads. Signature blocks adapt across mediums: in emails, they emphasize contact details and branding while complying with spam regulations; in Usenet and forums, they adhere to etiquette guidelines limiting size and content to prevent abuse; and in modern platforms like wikis or social media, they may be automated or restricted to maintain neutrality and focus on content. These conventions ensure signatures enhance communication without overwhelming the primary message.

Overview and Purpose

Definition

A signature block is a structured section typically placed at the end of emails, letters, contracts, or other formal documents, containing the sender's or signatory's identifying information and a space for a handwritten, typed, or electronic signature. It serves to authenticate the communication and provide details for follow-up. In digital contexts, such as emails or forum posts, it is often abbreviated as "sig" or "sig block" and may include creative elements like quotes or ASCII art. This block is automatically attached by many email and posting software, especially in Unix-based systems, and has been recognized as a form of personal expression in online communities. Unlike email footers or auto-appended disclaimers, which are generated by servers or policies for legal notices or branding, signature blocks are customized by the user for personal or identity. Footers and disclaimers typically appear below and serve compliance purposes rather than expression. The term "signature block" dates to the early , with the earliest recorded use in 1920 in contexts. It gained prominence in digital communication from the 1980s onward, coinciding with and Unix mail systems, where users adopted appended text to mimic traditional sign-offs. Signature blocks function as equivalents to handwritten closings in letters, authenticating and personalizing messages while facilitating contact. Signature blocks serve purposes including verifying identity, providing contact information, ensuring legal compliance in documents, and promoting . In professional and legal settings, they bind parties to agreements and enhance for interactions.

Common Components

Common components of a signature block vary by but generally include elements that identify the sender and support . Foundational elements often comprise the full name, professional title or position, and organization affiliation to establish credibility. Contact details, such as phone number, , or website URL, facilitate follow-up. In digital formats like emails, additional items may include links for networking, preferred pronouns for inclusivity, legal disclaimers for liability protection, motivational quotes for personalization, vCards for easy import, or legacy creative features like . In legal documents and traditional letters, components typically feature a signature line (sometimes denoted "/s/" for electronic signing), printed name, title indicating authority (e.g., for corporate representatives), date, and possibly witness or notary lines to ensure enforceability. Best practices recommend brevity, limiting to 4-6 lines for across devices and contexts. Overly elaborate blocks can appear unprofessional or clutter messages. Components have evolved from in early 20th-century documents and digital formats to HTML-enabled elements in modern emails, incorporating hyperlinks and images, though remains preferred for and compatibility. navigation benefits from simple text without complex markup.

Historical Development

Origins in FidoNet and BBS

The practice of appending signature blocks to messages first emerged in the late alongside the rise of systems (BBS). , established in 1984 by Tom Jennings as a decentralized store-and-forward network linking independent BBSes, formalized the use of automated "origin lines" in echomail messages to address the challenges of user and system identification across a distributed environment lacking central authentication. These origin lines were appended by the FidoNet-compatible software to every outgoing echomail message, providing a standardized way to trace the source BBS without relying on manual user input. The origin line format, as later standardized, began with "* Origin: " followed by the BBS name and address in parentheses (e.g., "* Origin: Riverside Software (1:18/300)"), often incorporating the node number for purposes and crediting the or system maintainer. This structure served primarily to enable proper attribution and reply in the network's toss-and-forward mechanism, where messages hopped between nodes overnight via timed calls. By 1985, the inaugural FidoNet policy document outlined technical procedures such as requiring email capability and defining network roles, while promoting general guidelines for conduct to maintain order among growing nodes. The FidoNet Technical Standards Committee (FTSC), formed in 1986, later refined these conventions; for example, FSC-0068 (1992) specified that origin lines should not exceed 79 characters to avoid issues with legacy mail processors and emphasized their placement after any user tearlines but before routing fields like SEEN-BY. Due to the constraints of early dial-up modems operating at 300 , messages faced strict size limits—often capped at a few kilobytes—necessitating concise origin lines, prioritizing essential identifiers over elaborate content. This brevity influenced the design of origin lines, which typically included only the node address, name, and a short , ensuring efficient transmission over lines shared with voice calls.

Evolution in Usenet

Signature blocks evolved in Usenet, a Unix-based discussion system launched in 1979 that grew into a global forum by the late 1980s and 1990s across academic and research networks. Signatures evolved from simple identifiers in early text-based newsgroups to standardized elements. Usenet conventions for signatures emphasized brevity and clarity to manage network bandwidth, establishing a maximum of four lines per signature—known as the McQuary limit—to curb excessive use and prevent "sig wars," informal competitions among users to create elaborate ASCII art signatures that bloated messages. Signatures were delimited from the message body by a line containing exactly "-- " (two hyphens followed by a space), a convention rooted in Usenet's text-only format and later formalized in standards for message processing. Newsreaders such as tin and nn supported automatic inclusion of signatures via a .signature file stored in the user's home directory, allowing seamless appending of personal details like name, email, and affiliation during posting. These guidelines were codified in RFC 1855, published in 1995 by the , which outlined netiquette for and , recommending signatures no longer than four lines and including contact information to facilitate replies while minimizing transmission costs for users on metered connections. In practice, .signature files became a form of personal expression, often featuring literary quotes, humorous aphorisms, or philosophical musings, transforming a functional tool into a that reflected individual wit or worldview in the anonymous expanse of newsgroups. A key difference from was 's shift toward more immediate, online posting via protocols like NNTP, compared to 's delayed batched echomail, which necessitated stricter etiquette enforcement through community norms and tools like killfiles to handle growing message volumes. By the late , the rise of graphical web-based forums and clients diminished the prominence of Usenet signatures, as users migrated to platforms with integrated profiles and visual elements that rendered text-only sig files obsolete.

Applications in Email

Structure and Delimiters

In email systems, the standard for separating the message body from the block is "-- " (two dashes followed by a space), a convention originating from and formalized in RFC 3676 for text/plain format messages. This enables mail user agents (MUAs) to automatically detect, parse, and handle the signature separately, such as by collapsing or quoting it during replies. Signature blocks are typically placed at the end of the email body, after a blank line, to maintain clear separation from the main content. is preferred for broad across MUAs, as it avoids rendering inconsistencies in diverse clients. However, HTML variants are supported in clients like , allowing formatted elements such as bold text, hyperlinks, and images, though this can lead to compatibility issues in non-HTML-supporting environments. Variations in implementation include automatic insertion of the signature and delimiter by MUAs; for example, appends the "-- " line when composing or replying to messages if a is configured. Additionally, signatures may integrate data for structured contact information exchange, as defined in RFC 6350, often as an attached .vcf file or embedded link to facilitate easy import into address books. Common issues arise with overlong signatures, which can exceed client limits (e.g., Gmail's 10,000-character cap) and cause rendering problems like truncation or formatting breakage during replies. Over time, signatures have evolved from strictly text-only formats to include multimedia elements like images and logos in proprietary systems, though this increases the risk of display inconsistencies across MUAs.

Business and Professional Use

In professional email communication, signature blocks serve as standardized footers that convey essential contact details, branding, and legal protections while adhering to norms. These typically include a sender's name, job title, affiliation, phone number, and , often augmented with a company logo for visual identity. Disclaimers such as "This email is confidential and may be privileged" are standard to safeguard sensitive information, particularly in industries like and . For commercial emails, compliance with the U.S. mandates inclusion of a valid physical postal to identify the sender and facilitate opt-out mechanisms, often placed within the signature block to meet these requirements. Best practices emphasize branding through hyperlinks to company websites or social profiles, which drive and reinforce professional identity without overwhelming the reader. is prioritized by incorporating alt text for images like , ensuring signatures render correctly for screen readers and comply with standards such as WCAG. Corporate policies vary: advocates in its Workspace environment, limiting signatures to basic contact information and a subtle to maintain simplicity and focus on content. In contrast, law firms often append detailed disclaimers warning against unauthorized disclosure or use, exemplified by statements like "This communication is intended solely for the designated recipient and may contain attorney-client privileged information," to mitigate liability in sensitive correspondence. Legally, signature blocks in emails can function as enforceable electronic signatures under the U.S. Electronic Signatures in Global and National Commerce Act (ESIGN Act) of 2000, which grants them equivalent validity to handwritten signatures when intent to sign is demonstrated, such as through a typed name or digital certificate. In the , the Regulation of 2014 establishes a framework for electronic signatures, recognizing advanced forms with qualified digital certificates as legally binding across member states, provided they meet authentication standards. However, including like phone numbers or addresses in signatures poses risks, including unintended data leakage if emails are forwarded or intercepted, potentially violating regulations like GDPR by exposing sensitive information without consent. Post-2010, enterprises have increasingly adopted automated signature management tools to centrally control and update blocks across organizations, integrating with CRM systems like for dynamic based on recipient data. These solutions, such as Exclaimer and CodeTwo, streamline compliance by enforcing disclaimers and branding while reducing manual errors, reflecting a shift toward scalable digital communication infrastructure.

Applications in Online Communities

Internet Forums

In web-based internet forums, signature blocks serve as customizable footers appended automatically to users' posts, differing from email signatures by integrating directly with platform rendering engines rather than relying on standardized delimiters like "-- ". These signatures emerged in the mid-1990s alongside the rise of graphical web forums, with early software such as Ultimate Bulletin Board (1996) and later (launched 2000) and (launched 2000) enabling users to define them via profile settings for automatic display below each message. Popular forum software like and supports signature creation through user profiles, where content is stored in the database (typically in a dedicated field like user_sig in the users table) and dynamically rendered with each post to ensure updates propagate across threads without manual editing. Features often include or limited for embedding links, quotes, and images—such as avatars or banners—though administrators can impose restrictions, like 's options to disable IMG tags or set maximum lengths (default 255 characters) to prevent abuse. In modern platforms like (launched ), signatures are not core functionality but available via plugins, allowing advanced editing with multiple images and toggles for visibility, reflecting a shift toward optional implementation. Moderation rules frequently target signatures to curb spam, with platforms like explicitly prohibiting them in posts since 2008, viewing them as unnecessary noise since user cards already link to profiles for . Forums integrate signatures with user profiles, where they complement elements like avatars and bios, but technical challenges arise in threaded views: rendering adds vertical space, potentially disrupting mobile scrolling or collapsing long discussions, leading some software (e.g., ) to hide them by default on narrow screens. Culturally, signatures foster personalization in hobbyist communities, particularly gaming forums, where users craft elaborate designs with character stats, artwork, or memes as a form of digital self-expression and status—evident in early 2000s sites like Hypixel or NeoGAF, where custom "sigs" became a point of pride. However, their prominence has declined post-2010 with mobile-first designs and the rise of social media, as limited screen real estate prioritizes concise threads over appended content, and profile-based info (e.g., bios, flairs) suffices for identity without cluttering discussions.

Social Media and Wikis

In social media platforms, signature blocks have evolved into more integrated and implicit forms, primarily through user profiles, bios, and automated attribution in posts and replies, diverging from the appended text blocks seen in earlier online forums. On (now X), launched in 2006 with a 140-character post limit that influenced overall brevity, user bios function as a compact signature space limited to 160 characters, allowing individuals to include essential identifiers like profession, location, or links without traditional delimiters. Similarly, profiles serve as professional signature equivalents, where sections for headlines, summaries, and contact info provide structured self-presentation that appears alongside posts and messages, emphasizing networking over casual commentary. Threaded replies on these platforms append user handles automatically, such as @username prefixes, which act as digital signatures to maintain conversation context amid algorithm-driven feeds that prioritize recency and over persistent footers. In collaborative wikis powered by software, signature blocks are formalized for talk pages to attribute contributions and enable timestamping. The standard syntax uses four tildes (~~~~), which expand to the user's name and current date/time upon saving, a feature integral to the software since its early implementations around Wikipedia's 2001 launch, with widespread adoption by 2002 as talk pages became central to coordination. Custom signatures can be configured via user preferences to include wiki markup for links to user or talk pages, but they must remain concise to avoid rendering issues in nested discussions. guidelines enforce signing on talk pages to promote , prohibiting unsigned comments and requiring links back to the contributor's page, with variations across wiki installations depending on local policies in the open-source framework. Modern trends in these environments reflect technological and regulatory shifts, integrating verification mechanisms and addressing constraints. Post-2015, verified badges—blue checkmarks on platforms like and —have served as enhanced signatures, confirming authenticity for public figures and brands, with 's program expanding to paid subscriptions in to broaden access. Some platforms have explored NFT integrations for profile badges, such as Ethereum-based tokens displayed as ownership proofs in bios or avatars, though adoption remains niche and tied to communities. The 2018 GDPR enforcement has prompted reductions in personal details within bios and signatures, mandating consent for and limiting identifiable information like emails or addresses in EU users' profiles to mitigate fines for non-compliance. Ephemeral content formats further adapt signature concepts to temporary interactions. On , Stories attribute content to usernames visible for 24 hours, functioning as transient signatures that encourage real-time without permanent blocks. Discord's custom statuses, introduced in 2017, allow users to append short, dynamic phrases or emojis to their profiles, visible in servers and direct messages as pseudo-signatures for ongoing presence indication. These elements build on forum precursors by embedding attribution into platform design, prioritizing fluidity over static appendages.

Standards and Variations

Technical Conventions

Signature blocks in digital communications adhere to established protocols that ensure structured inclusion and verification, particularly in systems. The (), defined in RFC 2045 published in 1996, enables the creation of multipart messages for overall structure, supporting diverse content types like text or attachments; however, signature blocks are typically appended as to the message body, separated by a conventional such as "-- " to distinguish them from the main content. For enhanced security, (), outlined in RFC 8551, incorporates certificates to facilitate authenticated digital signatures on the entire message, binding the signer's identity to the content via for integrity and . These protocols allow the full message, including any embedded signature block, to be formatted as a signed object, verifiable by recipients using the associated certificate chains. To promote cross-platform , signature blocks are conventionally rendered in format, defaulting to ISO-8859-1 encoding to accommodate basic Latin characters and ensure compatibility across legacy and modern clients without requiring advanced rendering capabilities. In protocols like the (IMAP), as specified in RFC 9051, full messages—including embedded signature blocks—are retrieved from servers, with separation and management of signatures performed client-side by applications to maintain message integrity during access and synchronization. This approach avoids protocol-level alterations to signatures, relying instead on delimiters such as "-- " for identification, as established in conventions. Various tools facilitate the generation and automation of signature blocks, enhancing usability across environments. Open-source web applications, such as MySigMail, provide customizable templates for creating HTML-compatible signatures suitable for clients like and Outlook, emphasizing transparency and self-hosting options. Email clients like integrate built-in automation features, allowing users to define and automatically append signatures to outgoing messages through preferences, supporting both and rich formatting without external dependencies. Looking ahead, blockchain-based verifiable signatures have emerged post-2020 as a promising extension for , with prototypes like Chainmail enabling on-chain verification of signed messages to combat while preserving privacy through cryptographic proofs, though adoption remains limited due to integration challenges. Signature blocks, often abbreviated as "sig blocks" in , have long served as a creative outlet for personal expression, incorporating elements like , philosophical quotes, or humorous fortune cookie-style messages appended to posts and emails. This informal tradition, rooted in early online communities such as BBS systems and , contrasts sharply with more structured cultural norms elsewhere. In Japanese business communication, email signatures emphasize formality through the use of keigo (honorific language), including polite disclaimers that convey and , such as phrases acknowledging potential errors or requesting understanding for any shortcomings in the message. These elements reflect broader cultural values of and indirectness, often integrating the sender's full name, , and company details in a vertical format aligned with traditional letter-writing conventions. Post-2010, the inclusion of gender-neutral pronouns—such as "they/them"—in email signatures has emerged as a practice to promote inclusivity and signal respect for diverse gender identities, particularly in professional and organizational settings in Western contexts. This trend, which gained momentum around 2018, typically places pronouns alongside the sender's name to normalize their use and reduce misgendering in digital interactions. Legally, signature blocks carrying endorsements or promotional content must adhere to (FTC) guidelines to avoid liability for misleading information, as endorsements in —including those in emails—must be truthful and clearly disclose any material connections between the endorser and the product. For instance, if a signature promotes a product without proper disclosure, it could violate Section 5 of the FTC Act, leading to enforcement actions. Under the (CCPA) of 2018, signature blocks containing , such as contact details or affiliations, must consider data protection obligations, as businesses collecting such data from California residents are required to provide privacy notices and honor consumer rights like data access and deletion requests. Including disclaimers in signatures can help mitigate risks by informing recipients of data handling practices, though failure to comply may result in civil penalties up to $7,500 per intentional violation. Ethically, unsolicited signature blocks in commercial emails raise concerns about spam potential, as elements like hyperlinks or promotional text can trigger filters under the CAN-SPAM Act, which prohibits deceptive practices and requires accurate sender identification to prevent unwanted solicitations. Organizations must balance personalization with restraint to avoid contributing to inbox overload and user frustration. Accessibility remains a key ethical consideration, with signature blocks needing to comply with (WCAG) 2.2 principles to ensure usability by users; this includes using plain text for essential information, providing alt text for images, and avoiding complex layouts that could disrupt linear reading. Released in 2023, WCAG 2.2 builds on WCAG 2.1 (2018) and emphasizes perceivable and operable content, making it applicable to clients despite not being a web-specific standard. Globally, email signature norms differ between the and the , with certain EU member state commercial laws mandating inclusion of full company details—like registered and register number—in business communications for transparency, whereas U.S. practices vary by state and sector, often focusing on CAN-SPAM's requirement for a valid without uniform formality. These disparities can complicate multinational operations, as seen in post-2005 advertising lawsuits where misleading email content, including undisclosed promotions, led to class actions under consumer protection laws like Washington's Consumer Protection Act.

References

  1. https://www.ietf.org/rfc/rfc3676.txt
  2. https://tools.ietf.org/html/rfc1855
  3. http://www.catb.org/jargon/html/S/sig-block.html
  4. https://www.wordorigins.org/harmless-drudge/word-of-the-month-usenet
  5. https://learn.microsoft.com/en-us/exchange/policy-and-compliance/mail-flow-rules/signatures
  6. https://exclaimer.com/email-signature-handbook/email-disclaimer/
  7. https://www.oed.com/dictionary/signature-block_n
  8. https://www.roberthalf.com/us/en/insights/career-development/email-signature-etiquette-the-good-the-bad-and-the-unnecessary
  9. https://exclaimer.com/email-signature-handbook/gender-pronouns-in-email-signatures/
  10. https://www.mail-signatures.com/articles/email-signature-tips-create-good-signature-block/
  11. https://www.mail-signatures.com/articles/vcards-in-email-signatures/
  12. https://agoradigital.art/blog-art-101-the-infinite-life-of-ascii-art/
  13. https://www.sutisoft.com/blog/your-guide-to-signature-blocks-what-they-are-why-they-matter/
  14. https://writing.kemitchell.com/2021/08/25/Signature-Blocks-101
  15. https://www.adobe.com/acrobat/resources/signature-block.html
  16. https://learnsic.com/blog/email-signature-format-best-practices-and-tips-for-professional
  17. https://writemail.ai/how-to/the-ultimate-guide-to-creating-professional-email-signatures-that-make-an-impact
  18. https://stripo.email/blog/email-design-evolution-from-plain-text-to-interactive-emails/
  19. https://emailauth.io/blog/email-evolution
  20. https://www.jmu.edu/accessibility/digital-accessibility/guides/microsoft-office/outlook.shtml
  21. https://www.coloradovirtuallibrary.org/technology/accessibility/accessibility-quick-tip-how-to-ensure-your-email-communications-are-accessible-by-all/
  22. https://brewminate.com/bbs-a-history-of-social-media-before-social-media-since-1973/
  23. https://www.fidonet.org/inet92_Randy_Bush.txt
  24. http://ftsc.org/docs/fsc-0068.001
  25. https://www.livinginternet.com/u/ui_usenethist.htm
  26. https://smfr.org/mtnw/docs/Usenet.html
  27. https://www.ietf.org/rfc/rfc1855.txt
  28. https://www.linuxjournal.com/article/4500
  29. https://www.lsu.edu/internet/guides/zen/zen-1.0_5.html
  30. https://www.zdnet.com/article/the-rise-and-fall-of-usenet-how-the-original-social-media-platform-came-to-be/
  31. https://service.alaska.edu/TDClient/36/Portal/KB/ArticleDet?ID=146
  32. https://support.microsoft.com/en-us/office/create-and-add-an-email-signature-in-outlook-com-or-outlook-on-the-web-776d9006-abdf-444e-b5b7-a61821dff034
  33. https://kb.mozillazine.org/Signatures_-_Thunderbird
  34. https://datatracker.ietf.org/doc/html/rfc6350
  35. https://exclaimer.com/email-signature-handbook/how-to-fix-the-gmail-signature-too-long-error/
  36. https://www.mail-signatures.com/articles/problems-email-signatures-office-365/
  37. https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business
  38. https://knowledge.hubspot.com/marketing-email/edit-office-location-information-in-email-footers
  39. https://exclaimer.com/email-signature-handbook/the-17-email-signature-dos-and-donts/
  40. https://www.mailerlite.com/blog/email-signature-best-practices
  41. https://gpanel.io/blog/effective-company-email-signatures-in-google-workspace
  42. https://www.clio.com/blog/confidential-email-disclaimer/
  43. https://helpx.adobe.com/legal/esignatures/regulations/united-states.html
  44. https://www.gislason.com/i-agreed-to-what-emails-and-text-messages-as-electronic-signatures/
  45. https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation
  46. https://www.docusign.com/en-gb/products/electronic-signature/learn/eidas-regulation-primer
  47. https://exclaimer.com/blog/4-biggest-risks-of-non-compliant-email-signatures/
  48. https://exclaimer.com/blog/exchange-email-signature-management-se/
  49. https://www.codetwo.com/email-signatures/
  50. https://help.salesforce.com/s/articleView?id=mktg.mc_es_can_spam_requirements.htm&language=en_US&type=5
  51. https://www.vbulletin.com/docs/html/adding_or_editing_a_user
  52. https://www.phpbb.com/support/docs/en/3.2/ug/quickstart/settings_boardfeatures/
  53. https://stackoverflow.com/questions/3850043/storing-a-users-signature-in-mysql
  54. https://meta.discourse.org/t/discourse-signatures/42263
  55. https://meta.stackexchange.com/questions/28416/what-is-the-policy-on-signatures-and-links-in-answers
  56. https://webmasters.stackexchange.com/questions/32467/should-forum-signatures-be-statically-stored-with-the-post
  57. https://hypixel.net/threads/how-do-i-create-custom-forum-signatures.2645619/
  58. https://www.neogaf.com/threads/throwback-thread-forum-signatures-56k-warning-lol.1404477/
  59. https://meta.discourse.org/t/are-post-signatures-really-a-thing-of-the-past/307379
  60. https://www.mediawiki.org/wiki/Help:Signatures
  61. https://www.mediawiki.org/wiki/Manual:User_signatures
  62. https://datatracker.ietf.org/doc/html/rfc2045
  63. https://www.rfc-editor.org/rfc/rfc8551.html
  64. https://www.emailonacid.com/blog/article/email-development/the-importance-of-content-type-character-encoding-in-html-emails/
  65. https://datatracker.ietf.org/doc/html/rfc9051
  66. https://github.com/antonreshetov/mysigmail
  67. https://support.apple.com/guide/mail/change-signatures-settings-cpmlprefsig/mac
  68. https://www.circle.com/blog/chainmail-verifying-email-on-the-blockchain
  69. https://whitefiles.org/dta/pgs/n02_jargon_file.pdf
  70. https://www.pc-freak.net/files/the-new-hacker-dictionary-eric-raymond.pdf
  71. https://www.fluentu.com/blog/japanese/japanese-email-etiquette-format/
  72. https://cotoacademy.com/ultimate-guide-japanese-business-emails/
  73. https://gsignature.com/blog-post/email-signatures-in-intercultural-communication-japan
  74. https://www.codetwo.com/blog/using-gender-pronouns-in-email-signatures/
  75. https://medium.com/gender-inclusivit/why-i-put-pronouns-on-my-email-signature-and-linkedin-profile-and-you-should-too-d3dc942c8743
  76. https://www.ftc.gov/sites/default/files/attachments/press-releases/ftc-publishes-final-guides-governing-endorsements-testimonials/091005revisedendorsementguides.pdf
  77. https://www.ecfr.gov/current/title-16/chapter-I/subchapter-B/part-255
  78. https://www.federalregister.gov/documents/2023/07/26/2023-14795/guides-concerning-the-use-of-endorsements-and-testimonials-in-advertising
  79. https://www.mail-signatures.com/articles/email-signatures-vs-spam/
  80. https://exclaimer.com/blog/10-common-email-signature-mistakes/
  81. https://www.w3.org/TR/WCAG22/
  82. https://www.hyphadev.io/blog/accessible-email-signature
  83. https://accessibility.huit.harvard.edu/creating-accessible-emails
  84. https://exclaimer.com/blog/email-signature-compliance-what-it-and-legal-teams-need-to-know/
  85. https://signandgo.io/blog/navigating-the-global-maze-a-guide-to-email-signature-legal-requirements-for-multinational-businesses/
  86. https://www.klgates.com/Washington-Supreme-Court-Increases-Risks-of-Lawsuits-for-False-or-Misleading-Email-Subject-Lines-8-7-2025
Add your contribution
Related Hubs
User Avatar
No comments yet.