xemacs-beta: man/gnus.texi comparison

comparison man/gnus.texi @ 116:9f59509498e1 r20-1b10

Import from CVS: tag r20-1b10

author	cvs
date	Mon, 13 Aug 2007 09:23:06 +0200
parents	8619ce7e4c50
children	7d55a9ba150c

comparison

equal deleted inserted replaced

-:f109f7dabbe2
+:9f59509498e1
 \input texinfo                  @c -*-texinfo-*-
 @setfilename gnus
-@settitle Gnus 5.4.33 Manual
+@settitle Gnus 5.4.37 Manual
 @synindex fn cp
 @synindex vr cp
 @synindex pg cp
 @iftex
 @finalout
 @end ifinfo
 @tex
 @titlepage
-@title Gnus 5.4.33 Manual
+@title Gnus 5.4.37 Manual
 @author by Lars Magne Ingebrigtsen
 @page
 @vskip 0pt plus 1filll
 You can read news (and mail) from within Emacs by using Gnus.  The news
 can be gotten by any nefarious means you can think of---@sc{nntp}, local
 spool or your mbox file.  All at the same time, if you want to push your
 luck.
-This manual corresponds to Gnus 5.4.33.
+This manual corresponds to Gnus 5.4.37.
 @end ifinfo
 @iftex
 will tell you, without making the least effort to see whether that is
 actually the case or not.
 That might seem quite naughty, but it does make sense most of the time.
 Let's say you have 10 groups subscribed to the server
-@samp{nepholococcygia.com}.  This server is located somewhere quite far
+@samp{nephelococcygia.com}.  This server is located somewhere quite far
-away from you, the machine is quite, so it takes 1 minute just to find
+away from you and the machine is quite slow, so it takes 1 minute just
-out that it refuses connection from you today.  If Gnus were to attempt
+to find out that it refuses connection from you today.  If Gnus were to
-to do that 10 times, you'd be quite annoyed, so Gnus won't attempt to do
+attempt to do that 10 times, you'd be quite annoyed, so Gnus won't
-that.  Once it has gotten a single ``connection refused'', it will
+attempt to do that.  Once it has gotten a single ``connection refused'',
-regard that server as ``down''.
+it will regard that server as ``down''.
 So, what happens if the machine was only feeling unwell temporarily?
 How do you test to see whether the machine has come up again?
 You jump to the server buffer (@pxref{The Server Buffer}) and poke it
 ("subject" "ding" "ding.misc"))
 ;; Other mailing lists...
 (any "procmail@@informatik\\.rwth-aachen\\.de" "procmail.list")
 (any "SmartList@@informatik\\.rwth-aachen\\.de" "SmartList.list")
 ;; People...
-(any "larsi@@ifi\\.uio\\.no" "people.Lars Magne Ingebrigtsen"))
+(any "larsi@@ifi\\.uio\\.no" "people.Lars_Magne_Ingebrigtsen"))
 ;; Unmatched mail goes to the catch all group.
 "misc.misc")
 @end lisp
 This variable has the format of a @dfn{split}.  A split is a (possibly)
 * Picons::                     How to display pictures of what your reading.
 * Undo::                       Some actions can be undone.
 * Moderation::                 What to do if you're a moderator.
 * XEmacs Enhancements::        There are more pictures and stuff under XEmacs.
 * Fuzzy Matching::             What's the big fuzz?
+* Thwarting Email Spam::       A how-to on avoiding unsolited commercial email.
 * Various Various::            Things that are really various.
 @end menu
 @node Process/Prefix
 daemons, you can use the @code{gnus-demon-cancel} function.
 Note that adding daemons can be pretty naughty if you overdo it.  Adding
 functions that scan all news and mail from all servers every two seconds
 is a sure-fire way of getting booted off any respectable system.  So
 behave.
 @node NoCeM
 @section NoCeM
 @cindex nocem
 Basically, it tries to remove all noise from lines before comparing.
 @samp{Re: }, parenthetical remarks, white space, and so on, are filtered
 out of the strings before comparing the results.  This often leads to
 adequate results---even when faced with strings generated by text
 manglers masquerading as newsreaders.
+@node Thwarting Email Spam
+@section Thwarting Email Spam
+@cindex email spam
+@cindex spam
+@cindex UCE
+@cindex unsolicited commercial email
+In these last days of the Usenet, commercial vultures are hanging about
+and grepping through news like crazy to find email addresses they can
+foist off their scams and products to.  As a reaction to this, many
+people have started putting nonsense addresses into their @code{From}
+lines.  I think this is counterproductive---it makes it difficult for
+people to send you legitimate mail in response to things you write, as
+well as making it difficult to see who wrote what.  This rewriting may
+perhaps be a bigger menace than the unsolicited commercial email itself
+in the end.
+The biggest problem I have with email spam is that it comes in under
+false pretenses.  I press @kbd{g} and Gnus merrily informs me that I
+have 10 new emails.  I say ``Golly gee!  Happy is me!'' and selects the
+mail group, only to find two pyramid schemes, seven advertisements
+``New!  Miracle tonic for growing full, lustrouos hair on your toes!''
+and one mail asking me to repent and find some god.
+This is annoying.
+The way to deal with this is having Gnus split out all spam into a
+@samp{spam} mail group (@pxref{Splitting Mail}).
+First, pick one (1) legal mail address that you can be reached at, and
+put it in your @code{From} header of all your news articles.  (I've
+chosen @samp{larsi@@trym.ifi.uio.no}.)
+@lisp
+(setq message-default-news-headers
+"From: Lars Magne Ingebrigtsen <larsi@@trym.ifi.uio.no>\n")
+@end lisp
+Then put the following split rule in @code{nnmail-split-fancy}
+(@pxref{Fancy Mail Splitting}):
+@lisp
+(
+...
+(to "larsi@@trym.ifi.uio.no"
+(| ("subject" "re:.*" "misc")
+("references" ".*@@.*" "misc")
+"spam"))
+...
+)
+@end lisp
+This says that all mail to this address is suspect, but if it has a
+@code{Subject} that starts with a @samp{Re:} or has a @code{References}
+header, it's probably ok.  All the rest goes to the @samp{spam} group.
+(This idea probably comes from Tim Pierce.)
+In my experience, this will sort virtually everything into the right
+group.  You still have to check the @samp{spam} group from time to time to
+check for legitimate mail, though.  If you feel like being a good net
+citizen, you can even send off complaints to the proper authorities on
+each unsolicited commercial email---at your leisure.
+This works for me.  It allows people an easy way to contact me (they can
+just press @kbd{r} in the usual way), and I'm not bothered at all with
+spam.  It's a win-win situation.  Forging @code{From} headers to point
+to non-existant domains is yucky, in my opinion.
 @node Various Various
 @section Various Various
 @cindex mode lines

Mercurial > hg > xemacs-beta

comparison man/gnus.texi @ 116:9f59509498e1 r20-1b10