Conformity
----------

   No rebels without a clue here, ma'am.  We conform to all standards
known to (wo)man.  Except for those standards and/or conventions we
disagree with, of course.

*RFC 822*
     There are no known breaches of this standard.

*RFC 1036*
     There are no known breaches of this standard, either.

*Usenet Seal of Approval*
     Gnus hasn't been formally through the Seal process, but I have read
     through the Seal text and I think Gnus would pass.

*Son-of-RFC 1036*
     We do have some breaches to this one.

    *MIME*
          Gnus does no MIME handling, and this standard-to-be seems to
          think that MIME is the bees' knees, so we have major breakage
          here.

    *X-Newsreader*
          This is considered to be a "vanity header", while I consider
          it to be consumer information.  After seeing so many badly
          formatted articles coming from `tin' and `Netscape' I know
          not to use either of those for posting articles.  I would not
          have known that if it wasn't for the `X-Newsreader' header.

    *References*
          Gnus does line breaking on this header.  I infer from RFC1036
          that being conservative in what you output is not creating
          5000-character lines, so it seems like a good idea to me.
          However, this standard-to-be says that whitespace in the
          `References' header is to be preserved, so...  It doesn't
          matter one way or the other to Gnus, so if somebody tells me
          what The Way is, I'll change it.  Or not.

   If you ever notice Gnus acting non-compliantly with regards to the
texts mentioned above, don't hesitate to drop a note to Gnus Towers and
let us know.