MailMan uses CGI to communicate with the host web server.
For more information about CGI, consult Nick Kew's CGI FAQ
at
<URL:http://www3.pair.com/webthing/docs/cgi/faqs/cgifaq.shtm
l>.

For the generation of HTTP headers, MailMan conforms as
closely as possible with the proposed standard RFC 2068,
"Hypertext Transfer Protocol -- HTTP/1.1", as well as the
earlier related specifications such as RFC 1945, "Hypertext
Transfer Protocol -- HTTP/1.0."

MailMan's user interface is generated using messages that
comply as closely as possible with RFC 1866, "HyperText
Markup Language Specification - 2.0" and related
specifications.

Persistent state information for the frames-based MailMan
interface is maintained according to RFC 2109, "HTTP State
Management Mechanism".

For communication with incoming internet email servers,
MailMan conforms as closely as possible with RFC 1939, "Post
Office Protocol - Version 3", and was originally based on
the earlier specification, RFC 1725.  MailMan is in strict
compliance with end of line delimiters specified in the POP3
standards documents and should be compatible with POP3
servers regardless of the end of line delimiter used in the
server's host operating system.

For communication with outgoing internet email servers,
MailMan conforms as closely as possible with RFC 821,
"Simple Mail Transfer Protocol".  MailMan does not make use
of enhancements provided by later approved extension
standards such as RFC 1869 or RFC 1870.

The messages that MailMan processes and generates are
compliant as closely as possible with RFC 822, "Standard for
the format of ARPA Internet text messages".  Formatted
messages and messages with attachments are automatically
handled by portions of MailMan which are compliant as
closely as possible with the specifications in RFC 2045, RFC
2046, RFC 2047, RFC 2048 and RFC 2049, "Multipurpose
Internet Mail Extensions (MIME)", parts one through five.

All of the above referenced standards documents are
available at <URL:http://www.ietf.org>.