-\input texinfo @c -*-texinfo-*-
+\input texinfo @c -*- mode: texinfo; coding: iso-2022-7bit; -*-
@setfilename message-ja
@settitle T-gnus 6.15 Message Manual
@item message-citation-line-function
@vindex message-citation-line-function
+@cindex attribution line
\e$B0zMQ9T$rA^F~$9$k$?$a$K8F$P$l$k4X?t$G$9!#=i4|CM\e(B
\e$B$O\e(B @code{message-insert-citation-line} \e$B$G!"$3$l$O0zMQ9T$r<!$N$h$&$K$7$^\e(B
\e$B$9\e(B:
\e$B$3$N4X?t$,8F$P$l$?$H$-!"%]%$%s%H$O%a%C%;!<%8$NK\BN$N@hF,$K$"$k$G$7$g$&!#\e(B
+\e$B$J$*\e(B gnus \e$B$K$O!"\e(B`writes:' \e$B$N>e$G%/%j%C%/$9$k$H0zMQ$5$l$?%F%-%9%H$r1#$95!\e(B
+\e$BG=$,$"$j$^$9!#$b$7$"$J$?$,EY$r1[$7$F0zMQ9T$rJQ99$7$F$7$^$&$H!"$=$l$rFI$`\e(B
+\e$B?M$?$A$bH`$i$N\e(B gnus \e$B$rBP1~$5$;$J$1$l$P$J$i$J$/$J$k$G$7$g$&!#JQ\e(B
+\e$B?t\e(B @code{gnus-cite-attribution-suffix} \e$B$r;2>H$7$F2<$5$$!#>\:Y\e(B
+\e$B$O\e(B @xref{Article Highlighting, , \e$B5-;v$N%O%$%i%$%H\e(B, gnus-ja}, \e$B$K$"$j$^$9!#\e(B
+
@item message-yank-prefix
@vindex message-yank-prefix
@cindex yanking
@cindex quoting
\e$B$"$J$?$,5-;v$KJVEz$+%U%)%m!<%"%C%W$r$7$F$$$k$H$-$O!"IaDL$O$"$J$?$,1~Ez$7\e(B
\e$B$F$$$k?M$N$b$N$K0zMQId$rIU$1$?$$$G$7$g$&!#0zMQJ8$NA^F~$O\e(B @dfn{\e$BE=$jIU$1\e(B}
-\e$B$K$h$C$F$J$5$l!"$=$l$>$l$NE=$jIU$1$i$l$?0zMQ9T$O$=$NA0\e(B
-\e$B$K\e(B @code{message-yank-prefix} \e$B$rIU$1$i$l$^$9!#=i4|CM$O\e(B @samp{> } \e$B$G$9!#\e(B
+\e$B$K$h$C$F$J$5$l\e(B (\e$B$9$G$K0zMQId$,IU$$$F$$$k$b$N$OBP>]30!"\e(B
+@code{message-yank-cited-prefix} \e$B$r;2>H$N$3$H\e(B)\e$B!"$=$l$>$l$NE=$jIU$1$i$l$?\e(B
+\e$B0zMQ9T$O$=$NA0$K\e(B @code{message-yank-prefix} \e$B$rIU$1$i$l$^$9!#=i4|CM\e(B
+\e$B$O\e(B @samp{> } \e$B$G$9!#\e(B
+
+@item message-yank-cited-prefix
+@vindex message-yank-cited-prefix
+@cindex yanking
+@cindex cited
+@cindex quoting
+\e$B$9$G$K0zMQ$5$l$?9T$K$O\e(B @code{message-yank-prefix} \e$B$NBe$o$j$K$3$NJQ?t$NFb\e(B
+\e$BMF$,0zMQId$H$7$F;H$o$l$^$9!#=i4|CM$O\e(B @samp{>} \e$B$G$9!#\e(B
@item message-yank-add-new-references
@vindex message-yank-add-new-references
\e$B$^$9$,!"=pL>$O>J$-$^$9!#\e(BSupercite \e$B$r;H$&$?$a$K!"$=$l\e(B
\e$B$r\e(B @code{sc-cite-original} \e$B$K@_Dj$9$k;v$b$G$-$^$9!#\e(B
+@item message-suspend-font-lock-when-citing
+@vindex message-suspend-font-lock-when-citing
+@code{nil} \e$B$G$J$1$l$P!"K\5-;v$r0zMQ$7$F$$$k4V\e(B font-lock \e$B$NF0:n$r;_$a$^$9!#\e(B
+\e$B$$$/$D$+$N!"\e(BEmacs \e$B$,2K$J$H$-$KCY$l$FF0:n$9$k\e(B font-lock \e$B$N$?$a$N%D!<\e(B
+\e$B%k\e(B (\e$B$^$?$O\e(B Emacs \e$B<+?H\e(B) \e$B$K$O%P%0$,$"$j!"$=$l$i$O$7$P$7$P\e(B font-lock \e$B$NF0:n\e(B
+\e$B$r9T$J$&BP>]$H$J$k%P%C%U%!$r<h$j0c$($^$9!#$=$l$O$?$$$F$$\e(B Emacs \e$B$,%_%K%P%C\e(B
+\e$B%U%!$G%f!<%6$K2?$+$NF~NO$rB%$9$H$-$K5/$3$j$^$9!#$3$l$O$=$N>l$7$N$.$NBP:v\e(B
+\e$B$G$O$"$k$N$G$9$,!"$3$N%*%W%7%g%s$rHs\e(B-@code{nil} \e$B$K$9$k$3$H$K$h$C$F!"$"$J\e(B
+\e$B$?$OITL{2w$J%(%i!<$r2sHr$G$-$k$+$b$7$l$^$;$s!#\e(B
+
@item message-indent-citation-function
@vindex message-indent-citation-function
\e$B$A$g$&$I%a!<%k%P%C%U%!$KA^F~$5$l$?0zMQJ8$r=$@5$9$k$?$a$N4X?t$G$9!#$3$l$O\e(B
\e$B$?$a$N8z2LE*$JJ}K!$G$9!#\e(B
@c FIXTGNUS We should provide MIME manual.
-@c @node MIME
-@c @section MIME
-@c @cindex MML
-@c @cindex MIME
-@c @cindex multipart
-@c @cindex attachment
-
-@c Message is a @sc{mime}-compliant posting agent. The user generally
-@c doesn't have to do anything to make the @sc{mime} happen---Message will
-@c automatically add the @code{Content-Type} and
-@c @code{Content-Transfer-Encoding} headers.
-
-@c The most typical thing users want to use the multipart things in
-@c @sc{mime} for is to add ``attachments'' to mail they send out. This can
-@c be done with the @code{C-c C-a} command, which will prompt for a file
-@c name and a @sc{mime} type.
-
-@c You can also create arbitrarily complex multiparts using the MML
-@c language (@pxref{Composing, , Composing, emacs-mime, The Emacs MIME
-@c Manual}).
-
-@c @node Security
-@c @section Security
-@c @cindex Security
-@c @cindex S/MIME
-@c @cindex PGP/MIME
-@c @cindex sign
-@c @cindex encrypt
-
-@c Using the MML language, Message is able to create digitally signed and
-@c digitally encrypted messages. Message (or rather MML) currently support
-@c PGP/MIME and S/MIME. Instructing MML to perform security operations on
-@c a MIME part is done using the @code{M-m s} key map for signing and the
-@c @code{M-m c} key map for encryption, as follows.
-
-@c @table @kbd
-
-@c @item M-m s s
-@c @kindex M-m s s
-@c @findex mml-secure-sign-smime
-
-@c Digitally sign current MIME part using S/MIME.
-
-@c @item M-m s p
-@c @kindex M-m s p
-@c @findex mml-secure-sign-pgp
-
-@c Digitally sign current MIME part using PGP/MIME.
-
-@c @item M-m c s
-@c @kindex M-m c s
-@c @findex mml-secure-encrypt-smime
-
-@c Digitally encrypt current MIME part using S/MIME.
-
-@c @item M-m c p
-@c @kindex M-m c p
-@c @findex mml-secure-encrypt-pgpmime
-
-@c Digitally encrypt current MIME part using PGP/MIME.
-
-@c @end table
-
-@c These commands do not immediately sign or encrypt the message, they
-@c merely insert proper MML tags to instruct the MML engine to perform that
-@c operation when the message is actually sent. They may perform other
-@c operations too, such as locating and retrieving a S/MIME certificate of
-@c the person you wish to send encrypted mail to.
-
-@c Since signing and especially encryption often is used when sensitive
-@c information is sent, you may want to have some way to ensure that your
-@c mail is actually signed or encrypted. After invoking the above
-@c sign/encrypt commands, it is possible to preview the raw article by
-@c using @code{C-u M-m P} (@code{mml-preview}). Then you can verify that
-@c your long rant about what your ex-significant other or whomever actually
-@c did with that funny looking person at that strange party the other
-@c night, actually will be sent encrypted.
-
-@c @emph{Note!} Neither PGP/MIME nor S/MIME encrypt/signs RFC822 headers.
-@c They only operate on the MIME object. Keep this in mind before sending
-@c mail with a sensitive Subject line.
-
-@c Actually using the security commands above is not very difficult. At
-@c least not compared with making sure all involved programs talk with each
-@c other properly. Thus, we now describe what external libraries or
-@c programs are required to make things work, and some small general hints.
-
-@c @subsection Using S/MIME
-
-@c @emph{Note!} This section assume you have a basic familiarity with
-@c modern cryptography, S/MIME, various PKCS standards, OpenSSL and so on.
-
-@c The S/MIME support in Message (and MML) require OpenSSL. OpenSSL
-@c perform the actual S/MIME sign/encrypt operations. OpenSSL can be found
-@c at @code{http://www.openssl.org/}. OpenSSL 0.9.6 and later should work.
-@c Version 0.9.5a cannot extract mail addresses from certificates, and it
-@c insert a spurious CR character into MIME separators so you may wish to
-@c avoid it if you would like to avoid being regarded as someone who send
-@c strange mail. (Although by sending S/MIME messages you've probably
-@c already lost that contest.)
-
-@c To be able to send encrypted mail, a personal certificate is not
-@c required. Message (MML) need a certificate for the person to whom you
-@c wish to communicate with though. You're asked for this when you type
-@c @code{M-m c s}. Currently there are two ways to retrieve this
-@c certificate, from a local file or from DNS. If you chose a local file,
-@c it need to contain a X.509 certificate in PEM format. If you chose DNS,
-@c you're asked for the domain name where the certificate is stored, the
-@c default is a good guess. To my belief, Message (MML) is the first mail
-@c agent in the world to support retrieving S/MIME certificates from DNS,
-@c so you're not likely to find very many certificates out there. At least
-@c there should be one, stored at the domain @code{simon.josefsson.org}.
-@c LDAP is a more popular method of distributing certificates, support for
-@c it is planned. (Meanwhile, you can use @code{ldapsearch} from the
-@c command line to retrieve a certificate into a file and use it.)
-
-@c As for signing messages, OpenSSL can't perform signing operations
-@c without some kind of configuration. Especially, you need to tell it
-@c where your private key and your certificate is stored. MML uses an
-@c Emacs interface to OpenSSL, aptly named @code{smime.el}, and it contain
-@c a @code{custom} group used for this configuration. So, try @code{M-x
-@c customize-group RET smime RET} and look around.
-
-@c Currently there is no support for talking to a CA (or RA) to create your
-@c own certificate. None is planned either. You need to do this manually
-@c with OpenSSL or using some other program. I used Netscape and got a
-@c free S/MIME certificate from one of the big CA's on the net. Netscape
-@c is able to export your private key and certificate in PKCS #12 format.
-@c Use OpenSSL to convert this into a plain X.509 certificate in PEM format
-@c as follows.
-
-@c @example
-@c $ openssl pkcs12 -in ns.p12 -clcerts -nodes > key+cert.pem
-@c @end example
-
-@c The @code{key+cert.pem} file should be pointed to from the
-@c @code{smime-keys} variable. You should now be able to send signed mail.
-
-@c @emph{Note!} Your private key is store unencrypted in the file, so take
-@c care in handling it.
-
-@c @subsection Using PGP/MIME
-
-@c PGP/MIME require an external OpenPGP implementation, such as GNU Privacy
-@c Guard (@code{http://www.gnupg.org/}. It also require a Emacs interface
-@c to it, such as Mailcrypt (available from
-@c @code{http://www.nb.net/~lbudney/linux/software/mailcrypt.html}) or
-@c Florian Weimer's @code{gpg.el}.
-
-@c Creating your own OpenPGP key is described in detail in the
-@c documentation of your OpenPGP implementation, so we refer to it.
+@ignore
+@node MIME
+@section MIME
+@cindex MML
+@cindex MIME
+@cindex multipart
+@cindex attachment
+
+Message is a @sc{mime}-compliant posting agent. The user generally
+doesn't have to do anything to make the @sc{mime} happen---Message will
+automatically add the @code{Content-Type} and
+@code{Content-Transfer-Encoding} headers.
+
+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
+name and a @sc{mime} type.
+
+You can also create arbitrarily complex multiparts using the MML
+language (@pxref{Composing, , Composing, emacs-mime, The Emacs MIME
+Manual}).
+
+@node Security
+@section Security
+@cindex Security
+@cindex S/MIME
+@cindex PGP/MIME
+@cindex sign
+@cindex encrypt
+
+Using the MML language, Message is able to create digitally signed and
+digitally encrypted messages. Message (or rather MML) currently support
+PGP/MIME 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.
+
+@table @kbd
+
+@item C-c C-m s s
+@kindex C-c C-m s s
+@findex mml-secure-sign-smime
+
+Digitally sign current MIME part using S/MIME.
+
+@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.
+
+@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.
+
+@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.
+@end table
+
+These commands do not immediately sign or encrypt the message, they
+merely insert proper MML tags 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.
+
+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.
+
+@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.
+
+Actually using the security commands above is not very difficult. At
+least not compared with making sure all involved programs talk with each
+other properly. Thus, we now describe what external libraries or
+programs are required to make things work, and some small general hints.
+
+@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 @code{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.)
+
+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.)
+
+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.
+
+@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
+@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
+care in handling it.
+
+@subsection Using PGP/MIME
+
+PGP/MIME requires an external OpenPGP implementation, such as GNU Privacy
+Guard (@code{http://www.gnupg.org/}). It also requires an Emacs interface
+to it, such as Mailcrypt (available from
+@code{http://www.nb.net/~lbudney/linux/software/mailcrypt.html}) or
+Florian Weimer's @code{gpg.el}.
+
+Creating your own OpenPGP key is described in detail in the
+documentation of your OpenPGP implementation, so we refer to it.
+
+@end ignore
@node Various Commands
@section \e$B$$$m$$$m$JL?Na\e(B
@item message-generate-headers-first
@vindex message-generate-headers-first
-@code{nil} \e$B$G$J$1$l$P!"%a%C%;!<%8$N:n@.$r;O$a$kA0$KA4$F$N%X%C%@!<$r:n@.\e(B
-\e$B$7$^$9!#\e(B
+@code{nil} \e$B$G$J$1$l$P!"%a%C%;!<%8$N:n@.$r;O$a$kA0$KA4$F$NI,MW$J%X%C%@!<\e(B
+\e$B$r:n@.$7$^$9!#\e(B
+
+\e$BJQ?t\e(B @code{message-required-mail-headers} \e$B$H\e(B @code{message-required-news-headers} \e$B$G!"\e(B
+\e$B$I$N%X%C%@!<$,I,MW$+$r;XDj$7$^$9!#\e(B
+
+\e$B$$$/$D$+$N%X%C%@!<$O!"Aw?.$9$kA0$K>C$5$l$?$j:n$jD>$5$l$?$j$7$^$9!#$3$l$K\e(B
+\e$B$OJQ?t\e(B @code{message-deletable-headers} (\e$B8e=R\e(B) \e$B$,4X78$7$^$9!#\e(B
@item message-from-style
@vindex message-from-style
-@code{From} \e$B%X%C%@!<$,$I$N$h$&$K8+$($k$+$r;XDj$7$^$9!#\e(B4\e$B$D$N9gK!E*CM$,$"\e(B
-\e$B$j$^$9\e(B:
+@code{From} \e$B%X%C%@!<$,$I$N$h$&$K8+$($k$+$r;XDj$7$^$9!#0J2<$N#4$D$NCM$,;H\e(B
+\e$B$($^$9\e(B:
@table @code
@item nil
@item message-ignored-mail-headers
@vindex message-ignored-mail-headers
\e$B%a!<%k$r=P$9A0$K<h$j=|$+$l$k%X%C%@!<$N@55,I=8=$G$9!#=i4|CM\e(B
-\e$B$O\e(B @samp{^[GF]cc:\\|^Resent-Fcc:} \e$B$G$9!#\e(B
+\e$B$O\e(B @samp{^[GF]cc:\\|^Resent-Fcc:\\|^Xref:\\|^X-Draft-From:} \e$B$G$9!#\e(B
@item message-default-mail-headers
@vindex message-default-mail-headers
@table @code
@item message-send-mail-function
@vindex message-send-mail-function
+@findex message-send-mail-with-sendmail
+@findex message-send-mail-with-mh
+@findex message-send-mail-with-qmail
+@findex message-send-mail-with-smtp
+@findex smtpmail-send-it
+@findex feedmail-send-it
\e$B8=:_$N%P%C%U%!$r%a!<%k$H$7$FAw$k$?$a$K;H$o$l$k4X?t$G$9!#=i4|CM\e(B
-\e$B$O\e(B @code{message-send-mail-with-sendmail} \e$B$G$9!#$b$7Be$o$j$K\e(B MH \e$B$GAw$k$N\e(B
-\e$B$r9%$`$N$G$"$l$P!"$3$NJQ?t$r\e(B @code{message-send-mail-with-mh} \e$B$K@_Dj$7$F\e(B
-\e$B2<$5$$!#\e(B
+\e$B$O\e(B @code{message-send-mail-with-sendmail} \e$B$G$9!#B>\e(B
+\e$B$K\e(B @code{message-send-mail-with-mh},
+@code{message-send-mail-with-qmail}, @code{message-send-mail-with-smtp},
+@code{smtpmail-send-it} \e$B$*$h$S\e(B @code{feedmail-send-it} \e$B$,;H$($^$9!#\e(B
@item message-mh-deletable-headers
@vindex message-mh-deletable-headers
@vindex message-required-news-headers
@code{message-required-news-headers} \e$B$O%X%C%@!<%7%s%\%k$N%j%9%H$G$9!#$3\e(B
\e$B$l$i$N%X%C%@!<$O<+F0E*$K:n@.$5$l$k$+!"$b$7$/$O$=$l$,IT2DG=$G$"$l$P!"F~NO\e(B
-\e$B$rB%?J$7$^$9!#0J2<$N%7%s%\%k$O9gK!E*$G$9\e(B:
+\e$B$rB%?J$7$^$9!#0J2<$N%7%s%\%k$,;H$($^$9\e(B:
@table @code
@vindex message-syntax-checks
@code{nil} \e$B$G$J$1$l$P!"\e(BMessage \e$B$OEj9F$NA0$K!"%X%C%@!<$HB>$N$b$N$N9gK!@-\e(B
\e$B$rD4$Y$^$9!#$3$N%j%9%H$KMWAG$rIU$12C$($?$j<h$j=|$$$?$j$9$k;v$G!"D4$Y$kN3\e(B
-\e$B$NBg$-$5$r@)8f$9$k;v$,$G$-$^$9!#9gK!E*$JMWAG$O\e(B:
+\e$B$NBg$-$5$r@)8f$9$k;v$,$G$-$^$9!#;H$($kMWAG$O\e(B:
@table @code
@item subject-cmsg
@item long-lines
\e$B$"$^$j$KD9$$9T$rD4$Y$^$9!#\e(B
@item control-chars
-\e$BHs9gK!J8;z$rD4$Y$^$9!#\e(B
+\e$B;H$C$F$O$$$1$J$$J8;z$rD4$Y$^$9!#\e(B
@item size
\e$B2a>j$JBg$-$5$rD4$Y$^$9!#\e(B
@item new-text
@item message-ignored-news-headers
@vindex message-ignored-news-headers
\e$BEj9F$9$kA0$K<h$j=|$+$l$k%X%C%@!<$N@55,I=8=$G$9!#=i4|CM$O\e(B @*
-@samp{^NNTP-Posting-Host:\\|^Xref:\\|^[BGF]cc:\\|^Resent-Fcc:} \e$B$G$9!#\e(B
+@samp{^NNTP-Posting-Host:\\|^Xref:\\|^[BGF]cc:\\|^Resent-Fcc:\\|^X-Draft-From:}
+\e$B$G$9!#\e(B
@item message-default-news-headers
@vindex message-default-news-headers
projects / elisp / gnus.git- / blobdiff