X-Git-Url: http://cgit.sxemacs.org/?p=gnus;a=blobdiff_plain;f=texi%2Fgnus.texi;h=9194753ddf7b06451d3c0c195402ebfa5c86fb03;hp=6feab478b1676142b670343d7c2a18b34983f63d;hb=a10e061d0e6d4792608c61659d34a0c770c1129b;hpb=488a620a161d20e8610302c4ffa10926ee572778 diff --git a/texi/gnus.texi b/texi/gnus.texi index 6feab478b..9194753dd 100644 --- a/texi/gnus.texi +++ b/texi/gnus.texi @@ -47,7 +47,7 @@ developing GNU and promoting software freedom.'' \begin{document} % Adjust ../Makefile.in if you change the following line: -\newcommand{\gnusversionname}{Ma Gnus v0.2} +\newcommand{\gnusversionname}{Ma Gnus v0.4} \newcommand{\gnuschaptername}{} \newcommand{\gnussectionname}{} @@ -358,7 +358,7 @@ spool or your mbox file. All at the same time, if you want to push your luck. @c Adjust ../Makefile.in if you change the following line: -This manual corresponds to Ma Gnus v0.2 +This manual corresponds to Ma Gnus v0.4 @ifnottex @insertcopying @@ -392,7 +392,7 @@ people should be empowered to do what they want by using (or abusing) the program. @c Adjust ../Makefile.in if you change the following line: -This manual corresponds to Ma Gnus v0.2 +This manual corresponds to Ma Gnus v0.4 @heading Other related manuals @itemize @@ -663,7 +663,6 @@ Getting News * Direct Functions:: Connecting directly to the server. * Indirect Functions:: Connecting indirectly to the server. * Common Variables:: Understood by several connection functions. -* NNTP marks:: Storing marks for @acronym{NNTP} servers. Getting Mail @@ -1067,10 +1066,6 @@ you would typically set this variable to (setq gnus-secondary-select-methods '((nnmbox ""))) @end lisp -Note: the @acronym{NNTP} back end stores marks in marks files -(@pxref{NNTP marks}). This feature makes it easy to share marks between -several Gnus installations, but may slow down things a bit when fetching -new articles. @xref{NNTP marks}, for more information. @node The Server is Down @@ -2885,7 +2880,7 @@ composed messages will be @code{Gcc}'d to the current group. If generated, if @code{(gcc-self . "string")} is present, this string will be inserted literally as a @code{gcc} header. This parameter takes precedence over any default @code{Gcc} rules as described later -(@pxref{Archived Messages}). +(@pxref{Archived Messages}), with the exception for messages to resend. @strong{Caveat}: Adding @code{(gcc-self . t)} to the parameter list of @code{nntp} groups (or the like) isn't valid. An @code{nntp} server @@ -3028,6 +3023,7 @@ like this in the group parameters: @example (posting-style (name "Funky Name") + ("X-Message-SMTP-Method" "smtp smtp.example.org 587") ("X-My-Header" "Funky Value") (signature "Funky Signature")) @end example @@ -4294,12 +4290,11 @@ default is @code{nil} in Emacs, or is the aliasee of the coding system named @code{file-name} (a certain coding system of which an alias is @code{file-name}) in XEmacs. -The @code{nnml} back end, the @code{nnrss} back end, the @acronym{NNTP} -marks feature (@pxref{NNTP marks}), the agent, and the cache use -non-@acronym{ASCII} group names in those files and directories. This -variable overrides the value of @code{file-name-coding-system} which -specifies the coding system used when encoding and decoding those file -names and directory names. +The @code{nnml} back end, the @code{nnrss} back end, the agent, and +the cache use non-@acronym{ASCII} group names in those files and +directories. This variable overrides the value of +@code{file-name-coding-system} which specifies the coding system used +when encoding and decoding those file names and directory names. In XEmacs (with the @code{mule} feature), @code{file-name-coding-system} is the only means to specify the coding system used to encode and decode @@ -10815,12 +10810,6 @@ buffers. For example: Also @pxref{Group Parameters}. -@vindex gnus-propagate-marks -@item gnus-propagate-marks -If non-@code{nil}, propagate marks to the backends for possible -storing. @xref{NNTP marks}, and friends, for a more fine-grained -sieve. - @end table @@ -12670,6 +12659,22 @@ and matches the Gcc group name, attach files as external parts; if it is non-@code{nil}, the behavior is the same as @code{all}, but it may be changed in the future. +@item gnus-gcc-self-resent-messages +@vindex gnus-gcc-self-resent-messages +Like the @code{gcc-self} group parameter, applied only for unmodified +messages that @code{gnus-summary-resend-message} (@pxref{Summary Mail +Commands}) resends. Non-@code{nil} value of this variable takes +precedence over any existing @code{Gcc} header. + +If this is @code{none}, no @code{Gcc} copy will be made. If this is +@code{t}, messages resent will be @code{Gcc} copied to the current +group. If this is a string, it specifies a group to which resent +messages will be @code{Gcc} copied. If this is @code{nil}, @code{Gcc} +will be done according to existing @code{Gcc} header(s), if any. If +this is @code{no-gcc-self}, that is the default, resent messages will be +@code{Gcc} copied to groups that existing @code{Gcc} header specifies, +except for the current group. + @end table @@ -12764,8 +12769,8 @@ from date id references chars lines xref extra. In the case of a string value, if the @code{match} is a regular expression, a @samp{gnus-match-substitute-replacement} is proceed on the value to replace the positional parameters @samp{\@var{n}} by the -corresponding parenthetical matches (see @xref{Replacing the Text that -Matched, , Text Replacement, elisp, The Emacs Lisp Reference Manual}.) +corresponding parenthetical matches (see @xref{Replacing Match,, +Replacing the Text that Matched, elisp, The Emacs Lisp Reference Manual}.) @vindex message-reply-headers @@ -12801,6 +12806,7 @@ So here's a new example: (signature-file "~/.work-signature") (address "user@@bar.foo") (body "You are fired.\n\nSincerely, your boss.") + ("X-Message-SMTP-Method" "smtp smtp.example.org 587") (organization "Important Work, Inc")) ("nnml:.*" (From (with-current-buffer gnus-article-buffer @@ -12815,6 +12821,13 @@ if you fill many roles. You may also use @code{message-alternative-emails} instead. @xref{Message Headers, ,Message Headers, message, Message Manual}. +Of particular interest in the ``work-mail'' style is the +@samp{X-Message-SMTP-Method} header. It specifies how to send the +outgoing email. You may want to sent certain emails through certain +@acronym{SMTP} servers due to company policies, for instance. +@xref{Mail Variables, ,Message Variables, message, Message Manual}. + + @node Drafts @section Drafts @cindex drafts @@ -13740,7 +13753,6 @@ don't update their active files often, this can help. * Direct Functions:: Connecting directly to the server. * Indirect Functions:: Connecting indirectly to the server. * Common Variables:: Understood by several connection functions. -* NNTP marks:: Storing marks for @acronym{NNTP} servers. @end menu @@ -14011,53 +14023,6 @@ is @samp{()}. @end table -@node NNTP marks -@subsubsection NNTP marks -@cindex storing NNTP marks - -Gnus stores marks (@pxref{Marking Articles}) for @acronym{NNTP} -servers in marks files. A marks file records what marks you have set -in a group and each file is specific to the corresponding server. -Marks files are stored in @file{~/News/marks} -(@code{nntp-marks-directory}) under a classic hierarchy resembling -that of a news server, for example marks for the group -@samp{gmane.discuss} on the news.gmane.org server will be stored in -the file @file{~/News/marks/news.gmane.org/gmane/discuss/.marks}. - -Marks files are useful because you can copy the @file{~/News/marks} -directory (using rsync, scp or whatever) to another Gnus installation, -and it will realize what articles you have read and marked. The data -in @file{~/News/marks} has priority over the same data in -@file{~/.newsrc.eld}. - -Note that marks files are very much server-specific: Gnus remembers -the article numbers so if you don't use the same servers on both -installations things are most likely to break (most @acronym{NNTP} -servers do not use the same article numbers as any other server). -However, if you use servers A, B, C on one installation and servers A, -D, E on the other, you can sync the marks files for A and then you'll -get synchronization for that server between the two installations. - -Using @acronym{NNTP} marks can possibly incur a performance penalty so -if Gnus feels sluggish, try setting the @code{nntp-marks-is-evil} -variable to @code{t}. Marks will then be stored in @file{~/.newsrc.eld}. - -Related variables: - -@table @code - -@item nntp-marks-is-evil -@vindex nntp-marks-is-evil -If non-@code{nil}, this back end will ignore any marks files. The -default is @code{nil}. - -@item nntp-marks-directory -@vindex nntp-marks-directory -The directory where marks for nntp groups will be stored. - -@end table - - @node News Spool @subsection News Spool @cindex nnspool @@ -14228,8 +14193,9 @@ if the server supports UID EXPUNGE, but it's not done by default on servers that doesn't support that command. @item nnimap-streaming -Virtually all @code{IMAP} server support fast streaming of data. If -you have problems connecting to the server, try setting this to @code{nil}. +Virtually all @acronym{IMAP} server support fast streaming of data. +If you have problems connecting to the server, try setting this to +@code{nil}. @item nnimap-fetch-partial-articles If non-@code{nil}, fetch partial articles from the server. If set to @@ -14237,6 +14203,10 @@ a string, then it's interpreted as a regexp, and parts that have matching types will be fetched. For instance, @samp{"text/"} will fetch all textual parts, while leaving the rest on the server. +@item nnimap-record-commands +If non-@code{nil}, record all @acronym{IMAP} commands in the +@samp{"*imap log*"} buffer. + @end table @@ -14752,6 +14722,18 @@ corresponding keywords. A script to be run before fetching the mail. The syntax is the same as the @code{:program} keyword. This can also be a function to be run. +One popular way to use this is to set up an SSH tunnel to access the +@acronym{POP} server. Here's an example: + +@lisp +(pop :server "127.0.0.1" + :port 1234 + :user "foo" + :password "secret" + :prescript + "nohup ssh -f -L 1234:pop.server:110 remote.host sleep 3600 &") +@end lisp + @item :postscript A script to be run after fetching the mail. The syntax is the same as the @code{:program} keyword. This can also be a function to be run. @@ -16131,22 +16113,6 @@ splitting. It has to create lots of files, and it also generates @acronym{NOV} databases for the incoming mails. This makes it possibly the fastest back end when it comes to reading mail. -@cindex self contained nnml servers -@cindex marks -When the marks file is used (which it is by default), @code{nnml} -servers have the property that you may backup them using @code{tar} or -similar, and later be able to restore them into Gnus (by adding the -proper @code{nnml} server) and have all your marks be preserved. Marks -for a group are usually stored in the @code{.marks} file (but see -@code{nnml-marks-file-name}) within each @code{nnml} group's directory. -Individual @code{nnml} groups are also possible to backup, use @kbd{G m} -to restore the group (after restoring the backup into the nnml -directory). - -If for some reason you believe your @file{.marks} files are screwed -up, you can just delete them all. Gnus will then correctly regenerate -them next time it starts. - Virtual server settings: @table @code @@ -16184,15 +16150,6 @@ The name of the @acronym{NOV} files. The default is @file{.overview}. @vindex nnml-prepare-save-mail-hook Hook run narrowed to an article before saving. -@item nnml-marks-is-evil -@vindex nnml-marks-is-evil -If non-@code{nil}, this back end will ignore any @sc{marks} files. The -default is @code{nil}. - -@item nnml-marks-file-name -@vindex nnml-marks-file-name -The name of the @dfn{marks} files. The default is @file{.marks}. - @item nnml-use-compressed-files @vindex nnml-use-compressed-files If non-@code{nil}, @code{nnml} will allow using compressed message @@ -16533,19 +16490,6 @@ separate file. Each file is in the standard Un*x mbox format. @code{nnfolder} will add extra headers to keep track of article numbers and arrival dates. -@cindex self contained nnfolder servers -@cindex marks -When the marks file is used (which it is by default), @code{nnfolder} -servers have the property that you may backup them using @code{tar} or -similar, and later be able to restore them into Gnus (by adding the -proper @code{nnfolder} server) and have all your marks be preserved. -Marks for a group are usually stored in a file named as the mbox file -with @code{.mrk} concatenated to it (but see -@code{nnfolder-marks-file-suffix}) within the @code{nnfolder} -directory. Individual @code{nnfolder} groups are also possible to -backup, use @kbd{G m} to restore the group (after restoring the backup -into the @code{nnfolder} directory). - Virtual server settings: @table @code @@ -16604,20 +16548,6 @@ The extension for @acronym{NOV} files. The default is @file{.nov}. The directory where the @acronym{NOV} files should be stored. If @code{nil}, @code{nnfolder-directory} is used. -@item nnfolder-marks-is-evil -@vindex nnfolder-marks-is-evil -If non-@code{nil}, this back end will ignore any @sc{marks} files. The -default is @code{nil}. - -@item nnfolder-marks-file-suffix -@vindex nnfolder-marks-file-suffix -The extension for @sc{marks} files. The default is @file{.mrk}. - -@item nnfolder-marks-directory -@vindex nnfolder-marks-directory -The directory where the @sc{marks} files should be stored. If -@code{nil}, @code{nnfolder-directory} is used. - @end table @@ -16778,9 +16708,7 @@ undergo treatment such as duplicate checking. @code{nnmaildir} stores article marks for a given group in the corresponding maildir, in a way designed so that it's easy to manipulate them from outside Gnus. You can tar up a maildir, unpack it somewhere -else, and still have your marks. @code{nnml} also stores marks, but -it's not as easy to work with them from outside Gnus as with -@code{nnmaildir}. +else, and still have your marks. @code{nnmaildir} uses a significant amount of memory to speed things up. (It keeps in memory some of the things that @code{nnml} stores in files @@ -16872,16 +16800,6 @@ adding a server definition pointing to that directory in Gnus. The might interfere with overwriting data, so you may want to shut down Gnus before you restore the data. -It is also possible to archive individual @code{nnml}, -@code{nnfolder}, or @code{nnmaildir} groups, while preserving marks. -For @code{nnml} or @code{nnmaildir}, you copy all files in the group's -directory. For @code{nnfolder} you need 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. -@code{nnmaildir} notices the new directory automatically, so @kbd{G m} -is unnecessary in that case. - @node Web Searches @subsection Web Searches @cindex nnweb @@ -28914,7 +28832,7 @@ Gnus will work. @item Try doing an @kbd{M-x gnus-version}. If you get something that looks like @c -@samp{Ma Gnus v0.2} @c Adjust ../Makefile.in if you change this line! +@samp{Ma Gnus v0.4} @c Adjust ../Makefile.in if you change this line! @c you have the right files loaded. Otherwise you have some old @file{.el} files lying around. Delete these.