A.3. COMPLETE HEADERS

A.3.1. Minimum required

  Date:     26 Aug 76 1429 EDT        Date:     26 Aug 76 1429 EDT
  From:     Jones@Registry.Org   or   From:     Jones@Registry.Org
  Bcc:                                To:       Smith@Registry.Org

Note that the "Bcc" field may be empty, while the "To" field is required to have at least one address.

A.3.2. Using some of the additional fields

  Date:     26 Aug 76 1430 EDT
  From:     George Jones<Group@Host>
  Sender:   Secy@SHOST
  To:       "Al Neuman"@Mad-Host,
            Sam.Irving@Other-Host
  Message-ID:  <some.string@SHOST>

A.3.3. About as complex as you're going to get

  Date     :  27 Aug 76 0932 PDT
  From     :  Ken Davis <KDavis@This-Host.This-net>
  Subject  :  Re: The Syntax in the RFC
  Sender   :  KSecy@Other-Host
  Reply-To :  Sam.Irving@Reg.Organization
  To       :  George Jones <Group@Some-Reg.An-Org>,
              Al.Neuman@MAD.Publisher
  cc       :  Important folk:
                Tom Softwood <Balsa@Tree.Root>,
                "Sam Irving"@Other-Host;,
              Standard Distribution:
                /main/davis/people/standard@Other-Host,
                "<Jones>standard.dist.3"@Tops-20-Host>;
  Comment  :  Sam is away on business. He asked me to handle
              his mail for him.  He'll be able to provide  a
              more  accurate  explanation  when  he  returns
              next week.
  In-Reply-To: <some.string@DBM.Group>, George's message
  X-Special-action:  This is a sample of user-defined field-names.
              There could also be a field-name
              "Special-action", but its name might later be
              preempted
  Message-ID: <4231.629.XYzi-What@Other-Host>