2002-01-05 Simon Josefsson <jas@extundo.com>

	* gnus.texi (Conformity): Add MIME and Disposition Notifications.

	* message.texi (Header Commands): Fix.  Add m-goto-from.
	(Insertion): Add m-i-disposition-notification-to.

diff --git a/texi/ChangeLog b/texi/ChangeLog
index 57bb454..1257304 100644 (file)
--- a/texi/ChangeLog
+++ b/texi/ChangeLog
@@ -1,3 +1,10 @@
+2002-01-05  Simon Josefsson  <jas@extundo.com>
+
+       * gnus.texi (Conformity): Add MIME and Disposition Notifications.
+
+       * message.texi (Header Commands): Fix.  Add m-goto-from.
+       (Insertion): Add m-i-disposition-notification-to.
+
 2002-01-05  ShengHuo ZHU  <zsh@cs.rochester.edu>
 
        * Makefile.in (.latexi.pdf-x): Use thumbpdf.

diff --git a/texi/gnus.texi b/texi/gnus.texi
index d167da5..23751ef 100644 (file)
--- a/texi/gnus.texi
+++ b/texi/gnus.texi
@@ -20707,10 +20707,16 @@ on Son-of-RFC 1036.  They have produced a number of drafts proposing
 various changes to the format of news articles.  The Gnus towers will
 look into implementing the changes when the draft is accepted as an RFC.
 
+@item MIME - RFC 2045-2049 etc
+@cindex MIME
+All the various MIME RFCs are supported.
+
+@item Disposition Notifications - RFC 2289
+Message Mode is able to request notifications from the receiver.
+
 @item PGP - RFC 1991 and RFC 2440
 @cindex RFC 1991
 @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
@@ -20718,17 +20724,14 @@ 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.
 Gnus supports both encoding and decoding.
 
 @item S/MIME - RFC 2633
-
 RFC 2633 describes the 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

diff --git a/texi/message.texi b/texi/message.texi
index f9fc2c0..8cd820c 100644 (file)
--- a/texi/message.texi
+++ b/texi/message.texi
@@ -359,7 +359,7 @@ inserted.
 
 @item C-c ?
 @kindex C-c ?
-@findex message-goto-to
+@findex describe-mode
 Describe the message mode.
 
 @item C-c C-f C-t
@@ -367,6 +367,12 @@ Describe the message mode.
 @findex message-goto-to
 Go to the @code{To} header (@code{message-goto-to}).
 
+@item C-c C-f C-o
+@kindex C-c C-f C-o
+@findex message-goto-from
+Go to the @code{From} header (@code{message-goto-from}).  (The ``o''
+in the key binding is for Originator.)
+
 @item C-c C-f C-b
 @kindex C-c C-f C-b
 @findex message-goto-bcc
@@ -503,6 +509,14 @@ Insert a signature at the end of the buffer
 @findex message-insert-headers
 Insert the message headers (@code{message-insert-headers}).
 
+@item C-c M-n
+@kindex C-c M-n
+@findex message-insert-disposition-notification-to
+Insert a request for a disposition
+notification. (@code{message-insert-disposition-notification-to}).
+This means that if the recipient support RFC 2298 she might send you a
+notification that she received the message.
+
 @end table