4 @settitle T-gnus 6.17 Manual
9 @documentencoding ISO-8859-1
12 Copyright (c) 1995, 1996, 1997, 1998, 1999, 2000, 2001,
13 2002, 2003, 2004, 2005
14 Free Software Foundation, Inc.
17 Permission is granted to copy, distribute and/or modify this document
18 under the terms of the GNU Free Documentation License, Version 1.1 or
19 any later version published by the Free Software Foundation; with no
20 Invariant Sections, with the Front-Cover texts being ``A GNU
21 Manual'', and with the Back-Cover Texts as in (a) below. A copy of the
22 license is included in the section entitled ``GNU Free Documentation
23 License'' in the Emacs manual.
25 (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
26 this GNU Manual, like GNU software. Copies published by the Free
27 Software Foundation raise funds for GNU development.''
29 This document is part of a collection distributed under the GNU Free
30 Documentation License. If you want to distribute this document
31 separately from the collection, you can do so by adding a copy of the
32 license to the document, as described in section 6 of the license.
38 \documentclass[twoside,a4paper,openright,11pt]{book}
39 \usepackage[latin1]{inputenc}
40 \usepackage{pagestyle}
43 \input{gnusconfig.tex}
45 \ifx\pdfoutput\undefined
47 \usepackage[pdftex,bookmarks,colorlinks=true]{hyperref}
55 \newcommand{\gnusversionname}{T-gnus v6.17}
56 \newcommand{\gnuschaptername}{}
57 \newcommand{\gnussectionname}{}
59 \newcommand{\gnusbackslash}{/}
61 \newcommand{\gnusref}[1]{``#1'' on page \pageref{#1}}
62 \ifx\pdfoutput\undefined
63 \newcommand{\gnusuref}[1]{\gnustt{#1}}
65 \newcommand{\gnusuref}[1]{\href{#1}{\gnustt{#1}}}
67 \newcommand{\gnusxref}[1]{See ``#1'' on page \pageref{#1}}
68 \newcommand{\gnuspxref}[1]{see ``#1'' on page \pageref{#1}}
70 \newcommand{\gnuskindex}[1]{\index{#1}}
71 \newcommand{\gnusindex}[1]{\index{#1}}
73 \newcommand{\gnustt}[1]{{\gnusselectttfont{}#1}}
74 \newcommand{\gnuscode}[1]{\gnustt{#1}}
75 \newcommand{\gnusasis}[1]{\gnustt{#1}}
76 \newcommand{\gnusurl}[1]{\gnustt{#1}}
77 \newcommand{\gnuscommand}[1]{\gnustt{#1}}
78 \newcommand{\gnusenv}[1]{\gnustt{#1}}
79 \newcommand{\gnussamp}[1]{``{\fontencoding{OT1}\gnusselectttfont{}#1}''}
80 \newcommand{\gnuslisp}[1]{\gnustt{#1}}
81 \newcommand{\gnuskbd}[1]{`\gnustt{#1}'}
82 \newcommand{\gnuskey}[1]{`\gnustt{#1}'}
83 \newcommand{\gnusfile}[1]{`\gnustt{#1}'}
84 \newcommand{\gnusdfn}[1]{\textit{#1}}
85 \newcommand{\gnusi}[1]{\textit{#1}}
86 \newcommand{\gnusr}[1]{\textrm{#1}}
87 \newcommand{\gnusstrong}[1]{\textbf{#1}}
88 \newcommand{\gnusemph}[1]{\textit{#1}}
89 \newcommand{\gnusvar}[1]{{\fontsize{10pt}{10}\selectfont\textsl{\textsf{#1}}}}
90 \newcommand{\gnussc}[1]{\textsc{#1}}
91 \newcommand{\gnustitle}[1]{{\huge\textbf{#1}}}
92 \newcommand{\gnusversion}[1]{{\small\textit{#1}}}
93 \newcommand{\gnusauthor}[1]{{\large\textbf{#1}}}
94 \newcommand{\gnusresult}[1]{\gnustt{=> #1}}
95 \newcommand{\gnusacronym}[1]{\textsc{#1}}
96 \newcommand{\gnusemail}[1]{\textit{#1}}
98 \newcommand{\gnusbullet}{{${\bullet}$}}
99 \newcommand{\gnusdollar}{\$}
100 \newcommand{\gnusampersand}{\&}
101 \newcommand{\gnuspercent}{\%}
102 \newcommand{\gnushash}{\#}
103 \newcommand{\gnushat}{\symbol{"5E}}
104 \newcommand{\gnusunderline}{\symbol{"5F}}
105 \newcommand{\gnusnot}{$\neg$}
106 \newcommand{\gnustilde}{\symbol{"7E}}
107 \newcommand{\gnusless}{{$<$}}
108 \newcommand{\gnusgreater}{{$>$}}
109 \newcommand{\gnusbraceleft}{{$>$}}
110 \newcommand{\gnusbraceright}{{$>$}}
112 \newcommand{\gnushead}{\raisebox{-1cm}{\epsfig{figure=ps/gnus-head,height=1cm}}}
113 \newcommand{\gnusinteresting}{
114 \marginpar[\mbox{}\hfill\gnushead]{\gnushead}
117 \newcommand{\gnuscleardoublepage}{\ifodd\count0\mbox{}\clearpage\thispagestyle{empty}\mbox{}\clearpage\else\clearpage\fi}
119 \newcommand{\gnuspagechapter}[1]{
123 \newdimen{\gnusdimen}
126 \newcommand{\gnuschapter}[2]{
128 \ifdim \gnusdimen = 0pt\setcounter{page}{1}\pagestyle{gnus}\pagenumbering{arabic} \gnusdimen 1pt\fi
130 \renewcommand{\gnussectionname}{}
131 \renewcommand{\gnuschaptername}{#2}
132 \thispagestyle{empty}
134 \begin{picture}(500,500)(0,0)
135 \put(480,350){\makebox(0,0)[tr]{#1}}
136 \put(40,300){\makebox(500,50)[bl]{{\Huge\bf{#2}}}}
141 \newcommand{\gnusfigure}[3]{
143 \mbox{}\ifodd\count0\hspace*{-0.8cm}\else\hspace*{-3cm}\fi\begin{picture}(440,#2)
150 \newcommand{\gnusicon}[1]{
151 \marginpar[\mbox{}\hfill\raisebox{-1.5cm}{\epsfig{figure=ps/#1-up,height=1.5cm}}]{\raisebox{-1cm}{\epsfig{figure=ps/#1-up,height=1cm}}}
154 \newcommand{\gnuspicon}[1]{
155 \margindex{\epsfig{figure=#1,width=2cm}}
158 \newcommand{\gnusxface}[2]{
159 \margindex{\epsfig{figure=#1,width=1cm}\epsfig{figure=#2,width=1cm}}
162 \newcommand{\gnussmiley}[2]{
163 \margindex{\makebox[2cm]{\hfill\epsfig{figure=#1,width=0.5cm}\hfill\epsfig{figure=#2,width=0.5cm}\hfill}}
166 \newcommand{\gnusitemx}[1]{\mbox{}\vspace*{-\itemsep}\vspace*{-\parsep}\item#1}
168 \newcommand{\gnussection}[1]{
169 \renewcommand{\gnussectionname}{#1}
173 \newenvironment{codelist}%
178 \newenvironment{asislist}%
183 \newenvironment{kbdlist}%
189 \newenvironment{dfnlist}%
194 \newenvironment{stronglist}%
199 \newenvironment{samplist}%
204 \newenvironment{varlist}%
209 \newenvironment{emphlist}%
214 \newlength\gnusheadtextwidth
215 \setlength{\gnusheadtextwidth}{\headtextwidth}
216 \addtolength{\gnusheadtextwidth}{1cm}
218 \newpagestyle{gnuspreamble}%
223 \hspace*{-0.23cm}\underline{\makebox[\gnusheadtextwidth]{\mbox{}}\textbf{\hfill\roman{page}}}
227 \hspace*{-3.25cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\roman{page}\hfill\mbox{}}}
236 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
238 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
243 \newpagestyle{gnusindex}%
248 \hspace*{-0.23cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\gnuschaptername\hfill\arabic{page}}}}
252 \hspace*{-3.25cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{page}\hfill\gnuschaptername}}}
260 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
262 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
272 \makebox[12cm]{\hspace*{3.1cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{chapter}.\arabic{section}} \textbf{\gnussectionname\hfill\arabic{page}}}}}
276 \makebox[12cm]{\hspace*{-2.95cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{page}\hfill\gnuschaptername}}}}
284 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
286 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
291 \pagenumbering{roman}
292 \pagestyle{gnuspreamble}
303 %\addtolength{\oddsidemargin}{-5cm}
304 %\addtolength{\evensidemargin}{-5cm}
306 \addtolength{\textheight}{2cm}
308 \gnustitle{\gnustitlename}\hfill\gnusversion{\gnusversionname}\\
311 \hspace*{0cm}\epsfig{figure=ps/gnus-big-logo,height=15cm}
314 \gnusauthor{by Lars Magne Ingebrigtsen}
321 \thispagestyle{empty}
335 * Gnus: (gnus). The newsreader Gnus.
340 @setchapternewpage odd
345 @title T-gnus 6.17 Manual
347 @author by Lars Magne Ingebrigtsen
349 @vskip 0pt plus 1filll
355 @top The gnus Newsreader
359 You can read news (and mail) from within Emacs by using T-gnus. The news
360 can be gotten by any nefarious means you can think of---@acronym{NNTP}, local
361 spool or your mbox file. All at the same time, if you want to push your
364 T-gnus provides @acronym{MIME} features based on @acronym{SEMI} API. So
365 T-gnus supports your right to read strange messages including big images
366 or other various kinds of formats. T-gnus also supports
367 internationalization/localization and multiscript features based on MULE
368 API. So T-gnus does not discriminate various language communities. Oh,
369 if you are a Klingon, please wait Unicode Next Generation.
371 This manual corresponds to T-gnus 6.17.
382 Gnus is the advanced, self-documenting, customizable, extensible
383 unreal-time newsreader for GNU Emacs.
385 Oops. That sounds oddly familiar, so let's start over again to avoid
386 being accused of plagiarism:
388 Gnus is a message-reading laboratory. It will let you look at just
389 about anything as if it were a newsgroup. You can read mail with it,
390 you can browse directories with it, you can @code{ftp} with it---you
391 can even read news with it!
393 Gnus tries to empower people who read news the same way Emacs empowers
394 people who edit text. Gnus sets no limits to what the user should be
395 allowed to do. Users are encouraged to extend gnus to make it behave
396 like they want it to behave. A program should not control people;
397 people should be empowered to do what they want by using (or abusing)
403 * Starting Up:: Finding news can be a pain.
404 * Group Buffer:: Selecting, subscribing and killing groups.
405 * Summary Buffer:: Reading, saving and posting articles.
406 * Article Buffer:: Displaying and handling articles.
407 * Composing Messages:: Information on sending mail and news.
408 * Select Methods:: Gnus reads all messages from various select methods.
409 * Scoring:: Assigning values to articles.
410 * Various:: General purpose settings.
411 * The End:: Farewell and goodbye.
412 * Appendices:: Terminology, Emacs intro, @acronym{FAQ}, History, Internals.
413 * Index:: Variable, function and concept index.
414 * Key Index:: Key Index.
416 Other related manuals
418 * Message:(message). Composing messages.
419 * Emacs-MIME:(emacs-mime). Composing messages; @acronym{MIME}-specific parts.
420 * Sieve:(sieve). Managing Sieve scripts in Emacs.
421 * PGG:(pgg). @acronym{PGP/MIME} with Gnus.
422 * SASL:(sasl). @acronym{SASL} authentication in Emacs.
425 --- The Detailed Node Listing ---
429 * Finding the News:: Choosing a method for getting news.
430 * The First Time:: What does Gnus do the first time you start it?
431 * The Server is Down:: How can I read my mail then?
432 * Slave Gnusae:: You can have more than one Gnus active at a time.
433 * Fetching a Group:: Starting Gnus just to read a group.
434 * New Groups:: What is Gnus supposed to do with new groups?
435 * Changing Servers:: You may want to move from one server to another.
436 * Startup Files:: Those pesky startup files---@file{.newsrc}.
437 * Auto Save:: Recovering from a crash.
438 * The Active File:: Reading the active file over a slow line Takes Time.
439 * Startup Variables:: Other variables you might change.
443 * Checking New Groups:: Determining what groups are new.
444 * Subscription Methods:: What Gnus should do with new groups.
445 * Filtering New Groups:: Making Gnus ignore certain new groups.
449 * Group Buffer Format:: Information listed and how you can change it.
450 * Group Maneuvering:: Commands for moving in the group buffer.
451 * Selecting a Group:: Actually reading news.
452 * Subscription Commands:: Unsubscribing, killing, subscribing.
453 * Group Data:: Changing the info for a group.
454 * Group Levels:: Levels? What are those, then?
455 * Group Score:: A mechanism for finding out what groups you like.
456 * Marking Groups:: You can mark groups for later processing.
457 * Foreign Groups:: Creating and editing groups.
458 * Group Parameters:: Each group may have different parameters set.
459 * Listing Groups:: Gnus can list various subsets of the groups.
460 * Sorting Groups:: Re-arrange the group order.
461 * Group Maintenance:: Maintaining a tidy @file{.newsrc} file.
462 * Browse Foreign Server:: You can browse a server. See what it has to offer.
463 * Exiting Gnus:: Stop reading news and get some work done.
464 * Group Topics:: A folding group mode divided into topics.
465 * Misc Group Stuff:: Other stuff that you can to do.
469 * Group Line Specification:: Deciding how the group buffer is to look.
470 * Group Mode Line Specification:: The group buffer mode line.
471 * Group Highlighting:: Having nice colors in the group buffer.
475 * Topic Commands:: Interactive E-Z commands.
476 * Topic Variables:: How to customize the topics the Lisp Way.
477 * Topic Sorting:: Sorting each topic individually.
478 * Topic Topology:: A map of the world.
479 * Topic Parameters:: Parameters that apply to all groups in a topic.
483 * Scanning New Messages:: Asking Gnus to see whether new messages have arrived.
484 * Group Information:: Information and help on groups and Gnus.
485 * Group Timestamp:: Making Gnus keep track of when you last read a group.
486 * File Commands:: Reading and writing the Gnus files.
487 * Sieve Commands:: Managing Sieve scripts.
491 * Summary Buffer Format:: Deciding how the summary buffer is to look.
492 * Summary Maneuvering:: Moving around the summary buffer.
493 * Choosing Articles:: Reading articles.
494 * Paging the Article:: Scrolling the current article.
495 * Reply Followup and Post:: Posting articles.
496 * Delayed Articles:: Send articles at a later time.
497 * Marking Articles:: Marking articles as read, expirable, etc.
498 * Limiting:: You can limit the summary buffer.
499 * Threading:: How threads are made.
500 * Sorting the Summary Buffer:: How articles and threads are sorted.
501 * Asynchronous Fetching:: Gnus might be able to pre-fetch articles.
502 * Article Caching:: You may store articles in a cache.
503 * Persistent Articles:: Making articles expiry-resistant.
504 * Article Backlog:: Having already read articles hang around.
505 * Saving Articles:: Ways of customizing article saving.
506 * Decoding Articles:: Gnus can treat series of (uu)encoded articles.
507 * Article Treatment:: The article buffer can be mangled at will.
508 * MIME Commands:: Doing MIMEy things with the articles.
509 * Charsets:: Character set issues.
510 * Article Commands:: Doing various things with the article buffer.
511 * Summary Sorting:: Sorting the summary buffer in various ways.
512 * Finding the Parent:: No child support? Get the parent.
513 * Alternative Approaches:: Reading using non-default summaries.
514 * Tree Display:: A more visual display of threads.
515 * Mail Group Commands:: Some commands can only be used in mail groups.
516 * Various Summary Stuff:: What didn't fit anywhere else.
517 * Exiting the Summary Buffer:: Returning to the Group buffer,
518 or reselecting the current group.
519 * Crosspost Handling:: How crossposted articles are dealt with.
520 * Duplicate Suppression:: An alternative when crosspost handling fails.
521 * Security:: Decrypt and Verify.
522 * Mailing List:: Mailing list minor mode.
524 Summary Buffer Format
526 * Summary Buffer Lines:: You can specify how summary lines should look.
527 * To From Newsgroups:: How to not display your own name.
528 * Summary Buffer Mode Line:: You can say how the mode line should look.
529 * Summary Highlighting:: Making the summary buffer all pretty and nice.
533 * Choosing Commands:: Commands for choosing articles.
534 * Choosing Variables:: Variables that influence these commands.
536 Reply, Followup and Post
538 * Summary Mail Commands:: Sending mail.
539 * Summary Post Commands:: Sending news.
540 * Summary Message Commands:: Other Message-related commands.
541 * Canceling and Superseding::
545 * Unread Articles:: Marks for unread articles.
546 * Read Articles:: Marks for read articles.
547 * Other Marks:: Marks that do not affect readedness.
548 * Setting Marks:: How to set and remove marks.
549 * Generic Marking Commands:: How to customize the marking.
550 * Setting Process Marks:: How to mark articles for later processing.
554 * Customizing Threading:: Variables you can change to affect the threading.
555 * Thread Commands:: Thread based commands in the summary buffer.
557 Customizing Threading
559 * Loose Threads:: How Gnus gathers loose threads into bigger threads.
560 * Filling In Threads:: Making the threads displayed look fuller.
561 * More Threading:: Even more variables for fiddling with threads.
562 * Low-Level Threading:: You thought it was over@dots{} but you were wrong!
566 * Uuencoded Articles:: Uudecode articles.
567 * Shell Archives:: Unshar articles.
568 * PostScript Files:: Split PostScript.
569 * Other Files:: Plain save and binhex.
570 * Decoding Variables:: Variables for a happy decoding.
571 * Viewing Files:: You want to look at the result of the decoding?
575 * Rule Variables:: Variables that say how a file is to be viewed.
576 * Other Decode Variables:: Other decode variables.
577 * Uuencoding and Posting:: Variables for customizing uuencoding.
581 * Article Highlighting:: You want to make the article look like fruit salad.
582 * Article Fontisizing:: Making emphasized text look nice.
583 * Article Hiding:: You also want to make certain info go away.
584 * Article Washing:: Lots of way-neat functions to make life better.
585 * Article Header:: Doing various header transformations.
586 * Article Buttons:: Click on URLs, Message-IDs, addresses and the like.
587 * Article Button Levels:: Controlling appearance of buttons.
588 * Article Date:: Grumble, UT!
589 * Article Display:: Display various stuff---X-Face, Picons, Smileys
590 * Article Signature:: What is a signature?
591 * Article Miscellanea:: Various other stuff.
593 Alternative Approaches
595 * Pick and Read:: First mark articles and then read them.
596 * Binary Groups:: Auto-decode all articles.
598 Various Summary Stuff
600 * Summary Group Information:: Information oriented commands.
601 * Searching for Articles:: Multiple article commands.
602 * Summary Generation Commands::
603 * Really Various Summary Commands:: Those pesky non-conformant commands.
607 * Hiding Headers:: Deciding what headers should be displayed.
608 * Using MIME:: Pushing articles through @acronym{MIME} before reading them.
609 * Customizing Articles:: Tailoring the look of the articles.
610 * Article Keymap:: Keystrokes available in the article buffer.
611 * Misc Article:: Other stuff.
615 * Mail:: Mailing and replying.
616 * Posting Server:: What server should you post and mail via?
617 * POP before SMTP:: You cannot send a mail unless you read a mail.
618 * Mail and Post:: Mailing and posting at the same time.
619 * Archived Messages:: Where Gnus stores the messages you've sent.
620 * Posting Styles:: An easier way to specify who you are.
621 * Drafts:: Postponing messages and rejected messages.
622 * Rejected Articles:: What happens if the server doesn't like your article?
623 * Signing and encrypting:: How to compose secure messages.
627 * Server Buffer:: Making and editing virtual servers.
628 * Getting News:: Reading USENET news with Gnus.
629 * Getting Mail:: Reading your personal mail with Gnus.
630 * Browsing the Web:: Getting messages from a plethora of Web sources.
631 * IMAP:: Using Gnus as a @acronym{IMAP} client.
632 * Other Sources:: Reading directories, files, SOUP packets.
633 * Combined Groups:: Combining groups into one group.
634 * Gnus Unplugged:: Reading news and mail offline.
638 * Server Buffer Format:: You can customize the look of this buffer.
639 * Server Commands:: Commands to manipulate servers.
640 * Example Methods:: Examples server specifications.
641 * Creating a Virtual Server:: An example session.
642 * Server Variables:: Which variables to set.
643 * Servers and Methods:: You can use server names as select methods.
644 * Unavailable Servers:: Some servers you try to contact may be down.
648 * NNTP:: Reading news from an @acronym{NNTP} server.
649 * News Spool:: Reading news from the local spool.
653 * Direct Functions:: Connecting directly to the server.
654 * Indirect Functions:: Connecting indirectly to the server.
655 * Common Variables:: Understood by several connection functions.
656 * NNTP marks:: Storing marks for @acronym{NNTP} servers.
660 * Mail in a Newsreader:: Important introductory notes.
661 * Getting Started Reading Mail:: A simple cookbook example.
662 * Splitting Mail:: How to create mail groups.
663 * Mail Sources:: How to tell Gnus where to get mail from.
664 * Mail Back End Variables:: Variables for customizing mail handling.
665 * Fancy Mail Splitting:: Gnus can do hairy splitting of incoming mail.
666 * Group Mail Splitting:: Use group customize to drive mail splitting.
667 * Incorporating Old Mail:: What about the old mail you have?
668 * Expiring Mail:: Getting rid of unwanted mail.
669 * Washing Mail:: Removing cruft from the mail you get.
670 * Duplicates:: Dealing with duplicated mail.
671 * Not Reading Mail:: Using mail back ends for reading other files.
672 * Choosing a Mail Back End:: Gnus can read a variety of mail formats.
676 * Mail Source Specifiers:: How to specify what a mail source is.
677 * Mail Source Customization:: Some variables that influence things.
678 * Fetching Mail:: Using the mail source specifiers.
680 Choosing a Mail Back End
682 * Unix Mail Box:: Using the (quite) standard Un*x mbox.
683 * Rmail Babyl:: Emacs programs use the Rmail Babyl format.
684 * Mail Spool:: Store your mail in a private spool?
685 * MH Spool:: An mhspool-like back end.
686 * Maildir:: Another one-file-per-message format.
687 * Mail Folders:: Having one file for each group.
688 * Comparing Mail Back Ends:: An in-depth looks at pros and cons.
693 * Web Searches:: Creating groups from articles that match a string.
694 * Slashdot:: Reading the Slashdot comments.
695 * Ultimate:: The Ultimate Bulletin Board systems.
696 * Web Archive:: Reading mailing list archived on web.
697 * RSS:: Reading RDF site summary.
698 * Customizing w3:: Doing stuff to Emacs/w3 from Gnus.
702 * Splitting in IMAP:: Splitting mail with nnimap.
703 * Expiring in IMAP:: Expiring mail with nnimap.
704 * Editing IMAP ACLs:: Limiting/enabling other users access to a mailbox.
705 * Expunging mailboxes:: Equivalent of a ``compress mailbox'' button.
706 * A note on namespaces:: How to (not) use @acronym{IMAP} namespace in Gnus.
707 * Debugging IMAP:: What to do when things don't work.
711 * Directory Groups:: You can read a directory as if it was a newsgroup.
712 * Anything Groups:: Dired? Who needs dired?
713 * Document Groups:: Single files can be the basis of a group.
714 * SOUP:: Reading @sc{soup} packets ``offline''.
715 * Mail-To-News Gateways:: Posting articles via mail-to-news gateways.
719 * Document Server Internals:: How to add your own document types.
723 * SOUP Commands:: Commands for creating and sending @sc{soup} packets
724 * SOUP Groups:: A back end for reading @sc{soup} packets.
725 * SOUP Replies:: How to enable @code{nnsoup} to take over mail and news.
729 * Virtual Groups:: Combining articles from many groups.
730 * Kibozed Groups:: Looking through parts of the newsfeed for articles.
734 * Agent Basics:: How it all is supposed to work.
735 * Agent Categories:: How to tell the Gnus Agent what to download.
736 * Agent Commands:: New commands for all the buffers.
737 * Agent Visuals:: Ways that the agent may effect your summary buffer.
738 * Agent as Cache:: The Agent is a big cache too.
739 * Agent Expiry:: How to make old articles go away.
740 * Agent Regeneration:: How to recover from lost connections and other accidents.
741 * Agent and IMAP:: How to use the Agent with @acronym{IMAP}.
742 * Outgoing Messages:: What happens when you post/mail something?
743 * Agent Variables:: Customizing is fun.
744 * Example Setup:: An example @file{~/.gnus.el} file for offline people.
745 * Batching Agents:: How to fetch news from a @code{cron} job.
746 * Agent Caveats:: What you think it'll do and what it does.
750 * Category Syntax:: What a category looks like.
751 * Category Buffer:: A buffer for maintaining categories.
752 * Category Variables:: Customize'r'Us.
756 * Group Agent Commands:: Configure groups and fetch their contents.
757 * Summary Agent Commands:: Manually select then fetch specific articles.
758 * Server Agent Commands:: Select the servers that are supported by the agent.
762 * Summary Score Commands:: Adding score entries for the current group.
763 * Group Score Commands:: General score commands.
764 * Score Variables:: Customize your scoring. (My, what terminology).
765 * Score File Format:: What a score file may contain.
766 * Score File Editing:: You can edit score files by hand as well.
767 * Adaptive Scoring:: Big Sister Gnus knows what you read.
768 * Home Score File:: How to say where new score entries are to go.
769 * Followups To Yourself:: Having Gnus notice when people answer you.
770 * Scoring On Other Headers:: Scoring on non-standard headers.
771 * Scoring Tips:: How to score effectively.
772 * Reverse Scoring:: That problem child of old is not problem.
773 * Global Score Files:: Earth-spanning, ear-splitting score files.
774 * Kill Files:: They are still here, but they can be ignored.
775 * Converting Kill Files:: Translating kill files to score files.
776 * Advanced Scoring:: Using logical expressions to build score rules.
777 * Score Decays:: It can be useful to let scores wither away.
781 * Advanced Scoring Syntax:: A definition.
782 * Advanced Scoring Examples:: What they look like.
783 * Advanced Scoring Tips:: Getting the most out of it.
787 * Process/Prefix:: A convention used by many treatment commands.
788 * Interactive:: Making Gnus ask you many questions.
789 * Symbolic Prefixes:: How to supply some Gnus functions with options.
790 * Formatting Variables:: You can specify what buffers should look like.
791 * Window Layout:: Configuring the Gnus buffer windows.
792 * Faces and Fonts:: How to change how faces look.
793 * Compilation:: How to speed Gnus up.
794 * Mode Lines:: Displaying information in the mode lines.
795 * Highlighting and Menus:: Making buffers look all nice and cozy.
796 * Buttons:: Get tendinitis in ten easy steps!
797 * Daemons:: Gnus can do things behind your back.
798 * NoCeM:: How to avoid spam and other fatty foods.
799 * Undo:: Some actions can be undone.
800 * Predicate Specifiers:: Specifying predicates.
801 * Moderation:: What to do if you're a moderator.
802 * Image Enhancements:: Modern versions of Emacs/XEmacs can display images.
803 * Fuzzy Matching:: What's the big fuzz?
804 * Thwarting Email Spam:: A how-to on avoiding unsolicited commercial email.
805 * Other modes:: Interaction with other modes.
806 * Various Various:: Things that are really various.
810 * Formatting Basics:: A formatting variable is basically a format string.
811 * Mode Line Formatting:: Some rules about mode line formatting variables.
812 * Advanced Formatting:: Modifying output in various ways.
813 * User-Defined Specs:: Having Gnus call your own functions.
814 * Formatting Fonts:: Making the formatting look colorful and nice.
815 * Positioning Point:: Moving point to a position after an operation.
816 * Tabulation:: Tabulating your output.
817 * Wide Characters:: Dealing with wide characters.
821 * X-Face:: Display a funky, teensy black-and-white image.
822 * Face:: Display a funkier, teensier colored image.
823 * Smileys:: Show all those happy faces the way they were meant to be shown.
824 * Picons:: How to display pictures of what you're reading.
825 * XVarious:: Other XEmacsy Gnusey variables.
829 * The problem of spam:: Some background, and some solutions
830 * Anti-Spam Basics:: Simple steps to reduce the amount of spam.
831 * SpamAssassin:: How to use external anti-spam tools.
832 * Hashcash:: Reduce spam by burning CPU time.
833 * Filtering Spam Using The Spam ELisp Package::
834 * Filtering Spam Using Statistics with spam-stat::
836 Filtering Spam Using The Spam ELisp Package
838 * Spam ELisp Package Sequence of Events::
839 * Spam ELisp Package Filtering of Incoming Mail::
840 * Spam ELisp Package Global Variables::
841 * Spam ELisp Package Configuration Examples::
842 * Blacklists and Whitelists::
844 * Gmane Spam Reporting::
845 * Anti-spam Hashcash Payments::
847 * Regular Expressions Header Matching::
849 * SpamAssassin back end::
850 * ifile spam filtering::
851 * spam-stat spam filtering::
853 * Extending the Spam ELisp package::
855 Filtering Spam Using Statistics with spam-stat
857 * Creating a spam-stat dictionary::
858 * Splitting mail using spam-stat::
859 * Low-level interface to the spam-stat dictionary::
863 * XEmacs:: Requirements for installing under XEmacs.
864 * History:: How Gnus got where it is today.
865 * On Writing Manuals:: Why this is not a beginner's guide.
866 * Terminology:: We use really difficult, like, words here.
867 * Customization:: Tailoring Gnus to your needs.
868 * Troubleshooting:: What you might try if things do not work.
869 * Gnus Reference Guide:: Rilly, rilly technical stuff.
870 * Emacs for Heathens:: A short introduction to Emacsian terms.
871 * Frequently Asked Questions:: The Gnus FAQ
875 * Gnus Versions:: What Gnus versions have been released.
876 * Other Gnus Versions:: Other Gnus versions that also have been released.
877 * Why?:: What's the point of Gnus?
878 * Compatibility:: Just how compatible is Gnus with @sc{gnus}?
879 * Conformity:: Gnus tries to conform to all standards.
880 * Emacsen:: Gnus can be run on a few modern Emacsen.
881 * Gnus Development:: How Gnus is developed.
882 * Contributors:: Oodles of people.
883 * New Features:: Pointers to some of the new stuff in Gnus.
887 * ding Gnus:: New things in Gnus 5.0/5.1, the first new Gnus.
888 * September Gnus:: The Thing Formally Known As Gnus 5.2/5.3.
889 * Red Gnus:: Third time best---Gnus 5.4/5.5.
890 * Quassia Gnus:: Two times two is four, or Gnus 5.6/5.7.
891 * Pterodactyl Gnus:: Pentad also starts with P, AKA Gnus 5.8/5.9.
892 * Oort Gnus:: It's big. It's far out. Gnus 5.10/5.11.
893 * No Gnus:: Lars, FIXME!
897 * Slow/Expensive Connection:: You run a local Emacs and get the news elsewhere.
898 * Slow Terminal Connection:: You run a remote Emacs.
899 * Little Disk Space:: You feel that having large setup files is icky.
900 * Slow Machine:: You feel like buying a faster machine.
904 * Gnus Utility Functions:: Common functions and variable to use.
905 * Back End Interface:: How Gnus communicates with the servers.
906 * Score File Syntax:: A BNF definition of the score file standard.
907 * Headers:: How Gnus stores headers internally.
908 * Ranges:: A handy format for storing mucho numbers.
909 * Group Info:: The group info format.
910 * Extended Interactive:: Symbolic prefixes and stuff.
911 * Emacs/XEmacs Code:: Gnus can be run under all modern Emacsen.
912 * Various File Formats:: Formats of files that Gnus use.
916 * Required Back End Functions:: Functions that must be implemented.
917 * Optional Back End Functions:: Functions that need not be implemented.
918 * Error Messaging:: How to get messages and report errors.
919 * Writing New Back Ends:: Extending old back ends.
920 * Hooking New Back Ends Into Gnus:: What has to be done on the Gnus end.
921 * Mail-like Back Ends:: Some tips on mail back ends.
925 * Active File Format:: Information on articles and groups available.
926 * Newsgroups File Format:: Group descriptions.
930 * Keystrokes:: Entering text and executing commands.
931 * Emacs Lisp:: The built-in Emacs programming language.
937 @chapter Starting gnus
942 If your system administrator has set things up properly, starting gnus
943 and reading news is extremely easy---you just type @kbd{M-x gnus} in
946 @findex gnus-other-frame
947 @kindex M-x gnus-other-frame
948 If you want to start gnus in a different frame, you can use the command
949 @kbd{M-x gnus-other-frame} instead.
951 If things do not go smoothly at startup, you have to twiddle some
952 variables in your @file{~/.gnus.el} file. This file is similar to
953 @file{~/.emacs}, but is read when Gnus starts.
955 If you puzzle at any terms used in this manual, please refer to the
956 terminology section (@pxref{Terminology}).
959 * Finding the News:: Choosing a method for getting news.
960 * The First Time:: What does Gnus do the first time you start it?
961 * The Server is Down:: How can I read my mail then?
962 * Slave Gnusae:: You can have more than one Gnus active at a time.
963 * Fetching a Group:: Starting Gnus just to read a group.
964 * New Groups:: What is Gnus supposed to do with new groups?
965 * Changing Servers:: You may want to move from one server to another.
966 * Startup Files:: Those pesky startup files---@file{.newsrc}.
967 * Auto Save:: Recovering from a crash.
968 * The Active File:: Reading the active file over a slow line Takes Time.
969 * Startup Variables:: Other variables you might change.
973 @node Finding the News
974 @section Finding the News
977 @vindex gnus-select-method
979 The @code{gnus-select-method} variable says where gnus should look for
980 news. This variable should be a list where the first element says
981 @dfn{how} and the second element says @dfn{where}. This method is your
982 native method. All groups not fetched with this method are
985 For instance, if the @samp{news.somewhere.edu} @acronym{NNTP} server is where
986 you want to get your daily dosage of news from, you'd say:
989 (setq gnus-select-method '(nntp "news.somewhere.edu"))
992 If you want to read directly from the local spool, say:
995 (setq gnus-select-method '(nnspool ""))
998 If you can use a local spool, you probably should, as it will almost
999 certainly be much faster. But do not use the local spool if your
1000 server is running Leafnode; in this case, use @code{(nntp "localhost")}.
1002 @vindex gnus-nntpserver-file
1004 @cindex @acronym{NNTP} server
1005 If this variable is not set, gnus will take a look at the
1006 @env{NNTPSERVER} environment variable. If that variable isn't set,
1007 gnus will see whether @code{gnus-nntpserver-file}
1008 (@file{/etc/nntpserver} by default) has any opinions on the matter.
1009 If that fails as well, gnus will try to use the machine running Emacs
1010 as an @acronym{NNTP} server. That's a long shot, though.
1012 @vindex gnus-nntp-server
1013 If @code{gnus-nntp-server} is set, this variable will override
1014 @code{gnus-select-method}. You should therefore set
1015 @code{gnus-nntp-server} to @code{nil}, which is what it is by default.
1017 @vindex gnus-secondary-servers
1018 @vindex gnus-nntp-server
1019 You can also make gnus prompt you interactively for the name of an
1020 @acronym{NNTP} server. If you give a non-numerical prefix to @code{gnus}
1021 (i.e., @kbd{C-u M-x gnus}), gnus will let you choose between the servers
1022 in the @code{gnus-secondary-servers} list (if any). You can also just
1023 type in the name of any server you feel like visiting. (Note that this
1024 will set @code{gnus-nntp-server}, which means that if you then @kbd{M-x
1025 gnus} later in the same Emacs session, Gnus will contact the same
1028 @findex gnus-group-browse-foreign-server
1030 However, if you use one @acronym{NNTP} server regularly and are just
1031 interested in a couple of groups from a different server, you would be
1032 better served by using the @kbd{B} command in the group buffer. It will
1033 let you have a look at what groups are available, and you can subscribe
1034 to any of the groups you want to. This also makes @file{.newsrc}
1035 maintenance much tidier. @xref{Foreign Groups}.
1037 @vindex gnus-secondary-select-methods
1039 A slightly different approach to foreign groups is to set the
1040 @code{gnus-secondary-select-methods} variable. The select methods
1041 listed in this variable are in many ways just as native as the
1042 @code{gnus-select-method} server. They will also be queried for active
1043 files during startup (if that's required), and new newsgroups that
1044 appear on these servers will be subscribed (or not) just as native
1047 For instance, if you use the @code{nnmbox} back end to read your mail,
1048 you would typically set this variable to
1051 (setq gnus-secondary-select-methods '((nnmbox "")))
1054 Note: the @acronym{NNTP} back end stores marks in marks files
1055 (@pxref{NNTP marks}). This feature makes it easy to share marks between
1056 several Gnus installations, but may slow down things a bit when fetching
1057 new articles. @xref{NNTP marks}, for more information.
1060 @node The First Time
1061 @section The First Time
1062 @cindex first time usage
1064 If no startup files exist, gnus will try to determine what groups should
1065 be subscribed by default.
1067 @vindex gnus-default-subscribed-newsgroups
1068 If the variable @code{gnus-default-subscribed-newsgroups} is set, gnus
1069 will subscribe you to just those groups in that list, leaving the rest
1070 killed. Your system administrator should have set this variable to
1073 Since she hasn't, gnus will just subscribe you to a few arbitrarily
1074 picked groups (i.e., @samp{*.newusers}). (@dfn{Arbitrary} is defined
1075 here as @dfn{whatever Lars thinks you should read}.)
1077 You'll also be subscribed to the gnus documentation group, which should
1078 help you with most common problems.
1080 If @code{gnus-default-subscribed-newsgroups} is @code{t}, gnus will just
1081 use the normal functions for handling new groups, and not do anything
1085 @node The Server is Down
1086 @section The Server is Down
1087 @cindex server errors
1089 If the default server is down, gnus will understandably have some
1090 problems starting. However, if you have some mail groups in addition to
1091 the news groups, you may want to start gnus anyway.
1093 Gnus, being the trusting sort of program, will ask whether to proceed
1094 without a native select method if that server can't be contacted. This
1095 will happen whether the server doesn't actually exist (i.e., you have
1096 given the wrong address) or the server has just momentarily taken ill
1097 for some reason or other. If you decide to continue and have no foreign
1098 groups, you'll find it difficult to actually do anything in the group
1099 buffer. But, hey, that's your problem. Blllrph!
1101 @findex gnus-no-server
1102 @kindex M-x gnus-no-server
1104 If you know that the server is definitely down, or you just want to read
1105 your mail without bothering with the server at all, you can use the
1106 @code{gnus-no-server} command to start gnus. That might come in handy
1107 if you're in a hurry as well. This command will not attempt to contact
1108 your primary server---instead, it will just activate all groups on level
1109 1 and 2. (You should preferably keep no native groups on those two
1110 levels.) Also @pxref{Group Levels}.
1114 @section Slave Gnusae
1117 You might want to run more than one Emacs with more than one gnus at the
1118 same time. If you are using different @file{.newsrc} files (e.g., if you
1119 are using the two different gnusae to read from two different servers),
1120 that is no problem whatsoever. You just do it.
1122 The problem appears when you want to run two Gnusae that use the same
1123 @file{.newsrc} file.
1125 To work around that problem some, we here at the Think-Tank at the gnus
1126 Towers have come up with a new concept: @dfn{Masters} and
1127 @dfn{slaves}. (We have applied for a patent on this concept, and have
1128 taken out a copyright on those words. If you wish to use those words in
1129 conjunction with each other, you have to send $1 per usage instance to
1130 me. Usage of the patent (@dfn{Master/Slave Relationships In Computer
1131 Applications}) will be much more expensive, of course.)
1134 Anyway, you start one gnus up the normal way with @kbd{M-x gnus} (or
1135 however you do it). Each subsequent slave gnusae should be started with
1136 @kbd{M-x gnus-slave}. These slaves won't save normal @file{.newsrc}
1137 files, but instead save @dfn{slave files} that contain information only
1138 on what groups have been read in the slave session. When a master gnus
1139 starts, it will read (and delete) these slave files, incorporating all
1140 information from them. (The slave files will be read in the sequence
1141 they were created, so the latest changes will have precedence.)
1143 Information from the slave files has, of course, precedence over the
1144 information in the normal (i.e., master) @file{.newsrc} file.
1146 If the @file{.newsrc*} files have not been saved in the master when the
1147 slave starts, you may be prompted as to whether to read an auto-save
1148 file. If you answer ``yes'', the unsaved changes to the master will be
1149 incorporated into the slave. If you answer ``no'', the slave may see some
1150 messages as unread that have been read in the master.
1152 @node Fetching a Group
1153 @section Fetching a Group
1154 @cindex fetching a group
1156 @findex gnus-fetch-group
1157 It is sometimes convenient to be able to just say ``I want to read this
1158 group and I don't care whether gnus has been started or not''. This is
1159 perhaps more useful for people who write code than for users, but the
1160 command @code{gnus-fetch-group} provides this functionality in any case.
1161 It takes the group name as a parameter.
1167 @cindex subscription
1169 @vindex gnus-check-new-newsgroups
1170 If you are satisfied that you really never want to see any new groups,
1171 you can set @code{gnus-check-new-newsgroups} to @code{nil}. This will
1172 also save you some time at startup. Even if this variable is
1173 @code{nil}, you can always subscribe to the new groups just by pressing
1174 @kbd{U} in the group buffer (@pxref{Group Maintenance}). This variable
1175 is @code{ask-server} by default. If you set this variable to
1176 @code{always}, then Gnus will query the back ends for new groups even
1177 when you do the @kbd{g} command (@pxref{Scanning New Messages}).
1180 * Checking New Groups:: Determining what groups are new.
1181 * Subscription Methods:: What Gnus should do with new groups.
1182 * Filtering New Groups:: Making Gnus ignore certain new groups.
1186 @node Checking New Groups
1187 @subsection Checking New Groups
1189 Gnus normally determines whether a group is new or not by comparing the
1190 list of groups from the active file(s) with the lists of subscribed and
1191 dead groups. This isn't a particularly fast method. If
1192 @code{gnus-check-new-newsgroups} is @code{ask-server}, gnus will ask the
1193 server for new groups since the last time. This is both faster and
1194 cheaper. This also means that you can get rid of the list of killed
1195 groups altogether, so you may set @code{gnus-save-killed-list} to
1196 @code{nil}, which will save time both at startup, at exit, and all over.
1197 Saves disk space, too. Why isn't this the default, then?
1198 Unfortunately, not all servers support this command.
1200 I bet I know what you're thinking now: How do I find out whether my
1201 server supports @code{ask-server}? No? Good, because I don't have a
1202 fail-safe answer. I would suggest just setting this variable to
1203 @code{ask-server} and see whether any new groups appear within the next
1204 few days. If any do, then it works. If none do, then it doesn't
1205 work. I could write a function to make gnus guess whether the server
1206 supports @code{ask-server}, but it would just be a guess. So I won't.
1207 You could @code{telnet} to the server and say @code{HELP} and see
1208 whether it lists @samp{NEWGROUPS} among the commands it understands. If
1209 it does, then it might work. (But there are servers that lists
1210 @samp{NEWGROUPS} without supporting the function properly.)
1212 This variable can also be a list of select methods. If so, gnus will
1213 issue an @code{ask-server} command to each of the select methods, and
1214 subscribe them (or not) using the normal methods. This might be handy
1215 if you are monitoring a few servers for new groups. A side effect is
1216 that startup will take much longer, so you can meditate while waiting.
1217 Use the mantra ``dingnusdingnusdingnus'' to achieve permanent bliss.
1220 @node Subscription Methods
1221 @subsection Subscription Methods
1223 @vindex gnus-subscribe-newsgroup-method
1224 What gnus does when it encounters a new group is determined by the
1225 @code{gnus-subscribe-newsgroup-method} variable.
1227 This variable should contain a function. This function will be called
1228 with the name of the new group as the only parameter.
1230 Some handy pre-fab functions are:
1234 @item gnus-subscribe-zombies
1235 @vindex gnus-subscribe-zombies
1236 Make all new groups zombies. This is the default. You can browse the
1237 zombies later (with @kbd{A z}) and either kill them all off properly
1238 (with @kbd{S z}), or subscribe to them (with @kbd{u}).
1240 @item gnus-subscribe-randomly
1241 @vindex gnus-subscribe-randomly
1242 Subscribe all new groups in arbitrary order. This really means that all
1243 new groups will be added at ``the top'' of the group buffer.
1245 @item gnus-subscribe-alphabetically
1246 @vindex gnus-subscribe-alphabetically
1247 Subscribe all new groups in alphabetical order.
1249 @item gnus-subscribe-hierarchically
1250 @vindex gnus-subscribe-hierarchically
1251 Subscribe all new groups hierarchically. The difference between this
1252 function and @code{gnus-subscribe-alphabetically} is slight.
1253 @code{gnus-subscribe-alphabetically} will subscribe new groups in a strictly
1254 alphabetical fashion, while this function will enter groups into its
1255 hierarchy. So if you want to have the @samp{rec} hierarchy before the
1256 @samp{comp} hierarchy, this function will not mess that configuration
1257 up. Or something like that.
1259 @item gnus-subscribe-interactively
1260 @vindex gnus-subscribe-interactively
1261 Subscribe new groups interactively. This means that gnus will ask
1262 you about @strong{all} new groups. The groups you choose to subscribe
1263 to will be subscribed hierarchically.
1265 @item gnus-subscribe-killed
1266 @vindex gnus-subscribe-killed
1267 Kill all new groups.
1269 @item gnus-subscribe-topics
1270 @vindex gnus-subscribe-topics
1271 Put the groups into the topic that has a matching @code{subscribe} topic
1272 parameter (@pxref{Topic Parameters}). For instance, a @code{subscribe}
1273 topic parameter that looks like
1279 will mean that all groups that match that regex will be subscribed under
1282 If no topics match the groups, the groups will be subscribed in the
1287 @vindex gnus-subscribe-hierarchical-interactive
1288 A closely related variable is
1289 @code{gnus-subscribe-hierarchical-interactive}. (That's quite a
1290 mouthful.) If this variable is non-@code{nil}, gnus will ask you in a
1291 hierarchical fashion whether to subscribe to new groups or not. Gnus
1292 will ask you for each sub-hierarchy whether you want to descend the
1295 One common mistake is to set the variable a few paragraphs above
1296 (@code{gnus-subscribe-newsgroup-method}) to
1297 @code{gnus-subscribe-hierarchical-interactive}. This is an error. This
1298 will not work. This is ga-ga. So don't do it.
1301 @node Filtering New Groups
1302 @subsection Filtering New Groups
1304 A nice and portable way to control which new newsgroups should be
1305 subscribed (or ignored) is to put an @dfn{options} line at the start of
1306 the @file{.newsrc} file. Here's an example:
1309 options -n !alt.all !rec.all sci.all
1312 @vindex gnus-subscribe-options-newsgroup-method
1313 This line obviously belongs to a serious-minded intellectual scientific
1314 person (or she may just be plain old boring), because it says that all
1315 groups that have names beginning with @samp{alt} and @samp{rec} should
1316 be ignored, and all groups with names beginning with @samp{sci} should
1317 be subscribed. Gnus will not use the normal subscription method for
1318 subscribing these groups.
1319 @code{gnus-subscribe-options-newsgroup-method} is used instead. This
1320 variable defaults to @code{gnus-subscribe-alphabetically}.
1322 @vindex gnus-options-not-subscribe
1323 @vindex gnus-options-subscribe
1324 If you don't want to mess with your @file{.newsrc} file, you can just
1325 set the two variables @code{gnus-options-subscribe} and
1326 @code{gnus-options-not-subscribe}. These two variables do exactly the
1327 same as the @file{.newsrc} @samp{options -n} trick. Both are regexps,
1328 and if the new group matches the former, it will be unconditionally
1329 subscribed, and if it matches the latter, it will be ignored.
1331 @vindex gnus-auto-subscribed-groups
1332 Yet another variable that meddles here is
1333 @code{gnus-auto-subscribed-groups}. It works exactly like
1334 @code{gnus-options-subscribe}, and is therefore really superfluous,
1335 but I thought it would be nice to have two of these. This variable is
1336 more meant for setting some ground rules, while the other variable is
1337 used more for user fiddling. By default this variable makes all new
1338 groups that come from mail back ends (@code{nnml}, @code{nnbabyl},
1339 @code{nnfolder}, @code{nnmbox}, @code{nnmh}, and @code{nnmaildir})
1340 subscribed. If you don't like that, just set this variable to
1343 New groups that match this regexp are subscribed using
1344 @code{gnus-subscribe-options-newsgroup-method}.
1347 @node Changing Servers
1348 @section Changing Servers
1349 @cindex changing servers
1351 Sometimes it is necessary to move from one @acronym{NNTP} server to another.
1352 This happens very rarely, but perhaps you change jobs, or one server is
1353 very flaky and you want to use another.
1355 Changing the server is pretty easy, right? You just change
1356 @code{gnus-select-method} to point to the new server?
1360 Article numbers are not (in any way) kept synchronized between different
1361 @acronym{NNTP} servers, and the only way Gnus keeps track of what articles
1362 you have read is by keeping track of article numbers. So when you
1363 change @code{gnus-select-method}, your @file{.newsrc} file becomes
1366 Gnus provides a few functions to attempt to translate a @file{.newsrc}
1367 file from one server to another. They all have one thing in
1368 common---they take a looong time to run. You don't want to use these
1369 functions more than absolutely necessary.
1371 @kindex M-x gnus-change-server
1372 @findex gnus-change-server
1373 If you have access to both servers, Gnus can request the headers for all
1374 the articles you have read and compare @code{Message-ID}s and map the
1375 article numbers of the read articles and article marks. The @kbd{M-x
1376 gnus-change-server} command will do this for all your native groups. It
1377 will prompt for the method you want to move to.
1379 @kindex M-x gnus-group-move-group-to-server
1380 @findex gnus-group-move-group-to-server
1381 You can also move individual groups with the @kbd{M-x
1382 gnus-group-move-group-to-server} command. This is useful if you want to
1383 move a (foreign) group from one server to another.
1385 @kindex M-x gnus-group-clear-data-on-native-groups
1386 @findex gnus-group-clear-data-on-native-groups
1387 If you don't have access to both the old and new server, all your marks
1388 and read ranges have become worthless. You can use the @kbd{M-x
1389 gnus-group-clear-data-on-native-groups} command to clear out all data
1390 that you have on your native groups. Use with caution.
1392 @kindex M-x gnus-group-clear-data
1393 @findex gnus-group-clear-data
1394 Clear the data from the current group only---nix out marks and the
1395 list of read articles (@code{gnus-group-clear-data}).
1397 After changing servers, you @strong{must} move the cache hierarchy away,
1398 since the cached articles will have wrong article numbers, which will
1399 affect which articles Gnus thinks are read.
1400 @code{gnus-group-clear-data-on-native-groups} will ask you if you want
1401 to have it done automatically; for @code{gnus-group-clear-data}, you
1402 can use @kbd{M-x gnus-cache-move-cache} (but beware, it will move the
1403 cache for all groups).
1407 @section Startup Files
1408 @cindex startup files
1413 Now, you all know about the @file{.newsrc} file. All subscription
1414 information is traditionally stored in this file.
1416 Things got a bit more complicated with @sc{gnus}. In addition to
1417 keeping the @file{.newsrc} file updated, it also used a file called
1418 @file{.newsrc.el} for storing all the information that didn't fit into
1419 the @file{.newsrc} file. (Actually, it also duplicated everything in
1420 the @file{.newsrc} file.) @sc{gnus} would read whichever one of these
1421 files was the most recently saved, which enabled people to swap between
1422 @sc{gnus} and other newsreaders.
1424 That was kinda silly, so Gnus went one better: In addition to the
1425 @file{.newsrc} and @file{.newsrc.el} files, Gnus also has a file called
1426 @file{.newsrc.eld}. It will read whichever of these files that are most
1427 recent, but it will never write a @file{.newsrc.el} file. You should
1428 never delete the @file{.newsrc.eld} file---it contains much information
1429 not stored in the @file{.newsrc} file.
1431 @vindex gnus-save-newsrc-file
1432 @vindex gnus-read-newsrc-file
1433 You can turn off writing the @file{.newsrc} file by setting
1434 @code{gnus-save-newsrc-file} to @code{nil}, which means you can delete
1435 the file and save some space, as well as exiting from gnus faster.
1436 However, this will make it impossible to use other newsreaders than
1437 gnus. But hey, who would want to, right? Similarly, setting
1438 @code{gnus-read-newsrc-file} to @code{nil} makes gnus ignore the
1439 @file{.newsrc} file and any @file{.newsrc-SERVER} files, which is
1440 convenient if you have a tendency to use Netscape once in a while.
1442 @vindex gnus-save-killed-list
1443 If @code{gnus-save-killed-list} (default @code{t}) is @code{nil}, Gnus
1444 will not save the list of killed groups to the startup file. This will
1445 save both time (when starting and quitting) and space (on disk). It
1446 will also mean that Gnus has no record of what groups are new or old,
1447 so the automatic new groups subscription methods become meaningless.
1448 You should always set @code{gnus-check-new-newsgroups} to @code{nil} or
1449 @code{ask-server} if you set this variable to @code{nil} (@pxref{New
1450 Groups}). This variable can also be a regular expression. If that's
1451 the case, remove all groups that do not match this regexp before
1452 saving. This can be useful in certain obscure situations that involve
1453 several servers where not all servers support @code{ask-server}.
1455 @vindex gnus-startup-file
1456 @vindex gnus-backup-startup-file
1457 @vindex version-control
1458 The @code{gnus-startup-file} variable says where the startup files are.
1459 The default value is @file{~/.newsrc}, with the Gnus (El Dingo) startup
1460 file being whatever that one is, with a @samp{.eld} appended.
1461 If you want version control for this file, set
1462 @code{gnus-backup-startup-file}. It respects the same values as the
1463 @code{version-control} variable.
1465 @vindex gnus-save-newsrc-hook
1466 @vindex gnus-save-quick-newsrc-hook
1467 @vindex gnus-save-standard-newsrc-hook
1468 @code{gnus-save-newsrc-hook} is called before saving any of the newsrc
1469 files, while @code{gnus-save-quick-newsrc-hook} is called just before
1470 saving the @file{.newsrc.eld} file, and
1471 @code{gnus-save-standard-newsrc-hook} is called just before saving the
1472 @file{.newsrc} file. The latter two are commonly used to turn version
1473 control on or off. Version control is on by default when saving the
1474 startup files. If you want to turn backup creation off, say something like:
1477 (defun turn-off-backup ()
1478 (set (make-local-variable 'backup-inhibited) t))
1480 (add-hook 'gnus-save-quick-newsrc-hook 'turn-off-backup)
1481 (add-hook 'gnus-save-standard-newsrc-hook 'turn-off-backup)
1484 @vindex gnus-init-file
1485 @vindex gnus-site-init-file
1486 When gnus starts, it will read the @code{gnus-site-init-file}
1487 (@file{.../site-lisp/gnus} by default) and @code{gnus-init-file}
1488 (@file{~/.gnus} by default) files. These are normal Emacs Lisp files
1489 and can be used to avoid cluttering your @file{~/.emacs} and
1490 @file{site-init} files with gnus stuff. Gnus will also check for files
1491 with the same names as these, but with @file{.elc} and @file{.el}
1492 suffixes. In other words, if you have set @code{gnus-init-file} to
1493 @file{~/.gnus}, it will look for @file{~/.gnus.elc}, @file{~/.gnus.el},
1494 and finally @file{~/.gnus} (in this order).
1500 @cindex dribble file
1503 Whenever you do something that changes the gnus data (reading articles,
1504 catching up, killing/subscribing groups), the change is added to a
1505 special @dfn{dribble buffer}. This buffer is auto-saved the normal
1506 Emacs way. If your Emacs should crash before you have saved the
1507 @file{.newsrc} files, all changes you have made can be recovered from
1510 If gnus detects this file at startup, it will ask the user whether to
1511 read it. The auto save file is deleted whenever the real startup file is
1514 @vindex gnus-use-dribble-file
1515 If @code{gnus-use-dribble-file} is @code{nil}, gnus won't create and
1516 maintain a dribble buffer. The default is @code{t}.
1518 @vindex gnus-dribble-directory
1519 Gnus will put the dribble file(s) in @code{gnus-dribble-directory}. If
1520 this variable is @code{nil}, which it is by default, gnus will dribble
1521 into the directory where the @file{.newsrc} file is located. (This is
1522 normally the user's home directory.) The dribble file will get the same
1523 file permissions as the @file{.newsrc} file.
1525 @vindex gnus-always-read-dribble-file
1526 If @code{gnus-always-read-dribble-file} is non-@code{nil}, Gnus will
1527 read the dribble file on startup without querying the user.
1530 @node The Active File
1531 @section The Active File
1533 @cindex ignored groups
1535 When gnus starts, or indeed whenever it tries to determine whether new
1536 articles have arrived, it reads the active file. This is a very large
1537 file that lists all the active groups and articles on the server.
1539 @vindex gnus-ignored-newsgroups
1540 Before examining the active file, gnus deletes all lines that match the
1541 regexp @code{gnus-ignored-newsgroups}. This is done primarily to reject
1542 any groups with bogus names, but you can use this variable to make gnus
1543 ignore hierarchies you aren't ever interested in. However, this is not
1544 recommended. In fact, it's highly discouraged. Instead, @pxref{New
1545 Groups} for an overview of other variables that can be used instead.
1548 @c @code{nil} by default, and will slow down active file handling somewhat
1549 @c if you set it to anything else.
1551 @vindex gnus-read-active-file
1553 The active file can be rather Huge, so if you have a slow network, you
1554 can set @code{gnus-read-active-file} to @code{nil} to prevent gnus from
1555 reading the active file. This variable is @code{some} by default.
1557 Gnus will try to make do by getting information just on the groups that
1558 you actually subscribe to.
1560 Note that if you subscribe to lots and lots of groups, setting this
1561 variable to @code{nil} will probably make gnus slower, not faster. At
1562 present, having this variable @code{nil} will slow gnus down
1563 considerably, unless you read news over a 2400 baud modem.
1565 This variable can also have the value @code{some}. Gnus will then
1566 attempt to read active info only on the subscribed groups. On some
1567 servers this is quite fast (on sparkling, brand new INN servers that
1568 support the @code{LIST ACTIVE group} command), on others this isn't fast
1569 at all. In any case, @code{some} should be faster than @code{nil}, and
1570 is certainly faster than @code{t} over slow lines.
1572 Some news servers (old versions of Leafnode and old versions of INN, for
1573 instance) do not support the @code{LIST ACTIVE group}. For these
1574 servers, @code{nil} is probably the most efficient value for this
1577 If this variable is @code{nil}, gnus will ask for group info in total
1578 lock-step, which isn't very fast. If it is @code{some} and you use an
1579 @acronym{NNTP} server, gnus will pump out commands as fast as it can, and
1580 read all the replies in one swoop. This will normally result in better
1581 performance, but if the server does not support the aforementioned
1582 @code{LIST ACTIVE group} command, this isn't very nice to the server.
1584 If you think that starting up Gnus takes too long, try all the three
1585 different values for this variable and see what works best for you.
1587 In any case, if you use @code{some} or @code{nil}, you should definitely
1588 kill all groups that you aren't interested in to speed things up.
1590 Note that this variable also affects active file retrieval from
1591 secondary select methods.
1594 @node Startup Variables
1595 @section Startup Variables
1599 @item gnus-load-hook
1600 @vindex gnus-load-hook
1601 A hook run while gnus is being loaded. Note that this hook will
1602 normally be run just once in each Emacs session, no matter how many
1603 times you start gnus.
1605 @item gnus-before-startup-hook
1606 @vindex gnus-before-startup-hook
1607 A hook run after starting up gnus successfully.
1609 @item gnus-startup-hook
1610 @vindex gnus-startup-hook
1611 A hook run as the very last thing after starting up gnus
1613 @item gnus-started-hook
1614 @vindex gnus-started-hook
1615 A hook that is run as the very last thing after starting up gnus
1618 @item gnus-setup-news-hook
1619 @vindex gnus-setup-news-hook
1620 A hook that is run after reading the @file{.newsrc} file(s), but before
1621 generating the group buffer.
1623 @item gnus-check-bogus-newsgroups
1624 @vindex gnus-check-bogus-newsgroups
1625 If non-@code{nil}, gnus will check for and delete all bogus groups at
1626 startup. A @dfn{bogus group} is a group that you have in your
1627 @file{.newsrc} file, but doesn't exist on the news server. Checking for
1628 bogus groups can take quite a while, so to save time and resources it's
1629 best to leave this option off, and do the checking for bogus groups once
1630 in a while from the group buffer instead (@pxref{Group Maintenance}).
1632 @item gnus-inhibit-startup-message
1633 @vindex gnus-inhibit-startup-message
1634 If non-@code{nil}, the startup message won't be displayed. That way,
1635 your boss might not notice as easily that you are reading news instead
1636 of doing your job. Note that this variable is used before
1637 @file{~/.gnus.el} is loaded, so it should be set in @file{.emacs} instead.
1639 @item gnus-no-groups-message
1640 @vindex gnus-no-groups-message
1641 Message displayed by gnus when no groups are available.
1643 @item gnus-play-startup-jingle
1644 @vindex gnus-play-startup-jingle
1645 If non-@code{nil}, play the gnus jingle at startup.
1647 @item gnus-startup-jingle
1648 @vindex gnus-startup-jingle
1649 Jingle to be played if the above variable is non-@code{nil}. The
1650 default is @samp{Tuxedomoon.Jingle4.au}.
1656 @chapter Group Buffer
1657 @cindex group buffer
1659 @c Alex Schroeder suggests to rearrange this as follows:
1661 @c <kensanata> ok, just save it for reference. I'll go to bed in a minute.
1662 @c 1. Selecting a Group, 2. (new) Finding a Group, 3. Group Levels,
1663 @c 4. Subscription Commands, 5. Group Maneuvering, 6. Group Data,
1664 @c 7. Group Score, 8. Group Buffer Format
1665 @c <kensanata> Group Levels should have more information on levels 5 to 9. I
1666 @c suggest to split the 4th paragraph ("Gnus considers groups...") as follows:
1667 @c <kensanata> First, "Gnus considers groups... (default 9)."
1668 @c <kensanata> New, a table summarizing what levels 1 to 9 mean.
1669 @c <kensanata> Third, "Gnus treats subscribed ... reasons of efficiency"
1670 @c <kensanata> Then expand the next paragraph or add some more to it.
1671 @c This short one sentence explains levels 1 and 2, therefore I understand
1672 @c that I should keep important news at 3 and boring news at 4.
1673 @c Say so! Then go on to explain why I should bother with levels 6 to 9.
1674 @c Maybe keep those that you don't want to read temporarily at 6,
1675 @c those that you never want to read at 8, those that offend your
1676 @c human rights at 9...
1679 The @dfn{group buffer} lists all (or parts) of the available groups. It
1680 is the first buffer shown when gnus starts, and will never be killed as
1681 long as gnus is active.
1685 \gnusfigure{The Group Buffer}{320}{
1686 \put(75,50){\epsfig{figure=ps/group,height=9cm}}
1687 \put(120,37){\makebox(0,0)[t]{Buffer name}}
1688 \put(120,38){\vector(1,2){10}}
1689 \put(40,60){\makebox(0,0)[r]{Mode line}}
1690 \put(40,58){\vector(1,0){30}}
1691 \put(200,28){\makebox(0,0)[t]{Native select method}}
1692 \put(200,26){\vector(-1,2){15}}
1698 * Group Buffer Format:: Information listed and how you can change it.
1699 * Group Maneuvering:: Commands for moving in the group buffer.
1700 * Selecting a Group:: Actually reading news.
1701 * Subscription Commands:: Unsubscribing, killing, subscribing.
1702 * Group Data:: Changing the info for a group.
1703 * Group Levels:: Levels? What are those, then?
1704 * Group Score:: A mechanism for finding out what groups you like.
1705 * Marking Groups:: You can mark groups for later processing.
1706 * Foreign Groups:: Creating and editing groups.
1707 * Group Parameters:: Each group may have different parameters set.
1708 * Listing Groups:: Gnus can list various subsets of the groups.
1709 * Sorting Groups:: Re-arrange the group order.
1710 * Group Maintenance:: Maintaining a tidy @file{.newsrc} file.
1711 * Browse Foreign Server:: You can browse a server. See what it has to offer.
1712 * Exiting Gnus:: Stop reading news and get some work done.
1713 * Group Topics:: A folding group mode divided into topics.
1714 * Misc Group Stuff:: Other stuff that you can to do.
1718 @node Group Buffer Format
1719 @section Group Buffer Format
1722 * Group Line Specification:: Deciding how the group buffer is to look.
1723 * Group Mode Line Specification:: The group buffer mode line.
1724 * Group Highlighting:: Having nice colors in the group buffer.
1728 @node Group Line Specification
1729 @subsection Group Line Specification
1730 @cindex group buffer format
1732 The default format of the group buffer is nice and dull, but you can
1733 make it as exciting and ugly as you feel like.
1735 Here's a couple of example group lines:
1738 25: news.announce.newusers
1739 * 0: alt.fan.andrea-dworkin
1744 You can see that there are 25 unread articles in
1745 @samp{news.announce.newusers}. There are no unread articles, but some
1746 ticked articles, in @samp{alt.fan.andrea-dworkin} (see that little
1747 asterisk at the beginning of the line?).
1749 @vindex gnus-group-line-format
1750 You can change that format to whatever you want by fiddling with the
1751 @code{gnus-group-line-format} variable. This variable works along the
1752 lines of a @code{format} specification, which is pretty much the same as
1753 a @code{printf} specifications, for those of you who use (feh!) C.
1754 @xref{Formatting Variables}.
1756 @samp{%M%S%5y:%B%(%g%)\n} is the value that produced those lines above.
1758 There should always be a colon on the line; the cursor always moves to
1759 the colon after performing an operation. @xref{Positioning
1760 Point}. Nothing else is required---not even the group name. All
1761 displayed text is just window dressing, and is never examined by Gnus.
1762 Gnus stores all real information it needs using text properties.
1764 (Note that if you make a really strange, wonderful, spreadsheet-like
1765 layout, everybody will believe you are hard at work with the accounting
1766 instead of wasting time reading news.)
1768 Here's a list of all available format characters:
1773 An asterisk if the group only has marked articles.
1776 Whether the group is subscribed.
1779 Level of subscribedness.
1782 Number of unread articles.
1785 Number of dormant articles.
1788 Number of ticked articles.
1791 Number of read articles.
1794 Number of unseen articles.
1797 Estimated total number of articles. (This is really @var{max-number}
1798 minus @var{min-number} plus 1.)
1800 Gnus uses this estimation because the @acronym{NNTP} protocol provides
1801 efficient access to @var{max-number} and @var{min-number} but getting
1802 the true unread message count is not possible efficiently. For
1803 hysterical raisins, even the mail back ends, where the true number of
1804 unread messages might be available efficiently, use the same limited
1805 interface. To remove this restriction from Gnus means that the back
1806 end interface has to be changed, which is not an easy job. If you
1807 want to work on this, please contact the Gnus mailing list.
1810 Number of unread, unticked, non-dormant articles.
1813 Number of ticked and dormant articles.
1822 Group comment (@pxref{Group Parameters}) or group name if there is no
1823 comment element in the group parameters.
1826 Newsgroup description. You need to read the group descriptions
1827 before these will appear, and to do that, you either have to set
1828 @code{gnus-read-active-file} or use the group buffer @kbd{M-d}
1832 @samp{m} if moderated.
1835 @samp{(m)} if moderated.
1841 If the summary buffer for the group is open or not.
1847 A string that looks like @samp{<%s:%n>} if a foreign select method is
1851 Indentation based on the level of the topic (@pxref{Group Topics}).
1854 @vindex gnus-group-uncollapsed-levels
1855 Short (collapsed) group name. The @code{gnus-group-uncollapsed-levels}
1856 variable says how many levels to leave at the end of the group name.
1857 The default is 1---this will mean that group names like
1858 @samp{gnu.emacs.gnus} will be shortened to @samp{g.e.gnus}.
1861 @vindex gnus-new-mail-mark
1863 @samp{%} (@code{gnus-new-mail-mark}) if there has arrived new mail to
1867 @samp{#} (@code{gnus-process-mark}) if the group is process marked.
1870 A string that says when you last read the group (@pxref{Group
1874 The disk space used by the articles fetched by both the cache and
1875 agent. The value is automatically scaled to bytes(B), kilobytes(K),
1876 megabytes(M), or gigabytes(G) to minimize the column width. A format
1877 of %7F is sufficient for a fixed-width column.
1880 User defined specifier. The next character in the format string should
1881 be a letter. Gnus will call the function
1882 @code{gnus-user-format-function-}@samp{X}, where @samp{X} is the letter
1883 following @samp{%u}. The function will be passed a single dummy
1884 parameter as argument. The function should return a string, which will
1885 be inserted into the buffer just like information from any other
1890 All the ``number-of'' specs will be filled with an asterisk (@samp{*})
1891 if no info is available---for instance, if it is a non-activated foreign
1892 group, or a bogus native group.
1895 @node Group Mode Line Specification
1896 @subsection Group Mode Line Specification
1897 @cindex group mode line
1899 @vindex gnus-group-mode-line-format
1900 The mode line can be changed by setting
1901 @code{gnus-group-mode-line-format} (@pxref{Mode Line Formatting}). It
1902 doesn't understand that many format specifiers:
1906 The native news server.
1908 The native select method.
1912 @node Group Highlighting
1913 @subsection Group Highlighting
1914 @cindex highlighting
1915 @cindex group highlighting
1917 @vindex gnus-group-highlight
1918 Highlighting in the group buffer is controlled by the
1919 @code{gnus-group-highlight} variable. This is an alist with elements
1920 that look like @code{(@var{form} . @var{face})}. If @var{form} evaluates to
1921 something non-@code{nil}, the @var{face} will be used on the line.
1923 Here's an example value for this variable that might look nice if the
1927 (cond (window-system
1928 (setq custom-background-mode 'light)
1929 (defface my-group-face-1
1930 '((t (:foreground "Red" :bold t))) "First group face")
1931 (defface my-group-face-2
1932 '((t (:foreground "DarkSeaGreen4" :bold t)))
1933 "Second group face")
1934 (defface my-group-face-3
1935 '((t (:foreground "Green4" :bold t))) "Third group face")
1936 (defface my-group-face-4
1937 '((t (:foreground "SteelBlue" :bold t))) "Fourth group face")
1938 (defface my-group-face-5
1939 '((t (:foreground "Blue" :bold t))) "Fifth group face")))
1941 (setq gnus-group-highlight
1942 '(((> unread 200) . my-group-face-1)
1943 ((and (< level 3) (zerop unread)) . my-group-face-2)
1944 ((< level 3) . my-group-face-3)
1945 ((zerop unread) . my-group-face-4)
1946 (t . my-group-face-5)))
1949 Also @pxref{Faces and Fonts}.
1951 Variables that are dynamically bound when the forms are evaluated
1958 The number of unread articles in the group.
1962 Whether the group is a mail group.
1964 The level of the group.
1966 The score of the group.
1968 The number of ticked articles in the group.
1970 The total number of articles in the group. Or rather,
1971 @var{max-number} minus @var{min-number} plus one.
1973 When using the topic minor mode, this variable is bound to the current
1974 topic being inserted.
1977 When the forms are @code{eval}ed, point is at the beginning of the line
1978 of the group in question, so you can use many of the normal gnus
1979 functions for snarfing info on the group.
1981 @vindex gnus-group-update-hook
1982 @findex gnus-group-highlight-line
1983 @code{gnus-group-update-hook} is called when a group line is changed.
1984 It will not be called when @code{gnus-visual} is @code{nil}. This hook
1985 calls @code{gnus-group-highlight-line} by default.
1988 @node Group Maneuvering
1989 @section Group Maneuvering
1990 @cindex group movement
1992 All movement commands understand the numeric prefix and will behave as
1993 expected, hopefully.
1999 @findex gnus-group-next-unread-group
2000 Go to the next group that has unread articles
2001 (@code{gnus-group-next-unread-group}).
2007 @findex gnus-group-prev-unread-group
2008 Go to the previous group that has unread articles
2009 (@code{gnus-group-prev-unread-group}).
2013 @findex gnus-group-next-group
2014 Go to the next group (@code{gnus-group-next-group}).
2018 @findex gnus-group-prev-group
2019 Go to the previous group (@code{gnus-group-prev-group}).
2023 @findex gnus-group-next-unread-group-same-level
2024 Go to the next unread group on the same (or lower) level
2025 (@code{gnus-group-next-unread-group-same-level}).
2029 @findex gnus-group-prev-unread-group-same-level
2030 Go to the previous unread group on the same (or lower) level
2031 (@code{gnus-group-prev-unread-group-same-level}).
2034 Three commands for jumping to groups:
2040 @findex gnus-group-jump-to-group
2041 Jump to a group (and make it visible if it isn't already)
2042 (@code{gnus-group-jump-to-group}). Killed groups can be jumped to, just
2047 @findex gnus-group-best-unread-group
2048 Jump to the unread group with the lowest level
2049 (@code{gnus-group-best-unread-group}).
2053 @findex gnus-group-first-unread-group
2054 Jump to the first group with unread articles
2055 (@code{gnus-group-first-unread-group}).
2058 @vindex gnus-group-goto-unread
2059 If @code{gnus-group-goto-unread} is @code{nil}, all the movement
2060 commands will move to the next group, not the next unread group. Even
2061 the commands that say they move to the next unread group. The default
2065 @node Selecting a Group
2066 @section Selecting a Group
2067 @cindex group selection
2072 @kindex SPACE (Group)
2073 @findex gnus-group-read-group
2074 Select the current group, switch to the summary buffer and display the
2075 first unread article (@code{gnus-group-read-group}). If there are no
2076 unread articles in the group, or if you give a non-numerical prefix to
2077 this command, gnus will offer to fetch all the old articles in this
2078 group from the server. If you give a numerical prefix @var{n}, @var{n}
2079 determines the number of articles Gnus will fetch. If @var{n} is
2080 positive, Gnus fetches the @var{n} newest articles, if @var{n} is
2081 negative, Gnus fetches the @code{abs(@var{n})} oldest articles.
2083 Thus, @kbd{SPC} enters the group normally, @kbd{C-u SPC} offers old
2084 articles, @kbd{C-u 4 2 SPC} fetches the 42 newest articles, and @kbd{C-u
2085 - 4 2 SPC} fetches the 42 oldest ones.
2087 When you are in the group (in the Summary buffer), you can type
2088 @kbd{M-g} to fetch new articles, or @kbd{C-u M-g} to also show the old
2093 @findex gnus-group-select-group
2094 Select the current group and switch to the summary buffer
2095 (@code{gnus-group-select-group}). Takes the same arguments as
2096 @code{gnus-group-read-group}---the only difference is that this command
2097 does not display the first unread article automatically upon group
2101 @kindex M-RET (Group)
2102 @findex gnus-group-quick-select-group
2103 This does the same as the command above, but tries to do it with the
2104 minimum amount of fuzz (@code{gnus-group-quick-select-group}). No
2105 scoring/killing will be performed, there will be no highlights and no
2106 expunging. This might be useful if you're in a real hurry and have to
2107 enter some humongous group. If you give a 0 prefix to this command
2108 (i.e., @kbd{0 M-RET}), gnus won't even generate the summary buffer,
2109 which is useful if you want to toggle threading before generating the
2110 summary buffer (@pxref{Summary Generation Commands}).
2113 @kindex M-SPACE (Group)
2114 @findex gnus-group-visible-select-group
2115 This is yet one more command that does the same as the @kbd{RET}
2116 command, but this one does it without expunging and hiding dormants
2117 (@code{gnus-group-visible-select-group}).
2120 @kindex C-M-RET (Group)
2121 @findex gnus-group-select-group-ephemerally
2122 Finally, this command selects the current group ephemerally without
2123 doing any processing of its contents
2124 (@code{gnus-group-select-group-ephemerally}). Even threading has been
2125 turned off. Everything you do in the group after selecting it in this
2126 manner will have no permanent effects.
2130 @vindex gnus-large-newsgroup
2131 The @code{gnus-large-newsgroup} variable says what Gnus should
2132 consider to be a big group. If it is @code{nil}, no groups are
2133 considered big. The default value is 200. If the group has more
2134 (unread and/or ticked) articles than this, gnus will query the user
2135 before entering the group. The user can then specify how many
2136 articles should be fetched from the server. If the user specifies a
2137 negative number (@var{-n}), the @var{n} oldest articles will be
2138 fetched. If it is positive, the @var{n} articles that have arrived
2139 most recently will be fetched.
2141 @vindex gnus-large-ephemeral-newsgroup
2142 @code{gnus-large-ephemeral-newsgroup} is the same as
2143 @code{gnus-large-newsgroup}, but is only used for ephemeral
2146 @vindex gnus-select-group-hook
2147 @vindex gnus-auto-select-first
2148 @vindex gnus-auto-select-subject
2149 If @code{gnus-auto-select-first} is non-@code{nil}, select an article
2150 automatically when entering a group with the @kbd{SPACE} command.
2151 Which article this is is controlled by the
2152 @code{gnus-auto-select-subject} variable. Valid values for this
2158 Place point on the subject line of the first unread article.
2161 Place point on the subject line of the first article.
2164 Place point on the subject line of the first unseen article.
2166 @item unseen-or-unread
2167 Place point on the subject line of the first unseen article, and if
2168 there is no such article, place point on the subject line of the first
2172 Place point on the subject line of the highest-scored unread article.
2176 This variable can also be a function. In that case, that function
2177 will be called to place point on a subject line.
2179 If you want to prevent automatic selection in some group (say, in a
2180 binary group with Huge articles) you can set the
2181 @code{gnus-auto-select-first} variable to @code{nil} in
2182 @code{gnus-select-group-hook}, which is called when a group is
2186 @node Subscription Commands
2187 @section Subscription Commands
2188 @cindex subscription
2196 @findex gnus-group-unsubscribe-current-group
2197 @c @icon{gnus-group-unsubscribe}
2198 Toggle subscription to the current group
2199 (@code{gnus-group-unsubscribe-current-group}).
2205 @findex gnus-group-unsubscribe-group
2206 Prompt for a group to subscribe, and then subscribe it. If it was
2207 subscribed already, unsubscribe it instead
2208 (@code{gnus-group-unsubscribe-group}).
2214 @findex gnus-group-kill-group
2215 @c @icon{gnus-group-kill-group}
2216 Kill the current group (@code{gnus-group-kill-group}).
2222 @findex gnus-group-yank-group
2223 Yank the last killed group (@code{gnus-group-yank-group}).
2226 @kindex C-x C-t (Group)
2227 @findex gnus-group-transpose-groups
2228 Transpose two groups (@code{gnus-group-transpose-groups}). This isn't
2229 really a subscription command, but you can use it instead of a
2230 kill-and-yank sequence sometimes.
2236 @findex gnus-group-kill-region
2237 Kill all groups in the region (@code{gnus-group-kill-region}).
2241 @findex gnus-group-kill-all-zombies
2242 Kill all zombie groups (@code{gnus-group-kill-all-zombies}).
2245 @kindex S C-k (Group)
2246 @findex gnus-group-kill-level
2247 Kill all groups on a certain level (@code{gnus-group-kill-level}).
2248 These groups can't be yanked back after killing, so this command should
2249 be used with some caution. The only time where this command comes in
2250 really handy is when you have a @file{.newsrc} with lots of unsubscribed
2251 groups that you want to get rid off. @kbd{S C-k} on level 7 will
2252 kill off all unsubscribed groups that do not have message numbers in the
2253 @file{.newsrc} file.
2257 Also @pxref{Group Levels}.
2267 @findex gnus-group-catchup-current
2268 @vindex gnus-group-catchup-group-hook
2269 @c @icon{gnus-group-catchup-current}
2270 Mark all unticked articles in this group as read
2271 (@code{gnus-group-catchup-current}).
2272 @code{gnus-group-catchup-group-hook} is called when catching up a group from
2277 @findex gnus-group-catchup-current-all
2278 Mark all articles in this group, even the ticked ones, as read
2279 (@code{gnus-group-catchup-current-all}).
2283 @findex gnus-group-clear-data
2284 Clear the data from the current group---nix out marks and the list of
2285 read articles (@code{gnus-group-clear-data}).
2287 @item M-x gnus-group-clear-data-on-native-groups
2288 @kindex M-x gnus-group-clear-data-on-native-groups
2289 @findex gnus-group-clear-data-on-native-groups
2290 If you have switched from one @acronym{NNTP} server to another, all your marks
2291 and read ranges have become worthless. You can use this command to
2292 clear out all data that you have on your native groups. Use with
2299 @section Group Levels
2303 All groups have a level of @dfn{subscribedness}. For instance, if a
2304 group is on level 2, it is more subscribed than a group on level 5. You
2305 can ask gnus to just list groups on a given level or lower
2306 (@pxref{Listing Groups}), or to just check for new articles in groups on
2307 a given level or lower (@pxref{Scanning New Messages}).
2309 Remember: The higher the level of the group, the less important it is.
2315 @findex gnus-group-set-current-level
2316 Set the level of the current group. If a numeric prefix is given, the
2317 next @var{n} groups will have their levels set. The user will be
2318 prompted for a level.
2321 @vindex gnus-level-killed
2322 @vindex gnus-level-zombie
2323 @vindex gnus-level-unsubscribed
2324 @vindex gnus-level-subscribed
2325 Gnus considers groups from levels 1 to
2326 @code{gnus-level-subscribed} (inclusive) (default 5) to be subscribed,
2327 @code{gnus-level-subscribed} (exclusive) and
2328 @code{gnus-level-unsubscribed} (inclusive) (default 7) to be
2329 unsubscribed, @code{gnus-level-zombie} to be zombies (walking dead)
2330 (default 8) and @code{gnus-level-killed} to be killed (completely dead)
2331 (default 9). Gnus treats subscribed and unsubscribed groups exactly the
2332 same, but zombie and killed groups have no information on what articles
2333 you have read, etc, stored. This distinction between dead and living
2334 groups isn't done because it is nice or clever, it is done purely for
2335 reasons of efficiency.
2337 It is recommended that you keep all your mail groups (if any) on quite
2338 low levels (e.g. 1 or 2).
2340 Maybe the following description of the default behavior of Gnus helps to
2341 understand what these levels are all about. By default, Gnus shows you
2342 subscribed nonempty groups, but by hitting @kbd{L} you can have it show
2343 empty subscribed groups and unsubscribed groups, too. Type @kbd{l} to
2344 go back to showing nonempty subscribed groups again. Thus, unsubscribed
2345 groups are hidden, in a way.
2347 Zombie and killed groups are similar to unsubscribed groups in that they
2348 are hidden by default. But they are different from subscribed and
2349 unsubscribed groups in that Gnus doesn't ask the news server for
2350 information (number of messages, number of unread messages) on zombie
2351 and killed groups. Normally, you use @kbd{C-k} to kill the groups you
2352 aren't interested in. If most groups are killed, Gnus is faster.
2354 Why does Gnus distinguish between zombie and killed groups? Well, when
2355 a new group arrives on the server, Gnus by default makes it a zombie
2356 group. This means that you are normally not bothered with new groups,
2357 but you can type @kbd{A z} to get a list of all new groups. Subscribe
2358 the ones you like and kill the ones you don't want. (@kbd{A k} shows a
2359 list of killed groups.)
2361 If you want to play with the level variables, you should show some care.
2362 Set them once, and don't touch them ever again. Better yet, don't touch
2363 them at all unless you know exactly what you're doing.
2365 @vindex gnus-level-default-unsubscribed
2366 @vindex gnus-level-default-subscribed
2367 Two closely related variables are @code{gnus-level-default-subscribed}
2368 (default 3) and @code{gnus-level-default-unsubscribed} (default 6),
2369 which are the levels that new groups will be put on if they are
2370 (un)subscribed. These two variables should, of course, be inside the
2371 relevant valid ranges.
2373 @vindex gnus-keep-same-level
2374 If @code{gnus-keep-same-level} is non-@code{nil}, some movement commands
2375 will only move to groups of the same level (or lower). In
2376 particular, going from the last article in one group to the next group
2377 will go to the next group of the same level (or lower). This might be
2378 handy if you want to read the most important groups before you read the
2381 If this variable is @code{best}, Gnus will make the next newsgroup the
2382 one with the best level.
2384 @vindex gnus-group-default-list-level
2385 All groups with a level less than or equal to
2386 @code{gnus-group-default-list-level} will be listed in the group buffer
2389 @vindex gnus-group-list-inactive-groups
2390 If @code{gnus-group-list-inactive-groups} is non-@code{nil}, non-active
2391 groups will be listed along with the unread groups. This variable is
2392 @code{t} by default. If it is @code{nil}, inactive groups won't be
2395 @vindex gnus-group-use-permanent-levels
2396 If @code{gnus-group-use-permanent-levels} is non-@code{nil}, once you
2397 give a level prefix to @kbd{g} or @kbd{l}, all subsequent commands will
2398 use this level as the ``work'' level.
2400 @vindex gnus-activate-level
2401 Gnus will normally just activate (i. e., query the server about) groups
2402 on level @code{gnus-activate-level} or less. If you don't want to
2403 activate unsubscribed groups, for instance, you might set this variable
2404 to 5. The default is 6.
2408 @section Group Score
2413 You would normally keep important groups on high levels, but that scheme
2414 is somewhat restrictive. Don't you wish you could have Gnus sort the
2415 group buffer according to how often you read groups, perhaps? Within
2418 This is what @dfn{group score} is for. You can have Gnus assign a score
2419 to each group through the mechanism described below. You can then sort
2420 the group buffer based on this score. Alternatively, you can sort on
2421 score and then level. (Taken together, the level and the score is
2422 called the @dfn{rank} of the group. A group that is on level 4 and has
2423 a score of 1 has a higher rank than a group on level 5 that has a score
2424 of 300. (The level is the most significant part and the score is the
2425 least significant part.))
2427 @findex gnus-summary-bubble-group
2428 If you want groups you read often to get higher scores than groups you
2429 read seldom you can add the @code{gnus-summary-bubble-group} function to
2430 the @code{gnus-summary-exit-hook} hook. This will result (after
2431 sorting) in a bubbling sort of action. If you want to see that in
2432 action after each summary exit, you can add
2433 @code{gnus-group-sort-groups-by-rank} or
2434 @code{gnus-group-sort-groups-by-score} to the same hook, but that will
2435 slow things down somewhat.
2438 @node Marking Groups
2439 @section Marking Groups
2440 @cindex marking groups
2442 If you want to perform some command on several groups, and they appear
2443 subsequently in the group buffer, you would normally just give a
2444 numerical prefix to the command. Most group commands will then do your
2445 bidding on those groups.
2447 However, if the groups are not in sequential order, you can still
2448 perform a command on several groups. You simply mark the groups first
2449 with the process mark and then execute the command.
2457 @findex gnus-group-mark-group
2458 Set the mark on the current group (@code{gnus-group-mark-group}).
2464 @findex gnus-group-unmark-group
2465 Remove the mark from the current group
2466 (@code{gnus-group-unmark-group}).
2470 @findex gnus-group-unmark-all-groups
2471 Remove the mark from all groups (@code{gnus-group-unmark-all-groups}).
2475 @findex gnus-group-mark-region
2476 Mark all groups between point and mark (@code{gnus-group-mark-region}).
2480 @findex gnus-group-mark-buffer
2481 Mark all groups in the buffer (@code{gnus-group-mark-buffer}).
2485 @findex gnus-group-mark-regexp
2486 Mark all groups that match some regular expression
2487 (@code{gnus-group-mark-regexp}).
2490 Also @pxref{Process/Prefix}.
2492 @findex gnus-group-universal-argument
2493 If you want to execute some command on all groups that have been marked
2494 with the process mark, you can use the @kbd{M-&}
2495 (@code{gnus-group-universal-argument}) command. It will prompt you for
2496 the command to be executed.
2499 @node Foreign Groups
2500 @section Foreign Groups
2501 @cindex foreign groups
2503 Below are some group mode commands for making and editing general foreign
2504 groups, as well as commands to ease the creation of a few
2505 special-purpose groups. All these commands insert the newly created
2506 groups under point---@code{gnus-subscribe-newsgroup-method} is not
2513 @findex gnus-group-make-group
2514 @cindex making groups
2515 Make a new group (@code{gnus-group-make-group}). Gnus will prompt you
2516 for a name, a method and possibly an @dfn{address}. For an easier way
2517 to subscribe to @acronym{NNTP} groups (@pxref{Browse Foreign Server}).
2521 @findex gnus-group-read-ephemeral-group
2522 Make an ephemeral group (@code{gnus-group-read-ephemeral-group}). Gnus
2523 will prompt you for a name, a method and an @dfn{address}.
2527 @findex gnus-group-rename-group
2528 @cindex renaming groups
2529 Rename the current group to something else
2530 (@code{gnus-group-rename-group}). This is valid only on some
2531 groups---mail groups mostly. This command might very well be quite slow
2537 @findex gnus-group-customize
2538 Customize the group parameters (@code{gnus-group-customize}).
2542 @findex gnus-group-edit-group-method
2543 @cindex renaming groups
2544 Enter a buffer where you can edit the select method of the current
2545 group (@code{gnus-group-edit-group-method}).
2549 @findex gnus-group-edit-group-parameters
2550 Enter a buffer where you can edit the group parameters
2551 (@code{gnus-group-edit-group-parameters}).
2555 @findex gnus-group-edit-group
2556 Enter a buffer where you can edit the group info
2557 (@code{gnus-group-edit-group}).
2561 @findex gnus-group-make-directory-group
2563 Make a directory group (@pxref{Directory Groups}). You will be prompted
2564 for a directory name (@code{gnus-group-make-directory-group}).
2569 @findex gnus-group-make-help-group
2570 Make the gnus help group (@code{gnus-group-make-help-group}).
2574 @cindex (ding) archive
2575 @cindex archive group
2576 @findex gnus-group-make-archive-group
2577 @vindex gnus-group-archive-directory
2578 @vindex gnus-group-recent-archive-directory
2579 Make a gnus archive group (@code{gnus-group-make-archive-group}). By
2580 default a group pointing to the most recent articles will be created
2581 (@code{gnus-group-recent-archive-directory}), but given a prefix, a full
2582 group will be created from @code{gnus-group-archive-directory}.
2586 @findex gnus-group-make-kiboze-group
2588 Make a kiboze group. You will be prompted for a name, for a regexp to
2589 match groups to be ``included'' in the kiboze group, and a series of
2590 strings to match on headers (@code{gnus-group-make-kiboze-group}).
2591 @xref{Kibozed Groups}.
2595 @findex gnus-group-enter-directory
2597 Read an arbitrary directory as if it were a newsgroup with the
2598 @code{nneething} back end (@code{gnus-group-enter-directory}).
2599 @xref{Anything Groups}.
2603 @findex gnus-group-make-doc-group
2604 @cindex ClariNet Briefs
2606 Make a group based on some file or other
2607 (@code{gnus-group-make-doc-group}). If you give a prefix to this
2608 command, you will be prompted for a file name and a file type.
2609 Currently supported types are @code{mbox}, @code{babyl},
2610 @code{digest}, @code{news}, @code{rnews}, @code{mmdf}, @code{forward},
2611 @code{rfc934}, @code{rfc822-forward}, @code{mime-parts},
2612 @code{standard-digest}, @code{slack-digest}, @code{clari-briefs},
2613 @code{nsmail}, @code{outlook}, @code{oe-dbx}, and @code{mailman}. If
2614 you run this command without a prefix, Gnus will guess at the file
2615 type. @xref{Document Groups}.
2619 @vindex gnus-useful-groups
2620 @findex gnus-group-make-useful-group
2621 Create one of the groups mentioned in @code{gnus-useful-groups}
2622 (@code{gnus-group-make-useful-group}).
2626 @findex gnus-group-make-web-group
2630 Make an ephemeral group based on a web search
2631 (@code{gnus-group-make-web-group}). If you give a prefix to this
2632 command, make a solid group instead. You will be prompted for the
2633 search engine type and the search string. Valid search engine types
2634 include @code{google}, @code{dejanews}, and @code{gmane}.
2635 @xref{Web Searches}.
2637 If you use the @code{google} search engine, you can limit the search
2638 to a particular group by using a match string like
2639 @samp{shaving group:alt.sysadmin.recovery}.
2643 @findex gnus-group-make-rss-group
2644 Make a group based on an @acronym{RSS} feed
2645 (@code{gnus-group-make-rss-group}). You will be prompted for an URL.
2649 @kindex G DEL (Group)
2650 @findex gnus-group-delete-group
2651 This function will delete the current group
2652 (@code{gnus-group-delete-group}). If given a prefix, this function will
2653 actually delete all the articles in the group, and forcibly remove the
2654 group itself from the face of the Earth. Use a prefix only if you are
2655 absolutely sure of what you are doing. This command can't be used on
2656 read-only groups (like @code{nntp} groups), though.
2660 @findex gnus-group-make-empty-virtual
2661 Make a new, fresh, empty @code{nnvirtual} group
2662 (@code{gnus-group-make-empty-virtual}). @xref{Virtual Groups}.
2666 @findex gnus-group-add-to-virtual
2667 Add the current group to an @code{nnvirtual} group
2668 (@code{gnus-group-add-to-virtual}). Uses the process/prefix convention.
2671 @xref{Select Methods}, for more information on the various select
2674 @vindex gnus-activate-foreign-newsgroups
2675 If @code{gnus-activate-foreign-newsgroups} is a positive number,
2676 gnus will check all foreign groups with this level or lower at startup.
2677 This might take quite a while, especially if you subscribe to lots of
2678 groups from different @acronym{NNTP} servers. Also @pxref{Group Levels};
2679 @code{gnus-activate-level} also affects activation of foreign
2683 @node Group Parameters
2684 @section Group Parameters
2685 @cindex group parameters
2687 The group parameters store information local to a particular group.
2688 Here's an example group parameter list:
2691 ((to-address . "ding@@gnus.org")
2695 We see that each element consists of a ``dotted pair''---the thing before
2696 the dot is the key, while the thing after the dot is the value. All the
2697 parameters have this form @emph{except} local variable specs, which are
2698 not dotted pairs, but proper lists.
2700 Some parameters have correspondent customizable variables, each of which
2701 is an alist of regexps and values.
2703 The following group parameters can be used:
2708 Address used by when doing followups and new posts.
2711 (to-address . "some@@where.com")
2714 This is primarily useful in mail groups that represent closed mailing
2715 lists---mailing lists where it's expected that everybody that writes to
2716 the mailing list is subscribed to it. Since using this parameter
2717 ensures that the mail only goes to the mailing list itself, it means
2718 that members won't receive two copies of your followups.
2720 Using @code{to-address} will actually work whether the group is foreign
2721 or not. Let's say there's a group on the server that is called
2722 @samp{fa.4ad-l}. This is a real newsgroup, but the server has gotten
2723 the articles from a mail-to-news gateway. Posting directly to this
2724 group is therefore impossible---you have to send mail to the mailing
2725 list address instead.
2727 See also @code{gnus-parameter-to-address-alist}.
2731 Address used when doing @kbd{a} in that group.
2734 (to-list . "some@@where.com")
2737 It is totally ignored
2738 when doing a followup---except that if it is present in a news group,
2739 you'll get mail group semantics when doing @kbd{f}.
2741 If you do an @kbd{a} command in a mail group and you have neither a
2742 @code{to-list} group parameter nor a @code{to-address} group parameter,
2743 then a @code{to-list} group parameter will be added automatically upon
2744 sending the message if @code{gnus-add-to-list} is set to @code{t}.
2745 @vindex gnus-add-to-list
2747 @findex gnus-mailing-list-mode
2748 @cindex mail list groups
2749 If this variable is set, @code{gnus-mailing-list-mode} is turned on when
2750 entering summary buffer.
2752 See also @code{gnus-parameter-to-list-alist}.
2757 @cindex Mail-Followup-To
2758 @findex gnus-find-subscribed-addresses
2759 If this parameter is set to @code{t}, Gnus will consider the
2760 to-address and to-list parameters for this group as addresses of
2761 mailing lists you are subscribed to. Giving Gnus this information is
2762 (only) a first step in getting it to generate correct Mail-Followup-To
2763 headers for your posts to these lists. The second step is to put the
2764 following in your @file{.gnus.el}
2767 (setq message-subscribed-address-functions
2768 '(gnus-find-subscribed-addresses))
2771 @xref{Mailing Lists, ,Mailing Lists, message, The Message Manual}, for
2772 a complete treatment of available MFT support.
2776 If the group parameter list has the element @code{(visible . t)},
2777 that group will always be visible in the Group buffer, regardless
2778 of whether it has any unread articles.
2780 @item broken-reply-to
2781 @cindex broken-reply-to
2782 Elements like @code{(broken-reply-to . t)} signals that @code{Reply-To}
2783 headers in this group are to be ignored, and for the header to be hidden
2784 if @code{reply-to} is part of @code{gnus-boring-article-headers}. This
2785 can be useful if you're reading a mailing list group where the listserv
2786 has inserted @code{Reply-To} headers that point back to the listserv
2787 itself. That is broken behavior. So there!
2791 Elements like @code{(to-group . "some.group.name")} means that all
2792 posts in that group will be sent to @code{some.group.name}.
2796 If you have @code{(newsgroup . t)} in the group parameter list, gnus
2797 will treat all responses as if they were responses to news articles.
2798 This can be useful if you have a mail group that's really a mirror of a
2803 If @code{(gcc-self . t)} is present in the group parameter list, newly
2804 composed messages will be @code{Gcc}'d to the current group. If
2805 @code{(gcc-self . none)} is present, no @code{Gcc:} header will be
2806 generated, if @code{(gcc-self . "string")} is present, this string will
2807 be inserted literally as a @code{gcc} header. This parameter takes
2808 precedence over any default @code{Gcc} rules as described later
2809 (@pxref{Archived Messages}).
2811 @strong{Caveat}: Adding @code{(gcc-self . t)} to the parameter list of
2812 @code{nntp} groups (or the like) isn't valid. An @code{nntp} server
2813 doesn't accept articles.
2817 If the group parameter has an element that looks like @code{(auto-expire
2818 . t)}, all articles read will be marked as expirable. For an
2819 alternative approach, @pxref{Expiring Mail}.
2821 See also @code{gnus-auto-expirable-newsgroups}.
2824 @cindex total-expire
2825 If the group parameter has an element that looks like
2826 @code{(total-expire . t)}, all read articles will be put through the
2827 expiry process, even if they are not marked as expirable. Use with
2828 caution. Unread, ticked and dormant articles are not eligible for
2831 See also @code{gnus-total-expirable-newsgroups}.
2835 @vindex nnmail-expiry-wait-function
2836 If the group parameter has an element that looks like
2837 @code{(expiry-wait . 10)}, this value will override any
2838 @code{nnmail-expiry-wait} and @code{nnmail-expiry-wait-function}
2839 (@pxref{Expiring Mail}) when expiring expirable messages. The value
2840 can either be a number of days (not necessarily an integer) or the
2841 symbols @code{never} or @code{immediate}.
2844 @cindex expiry-target
2845 Where expired messages end up. This parameter overrides
2846 @code{nnmail-expiry-target}.
2849 @cindex score file group parameter
2850 Elements that look like @code{(score-file . "file")} will make
2851 @file{file} into the current score file for the group in question. All
2852 interactive score entries will be put into this file.
2855 @cindex adapt file group parameter
2856 Elements that look like @code{(adapt-file . "file")} will make
2857 @file{file} into the current adaptive file for the group in question.
2858 All adaptive score entries will be put into this file.
2861 @cindex admin-address
2862 When unsubscribing from a mailing list you should never send the
2863 unsubscription notice to the mailing list itself. Instead, you'd send
2864 messages to the administrative address. This parameter allows you to
2865 put the admin address somewhere convenient.
2869 Elements that look like @code{(display . MODE)} say which articles to
2870 display on entering the group. Valid values are:
2874 Display all articles, both read and unread.
2877 Display the last @var{integer} articles in the group. This is the same as
2878 entering the group with @kbd{C-u @var{integer}}.
2881 Display the default visible articles, which normally includes unread and
2885 Display articles that satisfy a predicate.
2887 Here are some examples:
2891 Display only unread articles.
2894 Display everything except expirable articles.
2896 @item [and (not reply) (not expire)]
2897 Display everything except expirable and articles you've already
2901 The available operators are @code{not}, @code{and} and @code{or}.
2902 Predicates include @code{tick}, @code{unsend}, @code{undownload},
2903 @code{unread}, @code{dormant}, @code{expire}, @code{reply},
2904 @code{killed}, @code{bookmark}, @code{score}, @code{save},
2905 @code{cache}, @code{forward}, @code{unseen} and @code{recent}.
2909 The @code{display} parameter works by limiting the summary buffer to
2910 the subset specified. You can pop the limit by using the @kbd{/ w}
2911 command (@pxref{Limiting}).
2915 Elements that look like @code{(comment . "This is a comment")} are
2916 arbitrary comments on the group. You can display comments in the
2917 group line (@pxref{Group Line Specification}).
2921 Elements that look like @code{(charset . iso-8859-1)} will make
2922 @code{iso-8859-1} the default charset; that is, the charset that will be
2923 used for all articles that do not specify a charset.
2925 See also @code{gnus-group-charset-alist}.
2927 @item ignored-charsets
2928 @cindex ignored-charset
2929 Elements that look like @code{(ignored-charsets x-unknown iso-8859-1)}
2930 will make @code{iso-8859-1} and @code{x-unknown} ignored; that is, the
2931 default charset will be used for decoding articles.
2933 See also @code{gnus-group-ignored-charsets-alist}.
2936 @cindex posting-style
2937 You can store additional posting style information for this group
2938 here (@pxref{Posting Styles}). The format is that of an entry in the
2939 @code{gnus-posting-styles} alist, except that there's no regexp matching
2940 the group name (of course). Style elements in this group parameter will
2941 take precedence over the ones found in @code{gnus-posting-styles}.
2943 For instance, if you want a funky name and signature in this group only,
2944 instead of hacking @code{gnus-posting-styles}, you could put something
2945 like this in the group parameters:
2950 ("X-My-Header" "Funky Value")
2951 (signature "Funky Signature"))
2956 If it is set, the value is used as the method for posting message
2957 instead of @code{gnus-post-method}.
2961 An item like @code{(banner . @var{regexp})} causes any part of an article
2962 that matches the regular expression @var{regexp} to be stripped. Instead of
2963 @var{regexp}, you can also use the symbol @code{signature} which strips the
2964 last signature or any of the elements of the alist
2965 @code{gnus-article-banner-alist}.
2969 This parameter contains a Sieve test that should match incoming mail
2970 that should be placed in this group. From this group parameter, a
2971 Sieve @samp{IF} control structure is generated, having the test as the
2972 condition and @samp{fileinto "group.name";} as the body.
2974 For example, if the @samp{INBOX.list.sieve} group has the @code{(sieve
2975 address "sender" "sieve-admin@@extundo.com")} group parameter, when
2976 translating the group parameter into a Sieve script (@pxref{Sieve
2977 Commands}) the following Sieve code is generated:
2980 if address "sender" "sieve-admin@@extundo.com" @{
2981 fileinto "INBOX.list.sieve";
2985 To generate tests for multiple email-addresses use a group parameter
2986 like @code{(sieve address "sender" ("name@@one.org" else@@two.org"))}.
2987 When generating a sieve script (@pxref{Sieve Commands}) Sieve code
2988 like the following is generated:
2991 if address "sender" ["name@@one.org", "else@@two.org"] @{
2992 fileinto "INBOX.list.sieve";
2996 See @pxref{Sieve Commands} for commands and variables that might be of
2997 interest in relation to the sieve parameter.
2999 The Sieve language is described in RFC 3028. @xref{Top, Emacs Sieve,
3000 Top, sieve, Emacs Sieve}.
3002 @item (agent parameters)
3003 If the agent has been enabled, you can set any of the its parameters
3004 to control the behavior of the agent in individual groups. See Agent
3005 Parameters in @ref{Category Syntax}. Most users will choose to set
3006 agent parameters in either an agent category or group topic to
3007 minimize the configuration effort.
3009 @item (@var{variable} @var{form})
3010 You can use the group parameters to set variables local to the group you
3011 are entering. If you want to turn threading off in @samp{news.answers},
3012 you could put @code{(gnus-show-threads nil)} in the group parameters of
3013 that group. @code{gnus-show-threads} will be made into a local variable
3014 in the summary buffer you enter, and the form @code{nil} will be
3015 @code{eval}ed there.
3017 Note that this feature sets the variable locally to the summary buffer.
3018 But some variables are evaluated in the article buffer, or in the
3019 message buffer (of a reply or followup or otherwise newly created
3020 message). As a workaround, it might help to add the variable in
3021 question to @code{gnus-newsgroup-variables}. @xref{Various Summary
3022 Stuff}. So if you want to set @code{message-from-style} via the group
3023 parameters, then you may need the following statement elsewhere in your
3024 @file{~/.gnus} file:
3027 (add-to-list 'gnus-newsgroup-variables 'message-from-style)
3030 @vindex gnus-list-identifiers
3031 A use for this feature is to remove a mailing list identifier tag in
3032 the subject fields of articles. E.g. if the news group
3035 nntp+news.gnus.org:gmane.text.docbook.apps
3038 has the tag @samp{DOC-BOOK-APPS:} in the subject of all articles, this
3039 tag can be removed from the article subjects in the summary buffer for
3040 the group by putting @code{(gnus-list-identifiers "DOCBOOK-APPS:")}
3041 into the group parameters for the group.
3043 This can also be used as a group-specific hook function. If you want to
3044 hear a beep when you enter a group, you could put something like
3045 @code{(dummy-variable (ding))} in the parameters of that group.
3046 @code{dummy-variable} will be set to the (meaningless) result of the
3049 Alternatively, since the VARIABLE becomes local to the group, this
3050 pattern can be used to temporarily change a hook. For example, if the
3051 following is added to a group parameter
3054 (gnus-summary-prepared-hook
3055 '(lambda nil (local-set-key "d" (local-key-binding "n"))))
3058 when the group is entered, the 'd' key will not mark the article as
3063 Use the @kbd{G p} or the @kbd{G c} command to edit group parameters of a
3064 group. (@kbd{G p} presents you with a Lisp-based interface, @kbd{G c}
3065 presents you with a Customize-like interface. The latter helps avoid
3066 silly Lisp errors.) You might also be interested in reading about topic
3067 parameters (@pxref{Topic Parameters}).
3069 @vindex gnus-parameters
3070 Group parameters can be set via the @code{gnus-parameters} variable too.
3071 But some variables, such as @code{visible}, have no effect. For
3075 (setq gnus-parameters
3077 (gnus-show-threads nil)
3078 (gnus-use-scoring nil)
3079 (gnus-summary-line-format
3080 "%U%R%z%I%(%[%d:%ub%-23,23f%]%) %s\n")
3084 ("^nnimap:\\(foo.bar\\)$"
3088 (gnus-use-scoring t))
3092 (broken-reply-to . t))))
3095 String value of parameters will be subjected to regexp substitution, as
3096 the @code{to-group} example shows.
3099 @node Listing Groups
3100 @section Listing Groups
3101 @cindex group listing
3103 These commands all list various slices of the groups available.
3111 @findex gnus-group-list-groups
3112 List all groups that have unread articles
3113 (@code{gnus-group-list-groups}). If the numeric prefix is used, this
3114 command will list only groups of level ARG and lower. By default, it
3115 only lists groups of level five (i.e.,
3116 @code{gnus-group-default-list-level}) or lower (i.e., just subscribed
3123 @findex gnus-group-list-all-groups
3124 List all groups, whether they have unread articles or not
3125 (@code{gnus-group-list-all-groups}). If the numeric prefix is used,
3126 this command will list only groups of level ARG and lower. By default,
3127 it lists groups of level seven or lower (i.e., just subscribed and
3128 unsubscribed groups).
3132 @findex gnus-group-list-level
3133 List all unread groups on a specific level
3134 (@code{gnus-group-list-level}). If given a prefix, also list the groups
3135 with no unread articles.
3139 @findex gnus-group-list-killed
3140 List all killed groups (@code{gnus-group-list-killed}). If given a
3141 prefix argument, really list all groups that are available, but aren't
3142 currently (un)subscribed. This could entail reading the active file
3147 @findex gnus-group-list-zombies
3148 List all zombie groups (@code{gnus-group-list-zombies}).
3152 @findex gnus-group-list-matching
3153 List all unread, subscribed groups with names that match a regexp
3154 (@code{gnus-group-list-matching}).
3158 @findex gnus-group-list-all-matching
3159 List groups that match a regexp (@code{gnus-group-list-all-matching}).
3163 @findex gnus-group-list-active
3164 List absolutely all groups in the active file(s) of the
3165 server(s) you are connected to (@code{gnus-group-list-active}). This
3166 might very well take quite a while. It might actually be a better idea
3167 to do a @kbd{A M} to list all matching, and just give @samp{.} as the
3168 thing to match on. Also note that this command may list groups that
3169 don't exist (yet)---these will be listed as if they were killed groups.
3170 Take the output with some grains of salt.
3174 @findex gnus-group-apropos
3175 List all groups that have names that match a regexp
3176 (@code{gnus-group-apropos}).
3180 @findex gnus-group-description-apropos
3181 List all groups that have names or descriptions that match a regexp
3182 (@code{gnus-group-description-apropos}).
3186 @findex gnus-group-list-cached
3187 List all groups with cached articles (@code{gnus-group-list-cached}).
3191 @findex gnus-group-list-dormant
3192 List all groups with dormant articles (@code{gnus-group-list-dormant}).
3196 @findex gnus-group-list-limit
3197 List groups limited within the current selection
3198 (@code{gnus-group-list-limit}).
3202 @findex gnus-group-list-flush
3203 Flush groups from the current selection (@code{gnus-group-list-flush}).
3207 @findex gnus-group-list-plus
3208 List groups plus the current selection (@code{gnus-group-list-plus}).
3212 @vindex gnus-permanently-visible-groups
3213 @cindex visible group parameter
3214 Groups that match the @code{gnus-permanently-visible-groups} regexp will
3215 always be shown, whether they have unread articles or not. You can also
3216 add the @code{visible} element to the group parameters in question to
3217 get the same effect.
3219 @vindex gnus-list-groups-with-ticked-articles
3220 Groups that have just ticked articles in it are normally listed in the
3221 group buffer. If @code{gnus-list-groups-with-ticked-articles} is
3222 @code{nil}, these groups will be treated just like totally empty
3223 groups. It is @code{t} by default.
3226 @node Sorting Groups
3227 @section Sorting Groups
3228 @cindex sorting groups
3230 @kindex C-c C-s (Group)
3231 @findex gnus-group-sort-groups
3232 @vindex gnus-group-sort-function
3233 The @kbd{C-c C-s} (@code{gnus-group-sort-groups}) command sorts the
3234 group buffer according to the function(s) given by the
3235 @code{gnus-group-sort-function} variable. Available sorting functions
3240 @item gnus-group-sort-by-alphabet
3241 @findex gnus-group-sort-by-alphabet
3242 Sort the group names alphabetically. This is the default.
3244 @item gnus-group-sort-by-real-name
3245 @findex gnus-group-sort-by-real-name
3246 Sort the group alphabetically on the real (unprefixed) group names.
3248 @item gnus-group-sort-by-level
3249 @findex gnus-group-sort-by-level
3250 Sort by group level.
3252 @item gnus-group-sort-by-score
3253 @findex gnus-group-sort-by-score
3254 Sort by group score. @xref{Group Score}.
3256 @item gnus-group-sort-by-rank
3257 @findex gnus-group-sort-by-rank
3258 Sort by group score and then the group level. The level and the score
3259 are, when taken together, the group's @dfn{rank}. @xref{Group Score}.
3261 @item gnus-group-sort-by-unread
3262 @findex gnus-group-sort-by-unread
3263 Sort by number of unread articles.
3265 @item gnus-group-sort-by-method
3266 @findex gnus-group-sort-by-method
3267 Sort alphabetically on the select method.
3269 @item gnus-group-sort-by-server
3270 @findex gnus-group-sort-by-server
3271 Sort alphabetically on the Gnus server name.
3276 @code{gnus-group-sort-function} can also be a list of sorting
3277 functions. In that case, the most significant sort key function must be
3281 There are also a number of commands for sorting directly according to
3282 some sorting criteria:
3286 @kindex G S a (Group)
3287 @findex gnus-group-sort-groups-by-alphabet
3288 Sort the group buffer alphabetically by group name
3289 (@code{gnus-group-sort-groups-by-alphabet}).
3292 @kindex G S u (Group)
3293 @findex gnus-group-sort-groups-by-unread
3294 Sort the group buffer by the number of unread articles
3295 (@code{gnus-group-sort-groups-by-unread}).
3298 @kindex G S l (Group)
3299 @findex gnus-group-sort-groups-by-level
3300 Sort the group buffer by group level
3301 (@code{gnus-group-sort-groups-by-level}).
3304 @kindex G S v (Group)
3305 @findex gnus-group-sort-groups-by-score
3306 Sort the group buffer by group score
3307 (@code{gnus-group-sort-groups-by-score}). @xref{Group Score}.
3310 @kindex G S r (Group)
3311 @findex gnus-group-sort-groups-by-rank
3312 Sort the group buffer by group rank
3313 (@code{gnus-group-sort-groups-by-rank}). @xref{Group Score}.
3316 @kindex G S m (Group)
3317 @findex gnus-group-sort-groups-by-method
3318 Sort the group buffer alphabetically by back end name@*
3319 (@code{gnus-group-sort-groups-by-method}).
3322 @kindex G S n (Group)
3323 @findex gnus-group-sort-groups-by-real-name
3324 Sort the group buffer alphabetically by real (unprefixed) group name
3325 (@code{gnus-group-sort-groups-by-real-name}).
3329 All the commands below obey the process/prefix convention
3330 (@pxref{Process/Prefix}).
3332 When given a symbolic prefix (@pxref{Symbolic Prefixes}), all these
3333 commands will sort in reverse order.
3335 You can also sort a subset of the groups:
3339 @kindex G P a (Group)
3340 @findex gnus-group-sort-selected-groups-by-alphabet
3341 Sort the groups alphabetically by group name
3342 (@code{gnus-group-sort-selected-groups-by-alphabet}).
3345 @kindex G P u (Group)
3346 @findex gnus-group-sort-selected-groups-by-unread
3347 Sort the groups by the number of unread articles
3348 (@code{gnus-group-sort-selected-groups-by-unread}).
3351 @kindex G P l (Group)
3352 @findex gnus-group-sort-selected-groups-by-level
3353 Sort the groups by group level
3354 (@code{gnus-group-sort-selected-groups-by-level}).
3357 @kindex G P v (Group)
3358 @findex gnus-group-sort-selected-groups-by-score
3359 Sort the groups by group score
3360 (@code{gnus-group-sort-selected-groups-by-score}). @xref{Group Score}.
3363 @kindex G P r (Group)
3364 @findex gnus-group-sort-selected-groups-by-rank
3365 Sort the groups by group rank
3366 (@code{gnus-group-sort-selected-groups-by-rank}). @xref{Group Score}.
3369 @kindex G P m (Group)
3370 @findex gnus-group-sort-selected-groups-by-method
3371 Sort the groups alphabetically by back end name@*
3372 (@code{gnus-group-sort-selected-groups-by-method}).
3375 @kindex G P n (Group)
3376 @findex gnus-group-sort-selected-groups-by-real-name
3377 Sort the groups alphabetically by real (unprefixed) group name
3378 (@code{gnus-group-sort-selected-groups-by-real-name}).
3381 @kindex G P s (Group)
3382 @findex gnus-group-sort-selected-groups
3383 Sort the groups according to @code{gnus-group-sort-function}.
3387 And finally, note that you can use @kbd{C-k} and @kbd{C-y} to manually
3391 @node Group Maintenance
3392 @section Group Maintenance
3393 @cindex bogus groups
3398 @findex gnus-group-check-bogus-groups
3399 Find bogus groups and delete them
3400 (@code{gnus-group-check-bogus-groups}).
3404 @findex gnus-group-find-new-groups
3405 Find new groups and process them (@code{gnus-group-find-new-groups}).
3406 With 1 @kbd{C-u}, use the @code{ask-server} method to query the server
3407 for new groups. With 2 @kbd{C-u}'s, use most complete method possible
3408 to query the server for new groups, and subscribe the new groups as
3412 @kindex C-c C-x (Group)
3413 @findex gnus-group-expire-articles
3414 Run all expirable articles in the current group through the expiry
3415 process (if any) (@code{gnus-group-expire-articles}). That is, delete
3416 all expirable articles in the group that have been around for a while.
3417 (@pxref{Expiring Mail}).
3420 @kindex C-c C-M-x (Group)
3421 @findex gnus-group-expire-all-groups
3422 Run all expirable articles in all groups through the expiry process
3423 (@code{gnus-group-expire-all-groups}).
3428 @node Browse Foreign Server
3429 @section Browse Foreign Server
3430 @cindex foreign servers
3431 @cindex browsing servers
3436 @findex gnus-group-browse-foreign-server
3437 You will be queried for a select method and a server name. Gnus will
3438 then attempt to contact this server and let you browse the groups there
3439 (@code{gnus-group-browse-foreign-server}).
3442 @findex gnus-browse-mode
3443 A new buffer with a list of available groups will appear. This buffer
3444 will use the @code{gnus-browse-mode}. This buffer looks a bit (well,
3445 a lot) like a normal group buffer.
3447 Here's a list of keystrokes available in the browse mode:
3452 @findex gnus-group-next-group
3453 Go to the next group (@code{gnus-group-next-group}).
3457 @findex gnus-group-prev-group
3458 Go to the previous group (@code{gnus-group-prev-group}).
3461 @kindex SPACE (Browse)
3462 @findex gnus-browse-read-group
3463 Enter the current group and display the first article
3464 (@code{gnus-browse-read-group}).
3467 @kindex RET (Browse)
3468 @findex gnus-browse-select-group
3469 Enter the current group (@code{gnus-browse-select-group}).
3473 @findex gnus-browse-unsubscribe-current-group
3474 Unsubscribe to the current group, or, as will be the case here,
3475 subscribe to it (@code{gnus-browse-unsubscribe-current-group}).
3481 @findex gnus-browse-exit
3482 Exit browse mode (@code{gnus-browse-exit}).
3486 @findex gnus-browse-describe-group
3487 Describe the current group (@code{gnus-browse-describe-group}).
3491 @findex gnus-browse-describe-briefly
3492 Describe browse mode briefly (well, there's not much to describe, is
3493 there) (@code{gnus-browse-describe-briefly}).
3498 @section Exiting gnus
3499 @cindex exiting gnus
3501 Yes, gnus is ex(c)iting.
3506 @findex gnus-group-suspend
3507 Suspend gnus (@code{gnus-group-suspend}). This doesn't really exit gnus,
3508 but it kills all buffers except the Group buffer. I'm not sure why this
3509 is a gain, but then who am I to judge?
3513 @findex gnus-group-exit
3514 @c @icon{gnus-group-exit}
3515 Quit gnus (@code{gnus-group-exit}).
3519 @findex gnus-group-quit
3520 Quit gnus without saving the @file{.newsrc} files (@code{gnus-group-quit}).
3521 The dribble file will be saved, though (@pxref{Auto Save}).
3524 @vindex gnus-exit-gnus-hook
3525 @vindex gnus-suspend-gnus-hook
3526 @vindex gnus-after-exiting-gnus-hook
3527 @code{gnus-suspend-gnus-hook} is called when you suspend gnus and
3528 @code{gnus-exit-gnus-hook} is called when you quit gnus, while
3529 @code{gnus-after-exiting-gnus-hook} is called as the final item when
3535 Miss Lisa Cannifax, while sitting in English class, felt her feet go
3536 numbly heavy and herself fall into a hazy trance as the boy sitting
3537 behind her drew repeated lines with his pencil across the back of her
3543 @section Group Topics
3546 If you read lots and lots of groups, it might be convenient to group
3547 them hierarchically according to topics. You put your Emacs groups over
3548 here, your sex groups over there, and the rest (what, two groups or so?)
3549 you put in some misc section that you never bother with anyway. You can
3550 even group the Emacs sex groups as a sub-topic to either the Emacs
3551 groups or the sex groups---or both! Go wild!
3555 \gnusfigure{Group Topics}{400}{
3556 \put(75,50){\epsfig{figure=ps/group-topic,height=9cm}}
3567 2: alt.religion.emacs
3570 0: comp.talk.emacs.recovery
3572 8: comp.binaries.fractals
3573 13: comp.sources.unix
3576 @findex gnus-topic-mode
3578 To get this @emph{fab} functionality you simply turn on (ooh!) the
3579 @code{gnus-topic} minor mode---type @kbd{t} in the group buffer. (This
3580 is a toggling command.)
3582 Go ahead, just try it. I'll still be here when you get back. La de
3583 dum@dots{} Nice tune, that@dots{} la la la@dots{} What, you're back?
3584 Yes, and now press @kbd{l}. There. All your groups are now listed
3585 under @samp{misc}. Doesn't that make you feel all warm and fuzzy?
3588 If you want this permanently enabled, you should add that minor mode to
3589 the hook for the group mode. Put the following line in your
3590 @file{~/.gnus.el} file:
3593 (add-hook 'gnus-group-mode-hook 'gnus-topic-mode)
3597 * Topic Commands:: Interactive E-Z commands.
3598 * Topic Variables:: How to customize the topics the Lisp Way.
3599 * Topic Sorting:: Sorting each topic individually.
3600 * Topic Topology:: A map of the world.
3601 * Topic Parameters:: Parameters that apply to all groups in a topic.
3605 @node Topic Commands
3606 @subsection Topic Commands
3607 @cindex topic commands
3609 When the topic minor mode is turned on, a new @kbd{T} submap will be
3610 available. In addition, a few of the standard keys change their
3611 definitions slightly.
3613 In general, the following kinds of operations are possible on topics.
3614 First of all, you want to create topics. Secondly, you want to put
3615 groups in topics and to move them around until you have an order you
3616 like. The third kind of operation is to show/hide parts of the whole
3617 shebang. You might want to hide a topic including its subtopics and
3618 groups, to get a better overview of the other groups.
3620 Here is a list of the basic keys that you might need to set up topics
3627 @findex gnus-topic-create-topic
3628 Prompt for a new topic name and create it
3629 (@code{gnus-topic-create-topic}).
3633 @kindex T TAB (Topic)
3635 @findex gnus-topic-indent
3636 ``Indent'' the current topic so that it becomes a sub-topic of the
3637 previous topic (@code{gnus-topic-indent}). If given a prefix,
3638 ``un-indent'' the topic instead.
3641 @kindex M-TAB (Topic)
3642 @findex gnus-topic-unindent
3643 ``Un-indent'' the current topic so that it becomes a sub-topic of the
3644 parent of its current parent (@code{gnus-topic-unindent}).
3648 The following two keys can be used to move groups and topics around.
3649 They work like the well-known cut and paste. @kbd{C-k} is like cut and
3650 @kbd{C-y} is like paste. Of course, this being Emacs, we use the terms
3651 kill and yank rather than cut and paste.
3657 @findex gnus-topic-kill-group
3658 Kill a group or topic (@code{gnus-topic-kill-group}). All groups in the
3659 topic will be removed along with the topic.
3663 @findex gnus-topic-yank-group
3664 Yank the previously killed group or topic
3665 (@code{gnus-topic-yank-group}). Note that all topics will be yanked
3668 So, to move a topic to the beginning of the list of topics, just hit
3669 @kbd{C-k} on it. This is like the ``cut'' part of cut and paste. Then,
3670 move the cursor to the beginning of the buffer (just below the ``Gnus''
3671 topic) and hit @kbd{C-y}. This is like the ``paste'' part of cut and
3672 paste. Like I said -- E-Z.
3674 You can use @kbd{C-k} and @kbd{C-y} on groups as well as on topics. So
3675 you can move topics around as well as groups.
3679 After setting up the topics the way you like them, you might wish to
3680 hide a topic, or to show it again. That's why we have the following
3687 @findex gnus-topic-select-group
3689 Either select a group or fold a topic (@code{gnus-topic-select-group}).
3690 When you perform this command on a group, you'll enter the group, as
3691 usual. When done on a topic line, the topic will be folded (if it was
3692 visible) or unfolded (if it was folded already). So it's basically a
3693 toggling command on topics. In addition, if you give a numerical
3694 prefix, group on that level (and lower) will be displayed.
3698 Now for a list of other commands, in no particular order.
3704 @findex gnus-topic-move-group
3705 Move the current group to some other topic
3706 (@code{gnus-topic-move-group}). This command uses the process/prefix
3707 convention (@pxref{Process/Prefix}).
3711 @findex gnus-topic-jump-to-topic
3712 Go to a topic (@code{gnus-topic-jump-to-topic}).
3716 @findex gnus-topic-copy-group
3717 Copy the current group to some other topic
3718 (@code{gnus-topic-copy-group}). This command uses the process/prefix
3719 convention (@pxref{Process/Prefix}).
3723 @findex gnus-topic-hide-topic
3724 Hide the current topic (@code{gnus-topic-hide-topic}). If given
3725 a prefix, hide the topic permanently.
3729 @findex gnus-topic-show-topic
3730 Show the current topic (@code{gnus-topic-show-topic}). If given
3731 a prefix, show the topic permanently.
3735 @findex gnus-topic-remove-group
3736 Remove a group from the current topic (@code{gnus-topic-remove-group}).
3737 This command is mainly useful if you have the same group in several
3738 topics and wish to remove it from one of the topics. You may also
3739 remove a group from all topics, but in that case, Gnus will add it to
3740 the root topic the next time you start Gnus. In fact, all new groups
3741 (which, naturally, don't belong to any topic) will show up in the root
3744 This command uses the process/prefix convention
3745 (@pxref{Process/Prefix}).
3749 @findex gnus-topic-move-matching
3750 Move all groups that match some regular expression to a topic
3751 (@code{gnus-topic-move-matching}).
3755 @findex gnus-topic-copy-matching
3756 Copy all groups that match some regular expression to a topic
3757 (@code{gnus-topic-copy-matching}).
3761 @findex gnus-topic-toggle-display-empty-topics
3762 Toggle hiding empty topics
3763 (@code{gnus-topic-toggle-display-empty-topics}).
3767 @findex gnus-topic-mark-topic
3768 Mark all groups in the current topic with the process mark
3769 (@code{gnus-topic-mark-topic}). This command works recursively on
3770 sub-topics unless given a prefix.
3773 @kindex T M-# (Topic)
3774 @findex gnus-topic-unmark-topic
3775 Remove the process mark from all groups in the current topic
3776 (@code{gnus-topic-unmark-topic}). This command works recursively on
3777 sub-topics unless given a prefix.
3780 @kindex C-c C-x (Topic)
3781 @findex gnus-topic-expire-articles
3782 Run all expirable articles in the current group or topic through the
3783 expiry process (if any)
3784 (@code{gnus-topic-expire-articles}). (@pxref{Expiring Mail}).
3788 @findex gnus-topic-rename
3789 Rename a topic (@code{gnus-topic-rename}).
3792 @kindex T DEL (Topic)
3793 @findex gnus-topic-delete
3794 Delete an empty topic (@code{gnus-topic-delete}).
3798 @findex gnus-topic-list-active
3799 List all groups that gnus knows about in a topics-ified way
3800 (@code{gnus-topic-list-active}).
3803 @kindex T M-n (Topic)
3804 @findex gnus-topic-goto-next-topic
3805 Go to the next topic (@code{gnus-topic-goto-next-topic}).
3808 @kindex T M-p (Topic)
3809 @findex gnus-topic-goto-previous-topic
3810 Go to the previous topic (@code{gnus-topic-goto-previous-topic}).
3814 @findex gnus-topic-edit-parameters
3815 @cindex group parameters
3816 @cindex topic parameters
3818 Edit the topic parameters (@code{gnus-topic-edit-parameters}).
3819 @xref{Topic Parameters}.
3824 @node Topic Variables
3825 @subsection Topic Variables
3826 @cindex topic variables
3828 The previous section told you how to tell Gnus which topics to display.
3829 This section explains how to tell Gnus what to display about each topic.
3831 @vindex gnus-topic-line-format
3832 The topic lines themselves are created according to the
3833 @code{gnus-topic-line-format} variable (@pxref{Formatting Variables}).
3846 Number of groups in the topic.
3848 Number of unread articles in the topic.
3850 Number of unread articles in the topic and all its subtopics.
3853 @vindex gnus-topic-indent-level
3854 Each sub-topic (and the groups in the sub-topics) will be indented with
3855 @code{gnus-topic-indent-level} times the topic level number of spaces.
3858 @vindex gnus-topic-mode-hook
3859 @code{gnus-topic-mode-hook} is called in topic minor mode buffers.
3861 @vindex gnus-topic-display-empty-topics
3862 The @code{gnus-topic-display-empty-topics} says whether to display even
3863 topics that have no unread articles in them. The default is @code{t}.
3867 @subsection Topic Sorting
3868 @cindex topic sorting
3870 You can sort the groups in each topic individually with the following
3876 @kindex T S a (Topic)
3877 @findex gnus-topic-sort-groups-by-alphabet
3878 Sort the current topic alphabetically by group name
3879 (@code{gnus-topic-sort-groups-by-alphabet}).
3882 @kindex T S u (Topic)
3883 @findex gnus-topic-sort-groups-by-unread
3884 Sort the current topic by the number of unread articles
3885 (@code{gnus-topic-sort-groups-by-unread}).
3888 @kindex T S l (Topic)
3889 @findex gnus-topic-sort-groups-by-level
3890 Sort the current topic by group level
3891 (@code{gnus-topic-sort-groups-by-level}).
3894 @kindex T S v (Topic)
3895 @findex gnus-topic-sort-groups-by-score
3896 Sort the current topic by group score
3897 (@code{gnus-topic-sort-groups-by-score}). @xref{Group Score}.
3900 @kindex T S r (Topic)
3901 @findex gnus-topic-sort-groups-by-rank
3902 Sort the current topic by group rank
3903 (@code{gnus-topic-sort-groups-by-rank}). @xref{Group Score}.
3906 @kindex T S m (Topic)
3907 @findex gnus-topic-sort-groups-by-method
3908 Sort the current topic alphabetically by back end name
3909 (@code{gnus-topic-sort-groups-by-method}).
3912 @kindex T S e (Topic)
3913 @findex gnus-topic-sort-groups-by-server
3914 Sort the current topic alphabetically by server name
3915 (@code{gnus-topic-sort-groups-by-server}).
3918 @kindex T S s (Topic)
3919 @findex gnus-topic-sort-groups
3920 Sort the current topic according to the function(s) given by the
3921 @code{gnus-group-sort-function} variable
3922 (@code{gnus-topic-sort-groups}).
3926 When given a prefix argument, all these commands will sort in reverse
3927 order. @xref{Sorting Groups}, for more information about group
3931 @node Topic Topology
3932 @subsection Topic Topology
3933 @cindex topic topology
3936 So, let's have a look at an example group buffer:
3943 2: alt.religion.emacs
3946 0: comp.talk.emacs.recovery
3948 8: comp.binaries.fractals
3949 13: comp.sources.unix
3953 So, here we have one top-level topic (@samp{Gnus}), two topics under
3954 that, and one sub-topic under one of the sub-topics. (There is always
3955 just one (1) top-level topic). This topology can be expressed as
3960 (("Emacs -- I wuw it!" visible)
3961 (("Naughty Emacs" visible)))
3965 @vindex gnus-topic-topology
3966 This is in fact how the variable @code{gnus-topic-topology} would look
3967 for the display above. That variable is saved in the @file{.newsrc.eld}
3968 file, and shouldn't be messed with manually---unless you really want
3969 to. Since this variable is read from the @file{.newsrc.eld} file,
3970 setting it in any other startup files will have no effect.
3972 This topology shows what topics are sub-topics of what topics (right),
3973 and which topics are visible. Two settings are currently
3974 allowed---@code{visible} and @code{invisible}.
3977 @node Topic Parameters
3978 @subsection Topic Parameters
3979 @cindex topic parameters
3981 All groups in a topic will inherit group parameters from the parent
3982 (and ancestor) topic parameters. All valid group parameters are valid
3983 topic parameters (@pxref{Group Parameters}). When the agent is
3984 enabled, all agent parameters (See Agent Parameters in @ref{Category
3985 Syntax}) are also valid topic parameters.
3987 In addition, the following parameters are only valid as topic
3992 When subscribing new groups by topic (@pxref{Subscription Methods}), the
3993 @code{subscribe} topic parameter says what groups go in what topic. Its
3994 value should be a regexp to match the groups that should go in that
3997 @item subscribe-level
3998 When subscribing new groups by topic (see the @code{subscribe} parameter),
3999 the group will be subscribed with the level specified in the
4000 @code{subscribe-level} instead of @code{gnus-level-default-subscribed}.
4004 Group parameters (of course) override topic parameters, and topic
4005 parameters in sub-topics override topic parameters in super-topics. You
4006 know. Normal inheritance rules. (@dfn{Rules} is here a noun, not a
4007 verb, although you may feel free to disagree with me here.)
4014 2: alt.religion.emacs
4018 0: comp.talk.emacs.recovery
4020 8: comp.binaries.fractals
4021 13: comp.sources.unix
4026 The @samp{Emacs} topic has the topic parameter @code{(score-file
4027 . "emacs.SCORE")}; the @samp{Relief} topic has the topic parameter
4028 @code{(score-file . "relief.SCORE")}; and the @samp{Misc} topic has the
4029 topic parameter @code{(score-file . "emacs.SCORE")}. In addition,
4030 @* @samp{alt.religion.emacs} has the group parameter @code{(score-file
4031 . "religion.SCORE")}.
4033 Now, when you enter @samp{alt.sex.emacs} in the @samp{Relief} topic, you
4034 will get the @file{relief.SCORE} home score file. If you enter the same
4035 group in the @samp{Emacs} topic, you'll get the @file{emacs.SCORE} home
4036 score file. If you enter the group @samp{alt.religion.emacs}, you'll
4037 get the @file{religion.SCORE} home score file.
4039 This seems rather simple and self-evident, doesn't it? Well, yes. But
4040 there are some problems, especially with the @code{total-expiry}
4041 parameter. Say you have a mail group in two topics; one with
4042 @code{total-expiry} and one without. What happens when you do @kbd{M-x
4043 gnus-expire-all-expirable-groups}? Gnus has no way of telling which one
4044 of these topics you mean to expire articles from, so anything may
4045 happen. In fact, I hereby declare that it is @dfn{undefined} what
4046 happens. You just have to be careful if you do stuff like that.
4049 @node Misc Group Stuff
4050 @section Misc Group Stuff
4053 * Scanning New Messages:: Asking Gnus to see whether new messages have arrived.
4054 * Group Information:: Information and help on groups and Gnus.
4055 * Group Timestamp:: Making Gnus keep track of when you last read a group.
4056 * File Commands:: Reading and writing the Gnus files.
4057 * Sieve Commands:: Managing Sieve scripts.
4064 @findex gnus-group-enter-server-mode
4065 Enter the server buffer (@code{gnus-group-enter-server-mode}).
4066 @xref{Server Buffer}.
4070 @findex gnus-group-post-news
4071 Start composing a message (a news by default)
4072 (@code{gnus-group-post-news}). If given a prefix, post to the group
4073 under the point. If the prefix is 1, prompt for a group to post to.
4074 Contrary to what the name of this function suggests, the prepared
4075 article might be a mail instead of a news, if a mail group is specified
4076 with the prefix argument. @xref{Composing Messages}.
4080 @findex gnus-group-mail
4081 Mail a message somewhere (@code{gnus-group-mail}). If given a prefix,
4082 use the posting style of the group under the point. If the prefix is 1,
4083 prompt for a group name to find the posting style.
4084 @xref{Composing Messages}.
4088 @findex gnus-group-news
4089 Start composing a news (@code{gnus-group-news}). If given a prefix,
4090 post to the group under the point. If the prefix is 1, prompt
4091 for group to post to. @xref{Composing Messages}.
4093 This function actually prepares a news even when using mail groups.
4094 This is useful for ``posting'' messages to mail groups without actually
4095 sending them over the network: they're just saved directly to the group
4096 in question. The corresponding back end must have a request-post method
4097 for this to work though.
4101 Variables for the group buffer:
4105 @item gnus-group-mode-hook
4106 @vindex gnus-group-mode-hook
4107 is called after the group buffer has been
4110 @item gnus-group-prepare-hook
4111 @vindex gnus-group-prepare-hook
4112 is called after the group buffer is
4113 generated. It may be used to modify the buffer in some strange,
4116 @item gnus-group-prepared-hook
4117 @vindex gnus-group-prepare-hook
4118 is called as the very last thing after the group buffer has been
4119 generated. It may be used to move point around, for instance.
4121 @item gnus-permanently-visible-groups
4122 @vindex gnus-permanently-visible-groups
4123 Groups matching this regexp will always be listed in the group buffer,
4124 whether they are empty or not.
4126 @item gnus-group-name-charset-method-alist
4127 @vindex gnus-group-name-charset-method-alist
4128 An alist of method and the charset for group names. It is used to show
4129 non-@acronym{ASCII} group names.
4133 (setq gnus-group-name-charset-method-alist
4134 '(((nntp "news.com.cn") . cn-gb-2312)))
4137 @item gnus-group-name-charset-group-alist
4138 @cindex UTF-8 group names
4139 @vindex gnus-group-name-charset-group-alist
4140 An alist of regexp of group name and the charset for group names. It
4141 is used to show non-@acronym{ASCII} group names. @code{((".*"
4142 utf-8))} is the default value if UTF-8 is supported, otherwise the
4143 default is @code{nil}.
4147 (setq gnus-group-name-charset-group-alist
4148 '(("\\.com\\.cn:" . cn-gb-2312)))
4153 @node Scanning New Messages
4154 @subsection Scanning New Messages
4155 @cindex new messages
4156 @cindex scanning new news
4162 @findex gnus-group-get-new-news
4163 @c @icon{gnus-group-get-new-news}
4164 Check the server(s) for new articles. If the numerical prefix is used,
4165 this command will check only groups of level @var{arg} and lower
4166 (@code{gnus-group-get-new-news}). If given a non-numerical prefix, this
4167 command will force a total re-reading of the active file(s) from the
4172 @findex gnus-group-get-new-news-this-group
4173 @vindex gnus-goto-next-group-when-activating
4174 @c @icon{gnus-group-get-new-news-this-group}
4175 Check whether new articles have arrived in the current group
4176 (@code{gnus-group-get-new-news-this-group}).
4177 @code{gnus-goto-next-group-when-activating} says whether this command is
4178 to move point to the next group or not. It is @code{t} by default.
4180 @findex gnus-activate-all-groups
4181 @cindex activating groups
4183 @kindex C-c M-g (Group)
4184 Activate absolutely all groups (@code{gnus-activate-all-groups}).
4189 @findex gnus-group-restart
4190 Restart gnus (@code{gnus-group-restart}). This saves the @file{.newsrc}
4191 file(s), closes the connection to all servers, clears up all run-time
4192 gnus variables, and then starts gnus all over again.
4196 @vindex gnus-get-new-news-hook
4197 @code{gnus-get-new-news-hook} is run just before checking for new news.
4199 @vindex gnus-after-getting-new-news-hook
4200 @code{gnus-after-getting-new-news-hook} is run after checking for new
4204 @node Group Information
4205 @subsection Group Information
4206 @cindex group information
4207 @cindex information on groups
4214 @findex gnus-group-fetch-faq
4215 @vindex gnus-group-faq-directory
4218 Try to fetch the @acronym{FAQ} for the current group
4219 (@code{gnus-group-fetch-faq}). Gnus will try to get the @acronym{FAQ}
4220 from @code{gnus-group-faq-directory}, which is usually a directory on
4221 a remote machine. This variable can also be a list of directories.
4222 In that case, giving a prefix to this command will allow you to choose
4223 between the various sites. @code{ange-ftp} (or @code{efs}) will be
4224 used for fetching the file.
4226 If fetching from the first site is unsuccessful, gnus will attempt to go
4227 through @code{gnus-group-faq-directory} and try to open them one by one.
4231 @findex gnus-group-fetch-charter
4232 @vindex gnus-group-charter-alist
4234 Try to open the charter for the current group in a web browser
4235 (@code{gnus-group-fetch-charter}). Query for a group if given a
4238 Gnus will use @code{gnus-group-charter-alist} to find the location of
4239 the charter. If no location is known, Gnus will fetch the control
4240 messages for the group, which in some cases includes the charter.
4244 @findex gnus-group-fetch-control
4245 @vindex gnus-group-fetch-control-use-browse-url
4246 @cindex control message
4247 Fetch the control messages for the group from the archive at
4248 @code{ftp.isc.org} (@code{gnus-group-fetch-control}). Query for a
4249 group if given a prefix argument.
4251 If @code{gnus-group-fetch-control-use-browse-url} is non-@code{nil},
4252 Gnus will open the control messages in a browser using
4253 @code{browse-url}. Otherwise they are fetched using @code{ange-ftp}
4254 and displayed in an ephemeral group.
4256 Note that the control messages are compressed. To use this command
4257 you need to turn on @code{auto-compression-mode} (@pxref{Compressed
4258 Files, ,Compressed Files, emacs, The Emacs Manual}).
4262 @c @icon{gnus-group-describe-group}
4264 @kindex C-c C-d (Group)
4265 @cindex describing groups
4266 @cindex group description
4267 @findex gnus-group-describe-group
4268 Describe the current group (@code{gnus-group-describe-group}). If given
4269 a prefix, force Gnus to re-read the description from the server.
4273 @findex gnus-group-describe-all-groups
4274 Describe all groups (@code{gnus-group-describe-all-groups}). If given a
4275 prefix, force gnus to re-read the description file from the server.
4282 @findex gnus-version
4283 Display current gnus version numbers (@code{gnus-version}).
4287 @findex gnus-group-describe-briefly
4288 Give a very short help message (@code{gnus-group-describe-briefly}).
4291 @kindex C-c C-i (Group)
4294 @findex gnus-info-find-node
4295 Go to the gnus info node (@code{gnus-info-find-node}).
4299 @node Group Timestamp
4300 @subsection Group Timestamp
4302 @cindex group timestamps
4304 It can be convenient to let gnus keep track of when you last read a
4305 group. To set the ball rolling, you should add
4306 @code{gnus-group-set-timestamp} to @code{gnus-select-group-hook}:
4309 (add-hook 'gnus-select-group-hook 'gnus-group-set-timestamp)
4312 After doing this, each time you enter a group, it'll be recorded.
4314 This information can be displayed in various ways---the easiest is to
4315 use the @samp{%d} spec in the group line format:
4318 (setq gnus-group-line-format
4319 "%M\%S\%p\%P\%5y: %(%-40,40g%) %d\n")
4322 This will result in lines looking like:
4325 * 0: mail.ding 19961002T012943
4326 0: custom 19961002T012713
4329 As you can see, the date is displayed in compact ISO 8601 format. This
4330 may be a bit too much, so to just display the date, you could say
4334 (setq gnus-group-line-format
4335 "%M\%S\%p\%P\%5y: %(%-40,40g%) %6,6~(cut 2)d\n")
4338 If you would like greater control of the time format, you can use a
4339 user-defined format spec. Something like the following should do the
4343 (setq gnus-group-line-format
4344 "%M\%S\%p\%P\%5y: %(%-40,40g%) %ud\n")
4345 (defun gnus-user-format-function-d (headers)
4346 (let ((time (gnus-group-timestamp gnus-tmp-group)))
4348 (format-time-string "%b %d %H:%M" time)
4354 @subsection File Commands
4355 @cindex file commands
4361 @findex gnus-group-read-init-file
4362 @vindex gnus-init-file
4363 @cindex reading init file
4364 Re-read the init file (@code{gnus-init-file}, which defaults to
4365 @file{~/.gnus.el}) (@code{gnus-group-read-init-file}).
4369 @findex gnus-group-save-newsrc
4370 @cindex saving .newsrc
4371 Save the @file{.newsrc.eld} file (and @file{.newsrc} if wanted)
4372 (@code{gnus-group-save-newsrc}). If given a prefix, force saving the
4373 file(s) whether Gnus thinks it is necessary or not.
4376 @c @kindex Z (Group)
4377 @c @findex gnus-group-clear-dribble
4378 @c Clear the dribble buffer (@code{gnus-group-clear-dribble}).
4383 @node Sieve Commands
4384 @subsection Sieve Commands
4385 @cindex group sieve commands
4387 Sieve is a server-side mail filtering language. In Gnus you can use
4388 the @code{sieve} group parameter (@pxref{Group Parameters}) to specify
4389 sieve rules that should apply to each group. Gnus provides two
4390 commands to translate all these group parameters into a proper Sieve
4391 script that can be transfered to the server somehow.
4393 @vindex gnus-sieve-file
4394 @vindex gnus-sieve-region-start
4395 @vindex gnus-sieve-region-end
4396 The generated Sieve script is placed in @code{gnus-sieve-file} (by
4397 default @file{~/.sieve}). The Sieve code that Gnus generate is placed
4398 between two delimiters, @code{gnus-sieve-region-start} and
4399 @code{gnus-sieve-region-end}, so you may write additional Sieve code
4400 outside these delimiters that will not be removed the next time you
4401 regenerate the Sieve script.
4403 @vindex gnus-sieve-crosspost
4404 The variable @code{gnus-sieve-crosspost} controls how the Sieve script
4405 is generated. If it is non-@code{nil} (the default) articles is
4406 placed in all groups that have matching rules, otherwise the article
4407 is only placed in the group with the first matching rule. For
4408 example, the group parameter @samp{(sieve address "sender"
4409 "owner-ding@@hpc.uh.edu")} will generate the following piece of Sieve
4410 code if @code{gnus-sieve-crosspost} is @code{nil}. (When
4411 @code{gnus-sieve-crosspost} is non-@code{nil}, it looks the same
4412 except that the line containing the call to @code{stop} is removed.)
4415 if address "sender" "owner-ding@@hpc.uh.edu" @{
4416 fileinto "INBOX.ding";
4421 @xref{Top, Emacs Sieve, Top, sieve, Emacs Sieve}.
4427 @findex gnus-sieve-generate
4428 @vindex gnus-sieve-file
4429 @cindex generating sieve script
4430 Regenerate a Sieve script from the @code{sieve} group parameters and
4431 put you into the @code{gnus-sieve-file} without saving it.
4435 @findex gnus-sieve-update
4436 @vindex gnus-sieve-file
4437 @cindex updating sieve script
4438 Regenerates the Gnus managed part of @code{gnus-sieve-file} using the
4439 @code{sieve} group parameters, save the file and upload it to the
4440 server using the @code{sieveshell} program.
4445 @node Summary Buffer
4446 @chapter Summary Buffer
4447 @cindex summary buffer
4449 A line for each article is displayed in the summary buffer. You can
4450 move around, read articles, post articles and reply to articles.
4452 The most common way to a summary buffer is to select a group from the
4453 group buffer (@pxref{Selecting a Group}).
4455 You can have as many summary buffers open as you wish.
4458 * Summary Buffer Format:: Deciding how the summary buffer is to look.
4459 * Summary Maneuvering:: Moving around the summary buffer.
4460 * Choosing Articles:: Reading articles.
4461 * Paging the Article:: Scrolling the current article.
4462 * Reply Followup and Post:: Posting articles.
4463 * Delayed Articles:: Send articles at a later time.
4464 * Marking Articles:: Marking articles as read, expirable, etc.
4465 * Limiting:: You can limit the summary buffer.
4466 * Threading:: How threads are made.
4467 * Sorting the Summary Buffer:: How articles and threads are sorted.
4468 * Asynchronous Fetching:: Gnus might be able to pre-fetch articles.
4469 * Article Caching:: You may store articles in a cache.
4470 * Persistent Articles:: Making articles expiry-resistant.
4471 * Article Backlog:: Having already read articles hang around.
4472 * Saving Articles:: Ways of customizing article saving.
4473 * Decoding Articles:: Gnus can treat series of (uu)encoded articles.
4474 * Article Treatment:: The article buffer can be mangled at will.
4475 * MIME Commands:: Doing MIMEy things with the articles.
4476 * Charsets:: Character set issues.
4477 * Article Commands:: Doing various things with the article buffer.
4478 * Summary Sorting:: Sorting the summary buffer in various ways.
4479 * Finding the Parent:: No child support? Get the parent.
4480 * Alternative Approaches:: Reading using non-default summaries.
4481 * Tree Display:: A more visual display of threads.
4482 * Mail Group Commands:: Some commands can only be used in mail groups.
4483 * Various Summary Stuff:: What didn't fit anywhere else.
4484 * Exiting the Summary Buffer:: Returning to the Group buffer,
4485 or reselecting the current group.
4486 * Crosspost Handling:: How crossposted articles are dealt with.
4487 * Duplicate Suppression:: An alternative when crosspost handling fails.
4488 * Security:: Decrypt and Verify.
4489 * Mailing List:: Mailing list minor mode.
4493 @node Summary Buffer Format
4494 @section Summary Buffer Format
4495 @cindex summary buffer format
4499 \gnusfigure{The Summary Buffer}{180}{
4500 \put(0,0){\epsfig{figure=ps/summary,width=7.5cm}}
4501 \put(445,0){\makebox(0,0)[br]{\epsfig{figure=ps/summary-article,width=7.5cm}}}
4507 * Summary Buffer Lines:: You can specify how summary lines should look.
4508 * To From Newsgroups:: How to not display your own name.
4509 * Summary Buffer Mode Line:: You can say how the mode line should look.
4510 * Summary Highlighting:: Making the summary buffer all pretty and nice.
4513 @findex mail-extract-address-components
4514 @findex gnus-extract-address-components
4515 @vindex gnus-extract-address-components
4516 Gnus will use the value of the @code{gnus-extract-address-components}
4517 variable as a function for getting the name and address parts of a
4518 @code{From} header. Three pre-defined functions exist:
4519 @code{gnus-extract-address-components}, which is the default, quite
4520 fast, and too simplistic solution;
4521 @code{mail-extract-address-components}, which works nicely, but is
4522 slower; and @code{std11-extract-address-components}, which works very
4523 nicely, but is slower. The default function will return the wrong
4524 answer in 5% of the cases. If this is unacceptable to you, use the
4525 other function instead:
4528 (setq gnus-extract-address-components
4529 'mail-extract-address-components)
4532 @vindex gnus-summary-same-subject
4533 @code{gnus-summary-same-subject} is a string indicating that the current
4534 article has the same subject as the previous. This string will be used
4535 with those specs that require it. The default is @code{""}.
4538 @node Summary Buffer Lines
4539 @subsection Summary Buffer Lines
4541 @vindex gnus-summary-line-format
4542 You can change the format of the lines in the summary buffer by changing
4543 the @code{gnus-summary-line-format} variable. It works along the same
4544 lines as a normal @code{format} string, with some extensions
4545 (@pxref{Formatting Variables}).
4547 There should always be a colon or a point position marker on the line;
4548 the cursor always moves to the point position marker or the colon after
4549 performing an operation. (Of course, Gnus wouldn't be Gnus if it wasn't
4550 possible to change this. Just write a new function
4551 @code{gnus-goto-colon} which does whatever you like with the cursor.)
4552 @xref{Positioning Point}.
4554 The default string is @samp{%U%R%z%I%(%[%4L: %-23,23f%]%) %s\n}.
4556 The following format specification characters and extended format
4557 specification(s) are understood:
4563 Subject string. List identifiers stripped,
4564 @code{gnus-list-identifies}. @xref{Article Hiding}.
4566 Subject if the article is the root of the thread or the previous article
4567 had a different subject, @code{gnus-summary-same-subject} otherwise.
4568 (@code{gnus-summary-same-subject} defaults to @code{""}.)
4570 Full @code{From} header.
4572 The name (from the @code{From} header).
4574 The name, @code{To} header or the @code{Newsgroups} header (@pxref{To
4577 The name (from the @code{From} header). This differs from the @code{n}
4578 spec in that it uses the function designated by the
4579 @code{gnus-extract-address-components} variable, which is slower, but
4580 may be more thorough.
4582 The address (from the @code{From} header). This works the same way as
4585 Number of lines in the article.
4587 Number of characters in the article. This specifier is not supported
4588 in some methods (like nnfolder).
4590 Pretty-printed version of the number of characters in the article;
4591 for example, @samp{1.2k} or @samp{0.4M}.
4593 Indentation based on thread level (@pxref{Customizing Threading}).
4595 A complex trn-style thread tree, showing response-connecting trace
4596 lines. A thread could be drawn like this:
4609 You can customize the appearance with the following options. Note
4610 that it is possible to make the thread display look really neat by
4611 replacing the default @acronym{ASCII} characters with graphic
4612 line-drawing glyphs.
4614 @item gnus-sum-thread-tree-root
4615 @vindex gnus-sum-thread-tree-root
4616 Used for the root of a thread. If @code{nil}, use subject
4617 instead. The default is @samp{> }.
4619 @item gnus-sum-thread-tree-false-root
4620 @vindex gnus-sum-thread-tree-false-root
4621 Used for the false root of a thread (@pxref{Loose Threads}). If
4622 @code{nil}, use subject instead. The default is @samp{> }.
4624 @item gnus-sum-thread-tree-single-indent
4625 @vindex gnus-sum-thread-tree-single-indent
4626 Used for a thread with just one message. If @code{nil}, use subject
4627 instead. The default is @samp{}.
4629 @item gnus-sum-thread-tree-vertical
4630 @vindex gnus-sum-thread-tree-vertical
4631 Used for drawing a vertical line. The default is @samp{| }.
4633 @item gnus-sum-thread-tree-indent
4634 @vindex gnus-sum-thread-tree-indent
4635 Used for indenting. The default is @samp{ }.
4637 @item gnus-sum-thread-tree-leaf-with-other
4638 @vindex gnus-sum-thread-tree-leaf-with-other
4639 Used for a leaf with brothers. The default is @samp{+-> }.
4641 @item gnus-sum-thread-tree-single-leaf
4642 @vindex gnus-sum-thread-tree-single-leaf
4643 Used for a leaf without brothers. The default is @samp{\-> }
4648 Nothing if the article is a root and lots of spaces if it isn't (it
4649 pushes everything after it off the screen).
4651 Opening bracket, which is normally @samp{[}, but can also be @samp{<}
4652 for adopted articles (@pxref{Customizing Threading}).
4654 Closing bracket, which is normally @samp{]}, but can also be @samp{>}
4655 for adopted articles.
4657 One space for each thread level.
4659 Twenty minus thread level spaces.
4661 Unread. @xref{Read Articles}.
4664 This misleadingly named specifier is the @dfn{secondary mark}. This
4665 mark will say whether the article has been replied to, has been cached,
4666 or has been saved. @xref{Other Marks}.
4669 Score as a number (@pxref{Scoring}).
4671 @vindex gnus-summary-zcore-fuzz
4672 Zcore, @samp{+} if above the default level and @samp{-} if below the
4673 default level. If the difference between
4674 @code{gnus-summary-default-score} and the score is less than
4675 @code{gnus-summary-zcore-fuzz}, this spec will not be used.
4683 The @code{Date} in @code{DD-MMM} format.
4685 The @code{Date} in @var{YYYYMMDD}@code{T}@var{HHMMSS} format.
4691 Number of articles in the current sub-thread. Using this spec will slow
4692 down summary buffer generation somewhat.
4694 An @samp{=} (@code{gnus-not-empty-thread-mark}) will be displayed if the
4695 article has any children.
4701 Age sensitive date format. Various date format is defined in
4702 @code{gnus-user-date-format-alist}.
4704 User defined specifier. The next character in the format string should
4705 be a letter. Gnus will call the function
4706 @code{gnus-user-format-function-@var{x}}, where @var{x} is the letter
4707 following @samp{%u}. The function will be passed the current header as
4708 argument. The function should return a string, which will be inserted
4709 into the summary just like information from any other summary specifier.
4712 Text between @samp{%(} and @samp{%)} will be highlighted with
4713 @code{gnus-mouse-face} when the mouse point is placed inside the area.
4714 There can only be one such area.
4716 The @samp{%U} (status), @samp{%R} (replied) and @samp{%z} (zcore) specs
4717 have to be handled with care. For reasons of efficiency, gnus will
4718 compute what column these characters will end up in, and ``hard-code''
4719 that. This means that it is invalid to have these specs after a
4720 variable-length spec. Well, you might not be arrested, but your summary
4721 buffer will look strange, which is bad enough.
4723 The smart choice is to have these specs as far to the left as possible.
4724 (Isn't that the case with everything, though? But I digress.)
4726 This restriction may disappear in later versions of gnus.
4729 @node To From Newsgroups
4730 @subsection To From Newsgroups
4734 In some groups (particularly in archive groups), the @code{From} header
4735 isn't very interesting, since all the articles there are written by
4736 you. To display the information in the @code{To} or @code{Newsgroups}
4737 headers instead, you need to decide three things: What information to
4738 gather; where to display it; and when to display it.
4742 @vindex gnus-extra-headers
4743 The reading of extra header information is controlled by the
4744 @code{gnus-extra-headers}. This is a list of header symbols. For
4748 (setq gnus-extra-headers
4749 '(To Newsgroups X-Newsreader))
4752 This will result in Gnus trying to obtain these three headers, and
4753 storing it in header structures for later easy retrieval.
4756 @findex gnus-extra-header
4757 The value of these extra headers can be accessed via the
4758 @code{gnus-extra-header} function. Here's a format line spec that will
4759 access the @code{X-Newsreader} header:
4762 "%~(form (gnus-extra-header 'X-Newsreader))@@"
4766 @vindex gnus-ignored-from-addresses
4767 The @code{gnus-ignored-from-addresses} variable says when the @samp{%f}
4768 summary line spec returns the @code{To}, @code{Newsreader} or
4769 @code{From} header. If this regexp matches the contents of the
4770 @code{From} header, the value of the @code{To} or @code{Newsreader}
4771 headers are used instead.
4775 @vindex nnmail-extra-headers
4776 A related variable is @code{nnmail-extra-headers}, which controls when
4777 to include extra headers when generating overview (@acronym{NOV}) files.
4778 If you have old overview files, you should regenerate them after
4779 changing this variable, by entering the server buffer using @kbd{^},
4780 and then @kbd{g} on the appropriate mail server (e.g. nnml) to cause
4783 @vindex gnus-summary-line-format
4784 You also have to instruct Gnus to display the data by changing the
4785 @code{%n} spec to the @code{%f} spec in the
4786 @code{gnus-summary-line-format} variable.
4788 In summary, you'd typically put something like the following in
4792 (setq gnus-extra-headers
4794 (setq nnmail-extra-headers gnus-extra-headers)
4795 (setq gnus-summary-line-format
4796 "%U%R%z%I%(%[%4L: %-23,23f%]%) %s\n")
4797 (setq gnus-ignored-from-addresses
4801 (The values listed above are the default values in Gnus. Alter them
4804 A note for news server administrators, or for users who wish to try to
4805 convince their news server administrator to provide some additional
4808 The above is mostly useful for mail groups, where you have control over
4809 the @acronym{NOV} files that are created. However, if you can persuade your
4810 nntp admin to add (in the usual implementation, notably INN):
4816 to the end of her @file{overview.fmt} file, then you can use that just
4817 as you would the extra headers from the mail groups.
4820 @node Summary Buffer Mode Line
4821 @subsection Summary Buffer Mode Line
4823 @vindex gnus-summary-mode-line-format
4824 You can also change the format of the summary mode bar (@pxref{Mode Line
4825 Formatting}). Set @code{gnus-summary-mode-line-format} to whatever you
4826 like. The default is @samp{Gnus: %%b [%A] %Z}.
4828 Here are the elements you can play with:
4834 Unprefixed group name.
4836 Current article number.
4838 Current article score.
4842 Number of unread articles in this group.
4844 Number of unread articles in this group that aren't displayed in the
4847 A string with the number of unread and unselected articles represented
4848 either as @samp{<%U(+%e) more>} if there are both unread and unselected
4849 articles, and just as @samp{<%U more>} if there are just unread articles
4850 and no unselected ones.
4852 Shortish group name. For instance, @samp{rec.arts.anime} will be
4853 shortened to @samp{r.a.anime}.
4855 Subject of the current article.
4857 User-defined spec (@pxref{User-Defined Specs}).
4859 Name of the current score file (@pxref{Scoring}).
4861 Number of dormant articles (@pxref{Unread Articles}).
4863 Number of ticked articles (@pxref{Unread Articles}).
4865 Number of articles that have been marked as read in this session.
4867 Number of articles expunged by the score files.
4871 @node Summary Highlighting
4872 @subsection Summary Highlighting
4876 @item gnus-visual-mark-article-hook
4877 @vindex gnus-visual-mark-article-hook
4878 This hook is run after selecting an article. It is meant to be used for
4879 highlighting the article in some way. It is not run if
4880 @code{gnus-visual} is @code{nil}.
4882 @item gnus-summary-update-hook
4883 @vindex gnus-summary-update-hook
4884 This hook is called when a summary line is changed. It is not run if
4885 @code{gnus-visual} is @code{nil}.
4887 @item gnus-summary-selected-face
4888 @vindex gnus-summary-selected-face
4889 This is the face (or @dfn{font} as some people call it) used to
4890 highlight the current article in the summary buffer.
4892 @item gnus-summary-highlight
4893 @vindex gnus-summary-highlight
4894 Summary lines are highlighted according to this variable, which is a
4895 list where the elements are of the format @code{(@var{form}
4896 . @var{face})}. If you would, for instance, like ticked articles to be
4897 italic and high-scored articles to be bold, you could set this variable
4900 (((eq mark gnus-ticked-mark) . italic)
4901 ((> score default) . bold))
4903 As you may have guessed, if @var{form} returns a non-@code{nil} value,
4904 @var{face} will be applied to the line.
4908 @node Summary Maneuvering
4909 @section Summary Maneuvering
4910 @cindex summary movement
4912 All the straight movement commands understand the numeric prefix and
4913 behave pretty much as you'd expect.
4915 None of these commands select articles.
4920 @kindex M-n (Summary)
4921 @kindex G M-n (Summary)
4922 @findex gnus-summary-next-unread-subject
4923 Go to the next summary line of an unread article
4924 (@code{gnus-summary-next-unread-subject}).
4928 @kindex M-p (Summary)
4929 @kindex G M-p (Summary)
4930 @findex gnus-summary-prev-unread-subject
4931 Go to the previous summary line of an unread article
4932 (@code{gnus-summary-prev-unread-subject}).
4935 @kindex G g (Summary)
4936 @findex gnus-summary-goto-subject
4937 Ask for an article number and then go to the summary line of that article
4938 without displaying the article (@code{gnus-summary-goto-subject}).
4941 If gnus asks you to press a key to confirm going to the next group, you
4942 can use the @kbd{C-n} and @kbd{C-p} keys to move around the group
4943 buffer, searching for the next group to read without actually returning
4944 to the group buffer.
4946 Variables related to summary movement:
4950 @vindex gnus-auto-select-next
4951 @item gnus-auto-select-next
4952 If you issue one of the movement commands (like @kbd{n}) and there are
4953 no more unread articles after the current one, gnus will offer to go to
4954 the next group. If this variable is @code{t} and the next group is
4955 empty, gnus will exit summary mode and return to the group buffer. If
4956 this variable is neither @code{t} nor @code{nil}, gnus will select the
4957 next group with unread articles. As a special case, if this variable
4958 is @code{quietly}, Gnus will select the next group without asking for
4959 confirmation. If this variable is @code{almost-quietly}, the same
4960 will happen only if you are located on the last article in the group.
4961 Finally, if this variable is @code{slightly-quietly}, the @kbd{Z n}
4962 command will go to the next group without confirmation. Also
4963 @pxref{Group Levels}.
4965 @item gnus-auto-select-same
4966 @vindex gnus-auto-select-same
4967 If non-@code{nil}, all the movement commands will try to go to the next
4968 article with the same subject as the current. (@dfn{Same} here might
4969 mean @dfn{roughly equal}. See @code{gnus-summary-gather-subject-limit}
4970 for details (@pxref{Customizing Threading}).) If there are no more
4971 articles with the same subject, go to the first unread article.
4973 This variable is not particularly useful if you use a threaded display.
4975 @item gnus-summary-check-current
4976 @vindex gnus-summary-check-current
4977 If non-@code{nil}, all the ``unread'' movement commands will not proceed
4978 to the next (or previous) article if the current article is unread.
4979 Instead, they will choose the current article.
4981 @item gnus-auto-center-summary
4982 @vindex gnus-auto-center-summary
4983 If non-@code{nil}, gnus will keep the point in the summary buffer
4984 centered at all times. This makes things quite tidy, but if you have a
4985 slow network connection, or simply do not like this un-Emacsism, you can
4986 set this variable to @code{nil} to get the normal Emacs scrolling
4987 action. This will also inhibit horizontal re-centering of the summary
4988 buffer, which might make it more inconvenient to read extremely long
4991 This variable can also be a number. In that case, center the window at
4992 the given number of lines from the top.
4997 @node Choosing Articles
4998 @section Choosing Articles
4999 @cindex selecting articles
5002 * Choosing Commands:: Commands for choosing articles.
5003 * Choosing Variables:: Variables that influence these commands.
5007 @node Choosing Commands
5008 @subsection Choosing Commands
5010 None of the following movement commands understand the numeric prefix,
5011 and they all select and display an article.
5013 If you want to fetch new articles or redisplay the group, see
5014 @ref{Exiting the Summary Buffer}.
5018 @kindex SPACE (Summary)
5019 @findex gnus-summary-next-page
5020 Select the current article, or, if that one's read already, the next
5021 unread article (@code{gnus-summary-next-page}).
5023 If you have an article window open already and you press @kbd{SPACE}
5024 again, the article will be scrolled. This lets you conveniently
5025 @kbd{SPACE} through an entire newsgroup. @xref{Paging the Article}.
5030 @kindex G n (Summary)
5031 @findex gnus-summary-next-unread-article
5032 @c @icon{gnus-summary-next-unread}
5033 Go to next unread article (@code{gnus-summary-next-unread-article}).
5038 @findex gnus-summary-prev-unread-article
5039 @c @icon{gnus-summary-prev-unread}
5040 Go to previous unread article (@code{gnus-summary-prev-unread-article}).
5045 @kindex G N (Summary)
5046 @findex gnus-summary-next-article
5047 Go to the next article (@code{gnus-summary-next-article}).
5052 @kindex G P (Summary)
5053 @findex gnus-summary-prev-article
5054 Go to the previous article (@code{gnus-summary-prev-article}).
5057 @kindex G C-n (Summary)
5058 @findex gnus-summary-next-same-subject
5059 Go to the next article with the same subject
5060 (@code{gnus-summary-next-same-subject}).
5063 @kindex G C-p (Summary)
5064 @findex gnus-summary-prev-same-subject
5065 Go to the previous article with the same subject
5066 (@code{gnus-summary-prev-same-subject}).
5070 @kindex G f (Summary)
5072 @findex gnus-summary-first-unread-article
5073 Go to the first unread article
5074 (@code{gnus-summary-first-unread-article}).
5078 @kindex G b (Summary)
5080 @findex gnus-summary-best-unread-article
5081 Go to the unread article with the highest score
5082 (@code{gnus-summary-best-unread-article}). If given a prefix argument,
5083 go to the first unread article that has a score over the default score.
5088 @kindex G l (Summary)
5089 @findex gnus-summary-goto-last-article
5090 Go to the previous article read (@code{gnus-summary-goto-last-article}).
5093 @kindex G o (Summary)
5094 @findex gnus-summary-pop-article
5096 @cindex article history
5097 Pop an article off the summary history and go to this article
5098 (@code{gnus-summary-pop-article}). This command differs from the
5099 command above in that you can pop as many previous articles off the
5100 history as you like, while @kbd{l} toggles the two last read articles.
5101 For a somewhat related issue (if you use these commands a lot),
5102 @pxref{Article Backlog}.
5107 @kindex G j (Summary)
5108 @findex gnus-summary-goto-article
5109 Ask for an article number or @code{Message-ID}, and then go to that
5110 article (@code{gnus-summary-goto-article}).
5115 @node Choosing Variables
5116 @subsection Choosing Variables
5118 Some variables relevant for moving and selecting articles:
5121 @item gnus-auto-extend-newsgroup
5122 @vindex gnus-auto-extend-newsgroup
5123 All the movement commands will try to go to the previous (or next)
5124 article, even if that article isn't displayed in the Summary buffer if
5125 this variable is non-@code{nil}. Gnus will then fetch the article from
5126 the server and display it in the article buffer.
5128 @item gnus-select-article-hook
5129 @vindex gnus-select-article-hook
5130 This hook is called whenever an article is selected. By default it
5131 exposes any threads hidden under the selected article. If you would
5132 like each article to be saved in the Agent as you read it, putting
5133 @code{gnus-agent-fetch-selected-article} on this hook will do so.
5135 @item gnus-mark-article-hook
5136 @vindex gnus-mark-article-hook
5137 @findex gnus-summary-mark-unread-as-read
5138 @findex gnus-summary-mark-read-and-unread-as-read
5139 @findex gnus-unread-mark
5140 This hook is called whenever an article is selected. It is intended to
5141 be used for marking articles as read. The default value is
5142 @code{gnus-summary-mark-read-and-unread-as-read}, and will change the
5143 mark of almost any article you read to @code{gnus-unread-mark}. The
5144 only articles not affected by this function are ticked, dormant, and
5145 expirable articles. If you'd instead like to just have unread articles
5146 marked as read, you can use @code{gnus-summary-mark-unread-as-read}
5147 instead. It will leave marks like @code{gnus-low-score-mark},
5148 @code{gnus-del-mark} (and so on) alone.
5153 @node Paging the Article
5154 @section Scrolling the Article
5155 @cindex article scrolling
5160 @kindex SPACE (Summary)
5161 @findex gnus-summary-next-page
5162 Pressing @kbd{SPACE} will scroll the current article forward one page,
5163 or, if you have come to the end of the current article, will choose the
5164 next article (@code{gnus-summary-next-page}).
5166 @vindex gnus-article-boring-faces
5167 @vindex gnus-article-skip-boring
5168 If @code{gnus-article-skip-boring} is non-@code{nil} and the rest of
5169 the article consists only of citations and signature, then it will be
5170 skipped; the next article will be shown instead. You can customize
5171 what is considered uninteresting with
5172 @code{gnus-article-boring-faces}. You can manually view the article's
5173 pages, no matter how boring, using @kbd{C-M-v}.
5176 @kindex DEL (Summary)
5177 @findex gnus-summary-prev-page
5178 Scroll the current article back one page (@code{gnus-summary-prev-page}).
5181 @kindex RET (Summary)
5182 @findex gnus-summary-scroll-up
5183 Scroll the current article one line forward
5184 (@code{gnus-summary-scroll-up}).
5187 @kindex M-RET (Summary)
5188 @findex gnus-summary-scroll-down
5189 Scroll the current article one line backward
5190 (@code{gnus-summary-scroll-down}).
5194 @kindex A g (Summary)
5196 @findex gnus-summary-show-article
5197 @vindex gnus-summary-show-article-charset-alist
5198 (Re)fetch the current article (@code{gnus-summary-show-article}). If
5199 given a prefix, fetch the current article, but don't run any of the
5200 article treatment functions. This will give you a ``raw'' article, just
5201 the way it came from the server.
5203 If given a numerical prefix, you can do semi-manual charset stuff.
5204 @kbd{C-u 0 g cn-gb-2312 RET} will decode the message as if it were
5205 encoded in the @code{cn-gb-2312} charset. If you have
5208 (setq gnus-summary-show-article-charset-alist
5213 then you can say @kbd{C-u 1 g} to get the same effect.
5218 @kindex A < (Summary)
5219 @findex gnus-summary-beginning-of-article
5220 Scroll to the beginning of the article
5221 (@code{gnus-summary-beginning-of-article}).
5226 @kindex A > (Summary)
5227 @findex gnus-summary-end-of-article
5228 Scroll to the end of the article (@code{gnus-summary-end-of-article}).
5232 @kindex A s (Summary)
5234 @findex gnus-summary-isearch-article
5235 Perform an isearch in the article buffer
5236 (@code{gnus-summary-isearch-article}).
5240 @findex gnus-summary-select-article-buffer
5241 Select the article buffer (@code{gnus-summary-select-article-buffer}).
5246 @node Reply Followup and Post
5247 @section Reply, Followup and Post
5250 * Summary Mail Commands:: Sending mail.
5251 * Summary Post Commands:: Sending news.
5252 * Summary Message Commands:: Other Message-related commands.
5253 * Canceling and Superseding::
5257 @node Summary Mail Commands
5258 @subsection Summary Mail Commands
5260 @cindex composing mail
5262 Commands for composing a mail message:
5268 @kindex S r (Summary)
5270 @findex gnus-summary-reply
5271 @c @icon{gnus-summary-mail-reply}
5272 @c @icon{gnus-summary-reply}
5273 Mail a reply to the author of the current article
5274 (@code{gnus-summary-reply}).
5279 @kindex S R (Summary)
5280 @findex gnus-summary-reply-with-original
5281 @c @icon{gnus-summary-reply-with-original}
5282 Mail a reply to the author of the current article and include the
5283 original message (@code{gnus-summary-reply-with-original}). This
5284 command uses the process/prefix convention.
5287 @kindex S w (Summary)
5288 @findex gnus-summary-wide-reply
5289 Mail a wide reply to the author of the current article
5290 (@code{gnus-summary-wide-reply}). A @dfn{wide reply} is a reply that
5291 goes out to all people listed in the @code{To}, @code{From} (or
5292 @code{Reply-to}) and @code{Cc} headers. If @code{Mail-Followup-To} is
5293 present, that's used instead.
5296 @kindex S W (Summary)
5297 @findex gnus-summary-wide-reply-with-original
5298 Mail a wide reply to the current article and include the original
5299 message (@code{gnus-summary-wide-reply-with-original}). This command uses
5300 the process/prefix convention.
5303 @kindex S v (Summary)
5304 @findex gnus-summary-very-wide-reply
5305 Mail a very wide reply to the author of the current article
5306 (@code{gnus-summary-wide-reply}). A @dfn{very wide reply} is a reply
5307 that goes out to all people listed in the @code{To}, @code{From} (or
5308 @code{Reply-to}) and @code{Cc} headers in all the process/prefixed
5309 articles. This command uses the process/prefix convention.
5312 @kindex S V (Summary)
5313 @findex gnus-summary-very-wide-reply-with-original
5314 Mail a very wide reply to the author of the current article and include the
5315 original message (@code{gnus-summary-very-wide-reply-with-original}). This
5316 command uses the process/prefix convention.
5319 @kindex S B r (Summary)
5320 @findex gnus-summary-reply-broken-reply-to
5321 Mail a reply to the author of the current article but ignore the
5322 @code{Reply-To} field (@code{gnus-summary-reply-broken-reply-to}).
5323 If you need this because a mailing list incorrectly sets a
5324 @code{Reply-To} header pointing to the list, you probably want to set
5325 the @code{broken-reply-to} group parameter instead, so things will work
5326 correctly. @xref{Group Parameters}.
5329 @kindex S B R (Summary)
5330 @findex gnus-summary-reply-broken-reply-to-with-original
5331 Mail a reply to the author of the current article and include the
5332 original message but ignore the @code{Reply-To} field
5333 (@code{gnus-summary-reply-broken-reply-to-with-original}).
5337 @kindex S o m (Summary)
5338 @kindex C-c C-f (Summary)
5339 @findex gnus-summary-mail-forward
5340 @c @icon{gnus-summary-mail-forward}
5341 Forward the current article to some other person
5342 (@code{gnus-summary-mail-forward}). If given a prefix, include the full
5343 headers of the forwarded article.
5348 @kindex S m (Summary)
5349 @findex gnus-summary-mail-other-window
5350 @c @icon{gnus-summary-mail-originate}
5351 Prepare a mail (@code{gnus-summary-mail-other-window}). By default, use
5352 the posting style of the current group. If given a prefix, disable that.
5353 If the prefix is 1, prompt for a group name to find the posting style.
5358 @kindex S i (Summary)
5359 @findex gnus-summary-news-other-window
5360 Prepare a news (@code{gnus-summary-news-other-window}). By default,
5361 post to the current group. If given a prefix, disable that. If the
5362 prefix is 1, prompt for a group to post to.
5364 This function actually prepares a news even when using mail groups.
5365 This is useful for ``posting'' messages to mail groups without actually
5366 sending them over the network: they're just saved directly to the group
5367 in question. The corresponding back end must have a request-post method
5368 for this to work though.
5371 @kindex S D b (Summary)
5372 @findex gnus-summary-resend-bounced-mail
5373 @cindex bouncing mail
5374 If you have sent a mail, but the mail was bounced back to you for some
5375 reason (wrong address, transient failure), you can use this command to
5376 resend that bounced mail (@code{gnus-summary-resend-bounced-mail}). You
5377 will be popped into a mail buffer where you can edit the headers before
5378 sending the mail off again. If you give a prefix to this command, and
5379 the bounced mail is a reply to some other mail, gnus will try to fetch
5380 that mail and display it for easy perusal of its headers. This might
5381 very well fail, though.
5384 @kindex S D r (Summary)
5385 @findex gnus-summary-resend-message
5386 Not to be confused with the previous command,
5387 @code{gnus-summary-resend-message} will prompt you for an address to
5388 send the current message off to, and then send it to that place. The
5389 headers of the message won't be altered---but lots of headers that say
5390 @code{Resent-To}, @code{Resent-From} and so on will be added. This
5391 means that you actually send a mail to someone that has a @code{To}
5392 header that (probably) points to yourself. This will confuse people.
5393 So, natcherly you'll only do that if you're really eVIl.
5395 This command is mainly used if you have several accounts and want to
5396 ship a mail to a different account of yours. (If you're both
5397 @code{root} and @code{postmaster} and get a mail for @code{postmaster}
5398 to the @code{root} account, you may want to resend it to
5399 @code{postmaster}. Ordnung muss sein!
5401 This command understands the process/prefix convention
5402 (@pxref{Process/Prefix}).
5405 @kindex S D e (Summary)
5406 @findex gnus-summary-resend-message-edit
5408 Like the previous command, but will allow you to edit the message as
5409 if it were a new message before resending.
5412 @kindex S O m (Summary)
5413 @findex gnus-summary-digest-mail-forward
5414 Digest the current series (@pxref{Decoding Articles}) and forward the
5415 result using mail (@code{gnus-summary-digest-mail-forward}). This
5416 command uses the process/prefix convention (@pxref{Process/Prefix}).
5419 @kindex S M-c (Summary)
5420 @findex gnus-summary-mail-crosspost-complaint
5421 @cindex crossposting
5422 @cindex excessive crossposting
5423 Send a complaint about excessive crossposting to the author of the
5424 current article (@code{gnus-summary-mail-crosspost-complaint}).
5426 @findex gnus-crosspost-complaint
5427 This command is provided as a way to fight back against the current
5428 crossposting pandemic that's sweeping Usenet. It will compose a reply
5429 using the @code{gnus-crosspost-complaint} variable as a preamble. This
5430 command understands the process/prefix convention
5431 (@pxref{Process/Prefix}) and will prompt you before sending each mail.
5435 Also @xref{Header Commands, ,Header Commands, message, The Message
5436 Manual}, for more information.
5439 @node Summary Post Commands
5440 @subsection Summary Post Commands
5442 @cindex composing news
5444 Commands for posting a news article:
5450 @kindex S p (Summary)
5451 @findex gnus-summary-post-news
5452 @c @icon{gnus-summary-post-news}
5453 Prepare for posting an article (@code{gnus-summary-post-news}). By
5454 default, post to the current group. If given a prefix, disable that.
5455 If the prefix is 1, prompt for another group instead.
5460 @kindex S f (Summary)
5461 @findex gnus-summary-followup
5462 @c @icon{gnus-summary-followup}
5463 Post a followup to the current article (@code{gnus-summary-followup}).
5467 @kindex S F (Summary)
5469 @c @icon{gnus-summary-followup-with-original}
5470 @findex gnus-summary-followup-with-original
5471 Post a followup to the current article and include the original message
5472 (@code{gnus-summary-followup-with-original}). This command uses the
5473 process/prefix convention.
5476 @kindex S n (Summary)
5477 @findex gnus-summary-followup-to-mail
5478 Post a followup to the current article via news, even if you got the
5479 message through mail (@code{gnus-summary-followup-to-mail}).
5482 @kindex S N (Summary)
5483 @findex gnus-summary-followup-to-mail-with-original
5484 Post a followup to the current article via news, even if you got the
5485 message through mail and include the original message
5486 (@code{gnus-summary-followup-to-mail-with-original}). This command uses
5487 the process/prefix convention.
5490 @kindex S o p (Summary)
5491 @findex gnus-summary-post-forward
5492 Forward the current article to a newsgroup
5493 (@code{gnus-summary-post-forward}). If given a prefix, include the full
5494 headers of the forwarded article.
5497 @kindex S O p (Summary)
5498 @findex gnus-summary-digest-post-forward
5500 @cindex making digests
5501 Digest the current series and forward the result to a newsgroup
5502 (@code{gnus-summary-digest-post-forward}). This command uses the
5503 process/prefix convention.
5506 @kindex S u (Summary)
5507 @findex gnus-uu-post-news
5508 @c @icon{gnus-uu-post-news}
5509 Uuencode a file, split it into parts, and post it as a series
5510 (@code{gnus-uu-post-news}). (@pxref{Uuencoding and Posting}).
5513 Also @xref{Header Commands, ,Header Commands, message, The Message
5514 Manual}, for more information.
5517 @node Summary Message Commands
5518 @subsection Summary Message Commands
5522 @kindex S y (Summary)
5523 @findex gnus-summary-yank-message
5524 Yank the current article into an already existing Message composition
5525 buffer (@code{gnus-summary-yank-message}). This command prompts for
5526 what message buffer you want to yank into, and understands the
5527 process/prefix convention (@pxref{Process/Prefix}).
5532 @node Canceling and Superseding
5533 @subsection Canceling Articles
5534 @cindex canceling articles
5535 @cindex superseding articles
5537 Have you ever written something, and then decided that you really,
5538 really, really wish you hadn't posted that?
5540 Well, you can't cancel mail, but you can cancel posts.
5542 @findex gnus-summary-cancel-article
5544 @c @icon{gnus-summary-cancel-article}
5545 Find the article you wish to cancel (you can only cancel your own
5546 articles, so don't try any funny stuff). Then press @kbd{C} or @kbd{S
5547 c} (@code{gnus-summary-cancel-article}). Your article will be
5548 canceled---machines all over the world will be deleting your article.
5549 This command uses the process/prefix convention (@pxref{Process/Prefix}).
5551 Be aware, however, that not all sites honor cancels, so your article may
5552 live on here and there, while most sites will delete the article in
5555 Gnus will use the ``current'' select method when canceling. If you
5556 want to use the standard posting method, use the @samp{a} symbolic
5557 prefix (@pxref{Symbolic Prefixes}).
5559 Gnus ensures that only you can cancel your own messages using a
5560 @code{Cancel-Lock} header (@pxref{Canceling News, Canceling News, ,
5561 message, Message Manual}).
5563 If you discover that you have made some mistakes and want to do some
5564 corrections, you can post a @dfn{superseding} article that will replace
5565 your original article.
5567 @findex gnus-summary-supersede-article
5569 Go to the original article and press @kbd{S s}
5570 (@code{gnus-summary-supersede-article}). You will be put in a buffer
5571 where you can edit the article all you want before sending it off the
5574 The same goes for superseding as for canceling, only more so: Some
5575 sites do not honor superseding. On those sites, it will appear that you
5576 have posted almost the same article twice.
5578 If you have just posted the article, and change your mind right away,
5579 there is a trick you can use to cancel/supersede the article without
5580 waiting for the article to appear on your site first. You simply return
5581 to the post buffer (which is called @code{*sent ...*}). There you will
5582 find the article you just posted, with all the headers intact. Change
5583 the @code{Message-ID} header to a @code{Cancel} or @code{Supersedes}
5584 header by substituting one of those words for the word
5585 @code{Message-ID}. Then just press @kbd{C-c C-c} to send the article as
5586 you would do normally. The previous article will be
5587 canceled/superseded.
5589 Just remember, kids: There is no 'c' in 'supersede'.
5591 @node Delayed Articles
5592 @section Delayed Articles
5593 @cindex delayed sending
5594 @cindex send delayed
5596 Sometimes, you might wish to delay the sending of a message. For
5597 example, you might wish to arrange for a message to turn up just in time
5598 to remind your about the birthday of your Significant Other. For this,
5599 there is the @code{gnus-delay} package. Setup is simple:
5602 (gnus-delay-initialize)
5605 @findex gnus-delay-article
5606 Normally, to send a message you use the @kbd{C-c C-c} command from
5607 Message mode. To delay a message, use @kbd{C-c C-j}
5608 (@code{gnus-delay-article}) instead. This will ask you for how long the
5609 message should be delayed. Possible answers are:
5613 A time span. Consists of an integer and a letter. For example,
5614 @code{42d} means to delay for 42 days. Available letters are @code{m}
5615 (minutes), @code{h} (hours), @code{d} (days), @code{w} (weeks), @code{M}
5616 (months) and @code{Y} (years).
5619 A specific date. Looks like @code{YYYY-MM-DD}. The message will be
5620 delayed until that day, at a specific time (eight o'clock by default).
5621 See also @code{gnus-delay-default-hour}.
5624 A specific time of day. Given in @code{hh:mm} format, 24h, no am/pm
5625 stuff. The deadline will be at that time today, except if that time has
5626 already passed, then it's at the given time tomorrow. So if it's ten
5627 o'clock in the morning and you specify @code{11:15}, then the deadline
5628 is one hour and fifteen minutes hence. But if you specify @code{9:20},
5629 that means a time tomorrow.
5632 The action of the @code{gnus-delay-article} command is influenced by a
5633 couple of variables:
5636 @item gnus-delay-default-hour
5637 @vindex gnus-delay-default-hour
5638 When you specify a specific date, the message will be due on that hour
5639 on the given date. Possible values are integers 0 through 23.
5641 @item gnus-delay-default-delay
5642 @vindex gnus-delay-default-delay
5643 This is a string and gives the default delay. It can be of any of the
5644 formats described above.
5646 @item gnus-delay-group
5647 @vindex gnus-delay-group
5648 Delayed articles will be kept in this group on the drafts server until
5649 they are due. You probably don't need to change this. The default
5650 value is @code{"delayed"}.
5652 @item gnus-delay-header
5653 @vindex gnus-delay-header
5654 The deadline for each article will be stored in a header. This variable
5655 is a string and gives the header name. You probably don't need to
5656 change this. The default value is @code{"X-Gnus-Delayed"}.
5659 The way delaying works is like this: when you use the
5660 @code{gnus-delay-article} command, you give a certain delay. Gnus
5661 calculates the deadline of the message and stores it in the
5662 @code{X-Gnus-Delayed} header and puts the message in the
5663 @code{nndraft:delayed} group.
5665 @findex gnus-delay-send-queue
5666 And whenever you get new news, Gnus looks through the group for articles
5667 which are due and sends them. It uses the @code{gnus-delay-send-queue}
5668 function for this. By default, this function is added to the hook
5669 @code{gnus-get-new-news-hook}. But of course, you can change this.
5670 Maybe you want to use the demon to send drafts? Just tell the demon to
5671 execute the @code{gnus-delay-send-queue} function.
5674 @item gnus-delay-initialize
5675 @findex gnus-delay-initialize
5677 By default, this function installs @code{gnus-delay-send-queue} in
5678 @code{gnus-get-new-news-hook}. But it accepts the optional second
5679 argument @code{no-check}. If it is non-@code{nil},
5680 @code{gnus-get-new-news-hook} is not changed. The optional first
5681 argument is ignored.
5683 For example, @code{(gnus-delay-initialize nil t)} means to do nothing.
5684 Presumably, you want to use the demon for sending due delayed articles.
5685 Just don't forget to set that up :-)
5689 @node Marking Articles
5690 @section Marking Articles
5691 @cindex article marking
5692 @cindex article ticking
5695 There are several marks you can set on an article.
5697 You have marks that decide the @dfn{readedness} (whoo, neato-keano
5698 neologism ohoy!) of the article. Alphabetic marks generally mean
5699 @dfn{read}, while non-alphabetic characters generally mean @dfn{unread}.
5701 In addition, you also have marks that do not affect readedness.
5704 There's a plethora of commands for manipulating these marks.
5708 * Unread Articles:: Marks for unread articles.
5709 * Read Articles:: Marks for read articles.
5710 * Other Marks:: Marks that do not affect readedness.
5711 * Setting Marks:: How to set and remove marks.
5712 * Generic Marking Commands:: How to customize the marking.
5713 * Setting Process Marks:: How to mark articles for later processing.
5717 @node Unread Articles
5718 @subsection Unread Articles
5720 The following marks mark articles as (kinda) unread, in one form or
5725 @vindex gnus-ticked-mark
5726 Marked as ticked (@code{gnus-ticked-mark}).
5728 @dfn{Ticked articles} are articles that will remain visible always. If
5729 you see an article that you find interesting, or you want to put off
5730 reading it, or replying to it, until sometime later, you'd typically
5731 tick it. However, articles can be expired (from news servers by the
5732 news server software, Gnus itself never expires ticked messages), so if
5733 you want to keep an article forever, you'll have to make it persistent
5734 (@pxref{Persistent Articles}).
5737 @vindex gnus-dormant-mark
5738 Marked as dormant (@code{gnus-dormant-mark}).
5740 @dfn{Dormant articles} will only appear in the summary buffer if there
5741 are followups to it. If you want to see them even if they don't have
5742 followups, you can use the @kbd{/ D} command (@pxref{Limiting}).
5743 Otherwise (except for the visibility issue), they are just like ticked
5747 @vindex gnus-unread-mark
5748 Marked as unread (@code{gnus-unread-mark}).
5750 @dfn{Unread articles} are articles that haven't been read at all yet.
5755 @subsection Read Articles
5756 @cindex expirable mark
5758 All the following marks mark articles as read.
5763 @vindex gnus-del-mark
5764 These are articles that the user has marked as read with the @kbd{d}
5765 command manually, more or less (@code{gnus-del-mark}).
5768 @vindex gnus-read-mark
5769 Articles that have actually been read (@code{gnus-read-mark}).
5772 @vindex gnus-ancient-mark
5773 Articles that were marked as read in previous sessions and are now
5774 @dfn{old} (@code{gnus-ancient-mark}).
5777 @vindex gnus-killed-mark
5778 Marked as killed (@code{gnus-killed-mark}).
5781 @vindex gnus-kill-file-mark
5782 Marked as killed by kill files (@code{gnus-kill-file-mark}).
5785 @vindex gnus-low-score-mark
5786 Marked as read by having too low a score (@code{gnus-low-score-mark}).
5789 @vindex gnus-catchup-mark
5790 Marked as read by a catchup (@code{gnus-catchup-mark}).
5793 @vindex gnus-canceled-mark
5794 Canceled article (@code{gnus-canceled-mark})
5797 @vindex gnus-souped-mark
5798 @sc{soup}ed article (@code{gnus-souped-mark}). @xref{SOUP}.
5801 @vindex gnus-sparse-mark
5802 Sparsely reffed article (@code{gnus-sparse-mark}). @xref{Customizing
5806 @vindex gnus-duplicate-mark
5807 Article marked as read by duplicate suppression
5808 (@code{gnus-duplicate-mark}). @xref{Duplicate Suppression}.
5812 All these marks just mean that the article is marked as read, really.
5813 They are interpreted differently when doing adaptive scoring, though.
5815 One more special mark, though:
5819 @vindex gnus-expirable-mark
5820 Marked as expirable (@code{gnus-expirable-mark}).
5822 Marking articles as @dfn{expirable} (or have them marked as such
5823 automatically) doesn't make much sense in normal groups---a user doesn't
5824 control expiring of news articles, but in mail groups, for instance,
5825 articles marked as @dfn{expirable} can be deleted by gnus at
5831 @subsection Other Marks
5832 @cindex process mark
5835 There are some marks that have nothing to do with whether the article is
5841 You can set a bookmark in the current article. Say you are reading a
5842 long thesis on cats' urinary tracts, and have to go home for dinner
5843 before you've finished reading the thesis. You can then set a bookmark
5844 in the article, and gnus will jump to this bookmark the next time it
5845 encounters the article. @xref{Setting Marks}.
5848 @vindex gnus-replied-mark
5849 All articles that you have replied to or made a followup to (i.e., have
5850 answered) will be marked with an @samp{A} in the second column
5851 (@code{gnus-replied-mark}).
5854 @vindex gnus-forwarded-mark
5855 All articles that you have forwarded will be marked with an @samp{F} in
5856 the second column (@code{gnus-forwarded-mark}).
5859 @vindex gnus-cached-mark
5860 Articles stored in the article cache will be marked with an @samp{*} in
5861 the second column (@code{gnus-cached-mark}). @xref{Article Caching}.
5864 @vindex gnus-saved-mark
5865 Articles ``saved'' (in some manner or other; not necessarily
5866 religiously) are marked with an @samp{S} in the second column
5867 (@code{gnus-saved-mark}).
5870 @vindex gnus-recent-mark
5871 Articles that according to the server haven't been shown to the user
5872 before are marked with a @samp{N} in the second column
5873 (@code{gnus-recent-mark}). Note that not all servers support this
5874 mark, in which case it simply never appears. Compare with
5875 @code{gnus-unseen-mark}.
5878 @vindex gnus-unseen-mark
5879 Articles that haven't been seen before in Gnus by the user are marked
5880 with a @samp{.} in the second column (@code{gnus-unseen-mark}).
5881 Compare with @code{gnus-recent-mark}.
5884 @vindex gnus-downloaded-mark
5885 When using the Gnus agent (@pxref{Agent Basics}), articles may be
5886 downloaded for unplugged (offline) viewing. If you are using the
5887 @samp{%O} spec, these articles get the @samp{+} mark in that spec.
5888 (The variable @code{gnus-downloaded-mark} controls which character to
5892 @vindex gnus-undownloaded-mark
5893 When using the Gnus agent (@pxref{Agent Basics}), some articles might
5894 not have been downloaded. Such articles cannot be viewed while you
5895 are unplugged (offline). If you are using the @samp{%O} spec, these
5896 articles get the @samp{-} mark in that spec. (The variable
5897 @code{gnus-undownloaded-mark} controls which character to use.)
5900 @vindex gnus-downloadable-mark
5901 The Gnus agent (@pxref{Agent Basics}) downloads some articles
5902 automatically, but it is also possible to explicitly mark articles for
5903 download, even if they would not be downloaded automatically. Such
5904 explicitly-marked articles get the @samp{%} mark in the first column.
5905 (The variable @code{gnus-downloadable-mark} controls which character to
5909 @vindex gnus-not-empty-thread-mark
5910 @vindex gnus-empty-thread-mark
5911 If the @samp{%e} spec is used, the presence of threads or not will be
5912 marked with @code{gnus-not-empty-thread-mark} and
5913 @code{gnus-empty-thread-mark} in the third column, respectively.
5916 @vindex gnus-process-mark
5917 Finally we have the @dfn{process mark} (@code{gnus-process-mark}). A
5918 variety of commands react to the presence of the process mark. For
5919 instance, @kbd{X u} (@code{gnus-uu-decode-uu}) will uudecode and view
5920 all articles that have been marked with the process mark. Articles
5921 marked with the process mark have a @samp{#} in the second column.
5925 You might have noticed that most of these ``non-readedness'' marks
5926 appear in the second column by default. So if you have a cached, saved,
5927 replied article that you have process-marked, what will that look like?
5929 Nothing much. The precedence rules go as follows: process -> cache ->
5930 replied -> saved. So if the article is in the cache and is replied,
5931 you'll only see the cache mark and not the replied mark.
5935 @subsection Setting Marks
5936 @cindex setting marks
5938 All the marking commands understand the numeric prefix.
5943 @kindex M c (Summary)
5944 @kindex M-u (Summary)
5945 @findex gnus-summary-clear-mark-forward
5946 @cindex mark as unread
5947 Clear all readedness-marks from the current article
5948 (@code{gnus-summary-clear-mark-forward}). In other words, mark the
5954 @kindex M t (Summary)
5955 @findex gnus-summary-tick-article-forward
5956 Tick the current article (@code{gnus-summary-tick-article-forward}).
5957 @xref{Article Caching}.
5962 @kindex M ? (Summary)
5963 @findex gnus-summary-mark-as-dormant
5964 Mark the current article as dormant
5965 (@code{gnus-summary-mark-as-dormant}). @xref{Article Caching}.
5969 @kindex M d (Summary)
5971 @findex gnus-summary-mark-as-read-forward
5972 Mark the current article as read
5973 (@code{gnus-summary-mark-as-read-forward}).
5977 @findex gnus-summary-mark-as-read-backward
5978 Mark the current article as read and move point to the previous line
5979 (@code{gnus-summary-mark-as-read-backward}).
5984 @kindex M k (Summary)
5985 @findex gnus-summary-kill-same-subject-and-select
5986 Mark all articles that have the same subject as the current one as read,
5987 and then select the next unread article
5988 (@code{gnus-summary-kill-same-subject-and-select}).
5992 @kindex M K (Summary)
5993 @kindex C-k (Summary)
5994 @findex gnus-summary-kill-same-subject
5995 Mark all articles that have the same subject as the current one as read
5996 (@code{gnus-summary-kill-same-subject}).
5999 @kindex M C (Summary)
6000 @findex gnus-summary-catchup
6001 @c @icon{gnus-summary-catchup}
6002 Mark all unread articles as read (@code{gnus-summary-catchup}).
6005 @kindex M C-c (Summary)
6006 @findex gnus-summary-catchup-all
6007 Mark all articles in the group as read---even the ticked and dormant
6008 articles (@code{gnus-summary-catchup-all}).
6011 @kindex M H (Summary)
6012 @findex gnus-summary-catchup-to-here
6013 Catchup the current group to point (before the point)
6014 (@code{gnus-summary-catchup-to-here}).
6017 @kindex M h (Summary)
6018 @findex gnus-summary-catchup-from-here
6019 Catchup the current group from point (after the point)
6020 (@code{gnus-summary-catchup-from-here}).
6023 @kindex C-w (Summary)
6024 @findex gnus-summary-mark-region-as-read
6025 Mark all articles between point and mark as read
6026 (@code{gnus-summary-mark-region-as-read}).
6029 @kindex M V k (Summary)
6030 @findex gnus-summary-kill-below
6031 Kill all articles with scores below the default score (or below the
6032 numeric prefix) (@code{gnus-summary-kill-below}).
6036 @kindex M e (Summary)
6038 @findex gnus-summary-mark-as-expirable
6039 Mark the current article as expirable
6040 (@code{gnus-summary-mark-as-expirable}).
6043 @kindex M b (Summary)
6044 @findex gnus-summary-set-bookmark
6045 Set a bookmark in the current article
6046 (@code{gnus-summary-set-bookmark}).
6049 @kindex M B (Summary)
6050 @findex gnus-summary-remove-bookmark
6051 Remove the bookmark from the current article
6052 (@code{gnus-summary-remove-bookmark}).
6055 @kindex M V c (Summary)
6056 @findex gnus-summary-clear-above
6057 Clear all marks from articles with scores over the default score (or
6058 over the numeric prefix) (@code{gnus-summary-clear-above}).
6061 @kindex M V u (Summary)
6062 @findex gnus-summary-tick-above
6063 Tick all articles with scores over the default score (or over the
6064 numeric prefix) (@code{gnus-summary-tick-above}).
6067 @kindex M V m (Summary)
6068 @findex gnus-summary-mark-above
6069 Prompt for a mark, and mark all articles with scores over the default
6070 score (or over the numeric prefix) with this mark
6071 (@code{gnus-summary-clear-above}).
6074 @vindex gnus-summary-goto-unread
6075 The @code{gnus-summary-goto-unread} variable controls what action should
6076 be taken after setting a mark. If non-@code{nil}, point will move to
6077 the next/previous unread article. If @code{nil}, point will just move
6078 one line up or down. As a special case, if this variable is
6079 @code{never}, all the marking commands as well as other commands (like
6080 @kbd{SPACE}) will move to the next article, whether it is unread or not.
6081 The default is @code{t}.
6084 @node Generic Marking Commands
6085 @subsection Generic Marking Commands
6087 Some people would like the command that ticks an article (@kbd{!}) go to
6088 the next article. Others would like it to go to the next unread
6089 article. Yet others would like it to stay on the current article. And
6090 even though I haven't heard of anybody wanting it to go to the
6091 previous (unread) article, I'm sure there are people that want that as
6094 Multiply these five behaviors with five different marking commands, and
6095 you get a potentially complex set of variable to control what each
6098 To sidestep that mess, Gnus provides commands that do all these
6099 different things. They can be found on the @kbd{M M} map in the summary
6100 buffer. Type @kbd{M M C-h} to see them all---there are too many of them
6101 to list in this manual.
6103 While you can use these commands directly, most users would prefer
6104 altering the summary mode keymap. For instance, if you would like the
6105 @kbd{!} command to go to the next article instead of the next unread
6106 article, you could say something like:
6110 (add-hook 'gnus-summary-mode-hook 'my-alter-summary-map)
6111 (defun my-alter-summary-map ()
6112 (local-set-key "!" 'gnus-summary-put-mark-as-ticked-next))
6120 (defun my-alter-summary-map ()
6121 (local-set-key "!" "MM!n"))
6125 @node Setting Process Marks
6126 @subsection Setting Process Marks
6127 @cindex setting process marks
6129 Process marks are displayed as @code{#} in the summary buffer, and are
6130 used for marking articles in such a way that other commands will
6131 process these articles. For instance, if you process mark four
6132 articles and then use the @kbd{*} command, Gnus will enter these four
6133 commands into the cache. For more information,
6134 @pxref{Process/Prefix}.
6141 @kindex M P p (Summary)
6142 @findex gnus-summary-mark-as-processable
6143 Mark the current article with the process mark
6144 (@code{gnus-summary-mark-as-processable}).
6145 @findex gnus-summary-unmark-as-processable
6149 @kindex M P u (Summary)
6150 @kindex M-# (Summary)
6151 Remove the process mark, if any, from the current article
6152 (@code{gnus-summary-unmark-as-processable}).
6155 @kindex M P U (Summary)
6156 @findex gnus-summary-unmark-all-processable
6157 Remove the process mark from all articles
6158 (@code{gnus-summary-unmark-all-processable}).
6161 @kindex M P i (Summary)
6162 @findex gnus-uu-invert-processable
6163 Invert the list of process marked articles
6164 (@code{gnus-uu-invert-processable}).
6167 @kindex M P R (Summary)
6168 @findex gnus-uu-mark-by-regexp
6169 Mark articles that have a @code{Subject} header that matches a regular
6170 expression (@code{gnus-uu-mark-by-regexp}).
6173 @kindex M P G (Summary)
6174 @findex gnus-uu-unmark-by-regexp
6175 Unmark articles that have a @code{Subject} header that matches a regular
6176 expression (@code{gnus-uu-unmark-by-regexp}).
6179 @kindex M P r (Summary)
6180 @findex gnus-uu-mark-region
6181 Mark articles in region (@code{gnus-uu-mark-region}).
6184 @kindex M P g (Summary)
6185 @findex gnus-uu-unmark-region
6186 Unmark articles in region (@code{gnus-uu-unmark-region}).
6189 @kindex M P t (Summary)
6190 @findex gnus-uu-mark-thread
6191 Mark all articles in the current (sub)thread
6192 (@code{gnus-uu-mark-thread}).
6195 @kindex M P T (Summary)
6196 @findex gnus-uu-unmark-thread
6197 Unmark all articles in the current (sub)thread
6198 (@code{gnus-uu-unmark-thread}).
6201 @kindex M P v (Summary)
6202 @findex gnus-uu-mark-over
6203 Mark all articles that have a score above the prefix argument
6204 (@code{gnus-uu-mark-over}).
6207 @kindex M P s (Summary)
6208 @findex gnus-uu-mark-series
6209 Mark all articles in the current series (@code{gnus-uu-mark-series}).
6212 @kindex M P S (Summary)
6213 @findex gnus-uu-mark-sparse
6214 Mark all series that have already had some articles marked
6215 (@code{gnus-uu-mark-sparse}).
6218 @kindex M P a (Summary)
6219 @findex gnus-uu-mark-all
6220 Mark all articles in series order (@code{gnus-uu-mark-all}).
6223 @kindex M P b (Summary)
6224 @findex gnus-uu-mark-buffer
6225 Mark all articles in the buffer in the order they appear
6226 (@code{gnus-uu-mark-buffer}).
6229 @kindex M P k (Summary)
6230 @findex gnus-summary-kill-process-mark
6231 Push the current process mark set onto the stack and unmark all articles
6232 (@code{gnus-summary-kill-process-mark}).
6235 @kindex M P y (Summary)
6236 @findex gnus-summary-yank-process-mark
6237 Pop the previous process mark set from the stack and restore it
6238 (@code{gnus-summary-yank-process-mark}).
6241 @kindex M P w (Summary)
6242 @findex gnus-summary-save-process-mark
6243 Push the current process mark set onto the stack
6244 (@code{gnus-summary-save-process-mark}).
6248 Also see the @kbd{&} command in @ref{Searching for Articles}, for how to
6249 set process marks based on article body contents.
6256 It can be convenient to limit the summary buffer to just show some
6257 subset of the articles currently in the group. The effect most limit
6258 commands have is to remove a few (or many) articles from the summary
6261 All limiting commands work on subsets of the articles already fetched
6262 from the servers. None of these commands query the server for
6263 additional articles.
6269 @kindex / / (Summary)
6270 @findex gnus-summary-limit-to-subject
6271 Limit the summary buffer to articles that match some subject
6272 (@code{gnus-summary-limit-to-subject}). If given a prefix, exclude
6276 @kindex / a (Summary)
6277 @findex gnus-summary-limit-to-author
6278 Limit the summary buffer to articles that match some author
6279 (@code{gnus-summary-limit-to-author}). If given a prefix, exclude
6283 @kindex / R (Summary)
6284 @findex gnus-summary-limit-to-recipient
6285 Limit the summary buffer to articles that match some recipient
6286 (@code{gnus-summary-limit-to-recipient}). If given a prefix, exclude
6290 @kindex / x (Summary)
6291 @findex gnus-summary-limit-to-extra
6292 Limit the summary buffer to articles that match one of the ``extra''
6293 headers (@pxref{To From Newsgroups})
6294 (@code{gnus-summary-limit-to-extra}). If given a prefix, exclude
6299 @kindex / u (Summary)
6301 @findex gnus-summary-limit-to-unread
6302 Limit the summary buffer to articles not marked as read
6303 (@code{gnus-summary-limit-to-unread}). If given a prefix, limit the
6304 buffer to articles strictly unread. This means that ticked and
6305 dormant articles will also be excluded.
6308 @kindex / m (Summary)
6309 @findex gnus-summary-limit-to-marks
6310 Ask for a mark and then limit to all articles that have been marked
6311 with that mark (@code{gnus-summary-limit-to-marks}).
6314 @kindex / t (Summary)
6315 @findex gnus-summary-limit-to-age
6316 Ask for a number and then limit the summary buffer to articles older than (or equal to) that number of days
6317 (@code{gnus-summary-limit-to-age}). If given a prefix, limit to
6318 articles younger than that number of days.
6321 @kindex / n (Summary)
6322 @findex gnus-summary-limit-to-articles
6323 Limit the summary buffer to the current article
6324 (@code{gnus-summary-limit-to-articles}). Uses the process/prefix
6325 convention (@pxref{Process/Prefix}).
6328 @kindex / w (Summary)
6329 @findex gnus-summary-pop-limit
6330 Pop the previous limit off the stack and restore it
6331 (@code{gnus-summary-pop-limit}). If given a prefix, pop all limits off
6335 @kindex / . (Summary)
6336 @findex gnus-summary-limit-to-unseen
6337 Limit the summary buffer to the unseen articles
6338 (@code{gnus-summary-limit-to-unseen}).
6341 @kindex / v (Summary)
6342 @findex gnus-summary-limit-to-score
6343 Limit the summary buffer to articles that have a score at or above some
6344 score (@code{gnus-summary-limit-to-score}).
6347 @kindex / p (Summary)
6348 @findex gnus-summary-limit-to-display-predicate
6349 Limit the summary buffer to articles that satisfy the @code{display}
6350 group parameter predicate
6351 (@code{gnus-summary-limit-to-display-predicate}). @xref{Group
6352 Parameters}, for more on this predicate.
6355 @kindex / r (Summary)
6356 @findex gnus-summary-limit-to-replied
6357 Limit the summary buffer to replied articles
6358 (@code{gnus-summary-limit-to-replied}). If given a prefix, exclude
6363 @kindex M S (Summary)
6364 @kindex / E (Summary)
6365 @findex gnus-summary-limit-include-expunged
6366 Include all expunged articles in the limit
6367 (@code{gnus-summary-limit-include-expunged}).
6370 @kindex / D (Summary)
6371 @findex gnus-summary-limit-include-dormant
6372 Include all dormant articles in the limit
6373 (@code{gnus-summary-limit-include-dormant}).
6376 @kindex / * (Summary)
6377 @findex gnus-summary-limit-include-cached
6378 Include all cached articles in the limit
6379 (@code{gnus-summary-limit-include-cached}).
6382 @kindex / d (Summary)
6383 @findex gnus-summary-limit-exclude-dormant
6384 Exclude all dormant articles from the limit
6385 (@code{gnus-summary-limit-exclude-dormant}).
6388 @kindex / M (Summary)
6389 @findex gnus-summary-limit-exclude-marks
6390 Exclude all marked articles (@code{gnus-summary-limit-exclude-marks}).
6393 @kindex / T (Summary)
6394 @findex gnus-summary-limit-include-thread
6395 Include all the articles in the current thread in the limit.
6398 @kindex / c (Summary)
6399 @findex gnus-summary-limit-exclude-childless-dormant
6400 Exclude all dormant articles that have no children from the limit@*
6401 (@code{gnus-summary-limit-exclude-childless-dormant}).
6404 @kindex / C (Summary)
6405 @findex gnus-summary-limit-mark-excluded-as-read
6406 Mark all excluded unread articles as read
6407 (@code{gnus-summary-limit-mark-excluded-as-read}). If given a prefix,
6408 also mark excluded ticked and dormant articles as read.
6411 @kindex / N (Summary)
6412 @findex gnus-summary-insert-new-articles
6413 Insert all new articles in the summary buffer. It scans for new emails
6414 if @var{back-end}@code{-get-new-mail} is non-@code{nil}.
6417 @kindex / o (Summary)
6418 @findex gnus-summary-insert-old-articles
6419 Insert all old articles in the summary buffer. If given a numbered
6420 prefix, fetch this number of articles.
6428 @cindex article threading
6430 Gnus threads articles by default. @dfn{To thread} is to put responses
6431 to articles directly after the articles they respond to---in a
6432 hierarchical fashion.
6434 Threading is done by looking at the @code{References} headers of the
6435 articles. In a perfect world, this would be enough to build pretty
6436 trees, but unfortunately, the @code{References} header is often broken
6437 or simply missing. Weird news propagation exacerbates the problem,
6438 so one has to employ other heuristics to get pleasing results. A
6439 plethora of approaches exists, as detailed in horrible detail in
6440 @ref{Customizing Threading}.
6442 First, a quick overview of the concepts:
6446 The top-most article in a thread; the first article in the thread.
6449 A tree-like article structure.
6452 A small(er) section of this tree-like structure.
6455 Threads often lose their roots due to article expiry, or due to the root
6456 already having been read in a previous session, and not displayed in the
6457 summary buffer. We then typically have many sub-threads that really
6458 belong to one thread, but are without connecting roots. These are
6459 called loose threads.
6461 @item thread gathering
6462 An attempt to gather loose threads into bigger threads.
6464 @item sparse threads
6465 A thread where the missing articles have been ``guessed'' at, and are
6466 displayed as empty lines in the summary buffer.
6472 * Customizing Threading:: Variables you can change to affect the threading.
6473 * Thread Commands:: Thread based commands in the summary buffer.
6477 @node Customizing Threading
6478 @subsection Customizing Threading
6479 @cindex customizing threading
6482 * Loose Threads:: How Gnus gathers loose threads into bigger threads.
6483 * Filling In Threads:: Making the threads displayed look fuller.
6484 * More Threading:: Even more variables for fiddling with threads.
6485 * Low-Level Threading:: You thought it was over@dots{} but you were wrong!
6490 @subsubsection Loose Threads
6493 @cindex loose threads
6496 @item gnus-summary-make-false-root
6497 @vindex gnus-summary-make-false-root
6498 If non-@code{nil}, gnus will gather all loose subtrees into one big tree
6499 and create a dummy root at the top. (Wait a minute. Root at the top?
6500 Yup.) Loose subtrees occur when the real root has expired, or you've
6501 read or killed the root in a previous session.
6503 When there is no real root of a thread, gnus will have to fudge
6504 something. This variable says what fudging method gnus should use.
6505 There are four possible values:
6509 \gnusfigure{The Summary Buffer}{390}{
6510 \put(0,0){\epsfig{figure=ps/summary-adopt,width=7.5cm}}
6511 \put(445,0){\makebox(0,0)[br]{\epsfig{figure=ps/summary-empty,width=7.5cm}}}
6512 \put(0,400){\makebox(0,0)[tl]{\epsfig{figure=ps/summary-none,width=7.5cm}}}
6513 \put(445,400){\makebox(0,0)[tr]{\epsfig{figure=ps/summary-dummy,width=7.5cm}}}
6518 @cindex adopting articles
6523 Gnus will make the first of the orphaned articles the parent. This
6524 parent will adopt all the other articles. The adopted articles will be
6525 marked as such by pointy brackets (@samp{<>}) instead of the standard
6526 square brackets (@samp{[]}). This is the default method.
6529 @vindex gnus-summary-dummy-line-format
6530 @vindex gnus-summary-make-false-root-always
6531 Gnus will create a dummy summary line that will pretend to be the
6532 parent. This dummy line does not correspond to any real article, so
6533 selecting it will just select the first real article after the dummy
6534 article. @code{gnus-summary-dummy-line-format} is used to specify the
6535 format of the dummy roots. It accepts only one format spec: @samp{S},
6536 which is the subject of the article. @xref{Formatting Variables}.
6537 If you want all threads to have a dummy root, even the non-gathered
6538 ones, set @code{gnus-summary-make-false-root-always} to @code{t}.
6541 Gnus won't actually make any article the parent, but simply leave the
6542 subject field of all orphans except the first empty. (Actually, it will
6543 use @code{gnus-summary-same-subject} as the subject (@pxref{Summary
6547 Don't make any article parent at all. Just gather the threads and
6548 display them after one another.
6551 Don't gather loose threads.
6554 @item gnus-summary-gather-subject-limit
6555 @vindex gnus-summary-gather-subject-limit
6556 Loose threads are gathered by comparing subjects of articles. If this
6557 variable is @code{nil}, gnus requires an exact match between the
6558 subjects of the loose threads before gathering them into one big
6559 super-thread. This might be too strict a requirement, what with the
6560 presence of stupid newsreaders that chop off long subject lines. If
6561 you think so, set this variable to, say, 20 to require that only the
6562 first 20 characters of the subjects have to match. If you set this
6563 variable to a really low number, you'll find that gnus will gather
6564 everything in sight into one thread, which isn't very helpful.
6566 @cindex fuzzy article gathering
6567 If you set this variable to the special value @code{fuzzy}, gnus will
6568 use a fuzzy string comparison algorithm on the subjects (@pxref{Fuzzy
6571 @item gnus-simplify-subject-fuzzy-regexp
6572 @vindex gnus-simplify-subject-fuzzy-regexp
6573 This can either be a regular expression or list of regular expressions
6574 that match strings that will be removed from subjects if fuzzy subject
6575 simplification is used.
6577 @item gnus-simplify-ignored-prefixes
6578 @vindex gnus-simplify-ignored-prefixes
6579 If you set @code{gnus-summary-gather-subject-limit} to something as low
6580 as 10, you might consider setting this variable to something sensible:
6582 @c Written by Michael Ernst <mernst@cs.rice.edu>
6584 (setq gnus-simplify-ignored-prefixes
6590 "wanted" "followup" "summary\\( of\\)?"
6591 "help" "query" "problem" "question"
6592 "answer" "reference" "announce"
6593 "How can I" "How to" "Comparison of"
6598 (mapconcat 'identity
6599 '("for" "for reference" "with" "about")
6601 "\\)?\\]?:?[ \t]*"))
6604 All words that match this regexp will be removed before comparing two
6607 @item gnus-simplify-subject-functions
6608 @vindex gnus-simplify-subject-functions
6609 If non-@code{nil}, this variable overrides
6610 @code{gnus-summary-gather-subject-limit}. This variable should be a
6611 list of functions to apply to the @code{Subject} string iteratively to
6612 arrive at the simplified version of the string.
6614 Useful functions to put in this list include:
6617 @item gnus-simplify-subject-re
6618 @findex gnus-simplify-subject-re
6619 Strip the leading @samp{Re:}.
6621 @item gnus-simplify-subject-fuzzy
6622 @findex gnus-simplify-subject-fuzzy
6625 @item gnus-simplify-whitespace
6626 @findex gnus-simplify-whitespace
6627 Remove excessive whitespace.
6629 @item gnus-simplify-all-whitespace
6630 @findex gnus-simplify-all-whitespace
6631 Remove all whitespace.
6634 You may also write your own functions, of course.
6637 @item gnus-summary-gather-exclude-subject
6638 @vindex gnus-summary-gather-exclude-subject
6639 Since loose thread gathering is done on subjects only, that might lead
6640 to many false hits, especially with certain common subjects like
6641 @samp{} and @samp{(none)}. To make the situation slightly better,
6642 you can use the regexp @code{gnus-summary-gather-exclude-subject} to say
6643 what subjects should be excluded from the gathering process.@*
6644 The default is @samp{^ *$\\|^(none)$}.
6646 @item gnus-summary-thread-gathering-function
6647 @vindex gnus-summary-thread-gathering-function
6648 Gnus gathers threads by looking at @code{Subject} headers. This means
6649 that totally unrelated articles may end up in the same ``thread'', which
6650 is confusing. An alternate approach is to look at all the
6651 @code{Message-ID}s in all the @code{References} headers to find matches.
6652 This will ensure that no gathered threads ever include unrelated
6653 articles, but it also means that people who have posted with broken
6654 newsreaders won't be gathered properly. The choice is yours---plague or
6658 @item gnus-gather-threads-by-subject
6659 @findex gnus-gather-threads-by-subject
6660 This function is the default gathering function and looks at
6661 @code{Subject}s exclusively.
6663 @item gnus-gather-threads-by-references
6664 @findex gnus-gather-threads-by-references
6665 This function looks at @code{References} headers exclusively.
6668 If you want to test gathering by @code{References}, you could say
6672 (setq gnus-summary-thread-gathering-function
6673 'gnus-gather-threads-by-references)
6679 @node Filling In Threads
6680 @subsubsection Filling In Threads
6683 @item gnus-fetch-old-headers
6684 @vindex gnus-fetch-old-headers
6685 If non-@code{nil}, gnus will attempt to build old threads by fetching
6686 more old headers---headers to articles marked as read. If you would
6687 like to display as few summary lines as possible, but still connect as
6688 many loose threads as possible, you should set this variable to
6689 @code{some} or a number. If you set it to a number, no more than that
6690 number of extra old headers will be fetched. In either case, fetching
6691 old headers only works if the back end you are using carries overview
6692 files---this would normally be @code{nntp}, @code{nnspool},
6693 @code{nnml}, and @code{nnmaildir}. Also remember that if the root of
6694 the thread has been expired by the server, there's not much Gnus can
6697 This variable can also be set to @code{invisible}. This won't have any
6698 visible effects, but is useful if you use the @kbd{A T} command a lot
6699 (@pxref{Finding the Parent}).
6701 @item gnus-fetch-old-ephemeral-headers
6702 @vindex gnus-fetch-old-ephemeral-headers
6703 Same as @code{gnus-fetch-old-headers}, but only used for ephemeral
6706 @item gnus-build-sparse-threads
6707 @vindex gnus-build-sparse-threads
6708 Fetching old headers can be slow. A low-rent similar effect can be
6709 gotten by setting this variable to @code{some}. Gnus will then look at
6710 the complete @code{References} headers of all articles and try to string
6711 together articles that belong in the same thread. This will leave
6712 @dfn{gaps} in the threading display where gnus guesses that an article
6713 is missing from the thread. (These gaps appear like normal summary
6714 lines. If you select a gap, gnus will try to fetch the article in
6715 question.) If this variable is @code{t}, gnus will display all these
6716 ``gaps'' without regard for whether they are useful for completing the
6717 thread or not. Finally, if this variable is @code{more}, gnus won't cut
6718 off sparse leaf nodes that don't lead anywhere. This variable is
6719 @code{nil} by default.
6721 @item gnus-read-all-available-headers
6722 @vindex gnus-read-all-available-headers
6723 This is a rather obscure variable that few will find useful. It's
6724 intended for those non-news newsgroups where the back end has to fetch
6725 quite a lot to present the summary buffer, and where it's impossible to
6726 go back to parents of articles. This is mostly the case in the
6727 web-based groups, like the @code{nnultimate} groups.
6729 If you don't use those, then it's safe to leave this as the default
6730 @code{nil}. If you want to use this variable, it should be a regexp
6731 that matches the group name, or @code{t} for all groups.
6736 @node More Threading
6737 @subsubsection More Threading
6740 @item gnus-show-threads
6741 @vindex gnus-show-threads
6742 If this variable is @code{nil}, no threading will be done, and all of
6743 the rest of the variables here will have no effect. Turning threading
6744 off will speed group selection up a bit, but it is sure to make reading
6745 slower and more awkward.
6747 @item gnus-thread-hide-subtree
6748 @vindex gnus-thread-hide-subtree
6749 If non-@code{nil}, all threads will be hidden when the summary buffer is
6752 This can also be a predicate specifier (@pxref{Predicate Specifiers}).
6753 Available predicates are @code{gnus-article-unread-p} and
6754 @code{gnus-article-unseen-p}.
6759 (setq gnus-thread-hide-subtree
6760 '(or gnus-article-unread-p
6761 gnus-article-unseen-p))
6764 (It's a pretty nonsensical example, since all unseen articles are also
6765 unread, but you get my drift.)
6768 @item gnus-thread-expunge-below
6769 @vindex gnus-thread-expunge-below
6770 All threads that have a total score (as defined by
6771 @code{gnus-thread-score-function}) less than this number will be
6772 expunged. This variable is @code{nil} by default, which means that no
6773 threads are expunged.
6775 @item gnus-thread-hide-killed
6776 @vindex gnus-thread-hide-killed
6777 if you kill a thread and this variable is non-@code{nil}, the subtree
6780 @item gnus-thread-ignore-subject
6781 @vindex gnus-thread-ignore-subject
6782 Sometimes somebody changes the subject in the middle of a thread. If
6783 this variable is non-@code{nil}, which is the default, the subject
6784 change is ignored. If it is @code{nil}, a change in the subject will
6785 result in a new thread.
6787 @item gnus-thread-indent-level
6788 @vindex gnus-thread-indent-level
6789 This is a number that says how much each sub-thread should be indented.
6792 @item gnus-sort-gathered-threads-function
6793 @vindex gnus-sort-gathered-threads-function
6794 Sometimes, particularly with mailing lists, the order in which mails
6795 arrive locally is not necessarily the same as the order in which they
6796 arrived on the mailing list. Consequently, when sorting sub-threads
6797 using the default @code{gnus-thread-sort-by-number}, responses can end
6798 up appearing before the article to which they are responding to.
6799 Setting this variable to an alternate value
6800 (e.g. @code{gnus-thread-sort-by-date}), in a group's parameters or in an
6801 appropriate hook (e.g. @code{gnus-summary-generate-hook}) can produce a
6802 more logical sub-thread ordering in such instances.
6807 @node Low-Level Threading
6808 @subsubsection Low-Level Threading
6812 @item gnus-parse-headers-hook
6813 @vindex gnus-parse-headers-hook
6814 Hook run before parsing any headers. The default value is
6815 @code{(gnus-set-summary-default-charset)}, which sets up local value of
6816 @code{default-mime-charset} in summary buffer based on variable
6817 @code{gnus-newsgroup-default-charset-alist}.
6819 @item gnus-alter-header-function
6820 @vindex gnus-alter-header-function
6821 If non-@code{nil}, this function will be called to allow alteration of
6822 article header structures. The function is called with one parameter,
6823 the article header vector, which it may alter in any way. For instance,
6824 if you have a mail-to-news gateway which alters the @code{Message-ID}s
6825 in systematic ways (by adding prefixes and such), you can use this
6826 variable to un-scramble the @code{Message-ID}s so that they are more
6827 meaningful. Here's one example:
6830 (setq gnus-alter-header-function 'my-alter-message-id)
6832 (defun my-alter-message-id (header)
6833 (let ((id (mail-header-id header)))
6835 "\\(<[^<>@@]*\\)\\.?cygnus\\..*@@\\([^<>@@]*>\\)" id)
6837 (concat (match-string 1 id) "@@" (match-string 2 id))
6844 @node Thread Commands
6845 @subsection Thread Commands
6846 @cindex thread commands
6852 @kindex T k (Summary)
6853 @kindex C-M-k (Summary)
6854 @findex gnus-summary-kill-thread
6855 Mark all articles in the current (sub-)thread as read
6856 (@code{gnus-summary-kill-thread}). If the prefix argument is positive,
6857 remove all marks instead. If the prefix argument is negative, tick
6862 @kindex T l (Summary)
6863 @kindex C-M-l (Summary)
6864 @findex gnus-summary-lower-thread
6865 Lower the score of the current (sub-)thread
6866 (@code{gnus-summary-lower-thread}).
6869 @kindex T i (Summary)
6870 @findex gnus-summary-raise-thread
6871 Increase the score of the current (sub-)thread
6872 (@code{gnus-summary-raise-thread}).
6875 @kindex T # (Summary)
6876 @findex gnus-uu-mark-thread
6877 Set the process mark on the current (sub-)thread
6878 (@code{gnus-uu-mark-thread}).
6881 @kindex T M-# (Summary)
6882 @findex gnus-uu-unmark-thread
6883 Remove the process mark from the current (sub-)thread
6884 (@code{gnus-uu-unmark-thread}).
6887 @kindex T T (Summary)
6888 @findex gnus-summary-toggle-threads
6889 Toggle threading (@code{gnus-summary-toggle-threads}).
6892 @kindex T s (Summary)
6893 @findex gnus-summary-show-thread
6894 Expose the (sub-)thread hidden under the current article, if any@*
6895 (@code{gnus-summary-show-thread}).
6898 @kindex T h (Summary)
6899 @findex gnus-summary-hide-thread
6900 Hide the current (sub-)thread (@code{gnus-summary-hide-thread}).
6903 @kindex T S (Summary)
6904 @findex gnus-summary-show-all-threads
6905 Expose all hidden threads (@code{gnus-summary-show-all-threads}).
6908 @kindex T H (Summary)
6909 @findex gnus-summary-hide-all-threads
6910 Hide all threads (@code{gnus-summary-hide-all-threads}).
6913 @kindex T t (Summary)
6914 @findex gnus-summary-rethread-current
6915 Re-thread the current article's thread
6916 (@code{gnus-summary-rethread-current}). This works even when the
6917 summary buffer is otherwise unthreaded.
6920 @kindex T ^ (Summary)
6921 @findex gnus-summary-reparent-thread
6922 Make the current article the child of the marked (or previous) article
6923 (@code{gnus-summary-reparent-thread}).
6927 The following commands are thread movement commands. They all
6928 understand the numeric prefix.
6933 @kindex T n (Summary)
6935 @kindex C-M-n (Summary)
6937 @kindex M-down (Summary)
6938 @findex gnus-summary-next-thread
6939 Go to the next thread (@code{gnus-summary-next-thread}).
6942 @kindex T p (Summary)
6944 @kindex C-M-p (Summary)
6946 @kindex M-up (Summary)
6947 @findex gnus-summary-prev-thread
6948 Go to the previous thread (@code{gnus-summary-prev-thread}).
6951 @kindex T d (Summary)
6952 @findex gnus-summary-down-thread
6953 Descend the thread (@code{gnus-summary-down-thread}).
6956 @kindex T u (Summary)
6957 @findex gnus-summary-up-thread
6958 Ascend the thread (@code{gnus-summary-up-thread}).
6961 @kindex T o (Summary)
6962 @findex gnus-summary-top-thread
6963 Go to the top of the thread (@code{gnus-summary-top-thread}).
6966 @vindex gnus-thread-operation-ignore-subject
6967 If you ignore subject while threading, you'll naturally end up with
6968 threads that have several different subjects in them. If you then issue
6969 a command like @kbd{T k} (@code{gnus-summary-kill-thread}) you might not
6970 wish to kill the entire thread, but just those parts of the thread that
6971 have the same subject as the current article. If you like this idea,
6972 you can fiddle with @code{gnus-thread-operation-ignore-subject}. If it
6973 is non-@code{nil} (which it is by default), subjects will be ignored
6974 when doing thread commands. If this variable is @code{nil}, articles in
6975 the same thread with different subjects will not be included in the
6976 operation in question. If this variable is @code{fuzzy}, only articles
6977 that have subjects fuzzily equal will be included (@pxref{Fuzzy
6981 @node Sorting the Summary Buffer
6982 @section Sorting the Summary Buffer
6984 @findex gnus-thread-sort-by-total-score
6985 @findex gnus-thread-sort-by-date
6986 @findex gnus-thread-sort-by-score
6987 @findex gnus-thread-sort-by-subject
6988 @findex gnus-thread-sort-by-author
6989 @c @findex gnus-thread-sort-by-recipient
6990 @findex gnus-thread-sort-by-number
6991 @findex gnus-thread-sort-by-random
6992 @vindex gnus-thread-sort-functions
6993 @findex gnus-thread-sort-by-most-recent-number
6994 @findex gnus-thread-sort-by-most-recent-date
6995 If you are using a threaded summary display, you can sort the threads by
6996 setting @code{gnus-thread-sort-functions}, which can be either a single
6997 function, a list of functions, or a list containing functions and
6998 @code{(not some-function)} elements.
7000 By default, sorting is done on article numbers. Ready-made sorting
7001 predicate functions include @code{gnus-thread-sort-by-number},
7002 @code{gnus-thread-sort-by-author}, @code{gnus-thread-sort-by-subject},
7003 @code{gnus-thread-sort-by-date}, @code{gnus-thread-sort-by-score},
7004 @code{gnus-thread-sort-by-most-recent-number},
7005 @code{gnus-thread-sort-by-most-recent-date},
7006 @code{gnus-thread-sort-by-random} and
7007 @code{gnus-thread-sort-by-total-score}.
7009 Each function takes two threads and returns non-@code{nil} if the first
7010 thread should be sorted before the other. Note that sorting really is
7011 normally done by looking only at the roots of each thread.
7013 If you use more than one function, the primary sort key should be the
7014 last function in the list. You should probably always include
7015 @code{gnus-thread-sort-by-number} in the list of sorting
7016 functions---preferably first. This will ensure that threads that are
7017 equal with respect to the other sort criteria will be displayed in
7018 ascending article order.
7020 If you would like to sort by reverse score, then by subject, and finally
7021 by number, you could do something like:
7024 (setq gnus-thread-sort-functions
7025 '(gnus-thread-sort-by-number
7026 gnus-thread-sort-by-subject
7027 (not gnus-thread-sort-by-total-score)))
7030 The threads that have highest score will be displayed first in the
7031 summary buffer. When threads have the same score, they will be sorted
7032 alphabetically. The threads that have the same score and the same
7033 subject will be sorted by number, which is (normally) the sequence in
7034 which the articles arrived.
7036 If you want to sort by score and then reverse arrival order, you could
7040 (setq gnus-thread-sort-functions
7042 (not (gnus-thread-sort-by-number t1 t2)))
7043 gnus-thread-sort-by-score))
7046 @vindex gnus-thread-score-function
7047 The function in the @code{gnus-thread-score-function} variable (default
7048 @code{+}) is used for calculating the total score of a thread. Useful
7049 functions might be @code{max}, @code{min}, or squared means, or whatever
7052 @findex gnus-article-sort-functions
7053 @findex gnus-article-sort-by-date
7054 @findex gnus-article-sort-by-score
7055 @findex gnus-article-sort-by-subject
7056 @findex gnus-article-sort-by-author
7057 @findex gnus-article-sort-by-random
7058 @findex gnus-article-sort-by-number
7059 If you are using an unthreaded display for some strange reason or
7060 other, you have to fiddle with the @code{gnus-article-sort-functions}
7061 variable. It is very similar to the
7062 @code{gnus-thread-sort-functions}, except that it uses slightly
7063 different functions for article comparison. Available sorting
7064 predicate functions are @code{gnus-article-sort-by-number},
7065 @code{gnus-article-sort-by-author},
7066 @code{gnus-article-sort-by-subject}, @code{gnus-article-sort-by-date},
7067 @code{gnus-article-sort-by-random}, and
7068 @code{gnus-article-sort-by-score}.
7070 If you want to sort an unthreaded summary display by subject, you could
7074 (setq gnus-article-sort-functions
7075 '(gnus-article-sort-by-number
7076 gnus-article-sort-by-subject))
7081 @node Asynchronous Fetching
7082 @section Asynchronous Article Fetching
7083 @cindex asynchronous article fetching
7084 @cindex article pre-fetch
7087 If you read your news from an @acronym{NNTP} server that's far away, the
7088 network latencies may make reading articles a chore. You have to wait
7089 for a while after pressing @kbd{n} to go to the next article before the
7090 article appears. Why can't gnus just go ahead and fetch the article
7091 while you are reading the previous one? Why not, indeed.
7093 First, some caveats. There are some pitfalls to using asynchronous
7094 article fetching, especially the way gnus does it.
7096 Let's say you are reading article 1, which is short, and article 2 is
7097 quite long, and you are not interested in reading that. Gnus does not
7098 know this, so it goes ahead and fetches article 2. You decide to read
7099 article 3, but since gnus is in the process of fetching article 2, the
7100 connection is blocked.
7102 To avoid these situations, gnus will open two (count 'em two)
7103 connections to the server. Some people may think this isn't a very nice
7104 thing to do, but I don't see any real alternatives. Setting up that
7105 extra connection takes some time, so gnus startup will be slower.
7107 Gnus will fetch more articles than you will read. This will mean that
7108 the link between your machine and the @acronym{NNTP} server will become more
7109 loaded than if you didn't use article pre-fetch. The server itself will
7110 also become more loaded---both with the extra article requests, and the
7113 Ok, so now you know that you shouldn't really use this thing@dots{} unless
7116 @vindex gnus-asynchronous
7117 Here's how: Set @code{gnus-asynchronous} to @code{t}. The rest should
7118 happen automatically.
7120 @vindex gnus-use-article-prefetch
7121 You can control how many articles are to be pre-fetched by setting
7122 @code{gnus-use-article-prefetch}. This is 30 by default, which means
7123 that when you read an article in the group, the back end will pre-fetch
7124 the next 30 articles. If this variable is @code{t}, the back end will
7125 pre-fetch all the articles it can without bound. If it is
7126 @code{nil}, no pre-fetching will be done.
7128 @vindex gnus-async-prefetch-article-p
7129 @findex gnus-async-read-p
7130 There are probably some articles that you don't want to pre-fetch---read
7131 articles, for instance. The @code{gnus-async-prefetch-article-p}
7132 variable controls whether an article is to be pre-fetched. This
7133 function should return non-@code{nil} when the article in question is
7134 to be pre-fetched. The default is @code{gnus-async-read-p}, which
7135 returns @code{nil} on read articles. The function is called with an
7136 article data structure as the only parameter.
7138 If, for instance, you wish to pre-fetch only unread articles shorter
7139 than 100 lines, you could say something like:
7142 (defun my-async-short-unread-p (data)
7143 "Return non-nil for short, unread articles."
7144 (and (gnus-data-unread-p data)
7145 (< (mail-header-lines (gnus-data-header data))
7148 (setq gnus-async-prefetch-article-p 'my-async-short-unread-p)
7151 These functions will be called many, many times, so they should
7152 preferably be short and sweet to avoid slowing down gnus too much.
7153 It's probably a good idea to byte-compile things like this.
7155 @vindex gnus-prefetched-article-deletion-strategy
7156 Articles have to be removed from the asynch buffer sooner or later. The
7157 @code{gnus-prefetched-article-deletion-strategy} says when to remove
7158 articles. This is a list that may contain the following elements:
7162 Remove articles when they are read.
7165 Remove articles when exiting the group.
7168 The default value is @code{(read exit)}.
7170 @c @vindex gnus-use-header-prefetch
7171 @c If @code{gnus-use-header-prefetch} is non-@code{nil}, prefetch articles
7172 @c from the next group.
7175 @node Article Caching
7176 @section Article Caching
7177 @cindex article caching
7180 If you have an @emph{extremely} slow @acronym{NNTP} connection, you may
7181 consider turning article caching on. Each article will then be stored
7182 locally under your home directory. As you may surmise, this could
7183 potentially use @emph{huge} amounts of disk space, as well as eat up all
7184 your inodes so fast it will make your head swim. In vodka.
7186 Used carefully, though, it could be just an easier way to save articles.
7188 @vindex gnus-use-long-file-name
7189 @vindex gnus-cache-directory
7190 @vindex gnus-use-cache
7191 To turn caching on, set @code{gnus-use-cache} to @code{t}. By default,
7192 all articles ticked or marked as dormant will then be copied
7193 over to your local cache (@code{gnus-cache-directory}). Whether this
7194 cache is flat or hierarchical is controlled by the
7195 @code{gnus-use-long-file-name} variable, as usual.
7197 When re-selecting a ticked or dormant article, it will be fetched from the
7198 cache instead of from the server. As articles in your cache will never
7199 expire, this might serve as a method of saving articles while still
7200 keeping them where they belong. Just mark all articles you want to save
7201 as dormant, and don't worry.
7203 When an article is marked as read, is it removed from the cache.
7205 @vindex gnus-cache-remove-articles
7206 @vindex gnus-cache-enter-articles
7207 The entering/removal of articles from the cache is controlled by the
7208 @code{gnus-cache-enter-articles} and @code{gnus-cache-remove-articles}
7209 variables. Both are lists of symbols. The first is @code{(ticked
7210 dormant)} by default, meaning that ticked and dormant articles will be
7211 put in the cache. The latter is @code{(read)} by default, meaning that
7212 articles marked as read are removed from the cache. Possibly
7213 symbols in these two lists are @code{ticked}, @code{dormant},
7214 @code{unread} and @code{read}.
7216 @findex gnus-jog-cache
7217 So where does the massive article-fetching and storing come into the
7218 picture? The @code{gnus-jog-cache} command will go through all
7219 subscribed newsgroups, request all unread articles, score them, and
7220 store them in the cache. You should only ever, ever ever ever, use this
7221 command if 1) your connection to the @acronym{NNTP} server is really, really,
7222 really slow and 2) you have a really, really, really huge disk.
7223 Seriously. One way to cut down on the number of articles downloaded is
7224 to score unwanted articles down and have them marked as read. They will
7225 not then be downloaded by this command.
7227 @vindex gnus-uncacheable-groups
7228 @vindex gnus-cacheable-groups
7229 It is likely that you do not want caching on all groups. For instance,
7230 if your @code{nnml} mail is located under your home directory, it makes no
7231 sense to cache it somewhere else under your home directory. Unless you
7232 feel that it's neat to use twice as much space.
7234 To limit the caching, you could set @code{gnus-cacheable-groups} to a
7235 regexp of groups to cache, @samp{^nntp} for instance, or set the
7236 @code{gnus-uncacheable-groups} regexp to @samp{^nnml}, for instance.
7237 Both variables are @code{nil} by default. If a group matches both
7238 variables, the group is not cached.
7240 @findex gnus-cache-generate-nov-databases
7241 @findex gnus-cache-generate-active
7242 @vindex gnus-cache-active-file
7243 The cache stores information on what articles it contains in its active
7244 file (@code{gnus-cache-active-file}). If this file (or any other parts
7245 of the cache) becomes all messed up for some reason or other, gnus
7246 offers two functions that will try to set things right. @kbd{M-x
7247 gnus-cache-generate-nov-databases} will (re)build all the @acronym{NOV}
7248 files, and @kbd{gnus-cache-generate-active} will (re)generate the active
7251 @findex gnus-cache-move-cache
7252 @code{gnus-cache-move-cache} will move your whole
7253 @code{gnus-cache-directory} to some other location. You get asked to
7254 where, isn't that cool?
7256 @node Persistent Articles
7257 @section Persistent Articles
7258 @cindex persistent articles
7260 Closely related to article caching, we have @dfn{persistent articles}.
7261 In fact, it's just a different way of looking at caching, and much more
7262 useful in my opinion.
7264 Say you're reading a newsgroup, and you happen on to some valuable gem
7265 that you want to keep and treasure forever. You'd normally just save it
7266 (using one of the many saving commands) in some file. The problem with
7267 that is that it's just, well, yucky. Ideally you'd prefer just having
7268 the article remain in the group where you found it forever; untouched by
7269 the expiry going on at the news server.
7271 This is what a @dfn{persistent article} is---an article that just won't
7272 be deleted. It's implemented using the normal cache functions, but
7273 you use two explicit commands for managing persistent articles:
7279 @findex gnus-cache-enter-article
7280 Make the current article persistent (@code{gnus-cache-enter-article}).
7283 @kindex M-* (Summary)
7284 @findex gnus-cache-remove-article
7285 Remove the current article from the persistent articles
7286 (@code{gnus-cache-remove-article}). This will normally delete the
7290 Both these commands understand the process/prefix convention.
7292 To avoid having all ticked articles (and stuff) entered into the cache,
7293 you should set @code{gnus-use-cache} to @code{passive} if you're just
7294 interested in persistent articles:
7297 (setq gnus-use-cache 'passive)
7301 @node Article Backlog
7302 @section Article Backlog
7304 @cindex article backlog
7306 If you have a slow connection, but the idea of using caching seems
7307 unappealing to you (and it is, really), you can help the situation some
7308 by switching on the @dfn{backlog}. This is where gnus will buffer
7309 already read articles so that it doesn't have to re-fetch articles
7310 you've already read. This only helps if you are in the habit of
7311 re-selecting articles you've recently read, of course. If you never do
7312 that, turning the backlog on will slow gnus down a little bit, and
7313 increase memory usage some.
7315 @vindex gnus-keep-backlog
7316 If you set @code{gnus-keep-backlog} to a number @var{n}, gnus will store
7317 at most @var{n} old articles in a buffer for later re-fetching. If this
7318 variable is non-@code{nil} and is not a number, gnus will store
7319 @emph{all} read articles, which means that your Emacs will grow without
7320 bound before exploding and taking your machine down with you. I put
7321 that in there just to keep y'all on your toes.
7323 The default value is 20.
7326 @node Saving Articles
7327 @section Saving Articles
7328 @cindex saving articles
7330 Gnus can save articles in a number of ways. Below is the documentation
7331 for saving articles in a fairly straight-forward fashion (i.e., little
7332 processing of the article is done before it is saved). For a different
7333 approach (uudecoding, unsharing) you should use @code{gnus-uu}
7334 (@pxref{Decoding Articles}).
7336 For the commands listed here, the target is a file. If you want to
7337 save to a group, see the @kbd{B c} (@code{gnus-summary-copy-article})
7338 command (@pxref{Mail Group Commands}).
7340 @vindex gnus-save-all-headers
7341 If @code{gnus-save-all-headers} is non-@code{nil}, gnus will not delete
7342 unwanted headers before saving the article.
7344 @vindex gnus-saved-headers
7345 If the preceding variable is @code{nil}, all headers that match the
7346 @code{gnus-saved-headers} regexp will be kept, while the rest will be
7347 deleted before saving.
7353 @kindex O o (Summary)
7355 @findex gnus-summary-save-article
7356 @c @icon{gnus-summary-save-article}
7357 Save the current article using the default article saver
7358 (@code{gnus-summary-save-article}).
7361 @kindex O m (Summary)
7362 @findex gnus-summary-save-article-mail
7363 Save the current article in mail format
7364 (@code{gnus-summary-save-article-mail}).
7367 @kindex O r (Summary)
7368 @findex gnus-summary-save-article-rmail
7369 Save the current article in Rmail format
7370 (@code{gnus-summary-save-article-rmail}).
7373 @kindex O f (Summary)
7374 @findex gnus-summary-save-article-file
7375 @c @icon{gnus-summary-save-article-file}
7376 Save the current article in plain file format
7377 (@code{gnus-summary-save-article-file}).
7380 @kindex O F (Summary)
7381 @findex gnus-summary-write-article-file
7382 Write the current article in plain file format, overwriting any previous
7383 file contents (@code{gnus-summary-write-article-file}).
7386 @kindex O b (Summary)
7387 @findex gnus-summary-save-article-body-file
7388 Save the current article body in plain file format
7389 (@code{gnus-summary-save-article-body-file}).
7392 @kindex O h (Summary)
7393 @findex gnus-summary-save-article-folder
7394 Save the current article in mh folder format
7395 (@code{gnus-summary-save-article-folder}).
7398 @kindex O v (Summary)
7399 @findex gnus-summary-save-article-vm
7400 Save the current article in a VM folder
7401 (@code{gnus-summary-save-article-vm}).
7405 @kindex O p (Summary)
7407 @findex gnus-summary-pipe-output
7408 Save the current article in a pipe. Uhm, like, what I mean is---Pipe
7409 the current article to a process (@code{gnus-summary-pipe-output}).
7410 If given a symbolic prefix (@pxref{Symbolic Prefixes}), include the
7411 complete headers in the piped output.
7414 @kindex O P (Summary)
7415 @findex gnus-summary-muttprint
7416 @vindex gnus-summary-muttprint-program
7417 Save the current article into muttprint. That is, print it using the
7418 external program @uref{http://muttprint.sourceforge.net/,
7419 Muttprint}. The program name and options to use is controlled by the
7420 variable @code{gnus-summary-muttprint-program}.
7421 (@code{gnus-summary-muttprint}).
7425 @vindex gnus-prompt-before-saving
7426 All these commands use the process/prefix convention
7427 (@pxref{Process/Prefix}). If you save bunches of articles using these
7428 functions, you might get tired of being prompted for files to save each
7429 and every article in. The prompting action is controlled by
7430 the @code{gnus-prompt-before-saving} variable, which is @code{always} by
7431 default, giving you that excessive prompting action you know and
7432 loathe. If you set this variable to @code{t} instead, you'll be prompted
7433 just once for each series of articles you save. If you like to really
7434 have Gnus do all your thinking for you, you can even set this variable
7435 to @code{nil}, which means that you will never be prompted for files to
7436 save articles in. Gnus will simply save all the articles in the default
7440 @vindex gnus-default-article-saver
7441 You can customize the @code{gnus-default-article-saver} variable to make
7442 gnus do what you want it to. You can use any of the six ready-made
7443 functions below, or you can create your own.
7447 @item gnus-summary-save-in-rmail
7448 @findex gnus-summary-save-in-rmail
7449 @vindex gnus-rmail-save-name
7450 @findex gnus-plain-save-name
7451 This is the default format, @dfn{Babyl}. Uses the function in the
7452 @code{gnus-rmail-save-name} variable to get a file name to save the
7453 article in. The default is @code{gnus-plain-save-name}.
7455 @item gnus-summary-save-in-mail
7456 @findex gnus-summary-save-in-mail
7457 @vindex gnus-mail-save-name
7458 Save in a Unix mail (mbox) file. Uses the function in the
7459 @code{gnus-mail-save-name} variable to get a file name to save the
7460 article in. The default is @code{gnus-plain-save-name}.
7462 @item gnus-summary-save-in-file
7463 @findex gnus-summary-save-in-file
7464 @vindex gnus-file-save-name
7465 @findex gnus-numeric-save-name
7466 Append the article straight to an ordinary file. Uses the function in
7467 the @code{gnus-file-save-name} variable to get a file name to save the
7468 article in. The default is @code{gnus-numeric-save-name}.
7470 @item gnus-summary-write-to-file
7471 @findex gnus-summary-write-to-file
7472 Write the article straight to an ordinary file. The file is
7473 overwritten if it exists. Uses the function in the
7474 @code{gnus-file-save-name} variable to get a file name to save the
7475 article in. The default is @code{gnus-numeric-save-name}.
7477 @item gnus-summary-save-body-in-file
7478 @findex gnus-summary-save-body-in-file
7479 Append the article body to an ordinary file. Uses the function in the
7480 @code{gnus-file-save-name} variable to get a file name to save the
7481 article in. The default is @code{gnus-numeric-save-name}.
7483 @item gnus-summary-save-in-folder
7484 @findex gnus-summary-save-in-folder
7485 @findex gnus-folder-save-name
7486 @findex gnus-Folder-save-name
7487 @vindex gnus-folder-save-name
7490 Save the article to an MH folder using @code{rcvstore} from the MH
7491 library. Uses the function in the @code{gnus-folder-save-name} variable
7492 to get a file name to save the article in. The default is
7493 @code{gnus-folder-save-name}, but you can also use
7494 @code{gnus-Folder-save-name}, which creates capitalized names.
7496 @item gnus-summary-save-in-vm
7497 @findex gnus-summary-save-in-vm
7498 Save the article in a VM folder. You have to have the VM mail
7499 reader to use this setting.
7502 @vindex gnus-article-save-directory
7503 All of these functions, except for the last one, will save the article
7504 in the @code{gnus-article-save-directory}, which is initialized from the
7505 @env{SAVEDIR} environment variable. This is @file{~/News/} by
7508 As you can see above, the functions use different functions to find a
7509 suitable name of a file to save the article in. Below is a list of
7510 available functions that generate names:
7514 @item gnus-Numeric-save-name
7515 @findex gnus-Numeric-save-name
7516 File names like @file{~/News/Alt.andrea-dworkin/45}.
7518 @item gnus-numeric-save-name
7519 @findex gnus-numeric-save-name
7520 File names like @file{~/News/alt.andrea-dworkin/45}.
7522 @item gnus-Plain-save-name
7523 @findex gnus-Plain-save-name
7524 File names like @file{~/News/Alt.andrea-dworkin}.
7526 @item gnus-plain-save-name
7527 @findex gnus-plain-save-name
7528 File names like @file{~/News/alt.andrea-dworkin}.
7530 @item gnus-sender-save-name
7531 @findex gnus-sender-save-name
7532 File names like @file{~/News/larsi}.
7535 @vindex gnus-split-methods
7536 You can have gnus suggest where to save articles by plonking a regexp into
7537 the @code{gnus-split-methods} alist. For instance, if you would like to
7538 save articles related to gnus in the file @file{gnus-stuff}, and articles
7539 related to VM in @file{vm-stuff}, you could set this variable to something
7543 (("^Subject:.*gnus\\|^Newsgroups:.*gnus" "gnus-stuff")
7544 ("^Subject:.*vm\\|^Xref:.*vm" "vm-stuff")
7545 (my-choosing-function "../other-dir/my-stuff")
7546 ((equal gnus-newsgroup-name "mail.misc") "mail-stuff"))
7549 We see that this is a list where each element is a list that has two
7550 elements---the @dfn{match} and the @dfn{file}. The match can either be
7551 a string (in which case it is used as a regexp to match on the article
7552 head); it can be a symbol (which will be called as a function with the
7553 group name as a parameter); or it can be a list (which will be
7554 @code{eval}ed). If any of these actions have a non-@code{nil} result,
7555 the @dfn{file} will be used as a default prompt. In addition, the
7556 result of the operation itself will be used if the function or form
7557 called returns a string or a list of strings.
7559 You basically end up with a list of file names that might be used when
7560 saving the current article. (All ``matches'' will be used.) You will
7561 then be prompted for what you really want to use as a name, with file
7562 name completion over the results from applying this variable.
7564 This variable is @code{((gnus-article-archive-name))} by default, which
7565 means that gnus will look at the articles it saves for an
7566 @code{Archive-name} line and use that as a suggestion for the file
7569 Here's an example function to clean up file names somewhat. If you have
7570 lots of mail groups called things like
7571 @samp{nnml:mail.whatever}, you may want to chop off the beginning of
7572 these group names before creating the file name to save to. The
7573 following will do just that:
7576 (defun my-save-name (group)
7577 (when (string-match "^nnml:mail." group)
7578 (substring group (match-end 0))))
7580 (setq gnus-split-methods
7581 '((gnus-article-archive-name)
7586 @vindex gnus-use-long-file-name
7587 Finally, you have the @code{gnus-use-long-file-name} variable. If it is
7588 @code{nil}, all the preceding functions will replace all periods
7589 (@samp{.}) in the group names with slashes (@samp{/})---which means that
7590 the functions will generate hierarchies of directories instead of having
7591 all the files in the top level directory
7592 (@file{~/News/alt/andrea-dworkin} instead of
7593 @file{~/News/alt.andrea-dworkin}.) This variable is @code{t} by default
7594 on most systems. However, for historical reasons, this is @code{nil} on
7595 Xenix and usg-unix-v machines by default.
7597 This function also affects kill and score file names. If this variable
7598 is a list, and the list contains the element @code{not-score}, long file
7599 names will not be used for score files, if it contains the element
7600 @code{not-save}, long file names will not be used for saving, and if it
7601 contains the element @code{not-kill}, long file names will not be used
7604 If you'd like to save articles in a hierarchy that looks something like
7608 (setq gnus-use-long-file-name '(not-save)) ; @r{to get a hierarchy}
7609 (setq gnus-default-article-saver
7610 'gnus-summary-save-in-file) ; @r{no encoding}
7613 Then just save with @kbd{o}. You'd then read this hierarchy with
7614 ephemeral @code{nneething} groups---@kbd{G D} in the group buffer, and
7615 the top level directory as the argument (@file{~/News/}). Then just walk
7616 around to the groups/directories with @code{nneething}.
7619 @node Decoding Articles
7620 @section Decoding Articles
7621 @cindex decoding articles
7623 Sometime users post articles (or series of articles) that have been
7624 encoded in some way or other. Gnus can decode them for you.
7627 * Uuencoded Articles:: Uudecode articles.
7628 * Shell Archives:: Unshar articles.
7629 * PostScript Files:: Split PostScript.
7630 * Other Files:: Plain save and binhex.
7631 * Decoding Variables:: Variables for a happy decoding.
7632 * Viewing Files:: You want to look at the result of the decoding?
7636 @cindex article series
7637 All these functions use the process/prefix convention
7638 (@pxref{Process/Prefix}) for finding out what articles to work on, with
7639 the extension that a ``single article'' means ``a single series''. Gnus
7640 can find out by itself what articles belong to a series, decode all the
7641 articles and unpack/view/save the resulting file(s).
7643 Gnus guesses what articles are in the series according to the following
7644 simplish rule: The subjects must be (nearly) identical, except for the
7645 last two numbers of the line. (Spaces are largely ignored, however.)
7647 For example: If you choose a subject called @samp{cat.gif (2/3)}, gnus
7648 will find all the articles that match the regexp @samp{^cat.gif
7649 ([0-9]+/[0-9]+).*$}.
7651 Subjects that are non-standard, like @samp{cat.gif (2/3) Part 6 of a
7652 series}, will not be properly recognized by any of the automatic viewing
7653 commands, and you have to mark the articles manually with @kbd{#}.
7656 @node Uuencoded Articles
7657 @subsection Uuencoded Articles
7659 @cindex uuencoded articles
7664 @kindex X u (Summary)
7665 @findex gnus-uu-decode-uu
7666 @c @icon{gnus-uu-decode-uu}
7667 Uudecodes the current series (@code{gnus-uu-decode-uu}).
7670 @kindex X U (Summary)
7671 @findex gnus-uu-decode-uu-and-save
7672 Uudecodes and saves the current series
7673 (@code{gnus-uu-decode-uu-and-save}).
7676 @kindex X v u (Summary)
7677 @findex gnus-uu-decode-uu-view
7678 Uudecodes and views the current series (@code{gnus-uu-decode-uu-view}).
7681 @kindex X v U (Summary)
7682 @findex gnus-uu-decode-uu-and-save-view
7683 Uudecodes, views and saves the current series
7684 (@code{gnus-uu-decode-uu-and-save-view}).
7688 Remember that these all react to the presence of articles marked with
7689 the process mark. If, for instance, you'd like to decode and save an
7690 entire newsgroup, you'd typically do @kbd{M P a}
7691 (@code{gnus-uu-mark-all}) and then @kbd{X U}
7692 (@code{gnus-uu-decode-uu-and-save}).
7694 All this is very much different from how @code{gnus-uu} worked with
7695 @sc{gnus 4.1}, where you had explicit keystrokes for everything under
7696 the sun. This version of @code{gnus-uu} generally assumes that you mark
7697 articles in some way (@pxref{Setting Process Marks}) and then press
7700 @vindex gnus-uu-notify-files
7701 Note: When trying to decode articles that have names matching
7702 @code{gnus-uu-notify-files}, which is hard-coded to
7703 @samp{[Cc][Ii][Nn][Dd][Yy][0-9]+.\\(gif\\|jpg\\)}, @code{gnus-uu} will
7704 automatically post an article on @samp{comp.unix.wizards} saying that
7705 you have just viewed the file in question. This feature can't be turned
7709 @node Shell Archives
7710 @subsection Shell Archives
7712 @cindex shell archives
7713 @cindex shared articles
7715 Shell archives (``shar files'') used to be a popular way to distribute
7716 sources, but it isn't used all that much today. In any case, we have
7717 some commands to deal with these:
7722 @kindex X s (Summary)
7723 @findex gnus-uu-decode-unshar
7724 Unshars the current series (@code{gnus-uu-decode-unshar}).
7727 @kindex X S (Summary)
7728 @findex gnus-uu-decode-unshar-and-save
7729 Unshars and saves the current series (@code{gnus-uu-decode-unshar-and-save}).
7732 @kindex X v s (Summary)
7733 @findex gnus-uu-decode-unshar-view
7734 Unshars and views the current series (@code{gnus-uu-decode-unshar-view}).
7737 @kindex X v S (Summary)
7738 @findex gnus-uu-decode-unshar-and-save-view
7739 Unshars, views and saves the current series
7740 (@code{gnus-uu-decode-unshar-and-save-view}).
7744 @node PostScript Files
7745 @subsection PostScript Files
7751 @kindex X p (Summary)
7752 @findex gnus-uu-decode-postscript
7753 Unpack the current PostScript series (@code{gnus-uu-decode-postscript}).
7756 @kindex X P (Summary)
7757 @findex gnus-uu-decode-postscript-and-save
7758 Unpack and save the current PostScript series
7759 (@code{gnus-uu-decode-postscript-and-save}).
7762 @kindex X v p (Summary)
7763 @findex gnus-uu-decode-postscript-view
7764 View the current PostScript series
7765 (@code{gnus-uu-decode-postscript-view}).
7768 @kindex X v P (Summary)
7769 @findex gnus-uu-decode-postscript-and-save-view
7770 View and save the current PostScript series
7771 (@code{gnus-uu-decode-postscript-and-save-view}).
7776 @subsection Other Files
7780 @kindex X o (Summary)
7781 @findex gnus-uu-decode-save
7782 Save the current series
7783 (@code{gnus-uu-decode-save}).
7786 @kindex X b (Summary)
7787 @findex gnus-uu-decode-binhex
7788 Unbinhex the current series (@code{gnus-uu-decode-binhex}). This
7789 doesn't really work yet.
7793 @node Decoding Variables
7794 @subsection Decoding Variables
7796 Adjective, not verb.
7799 * Rule Variables:: Variables that say how a file is to be viewed.
7800 * Other Decode Variables:: Other decode variables.
7801 * Uuencoding and Posting:: Variables for customizing uuencoding.
7805 @node Rule Variables
7806 @subsubsection Rule Variables
7807 @cindex rule variables
7809 Gnus uses @dfn{rule variables} to decide how to view a file. All these
7810 variables are of the form
7813 (list '(regexp1 command2)
7820 @item gnus-uu-user-view-rules
7821 @vindex gnus-uu-user-view-rules
7823 This variable is consulted first when viewing files. If you wish to use,
7824 for instance, @code{sox} to convert an @file{.au} sound file, you could
7827 (setq gnus-uu-user-view-rules
7828 (list '("\\\\.au$" "sox %s -t .aiff > /dev/audio")))
7831 @item gnus-uu-user-view-rules-end
7832 @vindex gnus-uu-user-view-rules-end
7833 This variable is consulted if gnus couldn't make any matches from the
7834 user and default view rules.
7836 @item gnus-uu-user-archive-rules
7837 @vindex gnus-uu-user-archive-rules
7838 This variable can be used to say what commands should be used to unpack
7843 @node Other Decode Variables
7844 @subsubsection Other Decode Variables
7847 @vindex gnus-uu-grabbed-file-functions
7849 @item gnus-uu-grabbed-file-functions
7850 All functions in this list will be called right after each file has been
7851 successfully decoded---so that you can move or view files right away,
7852 and don't have to wait for all files to be decoded before you can do
7853 anything. Ready-made functions you can put in this list are:
7857 @item gnus-uu-grab-view
7858 @findex gnus-uu-grab-view
7861 @item gnus-uu-grab-move
7862 @findex gnus-uu-grab-move
7863 Move the file (if you're using a saving function.)
7866 @item gnus-uu-be-dangerous
7867 @vindex gnus-uu-be-dangerous
7868 Specifies what to do if unusual situations arise during decoding. If
7869 @code{nil}, be as conservative as possible. If @code{t}, ignore things
7870 that didn't work, and overwrite existing files. Otherwise, ask each
7873 @item gnus-uu-ignore-files-by-name
7874 @vindex gnus-uu-ignore-files-by-name
7875 Files with name matching this regular expression won't be viewed.
7877 @item gnus-uu-ignore-files-by-type
7878 @vindex gnus-uu-ignore-files-by-type
7879 Files with a @acronym{MIME} type matching this variable won't be viewed.
7880 Note that Gnus tries to guess what type the file is based on the name.
7881 @code{gnus-uu} is not a @acronym{MIME} package (yet), so this is slightly
7884 @item gnus-uu-tmp-dir
7885 @vindex gnus-uu-tmp-dir
7886 Where @code{gnus-uu} does its work.
7888 @item gnus-uu-do-not-unpack-archives
7889 @vindex gnus-uu-do-not-unpack-archives
7890 Non-@code{nil} means that @code{gnus-uu} won't peek inside archives
7891 looking for files to display.
7893 @item gnus-uu-view-and-save
7894 @vindex gnus-uu-view-and-save
7895 Non-@code{nil} means that the user will always be asked to save a file
7898 @item gnus-uu-ignore-default-view-rules
7899 @vindex gnus-uu-ignore-default-view-rules
7900 Non-@code{nil} means that @code{gnus-uu} will ignore the default viewing
7903 @item gnus-uu-ignore-default-archive-rules
7904 @vindex gnus-uu-ignore-default-archive-rules
7905 Non-@code{nil} means that @code{gnus-uu} will ignore the default archive
7908 @item gnus-uu-kill-carriage-return
7909 @vindex gnus-uu-kill-carriage-return
7910 Non-@code{nil} means that @code{gnus-uu} will strip all carriage returns
7913 @item gnus-uu-unmark-articles-not-decoded
7914 @vindex gnus-uu-unmark-articles-not-decoded
7915 Non-@code{nil} means that @code{gnus-uu} will mark unsuccessfully
7916 decoded articles as unread.
7918 @item gnus-uu-correct-stripped-uucode
7919 @vindex gnus-uu-correct-stripped-uucode
7920 Non-@code{nil} means that @code{gnus-uu} will @emph{try} to fix
7921 uuencoded files that have had trailing spaces deleted.
7923 @item gnus-uu-pre-uudecode-hook
7924 @vindex gnus-uu-pre-uudecode-hook
7925 Hook run before sending a message to @code{uudecode}.
7927 @item gnus-uu-view-with-metamail
7928 @vindex gnus-uu-view-with-metamail
7930 Non-@code{nil} means that @code{gnus-uu} will ignore the viewing
7931 commands defined by the rule variables and just fudge a @acronym{MIME}
7932 content type based on the file name. The result will be fed to
7933 @code{metamail} for viewing.
7935 @item gnus-uu-save-in-digest
7936 @vindex gnus-uu-save-in-digest
7937 Non-@code{nil} means that @code{gnus-uu}, when asked to save without
7938 decoding, will save in digests. If this variable is @code{nil},
7939 @code{gnus-uu} will just save everything in a file without any
7940 embellishments. The digesting almost conforms to RFC 1153---no easy way
7941 to specify any meaningful volume and issue numbers were found, so I
7942 simply dropped them.
7947 @node Uuencoding and Posting
7948 @subsubsection Uuencoding and Posting
7952 @item gnus-uu-post-include-before-composing
7953 @vindex gnus-uu-post-include-before-composing
7954 Non-@code{nil} means that @code{gnus-uu} will ask for a file to encode
7955 before you compose the article. If this variable is @code{t}, you can
7956 either include an encoded file with @kbd{C-c C-i} or have one included
7957 for you when you post the article.
7959 @item gnus-uu-post-length
7960 @vindex gnus-uu-post-length
7961 Maximum length of an article. The encoded file will be split into how
7962 many articles it takes to post the entire file.
7964 @item gnus-uu-post-threaded
7965 @vindex gnus-uu-post-threaded
7966 Non-@code{nil} means that @code{gnus-uu} will post the encoded file in a
7967 thread. This may not be smart, as no other decoder I have seen is able
7968 to follow threads when collecting uuencoded articles. (Well, I have
7969 seen one package that does that---@code{gnus-uu}, but somehow, I don't
7970 think that counts@dots{}) Default is @code{nil}.
7972 @item gnus-uu-post-separate-description
7973 @vindex gnus-uu-post-separate-description
7974 Non-@code{nil} means that the description will be posted in a separate
7975 article. The first article will typically be numbered (0/x). If this
7976 variable is @code{nil}, the description the user enters will be included
7977 at the beginning of the first article, which will be numbered (1/x).
7978 Default is @code{t}.
7984 @subsection Viewing Files
7985 @cindex viewing files
7986 @cindex pseudo-articles
7988 After decoding, if the file is some sort of archive, gnus will attempt
7989 to unpack the archive and see if any of the files in the archive can be
7990 viewed. For instance, if you have a gzipped tar file @file{pics.tar.gz}
7991 containing the files @file{pic1.jpg} and @file{pic2.gif}, gnus will
7992 uncompress and de-tar the main file, and then view the two pictures.
7993 This unpacking process is recursive, so if the archive contains archives
7994 of archives, it'll all be unpacked.
7996 Finally, gnus will normally insert a @dfn{pseudo-article} for each
7997 extracted file into the summary buffer. If you go to these
7998 ``articles'', you will be prompted for a command to run (usually Gnus
7999 will make a suggestion), and then the command will be run.
8001 @vindex gnus-view-pseudo-asynchronously
8002 If @code{gnus-view-pseudo-asynchronously} is @code{nil}, Emacs will wait
8003 until the viewing is done before proceeding.
8005 @vindex gnus-view-pseudos
8006 If @code{gnus-view-pseudos} is @code{automatic}, Gnus will not insert
8007 the pseudo-articles into the summary buffer, but view them
8008 immediately. If this variable is @code{not-confirm}, the user won't even
8009 be asked for a confirmation before viewing is done.
8011 @vindex gnus-view-pseudos-separately
8012 If @code{gnus-view-pseudos-separately} is non-@code{nil}, one
8013 pseudo-article will be created for each file to be viewed. If
8014 @code{nil}, all files that use the same viewing command will be given as
8015 a list of parameters to that command.
8017 @vindex gnus-insert-pseudo-articles
8018 If @code{gnus-insert-pseudo-articles} is non-@code{nil}, insert
8019 pseudo-articles when decoding. It is @code{t} by default.
8021 So; there you are, reading your @emph{pseudo-articles} in your
8022 @emph{virtual newsgroup} from the @emph{virtual server}; and you think:
8023 Why isn't anything real anymore? How did we get here?
8026 @node Article Treatment
8027 @section Article Treatment
8029 Reading through this huge manual, you may have quite forgotten that the
8030 object of newsreaders is to actually, like, read what people have
8031 written. Reading articles. Unfortunately, people are quite bad at
8032 writing, so there are tons of functions and variables to make reading
8033 these articles easier.
8036 * Article Highlighting:: You want to make the article look like fruit salad.
8037 * Article Fontisizing:: Making emphasized text look nice.
8038 * Article Hiding:: You also want to make certain info go away.
8039 * Article Washing:: Lots of way-neat functions to make life better.
8040 * Article Header:: Doing various header transformations.
8041 * Article Buttons:: Click on URLs, Message-IDs, addresses and the like.
8042 * Article Button Levels:: Controlling appearance of buttons.
8043 * Article Date:: Grumble, UT!
8044 * Article Display:: Display various stuff---X-Face, Picons, Smileys
8045 * Article Signature:: What is a signature?
8046 * Article Miscellanea:: Various other stuff.
8050 @node Article Highlighting
8051 @subsection Article Highlighting
8052 @cindex highlighting
8054 Not only do you want your article buffer to look like fruit salad, but
8055 you want it to look like technicolor fruit salad.
8060 @kindex W H a (Summary)
8061 @findex gnus-article-highlight
8062 @findex gnus-article-maybe-highlight
8063 Do much highlighting of the current article
8064 (@code{gnus-article-highlight}). This function highlights header, cited
8065 text, the signature, and adds buttons to the body and the head.
8068 @kindex W H h (Summary)
8069 @findex gnus-article-highlight-headers
8070 @vindex gnus-header-face-alist
8071 Highlight the headers (@code{gnus-article-highlight-headers}). The
8072 highlighting will be done according to the @code{gnus-header-face-alist}
8073 variable, which is a list where each element has the form
8074 @code{(@var{regexp} @var{name} @var{content})}.
8075 @var{regexp} is a regular expression for matching the
8076 header, @var{name} is the face used for highlighting the header name
8077 (@pxref{Faces and Fonts}) and @var{content} is the face for highlighting
8078 the header value. The first match made will be used. Note that
8079 @var{regexp} shouldn't have @samp{^} prepended---Gnus will add one.
8082 @kindex W H c (Summary)
8083 @findex gnus-article-highlight-citation
8084 Highlight cited text (@code{gnus-article-highlight-citation}).
8086 Some variables to customize the citation highlights:
8089 @vindex gnus-cite-parse-max-size
8091 @item gnus-cite-parse-max-size
8092 If the article size if bigger than this variable (which is 25000 by
8093 default), no citation highlighting will be performed.
8095 @item gnus-cite-max-prefix
8096 @vindex gnus-cite-max-prefix
8097 Maximum possible length for a citation prefix (default 20).
8099 @item gnus-cite-face-list
8100 @vindex gnus-cite-face-list
8101 List of faces used for highlighting citations (@pxref{Faces and Fonts}).
8102 When there are citations from multiple articles in the same message,
8103 gnus will try to give each citation from each article its own face.
8104 This should make it easier to see who wrote what.
8106 @item gnus-supercite-regexp
8107 @vindex gnus-supercite-regexp
8108 Regexp matching normal Supercite attribution lines.
8110 @item gnus-supercite-secondary-regexp
8111 @vindex gnus-supercite-secondary-regexp
8112 Regexp matching mangled Supercite attribution lines.
8114 @item gnus-cite-minimum-match-count
8115 @vindex gnus-cite-minimum-match-count
8116 Minimum number of identical prefixes we have to see before we believe
8117 that it's a citation.
8119 @item gnus-cite-attribution-prefix
8120 @vindex gnus-cite-attribution-prefix
8121 Regexp matching the beginning of an attribution line.
8123 @item gnus-cite-attribution-suffix
8124 @vindex gnus-cite-attribution-suffix
8125 Regexp matching the end of an attribution line.
8127 @item gnus-cite-attribution-face
8128 @vindex gnus-cite-attribution-face
8129 Face used for attribution lines. It is merged with the face for the
8130 cited text belonging to the attribution.
8132 @item gnus-cite-ignore-quoted-from
8133 @vindex gnus-cite-ignore-quoted-from
8134 If non-@code{nil}, no citation highlighting will be performed on lines
8135 beginning with @samp{>From }. Those lines may have been quoted by MTAs
8136 in order not to mix up with the envelope From line. The default value
8143 @kindex W H s (Summary)
8144 @vindex gnus-signature-separator
8145 @vindex gnus-signature-face
8146 @findex gnus-article-highlight-signature
8147 Highlight the signature (@code{gnus-article-highlight-signature}).
8148 Everything after @code{gnus-signature-separator} (@pxref{Article
8149 Signature}) in an article will be considered a signature and will be
8150 highlighted with @code{gnus-signature-face}, which is @code{italic} by
8155 @xref{Customizing Articles}, for how to highlight articles automatically.
8158 @node Article Fontisizing
8159 @subsection Article Fontisizing
8161 @cindex article emphasis
8163 @findex gnus-article-emphasize
8164 @kindex W e (Summary)
8165 People commonly add emphasis to words in news articles by writing things
8166 like @samp{_this_} or @samp{*this*} or @samp{/this/}. Gnus can make
8167 this look nicer by running the article through the @kbd{W e}
8168 (@code{gnus-article-emphasize}) command.
8170 @vindex gnus-emphasis-alist
8171 How the emphasis is computed is controlled by the
8172 @code{gnus-emphasis-alist} variable. This is an alist where the first
8173 element is a regular expression to be matched. The second is a number
8174 that says what regular expression grouping is used to find the entire
8175 emphasized word. The third is a number that says what regexp grouping
8176 should be displayed and highlighted. (The text between these two
8177 groupings will be hidden.) The fourth is the face used for
8181 (setq gnus-emphasis-alist
8182 '(("_\\(\\w+\\)_" 0 1 gnus-emphasis-underline)
8183 ("\\*\\(\\w+\\)\\*" 0 1 gnus-emphasis-bold)))
8192 @vindex gnus-emphasis-underline
8193 @vindex gnus-emphasis-bold
8194 @vindex gnus-emphasis-italic
8195 @vindex gnus-emphasis-underline-bold
8196 @vindex gnus-emphasis-underline-italic
8197 @vindex gnus-emphasis-bold-italic
8198 @vindex gnus-emphasis-underline-bold-italic
8199 By default, there are seven rules, and they use the following faces:
8200 @code{gnus-emphasis-bold}, @code{gnus-emphasis-italic},
8201 @code{gnus-emphasis-underline}, @code{gnus-emphasis-bold-italic},
8202 @code{gnus-emphasis-underline-italic},
8203 @code{gnus-emphasis-underline-bold}, and
8204 @code{gnus-emphasis-underline-bold-italic}.
8206 If you want to change these faces, you can either use @kbd{M-x
8207 customize}, or you can use @code{copy-face}. For instance, if you want
8208 to make @code{gnus-emphasis-italic} use a red face instead, you could
8212 (copy-face 'red 'gnus-emphasis-italic)
8215 @vindex gnus-group-highlight-words-alist
8217 If you want to highlight arbitrary words, you can use the
8218 @code{gnus-group-highlight-words-alist} variable, which uses the same
8219 syntax as @code{gnus-emphasis-alist}. The @code{highlight-words} group
8220 parameter (@pxref{Group Parameters}) can also be used.
8222 @xref{Customizing Articles}, for how to fontize articles automatically.
8225 @node Article Hiding
8226 @subsection Article Hiding
8227 @cindex article hiding
8229 Or rather, hiding certain things in each article. There usually is much
8230 too much cruft in most articles.
8235 @kindex W W a (Summary)
8236 @findex gnus-article-hide
8237 Do quite a lot of hiding on the article buffer
8238 (@kbd{gnus-article-hide}). In particular, this function will hide
8239 headers, @acronym{PGP}, cited text and the signature.
8242 @kindex W W h (Summary)
8243 @findex gnus-article-hide-headers
8244 Hide headers (@code{gnus-article-hide-headers}). @xref{Hiding
8248 @kindex W W b (Summary)
8249 @findex gnus-article-hide-boring-headers
8250 Hide headers that aren't particularly interesting
8251 (@code{gnus-article-hide-boring-headers}). @xref{Hiding Headers}.
8254 @kindex W W s (Summary)
8255 @findex gnus-article-hide-signature
8256 Hide signature (@code{gnus-article-hide-signature}). @xref{Article
8260 @kindex W W l (Summary)
8261 @findex gnus-article-hide-list-identifiers
8262 @vindex gnus-list-identifiers
8263 Strip list identifiers specified in @code{gnus-list-identifiers}. These
8264 are strings some mailing list servers add to the beginning of all
8265 @code{Subject} headers---for example, @samp{[zebra 4711]}. Any leading
8266 @samp{Re: } is skipped before stripping. @code{gnus-list-identifiers}
8267 may not contain @code{\\(..\\)}.
8271 @item gnus-list-identifiers
8272 @vindex gnus-list-identifiers
8273 A regular expression that matches list identifiers to be removed from
8274 subject. This can also be a list of regular expressions.
8279 @kindex W W P (Summary)
8280 @findex gnus-article-hide-pem
8281 Hide @acronym{PEM} (privacy enhanced messages) cruft
8282 (@code{gnus-article-hide-pem}).
8285 @kindex W W B (Summary)
8286 @findex gnus-article-strip-banner
8287 @vindex gnus-article-banner-alist
8288 @vindex gnus-article-address-banner-alist
8291 @cindex stripping advertisements
8292 @cindex advertisements
8293 Strip the banner specified by the @code{banner} group parameter
8294 (@code{gnus-article-strip-banner}). This is mainly used to hide those
8295 annoying banners and/or signatures that some mailing lists and moderated
8296 groups adds to all the messages. The way to use this function is to add
8297 the @code{banner} group parameter (@pxref{Group Parameters}) to the
8298 group you want banners stripped from. The parameter either be a string,
8299 which will be interpreted as a regular expression matching text to be
8300 removed, or the symbol @code{signature}, meaning that the (last)
8301 signature should be removed, or other symbol, meaning that the
8302 corresponding regular expression in @code{gnus-article-banner-alist} is
8305 Regardless of a group, you can hide things like advertisements only when
8306 the sender of an article has a certain mail address specified in
8307 @code{gnus-article-address-banner-alist}.
8311 @item gnus-article-address-banner-alist
8312 @vindex gnus-article-address-banner-alist
8313 Alist of mail addresses and banners. Each element has the form
8314 @code{(@var{address} . @var{banner})}, where @var{address} is a regexp
8315 matching a mail address in the From header, @var{banner} is one of a
8316 symbol @code{signature}, an item in @code{gnus-article-banner-alist},
8317 a regexp and @code{nil}. If @var{address} matches author's mail
8318 address, it will remove things like advertisements. For example, if a
8319 sender has the mail address @samp{hail@@yoo-hoo.co.jp} and there is a
8320 banner something like @samp{Do You Yoo-hoo!?} in all articles he
8321 sends, you can use the following element to remove them:
8324 ("@@yoo-hoo\\.co\\.jp\\'" .
8325 "\n_+\nDo You Yoo-hoo!\\?\n.*\n.*\n")
8331 @kindex W W c (Summary)
8332 @findex gnus-article-hide-citation
8333 Hide citation (@code{gnus-article-hide-citation}). Some variables for
8334 customizing the hiding:
8338 @item gnus-cited-opened-text-button-line-format
8339 @itemx gnus-cited-closed-text-button-line-format
8340 @vindex gnus-cited-closed-text-button-line-format
8341 @vindex gnus-cited-opened-text-button-line-format
8342 Gnus adds buttons to show where the cited text has been hidden, and to
8343 allow toggle hiding the text. The format of the variable is specified
8344 by these format-like variable (@pxref{Formatting Variables}). These
8349 Starting point of the hidden text.
8351 Ending point of the hidden text.
8353 Number of characters in the hidden region.
8355 Number of lines of hidden text.
8358 @item gnus-cited-lines-visible
8359 @vindex gnus-cited-lines-visible
8360 The number of lines at the beginning of the cited text to leave
8361 shown. This can also be a cons cell with the number of lines at the top
8362 and bottom of the text, respectively, to remain visible.
8367 @kindex W W C-c (Summary)
8368 @findex gnus-article-hide-citation-maybe
8370 Hide citation (@code{gnus-article-hide-citation-maybe}) depending on the
8371 following two variables:
8374 @item gnus-cite-hide-percentage
8375 @vindex gnus-cite-hide-percentage
8376 If the cited text is of a bigger percentage than this variable (default
8377 50), hide the cited text.
8379 @item gnus-cite-hide-absolute
8380 @vindex gnus-cite-hide-absolute
8381 The cited text must have at least this length (default 10) before it
8386 @kindex W W C (Summary)
8387 @findex gnus-article-hide-citation-in-followups
8388 Hide cited text in articles that aren't roots
8389 (@code{gnus-article-hide-citation-in-followups}). This isn't very
8390 useful as an interactive command, but might be a handy function to stick
8391 have happen automatically (@pxref{Customizing Articles}).
8395 All these ``hiding'' commands are toggles, but if you give a negative
8396 prefix to these commands, they will show what they have previously
8397 hidden. If you give a positive prefix, they will always hide.
8399 Also @pxref{Article Highlighting} for further variables for
8400 citation customization.
8402 @xref{Customizing Articles}, for how to hide article elements
8406 @node Article Washing
8407 @subsection Article Washing
8409 @cindex article washing
8411 We call this ``article washing'' for a really good reason. Namely, the
8412 @kbd{A} key was taken, so we had to use the @kbd{W} key instead.
8414 @dfn{Washing} is defined by us as ``changing something from something to
8415 something else'', but normally results in something looking better.
8418 @xref{Customizing Articles}, if you want to change how Gnus displays
8419 articles by default.
8424 This is not really washing, it's sort of the opposite of washing. If
8425 you type this, you see the article exactly as it exists on disk or on
8429 Force redisplaying of the current article
8430 (@code{gnus-summary-show-article}). This is also not really washing.
8431 If you type this, you see the article without any previously applied
8432 interactive Washing functions but with all default treatments
8433 (@pxref{Customizing Articles}).
8436 @kindex W l (Summary)
8437 @findex gnus-summary-stop-page-breaking
8438 Remove page breaks from the current article
8439 (@code{gnus-summary-stop-page-breaking}). @xref{Misc Article}, for page
8443 @kindex W r (Summary)
8444 @findex gnus-summary-caesar-message
8445 @c @icon{gnus-summary-caesar-message}
8446 Do a Caesar rotate (rot13) on the article buffer
8447 (@code{gnus-summary-caesar-message}).
8448 Unreadable articles that tell you to read them with Caesar rotate or rot13.
8449 (Typically offensive jokes and such.)
8451 It's commonly called ``rot13'' because each letter is rotated 13
8452 positions in the alphabet, e. g. @samp{B} (letter #2) -> @samp{O} (letter
8453 #15). It is sometimes referred to as ``Caesar rotate'' because Caesar
8454 is rumored to have employed this form of, uh, somewhat weak encryption.
8457 @kindex W m (Summary)
8458 @findex gnus-summary-morse-message
8459 Morse decode the article buffer (@code{gnus-summary-morse-message}).
8462 @kindex W i (Summary)
8463 @findex gnus-summary-idna-message
8464 Decode IDNA encoded domain names in the current articles. IDNA
8465 encoded domain names looks like @samp{xn--bar}. If a string remain
8466 unencoded after running invoking this, it is likely an invalid IDNA
8467 string (@samp{xn--bar} is invalid). You must have GNU Libidn
8468 (@url{http://www.gnu.org/software/libidn/}) installed for this command
8473 @kindex W t (Summary)
8475 @findex gnus-summary-toggle-header
8476 Toggle whether to display all headers in the article buffer
8477 (@code{gnus-summary-toggle-header}).
8480 @kindex W v (Summary)
8481 @findex gnus-summary-verbose-headers
8482 Toggle whether to display all headers in the article buffer permanently
8483 (@code{gnus-summary-verbose-headers}).
8486 @kindex W m (Summary)
8487 @findex gnus-summary-toggle-mime
8488 Toggle whether to run the article through @acronym{MIME} before
8489 displaying (@code{gnus-summary-toggle-mime}).
8492 @kindex W o (Summary)
8493 @findex gnus-article-treat-overstrike
8494 Treat overstrike (@code{gnus-article-treat-overstrike}).
8497 @kindex W d (Summary)
8498 @findex gnus-article-treat-dumbquotes
8499 @vindex gnus-article-dumbquotes-map
8501 @cindex M****s*** sm*rtq**t*s
8503 Treat M****s*** sm*rtq**t*s according to
8504 @code{gnus-article-dumbquotes-map}
8505 (@code{gnus-article-treat-dumbquotes}). Note that this function guesses
8506 whether a character is a sm*rtq**t* or not, so it should only be used
8509 Sm*rtq**t*s are M****s***'s unilateral extension to the character map in
8510 an attempt to provide more quoting characters. If you see something
8511 like @code{\222} or @code{\264} where you're expecting some kind of
8512 apostrophe or quotation mark, then try this wash.
8515 @kindex W Y f (Summary)
8516 @findex gnus-article-outlook-deuglify-article
8517 @cindex Outlook Express
8518 Full deuglify of broken Outlook (Express) articles: Treat dumbquotes,
8519 unwrap lines, repair attribution and rearrange citation.
8520 (@code{gnus-article-outlook-deuglify-article}).
8523 @kindex W Y u (Summary)
8524 @findex gnus-article-outlook-unwrap-lines
8525 @vindex gnus-outlook-deuglify-unwrap-min
8526 @vindex gnus-outlook-deuglify-unwrap-max
8527 Unwrap lines that appear to be wrapped citation lines. You can control
8528 what lines will be unwrapped by frobbing
8529 @code{gnus-outlook-deuglify-unwrap-min} and
8530 @code{gnus-outlook-deuglify-unwrap-max}, indicating the minimum and
8531 maximum length of an unwrapped citation line.
8532 (@code{gnus-article-outlook-unwrap-lines}).
8535 @kindex W Y a (Summary)
8536 @findex gnus-article-outlook-repair-attribution
8537 Repair a broken attribution line.@*
8538 (@code{gnus-article-outlook-repair-attribution}).
8541 @kindex W Y c (Summary)
8542 @findex gnus-article-outlook-rearrange-citation
8543 Repair broken citations by rearranging the text.
8544 (@code{gnus-article-outlook-rearrange-citation}).
8547 @kindex W w (Summary)
8548 @findex gnus-article-fill-cited-article
8549 Do word wrap (@code{gnus-article-fill-cited-article}).
8551 You can give the command a numerical prefix to specify the width to use
8555 @kindex W Q (Summary)
8556 @findex gnus-article-fill-long-lines
8557 Fill long lines (@code{gnus-article-fill-long-lines}).
8560 @kindex W C (Summary)
8561 @findex gnus-article-capitalize-sentences
8562 Capitalize the first word in each sentence
8563 (@code{gnus-article-capitalize-sentences}).
8566 @kindex W c (Summary)
8567 @findex gnus-article-remove-cr
8568 Translate CRLF pairs (i. e., @samp{^M}s on the end of the lines) into LF
8569 (this takes care of DOS line endings), and then translate any remaining
8570 CRs into LF (this takes care of Mac line endings)
8571 (@code{gnus-article-remove-cr}).
8573 @kindex W q (Summary)
8574 @findex gnus-article-de-quoted-unreadable
8575 Treat quoted-printable (@code{gnus-article-de-quoted-unreadable}).
8576 Quoted-Printable is one common @acronym{MIME} encoding employed when
8577 sending non-@acronym{ASCII} (i.e., 8-bit) articles. It typically
8578 makes strings like @samp{d@'ej@`a vu} look like @samp{d=E9j=E0 vu},
8579 which doesn't look very readable to me. Note that this is usually
8580 done automatically by Gnus if the message in question has a
8581 @code{Content-Transfer-Encoding} header that says that this encoding
8582 has been done. If a prefix is given, a charset will be asked for.
8585 @kindex W 6 (Summary)
8586 @findex gnus-article-de-base64-unreadable
8587 Treat base64 (@code{gnus-article-de-base64-unreadable}). Base64 is
8588 one common @acronym{MIME} encoding employed when sending
8589 non-@acronym{ASCII} (i.e., 8-bit) articles. Note that this is
8590 usually done automatically by Gnus if the message in question has a
8591 @code{Content-Transfer-Encoding} header that says that this encoding
8592 has been done. If a prefix is given, a charset will be asked for.
8595 @kindex W Z (Summary)
8596 @findex gnus-article-decode-HZ
8597 Treat HZ or HZP (@code{gnus-article-decode-HZ}). HZ (or HZP) is one
8598 common encoding employed when sending Chinese articles. It typically
8599 makes strings look like @samp{~@{<:Ky2;S@{#,NpJ)l6HK!#~@}}.
8602 @kindex W A (Summary)
8603 @findex gnus-article-treat-ansi-sequences
8604 @cindex @acronym{ANSI} control sequences
8605 Translate @acronym{ANSI} SGR control sequences into overlays or
8606 extents (@code{gnus-article-treat-ansi-sequences}). @acronym{ANSI}
8607 sequences are used in some Chinese hierarchies for highlighting.
8610 @kindex W u (Summary)
8611 @findex gnus-article-unsplit-urls
8612 Remove newlines from within URLs. Some mailers insert newlines into
8613 outgoing email messages to keep lines short. This reformatting can
8614 split long URLs onto multiple lines. Repair those URLs by removing
8615 the newlines (@code{gnus-article-unsplit-urls}).
8618 @kindex W h (Summary)
8619 @findex gnus-article-wash-html
8620 Treat @acronym{HTML} (@code{gnus-article-wash-html}). Note that this is
8621 usually done automatically by Gnus if the message in question has a
8622 @code{Content-Type} header that says that the message is @acronym{HTML}.
8624 If a prefix is given, a charset will be asked for.
8626 @vindex gnus-article-wash-function
8627 The default is to use the function specified by
8628 @code{mm-text-html-renderer} (@pxref{Display Customization, ,Display
8629 Customization, emacs-mime, The Emacs MIME Manual}) to convert the
8630 @acronym{HTML}, but this is controlled by the
8631 @code{gnus-article-wash-function} variable. Pre-defined functions you
8639 Use @uref{http://emacs-w3m.namazu.org/, emacs-w3m}.
8642 Use @uref{http://links.sf.net/, Links}.
8645 Use @uref{http://lynx.isc.org/, Lynx}.
8648 Use html2text---a simple @acronym{HTML} converter included with Gnus.
8653 @kindex W b (Summary)
8654 @findex gnus-article-add-buttons
8655 Add clickable buttons to the article (@code{gnus-article-add-buttons}).
8656 @xref{Article Buttons}.
8659 @kindex W B (Summary)
8660 @findex gnus-article-add-buttons-to-head
8661 Add clickable buttons to the article headers
8662 (@code{gnus-article-add-buttons-to-head}).
8665 @kindex W p (Summary)
8666 @findex gnus-article-verify-x-pgp-sig
8667 Verify a signed control message
8668 (@code{gnus-article-verify-x-pgp-sig}). Control messages such as
8669 @code{newgroup} and @code{checkgroups} are usually signed by the
8670 hierarchy maintainer. You need to add the @acronym{PGP} public key of
8671 the maintainer to your keyring to verify the
8672 message.@footnote{@acronym{PGP} keys for many hierarchies are
8673 available at @uref{ftp://ftp.isc.org/pub/pgpcontrol/README.html}}
8676 @kindex W s (Summary)
8677 @findex gnus-summary-force-verify-and-decrypt
8678 Verify a signed (@acronym{PGP}, @acronym{PGP/MIME} or
8679 @acronym{S/MIME}) message
8680 (@code{gnus-summary-force-verify-and-decrypt}). @xref{Security}.
8683 @kindex W a (Summary)
8684 @findex gnus-article-strip-headers-in-body
8685 Strip headers like the @code{X-No-Archive} header from the beginning of
8686 article bodies (@code{gnus-article-strip-headers-in-body}).
8689 @kindex W E l (Summary)
8690 @findex gnus-article-strip-leading-blank-lines
8691 Remove all blank lines from the beginning of the article
8692 (@code{gnus-article-strip-leading-blank-lines}).
8695 @kindex W E m (Summary)
8696 @findex gnus-article-strip-multiple-blank-lines
8697 Replace all blank lines with empty lines and then all multiple empty
8698 lines with a single empty line.
8699 (@code{gnus-article-strip-multiple-blank-lines}).
8702 @kindex W E t (Summary)
8703 @findex gnus-article-remove-trailing-blank-lines
8704 Remove all blank lines at the end of the article
8705 (@code{gnus-article-remove-trailing-blank-lines}).
8708 @kindex W E a (Summary)
8709 @findex gnus-article-strip-blank-lines
8710 Do all the three commands above
8711 (@code{gnus-article-strip-blank-lines}).
8714 @kindex W E A (Summary)
8715 @findex gnus-article-strip-all-blank-lines
8716 Remove all blank lines
8717 (@code{gnus-article-strip-all-blank-lines}).
8720 @kindex W E s (Summary)
8721 @findex gnus-article-strip-leading-space
8722 Remove all white space from the beginning of all lines of the article
8723 body (@code{gnus-article-strip-leading-space}).
8726 @kindex W E e (Summary)
8727 @findex gnus-article-strip-trailing-space
8728 Remove all white space from the end of all lines of the article
8729 body (@code{gnus-article-strip-trailing-space}).
8733 @xref{Customizing Articles}, for how to wash articles automatically.
8736 @node Article Header
8737 @subsection Article Header
8739 These commands perform various transformations of article header.
8744 @kindex W G u (Summary)
8745 @findex gnus-article-treat-unfold-headers
8746 Unfold folded header lines (@code{gnus-article-treat-unfold-headers}).
8749 @kindex W G n (Summary)
8750 @findex gnus-article-treat-fold-newsgroups
8751 Fold the @code{Newsgroups} and @code{Followup-To} headers
8752 (@code{gnus-article-treat-fold-newsgroups}).
8755 @kindex W G f (Summary)
8756 @findex gnus-article-treat-fold-headers
8757 Fold all the message headers
8758 (@code{gnus-article-treat-fold-headers}).
8761 @kindex W E w (Summary)
8762 @findex gnus-article-remove-leading-whitespace
8763 Remove excessive whitespace from all headers
8764 (@code{gnus-article-remove-leading-whitespace}).
8769 @node Article Buttons
8770 @subsection Article Buttons
8773 People often include references to other stuff in articles, and it would
8774 be nice if Gnus could just fetch whatever it is that people talk about
8775 with the minimum of fuzz when you hit @kbd{RET} or use the middle mouse
8776 button on these references.
8778 @vindex gnus-button-man-handler
8779 Gnus adds @dfn{buttons} to certain standard references by default:
8780 Well-formed URLs, mail addresses, Message-IDs, Info links, man pages and
8781 Emacs or Gnus related references. This is controlled by two variables,
8782 one that handles article bodies and one that handles article heads:
8786 @item gnus-button-alist
8787 @vindex gnus-button-alist
8788 This is an alist where each entry has this form:
8791 (@var{regexp} @var{button-par} @var{use-p} @var{function} @var{data-par})
8797 All text that match this regular expression (case insensitive) will be
8798 considered an external reference. Here's a typical regexp that matches
8799 embedded URLs: @samp{<URL:\\([^\n\r>]*\\)>}. This can also be a
8800 variable containing a regexp, useful variables to use include
8801 @code{gnus-button-url-regexp} and @code{gnus-button-mid-or-mail-regexp}.
8804 Gnus has to know which parts of the matches is to be highlighted. This
8805 is a number that says what sub-expression of the regexp is to be
8806 highlighted. If you want it all highlighted, you use 0 here.
8809 This form will be @code{eval}ed, and if the result is non-@code{nil},
8810 this is considered a match. This is useful if you want extra sifting to
8811 avoid false matches. Often variables named
8812 @code{gnus-button-@var{*}-level} are used here, @xref{Article Button
8813 Levels}, but any other form may be used too.
8815 @c @code{use-p} is @code{eval}ed only if @code{regexp} matches.
8818 This function will be called when you click on this button.
8821 As with @var{button-par}, this is a sub-expression number, but this one
8822 says which part of the match is to be sent as data to @var{function}.
8826 So the full entry for buttonizing URLs is then
8829 ("<URL:\\([^\n\r>]*\\)>" 0 t gnus-button-url 1)
8832 @item gnus-header-button-alist
8833 @vindex gnus-header-button-alist
8834 This is just like the other alist, except that it is applied to the
8835 article head only, and that each entry has an additional element that is
8836 used to say what headers to apply the buttonize coding to:
8839 (@var{header} @var{regexp} @var{button-par} @var{use-p} @var{function} @var{data-par})
8842 @var{header} is a regular expression.
8845 @subsubsection Related variables and functions
8848 @item gnus-button-@var{*}-level
8849 @xref{Article Button Levels}.
8851 @c Stuff related to gnus-button-browse-level
8853 @item gnus-button-url-regexp
8854 @vindex gnus-button-url-regexp
8855 A regular expression that matches embedded URLs. It is used in the
8856 default values of the variables above.
8858 @c Stuff related to gnus-button-man-level
8860 @item gnus-button-man-handler
8861 @vindex gnus-button-man-handler
8862 The function to use for displaying man pages. It must take at least one
8863 argument with a string naming the man page.
8865 @c Stuff related to gnus-button-message-level
8867 @item gnus-button-mid-or-mail-regexp
8868 @vindex gnus-button-mid-or-mail-regexp
8869 Regular expression that matches a message ID or a mail address.
8871 @item gnus-button-prefer-mid-or-mail
8872 @vindex gnus-button-prefer-mid-or-mail
8873 This variable determines what to do when the button on a string as
8874 @samp{foo123@@bar.invalid} is pushed. Strings like this can be either a
8875 message ID or a mail address. If it is one of the symbols @code{mid} or
8876 @code{mail}, Gnus will always assume that the string is a message ID or
8877 a mail address, respectively. If this variable is set to the symbol
8878 @code{ask}, always query the user what do do. If it is a function, this
8879 function will be called with the string as its only argument. The
8880 function must return @code{mid}, @code{mail}, @code{invalid} or
8881 @code{ask}. The default value is the function
8882 @code{gnus-button-mid-or-mail-heuristic}.
8884 @item gnus-button-mid-or-mail-heuristic
8885 @findex gnus-button-mid-or-mail-heuristic
8886 Function that guesses whether its argument is a message ID or a mail
8887 address. Returns @code{mid} if it's a message IDs, @code{mail} if
8888 it's a mail address, @code{ask} if unsure and @code{invalid} if the
8891 @item gnus-button-mid-or-mail-heuristic-alist
8892 @vindex gnus-button-mid-or-mail-heuristic-alist
8893 An alist of @code{(RATE . REGEXP)} pairs used by the function
8894 @code{gnus-button-mid-or-mail-heuristic}.
8896 @c Stuff related to gnus-button-tex-level
8898 @item gnus-button-ctan-handler
8899 @findex gnus-button-ctan-handler
8900 The function to use for displaying CTAN links. It must take one
8901 argument, the string naming the URL.
8904 @vindex gnus-ctan-url
8905 Top directory of a CTAN (Comprehensive TeX Archive Network) archive used
8906 by @code{gnus-button-ctan-handler}.
8910 @item gnus-article-button-face
8911 @vindex gnus-article-button-face
8912 Face used on buttons.
8914 @item gnus-article-mouse-face
8915 @vindex gnus-article-mouse-face
8916 Face used when the mouse cursor is over a button.
8920 @xref{Customizing Articles}, for how to buttonize articles automatically.
8923 @node Article Button Levels
8924 @subsection Article button levels
8925 @cindex button levels
8926 The higher the value of the variables @code{gnus-button-@var{*}-level},
8927 the more buttons will appear. If the level is zero, no corresponding
8928 buttons are displayed. With the default value (which is 5) you should
8929 already see quite a lot of buttons. With higher levels, you will see
8930 more buttons, but you may also get more false positives. To avoid them,
8931 you can set the variables @code{gnus-button-@var{*}-level} local to
8932 specific groups (@pxref{Group Parameters}). Here's an example for the
8933 variable @code{gnus-parameters}:
8936 ;; @r{increase @code{gnus-button-*-level} in some groups:}
8937 (setq gnus-parameters
8938 '(("\\<\\(emacs\\|gnus\\)\\>" (gnus-button-emacs-level 10))
8939 ("\\<unix\\>" (gnus-button-man-level 10))
8940 ("\\<tex\\>" (gnus-button-tex-level 10))))
8945 @item gnus-button-browse-level
8946 @vindex gnus-button-browse-level
8947 Controls the display of references to message IDs, mail addresses and
8948 news URLs. Related variables and functions include
8949 @code{gnus-button-url-regexp}, @code{browse-url}, and
8950 @code{browse-url-browser-function}.
8952 @item gnus-button-emacs-level
8953 @vindex gnus-button-emacs-level
8954 Controls the display of Emacs or Gnus references. Related functions are
8955 @code{gnus-button-handle-custom},
8956 @code{gnus-button-handle-describe-function},
8957 @code{gnus-button-handle-describe-variable},
8958 @code{gnus-button-handle-symbol},
8959 @code{gnus-button-handle-describe-key},
8960 @code{gnus-button-handle-apropos},
8961 @code{gnus-button-handle-apropos-command},
8962 @code{gnus-button-handle-apropos-variable},
8963 @code{gnus-button-handle-apropos-documentation}, and
8964 @code{gnus-button-handle-library}.
8966 @item gnus-button-man-level
8967 @vindex gnus-button-man-level
8968 Controls the display of references to (Unix) man pages.
8969 See @code{gnus-button-man-handler}.
8971 @item gnus-button-message-level
8972 @vindex gnus-button-message-level
8973 Controls the display of message IDs, mail addresses and news URLs.
8974 Related variables and functions include
8975 @code{gnus-button-mid-or-mail-regexp},
8976 @code{gnus-button-prefer-mid-or-mail},
8977 @code{gnus-button-mid-or-mail-heuristic}, and
8978 @code{gnus-button-mid-or-mail-heuristic-alist}.
8980 @item gnus-button-tex-level
8981 @vindex gnus-button-tex-level
8982 Controls the display of references to @TeX{} or LaTeX stuff, e.g. for CTAN
8983 URLs. See the variables @code{gnus-ctan-url},
8984 @code{gnus-button-ctan-handler},
8985 @code{gnus-button-ctan-directory-regexp}, and
8986 @code{gnus-button-handle-ctan-bogus-regexp}.
8992 @subsection Article Date
8994 The date is most likely generated in some obscure timezone you've never
8995 heard of, so it's quite nice to be able to find out what the time was
8996 when the article was sent.
9001 @kindex W T u (Summary)
9002 @findex gnus-article-date-ut
9003 Display the date in UT (aka. GMT, aka ZULU)
9004 (@code{gnus-article-date-ut}).
9007 @kindex W T i (Summary)
9008 @findex gnus-article-date-iso8601
9010 Display the date in international format, aka. ISO 8601
9011 (@code{gnus-article-date-iso8601}).
9014 @kindex W T l (Summary)
9015 @findex gnus-article-date-local
9016 Display the date in the local timezone (@code{gnus-article-date-local}).
9019 @kindex W T p (Summary)
9020 @findex gnus-article-date-english
9021 Display the date in a format that's easily pronounceable in English
9022 (@code{gnus-article-date-english}).
9025 @kindex W T s (Summary)
9026 @vindex gnus-article-time-format
9027 @findex gnus-article-date-user
9028 @findex format-time-string
9029 Display the date using a user-defined format
9030 (@code{gnus-article-date-user}). The format is specified by the
9031 @code{gnus-article-time-format} variable, and is a string that's passed
9032 to @code{format-time-string}. See the documentation of that variable
9033 for a list of possible format specs.
9036 @kindex W T e (Summary)
9037 @findex gnus-article-date-lapsed
9038 @findex gnus-start-date-timer
9039 @findex gnus-stop-date-timer
9040 Say how much time has elapsed between the article was posted and now
9041 (@code{gnus-article-date-lapsed}). It looks something like:
9044 X-Sent: 6 weeks, 4 days, 1 hour, 3 minutes, 8 seconds ago
9047 @vindex gnus-article-date-lapsed-new-header
9048 The value of @code{gnus-article-date-lapsed-new-header} determines
9049 whether this header will just be added below the old Date one, or will
9052 An advantage of using Gnus to read mail is that it converts simple bugs
9053 into wonderful absurdities.
9055 If you want to have this line updated continually, you can put
9058 (gnus-start-date-timer)
9061 in your @file{~/.gnus.el} file, or you can run it off of some hook. If
9062 you want to stop the timer, you can use the @code{gnus-stop-date-timer}
9066 @kindex W T o (Summary)
9067 @findex gnus-article-date-original
9068 Display the original date (@code{gnus-article-date-original}). This can
9069 be useful if you normally use some other conversion function and are
9070 worried that it might be doing something totally wrong. Say, claiming
9071 that the article was posted in 1854. Although something like that is
9072 @emph{totally} impossible. Don't you trust me? *titter*
9076 @xref{Customizing Articles}, for how to display the date in your
9077 preferred format automatically.
9080 @node Article Display
9081 @subsection Article Display
9086 These commands add various frivolous display gimmicks to the article
9087 buffer in Emacs versions that support them.
9089 @code{X-Face} headers are small black-and-white images supplied by the
9090 message headers (@pxref{X-Face}).
9092 @code{Face} headers are small colored images supplied by the message
9093 headers (@pxref{Face}).
9095 Smileys are those little @samp{:-)} symbols that people like to litter
9096 their messages with (@pxref{Smileys}).
9098 Picons, on the other hand, reside on your own system, and Gnus will
9099 try to match the headers to what you have (@pxref{Picons}).
9101 All these functions are toggles---if the elements already exist,
9106 @kindex W D x (Summary)
9107 @findex gnus-article-display-x-face
9108 Display an @code{X-Face} in the @code{From} header.
9109 (@code{gnus-article-display-x-face}).
9112 @kindex W D d (Summary)
9113 @findex gnus-article-display-face
9114 Display a @code{Face} in the @code{From} header.
9115 (@code{gnus-article-display-face}).
9118 @kindex W D s (Summary)
9119 @findex gnus-treat-smiley
9120 Display smileys (@code{gnus-treat-smiley}).
9123 @kindex W D f (Summary)
9124 @findex gnus-treat-from-picon
9125 Piconify the @code{From} header (@code{gnus-treat-from-picon}).
9128 @kindex W D m (Summary)
9129 @findex gnus-treat-mail-picon
9130 Piconify all mail headers (i. e., @code{Cc}, @code{To})
9131 (@code{gnus-treat-mail-picon}).
9134 @kindex W D n (Summary)
9135 @findex gnus-treat-newsgroups-picon
9136 Piconify all news headers (i. e., @code{Newsgroups} and
9137 @code{Followup-To}) (@code{gnus-treat-newsgroups-picon}).
9140 @kindex W D D (Summary)
9141 @findex gnus-article-remove-images
9142 Remove all images from the article buffer
9143 (@code{gnus-article-remove-images}).
9149 @node Article Signature
9150 @subsection Article Signature
9152 @cindex article signature
9154 @vindex gnus-signature-separator
9155 Each article is divided into two parts---the head and the body. The
9156 body can be divided into a signature part and a text part. The variable
9157 that says what is to be considered a signature is
9158 @code{gnus-signature-separator}. This is normally the standard
9159 @samp{^-- $} as mandated by son-of-RFC 1036. However, many people use
9160 non-standard signature separators, so this variable can also be a list
9161 of regular expressions to be tested, one by one. (Searches are done
9162 from the end of the body towards the beginning.) One likely value is:
9165 (setq gnus-signature-separator
9166 '("^-- $" ; @r{The standard}
9167 "^-- *$" ; @r{A common mangling}
9168 "^-------*$" ; @r{Many people just use a looong}
9169 ; @r{line of dashes. Shame!}
9170 "^ *--------*$" ; @r{Double-shame!}
9171 "^________*$" ; @r{Underscores are also popular}
9172 "^========*$")) ; @r{Pervert!}
9175 The more permissive you are, the more likely it is that you'll get false
9178 @vindex gnus-signature-limit
9179 @code{gnus-signature-limit} provides a limit to what is considered a
9180 signature when displaying articles.
9184 If it is an integer, no signature may be longer (in characters) than
9187 If it is a floating point number, no signature may be longer (in lines)
9190 If it is a function, the function will be called without any parameters,
9191 and if it returns @code{nil}, there is no signature in the buffer.
9193 If it is a string, it will be used as a regexp. If it matches, the text
9194 in question is not a signature.
9197 This variable can also be a list where the elements may be of the types
9198 listed above. Here's an example:
9201 (setq gnus-signature-limit
9202 '(200.0 "^---*Forwarded article"))
9205 This means that if there are more than 200 lines after the signature
9206 separator, or the text after the signature separator is matched by
9207 the regular expression @samp{^---*Forwarded article}, then it isn't a
9208 signature after all.
9211 @node Article Miscellanea
9212 @subsection Article Miscellanea
9216 @kindex A t (Summary)
9217 @findex gnus-article-babel
9218 Translate the article from one language to another
9219 (@code{gnus-article-babel}).
9225 @section MIME Commands
9226 @cindex MIME decoding
9228 @cindex viewing attachments
9230 The following commands all understand the numerical prefix. For
9231 instance, @kbd{3 b} means ``view the third @acronym{MIME} part''.
9237 @kindex K v (Summary)
9238 View the @acronym{MIME} part.
9241 @kindex K o (Summary)
9242 Save the @acronym{MIME} part.
9245 @kindex K c (Summary)
9246 Copy the @acronym{MIME} part.
9249 @kindex K e (Summary)
9250 View the @acronym{MIME} part externally.
9253 @kindex K i (Summary)
9254 View the @acronym{MIME} part internally.
9257 @kindex K | (Summary)
9258 Pipe the @acronym{MIME} part to an external command.
9261 The rest of these @acronym{MIME} commands do not use the numerical prefix in
9266 @kindex K b (Summary)
9267 Make all the @acronym{MIME} parts have buttons in front of them. This is
9268 mostly useful if you wish to save (or perform other actions) on inlined
9272 @kindex K m (Summary)
9273 @findex gnus-summary-repair-multipart
9274 Some multipart messages are transmitted with missing or faulty headers.
9275 This command will attempt to ``repair'' these messages so that they can
9276 be viewed in a more pleasant manner
9277 (@code{gnus-summary-repair-multipart}).
9280 @kindex X m (Summary)
9281 @findex gnus-summary-save-parts
9282 Save all parts matching a @acronym{MIME} type to a directory
9283 (@code{gnus-summary-save-parts}). Understands the process/prefix
9284 convention (@pxref{Process/Prefix}).
9287 @kindex M-t (Summary)
9288 @findex gnus-summary-toggle-display-buttonized
9289 Toggle the buttonized display of the article buffer
9290 (@code{gnus-summary-toggle-display-buttonized}).
9293 @kindex W M w (Summary)
9294 @findex gnus-article-decode-mime-words
9295 Decode RFC 2047-encoded words in the article headers
9296 (@code{gnus-article-decode-mime-words}).
9299 @kindex W M c (Summary)
9300 @findex gnus-article-decode-charset
9301 Decode encoded article bodies as well as charsets
9302 (@code{gnus-article-decode-charset}).
9304 This command looks in the @code{Content-Type} header to determine the
9305 charset. If there is no such header in the article, you can give it a
9306 prefix, which will prompt for the charset to decode as. In regional
9307 groups where people post using some common encoding (but do not
9308 include @acronym{MIME} headers), you can set the @code{charset} group/topic
9309 parameter to the required charset (@pxref{Group Parameters}).
9312 @kindex W M v (Summary)
9313 @findex gnus-mime-view-all-parts
9314 View all the @acronym{MIME} parts in the current article
9315 (@code{gnus-mime-view-all-parts}).
9322 @item gnus-ignored-mime-types
9323 @vindex gnus-ignored-mime-types
9324 This is a list of regexps. @acronym{MIME} types that match a regexp from
9325 this list will be completely ignored by Gnus. The default value is
9328 To have all Vcards be ignored, you'd say something like this:
9331 (setq gnus-ignored-mime-types
9335 @item gnus-article-loose-mime
9336 @vindex gnus-article-loose-mime
9337 If non-@code{nil}, Gnus won't require the @samp{MIME-Version} header
9338 before interpreting the message as a @acronym{MIME} message. This helps
9339 when reading messages from certain broken mail user agents. The
9340 default is @code{nil}.
9342 @item gnus-article-emulate-mime
9343 @vindex gnus-article-emulate-mime
9344 There are other, non-@acronym{MIME} encoding methods used. The most common
9345 is @samp{uuencode}, but yEncode is also getting to be popular. If
9346 this variable is non-@code{nil}, Gnus will look in message bodies to
9347 see if it finds these encodings, and if so, it'll run them through the
9348 Gnus @acronym{MIME} machinery. The default is @code{t}.
9350 @item gnus-unbuttonized-mime-types
9351 @vindex gnus-unbuttonized-mime-types
9352 This is a list of regexps. @acronym{MIME} types that match a regexp from
9353 this list won't have @acronym{MIME} buttons inserted unless they aren't
9354 displayed or this variable is overridden by
9355 @code{gnus-buttonized-mime-types}. The default value is
9356 @code{(".*/.*")}. This variable is only used when
9357 @code{gnus-inhibit-mime-unbuttonizing} is @code{nil}.
9359 @item gnus-buttonized-mime-types
9360 @vindex gnus-buttonized-mime-types
9361 This is a list of regexps. @acronym{MIME} types that match a regexp from
9362 this list will have @acronym{MIME} buttons inserted unless they aren't
9363 displayed. This variable overrides
9364 @code{gnus-unbuttonized-mime-types}. The default value is @code{nil}.
9365 This variable is only used when @code{gnus-inhibit-mime-unbuttonizing}
9368 To see e.g. security buttons but no other buttons, you could set this
9369 variable to @code{("multipart/signed")} and leave
9370 @code{gnus-unbuttonized-mime-types} at the default value.
9372 @item gnus-inhibit-mime-unbuttonizing
9373 @vindex gnus-inhibit-mime-unbuttonizing
9374 If this is non-@code{nil}, then all @acronym{MIME} parts get buttons. The
9375 default value is @code{nil}.
9377 @item gnus-article-mime-part-function
9378 @vindex gnus-article-mime-part-function
9379 For each @acronym{MIME} part, this function will be called with the @acronym{MIME}
9380 handle as the parameter. The function is meant to be used to allow
9381 users to gather information from the article (e. g., add Vcard info to
9382 the bbdb database) or to do actions based on parts (e. g., automatically
9383 save all jpegs into some directory).
9385 Here's an example function the does the latter:
9388 (defun my-save-all-jpeg-parts (handle)
9389 (when (equal (car (mm-handle-type handle)) "image/jpeg")
9391 (insert (mm-get-part handle))
9392 (write-region (point-min) (point-max)
9393 (read-file-name "Save jpeg to: ")))))
9394 (setq gnus-article-mime-part-function
9395 'my-save-all-jpeg-parts)
9398 @vindex gnus-mime-multipart-functions
9399 @item gnus-mime-multipart-functions
9400 Alist of @acronym{MIME} multipart types and functions to handle them.
9402 @vindex gnus-mime-display-multipart-alternative-as-mixed
9403 @item gnus-mime-display-multipart-alternative-as-mixed
9404 Display "multipart/alternative" parts as "multipart/mixed".
9406 @vindex gnus-mime-display-multipart-related-as-mixed
9407 @item gnus-mime-display-multipart-related-as-mixed
9408 Display "multipart/related" parts as "multipart/mixed".
9410 If displaying "text/html" is discouraged, see
9411 @code{mm-discouraged-alternatives} in @ref{Display Customization,
9412 Display Customization, , emacs-mime, Emacs-Mime Manual}. Images or
9413 other material inside a "multipart/related" part might be overlooked
9414 when this variable is @code{nil}.
9416 @vindex gnus-mime-display-multipart-as-mixed
9417 @item gnus-mime-display-multipart-as-mixed
9418 Display "multipart" parts as "multipart/mixed". If @code{t}, it
9419 overrides @code{nil} values of
9420 @code{gnus-mime-display-multipart-alternative-as-mixed} and
9421 @code{gnus-mime-display-multipart-related-as-mixed}.
9423 @vindex mm-file-name-rewrite-functions
9424 @item mm-file-name-rewrite-functions
9425 List of functions used for rewriting file names of @acronym{MIME} parts.
9426 Each function takes a file name as input and returns a file name.
9428 Ready-made functions include@*
9429 @code{mm-file-name-delete-whitespace},
9430 @code{mm-file-name-trim-whitespace},
9431 @code{mm-file-name-collapse-whitespace}, and
9432 @code{mm-file-name-replace-whitespace}. The later uses the value of
9433 the variable @code{mm-file-name-replace-whitespace} to replace each
9434 whitespace character in a file name with that string; default value
9435 is @code{"_"} (a single underscore).
9436 @findex mm-file-name-delete-whitespace
9437 @findex mm-file-name-trim-whitespace
9438 @findex mm-file-name-collapse-whitespace
9439 @findex mm-file-name-replace-whitespace
9440 @vindex mm-file-name-replace-whitespace
9442 The standard functions @code{capitalize}, @code{downcase},
9443 @code{upcase}, and @code{upcase-initials} may be useful, too.
9445 Everybody knows that whitespace characters in file names are evil,
9446 except those who don't know. If you receive lots of attachments from
9447 such unenlightened users, you can make live easier by adding
9450 (setq mm-file-name-rewrite-functions
9451 '(mm-file-name-trim-whitespace
9452 mm-file-name-collapse-whitespace
9453 mm-file-name-replace-whitespace))
9457 to your @file{~/.gnus.el} file.
9466 People use different charsets, and we have @acronym{MIME} to let us know what
9467 charsets they use. Or rather, we wish we had. Many people use
9468 newsreaders and mailers that do not understand or use @acronym{MIME}, and
9469 just send out messages without saying what character sets they use. To
9470 help a bit with this, some local news hierarchies have policies that say
9471 what character set is the default. For instance, the @samp{fj}
9472 hierarchy uses @code{iso-2022-jp-2}.
9474 @vindex gnus-group-charset-alist
9475 This knowledge is encoded in the @code{gnus-group-charset-alist}
9476 variable, which is an alist of regexps (use the first item to match full
9477 group names) and default charsets to be used when reading these groups.
9479 @vindex gnus-newsgroup-ignored-charsets
9480 In addition, some people do use soi-disant @acronym{MIME}-aware agents that
9481 aren't. These blithely mark messages as being in @code{iso-8859-1}
9482 even if they really are in @code{koi-8}. To help here, the
9483 @code{gnus-newsgroup-ignored-charsets} variable can be used. The
9484 charsets that are listed here will be ignored. The variable can be
9485 set on a group-by-group basis using the group parameters (@pxref{Group
9486 Parameters}). The default value is @code{(unknown-8bit x-unknown)},
9487 which includes values some agents insist on having in there.
9489 @vindex gnus-group-posting-charset-alist
9490 When posting, @code{gnus-group-posting-charset-alist} is used to
9491 determine which charsets should not be encoded using the @acronym{MIME}
9492 encodings. For instance, some hierarchies discourage using
9493 quoted-printable header encoding.
9495 This variable is an alist of regexps and permitted unencoded charsets
9496 for posting. Each element of the alist has the form @code{(}@var{test
9497 header body-list}@code{)}, where:
9501 is either a regular expression matching the newsgroup header or a
9504 is the charset which may be left unencoded in the header (@code{nil}
9505 means encode all charsets),
9507 is a list of charsets which may be encoded using 8bit content-transfer
9508 encoding in the body, or one of the special values @code{nil} (always
9509 encode using quoted-printable) or @code{t} (always use 8bit).
9516 @cindex coding system aliases
9517 @cindex preferred charset
9519 @xref{Encoding Customization, , Encoding Customization, emacs-mime,
9520 The Emacs MIME Manual}, for additional variables that control which
9521 MIME charsets are used when sending messages.
9523 Other charset tricks that may be useful, although not Gnus-specific:
9525 If there are several @acronym{MIME} charsets that encode the same Emacs
9526 charset, you can choose what charset to use by saying the following:
9529 (put-charset-property 'cyrillic-iso8859-5
9530 'preferred-coding-system 'koi8-r)
9533 This means that Russian will be encoded using @code{koi8-r} instead of
9534 the default @code{iso-8859-5} @acronym{MIME} charset.
9536 If you want to read messages in @code{koi8-u}, you can cheat and say
9539 (define-coding-system-alias 'koi8-u 'koi8-r)
9542 This will almost do the right thing.
9544 And finally, to read charsets like @code{windows-1251}, you can say
9548 (codepage-setup 1251)
9549 (define-coding-system-alias 'windows-1251 'cp1251)
9553 @node Article Commands
9554 @section Article Commands
9561 @kindex A P (Summary)
9562 @vindex gnus-ps-print-hook
9563 @findex gnus-summary-print-article
9564 Generate and print a PostScript image of the article buffer
9565 (@code{gnus-summary-print-article}). @code{gnus-ps-print-hook} will
9566 be run just before printing the buffer. An alternative way to print
9567 article is to use Muttprint (@pxref{Saving Articles}).
9572 @node Summary Sorting
9573 @section Summary Sorting
9574 @cindex summary sorting
9576 You can have the summary buffer sorted in various ways, even though I
9577 can't really see why you'd want that.
9582 @kindex C-c C-s C-n (Summary)
9583 @findex gnus-summary-sort-by-number
9584 Sort by article number (@code{gnus-summary-sort-by-number}).
9587 @kindex C-c C-s C-a (Summary)
9588 @findex gnus-summary-sort-by-author
9589 Sort by author (@code{gnus-summary-sort-by-author}).
9592 @kindex C-c C-s C-t (Summary)
9593 @findex gnus-summary-sort-by-recipient
9594 Sort by recipient (@code{gnus-summary-sort-by-recipient}).
9597 @kindex C-c C-s C-s (Summary)
9598 @findex gnus-summary-sort-by-subject
9599 Sort by subject (@code{gnus-summary-sort-by-subject}).
9602 @kindex C-c C-s C-d (Summary)
9603 @findex gnus-summary-sort-by-date
9604 Sort by date (@code{gnus-summary-sort-by-date}).
9607 @kindex C-c C-s C-l (Summary)
9608 @findex gnus-summary-sort-by-lines
9609 Sort by lines (@code{gnus-summary-sort-by-lines}).
9612 @kindex C-c C-s C-c (Summary)
9613 @findex gnus-summary-sort-by-chars
9614 Sort by article length (@code{gnus-summary-sort-by-chars}).
9617 @kindex C-c C-s C-i (Summary)
9618 @findex gnus-summary-sort-by-score
9619 Sort by score (@code{gnus-summary-sort-by-score}).
9622 @kindex C-c C-s C-r (Summary)
9623 @findex gnus-summary-sort-by-random
9624 Randomize (@code{gnus-summary-sort-by-random}).
9627 @kindex C-c C-s C-o (Summary)
9628 @findex gnus-summary-sort-by-original
9629 Sort using the default sorting method
9630 (@code{gnus-summary-sort-by-original}).
9633 These functions will work both when you use threading and when you don't
9634 use threading. In the latter case, all summary lines will be sorted,
9635 line by line. In the former case, sorting will be done on a
9636 root-by-root basis, which might not be what you were looking for. To
9637 toggle whether to use threading, type @kbd{T T} (@pxref{Thread
9641 @node Finding the Parent
9642 @section Finding the Parent
9643 @cindex parent articles
9644 @cindex referring articles
9649 @findex gnus-summary-refer-parent-article
9650 If you'd like to read the parent of the current article, and it is not
9651 displayed in the summary buffer, you might still be able to. That is,
9652 if the current group is fetched by @acronym{NNTP}, the parent hasn't expired
9653 and the @code{References} in the current article are not mangled, you
9654 can just press @kbd{^} or @kbd{A r}
9655 (@code{gnus-summary-refer-parent-article}). If everything goes well,
9656 you'll get the parent. If the parent is already displayed in the
9657 summary buffer, point will just move to this article.
9659 If given a positive numerical prefix, fetch that many articles back into
9660 the ancestry. If given a negative numerical prefix, fetch just that
9661 ancestor. So if you say @kbd{3 ^}, gnus will fetch the parent, the
9662 grandparent and the grandgrandparent of the current article. If you say
9663 @kbd{-3 ^}, gnus will only fetch the grandgrandparent of the current
9667 @findex gnus-summary-refer-references
9668 @kindex A R (Summary)
9669 Fetch all articles mentioned in the @code{References} header of the
9670 article (@code{gnus-summary-refer-references}).
9673 @findex gnus-summary-refer-thread
9674 @kindex A T (Summary)
9675 Display the full thread where the current article appears
9676 (@code{gnus-summary-refer-thread}). This command has to fetch all the
9677 headers in the current group to work, so it usually takes a while. If
9678 you do it often, you may consider setting @code{gnus-fetch-old-headers}
9679 to @code{invisible} (@pxref{Filling In Threads}). This won't have any
9680 visible effects normally, but it'll make this command work a whole lot
9681 faster. Of course, it'll make group entry somewhat slow.
9683 @vindex gnus-refer-thread-limit
9684 The @code{gnus-refer-thread-limit} variable says how many old (i. e.,
9685 articles before the first displayed in the current group) headers to
9686 fetch when doing this command. The default is 200. If @code{t}, all
9687 the available headers will be fetched. This variable can be overridden
9688 by giving the @kbd{A T} command a numerical prefix.
9691 @findex gnus-summary-refer-article
9692 @kindex M-^ (Summary)
9694 @cindex fetching by Message-ID
9695 You can also ask the @acronym{NNTP} server for an arbitrary article, no
9696 matter what group it belongs to. @kbd{M-^}
9697 (@code{gnus-summary-refer-article}) will ask you for a
9698 @code{Message-ID}, which is one of those long, hard-to-read thingies
9699 that look something like @samp{<38o6up$6f2@@hymir.ifi.uio.no>}. You
9700 have to get it all exactly right. No fuzzy searches, I'm afraid.
9703 The current select method will be used when fetching by
9704 @code{Message-ID} from non-news select method, but you can override this
9705 by giving this command a prefix.
9707 @vindex gnus-refer-article-method
9708 If the group you are reading is located on a back end that does not
9709 support fetching by @code{Message-ID} very well (like @code{nnspool}),
9710 you can set @code{gnus-refer-article-method} to an @acronym{NNTP} method. It
9711 would, perhaps, be best if the @acronym{NNTP} server you consult is the one
9712 updating the spool you are reading from, but that's not really
9715 It can also be a list of select methods, as well as the special symbol
9716 @code{current}, which means to use the current select method. If it
9717 is a list, Gnus will try all the methods in the list until it finds a
9720 Here's an example setting that will first try the current method, and
9721 then ask Google if that fails:
9724 (setq gnus-refer-article-method
9726 (nnweb "google" (nnweb-type google))))
9729 Most of the mail back ends support fetching by @code{Message-ID}, but
9730 do not do a particularly excellent job at it. That is, @code{nnmbox},
9731 @code{nnbabyl}, @code{nnmaildir}, @code{nnml}, are able to locate
9732 articles from any groups, while @code{nnfolder}, and @code{nnimap} are
9733 only able to locate articles that have been posted to the current
9734 group. (Anything else would be too time consuming.) @code{nnmh} does
9735 not support this at all.
9738 @node Alternative Approaches
9739 @section Alternative Approaches
9741 Different people like to read news using different methods. This being
9742 gnus, we offer a small selection of minor modes for the summary buffers.
9745 * Pick and Read:: First mark articles and then read them.
9746 * Binary Groups:: Auto-decode all articles.
9751 @subsection Pick and Read
9752 @cindex pick and read
9754 Some newsreaders (like @code{nn} and, uhm, @code{Netnews} on VM/CMS) use
9755 a two-phased reading interface. The user first marks in a summary
9756 buffer the articles she wants to read. Then she starts reading the
9757 articles with just an article buffer displayed.
9759 @findex gnus-pick-mode
9760 @kindex M-x gnus-pick-mode
9761 Gnus provides a summary buffer minor mode that allows
9762 this---@code{gnus-pick-mode}. This basically means that a few process
9763 mark commands become one-keystroke commands to allow easy marking, and
9764 it provides one additional command for switching to the summary buffer.
9766 Here are the available keystrokes when using pick mode:
9771 @findex gnus-pick-article-or-thread
9772 Pick the article or thread on the current line
9773 (@code{gnus-pick-article-or-thread}). If the variable
9774 @code{gnus-thread-hide-subtree} is true, then this key selects the
9775 entire thread when used at the first article of the thread. Otherwise,
9776 it selects just the article. If given a numerical prefix, go to that
9777 thread or article and pick it. (The line number is normally displayed
9778 at the beginning of the summary pick lines.)
9781 @kindex SPACE (Pick)
9782 @findex gnus-pick-next-page
9783 Scroll the summary buffer up one page (@code{gnus-pick-next-page}). If
9784 at the end of the buffer, start reading the picked articles.
9788 @findex gnus-pick-unmark-article-or-thread.
9789 Unpick the thread or article
9790 (@code{gnus-pick-unmark-article-or-thread}). If the variable
9791 @code{gnus-thread-hide-subtree} is true, then this key unpicks the
9792 thread if used at the first article of the thread. Otherwise it unpicks
9793 just the article. You can give this key a numerical prefix to unpick
9794 the thread or article at that line.
9798 @findex gnus-pick-start-reading
9799 @vindex gnus-pick-display-summary
9800 Start reading the picked articles (@code{gnus-pick-start-reading}). If
9801 given a prefix, mark all unpicked articles as read first. If
9802 @code{gnus-pick-display-summary} is non-@code{nil}, the summary buffer
9803 will still be visible when you are reading.
9807 All the normal summary mode commands are still available in the
9808 pick-mode, with the exception of @kbd{u}. However @kbd{!} is available
9809 which is mapped to the same function
9810 @code{gnus-summary-tick-article-forward}.
9812 If this sounds like a good idea to you, you could say:
9815 (add-hook 'gnus-summary-mode-hook 'gnus-pick-mode)
9818 @vindex gnus-pick-mode-hook
9819 @code{gnus-pick-mode-hook} is run in pick minor mode buffers.
9821 @vindex gnus-mark-unpicked-articles-as-read
9822 If @code{gnus-mark-unpicked-articles-as-read} is non-@code{nil}, mark
9823 all unpicked articles as read. The default is @code{nil}.
9825 @vindex gnus-summary-pick-line-format
9826 The summary line format in pick mode is slightly different from the
9827 standard format. At the beginning of each line the line number is
9828 displayed. The pick mode line format is controlled by the
9829 @code{gnus-summary-pick-line-format} variable (@pxref{Formatting
9830 Variables}). It accepts the same format specs that
9831 @code{gnus-summary-line-format} does (@pxref{Summary Buffer Lines}).
9835 @subsection Binary Groups
9836 @cindex binary groups
9838 @findex gnus-binary-mode
9839 @kindex M-x gnus-binary-mode
9840 If you spend much time in binary groups, you may grow tired of hitting
9841 @kbd{X u}, @kbd{n}, @kbd{RET} all the time. @kbd{M-x gnus-binary-mode}
9842 is a minor mode for summary buffers that makes all ordinary Gnus article
9843 selection functions uudecode series of articles and display the result
9844 instead of just displaying the articles the normal way.
9847 @findex gnus-binary-show-article
9848 The only way, in fact, to see the actual articles is the @kbd{g}
9849 command, when you have turned on this mode
9850 (@code{gnus-binary-show-article}).
9852 @vindex gnus-binary-mode-hook
9853 @code{gnus-binary-mode-hook} is called in binary minor mode buffers.
9857 @section Tree Display
9860 @vindex gnus-use-trees
9861 If you don't like the normal gnus summary display, you might try setting
9862 @code{gnus-use-trees} to @code{t}. This will create (by default) an
9863 additional @dfn{tree buffer}. You can execute all summary mode commands
9866 There are a few variables to customize the tree display, of course:
9869 @item gnus-tree-mode-hook
9870 @vindex gnus-tree-mode-hook
9871 A hook called in all tree mode buffers.
9873 @item gnus-tree-mode-line-format
9874 @vindex gnus-tree-mode-line-format
9875 A format string for the mode bar in the tree mode buffers (@pxref{Mode
9876 Line Formatting}). The default is @samp{Gnus: %%b %S %Z}. For a list
9877 of valid specs, @pxref{Summary Buffer Mode Line}.
9879 @item gnus-selected-tree-face
9880 @vindex gnus-selected-tree-face
9881 Face used for highlighting the selected article in the tree buffer. The
9882 default is @code{modeline}.
9884 @item gnus-tree-line-format
9885 @vindex gnus-tree-line-format
9886 A format string for the tree nodes. The name is a bit of a misnomer,
9887 though---it doesn't define a line, but just the node. The default value
9888 is @samp{%(%[%3,3n%]%)}, which displays the first three characters of
9889 the name of the poster. It is vital that all nodes are of the same
9890 length, so you @emph{must} use @samp{%4,4n}-like specifiers.
9896 The name of the poster.
9898 The @code{From} header.
9900 The number of the article.
9902 The opening bracket.
9904 The closing bracket.
9909 @xref{Formatting Variables}.
9911 Variables related to the display are:
9914 @item gnus-tree-brackets
9915 @vindex gnus-tree-brackets
9916 This is used for differentiating between ``real'' articles and
9917 ``sparse'' articles. The format is
9919 ((@var{real-open} . @var{real-close})
9920 (@var{sparse-open} . @var{sparse-close})
9921 (@var{dummy-open} . @var{dummy-close}))
9923 and the default is @code{((?[ . ?]) (?( . ?)) (?@{ . ?@}) (?< . ?>))}.
9925 @item gnus-tree-parent-child-edges
9926 @vindex gnus-tree-parent-child-edges
9927 This is a list that contains the characters used for connecting parent
9928 nodes to their children. The default is @code{(?- ?\\ ?|)}.
9932 @item gnus-tree-minimize-window
9933 @vindex gnus-tree-minimize-window
9934 If this variable is non-@code{nil}, gnus will try to keep the tree
9935 buffer as small as possible to allow more room for the other gnus
9936 windows. If this variable is a number, the tree buffer will never be
9937 higher than that number. The default is @code{t}. Note that if you
9938 have several windows displayed side-by-side in a frame and the tree
9939 buffer is one of these, minimizing the tree window will also resize all
9940 other windows displayed next to it.
9942 You may also wish to add the following hook to keep the window minimized
9946 (add-hook 'gnus-configure-windows-hook
9947 'gnus-tree-perhaps-minimize)
9950 @item gnus-generate-tree-function
9951 @vindex gnus-generate-tree-function
9952 @findex gnus-generate-horizontal-tree
9953 @findex gnus-generate-vertical-tree
9954 The function that actually generates the thread tree. Two predefined
9955 functions are available: @code{gnus-generate-horizontal-tree} and
9956 @code{gnus-generate-vertical-tree} (which is the default).
9960 Here's an example from a horizontal tree buffer:
9963 @{***@}-(***)-[odd]-[Gun]
9973 Here's the same thread displayed in a vertical tree buffer:
9978 |--------------------------\-----\-----\
9979 (***) [Bjo] [Gun] [Gun]
9981 [odd] [Jan] [odd] (***) [Jor]
9983 [Gun] [Eri] [Eri] [odd]
9989 If you're using horizontal trees, it might be nice to display the trees
9990 side-by-side with the summary buffer. You could add something like the
9991 following to your @file{~/.gnus.el} file:
9994 (setq gnus-use-trees t
9995 gnus-generate-tree-function 'gnus-generate-horizontal-tree
9996 gnus-tree-minimize-window nil)
9997 (gnus-add-configuration
10001 (summary 0.75 point)
10006 @xref{Window Layout}.
10009 @node Mail Group Commands
10010 @section Mail Group Commands
10011 @cindex mail group commands
10013 Some commands only make sense in mail groups. If these commands are
10014 invalid in the current group, they will raise a hell and let you know.
10016 All these commands (except the expiry and edit commands) use the
10017 process/prefix convention (@pxref{Process/Prefix}).
10022 @kindex B e (Summary)
10023 @findex gnus-summary-expire-articles
10024 Run all expirable articles in the current group through the expiry
10025 process (@code{gnus-summary-expire-articles}). That is, delete all
10026 expirable articles in the group that have been around for a while.
10027 (@pxref{Expiring Mail}).
10030 @kindex B C-M-e (Summary)
10031 @findex gnus-summary-expire-articles-now
10032 Delete all the expirable articles in the group
10033 (@code{gnus-summary-expire-articles-now}). This means that @strong{all}
10034 articles eligible for expiry in the current group will
10035 disappear forever into that big @file{/dev/null} in the sky.
10038 @kindex B DEL (Summary)
10039 @findex gnus-summary-delete-article
10040 @c @icon{gnus-summary-mail-delete}
10041 Delete the mail article. This is ``delete'' as in ``delete it from your
10042 disk forever and ever, never to return again.'' Use with caution.
10043 (@code{gnus-summary-delete-article}).
10046 @kindex B m (Summary)
10048 @findex gnus-summary-move-article
10049 @vindex gnus-preserve-marks
10050 Move the article from one mail group to another
10051 (@code{gnus-summary-move-article}). Marks will be preserved if
10052 @code{gnus-preserve-marks} is non-@code{nil} (which is the default).
10055 @kindex B c (Summary)
10057 @findex gnus-summary-copy-article
10058 @c @icon{gnus-summary-mail-copy}
10059 Copy the article from one group (mail group or not) to a mail group
10060 (@code{gnus-summary-copy-article}). Marks will be preserved if
10061 @code{gnus-preserve-marks} is non-@code{nil} (which is the default).
10064 @kindex B B (Summary)
10065 @cindex crosspost mail
10066 @findex gnus-summary-crosspost-article
10067 Crosspost the current article to some other group
10068 (@code{gnus-summary-crosspost-article}). This will create a new copy of
10069 the article in the other group, and the Xref headers of the article will
10070 be properly updated.
10073 @kindex B i (Summary)
10074 @findex gnus-summary-import-article
10075 Import an arbitrary file into the current mail newsgroup
10076 (@code{gnus-summary-import-article}). You will be prompted for a file
10077 name, a @code{From} header and a @code{Subject} header.
10080 @kindex B I (Summary)
10081 @findex gnus-summary-create-article
10082 Create an empty article in the current mail newsgroups
10083 (@code{gnus-summary-create-article}). You will be prompted for a
10084 @code{From} header and a @code{Subject} header.
10087 @kindex B r (Summary)
10088 @findex gnus-summary-respool-article
10089 @vindex gnus-summary-respool-default-method
10090 Respool the mail article (@code{gnus-summary-respool-article}).
10091 @code{gnus-summary-respool-default-method} will be used as the default
10092 select method when respooling. This variable is @code{nil} by default,
10093 which means that the current group select method will be used instead.
10094 Marks will be preserved if @code{gnus-preserve-marks} is non-@code{nil}
10095 (which is the default).
10099 @kindex B w (Summary)
10100 @kindex e (Summary)
10101 @findex gnus-summary-edit-article
10102 @kindex C-c C-c (Article)
10103 @findex gnus-summary-edit-article-done
10104 Edit the current article (@code{gnus-summary-edit-article}). To finish
10105 editing and make the changes permanent, type @kbd{C-c C-c}
10106 (@code{gnus-summary-edit-article-done}). If you give a prefix to the
10107 @kbd{C-c C-c} command, gnus won't re-highlight the article.
10110 @kindex B q (Summary)
10111 @findex gnus-summary-respool-query
10112 If you want to re-spool an article, you might be curious as to what group
10113 the article will end up in before you do the re-spooling. This command
10114 will tell you (@code{gnus-summary-respool-query}).
10117 @kindex B t (Summary)
10118 @findex gnus-summary-respool-trace
10119 Similarly, this command will display all fancy splitting patterns used
10120 when respooling, if any (@code{gnus-summary-respool-trace}).
10123 @kindex B p (Summary)
10124 @findex gnus-summary-article-posted-p
10125 Some people have a tendency to send you ``courtesy'' copies when they
10126 follow up to articles you have posted. These usually have a
10127 @code{Newsgroups} header in them, but not always. This command
10128 (@code{gnus-summary-article-posted-p}) will try to fetch the current
10129 article from your news server (or rather, from
10130 @code{gnus-refer-article-method} or @code{gnus-select-method}) and will
10131 report back whether it found the article or not. Even if it says that
10132 it didn't find the article, it may have been posted anyway---mail
10133 propagation is much faster than news propagation, and the news copy may
10134 just not have arrived yet.
10137 @kindex K E (Summary)
10138 @findex gnus-article-encrypt-body
10139 @vindex gnus-article-encrypt-protocol
10140 Encrypt the body of an article (@code{gnus-article-encrypt-body}).
10141 The body is encrypted with the encryption protocol specified by the
10142 variable @code{gnus-article-encrypt-protocol}.
10146 @vindex gnus-move-split-methods
10147 @cindex moving articles
10148 If you move (or copy) articles regularly, you might wish to have gnus
10149 suggest where to put the articles. @code{gnus-move-split-methods} is a
10150 variable that uses the same syntax as @code{gnus-split-methods}
10151 (@pxref{Saving Articles}). You may customize that variable to create
10152 suggestions you find reasonable. (Note that
10153 @code{gnus-move-split-methods} uses group names where
10154 @code{gnus-split-methods} uses file names.)
10157 (setq gnus-move-split-methods
10158 '(("^From:.*Lars Magne" "nnml:junk")
10159 ("^Subject:.*gnus" "nnfolder:important")
10160 (".*" "nnml:misc")))
10164 @node Various Summary Stuff
10165 @section Various Summary Stuff
10168 * Summary Group Information:: Information oriented commands.
10169 * Searching for Articles:: Multiple article commands.
10170 * Summary Generation Commands::
10171 * Really Various Summary Commands:: Those pesky non-conformant commands.
10175 @vindex gnus-summary-display-while-building
10176 @item gnus-summary-display-while-building
10177 If non-@code{nil}, show and update the summary buffer as it's being
10178 built. If @code{t}, update the buffer after every line is inserted.
10179 If the value is an integer, @var{n}, update the display every @var{n}
10180 lines. The default is @code{nil}.
10182 @vindex gnus-summary-display-arrow
10183 @item gnus-summary-display-arrow
10184 If non-@code{nil}, display an arrow in the fringe to indicate the
10187 @vindex gnus-summary-mode-hook
10188 @item gnus-summary-mode-hook
10189 This hook is called when creating a summary mode buffer.
10191 @vindex gnus-summary-generate-hook
10192 @item gnus-summary-generate-hook
10193 This is called as the last thing before doing the threading and the
10194 generation of the summary buffer. It's quite convenient for customizing
10195 the threading variables based on what data the newsgroup has. This hook
10196 is called from the summary buffer after most summary buffer variables
10199 @vindex gnus-summary-prepare-hook
10200 @item gnus-summary-prepare-hook
10201 It is called after the summary buffer has been generated. You might use
10202 it to, for instance, highlight lines or modify the look of the buffer in
10203 some other ungodly manner. I don't care.
10205 @vindex gnus-summary-prepared-hook
10206 @item gnus-summary-prepared-hook
10207 A hook called as the very last thing after the summary buffer has been
10210 @vindex gnus-summary-ignore-duplicates
10211 @item gnus-summary-ignore-duplicates
10212 When gnus discovers two articles that have the same @code{Message-ID},
10213 it has to do something drastic. No articles are allowed to have the
10214 same @code{Message-ID}, but this may happen when reading mail from some
10215 sources. Gnus allows you to customize what happens with this variable.
10216 If it is @code{nil} (which is the default), gnus will rename the
10217 @code{Message-ID} (for display purposes only) and display the article as
10218 any other article. If this variable is @code{t}, it won't display the
10219 article---it'll be as if it never existed.
10221 @vindex gnus-alter-articles-to-read-function
10222 @item gnus-alter-articles-to-read-function
10223 This function, which takes two parameters (the group name and the list
10224 of articles to be selected), is called to allow the user to alter the
10225 list of articles to be selected.
10227 For instance, the following function adds the list of cached articles to
10228 the list in one particular group:
10231 (defun my-add-cached-articles (group articles)
10232 (if (string= group "some.group")
10233 (append gnus-newsgroup-cached articles)
10237 @vindex gnus-newsgroup-variables
10238 @item gnus-newsgroup-variables
10239 A list of newsgroup (summary buffer) local variables, or cons of
10240 variables and their default expressions to be evalled (when the default
10241 values are not @code{nil}), that should be made global while the summary
10244 Note: The default expressions will be evaluated (using function
10245 @code{eval}) before assignment to the local variable rather than just
10246 assigned to it. If the default expression is the symbol @code{global},
10247 that symbol will not be evaluated but the global value of the local
10248 variable will be used instead.
10250 These variables can be used to set variables in the group parameters
10251 while still allowing them to affect operations done in other
10252 buffers. For example:
10255 (setq gnus-newsgroup-variables
10256 '(message-use-followup-to
10257 (gnus-visible-headers .
10258 "^From:\\|^Newsgroups:\\|^Subject:\\|^Date:\\|^To:")))
10261 Also @pxref{Group Parameters}.
10265 @node Summary Group Information
10266 @subsection Summary Group Information
10271 @kindex H f (Summary)
10272 @findex gnus-summary-fetch-faq
10273 @vindex gnus-group-faq-directory
10274 Try to fetch the @acronym{FAQ} (list of frequently asked questions)
10275 for the current group (@code{gnus-summary-fetch-faq}). Gnus will try
10276 to get the @acronym{FAQ} from @code{gnus-group-faq-directory}, which
10277 is usually a directory on a remote machine. This variable can also be
10278 a list of directories. In that case, giving a prefix to this command
10279 will allow you to choose between the various sites. @code{ange-ftp}
10280 or @code{efs} will probably be used for fetching the file.
10283 @kindex H d (Summary)
10284 @findex gnus-summary-describe-group
10285 Give a brief description of the current group
10286 (@code{gnus-summary-describe-group}). If given a prefix, force
10287 rereading the description from the server.
10290 @kindex H h (Summary)
10291 @findex gnus-summary-describe-briefly
10292 Give an extremely brief description of the most important summary
10293 keystrokes (@code{gnus-summary-describe-briefly}).
10296 @kindex H i (Summary)
10297 @findex gnus-info-find-node
10298 Go to the gnus info node (@code{gnus-info-find-node}).
10302 @node Searching for Articles
10303 @subsection Searching for Articles
10308 @kindex M-s (Summary)
10309 @findex gnus-summary-search-article-forward
10310 Search through all subsequent (raw) articles for a regexp
10311 (@code{gnus-summary-search-article-forward}).
10314 @kindex M-r (Summary)
10315 @findex gnus-summary-search-article-backward
10316 Search through all previous (raw) articles for a regexp
10317 (@code{gnus-summary-search-article-backward}).
10320 @kindex & (Summary)
10321 @findex gnus-summary-execute-command
10322 This command will prompt you for a header, a regular expression to match
10323 on this field, and a command to be executed if the match is made
10324 (@code{gnus-summary-execute-command}). If the header is an empty
10325 string, the match is done on the entire article. If given a prefix,
10326 search backward instead.
10328 For instance, @kbd{& RET some.*string RET #} will put the process mark on
10329 all articles that have heads or bodies that match @samp{some.*string}.
10332 @kindex M-& (Summary)
10333 @findex gnus-summary-universal-argument
10334 Perform any operation on all articles that have been marked with
10335 the process mark (@code{gnus-summary-universal-argument}).
10338 @node Summary Generation Commands
10339 @subsection Summary Generation Commands
10344 @kindex Y g (Summary)
10345 @findex gnus-summary-prepare
10346 Regenerate the current summary buffer (@code{gnus-summary-prepare}).
10349 @kindex Y c (Summary)
10350 @findex gnus-summary-insert-cached-articles
10351 Pull all cached articles (for the current group) into the summary buffer
10352 (@code{gnus-summary-insert-cached-articles}).
10355 @kindex Y d (Summary)
10356 @findex gnus-summary-insert-dormant-articles
10357 Pull all dormant articles (for the current group) into the summary buffer
10358 (@code{gnus-summary-insert-dormant-articles}).
10363 @node Really Various Summary Commands
10364 @subsection Really Various Summary Commands
10370 @kindex C-d (Summary)
10371 @kindex A D (Summary)
10372 @findex gnus-summary-enter-digest-group
10373 If the current article is a collection of other articles (for instance,
10374 a digest), you might use this command to enter a group based on the that
10375 article (@code{gnus-summary-enter-digest-group}). Gnus will try to
10376 guess what article type is currently displayed unless you give a prefix
10377 to this command, which forces a ``digest'' interpretation. Basically,
10378 whenever you see a message that is a collection of other messages of
10379 some format, you @kbd{C-d} and read these messages in a more convenient
10383 @kindex C-M-d (Summary)
10384 @findex gnus-summary-read-document
10385 This command is very similar to the one above, but lets you gather
10386 several documents into one biiig group
10387 (@code{gnus-summary-read-document}). It does this by opening several
10388 @code{nndoc} groups for each document, and then opening an
10389 @code{nnvirtual} group on top of these @code{nndoc} groups. This
10390 command understands the process/prefix convention
10391 (@pxref{Process/Prefix}).
10394 @kindex C-t (Summary)
10395 @findex gnus-summary-toggle-truncation
10396 Toggle truncation of summary lines
10397 (@code{gnus-summary-toggle-truncation}). This will probably confuse the
10398 line centering function in the summary buffer, so it's not a good idea
10399 to have truncation switched off while reading articles.
10402 @kindex = (Summary)
10403 @findex gnus-summary-expand-window
10404 Expand the summary buffer window (@code{gnus-summary-expand-window}).
10405 If given a prefix, force an @code{article} window configuration.
10408 @kindex C-M-e (Summary)
10409 @findex gnus-summary-edit-parameters
10410 Edit the group parameters (@pxref{Group Parameters}) of the current
10411 group (@code{gnus-summary-edit-parameters}).
10414 @kindex C-M-a (Summary)
10415 @findex gnus-summary-customize-parameters
10416 Customize the group parameters (@pxref{Group Parameters}) of the current
10417 group (@code{gnus-summary-customize-parameters}).
10422 @node Exiting the Summary Buffer
10423 @section Exiting the Summary Buffer
10424 @cindex summary exit
10425 @cindex exiting groups
10427 Exiting from the summary buffer will normally update all info on the
10428 group and return you to the group buffer.
10435 @kindex Z Z (Summary)
10436 @kindex Z Q (Summary)
10437 @kindex q (Summary)
10438 @findex gnus-summary-exit
10439 @vindex gnus-summary-exit-hook
10440 @vindex gnus-summary-prepare-exit-hook
10441 @vindex gnus-group-no-more-groups-hook
10442 @c @icon{gnus-summary-exit}
10443 Exit the current group and update all information on the group
10444 (@code{gnus-summary-exit}). @code{gnus-summary-prepare-exit-hook} is
10445 called before doing much of the exiting, which calls
10446 @code{gnus-summary-expire-articles} by default.
10447 @code{gnus-summary-exit-hook} is called after finishing the exit
10448 process. @code{gnus-group-no-more-groups-hook} is run when returning to
10449 group mode having no more (unread) groups.
10453 @kindex Z E (Summary)
10454 @kindex Q (Summary)
10455 @findex gnus-summary-exit-no-update
10456 Exit the current group without updating any information on the group
10457 (@code{gnus-summary-exit-no-update}).
10461 @kindex Z c (Summary)
10462 @kindex c (Summary)
10463 @findex gnus-summary-catchup-and-exit
10464 @c @icon{gnus-summary-catchup-and-exit}
10465 Mark all unticked articles in the group as read and then exit
10466 (@code{gnus-summary-catchup-and-exit}).
10469 @kindex Z C (Summary)
10470 @findex gnus-summary-catchup-all-and-exit
10471 Mark all articles, even the ticked ones, as read and then exit
10472 (@code{gnus-summary-catchup-all-and-exit}).
10475 @kindex Z n (Summary)
10476 @findex gnus-summary-catchup-and-goto-next-group
10477 Mark all articles as read and go to the next group
10478 (@code{gnus-summary-catchup-and-goto-next-group}).
10482 @kindex Z R (Summary)
10483 @kindex C-x C-s (Summary)
10484 @findex gnus-summary-reselect-current-group
10485 Exit this group, and then enter it again
10486 (@code{gnus-summary-reselect-current-group}). If given a prefix, select
10487 all articles, both read and unread.
10491 @kindex Z G (Summary)
10492 @kindex M-g (Summary)
10493 @findex gnus-summary-rescan-group
10494 @c @icon{gnus-summary-mail-get}
10495 Exit the group, check for new articles in the group, and select the
10496 group (@code{gnus-summary-rescan-group}). If given a prefix, select all
10497 articles, both read and unread.
10500 @kindex Z N (Summary)
10501 @findex gnus-summary-next-group
10502 Exit the group and go to the next group
10503 (@code{gnus-summary-next-group}).
10506 @kindex Z P (Summary)
10507 @findex gnus-summary-prev-group
10508 Exit the group and go to the previous group
10509 (@code{gnus-summary-prev-group}).
10512 @kindex Z s (Summary)
10513 @findex gnus-summary-save-newsrc
10514 Save the current number of read/marked articles in the dribble buffer
10515 and then save the dribble buffer (@code{gnus-summary-save-newsrc}). If
10516 given a prefix, also save the @file{.newsrc} file(s). Using this
10517 command will make exit without updating (the @kbd{Q} command) worthless.
10520 @vindex gnus-exit-group-hook
10521 @code{gnus-exit-group-hook} is called when you exit the current group
10522 with an ``updating'' exit. For instance @kbd{Q}
10523 (@code{gnus-summary-exit-no-update}) does not call this hook.
10525 @findex gnus-summary-wake-up-the-dead
10526 @findex gnus-dead-summary-mode
10527 @vindex gnus-kill-summary-on-exit
10528 If you're in the habit of exiting groups, and then changing your mind
10529 about it, you might set @code{gnus-kill-summary-on-exit} to @code{nil}.
10530 If you do that, gnus won't kill the summary buffer when you exit it.
10531 (Quelle surprise!) Instead it will change the name of the buffer to
10532 something like @samp{*Dead Summary ... *} and install a minor mode
10533 called @code{gnus-dead-summary-mode}. Now, if you switch back to this
10534 buffer, you'll find that all keys are mapped to a function called
10535 @code{gnus-summary-wake-up-the-dead}. So tapping any keys in a dead
10536 summary buffer will result in a live, normal summary buffer.
10538 There will never be more than one dead summary buffer at any one time.
10540 @vindex gnus-use-cross-reference
10541 The data on the current group will be updated (which articles you have
10542 read, which articles you have replied to, etc.) when you exit the
10543 summary buffer. If the @code{gnus-use-cross-reference} variable is
10544 @code{t} (which is the default), articles that are cross-referenced to
10545 this group and are marked as read, will also be marked as read in the
10546 other subscribed groups they were cross-posted to. If this variable is
10547 neither @code{nil} nor @code{t}, the article will be marked as read in
10548 both subscribed and unsubscribed groups (@pxref{Crosspost Handling}).
10551 @node Crosspost Handling
10552 @section Crosspost Handling
10556 Marking cross-posted articles as read ensures that you'll never have to
10557 read the same article more than once. Unless, of course, somebody has
10558 posted it to several groups separately. Posting the same article to
10559 several groups (not cross-posting) is called @dfn{spamming}, and you are
10560 by law required to send nasty-grams to anyone who perpetrates such a
10561 heinous crime. You may want to try NoCeM handling to filter out spam
10564 Remember: Cross-posting is kinda ok, but posting the same article
10565 separately to several groups is not. Massive cross-posting (aka.
10566 @dfn{velveeta}) is to be avoided at all costs, and you can even use the
10567 @code{gnus-summary-mail-crosspost-complaint} command to complain about
10568 excessive crossposting (@pxref{Summary Mail Commands}).
10570 @cindex cross-posting
10572 @cindex @acronym{NOV}
10573 One thing that may cause Gnus to not do the cross-posting thing
10574 correctly is if you use an @acronym{NNTP} server that supports @sc{xover}
10575 (which is very nice, because it speeds things up considerably) which
10576 does not include the @code{Xref} header in its @acronym{NOV} lines. This is
10577 Evil, but all too common, alas, alack. Gnus tries to Do The Right Thing
10578 even with @sc{xover} by registering the @code{Xref} lines of all
10579 articles you actually read, but if you kill the articles, or just mark
10580 them as read without reading them, Gnus will not get a chance to snoop
10581 the @code{Xref} lines out of these articles, and will be unable to use
10582 the cross reference mechanism.
10584 @cindex LIST overview.fmt
10585 @cindex overview.fmt
10586 To check whether your @acronym{NNTP} server includes the @code{Xref} header
10587 in its overview files, try @samp{telnet your.nntp.server nntp},
10588 @samp{MODE READER} on @code{inn} servers, and then say @samp{LIST
10589 overview.fmt}. This may not work, but if it does, and the last line you
10590 get does not read @samp{Xref:full}, then you should shout and whine at
10591 your news admin until she includes the @code{Xref} header in the
10594 @vindex gnus-nov-is-evil
10595 If you want Gnus to get the @code{Xref}s right all the time, you have to
10596 set @code{gnus-nov-is-evil} to @code{t}, which slows things down
10601 For an alternative approach, @pxref{Duplicate Suppression}.
10604 @node Duplicate Suppression
10605 @section Duplicate Suppression
10607 By default, gnus tries to make sure that you don't have to read the same
10608 article more than once by utilizing the crossposting mechanism
10609 (@pxref{Crosspost Handling}). However, that simple and efficient
10610 approach may not work satisfactory for some users for various
10615 The @acronym{NNTP} server may fail to generate the @code{Xref} header. This
10616 is evil and not very common.
10619 The @acronym{NNTP} server may fail to include the @code{Xref} header in the
10620 @file{.overview} data bases. This is evil and all too common, alas.
10623 You may be reading the same group (or several related groups) from
10624 different @acronym{NNTP} servers.
10627 You may be getting mail that duplicates articles posted to groups.
10630 I'm sure there are other situations where @code{Xref} handling fails as
10631 well, but these four are the most common situations.
10633 If, and only if, @code{Xref} handling fails for you, then you may
10634 consider switching on @dfn{duplicate suppression}. If you do so, Gnus
10635 will remember the @code{Message-ID}s of all articles you have read or
10636 otherwise marked as read, and then, as if by magic, mark them as read
10637 all subsequent times you see them---in @emph{all} groups. Using this
10638 mechanism is quite likely to be somewhat inefficient, but not overly
10639 so. It's certainly preferable to reading the same articles more than
10642 Duplicate suppression is not a very subtle instrument. It's more like a
10643 sledge hammer than anything else. It works in a very simple
10644 fashion---if you have marked an article as read, it adds this Message-ID
10645 to a cache. The next time it sees this Message-ID, it will mark the
10646 article as read with the @samp{M} mark. It doesn't care what group it
10647 saw the article in.
10650 @item gnus-suppress-duplicates
10651 @vindex gnus-suppress-duplicates
10652 If non-@code{nil}, suppress duplicates.
10654 @item gnus-save-duplicate-list
10655 @vindex gnus-save-duplicate-list
10656 If non-@code{nil}, save the list of duplicates to a file. This will
10657 make startup and shutdown take longer, so the default is @code{nil}.
10658 However, this means that only duplicate articles read in a single gnus
10659 session are suppressed.
10661 @item gnus-duplicate-list-length
10662 @vindex gnus-duplicate-list-length
10663 This variable says how many @code{Message-ID}s to keep in the duplicate
10664 suppression list. The default is 10000.
10666 @item gnus-duplicate-file
10667 @vindex gnus-duplicate-file
10668 The name of the file to store the duplicate suppression list in. The
10669 default is @file{~/News/suppression}.
10672 If you have a tendency to stop and start gnus often, setting
10673 @code{gnus-save-duplicate-list} to @code{t} is probably a good idea. If
10674 you leave gnus running for weeks on end, you may have it @code{nil}. On
10675 the other hand, saving the list makes startup and shutdown much slower,
10676 so that means that if you stop and start gnus often, you should set
10677 @code{gnus-save-duplicate-list} to @code{nil}. Uhm. I'll leave this up
10678 to you to figure out, I think.
10683 Gnus is able to verify signed messages or decrypt encrypted messages.
10684 The formats that are supported are @acronym{PGP}, @acronym{PGP/MIME}
10685 and @acronym{S/MIME}, however you need some external programs to get
10690 To handle @acronym{PGP} and @acronym{PGP/MIME} messages, you have to
10691 install an OpenPGP implementation such as GnuPG. The Lisp interface
10692 to GnuPG included with Gnus is called PGG (@pxref{Top, ,PGG, pgg, PGG
10693 Manual}), but Mailcrypt and gpg.el are also supported.
10696 To handle @acronym{S/MIME} message, you need to install OpenSSL. OpenSSL 0.9.6
10697 or newer is recommended.
10701 More information on how to set things up can be found in the message
10702 manual (@pxref{Security, ,Security, message, Message Manual}).
10705 @item mm-verify-option
10706 @vindex mm-verify-option
10707 Option of verifying signed parts. @code{never}, not verify;
10708 @code{always}, always verify; @code{known}, only verify known
10709 protocols. Otherwise, ask user.
10711 @item mm-decrypt-option
10712 @vindex mm-decrypt-option
10713 Option of decrypting encrypted parts. @code{never}, no decryption;
10714 @code{always}, always decrypt; @code{known}, only decrypt known
10715 protocols. Otherwise, ask user.
10718 @vindex mml1991-use
10719 Symbol indicating elisp interface to OpenPGP implementation for
10720 @acronym{PGP} messages. The default is @code{pgg}, but
10721 @code{mailcrypt} and @code{gpg} are also supported although
10725 @vindex mml2015-use
10726 Symbol indicating elisp interface to OpenPGP implementation for
10727 @acronym{PGP/MIME} messages. The default is @code{pgg}, but
10728 @code{mailcrypt} and @code{gpg} are also supported although
10733 @cindex snarfing keys
10734 @cindex importing PGP keys
10735 @cindex PGP key ring import
10736 Snarfing OpenPGP keys (i.e., importing keys from articles into your
10737 key ring) is not supported explicitly through a menu item or command,
10738 rather Gnus do detect and label keys as @samp{application/pgp-keys},
10739 allowing you to specify whatever action you think is appropriate
10740 through the usual @acronym{MIME} infrastructure. You can use a
10741 @file{~/.mailcap} entry (@pxref{mailcap, , mailcap, emacs-mime, The
10742 Emacs MIME Manual}) such as the following to import keys using GNU
10743 Privacy Guard when you click on the @acronym{MIME} button
10744 (@pxref{Using MIME}).
10747 application/pgp-keys; gpg --import --interactive --verbose; needsterminal
10750 This happens to also be the default action defined in
10751 @code{mailcap-mime-data}.
10754 @section Mailing List
10755 @cindex mailing list
10758 @kindex A M (summary)
10759 @findex gnus-mailing-list-insinuate
10760 Gnus understands some mailing list fields of RFC 2369. To enable it,
10761 add a @code{to-list} group parameter (@pxref{Group Parameters}),
10762 possibly using @kbd{A M} (@code{gnus-mailing-list-insinuate}) in the
10765 That enables the following commands to the summary buffer:
10770 @kindex C-c C-n h (Summary)
10771 @findex gnus-mailing-list-help
10772 Send a message to fetch mailing list help, if List-Help field exists.
10775 @kindex C-c C-n s (Summary)
10776 @findex gnus-mailing-list-subscribe
10777 Send a message to subscribe the mailing list, if List-Subscribe field exists.
10780 @kindex C-c C-n u (Summary)
10781 @findex gnus-mailing-list-unsubscribe
10782 Send a message to unsubscribe the mailing list, if List-Unsubscribe
10786 @kindex C-c C-n p (Summary)
10787 @findex gnus-mailing-list-post
10788 Post to the mailing list, if List-Post field exists.
10791 @kindex C-c C-n o (Summary)
10792 @findex gnus-mailing-list-owner
10793 Send a message to the mailing list owner, if List-Owner field exists.
10796 @kindex C-c C-n a (Summary)
10797 @findex gnus-mailing-list-archive
10798 Browse the mailing list archive, if List-Archive field exists.
10803 @node Article Buffer
10804 @chapter Article Buffer
10805 @cindex article buffer
10807 The articles are displayed in the article buffer, of which there is only
10808 one. All the summary buffers share the same article buffer unless you
10809 tell gnus otherwise.
10812 * Hiding Headers:: Deciding what headers should be displayed.
10813 * Using MIME:: Pushing articles through @acronym{MIME} before reading them.
10814 * Customizing Articles:: Tailoring the look of the articles.
10815 * Article Keymap:: Keystrokes available in the article buffer.
10816 * Misc Article:: Other stuff.
10820 @node Hiding Headers
10821 @section Hiding Headers
10822 @cindex hiding headers
10823 @cindex deleting headers
10825 The top section of each article is the @dfn{head}. (The rest is the
10826 @dfn{body}, but you may have guessed that already.)
10828 @vindex gnus-show-all-headers
10829 There is a lot of useful information in the head: the name of the person
10830 who wrote the article, the date it was written and the subject of the
10831 article. That's well and nice, but there's also lots of information
10832 most people do not want to see---what systems the article has passed
10833 through before reaching you, the @code{Message-ID}, the
10834 @code{References}, etc. ad nauseam---and you'll probably want to get rid
10835 of some of those lines. If you want to keep all those lines in the
10836 article buffer, you can set @code{gnus-show-all-headers} to @code{t}.
10838 Gnus provides you with two variables for sifting headers:
10842 @item gnus-visible-headers
10843 @vindex gnus-visible-headers
10844 If this variable is non-@code{nil}, it should be a regular expression
10845 that says what headers you wish to keep in the article buffer. All
10846 headers that do not match this variable will be hidden.
10848 For instance, if you only want to see the name of the person who wrote
10849 the article and the subject, you'd say:
10852 (setq gnus-visible-headers "^From:\\|^Subject:")
10855 This variable can also be a list of regexps to match headers to
10858 @item gnus-ignored-headers
10859 @vindex gnus-ignored-headers
10860 This variable is the reverse of @code{gnus-visible-headers}. If this
10861 variable is set (and @code{gnus-visible-headers} is @code{nil}), it
10862 should be a regular expression that matches all lines that you want to
10863 hide. All lines that do not match this variable will remain visible.
10865 For instance, if you just want to get rid of the @code{References} field
10866 and the @code{Xref} field, you might say:
10869 (setq gnus-ignored-headers "^References:\\|^Xref:")
10872 This variable can also be a list of regexps to match headers to
10875 Note that if @code{gnus-visible-headers} is non-@code{nil}, this
10876 variable will have no effect.
10880 @vindex gnus-sorted-header-list
10881 Gnus can also sort the headers for you. (It does this by default.) You
10882 can control the sorting by setting the @code{gnus-sorted-header-list}
10883 variable. It is a list of regular expressions that says in what order
10884 the headers are to be displayed.
10886 For instance, if you want the name of the author of the article first,
10887 and then the subject, you might say something like:
10890 (setq gnus-sorted-header-list '("^From:" "^Subject:"))
10893 Any headers that are to remain visible, but are not listed in this
10894 variable, will be displayed in random order after all the headers listed in this variable.
10896 @findex gnus-article-hide-boring-headers
10897 @vindex gnus-boring-article-headers
10898 You can hide further boring headers by setting
10899 @code{gnus-treat-hide-boring-headers} to @code{head}. What this function
10900 does depends on the @code{gnus-boring-article-headers} variable. It's a
10901 list, but this list doesn't actually contain header names. Instead it
10902 lists various @dfn{boring conditions} that Gnus can check and remove
10905 These conditions are:
10908 Remove all empty headers.
10910 Remove the @code{Followup-To} header if it is identical to the
10911 @code{Newsgroups} header.
10913 Remove the @code{Reply-To} header if it lists the same addresses as
10914 the @code{From} header, or if the @code{broken-reply-to} group
10917 Remove the @code{Newsgroups} header if it only contains the current group
10920 Remove the @code{To} header if it only contains the address identical to
10921 the current group's @code{to-address} parameter.
10923 Remove the @code{To} header if it only contains the address identical to
10924 the current group's @code{to-list} parameter.
10926 Remove the @code{CC} header if it only contains the address identical to
10927 the current group's @code{to-list} parameter.
10929 Remove the @code{Date} header if the article is less than three days
10932 Remove the @code{To} header if it is very long.
10934 Remove all @code{To} headers if there are more than one.
10937 To include these three elements, you could say something like:
10940 (setq gnus-boring-article-headers
10941 '(empty followup-to reply-to))
10944 This is also the default value for this variable.
10948 @section Using MIME
10949 @cindex @acronym{MIME}
10951 Mime is a standard for waving your hands through the air, aimlessly,
10952 while people stand around yawning.
10954 @acronym{MIME}, however, is a standard for encoding your articles, aimlessly,
10955 while all newsreaders die of fear.
10957 @acronym{MIME} may specify what character set the article uses, the encoding
10958 of the characters, and it also makes it possible to embed pictures and
10959 other naughty stuff in innocent-looking articles.
10961 @vindex gnus-show-mime
10962 @vindex gnus-article-display-method-for-mime
10963 @findex gnus-article-display-mime-message
10964 gnus handles @acronym{MIME} by pushing the articles through
10965 @code{gnus-article-display-method-for-mime}, which is
10966 @code{gnus-article-display-mime-message} by default. This function
10967 calls the @acronym{SEMI} MIME-View program to actually do the work. For
10968 more information on @acronym{SEMI} MIME-View, see its manual page
10969 (however it is not existed yet, sorry).
10971 Set @code{gnus-show-mime} to @code{t} if you want to use
10972 @acronym{MIME} all the time. If you have @code{gnus-show-mime} set,
10973 then you'll see some unfortunate display glitches in the article buffer.
10974 These can't be avoided.
10976 In GNUS or Gnus, it might be best to just use the toggling functions
10977 from the summary buffer to avoid getting nasty surprises. (For instance,
10978 you enter the group @samp{alt.sing-a-long} and, before you know it,
10979 @acronym{MIME} has decoded the sound file in the article and some
10980 horrible sing-a-long song comes screaming out your speakers, and you
10981 can't find the volume button, because there isn't one, and people are
10982 starting to look at you, and you try to stop the program, but you can't,
10983 and you can't find the program to control the volume, and everybody else
10984 in the room suddenly decides to look at you disdainfully, and you'll
10985 feel rather stupid.)
10987 Any similarity to real events and people is purely coincidental. Ahem.
10989 To avoid such kind of situation, gnus stops to use
10990 @code{metamail-buffer}. So now, you can set @code{gnus-show-mime} to
10991 non-@code{nil} every-time, then you can push button in the article
10992 buffer when there are nobody else.
10994 Also @pxref{MIME Commands}.
10997 @node Customizing Articles
10998 @section Customizing Articles
10999 @cindex article customization
11001 A slew of functions for customizing how the articles are to look like
11002 exist. You can call these functions interactively
11003 (@pxref{Article Washing}), or you can have them
11004 called automatically when you select the articles.
11006 To have them called automatically, you should set the corresponding
11007 ``treatment'' variable. For instance, to have headers hidden, you'd set
11008 @code{gnus-treat-hide-headers}. Below is a list of variables that can
11009 be set, but first we discuss the values these variables can have.
11011 Note: Some values, while valid, make little sense. Check the list below
11012 for sensible values.
11016 @code{nil}: Don't do this treatment.
11019 @code{t}: Do this treatment on all body parts.
11022 @code{head}: Do the treatment on the headers.
11025 @code{last}: Do this treatment on the last part.
11028 An integer: Do this treatment on all body parts that have a length less
11032 A list of strings: Do this treatment on all body parts that are in
11033 articles that are read in groups that have names that match one of the
11034 regexps in the list.
11037 A list where the first element is not a string:
11039 The list is evaluated recursively. The first element of the list is a
11040 predicate. The following predicates are recognized: @code{or},
11041 @code{and}, @code{not} and @code{typep}. Here's an example:
11045 (typep "text/x-vcard"))
11049 @code{mime}: Do this treatment if the value of @code{gnus-show-mime}' is
11054 You may have noticed that the word @dfn{part} is used here. This refers
11055 to the fact that some messages are @acronym{MIME} multipart articles that may
11056 be divided into several parts. Articles that are not multiparts are
11057 considered to contain just a single part.
11059 @vindex gnus-article-treat-types
11060 Are the treatments applied to all sorts of multipart parts? Yes, if you
11061 want to, but by default, only @samp{text/plain} parts are given the
11062 treatment. This is controlled by the @code{gnus-article-treat-types}
11063 variable, which is a list of regular expressions that are matched to the
11064 type of the part. This variable is ignored if the value of the
11065 controlling variable is a predicate list, as described above.
11067 The following treatment options are available. The easiest way to
11068 customize this is to examine the @code{gnus-article-treat} customization
11069 group. Values in parenthesis are suggested sensible values. Others are
11070 possible but those listed are probably sufficient for most people.
11073 @item gnus-treat-buttonize (t, integer)
11074 @item gnus-treat-buttonize-head (head)
11076 @xref{Article Buttons}.
11078 @item gnus-treat-capitalize-sentences (t, integer)
11079 @item gnus-treat-overstrike (t, integer)
11080 @item gnus-treat-strip-cr (t, integer)
11081 @item gnus-treat-strip-headers-in-body (t, integer)
11082 @item gnus-treat-strip-leading-blank-lines (t, integer)
11083 @item gnus-treat-strip-multiple-blank-lines (t, integer)
11084 @item gnus-treat-strip-pem (t, last, integer)
11085 @item gnus-treat-strip-trailing-blank-lines (t, last, integer)
11086 @item gnus-treat-unsplit-urls (t, integer)
11087 @item gnus-treat-wash-html (t, integer)
11088 @item gnus-treat-decode-article-as-default-mime-charset (t, integer)
11090 @xref{Article Washing}.
11092 @item gnus-treat-date-english (head)
11093 @item gnus-treat-date-iso8601 (head)
11094 @item gnus-treat-date-lapsed (head)
11095 @item gnus-treat-date-local (head)
11096 @item gnus-treat-date-original (head)
11097 @item gnus-treat-date-user-defined (head)
11098 @item gnus-treat-date-ut (head)
11100 @xref{Article Date}.
11102 @item gnus-treat-from-picon (head)
11103 @item gnus-treat-mail-picon (head)
11104 @item gnus-treat-newsgroups-picon (head)
11108 @item gnus-treat-display-smileys (t, integer)
11110 @item gnus-treat-body-boundary (head)
11112 @vindex gnus-body-boundary-delimiter
11113 Adds a delimiter between header and body, the string used as delimiter
11114 is controlled by @code{gnus-body-boundary-delimiter}.
11118 @item gnus-treat-display-x-face (head)
11122 @item gnus-treat-display-face (head)
11126 @item gnus-treat-emphasize (t, head, integer)
11127 @item gnus-treat-fill-article (t, integer)
11128 @item gnus-treat-fill-long-lines (t, integer)
11129 @item gnus-treat-hide-boring-headers (head)
11130 @item gnus-treat-hide-citation (t, integer)
11131 @item gnus-treat-hide-citation-maybe (t, integer)
11132 @item gnus-treat-hide-headers (head)
11133 @item gnus-treat-hide-signature (t, last)
11134 @item gnus-treat-strip-banner (t, last)
11135 @item gnus-treat-strip-list-identifiers (head)
11137 @xref{Article Hiding}.
11139 @item gnus-treat-highlight-citation (t, integer)
11140 @item gnus-treat-highlight-headers (head)
11141 @item gnus-treat-highlight-signature (t, last, integer)
11143 @xref{Article Highlighting}.
11145 @item gnus-treat-play-sounds
11146 @item gnus-treat-translate
11147 @item gnus-treat-ansi-sequences (t)
11148 @item gnus-treat-x-pgp-sig (head)
11150 @item gnus-treat-unfold-headers (head)
11151 @item gnus-treat-fold-headers (head)
11152 @item gnus-treat-fold-newsgroups (head)
11153 @item gnus-treat-leading-whitespace (head)
11155 @xref{Article Header}.
11160 @vindex gnus-part-display-hook
11161 You can, of course, write your own functions to be called from
11162 @code{gnus-part-display-hook}. The functions are called narrowed to the
11163 part, and you can do anything you like, pretty much. There is no
11164 information that you have to keep in the buffer---you can change
11168 @node Article Keymap
11169 @section Article Keymap
11171 Most of the keystrokes in the summary buffer can also be used in the
11172 article buffer. They should behave as if you typed them in the summary
11173 buffer, which means that you don't actually have to have a summary
11174 buffer displayed while reading. You can do it all from the article
11177 A few additional keystrokes are available:
11182 @kindex SPACE (Article)
11183 @findex gnus-article-next-page
11184 Scroll forwards one page (@code{gnus-article-next-page}).
11185 This is exactly the same as @kbd{h SPACE h}.
11188 @kindex DEL (Article)
11189 @findex gnus-article-prev-page
11190 Scroll backwards one page (@code{gnus-article-prev-page}).
11191 This is exactly the same as @kbd{h DEL h}.
11194 @kindex C-c ^ (Article)
11195 @findex gnus-article-refer-article
11196 If point is in the neighborhood of a @code{Message-ID} and you press
11197 @kbd{C-c ^}, Gnus will try to get that article from the server
11198 (@code{gnus-article-refer-article}).
11201 @kindex C-c C-m (Article)
11202 @findex gnus-article-mail
11203 Send a reply to the address near point (@code{gnus-article-mail}). If
11204 given a prefix, include the mail.
11207 @kindex s (Article)
11208 @findex gnus-article-show-summary
11209 Reconfigure the buffers so that the summary buffer becomes visible
11210 (@code{gnus-article-show-summary}).
11213 @kindex ? (Article)
11214 @findex gnus-article-describe-briefly
11215 Give a very brief description of the available keystrokes
11216 (@code{gnus-article-describe-briefly}).
11219 @kindex TAB (Article)
11220 @findex gnus-article-next-button
11221 Go to the next button, if any (@code{gnus-article-next-button}). This
11222 only makes sense if you have buttonizing turned on.
11225 @kindex M-TAB (Article)
11226 @findex gnus-article-prev-button
11227 Go to the previous button, if any (@code{gnus-article-prev-button}).
11230 @kindex R (Article)
11231 @findex gnus-article-reply-with-original
11232 Send a reply to the current article and yank the current article
11233 (@code{gnus-article-reply-with-original}). If given a prefix, make a
11234 wide reply. If the region is active, only yank the text in the
11238 @kindex F (Article)
11239 @findex gnus-article-followup-with-original
11240 Send a followup to the current article and yank the current article
11241 (@code{gnus-article-followup-with-original}). If given a prefix, make
11242 a wide reply. If the region is active, only yank the text in the
11250 @section Misc Article
11254 @item gnus-single-article-buffer
11255 @vindex gnus-single-article-buffer
11256 If non-@code{nil}, use the same article buffer for all the groups.
11257 (This is the default.) If @code{nil}, each group will have its own
11260 @vindex gnus-article-decode-hook
11261 @item gnus-article-decode-hook
11262 @cindex @acronym{MIME}
11263 Hook used to decode @acronym{MIME} articles. The default value is
11264 @code{(article-decode-charset article-decode-encoded-words)}
11266 @vindex gnus-article-prepare-hook
11267 @item gnus-article-prepare-hook
11268 This hook is called right after the article has been inserted into the
11269 article buffer. It is mainly intended for functions that do something
11270 depending on the contents; it should probably not be used for changing
11271 the contents of the article buffer.
11273 @item gnus-article-mode-hook
11274 @vindex gnus-article-mode-hook
11275 Hook called in article mode buffers.
11277 @item gnus-article-mode-syntax-table
11278 @vindex gnus-article-mode-syntax-table
11279 Syntax table used in article buffers. It is initialized from
11280 @code{text-mode-syntax-table}.
11282 @vindex gnus-article-over-scroll
11283 @item gnus-article-over-scroll
11284 If non-@code{nil}, allow scrolling the article buffer even when there
11285 no more new text to scroll in. The default is @code{nil}.
11287 @vindex gnus-article-mode-line-format
11288 @item gnus-article-mode-line-format
11289 This variable is a format string along the same lines as
11290 @code{gnus-summary-mode-line-format} (@pxref{Summary Buffer Mode
11291 Line}). It accepts the same format specifications as that variable,
11292 with two extensions:
11297 The @dfn{wash status} of the article. This is a short string with one
11298 character for each possible article wash operation that may have been
11299 performed. The characters and their meaning:
11304 Displayed when cited text may be hidden in the article buffer.
11307 Displayed when headers are hidden in the article buffer.
11310 Displayed when article is digitally signed or encrypted, and Gnus has
11311 hidden the security headers. (N.B. does not tell anything about
11312 security status, i.e. good or bad signature.)
11315 Displayed when the signature has been hidden in the Article buffer.
11318 Displayed when Gnus has treated overstrike characters in the article buffer.
11321 Displayed when Gnus has treated emphasised strings in the article buffer.
11326 The number of @acronym{MIME} parts in the article.
11330 @vindex gnus-break-pages
11332 @item gnus-break-pages
11333 Controls whether @dfn{page breaking} is to take place. If this variable
11334 is non-@code{nil}, the articles will be divided into pages whenever a
11335 page delimiter appears in the article. If this variable is @code{nil},
11336 paging will not be done.
11338 @item gnus-page-delimiter
11339 @vindex gnus-page-delimiter
11340 This is the delimiter mentioned above. By default, it is @samp{^L}
11344 @cindex internationalized domain names
11345 @vindex gnus-use-idna
11346 @item gnus-use-idna
11347 This variable controls whether Gnus performs IDNA decoding of
11348 internationalized domain names inside @samp{From}, @samp{To} and
11349 @samp{Cc} headers. @xref{IDNA, ,IDNA,message, The Message Manual},
11350 for how to compose such messages. This requires
11351 @uref{http://www.gnu.org/software/libidn/, GNU Libidn}, and this
11352 variable is only enabled if you have installed it.
11357 @node Composing Messages
11358 @chapter Composing Messages
11359 @cindex composing messages
11362 @cindex sending mail
11367 @cindex using s/mime
11368 @cindex using smime
11370 @kindex C-c C-c (Post)
11371 All commands for posting and mailing will put you in a message buffer
11372 where you can edit the article all you like, before you send the
11373 article by pressing @kbd{C-c C-c}. @xref{Top, , Overview, message,
11374 Message Manual}. Where the message will be posted/mailed to depends
11375 on your setup (@pxref{Posting Server}).
11378 * Mail:: Mailing and replying.
11379 * Posting Server:: What server should you post and mail via?
11380 * POP before SMTP:: You cannot send a mail unless you read a mail.
11381 * Mail and Post:: Mailing and posting at the same time.
11382 * Archived Messages:: Where Gnus stores the messages you've sent.
11383 * Posting Styles:: An easier way to specify who you are.
11384 * Drafts:: Postponing messages and rejected messages.
11385 * Rejected Articles:: What happens if the server doesn't like your article?
11386 * Signing and encrypting:: How to compose secure messages.
11389 Also @pxref{Canceling and Superseding} for information on how to
11390 remove articles you shouldn't have posted.
11396 Variables for customizing outgoing mail:
11399 @item gnus-uu-digest-headers
11400 @vindex gnus-uu-digest-headers
11401 List of regexps to match headers included in digested messages. The
11402 headers will be included in the sequence they are matched. If
11403 @code{nil} include all headers.
11405 @item gnus-add-to-list
11406 @vindex gnus-add-to-list
11407 If non-@code{nil}, add a @code{to-list} group parameter to mail groups
11408 that have none when you do a @kbd{a}.
11410 @item gnus-confirm-mail-reply-to-news
11411 @vindex gnus-confirm-mail-reply-to-news
11412 This can also be a function receiving the group name as the only
11413 parameter which should return non-@code{nil} if a confirmation is
11414 needed, or a regular expression matching group names, where
11415 confirmation is should be asked for.
11417 If you find yourself never wanting to reply to mail, but occasionally
11418 press R anyway, this variable might be for you.
11420 @item gnus-confirm-treat-mail-like-news
11421 @vindex gnus-confirm-treat-mail-like-news
11422 If non-@code{nil}, Gnus also requests confirmation according to
11423 @code{gnus-confirm-mail-reply-to-news} when replying to mail. This is
11424 useful for treating mailing lists like newsgroups.
11429 @node Posting Server
11430 @section Posting Server
11432 When you press those magical @kbd{C-c C-c} keys to ship off your latest
11433 (extremely intelligent, of course) article, where does it go?
11435 Thank you for asking. I hate you.
11437 It can be quite complicated.
11439 @vindex gnus-post-method
11440 When posting news, Message usually invokes @code{message-send-news}
11441 (@pxref{News Variables, , News Variables, message, Message Manual}).
11442 Normally, Gnus will post using the same select method as you're
11443 reading from (which might be convenient if you're reading lots of
11444 groups from different private servers). However. If the server
11445 you're reading from doesn't allow posting, just reading, you probably
11446 want to use some other server to post your (extremely intelligent and
11447 fabulously interesting) articles. You can then set the
11448 @code{gnus-post-method} to some other method:
11451 (setq gnus-post-method '(nnspool ""))
11454 Now, if you've done this, and then this server rejects your article, or
11455 this server is down, what do you do then? To override this variable you
11456 can use a non-zero prefix to the @kbd{C-c C-c} command to force using
11457 the ``current'' server, to get back the default behavior, for posting.
11459 If you give a zero prefix (i.e., @kbd{C-u 0 C-c C-c}) to that command,
11460 gnus will prompt you for what method to use for posting.
11462 You can also set @code{gnus-post-method} to a list of select methods.
11463 If that's the case, gnus will always prompt you for what method to use
11466 Finally, if you want to always post using the native select method,
11467 you can set this variable to @code{native}.
11469 When sending mail, Message invokes @code{message-send-mail-function}.
11470 The default function, @code{message-send-mail-with-sendmail}, pipes
11471 your article to the @code{sendmail} binary for further queuing and
11472 sending. When your local system is not configured for sending mail
11473 using @code{sendmail}, and you have access to a remote @acronym{SMTP}
11474 server, you can set @code{message-send-mail-function} to
11475 @code{smtpmail-send-it} and make sure to setup the @code{smtpmail}
11476 package correctly. An example:
11479 (setq message-send-mail-function 'smtpmail-send-it
11480 smtpmail-default-smtp-server "YOUR SMTP HOST")
11481 ;; @r{The following variable needs to be set if you are using smtpmail.el}
11482 ;; @r{distributed with FLIM, lesser than the version 1.14.6.}
11483 (setq smtp-default-server "YOUR SMTP HOST")
11486 To the thing similar to this, there is
11487 @code{message-smtpmail-send-it}. It is useful if your @acronym{ISP}
11488 requires the @acronym{POP}-before-@acronym{SMTP} authentication.
11489 @xref{POP before SMTP}.
11491 Other possible choices for @code{message-send-mail-function} includes
11492 @code{message-send-mail-with-mh}, @code{message-send-mail-with-qmail},
11493 and @code{feedmail-send-it}.
11495 @node POP before SMTP
11496 @section POP before SMTP
11497 @cindex pop before smtp
11498 @findex message-smtpmail-send-it
11499 @findex mail-source-touch-pop
11501 Does your @acronym{ISP} require the @acronym{POP}-before-@acronym{SMTP}
11502 authentication? It is whether you need to connect to the @acronym{POP}
11503 mail server within a certain time before sending mails. If so, there is
11504 a convenient way. To do that, put the following lines in your
11505 @file{~/.gnus.el} file:
11508 (setq message-send-mail-function 'message-smtpmail-send-it)
11509 (add-hook 'message-send-mail-hook 'mail-source-touch-pop)
11513 It means to let Gnus connect to the @acronym{POP} mail server in advance
11514 whenever you send a mail. The @code{mail-source-touch-pop} function
11515 does only a @acronym{POP} authentication according to the value of
11516 @code{mail-sources} without fetching mails, just before sending a mail.
11517 Note that you have to use @code{message-smtpmail-send-it} which runs
11518 @code{message-send-mail-hook} rather than @code{smtpmail-send-it} and
11519 set the value of @code{mail-sources} for a @acronym{POP} connection
11520 correctly. @xref{Mail Sources}.
11522 If you have two or more @acronym{POP} mail servers set in
11523 @code{mail-sources}, you may want to specify one of them to
11524 @code{mail-source-primary-source} as the @acronym{POP} mail server to be
11525 used for the @acronym{POP}-before-@acronym{SMTP} authentication. If it
11526 is your primary @acronym{POP} mail server (i.e., you are fetching mails
11527 mainly from that server), you can set it permanently as follows:
11530 (setq mail-source-primary-source
11531 '(pop :server "pop3.mail.server"
11532 :password "secret"))
11536 Otherwise, bind it dynamically only when performing the
11537 @acronym{POP}-before-@acronym{SMTP} authentication as follows:
11540 (add-hook 'message-send-mail-hook
11542 (let ((mail-source-primary-source
11543 '(pop :server "pop3.mail.server"
11544 :password "secret")))
11545 (mail-source-touch-pop))))
11548 @node Mail and Post
11549 @section Mail and Post
11551 Here's a list of variables relevant to both mailing and
11555 @item gnus-mailing-list-groups
11556 @findex gnus-mailing-list-groups
11557 @cindex mailing lists
11559 If your news server offers groups that are really mailing lists
11560 gatewayed to the @acronym{NNTP} server, you can read those groups without
11561 problems, but you can't post/followup to them without some difficulty.
11562 One solution is to add a @code{to-address} to the group parameters
11563 (@pxref{Group Parameters}). An easier thing to do is set the
11564 @code{gnus-mailing-list-groups} to a regexp that matches the groups that
11565 really are mailing lists. Then, at least, followups to the mailing
11566 lists will work most of the time. Posting to these groups (@kbd{a}) is
11567 still a pain, though.
11569 @item gnus-user-agent
11570 @vindex gnus-user-agent
11573 This variable controls which information should be exposed in the
11574 User-Agent header. It can be one of the symbols @code{gnus} (show only
11575 Gnus version), @code{emacs-gnus} (show only Emacs and Gnus versions),
11576 @code{emacs-gnus-config} (same as @code{emacs-gnus} plus system
11577 configuration), @code{emacs-gnus-type} (same as @code{emacs-gnus} plus
11578 system type) or a custom string. If you set it to a string, be sure to
11579 use a valid format, see RFC 2616.
11583 You may want to do spell-checking on messages that you send out. Or, if
11584 you don't want to spell-check by hand, you could add automatic
11585 spell-checking via the @code{ispell} package:
11588 @findex ispell-message
11590 (add-hook 'message-send-hook 'ispell-message)
11593 If you want to change the @code{ispell} dictionary based on what group
11594 you're in, you could say something like the following:
11597 (add-hook 'gnus-select-group-hook
11601 "^de\\." (gnus-group-real-name gnus-newsgroup-name))
11602 (ispell-change-dictionary "deutsch"))
11604 (ispell-change-dictionary "english")))))
11607 Modify to suit your needs.
11610 @node Archived Messages
11611 @section Archived Messages
11612 @cindex archived messages
11613 @cindex sent messages
11615 Gnus provides a few different methods for storing the mail and news you
11616 send. The default method is to use the @dfn{archive virtual server} to
11617 store the messages. If you want to disable this completely, the
11618 @code{gnus-message-archive-group} variable should be @code{nil}, which
11621 For archiving interesting messages in a group you read, see the
11622 @kbd{B c} (@code{gnus-summary-copy-article}) command (@pxref{Mail
11625 @vindex gnus-message-archive-method
11626 @code{gnus-message-archive-method} says what virtual server gnus is to
11627 use to store sent messages. The default is:
11630 (nnfolder "archive"
11631 (nnfolder-directory "~/Mail/archive")
11632 (nnfolder-active-file "~/Mail/archive/active")
11633 (nnfolder-get-new-mail nil)
11634 (nnfolder-inhibit-expiry t))
11637 You can, however, use any mail select method (@code{nnml},
11638 @code{nnmbox}, etc.). @code{nnfolder} is a quite likable select method
11639 for doing this sort of thing, though. If you don't like the default
11640 directory chosen, you could say something like:
11643 (setq gnus-message-archive-method
11644 '(nnfolder "archive"
11645 (nnfolder-inhibit-expiry t)
11646 (nnfolder-active-file "~/News/sent-mail/active")
11647 (nnfolder-directory "~/News/sent-mail/")))
11650 @vindex gnus-message-archive-group
11652 Gnus will insert @code{Gcc} headers in all outgoing messages that point
11653 to one or more group(s) on that server. Which group to use is
11654 determined by the @code{gnus-message-archive-group} variable.
11656 This variable can be used to do the following:
11660 Messages will be saved in that group.
11662 Note that you can include a select method in the group name, then the
11663 message will not be stored in the select method given by
11664 @code{gnus-message-archive-method}, but in the select method specified
11665 by the group name, instead. Suppose @code{gnus-message-archive-method}
11666 has the default value shown above. Then setting
11667 @code{gnus-message-archive-group} to @code{"foo"} means that outgoing
11668 messages are stored in @samp{nnfolder+archive:foo}, but if you use the
11669 value @code{"nnml:foo"}, then outgoing messages will be stored in
11672 @item a list of strings
11673 Messages will be saved in all those groups.
11675 @item an alist of regexps, functions and forms
11676 When a key ``matches'', the result is used.
11679 No message archiving will take place. This is the default.
11684 Just saving to a single group called @samp{MisK}:
11686 (setq gnus-message-archive-group "MisK")
11689 Saving to two groups, @samp{MisK} and @samp{safe}:
11691 (setq gnus-message-archive-group '("MisK" "safe"))
11694 Save to different groups based on what group you are in:
11696 (setq gnus-message-archive-group
11697 '(("^alt" "sent-to-alt")
11698 ("mail" "sent-to-mail")
11699 (".*" "sent-to-misc")))
11702 More complex stuff:
11704 (setq gnus-message-archive-group
11705 '((if (message-news-p)
11710 How about storing all news messages in one file, but storing all mail
11711 messages in one file per month:
11714 (setq gnus-message-archive-group
11715 '((if (message-news-p)
11717 (concat "mail." (format-time-string "%Y-%m")))))
11720 @c (XEmacs 19.13 doesn't have @code{format-time-string}, so you'll have to
11721 @c use a different value for @code{gnus-message-archive-group} there.)
11723 Now, when you send a message off, it will be stored in the appropriate
11724 group. (If you want to disable storing for just one particular message,
11725 you can just remove the @code{Gcc} header that has been inserted.) The
11726 archive group will appear in the group buffer the next time you start
11727 gnus, or the next time you press @kbd{F} in the group buffer. You can
11728 enter it and read the articles in it just like you'd read any other
11729 group. If the group gets really big and annoying, you can simply rename
11730 if (using @kbd{G r} in the group buffer) to something
11731 nice---@samp{misc-mail-september-1995}, or whatever. New messages will
11732 continue to be stored in the old (now empty) group.
11734 That's the default method of archiving sent messages. Gnus offers a
11735 different way for the people who don't like the default method. In that
11736 case you should set @code{gnus-message-archive-group} to @code{nil};
11737 this will disable archiving.
11740 @item gnus-outgoing-message-group
11741 @vindex gnus-outgoing-message-group
11742 All outgoing messages will be put in this group. If you want to store
11743 all your outgoing mail and articles in the group @samp{nnml:archive},
11744 you set this variable to that value. This variable can also be a list of
11747 If you want to have greater control over what group to put each
11748 message in, you can set this variable to a function that checks the
11749 current newsgroup name and then returns a suitable group name (or list
11752 This variable can be used instead of @code{gnus-message-archive-group},
11753 but the latter is the preferred method.
11755 @item gnus-gcc-mark-as-read
11756 @vindex gnus-gcc-mark-as-read
11757 If non-@code{nil}, automatically mark @code{Gcc} articles as read.
11759 @item gnus-gcc-externalize-attachments
11760 @vindex gnus-gcc-externalize-attachments
11761 If @code{nil}, attach files as normal parts in Gcc copies; if a regexp
11762 and matches the Gcc group name, attach files as external parts; if it is
11763 @code{all}, attach local files as external parts; if it is other
11764 non-@code{nil}, the behavior is the same as @code{all}, but it may be
11765 changed in the future.
11770 @node Posting Styles
11771 @section Posting Styles
11772 @cindex posting styles
11775 All them variables, they make my head swim.
11777 So what if you want a different @code{Organization} and signature based
11778 on what groups you post to? And you post both from your home machine
11779 and your work machine, and you want different @code{From} lines, and so
11782 @vindex gnus-posting-styles
11783 One way to do stuff like that is to write clever hooks that change the
11784 variables you need to have changed. That's a bit boring, so somebody
11785 came up with the bright idea of letting the user specify these things in
11786 a handy alist. Here's an example of a @code{gnus-posting-styles}
11791 (signature "Peace and happiness")
11792 (organization "What me?"))
11794 (signature "Death to everybody"))
11795 ("comp.emacs.i-love-it"
11796 (organization "Emacs is it")))
11799 As you might surmise from this example, this alist consists of several
11800 @dfn{styles}. Each style will be applicable if the first element
11801 ``matches'', in some form or other. The entire alist will be iterated
11802 over, from the beginning towards the end, and each match will be
11803 applied, which means that attributes in later styles that match override
11804 the same attributes in earlier matching styles. So
11805 @samp{comp.programming.literate} will have the @samp{Death to everybody}
11806 signature and the @samp{What me?} @code{Organization} header.
11808 The first element in each style is called the @code{match}. If it's a
11809 string, then Gnus will try to regexp match it against the group name.
11810 If it is the form @code{(header @var{match} @var{regexp})}, then Gnus
11811 will look in the original article for a header whose name is
11812 @var{match} and compare that @var{regexp}. @var{match} and
11813 @var{regexp} are strings. (The original article is the one you are
11814 replying or following up to. If you are not composing a reply or a
11815 followup, then there is nothing to match against.) If the
11816 @code{match} is a function symbol, that function will be called with
11817 no arguments. If it's a variable symbol, then the variable will be
11818 referenced. If it's a list, then that list will be @code{eval}ed. In
11819 any case, if this returns a non-@code{nil} value, then the style is
11820 said to @dfn{match}.
11822 Each style may contain an arbitrary amount of @dfn{attributes}. Each
11823 attribute consists of a @code{(@var{name} @var{value})} pair. In
11824 addition, you can also use the @code{(@var{name} :file @var{value})}
11825 form or the @code{(@var{name} :value @var{value})} form. Where
11826 @code{:file} signifies @var{value} represents a file name and its
11827 contents should be used as the attribute value, @code{:value} signifies
11828 @var{value} does not represent a file name explicitly. The attribute
11829 name can be one of:
11832 @item @code{signature}
11833 @item @code{signature-file}
11834 @item @code{x-face-file}
11835 @item @code{address}, overriding @code{user-mail-address}
11836 @item @code{name}, overriding @code{(user-full-name)}
11840 The attribute name can also be a string or a symbol. In that case,
11841 this will be used as a header name, and the value will be inserted in
11842 the headers of the article; if the value is @code{nil}, the header
11843 name will be removed. If the attribute name is @code{eval}, the form
11844 is evaluated, and the result is thrown away.
11846 The attribute value can be a string (used verbatim), a function with
11847 zero arguments (the return value will be used), a variable (its value
11848 will be used) or a list (it will be @code{eval}ed and the return value
11849 will be used). The functions and sexps are called/@code{eval}ed in the
11850 message buffer that is being set up. The headers of the current article
11851 are available through the @code{message-reply-headers} variable, which
11852 is a vector of the following headers: number subject from date id
11853 references chars lines xref extra.
11855 @vindex message-reply-headers
11857 If you wish to check whether the message you are about to compose is
11858 meant to be a news article or a mail message, you can check the values
11859 of the @code{message-news-p} and @code{message-mail-p} functions.
11861 @findex message-mail-p
11862 @findex message-news-p
11864 So here's a new example:
11867 (setq gnus-posting-styles
11869 (signature-file "~/.signature")
11871 ("X-Home-Page" (getenv "WWW_HOME"))
11872 (organization "People's Front Against MWM"))
11874 (signature my-funny-signature-randomizer))
11875 ((equal (system-name) "gnarly") ;; @r{A form}
11876 (signature my-quote-randomizer))
11877 (message-news-p ;; @r{A function symbol}
11878 (signature my-news-signature))
11879 (window-system ;; @r{A value symbol}
11880 ("X-Window-System" (format "%s" window-system)))
11881 ;; @r{If I'm replying to Larsi, set the Organization header.}
11882 ((header "from" "larsi.*org")
11883 (Organization "Somewhere, Inc."))
11884 ((posting-from-work-p) ;; @r{A user defined function}
11885 (signature-file "~/.work-signature")
11886 (address "user@@bar.foo")
11887 (body "You are fired.\n\nSincerely, your boss.")
11888 (organization "Important Work, Inc"))
11890 (From (save-excursion
11891 (set-buffer gnus-article-buffer)
11892 (message-fetch-field "to"))))
11894 (signature-file "~/.mail-signature"))))
11897 The @samp{nnml:.*} rule means that you use the @code{To} address as the
11898 @code{From} address in all your outgoing replies, which might be handy
11899 if you fill many roles.
11901 Setting the @code{gnus-named-posting-styles} variable will make
11902 posting-styles allow to have distinctive names. You can specify an
11903 arbitrary posting-style when article posting with @kbd{S P} in the
11904 summary buffer. @code{gnus-named-posting-styles} is an alist which maps
11905 the names to styles. Once a posting-style is added to the alist, we can
11906 import it from @code{gnus-posting-styles}. If an attribute whose name
11907 is @code{import} is found, Gnus will look for the attribute value in
11908 @code{gnus-named-posting-styles} and expand it in place.
11913 (setq gnus-named-posting-styles
11915 (signature-file "~/.signature")
11917 ("X-Home-Page" (getenv "WWW_HOME"))
11918 (organization "People's Front Against MWM"))
11921 (organization "The Church of Emacs"))))
11924 The posting-style named "Emacs" will inherit all the attributes from
11925 "Default" except @code{organization}.
11932 If you are writing a message (mail or news) and suddenly remember that
11933 you have a steak in the oven (or some pesto in the food processor, you
11934 craaazy vegetarians), you'll probably wish there was a method to save
11935 the message you are writing so that you can continue editing it some
11936 other day, and send it when you feel its finished.
11938 Well, don't worry about it. Whenever you start composing a message of
11939 some sort using the gnus mail and post commands, the buffer you get will
11940 automatically associate to an article in a special @dfn{draft} group.
11941 If you save the buffer the normal way (@kbd{C-x C-s}, for instance), the
11942 article will be saved there. (Auto-save files also go to the draft
11946 @vindex nndraft-directory
11947 The draft group is a special group (which is implemented as an
11948 @code{nndraft} group, if you absolutely have to know) called
11949 @samp{nndraft:drafts}. The variable @code{nndraft-directory} says where
11950 @code{nndraft} is to store its files. What makes this group special is
11951 that you can't tick any articles in it or mark any articles as
11952 read---all articles in the group are permanently unread.
11954 If the group doesn't exist, it will be created and you'll be subscribed
11955 to it. The only way to make it disappear from the Group buffer is to
11956 unsubscribe it. The special properties of the draft group comes from
11957 a group property (@pxref{Group Parameters}), and if lost the group
11958 behaves like any other group. This means the commands below will not
11959 be available. To restore the special properties of the group, the
11960 simplest way is to kill the group, using @kbd{C-k}, and restart
11961 Gnus. The group is automatically created again with the
11962 correct parameters. The content of the group is not lost.
11964 @c @findex gnus-dissociate-buffer-from-draft
11965 @c @kindex C-c M-d (Mail)
11966 @c @kindex C-c M-d (Post)
11967 @c @findex gnus-associate-buffer-with-draft
11968 @c @kindex C-c C-d (Mail)
11969 @c @kindex C-c C-d (Post)
11970 @c If you're writing some super-secret message that you later want to
11971 @c encode with PGP before sending, you may wish to turn the auto-saving
11972 @c (and association with the draft group) off. You never know who might be
11973 @c interested in reading all your extremely valuable and terribly horrible
11974 @c and interesting secrets. The @kbd{C-c M-d}
11975 @c (@code{gnus-dissociate-buffer-from-draft}) command does that for you.
11976 @c If you change your mind and want to turn the auto-saving back on again,
11977 @c @kbd{C-c C-d} (@code{gnus-associate-buffer-with-draft} does that.
11979 @c @vindex gnus-use-draft
11980 @c To leave association with the draft group off by default, set
11981 @c @code{gnus-use-draft} to @code{nil}. It is @code{t} by default.
11983 @findex gnus-draft-edit-message
11984 @kindex D e (Draft)
11985 When you want to continue editing the article, you simply enter the
11986 draft group and push @kbd{D e} (@code{gnus-draft-edit-message}) to do
11987 that. You will be placed in a buffer where you left off.
11989 Rejected articles will also be put in this draft group (@pxref{Rejected
11992 @findex gnus-draft-send-all-messages
11993 @kindex D s (Draft)
11994 @findex gnus-draft-send-message
11995 @kindex D S (Draft)
11996 If you have lots of rejected messages you want to post (or mail) without
11997 doing further editing, you can use the @kbd{D s} command
11998 (@code{gnus-draft-send-message}). This command understands the
11999 process/prefix convention (@pxref{Process/Prefix}). The @kbd{D S}
12000 command (@code{gnus-draft-send-all-messages}) will ship off all messages
12003 @findex gnus-draft-toggle-sending
12004 @kindex D t (Draft)
12005 If you have some messages that you wish not to send, you can use the
12006 @kbd{D t} (@code{gnus-draft-toggle-sending}) command to mark the message
12007 as unsendable. This is a toggling command.
12010 @node Rejected Articles
12011 @section Rejected Articles
12012 @cindex rejected articles
12014 Sometimes a news server will reject an article. Perhaps the server
12015 doesn't like your face. Perhaps it just feels miserable. Perhaps
12016 @emph{there be demons}. Perhaps you have included too much cited text.
12017 Perhaps the disk is full. Perhaps the server is down.
12019 These situations are, of course, totally beyond the control of gnus.
12020 (Gnus, of course, loves the way you look, always feels great, has angels
12021 fluttering around inside of it, doesn't care about how much cited text
12022 you include, never runs full and never goes down.) So gnus saves these
12023 articles until some later time when the server feels better.
12025 The rejected articles will automatically be put in a special draft group
12026 (@pxref{Drafts}). When the server comes back up again, you'd then
12027 typically enter that group and send all the articles off.
12029 @node Signing and encrypting
12030 @section Signing and encrypting
12032 @cindex using s/mime
12033 @cindex using smime
12035 Gnus can digitally sign and encrypt your messages, using vanilla
12036 @acronym{PGP} format or @acronym{PGP/MIME} or @acronym{S/MIME}. For
12037 decoding such messages, see the @code{mm-verify-option} and
12038 @code{mm-decrypt-option} options (@pxref{Security}).
12040 @vindex gnus-message-replysign
12041 @vindex gnus-message-replyencrypt
12042 @vindex gnus-message-replysignencrypted
12043 Often, you would like to sign replies to people who send you signed
12044 messages. Even more often, you might want to encrypt messages which
12045 are in reply to encrypted messages. Gnus offers
12046 @code{gnus-message-replysign} to enable the former, and
12047 @code{gnus-message-replyencrypt} for the latter. In addition, setting
12048 @code{gnus-message-replysignencrypted} (on by default) will sign
12049 automatically encrypted messages.
12051 Instructing @acronym{MML} to perform security operations on a
12052 @acronym{MIME} part is done using the @kbd{C-c C-m s} key map for
12053 signing and the @kbd{C-c C-m c} key map for encryption, as follows.
12058 @kindex C-c C-m s s (Message)
12059 @findex mml-secure-message-sign-smime
12061 Digitally sign current message using @acronym{S/MIME}.
12064 @kindex C-c C-m s o (Message)
12065 @findex mml-secure-message-sign-pgp
12067 Digitally sign current message using @acronym{PGP}.
12070 @kindex C-c C-m s p (Message)
12071 @findex mml-secure-message-sign-pgp
12073 Digitally sign current message using @acronym{PGP/MIME}.
12076 @kindex C-c C-m c s (Message)
12077 @findex mml-secure-message-encrypt-smime
12079 Digitally encrypt current message using @acronym{S/MIME}.
12082 @kindex C-c C-m c o (Message)
12083 @findex mml-secure-message-encrypt-pgp
12085 Digitally encrypt current message using @acronym{PGP}.
12088 @kindex C-c C-m c p (Message)
12089 @findex mml-secure-message-encrypt-pgpmime
12091 Digitally encrypt current message using @acronym{PGP/MIME}.
12094 @kindex C-c C-m C-n (Message)
12095 @findex mml-unsecure-message
12096 Remove security related @acronym{MML} tags from message.
12100 @xref{Security, ,Security, message, Message Manual}, for more information.
12102 @node Select Methods
12103 @chapter Select Methods
12104 @cindex foreign groups
12105 @cindex select methods
12107 A @dfn{foreign group} is a group not read by the usual (or
12108 default) means. It could be, for instance, a group from a different
12109 @acronym{NNTP} server, it could be a virtual group, or it could be your own
12110 personal mail group.
12112 A foreign group (or any group, really) is specified by a @dfn{name} and
12113 a @dfn{select method}. To take the latter first, a select method is a
12114 list where the first element says what back end to use (e.g. @code{nntp},
12115 @code{nnspool}, @code{nnml}) and the second element is the @dfn{server
12116 name}. There may be additional elements in the select method, where the
12117 value may have special meaning for the back end in question.
12119 One could say that a select method defines a @dfn{virtual server}---so
12120 we do just that (@pxref{Server Buffer}).
12122 The @dfn{name} of the group is the name the back end will recognize the
12125 For instance, the group @samp{soc.motss} on the @acronym{NNTP} server
12126 @samp{some.where.edu} will have the name @samp{soc.motss} and select
12127 method @code{(nntp "some.where.edu")}. Gnus will call this group
12128 @samp{nntp+some.where.edu:soc.motss}, even though the @code{nntp}
12129 back end just knows this group as @samp{soc.motss}.
12131 The different methods all have their peculiarities, of course.
12134 * Server Buffer:: Making and editing virtual servers.
12135 * Getting News:: Reading USENET news with Gnus.
12136 * Getting Mail:: Reading your personal mail with Gnus.
12137 * Browsing the Web:: Getting messages from a plethora of Web sources.
12138 * IMAP:: Using Gnus as a @acronym{IMAP} client.
12139 * Other Sources:: Reading directories, files, SOUP packets.
12140 * Combined Groups:: Combining groups into one group.
12141 * Gnus Unplugged:: Reading news and mail offline.
12145 @node Server Buffer
12146 @section Server Buffer
12148 Traditionally, a @dfn{server} is a machine or a piece of software that
12149 one connects to, and then requests information from. Gnus does not
12150 connect directly to any real servers, but does all transactions through
12151 one back end or other. But that's just putting one layer more between
12152 the actual media and Gnus, so we might just as well say that each
12153 back end represents a virtual server.
12155 For instance, the @code{nntp} back end may be used to connect to several
12156 different actual @acronym{NNTP} servers, or, perhaps, to many different ports
12157 on the same actual @acronym{NNTP} server. You tell Gnus which back end to
12158 use, and what parameters to set by specifying a @dfn{select method}.
12160 These select method specifications can sometimes become quite
12161 complicated---say, for instance, that you want to read from the
12162 @acronym{NNTP} server @samp{news.funet.fi} on port number 13, which
12163 hangs if queried for @acronym{NOV} headers and has a buggy select. Ahem.
12164 Anyway, if you had to specify that for each group that used this
12165 server, that would be too much work, so Gnus offers a way of naming
12166 select methods, which is what you do in the server buffer.
12168 To enter the server buffer, use the @kbd{^}
12169 (@code{gnus-group-enter-server-mode}) command in the group buffer.
12172 * Server Buffer Format:: You can customize the look of this buffer.
12173 * Server Commands:: Commands to manipulate servers.
12174 * Example Methods:: Examples server specifications.
12175 * Creating a Virtual Server:: An example session.
12176 * Server Variables:: Which variables to set.
12177 * Servers and Methods:: You can use server names as select methods.
12178 * Unavailable Servers:: Some servers you try to contact may be down.
12181 @vindex gnus-server-mode-hook
12182 @code{gnus-server-mode-hook} is run when creating the server buffer.
12185 @node Server Buffer Format
12186 @subsection Server Buffer Format
12187 @cindex server buffer format
12189 @vindex gnus-server-line-format
12190 You can change the look of the server buffer lines by changing the
12191 @code{gnus-server-line-format} variable. This is a @code{format}-like
12192 variable, with some simple extensions:
12197 How the news is fetched---the back end name.
12200 The name of this server.
12203 Where the news is to be fetched from---the address.
12206 The opened/closed/denied status of the server.
12209 @vindex gnus-server-mode-line-format
12210 The mode line can also be customized by using the
12211 @code{gnus-server-mode-line-format} variable (@pxref{Mode Line
12212 Formatting}). The following specs are understood:
12222 Also @pxref{Formatting Variables}.
12225 @node Server Commands
12226 @subsection Server Commands
12227 @cindex server commands
12233 @findex gnus-server-add-server
12234 Add a new server (@code{gnus-server-add-server}).
12238 @findex gnus-server-edit-server
12239 Edit a server (@code{gnus-server-edit-server}).
12242 @kindex SPACE (Server)
12243 @findex gnus-server-read-server
12244 Browse the current server (@code{gnus-server-read-server}).
12248 @findex gnus-server-exit
12249 Return to the group buffer (@code{gnus-server-exit}).
12253 @findex gnus-server-kill-server
12254 Kill the current server (@code{gnus-server-kill-server}).
12258 @findex gnus-server-yank-server
12259 Yank the previously killed server (@code{gnus-server-yank-server}).
12263 @findex gnus-server-copy-server
12264 Copy the current server (@code{gnus-server-copy-server}).
12268 @findex gnus-server-list-servers
12269 List all servers (@code{gnus-server-list-servers}).
12273 @findex gnus-server-scan-server
12274 Request that the server scan its sources for new articles
12275 (@code{gnus-server-scan-server}). This is mainly sensible with mail
12280 @findex gnus-server-regenerate-server
12281 Request that the server regenerate all its data structures
12282 (@code{gnus-server-regenerate-server}). This can be useful if you have
12283 a mail back end that has gotten out of sync.
12288 @node Example Methods
12289 @subsection Example Methods
12291 Most select methods are pretty simple and self-explanatory:
12294 (nntp "news.funet.fi")
12297 Reading directly from the spool is even simpler:
12303 As you can see, the first element in a select method is the name of the
12304 back end, and the second is the @dfn{address}, or @dfn{name}, if you
12307 After these two elements, there may be an arbitrary number of
12308 @code{(@var{variable} @var{form})} pairs.
12310 To go back to the first example---imagine that you want to read from
12311 port 15 on that machine. This is what the select method should
12315 (nntp "news.funet.fi" (nntp-port-number 15))
12318 You should read the documentation to each back end to find out what
12319 variables are relevant, but here's an @code{nnmh} example:
12321 @code{nnmh} is a mail back end that reads a spool-like structure. Say
12322 you have two structures that you wish to access: One is your private
12323 mail spool, and the other is a public one. Here's the possible spec for
12327 (nnmh "private" (nnmh-directory "~/private/mail/"))
12330 (This server is then called @samp{private}, but you may have guessed
12333 Here's the method for a public spool:
12337 (nnmh-directory "/usr/information/spool/")
12338 (nnmh-get-new-mail nil))
12344 If you are behind a firewall and only have access to the @acronym{NNTP}
12345 server from the firewall machine, you can instruct Gnus to @code{rlogin}
12346 on the firewall machine and telnet from there to the @acronym{NNTP} server.
12347 Doing this can be rather fiddly, but your virtual server definition
12348 should probably look something like this:
12352 (nntp-open-connection-function nntp-open-via-rlogin-and-telnet)
12353 (nntp-via-address "the.firewall.machine")
12354 (nntp-address "the.real.nntp.host")
12355 (nntp-end-of-line "\n"))
12358 If you want to use the wonderful @code{ssh} program to provide a
12359 compressed connection over the modem line, you could add the following
12360 configuration to the example above:
12363 (nntp-via-rlogin-command "ssh")
12366 See also @code{nntp-via-rlogin-command-switches}.
12368 If you're behind a firewall, but have direct access to the outside world
12369 through a wrapper command like "runsocks", you could open a socksified
12370 telnet connection to the news server as follows:
12374 (nntp-pre-command "runsocks")
12375 (nntp-open-connection-function nntp-open-via-telnet)
12376 (nntp-address "the.news.server")
12377 (nntp-end-of-line "\n"))
12380 This means that you have to have set up @code{ssh-agent} correctly to
12381 provide automatic authorization, of course. And to get a compressed
12382 connection, you have to have the @samp{Compression} option in the
12383 @code{ssh} @file{config} file.
12386 @node Creating a Virtual Server
12387 @subsection Creating a Virtual Server
12389 If you're saving lots of articles in the cache by using persistent
12390 articles, you may want to create a virtual server to read the cache.
12392 First you need to add a new server. The @kbd{a} command does that. It
12393 would probably be best to use @code{nnml} to read the cache. You
12394 could also use @code{nnspool} or @code{nnmh}, though.
12396 Type @kbd{a nnml RET cache RET}.
12398 You should now have a brand new @code{nnml} virtual server called
12399 @samp{cache}. You now need to edit it to have the right definitions.
12400 Type @kbd{e} to edit the server. You'll be entered into a buffer that
12401 will contain the following:
12411 (nnml-directory "~/News/cache/")
12412 (nnml-active-file "~/News/cache/active"))
12415 Type @kbd{C-c C-c} to return to the server buffer. If you now press
12416 @kbd{RET} over this virtual server, you should be entered into a browse
12417 buffer, and you should be able to enter any of the groups displayed.
12420 @node Server Variables
12421 @subsection Server Variables
12422 @cindex server variables
12423 @cindex server parameters
12425 One sticky point when defining variables (both on back ends and in Emacs
12426 in general) is that some variables are typically initialized from other
12427 variables when the definition of the variables is being loaded. If you
12428 change the ``base'' variable after the variables have been loaded, you
12429 won't change the ``derived'' variables.
12431 This typically affects directory and file variables. For instance,
12432 @code{nnml-directory} is @file{~/Mail/} by default, and all @code{nnml}
12433 directory variables are initialized from that variable, so
12434 @code{nnml-active-file} will be @file{~/Mail/active}. If you define a
12435 new virtual @code{nnml} server, it will @emph{not} suffice to set just
12436 @code{nnml-directory}---you have to explicitly set all the file
12437 variables to be what you want them to be. For a complete list of
12438 variables for each back end, see each back end's section later in this
12439 manual, but here's an example @code{nnml} definition:
12443 (nnml-directory "~/my-mail/")
12444 (nnml-active-file "~/my-mail/active")
12445 (nnml-newsgroups-file "~/my-mail/newsgroups"))
12448 Server variables are often called @dfn{server parameters}.
12450 @node Servers and Methods
12451 @subsection Servers and Methods
12453 Wherever you would normally use a select method
12454 (e.g. @code{gnus-secondary-select-method}, in the group select method,
12455 when browsing a foreign server) you can use a virtual server name
12456 instead. This could potentially save lots of typing. And it's nice all
12460 @node Unavailable Servers
12461 @subsection Unavailable Servers
12463 If a server seems to be unreachable, Gnus will mark that server as
12464 @code{denied}. That means that any subsequent attempt to make contact
12465 with that server will just be ignored. ``It can't be opened,'' Gnus
12466 will tell you, without making the least effort to see whether that is
12467 actually the case or not.
12469 That might seem quite naughty, but it does make sense most of the time.
12470 Let's say you have 10 groups subscribed to on server
12471 @samp{nephelococcygia.com}. This server is located somewhere quite far
12472 away from you and the machine is quite slow, so it takes 1 minute just
12473 to find out that it refuses connection to you today. If Gnus were to
12474 attempt to do that 10 times, you'd be quite annoyed, so Gnus won't
12475 attempt to do that. Once it has gotten a single ``connection refused'',
12476 it will regard that server as ``down''.
12478 So, what happens if the machine was only feeling unwell temporarily?
12479 How do you test to see whether the machine has come up again?
12481 You jump to the server buffer (@pxref{Server Buffer}) and poke it
12482 with the following commands:
12488 @findex gnus-server-open-server
12489 Try to establish connection to the server on the current line
12490 (@code{gnus-server-open-server}).
12494 @findex gnus-server-close-server
12495 Close the connection (if any) to the server
12496 (@code{gnus-server-close-server}).
12500 @findex gnus-server-deny-server
12501 Mark the current server as unreachable
12502 (@code{gnus-server-deny-server}).
12505 @kindex M-o (Server)
12506 @findex gnus-server-open-all-servers
12507 Open the connections to all servers in the buffer
12508 (@code{gnus-server-open-all-servers}).
12511 @kindex M-c (Server)
12512 @findex gnus-server-close-all-servers
12513 Close the connections to all servers in the buffer
12514 (@code{gnus-server-close-all-servers}).
12518 @findex gnus-server-remove-denials
12519 Remove all marks to whether Gnus was denied connection from any servers
12520 (@code{gnus-server-remove-denials}).
12524 @findex gnus-server-offline-server
12525 Set server status to offline (@code{gnus-server-offline-server}).
12531 @section Getting News
12532 @cindex reading news
12533 @cindex news back ends
12535 A newsreader is normally used for reading news. Gnus currently provides
12536 only two methods of getting news---it can read from an @acronym{NNTP} server,
12537 or it can read from a local spool.
12540 * NNTP:: Reading news from an @acronym{NNTP} server.
12541 * News Spool:: Reading news from the local spool.
12549 Subscribing to a foreign group from an @acronym{NNTP} server is rather easy.
12550 You just specify @code{nntp} as method and the address of the @acronym{NNTP}
12551 server as the, uhm, address.
12553 If the @acronym{NNTP} server is located at a non-standard port, setting the
12554 third element of the select method to this port number should allow you
12555 to connect to the right port. You'll have to edit the group info for
12556 that (@pxref{Foreign Groups}).
12558 The name of the foreign group can be the same as a native group. In
12559 fact, you can subscribe to the same group from as many different servers
12560 you feel like. There will be no name collisions.
12562 The following variables can be used to create a virtual @code{nntp}
12567 @item nntp-server-opened-hook
12568 @vindex nntp-server-opened-hook
12569 @cindex @sc{mode reader}
12571 @cindex authentification
12572 @cindex nntp authentification
12573 @findex nntp-send-authinfo
12574 @findex nntp-send-mode-reader
12575 is run after a connection has been made. It can be used to send
12576 commands to the @acronym{NNTP} server after it has been contacted. By
12577 default it sends the command @code{MODE READER} to the server with the
12578 @code{nntp-send-mode-reader} function. This function should always be
12579 present in this hook.
12581 @item nntp-authinfo-function
12582 @vindex nntp-authinfo-function
12583 @findex nntp-send-authinfo
12584 @vindex nntp-authinfo-file
12585 This function will be used to send @samp{AUTHINFO} to the @acronym{NNTP}
12586 server. The default function is @code{nntp-send-authinfo}, which looks
12587 through your @file{~/.authinfo} (or whatever you've set the
12588 @code{nntp-authinfo-file} variable to) for applicable entries. If none
12589 are found, it will prompt you for a login name and a password. The
12590 format of the @file{~/.authinfo} file is (almost) the same as the
12591 @code{ftp} @file{~/.netrc} file, which is defined in the @code{ftp}
12592 manual page, but here are the salient facts:
12596 The file contains one or more line, each of which define one server.
12599 Each line may contain an arbitrary number of token/value pairs.
12601 The valid tokens include @samp{machine}, @samp{login}, @samp{password},
12602 @samp{default}. In addition Gnus introduces two new tokens, not present
12603 in the original @file{.netrc}/@code{ftp} syntax, namely @samp{port} and
12604 @samp{force}. (This is the only way the @file{.authinfo} file format
12605 deviates from the @file{.netrc} file format.) @samp{port} is used to
12606 indicate what port on the server the credentials apply to and
12607 @samp{force} is explained below.
12611 Here's an example file:
12614 machine news.uio.no login larsi password geheimnis
12615 machine nntp.ifi.uio.no login larsi force yes
12618 The token/value pairs may appear in any order; @samp{machine} doesn't
12619 have to be first, for instance.
12621 In this example, both login name and password have been supplied for the
12622 former server, while the latter has only the login name listed, and the
12623 user will be prompted for the password. The latter also has the
12624 @samp{force} tag, which means that the authinfo will be sent to the
12625 @var{nntp} server upon connection; the default (i.e., when there is not
12626 @samp{force} tag) is to not send authinfo to the @var{nntp} server
12627 until the @var{nntp} server asks for it.
12629 You can also add @samp{default} lines that will apply to all servers
12630 that don't have matching @samp{machine} lines.
12636 This will force sending @samp{AUTHINFO} commands to all servers not
12637 previously mentioned.
12639 Remember to not leave the @file{~/.authinfo} file world-readable.
12641 @item nntp-server-action-alist
12642 @vindex nntp-server-action-alist
12643 This is a list of regexps to match on server types and actions to be
12644 taken when matches are made. For instance, if you want Gnus to beep
12645 every time you connect to innd, you could say something like:
12648 (setq nntp-server-action-alist
12649 '(("innd" (ding))))
12652 You probably don't want to do that, though.
12654 The default value is
12657 '(("nntpd 1\\.5\\.11t"
12658 (remove-hook 'nntp-server-opened-hook
12659 'nntp-send-mode-reader)))
12662 This ensures that Gnus doesn't send the @code{MODE READER} command to
12663 nntpd 1.5.11t, since that command chokes that server, I've been told.
12665 @item nntp-maximum-request
12666 @vindex nntp-maximum-request
12667 If the @acronym{NNTP} server doesn't support @acronym{NOV} headers, this back end
12668 will collect headers by sending a series of @code{head} commands. To
12669 speed things up, the back end sends lots of these commands without
12670 waiting for reply, and then reads all the replies. This is controlled
12671 by the @code{nntp-maximum-request} variable, and is 400 by default. If
12672 your network is buggy, you should set this to 1.
12674 @item nntp-connection-timeout
12675 @vindex nntp-connection-timeout
12676 If you have lots of foreign @code{nntp} groups that you connect to
12677 regularly, you're sure to have problems with @acronym{NNTP} servers not
12678 responding properly, or being too loaded to reply within reasonable
12679 time. This is can lead to awkward problems, which can be helped
12680 somewhat by setting @code{nntp-connection-timeout}. This is an integer
12681 that says how many seconds the @code{nntp} back end should wait for a
12682 connection before giving up. If it is @code{nil}, which is the default,
12683 no timeouts are done.
12685 @c @item nntp-command-timeout
12686 @c @vindex nntp-command-timeout
12687 @c @cindex PPP connections
12688 @c @cindex dynamic IP addresses
12689 @c If you're running Gnus on a machine that has a dynamically assigned
12690 @c address, Gnus may become confused. If the address of your machine
12691 @c changes after connecting to the @acronym{NNTP} server, Gnus will simply sit
12692 @c waiting forever for replies from the server. To help with this
12693 @c unfortunate problem, you can set this command to a number. Gnus will
12694 @c then, if it sits waiting for a reply from the server longer than that
12695 @c number of seconds, shut down the connection, start a new one, and resend
12696 @c the command. This should hopefully be transparent to the user. A
12697 @c likely number is 30 seconds.
12699 @c @item nntp-retry-on-break
12700 @c @vindex nntp-retry-on-break
12701 @c If this variable is non-@code{nil}, you can also @kbd{C-g} if Gnus
12702 @c hangs. This will have much the same effect as the command timeout
12703 @c described above.
12705 @item nntp-server-hook
12706 @vindex nntp-server-hook
12707 This hook is run as the last step when connecting to an @acronym{NNTP}
12710 @item nntp-buggy-select
12711 @vindex nntp-buggy-select
12712 Set this to non-@code{nil} if your select routine is buggy.
12714 @item nntp-nov-is-evil
12715 @vindex nntp-nov-is-evil
12716 If the @acronym{NNTP} server does not support @acronym{NOV}, you could set this
12717 variable to @code{t}, but @code{nntp} usually checks automatically whether @acronym{NOV}
12720 @item nntp-xover-commands
12721 @vindex nntp-xover-commands
12722 @cindex @acronym{NOV}
12724 List of strings used as commands to fetch @acronym{NOV} lines from a
12725 server. The default value of this variable is @code{("XOVER"
12729 @vindex nntp-nov-gap
12730 @code{nntp} normally sends just one big request for @acronym{NOV} lines to
12731 the server. The server responds with one huge list of lines. However,
12732 if you have read articles 2-5000 in the group, and only want to read
12733 article 1 and 5001, that means that @code{nntp} will fetch 4999 @acronym{NOV}
12734 lines that you will not need. This variable says how
12735 big a gap between two consecutive articles is allowed to be before the
12736 @code{XOVER} request is split into several request. Note that if your
12737 network is fast, setting this variable to a really small number means
12738 that fetching will probably be slower. If this variable is @code{nil},
12739 @code{nntp} will never split requests. The default is 5.
12741 @item nntp-prepare-server-hook
12742 @vindex nntp-prepare-server-hook
12743 A hook run before attempting to connect to an @acronym{NNTP} server.
12745 @item nntp-warn-about-losing-connection
12746 @vindex nntp-warn-about-losing-connection
12747 If this variable is non-@code{nil}, some noise will be made when a
12748 server closes connection.
12750 @item nntp-record-commands
12751 @vindex nntp-record-commands
12752 If non-@code{nil}, @code{nntp} will log all commands it sends to the
12753 @acronym{NNTP} server (along with a timestamp) in the @samp{*nntp-log*}
12754 buffer. This is useful if you are debugging a Gnus/@acronym{NNTP} connection
12755 that doesn't seem to work.
12757 @item nntp-open-connection-function
12758 @vindex nntp-open-connection-function
12759 It is possible to customize how the connection to the nntp server will
12760 be opened. If you specify an @code{nntp-open-connection-function}
12761 parameter, Gnus will use that function to establish the connection.
12762 Five pre-made functions are supplied. These functions can be grouped in
12763 two categories: direct connection functions (three pre-made), and
12764 indirect ones (two pre-made).
12766 @item nntp-prepare-post-hook
12767 @vindex nntp-prepare-post-hook
12768 A hook run just before posting an article. If there is no
12769 @code{Message-ID} header in the article and the news server provides the
12770 recommended ID, it will be added to the article before running this
12771 hook. It is useful to make @code{Cancel-Lock} headers even if you
12772 inhibit Gnus to add a @code{Message-ID} header, you could say:
12775 (add-hook 'nntp-prepare-post-hook 'canlock-insert-header)
12778 Note that not all servers support the recommended ID. This works for
12779 INN versions 2.3.0 and later, for instance.
12781 @item nntp-read-timeout
12782 @vindex nntp-read-timeout
12783 How long nntp should wait between checking for the end of output.
12784 Shorter values mean quicker response, but is more CPU intensive. The
12785 default is 0.1 seconds. If you have a slow line to the server (and
12786 don't like to see Emacs eat your available CPU power), you might set
12789 @item nntp-list-options
12790 @vindex nntp-list-options
12791 List of newsgroup name used for a option of the LIST command to restrict
12792 the listing output to only the specified newsgroups. Each newsgroup name
12793 can be a shell-style wildcard, for instance, @dfn{fj.*}, @dfn{japan.*},
12794 etc. Fortunately, if the server can accept such a option, it will
12795 probably make gnus run faster. You may use it as a server variable as
12799 (setq gnus-select-method
12800 '(nntp "news.somewhere.edu"
12801 (nntp-list-options ("fj.*" "japan.*"))))
12804 @item nntp-options-subscribe
12805 @vindex nntp-options-subscribe
12806 Regexp matching the newsgroup names which will be subscribed
12807 unconditionally. Use @dfn{ } instead of @dfn{$} for a regexp string.
12808 It may be effective as well as @code{nntp-list-options} even though the
12809 server could not accept a shell-style wildcard as a option of the LIST
12810 command. You may use it as a server variable as follows:
12813 (setq gnus-select-method
12814 '(nntp "news.somewhere.edu"
12815 (nntp-options-subscribe "^fj\\.\\|^japan\\.")))
12818 @item nntp-options-not-subscribe
12819 @vindex nntp-options-not-subscribe
12820 Regexp matching the newsgroup names which will not be subscribed
12821 unconditionally. Use @dfn{ } instead of @dfn{$} for a regexp string.
12822 It may be effective as well as @code{nntp-list-options} even though the
12823 server could not accept a shell-style wildcard as a option of the LIST
12824 command. You may use it as a server variable as follows:
12827 (setq gnus-select-method
12828 '(nntp "news.somewhere.edu"
12829 (nntp-options-not-subscribe "\\.binaries\\.")))
12834 * Direct Functions:: Connecting directly to the server.
12835 * Indirect Functions:: Connecting indirectly to the server.
12836 * Common Variables:: Understood by several connection functions.
12837 * NNTP marks:: Storing marks for @acronym{NNTP} servers.
12841 @node Direct Functions
12842 @subsubsection Direct Functions
12843 @cindex direct connection functions
12845 These functions are called direct because they open a direct connection
12846 between your machine and the @acronym{NNTP} server. The behavior of these
12847 functions is also affected by commonly understood variables
12848 (@pxref{Common Variables}).
12851 @findex nntp-open-network-stream
12852 @item nntp-open-network-stream
12853 This is the default, and simply connects to some port or other on the
12856 @findex nntp-open-tls-stream
12857 @item nntp-open-tls-stream
12858 Opens a connection to a server over a @dfn{secure} channel. To use
12859 this you must have @uref{http://www.gnu.org/software/gnutls/, GNUTLS}
12860 installed. You then define a server as follows:
12863 ;; @r{"nntps" is port 563 and is predefined in our @file{/etc/services}}
12864 ;; @r{however, @samp{gnutls-cli -p} doesn't like named ports.}
12866 (nntp "snews.bar.com"
12867 (nntp-open-connection-function nntp-open-tls-stream)
12868 (nntp-port-number )
12869 (nntp-address "snews.bar.com"))
12872 @findex nntp-open-ssl-stream
12873 @item nntp-open-ssl-stream
12874 Opens a connection to a server over a @dfn{secure} channel. To use
12875 this you must have @uref{http://www.openssl.org, OpenSSL} or
12876 @uref{ftp://ftp.psy.uq.oz.au/pub/Crypto/SSL, SSLeay} installed. You
12877 then define a server as follows:
12880 ;; @r{"snews" is port 563 and is predefined in our @file{/etc/services}}
12881 ;; @r{however, @samp{openssl s_client -port} doesn't like named ports.}
12883 (nntp "snews.bar.com"
12884 (nntp-open-connection-function nntp-open-ssl-stream)
12885 (nntp-port-number 563)
12886 (nntp-address "snews.bar.com"))
12889 @findex nntp-open-telnet-stream
12890 @item nntp-open-telnet-stream
12891 Opens a connection to an @acronym{NNTP} server by simply @samp{telnet}'ing
12892 it. You might wonder why this function exists, since we have the
12893 default @code{nntp-open-network-stream} which would do the job. (One
12894 of) the reason(s) is that if you are behind a firewall but have direct
12895 connections to the outside world thanks to a command wrapper like
12896 @code{runsocks}, you can use it like this:
12900 (nntp-pre-command "runsocks")
12901 (nntp-open-connection-function nntp-open-telnet-stream)
12902 (nntp-address "the.news.server"))
12905 With the default method, you would need to wrap your whole Emacs
12906 session, which is not a good idea.
12910 @node Indirect Functions
12911 @subsubsection Indirect Functions
12912 @cindex indirect connection functions
12914 These functions are called indirect because they connect to an
12915 intermediate host before actually connecting to the @acronym{NNTP} server.
12916 All of these functions and related variables are also said to belong to
12917 the ``via'' family of connection: they're all prefixed with ``via'' to make
12918 things cleaner. The behavior of these functions is also affected by
12919 commonly understood variables (@pxref{Common Variables}).
12922 @item nntp-open-via-rlogin-and-telnet
12923 @findex nntp-open-via-rlogin-and-telnet
12924 Does an @samp{rlogin} on a remote system, and then does a @samp{telnet}
12925 to the real @acronym{NNTP} server from there. This is useful for instance if
12926 you need to connect to a firewall machine first.
12928 @code{nntp-open-via-rlogin-and-telnet}-specific variables:
12931 @item nntp-via-rlogin-command
12932 @vindex nntp-via-rlogin-command
12933 Command used to log in on the intermediate host. The default is
12934 @samp{rsh}, but @samp{ssh} is a popular alternative.
12936 @item nntp-via-rlogin-command-switches
12937 @vindex nntp-via-rlogin-command-switches
12938 List of strings to be used as the switches to
12939 @code{nntp-via-rlogin-command}. The default is @code{nil}. If you use
12940 @samp{ssh} for @code{nntp-via-rlogin-command}, you may set this to
12941 @samp{("-C")} in order to compress all data connections, otherwise set
12942 this to @samp{("-t" "-e" "none")} or @samp{("-C" "-t" "-e" "none")} if
12943 the telnet command requires a pseudo-tty allocation on an intermediate
12947 Note that you may want to change the value for @code{nntp-end-of-line}
12948 to @samp{\n} (@pxref{Common Variables}).
12950 @item nntp-open-via-rlogin-and-netcat
12951 @findex nntp-open-via-rlogin-and-netcat
12952 Does essentially the same, but uses @samp{netcat}
12953 (@uref{http://netcat.sourceforge.net/}) instead of @samp{telnet} to
12954 connect to the real @acronym{NNTP} server from the intermediate host.
12956 @code{nntp-open-via-rlogin-and-netcat}-specific variables:
12959 @item nntp-via-netcat-command
12960 @vindex nntp-via-netcat-command
12961 Command used to connect to the real @acronym{NNTP} server from the
12962 intermediate host. The default is @samp{nc}. You can also use other
12963 programs like @samp{connect}
12964 (@uref{http://www.imasy.or.jp/~gotoh/ssh/connect.html}) instead.
12966 @item nntp-via-netcat-switches
12967 @vindex nntp-via-netcat-switches
12968 List of strings to be used as the switches to the
12969 @code{nntp-via-telnet-command} command. The default is @code{nil}.
12971 @item nntp-via-rlogin-command
12972 Command used to log in on the intermediate host. The default is
12973 @samp{rsh}, but @samp{ssh} is a popular alternative.
12975 @item nntp-via-rlogin-command-switches
12976 List of strings to be used as the switches to
12977 @code{nntp-via-rlogin-command}. The default is @code{nil}.
12980 @item nntp-open-via-telnet-and-telnet
12981 @findex nntp-open-via-telnet-and-telnet
12982 Does essentially also the same, but uses @samp{telnet} instead of
12983 @samp{rlogin} to connect to the intermediate host.
12985 @code{nntp-open-via-telnet-and-telnet}-specific variables:
12988 @item nntp-via-telnet-command
12989 @vindex nntp-via-telnet-command
12990 Command used to @code{telnet} the intermediate host. The default is
12993 @item nntp-via-telnet-switches
12994 @vindex nntp-via-telnet-switches
12995 List of strings to be used as the switches to the
12996 @code{nntp-via-telnet-command} command. The default is @samp{("-8")}.
12998 @item nntp-via-user-password
12999 @vindex nntp-via-user-password
13000 Password to use when logging in on the intermediate host.
13002 @item nntp-via-envuser
13003 @vindex nntp-via-envuser
13004 If non-@code{nil}, the intermediate @code{telnet} session (client and
13005 server both) will support the @code{ENVIRON} option and not prompt for
13006 login name. This works for Solaris @code{telnet}, for instance.
13008 @item nntp-via-shell-prompt
13009 @vindex nntp-via-shell-prompt
13010 Regexp matching the shell prompt on the intermediate host. The default
13011 is @samp{bash\\|\$ *\r?$\\|> *\r?}.
13015 Note that you may want to change the value for @code{nntp-end-of-line}
13016 to @samp{\n} (@pxref{Common Variables}).
13020 Here are some additional variables that are understood by all the above
13025 @item nntp-via-user-name
13026 @vindex nntp-via-user-name
13027 User name to use when connecting to the intermediate host.
13029 @item nntp-via-address
13030 @vindex nntp-via-address
13031 Address of the intermediate host to connect to.
13036 @node Common Variables
13037 @subsubsection Common Variables
13039 The following variables affect the behavior of all, or several of the
13040 pre-made connection functions. When not specified, all functions are
13045 @item nntp-pre-command
13046 @vindex nntp-pre-command
13047 A command wrapper to use when connecting through a non native
13048 connection function (all except @code{nntp-open-network-stream},
13049 @code{nntp-open-tls-stream}, and @code{nntp-open-ssl-stream}. This is
13050 where you would put a @samp{SOCKS} wrapper for instance.
13053 @vindex nntp-address
13054 The address of the @acronym{NNTP} server.
13056 @item nntp-port-number
13057 @vindex nntp-port-number
13058 Port number to connect to the @acronym{NNTP} server. The default is
13059 @samp{nntp}. If you use @acronym{NNTP} over
13060 @acronym{TLS}/@acronym{SSL}, you may want to use integer ports rather
13061 than named ports (i.e, use @samp{563} instead of @samp{snews} or
13062 @samp{nntps}), because external @acronym{TLS}/@acronym{SSL} tools may
13063 not work with named ports.
13065 @item nntp-end-of-line
13066 @vindex nntp-end-of-line
13067 String to use as end-of-line marker when talking to the @acronym{NNTP}
13068 server. This is @samp{\r\n} by default, but should be @samp{\n} when
13069 using a non native telnet connection function.
13071 @item nntp-telnet-command
13072 @vindex nntp-telnet-command
13073 Command to use when connecting to the @acronym{NNTP} server through
13074 @samp{telnet}. This is @emph{not} for an intermediate host. This is
13075 just for the real @acronym{NNTP} server. The default is
13078 @item nntp-telnet-switches
13079 @vindex nntp-telnet-switches
13080 A list of switches to pass to @code{nntp-telnet-command}. The default
13086 @subsubsection NNTP marks
13087 @cindex storing NNTP marks
13089 Gnus stores marks (@pxref{Marking Articles}) for @acronym{NNTP}
13090 servers in marks files. A marks file records what marks you have set
13091 in a group and each file is specific to the corresponding server.
13092 Marks files are stored in @file{~/News/marks}
13093 (@code{nntp-marks-directory}) under a classic hierarchy resembling
13094 that of a news server, for example marks for the group
13095 @samp{gmane.discuss} on the news.gmane.org server will be stored in
13096 the file @file{~/News/marks/news.gmane.org/gmane/discuss/.marks}.
13098 Marks files are useful because you can copy the @file{~/News/marks}
13099 directory (using rsync, scp or whatever) to another Gnus installation,
13100 and it will realize what articles you have read and marked. The data
13101 in @file{~/News/marks} has priority over the same data in
13102 @file{~/.newsrc.eld}.
13104 Note that marks files are very much server-specific: Gnus remembers
13105 the article numbers so if you don't use the same servers on both
13106 installations things are most likely to break (most @acronym{NNTP}
13107 servers do not use the same article numbers as any other server).
13108 However, if you use servers A, B, C on one installation and servers A,
13109 D, E on the other, you can sync the marks files for A and then you'll
13110 get synchronization for that server between the two installations.
13112 Using @acronym{NNTP} marks can possibly incur a performance penalty so
13113 if Gnus feels sluggish, try setting the @code{nntp-marks-is-evil}
13114 variable to @code{t}. Marks will then be stored in @file{~/.newsrc.eld}.
13120 @item nntp-marks-is-evil
13121 @vindex nntp-marks-is-evil
13122 If non-@code{nil}, this back end will ignore any marks files. The
13123 default is @code{nil}.
13125 @item nntp-marks-directory
13126 @vindex nntp-marks-directory
13127 The directory where marks for nntp groups will be stored.
13133 @subsection News Spool
13137 Subscribing to a foreign group from the local spool is extremely easy,
13138 and might be useful, for instance, to speed up reading groups that
13139 contain very big articles---@samp{alt.binaries.pictures.furniture}, for
13142 Anyway, you just specify @code{nnspool} as the method and @code{""} (or
13143 anything else) as the address.
13145 If you have access to a local spool, you should probably use that as the
13146 native select method (@pxref{Finding the News}). It is normally faster
13147 than using an @code{nntp} select method, but might not be. It depends.
13148 You just have to try to find out what's best at your site.
13152 @item nnspool-inews-program
13153 @vindex nnspool-inews-program
13154 Program used to post an article.
13156 @item nnspool-inews-switches
13157 @vindex nnspool-inews-switches
13158 Parameters given to the inews program when posting an article.
13160 @item nnspool-spool-directory
13161 @vindex nnspool-spool-directory
13162 Where @code{nnspool} looks for the articles. This is normally
13163 @file{/usr/spool/news/}.
13165 @item nnspool-nov-directory
13166 @vindex nnspool-nov-directory
13167 Where @code{nnspool} will look for @acronym{NOV} files. This is normally@*
13168 @file{/usr/spool/news/over.view/}.
13170 @item nnspool-lib-dir
13171 @vindex nnspool-lib-dir
13172 Where the news lib dir is (@file{/usr/lib/news/} by default).
13174 @item nnspool-active-file
13175 @vindex nnspool-active-file
13176 The name of the active file.
13178 @item nnspool-newsgroups-file
13179 @vindex nnspool-newsgroups-file
13180 The name of the group descriptions file.
13182 @item nnspool-history-file
13183 @vindex nnspool-history-file
13184 The name of the news history file.
13186 @item nnspool-active-times-file
13187 @vindex nnspool-active-times-file
13188 The name of the active date file.
13190 @item nnspool-nov-is-evil
13191 @vindex nnspool-nov-is-evil
13192 If non-@code{nil}, @code{nnspool} won't try to use any @acronym{NOV} files
13195 @item nnspool-sift-nov-with-sed
13196 @vindex nnspool-sift-nov-with-sed
13198 If non-@code{nil}, which is the default, use @code{sed} to get the
13199 relevant portion from the overview file. If @code{nil},
13200 @code{nnspool} will load the entire file into a buffer and process it
13207 @section Getting Mail
13208 @cindex reading mail
13211 Reading mail with a newsreader---isn't that just plain WeIrD? But of
13215 * Mail in a Newsreader:: Important introductory notes.
13216 * Getting Started Reading Mail:: A simple cookbook example.
13217 * Splitting Mail:: How to create mail groups.
13218 * Mail Sources:: How to tell Gnus where to get mail from.
13219 * Mail Back End Variables:: Variables for customizing mail handling.
13220 * Fancy Mail Splitting:: Gnus can do hairy splitting of incoming mail.
13221 * Group Mail Splitting:: Use group customize to drive mail splitting.
13222 * Incorporating Old Mail:: What about the old mail you have?
13223 * Expiring Mail:: Getting rid of unwanted mail.
13224 * Washing Mail:: Removing cruft from the mail you get.
13225 * Duplicates:: Dealing with duplicated mail.
13226 * Not Reading Mail:: Using mail back ends for reading other files.
13227 * Choosing a Mail Back End:: Gnus can read a variety of mail formats.
13231 @node Mail in a Newsreader
13232 @subsection Mail in a Newsreader
13234 If you are used to traditional mail readers, but have decided to switch
13235 to reading mail with Gnus, you may find yourself experiencing something
13236 of a culture shock.
13238 Gnus does not behave like traditional mail readers. If you want to make
13239 it behave that way, you can, but it's an uphill battle.
13241 Gnus, by default, handles all its groups using the same approach. This
13242 approach is very newsreaderly---you enter a group, see the new/unread
13243 messages, and when you read the messages, they get marked as read, and
13244 you don't see them any more. (Unless you explicitly ask for them.)
13246 In particular, you do not do anything explicitly to delete messages.
13248 Does this mean that all the messages that have been marked as read are
13249 deleted? How awful!
13251 But, no, it means that old messages are @dfn{expired} according to some
13252 scheme or other. For news messages, the expire process is controlled by
13253 the news administrator; for mail, the expire process is controlled by
13254 you. The expire process for mail is covered in depth in @ref{Expiring
13257 What many Gnus users find, after using it a while for both news and
13258 mail, is that the transport mechanism has very little to do with how
13259 they want to treat a message.
13261 Many people subscribe to several mailing lists. These are transported
13262 via @acronym{SMTP}, and are therefore mail. But we might go for weeks without
13263 answering, or even reading these messages very carefully. We may not
13264 need to save them because if we should need to read one again, they are
13265 archived somewhere else.
13267 Some people have local news groups which have only a handful of readers.
13268 These are transported via @acronym{NNTP}, and are therefore news. But we may need
13269 to read and answer a large fraction of the messages very carefully in
13270 order to do our work. And there may not be an archive, so we may need
13271 to save the interesting messages the same way we would personal mail.
13273 The important distinction turns out to be not the transport mechanism,
13274 but other factors such as how interested we are in the subject matter,
13275 or how easy it is to retrieve the message if we need to read it again.
13277 Gnus provides many options for sorting mail into ``groups'' which behave
13278 like newsgroups, and for treating each group (whether mail or news)
13281 Some users never get comfortable using the Gnus (ahem) paradigm and wish
13282 that Gnus should grow up and be a male, er, mail reader. It is possible
13283 to whip Gnus into a more mailreaderly being, but, as said before, it's
13284 not easy. People who prefer proper mail readers should try @sc{vm}
13285 instead, which is an excellent, and proper, mail reader.
13287 I don't mean to scare anybody off, but I want to make it clear that you
13288 may be required to learn a new way of thinking about messages. After
13289 you've been subjected to The Gnus Way, you will come to love it. I can
13290 guarantee it. (At least the guy who sold me the Emacs Subliminal
13291 Brain-Washing Functions that I've put into Gnus did guarantee it. You
13292 Will Be Assimilated. You Love Gnus. You Love The Gnus Mail Way.
13296 @node Getting Started Reading Mail
13297 @subsection Getting Started Reading Mail
13299 It's quite easy to use Gnus to read your new mail. You just plonk the
13300 mail back end of your choice into @code{gnus-secondary-select-methods},
13301 and things will happen automatically.
13303 For instance, if you want to use @code{nnml} (which is a ``one file per
13304 mail'' back end), you could put the following in your @file{~/.gnus.el} file:
13307 (setq gnus-secondary-select-methods '((nnml "")))
13310 Now, the next time you start Gnus, this back end will be queried for new
13311 articles, and it will move all the messages in your spool file to its
13312 directory, which is @file{~/Mail/} by default. The new group that will
13313 be created (@samp{mail.misc}) will be subscribed, and you can read it
13314 like any other group.
13316 You will probably want to split the mail into several groups, though:
13319 (setq nnmail-split-methods
13320 '(("junk" "^From:.*Lars Ingebrigtsen")
13321 ("crazy" "^Subject:.*die\\|^Organization:.*flabby")
13325 This will result in three new @code{nnml} mail groups being created:
13326 @samp{nnml:junk}, @samp{nnml:crazy}, and @samp{nnml:other}. All the
13327 mail that doesn't fit into the first two groups will be placed in the
13330 This should be sufficient for reading mail with Gnus. You might want to
13331 give the other sections in this part of the manual a perusal, though.
13332 Especially @pxref{Choosing a Mail Back End} and @pxref{Expiring Mail}.
13335 @node Splitting Mail
13336 @subsection Splitting Mail
13337 @cindex splitting mail
13338 @cindex mail splitting
13339 @cindex mail filtering (splitting)
13341 @vindex nnmail-split-methods
13342 The @code{nnmail-split-methods} variable says how the incoming mail is
13343 to be split into groups.
13346 (setq nnmail-split-methods
13347 '(("mail.junk" "^From:.*Lars Ingebrigtsen")
13348 ("mail.crazy" "^Subject:.*die\\|^Organization:.*flabby")
13349 ("mail.other" "")))
13352 This variable is a list of lists, where the first element of each of
13353 these lists is the name of the mail group (they do not have to be called
13354 something beginning with @samp{mail}, by the way), and the second
13355 element is a regular expression used on the header of each mail to
13356 determine if it belongs in this mail group. The first string may
13357 contain @samp{\\1} forms, like the ones used by @code{replace-match} to
13358 insert sub-expressions from the matched text. For instance:
13361 ("list.\\1" "From:.* \\(.*\\)-list@@majordomo.com")
13365 In that case, @code{nnmail-split-lowercase-expanded} controls whether
13366 the inserted text should be made lowercase. @xref{Fancy Mail Splitting}.
13368 The second element can also be a function. In that case, it will be
13369 called narrowed to the headers with the first element of the rule as the
13370 argument. It should return a non-@code{nil} value if it thinks that the
13371 mail belongs in that group.
13373 @cindex @samp{bogus} group
13374 The last of these groups should always be a general one, and the regular
13375 expression should @emph{always} be @samp{""} so that it matches any mails
13376 that haven't been matched by any of the other regexps. (These rules are
13377 processed from the beginning of the alist toward the end. The first rule
13378 to make a match will ``win'', unless you have crossposting enabled. In
13379 that case, all matching rules will ``win''.) If no rule matched, the mail
13380 will end up in the @samp{bogus} group. When new groups are created by
13381 splitting mail, you may want to run @code{gnus-group-find-new-groups} to
13382 see the new groups. This also applies to the @samp{bogus} group.
13384 If you like to tinker with this yourself, you can set this variable to a
13385 function of your choice. This function will be called without any
13386 arguments in a buffer narrowed to the headers of an incoming mail
13387 message. The function should return a list of group names that it
13388 thinks should carry this mail message.
13390 Note that the mail back ends are free to maul the poor, innocent,
13391 incoming headers all they want to. They all add @code{Lines} headers;
13392 some add @code{X-Gnus-Group} headers; most rename the Unix mbox
13393 @code{From<SPACE>} line to something else.
13395 @vindex nnmail-crosspost
13396 The mail back ends all support cross-posting. If several regexps match,
13397 the mail will be ``cross-posted'' to all those groups.
13398 @code{nnmail-crosspost} says whether to use this mechanism or not. Note
13399 that no articles are crossposted to the general (@samp{""}) group.
13401 @vindex nnmail-crosspost-link-function
13404 @code{nnmh} and @code{nnml} makes crossposts by creating hard links to
13405 the crossposted articles. However, not all file systems support hard
13406 links. If that's the case for you, set
13407 @code{nnmail-crosspost-link-function} to @code{copy-file}. (This
13408 variable is @code{add-name-to-file} by default.)
13410 @kindex M-x nnmail-split-history
13411 @findex nnmail-split-history
13412 If you wish to see where the previous mail split put the messages, you
13413 can use the @kbd{M-x nnmail-split-history} command. If you wish to see
13414 where re-spooling messages would put the messages, you can use
13415 @code{gnus-summary-respool-trace} and related commands (@pxref{Mail
13418 @vindex nnmail-split-header-length-limit
13419 Header lines longer than the value of
13420 @code{nnmail-split-header-length-limit} are excluded from the split
13423 @vindex nnmail-mail-splitting-charset
13424 @vindex nnmail-mail-splitting-decodes
13425 By default the splitting codes @acronym{MIME} decodes headers so you
13426 can match on non-@acronym{ASCII} strings. The
13427 @code{nnmail-mail-splitting-charset} variable specifies the default
13428 charset for decoding. The behaviour can be turned off completely by
13429 binding @code{nnmail-mail-splitting-decodes} to @code{nil}, which is
13430 useful if you want to match articles based on the raw header data.
13432 @vindex nnmail-resplit-incoming
13433 By default, splitting is performed on all incoming messages. If you
13434 specify a @code{directory} entry for the variable @code{mail-sources}
13435 (@pxref{Mail Source Specifiers}), however, then splitting does
13436 @emph{not} happen by default. You can set the variable
13437 @code{nnmail-resplit-incoming} to a non-@code{nil} value to make
13438 splitting happen even in this case. (This variable has no effect on
13439 other kinds of entries.)
13441 Gnus gives you all the opportunity you could possibly want for shooting
13442 yourself in the foot. Let's say you create a group that will contain
13443 all the mail you get from your boss. And then you accidentally
13444 unsubscribe from the group. Gnus will still put all the mail from your
13445 boss in the unsubscribed group, and so, when your boss mails you ``Have
13446 that report ready by Monday or you're fired!'', you'll never see it and,
13447 come Tuesday, you'll still believe that you're gainfully employed while
13448 you really should be out collecting empty bottles to save up for next
13449 month's rent money.
13453 @subsection Mail Sources
13455 Mail can be gotten from many different sources---the mail spool, from
13456 a @acronym{POP} mail server, from a procmail directory, or from a
13457 maildir, for instance.
13460 * Mail Source Specifiers:: How to specify what a mail source is.
13461 * Mail Source Customization:: Some variables that influence things.
13462 * Fetching Mail:: Using the mail source specifiers.
13466 @node Mail Source Specifiers
13467 @subsubsection Mail Source Specifiers
13469 @cindex mail server
13472 @cindex mail source
13474 You tell Gnus how to fetch mail by setting @code{mail-sources}
13475 (@pxref{Fetching Mail}) to a @dfn{mail source specifier}.
13480 (pop :server "pop3.mailserver.com" :user "myname")
13483 As can be observed, a mail source specifier is a list where the first
13484 element is a @dfn{mail source type}, followed by an arbitrary number of
13485 @dfn{keywords}. Keywords that are not explicitly specified are given
13488 The following mail source types are available:
13492 Get mail from a single file; typically from the mail spool.
13498 The file name. Defaults to the value of the @env{MAIL}
13499 environment variable or the value of @code{rmail-spool-directory}
13500 (usually something like @file{/usr/mail/spool/user-name}).
13504 Script run before/after fetching mail.
13507 An example file mail source:
13510 (file :path "/usr/spool/mail/user-name")
13513 Or using the default file name:
13519 If the mail spool file is not located on the local machine, it's best
13520 to use @acronym{POP} or @acronym{IMAP} or the like to fetch the mail.
13521 You can not use ange-ftp file names here---it has no way to lock the
13522 mail spool while moving the mail.
13524 If it's impossible to set up a proper server, you can use ssh instead.
13528 '((file :prescript "ssh host bin/getmail >%t")))
13531 The @samp{getmail} script would look something like the following:
13535 # getmail - move mail from spool to stdout
13538 MOVEMAIL=/usr/lib/emacs/20.3/i386-redhat-linux/movemail
13540 rm -f $TMP; $MOVEMAIL $MAIL $TMP >/dev/null && cat $TMP
13543 Alter this script to fit find the @samp{movemail} you want to use.
13547 @vindex nnmail-scan-directory-mail-source-once
13548 Get mail from several files in a directory. This is typically used
13549 when you have procmail split the incoming mail into several files.
13550 That is, there is a one-to-one correspondence between files in that
13551 directory and groups, so that mail from the file @file{foo.bar.spool}
13552 will be put in the group @code{foo.bar}. (You can change the suffix
13553 to be used instead of @code{.spool}.) Setting
13554 @code{nnmail-scan-directory-mail-source-once} to non-@code{nil} forces
13555 Gnus to scan the mail source only once. This is particularly useful
13556 if you want to scan mail groups at a specified level.
13558 @vindex nnmail-resplit-incoming
13559 There is also the variable @code{nnmail-resplit-incoming}, if you set
13560 that to a non-@code{nil} value, then the normal splitting process is
13561 applied to all the files from the directory, @ref{Splitting Mail}.
13567 The name of the directory where the files are. There is no default
13571 Only files ending with this suffix are used. The default is
13575 Only files that have this predicate return non-@code{nil} are returned.
13576 The default is @code{identity}. This is used as an additional
13577 filter---only files that have the right suffix @emph{and} satisfy this
13578 predicate are considered.
13582 Script run before/after fetching mail.
13586 An example directory mail source:
13589 (directory :path "/home/user-name/procmail-dir/"
13594 Get mail from a @acronym{POP} server.
13600 The name of the @acronym{POP} server. The default is taken from the
13601 @env{MAILHOST} environment variable.
13604 The port number of the @acronym{POP} server. This can be a number (eg,
13605 @samp{:port 1234}) or a string (eg, @samp{:port "pop3"}). If it is a
13606 string, it should be a service name as listed in @file{/etc/services} on
13607 Unix systems. The default is @samp{"pop3"}. On some systems you might
13608 need to specify it as @samp{"pop-3"} instead.
13611 The user name to give to the @acronym{POP} server. The default is the login
13615 The password to give to the @acronym{POP} server. If not specified,
13616 the user is prompted.
13619 The program to use to fetch mail from the @acronym{POP} server. This
13620 should be a @code{format}-like string. Here's an example:
13623 fetchmail %u@@%s -P %p %t
13626 The valid format specifier characters are:
13630 The name of the file the mail is to be moved to. This must always be
13631 included in this string.
13634 The name of the server.
13637 The port number of the server.
13640 The user name to use.
13643 The password to use.
13646 The values used for these specs are taken from the values you give the
13647 corresponding keywords.
13650 A script to be run before fetching the mail. The syntax is the same as
13651 the @code{:program} keyword. This can also be a function to be run.
13654 A script to be run after fetching the mail. The syntax is the same as
13655 the @code{:program} keyword. This can also be a function to be run.
13658 The function to use to fetch mail from the @acronym{POP} server. The
13659 function is called with one parameter---the name of the file where the
13660 mail should be moved to.
13662 @item :authentication
13663 This can be either the symbol @code{password} or the symbol @code{apop}
13664 and says what authentication scheme to use. The default is
13668 What stream to use for connecting to the server, this can be the symbol
13669 @code{ssl}, the symbol @code{tls} or others. The default is @code{nil}
13670 and use insecure connections. Note that for SSL/TLS, you need external
13671 programs and libraries:
13675 @dfn{ssl:} Connect through SSL@. Requires OpenSSL (the program
13676 @samp{openssl}) or SSLeay (@samp{s_client}) as well as the external
13677 library @samp{ssl.el}.
13679 @dfn{starttls:} Connect via the STARTTLS extension (similar to SSL)@.
13680 Requires the external library @samp{starttls.el} and program
13685 Non-@code{nil} if mail is to be left on the server and UIDL used for
13686 message retrieval. The default is @code{nil}.
13690 @vindex pop3-movemail
13691 @vindex pop3-leave-mail-on-server
13692 If the @code{:program} and @code{:function} keywords aren't specified,
13693 @code{pop3-movemail} will be used. If the
13694 @code{pop3-leave-mail-on-server} is non-@code{nil} the mail is to be
13695 left on the @acronym{POP} server after fetching when using
13696 @code{pop3-movemail}. Note that POP servers maintain no state
13697 information between sessions, so what the client believes is there and
13698 what is actually there may not match up. If they do not, then the whole
13699 thing can fall apart and leave you with a corrupt mailbox.
13701 Here are some examples. Fetch from the default @acronym{POP} server,
13702 using the default user name, and default fetcher:
13708 Fetch from a named server with a named user and password:
13711 (pop :server "my.pop.server"
13712 :user "user-name" :password "secret")
13715 Use @samp{movemail} to move the mail:
13718 (pop :program "movemail po:%u %t %p")
13722 Get mail from a maildir. This is a type of mailbox that is supported by
13723 at least qmail and postfix, where each file in a special directory
13724 contains exactly one mail.
13730 The name of the directory where the mails are stored. The default is
13731 taken from the @env{MAILDIR} environment variable or
13734 The subdirectories of the Maildir. The default is
13735 @samp{("new" "cur")}.
13737 @c If you sometimes look at your mail through a pop3 daemon before fetching
13738 @c them with Gnus, you may also have to fetch your mails from the
13739 @c @code{cur} directory inside the maildir, like in the first example
13742 You can also get mails from remote hosts (because maildirs don't suffer
13743 from locking problems).
13747 Two example maildir mail sources:
13750 (maildir :path "/home/user-name/Maildir/"
13751 :subdirs ("cur" "new"))
13755 (maildir :path "/user@@remotehost.org:~/Maildir/"
13760 Get mail from a @acronym{IMAP} server. If you don't want to use
13761 @acronym{IMAP} as intended, as a network mail reading protocol (ie
13762 with nnimap), for some reason or other, Gnus let you treat it similar
13763 to a @acronym{POP} server and fetches articles from a given
13764 @acronym{IMAP} mailbox. @xref{IMAP}, for more information.
13766 Note that for the Kerberos, GSSAPI, @acronym{TLS}/@acronym{SSL} and STARTTLS support you
13767 may need external programs and libraries, @xref{IMAP}.
13773 The name of the @acronym{IMAP} server. The default is taken from the
13774 @env{MAILHOST} environment variable.
13777 The port number of the @acronym{IMAP} server. The default is @samp{143}, or
13778 @samp{993} for @acronym{TLS}/@acronym{SSL} connections.
13781 The user name to give to the @acronym{IMAP} server. The default is the login
13785 The password to give to the @acronym{IMAP} server. If not specified, the user is
13789 What stream to use for connecting to the server, this is one of the
13790 symbols in @code{imap-stream-alist}. Right now, this means
13791 @samp{gssapi}, @samp{kerberos4}, @samp{starttls}, @samp{tls},
13792 @samp{ssl}, @samp{shell} or the default @samp{network}.
13794 @item :authentication
13795 Which authenticator to use for authenticating to the server, this is
13796 one of the symbols in @code{imap-authenticator-alist}. Right now,
13797 this means @samp{gssapi}, @samp{kerberos4}, @samp{digest-md5},
13798 @samp{cram-md5}, @samp{anonymous} or the default @samp{login}.
13801 When using the `shell' :stream, the contents of this variable is
13802 mapped into the @code{imap-shell-program} variable. This should be a
13803 @code{format}-like string (or list of strings). Here's an example:
13809 The valid format specifier characters are:
13813 The name of the server.
13816 User name from @code{imap-default-user}.
13819 The port number of the server.
13822 The values used for these specs are taken from the values you give the
13823 corresponding keywords.
13826 The name of the mailbox to get mail from. The default is @samp{INBOX}
13827 which normally is the mailbox which receive incoming mail.
13830 The predicate used to find articles to fetch. The default, @samp{UNSEEN
13831 UNDELETED}, is probably the best choice for most people, but if you
13832 sometimes peek in your mailbox with a @acronym{IMAP} client and mark some
13833 articles as read (or; SEEN) you might want to set this to @samp{1:*}.
13834 Then all articles in the mailbox is fetched, no matter what. For a
13835 complete list of predicates, see RFC 2060 section 6.4.4.
13838 How to flag fetched articles on the server, the default @samp{\Deleted}
13839 will mark them as deleted, an alternative would be @samp{\Seen} which
13840 would simply mark them as read. These are the two most likely choices,
13841 but more flags are defined in RFC 2060 section 2.3.2.
13844 If non-@code{nil}, don't remove all articles marked as deleted in the
13845 mailbox after finishing the fetch.
13849 An example @acronym{IMAP} mail source:
13852 (imap :server "mail.mycorp.com"
13854 :fetchflag "\\Seen")
13858 Get mail from a webmail server, such as @uref{http://www.hotmail.com/},
13859 @uref{http://webmail.netscape.com/}, @uref{http://www.netaddress.com/},
13860 @uref{http://mail.yahoo.com/}.
13862 NOTE: Webmail largely depends on cookies. A "one-line-cookie" patch is
13863 required for url "4.0pre.46".
13865 WARNING: Mails may be lost. NO WARRANTY.
13871 The type of the webmail server. The default is @code{hotmail}. The
13872 alternatives are @code{netscape}, @code{netaddress}, @code{my-deja}.
13875 The user name to give to the webmail server. The default is the login
13879 The password to give to the webmail server. If not specified, the user is
13883 If non-@code{nil}, only fetch unread articles and don't move them to
13884 trash folder after finishing the fetch.
13888 An example webmail source:
13891 (webmail :subtype 'hotmail
13893 :password "secret")
13898 @item Common Keywords
13899 Common keywords can be used in any type of mail source.
13905 If non-@code{nil}, fetch the mail even when Gnus is unplugged. If you
13906 use directory source to get mail, you can specify it as in this
13911 '((directory :path "/home/pavel/.Spool/"
13916 Gnus will then fetch your mail even when you are unplugged. This is
13917 useful when you use local mail and news.
13922 @subsubsection Function Interface
13924 Some of the above keywords specify a Lisp function to be executed.
13925 For each keyword @code{:foo}, the Lisp variable @code{foo} is bound to
13926 the value of the keyword while the function is executing. For example,
13927 consider the following mail-source setting:
13930 (setq mail-sources '((pop :user "jrl"
13931 :server "pophost" :function fetchfunc)))
13934 While the function @code{fetchfunc} is executing, the symbol @code{user}
13935 is bound to @code{"jrl"}, and the symbol @code{server} is bound to
13936 @code{"pophost"}. The symbols @code{port}, @code{password},
13937 @code{program}, @code{prescript}, @code{postscript}, @code{function},
13938 and @code{authentication} are also bound (to their default values).
13940 See above for a list of keywords for each type of mail source.
13943 @node Mail Source Customization
13944 @subsubsection Mail Source Customization
13946 The following is a list of variables that influence how the mail is
13947 fetched. You would normally not need to set or change any of these
13951 @item mail-source-crash-box
13952 @vindex mail-source-crash-box
13953 File where mail will be stored while processing it. The default is@*
13954 @file{~/.emacs-mail-crash-box}.
13956 @item mail-source-delete-incoming
13957 @vindex mail-source-delete-incoming
13958 If non-@code{nil}, delete incoming files after handling them. If
13959 @code{t}, delete the files immediately, if @code{nil}, never delete any
13960 files. If a positive number, delete files older than number of days
13961 (This will only happen, when receiving new mail). You may also set
13962 @code{mail-source-delete-incoming} to @code{nil} and call
13963 @code{mail-source-delete-old-incoming} from a hook or interactively.
13965 @item mail-source-delete-old-incoming-confirm
13966 @vindex mail-source-delete-old-incoming-confirm
13967 If non-@code{nil}, ask for for confirmation before deleting old incoming
13968 files. This variable only applies when
13969 @code{mail-source-delete-incoming} is a positive number.
13971 @item mail-source-ignore-errors
13972 @vindex mail-source-ignore-errors
13973 If non-@code{nil}, ignore errors when reading mail from a mail source.
13975 @item mail-source-directory
13976 @vindex mail-source-directory
13977 Directory where incoming mail source files (if any) will be stored. The
13978 default is @file{~/Mail/}. At present, the only thing this is used for
13979 is to say where the incoming files will be stored if the variable
13980 @code{mail-source-delete-incoming} is @code{nil} or a number.
13982 @item mail-source-incoming-file-prefix
13983 @vindex mail-source-incoming-file-prefix
13984 Prefix for file name for storing incoming mail. The default is
13985 @file{Incoming}, in which case files will end up with names like
13986 @file{Incoming30630D_} or @file{Incoming298602ZD}. This is really only
13987 relevant if @code{mail-source-delete-incoming} is @code{nil}.
13989 @item mail-source-default-file-modes
13990 @vindex mail-source-default-file-modes
13991 All new mail files will get this file mode. The default is 384.
13993 @item mail-source-movemail-program
13994 @vindex mail-source-movemail-program
13995 If non-@code{nil}, name of program for fetching new mail. If
13996 @code{nil}, @code{movemail} in @var{exec-directory}.
14001 @node Fetching Mail
14002 @subsubsection Fetching Mail
14004 @vindex mail-sources
14005 @vindex nnmail-spool-file
14006 The way to actually tell Gnus where to get new mail from is to set
14007 @code{mail-sources} to a list of mail source specifiers
14008 (@pxref{Mail Source Specifiers}).
14010 If this variable (and the obsolescent @code{nnmail-spool-file}) is
14011 @code{nil}, the mail back ends will never attempt to fetch mail by
14014 If you want to fetch mail both from your local spool as well as a
14015 @acronym{POP} mail server, you'd say something like:
14020 (pop :server "pop3.mail.server"
14021 :password "secret")))
14024 Or, if you don't want to use any of the keyword defaults:
14028 '((file :path "/var/spool/mail/user-name")
14029 (pop :server "pop3.mail.server"
14032 :password "secret")))
14036 When you use a mail back end, Gnus will slurp all your mail from your
14037 inbox and plonk it down in your home directory. Gnus doesn't move any
14038 mail if you're not using a mail back end---you have to do a lot of magic
14039 invocations first. At the time when you have finished drawing the
14040 pentagram, lightened the candles, and sacrificed the goat, you really
14041 shouldn't be too surprised when Gnus moves your mail.
14045 @node Mail Back End Variables
14046 @subsection Mail Back End Variables
14048 These variables are (for the most part) pertinent to all the various
14052 @vindex nnmail-read-incoming-hook
14053 @item nnmail-read-incoming-hook
14054 The mail back ends all call this hook after reading new mail. You can
14055 use this hook to notify any mail watch programs, if you want to.
14057 @vindex nnmail-split-hook
14058 @item nnmail-split-hook
14059 @findex gnus-article-decode-encoded-words
14060 @cindex RFC 1522 decoding
14061 @cindex RFC 2047 decoding
14062 Hook run in the buffer where the mail headers of each message is kept
14063 just before the splitting based on these headers is done. The hook is
14064 free to modify the buffer contents in any way it sees fit---the buffer
14065 is discarded after the splitting has been done, and no changes performed
14066 in the buffer will show up in any files.
14067 @code{gnus-article-decode-encoded-words} is one likely function to add
14070 @vindex nnmail-pre-get-new-mail-hook
14071 @vindex nnmail-post-get-new-mail-hook
14072 @item nnmail-pre-get-new-mail-hook
14073 @itemx nnmail-post-get-new-mail-hook
14074 These are two useful hooks executed when treating new incoming
14075 mail---@code{nnmail-pre-get-new-mail-hook} (is called just before
14076 starting to handle the new mail) and
14077 @code{nnmail-post-get-new-mail-hook} (is called when the mail handling
14078 is done). Here's and example of using these two hooks to change the
14079 default file modes the new mail files get:
14082 (add-hook 'nnmail-pre-get-new-mail-hook
14083 (lambda () (set-default-file-modes 511)))
14085 (add-hook 'nnmail-post-get-new-mail-hook
14086 (lambda () (set-default-file-modes 551)))
14089 @item nnmail-use-long-file-names
14090 @vindex nnmail-use-long-file-names
14091 If non-@code{nil}, the mail back ends will use long file and directory
14092 names. Groups like @samp{mail.misc} will end up in directories
14093 (assuming use of @code{nnml} back end) or files (assuming use of
14094 @code{nnfolder} back end) like @file{mail.misc}. If it is @code{nil},
14095 the same group will end up in @file{mail/misc}.
14097 @item nnmail-delete-file-function
14098 @vindex nnmail-delete-file-function
14099 @findex delete-file
14100 Function called to delete files. It is @code{delete-file} by default.
14102 @item nnmail-cache-accepted-message-ids
14103 @vindex nnmail-cache-accepted-message-ids
14104 If non-@code{nil}, put the @code{Message-ID}s of articles imported into
14105 the back end (via @code{Gcc}, for instance) into the mail duplication
14106 discovery cache. The default is @code{nil}.
14108 @item nnmail-cache-ignore-groups
14109 @vindex nnmail-cache-ignore-groups
14110 This can be a regular expression or a list of regular expressions.
14111 Group names that match any of the regular expressions will never be
14112 recorded in the @code{Message-ID} cache.
14114 This can be useful, for example, when using Fancy Splitting
14115 (@pxref{Fancy Mail Splitting}) together with the function
14116 @code{nnmail-split-fancy-with-parent}.
14121 @node Fancy Mail Splitting
14122 @subsection Fancy Mail Splitting
14123 @cindex mail splitting
14124 @cindex fancy mail splitting
14126 @vindex nnmail-split-fancy
14127 @findex nnmail-split-fancy
14128 If the rather simple, standard method for specifying how to split mail
14129 doesn't allow you to do what you want, you can set
14130 @code{nnmail-split-methods} to @code{nnmail-split-fancy}. Then you can
14131 play with the @code{nnmail-split-fancy} variable.
14133 Let's look at an example value of this variable first:
14136 ;; @r{Messages from the mailer daemon are not crossposted to any of}
14137 ;; @r{the ordinary groups. Warnings are put in a separate group}
14138 ;; @r{from real errors.}
14139 (| ("from" mail (| ("subject" "warn.*" "mail.warning")
14141 ;; @r{Non-error messages are crossposted to all relevant}
14142 ;; @r{groups, but we don't crosspost between the group for the}
14143 ;; @r{(ding) list and the group for other (ding) related mail.}
14144 (& (| (any "ding@@ifi\\.uio\\.no" "ding.list")
14145 ("subject" "ding" "ding.misc"))
14146 ;; @r{Other mailing lists@dots{}}
14147 (any "procmail@@informatik\\.rwth-aachen\\.de" "procmail.list")
14148 (any "SmartList@@informatik\\.rwth-aachen\\.de" "SmartList.list")
14149 ;; @r{Both lists below have the same suffix, so prevent}
14150 ;; @r{cross-posting to mkpkg.list of messages posted only to}
14151 ;; @r{the bugs- list, but allow cross-posting when the}
14152 ;; @r{message was really cross-posted.}
14153 (any "bugs-mypackage@@somewhere" "mypkg.bugs")
14154 (any "mypackage@@somewhere" - "bugs-mypackage" "mypkg.list")
14155 ;; @r{People@dots{}}
14156 (any "larsi@@ifi\\.uio\\.no" "people.Lars_Magne_Ingebrigtsen"))
14157 ;; @r{Unmatched mail goes to the catch all group.}
14161 This variable has the format of a @dfn{split}. A split is a
14162 (possibly) recursive structure where each split may contain other
14163 splits. Here are the possible split syntaxes:
14168 If the split is a string, that will be taken as a group name. Normal
14169 regexp match expansion will be done. See below for examples.
14171 @item (@var{field} @var{value} [- @var{restrict} [@dots{}] ] @var{split})
14172 If the split is a list, the first element of which is a string, then
14173 store the message as specified by @var{split}, if header @var{field}
14174 (a regexp) contains @var{value} (also a regexp). If @var{restrict}
14175 (yet another regexp) matches some string after @var{field} and before
14176 the end of the matched @var{value}, the @var{split} is ignored. If
14177 none of the @var{restrict} clauses match, @var{split} is processed.
14179 @item (| @var{split} @dots{})
14180 If the split is a list, and the first element is @code{|} (vertical
14181 bar), then process each @var{split} until one of them matches. A
14182 @var{split} is said to match if it will cause the mail message to be
14183 stored in one or more groups.
14185 @item (& @var{split} @dots{})
14186 If the split is a list, and the first element is @code{&}, then
14187 process all @var{split}s in the list.
14190 If the split is the symbol @code{junk}, then don't save (i.e., delete)
14191 this message. Use with extreme caution.
14193 @item (: @var{function} @var{arg1} @var{arg2} @dots{})
14194 If the split is a list, and the first element is @samp{:}, then the
14195 second element will be called as a function with @var{args} given as
14196 arguments. The function should return a @var{split}.
14199 For instance, the following function could be used to split based on the
14200 body of the messages:
14203 (defun split-on-body ()
14207 (goto-char (point-min))
14208 (when (re-search-forward "Some.*string" nil t)
14212 The buffer is narrowed to the message in question when @var{function}
14213 is run. That's why @code{(widen)} needs to be called after
14214 @code{save-excursion} and @code{save-restriction} in the example
14215 above. Also note that with the nnimap back end, message bodies will
14216 not be downloaded by default. You need to set
14217 @code{nnimap-split-download-body} to @code{t} to do that
14218 (@pxref{Splitting in IMAP}).
14220 @item (! @var{func} @var{split})
14221 If the split is a list, and the first element is @code{!}, then
14222 @var{split} will be processed, and @var{func} will be called as a
14223 function with the result of @var{split} as argument. @var{func}
14224 should return a split.
14227 If the split is @code{nil}, it is ignored.
14231 In these splits, @var{field} must match a complete field name.
14232 @var{value} must match a complete word according to the fundamental mode
14233 syntax table. You can use @code{.*} in the regexps to match partial
14234 field names or words. In other words, all @var{value}'s are wrapped in
14235 @samp{\<} and @samp{\>} pairs.
14237 @vindex nnmail-split-abbrev-alist
14238 @var{field} and @var{value} can also be Lisp symbols, in that case
14239 they are expanded as specified by the variable
14240 @code{nnmail-split-abbrev-alist}. This is an alist of cons cells,
14241 where the @sc{car} of a cell contains the key, and the @sc{cdr}
14242 contains the associated value. Predefined entries in
14243 @code{nnmail-split-abbrev-alist} include:
14247 Matches the @samp{From}, @samp{Sender} and @samp{Resent-From} fields.
14249 Matches the @samp{To}, @samp{Cc}, @samp{Apparently-To},
14250 @samp{Resent-To} and @samp{Resent-Cc} fields.
14252 Is the union of the @code{from} and @code{to} entries.
14255 @vindex nnmail-split-fancy-syntax-table
14256 @code{nnmail-split-fancy-syntax-table} is the syntax table in effect
14257 when all this splitting is performed.
14259 If you want to have Gnus create groups dynamically based on some
14260 information in the headers (i.e., do @code{replace-match}-like
14261 substitutions in the group names), you can say things like:
14264 (any "debian-\\b\\(\\w+\\)@@lists.debian.org" "mail.debian.\\1")
14267 In this example, messages sent to @samp{debian-foo@@lists.debian.org}
14268 will be filed in @samp{mail.debian.foo}.
14270 If the string contains the element @samp{\&}, then the previously
14271 matched string will be substituted. Similarly, the elements @samp{\\1}
14272 up to @samp{\\9} will be substituted with the text matched by the
14273 groupings 1 through 9.
14275 @vindex nnmail-split-lowercase-expanded
14276 Where @code{nnmail-split-lowercase-expanded} controls whether the
14277 lowercase of the matched string should be used for the substitution.
14278 Setting it as non-@code{nil} is useful to avoid the creation of multiple
14279 groups when users send to an address using different case
14280 (i.e. mailing-list@@domain vs Mailing-List@@Domain). The default value
14283 @vindex nnmail-split-fancy-match-partial-words
14284 @code{nnmail-split-fancy-match-partial-words} controls whether partial
14285 words are matched during fancy splitting.
14287 Normally, regular expressions given in @code{nnmail-split-fancy} are
14288 implicitly surrounded by @code{\<...\>} markers, which are word
14289 delimiters. If this variable is true, they are not implicitly
14290 surrounded by anything.
14293 (any "joe" "joemail")
14296 In this example, messages sent from @samp{joedavis@@foo.org} will
14297 normally not be filed in @samp{joemail}. With
14298 @code{nnmail-split-fancy-match-partial-words} set to t, however, the
14299 match will happen. In effect, the requirement of a word boundary is
14300 removed and instead the match becomes more like a grep.
14302 @findex nnmail-split-fancy-with-parent
14303 @code{nnmail-split-fancy-with-parent} is a function which allows you to
14304 split followups into the same groups their parents are in. Sometimes
14305 you can't make splitting rules for all your mail. For example, your
14306 boss might send you personal mail regarding different projects you are
14307 working on, and as you can't tell your boss to put a distinguishing
14308 string into the subject line, you have to resort to manually moving the
14309 messages into the right group. With this function, you only have to do
14310 it once per thread.
14312 To use this feature, you have to set @code{nnmail-treat-duplicates}
14313 and @code{nnmail-cache-accepted-message-ids} to a non-@code{nil}
14314 value. And then you can include @code{nnmail-split-fancy-with-parent}
14315 using the colon feature, like so:
14317 (setq nnmail-treat-duplicates 'warn ; @r{or @code{delete}}
14318 nnmail-cache-accepted-message-ids t
14320 '(| (: nnmail-split-fancy-with-parent)
14321 ;; @r{other splits go here}
14325 This feature works as follows: when @code{nnmail-treat-duplicates} is
14326 non-@code{nil}, Gnus records the message id of every message it sees
14327 in the file specified by the variable
14328 @code{nnmail-message-id-cache-file}, together with the group it is in
14329 (the group is omitted for non-mail messages). When mail splitting is
14330 invoked, the function @code{nnmail-split-fancy-with-parent} then looks
14331 at the References (and In-Reply-To) header of each message to split
14332 and searches the file specified by @code{nnmail-message-id-cache-file}
14333 for the message ids. When it has found a parent, it returns the
14334 corresponding group name unless the group name matches the regexp
14335 @code{nnmail-split-fancy-with-parent-ignore-groups}. It is
14336 recommended that you set @code{nnmail-message-id-cache-length} to a
14337 somewhat higher number than the default so that the message ids are
14338 still in the cache. (A value of 5000 appears to create a file some
14339 300 kBytes in size.)
14340 @vindex nnmail-cache-accepted-message-ids
14341 When @code{nnmail-cache-accepted-message-ids} is non-@code{nil}, Gnus
14342 also records the message ids of moved articles, so that the followup
14343 messages goes into the new group.
14345 Also see the variable @code{nnmail-cache-ignore-groups} if you don't
14346 want certain groups to be recorded in the cache. For example, if all
14347 outgoing messages are written to an ``outgoing'' group, you could set
14348 @code{nnmail-cache-ignore-groups} to match that group name.
14349 Otherwise, answers to all your messages would end up in the
14350 ``outgoing'' group.
14353 @node Group Mail Splitting
14354 @subsection Group Mail Splitting
14355 @cindex mail splitting
14356 @cindex group mail splitting
14358 @findex gnus-group-split
14359 If you subscribe to dozens of mailing lists but you don't want to
14360 maintain mail splitting rules manually, group mail splitting is for you.
14361 You just have to set @code{to-list} and/or @code{to-address} in group
14362 parameters or group customization and set @code{nnmail-split-methods} to
14363 @code{gnus-group-split}. This splitting function will scan all groups
14364 for those parameters and split mail accordingly, i.e., messages posted
14365 from or to the addresses specified in the parameters @code{to-list} or
14366 @code{to-address} of a mail group will be stored in that group.
14368 Sometimes, mailing lists have multiple addresses, and you may want mail
14369 splitting to recognize them all: just set the @code{extra-aliases} group
14370 parameter to the list of additional addresses and it's done. If you'd
14371 rather use a regular expression, set @code{split-regexp}.
14373 All these parameters in a group will be used to create an
14374 @code{nnmail-split-fancy} split, in which the @var{field} is @samp{any},
14375 the @var{value} is a single regular expression that matches
14376 @code{to-list}, @code{to-address}, all of @code{extra-aliases} and all
14377 matches of @code{split-regexp}, and the @var{split} is the name of the
14378 group. @var{restrict}s are also supported: just set the
14379 @code{split-exclude} parameter to a list of regular expressions.
14381 If you can't get the right split to be generated using all these
14382 parameters, or you just need something fancier, you can set the
14383 parameter @code{split-spec} to an @code{nnmail-split-fancy} split. In
14384 this case, all other aforementioned parameters will be ignored by
14385 @code{gnus-group-split}. In particular, @code{split-spec} may be set to
14386 @code{nil}, in which case the group will be ignored by
14387 @code{gnus-group-split}.
14389 @vindex gnus-group-split-default-catch-all-group
14390 @code{gnus-group-split} will do cross-posting on all groups that match,
14391 by defining a single @code{&} fancy split containing one split for each
14392 group. If a message doesn't match any split, it will be stored in the
14393 group named in @code{gnus-group-split-default-catch-all-group}, unless
14394 some group has @code{split-spec} set to @code{catch-all}, in which case
14395 that group is used as the catch-all group. Even though this variable is
14396 often used just to name a group, it may also be set to an arbitrarily
14397 complex fancy split (after all, a group name is a fancy split), and this
14398 may be useful to split mail that doesn't go to any mailing list to
14399 personal mail folders. Note that this fancy split is added as the last
14400 element of a @code{|} split list that also contains a @code{&} split
14401 with the rules extracted from group parameters.
14403 It's time for an example. Assume the following group parameters have
14408 ((to-address . "bar@@femail.com")
14409 (split-regexp . ".*@@femail\\.com"))
14411 ((to-list . "foo@@nowhere.gov")
14412 (extra-aliases "foo@@localhost" "foo-redist@@home")
14413 (split-exclude "bugs-foo" "rambling-foo")
14414 (admin-address . "foo-request@@nowhere.gov"))
14416 ((split-spec . catch-all))
14419 Setting @code{nnmail-split-methods} to @code{gnus-group-split} will
14420 behave as if @code{nnmail-split-fancy} had been selected and variable
14421 @code{nnmail-split-fancy} had been set as follows:
14424 (| (& (any "\\(bar@@femail\\.com\\|.*@@femail\\.com\\)" "mail.bar")
14425 (any "\\(foo@@nowhere\\.gov\\|foo@@localhost\\|foo-redist@@home\\)"
14426 - "bugs-foo" - "rambling-foo" "mail.foo"))
14430 @findex gnus-group-split-fancy
14431 If you'd rather not use group splitting for all your mail groups, you
14432 may use it for only some of them, by using @code{nnmail-split-fancy}
14436 (: gnus-group-split-fancy @var{groups} @var{no-crosspost} @var{catch-all})
14439 @var{groups} may be a regular expression or a list of group names whose
14440 parameters will be scanned to generate the output split.
14441 @var{no-crosspost} can be used to disable cross-posting; in this case, a
14442 single @code{|} split will be output. @var{catch-all} is the fall back
14443 fancy split, used like @code{gnus-group-split-default-catch-all-group}.
14444 If @var{catch-all} is @code{nil}, or if @code{split-regexp} matches the
14445 empty string in any selected group, no catch-all split will be issued.
14446 Otherwise, if some group has @code{split-spec} set to @code{catch-all},
14447 this group will override the value of the @var{catch-all} argument.
14449 @findex gnus-group-split-setup
14450 Unfortunately, scanning all groups and their parameters can be quite
14451 slow, especially considering that it has to be done for every message.
14452 But don't despair! The function @code{gnus-group-split-setup} can be
14453 used to enable @code{gnus-group-split} in a much more efficient way. It
14454 sets @code{nnmail-split-methods} to @code{nnmail-split-fancy} and sets
14455 @code{nnmail-split-fancy} to the split produced by
14456 @code{gnus-group-split-fancy}. Thus, the group parameters are only
14457 scanned once, no matter how many messages are split.
14459 @findex gnus-group-split-update
14460 However, if you change group parameters, you'd have to update
14461 @code{nnmail-split-fancy} manually. You can do it by running
14462 @code{gnus-group-split-update}. If you'd rather have it updated
14463 automatically, just tell @code{gnus-group-split-setup} to do it for
14464 you. For example, add to your @file{~/.gnus.el}:
14467 (gnus-group-split-setup @var{auto-update} @var{catch-all})
14470 If @var{auto-update} is non-@code{nil}, @code{gnus-group-split-update}
14471 will be added to @code{nnmail-pre-get-new-mail-hook}, so you won't ever
14472 have to worry about updating @code{nnmail-split-fancy} again. If you
14473 don't omit @var{catch-all} (it's optional, equivalent to @code{nil}),
14474 @code{gnus-group-split-default-catch-all-group} will be set to its
14477 @vindex gnus-group-split-updated-hook
14478 Because you may want to change @code{nnmail-split-fancy} after it is set
14479 by @code{gnus-group-split-update}, this function will run
14480 @code{gnus-group-split-updated-hook} just before finishing.
14482 @node Incorporating Old Mail
14483 @subsection Incorporating Old Mail
14484 @cindex incorporating old mail
14485 @cindex import old mail
14487 Most people have lots of old mail stored in various file formats. If
14488 you have set up Gnus to read mail using one of the spiffy Gnus mail
14489 back ends, you'll probably wish to have that old mail incorporated into
14492 Doing so can be quite easy.
14494 To take an example: You're reading mail using @code{nnml}
14495 (@pxref{Mail Spool}), and have set @code{nnmail-split-methods} to a
14496 satisfactory value (@pxref{Splitting Mail}). You have an old Unix mbox
14497 file filled with important, but old, mail. You want to move it into
14498 your @code{nnml} groups.
14504 Go to the group buffer.
14507 Type @kbd{G f} and give the file name to the mbox file when prompted to create an
14508 @code{nndoc} group from the mbox file (@pxref{Foreign Groups}).
14511 Type @kbd{SPACE} to enter the newly created group.
14514 Type @kbd{M P b} to process-mark all articles in this group's buffer
14515 (@pxref{Setting Process Marks}).
14518 Type @kbd{B r} to respool all the process-marked articles, and answer
14519 @samp{nnml} when prompted (@pxref{Mail Group Commands}).
14522 All the mail messages in the mbox file will now also be spread out over
14523 all your @code{nnml} groups. Try entering them and check whether things
14524 have gone without a glitch. If things look ok, you may consider
14525 deleting the mbox file, but I wouldn't do that unless I was absolutely
14526 sure that all the mail has ended up where it should be.
14528 Respooling is also a handy thing to do if you're switching from one mail
14529 back end to another. Just respool all the mail in the old mail groups
14530 using the new mail back end.
14533 @node Expiring Mail
14534 @subsection Expiring Mail
14535 @cindex article expiry
14537 Traditional mail readers have a tendency to remove mail articles when
14538 you mark them as read, in some way. Gnus takes a fundamentally
14539 different approach to mail reading.
14541 Gnus basically considers mail just to be news that has been received in
14542 a rather peculiar manner. It does not think that it has the power to
14543 actually change the mail, or delete any mail messages. If you enter a
14544 mail group, and mark articles as ``read'', or kill them in some other
14545 fashion, the mail articles will still exist on the system. I repeat:
14546 Gnus will not delete your old, read mail. Unless you ask it to, of
14549 To make Gnus get rid of your unwanted mail, you have to mark the
14550 articles as @dfn{expirable}. (With the default key bindings, this means
14551 that you have to type @kbd{E}.) This does not mean that the articles
14552 will disappear right away, however. In general, a mail article will be
14553 deleted from your system if, 1) it is marked as expirable, AND 2) it is
14554 more than one week old. If you do not mark an article as expirable, it
14555 will remain on your system until hell freezes over. This bears
14556 repeating one more time, with some spurious capitalizations: IF you do
14557 NOT mark articles as EXPIRABLE, Gnus will NEVER delete those ARTICLES.
14559 You do not have to mark articles as expirable by hand. Gnus provides
14560 two features, called ``auto-expire'' and ``total-expire'', that can help you
14561 with this. In a nutshell, ``auto-expire'' means that Gnus hits @kbd{E}
14562 for you when you select an article. And ``total-expire'' means that Gnus
14563 considers all articles as expirable that are read. So, in addition to
14564 the articles marked @samp{E}, also the articles marked @samp{r},
14565 @samp{R}, @samp{O}, @samp{K}, @samp{Y} and so on are considered
14568 When should either auto-expire or total-expire be used? Most people
14569 who are subscribed to mailing lists split each list into its own group
14570 and then turn on auto-expire or total-expire for those groups.
14571 (@xref{Splitting Mail}, for more information on splitting each list
14572 into its own group.)
14574 Which one is better, auto-expire or total-expire? It's not easy to
14575 answer. Generally speaking, auto-expire is probably faster. Another
14576 advantage of auto-expire is that you get more marks to work with: for
14577 the articles that are supposed to stick around, you can still choose
14578 between tick and dormant and read marks. But with total-expire, you
14579 only have dormant and ticked to choose from. The advantage of
14580 total-expire is that it works well with adaptive scoring (@pxref{Adaptive
14581 Scoring}). Auto-expire works with normal scoring but not with adaptive
14584 @vindex gnus-auto-expirable-newsgroups
14585 Groups that match the regular expression
14586 @code{gnus-auto-expirable-newsgroups} will have all articles that you
14587 read marked as expirable automatically. All articles marked as
14588 expirable have an @samp{E} in the first column in the summary buffer.
14590 By default, if you have auto expiry switched on, Gnus will mark all the
14591 articles you read as expirable, no matter if they were read or unread
14592 before. To avoid having articles marked as read marked as expirable
14593 automatically, you can put something like the following in your
14594 @file{~/.gnus.el} file:
14596 @vindex gnus-mark-article-hook
14598 (remove-hook 'gnus-mark-article-hook
14599 'gnus-summary-mark-read-and-unread-as-read)
14600 (add-hook 'gnus-mark-article-hook 'gnus-summary-mark-unread-as-read)
14603 Note that making a group auto-expirable doesn't mean that all read
14604 articles are expired---only the articles marked as expirable
14605 will be expired. Also note that using the @kbd{d} command won't make
14606 articles expirable---only semi-automatic marking of articles as read will
14607 mark the articles as expirable in auto-expirable groups.
14609 Let's say you subscribe to a couple of mailing lists, and you want the
14610 articles you have read to disappear after a while:
14613 (setq gnus-auto-expirable-newsgroups
14614 "mail.nonsense-list\\|mail.nice-list")
14617 Another way to have auto-expiry happen is to have the element
14618 @code{auto-expire} in the group parameters of the group.
14620 If you use adaptive scoring (@pxref{Adaptive Scoring}) and
14621 auto-expiring, you'll have problems. Auto-expiring and adaptive scoring
14622 don't really mix very well.
14624 @vindex nnmail-expiry-wait
14625 The @code{nnmail-expiry-wait} variable supplies the default time an
14626 expirable article has to live. Gnus starts counting days from when the
14627 message @emph{arrived}, not from when it was sent. The default is seven
14630 Gnus also supplies a function that lets you fine-tune how long articles
14631 are to live, based on what group they are in. Let's say you want to
14632 have one month expiry period in the @samp{mail.private} group, a one day
14633 expiry period in the @samp{mail.junk} group, and a six day expiry period
14636 @vindex nnmail-expiry-wait-function
14638 (setq nnmail-expiry-wait-function
14640 (cond ((string= group "mail.private")
14642 ((string= group "mail.junk")
14644 ((string= group "important")
14650 The group names this function is fed are ``unadorned'' group
14651 names---no @samp{nnml:} prefixes and the like.
14653 The @code{nnmail-expiry-wait} variable and
14654 @code{nnmail-expiry-wait-function} function can either be a number (not
14655 necessarily an integer) or one of the symbols @code{immediate} or
14658 You can also use the @code{expiry-wait} group parameter to selectively
14659 change the expiry period (@pxref{Group Parameters}).
14661 @vindex nnmail-expiry-target
14662 The normal action taken when expiring articles is to delete them.
14663 However, in some circumstances it might make more sense to move them
14664 to other groups instead of deleting them. The variable
14665 @code{nnmail-expiry-target} (and the @code{expiry-target} group
14666 parameter) controls this. The variable supplies a default value for
14667 all groups, which can be overridden for specific groups by the group
14668 parameter. default value is @code{delete}, but this can also be a
14669 string (which should be the name of the group the message should be
14670 moved to), or a function (which will be called in a buffer narrowed to
14671 the message in question, and with the name of the group being moved
14672 from as its parameter) which should return a target---either a group
14673 name or @code{delete}.
14675 Here's an example for specifying a group name:
14677 (setq nnmail-expiry-target "nnml:expired")
14680 @findex nnmail-fancy-expiry-target
14681 @vindex nnmail-fancy-expiry-targets
14682 Gnus provides a function @code{nnmail-fancy-expiry-target} which will
14683 expire mail to groups according to the variable
14684 @code{nnmail-fancy-expiry-targets}. Here's an example:
14687 (setq nnmail-expiry-target 'nnmail-fancy-expiry-target
14688 nnmail-fancy-expiry-targets
14689 '((to-from "boss" "nnfolder:Work")
14690 ("subject" "IMPORTANT" "nnfolder:IMPORTANT.%Y.%b")
14691 ("from" ".*" "nnfolder:Archive-%Y")))
14694 With this setup, any mail that has @code{IMPORTANT} in its Subject
14695 header and was sent in the year @code{YYYY} and month @code{MMM}, will
14696 get expired to the group @code{nnfolder:IMPORTANT.YYYY.MMM}. If its
14697 From or To header contains the string @code{boss}, it will get expired
14698 to @code{nnfolder:Work}. All other mail will get expired to
14699 @code{nnfolder:Archive-YYYY}.
14701 @vindex nnmail-keep-last-article
14702 If @code{nnmail-keep-last-article} is non-@code{nil}, Gnus will never
14703 expire the final article in a mail newsgroup. This is to make life
14704 easier for procmail users.
14706 @vindex gnus-total-expirable-newsgroups
14707 By the way: That line up there, about Gnus never expiring non-expirable
14708 articles, is a lie. If you put @code{total-expire} in the group
14709 parameters, articles will not be marked as expirable, but all read
14710 articles will be put through the expiry process. Use with extreme
14711 caution. Even more dangerous is the
14712 @code{gnus-total-expirable-newsgroups} variable. All groups that match
14713 this regexp will have all read articles put through the expiry process,
14714 which means that @emph{all} old mail articles in the groups in question
14715 will be deleted after a while. Use with extreme caution, and don't come
14716 crying to me when you discover that the regexp you used matched the
14717 wrong group and all your important mail has disappeared. Be a
14718 @emph{man}! Or a @emph{woman}! Whatever you feel more comfortable
14721 Most people make most of their mail groups total-expirable, though.
14723 @vindex gnus-inhibit-user-auto-expire
14724 If @code{gnus-inhibit-user-auto-expire} is non-@code{nil}, user marking
14725 commands will not mark an article as expirable, even if the group has
14726 auto-expire turned on.
14730 @subsection Washing Mail
14731 @cindex mail washing
14732 @cindex list server brain damage
14733 @cindex incoming mail treatment
14735 Mailers and list servers are notorious for doing all sorts of really,
14736 really stupid things with mail. ``Hey, RFC 822 doesn't explicitly
14737 prohibit us from adding the string @code{wE aRe ElItE!!!!!1!!} to the
14738 end of all lines passing through our server, so let's do that!!!!1!''
14739 Yes, but RFC 822 wasn't designed to be read by morons. Things that were
14740 considered to be self-evident were not discussed. So. Here we are.
14742 Case in point: The German version of Microsoft Exchange adds @samp{AW:
14743 } to the subjects of replies instead of @samp{Re: }. I could pretend to
14744 be shocked and dismayed by this, but I haven't got the energy. It is to
14747 Gnus provides a plethora of functions for washing articles while
14748 displaying them, but it might be nicer to do the filtering before
14749 storing the mail to disk. For that purpose, we have three hooks and
14750 various functions that can be put in these hooks.
14753 @item nnmail-prepare-incoming-hook
14754 @vindex nnmail-prepare-incoming-hook
14755 This hook is called before doing anything with the mail and is meant for
14756 grand, sweeping gestures. It is called in a buffer that contains all
14757 the new, incoming mail. Functions to be used include:
14760 @item nnheader-ms-strip-cr
14761 @findex nnheader-ms-strip-cr
14762 Remove trailing carriage returns from each line. This is default on
14763 Emacs running on MS machines.
14767 @item nnmail-prepare-incoming-header-hook
14768 @vindex nnmail-prepare-incoming-header-hook
14769 This hook is called narrowed to each header. It can be used when
14770 cleaning up the headers. Functions that can be used include:
14773 @item nnmail-remove-leading-whitespace
14774 @findex nnmail-remove-leading-whitespace
14775 Clear leading white space that ``helpful'' listservs have added to the
14776 headers to make them look nice. Aaah.
14778 (Note that this function works on both the header on the body of all
14779 messages, so it is a potentially dangerous function to use (if a body
14780 of a message contains something that looks like a header line). So
14781 rather than fix the bug, it is of course the right solution to make it
14782 into a feature by documenting it.)
14784 @item nnmail-remove-list-identifiers
14785 @findex nnmail-remove-list-identifiers
14786 Some list servers add an identifier---for example, @samp{(idm)}---to the
14787 beginning of all @code{Subject} headers. I'm sure that's nice for
14788 people who use stone age mail readers. This function will remove
14789 strings that match the @code{nnmail-list-identifiers} regexp, which can
14790 also be a list of regexp. @code{nnmail-list-identifiers} may not contain
14793 For instance, if you want to remove the @samp{(idm)} and the
14794 @samp{nagnagnag} identifiers:
14797 (setq nnmail-list-identifiers
14798 '("(idm)" "nagnagnag"))
14801 This can also be done non-destructively with
14802 @code{gnus-list-identifiers}, @xref{Article Hiding}.
14804 @item nnmail-remove-tabs
14805 @findex nnmail-remove-tabs
14806 Translate all @samp{TAB} characters into @samp{SPACE} characters.
14808 @item nnmail-fix-eudora-headers
14809 @findex nnmail-fix-eudora-headers
14811 Eudora produces broken @code{References} headers, but OK
14812 @code{In-Reply-To} headers. This function will get rid of the
14813 @code{References} headers.
14817 @item nnmail-prepare-incoming-message-hook
14818 @vindex nnmail-prepare-incoming-message-hook
14819 This hook is called narrowed to each message. Functions to be used
14823 @item article-de-quoted-unreadable
14824 @findex article-de-quoted-unreadable
14825 Decode Quoted Readable encoding.
14832 @subsection Duplicates
14834 @vindex nnmail-treat-duplicates
14835 @vindex nnmail-message-id-cache-length
14836 @vindex nnmail-message-id-cache-file
14837 @cindex duplicate mails
14838 If you are a member of a couple of mailing lists, you will sometimes
14839 receive two copies of the same mail. This can be quite annoying, so
14840 @code{nnmail} checks for and treats any duplicates it might find. To do
14841 this, it keeps a cache of old @code{Message-ID}s---
14842 @code{nnmail-message-id-cache-file}, which is @file{~/.nnmail-cache} by
14843 default. The approximate maximum number of @code{Message-ID}s stored
14844 there is controlled by the @code{nnmail-message-id-cache-length}
14845 variable, which is 1000 by default. (So 1000 @code{Message-ID}s will be
14846 stored.) If all this sounds scary to you, you can set
14847 @code{nnmail-treat-duplicates} to @code{warn} (which is what it is by
14848 default), and @code{nnmail} won't delete duplicate mails. Instead it
14849 will insert a warning into the head of the mail saying that it thinks
14850 that this is a duplicate of a different message.
14852 This variable can also be a function. If that's the case, the function
14853 will be called from a buffer narrowed to the message in question with
14854 the @code{Message-ID} as a parameter. The function must return either
14855 @code{nil}, @code{warn}, or @code{delete}.
14857 You can turn this feature off completely by setting the variable to
14860 If you want all the duplicate mails to be put into a special
14861 @dfn{duplicates} group, you could do that using the normal mail split
14865 (setq nnmail-split-fancy
14866 '(| ;; @r{Messages duplicates go to a separate group.}
14867 ("gnus-warning" "duplicat\\(e\\|ion\\) of message" "duplicate")
14868 ;; @r{Message from daemons, postmaster, and the like to another.}
14869 (any mail "mail.misc")
14870 ;; @r{Other rules.}
14876 (setq nnmail-split-methods
14877 '(("duplicates" "^Gnus-Warning:.*duplicate")
14878 ;; @r{Other rules.}
14882 Here's a neat feature: If you know that the recipient reads her mail
14883 with Gnus, and that she has @code{nnmail-treat-duplicates} set to
14884 @code{delete}, you can send her as many insults as you like, just by
14885 using a @code{Message-ID} of a mail that you know that she's already
14886 received. Think of all the fun! She'll never see any of it! Whee!
14889 @node Not Reading Mail
14890 @subsection Not Reading Mail
14892 If you start using any of the mail back ends, they have the annoying
14893 habit of assuming that you want to read mail with them. This might not
14894 be unreasonable, but it might not be what you want.
14896 If you set @code{mail-sources} and @code{nnmail-spool-file} to
14897 @code{nil}, none of the back ends will ever attempt to read incoming
14898 mail, which should help.
14900 @vindex nnbabyl-get-new-mail
14901 @vindex nnmbox-get-new-mail
14902 @vindex nnml-get-new-mail
14903 @vindex nnmh-get-new-mail
14904 @vindex nnfolder-get-new-mail
14905 This might be too much, if, for instance, you are reading mail quite
14906 happily with @code{nnml} and just want to peek at some old Rmail
14907 file you have stashed away with @code{nnbabyl}. All back ends have
14908 variables called back-end-@code{get-new-mail}. If you want to disable
14909 the @code{nnbabyl} mail reading, you edit the virtual server for the
14910 group to have a setting where @code{nnbabyl-get-new-mail} to @code{nil}.
14912 All the mail back ends will call @code{nn}*@code{-prepare-save-mail-hook}
14913 narrowed to the article to be saved before saving it when reading
14917 @node Choosing a Mail Back End
14918 @subsection Choosing a Mail Back End
14920 Gnus will read the mail spool when you activate a mail group. The mail
14921 file is first copied to your home directory. What happens after that
14922 depends on what format you want to store your mail in.
14924 There are six different mail back ends in the standard Gnus, and more
14925 back ends are available separately. The mail back end most people use
14926 (because it is possibly the fastest) is @code{nnml} (@pxref{Mail
14930 * Unix Mail Box:: Using the (quite) standard Un*x mbox.
14931 * Rmail Babyl:: Emacs programs use the Rmail Babyl format.
14932 * Mail Spool:: Store your mail in a private spool?
14933 * MH Spool:: An mhspool-like back end.
14934 * Maildir:: Another one-file-per-message format.
14935 * Mail Folders:: Having one file for each group.
14936 * Comparing Mail Back Ends:: An in-depth looks at pros and cons.
14940 @node Unix Mail Box
14941 @subsubsection Unix Mail Box
14943 @cindex unix mail box
14945 @vindex nnmbox-active-file
14946 @vindex nnmbox-mbox-file
14947 The @dfn{nnmbox} back end will use the standard Un*x mbox file to store
14948 mail. @code{nnmbox} will add extra headers to each mail article to say
14949 which group it belongs in.
14951 Virtual server settings:
14954 @item nnmbox-mbox-file
14955 @vindex nnmbox-mbox-file
14956 The name of the mail box in the user's home directory. Default is
14959 @item nnmbox-active-file
14960 @vindex nnmbox-active-file
14961 The name of the active file for the mail box. Default is
14962 @file{~/.mbox-active}.
14964 @item nnmbox-get-new-mail
14965 @vindex nnmbox-get-new-mail
14966 If non-@code{nil}, @code{nnmbox} will read incoming mail and split it
14967 into groups. Default is @code{t}.
14972 @subsubsection Rmail Babyl
14976 @vindex nnbabyl-active-file
14977 @vindex nnbabyl-mbox-file
14978 The @dfn{nnbabyl} back end will use a Babyl mail box (aka. @dfn{Rmail
14979 mbox}) to store mail. @code{nnbabyl} will add extra headers to each
14980 mail article to say which group it belongs in.
14982 Virtual server settings:
14985 @item nnbabyl-mbox-file
14986 @vindex nnbabyl-mbox-file
14987 The name of the Rmail mbox file. The default is @file{~/RMAIL}
14989 @item nnbabyl-active-file
14990 @vindex nnbabyl-active-file
14991 The name of the active file for the rmail box. The default is
14992 @file{~/.rmail-active}
14994 @item nnbabyl-get-new-mail
14995 @vindex nnbabyl-get-new-mail
14996 If non-@code{nil}, @code{nnbabyl} will read incoming mail. Default is
15002 @subsubsection Mail Spool
15004 @cindex mail @acronym{NOV} spool
15006 The @dfn{nnml} spool mail format isn't compatible with any other known
15007 format. It should be used with some caution.
15009 @vindex nnml-directory
15010 If you use this back end, Gnus will split all incoming mail into files,
15011 one file for each mail, and put the articles into the corresponding
15012 directories under the directory specified by the @code{nnml-directory}
15013 variable. The default value is @file{~/Mail/}.
15015 You do not have to create any directories beforehand; Gnus will take
15018 If you have a strict limit as to how many files you are allowed to store
15019 in your account, you should not use this back end. As each mail gets its
15020 own file, you might very well occupy thousands of inodes within a few
15021 weeks. If this is no problem for you, and it isn't a problem for you
15022 having your friendly systems administrator walking around, madly,
15023 shouting ``Who is eating all my inodes?! Who? Who!?!'', then you should
15024 know that this is probably the fastest format to use. You do not have
15025 to trudge through a big mbox file just to read your new mail.
15027 @code{nnml} is probably the slowest back end when it comes to article
15028 splitting. It has to create lots of files, and it also generates
15029 @acronym{NOV} databases for the incoming mails. This makes it possibly the
15030 fastest back end when it comes to reading mail.
15032 @cindex self contained nnml servers
15034 When the marks file is used (which it is by default), @code{nnml}
15035 servers have the property that you may backup them using @code{tar} or
15036 similar, and later be able to restore them into Gnus (by adding the
15037 proper @code{nnml} server) and have all your marks be preserved. Marks
15038 for a group is usually stored in the @code{.marks} file (but see
15039 @code{nnml-marks-file-name}) within each @code{nnml} group's directory.
15040 Individual @code{nnml} groups are also possible to backup, use @kbd{G m}
15041 to restore the group (after restoring the backup into the nnml
15044 If for some reason you believe your @file{.marks} files are screwed
15045 up, you can just delete them all. Gnus will then correctly regenerate
15046 them next time it starts.
15048 Virtual server settings:
15051 @item nnml-directory
15052 @vindex nnml-directory
15053 All @code{nnml} directories will be placed under this directory. The
15054 default is the value of @code{message-directory} (whose default value
15057 @item nnml-active-file
15058 @vindex nnml-active-file
15059 The active file for the @code{nnml} server. The default is
15060 @file{~/Mail/active}.
15062 @item nnml-newsgroups-file
15063 @vindex nnml-newsgroups-file
15064 The @code{nnml} group descriptions file. @xref{Newsgroups File
15065 Format}. The default is @file{~/Mail/newsgroups}.
15067 @item nnml-get-new-mail
15068 @vindex nnml-get-new-mail
15069 If non-@code{nil}, @code{nnml} will read incoming mail. The default is
15072 @item nnml-nov-is-evil
15073 @vindex nnml-nov-is-evil
15074 If non-@code{nil}, this back end will ignore any @acronym{NOV} files. The
15075 default is @code{nil}.
15077 @item nnml-nov-file-name
15078 @vindex nnml-nov-file-name
15079 The name of the @acronym{NOV} files. The default is @file{.overview}.
15081 @item nnml-prepare-save-mail-hook
15082 @vindex nnml-prepare-save-mail-hook
15083 Hook run narrowed to an article before saving.
15085 @item nnml-marks-is-evil
15086 @vindex nnml-marks-is-evil
15087 If non-@code{nil}, this back end will ignore any @sc{marks} files. The
15088 default is @code{nil}.
15090 @item nnml-marks-file-name
15091 @vindex nnml-marks-file-name
15092 The name of the @dfn{marks} files. The default is @file{.marks}.
15094 @item nnml-use-compressed-files
15095 @vindex nnml-use-compressed-files
15096 If non-@code{nil}, @code{nnml} will allow using compressed message
15101 @findex nnml-generate-nov-databases
15102 If your @code{nnml} groups and @acronym{NOV} files get totally out of
15103 whack, you can do a complete update by typing @kbd{M-x
15104 nnml-generate-nov-databases}. This command will trawl through the
15105 entire @code{nnml} hierarchy, looking at each and every article, so it
15106 might take a while to complete. A better interface to this
15107 functionality can be found in the server buffer (@pxref{Server
15112 @subsubsection MH Spool
15114 @cindex mh-e mail spool
15116 @code{nnmh} is just like @code{nnml}, except that is doesn't generate
15117 @acronym{NOV} databases and it doesn't keep an active file or marks
15118 file. This makes @code{nnmh} a @emph{much} slower back end than
15119 @code{nnml}, but it also makes it easier to write procmail scripts
15122 Virtual server settings:
15125 @item nnmh-directory
15126 @vindex nnmh-directory
15127 All @code{nnmh} directories will be located under this directory. The
15128 default is the value of @code{message-directory} (whose default is
15131 @item nnmh-get-new-mail
15132 @vindex nnmh-get-new-mail
15133 If non-@code{nil}, @code{nnmh} will read incoming mail. The default is
15137 @vindex nnmh-be-safe
15138 If non-@code{nil}, @code{nnmh} will go to ridiculous lengths to make
15139 sure that the articles in the folder are actually what Gnus thinks
15140 they are. It will check date stamps and stat everything in sight, so
15141 setting this to @code{t} will mean a serious slow-down. If you never
15142 use anything but Gnus to read the @code{nnmh} articles, you do not
15143 have to set this variable to @code{t}. The default is @code{nil}.
15148 @subsubsection Maildir
15152 @code{nnmaildir} stores mail in the maildir format, with each maildir
15153 corresponding to a group in Gnus. This format is documented here:
15154 @uref{http://cr.yp.to/proto/maildir.html} and here:
15155 @uref{http://www.qmail.org/man/man5/maildir.html}. @code{nnmaildir}
15156 also stores extra information in the @file{.nnmaildir/} directory
15159 Maildir format was designed to allow concurrent deliveries and
15160 reading, without needing locks. With other back ends, you would have
15161 your mail delivered to a spool of some kind, and then you would
15162 configure Gnus to split mail from that spool into your groups. You
15163 can still do that with @code{nnmaildir}, but the more common
15164 configuration is to have your mail delivered directly to the maildirs
15165 that appear as group in Gnus.
15167 @code{nnmaildir} is designed to be perfectly reliable: @kbd{C-g} will
15168 never corrupt its data in memory, and @code{SIGKILL} will never
15169 corrupt its data in the filesystem.
15171 @code{nnmaildir} stores article marks and @acronym{NOV} data in each
15172 maildir. So you can copy a whole maildir from one Gnus setup to
15173 another, and you will keep your marks.
15175 Virtual server settings:
15179 For each of your @code{nnmaildir} servers (it's very unlikely that
15180 you'd need more than one), you need to create a directory and populate
15181 it with maildirs or symlinks to maildirs (and nothing else; do not
15182 choose a directory already used for other purposes). Each maildir
15183 will be represented in Gnus as a newsgroup on that server; the
15184 filename of the symlink will be the name of the group. Any filenames
15185 in the directory starting with @samp{.} are ignored. The directory is
15186 scanned when you first start Gnus, and each time you type @kbd{g} in
15187 the group buffer; if any maildirs have been removed or added,
15188 @code{nnmaildir} notices at these times.
15190 The value of the @code{directory} parameter should be a Lisp form
15191 which is processed by @code{eval} and @code{expand-file-name} to get
15192 the path of the directory for this server. The form is @code{eval}ed
15193 only when the server is opened; the resulting string is used until the
15194 server is closed. (If you don't know about forms and @code{eval},
15195 don't worry---a simple string will work.) This parameter is not
15196 optional; you must specify it. I don't recommend using
15197 @code{"~/Mail"} or a subdirectory of it; several other parts of Gnus
15198 use that directory by default for various things, and may get confused
15199 if @code{nnmaildir} uses it too. @code{"~/.nnmaildir"} is a typical
15202 @item target-prefix
15203 This should be a Lisp form which is processed by @code{eval} and
15204 @code{expand-file-name}. The form is @code{eval}ed only when the
15205 server is opened; the resulting string is used until the server is
15208 When you create a group on an @code{nnmaildir} server, the maildir is
15209 created with @code{target-prefix} prepended to its name, and a symlink
15210 pointing to that maildir is created, named with the plain group name.
15211 So if @code{directory} is @code{"~/.nnmaildir"} and
15212 @code{target-prefix} is @code{"../maildirs/"}, then when you create
15213 the group @code{foo}, @code{nnmaildir} will create
15214 @file{~/.nnmaildir/../maildirs/foo} as a maildir, and will create
15215 @file{~/.nnmaildir/foo} as a symlink pointing to
15216 @file{../maildirs/foo}.
15218 You can set @code{target-prefix} to a string without any slashes to
15219 create both maildirs and symlinks in the same @code{directory}; in
15220 this case, any maildirs found in @code{directory} whose names start
15221 with @code{target-prefix} will not be listed as groups (but the
15222 symlinks pointing to them will be).
15224 As a special case, if @code{target-prefix} is @code{""} (the default),
15225 then when you create a group, the maildir will be created in
15226 @code{directory} without a corresponding symlink. Beware that you
15227 cannot use @code{gnus-group-delete-group} on such groups without the
15228 @code{force} argument.
15230 @item directory-files
15231 This should be a function with the same interface as
15232 @code{directory-files} (such as @code{directory-files} itself). It is
15233 used to scan the server's @code{directory} for maildirs. This
15234 parameter is optional; the default is
15235 @code{nnheader-directory-files-safe} if
15236 @code{nnheader-directory-files-is-safe} is @code{nil}, and
15237 @code{directory-files} otherwise.
15238 (@code{nnheader-directory-files-is-safe} is checked only once when the
15239 server is opened; if you want to check it each time the directory is
15240 scanned, you'll have to provide your own function that does that.)
15243 If non-@code{nil}, then after scanning for new mail in the group
15244 maildirs themselves as usual, this server will also incorporate mail
15245 the conventional Gnus way, from @code{mail-sources} according to
15246 @code{nnmail-split-methods} or @code{nnmail-split-fancy}. The default
15247 value is @code{nil}.
15249 Do @emph{not} use the same maildir both in @code{mail-sources} and as
15250 an @code{nnmaildir} group. The results might happen to be useful, but
15251 that would be by chance, not by design, and the results might be
15252 different in the future. If your split rules create new groups,
15253 remember to supply a @code{create-directory} server parameter.
15256 @subsubsection Group parameters
15258 @code{nnmaildir} uses several group parameters. It's safe to ignore
15259 all this; the default behavior for @code{nnmaildir} is the same as the
15260 default behavior for other mail back ends: articles are deleted after
15261 one week, etc. Except for the expiry parameters, all this
15262 functionality is unique to @code{nnmaildir}, so you can ignore it if
15263 you're just trying to duplicate the behavior you already have with
15266 If the value of any of these parameters is a vector, the first element
15267 is evaluated as a Lisp form and the result is used, rather than the
15268 original value. If the value is not a vector, the value itself is
15269 evaluated as a Lisp form. (This is why these parameters use names
15270 different from those of other, similar parameters supported by other
15271 back ends: they have different, though similar, meanings.) (For
15272 numbers, strings, @code{nil}, and @code{t}, you can ignore the
15273 @code{eval} business again; for other values, remember to use an extra
15274 quote and wrap the value in a vector when appropriate.)
15278 An integer specifying the minimum age, in seconds, of an article
15279 before it will be expired, or the symbol @code{never} to specify that
15280 articles should never be expired. If this parameter is not set,
15281 @code{nnmaildir} falls back to the usual
15282 @code{nnmail-expiry-wait}(@code{-function}) variables (overrideable by
15283 the @code{expiry-wait}(@code{-function}) group parameters. If you
15284 wanted a value of 3 days, you could use something like @code{[(* 3 24
15285 60 60)]}; @code{nnmaildir} will evaluate the form and use the result.
15286 An article's age is measured starting from the article file's
15287 modification time. Normally, this is the same as the article's
15288 delivery time, but editing an article makes it younger. Moving an
15289 article (other than via expiry) may also make an article younger.
15292 If this is set to a string such as a full Gnus group name, like
15294 "backend+server.address.string:group.name"
15296 and if it is not the name of the same group that the parameter belongs
15297 to, then articles will be moved to the specified group during expiry
15298 before being deleted. @emph{If this is set to an @code{nnmaildir}
15299 group, the article will be just as old in the destination group as it
15300 was in the source group.} So be careful with @code{expire-age} in the
15301 destination group. If this is set to the name of the same group that
15302 the parameter belongs to, then the article is not expired at all. If
15303 you use the vector form, the first element is evaluated once for each
15304 article. So that form can refer to
15305 @code{nnmaildir-article-file-name}, etc., to decide where to put the
15306 article. @emph{If this parameter is not set, @code{nnmaildir} does
15307 not fall back to the @code{expiry-target} group parameter or the
15308 @code{nnmail-expiry-target} variable.}
15311 If this is set to @code{t}, @code{nnmaildir} will treat the articles
15312 in this maildir as read-only. This means: articles are not renamed
15313 from @file{new/} into @file{cur/}; articles are only found in
15314 @file{new/}, not @file{cur/}; articles are never deleted; articles
15315 cannot be edited. @file{new/} is expected to be a symlink to the
15316 @file{new/} directory of another maildir---e.g., a system-wide mailbox
15317 containing a mailing list of common interest. Everything in the
15318 maildir outside @file{new/} is @emph{not} treated as read-only, so for
15319 a shared mailbox, you do still need to set up your own maildir (or
15320 have write permission to the shared mailbox); your maildir just won't
15321 contain extra copies of the articles.
15323 @item directory-files
15324 A function with the same interface as @code{directory-files}. It is
15325 used to scan the directories in the maildir corresponding to this
15326 group to find articles. The default is the function specified by the
15327 server's @code{directory-files} parameter.
15329 @item distrust-Lines:
15330 If non-@code{nil}, @code{nnmaildir} will always count the lines of an
15331 article, rather than use the @code{Lines:} header field. If
15332 @code{nil}, the header field will be used if present.
15335 A list of mark symbols, such as @code{['(read expire)]}. Whenever
15336 Gnus asks @code{nnmaildir} for article marks, @code{nnmaildir} will
15337 say that all articles have these marks, regardless of whether the
15338 marks stored in the filesystem say so. This is a proof-of-concept
15339 feature that will probably be removed eventually; it ought to be done
15340 in Gnus proper, or abandoned if it's not worthwhile.
15343 A list of mark symbols, such as @code{['(tick expire)]}. Whenever
15344 Gnus asks @code{nnmaildir} for article marks, @code{nnmaildir} will
15345 say that no articles have these marks, regardless of whether the marks
15346 stored in the filesystem say so. @code{never-marks} overrides
15347 @code{always-marks}. This is a proof-of-concept feature that will
15348 probably be removed eventually; it ought to be done in Gnus proper, or
15349 abandoned if it's not worthwhile.
15351 @item nov-cache-size
15352 An integer specifying the size of the @acronym{NOV} memory cache. To
15353 speed things up, @code{nnmaildir} keeps @acronym{NOV} data in memory
15354 for a limited number of articles in each group. (This is probably not
15355 worthwhile, and will probably be removed in the future.) This
15356 parameter's value is noticed only the first time a group is seen after
15357 the server is opened---i.e., when you first start Gnus, typically.
15358 The @acronym{NOV} cache is never resized until the server is closed
15359 and reopened. The default is an estimate of the number of articles
15360 that would be displayed in the summary buffer: a count of articles
15361 that are either marked with @code{tick} or not marked with
15362 @code{read}, plus a little extra.
15365 @subsubsection Article identification
15366 Articles are stored in the @file{cur/} subdirectory of each maildir.
15367 Each article file is named like @code{uniq:info}, where @code{uniq}
15368 contains no colons. @code{nnmaildir} ignores, but preserves, the
15369 @code{:info} part. (Other maildir readers typically use this part of
15370 the filename to store marks.) The @code{uniq} part uniquely
15371 identifies the article, and is used in various places in the
15372 @file{.nnmaildir/} subdirectory of the maildir to store information
15373 about the corresponding article. The full pathname of an article is
15374 available in the variable @code{nnmaildir-article-file-name} after you
15375 request the article in the summary buffer.
15377 @subsubsection NOV data
15378 An article identified by @code{uniq} has its @acronym{NOV} data (used
15379 to generate lines in the summary buffer) stored in
15380 @code{.nnmaildir/nov/uniq}. There is no
15381 @code{nnmaildir-generate-nov-databases} function. (There isn't much
15382 need for it---an article's @acronym{NOV} data is updated automatically
15383 when the article or @code{nnmail-extra-headers} has changed.) You can
15384 force @code{nnmaildir} to regenerate the @acronym{NOV} data for a
15385 single article simply by deleting the corresponding @acronym{NOV}
15386 file, but @emph{beware}: this will also cause @code{nnmaildir} to
15387 assign a new article number for this article, which may cause trouble
15388 with @code{seen} marks, the Agent, and the cache.
15390 @subsubsection Article marks
15391 An article identified by @code{uniq} is considered to have the mark
15392 @code{flag} when the file @file{.nnmaildir/marks/flag/uniq} exists.
15393 When Gnus asks @code{nnmaildir} for a group's marks, @code{nnmaildir}
15394 looks for such files and reports the set of marks it finds. When Gnus
15395 asks @code{nnmaildir} to store a new set of marks, @code{nnmaildir}
15396 creates and deletes the corresponding files as needed. (Actually,
15397 rather than create a new file for each mark, it just creates hard
15398 links to @file{.nnmaildir/markfile}, to save inodes.)
15400 You can invent new marks by creating a new directory in
15401 @file{.nnmaildir/marks/}. You can tar up a maildir and remove it from
15402 your server, untar it later, and keep your marks. You can add and
15403 remove marks yourself by creating and deleting mark files. If you do
15404 this while Gnus is running and your @code{nnmaildir} server is open,
15405 it's best to exit all summary buffers for @code{nnmaildir} groups and
15406 type @kbd{s} in the group buffer first, and to type @kbd{g} or
15407 @kbd{M-g} in the group buffer afterwards. Otherwise, Gnus might not
15408 pick up the changes, and might undo them.
15412 @subsubsection Mail Folders
15414 @cindex mbox folders
15415 @cindex mail folders
15417 @code{nnfolder} is a back end for storing each mail group in a
15418 separate file. Each file is in the standard Un*x mbox format.
15419 @code{nnfolder} will add extra headers to keep track of article
15420 numbers and arrival dates.
15422 @cindex self contained nnfolder servers
15424 When the marks file is used (which it is by default), @code{nnfolder}
15425 servers have the property that you may backup them using @code{tar} or
15426 similar, and later be able to restore them into Gnus (by adding the
15427 proper @code{nnfolder} server) and have all your marks be preserved.
15428 Marks for a group is usually stored in a file named as the mbox file
15429 with @code{.mrk} concatenated to it (but see
15430 @code{nnfolder-marks-file-suffix}) within the @code{nnfolder}
15431 directory. Individual @code{nnfolder} groups are also possible to
15432 backup, use @kbd{G m} to restore the group (after restoring the backup
15433 into the @code{nnfolder} directory).
15435 Virtual server settings:
15438 @item nnfolder-directory
15439 @vindex nnfolder-directory
15440 All the @code{nnfolder} mail boxes will be stored under this
15441 directory. The default is the value of @code{message-directory}
15442 (whose default is @file{~/Mail})
15444 @item nnfolder-active-file
15445 @vindex nnfolder-active-file
15446 The name of the active file. The default is @file{~/Mail/active}.
15448 @item nnfolder-newsgroups-file
15449 @vindex nnfolder-newsgroups-file
15450 The name of the group descriptions file. @xref{Newsgroups File
15451 Format}. The default is @file{~/Mail/newsgroups}
15453 @item nnfolder-get-new-mail
15454 @vindex nnfolder-get-new-mail
15455 If non-@code{nil}, @code{nnfolder} will read incoming mail. The
15456 default is @code{t}
15458 @item nnfolder-save-buffer-hook
15459 @vindex nnfolder-save-buffer-hook
15460 @cindex backup files
15461 Hook run before saving the folders. Note that Emacs does the normal
15462 backup renaming of files even with the @code{nnfolder} buffers. If
15463 you wish to switch this off, you could say something like the
15464 following in your @file{.emacs} file:
15467 (defun turn-off-backup ()
15468 (set (make-local-variable 'backup-inhibited) t))
15470 (add-hook 'nnfolder-save-buffer-hook 'turn-off-backup)
15473 @item nnfolder-delete-mail-hook
15474 @vindex nnfolder-delete-mail-hook
15475 Hook run in a buffer narrowed to the message that is to be deleted.
15476 This function can be used to copy the message to somewhere else, or to
15477 extract some information from it before removing it.
15479 @item nnfolder-nov-is-evil
15480 @vindex nnfolder-nov-is-evil
15481 If non-@code{nil}, this back end will ignore any @acronym{NOV} files. The
15482 default is @code{nil}.
15484 @item nnfolder-nov-file-suffix
15485 @vindex nnfolder-nov-file-suffix
15486 The extension for @acronym{NOV} files. The default is @file{.nov}.
15488 @item nnfolder-nov-directory
15489 @vindex nnfolder-nov-directory
15490 The directory where the @acronym{NOV} files should be stored. If
15491 @code{nil}, @code{nnfolder-directory} is used.
15493 @item nnfolder-marks-is-evil
15494 @vindex nnfolder-marks-is-evil
15495 If non-@code{nil}, this back end will ignore any @sc{marks} files. The
15496 default is @code{nil}.
15498 @item nnfolder-marks-file-suffix
15499 @vindex nnfolder-marks-file-suffix
15500 The extension for @sc{marks} files. The default is @file{.mrk}.
15502 @item nnfolder-marks-directory
15503 @vindex nnfolder-marks-directory
15504 The directory where the @sc{marks} files should be stored. If
15505 @code{nil}, @code{nnfolder-directory} is used.
15510 @findex nnfolder-generate-active-file
15511 @kindex M-x nnfolder-generate-active-file
15512 If you have lots of @code{nnfolder}-like files you'd like to read with
15513 @code{nnfolder}, you can use the @kbd{M-x nnfolder-generate-active-file}
15514 command to make @code{nnfolder} aware of all likely files in
15515 @code{nnfolder-directory}. This only works if you use long file names,
15518 @node Comparing Mail Back Ends
15519 @subsubsection Comparing Mail Back Ends
15521 First, just for terminology, the @dfn{back end} is the common word for a
15522 low-level access method---a transport, if you will, by which something
15523 is acquired. The sense is that one's mail has to come from somewhere,
15524 and so selection of a suitable back end is required in order to get that
15525 mail within spitting distance of Gnus.
15527 The same concept exists for Usenet itself: Though access to articles is
15528 typically done by @acronym{NNTP} these days, once upon a midnight dreary, everyone
15529 in the world got at Usenet by running a reader on the machine where the
15530 articles lay (the machine which today we call an @acronym{NNTP} server), and
15531 access was by the reader stepping into the articles' directory spool
15532 area directly. One can still select between either the @code{nntp} or
15533 @code{nnspool} back ends, to select between these methods, if one happens
15534 actually to live on the server (or can see its spool directly, anyway,
15537 The goal in selecting a mail back end is to pick one which
15538 simultaneously represents a suitable way of dealing with the original
15539 format plus leaving mail in a form that is convenient to use in the
15540 future. Here are some high and low points on each:
15545 UNIX systems have historically had a single, very common, and well-
15546 defined format. All messages arrive in a single @dfn{spool file}, and
15547 they are delineated by a line whose regular expression matches
15548 @samp{^From_}. (My notational use of @samp{_} is to indicate a space,
15549 to make it clear in this instance that this is not the RFC-specified
15550 @samp{From:} header.) Because Emacs and therefore Gnus emanate
15551 historically from the Unix environment, it is simplest if one does not
15552 mess a great deal with the original mailbox format, so if one chooses
15553 this back end, Gnus' primary activity in getting mail from the real spool
15554 area to Gnus' preferred directory is simply to copy it, with no
15555 (appreciable) format change in the process. It is the ``dumbest'' way
15556 to move mail into availability in the Gnus environment. This makes it
15557 fast to move into place, but slow to parse, when Gnus has to look at
15562 Once upon a time, there was the DEC-10 and DEC-20, running operating
15563 systems called TOPS and related things, and the usual (only?) mail
15564 reading environment was a thing called Babyl. I don't know what format
15565 was used for mail landing on the system, but Babyl had its own internal
15566 format to which mail was converted, primarily involving creating a
15567 spool-file-like entity with a scheme for inserting Babyl-specific
15568 headers and status bits above the top of each message in the file.
15569 Rmail was Emacs' first mail reader, it was written by Richard Stallman,
15570 and Stallman came out of that TOPS/Babyl environment, so he wrote Rmail
15571 to understand the mail files folks already had in existence. Gnus (and
15572 VM, for that matter) continue to support this format because it's
15573 perceived as having some good qualities in those mailer-specific
15574 headers/status bits stuff. Rmail itself still exists as well, of
15575 course, and is still maintained by Stallman.
15577 Both of the above forms leave your mail in a single file on your
15578 file system, and they must parse that entire file each time you take a
15583 @code{nnml} is the back end which smells the most as though you were
15584 actually operating with an @code{nnspool}-accessed Usenet system. (In
15585 fact, I believe @code{nnml} actually derived from @code{nnspool} code,
15586 lo these years ago.) One's mail is taken from the original spool file,
15587 and is then cut up into individual message files, 1:1. It maintains a
15588 Usenet-style active file (analogous to what one finds in an INN- or
15589 CNews-based news system in (for instance) @file{/var/lib/news/active},
15590 or what is returned via the @samp{NNTP LIST} verb) and also creates
15591 @dfn{overview} files for efficient group entry, as has been defined for
15592 @acronym{NNTP} servers for some years now. It is slower in mail-splitting,
15593 due to the creation of lots of files, updates to the @code{nnml} active
15594 file, and additions to overview files on a per-message basis, but it is
15595 extremely fast on access because of what amounts to the indexing support
15596 provided by the active file and overviews.
15598 @code{nnml} costs @dfn{inodes} in a big way; that is, it soaks up the
15599 resource which defines available places in the file system to put new
15600 files. Sysadmins take a dim view of heavy inode occupation within
15601 tight, shared file systems. But if you live on a personal machine where
15602 the file system is your own and space is not at a premium, @code{nnml}
15605 It is also problematic using this back end if you are living in a
15606 FAT16-based Windows world, since much space will be wasted on all these
15611 The Rand MH mail-reading system has been around UNIX systems for a very
15612 long time; it operates by splitting one's spool file of messages into
15613 individual files, but with little or no indexing support---@code{nnmh}
15614 is considered to be semantically equivalent to ``@code{nnml} without
15615 active file or overviews''. This is arguably the worst choice, because
15616 one gets the slowness of individual file creation married to the
15617 slowness of access parsing when learning what's new in one's groups.
15621 Basically the effect of @code{nnfolder} is @code{nnmbox} (the first
15622 method described above) on a per-group basis. That is, @code{nnmbox}
15623 itself puts @emph{all} one's mail in one file; @code{nnfolder} provides a
15624 little bit of optimization to this so that each of one's mail groups has
15625 a Unix mail box file. It's faster than @code{nnmbox} because each group
15626 can be parsed separately, and still provides the simple Unix mail box
15627 format requiring minimal effort in moving the mail around. In addition,
15628 it maintains an ``active'' file making it much faster for Gnus to figure
15629 out how many messages there are in each separate group.
15631 If you have groups that are expected to have a massive amount of
15632 messages, @code{nnfolder} is not the best choice, but if you receive
15633 only a moderate amount of mail, @code{nnfolder} is probably the most
15634 friendly mail back end all over.
15638 For configuring expiry and other things, @code{nnmaildir} uses
15639 incompatible group parameters, slightly different from those of other
15642 @code{nnmaildir} is largely similar to @code{nnml}, with some notable
15643 differences. Each message is stored in a separate file, but the
15644 filename is unrelated to the article number in Gnus. @code{nnmaildir}
15645 also stores the equivalent of @code{nnml}'s overview files in one file
15646 per article, so it uses about twice as many inodes as @code{nnml}. (Use
15647 @code{df -i} to see how plentiful your inode supply is.) If this slows
15648 you down or takes up very much space, consider switching to
15649 @uref{http://www.namesys.com/, ReiserFS} or another non-block-structured
15652 Since maildirs don't require locking for delivery, the maildirs you use
15653 as groups can also be the maildirs your mail is directly delivered to.
15654 This means you can skip Gnus' mail splitting if your mail is already
15655 organized into different mailboxes during delivery. A @code{directory}
15656 entry in @code{mail-sources} would have a similar effect, but would
15657 require one set of mailboxes for spooling deliveries (in mbox format,
15658 thus damaging message bodies), and another set to be used as groups (in
15659 whatever format you like). A maildir has a built-in spool, in the
15660 @code{new/} subdirectory. Beware that currently, mail moved from
15661 @code{new/} to @code{cur/} instead of via mail splitting will not
15662 undergo treatment such as duplicate checking.
15664 @code{nnmaildir} stores article marks for a given group in the
15665 corresponding maildir, in a way designed so that it's easy to manipulate
15666 them from outside Gnus. You can tar up a maildir, unpack it somewhere
15667 else, and still have your marks. @code{nnml} also stores marks, but
15668 it's not as easy to work with them from outside Gnus as with
15671 @code{nnmaildir} uses a significant amount of memory to speed things up.
15672 (It keeps in memory some of the things that @code{nnml} stores in files
15673 and that @code{nnmh} repeatedly parses out of message files.) If this
15674 is a problem for you, you can set the @code{nov-cache-size} group
15675 parameter to something small (0 would probably not work, but 1 probably
15676 would) to make it use less memory. This caching will probably be
15677 removed in the future.
15679 Startup is likely to be slower with @code{nnmaildir} than with other
15680 back ends. Everything else is likely to be faster, depending in part
15681 on your file system.
15683 @code{nnmaildir} does not use @code{nnoo}, so you cannot use @code{nnoo}
15684 to write an @code{nnmaildir}-derived back end.
15689 @node Browsing the Web
15690 @section Browsing the Web
15692 @cindex browsing the web
15696 Web-based discussion forums are getting more and more popular. On many
15697 subjects, the web-based forums have become the most important forums,
15698 eclipsing the importance of mailing lists and news groups. The reason
15699 is easy to understand---they are friendly to new users; you just point
15700 and click, and there's the discussion. With mailing lists, you have to
15701 go through a cumbersome subscription procedure, and most people don't
15702 even know what a news group is.
15704 The problem with this scenario is that web browsers are not very good at
15705 being newsreaders. They do not keep track of what articles you've read;
15706 they do not allow you to score on subjects you're interested in; they do
15707 not allow off-line browsing; they require you to click around and drive
15708 you mad in the end.
15710 So---if web browsers suck at reading discussion forums, why not use Gnus
15713 Gnus has been getting a bit of a collection of back ends for providing
15714 interfaces to these sources.
15718 * Web Searches:: Creating groups from articles that match a string.
15719 * Slashdot:: Reading the Slashdot comments.
15720 * Ultimate:: The Ultimate Bulletin Board systems.
15721 * Web Archive:: Reading mailing list archived on web.
15722 * RSS:: Reading RDF site summary.
15723 * Customizing w3:: Doing stuff to Emacs/w3 from Gnus.
15726 All the web sources require Emacs/w3 and the url library to work.
15728 The main caveat with all these web sources is that they probably won't
15729 work for a very long time. Gleaning information from the @acronym{HTML} data
15730 is guesswork at best, and when the layout is altered, the Gnus back end
15731 will fail. If you have reasonably new versions of these back ends,
15732 though, you should be ok.
15734 One thing all these Web methods have in common is that the Web sources
15735 are often down, unavailable or just plain too slow to be fun. In those
15736 cases, it makes a lot of sense to let the Gnus Agent (@pxref{Gnus
15737 Unplugged}) handle downloading articles, and then you can read them at
15738 leisure from your local disk. No more World Wide Wait for you.
15740 @node Archiving Mail
15741 @subsection Archiving Mail
15742 @cindex archiving mail
15743 @cindex backup of mail
15745 Some of the back ends, notably @code{nnml}, @code{nnfolder}, and
15746 @code{nnmaildir}, now actually store the article marks with each group.
15747 For these servers, archiving and restoring a group while preserving
15748 marks is fairly simple.
15750 (Preserving the group level and group parameters as well still
15751 requires ritual dancing and sacrifices to the @file{.newsrc.eld} deity
15754 To archive an entire @code{nnml}, @code{nnfolder}, or @code{nnmaildir}
15755 server, take a recursive copy of the server directory. There is no need
15756 to shut down Gnus, so archiving may be invoked by @code{cron} or
15757 similar. You restore the data by restoring the directory tree, and
15758 adding a server definition pointing to that directory in Gnus. The
15759 @ref{Article Backlog}, @ref{Asynchronous Fetching} and other things
15760 might interfere with overwriting data, so you may want to shut down Gnus
15761 before you restore the data.
15763 It is also possible to archive individual @code{nnml},
15764 @code{nnfolder}, or @code{nnmaildir} groups, while preserving marks.
15765 For @code{nnml} or @code{nnmaildir}, you copy all files in the group's
15766 directory. For @code{nnfolder} you need to copy both the base folder
15767 file itself (@file{FOO}, say), and the marks file (@file{FOO.mrk} in
15768 this example). Restoring the group is done with @kbd{G m} from the Group
15769 buffer. The last step makes Gnus notice the new directory.
15770 @code{nnmaildir} notices the new directory automatically, so @kbd{G m}
15771 is unnecessary in that case.
15774 @subsection Web Searches
15779 @cindex Usenet searches
15780 @cindex searching the Usenet
15782 It's, like, too neat to search the Usenet for articles that match a
15783 string, but it, like, totally @emph{sucks}, like, totally, to use one of
15784 those, like, Web browsers, and you, like, have to, rilly, like, look at
15785 the commercials, so, like, with Gnus you can do @emph{rad}, rilly,
15786 searches without having to use a browser.
15788 The @code{nnweb} back end allows an easy interface to the mighty search
15789 engine. You create an @code{nnweb} group, enter a search pattern, and
15790 then enter the group and read the articles like you would any normal
15791 group. The @kbd{G w} command in the group buffer (@pxref{Foreign
15792 Groups}) will do this in an easy-to-use fashion.
15794 @code{nnweb} groups don't really lend themselves to being solid
15795 groups---they have a very fleeting idea of article numbers. In fact,
15796 each time you enter an @code{nnweb} group (not even changing the search
15797 pattern), you are likely to get the articles ordered in a different
15798 manner. Not even using duplicate suppression (@pxref{Duplicate
15799 Suppression}) will help, since @code{nnweb} doesn't even know the
15800 @code{Message-ID} of the articles before reading them using some search
15801 engines (Google, for instance). The only possible way to keep track
15802 of which articles you've read is by scoring on the @code{Date}
15803 header---mark all articles posted before the last date you read the
15806 If the search engine changes its output substantially, @code{nnweb}
15807 won't be able to parse it and will fail. One could hardly fault the Web
15808 providers if they were to do this---their @emph{raison d'@^etre} is to
15809 make money off of advertisements, not to provide services to the
15810 community. Since @code{nnweb} washes the ads off all the articles, one
15811 might think that the providers might be somewhat miffed. We'll see.
15813 You must have the @code{url} and @code{w3} package installed to be able
15814 to use @code{nnweb}.
15816 Virtual server variables:
15821 What search engine type is being used. The currently supported types
15822 are @code{google}, @code{dejanews}, and @code{gmane}. Note that
15823 @code{dejanews} is an alias to @code{google}.
15826 @vindex nnweb-search
15827 The search string to feed to the search engine.
15829 @item nnweb-max-hits
15830 @vindex nnweb-max-hits
15831 Advisory maximum number of hits per search to display. The default is
15834 @item nnweb-type-definition
15835 @vindex nnweb-type-definition
15836 Type-to-definition alist. This alist says what @code{nnweb} should do
15837 with the various search engine types. The following elements must be
15842 Function to decode the article and provide something that Gnus
15846 Function to create an article number to message header and URL alist.
15849 Function to send the search string to the search engine.
15852 The address the aforementioned function should send the search string
15856 Format string URL to fetch an article by @code{Message-ID}.
15863 @subsection Slashdot
15867 @uref{http://slashdot.org/, Slashdot} is a popular news site, with
15868 lively discussion following the news articles. @code{nnslashdot} will
15869 let you read this forum in a convenient manner.
15871 The easiest way to read this source is to put something like the
15872 following in your @file{~/.gnus.el} file:
15875 (setq gnus-secondary-select-methods
15876 '((nnslashdot "")))
15879 This will make Gnus query the @code{nnslashdot} back end for new comments
15880 and groups. The @kbd{F} command will subscribe each new news article as
15881 a new Gnus group, and you can read the comments by entering these
15882 groups. (Note that the default subscription method is to subscribe new
15883 groups as zombies. Other methods are available (@pxref{Subscription
15886 If you want to remove an old @code{nnslashdot} group, the @kbd{G DEL}
15887 command is the most handy tool (@pxref{Foreign Groups}).
15889 When following up to @code{nnslashdot} comments (or posting new
15890 comments), some light @acronym{HTML}izations will be performed. In
15891 particular, text quoted with @samp{> } will be quoted with
15892 @samp{blockquote} instead, and signatures will have @samp{br} added to
15893 the end of each line. Other than that, you can just write @acronym{HTML}
15894 directly into the message buffer. Note that Slashdot filters out some
15895 @acronym{HTML} forms.
15897 The following variables can be altered to change its behavior:
15900 @item nnslashdot-threaded
15901 Whether @code{nnslashdot} should display threaded groups or not. The
15902 default is @code{t}. To be able to display threads, @code{nnslashdot}
15903 has to retrieve absolutely all comments in a group upon entry. If a
15904 threaded display is not required, @code{nnslashdot} will only retrieve
15905 the comments that are actually wanted by the user. Threading is nicer,
15906 but much, much slower than unthreaded.
15908 @item nnslashdot-login-name
15909 @vindex nnslashdot-login-name
15910 The login name to use when posting.
15912 @item nnslashdot-password
15913 @vindex nnslashdot-password
15914 The password to use when posting.
15916 @item nnslashdot-directory
15917 @vindex nnslashdot-directory
15918 Where @code{nnslashdot} will store its files. The default is
15919 @file{~/News/slashdot/}.
15921 @item nnslashdot-active-url
15922 @vindex nnslashdot-active-url
15923 The @acronym{URL} format string that will be used to fetch the
15924 information on news articles and comments. The default is@*
15925 @samp{http://slashdot.org/search.pl?section=&min=%d}.
15927 @item nnslashdot-comments-url
15928 @vindex nnslashdot-comments-url
15929 The @acronym{URL} format string that will be used to fetch comments.
15931 @item nnslashdot-article-url
15932 @vindex nnslashdot-article-url
15933 The @acronym{URL} format string that will be used to fetch the news
15934 article. The default is
15935 @samp{http://slashdot.org/article.pl?sid=%s&mode=nocomment}.
15937 @item nnslashdot-threshold
15938 @vindex nnslashdot-threshold
15939 The score threshold. The default is -1.
15941 @item nnslashdot-group-number
15942 @vindex nnslashdot-group-number
15943 The number of old groups, in addition to the ten latest, to keep
15944 updated. The default is 0.
15951 @subsection Ultimate
15953 @cindex Ultimate Bulletin Board
15955 @uref{http://www.ultimatebb.com/, The Ultimate Bulletin Board} is
15956 probably the most popular Web bulletin board system used. It has a
15957 quite regular and nice interface, and it's possible to get the
15958 information Gnus needs to keep groups updated.
15960 The easiest way to get started with @code{nnultimate} is to say
15961 something like the following in the group buffer: @kbd{B nnultimate RET
15962 http://www.tcj.com/messboard/ubbcgi/ RET}. (Substitute the @acronym{URL}
15963 (not including @samp{Ultimate.cgi} or the like at the end) for a forum
15964 you're interested in; there's quite a list of them on the Ultimate web
15965 site.) Then subscribe to the groups you're interested in from the
15966 server buffer, and read them from the group buffer.
15968 The following @code{nnultimate} variables can be altered:
15971 @item nnultimate-directory
15972 @vindex nnultimate-directory
15973 The directory where @code{nnultimate} stores its files. The default is@*
15974 @file{~/News/ultimate/}.
15979 @subsection Web Archive
15981 @cindex Web Archive
15983 Some mailing lists only have archives on Web servers, such as
15984 @uref{http://www.egroups.com/} and
15985 @uref{http://www.mail-archive.com/}. It has a quite regular and nice
15986 interface, and it's possible to get the information Gnus needs to keep
15989 @findex gnus-group-make-warchive-group
15990 The easiest way to get started with @code{nnwarchive} is to say
15991 something like the following in the group buffer: @kbd{M-x
15992 gnus-group-make-warchive-group RET @var{an_egroup} RET egroups RET
15993 www.egroups.com RET @var{your@@email.address} RET}. (Substitute the
15994 @var{an_egroup} with the mailing list you subscribed, the
15995 @var{your@@email.address} with your email address.), or to browse the
15996 back end by @kbd{B nnwarchive RET mail-archive RET}.
15998 The following @code{nnwarchive} variables can be altered:
16001 @item nnwarchive-directory
16002 @vindex nnwarchive-directory
16003 The directory where @code{nnwarchive} stores its files. The default is@*
16004 @file{~/News/warchive/}.
16006 @item nnwarchive-login
16007 @vindex nnwarchive-login
16008 The account name on the web server.
16010 @item nnwarchive-passwd
16011 @vindex nnwarchive-passwd
16012 The password for your account on the web server.
16020 Some web sites have an RDF Site Summary (@acronym{RSS}).
16021 @acronym{RSS} is a format for summarizing headlines from news related
16022 sites (such as BBC or CNN). But basically anything list-like can be
16023 presented as an @acronym{RSS} feed: weblogs, changelogs or recent
16024 changes to a wiki (e.g. @url{http://cliki.net/recent-changes.rdf}).
16026 @acronym{RSS} has a quite regular and nice interface, and it's
16027 possible to get the information Gnus needs to keep groups updated.
16029 Note: you had better use Emacs which supports the @code{utf-8} coding
16030 system because @acronym{RSS} uses UTF-8 for encoding non-@acronym{ASCII}
16031 text by default. It is also used by default for non-@acronym{ASCII}
16034 @kindex G R (Summary)
16035 Use @kbd{G R} from the summary buffer to subscribe to a feed---you will
16036 be prompted for the location, the title and the description of the feed.
16037 The title, which allows any characters, will be used for the group name
16038 and the name of the group data file. The description can be omitted.
16040 An easy way to get started with @code{nnrss} is to say something like
16041 the following in the group buffer: @kbd{B nnrss RET RET y}, then
16042 subscribe to groups.
16044 The @code{nnrss} back end saves the group data file in
16045 @code{nnrss-directory} (see below) for each @code{nnrss} group. File
16046 names containing non-@acronym{ASCII} characters will be encoded by the
16047 coding system specified with the @code{nnmail-pathname-coding-system}
16048 variable. If it is @code{nil}, in Emacs the coding system defaults to
16049 the value of @code{default-file-name-coding-system}. If you are using
16050 XEmacs and want to use non-@acronym{ASCII} group names, you should set
16051 the value for the @code{nnmail-pathname-coding-system} variable properly.
16054 You can also use the following commands to import and export your
16055 subscriptions from a file in @acronym{OPML} format (Outline Processor
16058 @defun nnrss-opml-import file
16059 Prompt for an @acronym{OPML} file, and subscribe to each feed in the
16063 @defun nnrss-opml-export
16064 Write your current @acronym{RSS} subscriptions to a buffer in
16065 @acronym{OPML} format.
16068 The following @code{nnrss} variables can be altered:
16071 @item nnrss-directory
16072 @vindex nnrss-directory
16073 The directory where @code{nnrss} stores its files. The default is
16074 @file{~/News/rss/}.
16076 @item nnrss-file-coding-system
16077 @vindex nnrss-file-coding-system
16078 The coding system used when reading and writing the @code{nnrss} groups
16079 data files. The default is the value of
16080 @code{mm-universal-coding-system} (which defaults to @code{emacs-mule}
16081 in Emacs or @code{escape-quoted} in XEmacs).
16083 @item nnrss-use-local
16084 @vindex nnrss-use-local
16085 @findex nnrss-generate-download-script
16086 If you set @code{nnrss-use-local} to @code{t}, @code{nnrss} will read
16087 the feeds from local files in @code{nnrss-directory}. You can use
16088 the command @code{nnrss-generate-download-script} to generate a
16089 download script using @command{wget}.
16092 The following code may be helpful, if you want to show the description in
16093 the summary buffer.
16096 (add-to-list 'nnmail-extra-headers nnrss-description-field)
16097 (setq gnus-summary-line-format "%U%R%z%I%(%[%4L: %-15,15f%]%) %s%uX\n")
16099 (defun gnus-user-format-function-X (header)
16101 (assq nnrss-description-field (mail-header-extra header))))
16102 (if descr (concat "\n\t" (cdr descr)) "")))
16105 The following code may be useful to open an nnrss url directly from the
16108 (require 'browse-url)
16110 (defun browse-nnrss-url( arg )
16112 (let ((url (assq nnrss-url-field
16115 (assq (gnus-summary-article-number)
16116 gnus-newsgroup-data))))))
16119 (browse-url (cdr url))
16120 (gnus-summary-mark-as-read-forward 1))
16121 (gnus-summary-scroll-up arg))))
16123 (eval-after-load "gnus"
16124 #'(define-key gnus-summary-mode-map
16125 (kbd "<RET>") 'browse-nnrss-url))
16126 (add-to-list 'nnmail-extra-headers nnrss-url-field)
16129 @node Customizing w3
16130 @subsection Customizing w3
16136 Gnus uses the url library to fetch web pages and Emacs/w3 to display web
16137 pages. Emacs/w3 is documented in its own manual, but there are some
16138 things that may be more relevant for Gnus users.
16140 For instance, a common question is how to make Emacs/w3 follow links
16141 using the @code{browse-url} functions (which will call some external web
16142 browser like Netscape). Here's one way:
16145 (eval-after-load "w3"
16147 (fset 'w3-fetch-orig (symbol-function 'w3-fetch))
16148 (defun w3-fetch (&optional url target)
16149 (interactive (list (w3-read-url-with-default)))
16150 (if (eq major-mode 'gnus-article-mode)
16152 (w3-fetch-orig url target)))))
16155 Put that in your @file{.emacs} file, and hitting links in w3-rendered
16156 @acronym{HTML} in the Gnus article buffers will use @code{browse-url} to
16163 @cindex @acronym{IMAP}
16165 @acronym{IMAP} is a network protocol for reading mail (or news, or @dots{}),
16166 think of it as a modernized @acronym{NNTP}. Connecting to a @acronym{IMAP}
16167 server is much similar to connecting to a news server, you just
16168 specify the network address of the server.
16170 @acronym{IMAP} has two properties. First, @acronym{IMAP} can do
16171 everything that @acronym{POP} can, it can hence be viewed as a
16172 @acronym{POP++}. Secondly, @acronym{IMAP} is a mail storage protocol,
16173 similar to @acronym{NNTP} being a news storage protocol---however,
16174 @acronym{IMAP} offers more features than @acronym{NNTP} because news
16175 is more or less read-only whereas mail is read-write.
16177 If you want to use @acronym{IMAP} as a @acronym{POP++}, use an imap
16178 entry in @code{mail-sources}. With this, Gnus will fetch mails from
16179 the @acronym{IMAP} server and store them on the local disk. This is
16180 not the usage described in this section---@xref{Mail Sources}.
16182 If you want to use @acronym{IMAP} as a mail storage protocol, use an nnimap
16183 entry in @code{gnus-secondary-select-methods}. With this, Gnus will
16184 manipulate mails stored on the @acronym{IMAP} server. This is the kind of
16185 usage explained in this section.
16187 A server configuration in @file{~/.gnus.el} with a few @acronym{IMAP}
16188 servers might look something like the following. (Note that for
16189 @acronym{TLS}/@acronym{SSL}, you need external programs and libraries,
16193 (setq gnus-secondary-select-methods
16194 '((nnimap "simpleserver") ; @r{no special configuration}
16195 ; @r{perhaps a ssh port forwarded server:}
16197 (nnimap-address "localhost")
16198 (nnimap-server-port 1430))
16199 ; @r{a UW server running on localhost}
16201 (nnimap-server-port 143)
16202 (nnimap-address "localhost")
16203 (nnimap-list-pattern ("INBOX" "mail/*")))
16204 ; @r{anonymous public cyrus server:}
16205 (nnimap "cyrus.andrew.cmu.edu"
16206 (nnimap-authenticator anonymous)
16207 (nnimap-list-pattern "archive.*")
16208 (nnimap-stream network))
16209 ; @r{a ssl server on a non-standard port:}
16211 (nnimap-address "vic20.somewhere.com")
16212 (nnimap-server-port 9930)
16213 (nnimap-stream ssl))))
16216 After defining the new server, you can subscribe to groups on the
16217 server using normal Gnus commands such as @kbd{U} in the Group Buffer
16218 (@pxref{Subscription Commands}) or via the Server Buffer
16219 (@pxref{Server Buffer}).
16221 The following variables can be used to create a virtual @code{nnimap}
16226 @item nnimap-address
16227 @vindex nnimap-address
16229 The address of the remote @acronym{IMAP} server. Defaults to the virtual
16230 server name if not specified.
16232 @item nnimap-server-port
16233 @vindex nnimap-server-port
16234 Port on server to contact. Defaults to port 143, or 993 for @acronym{TLS}/@acronym{SSL}.
16236 Note that this should be an integer, example server specification:
16239 (nnimap "mail.server.com"
16240 (nnimap-server-port 4711))
16243 @item nnimap-list-pattern
16244 @vindex nnimap-list-pattern
16245 String or list of strings of mailboxes to limit available groups to.
16246 This is used when the server has very many mailboxes and you're only
16247 interested in a few---some servers export your home directory via
16248 @acronym{IMAP}, you'll probably want to limit the mailboxes to those in
16249 @file{~/Mail/*} then.
16251 The string can also be a cons of REFERENCE and the string as above, what
16252 REFERENCE is used for is server specific, but on the University of
16253 Washington server it's a directory that will be concatenated with the
16256 Example server specification:
16259 (nnimap "mail.server.com"
16260 (nnimap-list-pattern ("INBOX" "Mail/*" "alt.sex.*"
16261 ("~friend/Mail/" . "list/*"))))
16264 @item nnimap-stream
16265 @vindex nnimap-stream
16266 The type of stream used to connect to your server. By default, nnimap
16267 will detect and automatically use all of the below, with the exception
16268 of @acronym{TLS}/@acronym{SSL}. (@acronym{IMAP} over
16269 @acronym{TLS}/@acronym{SSL} is being replaced by STARTTLS, which can
16270 be automatically detected, but it's not widely deployed yet.)
16272 Example server specification:
16275 (nnimap "mail.server.com"
16276 (nnimap-stream ssl))
16279 Please note that the value of @code{nnimap-stream} is a symbol!
16283 @dfn{gssapi:} Connect with GSSAPI (usually Kerberos 5). Requires the
16284 @samp{gsasl} or @samp{imtest} program.
16286 @dfn{kerberos4:} Connect with Kerberos 4. Requires the @samp{imtest} program.
16288 @dfn{starttls:} Connect via the STARTTLS extension (similar to
16289 @acronym{TLS}/@acronym{SSL}). Requires the external library @samp{starttls.el} and program
16292 @dfn{tls:} Connect through @acronym{TLS}. Requires GNUTLS (the program
16293 @samp{gnutls-cli}).
16295 @dfn{ssl:} Connect through @acronym{SSL}. Requires OpenSSL (the program
16296 @samp{openssl}) or SSLeay (@samp{s_client}).
16298 @dfn{shell:} Use a shell command to start @acronym{IMAP} connection.
16300 @dfn{network:} Plain, TCP/IP network connection.
16303 @vindex imap-kerberos4-program
16304 The @samp{imtest} program is shipped with Cyrus IMAPD. If you're
16305 using @samp{imtest} from Cyrus IMAPD < 2.0.14 (which includes version
16306 1.5.x and 1.6.x) you need to frob @code{imap-process-connection-type}
16307 to make @code{imap.el} use a pty instead of a pipe when communicating
16308 with @samp{imtest}. You will then suffer from a line length
16309 restrictions on @acronym{IMAP} commands, which might make Gnus seem to hang
16310 indefinitely if you have many articles in a mailbox. The variable
16311 @code{imap-kerberos4-program} contain parameters to pass to the imtest
16314 For @acronym{TLS} connection, the @code{gnutls-cli} program from GNUTLS is
16315 needed. It is available from
16316 @uref{http://www.gnu.org/software/gnutls/}.
16318 @vindex imap-gssapi-program
16319 This parameter specifies a list of command lines that invoke a GSSAPI
16320 authenticated @acronym{IMAP} stream in a subshell. They are tried
16321 sequentially until a connection is made, or the list has been
16322 exhausted. By default, @samp{gsasl} from GNU SASL, available from
16323 @uref{http://www.gnu.org/software/gsasl/}, and the @samp{imtest}
16324 program from Cyrus IMAPD (see @code{imap-kerberos4-program}), are
16327 @vindex imap-ssl-program
16328 For @acronym{SSL} connections, the OpenSSL program is available from
16329 @uref{http://www.openssl.org/}. OpenSSL was formerly known as SSLeay,
16330 and nnimap support it too---although the most recent versions of
16331 SSLeay, 0.9.x, are known to have serious bugs making it
16332 useless. Earlier versions, especially 0.8.x, of SSLeay are known to
16333 work. The variable @code{imap-ssl-program} contain parameters to pass
16336 @vindex imap-shell-program
16337 @vindex imap-shell-host
16338 For @acronym{IMAP} connections using the @code{shell} stream, the variable
16339 @code{imap-shell-program} specify what program to call.
16341 @item nnimap-authenticator
16342 @vindex nnimap-authenticator
16344 The authenticator used to connect to the server. By default, nnimap
16345 will use the most secure authenticator your server is capable of.
16347 Example server specification:
16350 (nnimap "mail.server.com"
16351 (nnimap-authenticator anonymous))
16354 Please note that the value of @code{nnimap-authenticator} is a symbol!
16358 @dfn{gssapi:} GSSAPI (usually kerberos 5) authentication. Requires
16359 external program @code{gsasl} or @code{imtest}.
16361 @dfn{kerberos4:} Kerberos 4 authentication. Requires external program
16364 @dfn{digest-md5:} Encrypted username/password via DIGEST-MD5. Requires
16365 external library @code{digest-md5.el}.
16367 @dfn{cram-md5:} Encrypted username/password via CRAM-MD5.
16369 @dfn{login:} Plain-text username/password via LOGIN.
16371 @dfn{anonymous:} Login as ``anonymous'', supplying your email address as password.
16374 @item nnimap-expunge-on-close
16376 @vindex nnimap-expunge-on-close
16377 Unlike Parmenides the @acronym{IMAP} designers have decided things that
16378 don't exist actually do exist. More specifically, @acronym{IMAP} has
16379 this concept of marking articles @code{Deleted} which doesn't actually
16380 delete them, and this (marking them @code{Deleted}, that is) is what
16381 nnimap does when you delete an article in Gnus (with @kbd{B DEL} or
16384 Since the articles aren't really removed when we mark them with the
16385 @code{Deleted} flag we'll need a way to actually delete them. Feel like
16386 running in circles yet?
16388 Traditionally, nnimap has removed all articles marked as @code{Deleted}
16389 when closing a mailbox but this is now configurable by this server
16392 The possible options are:
16397 The default behavior, delete all articles marked as ``Deleted'' when
16400 Never actually delete articles. Currently there is no way of showing
16401 the articles marked for deletion in nnimap, but other @acronym{IMAP} clients
16402 may allow you to do this. If you ever want to run the EXPUNGE command
16403 manually, @xref{Expunging mailboxes}.
16405 When closing mailboxes, nnimap will ask if you wish to expunge deleted
16410 @item nnimap-importantize-dormant
16411 @vindex nnimap-importantize-dormant
16413 If non-@code{nil} (the default), marks dormant articles as ticked (as
16414 well), for other @acronym{IMAP} clients. Within Gnus, dormant articles will
16415 naturally still (only) be marked as dormant. This is to make dormant
16416 articles stand out, just like ticked articles, in other @acronym{IMAP}
16417 clients. (In other words, Gnus has two ``Tick'' marks and @acronym{IMAP}
16420 Probably the only reason for frobing this would be if you're trying
16421 enable per-user persistent dormant flags, using something like:
16424 (setcdr (assq 'dormant nnimap-mark-to-flag-alist)
16425 (format "gnus-dormant-%s" (user-login-name)))
16426 (setcdr (assq 'dormant nnimap-mark-to-predicate-alist)
16427 (format "KEYWORD gnus-dormant-%s" (user-login-name)))
16430 In this case, you would not want the per-user dormant flag showing up
16431 as ticked for other users.
16433 @item nnimap-expunge-search-string
16435 @vindex nnimap-expunge-search-string
16437 This variable contain the @acronym{IMAP} search command sent to server when
16438 searching for articles eligible for expiring. The default is
16439 @code{"UID %s NOT SINCE %s"}, where the first @code{%s} is replaced by
16440 UID set and the second @code{%s} is replaced by a date.
16442 Probably the only useful value to change this to is
16443 @code{"UID %s NOT SENTSINCE %s"}, which makes nnimap use the Date: in
16444 messages instead of the internal article date. See section 6.4.4 of
16445 RFC 2060 for more information on valid strings.
16447 @item nnimap-authinfo-file
16448 @vindex nnimap-authinfo-file
16450 A file containing credentials used to log in on servers. The format is
16451 (almost) the same as the @code{ftp} @file{~/.netrc} file. See the
16452 variable @code{nntp-authinfo-file} for exact syntax; also see
16453 @ref{NNTP}. An example of an .authinfo line for an IMAP server, is:
16456 machine students.uio.no login larsi password geheimnis port imap
16459 Note that it should be @code{port imap}, or @code{port 143}, if you
16460 use a @code{nnimap-stream} of @code{tls} or @code{ssl}, even if the
16461 actual port number used is port 993 for secured IMAP. For
16462 convenience, Gnus will accept @code{port imaps} as a synonym of
16465 @item nnimap-need-unselect-to-notice-new-mail
16466 @vindex nnimap-need-unselect-to-notice-new-mail
16468 Unselect mailboxes before looking for new mail in them. Some servers
16469 seem to need this under some circumstances; it was reported that
16475 * Splitting in IMAP:: Splitting mail with nnimap.
16476 * Expiring in IMAP:: Expiring mail with nnimap.
16477 * Editing IMAP ACLs:: Limiting/enabling other users access to a mailbox.
16478 * Expunging mailboxes:: Equivalent of a ``compress mailbox'' button.
16479 * A note on namespaces:: How to (not) use @acronym{IMAP} namespace in Gnus.
16480 * Debugging IMAP:: What to do when things don't work.
16485 @node Splitting in IMAP
16486 @subsection Splitting in IMAP
16487 @cindex splitting imap mail
16489 Splitting is something Gnus users have loved and used for years, and now
16490 the rest of the world is catching up. Yeah, dream on, not many
16491 @acronym{IMAP} servers have server side splitting and those that have
16492 splitting seem to use some non-standard protocol. This means that
16493 @acronym{IMAP} support for Gnus has to do its own splitting.
16497 (Incidentally, people seem to have been dreaming on, and Sieve has
16498 gaining a market share and is supported by several IMAP servers.
16499 Fortunately, Gnus support it too, @xref{Sieve Commands}.)
16501 Here are the variables of interest:
16505 @item nnimap-split-crosspost
16506 @cindex splitting, crosspost
16508 @vindex nnimap-split-crosspost
16510 If non-@code{nil}, do crossposting if several split methods match the
16511 mail. If @code{nil}, the first match in @code{nnimap-split-rule}
16512 found will be used.
16514 Nnmail equivalent: @code{nnmail-crosspost}.
16516 @item nnimap-split-inbox
16517 @cindex splitting, inbox
16519 @vindex nnimap-split-inbox
16521 A string or a list of strings that gives the name(s) of @acronym{IMAP}
16522 mailboxes to split from. Defaults to @code{nil}, which means that
16523 splitting is disabled!
16526 (setq nnimap-split-inbox
16527 '("INBOX" ("~/friend/Mail" . "lists/*") "lists.imap"))
16530 No nnmail equivalent.
16532 @item nnimap-split-rule
16533 @cindex splitting, rules
16534 @vindex nnimap-split-rule
16536 New mail found in @code{nnimap-split-inbox} will be split according to
16539 This variable contains a list of lists, where the first element in the
16540 sublist gives the name of the @acronym{IMAP} mailbox to move articles
16541 matching the regexp in the second element in the sublist. Got that?
16542 Neither did I, we need examples.
16545 (setq nnimap-split-rule
16547 "^Sender: owner-nnimap@@vic20.globalcom.se")
16548 ("INBOX.junk" "^Subject:.*MAKE MONEY")
16549 ("INBOX.private" "")))
16552 This will put all articles from the nnimap mailing list into mailbox
16553 INBOX.nnimap, all articles containing MAKE MONEY in the Subject: line
16554 into INBOX.junk and everything else in INBOX.private.
16556 The first string may contain @samp{\\1} forms, like the ones used by
16557 replace-match to insert sub-expressions from the matched text. For
16561 ("INBOX.lists.\\1" "^Sender: owner-\\([a-z-]+\\)@@")
16564 The first element can also be the symbol @code{junk} to indicate that
16565 matching messages should simply be deleted. Use with care.
16567 The second element can also be a function. In that case, it will be
16568 called with the first element of the rule as the argument, in a buffer
16569 containing the headers of the article. It should return a
16570 non-@code{nil} value if it thinks that the mail belongs in that group.
16572 Nnmail users might recollect that the last regexp had to be empty to
16573 match all articles (like in the example above). This is not required in
16574 nnimap. Articles not matching any of the regexps will not be moved out
16575 of your inbox. (This might affect performance if you keep lots of
16576 unread articles in your inbox, since the splitting code would go over
16577 them every time you fetch new mail.)
16579 These rules are processed from the beginning of the alist toward the
16580 end. The first rule to make a match will ``win'', unless you have
16581 crossposting enabled. In that case, all matching rules will ``win''.
16583 This variable can also have a function as its value, the function will
16584 be called with the headers narrowed and should return a group where it
16585 thinks the article should be split to. See @code{nnimap-split-fancy}.
16587 The splitting code tries to create mailboxes if it needs to.
16589 To allow for different split rules on different virtual servers, and
16590 even different split rules in different inboxes on the same server,
16591 the syntax of this variable have been extended along the lines of:
16594 (setq nnimap-split-rule
16595 '(("my1server" (".*" (("ding" "ding@@gnus.org")
16596 ("junk" "From:.*Simon"))))
16597 ("my2server" ("INBOX" nnimap-split-fancy))
16598 ("my[34]server" (".*" (("private" "To:.*Simon")
16599 ("junk" my-junk-func))))))
16602 The virtual server name is in fact a regexp, so that the same rules
16603 may apply to several servers. In the example, the servers
16604 @code{my3server} and @code{my4server} both use the same rules.
16605 Similarly, the inbox string is also a regexp. The actual splitting
16606 rules are as before, either a function, or a list with group/regexp or
16607 group/function elements.
16609 Nnmail equivalent: @code{nnmail-split-methods}.
16611 @item nnimap-split-predicate
16613 @vindex nnimap-split-predicate
16615 Mail matching this predicate in @code{nnimap-split-inbox} will be
16616 split, it is a string and the default is @samp{UNSEEN UNDELETED}.
16618 This might be useful if you use another @acronym{IMAP} client to read mail in
16619 your inbox but would like Gnus to split all articles in the inbox
16620 regardless of readedness. Then you might change this to
16623 @item nnimap-split-fancy
16624 @cindex splitting, fancy
16625 @findex nnimap-split-fancy
16626 @vindex nnimap-split-fancy
16628 It's possible to set @code{nnimap-split-rule} to
16629 @code{nnmail-split-fancy} if you want to use fancy
16630 splitting. @xref{Fancy Mail Splitting}.
16632 However, to be able to have different fancy split rules for nnmail and
16633 nnimap back ends you can set @code{nnimap-split-rule} to
16634 @code{nnimap-split-fancy} and define the nnimap specific fancy split
16635 rule in @code{nnimap-split-fancy}.
16640 (setq nnimap-split-rule 'nnimap-split-fancy
16641 nnimap-split-fancy ...)
16644 Nnmail equivalent: @code{nnmail-split-fancy}.
16646 @item nnimap-split-download-body
16647 @findex nnimap-split-download-body
16648 @vindex nnimap-split-download-body
16650 Set to non-@code{nil} to download entire articles during splitting.
16651 This is generally not required, and will slow things down
16652 considerably. You may need it if you want to use an advanced
16653 splitting function that analyses the body to split the article.
16657 @node Expiring in IMAP
16658 @subsection Expiring in IMAP
16659 @cindex expiring imap mail
16661 Even though @code{nnimap} is not a proper @code{nnmail} derived back
16662 end, it supports most features in regular expiring (@pxref{Expiring
16663 Mail}). Unlike splitting in @acronym{IMAP} (@pxref{Splitting in
16664 IMAP}) it does not clone the @code{nnmail} variables (i.e., creating
16665 @var{nnimap-expiry-wait}) but reuse the @code{nnmail} variables. What
16666 follows below are the variables used by the @code{nnimap} expiry
16669 A note on how the expire mark is stored on the @acronym{IMAP} server is
16670 appropriate here as well. The expire mark is translated into a
16671 @code{imap} client specific mark, @code{gnus-expire}, and stored on the
16672 message. This means that likely only Gnus will understand and treat
16673 the @code{gnus-expire} mark properly, although other clients may allow
16674 you to view client specific flags on the message. It also means that
16675 your server must support permanent storage of client specific flags on
16676 messages. Most do, fortunately.
16680 @item nnmail-expiry-wait
16681 @item nnmail-expiry-wait-function
16683 These variables are fully supported. The expire value can be a
16684 number, the symbol @code{immediate} or @code{never}.
16686 @item nnmail-expiry-target
16688 This variable is supported, and internally implemented by calling the
16689 @code{nnmail} functions that handle this. It contains an optimization
16690 that if the destination is a @acronym{IMAP} group on the same server, the
16691 article is copied instead of appended (that is, uploaded again).
16695 @node Editing IMAP ACLs
16696 @subsection Editing IMAP ACLs
16697 @cindex editing imap acls
16698 @cindex Access Control Lists
16699 @cindex Editing @acronym{IMAP} ACLs
16700 @kindex G l (Group)
16701 @findex gnus-group-nnimap-edit-acl
16703 ACL stands for Access Control List. ACLs are used in @acronym{IMAP} for
16704 limiting (or enabling) other users access to your mail boxes. Not all
16705 @acronym{IMAP} servers support this, this function will give an error if it
16708 To edit an ACL for a mailbox, type @kbd{G l}
16709 (@code{gnus-group-edit-nnimap-acl}) and you'll be presented with an ACL
16710 editing window with detailed instructions.
16712 Some possible uses:
16716 Giving ``anyone'' the ``lrs'' rights (lookup, read, keep seen/unseen flags)
16717 on your mailing list mailboxes enables other users on the same server to
16718 follow the list without subscribing to it.
16720 At least with the Cyrus server, you are required to give the user
16721 ``anyone'' posting ("p") capabilities to have ``plussing'' work (that is,
16722 mail sent to user+mailbox@@domain ending up in the @acronym{IMAP} mailbox
16726 @node Expunging mailboxes
16727 @subsection Expunging mailboxes
16731 @cindex manual expunging
16732 @kindex G x (Group)
16733 @findex gnus-group-nnimap-expunge
16735 If you're using the @code{never} setting of @code{nnimap-expunge-on-close},
16736 you may want the option of expunging all deleted articles in a mailbox
16737 manually. This is exactly what @kbd{G x} does.
16739 Currently there is no way of showing deleted articles, you can just
16742 @node A note on namespaces
16743 @subsection A note on namespaces
16744 @cindex IMAP namespace
16747 The @acronym{IMAP} protocol has a concept called namespaces, described
16748 by the following text in the RFC:
16751 5.1.2. Mailbox Namespace Naming Convention
16753 By convention, the first hierarchical element of any mailbox name
16754 which begins with "#" identifies the "namespace" of the remainder of
16755 the name. This makes it possible to disambiguate between different
16756 types of mailbox stores, each of which have their own namespaces.
16758 For example, implementations which offer access to USENET
16759 newsgroups MAY use the "#news" namespace to partition the USENET
16760 newsgroup namespace from that of other mailboxes. Thus, the
16761 comp.mail.misc newsgroup would have an mailbox name of
16762 "#news.comp.mail.misc", and the name "comp.mail.misc" could refer
16763 to a different object (e.g. a user's private mailbox).
16766 While there is nothing in this text that warrants concern for the
16767 @acronym{IMAP} implementation in Gnus, some servers use namespace
16768 prefixes in a way that does not work with how Gnus uses mailbox names.
16770 Specifically, University of Washington's @acronym{IMAP} server uses
16771 mailbox names like @code{#driver.mbx/read-mail} which are valid only
16772 in the @sc{create} and @sc{append} commands. After the mailbox is
16773 created (or a messages is appended to a mailbox), it must be accessed
16774 without the namespace prefix, i.e. @code{read-mail}. Since Gnus do
16775 not make it possible for the user to guarantee that user entered
16776 mailbox names will only be used with the CREATE and APPEND commands,
16777 you should simply not use the namespace prefixed mailbox names in
16780 See the UoW IMAPD documentation for the @code{#driver.*/} prefix
16781 for more information on how to use the prefixes. They are a power
16782 tool and should be used only if you are sure what the effects are.
16784 @node Debugging IMAP
16785 @subsection Debugging IMAP
16786 @cindex IMAP debugging
16787 @cindex protocol dump (IMAP)
16789 @acronym{IMAP} is a complex protocol, more so than @acronym{NNTP} or
16790 @acronym{POP3}. Implementation bugs are not unlikely, and we do our
16791 best to fix them right away. If you encounter odd behaviour, chances
16792 are that either the server or Gnus is buggy.
16794 If you are familiar with network protocols in general, you will
16795 probably be able to extract some clues from the protocol dump of the
16796 exchanges between Gnus and the server. Even if you are not familiar
16797 with network protocols, when you include the protocol dump in
16798 @acronym{IMAP}-related bug reports you are helping us with data
16799 critical to solving the problem. Therefore, we strongly encourage you
16800 to include the protocol dump when reporting IMAP bugs in Gnus.
16804 Because the protocol dump, when enabled, generates lots of data, it is
16805 disabled by default. You can enable it by setting @code{imap-log} as
16812 This instructs the @code{imap.el} package to log any exchanges with
16813 the server. The log is stored in the buffer @samp{*imap-log*}. Look
16814 for error messages, which sometimes are tagged with the keyword
16815 @code{BAD}---but when submitting a bug, make sure to include all the
16818 @node Other Sources
16819 @section Other Sources
16821 Gnus can do more than just read news or mail. The methods described
16822 below allow Gnus to view directories and files as if they were
16826 * Directory Groups:: You can read a directory as if it was a newsgroup.
16827 * Anything Groups:: Dired? Who needs dired?
16828 * Document Groups:: Single files can be the basis of a group.
16829 * SOUP:: Reading @sc{soup} packets ``offline''.
16830 * Mail-To-News Gateways:: Posting articles via mail-to-news gateways.
16834 @node Directory Groups
16835 @subsection Directory Groups
16837 @cindex directory groups
16839 If you have a directory that has lots of articles in separate files in
16840 it, you might treat it as a newsgroup. The files have to have numerical
16843 This might be an opportune moment to mention @code{ange-ftp} (and its
16844 successor @code{efs}), that most wonderful of all wonderful Emacs
16845 packages. When I wrote @code{nndir}, I didn't think much about it---a
16846 back end to read directories. Big deal.
16848 @code{ange-ftp} changes that picture dramatically. For instance, if you
16849 enter the @code{ange-ftp} file name
16850 @file{/ftp.hpc.uh.edu:/pub/emacs/ding-list/} as the directory name,
16851 @code{ange-ftp} or @code{efs} will actually allow you to read this
16852 directory over at @samp{sina} as a newsgroup. Distributed news ahoy!
16854 @code{nndir} will use @acronym{NOV} files if they are present.
16856 @code{nndir} is a ``read-only'' back end---you can't delete or expire
16857 articles with this method. You can use @code{nnmh} or @code{nnml} for
16858 whatever you use @code{nndir} for, so you could switch to any of those
16859 methods if you feel the need to have a non-read-only @code{nndir}.
16862 @node Anything Groups
16863 @subsection Anything Groups
16866 From the @code{nndir} back end (which reads a single spool-like
16867 directory), it's just a hop and a skip to @code{nneething}, which
16868 pretends that any arbitrary directory is a newsgroup. Strange, but
16871 When @code{nneething} is presented with a directory, it will scan this
16872 directory and assign article numbers to each file. When you enter such
16873 a group, @code{nneething} must create ``headers'' that Gnus can use.
16874 After all, Gnus is a newsreader, in case you're forgetting.
16875 @code{nneething} does this in a two-step process. First, it snoops each
16876 file in question. If the file looks like an article (i.e., the first
16877 few lines look like headers), it will use this as the head. If this is
16878 just some arbitrary file without a head (e.g. a C source file),
16879 @code{nneething} will cobble up a header out of thin air. It will use
16880 file ownership, name and date and do whatever it can with these
16883 All this should happen automatically for you, and you will be presented
16884 with something that looks very much like a newsgroup. Totally like a
16885 newsgroup, to be precise. If you select an article, it will be displayed
16886 in the article buffer, just as usual.
16888 If you select a line that represents a directory, Gnus will pop you into
16889 a new summary buffer for this @code{nneething} group. And so on. You can
16890 traverse the entire disk this way, if you feel like, but remember that
16891 Gnus is not dired, really, and does not intend to be, either.
16893 There are two overall modes to this action---ephemeral or solid. When
16894 doing the ephemeral thing (i.e., @kbd{G D} from the group buffer), Gnus
16895 will not store information on what files you have read, and what files
16896 are new, and so on. If you create a solid @code{nneething} group the
16897 normal way with @kbd{G m}, Gnus will store a mapping table between
16898 article numbers and file names, and you can treat this group like any
16899 other groups. When you activate a solid @code{nneething} group, you will
16900 be told how many unread articles it contains, etc., etc.
16905 @item nneething-map-file-directory
16906 @vindex nneething-map-file-directory
16907 All the mapping files for solid @code{nneething} groups will be stored
16908 in this directory, which defaults to @file{~/.nneething/}.
16910 @item nneething-exclude-files
16911 @vindex nneething-exclude-files
16912 All files that match this regexp will be ignored. Nice to use to exclude
16913 auto-save files and the like, which is what it does by default.
16915 @item nneething-include-files
16916 @vindex nneething-include-files
16917 Regexp saying what files to include in the group. If this variable is
16918 non-@code{nil}, only files matching this regexp will be included.
16920 @item nneething-map-file
16921 @vindex nneething-map-file
16922 Name of the map files.
16926 @node Document Groups
16927 @subsection Document Groups
16929 @cindex documentation group
16932 @code{nndoc} is a cute little thing that will let you read a single file
16933 as a newsgroup. Several files types are supported:
16940 The Babyl (Rmail) mail box.
16945 The standard Unix mbox file.
16947 @cindex MMDF mail box
16949 The MMDF mail box format.
16952 Several news articles appended into a file.
16955 @cindex rnews batch files
16956 The rnews batch transport format.
16957 @cindex forwarded messages
16960 Forwarded articles.
16963 Netscape mail boxes.
16966 @acronym{MIME} multipart messages.
16968 @item standard-digest
16969 The standard (RFC 1153) digest format.
16972 A @acronym{MIME} digest of messages.
16974 @item lanl-gov-announce
16975 Announcement messages from LANL Gov Announce.
16977 @item rfc822-forward
16978 A message forwarded according to RFC822.
16981 The Outlook mail box.
16984 The Outlook Express dbx mail box.
16987 A bounce message from the Exim MTA.
16990 A message forwarded according to informal rules.
16993 An RFC934-forwarded message.
16999 A digest of Clarinet brief news items.
17002 Non-standard digest format---matches most things, but does it badly.
17008 You can also use the special ``file type'' @code{guess}, which means
17009 that @code{nndoc} will try to guess what file type it is looking at.
17010 @code{digest} means that @code{nndoc} should guess what digest type the
17013 @code{nndoc} will not try to change the file or insert any extra headers into
17014 it---it will simply, like, let you use the file as the basis for a
17015 group. And that's it.
17017 If you have some old archived articles that you want to insert into your
17018 new & spiffy Gnus mail back end, @code{nndoc} can probably help you with
17019 that. Say you have an old @file{RMAIL} file with mail that you now want
17020 to split into your new @code{nnml} groups. You look at that file using
17021 @code{nndoc} (using the @kbd{G f} command in the group buffer
17022 (@pxref{Foreign Groups})), set the process mark on all the articles in
17023 the buffer (@kbd{M P b}, for instance), and then re-spool (@kbd{B r})
17024 using @code{nnml}. If all goes well, all the mail in the @file{RMAIL}
17025 file is now also stored in lots of @code{nnml} directories, and you can
17026 delete that pesky @file{RMAIL} file. If you have the guts!
17028 Virtual server variables:
17031 @item nndoc-article-type
17032 @vindex nndoc-article-type
17033 This should be one of @code{mbox}, @code{babyl}, @code{digest},
17034 @code{news}, @code{rnews}, @code{mmdf}, @code{forward}, @code{rfc934},
17035 @code{rfc822-forward}, @code{mime-parts}, @code{standard-digest},
17036 @code{slack-digest}, @code{clari-briefs}, @code{nsmail}, @code{outlook},
17037 @code{oe-dbx}, @code{mailman}, and @code{mail-in-mail} or @code{guess}.
17039 @item nndoc-post-type
17040 @vindex nndoc-post-type
17041 This variable says whether Gnus is to consider the group a news group or
17042 a mail group. There are two valid values: @code{mail} (the default)
17047 * Document Server Internals:: How to add your own document types.
17051 @node Document Server Internals
17052 @subsubsection Document Server Internals
17054 Adding new document types to be recognized by @code{nndoc} isn't
17055 difficult. You just have to whip up a definition of what the document
17056 looks like, write a predicate function to recognize that document type,
17057 and then hook into @code{nndoc}.
17059 First, here's an example document type definition:
17063 (article-begin . "^\^A\^A\^A\^A\n")
17064 (body-end . "^\^A\^A\^A\^A\n"))
17067 The definition is simply a unique @dfn{name} followed by a series of
17068 regexp pseudo-variable settings. Below are the possible
17069 variables---don't be daunted by the number of variables; most document
17070 types can be defined with very few settings:
17073 @item first-article
17074 If present, @code{nndoc} will skip past all text until it finds
17075 something that match this regexp. All text before this will be
17078 @item article-begin
17079 This setting has to be present in all document type definitions. It
17080 says what the beginning of each article looks like.
17082 @item head-begin-function
17083 If present, this should be a function that moves point to the head of
17086 @item nndoc-head-begin
17087 If present, this should be a regexp that matches the head of the
17090 @item nndoc-head-end
17091 This should match the end of the head of the article. It defaults to
17092 @samp{^$}---the empty line.
17094 @item body-begin-function
17095 If present, this function should move point to the beginning of the body
17099 This should match the beginning of the body of the article. It defaults
17102 @item body-end-function
17103 If present, this function should move point to the end of the body of
17107 If present, this should match the end of the body of the article.
17110 If present, this should match the end of the file. All text after this
17111 regexp will be totally ignored.
17115 So, using these variables @code{nndoc} is able to dissect a document
17116 file into a series of articles, each with a head and a body. However, a
17117 few more variables are needed since not all document types are all that
17118 news-like---variables needed to transform the head or the body into
17119 something that's palatable for Gnus:
17122 @item prepare-body-function
17123 If present, this function will be called when requesting an article. It
17124 will be called with point at the start of the body, and is useful if the
17125 document has encoded some parts of its contents.
17127 @item article-transform-function
17128 If present, this function is called when requesting an article. It's
17129 meant to be used for more wide-ranging transformation of both head and
17130 body of the article.
17132 @item generate-head-function
17133 If present, this function is called to generate a head that Gnus can
17134 understand. It is called with the article number as a parameter, and is
17135 expected to generate a nice head for the article in question. It is
17136 called when requesting the headers of all articles.
17140 Let's look at the most complicated example I can come up with---standard
17145 (first-article . ,(concat "^" (make-string 70 ?-) "\n\n+"))
17146 (article-begin . ,(concat "\n\n" (make-string 30 ?-) "\n\n+"))
17147 (prepare-body-function . nndoc-unquote-dashes)
17148 (body-end-function . nndoc-digest-body-end)
17149 (head-end . "^ ?$")
17150 (body-begin . "^ ?\n")
17151 (file-end . "^End of .*digest.*[0-9].*\n\\*\\*\\|^End of.*Digest *$")
17152 (subtype digest guess))
17155 We see that all text before a 70-width line of dashes is ignored; all
17156 text after a line that starts with that @samp{^End of} is also ignored;
17157 each article begins with a 30-width line of dashes; the line separating
17158 the head from the body may contain a single space; and that the body is
17159 run through @code{nndoc-unquote-dashes} before being delivered.
17161 To hook your own document definition into @code{nndoc}, use the
17162 @code{nndoc-add-type} function. It takes two parameters---the first
17163 is the definition itself and the second (optional) parameter says
17164 where in the document type definition alist to put this definition.
17165 The alist is traversed sequentially, and
17166 @code{nndoc-@var{type}-type-p} is called for a given type @var{type}.
17167 So @code{nndoc-mmdf-type-p} is called to see whether a document is of
17168 @code{mmdf} type, and so on. These type predicates should return
17169 @code{nil} if the document is not of the correct type; @code{t} if it
17170 is of the correct type; and a number if the document might be of the
17171 correct type. A high number means high probability; a low number
17172 means low probability with @samp{0} being the lowest valid number.
17180 In the PC world people often talk about ``offline'' newsreaders. These
17181 are thingies that are combined reader/news transport monstrosities.
17182 With built-in modem programs. Yecchh!
17184 Of course, us Unix Weenie types of human beans use things like
17185 @code{uucp} and, like, @code{nntpd} and set up proper news and mail
17186 transport things like Ghod intended. And then we just use normal
17189 However, it can sometimes be convenient to do something that's a bit
17190 easier on the brain if you have a very slow modem, and you're not really
17191 that interested in doing things properly.
17193 A file format called @sc{soup} has been developed for transporting news
17194 and mail from servers to home machines and back again. It can be a bit
17197 First some terminology:
17202 This is the machine that is connected to the outside world and where you
17203 get news and/or mail from.
17206 This is the machine that you want to do the actual reading and responding
17207 on. It is typically not connected to the rest of the world in any way.
17210 Something that contains messages and/or commands. There are two kinds
17214 @item message packets
17215 These are packets made at the server, and typically contain lots of
17216 messages for you to read. These are called @file{SoupoutX.tgz} by
17217 default, where @var{x} is a number.
17219 @item response packets
17220 These are packets made at the home machine, and typically contains
17221 replies that you've written. These are called @file{SoupinX.tgz} by
17222 default, where @var{x} is a number.
17232 You log in on the server and create a @sc{soup} packet. You can either
17233 use a dedicated @sc{soup} thingie (like the @code{awk} program), or you
17234 can use Gnus to create the packet with its @sc{soup} commands (@kbd{O
17235 s} and/or @kbd{G s b}; and then @kbd{G s p}) (@pxref{SOUP Commands}).
17238 You transfer the packet home. Rail, boat, car or modem will do fine.
17241 You put the packet in your home directory.
17244 You fire up Gnus on your home machine using the @code{nnsoup} back end as
17245 the native or secondary server.
17248 You read articles and mail and answer and followup to the things you
17249 want (@pxref{SOUP Replies}).
17252 You do the @kbd{G s r} command to pack these replies into a @sc{soup}
17256 You transfer this packet to the server.
17259 You use Gnus to mail this packet out with the @kbd{G s s} command.
17262 You then repeat until you die.
17266 So you basically have a bipartite system---you use @code{nnsoup} for
17267 reading and Gnus for packing/sending these @sc{soup} packets.
17270 * SOUP Commands:: Commands for creating and sending @sc{soup} packets
17271 * SOUP Groups:: A back end for reading @sc{soup} packets.
17272 * SOUP Replies:: How to enable @code{nnsoup} to take over mail and news.
17276 @node SOUP Commands
17277 @subsubsection SOUP Commands
17279 These are commands for creating and manipulating @sc{soup} packets.
17283 @kindex G s b (Group)
17284 @findex gnus-group-brew-soup
17285 Pack all unread articles in the current group
17286 (@code{gnus-group-brew-soup}). This command understands the
17287 process/prefix convention.
17290 @kindex G s w (Group)
17291 @findex gnus-soup-save-areas
17292 Save all @sc{soup} data files (@code{gnus-soup-save-areas}).
17295 @kindex G s s (Group)
17296 @findex gnus-soup-send-replies
17297 Send all replies from the replies packet
17298 (@code{gnus-soup-send-replies}).
17301 @kindex G s p (Group)
17302 @findex gnus-soup-pack-packet
17303 Pack all files into a @sc{soup} packet (@code{gnus-soup-pack-packet}).
17306 @kindex G s r (Group)
17307 @findex nnsoup-pack-replies
17308 Pack all replies into a replies packet (@code{nnsoup-pack-replies}).
17311 @kindex O s (Summary)
17312 @findex gnus-soup-add-article
17313 This summary-mode command adds the current article to a @sc{soup} packet
17314 (@code{gnus-soup-add-article}). It understands the process/prefix
17315 convention (@pxref{Process/Prefix}).
17320 There are a few variables to customize where Gnus will put all these
17325 @item gnus-soup-directory
17326 @vindex gnus-soup-directory
17327 Directory where Gnus will save intermediate files while composing
17328 @sc{soup} packets. The default is @file{~/SoupBrew/}.
17330 @item gnus-soup-replies-directory
17331 @vindex gnus-soup-replies-directory
17332 This is what Gnus will use as a temporary directory while sending our
17333 reply packets. @file{~/SoupBrew/SoupReplies/} is the default.
17335 @item gnus-soup-prefix-file
17336 @vindex gnus-soup-prefix-file
17337 Name of the file where Gnus stores the last used prefix. The default is
17338 @samp{gnus-prefix}.
17340 @item gnus-soup-packer
17341 @vindex gnus-soup-packer
17342 A format string command for packing a @sc{soup} packet. The default is
17343 @samp{tar cf - %s | gzip > $HOME/Soupout%d.tgz}.
17345 @item gnus-soup-unpacker
17346 @vindex gnus-soup-unpacker
17347 Format string command for unpacking a @sc{soup} packet. The default is
17348 @samp{gunzip -c %s | tar xvf -}.
17350 @item gnus-soup-packet-directory
17351 @vindex gnus-soup-packet-directory
17352 Where Gnus will look for reply packets. The default is @file{~/}.
17354 @item gnus-soup-packet-regexp
17355 @vindex gnus-soup-packet-regexp
17356 Regular expression matching @sc{soup} reply packets in
17357 @code{gnus-soup-packet-directory}.
17363 @subsubsection SOUP Groups
17366 @code{nnsoup} is the back end for reading @sc{soup} packets. It will
17367 read incoming packets, unpack them, and put them in a directory where
17368 you can read them at leisure.
17370 These are the variables you can use to customize its behavior:
17374 @item nnsoup-tmp-directory
17375 @vindex nnsoup-tmp-directory
17376 When @code{nnsoup} unpacks a @sc{soup} packet, it does it in this
17377 directory. (@file{/tmp/} by default.)
17379 @item nnsoup-directory
17380 @vindex nnsoup-directory
17381 @code{nnsoup} then moves each message and index file to this directory.
17382 The default is @file{~/SOUP/}.
17384 @item nnsoup-replies-directory
17385 @vindex nnsoup-replies-directory
17386 All replies will be stored in this directory before being packed into a
17387 reply packet. The default is @file{~/SOUP/replies/}.
17389 @item nnsoup-replies-format-type
17390 @vindex nnsoup-replies-format-type
17391 The @sc{soup} format of the replies packets. The default is @samp{?n}
17392 (rnews), and I don't think you should touch that variable. I probably
17393 shouldn't even have documented it. Drats! Too late!
17395 @item nnsoup-replies-index-type
17396 @vindex nnsoup-replies-index-type
17397 The index type of the replies packet. The default is @samp{?n}, which
17398 means ``none''. Don't fiddle with this one either!
17400 @item nnsoup-active-file
17401 @vindex nnsoup-active-file
17402 Where @code{nnsoup} stores lots of information. This is not an ``active
17403 file'' in the @code{nntp} sense; it's an Emacs Lisp file. If you lose
17404 this file or mess it up in any way, you're dead. The default is
17405 @file{~/SOUP/active}.
17407 @item nnsoup-packer
17408 @vindex nnsoup-packer
17409 Format string command for packing a reply @sc{soup} packet. The default
17410 is @samp{tar cf - %s | gzip > $HOME/Soupin%d.tgz}.
17412 @item nnsoup-unpacker
17413 @vindex nnsoup-unpacker
17414 Format string command for unpacking incoming @sc{soup} packets. The
17415 default is @samp{gunzip -c %s | tar xvf -}.
17417 @item nnsoup-packet-directory
17418 @vindex nnsoup-packet-directory
17419 Where @code{nnsoup} will look for incoming packets. The default is
17422 @item nnsoup-packet-regexp
17423 @vindex nnsoup-packet-regexp
17424 Regular expression matching incoming @sc{soup} packets. The default is
17427 @item nnsoup-always-save
17428 @vindex nnsoup-always-save
17429 If non-@code{nil}, save the replies buffer after each posted message.
17435 @subsubsection SOUP Replies
17437 Just using @code{nnsoup} won't mean that your postings and mailings end
17438 up in @sc{soup} reply packets automagically. You have to work a bit
17439 more for that to happen.
17441 @findex nnsoup-set-variables
17442 The @code{nnsoup-set-variables} command will set the appropriate
17443 variables to ensure that all your followups and replies end up in the
17446 In specific, this is what it does:
17449 (setq message-send-news-function 'nnsoup-request-post)
17450 (setq message-send-mail-function 'nnsoup-request-mail)
17453 And that's it, really. If you only want news to go into the @sc{soup}
17454 system you just use the first line. If you only want mail to be
17455 @sc{soup}ed you use the second.
17458 @node Mail-To-News Gateways
17459 @subsection Mail-To-News Gateways
17460 @cindex mail-to-news gateways
17463 If your local @code{nntp} server doesn't allow posting, for some reason
17464 or other, you can post using one of the numerous mail-to-news gateways.
17465 The @code{nngateway} back end provides the interface.
17467 Note that you can't read anything from this back end---it can only be
17473 @item nngateway-address
17474 @vindex nngateway-address
17475 This is the address of the mail-to-news gateway.
17477 @item nngateway-header-transformation
17478 @vindex nngateway-header-transformation
17479 News headers often have to be transformed in some odd way or other
17480 for the mail-to-news gateway to accept it. This variable says what
17481 transformation should be called, and defaults to
17482 @code{nngateway-simple-header-transformation}. The function is called
17483 narrowed to the headers to be transformed and with one parameter---the
17486 This default function just inserts a new @code{To} header based on the
17487 @code{Newsgroups} header and the gateway address.
17488 For instance, an article with this @code{Newsgroups} header:
17491 Newsgroups: alt.religion.emacs
17494 will get this @code{To} header inserted:
17497 To: alt-religion-emacs@@GATEWAY
17500 The following pre-defined functions exist:
17502 @findex nngateway-simple-header-transformation
17505 @item nngateway-simple-header-transformation
17506 Creates a @code{To} header that looks like
17507 @var{newsgroup}@@@code{nngateway-address}.
17509 @findex nngateway-mail2news-header-transformation
17511 @item nngateway-mail2news-header-transformation
17512 Creates a @code{To} header that looks like
17513 @code{nngateway-address}.
17521 (setq gnus-post-method
17523 "mail2news@@replay.com"
17524 (nngateway-header-transformation
17525 nngateway-mail2news-header-transformation)))
17528 So, to use this, simply say something like:
17531 (setq gnus-post-method '(nngateway "GATEWAY.ADDRESS"))
17536 @node Combined Groups
17537 @section Combined Groups
17539 Gnus allows combining a mixture of all the other group types into bigger
17543 * Virtual Groups:: Combining articles from many groups.
17544 * Kibozed Groups:: Looking through parts of the newsfeed for articles.
17548 @node Virtual Groups
17549 @subsection Virtual Groups
17551 @cindex virtual groups
17552 @cindex merging groups
17554 An @dfn{nnvirtual group} is really nothing more than a collection of
17557 For instance, if you are tired of reading many small groups, you can
17558 put them all in one big group, and then grow tired of reading one
17559 big, unwieldy group. The joys of computing!
17561 You specify @code{nnvirtual} as the method. The address should be a
17562 regexp to match component groups.
17564 All marks in the virtual group will stick to the articles in the
17565 component groups. So if you tick an article in a virtual group, the
17566 article will also be ticked in the component group from whence it
17567 came. (And vice versa---marks from the component groups will also be
17568 shown in the virtual group.). To create an empty virtual group, run
17569 @kbd{G V} (@code{gnus-group-make-empty-virtual}) in the group buffer
17570 and edit the method regexp with @kbd{M-e}
17571 (@code{gnus-group-edit-group-method})
17573 Here's an example @code{nnvirtual} method that collects all Andrea Dworkin
17574 newsgroups into one, big, happy newsgroup:
17577 (nnvirtual "^alt\\.fan\\.andrea-dworkin$\\|^rec\\.dworkin.*")
17580 The component groups can be native or foreign; everything should work
17581 smoothly, but if your computer explodes, it was probably my fault.
17583 Collecting the same group from several servers might actually be a good
17584 idea if users have set the Distribution header to limit distribution.
17585 If you would like to read @samp{soc.motss} both from a server in Japan
17586 and a server in Norway, you could use the following as the group regexp:
17589 "^nntp\\+server\\.jp:soc\\.motss$\\|^nntp\\+server\\.no:soc\\.motss$"
17592 (Remember, though, that if you're creating the group with @kbd{G m}, you
17593 shouldn't double the backslashes, and you should leave off the quote
17594 characters at the beginning and the end of the string.)
17596 This should work kinda smoothly---all articles from both groups should
17597 end up in this one, and there should be no duplicates. Threading (and
17598 the rest) will still work as usual, but there might be problems with the
17599 sequence of articles. Sorting on date might be an option here
17600 (@pxref{Selecting a Group}).
17602 One limitation, however---all groups included in a virtual
17603 group have to be alive (i.e., subscribed or unsubscribed). Killed or
17604 zombie groups can't be component groups for @code{nnvirtual} groups.
17606 @vindex nnvirtual-always-rescan
17607 If the @code{nnvirtual-always-rescan} is non-@code{nil},
17608 @code{nnvirtual} will always scan groups for unread articles when
17609 entering a virtual group. If this variable is @code{nil} (which is the
17610 default) and you read articles in a component group after the virtual
17611 group has been activated, the read articles from the component group
17612 will show up when you enter the virtual group. You'll also see this
17613 effect if you have two virtual groups that have a component group in
17614 common. If that's the case, you should set this variable to @code{t}.
17615 Or you can just tap @code{M-g} on the virtual group every time before
17616 you enter it---it'll have much the same effect.
17618 @code{nnvirtual} can have both mail and news groups as component groups.
17619 When responding to articles in @code{nnvirtual} groups, @code{nnvirtual}
17620 has to ask the back end of the component group the article comes from
17621 whether it is a news or mail back end. However, when you do a @kbd{^},
17622 there is typically no sure way for the component back end to know this,
17623 and in that case @code{nnvirtual} tells Gnus that the article came from a
17624 not-news back end. (Just to be on the safe side.)
17626 @kbd{C-c C-n} in the message buffer will insert the @code{Newsgroups}
17627 line from the article you respond to in these cases.
17629 @code{nnvirtual} groups do not inherit anything but articles and marks
17630 from component groups---group parameters, for instance, are not
17634 @node Kibozed Groups
17635 @subsection Kibozed Groups
17639 @dfn{Kibozing} is defined by the @acronym{OED} as ``grepping through
17640 (parts of) the news feed''. @code{nnkiboze} is a back end that will
17641 do this for you. Oh joy! Now you can grind any @acronym{NNTP} server
17642 down to a halt with useless requests! Oh happiness!
17644 @kindex G k (Group)
17645 To create a kibozed group, use the @kbd{G k} command in the group
17648 The address field of the @code{nnkiboze} method is, as with
17649 @code{nnvirtual}, a regexp to match groups to be ``included'' in the
17650 @code{nnkiboze} group. That's where most similarities between
17651 @code{nnkiboze} and @code{nnvirtual} end.
17653 In addition to this regexp detailing component groups, an
17654 @code{nnkiboze} group must have a score file to say what articles are
17655 to be included in the group (@pxref{Scoring}).
17657 @kindex M-x nnkiboze-generate-groups
17658 @findex nnkiboze-generate-groups
17659 You must run @kbd{M-x nnkiboze-generate-groups} after creating the
17660 @code{nnkiboze} groups you want to have. This command will take time.
17661 Lots of time. Oodles and oodles of time. Gnus has to fetch the
17662 headers from all the articles in all the component groups and run them
17663 through the scoring process to determine if there are any articles in
17664 the groups that are to be part of the @code{nnkiboze} groups.
17666 Please limit the number of component groups by using restrictive
17667 regexps. Otherwise your sysadmin may become annoyed with you, and the
17668 @acronym{NNTP} site may throw you off and never let you back in again.
17669 Stranger things have happened.
17671 @code{nnkiboze} component groups do not have to be alive---they can be dead,
17672 and they can be foreign. No restrictions.
17674 @vindex nnkiboze-directory
17675 The generation of an @code{nnkiboze} group means writing two files in
17676 @code{nnkiboze-directory}, which is @file{~/News/kiboze/} by default.
17677 One contains the @acronym{NOV} header lines for all the articles in
17678 the group, and the other is an additional @file{.newsrc} file to store
17679 information on what groups have been searched through to find
17680 component articles.
17682 Articles marked as read in the @code{nnkiboze} group will have
17683 their @acronym{NOV} lines removed from the @acronym{NOV} file.
17686 @node Gnus Unplugged
17687 @section Gnus Unplugged
17692 @cindex Gnus unplugged
17694 In olden times (ca. February '88), people used to run their newsreaders
17695 on big machines with permanent connections to the net. News transport
17696 was dealt with by news servers, and all the newsreaders had to do was to
17697 read news. Believe it or not.
17699 Nowadays most people read news and mail at home, and use some sort of
17700 modem to connect to the net. To avoid running up huge phone bills, it
17701 would be nice to have a way to slurp down all the news and mail, hang up
17702 the phone, read for several hours, and then upload any responses you
17703 have to make. And then you repeat the procedure.
17705 Of course, you can use news servers for doing this as well. I've used
17706 @code{inn} together with @code{slurp}, @code{pop} and @code{sendmail}
17707 for some years, but doing that's a bore. Moving the news server
17708 functionality up to the newsreader makes sense if you're the only person
17709 reading news on a machine.
17711 Setting up Gnus as an ``offline'' newsreader is quite simple. In
17712 fact, you don't have to configure anything as the agent is now enabled
17713 by default (@pxref{Agent Variables, gnus-agent}).
17715 Of course, to use it as such, you have to learn a few new commands.
17718 * Agent Basics:: How it all is supposed to work.
17719 * Agent Categories:: How to tell the Gnus Agent what to download.
17720 * Agent Commands:: New commands for all the buffers.
17721 * Agent Visuals:: Ways that the agent may effect your summary buffer.
17722 * Agent as Cache:: The Agent is a big cache too.
17723 * Agent Expiry:: How to make old articles go away.
17724 * Agent Regeneration:: How to recover from lost connections and other accidents.
17725 * Agent and IMAP:: How to use the Agent with @acronym{IMAP}.
17726 * Outgoing Messages:: What happens when you post/mail something?
17727 * Agent Variables:: Customizing is fun.
17728 * Example Setup:: An example @file{~/.gnus.el} file for offline people.
17729 * Batching Agents:: How to fetch news from a @code{cron} job.
17730 * Agent Caveats:: What you think it'll do and what it does.
17735 @subsection Agent Basics
17737 First, let's get some terminology out of the way.
17739 The Gnus Agent is said to be @dfn{unplugged} when you have severed the
17740 connection to the net (and notified the Agent that this is the case).
17741 When the connection to the net is up again (and Gnus knows this), the
17742 Agent is @dfn{plugged}.
17744 The @dfn{local} machine is the one you're running on, and which isn't
17745 connected to the net continuously.
17747 @dfn{Downloading} means fetching things from the net to your local
17748 machine. @dfn{Uploading} is doing the opposite.
17750 You know that Gnus gives you all the opportunity you'd ever want for
17751 shooting yourself in the foot. Some people call it flexibility. Gnus
17752 is also customizable to a great extent, which means that the user has a
17753 say on how Gnus behaves. Other newsreaders might unconditionally shoot
17754 you in your foot, but with Gnus, you have a choice!
17756 Gnus is never really in plugged or unplugged state. Rather, it applies
17757 that state to each server individually. This means that some servers
17758 can be plugged while others can be unplugged. Additionally, some
17759 servers can be ignored by the Agent altogether (which means that
17760 they're kinda like plugged always).
17762 So when you unplug the Agent and then wonder why is Gnus opening a
17763 connection to the Net, the next step to do is to look whether all
17764 servers are agentized. If there is an unagentized server, you found
17767 Another thing is the @dfn{offline} state. Sometimes, servers aren't
17768 reachable. When Gnus notices this, it asks you whether you want the
17769 server to be switched to offline state. If you say yes, then the
17770 server will behave somewhat as if it was unplugged, except that Gnus
17771 will ask you whether you want to switch it back online again.
17773 Let's take a typical Gnus session using the Agent.
17778 @findex gnus-unplugged
17779 You start Gnus with @code{gnus-unplugged}. This brings up the Gnus
17780 Agent in a disconnected state. You can read all the news that you have
17781 already fetched while in this mode.
17784 You then decide to see whether any new news has arrived. You connect
17785 your machine to the net (using PPP or whatever), and then hit @kbd{J j}
17786 to make Gnus become @dfn{plugged} and use @kbd{g} to check for new mail
17787 as usual. To check for new mail in unplugged mode (@pxref{Mail
17788 Source Specifiers}).
17791 You can then read the new news immediately, or you can download the
17792 news onto your local machine. If you want to do the latter, you press
17793 @kbd{g} to check if there are any new news and then @kbd{J s} to fetch
17794 all the eligible articles in all the groups. (To let Gnus know which
17795 articles you want to download, @pxref{Agent Categories}).
17798 After fetching the articles, you press @kbd{J j} to make Gnus become
17799 unplugged again, and you shut down the PPP thing (or whatever). And
17800 then you read the news offline.
17803 And then you go to step 2.
17806 Here are some things you should do the first time (or so) that you use
17812 Decide which servers should be covered by the Agent. If you have a mail
17813 back end, it would probably be nonsensical to have it covered by the
17814 Agent. Go to the server buffer (@kbd{^} in the group buffer) and press
17815 @kbd{J a} on the server (or servers) that you wish to have covered by the
17816 Agent (@pxref{Server Agent Commands}), or @kbd{J r} on automatically
17817 added servers you do not wish to have covered by the Agent. By default,
17818 all @code{nntp} and @code{nnimap} servers in @code{gnus-select-method} and
17819 @code{gnus-secondary-select-methods} are agentized.
17822 Decide on download policy. It's fairly simple once you decide whether
17823 you are going to use agent categories, topic parameters, and/or group
17824 parameters to implement your policy. If you're new to gnus, it
17825 is probably best to start with a category, @xref{Agent Categories}.
17827 Both topic parameters (@pxref{Topic Parameters}) and agent categories
17828 (@pxref{Agent Categories}) provide for setting a policy that applies
17829 to multiple groups. Which you use is entirely up to you. Topic
17830 parameters do override categories so, if you mix the two, you'll have
17831 to take that into account. If you have a few groups that deviate from
17832 your policy, you can use group parameters (@pxref{Group Parameters}) to
17836 Uhm@dots{} that's it.
17840 @node Agent Categories
17841 @subsection Agent Categories
17843 One of the main reasons to integrate the news transport layer into the
17844 newsreader is to allow greater control over what articles to download.
17845 There's not much point in downloading huge amounts of articles, just to
17846 find out that you're not interested in reading any of them. It's better
17847 to be somewhat more conservative in choosing what to download, and then
17848 mark the articles for downloading manually if it should turn out that
17849 you're interested in the articles anyway.
17851 One of the more effective methods for controlling what is to be
17852 downloaded is to create a @dfn{category} and then assign some (or all)
17853 groups to this category. Groups that do not belong in any other
17854 category belong to the @code{default} category. Gnus has its own
17855 buffer for creating and managing categories.
17857 If you prefer, you can also use group parameters (@pxref{Group
17858 Parameters}) and topic parameters (@pxref{Topic Parameters}) for an
17859 alternative approach to controlling the agent. The only real
17860 difference is that categories are specific to the agent (so there is
17861 less to learn) while group and topic parameters include the kitchen
17864 Since you can set agent parameters in several different places we have
17865 a rule to decide which source to believe. This rule specifies that
17866 the parameter sources are checked in the following order: group
17867 parameters, topic parameters, agent category, and finally customizable
17868 variables. So you can mix all of these sources to produce a wide range
17869 of behavior, just don't blame me if you don't remember where you put
17873 * Category Syntax:: What a category looks like.
17874 * Category Buffer:: A buffer for maintaining categories.
17875 * Category Variables:: Customize'r'Us.
17879 @node Category Syntax
17880 @subsubsection Category Syntax
17882 A category consists of a name, the list of groups belonging to the
17883 category, and a number of optional parameters that override the
17884 customizable variables. The complete list of agent parameters are
17887 @cindex Agent Parameters
17889 @item agent-cat-name
17890 The name of the category.
17893 The list of groups that are in this category.
17895 @item agent-predicate
17896 A predicate which (generally) gives a rough outline of which articles
17897 are eligible for downloading; and
17899 @item agent-score-file
17900 a score rule which (generally) gives you a finer granularity when
17901 deciding what articles to download. (Note that this @dfn{download
17902 score} is not necessarily related to normal scores.)
17904 @item agent-enable-expiration
17905 a boolean indicating whether the agent should expire old articles in
17906 this group. Most groups should be expired to conserve disk space. In
17907 fact, its probably safe to say that the gnus.* hierarchy contains the
17908 only groups that should not be expired.
17910 @item agent-days-until-old
17911 an integer indicating the number of days that the agent should wait
17912 before deciding that a read article is safe to expire.
17914 @item agent-low-score
17915 an integer that overrides the value of @code{gnus-agent-low-score}.
17917 @item agent-high-score
17918 an integer that overrides the value of @code{gnus-agent-high-score}.
17920 @item agent-length-when-short
17921 an integer that overrides the value of
17922 @code{gnus-agent-short-article}.
17924 @item agent-length-when-long
17925 an integer that overrides the value of @code{gnus-agent-long-article}.
17927 @item agent-enable-undownloaded-faces
17928 a symbol indicating whether the summary buffer should display
17929 undownloaded articles using the @code{gnus-summary-*-undownloaded-face}
17930 faces. Any symbol other than @code{nil} will enable the use of
17931 undownloaded faces.
17934 The name of a category can not be changed once the category has been
17937 Each category maintains a list of groups that are exclusive members of
17938 that category. The exclusivity rule is automatically enforced, add a
17939 group to a new category and it is automatically removed from its old
17942 A predicate in its simplest form can be a single predicate such as
17943 @code{true} or @code{false}. These two will download every available
17944 article or nothing respectively. In the case of these two special
17945 predicates an additional score rule is superfluous.
17947 Predicates of @code{high} or @code{low} download articles in respect of
17948 their scores in relationship to @code{gnus-agent-high-score} and
17949 @code{gnus-agent-low-score} as described below.
17951 To gain even finer control of what is to be regarded eligible for
17952 download a predicate can consist of a number of predicates with logical
17953 operators sprinkled in between.
17955 Perhaps some examples are in order.
17957 Here's a simple predicate. (It's the default predicate, in fact, used
17958 for all groups that don't belong to any other category.)
17964 Quite simple, eh? This predicate is true if and only if the article is
17965 short (for some value of ``short'').
17967 Here's a more complex predicate:
17976 This means that an article should be downloaded if it has a high score,
17977 or if the score is not low and the article is not long. You get the
17980 The available logical operators are @code{or}, @code{and} and
17981 @code{not}. (If you prefer, you can use the more ``C''-ish operators
17982 @samp{|}, @code{&} and @code{!} instead.)
17984 The following predicates are pre-defined, but if none of these fit what
17985 you want to do, you can write your own.
17987 When evaluating each of these predicates, the named constant will be
17988 bound to the value determined by calling
17989 @code{gnus-agent-find-parameter} on the appropriate parameter. For
17990 example, gnus-agent-short-article will be bound to
17991 @code{(gnus-agent-find-parameter group 'agent-short-article)}. This
17992 means that you can specify a predicate in your category then tune that
17993 predicate to individual groups.
17997 True iff the article is shorter than @code{gnus-agent-short-article}
17998 lines; default 100.
18001 True iff the article is longer than @code{gnus-agent-long-article}
18002 lines; default 200.
18005 True iff the article has a download score less than
18006 @code{gnus-agent-low-score}; default 0.
18009 True iff the article has a download score greater than
18010 @code{gnus-agent-high-score}; default 0.
18013 True iff the Gnus Agent guesses that the article is spam. The
18014 heuristics may change over time, but at present it just computes a
18015 checksum and sees whether articles match.
18024 If you want to create your own predicate function, here's what you have
18025 to know: The functions are called with no parameters, but the
18026 @code{gnus-headers} and @code{gnus-score} dynamic variables are bound to
18029 For example, you could decide that you don't want to download articles
18030 that were posted more than a certain number of days ago (e.g. posted
18031 more than @code{gnus-agent-expire-days} ago) you might write a function
18032 something along the lines of the following:
18035 (defun my-article-old-p ()
18036 "Say whether an article is old."
18037 (< (time-to-days (date-to-time (mail-header-date gnus-headers)))
18038 (- (time-to-days (current-time)) gnus-agent-expire-days)))
18041 with the predicate then defined as:
18044 (not my-article-old-p)
18047 or you could append your predicate to the predefined
18048 @code{gnus-category-predicate-alist} in your @file{~/.gnus.el} or
18052 (require 'gnus-agent)
18053 (setq gnus-category-predicate-alist
18054 (append gnus-category-predicate-alist
18055 '((old . my-article-old-p))))
18058 and simply specify your predicate as:
18064 If/when using something like the above, be aware that there are many
18065 misconfigured systems/mailers out there and so an article's date is not
18066 always a reliable indication of when it was posted. Hell, some people
18067 just don't give a damn.
18069 The above predicates apply to @emph{all} the groups which belong to the
18070 category. However, if you wish to have a specific predicate for an
18071 individual group within a category, or you're just too lazy to set up a
18072 new category, you can enter a group's individual predicate in its group
18073 parameters like so:
18076 (agent-predicate . short)
18079 This is the group/topic parameter equivalent of the agent category default.
18080 Note that when specifying a single word predicate like this, the
18081 @code{agent-predicate} specification must be in dotted pair notation.
18083 The equivalent of the longer example from above would be:
18086 (agent-predicate or high (and (not low) (not long)))
18089 The outer parenthesis required in the category specification are not
18090 entered here as, not being in dotted pair notation, the value of the
18091 predicate is assumed to be a list.
18094 Now, the syntax of the download score is the same as the syntax of
18095 normal score files, except that all elements that require actually
18096 seeing the article itself are verboten. This means that only the
18097 following headers can be scored on: @code{Subject}, @code{From},
18098 @code{Date}, @code{Message-ID}, @code{References}, @code{Chars},
18099 @code{Lines}, and @code{Xref}.
18101 As with predicates, the specification of the @code{download score rule}
18102 to use in respect of a group can be in either the category definition if
18103 it's to be applicable to all groups in therein, or a group's parameters
18104 if it's to be specific to that group.
18106 In both of these places the @code{download score rule} can take one of
18113 This has the same syntax as a normal Gnus score file except only a
18114 subset of scoring keywords are available as mentioned above.
18120 Category specification
18124 ("Lars Ingebrigtsen" 1000000 nil s))
18130 Group/Topic Parameter specification
18133 (agent-score ("from"
18134 ("Lars Ingebrigtsen" 1000000 nil s))
18139 Again, note the omission of the outermost parenthesis here.
18145 These score files must @emph{only} contain the permitted scoring
18146 keywords stated above.
18152 Category specification
18155 ("~/News/agent.SCORE")
18161 ("~/News/agent.SCORE" "~/News/agent.group.SCORE")
18165 Group Parameter specification
18168 (agent-score "~/News/agent.SCORE")
18171 Additional score files can be specified as above. Need I say anything
18176 Use @code{normal} score files
18178 If you don't want to maintain two sets of scoring rules for a group, and
18179 your desired @code{downloading} criteria for a group are the same as your
18180 @code{reading} criteria then you can tell the agent to refer to your
18181 @code{normal} score files when deciding what to download.
18183 These directives in either the category definition or a group's
18184 parameters will cause the agent to read in all the applicable score
18185 files for a group, @emph{filtering out} those sections that do not
18186 relate to one of the permitted subset of scoring keywords.
18190 Category Specification
18197 Group Parameter specification
18200 (agent-score . file)
18205 @node Category Buffer
18206 @subsubsection Category Buffer
18208 You'd normally do all category maintenance from the category buffer.
18209 When you enter it for the first time (with the @kbd{J c} command from
18210 the group buffer), you'll only see the @code{default} category.
18212 The following commands are available in this buffer:
18216 @kindex q (Category)
18217 @findex gnus-category-exit
18218 Return to the group buffer (@code{gnus-category-exit}).
18221 @kindex e (Category)
18222 @findex gnus-category-customize-category
18223 Use a customization buffer to set all of the selected category's
18224 parameters at one time (@code{gnus-category-customize-category}).
18227 @kindex k (Category)
18228 @findex gnus-category-kill
18229 Kill the current category (@code{gnus-category-kill}).
18232 @kindex c (Category)
18233 @findex gnus-category-copy
18234 Copy the current category (@code{gnus-category-copy}).
18237 @kindex a (Category)
18238 @findex gnus-category-add
18239 Add a new category (@code{gnus-category-add}).
18242 @kindex p (Category)
18243 @findex gnus-category-edit-predicate
18244 Edit the predicate of the current category
18245 (@code{gnus-category-edit-predicate}).
18248 @kindex g (Category)
18249 @findex gnus-category-edit-groups
18250 Edit the list of groups belonging to the current category
18251 (@code{gnus-category-edit-groups}).
18254 @kindex s (Category)
18255 @findex gnus-category-edit-score
18256 Edit the download score rule of the current category
18257 (@code{gnus-category-edit-score}).
18260 @kindex l (Category)
18261 @findex gnus-category-list
18262 List all the categories (@code{gnus-category-list}).
18266 @node Category Variables
18267 @subsubsection Category Variables
18270 @item gnus-category-mode-hook
18271 @vindex gnus-category-mode-hook
18272 Hook run in category buffers.
18274 @item gnus-category-line-format
18275 @vindex gnus-category-line-format
18276 Format of the lines in the category buffer (@pxref{Formatting
18277 Variables}). Valid elements are:
18281 The name of the category.
18284 The number of groups in the category.
18287 @item gnus-category-mode-line-format
18288 @vindex gnus-category-mode-line-format
18289 Format of the category mode line (@pxref{Mode Line Formatting}).
18291 @item gnus-agent-short-article
18292 @vindex gnus-agent-short-article
18293 Articles that have fewer lines than this are short. Default 100.
18295 @item gnus-agent-long-article
18296 @vindex gnus-agent-long-article
18297 Articles that have more lines than this are long. Default 200.
18299 @item gnus-agent-low-score
18300 @vindex gnus-agent-low-score
18301 Articles that have a score lower than this have a low score. Default
18304 @item gnus-agent-high-score
18305 @vindex gnus-agent-high-score
18306 Articles that have a score higher than this have a high score. Default
18309 @item gnus-agent-expire-days
18310 @vindex gnus-agent-expire-days
18311 The number of days that a @samp{read} article must stay in the agent's
18312 local disk before becoming eligible for expiration (While the name is
18313 the same, this doesn't mean expiring the article on the server. It
18314 just means deleting the local copy of the article). What is also
18315 important to understand is that the counter starts with the time the
18316 article was written to the local disk and not the time the article was
18320 @item gnus-agent-enable-expiration
18321 @vindex gnus-agent-enable-expiration
18322 Determines whether articles in a group are, by default, expired or
18323 retained indefinitely. The default is @code{ENABLE} which means that
18324 you'll have to disable expiration when desired. On the other hand,
18325 you could set this to @code{DISABLE}. In that case, you would then
18326 have to enable expiration in selected groups.
18331 @node Agent Commands
18332 @subsection Agent Commands
18333 @findex gnus-agent-toggle-plugged
18334 @kindex J j (Agent)
18336 All the Gnus Agent commands are on the @kbd{J} submap. The @kbd{J j}
18337 (@code{gnus-agent-toggle-plugged}) command works in all modes, and
18338 toggles the plugged/unplugged state of the Gnus Agent.
18342 * Group Agent Commands:: Configure groups and fetch their contents.
18343 * Summary Agent Commands:: Manually select then fetch specific articles.
18344 * Server Agent Commands:: Select the servers that are supported by the agent.
18350 @node Group Agent Commands
18351 @subsubsection Group Agent Commands
18355 @kindex J u (Agent Group)
18356 @findex gnus-agent-fetch-groups
18357 Fetch all eligible articles in the current group
18358 (@code{gnus-agent-fetch-groups}).
18361 @kindex J c (Agent Group)
18362 @findex gnus-enter-category-buffer
18363 Enter the Agent category buffer (@code{gnus-enter-category-buffer}).
18366 @kindex J s (Agent Group)
18367 @findex gnus-agent-fetch-session
18368 Fetch all eligible articles in all groups
18369 (@code{gnus-agent-fetch-session}).
18372 @kindex J S (Agent Group)
18373 @findex gnus-group-send-queue
18374 Send all sendable messages in the queue group
18375 (@code{gnus-group-send-queue}). @xref{Drafts}.
18378 @kindex J a (Agent Group)
18379 @findex gnus-agent-add-group
18380 Add the current group to an Agent category
18381 (@code{gnus-agent-add-group}). This command understands the
18382 process/prefix convention (@pxref{Process/Prefix}).
18385 @kindex J r (Agent Group)
18386 @findex gnus-agent-remove-group
18387 Remove the current group from its category, if any
18388 (@code{gnus-agent-remove-group}). This command understands the
18389 process/prefix convention (@pxref{Process/Prefix}).
18392 @kindex J Y (Agent Group)
18393 @findex gnus-agent-synchronize-flags
18394 Synchronize flags changed while unplugged with remote server, if any.
18400 @node Summary Agent Commands
18401 @subsubsection Summary Agent Commands
18405 @kindex J # (Agent Summary)
18406 @findex gnus-agent-mark-article
18407 Mark the article for downloading (@code{gnus-agent-mark-article}).
18410 @kindex J M-# (Agent Summary)
18411 @findex gnus-agent-unmark-article
18412 Remove the downloading mark from the article
18413 (@code{gnus-agent-unmark-article}).
18417 @kindex @@ (Agent Summary)
18418 @findex gnus-agent-toggle-mark
18419 Toggle whether to download the article
18420 (@code{gnus-agent-toggle-mark}). The download mark is @samp{%} by
18424 @kindex J c (Agent Summary)
18425 @findex gnus-agent-catchup
18426 Mark all articles as read (@code{gnus-agent-catchup}) that are neither cached, downloaded, nor downloadable.
18429 @kindex J S (Agent Summary)
18430 @findex gnus-agent-fetch-group
18431 Download all eligible (@pxref{Agent Categories}) articles in this group.
18432 (@code{gnus-agent-fetch-group}).
18435 @kindex J s (Agent Summary)
18436 @findex gnus-agent-fetch-series
18437 Download all processable articles in this group.
18438 (@code{gnus-agent-fetch-series}).
18441 @kindex J u (Agent Summary)
18442 @findex gnus-agent-summary-fetch-group
18443 Download all downloadable articles in the current group
18444 (@code{gnus-agent-summary-fetch-group}).
18449 @node Server Agent Commands
18450 @subsubsection Server Agent Commands
18454 @kindex J a (Agent Server)
18455 @findex gnus-agent-add-server
18456 Add the current server to the list of servers covered by the Gnus Agent
18457 (@code{gnus-agent-add-server}).
18460 @kindex J r (Agent Server)
18461 @findex gnus-agent-remove-server
18462 Remove the current server from the list of servers covered by the Gnus
18463 Agent (@code{gnus-agent-remove-server}).
18468 @node Agent Visuals
18469 @subsection Agent Visuals
18471 If you open a summary while unplugged and, Gnus knows from the group's
18472 active range that there are more articles than the headers currently
18473 stored in the Agent, you may see some articles whose subject looks
18474 something like @samp{[Undownloaded article #####]}. These are
18475 placeholders for the missing headers. Aside from setting a mark,
18476 there is not much that can be done with one of these placeholders.
18477 When Gnus finally gets a chance to fetch the group's headers, the
18478 placeholders will automatically be replaced by the actual headers.
18479 You can configure the summary buffer's maneuvering to skip over the
18480 placeholders if you care (See @code{gnus-auto-goto-ignores}).
18482 While it may be obvious to all, the only headers and articles
18483 available while unplugged are those headers and articles that were
18484 fetched into the Agent while previously plugged. To put it another
18485 way, ``If you forget to fetch something while plugged, you might have a
18486 less than satisfying unplugged session''. For this reason, the Agent
18487 adds two visual effects to your summary buffer. These effects display
18488 the download status of each article so that you always know which
18489 articles will be available when unplugged.
18491 The first visual effect is the @samp{%O} spec. If you customize
18492 @code{gnus-summary-line-format} to include this specifier, you will add
18493 a single character field that indicates an article's download status.
18494 Articles that have been fetched into either the Agent or the Cache,
18495 will display @code{gnus-downloaded-mark} (defaults to @samp{+}). All
18496 other articles will display @code{gnus-undownloaded-mark} (defaults to
18497 @samp{-}). If you open a group that has not been agentized, a space
18498 (@samp{ }) will be displayed.
18500 The second visual effect are the undownloaded faces. The faces, there
18501 are three indicating the article's score (low, normal, high), seem to
18502 result in a love/hate response from many Gnus users. The problem is
18503 that the face selection is controlled by a list of condition tests and
18504 face names (See @code{gnus-summary-highlight}). Each condition is
18505 tested in the order in which it appears in the list so early
18506 conditions have precedence over later conditions. All of this means
18507 that, if you tick an undownloaded article, the article will continue
18508 to be displayed in the undownloaded face rather than the ticked face.
18510 If you use the Agent as a cache (to avoid downloading the same article
18511 each time you visit it or to minimize your connection time), the
18512 undownloaded face will probably seem like a good idea. The reason
18513 being that you do all of our work (marking, reading, deleting) with
18514 downloaded articles so the normal faces always appear. For those
18515 users using the agent to improve online performance by caching the NOV
18516 database (most users since 5.10.2), the undownloaded faces may appear
18517 to be an absolutely horrible idea. The issue being that, since none
18518 of their articles have been fetched into the Agent, all of the
18519 normal faces will be obscured by the undownloaded faces.
18521 If you would like to use the undownloaded faces, you must enable the
18522 undownloaded faces by setting the @code{agent-enable-undownloaded-faces}
18523 group parameter to t. This parameter, like all other agent
18524 parameters, may be set on an Agent Category (@pxref{Agent
18525 Categories}), a Group Topic (@pxref{Topic Parameters}), or an
18526 individual group (@pxref{Group Parameters}).
18528 The one problem common to all users using the agent is how quickly it
18529 can consume disk space. If you using the agent on many groups, it is
18530 even more difficult to effectively recover disk space. One solution
18531 is the @samp{%F} format available in @code{gnus-group-line-format}.
18532 This format will display the actual disk space used by articles
18533 fetched into both the agent and cache. By knowing which groups use
18534 the most space, users know where to focus their efforts when ``agent
18535 expiring'' articles.
18537 @node Agent as Cache
18538 @subsection Agent as Cache
18540 When Gnus is plugged, it is not efficient to download headers or
18541 articles from the server again, if they are already stored in the
18542 Agent. So, Gnus normally only downloads headers once, and stores them
18543 in the Agent. These headers are later used when generating the summary
18544 buffer, regardless of whether you are plugged or unplugged. Articles
18545 are not cached in the Agent by default though (that would potentially
18546 consume lots of disk space), but if you have already downloaded an
18547 article into the Agent, Gnus will not download the article from the
18548 server again but use the locally stored copy instead.
18550 If you so desire, you can configure the agent (see @code{gnus-agent-cache}
18551 @pxref{Agent Variables}) to always download headers and articles while
18552 plugged. Gnus will almost certainly be slower, but it will be kept
18553 synchronized with the server. That last point probably won't make any
18554 sense if you are using a nntp or nnimap back end.
18557 @subsection Agent Expiry
18559 @vindex gnus-agent-expire-days
18560 @findex gnus-agent-expire
18561 @kindex M-x gnus-agent-expire
18562 @kindex M-x gnus-agent-expire-group
18563 @findex gnus-agent-expire-group
18564 @cindex agent expiry
18565 @cindex Gnus agent expiry
18568 The Agent back end, @code{nnagent}, doesn't handle expiry. Well, at
18569 least it doesn't handle it like other back ends. Instead, there are
18570 special @code{gnus-agent-expire} and @code{gnus-agent-expire-group}
18571 commands that will expire all read articles that are older than
18572 @code{gnus-agent-expire-days} days. They can be run whenever you feel
18573 that you're running out of space. Neither are particularly fast or
18574 efficient, and it's not a particularly good idea to interrupt them (with
18575 @kbd{C-g} or anything else) once you've started one of them.
18577 Note that other functions, e.g. @code{gnus-request-expire-articles},
18578 might run @code{gnus-agent-expire} for you to keep the agent
18579 synchronized with the group.
18581 The agent parameter @code{agent-enable-expiration} may be used to
18582 prevent expiration in selected groups.
18584 @vindex gnus-agent-expire-all
18585 If @code{gnus-agent-expire-all} is non-@code{nil}, the agent
18586 expiration commands will expire all articles---unread, read, ticked
18587 and dormant. If @code{nil} (which is the default), only read articles
18588 are eligible for expiry, and unread, ticked and dormant articles will
18589 be kept indefinitely.
18591 If you find that some articles eligible for expiry are never expired,
18592 perhaps some Gnus Agent files are corrupted. There's are special
18593 commands, @code{gnus-agent-regenerate} and
18594 @code{gnus-agent-regenerate-group}, to fix possible problems.
18596 @node Agent Regeneration
18597 @subsection Agent Regeneration
18599 @cindex agent regeneration
18600 @cindex Gnus agent regeneration
18601 @cindex regeneration
18603 The local data structures used by @code{nnagent} may become corrupted
18604 due to certain exceptional conditions. When this happens,
18605 @code{nnagent} functionality may degrade or even fail. The solution
18606 to this problem is to repair the local data structures by removing all
18607 internal inconsistencies.
18609 For example, if your connection to your server is lost while
18610 downloaded articles into the agent, the local data structures will not
18611 know about articles successfully downloaded prior to the connection
18612 failure. Running @code{gnus-agent-regenerate} or
18613 @code{gnus-agent-regenerate-group} will update the data structures
18614 such that you don't need to download these articles a second time.
18616 @findex gnus-agent-regenerate
18617 @kindex M-x gnus-agent-regenerate
18618 The command @code{gnus-agent-regenerate} will perform
18619 @code{gnus-agent-regenerate-group} on every agentized group. While
18620 you can run @code{gnus-agent-regenerate} in any buffer, it is strongly
18621 recommended that you first close all summary buffers.
18623 @findex gnus-agent-regenerate-group
18624 @kindex M-x gnus-agent-regenerate-group
18625 The command @code{gnus-agent-regenerate-group} uses the local copies
18626 of individual articles to repair the local @acronym{NOV}(header) database. It
18627 then updates the internal data structures that document which articles
18628 are stored locally. An optional argument will mark articles in the
18631 @node Agent and IMAP
18632 @subsection Agent and IMAP
18634 The Agent works with any Gnus back end, including nnimap. However,
18635 since there are some conceptual differences between @acronym{NNTP} and
18636 @acronym{IMAP}, this section (should) provide you with some information to
18637 make Gnus Agent work smoother as a @acronym{IMAP} Disconnected Mode client.
18639 The first thing to keep in mind is that all flags (read, ticked, etc)
18640 are kept on the @acronym{IMAP} server, rather than in @file{.newsrc} as is the
18641 case for nntp. Thus Gnus need to remember flag changes when
18642 disconnected, and synchronize these flags when you plug back in.
18644 Gnus keeps track of flag changes when reading nnimap groups under the
18645 Agent. When you plug back in, Gnus will check if you have any changed
18646 any flags and ask if you wish to synchronize these with the server.
18647 The behavior is customizable by @code{gnus-agent-synchronize-flags}.
18649 @vindex gnus-agent-synchronize-flags
18650 If @code{gnus-agent-synchronize-flags} is @code{nil}, the Agent will
18651 never automatically synchronize flags. If it is @code{ask}, which is
18652 the default, the Agent will check if you made any changes and if so
18653 ask if you wish to synchronize these when you re-connect. If it has
18654 any other value, all flags will be synchronized automatically.
18656 If you do not wish to synchronize flags automatically when you
18657 re-connect, you can do it manually with the
18658 @code{gnus-agent-synchronize-flags} command that is bound to @kbd{J Y}
18659 in the group buffer.
18661 Some things are currently not implemented in the Agent that you'd might
18662 expect from a disconnected @acronym{IMAP} client, including:
18667 Copying/moving articles into nnimap groups when unplugged.
18670 Creating/deleting nnimap groups when unplugged.
18674 Technical note: the synchronization algorithm does not work by ``pushing''
18675 all local flags to the server, but rather incrementally update the
18676 server view of flags by changing only those flags that were changed by
18677 the user. Thus, if you set one flag on an article, quit the group and
18678 re-select the group and remove the flag; the flag will be set and
18679 removed from the server when you ``synchronize''. The queued flag
18680 operations can be found in the per-server @code{flags} file in the Agent
18681 directory. It's emptied when you synchronize flags.
18684 @node Outgoing Messages
18685 @subsection Outgoing Messages
18687 By default, when Gnus is unplugged, all outgoing messages (both mail
18688 and news) are stored in the draft group ``queue'' (@pxref{Drafts}).
18689 You can view them there after posting, and edit them at will.
18691 You can control the circumstances under which outgoing mail is queued
18692 (see @code{gnus-agent-queue-mail}, @pxref{Agent Variables}). Outgoing
18693 news is always queued when Gnus is unplugged, and never otherwise.
18695 You can send the messages either from the draft group with the special
18696 commands available there, or you can use the @kbd{J S} command in the
18697 group buffer to send all the sendable messages in the draft group.
18698 Posting news will only work when Gnus is plugged, but you can send
18701 If sending mail while unplugged does not work for you and you worry
18702 about hitting @kbd{J S} by accident when unplugged, you can have Gnus
18703 ask you to confirm your action (see
18704 @code{gnus-agent-prompt-send-queue}, @pxref{Agent Variables}).
18706 @node Agent Variables
18707 @subsection Agent Variables
18712 Is the agent enabled? The default is @code{t}. When first enabled,
18713 the agent will use @code{gnus-agent-auto-agentize-methods} to
18714 automatically mark some back ends as agentized. You may change which
18715 back ends are agentized using the agent commands in the server buffer.
18717 To enter the server buffer, use the @kbd{^}
18718 (@code{gnus-group-enter-server-mode}) command in the group buffer.
18721 @item gnus-agent-directory
18722 @vindex gnus-agent-directory
18723 Where the Gnus Agent will store its files. The default is
18724 @file{~/News/agent/}.
18726 @item gnus-agent-handle-level
18727 @vindex gnus-agent-handle-level
18728 Groups on levels (@pxref{Group Levels}) higher than this variable will
18729 be ignored by the Agent. The default is @code{gnus-level-subscribed},
18730 which means that only subscribed group will be considered by the Agent
18733 @item gnus-agent-plugged-hook
18734 @vindex gnus-agent-plugged-hook
18735 Hook run when connecting to the network.
18737 @item gnus-agent-unplugged-hook
18738 @vindex gnus-agent-unplugged-hook
18739 Hook run when disconnecting from the network.
18741 @item gnus-agent-fetched-hook
18742 @vindex gnus-agent-fetched-hook
18743 Hook run when finished fetching articles.
18745 @item gnus-agent-cache
18746 @vindex gnus-agent-cache
18747 Variable to control whether use the locally stored @acronym{NOV} and
18748 articles when plugged, e.g. essentially using the Agent as a cache.
18749 The default is non-@code{nil}, which means to use the Agent as a cache.
18751 @item gnus-agent-go-online
18752 @vindex gnus-agent-go-online
18753 If @code{gnus-agent-go-online} is @code{nil}, the Agent will never
18754 automatically switch offline servers into online status. If it is
18755 @code{ask}, the default, the Agent will ask if you wish to switch
18756 offline servers into online status when you re-connect. If it has any
18757 other value, all offline servers will be automatically switched into
18760 @item gnus-agent-mark-unread-after-downloaded
18761 @vindex gnus-agent-mark-unread-after-downloaded
18762 If @code{gnus-agent-mark-unread-after-downloaded} is non-@code{nil},
18763 mark articles as unread after downloading. This is usually a safe
18764 thing to do as the newly downloaded article has obviously not been
18765 read. The default is t.
18767 @item gnus-agent-consider-all-articles
18768 @vindex gnus-agent-consider-all-articles
18769 If @code{gnus-agent-consider-all-articles} is non-@code{nil}, the
18770 agent will let the agent predicate decide whether articles need to be
18771 downloaded or not, for all articles. When @code{nil}, the default,
18772 the agent will only let the predicate decide whether unread articles
18773 are downloaded or not. If you enable this, you may also want to look
18774 into the agent expiry settings (@pxref{Category Variables}), so that
18775 the agent doesn't download articles which the agent will later expire,
18776 over and over again.
18778 @item gnus-agent-max-fetch-size
18779 @vindex gnus-agent-max-fetch-size
18780 The agent fetches articles into a temporary buffer prior to parsing
18781 them into individual files. To avoid exceeding the max. buffer size,
18782 the agent alternates between fetching and parsing until all articles
18783 have been fetched. @code{gnus-agent-max-fetch-size} provides a size
18784 limit to control how often the cycling occurs. A large value improves
18785 performance. A small value minimizes the time lost should the
18786 connection be lost while fetching (You may need to run
18787 @code{gnus-agent-regenerate-group} to update the group's state.
18788 However, all articles parsed prior to loosing the connection will be
18789 available while unplugged). The default is 10M so it is unusual to
18792 @item gnus-server-unopen-status
18793 @vindex gnus-server-unopen-status
18794 Perhaps not an Agent variable, but closely related to the Agent, this
18795 variable says what will happen if Gnus cannot open a server. If the
18796 Agent is enabled, the default, @code{nil}, makes Gnus ask the user
18797 whether to deny the server or whether to unplug the agent. If the
18798 Agent is disabled, Gnus always simply deny the server. Other choices
18799 for this variable include @code{denied} and @code{offline} the latter
18800 is only valid if the Agent is used.
18802 @item gnus-auto-goto-ignores
18803 @vindex gnus-auto-goto-ignores
18804 Another variable that isn't an Agent variable, yet so closely related
18805 that most will look for it here, this variable tells the summary
18806 buffer how to maneuver around undownloaded (only headers stored in the
18807 agent) and unfetched (neither article nor headers stored) articles.
18809 The legal values are @code{nil} (maneuver to any article),
18810 @code{undownloaded} (maneuvering while unplugged ignores articles that
18811 have not been fetched), @code{always-undownloaded} (maneuvering always
18812 ignores articles that have not been fetched), @code{unfetched}
18813 (maneuvering ignores articles whose headers have not been fetched).
18815 @item gnus-agent-queue-mail
18816 @vindex gnus-agent-queue-mail
18817 When @code{gnus-agent-queue-mail} is @code{always}, Gnus will always
18818 queue mail rather than sending it straight away. When @code{t}, Gnus
18819 will queue mail when unplugged only. When @code{nil}, never queue
18820 mail. The default is @code{t}.
18822 @item gnus-agent-prompt-send-queue
18823 @vindex gnus-agent-prompt-send-queue
18824 When @code{gnus-agent-prompt-send-queue} is non-@code{nil} Gnus will
18825 prompt you to confirm that you really wish to proceed if you hit
18826 @kbd{J S} while unplugged. The default is @code{nil}.
18828 @item gnus-agent-auto-agentize-methods
18829 @vindex gnus-agent-auto-agentize-methods
18830 If you have never used the Agent before (or more technically, if
18831 @file{~/News/agent/lib/servers} does not exist), Gnus will
18832 automatically agentize a few servers for you. This variable control
18833 which back ends should be auto-agentized. It is typically only useful
18834 to agentize remote back ends. The auto-agentizing has the same effect
18835 as running @kbd{J a} on the servers (@pxref{Server Agent Commands}).
18836 If the file exist, you must manage the servers manually by adding or
18837 removing them, this variable is only applicable the first time you
18838 start Gnus. The default is @samp{(nntp nnimap)}.
18843 @node Example Setup
18844 @subsection Example Setup
18846 If you don't want to read this manual, and you have a fairly standard
18847 setup, you may be able to use something like the following as your
18848 @file{~/.gnus.el} file to get started.
18851 ;;; @r{Define how Gnus is to fetch news. We do this over @acronym{NNTP}}
18852 ;;; @r{from your ISP's server.}
18853 (setq gnus-select-method '(nntp "news.your-isp.com"))
18855 ;;; @r{Define how Gnus is to read your mail. We read mail from}
18856 ;;; @r{your ISP's @acronym{POP} server.}
18857 (setq mail-sources '((pop :server "pop.your-isp.com")))
18859 ;;; @r{Say how Gnus is to store the mail. We use nnml groups.}
18860 (setq gnus-secondary-select-methods '((nnml "")))
18862 ;;; @r{Make Gnus into an offline newsreader.}
18863 ;;; (gnus-agentize) ; @r{The obsolete setting.}
18864 ;;; (setq gnus-agent t) ; @r{Now the default.}
18867 That should be it, basically. Put that in your @file{~/.gnus.el} file,
18868 edit to suit your needs, start up PPP (or whatever), and type @kbd{M-x
18871 If this is the first time you've run Gnus, you will be subscribed
18872 automatically to a few default newsgroups. You'll probably want to
18873 subscribe to more groups, and to do that, you have to query the
18874 @acronym{NNTP} server for a complete list of groups with the @kbd{A A}
18875 command. This usually takes quite a while, but you only have to do it
18878 After reading and parsing a while, you'll be presented with a list of
18879 groups. Subscribe to the ones you want to read with the @kbd{u}
18880 command. @kbd{l} to make all the killed groups disappear after you've
18881 subscribe to all the groups you want to read. (@kbd{A k} will bring
18882 back all the killed groups.)
18884 You can now read the groups at once, or you can download the articles
18885 with the @kbd{J s} command. And then read the rest of this manual to
18886 find out which of the other gazillion things you want to customize.
18889 @node Batching Agents
18890 @subsection Batching Agents
18891 @findex gnus-agent-batch
18893 Having the Gnus Agent fetch articles (and post whatever messages you've
18894 written) is quite easy once you've gotten things set up properly. The
18895 following shell script will do everything that is necessary:
18897 You can run a complete batch command from the command line with the
18898 following incantation:
18902 emacs -batch -l ~/.emacs -l ~/.gnus.el gnus-agent-batch >/dev/null 2>&1
18906 @node Agent Caveats
18907 @subsection Agent Caveats
18909 The Gnus Agent doesn't seem to work like most other offline
18910 newsreaders. Here are some common questions that some imaginary people
18914 @item If I read an article while plugged, do they get entered into the Agent?
18916 @strong{No}. If you want this behaviour, add
18917 @code{gnus-agent-fetch-selected-article} to
18918 @code{gnus-select-article-hook}.
18920 @item If I read an article while plugged, and the article already exists in
18921 the Agent, will it get downloaded once more?
18923 @strong{No}, unless @code{gnus-agent-cache} is @code{nil}.
18927 In short, when Gnus is unplugged, it only looks into the locally stored
18928 articles; when it's plugged, it talks to your ISP and may also use the
18929 locally stored articles.
18936 Other people use @dfn{kill files}, but we here at Gnus Towers like
18937 scoring better than killing, so we'd rather switch than fight. They do
18938 something completely different as well, so sit up straight and pay
18941 @vindex gnus-summary-mark-below
18942 All articles have a default score (@code{gnus-summary-default-score}),
18943 which is 0 by default. This score may be raised or lowered either
18944 interactively or by score files. Articles that have a score lower than
18945 @code{gnus-summary-mark-below} are marked as read.
18947 Gnus will read any @dfn{score files} that apply to the current group
18948 before generating the summary buffer.
18950 There are several commands in the summary buffer that insert score
18951 entries based on the current article. You can, for instance, ask Gnus to
18952 lower or increase the score of all articles with a certain subject.
18954 There are two sorts of scoring entries: Permanent and temporary.
18955 Temporary score entries are self-expiring entries. Any entries that are
18956 temporary and have not been used for, say, a week, will be removed
18957 silently to help keep the sizes of the score files down.
18960 * Summary Score Commands:: Adding score entries for the current group.
18961 * Group Score Commands:: General score commands.
18962 * Score Variables:: Customize your scoring. (My, what terminology).
18963 * Score File Format:: What a score file may contain.
18964 * Score File Editing:: You can edit score files by hand as well.
18965 * Adaptive Scoring:: Big Sister Gnus knows what you read.
18966 * Home Score File:: How to say where new score entries are to go.
18967 * Followups To Yourself:: Having Gnus notice when people answer you.
18968 * Scoring On Other Headers:: Scoring on non-standard headers.
18969 * Scoring Tips:: How to score effectively.
18970 * Reverse Scoring:: That problem child of old is not problem.
18971 * Global Score Files:: Earth-spanning, ear-splitting score files.
18972 * Kill Files:: They are still here, but they can be ignored.
18973 * Converting Kill Files:: Translating kill files to score files.
18974 * Advanced Scoring:: Using logical expressions to build score rules.
18975 * Score Decays:: It can be useful to let scores wither away.
18979 @node Summary Score Commands
18980 @section Summary Score Commands
18981 @cindex score commands
18983 The score commands that alter score entries do not actually modify real
18984 score files. That would be too inefficient. Gnus maintains a cache of
18985 previously loaded score files, one of which is considered the
18986 @dfn{current score file alist}. The score commands simply insert
18987 entries into this list, and upon group exit, this list is saved.
18989 The current score file is by default the group's local score file, even
18990 if no such score file actually exists. To insert score commands into
18991 some other score file (e.g. @file{all.SCORE}), you must first make this
18992 score file the current one.
18994 General score commands that don't actually change the score file:
18999 @kindex V s (Summary)
19000 @findex gnus-summary-set-score
19001 Set the score of the current article (@code{gnus-summary-set-score}).
19004 @kindex V S (Summary)
19005 @findex gnus-summary-current-score
19006 Display the score of the current article
19007 (@code{gnus-summary-current-score}).
19010 @kindex V t (Summary)
19011 @findex gnus-score-find-trace
19012 Display all score rules that have been used on the current article
19013 (@code{gnus-score-find-trace}). In the @code{*Score Trace*} buffer, you
19014 may type @kbd{e} to edit score file corresponding to the score rule on
19015 current line and @kbd{f} to format (@code{gnus-score-pretty-print}) the
19016 score file and edit it.
19019 @kindex V w (Summary)
19020 @findex gnus-score-find-favourite-words
19021 List words used in scoring (@code{gnus-score-find-favourite-words}).
19024 @kindex V R (Summary)
19025 @findex gnus-summary-rescore
19026 Run the current summary through the scoring process
19027 (@code{gnus-summary-rescore}). This might be useful if you're playing
19028 around with your score files behind Gnus' back and want to see the
19029 effect you're having.
19032 @kindex V c (Summary)
19033 @findex gnus-score-change-score-file
19034 Make a different score file the current
19035 (@code{gnus-score-change-score-file}).
19038 @kindex V e (Summary)
19039 @findex gnus-score-edit-current-scores
19040 Edit the current score file (@code{gnus-score-edit-current-scores}).
19041 You will be popped into a @code{gnus-score-mode} buffer (@pxref{Score
19045 @kindex V f (Summary)
19046 @findex gnus-score-edit-file
19047 Edit a score file and make this score file the current one
19048 (@code{gnus-score-edit-file}).
19051 @kindex V F (Summary)
19052 @findex gnus-score-flush-cache
19053 Flush the score cache (@code{gnus-score-flush-cache}). This is useful
19054 after editing score files.
19057 @kindex V C (Summary)
19058 @findex gnus-score-customize
19059 Customize a score file in a visually pleasing manner
19060 (@code{gnus-score-customize}).
19064 The rest of these commands modify the local score file.
19069 @kindex V m (Summary)
19070 @findex gnus-score-set-mark-below
19071 Prompt for a score, and mark all articles with a score below this as
19072 read (@code{gnus-score-set-mark-below}).
19075 @kindex V x (Summary)
19076 @findex gnus-score-set-expunge-below
19077 Prompt for a score, and add a score rule to the current score file to
19078 expunge all articles below this score
19079 (@code{gnus-score-set-expunge-below}).
19082 The keystrokes for actually making score entries follow a very regular
19083 pattern, so there's no need to list all the commands. (Hundreds of
19086 @findex gnus-summary-increase-score
19087 @findex gnus-summary-lower-score
19091 The first key is either @kbd{I} (upper case i) for increasing the score
19092 or @kbd{L} for lowering the score.
19094 The second key says what header you want to score on. The following
19095 keys are available:
19099 Score on the author name.
19102 Score on the subject line.
19105 Score on the @code{Xref} line---i.e., the cross-posting line.
19108 Score on the @code{References} line.
19114 Score on the number of lines.
19117 Score on the @code{Message-ID} header.
19120 Score on an ``extra'' header, that is, one of those in gnus-extra-headers,
19121 if your @acronym{NNTP} server tracks additional header data in overviews.
19124 Score on followups---this matches the author name, and adds scores to
19125 the followups to this author. (Using this key leads to the creation of
19126 @file{ADAPT} files.)
19135 Score on thread. (Using this key leads to the creation of @file{ADAPT}
19141 The third key is the match type. Which match types are valid depends on
19142 what headers you are scoring on.
19154 Substring matching.
19157 Fuzzy matching (@pxref{Fuzzy Matching}).
19186 Greater than number.
19191 The fourth and usually final key says whether this is a temporary (i.e.,
19192 expiring) score entry, or a permanent (i.e., non-expiring) score entry,
19193 or whether it is to be done immediately, without adding to the score
19198 Temporary score entry.
19201 Permanent score entry.
19204 Immediately scoring.
19208 If you are scoring on `e' (extra) headers, you will then be prompted for
19209 the header name on which you wish to score. This must be a header named
19210 in gnus-extra-headers, and @samp{TAB} completion is available.
19214 So, let's say you want to increase the score on the current author with
19215 exact matching permanently: @kbd{I a e p}. If you want to lower the
19216 score based on the subject line, using substring matching, and make a
19217 temporary score entry: @kbd{L s s t}. Pretty easy.
19219 To make things a bit more complicated, there are shortcuts. If you use
19220 a capital letter on either the second or third keys, Gnus will use
19221 defaults for the remaining one or two keystrokes. The defaults are
19222 ``substring'' and ``temporary''. So @kbd{I A} is the same as @kbd{I a s
19223 t}, and @kbd{I a R} is the same as @kbd{I a r t}.
19225 These functions take both the numerical prefix and the symbolic prefix
19226 (@pxref{Symbolic Prefixes}). A numerical prefix says how much to lower
19227 (or increase) the score of the article. A symbolic prefix of @code{a}
19228 says to use the @file{all.SCORE} file for the command instead of the
19229 current score file.
19231 @vindex gnus-score-mimic-keymap
19232 The @code{gnus-score-mimic-keymap} says whether these commands will
19233 pretend they are keymaps or not.
19236 @node Group Score Commands
19237 @section Group Score Commands
19238 @cindex group score commands
19240 There aren't many of these as yet, I'm afraid.
19245 @kindex W e (Group)
19246 @findex gnus-score-edit-all-score
19247 Edit the apply-to-all-groups all.SCORE file. You will be popped into
19248 a @code{gnus-score-mode} buffer (@pxref{Score File Editing}).
19251 @kindex W f (Group)
19252 @findex gnus-score-flush-cache
19253 Gnus maintains a cache of score alists to avoid having to reload them
19254 all the time. This command will flush the cache
19255 (@code{gnus-score-flush-cache}).
19259 You can do scoring from the command line by saying something like:
19261 @findex gnus-batch-score
19262 @cindex batch scoring
19264 $ emacs -batch -l ~/.emacs -l ~/.gnus.el -f gnus-batch-score
19268 @node Score Variables
19269 @section Score Variables
19270 @cindex score variables
19274 @item gnus-use-scoring
19275 @vindex gnus-use-scoring
19276 If @code{nil}, Gnus will not check for score files, and will not, in
19277 general, do any score-related work. This is @code{t} by default.
19279 @item gnus-kill-killed
19280 @vindex gnus-kill-killed
19281 If this variable is @code{nil}, Gnus will never apply score files to
19282 articles that have already been through the kill process. While this
19283 may save you lots of time, it also means that if you apply a kill file
19284 to a group, and then change the kill file and want to run it over you
19285 group again to kill more articles, it won't work. You have to set this
19286 variable to @code{t} to do that. (It is @code{t} by default.)
19288 @item gnus-kill-files-directory
19289 @vindex gnus-kill-files-directory
19290 All kill and score files will be stored in this directory, which is
19291 initialized from the @env{SAVEDIR} environment variable by default.
19292 This is @file{~/News/} by default.
19294 @item gnus-score-file-suffix
19295 @vindex gnus-score-file-suffix
19296 Suffix to add to the group name to arrive at the score file name
19297 (@file{SCORE} by default.)
19299 @item gnus-score-uncacheable-files
19300 @vindex gnus-score-uncacheable-files
19301 @cindex score cache
19302 All score files are normally cached to avoid excessive re-loading of
19303 score files. However, if this might make your Emacs grow big and
19304 bloated, so this regexp can be used to weed out score files unlikely
19305 to be needed again. It would be a bad idea to deny caching of
19306 @file{all.SCORE}, while it might be a good idea to not cache
19307 @file{comp.infosystems.www.authoring.misc.ADAPT}. In fact, this
19308 variable is @samp{ADAPT$} by default, so no adaptive score files will
19311 @item gnus-save-score
19312 @vindex gnus-save-score
19313 If you have really complicated score files, and do lots of batch
19314 scoring, then you might set this variable to @code{t}. This will make
19315 Gnus save the scores into the @file{.newsrc.eld} file.
19317 If you do not set this to @code{t}, then manual scores (like those set
19318 with @kbd{V s} (@code{gnus-summary-set-score})) will not be preserved
19319 across group visits.
19321 @item gnus-score-interactive-default-score
19322 @vindex gnus-score-interactive-default-score
19323 Score used by all the interactive raise/lower commands to raise/lower
19324 score with. Default is 1000, which may seem excessive, but this is to
19325 ensure that the adaptive scoring scheme gets enough room to play with.
19326 We don't want the small changes from the adaptive scoring to overwrite
19327 manually entered data.
19329 @item gnus-summary-default-score
19330 @vindex gnus-summary-default-score
19331 Default score of an article, which is 0 by default.
19333 @item gnus-summary-expunge-below
19334 @vindex gnus-summary-expunge-below
19335 Don't display the summary lines of articles that have scores lower than
19336 this variable. This is @code{nil} by default, which means that no
19337 articles will be hidden. This variable is local to the summary buffers,
19338 and has to be set from @code{gnus-summary-mode-hook}.
19340 @item gnus-score-over-mark
19341 @vindex gnus-score-over-mark
19342 Mark (in the third column) used for articles with a score over the
19343 default. Default is @samp{+}.
19345 @item gnus-score-below-mark
19346 @vindex gnus-score-below-mark
19347 Mark (in the third column) used for articles with a score below the
19348 default. Default is @samp{-}.
19350 @item gnus-score-find-score-files-function
19351 @vindex gnus-score-find-score-files-function
19352 Function used to find score files for the current group. This function
19353 is called with the name of the group as the argument.
19355 Predefined functions available are:
19358 @item gnus-score-find-single
19359 @findex gnus-score-find-single
19360 Only apply the group's own score file.
19362 @item gnus-score-find-bnews
19363 @findex gnus-score-find-bnews
19364 Apply all score files that match, using bnews syntax. This is the
19365 default. If the current group is @samp{gnu.emacs.gnus}, for instance,
19366 @file{all.emacs.all.SCORE}, @file{not.alt.all.SCORE} and
19367 @file{gnu.all.SCORE} would all apply. In short, the instances of
19368 @samp{all} in the score file names are translated into @samp{.*}, and
19369 then a regexp match is done.
19371 This means that if you have some score entries that you want to apply to
19372 all groups, then you put those entries in the @file{all.SCORE} file.
19374 The score files are applied in a semi-random order, although Gnus will
19375 try to apply the more general score files before the more specific score
19376 files. It does this by looking at the number of elements in the score
19377 file names---discarding the @samp{all} elements.
19379 @item gnus-score-find-hierarchical
19380 @findex gnus-score-find-hierarchical
19381 Apply all score files from all the parent groups. This means that you
19382 can't have score files like @file{all.SCORE}, but you can have
19383 @file{SCORE}, @file{comp.SCORE} and @file{comp.emacs.SCORE} for each
19387 This variable can also be a list of functions. In that case, all
19388 these functions will be called with the group name as argument, and
19389 all the returned lists of score files will be applied. These
19390 functions can also return lists of lists of score alists directly. In
19391 that case, the functions that return these non-file score alists
19392 should probably be placed before the ``real'' score file functions, to
19393 ensure that the last score file returned is the local score file.
19396 For example, to do hierarchical scoring but use a non-server-specific
19397 overall score file, you could use the value
19399 (list (lambda (group) ("all.SCORE"))
19400 'gnus-score-find-hierarchical)
19403 @item gnus-score-expiry-days
19404 @vindex gnus-score-expiry-days
19405 This variable says how many days should pass before an unused score file
19406 entry is expired. If this variable is @code{nil}, no score file entries
19407 are expired. It's 7 by default.
19409 @item gnus-update-score-entry-dates
19410 @vindex gnus-update-score-entry-dates
19411 If this variable is non-@code{nil}, temporary score entries that have
19412 been triggered (matched) will have their dates updated. (This is how Gnus
19413 controls expiry---all non-matched-entries will become too old while
19414 matched entries will stay fresh and young.) However, if you set this
19415 variable to @code{nil}, even matched entries will grow old and will
19416 have to face that oh-so grim reaper.
19418 @item gnus-score-after-write-file-function
19419 @vindex gnus-score-after-write-file-function
19420 Function called with the name of the score file just written.
19422 @item gnus-score-thread-simplify
19423 @vindex gnus-score-thread-simplify
19424 If this variable is non-@code{nil}, article subjects will be
19425 simplified for subject scoring purposes in the same manner as with
19426 threading---according to the current value of
19427 @code{gnus-simplify-subject-functions}. If the scoring entry uses
19428 @code{substring} or @code{exact} matching, the match will also be
19429 simplified in this manner.
19434 @node Score File Format
19435 @section Score File Format
19436 @cindex score file format
19438 A score file is an @code{emacs-lisp} file that normally contains just a
19439 single form. Casual users are not expected to edit these files;
19440 everything can be changed from the summary buffer.
19442 Anyway, if you'd like to dig into it yourself, here's an example:
19446 ("Lars Ingebrigtsen" -10000)
19448 ("larsi\\|lmi" -50000 nil R))
19450 ("Ding is Badd" nil 728373))
19452 ("alt.politics" -1000 728372 s))
19457 (mark-and-expunge -10)
19461 (files "/hom/larsi/News/gnu.SCORE")
19462 (exclude-files "all.SCORE")
19463 (local (gnus-newsgroup-auto-expire t)
19464 (gnus-summary-make-false-root empty))
19468 This example demonstrates most score file elements. @xref{Advanced
19469 Scoring}, for a different approach.
19471 Even though this looks much like Lisp code, nothing here is actually
19472 @code{eval}ed. The Lisp reader is used to read this form, though, so it
19473 has to be valid syntactically, if not semantically.
19475 Six keys are supported by this alist:
19480 If the key is a string, it is the name of the header to perform the
19481 match on. Scoring can only be performed on these eight headers:
19482 @code{From}, @code{Subject}, @code{References}, @code{Message-ID},
19483 @code{Xref}, @code{Lines}, @code{Chars} and @code{Date}. In addition to
19484 these headers, there are three strings to tell Gnus to fetch the entire
19485 article and do the match on larger parts of the article: @code{Body}
19486 will perform the match on the body of the article, @code{Head} will
19487 perform the match on the head of the article, and @code{All} will
19488 perform the match on the entire article. Note that using any of these
19489 last three keys will slow down group entry @emph{considerably}. The
19490 final ``header'' you can score on is @code{Followup}. These score
19491 entries will result in new score entries being added for all follow-ups
19492 to articles that matches these score entries.
19494 Following this key is an arbitrary number of score entries, where each
19495 score entry has one to four elements.
19499 The first element is the @dfn{match element}. On most headers this will
19500 be a string, but on the Lines and Chars headers, this must be an
19504 If the second element is present, it should be a number---the @dfn{score
19505 element}. This number should be an integer in the neginf to posinf
19506 interval. This number is added to the score of the article if the match
19507 is successful. If this element is not present, the
19508 @code{gnus-score-interactive-default-score} number will be used
19509 instead. This is 1000 by default.
19512 If the third element is present, it should be a number---the @dfn{date
19513 element}. This date says when the last time this score entry matched,
19514 which provides a mechanism for expiring the score entries. It this
19515 element is not present, the score entry is permanent. The date is
19516 represented by the number of days since December 31, 1 BCE.
19519 If the fourth element is present, it should be a symbol---the @dfn{type
19520 element}. This element specifies what function should be used to see
19521 whether this score entry matches the article. What match types that can
19522 be used depends on what header you wish to perform the match on.
19525 @item From, Subject, References, Xref, Message-ID
19526 For most header types, there are the @code{r} and @code{R} (regexp), as
19527 well as @code{s} and @code{S} (substring) types, and @code{e} and
19528 @code{E} (exact match), and @code{w} (word match) types. If this
19529 element is not present, Gnus will assume that substring matching should
19530 be used. @code{R}, @code{S}, and @code{E} differ from the others in
19531 that the matches will be done in a case-sensitive manner. All these
19532 one-letter types are really just abbreviations for the @code{regexp},
19533 @code{string}, @code{exact}, and @code{word} types, which you can use
19534 instead, if you feel like.
19537 Just as for the standard string overview headers, if you are using
19538 gnus-extra-headers, you can score on these headers' values. In this
19539 case, there is a 5th element in the score entry, being the name of the
19540 header to be scored. The following entry is useful in your
19541 @file{all.SCORE} file in case of spam attacks from a single origin
19542 host, if your @acronym{NNTP} server tracks @samp{NNTP-Posting-Host} in
19546 ("111.222.333.444" -1000 nil s
19547 "NNTP-Posting-Host")
19551 These two headers use different match types: @code{<}, @code{>},
19552 @code{=}, @code{>=} and @code{<=}.
19554 These predicates are true if
19557 (PREDICATE HEADER MATCH)
19560 evaluates to non-@code{nil}. For instance, the advanced match
19561 @code{("lines" 4 <)} (@pxref{Advanced Scoring}) will result in the
19568 Or to put it another way: When using @code{<} on @code{Lines} with 4 as
19569 the match, we get the score added if the article has less than 4 lines.
19570 (It's easy to get confused and think it's the other way around. But
19571 it's not. I think.)
19573 When matching on @code{Lines}, be careful because some back ends (like
19574 @code{nndir}) do not generate @code{Lines} header, so every article ends
19575 up being marked as having 0 lines. This can lead to strange results if
19576 you happen to lower score of the articles with few lines.
19579 For the Date header we have three kinda silly match types:
19580 @code{before}, @code{at} and @code{after}. I can't really imagine this
19581 ever being useful, but, like, it would feel kinda silly not to provide
19582 this function. Just in case. You never know. Better safe than sorry.
19583 Once burnt, twice shy. Don't judge a book by its cover. Never not have
19584 sex on a first date. (I have been told that at least one person, and I
19585 quote, ``found this function indispensable'', however.)
19589 A more useful match type is @code{regexp}. With it, you can match the
19590 date string using a regular expression. The date is normalized to
19591 ISO8601 compact format first---@var{YYYYMMDD}@code{T}@var{HHMMSS}. If
19592 you want to match all articles that have been posted on April 1st in
19593 every year, you could use @samp{....0401.........} as a match string,
19594 for instance. (Note that the date is kept in its original time zone, so
19595 this will match articles that were posted when it was April 1st where
19596 the article was posted from. Time zones are such wholesome fun for the
19599 @item Head, Body, All
19600 These three match keys use the same match types as the @code{From} (etc)
19604 This match key is somewhat special, in that it will match the
19605 @code{From} header, and affect the score of not only the matching
19606 articles, but also all followups to the matching articles. This allows
19607 you e.g. increase the score of followups to your own articles, or
19608 decrease the score of followups to the articles of some known
19609 trouble-maker. Uses the same match types as the @code{From} header
19610 uses. (Using this match key will lead to creation of @file{ADAPT}
19614 This match key works along the same lines as the @code{Followup} match
19615 key. If you say that you want to score on a (sub-)thread started by an
19616 article with a @code{Message-ID} @var{x}, then you add a @samp{thread}
19617 match. This will add a new @samp{thread} match for each article that
19618 has @var{x} in its @code{References} header. (These new @samp{thread}
19619 matches will use the @code{Message-ID}s of these matching articles.)
19620 This will ensure that you can raise/lower the score of an entire thread,
19621 even though some articles in the thread may not have complete
19622 @code{References} headers. Note that using this may lead to
19623 undeterministic scores of the articles in the thread. (Using this match
19624 key will lead to creation of @file{ADAPT} files.)
19628 @cindex score file atoms
19630 The value of this entry should be a number. Any articles with a score
19631 lower than this number will be marked as read.
19634 The value of this entry should be a number. Any articles with a score
19635 lower than this number will be removed from the summary buffer.
19637 @item mark-and-expunge
19638 The value of this entry should be a number. Any articles with a score
19639 lower than this number will be marked as read and removed from the
19642 @item thread-mark-and-expunge
19643 The value of this entry should be a number. All articles that belong to
19644 a thread that has a total score below this number will be marked as read
19645 and removed from the summary buffer. @code{gnus-thread-score-function}
19646 says how to compute the total score for a thread.
19649 The value of this entry should be any number of file names. These files
19650 are assumed to be score files as well, and will be loaded the same way
19653 @item exclude-files
19654 The clue of this entry should be any number of files. These files will
19655 not be loaded, even though they would normally be so, for some reason or
19659 The value of this entry will be @code{eval}el. This element will be
19660 ignored when handling global score files.
19663 Read-only score files will not be updated or saved. Global score files
19664 should feature this atom (@pxref{Global Score Files}). (Note:
19665 @dfn{Global} here really means @dfn{global}; not your personal
19666 apply-to-all-groups score files.)
19669 The value of this entry should be a number. Articles that do not have
19670 parents will get this number added to their scores. Imagine you follow
19671 some high-volume newsgroup, like @samp{comp.lang.c}. Most likely you
19672 will only follow a few of the threads, also want to see any new threads.
19674 You can do this with the following two score file entries:
19678 (mark-and-expunge -100)
19681 When you enter the group the first time, you will only see the new
19682 threads. You then raise the score of the threads that you find
19683 interesting (with @kbd{I T} or @kbd{I S}), and ignore (@kbd{C y}) the
19684 rest. Next time you enter the group, you will see new articles in the
19685 interesting threads, plus any new threads.
19687 I.e.---the orphan score atom is for high-volume groups where a few
19688 interesting threads which can't be found automatically by ordinary
19689 scoring rules exist.
19692 This entry controls the adaptive scoring. If it is @code{t}, the
19693 default adaptive scoring rules will be used. If it is @code{ignore}, no
19694 adaptive scoring will be performed on this group. If it is a list, this
19695 list will be used as the adaptive scoring rules. If it isn't present,
19696 or is something other than @code{t} or @code{ignore}, the default
19697 adaptive scoring rules will be used. If you want to use adaptive
19698 scoring on most groups, you'd set @code{gnus-use-adaptive-scoring} to
19699 @code{t}, and insert an @code{(adapt ignore)} in the groups where you do
19700 not want adaptive scoring. If you only want adaptive scoring in a few
19701 groups, you'd set @code{gnus-use-adaptive-scoring} to @code{nil}, and
19702 insert @code{(adapt t)} in the score files of the groups where you want
19706 All adaptive score entries will go to the file named by this entry. It
19707 will also be applied when entering the group. This atom might be handy
19708 if you want to adapt on several groups at once, using the same adaptive
19709 file for a number of groups.
19712 @cindex local variables
19713 The value of this entry should be a list of @code{(@var{var}
19714 @var{value})} pairs. Each @var{var} will be made buffer-local to the
19715 current summary buffer, and set to the value specified. This is a
19716 convenient, if somewhat strange, way of setting variables in some
19717 groups if you don't like hooks much. Note that the @var{value} won't
19722 @node Score File Editing
19723 @section Score File Editing
19725 You normally enter all scoring commands from the summary buffer, but you
19726 might feel the urge to edit them by hand as well, so we've supplied you
19727 with a mode for that.
19729 It's simply a slightly customized @code{emacs-lisp} mode, with these
19730 additional commands:
19735 @kindex C-c C-c (Score)
19736 @findex gnus-score-edit-done
19737 Save the changes you have made and return to the summary buffer
19738 (@code{gnus-score-edit-done}).
19741 @kindex C-c C-d (Score)
19742 @findex gnus-score-edit-insert-date
19743 Insert the current date in numerical format
19744 (@code{gnus-score-edit-insert-date}). This is really the day number, if
19745 you were wondering.
19748 @kindex C-c C-p (Score)
19749 @findex gnus-score-pretty-print
19750 The adaptive score files are saved in an unformatted fashion. If you
19751 intend to read one of these files, you want to @dfn{pretty print} it
19752 first. This command (@code{gnus-score-pretty-print}) does that for
19757 Type @kbd{M-x gnus-score-mode} to use this mode.
19759 @vindex gnus-score-mode-hook
19760 @code{gnus-score-menu-hook} is run in score mode buffers.
19762 In the summary buffer you can use commands like @kbd{V f}, @kbd{V e} and
19763 @kbd{V t} to begin editing score files.
19766 @node Adaptive Scoring
19767 @section Adaptive Scoring
19768 @cindex adaptive scoring
19770 If all this scoring is getting you down, Gnus has a way of making it all
19771 happen automatically---as if by magic. Or rather, as if by artificial
19772 stupidity, to be precise.
19774 @vindex gnus-use-adaptive-scoring
19775 When you read an article, or mark an article as read, or kill an
19776 article, you leave marks behind. On exit from the group, Gnus can sniff
19777 these marks and add score elements depending on what marks it finds.
19778 You turn on this ability by setting @code{gnus-use-adaptive-scoring} to
19779 @code{t} or @code{(line)}. If you want score adaptively on separate
19780 words appearing in the subjects, you should set this variable to
19781 @code{(word)}. If you want to use both adaptive methods, set this
19782 variable to @code{(word line)}.
19784 @vindex gnus-default-adaptive-score-alist
19785 To give you complete control over the scoring process, you can customize
19786 the @code{gnus-default-adaptive-score-alist} variable. For instance, it
19787 might look something like this:
19790 (setq gnus-default-adaptive-score-alist
19791 '((gnus-unread-mark)
19792 (gnus-ticked-mark (from 4))
19793 (gnus-dormant-mark (from 5))
19794 (gnus-del-mark (from -4) (subject -1))
19795 (gnus-read-mark (from 4) (subject 2))
19796 (gnus-expirable-mark (from -1) (subject -1))
19797 (gnus-killed-mark (from -1) (subject -3))
19798 (gnus-kill-file-mark)
19799 (gnus-ancient-mark)
19800 (gnus-low-score-mark)
19801 (gnus-catchup-mark (from -1) (subject -1))))
19804 As you see, each element in this alist has a mark as a key (either a
19805 variable name or a ``real'' mark---a character). Following this key is
19806 a arbitrary number of header/score pairs. If there are no header/score
19807 pairs following the key, no adaptive scoring will be done on articles
19808 that have that key as the article mark. For instance, articles with
19809 @code{gnus-unread-mark} in the example above will not get adaptive score
19812 Each article can have only one mark, so just a single of these rules
19813 will be applied to each article.
19815 To take @code{gnus-del-mark} as an example---this alist says that all
19816 articles that have that mark (i.e., are marked with @samp{e}) will have a
19817 score entry added to lower based on the @code{From} header by -4, and
19818 lowered by @code{Subject} by -1. Change this to fit your prejudices.
19820 If you have marked 10 articles with the same subject with
19821 @code{gnus-del-mark}, the rule for that mark will be applied ten times.
19822 That means that that subject will get a score of ten times -1, which
19823 should be, unless I'm much mistaken, -10.
19825 If you have auto-expirable (mail) groups (@pxref{Expiring Mail}), all
19826 the read articles will be marked with the @samp{E} mark. This'll
19827 probably make adaptive scoring slightly impossible, so auto-expiring and
19828 adaptive scoring doesn't really mix very well.
19830 The headers you can score on are @code{from}, @code{subject},
19831 @code{message-id}, @code{references}, @code{xref}, @code{lines},
19832 @code{chars} and @code{date}. In addition, you can score on
19833 @code{followup}, which will create an adaptive score entry that matches
19834 on the @code{References} header using the @code{Message-ID} of the
19835 current article, thereby matching the following thread.
19837 If you use this scheme, you should set the score file atom @code{mark}
19838 to something small---like -300, perhaps, to avoid having small random
19839 changes result in articles getting marked as read.
19841 After using adaptive scoring for a week or so, Gnus should start to
19842 become properly trained and enhance the authors you like best, and kill
19843 the authors you like least, without you having to say so explicitly.
19845 You can control what groups the adaptive scoring is to be performed on
19846 by using the score files (@pxref{Score File Format}). This will also
19847 let you use different rules in different groups.
19849 @vindex gnus-adaptive-file-suffix
19850 The adaptive score entries will be put into a file where the name is the
19851 group name with @code{gnus-adaptive-file-suffix} appended. The default
19854 @vindex gnus-adaptive-pretty-print
19855 Adaptive score files can get huge and are not meant to be edited by
19856 human hands. If @code{gnus-adaptive-pretty-print} is @code{nil} (the
19857 deafult) those files will not be written in a human readable way.
19859 @vindex gnus-score-exact-adapt-limit
19860 When doing adaptive scoring, substring or fuzzy matching would probably
19861 give you the best results in most cases. However, if the header one
19862 matches is short, the possibility for false positives is great, so if
19863 the length of the match is less than
19864 @code{gnus-score-exact-adapt-limit}, exact matching will be used. If
19865 this variable is @code{nil}, exact matching will always be used to avoid
19868 @vindex gnus-default-adaptive-word-score-alist
19869 As mentioned above, you can adapt either on individual words or entire
19870 headers. If you adapt on words, the
19871 @code{gnus-default-adaptive-word-score-alist} variable says what score
19872 each instance of a word should add given a mark.
19875 (setq gnus-default-adaptive-word-score-alist
19876 `((,gnus-read-mark . 30)
19877 (,gnus-catchup-mark . -10)
19878 (,gnus-killed-mark . -20)
19879 (,gnus-del-mark . -15)))
19882 This is the default value. If you have adaption on words enabled, every
19883 word that appears in subjects of articles marked with
19884 @code{gnus-read-mark} will result in a score rule that increase the
19885 score with 30 points.
19887 @vindex gnus-default-ignored-adaptive-words
19888 @vindex gnus-ignored-adaptive-words
19889 Words that appear in the @code{gnus-default-ignored-adaptive-words} list
19890 will be ignored. If you wish to add more words to be ignored, use the
19891 @code{gnus-ignored-adaptive-words} list instead.
19893 @vindex gnus-adaptive-word-length-limit
19894 Some may feel that short words shouldn't count when doing adaptive
19895 scoring. If so, you may set @code{gnus-adaptive-word-length-limit} to
19896 an integer. Words shorter than this number will be ignored. This
19897 variable defaults to @code{nil}.
19899 @vindex gnus-adaptive-word-syntax-table
19900 When the scoring is done, @code{gnus-adaptive-word-syntax-table} is the
19901 syntax table in effect. It is similar to the standard syntax table, but
19902 it considers numbers to be non-word-constituent characters.
19904 @vindex gnus-adaptive-word-minimum
19905 If @code{gnus-adaptive-word-minimum} is set to a number, the adaptive
19906 word scoring process will never bring down the score of an article to
19907 below this number. The default is @code{nil}.
19909 @vindex gnus-adaptive-word-no-group-words
19910 If @code{gnus-adaptive-word-no-group-words} is set to @code{t}, gnus
19911 won't adaptively word score any of the words in the group name. Useful
19912 for groups like @samp{comp.editors.emacs}, where most of the subject
19913 lines contain the word @samp{emacs}.
19915 After using this scheme for a while, it might be nice to write a
19916 @code{gnus-psychoanalyze-user} command to go through the rules and see
19917 what words you like and what words you don't like. Or perhaps not.
19919 Note that the adaptive word scoring thing is highly experimental and is
19920 likely to change in the future. Initial impressions seem to indicate
19921 that it's totally useless as it stands. Some more work (involving more
19922 rigorous statistical methods) will have to be done to make this useful.
19925 @node Home Score File
19926 @section Home Score File
19928 The score file where new score file entries will go is called the
19929 @dfn{home score file}. This is normally (and by default) the score file
19930 for the group itself. For instance, the home score file for
19931 @samp{gnu.emacs.gnus} is @file{gnu.emacs.gnus.SCORE}.
19933 However, this may not be what you want. It is often convenient to share
19934 a common home score file among many groups---all @samp{emacs} groups
19935 could perhaps use the same home score file.
19937 @vindex gnus-home-score-file
19938 The variable that controls this is @code{gnus-home-score-file}. It can
19943 A string. Then this file will be used as the home score file for all
19947 A function. The result of this function will be used as the home score
19948 file. The function will be called with the name of the group as the
19952 A list. The elements in this list can be:
19956 @code{(@var{regexp} @var{file-name})}. If the @var{regexp} matches the
19957 group name, the @var{file-name} will be used as the home score file.
19960 A function. If the function returns non-@code{nil}, the result will
19961 be used as the home score file.
19964 A string. Use the string as the home score file.
19967 The list will be traversed from the beginning towards the end looking
19972 So, if you want to use just a single score file, you could say:
19975 (setq gnus-home-score-file
19976 "my-total-score-file.SCORE")
19979 If you want to use @file{gnu.SCORE} for all @samp{gnu} groups and
19980 @file{rec.SCORE} for all @samp{rec} groups (and so on), you can say:
19982 @findex gnus-hierarchial-home-score-file
19984 (setq gnus-home-score-file
19985 'gnus-hierarchial-home-score-file)
19988 This is a ready-made function provided for your convenience.
19989 Other functions include
19992 @item gnus-current-home-score-file
19993 @findex gnus-current-home-score-file
19994 Return the ``current'' regular score file. This will make scoring
19995 commands add entry to the ``innermost'' matching score file.
19999 If you want to have one score file for the @samp{emacs} groups and
20000 another for the @samp{comp} groups, while letting all other groups use
20001 their own home score files:
20004 (setq gnus-home-score-file
20005 ;; @r{All groups that match the regexp @code{"\\.emacs"}}
20006 '(("\\.emacs" "emacs.SCORE")
20007 ;; @r{All the comp groups in one score file}
20008 ("^comp" "comp.SCORE")))
20011 @vindex gnus-home-adapt-file
20012 @code{gnus-home-adapt-file} works exactly the same way as
20013 @code{gnus-home-score-file}, but says what the home adaptive score file
20014 is instead. All new adaptive file entries will go into the file
20015 specified by this variable, and the same syntax is allowed.
20017 In addition to using @code{gnus-home-score-file} and
20018 @code{gnus-home-adapt-file}, you can also use group parameters
20019 (@pxref{Group Parameters}) and topic parameters (@pxref{Topic
20020 Parameters}) to achieve much the same. Group and topic parameters take
20021 precedence over this variable.
20024 @node Followups To Yourself
20025 @section Followups To Yourself
20027 Gnus offers two commands for picking out the @code{Message-ID} header in
20028 the current buffer. Gnus will then add a score rule that scores using
20029 this @code{Message-ID} on the @code{References} header of other
20030 articles. This will, in effect, increase the score of all articles that
20031 respond to the article in the current buffer. Quite useful if you want
20032 to easily note when people answer what you've said.
20036 @item gnus-score-followup-article
20037 @findex gnus-score-followup-article
20038 This will add a score to articles that directly follow up your own
20041 @item gnus-score-followup-thread
20042 @findex gnus-score-followup-thread
20043 This will add a score to all articles that appear in a thread ``below''
20047 @vindex message-sent-hook
20048 These two functions are both primarily meant to be used in hooks like
20049 @code{message-sent-hook}, like this:
20051 (add-hook 'message-sent-hook 'gnus-score-followup-thread)
20055 If you look closely at your own @code{Message-ID}, you'll notice that
20056 the first two or three characters are always the same. Here's two of
20060 <x6u3u47icf.fsf@@eyesore.no>
20061 <x6sp9o7ibw.fsf@@eyesore.no>
20064 So ``my'' ident on this machine is @samp{x6}. This can be
20065 exploited---the following rule will raise the score on all followups to
20070 ("<x6[0-9a-z]+\\.fsf\\(_-_\\)?@@.*eyesore\\.no>"
20074 Whether it's the first two or first three characters that are ``yours''
20075 is system-dependent.
20078 @node Scoring On Other Headers
20079 @section Scoring On Other Headers
20080 @cindex scoring on other headers
20082 Gnus is quite fast when scoring the ``traditional''
20083 headers---@samp{From}, @samp{Subject} and so on. However, scoring
20084 other headers requires writing a @code{head} scoring rule, which means
20085 that Gnus has to request every single article from the back end to find
20086 matches. This takes a long time in big groups.
20088 Now, there's not much you can do about this for news groups, but for
20089 mail groups, you have greater control. In @ref{To From Newsgroups},
20090 it's explained in greater detail what this mechanism does, but here's
20091 a cookbook example for @code{nnml} on how to allow scoring on the
20092 @samp{To} and @samp{Cc} headers.
20094 Put the following in your @file{~/.gnus.el} file.
20097 (setq gnus-extra-headers '(To Cc Newsgroups Keywords)
20098 nnmail-extra-headers gnus-extra-headers)
20101 Restart Gnus and rebuild your @code{nnml} overview files with the
20102 @kbd{M-x nnml-generate-nov-databases} command. This will take a long
20103 time if you have much mail.
20105 Now you can score on @samp{To} and @samp{Cc} as ``extra headers'' like
20106 so: @kbd{I e s p To RET <your name> RET}.
20112 @section Scoring Tips
20113 @cindex scoring tips
20119 @cindex scoring crossposts
20120 If you want to lower the score of crossposts, the line to match on is
20121 the @code{Xref} header.
20123 ("xref" (" talk.politics.misc:" -1000))
20126 @item Multiple crossposts
20127 If you want to lower the score of articles that have been crossposted to
20128 more than, say, 3 groups:
20131 ("[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+"
20135 @item Matching on the body
20136 This is generally not a very good idea---it takes a very long time.
20137 Gnus actually has to fetch each individual article from the server. But
20138 you might want to anyway, I guess. Even though there are three match
20139 keys (@code{Head}, @code{Body} and @code{All}), you should choose one
20140 and stick with it in each score file. If you use any two, each article
20141 will be fetched @emph{twice}. If you want to match a bit on the
20142 @code{Head} and a bit on the @code{Body}, just use @code{All} for all
20145 @item Marking as read
20146 You will probably want to mark articles that have scores below a certain
20147 number as read. This is most easily achieved by putting the following
20148 in your @file{all.SCORE} file:
20152 You may also consider doing something similar with @code{expunge}.
20154 @item Negated character classes
20155 If you say stuff like @code{[^abcd]*}, you may get unexpected results.
20156 That will match newlines, which might lead to, well, The Unknown. Say
20157 @code{[^abcd\n]*} instead.
20161 @node Reverse Scoring
20162 @section Reverse Scoring
20163 @cindex reverse scoring
20165 If you want to keep just articles that have @samp{Sex with Emacs} in the
20166 subject header, and expunge all other articles, you could put something
20167 like this in your score file:
20171 ("Sex with Emacs" 2))
20176 So, you raise all articles that match @samp{Sex with Emacs} and mark the
20177 rest as read, and expunge them to boot.
20180 @node Global Score Files
20181 @section Global Score Files
20182 @cindex global score files
20184 Sure, other newsreaders have ``global kill files''. These are usually
20185 nothing more than a single kill file that applies to all groups, stored
20186 in the user's home directory. Bah! Puny, weak newsreaders!
20188 What I'm talking about here are Global Score Files. Score files from
20189 all over the world, from users everywhere, uniting all nations in one
20190 big, happy score file union! Ange-score! New and untested!
20192 @vindex gnus-global-score-files
20193 All you have to do to use other people's score files is to set the
20194 @code{gnus-global-score-files} variable. One entry for each score file,
20195 or each score file directory. Gnus will decide by itself what score
20196 files are applicable to which group.
20198 To use the score file
20199 @file{/ftp@@ftp.gnus.org:/pub/larsi/ding/score/soc.motss.SCORE} and
20200 all score files in the @file{/ftp@@ftp.some-where:/pub/score} directory,
20204 (setq gnus-global-score-files
20205 '("/ftp@@ftp.gnus.org:/pub/larsi/ding/score/soc.motss.SCORE"
20206 "/ftp@@ftp.some-where:/pub/score/"))
20209 @findex gnus-score-search-global-directories
20211 Simple, eh? Directory names must end with a @samp{/}. These
20212 directories are typically scanned only once during each Gnus session.
20213 If you feel the need to manually re-scan the remote directories, you can
20214 use the @code{gnus-score-search-global-directories} command.
20216 Note that, at present, using this option will slow down group entry
20217 somewhat. (That is---a lot.)
20219 If you want to start maintaining score files for other people to use,
20220 just put your score file up for anonymous ftp and announce it to the
20221 world. Become a retro-moderator! Participate in the retro-moderator
20222 wars sure to ensue, where retro-moderators battle it out for the
20223 sympathy of the people, luring them to use their score files on false
20224 premises! Yay! The net is saved!
20226 Here are some tips for the would-be retro-moderator, off the top of my
20232 Articles heavily crossposted are probably junk.
20234 To lower a single inappropriate article, lower by @code{Message-ID}.
20236 Particularly brilliant authors can be raised on a permanent basis.
20238 Authors that repeatedly post off-charter for the group can safely be
20239 lowered out of existence.
20241 Set the @code{mark} and @code{expunge} atoms to obliterate the nastiest
20242 articles completely.
20245 Use expiring score entries to keep the size of the file down. You
20246 should probably have a long expiry period, though, as some sites keep
20247 old articles for a long time.
20250 @dots{} I wonder whether other newsreaders will support global score files
20251 in the future. @emph{Snicker}. Yup, any day now, newsreaders like Blue
20252 Wave, xrn and 1stReader are bound to implement scoring. Should we start
20253 holding our breath yet?
20257 @section Kill Files
20260 Gnus still supports those pesky old kill files. In fact, the kill file
20261 entries can now be expiring, which is something I wrote before Daniel
20262 Quinlan thought of doing score files, so I've left the code in there.
20264 In short, kill processing is a lot slower (and I do mean @emph{a lot})
20265 than score processing, so it might be a good idea to rewrite your kill
20266 files into score files.
20268 Anyway, a kill file is a normal @code{emacs-lisp} file. You can put any
20269 forms into this file, which means that you can use kill files as some
20270 sort of primitive hook function to be run on group entry, even though
20271 that isn't a very good idea.
20273 Normal kill files look like this:
20276 (gnus-kill "From" "Lars Ingebrigtsen")
20277 (gnus-kill "Subject" "ding")
20281 This will mark every article written by me as read, and remove the
20282 marked articles from the summary buffer. Very useful, you'll agree.
20284 Other programs use a totally different kill file syntax. If Gnus
20285 encounters what looks like a @code{rn} kill file, it will take a stab at
20288 Two summary functions for editing a @sc{gnus} kill file:
20293 @kindex M-k (Summary)
20294 @findex gnus-summary-edit-local-kill
20295 Edit this group's kill file (@code{gnus-summary-edit-local-kill}).
20298 @kindex M-K (Summary)
20299 @findex gnus-summary-edit-global-kill
20300 Edit the general kill file (@code{gnus-summary-edit-global-kill}).
20303 Two group mode functions for editing the kill files:
20308 @kindex M-k (Group)
20309 @findex gnus-group-edit-local-kill
20310 Edit this group's kill file (@code{gnus-group-edit-local-kill}).
20313 @kindex M-K (Group)
20314 @findex gnus-group-edit-global-kill
20315 Edit the general kill file (@code{gnus-group-edit-global-kill}).
20318 Kill file variables:
20321 @item gnus-kill-file-name
20322 @vindex gnus-kill-file-name
20323 A kill file for the group @samp{soc.motss} is normally called
20324 @file{soc.motss.KILL}. The suffix appended to the group name to get
20325 this file name is detailed by the @code{gnus-kill-file-name} variable.
20326 The ``global'' kill file (not in the score file sense of ``global'', of
20327 course) is just called @file{KILL}.
20329 @vindex gnus-kill-save-kill-file
20330 @item gnus-kill-save-kill-file
20331 If this variable is non-@code{nil}, Gnus will save the
20332 kill file after processing, which is necessary if you use expiring
20335 @item gnus-apply-kill-hook
20336 @vindex gnus-apply-kill-hook
20337 @findex gnus-apply-kill-file-unless-scored
20338 @findex gnus-apply-kill-file
20339 A hook called to apply kill files to a group. It is
20340 @code{(gnus-apply-kill-file)} by default. If you want to ignore the
20341 kill file if you have a score file for the same group, you can set this
20342 hook to @code{(gnus-apply-kill-file-unless-scored)}. If you don't want
20343 kill files to be processed, you should set this variable to @code{nil}.
20345 @item gnus-kill-file-mode-hook
20346 @vindex gnus-kill-file-mode-hook
20347 A hook called in kill-file mode buffers.
20352 @node Converting Kill Files
20353 @section Converting Kill Files
20355 @cindex converting kill files
20357 If you have loads of old kill files, you may want to convert them into
20358 score files. If they are ``regular'', you can use
20359 the @file{gnus-kill-to-score.el} package; if not, you'll have to do it
20362 The kill to score conversion package isn't included in Gnus by default.
20363 You can fetch it from
20364 @uref{http://www.stud.ifi.uio.no/~larsi/ding-various/gnus-kill-to-score.el}.
20366 If your old kill files are very complex---if they contain more
20367 non-@code{gnus-kill} forms than not, you'll have to convert them by
20368 hand. Or just let them be as they are. Gnus will still use them as
20372 @node Advanced Scoring
20373 @section Advanced Scoring
20375 Scoring on Subjects and From headers is nice enough, but what if you're
20376 really interested in what a person has to say only when she's talking
20377 about a particular subject? Or what if you really don't want to
20378 read what person A has to say when she's following up to person B, but
20379 want to read what she says when she's following up to person C?
20381 By using advanced scoring rules you may create arbitrarily complex
20385 * Advanced Scoring Syntax:: A definition.
20386 * Advanced Scoring Examples:: What they look like.
20387 * Advanced Scoring Tips:: Getting the most out of it.
20391 @node Advanced Scoring Syntax
20392 @subsection Advanced Scoring Syntax
20394 Ordinary scoring rules have a string as the first element in the rule.
20395 Advanced scoring rules have a list as the first element. The second
20396 element is the score to be applied if the first element evaluated to a
20397 non-@code{nil} value.
20399 These lists may consist of three logical operators, one redirection
20400 operator, and various match operators.
20407 This logical operator will evaluate each of its arguments until it finds
20408 one that evaluates to @code{false}, and then it'll stop. If all arguments
20409 evaluate to @code{true} values, then this operator will return
20414 This logical operator will evaluate each of its arguments until it finds
20415 one that evaluates to @code{true}. If no arguments are @code{true},
20416 then this operator will return @code{false}.
20421 This logical operator only takes a single argument. It returns the
20422 logical negation of the value of its argument.
20426 There is an @dfn{indirection operator} that will make its arguments
20427 apply to the ancestors of the current article being scored. For
20428 instance, @code{1-} will make score rules apply to the parent of the
20429 current article. @code{2-} will make score rules apply to the
20430 grandparent of the current article. Alternatively, you can write
20431 @code{^^}, where the number of @code{^}s (carets) says how far back into
20432 the ancestry you want to go.
20434 Finally, we have the match operators. These are the ones that do the
20435 real work. Match operators are header name strings followed by a match
20436 and a match type. A typical match operator looks like @samp{("from"
20437 "Lars Ingebrigtsen" s)}. The header names are the same as when using
20438 simple scoring, and the match types are also the same.
20441 @node Advanced Scoring Examples
20442 @subsection Advanced Scoring Examples
20444 Please note that the following examples are score file rules. To
20445 make a complete score file from them, surround them with another pair
20448 Let's say you want to increase the score of articles written by Lars
20449 when he's talking about Gnus:
20454 ("from" "Lars Ingebrigtsen")
20455 ("subject" "Gnus"))
20462 When he writes long articles, he sometimes has something nice to say:
20466 ("from" "Lars Ingebrigtsen")
20473 However, when he responds to things written by Reig Eigil Logge, you
20474 really don't want to read what he's written:
20478 ("from" "Lars Ingebrigtsen")
20479 (1- ("from" "Reig Eigir Logge")))
20483 Everybody that follows up Redmondo when he writes about disappearing
20484 socks should have their scores raised, but only when they talk about
20485 white socks. However, when Lars talks about socks, it's usually not
20492 ("from" "redmondo@@.*no" r)
20493 ("body" "disappearing.*socks" t)))
20494 (! ("from" "Lars Ingebrigtsen"))
20495 ("body" "white.*socks"))
20499 The possibilities are endless.
20502 @node Advanced Scoring Tips
20503 @subsection Advanced Scoring Tips
20505 The @code{&} and @code{|} logical operators do short-circuit logic.
20506 That is, they stop processing their arguments when it's clear what the
20507 result of the operation will be. For instance, if one of the arguments
20508 of an @code{&} evaluates to @code{false}, there's no point in evaluating
20509 the rest of the arguments. This means that you should put slow matches
20510 (@samp{body}, @samp{header}) last and quick matches (@samp{from},
20511 @samp{subject}) first.
20513 The indirection arguments (@code{1-} and so on) will make their
20514 arguments work on previous generations of the thread. If you say
20525 Then that means ``score on the from header of the grandparent of the
20526 current article''. An indirection is quite fast, but it's better to say:
20532 ("subject" "Gnus")))
20539 (1- ("from" "Lars"))
20540 (1- ("subject" "Gnus")))
20545 @section Score Decays
20546 @cindex score decays
20549 You may find that your scores have a tendency to grow without
20550 bounds, especially if you're using adaptive scoring. If scores get too
20551 big, they lose all meaning---they simply max out and it's difficult to
20552 use them in any sensible way.
20554 @vindex gnus-decay-scores
20555 @findex gnus-decay-score
20556 @vindex gnus-decay-score-function
20557 Gnus provides a mechanism for decaying scores to help with this problem.
20558 When score files are loaded and @code{gnus-decay-scores} is
20559 non-@code{nil}, Gnus will run the score files through the decaying
20560 mechanism thereby lowering the scores of all non-permanent score rules.
20561 If @code{gnus-decay-scores} is a regexp, only score files matching this
20562 regexp are treated. E.g. you may set it to @samp{\\.ADAPT\\'} if only
20563 @emph{adaptive} score files should be decayed. The decay itself if
20564 performed by the @code{gnus-decay-score-function} function, which is
20565 @code{gnus-decay-score} by default. Here's the definition of that
20569 (defun gnus-decay-score (score)
20570 "Decay SCORE according to `gnus-score-decay-constant'
20571 and `gnus-score-decay-scale'."
20573 (* (if (< score 0) -1 1)
20575 (max gnus-score-decay-constant
20577 gnus-score-decay-scale)))))))
20578 (if (and (featurep 'xemacs)
20579 ;; XEmacs' floor can handle only the floating point
20580 ;; number below the half of the maximum integer.
20581 (> (abs n) (lsh -1 -2)))
20583 (car (split-string (number-to-string n) "\\.")))
20587 @vindex gnus-score-decay-scale
20588 @vindex gnus-score-decay-constant
20589 @code{gnus-score-decay-constant} is 3 by default and
20590 @code{gnus-score-decay-scale} is 0.05. This should cause the following:
20594 Scores between -3 and 3 will be set to 0 when this function is called.
20597 Scores with magnitudes between 3 and 60 will be shrunk by 3.
20600 Scores with magnitudes greater than 60 will be shrunk by 5% of the
20604 If you don't like this decay function, write your own. It is called
20605 with the score to be decayed as its only parameter, and it should return
20606 the new score, which should be an integer.
20608 Gnus will try to decay scores once a day. If you haven't run Gnus for
20609 four days, Gnus will decay the scores four times, for instance.
20614 @include message.texi
20615 @chapter Emacs MIME
20616 @include emacs-mime.texi
20618 @include sieve.texi
20620 @c @include pgg.texi
20622 @c @include sasl.texi
20630 * Process/Prefix:: A convention used by many treatment commands.
20631 * Interactive:: Making Gnus ask you many questions.
20632 * Symbolic Prefixes:: How to supply some Gnus functions with options.
20633 * Formatting Variables:: You can specify what buffers should look like.
20634 * Window Layout:: Configuring the Gnus buffer windows.
20635 * Faces and Fonts:: How to change how faces look.
20636 * Compilation:: How to speed Gnus up.
20637 * Mode Lines:: Displaying information in the mode lines.
20638 * Highlighting and Menus:: Making buffers look all nice and cozy.
20639 * Buttons:: Get tendinitis in ten easy steps!
20640 * Daemons:: Gnus can do things behind your back.
20641 * NoCeM:: How to avoid spam and other fatty foods.
20642 * Undo:: Some actions can be undone.
20643 * Predicate Specifiers:: Specifying predicates.
20644 * Moderation:: What to do if you're a moderator.
20645 * Image Enhancements:: Modern versions of Emacs/XEmacs can display images.
20646 * Fuzzy Matching:: What's the big fuzz?
20647 * Thwarting Email Spam:: A how-to on avoiding unsolicited commercial email.
20648 * Other modes:: Interaction with other modes.
20649 * Various Various:: Things that are really various.
20653 @node Process/Prefix
20654 @section Process/Prefix
20655 @cindex process/prefix convention
20657 Many functions, among them functions for moving, decoding and saving
20658 articles, use what is known as the @dfn{Process/Prefix convention}.
20660 This is a method for figuring out what articles the user wants the
20661 command to be performed on.
20665 If the numeric prefix is N, perform the operation on the next N
20666 articles, starting with the current one. If the numeric prefix is
20667 negative, perform the operation on the previous N articles, starting
20668 with the current one.
20670 @vindex transient-mark-mode
20671 If @code{transient-mark-mode} in non-@code{nil} and the region is
20672 active, all articles in the region will be worked upon.
20674 If there is no numeric prefix, but some articles are marked with the
20675 process mark, perform the operation on the articles marked with
20678 If there is neither a numeric prefix nor any articles marked with the
20679 process mark, just perform the operation on the current article.
20681 Quite simple, really, but it needs to be made clear so that surprises
20684 Commands that react to the process mark will push the current list of
20685 process marked articles onto a stack and will then clear all process
20686 marked articles. You can restore the previous configuration with the
20687 @kbd{M P y} command (@pxref{Setting Process Marks}).
20689 @vindex gnus-summary-goto-unread
20690 One thing that seems to shock & horrify lots of people is that, for
20691 instance, @kbd{3 d} does exactly the same as @kbd{d} @kbd{d} @kbd{d}.
20692 Since each @kbd{d} (which marks the current article as read) by default
20693 goes to the next unread article after marking, this means that @kbd{3 d}
20694 will mark the next three unread articles as read, no matter what the
20695 summary buffer looks like. Set @code{gnus-summary-goto-unread} to
20696 @code{nil} for a more straightforward action.
20698 Many commands do not use the process/prefix convention. All commands
20699 that do explicitly say so in this manual. To apply the process/prefix
20700 convention to commands that do not use it, you can use the @kbd{M-&}
20701 command. For instance, to mark all the articles in the group as
20702 expirable, you could say @kbd{M P b M-& E}.
20706 @section Interactive
20707 @cindex interaction
20711 @item gnus-novice-user
20712 @vindex gnus-novice-user
20713 If this variable is non-@code{nil}, you are either a newcomer to the
20714 World of Usenet, or you are very cautious, which is a nice thing to be,
20715 really. You will be given questions of the type ``Are you sure you want
20716 to do this?'' before doing anything dangerous. This is @code{t} by
20719 @item gnus-expert-user
20720 @vindex gnus-expert-user
20721 If this variable is non-@code{nil}, you will seldom be asked any
20722 questions by Gnus. It will simply assume you know what you're doing, no
20723 matter how strange.
20725 @item gnus-interactive-catchup
20726 @vindex gnus-interactive-catchup
20727 Require confirmation before catching up a group if non-@code{nil}. It
20728 is @code{t} by default.
20730 @item gnus-interactive-exit
20731 @vindex gnus-interactive-exit
20732 Require confirmation before exiting Gnus. This variable is @code{t} by
20737 @node Symbolic Prefixes
20738 @section Symbolic Prefixes
20739 @cindex symbolic prefixes
20741 Quite a lot of Emacs commands react to the (numeric) prefix. For
20742 instance, @kbd{C-u 4 C-f} moves point four characters forward, and
20743 @kbd{C-u 9 0 0 I s s p} adds a permanent @code{Subject} substring score
20744 rule of 900 to the current article.
20746 This is all nice and well, but what if you want to give a command some
20747 additional information? Well, what most commands do is interpret the
20748 ``raw'' prefix in some special way. @kbd{C-u 0 C-x C-s} means that one
20749 doesn't want a backup file to be created when saving the current buffer,
20750 for instance. But what if you want to save without making a backup
20751 file, and you want Emacs to flash lights and play a nice tune at the
20752 same time? You can't, and you're probably perfectly happy that way.
20754 @kindex M-i (Summary)
20755 @findex gnus-symbolic-argument
20756 I'm not, so I've added a second prefix---the @dfn{symbolic prefix}. The
20757 prefix key is @kbd{M-i} (@code{gnus-symbolic-argument}), and the next
20758 character typed in is the value. You can stack as many @kbd{M-i}
20759 prefixes as you want. @kbd{M-i a C-M-u} means ``feed the @kbd{C-M-u}
20760 command the symbolic prefix @code{a}''. @kbd{M-i a M-i b C-M-u} means
20761 ``feed the @kbd{C-M-u} command the symbolic prefixes @code{a} and
20762 @code{b}''. You get the drift.
20764 Typing in symbolic prefixes to commands that don't accept them doesn't
20765 hurt, but it doesn't do any good either. Currently not many Gnus
20766 functions make use of the symbolic prefix.
20768 If you're interested in how Gnus implements this, @pxref{Extended
20772 @node Formatting Variables
20773 @section Formatting Variables
20774 @cindex formatting variables
20776 Throughout this manual you've probably noticed lots of variables called
20777 things like @code{gnus-group-line-format} and
20778 @code{gnus-summary-mode-line-format}. These control how Gnus is to
20779 output lines in the various buffers. There's quite a lot of them.
20780 Fortunately, they all use the same syntax, so there's not that much to
20783 Here's an example format spec (from the group buffer): @samp{%M%S%5y:
20784 %(%g%)\n}. We see that it is indeed extremely ugly, and that there are
20785 lots of percentages everywhere.
20788 * Formatting Basics:: A formatting variable is basically a format string.
20789 * Mode Line Formatting:: Some rules about mode line formatting variables.
20790 * Advanced Formatting:: Modifying output in various ways.
20791 * User-Defined Specs:: Having Gnus call your own functions.
20792 * Formatting Fonts:: Making the formatting look colorful and nice.
20793 * Positioning Point:: Moving point to a position after an operation.
20794 * Tabulation:: Tabulating your output.
20795 * Wide Characters:: Dealing with wide characters.
20798 Currently Gnus uses the following formatting variables:
20799 @code{gnus-group-line-format}, @code{gnus-summary-line-format},
20800 @code{gnus-server-line-format}, @code{gnus-topic-line-format},
20801 @code{gnus-group-mode-line-format},
20802 @code{gnus-summary-mode-line-format},
20803 @code{gnus-article-mode-line-format},
20804 @code{gnus-server-mode-line-format}, and
20805 @code{gnus-summary-pick-line-format}.
20807 All these format variables can also be arbitrary elisp forms. In that
20808 case, they will be @code{eval}ed to insert the required lines.
20810 @kindex M-x gnus-update-format
20811 @findex gnus-update-format
20812 Gnus includes a command to help you while creating your own format
20813 specs. @kbd{M-x gnus-update-format} will @code{eval} the current form,
20814 update the spec in question and pop you to a buffer where you can
20815 examine the resulting Lisp code to be run to generate the line.
20819 @node Formatting Basics
20820 @subsection Formatting Basics
20822 Each @samp{%} element will be replaced by some string or other when the
20823 buffer in question is generated. @samp{%5y} means ``insert the @samp{y}
20824 spec, and pad with spaces to get a 5-character field''.
20826 As with normal C and Emacs Lisp formatting strings, the numerical
20827 modifier between the @samp{%} and the formatting type character will
20828 @dfn{pad} the output so that it is always at least that long.
20829 @samp{%5y} will make the field always (at least) five characters wide by
20830 padding with spaces to the left. If you say @samp{%-5y}, it will pad to
20833 You may also wish to limit the length of the field to protect against
20834 particularly wide values. For that you can say @samp{%4,6y}, which
20835 means that the field will never be more than 6 characters wide and never
20836 less than 4 characters wide.
20838 Also Gnus supports some extended format specifications, such as
20839 @samp{%&user-date;}.
20842 @node Mode Line Formatting
20843 @subsection Mode Line Formatting
20845 Mode line formatting variables (e.g.,
20846 @code{gnus-summary-mode-line-format}) follow the same rules as other,
20847 buffer line oriented formatting variables (@pxref{Formatting Basics})
20848 with the following two differences:
20853 There must be no newline (@samp{\n}) at the end.
20856 The special @samp{%%b} spec can be used to display the buffer name.
20857 Well, it's no spec at all, really---@samp{%%} is just a way to quote
20858 @samp{%} to allow it to pass through the formatting machinery unmangled,
20859 so that Emacs receives @samp{%b}, which is something the Emacs mode line
20860 display interprets to mean ``show the buffer name''. For a full list of
20861 mode line specs Emacs understands, see the documentation of the
20862 @code{mode-line-format} variable.
20867 @node Advanced Formatting
20868 @subsection Advanced Formatting
20870 It is frequently useful to post-process the fields in some way.
20871 Padding, limiting, cutting off parts and suppressing certain values can
20872 be achieved by using @dfn{tilde modifiers}. A typical tilde spec might
20873 look like @samp{%~(cut 3)~(ignore "0")y}.
20875 These are the valid modifiers:
20880 Pad the field to the left with spaces until it reaches the required
20884 Pad the field to the right with spaces until it reaches the required
20889 Cut off characters from the left until it reaches the specified length.
20892 Cut off characters from the right until it reaches the specified
20897 Cut off the specified number of characters from the left.
20900 Cut off the specified number of characters from the right.
20903 Return an empty string if the field is equal to the specified value.
20906 Use the specified form as the field value when the @samp{@@} spec is
20912 "~(form (current-time-string))@@"
20917 Let's take an example. The @samp{%o} spec in the summary mode lines
20918 will return a date in compact ISO8601 format---@samp{19960809T230410}.
20919 This is quite a mouthful, so we want to shave off the century number and
20920 the time, leaving us with a six-character date. That would be
20921 @samp{%~(cut-left 2)~(max-right 6)~(pad 6)o}. (Cutting is done before
20922 maxing, and we need the padding to ensure that the date is never less
20923 than 6 characters to make it look nice in columns.)
20925 Ignoring is done first; then cutting; then maxing; and then as the very
20926 last operation, padding.
20928 @vindex gnus-compile-user-specs
20929 If @code{gnus-compile-user-specs} is set to @code{nil} (@code{t} by
20930 default) with your strong personality, and use a lots of these advanced
20931 thingies, you'll find that Gnus gets quite slow. This can be helped
20932 enormously by running @kbd{M-x gnus-compile} when you are satisfied with
20933 the look of your lines.
20934 @xref{Compilation}.
20937 @node User-Defined Specs
20938 @subsection User-Defined Specs
20940 All the specs allow for inserting user defined specifiers---@samp{u}.
20941 The next character in the format string should be a letter. Gnus
20942 will call the function @code{gnus-user-format-function-}@samp{X}, where
20943 @samp{X} is the letter following @samp{%u}. The function will be passed
20944 a single parameter---what the parameter means depends on what buffer
20945 it's being called from. The function should return a string, which will
20946 be inserted into the buffer just like information from any other
20947 specifier. This function may also be called with dummy values, so it
20948 should protect against that.
20950 Also Gnus supports extended user-defined specs, such as @samp{%u&foo;}.
20951 Gnus will call the function @code{gnus-user-format-function-}@samp{foo}.
20953 You can also use tilde modifiers (@pxref{Advanced Formatting} to achieve
20954 much the same without defining new functions. Here's an example:
20955 @samp{%~(form (count-lines (point-min) (point)))@@}. The form
20956 given here will be evaluated to yield the current line number, and then
20960 @node Formatting Fonts
20961 @subsection Formatting Fonts
20963 There are specs for highlighting, and these are shared by all the format
20964 variables. Text inside the @samp{%(} and @samp{%)} specifiers will get
20965 the special @code{mouse-face} property set, which means that it will be
20966 highlighted (with @code{gnus-mouse-face}) when you put the mouse pointer
20969 Text inside the @samp{%@{} and @samp{%@}} specifiers will have their
20970 normal faces set using @code{gnus-face-0}, which is @code{bold} by
20971 default. If you say @samp{%1@{}, you'll get @code{gnus-face-1} instead,
20972 and so on. Create as many faces as you wish. The same goes for the
20973 @code{mouse-face} specs---you can say @samp{%3(hello%)} to have
20974 @samp{hello} mouse-highlighted with @code{gnus-mouse-face-3}.
20976 Text inside the @samp{%<<} and @samp{%>>} specifiers will get the
20977 special @code{balloon-help} property set to
20978 @code{gnus-balloon-face-0}. If you say @samp{%1<<}, you'll get
20979 @code{gnus-balloon-face-1} and so on. The @code{gnus-balloon-face-*}
20980 variables should be either strings or symbols naming functions that
20981 return a string. When the mouse passes over text with this property
20982 set, a balloon window will appear and display the string. Please
20983 refer to @ref{Tooltips, ,Tooltips, emacs, The Emacs Manual},
20984 (in GNU Emacs) or the doc string of @code{balloon-help-mode} (in
20985 XEmacs) for more information on this. (For technical reasons, the
20986 guillemets have been approximated as @samp{<<} and @samp{>>} in this
20989 Here's an alternative recipe for the group buffer:
20992 ;; @r{Create three face types.}
20993 (setq gnus-face-1 'bold)
20994 (setq gnus-face-3 'italic)
20996 ;; @r{We want the article count to be in}
20997 ;; @r{a bold and green face. So we create}
20998 ;; @r{a new face called @code{my-green-bold}.}
20999 (copy-face 'bold 'my-green-bold)
21000 ;; @r{Set the color.}
21001 (set-face-foreground 'my-green-bold "ForestGreen")
21002 (setq gnus-face-2 'my-green-bold)
21004 ;; @r{Set the new & fancy format.}
21005 (setq gnus-group-line-format
21006 "%M%S%3@{%5y%@}%2[:%] %(%1@{%g%@}%)\n")
21009 I'm sure you'll be able to use this scheme to create totally unreadable
21010 and extremely vulgar displays. Have fun!
21012 Note that the @samp{%(} specs (and friends) do not make any sense on the
21013 mode-line variables.
21015 @node Positioning Point
21016 @subsection Positioning Point
21018 Gnus usually moves point to a pre-defined place on each line in most
21019 buffers. By default, point move to the first colon character on the
21020 line. You can customize this behaviour in three different ways.
21022 You can move the colon character to somewhere else on the line.
21024 @findex gnus-goto-colon
21025 You can redefine the function that moves the point to the colon. The
21026 function is called @code{gnus-goto-colon}.
21028 But perhaps the most convenient way to deal with this, if you don't want
21029 to have a colon in your line, is to use the @samp{%*} specifier. If you
21030 put a @samp{%*} somewhere in your format line definition, Gnus will
21035 @subsection Tabulation
21037 You can usually line up your displays by padding and cutting your
21038 strings. However, when combining various strings of different size, it
21039 can often be more convenient to just output the strings, and then worry
21040 about lining up the following text afterwards.
21042 To do that, Gnus supplies tabulator specs---@samp{%=}. There are two
21043 different types---@dfn{hard tabulators} and @dfn{soft tabulators}.
21045 @samp{%50=} will insert space characters to pad the line up to column
21046 50. If the text is already past column 50, nothing will be inserted.
21047 This is the soft tabulator.
21049 @samp{%-50=} will insert space characters to pad the line up to column
21050 50. If the text is already past column 50, the excess text past column
21051 50 will be removed. This is the hard tabulator.
21054 @node Wide Characters
21055 @subsection Wide Characters
21057 Fixed width fonts in most countries have characters of the same width.
21058 Some countries, however, use Latin characters mixed with wider
21059 characters---most notable East Asian countries.
21061 The problem is that when formatting, Gnus assumes that if a string is 10
21062 characters wide, it'll be 10 Latin characters wide on the screen. In
21063 these countries, that's not true.
21065 @vindex gnus-use-correct-string-widths
21066 To help fix this, you can set @code{gnus-use-correct-string-widths} to
21067 @code{t}. This makes buffer generation slower, but the results will be
21068 prettier. The default value under XEmacs is @code{t} but @code{nil}
21072 @node Window Layout
21073 @section Window Layout
21074 @cindex window layout
21076 No, there's nothing here about X, so be quiet.
21078 @vindex gnus-use-full-window
21079 If @code{gnus-use-full-window} non-@code{nil}, Gnus will delete all
21080 other windows and occupy the entire Emacs screen by itself. It is
21081 @code{t} by default.
21083 Setting this variable to @code{nil} kinda works, but there are
21084 glitches. Use at your own peril.
21086 @vindex gnus-buffer-configuration
21087 @code{gnus-buffer-configuration} describes how much space each Gnus
21088 buffer should be given. Here's an excerpt of this variable:
21091 ((group (vertical 1.0 (group 1.0 point)
21092 (if gnus-carpal (group-carpal 4))))
21093 (article (vertical 1.0 (summary 0.25 point)
21097 This is an alist. The @dfn{key} is a symbol that names some action or
21098 other. For instance, when displaying the group buffer, the window
21099 configuration function will use @code{group} as the key. A full list of
21100 possible names is listed below.
21102 The @dfn{value} (i.e., the @dfn{split}) says how much space each buffer
21103 should occupy. To take the @code{article} split as an example -
21106 (article (vertical 1.0 (summary 0.25 point)
21110 This @dfn{split} says that the summary buffer should occupy 25% of upper
21111 half of the screen, and that it is placed over the article buffer. As
21112 you may have noticed, 100% + 25% is actually 125% (yup, I saw y'all
21113 reaching for that calculator there). However, the special number
21114 @code{1.0} is used to signal that this buffer should soak up all the
21115 rest of the space available after the rest of the buffers have taken
21116 whatever they need. There should be only one buffer with the @code{1.0}
21117 size spec per split.
21119 Point will be put in the buffer that has the optional third element
21120 @code{point}. In a @code{frame} split, the last subsplit having a leaf
21121 split where the tag @code{frame-focus} is a member (i.e. is the third or
21122 fourth element in the list, depending on whether the @code{point} tag is
21123 present) gets focus.
21125 Here's a more complicated example:
21128 (article (vertical 1.0 (group 4)
21129 (summary 0.25 point)
21130 (if gnus-carpal (summary-carpal 4))
21134 If the size spec is an integer instead of a floating point number,
21135 then that number will be used to say how many lines a buffer should
21136 occupy, not a percentage.
21138 If the @dfn{split} looks like something that can be @code{eval}ed (to be
21139 precise---if the @code{car} of the split is a function or a subr), this
21140 split will be @code{eval}ed. If the result is non-@code{nil}, it will
21141 be used as a split. This means that there will be three buffers if
21142 @code{gnus-carpal} is @code{nil}, and four buffers if @code{gnus-carpal}
21145 Not complicated enough for you? Well, try this on for size:
21148 (article (horizontal 1.0
21153 (summary 0.25 point)
21158 Whoops. Two buffers with the mystery 100% tag. And what's that
21159 @code{horizontal} thingie?
21161 If the first element in one of the split is @code{horizontal}, Gnus will
21162 split the window horizontally, giving you two windows side-by-side.
21163 Inside each of these strips you may carry on all you like in the normal
21164 fashion. The number following @code{horizontal} says what percentage of
21165 the screen is to be given to this strip.
21167 For each split, there @emph{must} be one element that has the 100% tag.
21168 The splitting is never accurate, and this buffer will eat any leftover
21169 lines from the splits.
21171 To be slightly more formal, here's a definition of what a valid split
21176 split = frame | horizontal | vertical | buffer | form
21177 frame = "(frame " size *split ")"
21178 horizontal = "(horizontal " size *split ")"
21179 vertical = "(vertical " size *split ")"
21180 buffer = "(" buf-name " " size *[ "point" ] *[ "frame-focus"] ")"
21181 size = number | frame-params
21182 buf-name = group | article | summary ...
21186 The limitations are that the @code{frame} split can only appear as the
21187 top-level split. @var{form} should be an Emacs Lisp form that should
21188 return a valid split. We see that each split is fully recursive, and
21189 may contain any number of @code{vertical} and @code{horizontal} splits.
21191 @vindex gnus-window-min-width
21192 @vindex gnus-window-min-height
21193 @cindex window height
21194 @cindex window width
21195 Finding the right sizes can be a bit complicated. No window may be less
21196 than @code{gnus-window-min-height} (default 1) characters high, and all
21197 windows must be at least @code{gnus-window-min-width} (default 1)
21198 characters wide. Gnus will try to enforce this before applying the
21199 splits. If you want to use the normal Emacs window width/height limit,
21200 you can just set these two variables to @code{nil}.
21202 If you're not familiar with Emacs terminology, @code{horizontal} and
21203 @code{vertical} splits may work the opposite way of what you'd expect.
21204 Windows inside a @code{horizontal} split are shown side-by-side, and
21205 windows within a @code{vertical} split are shown above each other.
21207 @findex gnus-configure-frame
21208 If you want to experiment with window placement, a good tip is to call
21209 @code{gnus-configure-frame} directly with a split. This is the function
21210 that does all the real work when splitting buffers. Below is a pretty
21211 nonsensical configuration with 5 windows; two for the group buffer and
21212 three for the article buffer. (I said it was nonsensical.) If you
21213 @code{eval} the statement below, you can get an idea of how that would
21214 look straight away, without going through the normal Gnus channels.
21215 Play with it until you're satisfied, and then use
21216 @code{gnus-add-configuration} to add your new creation to the buffer
21217 configuration list.
21220 (gnus-configure-frame
21224 (article 0.3 point))
21232 You might want to have several frames as well. No prob---just use the
21233 @code{frame} split:
21236 (gnus-configure-frame
21239 (summary 0.25 point frame-focus)
21241 (vertical ((height . 5) (width . 15)
21242 (user-position . t)
21243 (left . -1) (top . 1))
21248 This split will result in the familiar summary/article window
21249 configuration in the first (or ``main'') frame, while a small additional
21250 frame will be created where picons will be shown. As you can see,
21251 instead of the normal @code{1.0} top-level spec, each additional split
21252 should have a frame parameter alist as the size spec.
21253 @xref{Frame Parameters, , Frame Parameters, elisp, The GNU Emacs Lisp
21254 Reference Manual}. Under XEmacs, a frame property list will be
21255 accepted, too---for instance, @code{(height 5 width 15 left -1 top 1)}
21257 The list of all possible keys for @code{gnus-buffer-configuration} can
21258 be found in its default value.
21260 Note that the @code{message} key is used for both
21261 @code{gnus-group-mail} and @code{gnus-summary-mail-other-window}. If
21262 it is desirable to distinguish between the two, something like this
21266 (message (horizontal 1.0
21267 (vertical 1.0 (message 1.0 point))
21269 (if (buffer-live-p gnus-summary-buffer)
21274 One common desire for a multiple frame split is to have a separate frame
21275 for composing mail and news while leaving the original frame intact. To
21276 accomplish that, something like the following can be done:
21281 (if (not (buffer-live-p gnus-summary-buffer))
21282 (car (cdr (assoc 'group gnus-buffer-configuration)))
21283 (car (cdr (assoc 'summary gnus-buffer-configuration))))
21284 (vertical ((user-position . t) (top . 1) (left . 1)
21285 (name . "Message"))
21286 (message 1.0 point))))
21289 @findex gnus-add-configuration
21290 Since the @code{gnus-buffer-configuration} variable is so long and
21291 complicated, there's a function you can use to ease changing the config
21292 of a single setting: @code{gnus-add-configuration}. If, for instance,
21293 you want to change the @code{article} setting, you could say:
21296 (gnus-add-configuration
21297 '(article (vertical 1.0
21299 (summary .25 point)
21303 You'd typically stick these @code{gnus-add-configuration} calls in your
21304 @file{~/.gnus.el} file or in some startup hook---they should be run after
21305 Gnus has been loaded.
21307 @vindex gnus-always-force-window-configuration
21308 If all windows mentioned in the configuration are already visible, Gnus
21309 won't change the window configuration. If you always want to force the
21310 ``right'' window configuration, you can set
21311 @code{gnus-always-force-window-configuration} to non-@code{nil}.
21313 If you're using tree displays (@pxref{Tree Display}), and the tree
21314 window is displayed vertically next to another window, you may also want
21315 to fiddle with @code{gnus-tree-minimize-window} to avoid having the
21318 @subsection Example Window Configurations
21322 Narrow left hand side occupied by group buffer. Right hand side split
21323 between summary buffer (top one-sixth) and article buffer (bottom).
21338 (gnus-add-configuration
21341 (vertical 25 (group 1.0))
21343 (summary 0.16 point)
21346 (gnus-add-configuration
21349 (vertical 25 (group 1.0))
21350 (vertical 1.0 (summary 1.0 point)))))
21356 @node Faces and Fonts
21357 @section Faces and Fonts
21362 Fiddling with fonts and faces used to be very difficult, but these days
21363 it is very simple. You simply say @kbd{M-x customize-face}, pick out
21364 the face you want to alter, and alter it via the standard Customize
21369 @section Compilation
21370 @cindex compilation
21371 @cindex byte-compilation
21373 @findex gnus-compile
21375 Remember all those line format specification variables?
21376 @code{gnus-summary-line-format}, @code{gnus-group-line-format}, and so
21377 on. By default, T-gnus will use the byte-compiled codes of these
21378 variables and we can keep a slow-down to a minimum. However, if you set
21379 @code{gnus-compile-user-specs} to @code{nil} (@code{t} by default),
21380 unfortunately, changing them will mean a quite significant slow-down.
21381 (The default values of these variables have byte-compiled functions
21382 associated with them, while the user-generated versions do not, of
21385 To help with this, you can run @kbd{M-x gnus-compile} after you've
21386 fiddled around with the variables and feel that you're (kind of)
21387 satisfied. This will result in the new specs being byte-compiled, and
21388 you'll get top speed again. Note that T-gnus will not save these
21389 compiled specs in the @file{.newsrc.eld} file.
21392 @item gnus-compile-user-specs
21393 @vindex gnus-compile-user-specs
21394 If it is non-nil, the user-defined format specs will be byte-compiled
21395 automatically. The default value of this variable is @code{t}. It has
21396 an effect on the values of @code{gnus-*-line-format-spec}.
21401 @section Mode Lines
21404 @vindex gnus-updated-mode-lines
21405 @code{gnus-updated-mode-lines} says what buffers should keep their mode
21406 lines updated. It is a list of symbols. Supported symbols include
21407 @code{group}, @code{article}, @code{summary}, @code{server},
21408 @code{browse}, and @code{tree}. If the corresponding symbol is present,
21409 Gnus will keep that mode line updated with information that may be
21410 pertinent. If this variable is @code{nil}, screen refresh may be
21413 @cindex display-time
21415 @vindex gnus-mode-non-string-length
21416 By default, Gnus displays information on the current article in the mode
21417 lines of the summary and article buffers. The information Gnus wishes
21418 to display (e.g. the subject of the article) is often longer than the
21419 mode lines, and therefore have to be cut off at some point. The
21420 @code{gnus-mode-non-string-length} variable says how long the other
21421 elements on the line is (i.e., the non-info part). If you put
21422 additional elements on the mode line (e.g. a clock), you should modify
21425 @c Hook written by Francesco Potorti` <pot@cnuce.cnr.it>
21427 (add-hook 'display-time-hook
21428 (lambda () (setq gnus-mode-non-string-length
21430 (if line-number-mode 5 0)
21431 (if column-number-mode 4 0)
21432 (length display-time-string)))))
21435 If this variable is @code{nil} (which is the default), the mode line
21436 strings won't be chopped off, and they won't be padded either. Note
21437 that the default is unlikely to be desirable, as even the percentage
21438 complete in the buffer may be crowded off the mode line; the user should
21439 configure this variable appropriately for her configuration.
21442 @node Highlighting and Menus
21443 @section Highlighting and Menus
21445 @cindex highlighting
21448 @vindex gnus-visual
21449 The @code{gnus-visual} variable controls most of the Gnus-prettifying
21450 aspects. If @code{nil}, Gnus won't attempt to create menus or use fancy
21451 colors or fonts. This will also inhibit loading the @file{gnus-vis.el}
21454 This variable can be a list of visual properties that are enabled. The
21455 following elements are valid, and are all included by default:
21458 @item group-highlight
21459 Do highlights in the group buffer.
21460 @item summary-highlight
21461 Do highlights in the summary buffer.
21462 @item article-highlight
21463 Do highlights in the article buffer.
21465 Turn on highlighting in all buffers.
21467 Create menus in the group buffer.
21469 Create menus in the summary buffers.
21471 Create menus in the article buffer.
21473 Create menus in the browse buffer.
21475 Create menus in the server buffer.
21477 Create menus in the score buffers.
21479 Create menus in all buffers.
21482 So if you only want highlighting in the article buffer and menus in all
21483 buffers, you could say something like:
21486 (setq gnus-visual '(article-highlight menu))
21489 If you want highlighting only and no menus whatsoever, you'd say:
21492 (setq gnus-visual '(highlight))
21495 If @code{gnus-visual} is @code{t}, highlighting and menus will be used
21496 in all Gnus buffers.
21498 Other general variables that influence the look of all buffers include:
21501 @item gnus-mouse-face
21502 @vindex gnus-mouse-face
21503 This is the face (i.e., font) used for mouse highlighting in Gnus. No
21504 mouse highlights will be done if @code{gnus-visual} is @code{nil}.
21508 There are hooks associated with the creation of all the different menus:
21512 @item gnus-article-menu-hook
21513 @vindex gnus-article-menu-hook
21514 Hook called after creating the article mode menu.
21516 @item gnus-group-menu-hook
21517 @vindex gnus-group-menu-hook
21518 Hook called after creating the group mode menu.
21520 @item gnus-summary-menu-hook
21521 @vindex gnus-summary-menu-hook
21522 Hook called after creating the summary mode menu.
21524 @item gnus-server-menu-hook
21525 @vindex gnus-server-menu-hook
21526 Hook called after creating the server mode menu.
21528 @item gnus-browse-menu-hook
21529 @vindex gnus-browse-menu-hook
21530 Hook called after creating the browse mode menu.
21532 @item gnus-score-menu-hook
21533 @vindex gnus-score-menu-hook
21534 Hook called after creating the score mode menu.
21545 Those new-fangled @dfn{mouse} contraptions is very popular with the
21546 young, hep kids who don't want to learn the proper way to do things
21547 these days. Why, I remember way back in the summer of '89, when I was
21548 using Emacs on a Tops 20 system. Three hundred users on one single
21549 machine, and every user was running Simula compilers. Bah!
21553 @vindex gnus-carpal
21554 Well, you can make Gnus display bufferfuls of buttons you can click to
21555 do anything by setting @code{gnus-carpal} to @code{t}. Pretty simple,
21556 really. Tell the chiropractor I sent you.
21561 @item gnus-carpal-mode-hook
21562 @vindex gnus-carpal-mode-hook
21563 Hook run in all carpal mode buffers.
21565 @item gnus-carpal-button-face
21566 @vindex gnus-carpal-button-face
21567 Face used on buttons.
21569 @item gnus-carpal-header-face
21570 @vindex gnus-carpal-header-face
21571 Face used on carpal buffer headers.
21573 @item gnus-carpal-group-buffer-buttons
21574 @vindex gnus-carpal-group-buffer-buttons
21575 Buttons in the group buffer.
21577 @item gnus-carpal-summary-buffer-buttons
21578 @vindex gnus-carpal-summary-buffer-buttons
21579 Buttons in the summary buffer.
21581 @item gnus-carpal-server-buffer-buttons
21582 @vindex gnus-carpal-server-buffer-buttons
21583 Buttons in the server buffer.
21585 @item gnus-carpal-browse-buffer-buttons
21586 @vindex gnus-carpal-browse-buffer-buttons
21587 Buttons in the browse buffer.
21590 All the @code{buttons} variables are lists. The elements in these list
21591 are either cons cells where the @code{car} contains a text to be displayed and
21592 the @code{cdr} contains a function symbol, or a simple string.
21600 Gnus, being larger than any program ever written (allegedly), does lots
21601 of strange stuff that you may wish to have done while you're not
21602 present. For instance, you may want it to check for new mail once in a
21603 while. Or you may want it to close down all connections to all servers
21604 when you leave Emacs idle. And stuff like that.
21606 Gnus will let you do stuff like that by defining various
21607 @dfn{handlers}. Each handler consists of three elements: A
21608 @var{function}, a @var{time}, and an @var{idle} parameter.
21610 Here's an example of a handler that closes connections when Emacs has
21611 been idle for thirty minutes:
21614 (gnus-demon-close-connections nil 30)
21617 Here's a handler that scans for @acronym{PGP} headers every hour when
21621 (gnus-demon-scan-pgp 60 t)
21624 This @var{time} parameter and that @var{idle} parameter work together
21625 in a strange, but wonderful fashion. Basically, if @var{idle} is
21626 @code{nil}, then the function will be called every @var{time} minutes.
21628 If @var{idle} is @code{t}, then the function will be called after
21629 @var{time} minutes only if Emacs is idle. So if Emacs is never idle,
21630 the function will never be called. But once Emacs goes idle, the
21631 function will be called every @var{time} minutes.
21633 If @var{idle} is a number and @var{time} is a number, the function will
21634 be called every @var{time} minutes only when Emacs has been idle for
21635 @var{idle} minutes.
21637 If @var{idle} is a number and @var{time} is @code{nil}, the function
21638 will be called once every time Emacs has been idle for @var{idle}
21641 And if @var{time} is a string, it should look like @samp{07:31}, and
21642 the function will then be called once every day somewhere near that
21643 time. Modified by the @var{idle} parameter, of course.
21645 @vindex gnus-demon-timestep
21646 (When I say ``minute'' here, I really mean @code{gnus-demon-timestep}
21647 seconds. This is 60 by default. If you change that variable,
21648 all the timings in the handlers will be affected.)
21650 So, if you want to add a handler, you could put something like this in
21651 your @file{~/.gnus.el} file:
21653 @findex gnus-demon-add-handler
21655 (gnus-demon-add-handler 'gnus-demon-close-connections 30 t)
21658 @findex gnus-demon-add-nocem
21659 @findex gnus-demon-add-scanmail
21660 @findex gnus-demon-add-rescan
21661 @findex gnus-demon-add-scan-timestamps
21662 @findex gnus-demon-add-disconnection
21663 Some ready-made functions to do this have been created:
21664 @code{gnus-demon-add-nocem}, @code{gnus-demon-add-disconnection},
21665 @code{gnus-demon-add-nntp-close-connection},
21666 @code{gnus-demon-add-scan-timestamps}, @code{gnus-demon-add-rescan}, and
21667 @code{gnus-demon-add-scanmail}. Just put those functions in your
21668 @file{~/.gnus.el} if you want those abilities.
21670 @findex gnus-demon-init
21671 @findex gnus-demon-cancel
21672 @vindex gnus-demon-handlers
21673 If you add handlers to @code{gnus-demon-handlers} directly, you should
21674 run @code{gnus-demon-init} to make the changes take hold. To cancel all
21675 daemons, you can use the @code{gnus-demon-cancel} function.
21677 Note that adding daemons can be pretty naughty if you over do it. Adding
21678 functions that scan all news and mail from all servers every two seconds
21679 is a sure-fire way of getting booted off any respectable system. So
21688 @dfn{Spamming} is posting the same article lots and lots of times.
21689 Spamming is bad. Spamming is evil.
21691 Spamming is usually canceled within a day or so by various anti-spamming
21692 agencies. These agencies usually also send out @dfn{NoCeM} messages.
21693 NoCeM is pronounced ``no see-'em'', and means what the name
21694 implies---these are messages that make the offending articles, like, go
21697 What use are these NoCeM messages if the articles are canceled anyway?
21698 Some sites do not honor cancel messages and some sites just honor cancels
21699 from a select few people. Then you may wish to make use of the NoCeM
21700 messages, which are distributed in the @samp{alt.nocem.misc} newsgroup.
21702 Gnus can read and parse the messages in this group automatically, and
21703 this will make spam disappear.
21705 There are some variables to customize, of course:
21708 @item gnus-use-nocem
21709 @vindex gnus-use-nocem
21710 Set this variable to @code{t} to set the ball rolling. It is @code{nil}
21713 @item gnus-nocem-groups
21714 @vindex gnus-nocem-groups
21715 Gnus will look for NoCeM messages in the groups in this list. The
21718 ("news.lists.filters" "news.admin.net-abuse.bulletins"
21719 "alt.nocem.misc" "news.admin.net-abuse.announce")
21722 @item gnus-nocem-issuers
21723 @vindex gnus-nocem-issuers
21724 There are many people issuing NoCeM messages. This list says what
21725 people you want to listen to. The default is
21727 ("Automoose-1" "clewis@@ferret.ocunix.on.ca"
21728 "cosmo.roadkill" "SpamHippo" "hweede@@snafu.de")
21730 fine, upstanding citizens all of them.
21732 Known despammers that you can put in this list are listed at@*
21733 @uref{http://www.xs4all.nl/~rosalind/nocemreg/nocemreg.html}.
21735 You do not have to heed NoCeM messages from all these people---just the
21736 ones you want to listen to. You also don't have to accept all NoCeM
21737 messages from the people you like. Each NoCeM message has a @dfn{type}
21738 header that gives the message a (more or less, usually less) rigorous
21739 definition. Common types are @samp{spam}, @samp{spew}, @samp{mmf},
21740 @samp{binary}, and @samp{troll}. To specify this, you have to use
21741 @code{(@var{issuer} @var{conditions} @dots{})} elements in the list.
21742 Each condition is either a string (which is a regexp that matches types
21743 you want to use) or a list on the form @code{(not @var{string})}, where
21744 @var{string} is a regexp that matches types you don't want to use.
21746 For instance, if you want all NoCeM messages from Chris Lewis except his
21747 @samp{troll} messages, you'd say:
21750 ("clewis@@ferret.ocunix.on.ca" ".*" (not "troll"))
21753 On the other hand, if you just want nothing but his @samp{spam} and
21754 @samp{spew} messages, you'd say:
21757 ("clewis@@ferret.ocunix.on.ca" (not ".*") "spew" "spam")
21760 The specs are applied left-to-right.
21763 @item gnus-nocem-verifyer
21764 @vindex gnus-nocem-verifyer
21766 This should be a function for verifying that the NoCeM issuer is who she
21767 says she is. The default is @code{mc-verify}, which is a Mailcrypt
21768 function. If this is too slow and you don't care for verification
21769 (which may be dangerous), you can set this variable to @code{nil}.
21771 If you want signed NoCeM messages to be verified and unsigned messages
21772 not to be verified (but used anyway), you could do something like:
21775 (setq gnus-nocem-verifyer 'my-gnus-mc-verify)
21777 (defun my-gnus-mc-verify ()
21785 This might be dangerous, though.
21787 @item gnus-nocem-directory
21788 @vindex gnus-nocem-directory
21789 This is where Gnus will store its NoCeM cache files. The default is@*
21790 @file{~/News/NoCeM/}.
21792 @item gnus-nocem-expiry-wait
21793 @vindex gnus-nocem-expiry-wait
21794 The number of days before removing old NoCeM entries from the cache.
21795 The default is 15. If you make it shorter Gnus will be faster, but you
21796 might then see old spam.
21798 @item gnus-nocem-check-from
21799 @vindex gnus-nocem-check-from
21800 Non-@code{nil} means check for valid issuers in message bodies.
21801 Otherwise don't bother fetching articles unless their author matches a
21802 valid issuer; that is much faster if you are selective about the
21805 @item gnus-nocem-check-article-limit
21806 @vindex gnus-nocem-check-article-limit
21807 If non-@code{nil}, the maximum number of articles to check in any NoCeM
21808 group. NoCeM groups can be huge and very slow to process.
21812 Using NoCeM could potentially be a memory hog. If you have many living
21813 (i. e., subscribed or unsubscribed groups), your Emacs process will grow
21814 big. If this is a problem, you should kill off all (or most) of your
21815 unsubscribed groups (@pxref{Subscription Commands}).
21822 It is very useful to be able to undo actions one has done. In normal
21823 Emacs buffers, it's easy enough---you just push the @code{undo} button.
21824 In Gnus buffers, however, it isn't that simple.
21826 The things Gnus displays in its buffer is of no value whatsoever to
21827 Gnus---it's all just data designed to look nice to the user.
21828 Killing a group in the group buffer with @kbd{C-k} makes the line
21829 disappear, but that's just a side-effect of the real action---the
21830 removal of the group in question from the internal Gnus structures.
21831 Undoing something like that can't be done by the normal Emacs
21832 @code{undo} function.
21834 Gnus tries to remedy this somewhat by keeping track of what the user
21835 does and coming up with actions that would reverse the actions the user
21836 takes. When the user then presses the @code{undo} key, Gnus will run
21837 the code to reverse the previous action, or the previous actions.
21838 However, not all actions are easily reversible, so Gnus currently offers
21839 a few key functions to be undoable. These include killing groups,
21840 yanking groups, and changing the list of read articles of groups.
21841 That's it, really. More functions may be added in the future, but each
21842 added function means an increase in data to be stored, so Gnus will
21843 never be totally undoable.
21845 @findex gnus-undo-mode
21846 @vindex gnus-use-undo
21848 The undoability is provided by the @code{gnus-undo-mode} minor mode. It
21849 is used if @code{gnus-use-undo} is non-@code{nil}, which is the
21850 default. The @kbd{C-M-_} key performs the @code{gnus-undo}
21851 command, which should feel kinda like the normal Emacs @code{undo}
21855 @node Predicate Specifiers
21856 @section Predicate Specifiers
21857 @cindex predicate specifiers
21859 Some Gnus variables are @dfn{predicate specifiers}. This is a special
21860 form that allows flexible specification of predicates without having
21861 to type all that much.
21863 These specifiers are lists consisting of functions, symbols and lists.
21868 (or gnus-article-unseen-p
21869 gnus-article-unread-p)
21872 The available symbols are @code{or}, @code{and} and @code{not}. The
21873 functions all take one parameter.
21875 @findex gnus-make-predicate
21876 Internally, Gnus calls @code{gnus-make-predicate} on these specifiers
21877 to create a function that can be called. This input parameter to this
21878 function will be passed along to all the functions in the predicate
21883 @section Moderation
21886 If you are a moderator, you can use the @file{gnus-mdrtn.el} package.
21887 It is not included in the standard Gnus package. Write a mail to
21888 @samp{larsi@@gnus.org} and state what group you moderate, and you'll
21891 The moderation package is implemented as a minor mode for summary
21895 (add-hook 'gnus-summary-mode-hook 'gnus-moderate)
21898 in your @file{~/.gnus.el} file.
21900 If you are the moderator of @samp{rec.zoofle}, this is how it's
21905 You split your incoming mail by matching on
21906 @samp{Newsgroups:.*rec.zoofle}, which will put all the to-be-posted
21907 articles in some mail group---for instance, @samp{nnml:rec.zoofle}.
21910 You enter that group once in a while and post articles using the @kbd{e}
21911 (edit-and-post) or @kbd{s} (just send unedited) commands.
21914 If, while reading the @samp{rec.zoofle} newsgroup, you happen upon some
21915 articles that weren't approved by you, you can cancel them with the
21919 To use moderation mode in these two groups, say:
21922 (setq gnus-moderated-list
21923 "^nnml:rec.zoofle$\\|^rec.zoofle$")
21927 @node Image Enhancements
21928 @section Image Enhancements
21930 XEmacs, as well as Emacs 21@footnote{Emacs 21 on MS Windows doesn't
21931 support images yet.}, is able to display pictures and stuff, so Gnus has
21932 taken advantage of that.
21935 * X-Face:: Display a funky, teensy black-and-white image.
21936 * Face:: Display a funkier, teensier colored image.
21937 * Smileys:: Show all those happy faces the way they were meant to be shown.
21938 * Picons:: How to display pictures of what you're reading.
21939 * XVarious:: Other XEmacsy Gnusey variables.
21947 @code{X-Face} headers describe a 48x48 pixel black-and-white (1 bit
21948 depth) image that's supposed to represent the author of the message.
21949 It seems to be supported by an ever-growing number of mail and news
21953 @findex gnus-article-display-x-face
21954 @vindex gnus-article-x-face-command
21955 @vindex gnus-article-x-face-too-ugly
21963 Decoding an @code{X-Face} header either requires an Emacs that has
21964 @samp{compface} support (which most XEmacs versions has), or that you
21965 have @samp{compface} installed on your system. If either is true,
21966 Gnus will default to displaying @code{X-Face} headers.
21968 The variable that controls this is the
21969 @code{gnus-article-x-face-command} variable. If this variable is a
21970 string, this string will be executed in a sub-shell. If it is a
21971 function, this function will be called with the face as the argument.
21972 If the @code{gnus-article-x-face-too-ugly} (which is a regexp) matches
21973 the @code{From} header, the face will not be shown.
21975 The default action under Emacs 20 is to fork off the @code{display}
21976 program@footnote{@code{display} is from the ImageMagick package. For
21977 the @code{uncompface} and @code{icontopbm} programs look for a package
21978 like @code{compface} or @code{faces-xface} on a GNU/Linux system.} to
21981 Under XEmacs or Emacs 21+ with suitable image support, the default
21982 action is to display the face before the @code{From} header. (It's
21983 nicer if XEmacs has been compiled with @code{X-Face} support---that
21984 will make display somewhat faster. If there's no native @code{X-Face}
21985 support, Gnus will try to convert the @code{X-Face} header using
21986 external programs from the @code{pbmplus} package and
21987 friends.@footnote{On a GNU/Linux system look for packages with names
21988 like @code{netpbm}, @code{libgr-progs} and @code{compface}.})
21990 (Note: @code{x-face} is used in the variable/function names, not
21998 @vindex gnus-x-face
21999 Face to show X-Face. The colors from this face are used as the
22000 foreground and background colors of the displayed X-Faces. The
22001 default colors are black and white.
22003 @item gnus-face-properties-alist
22004 @vindex gnus-face-properties-alist
22005 Alist of image types and properties applied to Face (@pxref{Face}) and
22006 X-Face images. The default value is @code{((pbm . (:face gnus-x-face))
22007 (png . nil))} for Emacs or @code{((xface . (:face gnus-x-face)))} for
22008 XEmacs. Here are examples:
22011 ;; Specify the altitude of Face and X-Face images in the From header.
22012 (setq gnus-face-properties-alist
22013 '((pbm . (:face gnus-x-face :ascent 80))
22014 (png . (:ascent 80))))
22016 ;; Show Face and X-Face images as pressed buttons.
22017 (setq gnus-face-properties-alist
22018 '((pbm . (:face gnus-x-face :relief -2))
22019 (png . (:relief -2))))
22022 @pxref{Image Descriptors, ,Image Descriptors, elisp, The Emacs Lisp
22023 Reference Manual} for the valid properties for various image types.
22024 Currently, @code{pbm} is used for X-Face images and @code{png} is used
22025 for Face images in Emacs. Only the @code{:face} property is effective
22026 on the @code{xface} image type in XEmacs if it is built with the
22027 @samp{libcompface} library.
22030 Gnus provides a few convenience functions and variables to allow
22031 easier insertion of X-Face headers in outgoing messages.
22033 @findex gnus-random-x-face
22034 @vindex gnus-convert-pbm-to-x-face-command
22035 @vindex gnus-x-face-directory
22036 @code{gnus-random-x-face} goes through all the @samp{pbm} files in
22037 @code{gnus-x-face-directory} and picks one at random, and then
22038 converts it to the X-Face format by using the
22039 @code{gnus-convert-pbm-to-x-face-command} shell command. The
22040 @samp{pbm} files should be 48x48 pixels big. It returns the X-Face
22041 header data as a string.
22043 @findex gnus-insert-random-x-face-header
22044 @code{gnus-insert-random-x-face-header} calls
22045 @code{gnus-random-x-face} and inserts a @samp{X-Face} header with the
22046 randomly generated data.
22048 @findex gnus-x-face-from-file
22049 @vindex gnus-convert-image-to-x-face-command
22050 @code{gnus-x-face-from-file} takes a GIF file as the parameter, and then
22051 converts the file to X-Face format by using the
22052 @code{gnus-convert-image-to-x-face-command} shell command.
22054 Here's how you would typically use the first function. Put something
22055 like the following in your @file{~/.gnus.el} file:
22058 (setq message-required-news-headers
22059 (nconc message-required-news-headers
22060 (list '(X-Face . gnus-random-x-face))))
22063 Using the last function would be something like this:
22066 (setq message-required-news-headers
22067 (nconc message-required-news-headers
22068 (list '(X-Face . (lambda ()
22069 (gnus-x-face-from-file
22070 "~/My-face.gif"))))))
22078 @c #### FIXME: faces and x-faces'implementations should really be harmonized.
22080 @code{Face} headers are essentially a funkier version of @code{X-Face}
22081 ones. They describe a 48x48 pixel colored image that's supposed to
22082 represent the author of the message.
22085 @findex gnus-article-display-face
22086 The contents of a @code{Face} header must be a base64 encoded PNG image.
22087 See @uref{http://quimby.gnus.org/circus/face/} for the precise
22090 The @code{gnus-face-properties-alist} variable affects the appearance of
22091 displayed Face images. @xref{X-Face}.
22093 Gnus provides a few convenience functions and variables to allow
22094 easier insertion of Face headers in outgoing messages.
22096 @findex gnus-convert-png-to-face
22097 @code{gnus-convert-png-to-face} takes a 48x48 PNG image, no longer than
22098 726 bytes long, and converts it to a face.
22100 @findex gnus-face-from-file
22101 @vindex gnus-convert-image-to-face-command
22102 @code{gnus-face-from-file} takes a JPEG file as the parameter, and then
22103 converts the file to Face format by using the
22104 @code{gnus-convert-image-to-face-command} shell command.
22106 Here's how you would typically use this function. Put something like the
22107 following in your @file{~/.gnus.el} file:
22110 (setq message-required-news-headers
22111 (nconc message-required-news-headers
22112 (list '(Face . (lambda ()
22113 (gnus-face-from-file "~/face.jpg"))))))
22118 @subsection Smileys
22123 \gnusfig{-3cm}{0.5cm}{\epsfig{figure=ps/BigFace,height=20cm}}
22128 @dfn{Smiley} is a package separate from Gnus, but since Gnus is
22129 currently the only package that uses Smiley, it is documented here.
22131 In short---to use Smiley in Gnus, put the following in your
22132 @file{~/.gnus.el} file:
22135 (setq gnus-treat-display-smileys t)
22138 Smiley maps text smiley faces---@samp{:-)}, @samp{8-)}, @samp{:-(} and
22139 the like---to pictures and displays those instead of the text smiley
22140 faces. The conversion is controlled by a list of regexps that matches
22141 text and maps that to file names.
22143 @vindex smiley-regexp-alist
22144 The alist used is specified by the @code{smiley-regexp-alist}
22145 variable. The first item in each element is the regexp to be matched;
22146 the second element is the regexp match group that is to be replaced by
22147 the picture; and the third element is the name of the file to be
22150 The following variables customize where Smiley will look for these
22155 @item smiley-data-directory
22156 @vindex smiley-data-directory
22157 Where Smiley will look for smiley faces files.
22159 @item gnus-smiley-file-types
22160 @vindex gnus-smiley-file-types
22161 List of suffixes on smiley file names to try.
22175 So@dots{} You want to slow down your news reader even more! This is a
22176 good way to do so. It's also a great way to impress people staring
22177 over your shoulder as you read news.
22179 What are Picons? To quote directly from the Picons Web site:
22188 @dfn{Picons} is short for ``personal icons''. They're small,
22189 constrained images used to represent users and domains on the net,
22190 organized into databases so that the appropriate image for a given
22191 e-mail address can be found. Besides users and domains, there are picon
22192 databases for Usenet newsgroups and weather forecasts. The picons are
22193 in either monochrome @code{XBM} format or color @code{XPM} and
22194 @code{GIF} formats.
22197 @vindex gnus-picon-databases
22198 For instructions on obtaining and installing the picons databases,
22199 point your Web browser at
22200 @uref{http://www.cs.indiana.edu/picons/ftp/index.html}.
22202 If you are using Debian GNU/Linux, saying @samp{apt-get install
22203 picons.*} will install the picons where Gnus can find them.
22205 To enable displaying picons, simply make sure that
22206 @code{gnus-picon-databases} points to the directory containing the
22209 @vindex gnus-picon-style
22210 The variable @code{gnus-picon-style} controls how picons are displayed.
22211 If @code{inline}, the textual representation is replaced. If
22212 @code{right}, picons are added right to the textual representation.
22214 The following variables offer control over where things are located.
22218 @item gnus-picon-databases
22219 @vindex gnus-picon-databases
22220 The location of the picons database. This is a list of directories
22221 containing the @file{news}, @file{domains}, @file{users} (and so on)
22222 subdirectories. Defaults to @code{("/usr/lib/picon"
22223 "/usr/local/faces")}.
22225 @item gnus-picon-news-directories
22226 @vindex gnus-picon-news-directories
22227 List of subdirectories to search in @code{gnus-picon-databases} for
22228 newsgroups faces. @code{("news")} is the default.
22230 @item gnus-picon-user-directories
22231 @vindex gnus-picon-user-directories
22232 List of subdirectories to search in @code{gnus-picon-databases} for user
22233 faces. @code{("users" "usenix" "local" "misc")} is the default.
22235 @item gnus-picon-domain-directories
22236 @vindex gnus-picon-domain-directories
22237 List of subdirectories to search in @code{gnus-picon-databases} for
22238 domain name faces. Defaults to @code{("domains")}. Some people may
22239 want to add @samp{"unknown"} to this list.
22241 @item gnus-picon-file-types
22242 @vindex gnus-picon-file-types
22243 Ordered list of suffixes on picon file names to try. Defaults to
22244 @code{("xpm" "gif" "xbm")} minus those not built-in your Emacs.
22250 @subsection Various XEmacs Variables
22253 @item gnus-xmas-glyph-directory
22254 @vindex gnus-xmas-glyph-directory
22255 This is where Gnus will look for pictures. Gnus will normally
22256 auto-detect this directory, but you may set it manually if you have an
22257 unusual directory structure.
22259 @item gnus-xmas-logo-color-alist
22260 @vindex gnus-xmas-logo-color-alist
22261 This is an alist where the key is a type symbol and the values are the
22262 foreground and background color of the splash page glyph.
22264 @item gnus-xmas-logo-color-style
22265 @vindex gnus-xmas-logo-color-style
22266 This is the key used to look up the color in the alist described above.
22267 Valid values include @code{flame}, @code{pine}, @code{moss},
22268 @code{irish}, @code{sky}, @code{tin}, @code{velvet}, @code{grape},
22269 @code{labia}, @code{berry}, @code{neutral}, and @code{september}.
22271 @item gnus-xmas-modeline-glyph
22272 @vindex gnus-xmas-modeline-glyph
22273 A glyph displayed in all Gnus mode lines. It is a tiny gnu head by
22278 @subsubsection Toolbar
22282 @item gnus-use-toolbar
22283 @vindex gnus-use-toolbar
22284 If @code{nil}, don't display toolbars. If non-@code{nil}, it should be
22285 one of @code{default-toolbar}, @code{top-toolbar}, @code{bottom-toolbar},
22286 @code{right-toolbar}, or @code{left-toolbar}.
22288 @item gnus-group-toolbar
22289 @vindex gnus-group-toolbar
22290 The toolbar in the group buffer.
22292 @item gnus-summary-toolbar
22293 @vindex gnus-summary-toolbar
22294 The toolbar in the summary buffer.
22296 @item gnus-summary-mail-toolbar
22297 @vindex gnus-summary-mail-toolbar
22298 The toolbar in the summary buffer of mail groups.
22309 @node Fuzzy Matching
22310 @section Fuzzy Matching
22311 @cindex fuzzy matching
22313 Gnus provides @dfn{fuzzy matching} of @code{Subject} lines when doing
22314 things like scoring, thread gathering and thread comparison.
22316 As opposed to regular expression matching, fuzzy matching is very fuzzy.
22317 It's so fuzzy that there's not even a definition of what @dfn{fuzziness}
22318 means, and the implementation has changed over time.
22320 Basically, it tries to remove all noise from lines before comparing.
22321 @samp{Re: }, parenthetical remarks, white space, and so on, are filtered
22322 out of the strings before comparing the results. This often leads to
22323 adequate results---even when faced with strings generated by text
22324 manglers masquerading as newsreaders.
22327 @node Thwarting Email Spam
22328 @section Thwarting Email Spam
22332 @cindex unsolicited commercial email
22334 In these last days of the Usenet, commercial vultures are hanging about
22335 and grepping through news like crazy to find email addresses they can
22336 foist off their scams and products to. As a reaction to this, many
22337 people have started putting nonsense addresses into their @code{From}
22338 lines. I think this is counterproductive---it makes it difficult for
22339 people to send you legitimate mail in response to things you write, as
22340 well as making it difficult to see who wrote what. This rewriting may
22341 perhaps be a bigger menace than the unsolicited commercial email itself
22344 The biggest problem I have with email spam is that it comes in under
22345 false pretenses. I press @kbd{g} and Gnus merrily informs me that I
22346 have 10 new emails. I say ``Golly gee! Happy is me!'' and select the
22347 mail group, only to find two pyramid schemes, seven advertisements
22348 (``New! Miracle tonic for growing full, lustrous hair on your toes!'')
22349 and one mail asking me to repent and find some god.
22351 This is annoying. Here's what you can do about it.
22354 * The problem of spam:: Some background, and some solutions
22355 * Anti-Spam Basics:: Simple steps to reduce the amount of spam.
22356 * SpamAssassin:: How to use external anti-spam tools.
22357 * Hashcash:: Reduce spam by burning CPU time.
22358 * Filtering Spam Using The Spam ELisp Package::
22359 * Filtering Spam Using Statistics with spam-stat::
22362 @node The problem of spam
22363 @subsection The problem of spam
22365 @cindex spam filtering approaches
22366 @cindex filtering approaches, spam
22368 @cindex unsolicited commercial email
22370 First, some background on spam.
22372 If you have access to e-mail, you are familiar with spam (technically
22373 termed @acronym{UCE}, Unsolicited Commercial E-mail). Simply put, it
22374 exists because e-mail delivery is very cheap compared to paper mail,
22375 so only a very small percentage of people need to respond to an UCE to
22376 make it worthwhile to the advertiser. Ironically, one of the most
22377 common spams is the one offering a database of e-mail addresses for
22378 further spamming. Senders of spam are usually called @emph{spammers},
22379 but terms like @emph{vermin}, @emph{scum}, @emph{sociopaths}, and
22380 @emph{morons} are in common use as well.
22382 Spam comes from a wide variety of sources. It is simply impossible to
22383 dispose of all spam without discarding useful messages. A good
22384 example is the TMDA system, which requires senders
22385 unknown to you to confirm themselves as legitimate senders before
22386 their e-mail can reach you. Without getting into the technical side
22387 of TMDA, a downside is clearly that e-mail from legitimate sources may
22388 be discarded if those sources can't or won't confirm themselves
22389 through the TMDA system. Another problem with TMDA is that it
22390 requires its users to have a basic understanding of e-mail delivery
22393 The simplest approach to filtering spam is filtering, at the mail
22394 server or when you sort through incoming mail. If you get 200 spam
22395 messages per day from @samp{random-address@@vmadmin.com}, you block
22396 @samp{vmadmin.com}. If you get 200 messages about @samp{VIAGRA}, you
22397 discard all messages with @samp{VIAGRA} in the message. If you get
22398 lots of spam from Bulgaria, for example, you try to filter all mail
22399 from Bulgarian IPs.
22401 This, unfortunately, is a great way to discard legitimate e-mail. The
22402 risks of blocking a whole country (Bulgaria, Norway, Nigeria, China,
22403 etc.) or even a continent (Asia, Africa, Europe, etc.) from contacting
22404 you should be obvious, so don't do it if you have the choice.
22406 In another instance, the very informative and useful RISKS digest has
22407 been blocked by overzealous mail filters because it @strong{contained}
22408 words that were common in spam messages. Nevertheless, in isolated
22409 cases, with great care, direct filtering of mail can be useful.
22411 Another approach to filtering e-mail is the distributed spam
22412 processing, for instance DCC implements such a system. In essence,
22413 @var{N} systems around the world agree that a machine @var{X} in
22414 Ghana, Estonia, or California is sending out spam e-mail, and these
22415 @var{N} systems enter @var{X} or the spam e-mail from @var{X} into a
22416 database. The criteria for spam detection vary---it may be the number
22417 of messages sent, the content of the messages, and so on. When a user
22418 of the distributed processing system wants to find out if a message is
22419 spam, he consults one of those @var{N} systems.
22421 Distributed spam processing works very well against spammers that send
22422 a large number of messages at once, but it requires the user to set up
22423 fairly complicated checks. There are commercial and free distributed
22424 spam processing systems. Distributed spam processing has its risks as
22425 well. For instance legitimate e-mail senders have been accused of
22426 sending spam, and their web sites and mailing lists have been shut
22427 down for some time because of the incident.
22429 The statistical approach to spam filtering is also popular. It is
22430 based on a statistical analysis of previous spam messages. Usually
22431 the analysis is a simple word frequency count, with perhaps pairs of
22432 words or 3-word combinations thrown into the mix. Statistical
22433 analysis of spam works very well in most of the cases, but it can
22434 classify legitimate e-mail as spam in some cases. It takes time to
22435 run the analysis, the full message must be analyzed, and the user has
22436 to store the database of spam analyses. Statistical analysis on the
22437 server is gaining popularity. This has the advantage of letting the
22438 user Just Read Mail, but has the disadvantage that it's harder to tell
22439 the server that it has misclassified mail.
22441 Fighting spam is not easy, no matter what anyone says. There is no
22442 magic switch that will distinguish Viagra ads from Mom's e-mails.
22443 Even people are having a hard time telling spam apart from non-spam,
22444 because spammers are actively looking to fool us into thinking they
22445 are Mom, essentially. Spamming is irritating, irresponsible, and
22446 idiotic behavior from a bunch of people who think the world owes them
22447 a favor. We hope the following sections will help you in fighting the
22450 @node Anti-Spam Basics
22451 @subsection Anti-Spam Basics
22455 @cindex unsolicited commercial email
22457 One way of dealing with spam is having Gnus split out all spam into a
22458 @samp{spam} mail group (@pxref{Splitting Mail}).
22460 First, pick one (1) valid mail address that you can be reached at, and
22461 put it in your @code{From} header of all your news articles. (I've
22462 chosen @samp{larsi@@trym.ifi.uio.no}, but for many addresses on the form
22463 @samp{larsi+usenet@@ifi.uio.no} will be a better choice. Ask your
22464 sysadmin whether your sendmail installation accepts keywords in the local
22465 part of the mail address.)
22468 (setq message-default-news-headers
22469 "From: Lars Magne Ingebrigtsen <larsi@@trym.ifi.uio.no>\n")
22472 Then put the following split rule in @code{nnmail-split-fancy}
22473 (@pxref{Fancy Mail Splitting}):
22477 (to "larsi@@trym.ifi.uio.no"
22478 (| ("subject" "re:.*" "misc")
22479 ("references" ".*@@.*" "misc")
22484 This says that all mail to this address is suspect, but if it has a
22485 @code{Subject} that starts with a @samp{Re:} or has a @code{References}
22486 header, it's probably ok. All the rest goes to the @samp{spam} group.
22487 (This idea probably comes from Tim Pierce.)
22489 In addition, many mail spammers talk directly to your @acronym{SMTP} server
22490 and do not include your email address explicitly in the @code{To}
22491 header. Why they do this is unknown---perhaps it's to thwart this
22492 thwarting scheme? In any case, this is trivial to deal with---you just
22493 put anything not addressed to you in the @samp{spam} group by ending
22494 your fancy split rule in this way:
22499 (to "larsi" "misc")
22503 In my experience, this will sort virtually everything into the right
22504 group. You still have to check the @samp{spam} group from time to time to
22505 check for legitimate mail, though. If you feel like being a good net
22506 citizen, you can even send off complaints to the proper authorities on
22507 each unsolicited commercial email---at your leisure.
22509 This works for me. It allows people an easy way to contact me (they can
22510 just press @kbd{r} in the usual way), and I'm not bothered at all with
22511 spam. It's a win-win situation. Forging @code{From} headers to point
22512 to non-existent domains is yucky, in my opinion.
22514 Be careful with this approach. Spammers are wise to it.
22518 @subsection SpamAssassin, Vipul's Razor, DCC, etc
22519 @cindex SpamAssassin
22520 @cindex Vipul's Razor
22523 The days where the hints in the previous section were sufficient in
22524 avoiding spam are coming to an end. There are many tools out there
22525 that claim to reduce the amount of spam you get. This section could
22526 easily become outdated fast, as new products replace old, but
22527 fortunately most of these tools seem to have similar interfaces. Even
22528 though this section will use SpamAssassin as an example, it should be
22529 easy to adapt it to most other tools.
22531 Note that this section does not involve the @code{spam.el} package,
22532 which is discussed in the next section. If you don't care for all
22533 the features of @code{spam.el}, you can make do with these simple
22536 If the tool you are using is not installed on the mail server, you
22537 need to invoke it yourself. Ideas on how to use the
22538 @code{:postscript} mail source parameter (@pxref{Mail Source
22539 Specifiers}) follow.
22543 '((file :prescript "formail -bs spamassassin < /var/mail/%u")
22547 "mv %t /tmp/foo; formail -bs spamc < /tmp/foo > %t")))
22550 Once you manage to process your incoming spool somehow, thus making
22551 the mail contain e.g.@: a header indicating it is spam, you are ready to
22552 filter it out. Using normal split methods (@pxref{Splitting Mail}):
22555 (setq nnmail-split-methods '(("spam" "^X-Spam-Flag: YES")
22559 Or using fancy split methods (@pxref{Fancy Mail Splitting}):
22562 (setq nnmail-split-methods 'nnmail-split-fancy
22563 nnmail-split-fancy '(| ("X-Spam-Flag" "YES" "spam")
22567 Some people might not like the idea of piping the mail through various
22568 programs using a @code{:prescript} (if some program is buggy, you
22569 might lose all mail). If you are one of them, another solution is to
22570 call the external tools during splitting. Example fancy split method:
22573 (setq nnmail-split-fancy '(| (: kevin-spamassassin)
22575 (defun kevin-spamassassin ()
22579 (if (eq 1 (call-process-region (point-min) (point-max)
22580 "spamc" nil nil nil "-c"))
22584 Note that with the nnimap back end, message bodies will not be
22585 downloaded by default. You need to set
22586 @code{nnimap-split-download-body} to @code{t} to do that
22587 (@pxref{Splitting in IMAP}).
22589 That is about it. As some spam is likely to get through anyway, you
22590 might want to have a nifty function to call when you happen to read
22591 spam. And here is the nifty function:
22594 (defun my-gnus-raze-spam ()
22595 "Submit SPAM to Vipul's Razor, then mark it as expirable."
22597 (gnus-summary-show-raw-article)
22598 (gnus-summary-save-in-pipe "razor-report -f -d")
22599 (gnus-summary-mark-as-expirable 1))
22603 @subsection Hashcash
22606 A novel technique to fight spam is to require senders to do something
22607 costly and demonstrably unique for each message they send. This has
22608 the obvious drawback that you cannot rely on everyone in the world
22609 using this technique, since it is not part of the Internet standards,
22610 but it may be useful in smaller communities.
22612 While the tools in the previous section work well in practice, they
22613 work only because the tools are constantly maintained and updated as
22614 new form of spam appears. This means that a small percentage of spam
22615 will always get through. It also means that somewhere, someone needs
22616 to read lots of spam to update these tools. Hashcash avoids that, but
22617 instead prefers that everyone you contact through e-mail supports the
22618 scheme. You can view the two approaches as pragmatic vs dogmatic.
22619 The approaches have their own advantages and disadvantages, but as
22620 often in the real world, a combination of them is stronger than either
22621 one of them separately.
22624 The ``something costly'' is to burn CPU time, more specifically to
22625 compute a hash collision up to a certain number of bits. The
22626 resulting hashcash cookie is inserted in a @samp{X-Hashcash:} header.
22627 For more details, and for the external application @code{hashcash} you
22628 need to install to use this feature, see
22629 @uref{http://www.hashcash.org/}. Even more information can be found
22630 at @uref{http://www.camram.org/}.
22632 If you wish to generate hashcash for each message you send, you can
22633 customize @code{message-generate-hashcash} (@pxref{Mail Headers, ,Mail
22634 Headers,message, The Message Manual}), as in:
22637 (setq message-generate-hashcash t)
22640 You will need to set up some additional variables as well:
22644 @item hashcash-default-payment
22645 @vindex hashcash-default-payment
22646 This variable indicates the default number of bits the hash collision
22647 should consist of. By default this is 20. Suggested useful values
22650 @item hashcash-payment-alist
22651 @vindex hashcash-payment-alist
22652 Some receivers may require you to spend burn more CPU time than the
22653 default. This variable contains a list of @samp{(@var{addr}
22654 @var{amount})} cells, where @var{addr} is the receiver (email address
22655 or newsgroup) and @var{amount} is the number of bits in the collision
22656 that is needed. It can also contain @samp{(@var{addr} @var{string}
22657 @var{amount})} cells, where the @var{string} is the string to use
22658 (normally the email address or newsgroup name is used).
22660 @item hashcash-path
22661 @vindex hashcash-path
22662 Where the @code{hashcash} binary is installed. This variable should
22663 be automatically set by @code{executable-find}, but if it's @code{nil}
22664 (usually because the @code{hashcash} binary is not in your path)
22665 you'll get a warning when you check hashcash payments and an error
22666 when you generate hashcash payments.
22670 Gnus can verify hashcash cookies, although this can also be done by
22671 hand customized mail filtering scripts. To verify a hashcash cookie
22672 in a message, use the @code{mail-check-payment} function in the
22673 @code{hashcash.el} library. You can also use the @code{spam.el}
22674 package with the @code{spam-use-hashcash} back end to validate hashcash
22675 cookies in incoming mail and filter mail accordingly (@pxref{Anti-spam
22676 Hashcash Payments}).
22678 @node Filtering Spam Using The Spam ELisp Package
22679 @subsection Filtering Spam Using The Spam ELisp Package
22680 @cindex spam filtering
22683 The idea behind @code{spam.el} is to have a control center for spam detection
22684 and filtering in Gnus. To that end, @code{spam.el} does two things: it
22685 filters new mail, and it analyzes mail known to be spam or ham.
22686 @dfn{Ham} is the name used throughout @code{spam.el} to indicate
22689 Make sure you read the section on the @code{spam.el} sequence of
22690 events. See @xref{Spam ELisp Package Sequence of Events}.
22692 @cindex spam-initialize
22693 To use @code{spam.el}, you @strong{must} run the function
22694 @code{spam-initialize} to autoload @file{spam.el} and to install the
22695 @code{spam.el} hooks. There is one exception: if you use the
22696 @code{spam-use-stat} (@pxref{spam-stat spam filtering}) setting, you
22697 should turn it on before @code{spam-initialize}:
22700 (setq spam-use-stat t) ;; if needed
22704 So, what happens when you load @file{spam.el}?
22706 First, some hooks will get installed by @code{spam-initialize}. There
22707 are some hooks for @code{spam-stat} so it can save its databases, and
22708 there are hooks so interesting things will happen when you enter and
22709 leave a group. More on the sequence of events later (@pxref{Spam
22710 ELisp Package Sequence of Events}).
22712 You get the following keyboard commands:
22722 @findex gnus-summary-mark-as-spam
22723 @code{gnus-summary-mark-as-spam}.
22725 Mark current article as spam, showing it with the @samp{$} mark.
22726 Whenever you see a spam article, make sure to mark its summary line
22727 with @kbd{M-d} before leaving the group. This is done automatically
22728 for unread articles in @emph{spam} groups.
22734 @findex spam-bogofilter-score
22735 @code{spam-bogofilter-score}.
22737 You must have Bogofilter installed for that command to work properly.
22743 Also, when you load @file{spam.el}, you will be able to customize its
22744 variables. Try @code{customize-group} on the @samp{spam} variable
22748 * Spam ELisp Package Sequence of Events::
22749 * Spam ELisp Package Filtering of Incoming Mail::
22750 * Spam ELisp Package Global Variables::
22751 * Spam ELisp Package Sorting and Score Display in Summary Buffer::
22752 * Spam ELisp Package Configuration Examples::
22753 * Blacklists and Whitelists::
22754 * BBDB Whitelists::
22755 * Gmane Spam Reporting::
22756 * Anti-spam Hashcash Payments::
22758 * Regular Expressions Header Matching::
22760 * SpamAssassin back end::
22761 * ifile spam filtering::
22762 * spam-stat spam filtering::
22764 * Extending the Spam ELisp package::
22767 @node Spam ELisp Package Sequence of Events
22768 @subsubsection Spam ELisp Package Sequence of Events
22769 @cindex spam filtering
22770 @cindex spam filtering sequence of events
22772 You must read this section to understand how @code{spam.el} works.
22773 Do not skip, speed-read, or glance through this section.
22775 There are two @emph{contact points}, if you will, between
22776 @code{spam.el} and the rest of Gnus: checking new mail for spam, and
22779 Getting new mail in Gnus is done in one of two ways. You can either
22780 split your incoming mail or you can classify new articles as ham or
22781 spam when you enter the group.
22783 Splitting incoming mail is better suited to mail back ends such as
22784 @code{nnml} or @code{nnimap} where new mail appears in a single file
22785 called a @dfn{Spool File}. See @xref{Spam ELisp Package Filtering of
22788 @vindex gnus-spam-autodetect
22789 @vindex gnus-spam-autodetect-methods
22790 For back ends such as @code{nntp} there is no incoming mail spool, so
22791 an alternate mechanism must be used. This may also happen for
22792 back ends where the server is in charge of splitting incoming mail, and
22793 Gnus does not do further splitting. The @code{spam-autodetect} and
22794 @code{spam-autodetect-methods} group parameters (accessible with
22795 @kbd{G c} and @kbd{G p} as usual), and the corresponding variables
22796 @code{gnus-spam-autodetect} and @code{gnus-spam-autodetect-methods}
22797 (accessible with @kbd{M-x customize-variable} as usual) can help.
22799 When @code{spam-autodetect} is used (you can turn it on for a
22800 group/topic or wholesale by regular expression matches, as needed), it
22801 hooks into the process of entering a group. Thus, entering a group
22802 with unseen or unread articles becomes the substitute for checking
22803 incoming mail. Whether only unseen articles or all unread articles
22804 will be processed is determined by the
22805 @code{spam-autodetect-recheck-messages}. When set to @code{t}, unread
22806 messages will be rechecked. You should probably stick with the
22807 default of only checking unseen messages.
22809 @code{spam-autodetect} grants the user at once more and less control
22810 of spam filtering. The user will have more control over each group's
22811 spam methods, so for instance the @samp{ding} group may have
22812 @code{spam-use-BBDB} as the autodetection method, while the
22813 @samp{suspect} group may have the @code{spam-use-blacklist} and
22814 @code{spam-use-bogofilter} methods enabled. Every article detected to
22815 be spam will be marked with the spam mark @samp{$} and processed on
22816 exit from the group as normal spam. The user has less control over
22817 the @emph{sequence} of checks, as he might with @code{spam-split}.
22819 When the newly split mail goes into groups, or messages are
22820 autodetected to be ham or spam, those groups must be exited (after
22821 entering, if needed) for further spam processing to happen. It
22822 matters whether the group is considered a ham group, a spam group, or
22823 is unclassified, based on its @code{spam-content} parameter
22824 (@pxref{Spam ELisp Package Global Variables}). Spam groups have the
22825 additional characteristic that, when entered, any unseen or unread
22826 articles (depending on the @code{spam-mark-only-unseen-as-spam}
22827 variable) will be marked as spam. Thus, mail split into a spam group
22828 gets automatically marked as spam when you enter the group.
22830 Thus, when you exit a group, the @code{spam-processors} are applied,
22831 if any are set, and the processed mail is moved to the
22832 @code{ham-process-destination} or the @code{spam-process-destination}
22833 depending on the article's classification. If the
22834 @code{ham-process-destination} or the @code{spam-process-destination},
22835 whichever is appropriate, are @code{nil}, the article is left in the
22838 If a spam is found in any group (this can be changed to only non-spam
22839 groups with @code{spam-move-spam-nonspam-groups-only}), it is
22840 processed by the active @code{spam-processors} (@pxref{Spam ELisp
22841 Package Global Variables}) when the group is exited. Furthermore, the
22842 spam is moved to the @code{spam-process-destination} (@pxref{Spam
22843 ELisp Package Global Variables}) for further training or deletion.
22844 You have to load the @code{gnus-registry.el} package and enable the
22845 @code{spam-log-to-registry} variable if you want spam to be processed
22846 no more than once. Thus, spam is detected and processed everywhere,
22847 which is what most people want. If the
22848 @code{spam-process-destination} is @code{nil}, the spam is marked as
22849 expired, which is usually the right thing to do.
22851 If spam can not be moved---because of a read-only back end such as
22852 @acronym{NNTP}, for example, it will be copied.
22854 If a ham mail is found in a ham group, as determined by the
22855 @code{ham-marks} parameter, it is processed as ham by the active ham
22856 @code{spam-processor} when the group is exited. With the variables
22857 @code{spam-process-ham-in-spam-groups} and
22858 @code{spam-process-ham-in-nonham-groups} the behavior can be further
22859 altered so ham found anywhere can be processed. You have to load the
22860 @code{gnus-registry.el} package and enable the
22861 @code{spam-log-to-registry} variable if you want ham to be processed
22862 no more than once. Thus, ham is detected and processed only when
22863 necessary, which is what most people want. More on this in
22864 @xref{Spam ELisp Package Configuration Examples}.
22866 If ham can not be moved---because of a read-only back end such as
22867 @acronym{NNTP}, for example, it will be copied.
22869 If all this seems confusing, don't worry. Soon it will be as natural
22870 as typing Lisp one-liners on a neural interface@dots{} err, sorry, that's
22871 50 years in the future yet. Just trust us, it's not so bad.
22873 @node Spam ELisp Package Filtering of Incoming Mail
22874 @subsubsection Spam ELisp Package Filtering of Incoming Mail
22875 @cindex spam filtering
22876 @cindex spam filtering incoming mail
22879 To use the @code{spam.el} facilities for incoming mail filtering, you
22880 must add the following to your fancy split list
22881 @code{nnmail-split-fancy} or @code{nnimap-split-fancy}:
22887 Note that the fancy split may be called @code{nnmail-split-fancy} or
22888 @code{nnimap-split-fancy}, depending on whether you use the nnmail or
22889 nnimap back ends to retrieve your mail.
22891 Also, @code{spam-split} will not modify incoming mail in any way.
22893 The @code{spam-split} function will process incoming mail and send the
22894 mail considered to be spam into the group name given by the variable
22895 @code{spam-split-group}. By default that group name is @samp{spam},
22896 but you can customize @code{spam-split-group}. Make sure the contents
22897 of @code{spam-split-group} are an @emph{unqualified} group name, for
22898 instance in an @code{nnimap} server @samp{your-server} the value
22899 @samp{spam} will turn out to be @samp{nnimap+your-server:spam}. The
22900 value @samp{nnimap+server:spam}, therefore, is wrong and will
22901 actually give you the group
22902 @samp{nnimap+your-server:nnimap+server:spam} which may or may not
22903 work depending on your server's tolerance for strange group names.
22905 You can also give @code{spam-split} a parameter,
22906 e.g. @code{spam-use-regex-headers} or @code{"maybe-spam"}. Why is
22909 Take these split rules (with @code{spam-use-regex-headers} and
22910 @code{spam-use-blackholes} set):
22913 nnimap-split-fancy '(|
22914 (any "ding" "ding")
22916 ;; @r{default mailbox}
22920 Now, the problem is that you want all ding messages to make it to the
22921 ding folder. But that will let obvious spam (for example, spam
22922 detected by SpamAssassin, and @code{spam-use-regex-headers}) through,
22923 when it's sent to the ding list. On the other hand, some messages to
22924 the ding list are from a mail server in the blackhole list, so the
22925 invocation of @code{spam-split} can't be before the ding rule.
22927 You can let SpamAssassin headers supersede ding rules, but all other
22928 @code{spam-split} rules (including a second invocation of the
22929 regex-headers check) will be after the ding rule:
22934 ;; @r{all spam detected by @code{spam-use-regex-headers} goes to @samp{regex-spam}}
22935 (: spam-split "regex-spam" 'spam-use-regex-headers)
22936 (any "ding" "ding")
22937 ;; @r{all other spam detected by spam-split goes to @code{spam-split-group}}
22939 ;; @r{default mailbox}
22943 This lets you invoke specific @code{spam-split} checks depending on
22944 your particular needs, and to target the results of those checks to a
22945 particular spam group. You don't have to throw all mail into all the
22946 spam tests. Another reason why this is nice is that messages to
22947 mailing lists you have rules for don't have to have resource-intensive
22948 blackhole checks performed on them. You could also specify different
22949 spam checks for your nnmail split vs. your nnimap split. Go crazy.
22951 You should still have specific checks such as
22952 @code{spam-use-regex-headers} set to @code{t}, even if you
22953 specifically invoke @code{spam-split} with the check. The reason is
22954 that when loading @file{spam.el}, some conditional loading is done
22955 depending on what @code{spam-use-xyz} variables you have set. This
22956 is usually not critical, though.
22958 @emph{Note for IMAP users}
22960 The boolean variable @code{nnimap-split-download-body} needs to be
22961 set, if you want to split based on the whole message instead of just
22962 the headers. By default, the nnimap back end will only retrieve the
22963 message headers. If you use a @emph{statistical} filter,
22964 e.g. @code{spam-check-bogofilter}, @code{spam-check-ifile}, or
22965 @code{spam-check-stat} (the splitters that can benefit from the full
22966 message body), this variable will be set automatically. It is not set
22967 for non-statistical back ends by default because it will slow
22968 @acronym{IMAP} down.
22970 @xref{Splitting in IMAP}.
22972 @node Spam ELisp Package Global Variables
22973 @subsubsection Spam ELisp Package Global Variables
22974 @cindex spam filtering
22975 @cindex spam filtering variables
22976 @cindex spam variables
22979 @vindex gnus-spam-process-newsgroups
22980 The concepts of ham processors and spam processors are very important.
22981 Ham processors and spam processors for a group can be set with the
22982 @code{spam-process} group parameter, or the
22983 @code{gnus-spam-process-newsgroups} variable. Ham processors take
22984 mail known to be non-spam (@emph{ham}) and process it in some way so
22985 that later similar mail will also be considered non-spam. Spam
22986 processors take mail known to be spam and process it so similar spam
22987 will be detected later.
22989 The format of the spam or ham processor entry used to be a symbol,
22990 but now it is a @sc{cons} cell. See the individual spam processor entries
22991 for more information.
22993 @vindex gnus-spam-newsgroup-contents
22994 Gnus learns from the spam you get. You have to collect your spam in
22995 one or more spam groups, and set or customize the variable
22996 @code{spam-junk-mailgroups} as appropriate. You can also declare
22997 groups to contain spam by setting their group parameter
22998 @code{spam-contents} to @code{gnus-group-spam-classification-spam}, or
22999 by customizing the corresponding variable
23000 @code{gnus-spam-newsgroup-contents}. The @code{spam-contents} group
23001 parameter and the @code{gnus-spam-newsgroup-contents} variable can
23002 also be used to declare groups as @emph{ham} groups if you set their
23003 classification to @code{gnus-group-spam-classification-ham}. If
23004 groups are not classified by means of @code{spam-junk-mailgroups},
23005 @code{spam-contents}, or @code{gnus-spam-newsgroup-contents}, they are
23006 considered @emph{unclassified}. All groups are unclassified by
23009 @vindex gnus-spam-mark
23011 In spam groups, all messages are considered to be spam by default:
23012 they get the @samp{$} mark (@code{gnus-spam-mark}) when you enter the
23013 group. If you have seen a message, had it marked as spam, then
23014 unmarked it, it won't be marked as spam when you enter the group
23015 thereafter. You can disable that behavior, so all unread messages
23016 will get the @samp{$} mark, if you set the
23017 @code{spam-mark-only-unseen-as-spam} parameter to @code{nil}. You
23018 should remove the @samp{$} mark when you are in the group summary
23019 buffer for every message that is not spam after all. To remove the
23020 @samp{$} mark, you can use @kbd{M-u} to ``unread'' the article, or
23021 @kbd{d} for declaring it read the non-spam way. When you leave a
23022 group, all spam-marked (@samp{$}) articles are sent to a spam
23023 processor which will study them as spam samples.
23025 Messages may also be deleted in various other ways, and unless
23026 @code{ham-marks} group parameter gets overridden below, marks @samp{R}
23027 and @samp{r} for default read or explicit delete, marks @samp{X} and
23028 @samp{K} for automatic or explicit kills, as well as mark @samp{Y} for
23029 low scores, are all considered to be associated with articles which
23030 are not spam. This assumption might be false, in particular if you
23031 use kill files or score files as means for detecting genuine spam, you
23032 should then adjust the @code{ham-marks} group parameter.
23035 You can customize this group or topic parameter to be the list of
23036 marks you want to consider ham. By default, the list contains the
23037 deleted, read, killed, kill-filed, and low-score marks (the idea is
23038 that these articles have been read, but are not spam). It can be
23039 useful to also include the tick mark in the ham marks. It is not
23040 recommended to make the unread mark a ham mark, because it normally
23041 indicates a lack of classification. But you can do it, and we'll be
23046 You can customize this group or topic parameter to be the list of
23047 marks you want to consider spam. By default, the list contains only
23048 the spam mark. It is not recommended to change that, but you can if
23049 you really want to.
23052 When you leave @emph{any} group, regardless of its
23053 @code{spam-contents} classification, all spam-marked articles are sent
23054 to a spam processor, which will study these as spam samples. If you
23055 explicit kill a lot, you might sometimes end up with articles marked
23056 @samp{K} which you never saw, and which might accidentally contain
23057 spam. Best is to make sure that real spam is marked with @samp{$},
23060 @vindex gnus-ham-process-destinations
23061 When you leave a @emph{spam} group, all spam-marked articles are
23062 marked as expired after processing with the spam processor. This is
23063 not done for @emph{unclassified} or @emph{ham} groups. Also, any
23064 @strong{ham} articles in a spam group will be moved to a location
23065 determined by either the @code{ham-process-destination} group
23066 parameter or a match in the @code{gnus-ham-process-destinations}
23067 variable, which is a list of regular expressions matched with group
23068 names (it's easiest to customize this variable with @kbd{M-x
23069 customize-variable @key{RET} gnus-ham-process-destinations}). Each
23070 group name list is a standard Lisp list, if you prefer to customize
23071 the variable manually. If the @code{ham-process-destination}
23072 parameter is not set, ham articles are left in place. If the
23073 @code{spam-mark-ham-unread-before-move-from-spam-group} parameter is
23074 set, the ham articles are marked as unread before being moved.
23076 If ham can not be moved---because of a read-only back end such as
23077 @acronym{NNTP}, for example, it will be copied.
23079 Note that you can use multiples destinations per group or regular
23080 expression! This enables you to send your ham to a regular mail
23081 group and to a @emph{ham training} group.
23083 When you leave a @emph{ham} group, all ham-marked articles are sent to
23084 a ham processor, which will study these as non-spam samples.
23086 @vindex spam-process-ham-in-spam-groups
23087 By default the variable @code{spam-process-ham-in-spam-groups} is
23088 @code{nil}. Set it to @code{t} if you want ham found in spam groups
23089 to be processed. Normally this is not done, you are expected instead
23090 to send your ham to a ham group and process it there.
23092 @vindex spam-process-ham-in-nonham-groups
23093 By default the variable @code{spam-process-ham-in-nonham-groups} is
23094 @code{nil}. Set it to @code{t} if you want ham found in non-ham (spam
23095 or unclassified) groups to be processed. Normally this is not done,
23096 you are expected instead to send your ham to a ham group and process
23099 @vindex gnus-spam-process-destinations
23100 When you leave a @emph{ham} or @emph{unclassified} group, all
23101 @strong{spam} articles are moved to a location determined by either
23102 the @code{spam-process-destination} group parameter or a match in the
23103 @code{gnus-spam-process-destinations} variable, which is a list of
23104 regular expressions matched with group names (it's easiest to
23105 customize this variable with @kbd{M-x customize-variable @key{RET}
23106 gnus-spam-process-destinations}). Each group name list is a standard
23107 Lisp list, if you prefer to customize the variable manually. If the
23108 @code{spam-process-destination} parameter is not set, the spam
23109 articles are only expired. The group name is fully qualified, meaning
23110 that if you see @samp{nntp:servername} before the group name in the
23111 group buffer then you need it here as well.
23113 If spam can not be moved---because of a read-only back end such as
23114 @acronym{NNTP}, for example, it will be copied.
23116 Note that you can use multiples destinations per group or regular
23117 expression! This enables you to send your spam to multiple @emph{spam
23120 @vindex spam-log-to-registry
23121 The problem with processing ham and spam is that Gnus doesn't track
23122 this processing by default. Enable the @code{spam-log-to-registry}
23123 variable so @code{spam.el} will use @code{gnus-registry.el} to track
23124 what articles have been processed, and avoid processing articles
23125 multiple times. Keep in mind that if you limit the number of registry
23126 entries, this won't work as well as it does without a limit.
23128 @vindex spam-mark-only-unseen-as-spam
23129 Set this variable if you want only unseen articles in spam groups to
23130 be marked as spam. By default, it is set. If you set it to
23131 @code{nil}, unread articles will also be marked as spam.
23133 @vindex spam-mark-ham-unread-before-move-from-spam-group
23134 Set this variable if you want ham to be unmarked before it is moved
23135 out of the spam group. This is very useful when you use something
23136 like the tick mark @samp{!} to mark ham---the article will be placed
23137 in your @code{ham-process-destination}, unmarked as if it came fresh
23138 from the mail server.
23140 @vindex spam-autodetect-recheck-messages
23141 When autodetecting spam, this variable tells @code{spam.el} whether
23142 only unseen articles or all unread articles should be checked for
23143 spam. It is recommended that you leave it off.
23145 @node Spam ELisp Package Sorting and Score Display in Summary Buffer
23146 @subsubsection Spam ELisp Package Sorting and Score Display in Summary Buffer
23147 @cindex spam scoring
23148 @cindex spam sorting
23149 @cindex spam score summary buffer
23150 @cindex spam sort summary buffer
23153 You can display the spam score of articles in your summary buffer, and
23154 you can sort articles by their spam score.
23156 First you need to decide which back end you will be using. If you use
23157 the @code{spam-use-spamassassin},
23158 @code{spam-use-spamassassin-headers}, or @code{spam-use-regex-headers}
23159 back end, the @code{X-Spam-Status} header will be used. If you use
23160 @code{spam-use-bogofilter}, the @code{X-Bogosity} header will be used.
23161 If you use @code{spam-use-crm114}, any header that matches the CRM114
23162 score format will be used. As long as you set the appropriate back end
23163 variable to t @emph{before} you load @file{spam.el}, you will be
23164 fine. @code{spam.el} will automatically add the right header to the
23165 internal Gnus list of required headers.
23167 To show the spam score in your summary buffer, add this line to your
23168 @code{gnus.el} file (note @code{spam.el} does not do that by default
23169 so it won't override any existing @code{S} formats you may have).
23172 (defalias 'gnus-user-format-function-S 'spam-user-format-function-S)
23175 Now just set your summary line format to use @code{%uS}. Here's an
23176 example that formats the spam score in a 5-character field:
23179 (setq gnus-summary-line-format
23180 "%U%R %10&user-date; $%5uS %6k %B %(%4L: %*%-25,25a%) %s \n")
23183 Finally, to sort by spam status, either do it globally:
23187 gnus-show-threads nil
23188 gnus-article-sort-functions
23189 '(spam-article-sort-by-spam-status))
23192 or per group (@pxref{Sorting the Summary Buffer}).
23194 @node Spam ELisp Package Configuration Examples
23195 @subsubsection Spam ELisp Package Configuration Examples
23196 @cindex spam filtering
23197 @cindex spam filtering configuration examples
23198 @cindex spam configuration examples
23201 @subsubheading Ted's setup
23203 From Ted Zlatanov <tzz@@lifelogs.com>.
23205 ;; @r{for @code{gnus-registry-split-fancy-with-parent} and spam autodetection}
23206 ;; @r{see @file{gnus-registry.el} for more information}
23207 (gnus-registry-initialize)
23210 ;; @r{I like @kbd{C-s} for marking spam}
23211 (define-key gnus-summary-mode-map "\C-s" 'gnus-summary-mark-as-spam)
23214 spam-log-to-registry t ; @r{for spam autodetection}
23216 spam-use-regex-headers t ; @r{catch X-Spam-Flag (SpamAssassin)}
23217 ;; @r{all groups with @samp{spam} in the name contain spam}
23218 gnus-spam-newsgroup-contents
23219 '(("spam" gnus-group-spam-classification-spam))
23220 ;; @r{see documentation for these}
23221 spam-move-spam-nonspam-groups-only nil
23222 spam-mark-only-unseen-as-spam t
23223 spam-mark-ham-unread-before-move-from-spam-group t
23224 nnimap-split-rule 'nnimap-split-fancy
23225 ;; @r{understand what this does before you copy it to your own setup!}
23226 nnimap-split-fancy '(|
23227 ;; @r{trace references to parents and put in their group}
23228 (: gnus-registry-split-fancy-with-parent)
23229 ;; @r{this will catch server-side SpamAssassin tags}
23230 (: spam-split 'spam-use-regex-headers)
23231 (any "ding" "ding")
23232 ;; @r{note that spam by default will go to @samp{spam}}
23234 ;; @r{default mailbox}
23237 ;; @r{my parameters, set with @kbd{G p}}
23239 ;; @r{all nnml groups, and all nnimap groups except}
23240 ;; @r{@samp{nnimap+mail.lifelogs.com:train} and}
23241 ;; @r{@samp{nnimap+mail.lifelogs.com:spam}: any spam goes to nnimap training,}
23242 ;; @r{because it must have been detected manually}
23244 ((spam-process-destination . "nnimap+mail.lifelogs.com:train"))
23246 ;; @r{all @acronym{NNTP} groups}
23247 ;; @r{autodetect spam with the blacklist and ham with the BBDB}
23248 ((spam-autodetect-methods spam-use-blacklist spam-use-BBDB)
23249 ;; @r{send all spam to the training group}
23250 (spam-process-destination . "nnimap+mail.lifelogs.com:train"))
23252 ;; @r{only some @acronym{NNTP} groups, where I want to autodetect spam}
23253 ((spam-autodetect . t))
23255 ;; @r{my nnimap @samp{nnimap+mail.lifelogs.com:spam} group}
23257 ;; @r{this is a spam group}
23258 ((spam-contents gnus-group-spam-classification-spam)
23260 ;; @r{any spam (which happens when I enter for all unseen messages,}
23261 ;; @r{because of the @code{gnus-spam-newsgroup-contents} setting above), goes to}
23262 ;; @r{@samp{nnimap+mail.lifelogs.com:train} unless I mark it as ham}
23264 (spam-process-destination "nnimap+mail.lifelogs.com:train")
23266 ;; @r{any ham goes to my @samp{nnimap+mail.lifelogs.com:mail} folder, but}
23267 ;; @r{also to my @samp{nnimap+mail.lifelogs.com:trainham} folder for training}
23269 (ham-process-destination "nnimap+mail.lifelogs.com:mail"
23270 "nnimap+mail.lifelogs.com:trainham")
23271 ;; @r{in this group, only @samp{!} marks are ham}
23273 (gnus-ticked-mark))
23274 ;; @r{remembers senders in the blacklist on the way out---this is}
23275 ;; @r{definitely not needed, it just makes me feel better}
23276 (spam-process (gnus-group-spam-exit-processor-blacklist)))
23278 ;; @r{Later, on the @acronym{IMAP} server I use the @samp{train} group for training}
23279 ;; @r{SpamAssassin to recognize spam, and the @samp{trainham} group fora}
23280 ;; @r{recognizing ham---but Gnus has nothing to do with it.}
23284 @subsubheading Using @code{spam.el} on an IMAP server with a statistical filter on the server
23285 From Reiner Steib <reiner.steib@@gmx.de>.
23287 My provider has set up bogofilter (in combination with @acronym{DCC}) on
23288 the mail server (@acronym{IMAP}). Recognized spam goes to
23289 @samp{spam.detected}, the rest goes through the normal filter rules,
23290 i.e. to @samp{some.folder} or to @samp{INBOX}. Training on false
23291 positives or negatives is done by copying or moving the article to
23292 @samp{training.ham} or @samp{training.spam} respectively. A cron job on
23293 the server feeds those to bogofilter with the suitable ham or spam
23294 options and deletes them from the @samp{training.ham} and
23295 @samp{training.spam} folders.
23297 With the following entries in @code{gnus-parameters}, @code{spam.el}
23298 does most of the job for me:
23301 ("nnimap:spam\\.detected"
23302 (gnus-article-sort-functions '(gnus-article-sort-by-chars))
23303 (ham-process-destination "nnimap:INBOX" "nnimap:training.ham")
23304 (spam-contents gnus-group-spam-classification-spam))
23305 ("nnimap:\\(INBOX\\|other-folders\\)"
23306 (spam-process-destination . "nnimap:training.spam")
23307 (spam-contents gnus-group-spam-classification-ham))
23312 @item @b{The Spam folder:}
23314 In the folder @samp{spam.detected}, I have to check for false positives
23315 (i.e. legitimate mails, that were wrongly judged as spam by
23316 bogofilter or DCC).
23318 Because of the @code{gnus-group-spam-classification-spam} entry, all
23319 messages are marked as spam (with @code{$}). When I find a false
23320 positive, I mark the message with some other ham mark (@code{ham-marks},
23321 @ref{Spam ELisp Package Global Variables}). On group exit, those
23322 messages are copied to both groups, @samp{INBOX} (where I want to have
23323 the article) and @samp{training.ham} (for training bogofilter) and
23324 deleted from the @samp{spam.detected} folder.
23326 The @code{gnus-article-sort-by-chars} entry simplifies detection of
23327 false positives for me. I receive lots of worms (sweN, @dots{}), that all
23328 have a similar size. Grouping them by size (i.e. chars) makes finding
23329 other false positives easier. (Of course worms aren't @i{spam}
23330 (@acronym{UCE}, @acronym{UBE}) strictly speaking. Anyhow, bogofilter is
23331 an excellent tool for filtering those unwanted mails for me.)
23333 @item @b{Ham folders:}
23335 In my ham folders, I just hit @kbd{S x}
23336 (@code{gnus-summary-mark-as-spam}) whenever I see an unrecognized spam
23337 mail (false negative). On group exit, those messages are moved to
23338 @samp{training.ham}.
23341 @subsubheading Reporting spam articles in Gmane groups with @code{spam-report.el}
23343 From Reiner Steib <reiner.steib@@gmx.de>.
23345 With following entry in @code{gnus-parameters}, @kbd{S x}
23346 (@code{gnus-summary-mark-as-spam}) marks articles in @code{gmane.*}
23347 groups as spam and reports the to Gmane at group exit:
23351 (spam-process (gnus-group-spam-exit-processor-report-gmane)))
23354 Additionally, I use @code{(setq spam-report-gmane-use-article-number nil)}
23355 because I don't read the groups directly from news.gmane.org, but
23356 through my local news server (leafnode). I.e. the article numbers are
23357 not the same as on news.gmane.org, thus @code{spam-report.el} has to check
23358 the @code{X-Report-Spam} header to find the correct number.
23360 @node Blacklists and Whitelists
23361 @subsubsection Blacklists and Whitelists
23362 @cindex spam filtering
23363 @cindex whitelists, spam filtering
23364 @cindex blacklists, spam filtering
23367 @defvar spam-use-blacklist
23369 Set this variable to @code{t} if you want to use blacklists when
23370 splitting incoming mail. Messages whose senders are in the blacklist
23371 will be sent to the @code{spam-split-group}. This is an explicit
23372 filter, meaning that it acts only on mail senders @emph{declared} to
23377 @defvar spam-use-whitelist
23379 Set this variable to @code{t} if you want to use whitelists when
23380 splitting incoming mail. Messages whose senders are not in the
23381 whitelist will be sent to the next spam-split rule. This is an
23382 explicit filter, meaning that unless someone is in the whitelist, their
23383 messages are not assumed to be spam or ham.
23387 @defvar spam-use-whitelist-exclusive
23389 Set this variable to @code{t} if you want to use whitelists as an
23390 implicit filter, meaning that every message will be considered spam
23391 unless the sender is in the whitelist. Use with care.
23395 @defvar gnus-group-spam-exit-processor-blacklist
23397 Add this symbol to a group's @code{spam-process} parameter by
23398 customizing the group parameters or the
23399 @code{gnus-spam-process-newsgroups} variable. When this symbol is
23400 added to a group's @code{spam-process} parameter, the senders of
23401 spam-marked articles will be added to the blacklist.
23405 Instead of the obsolete
23406 @code{gnus-group-spam-exit-processor-blacklist}, it is recommended
23407 that you use @code{'(spam spam-use-blacklist)}. Everything will work
23408 the same way, we promise.
23412 @defvar gnus-group-ham-exit-processor-whitelist
23414 Add this symbol to a group's @code{spam-process} parameter by
23415 customizing the group parameters or the
23416 @code{gnus-spam-process-newsgroups} variable. When this symbol is
23417 added to a group's @code{spam-process} parameter, the senders of
23418 ham-marked articles in @emph{ham} groups will be added to the
23423 Instead of the obsolete
23424 @code{gnus-group-ham-exit-processor-whitelist}, it is recommended
23425 that you use @code{'(ham spam-use-whitelist)}. Everything will work
23426 the same way, we promise.
23430 Blacklists are lists of regular expressions matching addresses you
23431 consider to be spam senders. For instance, to block mail from any
23432 sender at @samp{vmadmin.com}, you can put @samp{vmadmin.com} in your
23433 blacklist. You start out with an empty blacklist. Blacklist entries
23434 use the Emacs regular expression syntax.
23436 Conversely, whitelists tell Gnus what addresses are considered
23437 legitimate. All messages from whitelisted addresses are considered
23438 non-spam. Also see @ref{BBDB Whitelists}. Whitelist entries use the
23439 Emacs regular expression syntax.
23441 The blacklist and whitelist file locations can be customized with the
23442 @code{spam-directory} variable (@file{~/News/spam} by default), or
23443 the @code{spam-whitelist} and @code{spam-blacklist} variables
23444 directly. The whitelist and blacklist files will by default be in the
23445 @code{spam-directory} directory, named @file{whitelist} and
23446 @file{blacklist} respectively.
23448 @node BBDB Whitelists
23449 @subsubsection BBDB Whitelists
23450 @cindex spam filtering
23451 @cindex BBDB whitelists, spam filtering
23452 @cindex BBDB, spam filtering
23455 @defvar spam-use-BBDB
23457 Analogous to @code{spam-use-whitelist} (@pxref{Blacklists and
23458 Whitelists}), but uses the BBDB as the source of whitelisted
23459 addresses, without regular expressions. You must have the BBDB loaded
23460 for @code{spam-use-BBDB} to work properly. Messages whose senders are
23461 not in the BBDB will be sent to the next spam-split rule. This is an
23462 explicit filter, meaning that unless someone is in the BBDB, their
23463 messages are not assumed to be spam or ham.
23467 @defvar spam-use-BBDB-exclusive
23469 Set this variable to @code{t} if you want to use the BBDB as an
23470 implicit filter, meaning that every message will be considered spam
23471 unless the sender is in the BBDB. Use with care. Only sender
23472 addresses in the BBDB will be allowed through; all others will be
23473 classified as spammers.
23475 While @code{spam-use-BBDB-exclusive} @emph{can} be used as an alias
23476 for @code{spam-use-BBDB} as far as @code{spam.el} is concerned, it is
23477 @emph{not} a separate back end. If you set
23478 @code{spam-use-BBDB-exclusive} to t, @emph{all} your BBDB splitting
23483 @defvar gnus-group-ham-exit-processor-BBDB
23485 Add this symbol to a group's @code{spam-process} parameter by
23486 customizing the group parameters or the
23487 @code{gnus-spam-process-newsgroups} variable. When this symbol is
23488 added to a group's @code{spam-process} parameter, the senders of
23489 ham-marked articles in @emph{ham} groups will be added to the
23494 Instead of the obsolete
23495 @code{gnus-group-ham-exit-processor-BBDB}, it is recommended
23496 that you use @code{'(ham spam-use-BBDB)}. Everything will work
23497 the same way, we promise.
23501 @node Gmane Spam Reporting
23502 @subsubsection Gmane Spam Reporting
23503 @cindex spam reporting
23504 @cindex Gmane, spam reporting
23505 @cindex Gmane, spam reporting
23508 @defvar gnus-group-spam-exit-processor-report-gmane
23510 Add this symbol to a group's @code{spam-process} parameter by
23511 customizing the group parameters or the
23512 @code{gnus-spam-process-newsgroups} variable. When this symbol is
23513 added to a group's @code{spam-process} parameter, the spam-marked
23514 articles groups will be reported to the Gmane administrators via a
23517 Gmane can be found at @uref{http://gmane.org}.
23521 Instead of the obsolete
23522 @code{gnus-group-spam-exit-processor-report-gmane}, it is recommended
23523 that you use @code{'(spam spam-use-gmane)}. Everything will work the
23524 same way, we promise.
23528 @defvar spam-report-gmane-use-article-number
23530 This variable is @code{t} by default. Set it to @code{nil} if you are
23531 running your own news server, for instance, and the local article
23532 numbers don't correspond to the Gmane article numbers. When
23533 @code{spam-report-gmane-use-article-number} is @code{nil},
23534 @code{spam-report.el} will use the @code{X-Report-Spam} header that
23539 @node Anti-spam Hashcash Payments
23540 @subsubsection Anti-spam Hashcash Payments
23541 @cindex spam filtering
23542 @cindex hashcash, spam filtering
23545 @defvar spam-use-hashcash
23547 Similar to @code{spam-use-whitelist} (@pxref{Blacklists and
23548 Whitelists}), but uses hashcash tokens for whitelisting messages
23549 instead of the sender address. Messages without a hashcash payment
23550 token will be sent to the next spam-split rule. This is an explicit
23551 filter, meaning that unless a hashcash token is found, the messages
23552 are not assumed to be spam or ham.
23557 @subsubsection Blackholes
23558 @cindex spam filtering
23559 @cindex blackholes, spam filtering
23562 @defvar spam-use-blackholes
23564 This option is disabled by default. You can let Gnus consult the
23565 blackhole-type distributed spam processing systems (DCC, for instance)
23566 when you set this option. The variable @code{spam-blackhole-servers}
23567 holds the list of blackhole servers Gnus will consult. The current
23568 list is fairly comprehensive, but make sure to let us know if it
23569 contains outdated servers.
23571 The blackhole check uses the @code{dig.el} package, but you can tell
23572 @code{spam.el} to use @code{dns.el} instead for better performance if
23573 you set @code{spam-use-dig} to @code{nil}. It is not recommended at
23574 this time to set @code{spam-use-dig} to @code{nil} despite the
23575 possible performance improvements, because some users may be unable to
23576 use it, but you can try it and see if it works for you.
23580 @defvar spam-blackhole-servers
23582 The list of servers to consult for blackhole checks.
23586 @defvar spam-blackhole-good-server-regex
23588 A regular expression for IPs that should not be checked against the
23589 blackhole server list. When set to @code{nil}, it has no effect.
23593 @defvar spam-use-dig
23595 Use the @code{dig.el} package instead of the @code{dns.el} package.
23596 The default setting of @code{t} is recommended.
23600 Blackhole checks are done only on incoming mail. There is no spam or
23601 ham processor for blackholes.
23603 @node Regular Expressions Header Matching
23604 @subsubsection Regular Expressions Header Matching
23605 @cindex spam filtering
23606 @cindex regular expressions header matching, spam filtering
23609 @defvar spam-use-regex-headers
23611 This option is disabled by default. You can let Gnus check the
23612 message headers against lists of regular expressions when you set this
23613 option. The variables @code{spam-regex-headers-spam} and
23614 @code{spam-regex-headers-ham} hold the list of regular expressions.
23615 Gnus will check against the message headers to determine if the
23616 message is spam or ham, respectively.
23620 @defvar spam-regex-headers-spam
23622 The list of regular expressions that, when matched in the headers of
23623 the message, positively identify it as spam.
23627 @defvar spam-regex-headers-ham
23629 The list of regular expressions that, when matched in the headers of
23630 the message, positively identify it as ham.
23634 Regular expression header checks are done only on incoming mail.
23635 There is no specific spam or ham processor for regular expressions.
23638 @subsubsection Bogofilter
23639 @cindex spam filtering
23640 @cindex bogofilter, spam filtering
23643 @defvar spam-use-bogofilter
23645 Set this variable if you want @code{spam-split} to use Eric Raymond's
23648 With a minimum of care for associating the @samp{$} mark for spam
23649 articles only, Bogofilter training all gets fairly automatic. You
23650 should do this until you get a few hundreds of articles in each
23651 category, spam or not. The command @kbd{S t} in summary mode, either
23652 for debugging or for curiosity, shows the @emph{spamicity} score of
23653 the current article (between 0.0 and 1.0).
23655 Bogofilter determines if a message is spam based on a specific
23656 threshold. That threshold can be customized, consult the Bogofilter
23659 If the @code{bogofilter} executable is not in your path, Bogofilter
23660 processing will be turned off.
23662 You should not enable this if you use @code{spam-use-bogofilter-headers}.
23666 @defvar spam-use-bogofilter-headers
23668 Set this variable if you want @code{spam-split} to use Eric Raymond's
23669 speedy Bogofilter, looking only at the message headers. It works
23670 similarly to @code{spam-use-bogofilter}, but the @code{X-Bogosity} header
23671 must be in the message already. Normally you would do this with a
23672 procmail recipe or something similar; consult the Bogofilter
23673 installation documents for details.
23675 You should not enable this if you use @code{spam-use-bogofilter}.
23679 @defvar gnus-group-spam-exit-processor-bogofilter
23680 Add this symbol to a group's @code{spam-process} parameter by
23681 customizing the group parameters or the
23682 @code{gnus-spam-process-newsgroups} variable. When this symbol is
23683 added to a group's @code{spam-process} parameter, spam-marked articles
23684 will be added to the Bogofilter spam database.
23688 Instead of the obsolete
23689 @code{gnus-group-spam-exit-processor-bogofilter}, it is recommended
23690 that you use @code{'(spam spam-use-bogofilter)}. Everything will work
23691 the same way, we promise.
23694 @defvar gnus-group-ham-exit-processor-bogofilter
23695 Add this symbol to a group's @code{spam-process} parameter by
23696 customizing the group parameters or the
23697 @code{gnus-spam-process-newsgroups} variable. When this symbol is
23698 added to a group's @code{spam-process} parameter, the ham-marked
23699 articles in @emph{ham} groups will be added to the Bogofilter database
23700 of non-spam messages.
23704 Instead of the obsolete
23705 @code{gnus-group-ham-exit-processor-bogofilter}, it is recommended
23706 that you use @code{'(ham spam-use-bogofilter)}. Everything will work
23707 the same way, we promise.
23710 @defvar spam-bogofilter-database-directory
23712 This is the directory where Bogofilter will store its databases. It
23713 is not specified by default, so Bogofilter will use its own default
23714 database directory.
23718 The Bogofilter mail classifier is similar to @command{ifile} in intent and
23719 purpose. A ham and a spam processor are provided, plus the
23720 @code{spam-use-bogofilter} and @code{spam-use-bogofilter-headers}
23721 variables to indicate to spam-split that Bogofilter should either be
23722 used, or has already been used on the article. The 0.9.2.1 version of
23723 Bogofilter was used to test this functionality.
23725 @node SpamAssassin back end
23726 @subsubsection SpamAssassin back end
23727 @cindex spam filtering
23728 @cindex spamassassin, spam filtering
23731 @defvar spam-use-spamassassin
23733 Set this variable if you want @code{spam-split} to use SpamAssassin.
23735 SpamAssassin assigns a score to each article based on a set of rules
23736 and tests, including a Bayesian filter. The Bayesian filter can be
23737 trained by associating the @samp{$} mark for spam articles. The
23738 spam score can be viewed by using the command @kbd{S t} in summary
23741 If you set this variable, each article will be processed by
23742 SpamAssassin when @code{spam-split} is called. If your mail is
23743 preprocessed by SpamAssassin, and you want to just use the
23744 SpamAssassin headers, set @code{spam-use-spamassassin-headers}
23747 You should not enable this is you use
23748 @code{spam-use-spamassassin-headers}.
23752 @defvar spam-use-spamassassin-headers
23754 Set this variable if your mail is preprocessed by SpamAssassin and
23755 want @code{spam-split} to split based on the SpamAssassin headers.
23757 You should not enable this is you use @code{spam-use-spamassassin}.
23761 @defvar spam-spamassassin-path
23763 This variable points to the SpamAssassin executable. If you have
23764 @code{spamd} running, you can set this variable to the @code{spamc}
23765 executable for faster processing. See the SpamAssassin documentation
23766 for more information on @code{spamd}/@code{spamc}.
23770 SpamAssassin is a powerful and flexible spam filter that uses a wide
23771 variety of tests to identify spam. A ham and a spam processors are
23772 provided, plus the @code{spam-use-spamassassin} and
23773 @code{spam-use-spamassassin-headers} variables to indicate to
23774 spam-split that SpamAssassin should be either used, or has already
23775 been used on the article. The 2.63 version of SpamAssassin was used
23776 to test this functionality.
23778 @node ifile spam filtering
23779 @subsubsection ifile spam filtering
23780 @cindex spam filtering
23781 @cindex ifile, spam filtering
23784 @defvar spam-use-ifile
23786 Enable this variable if you want @code{spam-split} to use @command{ifile}, a
23787 statistical analyzer similar to Bogofilter.
23791 @defvar spam-ifile-all-categories
23793 Enable this variable if you want @code{spam-use-ifile} to give you all
23794 the ifile categories, not just spam/non-spam. If you use this, make
23795 sure you train ifile as described in its documentation.
23799 @defvar spam-ifile-spam-category
23801 This is the category of spam messages as far as ifile is concerned.
23802 The actual string used is irrelevant, but you probably want to leave
23803 the default value of @samp{spam}.
23806 @defvar spam-ifile-database-path
23808 This is the filename for the ifile database. It is not specified by
23809 default, so ifile will use its own default database name.
23813 The ifile mail classifier is similar to Bogofilter in intent and
23814 purpose. A ham and a spam processor are provided, plus the
23815 @code{spam-use-ifile} variable to indicate to spam-split that ifile
23816 should be used. The 1.2.1 version of ifile was used to test this
23819 @node spam-stat spam filtering
23820 @subsubsection spam-stat spam filtering
23821 @cindex spam filtering
23822 @cindex spam-stat, spam filtering
23826 @xref{Filtering Spam Using Statistics with spam-stat}.
23828 @defvar spam-use-stat
23830 Enable this variable if you want @code{spam-split} to use
23831 spam-stat.el, an Emacs Lisp statistical analyzer.
23835 @defvar gnus-group-spam-exit-processor-stat
23836 Add this symbol to a group's @code{spam-process} parameter by
23837 customizing the group parameters or the
23838 @code{gnus-spam-process-newsgroups} variable. When this symbol is
23839 added to a group's @code{spam-process} parameter, the spam-marked
23840 articles will be added to the spam-stat database of spam messages.
23844 Instead of the obsolete
23845 @code{gnus-group-spam-exit-processor-stat}, it is recommended
23846 that you use @code{'(spam spam-use-stat)}. Everything will work
23847 the same way, we promise.
23850 @defvar gnus-group-ham-exit-processor-stat
23851 Add this symbol to a group's @code{spam-process} parameter by
23852 customizing the group parameters or the
23853 @code{gnus-spam-process-newsgroups} variable. When this symbol is
23854 added to a group's @code{spam-process} parameter, the ham-marked
23855 articles in @emph{ham} groups will be added to the spam-stat database
23856 of non-spam messages.
23860 Instead of the obsolete
23861 @code{gnus-group-ham-exit-processor-stat}, it is recommended
23862 that you use @code{'(ham spam-use-stat)}. Everything will work
23863 the same way, we promise.
23866 This enables @code{spam.el} to cooperate with @file{spam-stat.el}.
23867 @file{spam-stat.el} provides an internal (Lisp-only) spam database,
23868 which unlike ifile or Bogofilter does not require external programs.
23869 A spam and a ham processor, and the @code{spam-use-stat} variable for
23870 @code{spam-split} are provided.
23873 @subsubsection Using SpamOracle with Gnus
23874 @cindex spam filtering
23878 An easy way to filter out spam is to use SpamOracle. SpamOracle is an
23879 statistical mail filtering tool written by Xavier Leroy and needs to be
23880 installed separately.
23882 There are several ways to use SpamOracle with Gnus. In all cases, your
23883 mail is piped through SpamOracle in its @emph{mark} mode. SpamOracle will
23884 then enter an @samp{X-Spam} header indicating whether it regards the
23885 mail as a spam mail or not.
23887 One possibility is to run SpamOracle as a @code{:prescript} from the
23888 @xref{Mail Source Specifiers}, (@pxref{SpamAssassin}). This method has
23889 the advantage that the user can see the @emph{X-Spam} headers.
23891 The easiest method is to make @code{spam.el} (@pxref{Filtering Spam
23892 Using The Spam ELisp Package}) call SpamOracle.
23894 @vindex spam-use-spamoracle
23895 To enable SpamOracle usage by @code{spam.el}, set the variable
23896 @code{spam-use-spamoracle} to @code{t} and configure the
23897 @code{nnmail-split-fancy} or @code{nnimap-split-fancy} as described in
23898 the section @xref{Filtering Spam Using The Spam ELisp Package}. In
23899 this example the @samp{INBOX} of an nnimap server is filtered using
23900 SpamOracle. Mails recognized as spam mails will be moved to
23901 @code{spam-split-group}, @samp{Junk} in this case. Ham messages stay
23905 (setq spam-use-spamoracle t
23906 spam-split-group "Junk"
23907 nnimap-split-inbox '("INBOX")
23908 nnimap-split-rule 'nnimap-split-fancy
23909 nnimap-split-fancy '(| (: spam-split) "INBOX"))
23912 @defvar spam-use-spamoracle
23913 Set to @code{t} if you want Gnus to enable spam filtering using
23917 @defvar spam-spamoracle-binary
23918 Gnus uses the SpamOracle binary called @file{spamoracle} found in the
23919 user's PATH. Using the variable @code{spam-spamoracle-binary}, this
23923 @defvar spam-spamoracle-database
23924 By default, SpamOracle uses the file @file{~/.spamoracle.db} as a database to
23925 store its analyses. This is controlled by the variable
23926 @code{spam-spamoracle-database} which defaults to @code{nil}. That means
23927 the default SpamOracle database will be used. In case you want your
23928 database to live somewhere special, set
23929 @code{spam-spamoracle-database} to this path.
23932 SpamOracle employs a statistical algorithm to determine whether a
23933 message is spam or ham. In order to get good results, meaning few
23934 false hits or misses, SpamOracle needs training. SpamOracle learns the
23935 characteristics of your spam mails. Using the @emph{add} mode
23936 (training mode) one has to feed good (ham) and spam mails to
23937 SpamOracle. This can be done by pressing @kbd{|} in the Summary buffer
23938 and pipe the mail to a SpamOracle process or using @code{spam.el}'s
23939 spam- and ham-processors, which is much more convenient. For a
23940 detailed description of spam- and ham-processors, @xref{Filtering Spam
23941 Using The Spam ELisp Package}.
23943 @defvar gnus-group-spam-exit-processor-spamoracle
23944 Add this symbol to a group's @code{spam-process} parameter by
23945 customizing the group parameter or the
23946 @code{gnus-spam-process-newsgroups} variable. When this symbol is added
23947 to a group's @code{spam-process} parameter, spam-marked articles will be
23948 sent to SpamOracle as spam samples.
23952 Instead of the obsolete
23953 @code{gnus-group-spam-exit-processor-spamoracle}, it is recommended
23954 that you use @code{'(spam spam-use-spamoracle)}. Everything will work
23955 the same way, we promise.
23958 @defvar gnus-group-ham-exit-processor-spamoracle
23959 Add this symbol to a group's @code{spam-process} parameter by
23960 customizing the group parameter or the
23961 @code{gnus-spam-process-newsgroups} variable. When this symbol is added
23962 to a group's @code{spam-process} parameter, the ham-marked articles in
23963 @emph{ham} groups will be sent to the SpamOracle as samples of ham
23968 Instead of the obsolete
23969 @code{gnus-group-ham-exit-processor-spamoracle}, it is recommended
23970 that you use @code{'(ham spam-use-spamoracle)}. Everything will work
23971 the same way, we promise.
23974 @emph{Example:} These are the Group Parameters of a group that has been
23975 classified as a ham group, meaning that it should only contain ham
23978 ((spam-contents gnus-group-spam-classification-ham)
23979 (spam-process ((ham spam-use-spamoracle)
23980 (spam spam-use-spamoracle))))
23982 For this group the @code{spam-use-spamoracle} is installed for both
23983 ham and spam processing. If the group contains spam message
23984 (e.g. because SpamOracle has not had enough sample messages yet) and
23985 the user marks some messages as spam messages, these messages will be
23986 processed by SpamOracle. The processor sends the messages to
23987 SpamOracle as new samples for spam.
23989 @node Extending the Spam ELisp package
23990 @subsubsection Extending the Spam ELisp package
23991 @cindex spam filtering
23992 @cindex spam elisp package, extending
23993 @cindex extending the spam elisp package
23995 Say you want to add a new back end called blackbox. For filtering
23996 incoming mail, provide the following:
24004 (defvar spam-use-blackbox nil
24005 "True if blackbox should be used.")
24008 Write @code{spam-check-blackbox} if Blackbox can check incoming mail.
24010 Write @code{spam-blackbox-register-routine} and
24011 @code{spam-blackbox-unregister-routine} using the bogofilter
24012 register/unregister routines as a start, or other restister/unregister
24013 routines more appropriate to Blackbox, if Blackbox can
24014 register/unregister spam and ham.
24019 The @code{spam-check-blackbox} function should return @samp{nil} or
24020 @code{spam-split-group}, observing the other conventions. See the
24021 existing @code{spam-check-*} functions for examples of what you can
24022 do, and stick to the template unless you fully understand the reasons
24027 For processing spam and ham messages, provide the following:
24034 Note you don't have to provide a spam or a ham processor. Only
24035 provide them if Blackbox supports spam or ham processing.
24037 Also, ham and spam processors are being phased out as single
24038 variables. Instead the form @code{'(spam spam-use-blackbox)} or
24039 @code{'(ham spam-use-blackbox)} is favored. For now, spam/ham
24040 processor variables are still around but they won't be for long.
24043 (defvar gnus-group-spam-exit-processor-blackbox "blackbox-spam"
24044 "The Blackbox summary exit spam processor.
24045 Only applicable to spam groups.")
24047 (defvar gnus-group-ham-exit-processor-blackbox "blackbox-ham"
24048 "The whitelist summary exit ham processor.
24049 Only applicable to non-spam (unclassified and ham) groups.")
24058 (const :tag "Spam: Blackbox" (spam spam-use-blackbox))
24059 (const :tag "Ham: Blackbox" (ham spam-use-blackbox))
24061 to the @code{spam-process} group parameter in @code{gnus.el}. Make
24062 sure you do it twice, once for the parameter and once for the
24063 variable customization.
24067 (variable-item spam-use-blackbox)
24069 to the @code{spam-autodetect-methods} group parameter in
24070 @code{gnus.el} if Blackbox can check incoming mail for spam contents.
24072 Finally, use the appropriate @code{spam-install-*-backend} function in
24073 @code{spam.el}. Here are the available functions.
24079 @code{spam-install-backend-alias}
24081 This function will simply install an alias for a back end that does
24082 everything like the original back end. It is currently only used to
24083 make @code{spam-use-BBDB-exclusive} act like @code{spam-use-BBDB}.
24086 @code{spam-install-nocheck-backend}
24088 This function installs a back end that has no check function, but can
24089 register/unregister ham or spam. The @code{spam-use-gmane} back end is
24093 @code{spam-install-checkonly-backend}
24095 This function will install a back end that can only check incoming mail
24096 for spam contents. It can't register or unregister messages.
24097 @code{spam-use-blackholes} and @code{spam-use-hashcash} are such
24101 @code{spam-install-statistical-checkonly-backend}
24103 This function installs a statistical back end (one which requires the
24104 full body of a message to check it) that can only check incoming mail
24105 for contents. @code{spam-use-regex-body} is such a filter.
24108 @code{spam-install-statistical-backend}
24110 This function install a statistical back end with incoming checks and
24111 registration/unregistration routines. @code{spam-use-bogofilter} is
24115 @code{spam-install-backend}
24117 This is the most normal back end installation, where a back end that can
24118 check and register/unregister messages is set up without statistical
24119 abilities. The @code{spam-use-BBDB} is such a back end.
24122 @code{spam-install-mover-backend}
24124 Mover back ends are internal to @code{spam.el} and specifically move
24125 articles around when the summary is exited. You will very probably
24126 never install such a back end.
24132 @node Filtering Spam Using Statistics with spam-stat
24133 @subsection Filtering Spam Using Statistics with spam-stat
24134 @cindex Paul Graham
24135 @cindex Graham, Paul
24136 @cindex naive Bayesian spam filtering
24137 @cindex Bayesian spam filtering, naive
24138 @cindex spam filtering, naive Bayesian
24140 Paul Graham has written an excellent essay about spam filtering using
24141 statistics: @uref{http://www.paulgraham.com/spam.html,A Plan for
24142 Spam}. In it he describes the inherent deficiency of rule-based
24143 filtering as used by SpamAssassin, for example: Somebody has to write
24144 the rules, and everybody else has to install these rules. You are
24145 always late. It would be much better, he argues, to filter mail based
24146 on whether it somehow resembles spam or non-spam. One way to measure
24147 this is word distribution. He then goes on to describe a solution
24148 that checks whether a new mail resembles any of your other spam mails
24151 The basic idea is this: Create a two collections of your mail, one
24152 with spam, one with non-spam. Count how often each word appears in
24153 either collection, weight this by the total number of mails in the
24154 collections, and store this information in a dictionary. For every
24155 word in a new mail, determine its probability to belong to a spam or a
24156 non-spam mail. Use the 15 most conspicuous words, compute the total
24157 probability of the mail being spam. If this probability is higher
24158 than a certain threshold, the mail is considered to be spam.
24160 Gnus supports this kind of filtering. But it needs some setting up.
24161 First, you need two collections of your mail, one with spam, one with
24162 non-spam. Then you need to create a dictionary using these two
24163 collections, and save it. And last but not least, you need to use
24164 this dictionary in your fancy mail splitting rules.
24167 * Creating a spam-stat dictionary::
24168 * Splitting mail using spam-stat::
24169 * Low-level interface to the spam-stat dictionary::
24172 @node Creating a spam-stat dictionary
24173 @subsubsection Creating a spam-stat dictionary
24175 Before you can begin to filter spam based on statistics, you must
24176 create these statistics based on two mail collections, one with spam,
24177 one with non-spam. These statistics are then stored in a dictionary
24178 for later use. In order for these statistics to be meaningful, you
24179 need several hundred emails in both collections.
24181 Gnus currently supports only the nnml back end for automated dictionary
24182 creation. The nnml back end stores all mails in a directory, one file
24183 per mail. Use the following:
24185 @defun spam-stat-process-spam-directory
24186 Create spam statistics for every file in this directory. Every file
24187 is treated as one spam mail.
24190 @defun spam-stat-process-non-spam-directory
24191 Create non-spam statistics for every file in this directory. Every
24192 file is treated as one non-spam mail.
24195 Usually you would call @code{spam-stat-process-spam-directory} on a
24196 directory such as @file{~/Mail/mail/spam} (this usually corresponds
24197 the the group @samp{nnml:mail.spam}), and you would call
24198 @code{spam-stat-process-non-spam-directory} on a directory such as
24199 @file{~/Mail/mail/misc} (this usually corresponds the the group
24200 @samp{nnml:mail.misc}).
24202 When you are using @acronym{IMAP}, you won't have the mails available
24203 locally, so that will not work. One solution is to use the Gnus Agent
24204 to cache the articles. Then you can use directories such as
24205 @file{"~/News/agent/nnimap/mail.yourisp.com/personal_spam"} for
24206 @code{spam-stat-process-spam-directory}. @xref{Agent as Cache}.
24209 This variable holds the hash-table with all the statistics---the
24210 dictionary we have been talking about. For every word in either
24211 collection, this hash-table stores a vector describing how often the
24212 word appeared in spam and often it appeared in non-spam mails.
24215 If you want to regenerate the statistics from scratch, you need to
24216 reset the dictionary.
24218 @defun spam-stat-reset
24219 Reset the @code{spam-stat} hash-table, deleting all the statistics.
24222 When you are done, you must save the dictionary. The dictionary may
24223 be rather large. If you will not update the dictionary incrementally
24224 (instead, you will recreate it once a month, for example), then you
24225 can reduce the size of the dictionary by deleting all words that did
24226 not appear often enough or that do not clearly belong to only spam or
24227 only non-spam mails.
24229 @defun spam-stat-reduce-size
24230 Reduce the size of the dictionary. Use this only if you do not want
24231 to update the dictionary incrementally.
24234 @defun spam-stat-save
24235 Save the dictionary.
24238 @defvar spam-stat-file
24239 The filename used to store the dictionary. This defaults to
24240 @file{~/.spam-stat.el}.
24243 @node Splitting mail using spam-stat
24244 @subsubsection Splitting mail using spam-stat
24246 In order to use @code{spam-stat} to split your mail, you need to add the
24247 following to your @file{~/.gnus.el} file:
24250 (require 'spam-stat)
24254 This will load the necessary Gnus code, and the dictionary you
24257 Next, you need to adapt your fancy splitting rules: You need to
24258 determine how to use @code{spam-stat}. The following examples are for
24259 the nnml back end. Using the nnimap back end works just as well. Just
24260 use @code{nnimap-split-fancy} instead of @code{nnmail-split-fancy}.
24262 In the simplest case, you only have two groups, @samp{mail.misc} and
24263 @samp{mail.spam}. The following expression says that mail is either
24264 spam or it should go into @samp{mail.misc}. If it is spam, then
24265 @code{spam-stat-split-fancy} will return @samp{mail.spam}.
24268 (setq nnmail-split-fancy
24269 `(| (: spam-stat-split-fancy)
24273 @defvar spam-stat-split-fancy-spam-group
24274 The group to use for spam. Default is @samp{mail.spam}.
24277 If you also filter mail with specific subjects into other groups, use
24278 the following expression. Only mails not matching the regular
24279 expression are considered potential spam.
24282 (setq nnmail-split-fancy
24283 `(| ("Subject" "\\bspam-stat\\b" "mail.emacs")
24284 (: spam-stat-split-fancy)
24288 If you want to filter for spam first, then you must be careful when
24289 creating the dictionary. Note that @code{spam-stat-split-fancy} must
24290 consider both mails in @samp{mail.emacs} and in @samp{mail.misc} as
24291 non-spam, therefore both should be in your collection of non-spam
24292 mails, when creating the dictionary!
24295 (setq nnmail-split-fancy
24296 `(| (: spam-stat-split-fancy)
24297 ("Subject" "\\bspam-stat\\b" "mail.emacs")
24301 You can combine this with traditional filtering. Here, we move all
24302 HTML-only mails into the @samp{mail.spam.filtered} group. Note that since
24303 @code{spam-stat-split-fancy} will never see them, the mails in
24304 @samp{mail.spam.filtered} should be neither in your collection of spam mails,
24305 nor in your collection of non-spam mails, when creating the
24309 (setq nnmail-split-fancy
24310 `(| ("Content-Type" "text/html" "mail.spam.filtered")
24311 (: spam-stat-split-fancy)
24312 ("Subject" "\\bspam-stat\\b" "mail.emacs")
24317 @node Low-level interface to the spam-stat dictionary
24318 @subsubsection Low-level interface to the spam-stat dictionary
24320 The main interface to using @code{spam-stat}, are the following functions:
24322 @defun spam-stat-buffer-is-spam
24323 Called in a buffer, that buffer is considered to be a new spam mail.
24324 Use this for new mail that has not been processed before.
24327 @defun spam-stat-buffer-is-no-spam
24328 Called in a buffer, that buffer is considered to be a new non-spam
24329 mail. Use this for new mail that has not been processed before.
24332 @defun spam-stat-buffer-change-to-spam
24333 Called in a buffer, that buffer is no longer considered to be normal
24334 mail but spam. Use this to change the status of a mail that has
24335 already been processed as non-spam.
24338 @defun spam-stat-buffer-change-to-non-spam
24339 Called in a buffer, that buffer is no longer considered to be spam but
24340 normal mail. Use this to change the status of a mail that has already
24341 been processed as spam.
24344 @defun spam-stat-save
24345 Save the hash table to the file. The filename used is stored in the
24346 variable @code{spam-stat-file}.
24349 @defun spam-stat-load
24350 Load the hash table from a file. The filename used is stored in the
24351 variable @code{spam-stat-file}.
24354 @defun spam-stat-score-word
24355 Return the spam score for a word.
24358 @defun spam-stat-score-buffer
24359 Return the spam score for a buffer.
24362 @defun spam-stat-split-fancy
24363 Use this function for fancy mail splitting. Add the rule @samp{(:
24364 spam-stat-split-fancy)} to @code{nnmail-split-fancy}
24367 Make sure you load the dictionary before using it. This requires the
24368 following in your @file{~/.gnus.el} file:
24371 (require 'spam-stat)
24375 Typical test will involve calls to the following functions:
24378 Reset: (setq spam-stat (make-hash-table :test 'equal))
24379 Learn spam: (spam-stat-process-spam-directory "~/Mail/mail/spam")
24380 Learn non-spam: (spam-stat-process-non-spam-directory "~/Mail/mail/misc")
24381 Save table: (spam-stat-save)
24382 File size: (nth 7 (file-attributes spam-stat-file))
24383 Number of words: (hash-table-count spam-stat)
24384 Test spam: (spam-stat-test-directory "~/Mail/mail/spam")
24385 Test non-spam: (spam-stat-test-directory "~/Mail/mail/misc")
24386 Reduce table size: (spam-stat-reduce-size)
24387 Save table: (spam-stat-save)
24388 File size: (nth 7 (file-attributes spam-stat-file))
24389 Number of words: (hash-table-count spam-stat)
24390 Test spam: (spam-stat-test-directory "~/Mail/mail/spam")
24391 Test non-spam: (spam-stat-test-directory "~/Mail/mail/misc")
24394 Here is how you would create your dictionary:
24397 Reset: (setq spam-stat (make-hash-table :test 'equal))
24398 Learn spam: (spam-stat-process-spam-directory "~/Mail/mail/spam")
24399 Learn non-spam: (spam-stat-process-non-spam-directory "~/Mail/mail/misc")
24400 Repeat for any other non-spam group you need...
24401 Reduce table size: (spam-stat-reduce-size)
24402 Save table: (spam-stat-save)
24406 @section Interaction with other modes
24411 @code{gnus-dired-minor-mode} provided some useful functions for dired
24412 buffers. It is enabled with
24414 (add-hook 'dired-mode-hook 'turn-on-gnus-dired-mode)
24419 @findex gnus-dired-attach
24420 Send dired's marked files as an attachment (@code{gnus-dired-attach}).
24421 You will be prompted for a message buffer.
24424 @findex gnus-dired-find-file-mailcap
24425 Visit a file according to the appropriate mailcap entry
24426 (@code{gnus-dired-find-file-mailcap}). With prefix, open file in a new
24430 @findex gnus-dired-print
24431 Print file according to the mailcap entry (@code{gnus-dired-print}). If
24432 there is no print command, print in a PostScript image.
24435 @node Various Various
24436 @section Various Various
24442 @item gnus-home-directory
24443 @vindex gnus-home-directory
24444 All Gnus file and directory variables will be initialized from this
24445 variable, which defaults to @file{~/}.
24447 @item gnus-directory
24448 @vindex gnus-directory
24449 Most Gnus storage file and directory variables will be initialized from
24450 this variable, which defaults to the @env{SAVEDIR} environment
24451 variable, or @file{~/News/} if that variable isn't set.
24453 Note that gnus is mostly loaded when the @file{.gnus.el} file is read.
24454 This means that other directory variables that are initialized from this
24455 variable won't be set properly if you set this variable in
24456 @file{.gnus.el}. Set this variable in @file{.emacs} instead.
24458 @item gnus-default-directory
24459 @vindex gnus-default-directory
24460 Not related to the above variable at all---this variable says what the
24461 default directory of all Gnus buffers should be. If you issue commands
24462 like @kbd{C-x C-f}, the prompt you'll get starts in the current buffer's
24463 default directory. If this variable is @code{nil} (which is the
24464 default), the default directory will be the default directory of the
24465 buffer you were in when you started Gnus.
24468 @vindex gnus-verbose
24469 This variable is an integer between zero and ten. The higher the value,
24470 the more messages will be displayed. If this variable is zero, Gnus
24471 will never flash any messages, if it is seven (which is the default),
24472 most important messages will be shown, and if it is ten, Gnus won't ever
24473 shut up, but will flash so many messages it will make your head swim.
24475 @item gnus-verbose-backends
24476 @vindex gnus-verbose-backends
24477 This variable works the same way as @code{gnus-verbose}, but it applies
24478 to the Gnus back ends instead of Gnus proper.
24480 @item nnheader-max-head-length
24481 @vindex nnheader-max-head-length
24482 When the back ends read straight heads of articles, they all try to read
24483 as little as possible. This variable (default 4096) specifies
24484 the absolute max length the back ends will try to read before giving up
24485 on finding a separator line between the head and the body. If this
24486 variable is @code{nil}, there is no upper read bound. If it is
24487 @code{t}, the back ends won't try to read the articles piece by piece,
24488 but read the entire articles. This makes sense with some versions of
24489 @code{ange-ftp} or @code{efs}.
24491 @item nnheader-head-chop-length
24492 @vindex nnheader-head-chop-length
24493 This variable (default 2048) says how big a piece of each article to
24494 read when doing the operation described above.
24496 @item nnheader-file-name-translation-alist
24497 @vindex nnheader-file-name-translation-alist
24499 @cindex invalid characters in file names
24500 @cindex characters in file names
24501 This is an alist that says how to translate characters in file names.
24502 For instance, if @samp{:} is invalid as a file character in file names
24503 on your system (you OS/2 user you), you could say something like:
24507 (setq nnheader-file-name-translation-alist
24512 In fact, this is the default value for this variable on OS/2 and MS
24513 Windows (phooey) systems.
24515 @item gnus-hidden-properties
24516 @vindex gnus-hidden-properties
24517 This is a list of properties to use to hide ``invisible'' text. It is
24518 @code{(invisible t intangible t)} by default on most systems, which
24519 makes invisible text invisible and intangible.
24521 @item gnus-parse-headers-hook
24522 @vindex gnus-parse-headers-hook
24523 A hook called before parsing headers. It can be used, for instance, to
24524 gather statistics on the headers fetched, or perhaps you'd like to prune
24525 some headers. I don't see why you'd want that, though.
24527 @item gnus-shell-command-separator
24528 @vindex gnus-shell-command-separator
24529 String used to separate two shell commands. The default is @samp{;}.
24531 @item gnus-invalid-group-regexp
24532 @vindex gnus-invalid-group-regexp
24534 Regexp to match ``invalid'' group names when querying user for a group
24535 name. The default value catches some @strong{really} invalid group
24536 names who could possibly mess up Gnus internally (like allowing
24537 @samp{:} in a group name, which is normally used to delimit method and
24540 @acronym{IMAP} users might want to allow @samp{/} in group names though.
24548 Well, that's the manual---you can get on with your life now. Keep in
24549 touch. Say hello to your cats from me.
24551 My @strong{ghod}---I just can't stand goodbyes. Sniffle.
24553 Ol' Charles Reznikoff said it pretty well, so I leave the floor to him:
24559 Not because of victories @*
24562 but for the common sunshine,@*
24564 the largess of the spring.
24568 but for the day's work done@*
24569 as well as I was able;@*
24570 not for a seat upon the dais@*
24571 but at the common table.@*
24576 @chapter Appendices
24579 * XEmacs:: Requirements for installing under XEmacs.
24580 * History:: How Gnus got where it is today.
24581 * On Writing Manuals:: Why this is not a beginner's guide.
24582 * Terminology:: We use really difficult, like, words here.
24583 * Customization:: Tailoring Gnus to your needs.
24584 * Troubleshooting:: What you might try if things do not work.
24585 * Gnus Reference Guide:: Rilly, rilly technical stuff.
24586 * Emacs for Heathens:: A short introduction to Emacsian terms.
24587 * Frequently Asked Questions:: The Gnus FAQ
24594 @cindex installing under XEmacs
24596 XEmacs is distributed as a collection of packages. You should install
24597 whatever packages the Gnus XEmacs package requires. The current
24598 requirements are @samp{gnus}, @samp{mail-lib}, @samp{xemacs-base},
24599 @samp{eterm}, @samp{sh-script}, @samp{net-utils}, @samp{os-utils},
24600 @samp{dired}, @samp{mh-e}, @samp{sieve}, @samp{ps-print}, @samp{w3},
24601 @samp{pgg}, @samp{mailcrypt}, @samp{ecrypto}, and @samp{sasl}.
24608 @sc{gnus} was written by Masanobu @sc{Umeda}. When autumn crept up in
24609 '94, Lars Magne Ingebrigtsen grew bored and decided to rewrite Gnus.
24611 If you want to investigate the person responsible for this outrage,
24612 you can point your (feh!) web browser to
24613 @uref{http://quimby.gnus.org/}. This is also the primary
24614 distribution point for the new and spiffy versions of Gnus, and is
24615 known as The Site That Destroys Newsrcs And Drives People Mad.
24617 During the first extended alpha period of development, the new Gnus was
24618 called ``(ding) Gnus''. @dfn{(ding)} is, of course, short for
24619 @dfn{ding is not Gnus}, which is a total and utter lie, but who cares?
24620 (Besides, the ``Gnus'' in this abbreviation should probably be
24621 pronounced ``news'' as @sc{Umeda} intended, which makes it a more
24622 appropriate name, don't you think?)
24624 In any case, after spending all that energy on coming up with a new and
24625 spunky name, we decided that the name was @emph{too} spunky, so we
24626 renamed it back again to ``Gnus''. But in mixed case. ``Gnus'' vs.
24627 ``@sc{gnus}''. New vs. old.
24630 * Gnus Versions:: What Gnus versions have been released.
24631 * Other Gnus Versions:: Other Gnus versions that also have been released.
24632 * Why?:: What's the point of Gnus?
24633 * Compatibility:: Just how compatible is Gnus with @sc{gnus}?
24634 * Conformity:: Gnus tries to conform to all standards.
24635 * Emacsen:: Gnus can be run on a few modern Emacsen.
24636 * Gnus Development:: How Gnus is developed.
24637 * Contributors:: Oodles of people.
24638 * New Features:: Pointers to some of the new stuff in Gnus.
24642 @node Gnus Versions
24643 @subsection Gnus Versions
24645 @cindex September Gnus
24647 @cindex Quassia Gnus
24648 @cindex Pterodactyl Gnus
24651 @cindex Gnus versions
24653 The first ``proper'' release of Gnus 5 was done in November 1995 when it
24654 was included in the Emacs 19.30 distribution (132 (ding) Gnus releases
24655 plus 15 Gnus 5.0 releases).
24657 In May 1996 the next Gnus generation (aka. ``September Gnus'' (after 99
24658 releases)) was released under the name ``Gnus 5.2'' (40 releases).
24660 On July 28th 1996 work on Red Gnus was begun, and it was released on
24661 January 25th 1997 (after 84 releases) as ``Gnus 5.4'' (67 releases).
24663 On September 13th 1997, Quassia Gnus was started and lasted 37 releases.
24664 If was released as ``Gnus 5.6'' on March 8th 1998 (46 releases).
24666 Gnus 5.6 begat Pterodactyl Gnus on August 29th 1998 and was released as
24667 ``Gnus 5.8'' (after 99 releases and a CVS repository) on December 3rd
24670 On the 26th of October 2000, Oort Gnus was begun.
24672 If you happen upon a version of Gnus that has a prefixed name --
24673 ``(ding) Gnus'', ``September Gnus'', ``Red Gnus'', ``Quassia Gnus'',
24674 ``Pterodactyl Gnus'', ``Oort Gnus'' -- don't panic. Don't let it know
24675 that you're frightened. Back away. Slowly. Whatever you do, don't
24676 run. Walk away, calmly, until you're out of its reach. Find a proper
24677 released version of Gnus and snuggle up to that instead.
24680 @node Other Gnus Versions
24681 @subsection Other Gnus Versions
24684 In addition to the versions of Gnus which have had their releases
24685 coordinated by Lars, one major development has been Semi-gnus from
24686 Japan. It's based on a library called @acronym{SEMI}, which provides
24687 @acronym{MIME} capabilities.
24689 These Gnusae are based mainly on Gnus 5.6 and Pterodactyl Gnus.
24690 Collectively, they are called ``Semi-gnus'', and different strains are
24691 called T-gnus, ET-gnus, Nana-gnus and Chaos. These provide powerful
24692 @acronym{MIME} and multilingualization things, especially important for
24699 What's the point of Gnus?
24701 I want to provide a ``rad'', ``happening'', ``way cool'' and ``hep''
24702 newsreader, that lets you do anything you can think of. That was my
24703 original motivation, but while working on Gnus, it has become clear to
24704 me that this generation of newsreaders really belong in the stone age.
24705 Newsreaders haven't developed much since the infancy of the net. If the
24706 volume continues to rise with the current rate of increase, all current
24707 newsreaders will be pretty much useless. How do you deal with
24708 newsgroups that have thousands of new articles each day? How do you
24709 keep track of millions of people who post?
24711 Gnus offers no real solutions to these questions, but I would very much
24712 like to see Gnus being used as a testing ground for new methods of
24713 reading and fetching news. Expanding on @sc{Umeda}-san's wise decision
24714 to separate the newsreader from the back ends, Gnus now offers a simple
24715 interface for anybody who wants to write new back ends for fetching mail
24716 and news from different sources. I have added hooks for customizations
24717 everywhere I could imagine it being useful. By doing so, I'm inviting
24718 every one of you to explore and invent.
24720 May Gnus never be complete. @kbd{C-u 100 M-x all-hail-emacs} and
24721 @kbd{C-u 100 M-x all-hail-xemacs}.
24724 @node Compatibility
24725 @subsection Compatibility
24727 @cindex compatibility
24728 Gnus was designed to be fully compatible with @sc{gnus}. Almost all key
24729 bindings have been kept. More key bindings have been added, of course,
24730 but only in one or two obscure cases have old bindings been changed.
24735 @center In a cloud bones of steel.
24739 All commands have kept their names. Some internal functions have changed
24742 The @code{gnus-uu} package has changed drastically. @xref{Decoding
24745 One major compatibility question is the presence of several summary
24746 buffers. All variables relevant while reading a group are
24747 buffer-local to the summary buffer they belong in. Although many
24748 important variables have their values copied into their global
24749 counterparts whenever a command is executed in the summary buffer, this
24750 change might lead to incorrect values being used unless you are careful.
24752 All code that relies on knowledge of @sc{gnus} internals will probably
24753 fail. To take two examples: Sorting @code{gnus-newsrc-alist} (or
24754 changing it in any way, as a matter of fact) is strictly verboten. Gnus
24755 maintains a hash table that points to the entries in this alist (which
24756 speeds up many functions), and changing the alist directly will lead to
24760 @cindex highlighting
24761 Old hilit19 code does not work at all. In fact, you should probably
24762 remove all hilit code from all Gnus hooks
24763 (@code{gnus-group-prepare-hook} and @code{gnus-summary-prepare-hook}).
24764 Gnus provides various integrated functions for highlighting. These are
24765 faster and more accurate. To make life easier for everybody, Gnus will
24766 by default remove all hilit calls from all hilit hooks. Uncleanliness!
24769 Packages like @code{expire-kill} will no longer work. As a matter of
24770 fact, you should probably remove all old @sc{gnus} packages (and other
24771 code) when you start using Gnus. More likely than not, Gnus already
24772 does what you have written code to make @sc{gnus} do. (Snicker.)
24774 Even though old methods of doing things are still supported, only the
24775 new methods are documented in this manual. If you detect a new method of
24776 doing something while reading this manual, that does not mean you have
24777 to stop doing it the old way.
24779 Gnus understands all @sc{gnus} startup files.
24781 @kindex M-x gnus-bug
24783 @cindex reporting bugs
24785 Overall, a casual user who hasn't written much code that depends on
24786 @sc{gnus} internals should suffer no problems. If problems occur,
24787 please let me know by issuing that magic command @kbd{M-x gnus-bug}.
24789 @vindex gnus-bug-create-help-buffer
24790 If you are in the habit of sending bug reports @emph{very} often, you
24791 may find the helpful help buffer annoying after a while. If so, set
24792 @code{gnus-bug-create-help-buffer} to @code{nil} to avoid having it pop
24797 @subsection Conformity
24799 No rebels without a clue here, ma'am. We conform to all standards known
24800 to (wo)man. Except for those standards and/or conventions we disagree
24808 There are no known breaches of this standard.
24812 There are no known breaches of this standard, either.
24814 @item Son-of-RFC 1036
24815 @cindex Son-of-RFC 1036
24816 We do have some breaches to this one.
24822 These are considered to be ``vanity headers'', while I consider them
24823 to be consumer information. After seeing so many badly formatted
24824 articles coming from @code{tin} and @code{Netscape} I know not to use
24825 either of those for posting articles. I would not have known that if
24826 it wasn't for the @code{X-Newsreader} header.
24831 USEFOR is an IETF working group writing a successor to RFC 1036, based
24832 on Son-of-RFC 1036. They have produced a number of drafts proposing
24833 various changes to the format of news articles. The Gnus towers will
24834 look into implementing the changes when the draft is accepted as an RFC.
24836 @item MIME - RFC 2045-2049 etc
24837 @cindex @acronym{MIME}
24838 All the various @acronym{MIME} RFCs are supported.
24840 @item Disposition Notifications - RFC 2298
24841 Message Mode is able to request notifications from the receiver.
24843 @item PGP - RFC 1991 and RFC 2440
24846 RFC 1991 is the original @acronym{PGP} message specification,
24847 published as an informational RFC. RFC 2440 was the follow-up, now
24848 called Open PGP, and put on the Standards Track. Both document a
24849 non-@acronym{MIME} aware @acronym{PGP} format. Gnus supports both
24850 encoding (signing and encryption) and decoding (verification and
24853 @item PGP/MIME - RFC 2015/3156
24854 RFC 2015 (superseded by 3156 which references RFC 2440 instead of RFC
24855 1991) describes the @acronym{MIME}-wrapping around the RF 1991/2440 format.
24856 Gnus supports both encoding and decoding.
24858 @item S/MIME - RFC 2633
24859 RFC 2633 describes the @acronym{S/MIME} format.
24861 @item IMAP - RFC 1730/2060, RFC 2195, RFC 2086, RFC 2359, RFC 2595, RFC 1731
24862 RFC 1730 is @acronym{IMAP} version 4, updated somewhat by RFC 2060
24863 (@acronym{IMAP} 4 revision 1). RFC 2195 describes CRAM-MD5
24864 authentication for @acronym{IMAP}. RFC 2086 describes access control
24865 lists (ACLs) for @acronym{IMAP}. RFC 2359 describes a @acronym{IMAP}
24866 protocol enhancement. RFC 2595 describes the proper @acronym{TLS}
24867 integration (STARTTLS) with @acronym{IMAP}. RFC 1731 describes the
24868 GSSAPI/Kerberos4 mechanisms for @acronym{IMAP}.
24872 If you ever notice Gnus acting non-compliant with regards to the texts
24873 mentioned above, don't hesitate to drop a note to Gnus Towers and let us
24878 @subsection Emacsen
24884 Gnus should work on:
24892 XEmacs 21.4 and up.
24896 This Gnus version will absolutely not work on any Emacsen older than
24897 that. Not reliably, at least. Older versions of Gnus may work on older
24898 Emacs versions. However, T-gnus does support ``Mule 2.3 based on Emacs
24899 19.34'' and possibly the versions of XEmacs prior to 21.1.1, e.g. 20.4.
24900 See the file ``README'' in the T-gnus distribution for more details.
24902 There are some vague differences between Gnus on the various
24903 platforms---XEmacs features more graphics (a logo and a toolbar)---but
24904 other than that, things should look pretty much the same under all
24908 @node Gnus Development
24909 @subsection Gnus Development
24911 Gnus is developed in a two-phased cycle. The first phase involves much
24912 discussion on the @samp{ding@@gnus.org} mailing list, where people
24913 propose changes and new features, post patches and new back ends. This
24914 phase is called the @dfn{alpha} phase, since the Gnusae released in this
24915 phase are @dfn{alpha releases}, or (perhaps more commonly in other
24916 circles) @dfn{snapshots}. During this phase, Gnus is assumed to be
24917 unstable and should not be used by casual users. Gnus alpha releases
24918 have names like ``Red Gnus'' and ``Quassia Gnus''.
24920 After futzing around for 50-100 alpha releases, Gnus is declared
24921 @dfn{frozen}, and only bug fixes are applied. Gnus loses the prefix,
24922 and is called things like ``Gnus 5.6.32'' instead. Normal people are
24923 supposed to be able to use these, and these are mostly discussed on the
24924 @samp{gnu.emacs.gnus} newsgroup.
24927 @vindex mail-source-delete-incoming
24928 Some variable defaults differ between alpha Gnusae and released Gnusae.
24929 In particular, @code{mail-source-delete-incoming} defaults to @code{nil} in
24930 alpha Gnusae and @code{t} in released Gnusae. This is to prevent
24931 lossage of mail if an alpha release hiccups while handling the mail.
24933 The division of discussion between the ding mailing list and the Gnus
24934 newsgroup is not purely based on publicity concerns. It's true that
24935 having people write about the horrible things that an alpha Gnus release
24936 can do (sometimes) in a public forum may scare people off, but more
24937 importantly, talking about new experimental features that have been
24938 introduced may confuse casual users. New features are frequently
24939 introduced, fiddled with, and judged to be found wanting, and then
24940 either discarded or totally rewritten. People reading the mailing list
24941 usually keep up with these rapid changes, while people on the newsgroup
24942 can't be assumed to do so.
24947 @subsection Contributors
24948 @cindex contributors
24950 The new Gnus version couldn't have been done without the help of all the
24951 people on the (ding) mailing list. Every day for over a year I have
24952 gotten billions of nice bug reports from them, filling me with joy,
24953 every single one of them. Smooches. The people on the list have been
24954 tried beyond endurance, what with my ``oh, that's a neat idea <type
24955 type>, yup, I'll release it right away <ship off> no wait, that doesn't
24956 work at all <type type>, yup, I'll ship that one off right away <ship
24957 off> no, wait, that absolutely does not work'' policy for releases.
24958 Micro$oft---bah. Amateurs. I'm @emph{much} worse. (Or is that
24959 ``worser''? ``much worser''? ``worsest''?)
24961 I would like to take this opportunity to thank the Academy for@dots{} oops,
24967 Masanobu @sc{Umeda}---the writer of the original @sc{gnus}.
24970 Shenghuo Zhu---uudecode.el, mm-uu.el, rfc1843.el, webmail.el,
24971 nnwarchive and many, many other things connected with @acronym{MIME} and
24972 other types of en/decoding, as well as general bug fixing, new
24973 functionality and stuff.
24976 Per Abrahamsen---custom, scoring, highlighting and @sc{soup} code (as
24977 well as numerous other things).
24980 Luis Fernandes---design and graphics.
24983 Joe Reiss---creator of the smiley faces.
24986 Justin Sheehy---the @acronym{FAQ} maintainer.
24989 Erik Naggum---help, ideas, support, code and stuff.
24992 Wes Hardaker---@file{gnus-picon.el} and the manual section on
24993 @dfn{picons} (@pxref{Picons}).
24996 Kim-Minh Kaplan---further work on the picon code.
24999 Brad Miller---@file{gnus-gl.el} and the GroupLens manual section.
25002 Sudish Joseph---innumerable bug fixes.
25005 Ilja Weis---@file{gnus-topic.el}.
25008 Steven L. Baur---lots and lots and lots of bugs detections and fixes.
25011 Vladimir Alexiev---the refcard and reference booklets.
25014 Felix Lee & Jamie Zawinski---I stole some pieces from the XGnus
25015 distribution by Felix Lee and JWZ.
25018 Scott Byer---@file{nnfolder.el} enhancements & rewrite.
25021 Peter Mutsaers---orphan article scoring code.
25024 Ken Raeburn---POP mail support.
25027 Hallvard B Furuseth---various bits and pieces, especially dealing with
25031 Brian Edmonds---@file{gnus-bbdb.el}.
25034 David Moore---rewrite of @file{nnvirtual.el} and many other things.
25037 Kevin Davidson---came up with the name @dfn{ding}, so blame him.
25040 Fran@,{c}ois Pinard---many, many interesting and thorough bug reports, as
25041 well as autoconf support.
25045 This manual was proof-read by Adrian Aichner, with Ricardo Nassif, Mark
25046 Borges, and Jost Krieger proof-reading parts of the manual.
25048 The following people have contributed many patches and suggestions:
25063 Jason L. Tibbitts, III,
25065 Katsumi Yamaoka, @c Yamaoka
25069 Also thanks to the following for patches and stuff:
25079 Alexei V. Barantsev,
25094 Massimo Campostrini,
25099 Jae-you Chung, @c ?
25100 James H. Cloos, Jr.,
25104 Andrew J. Cosgriff,
25107 Geoffrey T. Dairiki,
25113 Michael Welsh Duggan,
25118 Enami Tsugutomo, @c Enami
25122 Nelson Jose dos Santos Ferreira,
25130 Arne Georg Gleditsch,
25132 Michelangelo Grigni,
25136 Kenichi Handa, @c Handa
25138 Yoshiki Hayashi, @c Hayashi
25140 Hisashige Kenji, @c Hisashige
25147 Fran@,{c}ois Felix Ingrand,
25148 Tatsuya Ichikawa, @c Ichikawa
25149 Ishikawa Ichiro, @c Ishikawa
25151 Iwamuro Motonori, @c Iwamuro
25161 Peter Skov Knudsen,
25162 Shuhei Kobayashi, @c Kobayashi
25164 Koseki Yoshinori, @c Koseki
25165 Thor Kristoffersen,
25168 Seokchan Lee, @c Lee
25186 Morioka Tomohiko, @c Morioka
25187 Erik Toubro Nielsen,
25194 Masaharu Onishi, @c Onishi
25199 Jens-Ulrik Holger Petersen,
25203 John McClary Prevost,
25209 Lars Balker Rasmussen,
25214 Christian von Roques,
25217 Wolfgang Rupprecht,
25224 Philippe Schnoebelen,
25226 Randal L. Schwartz,
25240 Kiyokazu Suto, @c Suto
25245 Tozawa Akihiko, @c Tozawa
25265 For a full overview of what each person has done, the ChangeLogs
25266 included in the Gnus alpha distributions should give ample reading
25267 (550kB and counting).
25269 Apologies to everybody that I've forgotten, of which there are many, I'm
25272 Gee, that's quite a list of people. I guess that must mean that there
25273 actually are people who are using Gnus. Who'd'a thunk it!
25277 @subsection New Features
25278 @cindex new features
25281 * ding Gnus:: New things in Gnus 5.0/5.1, the first new Gnus.
25282 * September Gnus:: The Thing Formally Known As Gnus 5.2/5.3.
25283 * Red Gnus:: Third time best---Gnus 5.4/5.5.
25284 * Quassia Gnus:: Two times two is four, or Gnus 5.6/5.7.
25285 * Pterodactyl Gnus:: Pentad also starts with P, AKA Gnus 5.8/5.9.
25286 * Oort Gnus:: It's big. It's far out. Gnus 5.10/5.11.
25287 * No Gnus:: Lars, FIXME!
25290 These lists are, of course, just @emph{short} overviews of the
25291 @emph{most} important new features. No, really. There are tons more.
25292 Yes, we have feeping creaturism in full effect.
25295 @subsubsection (ding) Gnus
25297 New features in Gnus 5.0/5.1:
25302 The look of all buffers can be changed by setting format-like variables
25303 (@pxref{Group Buffer Format} and @pxref{Summary Buffer Format}).
25306 Local spool and several @acronym{NNTP} servers can be used at once
25307 (@pxref{Select Methods}).
25310 You can combine groups into virtual groups (@pxref{Virtual Groups}).
25313 You can read a number of different mail formats (@pxref{Getting Mail}).
25314 All the mail back ends implement a convenient mail expiry scheme
25315 (@pxref{Expiring Mail}).
25318 Gnus can use various strategies for gathering threads that have lost
25319 their roots (thereby gathering loose sub-threads into one thread) or it
25320 can go back and retrieve enough headers to build a complete thread
25321 (@pxref{Customizing Threading}).
25324 Killed groups can be displayed in the group buffer, and you can read
25325 them as well (@pxref{Listing Groups}).
25328 Gnus can do partial group updates---you do not have to retrieve the
25329 entire active file just to check for new articles in a few groups
25330 (@pxref{The Active File}).
25333 Gnus implements a sliding scale of subscribedness to groups
25334 (@pxref{Group Levels}).
25337 You can score articles according to any number of criteria
25338 (@pxref{Scoring}). You can even get Gnus to find out how to score
25339 articles for you (@pxref{Adaptive Scoring}).
25342 Gnus maintains a dribble buffer that is auto-saved the normal Emacs
25343 manner, so it should be difficult to lose much data on what you have
25344 read if your machine should go down (@pxref{Auto Save}).
25347 Gnus now has its own startup file (@file{~/.gnus.el}) to avoid
25348 cluttering up the @file{.emacs} file.
25351 You can set the process mark on both groups and articles and perform
25352 operations on all the marked items (@pxref{Process/Prefix}).
25355 You can grep through a subset of groups and create a group from the
25356 results (@pxref{Kibozed Groups}).
25359 You can list subsets of groups according to, well, anything
25360 (@pxref{Listing Groups}).
25363 You can browse foreign servers and subscribe to groups from those
25364 servers (@pxref{Browse Foreign Server}).
25367 Gnus can fetch articles, asynchronously, on a second connection to the
25368 server (@pxref{Asynchronous Fetching}).
25371 You can cache articles locally (@pxref{Article Caching}).
25374 The uudecode functions have been expanded and generalized
25375 (@pxref{Decoding Articles}).
25378 You can still post uuencoded articles, which was a little-known feature
25379 of @sc{gnus}' past (@pxref{Uuencoding and Posting}).
25382 Fetching parents (and other articles) now actually works without
25383 glitches (@pxref{Finding the Parent}).
25386 Gnus can fetch @acronym{FAQ}s and group descriptions (@pxref{Group Information}).
25389 Digests (and other files) can be used as the basis for groups
25390 (@pxref{Document Groups}).
25393 Articles can be highlighted and customized (@pxref{Customizing
25397 URLs and other external references can be buttonized (@pxref{Article
25401 You can do lots of strange stuff with the Gnus window & frame
25402 configuration (@pxref{Window Layout}).
25405 You can click on buttons instead of using the keyboard
25411 @node September Gnus
25412 @subsubsection September Gnus
25416 \gnusfig{-28cm}{0cm}{\epsfig{figure=ps/september,height=20cm}}
25420 New features in Gnus 5.2/5.3:
25425 A new message composition mode is used. All old customization variables
25426 for @code{mail-mode}, @code{rnews-reply-mode} and @code{gnus-msg} are
25430 Gnus is now able to generate @dfn{sparse} threads---threads where
25431 missing articles are represented by empty nodes (@pxref{Customizing
25435 (setq gnus-build-sparse-threads 'some)
25439 Outgoing articles are stored on a special archive server
25440 (@pxref{Archived Messages}).
25443 Partial thread regeneration now happens when articles are
25447 Gnus can make use of GroupLens predictions.
25450 Picons (personal icons) can be displayed under XEmacs (@pxref{Picons}).
25453 A @code{trn}-like tree buffer can be displayed (@pxref{Tree Display}).
25456 (setq gnus-use-trees t)
25460 An @code{nn}-like pick-and-read minor mode is available for the summary
25461 buffers (@pxref{Pick and Read}).
25464 (add-hook 'gnus-summary-mode-hook 'gnus-pick-mode)
25468 In binary groups you can use a special binary minor mode (@pxref{Binary
25472 Groups can be grouped in a folding topic hierarchy (@pxref{Group
25476 (add-hook 'gnus-group-mode-hook 'gnus-topic-mode)
25480 Gnus can re-send and bounce mail (@pxref{Summary Mail Commands}).
25483 Groups can now have a score, and bubbling based on entry frequency
25484 is possible (@pxref{Group Score}).
25487 (add-hook 'gnus-summary-exit-hook 'gnus-summary-bubble-group)
25491 Groups can be process-marked, and commands can be performed on
25492 groups of groups (@pxref{Marking Groups}).
25495 Caching is possible in virtual groups.
25498 @code{nndoc} now understands all kinds of digests, mail boxes, rnews
25499 news batches, ClariNet briefs collections, and just about everything
25500 else (@pxref{Document Groups}).
25503 Gnus has a new back end (@code{nnsoup}) to create/read SOUP packets
25507 The Gnus cache is much faster.
25510 Groups can be sorted according to many criteria (@pxref{Sorting
25514 New group parameters have been introduced to set list-addresses and
25515 expiry times (@pxref{Group Parameters}).
25518 All formatting specs allow specifying faces to be used
25519 (@pxref{Formatting Fonts}).
25522 There are several more commands for setting/removing/acting on process
25523 marked articles on the @kbd{M P} submap (@pxref{Setting Process Marks}).
25526 The summary buffer can be limited to show parts of the available
25527 articles based on a wide range of criteria. These commands have been
25528 bound to keys on the @kbd{/} submap (@pxref{Limiting}).
25531 Articles can be made persistent with the @kbd{*} command
25532 (@pxref{Persistent Articles}).
25535 All functions for hiding article elements are now toggles.
25538 Article headers can be buttonized (@pxref{Article Washing}).
25541 All mail back ends support fetching articles by @code{Message-ID}.
25544 Duplicate mail can now be treated properly (@pxref{Duplicates}).
25547 All summary mode commands are available directly from the article
25548 buffer (@pxref{Article Keymap}).
25551 Frames can be part of @code{gnus-buffer-configuration} (@pxref{Window
25555 Mail can be re-scanned by a daemonic process (@pxref{Daemons}).
25558 \marginpar[\mbox{}\hfill\epsfig{figure=ps/fseptember,height=5cm}]{\epsfig{figure=ps/fseptember,height=5cm}}
25563 Gnus can make use of NoCeM files to weed out spam (@pxref{NoCeM}).
25566 (setq gnus-use-nocem t)
25570 Groups can be made permanently visible (@pxref{Listing Groups}).
25573 (setq gnus-permanently-visible-groups "^nnml:")
25577 Many new hooks have been introduced to make customizing easier.
25580 Gnus respects the @code{Mail-Copies-To} header.
25583 Threads can be gathered by looking at the @code{References} header
25584 (@pxref{Customizing Threading}).
25587 (setq gnus-summary-thread-gathering-function
25588 'gnus-gather-threads-by-references)
25592 Read articles can be stored in a special backlog buffer to avoid
25593 refetching (@pxref{Article Backlog}).
25596 (setq gnus-keep-backlog 50)
25600 A clean copy of the current article is always stored in a separate
25601 buffer to allow easier treatment.
25604 Gnus can suggest where to save articles (@pxref{Saving Articles}).
25607 Gnus doesn't have to do as much prompting when saving (@pxref{Saving
25611 (setq gnus-prompt-before-saving t)
25615 @code{gnus-uu} can view decoded files asynchronously while fetching
25616 articles (@pxref{Other Decode Variables}).
25619 (setq gnus-uu-grabbed-file-functions 'gnus-uu-grab-view)
25623 Filling in the article buffer now works properly on cited text
25624 (@pxref{Article Washing}).
25627 Hiding cited text adds buttons to toggle hiding, and how much
25628 cited text to hide is now customizable (@pxref{Article Hiding}).
25631 (setq gnus-cited-lines-visible 2)
25635 Boring headers can be hidden (@pxref{Article Hiding}).
25638 Default scoring values can now be set from the menu bar.
25641 Further syntax checking of outgoing articles have been added.
25647 @subsubsection Red Gnus
25649 New features in Gnus 5.4/5.5:
25653 \gnusfig{-5.5cm}{-4cm}{\epsfig{figure=ps/red,height=20cm}}
25660 @file{nntp.el} has been totally rewritten in an asynchronous fashion.
25663 Article prefetching functionality has been moved up into
25664 Gnus (@pxref{Asynchronous Fetching}).
25667 Scoring can now be performed with logical operators like @code{and},
25668 @code{or}, @code{not}, and parent redirection (@pxref{Advanced
25672 Article washing status can be displayed in the
25673 article mode line (@pxref{Misc Article}).
25676 @file{gnus.el} has been split into many smaller files.
25679 Suppression of duplicate articles based on Message-ID can be done
25680 (@pxref{Duplicate Suppression}).
25683 (setq gnus-suppress-duplicates t)
25687 New variables for specifying what score and adapt files are to be
25688 considered home score and adapt files (@pxref{Home Score File}) have
25692 @code{nndoc} was rewritten to be easily extendable (@pxref{Document
25693 Server Internals}).
25696 Groups can inherit group parameters from parent topics (@pxref{Topic
25700 Article editing has been revamped and is now actually usable.
25703 Signatures can be recognized in more intelligent fashions
25704 (@pxref{Article Signature}).
25707 Summary pick mode has been made to look more @code{nn}-like. Line
25708 numbers are displayed and the @kbd{.} command can be used to pick
25709 articles (@code{Pick and Read}).
25712 Commands for moving the @file{.newsrc.eld} from one server to
25713 another have been added (@pxref{Changing Servers}).
25716 There's a way now to specify that ``uninteresting'' fields be suppressed
25717 when generating lines in buffers (@pxref{Advanced Formatting}).
25720 Several commands in the group buffer can be undone with @kbd{C-M-_}
25724 Scoring can be done on words using the new score type @code{w}
25725 (@pxref{Score File Format}).
25728 Adaptive scoring can be done on a Subject word-by-word basis
25729 (@pxref{Adaptive Scoring}).
25732 (setq gnus-use-adaptive-scoring '(word))
25736 Scores can be decayed (@pxref{Score Decays}).
25739 (setq gnus-decay-scores t)
25743 Scoring can be performed using a regexp on the Date header. The Date is
25744 normalized to compact ISO 8601 format first (@pxref{Score File Format}).
25747 A new command has been added to remove all data on articles from
25748 the native server (@pxref{Changing Servers}).
25751 A new command for reading collections of documents
25752 (@code{nndoc} with @code{nnvirtual} on top) has been added---@kbd{C-M-d}
25753 (@pxref{Really Various Summary Commands}).
25756 Process mark sets can be pushed and popped (@pxref{Setting Process
25760 A new mail-to-news back end makes it possible to post even when the @acronym{NNTP}
25761 server doesn't allow posting (@pxref{Mail-To-News Gateways}).
25764 A new back end for reading searches from Web search engines
25765 (@dfn{DejaNews}, @dfn{Alta Vista}, @dfn{InReference}) has been added
25766 (@pxref{Web Searches}).
25769 Groups inside topics can now be sorted using the standard sorting
25770 functions, and each topic can be sorted independently (@pxref{Topic
25774 Subsets of the groups can be sorted independently (@code{Sorting
25778 Cached articles can be pulled into the groups (@pxref{Summary Generation
25782 \marginpar[\mbox{}\hfill\epsfig{figure=ps/fred,width=3cm}]{\epsfig{figure=ps/fred,width=3cm}}
25787 Score files are now applied in a more reliable order (@pxref{Score
25791 Reports on where mail messages end up can be generated (@pxref{Splitting
25795 More hooks and functions have been added to remove junk from incoming
25796 mail before saving the mail (@pxref{Washing Mail}).
25799 Emphasized text can be properly fontisized:
25805 @subsubsection Quassia Gnus
25807 New features in Gnus 5.6:
25812 New functionality for using Gnus as an offline newsreader has been
25813 added. A plethora of new commands and modes have been added.
25814 @xref{Gnus Unplugged}, for the full story.
25817 The @code{nndraft} back end has returned, but works differently than
25818 before. All Message buffers are now also articles in the @code{nndraft}
25819 group, which is created automatically.
25822 @code{gnus-alter-header-function} can now be used to alter header
25826 @code{gnus-summary-goto-article} now accept Message-ID's.
25829 A new Message command for deleting text in the body of a message
25830 outside the region: @kbd{C-c C-v}.
25833 You can now post to component group in @code{nnvirtual} groups with
25837 @code{nntp-rlogin-program}---new variable to ease customization.
25840 @code{C-u C-c C-c} in @code{gnus-article-edit-mode} will now inhibit
25841 re-highlighting of the article buffer.
25844 New element in @code{gnus-boring-article-headers}---@code{long-to}.
25847 @kbd{M-i} symbolic prefix command. @xref{Symbolic Prefixes}, for
25851 @kbd{L} and @kbd{I} in the summary buffer now take the symbolic prefix
25852 @kbd{a} to add the score rule to the @file{all.SCORE} file.
25855 @code{gnus-simplify-subject-functions} variable to allow greater
25856 control over simplification.
25859 @kbd{A T}---new command for fetching the current thread.
25862 @kbd{/ T}---new command for including the current thread in the
25866 @kbd{M-RET} is a new Message command for breaking cited text.
25869 @samp{\\1}-expressions are now valid in @code{nnmail-split-methods}.
25872 The @code{custom-face-lookup} function has been removed.
25873 If you used this function in your initialization files, you must
25874 rewrite them to use @code{face-spec-set} instead.
25877 Canceling now uses the current select method. Symbolic prefix
25878 @kbd{a} forces normal posting method.
25881 New command to translate M******** sm*rtq**t*s into proper
25885 For easier debugging of @code{nntp}, you can set
25886 @code{nntp-record-commands} to a non-@code{nil} value.
25889 @code{nntp} now uses @file{~/.authinfo}, a @file{.netrc}-like file, for
25890 controlling where and how to send @sc{authinfo} to @acronym{NNTP} servers.
25893 A command for editing group parameters from the summary buffer
25897 A history of where mails have been split is available.
25900 A new article date command has been added---@code{article-date-iso8601}.
25903 Subjects can be simplified when threading by setting
25904 @code{gnus-score-thread-simplify}.
25907 A new function for citing in Message has been
25908 added---@code{message-cite-original-without-signature}.
25911 @code{article-strip-all-blank-lines}---new article command.
25914 A new Message command to kill to the end of the article has
25918 A minimum adaptive score can be specified by using the
25919 @code{gnus-adaptive-word-minimum} variable.
25922 The ``lapsed date'' article header can be kept continually
25923 updated by the @code{gnus-start-date-timer} command.
25926 Web listserv archives can be read with the @code{nnlistserv} back end.
25929 Old dejanews archives can now be read by @code{nnweb}.
25933 @node Pterodactyl Gnus
25934 @subsubsection Pterodactyl Gnus
25936 New features in Gnus 5.8:
25941 The mail-fetching functions have changed. See the manual for the
25942 many details. In particular, all procmail fetching variables are gone.
25944 If you used procmail like in
25947 (setq nnmail-use-procmail t)
25948 (setq nnmail-spool-file 'procmail)
25949 (setq nnmail-procmail-directory "~/mail/incoming/")
25950 (setq nnmail-procmail-suffix "\\.in")
25953 this now has changed to
25957 '((directory :path "~/mail/incoming/"
25961 @xref{Mail Source Specifiers}.
25964 Gnus is now a @acronym{MIME}-capable reader. This affects many parts of
25965 Gnus, and adds a slew of new commands. See the manual for details.
25968 Gnus has also been multilingualized. This also affects too
25969 many parts of Gnus to summarize here, and adds many new variables.
25972 @code{gnus-auto-select-first} can now be a function to be
25973 called to position point.
25976 The user can now decide which extra headers should be included in
25977 summary buffers and @acronym{NOV} files.
25980 @code{gnus-article-display-hook} has been removed. Instead, a number
25981 of variables starting with @code{gnus-treat-} have been added.
25984 The Gnus posting styles have been redone again and now works in a
25985 subtly different manner.
25988 New web-based back ends have been added: @code{nnslashdot},
25989 @code{nnwarchive} and @code{nnultimate}. nnweb has been revamped,
25990 again, to keep up with ever-changing layouts.
25993 Gnus can now read @acronym{IMAP} mail via @code{nnimap}.
25998 @subsubsection Oort Gnus
26001 New features in Gnus 5.10:
26006 @kbd{F} (@code{gnus-article-followup-with-original}) and @kbd{R}
26007 (@code{gnus-article-reply-with-original}) only yank the text in the
26008 region if the region is active.
26011 @code{gnus-group-read-ephemeral-group} can be called interactively,
26015 In draft groups, @kbd{e} is now bound to @code{gnus-draft-edit-message}.
26016 Use @kbd{B w} for @code{gnus-summary-edit-article} instead.
26019 The revised Gnus @acronym{FAQ} is included in the manual,
26020 @xref{Frequently Asked Questions}.
26023 Upgrading from previous (stable) version if you have used Oort.
26025 If you have tried Oort (the unstable Gnus branch leading to this
26026 release) but went back to a stable version, be careful when upgrading to
26027 this version. In particular, you will probably want to remove all
26028 @file{.marks} (nnml) and @file{.mrk} (nnfolder) files, so that flags are
26029 read from your @file{.newsrc.eld} instead of from the
26030 @file{.marks}/@file{.mrk} file where this release store flags. See a
26031 later entry for more information about marks. Note that downgrading
26032 isn't save in general.
26037 More buttons for URLs, mail addresses, Message-IDs, Info links, man
26038 pages and Emacs or Gnus related references. @xref{Article Buttons}. The
26039 variables @code{gnus-button-@var{*}-level} can be used to control the
26040 appearance of all article buttons. @xref{Article Button Levels}.
26045 @code{gnus-dired-minor-mode} (see @ref{Other modes}) installs key
26046 bindings in dired buffers to send a file as an attachment, open a file
26047 using the appropriate mailcap entry, and print a file using the mailcap
26051 Gnus can display RSS newsfeeds as a newsgroup. @xref{RSS}.
26054 Single-part yenc encoded attachments can be decoded.
26059 The picons code has been reimplemented to work in GNU Emacs---some of
26060 the previous options have been removed or renamed.
26062 Picons are small ``personal icons'' representing users, domain and
26063 newsgroups, which can be displayed in the Article buffer.
26067 If the new option @code{gnus-treat-body-boundary} is non-@code{nil}, a
26068 boundary line is drawn at the end of the headers.
26071 Retrieval of charters and control messages
26073 There are new commands for fetching newsgroup charters (@kbd{H c}) and
26074 control messages (@kbd{H C}).
26079 You can delay the sending of a message with @kbd{C-c C-j} in the Message
26080 buffer. The messages are delivered at specified time. This is useful
26081 for sending yourself reminders. @xref{Delayed Articles}.
26084 If @code{auto-compression-mode} is enabled, attachments are automatically
26085 decompressed when activated.
26088 If the new option @code{nnml-use-compressed-files} is non-@code{nil},
26089 the nnml back end allows compressed message files.
26092 Signed article headers (X-PGP-Sig) can be verified with @kbd{W p}.
26095 The Summary Buffer uses an arrow in the fringe to indicate the current
26096 article. Use @code{(setq gnus-summary-display-arrow nil)} to disable it.
26099 Warn about email replies to news
26101 Do you often find yourself replying to news by email by mistake? Then
26102 the new option @code{gnus-confirm-mail-reply-to-news} is just the thing for
26106 If the new option @code{gnus-summary-display-while-building} is
26107 non-@code{nil}, the summary buffer is shown and updated as it's being
26111 The new @code{recent} mark @samp{.} indicates newly arrived messages (as
26112 opposed to old but unread messages).
26115 The new option @code{gnus-gcc-mark-as-read} automatically marks
26116 Gcc articles as read.
26119 The nndoc back end now supports mailman digests and exim bounces.
26122 Gnus supports RFC 2369 mailing list headers, and adds a number of
26123 related commands in mailing list groups. @xref{Mailing List}.
26126 The Date header can be displayed in a format that can be read aloud
26127 in English. @xref{Article Date}.
26130 The envelope sender address can be customized when using Sendmail.
26131 @xref{Mail Variables, Mail Variables,, message, Message Manual}.
26134 diffs are automatically highlighted in groups matching
26135 @code{mm-uu-diff-groups-regexp}
26138 @acronym{TLS} wrapper shipped with Gnus
26140 @acronym{TLS}/@acronym{SSL} is now supported in @acronym{IMAP} and
26141 @acronym{NNTP} via @file{tls.el} and GNUTLS. The old
26142 @acronym{TLS}/@acronym{SSL} support via (external third party)
26143 @file{ssl.el} and OpenSSL still works.
26146 New @file{make.bat} for compiling and installing Gnus under MS Windows
26148 Use @file{make.bat} if you want to install Gnus under MS Windows, the
26149 first argument to the batch-program should be the directory where
26150 @file{xemacs.exe} respectively @file{emacs.exe} is located, iff you want
26151 to install Gnus after compiling it, give @file{make.bat} @code{/copy} as
26152 the second parameter.
26154 @file{make.bat} has been rewritten from scratch, it now features
26155 automatic recognition of XEmacs and GNU Emacs, generates
26156 @file{gnus-load.el}, checks if errors occur while compilation and
26157 generation of info files and reports them at the end of the build
26158 process. It now uses @code{makeinfo} if it is available and falls
26159 back to @file{infohack.el} otherwise. @file{make.bat} should now
26160 install all files which are necessary to run Gnus and be generally a
26161 complete replacement for the @code{configure; make; make install}
26162 cycle used under Unix systems.
26164 The new @file{make.bat} makes @file{make-x.bat} superfluous, so it has
26168 Support for non-@acronym{ASCII} domain names
26170 Message supports non-@acronym{ASCII} domain names in From:, To: and
26171 Cc: and will query you whether to perform encoding when you try to
26172 send a message. The variable @code{message-use-idna} controls this.
26173 Gnus will also decode non-@acronym{ASCII} domain names in From:, To:
26174 and Cc: when you view a message. The variable @code{gnus-use-idna}
26178 Better handling of Microsoft citation styles
26180 Gnus now tries to recognize the mangled header block that some Microsoft
26181 mailers use to indicate that the rest of the message is a citation, even
26182 though it is not quoted in any way. The variable
26183 @code{gnus-cite-unsightly-citation-regexp} matches the start of these
26187 @code{gnus-article-skip-boring}
26189 If you set @code{gnus-article-skip-boring} to @code{t}, then Gnus will
26190 not scroll down to show you a page that contains only boring text,
26191 which by default means cited text and signature. You can customize
26192 what is skippable using @code{gnus-article-boring-faces}.
26194 This feature is especially useful if you read many articles that
26195 consist of a little new content at the top with a long, untrimmed
26196 message cited below.
26199 The format spec @code{%C} for positioning point has changed to @code{%*}.
26202 The new variable @code{gnus-parameters} can be used to set group parameters.
26204 Earlier this was done only via @kbd{G p} (or @kbd{G c}), which stored
26205 the parameters in @file{~/.newsrc.eld}, but via this variable you can
26206 enjoy the powers of customize, and simplified backups since you set the
26207 variable in @file{~/.emacs} instead of @file{~/.newsrc.eld}. The
26208 variable maps regular expressions matching group names to group
26211 (setq gnus-parameters
26213 (gnus-show-threads nil)
26214 (gnus-use-scoring nil))
26215 ("^nnimap:\\(foo.bar\\)$"
26216 (to-group . "\\1"))))
26220 Smileys (@samp{:-)}, @samp{;-)} etc) are now iconized for Emacs too.
26222 Put @code{(setq gnus-treat-display-smileys nil)} in @file{~/.emacs} to
26226 Gnus no longer generate the Sender: header automatically.
26228 Earlier it was generated iff the user configurable email address was
26229 different from the Gnus guessed default user address. As the guessing
26230 algorithm is rarely correct these days, and (more controversially) the
26231 only use of the Sender: header was to check if you are entitled to
26232 cancel/supersede news (which is now solved by Cancel Locks instead,
26233 see another entry), generation of the header has been disabled by
26234 default. See the variables @code{message-required-headers},
26235 @code{message-required-news-headers}, and
26236 @code{message-required-mail-headers}.
26239 Features from third party @file{message-utils.el} added to @file{message.el}.
26241 Message now asks if you wish to remove @samp{(was: <old subject>)} from
26242 subject lines (see @code{message-subject-trailing-was-query}). @kbd{C-c
26243 M-m} and @kbd{C-c M-f} inserts markers indicating included text.
26244 @kbd{C-c C-f a} adds a X-No-Archive: header. @kbd{C-c C-f x} inserts
26245 appropriate headers and a note in the body for cross-postings and
26246 followups (see the variables @code{message-cross-post-@var{*}}).
26249 References and X-Draft-Headers are no longer generated when you start
26250 composing messages and @code{message-generate-headers-first} is
26254 Improved anti-spam features.
26256 Gnus is now able to take out spam from your mail and news streams
26257 using a wide variety of programs and filter rules. Among the supported
26258 methods are RBL blocklists, bogofilter and white/blacklists. Hooks
26259 for easy use of external packages such as SpamAssassin and Hashcash
26260 are also new. @xref{Thwarting Email Spam}.
26263 Easy inclusion of X-Faces headers.
26266 Face headers handling.
26269 In the summary buffer, the new command @kbd{/ N} inserts new messages
26270 and @kbd{/ o} inserts old messages.
26273 Gnus decodes morse encoded messages if you press @kbd{W m}.
26276 Unread count correct in nnimap groups.
26278 The estimated number of unread articles in the group buffer should now
26279 be correct for nnimap groups. This is achieved by calling
26280 @code{nnimap-fixup-unread-after-getting-new-news} from the
26281 @code{gnus-setup-news-hook} (called on startup) and
26282 @code{gnus-after-getting-new-news-hook}. (called after getting new
26283 mail). If you have modified those variables from the default, you may
26284 want to add @code{nnimap-fixup-unread-after-getting-new-news} again. If
26285 you were happy with the estimate and want to save some (minimal) time
26286 when getting new mail, remove the function.
26289 Group Carbon Copy (GCC) quoting
26291 To support groups that contains SPC and other weird characters, groups
26292 are quoted before they are placed in the Gcc: header. This means
26293 variables such as @code{gnus-message-archive-group} should no longer
26294 contain quote characters to make groups containing SPC work. Also, if
26295 you are using the string @samp{nnml:foo, nnml:bar} (indicating Gcc
26296 into two groups) you must change it to return the list
26297 @code{("nnml:foo" "nnml:bar")}, otherwise the Gcc: line will be quoted
26298 incorrectly. Note that returning the string @samp{nnml:foo, nnml:bar}
26299 was incorrect earlier, it just didn't generate any problems since it
26300 was inserted directly.
26303 @file{~/News/overview/} not used.
26305 As a result of the following change, the @file{~/News/overview/}
26306 directory is not used any more. You can safely delete the entire
26312 The Gnus Agent has seen a major updated and is now enabled by default,
26313 and all nntp and nnimap servers from @code{gnus-select-method} and
26314 @code{gnus-secondary-select-method} are agentized by default. Earlier
26315 only the server in @code{gnus-select-method} was agentized by the
26316 default, and the agent was disabled by default. When the agent is
26317 enabled, headers are now also retrieved from the Agent cache instead
26318 of the back ends when possible. Earlier this only happened in the
26319 unplugged state. You can enroll or remove servers with @kbd{J a} and
26320 @kbd{J r} in the server buffer. Gnus will not download articles into
26321 the Agent cache, unless you instruct it to do so, though, by using
26322 @kbd{J u} or @kbd{J s} from the Group buffer. You revert to the old
26323 behaviour of having the Agent disabled with @code{(setq gnus-agent
26324 nil)}. Note that putting @code{(gnus-agentize)} in @file{~/.gnus.el}
26325 is not needed any more.
26328 @code{gnus-summary-line-format}
26330 The default value changed to @samp{%U%R%z%I%(%[%4L: %-23,23f%]%)
26331 %s\n}. Moreover @code{gnus-extra-headers},
26332 @code{nnmail-extra-headers} and @code{gnus-ignored-from-addresses}
26333 changed their default so that the users name will be replaced by the
26334 recipient's name or the group name posting to for @acronym{NNTP}
26338 @file{deuglify.el} (@code{gnus-article-outlook-deuglify-article})
26340 A new file from Raymond Scholz @email{rscholz@@zonix.de} for deuglifying
26341 broken Outlook (Express) articles.
26344 @code{(require 'gnus-load)}
26346 If you use a stand-alone Gnus distribution, you'd better add
26347 @code{(require 'gnus-load)} into your @file{~/.emacs} after adding the Gnus
26348 lisp directory into load-path.
26350 File @file{gnus-load.el} contains autoload commands, functions and variables,
26351 some of which may not be included in distributions of Emacsen.
26354 @code{gnus-slave-unplugged}
26356 A new command which starts Gnus offline in slave mode.
26359 @code{message-insinuate-rmail}
26361 Adding @code{(message-insinuate-rmail)} and @code{(setq
26362 mail-user-agent 'gnus-user-agent)} in @file{.emacs} convinces Rmail to
26363 compose, reply and forward messages in message-mode, where you can
26364 enjoy the power of @acronym{MML}.
26367 @code{message-minibuffer-local-map}
26369 The line below enables BBDB in resending a message:
26371 (define-key message-minibuffer-local-map [(tab)]
26372 'bbdb-complete-name)
26376 Externalizing and deleting of attachments.
26378 If @code{gnus-gcc-externalize-attachments} or
26379 @code{message-fcc-externalize-attachments} is non-@code{nil}, attach
26380 local files as external parts.
26382 The command @code{gnus-mime-save-part-and-strip} (bound to @kbd{C-o}
26383 on @acronym{MIME} buttons) saves a part and replaces the part with an
26384 external one. @code{gnus-mime-delete-part} (bound to @kbd{d} on
26385 @acronym{MIME} buttons) removes a part. It works only on back ends
26386 that support editing.
26389 @code{gnus-default-charset}
26391 The default value is determined from the
26392 @code{current-language-environment} variable, instead of
26393 @code{iso-8859-1}. Also the @samp{.*} item in
26394 @code{gnus-group-charset-alist} is removed.
26397 @code{gnus-posting-styles}
26399 Add a new format of match like
26401 ((header "to" "larsi.*org")
26402 (Organization "Somewhere, Inc."))
26404 The old format like the lines below is obsolete, but still accepted.
26406 (header "to" "larsi.*org"
26407 (Organization "Somewhere, Inc."))
26411 @code{message-ignored-news-headers} and @code{message-ignored-mail-headers}
26413 @samp{X-Draft-From} and @samp{X-Gnus-Agent-Meta-Information} have been
26414 added into these two variables. If you customized those, perhaps you
26415 need add those two headers too.
26418 Gnus reads the @acronym{NOV} and articles in the Agent if plugged.
26420 If one reads an article while plugged, and the article already exists
26421 in the Agent, it won't get downloaded once more. @code{(setq
26422 gnus-agent-cache nil)} reverts to the old behavior.
26425 Gnus supports the ``format=flowed'' (RFC 2646) parameter. On
26426 composing messages, it is enabled by @code{use-hard-newlines}.
26427 Decoding format=flowed was present but not documented in earlier
26431 Gnus supports the generation of RFC 2298 Disposition Notification requests.
26433 This is invoked with the @kbd{C-c M-n} key binding from message mode.
26436 Gnus supports Maildir groups.
26438 Gnus includes a new back end @file{nnmaildir.el}. @xref{Maildir}.
26441 Printing capabilities are enhanced.
26443 Gnus supports Muttprint natively with @kbd{O P} from the Summary and
26444 Article buffers. Also, each individual @acronym{MIME} part can be
26445 printed using @kbd{p} on the @acronym{MIME} button.
26448 Message supports the Importance: (RFC 2156) header.
26450 In the message buffer, @kbd{C-c C-f C-i} or @kbd{C-c C-u} cycles through
26454 Gnus supports Cancel Locks in News.
26456 This means a header @samp{Cancel-Lock} is inserted in news posting. It is
26457 used to determine if you wrote an article or not (for canceling and
26458 superseding). Gnus generates a random password string the first time
26459 you post a message, and saves it in your @file{~/.emacs} using the Custom
26460 system. While the variable is called @code{canlock-password}, it is not
26461 security sensitive data. Publishing your canlock string on the web
26462 will not allow anyone to be able to anything she could not already do.
26463 The behaviour can be changed by customizing @code{message-insert-canlock}.
26466 Gnus supports server-side mail filtering using Sieve.
26468 Sieve rules can be added as Group Parameters for groups, and the
26469 complete Sieve script is generated using @kbd{D g} from the Group
26470 buffer, and then uploaded to the server using @kbd{C-c C-l} in the
26471 generated Sieve buffer. @xref{Sieve Commands}, and the new Sieve
26472 manual @ref{Top, , Top, sieve, Emacs Sieve}.
26475 Extended format specs.
26477 Format spec @samp{%&user-date;} is added into
26478 @code{gnus-summary-line-format-alist}. Also, user defined extended
26479 format specs are supported. The extended format specs look like
26480 @samp{%u&foo;}, which invokes function
26481 @code{gnus-user-format-function-@var{foo}}. Because @samp{&} is used as the
26482 escape character, old user defined format @samp{%u&} is no longer supported.
26485 @kbd{/ *} (@code{gnus-summary-limit-include-cached}) is rewritten.
26487 It was aliased to @kbd{Y c}
26488 (@code{gnus-summary-insert-cached-articles}). The new function filters
26489 out other articles.
26491 @item Some limiting commands accept a @kbd{C-u} prefix to negate the match.
26493 If @kbd{C-u} is used on subject, author or extra headers, i.e., @kbd{/
26494 s}, @kbd{/ a}, and @kbd{/ x}
26495 (@code{gnus-summary-limit-to-@{subject,author,extra@}}) respectively, the
26496 result will be to display all articles that do not match the expression.
26499 Group names are treated as UTF-8 by default.
26501 This is supposedly what USEFOR wanted to migrate to. See
26502 @code{gnus-group-name-charset-group-alist} and
26503 @code{gnus-group-name-charset-method-alist} for customization.
26506 The nnml and nnfolder back ends store marks for each groups.
26508 This makes it possible to take backup of nnml/nnfolder servers/groups
26509 separately of @file{~/.newsrc.eld}, while preserving marks. It also
26510 makes it possible to share articles and marks between users (without
26511 sharing the @file{~/.newsrc.eld} file) within e.g. a department. It
26512 works by storing the marks stored in @file{~/.newsrc.eld} in a per-group
26513 file @file{.marks} (for nnml) and @file{@var{groupname}.mrk} (for
26514 nnfolder, named @var{groupname}). If the nnml/nnfolder is moved to
26515 another machine, Gnus will automatically use the @file{.marks} or
26516 @file{.mrk} file instead of the information in @file{~/.newsrc.eld}.
26517 The new server variables @code{nnml-marks-is-evil} and
26518 @code{nnfolder-marks-is-evil} can be used to disable this feature.
26521 The menu bar item (in Group and Summary buffer) named ``Misc'' has
26522 been renamed to ``Gnus''.
26525 The menu bar item (in Message mode) named ``@acronym{MML}'' has been
26526 renamed to ``Attachments''. Note that this menu also contains security
26527 related stuff, like signing and encryption (@pxref{Security, Security,,
26528 message, Message Manual}).
26531 @code{gnus-group-charset-alist} and
26532 @code{gnus-group-ignored-charsets-alist}.
26534 The regexps in these variables are compared with full group names
26535 instead of real group names in 5.8. Users who customize these
26536 variables should change those regexps accordingly. For example:
26538 ("^han\\>" euc-kr) -> ("\\(^\\|:\\)han\\>" euc-kr)
26542 Gnus supports @acronym{PGP} (RFC 1991/2440), @acronym{PGP/MIME} (RFC
26543 2015/3156) and @acronym{S/MIME} (RFC 2630-2633).
26545 It needs an external @acronym{S/MIME} and OpenPGP implementation, but no
26546 additional Lisp libraries. This add several menu items to the
26547 Attachments menu, and @kbd{C-c RET} key bindings, when composing
26548 messages. This also obsoletes @code{gnus-article-hide-pgp-hook}.
26551 Gnus inlines external parts (message/external).
26554 @acronym{MML} (Mime compose) prefix changed from @kbd{M-m} to @kbd{C-c
26557 This change was made to avoid conflict with the standard binding of
26558 @code{back-to-indentation}, which is also useful in message mode.
26561 The default for @code{message-forward-show-mml} changed to symbol @code{best}.
26563 The behaviour for the @code{best} value is to show @acronym{MML} (i.e.,
26564 convert to @acronym{MIME}) when appropriate. @acronym{MML} will not be
26565 used when forwarding signed or encrypted messages, as the conversion
26566 invalidate the digital signature.
26570 @subsubsection No Gnus
26573 New features in No Gnus:
26574 @c FIXME: Gnus 5.12?
26576 @include gnus-news.texi
26582 @section The Manual
26586 This manual was generated from a TeXinfo file and then run through
26587 either @code{texi2dvi}
26589 or my own home-brewed TeXinfo to \LaTeX\ transformer,
26590 and then run through @code{latex} and @code{dvips}
26592 to get what you hold in your hands now.
26594 The following conventions have been used:
26599 This is a @samp{string}
26602 This is a @kbd{keystroke}
26605 This is a @file{file}
26608 This is a @code{symbol}
26612 So if I were to say ``set @code{flargnoze} to @samp{yes}'', that would
26616 (setq flargnoze "yes")
26619 If I say ``set @code{flumphel} to @code{yes}'', that would mean:
26622 (setq flumphel 'yes)
26625 @samp{yes} and @code{yes} are two @emph{very} different things---don't
26626 ever get them confused.
26630 Of course, everything in this manual is of vital interest, so you should
26631 read it all. Several times. However, if you feel like skimming the
26632 manual, look for that gnu head you should see in the margin over
26633 there---it means that what's being discussed is of more importance than
26634 the rest of the stuff. (On the other hand, if everything is infinitely
26635 important, how can anything be more important than that? Just one more
26636 of the mysteries of this world, I guess.)
26642 @node On Writing Manuals
26643 @section On Writing Manuals
26645 I guess most manuals are written after-the-fact; documenting a program
26646 that's already there. This is not how this manual is written. When
26647 implementing something, I write the manual entry for that something
26648 straight away. I then see that it's difficult to explain the
26649 functionality, so I write how it's supposed to be, and then I change the
26650 implementation. Writing the documentation and writing the code goes
26653 This, of course, means that this manual has no, or little, flow. It
26654 documents absolutely everything in Gnus, but often not where you're
26655 looking for it. It is a reference manual, and not a guide to how to get
26658 That would be a totally different book, that should be written using the
26659 reference manual as source material. It would look quite differently.
26664 @section Terminology
26666 @cindex terminology
26671 This is what you are supposed to use this thing for---reading news.
26672 News is generally fetched from a nearby @acronym{NNTP} server, and is
26673 generally publicly available to everybody. If you post news, the entire
26674 world is likely to read just what you have written, and they'll all
26675 snigger mischievously. Behind your back.
26679 Everything that's delivered to you personally is mail. Some news/mail
26680 readers (like Gnus) blur the distinction between mail and news, but
26681 there is a difference. Mail is private. News is public. Mailing is
26682 not posting, and replying is not following up.
26686 Send a mail to the person who has written what you are reading.
26690 Post an article to the current newsgroup responding to the article you
26695 Gnus considers mail and news to be mostly the same, really. The only
26696 difference is how to access the actual articles. News articles are
26697 commonly fetched via the protocol @acronym{NNTP}, whereas mail
26698 messages could be read from a file on the local disk. The internal
26699 architecture of Gnus thus comprises a ``front end'' and a number of
26700 ``back ends''. Internally, when you enter a group (by hitting
26701 @key{RET}, say), you thereby invoke a function in the front end in
26702 Gnus. The front end then ``talks'' to a back end and says things like
26703 ``Give me the list of articles in the foo group'' or ``Show me article
26706 So a back end mainly defines either a protocol (the @code{nntp} back
26707 end accesses news via @acronym{NNTP}, the @code{nnimap} back end
26708 accesses mail via @acronym{IMAP}) or a file format and directory
26709 layout (the @code{nnspool} back end accesses news via the common
26710 ``spool directory'' format, the @code{nnml} back end access mail via a
26711 file format and directory layout that's quite similar).
26713 Gnus does not handle the underlying media, so to speak---this is all
26714 done by the back ends. A back end is a collection of functions to
26715 access the articles.
26717 However, sometimes the term ``back end'' is also used where ``server''
26718 would have been more appropriate. And then there is the term ``select
26719 method'' which can mean either. The Gnus terminology can be quite
26724 Gnus will always use one method (and back end) as the @dfn{native}, or
26725 default, way of getting news.
26729 You can also have any number of foreign groups active at the same time.
26730 These are groups that use non-native non-secondary back ends for getting
26735 Secondary back ends are somewhere half-way between being native and being
26736 foreign, but they mostly act like they are native.
26740 A message that has been posted as news.
26743 @cindex mail message
26744 A message that has been mailed.
26748 A mail message or news article
26752 The top part of a message, where administrative information (etc.) is
26757 The rest of an article. Everything not in the head is in the
26762 A line from the head of an article.
26766 A collection of such lines, or a collection of heads. Or even a
26767 collection of @acronym{NOV} lines.
26769 @item @acronym{NOV}
26770 @cindex @acronym{NOV}
26771 When Gnus enters a group, it asks the back end for the headers of all
26772 unread articles in the group. Most servers support the News OverView
26773 format, which is more compact and much faster to read and parse than the
26774 normal @sc{head} format.
26778 Each group is subscribed at some @dfn{level} or other (1-9). The ones
26779 that have a lower level are ``more'' subscribed than the groups with a
26780 higher level. In fact, groups on levels 1-5 are considered
26781 @dfn{subscribed}; 6-7 are @dfn{unsubscribed}; 8 are @dfn{zombies}; and 9
26782 are @dfn{killed}. Commands for listing groups and scanning for new
26783 articles will all use the numeric prefix as @dfn{working level}.
26785 @item killed groups
26786 @cindex killed groups
26787 No information on killed groups is stored or updated, which makes killed
26788 groups much easier to handle than subscribed groups.
26790 @item zombie groups
26791 @cindex zombie groups
26792 Just like killed groups, only slightly less dead.
26795 @cindex active file
26796 The news server has to keep track of what articles it carries, and what
26797 groups exist. All this information in stored in the active file, which
26798 is rather large, as you might surmise.
26801 @cindex bogus groups
26802 A group that exists in the @file{.newsrc} file, but isn't known to the
26803 server (i.e., it isn't in the active file), is a @emph{bogus group}.
26804 This means that the group probably doesn't exist (any more).
26807 @cindex activating groups
26808 The act of asking the server for info on a group and computing the
26809 number of unread articles is called @dfn{activating the group}.
26810 Un-activated groups are listed with @samp{*} in the group buffer.
26814 A machine one can connect to and get news (or mail) from.
26816 @item select method
26817 @cindex select method
26818 A structure that specifies the back end, the server and the virtual
26821 @item virtual server
26822 @cindex virtual server
26823 A named select method. Since a select method defines all there is to
26824 know about connecting to a (physical) server, taking the thing as a
26825 whole is a virtual server.
26829 Taking a buffer and running it through a filter of some sort. The
26830 result will (more often than not) be cleaner and more pleasing than the
26833 @item ephemeral groups
26834 @cindex ephemeral groups
26835 @cindex temporary groups
26836 Most groups store data on what articles you have read. @dfn{Ephemeral}
26837 groups are groups that will have no data stored---when you exit the
26838 group, it'll disappear into the aether.
26841 @cindex solid groups
26842 This is the opposite of ephemeral groups. All groups listed in the
26843 group buffer are solid groups.
26845 @item sparse articles
26846 @cindex sparse articles
26847 These are article placeholders shown in the summary buffer when
26848 @code{gnus-build-sparse-threads} has been switched on.
26852 To put responses to articles directly after the articles they respond
26853 to---in a hierarchical fashion.
26857 @cindex thread root
26858 The first article in a thread is the root. It is the ancestor of all
26859 articles in the thread.
26863 An article that has responses.
26867 An article that responds to a different article---its parent.
26871 A collection of messages in one file. The most common digest format is
26872 specified by RFC 1153.
26875 @cindex splitting, terminolgy
26876 @cindex mail sorting
26877 @cindex mail filtering (splitting)
26878 The action of sorting your emails according to certain rules. Sometimes
26879 incorrectly called mail filtering.
26885 @node Customization
26886 @section Customization
26887 @cindex general customization
26889 All variables are properly documented elsewhere in this manual. This
26890 section is designed to give general pointers on how to customize Gnus
26891 for some quite common situations.
26894 * Slow/Expensive Connection:: You run a local Emacs and get the news elsewhere.
26895 * Slow Terminal Connection:: You run a remote Emacs.
26896 * Little Disk Space:: You feel that having large setup files is icky.
26897 * Slow Machine:: You feel like buying a faster machine.
26901 @node Slow/Expensive Connection
26902 @subsection Slow/Expensive NNTP Connection
26904 If you run Emacs on a machine locally, and get your news from a machine
26905 over some very thin strings, you want to cut down on the amount of data
26906 Gnus has to get from the @acronym{NNTP} server.
26910 @item gnus-read-active-file
26911 Set this to @code{nil}, which will inhibit Gnus from requesting the
26912 entire active file from the server. This file is often v. large. You
26913 also have to set @code{gnus-check-new-newsgroups} and
26914 @code{gnus-check-bogus-newsgroups} to @code{nil} to make sure that Gnus
26915 doesn't suddenly decide to fetch the active file anyway.
26917 @item gnus-nov-is-evil
26918 This one has to be @code{nil}. If not, grabbing article headers from
26919 the @acronym{NNTP} server will not be very fast. Not all @acronym{NNTP} servers
26920 support @sc{xover}; Gnus will detect this by itself.
26924 @node Slow Terminal Connection
26925 @subsection Slow Terminal Connection
26927 Let's say you use your home computer for dialing up the system that runs
26928 Emacs and Gnus. If your modem is slow, you want to reduce (as much as
26929 possible) the amount of data sent over the wires.
26933 @item gnus-auto-center-summary
26934 Set this to @code{nil} to inhibit Gnus from re-centering the summary
26935 buffer all the time. If it is @code{vertical}, do only vertical
26936 re-centering. If it is neither @code{nil} nor @code{vertical}, do both
26937 horizontal and vertical recentering.
26939 @item gnus-visible-headers
26940 Cut down on the headers included in the articles to the
26941 minimum. You can, in fact, make do without them altogether---most of the
26942 useful data is in the summary buffer, anyway. Set this variable to
26943 @samp{^NEVVVVER} or @samp{From:}, or whatever you feel you need.
26945 Set this hook to all the available hiding commands:
26947 (setq gnus-treat-hide-headers 'head
26948 gnus-treat-hide-signature t
26949 gnus-treat-hide-citation t)
26952 @item gnus-use-full-window
26953 By setting this to @code{nil}, you can make all the windows smaller.
26954 While this doesn't really cut down much generally, it means that you
26955 have to see smaller portions of articles before deciding that you didn't
26956 want to read them anyway.
26958 @item gnus-thread-hide-subtree
26959 If this is non-@code{nil}, all threads in the summary buffer will be
26963 @item gnus-updated-mode-lines
26964 If this is @code{nil}, Gnus will not put information in the buffer mode
26965 lines, which might save some time.
26969 @node Little Disk Space
26970 @subsection Little Disk Space
26973 The startup files can get rather large, so you may want to cut their
26974 sizes a bit if you are running out of space.
26978 @item gnus-save-newsrc-file
26979 If this is @code{nil}, Gnus will never save @file{.newsrc}---it will
26980 only save @file{.newsrc.eld}. This means that you will not be able to
26981 use any other newsreaders than Gnus. This variable is @code{t} by
26984 @item gnus-read-newsrc-file
26985 If this is @code{nil}, Gnus will never read @file{.newsrc}---it will
26986 only read @file{.newsrc.eld}. This means that you will not be able to
26987 use any other newsreaders than Gnus. This variable is @code{t} by
26990 @item gnus-save-killed-list
26991 If this is @code{nil}, Gnus will not save the list of dead groups. You
26992 should also set @code{gnus-check-new-newsgroups} to @code{ask-server}
26993 and @code{gnus-check-bogus-newsgroups} to @code{nil} if you set this
26994 variable to @code{nil}. This variable is @code{t} by default.
27000 @subsection Slow Machine
27001 @cindex slow machine
27003 If you have a slow machine, or are just really impatient, there are a
27004 few things you can do to make Gnus run faster.
27006 Set @code{gnus-check-new-newsgroups} and
27007 @code{gnus-check-bogus-newsgroups} to @code{nil} to make startup faster.
27009 Set @code{gnus-show-threads}, @code{gnus-use-cross-reference} and
27010 @code{gnus-nov-is-evil} to @code{nil} to make entering and exiting the
27011 summary buffer faster.
27015 @node Troubleshooting
27016 @section Troubleshooting
27017 @cindex troubleshooting
27019 Gnus works @emph{so} well straight out of the box---I can't imagine any
27027 Make sure your computer is switched on.
27030 Make sure that you really load the current Gnus version. If you have
27031 been running @sc{gnus}, you need to exit Emacs and start it up again before
27035 Try doing an @kbd{M-x gnus-version}. If you get something that looks
27036 like @samp{T-gnus 6.17.* (based on Gnus v5.10.*; for SEMI 1.1*, FLIM
27037 1.1*)} you have the right files loaded. Otherwise you have some old
27038 @file{.el} files lying around. Delete these.
27041 Read the help group (@kbd{G h} in the group buffer) for a
27042 @acronym{FAQ} and a how-to.
27045 @vindex max-lisp-eval-depth
27046 Gnus works on many recursive structures, and in some extreme (and very
27047 rare) cases Gnus may recurse down ``too deeply'' and Emacs will beep at
27048 you. If this happens to you, set @code{max-lisp-eval-depth} to 500 or
27049 something like that.
27052 If all else fails, report the problem as a bug.
27055 @cindex reporting bugs
27057 @kindex M-x gnus-bug
27059 If you find a bug in Gnus, you can report it with the @kbd{M-x gnus-bug}
27060 command. @kbd{M-x set-variable RET debug-on-error RET t RET}, and send
27061 me the backtrace. I will fix bugs, but I can only fix them if you send
27062 me a precise description as to how to reproduce the bug.
27064 You really can never be too detailed in a bug report. Always use the
27065 @kbd{M-x gnus-bug} command when you make bug reports, even if it creates
27066 a 10Kb mail each time you use it, and even if you have sent me your
27067 environment 500 times before. I don't care. I want the full info each
27070 It is also important to remember that I have no memory whatsoever. If
27071 you send a bug report, and I send you a reply, and then you just send
27072 back ``No, it's not! Moron!'', I will have no idea what you are
27073 insulting me about. Always over-explain everything. It's much easier
27074 for all of us---if I don't have all the information I need, I will just
27075 mail you and ask for more info, and everything takes more time.
27077 If the problem you're seeing is very visual, and you can't quite explain
27078 it, copy the Emacs window to a file (with @code{xwd}, for instance), put
27079 it somewhere it can be reached, and include the URL of the picture in
27083 If you would like to contribute a patch to fix bugs or make
27084 improvements, please produce the patch using @samp{diff -u}.
27087 If you want to debug your problem further before reporting, possibly
27088 in order to solve the problem yourself and send a patch, you can use
27089 edebug. Debugging Lisp code is documented in the Elisp manual
27090 (@pxref{Debugging, , Debugging Lisp Programs, elisp, The GNU Emacs
27091 Lisp Reference Manual}). To get you started with edebug, consider if
27092 you discover some weird behaviour when pressing @kbd{c}, the first
27093 step is to do @kbd{C-h k c} and click on the hyperlink (Emacs only) in
27094 the documentation buffer that leads you to the function definition,
27095 then press @kbd{M-x edebug-defun RET} with point inside that function,
27096 return to Gnus and press @kbd{c} to invoke the code. You will be
27097 placed in the lisp buffer and can single step using @kbd{SPC} and
27098 evaluate expressions using @kbd{M-:} or inspect variables using
27099 @kbd{C-h v}, abort execution with @kbd{q}, and resume execution with
27100 @kbd{c} or @kbd{g}.
27105 Sometimes, a problem do not directly generate an elisp error but
27106 manifests itself by causing Gnus to be very slow. In these cases, you
27107 can use @kbd{M-x toggle-debug-on-quit} and press @kbd{C-g} when things are
27108 slow, and then try to analyze the backtrace (repeating the procedure
27109 helps isolating the real problem areas).
27111 A fancier approach is to use the elisp profiler, ELP. The profiler is
27112 (or should be) fully documented elsewhere, but to get you started
27113 there are a few steps that need to be followed. First, instrument the
27114 part of Gnus you are interested in for profiling, e.g. @kbd{M-x
27115 elp-instrument-package RET gnus} or @kbd{M-x elp-instrument-package
27116 RET message}. Then perform the operation that is slow and press
27117 @kbd{M-x elp-results}. You will then see which operations that takes
27118 time, and can debug them further. If the entire operation takes much
27119 longer than the time spent in the slowest function in the profiler
27120 output, you probably profiled the wrong part of Gnus. To reset
27121 profiling statistics, use @kbd{M-x elp-reset-all}. @kbd{M-x
27122 elp-restore-all} is supposed to remove profiling, but given the
27123 complexities and dynamic code generation in Gnus, it might not always
27126 @cindex gnu.emacs.gnus
27127 @cindex ding mailing list
27128 If you just need help, you are better off asking on
27129 @samp{gnu.emacs.gnus}. I'm not very helpful. You can also ask on
27130 @email{ding@@gnus.org, the ding mailing list}. Write to
27131 @email{ding-request@@gnus.org} to subscribe.
27135 @node Gnus Reference Guide
27136 @section Gnus Reference Guide
27138 It is my hope that other people will figure out smart stuff that Gnus
27139 can do, and that other people will write those smart things as well. To
27140 facilitate that I thought it would be a good idea to describe the inner
27141 workings of Gnus. And some of the not-so-inner workings, while I'm at
27144 You can never expect the internals of a program not to change, but I
27145 will be defining (in some details) the interface between Gnus and its
27146 back ends (this is written in stone), the format of the score files
27147 (ditto), data structures (some are less likely to change than others)
27148 and general methods of operation.
27151 * Gnus Utility Functions:: Common functions and variable to use.
27152 * Back End Interface:: How Gnus communicates with the servers.
27153 * Score File Syntax:: A BNF definition of the score file standard.
27154 * Headers:: How Gnus stores headers internally.
27155 * Ranges:: A handy format for storing mucho numbers.
27156 * Group Info:: The group info format.
27157 * Extended Interactive:: Symbolic prefixes and stuff.
27158 * Emacs/XEmacs Code:: Gnus can be run under all modern Emacsen.
27159 * Various File Formats:: Formats of files that Gnus use.
27163 @node Gnus Utility Functions
27164 @subsection Gnus Utility Functions
27165 @cindex Gnus utility functions
27166 @cindex utility functions
27168 @cindex internal variables
27170 When writing small functions to be run from hooks (and stuff), it's
27171 vital to have access to the Gnus internal functions and variables.
27172 Below is a list of the most common ones.
27176 @item gnus-newsgroup-name
27177 @vindex gnus-newsgroup-name
27178 This variable holds the name of the current newsgroup.
27180 @item gnus-find-method-for-group
27181 @findex gnus-find-method-for-group
27182 A function that returns the select method for @var{group}.
27184 @item gnus-group-real-name
27185 @findex gnus-group-real-name
27186 Takes a full (prefixed) Gnus group name, and returns the unprefixed
27189 @item gnus-group-prefixed-name
27190 @findex gnus-group-prefixed-name
27191 Takes an unprefixed group name and a select method, and returns the full
27192 (prefixed) Gnus group name.
27194 @item gnus-get-info
27195 @findex gnus-get-info
27196 Returns the group info list for @var{group}.
27198 @item gnus-group-unread
27199 @findex gnus-group-unread
27200 The number of unread articles in @var{group}, or @code{t} if that is
27204 @findex gnus-active
27205 The active entry for @var{group}.
27207 @item gnus-set-active
27208 @findex gnus-set-active
27209 Set the active entry for @var{group}.
27211 @item gnus-add-current-to-buffer-list
27212 @findex gnus-add-current-to-buffer-list
27213 Adds the current buffer to the list of buffers to be killed on Gnus
27216 @item gnus-continuum-version
27217 @findex gnus-continuum-version
27218 Takes a Gnus version string as a parameter and returns a floating point
27219 number. Earlier versions will always get a lower number than later
27222 @item gnus-group-read-only-p
27223 @findex gnus-group-read-only-p
27224 Says whether @var{group} is read-only or not.
27226 @item gnus-news-group-p
27227 @findex gnus-news-group-p
27228 Says whether @var{group} came from a news back end.
27230 @item gnus-ephemeral-group-p
27231 @findex gnus-ephemeral-group-p
27232 Says whether @var{group} is ephemeral or not.
27234 @item gnus-server-to-method
27235 @findex gnus-server-to-method
27236 Returns the select method corresponding to @var{server}.
27238 @item gnus-server-equal
27239 @findex gnus-server-equal
27240 Says whether two virtual servers are equal.
27242 @item gnus-group-native-p
27243 @findex gnus-group-native-p
27244 Says whether @var{group} is native or not.
27246 @item gnus-group-secondary-p
27247 @findex gnus-group-secondary-p
27248 Says whether @var{group} is secondary or not.
27250 @item gnus-group-foreign-p
27251 @findex gnus-group-foreign-p
27252 Says whether @var{group} is foreign or not.
27254 @item gnus-group-find-parameter
27255 @findex gnus-group-find-parameter
27256 Returns the parameter list of @var{group}. If given a second parameter,
27257 returns the value of that parameter for @var{group}.
27259 @item gnus-group-set-parameter
27260 @findex gnus-group-set-parameter
27261 Takes three parameters; @var{group}, @var{parameter} and @var{value}.
27263 @item gnus-narrow-to-body
27264 @findex gnus-narrow-to-body
27265 Narrows the current buffer to the body of the article.
27267 @item gnus-check-backend-function
27268 @findex gnus-check-backend-function
27269 Takes two parameters, @var{function} and @var{group}. If the back end
27270 @var{group} comes from supports @var{function}, return non-@code{nil}.
27273 (gnus-check-backend-function "request-scan" "nnml:misc")
27277 @item gnus-read-method
27278 @findex gnus-read-method
27279 Prompts the user for a select method.
27284 @node Back End Interface
27285 @subsection Back End Interface
27287 Gnus doesn't know anything about @acronym{NNTP}, spools, mail or virtual
27288 groups. It only knows how to talk to @dfn{virtual servers}. A virtual
27289 server is a @dfn{back end} and some @dfn{back end variables}. As examples
27290 of the first, we have @code{nntp}, @code{nnspool} and @code{nnmbox}. As
27291 examples of the latter we have @code{nntp-port-number} and
27292 @code{nnmbox-directory}.
27294 When Gnus asks for information from a back end---say @code{nntp}---on
27295 something, it will normally include a virtual server name in the
27296 function parameters. (If not, the back end should use the ``current''
27297 virtual server.) For instance, @code{nntp-request-list} takes a virtual
27298 server as its only (optional) parameter. If this virtual server hasn't
27299 been opened, the function should fail.
27301 Note that a virtual server name has no relation to some physical server
27302 name. Take this example:
27306 (nntp-address "ifi.uio.no")
27307 (nntp-port-number 4324))
27310 Here the virtual server name is @samp{odd-one} while the name of
27311 the physical server is @samp{ifi.uio.no}.
27313 The back ends should be able to switch between several virtual servers.
27314 The standard back ends implement this by keeping an alist of virtual
27315 server environments that they pull down/push up when needed.
27317 There are two groups of interface functions: @dfn{required functions},
27318 which must be present, and @dfn{optional functions}, which Gnus will
27319 always check for presence before attempting to call 'em.
27321 All these functions are expected to return data in the buffer
27322 @code{nntp-server-buffer} (@samp{ *nntpd*}), which is somewhat
27323 unfortunately named, but we'll have to live with it. When I talk about
27324 @dfn{resulting data}, I always refer to the data in that buffer. When I
27325 talk about @dfn{return value}, I talk about the function value returned by
27326 the function call. Functions that fail should return @code{nil} as the
27329 Some back ends could be said to be @dfn{server-forming} back ends, and
27330 some might be said not to be. The latter are back ends that generally
27331 only operate on one group at a time, and have no concept of ``server''
27332 ---they have a group, and they deliver info on that group and nothing
27335 Gnus identifies each message by way of group name and article number. A
27336 few remarks about these article numbers might be useful. First of all,
27337 the numbers are positive integers. Secondly, it is normally not
27338 possible for later articles to ``re-use'' older article numbers without
27339 confusing Gnus. That is, if a group has ever contained a message
27340 numbered 42, then no other message may get that number, or Gnus will get
27341 mightily confused.@footnote{See the function
27342 @code{nnchoke-request-update-info}, @ref{Optional Back End Functions}.}
27343 Third, article numbers must be assigned in order of arrival in the
27344 group; this is not necessarily the same as the date of the message.
27346 The previous paragraph already mentions all the ``hard'' restrictions that
27347 article numbers must fulfill. But it seems that it might be useful to
27348 assign @emph{consecutive} article numbers, for Gnus gets quite confused
27349 if there are holes in the article numbering sequence. However, due to
27350 the ``no-reuse'' restriction, holes cannot be avoided altogether. It's
27351 also useful for the article numbers to start at 1 to avoid running out
27352 of numbers as long as possible.
27354 Note that by convention, back ends are named @code{nnsomething}, but
27355 Gnus also comes with some @code{nnnotbackends}, such as
27356 @file{nnheader.el}, @file{nnmail.el} and @file{nnoo.el}.
27358 In the examples and definitions I will refer to the imaginary back end
27361 @cindex @code{nnchoke}
27364 * Required Back End Functions:: Functions that must be implemented.
27365 * Optional Back End Functions:: Functions that need not be implemented.
27366 * Error Messaging:: How to get messages and report errors.
27367 * Writing New Back Ends:: Extending old back ends.
27368 * Hooking New Back Ends Into Gnus:: What has to be done on the Gnus end.
27369 * Mail-like Back Ends:: Some tips on mail back ends.
27373 @node Required Back End Functions
27374 @subsubsection Required Back End Functions
27378 @item (nnchoke-retrieve-headers ARTICLES &optional GROUP SERVER FETCH-OLD)
27380 @var{articles} is either a range of article numbers or a list of
27381 @code{Message-ID}s. Current back ends do not fully support either---only
27382 sequences (lists) of article numbers, and most back ends do not support
27383 retrieval of @code{Message-ID}s. But they should try for both.
27385 The result data should either be HEADs or @acronym{NOV} lines, and the result
27386 value should either be @code{headers} or @code{nov} to reflect this.
27387 This might later be expanded to @code{various}, which will be a mixture
27388 of HEADs and @acronym{NOV} lines, but this is currently not supported by Gnus.
27390 If @var{fetch-old} is non-@code{nil} it says to try fetching ``extra
27391 headers'', in some meaning of the word. This is generally done by
27392 fetching (at most) @var{fetch-old} extra headers less than the smallest
27393 article number in @code{articles}, and filling the gaps as well. The
27394 presence of this parameter can be ignored if the back end finds it
27395 cumbersome to follow the request. If this is non-@code{nil} and not a
27396 number, do maximum fetches.
27398 Here's an example HEAD:
27401 221 1056 Article retrieved.
27402 Path: ifi.uio.no!sturles
27403 From: sturles@@ifi.uio.no (Sturle Sunde)
27404 Newsgroups: ifi.discussion
27405 Subject: Re: Something very droll
27406 Date: 27 Oct 1994 14:02:57 +0100
27407 Organization: Dept. of Informatics, University of Oslo, Norway
27409 Message-ID: <38o8e1$a0o@@holmenkollen.ifi.uio.no>
27410 References: <38jdmq$4qu@@visbur.ifi.uio.no>
27411 NNTP-Posting-Host: holmenkollen.ifi.uio.no
27415 So a @code{headers} return value would imply that there's a number of
27416 these in the data buffer.
27418 Here's a BNF definition of such a buffer:
27422 head = error / valid-head
27423 error-message = [ "4" / "5" ] 2number " " <error message> eol
27424 valid-head = valid-message *header "." eol
27425 valid-message = "221 " <number> " Article retrieved." eol
27426 header = <text> eol
27430 (The version of BNF used here is the one used in RFC822.)
27432 If the return value is @code{nov}, the data buffer should contain
27433 @dfn{network overview database} lines. These are basically fields
27437 nov-buffer = *nov-line
27438 nov-line = field 7*8[ <TAB> field ] eol
27439 field = <text except TAB>
27442 For a closer look at what should be in those fields,
27446 @item (nnchoke-open-server SERVER &optional DEFINITIONS)
27448 @var{server} is here the virtual server name. @var{definitions} is a
27449 list of @code{(VARIABLE VALUE)} pairs that define this virtual server.
27451 If the server can't be opened, no error should be signaled. The back end
27452 may then choose to refuse further attempts at connecting to this
27453 server. In fact, it should do so.
27455 If the server is opened already, this function should return a
27456 non-@code{nil} value. There should be no data returned.
27459 @item (nnchoke-close-server &optional SERVER)
27461 Close connection to @var{server} and free all resources connected
27462 to it. Return @code{nil} if the server couldn't be closed for some
27465 There should be no data returned.
27468 @item (nnchoke-request-close)
27470 Close connection to all servers and free all resources that the back end
27471 have reserved. All buffers that have been created by that back end
27472 should be killed. (Not the @code{nntp-server-buffer}, though.) This
27473 function is generally only called when Gnus is shutting down.
27475 There should be no data returned.
27478 @item (nnchoke-server-opened &optional SERVER)
27480 If @var{server} is the current virtual server, and the connection to the
27481 physical server is alive, then this function should return a
27482 non-@code{nil} value. This function should under no circumstances
27483 attempt to reconnect to a server we have lost connection to.
27485 There should be no data returned.
27488 @item (nnchoke-status-message &optional SERVER)
27490 This function should return the last error message from @var{server}.
27492 There should be no data returned.
27495 @item (nnchoke-request-article ARTICLE &optional GROUP SERVER TO-BUFFER)
27497 The result data from this function should be the article specified by
27498 @var{article}. This might either be a @code{Message-ID} or a number.
27499 It is optional whether to implement retrieval by @code{Message-ID}, but
27500 it would be nice if that were possible.
27502 If @var{to-buffer} is non-@code{nil}, the result data should be returned
27503 in this buffer instead of the normal data buffer. This is to make it
27504 possible to avoid copying large amounts of data from one buffer to
27505 another, while Gnus mainly requests articles to be inserted directly
27506 into its article buffer.
27508 If it is at all possible, this function should return a cons cell where
27509 the @code{car} is the group name the article was fetched from, and the @code{cdr} is
27510 the article number. This will enable Gnus to find out what the real
27511 group and article numbers are when fetching articles by
27512 @code{Message-ID}. If this isn't possible, @code{t} should be returned
27513 on successful article retrieval.
27516 @item (nnchoke-request-group GROUP &optional SERVER FAST)
27518 Get data on @var{group}. This function also has the side effect of
27519 making @var{group} the current group.
27521 If @var{fast}, don't bother to return useful data, just make @var{group}
27524 Here's an example of some result data and a definition of the same:
27527 211 56 1000 1059 ifi.discussion
27530 The first number is the status, which should be 211. Next is the
27531 total number of articles in the group, the lowest article number, the
27532 highest article number, and finally the group name. Note that the total
27533 number of articles may be less than one might think while just
27534 considering the highest and lowest article numbers, but some articles
27535 may have been canceled. Gnus just discards the total-number, so
27536 whether one should take the bother to generate it properly (if that is a
27537 problem) is left as an exercise to the reader. If the group contains no
27538 articles, the lowest article number should be reported as 1 and the
27542 group-status = [ error / info ] eol
27543 error = [ "4" / "5" ] 2<number> " " <Error message>
27544 info = "211 " 3* [ <number> " " ] <string>
27548 @item (nnchoke-close-group GROUP &optional SERVER)
27550 Close @var{group} and free any resources connected to it. This will be
27551 a no-op on most back ends.
27553 There should be no data returned.
27556 @item (nnchoke-request-list &optional SERVER)
27558 Return a list of all groups available on @var{server}. And that means
27561 Here's an example from a server that only carries two groups:
27564 ifi.test 0000002200 0000002000 y
27565 ifi.discussion 3324 3300 n
27568 On each line we have a group name, then the highest article number in
27569 that group, the lowest article number, and finally a flag. If the group
27570 contains no articles, the lowest article number should be reported as 1
27571 and the highest as 0.
27574 active-file = *active-line
27575 active-line = name " " <number> " " <number> " " flags eol
27577 flags = "n" / "y" / "m" / "x" / "j" / "=" name
27580 The flag says whether the group is read-only (@samp{n}), is moderated
27581 (@samp{m}), is dead (@samp{x}), is aliased to some other group
27582 (@samp{=other-group}) or none of the above (@samp{y}).
27585 @item (nnchoke-request-post &optional SERVER)
27587 This function should post the current buffer. It might return whether
27588 the posting was successful or not, but that's not required. If, for
27589 instance, the posting is done asynchronously, it has generally not been
27590 completed by the time this function concludes. In that case, this
27591 function should set up some kind of sentinel to beep the user loud and
27592 clear if the posting could not be completed.
27594 There should be no result data from this function.
27599 @node Optional Back End Functions
27600 @subsubsection Optional Back End Functions
27604 @item (nnchoke-retrieve-groups GROUPS &optional SERVER)
27606 @var{groups} is a list of groups, and this function should request data
27607 on all those groups. How it does it is of no concern to Gnus, but it
27608 should attempt to do this in a speedy fashion.
27610 The return value of this function can be either @code{active} or
27611 @code{group}, which says what the format of the result data is. The
27612 former is in the same format as the data from
27613 @code{nnchoke-request-list}, while the latter is a buffer full of lines
27614 in the same format as @code{nnchoke-request-group} gives.
27617 group-buffer = *active-line / *group-status
27621 @item (nnchoke-request-update-info GROUP INFO &optional SERVER)
27623 A Gnus group info (@pxref{Group Info}) is handed to the back end for
27624 alterations. This comes in handy if the back end really carries all
27625 the information (as is the case with virtual and imap groups). This
27626 function should destructively alter the info to suit its needs, and
27627 should return a non-@code{nil} value.
27629 There should be no result data from this function.
27632 @item (nnchoke-request-type GROUP &optional ARTICLE)
27634 When the user issues commands for ``sending news'' (@kbd{F} in the
27635 summary buffer, for instance), Gnus has to know whether the article the
27636 user is following up on is news or mail. This function should return
27637 @code{news} if @var{article} in @var{group} is news, @code{mail} if it
27638 is mail and @code{unknown} if the type can't be decided. (The
27639 @var{article} parameter is necessary in @code{nnvirtual} groups which
27640 might very well combine mail groups and news groups.) Both @var{group}
27641 and @var{article} may be @code{nil}.
27643 There should be no result data from this function.
27646 @item (nnchoke-request-set-mark GROUP ACTION &optional SERVER)
27648 Set/remove/add marks on articles. Normally Gnus handles the article
27649 marks (such as read, ticked, expired etc) internally, and store them in
27650 @file{~/.newsrc.eld}. Some back ends (such as @acronym{IMAP}) however carry
27651 all information about the articles on the server, so Gnus need to
27652 propagate the mark information to the server.
27654 @var{action} is a list of mark setting requests, having this format:
27657 (RANGE ACTION MARK)
27660 @var{range} is a range of articles you wish to update marks on.
27661 @var{action} is @code{add} or @code{del}, used to add marks or remove
27662 marks (preserving all marks not mentioned). @var{mark} is a list of
27663 marks; where each mark is a symbol. Currently used marks are
27664 @code{read}, @code{tick}, @code{reply}, @code{expire}, @code{killed},
27665 @code{dormant}, @code{save}, @code{download}, @code{unsend},
27666 @code{forward} and @code{recent}, but your back end should, if
27667 possible, not limit itself to these.
27669 Given contradictory actions, the last action in the list should be the
27670 effective one. That is, if your action contains a request to add the
27671 @code{tick} mark on article 1 and, later in the list, a request to
27672 remove the mark on the same article, the mark should in fact be removed.
27674 An example action list:
27677 (((5 12 30) 'del '(tick))
27678 ((10 . 90) 'add '(read expire))
27679 ((92 94) 'del '(read)))
27682 The function should return a range of articles it wasn't able to set the
27683 mark on (currently not used for anything).
27685 There should be no result data from this function.
27687 @item (nnchoke-request-update-mark GROUP ARTICLE MARK)
27689 If the user tries to set a mark that the back end doesn't like, this
27690 function may change the mark. Gnus will use whatever this function
27691 returns as the mark for @var{article} instead of the original
27692 @var{mark}. If the back end doesn't care, it must return the original
27693 @var{mark}, and not @code{nil} or any other type of garbage.
27695 The only use for this I can see is what @code{nnvirtual} does with
27696 it---if a component group is auto-expirable, marking an article as read
27697 in the virtual group should result in the article being marked as
27700 There should be no result data from this function.
27703 @item (nnchoke-request-scan &optional GROUP SERVER)
27705 This function may be called at any time (by Gnus or anything else) to
27706 request that the back end check for incoming articles, in one way or
27707 another. A mail back end will typically read the spool file or query
27708 the @acronym{POP} server when this function is invoked. The
27709 @var{group} doesn't have to be heeded---if the back end decides that
27710 it is too much work just scanning for a single group, it may do a
27711 total scan of all groups. It would be nice, however, to keep things
27712 local if that's practical.
27714 There should be no result data from this function.
27717 @item (nnchoke-request-group-description GROUP &optional SERVER)
27719 The result data from this function should be a description of
27723 description-line = name <TAB> description eol
27725 description = <text>
27728 @item (nnchoke-request-list-newsgroups &optional SERVER)
27730 The result data from this function should be the description of all
27731 groups available on the server.
27734 description-buffer = *description-line
27738 @item (nnchoke-request-newgroups DATE &optional SERVER)
27740 The result data from this function should be all groups that were
27741 created after @samp{date}, which is in normal human-readable date format
27742 (i.e., the date format used in mail and news headers, and returned by
27743 the function @code{message-make-date} by default). The data should be
27744 in the active buffer format.
27746 It is okay for this function to return ``too many'' groups; some back ends
27747 might find it cheaper to return the full list of groups, rather than
27748 just the new groups. But don't do this for back ends with many groups.
27749 Normally, if the user creates the groups herself, there won't be too
27750 many groups, so @code{nnml} and the like are probably safe. But for
27751 back ends like @code{nntp}, where the groups have been created by the
27752 server, it is quite likely that there can be many groups.
27755 @item (nnchoke-request-create-group GROUP &optional SERVER)
27757 This function should create an empty group with name @var{group}.
27759 There should be no return data.
27762 @item (nnchoke-request-expire-articles ARTICLES &optional GROUP SERVER FORCE)
27764 This function should run the expiry process on all articles in the
27765 @var{articles} range (which is currently a simple list of article
27766 numbers.) It is left up to the back end to decide how old articles
27767 should be before they are removed by this function. If @var{force} is
27768 non-@code{nil}, all @var{articles} should be deleted, no matter how new
27771 This function should return a list of articles that it did not/was not
27774 There should be no result data returned.
27777 @item (nnchoke-request-move-article ARTICLE GROUP SERVER ACCEPT-FORM &optional LAST)
27779 This function should move @var{article} (which is a number) from
27780 @var{group} by calling @var{accept-form}.
27782 This function should ready the article in question for moving by
27783 removing any header lines it has added to the article, and generally
27784 should ``tidy up'' the article. Then it should @code{eval}
27785 @var{accept-form} in the buffer where the ``tidy'' article is. This
27786 will do the actual copying. If this @code{eval} returns a
27787 non-@code{nil} value, the article should be removed.
27789 If @var{last} is @code{nil}, that means that there is a high likelihood
27790 that there will be more requests issued shortly, so that allows some
27793 The function should return a cons where the @code{car} is the group name and
27794 the @code{cdr} is the article number that the article was entered as.
27796 The group should exist before the back end is asked to accept the
27797 article for that group.
27799 There should be no data returned.
27802 @item (nnchoke-request-accept-article GROUP &optional SERVER LAST)
27804 This function takes the current buffer and inserts it into @var{group}.
27805 If @var{last} in @code{nil}, that means that there will be more calls to
27806 this function in short order.
27808 The function should return a cons where the @code{car} is the group name and
27809 the @code{cdr} is the article number that the article was entered as.
27811 There should be no data returned.
27814 @item (nnchoke-request-replace-article ARTICLE GROUP BUFFER)
27816 This function should remove @var{article} (which is a number) from
27817 @var{group} and insert @var{buffer} there instead.
27819 There should be no data returned.
27822 @item (nnchoke-request-delete-group GROUP FORCE &optional SERVER)
27824 This function should delete @var{group}. If @var{force}, it should
27825 really delete all the articles in the group, and then delete the group
27826 itself. (If there is such a thing as ``the group itself''.)
27828 There should be no data returned.
27831 @item (nnchoke-request-rename-group GROUP NEW-NAME &optional SERVER)
27833 This function should rename @var{group} into @var{new-name}. All
27834 articles in @var{group} should move to @var{new-name}.
27836 There should be no data returned.
27841 @node Error Messaging
27842 @subsubsection Error Messaging
27844 @findex nnheader-report
27845 @findex nnheader-get-report
27846 The back ends should use the function @code{nnheader-report} to report
27847 error conditions---they should not raise errors when they aren't able to
27848 perform a request. The first argument to this function is the back end
27849 symbol, and the rest are interpreted as arguments to @code{format} if
27850 there are multiple of them, or just a string if there is one of them.
27851 This function must always returns @code{nil}.
27854 (nnheader-report 'nnchoke "You did something totally bogus")
27856 (nnheader-report 'nnchoke "Could not request group %s" group)
27859 Gnus, in turn, will call @code{nnheader-get-report} when it gets a
27860 @code{nil} back from a server, and this function returns the most
27861 recently reported message for the back end in question. This function
27862 takes one argument---the server symbol.
27864 Internally, these functions access @var{back-end}@code{-status-string},
27865 so the @code{nnchoke} back end will have its error message stored in
27866 @code{nnchoke-status-string}.
27869 @node Writing New Back Ends
27870 @subsubsection Writing New Back Ends
27872 Many back ends are quite similar. @code{nnml} is just like
27873 @code{nnspool}, but it allows you to edit the articles on the server.
27874 @code{nnmh} is just like @code{nnml}, but it doesn't use an active file,
27875 and it doesn't maintain overview databases. @code{nndir} is just like
27876 @code{nnml}, but it has no concept of ``groups'', and it doesn't allow
27879 It would make sense if it were possible to ``inherit'' functions from
27880 back ends when writing new back ends. And, indeed, you can do that if you
27881 want to. (You don't have to if you don't want to, of course.)
27883 All the back ends declare their public variables and functions by using a
27884 package called @code{nnoo}.
27886 To inherit functions from other back ends (and allow other back ends to
27887 inherit functions from the current back end), you should use the
27893 This macro declares the first parameter to be a child of the subsequent
27894 parameters. For instance:
27897 (nnoo-declare nndir
27901 @code{nndir} has declared here that it intends to inherit functions from
27902 both @code{nnml} and @code{nnmh}.
27905 This macro is equivalent to @code{defvar}, but registers the variable as
27906 a public server variable. Most state-oriented variables should be
27907 declared with @code{defvoo} instead of @code{defvar}.
27909 In addition to the normal @code{defvar} parameters, it takes a list of
27910 variables in the parent back ends to map the variable to when executing
27911 a function in those back ends.
27914 (defvoo nndir-directory nil
27915 "Where nndir will look for groups."
27916 nnml-current-directory nnmh-current-directory)
27919 This means that @code{nnml-current-directory} will be set to
27920 @code{nndir-directory} when an @code{nnml} function is called on behalf
27921 of @code{nndir}. (The same with @code{nnmh}.)
27923 @item nnoo-define-basics
27924 This macro defines some common functions that almost all back ends should
27928 (nnoo-define-basics nndir)
27932 This macro is just like @code{defun} and takes the same parameters. In
27933 addition to doing the normal @code{defun} things, it registers the
27934 function as being public so that other back ends can inherit it.
27936 @item nnoo-map-functions
27937 This macro allows mapping of functions from the current back end to
27938 functions from the parent back ends.
27941 (nnoo-map-functions nndir
27942 (nnml-retrieve-headers 0 nndir-current-group 0 0)
27943 (nnmh-request-article 0 nndir-current-group 0 0))
27946 This means that when @code{nndir-retrieve-headers} is called, the first,
27947 third, and fourth parameters will be passed on to
27948 @code{nnml-retrieve-headers}, while the second parameter is set to the
27949 value of @code{nndir-current-group}.
27952 This macro allows importing functions from back ends. It should be the
27953 last thing in the source file, since it will only define functions that
27954 haven't already been defined.
27960 nnmh-request-newgroups)
27964 This means that calls to @code{nndir-request-list} should just be passed
27965 on to @code{nnmh-request-list}, while all public functions from
27966 @code{nnml} that haven't been defined in @code{nndir} yet should be
27971 Below is a slightly shortened version of the @code{nndir} back end.
27974 ;;; @r{nndir.el --- single directory newsgroup access for Gnus}
27975 ;; @r{Copyright (C) 1995,96 Free Software Foundation, Inc.}
27979 (require 'nnheader)
27983 (eval-when-compile (require 'cl))
27985 (nnoo-declare nndir
27988 (defvoo nndir-directory nil
27989 "Where nndir will look for groups."
27990 nnml-current-directory nnmh-current-directory)
27992 (defvoo nndir-nov-is-evil nil
27993 "*Non-nil means that nndir will never retrieve NOV headers."
27996 (defvoo nndir-current-group ""
27998 nnml-current-group nnmh-current-group)
27999 (defvoo nndir-top-directory nil nil nnml-directory nnmh-directory)
28000 (defvoo nndir-get-new-mail nil nil nnml-get-new-mail nnmh-get-new-mail)
28002 (defvoo nndir-status-string "" nil nnmh-status-string)
28003 (defconst nndir-version "nndir 1.0")
28005 ;;; @r{Interface functions.}
28007 (nnoo-define-basics nndir)
28009 (deffoo nndir-open-server (server &optional defs)
28010 (setq nndir-directory
28011 (or (cadr (assq 'nndir-directory defs))
28013 (unless (assq 'nndir-directory defs)
28014 (push `(nndir-directory ,server) defs))
28015 (push `(nndir-current-group
28016 ,(file-name-nondirectory
28017 (directory-file-name nndir-directory)))
28019 (push `(nndir-top-directory
28020 ,(file-name-directory (directory-file-name nndir-directory)))
28022 (nnoo-change-server 'nndir server defs))
28024 (nnoo-map-functions nndir
28025 (nnml-retrieve-headers 0 nndir-current-group 0 0)
28026 (nnmh-request-article 0 nndir-current-group 0 0)
28027 (nnmh-request-group nndir-current-group 0 0)
28028 (nnmh-close-group nndir-current-group 0))
28032 nnmh-status-message
28034 nnmh-request-newgroups))
28040 @node Hooking New Back Ends Into Gnus
28041 @subsubsection Hooking New Back Ends Into Gnus
28043 @vindex gnus-valid-select-methods
28044 @findex gnus-declare-backend
28045 Having Gnus start using your new back end is rather easy---you just
28046 declare it with the @code{gnus-declare-backend} functions. This will
28047 enter the back end into the @code{gnus-valid-select-methods} variable.
28049 @code{gnus-declare-backend} takes two parameters---the back end name and
28050 an arbitrary number of @dfn{abilities}.
28055 (gnus-declare-backend "nnchoke" 'mail 'respool 'address)
28058 The above line would then go in the @file{nnchoke.el} file.
28060 The abilities can be:
28064 This is a mailish back end---followups should (probably) go via mail.
28066 This is a newsish back end---followups should (probably) go via news.
28068 This back end supports both mail and news.
28070 This is neither a post nor mail back end---it's something completely
28073 It supports respooling---or rather, it is able to modify its source
28074 articles and groups.
28076 The name of the server should be in the virtual server name. This is
28077 true for almost all back ends.
28078 @item prompt-address
28079 The user should be prompted for an address when doing commands like
28080 @kbd{B} in the group buffer. This is true for back ends like
28081 @code{nntp}, but not @code{nnmbox}, for instance.
28085 @node Mail-like Back Ends
28086 @subsubsection Mail-like Back Ends
28088 One of the things that separate the mail back ends from the rest of the
28089 back ends is the heavy dependence by most of the mail back ends on
28090 common functions in @file{nnmail.el}. For instance, here's the
28091 definition of @code{nnml-request-scan}:
28094 (deffoo nnml-request-scan (&optional group server)
28095 (setq nnml-article-file-alist nil)
28096 (nnmail-get-new-mail 'nnml 'nnml-save-nov nnml-directory group))
28099 It simply calls @code{nnmail-get-new-mail} with a few parameters,
28100 and @code{nnmail} takes care of all the moving and splitting of the
28103 This function takes four parameters.
28107 This should be a symbol to designate which back end is responsible for
28110 @item exit-function
28111 This function should be called after the splitting has been performed.
28113 @item temp-directory
28114 Where the temporary files should be stored.
28117 This optional argument should be a group name if the splitting is to be
28118 performed for one group only.
28121 @code{nnmail-get-new-mail} will call @var{back-end}@code{-save-mail} to
28122 save each article. @var{back-end}@code{-active-number} will be called to
28123 find the article number assigned to this article.
28125 The function also uses the following variables:
28126 @var{back-end}@code{-get-new-mail} (to see whether to get new mail for
28127 this back end); and @var{back-end}@code{-group-alist} and
28128 @var{back-end}@code{-active-file} to generate the new active file.
28129 @var{back-end}@code{-group-alist} should be a group-active alist, like
28133 (("a-group" (1 . 10))
28134 ("some-group" (34 . 39)))
28138 @node Score File Syntax
28139 @subsection Score File Syntax
28141 Score files are meant to be easily parseable, but yet extremely
28142 mallable. It was decided that something that had the same read syntax
28143 as an Emacs Lisp list would fit that spec.
28145 Here's a typical score file:
28149 ("win95" -10000 nil s)
28156 BNF definition of a score file:
28159 score-file = "" / "(" *element ")"
28160 element = rule / atom
28161 rule = string-rule / number-rule / date-rule
28162 string-rule = "(" quote string-header quote space *string-match ")"
28163 number-rule = "(" quote number-header quote space *number-match ")"
28164 date-rule = "(" quote date-header quote space *date-match ")"
28166 string-header = "subject" / "from" / "references" / "message-id" /
28167 "xref" / "body" / "head" / "all" / "followup"
28168 number-header = "lines" / "chars"
28169 date-header = "date"
28170 string-match = "(" quote <string> quote [ "" / [ space score [ "" /
28171 space date [ "" / [ space string-match-t ] ] ] ] ] ")"
28172 score = "nil" / <integer>
28173 date = "nil" / <natural number>
28174 string-match-t = "nil" / "s" / "substring" / "S" / "Substring" /
28175 "r" / "regex" / "R" / "Regex" /
28176 "e" / "exact" / "E" / "Exact" /
28177 "f" / "fuzzy" / "F" / "Fuzzy"
28178 number-match = "(" <integer> [ "" / [ space score [ "" /
28179 space date [ "" / [ space number-match-t ] ] ] ] ] ")"
28180 number-match-t = "nil" / "=" / "<" / ">" / ">=" / "<="
28181 date-match = "(" quote <string> quote [ "" / [ space score [ "" /
28182 space date [ "" / [ space date-match-t ] ] ] ] ")"
28183 date-match-t = "nil" / "at" / "before" / "after"
28184 atom = "(" [ required-atom / optional-atom ] ")"
28185 required-atom = mark / expunge / mark-and-expunge / files /
28186 exclude-files / read-only / touched
28187 optional-atom = adapt / local / eval
28188 mark = "mark" space nil-or-number
28189 nil-or-number = "nil" / <integer>
28190 expunge = "expunge" space nil-or-number
28191 mark-and-expunge = "mark-and-expunge" space nil-or-number
28192 files = "files" *[ space <string> ]
28193 exclude-files = "exclude-files" *[ space <string> ]
28194 read-only = "read-only" [ space "nil" / space "t" ]
28195 adapt = "adapt" [ space "ignore" / space "t" / space adapt-rule ]
28196 adapt-rule = "(" *[ <string> *[ "(" <string> <integer> ")" ] ")"
28197 local = "local" *[ space "(" <string> space <form> ")" ]
28198 eval = "eval" space <form>
28199 space = *[ " " / <TAB> / <NEWLINE> ]
28202 Any unrecognized elements in a score file should be ignored, but not
28205 As you can see, white space is needed, but the type and amount of white
28206 space is irrelevant. This means that formatting of the score file is
28207 left up to the programmer---if it's simpler to just spew it all out on
28208 one looong line, then that's ok.
28210 The meaning of the various atoms are explained elsewhere in this
28211 manual (@pxref{Score File Format}).
28215 @subsection Headers
28217 Internally Gnus uses a format for storing article headers that
28218 corresponds to the @acronym{NOV} format in a mysterious fashion. One could
28219 almost suspect that the author looked at the @acronym{NOV} specification and
28220 just shamelessly @emph{stole} the entire thing, and one would be right.
28222 @dfn{Header} is a severely overloaded term. ``Header'' is used in
28223 RFC 1036 to talk about lines in the head of an article (e.g.,
28224 @code{From}). It is used by many people as a synonym for
28225 ``head''---``the header and the body''. (That should be avoided, in my
28226 opinion.) And Gnus uses a format internally that it calls ``header'',
28227 which is what I'm talking about here. This is a 9-element vector,
28228 basically, with each header (ouch) having one slot.
28230 These slots are, in order: @code{number}, @code{subject}, @code{from},
28231 @code{date}, @code{id}, @code{references}, @code{chars}, @code{lines},
28232 @code{xref}, and @code{extra}. There are macros for accessing and
28233 setting these slots---they all have predictable names beginning with
28234 @code{mail-header-} and @code{mail-header-set-}, respectively.
28236 All these slots contain strings, except the @code{extra} slot, which
28237 contains an alist of header/value pairs (@pxref{To From Newsgroups}).
28243 @sc{gnus} introduced a concept that I found so useful that I've started
28244 using it a lot and have elaborated on it greatly.
28246 The question is simple: If you have a large amount of objects that are
28247 identified by numbers (say, articles, to take a @emph{wild} example)
28248 that you want to qualify as being ``included'', a normal sequence isn't
28249 very useful. (A 200,000 length sequence is a bit long-winded.)
28251 The solution is as simple as the question: You just collapse the
28255 (1 2 3 4 5 6 10 11 12)
28258 is transformed into
28261 ((1 . 6) (10 . 12))
28264 To avoid having those nasty @samp{(13 . 13)} elements to denote a
28265 lonesome object, a @samp{13} is a valid element:
28268 ((1 . 6) 7 (10 . 12))
28271 This means that comparing two ranges to find out whether they are equal
28272 is slightly tricky:
28275 ((1 . 5) 7 8 (10 . 12))
28281 ((1 . 5) (7 . 8) (10 . 12))
28284 are equal. In fact, any non-descending list is a range:
28290 is a perfectly valid range, although a pretty long-winded one. This is
28297 and is equal to the previous range.
28299 Here's a BNF definition of ranges. Of course, one must remember the
28300 semantic requirement that the numbers are non-descending. (Any number
28301 of repetition of the same number is allowed, but apt to disappear in
28305 range = simple-range / normal-range
28306 simple-range = "(" number " . " number ")"
28307 normal-range = "(" start-contents ")"
28308 contents = "" / simple-range *[ " " contents ] /
28309 number *[ " " contents ]
28312 Gnus currently uses ranges to keep track of read articles and article
28313 marks. I plan on implementing a number of range operators in C if The
28314 Powers That Be are willing to let me. (I haven't asked yet, because I
28315 need to do some more thinking on what operators I need to make life
28316 totally range-based without ever having to convert back to normal
28321 @subsection Group Info
28323 Gnus stores all permanent info on groups in a @dfn{group info} list.
28324 This list is from three to six elements (or more) long and exhaustively
28325 describes the group.
28327 Here are two example group infos; one is a very simple group while the
28328 second is a more complex one:
28331 ("no.group" 5 ((1 . 54324)))
28333 ("nnml:my.mail" 3 ((1 . 5) 9 (20 . 55))
28334 ((tick (15 . 19)) (replied 3 6 (19 . 3)))
28336 ((auto-expire . t) (to-address . "ding@@gnus.org")))
28339 The first element is the @dfn{group name}---as Gnus knows the group,
28340 anyway. The second element is the @dfn{subscription level}, which
28341 normally is a small integer. (It can also be the @dfn{rank}, which is a
28342 cons cell where the @code{car} is the level and the @code{cdr} is the
28343 score.) The third element is a list of ranges of read articles. The
28344 fourth element is a list of lists of article marks of various kinds.
28345 The fifth element is the select method (or virtual server, if you like).
28346 The sixth element is a list of @dfn{group parameters}, which is what
28347 this section is about.
28349 Any of the last three elements may be missing if they are not required.
28350 In fact, the vast majority of groups will normally only have the first
28351 three elements, which saves quite a lot of cons cells.
28353 Here's a BNF definition of the group info format:
28356 info = "(" group space ralevel space read
28357 [ "" / [ space marks-list [ "" / [ space method [ "" /
28358 space parameters ] ] ] ] ] ")"
28359 group = quote <string> quote
28360 ralevel = rank / level
28361 level = <integer in the range of 1 to inf>
28362 rank = "(" level "." score ")"
28363 score = <integer in the range of 1 to inf>
28365 marks-lists = nil / "(" *marks ")"
28366 marks = "(" <string> range ")"
28367 method = "(" <string> *elisp-forms ")"
28368 parameters = "(" *elisp-forms ")"
28371 Actually that @samp{marks} rule is a fib. A @samp{marks} is a
28372 @samp{<string>} consed on to a @samp{range}, but that's a bitch to say
28375 If you have a Gnus info and want to access the elements, Gnus offers a
28376 series of macros for getting/setting these elements.
28379 @item gnus-info-group
28380 @itemx gnus-info-set-group
28381 @findex gnus-info-group
28382 @findex gnus-info-set-group
28383 Get/set the group name.
28385 @item gnus-info-rank
28386 @itemx gnus-info-set-rank
28387 @findex gnus-info-rank
28388 @findex gnus-info-set-rank
28389 Get/set the group rank (@pxref{Group Score}).
28391 @item gnus-info-level
28392 @itemx gnus-info-set-level
28393 @findex gnus-info-level
28394 @findex gnus-info-set-level
28395 Get/set the group level.
28397 @item gnus-info-score
28398 @itemx gnus-info-set-score
28399 @findex gnus-info-score
28400 @findex gnus-info-set-score
28401 Get/set the group score (@pxref{Group Score}).
28403 @item gnus-info-read
28404 @itemx gnus-info-set-read
28405 @findex gnus-info-read
28406 @findex gnus-info-set-read
28407 Get/set the ranges of read articles.
28409 @item gnus-info-marks
28410 @itemx gnus-info-set-marks
28411 @findex gnus-info-marks
28412 @findex gnus-info-set-marks
28413 Get/set the lists of ranges of marked articles.
28415 @item gnus-info-method
28416 @itemx gnus-info-set-method
28417 @findex gnus-info-method
28418 @findex gnus-info-set-method
28419 Get/set the group select method.
28421 @item gnus-info-params
28422 @itemx gnus-info-set-params
28423 @findex gnus-info-params
28424 @findex gnus-info-set-params
28425 Get/set the group parameters.
28428 All the getter functions take one parameter---the info list. The setter
28429 functions take two parameters---the info list and the new value.
28431 The last three elements in the group info aren't mandatory, so it may be
28432 necessary to extend the group info before setting the element. If this
28433 is necessary, you can just pass on a non-@code{nil} third parameter to
28434 the three final setter functions to have this happen automatically.
28437 @node Extended Interactive
28438 @subsection Extended Interactive
28439 @cindex interactive
28440 @findex gnus-interactive
28442 Gnus extends the standard Emacs @code{interactive} specification
28443 slightly to allow easy use of the symbolic prefix (@pxref{Symbolic
28444 Prefixes}). Here's an example of how this is used:
28447 (defun gnus-summary-increase-score (&optional score symp)
28448 (interactive (gnus-interactive "P\ny"))
28453 The best thing to do would have been to implement
28454 @code{gnus-interactive} as a macro which would have returned an
28455 @code{interactive} form, but this isn't possible since Emacs checks
28456 whether a function is interactive or not by simply doing an @code{assq}
28457 on the lambda form. So, instead we have @code{gnus-interactive}
28458 function that takes a string and returns values that are usable to
28459 @code{interactive}.
28461 This function accepts (almost) all normal @code{interactive} specs, but
28466 @vindex gnus-current-prefix-symbol
28467 The current symbolic prefix---the @code{gnus-current-prefix-symbol}
28471 @vindex gnus-current-prefix-symbols
28472 A list of the current symbolic prefixes---the
28473 @code{gnus-current-prefix-symbol} variable.
28476 The current article number---the @code{gnus-summary-article-number}
28480 The current article header---the @code{gnus-summary-article-header}
28484 The current group name---the @code{gnus-group-group-name}
28490 @node Emacs/XEmacs Code
28491 @subsection Emacs/XEmacs Code
28495 While Gnus runs under Emacs, XEmacs and Mule, I decided that one of the
28496 platforms must be the primary one. I chose Emacs. Not because I don't
28497 like XEmacs or Mule, but because it comes first alphabetically.
28499 This means that Gnus will byte-compile under Emacs with nary a warning,
28500 while XEmacs will pump out gigabytes of warnings while byte-compiling.
28501 As I use byte-compilation warnings to help me root out trivial errors in
28502 Gnus, that's very useful.
28504 I've also consistently used Emacs function interfaces, but have used
28505 Gnusey aliases for the functions. To take an example: Emacs defines a
28506 @code{run-at-time} function while XEmacs defines a @code{start-itimer}
28507 function. I then define a function called @code{gnus-run-at-time} that
28508 takes the same parameters as the Emacs @code{run-at-time}. When running
28509 Gnus under Emacs, the former function is just an alias for the latter.
28510 However, when running under XEmacs, the former is an alias for the
28511 following function:
28514 (defun gnus-xmas-run-at-time (time repeat function &rest args)
28518 (,function ,@@args))
28522 This sort of thing has been done for bunches of functions. Gnus does
28523 not redefine any native Emacs functions while running under XEmacs---it
28524 does this @code{defalias} thing with Gnus equivalents instead. Cleaner
28527 In the cases where the XEmacs function interface was obviously cleaner,
28528 I used it instead. For example @code{gnus-region-active-p} is an alias
28529 for @code{region-active-p} in XEmacs, whereas in Emacs it is a function.
28531 Of course, I could have chosen XEmacs as my native platform and done
28532 mapping functions the other way around. But I didn't. The performance
28533 hit these indirections impose on Gnus under XEmacs should be slight.
28536 @node Various File Formats
28537 @subsection Various File Formats
28540 * Active File Format:: Information on articles and groups available.
28541 * Newsgroups File Format:: Group descriptions.
28545 @node Active File Format
28546 @subsubsection Active File Format
28548 The active file lists all groups available on the server in
28549 question. It also lists the highest and lowest current article numbers
28552 Here's an excerpt from a typical active file:
28555 soc.motss 296030 293865 y
28556 alt.binaries.pictures.fractals 3922 3913 n
28557 comp.sources.unix 1605 1593 m
28558 comp.binaries.ibm.pc 5097 5089 y
28559 no.general 1000 900 y
28562 Here's a pseudo-BNF definition of this file:
28565 active = *group-line
28566 group-line = group spc high-number spc low-number spc flag <NEWLINE>
28567 group = <non-white-space string>
28569 high-number = <non-negative integer>
28570 low-number = <positive integer>
28571 flag = "y" / "n" / "m" / "j" / "x" / "=" group
28574 For a full description of this file, see the manual pages for
28575 @samp{innd}, in particular @samp{active(5)}.
28578 @node Newsgroups File Format
28579 @subsubsection Newsgroups File Format
28581 The newsgroups file lists groups along with their descriptions. Not all
28582 groups on the server have to be listed, and not all groups in the file
28583 have to exist on the server. The file is meant purely as information to
28586 The format is quite simple; a group name, a tab, and the description.
28587 Here's the definition:
28591 line = group tab description <NEWLINE>
28592 group = <non-white-space string>
28594 description = <string>
28599 @node Emacs for Heathens
28600 @section Emacs for Heathens
28602 Believe it or not, but some people who use Gnus haven't really used
28603 Emacs much before they embarked on their journey on the Gnus Love Boat.
28604 If you are one of those unfortunates whom ``@kbd{C-M-a}'', ``kill the
28605 region'', and ``set @code{gnus-flargblossen} to an alist where the key
28606 is a regexp that is used for matching on the group name'' are magical
28607 phrases with little or no meaning, then this appendix is for you. If
28608 you are already familiar with Emacs, just ignore this and go fondle your
28612 * Keystrokes:: Entering text and executing commands.
28613 * Emacs Lisp:: The built-in Emacs programming language.
28618 @subsection Keystrokes
28622 Q: What is an experienced Emacs user?
28625 A: A person who wishes that the terminal had pedals.
28628 Yes, when you use Emacs, you are apt to use the control key, the shift
28629 key and the meta key a lot. This is very annoying to some people
28630 (notably @code{vi}le users), and the rest of us just love the hell out
28631 of it. Just give up and submit. Emacs really does stand for
28632 ``Escape-Meta-Alt-Control-Shift'', and not ``Editing Macros'', as you
28633 may have heard from other disreputable sources (like the Emacs author).
28635 The shift keys are normally located near your pinky fingers, and are
28636 normally used to get capital letters and stuff. You probably use it all
28637 the time. The control key is normally marked ``CTRL'' or something like
28638 that. The meta key is, funnily enough, never marked as such on any
28639 keyboard. The one I'm currently at has a key that's marked ``Alt'',
28640 which is the meta key on this keyboard. It's usually located somewhere
28641 to the left hand side of the keyboard, usually on the bottom row.
28643 Now, us Emacs people don't say ``press the meta-control-m key'',
28644 because that's just too inconvenient. We say ``press the @kbd{C-M-m}
28645 key''. @kbd{M-} is the prefix that means ``meta'' and ``C-'' is the
28646 prefix that means ``control''. So ``press @kbd{C-k}'' means ``press
28647 down the control key, and hold it down while you press @kbd{k}''.
28648 ``Press @kbd{C-M-k}'' means ``press down and hold down the meta key and
28649 the control key and then press @kbd{k}''. Simple, ay?
28651 This is somewhat complicated by the fact that not all keyboards have a
28652 meta key. In that case you can use the ``escape'' key. Then @kbd{M-k}
28653 means ``press escape, release escape, press @kbd{k}''. That's much more
28654 work than if you have a meta key, so if that's the case, I respectfully
28655 suggest you get a real keyboard with a meta key. You can't live without
28661 @subsection Emacs Lisp
28663 Emacs is the King of Editors because it's really a Lisp interpreter.
28664 Each and every key you tap runs some Emacs Lisp code snippet, and since
28665 Emacs Lisp is an interpreted language, that means that you can configure
28666 any key to run any arbitrary code. You just, like, do it.
28668 Gnus is written in Emacs Lisp, and is run as a bunch of interpreted
28669 functions. (These are byte-compiled for speed, but it's still
28670 interpreted.) If you decide that you don't like the way Gnus does
28671 certain things, it's trivial to have it do something a different way.
28672 (Well, at least if you know how to write Lisp code.) However, that's
28673 beyond the scope of this manual, so we are simply going to talk about
28674 some common constructs that you normally use in your @file{.emacs} file
28677 If you want to set the variable @code{gnus-florgbnize} to four (4), you
28678 write the following:
28681 (setq gnus-florgbnize 4)
28684 This function (really ``special form'') @code{setq} is the one that can
28685 set a variable to some value. This is really all you need to know. Now
28686 you can go and fill your @file{.emacs} file with lots of these to change
28689 If you have put that thing in your @file{.emacs} file, it will be read
28690 and @code{eval}ed (which is lisp-ese for ``run'') the next time you
28691 start Emacs. If you want to change the variable right away, simply say
28692 @kbd{C-x C-e} after the closing parenthesis. That will @code{eval} the
28693 previous ``form'', which is a simple @code{setq} statement here.
28695 Go ahead---just try it, if you're located at your Emacs. After you
28696 @kbd{C-x C-e}, you will see @samp{4} appear in the echo area, which
28697 is the return value of the form you @code{eval}ed.
28701 If the manual says ``set @code{gnus-read-active-file} to @code{some}'',
28705 (setq gnus-read-active-file 'some)
28708 On the other hand, if the manual says ``set @code{gnus-nntp-server} to
28709 @samp{nntp.ifi.uio.no}'', that means:
28712 (setq gnus-nntp-server "nntp.ifi.uio.no")
28715 So be careful not to mix up strings (the latter) with symbols (the
28716 former). The manual is unambiguous, but it can be confusing.
28719 @include gnus-faq.texi
28739 @c Local Variables:
28741 @c coding: iso-8859-1