Reinstate some changes to make latexpdf work.
* message.texi (Security): Don't use @key.
(Various Commands): Don't use @point.
* gnus.texi (Mail Source Specifiers): Use @uref.
2002-02-13 Jesper Harder <harder@ifa.au.dk>
* message.texi, gnus.texi, emacs-mime.texi: Use small caps
consistently. MIME, NOV, NNTP, HTML, IMAP are written with @sc
most places -- it looks better if it's the same *everywhere*.
@kbd instead of @code for key sequences. @file instead of @code
for files.
* message.texi (Various Commands): use the proper @point glyph.
* gnus.texi (Summary Mail Commands): \e,A_\e(B doesn't work. A German
spelling reform changed the correct spelling to "muss" anyway (I
think).
* gnus.texi (Mail sources): \e,A'\e(B doesn't work. Use "section" instead.
* gnus.texi (Mail Source Specifiers): use @url.
* message.texi, emacs-mime.texi: update copyright year.
+2002-02-13 ShengHuo ZHU <zsh@cs.rochester.edu>
+
+ Reinstate some changes to make latexpdf work.
+
+ * message.texi (Security): Don't use @key.
+ (Various Commands): Don't use @point.
+
+ * gnus.texi (Mail Source Specifiers): Use @uref.
+
+2002-02-13 Jesper Harder <harder@ifa.au.dk>
+
+ * message.texi, gnus.texi, emacs-mime.texi: Use small caps
+ consistently. MIME, NOV, NNTP, HTML, IMAP are written with @sc
+ most places -- it looks better if it's the same *everywhere*.
+ @kbd instead of @code for key sequences. @file instead of @code
+ for files.
+
+ * message.texi (Various Commands): use the proper @point glyph.
+
+ * gnus.texi (Summary Mail Commands): \e,A_\e(B doesn't work. A German
+ spelling reform changed the correct spelling to "muss" anyway (I
+ think).
+
+ * gnus.texi (Mail sources): \e,A'\e(B doesn't work. Use "section" instead.
+
+ * gnus.texi (Mail Source Specifiers): use @url.
+
+ * message.texi, emacs-mime.texi: update copyright year.
+
2002-02-12 Paul Jarc <prj@po.cwru.edu>
* gnus.texi (Required Back End Functions): specify the lowest and
@page
@vskip 0pt plus 1filll
-Copyright @copyright{} 1998, 1999, 2000 Free Software Foundation, Inc.
+Copyright @copyright{} 1998, 1999, 2000, 2001, 2002 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.1 or
* Interface Functions:: An abstraction over the basic functions.
* Basic Functions:: Utility and basic parsing functions.
* Decoding and Viewing:: A framework for decoding and viewing.
-* Composing:: MML; a language for describing MIME parts.
+* Composing:: MML; a language for describing @sc{mime} parts.
* Standards:: A summary of RFCs and working documents used.
* Index:: Function and variable index.
@end menu
library, one must choose between the old version of the library and the
new version of the library.
-The Emacs MIME library takes a different tack. It defines a series of
-low-level libraries (@file{rfc2047.el}, @file{rfc2231.el} and so on)
-that parses strictly according to the corresponding standard. However,
-normal programs would not use the functions provided by these libraries
-directly, but instead use the functions provided by the
-@code{mail-parse} library. The functions in this library are just
-aliases to the corresponding functions in the latest low-level
-libraries. Using this scheme, programs get a consistent interface they
-can use, and library developers are free to create write code that
-handles new standards.
+The Emacs @sc{mime} library takes a different tack. It defines a
+series of low-level libraries (@file{rfc2047.el}, @file{rfc2231.el}
+and so on) that parses strictly according to the corresponding
+standard. However, normal programs would not use the functions
+provided by these libraries directly, but instead use the functions
+provided by the @code{mail-parse} library. The functions in this
+library are just aliases to the corresponding functions in the latest
+low-level libraries. Using this scheme, programs get a consistent
+interface they can use, and library developers are free to create
+write code that handles new standards.
The following functions are defined by this library:
@node Non-MIME
@section Non-MIME
-Gnus also understands some non-MIME attachments, such as postscript,
-uuencode, binhex, shar, forward, gnatsweb, pgp. Each of these features
-can be disabled by add an item into @code{mm-uu-configure-list}.
-For example,
+Gnus also understands some non-@sc{mime} attachments, such as
+postscript, uuencode, binhex, shar, forward, gnatsweb, pgp. Each of
+these features can be disabled by add an item into
+@code{mm-uu-configure-list}. For example,
@lisp
(require 'mm-uu)
@item mm-inline-text-html-renderer
@findex mm-inline-text-html-render-with-w3
@findex mm-inline-text-html-render-with-w3m
-This function will be used to convert the HTML to the text. There are
+This function will be used to convert the @sc{html} to the text. There are
two pre-defined functions: @code{mm-inline-text-html-render-with-w3},
which uses Emacs/w3; and @code{mm-inline-text-html-render-with-w3m},
which uses emacs-w3m (see @uref{http://emacs-w3m.namazu.org/} for more
-information about emacs-w3m). The function will be called with a MIME
-handle as the argument.
+information about emacs-w3m). The function will be called with a
+@sc{mime} handle as the argument.
@item mm-inline-text-html-with-images
-Some HTML mails might have the trick of spammers using @samp{<img>} tags.
-It is likely to be intended to verify whether you have read the mail.
-You can prevent your personal informations from leaking by setting this
-option to @code{nil} (which is the default). It is currently ignored by
-Emacs/w3. For emacs-w3m, you may use the command @kbd{t} on the image
-anchor to show an image even if it is @code{nil}.@footnote{The command
-@kbd{T} will load all images. If you have set the option
-@code{w3m-key-binding} to @code{info}, use @kbd{i} or @kbd{I} instead.}
+Some @sc{html} mails might have the trick of spammers using
+@samp{<img>} tags. It is likely to be intended to verify whether you
+have read the mail. You can prevent your personal informations from
+leaking by setting this option to @code{nil} (which is the default).
+It is currently ignored by Emacs/w3. For emacs-w3m, you may use the
+command @kbd{t} on the image anchor to show an image even if it is
+@code{nil}.@footnote{The command @kbd{T} will load all images. If you
+have set the option @code{w3m-key-binding} to @code{info}, use @kbd{i}
+or @kbd{I} instead.}
@item mm-inline-text-html-with-w3m-keymap
You can use emacs-w3m command keys in the inlined text/html part by
* Simple MML Example:: An example MML document.
* MML Definition:: All valid MML elements.
* Advanced MML Example:: Another example MML document.
-* Charset Translation:: How charsets are mapped from @sc{mule} to MIME.
+* Charset Translation:: How charsets are mapped from @sc{mule} to @sc{mime}.
* Conversion:: Going from @sc{mime} to MML and vice versa.
* Flowed text:: Soft and hard newlines.
@end menu
Conformance Criteria and Examples
@item RFC2231
-MIME Parameter Value and Encoded Word Extensions: Character Sets,
+@sc{mime} Parameter Value and Encoded Word Extensions: Character Sets,
Languages, and Continuations
@item RFC1843
Draft for the successor of RFC822
@item RFC2112
-The MIME Multipart/Related Content-type
+The @sc{mime} Multipart/Related Content-type
@item RFC1892
The Multipart/Report Content Type for the Reporting of Mail System
Estimated total number of articles. (This is really @var{max-number}
minus @var{min-number} plus 1.)
-Gnus uses this estimation because the NNTP protocol provides efficient
-access to @var{max-number} and @var{min-number} but getting the true
-unread message count is not possible efficiently. For hysterical
-raisins, even the mail back ends, where the true number of unread
-messages might be available efficiently, use the same limited
-interface. To remove this restriction from Gnus means that the
-back end interface has to be changed, which is not an easy job. If you
+Gnus uses this estimation because the @sc{nntp} protocol provides
+efficient access to @var{max-number} and @var{min-number} but getting
+the true unread message count is not possible efficiently. For
+hysterical raisins, even the mail back ends, where the true number of
+unread messages might be available efficiently, use the same limited
+interface. To remove this restriction from Gnus means that the back
+end interface has to be changed, which is not an easy job. If you
want to work on this, please contact the Gnus mailing list.
@item y
is forwarded according to the value of (@code{message-forward-as-mime})
and (@code{message-forward-show-mml}); if the prefix is 1, decode the
message and forward directly inline; if the prefix is 2, forward message
-as an rfc822 MIME section; if the prefix is 3, decode message and
-forward as an rfc822 MIME section; if the prefix is 4, forward message
+as an rfc822 @sc{mime} section; if the prefix is 3, decode message and
+forward as an rfc822 @sc{mime} section; if the prefix is 4, forward message
directly inline; otherwise, the message is forwarded as no prefix given
but use the flipped value of (@code{message-forward-as-mime}). By
-default, the message is decoded and forwarded as an rfc822 MIME section.
+default, the message is decoded and forwarded as an rfc822 @sc{mime}
+section.
@item S m
@itemx m
ship a mail to a different account of yours. (If you're both
@code{root} and @code{postmaster} and get a mail for @code{postmaster}
to the @code{root} account, you may want to resend it to
-@code{postmaster}. Ordnung muß sein!
+@code{postmaster}. Ordnung muss sein!
This command understands the process/prefix convention
(@pxref{Process/Prefix}).
of (@code{message-forward-as-mime}) and
(@code{message-forward-show-mml}); if the prefix is 1, decode the
message and forward directly inline; if the prefix is 2, forward message
-as an rfc822 MIME section; if the prefix is 3, decode message and
-forward as an rfc822 MIME section; if the prefix is 4, forward message
+as an rfc822 @sc{mime} section; if the prefix is 3, decode message and
+forward as an rfc822 @sc{mime} section; if the prefix is 4, forward message
directly inline; otherwise, the message is forwarded as no prefix given
but use the flipped value of (@code{message-forward-as-mime}). By
-default, the message is decoded and forwarded as an rfc822 MIME section.
+default, the message is decoded and forwarded as an rfc822 @sc{mime} section.
@item S O p
@kindex S O p (Summary)
@item W h
@kindex W h (Summary)
@findex gnus-article-wash-html
-Treat HTML (@code{gnus-article-wash-html}). Note that the this is
+Treat @sc{html} (@code{gnus-article-wash-html}). Note that the this is
usually done automatically by Gnus if the message in question has a
-@code{Content-Type} header that says that the message is HTML.
+@code{Content-Type} header that says that the message is @sc{html}.
If a prefix is given, a charset will be asked for.
@vindex gnus-article-wash-function
-The default is to use w3 to convert the HTML, but this is controlled
-by the @code{gnus-article-wash-function} variable. Pre-defined
-functions you can use include:
+The default is to use w3 to convert the @sc{html}, but this is
+controlled by the @code{gnus-article-wash-function} variable.
+Pre-defined functions you can use include:
@table @code
@item gnus-article-wash-html-with-w3
@item W s
@kindex W s (Summary)
@findex gnus-summary-force-verify-and-decrypt
-Verify a signed (PGP, PGP/MIME or S/MIME) message
+Verify a signed (PGP, @sc{pgp/mime} or @sc{s/mime}) message
(@code{gnus-summary-force-verify-and-decrypt}). @xref{Security}.
@item W W H
This command looks in the @code{Content-Type} header to determine the
charset. If there is no such header in the article, you can give it a
prefix, which will prompt for the charset to decode as. In regional
-groups where people post using some common encoding (but do not include
-MIME headers), you can set the @code{charset} group/topic parameter to
-the required charset (@pxref{Group Parameters}).
+groups where people post using some common encoding (but do not
+include @sc{mime} headers), you can set the @code{charset} group/topic
+parameter to the required charset (@pxref{Group Parameters}).
@item W M v
@kindex W M v (Summary)
@section Security
Gnus is able to verify signed messages or decrypt encrypted messages.
-The formats that are supported are PGP, PGP/MIME and S/MIME, however
-you need some external programs to get things to work:
+The formats that are supported are PGP, @sc{pgp/mime} and @sc{s/mime},
+however you need some external programs to get things to work:
@enumerate
@item
well as a OpenPGP implementation (such as GnuPG).
@item
-To handle S/MIME message, you need to install OpenSSL. OpenSSL 0.9.6
+To handle @sc{s/mime} message, you need to install OpenSSL. OpenSSL 0.9.6
or newer is recommended.
@end enumerate
@end table
Gnus will display some @sc{mime} objects automatically. The way Gnus
-determines which parts to do this with is described in the Emacs MIME
-manual.
+determines which parts to do this with is described in the Emacs
+@sc{mime} manual.
It might be best to just use the toggling functions from the article
buffer to avoid getting nasty surprises. (For instance, you enter the
@cindex using smime
Gnus can digitally sign and encrypt your messages, using vanilla PGP
-format or PGP/MIME or S/MIME. For decoding such messages, see the
-@code{mm-verify-option} and @code{mm-decrypt-option} options
+format or @sc{pgp/mime} or @sc{s/mime}. For decoding such messages,
+see the @code{mm-verify-option} and @code{mm-decrypt-option} options
(@pxref{Security}).
For PGP, Gnus supports two external libraries, @sc{gpg.el} and
-@sc{Mailcrypt}, you need to install at least one of them. The S/MIME
-support in Gnus requires the external program OpenSSL.
+@sc{Mailcrypt}, you need to install at least one of them. The
+@sc{s/mime} support in Gnus requires the external program OpenSSL.
-Instructing MML to perform security operations on a MIME part is done
-using the @code{C-c C-m s} key map for signing and the @code{C-c C-m
-c} key map for encryption, as follows.
+Instructing MML to perform security operations on a @sc{mime} part is
+done using the @kbd{C-c C-m s} key map for signing and the @kbd{C-c
+C-m c} key map for encryption, as follows.
@table @kbd
@kindex C-c C-m s s
@findex mml-secure-sign-smime
-Digitally sign current MIME part using S/MIME.
+Digitally sign current @sc{mime} part using @sc{s/mime}.
@item C-c C-m s o
@kindex C-c C-m s o
@findex mml-secure-sign-pgp
-Digitally sign current MIME part using PGP.
+Digitally sign current @sc{mime} part using PGP.
@item C-c C-m s p
@kindex C-c C-m s p
@findex mml-secure-sign-pgp
-Digitally sign current MIME part using PGP/MIME.
+Digitally sign current @sc{mime} part using @sc{pgp/mime}.
@item C-c C-m c s
@kindex C-c C-m c s
@findex mml-secure-encrypt-smime
-Digitally encrypt current MIME part using S/MIME.
+Digitally encrypt current @sc{mime} part using @sc{s/mime}.
@item C-c C-m c o
@kindex C-c C-m c o
@findex mml-secure-encrypt-pgp
-Digitally encrypt current MIME part using PGP.
+Digitally encrypt current @sc{mime} part using PGP.
@item C-c C-m c p
@kindex C-c C-m c p
@findex mml-secure-encrypt-pgpmime
-Digitally encrypt current MIME part using PGP/MIME.
+Digitally encrypt current @sc{mime} part using @sc{pgp/mime}.
@end table
sometimes peek in your mailbox with a @sc{imap} client and mark some
articles as read (or; SEEN) you might want to set this to @samp{nil}.
Then all articles in the mailbox is fetched, no matter what. For a
-complete list of predicates, see RFC 2060 §6.4.4.
+complete list of predicates, see RFC 2060 section 6.4.4.
@item :fetchflag
How to flag fetched articles on the server, the default @samp{\Deleted}
will mark them as deleted, an alternative would be @samp{\Seen} which
would simply mark them as read. These are the two most likely choices,
-but more flags are defined in RFC 2060 §2.3.2.
+but more flags are defined in RFC 2060 section 2.3.2.
@item :dontexpunge
If non-nil, don't remove all articles marked as deleted in the mailbox
@end lisp
@item webmail
-Get mail from a webmail server, such as www.hotmail.com,
-webmail.netscape.com, www.netaddress.com, www.my-deja.com.
+Get mail from a webmail server, such as @uref{www.hotmail.com},
+@uref{webmail.netscape.com}, @uref{www.netaddress.com},
+@uref{www.my-deja.com}.
-NOTE: Now mail.yahoo.com provides POP3 service, so @sc{pop} mail source
+NOTE: Now @uref{mail.yahoo.com} provides POP3 service, so @sc{pop} mail source
is suggested.
NOTE: Webmail largely depends cookies. A "one-line-cookie" patch is
restoring a group while preserving marks is fairly simple.
(Preserving the group level and group parameters as well still
-requires ritual dancing and sacrifices to the @code{.newsrc.eld} deity
+requires ritual dancing and sacrifices to the @file{.newsrc.eld} deity
though.)
To archive an entire @code{nnml} or @code{nnfolder} server, take a
It is also possible to archive individual @code{nnml} or
@code{nnfolder} groups, while preserving marks. For @code{nnml}, you
copy all files in the group's directory. For @code{nnfolder} you need
-to copy both the base folder file itself (@code{FOO}, say), and the
-marks file (@code{FOO.mrk} in this example). Restoring the group is
+to copy both the base folder file itself (@file{FOO}, say), and the
+marks file (@file{FOO.mrk} in this example). Restoring the group is
done with @kbd{G m} from the Group buffer. The last step makes Gnus
notice the new directory.
@vindex nnimap-stream
The type of stream used to connect to your server. By default, nnimap
will detect and automatically use all of the below, with the exception
-of SSL/TLS. (IMAP over SSL/TLS is being replaced by STARTTLS, which
+of SSL/TLS. (@sc{imap} over SSL/TLS is being replaced by STARTTLS, which
can be automatically detected, but it's not widely deployed yet.)
Example server specification:
1.5.x and 1.6.x) you need to frob @code{imap-process-connection-type}
to make @code{imap.el} use a pty instead of a pipe when communicating
with @samp{imtest}. You will then suffer from a line length
-restrictions on IMAP commands, which might make Gnus seem to hang
+restrictions on @sc{imap} commands, which might make Gnus seem to hang
indefinitely if you have many articles in a mailbox. The variable
@code{imap-kerberos4-program} contain parameters to pass to the imtest
program.
@item nnimap-importantize-dormant
@vindex nnimap-importantize-dormant
-If non-nil, marks dormant articles as ticked (as well), for other IMAP
-clients. Within Gnus, dormant articles will naturally still (only) be
-marked as ticked. This is to make dormant articles stand out, just
-like ticked articles, in other IMAP clients. (In other words, Gnus has
-two ``Tick'' marks and IMAP has only one.)
+If non-nil, marks dormant articles as ticked (as well), for other
+@sc{imap} clients. Within Gnus, dormant articles will naturally still
+(only) be marked as ticked. This is to make dormant articles stand
+out, just like ticked articles, in other @sc{imap} clients. (In other
+words, Gnus has two ``Tick'' marks and @sc{imap} has only one.)
Probably the only reason for frobing this would be if you're trying
enable per-user persistant dormant flags, using something like:
@cindex Expunging
@vindex nnimap-expunge-search-string
-This variable contain the IMAP search command sent to server when
+This variable contain the @sc{imap} search command sent to server when
searching for articles eligible for expiring. The default is
@code{"UID %s NOT SINCE %s"}, where the first @code{%s} is replaced by
UID set and the second @code{%s} is replaced by a date.
Netscape mail boxes.
@item mime-parts
-MIME multipart messages.
+@sc{mime} multipart messages.
@item standard-digest
The standard (RFC 1153) digest format.
@item mime-digest
-A MIME digest of messages.
+A @sc{mime} digest of messages.
@item lanl-gov-announce
Announcement messages from LANL Gov Announce.
@item gnus-agent-cache
@vindex gnus-agent-cache
-Variable to control whether use the locally stored NOV and articles when
+Variable to control whether use the locally stored @sc{nov} and articles when
plugged.
@item gnus-agent-go-online
@item e
Score on an "extra" header, that is, one of those in gnus-extra-headers,
-if your NNTP server tracks additional header data in overviews.
+if your @sc{nntp} server tracks additional header data in overviews.
@item f
Score on followups---this matches the author name, and adds scores to
case, there is a 5th element in the score entry, being the name of the
header to be scored. The following entry is useful in your
@file{all.SCORE} file in case of spam attacks from a single origin host,
-if your NNTP server tracks NNTP-Posting-Host in overviews:
+if your @sc{nntp} server tracks NNTP-Posting-Host in overviews:
@lisp
("111.222.333.444" -1000 nil s "NNTP-Posting-Host")
@item MIME - RFC 2045-2049 etc
@cindex MIME
-All the various MIME RFCs are supported.
+All the various @sc{mime} RFCs are supported.
@item Disposition Notifications - RFC 2298
Message Mode is able to request notifications from the receiver.
@cindex RFC 2440
RFC 1991 is the original PGP message specification, published as a
Information RFC. RFC 2440 was the follow-up, now called Open PGP, and
-put on the Standards Track. Both document a non-MIME aware PGP
+put on the Standards Track. Both document a non-@sc{mime} aware PGP
format. Gnus supports both encoding (signing and encryption) and
decoding (verification and decryption).
@item PGP/MIME - RFC 2015/3156
RFC 2015 (superceded by 3156 which references RFC 2440 instead of RFC
-1991) describes the MIME-wrapping around the RF 1991/2440 format.
+1991) describes the @sc{mime}-wrapping around the RF 1991/2440 format.
Gnus supports both encoding and decoding.
@item S/MIME - RFC 2633
-RFC 2633 describes the S/MIME format.
+RFC 2633 describes the @sc{s/mime} format.
@item IMAP - RFC 1730/2060, RFC 2195, RFC 2086, RFC 2359, RFC 2595, RFC 1731
-RFC 1730 is IMAP version 4, updated somewhat by RFC 2060 (IMAP 4
-revision 1). RFC 2195 describes CRAM-MD5 authentication for IMAP. RFC
-2086 describes access control lists (ACLs) for IMAP. RFC 2359
-describes a IMAP protocol enhancement. RFC 2595 describes the proper
-TLS integration (STARTTLS) with IMAP. RFC 1731 describes the
-GSSAPI/Kerberos4 mechanisms for IMAP.
+RFC 1730 is @sc{imap} version 4, updated somewhat by RFC 2060 (@sc{imap} 4
+revision 1). RFC 2195 describes CRAM-MD5 authentication for @sc{imap}. RFC
+2086 describes access control lists (ACLs) for @sc{imap}. RFC 2359
+describes a @sc{imap} protocol enhancement. RFC 2595 describes the proper
+TLS integration (STARTTLS) with @sc{imap}. RFC 1731 describes the
+GSSAPI/Kerberos4 mechanisms for @sc{imap}.
@end table
Getting Mail -> Mail Sources
@item
-Gnus is now a MIME-capable reader. This affects many parts of
+Gnus is now a @sc{mime}-capable reader. This affects many parts of
Gnus, and adds a slew of new commands. See the manual for details.
@item
@item
The user can now decide which extra headers should be included in
-summary buffers and NOV files.
+summary buffers and @sc{nov} files.
@item
@code{gnus-article-display-hook} has been removed. Instead, a number
again, to keep up with ever-changing layouts.
@item
-Gnus can now read IMAP mail via @code{nnimap}.
+Gnus can now read @sc{imap} mail via @code{nnimap}.
@end itemize
sequences (lists) of article numbers, and most back ends do not support
retrieval of @code{Message-ID}s. But they should try for both.
-The result data should either be HEADs or NOV lines, and the result
+The result data should either be HEADs or @sc{nov} lines, and the result
value should either be @code{headers} or @code{nov} to reflect this.
This might later be expanded to @code{various}, which will be a mixture
-of HEADs and NOV lines, but this is currently not supported by Gnus.
+of HEADs and @sc{nov} lines, but this is currently not supported by Gnus.
If @var{fetch-old} is non-@code{nil} it says to try fetching "extra
headers", in some meaning of the word. This is generally done by
@page
@vskip 0pt plus 1filll
-Copyright @copyright{} 1996, 1997, 1998, 1999, 2000
+Copyright @copyright{} 1996, 1997, 1998, 1999, 2000, 2001, 2002
Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
@item message-forward-as-mime
@vindex message-forward-as-mime
If this variable is @code{t} (the default), forwarded messages are
-included as inline MIME RFC822 parts. If it's @code{nil}, forwarded
+included as inline @sc{mime} RFC822 parts. If it's @code{nil}, forwarded
messages will just be copied inline to the new message, like previous,
-non MIME-savvy versions of gnus would do.
+non @sc{mime}-savvy versions of gnus would do.
@end table
The most typical thing users want to use the multipart things in
@sc{mime} for is to add ``attachments'' to mail they send out. This can
-be done with the @code{C-c C-a} command, which will prompt for a file
+be done with the @kbd{C-c C-a} command, which will prompt for a file
name and a @sc{mime} type.
You can also create arbitrarily complex multiparts using the MML
Using the MML language, Message is able to create digitally signed and
digitally encrypted messages. Message (or rather MML) currently
-support PGP (RFC 1991), PGP/MIME (RFC 2015/3156) and S/MIME.
-Instructing MML to perform security operations on a MIME part is done
-using the @code{C-c C-m s} key map for signing and the @code{C-c C-m
-c} key map for encryption, as follows.
+support PGP (RFC 1991), @sc{pgp/mime} (RFC 2015/3156) and @sc{s/mime}.
+Instructing MML to perform security operations on a @sc{mime} part is
+done using the @kbd{C-c C-m s} key map for signing and the @kbd{C-c
+C-m c} key map for encryption, as follows.
@table @kbd
@kindex C-c C-m s s
@findex mml-secure-message-sign-smime
-Digitally sign current message using S/MIME.
+Digitally sign current message using @sc{s/mime}.
@item C-c C-m s o
@kindex C-c C-m s o
@kindex C-c C-m s p
@findex mml-secure-message-sign-pgp
-Digitally sign current message using PGP/MIME.
+Digitally sign current message using @sc{pgp/mime}.
@item C-c C-m c s
@kindex C-c C-m c s
@findex mml-secure-message-encrypt-smime
-Digitally encrypt current message using S/MIME.
+Digitally encrypt current message using @sc{s/mime}.
@item C-c C-m c o
@kindex C-c C-m c o
@kindex C-c C-m c p
@findex mml-secure-message-encrypt-pgpmime
-Digitally encrypt current message using PGP/MIME.
+Digitally encrypt current message using @sc{pgp/mime}.
@end table
These commands do not immediately sign or encrypt the message, they
merely insert the proper MML secure tag to instruct the MML engine to
perform that operation when the message is actually sent. They may
-perform other operations too, such as locating and retrieving a S/MIME
-certificate of the person you wish to send encrypted mail to. When the
-mml parsing engine converts your MML into a properly encoded MIME
-message, the secure tag will be replaced with either a part or a
-multipart tag. If your message contains other mml parts, a multipart
-tag will be used; if no other parts are present in your message a single
-part tag will be used. This way, message mode will do the Right Thing
-(TM) with signed/encrypted multipart messages.
+perform other operations too, such as locating and retrieving a
+@sc{s/mime} certificate of the person you wish to send encrypted mail
+to. When the mml parsing engine converts your MML into a properly
+encoded @sc{mime} message, the secure tag will be replaced with either
+a part or a multipart tag. If your message contains other mml parts,
+a multipart tag will be used; if no other parts are present in your
+message a single part tag will be used. This way, message mode will
+do the Right Thing (TM) with signed/encrypted multipart messages.
Since signing and especially encryption often is used when sensitive
information is sent, you may want to have some way to ensure that your
mail is actually signed or encrypted. After invoking the above
sign/encrypt commands, it is possible to preview the raw article by
-using @code{C-u C-m P} (@code{mml-preview}). Then you can verify that
-your long rant about what your ex-significant other or whomever actually
-did with that funny looking person at that strange party the other
-night, actually will be sent encrypted.
+using @kbd{C-u C-c RET P} (@code{mml-preview}). Then you can
+verify that your long rant about what your ex-significant other or
+whomever actually did with that funny looking person at that strange
+party the other night, actually will be sent encrypted.
-@emph{Note!} Neither PGP/MIME nor S/MIME encrypt/signs RFC822 headers.
-They only operate on the MIME object. Keep this in mind before sending
-mail with a sensitive Subject line.
+@emph{Note!} Neither @sc{pgp/mime} nor @sc{s/mime} encrypt/signs
+RFC822 headers. They only operate on the @sc{mime} object. Keep this
+in mind before sending mail with a sensitive Subject line.
Actually using the security commands above is not very difficult. At
least not compared with making sure all involved programs talk with each
@subsection Using S/MIME
@emph{Note!} This section assume you have a basic familiarity with
-modern cryptography, S/MIME, various PKCS standards, OpenSSL and so on.
-
-The S/MIME support in Message (and MML) require OpenSSL. OpenSSL
-perform the actual S/MIME sign/encrypt operations. OpenSSL can be found
-at @uref{http://www.openssl.org/}. OpenSSL 0.9.6 and later should work.
-Version 0.9.5a cannot extract mail addresses from certificates, and it
-insert a spurious CR character into MIME separators so you may wish to
-avoid it if you would like to avoid being regarded as someone who send
-strange mail. (Although by sending S/MIME messages you've probably
-already lost that contest.)
+modern cryptography, @sc{s/mime}, various PKCS standards, OpenSSL and
+so on.
+
+The @sc{s/mime} support in Message (and MML) require OpenSSL. OpenSSL
+perform the actual @sc{s/mime} sign/encrypt operations. OpenSSL can
+be found at @uref{http://www.openssl.org/}. OpenSSL 0.9.6 and later
+should work. Version 0.9.5a cannot extract mail addresses from
+certificates, and it insert a spurious CR character into @sc{mime}
+separators so you may wish to avoid it if you would like to avoid
+being regarded as someone who send strange mail. (Although by sending
+@sc{s/mime} messages you've probably already lost that contest.)
To be able to send encrypted mail, a personal certificate is not
required. Message (MML) need a certificate for the person to whom you
wish to communicate with though. You're asked for this when you type
-@code{C-c C-m c s}. Currently there are two ways to retrieve this
-certificate, from a local file or from DNS. If you chose a local file,
-it need to contain a X.509 certificate in PEM format. If you chose DNS,
-you're asked for the domain name where the certificate is stored, the
-default is a good guess. To my belief, Message (MML) is the first mail
-agent in the world to support retrieving S/MIME certificates from DNS,
-so you're not likely to find very many certificates out there. At least
-there should be one, stored at the domain @code{simon.josefsson.org}.
-LDAP is a more popular method of distributing certificates, support for
-it is planned. (Meanwhile, you can use @code{ldapsearch} from the
-command line to retrieve a certificate into a file and use it.)
+@kbd{C-c C-m c s}. Currently there are two ways to retrieve this
+certificate, from a local file or from DNS. If you chose a local
+file, it need to contain a X.509 certificate in PEM format. If you
+chose DNS, you're asked for the domain name where the certificate is
+stored, the default is a good guess. To my belief, Message (MML) is
+the first mail agent in the world to support retrieving @sc{s/mime}
+certificates from DNS, so you're not likely to find very many
+certificates out there. At least there should be one, stored at the
+domain @code{simon.josefsson.org}. LDAP is a more popular method of
+distributing certificates, support for it is planned. (Meanwhile, you
+can use @code{ldapsearch} from the command line to retrieve a
+certificate into a file and use it.)
As for signing messages, OpenSSL can't perform signing operations
without some kind of configuration. Especially, you need to tell it
where your private key and your certificate is stored. MML uses an
-Emacs interface to OpenSSL, aptly named @code{smime.el}, and it contain
-a @code{custom} group used for this configuration. So, try @code{M-x
-customize-group RET smime RET} and look around.
-
-Currently there is no support for talking to a CA (or RA) to create your
-own certificate. None is planned either. You need to do this manually
-with OpenSSL or using some other program. I used Netscape and got a
-free S/MIME certificate from one of the big CA's on the net. Netscape
-is able to export your private key and certificate in PKCS #12 format.
-Use OpenSSL to convert this into a plain X.509 certificate in PEM format
-as follows.
+Emacs interface to OpenSSL, aptly named @code{smime.el}, and it
+contain a @code{custom} group used for this configuration. So, try
+@kbd{M-x customize-group RET smime RET} and look around.
+
+Currently there is no support for talking to a CA (or RA) to create
+your own certificate. None is planned either. You need to do this
+manually with OpenSSL or using some other program. I used Netscape
+and got a free @sc{s/mime} certificate from one of the big CA's on the
+net. Netscape is able to export your private key and certificate in
+PKCS #12 format. Use OpenSSL to convert this into a plain X.509
+certificate in PEM format as follows.
@example
$ openssl pkcs12 -in ns.p12 -clcerts -nodes > key+cert.pem
@end example
-The @code{key+cert.pem} file should be pointed to from the
+The @file{key+cert.pem} file should be pointed to from the
@code{smime-keys} variable. You should now be able to send signed mail.
@emph{Note!} Your private key is store unencrypted in the file, so take
@subsection Using PGP/MIME
-PGP/MIME requires an external OpenPGP implementation, such as GNU
-Privacy Guard (@uref{http://www.gnupg.org/}). It also requires an Emacs
-interface to it, such as Mailcrypt (available from
+@sc{pgp/mime} requires an external OpenPGP implementation, such as GNU
+Privacy Guard (@uref{http://www.gnupg.org/}). It also requires an
+Emacs interface to it, such as Mailcrypt (available from
@uref{http://www.nb.net/~lbudney/linux/software/mailcrypt.html}) or
Florian Weimer's @code{gpg.el}.
@item message-signature-file
@vindex message-signature-file
File containing the signature to be inserted at the end of the buffer.
-The default is @samp{~/.signature}.
+The default is @file{~/.signature}.
@end table
Message uses virtually only its own variables---older @code{mail-}
variables aren't consulted. To force Message to take those variables
-into account, you can put the following in your @code{.emacs} file:
+into account, you can put the following in your @file{.emacs} file:
@lisp
(require 'messcompat)
projects / gnus / commitdiff