[Emacs-diffs] Changes to emacs/man/gnus.texi

[Juanma Barranquero]

Index: emacs/man/gnus.texi
diff -c emacs/man/gnus.texi:1.47 emacs/man/gnus.texi:1.48
*** emacs/man/gnus.texi:1.47    Sun Apr 10 04:20:14 2005
--- emacs/man/gnus.texi Mon Jun 20 14:42:47 2005
***************
*** 832,852 ****
  
  Filtering Spam Using The Spam ELisp Package
  
! * Spam ELisp Package Sequence of Events::  
! * Spam ELisp Package Filtering of Incoming Mail::  
! * Spam ELisp Package Global Variables::  
! * Spam ELisp Package Configuration Examples::  
! * Blacklists and Whitelists::   
! * BBDB Whitelists::             
! * Gmane Spam Reporting::        
! * Anti-spam Hashcash Payments::  
! * Blackholes::                  
! * Regular Expressions Header Matching::  
! * Bogofilter::                  
! * ifile spam filtering::        
! * spam-stat spam filtering::    
! * SpamOracle::                  
! * Extending the Spam ELisp package::  
  
  Filtering Spam Using Statistics with spam-stat
  
--- 832,852 ----
  
  Filtering Spam Using The Spam ELisp Package
  
! * Spam ELisp Package Sequence of Events::
! * Spam ELisp Package Filtering of Incoming Mail::
! * Spam ELisp Package Global Variables::
! * Spam ELisp Package Configuration Examples::
! * Blacklists and Whitelists::
! * BBDB Whitelists::
! * Gmane Spam Reporting::
! * Anti-spam Hashcash Payments::
! * Blackholes::
! * Regular Expressions Header Matching::
! * Bogofilter::
! * ifile spam filtering::
! * spam-stat spam filtering::
! * SpamOracle::
! * Extending the Spam ELisp package::
  
  Filtering Spam Using Statistics with spam-stat
  
***************
*** 1393,1399 ****
  Most common Unix news readers use a shared startup file called
  @file{.newsrc}.  This file contains all the information about what
  groups are subscribed, and which articles in these groups have been
! read. 
  
  Things got a bit more complicated with @sc{gnus}.  In addition to
  keeping the @file{.newsrc} file updated, it also used a file called
--- 1393,1399 ----
  Most common Unix news readers use a shared startup file called
  @file{.newsrc}.  This file contains all the information about what
  groups are subscribed, and which articles in these groups have been
! read.
  
  Things got a bit more complicated with @sc{gnus}.  In addition to
  keeping the @file{.newsrc} file updated, it also used a file called
***************
*** 3008,3014 ****
  hear a beep when you enter a group, you could put something like
  @code{(dummy-variable (ding))} in the parameters of that group.
  @code{dummy-variable} will be set to the (meaningless) result of the
! @code{(ding)} form.  
  
  Alternatively, since the VARIABLE becomes local to the group, this
  pattern can be used to temporarily change a hook.  For example, if the
--- 3008,3014 ----
  hear a beep when you enter a group, you could put something like
  @code{(dummy-variable (ding))} in the parameters of that group.
  @code{dummy-variable} will be set to the (meaningless) result of the
! @code{(ding)} form.
  
  Alternatively, since the VARIABLE becomes local to the group, this
  pattern can be used to temporarily change a hook.  For example, if the
***************
*** 3984,3990 ****
       8: comp.binaries.fractals
      13: comp.sources.unix
     452: alt.sex.emacs
! @end group   
  @end example
  
  The @samp{Emacs} topic has the topic parameter @code{(score-file
--- 3984,3990 ----
       8: comp.binaries.fractals
      13: comp.sources.unix
     452: alt.sex.emacs
! @end group
  @end example
  
  The @samp{Emacs} topic has the topic parameter @code{(score-file
***************
*** 13293,13299 ****
  By default the splitting codes @acronym{MIME} decodes headers so you
  can match on address@hidden strings.  The
  @code{nnmail-mail-splitting-charset} variable specifies the default
! charset for decoding.  The behaviour can be turned off completely by
  binding @code{nnmail-mail-splitting-decodes} to @code{nil}, which is
  useful if you want to match articles based on the raw header data.
  
--- 13293,13299 ----
  By default the splitting codes @acronym{MIME} decodes headers so you
  can match on address@hidden strings.  The
  @code{nnmail-mail-splitting-charset} variable specifies the default
! charset for decoding.  The behavior can be turned off completely by
  binding @code{nnmail-mail-splitting-decodes} to @code{nil}, which is
  useful if you want to match articles based on the raw header data.
  
***************
*** 14011,14017 ****
  
  @table @code
  
! @item group 
  If the split is a string, that will be taken as a group name.  Normal
  regexp match expansion will be done.  See below for examples.
  
--- 14011,14017 ----
  
  @table @code
  
! @item group
  If the split is a string, that will be taken as a group name.  Normal
  regexp match expansion will be done.  See below for examples.
  
***************
*** 16297,16303 ****
  A file containing credentials used to log in on servers.  The format is
  (almost) the same as the @code{ftp} @file{~/.netrc} file.  See the
  variable @code{nntp-authinfo-file} for exact syntax; also see
! @ref{NNTP}.  An example of an .authinfo line for an IMAP server, is: 
  
  @example
  machine students.uio.no login larsi password geheimnis port imap
--- 16297,16303 ----
  A file containing credentials used to log in on servers.  The format is
  (almost) the same as the @code{ftp} @file{~/.netrc} file.  See the
  variable @code{nntp-authinfo-file} for exact syntax; also see
! @ref{NNTP}.  An example of an .authinfo line for an IMAP server, is:
  
  @example
  machine students.uio.no login larsi password geheimnis port imap
***************
*** 16635,16641 ****
  
  @acronym{IMAP} is a complex protocol, more so than @acronym{NNTP} or
  @acronym{POP3}.  Implementation bugs are not unlikely, and we do our
! best to fix them right away.  If you encounter odd behaviour, chances
  are that either the server or Gnus is buggy.
  
  If you are familiar with network protocols in general, you will
--- 16635,16641 ----
  
  @acronym{IMAP} is a complex protocol, more so than @acronym{NNTP} or
  @acronym{POP3}.  Implementation bugs are not unlikely, and we do our
! best to fix them right away.  If you encounter odd behavior, chances
  are that either the server or Gnus is buggy.
  
  If you are familiar with network protocols in general, you will
***************
*** 16650,16656 ****
  @vindex imap-log
  Because the protocol dump, when enabled, generates lots of data, it is
  disabled by default.  You can enable it by setting @code{imap-log} as
! follows: 
  
  @lisp
  (setq imap-log t)
--- 16650,16656 ----
  @vindex imap-log
  Because the protocol dump, when enabled, generates lots of data, it is
  disabled by default.  You can enable it by setting @code{imap-log} as
! follows:
  
  @lisp
  (setq imap-log t)
***************
*** 18726,18732 ****
  @table @dfn
  @item If I read an article while plugged, do they get entered into the Agent?
  
! @strong{No}.  If you want this behaviour, add
  @code{gnus-agent-fetch-selected-article} to
  @code{gnus-select-article-hook}.
  
--- 18726,18732 ----
  @table @dfn
  @item If I read an article while plugged, do they get entered into the Agent?
  
! @strong{No}.  If you want this behavior, add
  @code{gnus-agent-fetch-selected-article} to
  @code{gnus-select-article-hook}.
  
***************
*** 21012,21018 ****
  
  Gnus usually moves point to a pre-defined place on each line in most
  buffers.  By default, point move to the first colon character on the
! line.  You can customize this behaviour in three different ways.
  
  You can move the colon character to somewhere else on the line.
  
--- 21012,21018 ----
  
  Gnus usually moves point to a pre-defined place on each line in most
  buffers.  By default, point move to the first colon character on the
! line.  You can customize this behavior in three different ways.
  
  You can move the colon character to somewhere else on the line.
  
***************
*** 22361,22367 ****
  @samp{vmadmin.com}.  If you get 200 messages about @samp{VIAGRA}, you
  discard all messages with @samp{VIAGRA} in the message.  If you get
  lots of spam from Bulgaria, for example, you try to filter all mail
! from Bulgarian IPs.  
  
  This, unfortunately, is a great way to discard legitimate e-mail.  The
  risks of blocking a whole country (Bulgaria, Norway, Nigeria, China,
--- 22361,22367 ----
  @samp{vmadmin.com}.  If you get 200 messages about @samp{VIAGRA}, you
  discard all messages with @samp{VIAGRA} in the message.  If you get
  lots of spam from Bulgaria, for example, you try to filter all mail
! from Bulgarian IPs.
  
  This, unfortunately, is a great way to discard legitimate e-mail.  The
  risks of blocking a whole country (Bulgaria, Norway, Nigeria, China,
***************
*** 22704,22725 ****
  group.
  
  @menu
! * Spam ELisp Package Sequence of Events::  
! * Spam ELisp Package Filtering of Incoming Mail::  
! * Spam ELisp Package Global Variables::  
! * Spam ELisp Package Configuration Examples::  
! * Blacklists and Whitelists::   
! * BBDB Whitelists::             
! * Gmane Spam Reporting::        
! * Anti-spam Hashcash Payments::  
! * Blackholes::                  
! * Regular Expressions Header Matching::  
! * Bogofilter::                  
! * ifile spam filtering::        
! * spam-stat spam filtering::    
! * SpamOracle::                  
! * Extending the Spam ELisp package::  
! @end menu 
  
  @node Spam ELisp Package Sequence of Events
  @subsubsection Spam ELisp Package Sequence of Events
--- 22704,22725 ----
  group.
  
  @menu
! * Spam ELisp Package Sequence of Events::
! * Spam ELisp Package Filtering of Incoming Mail::
! * Spam ELisp Package Global Variables::
! * Spam ELisp Package Configuration Examples::
! * Blacklists and Whitelists::
! * BBDB Whitelists::
! * Gmane Spam Reporting::
! * Anti-spam Hashcash Payments::
! * Blackholes::
! * Regular Expressions Header Matching::
! * Bogofilter::
! * ifile spam filtering::
! * spam-stat spam filtering::
! * SpamOracle::
! * Extending the Spam ELisp package::
! @end menu
  
  @node Spam ELisp Package Sequence of Events
  @subsubsection Spam ELisp Package Sequence of Events
***************
*** 23174,23180 ****
   ;; @r{any ham goes to my @samp{nnimap+mail.lifelogs.com:mail} folder, but}
   ;; @r{also to my @samp{nnimap+mail.lifelogs.com:trainham} folder for 
training}
  
!  (ham-process-destination "nnimap+mail.lifelogs.com:mail" 
                            "nnimap+mail.lifelogs.com:trainham")
   ;; @r{in this group, only @samp{!} marks are ham}
   (ham-marks
--- 23174,23180 ----
   ;; @r{any ham goes to my @samp{nnimap+mail.lifelogs.com:mail} folder, but}
   ;; @r{also to my @samp{nnimap+mail.lifelogs.com:trainham} folder for 
training}
  
!  (ham-process-destination "nnimap+mail.lifelogs.com:mail"
                            "nnimap+mail.lifelogs.com:trainham")
   ;; @r{in this group, only @samp{!} marks are ham}
   (ham-marks
***************
*** 23215,23221 ****
      (spam-contents gnus-group-spam-classification-ham))
  @end lisp
  
! @itemize 
  
  @item @b{The Spam folder:}
  
--- 23215,23221 ----
      (spam-contents gnus-group-spam-classification-ham))
  @end lisp
  
! @itemize
  
  @item @b{The Spam folder:}
  
***************
*** 23308,23314 ****
  added to a group's @code{spam-process} parameter, the senders of
  spam-marked articles will be added to the blacklist.
  
! @emph{WARNING} 
  
  Instead of the obsolete
  @code{gnus-group-spam-exit-processor-blacklist}, it is recommended
--- 23308,23314 ----
  added to a group's @code{spam-process} parameter, the senders of
  spam-marked articles will be added to the blacklist.
  
! @emph{WARNING}
  
  Instead of the obsolete
  @code{gnus-group-spam-exit-processor-blacklist}, it is recommended
***************
*** 23327,23333 ****
  whitelist.  Note that this ham processor has no effect in @emph{spam}
  or @emph{unclassified} groups.
  
! @emph{WARNING} 
  
  Instead of the obsolete
  @code{gnus-group-ham-exit-processor-whitelist}, it is recommended
--- 23327,23333 ----
  whitelist.  Note that this ham processor has no effect in @emph{spam}
  or @emph{unclassified} groups.
  
! @emph{WARNING}
  
  Instead of the obsolete
  @code{gnus-group-ham-exit-processor-whitelist}, it is recommended
***************
*** 23393,23399 ****
  BBDB.  Note that this ham processor has no effect in @emph{spam}
  or @emph{unclassified} groups.
  
! @emph{WARNING} 
  
  Instead of the obsolete
  @code{gnus-group-ham-exit-processor-BBDB}, it is recommended
--- 23393,23399 ----
  BBDB.  Note that this ham processor has no effect in @emph{spam}
  or @emph{unclassified} groups.
  
! @emph{WARNING}
  
  Instead of the obsolete
  @code{gnus-group-ham-exit-processor-BBDB}, it is recommended
***************
*** 23420,23426 ****
  
  Gmane can be found at @uref{http://gmane.org}.
  
! @emph{WARNING} 
  
  Instead of the obsolete
  @code{gnus-group-spam-exit-processor-report-gmane}, it is recommended
--- 23420,23426 ----
  
  Gmane can be found at @uref{http://gmane.org}.
  
! @emph{WARNING}
  
  Instead of the obsolete
  @code{gnus-group-spam-exit-processor-report-gmane}, it is recommended
***************
*** 23589,23595 ****
  added to a group's @code{spam-process} parameter, spam-marked articles
  will be added to the Bogofilter spam database.
  
! @emph{WARNING} 
  
  Instead of the obsolete
  @code{gnus-group-spam-exit-processor-bogofilter}, it is recommended
--- 23589,23595 ----
  added to a group's @code{spam-process} parameter, spam-marked articles
  will be added to the Bogofilter spam database.
  
! @emph{WARNING}
  
  Instead of the obsolete
  @code{gnus-group-spam-exit-processor-bogofilter}, it is recommended
***************
*** 23606,23612 ****
  of non-spam messages.  Note that this ham processor has no effect in
  @emph{spam} or @emph{unclassified} groups.
  
! @emph{WARNING} 
  
  Instead of the obsolete
  @code{gnus-group-ham-exit-processor-bogofilter}, it is recommended
--- 23606,23612 ----
  of non-spam messages.  Note that this ham processor has no effect in
  @emph{spam} or @emph{unclassified} groups.
  
! @emph{WARNING}
  
  Instead of the obsolete
  @code{gnus-group-ham-exit-processor-bogofilter}, it is recommended
***************
*** 23693,23699 ****
  added to a group's @code{spam-process} parameter, the spam-marked
  articles will be added to the spam-stat database of spam messages.
  
! @emph{WARNING} 
  
  Instead of the obsolete
  @code{gnus-group-spam-exit-processor-stat}, it is recommended
--- 23693,23699 ----
  added to a group's @code{spam-process} parameter, the spam-marked
  articles will be added to the spam-stat database of spam messages.
  
! @emph{WARNING}
  
  Instead of the obsolete
  @code{gnus-group-spam-exit-processor-stat}, it is recommended
***************
*** 23710,23716 ****
  of non-spam messages.  Note that this ham processor has no effect in
  @emph{spam} or @emph{unclassified} groups.
  
! @emph{WARNING} 
  
  Instead of the obsolete
  @code{gnus-group-ham-exit-processor-stat}, it is recommended
--- 23710,23716 ----
  of non-spam messages.  Note that this ham processor has no effect in
  @emph{spam} or @emph{unclassified} groups.
  
! @emph{WARNING}
  
  Instead of the obsolete
  @code{gnus-group-ham-exit-processor-stat}, it is recommended
***************
*** 23802,23808 ****
  to a group's @code{spam-process} parameter, spam-marked articles will be
  sent to SpamOracle as spam samples.
  
! @emph{WARNING} 
  
  Instead of the obsolete
  @code{gnus-group-spam-exit-processor-spamoracle}, it is recommended
--- 23802,23808 ----
  to a group's @code{spam-process} parameter, spam-marked articles will be
  sent to SpamOracle as spam samples.
  
! @emph{WARNING}
  
  Instead of the obsolete
  @code{gnus-group-spam-exit-processor-spamoracle}, it is recommended
***************
*** 23819,23825 ****
  messages.  Note that this ham processor has no effect in @emph{spam} or
  @emph{unclassified} groups.
  
! @emph{WARNING} 
  
  Instead of the obsolete
  @code{gnus-group-ham-exit-processor-spamoracle}, it is recommended
--- 23819,23825 ----
  messages.  Note that this ham processor has no effect in @emph{spam} or
  @emph{unclassified} groups.
  
! @emph{WARNING}
  
  Instead of the obsolete
  @code{gnus-group-ham-exit-processor-spamoracle}, it is recommended
***************
*** 23914,23920 ****
  provide them if Blackbox supports spam or ham processing.
  
  Also, ham and spam processors are being phased out as single
! variables.  Instead the form @code{'(spam spam-use-blackbox)} or 
  @code{'(ham spam-use-blackbox)} is favored.  For now, spam/ham
  processor variables are still around but they won't be for long.
  
--- 23914,23920 ----
  provide them if Blackbox supports spam or ham processing.
  
  Also, ham and spam processors are being phased out as single
! variables.  Instead the form @code{'(spam spam-use-blackbox)} or
  @code{'(ham spam-use-blackbox)} is favored.  For now, spam/ham
  processor variables are still around but they won't be for long.
  
***************
*** 26140,26146 ****
  @kbd{J r} in the server buffer.  Gnus will not download articles into
  the Agent cache, unless you instruct it to do so, though, by using
  @kbd{J u} or @kbd{J s} from the Group buffer.  You revert to the old
! behaviour of having the Agent disabled with @code{(setq gnus-agent
  nil)}.  Note that putting @code{(gnus-agentize)} in @file{~/.gnus.el}
  is not needed any more.
  
--- 26140,26146 ----
  @kbd{J r} in the server buffer.  Gnus will not download articles into
  the Agent cache, unless you instruct it to do so, though, by using
  @kbd{J u} or @kbd{J s} from the Group buffer.  You revert to the old
! behavior of having the Agent disabled with @code{(setq gnus-agent
  nil)}.  Note that putting @code{(gnus-agentize)} in @file{~/.gnus.el}
  is not needed any more.
  
***************
*** 26280,26286 ****
  system.  While the variable is called @code{canlock-password}, it is not
  security sensitive data.  Publishing your canlock string on the web
  will not allow anyone to be able to anything she could not already do.
! The behaviour can be changed by customizing @code{message-insert-canlock}.
  
  @item
  Gnus supports server-side mail filtering using Sieve.
--- 26280,26286 ----
  system.  While the variable is called @code{canlock-password}, it is not
  security sensitive data.  Publishing your canlock string on the web
  will not allow anyone to be able to anything she could not already do.
! The behavior can be changed by customizing @code{message-insert-canlock}.
  
  @item
  Gnus supports server-side mail filtering using Sieve.
***************
*** 26380,26386 ****
  @item
  The default for @code{message-forward-show-mml} changed to symbol @code{best}.
  
! The behaviour for the @code{best} value is to show @acronym{MML} (i.e.,
  convert to @acronym{MIME}) when appropriate.  @acronym{MML} will not be
  used when forwarding signed or encrypted messages, as the conversion
  invalidate the digital signature.
--- 26380,26386 ----
  @item
  The default for @code{message-forward-show-mml} changed to symbol @code{best}.
  
! The behavior for the @code{best} value is to show @acronym{MML} (i.e.,
  convert to @acronym{MIME}) when appropriate.  @acronym{MML} will not be
  used when forwarding signed or encrypted messages, as the conversion
  invalidate the digital signature.
***************
*** 26905,26911 ****
  edebug.  Debugging Lisp code is documented in the Elisp manual
  (@pxref{Debugging, , Debugging Lisp Programs, elisp, The GNU Emacs
  Lisp Reference Manual}).  To get you started with edebug, consider if
! you discover some weird behaviour when pressing @kbd{c}, the first
  step is to do @kbd{C-h k c} and click on the hyperlink (Emacs only) in
  the documentation buffer that leads you to the function definition,
  then press @kbd{M-x edebug-defun RET} with point inside that function,
--- 26905,26911 ----
  edebug.  Debugging Lisp code is documented in the Elisp manual
  (@pxref{Debugging, , Debugging Lisp Programs, elisp, The GNU Emacs
  Lisp Reference Manual}).  To get you started with edebug, consider if
! you discover some weird behavior when pressing @kbd{c}, the first
  step is to do @kbd{C-h k c} and click on the hyperlink (Emacs only) in
  the documentation buffer that leads you to the function definition,
  then press @kbd{M-x edebug-defun RET} with point inside that function,