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}{No Gnus v0.3}
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
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 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 This manual corresponds to No Gnus v0.3.
375 Gnus is the advanced, self-documenting, customizable, extensible
376 unreal-time newsreader for GNU Emacs.
378 Oops. That sounds oddly familiar, so let's start over again to avoid
379 being accused of plagiarism:
381 Gnus is a message-reading laboratory. It will let you look at just
382 about anything as if it were a newsgroup. You can read mail with it,
383 you can browse directories with it, you can @code{ftp} with it---you
384 can even read news with it!
386 Gnus tries to empower people who read news the same way Emacs empowers
387 people who edit text. Gnus sets no limits to what the user should be
388 allowed to do. Users are encouraged to extend Gnus to make it behave
389 like they want it to behave. A program should not control people;
390 people should be empowered to do what they want by using (or abusing)
396 * Starting Up:: Finding news can be a pain.
397 * Group Buffer:: Selecting, subscribing and killing groups.
398 * Summary Buffer:: Reading, saving and posting articles.
399 * Article Buffer:: Displaying and handling articles.
400 * Composing Messages:: Information on sending mail and news.
401 * Select Methods:: Gnus reads all messages from various select methods.
402 * Scoring:: Assigning values to articles.
403 * Various:: General purpose settings.
404 * The End:: Farewell and goodbye.
405 * Appendices:: Terminology, Emacs intro, @acronym{FAQ}, History, Internals.
406 * Index:: Variable, function and concept index.
407 * Key Index:: Key Index.
409 Other related manuals
411 * Message:(message). Composing messages.
412 * Emacs-MIME:(emacs-mime). Composing messages; @acronym{MIME}-specific parts.
413 * Sieve:(sieve). Managing Sieve scripts in Emacs.
414 * PGG:(pgg). @acronym{PGP/MIME} with Gnus.
415 * SASL:(sasl). @acronym{SASL} authentication in Emacs.
418 --- The Detailed Node Listing ---
422 * Finding the News:: Choosing a method for getting news.
423 * The First Time:: What does Gnus do the first time you start it?
424 * The Server is Down:: How can I read my mail then?
425 * Slave Gnusae:: You can have more than one Gnus active at a time.
426 * Fetching a Group:: Starting Gnus just to read a group.
427 * New Groups:: What is Gnus supposed to do with new groups?
428 * Changing Servers:: You may want to move from one server to another.
429 * Startup Files:: Those pesky startup files---@file{.newsrc}.
430 * Auto Save:: Recovering from a crash.
431 * The Active File:: Reading the active file over a slow line Takes Time.
432 * Startup Variables:: Other variables you might change.
436 * Checking New Groups:: Determining what groups are new.
437 * Subscription Methods:: What Gnus should do with new groups.
438 * Filtering New Groups:: Making Gnus ignore certain new groups.
442 * Group Buffer Format:: Information listed and how you can change it.
443 * Group Maneuvering:: Commands for moving in the group buffer.
444 * Selecting a Group:: Actually reading news.
445 * Subscription Commands:: Unsubscribing, killing, subscribing.
446 * Group Data:: Changing the info for a group.
447 * Group Levels:: Levels? What are those, then?
448 * Group Score:: A mechanism for finding out what groups you like.
449 * Marking Groups:: You can mark groups for later processing.
450 * Foreign Groups:: Creating and editing groups.
451 * Group Parameters:: Each group may have different parameters set.
452 * Listing Groups:: Gnus can list various subsets of the groups.
453 * Sorting Groups:: Re-arrange the group order.
454 * Group Maintenance:: Maintaining a tidy @file{.newsrc} file.
455 * Browse Foreign Server:: You can browse a server. See what it has to offer.
456 * Exiting Gnus:: Stop reading news and get some work done.
457 * Group Topics:: A folding group mode divided into topics.
458 * Misc Group Stuff:: Other stuff that you can to do.
462 * Group Line Specification:: Deciding how the group buffer is to look.
463 * Group Mode Line Specification:: The group buffer mode line.
464 * Group Highlighting:: Having nice colors in the group buffer.
468 * Topic Commands:: Interactive E-Z commands.
469 * Topic Variables:: How to customize the topics the Lisp Way.
470 * Topic Sorting:: Sorting each topic individually.
471 * Topic Topology:: A map of the world.
472 * Topic Parameters:: Parameters that apply to all groups in a topic.
476 * Scanning New Messages:: Asking Gnus to see whether new messages have arrived.
477 * Group Information:: Information and help on groups and Gnus.
478 * Group Timestamp:: Making Gnus keep track of when you last read a group.
479 * File Commands:: Reading and writing the Gnus files.
480 * Sieve Commands:: Managing Sieve scripts.
484 * Summary Buffer Format:: Deciding how the summary buffer is to look.
485 * Summary Maneuvering:: Moving around the summary buffer.
486 * Choosing Articles:: Reading articles.
487 * Paging the Article:: Scrolling the current article.
488 * Reply Followup and Post:: Posting articles.
489 * Delayed Articles:: Send articles at a later time.
490 * Marking Articles:: Marking articles as read, expirable, etc.
491 * Limiting:: You can limit the summary buffer.
492 * Threading:: How threads are made.
493 * Sorting the Summary Buffer:: How articles and threads are sorted.
494 * Asynchronous Fetching:: Gnus might be able to pre-fetch articles.
495 * Article Caching:: You may store articles in a cache.
496 * Persistent Articles:: Making articles expiry-resistant.
497 * Article Backlog:: Having already read articles hang around.
498 * Saving Articles:: Ways of customizing article saving.
499 * Decoding Articles:: Gnus can treat series of (uu)encoded articles.
500 * Article Treatment:: The article buffer can be mangled at will.
501 * MIME Commands:: Doing MIMEy things with the articles.
502 * Charsets:: Character set issues.
503 * Article Commands:: Doing various things with the article buffer.
504 * Summary Sorting:: Sorting the summary buffer in various ways.
505 * Finding the Parent:: No child support? Get the parent.
506 * Alternative Approaches:: Reading using non-default summaries.
507 * Tree Display:: A more visual display of threads.
508 * Mail Group Commands:: Some commands can only be used in mail groups.
509 * Various Summary Stuff:: What didn't fit anywhere else.
510 * Exiting the Summary Buffer:: Returning to the Group buffer,
511 or reselecting the current group.
512 * Crosspost Handling:: How crossposted articles are dealt with.
513 * Duplicate Suppression:: An alternative when crosspost handling fails.
514 * Security:: Decrypt and Verify.
515 * Mailing List:: Mailing list minor mode.
517 Summary Buffer Format
519 * Summary Buffer Lines:: You can specify how summary lines should look.
520 * To From Newsgroups:: How to not display your own name.
521 * Summary Buffer Mode Line:: You can say how the mode line should look.
522 * Summary Highlighting:: Making the summary buffer all pretty and nice.
526 * Choosing Commands:: Commands for choosing articles.
527 * Choosing Variables:: Variables that influence these commands.
529 Reply, Followup and Post
531 * Summary Mail Commands:: Sending mail.
532 * Summary Post Commands:: Sending news.
533 * Summary Message Commands:: Other Message-related commands.
534 * Canceling and Superseding::
538 * Unread Articles:: Marks for unread articles.
539 * Read Articles:: Marks for read articles.
540 * Other Marks:: Marks that do not affect readedness.
541 * Setting Marks:: How to set and remove marks.
542 * Generic Marking Commands:: How to customize the marking.
543 * Setting Process Marks:: How to mark articles for later processing.
547 * Customizing Threading:: Variables you can change to affect the threading.
548 * Thread Commands:: Thread based commands in the summary buffer.
550 Customizing Threading
552 * Loose Threads:: How Gnus gathers loose threads into bigger threads.
553 * Filling In Threads:: Making the threads displayed look fuller.
554 * More Threading:: Even more variables for fiddling with threads.
555 * Low-Level Threading:: You thought it was over@dots{} but you were wrong!
559 * Uuencoded Articles:: Uudecode articles.
560 * Shell Archives:: Unshar articles.
561 * PostScript Files:: Split PostScript.
562 * Other Files:: Plain save and binhex.
563 * Decoding Variables:: Variables for a happy decoding.
564 * Viewing Files:: You want to look at the result of the decoding?
568 * Rule Variables:: Variables that say how a file is to be viewed.
569 * Other Decode Variables:: Other decode variables.
570 * Uuencoding and Posting:: Variables for customizing uuencoding.
574 * Article Highlighting:: You want to make the article look like fruit salad.
575 * Article Fontisizing:: Making emphasized text look nice.
576 * Article Hiding:: You also want to make certain info go away.
577 * Article Washing:: Lots of way-neat functions to make life better.
578 * Article Header:: Doing various header transformations.
579 * Article Buttons:: Click on URLs, Message-IDs, addresses and the like.
580 * Article Button Levels:: Controlling appearance of buttons.
581 * Article Date:: Grumble, UT!
582 * Article Display:: Display various stuff---X-Face, Picons, Smileys
583 * Article Signature:: What is a signature?
584 * Article Miscellanea:: Various other stuff.
586 Alternative Approaches
588 * Pick and Read:: First mark articles and then read them.
589 * Binary Groups:: Auto-decode all articles.
591 Various Summary Stuff
593 * Summary Group Information:: Information oriented commands.
594 * Searching for Articles:: Multiple article commands.
595 * Summary Generation Commands::
596 * Really Various Summary Commands:: Those pesky non-conformant commands.
600 * Hiding Headers:: Deciding what headers should be displayed.
601 * Using MIME:: Pushing articles through @acronym{MIME} before reading them.
602 * Customizing Articles:: Tailoring the look of the articles.
603 * Article Keymap:: Keystrokes available in the article buffer.
604 * Misc Article:: Other stuff.
608 * Mail:: Mailing and replying.
609 * Posting Server:: What server should you post and mail via?
610 * POP before SMTP:: You cannot send a mail unless you read a mail.
611 * Mail and Post:: Mailing and posting at the same time.
612 * Archived Messages:: Where Gnus stores the messages you've sent.
613 * Posting Styles:: An easier way to specify who you are.
614 * Drafts:: Postponing messages and rejected messages.
615 * Rejected Articles:: What happens if the server doesn't like your article?
616 * Signing and encrypting:: How to compose secure messages.
620 * Server Buffer:: Making and editing virtual servers.
621 * Getting News:: Reading USENET news with Gnus.
622 * Getting Mail:: Reading your personal mail with Gnus.
623 * Browsing the Web:: Getting messages from a plethora of Web sources.
624 * IMAP:: Using Gnus as a @acronym{IMAP} client.
625 * Other Sources:: Reading directories, files, SOUP packets.
626 * Combined Groups:: Combining groups into one group.
627 * Email Based Diary:: Using mails to manage diary events in Gnus.
628 * Gnus Unplugged:: Reading news and mail offline.
632 * Server Buffer Format:: You can customize the look of this buffer.
633 * Server Commands:: Commands to manipulate servers.
634 * Example Methods:: Examples server specifications.
635 * Creating a Virtual Server:: An example session.
636 * Server Variables:: Which variables to set.
637 * Servers and Methods:: You can use server names as select methods.
638 * Unavailable Servers:: Some servers you try to contact may be down.
642 * NNTP:: Reading news from an @acronym{NNTP} server.
643 * News Spool:: Reading news from the local spool.
647 * Direct Functions:: Connecting directly to the server.
648 * Indirect Functions:: Connecting indirectly to the server.
649 * Common Variables:: Understood by several connection functions.
650 * NNTP marks:: Storing marks for @acronym{NNTP} servers.
654 * Mail in a Newsreader:: Important introductory notes.
655 * Getting Started Reading Mail:: A simple cookbook example.
656 * Splitting Mail:: How to create mail groups.
657 * Mail Sources:: How to tell Gnus where to get mail from.
658 * Mail Back End Variables:: Variables for customizing mail handling.
659 * Fancy Mail Splitting:: Gnus can do hairy splitting of incoming mail.
660 * Group Mail Splitting:: Use group customize to drive mail splitting.
661 * Incorporating Old Mail:: What about the old mail you have?
662 * Expiring Mail:: Getting rid of unwanted mail.
663 * Washing Mail:: Removing cruft from the mail you get.
664 * Duplicates:: Dealing with duplicated mail.
665 * Not Reading Mail:: Using mail back ends for reading other files.
666 * Choosing a Mail Back End:: Gnus can read a variety of mail formats.
670 * Mail Source Specifiers:: How to specify what a mail source is.
671 * Mail Source Customization:: Some variables that influence things.
672 * Fetching Mail:: Using the mail source specifiers.
674 Choosing a Mail Back End
676 * Unix Mail Box:: Using the (quite) standard Un*x mbox.
677 * Rmail Babyl:: Emacs programs use the Rmail Babyl format.
678 * Mail Spool:: Store your mail in a private spool?
679 * MH Spool:: An mhspool-like back end.
680 * Maildir:: Another one-file-per-message format.
681 * Mail Folders:: Having one file for each group.
682 * Comparing Mail Back Ends:: An in-depth looks at pros and cons.
687 * Web Searches:: Creating groups from articles that match a string.
688 * Slashdot:: Reading the Slashdot comments.
689 * Ultimate:: The Ultimate Bulletin Board systems.
690 * Web Archive:: Reading mailing list archived on web.
691 * RSS:: Reading RDF site summary.
692 * Customizing w3:: Doing stuff to Emacs/w3 from Gnus.
696 * Splitting in IMAP:: Splitting mail with nnimap.
697 * Expiring in IMAP:: Expiring mail with nnimap.
698 * Editing IMAP ACLs:: Limiting/enabling other users access to a mailbox.
699 * Expunging mailboxes:: Equivalent of a ``compress mailbox'' button.
700 * A note on namespaces:: How to (not) use @acronym{IMAP} namespace in Gnus.
701 * Debugging IMAP:: What to do when things don't work.
705 * Directory Groups:: You can read a directory as if it was a newsgroup.
706 * Anything Groups:: Dired? Who needs dired?
707 * Document Groups:: Single files can be the basis of a group.
708 * SOUP:: Reading @sc{soup} packets ``offline''.
709 * Mail-To-News Gateways:: Posting articles via mail-to-news gateways.
713 * Document Server Internals:: How to add your own document types.
717 * SOUP Commands:: Commands for creating and sending @sc{soup} packets
718 * SOUP Groups:: A back end for reading @sc{soup} packets.
719 * SOUP Replies:: How to enable @code{nnsoup} to take over mail and news.
723 * Virtual Groups:: Combining articles from many groups.
724 * Kibozed Groups:: Looking through parts of the newsfeed for articles.
728 * The NNDiary Back End:: Basic setup and usage.
729 * The Gnus Diary Library:: Utility toolkit on top of nndiary.
730 * Sending or Not Sending:: A final note on sending diary messages.
734 * Diary Messages:: What makes a message valid for nndiary.
735 * Running NNDiary:: NNDiary has two modes of operation.
736 * Customizing NNDiary:: Bells and whistles.
738 The Gnus Diary Library
740 * Diary Summary Line Format:: A nicer summary buffer line format.
741 * Diary Articles Sorting:: A nicer way to sort messages.
742 * Diary Headers Generation:: Not doing it manually.
743 * Diary Group Parameters:: Not handling them manually.
747 * Agent Basics:: How it all is supposed to work.
748 * Agent Categories:: How to tell the Gnus Agent what to download.
749 * Agent Commands:: New commands for all the buffers.
750 * Agent Visuals:: Ways that the agent may effect your summary buffer.
751 * Agent as Cache:: The Agent is a big cache too.
752 * Agent Expiry:: How to make old articles go away.
753 * Agent Regeneration:: How to recover from lost connections and other accidents.
754 * Agent and IMAP:: How to use the Agent with @acronym{IMAP}.
755 * Outgoing Messages:: What happens when you post/mail something?
756 * Agent Variables:: Customizing is fun.
757 * Example Setup:: An example @file{~/.gnus.el} file for offline people.
758 * Batching Agents:: How to fetch news from a @code{cron} job.
759 * Agent Caveats:: What you think it'll do and what it does.
763 * Category Syntax:: What a category looks like.
764 * Category Buffer:: A buffer for maintaining categories.
765 * Category Variables:: Customize'r'Us.
769 * Group Agent Commands:: Configure groups and fetch their contents.
770 * Summary Agent Commands:: Manually select then fetch specific articles.
771 * Server Agent Commands:: Select the servers that are supported by the agent.
775 * Summary Score Commands:: Adding score entries for the current group.
776 * Group Score Commands:: General score commands.
777 * Score Variables:: Customize your scoring. (My, what terminology).
778 * Score File Format:: What a score file may contain.
779 * Score File Editing:: You can edit score files by hand as well.
780 * Adaptive Scoring:: Big Sister Gnus knows what you read.
781 * Home Score File:: How to say where new score entries are to go.
782 * Followups To Yourself:: Having Gnus notice when people answer you.
783 * Scoring On Other Headers:: Scoring on non-standard headers.
784 * Scoring Tips:: How to score effectively.
785 * Reverse Scoring:: That problem child of old is not problem.
786 * Global Score Files:: Earth-spanning, ear-splitting score files.
787 * Kill Files:: They are still here, but they can be ignored.
788 * Converting Kill Files:: Translating kill files to score files.
789 * Advanced Scoring:: Using logical expressions to build score rules.
790 * Score Decays:: It can be useful to let scores wither away.
794 * Advanced Scoring Syntax:: A definition.
795 * Advanced Scoring Examples:: What they look like.
796 * Advanced Scoring Tips:: Getting the most out of it.
800 * Process/Prefix:: A convention used by many treatment commands.
801 * Interactive:: Making Gnus ask you many questions.
802 * Symbolic Prefixes:: How to supply some Gnus functions with options.
803 * Formatting Variables:: You can specify what buffers should look like.
804 * Window Layout:: Configuring the Gnus buffer windows.
805 * Faces and Fonts:: How to change how faces look.
806 * Compilation:: How to speed Gnus up.
807 * Mode Lines:: Displaying information in the mode lines.
808 * Highlighting and Menus:: Making buffers look all nice and cozy.
809 * Buttons:: Get tendinitis in ten easy steps!
810 * Daemons:: Gnus can do things behind your back.
811 * NoCeM:: How to avoid spam and other fatty foods.
812 * Undo:: Some actions can be undone.
813 * Predicate Specifiers:: Specifying predicates.
814 * Moderation:: What to do if you're a moderator.
815 * Image Enhancements:: Modern versions of Emacs/XEmacs can display images.
816 * Fuzzy Matching:: What's the big fuzz?
817 * Thwarting Email Spam:: A how-to on avoiding unsolicited commercial email.
818 * Other modes:: Interaction with other modes.
819 * Various Various:: Things that are really various.
823 * Formatting Basics:: A formatting variable is basically a format string.
824 * Mode Line Formatting:: Some rules about mode line formatting variables.
825 * Advanced Formatting:: Modifying output in various ways.
826 * User-Defined Specs:: Having Gnus call your own functions.
827 * Formatting Fonts:: Making the formatting look colorful and nice.
828 * Positioning Point:: Moving point to a position after an operation.
829 * Tabulation:: Tabulating your output.
830 * Wide Characters:: Dealing with wide characters.
834 * X-Face:: Display a funky, teensy black-and-white image.
835 * Face:: Display a funkier, teensier colored image.
836 * Smileys:: Show all those happy faces the way they were meant to be shown.
837 * Picons:: How to display pictures of what you're reading.
838 * XVarious:: Other XEmacsy Gnusey variables.
842 * The problem of spam:: Some background, and some solutions
843 * Anti-Spam Basics:: Simple steps to reduce the amount of spam.
844 * SpamAssassin:: How to use external anti-spam tools.
845 * Hashcash:: Reduce spam by burning CPU time.
846 * Filtering Spam Using The Spam ELisp Package::
847 * Filtering Spam Using Statistics with spam-stat::
849 Filtering Spam Using The Spam ELisp Package
851 * Spam ELisp Package Sequence of Events::
852 * Spam ELisp Package Filtering of Incoming Mail::
853 * Spam ELisp Package Global Variables::
854 * Spam ELisp Package Configuration Examples::
855 * Blacklists and Whitelists::
857 * Gmane Spam Reporting::
858 * Anti-spam Hashcash Payments::
860 * Regular Expressions Header Matching::
862 * SpamAssassin back end::
863 * ifile spam filtering::
864 * spam-stat spam filtering::
866 * Extending the Spam ELisp package::
868 Filtering Spam Using Statistics with spam-stat
870 * Creating a spam-stat dictionary::
871 * Splitting mail using spam-stat::
872 * Low-level interface to the spam-stat dictionary::
876 * XEmacs:: Requirements for installing under XEmacs.
877 * History:: How Gnus got where it is today.
878 * On Writing Manuals:: Why this is not a beginner's guide.
879 * Terminology:: We use really difficult, like, words here.
880 * Customization:: Tailoring Gnus to your needs.
881 * Troubleshooting:: What you might try if things do not work.
882 * Gnus Reference Guide:: Rilly, rilly technical stuff.
883 * Emacs for Heathens:: A short introduction to Emacsian terms.
884 * Frequently Asked Questions:: The Gnus FAQ
888 * Gnus Versions:: What Gnus versions have been released.
889 * Other Gnus Versions:: Other Gnus versions that also have been released.
890 * Why?:: What's the point of Gnus?
891 * Compatibility:: Just how compatible is Gnus with @sc{gnus}?
892 * Conformity:: Gnus tries to conform to all standards.
893 * Emacsen:: Gnus can be run on a few modern Emacsen.
894 * Gnus Development:: How Gnus is developed.
895 * Contributors:: Oodles of people.
896 * New Features:: Pointers to some of the new stuff in Gnus.
900 * ding Gnus:: New things in Gnus 5.0/5.1, the first new Gnus.
901 * September Gnus:: The Thing Formally Known As Gnus 5.2/5.3.
902 * Red Gnus:: Third time best---Gnus 5.4/5.5.
903 * Quassia Gnus:: Two times two is four, or Gnus 5.6/5.7.
904 * Pterodactyl Gnus:: Pentad also starts with P, AKA Gnus 5.8/5.9.
905 * Oort Gnus:: It's big. It's far out. Gnus 5.10/5.11.
906 * No Gnus:: Lars, FIXME!
910 * Slow/Expensive Connection:: You run a local Emacs and get the news elsewhere.
911 * Slow Terminal Connection:: You run a remote Emacs.
912 * Little Disk Space:: You feel that having large setup files is icky.
913 * Slow Machine:: You feel like buying a faster machine.
917 * Gnus Utility Functions:: Common functions and variable to use.
918 * Back End Interface:: How Gnus communicates with the servers.
919 * Score File Syntax:: A BNF definition of the score file standard.
920 * Headers:: How Gnus stores headers internally.
921 * Ranges:: A handy format for storing mucho numbers.
922 * Group Info:: The group info format.
923 * Extended Interactive:: Symbolic prefixes and stuff.
924 * Emacs/XEmacs Code:: Gnus can be run under all modern Emacsen.
925 * Various File Formats:: Formats of files that Gnus use.
929 * Required Back End Functions:: Functions that must be implemented.
930 * Optional Back End Functions:: Functions that need not be implemented.
931 * Error Messaging:: How to get messages and report errors.
932 * Writing New Back Ends:: Extending old back ends.
933 * Hooking New Back Ends Into Gnus:: What has to be done on the Gnus end.
934 * Mail-like Back Ends:: Some tips on mail back ends.
938 * Active File Format:: Information on articles and groups available.
939 * Newsgroups File Format:: Group descriptions.
943 * Keystrokes:: Entering text and executing commands.
944 * Emacs Lisp:: The built-in Emacs programming language.
950 @chapter Starting Gnus
955 If your system administrator has set things up properly, starting Gnus
956 and reading news is extremely easy---you just type @kbd{M-x gnus} in
959 @findex gnus-other-frame
960 @kindex M-x gnus-other-frame
961 If you want to start Gnus in a different frame, you can use the command
962 @kbd{M-x gnus-other-frame} instead.
964 If things do not go smoothly at startup, you have to twiddle some
965 variables in your @file{~/.gnus.el} file. This file is similar to
966 @file{~/.emacs}, but is read when Gnus starts.
968 If you puzzle at any terms used in this manual, please refer to the
969 terminology section (@pxref{Terminology}).
972 * Finding the News:: Choosing a method for getting news.
973 * The First Time:: What does Gnus do the first time you start it?
974 * The Server is Down:: How can I read my mail then?
975 * Slave Gnusae:: You can have more than one Gnus active at a time.
976 * New Groups:: What is Gnus supposed to do with new groups?
977 * Changing Servers:: You may want to move from one server to another.
978 * Startup Files:: Those pesky startup files---@file{.newsrc}.
979 * Auto Save:: Recovering from a crash.
980 * The Active File:: Reading the active file over a slow line Takes Time.
981 * Startup Variables:: Other variables you might change.
985 @node Finding the News
986 @section Finding the News
989 @vindex gnus-select-method
991 The @code{gnus-select-method} variable says where Gnus should look for
992 news. This variable should be a list where the first element says
993 @dfn{how} and the second element says @dfn{where}. This method is your
994 native method. All groups not fetched with this method are
997 For instance, if the @samp{news.somewhere.edu} @acronym{NNTP} server is where
998 you want to get your daily dosage of news from, you'd say:
1001 (setq gnus-select-method '(nntp "news.somewhere.edu"))
1004 If you want to read directly from the local spool, say:
1007 (setq gnus-select-method '(nnspool ""))
1010 If you can use a local spool, you probably should, as it will almost
1011 certainly be much faster. But do not use the local spool if your
1012 server is running Leafnode (which is a simple, standalone private news
1013 server); in this case, use @code{(nntp "localhost")}.
1015 @vindex gnus-nntpserver-file
1017 @cindex @acronym{NNTP} server
1018 If this variable is not set, Gnus will take a look at the
1019 @env{NNTPSERVER} environment variable. If that variable isn't set,
1020 Gnus will see whether @code{gnus-nntpserver-file}
1021 (@file{/etc/nntpserver} by default) has any opinions on the matter.
1022 If that fails as well, Gnus will try to use the machine running Emacs
1023 as an @acronym{NNTP} server. That's a long shot, though.
1025 @vindex gnus-nntp-server
1026 If @code{gnus-nntp-server} is set, this variable will override
1027 @code{gnus-select-method}. You should therefore set
1028 @code{gnus-nntp-server} to @code{nil}, which is what it is by default.
1030 @vindex gnus-secondary-servers
1031 @vindex gnus-nntp-server
1032 You can also make Gnus prompt you interactively for the name of an
1033 @acronym{NNTP} server. If you give a non-numerical prefix to @code{gnus}
1034 (i.e., @kbd{C-u M-x gnus}), Gnus will let you choose between the servers
1035 in the @code{gnus-secondary-servers} list (if any). You can also just
1036 type in the name of any server you feel like visiting. (Note that this
1037 will set @code{gnus-nntp-server}, which means that if you then @kbd{M-x
1038 gnus} later in the same Emacs session, Gnus will contact the same
1041 @findex gnus-group-browse-foreign-server
1043 However, if you use one @acronym{NNTP} server regularly and are just
1044 interested in a couple of groups from a different server, you would be
1045 better served by using the @kbd{B} command in the group buffer. It will
1046 let you have a look at what groups are available, and you can subscribe
1047 to any of the groups you want to. This also makes @file{.newsrc}
1048 maintenance much tidier. @xref{Foreign Groups}.
1050 @vindex gnus-secondary-select-methods
1052 A slightly different approach to foreign groups is to set the
1053 @code{gnus-secondary-select-methods} variable. The select methods
1054 listed in this variable are in many ways just as native as the
1055 @code{gnus-select-method} server. They will also be queried for active
1056 files during startup (if that's required), and new newsgroups that
1057 appear on these servers will be subscribed (or not) just as native
1060 For instance, if you use the @code{nnmbox} back end to read your mail,
1061 you would typically set this variable to
1064 (setq gnus-secondary-select-methods '((nnmbox "")))
1067 Note: the @acronym{NNTP} back end stores marks in marks files
1068 (@pxref{NNTP marks}). This feature makes it easy to share marks between
1069 several Gnus installations, but may slow down things a bit when fetching
1070 new articles. @xref{NNTP marks}, for more information.
1073 @node The First Time
1074 @section The First Time
1075 @cindex first time usage
1077 If no startup files exist (@pxref{Startup Files}), Gnus will try to
1078 determine what groups should be subscribed by default.
1080 @vindex gnus-default-subscribed-newsgroups
1081 If the variable @code{gnus-default-subscribed-newsgroups} is set, Gnus
1082 will subscribe you to just those groups in that list, leaving the rest
1083 killed. Your system administrator should have set this variable to
1086 Since she hasn't, Gnus will just subscribe you to a few arbitrarily
1087 picked groups (i.e., @samp{*.newusers}). (@dfn{Arbitrary} is defined
1088 here as @dfn{whatever Lars thinks you should read}.)
1090 You'll also be subscribed to the Gnus documentation group, which should
1091 help you with most common problems.
1093 If @code{gnus-default-subscribed-newsgroups} is @code{t}, Gnus will just
1094 use the normal functions for handling new groups, and not do anything
1098 @node The Server is Down
1099 @section The Server is Down
1100 @cindex server errors
1102 If the default server is down, Gnus will understandably have some
1103 problems starting. However, if you have some mail groups in addition to
1104 the news groups, you may want to start Gnus anyway.
1106 Gnus, being the trusting sort of program, will ask whether to proceed
1107 without a native select method if that server can't be contacted. This
1108 will happen whether the server doesn't actually exist (i.e., you have
1109 given the wrong address) or the server has just momentarily taken ill
1110 for some reason or other. If you decide to continue and have no foreign
1111 groups, you'll find it difficult to actually do anything in the group
1112 buffer. But, hey, that's your problem. Blllrph!
1114 @findex gnus-no-server
1115 @kindex M-x gnus-no-server
1117 If you know that the server is definitely down, or you just want to read
1118 your mail without bothering with the server at all, you can use the
1119 @code{gnus-no-server} command to start Gnus. That might come in handy
1120 if you're in a hurry as well. This command will not attempt to contact
1121 your primary server---instead, it will just activate all groups on level
1122 1 and 2. (You should preferably keep no native groups on those two
1123 levels.) Also @pxref{Group Levels}.
1127 @section Slave Gnusae
1130 You might want to run more than one Emacs with more than one Gnus at the
1131 same time. If you are using different @file{.newsrc} files (e.g., if you
1132 are using the two different Gnusae to read from two different servers),
1133 that is no problem whatsoever. You just do it.
1135 The problem appears when you want to run two Gnusae that use the same
1136 @file{.newsrc} file.
1138 To work around that problem some, we here at the Think-Tank at the Gnus
1139 Towers have come up with a new concept: @dfn{Masters} and
1140 @dfn{slaves}. (We have applied for a patent on this concept, and have
1141 taken out a copyright on those words. If you wish to use those words in
1142 conjunction with each other, you have to send $1 per usage instance to
1143 me. Usage of the patent (@dfn{Master/Slave Relationships In Computer
1144 Applications}) will be much more expensive, of course.)
1147 Anyway, you start one Gnus up the normal way with @kbd{M-x gnus} (or
1148 however you do it). Each subsequent slave Gnusae should be started with
1149 @kbd{M-x gnus-slave}. These slaves won't save normal @file{.newsrc}
1150 files, but instead save @dfn{slave files} that contain information only
1151 on what groups have been read in the slave session. When a master Gnus
1152 starts, it will read (and delete) these slave files, incorporating all
1153 information from them. (The slave files will be read in the sequence
1154 they were created, so the latest changes will have precedence.)
1156 Information from the slave files has, of course, precedence over the
1157 information in the normal (i.e., master) @file{.newsrc} file.
1159 If the @file{.newsrc*} files have not been saved in the master when the
1160 slave starts, you may be prompted as to whether to read an auto-save
1161 file. If you answer ``yes'', the unsaved changes to the master will be
1162 incorporated into the slave. If you answer ``no'', the slave may see some
1163 messages as unread that have been read in the master.
1170 @cindex subscription
1172 @vindex gnus-check-new-newsgroups
1173 If you are satisfied that you really never want to see any new groups,
1174 you can set @code{gnus-check-new-newsgroups} to @code{nil}. This will
1175 also save you some time at startup. Even if this variable is
1176 @code{nil}, you can always subscribe to the new groups just by pressing
1177 @kbd{U} in the group buffer (@pxref{Group Maintenance}). This variable
1178 is @code{ask-server} by default. If you set this variable to
1179 @code{always}, then Gnus will query the back ends for new groups even
1180 when you do the @kbd{g} command (@pxref{Scanning New Messages}).
1183 * Checking New Groups:: Determining what groups are new.
1184 * Subscription Methods:: What Gnus should do with new groups.
1185 * Filtering New Groups:: Making Gnus ignore certain new groups.
1189 @node Checking New Groups
1190 @subsection Checking New Groups
1192 Gnus normally determines whether a group is new or not by comparing the
1193 list of groups from the active file(s) with the lists of subscribed and
1194 dead groups. This isn't a particularly fast method. If
1195 @code{gnus-check-new-newsgroups} is @code{ask-server}, Gnus will ask the
1196 server for new groups since the last time. This is both faster and
1197 cheaper. This also means that you can get rid of the list of killed
1198 groups altogether, so you may set @code{gnus-save-killed-list} to
1199 @code{nil}, which will save time both at startup, at exit, and all over.
1200 Saves disk space, too. Why isn't this the default, then?
1201 Unfortunately, not all servers support this command.
1203 I bet I know what you're thinking now: How do I find out whether my
1204 server supports @code{ask-server}? No? Good, because I don't have a
1205 fail-safe answer. I would suggest just setting this variable to
1206 @code{ask-server} and see whether any new groups appear within the next
1207 few days. If any do, then it works. If none do, then it doesn't
1208 work. I could write a function to make Gnus guess whether the server
1209 supports @code{ask-server}, but it would just be a guess. So I won't.
1210 You could @code{telnet} to the server and say @code{HELP} and see
1211 whether it lists @samp{NEWGROUPS} among the commands it understands. If
1212 it does, then it might work. (But there are servers that lists
1213 @samp{NEWGROUPS} without supporting the function properly.)
1215 This variable can also be a list of select methods. If so, Gnus will
1216 issue an @code{ask-server} command to each of the select methods, and
1217 subscribe them (or not) using the normal methods. This might be handy
1218 if you are monitoring a few servers for new groups. A side effect is
1219 that startup will take much longer, so you can meditate while waiting.
1220 Use the mantra ``dingnusdingnusdingnus'' to achieve permanent bliss.
1223 @node Subscription Methods
1224 @subsection Subscription Methods
1226 @vindex gnus-subscribe-newsgroup-method
1227 What Gnus does when it encounters a new group is determined by the
1228 @code{gnus-subscribe-newsgroup-method} variable.
1230 This variable should contain a function. This function will be called
1231 with the name of the new group as the only parameter.
1233 Some handy pre-fab functions are:
1237 @item gnus-subscribe-zombies
1238 @vindex gnus-subscribe-zombies
1239 Make all new groups zombies. This is the default. You can browse the
1240 zombies later (with @kbd{A z}) and either kill them all off properly
1241 (with @kbd{S z}), or subscribe to them (with @kbd{u}).
1243 @item gnus-subscribe-randomly
1244 @vindex gnus-subscribe-randomly
1245 Subscribe all new groups in arbitrary order. This really means that all
1246 new groups will be added at ``the top'' of the group buffer.
1248 @item gnus-subscribe-alphabetically
1249 @vindex gnus-subscribe-alphabetically
1250 Subscribe all new groups in alphabetical order.
1252 @item gnus-subscribe-hierarchically
1253 @vindex gnus-subscribe-hierarchically
1254 Subscribe all new groups hierarchically. The difference between this
1255 function and @code{gnus-subscribe-alphabetically} is slight.
1256 @code{gnus-subscribe-alphabetically} will subscribe new groups in a strictly
1257 alphabetical fashion, while this function will enter groups into its
1258 hierarchy. So if you want to have the @samp{rec} hierarchy before the
1259 @samp{comp} hierarchy, this function will not mess that configuration
1260 up. Or something like that.
1262 @item gnus-subscribe-interactively
1263 @vindex gnus-subscribe-interactively
1264 Subscribe new groups interactively. This means that Gnus will ask
1265 you about @strong{all} new groups. The groups you choose to subscribe
1266 to will be subscribed hierarchically.
1268 @item gnus-subscribe-killed
1269 @vindex gnus-subscribe-killed
1270 Kill all new groups.
1272 @item gnus-subscribe-topics
1273 @vindex gnus-subscribe-topics
1274 Put the groups into the topic that has a matching @code{subscribe} topic
1275 parameter (@pxref{Topic Parameters}). For instance, a @code{subscribe}
1276 topic parameter that looks like
1282 will mean that all groups that match that regex will be subscribed under
1285 If no topics match the groups, the groups will be subscribed in the
1290 @vindex gnus-subscribe-hierarchical-interactive
1291 A closely related variable is
1292 @code{gnus-subscribe-hierarchical-interactive}. (That's quite a
1293 mouthful.) If this variable is non-@code{nil}, Gnus will ask you in a
1294 hierarchical fashion whether to subscribe to new groups or not. Gnus
1295 will ask you for each sub-hierarchy whether you want to descend the
1298 One common mistake is to set the variable a few paragraphs above
1299 (@code{gnus-subscribe-newsgroup-method}) to
1300 @code{gnus-subscribe-hierarchical-interactive}. This is an error. This
1301 will not work. This is ga-ga. So don't do it.
1304 @node Filtering New Groups
1305 @subsection Filtering New Groups
1307 A nice and portable way to control which new newsgroups should be
1308 subscribed (or ignored) is to put an @dfn{options} line at the start of
1309 the @file{.newsrc} file. Here's an example:
1312 options -n !alt.all !rec.all sci.all
1315 @vindex gnus-subscribe-options-newsgroup-method
1316 This line obviously belongs to a serious-minded intellectual scientific
1317 person (or she may just be plain old boring), because it says that all
1318 groups that have names beginning with @samp{alt} and @samp{rec} should
1319 be ignored, and all groups with names beginning with @samp{sci} should
1320 be subscribed. Gnus will not use the normal subscription method for
1321 subscribing these groups.
1322 @code{gnus-subscribe-options-newsgroup-method} is used instead. This
1323 variable defaults to @code{gnus-subscribe-alphabetically}.
1325 @vindex gnus-options-not-subscribe
1326 @vindex gnus-options-subscribe
1327 If you don't want to mess with your @file{.newsrc} file, you can just
1328 set the two variables @code{gnus-options-subscribe} and
1329 @code{gnus-options-not-subscribe}. These two variables do exactly the
1330 same as the @file{.newsrc} @samp{options -n} trick. Both are regexps,
1331 and if the new group matches the former, it will be unconditionally
1332 subscribed, and if it matches the latter, it will be ignored.
1334 @vindex gnus-auto-subscribed-groups
1335 Yet another variable that meddles here is
1336 @code{gnus-auto-subscribed-groups}. It works exactly like
1337 @code{gnus-options-subscribe}, and is therefore really superfluous,
1338 but I thought it would be nice to have two of these. This variable is
1339 more meant for setting some ground rules, while the other variable is
1340 used more for user fiddling. By default this variable makes all new
1341 groups that come from mail back ends (@code{nnml}, @code{nnbabyl},
1342 @code{nnfolder}, @code{nnmbox}, @code{nnmh}, and @code{nnmaildir})
1343 subscribed. If you don't like that, just set this variable to
1346 New groups that match this regexp are subscribed using
1347 @code{gnus-subscribe-options-newsgroup-method}.
1350 @node Changing Servers
1351 @section Changing Servers
1352 @cindex changing servers
1354 Sometimes it is necessary to move from one @acronym{NNTP} server to another.
1355 This happens very rarely, but perhaps you change jobs, or one server is
1356 very flaky and you want to use another.
1358 Changing the server is pretty easy, right? You just change
1359 @code{gnus-select-method} to point to the new server?
1363 Article numbers are not (in any way) kept synchronized between different
1364 @acronym{NNTP} servers, and the only way Gnus keeps track of what articles
1365 you have read is by keeping track of article numbers. So when you
1366 change @code{gnus-select-method}, your @file{.newsrc} file becomes
1369 Gnus provides a few functions to attempt to translate a @file{.newsrc}
1370 file from one server to another. They all have one thing in
1371 common---they take a looong time to run. You don't want to use these
1372 functions more than absolutely necessary.
1374 @kindex M-x gnus-change-server
1375 @findex gnus-change-server
1376 If you have access to both servers, Gnus can request the headers for all
1377 the articles you have read and compare @code{Message-ID}s and map the
1378 article numbers of the read articles and article marks. The @kbd{M-x
1379 gnus-change-server} command will do this for all your native groups. It
1380 will prompt for the method you want to move to.
1382 @kindex M-x gnus-group-move-group-to-server
1383 @findex gnus-group-move-group-to-server
1384 You can also move individual groups with the @kbd{M-x
1385 gnus-group-move-group-to-server} command. This is useful if you want to
1386 move a (foreign) group from one server to another.
1388 @kindex M-x gnus-group-clear-data-on-native-groups
1389 @findex gnus-group-clear-data-on-native-groups
1390 If you don't have access to both the old and new server, all your marks
1391 and read ranges have become worthless. You can use the @kbd{M-x
1392 gnus-group-clear-data-on-native-groups} command to clear out all data
1393 that you have on your native groups. Use with caution.
1395 @kindex M-x gnus-group-clear-data
1396 @findex gnus-group-clear-data
1397 Clear the data from the current group only---nix out marks and the
1398 list of read articles (@code{gnus-group-clear-data}).
1400 After changing servers, you @strong{must} move the cache hierarchy away,
1401 since the cached articles will have wrong article numbers, which will
1402 affect which articles Gnus thinks are read.
1403 @code{gnus-group-clear-data-on-native-groups} will ask you if you want
1404 to have it done automatically; for @code{gnus-group-clear-data}, you
1405 can use @kbd{M-x gnus-cache-move-cache} (but beware, it will move the
1406 cache for all groups).
1410 @section Startup Files
1411 @cindex startup files
1416 Most common Unix news readers use a shared startup file called
1417 @file{.newsrc}. This file contains all the information about what
1418 groups are subscribed, and which articles in these groups have been
1421 Things got a bit more complicated with @sc{gnus}. In addition to
1422 keeping the @file{.newsrc} file updated, it also used a file called
1423 @file{.newsrc.el} for storing all the information that didn't fit into
1424 the @file{.newsrc} file. (Actually, it also duplicated everything in
1425 the @file{.newsrc} file.) @sc{gnus} would read whichever one of these
1426 files was the most recently saved, which enabled people to swap between
1427 @sc{gnus} and other newsreaders.
1429 That was kinda silly, so Gnus went one better: In addition to the
1430 @file{.newsrc} and @file{.newsrc.el} files, Gnus also has a file called
1431 @file{.newsrc.eld}. It will read whichever of these files that are most
1432 recent, but it will never write a @file{.newsrc.el} file. You should
1433 never delete the @file{.newsrc.eld} file---it contains much information
1434 not stored in the @file{.newsrc} file.
1436 @vindex gnus-save-newsrc-file
1437 @vindex gnus-read-newsrc-file
1438 You can turn off writing the @file{.newsrc} file by setting
1439 @code{gnus-save-newsrc-file} to @code{nil}, which means you can delete
1440 the file and save some space, as well as exiting from Gnus faster.
1441 However, this will make it impossible to use other newsreaders than
1442 Gnus. But hey, who would want to, right? Similarly, setting
1443 @code{gnus-read-newsrc-file} to @code{nil} makes Gnus ignore the
1444 @file{.newsrc} file and any @file{.newsrc-SERVER} files, which can be
1445 convenient if you use a different news reader occasionally, and you
1446 want to read a different subset of the available groups with that
1449 @vindex gnus-save-killed-list
1450 If @code{gnus-save-killed-list} (default @code{t}) is @code{nil}, Gnus
1451 will not save the list of killed groups to the startup file. This will
1452 save both time (when starting and quitting) and space (on disk). It
1453 will also mean that Gnus has no record of what groups are new or old,
1454 so the automatic new groups subscription methods become meaningless.
1455 You should always set @code{gnus-check-new-newsgroups} to @code{nil} or
1456 @code{ask-server} if you set this variable to @code{nil} (@pxref{New
1457 Groups}). This variable can also be a regular expression. If that's
1458 the case, remove all groups that do not match this regexp before
1459 saving. This can be useful in certain obscure situations that involve
1460 several servers where not all servers support @code{ask-server}.
1462 @vindex gnus-startup-file
1463 @vindex gnus-backup-startup-file
1464 @vindex version-control
1465 The @code{gnus-startup-file} variable says where the startup files are.
1466 The default value is @file{~/.newsrc}, with the Gnus (El Dingo) startup
1467 file being whatever that one is, with a @samp{.eld} appended.
1468 If you want version control for this file, set
1469 @code{gnus-backup-startup-file}. It respects the same values as the
1470 @code{version-control} variable.
1472 @vindex gnus-save-newsrc-hook
1473 @vindex gnus-save-quick-newsrc-hook
1474 @vindex gnus-save-standard-newsrc-hook
1475 @code{gnus-save-newsrc-hook} is called before saving any of the newsrc
1476 files, while @code{gnus-save-quick-newsrc-hook} is called just before
1477 saving the @file{.newsrc.eld} file, and
1478 @code{gnus-save-standard-newsrc-hook} is called just before saving the
1479 @file{.newsrc} file. The latter two are commonly used to turn version
1480 control on or off. Version control is on by default when saving the
1481 startup files. If you want to turn backup creation off, say something like:
1484 (defun turn-off-backup ()
1485 (set (make-local-variable 'backup-inhibited) t))
1487 (add-hook 'gnus-save-quick-newsrc-hook 'turn-off-backup)
1488 (add-hook 'gnus-save-standard-newsrc-hook 'turn-off-backup)
1491 @vindex gnus-init-file
1492 @vindex gnus-site-init-file
1493 When Gnus starts, it will read the @code{gnus-site-init-file}
1494 (@file{.../site-lisp/gnus-init} by default) and @code{gnus-init-file}
1495 (@file{~/.gnus} by default) files. These are normal Emacs Lisp files
1496 and can be used to avoid cluttering your @file{~/.emacs} and
1497 @file{site-init} files with Gnus stuff. Gnus will also check for files
1498 with the same names as these, but with @file{.elc} and @file{.el}
1499 suffixes. In other words, if you have set @code{gnus-init-file} to
1500 @file{~/.gnus}, it will look for @file{~/.gnus.elc}, @file{~/.gnus.el},
1501 and finally @file{~/.gnus} (in this order). If Emacs was invoked with
1502 the @option{-q} or @option{--no-init-file} options (@pxref{Initial
1503 Options, ,Initial Options, emacs, The Emacs Manual}), Gnus doesn't read
1504 @code{gnus-init-file}.
1509 @cindex dribble file
1512 Whenever you do something that changes the Gnus data (reading articles,
1513 catching up, killing/subscribing groups), the change is added to a
1514 special @dfn{dribble buffer}. This buffer is auto-saved the normal
1515 Emacs way. If your Emacs should crash before you have saved the
1516 @file{.newsrc} files, all changes you have made can be recovered from
1519 If Gnus detects this file at startup, it will ask the user whether to
1520 read it. The auto save file is deleted whenever the real startup file is
1523 @vindex gnus-use-dribble-file
1524 If @code{gnus-use-dribble-file} is @code{nil}, Gnus won't create and
1525 maintain a dribble buffer. The default is @code{t}.
1527 @vindex gnus-dribble-directory
1528 Gnus will put the dribble file(s) in @code{gnus-dribble-directory}. If
1529 this variable is @code{nil}, which it is by default, Gnus will dribble
1530 into the directory where the @file{.newsrc} file is located. (This is
1531 normally the user's home directory.) The dribble file will get the same
1532 file permissions as the @file{.newsrc} file.
1534 @vindex gnus-always-read-dribble-file
1535 If @code{gnus-always-read-dribble-file} is non-@code{nil}, Gnus will
1536 read the dribble file on startup without querying the user.
1539 @node The Active File
1540 @section The Active File
1542 @cindex ignored groups
1544 When Gnus starts, or indeed whenever it tries to determine whether new
1545 articles have arrived, it reads the active file. This is a very large
1546 file that lists all the active groups and articles on the server.
1548 @vindex gnus-ignored-newsgroups
1549 Before examining the active file, Gnus deletes all lines that match the
1550 regexp @code{gnus-ignored-newsgroups}. This is done primarily to reject
1551 any groups with bogus names, but you can use this variable to make Gnus
1552 ignore hierarchies you aren't ever interested in. However, this is not
1553 recommended. In fact, it's highly discouraged. Instead, @pxref{New
1554 Groups} for an overview of other variables that can be used instead.
1557 @c @code{nil} by default, and will slow down active file handling somewhat
1558 @c if you set it to anything else.
1560 @vindex gnus-read-active-file
1562 The active file can be rather Huge, so if you have a slow network, you
1563 can set @code{gnus-read-active-file} to @code{nil} to prevent Gnus from
1564 reading the active file. This variable is @code{some} by default.
1566 Gnus will try to make do by getting information just on the groups that
1567 you actually subscribe to.
1569 Note that if you subscribe to lots and lots of groups, setting this
1570 variable to @code{nil} will probably make Gnus slower, not faster. At
1571 present, having this variable @code{nil} will slow Gnus down
1572 considerably, unless you read news over a 2400 baud modem.
1574 This variable can also have the value @code{some}. Gnus will then
1575 attempt to read active info only on the subscribed groups. On some
1576 servers this is quite fast (on sparkling, brand new INN servers that
1577 support the @code{LIST ACTIVE group} command), on others this isn't fast
1578 at all. In any case, @code{some} should be faster than @code{nil}, and
1579 is certainly faster than @code{t} over slow lines.
1581 Some news servers (old versions of Leafnode and old versions of INN, for
1582 instance) do not support the @code{LIST ACTIVE group}. For these
1583 servers, @code{nil} is probably the most efficient value for this
1586 If this variable is @code{nil}, Gnus will ask for group info in total
1587 lock-step, which isn't very fast. If it is @code{some} and you use an
1588 @acronym{NNTP} server, Gnus will pump out commands as fast as it can, and
1589 read all the replies in one swoop. This will normally result in better
1590 performance, but if the server does not support the aforementioned
1591 @code{LIST ACTIVE group} command, this isn't very nice to the server.
1593 If you think that starting up Gnus takes too long, try all the three
1594 different values for this variable and see what works best for you.
1596 In any case, if you use @code{some} or @code{nil}, you should definitely
1597 kill all groups that you aren't interested in to speed things up.
1599 Note that this variable also affects active file retrieval from
1600 secondary select methods.
1603 @node Startup Variables
1604 @section Startup Variables
1608 @item gnus-load-hook
1609 @vindex gnus-load-hook
1610 A hook run while Gnus is being loaded. Note that this hook will
1611 normally be run just once in each Emacs session, no matter how many
1612 times you start Gnus.
1614 @item gnus-before-startup-hook
1615 @vindex gnus-before-startup-hook
1616 A hook run after starting up Gnus successfully.
1618 @item gnus-startup-hook
1619 @vindex gnus-startup-hook
1620 A hook run as the very last thing after starting up Gnus
1622 @item gnus-started-hook
1623 @vindex gnus-started-hook
1624 A hook that is run as the very last thing after starting up Gnus
1627 @item gnus-setup-news-hook
1628 @vindex gnus-setup-news-hook
1629 A hook that is run after reading the @file{.newsrc} file(s), but before
1630 generating the group buffer.
1632 @item gnus-check-bogus-newsgroups
1633 @vindex gnus-check-bogus-newsgroups
1634 If non-@code{nil}, Gnus will check for and delete all bogus groups at
1635 startup. A @dfn{bogus group} is a group that you have in your
1636 @file{.newsrc} file, but doesn't exist on the news server. Checking for
1637 bogus groups can take quite a while, so to save time and resources it's
1638 best to leave this option off, and do the checking for bogus groups once
1639 in a while from the group buffer instead (@pxref{Group Maintenance}).
1641 @item gnus-inhibit-startup-message
1642 @vindex gnus-inhibit-startup-message
1643 If non-@code{nil}, the startup message won't be displayed. That way,
1644 your boss might not notice as easily that you are reading news instead
1645 of doing your job. Note that this variable is used before
1646 @file{~/.gnus.el} is loaded, so it should be set in @file{.emacs} instead.
1648 @item gnus-no-groups-message
1649 @vindex gnus-no-groups-message
1650 Message displayed by Gnus when no groups are available.
1652 @item gnus-play-startup-jingle
1653 @vindex gnus-play-startup-jingle
1654 If non-@code{nil}, play the Gnus jingle at startup.
1656 @item gnus-startup-jingle
1657 @vindex gnus-startup-jingle
1658 Jingle to be played if the above variable is non-@code{nil}. The
1659 default is @samp{Tuxedomoon.Jingle4.au}.
1665 @chapter Group Buffer
1666 @cindex group buffer
1668 @c Alex Schroeder suggests to rearrange this as follows:
1670 @c <kensanata> ok, just save it for reference. I'll go to bed in a minute.
1671 @c 1. Selecting a Group, 2. (new) Finding a Group, 3. Group Levels,
1672 @c 4. Subscription Commands, 5. Group Maneuvering, 6. Group Data,
1673 @c 7. Group Score, 8. Group Buffer Format
1674 @c <kensanata> Group Levels should have more information on levels 5 to 9. I
1675 @c suggest to split the 4th paragraph ("Gnus considers groups...") as follows:
1676 @c <kensanata> First, "Gnus considers groups... (default 9)."
1677 @c <kensanata> New, a table summarizing what levels 1 to 9 mean.
1678 @c <kensanata> Third, "Gnus treats subscribed ... reasons of efficiency"
1679 @c <kensanata> Then expand the next paragraph or add some more to it.
1680 @c This short one sentence explains levels 1 and 2, therefore I understand
1681 @c that I should keep important news at 3 and boring news at 4.
1682 @c Say so! Then go on to explain why I should bother with levels 6 to 9.
1683 @c Maybe keep those that you don't want to read temporarily at 6,
1684 @c those that you never want to read at 8, those that offend your
1685 @c human rights at 9...
1688 The @dfn{group buffer} lists all (or parts) of the available groups. It
1689 is the first buffer shown when Gnus starts, and will never be killed as
1690 long as Gnus is active.
1694 \gnusfigure{The Group Buffer}{320}{
1695 \put(75,50){\epsfig{figure=ps/group,height=9cm}}
1696 \put(120,37){\makebox(0,0)[t]{Buffer name}}
1697 \put(120,38){\vector(1,2){10}}
1698 \put(40,60){\makebox(0,0)[r]{Mode line}}
1699 \put(40,58){\vector(1,0){30}}
1700 \put(200,28){\makebox(0,0)[t]{Native select method}}
1701 \put(200,26){\vector(-1,2){15}}
1707 * Group Buffer Format:: Information listed and how you can change it.
1708 * Group Maneuvering:: Commands for moving in the group buffer.
1709 * Selecting a Group:: Actually reading news.
1710 * Subscription Commands:: Unsubscribing, killing, subscribing.
1711 * Group Data:: Changing the info for a group.
1712 * Group Levels:: Levels? What are those, then?
1713 * Group Score:: A mechanism for finding out what groups you like.
1714 * Marking Groups:: You can mark groups for later processing.
1715 * Foreign Groups:: Creating and editing groups.
1716 * Group Parameters:: Each group may have different parameters set.
1717 * Listing Groups:: Gnus can list various subsets of the groups.
1718 * Sorting Groups:: Re-arrange the group order.
1719 * Group Maintenance:: Maintaining a tidy @file{.newsrc} file.
1720 * Browse Foreign Server:: You can browse a server. See what it has to offer.
1721 * Exiting Gnus:: Stop reading news and get some work done.
1722 * Group Topics:: A folding group mode divided into topics.
1723 * Misc Group Stuff:: Other stuff that you can to do.
1727 @node Group Buffer Format
1728 @section Group Buffer Format
1731 * Group Line Specification:: Deciding how the group buffer is to look.
1732 * Group Mode Line Specification:: The group buffer mode line.
1733 * Group Highlighting:: Having nice colors in the group buffer.
1737 @node Group Line Specification
1738 @subsection Group Line Specification
1739 @cindex group buffer format
1741 The default format of the group buffer is nice and dull, but you can
1742 make it as exciting and ugly as you feel like.
1744 Here's a couple of example group lines:
1747 25: news.announce.newusers
1748 * 0: alt.fan.andrea-dworkin
1753 You can see that there are 25 unread articles in
1754 @samp{news.announce.newusers}. There are no unread articles, but some
1755 ticked articles, in @samp{alt.fan.andrea-dworkin} (see that little
1756 asterisk at the beginning of the line?).
1758 @vindex gnus-group-line-format
1759 You can change that format to whatever you want by fiddling with the
1760 @code{gnus-group-line-format} variable. This variable works along the
1761 lines of a @code{format} specification, which is pretty much the same as
1762 a @code{printf} specifications, for those of you who use (feh!) C.
1763 @xref{Formatting Variables}.
1765 @samp{%M%S%5y:%B%(%g%)\n} is the value that produced those lines above.
1767 There should always be a colon on the line; the cursor always moves to
1768 the colon after performing an operation. @xref{Positioning
1769 Point}. Nothing else is required---not even the group name. All
1770 displayed text is just window dressing, and is never examined by Gnus.
1771 Gnus stores all real information it needs using text properties.
1773 (Note that if you make a really strange, wonderful, spreadsheet-like
1774 layout, everybody will believe you are hard at work with the accounting
1775 instead of wasting time reading news.)
1777 Here's a list of all available format characters:
1782 An asterisk if the group only has marked articles.
1785 Whether the group is subscribed.
1788 Level of subscribedness.
1791 Number of unread articles.
1794 Number of dormant articles.
1797 Number of ticked articles.
1800 Number of read articles.
1803 Number of unseen articles.
1806 Estimated total number of articles. (This is really @var{max-number}
1807 minus @var{min-number} plus 1.)
1809 Gnus uses this estimation because the @acronym{NNTP} protocol provides
1810 efficient access to @var{max-number} and @var{min-number} but getting
1811 the true unread message count is not possible efficiently. For
1812 hysterical raisins, even the mail back ends, where the true number of
1813 unread messages might be available efficiently, use the same limited
1814 interface. To remove this restriction from Gnus means that the back
1815 end interface has to be changed, which is not an easy job. If you
1816 want to work on this, please contact the Gnus mailing list.
1819 Number of unread, unticked, non-dormant articles.
1822 Number of ticked and dormant articles.
1831 Group comment (@pxref{Group Parameters}) or group name if there is no
1832 comment element in the group parameters.
1835 Newsgroup description. You need to read the group descriptions
1836 before these will appear, and to do that, you either have to set
1837 @code{gnus-read-active-file} or use the group buffer @kbd{M-d}
1841 @samp{m} if moderated.
1844 @samp{(m)} if moderated.
1850 If the summary buffer for the group is open or not.
1856 A string that looks like @samp{<%s:%n>} if a foreign select method is
1860 Indentation based on the level of the topic (@pxref{Group Topics}).
1863 @vindex gnus-group-uncollapsed-levels
1864 Short (collapsed) group name. The @code{gnus-group-uncollapsed-levels}
1865 variable says how many levels to leave at the end of the group name.
1866 The default is 1---this will mean that group names like
1867 @samp{gnu.emacs.gnus} will be shortened to @samp{g.e.gnus}.
1870 @vindex gnus-new-mail-mark
1872 @samp{%} (@code{gnus-new-mail-mark}) if there has arrived new mail to
1876 @samp{#} (@code{gnus-process-mark}) if the group is process marked.
1879 A string that says when you last read the group (@pxref{Group
1883 The disk space used by the articles fetched by both the cache and
1884 agent. The value is automatically scaled to bytes(B), kilobytes(K),
1885 megabytes(M), or gigabytes(G) to minimize the column width. A format
1886 of %7F is sufficient for a fixed-width column.
1889 User defined specifier. The next character in the format string should
1890 be a letter. Gnus will call the function
1891 @code{gnus-user-format-function-}@samp{X}, where @samp{X} is the letter
1892 following @samp{%u}. The function will be passed a single dummy
1893 parameter as argument. The function should return a string, which will
1894 be inserted into the buffer just like information from any other
1899 All the ``number-of'' specs will be filled with an asterisk (@samp{*})
1900 if no info is available---for instance, if it is a non-activated foreign
1901 group, or a bogus native group.
1904 @node Group Mode Line Specification
1905 @subsection Group Mode Line Specification
1906 @cindex group mode line
1908 @vindex gnus-group-mode-line-format
1909 The mode line can be changed by setting
1910 @code{gnus-group-mode-line-format} (@pxref{Mode Line Formatting}). It
1911 doesn't understand that many format specifiers:
1915 The native news server.
1917 The native select method.
1921 @node Group Highlighting
1922 @subsection Group Highlighting
1923 @cindex highlighting
1924 @cindex group highlighting
1926 @vindex gnus-group-highlight
1927 Highlighting in the group buffer is controlled by the
1928 @code{gnus-group-highlight} variable. This is an alist with elements
1929 that look like @code{(@var{form} . @var{face})}. If @var{form} evaluates to
1930 something non-@code{nil}, the @var{face} will be used on the line.
1932 Here's an example value for this variable that might look nice if the
1936 (cond (window-system
1937 (setq custom-background-mode 'light)
1938 (defface my-group-face-1
1939 '((t (:foreground "Red" :bold t))) "First group face")
1940 (defface my-group-face-2
1941 '((t (:foreground "DarkSeaGreen4" :bold t)))
1942 "Second group face")
1943 (defface my-group-face-3
1944 '((t (:foreground "Green4" :bold t))) "Third group face")
1945 (defface my-group-face-4
1946 '((t (:foreground "SteelBlue" :bold t))) "Fourth group face")
1947 (defface my-group-face-5
1948 '((t (:foreground "Blue" :bold t))) "Fifth group face")))
1950 (setq gnus-group-highlight
1951 '(((> unread 200) . my-group-face-1)
1952 ((and (< level 3) (zerop unread)) . my-group-face-2)
1953 ((< level 3) . my-group-face-3)
1954 ((zerop unread) . my-group-face-4)
1955 (t . my-group-face-5)))
1958 Also @pxref{Faces and Fonts}.
1960 Variables that are dynamically bound when the forms are evaluated
1967 The number of unread articles in the group.
1971 Whether the group is a mail group.
1973 The level of the group.
1975 The score of the group.
1977 The number of ticked articles in the group.
1979 The total number of articles in the group. Or rather,
1980 @var{max-number} minus @var{min-number} plus one.
1982 When using the topic minor mode, this variable is bound to the current
1983 topic being inserted.
1986 When the forms are @code{eval}ed, point is at the beginning of the line
1987 of the group in question, so you can use many of the normal Gnus
1988 functions for snarfing info on the group.
1990 @vindex gnus-group-update-hook
1991 @findex gnus-group-highlight-line
1992 @code{gnus-group-update-hook} is called when a group line is changed.
1993 It will not be called when @code{gnus-visual} is @code{nil}. This hook
1994 calls @code{gnus-group-highlight-line} by default.
1997 @node Group Maneuvering
1998 @section Group Maneuvering
1999 @cindex group movement
2001 All movement commands understand the numeric prefix and will behave as
2002 expected, hopefully.
2008 @findex gnus-group-next-unread-group
2009 Go to the next group that has unread articles
2010 (@code{gnus-group-next-unread-group}).
2016 @findex gnus-group-prev-unread-group
2017 Go to the previous group that has unread articles
2018 (@code{gnus-group-prev-unread-group}).
2022 @findex gnus-group-next-group
2023 Go to the next group (@code{gnus-group-next-group}).
2027 @findex gnus-group-prev-group
2028 Go to the previous group (@code{gnus-group-prev-group}).
2032 @findex gnus-group-next-unread-group-same-level
2033 Go to the next unread group on the same (or lower) level
2034 (@code{gnus-group-next-unread-group-same-level}).
2038 @findex gnus-group-prev-unread-group-same-level
2039 Go to the previous unread group on the same (or lower) level
2040 (@code{gnus-group-prev-unread-group-same-level}).
2043 Three commands for jumping to groups:
2049 @findex gnus-group-jump-to-group
2050 Jump to a group (and make it visible if it isn't already)
2051 (@code{gnus-group-jump-to-group}). Killed groups can be jumped to, just
2056 @findex gnus-group-best-unread-group
2057 Jump to the unread group with the lowest level
2058 (@code{gnus-group-best-unread-group}).
2062 @findex gnus-group-first-unread-group
2063 Jump to the first group with unread articles
2064 (@code{gnus-group-first-unread-group}).
2067 @vindex gnus-group-goto-unread
2068 If @code{gnus-group-goto-unread} is @code{nil}, all the movement
2069 commands will move to the next group, not the next unread group. Even
2070 the commands that say they move to the next unread group. The default
2074 @node Selecting a Group
2075 @section Selecting a Group
2076 @cindex group selection
2081 @kindex SPACE (Group)
2082 @findex gnus-group-read-group
2083 Select the current group, switch to the summary buffer and display the
2084 first unread article (@code{gnus-group-read-group}). If there are no
2085 unread articles in the group, or if you give a non-numerical prefix to
2086 this command, Gnus will offer to fetch all the old articles in this
2087 group from the server. If you give a numerical prefix @var{n}, @var{n}
2088 determines the number of articles Gnus will fetch. If @var{n} is
2089 positive, Gnus fetches the @var{n} newest articles, if @var{n} is
2090 negative, Gnus fetches the @code{abs(@var{n})} oldest articles.
2092 Thus, @kbd{SPC} enters the group normally, @kbd{C-u SPC} offers old
2093 articles, @kbd{C-u 4 2 SPC} fetches the 42 newest articles, and @kbd{C-u
2094 - 4 2 SPC} fetches the 42 oldest ones.
2096 When you are in the group (in the Summary buffer), you can type
2097 @kbd{M-g} to fetch new articles, or @kbd{C-u M-g} to also show the old
2102 @findex gnus-group-select-group
2103 Select the current group and switch to the summary buffer
2104 (@code{gnus-group-select-group}). Takes the same arguments as
2105 @code{gnus-group-read-group}---the only difference is that this command
2106 does not display the first unread article automatically upon group
2110 @kindex M-RET (Group)
2111 @findex gnus-group-quick-select-group
2112 This does the same as the command above, but tries to do it with the
2113 minimum amount of fuzz (@code{gnus-group-quick-select-group}). No
2114 scoring/killing will be performed, there will be no highlights and no
2115 expunging. This might be useful if you're in a real hurry and have to
2116 enter some humongous group. If you give a 0 prefix to this command
2117 (i.e., @kbd{0 M-RET}), Gnus won't even generate the summary buffer,
2118 which is useful if you want to toggle threading before generating the
2119 summary buffer (@pxref{Summary Generation Commands}).
2122 @kindex M-SPACE (Group)
2123 @findex gnus-group-visible-select-group
2124 This is yet one more command that does the same as the @kbd{RET}
2125 command, but this one does it without expunging and hiding dormants
2126 (@code{gnus-group-visible-select-group}).
2129 @kindex C-M-RET (Group)
2130 @findex gnus-group-select-group-ephemerally
2131 Finally, this command selects the current group ephemerally without
2132 doing any processing of its contents
2133 (@code{gnus-group-select-group-ephemerally}). Even threading has been
2134 turned off. Everything you do in the group after selecting it in this
2135 manner will have no permanent effects.
2139 @vindex gnus-large-newsgroup
2140 The @code{gnus-large-newsgroup} variable says what Gnus should
2141 consider to be a big group. If it is @code{nil}, no groups are
2142 considered big. The default value is 200. If the group has more
2143 (unread and/or ticked) articles than this, Gnus will query the user
2144 before entering the group. The user can then specify how many
2145 articles should be fetched from the server. If the user specifies a
2146 negative number (@var{-n}), the @var{n} oldest articles will be
2147 fetched. If it is positive, the @var{n} articles that have arrived
2148 most recently will be fetched.
2150 @vindex gnus-large-ephemeral-newsgroup
2151 @code{gnus-large-ephemeral-newsgroup} is the same as
2152 @code{gnus-large-newsgroup}, but is only used for ephemeral
2155 @vindex gnus-select-group-hook
2156 @vindex gnus-auto-select-first
2157 @vindex gnus-auto-select-subject
2158 If @code{gnus-auto-select-first} is non-@code{nil}, select an article
2159 automatically when entering a group with the @kbd{SPACE} command.
2160 Which article this is is controlled by the
2161 @code{gnus-auto-select-subject} variable. Valid values for this
2167 Place point on the subject line of the first unread article.
2170 Place point on the subject line of the first article.
2173 Place point on the subject line of the first unseen article.
2175 @item unseen-or-unread
2176 Place point on the subject line of the first unseen article, and if
2177 there is no such article, place point on the subject line of the first
2181 Place point on the subject line of the highest-scored unread article.
2185 This variable can also be a function. In that case, that function
2186 will be called to place point on a subject line.
2188 If you want to prevent automatic selection in some group (say, in a
2189 binary group with Huge articles) you can set the
2190 @code{gnus-auto-select-first} variable to @code{nil} in
2191 @code{gnus-select-group-hook}, which is called when a group is
2195 @node Subscription Commands
2196 @section Subscription Commands
2197 @cindex subscription
2205 @findex gnus-group-unsubscribe-current-group
2206 @c @icon{gnus-group-unsubscribe}
2207 Toggle subscription to the current group
2208 (@code{gnus-group-unsubscribe-current-group}).
2214 @findex gnus-group-unsubscribe-group
2215 Prompt for a group to subscribe, and then subscribe it. If it was
2216 subscribed already, unsubscribe it instead
2217 (@code{gnus-group-unsubscribe-group}).
2223 @findex gnus-group-kill-group
2224 @c @icon{gnus-group-kill-group}
2225 Kill the current group (@code{gnus-group-kill-group}).
2231 @findex gnus-group-yank-group
2232 Yank the last killed group (@code{gnus-group-yank-group}).
2235 @kindex C-x C-t (Group)
2236 @findex gnus-group-transpose-groups
2237 Transpose two groups (@code{gnus-group-transpose-groups}). This isn't
2238 really a subscription command, but you can use it instead of a
2239 kill-and-yank sequence sometimes.
2245 @findex gnus-group-kill-region
2246 Kill all groups in the region (@code{gnus-group-kill-region}).
2250 @findex gnus-group-kill-all-zombies
2251 Kill all zombie groups (@code{gnus-group-kill-all-zombies}).
2254 @kindex S C-k (Group)
2255 @findex gnus-group-kill-level
2256 Kill all groups on a certain level (@code{gnus-group-kill-level}).
2257 These groups can't be yanked back after killing, so this command should
2258 be used with some caution. The only time where this command comes in
2259 really handy is when you have a @file{.newsrc} with lots of unsubscribed
2260 groups that you want to get rid off. @kbd{S C-k} on level 7 will
2261 kill off all unsubscribed groups that do not have message numbers in the
2262 @file{.newsrc} file.
2266 Also @pxref{Group Levels}.
2276 @findex gnus-group-catchup-current
2277 @vindex gnus-group-catchup-group-hook
2278 @c @icon{gnus-group-catchup-current}
2279 Mark all unticked articles in this group as read
2280 (@code{gnus-group-catchup-current}).
2281 @code{gnus-group-catchup-group-hook} is called when catching up a group from
2286 @findex gnus-group-catchup-current-all
2287 Mark all articles in this group, even the ticked ones, as read
2288 (@code{gnus-group-catchup-current-all}).
2292 @findex gnus-group-clear-data
2293 Clear the data from the current group---nix out marks and the list of
2294 read articles (@code{gnus-group-clear-data}).
2296 @item M-x gnus-group-clear-data-on-native-groups
2297 @kindex M-x gnus-group-clear-data-on-native-groups
2298 @findex gnus-group-clear-data-on-native-groups
2299 If you have switched from one @acronym{NNTP} server to another, all your marks
2300 and read ranges have become worthless. You can use this command to
2301 clear out all data that you have on your native groups. Use with
2308 @section Group Levels
2312 All groups have a level of @dfn{subscribedness}. For instance, if a
2313 group is on level 2, it is more subscribed than a group on level 5. You
2314 can ask Gnus to just list groups on a given level or lower
2315 (@pxref{Listing Groups}), or to just check for new articles in groups on
2316 a given level or lower (@pxref{Scanning New Messages}).
2318 Remember: The higher the level of the group, the less important it is.
2324 @findex gnus-group-set-current-level
2325 Set the level of the current group. If a numeric prefix is given, the
2326 next @var{n} groups will have their levels set. The user will be
2327 prompted for a level.
2330 @vindex gnus-level-killed
2331 @vindex gnus-level-zombie
2332 @vindex gnus-level-unsubscribed
2333 @vindex gnus-level-subscribed
2334 Gnus considers groups from levels 1 to
2335 @code{gnus-level-subscribed} (inclusive) (default 5) to be subscribed,
2336 @code{gnus-level-subscribed} (exclusive) and
2337 @code{gnus-level-unsubscribed} (inclusive) (default 7) to be
2338 unsubscribed, @code{gnus-level-zombie} to be zombies (walking dead)
2339 (default 8) and @code{gnus-level-killed} to be killed (completely dead)
2340 (default 9). Gnus treats subscribed and unsubscribed groups exactly the
2341 same, but zombie and killed groups have no information on what articles
2342 you have read, etc, stored. This distinction between dead and living
2343 groups isn't done because it is nice or clever, it is done purely for
2344 reasons of efficiency.
2346 It is recommended that you keep all your mail groups (if any) on quite
2347 low levels (e.g. 1 or 2).
2349 Maybe the following description of the default behavior of Gnus helps to
2350 understand what these levels are all about. By default, Gnus shows you
2351 subscribed nonempty groups, but by hitting @kbd{L} you can have it show
2352 empty subscribed groups and unsubscribed groups, too. Type @kbd{l} to
2353 go back to showing nonempty subscribed groups again. Thus, unsubscribed
2354 groups are hidden, in a way.
2356 Zombie and killed groups are similar to unsubscribed groups in that they
2357 are hidden by default. But they are different from subscribed and
2358 unsubscribed groups in that Gnus doesn't ask the news server for
2359 information (number of messages, number of unread messages) on zombie
2360 and killed groups. Normally, you use @kbd{C-k} to kill the groups you
2361 aren't interested in. If most groups are killed, Gnus is faster.
2363 Why does Gnus distinguish between zombie and killed groups? Well, when
2364 a new group arrives on the server, Gnus by default makes it a zombie
2365 group. This means that you are normally not bothered with new groups,
2366 but you can type @kbd{A z} to get a list of all new groups. Subscribe
2367 the ones you like and kill the ones you don't want. (@kbd{A k} shows a
2368 list of killed groups.)
2370 If you want to play with the level variables, you should show some care.
2371 Set them once, and don't touch them ever again. Better yet, don't touch
2372 them at all unless you know exactly what you're doing.
2374 @vindex gnus-level-default-unsubscribed
2375 @vindex gnus-level-default-subscribed
2376 Two closely related variables are @code{gnus-level-default-subscribed}
2377 (default 3) and @code{gnus-level-default-unsubscribed} (default 6),
2378 which are the levels that new groups will be put on if they are
2379 (un)subscribed. These two variables should, of course, be inside the
2380 relevant valid ranges.
2382 @vindex gnus-keep-same-level
2383 If @code{gnus-keep-same-level} is non-@code{nil}, some movement commands
2384 will only move to groups of the same level (or lower). In
2385 particular, going from the last article in one group to the next group
2386 will go to the next group of the same level (or lower). This might be
2387 handy if you want to read the most important groups before you read the
2390 If this variable is @code{best}, Gnus will make the next newsgroup the
2391 one with the best level.
2393 @vindex gnus-group-default-list-level
2394 All groups with a level less than or equal to
2395 @code{gnus-group-default-list-level} will be listed in the group buffer
2398 @vindex gnus-group-list-inactive-groups
2399 If @code{gnus-group-list-inactive-groups} is non-@code{nil}, non-active
2400 groups will be listed along with the unread groups. This variable is
2401 @code{t} by default. If it is @code{nil}, inactive groups won't be
2404 @vindex gnus-group-use-permanent-levels
2405 If @code{gnus-group-use-permanent-levels} is non-@code{nil}, once you
2406 give a level prefix to @kbd{g} or @kbd{l}, all subsequent commands will
2407 use this level as the ``work'' level.
2409 @vindex gnus-activate-level
2410 Gnus will normally just activate (i. e., query the server about) groups
2411 on level @code{gnus-activate-level} or less. If you don't want to
2412 activate unsubscribed groups, for instance, you might set this variable
2413 to 5. The default is 6.
2417 @section Group Score
2422 You would normally keep important groups on high levels, but that scheme
2423 is somewhat restrictive. Don't you wish you could have Gnus sort the
2424 group buffer according to how often you read groups, perhaps? Within
2427 This is what @dfn{group score} is for. You can have Gnus assign a score
2428 to each group through the mechanism described below. You can then sort
2429 the group buffer based on this score. Alternatively, you can sort on
2430 score and then level. (Taken together, the level and the score is
2431 called the @dfn{rank} of the group. A group that is on level 4 and has
2432 a score of 1 has a higher rank than a group on level 5 that has a score
2433 of 300. (The level is the most significant part and the score is the
2434 least significant part.))
2436 @findex gnus-summary-bubble-group
2437 If you want groups you read often to get higher scores than groups you
2438 read seldom you can add the @code{gnus-summary-bubble-group} function to
2439 the @code{gnus-summary-exit-hook} hook. This will result (after
2440 sorting) in a bubbling sort of action. If you want to see that in
2441 action after each summary exit, you can add
2442 @code{gnus-group-sort-groups-by-rank} or
2443 @code{gnus-group-sort-groups-by-score} to the same hook, but that will
2444 slow things down somewhat.
2447 @node Marking Groups
2448 @section Marking Groups
2449 @cindex marking groups
2451 If you want to perform some command on several groups, and they appear
2452 subsequently in the group buffer, you would normally just give a
2453 numerical prefix to the command. Most group commands will then do your
2454 bidding on those groups.
2456 However, if the groups are not in sequential order, you can still
2457 perform a command on several groups. You simply mark the groups first
2458 with the process mark and then execute the command.
2466 @findex gnus-group-mark-group
2467 Set the mark on the current group (@code{gnus-group-mark-group}).
2473 @findex gnus-group-unmark-group
2474 Remove the mark from the current group
2475 (@code{gnus-group-unmark-group}).
2479 @findex gnus-group-unmark-all-groups
2480 Remove the mark from all groups (@code{gnus-group-unmark-all-groups}).
2484 @findex gnus-group-mark-region
2485 Mark all groups between point and mark (@code{gnus-group-mark-region}).
2489 @findex gnus-group-mark-buffer
2490 Mark all groups in the buffer (@code{gnus-group-mark-buffer}).
2494 @findex gnus-group-mark-regexp
2495 Mark all groups that match some regular expression
2496 (@code{gnus-group-mark-regexp}).
2499 Also @pxref{Process/Prefix}.
2501 @findex gnus-group-universal-argument
2502 If you want to execute some command on all groups that have been marked
2503 with the process mark, you can use the @kbd{M-&}
2504 (@code{gnus-group-universal-argument}) command. It will prompt you for
2505 the command to be executed.
2508 @node Foreign Groups
2509 @section Foreign Groups
2510 @cindex foreign groups
2512 Below are some group mode commands for making and editing general foreign
2513 groups, as well as commands to ease the creation of a few
2514 special-purpose groups. All these commands insert the newly created
2515 groups under point---@code{gnus-subscribe-newsgroup-method} is not
2522 @findex gnus-group-make-group
2523 @cindex making groups
2524 Make a new group (@code{gnus-group-make-group}). Gnus will prompt you
2525 for a name, a method and possibly an @dfn{address}. For an easier way
2526 to subscribe to @acronym{NNTP} groups (@pxref{Browse Foreign Server}).
2530 @findex gnus-group-read-ephemeral-group
2531 Make an ephemeral group (@code{gnus-group-read-ephemeral-group}). Gnus
2532 will prompt you for a name, a method and an @dfn{address}.
2536 @findex gnus-group-rename-group
2537 @cindex renaming groups
2538 Rename the current group to something else
2539 (@code{gnus-group-rename-group}). This is valid only on some
2540 groups---mail groups mostly. This command might very well be quite slow
2546 @findex gnus-group-customize
2547 Customize the group parameters (@code{gnus-group-customize}).
2551 @findex gnus-group-edit-group-method
2552 @cindex renaming groups
2553 Enter a buffer where you can edit the select method of the current
2554 group (@code{gnus-group-edit-group-method}).
2558 @findex gnus-group-edit-group-parameters
2559 Enter a buffer where you can edit the group parameters
2560 (@code{gnus-group-edit-group-parameters}).
2564 @findex gnus-group-edit-group
2565 Enter a buffer where you can edit the group info
2566 (@code{gnus-group-edit-group}).
2570 @findex gnus-group-make-directory-group
2572 Make a directory group (@pxref{Directory Groups}). You will be prompted
2573 for a directory name (@code{gnus-group-make-directory-group}).
2578 @findex gnus-group-make-help-group
2579 Make the Gnus help group (@code{gnus-group-make-help-group}).
2583 @cindex (ding) archive
2584 @cindex archive group
2585 @findex gnus-group-make-archive-group
2586 @vindex gnus-group-archive-directory
2587 @vindex gnus-group-recent-archive-directory
2588 Make a Gnus archive group (@code{gnus-group-make-archive-group}). By
2589 default a group pointing to the most recent articles will be created
2590 (@code{gnus-group-recent-archive-directory}), but given a prefix, a full
2591 group will be created from @code{gnus-group-archive-directory}.
2595 @findex gnus-group-make-kiboze-group
2597 Make a kiboze group. You will be prompted for a name, for a regexp to
2598 match groups to be ``included'' in the kiboze group, and a series of
2599 strings to match on headers (@code{gnus-group-make-kiboze-group}).
2600 @xref{Kibozed Groups}.
2604 @findex gnus-group-enter-directory
2606 Read an arbitrary directory as if it were a newsgroup with the
2607 @code{nneething} back end (@code{gnus-group-enter-directory}).
2608 @xref{Anything Groups}.
2612 @findex gnus-group-make-doc-group
2613 @cindex ClariNet Briefs
2615 Make a group based on some file or other
2616 (@code{gnus-group-make-doc-group}). If you give a prefix to this
2617 command, you will be prompted for a file name and a file type.
2618 Currently supported types are @code{mbox}, @code{babyl},
2619 @code{digest}, @code{news}, @code{rnews}, @code{mmdf}, @code{forward},
2620 @code{rfc934}, @code{rfc822-forward}, @code{mime-parts},
2621 @code{standard-digest}, @code{slack-digest}, @code{clari-briefs},
2622 @code{nsmail}, @code{outlook}, @code{oe-dbx}, and @code{mailman}. If
2623 you run this command without a prefix, Gnus will guess at the file
2624 type. @xref{Document Groups}.
2628 @vindex gnus-useful-groups
2629 @findex gnus-group-make-useful-group
2630 Create one of the groups mentioned in @code{gnus-useful-groups}
2631 (@code{gnus-group-make-useful-group}).
2635 @findex gnus-group-make-web-group
2639 Make an ephemeral group based on a web search
2640 (@code{gnus-group-make-web-group}). If you give a prefix to this
2641 command, make a solid group instead. You will be prompted for the
2642 search engine type and the search string. Valid search engine types
2643 include @code{google}, @code{dejanews}, and @code{gmane}.
2644 @xref{Web Searches}.
2646 If you use the @code{google} search engine, you can limit the search
2647 to a particular group by using a match string like
2648 @samp{shaving group:alt.sysadmin.recovery}.
2652 @findex gnus-group-make-rss-group
2653 Make a group based on an @acronym{RSS} feed
2654 (@code{gnus-group-make-rss-group}). You will be prompted for an URL.
2658 @kindex G DEL (Group)
2659 @findex gnus-group-delete-group
2660 This function will delete the current group
2661 (@code{gnus-group-delete-group}). If given a prefix, this function will
2662 actually delete all the articles in the group, and forcibly remove the
2663 group itself from the face of the Earth. Use a prefix only if you are
2664 absolutely sure of what you are doing. This command can't be used on
2665 read-only groups (like @code{nntp} groups), though.
2669 @findex gnus-group-make-empty-virtual
2670 Make a new, fresh, empty @code{nnvirtual} group
2671 (@code{gnus-group-make-empty-virtual}). @xref{Virtual Groups}.
2675 @findex gnus-group-add-to-virtual
2676 Add the current group to an @code{nnvirtual} group
2677 (@code{gnus-group-add-to-virtual}). Uses the process/prefix convention.
2680 @xref{Select Methods}, for more information on the various select
2683 @vindex gnus-activate-foreign-newsgroups
2684 If @code{gnus-activate-foreign-newsgroups} is a positive number,
2685 Gnus will check all foreign groups with this level or lower at startup.
2686 This might take quite a while, especially if you subscribe to lots of
2687 groups from different @acronym{NNTP} servers. Also @pxref{Group Levels};
2688 @code{gnus-activate-level} also affects activation of foreign
2692 @node Group Parameters
2693 @section Group Parameters
2694 @cindex group parameters
2696 The group parameters store information local to a particular group.
2697 Here's an example group parameter list:
2700 ((to-address . "ding@@gnus.org")
2704 We see that each element consists of a ``dotted pair''---the thing before
2705 the dot is the key, while the thing after the dot is the value. All the
2706 parameters have this form @emph{except} local variable specs, which are
2707 not dotted pairs, but proper lists.
2709 Some parameters have correspondent customizable variables, each of which
2710 is an alist of regexps and values.
2712 The following group parameters can be used:
2717 Address used by when doing followups and new posts.
2720 (to-address . "some@@where.com")
2723 This is primarily useful in mail groups that represent closed mailing
2724 lists---mailing lists where it's expected that everybody that writes to
2725 the mailing list is subscribed to it. Since using this parameter
2726 ensures that the mail only goes to the mailing list itself, it means
2727 that members won't receive two copies of your followups.
2729 Using @code{to-address} will actually work whether the group is foreign
2730 or not. Let's say there's a group on the server that is called
2731 @samp{fa.4ad-l}. This is a real newsgroup, but the server has gotten
2732 the articles from a mail-to-news gateway. Posting directly to this
2733 group is therefore impossible---you have to send mail to the mailing
2734 list address instead.
2736 See also @code{gnus-parameter-to-address-alist}.
2740 Address used when doing @kbd{a} in that group.
2743 (to-list . "some@@where.com")
2746 It is totally ignored
2747 when doing a followup---except that if it is present in a news group,
2748 you'll get mail group semantics when doing @kbd{f}.
2750 If you do an @kbd{a} command in a mail group and you have neither a
2751 @code{to-list} group parameter nor a @code{to-address} group parameter,
2752 then a @code{to-list} group parameter will be added automatically upon
2753 sending the message if @code{gnus-add-to-list} is set to @code{t}.
2754 @vindex gnus-add-to-list
2756 @findex gnus-mailing-list-mode
2757 @cindex mail list groups
2758 If this variable is set, @code{gnus-mailing-list-mode} is turned on when
2759 entering summary buffer.
2761 See also @code{gnus-parameter-to-list-alist}.
2766 @cindex Mail-Followup-To
2767 @findex gnus-find-subscribed-addresses
2768 If this parameter is set to @code{t}, Gnus will consider the
2769 to-address and to-list parameters for this group as addresses of
2770 mailing lists you are subscribed to. Giving Gnus this information is
2771 (only) a first step in getting it to generate correct Mail-Followup-To
2772 headers for your posts to these lists. The second step is to put the
2773 following in your @file{.gnus.el}
2776 (setq message-subscribed-address-functions
2777 '(gnus-find-subscribed-addresses))
2780 @xref{Mailing Lists, ,Mailing Lists, message, The Message Manual}, for
2781 a complete treatment of available MFT support.
2785 If the group parameter list has the element @code{(visible . t)},
2786 that group will always be visible in the Group buffer, regardless
2787 of whether it has any unread articles.
2789 @item broken-reply-to
2790 @cindex broken-reply-to
2791 Elements like @code{(broken-reply-to . t)} signals that @code{Reply-To}
2792 headers in this group are to be ignored, and for the header to be hidden
2793 if @code{reply-to} is part of @code{gnus-boring-article-headers}. This
2794 can be useful if you're reading a mailing list group where the listserv
2795 has inserted @code{Reply-To} headers that point back to the listserv
2796 itself. That is broken behavior. So there!
2800 Elements like @code{(to-group . "some.group.name")} means that all
2801 posts in that group will be sent to @code{some.group.name}.
2805 If you have @code{(newsgroup . t)} in the group parameter list, Gnus
2806 will treat all responses as if they were responses to news articles.
2807 This can be useful if you have a mail group that's really a mirror of a
2812 If @code{(gcc-self . t)} is present in the group parameter list, newly
2813 composed messages will be @code{Gcc}'d to the current group. If
2814 @code{(gcc-self . none)} is present, no @code{Gcc:} header will be
2815 generated, if @code{(gcc-self . "string")} is present, this string will
2816 be inserted literally as a @code{gcc} header. This parameter takes
2817 precedence over any default @code{Gcc} rules as described later
2818 (@pxref{Archived Messages}).
2820 @strong{Caveat}: Adding @code{(gcc-self . t)} to the parameter list of
2821 @code{nntp} groups (or the like) isn't valid. An @code{nntp} server
2822 doesn't accept articles.
2826 If the group parameter has an element that looks like @code{(auto-expire
2827 . t)}, all articles read will be marked as expirable. For an
2828 alternative approach, @pxref{Expiring Mail}.
2830 See also @code{gnus-auto-expirable-newsgroups}.
2833 @cindex total-expire
2834 If the group parameter has an element that looks like
2835 @code{(total-expire . t)}, all read articles will be put through the
2836 expiry process, even if they are not marked as expirable. Use with
2837 caution. Unread, ticked and dormant articles are not eligible for
2840 See also @code{gnus-total-expirable-newsgroups}.
2844 @vindex nnmail-expiry-wait-function
2845 If the group parameter has an element that looks like
2846 @code{(expiry-wait . 10)}, this value will override any
2847 @code{nnmail-expiry-wait} and @code{nnmail-expiry-wait-function}
2848 (@pxref{Expiring Mail}) when expiring expirable messages. The value
2849 can either be a number of days (not necessarily an integer) or the
2850 symbols @code{never} or @code{immediate}.
2853 @cindex expiry-target
2854 Where expired messages end up. This parameter overrides
2855 @code{nnmail-expiry-target}.
2858 @cindex score file group parameter
2859 Elements that look like @code{(score-file . "file")} will make
2860 @file{file} into the current score file for the group in question. All
2861 interactive score entries will be put into this file.
2864 @cindex adapt file group parameter
2865 Elements that look like @code{(adapt-file . "file")} will make
2866 @file{file} into the current adaptive file for the group in question.
2867 All adaptive score entries will be put into this file.
2870 @cindex admin-address
2871 When unsubscribing from a mailing list you should never send the
2872 unsubscription notice to the mailing list itself. Instead, you'd send
2873 messages to the administrative address. This parameter allows you to
2874 put the admin address somewhere convenient.
2878 Elements that look like @code{(display . MODE)} say which articles to
2879 display on entering the group. Valid values are:
2883 Display all articles, both read and unread.
2886 Display the last @var{integer} articles in the group. This is the same as
2887 entering the group with @kbd{C-u @var{integer}}.
2890 Display the default visible articles, which normally includes unread and
2894 Display articles that satisfy a predicate.
2896 Here are some examples:
2900 Display only unread articles.
2903 Display everything except expirable articles.
2905 @item [and (not reply) (not expire)]
2906 Display everything except expirable and articles you've already
2910 The available operators are @code{not}, @code{and} and @code{or}.
2911 Predicates include @code{tick}, @code{unsend}, @code{undownload},
2912 @code{unread}, @code{dormant}, @code{expire}, @code{reply},
2913 @code{killed}, @code{bookmark}, @code{score}, @code{save},
2914 @code{cache}, @code{forward}, @code{unseen} and @code{recent}.
2918 The @code{display} parameter works by limiting the summary buffer to
2919 the subset specified. You can pop the limit by using the @kbd{/ w}
2920 command (@pxref{Limiting}).
2924 Elements that look like @code{(comment . "This is a comment")} are
2925 arbitrary comments on the group. You can display comments in the
2926 group line (@pxref{Group Line Specification}).
2930 Elements that look like @code{(charset . iso-8859-1)} will make
2931 @code{iso-8859-1} the default charset; that is, the charset that will be
2932 used for all articles that do not specify a charset.
2934 See also @code{gnus-group-charset-alist}.
2936 @item ignored-charsets
2937 @cindex ignored-charset
2938 Elements that look like @code{(ignored-charsets x-unknown iso-8859-1)}
2939 will make @code{iso-8859-1} and @code{x-unknown} ignored; that is, the
2940 default charset will be used for decoding articles.
2942 See also @code{gnus-group-ignored-charsets-alist}.
2945 @cindex posting-style
2946 You can store additional posting style information for this group
2947 here (@pxref{Posting Styles}). The format is that of an entry in the
2948 @code{gnus-posting-styles} alist, except that there's no regexp matching
2949 the group name (of course). Style elements in this group parameter will
2950 take precedence over the ones found in @code{gnus-posting-styles}.
2952 For instance, if you want a funky name and signature in this group only,
2953 instead of hacking @code{gnus-posting-styles}, you could put something
2954 like this in the group parameters:
2959 ("X-My-Header" "Funky Value")
2960 (signature "Funky Signature"))
2965 If it is set, the value is used as the method for posting message
2966 instead of @code{gnus-post-method}.
2970 An item like @code{(banner . @var{regexp})} causes any part of an article
2971 that matches the regular expression @var{regexp} to be stripped. Instead of
2972 @var{regexp}, you can also use the symbol @code{signature} which strips the
2973 last signature or any of the elements of the alist
2974 @code{gnus-article-banner-alist}.
2978 This parameter contains a Sieve test that should match incoming mail
2979 that should be placed in this group. From this group parameter, a
2980 Sieve @samp{IF} control structure is generated, having the test as the
2981 condition and @samp{fileinto "group.name";} as the body.
2983 For example, if the @samp{INBOX.list.sieve} group has the @code{(sieve
2984 address "sender" "sieve-admin@@extundo.com")} group parameter, when
2985 translating the group parameter into a Sieve script (@pxref{Sieve
2986 Commands}) the following Sieve code is generated:
2989 if address "sender" "sieve-admin@@extundo.com" @{
2990 fileinto "INBOX.list.sieve";
2994 To generate tests for multiple email-addresses use a group parameter
2995 like @code{(sieve address "sender" ("name@@one.org" else@@two.org"))}.
2996 When generating a sieve script (@pxref{Sieve Commands}) Sieve code
2997 like the following is generated:
3000 if address "sender" ["name@@one.org", "else@@two.org"] @{
3001 fileinto "INBOX.list.sieve";
3005 See @pxref{Sieve Commands} for commands and variables that might be of
3006 interest in relation to the sieve parameter.
3008 The Sieve language is described in RFC 3028. @xref{Top, Emacs Sieve,
3009 Top, sieve, Emacs Sieve}.
3011 @item (agent parameters)
3012 If the agent has been enabled, you can set any of the its parameters
3013 to control the behavior of the agent in individual groups. See Agent
3014 Parameters in @ref{Category Syntax}. Most users will choose to set
3015 agent parameters in either an agent category or group topic to
3016 minimize the configuration effort.
3018 @item (@var{variable} @var{form})
3019 You can use the group parameters to set variables local to the group you
3020 are entering. If you want to turn threading off in @samp{news.answers},
3021 you could put @code{(gnus-show-threads nil)} in the group parameters of
3022 that group. @code{gnus-show-threads} will be made into a local variable
3023 in the summary buffer you enter, and the form @code{nil} will be
3024 @code{eval}ed there.
3026 Note that this feature sets the variable locally to the summary buffer.
3027 But some variables are evaluated in the article buffer, or in the
3028 message buffer (of a reply or followup or otherwise newly created
3029 message). As a workaround, it might help to add the variable in
3030 question to @code{gnus-newsgroup-variables}. @xref{Various Summary
3031 Stuff}. So if you want to set @code{message-from-style} via the group
3032 parameters, then you may need the following statement elsewhere in your
3033 @file{~/.gnus} file:
3036 (add-to-list 'gnus-newsgroup-variables 'message-from-style)
3039 @vindex gnus-list-identifiers
3040 A use for this feature is to remove a mailing list identifier tag in
3041 the subject fields of articles. E.g. if the news group
3044 nntp+news.gnus.org:gmane.text.docbook.apps
3047 has the tag @samp{DOC-BOOK-APPS:} in the subject of all articles, this
3048 tag can be removed from the article subjects in the summary buffer for
3049 the group by putting @code{(gnus-list-identifiers "DOCBOOK-APPS:")}
3050 into the group parameters for the group.
3052 This can also be used as a group-specific hook function. If you want to
3053 hear a beep when you enter a group, you could put something like
3054 @code{(dummy-variable (ding))} in the parameters of that group.
3055 @code{dummy-variable} will be set to the (meaningless) result of the
3058 Alternatively, since the VARIABLE becomes local to the group, this
3059 pattern can be used to temporarily change a hook. For example, if the
3060 following is added to a group parameter
3063 (gnus-summary-prepared-hook
3064 '(lambda nil (local-set-key "d" (local-key-binding "n"))))
3067 when the group is entered, the 'd' key will not mark the article as
3072 Use the @kbd{G p} or the @kbd{G c} command to edit group parameters of a
3073 group. (@kbd{G p} presents you with a Lisp-based interface, @kbd{G c}
3074 presents you with a Customize-like interface. The latter helps avoid
3075 silly Lisp errors.) You might also be interested in reading about topic
3076 parameters (@pxref{Topic Parameters}).
3078 @vindex gnus-parameters
3079 Group parameters can be set via the @code{gnus-parameters} variable too.
3080 But some variables, such as @code{visible}, have no effect. For
3084 (setq gnus-parameters
3086 (gnus-show-threads nil)
3087 (gnus-use-scoring nil)
3088 (gnus-summary-line-format
3089 "%U%R%z%I%(%[%d:%ub%-23,23f%]%) %s\n")
3093 ("^nnimap:\\(foo.bar\\)$"
3097 (gnus-use-scoring t))
3101 (broken-reply-to . t))))
3104 String value of parameters will be subjected to regexp substitution, as
3105 the @code{to-group} example shows.
3108 @node Listing Groups
3109 @section Listing Groups
3110 @cindex group listing
3112 These commands all list various slices of the groups available.
3120 @findex gnus-group-list-groups
3121 List all groups that have unread articles
3122 (@code{gnus-group-list-groups}). If the numeric prefix is used, this
3123 command will list only groups of level ARG and lower. By default, it
3124 only lists groups of level five (i.e.,
3125 @code{gnus-group-default-list-level}) or lower (i.e., just subscribed
3132 @findex gnus-group-list-all-groups
3133 List all groups, whether they have unread articles or not
3134 (@code{gnus-group-list-all-groups}). If the numeric prefix is used,
3135 this command will list only groups of level ARG and lower. By default,
3136 it lists groups of level seven or lower (i.e., just subscribed and
3137 unsubscribed groups).
3141 @findex gnus-group-list-level
3142 List all unread groups on a specific level
3143 (@code{gnus-group-list-level}). If given a prefix, also list the groups
3144 with no unread articles.
3148 @findex gnus-group-list-killed
3149 List all killed groups (@code{gnus-group-list-killed}). If given a
3150 prefix argument, really list all groups that are available, but aren't
3151 currently (un)subscribed. This could entail reading the active file
3156 @findex gnus-group-list-zombies
3157 List all zombie groups (@code{gnus-group-list-zombies}).
3161 @findex gnus-group-list-matching
3162 List all unread, subscribed groups with names that match a regexp
3163 (@code{gnus-group-list-matching}).
3167 @findex gnus-group-list-all-matching
3168 List groups that match a regexp (@code{gnus-group-list-all-matching}).
3172 @findex gnus-group-list-active
3173 List absolutely all groups in the active file(s) of the
3174 server(s) you are connected to (@code{gnus-group-list-active}). This
3175 might very well take quite a while. It might actually be a better idea
3176 to do a @kbd{A M} to list all matching, and just give @samp{.} as the
3177 thing to match on. Also note that this command may list groups that
3178 don't exist (yet)---these will be listed as if they were killed groups.
3179 Take the output with some grains of salt.
3183 @findex gnus-group-apropos
3184 List all groups that have names that match a regexp
3185 (@code{gnus-group-apropos}).
3189 @findex gnus-group-description-apropos
3190 List all groups that have names or descriptions that match a regexp
3191 (@code{gnus-group-description-apropos}).
3195 @findex gnus-group-list-cached
3196 List all groups with cached articles (@code{gnus-group-list-cached}).
3200 @findex gnus-group-list-dormant
3201 List all groups with dormant articles (@code{gnus-group-list-dormant}).
3205 @findex gnus-group-list-limit
3206 List groups limited within the current selection
3207 (@code{gnus-group-list-limit}).
3211 @findex gnus-group-list-flush
3212 Flush groups from the current selection (@code{gnus-group-list-flush}).
3216 @findex gnus-group-list-plus
3217 List groups plus the current selection (@code{gnus-group-list-plus}).
3221 @vindex gnus-permanently-visible-groups
3222 @cindex visible group parameter
3223 Groups that match the @code{gnus-permanently-visible-groups} regexp will
3224 always be shown, whether they have unread articles or not. You can also
3225 add the @code{visible} element to the group parameters in question to
3226 get the same effect.
3228 @vindex gnus-list-groups-with-ticked-articles
3229 Groups that have just ticked articles in it are normally listed in the
3230 group buffer. If @code{gnus-list-groups-with-ticked-articles} is
3231 @code{nil}, these groups will be treated just like totally empty
3232 groups. It is @code{t} by default.
3235 @node Sorting Groups
3236 @section Sorting Groups
3237 @cindex sorting groups
3239 @kindex C-c C-s (Group)
3240 @findex gnus-group-sort-groups
3241 @vindex gnus-group-sort-function
3242 The @kbd{C-c C-s} (@code{gnus-group-sort-groups}) command sorts the
3243 group buffer according to the function(s) given by the
3244 @code{gnus-group-sort-function} variable. Available sorting functions
3249 @item gnus-group-sort-by-alphabet
3250 @findex gnus-group-sort-by-alphabet
3251 Sort the group names alphabetically. This is the default.
3253 @item gnus-group-sort-by-real-name
3254 @findex gnus-group-sort-by-real-name
3255 Sort the group alphabetically on the real (unprefixed) group names.
3257 @item gnus-group-sort-by-level
3258 @findex gnus-group-sort-by-level
3259 Sort by group level.
3261 @item gnus-group-sort-by-score
3262 @findex gnus-group-sort-by-score
3263 Sort by group score. @xref{Group Score}.
3265 @item gnus-group-sort-by-rank
3266 @findex gnus-group-sort-by-rank
3267 Sort by group score and then the group level. The level and the score
3268 are, when taken together, the group's @dfn{rank}. @xref{Group Score}.
3270 @item gnus-group-sort-by-unread
3271 @findex gnus-group-sort-by-unread
3272 Sort by number of unread articles.
3274 @item gnus-group-sort-by-method
3275 @findex gnus-group-sort-by-method
3276 Sort alphabetically on the select method.
3278 @item gnus-group-sort-by-server
3279 @findex gnus-group-sort-by-server
3280 Sort alphabetically on the Gnus server name.
3285 @code{gnus-group-sort-function} can also be a list of sorting
3286 functions. In that case, the most significant sort key function must be
3290 There are also a number of commands for sorting directly according to
3291 some sorting criteria:
3295 @kindex G S a (Group)
3296 @findex gnus-group-sort-groups-by-alphabet
3297 Sort the group buffer alphabetically by group name
3298 (@code{gnus-group-sort-groups-by-alphabet}).
3301 @kindex G S u (Group)
3302 @findex gnus-group-sort-groups-by-unread
3303 Sort the group buffer by the number of unread articles
3304 (@code{gnus-group-sort-groups-by-unread}).
3307 @kindex G S l (Group)
3308 @findex gnus-group-sort-groups-by-level
3309 Sort the group buffer by group level
3310 (@code{gnus-group-sort-groups-by-level}).
3313 @kindex G S v (Group)
3314 @findex gnus-group-sort-groups-by-score
3315 Sort the group buffer by group score
3316 (@code{gnus-group-sort-groups-by-score}). @xref{Group Score}.
3319 @kindex G S r (Group)
3320 @findex gnus-group-sort-groups-by-rank
3321 Sort the group buffer by group rank
3322 (@code{gnus-group-sort-groups-by-rank}). @xref{Group Score}.
3325 @kindex G S m (Group)
3326 @findex gnus-group-sort-groups-by-method
3327 Sort the group buffer alphabetically by back end name@*
3328 (@code{gnus-group-sort-groups-by-method}).
3331 @kindex G S n (Group)
3332 @findex gnus-group-sort-groups-by-real-name
3333 Sort the group buffer alphabetically by real (unprefixed) group name
3334 (@code{gnus-group-sort-groups-by-real-name}).
3338 All the commands below obey the process/prefix convention
3339 (@pxref{Process/Prefix}).
3341 When given a symbolic prefix (@pxref{Symbolic Prefixes}), all these
3342 commands will sort in reverse order.
3344 You can also sort a subset of the groups:
3348 @kindex G P a (Group)
3349 @findex gnus-group-sort-selected-groups-by-alphabet
3350 Sort the groups alphabetically by group name
3351 (@code{gnus-group-sort-selected-groups-by-alphabet}).
3354 @kindex G P u (Group)
3355 @findex gnus-group-sort-selected-groups-by-unread
3356 Sort the groups by the number of unread articles
3357 (@code{gnus-group-sort-selected-groups-by-unread}).
3360 @kindex G P l (Group)
3361 @findex gnus-group-sort-selected-groups-by-level
3362 Sort the groups by group level
3363 (@code{gnus-group-sort-selected-groups-by-level}).
3366 @kindex G P v (Group)
3367 @findex gnus-group-sort-selected-groups-by-score
3368 Sort the groups by group score
3369 (@code{gnus-group-sort-selected-groups-by-score}). @xref{Group Score}.
3372 @kindex G P r (Group)
3373 @findex gnus-group-sort-selected-groups-by-rank
3374 Sort the groups by group rank
3375 (@code{gnus-group-sort-selected-groups-by-rank}). @xref{Group Score}.
3378 @kindex G P m (Group)
3379 @findex gnus-group-sort-selected-groups-by-method
3380 Sort the groups alphabetically by back end name@*
3381 (@code{gnus-group-sort-selected-groups-by-method}).
3384 @kindex G P n (Group)
3385 @findex gnus-group-sort-selected-groups-by-real-name
3386 Sort the groups alphabetically by real (unprefixed) group name
3387 (@code{gnus-group-sort-selected-groups-by-real-name}).
3390 @kindex G P s (Group)
3391 @findex gnus-group-sort-selected-groups
3392 Sort the groups according to @code{gnus-group-sort-function}.
3396 And finally, note that you can use @kbd{C-k} and @kbd{C-y} to manually
3400 @node Group Maintenance
3401 @section Group Maintenance
3402 @cindex bogus groups
3407 @findex gnus-group-check-bogus-groups
3408 Find bogus groups and delete them
3409 (@code{gnus-group-check-bogus-groups}).
3413 @findex gnus-group-find-new-groups
3414 Find new groups and process them (@code{gnus-group-find-new-groups}).
3415 With 1 @kbd{C-u}, use the @code{ask-server} method to query the server
3416 for new groups. With 2 @kbd{C-u}'s, use most complete method possible
3417 to query the server for new groups, and subscribe the new groups as
3421 @kindex C-c C-x (Group)
3422 @findex gnus-group-expire-articles
3423 Run all expirable articles in the current group through the expiry
3424 process (if any) (@code{gnus-group-expire-articles}). That is, delete
3425 all expirable articles in the group that have been around for a while.
3426 (@pxref{Expiring Mail}).
3429 @kindex C-c C-M-x (Group)
3430 @findex gnus-group-expire-all-groups
3431 Run all expirable articles in all groups through the expiry process
3432 (@code{gnus-group-expire-all-groups}).
3437 @node Browse Foreign Server
3438 @section Browse Foreign Server
3439 @cindex foreign servers
3440 @cindex browsing servers
3445 @findex gnus-group-browse-foreign-server
3446 You will be queried for a select method and a server name. Gnus will
3447 then attempt to contact this server and let you browse the groups there
3448 (@code{gnus-group-browse-foreign-server}).
3451 @findex gnus-browse-mode
3452 A new buffer with a list of available groups will appear. This buffer
3453 will use the @code{gnus-browse-mode}. This buffer looks a bit (well,
3454 a lot) like a normal group buffer.
3456 Here's a list of keystrokes available in the browse mode:
3461 @findex gnus-group-next-group
3462 Go to the next group (@code{gnus-group-next-group}).
3466 @findex gnus-group-prev-group
3467 Go to the previous group (@code{gnus-group-prev-group}).
3470 @kindex SPACE (Browse)
3471 @findex gnus-browse-read-group
3472 Enter the current group and display the first article
3473 (@code{gnus-browse-read-group}).
3476 @kindex RET (Browse)
3477 @findex gnus-browse-select-group
3478 Enter the current group (@code{gnus-browse-select-group}).
3482 @findex gnus-browse-unsubscribe-current-group
3483 Unsubscribe to the current group, or, as will be the case here,
3484 subscribe to it (@code{gnus-browse-unsubscribe-current-group}).
3490 @findex gnus-browse-exit
3491 Exit browse mode (@code{gnus-browse-exit}).
3495 @findex gnus-browse-describe-group
3496 Describe the current group (@code{gnus-browse-describe-group}).
3500 @findex gnus-browse-describe-briefly
3501 Describe browse mode briefly (well, there's not much to describe, is
3502 there) (@code{gnus-browse-describe-briefly}).
3507 @section Exiting Gnus
3508 @cindex exiting Gnus
3510 Yes, Gnus is ex(c)iting.
3515 @findex gnus-group-suspend
3516 Suspend Gnus (@code{gnus-group-suspend}). This doesn't really exit Gnus,
3517 but it kills all buffers except the Group buffer. I'm not sure why this
3518 is a gain, but then who am I to judge?
3522 @findex gnus-group-exit
3523 @c @icon{gnus-group-exit}
3524 Quit Gnus (@code{gnus-group-exit}).
3528 @findex gnus-group-quit
3529 Quit Gnus without saving the @file{.newsrc} files (@code{gnus-group-quit}).
3530 The dribble file will be saved, though (@pxref{Auto Save}).
3533 @vindex gnus-exit-gnus-hook
3534 @vindex gnus-suspend-gnus-hook
3535 @vindex gnus-after-exiting-gnus-hook
3536 @code{gnus-suspend-gnus-hook} is called when you suspend Gnus and
3537 @code{gnus-exit-gnus-hook} is called when you quit Gnus, while
3538 @code{gnus-after-exiting-gnus-hook} is called as the final item when
3544 Miss Lisa Cannifax, while sitting in English class, felt her feet go
3545 numbly heavy and herself fall into a hazy trance as the boy sitting
3546 behind her drew repeated lines with his pencil across the back of her
3552 @section Group Topics
3555 If you read lots and lots of groups, it might be convenient to group
3556 them hierarchically according to topics. You put your Emacs groups over
3557 here, your sex groups over there, and the rest (what, two groups or so?)
3558 you put in some misc section that you never bother with anyway. You can
3559 even group the Emacs sex groups as a sub-topic to either the Emacs
3560 groups or the sex groups---or both! Go wild!
3564 \gnusfigure{Group Topics}{400}{
3565 \put(75,50){\epsfig{figure=ps/group-topic,height=9cm}}
3576 2: alt.religion.emacs
3579 0: comp.talk.emacs.recovery
3581 8: comp.binaries.fractals
3582 13: comp.sources.unix
3585 @findex gnus-topic-mode
3587 To get this @emph{fab} functionality you simply turn on (ooh!) the
3588 @code{gnus-topic} minor mode---type @kbd{t} in the group buffer. (This
3589 is a toggling command.)
3591 Go ahead, just try it. I'll still be here when you get back. La de
3592 dum@dots{} Nice tune, that@dots{} la la la@dots{} What, you're back?
3593 Yes, and now press @kbd{l}. There. All your groups are now listed
3594 under @samp{misc}. Doesn't that make you feel all warm and fuzzy?
3597 If you want this permanently enabled, you should add that minor mode to
3598 the hook for the group mode. Put the following line in your
3599 @file{~/.gnus.el} file:
3602 (add-hook 'gnus-group-mode-hook 'gnus-topic-mode)
3606 * Topic Commands:: Interactive E-Z commands.
3607 * Topic Variables:: How to customize the topics the Lisp Way.
3608 * Topic Sorting:: Sorting each topic individually.
3609 * Topic Topology:: A map of the world.
3610 * Topic Parameters:: Parameters that apply to all groups in a topic.
3614 @node Topic Commands
3615 @subsection Topic Commands
3616 @cindex topic commands
3618 When the topic minor mode is turned on, a new @kbd{T} submap will be
3619 available. In addition, a few of the standard keys change their
3620 definitions slightly.
3622 In general, the following kinds of operations are possible on topics.
3623 First of all, you want to create topics. Secondly, you want to put
3624 groups in topics and to move them around until you have an order you
3625 like. The third kind of operation is to show/hide parts of the whole
3626 shebang. You might want to hide a topic including its subtopics and
3627 groups, to get a better overview of the other groups.
3629 Here is a list of the basic keys that you might need to set up topics
3636 @findex gnus-topic-create-topic
3637 Prompt for a new topic name and create it
3638 (@code{gnus-topic-create-topic}).
3642 @kindex T TAB (Topic)
3644 @findex gnus-topic-indent
3645 ``Indent'' the current topic so that it becomes a sub-topic of the
3646 previous topic (@code{gnus-topic-indent}). If given a prefix,
3647 ``un-indent'' the topic instead.
3650 @kindex M-TAB (Topic)
3651 @findex gnus-topic-unindent
3652 ``Un-indent'' the current topic so that it becomes a sub-topic of the
3653 parent of its current parent (@code{gnus-topic-unindent}).
3657 The following two keys can be used to move groups and topics around.
3658 They work like the well-known cut and paste. @kbd{C-k} is like cut and
3659 @kbd{C-y} is like paste. Of course, this being Emacs, we use the terms
3660 kill and yank rather than cut and paste.
3666 @findex gnus-topic-kill-group
3667 Kill a group or topic (@code{gnus-topic-kill-group}). All groups in the
3668 topic will be removed along with the topic.
3672 @findex gnus-topic-yank-group
3673 Yank the previously killed group or topic
3674 (@code{gnus-topic-yank-group}). Note that all topics will be yanked
3677 So, to move a topic to the beginning of the list of topics, just hit
3678 @kbd{C-k} on it. This is like the ``cut'' part of cut and paste. Then,
3679 move the cursor to the beginning of the buffer (just below the ``Gnus''
3680 topic) and hit @kbd{C-y}. This is like the ``paste'' part of cut and
3681 paste. Like I said -- E-Z.
3683 You can use @kbd{C-k} and @kbd{C-y} on groups as well as on topics. So
3684 you can move topics around as well as groups.
3688 After setting up the topics the way you like them, you might wish to
3689 hide a topic, or to show it again. That's why we have the following
3696 @findex gnus-topic-select-group
3698 Either select a group or fold a topic (@code{gnus-topic-select-group}).
3699 When you perform this command on a group, you'll enter the group, as
3700 usual. When done on a topic line, the topic will be folded (if it was
3701 visible) or unfolded (if it was folded already). So it's basically a
3702 toggling command on topics. In addition, if you give a numerical
3703 prefix, group on that level (and lower) will be displayed.
3707 Now for a list of other commands, in no particular order.
3713 @findex gnus-topic-move-group
3714 Move the current group to some other topic
3715 (@code{gnus-topic-move-group}). This command uses the process/prefix
3716 convention (@pxref{Process/Prefix}).
3720 @findex gnus-topic-jump-to-topic
3721 Go to a topic (@code{gnus-topic-jump-to-topic}).
3725 @findex gnus-topic-copy-group
3726 Copy the current group to some other topic
3727 (@code{gnus-topic-copy-group}). This command uses the process/prefix
3728 convention (@pxref{Process/Prefix}).
3732 @findex gnus-topic-hide-topic
3733 Hide the current topic (@code{gnus-topic-hide-topic}). If given
3734 a prefix, hide the topic permanently.
3738 @findex gnus-topic-show-topic
3739 Show the current topic (@code{gnus-topic-show-topic}). If given
3740 a prefix, show the topic permanently.
3744 @findex gnus-topic-remove-group
3745 Remove a group from the current topic (@code{gnus-topic-remove-group}).
3746 This command is mainly useful if you have the same group in several
3747 topics and wish to remove it from one of the topics. You may also
3748 remove a group from all topics, but in that case, Gnus will add it to
3749 the root topic the next time you start Gnus. In fact, all new groups
3750 (which, naturally, don't belong to any topic) will show up in the root
3753 This command uses the process/prefix convention
3754 (@pxref{Process/Prefix}).
3758 @findex gnus-topic-move-matching
3759 Move all groups that match some regular expression to a topic
3760 (@code{gnus-topic-move-matching}).
3764 @findex gnus-topic-copy-matching
3765 Copy all groups that match some regular expression to a topic
3766 (@code{gnus-topic-copy-matching}).
3770 @findex gnus-topic-toggle-display-empty-topics
3771 Toggle hiding empty topics
3772 (@code{gnus-topic-toggle-display-empty-topics}).
3776 @findex gnus-topic-mark-topic
3777 Mark all groups in the current topic with the process mark
3778 (@code{gnus-topic-mark-topic}). This command works recursively on
3779 sub-topics unless given a prefix.
3782 @kindex T M-# (Topic)
3783 @findex gnus-topic-unmark-topic
3784 Remove the process mark from all groups in the current topic
3785 (@code{gnus-topic-unmark-topic}). This command works recursively on
3786 sub-topics unless given a prefix.
3789 @kindex C-c C-x (Topic)
3790 @findex gnus-topic-expire-articles
3791 Run all expirable articles in the current group or topic through the
3792 expiry process (if any)
3793 (@code{gnus-topic-expire-articles}). (@pxref{Expiring Mail}).
3797 @findex gnus-topic-rename
3798 Rename a topic (@code{gnus-topic-rename}).
3801 @kindex T DEL (Topic)
3802 @findex gnus-topic-delete
3803 Delete an empty topic (@code{gnus-topic-delete}).
3807 @findex gnus-topic-list-active
3808 List all groups that Gnus knows about in a topics-ified way
3809 (@code{gnus-topic-list-active}).
3812 @kindex T M-n (Topic)
3813 @findex gnus-topic-goto-next-topic
3814 Go to the next topic (@code{gnus-topic-goto-next-topic}).
3817 @kindex T M-p (Topic)
3818 @findex gnus-topic-goto-previous-topic
3819 Go to the previous topic (@code{gnus-topic-goto-previous-topic}).
3823 @findex gnus-topic-edit-parameters
3824 @cindex group parameters
3825 @cindex topic parameters
3827 Edit the topic parameters (@code{gnus-topic-edit-parameters}).
3828 @xref{Topic Parameters}.
3833 @node Topic Variables
3834 @subsection Topic Variables
3835 @cindex topic variables
3837 The previous section told you how to tell Gnus which topics to display.
3838 This section explains how to tell Gnus what to display about each topic.
3840 @vindex gnus-topic-line-format
3841 The topic lines themselves are created according to the
3842 @code{gnus-topic-line-format} variable (@pxref{Formatting Variables}).
3855 Number of groups in the topic.
3857 Number of unread articles in the topic.
3859 Number of unread articles in the topic and all its subtopics.
3862 @vindex gnus-topic-indent-level
3863 Each sub-topic (and the groups in the sub-topics) will be indented with
3864 @code{gnus-topic-indent-level} times the topic level number of spaces.
3867 @vindex gnus-topic-mode-hook
3868 @code{gnus-topic-mode-hook} is called in topic minor mode buffers.
3870 @vindex gnus-topic-display-empty-topics
3871 The @code{gnus-topic-display-empty-topics} says whether to display even
3872 topics that have no unread articles in them. The default is @code{t}.
3876 @subsection Topic Sorting
3877 @cindex topic sorting
3879 You can sort the groups in each topic individually with the following
3885 @kindex T S a (Topic)
3886 @findex gnus-topic-sort-groups-by-alphabet
3887 Sort the current topic alphabetically by group name
3888 (@code{gnus-topic-sort-groups-by-alphabet}).
3891 @kindex T S u (Topic)
3892 @findex gnus-topic-sort-groups-by-unread
3893 Sort the current topic by the number of unread articles
3894 (@code{gnus-topic-sort-groups-by-unread}).
3897 @kindex T S l (Topic)
3898 @findex gnus-topic-sort-groups-by-level
3899 Sort the current topic by group level
3900 (@code{gnus-topic-sort-groups-by-level}).
3903 @kindex T S v (Topic)
3904 @findex gnus-topic-sort-groups-by-score
3905 Sort the current topic by group score
3906 (@code{gnus-topic-sort-groups-by-score}). @xref{Group Score}.
3909 @kindex T S r (Topic)
3910 @findex gnus-topic-sort-groups-by-rank
3911 Sort the current topic by group rank
3912 (@code{gnus-topic-sort-groups-by-rank}). @xref{Group Score}.
3915 @kindex T S m (Topic)
3916 @findex gnus-topic-sort-groups-by-method
3917 Sort the current topic alphabetically by back end name
3918 (@code{gnus-topic-sort-groups-by-method}).
3921 @kindex T S e (Topic)
3922 @findex gnus-topic-sort-groups-by-server
3923 Sort the current topic alphabetically by server name
3924 (@code{gnus-topic-sort-groups-by-server}).
3927 @kindex T S s (Topic)
3928 @findex gnus-topic-sort-groups
3929 Sort the current topic according to the function(s) given by the
3930 @code{gnus-group-sort-function} variable
3931 (@code{gnus-topic-sort-groups}).
3935 When given a prefix argument, all these commands will sort in reverse
3936 order. @xref{Sorting Groups}, for more information about group
3940 @node Topic Topology
3941 @subsection Topic Topology
3942 @cindex topic topology
3945 So, let's have a look at an example group buffer:
3952 2: alt.religion.emacs
3955 0: comp.talk.emacs.recovery
3957 8: comp.binaries.fractals
3958 13: comp.sources.unix
3962 So, here we have one top-level topic (@samp{Gnus}), two topics under
3963 that, and one sub-topic under one of the sub-topics. (There is always
3964 just one (1) top-level topic). This topology can be expressed as
3969 (("Emacs -- I wuw it!" visible)
3970 (("Naughty Emacs" visible)))
3974 @vindex gnus-topic-topology
3975 This is in fact how the variable @code{gnus-topic-topology} would look
3976 for the display above. That variable is saved in the @file{.newsrc.eld}
3977 file, and shouldn't be messed with manually---unless you really want
3978 to. Since this variable is read from the @file{.newsrc.eld} file,
3979 setting it in any other startup files will have no effect.
3981 This topology shows what topics are sub-topics of what topics (right),
3982 and which topics are visible. Two settings are currently
3983 allowed---@code{visible} and @code{invisible}.
3986 @node Topic Parameters
3987 @subsection Topic Parameters
3988 @cindex topic parameters
3990 All groups in a topic will inherit group parameters from the parent
3991 (and ancestor) topic parameters. All valid group parameters are valid
3992 topic parameters (@pxref{Group Parameters}). When the agent is
3993 enabled, all agent parameters (See Agent Parameters in @ref{Category
3994 Syntax}) are also valid topic parameters.
3996 In addition, the following parameters are only valid as topic
4001 When subscribing new groups by topic (@pxref{Subscription Methods}), the
4002 @code{subscribe} topic parameter says what groups go in what topic. Its
4003 value should be a regexp to match the groups that should go in that
4006 @item subscribe-level
4007 When subscribing new groups by topic (see the @code{subscribe} parameter),
4008 the group will be subscribed with the level specified in the
4009 @code{subscribe-level} instead of @code{gnus-level-default-subscribed}.
4013 Group parameters (of course) override topic parameters, and topic
4014 parameters in sub-topics override topic parameters in super-topics. You
4015 know. Normal inheritance rules. (@dfn{Rules} is here a noun, not a
4016 verb, although you may feel free to disagree with me here.)
4023 2: alt.religion.emacs
4027 0: comp.talk.emacs.recovery
4029 8: comp.binaries.fractals
4030 13: comp.sources.unix
4035 The @samp{Emacs} topic has the topic parameter @code{(score-file
4036 . "emacs.SCORE")}; the @samp{Relief} topic has the topic parameter
4037 @code{(score-file . "relief.SCORE")}; and the @samp{Misc} topic has the
4038 topic parameter @code{(score-file . "emacs.SCORE")}. In addition,
4039 @* @samp{alt.religion.emacs} has the group parameter @code{(score-file
4040 . "religion.SCORE")}.
4042 Now, when you enter @samp{alt.sex.emacs} in the @samp{Relief} topic, you
4043 will get the @file{relief.SCORE} home score file. If you enter the same
4044 group in the @samp{Emacs} topic, you'll get the @file{emacs.SCORE} home
4045 score file. If you enter the group @samp{alt.religion.emacs}, you'll
4046 get the @file{religion.SCORE} home score file.
4048 This seems rather simple and self-evident, doesn't it? Well, yes. But
4049 there are some problems, especially with the @code{total-expiry}
4050 parameter. Say you have a mail group in two topics; one with
4051 @code{total-expiry} and one without. What happens when you do @kbd{M-x
4052 gnus-expire-all-expirable-groups}? Gnus has no way of telling which one
4053 of these topics you mean to expire articles from, so anything may
4054 happen. In fact, I hereby declare that it is @dfn{undefined} what
4055 happens. You just have to be careful if you do stuff like that.
4058 @node Misc Group Stuff
4059 @section Misc Group Stuff
4062 * Scanning New Messages:: Asking Gnus to see whether new messages have arrived.
4063 * Group Information:: Information and help on groups and Gnus.
4064 * Group Timestamp:: Making Gnus keep track of when you last read a group.
4065 * File Commands:: Reading and writing the Gnus files.
4066 * Sieve Commands:: Managing Sieve scripts.
4073 @findex gnus-group-enter-server-mode
4074 Enter the server buffer (@code{gnus-group-enter-server-mode}).
4075 @xref{Server Buffer}.
4079 @findex gnus-group-post-news
4080 Start composing a message (a news by default)
4081 (@code{gnus-group-post-news}). If given a prefix, post to the group
4082 under the point. If the prefix is 1, prompt for a group to post to.
4083 Contrary to what the name of this function suggests, the prepared
4084 article might be a mail instead of a news, if a mail group is specified
4085 with the prefix argument. @xref{Composing Messages}.
4089 @findex gnus-group-mail
4090 Mail a message somewhere (@code{gnus-group-mail}). If given a prefix,
4091 use the posting style of the group under the point. If the prefix is 1,
4092 prompt for a group name to find the posting style.
4093 @xref{Composing Messages}.
4097 @findex gnus-group-news
4098 Start composing a news (@code{gnus-group-news}). If given a prefix,
4099 post to the group under the point. If the prefix is 1, prompt
4100 for group to post to. @xref{Composing Messages}.
4102 This function actually prepares a news even when using mail groups.
4103 This is useful for ``posting'' messages to mail groups without actually
4104 sending them over the network: they're just saved directly to the group
4105 in question. The corresponding back end must have a request-post method
4106 for this to work though.
4110 Variables for the group buffer:
4114 @item gnus-group-mode-hook
4115 @vindex gnus-group-mode-hook
4116 is called after the group buffer has been
4119 @item gnus-group-prepare-hook
4120 @vindex gnus-group-prepare-hook
4121 is called after the group buffer is
4122 generated. It may be used to modify the buffer in some strange,
4125 @item gnus-group-prepared-hook
4126 @vindex gnus-group-prepare-hook
4127 is called as the very last thing after the group buffer has been
4128 generated. It may be used to move point around, for instance.
4130 @item gnus-permanently-visible-groups
4131 @vindex gnus-permanently-visible-groups
4132 Groups matching this regexp will always be listed in the group buffer,
4133 whether they are empty or not.
4135 @item gnus-group-name-charset-method-alist
4136 @vindex gnus-group-name-charset-method-alist
4137 An alist of method and the charset for group names. It is used to show
4138 non-@acronym{ASCII} group names.
4142 (setq gnus-group-name-charset-method-alist
4143 '(((nntp "news.com.cn") . cn-gb-2312)))
4146 @item gnus-group-name-charset-group-alist
4147 @cindex UTF-8 group names
4148 @vindex gnus-group-name-charset-group-alist
4149 An alist of regexp of group name and the charset for group names. It
4150 is used to show non-@acronym{ASCII} group names. @code{((".*"
4151 utf-8))} is the default value if UTF-8 is supported, otherwise the
4152 default is @code{nil}.
4156 (setq gnus-group-name-charset-group-alist
4157 '(("\\.com\\.cn:" . cn-gb-2312)))
4162 @node Scanning New Messages
4163 @subsection Scanning New Messages
4164 @cindex new messages
4165 @cindex scanning new news
4171 @findex gnus-group-get-new-news
4172 @c @icon{gnus-group-get-new-news}
4173 Check the server(s) for new articles. If the numerical prefix is used,
4174 this command will check only groups of level @var{arg} and lower
4175 (@code{gnus-group-get-new-news}). If given a non-numerical prefix, this
4176 command will force a total re-reading of the active file(s) from the
4181 @findex gnus-group-get-new-news-this-group
4182 @vindex gnus-goto-next-group-when-activating
4183 @c @icon{gnus-group-get-new-news-this-group}
4184 Check whether new articles have arrived in the current group
4185 (@code{gnus-group-get-new-news-this-group}).
4186 @code{gnus-goto-next-group-when-activating} says whether this command is
4187 to move point to the next group or not. It is @code{t} by default.
4189 @findex gnus-activate-all-groups
4190 @cindex activating groups
4192 @kindex C-c M-g (Group)
4193 Activate absolutely all groups (@code{gnus-activate-all-groups}).
4198 @findex gnus-group-restart
4199 Restart Gnus (@code{gnus-group-restart}). This saves the @file{.newsrc}
4200 file(s), closes the connection to all servers, clears up all run-time
4201 Gnus variables, and then starts Gnus all over again.
4205 @vindex gnus-get-new-news-hook
4206 @code{gnus-get-new-news-hook} is run just before checking for new news.
4208 @vindex gnus-after-getting-new-news-hook
4209 @code{gnus-after-getting-new-news-hook} is run after checking for new
4213 @node Group Information
4214 @subsection Group Information
4215 @cindex group information
4216 @cindex information on groups
4223 @findex gnus-group-fetch-faq
4224 @vindex gnus-group-faq-directory
4227 Try to fetch the @acronym{FAQ} for the current group
4228 (@code{gnus-group-fetch-faq}). Gnus will try to get the @acronym{FAQ}
4229 from @code{gnus-group-faq-directory}, which is usually a directory on
4230 a remote machine. This variable can also be a list of directories.
4231 In that case, giving a prefix to this command will allow you to choose
4232 between the various sites. @code{ange-ftp} (or @code{efs}) will be
4233 used for fetching the file.
4235 If fetching from the first site is unsuccessful, Gnus will attempt to go
4236 through @code{gnus-group-faq-directory} and try to open them one by one.
4240 @findex gnus-group-fetch-charter
4241 @vindex gnus-group-charter-alist
4243 Try to open the charter for the current group in a web browser
4244 (@code{gnus-group-fetch-charter}). Query for a group if given a
4247 Gnus will use @code{gnus-group-charter-alist} to find the location of
4248 the charter. If no location is known, Gnus will fetch the control
4249 messages for the group, which in some cases includes the charter.
4253 @findex gnus-group-fetch-control
4254 @vindex gnus-group-fetch-control-use-browse-url
4255 @cindex control message
4256 Fetch the control messages for the group from the archive at
4257 @code{ftp.isc.org} (@code{gnus-group-fetch-control}). Query for a
4258 group if given a prefix argument.
4260 If @code{gnus-group-fetch-control-use-browse-url} is non-@code{nil},
4261 Gnus will open the control messages in a browser using
4262 @code{browse-url}. Otherwise they are fetched using @code{ange-ftp}
4263 and displayed in an ephemeral group.
4265 Note that the control messages are compressed. To use this command
4266 you need to turn on @code{auto-compression-mode} (@pxref{Compressed
4267 Files, ,Compressed Files, emacs, The Emacs Manual}).
4271 @c @icon{gnus-group-describe-group}
4273 @kindex C-c C-d (Group)
4274 @cindex describing groups
4275 @cindex group description
4276 @findex gnus-group-describe-group
4277 Describe the current group (@code{gnus-group-describe-group}). If given
4278 a prefix, force Gnus to re-read the description from the server.
4282 @findex gnus-group-describe-all-groups
4283 Describe all groups (@code{gnus-group-describe-all-groups}). If given a
4284 prefix, force Gnus to re-read the description file from the server.
4291 @findex gnus-version
4292 Display current Gnus version numbers (@code{gnus-version}).
4296 @findex gnus-group-describe-briefly
4297 Give a very short help message (@code{gnus-group-describe-briefly}).
4300 @kindex C-c C-i (Group)
4303 @findex gnus-info-find-node
4304 Go to the Gnus info node (@code{gnus-info-find-node}).
4308 @node Group Timestamp
4309 @subsection Group Timestamp
4311 @cindex group timestamps
4313 It can be convenient to let Gnus keep track of when you last read a
4314 group. To set the ball rolling, you should add
4315 @code{gnus-group-set-timestamp} to @code{gnus-select-group-hook}:
4318 (add-hook 'gnus-select-group-hook 'gnus-group-set-timestamp)
4321 After doing this, each time you enter a group, it'll be recorded.
4323 This information can be displayed in various ways---the easiest is to
4324 use the @samp{%d} spec in the group line format:
4327 (setq gnus-group-line-format
4328 "%M\%S\%p\%P\%5y: %(%-40,40g%) %d\n")
4331 This will result in lines looking like:
4334 * 0: mail.ding 19961002T012943
4335 0: custom 19961002T012713
4338 As you can see, the date is displayed in compact ISO 8601 format. This
4339 may be a bit too much, so to just display the date, you could say
4343 (setq gnus-group-line-format
4344 "%M\%S\%p\%P\%5y: %(%-40,40g%) %6,6~(cut 2)d\n")
4347 If you would like greater control of the time format, you can use a
4348 user-defined format spec. Something like the following should do the
4352 (setq gnus-group-line-format
4353 "%M\%S\%p\%P\%5y: %(%-40,40g%) %ud\n")
4354 (defun gnus-user-format-function-d (headers)
4355 (let ((time (gnus-group-timestamp gnus-tmp-group)))
4357 (format-time-string "%b %d %H:%M" time)
4363 @subsection File Commands
4364 @cindex file commands
4370 @findex gnus-group-read-init-file
4371 @vindex gnus-init-file
4372 @cindex reading init file
4373 Re-read the init file (@code{gnus-init-file}, which defaults to
4374 @file{~/.gnus.el}) (@code{gnus-group-read-init-file}).
4378 @findex gnus-group-save-newsrc
4379 @cindex saving .newsrc
4380 Save the @file{.newsrc.eld} file (and @file{.newsrc} if wanted)
4381 (@code{gnus-group-save-newsrc}). If given a prefix, force saving the
4382 file(s) whether Gnus thinks it is necessary or not.
4385 @c @kindex Z (Group)
4386 @c @findex gnus-group-clear-dribble
4387 @c Clear the dribble buffer (@code{gnus-group-clear-dribble}).
4392 @node Sieve Commands
4393 @subsection Sieve Commands
4394 @cindex group sieve commands
4396 Sieve is a server-side mail filtering language. In Gnus you can use
4397 the @code{sieve} group parameter (@pxref{Group Parameters}) to specify
4398 sieve rules that should apply to each group. Gnus provides two
4399 commands to translate all these group parameters into a proper Sieve
4400 script that can be transfered to the server somehow.
4402 @vindex gnus-sieve-file
4403 @vindex gnus-sieve-region-start
4404 @vindex gnus-sieve-region-end
4405 The generated Sieve script is placed in @code{gnus-sieve-file} (by
4406 default @file{~/.sieve}). The Sieve code that Gnus generate is placed
4407 between two delimiters, @code{gnus-sieve-region-start} and
4408 @code{gnus-sieve-region-end}, so you may write additional Sieve code
4409 outside these delimiters that will not be removed the next time you
4410 regenerate the Sieve script.
4412 @vindex gnus-sieve-crosspost
4413 The variable @code{gnus-sieve-crosspost} controls how the Sieve script
4414 is generated. If it is non-@code{nil} (the default) articles is
4415 placed in all groups that have matching rules, otherwise the article
4416 is only placed in the group with the first matching rule. For
4417 example, the group parameter @samp{(sieve address "sender"
4418 "owner-ding@@hpc.uh.edu")} will generate the following piece of Sieve
4419 code if @code{gnus-sieve-crosspost} is @code{nil}. (When
4420 @code{gnus-sieve-crosspost} is non-@code{nil}, it looks the same
4421 except that the line containing the call to @code{stop} is removed.)
4424 if address "sender" "owner-ding@@hpc.uh.edu" @{
4425 fileinto "INBOX.ding";
4430 @xref{Top, Emacs Sieve, Top, sieve, Emacs Sieve}.
4436 @findex gnus-sieve-generate
4437 @vindex gnus-sieve-file
4438 @cindex generating sieve script
4439 Regenerate a Sieve script from the @code{sieve} group parameters and
4440 put you into the @code{gnus-sieve-file} without saving it.
4444 @findex gnus-sieve-update
4445 @vindex gnus-sieve-file
4446 @cindex updating sieve script
4447 Regenerates the Gnus managed part of @code{gnus-sieve-file} using the
4448 @code{sieve} group parameters, save the file and upload it to the
4449 server using the @code{sieveshell} program.
4454 @node Summary Buffer
4455 @chapter Summary Buffer
4456 @cindex summary buffer
4458 A line for each article is displayed in the summary buffer. You can
4459 move around, read articles, post articles and reply to articles.
4461 The most common way to a summary buffer is to select a group from the
4462 group buffer (@pxref{Selecting a Group}).
4464 You can have as many summary buffers open as you wish.
4467 * Summary Buffer Format:: Deciding how the summary buffer is to look.
4468 * Summary Maneuvering:: Moving around the summary buffer.
4469 * Choosing Articles:: Reading articles.
4470 * Paging the Article:: Scrolling the current article.
4471 * Reply Followup and Post:: Posting articles.
4472 * Delayed Articles:: Send articles at a later time.
4473 * Marking Articles:: Marking articles as read, expirable, etc.
4474 * Limiting:: You can limit the summary buffer.
4475 * Threading:: How threads are made.
4476 * Sorting the Summary Buffer:: How articles and threads are sorted.
4477 * Asynchronous Fetching:: Gnus might be able to pre-fetch articles.
4478 * Article Caching:: You may store articles in a cache.
4479 * Persistent Articles:: Making articles expiry-resistant.
4480 * Article Backlog:: Having already read articles hang around.
4481 * Saving Articles:: Ways of customizing article saving.
4482 * Decoding Articles:: Gnus can treat series of (uu)encoded articles.
4483 * Article Treatment:: The article buffer can be mangled at will.
4484 * MIME Commands:: Doing MIMEy things with the articles.
4485 * Charsets:: Character set issues.
4486 * Article Commands:: Doing various things with the article buffer.
4487 * Summary Sorting:: Sorting the summary buffer in various ways.
4488 * Finding the Parent:: No child support? Get the parent.
4489 * Alternative Approaches:: Reading using non-default summaries.
4490 * Tree Display:: A more visual display of threads.
4491 * Mail Group Commands:: Some commands can only be used in mail groups.
4492 * Various Summary Stuff:: What didn't fit anywhere else.
4493 * Exiting the Summary Buffer:: Returning to the Group buffer,
4494 or reselecting the current group.
4495 * Crosspost Handling:: How crossposted articles are dealt with.
4496 * Duplicate Suppression:: An alternative when crosspost handling fails.
4497 * Security:: Decrypt and Verify.
4498 * Mailing List:: Mailing list minor mode.
4502 @node Summary Buffer Format
4503 @section Summary Buffer Format
4504 @cindex summary buffer format
4508 \gnusfigure{The Summary Buffer}{180}{
4509 \put(0,0){\epsfig{figure=ps/summary,width=7.5cm}}
4510 \put(445,0){\makebox(0,0)[br]{\epsfig{figure=ps/summary-article,width=7.5cm}}}
4516 * Summary Buffer Lines:: You can specify how summary lines should look.
4517 * To From Newsgroups:: How to not display your own name.
4518 * Summary Buffer Mode Line:: You can say how the mode line should look.
4519 * Summary Highlighting:: Making the summary buffer all pretty and nice.
4522 @findex mail-extract-address-components
4523 @findex gnus-extract-address-components
4524 @vindex gnus-extract-address-components
4525 Gnus will use the value of the @code{gnus-extract-address-components}
4526 variable as a function for getting the name and address parts of a
4527 @code{From} header. Two pre-defined functions exist:
4528 @code{gnus-extract-address-components}, which is the default, quite
4529 fast, and too simplistic solution; and
4530 @code{mail-extract-address-components}, which works very nicely, but is
4531 slower. The default function will return the wrong answer in 5% of the
4532 cases. If this is unacceptable to you, use the other function instead:
4535 (setq gnus-extract-address-components
4536 'mail-extract-address-components)
4539 @vindex gnus-summary-same-subject
4540 @code{gnus-summary-same-subject} is a string indicating that the current
4541 article has the same subject as the previous. This string will be used
4542 with those specs that require it. The default is @code{""}.
4545 @node Summary Buffer Lines
4546 @subsection Summary Buffer Lines
4548 @vindex gnus-summary-line-format
4549 You can change the format of the lines in the summary buffer by changing
4550 the @code{gnus-summary-line-format} variable. It works along the same
4551 lines as a normal @code{format} string, with some extensions
4552 (@pxref{Formatting Variables}).
4554 There should always be a colon or a point position marker on the line;
4555 the cursor always moves to the point position marker or the colon after
4556 performing an operation. (Of course, Gnus wouldn't be Gnus if it wasn't
4557 possible to change this. Just write a new function
4558 @code{gnus-goto-colon} which does whatever you like with the cursor.)
4559 @xref{Positioning Point}.
4561 The default string is @samp{%U%R%z%I%(%[%4L: %-23,23f%]%) %s\n}.
4563 The following format specification characters and extended format
4564 specification(s) are understood:
4570 Subject string. List identifiers stripped,
4571 @code{gnus-list-identifies}. @xref{Article Hiding}.
4573 Subject if the article is the root of the thread or the previous article
4574 had a different subject, @code{gnus-summary-same-subject} otherwise.
4575 (@code{gnus-summary-same-subject} defaults to @code{""}.)
4577 Full @code{From} header.
4579 The name (from the @code{From} header).
4581 The name, @code{To} header or the @code{Newsgroups} header (@pxref{To
4584 The name (from the @code{From} header). This differs from the @code{n}
4585 spec in that it uses the function designated by the
4586 @code{gnus-extract-address-components} variable, which is slower, but
4587 may be more thorough.
4589 The address (from the @code{From} header). This works the same way as
4592 Number of lines in the article.
4594 Number of characters in the article. This specifier is not supported
4595 in some methods (like nnfolder).
4597 Pretty-printed version of the number of characters in the article;
4598 for example, @samp{1.2k} or @samp{0.4M}.
4600 Indentation based on thread level (@pxref{Customizing Threading}).
4602 A complex trn-style thread tree, showing response-connecting trace
4603 lines. A thread could be drawn like this:
4616 You can customize the appearance with the following options. Note
4617 that it is possible to make the thread display look really neat by
4618 replacing the default @acronym{ASCII} characters with graphic
4619 line-drawing glyphs.
4621 @item gnus-sum-thread-tree-root
4622 @vindex gnus-sum-thread-tree-root
4623 Used for the root of a thread. If @code{nil}, use subject
4624 instead. The default is @samp{> }.
4626 @item gnus-sum-thread-tree-false-root
4627 @vindex gnus-sum-thread-tree-false-root
4628 Used for the false root of a thread (@pxref{Loose Threads}). If
4629 @code{nil}, use subject instead. The default is @samp{> }.
4631 @item gnus-sum-thread-tree-single-indent
4632 @vindex gnus-sum-thread-tree-single-indent
4633 Used for a thread with just one message. If @code{nil}, use subject
4634 instead. The default is @samp{}.
4636 @item gnus-sum-thread-tree-vertical
4637 @vindex gnus-sum-thread-tree-vertical
4638 Used for drawing a vertical line. The default is @samp{| }.
4640 @item gnus-sum-thread-tree-indent
4641 @vindex gnus-sum-thread-tree-indent
4642 Used for indenting. The default is @samp{ }.
4644 @item gnus-sum-thread-tree-leaf-with-other
4645 @vindex gnus-sum-thread-tree-leaf-with-other
4646 Used for a leaf with brothers. The default is @samp{+-> }.
4648 @item gnus-sum-thread-tree-single-leaf
4649 @vindex gnus-sum-thread-tree-single-leaf
4650 Used for a leaf without brothers. The default is @samp{\-> }
4655 Nothing if the article is a root and lots of spaces if it isn't (it
4656 pushes everything after it off the screen).
4658 Opening bracket, which is normally @samp{[}, but can also be @samp{<}
4659 for adopted articles (@pxref{Customizing Threading}).
4661 Closing bracket, which is normally @samp{]}, but can also be @samp{>}
4662 for adopted articles.
4664 One space for each thread level.
4666 Twenty minus thread level spaces.
4668 Unread. @xref{Read Articles}.
4671 This misleadingly named specifier is the @dfn{secondary mark}. This
4672 mark will say whether the article has been replied to, has been cached,
4673 or has been saved. @xref{Other Marks}.
4676 Score as a number (@pxref{Scoring}).
4678 @vindex gnus-summary-zcore-fuzz
4679 Zcore, @samp{+} if above the default level and @samp{-} if below the
4680 default level. If the difference between
4681 @code{gnus-summary-default-score} and the score is less than
4682 @code{gnus-summary-zcore-fuzz}, this spec will not be used.
4690 The @code{Date} in @code{DD-MMM} format.
4692 The @code{Date} in @var{YYYYMMDD}@code{T}@var{HHMMSS} format.
4698 Number of articles in the current sub-thread. Using this spec will slow
4699 down summary buffer generation somewhat.
4701 An @samp{=} (@code{gnus-not-empty-thread-mark}) will be displayed if the
4702 article has any children.
4708 Age sensitive date format. Various date format is defined in
4709 @code{gnus-user-date-format-alist}.
4711 User defined specifier. The next character in the format string should
4712 be a letter. Gnus will call the function
4713 @code{gnus-user-format-function-@var{x}}, where @var{x} is the letter
4714 following @samp{%u}. The function will be passed the current header as
4715 argument. The function should return a string, which will be inserted
4716 into the summary just like information from any other summary specifier.
4719 Text between @samp{%(} and @samp{%)} will be highlighted with
4720 @code{gnus-mouse-face} when the mouse point is placed inside the area.
4721 There can only be one such area.
4723 The @samp{%U} (status), @samp{%R} (replied) and @samp{%z} (zcore) specs
4724 have to be handled with care. For reasons of efficiency, Gnus will
4725 compute what column these characters will end up in, and ``hard-code''
4726 that. This means that it is invalid to have these specs after a
4727 variable-length spec. Well, you might not be arrested, but your summary
4728 buffer will look strange, which is bad enough.
4730 The smart choice is to have these specs as far to the left as possible.
4731 (Isn't that the case with everything, though? But I digress.)
4733 This restriction may disappear in later versions of Gnus.
4736 @node To From Newsgroups
4737 @subsection To From Newsgroups
4741 In some groups (particularly in archive groups), the @code{From} header
4742 isn't very interesting, since all the articles there are written by
4743 you. To display the information in the @code{To} or @code{Newsgroups}
4744 headers instead, you need to decide three things: What information to
4745 gather; where to display it; and when to display it.
4749 @vindex gnus-extra-headers
4750 The reading of extra header information is controlled by the
4751 @code{gnus-extra-headers}. This is a list of header symbols. For
4755 (setq gnus-extra-headers
4756 '(To Newsgroups X-Newsreader))
4759 This will result in Gnus trying to obtain these three headers, and
4760 storing it in header structures for later easy retrieval.
4763 @findex gnus-extra-header
4764 The value of these extra headers can be accessed via the
4765 @code{gnus-extra-header} function. Here's a format line spec that will
4766 access the @code{X-Newsreader} header:
4769 "%~(form (gnus-extra-header 'X-Newsreader))@@"
4773 @vindex gnus-ignored-from-addresses
4774 The @code{gnus-ignored-from-addresses} variable says when the @samp{%f}
4775 summary line spec returns the @code{To}, @code{Newsreader} or
4776 @code{From} header. If this regexp matches the contents of the
4777 @code{From} header, the value of the @code{To} or @code{Newsreader}
4778 headers are used instead.
4780 To distinguish regular articles from those where the @code{From} field
4781 has been swapped, a string is prefixed to the @code{To} or
4782 @code{Newsgroups} header in the summary line. By default the string is
4783 @samp{-> } for @code{To} and @samp{=> } for @code{Newsgroups}, you can
4784 customize these strings with @code{gnus-summary-to-prefix} and
4785 @code{gnus-summary-newsgroup-prefix}.
4789 @vindex nnmail-extra-headers
4790 A related variable is @code{nnmail-extra-headers}, which controls when
4791 to include extra headers when generating overview (@acronym{NOV}) files.
4792 If you have old overview files, you should regenerate them after
4793 changing this variable, by entering the server buffer using @kbd{^},
4794 and then @kbd{g} on the appropriate mail server (e.g. nnml) to cause
4797 @vindex gnus-summary-line-format
4798 You also have to instruct Gnus to display the data by changing the
4799 @code{%n} spec to the @code{%f} spec in the
4800 @code{gnus-summary-line-format} variable.
4802 In summary, you'd typically put something like the following in
4806 (setq gnus-extra-headers
4808 (setq nnmail-extra-headers gnus-extra-headers)
4809 (setq gnus-summary-line-format
4810 "%U%R%z%I%(%[%4L: %-23,23f%]%) %s\n")
4811 (setq gnus-ignored-from-addresses
4815 (The values listed above are the default values in Gnus. Alter them
4818 A note for news server administrators, or for users who wish to try to
4819 convince their news server administrator to provide some additional
4822 The above is mostly useful for mail groups, where you have control over
4823 the @acronym{NOV} files that are created. However, if you can persuade your
4824 nntp admin to add (in the usual implementation, notably INN):
4830 to the end of her @file{overview.fmt} file, then you can use that just
4831 as you would the extra headers from the mail groups.
4834 @node Summary Buffer Mode Line
4835 @subsection Summary Buffer Mode Line
4837 @vindex gnus-summary-mode-line-format
4838 You can also change the format of the summary mode bar (@pxref{Mode Line
4839 Formatting}). Set @code{gnus-summary-mode-line-format} to whatever you
4840 like. The default is @samp{Gnus: %%b [%A] %Z}.
4842 Here are the elements you can play with:
4848 Unprefixed group name.
4850 Current article number.
4852 Current article score.
4856 Number of unread articles in this group.
4858 Number of unread articles in this group that aren't displayed in the
4861 A string with the number of unread and unselected articles represented
4862 either as @samp{<%U(+%e) more>} if there are both unread and unselected
4863 articles, and just as @samp{<%U more>} if there are just unread articles
4864 and no unselected ones.
4866 Shortish group name. For instance, @samp{rec.arts.anime} will be
4867 shortened to @samp{r.a.anime}.
4869 Subject of the current article.
4871 User-defined spec (@pxref{User-Defined Specs}).
4873 Name of the current score file (@pxref{Scoring}).
4875 Number of dormant articles (@pxref{Unread Articles}).
4877 Number of ticked articles (@pxref{Unread Articles}).
4879 Number of articles that have been marked as read in this session.
4881 Number of articles expunged by the score files.
4885 @node Summary Highlighting
4886 @subsection Summary Highlighting
4890 @item gnus-visual-mark-article-hook
4891 @vindex gnus-visual-mark-article-hook
4892 This hook is run after selecting an article. It is meant to be used for
4893 highlighting the article in some way. It is not run if
4894 @code{gnus-visual} is @code{nil}.
4896 @item gnus-summary-update-hook
4897 @vindex gnus-summary-update-hook
4898 This hook is called when a summary line is changed. It is not run if
4899 @code{gnus-visual} is @code{nil}.
4901 @item gnus-summary-selected-face
4902 @vindex gnus-summary-selected-face
4903 This is the face (or @dfn{font} as some people call it) used to
4904 highlight the current article in the summary buffer.
4906 @item gnus-summary-highlight
4907 @vindex gnus-summary-highlight
4908 Summary lines are highlighted according to this variable, which is a
4909 list where the elements are of the format @code{(@var{form}
4910 . @var{face})}. If you would, for instance, like ticked articles to be
4911 italic and high-scored articles to be bold, you could set this variable
4914 (((eq mark gnus-ticked-mark) . italic)
4915 ((> score default) . bold))
4917 As you may have guessed, if @var{form} returns a non-@code{nil} value,
4918 @var{face} will be applied to the line.
4922 @node Summary Maneuvering
4923 @section Summary Maneuvering
4924 @cindex summary movement
4926 All the straight movement commands understand the numeric prefix and
4927 behave pretty much as you'd expect.
4929 None of these commands select articles.
4934 @kindex M-n (Summary)
4935 @kindex G M-n (Summary)
4936 @findex gnus-summary-next-unread-subject
4937 Go to the next summary line of an unread article
4938 (@code{gnus-summary-next-unread-subject}).
4942 @kindex M-p (Summary)
4943 @kindex G M-p (Summary)
4944 @findex gnus-summary-prev-unread-subject
4945 Go to the previous summary line of an unread article
4946 (@code{gnus-summary-prev-unread-subject}).
4949 @kindex G g (Summary)
4950 @findex gnus-summary-goto-subject
4951 Ask for an article number and then go to the summary line of that article
4952 without displaying the article (@code{gnus-summary-goto-subject}).
4955 If Gnus asks you to press a key to confirm going to the next group, you
4956 can use the @kbd{C-n} and @kbd{C-p} keys to move around the group
4957 buffer, searching for the next group to read without actually returning
4958 to the group buffer.
4960 Variables related to summary movement:
4964 @vindex gnus-auto-select-next
4965 @item gnus-auto-select-next
4966 If you issue one of the movement commands (like @kbd{n}) and there are
4967 no more unread articles after the current one, Gnus will offer to go to
4968 the next group. If this variable is @code{t} and the next group is
4969 empty, Gnus will exit summary mode and return to the group buffer. If
4970 this variable is neither @code{t} nor @code{nil}, Gnus will select the
4971 next group with unread articles. As a special case, if this variable
4972 is @code{quietly}, Gnus will select the next group without asking for
4973 confirmation. If this variable is @code{almost-quietly}, the same
4974 will happen only if you are located on the last article in the group.
4975 Finally, if this variable is @code{slightly-quietly}, the @kbd{Z n}
4976 command will go to the next group without confirmation. Also
4977 @pxref{Group Levels}.
4979 @item gnus-auto-select-same
4980 @vindex gnus-auto-select-same
4981 If non-@code{nil}, all the movement commands will try to go to the next
4982 article with the same subject as the current. (@dfn{Same} here might
4983 mean @dfn{roughly equal}. See @code{gnus-summary-gather-subject-limit}
4984 for details (@pxref{Customizing Threading}).) If there are no more
4985 articles with the same subject, go to the first unread article.
4987 This variable is not particularly useful if you use a threaded display.
4989 @item gnus-summary-check-current
4990 @vindex gnus-summary-check-current
4991 If non-@code{nil}, all the ``unread'' movement commands will not proceed
4992 to the next (or previous) article if the current article is unread.
4993 Instead, they will choose the current article.
4995 @item gnus-auto-center-summary
4996 @vindex gnus-auto-center-summary
4997 If non-@code{nil}, Gnus will keep the point in the summary buffer
4998 centered at all times. This makes things quite tidy, but if you have a
4999 slow network connection, or simply do not like this un-Emacsism, you can
5000 set this variable to @code{nil} to get the normal Emacs scrolling
5001 action. This will also inhibit horizontal re-centering of the summary
5002 buffer, which might make it more inconvenient to read extremely long
5005 This variable can also be a number. In that case, center the window at
5006 the given number of lines from the top.
5011 @node Choosing Articles
5012 @section Choosing Articles
5013 @cindex selecting articles
5016 * Choosing Commands:: Commands for choosing articles.
5017 * Choosing Variables:: Variables that influence these commands.
5021 @node Choosing Commands
5022 @subsection Choosing Commands
5024 None of the following movement commands understand the numeric prefix,
5025 and they all select and display an article.
5027 If you want to fetch new articles or redisplay the group, see
5028 @ref{Exiting the Summary Buffer}.
5032 @kindex SPACE (Summary)
5033 @findex gnus-summary-next-page
5034 Select the current article, or, if that one's read already, the next
5035 unread article (@code{gnus-summary-next-page}).
5037 If you have an article window open already and you press @kbd{SPACE}
5038 again, the article will be scrolled. This lets you conveniently
5039 @kbd{SPACE} through an entire newsgroup. @xref{Paging the Article}.
5044 @kindex G n (Summary)
5045 @findex gnus-summary-next-unread-article
5046 @c @icon{gnus-summary-next-unread}
5047 Go to next unread article (@code{gnus-summary-next-unread-article}).
5052 @findex gnus-summary-prev-unread-article
5053 @c @icon{gnus-summary-prev-unread}
5054 Go to previous unread article (@code{gnus-summary-prev-unread-article}).
5059 @kindex G N (Summary)
5060 @findex gnus-summary-next-article
5061 Go to the next article (@code{gnus-summary-next-article}).
5066 @kindex G P (Summary)
5067 @findex gnus-summary-prev-article
5068 Go to the previous article (@code{gnus-summary-prev-article}).
5071 @kindex G C-n (Summary)
5072 @findex gnus-summary-next-same-subject
5073 Go to the next article with the same subject
5074 (@code{gnus-summary-next-same-subject}).
5077 @kindex G C-p (Summary)
5078 @findex gnus-summary-prev-same-subject
5079 Go to the previous article with the same subject
5080 (@code{gnus-summary-prev-same-subject}).
5084 @kindex G f (Summary)
5086 @findex gnus-summary-first-unread-article
5087 Go to the first unread article
5088 (@code{gnus-summary-first-unread-article}).
5092 @kindex G b (Summary)
5094 @findex gnus-summary-best-unread-article
5095 Go to the unread article with the highest score
5096 (@code{gnus-summary-best-unread-article}). If given a prefix argument,
5097 go to the first unread article that has a score over the default score.
5102 @kindex G l (Summary)
5103 @findex gnus-summary-goto-last-article
5104 Go to the previous article read (@code{gnus-summary-goto-last-article}).
5107 @kindex G o (Summary)
5108 @findex gnus-summary-pop-article
5110 @cindex article history
5111 Pop an article off the summary history and go to this article
5112 (@code{gnus-summary-pop-article}). This command differs from the
5113 command above in that you can pop as many previous articles off the
5114 history as you like, while @kbd{l} toggles the two last read articles.
5115 For a somewhat related issue (if you use these commands a lot),
5116 @pxref{Article Backlog}.
5121 @kindex G j (Summary)
5122 @findex gnus-summary-goto-article
5123 Ask for an article number or @code{Message-ID}, and then go to that
5124 article (@code{gnus-summary-goto-article}).
5129 @node Choosing Variables
5130 @subsection Choosing Variables
5132 Some variables relevant for moving and selecting articles:
5135 @item gnus-auto-extend-newsgroup
5136 @vindex gnus-auto-extend-newsgroup
5137 All the movement commands will try to go to the previous (or next)
5138 article, even if that article isn't displayed in the Summary buffer if
5139 this variable is non-@code{nil}. Gnus will then fetch the article from
5140 the server and display it in the article buffer.
5142 @item gnus-select-article-hook
5143 @vindex gnus-select-article-hook
5144 This hook is called whenever an article is selected. By default it
5145 exposes any threads hidden under the selected article. If you would
5146 like each article to be saved in the Agent as you read it, putting
5147 @code{gnus-agent-fetch-selected-article} on this hook will do so.
5149 @item gnus-mark-article-hook
5150 @vindex gnus-mark-article-hook
5151 @findex gnus-summary-mark-unread-as-read
5152 @findex gnus-summary-mark-read-and-unread-as-read
5153 @findex gnus-unread-mark
5154 This hook is called whenever an article is selected. It is intended to
5155 be used for marking articles as read. The default value is
5156 @code{gnus-summary-mark-read-and-unread-as-read}, and will change the
5157 mark of almost any article you read to @code{gnus-unread-mark}. The
5158 only articles not affected by this function are ticked, dormant, and
5159 expirable articles. If you'd instead like to just have unread articles
5160 marked as read, you can use @code{gnus-summary-mark-unread-as-read}
5161 instead. It will leave marks like @code{gnus-low-score-mark},
5162 @code{gnus-del-mark} (and so on) alone.
5167 @node Paging the Article
5168 @section Scrolling the Article
5169 @cindex article scrolling
5174 @kindex SPACE (Summary)
5175 @findex gnus-summary-next-page
5176 Pressing @kbd{SPACE} will scroll the current article forward one page,
5177 or, if you have come to the end of the current article, will choose the
5178 next article (@code{gnus-summary-next-page}).
5180 @vindex gnus-article-boring-faces
5181 @vindex gnus-article-skip-boring
5182 If @code{gnus-article-skip-boring} is non-@code{nil} and the rest of
5183 the article consists only of citations and signature, then it will be
5184 skipped; the next article will be shown instead. You can customize
5185 what is considered uninteresting with
5186 @code{gnus-article-boring-faces}. You can manually view the article's
5187 pages, no matter how boring, using @kbd{C-M-v}.
5190 @kindex DEL (Summary)
5191 @findex gnus-summary-prev-page
5192 Scroll the current article back one page (@code{gnus-summary-prev-page}).
5195 @kindex RET (Summary)
5196 @findex gnus-summary-scroll-up
5197 Scroll the current article one line forward
5198 (@code{gnus-summary-scroll-up}).
5201 @kindex M-RET (Summary)
5202 @findex gnus-summary-scroll-down
5203 Scroll the current article one line backward
5204 (@code{gnus-summary-scroll-down}).
5208 @kindex A g (Summary)
5210 @findex gnus-summary-show-article
5211 @vindex gnus-summary-show-article-charset-alist
5212 (Re)fetch the current article (@code{gnus-summary-show-article}). If
5213 given a prefix, fetch the current article, but don't run any of the
5214 article treatment functions. This will give you a ``raw'' article, just
5215 the way it came from the server.
5217 If given a numerical prefix, you can do semi-manual charset stuff.
5218 @kbd{C-u 0 g cn-gb-2312 RET} will decode the message as if it were
5219 encoded in the @code{cn-gb-2312} charset. If you have
5222 (setq gnus-summary-show-article-charset-alist
5227 then you can say @kbd{C-u 1 g} to get the same effect.
5232 @kindex A < (Summary)
5233 @findex gnus-summary-beginning-of-article
5234 Scroll to the beginning of the article
5235 (@code{gnus-summary-beginning-of-article}).
5240 @kindex A > (Summary)
5241 @findex gnus-summary-end-of-article
5242 Scroll to the end of the article (@code{gnus-summary-end-of-article}).
5246 @kindex A s (Summary)
5248 @findex gnus-summary-isearch-article
5249 Perform an isearch in the article buffer
5250 (@code{gnus-summary-isearch-article}).
5254 @findex gnus-summary-select-article-buffer
5255 Select the article buffer (@code{gnus-summary-select-article-buffer}).
5260 @node Reply Followup and Post
5261 @section Reply, Followup and Post
5264 * Summary Mail Commands:: Sending mail.
5265 * Summary Post Commands:: Sending news.
5266 * Summary Message Commands:: Other Message-related commands.
5267 * Canceling and Superseding::
5271 @node Summary Mail Commands
5272 @subsection Summary Mail Commands
5274 @cindex composing mail
5276 Commands for composing a mail message:
5282 @kindex S r (Summary)
5284 @findex gnus-summary-reply
5285 @c @icon{gnus-summary-mail-reply}
5286 @c @icon{gnus-summary-reply}
5287 Mail a reply to the author of the current article
5288 (@code{gnus-summary-reply}).
5293 @kindex S R (Summary)
5294 @findex gnus-summary-reply-with-original
5295 @c @icon{gnus-summary-reply-with-original}
5296 Mail a reply to the author of the current article and include the
5297 original message (@code{gnus-summary-reply-with-original}). This
5298 command uses the process/prefix convention.
5301 @kindex S w (Summary)
5302 @findex gnus-summary-wide-reply
5303 Mail a wide reply to the author of the current article
5304 (@code{gnus-summary-wide-reply}). A @dfn{wide reply} is a reply that
5305 goes out to all people listed in the @code{To}, @code{From} (or
5306 @code{Reply-to}) and @code{Cc} headers. If @code{Mail-Followup-To} is
5307 present, that's used instead.
5310 @kindex S W (Summary)
5311 @findex gnus-summary-wide-reply-with-original
5312 Mail a wide reply to the current article and include the original
5313 message (@code{gnus-summary-wide-reply-with-original}). This command uses
5314 the process/prefix convention.
5317 @kindex S v (Summary)
5318 @findex gnus-summary-very-wide-reply
5319 Mail a very wide reply to the author of the current article
5320 (@code{gnus-summary-wide-reply}). A @dfn{very wide reply} is a reply
5321 that goes out to all people listed in the @code{To}, @code{From} (or
5322 @code{Reply-to}) and @code{Cc} headers in all the process/prefixed
5323 articles. This command uses the process/prefix convention.
5326 @kindex S V (Summary)
5327 @findex gnus-summary-very-wide-reply-with-original
5328 Mail a very wide reply to the author of the current article and include the
5329 original message (@code{gnus-summary-very-wide-reply-with-original}). This
5330 command uses the process/prefix convention.
5333 @kindex S B r (Summary)
5334 @findex gnus-summary-reply-broken-reply-to
5335 Mail a reply to the author of the current article but ignore the
5336 @code{Reply-To} field (@code{gnus-summary-reply-broken-reply-to}).
5337 If you need this because a mailing list incorrectly sets a
5338 @code{Reply-To} header pointing to the list, you probably want to set
5339 the @code{broken-reply-to} group parameter instead, so things will work
5340 correctly. @xref{Group Parameters}.
5343 @kindex S B R (Summary)
5344 @findex gnus-summary-reply-broken-reply-to-with-original
5345 Mail a reply to the author of the current article and include the
5346 original message but ignore the @code{Reply-To} field
5347 (@code{gnus-summary-reply-broken-reply-to-with-original}).
5351 @kindex S o m (Summary)
5352 @kindex C-c C-f (Summary)
5353 @findex gnus-summary-mail-forward
5354 @c @icon{gnus-summary-mail-forward}
5355 Forward the current article to some other person
5356 (@code{gnus-summary-mail-forward}). If no prefix is given, the message
5357 is forwarded according to the value of (@code{message-forward-as-mime})
5358 and (@code{message-forward-show-mml}); if the prefix is 1, decode the
5359 message and forward directly inline; if the prefix is 2, forward message
5360 as an rfc822 @acronym{MIME} section; if the prefix is 3, decode message and
5361 forward as an rfc822 @acronym{MIME} section; if the prefix is 4, forward message
5362 directly inline; otherwise, the message is forwarded as no prefix given
5363 but use the flipped value of (@code{message-forward-as-mime}). By
5364 default, the message is decoded and forwarded as an rfc822 @acronym{MIME}
5370 @kindex S m (Summary)
5371 @findex gnus-summary-mail-other-window
5372 @c @icon{gnus-summary-mail-originate}
5373 Prepare a mail (@code{gnus-summary-mail-other-window}). By default, use
5374 the posting style of the current group. If given a prefix, disable that.
5375 If the prefix is 1, prompt for a group name to find the posting style.
5380 @kindex S i (Summary)
5381 @findex gnus-summary-news-other-window
5382 Prepare a news (@code{gnus-summary-news-other-window}). By default,
5383 post to the current group. If given a prefix, disable that. If the
5384 prefix is 1, prompt for a group to post to.
5386 This function actually prepares a news even when using mail groups.
5387 This is useful for ``posting'' messages to mail groups without actually
5388 sending them over the network: they're just saved directly to the group
5389 in question. The corresponding back end must have a request-post method
5390 for this to work though.
5393 @kindex S D b (Summary)
5394 @findex gnus-summary-resend-bounced-mail
5395 @cindex bouncing mail
5396 If you have sent a mail, but the mail was bounced back to you for some
5397 reason (wrong address, transient failure), you can use this command to
5398 resend that bounced mail (@code{gnus-summary-resend-bounced-mail}). You
5399 will be popped into a mail buffer where you can edit the headers before
5400 sending the mail off again. If you give a prefix to this command, and
5401 the bounced mail is a reply to some other mail, Gnus will try to fetch
5402 that mail and display it for easy perusal of its headers. This might
5403 very well fail, though.
5406 @kindex S D r (Summary)
5407 @findex gnus-summary-resend-message
5408 Not to be confused with the previous command,
5409 @code{gnus-summary-resend-message} will prompt you for an address to
5410 send the current message off to, and then send it to that place. The
5411 headers of the message won't be altered---but lots of headers that say
5412 @code{Resent-To}, @code{Resent-From} and so on will be added. This
5413 means that you actually send a mail to someone that has a @code{To}
5414 header that (probably) points to yourself. This will confuse people.
5415 So, natcherly you'll only do that if you're really eVIl.
5417 This command is mainly used if you have several accounts and want to
5418 ship a mail to a different account of yours. (If you're both
5419 @code{root} and @code{postmaster} and get a mail for @code{postmaster}
5420 to the @code{root} account, you may want to resend it to
5421 @code{postmaster}. Ordnung muss sein!
5423 This command understands the process/prefix convention
5424 (@pxref{Process/Prefix}).
5427 @kindex S D e (Summary)
5428 @findex gnus-summary-resend-message-edit
5430 Like the previous command, but will allow you to edit the message as
5431 if it were a new message before resending.
5434 @kindex S O m (Summary)
5435 @findex gnus-uu-digest-mail-forward
5436 Digest the current series (@pxref{Decoding Articles}) and forward the
5437 result using mail (@code{gnus-uu-digest-mail-forward}). This command
5438 uses the process/prefix convention (@pxref{Process/Prefix}).
5441 @kindex S M-c (Summary)
5442 @findex gnus-summary-mail-crosspost-complaint
5443 @cindex crossposting
5444 @cindex excessive crossposting
5445 Send a complaint about excessive crossposting to the author of the
5446 current article (@code{gnus-summary-mail-crosspost-complaint}).
5448 @findex gnus-crosspost-complaint
5449 This command is provided as a way to fight back against the current
5450 crossposting pandemic that's sweeping Usenet. It will compose a reply
5451 using the @code{gnus-crosspost-complaint} variable as a preamble. This
5452 command understands the process/prefix convention
5453 (@pxref{Process/Prefix}) and will prompt you before sending each mail.
5457 Also @xref{Header Commands, ,Header Commands, message, The Message
5458 Manual}, for more information.
5461 @node Summary Post Commands
5462 @subsection Summary Post Commands
5464 @cindex composing news
5466 Commands for posting a news article:
5472 @kindex S p (Summary)
5473 @findex gnus-summary-post-news
5474 @c @icon{gnus-summary-post-news}
5475 Prepare for posting an article (@code{gnus-summary-post-news}). By
5476 default, post to the current group. If given a prefix, disable that.
5477 If the prefix is 1, prompt for another group instead.
5482 @kindex S f (Summary)
5483 @findex gnus-summary-followup
5484 @c @icon{gnus-summary-followup}
5485 Post a followup to the current article (@code{gnus-summary-followup}).
5489 @kindex S F (Summary)
5491 @c @icon{gnus-summary-followup-with-original}
5492 @findex gnus-summary-followup-with-original
5493 Post a followup to the current article and include the original message
5494 (@code{gnus-summary-followup-with-original}). This command uses the
5495 process/prefix convention.
5498 @kindex S n (Summary)
5499 @findex gnus-summary-followup-to-mail
5500 Post a followup to the current article via news, even if you got the
5501 message through mail (@code{gnus-summary-followup-to-mail}).
5504 @kindex S N (Summary)
5505 @findex gnus-summary-followup-to-mail-with-original
5506 Post a followup to the current article via news, even if you got the
5507 message through mail and include the original message
5508 (@code{gnus-summary-followup-to-mail-with-original}). This command uses
5509 the process/prefix convention.
5512 @kindex S o p (Summary)
5513 @findex gnus-summary-post-forward
5514 Forward the current article to a newsgroup
5515 (@code{gnus-summary-post-forward}).
5516 If no prefix is given, the message is forwarded according to the value
5517 of (@code{message-forward-as-mime}) and
5518 (@code{message-forward-show-mml}); if the prefix is 1, decode the
5519 message and forward directly inline; if the prefix is 2, forward message
5520 as an rfc822 @acronym{MIME} section; if the prefix is 3, decode message and
5521 forward as an rfc822 @acronym{MIME} section; if the prefix is 4, forward message
5522 directly inline; otherwise, the message is forwarded as no prefix given
5523 but use the flipped value of (@code{message-forward-as-mime}). By
5524 default, the message is decoded and forwarded as an rfc822 @acronym{MIME} section.
5527 @kindex S O p (Summary)
5528 @findex gnus-uu-digest-post-forward
5530 @cindex making digests
5531 Digest the current series and forward the result to a newsgroup
5532 (@code{gnus-uu-digest-mail-forward}). This command uses the
5533 process/prefix convention.
5536 @kindex S u (Summary)
5537 @findex gnus-uu-post-news
5538 @c @icon{gnus-uu-post-news}
5539 Uuencode a file, split it into parts, and post it as a series
5540 (@code{gnus-uu-post-news}). (@pxref{Uuencoding and Posting}).
5543 Also @xref{Header Commands, ,Header Commands, message, The Message
5544 Manual}, for more information.
5547 @node Summary Message Commands
5548 @subsection Summary Message Commands
5552 @kindex S y (Summary)
5553 @findex gnus-summary-yank-message
5554 Yank the current article into an already existing Message composition
5555 buffer (@code{gnus-summary-yank-message}). This command prompts for
5556 what message buffer you want to yank into, and understands the
5557 process/prefix convention (@pxref{Process/Prefix}).
5562 @node Canceling and Superseding
5563 @subsection Canceling Articles
5564 @cindex canceling articles
5565 @cindex superseding articles
5567 Have you ever written something, and then decided that you really,
5568 really, really wish you hadn't posted that?
5570 Well, you can't cancel mail, but you can cancel posts.
5572 @findex gnus-summary-cancel-article
5574 @c @icon{gnus-summary-cancel-article}
5575 Find the article you wish to cancel (you can only cancel your own
5576 articles, so don't try any funny stuff). Then press @kbd{C} or @kbd{S
5577 c} (@code{gnus-summary-cancel-article}). Your article will be
5578 canceled---machines all over the world will be deleting your article.
5579 This command uses the process/prefix convention (@pxref{Process/Prefix}).
5581 Be aware, however, that not all sites honor cancels, so your article may
5582 live on here and there, while most sites will delete the article in
5585 Gnus will use the ``current'' select method when canceling. If you
5586 want to use the standard posting method, use the @samp{a} symbolic
5587 prefix (@pxref{Symbolic Prefixes}).
5589 Gnus ensures that only you can cancel your own messages using a
5590 @code{Cancel-Lock} header (@pxref{Canceling News, Canceling News, ,
5591 message, Message Manual}).
5593 If you discover that you have made some mistakes and want to do some
5594 corrections, you can post a @dfn{superseding} article that will replace
5595 your original article.
5597 @findex gnus-summary-supersede-article
5599 Go to the original article and press @kbd{S s}
5600 (@code{gnus-summary-supersede-article}). You will be put in a buffer
5601 where you can edit the article all you want before sending it off the
5604 The same goes for superseding as for canceling, only more so: Some
5605 sites do not honor superseding. On those sites, it will appear that you
5606 have posted almost the same article twice.
5608 If you have just posted the article, and change your mind right away,
5609 there is a trick you can use to cancel/supersede the article without
5610 waiting for the article to appear on your site first. You simply return
5611 to the post buffer (which is called @code{*sent ...*}). There you will
5612 find the article you just posted, with all the headers intact. Change
5613 the @code{Message-ID} header to a @code{Cancel} or @code{Supersedes}
5614 header by substituting one of those words for the word
5615 @code{Message-ID}. Then just press @kbd{C-c C-c} to send the article as
5616 you would do normally. The previous article will be
5617 canceled/superseded.
5619 Just remember, kids: There is no 'c' in 'supersede'.
5621 @node Delayed Articles
5622 @section Delayed Articles
5623 @cindex delayed sending
5624 @cindex send delayed
5626 Sometimes, you might wish to delay the sending of a message. For
5627 example, you might wish to arrange for a message to turn up just in time
5628 to remind your about the birthday of your Significant Other. For this,
5629 there is the @code{gnus-delay} package. Setup is simple:
5632 (gnus-delay-initialize)
5635 @findex gnus-delay-article
5636 Normally, to send a message you use the @kbd{C-c C-c} command from
5637 Message mode. To delay a message, use @kbd{C-c C-j}
5638 (@code{gnus-delay-article}) instead. This will ask you for how long the
5639 message should be delayed. Possible answers are:
5643 A time span. Consists of an integer and a letter. For example,
5644 @code{42d} means to delay for 42 days. Available letters are @code{m}
5645 (minutes), @code{h} (hours), @code{d} (days), @code{w} (weeks), @code{M}
5646 (months) and @code{Y} (years).
5649 A specific date. Looks like @code{YYYY-MM-DD}. The message will be
5650 delayed until that day, at a specific time (eight o'clock by default).
5651 See also @code{gnus-delay-default-hour}.
5654 A specific time of day. Given in @code{hh:mm} format, 24h, no am/pm
5655 stuff. The deadline will be at that time today, except if that time has
5656 already passed, then it's at the given time tomorrow. So if it's ten
5657 o'clock in the morning and you specify @code{11:15}, then the deadline
5658 is one hour and fifteen minutes hence. But if you specify @code{9:20},
5659 that means a time tomorrow.
5662 The action of the @code{gnus-delay-article} command is influenced by a
5663 couple of variables:
5666 @item gnus-delay-default-hour
5667 @vindex gnus-delay-default-hour
5668 When you specify a specific date, the message will be due on that hour
5669 on the given date. Possible values are integers 0 through 23.
5671 @item gnus-delay-default-delay
5672 @vindex gnus-delay-default-delay
5673 This is a string and gives the default delay. It can be of any of the
5674 formats described above.
5676 @item gnus-delay-group
5677 @vindex gnus-delay-group
5678 Delayed articles will be kept in this group on the drafts server until
5679 they are due. You probably don't need to change this. The default
5680 value is @code{"delayed"}.
5682 @item gnus-delay-header
5683 @vindex gnus-delay-header
5684 The deadline for each article will be stored in a header. This variable
5685 is a string and gives the header name. You probably don't need to
5686 change this. The default value is @code{"X-Gnus-Delayed"}.
5689 The way delaying works is like this: when you use the
5690 @code{gnus-delay-article} command, you give a certain delay. Gnus
5691 calculates the deadline of the message and stores it in the
5692 @code{X-Gnus-Delayed} header and puts the message in the
5693 @code{nndraft:delayed} group.
5695 @findex gnus-delay-send-queue
5696 And whenever you get new news, Gnus looks through the group for articles
5697 which are due and sends them. It uses the @code{gnus-delay-send-queue}
5698 function for this. By default, this function is added to the hook
5699 @code{gnus-get-new-news-hook}. But of course, you can change this.
5700 Maybe you want to use the demon to send drafts? Just tell the demon to
5701 execute the @code{gnus-delay-send-queue} function.
5704 @item gnus-delay-initialize
5705 @findex gnus-delay-initialize
5706 By default, this function installs @code{gnus-delay-send-queue} in
5707 @code{gnus-get-new-news-hook}. But it accepts the optional second
5708 argument @code{no-check}. If it is non-@code{nil},
5709 @code{gnus-get-new-news-hook} is not changed. The optional first
5710 argument is ignored.
5712 For example, @code{(gnus-delay-initialize nil t)} means to do nothing.
5713 Presumably, you want to use the demon for sending due delayed articles.
5714 Just don't forget to set that up :-)
5718 @node Marking Articles
5719 @section Marking Articles
5720 @cindex article marking
5721 @cindex article ticking
5724 There are several marks you can set on an article.
5726 You have marks that decide the @dfn{readedness} (whoo, neato-keano
5727 neologism ohoy!) of the article. Alphabetic marks generally mean
5728 @dfn{read}, while non-alphabetic characters generally mean @dfn{unread}.
5730 In addition, you also have marks that do not affect readedness.
5733 There's a plethora of commands for manipulating these marks.
5737 * Unread Articles:: Marks for unread articles.
5738 * Read Articles:: Marks for read articles.
5739 * Other Marks:: Marks that do not affect readedness.
5740 * Setting Marks:: How to set and remove marks.
5741 * Generic Marking Commands:: How to customize the marking.
5742 * Setting Process Marks:: How to mark articles for later processing.
5746 @node Unread Articles
5747 @subsection Unread Articles
5749 The following marks mark articles as (kinda) unread, in one form or
5754 @vindex gnus-ticked-mark
5755 Marked as ticked (@code{gnus-ticked-mark}).
5757 @dfn{Ticked articles} are articles that will remain visible always. If
5758 you see an article that you find interesting, or you want to put off
5759 reading it, or replying to it, until sometime later, you'd typically
5760 tick it. However, articles can be expired (from news servers by the
5761 news server software, Gnus itself never expires ticked messages), so if
5762 you want to keep an article forever, you'll have to make it persistent
5763 (@pxref{Persistent Articles}).
5766 @vindex gnus-dormant-mark
5767 Marked as dormant (@code{gnus-dormant-mark}).
5769 @dfn{Dormant articles} will only appear in the summary buffer if there
5770 are followups to it. If you want to see them even if they don't have
5771 followups, you can use the @kbd{/ D} command (@pxref{Limiting}).
5772 Otherwise (except for the visibility issue), they are just like ticked
5776 @vindex gnus-unread-mark
5777 Marked as unread (@code{gnus-unread-mark}).
5779 @dfn{Unread articles} are articles that haven't been read at all yet.
5784 @subsection Read Articles
5785 @cindex expirable mark
5787 All the following marks mark articles as read.
5792 @vindex gnus-del-mark
5793 These are articles that the user has marked as read with the @kbd{d}
5794 command manually, more or less (@code{gnus-del-mark}).
5797 @vindex gnus-read-mark
5798 Articles that have actually been read (@code{gnus-read-mark}).
5801 @vindex gnus-ancient-mark
5802 Articles that were marked as read in previous sessions and are now
5803 @dfn{old} (@code{gnus-ancient-mark}).
5806 @vindex gnus-killed-mark
5807 Marked as killed (@code{gnus-killed-mark}).
5810 @vindex gnus-kill-file-mark
5811 Marked as killed by kill files (@code{gnus-kill-file-mark}).
5814 @vindex gnus-low-score-mark
5815 Marked as read by having too low a score (@code{gnus-low-score-mark}).
5818 @vindex gnus-catchup-mark
5819 Marked as read by a catchup (@code{gnus-catchup-mark}).
5822 @vindex gnus-canceled-mark
5823 Canceled article (@code{gnus-canceled-mark})
5826 @vindex gnus-souped-mark
5827 @sc{soup}ed article (@code{gnus-souped-mark}). @xref{SOUP}.
5830 @vindex gnus-sparse-mark
5831 Sparsely reffed article (@code{gnus-sparse-mark}). @xref{Customizing
5835 @vindex gnus-duplicate-mark
5836 Article marked as read by duplicate suppression
5837 (@code{gnus-duplicate-mark}). @xref{Duplicate Suppression}.
5841 All these marks just mean that the article is marked as read, really.
5842 They are interpreted differently when doing adaptive scoring, though.
5844 One more special mark, though:
5848 @vindex gnus-expirable-mark
5849 Marked as expirable (@code{gnus-expirable-mark}).
5851 Marking articles as @dfn{expirable} (or have them marked as such
5852 automatically) doesn't make much sense in normal groups---a user doesn't
5853 control expiring of news articles, but in mail groups, for instance,
5854 articles marked as @dfn{expirable} can be deleted by Gnus at
5860 @subsection Other Marks
5861 @cindex process mark
5864 There are some marks that have nothing to do with whether the article is
5870 You can set a bookmark in the current article. Say you are reading a
5871 long thesis on cats' urinary tracts, and have to go home for dinner
5872 before you've finished reading the thesis. You can then set a bookmark
5873 in the article, and Gnus will jump to this bookmark the next time it
5874 encounters the article. @xref{Setting Marks}.
5877 @vindex gnus-replied-mark
5878 All articles that you have replied to or made a followup to (i.e., have
5879 answered) will be marked with an @samp{A} in the second column
5880 (@code{gnus-replied-mark}).
5883 @vindex gnus-forwarded-mark
5884 All articles that you have forwarded will be marked with an @samp{F} in
5885 the second column (@code{gnus-forwarded-mark}).
5888 @vindex gnus-cached-mark
5889 Articles stored in the article cache will be marked with an @samp{*} in
5890 the second column (@code{gnus-cached-mark}). @xref{Article Caching}.
5893 @vindex gnus-saved-mark
5894 Articles ``saved'' (in some manner or other; not necessarily
5895 religiously) are marked with an @samp{S} in the second column
5896 (@code{gnus-saved-mark}).
5899 @vindex gnus-recent-mark
5900 Articles that according to the server haven't been shown to the user
5901 before are marked with a @samp{N} in the second column
5902 (@code{gnus-recent-mark}). Note that not all servers support this
5903 mark, in which case it simply never appears. Compare with
5904 @code{gnus-unseen-mark}.
5907 @vindex gnus-unseen-mark
5908 Articles that haven't been seen before in Gnus by the user are marked
5909 with a @samp{.} in the second column (@code{gnus-unseen-mark}).
5910 Compare with @code{gnus-recent-mark}.
5913 @vindex gnus-downloaded-mark
5914 When using the Gnus agent (@pxref{Agent Basics}), articles may be
5915 downloaded for unplugged (offline) viewing. If you are using the
5916 @samp{%O} spec, these articles get the @samp{+} mark in that spec.
5917 (The variable @code{gnus-downloaded-mark} controls which character to
5921 @vindex gnus-undownloaded-mark
5922 When using the Gnus agent (@pxref{Agent Basics}), some articles might
5923 not have been downloaded. Such articles cannot be viewed while you
5924 are unplugged (offline). If you are using the @samp{%O} spec, these
5925 articles get the @samp{-} mark in that spec. (The variable
5926 @code{gnus-undownloaded-mark} controls which character to use.)
5929 @vindex gnus-downloadable-mark
5930 The Gnus agent (@pxref{Agent Basics}) downloads some articles
5931 automatically, but it is also possible to explicitly mark articles for
5932 download, even if they would not be downloaded automatically. Such
5933 explicitly-marked articles get the @samp{%} mark in the first column.
5934 (The variable @code{gnus-downloadable-mark} controls which character to
5938 @vindex gnus-not-empty-thread-mark
5939 @vindex gnus-empty-thread-mark
5940 If the @samp{%e} spec is used, the presence of threads or not will be
5941 marked with @code{gnus-not-empty-thread-mark} and
5942 @code{gnus-empty-thread-mark} in the third column, respectively.
5945 @vindex gnus-process-mark
5946 Finally we have the @dfn{process mark} (@code{gnus-process-mark}). A
5947 variety of commands react to the presence of the process mark. For
5948 instance, @kbd{X u} (@code{gnus-uu-decode-uu}) will uudecode and view
5949 all articles that have been marked with the process mark. Articles
5950 marked with the process mark have a @samp{#} in the second column.
5954 You might have noticed that most of these ``non-readedness'' marks
5955 appear in the second column by default. So if you have a cached, saved,
5956 replied article that you have process-marked, what will that look like?
5958 Nothing much. The precedence rules go as follows: process -> cache ->
5959 replied -> saved. So if the article is in the cache and is replied,
5960 you'll only see the cache mark and not the replied mark.
5964 @subsection Setting Marks
5965 @cindex setting marks
5967 All the marking commands understand the numeric prefix.
5972 @kindex M c (Summary)
5973 @kindex M-u (Summary)
5974 @findex gnus-summary-clear-mark-forward
5975 @cindex mark as unread
5976 Clear all readedness-marks from the current article
5977 (@code{gnus-summary-clear-mark-forward}). In other words, mark the
5983 @kindex M t (Summary)
5984 @findex gnus-summary-tick-article-forward
5985 Tick the current article (@code{gnus-summary-tick-article-forward}).
5986 @xref{Article Caching}.
5991 @kindex M ? (Summary)
5992 @findex gnus-summary-mark-as-dormant
5993 Mark the current article as dormant
5994 (@code{gnus-summary-mark-as-dormant}). @xref{Article Caching}.
5998 @kindex M d (Summary)
6000 @findex gnus-summary-mark-as-read-forward
6001 Mark the current article as read
6002 (@code{gnus-summary-mark-as-read-forward}).
6006 @findex gnus-summary-mark-as-read-backward
6007 Mark the current article as read and move point to the previous line
6008 (@code{gnus-summary-mark-as-read-backward}).
6013 @kindex M k (Summary)
6014 @findex gnus-summary-kill-same-subject-and-select
6015 Mark all articles that have the same subject as the current one as read,
6016 and then select the next unread article
6017 (@code{gnus-summary-kill-same-subject-and-select}).
6021 @kindex M K (Summary)
6022 @kindex C-k (Summary)
6023 @findex gnus-summary-kill-same-subject
6024 Mark all articles that have the same subject as the current one as read
6025 (@code{gnus-summary-kill-same-subject}).
6028 @kindex M C (Summary)
6029 @findex gnus-summary-catchup
6030 @c @icon{gnus-summary-catchup}
6031 Mark all unread articles as read (@code{gnus-summary-catchup}).
6034 @kindex M C-c (Summary)
6035 @findex gnus-summary-catchup-all
6036 Mark all articles in the group as read---even the ticked and dormant
6037 articles (@code{gnus-summary-catchup-all}).
6040 @kindex M H (Summary)
6041 @findex gnus-summary-catchup-to-here
6042 Catchup the current group to point (before the point)
6043 (@code{gnus-summary-catchup-to-here}).
6046 @kindex M h (Summary)
6047 @findex gnus-summary-catchup-from-here
6048 Catchup the current group from point (after the point)
6049 (@code{gnus-summary-catchup-from-here}).
6052 @kindex C-w (Summary)
6053 @findex gnus-summary-mark-region-as-read
6054 Mark all articles between point and mark as read
6055 (@code{gnus-summary-mark-region-as-read}).
6058 @kindex M V k (Summary)
6059 @findex gnus-summary-kill-below
6060 Kill all articles with scores below the default score (or below the
6061 numeric prefix) (@code{gnus-summary-kill-below}).
6065 @kindex M e (Summary)
6067 @findex gnus-summary-mark-as-expirable
6068 Mark the current article as expirable
6069 (@code{gnus-summary-mark-as-expirable}).
6072 @kindex M b (Summary)
6073 @findex gnus-summary-set-bookmark
6074 Set a bookmark in the current article
6075 (@code{gnus-summary-set-bookmark}).
6078 @kindex M B (Summary)
6079 @findex gnus-summary-remove-bookmark
6080 Remove the bookmark from the current article
6081 (@code{gnus-summary-remove-bookmark}).
6084 @kindex M V c (Summary)
6085 @findex gnus-summary-clear-above
6086 Clear all marks from articles with scores over the default score (or
6087 over the numeric prefix) (@code{gnus-summary-clear-above}).
6090 @kindex M V u (Summary)
6091 @findex gnus-summary-tick-above
6092 Tick all articles with scores over the default score (or over the
6093 numeric prefix) (@code{gnus-summary-tick-above}).
6096 @kindex M V m (Summary)
6097 @findex gnus-summary-mark-above
6098 Prompt for a mark, and mark all articles with scores over the default
6099 score (or over the numeric prefix) with this mark
6100 (@code{gnus-summary-clear-above}).
6103 @vindex gnus-summary-goto-unread
6104 The @code{gnus-summary-goto-unread} variable controls what action should
6105 be taken after setting a mark. If non-@code{nil}, point will move to
6106 the next/previous unread article. If @code{nil}, point will just move
6107 one line up or down. As a special case, if this variable is
6108 @code{never}, all the marking commands as well as other commands (like
6109 @kbd{SPACE}) will move to the next article, whether it is unread or not.
6110 The default is @code{t}.
6113 @node Generic Marking Commands
6114 @subsection Generic Marking Commands
6116 Some people would like the command that ticks an article (@kbd{!}) go to
6117 the next article. Others would like it to go to the next unread
6118 article. Yet others would like it to stay on the current article. And
6119 even though I haven't heard of anybody wanting it to go to the
6120 previous (unread) article, I'm sure there are people that want that as
6123 Multiply these five behaviors with five different marking commands, and
6124 you get a potentially complex set of variable to control what each
6127 To sidestep that mess, Gnus provides commands that do all these
6128 different things. They can be found on the @kbd{M M} map in the summary
6129 buffer. Type @kbd{M M C-h} to see them all---there are too many of them
6130 to list in this manual.
6132 While you can use these commands directly, most users would prefer
6133 altering the summary mode keymap. For instance, if you would like the
6134 @kbd{!} command to go to the next article instead of the next unread
6135 article, you could say something like:
6139 (add-hook 'gnus-summary-mode-hook 'my-alter-summary-map)
6140 (defun my-alter-summary-map ()
6141 (local-set-key "!" 'gnus-summary-put-mark-as-ticked-next))
6149 (defun my-alter-summary-map ()
6150 (local-set-key "!" "MM!n"))
6154 @node Setting Process Marks
6155 @subsection Setting Process Marks
6156 @cindex setting process marks
6158 Process marks are displayed as @code{#} in the summary buffer, and are
6159 used for marking articles in such a way that other commands will
6160 process these articles. For instance, if you process mark four
6161 articles and then use the @kbd{*} command, Gnus will enter these four
6162 commands into the cache. For more information,
6163 @pxref{Process/Prefix}.
6170 @kindex M P p (Summary)
6171 @findex gnus-summary-mark-as-processable
6172 Mark the current article with the process mark
6173 (@code{gnus-summary-mark-as-processable}).
6174 @findex gnus-summary-unmark-as-processable
6178 @kindex M P u (Summary)
6179 @kindex M-# (Summary)
6180 Remove the process mark, if any, from the current article
6181 (@code{gnus-summary-unmark-as-processable}).
6184 @kindex M P U (Summary)
6185 @findex gnus-summary-unmark-all-processable
6186 Remove the process mark from all articles
6187 (@code{gnus-summary-unmark-all-processable}).
6190 @kindex M P i (Summary)
6191 @findex gnus-uu-invert-processable
6192 Invert the list of process marked articles
6193 (@code{gnus-uu-invert-processable}).
6196 @kindex M P R (Summary)
6197 @findex gnus-uu-mark-by-regexp
6198 Mark articles that have a @code{Subject} header that matches a regular
6199 expression (@code{gnus-uu-mark-by-regexp}).
6202 @kindex M P G (Summary)
6203 @findex gnus-uu-unmark-by-regexp
6204 Unmark articles that have a @code{Subject} header that matches a regular
6205 expression (@code{gnus-uu-unmark-by-regexp}).
6208 @kindex M P r (Summary)
6209 @findex gnus-uu-mark-region
6210 Mark articles in region (@code{gnus-uu-mark-region}).
6213 @kindex M P g (Summary)
6214 @findex gnus-uu-unmark-region
6215 Unmark articles in region (@code{gnus-uu-unmark-region}).
6218 @kindex M P t (Summary)
6219 @findex gnus-uu-mark-thread
6220 Mark all articles in the current (sub)thread
6221 (@code{gnus-uu-mark-thread}).
6224 @kindex M P T (Summary)
6225 @findex gnus-uu-unmark-thread
6226 Unmark all articles in the current (sub)thread
6227 (@code{gnus-uu-unmark-thread}).
6230 @kindex M P v (Summary)
6231 @findex gnus-uu-mark-over
6232 Mark all articles that have a score above the prefix argument
6233 (@code{gnus-uu-mark-over}).
6236 @kindex M P s (Summary)
6237 @findex gnus-uu-mark-series
6238 Mark all articles in the current series (@code{gnus-uu-mark-series}).
6241 @kindex M P S (Summary)
6242 @findex gnus-uu-mark-sparse
6243 Mark all series that have already had some articles marked
6244 (@code{gnus-uu-mark-sparse}).
6247 @kindex M P a (Summary)
6248 @findex gnus-uu-mark-all
6249 Mark all articles in series order (@code{gnus-uu-mark-all}).
6252 @kindex M P b (Summary)
6253 @findex gnus-uu-mark-buffer
6254 Mark all articles in the buffer in the order they appear
6255 (@code{gnus-uu-mark-buffer}).
6258 @kindex M P k (Summary)
6259 @findex gnus-summary-kill-process-mark
6260 Push the current process mark set onto the stack and unmark all articles
6261 (@code{gnus-summary-kill-process-mark}).
6264 @kindex M P y (Summary)
6265 @findex gnus-summary-yank-process-mark
6266 Pop the previous process mark set from the stack and restore it
6267 (@code{gnus-summary-yank-process-mark}).
6270 @kindex M P w (Summary)
6271 @findex gnus-summary-save-process-mark
6272 Push the current process mark set onto the stack
6273 (@code{gnus-summary-save-process-mark}).
6277 Also see the @kbd{&} command in @ref{Searching for Articles}, for how to
6278 set process marks based on article body contents.
6285 It can be convenient to limit the summary buffer to just show some
6286 subset of the articles currently in the group. The effect most limit
6287 commands have is to remove a few (or many) articles from the summary
6290 All limiting commands work on subsets of the articles already fetched
6291 from the servers. None of these commands query the server for
6292 additional articles.
6298 @kindex / / (Summary)
6299 @findex gnus-summary-limit-to-subject
6300 Limit the summary buffer to articles that match some subject
6301 (@code{gnus-summary-limit-to-subject}). If given a prefix, exclude
6305 @kindex / a (Summary)
6306 @findex gnus-summary-limit-to-author
6307 Limit the summary buffer to articles that match some author
6308 (@code{gnus-summary-limit-to-author}). If given a prefix, exclude
6312 @kindex / R (Summary)
6313 @findex gnus-summary-limit-to-recipient
6314 Limit the summary buffer to articles that match some recipient
6315 (@code{gnus-summary-limit-to-recipient}). If given a prefix, exclude
6319 @kindex / x (Summary)
6320 @findex gnus-summary-limit-to-extra
6321 Limit the summary buffer to articles that match one of the ``extra''
6322 headers (@pxref{To From Newsgroups})
6323 (@code{gnus-summary-limit-to-extra}). If given a prefix, exclude
6328 @kindex / u (Summary)
6330 @findex gnus-summary-limit-to-unread
6331 Limit the summary buffer to articles not marked as read
6332 (@code{gnus-summary-limit-to-unread}). If given a prefix, limit the
6333 buffer to articles strictly unread. This means that ticked and
6334 dormant articles will also be excluded.
6337 @kindex / m (Summary)
6338 @findex gnus-summary-limit-to-marks
6339 Ask for a mark and then limit to all articles that have been marked
6340 with that mark (@code{gnus-summary-limit-to-marks}).
6343 @kindex / t (Summary)
6344 @findex gnus-summary-limit-to-age
6345 Ask for a number and then limit the summary buffer to articles older than (or equal to) that number of days
6346 (@code{gnus-summary-limit-to-age}). If given a prefix, limit to
6347 articles younger than that number of days.
6350 @kindex / n (Summary)
6351 @findex gnus-summary-limit-to-articles
6352 Limit the summary buffer to the current article
6353 (@code{gnus-summary-limit-to-articles}). Uses the process/prefix
6354 convention (@pxref{Process/Prefix}).
6357 @kindex / w (Summary)
6358 @findex gnus-summary-pop-limit
6359 Pop the previous limit off the stack and restore it
6360 (@code{gnus-summary-pop-limit}). If given a prefix, pop all limits off
6364 @kindex / . (Summary)
6365 @findex gnus-summary-limit-to-unseen
6366 Limit the summary buffer to the unseen articles
6367 (@code{gnus-summary-limit-to-unseen}).
6370 @kindex / v (Summary)
6371 @findex gnus-summary-limit-to-score
6372 Limit the summary buffer to articles that have a score at or above some
6373 score (@code{gnus-summary-limit-to-score}).
6376 @kindex / p (Summary)
6377 @findex gnus-summary-limit-to-display-predicate
6378 Limit the summary buffer to articles that satisfy the @code{display}
6379 group parameter predicate
6380 (@code{gnus-summary-limit-to-display-predicate}). @xref{Group
6381 Parameters}, for more on this predicate.
6384 @kindex / r (Summary)
6385 @findex gnus-summary-limit-to-replied
6386 Limit the summary buffer to replied articles
6387 (@code{gnus-summary-limit-to-replied}). If given a prefix, exclude
6392 @kindex M S (Summary)
6393 @kindex / E (Summary)
6394 @findex gnus-summary-limit-include-expunged
6395 Include all expunged articles in the limit
6396 (@code{gnus-summary-limit-include-expunged}).
6399 @kindex / D (Summary)
6400 @findex gnus-summary-limit-include-dormant
6401 Include all dormant articles in the limit
6402 (@code{gnus-summary-limit-include-dormant}).
6405 @kindex / * (Summary)
6406 @findex gnus-summary-limit-include-cached
6407 Include all cached articles in the limit
6408 (@code{gnus-summary-limit-include-cached}).
6411 @kindex / d (Summary)
6412 @findex gnus-summary-limit-exclude-dormant
6413 Exclude all dormant articles from the limit
6414 (@code{gnus-summary-limit-exclude-dormant}).
6417 @kindex / M (Summary)
6418 @findex gnus-summary-limit-exclude-marks
6419 Exclude all marked articles (@code{gnus-summary-limit-exclude-marks}).
6422 @kindex / T (Summary)
6423 @findex gnus-summary-limit-include-thread
6424 Include all the articles in the current thread in the limit.
6427 @kindex / c (Summary)
6428 @findex gnus-summary-limit-exclude-childless-dormant
6429 Exclude all dormant articles that have no children from the limit@*
6430 (@code{gnus-summary-limit-exclude-childless-dormant}).
6433 @kindex / C (Summary)
6434 @findex gnus-summary-limit-mark-excluded-as-read
6435 Mark all excluded unread articles as read
6436 (@code{gnus-summary-limit-mark-excluded-as-read}). If given a prefix,
6437 also mark excluded ticked and dormant articles as read.
6440 @kindex / N (Summary)
6441 @findex gnus-summary-insert-new-articles
6442 Insert all new articles in the summary buffer. It scans for new emails
6443 if @var{back-end}@code{-get-new-mail} is non-@code{nil}.
6446 @kindex / o (Summary)
6447 @findex gnus-summary-insert-old-articles
6448 Insert all old articles in the summary buffer. If given a numbered
6449 prefix, fetch this number of articles.
6457 @cindex article threading
6459 Gnus threads articles by default. @dfn{To thread} is to put responses
6460 to articles directly after the articles they respond to---in a
6461 hierarchical fashion.
6463 Threading is done by looking at the @code{References} headers of the
6464 articles. In a perfect world, this would be enough to build pretty
6465 trees, but unfortunately, the @code{References} header is often broken
6466 or simply missing. Weird news propagation exacerbates the problem,
6467 so one has to employ other heuristics to get pleasing results. A
6468 plethora of approaches exists, as detailed in horrible detail in
6469 @ref{Customizing Threading}.
6471 First, a quick overview of the concepts:
6475 The top-most article in a thread; the first article in the thread.
6478 A tree-like article structure.
6481 A small(er) section of this tree-like structure.
6484 Threads often lose their roots due to article expiry, or due to the root
6485 already having been read in a previous session, and not displayed in the
6486 summary buffer. We then typically have many sub-threads that really
6487 belong to one thread, but are without connecting roots. These are
6488 called loose threads.
6490 @item thread gathering
6491 An attempt to gather loose threads into bigger threads.
6493 @item sparse threads
6494 A thread where the missing articles have been ``guessed'' at, and are
6495 displayed as empty lines in the summary buffer.
6501 * Customizing Threading:: Variables you can change to affect the threading.
6502 * Thread Commands:: Thread based commands in the summary buffer.
6506 @node Customizing Threading
6507 @subsection Customizing Threading
6508 @cindex customizing threading
6511 * Loose Threads:: How Gnus gathers loose threads into bigger threads.
6512 * Filling In Threads:: Making the threads displayed look fuller.
6513 * More Threading:: Even more variables for fiddling with threads.
6514 * Low-Level Threading:: You thought it was over@dots{} but you were wrong!
6519 @subsubsection Loose Threads
6522 @cindex loose threads
6525 @item gnus-summary-make-false-root
6526 @vindex gnus-summary-make-false-root
6527 If non-@code{nil}, Gnus will gather all loose subtrees into one big tree
6528 and create a dummy root at the top. (Wait a minute. Root at the top?
6529 Yup.) Loose subtrees occur when the real root has expired, or you've
6530 read or killed the root in a previous session.
6532 When there is no real root of a thread, Gnus will have to fudge
6533 something. This variable says what fudging method Gnus should use.
6534 There are four possible values:
6538 \gnusfigure{The Summary Buffer}{390}{
6539 \put(0,0){\epsfig{figure=ps/summary-adopt,width=7.5cm}}
6540 \put(445,0){\makebox(0,0)[br]{\epsfig{figure=ps/summary-empty,width=7.5cm}}}
6541 \put(0,400){\makebox(0,0)[tl]{\epsfig{figure=ps/summary-none,width=7.5cm}}}
6542 \put(445,400){\makebox(0,0)[tr]{\epsfig{figure=ps/summary-dummy,width=7.5cm}}}
6547 @cindex adopting articles
6552 Gnus will make the first of the orphaned articles the parent. This
6553 parent will adopt all the other articles. The adopted articles will be
6554 marked as such by pointy brackets (@samp{<>}) instead of the standard
6555 square brackets (@samp{[]}). This is the default method.
6558 @vindex gnus-summary-dummy-line-format
6559 @vindex gnus-summary-make-false-root-always
6560 Gnus will create a dummy summary line that will pretend to be the
6561 parent. This dummy line does not correspond to any real article, so
6562 selecting it will just select the first real article after the dummy
6563 article. @code{gnus-summary-dummy-line-format} is used to specify the
6564 format of the dummy roots. It accepts only one format spec: @samp{S},
6565 which is the subject of the article. @xref{Formatting Variables}.
6566 If you want all threads to have a dummy root, even the non-gathered
6567 ones, set @code{gnus-summary-make-false-root-always} to @code{t}.
6570 Gnus won't actually make any article the parent, but simply leave the
6571 subject field of all orphans except the first empty. (Actually, it will
6572 use @code{gnus-summary-same-subject} as the subject (@pxref{Summary
6576 Don't make any article parent at all. Just gather the threads and
6577 display them after one another.
6580 Don't gather loose threads.
6583 @item gnus-summary-gather-subject-limit
6584 @vindex gnus-summary-gather-subject-limit
6585 Loose threads are gathered by comparing subjects of articles. If this
6586 variable is @code{nil}, Gnus requires an exact match between the
6587 subjects of the loose threads before gathering them into one big
6588 super-thread. This might be too strict a requirement, what with the
6589 presence of stupid newsreaders that chop off long subject lines. If
6590 you think so, set this variable to, say, 20 to require that only the
6591 first 20 characters of the subjects have to match. If you set this
6592 variable to a really low number, you'll find that Gnus will gather
6593 everything in sight into one thread, which isn't very helpful.
6595 @cindex fuzzy article gathering
6596 If you set this variable to the special value @code{fuzzy}, Gnus will
6597 use a fuzzy string comparison algorithm on the subjects (@pxref{Fuzzy
6600 @item gnus-simplify-subject-fuzzy-regexp
6601 @vindex gnus-simplify-subject-fuzzy-regexp
6602 This can either be a regular expression or list of regular expressions
6603 that match strings that will be removed from subjects if fuzzy subject
6604 simplification is used.
6606 @item gnus-simplify-ignored-prefixes
6607 @vindex gnus-simplify-ignored-prefixes
6608 If you set @code{gnus-summary-gather-subject-limit} to something as low
6609 as 10, you might consider setting this variable to something sensible:
6611 @c Written by Michael Ernst <mernst@cs.rice.edu>
6613 (setq gnus-simplify-ignored-prefixes
6619 "wanted" "followup" "summary\\( of\\)?"
6620 "help" "query" "problem" "question"
6621 "answer" "reference" "announce"
6622 "How can I" "How to" "Comparison of"
6627 (mapconcat 'identity
6628 '("for" "for reference" "with" "about")
6630 "\\)?\\]?:?[ \t]*"))
6633 All words that match this regexp will be removed before comparing two
6636 @item gnus-simplify-subject-functions
6637 @vindex gnus-simplify-subject-functions
6638 If non-@code{nil}, this variable overrides
6639 @code{gnus-summary-gather-subject-limit}. This variable should be a
6640 list of functions to apply to the @code{Subject} string iteratively to
6641 arrive at the simplified version of the string.
6643 Useful functions to put in this list include:
6646 @item gnus-simplify-subject-re
6647 @findex gnus-simplify-subject-re
6648 Strip the leading @samp{Re:}.
6650 @item gnus-simplify-subject-fuzzy
6651 @findex gnus-simplify-subject-fuzzy
6654 @item gnus-simplify-whitespace
6655 @findex gnus-simplify-whitespace
6656 Remove excessive whitespace.
6658 @item gnus-simplify-all-whitespace
6659 @findex gnus-simplify-all-whitespace
6660 Remove all whitespace.
6663 You may also write your own functions, of course.
6666 @item gnus-summary-gather-exclude-subject
6667 @vindex gnus-summary-gather-exclude-subject
6668 Since loose thread gathering is done on subjects only, that might lead
6669 to many false hits, especially with certain common subjects like
6670 @samp{} and @samp{(none)}. To make the situation slightly better,
6671 you can use the regexp @code{gnus-summary-gather-exclude-subject} to say
6672 what subjects should be excluded from the gathering process.@*
6673 The default is @samp{^ *$\\|^(none)$}.
6675 @item gnus-summary-thread-gathering-function
6676 @vindex gnus-summary-thread-gathering-function
6677 Gnus gathers threads by looking at @code{Subject} headers. This means
6678 that totally unrelated articles may end up in the same ``thread'', which
6679 is confusing. An alternate approach is to look at all the
6680 @code{Message-ID}s in all the @code{References} headers to find matches.
6681 This will ensure that no gathered threads ever include unrelated
6682 articles, but it also means that people who have posted with broken
6683 newsreaders won't be gathered properly. The choice is yours---plague or
6687 @item gnus-gather-threads-by-subject
6688 @findex gnus-gather-threads-by-subject
6689 This function is the default gathering function and looks at
6690 @code{Subject}s exclusively.
6692 @item gnus-gather-threads-by-references
6693 @findex gnus-gather-threads-by-references
6694 This function looks at @code{References} headers exclusively.
6697 If you want to test gathering by @code{References}, you could say
6701 (setq gnus-summary-thread-gathering-function
6702 'gnus-gather-threads-by-references)
6708 @node Filling In Threads
6709 @subsubsection Filling In Threads
6712 @item gnus-fetch-old-headers
6713 @vindex gnus-fetch-old-headers
6714 If non-@code{nil}, Gnus will attempt to build old threads by fetching
6715 more old headers---headers to articles marked as read. If you would
6716 like to display as few summary lines as possible, but still connect as
6717 many loose threads as possible, you should set this variable to
6718 @code{some} or a number. If you set it to a number, no more than that
6719 number of extra old headers will be fetched. In either case, fetching
6720 old headers only works if the back end you are using carries overview
6721 files---this would normally be @code{nntp}, @code{nnspool},
6722 @code{nnml}, and @code{nnmaildir}. Also remember that if the root of
6723 the thread has been expired by the server, there's not much Gnus can
6726 This variable can also be set to @code{invisible}. This won't have any
6727 visible effects, but is useful if you use the @kbd{A T} command a lot
6728 (@pxref{Finding the Parent}).
6730 @item gnus-fetch-old-ephemeral-headers
6731 @vindex gnus-fetch-old-ephemeral-headers
6732 Same as @code{gnus-fetch-old-headers}, but only used for ephemeral
6735 @item gnus-build-sparse-threads
6736 @vindex gnus-build-sparse-threads
6737 Fetching old headers can be slow. A low-rent similar effect can be
6738 gotten by setting this variable to @code{some}. Gnus will then look at
6739 the complete @code{References} headers of all articles and try to string
6740 together articles that belong in the same thread. This will leave
6741 @dfn{gaps} in the threading display where Gnus guesses that an article
6742 is missing from the thread. (These gaps appear like normal summary
6743 lines. If you select a gap, Gnus will try to fetch the article in
6744 question.) If this variable is @code{t}, Gnus will display all these
6745 ``gaps'' without regard for whether they are useful for completing the
6746 thread or not. Finally, if this variable is @code{more}, Gnus won't cut
6747 off sparse leaf nodes that don't lead anywhere. This variable is
6748 @code{nil} by default.
6750 @item gnus-read-all-available-headers
6751 @vindex gnus-read-all-available-headers
6752 This is a rather obscure variable that few will find useful. It's
6753 intended for those non-news newsgroups where the back end has to fetch
6754 quite a lot to present the summary buffer, and where it's impossible to
6755 go back to parents of articles. This is mostly the case in the
6756 web-based groups, like the @code{nnultimate} groups.
6758 If you don't use those, then it's safe to leave this as the default
6759 @code{nil}. If you want to use this variable, it should be a regexp
6760 that matches the group name, or @code{t} for all groups.
6765 @node More Threading
6766 @subsubsection More Threading
6769 @item gnus-show-threads
6770 @vindex gnus-show-threads
6771 If this variable is @code{nil}, no threading will be done, and all of
6772 the rest of the variables here will have no effect. Turning threading
6773 off will speed group selection up a bit, but it is sure to make reading
6774 slower and more awkward.
6776 @item gnus-thread-hide-subtree
6777 @vindex gnus-thread-hide-subtree
6778 If non-@code{nil}, all threads will be hidden when the summary buffer is
6781 This can also be a predicate specifier (@pxref{Predicate Specifiers}).
6782 Available predicates are @code{gnus-article-unread-p} and
6783 @code{gnus-article-unseen-p}.
6788 (setq gnus-thread-hide-subtree
6789 '(or gnus-article-unread-p
6790 gnus-article-unseen-p))
6793 (It's a pretty nonsensical example, since all unseen articles are also
6794 unread, but you get my drift.)
6797 @item gnus-thread-expunge-below
6798 @vindex gnus-thread-expunge-below
6799 All threads that have a total score (as defined by
6800 @code{gnus-thread-score-function}) less than this number will be
6801 expunged. This variable is @code{nil} by default, which means that no
6802 threads are expunged.
6804 @item gnus-thread-hide-killed
6805 @vindex gnus-thread-hide-killed
6806 if you kill a thread and this variable is non-@code{nil}, the subtree
6809 @item gnus-thread-ignore-subject
6810 @vindex gnus-thread-ignore-subject
6811 Sometimes somebody changes the subject in the middle of a thread. If
6812 this variable is non-@code{nil}, which is the default, the subject
6813 change is ignored. If it is @code{nil}, a change in the subject will
6814 result in a new thread.
6816 @item gnus-thread-indent-level
6817 @vindex gnus-thread-indent-level
6818 This is a number that says how much each sub-thread should be indented.
6821 @item gnus-sort-gathered-threads-function
6822 @vindex gnus-sort-gathered-threads-function
6823 Sometimes, particularly with mailing lists, the order in which mails
6824 arrive locally is not necessarily the same as the order in which they
6825 arrived on the mailing list. Consequently, when sorting sub-threads
6826 using the default @code{gnus-thread-sort-by-number}, responses can end
6827 up appearing before the article to which they are responding to.
6828 Setting this variable to an alternate value
6829 (e.g. @code{gnus-thread-sort-by-date}), in a group's parameters or in an
6830 appropriate hook (e.g. @code{gnus-summary-generate-hook}) can produce a
6831 more logical sub-thread ordering in such instances.
6836 @node Low-Level Threading
6837 @subsubsection Low-Level Threading
6841 @item gnus-parse-headers-hook
6842 @vindex gnus-parse-headers-hook
6843 Hook run before parsing any headers.
6845 @item gnus-alter-header-function
6846 @vindex gnus-alter-header-function
6847 If non-@code{nil}, this function will be called to allow alteration of
6848 article header structures. The function is called with one parameter,
6849 the article header vector, which it may alter in any way. For instance,
6850 if you have a mail-to-news gateway which alters the @code{Message-ID}s
6851 in systematic ways (by adding prefixes and such), you can use this
6852 variable to un-scramble the @code{Message-ID}s so that they are more
6853 meaningful. Here's one example:
6856 (setq gnus-alter-header-function 'my-alter-message-id)
6858 (defun my-alter-message-id (header)
6859 (let ((id (mail-header-id header)))
6861 "\\(<[^<>@@]*\\)\\.?cygnus\\..*@@\\([^<>@@]*>\\)" id)
6863 (concat (match-string 1 id) "@@" (match-string 2 id))
6870 @node Thread Commands
6871 @subsection Thread Commands
6872 @cindex thread commands
6878 @kindex T k (Summary)
6879 @kindex C-M-k (Summary)
6880 @findex gnus-summary-kill-thread
6881 Mark all articles in the current (sub-)thread as read
6882 (@code{gnus-summary-kill-thread}). If the prefix argument is positive,
6883 remove all marks instead. If the prefix argument is negative, tick
6888 @kindex T l (Summary)
6889 @kindex C-M-l (Summary)
6890 @findex gnus-summary-lower-thread
6891 Lower the score of the current (sub-)thread
6892 (@code{gnus-summary-lower-thread}).
6895 @kindex T i (Summary)
6896 @findex gnus-summary-raise-thread
6897 Increase the score of the current (sub-)thread
6898 (@code{gnus-summary-raise-thread}).
6901 @kindex T # (Summary)
6902 @findex gnus-uu-mark-thread
6903 Set the process mark on the current (sub-)thread
6904 (@code{gnus-uu-mark-thread}).
6907 @kindex T M-# (Summary)
6908 @findex gnus-uu-unmark-thread
6909 Remove the process mark from the current (sub-)thread
6910 (@code{gnus-uu-unmark-thread}).
6913 @kindex T T (Summary)
6914 @findex gnus-summary-toggle-threads
6915 Toggle threading (@code{gnus-summary-toggle-threads}).
6918 @kindex T s (Summary)
6919 @findex gnus-summary-show-thread
6920 Expose the (sub-)thread hidden under the current article, if any@*
6921 (@code{gnus-summary-show-thread}).
6924 @kindex T h (Summary)
6925 @findex gnus-summary-hide-thread
6926 Hide the current (sub-)thread (@code{gnus-summary-hide-thread}).
6929 @kindex T S (Summary)
6930 @findex gnus-summary-show-all-threads
6931 Expose all hidden threads (@code{gnus-summary-show-all-threads}).
6934 @kindex T H (Summary)
6935 @findex gnus-summary-hide-all-threads
6936 Hide all threads (@code{gnus-summary-hide-all-threads}).
6939 @kindex T t (Summary)
6940 @findex gnus-summary-rethread-current
6941 Re-thread the current article's thread
6942 (@code{gnus-summary-rethread-current}). This works even when the
6943 summary buffer is otherwise unthreaded.
6946 @kindex T ^ (Summary)
6947 @findex gnus-summary-reparent-thread
6948 Make the current article the child of the marked (or previous) article
6949 (@code{gnus-summary-reparent-thread}).
6953 The following commands are thread movement commands. They all
6954 understand the numeric prefix.
6959 @kindex T n (Summary)
6961 @kindex C-M-n (Summary)
6963 @kindex M-down (Summary)
6964 @findex gnus-summary-next-thread
6965 Go to the next thread (@code{gnus-summary-next-thread}).
6968 @kindex T p (Summary)
6970 @kindex C-M-p (Summary)
6972 @kindex M-up (Summary)
6973 @findex gnus-summary-prev-thread
6974 Go to the previous thread (@code{gnus-summary-prev-thread}).
6977 @kindex T d (Summary)
6978 @findex gnus-summary-down-thread
6979 Descend the thread (@code{gnus-summary-down-thread}).
6982 @kindex T u (Summary)
6983 @findex gnus-summary-up-thread
6984 Ascend the thread (@code{gnus-summary-up-thread}).
6987 @kindex T o (Summary)
6988 @findex gnus-summary-top-thread
6989 Go to the top of the thread (@code{gnus-summary-top-thread}).
6992 @vindex gnus-thread-operation-ignore-subject
6993 If you ignore subject while threading, you'll naturally end up with
6994 threads that have several different subjects in them. If you then issue
6995 a command like @kbd{T k} (@code{gnus-summary-kill-thread}) you might not
6996 wish to kill the entire thread, but just those parts of the thread that
6997 have the same subject as the current article. If you like this idea,
6998 you can fiddle with @code{gnus-thread-operation-ignore-subject}. If it
6999 is non-@code{nil} (which it is by default), subjects will be ignored
7000 when doing thread commands. If this variable is @code{nil}, articles in
7001 the same thread with different subjects will not be included in the
7002 operation in question. If this variable is @code{fuzzy}, only articles
7003 that have subjects fuzzily equal will be included (@pxref{Fuzzy
7007 @node Sorting the Summary Buffer
7008 @section Sorting the Summary Buffer
7010 @findex gnus-thread-sort-by-total-score
7011 @findex gnus-thread-sort-by-date
7012 @findex gnus-thread-sort-by-score
7013 @findex gnus-thread-sort-by-subject
7014 @findex gnus-thread-sort-by-author
7015 @c @findex gnus-thread-sort-by-recipient
7016 @findex gnus-thread-sort-by-number
7017 @findex gnus-thread-sort-by-random
7018 @vindex gnus-thread-sort-functions
7019 @findex gnus-thread-sort-by-most-recent-number
7020 @findex gnus-thread-sort-by-most-recent-date
7021 If you are using a threaded summary display, you can sort the threads by
7022 setting @code{gnus-thread-sort-functions}, which can be either a single
7023 function, a list of functions, or a list containing functions and
7024 @code{(not some-function)} elements.
7026 By default, sorting is done on article numbers. Ready-made sorting
7027 predicate functions include @code{gnus-thread-sort-by-number},
7028 @code{gnus-thread-sort-by-author}, @code{gnus-thread-sort-by-subject},
7029 @code{gnus-thread-sort-by-date}, @code{gnus-thread-sort-by-score},
7030 @code{gnus-thread-sort-by-most-recent-number},
7031 @code{gnus-thread-sort-by-most-recent-date},
7032 @code{gnus-thread-sort-by-random} and
7033 @code{gnus-thread-sort-by-total-score}.
7035 Each function takes two threads and returns non-@code{nil} if the first
7036 thread should be sorted before the other. Note that sorting really is
7037 normally done by looking only at the roots of each thread.
7039 If you use more than one function, the primary sort key should be the
7040 last function in the list. You should probably always include
7041 @code{gnus-thread-sort-by-number} in the list of sorting
7042 functions---preferably first. This will ensure that threads that are
7043 equal with respect to the other sort criteria will be displayed in
7044 ascending article order.
7046 If you would like to sort by reverse score, then by subject, and finally
7047 by number, you could do something like:
7050 (setq gnus-thread-sort-functions
7051 '(gnus-thread-sort-by-number
7052 gnus-thread-sort-by-subject
7053 (not gnus-thread-sort-by-total-score)))
7056 The threads that have highest score will be displayed first in the
7057 summary buffer. When threads have the same score, they will be sorted
7058 alphabetically. The threads that have the same score and the same
7059 subject will be sorted by number, which is (normally) the sequence in
7060 which the articles arrived.
7062 If you want to sort by score and then reverse arrival order, you could
7066 (setq gnus-thread-sort-functions
7068 (not (gnus-thread-sort-by-number t1 t2)))
7069 gnus-thread-sort-by-score))
7072 @vindex gnus-thread-score-function
7073 The function in the @code{gnus-thread-score-function} variable (default
7074 @code{+}) is used for calculating the total score of a thread. Useful
7075 functions might be @code{max}, @code{min}, or squared means, or whatever
7078 @findex gnus-article-sort-functions
7079 @findex gnus-article-sort-by-date
7080 @findex gnus-article-sort-by-score
7081 @findex gnus-article-sort-by-subject
7082 @findex gnus-article-sort-by-author
7083 @findex gnus-article-sort-by-random
7084 @findex gnus-article-sort-by-number
7085 If you are using an unthreaded display for some strange reason or
7086 other, you have to fiddle with the @code{gnus-article-sort-functions}
7087 variable. It is very similar to the
7088 @code{gnus-thread-sort-functions}, except that it uses slightly
7089 different functions for article comparison. Available sorting
7090 predicate functions are @code{gnus-article-sort-by-number},
7091 @code{gnus-article-sort-by-author},
7092 @code{gnus-article-sort-by-subject}, @code{gnus-article-sort-by-date},
7093 @code{gnus-article-sort-by-random}, and
7094 @code{gnus-article-sort-by-score}.
7096 If you want to sort an unthreaded summary display by subject, you could
7100 (setq gnus-article-sort-functions
7101 '(gnus-article-sort-by-number
7102 gnus-article-sort-by-subject))
7107 @node Asynchronous Fetching
7108 @section Asynchronous Article Fetching
7109 @cindex asynchronous article fetching
7110 @cindex article pre-fetch
7113 If you read your news from an @acronym{NNTP} server that's far away, the
7114 network latencies may make reading articles a chore. You have to wait
7115 for a while after pressing @kbd{n} to go to the next article before the
7116 article appears. Why can't Gnus just go ahead and fetch the article
7117 while you are reading the previous one? Why not, indeed.
7119 First, some caveats. There are some pitfalls to using asynchronous
7120 article fetching, especially the way Gnus does it.
7122 Let's say you are reading article 1, which is short, and article 2 is
7123 quite long, and you are not interested in reading that. Gnus does not
7124 know this, so it goes ahead and fetches article 2. You decide to read
7125 article 3, but since Gnus is in the process of fetching article 2, the
7126 connection is blocked.
7128 To avoid these situations, Gnus will open two (count 'em two)
7129 connections to the server. Some people may think this isn't a very nice
7130 thing to do, but I don't see any real alternatives. Setting up that
7131 extra connection takes some time, so Gnus startup will be slower.
7133 Gnus will fetch more articles than you will read. This will mean that
7134 the link between your machine and the @acronym{NNTP} server will become more
7135 loaded than if you didn't use article pre-fetch. The server itself will
7136 also become more loaded---both with the extra article requests, and the
7139 Ok, so now you know that you shouldn't really use this thing@dots{} unless
7142 @vindex gnus-asynchronous
7143 Here's how: Set @code{gnus-asynchronous} to @code{t}. The rest should
7144 happen automatically.
7146 @vindex gnus-use-article-prefetch
7147 You can control how many articles are to be pre-fetched by setting
7148 @code{gnus-use-article-prefetch}. This is 30 by default, which means
7149 that when you read an article in the group, the back end will pre-fetch
7150 the next 30 articles. If this variable is @code{t}, the back end will
7151 pre-fetch all the articles it can without bound. If it is
7152 @code{nil}, no pre-fetching will be done.
7154 @vindex gnus-async-prefetch-article-p
7155 @findex gnus-async-read-p
7156 There are probably some articles that you don't want to pre-fetch---read
7157 articles, for instance. The @code{gnus-async-prefetch-article-p}
7158 variable controls whether an article is to be pre-fetched. This
7159 function should return non-@code{nil} when the article in question is
7160 to be pre-fetched. The default is @code{gnus-async-read-p}, which
7161 returns @code{nil} on read articles. The function is called with an
7162 article data structure as the only parameter.
7164 If, for instance, you wish to pre-fetch only unread articles shorter
7165 than 100 lines, you could say something like:
7168 (defun my-async-short-unread-p (data)
7169 "Return non-nil for short, unread articles."
7170 (and (gnus-data-unread-p data)
7171 (< (mail-header-lines (gnus-data-header data))
7174 (setq gnus-async-prefetch-article-p 'my-async-short-unread-p)
7177 These functions will be called many, many times, so they should
7178 preferably be short and sweet to avoid slowing down Gnus too much.
7179 It's probably a good idea to byte-compile things like this.
7181 @vindex gnus-prefetched-article-deletion-strategy
7182 Articles have to be removed from the asynch buffer sooner or later. The
7183 @code{gnus-prefetched-article-deletion-strategy} says when to remove
7184 articles. This is a list that may contain the following elements:
7188 Remove articles when they are read.
7191 Remove articles when exiting the group.
7194 The default value is @code{(read exit)}.
7196 @c @vindex gnus-use-header-prefetch
7197 @c If @code{gnus-use-header-prefetch} is non-@code{nil}, prefetch articles
7198 @c from the next group.
7201 @node Article Caching
7202 @section Article Caching
7203 @cindex article caching
7206 If you have an @emph{extremely} slow @acronym{NNTP} connection, you may
7207 consider turning article caching on. Each article will then be stored
7208 locally under your home directory. As you may surmise, this could
7209 potentially use @emph{huge} amounts of disk space, as well as eat up all
7210 your inodes so fast it will make your head swim. In vodka.
7212 Used carefully, though, it could be just an easier way to save articles.
7214 @vindex gnus-use-long-file-name
7215 @vindex gnus-cache-directory
7216 @vindex gnus-use-cache
7217 To turn caching on, set @code{gnus-use-cache} to @code{t}. By default,
7218 all articles ticked or marked as dormant will then be copied
7219 over to your local cache (@code{gnus-cache-directory}). Whether this
7220 cache is flat or hierarchical is controlled by the
7221 @code{gnus-use-long-file-name} variable, as usual.
7223 When re-selecting a ticked or dormant article, it will be fetched from the
7224 cache instead of from the server. As articles in your cache will never
7225 expire, this might serve as a method of saving articles while still
7226 keeping them where they belong. Just mark all articles you want to save
7227 as dormant, and don't worry.
7229 When an article is marked as read, is it removed from the cache.
7231 @vindex gnus-cache-remove-articles
7232 @vindex gnus-cache-enter-articles
7233 The entering/removal of articles from the cache is controlled by the
7234 @code{gnus-cache-enter-articles} and @code{gnus-cache-remove-articles}
7235 variables. Both are lists of symbols. The first is @code{(ticked
7236 dormant)} by default, meaning that ticked and dormant articles will be
7237 put in the cache. The latter is @code{(read)} by default, meaning that
7238 articles marked as read are removed from the cache. Possibly
7239 symbols in these two lists are @code{ticked}, @code{dormant},
7240 @code{unread} and @code{read}.
7242 @findex gnus-jog-cache
7243 So where does the massive article-fetching and storing come into the
7244 picture? The @code{gnus-jog-cache} command will go through all
7245 subscribed newsgroups, request all unread articles, score them, and
7246 store them in the cache. You should only ever, ever ever ever, use this
7247 command if 1) your connection to the @acronym{NNTP} server is really, really,
7248 really slow and 2) you have a really, really, really huge disk.
7249 Seriously. One way to cut down on the number of articles downloaded is
7250 to score unwanted articles down and have them marked as read. They will
7251 not then be downloaded by this command.
7253 @vindex gnus-uncacheable-groups
7254 @vindex gnus-cacheable-groups
7255 It is likely that you do not want caching on all groups. For instance,
7256 if your @code{nnml} mail is located under your home directory, it makes no
7257 sense to cache it somewhere else under your home directory. Unless you
7258 feel that it's neat to use twice as much space.
7260 To limit the caching, you could set @code{gnus-cacheable-groups} to a
7261 regexp of groups to cache, @samp{^nntp} for instance, or set the
7262 @code{gnus-uncacheable-groups} regexp to @samp{^nnml}, for instance.
7263 Both variables are @code{nil} by default. If a group matches both
7264 variables, the group is not cached.
7266 @findex gnus-cache-generate-nov-databases
7267 @findex gnus-cache-generate-active
7268 @vindex gnus-cache-active-file
7269 The cache stores information on what articles it contains in its active
7270 file (@code{gnus-cache-active-file}). If this file (or any other parts
7271 of the cache) becomes all messed up for some reason or other, Gnus
7272 offers two functions that will try to set things right. @kbd{M-x
7273 gnus-cache-generate-nov-databases} will (re)build all the @acronym{NOV}
7274 files, and @kbd{gnus-cache-generate-active} will (re)generate the active
7277 @findex gnus-cache-move-cache
7278 @code{gnus-cache-move-cache} will move your whole
7279 @code{gnus-cache-directory} to some other location. You get asked to
7280 where, isn't that cool?
7282 @node Persistent Articles
7283 @section Persistent Articles
7284 @cindex persistent articles
7286 Closely related to article caching, we have @dfn{persistent articles}.
7287 In fact, it's just a different way of looking at caching, and much more
7288 useful in my opinion.
7290 Say you're reading a newsgroup, and you happen on to some valuable gem
7291 that you want to keep and treasure forever. You'd normally just save it
7292 (using one of the many saving commands) in some file. The problem with
7293 that is that it's just, well, yucky. Ideally you'd prefer just having
7294 the article remain in the group where you found it forever; untouched by
7295 the expiry going on at the news server.
7297 This is what a @dfn{persistent article} is---an article that just won't
7298 be deleted. It's implemented using the normal cache functions, but
7299 you use two explicit commands for managing persistent articles:
7305 @findex gnus-cache-enter-article
7306 Make the current article persistent (@code{gnus-cache-enter-article}).
7309 @kindex M-* (Summary)
7310 @findex gnus-cache-remove-article
7311 Remove the current article from the persistent articles
7312 (@code{gnus-cache-remove-article}). This will normally delete the
7316 Both these commands understand the process/prefix convention.
7318 To avoid having all ticked articles (and stuff) entered into the cache,
7319 you should set @code{gnus-use-cache} to @code{passive} if you're just
7320 interested in persistent articles:
7323 (setq gnus-use-cache 'passive)
7327 @node Article Backlog
7328 @section Article Backlog
7330 @cindex article backlog
7332 If you have a slow connection, but the idea of using caching seems
7333 unappealing to you (and it is, really), you can help the situation some
7334 by switching on the @dfn{backlog}. This is where Gnus will buffer
7335 already read articles so that it doesn't have to re-fetch articles
7336 you've already read. This only helps if you are in the habit of
7337 re-selecting articles you've recently read, of course. If you never do
7338 that, turning the backlog on will slow Gnus down a little bit, and
7339 increase memory usage some.
7341 @vindex gnus-keep-backlog
7342 If you set @code{gnus-keep-backlog} to a number @var{n}, Gnus will store
7343 at most @var{n} old articles in a buffer for later re-fetching. If this
7344 variable is non-@code{nil} and is not a number, Gnus will store
7345 @emph{all} read articles, which means that your Emacs will grow without
7346 bound before exploding and taking your machine down with you. I put
7347 that in there just to keep y'all on your toes.
7349 The default value is 20.
7352 @node Saving Articles
7353 @section Saving Articles
7354 @cindex saving articles
7356 Gnus can save articles in a number of ways. Below is the documentation
7357 for saving articles in a fairly straight-forward fashion (i.e., little
7358 processing of the article is done before it is saved). For a different
7359 approach (uudecoding, unsharing) you should use @code{gnus-uu}
7360 (@pxref{Decoding Articles}).
7362 For the commands listed here, the target is a file. If you want to
7363 save to a group, see the @kbd{B c} (@code{gnus-summary-copy-article})
7364 command (@pxref{Mail Group Commands}).
7366 @vindex gnus-save-all-headers
7367 If @code{gnus-save-all-headers} is non-@code{nil}, Gnus will not delete
7368 unwanted headers before saving the article.
7370 @vindex gnus-saved-headers
7371 If the preceding variable is @code{nil}, all headers that match the
7372 @code{gnus-saved-headers} regexp will be kept, while the rest will be
7373 deleted before saving.
7379 @kindex O o (Summary)
7381 @findex gnus-summary-save-article
7382 @c @icon{gnus-summary-save-article}
7383 Save the current article using the default article saver
7384 (@code{gnus-summary-save-article}).
7387 @kindex O m (Summary)
7388 @findex gnus-summary-save-article-mail
7389 Save the current article in mail format
7390 (@code{gnus-summary-save-article-mail}).
7393 @kindex O r (Summary)
7394 @findex gnus-summary-save-article-rmail
7395 Save the current article in Rmail format
7396 (@code{gnus-summary-save-article-rmail}).
7399 @kindex O f (Summary)
7400 @findex gnus-summary-save-article-file
7401 @c @icon{gnus-summary-save-article-file}
7402 Save the current article in plain file format
7403 (@code{gnus-summary-save-article-file}).
7406 @kindex O F (Summary)
7407 @findex gnus-summary-write-article-file
7408 Write the current article in plain file format, overwriting any previous
7409 file contents (@code{gnus-summary-write-article-file}).
7412 @kindex O b (Summary)
7413 @findex gnus-summary-save-article-body-file
7414 Save the current article body in plain file format
7415 (@code{gnus-summary-save-article-body-file}).
7418 @kindex O h (Summary)
7419 @findex gnus-summary-save-article-folder
7420 Save the current article in mh folder format
7421 (@code{gnus-summary-save-article-folder}).
7424 @kindex O v (Summary)
7425 @findex gnus-summary-save-article-vm
7426 Save the current article in a VM folder
7427 (@code{gnus-summary-save-article-vm}).
7431 @kindex O p (Summary)
7433 @findex gnus-summary-pipe-output
7434 Save the current article in a pipe. Uhm, like, what I mean is---Pipe
7435 the current article to a process (@code{gnus-summary-pipe-output}).
7436 If given a symbolic prefix (@pxref{Symbolic Prefixes}), include the
7437 complete headers in the piped output.
7440 @kindex O P (Summary)
7441 @findex gnus-summary-muttprint
7442 @vindex gnus-summary-muttprint-program
7443 Save the current article into muttprint. That is, print it using the
7444 external program @uref{http://muttprint.sourceforge.net/,
7445 Muttprint}. The program name and options to use is controlled by the
7446 variable @code{gnus-summary-muttprint-program}.
7447 (@code{gnus-summary-muttprint}).
7451 @vindex gnus-prompt-before-saving
7452 All these commands use the process/prefix convention
7453 (@pxref{Process/Prefix}). If you save bunches of articles using these
7454 functions, you might get tired of being prompted for files to save each
7455 and every article in. The prompting action is controlled by
7456 the @code{gnus-prompt-before-saving} variable, which is @code{always} by
7457 default, giving you that excessive prompting action you know and
7458 loathe. If you set this variable to @code{t} instead, you'll be prompted
7459 just once for each series of articles you save. If you like to really
7460 have Gnus do all your thinking for you, you can even set this variable
7461 to @code{nil}, which means that you will never be prompted for files to
7462 save articles in. Gnus will simply save all the articles in the default
7466 @vindex gnus-default-article-saver
7467 You can customize the @code{gnus-default-article-saver} variable to make
7468 Gnus do what you want it to. You can use any of the six ready-made
7469 functions below, or you can create your own.
7473 @item gnus-summary-save-in-rmail
7474 @findex gnus-summary-save-in-rmail
7475 @vindex gnus-rmail-save-name
7476 @findex gnus-plain-save-name
7477 This is the default format, @dfn{Babyl}. Uses the function in the
7478 @code{gnus-rmail-save-name} variable to get a file name to save the
7479 article in. The default is @code{gnus-plain-save-name}.
7481 @item gnus-summary-save-in-mail
7482 @findex gnus-summary-save-in-mail
7483 @vindex gnus-mail-save-name
7484 Save in a Unix mail (mbox) file. Uses the function in the
7485 @code{gnus-mail-save-name} variable to get a file name to save the
7486 article in. The default is @code{gnus-plain-save-name}.
7488 @item gnus-summary-save-in-file
7489 @findex gnus-summary-save-in-file
7490 @vindex gnus-file-save-name
7491 @findex gnus-numeric-save-name
7492 Append the article straight to an ordinary file. Uses the function in
7493 the @code{gnus-file-save-name} variable to get a file name to save the
7494 article in. The default is @code{gnus-numeric-save-name}.
7496 @item gnus-summary-write-to-file
7497 @findex gnus-summary-write-to-file
7498 Write the article straight to an ordinary file. The file is
7499 overwritten if it exists. Uses the function in the
7500 @code{gnus-file-save-name} variable to get a file name to save the
7501 article in. The default is @code{gnus-numeric-save-name}.
7503 @item gnus-summary-save-body-in-file
7504 @findex gnus-summary-save-body-in-file
7505 Append the article body to an ordinary file. Uses the function in the
7506 @code{gnus-file-save-name} variable to get a file name to save the
7507 article in. The default is @code{gnus-numeric-save-name}.
7509 @item gnus-summary-save-in-folder
7510 @findex gnus-summary-save-in-folder
7511 @findex gnus-folder-save-name
7512 @findex gnus-Folder-save-name
7513 @vindex gnus-folder-save-name
7516 Save the article to an MH folder using @code{rcvstore} from the MH
7517 library. Uses the function in the @code{gnus-folder-save-name} variable
7518 to get a file name to save the article in. The default is
7519 @code{gnus-folder-save-name}, but you can also use
7520 @code{gnus-Folder-save-name}, which creates capitalized names.
7522 @item gnus-summary-save-in-vm
7523 @findex gnus-summary-save-in-vm
7524 Save the article in a VM folder. You have to have the VM mail
7525 reader to use this setting.
7528 @vindex gnus-article-save-directory
7529 All of these functions, except for the last one, will save the article
7530 in the @code{gnus-article-save-directory}, which is initialized from the
7531 @env{SAVEDIR} environment variable. This is @file{~/News/} by
7534 As you can see above, the functions use different functions to find a
7535 suitable name of a file to save the article in. Below is a list of
7536 available functions that generate names:
7540 @item gnus-Numeric-save-name
7541 @findex gnus-Numeric-save-name
7542 File names like @file{~/News/Alt.andrea-dworkin/45}.
7544 @item gnus-numeric-save-name
7545 @findex gnus-numeric-save-name
7546 File names like @file{~/News/alt.andrea-dworkin/45}.
7548 @item gnus-Plain-save-name
7549 @findex gnus-Plain-save-name
7550 File names like @file{~/News/Alt.andrea-dworkin}.
7552 @item gnus-plain-save-name
7553 @findex gnus-plain-save-name
7554 File names like @file{~/News/alt.andrea-dworkin}.
7556 @item gnus-sender-save-name
7557 @findex gnus-sender-save-name
7558 File names like @file{~/News/larsi}.
7561 @vindex gnus-split-methods
7562 You can have Gnus suggest where to save articles by plonking a regexp into
7563 the @code{gnus-split-methods} alist. For instance, if you would like to
7564 save articles related to Gnus in the file @file{gnus-stuff}, and articles
7565 related to VM in @file{vm-stuff}, you could set this variable to something
7569 (("^Subject:.*gnus\\|^Newsgroups:.*gnus" "gnus-stuff")
7570 ("^Subject:.*vm\\|^Xref:.*vm" "vm-stuff")
7571 (my-choosing-function "../other-dir/my-stuff")
7572 ((equal gnus-newsgroup-name "mail.misc") "mail-stuff"))
7575 We see that this is a list where each element is a list that has two
7576 elements---the @dfn{match} and the @dfn{file}. The match can either be
7577 a string (in which case it is used as a regexp to match on the article
7578 head); it can be a symbol (which will be called as a function with the
7579 group name as a parameter); or it can be a list (which will be
7580 @code{eval}ed). If any of these actions have a non-@code{nil} result,
7581 the @dfn{file} will be used as a default prompt. In addition, the
7582 result of the operation itself will be used if the function or form
7583 called returns a string or a list of strings.
7585 You basically end up with a list of file names that might be used when
7586 saving the current article. (All ``matches'' will be used.) You will
7587 then be prompted for what you really want to use as a name, with file
7588 name completion over the results from applying this variable.
7590 This variable is @code{((gnus-article-archive-name))} by default, which
7591 means that Gnus will look at the articles it saves for an
7592 @code{Archive-name} line and use that as a suggestion for the file
7595 Here's an example function to clean up file names somewhat. If you have
7596 lots of mail groups called things like
7597 @samp{nnml:mail.whatever}, you may want to chop off the beginning of
7598 these group names before creating the file name to save to. The
7599 following will do just that:
7602 (defun my-save-name (group)
7603 (when (string-match "^nnml:mail." group)
7604 (substring group (match-end 0))))
7606 (setq gnus-split-methods
7607 '((gnus-article-archive-name)
7612 @vindex gnus-use-long-file-name
7613 Finally, you have the @code{gnus-use-long-file-name} variable. If it is
7614 @code{nil}, all the preceding functions will replace all periods
7615 (@samp{.}) in the group names with slashes (@samp{/})---which means that
7616 the functions will generate hierarchies of directories instead of having
7617 all the files in the top level directory
7618 (@file{~/News/alt/andrea-dworkin} instead of
7619 @file{~/News/alt.andrea-dworkin}.) This variable is @code{t} by default
7620 on most systems. However, for historical reasons, this is @code{nil} on
7621 Xenix and usg-unix-v machines by default.
7623 This function also affects kill and score file names. If this variable
7624 is a list, and the list contains the element @code{not-score}, long file
7625 names will not be used for score files, if it contains the element
7626 @code{not-save}, long file names will not be used for saving, and if it
7627 contains the element @code{not-kill}, long file names will not be used
7630 If you'd like to save articles in a hierarchy that looks something like
7634 (setq gnus-use-long-file-name '(not-save)) ; @r{to get a hierarchy}
7635 (setq gnus-default-article-saver
7636 'gnus-summary-save-in-file) ; @r{no encoding}
7639 Then just save with @kbd{o}. You'd then read this hierarchy with
7640 ephemeral @code{nneething} groups---@kbd{G D} in the group buffer, and
7641 the top level directory as the argument (@file{~/News/}). Then just walk
7642 around to the groups/directories with @code{nneething}.
7645 @node Decoding Articles
7646 @section Decoding Articles
7647 @cindex decoding articles
7649 Sometime users post articles (or series of articles) that have been
7650 encoded in some way or other. Gnus can decode them for you.
7653 * Uuencoded Articles:: Uudecode articles.
7654 * Shell Archives:: Unshar articles.
7655 * PostScript Files:: Split PostScript.
7656 * Other Files:: Plain save and binhex.
7657 * Decoding Variables:: Variables for a happy decoding.
7658 * Viewing Files:: You want to look at the result of the decoding?
7662 @cindex article series
7663 All these functions use the process/prefix convention
7664 (@pxref{Process/Prefix}) for finding out what articles to work on, with
7665 the extension that a ``single article'' means ``a single series''. Gnus
7666 can find out by itself what articles belong to a series, decode all the
7667 articles and unpack/view/save the resulting file(s).
7669 Gnus guesses what articles are in the series according to the following
7670 simplish rule: The subjects must be (nearly) identical, except for the
7671 last two numbers of the line. (Spaces are largely ignored, however.)
7673 For example: If you choose a subject called @samp{cat.gif (2/3)}, Gnus
7674 will find all the articles that match the regexp @samp{^cat.gif
7675 ([0-9]+/[0-9]+).*$}.
7677 Subjects that are non-standard, like @samp{cat.gif (2/3) Part 6 of a
7678 series}, will not be properly recognized by any of the automatic viewing
7679 commands, and you have to mark the articles manually with @kbd{#}.
7682 @node Uuencoded Articles
7683 @subsection Uuencoded Articles
7685 @cindex uuencoded articles
7690 @kindex X u (Summary)
7691 @findex gnus-uu-decode-uu
7692 @c @icon{gnus-uu-decode-uu}
7693 Uudecodes the current series (@code{gnus-uu-decode-uu}).
7696 @kindex X U (Summary)
7697 @findex gnus-uu-decode-uu-and-save
7698 Uudecodes and saves the current series
7699 (@code{gnus-uu-decode-uu-and-save}).
7702 @kindex X v u (Summary)
7703 @findex gnus-uu-decode-uu-view
7704 Uudecodes and views the current series (@code{gnus-uu-decode-uu-view}).
7707 @kindex X v U (Summary)
7708 @findex gnus-uu-decode-uu-and-save-view
7709 Uudecodes, views and saves the current series
7710 (@code{gnus-uu-decode-uu-and-save-view}).
7714 Remember that these all react to the presence of articles marked with
7715 the process mark. If, for instance, you'd like to decode and save an
7716 entire newsgroup, you'd typically do @kbd{M P a}
7717 (@code{gnus-uu-mark-all}) and then @kbd{X U}
7718 (@code{gnus-uu-decode-uu-and-save}).
7720 All this is very much different from how @code{gnus-uu} worked with
7721 @sc{gnus 4.1}, where you had explicit keystrokes for everything under
7722 the sun. This version of @code{gnus-uu} generally assumes that you mark
7723 articles in some way (@pxref{Setting Process Marks}) and then press
7726 @vindex gnus-uu-notify-files
7727 Note: When trying to decode articles that have names matching
7728 @code{gnus-uu-notify-files}, which is hard-coded to
7729 @samp{[Cc][Ii][Nn][Dd][Yy][0-9]+.\\(gif\\|jpg\\)}, @code{gnus-uu} will
7730 automatically post an article on @samp{comp.unix.wizards} saying that
7731 you have just viewed the file in question. This feature can't be turned
7735 @node Shell Archives
7736 @subsection Shell Archives
7738 @cindex shell archives
7739 @cindex shared articles
7741 Shell archives (``shar files'') used to be a popular way to distribute
7742 sources, but it isn't used all that much today. In any case, we have
7743 some commands to deal with these:
7748 @kindex X s (Summary)
7749 @findex gnus-uu-decode-unshar
7750 Unshars the current series (@code{gnus-uu-decode-unshar}).
7753 @kindex X S (Summary)
7754 @findex gnus-uu-decode-unshar-and-save
7755 Unshars and saves the current series (@code{gnus-uu-decode-unshar-and-save}).
7758 @kindex X v s (Summary)
7759 @findex gnus-uu-decode-unshar-view
7760 Unshars and views the current series (@code{gnus-uu-decode-unshar-view}).
7763 @kindex X v S (Summary)
7764 @findex gnus-uu-decode-unshar-and-save-view
7765 Unshars, views and saves the current series
7766 (@code{gnus-uu-decode-unshar-and-save-view}).
7770 @node PostScript Files
7771 @subsection PostScript Files
7777 @kindex X p (Summary)
7778 @findex gnus-uu-decode-postscript
7779 Unpack the current PostScript series (@code{gnus-uu-decode-postscript}).
7782 @kindex X P (Summary)
7783 @findex gnus-uu-decode-postscript-and-save
7784 Unpack and save the current PostScript series
7785 (@code{gnus-uu-decode-postscript-and-save}).
7788 @kindex X v p (Summary)
7789 @findex gnus-uu-decode-postscript-view
7790 View the current PostScript series
7791 (@code{gnus-uu-decode-postscript-view}).
7794 @kindex X v P (Summary)
7795 @findex gnus-uu-decode-postscript-and-save-view
7796 View and save the current PostScript series
7797 (@code{gnus-uu-decode-postscript-and-save-view}).
7802 @subsection Other Files
7806 @kindex X o (Summary)
7807 @findex gnus-uu-decode-save
7808 Save the current series
7809 (@code{gnus-uu-decode-save}).
7812 @kindex X b (Summary)
7813 @findex gnus-uu-decode-binhex
7814 Unbinhex the current series (@code{gnus-uu-decode-binhex}). This
7815 doesn't really work yet.
7819 @node Decoding Variables
7820 @subsection Decoding Variables
7822 Adjective, not verb.
7825 * Rule Variables:: Variables that say how a file is to be viewed.
7826 * Other Decode Variables:: Other decode variables.
7827 * Uuencoding and Posting:: Variables for customizing uuencoding.
7831 @node Rule Variables
7832 @subsubsection Rule Variables
7833 @cindex rule variables
7835 Gnus uses @dfn{rule variables} to decide how to view a file. All these
7836 variables are of the form
7839 (list '(regexp1 command2)
7846 @item gnus-uu-user-view-rules
7847 @vindex gnus-uu-user-view-rules
7849 This variable is consulted first when viewing files. If you wish to use,
7850 for instance, @code{sox} to convert an @file{.au} sound file, you could
7853 (setq gnus-uu-user-view-rules
7854 (list '("\\\\.au$" "sox %s -t .aiff > /dev/audio")))
7857 @item gnus-uu-user-view-rules-end
7858 @vindex gnus-uu-user-view-rules-end
7859 This variable is consulted if Gnus couldn't make any matches from the
7860 user and default view rules.
7862 @item gnus-uu-user-archive-rules
7863 @vindex gnus-uu-user-archive-rules
7864 This variable can be used to say what commands should be used to unpack
7869 @node Other Decode Variables
7870 @subsubsection Other Decode Variables
7873 @vindex gnus-uu-grabbed-file-functions
7875 @item gnus-uu-grabbed-file-functions
7876 All functions in this list will be called right after each file has been
7877 successfully decoded---so that you can move or view files right away,
7878 and don't have to wait for all files to be decoded before you can do
7879 anything. Ready-made functions you can put in this list are:
7883 @item gnus-uu-grab-view
7884 @findex gnus-uu-grab-view
7887 @item gnus-uu-grab-move
7888 @findex gnus-uu-grab-move
7889 Move the file (if you're using a saving function.)
7892 @item gnus-uu-be-dangerous
7893 @vindex gnus-uu-be-dangerous
7894 Specifies what to do if unusual situations arise during decoding. If
7895 @code{nil}, be as conservative as possible. If @code{t}, ignore things
7896 that didn't work, and overwrite existing files. Otherwise, ask each
7899 @item gnus-uu-ignore-files-by-name
7900 @vindex gnus-uu-ignore-files-by-name
7901 Files with name matching this regular expression won't be viewed.
7903 @item gnus-uu-ignore-files-by-type
7904 @vindex gnus-uu-ignore-files-by-type
7905 Files with a @acronym{MIME} type matching this variable won't be viewed.
7906 Note that Gnus tries to guess what type the file is based on the name.
7907 @code{gnus-uu} is not a @acronym{MIME} package (yet), so this is slightly
7910 @item gnus-uu-tmp-dir
7911 @vindex gnus-uu-tmp-dir
7912 Where @code{gnus-uu} does its work.
7914 @item gnus-uu-do-not-unpack-archives
7915 @vindex gnus-uu-do-not-unpack-archives
7916 Non-@code{nil} means that @code{gnus-uu} won't peek inside archives
7917 looking for files to display.
7919 @item gnus-uu-view-and-save
7920 @vindex gnus-uu-view-and-save
7921 Non-@code{nil} means that the user will always be asked to save a file
7924 @item gnus-uu-ignore-default-view-rules
7925 @vindex gnus-uu-ignore-default-view-rules
7926 Non-@code{nil} means that @code{gnus-uu} will ignore the default viewing
7929 @item gnus-uu-ignore-default-archive-rules
7930 @vindex gnus-uu-ignore-default-archive-rules
7931 Non-@code{nil} means that @code{gnus-uu} will ignore the default archive
7934 @item gnus-uu-kill-carriage-return
7935 @vindex gnus-uu-kill-carriage-return
7936 Non-@code{nil} means that @code{gnus-uu} will strip all carriage returns
7939 @item gnus-uu-unmark-articles-not-decoded
7940 @vindex gnus-uu-unmark-articles-not-decoded
7941 Non-@code{nil} means that @code{gnus-uu} will mark unsuccessfully
7942 decoded articles as unread.
7944 @item gnus-uu-correct-stripped-uucode
7945 @vindex gnus-uu-correct-stripped-uucode
7946 Non-@code{nil} means that @code{gnus-uu} will @emph{try} to fix
7947 uuencoded files that have had trailing spaces deleted.
7949 @item gnus-uu-pre-uudecode-hook
7950 @vindex gnus-uu-pre-uudecode-hook
7951 Hook run before sending a message to @code{uudecode}.
7953 @item gnus-uu-view-with-metamail
7954 @vindex gnus-uu-view-with-metamail
7956 Non-@code{nil} means that @code{gnus-uu} will ignore the viewing
7957 commands defined by the rule variables and just fudge a @acronym{MIME}
7958 content type based on the file name. The result will be fed to
7959 @code{metamail} for viewing.
7961 @item gnus-uu-save-in-digest
7962 @vindex gnus-uu-save-in-digest
7963 Non-@code{nil} means that @code{gnus-uu}, when asked to save without
7964 decoding, will save in digests. If this variable is @code{nil},
7965 @code{gnus-uu} will just save everything in a file without any
7966 embellishments. The digesting almost conforms to RFC 1153---no easy way
7967 to specify any meaningful volume and issue numbers were found, so I
7968 simply dropped them.
7973 @node Uuencoding and Posting
7974 @subsubsection Uuencoding and Posting
7978 @item gnus-uu-post-include-before-composing
7979 @vindex gnus-uu-post-include-before-composing
7980 Non-@code{nil} means that @code{gnus-uu} will ask for a file to encode
7981 before you compose the article. If this variable is @code{t}, you can
7982 either include an encoded file with @kbd{C-c C-i} or have one included
7983 for you when you post the article.
7985 @item gnus-uu-post-length
7986 @vindex gnus-uu-post-length
7987 Maximum length of an article. The encoded file will be split into how
7988 many articles it takes to post the entire file.
7990 @item gnus-uu-post-threaded
7991 @vindex gnus-uu-post-threaded
7992 Non-@code{nil} means that @code{gnus-uu} will post the encoded file in a
7993 thread. This may not be smart, as no other decoder I have seen is able
7994 to follow threads when collecting uuencoded articles. (Well, I have
7995 seen one package that does that---@code{gnus-uu}, but somehow, I don't
7996 think that counts@dots{}) Default is @code{nil}.
7998 @item gnus-uu-post-separate-description
7999 @vindex gnus-uu-post-separate-description
8000 Non-@code{nil} means that the description will be posted in a separate
8001 article. The first article will typically be numbered (0/x). If this
8002 variable is @code{nil}, the description the user enters will be included
8003 at the beginning of the first article, which will be numbered (1/x).
8004 Default is @code{t}.
8010 @subsection Viewing Files
8011 @cindex viewing files
8012 @cindex pseudo-articles
8014 After decoding, if the file is some sort of archive, Gnus will attempt
8015 to unpack the archive and see if any of the files in the archive can be
8016 viewed. For instance, if you have a gzipped tar file @file{pics.tar.gz}
8017 containing the files @file{pic1.jpg} and @file{pic2.gif}, Gnus will
8018 uncompress and de-tar the main file, and then view the two pictures.
8019 This unpacking process is recursive, so if the archive contains archives
8020 of archives, it'll all be unpacked.
8022 Finally, Gnus will normally insert a @dfn{pseudo-article} for each
8023 extracted file into the summary buffer. If you go to these
8024 ``articles'', you will be prompted for a command to run (usually Gnus
8025 will make a suggestion), and then the command will be run.
8027 @vindex gnus-view-pseudo-asynchronously
8028 If @code{gnus-view-pseudo-asynchronously} is @code{nil}, Emacs will wait
8029 until the viewing is done before proceeding.
8031 @vindex gnus-view-pseudos
8032 If @code{gnus-view-pseudos} is @code{automatic}, Gnus will not insert
8033 the pseudo-articles into the summary buffer, but view them
8034 immediately. If this variable is @code{not-confirm}, the user won't even
8035 be asked for a confirmation before viewing is done.
8037 @vindex gnus-view-pseudos-separately
8038 If @code{gnus-view-pseudos-separately} is non-@code{nil}, one
8039 pseudo-article will be created for each file to be viewed. If
8040 @code{nil}, all files that use the same viewing command will be given as
8041 a list of parameters to that command.
8043 @vindex gnus-insert-pseudo-articles
8044 If @code{gnus-insert-pseudo-articles} is non-@code{nil}, insert
8045 pseudo-articles when decoding. It is @code{t} by default.
8047 So; there you are, reading your @emph{pseudo-articles} in your
8048 @emph{virtual newsgroup} from the @emph{virtual server}; and you think:
8049 Why isn't anything real anymore? How did we get here?
8052 @node Article Treatment
8053 @section Article Treatment
8055 Reading through this huge manual, you may have quite forgotten that the
8056 object of newsreaders is to actually, like, read what people have
8057 written. Reading articles. Unfortunately, people are quite bad at
8058 writing, so there are tons of functions and variables to make reading
8059 these articles easier.
8062 * Article Highlighting:: You want to make the article look like fruit salad.
8063 * Article Fontisizing:: Making emphasized text look nice.
8064 * Article Hiding:: You also want to make certain info go away.
8065 * Article Washing:: Lots of way-neat functions to make life better.
8066 * Article Header:: Doing various header transformations.
8067 * Article Buttons:: Click on URLs, Message-IDs, addresses and the like.
8068 * Article Button Levels:: Controlling appearance of buttons.
8069 * Article Date:: Grumble, UT!
8070 * Article Display:: Display various stuff---X-Face, Picons, Smileys
8071 * Article Signature:: What is a signature?
8072 * Article Miscellanea:: Various other stuff.
8076 @node Article Highlighting
8077 @subsection Article Highlighting
8078 @cindex highlighting
8080 Not only do you want your article buffer to look like fruit salad, but
8081 you want it to look like technicolor fruit salad.
8086 @kindex W H a (Summary)
8087 @findex gnus-article-highlight
8088 @findex gnus-article-maybe-highlight
8089 Do much highlighting of the current article
8090 (@code{gnus-article-highlight}). This function highlights header, cited
8091 text, the signature, and adds buttons to the body and the head.
8094 @kindex W H h (Summary)
8095 @findex gnus-article-highlight-headers
8096 @vindex gnus-header-face-alist
8097 Highlight the headers (@code{gnus-article-highlight-headers}). The
8098 highlighting will be done according to the @code{gnus-header-face-alist}
8099 variable, which is a list where each element has the form
8100 @code{(@var{regexp} @var{name} @var{content})}.
8101 @var{regexp} is a regular expression for matching the
8102 header, @var{name} is the face used for highlighting the header name
8103 (@pxref{Faces and Fonts}) and @var{content} is the face for highlighting
8104 the header value. The first match made will be used. Note that
8105 @var{regexp} shouldn't have @samp{^} prepended---Gnus will add one.
8108 @kindex W H c (Summary)
8109 @findex gnus-article-highlight-citation
8110 Highlight cited text (@code{gnus-article-highlight-citation}).
8112 Some variables to customize the citation highlights:
8115 @vindex gnus-cite-parse-max-size
8117 @item gnus-cite-parse-max-size
8118 If the article size if bigger than this variable (which is 25000 by
8119 default), no citation highlighting will be performed.
8121 @item gnus-cite-max-prefix
8122 @vindex gnus-cite-max-prefix
8123 Maximum possible length for a citation prefix (default 20).
8125 @item gnus-cite-face-list
8126 @vindex gnus-cite-face-list
8127 List of faces used for highlighting citations (@pxref{Faces and Fonts}).
8128 When there are citations from multiple articles in the same message,
8129 Gnus will try to give each citation from each article its own face.
8130 This should make it easier to see who wrote what.
8132 @item gnus-supercite-regexp
8133 @vindex gnus-supercite-regexp
8134 Regexp matching normal Supercite attribution lines.
8136 @item gnus-supercite-secondary-regexp
8137 @vindex gnus-supercite-secondary-regexp
8138 Regexp matching mangled Supercite attribution lines.
8140 @item gnus-cite-minimum-match-count
8141 @vindex gnus-cite-minimum-match-count
8142 Minimum number of identical prefixes we have to see before we believe
8143 that it's a citation.
8145 @item gnus-cite-attribution-prefix
8146 @vindex gnus-cite-attribution-prefix
8147 Regexp matching the beginning of an attribution line.
8149 @item gnus-cite-attribution-suffix
8150 @vindex gnus-cite-attribution-suffix
8151 Regexp matching the end of an attribution line.
8153 @item gnus-cite-attribution-face
8154 @vindex gnus-cite-attribution-face
8155 Face used for attribution lines. It is merged with the face for the
8156 cited text belonging to the attribution.
8158 @item gnus-cite-ignore-quoted-from
8159 @vindex gnus-cite-ignore-quoted-from
8160 If non-@code{nil}, no citation highlighting will be performed on lines
8161 beginning with @samp{>From }. Those lines may have been quoted by MTAs
8162 in order not to mix up with the envelope From line. The default value
8169 @kindex W H s (Summary)
8170 @vindex gnus-signature-separator
8171 @vindex gnus-signature-face
8172 @findex gnus-article-highlight-signature
8173 Highlight the signature (@code{gnus-article-highlight-signature}).
8174 Everything after @code{gnus-signature-separator} (@pxref{Article
8175 Signature}) in an article will be considered a signature and will be
8176 highlighted with @code{gnus-signature-face}, which is @code{italic} by
8181 @xref{Customizing Articles}, for how to highlight articles automatically.
8184 @node Article Fontisizing
8185 @subsection Article Fontisizing
8187 @cindex article emphasis
8189 @findex gnus-article-emphasize
8190 @kindex W e (Summary)
8191 People commonly add emphasis to words in news articles by writing things
8192 like @samp{_this_} or @samp{*this*} or @samp{/this/}. Gnus can make
8193 this look nicer by running the article through the @kbd{W e}
8194 (@code{gnus-article-emphasize}) command.
8196 @vindex gnus-emphasis-alist
8197 How the emphasis is computed is controlled by the
8198 @code{gnus-emphasis-alist} variable. This is an alist where the first
8199 element is a regular expression to be matched. The second is a number
8200 that says what regular expression grouping is used to find the entire
8201 emphasized word. The third is a number that says what regexp grouping
8202 should be displayed and highlighted. (The text between these two
8203 groupings will be hidden.) The fourth is the face used for
8207 (setq gnus-emphasis-alist
8208 '(("_\\(\\w+\\)_" 0 1 gnus-emphasis-underline)
8209 ("\\*\\(\\w+\\)\\*" 0 1 gnus-emphasis-bold)))
8218 @vindex gnus-emphasis-underline
8219 @vindex gnus-emphasis-bold
8220 @vindex gnus-emphasis-italic
8221 @vindex gnus-emphasis-underline-bold
8222 @vindex gnus-emphasis-underline-italic
8223 @vindex gnus-emphasis-bold-italic
8224 @vindex gnus-emphasis-underline-bold-italic
8225 By default, there are seven rules, and they use the following faces:
8226 @code{gnus-emphasis-bold}, @code{gnus-emphasis-italic},
8227 @code{gnus-emphasis-underline}, @code{gnus-emphasis-bold-italic},
8228 @code{gnus-emphasis-underline-italic},
8229 @code{gnus-emphasis-underline-bold}, and
8230 @code{gnus-emphasis-underline-bold-italic}.
8232 If you want to change these faces, you can either use @kbd{M-x
8233 customize}, or you can use @code{copy-face}. For instance, if you want
8234 to make @code{gnus-emphasis-italic} use a red face instead, you could
8238 (copy-face 'red 'gnus-emphasis-italic)
8241 @vindex gnus-group-highlight-words-alist
8243 If you want to highlight arbitrary words, you can use the
8244 @code{gnus-group-highlight-words-alist} variable, which uses the same
8245 syntax as @code{gnus-emphasis-alist}. The @code{highlight-words} group
8246 parameter (@pxref{Group Parameters}) can also be used.
8248 @xref{Customizing Articles}, for how to fontize articles automatically.
8251 @node Article Hiding
8252 @subsection Article Hiding
8253 @cindex article hiding
8255 Or rather, hiding certain things in each article. There usually is much
8256 too much cruft in most articles.
8261 @kindex W W a (Summary)
8262 @findex gnus-article-hide
8263 Do quite a lot of hiding on the article buffer
8264 (@kbd{gnus-article-hide}). In particular, this function will hide
8265 headers, @acronym{PGP}, cited text and the signature.
8268 @kindex W W h (Summary)
8269 @findex gnus-article-hide-headers
8270 Hide headers (@code{gnus-article-hide-headers}). @xref{Hiding
8274 @kindex W W b (Summary)
8275 @findex gnus-article-hide-boring-headers
8276 Hide headers that aren't particularly interesting
8277 (@code{gnus-article-hide-boring-headers}). @xref{Hiding Headers}.
8280 @kindex W W s (Summary)
8281 @findex gnus-article-hide-signature
8282 Hide signature (@code{gnus-article-hide-signature}). @xref{Article
8286 @kindex W W l (Summary)
8287 @findex gnus-article-hide-list-identifiers
8288 @vindex gnus-list-identifiers
8289 Strip list identifiers specified in @code{gnus-list-identifiers}. These
8290 are strings some mailing list servers add to the beginning of all
8291 @code{Subject} headers---for example, @samp{[zebra 4711]}. Any leading
8292 @samp{Re: } is skipped before stripping. @code{gnus-list-identifiers}
8293 may not contain @code{\\(..\\)}.
8297 @item gnus-list-identifiers
8298 @vindex gnus-list-identifiers
8299 A regular expression that matches list identifiers to be removed from
8300 subject. This can also be a list of regular expressions.
8305 @kindex W W P (Summary)
8306 @findex gnus-article-hide-pem
8307 Hide @acronym{PEM} (privacy enhanced messages) cruft
8308 (@code{gnus-article-hide-pem}).
8311 @kindex W W B (Summary)
8312 @findex gnus-article-strip-banner
8313 @vindex gnus-article-banner-alist
8314 @vindex gnus-article-address-banner-alist
8317 @cindex stripping advertisements
8318 @cindex advertisements
8319 Strip the banner specified by the @code{banner} group parameter
8320 (@code{gnus-article-strip-banner}). This is mainly used to hide those
8321 annoying banners and/or signatures that some mailing lists and moderated
8322 groups adds to all the messages. The way to use this function is to add
8323 the @code{banner} group parameter (@pxref{Group Parameters}) to the
8324 group you want banners stripped from. The parameter either be a string,
8325 which will be interpreted as a regular expression matching text to be
8326 removed, or the symbol @code{signature}, meaning that the (last)
8327 signature should be removed, or other symbol, meaning that the
8328 corresponding regular expression in @code{gnus-article-banner-alist} is
8331 Regardless of a group, you can hide things like advertisements only when
8332 the sender of an article has a certain mail address specified in
8333 @code{gnus-article-address-banner-alist}.
8337 @item gnus-article-address-banner-alist
8338 @vindex gnus-article-address-banner-alist
8339 Alist of mail addresses and banners. Each element has the form
8340 @code{(@var{address} . @var{banner})}, where @var{address} is a regexp
8341 matching a mail address in the From header, @var{banner} is one of a
8342 symbol @code{signature}, an item in @code{gnus-article-banner-alist},
8343 a regexp and @code{nil}. If @var{address} matches author's mail
8344 address, it will remove things like advertisements. For example, if a
8345 sender has the mail address @samp{hail@@yoo-hoo.co.jp} and there is a
8346 banner something like @samp{Do You Yoo-hoo!?} in all articles he
8347 sends, you can use the following element to remove them:
8350 ("@@yoo-hoo\\.co\\.jp\\'" .
8351 "\n_+\nDo You Yoo-hoo!\\?\n.*\n.*\n")
8357 @kindex W W c (Summary)
8358 @findex gnus-article-hide-citation
8359 Hide citation (@code{gnus-article-hide-citation}). Some variables for
8360 customizing the hiding:
8364 @item gnus-cited-opened-text-button-line-format
8365 @itemx gnus-cited-closed-text-button-line-format
8366 @vindex gnus-cited-closed-text-button-line-format
8367 @vindex gnus-cited-opened-text-button-line-format
8368 Gnus adds buttons to show where the cited text has been hidden, and to
8369 allow toggle hiding the text. The format of the variable is specified
8370 by these format-like variable (@pxref{Formatting Variables}). These
8375 Starting point of the hidden text.
8377 Ending point of the hidden text.
8379 Number of characters in the hidden region.
8381 Number of lines of hidden text.
8384 @item gnus-cited-lines-visible
8385 @vindex gnus-cited-lines-visible
8386 The number of lines at the beginning of the cited text to leave
8387 shown. This can also be a cons cell with the number of lines at the top
8388 and bottom of the text, respectively, to remain visible.
8393 @kindex W W C-c (Summary)
8394 @findex gnus-article-hide-citation-maybe
8396 Hide citation (@code{gnus-article-hide-citation-maybe}) depending on the
8397 following two variables:
8400 @item gnus-cite-hide-percentage
8401 @vindex gnus-cite-hide-percentage
8402 If the cited text is of a bigger percentage than this variable (default
8403 50), hide the cited text.
8405 @item gnus-cite-hide-absolute
8406 @vindex gnus-cite-hide-absolute
8407 The cited text must have at least this length (default 10) before it
8412 @kindex W W C (Summary)
8413 @findex gnus-article-hide-citation-in-followups
8414 Hide cited text in articles that aren't roots
8415 (@code{gnus-article-hide-citation-in-followups}). This isn't very
8416 useful as an interactive command, but might be a handy function to stick
8417 have happen automatically (@pxref{Customizing Articles}).
8421 All these ``hiding'' commands are toggles, but if you give a negative
8422 prefix to these commands, they will show what they have previously
8423 hidden. If you give a positive prefix, they will always hide.
8425 Also @pxref{Article Highlighting} for further variables for
8426 citation customization.
8428 @xref{Customizing Articles}, for how to hide article elements
8432 @node Article Washing
8433 @subsection Article Washing
8435 @cindex article washing
8437 We call this ``article washing'' for a really good reason. Namely, the
8438 @kbd{A} key was taken, so we had to use the @kbd{W} key instead.
8440 @dfn{Washing} is defined by us as ``changing something from something to
8441 something else'', but normally results in something looking better.
8444 @xref{Customizing Articles}, if you want to change how Gnus displays
8445 articles by default.
8450 This is not really washing, it's sort of the opposite of washing. If
8451 you type this, you see the article exactly as it exists on disk or on
8455 Force redisplaying of the current article
8456 (@code{gnus-summary-show-article}). This is also not really washing.
8457 If you type this, you see the article without any previously applied
8458 interactive Washing functions but with all default treatments
8459 (@pxref{Customizing Articles}).
8462 @kindex W l (Summary)
8463 @findex gnus-summary-stop-page-breaking
8464 Remove page breaks from the current article
8465 (@code{gnus-summary-stop-page-breaking}). @xref{Misc Article}, for page
8469 @kindex W r (Summary)
8470 @findex gnus-summary-caesar-message
8471 @c @icon{gnus-summary-caesar-message}
8472 Do a Caesar rotate (rot13) on the article buffer
8473 (@code{gnus-summary-caesar-message}).
8474 Unreadable articles that tell you to read them with Caesar rotate or rot13.
8475 (Typically offensive jokes and such.)
8477 It's commonly called ``rot13'' because each letter is rotated 13
8478 positions in the alphabet, e. g. @samp{B} (letter #2) -> @samp{O} (letter
8479 #15). It is sometimes referred to as ``Caesar rotate'' because Caesar
8480 is rumored to have employed this form of, uh, somewhat weak encryption.
8483 @kindex W m (Summary)
8484 @findex gnus-summary-morse-message
8485 Morse decode the article buffer (@code{gnus-summary-morse-message}).
8488 @kindex W i (Summary)
8489 @findex gnus-summary-idna-message
8490 Decode IDNA encoded domain names in the current articles. IDNA
8491 encoded domain names looks like @samp{xn--bar}. If a string remain
8492 unencoded after running invoking this, it is likely an invalid IDNA
8493 string (@samp{xn--bar} is invalid). You must have GNU Libidn
8494 (@url{http://www.gnu.org/software/libidn/}) installed for this command
8499 @kindex W t (Summary)
8501 @findex gnus-summary-toggle-header
8502 Toggle whether to display all headers in the article buffer
8503 (@code{gnus-summary-toggle-header}).
8506 @kindex W v (Summary)
8507 @findex gnus-summary-verbose-headers
8508 Toggle whether to display all headers in the article buffer permanently
8509 (@code{gnus-summary-verbose-headers}).
8512 @kindex W o (Summary)
8513 @findex gnus-article-treat-overstrike
8514 Treat overstrike (@code{gnus-article-treat-overstrike}).
8517 @kindex W d (Summary)
8518 @findex gnus-article-treat-dumbquotes
8519 @vindex gnus-article-dumbquotes-map
8521 @cindex M****s*** sm*rtq**t*s
8523 Treat M****s*** sm*rtq**t*s according to
8524 @code{gnus-article-dumbquotes-map}
8525 (@code{gnus-article-treat-dumbquotes}). Note that this function guesses
8526 whether a character is a sm*rtq**t* or not, so it should only be used
8529 Sm*rtq**t*s are M****s***'s unilateral extension to the character map in
8530 an attempt to provide more quoting characters. If you see something
8531 like @code{\222} or @code{\264} where you're expecting some kind of
8532 apostrophe or quotation mark, then try this wash.
8535 @kindex W Y f (Summary)
8536 @findex gnus-article-outlook-deuglify-article
8537 @cindex Outlook Express
8538 Full deuglify of broken Outlook (Express) articles: Treat dumbquotes,
8539 unwrap lines, repair attribution and rearrange citation.
8540 (@code{gnus-article-outlook-deuglify-article}).
8543 @kindex W Y u (Summary)
8544 @findex gnus-article-outlook-unwrap-lines
8545 @vindex gnus-outlook-deuglify-unwrap-min
8546 @vindex gnus-outlook-deuglify-unwrap-max
8547 Unwrap lines that appear to be wrapped citation lines. You can control
8548 what lines will be unwrapped by frobbing
8549 @code{gnus-outlook-deuglify-unwrap-min} and
8550 @code{gnus-outlook-deuglify-unwrap-max}, indicating the minimum and
8551 maximum length of an unwrapped citation line.
8552 (@code{gnus-article-outlook-unwrap-lines}).
8555 @kindex W Y a (Summary)
8556 @findex gnus-article-outlook-repair-attribution
8557 Repair a broken attribution line.@*
8558 (@code{gnus-article-outlook-repair-attribution}).
8561 @kindex W Y c (Summary)
8562 @findex gnus-article-outlook-rearrange-citation
8563 Repair broken citations by rearranging the text.
8564 (@code{gnus-article-outlook-rearrange-citation}).
8567 @kindex W w (Summary)
8568 @findex gnus-article-fill-cited-article
8569 Do word wrap (@code{gnus-article-fill-cited-article}).
8571 You can give the command a numerical prefix to specify the width to use
8575 @kindex W Q (Summary)
8576 @findex gnus-article-fill-long-lines
8577 Fill long lines (@code{gnus-article-fill-long-lines}).
8580 @kindex W C (Summary)
8581 @findex gnus-article-capitalize-sentences
8582 Capitalize the first word in each sentence
8583 (@code{gnus-article-capitalize-sentences}).
8586 @kindex W c (Summary)
8587 @findex gnus-article-remove-cr
8588 Translate CRLF pairs (i. e., @samp{^M}s on the end of the lines) into LF
8589 (this takes care of DOS line endings), and then translate any remaining
8590 CRs into LF (this takes care of Mac line endings)
8591 (@code{gnus-article-remove-cr}).
8594 @kindex W q (Summary)
8595 @findex gnus-article-de-quoted-unreadable
8596 Treat quoted-printable (@code{gnus-article-de-quoted-unreadable}).
8597 Quoted-Printable is one common @acronym{MIME} encoding employed when
8598 sending non-@acronym{ASCII} (i.e., 8-bit) articles. It typically
8599 makes strings like @samp{d@'ej@`a vu} look like @samp{d=E9j=E0 vu},
8600 which doesn't look very readable to me. Note that this is usually
8601 done automatically by Gnus if the message in question has a
8602 @code{Content-Transfer-Encoding} header that says that this encoding
8603 has been done. If a prefix is given, a charset will be asked for.
8606 @kindex W 6 (Summary)
8607 @findex gnus-article-de-base64-unreadable
8608 Treat base64 (@code{gnus-article-de-base64-unreadable}). Base64 is
8609 one common @acronym{MIME} encoding employed when sending
8610 non-@acronym{ASCII} (i.e., 8-bit) articles. Note that this is
8611 usually done automatically by Gnus if the message in question has a
8612 @code{Content-Transfer-Encoding} header that says that this encoding
8613 has been done. If a prefix is given, a charset will be asked for.
8616 @kindex W Z (Summary)
8617 @findex gnus-article-decode-HZ
8618 Treat HZ or HZP (@code{gnus-article-decode-HZ}). HZ (or HZP) is one
8619 common encoding employed when sending Chinese articles. It typically
8620 makes strings look like @samp{~@{<:Ky2;S@{#,NpJ)l6HK!#~@}}.
8623 @kindex W A (Summary)
8624 @findex gnus-article-treat-ansi-sequences
8625 @cindex @acronym{ANSI} control sequences
8626 Translate @acronym{ANSI} SGR control sequences into overlays or
8627 extents (@code{gnus-article-treat-ansi-sequences}). @acronym{ANSI}
8628 sequences are used in some Chinese hierarchies for highlighting.
8631 @kindex W u (Summary)
8632 @findex gnus-article-unsplit-urls
8633 Remove newlines from within URLs. Some mailers insert newlines into
8634 outgoing email messages to keep lines short. This reformatting can
8635 split long URLs onto multiple lines. Repair those URLs by removing
8636 the newlines (@code{gnus-article-unsplit-urls}).
8639 @kindex W h (Summary)
8640 @findex gnus-article-wash-html
8641 Treat @acronym{HTML} (@code{gnus-article-wash-html}). Note that this is
8642 usually done automatically by Gnus if the message in question has a
8643 @code{Content-Type} header that says that the message is @acronym{HTML}.
8645 If a prefix is given, a charset will be asked for.
8647 @vindex gnus-article-wash-function
8648 The default is to use the function specified by
8649 @code{mm-text-html-renderer} (@pxref{Display Customization, ,Display
8650 Customization, emacs-mime, The Emacs MIME Manual}) to convert the
8651 @acronym{HTML}, but this is controlled by the
8652 @code{gnus-article-wash-function} variable. Pre-defined functions you
8660 Use @uref{http://emacs-w3m.namazu.org/, emacs-w3m}.
8663 Use @uref{http://links.sf.net/, Links}.
8666 Use @uref{http://lynx.isc.org/, Lynx}.
8669 Use html2text---a simple @acronym{HTML} converter included with Gnus.
8674 @kindex W b (Summary)
8675 @findex gnus-article-add-buttons
8676 Add clickable buttons to the article (@code{gnus-article-add-buttons}).
8677 @xref{Article Buttons}.
8680 @kindex W B (Summary)
8681 @findex gnus-article-add-buttons-to-head
8682 Add clickable buttons to the article headers
8683 (@code{gnus-article-add-buttons-to-head}).
8686 @kindex W p (Summary)
8687 @findex gnus-article-verify-x-pgp-sig
8688 Verify a signed control message
8689 (@code{gnus-article-verify-x-pgp-sig}). Control messages such as
8690 @code{newgroup} and @code{checkgroups} are usually signed by the
8691 hierarchy maintainer. You need to add the @acronym{PGP} public key of
8692 the maintainer to your keyring to verify the
8693 message.@footnote{@acronym{PGP} keys for many hierarchies are
8694 available at @uref{ftp://ftp.isc.org/pub/pgpcontrol/README.html}}
8697 @kindex W s (Summary)
8698 @findex gnus-summary-force-verify-and-decrypt
8699 Verify a signed (@acronym{PGP}, @acronym{PGP/MIME} or
8700 @acronym{S/MIME}) message
8701 (@code{gnus-summary-force-verify-and-decrypt}). @xref{Security}.
8704 @kindex W a (Summary)
8705 @findex gnus-article-strip-headers-in-body
8706 Strip headers like the @code{X-No-Archive} header from the beginning of
8707 article bodies (@code{gnus-article-strip-headers-in-body}).
8710 @kindex W E l (Summary)
8711 @findex gnus-article-strip-leading-blank-lines
8712 Remove all blank lines from the beginning of the article
8713 (@code{gnus-article-strip-leading-blank-lines}).
8716 @kindex W E m (Summary)
8717 @findex gnus-article-strip-multiple-blank-lines
8718 Replace all blank lines with empty lines and then all multiple empty
8719 lines with a single empty line.
8720 (@code{gnus-article-strip-multiple-blank-lines}).
8723 @kindex W E t (Summary)
8724 @findex gnus-article-remove-trailing-blank-lines
8725 Remove all blank lines at the end of the article
8726 (@code{gnus-article-remove-trailing-blank-lines}).
8729 @kindex W E a (Summary)
8730 @findex gnus-article-strip-blank-lines
8731 Do all the three commands above
8732 (@code{gnus-article-strip-blank-lines}).
8735 @kindex W E A (Summary)
8736 @findex gnus-article-strip-all-blank-lines
8737 Remove all blank lines
8738 (@code{gnus-article-strip-all-blank-lines}).
8741 @kindex W E s (Summary)
8742 @findex gnus-article-strip-leading-space
8743 Remove all white space from the beginning of all lines of the article
8744 body (@code{gnus-article-strip-leading-space}).
8747 @kindex W E e (Summary)
8748 @findex gnus-article-strip-trailing-space
8749 Remove all white space from the end of all lines of the article
8750 body (@code{gnus-article-strip-trailing-space}).
8754 @xref{Customizing Articles}, for how to wash articles automatically.
8757 @node Article Header
8758 @subsection Article Header
8760 These commands perform various transformations of article header.
8765 @kindex W G u (Summary)
8766 @findex gnus-article-treat-unfold-headers
8767 Unfold folded header lines (@code{gnus-article-treat-unfold-headers}).
8770 @kindex W G n (Summary)
8771 @findex gnus-article-treat-fold-newsgroups
8772 Fold the @code{Newsgroups} and @code{Followup-To} headers
8773 (@code{gnus-article-treat-fold-newsgroups}).
8776 @kindex W G f (Summary)
8777 @findex gnus-article-treat-fold-headers
8778 Fold all the message headers
8779 (@code{gnus-article-treat-fold-headers}).
8782 @kindex W E w (Summary)
8783 @findex gnus-article-remove-leading-whitespace
8784 Remove excessive whitespace from all headers
8785 (@code{gnus-article-remove-leading-whitespace}).
8790 @node Article Buttons
8791 @subsection Article Buttons
8794 People often include references to other stuff in articles, and it would
8795 be nice if Gnus could just fetch whatever it is that people talk about
8796 with the minimum of fuzz when you hit @kbd{RET} or use the middle mouse
8797 button on these references.
8799 @vindex gnus-button-man-handler
8800 Gnus adds @dfn{buttons} to certain standard references by default:
8801 Well-formed URLs, mail addresses, Message-IDs, Info links, man pages and
8802 Emacs or Gnus related references. This is controlled by two variables,
8803 one that handles article bodies and one that handles article heads:
8807 @item gnus-button-alist
8808 @vindex gnus-button-alist
8809 This is an alist where each entry has this form:
8812 (@var{regexp} @var{button-par} @var{use-p} @var{function} @var{data-par})
8818 All text that match this regular expression (case insensitive) will be
8819 considered an external reference. Here's a typical regexp that matches
8820 embedded URLs: @samp{<URL:\\([^\n\r>]*\\)>}. This can also be a
8821 variable containing a regexp, useful variables to use include
8822 @code{gnus-button-url-regexp} and @code{gnus-button-mid-or-mail-regexp}.
8825 Gnus has to know which parts of the matches is to be highlighted. This
8826 is a number that says what sub-expression of the regexp is to be
8827 highlighted. If you want it all highlighted, you use 0 here.
8830 This form will be @code{eval}ed, and if the result is non-@code{nil},
8831 this is considered a match. This is useful if you want extra sifting to
8832 avoid false matches. Often variables named
8833 @code{gnus-button-@var{*}-level} are used here, @xref{Article Button
8834 Levels}, but any other form may be used too.
8836 @c @code{use-p} is @code{eval}ed only if @code{regexp} matches.
8839 This function will be called when you click on this button.
8842 As with @var{button-par}, this is a sub-expression number, but this one
8843 says which part of the match is to be sent as data to @var{function}.
8847 So the full entry for buttonizing URLs is then
8850 ("<URL:\\([^\n\r>]*\\)>" 0 t gnus-button-url 1)
8853 @item gnus-header-button-alist
8854 @vindex gnus-header-button-alist
8855 This is just like the other alist, except that it is applied to the
8856 article head only, and that each entry has an additional element that is
8857 used to say what headers to apply the buttonize coding to:
8860 (@var{header} @var{regexp} @var{button-par} @var{use-p} @var{function} @var{data-par})
8863 @var{header} is a regular expression.
8866 @subsubsection Related variables and functions
8869 @item gnus-button-@var{*}-level
8870 @xref{Article Button Levels}.
8872 @c Stuff related to gnus-button-browse-level
8874 @item gnus-button-url-regexp
8875 @vindex gnus-button-url-regexp
8876 A regular expression that matches embedded URLs. It is used in the
8877 default values of the variables above.
8879 @c Stuff related to gnus-button-man-level
8881 @item gnus-button-man-handler
8882 @vindex gnus-button-man-handler
8883 The function to use for displaying man pages. It must take at least one
8884 argument with a string naming the man page.
8886 @c Stuff related to gnus-button-message-level
8888 @item gnus-button-mid-or-mail-regexp
8889 @vindex gnus-button-mid-or-mail-regexp
8890 Regular expression that matches a message ID or a mail address.
8892 @item gnus-button-prefer-mid-or-mail
8893 @vindex gnus-button-prefer-mid-or-mail
8894 This variable determines what to do when the button on a string as
8895 @samp{foo123@@bar.invalid} is pushed. Strings like this can be either a
8896 message ID or a mail address. If it is one of the symbols @code{mid} or
8897 @code{mail}, Gnus will always assume that the string is a message ID or
8898 a mail address, respectively. If this variable is set to the symbol
8899 @code{ask}, always query the user what do do. If it is a function, this
8900 function will be called with the string as its only argument. The
8901 function must return @code{mid}, @code{mail}, @code{invalid} or
8902 @code{ask}. The default value is the function
8903 @code{gnus-button-mid-or-mail-heuristic}.
8905 @item gnus-button-mid-or-mail-heuristic
8906 @findex gnus-button-mid-or-mail-heuristic
8907 Function that guesses whether its argument is a message ID or a mail
8908 address. Returns @code{mid} if it's a message IDs, @code{mail} if
8909 it's a mail address, @code{ask} if unsure and @code{invalid} if the
8912 @item gnus-button-mid-or-mail-heuristic-alist
8913 @vindex gnus-button-mid-or-mail-heuristic-alist
8914 An alist of @code{(RATE . REGEXP)} pairs used by the function
8915 @code{gnus-button-mid-or-mail-heuristic}.
8917 @c Stuff related to gnus-button-tex-level
8919 @item gnus-button-ctan-handler
8920 @findex gnus-button-ctan-handler
8921 The function to use for displaying CTAN links. It must take one
8922 argument, the string naming the URL.
8925 @vindex gnus-ctan-url
8926 Top directory of a CTAN (Comprehensive TeX Archive Network) archive used
8927 by @code{gnus-button-ctan-handler}.
8931 @item gnus-article-button-face
8932 @vindex gnus-article-button-face
8933 Face used on buttons.
8935 @item gnus-article-mouse-face
8936 @vindex gnus-article-mouse-face
8937 Face used when the mouse cursor is over a button.
8941 @xref{Customizing Articles}, for how to buttonize articles automatically.
8944 @node Article Button Levels
8945 @subsection Article button levels
8946 @cindex button levels
8947 The higher the value of the variables @code{gnus-button-@var{*}-level},
8948 the more buttons will appear. If the level is zero, no corresponding
8949 buttons are displayed. With the default value (which is 5) you should
8950 already see quite a lot of buttons. With higher levels, you will see
8951 more buttons, but you may also get more false positives. To avoid them,
8952 you can set the variables @code{gnus-button-@var{*}-level} local to
8953 specific groups (@pxref{Group Parameters}). Here's an example for the
8954 variable @code{gnus-parameters}:
8957 ;; @r{increase @code{gnus-button-*-level} in some groups:}
8958 (setq gnus-parameters
8959 '(("\\<\\(emacs\\|gnus\\)\\>" (gnus-button-emacs-level 10))
8960 ("\\<unix\\>" (gnus-button-man-level 10))
8961 ("\\<tex\\>" (gnus-button-tex-level 10))))
8966 @item gnus-button-browse-level
8967 @vindex gnus-button-browse-level
8968 Controls the display of references to message IDs, mail addresses and
8969 news URLs. Related variables and functions include
8970 @code{gnus-button-url-regexp}, @code{browse-url}, and
8971 @code{browse-url-browser-function}.
8973 @item gnus-button-emacs-level
8974 @vindex gnus-button-emacs-level
8975 Controls the display of Emacs or Gnus references. Related functions are
8976 @code{gnus-button-handle-custom},
8977 @code{gnus-button-handle-describe-function},
8978 @code{gnus-button-handle-describe-variable},
8979 @code{gnus-button-handle-symbol},
8980 @code{gnus-button-handle-describe-key},
8981 @code{gnus-button-handle-apropos},
8982 @code{gnus-button-handle-apropos-command},
8983 @code{gnus-button-handle-apropos-variable},
8984 @code{gnus-button-handle-apropos-documentation}, and
8985 @code{gnus-button-handle-library}.
8987 @item gnus-button-man-level
8988 @vindex gnus-button-man-level
8989 Controls the display of references to (Unix) man pages.
8990 See @code{gnus-button-man-handler}.
8992 @item gnus-button-message-level
8993 @vindex gnus-button-message-level
8994 Controls the display of message IDs, mail addresses and news URLs.
8995 Related variables and functions include
8996 @code{gnus-button-mid-or-mail-regexp},
8997 @code{gnus-button-prefer-mid-or-mail},
8998 @code{gnus-button-mid-or-mail-heuristic}, and
8999 @code{gnus-button-mid-or-mail-heuristic-alist}.
9001 @item gnus-button-tex-level
9002 @vindex gnus-button-tex-level
9003 Controls the display of references to @TeX{} or LaTeX stuff, e.g. for CTAN
9004 URLs. See the variables @code{gnus-ctan-url},
9005 @code{gnus-button-ctan-handler},
9006 @code{gnus-button-ctan-directory-regexp}, and
9007 @code{gnus-button-handle-ctan-bogus-regexp}.
9013 @subsection Article Date
9015 The date is most likely generated in some obscure timezone you've never
9016 heard of, so it's quite nice to be able to find out what the time was
9017 when the article was sent.
9022 @kindex W T u (Summary)
9023 @findex gnus-article-date-ut
9024 Display the date in UT (aka. GMT, aka ZULU)
9025 (@code{gnus-article-date-ut}).
9028 @kindex W T i (Summary)
9029 @findex gnus-article-date-iso8601
9031 Display the date in international format, aka. ISO 8601
9032 (@code{gnus-article-date-iso8601}).
9035 @kindex W T l (Summary)
9036 @findex gnus-article-date-local
9037 Display the date in the local timezone (@code{gnus-article-date-local}).
9040 @kindex W T p (Summary)
9041 @findex gnus-article-date-english
9042 Display the date in a format that's easily pronounceable in English
9043 (@code{gnus-article-date-english}).
9046 @kindex W T s (Summary)
9047 @vindex gnus-article-time-format
9048 @findex gnus-article-date-user
9049 @findex format-time-string
9050 Display the date using a user-defined format
9051 (@code{gnus-article-date-user}). The format is specified by the
9052 @code{gnus-article-time-format} variable, and is a string that's passed
9053 to @code{format-time-string}. See the documentation of that variable
9054 for a list of possible format specs.
9057 @kindex W T e (Summary)
9058 @findex gnus-article-date-lapsed
9059 @findex gnus-start-date-timer
9060 @findex gnus-stop-date-timer
9061 Say how much time has elapsed between the article was posted and now
9062 (@code{gnus-article-date-lapsed}). It looks something like:
9065 X-Sent: 6 weeks, 4 days, 1 hour, 3 minutes, 8 seconds ago
9068 @vindex gnus-article-date-lapsed-new-header
9069 The value of @code{gnus-article-date-lapsed-new-header} determines
9070 whether this header will just be added below the old Date one, or will
9073 An advantage of using Gnus to read mail is that it converts simple bugs
9074 into wonderful absurdities.
9076 If you want to have this line updated continually, you can put
9079 (gnus-start-date-timer)
9082 in your @file{~/.gnus.el} file, or you can run it off of some hook. If
9083 you want to stop the timer, you can use the @code{gnus-stop-date-timer}
9087 @kindex W T o (Summary)
9088 @findex gnus-article-date-original
9089 Display the original date (@code{gnus-article-date-original}). This can
9090 be useful if you normally use some other conversion function and are
9091 worried that it might be doing something totally wrong. Say, claiming
9092 that the article was posted in 1854. Although something like that is
9093 @emph{totally} impossible. Don't you trust me? *titter*
9097 @xref{Customizing Articles}, for how to display the date in your
9098 preferred format automatically.
9101 @node Article Display
9102 @subsection Article Display
9107 These commands add various frivolous display gimmicks to the article
9108 buffer in Emacs versions that support them.
9110 @code{X-Face} headers are small black-and-white images supplied by the
9111 message headers (@pxref{X-Face}).
9113 @code{Face} headers are small colored images supplied by the message
9114 headers (@pxref{Face}).
9116 Smileys are those little @samp{:-)} symbols that people like to litter
9117 their messages with (@pxref{Smileys}).
9119 Picons, on the other hand, reside on your own system, and Gnus will
9120 try to match the headers to what you have (@pxref{Picons}).
9122 All these functions are toggles---if the elements already exist,
9127 @kindex W D x (Summary)
9128 @findex gnus-article-display-x-face
9129 Display an @code{X-Face} in the @code{From} header.
9130 (@code{gnus-article-display-x-face}).
9133 @kindex W D d (Summary)
9134 @findex gnus-article-display-face
9135 Display a @code{Face} in the @code{From} header.
9136 (@code{gnus-article-display-face}).
9139 @kindex W D s (Summary)
9140 @findex gnus-treat-smiley
9141 Display smileys (@code{gnus-treat-smiley}).
9144 @kindex W D f (Summary)
9145 @findex gnus-treat-from-picon
9146 Piconify the @code{From} header (@code{gnus-treat-from-picon}).
9149 @kindex W D m (Summary)
9150 @findex gnus-treat-mail-picon
9151 Piconify all mail headers (i. e., @code{Cc}, @code{To})
9152 (@code{gnus-treat-mail-picon}).
9155 @kindex W D n (Summary)
9156 @findex gnus-treat-newsgroups-picon
9157 Piconify all news headers (i. e., @code{Newsgroups} and
9158 @code{Followup-To}) (@code{gnus-treat-newsgroups-picon}).
9161 @kindex W D D (Summary)
9162 @findex gnus-article-remove-images
9163 Remove all images from the article buffer
9164 (@code{gnus-article-remove-images}).
9170 @node Article Signature
9171 @subsection Article Signature
9173 @cindex article signature
9175 @vindex gnus-signature-separator
9176 Each article is divided into two parts---the head and the body. The
9177 body can be divided into a signature part and a text part. The variable
9178 that says what is to be considered a signature is
9179 @code{gnus-signature-separator}. This is normally the standard
9180 @samp{^-- $} as mandated by son-of-RFC 1036. However, many people use
9181 non-standard signature separators, so this variable can also be a list
9182 of regular expressions to be tested, one by one. (Searches are done
9183 from the end of the body towards the beginning.) One likely value is:
9186 (setq gnus-signature-separator
9187 '("^-- $" ; @r{The standard}
9188 "^-- *$" ; @r{A common mangling}
9189 "^-------*$" ; @r{Many people just use a looong}
9190 ; @r{line of dashes. Shame!}
9191 "^ *--------*$" ; @r{Double-shame!}
9192 "^________*$" ; @r{Underscores are also popular}
9193 "^========*$")) ; @r{Pervert!}
9196 The more permissive you are, the more likely it is that you'll get false
9199 @vindex gnus-signature-limit
9200 @code{gnus-signature-limit} provides a limit to what is considered a
9201 signature when displaying articles.
9205 If it is an integer, no signature may be longer (in characters) than
9208 If it is a floating point number, no signature may be longer (in lines)
9211 If it is a function, the function will be called without any parameters,
9212 and if it returns @code{nil}, there is no signature in the buffer.
9214 If it is a string, it will be used as a regexp. If it matches, the text
9215 in question is not a signature.
9218 This variable can also be a list where the elements may be of the types
9219 listed above. Here's an example:
9222 (setq gnus-signature-limit
9223 '(200.0 "^---*Forwarded article"))
9226 This means that if there are more than 200 lines after the signature
9227 separator, or the text after the signature separator is matched by
9228 the regular expression @samp{^---*Forwarded article}, then it isn't a
9229 signature after all.
9232 @node Article Miscellanea
9233 @subsection Article Miscellanea
9237 @kindex A t (Summary)
9238 @findex gnus-article-babel
9239 Translate the article from one language to another
9240 (@code{gnus-article-babel}).
9246 @section MIME Commands
9247 @cindex MIME decoding
9249 @cindex viewing attachments
9251 The following commands all understand the numerical prefix. For
9252 instance, @kbd{3 b} means ``view the third @acronym{MIME} part''.
9258 @kindex K v (Summary)
9259 View the @acronym{MIME} part.
9262 @kindex K o (Summary)
9263 Save the @acronym{MIME} part.
9266 @kindex K c (Summary)
9267 Copy the @acronym{MIME} part.
9270 @kindex K e (Summary)
9271 View the @acronym{MIME} part externally.
9274 @kindex K i (Summary)
9275 View the @acronym{MIME} part internally.
9278 @kindex K | (Summary)
9279 Pipe the @acronym{MIME} part to an external command.
9282 The rest of these @acronym{MIME} commands do not use the numerical prefix in
9287 @kindex K b (Summary)
9288 Make all the @acronym{MIME} parts have buttons in front of them. This is
9289 mostly useful if you wish to save (or perform other actions) on inlined
9293 @kindex K m (Summary)
9294 @findex gnus-summary-repair-multipart
9295 Some multipart messages are transmitted with missing or faulty headers.
9296 This command will attempt to ``repair'' these messages so that they can
9297 be viewed in a more pleasant manner
9298 (@code{gnus-summary-repair-multipart}).
9301 @kindex X m (Summary)
9302 @findex gnus-summary-save-parts
9303 Save all parts matching a @acronym{MIME} type to a directory
9304 (@code{gnus-summary-save-parts}). Understands the process/prefix
9305 convention (@pxref{Process/Prefix}).
9308 @kindex M-t (Summary)
9309 @findex gnus-summary-toggle-display-buttonized
9310 Toggle the buttonized display of the article buffer
9311 (@code{gnus-summary-toggle-display-buttonized}).
9314 @kindex W M w (Summary)
9315 @findex gnus-article-decode-mime-words
9316 Decode RFC 2047-encoded words in the article headers
9317 (@code{gnus-article-decode-mime-words}).
9320 @kindex W M c (Summary)
9321 @findex gnus-article-decode-charset
9322 Decode encoded article bodies as well as charsets
9323 (@code{gnus-article-decode-charset}).
9325 This command looks in the @code{Content-Type} header to determine the
9326 charset. If there is no such header in the article, you can give it a
9327 prefix, which will prompt for the charset to decode as. In regional
9328 groups where people post using some common encoding (but do not
9329 include @acronym{MIME} headers), you can set the @code{charset} group/topic
9330 parameter to the required charset (@pxref{Group Parameters}).
9333 @kindex W M v (Summary)
9334 @findex gnus-mime-view-all-parts
9335 View all the @acronym{MIME} parts in the current article
9336 (@code{gnus-mime-view-all-parts}).
9343 @item gnus-ignored-mime-types
9344 @vindex gnus-ignored-mime-types
9345 This is a list of regexps. @acronym{MIME} types that match a regexp from
9346 this list will be completely ignored by Gnus. The default value is
9349 To have all Vcards be ignored, you'd say something like this:
9352 (setq gnus-ignored-mime-types
9356 @item gnus-article-loose-mime
9357 @vindex gnus-article-loose-mime
9358 If non-@code{nil}, Gnus won't require the @samp{MIME-Version} header
9359 before interpreting the message as a @acronym{MIME} message. This helps
9360 when reading messages from certain broken mail user agents. The
9361 default is @code{nil}.
9363 @item gnus-article-emulate-mime
9364 @vindex gnus-article-emulate-mime
9365 There are other, non-@acronym{MIME} encoding methods used. The most common
9366 is @samp{uuencode}, but yEncode is also getting to be popular. If
9367 this variable is non-@code{nil}, Gnus will look in message bodies to
9368 see if it finds these encodings, and if so, it'll run them through the
9369 Gnus @acronym{MIME} machinery. The default is @code{t}.
9371 @item gnus-unbuttonized-mime-types
9372 @vindex gnus-unbuttonized-mime-types
9373 This is a list of regexps. @acronym{MIME} types that match a regexp from
9374 this list won't have @acronym{MIME} buttons inserted unless they aren't
9375 displayed or this variable is overridden by
9376 @code{gnus-buttonized-mime-types}. The default value is
9377 @code{(".*/.*")}. This variable is only used when
9378 @code{gnus-inhibit-mime-unbuttonizing} is @code{nil}.
9380 @item gnus-buttonized-mime-types
9381 @vindex gnus-buttonized-mime-types
9382 This is a list of regexps. @acronym{MIME} types that match a regexp from
9383 this list will have @acronym{MIME} buttons inserted unless they aren't
9384 displayed. This variable overrides
9385 @code{gnus-unbuttonized-mime-types}. The default value is @code{nil}.
9386 This variable is only used when @code{gnus-inhibit-mime-unbuttonizing}
9389 To see e.g. security buttons but no other buttons, you could set this
9390 variable to @code{("multipart/signed")} and leave
9391 @code{gnus-unbuttonized-mime-types} at the default value.
9393 @item gnus-inhibit-mime-unbuttonizing
9394 @vindex gnus-inhibit-mime-unbuttonizing
9395 If this is non-@code{nil}, then all @acronym{MIME} parts get buttons. The
9396 default value is @code{nil}.
9398 @item gnus-article-mime-part-function
9399 @vindex gnus-article-mime-part-function
9400 For each @acronym{MIME} part, this function will be called with the @acronym{MIME}
9401 handle as the parameter. The function is meant to be used to allow
9402 users to gather information from the article (e. g., add Vcard info to
9403 the bbdb database) or to do actions based on parts (e. g., automatically
9404 save all jpegs into some directory).
9406 Here's an example function the does the latter:
9409 (defun my-save-all-jpeg-parts (handle)
9410 (when (equal (car (mm-handle-type handle)) "image/jpeg")
9412 (insert (mm-get-part handle))
9413 (write-region (point-min) (point-max)
9414 (read-file-name "Save jpeg to: ")))))
9415 (setq gnus-article-mime-part-function
9416 'my-save-all-jpeg-parts)
9419 @vindex gnus-mime-multipart-functions
9420 @item gnus-mime-multipart-functions
9421 Alist of @acronym{MIME} multipart types and functions to handle them.
9423 @vindex gnus-mime-display-multipart-alternative-as-mixed
9424 @item gnus-mime-display-multipart-alternative-as-mixed
9425 Display "multipart/alternative" parts as "multipart/mixed".
9427 @vindex gnus-mime-display-multipart-related-as-mixed
9428 @item gnus-mime-display-multipart-related-as-mixed
9429 Display "multipart/related" parts as "multipart/mixed".
9431 If displaying "text/html" is discouraged, see
9432 @code{mm-discouraged-alternatives} in @ref{Display Customization,
9433 Display Customization, , emacs-mime, Emacs-Mime Manual}. Images or
9434 other material inside a "multipart/related" part might be overlooked
9435 when this variable is @code{nil}.
9437 @vindex gnus-mime-display-multipart-as-mixed
9438 @item gnus-mime-display-multipart-as-mixed
9439 Display "multipart" parts as "multipart/mixed". If @code{t}, it
9440 overrides @code{nil} values of
9441 @code{gnus-mime-display-multipart-alternative-as-mixed} and
9442 @code{gnus-mime-display-multipart-related-as-mixed}.
9444 @vindex mm-file-name-rewrite-functions
9445 @item mm-file-name-rewrite-functions
9446 List of functions used for rewriting file names of @acronym{MIME} parts.
9447 Each function takes a file name as input and returns a file name.
9449 Ready-made functions include@*
9450 @code{mm-file-name-delete-whitespace},
9451 @code{mm-file-name-trim-whitespace},
9452 @code{mm-file-name-collapse-whitespace}, and
9453 @code{mm-file-name-replace-whitespace}. The later uses the value of
9454 the variable @code{mm-file-name-replace-whitespace} to replace each
9455 whitespace character in a file name with that string; default value
9456 is @code{"_"} (a single underscore).
9457 @findex mm-file-name-delete-whitespace
9458 @findex mm-file-name-trim-whitespace
9459 @findex mm-file-name-collapse-whitespace
9460 @findex mm-file-name-replace-whitespace
9461 @vindex mm-file-name-replace-whitespace
9463 The standard functions @code{capitalize}, @code{downcase},
9464 @code{upcase}, and @code{upcase-initials} may be useful, too.
9466 Everybody knows that whitespace characters in file names are evil,
9467 except those who don't know. If you receive lots of attachments from
9468 such unenlightened users, you can make live easier by adding
9471 (setq mm-file-name-rewrite-functions
9472 '(mm-file-name-trim-whitespace
9473 mm-file-name-collapse-whitespace
9474 mm-file-name-replace-whitespace))
9478 to your @file{~/.gnus.el} file.
9487 People use different charsets, and we have @acronym{MIME} to let us know what
9488 charsets they use. Or rather, we wish we had. Many people use
9489 newsreaders and mailers that do not understand or use @acronym{MIME}, and
9490 just send out messages without saying what character sets they use. To
9491 help a bit with this, some local news hierarchies have policies that say
9492 what character set is the default. For instance, the @samp{fj}
9493 hierarchy uses @code{iso-2022-jp}.
9495 @vindex gnus-group-charset-alist
9496 This knowledge is encoded in the @code{gnus-group-charset-alist}
9497 variable, which is an alist of regexps (use the first item to match full
9498 group names) and default charsets to be used when reading these groups.
9500 @vindex gnus-newsgroup-ignored-charsets
9501 In addition, some people do use soi-disant @acronym{MIME}-aware agents that
9502 aren't. These blithely mark messages as being in @code{iso-8859-1}
9503 even if they really are in @code{koi-8}. To help here, the
9504 @code{gnus-newsgroup-ignored-charsets} variable can be used. The
9505 charsets that are listed here will be ignored. The variable can be
9506 set on a group-by-group basis using the group parameters (@pxref{Group
9507 Parameters}). The default value is @code{(unknown-8bit x-unknown)},
9508 which includes values some agents insist on having in there.
9510 @vindex gnus-group-posting-charset-alist
9511 When posting, @code{gnus-group-posting-charset-alist} is used to
9512 determine which charsets should not be encoded using the @acronym{MIME}
9513 encodings. For instance, some hierarchies discourage using
9514 quoted-printable header encoding.
9516 This variable is an alist of regexps and permitted unencoded charsets
9517 for posting. Each element of the alist has the form @code{(}@var{test
9518 header body-list}@code{)}, where:
9522 is either a regular expression matching the newsgroup header or a
9525 is the charset which may be left unencoded in the header (@code{nil}
9526 means encode all charsets),
9528 is a list of charsets which may be encoded using 8bit content-transfer
9529 encoding in the body, or one of the special values @code{nil} (always
9530 encode using quoted-printable) or @code{t} (always use 8bit).
9537 @cindex coding system aliases
9538 @cindex preferred charset
9540 @xref{Encoding Customization, , Encoding Customization, emacs-mime,
9541 The Emacs MIME Manual}, for additional variables that control which
9542 MIME charsets are used when sending messages.
9544 Other charset tricks that may be useful, although not Gnus-specific:
9546 If there are several @acronym{MIME} charsets that encode the same Emacs
9547 charset, you can choose what charset to use by saying the following:
9550 (put-charset-property 'cyrillic-iso8859-5
9551 'preferred-coding-system 'koi8-r)
9554 This means that Russian will be encoded using @code{koi8-r} instead of
9555 the default @code{iso-8859-5} @acronym{MIME} charset.
9557 If you want to read messages in @code{koi8-u}, you can cheat and say
9560 (define-coding-system-alias 'koi8-u 'koi8-r)
9563 This will almost do the right thing.
9565 And finally, to read charsets like @code{windows-1251}, you can say
9569 (codepage-setup 1251)
9570 (define-coding-system-alias 'windows-1251 'cp1251)
9574 @node Article Commands
9575 @section Article Commands
9582 @kindex A P (Summary)
9583 @vindex gnus-ps-print-hook
9584 @findex gnus-summary-print-article
9585 Generate and print a PostScript image of the article buffer
9586 (@code{gnus-summary-print-article}). @code{gnus-ps-print-hook} will
9587 be run just before printing the buffer. An alternative way to print
9588 article is to use Muttprint (@pxref{Saving Articles}).
9593 @node Summary Sorting
9594 @section Summary Sorting
9595 @cindex summary sorting
9597 You can have the summary buffer sorted in various ways, even though I
9598 can't really see why you'd want that.
9603 @kindex C-c C-s C-n (Summary)
9604 @findex gnus-summary-sort-by-number
9605 Sort by article number (@code{gnus-summary-sort-by-number}).
9608 @kindex C-c C-s C-a (Summary)
9609 @findex gnus-summary-sort-by-author
9610 Sort by author (@code{gnus-summary-sort-by-author}).
9613 @kindex C-c C-s C-t (Summary)
9614 @findex gnus-summary-sort-by-recipient
9615 Sort by recipient (@code{gnus-summary-sort-by-recipient}).
9618 @kindex C-c C-s C-s (Summary)
9619 @findex gnus-summary-sort-by-subject
9620 Sort by subject (@code{gnus-summary-sort-by-subject}).
9623 @kindex C-c C-s C-d (Summary)
9624 @findex gnus-summary-sort-by-date
9625 Sort by date (@code{gnus-summary-sort-by-date}).
9628 @kindex C-c C-s C-l (Summary)
9629 @findex gnus-summary-sort-by-lines
9630 Sort by lines (@code{gnus-summary-sort-by-lines}).
9633 @kindex C-c C-s C-c (Summary)
9634 @findex gnus-summary-sort-by-chars
9635 Sort by article length (@code{gnus-summary-sort-by-chars}).
9638 @kindex C-c C-s C-i (Summary)
9639 @findex gnus-summary-sort-by-score
9640 Sort by score (@code{gnus-summary-sort-by-score}).
9643 @kindex C-c C-s C-r (Summary)
9644 @findex gnus-summary-sort-by-random
9645 Randomize (@code{gnus-summary-sort-by-random}).
9648 @kindex C-c C-s C-o (Summary)
9649 @findex gnus-summary-sort-by-original
9650 Sort using the default sorting method
9651 (@code{gnus-summary-sort-by-original}).
9654 These functions will work both when you use threading and when you don't
9655 use threading. In the latter case, all summary lines will be sorted,
9656 line by line. In the former case, sorting will be done on a
9657 root-by-root basis, which might not be what you were looking for. To
9658 toggle whether to use threading, type @kbd{T T} (@pxref{Thread
9662 @node Finding the Parent
9663 @section Finding the Parent
9664 @cindex parent articles
9665 @cindex referring articles
9670 @findex gnus-summary-refer-parent-article
9671 If you'd like to read the parent of the current article, and it is not
9672 displayed in the summary buffer, you might still be able to. That is,
9673 if the current group is fetched by @acronym{NNTP}, the parent hasn't expired
9674 and the @code{References} in the current article are not mangled, you
9675 can just press @kbd{^} or @kbd{A r}
9676 (@code{gnus-summary-refer-parent-article}). If everything goes well,
9677 you'll get the parent. If the parent is already displayed in the
9678 summary buffer, point will just move to this article.
9680 If given a positive numerical prefix, fetch that many articles back into
9681 the ancestry. If given a negative numerical prefix, fetch just that
9682 ancestor. So if you say @kbd{3 ^}, Gnus will fetch the parent, the
9683 grandparent and the grandgrandparent of the current article. If you say
9684 @kbd{-3 ^}, Gnus will only fetch the grandgrandparent of the current
9688 @findex gnus-summary-refer-references
9689 @kindex A R (Summary)
9690 Fetch all articles mentioned in the @code{References} header of the
9691 article (@code{gnus-summary-refer-references}).
9694 @findex gnus-summary-refer-thread
9695 @kindex A T (Summary)
9696 Display the full thread where the current article appears
9697 (@code{gnus-summary-refer-thread}). This command has to fetch all the
9698 headers in the current group to work, so it usually takes a while. If
9699 you do it often, you may consider setting @code{gnus-fetch-old-headers}
9700 to @code{invisible} (@pxref{Filling In Threads}). This won't have any
9701 visible effects normally, but it'll make this command work a whole lot
9702 faster. Of course, it'll make group entry somewhat slow.
9704 @vindex gnus-refer-thread-limit
9705 The @code{gnus-refer-thread-limit} variable says how many old (i. e.,
9706 articles before the first displayed in the current group) headers to
9707 fetch when doing this command. The default is 200. If @code{t}, all
9708 the available headers will be fetched. This variable can be overridden
9709 by giving the @kbd{A T} command a numerical prefix.
9712 @findex gnus-summary-refer-article
9713 @kindex M-^ (Summary)
9715 @cindex fetching by Message-ID
9716 You can also ask the @acronym{NNTP} server for an arbitrary article, no
9717 matter what group it belongs to. @kbd{M-^}
9718 (@code{gnus-summary-refer-article}) will ask you for a
9719 @code{Message-ID}, which is one of those long, hard-to-read thingies
9720 that look something like @samp{<38o6up$6f2@@hymir.ifi.uio.no>}. You
9721 have to get it all exactly right. No fuzzy searches, I'm afraid.
9724 The current select method will be used when fetching by
9725 @code{Message-ID} from non-news select method, but you can override this
9726 by giving this command a prefix.
9728 @vindex gnus-refer-article-method
9729 If the group you are reading is located on a back end that does not
9730 support fetching by @code{Message-ID} very well (like @code{nnspool}),
9731 you can set @code{gnus-refer-article-method} to an @acronym{NNTP} method. It
9732 would, perhaps, be best if the @acronym{NNTP} server you consult is the one
9733 updating the spool you are reading from, but that's not really
9736 It can also be a list of select methods, as well as the special symbol
9737 @code{current}, which means to use the current select method. If it
9738 is a list, Gnus will try all the methods in the list until it finds a
9741 Here's an example setting that will first try the current method, and
9742 then ask Google if that fails:
9745 (setq gnus-refer-article-method
9747 (nnweb "google" (nnweb-type google))))
9750 Most of the mail back ends support fetching by @code{Message-ID}, but
9751 do not do a particularly excellent job at it. That is, @code{nnmbox},
9752 @code{nnbabyl}, @code{nnmaildir}, @code{nnml}, are able to locate
9753 articles from any groups, while @code{nnfolder}, and @code{nnimap} are
9754 only able to locate articles that have been posted to the current
9755 group. (Anything else would be too time consuming.) @code{nnmh} does
9756 not support this at all.
9759 @node Alternative Approaches
9760 @section Alternative Approaches
9762 Different people like to read news using different methods. This being
9763 Gnus, we offer a small selection of minor modes for the summary buffers.
9766 * Pick and Read:: First mark articles and then read them.
9767 * Binary Groups:: Auto-decode all articles.
9772 @subsection Pick and Read
9773 @cindex pick and read
9775 Some newsreaders (like @code{nn} and, uhm, @code{Netnews} on VM/CMS) use
9776 a two-phased reading interface. The user first marks in a summary
9777 buffer the articles she wants to read. Then she starts reading the
9778 articles with just an article buffer displayed.
9780 @findex gnus-pick-mode
9781 @kindex M-x gnus-pick-mode
9782 Gnus provides a summary buffer minor mode that allows
9783 this---@code{gnus-pick-mode}. This basically means that a few process
9784 mark commands become one-keystroke commands to allow easy marking, and
9785 it provides one additional command for switching to the summary buffer.
9787 Here are the available keystrokes when using pick mode:
9792 @findex gnus-pick-article-or-thread
9793 Pick the article or thread on the current line
9794 (@code{gnus-pick-article-or-thread}). If the variable
9795 @code{gnus-thread-hide-subtree} is true, then this key selects the
9796 entire thread when used at the first article of the thread. Otherwise,
9797 it selects just the article. If given a numerical prefix, go to that
9798 thread or article and pick it. (The line number is normally displayed
9799 at the beginning of the summary pick lines.)
9802 @kindex SPACE (Pick)
9803 @findex gnus-pick-next-page
9804 Scroll the summary buffer up one page (@code{gnus-pick-next-page}). If
9805 at the end of the buffer, start reading the picked articles.
9809 @findex gnus-pick-unmark-article-or-thread.
9810 Unpick the thread or article
9811 (@code{gnus-pick-unmark-article-or-thread}). If the variable
9812 @code{gnus-thread-hide-subtree} is true, then this key unpicks the
9813 thread if used at the first article of the thread. Otherwise it unpicks
9814 just the article. You can give this key a numerical prefix to unpick
9815 the thread or article at that line.
9819 @findex gnus-pick-start-reading
9820 @vindex gnus-pick-display-summary
9821 Start reading the picked articles (@code{gnus-pick-start-reading}). If
9822 given a prefix, mark all unpicked articles as read first. If
9823 @code{gnus-pick-display-summary} is non-@code{nil}, the summary buffer
9824 will still be visible when you are reading.
9828 All the normal summary mode commands are still available in the
9829 pick-mode, with the exception of @kbd{u}. However @kbd{!} is available
9830 which is mapped to the same function
9831 @code{gnus-summary-tick-article-forward}.
9833 If this sounds like a good idea to you, you could say:
9836 (add-hook 'gnus-summary-mode-hook 'gnus-pick-mode)
9839 @vindex gnus-pick-mode-hook
9840 @code{gnus-pick-mode-hook} is run in pick minor mode buffers.
9842 @vindex gnus-mark-unpicked-articles-as-read
9843 If @code{gnus-mark-unpicked-articles-as-read} is non-@code{nil}, mark
9844 all unpicked articles as read. The default is @code{nil}.
9846 @vindex gnus-summary-pick-line-format
9847 The summary line format in pick mode is slightly different from the
9848 standard format. At the beginning of each line the line number is
9849 displayed. The pick mode line format is controlled by the
9850 @code{gnus-summary-pick-line-format} variable (@pxref{Formatting
9851 Variables}). It accepts the same format specs that
9852 @code{gnus-summary-line-format} does (@pxref{Summary Buffer Lines}).
9856 @subsection Binary Groups
9857 @cindex binary groups
9859 @findex gnus-binary-mode
9860 @kindex M-x gnus-binary-mode
9861 If you spend much time in binary groups, you may grow tired of hitting
9862 @kbd{X u}, @kbd{n}, @kbd{RET} all the time. @kbd{M-x gnus-binary-mode}
9863 is a minor mode for summary buffers that makes all ordinary Gnus article
9864 selection functions uudecode series of articles and display the result
9865 instead of just displaying the articles the normal way.
9868 @findex gnus-binary-show-article
9869 The only way, in fact, to see the actual articles is the @kbd{g}
9870 command, when you have turned on this mode
9871 (@code{gnus-binary-show-article}).
9873 @vindex gnus-binary-mode-hook
9874 @code{gnus-binary-mode-hook} is called in binary minor mode buffers.
9878 @section Tree Display
9881 @vindex gnus-use-trees
9882 If you don't like the normal Gnus summary display, you might try setting
9883 @code{gnus-use-trees} to @code{t}. This will create (by default) an
9884 additional @dfn{tree buffer}. You can execute all summary mode commands
9887 There are a few variables to customize the tree display, of course:
9890 @item gnus-tree-mode-hook
9891 @vindex gnus-tree-mode-hook
9892 A hook called in all tree mode buffers.
9894 @item gnus-tree-mode-line-format
9895 @vindex gnus-tree-mode-line-format
9896 A format string for the mode bar in the tree mode buffers (@pxref{Mode
9897 Line Formatting}). The default is @samp{Gnus: %%b %S %Z}. For a list
9898 of valid specs, @pxref{Summary Buffer Mode Line}.
9900 @item gnus-selected-tree-face
9901 @vindex gnus-selected-tree-face
9902 Face used for highlighting the selected article in the tree buffer. The
9903 default is @code{modeline}.
9905 @item gnus-tree-line-format
9906 @vindex gnus-tree-line-format
9907 A format string for the tree nodes. The name is a bit of a misnomer,
9908 though---it doesn't define a line, but just the node. The default value
9909 is @samp{%(%[%3,3n%]%)}, which displays the first three characters of
9910 the name of the poster. It is vital that all nodes are of the same
9911 length, so you @emph{must} use @samp{%4,4n}-like specifiers.
9917 The name of the poster.
9919 The @code{From} header.
9921 The number of the article.
9923 The opening bracket.
9925 The closing bracket.
9930 @xref{Formatting Variables}.
9932 Variables related to the display are:
9935 @item gnus-tree-brackets
9936 @vindex gnus-tree-brackets
9937 This is used for differentiating between ``real'' articles and
9938 ``sparse'' articles. The format is
9940 ((@var{real-open} . @var{real-close})
9941 (@var{sparse-open} . @var{sparse-close})
9942 (@var{dummy-open} . @var{dummy-close}))
9944 and the default is @code{((?[ . ?]) (?( . ?)) (?@{ . ?@}) (?< . ?>))}.
9946 @item gnus-tree-parent-child-edges
9947 @vindex gnus-tree-parent-child-edges
9948 This is a list that contains the characters used for connecting parent
9949 nodes to their children. The default is @code{(?- ?\\ ?|)}.
9953 @item gnus-tree-minimize-window
9954 @vindex gnus-tree-minimize-window
9955 If this variable is non-@code{nil}, Gnus will try to keep the tree
9956 buffer as small as possible to allow more room for the other Gnus
9957 windows. If this variable is a number, the tree buffer will never be
9958 higher than that number. The default is @code{t}. Note that if you
9959 have several windows displayed side-by-side in a frame and the tree
9960 buffer is one of these, minimizing the tree window will also resize all
9961 other windows displayed next to it.
9963 You may also wish to add the following hook to keep the window minimized
9967 (add-hook 'gnus-configure-windows-hook
9968 'gnus-tree-perhaps-minimize)
9971 @item gnus-generate-tree-function
9972 @vindex gnus-generate-tree-function
9973 @findex gnus-generate-horizontal-tree
9974 @findex gnus-generate-vertical-tree
9975 The function that actually generates the thread tree. Two predefined
9976 functions are available: @code{gnus-generate-horizontal-tree} and
9977 @code{gnus-generate-vertical-tree} (which is the default).
9981 Here's an example from a horizontal tree buffer:
9984 @{***@}-(***)-[odd]-[Gun]
9994 Here's the same thread displayed in a vertical tree buffer:
9999 |--------------------------\-----\-----\
10000 (***) [Bjo] [Gun] [Gun]
10002 [odd] [Jan] [odd] (***) [Jor]
10004 [Gun] [Eri] [Eri] [odd]
10010 If you're using horizontal trees, it might be nice to display the trees
10011 side-by-side with the summary buffer. You could add something like the
10012 following to your @file{~/.gnus.el} file:
10015 (setq gnus-use-trees t
10016 gnus-generate-tree-function 'gnus-generate-horizontal-tree
10017 gnus-tree-minimize-window nil)
10018 (gnus-add-configuration
10022 (summary 0.75 point)
10027 @xref{Window Layout}.
10030 @node Mail Group Commands
10031 @section Mail Group Commands
10032 @cindex mail group commands
10034 Some commands only make sense in mail groups. If these commands are
10035 invalid in the current group, they will raise a hell and let you know.
10037 All these commands (except the expiry and edit commands) use the
10038 process/prefix convention (@pxref{Process/Prefix}).
10043 @kindex B e (Summary)
10044 @findex gnus-summary-expire-articles
10045 Run all expirable articles in the current group through the expiry
10046 process (@code{gnus-summary-expire-articles}). That is, delete all
10047 expirable articles in the group that have been around for a while.
10048 (@pxref{Expiring Mail}).
10051 @kindex B C-M-e (Summary)
10052 @findex gnus-summary-expire-articles-now
10053 Delete all the expirable articles in the group
10054 (@code{gnus-summary-expire-articles-now}). This means that @strong{all}
10055 articles eligible for expiry in the current group will
10056 disappear forever into that big @file{/dev/null} in the sky.
10059 @kindex B DEL (Summary)
10060 @findex gnus-summary-delete-article
10061 @c @icon{gnus-summary-mail-delete}
10062 Delete the mail article. This is ``delete'' as in ``delete it from your
10063 disk forever and ever, never to return again.'' Use with caution.
10064 (@code{gnus-summary-delete-article}).
10067 @kindex B m (Summary)
10069 @findex gnus-summary-move-article
10070 @vindex gnus-preserve-marks
10071 Move the article from one mail group to another
10072 (@code{gnus-summary-move-article}). Marks will be preserved if
10073 @code{gnus-preserve-marks} is non-@code{nil} (which is the default).
10076 @kindex B c (Summary)
10078 @findex gnus-summary-copy-article
10079 @c @icon{gnus-summary-mail-copy}
10080 Copy the article from one group (mail group or not) to a mail group
10081 (@code{gnus-summary-copy-article}). Marks will be preserved if
10082 @code{gnus-preserve-marks} is non-@code{nil} (which is the default).
10085 @kindex B B (Summary)
10086 @cindex crosspost mail
10087 @findex gnus-summary-crosspost-article
10088 Crosspost the current article to some other group
10089 (@code{gnus-summary-crosspost-article}). This will create a new copy of
10090 the article in the other group, and the Xref headers of the article will
10091 be properly updated.
10094 @kindex B i (Summary)
10095 @findex gnus-summary-import-article
10096 Import an arbitrary file into the current mail newsgroup
10097 (@code{gnus-summary-import-article}). You will be prompted for a file
10098 name, a @code{From} header and a @code{Subject} header.
10101 @kindex B I (Summary)
10102 @findex gnus-summary-create-article
10103 Create an empty article in the current mail newsgroups
10104 (@code{gnus-summary-create-article}). You will be prompted for a
10105 @code{From} header and a @code{Subject} header.
10108 @kindex B r (Summary)
10109 @findex gnus-summary-respool-article
10110 @vindex gnus-summary-respool-default-method
10111 Respool the mail article (@code{gnus-summary-respool-article}).
10112 @code{gnus-summary-respool-default-method} will be used as the default
10113 select method when respooling. This variable is @code{nil} by default,
10114 which means that the current group select method will be used instead.
10115 Marks will be preserved if @code{gnus-preserve-marks} is non-@code{nil}
10116 (which is the default).
10120 @kindex B w (Summary)
10121 @kindex e (Summary)
10122 @findex gnus-summary-edit-article
10123 @kindex C-c C-c (Article)
10124 @findex gnus-summary-edit-article-done
10125 Edit the current article (@code{gnus-summary-edit-article}). To finish
10126 editing and make the changes permanent, type @kbd{C-c C-c}
10127 (@code{gnus-summary-edit-article-done}). If you give a prefix to the
10128 @kbd{C-c C-c} command, Gnus won't re-highlight the article.
10131 @kindex B q (Summary)
10132 @findex gnus-summary-respool-query
10133 If you want to re-spool an article, you might be curious as to what group
10134 the article will end up in before you do the re-spooling. This command
10135 will tell you (@code{gnus-summary-respool-query}).
10138 @kindex B t (Summary)
10139 @findex gnus-summary-respool-trace
10140 Similarly, this command will display all fancy splitting patterns used
10141 when respooling, if any (@code{gnus-summary-respool-trace}).
10144 @kindex B p (Summary)
10145 @findex gnus-summary-article-posted-p
10146 Some people have a tendency to send you ``courtesy'' copies when they
10147 follow up to articles you have posted. These usually have a
10148 @code{Newsgroups} header in them, but not always. This command
10149 (@code{gnus-summary-article-posted-p}) will try to fetch the current
10150 article from your news server (or rather, from
10151 @code{gnus-refer-article-method} or @code{gnus-select-method}) and will
10152 report back whether it found the article or not. Even if it says that
10153 it didn't find the article, it may have been posted anyway---mail
10154 propagation is much faster than news propagation, and the news copy may
10155 just not have arrived yet.
10158 @kindex K E (Summary)
10159 @findex gnus-article-encrypt-body
10160 @vindex gnus-article-encrypt-protocol
10161 Encrypt the body of an article (@code{gnus-article-encrypt-body}).
10162 The body is encrypted with the encryption protocol specified by the
10163 variable @code{gnus-article-encrypt-protocol}.
10167 @vindex gnus-move-split-methods
10168 @cindex moving articles
10169 If you move (or copy) articles regularly, you might wish to have Gnus
10170 suggest where to put the articles. @code{gnus-move-split-methods} is a
10171 variable that uses the same syntax as @code{gnus-split-methods}
10172 (@pxref{Saving Articles}). You may customize that variable to create
10173 suggestions you find reasonable. (Note that
10174 @code{gnus-move-split-methods} uses group names where
10175 @code{gnus-split-methods} uses file names.)
10178 (setq gnus-move-split-methods
10179 '(("^From:.*Lars Magne" "nnml:junk")
10180 ("^Subject:.*gnus" "nnfolder:important")
10181 (".*" "nnml:misc")))
10185 @node Various Summary Stuff
10186 @section Various Summary Stuff
10189 * Summary Group Information:: Information oriented commands.
10190 * Searching for Articles:: Multiple article commands.
10191 * Summary Generation Commands::
10192 * Really Various Summary Commands:: Those pesky non-conformant commands.
10196 @vindex gnus-summary-display-while-building
10197 @item gnus-summary-display-while-building
10198 If non-@code{nil}, show and update the summary buffer as it's being
10199 built. If @code{t}, update the buffer after every line is inserted.
10200 If the value is an integer, @var{n}, update the display every @var{n}
10201 lines. The default is @code{nil}.
10203 @vindex gnus-summary-display-arrow
10204 @item gnus-summary-display-arrow
10205 If non-@code{nil}, display an arrow in the fringe to indicate the
10208 @vindex gnus-summary-mode-hook
10209 @item gnus-summary-mode-hook
10210 This hook is called when creating a summary mode buffer.
10212 @vindex gnus-summary-generate-hook
10213 @item gnus-summary-generate-hook
10214 This is called as the last thing before doing the threading and the
10215 generation of the summary buffer. It's quite convenient for customizing
10216 the threading variables based on what data the newsgroup has. This hook
10217 is called from the summary buffer after most summary buffer variables
10220 @vindex gnus-summary-prepare-hook
10221 @item gnus-summary-prepare-hook
10222 It is called after the summary buffer has been generated. You might use
10223 it to, for instance, highlight lines or modify the look of the buffer in
10224 some other ungodly manner. I don't care.
10226 @vindex gnus-summary-prepared-hook
10227 @item gnus-summary-prepared-hook
10228 A hook called as the very last thing after the summary buffer has been
10231 @vindex gnus-summary-ignore-duplicates
10232 @item gnus-summary-ignore-duplicates
10233 When Gnus discovers two articles that have the same @code{Message-ID},
10234 it has to do something drastic. No articles are allowed to have the
10235 same @code{Message-ID}, but this may happen when reading mail from some
10236 sources. Gnus allows you to customize what happens with this variable.
10237 If it is @code{nil} (which is the default), Gnus will rename the
10238 @code{Message-ID} (for display purposes only) and display the article as
10239 any other article. If this variable is @code{t}, it won't display the
10240 article---it'll be as if it never existed.
10242 @vindex gnus-alter-articles-to-read-function
10243 @item gnus-alter-articles-to-read-function
10244 This function, which takes two parameters (the group name and the list
10245 of articles to be selected), is called to allow the user to alter the
10246 list of articles to be selected.
10248 For instance, the following function adds the list of cached articles to
10249 the list in one particular group:
10252 (defun my-add-cached-articles (group articles)
10253 (if (string= group "some.group")
10254 (append gnus-newsgroup-cached articles)
10258 @vindex gnus-newsgroup-variables
10259 @item gnus-newsgroup-variables
10260 A list of newsgroup (summary buffer) local variables, or cons of
10261 variables and their default expressions to be evalled (when the default
10262 values are not @code{nil}), that should be made global while the summary
10265 Note: The default expressions will be evaluated (using function
10266 @code{eval}) before assignment to the local variable rather than just
10267 assigned to it. If the default expression is the symbol @code{global},
10268 that symbol will not be evaluated but the global value of the local
10269 variable will be used instead.
10271 These variables can be used to set variables in the group parameters
10272 while still allowing them to affect operations done in other
10273 buffers. For example:
10276 (setq gnus-newsgroup-variables
10277 '(message-use-followup-to
10278 (gnus-visible-headers .
10279 "^From:\\|^Newsgroups:\\|^Subject:\\|^Date:\\|^To:")))
10282 Also @pxref{Group Parameters}.
10286 @node Summary Group Information
10287 @subsection Summary Group Information
10292 @kindex H f (Summary)
10293 @findex gnus-summary-fetch-faq
10294 @vindex gnus-group-faq-directory
10295 Try to fetch the @acronym{FAQ} (list of frequently asked questions)
10296 for the current group (@code{gnus-summary-fetch-faq}). Gnus will try
10297 to get the @acronym{FAQ} from @code{gnus-group-faq-directory}, which
10298 is usually a directory on a remote machine. This variable can also be
10299 a list of directories. In that case, giving a prefix to this command
10300 will allow you to choose between the various sites. @code{ange-ftp}
10301 or @code{efs} will probably be used for fetching the file.
10304 @kindex H d (Summary)
10305 @findex gnus-summary-describe-group
10306 Give a brief description of the current group
10307 (@code{gnus-summary-describe-group}). If given a prefix, force
10308 rereading the description from the server.
10311 @kindex H h (Summary)
10312 @findex gnus-summary-describe-briefly
10313 Give an extremely brief description of the most important summary
10314 keystrokes (@code{gnus-summary-describe-briefly}).
10317 @kindex H i (Summary)
10318 @findex gnus-info-find-node
10319 Go to the Gnus info node (@code{gnus-info-find-node}).
10323 @node Searching for Articles
10324 @subsection Searching for Articles
10329 @kindex M-s (Summary)
10330 @findex gnus-summary-search-article-forward
10331 Search through all subsequent (raw) articles for a regexp
10332 (@code{gnus-summary-search-article-forward}).
10335 @kindex M-r (Summary)
10336 @findex gnus-summary-search-article-backward
10337 Search through all previous (raw) articles for a regexp
10338 (@code{gnus-summary-search-article-backward}).
10341 @kindex & (Summary)
10342 @findex gnus-summary-execute-command
10343 This command will prompt you for a header, a regular expression to match
10344 on this field, and a command to be executed if the match is made
10345 (@code{gnus-summary-execute-command}). If the header is an empty
10346 string, the match is done on the entire article. If given a prefix,
10347 search backward instead.
10349 For instance, @kbd{& RET some.*string RET #} will put the process mark on
10350 all articles that have heads or bodies that match @samp{some.*string}.
10353 @kindex M-& (Summary)
10354 @findex gnus-summary-universal-argument
10355 Perform any operation on all articles that have been marked with
10356 the process mark (@code{gnus-summary-universal-argument}).
10359 @node Summary Generation Commands
10360 @subsection Summary Generation Commands
10365 @kindex Y g (Summary)
10366 @findex gnus-summary-prepare
10367 Regenerate the current summary buffer (@code{gnus-summary-prepare}).
10370 @kindex Y c (Summary)
10371 @findex gnus-summary-insert-cached-articles
10372 Pull all cached articles (for the current group) into the summary buffer
10373 (@code{gnus-summary-insert-cached-articles}).
10376 @kindex Y d (Summary)
10377 @findex gnus-summary-insert-dormant-articles
10378 Pull all dormant articles (for the current group) into the summary buffer
10379 (@code{gnus-summary-insert-dormant-articles}).
10384 @node Really Various Summary Commands
10385 @subsection Really Various Summary Commands
10391 @kindex C-d (Summary)
10392 @kindex A D (Summary)
10393 @findex gnus-summary-enter-digest-group
10394 If the current article is a collection of other articles (for instance,
10395 a digest), you might use this command to enter a group based on the that
10396 article (@code{gnus-summary-enter-digest-group}). Gnus will try to
10397 guess what article type is currently displayed unless you give a prefix
10398 to this command, which forces a ``digest'' interpretation. Basically,
10399 whenever you see a message that is a collection of other messages of
10400 some format, you @kbd{C-d} and read these messages in a more convenient
10404 @kindex C-M-d (Summary)
10405 @findex gnus-summary-read-document
10406 This command is very similar to the one above, but lets you gather
10407 several documents into one biiig group
10408 (@code{gnus-summary-read-document}). It does this by opening several
10409 @code{nndoc} groups for each document, and then opening an
10410 @code{nnvirtual} group on top of these @code{nndoc} groups. This
10411 command understands the process/prefix convention
10412 (@pxref{Process/Prefix}).
10415 @kindex C-t (Summary)
10416 @findex gnus-summary-toggle-truncation
10417 Toggle truncation of summary lines
10418 (@code{gnus-summary-toggle-truncation}). This will probably confuse the
10419 line centering function in the summary buffer, so it's not a good idea
10420 to have truncation switched off while reading articles.
10423 @kindex = (Summary)
10424 @findex gnus-summary-expand-window
10425 Expand the summary buffer window (@code{gnus-summary-expand-window}).
10426 If given a prefix, force an @code{article} window configuration.
10429 @kindex C-M-e (Summary)
10430 @findex gnus-summary-edit-parameters
10431 Edit the group parameters (@pxref{Group Parameters}) of the current
10432 group (@code{gnus-summary-edit-parameters}).
10435 @kindex C-M-a (Summary)
10436 @findex gnus-summary-customize-parameters
10437 Customize the group parameters (@pxref{Group Parameters}) of the current
10438 group (@code{gnus-summary-customize-parameters}).
10443 @node Exiting the Summary Buffer
10444 @section Exiting the Summary Buffer
10445 @cindex summary exit
10446 @cindex exiting groups
10448 Exiting from the summary buffer will normally update all info on the
10449 group and return you to the group buffer.
10456 @kindex Z Z (Summary)
10457 @kindex Z Q (Summary)
10458 @kindex q (Summary)
10459 @findex gnus-summary-exit
10460 @vindex gnus-summary-exit-hook
10461 @vindex gnus-summary-prepare-exit-hook
10462 @vindex gnus-group-no-more-groups-hook
10463 @c @icon{gnus-summary-exit}
10464 Exit the current group and update all information on the group
10465 (@code{gnus-summary-exit}). @code{gnus-summary-prepare-exit-hook} is
10466 called before doing much of the exiting, which calls
10467 @code{gnus-summary-expire-articles} by default.
10468 @code{gnus-summary-exit-hook} is called after finishing the exit
10469 process. @code{gnus-group-no-more-groups-hook} is run when returning to
10470 group mode having no more (unread) groups.
10474 @kindex Z E (Summary)
10475 @kindex Q (Summary)
10476 @findex gnus-summary-exit-no-update
10477 Exit the current group without updating any information on the group
10478 (@code{gnus-summary-exit-no-update}).
10482 @kindex Z c (Summary)
10483 @kindex c (Summary)
10484 @findex gnus-summary-catchup-and-exit
10485 @c @icon{gnus-summary-catchup-and-exit}
10486 Mark all unticked articles in the group as read and then exit
10487 (@code{gnus-summary-catchup-and-exit}).
10490 @kindex Z C (Summary)
10491 @findex gnus-summary-catchup-all-and-exit
10492 Mark all articles, even the ticked ones, as read and then exit
10493 (@code{gnus-summary-catchup-all-and-exit}).
10496 @kindex Z n (Summary)
10497 @findex gnus-summary-catchup-and-goto-next-group
10498 Mark all articles as read and go to the next group
10499 (@code{gnus-summary-catchup-and-goto-next-group}).
10503 @kindex Z R (Summary)
10504 @kindex C-x C-s (Summary)
10505 @findex gnus-summary-reselect-current-group
10506 Exit this group, and then enter it again
10507 (@code{gnus-summary-reselect-current-group}). If given a prefix, select
10508 all articles, both read and unread.
10512 @kindex Z G (Summary)
10513 @kindex M-g (Summary)
10514 @findex gnus-summary-rescan-group
10515 @c @icon{gnus-summary-mail-get}
10516 Exit the group, check for new articles in the group, and select the
10517 group (@code{gnus-summary-rescan-group}). If given a prefix, select all
10518 articles, both read and unread.
10521 @kindex Z N (Summary)
10522 @findex gnus-summary-next-group
10523 Exit the group and go to the next group
10524 (@code{gnus-summary-next-group}).
10527 @kindex Z P (Summary)
10528 @findex gnus-summary-prev-group
10529 Exit the group and go to the previous group
10530 (@code{gnus-summary-prev-group}).
10533 @kindex Z s (Summary)
10534 @findex gnus-summary-save-newsrc
10535 Save the current number of read/marked articles in the dribble buffer
10536 and then save the dribble buffer (@code{gnus-summary-save-newsrc}). If
10537 given a prefix, also save the @file{.newsrc} file(s). Using this
10538 command will make exit without updating (the @kbd{Q} command) worthless.
10541 @vindex gnus-exit-group-hook
10542 @code{gnus-exit-group-hook} is called when you exit the current group
10543 with an ``updating'' exit. For instance @kbd{Q}
10544 (@code{gnus-summary-exit-no-update}) does not call this hook.
10546 @findex gnus-summary-wake-up-the-dead
10547 @findex gnus-dead-summary-mode
10548 @vindex gnus-kill-summary-on-exit
10549 If you're in the habit of exiting groups, and then changing your mind
10550 about it, you might set @code{gnus-kill-summary-on-exit} to @code{nil}.
10551 If you do that, Gnus won't kill the summary buffer when you exit it.
10552 (Quelle surprise!) Instead it will change the name of the buffer to
10553 something like @samp{*Dead Summary ... *} and install a minor mode
10554 called @code{gnus-dead-summary-mode}. Now, if you switch back to this
10555 buffer, you'll find that all keys are mapped to a function called
10556 @code{gnus-summary-wake-up-the-dead}. So tapping any keys in a dead
10557 summary buffer will result in a live, normal summary buffer.
10559 There will never be more than one dead summary buffer at any one time.
10561 @vindex gnus-use-cross-reference
10562 The data on the current group will be updated (which articles you have
10563 read, which articles you have replied to, etc.) when you exit the
10564 summary buffer. If the @code{gnus-use-cross-reference} variable is
10565 @code{t} (which is the default), articles that are cross-referenced to
10566 this group and are marked as read, will also be marked as read in the
10567 other subscribed groups they were cross-posted to. If this variable is
10568 neither @code{nil} nor @code{t}, the article will be marked as read in
10569 both subscribed and unsubscribed groups (@pxref{Crosspost Handling}).
10572 @node Crosspost Handling
10573 @section Crosspost Handling
10577 Marking cross-posted articles as read ensures that you'll never have to
10578 read the same article more than once. Unless, of course, somebody has
10579 posted it to several groups separately. Posting the same article to
10580 several groups (not cross-posting) is called @dfn{spamming}, and you are
10581 by law required to send nasty-grams to anyone who perpetrates such a
10582 heinous crime. You may want to try NoCeM handling to filter out spam
10585 Remember: Cross-posting is kinda ok, but posting the same article
10586 separately to several groups is not. Massive cross-posting (aka.
10587 @dfn{velveeta}) is to be avoided at all costs, and you can even use the
10588 @code{gnus-summary-mail-crosspost-complaint} command to complain about
10589 excessive crossposting (@pxref{Summary Mail Commands}).
10591 @cindex cross-posting
10593 @cindex @acronym{NOV}
10594 One thing that may cause Gnus to not do the cross-posting thing
10595 correctly is if you use an @acronym{NNTP} server that supports @sc{xover}
10596 (which is very nice, because it speeds things up considerably) which
10597 does not include the @code{Xref} header in its @acronym{NOV} lines. This is
10598 Evil, but all too common, alas, alack. Gnus tries to Do The Right Thing
10599 even with @sc{xover} by registering the @code{Xref} lines of all
10600 articles you actually read, but if you kill the articles, or just mark
10601 them as read without reading them, Gnus will not get a chance to snoop
10602 the @code{Xref} lines out of these articles, and will be unable to use
10603 the cross reference mechanism.
10605 @cindex LIST overview.fmt
10606 @cindex overview.fmt
10607 To check whether your @acronym{NNTP} server includes the @code{Xref} header
10608 in its overview files, try @samp{telnet your.nntp.server nntp},
10609 @samp{MODE READER} on @code{inn} servers, and then say @samp{LIST
10610 overview.fmt}. This may not work, but if it does, and the last line you
10611 get does not read @samp{Xref:full}, then you should shout and whine at
10612 your news admin until she includes the @code{Xref} header in the
10615 @vindex gnus-nov-is-evil
10616 If you want Gnus to get the @code{Xref}s right all the time, you have to
10617 set @code{gnus-nov-is-evil} to @code{t}, which slows things down
10622 For an alternative approach, @pxref{Duplicate Suppression}.
10625 @node Duplicate Suppression
10626 @section Duplicate Suppression
10628 By default, Gnus tries to make sure that you don't have to read the same
10629 article more than once by utilizing the crossposting mechanism
10630 (@pxref{Crosspost Handling}). However, that simple and efficient
10631 approach may not work satisfactory for some users for various
10636 The @acronym{NNTP} server may fail to generate the @code{Xref} header. This
10637 is evil and not very common.
10640 The @acronym{NNTP} server may fail to include the @code{Xref} header in the
10641 @file{.overview} data bases. This is evil and all too common, alas.
10644 You may be reading the same group (or several related groups) from
10645 different @acronym{NNTP} servers.
10648 You may be getting mail that duplicates articles posted to groups.
10651 I'm sure there are other situations where @code{Xref} handling fails as
10652 well, but these four are the most common situations.
10654 If, and only if, @code{Xref} handling fails for you, then you may
10655 consider switching on @dfn{duplicate suppression}. If you do so, Gnus
10656 will remember the @code{Message-ID}s of all articles you have read or
10657 otherwise marked as read, and then, as if by magic, mark them as read
10658 all subsequent times you see them---in @emph{all} groups. Using this
10659 mechanism is quite likely to be somewhat inefficient, but not overly
10660 so. It's certainly preferable to reading the same articles more than
10663 Duplicate suppression is not a very subtle instrument. It's more like a
10664 sledge hammer than anything else. It works in a very simple
10665 fashion---if you have marked an article as read, it adds this Message-ID
10666 to a cache. The next time it sees this Message-ID, it will mark the
10667 article as read with the @samp{M} mark. It doesn't care what group it
10668 saw the article in.
10671 @item gnus-suppress-duplicates
10672 @vindex gnus-suppress-duplicates
10673 If non-@code{nil}, suppress duplicates.
10675 @item gnus-save-duplicate-list
10676 @vindex gnus-save-duplicate-list
10677 If non-@code{nil}, save the list of duplicates to a file. This will
10678 make startup and shutdown take longer, so the default is @code{nil}.
10679 However, this means that only duplicate articles read in a single Gnus
10680 session are suppressed.
10682 @item gnus-duplicate-list-length
10683 @vindex gnus-duplicate-list-length
10684 This variable says how many @code{Message-ID}s to keep in the duplicate
10685 suppression list. The default is 10000.
10687 @item gnus-duplicate-file
10688 @vindex gnus-duplicate-file
10689 The name of the file to store the duplicate suppression list in. The
10690 default is @file{~/News/suppression}.
10693 If you have a tendency to stop and start Gnus often, setting
10694 @code{gnus-save-duplicate-list} to @code{t} is probably a good idea. If
10695 you leave Gnus running for weeks on end, you may have it @code{nil}. On
10696 the other hand, saving the list makes startup and shutdown much slower,
10697 so that means that if you stop and start Gnus often, you should set
10698 @code{gnus-save-duplicate-list} to @code{nil}. Uhm. I'll leave this up
10699 to you to figure out, I think.
10704 Gnus is able to verify signed messages or decrypt encrypted messages.
10705 The formats that are supported are @acronym{PGP}, @acronym{PGP/MIME}
10706 and @acronym{S/MIME}, however you need some external programs to get
10711 To handle @acronym{PGP} and @acronym{PGP/MIME} messages, you have to
10712 install an OpenPGP implementation such as GnuPG. The Lisp interface
10713 to GnuPG included with Gnus is called PGG (@pxref{Top, ,PGG, pgg, PGG
10714 Manual}), but Mailcrypt and gpg.el are also supported.
10717 To handle @acronym{S/MIME} message, you need to install OpenSSL. OpenSSL 0.9.6
10718 or newer is recommended.
10722 More information on how to set things up can be found in the message
10723 manual (@pxref{Security, ,Security, message, Message Manual}).
10726 @item mm-verify-option
10727 @vindex mm-verify-option
10728 Option of verifying signed parts. @code{never}, not verify;
10729 @code{always}, always verify; @code{known}, only verify known
10730 protocols. Otherwise, ask user.
10732 @item mm-decrypt-option
10733 @vindex mm-decrypt-option
10734 Option of decrypting encrypted parts. @code{never}, no decryption;
10735 @code{always}, always decrypt; @code{known}, only decrypt known
10736 protocols. Otherwise, ask user.
10739 @vindex mml1991-use
10740 Symbol indicating elisp interface to OpenPGP implementation for
10741 @acronym{PGP} messages. The default is @code{pgg}, but
10742 @code{mailcrypt} and @code{gpg} are also supported although
10746 @vindex mml2015-use
10747 Symbol indicating elisp interface to OpenPGP implementation for
10748 @acronym{PGP/MIME} messages. The default is @code{pgg}, but
10749 @code{mailcrypt} and @code{gpg} are also supported although
10754 @cindex snarfing keys
10755 @cindex importing PGP keys
10756 @cindex PGP key ring import
10757 Snarfing OpenPGP keys (i.e., importing keys from articles into your
10758 key ring) is not supported explicitly through a menu item or command,
10759 rather Gnus do detect and label keys as @samp{application/pgp-keys},
10760 allowing you to specify whatever action you think is appropriate
10761 through the usual @acronym{MIME} infrastructure. You can use a
10762 @file{~/.mailcap} entry (@pxref{mailcap, , mailcap, emacs-mime, The
10763 Emacs MIME Manual}) such as the following to import keys using GNU
10764 Privacy Guard when you click on the @acronym{MIME} button
10765 (@pxref{Using MIME}).
10768 application/pgp-keys; gpg --import --interactive --verbose; needsterminal
10771 This happens to also be the default action defined in
10772 @code{mailcap-mime-data}.
10775 @section Mailing List
10776 @cindex mailing list
10779 @kindex A M (summary)
10780 @findex gnus-mailing-list-insinuate
10781 Gnus understands some mailing list fields of RFC 2369. To enable it,
10782 add a @code{to-list} group parameter (@pxref{Group Parameters}),
10783 possibly using @kbd{A M} (@code{gnus-mailing-list-insinuate}) in the
10786 That enables the following commands to the summary buffer:
10791 @kindex C-c C-n h (Summary)
10792 @findex gnus-mailing-list-help
10793 Send a message to fetch mailing list help, if List-Help field exists.
10796 @kindex C-c C-n s (Summary)
10797 @findex gnus-mailing-list-subscribe
10798 Send a message to subscribe the mailing list, if List-Subscribe field exists.
10801 @kindex C-c C-n u (Summary)
10802 @findex gnus-mailing-list-unsubscribe
10803 Send a message to unsubscribe the mailing list, if List-Unsubscribe
10807 @kindex C-c C-n p (Summary)
10808 @findex gnus-mailing-list-post
10809 Post to the mailing list, if List-Post field exists.
10812 @kindex C-c C-n o (Summary)
10813 @findex gnus-mailing-list-owner
10814 Send a message to the mailing list owner, if List-Owner field exists.
10817 @kindex C-c C-n a (Summary)
10818 @findex gnus-mailing-list-archive
10819 Browse the mailing list archive, if List-Archive field exists.
10824 @node Article Buffer
10825 @chapter Article Buffer
10826 @cindex article buffer
10828 The articles are displayed in the article buffer, of which there is only
10829 one. All the summary buffers share the same article buffer unless you
10830 tell Gnus otherwise.
10833 * Hiding Headers:: Deciding what headers should be displayed.
10834 * Using MIME:: Pushing articles through @acronym{MIME} before reading them.
10835 * Customizing Articles:: Tailoring the look of the articles.
10836 * Article Keymap:: Keystrokes available in the article buffer.
10837 * Misc Article:: Other stuff.
10841 @node Hiding Headers
10842 @section Hiding Headers
10843 @cindex hiding headers
10844 @cindex deleting headers
10846 The top section of each article is the @dfn{head}. (The rest is the
10847 @dfn{body}, but you may have guessed that already.)
10849 @vindex gnus-show-all-headers
10850 There is a lot of useful information in the head: the name of the person
10851 who wrote the article, the date it was written and the subject of the
10852 article. That's well and nice, but there's also lots of information
10853 most people do not want to see---what systems the article has passed
10854 through before reaching you, the @code{Message-ID}, the
10855 @code{References}, etc. ad nauseam---and you'll probably want to get rid
10856 of some of those lines. If you want to keep all those lines in the
10857 article buffer, you can set @code{gnus-show-all-headers} to @code{t}.
10859 Gnus provides you with two variables for sifting headers:
10863 @item gnus-visible-headers
10864 @vindex gnus-visible-headers
10865 If this variable is non-@code{nil}, it should be a regular expression
10866 that says what headers you wish to keep in the article buffer. All
10867 headers that do not match this variable will be hidden.
10869 For instance, if you only want to see the name of the person who wrote
10870 the article and the subject, you'd say:
10873 (setq gnus-visible-headers "^From:\\|^Subject:")
10876 This variable can also be a list of regexps to match headers to
10879 @item gnus-ignored-headers
10880 @vindex gnus-ignored-headers
10881 This variable is the reverse of @code{gnus-visible-headers}. If this
10882 variable is set (and @code{gnus-visible-headers} is @code{nil}), it
10883 should be a regular expression that matches all lines that you want to
10884 hide. All lines that do not match this variable will remain visible.
10886 For instance, if you just want to get rid of the @code{References} line
10887 and the @code{Xref} line, you might say:
10890 (setq gnus-ignored-headers "^References:\\|^Xref:")
10893 This variable can also be a list of regexps to match headers to
10896 Note that if @code{gnus-visible-headers} is non-@code{nil}, this
10897 variable will have no effect.
10901 @vindex gnus-sorted-header-list
10902 Gnus can also sort the headers for you. (It does this by default.) You
10903 can control the sorting by setting the @code{gnus-sorted-header-list}
10904 variable. It is a list of regular expressions that says in what order
10905 the headers are to be displayed.
10907 For instance, if you want the name of the author of the article first,
10908 and then the subject, you might say something like:
10911 (setq gnus-sorted-header-list '("^From:" "^Subject:"))
10914 Any headers that are to remain visible, but are not listed in this
10915 variable, will be displayed in random order after all the headers listed in this variable.
10917 @findex gnus-article-hide-boring-headers
10918 @vindex gnus-boring-article-headers
10919 You can hide further boring headers by setting
10920 @code{gnus-treat-hide-boring-headers} to @code{head}. What this function
10921 does depends on the @code{gnus-boring-article-headers} variable. It's a
10922 list, but this list doesn't actually contain header names. Instead it
10923 lists various @dfn{boring conditions} that Gnus can check and remove
10926 These conditions are:
10929 Remove all empty headers.
10931 Remove the @code{Followup-To} header if it is identical to the
10932 @code{Newsgroups} header.
10934 Remove the @code{Reply-To} header if it lists the same addresses as
10935 the @code{From} header, or if the @code{broken-reply-to} group
10938 Remove the @code{Newsgroups} header if it only contains the current group
10941 Remove the @code{To} header if it only contains the address identical to
10942 the current group's @code{to-address} parameter.
10944 Remove the @code{To} header if it only contains the address identical to
10945 the current group's @code{to-list} parameter.
10947 Remove the @code{CC} header if it only contains the address identical to
10948 the current group's @code{to-list} parameter.
10950 Remove the @code{Date} header if the article is less than three days
10953 Remove the @code{To} header if it is very long.
10955 Remove all @code{To} headers if there are more than one.
10958 To include these three elements, you could say something like:
10961 (setq gnus-boring-article-headers
10962 '(empty followup-to reply-to))
10965 This is also the default value for this variable.
10969 @section Using MIME
10970 @cindex @acronym{MIME}
10972 Mime is a standard for waving your hands through the air, aimlessly,
10973 while people stand around yawning.
10975 @acronym{MIME}, however, is a standard for encoding your articles, aimlessly,
10976 while all newsreaders die of fear.
10978 @acronym{MIME} may specify what character set the article uses, the encoding
10979 of the characters, and it also makes it possible to embed pictures and
10980 other naughty stuff in innocent-looking articles.
10982 @vindex gnus-display-mime-function
10983 @findex gnus-display-mime
10984 Gnus pushes @acronym{MIME} articles through @code{gnus-display-mime-function}
10985 to display the @acronym{MIME} parts. This is @code{gnus-display-mime} by
10986 default, which creates a bundle of clickable buttons that can be used to
10987 display, save and manipulate the @acronym{MIME} objects.
10989 The following commands are available when you have placed point over a
10990 @acronym{MIME} button:
10993 @findex gnus-article-press-button
10994 @item RET (Article)
10995 @kindex RET (Article)
10996 @itemx BUTTON-2 (Article)
10997 Toggle displaying of the @acronym{MIME} object
10998 (@code{gnus-article-press-button}). If built-in viewers can not display
10999 the object, Gnus resorts to external viewers in the @file{mailcap}
11000 files. If a viewer has the @samp{copiousoutput} specification, the
11001 object is displayed inline.
11003 @findex gnus-mime-view-part
11004 @item M-RET (Article)
11005 @kindex M-RET (Article)
11007 Prompt for a method, and then view the @acronym{MIME} object using this
11008 method (@code{gnus-mime-view-part}).
11010 @findex gnus-mime-view-part-as-type
11012 @kindex t (Article)
11013 View the @acronym{MIME} object as if it were a different @acronym{MIME} media type
11014 (@code{gnus-mime-view-part-as-type}).
11016 @findex gnus-mime-view-part-as-charset
11018 @kindex C (Article)
11019 Prompt for a charset, and then view the @acronym{MIME} object using this
11020 charset (@code{gnus-mime-view-part-as-charset}).
11022 @findex gnus-mime-save-part
11024 @kindex o (Article)
11025 Prompt for a file name, and then save the @acronym{MIME} object
11026 (@code{gnus-mime-save-part}).
11028 @findex gnus-mime-save-part-and-strip
11029 @item C-o (Article)
11030 @kindex C-o (Article)
11031 Prompt for a file name, then save the @acronym{MIME} object and strip it from
11032 the article. Then proceed to article editing, where a reasonable
11033 suggestion is being made on how the altered article should look
11034 like. The stripped @acronym{MIME} object will be referred via the
11035 message/external-body @acronym{MIME} type.
11036 (@code{gnus-mime-save-part-and-strip}).
11038 @findex gnus-mime-delete-part
11040 @kindex d (Article)
11041 Delete the @acronym{MIME} object from the article and replace it with some
11042 information about the removed @acronym{MIME} object
11043 (@code{gnus-mime-delete-part}).
11045 @findex gnus-mime-copy-part
11047 @kindex c (Article)
11048 Copy the @acronym{MIME} object to a fresh buffer and display this buffer
11049 (@code{gnus-mime-copy-part}). If given a prefix, copy the raw contents
11050 without decoding. If given a numerical prefix, you can do semi-manual
11051 charset stuff (see @code{gnus-summary-show-article-charset-alist} in
11052 @ref{Paging the Article}). Compressed files like @file{.gz} and
11053 @file{.bz2} are automatically decompressed if
11054 @code{auto-compression-mode} is enabled (@pxref{Compressed Files,,
11055 Accessing Compressed Files, emacs, The Emacs Editor}).
11057 @findex gnus-mime-print-part
11059 @kindex p (Article)
11060 Print the @acronym{MIME} object (@code{gnus-mime-print-part}). This
11061 command respects the @samp{print=} specifications in the
11062 @file{.mailcap} file.
11064 @findex gnus-mime-inline-part
11066 @kindex i (Article)
11067 Insert the contents of the @acronym{MIME} object into the buffer
11068 (@code{gnus-mime-inline-part}) as text/plain. If given a prefix, insert
11069 the raw contents without decoding. If given a numerical prefix, you can
11070 do semi-manual charset stuff (see
11071 @code{gnus-summary-show-article-charset-alist} in @ref{Paging the
11072 Article}). Compressed files like @file{.gz} and @file{.bz2} are
11073 automatically decompressed depending on @code{jka-compr} regardless of
11074 @code{auto-compression-mode} (@pxref{Compressed Files,, Accessing
11075 Compressed Files, emacs, The Emacs Editor}).
11077 @findex gnus-mime-view-part-internally
11079 @kindex E (Article)
11080 View the @acronym{MIME} object with an internal viewer. If no internal
11081 viewer is available, use an external viewer
11082 (@code{gnus-mime-view-part-internally}).
11084 @findex gnus-mime-view-part-externally
11086 @kindex e (Article)
11087 View the @acronym{MIME} object with an external viewer.
11088 (@code{gnus-mime-view-part-externally}).
11090 @findex gnus-mime-pipe-part
11092 @kindex | (Article)
11093 Output the @acronym{MIME} object to a process (@code{gnus-mime-pipe-part}).
11095 @findex gnus-mime-action-on-part
11097 @kindex . (Article)
11098 Interactively run an action on the @acronym{MIME} object
11099 (@code{gnus-mime-action-on-part}).
11103 Gnus will display some @acronym{MIME} objects automatically. The way Gnus
11104 determines which parts to do this with is described in the Emacs
11105 @acronym{MIME} manual.
11107 It might be best to just use the toggling functions from the article
11108 buffer to avoid getting nasty surprises. (For instance, you enter the
11109 group @samp{alt.sing-a-long} and, before you know it, @acronym{MIME} has
11110 decoded the sound file in the article and some horrible sing-a-long song
11111 comes screaming out your speakers, and you can't find the volume button,
11112 because there isn't one, and people are starting to look at you, and you
11113 try to stop the program, but you can't, and you can't find the program
11114 to control the volume, and everybody else in the room suddenly decides
11115 to look at you disdainfully, and you'll feel rather stupid.)
11117 Any similarity to real events and people is purely coincidental. Ahem.
11119 Also @pxref{MIME Commands}.
11122 @node Customizing Articles
11123 @section Customizing Articles
11124 @cindex article customization
11126 A slew of functions for customizing how the articles are to look like
11127 exist. You can call these functions interactively
11128 (@pxref{Article Washing}), or you can have them
11129 called automatically when you select the articles.
11131 To have them called automatically, you should set the corresponding
11132 ``treatment'' variable. For instance, to have headers hidden, you'd set
11133 @code{gnus-treat-hide-headers}. Below is a list of variables that can
11134 be set, but first we discuss the values these variables can have.
11136 Note: Some values, while valid, make little sense. Check the list below
11137 for sensible values.
11141 @code{nil}: Don't do this treatment.
11144 @code{t}: Do this treatment on all body parts.
11147 @code{head}: Do the treatment on the headers.
11150 @code{last}: Do this treatment on the last part.
11153 An integer: Do this treatment on all body parts that have a length less
11157 A list of strings: Do this treatment on all body parts that are in
11158 articles that are read in groups that have names that match one of the
11159 regexps in the list.
11162 A list where the first element is not a string:
11164 The list is evaluated recursively. The first element of the list is a
11165 predicate. The following predicates are recognized: @code{or},
11166 @code{and}, @code{not} and @code{typep}. Here's an example:
11170 (typep "text/x-vcard"))
11175 You may have noticed that the word @dfn{part} is used here. This refers
11176 to the fact that some messages are @acronym{MIME} multipart articles that may
11177 be divided into several parts. Articles that are not multiparts are
11178 considered to contain just a single part.
11180 @vindex gnus-article-treat-types
11181 Are the treatments applied to all sorts of multipart parts? Yes, if you
11182 want to, but by default, only @samp{text/plain} parts are given the
11183 treatment. This is controlled by the @code{gnus-article-treat-types}
11184 variable, which is a list of regular expressions that are matched to the
11185 type of the part. This variable is ignored if the value of the
11186 controlling variable is a predicate list, as described above.
11188 The following treatment options are available. The easiest way to
11189 customize this is to examine the @code{gnus-article-treat} customization
11190 group. Values in parenthesis are suggested sensible values. Others are
11191 possible but those listed are probably sufficient for most people.
11194 @item gnus-treat-buttonize (t, integer)
11195 @item gnus-treat-buttonize-head (head)
11197 @xref{Article Buttons}.
11199 @item gnus-treat-capitalize-sentences (t, integer)
11200 @item gnus-treat-overstrike (t, integer)
11201 @item gnus-treat-strip-cr (t, integer)
11202 @item gnus-treat-strip-headers-in-body (t, integer)
11203 @item gnus-treat-strip-leading-blank-lines (t, integer)
11204 @item gnus-treat-strip-multiple-blank-lines (t, integer)
11205 @item gnus-treat-strip-pem (t, last, integer)
11206 @item gnus-treat-strip-trailing-blank-lines (t, last, integer)
11207 @item gnus-treat-unsplit-urls (t, integer)
11208 @item gnus-treat-wash-html (t, integer)
11210 @xref{Article Washing}.
11212 @item gnus-treat-date-english (head)
11213 @item gnus-treat-date-iso8601 (head)
11214 @item gnus-treat-date-lapsed (head)
11215 @item gnus-treat-date-local (head)
11216 @item gnus-treat-date-original (head)
11217 @item gnus-treat-date-user-defined (head)
11218 @item gnus-treat-date-ut (head)
11220 @xref{Article Date}.
11222 @item gnus-treat-from-picon (head)
11223 @item gnus-treat-mail-picon (head)
11224 @item gnus-treat-newsgroups-picon (head)
11228 @item gnus-treat-display-smileys (t, integer)
11230 @item gnus-treat-body-boundary (head)
11232 @vindex gnus-body-boundary-delimiter
11233 Adds a delimiter between header and body, the string used as delimiter
11234 is controlled by @code{gnus-body-boundary-delimiter}.
11238 @item gnus-treat-display-x-face (head)
11242 @item gnus-treat-display-face (head)
11246 @item gnus-treat-emphasize (t, head, integer)
11247 @item gnus-treat-fill-article (t, integer)
11248 @item gnus-treat-fill-long-lines (t, integer)
11249 @item gnus-treat-hide-boring-headers (head)
11250 @item gnus-treat-hide-citation (t, integer)
11251 @item gnus-treat-hide-citation-maybe (t, integer)
11252 @item gnus-treat-hide-headers (head)
11253 @item gnus-treat-hide-signature (t, last)
11254 @item gnus-treat-strip-banner (t, last)
11255 @item gnus-treat-strip-list-identifiers (head)
11257 @xref{Article Hiding}.
11259 @item gnus-treat-highlight-citation (t, integer)
11260 @item gnus-treat-highlight-headers (head)
11261 @item gnus-treat-highlight-signature (t, last, integer)
11263 @xref{Article Highlighting}.
11265 @item gnus-treat-play-sounds
11266 @item gnus-treat-translate
11267 @item gnus-treat-ansi-sequences (t)
11268 @item gnus-treat-x-pgp-sig (head)
11270 @item gnus-treat-unfold-headers (head)
11271 @item gnus-treat-fold-headers (head)
11272 @item gnus-treat-fold-newsgroups (head)
11273 @item gnus-treat-leading-whitespace (head)
11275 @xref{Article Header}.
11280 @vindex gnus-part-display-hook
11281 You can, of course, write your own functions to be called from
11282 @code{gnus-part-display-hook}. The functions are called narrowed to the
11283 part, and you can do anything you like, pretty much. There is no
11284 information that you have to keep in the buffer---you can change
11288 @node Article Keymap
11289 @section Article Keymap
11291 Most of the keystrokes in the summary buffer can also be used in the
11292 article buffer. They should behave as if you typed them in the summary
11293 buffer, which means that you don't actually have to have a summary
11294 buffer displayed while reading. You can do it all from the article
11297 A few additional keystrokes are available:
11302 @kindex SPACE (Article)
11303 @findex gnus-article-next-page
11304 Scroll forwards one page (@code{gnus-article-next-page}).
11305 This is exactly the same as @kbd{h SPACE h}.
11308 @kindex DEL (Article)
11309 @findex gnus-article-prev-page
11310 Scroll backwards one page (@code{gnus-article-prev-page}).
11311 This is exactly the same as @kbd{h DEL h}.
11314 @kindex C-c ^ (Article)
11315 @findex gnus-article-refer-article
11316 If point is in the neighborhood of a @code{Message-ID} and you press
11317 @kbd{C-c ^}, Gnus will try to get that article from the server
11318 (@code{gnus-article-refer-article}).
11321 @kindex C-c C-m (Article)
11322 @findex gnus-article-mail
11323 Send a reply to the address near point (@code{gnus-article-mail}). If
11324 given a prefix, include the mail.
11327 @kindex s (Article)
11328 @findex gnus-article-show-summary
11329 Reconfigure the buffers so that the summary buffer becomes visible
11330 (@code{gnus-article-show-summary}).
11333 @kindex ? (Article)
11334 @findex gnus-article-describe-briefly
11335 Give a very brief description of the available keystrokes
11336 (@code{gnus-article-describe-briefly}).
11339 @kindex TAB (Article)
11340 @findex gnus-article-next-button
11341 Go to the next button, if any (@code{gnus-article-next-button}). This
11342 only makes sense if you have buttonizing turned on.
11345 @kindex M-TAB (Article)
11346 @findex gnus-article-prev-button
11347 Go to the previous button, if any (@code{gnus-article-prev-button}).
11350 @kindex R (Article)
11351 @findex gnus-article-reply-with-original
11352 Send a reply to the current article and yank the current article
11353 (@code{gnus-article-reply-with-original}). If given a prefix, make a
11354 wide reply. If the region is active, only yank the text in the
11358 @kindex F (Article)
11359 @findex gnus-article-followup-with-original
11360 Send a followup to the current article and yank the current article
11361 (@code{gnus-article-followup-with-original}). If given a prefix, make
11362 a wide reply. If the region is active, only yank the text in the
11370 @section Misc Article
11374 @item gnus-single-article-buffer
11375 @vindex gnus-single-article-buffer
11376 If non-@code{nil}, use the same article buffer for all the groups.
11377 (This is the default.) If @code{nil}, each group will have its own
11380 @vindex gnus-article-decode-hook
11381 @item gnus-article-decode-hook
11382 @cindex @acronym{MIME}
11383 Hook used to decode @acronym{MIME} articles. The default value is
11384 @code{(article-decode-charset article-decode-encoded-words)}
11386 @vindex gnus-article-prepare-hook
11387 @item gnus-article-prepare-hook
11388 This hook is called right after the article has been inserted into the
11389 article buffer. It is mainly intended for functions that do something
11390 depending on the contents; it should probably not be used for changing
11391 the contents of the article buffer.
11393 @item gnus-article-mode-hook
11394 @vindex gnus-article-mode-hook
11395 Hook called in article mode buffers.
11397 @item gnus-article-mode-syntax-table
11398 @vindex gnus-article-mode-syntax-table
11399 Syntax table used in article buffers. It is initialized from
11400 @code{text-mode-syntax-table}.
11402 @vindex gnus-article-over-scroll
11403 @item gnus-article-over-scroll
11404 If non-@code{nil}, allow scrolling the article buffer even when there
11405 no more new text to scroll in. The default is @code{nil}.
11407 @vindex gnus-article-mode-line-format
11408 @item gnus-article-mode-line-format
11409 This variable is a format string along the same lines as
11410 @code{gnus-summary-mode-line-format} (@pxref{Summary Buffer Mode
11411 Line}). It accepts the same format specifications as that variable,
11412 with two extensions:
11417 The @dfn{wash status} of the article. This is a short string with one
11418 character for each possible article wash operation that may have been
11419 performed. The characters and their meaning:
11424 Displayed when cited text may be hidden in the article buffer.
11427 Displayed when headers are hidden in the article buffer.
11430 Displayed when article is digitally signed or encrypted, and Gnus has
11431 hidden the security headers. (N.B. does not tell anything about
11432 security status, i.e. good or bad signature.)
11435 Displayed when the signature has been hidden in the Article buffer.
11438 Displayed when Gnus has treated overstrike characters in the article buffer.
11441 Displayed when Gnus has treated emphasised strings in the article buffer.
11446 The number of @acronym{MIME} parts in the article.
11450 @vindex gnus-break-pages
11452 @item gnus-break-pages
11453 Controls whether @dfn{page breaking} is to take place. If this variable
11454 is non-@code{nil}, the articles will be divided into pages whenever a
11455 page delimiter appears in the article. If this variable is @code{nil},
11456 paging will not be done.
11458 @item gnus-page-delimiter
11459 @vindex gnus-page-delimiter
11460 This is the delimiter mentioned above. By default, it is @samp{^L}
11464 @cindex internationalized domain names
11465 @vindex gnus-use-idna
11466 @item gnus-use-idna
11467 This variable controls whether Gnus performs IDNA decoding of
11468 internationalized domain names inside @samp{From}, @samp{To} and
11469 @samp{Cc} headers. @xref{IDNA, ,IDNA,message, The Message Manual},
11470 for how to compose such messages. This requires
11471 @uref{http://www.gnu.org/software/libidn/, GNU Libidn}, and this
11472 variable is only enabled if you have installed it.
11477 @node Composing Messages
11478 @chapter Composing Messages
11479 @cindex composing messages
11482 @cindex sending mail
11487 @cindex using s/mime
11488 @cindex using smime
11490 @kindex C-c C-c (Post)
11491 All commands for posting and mailing will put you in a message buffer
11492 where you can edit the article all you like, before you send the
11493 article by pressing @kbd{C-c C-c}. @xref{Top, , Overview, message,
11494 Message Manual}. Where the message will be posted/mailed to depends
11495 on your setup (@pxref{Posting Server}).
11498 * Mail:: Mailing and replying.
11499 * Posting Server:: What server should you post and mail via?
11500 * POP before SMTP:: You cannot send a mail unless you read a mail.
11501 * Mail and Post:: Mailing and posting at the same time.
11502 * Archived Messages:: Where Gnus stores the messages you've sent.
11503 * Posting Styles:: An easier way to specify who you are.
11504 * Drafts:: Postponing messages and rejected messages.
11505 * Rejected Articles:: What happens if the server doesn't like your article?
11506 * Signing and encrypting:: How to compose secure messages.
11509 Also @pxref{Canceling and Superseding} for information on how to
11510 remove articles you shouldn't have posted.
11516 Variables for customizing outgoing mail:
11519 @item gnus-uu-digest-headers
11520 @vindex gnus-uu-digest-headers
11521 List of regexps to match headers included in digested messages. The
11522 headers will be included in the sequence they are matched. If
11523 @code{nil} include all headers.
11525 @item gnus-add-to-list
11526 @vindex gnus-add-to-list
11527 If non-@code{nil}, add a @code{to-list} group parameter to mail groups
11528 that have none when you do a @kbd{a}.
11530 @item gnus-confirm-mail-reply-to-news
11531 @vindex gnus-confirm-mail-reply-to-news
11532 This can also be a function receiving the group name as the only
11533 parameter which should return non-@code{nil} if a confirmation is
11534 needed, or a regular expression matching group names, where
11535 confirmation is should be asked for.
11537 If you find yourself never wanting to reply to mail, but occasionally
11538 press R anyway, this variable might be for you.
11540 @item gnus-confirm-treat-mail-like-news
11541 @vindex gnus-confirm-treat-mail-like-news
11542 If non-@code{nil}, Gnus also requests confirmation according to
11543 @code{gnus-confirm-mail-reply-to-news} when replying to mail. This is
11544 useful for treating mailing lists like newsgroups.
11549 @node Posting Server
11550 @section Posting Server
11552 When you press those magical @kbd{C-c C-c} keys to ship off your latest
11553 (extremely intelligent, of course) article, where does it go?
11555 Thank you for asking. I hate you.
11557 It can be quite complicated.
11559 @vindex gnus-post-method
11560 When posting news, Message usually invokes @code{message-send-news}
11561 (@pxref{News Variables, , News Variables, message, Message Manual}).
11562 Normally, Gnus will post using the same select method as you're
11563 reading from (which might be convenient if you're reading lots of
11564 groups from different private servers). However. If the server
11565 you're reading from doesn't allow posting, just reading, you probably
11566 want to use some other server to post your (extremely intelligent and
11567 fabulously interesting) articles. You can then set the
11568 @code{gnus-post-method} to some other method:
11571 (setq gnus-post-method '(nnspool ""))
11574 Now, if you've done this, and then this server rejects your article, or
11575 this server is down, what do you do then? To override this variable you
11576 can use a non-zero prefix to the @kbd{C-c C-c} command to force using
11577 the ``current'' server, to get back the default behavior, for posting.
11579 If you give a zero prefix (i.e., @kbd{C-u 0 C-c C-c}) to that command,
11580 Gnus will prompt you for what method to use for posting.
11582 You can also set @code{gnus-post-method} to a list of select methods.
11583 If that's the case, Gnus will always prompt you for what method to use
11586 Finally, if you want to always post using the native select method,
11587 you can set this variable to @code{native}.
11589 When sending mail, Message invokes @code{message-send-mail-function}.
11590 The default function, @code{message-send-mail-with-sendmail}, pipes
11591 your article to the @code{sendmail} binary for further queuing and
11592 sending. When your local system is not configured for sending mail
11593 using @code{sendmail}, and you have access to a remote @acronym{SMTP}
11594 server, you can set @code{message-send-mail-function} to
11595 @code{smtpmail-send-it} and make sure to setup the @code{smtpmail}
11596 package correctly. An example:
11599 (setq message-send-mail-function 'smtpmail-send-it
11600 smtpmail-default-smtp-server "YOUR SMTP HOST")
11603 To the thing similar to this, there is
11604 @code{message-smtpmail-send-it}. It is useful if your @acronym{ISP}
11605 requires the @acronym{POP}-before-@acronym{SMTP} authentication.
11606 @xref{POP before SMTP}.
11608 Other possible choices for @code{message-send-mail-function} includes
11609 @code{message-send-mail-with-mh}, @code{message-send-mail-with-qmail},
11610 and @code{feedmail-send-it}.
11612 @node POP before SMTP
11613 @section POP before SMTP
11614 @cindex pop before smtp
11615 @findex message-smtpmail-send-it
11616 @findex mail-source-touch-pop
11618 Does your @acronym{ISP} require the @acronym{POP}-before-@acronym{SMTP}
11619 authentication? It is whether you need to connect to the @acronym{POP}
11620 mail server within a certain time before sending mails. If so, there is
11621 a convenient way. To do that, put the following lines in your
11622 @file{~/.gnus.el} file:
11625 (setq message-send-mail-function 'message-smtpmail-send-it)
11626 (add-hook 'message-send-mail-hook 'mail-source-touch-pop)
11630 It means to let Gnus connect to the @acronym{POP} mail server in advance
11631 whenever you send a mail. The @code{mail-source-touch-pop} function
11632 does only a @acronym{POP} authentication according to the value of
11633 @code{mail-sources} without fetching mails, just before sending a mail.
11634 Note that you have to use @code{message-smtpmail-send-it} which runs
11635 @code{message-send-mail-hook} rather than @code{smtpmail-send-it} and
11636 set the value of @code{mail-sources} for a @acronym{POP} connection
11637 correctly. @xref{Mail Sources}.
11639 If you have two or more @acronym{POP} mail servers set in
11640 @code{mail-sources}, you may want to specify one of them to
11641 @code{mail-source-primary-source} as the @acronym{POP} mail server to be
11642 used for the @acronym{POP}-before-@acronym{SMTP} authentication. If it
11643 is your primary @acronym{POP} mail server (i.e., you are fetching mails
11644 mainly from that server), you can set it permanently as follows:
11647 (setq mail-source-primary-source
11648 '(pop :server "pop3.mail.server"
11649 :password "secret"))
11653 Otherwise, bind it dynamically only when performing the
11654 @acronym{POP}-before-@acronym{SMTP} authentication as follows:
11657 (add-hook 'message-send-mail-hook
11659 (let ((mail-source-primary-source
11660 '(pop :server "pop3.mail.server"
11661 :password "secret")))
11662 (mail-source-touch-pop))))
11665 @node Mail and Post
11666 @section Mail and Post
11668 Here's a list of variables relevant to both mailing and
11672 @item gnus-mailing-list-groups
11673 @findex gnus-mailing-list-groups
11674 @cindex mailing lists
11676 If your news server offers groups that are really mailing lists
11677 gatewayed to the @acronym{NNTP} server, you can read those groups without
11678 problems, but you can't post/followup to them without some difficulty.
11679 One solution is to add a @code{to-address} to the group parameters
11680 (@pxref{Group Parameters}). An easier thing to do is set the
11681 @code{gnus-mailing-list-groups} to a regexp that matches the groups that
11682 really are mailing lists. Then, at least, followups to the mailing
11683 lists will work most of the time. Posting to these groups (@kbd{a}) is
11684 still a pain, though.
11686 @item gnus-user-agent
11687 @vindex gnus-user-agent
11690 This variable controls which information should be exposed in the
11691 User-Agent header. It can be one of the symbols @code{gnus} (show only
11692 Gnus version), @code{emacs-gnus} (show only Emacs and Gnus versions),
11693 @code{emacs-gnus-config} (same as @code{emacs-gnus} plus system
11694 configuration), @code{emacs-gnus-type} (same as @code{emacs-gnus} plus
11695 system type) or a custom string. If you set it to a string, be sure to
11696 use a valid format, see RFC 2616.
11700 You may want to do spell-checking on messages that you send out. Or, if
11701 you don't want to spell-check by hand, you could add automatic
11702 spell-checking via the @code{ispell} package:
11705 @findex ispell-message
11707 (add-hook 'message-send-hook 'ispell-message)
11710 If you want to change the @code{ispell} dictionary based on what group
11711 you're in, you could say something like the following:
11714 (add-hook 'gnus-select-group-hook
11718 "^de\\." (gnus-group-real-name gnus-newsgroup-name))
11719 (ispell-change-dictionary "deutsch"))
11721 (ispell-change-dictionary "english")))))
11724 Modify to suit your needs.
11727 @node Archived Messages
11728 @section Archived Messages
11729 @cindex archived messages
11730 @cindex sent messages
11732 Gnus provides a few different methods for storing the mail and news you
11733 send. The default method is to use the @dfn{archive virtual server} to
11734 store the messages. If you want to disable this completely, the
11735 @code{gnus-message-archive-group} variable should be @code{nil}, which
11738 For archiving interesting messages in a group you read, see the
11739 @kbd{B c} (@code{gnus-summary-copy-article}) command (@pxref{Mail
11742 @vindex gnus-message-archive-method
11743 @code{gnus-message-archive-method} says what virtual server Gnus is to
11744 use to store sent messages. The default is:
11747 (nnfolder "archive"
11748 (nnfolder-directory "~/Mail/archive")
11749 (nnfolder-active-file "~/Mail/archive/active")
11750 (nnfolder-get-new-mail nil)
11751 (nnfolder-inhibit-expiry t))
11754 You can, however, use any mail select method (@code{nnml},
11755 @code{nnmbox}, etc.). @code{nnfolder} is a quite likable select method
11756 for doing this sort of thing, though. If you don't like the default
11757 directory chosen, you could say something like:
11760 (setq gnus-message-archive-method
11761 '(nnfolder "archive"
11762 (nnfolder-inhibit-expiry t)
11763 (nnfolder-active-file "~/News/sent-mail/active")
11764 (nnfolder-directory "~/News/sent-mail/")))
11767 @vindex gnus-message-archive-group
11769 Gnus will insert @code{Gcc} headers in all outgoing messages that point
11770 to one or more group(s) on that server. Which group to use is
11771 determined by the @code{gnus-message-archive-group} variable.
11773 This variable can be used to do the following:
11777 Messages will be saved in that group.
11779 Note that you can include a select method in the group name, then the
11780 message will not be stored in the select method given by
11781 @code{gnus-message-archive-method}, but in the select method specified
11782 by the group name, instead. Suppose @code{gnus-message-archive-method}
11783 has the default value shown above. Then setting
11784 @code{gnus-message-archive-group} to @code{"foo"} means that outgoing
11785 messages are stored in @samp{nnfolder+archive:foo}, but if you use the
11786 value @code{"nnml:foo"}, then outgoing messages will be stored in
11789 @item a list of strings
11790 Messages will be saved in all those groups.
11792 @item an alist of regexps, functions and forms
11793 When a key ``matches'', the result is used.
11796 No message archiving will take place. This is the default.
11801 Just saving to a single group called @samp{MisK}:
11803 (setq gnus-message-archive-group "MisK")
11806 Saving to two groups, @samp{MisK} and @samp{safe}:
11808 (setq gnus-message-archive-group '("MisK" "safe"))
11811 Save to different groups based on what group you are in:
11813 (setq gnus-message-archive-group
11814 '(("^alt" "sent-to-alt")
11815 ("mail" "sent-to-mail")
11816 (".*" "sent-to-misc")))
11819 More complex stuff:
11821 (setq gnus-message-archive-group
11822 '((if (message-news-p)
11827 How about storing all news messages in one file, but storing all mail
11828 messages in one file per month:
11831 (setq gnus-message-archive-group
11832 '((if (message-news-p)
11834 (concat "mail." (format-time-string "%Y-%m")))))
11837 @c (XEmacs 19.13 doesn't have @code{format-time-string}, so you'll have to
11838 @c use a different value for @code{gnus-message-archive-group} there.)
11840 Now, when you send a message off, it will be stored in the appropriate
11841 group. (If you want to disable storing for just one particular message,
11842 you can just remove the @code{Gcc} header that has been inserted.) The
11843 archive group will appear in the group buffer the next time you start
11844 Gnus, or the next time you press @kbd{F} in the group buffer. You can
11845 enter it and read the articles in it just like you'd read any other
11846 group. If the group gets really big and annoying, you can simply rename
11847 if (using @kbd{G r} in the group buffer) to something
11848 nice---@samp{misc-mail-september-1995}, or whatever. New messages will
11849 continue to be stored in the old (now empty) group.
11851 That's the default method of archiving sent messages. Gnus offers a
11852 different way for the people who don't like the default method. In that
11853 case you should set @code{gnus-message-archive-group} to @code{nil};
11854 this will disable archiving.
11857 @item gnus-outgoing-message-group
11858 @vindex gnus-outgoing-message-group
11859 All outgoing messages will be put in this group. If you want to store
11860 all your outgoing mail and articles in the group @samp{nnml:archive},
11861 you set this variable to that value. This variable can also be a list of
11864 If you want to have greater control over what group to put each
11865 message in, you can set this variable to a function that checks the
11866 current newsgroup name and then returns a suitable group name (or list
11869 This variable can be used instead of @code{gnus-message-archive-group},
11870 but the latter is the preferred method.
11872 @item gnus-gcc-mark-as-read
11873 @vindex gnus-gcc-mark-as-read
11874 If non-@code{nil}, automatically mark @code{Gcc} articles as read.
11876 @item gnus-gcc-externalize-attachments
11877 @vindex gnus-gcc-externalize-attachments
11878 If @code{nil}, attach files as normal parts in Gcc copies; if a regexp
11879 and matches the Gcc group name, attach files as external parts; if it is
11880 @code{all}, attach local files as external parts; if it is other
11881 non-@code{nil}, the behavior is the same as @code{all}, but it may be
11882 changed in the future.
11887 @node Posting Styles
11888 @section Posting Styles
11889 @cindex posting styles
11892 All them variables, they make my head swim.
11894 So what if you want a different @code{Organization} and signature based
11895 on what groups you post to? And you post both from your home machine
11896 and your work machine, and you want different @code{From} lines, and so
11899 @vindex gnus-posting-styles
11900 One way to do stuff like that is to write clever hooks that change the
11901 variables you need to have changed. That's a bit boring, so somebody
11902 came up with the bright idea of letting the user specify these things in
11903 a handy alist. Here's an example of a @code{gnus-posting-styles}
11908 (signature "Peace and happiness")
11909 (organization "What me?"))
11911 (signature "Death to everybody"))
11912 ("comp.emacs.i-love-it"
11913 (organization "Emacs is it")))
11916 As you might surmise from this example, this alist consists of several
11917 @dfn{styles}. Each style will be applicable if the first element
11918 ``matches'', in some form or other. The entire alist will be iterated
11919 over, from the beginning towards the end, and each match will be
11920 applied, which means that attributes in later styles that match override
11921 the same attributes in earlier matching styles. So
11922 @samp{comp.programming.literate} will have the @samp{Death to everybody}
11923 signature and the @samp{What me?} @code{Organization} header.
11925 The first element in each style is called the @code{match}. If it's a
11926 string, then Gnus will try to regexp match it against the group name.
11927 If it is the form @code{(header @var{match} @var{regexp})}, then Gnus
11928 will look in the original article for a header whose name is
11929 @var{match} and compare that @var{regexp}. @var{match} and
11930 @var{regexp} are strings. (The original article is the one you are
11931 replying or following up to. If you are not composing a reply or a
11932 followup, then there is nothing to match against.) If the
11933 @code{match} is a function symbol, that function will be called with
11934 no arguments. If it's a variable symbol, then the variable will be
11935 referenced. If it's a list, then that list will be @code{eval}ed. In
11936 any case, if this returns a non-@code{nil} value, then the style is
11937 said to @dfn{match}.
11939 Each style may contain an arbitrary amount of @dfn{attributes}. Each
11940 attribute consists of a @code{(@var{name} @var{value})} pair. In
11941 addition, you can also use the @code{(@var{name} :file @var{value})}
11942 form or the @code{(@var{name} :value @var{value})} form. Where
11943 @code{:file} signifies @var{value} represents a file name and its
11944 contents should be used as the attribute value, @code{:value} signifies
11945 @var{value} does not represent a file name explicitly. The attribute
11946 name can be one of:
11949 @item @code{signature}
11950 @item @code{signature-file}
11951 @item @code{x-face-file}
11952 @item @code{address}, overriding @code{user-mail-address}
11953 @item @code{name}, overriding @code{(user-full-name)}
11957 The attribute name can also be a string or a symbol. In that case,
11958 this will be used as a header name, and the value will be inserted in
11959 the headers of the article; if the value is @code{nil}, the header
11960 name will be removed. If the attribute name is @code{eval}, the form
11961 is evaluated, and the result is thrown away.
11963 The attribute value can be a string (used verbatim), a function with
11964 zero arguments (the return value will be used), a variable (its value
11965 will be used) or a list (it will be @code{eval}ed and the return value
11966 will be used). The functions and sexps are called/@code{eval}ed in the
11967 message buffer that is being set up. The headers of the current article
11968 are available through the @code{message-reply-headers} variable, which
11969 is a vector of the following headers: number subject from date id
11970 references chars lines xref extra.
11972 @vindex message-reply-headers
11974 If you wish to check whether the message you are about to compose is
11975 meant to be a news article or a mail message, you can check the values
11976 of the @code{message-news-p} and @code{message-mail-p} functions.
11978 @findex message-mail-p
11979 @findex message-news-p
11981 So here's a new example:
11984 (setq gnus-posting-styles
11986 (signature-file "~/.signature")
11988 ("X-Home-Page" (getenv "WWW_HOME"))
11989 (organization "People's Front Against MWM"))
11991 (signature my-funny-signature-randomizer))
11992 ((equal (system-name) "gnarly") ;; @r{A form}
11993 (signature my-quote-randomizer))
11994 (message-news-p ;; @r{A function symbol}
11995 (signature my-news-signature))
11996 (window-system ;; @r{A value symbol}
11997 ("X-Window-System" (format "%s" window-system)))
11998 ;; @r{If I'm replying to Larsi, set the Organization header.}
11999 ((header "from" "larsi.*org")
12000 (Organization "Somewhere, Inc."))
12001 ((posting-from-work-p) ;; @r{A user defined function}
12002 (signature-file "~/.work-signature")
12003 (address "user@@bar.foo")
12004 (body "You are fired.\n\nSincerely, your boss.")
12005 (organization "Important Work, Inc"))
12007 (From (save-excursion
12008 (set-buffer gnus-article-buffer)
12009 (message-fetch-field "to"))))
12011 (signature-file "~/.mail-signature"))))
12014 The @samp{nnml:.*} rule means that you use the @code{To} address as the
12015 @code{From} address in all your outgoing replies, which might be handy
12016 if you fill many roles.
12023 If you are writing a message (mail or news) and suddenly remember that
12024 you have a steak in the oven (or some pesto in the food processor, you
12025 craaazy vegetarians), you'll probably wish there was a method to save
12026 the message you are writing so that you can continue editing it some
12027 other day, and send it when you feel its finished.
12029 Well, don't worry about it. Whenever you start composing a message of
12030 some sort using the Gnus mail and post commands, the buffer you get will
12031 automatically associate to an article in a special @dfn{draft} group.
12032 If you save the buffer the normal way (@kbd{C-x C-s}, for instance), the
12033 article will be saved there. (Auto-save files also go to the draft
12037 @vindex nndraft-directory
12038 The draft group is a special group (which is implemented as an
12039 @code{nndraft} group, if you absolutely have to know) called
12040 @samp{nndraft:drafts}. The variable @code{nndraft-directory} says where
12041 @code{nndraft} is to store its files. What makes this group special is
12042 that you can't tick any articles in it or mark any articles as
12043 read---all articles in the group are permanently unread.
12045 If the group doesn't exist, it will be created and you'll be subscribed
12046 to it. The only way to make it disappear from the Group buffer is to
12047 unsubscribe it. The special properties of the draft group comes from
12048 a group property (@pxref{Group Parameters}), and if lost the group
12049 behaves like any other group. This means the commands below will not
12050 be available. To restore the special properties of the group, the
12051 simplest way is to kill the group, using @kbd{C-k}, and restart
12052 Gnus. The group is automatically created again with the
12053 correct parameters. The content of the group is not lost.
12055 @c @findex gnus-dissociate-buffer-from-draft
12056 @c @kindex C-c M-d (Mail)
12057 @c @kindex C-c M-d (Post)
12058 @c @findex gnus-associate-buffer-with-draft
12059 @c @kindex C-c C-d (Mail)
12060 @c @kindex C-c C-d (Post)
12061 @c If you're writing some super-secret message that you later want to
12062 @c encode with PGP before sending, you may wish to turn the auto-saving
12063 @c (and association with the draft group) off. You never know who might be
12064 @c interested in reading all your extremely valuable and terribly horrible
12065 @c and interesting secrets. The @kbd{C-c M-d}
12066 @c (@code{gnus-dissociate-buffer-from-draft}) command does that for you.
12067 @c If you change your mind and want to turn the auto-saving back on again,
12068 @c @kbd{C-c C-d} (@code{gnus-associate-buffer-with-draft} does that.
12070 @c @vindex gnus-use-draft
12071 @c To leave association with the draft group off by default, set
12072 @c @code{gnus-use-draft} to @code{nil}. It is @code{t} by default.
12074 @findex gnus-draft-edit-message
12075 @kindex D e (Draft)
12076 When you want to continue editing the article, you simply enter the
12077 draft group and push @kbd{D e} (@code{gnus-draft-edit-message}) to do
12078 that. You will be placed in a buffer where you left off.
12080 Rejected articles will also be put in this draft group (@pxref{Rejected
12083 @findex gnus-draft-send-all-messages
12084 @kindex D s (Draft)
12085 @findex gnus-draft-send-message
12086 @kindex D S (Draft)
12087 If you have lots of rejected messages you want to post (or mail) without
12088 doing further editing, you can use the @kbd{D s} command
12089 (@code{gnus-draft-send-message}). This command understands the
12090 process/prefix convention (@pxref{Process/Prefix}). The @kbd{D S}
12091 command (@code{gnus-draft-send-all-messages}) will ship off all messages
12094 @findex gnus-draft-toggle-sending
12095 @kindex D t (Draft)
12096 If you have some messages that you wish not to send, you can use the
12097 @kbd{D t} (@code{gnus-draft-toggle-sending}) command to mark the message
12098 as unsendable. This is a toggling command.
12101 @node Rejected Articles
12102 @section Rejected Articles
12103 @cindex rejected articles
12105 Sometimes a news server will reject an article. Perhaps the server
12106 doesn't like your face. Perhaps it just feels miserable. Perhaps
12107 @emph{there be demons}. Perhaps you have included too much cited text.
12108 Perhaps the disk is full. Perhaps the server is down.
12110 These situations are, of course, totally beyond the control of Gnus.
12111 (Gnus, of course, loves the way you look, always feels great, has angels
12112 fluttering around inside of it, doesn't care about how much cited text
12113 you include, never runs full and never goes down.) So Gnus saves these
12114 articles until some later time when the server feels better.
12116 The rejected articles will automatically be put in a special draft group
12117 (@pxref{Drafts}). When the server comes back up again, you'd then
12118 typically enter that group and send all the articles off.
12120 @node Signing and encrypting
12121 @section Signing and encrypting
12123 @cindex using s/mime
12124 @cindex using smime
12126 Gnus can digitally sign and encrypt your messages, using vanilla
12127 @acronym{PGP} format or @acronym{PGP/MIME} or @acronym{S/MIME}. For
12128 decoding such messages, see the @code{mm-verify-option} and
12129 @code{mm-decrypt-option} options (@pxref{Security}).
12131 @vindex gnus-message-replysign
12132 @vindex gnus-message-replyencrypt
12133 @vindex gnus-message-replysignencrypted
12134 Often, you would like to sign replies to people who send you signed
12135 messages. Even more often, you might want to encrypt messages which
12136 are in reply to encrypted messages. Gnus offers
12137 @code{gnus-message-replysign} to enable the former, and
12138 @code{gnus-message-replyencrypt} for the latter. In addition, setting
12139 @code{gnus-message-replysignencrypted} (on by default) will sign
12140 automatically encrypted messages.
12142 Instructing @acronym{MML} to perform security operations on a
12143 @acronym{MIME} part is done using the @kbd{C-c C-m s} key map for
12144 signing and the @kbd{C-c C-m c} key map for encryption, as follows.
12149 @kindex C-c C-m s s (Message)
12150 @findex mml-secure-message-sign-smime
12152 Digitally sign current message using @acronym{S/MIME}.
12155 @kindex C-c C-m s o (Message)
12156 @findex mml-secure-message-sign-pgp
12158 Digitally sign current message using @acronym{PGP}.
12161 @kindex C-c C-m s p (Message)
12162 @findex mml-secure-message-sign-pgp
12164 Digitally sign current message using @acronym{PGP/MIME}.
12167 @kindex C-c C-m c s (Message)
12168 @findex mml-secure-message-encrypt-smime
12170 Digitally encrypt current message using @acronym{S/MIME}.
12173 @kindex C-c C-m c o (Message)
12174 @findex mml-secure-message-encrypt-pgp
12176 Digitally encrypt current message using @acronym{PGP}.
12179 @kindex C-c C-m c p (Message)
12180 @findex mml-secure-message-encrypt-pgpmime
12182 Digitally encrypt current message using @acronym{PGP/MIME}.
12185 @kindex C-c C-m C-n (Message)
12186 @findex mml-unsecure-message
12187 Remove security related @acronym{MML} tags from message.
12191 @xref{Security, ,Security, message, Message Manual}, for more information.
12193 @node Select Methods
12194 @chapter Select Methods
12195 @cindex foreign groups
12196 @cindex select methods
12198 A @dfn{foreign group} is a group not read by the usual (or
12199 default) means. It could be, for instance, a group from a different
12200 @acronym{NNTP} server, it could be a virtual group, or it could be your own
12201 personal mail group.
12203 A foreign group (or any group, really) is specified by a @dfn{name} and
12204 a @dfn{select method}. To take the latter first, a select method is a
12205 list where the first element says what back end to use (e.g. @code{nntp},
12206 @code{nnspool}, @code{nnml}) and the second element is the @dfn{server
12207 name}. There may be additional elements in the select method, where the
12208 value may have special meaning for the back end in question.
12210 One could say that a select method defines a @dfn{virtual server}---so
12211 we do just that (@pxref{Server Buffer}).
12213 The @dfn{name} of the group is the name the back end will recognize the
12216 For instance, the group @samp{soc.motss} on the @acronym{NNTP} server
12217 @samp{some.where.edu} will have the name @samp{soc.motss} and select
12218 method @code{(nntp "some.where.edu")}. Gnus will call this group
12219 @samp{nntp+some.where.edu:soc.motss}, even though the @code{nntp}
12220 back end just knows this group as @samp{soc.motss}.
12222 The different methods all have their peculiarities, of course.
12225 * Server Buffer:: Making and editing virtual servers.
12226 * Getting News:: Reading USENET news with Gnus.
12227 * Getting Mail:: Reading your personal mail with Gnus.
12228 * Browsing the Web:: Getting messages from a plethora of Web sources.
12229 * IMAP:: Using Gnus as a @acronym{IMAP} client.
12230 * Other Sources:: Reading directories, files, SOUP packets.
12231 * Combined Groups:: Combining groups into one group.
12232 * Email Based Diary:: Using mails to manage diary events in Gnus.
12233 * Gnus Unplugged:: Reading news and mail offline.
12237 @node Server Buffer
12238 @section Server Buffer
12240 Traditionally, a @dfn{server} is a machine or a piece of software that
12241 one connects to, and then requests information from. Gnus does not
12242 connect directly to any real servers, but does all transactions through
12243 one back end or other. But that's just putting one layer more between
12244 the actual media and Gnus, so we might just as well say that each
12245 back end represents a virtual server.
12247 For instance, the @code{nntp} back end may be used to connect to several
12248 different actual @acronym{NNTP} servers, or, perhaps, to many different ports
12249 on the same actual @acronym{NNTP} server. You tell Gnus which back end to
12250 use, and what parameters to set by specifying a @dfn{select method}.
12252 These select method specifications can sometimes become quite
12253 complicated---say, for instance, that you want to read from the
12254 @acronym{NNTP} server @samp{news.funet.fi} on port number 13, which
12255 hangs if queried for @acronym{NOV} headers and has a buggy select. Ahem.
12256 Anyway, if you had to specify that for each group that used this
12257 server, that would be too much work, so Gnus offers a way of naming
12258 select methods, which is what you do in the server buffer.
12260 To enter the server buffer, use the @kbd{^}
12261 (@code{gnus-group-enter-server-mode}) command in the group buffer.
12264 * Server Buffer Format:: You can customize the look of this buffer.
12265 * Server Commands:: Commands to manipulate servers.
12266 * Example Methods:: Examples server specifications.
12267 * Creating a Virtual Server:: An example session.
12268 * Server Variables:: Which variables to set.
12269 * Servers and Methods:: You can use server names as select methods.
12270 * Unavailable Servers:: Some servers you try to contact may be down.
12273 @vindex gnus-server-mode-hook
12274 @code{gnus-server-mode-hook} is run when creating the server buffer.
12277 @node Server Buffer Format
12278 @subsection Server Buffer Format
12279 @cindex server buffer format
12281 @vindex gnus-server-line-format
12282 You can change the look of the server buffer lines by changing the
12283 @code{gnus-server-line-format} variable. This is a @code{format}-like
12284 variable, with some simple extensions:
12289 How the news is fetched---the back end name.
12292 The name of this server.
12295 Where the news is to be fetched from---the address.
12298 The opened/closed/denied status of the server.
12301 @vindex gnus-server-mode-line-format
12302 The mode line can also be customized by using the
12303 @code{gnus-server-mode-line-format} variable (@pxref{Mode Line
12304 Formatting}). The following specs are understood:
12314 Also @pxref{Formatting Variables}.
12317 @node Server Commands
12318 @subsection Server Commands
12319 @cindex server commands
12325 @findex gnus-server-add-server
12326 Add a new server (@code{gnus-server-add-server}).
12330 @findex gnus-server-edit-server
12331 Edit a server (@code{gnus-server-edit-server}).
12334 @kindex SPACE (Server)
12335 @findex gnus-server-read-server
12336 Browse the current server (@code{gnus-server-read-server}).
12340 @findex gnus-server-exit
12341 Return to the group buffer (@code{gnus-server-exit}).
12345 @findex gnus-server-kill-server
12346 Kill the current server (@code{gnus-server-kill-server}).
12350 @findex gnus-server-yank-server
12351 Yank the previously killed server (@code{gnus-server-yank-server}).
12355 @findex gnus-server-copy-server
12356 Copy the current server (@code{gnus-server-copy-server}).
12360 @findex gnus-server-list-servers
12361 List all servers (@code{gnus-server-list-servers}).
12365 @findex gnus-server-scan-server
12366 Request that the server scan its sources for new articles
12367 (@code{gnus-server-scan-server}). This is mainly sensible with mail
12372 @findex gnus-server-regenerate-server
12373 Request that the server regenerate all its data structures
12374 (@code{gnus-server-regenerate-server}). This can be useful if you have
12375 a mail back end that has gotten out of sync.
12380 @node Example Methods
12381 @subsection Example Methods
12383 Most select methods are pretty simple and self-explanatory:
12386 (nntp "news.funet.fi")
12389 Reading directly from the spool is even simpler:
12395 As you can see, the first element in a select method is the name of the
12396 back end, and the second is the @dfn{address}, or @dfn{name}, if you
12399 After these two elements, there may be an arbitrary number of
12400 @code{(@var{variable} @var{form})} pairs.
12402 To go back to the first example---imagine that you want to read from
12403 port 15 on that machine. This is what the select method should
12407 (nntp "news.funet.fi" (nntp-port-number 15))
12410 You should read the documentation to each back end to find out what
12411 variables are relevant, but here's an @code{nnmh} example:
12413 @code{nnmh} is a mail back end that reads a spool-like structure. Say
12414 you have two structures that you wish to access: One is your private
12415 mail spool, and the other is a public one. Here's the possible spec for
12419 (nnmh "private" (nnmh-directory "~/private/mail/"))
12422 (This server is then called @samp{private}, but you may have guessed
12425 Here's the method for a public spool:
12429 (nnmh-directory "/usr/information/spool/")
12430 (nnmh-get-new-mail nil))
12436 If you are behind a firewall and only have access to the @acronym{NNTP}
12437 server from the firewall machine, you can instruct Gnus to @code{rlogin}
12438 on the firewall machine and telnet from there to the @acronym{NNTP} server.
12439 Doing this can be rather fiddly, but your virtual server definition
12440 should probably look something like this:
12444 (nntp-open-connection-function nntp-open-via-rlogin-and-telnet)
12445 (nntp-via-address "the.firewall.machine")
12446 (nntp-address "the.real.nntp.host")
12447 (nntp-end-of-line "\n"))
12450 If you want to use the wonderful @code{ssh} program to provide a
12451 compressed connection over the modem line, you could add the following
12452 configuration to the example above:
12455 (nntp-via-rlogin-command "ssh")
12458 See also @code{nntp-via-rlogin-command-switches}.
12460 If you're behind a firewall, but have direct access to the outside world
12461 through a wrapper command like "runsocks", you could open a socksified
12462 telnet connection to the news server as follows:
12466 (nntp-pre-command "runsocks")
12467 (nntp-open-connection-function nntp-open-via-telnet)
12468 (nntp-address "the.news.server")
12469 (nntp-end-of-line "\n"))
12472 This means that you have to have set up @code{ssh-agent} correctly to
12473 provide automatic authorization, of course. And to get a compressed
12474 connection, you have to have the @samp{Compression} option in the
12475 @code{ssh} @file{config} file.
12478 @node Creating a Virtual Server
12479 @subsection Creating a Virtual Server
12481 If you're saving lots of articles in the cache by using persistent
12482 articles, you may want to create a virtual server to read the cache.
12484 First you need to add a new server. The @kbd{a} command does that. It
12485 would probably be best to use @code{nnml} to read the cache. You
12486 could also use @code{nnspool} or @code{nnmh}, though.
12488 Type @kbd{a nnml RET cache RET}.
12490 You should now have a brand new @code{nnml} virtual server called
12491 @samp{cache}. You now need to edit it to have the right definitions.
12492 Type @kbd{e} to edit the server. You'll be entered into a buffer that
12493 will contain the following:
12503 (nnml-directory "~/News/cache/")
12504 (nnml-active-file "~/News/cache/active"))
12507 Type @kbd{C-c C-c} to return to the server buffer. If you now press
12508 @kbd{RET} over this virtual server, you should be entered into a browse
12509 buffer, and you should be able to enter any of the groups displayed.
12512 @node Server Variables
12513 @subsection Server Variables
12514 @cindex server variables
12515 @cindex server parameters
12517 One sticky point when defining variables (both on back ends and in Emacs
12518 in general) is that some variables are typically initialized from other
12519 variables when the definition of the variables is being loaded. If you
12520 change the ``base'' variable after the variables have been loaded, you
12521 won't change the ``derived'' variables.
12523 This typically affects directory and file variables. For instance,
12524 @code{nnml-directory} is @file{~/Mail/} by default, and all @code{nnml}
12525 directory variables are initialized from that variable, so
12526 @code{nnml-active-file} will be @file{~/Mail/active}. If you define a
12527 new virtual @code{nnml} server, it will @emph{not} suffice to set just
12528 @code{nnml-directory}---you have to explicitly set all the file
12529 variables to be what you want them to be. For a complete list of
12530 variables for each back end, see each back end's section later in this
12531 manual, but here's an example @code{nnml} definition:
12535 (nnml-directory "~/my-mail/")
12536 (nnml-active-file "~/my-mail/active")
12537 (nnml-newsgroups-file "~/my-mail/newsgroups"))
12540 Server variables are often called @dfn{server parameters}.
12542 @node Servers and Methods
12543 @subsection Servers and Methods
12545 Wherever you would normally use a select method
12546 (e.g. @code{gnus-secondary-select-method}, in the group select method,
12547 when browsing a foreign server) you can use a virtual server name
12548 instead. This could potentially save lots of typing. And it's nice all
12552 @node Unavailable Servers
12553 @subsection Unavailable Servers
12555 If a server seems to be unreachable, Gnus will mark that server as
12556 @code{denied}. That means that any subsequent attempt to make contact
12557 with that server will just be ignored. ``It can't be opened,'' Gnus
12558 will tell you, without making the least effort to see whether that is
12559 actually the case or not.
12561 That might seem quite naughty, but it does make sense most of the time.
12562 Let's say you have 10 groups subscribed to on server
12563 @samp{nephelococcygia.com}. This server is located somewhere quite far
12564 away from you and the machine is quite slow, so it takes 1 minute just
12565 to find out that it refuses connection to you today. If Gnus were to
12566 attempt to do that 10 times, you'd be quite annoyed, so Gnus won't
12567 attempt to do that. Once it has gotten a single ``connection refused'',
12568 it will regard that server as ``down''.
12570 So, what happens if the machine was only feeling unwell temporarily?
12571 How do you test to see whether the machine has come up again?
12573 You jump to the server buffer (@pxref{Server Buffer}) and poke it
12574 with the following commands:
12580 @findex gnus-server-open-server
12581 Try to establish connection to the server on the current line
12582 (@code{gnus-server-open-server}).
12586 @findex gnus-server-close-server
12587 Close the connection (if any) to the server
12588 (@code{gnus-server-close-server}).
12592 @findex gnus-server-deny-server
12593 Mark the current server as unreachable
12594 (@code{gnus-server-deny-server}).
12597 @kindex M-o (Server)
12598 @findex gnus-server-open-all-servers
12599 Open the connections to all servers in the buffer
12600 (@code{gnus-server-open-all-servers}).
12603 @kindex M-c (Server)
12604 @findex gnus-server-close-all-servers
12605 Close the connections to all servers in the buffer
12606 (@code{gnus-server-close-all-servers}).
12610 @findex gnus-server-remove-denials
12611 Remove all marks to whether Gnus was denied connection from any servers
12612 (@code{gnus-server-remove-denials}).
12616 @findex gnus-server-offline-server
12617 Set server status to offline (@code{gnus-server-offline-server}).
12623 @section Getting News
12624 @cindex reading news
12625 @cindex news back ends
12627 A newsreader is normally used for reading news. Gnus currently provides
12628 only two methods of getting news---it can read from an @acronym{NNTP} server,
12629 or it can read from a local spool.
12632 * NNTP:: Reading news from an @acronym{NNTP} server.
12633 * News Spool:: Reading news from the local spool.
12641 Subscribing to a foreign group from an @acronym{NNTP} server is rather easy.
12642 You just specify @code{nntp} as method and the address of the @acronym{NNTP}
12643 server as the, uhm, address.
12645 If the @acronym{NNTP} server is located at a non-standard port, setting the
12646 third element of the select method to this port number should allow you
12647 to connect to the right port. You'll have to edit the group info for
12648 that (@pxref{Foreign Groups}).
12650 The name of the foreign group can be the same as a native group. In
12651 fact, you can subscribe to the same group from as many different servers
12652 you feel like. There will be no name collisions.
12654 The following variables can be used to create a virtual @code{nntp}
12659 @item nntp-server-opened-hook
12660 @vindex nntp-server-opened-hook
12661 @cindex @sc{mode reader}
12663 @cindex authentification
12664 @cindex nntp authentification
12665 @findex nntp-send-authinfo
12666 @findex nntp-send-mode-reader
12667 is run after a connection has been made. It can be used to send
12668 commands to the @acronym{NNTP} server after it has been contacted. By
12669 default it sends the command @code{MODE READER} to the server with the
12670 @code{nntp-send-mode-reader} function. This function should always be
12671 present in this hook.
12673 @item nntp-authinfo-function
12674 @vindex nntp-authinfo-function
12675 @findex nntp-send-authinfo
12676 @vindex nntp-authinfo-file
12677 This function will be used to send @samp{AUTHINFO} to the @acronym{NNTP}
12678 server. The default function is @code{nntp-send-authinfo}, which looks
12679 through your @file{~/.authinfo} (or whatever you've set the
12680 @code{nntp-authinfo-file} variable to) for applicable entries. If none
12681 are found, it will prompt you for a login name and a password. The
12682 format of the @file{~/.authinfo} file is (almost) the same as the
12683 @code{ftp} @file{~/.netrc} file, which is defined in the @code{ftp}
12684 manual page, but here are the salient facts:
12688 The file contains one or more line, each of which define one server.
12691 Each line may contain an arbitrary number of token/value pairs.
12693 The valid tokens include @samp{machine}, @samp{login}, @samp{password},
12694 @samp{default}. In addition Gnus introduces two new tokens, not present
12695 in the original @file{.netrc}/@code{ftp} syntax, namely @samp{port} and
12696 @samp{force}. (This is the only way the @file{.authinfo} file format
12697 deviates from the @file{.netrc} file format.) @samp{port} is used to
12698 indicate what port on the server the credentials apply to and
12699 @samp{force} is explained below.
12703 Here's an example file:
12706 machine news.uio.no login larsi password geheimnis
12707 machine nntp.ifi.uio.no login larsi force yes
12710 The token/value pairs may appear in any order; @samp{machine} doesn't
12711 have to be first, for instance.
12713 In this example, both login name and password have been supplied for the
12714 former server, while the latter has only the login name listed, and the
12715 user will be prompted for the password. The latter also has the
12716 @samp{force} tag, which means that the authinfo will be sent to the
12717 @var{nntp} server upon connection; the default (i.e., when there is not
12718 @samp{force} tag) is to not send authinfo to the @var{nntp} server
12719 until the @var{nntp} server asks for it.
12721 You can also add @samp{default} lines that will apply to all servers
12722 that don't have matching @samp{machine} lines.
12728 This will force sending @samp{AUTHINFO} commands to all servers not
12729 previously mentioned.
12731 Remember to not leave the @file{~/.authinfo} file world-readable.
12733 @item nntp-server-action-alist
12734 @vindex nntp-server-action-alist
12735 This is a list of regexps to match on server types and actions to be
12736 taken when matches are made. For instance, if you want Gnus to beep
12737 every time you connect to innd, you could say something like:
12740 (setq nntp-server-action-alist
12741 '(("innd" (ding))))
12744 You probably don't want to do that, though.
12746 The default value is
12749 '(("nntpd 1\\.5\\.11t"
12750 (remove-hook 'nntp-server-opened-hook
12751 'nntp-send-mode-reader)))
12754 This ensures that Gnus doesn't send the @code{MODE READER} command to
12755 nntpd 1.5.11t, since that command chokes that server, I've been told.
12757 @item nntp-maximum-request
12758 @vindex nntp-maximum-request
12759 If the @acronym{NNTP} server doesn't support @acronym{NOV} headers, this back end
12760 will collect headers by sending a series of @code{head} commands. To
12761 speed things up, the back end sends lots of these commands without
12762 waiting for reply, and then reads all the replies. This is controlled
12763 by the @code{nntp-maximum-request} variable, and is 400 by default. If
12764 your network is buggy, you should set this to 1.
12766 @item nntp-connection-timeout
12767 @vindex nntp-connection-timeout
12768 If you have lots of foreign @code{nntp} groups that you connect to
12769 regularly, you're sure to have problems with @acronym{NNTP} servers not
12770 responding properly, or being too loaded to reply within reasonable
12771 time. This is can lead to awkward problems, which can be helped
12772 somewhat by setting @code{nntp-connection-timeout}. This is an integer
12773 that says how many seconds the @code{nntp} back end should wait for a
12774 connection before giving up. If it is @code{nil}, which is the default,
12775 no timeouts are done.
12777 @c @item nntp-command-timeout
12778 @c @vindex nntp-command-timeout
12779 @c @cindex PPP connections
12780 @c @cindex dynamic IP addresses
12781 @c If you're running Gnus on a machine that has a dynamically assigned
12782 @c address, Gnus may become confused. If the address of your machine
12783 @c changes after connecting to the @acronym{NNTP} server, Gnus will simply sit
12784 @c waiting forever for replies from the server. To help with this
12785 @c unfortunate problem, you can set this command to a number. Gnus will
12786 @c then, if it sits waiting for a reply from the server longer than that
12787 @c number of seconds, shut down the connection, start a new one, and resend
12788 @c the command. This should hopefully be transparent to the user. A
12789 @c likely number is 30 seconds.
12791 @c @item nntp-retry-on-break
12792 @c @vindex nntp-retry-on-break
12793 @c If this variable is non-@code{nil}, you can also @kbd{C-g} if Gnus
12794 @c hangs. This will have much the same effect as the command timeout
12795 @c described above.
12797 @item nntp-server-hook
12798 @vindex nntp-server-hook
12799 This hook is run as the last step when connecting to an @acronym{NNTP}
12802 @item nntp-buggy-select
12803 @vindex nntp-buggy-select
12804 Set this to non-@code{nil} if your select routine is buggy.
12806 @item nntp-nov-is-evil
12807 @vindex nntp-nov-is-evil
12808 If the @acronym{NNTP} server does not support @acronym{NOV}, you could set this
12809 variable to @code{t}, but @code{nntp} usually checks automatically whether @acronym{NOV}
12812 @item nntp-xover-commands
12813 @vindex nntp-xover-commands
12814 @cindex @acronym{NOV}
12816 List of strings used as commands to fetch @acronym{NOV} lines from a
12817 server. The default value of this variable is @code{("XOVER"
12821 @vindex nntp-nov-gap
12822 @code{nntp} normally sends just one big request for @acronym{NOV} lines to
12823 the server. The server responds with one huge list of lines. However,
12824 if you have read articles 2-5000 in the group, and only want to read
12825 article 1 and 5001, that means that @code{nntp} will fetch 4999 @acronym{NOV}
12826 lines that you will not need. This variable says how
12827 big a gap between two consecutive articles is allowed to be before the
12828 @code{XOVER} request is split into several request. Note that if your
12829 network is fast, setting this variable to a really small number means
12830 that fetching will probably be slower. If this variable is @code{nil},
12831 @code{nntp} will never split requests. The default is 5.
12833 @item nntp-prepare-server-hook
12834 @vindex nntp-prepare-server-hook
12835 A hook run before attempting to connect to an @acronym{NNTP} server.
12837 @item nntp-warn-about-losing-connection
12838 @vindex nntp-warn-about-losing-connection
12839 If this variable is non-@code{nil}, some noise will be made when a
12840 server closes connection.
12842 @item nntp-record-commands
12843 @vindex nntp-record-commands
12844 If non-@code{nil}, @code{nntp} will log all commands it sends to the
12845 @acronym{NNTP} server (along with a timestamp) in the @samp{*nntp-log*}
12846 buffer. This is useful if you are debugging a Gnus/@acronym{NNTP} connection
12847 that doesn't seem to work.
12849 @item nntp-open-connection-function
12850 @vindex nntp-open-connection-function
12851 It is possible to customize how the connection to the nntp server will
12852 be opened. If you specify an @code{nntp-open-connection-function}
12853 parameter, Gnus will use that function to establish the connection.
12854 Five pre-made functions are supplied. These functions can be grouped in
12855 two categories: direct connection functions (three pre-made), and
12856 indirect ones (two pre-made).
12858 @item nntp-prepare-post-hook
12859 @vindex nntp-prepare-post-hook
12860 A hook run just before posting an article. If there is no
12861 @code{Message-ID} header in the article and the news server provides the
12862 recommended ID, it will be added to the article before running this
12863 hook. It is useful to make @code{Cancel-Lock} headers even if you
12864 inhibit Gnus to add a @code{Message-ID} header, you could say:
12867 (add-hook 'nntp-prepare-post-hook 'canlock-insert-header)
12870 Note that not all servers support the recommended ID. This works for
12871 INN versions 2.3.0 and later, for instance.
12873 @item nntp-read-timeout
12874 @vindex nntp-read-timeout
12875 How long nntp should wait between checking for the end of output.
12876 Shorter values mean quicker response, but is more CPU intensive. The
12877 default is 0.1 seconds. If you have a slow line to the server (and
12878 don't like to see Emacs eat your available CPU power), you might set
12884 * Direct Functions:: Connecting directly to the server.
12885 * Indirect Functions:: Connecting indirectly to the server.
12886 * Common Variables:: Understood by several connection functions.
12887 * NNTP marks:: Storing marks for @acronym{NNTP} servers.
12891 @node Direct Functions
12892 @subsubsection Direct Functions
12893 @cindex direct connection functions
12895 These functions are called direct because they open a direct connection
12896 between your machine and the @acronym{NNTP} server. The behavior of these
12897 functions is also affected by commonly understood variables
12898 (@pxref{Common Variables}).
12901 @findex nntp-open-network-stream
12902 @item nntp-open-network-stream
12903 This is the default, and simply connects to some port or other on the
12906 @findex nntp-open-tls-stream
12907 @item nntp-open-tls-stream
12908 Opens a connection to a server over a @dfn{secure} channel. To use
12909 this you must have @uref{http://www.gnu.org/software/gnutls/, GNUTLS}
12910 installed. You then define a server as follows:
12913 ;; @r{"nntps" is port 563 and is predefined in our @file{/etc/services}}
12914 ;; @r{however, @samp{gnutls-cli -p} doesn't like named ports.}
12916 (nntp "snews.bar.com"
12917 (nntp-open-connection-function nntp-open-tls-stream)
12918 (nntp-port-number )
12919 (nntp-address "snews.bar.com"))
12922 @findex nntp-open-ssl-stream
12923 @item nntp-open-ssl-stream
12924 Opens a connection to a server over a @dfn{secure} channel. To use
12925 this you must have @uref{http://www.openssl.org, OpenSSL} or
12926 @uref{ftp://ftp.psy.uq.oz.au/pub/Crypto/SSL, SSLeay} installed. You
12927 then define a server as follows:
12930 ;; @r{"snews" is port 563 and is predefined in our @file{/etc/services}}
12931 ;; @r{however, @samp{openssl s_client -port} doesn't like named ports.}
12933 (nntp "snews.bar.com"
12934 (nntp-open-connection-function nntp-open-ssl-stream)
12935 (nntp-port-number 563)
12936 (nntp-address "snews.bar.com"))
12939 @findex nntp-open-telnet-stream
12940 @item nntp-open-telnet-stream
12941 Opens a connection to an @acronym{NNTP} server by simply @samp{telnet}'ing
12942 it. You might wonder why this function exists, since we have the
12943 default @code{nntp-open-network-stream} which would do the job. (One
12944 of) the reason(s) is that if you are behind a firewall but have direct
12945 connections to the outside world thanks to a command wrapper like
12946 @code{runsocks}, you can use it like this:
12950 (nntp-pre-command "runsocks")
12951 (nntp-open-connection-function nntp-open-telnet-stream)
12952 (nntp-address "the.news.server"))
12955 With the default method, you would need to wrap your whole Emacs
12956 session, which is not a good idea.
12960 @node Indirect Functions
12961 @subsubsection Indirect Functions
12962 @cindex indirect connection functions
12964 These functions are called indirect because they connect to an
12965 intermediate host before actually connecting to the @acronym{NNTP} server.
12966 All of these functions and related variables are also said to belong to
12967 the ``via'' family of connection: they're all prefixed with ``via'' to make
12968 things cleaner. The behavior of these functions is also affected by
12969 commonly understood variables (@pxref{Common Variables}).
12972 @item nntp-open-via-rlogin-and-telnet
12973 @findex nntp-open-via-rlogin-and-telnet
12974 Does an @samp{rlogin} on a remote system, and then does a @samp{telnet}
12975 to the real @acronym{NNTP} server from there. This is useful for instance if
12976 you need to connect to a firewall machine first.
12978 @code{nntp-open-via-rlogin-and-telnet}-specific variables:
12981 @item nntp-via-rlogin-command
12982 @vindex nntp-via-rlogin-command
12983 Command used to log in on the intermediate host. The default is
12984 @samp{rsh}, but @samp{ssh} is a popular alternative.
12986 @item nntp-via-rlogin-command-switches
12987 @vindex nntp-via-rlogin-command-switches
12988 List of strings to be used as the switches to
12989 @code{nntp-via-rlogin-command}. The default is @code{nil}. If you use
12990 @samp{ssh} for @code{nntp-via-rlogin-command}, you may set this to
12991 @samp{("-C")} in order to compress all data connections, otherwise set
12992 this to @samp{("-t" "-e" "none")} or @samp{("-C" "-t" "-e" "none")} if
12993 the telnet command requires a pseudo-tty allocation on an intermediate
12997 Note that you may want to change the value for @code{nntp-end-of-line}
12998 to @samp{\n} (@pxref{Common Variables}).
13000 @item nntp-open-via-rlogin-and-netcat
13001 @findex nntp-open-via-rlogin-and-netcat
13002 Does essentially the same, but uses
13003 @uref{http://netcat.sourceforge.net/, netcat} instead of @samp{telnet}
13004 to connect to the real @acronym{NNTP} server from the intermediate host.
13006 @code{nntp-open-via-rlogin-and-netcat}-specific variables:
13009 @item nntp-via-netcat-command
13010 @vindex nntp-via-netcat-command
13011 Command used to connect to the real @acronym{NNTP} server from the
13012 intermediate host. The default is @samp{nc}. You can also use other
13013 programs like @uref{http://www.imasy.or.jp/~gotoh/ssh/connect.html,
13016 @item nntp-via-netcat-switches
13017 @vindex nntp-via-netcat-switches
13018 List of strings to be used as the switches to the
13019 @code{nntp-via-telnet-command} command. The default is @code{nil}.
13021 @item nntp-via-rlogin-command
13022 @vindex nntp-via-rlogin-command
13023 Command used to log in on the intermediate host. The default is
13024 @samp{rsh}, but @samp{ssh} is a popular alternative.
13026 @item nntp-via-rlogin-command-switches
13027 @vindex nntp-via-rlogin-command-switches
13028 List of strings to be used as the switches to
13029 @code{nntp-via-rlogin-command}. The default is @code{nil}.
13032 @item nntp-open-via-telnet-and-telnet
13033 @findex nntp-open-via-telnet-and-telnet
13034 Does essentially also the same, but uses @samp{telnet} instead of
13035 @samp{rlogin} to connect to the intermediate host.
13037 @code{nntp-open-via-telnet-and-telnet}-specific variables:
13040 @item nntp-via-telnet-command
13041 @vindex nntp-via-telnet-command
13042 Command used to @code{telnet} the intermediate host. The default is
13045 @item nntp-via-telnet-switches
13046 @vindex nntp-via-telnet-switches
13047 List of strings to be used as the switches to the
13048 @code{nntp-via-telnet-command} command. The default is @samp{("-8")}.
13050 @item nntp-via-user-password
13051 @vindex nntp-via-user-password
13052 Password to use when logging in on the intermediate host.
13054 @item nntp-via-envuser
13055 @vindex nntp-via-envuser
13056 If non-@code{nil}, the intermediate @code{telnet} session (client and
13057 server both) will support the @code{ENVIRON} option and not prompt for
13058 login name. This works for Solaris @code{telnet}, for instance.
13060 @item nntp-via-shell-prompt
13061 @vindex nntp-via-shell-prompt
13062 Regexp matching the shell prompt on the intermediate host. The default
13063 is @samp{bash\\|\$ *\r?$\\|> *\r?}.
13067 Note that you may want to change the value for @code{nntp-end-of-line}
13068 to @samp{\n} (@pxref{Common Variables}).
13072 Here are some additional variables that are understood by all the above
13077 @item nntp-via-user-name
13078 @vindex nntp-via-user-name
13079 User name to use when connecting to the intermediate host.
13081 @item nntp-via-address
13082 @vindex nntp-via-address
13083 Address of the intermediate host to connect to.
13088 @node Common Variables
13089 @subsubsection Common Variables
13091 The following variables affect the behavior of all, or several of the
13092 pre-made connection functions. When not specified, all functions are
13097 @item nntp-pre-command
13098 @vindex nntp-pre-command
13099 A command wrapper to use when connecting through a non native
13100 connection function (all except @code{nntp-open-network-stream},
13101 @code{nntp-open-tls-stream}, and @code{nntp-open-ssl-stream}. This is
13102 where you would put a @samp{SOCKS} wrapper for instance.
13105 @vindex nntp-address
13106 The address of the @acronym{NNTP} server.
13108 @item nntp-port-number
13109 @vindex nntp-port-number
13110 Port number to connect to the @acronym{NNTP} server. The default is
13111 @samp{nntp}. If you use @acronym{NNTP} over
13112 @acronym{tls}/@acronym{ssl}, you may want to use integer ports rather
13113 than named ports (i.e, use @samp{563} instead of @samp{snews} or
13114 @samp{nntps}), because external @acronym{TLS}/@acronym{SSL} tools may
13115 not work with named ports.
13117 @item nntp-end-of-line
13118 @vindex nntp-end-of-line
13119 String to use as end-of-line marker when talking to the @acronym{NNTP}
13120 server. This is @samp{\r\n} by default, but should be @samp{\n} when
13121 using a non native telnet connection function.
13123 @item nntp-telnet-command
13124 @vindex nntp-telnet-command
13125 Command to use when connecting to the @acronym{NNTP} server through
13126 @samp{telnet}. This is @emph{not} for an intermediate host. This is
13127 just for the real @acronym{NNTP} server. The default is
13130 @item nntp-telnet-switches
13131 @vindex nntp-telnet-switches
13132 A list of switches to pass to @code{nntp-telnet-command}. The default
13138 @subsubsection NNTP marks
13139 @cindex storing NNTP marks
13141 Gnus stores marks (@pxref{Marking Articles}) for @acronym{NNTP}
13142 servers in marks files. A marks file records what marks you have set
13143 in a group and each file is specific to the corresponding server.
13144 Marks files are stored in @file{~/News/marks}
13145 (@code{nntp-marks-directory}) under a classic hierarchy resembling
13146 that of a news server, for example marks for the group
13147 @samp{gmane.discuss} on the news.gmane.org server will be stored in
13148 the file @file{~/News/marks/news.gmane.org/gmane/discuss/.marks}.
13150 Marks files are useful because you can copy the @file{~/News/marks}
13151 directory (using rsync, scp or whatever) to another Gnus installation,
13152 and it will realize what articles you have read and marked. The data
13153 in @file{~/News/marks} has priority over the same data in
13154 @file{~/.newsrc.eld}.
13156 Note that marks files are very much server-specific: Gnus remembers
13157 the article numbers so if you don't use the same servers on both
13158 installations things are most likely to break (most @acronym{NNTP}
13159 servers do not use the same article numbers as any other server).
13160 However, if you use servers A, B, C on one installation and servers A,
13161 D, E on the other, you can sync the marks files for A and then you'll
13162 get synchronization for that server between the two installations.
13164 Using @acronym{NNTP} marks can possibly incur a performance penalty so
13165 if Gnus feels sluggish, try setting the @code{nntp-marks-is-evil}
13166 variable to @code{t}. Marks will then be stored in @file{~/.newsrc.eld}.
13172 @item nntp-marks-is-evil
13173 @vindex nntp-marks-is-evil
13174 If non-@code{nil}, this back end will ignore any marks files. The
13175 default is @code{nil}.
13177 @item nntp-marks-directory
13178 @vindex nntp-marks-directory
13179 The directory where marks for nntp groups will be stored.
13185 @subsection News Spool
13189 Subscribing to a foreign group from the local spool is extremely easy,
13190 and might be useful, for instance, to speed up reading groups that
13191 contain very big articles---@samp{alt.binaries.pictures.furniture}, for
13194 Anyway, you just specify @code{nnspool} as the method and @code{""} (or
13195 anything else) as the address.
13197 If you have access to a local spool, you should probably use that as the
13198 native select method (@pxref{Finding the News}). It is normally faster
13199 than using an @code{nntp} select method, but might not be. It depends.
13200 You just have to try to find out what's best at your site.
13204 @item nnspool-inews-program
13205 @vindex nnspool-inews-program
13206 Program used to post an article.
13208 @item nnspool-inews-switches
13209 @vindex nnspool-inews-switches
13210 Parameters given to the inews program when posting an article.
13212 @item nnspool-spool-directory
13213 @vindex nnspool-spool-directory
13214 Where @code{nnspool} looks for the articles. This is normally
13215 @file{/usr/spool/news/}.
13217 @item nnspool-nov-directory
13218 @vindex nnspool-nov-directory
13219 Where @code{nnspool} will look for @acronym{NOV} files. This is normally@*
13220 @file{/usr/spool/news/over.view/}.
13222 @item nnspool-lib-dir
13223 @vindex nnspool-lib-dir
13224 Where the news lib dir is (@file{/usr/lib/news/} by default).
13226 @item nnspool-active-file
13227 @vindex nnspool-active-file
13228 The name of the active file.
13230 @item nnspool-newsgroups-file
13231 @vindex nnspool-newsgroups-file
13232 The name of the group descriptions file.
13234 @item nnspool-history-file
13235 @vindex nnspool-history-file
13236 The name of the news history file.
13238 @item nnspool-active-times-file
13239 @vindex nnspool-active-times-file
13240 The name of the active date file.
13242 @item nnspool-nov-is-evil
13243 @vindex nnspool-nov-is-evil
13244 If non-@code{nil}, @code{nnspool} won't try to use any @acronym{NOV} files
13247 @item nnspool-sift-nov-with-sed
13248 @vindex nnspool-sift-nov-with-sed
13250 If non-@code{nil}, which is the default, use @code{sed} to get the
13251 relevant portion from the overview file. If @code{nil},
13252 @code{nnspool} will load the entire file into a buffer and process it
13259 @section Getting Mail
13260 @cindex reading mail
13263 Reading mail with a newsreader---isn't that just plain WeIrD? But of
13267 * Mail in a Newsreader:: Important introductory notes.
13268 * Getting Started Reading Mail:: A simple cookbook example.
13269 * Splitting Mail:: How to create mail groups.
13270 * Mail Sources:: How to tell Gnus where to get mail from.
13271 * Mail Back End Variables:: Variables for customizing mail handling.
13272 * Fancy Mail Splitting:: Gnus can do hairy splitting of incoming mail.
13273 * Group Mail Splitting:: Use group customize to drive mail splitting.
13274 * Incorporating Old Mail:: What about the old mail you have?
13275 * Expiring Mail:: Getting rid of unwanted mail.
13276 * Washing Mail:: Removing cruft from the mail you get.
13277 * Duplicates:: Dealing with duplicated mail.
13278 * Not Reading Mail:: Using mail back ends for reading other files.
13279 * Choosing a Mail Back End:: Gnus can read a variety of mail formats.
13283 @node Mail in a Newsreader
13284 @subsection Mail in a Newsreader
13286 If you are used to traditional mail readers, but have decided to switch
13287 to reading mail with Gnus, you may find yourself experiencing something
13288 of a culture shock.
13290 Gnus does not behave like traditional mail readers. If you want to make
13291 it behave that way, you can, but it's an uphill battle.
13293 Gnus, by default, handles all its groups using the same approach. This
13294 approach is very newsreaderly---you enter a group, see the new/unread
13295 messages, and when you read the messages, they get marked as read, and
13296 you don't see them any more. (Unless you explicitly ask for them.)
13298 In particular, you do not do anything explicitly to delete messages.
13300 Does this mean that all the messages that have been marked as read are
13301 deleted? How awful!
13303 But, no, it means that old messages are @dfn{expired} according to some
13304 scheme or other. For news messages, the expire process is controlled by
13305 the news administrator; for mail, the expire process is controlled by
13306 you. The expire process for mail is covered in depth in @ref{Expiring
13309 What many Gnus users find, after using it a while for both news and
13310 mail, is that the transport mechanism has very little to do with how
13311 they want to treat a message.
13313 Many people subscribe to several mailing lists. These are transported
13314 via @acronym{SMTP}, and are therefore mail. But we might go for weeks without
13315 answering, or even reading these messages very carefully. We may not
13316 need to save them because if we should need to read one again, they are
13317 archived somewhere else.
13319 Some people have local news groups which have only a handful of readers.
13320 These are transported via @acronym{NNTP}, and are therefore news. But we may need
13321 to read and answer a large fraction of the messages very carefully in
13322 order to do our work. And there may not be an archive, so we may need
13323 to save the interesting messages the same way we would personal mail.
13325 The important distinction turns out to be not the transport mechanism,
13326 but other factors such as how interested we are in the subject matter,
13327 or how easy it is to retrieve the message if we need to read it again.
13329 Gnus provides many options for sorting mail into ``groups'' which behave
13330 like newsgroups, and for treating each group (whether mail or news)
13333 Some users never get comfortable using the Gnus (ahem) paradigm and wish
13334 that Gnus should grow up and be a male, er, mail reader. It is possible
13335 to whip Gnus into a more mailreaderly being, but, as said before, it's
13336 not easy. People who prefer proper mail readers should try @sc{vm}
13337 instead, which is an excellent, and proper, mail reader.
13339 I don't mean to scare anybody off, but I want to make it clear that you
13340 may be required to learn a new way of thinking about messages. After
13341 you've been subjected to The Gnus Way, you will come to love it. I can
13342 guarantee it. (At least the guy who sold me the Emacs Subliminal
13343 Brain-Washing Functions that I've put into Gnus did guarantee it. You
13344 Will Be Assimilated. You Love Gnus. You Love The Gnus Mail Way.
13348 @node Getting Started Reading Mail
13349 @subsection Getting Started Reading Mail
13351 It's quite easy to use Gnus to read your new mail. You just plonk the
13352 mail back end of your choice into @code{gnus-secondary-select-methods},
13353 and things will happen automatically.
13355 For instance, if you want to use @code{nnml} (which is a ``one file per
13356 mail'' back end), you could put the following in your @file{~/.gnus.el} file:
13359 (setq gnus-secondary-select-methods '((nnml "")))
13362 Now, the next time you start Gnus, this back end will be queried for new
13363 articles, and it will move all the messages in your spool file to its
13364 directory, which is @file{~/Mail/} by default. The new group that will
13365 be created (@samp{mail.misc}) will be subscribed, and you can read it
13366 like any other group.
13368 You will probably want to split the mail into several groups, though:
13371 (setq nnmail-split-methods
13372 '(("junk" "^From:.*Lars Ingebrigtsen")
13373 ("crazy" "^Subject:.*die\\|^Organization:.*flabby")
13377 This will result in three new @code{nnml} mail groups being created:
13378 @samp{nnml:junk}, @samp{nnml:crazy}, and @samp{nnml:other}. All the
13379 mail that doesn't fit into the first two groups will be placed in the
13382 This should be sufficient for reading mail with Gnus. You might want to
13383 give the other sections in this part of the manual a perusal, though.
13384 Especially @pxref{Choosing a Mail Back End} and @pxref{Expiring Mail}.
13387 @node Splitting Mail
13388 @subsection Splitting Mail
13389 @cindex splitting mail
13390 @cindex mail splitting
13391 @cindex mail filtering (splitting)
13393 @vindex nnmail-split-methods
13394 The @code{nnmail-split-methods} variable says how the incoming mail is
13395 to be split into groups.
13398 (setq nnmail-split-methods
13399 '(("mail.junk" "^From:.*Lars Ingebrigtsen")
13400 ("mail.crazy" "^Subject:.*die\\|^Organization:.*flabby")
13401 ("mail.other" "")))
13404 This variable is a list of lists, where the first element of each of
13405 these lists is the name of the mail group (they do not have to be called
13406 something beginning with @samp{mail}, by the way), and the second
13407 element is a regular expression used on the header of each mail to
13408 determine if it belongs in this mail group. The first string may
13409 contain @samp{\\1} forms, like the ones used by @code{replace-match} to
13410 insert sub-expressions from the matched text. For instance:
13413 ("list.\\1" "From:.* \\(.*\\)-list@@majordomo.com")
13417 In that case, @code{nnmail-split-lowercase-expanded} controls whether
13418 the inserted text should be made lowercase. @xref{Fancy Mail Splitting}.
13420 The second element can also be a function. In that case, it will be
13421 called narrowed to the headers with the first element of the rule as the
13422 argument. It should return a non-@code{nil} value if it thinks that the
13423 mail belongs in that group.
13425 @cindex @samp{bogus} group
13426 The last of these groups should always be a general one, and the regular
13427 expression should @emph{always} be @samp{""} so that it matches any mails
13428 that haven't been matched by any of the other regexps. (These rules are
13429 processed from the beginning of the alist toward the end. The first rule
13430 to make a match will ``win'', unless you have crossposting enabled. In
13431 that case, all matching rules will ``win''.) If no rule matched, the mail
13432 will end up in the @samp{bogus} group. When new groups are created by
13433 splitting mail, you may want to run @code{gnus-group-find-new-groups} to
13434 see the new groups. This also applies to the @samp{bogus} group.
13436 If you like to tinker with this yourself, you can set this variable to a
13437 function of your choice. This function will be called without any
13438 arguments in a buffer narrowed to the headers of an incoming mail
13439 message. The function should return a list of group names that it
13440 thinks should carry this mail message.
13442 Note that the mail back ends are free to maul the poor, innocent,
13443 incoming headers all they want to. They all add @code{Lines} headers;
13444 some add @code{X-Gnus-Group} headers; most rename the Unix mbox
13445 @code{From<SPACE>} line to something else.
13447 @vindex nnmail-crosspost
13448 The mail back ends all support cross-posting. If several regexps match,
13449 the mail will be ``cross-posted'' to all those groups.
13450 @code{nnmail-crosspost} says whether to use this mechanism or not. Note
13451 that no articles are crossposted to the general (@samp{""}) group.
13453 @vindex nnmail-crosspost-link-function
13456 @code{nnmh} and @code{nnml} makes crossposts by creating hard links to
13457 the crossposted articles. However, not all file systems support hard
13458 links. If that's the case for you, set
13459 @code{nnmail-crosspost-link-function} to @code{copy-file}. (This
13460 variable is @code{add-name-to-file} by default.)
13462 @kindex M-x nnmail-split-history
13463 @findex nnmail-split-history
13464 If you wish to see where the previous mail split put the messages, you
13465 can use the @kbd{M-x nnmail-split-history} command. If you wish to see
13466 where re-spooling messages would put the messages, you can use
13467 @code{gnus-summary-respool-trace} and related commands (@pxref{Mail
13470 @vindex nnmail-split-header-length-limit
13471 Header lines longer than the value of
13472 @code{nnmail-split-header-length-limit} are excluded from the split
13475 @vindex nnmail-mail-splitting-charset
13476 @vindex nnmail-mail-splitting-decodes
13477 By default the splitting codes @acronym{MIME} decodes headers so you
13478 can match on non-@acronym{ASCII} strings. The
13479 @code{nnmail-mail-splitting-charset} variable specifies the default
13480 charset for decoding. The behavior can be turned off completely by
13481 binding @code{nnmail-mail-splitting-decodes} to @code{nil}, which is
13482 useful if you want to match articles based on the raw header data.
13484 @vindex nnmail-resplit-incoming
13485 By default, splitting is performed on all incoming messages. If you
13486 specify a @code{directory} entry for the variable @code{mail-sources}
13487 (@pxref{Mail Source Specifiers}), however, then splitting does
13488 @emph{not} happen by default. You can set the variable
13489 @code{nnmail-resplit-incoming} to a non-@code{nil} value to make
13490 splitting happen even in this case. (This variable has no effect on
13491 other kinds of entries.)
13493 Gnus gives you all the opportunity you could possibly want for shooting
13494 yourself in the foot. Let's say you create a group that will contain
13495 all the mail you get from your boss. And then you accidentally
13496 unsubscribe from the group. Gnus will still put all the mail from your
13497 boss in the unsubscribed group, and so, when your boss mails you ``Have
13498 that report ready by Monday or you're fired!'', you'll never see it and,
13499 come Tuesday, you'll still believe that you're gainfully employed while
13500 you really should be out collecting empty bottles to save up for next
13501 month's rent money.
13505 @subsection Mail Sources
13507 Mail can be gotten from many different sources---the mail spool, from
13508 a @acronym{POP} mail server, from a procmail directory, or from a
13509 maildir, for instance.
13512 * Mail Source Specifiers:: How to specify what a mail source is.
13513 * Mail Source Customization:: Some variables that influence things.
13514 * Fetching Mail:: Using the mail source specifiers.
13518 @node Mail Source Specifiers
13519 @subsubsection Mail Source Specifiers
13521 @cindex mail server
13524 @cindex mail source
13526 You tell Gnus how to fetch mail by setting @code{mail-sources}
13527 (@pxref{Fetching Mail}) to a @dfn{mail source specifier}.
13532 (pop :server "pop3.mailserver.com" :user "myname")
13535 As can be observed, a mail source specifier is a list where the first
13536 element is a @dfn{mail source type}, followed by an arbitrary number of
13537 @dfn{keywords}. Keywords that are not explicitly specified are given
13540 The following mail source types are available:
13544 Get mail from a single file; typically from the mail spool.
13550 The file name. Defaults to the value of the @env{MAIL}
13551 environment variable or the value of @code{rmail-spool-directory}
13552 (usually something like @file{/usr/mail/spool/user-name}).
13556 Script run before/after fetching mail.
13559 An example file mail source:
13562 (file :path "/usr/spool/mail/user-name")
13565 Or using the default file name:
13571 If the mail spool file is not located on the local machine, it's best
13572 to use @acronym{POP} or @acronym{IMAP} or the like to fetch the mail.
13573 You can not use ange-ftp file names here---it has no way to lock the
13574 mail spool while moving the mail.
13576 If it's impossible to set up a proper server, you can use ssh instead.
13580 '((file :prescript "ssh host bin/getmail >%t")))
13583 The @samp{getmail} script would look something like the following:
13587 # getmail - move mail from spool to stdout
13590 MOVEMAIL=/usr/lib/emacs/20.3/i386-redhat-linux/movemail
13592 rm -f $TMP; $MOVEMAIL $MAIL $TMP >/dev/null && cat $TMP
13595 Alter this script to fit find the @samp{movemail} you want to use.
13599 @vindex nnmail-scan-directory-mail-source-once
13600 Get mail from several files in a directory. This is typically used
13601 when you have procmail split the incoming mail into several files.
13602 That is, there is a one-to-one correspondence between files in that
13603 directory and groups, so that mail from the file @file{foo.bar.spool}
13604 will be put in the group @code{foo.bar}. (You can change the suffix
13605 to be used instead of @code{.spool}.) Setting
13606 @code{nnmail-scan-directory-mail-source-once} to non-@code{nil} forces
13607 Gnus to scan the mail source only once. This is particularly useful
13608 if you want to scan mail groups at a specified level.
13610 @vindex nnmail-resplit-incoming
13611 There is also the variable @code{nnmail-resplit-incoming}, if you set
13612 that to a non-@code{nil} value, then the normal splitting process is
13613 applied to all the files from the directory, @ref{Splitting Mail}.
13619 The name of the directory where the files are. There is no default
13623 Only files ending with this suffix are used. The default is
13627 Only files that have this predicate return non-@code{nil} are returned.
13628 The default is @code{identity}. This is used as an additional
13629 filter---only files that have the right suffix @emph{and} satisfy this
13630 predicate are considered.
13634 Script run before/after fetching mail.
13638 An example directory mail source:
13641 (directory :path "/home/user-name/procmail-dir/"
13646 Get mail from a @acronym{POP} server.
13652 The name of the @acronym{POP} server. The default is taken from the
13653 @env{MAILHOST} environment variable.
13656 The port number of the @acronym{POP} server. This can be a number (eg,
13657 @samp{:port 1234}) or a string (eg, @samp{:port "pop3"}). If it is a
13658 string, it should be a service name as listed in @file{/etc/services} on
13659 Unix systems. The default is @samp{"pop3"}. On some systems you might
13660 need to specify it as @samp{"pop-3"} instead.
13663 The user name to give to the @acronym{POP} server. The default is the login
13667 The password to give to the @acronym{POP} server. If not specified,
13668 the user is prompted.
13671 The program to use to fetch mail from the @acronym{POP} server. This
13672 should be a @code{format}-like string. Here's an example:
13675 fetchmail %u@@%s -P %p %t
13678 The valid format specifier characters are:
13682 The name of the file the mail is to be moved to. This must always be
13683 included in this string.
13686 The name of the server.
13689 The port number of the server.
13692 The user name to use.
13695 The password to use.
13698 The values used for these specs are taken from the values you give the
13699 corresponding keywords.
13702 A script to be run before fetching the mail. The syntax is the same as
13703 the @code{:program} keyword. This can also be a function to be run.
13706 A script to be run after fetching the mail. The syntax is the same as
13707 the @code{:program} keyword. This can also be a function to be run.
13710 The function to use to fetch mail from the @acronym{POP} server. The
13711 function is called with one parameter---the name of the file where the
13712 mail should be moved to.
13714 @item :authentication
13715 This can be either the symbol @code{password} or the symbol @code{apop}
13716 and says what authentication scheme to use. The default is
13721 @vindex pop3-movemail
13722 @vindex pop3-leave-mail-on-server
13723 If the @code{:program} and @code{:function} keywords aren't specified,
13724 @code{pop3-movemail} will be used. If the
13725 @code{pop3-leave-mail-on-server} is non-@code{nil} the mail is to be
13726 left on the @acronym{POP} server after fetching when using
13727 @code{pop3-movemail}. Note that POP servers maintain no state
13728 information between sessions, so what the client believes is there and
13729 what is actually there may not match up. If they do not, then the whole
13730 thing can fall apart and leave you with a corrupt mailbox.
13732 Here are some examples. Fetch from the default @acronym{POP} server,
13733 using the default user name, and default fetcher:
13739 Fetch from a named server with a named user and password:
13742 (pop :server "my.pop.server"
13743 :user "user-name" :password "secret")
13746 Use @samp{movemail} to move the mail:
13749 (pop :program "movemail po:%u %t %p")
13753 Get mail from a maildir. This is a type of mailbox that is supported by
13754 at least qmail and postfix, where each file in a special directory
13755 contains exactly one mail.
13761 The name of the directory where the mails are stored. The default is
13762 taken from the @env{MAILDIR} environment variable or
13765 The subdirectories of the Maildir. The default is
13766 @samp{("new" "cur")}.
13768 @c If you sometimes look at your mail through a pop3 daemon before fetching
13769 @c them with Gnus, you may also have to fetch your mails from the
13770 @c @code{cur} directory inside the maildir, like in the first example
13773 You can also get mails from remote hosts (because maildirs don't suffer
13774 from locking problems).
13778 Two example maildir mail sources:
13781 (maildir :path "/home/user-name/Maildir/"
13782 :subdirs ("cur" "new"))
13786 (maildir :path "/user@@remotehost.org:~/Maildir/"
13791 Get mail from a @acronym{IMAP} server. If you don't want to use
13792 @acronym{IMAP} as intended, as a network mail reading protocol (ie
13793 with nnimap), for some reason or other, Gnus let you treat it similar
13794 to a @acronym{POP} server and fetches articles from a given
13795 @acronym{IMAP} mailbox. @xref{IMAP}, for more information.
13797 Note that for the Kerberos, GSSAPI, @acronym{TLS}/@acronym{SSL} and STARTTLS support you
13798 may need external programs and libraries, @xref{IMAP}.
13804 The name of the @acronym{IMAP} server. The default is taken from the
13805 @env{MAILHOST} environment variable.
13808 The port number of the @acronym{IMAP} server. The default is @samp{143}, or
13809 @samp{993} for @acronym{TLS}/@acronym{SSL} connections.
13812 The user name to give to the @acronym{IMAP} server. The default is the login
13816 The password to give to the @acronym{IMAP} server. If not specified, the user is
13820 What stream to use for connecting to the server, this is one of the
13821 symbols in @code{imap-stream-alist}. Right now, this means
13822 @samp{gssapi}, @samp{kerberos4}, @samp{starttls}, @samp{tls},
13823 @samp{ssl}, @samp{shell} or the default @samp{network}.
13825 @item :authentication
13826 Which authenticator to use for authenticating to the server, this is
13827 one of the symbols in @code{imap-authenticator-alist}. Right now,
13828 this means @samp{gssapi}, @samp{kerberos4}, @samp{digest-md5},
13829 @samp{cram-md5}, @samp{anonymous} or the default @samp{login}.
13832 When using the `shell' :stream, the contents of this variable is
13833 mapped into the @code{imap-shell-program} variable. This should be a
13834 @code{format}-like string (or list of strings). Here's an example:
13840 The valid format specifier characters are:
13844 The name of the server.
13847 User name from @code{imap-default-user}.
13850 The port number of the server.
13853 The values used for these specs are taken from the values you give the
13854 corresponding keywords.
13857 The name of the mailbox to get mail from. The default is @samp{INBOX}
13858 which normally is the mailbox which receive incoming mail.
13861 The predicate used to find articles to fetch. The default, @samp{UNSEEN
13862 UNDELETED}, is probably the best choice for most people, but if you
13863 sometimes peek in your mailbox with a @acronym{IMAP} client and mark some
13864 articles as read (or; SEEN) you might want to set this to @samp{1:*}.
13865 Then all articles in the mailbox is fetched, no matter what. For a
13866 complete list of predicates, see RFC 2060 section 6.4.4.
13869 How to flag fetched articles on the server, the default @samp{\Deleted}
13870 will mark them as deleted, an alternative would be @samp{\Seen} which
13871 would simply mark them as read. These are the two most likely choices,
13872 but more flags are defined in RFC 2060 section 2.3.2.
13875 If non-@code{nil}, don't remove all articles marked as deleted in the
13876 mailbox after finishing the fetch.
13880 An example @acronym{IMAP} mail source:
13883 (imap :server "mail.mycorp.com"
13885 :fetchflag "\\Seen")
13889 Get mail from a webmail server, such as @uref{http://www.hotmail.com/},
13890 @uref{http://webmail.netscape.com/}, @uref{http://www.netaddress.com/},
13891 @uref{http://mail.yahoo.com/}.
13893 NOTE: Webmail largely depends on cookies. A "one-line-cookie" patch is
13894 required for url "4.0pre.46".
13896 WARNING: Mails may be lost. NO WARRANTY.
13902 The type of the webmail server. The default is @code{hotmail}. The
13903 alternatives are @code{netscape}, @code{netaddress}, @code{my-deja}.
13906 The user name to give to the webmail server. The default is the login
13910 The password to give to the webmail server. If not specified, the user is
13914 If non-@code{nil}, only fetch unread articles and don't move them to
13915 trash folder after finishing the fetch.
13919 An example webmail source:
13922 (webmail :subtype 'hotmail
13924 :password "secret")
13929 @item Common Keywords
13930 Common keywords can be used in any type of mail source.
13936 If non-@code{nil}, fetch the mail even when Gnus is unplugged. If you
13937 use directory source to get mail, you can specify it as in this
13942 '((directory :path "/home/pavel/.Spool/"
13947 Gnus will then fetch your mail even when you are unplugged. This is
13948 useful when you use local mail and news.
13953 @subsubsection Function Interface
13955 Some of the above keywords specify a Lisp function to be executed.
13956 For each keyword @code{:foo}, the Lisp variable @code{foo} is bound to
13957 the value of the keyword while the function is executing. For example,
13958 consider the following mail-source setting:
13961 (setq mail-sources '((pop :user "jrl"
13962 :server "pophost" :function fetchfunc)))
13965 While the function @code{fetchfunc} is executing, the symbol @code{user}
13966 is bound to @code{"jrl"}, and the symbol @code{server} is bound to
13967 @code{"pophost"}. The symbols @code{port}, @code{password},
13968 @code{program}, @code{prescript}, @code{postscript}, @code{function},
13969 and @code{authentication} are also bound (to their default values).
13971 See above for a list of keywords for each type of mail source.
13974 @node Mail Source Customization
13975 @subsubsection Mail Source Customization
13977 The following is a list of variables that influence how the mail is
13978 fetched. You would normally not need to set or change any of these
13982 @item mail-source-crash-box
13983 @vindex mail-source-crash-box
13984 File where mail will be stored while processing it. The default is@*
13985 @file{~/.emacs-mail-crash-box}.
13987 @item mail-source-delete-incoming
13988 @vindex mail-source-delete-incoming
13989 If non-@code{nil}, delete incoming files after handling them. If
13990 @code{t}, delete the files immediately, if @code{nil}, never delete any
13991 files. If a positive number, delete files older than number of days
13992 (This will only happen, when receiving new mail). You may also set
13993 @code{mail-source-delete-incoming} to @code{nil} and call
13994 @code{mail-source-delete-old-incoming} from a hook or interactively.
13996 @item mail-source-delete-old-incoming-confirm
13997 @vindex mail-source-delete-old-incoming-confirm
13998 If non-@code{nil}, ask for for confirmation before deleting old incoming
13999 files. This variable only applies when
14000 @code{mail-source-delete-incoming} is a positive number.
14002 @item mail-source-ignore-errors
14003 @vindex mail-source-ignore-errors
14004 If non-@code{nil}, ignore errors when reading mail from a mail source.
14006 @item mail-source-directory
14007 @vindex mail-source-directory
14008 Directory where incoming mail source files (if any) will be stored. The
14009 default is @file{~/Mail/}. At present, the only thing this is used for
14010 is to say where the incoming files will be stored if the variable
14011 @code{mail-source-delete-incoming} is @code{nil} or a number.
14013 @item mail-source-incoming-file-prefix
14014 @vindex mail-source-incoming-file-prefix
14015 Prefix for file name for storing incoming mail. The default is
14016 @file{Incoming}, in which case files will end up with names like
14017 @file{Incoming30630D_} or @file{Incoming298602ZD}. This is really only
14018 relevant if @code{mail-source-delete-incoming} is @code{nil}.
14020 @item mail-source-default-file-modes
14021 @vindex mail-source-default-file-modes
14022 All new mail files will get this file mode. The default is 384.
14024 @item mail-source-movemail-program
14025 @vindex mail-source-movemail-program
14026 If non-@code{nil}, name of program for fetching new mail. If
14027 @code{nil}, @code{movemail} in @var{exec-directory}.
14032 @node Fetching Mail
14033 @subsubsection Fetching Mail
14035 @vindex mail-sources
14036 @vindex nnmail-spool-file
14037 The way to actually tell Gnus where to get new mail from is to set
14038 @code{mail-sources} to a list of mail source specifiers
14039 (@pxref{Mail Source Specifiers}).
14041 If this variable (and the obsolescent @code{nnmail-spool-file}) is
14042 @code{nil}, the mail back ends will never attempt to fetch mail by
14045 If you want to fetch mail both from your local spool as well as a
14046 @acronym{POP} mail server, you'd say something like:
14051 (pop :server "pop3.mail.server"
14052 :password "secret")))
14055 Or, if you don't want to use any of the keyword defaults:
14059 '((file :path "/var/spool/mail/user-name")
14060 (pop :server "pop3.mail.server"
14063 :password "secret")))
14067 When you use a mail back end, Gnus will slurp all your mail from your
14068 inbox and plonk it down in your home directory. Gnus doesn't move any
14069 mail if you're not using a mail back end---you have to do a lot of magic
14070 invocations first. At the time when you have finished drawing the
14071 pentagram, lightened the candles, and sacrificed the goat, you really
14072 shouldn't be too surprised when Gnus moves your mail.
14076 @node Mail Back End Variables
14077 @subsection Mail Back End Variables
14079 These variables are (for the most part) pertinent to all the various
14083 @vindex nnmail-read-incoming-hook
14084 @item nnmail-read-incoming-hook
14085 The mail back ends all call this hook after reading new mail. You can
14086 use this hook to notify any mail watch programs, if you want to.
14088 @vindex nnmail-split-hook
14089 @item nnmail-split-hook
14090 @findex gnus-article-decode-encoded-words
14091 @cindex RFC 1522 decoding
14092 @cindex RFC 2047 decoding
14093 Hook run in the buffer where the mail headers of each message is kept
14094 just before the splitting based on these headers is done. The hook is
14095 free to modify the buffer contents in any way it sees fit---the buffer
14096 is discarded after the splitting has been done, and no changes performed
14097 in the buffer will show up in any files.
14098 @code{gnus-article-decode-encoded-words} is one likely function to add
14101 @vindex nnmail-pre-get-new-mail-hook
14102 @vindex nnmail-post-get-new-mail-hook
14103 @item nnmail-pre-get-new-mail-hook
14104 @itemx nnmail-post-get-new-mail-hook
14105 These are two useful hooks executed when treating new incoming
14106 mail---@code{nnmail-pre-get-new-mail-hook} (is called just before
14107 starting to handle the new mail) and
14108 @code{nnmail-post-get-new-mail-hook} (is called when the mail handling
14109 is done). Here's and example of using these two hooks to change the
14110 default file modes the new mail files get:
14113 (add-hook 'nnmail-pre-get-new-mail-hook
14114 (lambda () (set-default-file-modes 511)))
14116 (add-hook 'nnmail-post-get-new-mail-hook
14117 (lambda () (set-default-file-modes 551)))
14120 @item nnmail-use-long-file-names
14121 @vindex nnmail-use-long-file-names
14122 If non-@code{nil}, the mail back ends will use long file and directory
14123 names. Groups like @samp{mail.misc} will end up in directories
14124 (assuming use of @code{nnml} back end) or files (assuming use of
14125 @code{nnfolder} back end) like @file{mail.misc}. If it is @code{nil},
14126 the same group will end up in @file{mail/misc}.
14128 @item nnmail-delete-file-function
14129 @vindex nnmail-delete-file-function
14130 @findex delete-file
14131 Function called to delete files. It is @code{delete-file} by default.
14133 @item nnmail-cache-accepted-message-ids
14134 @vindex nnmail-cache-accepted-message-ids
14135 If non-@code{nil}, put the @code{Message-ID}s of articles imported into
14136 the back end (via @code{Gcc}, for instance) into the mail duplication
14137 discovery cache. The default is @code{nil}.
14139 @item nnmail-cache-ignore-groups
14140 @vindex nnmail-cache-ignore-groups
14141 This can be a regular expression or a list of regular expressions.
14142 Group names that match any of the regular expressions will never be
14143 recorded in the @code{Message-ID} cache.
14145 This can be useful, for example, when using Fancy Splitting
14146 (@pxref{Fancy Mail Splitting}) together with the function
14147 @code{nnmail-split-fancy-with-parent}.
14152 @node Fancy Mail Splitting
14153 @subsection Fancy Mail Splitting
14154 @cindex mail splitting
14155 @cindex fancy mail splitting
14157 @vindex nnmail-split-fancy
14158 @findex nnmail-split-fancy
14159 If the rather simple, standard method for specifying how to split mail
14160 doesn't allow you to do what you want, you can set
14161 @code{nnmail-split-methods} to @code{nnmail-split-fancy}. Then you can
14162 play with the @code{nnmail-split-fancy} variable.
14164 Let's look at an example value of this variable first:
14167 ;; @r{Messages from the mailer daemon are not crossposted to any of}
14168 ;; @r{the ordinary groups. Warnings are put in a separate group}
14169 ;; @r{from real errors.}
14170 (| ("from" mail (| ("subject" "warn.*" "mail.warning")
14172 ;; @r{Non-error messages are crossposted to all relevant}
14173 ;; @r{groups, but we don't crosspost between the group for the}
14174 ;; @r{(ding) list and the group for other (ding) related mail.}
14175 (& (| (any "ding@@ifi\\.uio\\.no" "ding.list")
14176 ("subject" "ding" "ding.misc"))
14177 ;; @r{Other mailing lists@dots{}}
14178 (any "procmail@@informatik\\.rwth-aachen\\.de" "procmail.list")
14179 (any "SmartList@@informatik\\.rwth-aachen\\.de" "SmartList.list")
14180 ;; @r{Both lists below have the same suffix, so prevent}
14181 ;; @r{cross-posting to mkpkg.list of messages posted only to}
14182 ;; @r{the bugs- list, but allow cross-posting when the}
14183 ;; @r{message was really cross-posted.}
14184 (any "bugs-mypackage@@somewhere" "mypkg.bugs")
14185 (any "mypackage@@somewhere" - "bugs-mypackage" "mypkg.list")
14186 ;; @r{People@dots{}}
14187 (any "larsi@@ifi\\.uio\\.no" "people.Lars_Magne_Ingebrigtsen"))
14188 ;; @r{Unmatched mail goes to the catch all group.}
14192 This variable has the format of a @dfn{split}. A split is a
14193 (possibly) recursive structure where each split may contain other
14194 splits. Here are the possible split syntaxes:
14199 If the split is a string, that will be taken as a group name. Normal
14200 regexp match expansion will be done. See below for examples.
14202 @item (@var{field} @var{value} [- @var{restrict} [@dots{}] ] @var{split})
14203 If the split is a list, the first element of which is a string, then
14204 store the message as specified by @var{split}, if header @var{field}
14205 (a regexp) contains @var{value} (also a regexp). If @var{restrict}
14206 (yet another regexp) matches some string after @var{field} and before
14207 the end of the matched @var{value}, the @var{split} is ignored. If
14208 none of the @var{restrict} clauses match, @var{split} is processed.
14210 @item (| @var{split} @dots{})
14211 If the split is a list, and the first element is @code{|} (vertical
14212 bar), then process each @var{split} until one of them matches. A
14213 @var{split} is said to match if it will cause the mail message to be
14214 stored in one or more groups.
14216 @item (& @var{split} @dots{})
14217 If the split is a list, and the first element is @code{&}, then
14218 process all @var{split}s in the list.
14221 If the split is the symbol @code{junk}, then don't save (i.e., delete)
14222 this message. Use with extreme caution.
14224 @item (: @var{function} @var{arg1} @var{arg2} @dots{})
14225 If the split is a list, and the first element is @samp{:}, then the
14226 second element will be called as a function with @var{args} given as
14227 arguments. The function should return a @var{split}.
14230 For instance, the following function could be used to split based on the
14231 body of the messages:
14234 (defun split-on-body ()
14238 (goto-char (point-min))
14239 (when (re-search-forward "Some.*string" nil t)
14243 The buffer is narrowed to the message in question when @var{function}
14244 is run. That's why @code{(widen)} needs to be called after
14245 @code{save-excursion} and @code{save-restriction} in the example
14246 above. Also note that with the nnimap back end, message bodies will
14247 not be downloaded by default. You need to set
14248 @code{nnimap-split-download-body} to @code{t} to do that
14249 (@pxref{Splitting in IMAP}).
14251 @item (! @var{func} @var{split})
14252 If the split is a list, and the first element is @code{!}, then
14253 @var{split} will be processed, and @var{func} will be called as a
14254 function with the result of @var{split} as argument. @var{func}
14255 should return a split.
14258 If the split is @code{nil}, it is ignored.
14262 In these splits, @var{field} must match a complete field name.
14263 @var{value} must match a complete word according to the fundamental mode
14264 syntax table. You can use @code{.*} in the regexps to match partial
14265 field names or words. In other words, all @var{value}'s are wrapped in
14266 @samp{\<} and @samp{\>} pairs.
14268 @vindex nnmail-split-abbrev-alist
14269 @var{field} and @var{value} can also be Lisp symbols, in that case
14270 they are expanded as specified by the variable
14271 @code{nnmail-split-abbrev-alist}. This is an alist of cons cells,
14272 where the @sc{car} of a cell contains the key, and the @sc{cdr}
14273 contains the associated value. Predefined entries in
14274 @code{nnmail-split-abbrev-alist} include:
14278 Matches the @samp{From}, @samp{Sender} and @samp{Resent-From} fields.
14280 Matches the @samp{To}, @samp{Cc}, @samp{Apparently-To},
14281 @samp{Resent-To} and @samp{Resent-Cc} fields.
14283 Is the union of the @code{from} and @code{to} entries.
14286 @vindex nnmail-split-fancy-syntax-table
14287 @code{nnmail-split-fancy-syntax-table} is the syntax table in effect
14288 when all this splitting is performed.
14290 If you want to have Gnus create groups dynamically based on some
14291 information in the headers (i.e., do @code{replace-match}-like
14292 substitutions in the group names), you can say things like:
14295 (any "debian-\\b\\(\\w+\\)@@lists.debian.org" "mail.debian.\\1")
14298 In this example, messages sent to @samp{debian-foo@@lists.debian.org}
14299 will be filed in @samp{mail.debian.foo}.
14301 If the string contains the element @samp{\&}, then the previously
14302 matched string will be substituted. Similarly, the elements @samp{\\1}
14303 up to @samp{\\9} will be substituted with the text matched by the
14304 groupings 1 through 9.
14306 @vindex nnmail-split-lowercase-expanded
14307 Where @code{nnmail-split-lowercase-expanded} controls whether the
14308 lowercase of the matched string should be used for the substitution.
14309 Setting it as non-@code{nil} is useful to avoid the creation of multiple
14310 groups when users send to an address using different case
14311 (i.e. mailing-list@@domain vs Mailing-List@@Domain). The default value
14314 @vindex nnmail-split-fancy-match-partial-words
14315 @code{nnmail-split-fancy-match-partial-words} controls whether partial
14316 words are matched during fancy splitting.
14318 Normally, regular expressions given in @code{nnmail-split-fancy} are
14319 implicitly surrounded by @code{\<...\>} markers, which are word
14320 delimiters. If this variable is true, they are not implicitly
14321 surrounded by anything.
14324 (any "joe" "joemail")
14327 In this example, messages sent from @samp{joedavis@@foo.org} will
14328 normally not be filed in @samp{joemail}. With
14329 @code{nnmail-split-fancy-match-partial-words} set to @code{t},
14330 however, the match will happen. In effect, the requirement of a word
14331 boundary is removed and instead the match becomes more like a grep.
14333 @findex nnmail-split-fancy-with-parent
14334 @code{nnmail-split-fancy-with-parent} is a function which allows you to
14335 split followups into the same groups their parents are in. Sometimes
14336 you can't make splitting rules for all your mail. For example, your
14337 boss might send you personal mail regarding different projects you are
14338 working on, and as you can't tell your boss to put a distinguishing
14339 string into the subject line, you have to resort to manually moving the
14340 messages into the right group. With this function, you only have to do
14341 it once per thread.
14343 To use this feature, you have to set @code{nnmail-treat-duplicates}
14344 and @code{nnmail-cache-accepted-message-ids} to a non-@code{nil}
14345 value. And then you can include @code{nnmail-split-fancy-with-parent}
14346 using the colon feature, like so:
14348 (setq nnmail-treat-duplicates 'warn ; @r{or @code{delete}}
14349 nnmail-cache-accepted-message-ids t
14351 '(| (: nnmail-split-fancy-with-parent)
14352 ;; @r{other splits go here}
14356 This feature works as follows: when @code{nnmail-treat-duplicates} is
14357 non-@code{nil}, Gnus records the message id of every message it sees
14358 in the file specified by the variable
14359 @code{nnmail-message-id-cache-file}, together with the group it is in
14360 (the group is omitted for non-mail messages). When mail splitting is
14361 invoked, the function @code{nnmail-split-fancy-with-parent} then looks
14362 at the References (and In-Reply-To) header of each message to split
14363 and searches the file specified by @code{nnmail-message-id-cache-file}
14364 for the message ids. When it has found a parent, it returns the
14365 corresponding group name unless the group name matches the regexp
14366 @code{nnmail-split-fancy-with-parent-ignore-groups}. It is
14367 recommended that you set @code{nnmail-message-id-cache-length} to a
14368 somewhat higher number than the default so that the message ids are
14369 still in the cache. (A value of 5000 appears to create a file some
14370 300 kBytes in size.)
14371 @vindex nnmail-cache-accepted-message-ids
14372 When @code{nnmail-cache-accepted-message-ids} is non-@code{nil}, Gnus
14373 also records the message ids of moved articles, so that the followup
14374 messages goes into the new group.
14376 Also see the variable @code{nnmail-cache-ignore-groups} if you don't
14377 want certain groups to be recorded in the cache. For example, if all
14378 outgoing messages are written to an ``outgoing'' group, you could set
14379 @code{nnmail-cache-ignore-groups} to match that group name.
14380 Otherwise, answers to all your messages would end up in the
14381 ``outgoing'' group.
14384 @node Group Mail Splitting
14385 @subsection Group Mail Splitting
14386 @cindex mail splitting
14387 @cindex group mail splitting
14389 @findex gnus-group-split
14390 If you subscribe to dozens of mailing lists but you don't want to
14391 maintain mail splitting rules manually, group mail splitting is for you.
14392 You just have to set @code{to-list} and/or @code{to-address} in group
14393 parameters or group customization and set @code{nnmail-split-methods} to
14394 @code{gnus-group-split}. This splitting function will scan all groups
14395 for those parameters and split mail accordingly, i.e., messages posted
14396 from or to the addresses specified in the parameters @code{to-list} or
14397 @code{to-address} of a mail group will be stored in that group.
14399 Sometimes, mailing lists have multiple addresses, and you may want mail
14400 splitting to recognize them all: just set the @code{extra-aliases} group
14401 parameter to the list of additional addresses and it's done. If you'd
14402 rather use a regular expression, set @code{split-regexp}.
14404 All these parameters in a group will be used to create an
14405 @code{nnmail-split-fancy} split, in which the @var{field} is @samp{any},
14406 the @var{value} is a single regular expression that matches
14407 @code{to-list}, @code{to-address}, all of @code{extra-aliases} and all
14408 matches of @code{split-regexp}, and the @var{split} is the name of the
14409 group. @var{restrict}s are also supported: just set the
14410 @code{split-exclude} parameter to a list of regular expressions.
14412 If you can't get the right split to be generated using all these
14413 parameters, or you just need something fancier, you can set the
14414 parameter @code{split-spec} to an @code{nnmail-split-fancy} split. In
14415 this case, all other aforementioned parameters will be ignored by
14416 @code{gnus-group-split}. In particular, @code{split-spec} may be set to
14417 @code{nil}, in which case the group will be ignored by
14418 @code{gnus-group-split}.
14420 @vindex gnus-group-split-default-catch-all-group
14421 @code{gnus-group-split} will do cross-posting on all groups that match,
14422 by defining a single @code{&} fancy split containing one split for each
14423 group. If a message doesn't match any split, it will be stored in the
14424 group named in @code{gnus-group-split-default-catch-all-group}, unless
14425 some group has @code{split-spec} set to @code{catch-all}, in which case
14426 that group is used as the catch-all group. Even though this variable is
14427 often used just to name a group, it may also be set to an arbitrarily
14428 complex fancy split (after all, a group name is a fancy split), and this
14429 may be useful to split mail that doesn't go to any mailing list to
14430 personal mail folders. Note that this fancy split is added as the last
14431 element of a @code{|} split list that also contains a @code{&} split
14432 with the rules extracted from group parameters.
14434 It's time for an example. Assume the following group parameters have
14439 ((to-address . "bar@@femail.com")
14440 (split-regexp . ".*@@femail\\.com"))
14442 ((to-list . "foo@@nowhere.gov")
14443 (extra-aliases "foo@@localhost" "foo-redist@@home")
14444 (split-exclude "bugs-foo" "rambling-foo")
14445 (admin-address . "foo-request@@nowhere.gov"))
14447 ((split-spec . catch-all))
14450 Setting @code{nnmail-split-methods} to @code{gnus-group-split} will
14451 behave as if @code{nnmail-split-fancy} had been selected and variable
14452 @code{nnmail-split-fancy} had been set as follows:
14455 (| (& (any "\\(bar@@femail\\.com\\|.*@@femail\\.com\\)" "mail.bar")
14456 (any "\\(foo@@nowhere\\.gov\\|foo@@localhost\\|foo-redist@@home\\)"
14457 - "bugs-foo" - "rambling-foo" "mail.foo"))
14461 @findex gnus-group-split-fancy
14462 If you'd rather not use group splitting for all your mail groups, you
14463 may use it for only some of them, by using @code{nnmail-split-fancy}
14467 (: gnus-group-split-fancy @var{groups} @var{no-crosspost} @var{catch-all})
14470 @var{groups} may be a regular expression or a list of group names whose
14471 parameters will be scanned to generate the output split.
14472 @var{no-crosspost} can be used to disable cross-posting; in this case, a
14473 single @code{|} split will be output. @var{catch-all} is the fall back
14474 fancy split, used like @code{gnus-group-split-default-catch-all-group}.
14475 If @var{catch-all} is @code{nil}, or if @code{split-regexp} matches the
14476 empty string in any selected group, no catch-all split will be issued.
14477 Otherwise, if some group has @code{split-spec} set to @code{catch-all},
14478 this group will override the value of the @var{catch-all} argument.
14480 @findex gnus-group-split-setup
14481 Unfortunately, scanning all groups and their parameters can be quite
14482 slow, especially considering that it has to be done for every message.
14483 But don't despair! The function @code{gnus-group-split-setup} can be
14484 used to enable @code{gnus-group-split} in a much more efficient way. It
14485 sets @code{nnmail-split-methods} to @code{nnmail-split-fancy} and sets
14486 @code{nnmail-split-fancy} to the split produced by
14487 @code{gnus-group-split-fancy}. Thus, the group parameters are only
14488 scanned once, no matter how many messages are split.
14490 @findex gnus-group-split-update
14491 However, if you change group parameters, you'd have to update
14492 @code{nnmail-split-fancy} manually. You can do it by running
14493 @code{gnus-group-split-update}. If you'd rather have it updated
14494 automatically, just tell @code{gnus-group-split-setup} to do it for
14495 you. For example, add to your @file{~/.gnus.el}:
14498 (gnus-group-split-setup @var{auto-update} @var{catch-all})
14501 If @var{auto-update} is non-@code{nil}, @code{gnus-group-split-update}
14502 will be added to @code{nnmail-pre-get-new-mail-hook}, so you won't ever
14503 have to worry about updating @code{nnmail-split-fancy} again. If you
14504 don't omit @var{catch-all} (it's optional, equivalent to @code{nil}),
14505 @code{gnus-group-split-default-catch-all-group} will be set to its
14508 @vindex gnus-group-split-updated-hook
14509 Because you may want to change @code{nnmail-split-fancy} after it is set
14510 by @code{gnus-group-split-update}, this function will run
14511 @code{gnus-group-split-updated-hook} just before finishing.
14513 @node Incorporating Old Mail
14514 @subsection Incorporating Old Mail
14515 @cindex incorporating old mail
14516 @cindex import old mail
14518 Most people have lots of old mail stored in various file formats. If
14519 you have set up Gnus to read mail using one of the spiffy Gnus mail
14520 back ends, you'll probably wish to have that old mail incorporated into
14523 Doing so can be quite easy.
14525 To take an example: You're reading mail using @code{nnml}
14526 (@pxref{Mail Spool}), and have set @code{nnmail-split-methods} to a
14527 satisfactory value (@pxref{Splitting Mail}). You have an old Unix mbox
14528 file filled with important, but old, mail. You want to move it into
14529 your @code{nnml} groups.
14535 Go to the group buffer.
14538 Type @kbd{G f} and give the file name to the mbox file when prompted to create an
14539 @code{nndoc} group from the mbox file (@pxref{Foreign Groups}).
14542 Type @kbd{SPACE} to enter the newly created group.
14545 Type @kbd{M P b} to process-mark all articles in this group's buffer
14546 (@pxref{Setting Process Marks}).
14549 Type @kbd{B r} to respool all the process-marked articles, and answer
14550 @samp{nnml} when prompted (@pxref{Mail Group Commands}).
14553 All the mail messages in the mbox file will now also be spread out over
14554 all your @code{nnml} groups. Try entering them and check whether things
14555 have gone without a glitch. If things look ok, you may consider
14556 deleting the mbox file, but I wouldn't do that unless I was absolutely
14557 sure that all the mail has ended up where it should be.
14559 Respooling is also a handy thing to do if you're switching from one mail
14560 back end to another. Just respool all the mail in the old mail groups
14561 using the new mail back end.
14564 @node Expiring Mail
14565 @subsection Expiring Mail
14566 @cindex article expiry
14568 Traditional mail readers have a tendency to remove mail articles when
14569 you mark them as read, in some way. Gnus takes a fundamentally
14570 different approach to mail reading.
14572 Gnus basically considers mail just to be news that has been received in
14573 a rather peculiar manner. It does not think that it has the power to
14574 actually change the mail, or delete any mail messages. If you enter a
14575 mail group, and mark articles as ``read'', or kill them in some other
14576 fashion, the mail articles will still exist on the system. I repeat:
14577 Gnus will not delete your old, read mail. Unless you ask it to, of
14580 To make Gnus get rid of your unwanted mail, you have to mark the
14581 articles as @dfn{expirable}. (With the default key bindings, this means
14582 that you have to type @kbd{E}.) This does not mean that the articles
14583 will disappear right away, however. In general, a mail article will be
14584 deleted from your system if, 1) it is marked as expirable, AND 2) it is
14585 more than one week old. If you do not mark an article as expirable, it
14586 will remain on your system until hell freezes over. This bears
14587 repeating one more time, with some spurious capitalizations: IF you do
14588 NOT mark articles as EXPIRABLE, Gnus will NEVER delete those ARTICLES.
14590 You do not have to mark articles as expirable by hand. Gnus provides
14591 two features, called ``auto-expire'' and ``total-expire'', that can help you
14592 with this. In a nutshell, ``auto-expire'' means that Gnus hits @kbd{E}
14593 for you when you select an article. And ``total-expire'' means that Gnus
14594 considers all articles as expirable that are read. So, in addition to
14595 the articles marked @samp{E}, also the articles marked @samp{r},
14596 @samp{R}, @samp{O}, @samp{K}, @samp{Y} and so on are considered
14599 When should either auto-expire or total-expire be used? Most people
14600 who are subscribed to mailing lists split each list into its own group
14601 and then turn on auto-expire or total-expire for those groups.
14602 (@xref{Splitting Mail}, for more information on splitting each list
14603 into its own group.)
14605 Which one is better, auto-expire or total-expire? It's not easy to
14606 answer. Generally speaking, auto-expire is probably faster. Another
14607 advantage of auto-expire is that you get more marks to work with: for
14608 the articles that are supposed to stick around, you can still choose
14609 between tick and dormant and read marks. But with total-expire, you
14610 only have dormant and ticked to choose from. The advantage of
14611 total-expire is that it works well with adaptive scoring (@pxref{Adaptive
14612 Scoring}). Auto-expire works with normal scoring but not with adaptive
14615 @vindex gnus-auto-expirable-newsgroups
14616 Groups that match the regular expression
14617 @code{gnus-auto-expirable-newsgroups} will have all articles that you
14618 read marked as expirable automatically. All articles marked as
14619 expirable have an @samp{E} in the first column in the summary buffer.
14621 By default, if you have auto expiry switched on, Gnus will mark all the
14622 articles you read as expirable, no matter if they were read or unread
14623 before. To avoid having articles marked as read marked as expirable
14624 automatically, you can put something like the following in your
14625 @file{~/.gnus.el} file:
14627 @vindex gnus-mark-article-hook
14629 (remove-hook 'gnus-mark-article-hook
14630 'gnus-summary-mark-read-and-unread-as-read)
14631 (add-hook 'gnus-mark-article-hook 'gnus-summary-mark-unread-as-read)
14634 Note that making a group auto-expirable doesn't mean that all read
14635 articles are expired---only the articles marked as expirable
14636 will be expired. Also note that using the @kbd{d} command won't make
14637 articles expirable---only semi-automatic marking of articles as read will
14638 mark the articles as expirable in auto-expirable groups.
14640 Let's say you subscribe to a couple of mailing lists, and you want the
14641 articles you have read to disappear after a while:
14644 (setq gnus-auto-expirable-newsgroups
14645 "mail.nonsense-list\\|mail.nice-list")
14648 Another way to have auto-expiry happen is to have the element
14649 @code{auto-expire} in the group parameters of the group.
14651 If you use adaptive scoring (@pxref{Adaptive Scoring}) and
14652 auto-expiring, you'll have problems. Auto-expiring and adaptive scoring
14653 don't really mix very well.
14655 @vindex nnmail-expiry-wait
14656 The @code{nnmail-expiry-wait} variable supplies the default time an
14657 expirable article has to live. Gnus starts counting days from when the
14658 message @emph{arrived}, not from when it was sent. The default is seven
14661 Gnus also supplies a function that lets you fine-tune how long articles
14662 are to live, based on what group they are in. Let's say you want to
14663 have one month expiry period in the @samp{mail.private} group, a one day
14664 expiry period in the @samp{mail.junk} group, and a six day expiry period
14667 @vindex nnmail-expiry-wait-function
14669 (setq nnmail-expiry-wait-function
14671 (cond ((string= group "mail.private")
14673 ((string= group "mail.junk")
14675 ((string= group "important")
14681 The group names this function is fed are ``unadorned'' group
14682 names---no @samp{nnml:} prefixes and the like.
14684 The @code{nnmail-expiry-wait} variable and
14685 @code{nnmail-expiry-wait-function} function can either be a number (not
14686 necessarily an integer) or one of the symbols @code{immediate} or
14689 You can also use the @code{expiry-wait} group parameter to selectively
14690 change the expiry period (@pxref{Group Parameters}).
14692 @vindex nnmail-expiry-target
14693 The normal action taken when expiring articles is to delete them.
14694 However, in some circumstances it might make more sense to move them
14695 to other groups instead of deleting them. The variable
14696 @code{nnmail-expiry-target} (and the @code{expiry-target} group
14697 parameter) controls this. The variable supplies a default value for
14698 all groups, which can be overridden for specific groups by the group
14699 parameter. default value is @code{delete}, but this can also be a
14700 string (which should be the name of the group the message should be
14701 moved to), or a function (which will be called in a buffer narrowed to
14702 the message in question, and with the name of the group being moved
14703 from as its parameter) which should return a target---either a group
14704 name or @code{delete}.
14706 Here's an example for specifying a group name:
14708 (setq nnmail-expiry-target "nnml:expired")
14711 @findex nnmail-fancy-expiry-target
14712 @vindex nnmail-fancy-expiry-targets
14713 Gnus provides a function @code{nnmail-fancy-expiry-target} which will
14714 expire mail to groups according to the variable
14715 @code{nnmail-fancy-expiry-targets}. Here's an example:
14718 (setq nnmail-expiry-target 'nnmail-fancy-expiry-target
14719 nnmail-fancy-expiry-targets
14720 '((to-from "boss" "nnfolder:Work")
14721 ("subject" "IMPORTANT" "nnfolder:IMPORTANT.%Y.%b")
14722 ("from" ".*" "nnfolder:Archive-%Y")))
14725 With this setup, any mail that has @code{IMPORTANT} in its Subject
14726 header and was sent in the year @code{YYYY} and month @code{MMM}, will
14727 get expired to the group @code{nnfolder:IMPORTANT.YYYY.MMM}. If its
14728 From or To header contains the string @code{boss}, it will get expired
14729 to @code{nnfolder:Work}. All other mail will get expired to
14730 @code{nnfolder:Archive-YYYY}.
14732 @vindex nnmail-keep-last-article
14733 If @code{nnmail-keep-last-article} is non-@code{nil}, Gnus will never
14734 expire the final article in a mail newsgroup. This is to make life
14735 easier for procmail users.
14737 @vindex gnus-total-expirable-newsgroups
14738 By the way: That line up there, about Gnus never expiring non-expirable
14739 articles, is a lie. If you put @code{total-expire} in the group
14740 parameters, articles will not be marked as expirable, but all read
14741 articles will be put through the expiry process. Use with extreme
14742 caution. Even more dangerous is the
14743 @code{gnus-total-expirable-newsgroups} variable. All groups that match
14744 this regexp will have all read articles put through the expiry process,
14745 which means that @emph{all} old mail articles in the groups in question
14746 will be deleted after a while. Use with extreme caution, and don't come
14747 crying to me when you discover that the regexp you used matched the
14748 wrong group and all your important mail has disappeared. Be a
14749 @emph{man}! Or a @emph{woman}! Whatever you feel more comfortable
14752 Most people make most of their mail groups total-expirable, though.
14754 @vindex gnus-inhibit-user-auto-expire
14755 If @code{gnus-inhibit-user-auto-expire} is non-@code{nil}, user marking
14756 commands will not mark an article as expirable, even if the group has
14757 auto-expire turned on.
14761 @subsection Washing Mail
14762 @cindex mail washing
14763 @cindex list server brain damage
14764 @cindex incoming mail treatment
14766 Mailers and list servers are notorious for doing all sorts of really,
14767 really stupid things with mail. ``Hey, RFC 822 doesn't explicitly
14768 prohibit us from adding the string @code{wE aRe ElItE!!!!!1!!} to the
14769 end of all lines passing through our server, so let's do that!!!!1!''
14770 Yes, but RFC 822 wasn't designed to be read by morons. Things that were
14771 considered to be self-evident were not discussed. So. Here we are.
14773 Case in point: The German version of Microsoft Exchange adds @samp{AW:
14774 } to the subjects of replies instead of @samp{Re: }. I could pretend to
14775 be shocked and dismayed by this, but I haven't got the energy. It is to
14778 Gnus provides a plethora of functions for washing articles while
14779 displaying them, but it might be nicer to do the filtering before
14780 storing the mail to disk. For that purpose, we have three hooks and
14781 various functions that can be put in these hooks.
14784 @item nnmail-prepare-incoming-hook
14785 @vindex nnmail-prepare-incoming-hook
14786 This hook is called before doing anything with the mail and is meant for
14787 grand, sweeping gestures. It is called in a buffer that contains all
14788 the new, incoming mail. Functions to be used include:
14791 @item nnheader-ms-strip-cr
14792 @findex nnheader-ms-strip-cr
14793 Remove trailing carriage returns from each line. This is default on
14794 Emacs running on MS machines.
14798 @item nnmail-prepare-incoming-header-hook
14799 @vindex nnmail-prepare-incoming-header-hook
14800 This hook is called narrowed to each header. It can be used when
14801 cleaning up the headers. Functions that can be used include:
14804 @item nnmail-remove-leading-whitespace
14805 @findex nnmail-remove-leading-whitespace
14806 Clear leading white space that ``helpful'' listservs have added to the
14807 headers to make them look nice. Aaah.
14809 (Note that this function works on both the header on the body of all
14810 messages, so it is a potentially dangerous function to use (if a body
14811 of a message contains something that looks like a header line). So
14812 rather than fix the bug, it is of course the right solution to make it
14813 into a feature by documenting it.)
14815 @item nnmail-remove-list-identifiers
14816 @findex nnmail-remove-list-identifiers
14817 Some list servers add an identifier---for example, @samp{(idm)}---to the
14818 beginning of all @code{Subject} headers. I'm sure that's nice for
14819 people who use stone age mail readers. This function will remove
14820 strings that match the @code{nnmail-list-identifiers} regexp, which can
14821 also be a list of regexp. @code{nnmail-list-identifiers} may not contain
14824 For instance, if you want to remove the @samp{(idm)} and the
14825 @samp{nagnagnag} identifiers:
14828 (setq nnmail-list-identifiers
14829 '("(idm)" "nagnagnag"))
14832 This can also be done non-destructively with
14833 @code{gnus-list-identifiers}, @xref{Article Hiding}.
14835 @item nnmail-remove-tabs
14836 @findex nnmail-remove-tabs
14837 Translate all @samp{TAB} characters into @samp{SPACE} characters.
14839 @item nnmail-fix-eudora-headers
14840 @findex nnmail-fix-eudora-headers
14842 Eudora produces broken @code{References} headers, but OK
14843 @code{In-Reply-To} headers. This function will get rid of the
14844 @code{References} headers.
14848 @item nnmail-prepare-incoming-message-hook
14849 @vindex nnmail-prepare-incoming-message-hook
14850 This hook is called narrowed to each message. Functions to be used
14854 @item article-de-quoted-unreadable
14855 @findex article-de-quoted-unreadable
14856 Decode Quoted Readable encoding.
14863 @subsection Duplicates
14865 @vindex nnmail-treat-duplicates
14866 @vindex nnmail-message-id-cache-length
14867 @vindex nnmail-message-id-cache-file
14868 @cindex duplicate mails
14869 If you are a member of a couple of mailing lists, you will sometimes
14870 receive two copies of the same mail. This can be quite annoying, so
14871 @code{nnmail} checks for and treats any duplicates it might find. To do
14872 this, it keeps a cache of old @code{Message-ID}s---
14873 @code{nnmail-message-id-cache-file}, which is @file{~/.nnmail-cache} by
14874 default. The approximate maximum number of @code{Message-ID}s stored
14875 there is controlled by the @code{nnmail-message-id-cache-length}
14876 variable, which is 1000 by default. (So 1000 @code{Message-ID}s will be
14877 stored.) If all this sounds scary to you, you can set
14878 @code{nnmail-treat-duplicates} to @code{warn} (which is what it is by
14879 default), and @code{nnmail} won't delete duplicate mails. Instead it
14880 will insert a warning into the head of the mail saying that it thinks
14881 that this is a duplicate of a different message.
14883 This variable can also be a function. If that's the case, the function
14884 will be called from a buffer narrowed to the message in question with
14885 the @code{Message-ID} as a parameter. The function must return either
14886 @code{nil}, @code{warn}, or @code{delete}.
14888 You can turn this feature off completely by setting the variable to
14891 If you want all the duplicate mails to be put into a special
14892 @dfn{duplicates} group, you could do that using the normal mail split
14896 (setq nnmail-split-fancy
14897 '(| ;; @r{Messages duplicates go to a separate group.}
14898 ("gnus-warning" "duplicat\\(e\\|ion\\) of message" "duplicate")
14899 ;; @r{Message from daemons, postmaster, and the like to another.}
14900 (any mail "mail.misc")
14901 ;; @r{Other rules.}
14907 (setq nnmail-split-methods
14908 '(("duplicates" "^Gnus-Warning:.*duplicate")
14909 ;; @r{Other rules.}
14913 Here's a neat feature: If you know that the recipient reads her mail
14914 with Gnus, and that she has @code{nnmail-treat-duplicates} set to
14915 @code{delete}, you can send her as many insults as you like, just by
14916 using a @code{Message-ID} of a mail that you know that she's already
14917 received. Think of all the fun! She'll never see any of it! Whee!
14920 @node Not Reading Mail
14921 @subsection Not Reading Mail
14923 If you start using any of the mail back ends, they have the annoying
14924 habit of assuming that you want to read mail with them. This might not
14925 be unreasonable, but it might not be what you want.
14927 If you set @code{mail-sources} and @code{nnmail-spool-file} to
14928 @code{nil}, none of the back ends will ever attempt to read incoming
14929 mail, which should help.
14931 @vindex nnbabyl-get-new-mail
14932 @vindex nnmbox-get-new-mail
14933 @vindex nnml-get-new-mail
14934 @vindex nnmh-get-new-mail
14935 @vindex nnfolder-get-new-mail
14936 This might be too much, if, for instance, you are reading mail quite
14937 happily with @code{nnml} and just want to peek at some old Rmail
14938 file you have stashed away with @code{nnbabyl}. All back ends have
14939 variables called back-end-@code{get-new-mail}. If you want to disable
14940 the @code{nnbabyl} mail reading, you edit the virtual server for the
14941 group to have a setting where @code{nnbabyl-get-new-mail} to @code{nil}.
14943 All the mail back ends will call @code{nn}*@code{-prepare-save-mail-hook}
14944 narrowed to the article to be saved before saving it when reading
14948 @node Choosing a Mail Back End
14949 @subsection Choosing a Mail Back End
14951 Gnus will read the mail spool when you activate a mail group. The mail
14952 file is first copied to your home directory. What happens after that
14953 depends on what format you want to store your mail in.
14955 There are six different mail back ends in the standard Gnus, and more
14956 back ends are available separately. The mail back end most people use
14957 (because it is possibly the fastest) is @code{nnml} (@pxref{Mail
14961 * Unix Mail Box:: Using the (quite) standard Un*x mbox.
14962 * Rmail Babyl:: Emacs programs use the Rmail Babyl format.
14963 * Mail Spool:: Store your mail in a private spool?
14964 * MH Spool:: An mhspool-like back end.
14965 * Maildir:: Another one-file-per-message format.
14966 * Mail Folders:: Having one file for each group.
14967 * Comparing Mail Back Ends:: An in-depth looks at pros and cons.
14971 @node Unix Mail Box
14972 @subsubsection Unix Mail Box
14974 @cindex unix mail box
14976 @vindex nnmbox-active-file
14977 @vindex nnmbox-mbox-file
14978 The @dfn{nnmbox} back end will use the standard Un*x mbox file to store
14979 mail. @code{nnmbox} will add extra headers to each mail article to say
14980 which group it belongs in.
14982 Virtual server settings:
14985 @item nnmbox-mbox-file
14986 @vindex nnmbox-mbox-file
14987 The name of the mail box in the user's home directory. Default is
14990 @item nnmbox-active-file
14991 @vindex nnmbox-active-file
14992 The name of the active file for the mail box. Default is
14993 @file{~/.mbox-active}.
14995 @item nnmbox-get-new-mail
14996 @vindex nnmbox-get-new-mail
14997 If non-@code{nil}, @code{nnmbox} will read incoming mail and split it
14998 into groups. Default is @code{t}.
15003 @subsubsection Rmail Babyl
15007 @vindex nnbabyl-active-file
15008 @vindex nnbabyl-mbox-file
15009 The @dfn{nnbabyl} back end will use a Babyl mail box (aka. @dfn{Rmail
15010 mbox}) to store mail. @code{nnbabyl} will add extra headers to each
15011 mail article to say which group it belongs in.
15013 Virtual server settings:
15016 @item nnbabyl-mbox-file
15017 @vindex nnbabyl-mbox-file
15018 The name of the Rmail mbox file. The default is @file{~/RMAIL}
15020 @item nnbabyl-active-file
15021 @vindex nnbabyl-active-file
15022 The name of the active file for the rmail box. The default is
15023 @file{~/.rmail-active}
15025 @item nnbabyl-get-new-mail
15026 @vindex nnbabyl-get-new-mail
15027 If non-@code{nil}, @code{nnbabyl} will read incoming mail. Default is
15033 @subsubsection Mail Spool
15035 @cindex mail @acronym{NOV} spool
15037 The @dfn{nnml} spool mail format isn't compatible with any other known
15038 format. It should be used with some caution.
15040 @vindex nnml-directory
15041 If you use this back end, Gnus will split all incoming mail into files,
15042 one file for each mail, and put the articles into the corresponding
15043 directories under the directory specified by the @code{nnml-directory}
15044 variable. The default value is @file{~/Mail/}.
15046 You do not have to create any directories beforehand; Gnus will take
15049 If you have a strict limit as to how many files you are allowed to store
15050 in your account, you should not use this back end. As each mail gets its
15051 own file, you might very well occupy thousands of inodes within a few
15052 weeks. If this is no problem for you, and it isn't a problem for you
15053 having your friendly systems administrator walking around, madly,
15054 shouting ``Who is eating all my inodes?! Who? Who!?!'', then you should
15055 know that this is probably the fastest format to use. You do not have
15056 to trudge through a big mbox file just to read your new mail.
15058 @code{nnml} is probably the slowest back end when it comes to article
15059 splitting. It has to create lots of files, and it also generates
15060 @acronym{NOV} databases for the incoming mails. This makes it possibly the
15061 fastest back end when it comes to reading mail.
15063 @cindex self contained nnml servers
15065 When the marks file is used (which it is by default), @code{nnml}
15066 servers have the property that you may backup them using @code{tar} or
15067 similar, and later be able to restore them into Gnus (by adding the
15068 proper @code{nnml} server) and have all your marks be preserved. Marks
15069 for a group is usually stored in the @code{.marks} file (but see
15070 @code{nnml-marks-file-name}) within each @code{nnml} group's directory.
15071 Individual @code{nnml} groups are also possible to backup, use @kbd{G m}
15072 to restore the group (after restoring the backup into the nnml
15075 If for some reason you believe your @file{.marks} files are screwed
15076 up, you can just delete them all. Gnus will then correctly regenerate
15077 them next time it starts.
15079 Virtual server settings:
15082 @item nnml-directory
15083 @vindex nnml-directory
15084 All @code{nnml} directories will be placed under this directory. The
15085 default is the value of @code{message-directory} (whose default value
15088 @item nnml-active-file
15089 @vindex nnml-active-file
15090 The active file for the @code{nnml} server. The default is
15091 @file{~/Mail/active}.
15093 @item nnml-newsgroups-file
15094 @vindex nnml-newsgroups-file
15095 The @code{nnml} group descriptions file. @xref{Newsgroups File
15096 Format}. The default is @file{~/Mail/newsgroups}.
15098 @item nnml-get-new-mail
15099 @vindex nnml-get-new-mail
15100 If non-@code{nil}, @code{nnml} will read incoming mail. The default is
15103 @item nnml-nov-is-evil
15104 @vindex nnml-nov-is-evil
15105 If non-@code{nil}, this back end will ignore any @acronym{NOV} files. The
15106 default is @code{nil}.
15108 @item nnml-nov-file-name
15109 @vindex nnml-nov-file-name
15110 The name of the @acronym{NOV} files. The default is @file{.overview}.
15112 @item nnml-prepare-save-mail-hook
15113 @vindex nnml-prepare-save-mail-hook
15114 Hook run narrowed to an article before saving.
15116 @item nnml-marks-is-evil
15117 @vindex nnml-marks-is-evil
15118 If non-@code{nil}, this back end will ignore any @sc{marks} files. The
15119 default is @code{nil}.
15121 @item nnml-marks-file-name
15122 @vindex nnml-marks-file-name
15123 The name of the @dfn{marks} files. The default is @file{.marks}.
15125 @item nnml-use-compressed-files
15126 @vindex nnml-use-compressed-files
15127 If non-@code{nil}, @code{nnml} will allow using compressed message
15132 @findex nnml-generate-nov-databases
15133 If your @code{nnml} groups and @acronym{NOV} files get totally out of
15134 whack, you can do a complete update by typing @kbd{M-x
15135 nnml-generate-nov-databases}. This command will trawl through the
15136 entire @code{nnml} hierarchy, looking at each and every article, so it
15137 might take a while to complete. A better interface to this
15138 functionality can be found in the server buffer (@pxref{Server
15143 @subsubsection MH Spool
15145 @cindex mh-e mail spool
15147 @code{nnmh} is just like @code{nnml}, except that is doesn't generate
15148 @acronym{NOV} databases and it doesn't keep an active file or marks
15149 file. This makes @code{nnmh} a @emph{much} slower back end than
15150 @code{nnml}, but it also makes it easier to write procmail scripts
15153 Virtual server settings:
15156 @item nnmh-directory
15157 @vindex nnmh-directory
15158 All @code{nnmh} directories will be located under this directory. The
15159 default is the value of @code{message-directory} (whose default is
15162 @item nnmh-get-new-mail
15163 @vindex nnmh-get-new-mail
15164 If non-@code{nil}, @code{nnmh} will read incoming mail. The default is
15168 @vindex nnmh-be-safe
15169 If non-@code{nil}, @code{nnmh} will go to ridiculous lengths to make
15170 sure that the articles in the folder are actually what Gnus thinks
15171 they are. It will check date stamps and stat everything in sight, so
15172 setting this to @code{t} will mean a serious slow-down. If you never
15173 use anything but Gnus to read the @code{nnmh} articles, you do not
15174 have to set this variable to @code{t}. The default is @code{nil}.
15179 @subsubsection Maildir
15183 @code{nnmaildir} stores mail in the maildir format, with each maildir
15184 corresponding to a group in Gnus. This format is documented here:
15185 @uref{http://cr.yp.to/proto/maildir.html} and here:
15186 @uref{http://www.qmail.org/man/man5/maildir.html}. @code{nnmaildir}
15187 also stores extra information in the @file{.nnmaildir/} directory
15190 Maildir format was designed to allow concurrent deliveries and
15191 reading, without needing locks. With other back ends, you would have
15192 your mail delivered to a spool of some kind, and then you would
15193 configure Gnus to split mail from that spool into your groups. You
15194 can still do that with @code{nnmaildir}, but the more common
15195 configuration is to have your mail delivered directly to the maildirs
15196 that appear as group in Gnus.
15198 @code{nnmaildir} is designed to be perfectly reliable: @kbd{C-g} will
15199 never corrupt its data in memory, and @code{SIGKILL} will never
15200 corrupt its data in the filesystem.
15202 @code{nnmaildir} stores article marks and @acronym{NOV} data in each
15203 maildir. So you can copy a whole maildir from one Gnus setup to
15204 another, and you will keep your marks.
15206 Virtual server settings:
15210 For each of your @code{nnmaildir} servers (it's very unlikely that
15211 you'd need more than one), you need to create a directory and populate
15212 it with maildirs or symlinks to maildirs (and nothing else; do not
15213 choose a directory already used for other purposes). Each maildir
15214 will be represented in Gnus as a newsgroup on that server; the
15215 filename of the symlink will be the name of the group. Any filenames
15216 in the directory starting with @samp{.} are ignored. The directory is
15217 scanned when you first start Gnus, and each time you type @kbd{g} in
15218 the group buffer; if any maildirs have been removed or added,
15219 @code{nnmaildir} notices at these times.
15221 The value of the @code{directory} parameter should be a Lisp form
15222 which is processed by @code{eval} and @code{expand-file-name} to get
15223 the path of the directory for this server. The form is @code{eval}ed
15224 only when the server is opened; the resulting string is used until the
15225 server is closed. (If you don't know about forms and @code{eval},
15226 don't worry---a simple string will work.) This parameter is not
15227 optional; you must specify it. I don't recommend using
15228 @code{"~/Mail"} or a subdirectory of it; several other parts of Gnus
15229 use that directory by default for various things, and may get confused
15230 if @code{nnmaildir} uses it too. @code{"~/.nnmaildir"} is a typical
15233 @item target-prefix
15234 This should be a Lisp form which is processed by @code{eval} and
15235 @code{expand-file-name}. The form is @code{eval}ed only when the
15236 server is opened; the resulting string is used until the server is
15239 When you create a group on an @code{nnmaildir} server, the maildir is
15240 created with @code{target-prefix} prepended to its name, and a symlink
15241 pointing to that maildir is created, named with the plain group name.
15242 So if @code{directory} is @code{"~/.nnmaildir"} and
15243 @code{target-prefix} is @code{"../maildirs/"}, then when you create
15244 the group @code{foo}, @code{nnmaildir} will create
15245 @file{~/.nnmaildir/../maildirs/foo} as a maildir, and will create
15246 @file{~/.nnmaildir/foo} as a symlink pointing to
15247 @file{../maildirs/foo}.
15249 You can set @code{target-prefix} to a string without any slashes to
15250 create both maildirs and symlinks in the same @code{directory}; in
15251 this case, any maildirs found in @code{directory} whose names start
15252 with @code{target-prefix} will not be listed as groups (but the
15253 symlinks pointing to them will be).
15255 As a special case, if @code{target-prefix} is @code{""} (the default),
15256 then when you create a group, the maildir will be created in
15257 @code{directory} without a corresponding symlink. Beware that you
15258 cannot use @code{gnus-group-delete-group} on such groups without the
15259 @code{force} argument.
15261 @item directory-files
15262 This should be a function with the same interface as
15263 @code{directory-files} (such as @code{directory-files} itself). It is
15264 used to scan the server's @code{directory} for maildirs. This
15265 parameter is optional; the default is
15266 @code{nnheader-directory-files-safe} if
15267 @code{nnheader-directory-files-is-safe} is @code{nil}, and
15268 @code{directory-files} otherwise.
15269 (@code{nnheader-directory-files-is-safe} is checked only once when the
15270 server is opened; if you want to check it each time the directory is
15271 scanned, you'll have to provide your own function that does that.)
15274 If non-@code{nil}, then after scanning for new mail in the group
15275 maildirs themselves as usual, this server will also incorporate mail
15276 the conventional Gnus way, from @code{mail-sources} according to
15277 @code{nnmail-split-methods} or @code{nnmail-split-fancy}. The default
15278 value is @code{nil}.
15280 Do @emph{not} use the same maildir both in @code{mail-sources} and as
15281 an @code{nnmaildir} group. The results might happen to be useful, but
15282 that would be by chance, not by design, and the results might be
15283 different in the future. If your split rules create new groups,
15284 remember to supply a @code{create-directory} server parameter.
15287 @subsubsection Group parameters
15289 @code{nnmaildir} uses several group parameters. It's safe to ignore
15290 all this; the default behavior for @code{nnmaildir} is the same as the
15291 default behavior for other mail back ends: articles are deleted after
15292 one week, etc. Except for the expiry parameters, all this
15293 functionality is unique to @code{nnmaildir}, so you can ignore it if
15294 you're just trying to duplicate the behavior you already have with
15297 If the value of any of these parameters is a vector, the first element
15298 is evaluated as a Lisp form and the result is used, rather than the
15299 original value. If the value is not a vector, the value itself is
15300 evaluated as a Lisp form. (This is why these parameters use names
15301 different from those of other, similar parameters supported by other
15302 back ends: they have different, though similar, meanings.) (For
15303 numbers, strings, @code{nil}, and @code{t}, you can ignore the
15304 @code{eval} business again; for other values, remember to use an extra
15305 quote and wrap the value in a vector when appropriate.)
15309 An integer specifying the minimum age, in seconds, of an article
15310 before it will be expired, or the symbol @code{never} to specify that
15311 articles should never be expired. If this parameter is not set,
15312 @code{nnmaildir} falls back to the usual
15313 @code{nnmail-expiry-wait}(@code{-function}) variables (overrideable by
15314 the @code{expiry-wait}(@code{-function}) group parameters. If you
15315 wanted a value of 3 days, you could use something like @code{[(* 3 24
15316 60 60)]}; @code{nnmaildir} will evaluate the form and use the result.
15317 An article's age is measured starting from the article file's
15318 modification time. Normally, this is the same as the article's
15319 delivery time, but editing an article makes it younger. Moving an
15320 article (other than via expiry) may also make an article younger.
15323 If this is set to a string such as a full Gnus group name, like
15325 "backend+server.address.string:group.name"
15327 and if it is not the name of the same group that the parameter belongs
15328 to, then articles will be moved to the specified group during expiry
15329 before being deleted. @emph{If this is set to an @code{nnmaildir}
15330 group, the article will be just as old in the destination group as it
15331 was in the source group.} So be careful with @code{expire-age} in the
15332 destination group. If this is set to the name of the same group that
15333 the parameter belongs to, then the article is not expired at all. If
15334 you use the vector form, the first element is evaluated once for each
15335 article. So that form can refer to
15336 @code{nnmaildir-article-file-name}, etc., to decide where to put the
15337 article. @emph{If this parameter is not set, @code{nnmaildir} does
15338 not fall back to the @code{expiry-target} group parameter or the
15339 @code{nnmail-expiry-target} variable.}
15342 If this is set to @code{t}, @code{nnmaildir} will treat the articles
15343 in this maildir as read-only. This means: articles are not renamed
15344 from @file{new/} into @file{cur/}; articles are only found in
15345 @file{new/}, not @file{cur/}; articles are never deleted; articles
15346 cannot be edited. @file{new/} is expected to be a symlink to the
15347 @file{new/} directory of another maildir---e.g., a system-wide mailbox
15348 containing a mailing list of common interest. Everything in the
15349 maildir outside @file{new/} is @emph{not} treated as read-only, so for
15350 a shared mailbox, you do still need to set up your own maildir (or
15351 have write permission to the shared mailbox); your maildir just won't
15352 contain extra copies of the articles.
15354 @item directory-files
15355 A function with the same interface as @code{directory-files}. It is
15356 used to scan the directories in the maildir corresponding to this
15357 group to find articles. The default is the function specified by the
15358 server's @code{directory-files} parameter.
15360 @item distrust-Lines:
15361 If non-@code{nil}, @code{nnmaildir} will always count the lines of an
15362 article, rather than use the @code{Lines:} header field. If
15363 @code{nil}, the header field will be used if present.
15366 A list of mark symbols, such as @code{['(read expire)]}. Whenever
15367 Gnus asks @code{nnmaildir} for article marks, @code{nnmaildir} will
15368 say that all articles have these marks, regardless of whether the
15369 marks stored in the filesystem say so. This is a proof-of-concept
15370 feature that will probably be removed eventually; it ought to be done
15371 in Gnus proper, or abandoned if it's not worthwhile.
15374 A list of mark symbols, such as @code{['(tick expire)]}. Whenever
15375 Gnus asks @code{nnmaildir} for article marks, @code{nnmaildir} will
15376 say that no articles have these marks, regardless of whether the marks
15377 stored in the filesystem say so. @code{never-marks} overrides
15378 @code{always-marks}. This is a proof-of-concept feature that will
15379 probably be removed eventually; it ought to be done in Gnus proper, or
15380 abandoned if it's not worthwhile.
15382 @item nov-cache-size
15383 An integer specifying the size of the @acronym{NOV} memory cache. To
15384 speed things up, @code{nnmaildir} keeps @acronym{NOV} data in memory
15385 for a limited number of articles in each group. (This is probably not
15386 worthwhile, and will probably be removed in the future.) This
15387 parameter's value is noticed only the first time a group is seen after
15388 the server is opened---i.e., when you first start Gnus, typically.
15389 The @acronym{NOV} cache is never resized until the server is closed
15390 and reopened. The default is an estimate of the number of articles
15391 that would be displayed in the summary buffer: a count of articles
15392 that are either marked with @code{tick} or not marked with
15393 @code{read}, plus a little extra.
15396 @subsubsection Article identification
15397 Articles are stored in the @file{cur/} subdirectory of each maildir.
15398 Each article file is named like @code{uniq:info}, where @code{uniq}
15399 contains no colons. @code{nnmaildir} ignores, but preserves, the
15400 @code{:info} part. (Other maildir readers typically use this part of
15401 the filename to store marks.) The @code{uniq} part uniquely
15402 identifies the article, and is used in various places in the
15403 @file{.nnmaildir/} subdirectory of the maildir to store information
15404 about the corresponding article. The full pathname of an article is
15405 available in the variable @code{nnmaildir-article-file-name} after you
15406 request the article in the summary buffer.
15408 @subsubsection NOV data
15409 An article identified by @code{uniq} has its @acronym{NOV} data (used
15410 to generate lines in the summary buffer) stored in
15411 @code{.nnmaildir/nov/uniq}. There is no
15412 @code{nnmaildir-generate-nov-databases} function. (There isn't much
15413 need for it---an article's @acronym{NOV} data is updated automatically
15414 when the article or @code{nnmail-extra-headers} has changed.) You can
15415 force @code{nnmaildir} to regenerate the @acronym{NOV} data for a
15416 single article simply by deleting the corresponding @acronym{NOV}
15417 file, but @emph{beware}: this will also cause @code{nnmaildir} to
15418 assign a new article number for this article, which may cause trouble
15419 with @code{seen} marks, the Agent, and the cache.
15421 @subsubsection Article marks
15422 An article identified by @code{uniq} is considered to have the mark
15423 @code{flag} when the file @file{.nnmaildir/marks/flag/uniq} exists.
15424 When Gnus asks @code{nnmaildir} for a group's marks, @code{nnmaildir}
15425 looks for such files and reports the set of marks it finds. When Gnus
15426 asks @code{nnmaildir} to store a new set of marks, @code{nnmaildir}
15427 creates and deletes the corresponding files as needed. (Actually,
15428 rather than create a new file for each mark, it just creates hard
15429 links to @file{.nnmaildir/markfile}, to save inodes.)
15431 You can invent new marks by creating a new directory in
15432 @file{.nnmaildir/marks/}. You can tar up a maildir and remove it from
15433 your server, untar it later, and keep your marks. You can add and
15434 remove marks yourself by creating and deleting mark files. If you do
15435 this while Gnus is running and your @code{nnmaildir} server is open,
15436 it's best to exit all summary buffers for @code{nnmaildir} groups and
15437 type @kbd{s} in the group buffer first, and to type @kbd{g} or
15438 @kbd{M-g} in the group buffer afterwards. Otherwise, Gnus might not
15439 pick up the changes, and might undo them.
15443 @subsubsection Mail Folders
15445 @cindex mbox folders
15446 @cindex mail folders
15448 @code{nnfolder} is a back end for storing each mail group in a
15449 separate file. Each file is in the standard Un*x mbox format.
15450 @code{nnfolder} will add extra headers to keep track of article
15451 numbers and arrival dates.
15453 @cindex self contained nnfolder servers
15455 When the marks file is used (which it is by default), @code{nnfolder}
15456 servers have the property that you may backup them using @code{tar} or
15457 similar, and later be able to restore them into Gnus (by adding the
15458 proper @code{nnfolder} server) and have all your marks be preserved.
15459 Marks for a group is usually stored in a file named as the mbox file
15460 with @code{.mrk} concatenated to it (but see
15461 @code{nnfolder-marks-file-suffix}) within the @code{nnfolder}
15462 directory. Individual @code{nnfolder} groups are also possible to
15463 backup, use @kbd{G m} to restore the group (after restoring the backup
15464 into the @code{nnfolder} directory).
15466 Virtual server settings:
15469 @item nnfolder-directory
15470 @vindex nnfolder-directory
15471 All the @code{nnfolder} mail boxes will be stored under this
15472 directory. The default is the value of @code{message-directory}
15473 (whose default is @file{~/Mail})
15475 @item nnfolder-active-file
15476 @vindex nnfolder-active-file
15477 The name of the active file. The default is @file{~/Mail/active}.
15479 @item nnfolder-newsgroups-file
15480 @vindex nnfolder-newsgroups-file
15481 The name of the group descriptions file. @xref{Newsgroups File
15482 Format}. The default is @file{~/Mail/newsgroups}
15484 @item nnfolder-get-new-mail
15485 @vindex nnfolder-get-new-mail
15486 If non-@code{nil}, @code{nnfolder} will read incoming mail. The
15487 default is @code{t}
15489 @item nnfolder-save-buffer-hook
15490 @vindex nnfolder-save-buffer-hook
15491 @cindex backup files
15492 Hook run before saving the folders. Note that Emacs does the normal
15493 backup renaming of files even with the @code{nnfolder} buffers. If
15494 you wish to switch this off, you could say something like the
15495 following in your @file{.emacs} file:
15498 (defun turn-off-backup ()
15499 (set (make-local-variable 'backup-inhibited) t))
15501 (add-hook 'nnfolder-save-buffer-hook 'turn-off-backup)
15504 @item nnfolder-delete-mail-hook
15505 @vindex nnfolder-delete-mail-hook
15506 Hook run in a buffer narrowed to the message that is to be deleted.
15507 This function can be used to copy the message to somewhere else, or to
15508 extract some information from it before removing it.
15510 @item nnfolder-nov-is-evil
15511 @vindex nnfolder-nov-is-evil
15512 If non-@code{nil}, this back end will ignore any @acronym{NOV} files. The
15513 default is @code{nil}.
15515 @item nnfolder-nov-file-suffix
15516 @vindex nnfolder-nov-file-suffix
15517 The extension for @acronym{NOV} files. The default is @file{.nov}.
15519 @item nnfolder-nov-directory
15520 @vindex nnfolder-nov-directory
15521 The directory where the @acronym{NOV} files should be stored. If
15522 @code{nil}, @code{nnfolder-directory} is used.
15524 @item nnfolder-marks-is-evil
15525 @vindex nnfolder-marks-is-evil
15526 If non-@code{nil}, this back end will ignore any @sc{marks} files. The
15527 default is @code{nil}.
15529 @item nnfolder-marks-file-suffix
15530 @vindex nnfolder-marks-file-suffix
15531 The extension for @sc{marks} files. The default is @file{.mrk}.
15533 @item nnfolder-marks-directory
15534 @vindex nnfolder-marks-directory
15535 The directory where the @sc{marks} files should be stored. If
15536 @code{nil}, @code{nnfolder-directory} is used.
15541 @findex nnfolder-generate-active-file
15542 @kindex M-x nnfolder-generate-active-file
15543 If you have lots of @code{nnfolder}-like files you'd like to read with
15544 @code{nnfolder}, you can use the @kbd{M-x nnfolder-generate-active-file}
15545 command to make @code{nnfolder} aware of all likely files in
15546 @code{nnfolder-directory}. This only works if you use long file names,
15549 @node Comparing Mail Back Ends
15550 @subsubsection Comparing Mail Back Ends
15552 First, just for terminology, the @dfn{back end} is the common word for a
15553 low-level access method---a transport, if you will, by which something
15554 is acquired. The sense is that one's mail has to come from somewhere,
15555 and so selection of a suitable back end is required in order to get that
15556 mail within spitting distance of Gnus.
15558 The same concept exists for Usenet itself: Though access to articles is
15559 typically done by @acronym{NNTP} these days, once upon a midnight dreary, everyone
15560 in the world got at Usenet by running a reader on the machine where the
15561 articles lay (the machine which today we call an @acronym{NNTP} server), and
15562 access was by the reader stepping into the articles' directory spool
15563 area directly. One can still select between either the @code{nntp} or
15564 @code{nnspool} back ends, to select between these methods, if one happens
15565 actually to live on the server (or can see its spool directly, anyway,
15568 The goal in selecting a mail back end is to pick one which
15569 simultaneously represents a suitable way of dealing with the original
15570 format plus leaving mail in a form that is convenient to use in the
15571 future. Here are some high and low points on each:
15576 UNIX systems have historically had a single, very common, and well-
15577 defined format. All messages arrive in a single @dfn{spool file}, and
15578 they are delineated by a line whose regular expression matches
15579 @samp{^From_}. (My notational use of @samp{_} is to indicate a space,
15580 to make it clear in this instance that this is not the RFC-specified
15581 @samp{From:} header.) Because Emacs and therefore Gnus emanate
15582 historically from the Unix environment, it is simplest if one does not
15583 mess a great deal with the original mailbox format, so if one chooses
15584 this back end, Gnus' primary activity in getting mail from the real spool
15585 area to Gnus' preferred directory is simply to copy it, with no
15586 (appreciable) format change in the process. It is the ``dumbest'' way
15587 to move mail into availability in the Gnus environment. This makes it
15588 fast to move into place, but slow to parse, when Gnus has to look at
15593 Once upon a time, there was the DEC-10 and DEC-20, running operating
15594 systems called TOPS and related things, and the usual (only?) mail
15595 reading environment was a thing called Babyl. I don't know what format
15596 was used for mail landing on the system, but Babyl had its own internal
15597 format to which mail was converted, primarily involving creating a
15598 spool-file-like entity with a scheme for inserting Babyl-specific
15599 headers and status bits above the top of each message in the file.
15600 Rmail was Emacs' first mail reader, it was written by Richard Stallman,
15601 and Stallman came out of that TOPS/Babyl environment, so he wrote Rmail
15602 to understand the mail files folks already had in existence. Gnus (and
15603 VM, for that matter) continue to support this format because it's
15604 perceived as having some good qualities in those mailer-specific
15605 headers/status bits stuff. Rmail itself still exists as well, of
15606 course, and is still maintained by Stallman.
15608 Both of the above forms leave your mail in a single file on your
15609 file system, and they must parse that entire file each time you take a
15614 @code{nnml} is the back end which smells the most as though you were
15615 actually operating with an @code{nnspool}-accessed Usenet system. (In
15616 fact, I believe @code{nnml} actually derived from @code{nnspool} code,
15617 lo these years ago.) One's mail is taken from the original spool file,
15618 and is then cut up into individual message files, 1:1. It maintains a
15619 Usenet-style active file (analogous to what one finds in an INN- or
15620 CNews-based news system in (for instance) @file{/var/lib/news/active},
15621 or what is returned via the @samp{NNTP LIST} verb) and also creates
15622 @dfn{overview} files for efficient group entry, as has been defined for
15623 @acronym{NNTP} servers for some years now. It is slower in mail-splitting,
15624 due to the creation of lots of files, updates to the @code{nnml} active
15625 file, and additions to overview files on a per-message basis, but it is
15626 extremely fast on access because of what amounts to the indexing support
15627 provided by the active file and overviews.
15629 @code{nnml} costs @dfn{inodes} in a big way; that is, it soaks up the
15630 resource which defines available places in the file system to put new
15631 files. Sysadmins take a dim view of heavy inode occupation within
15632 tight, shared file systems. But if you live on a personal machine where
15633 the file system is your own and space is not at a premium, @code{nnml}
15636 It is also problematic using this back end if you are living in a
15637 FAT16-based Windows world, since much space will be wasted on all these
15642 The Rand MH mail-reading system has been around UNIX systems for a very
15643 long time; it operates by splitting one's spool file of messages into
15644 individual files, but with little or no indexing support---@code{nnmh}
15645 is considered to be semantically equivalent to ``@code{nnml} without
15646 active file or overviews''. This is arguably the worst choice, because
15647 one gets the slowness of individual file creation married to the
15648 slowness of access parsing when learning what's new in one's groups.
15652 Basically the effect of @code{nnfolder} is @code{nnmbox} (the first
15653 method described above) on a per-group basis. That is, @code{nnmbox}
15654 itself puts @emph{all} one's mail in one file; @code{nnfolder} provides a
15655 little bit of optimization to this so that each of one's mail groups has
15656 a Unix mail box file. It's faster than @code{nnmbox} because each group
15657 can be parsed separately, and still provides the simple Unix mail box
15658 format requiring minimal effort in moving the mail around. In addition,
15659 it maintains an ``active'' file making it much faster for Gnus to figure
15660 out how many messages there are in each separate group.
15662 If you have groups that are expected to have a massive amount of
15663 messages, @code{nnfolder} is not the best choice, but if you receive
15664 only a moderate amount of mail, @code{nnfolder} is probably the most
15665 friendly mail back end all over.
15669 For configuring expiry and other things, @code{nnmaildir} uses
15670 incompatible group parameters, slightly different from those of other
15673 @code{nnmaildir} is largely similar to @code{nnml}, with some notable
15674 differences. Each message is stored in a separate file, but the
15675 filename is unrelated to the article number in Gnus. @code{nnmaildir}
15676 also stores the equivalent of @code{nnml}'s overview files in one file
15677 per article, so it uses about twice as many inodes as @code{nnml}. (Use
15678 @code{df -i} to see how plentiful your inode supply is.) If this slows
15679 you down or takes up very much space, consider switching to
15680 @uref{http://www.namesys.com/, ReiserFS} or another non-block-structured
15683 Since maildirs don't require locking for delivery, the maildirs you use
15684 as groups can also be the maildirs your mail is directly delivered to.
15685 This means you can skip Gnus' mail splitting if your mail is already
15686 organized into different mailboxes during delivery. A @code{directory}
15687 entry in @code{mail-sources} would have a similar effect, but would
15688 require one set of mailboxes for spooling deliveries (in mbox format,
15689 thus damaging message bodies), and another set to be used as groups (in
15690 whatever format you like). A maildir has a built-in spool, in the
15691 @code{new/} subdirectory. Beware that currently, mail moved from
15692 @code{new/} to @code{cur/} instead of via mail splitting will not
15693 undergo treatment such as duplicate checking.
15695 @code{nnmaildir} stores article marks for a given group in the
15696 corresponding maildir, in a way designed so that it's easy to manipulate
15697 them from outside Gnus. You can tar up a maildir, unpack it somewhere
15698 else, and still have your marks. @code{nnml} also stores marks, but
15699 it's not as easy to work with them from outside Gnus as with
15702 @code{nnmaildir} uses a significant amount of memory to speed things up.
15703 (It keeps in memory some of the things that @code{nnml} stores in files
15704 and that @code{nnmh} repeatedly parses out of message files.) If this
15705 is a problem for you, you can set the @code{nov-cache-size} group
15706 parameter to something small (0 would probably not work, but 1 probably
15707 would) to make it use less memory. This caching will probably be
15708 removed in the future.
15710 Startup is likely to be slower with @code{nnmaildir} than with other
15711 back ends. Everything else is likely to be faster, depending in part
15712 on your file system.
15714 @code{nnmaildir} does not use @code{nnoo}, so you cannot use @code{nnoo}
15715 to write an @code{nnmaildir}-derived back end.
15720 @node Browsing the Web
15721 @section Browsing the Web
15723 @cindex browsing the web
15727 Web-based discussion forums are getting more and more popular. On many
15728 subjects, the web-based forums have become the most important forums,
15729 eclipsing the importance of mailing lists and news groups. The reason
15730 is easy to understand---they are friendly to new users; you just point
15731 and click, and there's the discussion. With mailing lists, you have to
15732 go through a cumbersome subscription procedure, and most people don't
15733 even know what a news group is.
15735 The problem with this scenario is that web browsers are not very good at
15736 being newsreaders. They do not keep track of what articles you've read;
15737 they do not allow you to score on subjects you're interested in; they do
15738 not allow off-line browsing; they require you to click around and drive
15739 you mad in the end.
15741 So---if web browsers suck at reading discussion forums, why not use Gnus
15744 Gnus has been getting a bit of a collection of back ends for providing
15745 interfaces to these sources.
15749 * Web Searches:: Creating groups from articles that match a string.
15750 * Slashdot:: Reading the Slashdot comments.
15751 * Ultimate:: The Ultimate Bulletin Board systems.
15752 * Web Archive:: Reading mailing list archived on web.
15753 * RSS:: Reading RDF site summary.
15754 * Customizing w3:: Doing stuff to Emacs/w3 from Gnus.
15757 All the web sources require Emacs/w3 and the url library to work.
15759 The main caveat with all these web sources is that they probably won't
15760 work for a very long time. Gleaning information from the @acronym{HTML} data
15761 is guesswork at best, and when the layout is altered, the Gnus back end
15762 will fail. If you have reasonably new versions of these back ends,
15763 though, you should be ok.
15765 One thing all these Web methods have in common is that the Web sources
15766 are often down, unavailable or just plain too slow to be fun. In those
15767 cases, it makes a lot of sense to let the Gnus Agent (@pxref{Gnus
15768 Unplugged}) handle downloading articles, and then you can read them at
15769 leisure from your local disk. No more World Wide Wait for you.
15771 @node Archiving Mail
15772 @subsection Archiving Mail
15773 @cindex archiving mail
15774 @cindex backup of mail
15776 Some of the back ends, notably @code{nnml}, @code{nnfolder}, and
15777 @code{nnmaildir}, now actually store the article marks with each group.
15778 For these servers, archiving and restoring a group while preserving
15779 marks is fairly simple.
15781 (Preserving the group level and group parameters as well still
15782 requires ritual dancing and sacrifices to the @file{.newsrc.eld} deity
15785 To archive an entire @code{nnml}, @code{nnfolder}, or @code{nnmaildir}
15786 server, take a recursive copy of the server directory. There is no need
15787 to shut down Gnus, so archiving may be invoked by @code{cron} or
15788 similar. You restore the data by restoring the directory tree, and
15789 adding a server definition pointing to that directory in Gnus. The
15790 @ref{Article Backlog}, @ref{Asynchronous Fetching} and other things
15791 might interfere with overwriting data, so you may want to shut down Gnus
15792 before you restore the data.
15794 It is also possible to archive individual @code{nnml},
15795 @code{nnfolder}, or @code{nnmaildir} groups, while preserving marks.
15796 For @code{nnml} or @code{nnmaildir}, you copy all files in the group's
15797 directory. For @code{nnfolder} you need to copy both the base folder
15798 file itself (@file{FOO}, say), and the marks file (@file{FOO.mrk} in
15799 this example). Restoring the group is done with @kbd{G m} from the Group
15800 buffer. The last step makes Gnus notice the new directory.
15801 @code{nnmaildir} notices the new directory automatically, so @kbd{G m}
15802 is unnecessary in that case.
15805 @subsection Web Searches
15810 @cindex Usenet searches
15811 @cindex searching the Usenet
15813 It's, like, too neat to search the Usenet for articles that match a
15814 string, but it, like, totally @emph{sucks}, like, totally, to use one of
15815 those, like, Web browsers, and you, like, have to, rilly, like, look at
15816 the commercials, so, like, with Gnus you can do @emph{rad}, rilly,
15817 searches without having to use a browser.
15819 The @code{nnweb} back end allows an easy interface to the mighty search
15820 engine. You create an @code{nnweb} group, enter a search pattern, and
15821 then enter the group and read the articles like you would any normal
15822 group. The @kbd{G w} command in the group buffer (@pxref{Foreign
15823 Groups}) will do this in an easy-to-use fashion.
15825 @code{nnweb} groups don't really lend themselves to being solid
15826 groups---they have a very fleeting idea of article numbers. In fact,
15827 each time you enter an @code{nnweb} group (not even changing the search
15828 pattern), you are likely to get the articles ordered in a different
15829 manner. Not even using duplicate suppression (@pxref{Duplicate
15830 Suppression}) will help, since @code{nnweb} doesn't even know the
15831 @code{Message-ID} of the articles before reading them using some search
15832 engines (Google, for instance). The only possible way to keep track
15833 of which articles you've read is by scoring on the @code{Date}
15834 header---mark all articles posted before the last date you read the
15837 If the search engine changes its output substantially, @code{nnweb}
15838 won't be able to parse it and will fail. One could hardly fault the Web
15839 providers if they were to do this---their @emph{raison d'@^etre} is to
15840 make money off of advertisements, not to provide services to the
15841 community. Since @code{nnweb} washes the ads off all the articles, one
15842 might think that the providers might be somewhat miffed. We'll see.
15844 You must have the @code{url} and @code{w3} package installed to be able
15845 to use @code{nnweb}.
15847 Virtual server variables:
15852 What search engine type is being used. The currently supported types
15853 are @code{google}, @code{dejanews}, and @code{gmane}. Note that
15854 @code{dejanews} is an alias to @code{google}.
15857 @vindex nnweb-search
15858 The search string to feed to the search engine.
15860 @item nnweb-max-hits
15861 @vindex nnweb-max-hits
15862 Advisory maximum number of hits per search to display. The default is
15865 @item nnweb-type-definition
15866 @vindex nnweb-type-definition
15867 Type-to-definition alist. This alist says what @code{nnweb} should do
15868 with the various search engine types. The following elements must be
15873 Function to decode the article and provide something that Gnus
15877 Function to create an article number to message header and URL alist.
15880 Function to send the search string to the search engine.
15883 The address the aforementioned function should send the search string
15887 Format string URL to fetch an article by @code{Message-ID}.
15894 @subsection Slashdot
15898 @uref{http://slashdot.org/, Slashdot} is a popular news site, with
15899 lively discussion following the news articles. @code{nnslashdot} will
15900 let you read this forum in a convenient manner.
15902 The easiest way to read this source is to put something like the
15903 following in your @file{~/.gnus.el} file:
15906 (setq gnus-secondary-select-methods
15907 '((nnslashdot "")))
15910 This will make Gnus query the @code{nnslashdot} back end for new comments
15911 and groups. The @kbd{F} command will subscribe each new news article as
15912 a new Gnus group, and you can read the comments by entering these
15913 groups. (Note that the default subscription method is to subscribe new
15914 groups as zombies. Other methods are available (@pxref{Subscription
15917 If you want to remove an old @code{nnslashdot} group, the @kbd{G DEL}
15918 command is the most handy tool (@pxref{Foreign Groups}).
15920 When following up to @code{nnslashdot} comments (or posting new
15921 comments), some light @acronym{HTML}izations will be performed. In
15922 particular, text quoted with @samp{> } will be quoted with
15923 @samp{blockquote} instead, and signatures will have @samp{br} added to
15924 the end of each line. Other than that, you can just write @acronym{HTML}
15925 directly into the message buffer. Note that Slashdot filters out some
15926 @acronym{HTML} forms.
15928 The following variables can be altered to change its behavior:
15931 @item nnslashdot-threaded
15932 Whether @code{nnslashdot} should display threaded groups or not. The
15933 default is @code{t}. To be able to display threads, @code{nnslashdot}
15934 has to retrieve absolutely all comments in a group upon entry. If a
15935 threaded display is not required, @code{nnslashdot} will only retrieve
15936 the comments that are actually wanted by the user. Threading is nicer,
15937 but much, much slower than unthreaded.
15939 @item nnslashdot-login-name
15940 @vindex nnslashdot-login-name
15941 The login name to use when posting.
15943 @item nnslashdot-password
15944 @vindex nnslashdot-password
15945 The password to use when posting.
15947 @item nnslashdot-directory
15948 @vindex nnslashdot-directory
15949 Where @code{nnslashdot} will store its files. The default is
15950 @file{~/News/slashdot/}.
15952 @item nnslashdot-active-url
15953 @vindex nnslashdot-active-url
15954 The @acronym{URL} format string that will be used to fetch the
15955 information on news articles and comments. The default is@*
15956 @samp{http://slashdot.org/search.pl?section=&min=%d}.
15958 @item nnslashdot-comments-url
15959 @vindex nnslashdot-comments-url
15960 The @acronym{URL} format string that will be used to fetch comments.
15962 @item nnslashdot-article-url
15963 @vindex nnslashdot-article-url
15964 The @acronym{URL} format string that will be used to fetch the news
15965 article. The default is
15966 @samp{http://slashdot.org/article.pl?sid=%s&mode=nocomment}.
15968 @item nnslashdot-threshold
15969 @vindex nnslashdot-threshold
15970 The score threshold. The default is -1.
15972 @item nnslashdot-group-number
15973 @vindex nnslashdot-group-number
15974 The number of old groups, in addition to the ten latest, to keep
15975 updated. The default is 0.
15982 @subsection Ultimate
15984 @cindex Ultimate Bulletin Board
15986 @uref{http://www.ultimatebb.com/, The Ultimate Bulletin Board} is
15987 probably the most popular Web bulletin board system used. It has a
15988 quite regular and nice interface, and it's possible to get the
15989 information Gnus needs to keep groups updated.
15991 The easiest way to get started with @code{nnultimate} is to say
15992 something like the following in the group buffer: @kbd{B nnultimate RET
15993 http://www.tcj.com/messboard/ubbcgi/ RET}. (Substitute the @acronym{URL}
15994 (not including @samp{Ultimate.cgi} or the like at the end) for a forum
15995 you're interested in; there's quite a list of them on the Ultimate web
15996 site.) Then subscribe to the groups you're interested in from the
15997 server buffer, and read them from the group buffer.
15999 The following @code{nnultimate} variables can be altered:
16002 @item nnultimate-directory
16003 @vindex nnultimate-directory
16004 The directory where @code{nnultimate} stores its files. The default is@*
16005 @file{~/News/ultimate/}.
16010 @subsection Web Archive
16012 @cindex Web Archive
16014 Some mailing lists only have archives on Web servers, such as
16015 @uref{http://www.egroups.com/} and
16016 @uref{http://www.mail-archive.com/}. It has a quite regular and nice
16017 interface, and it's possible to get the information Gnus needs to keep
16020 @findex gnus-group-make-warchive-group
16021 The easiest way to get started with @code{nnwarchive} is to say
16022 something like the following in the group buffer: @kbd{M-x
16023 gnus-group-make-warchive-group RET @var{an_egroup} RET egroups RET
16024 www.egroups.com RET @var{your@@email.address} RET}. (Substitute the
16025 @var{an_egroup} with the mailing list you subscribed, the
16026 @var{your@@email.address} with your email address.), or to browse the
16027 back end by @kbd{B nnwarchive RET mail-archive RET}.
16029 The following @code{nnwarchive} variables can be altered:
16032 @item nnwarchive-directory
16033 @vindex nnwarchive-directory
16034 The directory where @code{nnwarchive} stores its files. The default is@*
16035 @file{~/News/warchive/}.
16037 @item nnwarchive-login
16038 @vindex nnwarchive-login
16039 The account name on the web server.
16041 @item nnwarchive-passwd
16042 @vindex nnwarchive-passwd
16043 The password for your account on the web server.
16051 Some web sites have an RDF Site Summary (@acronym{RSS}).
16052 @acronym{RSS} is a format for summarizing headlines from news related
16053 sites (such as BBC or CNN). But basically anything list-like can be
16054 presented as an @acronym{RSS} feed: weblogs, changelogs or recent
16055 changes to a wiki (e.g. @url{http://cliki.net/recent-changes.rdf}).
16057 @acronym{RSS} has a quite regular and nice interface, and it's
16058 possible to get the information Gnus needs to keep groups updated.
16060 Note: you had better use Emacs which supports the @code{utf-8} coding
16061 system because @acronym{RSS} uses UTF-8 for encoding non-@acronym{ASCII}
16062 text by default. It is also used by default for non-@acronym{ASCII}
16065 @kindex G R (Summary)
16066 Use @kbd{G R} from the summary buffer to subscribe to a feed---you will
16067 be prompted for the location, the title and the description of the feed.
16068 The title, which allows any characters, will be used for the group name
16069 and the name of the group data file. The description can be omitted.
16071 An easy way to get started with @code{nnrss} is to say something like
16072 the following in the group buffer: @kbd{B nnrss RET RET y}, then
16073 subscribe to groups.
16075 The @code{nnrss} back end saves the group data file in
16076 @code{nnrss-directory} (see below) for each @code{nnrss} group. File
16077 names containing non-@acronym{ASCII} characters will be encoded by the
16078 coding system specified with the @code{nnmail-pathname-coding-system}
16079 variable. If it is @code{nil}, in Emacs the coding system defaults to
16080 the value of @code{default-file-name-coding-system}. If you are using
16081 XEmacs and want to use non-@acronym{ASCII} group names, you should set
16082 the value for the @code{nnmail-pathname-coding-system} variable properly.
16085 You can also use the following commands to import and export your
16086 subscriptions from a file in @acronym{OPML} format (Outline Processor
16089 @defun nnrss-opml-import file
16090 Prompt for an @acronym{OPML} file, and subscribe to each feed in the
16094 @defun nnrss-opml-export
16095 Write your current @acronym{RSS} subscriptions to a buffer in
16096 @acronym{OPML} format.
16099 The following @code{nnrss} variables can be altered:
16102 @item nnrss-directory
16103 @vindex nnrss-directory
16104 The directory where @code{nnrss} stores its files. The default is
16105 @file{~/News/rss/}.
16107 @item nnrss-file-coding-system
16108 @vindex nnrss-file-coding-system
16109 The coding system used when reading and writing the @code{nnrss} groups
16110 data files. The default is the value of
16111 @code{mm-universal-coding-system} (which defaults to @code{emacs-mule}
16112 in Emacs or @code{escape-quoted} in XEmacs).
16114 @item nnrss-use-local
16115 @vindex nnrss-use-local
16116 @findex nnrss-generate-download-script
16117 If you set @code{nnrss-use-local} to @code{t}, @code{nnrss} will read
16118 the feeds from local files in @code{nnrss-directory}. You can use
16119 the command @code{nnrss-generate-download-script} to generate a
16120 download script using @command{wget}.
16123 The following code may be helpful, if you want to show the description in
16124 the summary buffer.
16127 (add-to-list 'nnmail-extra-headers nnrss-description-field)
16128 (setq gnus-summary-line-format "%U%R%z%I%(%[%4L: %-15,15f%]%) %s%uX\n")
16130 (defun gnus-user-format-function-X (header)
16132 (assq nnrss-description-field (mail-header-extra header))))
16133 (if descr (concat "\n\t" (cdr descr)) "")))
16136 The following code may be useful to open an nnrss url directly from the
16139 (require 'browse-url)
16141 (defun browse-nnrss-url( arg )
16143 (let ((url (assq nnrss-url-field
16146 (assq (gnus-summary-article-number)
16147 gnus-newsgroup-data))))))
16150 (browse-url (cdr url))
16151 (gnus-summary-mark-as-read-forward 1))
16152 (gnus-summary-scroll-up arg))))
16154 (eval-after-load "gnus"
16155 #'(define-key gnus-summary-mode-map
16156 (kbd "<RET>") 'browse-nnrss-url))
16157 (add-to-list 'nnmail-extra-headers nnrss-url-field)
16160 @node Customizing w3
16161 @subsection Customizing w3
16167 Gnus uses the url library to fetch web pages and Emacs/w3 to display web
16168 pages. Emacs/w3 is documented in its own manual, but there are some
16169 things that may be more relevant for Gnus users.
16171 For instance, a common question is how to make Emacs/w3 follow links
16172 using the @code{browse-url} functions (which will call some external web
16173 browser like Netscape). Here's one way:
16176 (eval-after-load "w3"
16178 (fset 'w3-fetch-orig (symbol-function 'w3-fetch))
16179 (defun w3-fetch (&optional url target)
16180 (interactive (list (w3-read-url-with-default)))
16181 (if (eq major-mode 'gnus-article-mode)
16183 (w3-fetch-orig url target)))))
16186 Put that in your @file{.emacs} file, and hitting links in w3-rendered
16187 @acronym{HTML} in the Gnus article buffers will use @code{browse-url} to
16194 @cindex @acronym{IMAP}
16196 @acronym{IMAP} is a network protocol for reading mail (or news, or @dots{}),
16197 think of it as a modernized @acronym{NNTP}. Connecting to a @acronym{IMAP}
16198 server is much similar to connecting to a news server, you just
16199 specify the network address of the server.
16201 @acronym{IMAP} has two properties. First, @acronym{IMAP} can do
16202 everything that @acronym{POP} can, it can hence be viewed as a
16203 @acronym{POP++}. Secondly, @acronym{IMAP} is a mail storage protocol,
16204 similar to @acronym{NNTP} being a news storage protocol---however,
16205 @acronym{IMAP} offers more features than @acronym{NNTP} because news
16206 is more or less read-only whereas mail is read-write.
16208 If you want to use @acronym{IMAP} as a @acronym{POP++}, use an imap
16209 entry in @code{mail-sources}. With this, Gnus will fetch mails from
16210 the @acronym{IMAP} server and store them on the local disk. This is
16211 not the usage described in this section---@xref{Mail Sources}.
16213 If you want to use @acronym{IMAP} as a mail storage protocol, use an nnimap
16214 entry in @code{gnus-secondary-select-methods}. With this, Gnus will
16215 manipulate mails stored on the @acronym{IMAP} server. This is the kind of
16216 usage explained in this section.
16218 A server configuration in @file{~/.gnus.el} with a few @acronym{IMAP}
16219 servers might look something like the following. (Note that for
16220 @acronym{TLS}/@acronym{SSL}, you need external programs and libraries,
16224 (setq gnus-secondary-select-methods
16225 '((nnimap "simpleserver") ; @r{no special configuration}
16226 ; @r{perhaps a ssh port forwarded server:}
16228 (nnimap-address "localhost")
16229 (nnimap-server-port 1430))
16230 ; @r{a UW server running on localhost}
16232 (nnimap-server-port 143)
16233 (nnimap-address "localhost")
16234 (nnimap-list-pattern ("INBOX" "mail/*")))
16235 ; @r{anonymous public cyrus server:}
16236 (nnimap "cyrus.andrew.cmu.edu"
16237 (nnimap-authenticator anonymous)
16238 (nnimap-list-pattern "archive.*")
16239 (nnimap-stream network))
16240 ; @r{a ssl server on a non-standard port:}
16242 (nnimap-address "vic20.somewhere.com")
16243 (nnimap-server-port 9930)
16244 (nnimap-stream ssl))))
16247 After defining the new server, you can subscribe to groups on the
16248 server using normal Gnus commands such as @kbd{U} in the Group Buffer
16249 (@pxref{Subscription Commands}) or via the Server Buffer
16250 (@pxref{Server Buffer}).
16252 The following variables can be used to create a virtual @code{nnimap}
16257 @item nnimap-address
16258 @vindex nnimap-address
16260 The address of the remote @acronym{IMAP} server. Defaults to the virtual
16261 server name if not specified.
16263 @item nnimap-server-port
16264 @vindex nnimap-server-port
16265 Port on server to contact. Defaults to port 143, or 993 for @acronym{TLS}/@acronym{SSL}.
16267 Note that this should be an integer, example server specification:
16270 (nnimap "mail.server.com"
16271 (nnimap-server-port 4711))
16274 @item nnimap-list-pattern
16275 @vindex nnimap-list-pattern
16276 String or list of strings of mailboxes to limit available groups to.
16277 This is used when the server has very many mailboxes and you're only
16278 interested in a few---some servers export your home directory via
16279 @acronym{IMAP}, you'll probably want to limit the mailboxes to those in
16280 @file{~/Mail/*} then.
16282 The string can also be a cons of REFERENCE and the string as above, what
16283 REFERENCE is used for is server specific, but on the University of
16284 Washington server it's a directory that will be concatenated with the
16287 Example server specification:
16290 (nnimap "mail.server.com"
16291 (nnimap-list-pattern ("INBOX" "Mail/*" "alt.sex.*"
16292 ("~friend/Mail/" . "list/*"))))
16295 @item nnimap-stream
16296 @vindex nnimap-stream
16297 The type of stream used to connect to your server. By default, nnimap
16298 will detect and automatically use all of the below, with the exception
16299 of @acronym{TLS}/@acronym{SSL}. (@acronym{IMAP} over
16300 @acronym{TLS}/@acronym{SSL} is being replaced by STARTTLS, which can
16301 be automatically detected, but it's not widely deployed yet.)
16303 Example server specification:
16306 (nnimap "mail.server.com"
16307 (nnimap-stream ssl))
16310 Please note that the value of @code{nnimap-stream} is a symbol!
16314 @dfn{gssapi:} Connect with GSSAPI (usually Kerberos 5). Requires the
16315 @samp{gsasl} or @samp{imtest} program.
16317 @dfn{kerberos4:} Connect with Kerberos 4. Requires the @samp{imtest} program.
16319 @dfn{starttls:} Connect via the STARTTLS extension (similar to
16320 @acronym{TLS}/@acronym{SSL}). Requires the external library @samp{starttls.el} and program
16323 @dfn{tls:} Connect through @acronym{TLS}. Requires GNUTLS (the program
16324 @samp{gnutls-cli}).
16326 @dfn{ssl:} Connect through @acronym{SSL}. Requires OpenSSL (the program
16327 @samp{openssl}) or SSLeay (@samp{s_client}).
16329 @dfn{shell:} Use a shell command to start @acronym{IMAP} connection.
16331 @dfn{network:} Plain, TCP/IP network connection.
16334 @vindex imap-kerberos4-program
16335 The @samp{imtest} program is shipped with Cyrus IMAPD. If you're
16336 using @samp{imtest} from Cyrus IMAPD < 2.0.14 (which includes version
16337 1.5.x and 1.6.x) you need to frob @code{imap-process-connection-type}
16338 to make @code{imap.el} use a pty instead of a pipe when communicating
16339 with @samp{imtest}. You will then suffer from a line length
16340 restrictions on @acronym{IMAP} commands, which might make Gnus seem to hang
16341 indefinitely if you have many articles in a mailbox. The variable
16342 @code{imap-kerberos4-program} contain parameters to pass to the imtest
16345 For @acronym{TLS} connection, the @code{gnutls-cli} program from GNUTLS is
16346 needed. It is available from
16347 @uref{http://www.gnu.org/software/gnutls/}.
16349 @vindex imap-gssapi-program
16350 This parameter specifies a list of command lines that invoke a GSSAPI
16351 authenticated @acronym{IMAP} stream in a subshell. They are tried
16352 sequentially until a connection is made, or the list has been
16353 exhausted. By default, @samp{gsasl} from GNU SASL, available from
16354 @uref{http://www.gnu.org/software/gsasl/}, and the @samp{imtest}
16355 program from Cyrus IMAPD (see @code{imap-kerberos4-program}), are
16358 @vindex imap-ssl-program
16359 For @acronym{SSL} connections, the OpenSSL program is available from
16360 @uref{http://www.openssl.org/}. OpenSSL was formerly known as SSLeay,
16361 and nnimap support it too---although the most recent versions of
16362 SSLeay, 0.9.x, are known to have serious bugs making it
16363 useless. Earlier versions, especially 0.8.x, of SSLeay are known to
16364 work. The variable @code{imap-ssl-program} contain parameters to pass
16367 @vindex imap-shell-program
16368 @vindex imap-shell-host
16369 For @acronym{IMAP} connections using the @code{shell} stream, the variable
16370 @code{imap-shell-program} specify what program to call.
16372 @item nnimap-authenticator
16373 @vindex nnimap-authenticator
16375 The authenticator used to connect to the server. By default, nnimap
16376 will use the most secure authenticator your server is capable of.
16378 Example server specification:
16381 (nnimap "mail.server.com"
16382 (nnimap-authenticator anonymous))
16385 Please note that the value of @code{nnimap-authenticator} is a symbol!
16389 @dfn{gssapi:} GSSAPI (usually kerberos 5) authentication. Requires
16390 external program @code{gsasl} or @code{imtest}.
16392 @dfn{kerberos4:} Kerberos 4 authentication. Requires external program
16395 @dfn{digest-md5:} Encrypted username/password via DIGEST-MD5. Requires
16396 external library @code{digest-md5.el}.
16398 @dfn{cram-md5:} Encrypted username/password via CRAM-MD5.
16400 @dfn{login:} Plain-text username/password via LOGIN.
16402 @dfn{anonymous:} Login as ``anonymous'', supplying your email address as password.
16405 @item nnimap-expunge-on-close
16407 @vindex nnimap-expunge-on-close
16408 Unlike Parmenides the @acronym{IMAP} designers have decided things that
16409 don't exist actually do exist. More specifically, @acronym{IMAP} has
16410 this concept of marking articles @code{Deleted} which doesn't actually
16411 delete them, and this (marking them @code{Deleted}, that is) is what
16412 nnimap does when you delete an article in Gnus (with @kbd{B DEL} or
16415 Since the articles aren't really removed when we mark them with the
16416 @code{Deleted} flag we'll need a way to actually delete them. Feel like
16417 running in circles yet?
16419 Traditionally, nnimap has removed all articles marked as @code{Deleted}
16420 when closing a mailbox but this is now configurable by this server
16423 The possible options are:
16428 The default behavior, delete all articles marked as ``Deleted'' when
16431 Never actually delete articles. Currently there is no way of showing
16432 the articles marked for deletion in nnimap, but other @acronym{IMAP} clients
16433 may allow you to do this. If you ever want to run the EXPUNGE command
16434 manually, @xref{Expunging mailboxes}.
16436 When closing mailboxes, nnimap will ask if you wish to expunge deleted
16441 @item nnimap-importantize-dormant
16442 @vindex nnimap-importantize-dormant
16444 If non-@code{nil} (the default), marks dormant articles as ticked (as
16445 well), for other @acronym{IMAP} clients. Within Gnus, dormant articles will
16446 naturally still (only) be marked as dormant. This is to make dormant
16447 articles stand out, just like ticked articles, in other @acronym{IMAP}
16448 clients. (In other words, Gnus has two ``Tick'' marks and @acronym{IMAP}
16451 Probably the only reason for frobing this would be if you're trying
16452 enable per-user persistent dormant flags, using something like:
16455 (setcdr (assq 'dormant nnimap-mark-to-flag-alist)
16456 (format "gnus-dormant-%s" (user-login-name)))
16457 (setcdr (assq 'dormant nnimap-mark-to-predicate-alist)
16458 (format "KEYWORD gnus-dormant-%s" (user-login-name)))
16461 In this case, you would not want the per-user dormant flag showing up
16462 as ticked for other users.
16464 @item nnimap-expunge-search-string
16466 @vindex nnimap-expunge-search-string
16468 This variable contain the @acronym{IMAP} search command sent to server when
16469 searching for articles eligible for expiring. The default is
16470 @code{"UID %s NOT SINCE %s"}, where the first @code{%s} is replaced by
16471 UID set and the second @code{%s} is replaced by a date.
16473 Probably the only useful value to change this to is
16474 @code{"UID %s NOT SENTSINCE %s"}, which makes nnimap use the Date: in
16475 messages instead of the internal article date. See section 6.4.4 of
16476 RFC 2060 for more information on valid strings.
16478 @item nnimap-authinfo-file
16479 @vindex nnimap-authinfo-file
16481 A file containing credentials used to log in on servers. The format is
16482 (almost) the same as the @code{ftp} @file{~/.netrc} file. See the
16483 variable @code{nntp-authinfo-file} for exact syntax; also see
16484 @ref{NNTP}. An example of an .authinfo line for an IMAP server, is:
16487 machine students.uio.no login larsi password geheimnis port imap
16490 Note that it should be @code{port imap}, or @code{port 143}, if you
16491 use a @code{nnimap-stream} of @code{tls} or @code{ssl}, even if the
16492 actual port number used is port 993 for secured IMAP. For
16493 convenience, Gnus will accept @code{port imaps} as a synonym of
16496 @item nnimap-need-unselect-to-notice-new-mail
16497 @vindex nnimap-need-unselect-to-notice-new-mail
16499 Unselect mailboxes before looking for new mail in them. Some servers
16500 seem to need this under some circumstances; it was reported that
16506 * Splitting in IMAP:: Splitting mail with nnimap.
16507 * Expiring in IMAP:: Expiring mail with nnimap.
16508 * Editing IMAP ACLs:: Limiting/enabling other users access to a mailbox.
16509 * Expunging mailboxes:: Equivalent of a ``compress mailbox'' button.
16510 * A note on namespaces:: How to (not) use @acronym{IMAP} namespace in Gnus.
16511 * Debugging IMAP:: What to do when things don't work.
16516 @node Splitting in IMAP
16517 @subsection Splitting in IMAP
16518 @cindex splitting imap mail
16520 Splitting is something Gnus users have loved and used for years, and now
16521 the rest of the world is catching up. Yeah, dream on, not many
16522 @acronym{IMAP} servers have server side splitting and those that have
16523 splitting seem to use some non-standard protocol. This means that
16524 @acronym{IMAP} support for Gnus has to do its own splitting.
16528 (Incidentally, people seem to have been dreaming on, and Sieve has
16529 gaining a market share and is supported by several IMAP servers.
16530 Fortunately, Gnus support it too, @xref{Sieve Commands}.)
16532 Here are the variables of interest:
16536 @item nnimap-split-crosspost
16537 @cindex splitting, crosspost
16539 @vindex nnimap-split-crosspost
16541 If non-@code{nil}, do crossposting if several split methods match the
16542 mail. If @code{nil}, the first match in @code{nnimap-split-rule}
16543 found will be used.
16545 Nnmail equivalent: @code{nnmail-crosspost}.
16547 @item nnimap-split-inbox
16548 @cindex splitting, inbox
16550 @vindex nnimap-split-inbox
16552 A string or a list of strings that gives the name(s) of @acronym{IMAP}
16553 mailboxes to split from. Defaults to @code{nil}, which means that
16554 splitting is disabled!
16557 (setq nnimap-split-inbox
16558 '("INBOX" ("~/friend/Mail" . "lists/*") "lists.imap"))
16561 No nnmail equivalent.
16563 @item nnimap-split-rule
16564 @cindex splitting, rules
16565 @vindex nnimap-split-rule
16567 New mail found in @code{nnimap-split-inbox} will be split according to
16570 This variable contains a list of lists, where the first element in the
16571 sublist gives the name of the @acronym{IMAP} mailbox to move articles
16572 matching the regexp in the second element in the sublist. Got that?
16573 Neither did I, we need examples.
16576 (setq nnimap-split-rule
16578 "^Sender: owner-nnimap@@vic20.globalcom.se")
16579 ("INBOX.junk" "^Subject:.*MAKE MONEY")
16580 ("INBOX.private" "")))
16583 This will put all articles from the nnimap mailing list into mailbox
16584 INBOX.nnimap, all articles containing MAKE MONEY in the Subject: line
16585 into INBOX.junk and everything else in INBOX.private.
16587 The first string may contain @samp{\\1} forms, like the ones used by
16588 replace-match to insert sub-expressions from the matched text. For
16592 ("INBOX.lists.\\1" "^Sender: owner-\\([a-z-]+\\)@@")
16595 The first element can also be the symbol @code{junk} to indicate that
16596 matching messages should simply be deleted. Use with care.
16598 The second element can also be a function. In that case, it will be
16599 called with the first element of the rule as the argument, in a buffer
16600 containing the headers of the article. It should return a
16601 non-@code{nil} value if it thinks that the mail belongs in that group.
16603 Nnmail users might recollect that the last regexp had to be empty to
16604 match all articles (like in the example above). This is not required in
16605 nnimap. Articles not matching any of the regexps will not be moved out
16606 of your inbox. (This might affect performance if you keep lots of
16607 unread articles in your inbox, since the splitting code would go over
16608 them every time you fetch new mail.)
16610 These rules are processed from the beginning of the alist toward the
16611 end. The first rule to make a match will ``win'', unless you have
16612 crossposting enabled. In that case, all matching rules will ``win''.
16614 This variable can also have a function as its value, the function will
16615 be called with the headers narrowed and should return a group where it
16616 thinks the article should be split to. See @code{nnimap-split-fancy}.
16618 The splitting code tries to create mailboxes if it needs to.
16620 To allow for different split rules on different virtual servers, and
16621 even different split rules in different inboxes on the same server,
16622 the syntax of this variable have been extended along the lines of:
16625 (setq nnimap-split-rule
16626 '(("my1server" (".*" (("ding" "ding@@gnus.org")
16627 ("junk" "From:.*Simon"))))
16628 ("my2server" ("INBOX" nnimap-split-fancy))
16629 ("my[34]server" (".*" (("private" "To:.*Simon")
16630 ("junk" my-junk-func))))))
16633 The virtual server name is in fact a regexp, so that the same rules
16634 may apply to several servers. In the example, the servers
16635 @code{my3server} and @code{my4server} both use the same rules.
16636 Similarly, the inbox string is also a regexp. The actual splitting
16637 rules are as before, either a function, or a list with group/regexp or
16638 group/function elements.
16640 Nnmail equivalent: @code{nnmail-split-methods}.
16642 @item nnimap-split-predicate
16644 @vindex nnimap-split-predicate
16646 Mail matching this predicate in @code{nnimap-split-inbox} will be
16647 split, it is a string and the default is @samp{UNSEEN UNDELETED}.
16649 This might be useful if you use another @acronym{IMAP} client to read mail in
16650 your inbox but would like Gnus to split all articles in the inbox
16651 regardless of readedness. Then you might change this to
16654 @item nnimap-split-fancy
16655 @cindex splitting, fancy
16656 @findex nnimap-split-fancy
16657 @vindex nnimap-split-fancy
16659 It's possible to set @code{nnimap-split-rule} to
16660 @code{nnmail-split-fancy} if you want to use fancy
16661 splitting. @xref{Fancy Mail Splitting}.
16663 However, to be able to have different fancy split rules for nnmail and
16664 nnimap back ends you can set @code{nnimap-split-rule} to
16665 @code{nnimap-split-fancy} and define the nnimap specific fancy split
16666 rule in @code{nnimap-split-fancy}.
16671 (setq nnimap-split-rule 'nnimap-split-fancy
16672 nnimap-split-fancy ...)
16675 Nnmail equivalent: @code{nnmail-split-fancy}.
16677 @item nnimap-split-download-body
16678 @findex nnimap-split-download-body
16679 @vindex nnimap-split-download-body
16681 Set to non-@code{nil} to download entire articles during splitting.
16682 This is generally not required, and will slow things down
16683 considerably. You may need it if you want to use an advanced
16684 splitting function that analyzes the body to split the article.
16688 @node Expiring in IMAP
16689 @subsection Expiring in IMAP
16690 @cindex expiring imap mail
16692 Even though @code{nnimap} is not a proper @code{nnmail} derived back
16693 end, it supports most features in regular expiring (@pxref{Expiring
16694 Mail}). Unlike splitting in @acronym{IMAP} (@pxref{Splitting in
16695 IMAP}) it does not clone the @code{nnmail} variables (i.e., creating
16696 @var{nnimap-expiry-wait}) but reuse the @code{nnmail} variables. What
16697 follows below are the variables used by the @code{nnimap} expiry
16700 A note on how the expire mark is stored on the @acronym{IMAP} server is
16701 appropriate here as well. The expire mark is translated into a
16702 @code{imap} client specific mark, @code{gnus-expire}, and stored on the
16703 message. This means that likely only Gnus will understand and treat
16704 the @code{gnus-expire} mark properly, although other clients may allow
16705 you to view client specific flags on the message. It also means that
16706 your server must support permanent storage of client specific flags on
16707 messages. Most do, fortunately.
16711 @item nnmail-expiry-wait
16712 @item nnmail-expiry-wait-function
16714 These variables are fully supported. The expire value can be a
16715 number, the symbol @code{immediate} or @code{never}.
16717 @item nnmail-expiry-target
16719 This variable is supported, and internally implemented by calling the
16720 @code{nnmail} functions that handle this. It contains an optimization
16721 that if the destination is a @acronym{IMAP} group on the same server, the
16722 article is copied instead of appended (that is, uploaded again).
16726 @node Editing IMAP ACLs
16727 @subsection Editing IMAP ACLs
16728 @cindex editing imap acls
16729 @cindex Access Control Lists
16730 @cindex Editing @acronym{IMAP} ACLs
16731 @kindex G l (Group)
16732 @findex gnus-group-nnimap-edit-acl
16734 ACL stands for Access Control List. ACLs are used in @acronym{IMAP} for
16735 limiting (or enabling) other users access to your mail boxes. Not all
16736 @acronym{IMAP} servers support this, this function will give an error if it
16739 To edit an ACL for a mailbox, type @kbd{G l}
16740 (@code{gnus-group-edit-nnimap-acl}) and you'll be presented with an ACL
16741 editing window with detailed instructions.
16743 Some possible uses:
16747 Giving ``anyone'' the ``lrs'' rights (lookup, read, keep seen/unseen flags)
16748 on your mailing list mailboxes enables other users on the same server to
16749 follow the list without subscribing to it.
16751 At least with the Cyrus server, you are required to give the user
16752 ``anyone'' posting ("p") capabilities to have ``plussing'' work (that is,
16753 mail sent to user+mailbox@@domain ending up in the @acronym{IMAP} mailbox
16757 @node Expunging mailboxes
16758 @subsection Expunging mailboxes
16762 @cindex manual expunging
16763 @kindex G x (Group)
16764 @findex gnus-group-nnimap-expunge
16766 If you're using the @code{never} setting of @code{nnimap-expunge-on-close},
16767 you may want the option of expunging all deleted articles in a mailbox
16768 manually. This is exactly what @kbd{G x} does.
16770 Currently there is no way of showing deleted articles, you can just
16773 @node A note on namespaces
16774 @subsection A note on namespaces
16775 @cindex IMAP namespace
16778 The @acronym{IMAP} protocol has a concept called namespaces, described
16779 by the following text in the RFC:
16782 5.1.2. Mailbox Namespace Naming Convention
16784 By convention, the first hierarchical element of any mailbox name
16785 which begins with "#" identifies the "namespace" of the remainder of
16786 the name. This makes it possible to disambiguate between different
16787 types of mailbox stores, each of which have their own namespaces.
16789 For example, implementations which offer access to USENET
16790 newsgroups MAY use the "#news" namespace to partition the USENET
16791 newsgroup namespace from that of other mailboxes. Thus, the
16792 comp.mail.misc newsgroup would have an mailbox name of
16793 "#news.comp.mail.misc", and the name "comp.mail.misc" could refer
16794 to a different object (e.g. a user's private mailbox).
16797 While there is nothing in this text that warrants concern for the
16798 @acronym{IMAP} implementation in Gnus, some servers use namespace
16799 prefixes in a way that does not work with how Gnus uses mailbox names.
16801 Specifically, University of Washington's @acronym{IMAP} server uses
16802 mailbox names like @code{#driver.mbx/read-mail} which are valid only
16803 in the @sc{create} and @sc{append} commands. After the mailbox is
16804 created (or a messages is appended to a mailbox), it must be accessed
16805 without the namespace prefix, i.e. @code{read-mail}. Since Gnus do
16806 not make it possible for the user to guarantee that user entered
16807 mailbox names will only be used with the CREATE and APPEND commands,
16808 you should simply not use the namespace prefixed mailbox names in
16811 See the UoW IMAPD documentation for the @code{#driver.*/} prefix
16812 for more information on how to use the prefixes. They are a power
16813 tool and should be used only if you are sure what the effects are.
16815 @node Debugging IMAP
16816 @subsection Debugging IMAP
16817 @cindex IMAP debugging
16818 @cindex protocol dump (IMAP)
16820 @acronym{IMAP} is a complex protocol, more so than @acronym{NNTP} or
16821 @acronym{POP3}. Implementation bugs are not unlikely, and we do our
16822 best to fix them right away. If you encounter odd behavior, chances
16823 are that either the server or Gnus is buggy.
16825 If you are familiar with network protocols in general, you will
16826 probably be able to extract some clues from the protocol dump of the
16827 exchanges between Gnus and the server. Even if you are not familiar
16828 with network protocols, when you include the protocol dump in
16829 @acronym{IMAP}-related bug reports you are helping us with data
16830 critical to solving the problem. Therefore, we strongly encourage you
16831 to include the protocol dump when reporting IMAP bugs in Gnus.
16835 Because the protocol dump, when enabled, generates lots of data, it is
16836 disabled by default. You can enable it by setting @code{imap-log} as
16843 This instructs the @code{imap.el} package to log any exchanges with
16844 the server. The log is stored in the buffer @samp{*imap-log*}. Look
16845 for error messages, which sometimes are tagged with the keyword
16846 @code{BAD}---but when submitting a bug, make sure to include all the
16849 @node Other Sources
16850 @section Other Sources
16852 Gnus can do more than just read news or mail. The methods described
16853 below allow Gnus to view directories and files as if they were
16857 * Directory Groups:: You can read a directory as if it was a newsgroup.
16858 * Anything Groups:: Dired? Who needs dired?
16859 * Document Groups:: Single files can be the basis of a group.
16860 * SOUP:: Reading @sc{soup} packets ``offline''.
16861 * Mail-To-News Gateways:: Posting articles via mail-to-news gateways.
16865 @node Directory Groups
16866 @subsection Directory Groups
16868 @cindex directory groups
16870 If you have a directory that has lots of articles in separate files in
16871 it, you might treat it as a newsgroup. The files have to have numerical
16874 This might be an opportune moment to mention @code{ange-ftp} (and its
16875 successor @code{efs}), that most wonderful of all wonderful Emacs
16876 packages. When I wrote @code{nndir}, I didn't think much about it---a
16877 back end to read directories. Big deal.
16879 @code{ange-ftp} changes that picture dramatically. For instance, if you
16880 enter the @code{ange-ftp} file name
16881 @file{/ftp.hpc.uh.edu:/pub/emacs/ding-list/} as the directory name,
16882 @code{ange-ftp} or @code{efs} will actually allow you to read this
16883 directory over at @samp{sina} as a newsgroup. Distributed news ahoy!
16885 @code{nndir} will use @acronym{NOV} files if they are present.
16887 @code{nndir} is a ``read-only'' back end---you can't delete or expire
16888 articles with this method. You can use @code{nnmh} or @code{nnml} for
16889 whatever you use @code{nndir} for, so you could switch to any of those
16890 methods if you feel the need to have a non-read-only @code{nndir}.
16893 @node Anything Groups
16894 @subsection Anything Groups
16897 From the @code{nndir} back end (which reads a single spool-like
16898 directory), it's just a hop and a skip to @code{nneething}, which
16899 pretends that any arbitrary directory is a newsgroup. Strange, but
16902 When @code{nneething} is presented with a directory, it will scan this
16903 directory and assign article numbers to each file. When you enter such
16904 a group, @code{nneething} must create ``headers'' that Gnus can use.
16905 After all, Gnus is a newsreader, in case you're forgetting.
16906 @code{nneething} does this in a two-step process. First, it snoops each
16907 file in question. If the file looks like an article (i.e., the first
16908 few lines look like headers), it will use this as the head. If this is
16909 just some arbitrary file without a head (e.g. a C source file),
16910 @code{nneething} will cobble up a header out of thin air. It will use
16911 file ownership, name and date and do whatever it can with these
16914 All this should happen automatically for you, and you will be presented
16915 with something that looks very much like a newsgroup. Totally like a
16916 newsgroup, to be precise. If you select an article, it will be displayed
16917 in the article buffer, just as usual.
16919 If you select a line that represents a directory, Gnus will pop you into
16920 a new summary buffer for this @code{nneething} group. And so on. You can
16921 traverse the entire disk this way, if you feel like, but remember that
16922 Gnus is not dired, really, and does not intend to be, either.
16924 There are two overall modes to this action---ephemeral or solid. When
16925 doing the ephemeral thing (i.e., @kbd{G D} from the group buffer), Gnus
16926 will not store information on what files you have read, and what files
16927 are new, and so on. If you create a solid @code{nneething} group the
16928 normal way with @kbd{G m}, Gnus will store a mapping table between
16929 article numbers and file names, and you can treat this group like any
16930 other groups. When you activate a solid @code{nneething} group, you will
16931 be told how many unread articles it contains, etc., etc.
16936 @item nneething-map-file-directory
16937 @vindex nneething-map-file-directory
16938 All the mapping files for solid @code{nneething} groups will be stored
16939 in this directory, which defaults to @file{~/.nneething/}.
16941 @item nneething-exclude-files
16942 @vindex nneething-exclude-files
16943 All files that match this regexp will be ignored. Nice to use to exclude
16944 auto-save files and the like, which is what it does by default.
16946 @item nneething-include-files
16947 @vindex nneething-include-files
16948 Regexp saying what files to include in the group. If this variable is
16949 non-@code{nil}, only files matching this regexp will be included.
16951 @item nneething-map-file
16952 @vindex nneething-map-file
16953 Name of the map files.
16957 @node Document Groups
16958 @subsection Document Groups
16960 @cindex documentation group
16963 @code{nndoc} is a cute little thing that will let you read a single file
16964 as a newsgroup. Several files types are supported:
16971 The Babyl (Rmail) mail box.
16976 The standard Unix mbox file.
16978 @cindex MMDF mail box
16980 The MMDF mail box format.
16983 Several news articles appended into a file.
16986 @cindex rnews batch files
16987 The rnews batch transport format.
16988 @cindex forwarded messages
16991 Forwarded articles.
16994 Netscape mail boxes.
16997 @acronym{MIME} multipart messages.
16999 @item standard-digest
17000 The standard (RFC 1153) digest format.
17003 A @acronym{MIME} digest of messages.
17005 @item lanl-gov-announce
17006 Announcement messages from LANL Gov Announce.
17008 @item rfc822-forward
17009 A message forwarded according to RFC822.
17012 The Outlook mail box.
17015 The Outlook Express dbx mail box.
17018 A bounce message from the Exim MTA.
17021 A message forwarded according to informal rules.
17024 An RFC934-forwarded message.
17030 A digest of Clarinet brief news items.
17033 Non-standard digest format---matches most things, but does it badly.
17039 You can also use the special ``file type'' @code{guess}, which means
17040 that @code{nndoc} will try to guess what file type it is looking at.
17041 @code{digest} means that @code{nndoc} should guess what digest type the
17044 @code{nndoc} will not try to change the file or insert any extra headers into
17045 it---it will simply, like, let you use the file as the basis for a
17046 group. And that's it.
17048 If you have some old archived articles that you want to insert into your
17049 new & spiffy Gnus mail back end, @code{nndoc} can probably help you with
17050 that. Say you have an old @file{RMAIL} file with mail that you now want
17051 to split into your new @code{nnml} groups. You look at that file using
17052 @code{nndoc} (using the @kbd{G f} command in the group buffer
17053 (@pxref{Foreign Groups})), set the process mark on all the articles in
17054 the buffer (@kbd{M P b}, for instance), and then re-spool (@kbd{B r})
17055 using @code{nnml}. If all goes well, all the mail in the @file{RMAIL}
17056 file is now also stored in lots of @code{nnml} directories, and you can
17057 delete that pesky @file{RMAIL} file. If you have the guts!
17059 Virtual server variables:
17062 @item nndoc-article-type
17063 @vindex nndoc-article-type
17064 This should be one of @code{mbox}, @code{babyl}, @code{digest},
17065 @code{news}, @code{rnews}, @code{mmdf}, @code{forward}, @code{rfc934},
17066 @code{rfc822-forward}, @code{mime-parts}, @code{standard-digest},
17067 @code{slack-digest}, @code{clari-briefs}, @code{nsmail}, @code{outlook},
17068 @code{oe-dbx}, @code{mailman}, and @code{mail-in-mail} or @code{guess}.
17070 @item nndoc-post-type
17071 @vindex nndoc-post-type
17072 This variable says whether Gnus is to consider the group a news group or
17073 a mail group. There are two valid values: @code{mail} (the default)
17078 * Document Server Internals:: How to add your own document types.
17082 @node Document Server Internals
17083 @subsubsection Document Server Internals
17085 Adding new document types to be recognized by @code{nndoc} isn't
17086 difficult. You just have to whip up a definition of what the document
17087 looks like, write a predicate function to recognize that document type,
17088 and then hook into @code{nndoc}.
17090 First, here's an example document type definition:
17094 (article-begin . "^\^A\^A\^A\^A\n")
17095 (body-end . "^\^A\^A\^A\^A\n"))
17098 The definition is simply a unique @dfn{name} followed by a series of
17099 regexp pseudo-variable settings. Below are the possible
17100 variables---don't be daunted by the number of variables; most document
17101 types can be defined with very few settings:
17104 @item first-article
17105 If present, @code{nndoc} will skip past all text until it finds
17106 something that match this regexp. All text before this will be
17109 @item article-begin
17110 This setting has to be present in all document type definitions. It
17111 says what the beginning of each article looks like.
17113 @item head-begin-function
17114 If present, this should be a function that moves point to the head of
17117 @item nndoc-head-begin
17118 If present, this should be a regexp that matches the head of the
17121 @item nndoc-head-end
17122 This should match the end of the head of the article. It defaults to
17123 @samp{^$}---the empty line.
17125 @item body-begin-function
17126 If present, this function should move point to the beginning of the body
17130 This should match the beginning of the body of the article. It defaults
17133 @item body-end-function
17134 If present, this function should move point to the end of the body of
17138 If present, this should match the end of the body of the article.
17141 If present, this should match the end of the file. All text after this
17142 regexp will be totally ignored.
17146 So, using these variables @code{nndoc} is able to dissect a document
17147 file into a series of articles, each with a head and a body. However, a
17148 few more variables are needed since not all document types are all that
17149 news-like---variables needed to transform the head or the body into
17150 something that's palatable for Gnus:
17153 @item prepare-body-function
17154 If present, this function will be called when requesting an article. It
17155 will be called with point at the start of the body, and is useful if the
17156 document has encoded some parts of its contents.
17158 @item article-transform-function
17159 If present, this function is called when requesting an article. It's
17160 meant to be used for more wide-ranging transformation of both head and
17161 body of the article.
17163 @item generate-head-function
17164 If present, this function is called to generate a head that Gnus can
17165 understand. It is called with the article number as a parameter, and is
17166 expected to generate a nice head for the article in question. It is
17167 called when requesting the headers of all articles.
17171 Let's look at the most complicated example I can come up with---standard
17176 (first-article . ,(concat "^" (make-string 70 ?-) "\n\n+"))
17177 (article-begin . ,(concat "\n\n" (make-string 30 ?-) "\n\n+"))
17178 (prepare-body-function . nndoc-unquote-dashes)
17179 (body-end-function . nndoc-digest-body-end)
17180 (head-end . "^ ?$")
17181 (body-begin . "^ ?\n")
17182 (file-end . "^End of .*digest.*[0-9].*\n\\*\\*\\|^End of.*Digest *$")
17183 (subtype digest guess))
17186 We see that all text before a 70-width line of dashes is ignored; all
17187 text after a line that starts with that @samp{^End of} is also ignored;
17188 each article begins with a 30-width line of dashes; the line separating
17189 the head from the body may contain a single space; and that the body is
17190 run through @code{nndoc-unquote-dashes} before being delivered.
17192 To hook your own document definition into @code{nndoc}, use the
17193 @code{nndoc-add-type} function. It takes two parameters---the first
17194 is the definition itself and the second (optional) parameter says
17195 where in the document type definition alist to put this definition.
17196 The alist is traversed sequentially, and
17197 @code{nndoc-@var{type}-type-p} is called for a given type @var{type}.
17198 So @code{nndoc-mmdf-type-p} is called to see whether a document is of
17199 @code{mmdf} type, and so on. These type predicates should return
17200 @code{nil} if the document is not of the correct type; @code{t} if it
17201 is of the correct type; and a number if the document might be of the
17202 correct type. A high number means high probability; a low number
17203 means low probability with @samp{0} being the lowest valid number.
17211 In the PC world people often talk about ``offline'' newsreaders. These
17212 are thingies that are combined reader/news transport monstrosities.
17213 With built-in modem programs. Yecchh!
17215 Of course, us Unix Weenie types of human beans use things like
17216 @code{uucp} and, like, @code{nntpd} and set up proper news and mail
17217 transport things like Ghod intended. And then we just use normal
17220 However, it can sometimes be convenient to do something that's a bit
17221 easier on the brain if you have a very slow modem, and you're not really
17222 that interested in doing things properly.
17224 A file format called @sc{soup} has been developed for transporting news
17225 and mail from servers to home machines and back again. It can be a bit
17228 First some terminology:
17233 This is the machine that is connected to the outside world and where you
17234 get news and/or mail from.
17237 This is the machine that you want to do the actual reading and responding
17238 on. It is typically not connected to the rest of the world in any way.
17241 Something that contains messages and/or commands. There are two kinds
17245 @item message packets
17246 These are packets made at the server, and typically contain lots of
17247 messages for you to read. These are called @file{SoupoutX.tgz} by
17248 default, where @var{x} is a number.
17250 @item response packets
17251 These are packets made at the home machine, and typically contains
17252 replies that you've written. These are called @file{SoupinX.tgz} by
17253 default, where @var{x} is a number.
17263 You log in on the server and create a @sc{soup} packet. You can either
17264 use a dedicated @sc{soup} thingie (like the @code{awk} program), or you
17265 can use Gnus to create the packet with its @sc{soup} commands (@kbd{O
17266 s} and/or @kbd{G s b}; and then @kbd{G s p}) (@pxref{SOUP Commands}).
17269 You transfer the packet home. Rail, boat, car or modem will do fine.
17272 You put the packet in your home directory.
17275 You fire up Gnus on your home machine using the @code{nnsoup} back end as
17276 the native or secondary server.
17279 You read articles and mail and answer and followup to the things you
17280 want (@pxref{SOUP Replies}).
17283 You do the @kbd{G s r} command to pack these replies into a @sc{soup}
17287 You transfer this packet to the server.
17290 You use Gnus to mail this packet out with the @kbd{G s s} command.
17293 You then repeat until you die.
17297 So you basically have a bipartite system---you use @code{nnsoup} for
17298 reading and Gnus for packing/sending these @sc{soup} packets.
17301 * SOUP Commands:: Commands for creating and sending @sc{soup} packets
17302 * SOUP Groups:: A back end for reading @sc{soup} packets.
17303 * SOUP Replies:: How to enable @code{nnsoup} to take over mail and news.
17307 @node SOUP Commands
17308 @subsubsection SOUP Commands
17310 These are commands for creating and manipulating @sc{soup} packets.
17314 @kindex G s b (Group)
17315 @findex gnus-group-brew-soup
17316 Pack all unread articles in the current group
17317 (@code{gnus-group-brew-soup}). This command understands the
17318 process/prefix convention.
17321 @kindex G s w (Group)
17322 @findex gnus-soup-save-areas
17323 Save all @sc{soup} data files (@code{gnus-soup-save-areas}).
17326 @kindex G s s (Group)
17327 @findex gnus-soup-send-replies
17328 Send all replies from the replies packet
17329 (@code{gnus-soup-send-replies}).
17332 @kindex G s p (Group)
17333 @findex gnus-soup-pack-packet
17334 Pack all files into a @sc{soup} packet (@code{gnus-soup-pack-packet}).
17337 @kindex G s r (Group)
17338 @findex nnsoup-pack-replies
17339 Pack all replies into a replies packet (@code{nnsoup-pack-replies}).
17342 @kindex O s (Summary)
17343 @findex gnus-soup-add-article
17344 This summary-mode command adds the current article to a @sc{soup} packet
17345 (@code{gnus-soup-add-article}). It understands the process/prefix
17346 convention (@pxref{Process/Prefix}).
17351 There are a few variables to customize where Gnus will put all these
17356 @item gnus-soup-directory
17357 @vindex gnus-soup-directory
17358 Directory where Gnus will save intermediate files while composing
17359 @sc{soup} packets. The default is @file{~/SoupBrew/}.
17361 @item gnus-soup-replies-directory
17362 @vindex gnus-soup-replies-directory
17363 This is what Gnus will use as a temporary directory while sending our
17364 reply packets. @file{~/SoupBrew/SoupReplies/} is the default.
17366 @item gnus-soup-prefix-file
17367 @vindex gnus-soup-prefix-file
17368 Name of the file where Gnus stores the last used prefix. The default is
17369 @samp{gnus-prefix}.
17371 @item gnus-soup-packer
17372 @vindex gnus-soup-packer
17373 A format string command for packing a @sc{soup} packet. The default is
17374 @samp{tar cf - %s | gzip > $HOME/Soupout%d.tgz}.
17376 @item gnus-soup-unpacker
17377 @vindex gnus-soup-unpacker
17378 Format string command for unpacking a @sc{soup} packet. The default is
17379 @samp{gunzip -c %s | tar xvf -}.
17381 @item gnus-soup-packet-directory
17382 @vindex gnus-soup-packet-directory
17383 Where Gnus will look for reply packets. The default is @file{~/}.
17385 @item gnus-soup-packet-regexp
17386 @vindex gnus-soup-packet-regexp
17387 Regular expression matching @sc{soup} reply packets in
17388 @code{gnus-soup-packet-directory}.
17394 @subsubsection SOUP Groups
17397 @code{nnsoup} is the back end for reading @sc{soup} packets. It will
17398 read incoming packets, unpack them, and put them in a directory where
17399 you can read them at leisure.
17401 These are the variables you can use to customize its behavior:
17405 @item nnsoup-tmp-directory
17406 @vindex nnsoup-tmp-directory
17407 When @code{nnsoup} unpacks a @sc{soup} packet, it does it in this
17408 directory. (@file{/tmp/} by default.)
17410 @item nnsoup-directory
17411 @vindex nnsoup-directory
17412 @code{nnsoup} then moves each message and index file to this directory.
17413 The default is @file{~/SOUP/}.
17415 @item nnsoup-replies-directory
17416 @vindex nnsoup-replies-directory
17417 All replies will be stored in this directory before being packed into a
17418 reply packet. The default is @file{~/SOUP/replies/}.
17420 @item nnsoup-replies-format-type
17421 @vindex nnsoup-replies-format-type
17422 The @sc{soup} format of the replies packets. The default is @samp{?n}
17423 (rnews), and I don't think you should touch that variable. I probably
17424 shouldn't even have documented it. Drats! Too late!
17426 @item nnsoup-replies-index-type
17427 @vindex nnsoup-replies-index-type
17428 The index type of the replies packet. The default is @samp{?n}, which
17429 means ``none''. Don't fiddle with this one either!
17431 @item nnsoup-active-file
17432 @vindex nnsoup-active-file
17433 Where @code{nnsoup} stores lots of information. This is not an ``active
17434 file'' in the @code{nntp} sense; it's an Emacs Lisp file. If you lose
17435 this file or mess it up in any way, you're dead. The default is
17436 @file{~/SOUP/active}.
17438 @item nnsoup-packer
17439 @vindex nnsoup-packer
17440 Format string command for packing a reply @sc{soup} packet. The default
17441 is @samp{tar cf - %s | gzip > $HOME/Soupin%d.tgz}.
17443 @item nnsoup-unpacker
17444 @vindex nnsoup-unpacker
17445 Format string command for unpacking incoming @sc{soup} packets. The
17446 default is @samp{gunzip -c %s | tar xvf -}.
17448 @item nnsoup-packet-directory
17449 @vindex nnsoup-packet-directory
17450 Where @code{nnsoup} will look for incoming packets. The default is
17453 @item nnsoup-packet-regexp
17454 @vindex nnsoup-packet-regexp
17455 Regular expression matching incoming @sc{soup} packets. The default is
17458 @item nnsoup-always-save
17459 @vindex nnsoup-always-save
17460 If non-@code{nil}, save the replies buffer after each posted message.
17466 @subsubsection SOUP Replies
17468 Just using @code{nnsoup} won't mean that your postings and mailings end
17469 up in @sc{soup} reply packets automagically. You have to work a bit
17470 more for that to happen.
17472 @findex nnsoup-set-variables
17473 The @code{nnsoup-set-variables} command will set the appropriate
17474 variables to ensure that all your followups and replies end up in the
17477 In specific, this is what it does:
17480 (setq message-send-news-function 'nnsoup-request-post)
17481 (setq message-send-mail-function 'nnsoup-request-mail)
17484 And that's it, really. If you only want news to go into the @sc{soup}
17485 system you just use the first line. If you only want mail to be
17486 @sc{soup}ed you use the second.
17489 @node Mail-To-News Gateways
17490 @subsection Mail-To-News Gateways
17491 @cindex mail-to-news gateways
17494 If your local @code{nntp} server doesn't allow posting, for some reason
17495 or other, you can post using one of the numerous mail-to-news gateways.
17496 The @code{nngateway} back end provides the interface.
17498 Note that you can't read anything from this back end---it can only be
17504 @item nngateway-address
17505 @vindex nngateway-address
17506 This is the address of the mail-to-news gateway.
17508 @item nngateway-header-transformation
17509 @vindex nngateway-header-transformation
17510 News headers often have to be transformed in some odd way or other
17511 for the mail-to-news gateway to accept it. This variable says what
17512 transformation should be called, and defaults to
17513 @code{nngateway-simple-header-transformation}. The function is called
17514 narrowed to the headers to be transformed and with one parameter---the
17517 This default function just inserts a new @code{To} header based on the
17518 @code{Newsgroups} header and the gateway address.
17519 For instance, an article with this @code{Newsgroups} header:
17522 Newsgroups: alt.religion.emacs
17525 will get this @code{To} header inserted:
17528 To: alt-religion-emacs@@GATEWAY
17531 The following pre-defined functions exist:
17533 @findex nngateway-simple-header-transformation
17536 @item nngateway-simple-header-transformation
17537 Creates a @code{To} header that looks like
17538 @var{newsgroup}@@@code{nngateway-address}.
17540 @findex nngateway-mail2news-header-transformation
17542 @item nngateway-mail2news-header-transformation
17543 Creates a @code{To} header that looks like
17544 @code{nngateway-address}.
17552 (setq gnus-post-method
17554 "mail2news@@replay.com"
17555 (nngateway-header-transformation
17556 nngateway-mail2news-header-transformation)))
17559 So, to use this, simply say something like:
17562 (setq gnus-post-method '(nngateway "GATEWAY.ADDRESS"))
17567 @node Combined Groups
17568 @section Combined Groups
17570 Gnus allows combining a mixture of all the other group types into bigger
17574 * Virtual Groups:: Combining articles from many groups.
17575 * Kibozed Groups:: Looking through parts of the newsfeed for articles.
17579 @node Virtual Groups
17580 @subsection Virtual Groups
17582 @cindex virtual groups
17583 @cindex merging groups
17585 An @dfn{nnvirtual group} is really nothing more than a collection of
17588 For instance, if you are tired of reading many small groups, you can
17589 put them all in one big group, and then grow tired of reading one
17590 big, unwieldy group. The joys of computing!
17592 You specify @code{nnvirtual} as the method. The address should be a
17593 regexp to match component groups.
17595 All marks in the virtual group will stick to the articles in the
17596 component groups. So if you tick an article in a virtual group, the
17597 article will also be ticked in the component group from whence it
17598 came. (And vice versa---marks from the component groups will also be
17599 shown in the virtual group.). To create an empty virtual group, run
17600 @kbd{G V} (@code{gnus-group-make-empty-virtual}) in the group buffer
17601 and edit the method regexp with @kbd{M-e}
17602 (@code{gnus-group-edit-group-method})
17604 Here's an example @code{nnvirtual} method that collects all Andrea Dworkin
17605 newsgroups into one, big, happy newsgroup:
17608 (nnvirtual "^alt\\.fan\\.andrea-dworkin$\\|^rec\\.dworkin.*")
17611 The component groups can be native or foreign; everything should work
17612 smoothly, but if your computer explodes, it was probably my fault.
17614 Collecting the same group from several servers might actually be a good
17615 idea if users have set the Distribution header to limit distribution.
17616 If you would like to read @samp{soc.motss} both from a server in Japan
17617 and a server in Norway, you could use the following as the group regexp:
17620 "^nntp\\+server\\.jp:soc\\.motss$\\|^nntp\\+server\\.no:soc\\.motss$"
17623 (Remember, though, that if you're creating the group with @kbd{G m}, you
17624 shouldn't double the backslashes, and you should leave off the quote
17625 characters at the beginning and the end of the string.)
17627 This should work kinda smoothly---all articles from both groups should
17628 end up in this one, and there should be no duplicates. Threading (and
17629 the rest) will still work as usual, but there might be problems with the
17630 sequence of articles. Sorting on date might be an option here
17631 (@pxref{Selecting a Group}).
17633 One limitation, however---all groups included in a virtual
17634 group have to be alive (i.e., subscribed or unsubscribed). Killed or
17635 zombie groups can't be component groups for @code{nnvirtual} groups.
17637 @vindex nnvirtual-always-rescan
17638 If the @code{nnvirtual-always-rescan} is non-@code{nil},
17639 @code{nnvirtual} will always scan groups for unread articles when
17640 entering a virtual group. If this variable is @code{nil} (which is the
17641 default) and you read articles in a component group after the virtual
17642 group has been activated, the read articles from the component group
17643 will show up when you enter the virtual group. You'll also see this
17644 effect if you have two virtual groups that have a component group in
17645 common. If that's the case, you should set this variable to @code{t}.
17646 Or you can just tap @code{M-g} on the virtual group every time before
17647 you enter it---it'll have much the same effect.
17649 @code{nnvirtual} can have both mail and news groups as component groups.
17650 When responding to articles in @code{nnvirtual} groups, @code{nnvirtual}
17651 has to ask the back end of the component group the article comes from
17652 whether it is a news or mail back end. However, when you do a @kbd{^},
17653 there is typically no sure way for the component back end to know this,
17654 and in that case @code{nnvirtual} tells Gnus that the article came from a
17655 not-news back end. (Just to be on the safe side.)
17657 @kbd{C-c C-n} in the message buffer will insert the @code{Newsgroups}
17658 line from the article you respond to in these cases.
17660 @code{nnvirtual} groups do not inherit anything but articles and marks
17661 from component groups---group parameters, for instance, are not
17665 @node Kibozed Groups
17666 @subsection Kibozed Groups
17670 @dfn{Kibozing} is defined by the @acronym{OED} as ``grepping through
17671 (parts of) the news feed''. @code{nnkiboze} is a back end that will
17672 do this for you. Oh joy! Now you can grind any @acronym{NNTP} server
17673 down to a halt with useless requests! Oh happiness!
17675 @kindex G k (Group)
17676 To create a kibozed group, use the @kbd{G k} command in the group
17679 The address field of the @code{nnkiboze} method is, as with
17680 @code{nnvirtual}, a regexp to match groups to be ``included'' in the
17681 @code{nnkiboze} group. That's where most similarities between
17682 @code{nnkiboze} and @code{nnvirtual} end.
17684 In addition to this regexp detailing component groups, an
17685 @code{nnkiboze} group must have a score file to say what articles are
17686 to be included in the group (@pxref{Scoring}).
17688 @kindex M-x nnkiboze-generate-groups
17689 @findex nnkiboze-generate-groups
17690 You must run @kbd{M-x nnkiboze-generate-groups} after creating the
17691 @code{nnkiboze} groups you want to have. This command will take time.
17692 Lots of time. Oodles and oodles of time. Gnus has to fetch the
17693 headers from all the articles in all the component groups and run them
17694 through the scoring process to determine if there are any articles in
17695 the groups that are to be part of the @code{nnkiboze} groups.
17697 Please limit the number of component groups by using restrictive
17698 regexps. Otherwise your sysadmin may become annoyed with you, and the
17699 @acronym{NNTP} site may throw you off and never let you back in again.
17700 Stranger things have happened.
17702 @code{nnkiboze} component groups do not have to be alive---they can be dead,
17703 and they can be foreign. No restrictions.
17705 @vindex nnkiboze-directory
17706 The generation of an @code{nnkiboze} group means writing two files in
17707 @code{nnkiboze-directory}, which is @file{~/News/kiboze/} by default.
17708 One contains the @acronym{NOV} header lines for all the articles in
17709 the group, and the other is an additional @file{.newsrc} file to store
17710 information on what groups have been searched through to find
17711 component articles.
17713 Articles marked as read in the @code{nnkiboze} group will have
17714 their @acronym{NOV} lines removed from the @acronym{NOV} file.
17717 @node Email Based Diary
17718 @section Email Based Diary
17720 @cindex email based diary
17723 This section describes a special mail back end called @code{nndiary},
17724 and its companion library @code{gnus-diary}. It is ``special'' in the
17725 sense that it is not meant to be one of the standard alternatives for
17726 reading mail with Gnus. See @ref{Choosing a Mail Back End} for that.
17727 Instead, it is used to treat @emph{some} of your mails in a special way,
17728 namely, as event reminders.
17730 Here is a typical scenario:
17734 You've got a date with Andy Mc Dowell or Bruce Willis (select according
17735 to your sexual preference) in one month. You don't want to forget it.
17737 So you send a ``reminder'' message (actually, a diary one) to yourself.
17739 You forget all about it and keep on getting and reading new mail, as usual.
17741 From time to time, as you type `g' in the group buffer and as the date
17742 is getting closer, the message will pop up again to remind you of your
17743 appointment, just as if it were new and unread.
17745 Read your ``new'' messages, this one included, and start dreaming again
17746 of the night you're gonna have.
17748 Once the date is over (you actually fell asleep just after dinner), the
17749 message will be automatically deleted if it is marked as expirable.
17752 The Gnus Diary back end has the ability to handle regular appointments
17753 (that wouldn't ever be deleted) as well as punctual ones, operates as a
17754 real mail back end and is configurable in many ways. All of this is
17755 explained in the sections below.
17758 * The NNDiary Back End:: Basic setup and usage.
17759 * The Gnus Diary Library:: Utility toolkit on top of nndiary.
17760 * Sending or Not Sending:: A final note on sending diary messages.
17764 @node The NNDiary Back End
17765 @subsection The NNDiary Back End
17767 @cindex the nndiary back end
17769 @code{nndiary} is a back end very similar to @code{nnml} (@pxref{Mail
17770 Spool}). Actually, it could appear as a mix of @code{nnml} and
17771 @code{nndraft}. If you know @code{nnml}, you're already familiar with
17772 the message storing scheme of @code{nndiary}: one file per message, one
17773 directory per group.
17775 Before anything, there is one requirement to be able to run
17776 @code{nndiary} properly: you @emph{must} use the group timestamp feature
17777 of Gnus. This adds a timestamp to each group's parameters. @ref{Group
17778 Timestamp} to see how it's done.
17781 * Diary Messages:: What makes a message valid for nndiary.
17782 * Running NNDiary:: NNDiary has two modes of operation.
17783 * Customizing NNDiary:: Bells and whistles.
17786 @node Diary Messages
17787 @subsubsection Diary Messages
17788 @cindex nndiary messages
17789 @cindex nndiary mails
17791 @code{nndiary} messages are just normal ones, except for the mandatory
17792 presence of 7 special headers. These headers are of the form
17793 @code{X-Diary-<something>}, @code{<something>} being one of
17794 @code{Minute}, @code{Hour}, @code{Dom}, @code{Month}, @code{Year},
17795 @code{Time-Zone} and @code{Dow}. @code{Dom} means ``Day of Month'', and
17796 @code{dow} means ``Day of Week''. These headers actually behave like
17797 crontab specifications and define the event date(s):
17801 For all headers except the @code{Time-Zone} one, a header value is
17802 either a star (meaning all possible values), or a list of fields
17803 (separated by a comma).
17805 A field is either an integer, or a range.
17807 A range is two integers separated by a dash.
17809 Possible integer values are 0--59 for @code{Minute}, 0--23 for
17810 @code{Hour}, 1--31 for @code{Dom}, 1--12 for @code{Month}, above 1971
17811 for @code{Year} and 0--6 for @code{Dow} (0 meaning Sunday).
17813 As a special case, a star in either @code{Dom} or @code{Dow} doesn't
17814 mean ``all possible values'', but ``use only the other field''. Note
17815 that if both are star'ed, the use of either one gives the same result.
17817 The @code{Time-Zone} header is special in that it can only have one
17818 value (@code{GMT}, for instance). A star doesn't mean ``all possible
17819 values'' (because it makes no sense), but ``the current local time
17820 zone''. Most of the time, you'll be using a star here. However, for a
17821 list of available time zone values, see the variable
17822 @code{nndiary-headers}.
17825 As a concrete example, here are the diary headers to add to your message
17826 for specifying ``Each Monday and each 1st of month, at 12:00, 20:00,
17827 21:00, 22:00, 23:00 and 24:00, from 1999 to 2010'' (I'll let you find
17832 X-Diary-Hour: 12, 20-24
17835 X-Diary-Year: 1999-2010
17837 X-Diary-Time-Zone: *
17840 @node Running NNDiary
17841 @subsubsection Running NNDiary
17842 @cindex running nndiary
17843 @cindex nndiary operation modes
17845 @code{nndiary} has two modes of operation: ``traditional'' (the default)
17846 and ``autonomous''. In traditional mode, @code{nndiary} does not get new
17847 mail by itself. You have to move (@kbd{B m}) or copy (@kbd{B c}) mails
17848 from your primary mail back end to nndiary groups in order to handle them
17849 as diary messages. In autonomous mode, @code{nndiary} retrieves its own
17850 mail and handles it independently from your primary mail back end.
17852 One should note that Gnus is not inherently designed to allow several
17853 ``master'' mail back ends at the same time. However, this does make
17854 sense with @code{nndiary}: you really want to send and receive diary
17855 messages to your diary groups directly. So, @code{nndiary} supports
17856 being sort of a ``second primary mail back end'' (to my knowledge, it is
17857 the only back end offering this feature). However, there is a limitation
17858 (which I hope to fix some day): respooling doesn't work in autonomous
17861 In order to use @code{nndiary} in autonomous mode, you have several
17866 Allow @code{nndiary} to retrieve new mail by itself. Put the following
17867 line in your @file{gnusrc} file:
17870 (setq nndiary-get-new-mail t)
17873 You must arrange for diary messages (those containing @code{X-Diary-*}
17874 headers) to be split in a private folder @emph{before} Gnus treat them.
17875 Again, this is needed because Gnus cannot (yet ?) properly handle
17876 multiple primary mail back ends. Getting those messages from a separate
17877 source will compensate this misfeature to some extent.
17879 As an example, here's my procmailrc entry to store diary files in
17880 @file{~/.nndiary} (the default @code{nndiary} mail source file):
17889 Once this is done, you might want to customize the following two options
17890 that affect the diary mail retrieval and splitting processes:
17892 @defvar nndiary-mail-sources
17893 This is the diary-specific replacement for the standard
17894 @code{mail-sources} variable. It obeys the same syntax, and defaults to
17895 @code{(file :path "~/.nndiary")}.
17898 @defvar nndiary-split-methods
17899 This is the diary-specific replacement for the standard
17900 @code{nnmail-split-methods} variable. It obeys the same syntax.
17903 Finally, you may add a permanent @code{nndiary} virtual server
17904 (something like @code{(nndiary "diary")} should do) to your
17905 @code{gnus-secondary-select-methods}.
17907 Hopefully, almost everything (see the TODO section in
17908 @file{nndiary.el}) will work as expected when you restart Gnus: in
17909 autonomous mode, typing @kbd{g} and @kbd{M-g} in the group buffer, will
17910 also get your new diary mails and split them according to your
17911 diary-specific rules, @kbd{F} will find your new diary groups etc.
17913 @node Customizing NNDiary
17914 @subsubsection Customizing NNDiary
17915 @cindex customizing nndiary
17916 @cindex nndiary customization
17918 Now that @code{nndiary} is up and running, it's time to customize it.
17919 The custom group is called @code{nndiary} (no, really ?!). You should
17920 browse it to figure out which options you'd like to tweak. The following
17921 two variables are probably the only ones you will want to change:
17923 @defvar nndiary-reminders
17924 This is the list of times when you want to be reminded of your
17925 appointements (e.g. 3 weeks before, then 2 days before, then 1 hour
17926 before and that's it). Remember that ``being reminded'' means that the
17927 diary message will pop up as brand new and unread again when you get new
17931 @defvar nndiary-week-starts-on-monday
17932 Rather self-explanatory. Otherwise, Sunday is assumed (this is the
17937 @node The Gnus Diary Library
17938 @subsection The Gnus Diary Library
17940 @cindex the gnus diary library
17942 Using @code{nndiary} manually (I mean, writing the headers by hand and
17943 so on) would be rather boring. Fortunately, there is a library called
17944 @code{gnus-diary} written on top of @code{nndiary}, that does many
17945 useful things for you.
17947 In order to use it, add the following line to your @file{gnusrc} file:
17950 (require 'gnus-diary)
17953 Also, you shouldn't use any @code{gnus-user-format-function-[d|D]}
17954 (@pxref{Summary Buffer Lines}). @code{gnus-diary} provides both of these
17955 (sorry if you used them before).
17959 * Diary Summary Line Format:: A nicer summary buffer line format.
17960 * Diary Articles Sorting:: A nicer way to sort messages.
17961 * Diary Headers Generation:: Not doing it manually.
17962 * Diary Group Parameters:: Not handling them manually.
17965 @node Diary Summary Line Format
17966 @subsubsection Diary Summary Line Format
17967 @cindex diary summary buffer line
17968 @cindex diary summary line format
17970 Displaying diary messages in standard summary line format (usually
17971 something like @samp{From Joe: Subject}) is pretty useless. Most of
17972 the time, you're the one who wrote the message, and you mostly want to
17973 see the event's date.
17975 @code{gnus-diary} provides two supplemental user formats to be used in
17976 summary line formats. @code{D} corresponds to a formatted time string
17977 for the next occurrence of the event (e.g. ``Sat, Sep 22 01, 12:00''),
17978 while @code{d} corresponds to an approximative remaining time until the
17979 next occurrence of the event (e.g. ``in 6 months, 1 week'').
17981 For example, here's how Joe's birthday is displayed in my
17982 @code{nndiary+diary:birthdays} summary buffer (note that the message is
17983 expirable, but will never be deleted, as it specifies a periodic event):
17986 E Sat, Sep 22 01, 12:00: Joe's birthday (in 6 months, 1 week)
17989 In order to get something like the above, you would normally add the
17990 following line to your diary groups'parameters:
17993 (gnus-summary-line-format "%U%R%z %uD: %(%s%) (%ud)\n")
17996 However, @code{gnus-diary} does it automatically (@pxref{Diary Group
17997 Parameters}). You can however customize the provided summary line format
17998 with the following user options:
18000 @defvar gnus-diary-summary-line-format
18001 Defines the summary line format used for diary groups (@pxref{Summary
18002 Buffer Lines}). @code{gnus-diary} uses it to automatically update the
18003 diary groups'parameters.
18006 @defvar gnus-diary-time-format
18007 Defines the format to display dates in diary summary buffers. This is
18008 used by the @code{D} user format. See the docstring for details.
18011 @defvar gnus-diary-delay-format-function
18012 Defines the format function to use for displaying delays (remaining
18013 times) in diary summary buffers. This is used by the @code{d} user
18014 format. There are currently built-in functions for English and French;
18015 you can also define your own. See the docstring for details.
18018 @node Diary Articles Sorting
18019 @subsubsection Diary Articles Sorting
18020 @cindex diary articles sorting
18021 @cindex diary summary lines sorting
18022 @findex gnus-summary-sort-by-schedule
18023 @findex gnus-thread-sort-by-schedule
18024 @findex gnus-article-sort-by-schedule
18026 @code{gnus-diary} provides new sorting functions (@pxref{Sorting the
18027 Summary Buffer} ) called @code{gnus-summary-sort-by-schedule},
18028 @code{gnus-thread-sort-by-schedule} and
18029 @code{gnus-article-sort-by-schedule}. These functions let you organize
18030 your diary summary buffers from the closest event to the farthest one.
18032 @code{gnus-diary} automatically installs
18033 @code{gnus-summary-sort-by-schedule} as a menu item in the summary
18034 buffer's ``sort'' menu, and the two others as the primary (hence
18035 default) sorting functions in the group parameters (@pxref{Diary Group
18038 @node Diary Headers Generation
18039 @subsubsection Diary Headers Generation
18040 @cindex diary headers generation
18041 @findex gnus-diary-check-message
18043 @code{gnus-diary} provides a function called
18044 @code{gnus-diary-check-message} to help you handle the @code{X-Diary-*}
18045 headers. This function ensures that the current message contains all the
18046 required diary headers, and prompts you for values or corrections if
18049 This function is hooked into the @code{nndiary} back end, so that
18050 moving or copying an article to a diary group will trigger it
18051 automatically. It is also bound to @kbd{C-c D c} in @code{message-mode}
18052 and @code{article-edit-mode} in order to ease the process of converting
18053 a usual mail to a diary one.
18055 This function takes a prefix argument which will force prompting of
18056 all diary headers, regardless of their presence or validity. That way,
18057 you can very easily reschedule an already valid diary message, for
18060 @node Diary Group Parameters
18061 @subsubsection Diary Group Parameters
18062 @cindex diary group parameters
18064 When you create a new diary group, or visit one, @code{gnus-diary}
18065 automatically checks your group parameters and if needed, sets the
18066 summary line format to the diary-specific value, installs the
18067 diary-specific sorting functions, and also adds the different
18068 @code{X-Diary-*} headers to the group's posting-style. It is then easier
18069 to send a diary message, because if you use @kbd{C-u a} or @kbd{C-u m}
18070 on a diary group to prepare a message, these headers will be inserted
18071 automatically (although not filled with proper values yet).
18073 @node Sending or Not Sending
18074 @subsection Sending or Not Sending
18076 Well, assuming you've read of of the above, here are two final notes on
18077 mail sending with @code{nndiary}:
18081 @code{nndiary} is a @emph{real} mail back end. You really send real diary
18082 messsages for real. This means for instance that you can give
18083 appointements to anybody (provided they use Gnus and @code{nndiary}) by
18084 sending the diary message to them as well.
18086 However, since @code{nndiary} also has a @code{request-post} method, you
18087 can also use @kbd{C-u a} instead of @kbd{C-u m} on a diary group and the
18088 message won't actually be sent; just stored locally in the group. This
18089 comes in very handy for private appointments.
18092 @node Gnus Unplugged
18093 @section Gnus Unplugged
18098 @cindex Gnus unplugged
18100 In olden times (ca. February '88), people used to run their newsreaders
18101 on big machines with permanent connections to the net. News transport
18102 was dealt with by news servers, and all the newsreaders had to do was to
18103 read news. Believe it or not.
18105 Nowadays most people read news and mail at home, and use some sort of
18106 modem to connect to the net. To avoid running up huge phone bills, it
18107 would be nice to have a way to slurp down all the news and mail, hang up
18108 the phone, read for several hours, and then upload any responses you
18109 have to make. And then you repeat the procedure.
18111 Of course, you can use news servers for doing this as well. I've used
18112 @code{inn} together with @code{slurp}, @code{pop} and @code{sendmail}
18113 for some years, but doing that's a bore. Moving the news server
18114 functionality up to the newsreader makes sense if you're the only person
18115 reading news on a machine.
18117 Setting up Gnus as an ``offline'' newsreader is quite simple. In
18118 fact, you don't have to configure anything as the agent is now enabled
18119 by default (@pxref{Agent Variables, gnus-agent}).
18121 Of course, to use it as such, you have to learn a few new commands.
18124 * Agent Basics:: How it all is supposed to work.
18125 * Agent Categories:: How to tell the Gnus Agent what to download.
18126 * Agent Commands:: New commands for all the buffers.
18127 * Agent Visuals:: Ways that the agent may effect your summary buffer.
18128 * Agent as Cache:: The Agent is a big cache too.
18129 * Agent Expiry:: How to make old articles go away.
18130 * Agent Regeneration:: How to recover from lost connections and other accidents.
18131 * Agent and IMAP:: How to use the Agent with @acronym{IMAP}.
18132 * Outgoing Messages:: What happens when you post/mail something?
18133 * Agent Variables:: Customizing is fun.
18134 * Example Setup:: An example @file{~/.gnus.el} file for offline people.
18135 * Batching Agents:: How to fetch news from a @code{cron} job.
18136 * Agent Caveats:: What you think it'll do and what it does.
18141 @subsection Agent Basics
18143 First, let's get some terminology out of the way.
18145 The Gnus Agent is said to be @dfn{unplugged} when you have severed the
18146 connection to the net (and notified the Agent that this is the case).
18147 When the connection to the net is up again (and Gnus knows this), the
18148 Agent is @dfn{plugged}.
18150 The @dfn{local} machine is the one you're running on, and which isn't
18151 connected to the net continuously.
18153 @dfn{Downloading} means fetching things from the net to your local
18154 machine. @dfn{Uploading} is doing the opposite.
18156 You know that Gnus gives you all the opportunity you'd ever want for
18157 shooting yourself in the foot. Some people call it flexibility. Gnus
18158 is also customizable to a great extent, which means that the user has a
18159 say on how Gnus behaves. Other newsreaders might unconditionally shoot
18160 you in your foot, but with Gnus, you have a choice!
18162 Gnus is never really in plugged or unplugged state. Rather, it applies
18163 that state to each server individually. This means that some servers
18164 can be plugged while others can be unplugged. Additionally, some
18165 servers can be ignored by the Agent altogether (which means that
18166 they're kinda like plugged always).
18168 So when you unplug the Agent and then wonder why is Gnus opening a
18169 connection to the Net, the next step to do is to look whether all
18170 servers are agentized. If there is an unagentized server, you found
18173 Another thing is the @dfn{offline} state. Sometimes, servers aren't
18174 reachable. When Gnus notices this, it asks you whether you want the
18175 server to be switched to offline state. If you say yes, then the
18176 server will behave somewhat as if it was unplugged, except that Gnus
18177 will ask you whether you want to switch it back online again.
18179 Let's take a typical Gnus session using the Agent.
18184 @findex gnus-unplugged
18185 You start Gnus with @code{gnus-unplugged}. This brings up the Gnus
18186 Agent in a disconnected state. You can read all the news that you have
18187 already fetched while in this mode.
18190 You then decide to see whether any new news has arrived. You connect
18191 your machine to the net (using PPP or whatever), and then hit @kbd{J j}
18192 to make Gnus become @dfn{plugged} and use @kbd{g} to check for new mail
18193 as usual. To check for new mail in unplugged mode (@pxref{Mail
18194 Source Specifiers}).
18197 You can then read the new news immediately, or you can download the
18198 news onto your local machine. If you want to do the latter, you press
18199 @kbd{g} to check if there are any new news and then @kbd{J s} to fetch
18200 all the eligible articles in all the groups. (To let Gnus know which
18201 articles you want to download, @pxref{Agent Categories}).
18204 After fetching the articles, you press @kbd{J j} to make Gnus become
18205 unplugged again, and you shut down the PPP thing (or whatever). And
18206 then you read the news offline.
18209 And then you go to step 2.
18212 Here are some things you should do the first time (or so) that you use
18218 Decide which servers should be covered by the Agent. If you have a mail
18219 back end, it would probably be nonsensical to have it covered by the
18220 Agent. Go to the server buffer (@kbd{^} in the group buffer) and press
18221 @kbd{J a} on the server (or servers) that you wish to have covered by the
18222 Agent (@pxref{Server Agent Commands}), or @kbd{J r} on automatically
18223 added servers you do not wish to have covered by the Agent. By default,
18224 all @code{nntp} and @code{nnimap} servers in @code{gnus-select-method} and
18225 @code{gnus-secondary-select-methods} are agentized.
18228 Decide on download policy. It's fairly simple once you decide whether
18229 you are going to use agent categories, topic parameters, and/or group
18230 parameters to implement your policy. If you're new to gnus, it
18231 is probably best to start with a category, @xref{Agent Categories}.
18233 Both topic parameters (@pxref{Topic Parameters}) and agent categories
18234 (@pxref{Agent Categories}) provide for setting a policy that applies
18235 to multiple groups. Which you use is entirely up to you. Topic
18236 parameters do override categories so, if you mix the two, you'll have
18237 to take that into account. If you have a few groups that deviate from
18238 your policy, you can use group parameters (@pxref{Group Parameters}) to
18242 Uhm@dots{} that's it.
18246 @node Agent Categories
18247 @subsection Agent Categories
18249 One of the main reasons to integrate the news transport layer into the
18250 newsreader is to allow greater control over what articles to download.
18251 There's not much point in downloading huge amounts of articles, just to
18252 find out that you're not interested in reading any of them. It's better
18253 to be somewhat more conservative in choosing what to download, and then
18254 mark the articles for downloading manually if it should turn out that
18255 you're interested in the articles anyway.
18257 One of the more effective methods for controlling what is to be
18258 downloaded is to create a @dfn{category} and then assign some (or all)
18259 groups to this category. Groups that do not belong in any other
18260 category belong to the @code{default} category. Gnus has its own
18261 buffer for creating and managing categories.
18263 If you prefer, you can also use group parameters (@pxref{Group
18264 Parameters}) and topic parameters (@pxref{Topic Parameters}) for an
18265 alternative approach to controlling the agent. The only real
18266 difference is that categories are specific to the agent (so there is
18267 less to learn) while group and topic parameters include the kitchen
18270 Since you can set agent parameters in several different places we have
18271 a rule to decide which source to believe. This rule specifies that
18272 the parameter sources are checked in the following order: group
18273 parameters, topic parameters, agent category, and finally customizable
18274 variables. So you can mix all of these sources to produce a wide range
18275 of behavior, just don't blame me if you don't remember where you put
18279 * Category Syntax:: What a category looks like.
18280 * Category Buffer:: A buffer for maintaining categories.
18281 * Category Variables:: Customize'r'Us.
18285 @node Category Syntax
18286 @subsubsection Category Syntax
18288 A category consists of a name, the list of groups belonging to the
18289 category, and a number of optional parameters that override the
18290 customizable variables. The complete list of agent parameters are
18293 @cindex Agent Parameters
18295 @item agent-cat-name
18296 The name of the category.
18299 The list of groups that are in this category.
18301 @item agent-predicate
18302 A predicate which (generally) gives a rough outline of which articles
18303 are eligible for downloading; and
18305 @item agent-score-file
18306 a score rule which (generally) gives you a finer granularity when
18307 deciding what articles to download. (Note that this @dfn{download
18308 score} is not necessarily related to normal scores.)
18310 @item agent-enable-expiration
18311 a boolean indicating whether the agent should expire old articles in
18312 this group. Most groups should be expired to conserve disk space. In
18313 fact, its probably safe to say that the gnus.* hierarchy contains the
18314 only groups that should not be expired.
18316 @item agent-days-until-old
18317 an integer indicating the number of days that the agent should wait
18318 before deciding that a read article is safe to expire.
18320 @item agent-low-score
18321 an integer that overrides the value of @code{gnus-agent-low-score}.
18323 @item agent-high-score
18324 an integer that overrides the value of @code{gnus-agent-high-score}.
18326 @item agent-length-when-short
18327 an integer that overrides the value of
18328 @code{gnus-agent-short-article}.
18330 @item agent-length-when-long
18331 an integer that overrides the value of @code{gnus-agent-long-article}.
18333 @item agent-enable-undownloaded-faces
18334 a symbol indicating whether the summary buffer should display
18335 undownloaded articles using the @code{gnus-summary-*-undownloaded-face}
18336 faces. Any symbol other than @code{nil} will enable the use of
18337 undownloaded faces.
18340 The name of a category can not be changed once the category has been
18343 Each category maintains a list of groups that are exclusive members of
18344 that category. The exclusivity rule is automatically enforced, add a
18345 group to a new category and it is automatically removed from its old
18348 A predicate in its simplest form can be a single predicate such as
18349 @code{true} or @code{false}. These two will download every available
18350 article or nothing respectively. In the case of these two special
18351 predicates an additional score rule is superfluous.
18353 Predicates of @code{high} or @code{low} download articles in respect of
18354 their scores in relationship to @code{gnus-agent-high-score} and
18355 @code{gnus-agent-low-score} as described below.
18357 To gain even finer control of what is to be regarded eligible for
18358 download a predicate can consist of a number of predicates with logical
18359 operators sprinkled in between.
18361 Perhaps some examples are in order.
18363 Here's a simple predicate. (It's the default predicate, in fact, used
18364 for all groups that don't belong to any other category.)
18370 Quite simple, eh? This predicate is true if and only if the article is
18371 short (for some value of ``short'').
18373 Here's a more complex predicate:
18382 This means that an article should be downloaded if it has a high score,
18383 or if the score is not low and the article is not long. You get the
18386 The available logical operators are @code{or}, @code{and} and
18387 @code{not}. (If you prefer, you can use the more ``C''-ish operators
18388 @samp{|}, @code{&} and @code{!} instead.)
18390 The following predicates are pre-defined, but if none of these fit what
18391 you want to do, you can write your own.
18393 When evaluating each of these predicates, the named constant will be
18394 bound to the value determined by calling
18395 @code{gnus-agent-find-parameter} on the appropriate parameter. For
18396 example, gnus-agent-short-article will be bound to
18397 @code{(gnus-agent-find-parameter group 'agent-short-article)}. This
18398 means that you can specify a predicate in your category then tune that
18399 predicate to individual groups.
18403 True iff the article is shorter than @code{gnus-agent-short-article}
18404 lines; default 100.
18407 True iff the article is longer than @code{gnus-agent-long-article}
18408 lines; default 200.
18411 True iff the article has a download score less than
18412 @code{gnus-agent-low-score}; default 0.
18415 True iff the article has a download score greater than
18416 @code{gnus-agent-high-score}; default 0.
18419 True iff the Gnus Agent guesses that the article is spam. The
18420 heuristics may change over time, but at present it just computes a
18421 checksum and sees whether articles match.
18430 If you want to create your own predicate function, here's what you have
18431 to know: The functions are called with no parameters, but the
18432 @code{gnus-headers} and @code{gnus-score} dynamic variables are bound to
18435 For example, you could decide that you don't want to download articles
18436 that were posted more than a certain number of days ago (e.g. posted
18437 more than @code{gnus-agent-expire-days} ago) you might write a function
18438 something along the lines of the following:
18441 (defun my-article-old-p ()
18442 "Say whether an article is old."
18443 (< (time-to-days (date-to-time (mail-header-date gnus-headers)))
18444 (- (time-to-days (current-time)) gnus-agent-expire-days)))
18447 with the predicate then defined as:
18450 (not my-article-old-p)
18453 or you could append your predicate to the predefined
18454 @code{gnus-category-predicate-alist} in your @file{~/.gnus.el} or
18458 (require 'gnus-agent)
18459 (setq gnus-category-predicate-alist
18460 (append gnus-category-predicate-alist
18461 '((old . my-article-old-p))))
18464 and simply specify your predicate as:
18470 If/when using something like the above, be aware that there are many
18471 misconfigured systems/mailers out there and so an article's date is not
18472 always a reliable indication of when it was posted. Hell, some people
18473 just don't give a damn.
18475 The above predicates apply to @emph{all} the groups which belong to the
18476 category. However, if you wish to have a specific predicate for an
18477 individual group within a category, or you're just too lazy to set up a
18478 new category, you can enter a group's individual predicate in its group
18479 parameters like so:
18482 (agent-predicate . short)
18485 This is the group/topic parameter equivalent of the agent category default.
18486 Note that when specifying a single word predicate like this, the
18487 @code{agent-predicate} specification must be in dotted pair notation.
18489 The equivalent of the longer example from above would be:
18492 (agent-predicate or high (and (not low) (not long)))
18495 The outer parenthesis required in the category specification are not
18496 entered here as, not being in dotted pair notation, the value of the
18497 predicate is assumed to be a list.
18500 Now, the syntax of the download score is the same as the syntax of
18501 normal score files, except that all elements that require actually
18502 seeing the article itself are verboten. This means that only the
18503 following headers can be scored on: @code{Subject}, @code{From},
18504 @code{Date}, @code{Message-ID}, @code{References}, @code{Chars},
18505 @code{Lines}, and @code{Xref}.
18507 As with predicates, the specification of the @code{download score rule}
18508 to use in respect of a group can be in either the category definition if
18509 it's to be applicable to all groups in therein, or a group's parameters
18510 if it's to be specific to that group.
18512 In both of these places the @code{download score rule} can take one of
18519 This has the same syntax as a normal Gnus score file except only a
18520 subset of scoring keywords are available as mentioned above.
18526 Category specification
18530 ("Lars Ingebrigtsen" 1000000 nil s))
18536 Group/Topic Parameter specification
18539 (agent-score ("from"
18540 ("Lars Ingebrigtsen" 1000000 nil s))
18545 Again, note the omission of the outermost parenthesis here.
18551 These score files must @emph{only} contain the permitted scoring
18552 keywords stated above.
18558 Category specification
18561 ("~/News/agent.SCORE")
18567 ("~/News/agent.SCORE" "~/News/agent.group.SCORE")
18571 Group Parameter specification
18574 (agent-score "~/News/agent.SCORE")
18577 Additional score files can be specified as above. Need I say anything
18582 Use @code{normal} score files
18584 If you don't want to maintain two sets of scoring rules for a group, and
18585 your desired @code{downloading} criteria for a group are the same as your
18586 @code{reading} criteria then you can tell the agent to refer to your
18587 @code{normal} score files when deciding what to download.
18589 These directives in either the category definition or a group's
18590 parameters will cause the agent to read in all the applicable score
18591 files for a group, @emph{filtering out} those sections that do not
18592 relate to one of the permitted subset of scoring keywords.
18596 Category Specification
18603 Group Parameter specification
18606 (agent-score . file)
18611 @node Category Buffer
18612 @subsubsection Category Buffer
18614 You'd normally do all category maintenance from the category buffer.
18615 When you enter it for the first time (with the @kbd{J c} command from
18616 the group buffer), you'll only see the @code{default} category.
18618 The following commands are available in this buffer:
18622 @kindex q (Category)
18623 @findex gnus-category-exit
18624 Return to the group buffer (@code{gnus-category-exit}).
18627 @kindex e (Category)
18628 @findex gnus-category-customize-category
18629 Use a customization buffer to set all of the selected category's
18630 parameters at one time (@code{gnus-category-customize-category}).
18633 @kindex k (Category)
18634 @findex gnus-category-kill
18635 Kill the current category (@code{gnus-category-kill}).
18638 @kindex c (Category)
18639 @findex gnus-category-copy
18640 Copy the current category (@code{gnus-category-copy}).
18643 @kindex a (Category)
18644 @findex gnus-category-add
18645 Add a new category (@code{gnus-category-add}).
18648 @kindex p (Category)
18649 @findex gnus-category-edit-predicate
18650 Edit the predicate of the current category
18651 (@code{gnus-category-edit-predicate}).
18654 @kindex g (Category)
18655 @findex gnus-category-edit-groups
18656 Edit the list of groups belonging to the current category
18657 (@code{gnus-category-edit-groups}).
18660 @kindex s (Category)
18661 @findex gnus-category-edit-score
18662 Edit the download score rule of the current category
18663 (@code{gnus-category-edit-score}).
18666 @kindex l (Category)
18667 @findex gnus-category-list
18668 List all the categories (@code{gnus-category-list}).
18672 @node Category Variables
18673 @subsubsection Category Variables
18676 @item gnus-category-mode-hook
18677 @vindex gnus-category-mode-hook
18678 Hook run in category buffers.
18680 @item gnus-category-line-format
18681 @vindex gnus-category-line-format
18682 Format of the lines in the category buffer (@pxref{Formatting
18683 Variables}). Valid elements are:
18687 The name of the category.
18690 The number of groups in the category.
18693 @item gnus-category-mode-line-format
18694 @vindex gnus-category-mode-line-format
18695 Format of the category mode line (@pxref{Mode Line Formatting}).
18697 @item gnus-agent-short-article
18698 @vindex gnus-agent-short-article
18699 Articles that have fewer lines than this are short. Default 100.
18701 @item gnus-agent-long-article
18702 @vindex gnus-agent-long-article
18703 Articles that have more lines than this are long. Default 200.
18705 @item gnus-agent-low-score
18706 @vindex gnus-agent-low-score
18707 Articles that have a score lower than this have a low score. Default
18710 @item gnus-agent-high-score
18711 @vindex gnus-agent-high-score
18712 Articles that have a score higher than this have a high score. Default
18715 @item gnus-agent-expire-days
18716 @vindex gnus-agent-expire-days
18717 The number of days that a @samp{read} article must stay in the agent's
18718 local disk before becoming eligible for expiration (While the name is
18719 the same, this doesn't mean expiring the article on the server. It
18720 just means deleting the local copy of the article). What is also
18721 important to understand is that the counter starts with the time the
18722 article was written to the local disk and not the time the article was
18726 @item gnus-agent-enable-expiration
18727 @vindex gnus-agent-enable-expiration
18728 Determines whether articles in a group are, by default, expired or
18729 retained indefinitely. The default is @code{ENABLE} which means that
18730 you'll have to disable expiration when desired. On the other hand,
18731 you could set this to @code{DISABLE}. In that case, you would then
18732 have to enable expiration in selected groups.
18737 @node Agent Commands
18738 @subsection Agent Commands
18739 @findex gnus-agent-toggle-plugged
18740 @kindex J j (Agent)
18742 All the Gnus Agent commands are on the @kbd{J} submap. The @kbd{J j}
18743 (@code{gnus-agent-toggle-plugged}) command works in all modes, and
18744 toggles the plugged/unplugged state of the Gnus Agent.
18748 * Group Agent Commands:: Configure groups and fetch their contents.
18749 * Summary Agent Commands:: Manually select then fetch specific articles.
18750 * Server Agent Commands:: Select the servers that are supported by the agent.
18756 @node Group Agent Commands
18757 @subsubsection Group Agent Commands
18761 @kindex J u (Agent Group)
18762 @findex gnus-agent-fetch-groups
18763 Fetch all eligible articles in the current group
18764 (@code{gnus-agent-fetch-groups}).
18767 @kindex J c (Agent Group)
18768 @findex gnus-enter-category-buffer
18769 Enter the Agent category buffer (@code{gnus-enter-category-buffer}).
18772 @kindex J s (Agent Group)
18773 @findex gnus-agent-fetch-session
18774 Fetch all eligible articles in all groups
18775 (@code{gnus-agent-fetch-session}).
18778 @kindex J S (Agent Group)
18779 @findex gnus-group-send-queue
18780 Send all sendable messages in the queue group
18781 (@code{gnus-group-send-queue}). @xref{Drafts}.
18784 @kindex J a (Agent Group)
18785 @findex gnus-agent-add-group
18786 Add the current group to an Agent category
18787 (@code{gnus-agent-add-group}). This command understands the
18788 process/prefix convention (@pxref{Process/Prefix}).
18791 @kindex J r (Agent Group)
18792 @findex gnus-agent-remove-group
18793 Remove the current group from its category, if any
18794 (@code{gnus-agent-remove-group}). This command understands the
18795 process/prefix convention (@pxref{Process/Prefix}).
18798 @kindex J Y (Agent Group)
18799 @findex gnus-agent-synchronize-flags
18800 Synchronize flags changed while unplugged with remote server, if any.
18806 @node Summary Agent Commands
18807 @subsubsection Summary Agent Commands
18811 @kindex J # (Agent Summary)
18812 @findex gnus-agent-mark-article
18813 Mark the article for downloading (@code{gnus-agent-mark-article}).
18816 @kindex J M-# (Agent Summary)
18817 @findex gnus-agent-unmark-article
18818 Remove the downloading mark from the article
18819 (@code{gnus-agent-unmark-article}).
18823 @kindex @@ (Agent Summary)
18824 @findex gnus-agent-toggle-mark
18825 Toggle whether to download the article
18826 (@code{gnus-agent-toggle-mark}). The download mark is @samp{%} by
18830 @kindex J c (Agent Summary)
18831 @findex gnus-agent-catchup
18832 Mark all articles as read (@code{gnus-agent-catchup}) that are neither cached, downloaded, nor downloadable.
18835 @kindex J S (Agent Summary)
18836 @findex gnus-agent-fetch-group
18837 Download all eligible (@pxref{Agent Categories}) articles in this group.
18838 (@code{gnus-agent-fetch-group}).
18841 @kindex J s (Agent Summary)
18842 @findex gnus-agent-fetch-series
18843 Download all processable articles in this group.
18844 (@code{gnus-agent-fetch-series}).
18847 @kindex J u (Agent Summary)
18848 @findex gnus-agent-summary-fetch-group
18849 Download all downloadable articles in the current group
18850 (@code{gnus-agent-summary-fetch-group}).
18855 @node Server Agent Commands
18856 @subsubsection Server Agent Commands
18860 @kindex J a (Agent Server)
18861 @findex gnus-agent-add-server
18862 Add the current server to the list of servers covered by the Gnus Agent
18863 (@code{gnus-agent-add-server}).
18866 @kindex J r (Agent Server)
18867 @findex gnus-agent-remove-server
18868 Remove the current server from the list of servers covered by the Gnus
18869 Agent (@code{gnus-agent-remove-server}).
18874 @node Agent Visuals
18875 @subsection Agent Visuals
18877 If you open a summary while unplugged and, Gnus knows from the group's
18878 active range that there are more articles than the headers currently
18879 stored in the Agent, you may see some articles whose subject looks
18880 something like @samp{[Undownloaded article #####]}. These are
18881 placeholders for the missing headers. Aside from setting a mark,
18882 there is not much that can be done with one of these placeholders.
18883 When Gnus finally gets a chance to fetch the group's headers, the
18884 placeholders will automatically be replaced by the actual headers.
18885 You can configure the summary buffer's maneuvering to skip over the
18886 placeholders if you care (See @code{gnus-auto-goto-ignores}).
18888 While it may be obvious to all, the only headers and articles
18889 available while unplugged are those headers and articles that were
18890 fetched into the Agent while previously plugged. To put it another
18891 way, ``If you forget to fetch something while plugged, you might have a
18892 less than satisfying unplugged session''. For this reason, the Agent
18893 adds two visual effects to your summary buffer. These effects display
18894 the download status of each article so that you always know which
18895 articles will be available when unplugged.
18897 The first visual effect is the @samp{%O} spec. If you customize
18898 @code{gnus-summary-line-format} to include this specifier, you will add
18899 a single character field that indicates an article's download status.
18900 Articles that have been fetched into either the Agent or the Cache,
18901 will display @code{gnus-downloaded-mark} (defaults to @samp{+}). All
18902 other articles will display @code{gnus-undownloaded-mark} (defaults to
18903 @samp{-}). If you open a group that has not been agentized, a space
18904 (@samp{ }) will be displayed.
18906 The second visual effect are the undownloaded faces. The faces, there
18907 are three indicating the article's score (low, normal, high), seem to
18908 result in a love/hate response from many Gnus users. The problem is
18909 that the face selection is controlled by a list of condition tests and
18910 face names (See @code{gnus-summary-highlight}). Each condition is
18911 tested in the order in which it appears in the list so early
18912 conditions have precedence over later conditions. All of this means
18913 that, if you tick an undownloaded article, the article will continue
18914 to be displayed in the undownloaded face rather than the ticked face.
18916 If you use the Agent as a cache (to avoid downloading the same article
18917 each time you visit it or to minimize your connection time), the
18918 undownloaded face will probably seem like a good idea. The reason
18919 being that you do all of our work (marking, reading, deleting) with
18920 downloaded articles so the normal faces always appear. For those
18921 users using the agent to improve online performance by caching the NOV
18922 database (most users since 5.10.2), the undownloaded faces may appear
18923 to be an absolutely horrible idea. The issue being that, since none
18924 of their articles have been fetched into the Agent, all of the
18925 normal faces will be obscured by the undownloaded faces.
18927 If you would like to use the undownloaded faces, you must enable the
18928 undownloaded faces by setting the @code{agent-enable-undownloaded-faces}
18929 group parameter to @code{t}. This parameter, like all other agent
18930 parameters, may be set on an Agent Category (@pxref{Agent Categories}),
18931 a Group Topic (@pxref{Topic Parameters}), or an individual group
18932 (@pxref{Group Parameters}).
18934 The one problem common to all users using the agent is how quickly it
18935 can consume disk space. If you using the agent on many groups, it is
18936 even more difficult to effectively recover disk space. One solution
18937 is the @samp{%F} format available in @code{gnus-group-line-format}.
18938 This format will display the actual disk space used by articles
18939 fetched into both the agent and cache. By knowing which groups use
18940 the most space, users know where to focus their efforts when ``agent
18941 expiring'' articles.
18943 @node Agent as Cache
18944 @subsection Agent as Cache
18946 When Gnus is plugged, it is not efficient to download headers or
18947 articles from the server again, if they are already stored in the
18948 Agent. So, Gnus normally only downloads headers once, and stores them
18949 in the Agent. These headers are later used when generating the summary
18950 buffer, regardless of whether you are plugged or unplugged. Articles
18951 are not cached in the Agent by default though (that would potentially
18952 consume lots of disk space), but if you have already downloaded an
18953 article into the Agent, Gnus will not download the article from the
18954 server again but use the locally stored copy instead.
18956 If you so desire, you can configure the agent (see @code{gnus-agent-cache}
18957 @pxref{Agent Variables}) to always download headers and articles while
18958 plugged. Gnus will almost certainly be slower, but it will be kept
18959 synchronized with the server. That last point probably won't make any
18960 sense if you are using a nntp or nnimap back end.
18963 @subsection Agent Expiry
18965 @vindex gnus-agent-expire-days
18966 @findex gnus-agent-expire
18967 @kindex M-x gnus-agent-expire
18968 @kindex M-x gnus-agent-expire-group
18969 @findex gnus-agent-expire-group
18970 @cindex agent expiry
18971 @cindex Gnus agent expiry
18974 The Agent back end, @code{nnagent}, doesn't handle expiry. Well, at
18975 least it doesn't handle it like other back ends. Instead, there are
18976 special @code{gnus-agent-expire} and @code{gnus-agent-expire-group}
18977 commands that will expire all read articles that are older than
18978 @code{gnus-agent-expire-days} days. They can be run whenever you feel
18979 that you're running out of space. Neither are particularly fast or
18980 efficient, and it's not a particularly good idea to interrupt them (with
18981 @kbd{C-g} or anything else) once you've started one of them.
18983 Note that other functions, e.g. @code{gnus-request-expire-articles},
18984 might run @code{gnus-agent-expire} for you to keep the agent
18985 synchronized with the group.
18987 The agent parameter @code{agent-enable-expiration} may be used to
18988 prevent expiration in selected groups.
18990 @vindex gnus-agent-expire-all
18991 If @code{gnus-agent-expire-all} is non-@code{nil}, the agent
18992 expiration commands will expire all articles---unread, read, ticked
18993 and dormant. If @code{nil} (which is the default), only read articles
18994 are eligible for expiry, and unread, ticked and dormant articles will
18995 be kept indefinitely.
18997 If you find that some articles eligible for expiry are never expired,
18998 perhaps some Gnus Agent files are corrupted. There's are special
18999 commands, @code{gnus-agent-regenerate} and
19000 @code{gnus-agent-regenerate-group}, to fix possible problems.
19002 @node Agent Regeneration
19003 @subsection Agent Regeneration
19005 @cindex agent regeneration
19006 @cindex Gnus agent regeneration
19007 @cindex regeneration
19009 The local data structures used by @code{nnagent} may become corrupted
19010 due to certain exceptional conditions. When this happens,
19011 @code{nnagent} functionality may degrade or even fail. The solution
19012 to this problem is to repair the local data structures by removing all
19013 internal inconsistencies.
19015 For example, if your connection to your server is lost while
19016 downloaded articles into the agent, the local data structures will not
19017 know about articles successfully downloaded prior to the connection
19018 failure. Running @code{gnus-agent-regenerate} or
19019 @code{gnus-agent-regenerate-group} will update the data structures
19020 such that you don't need to download these articles a second time.
19022 @findex gnus-agent-regenerate
19023 @kindex M-x gnus-agent-regenerate
19024 The command @code{gnus-agent-regenerate} will perform
19025 @code{gnus-agent-regenerate-group} on every agentized group. While
19026 you can run @code{gnus-agent-regenerate} in any buffer, it is strongly
19027 recommended that you first close all summary buffers.
19029 @findex gnus-agent-regenerate-group
19030 @kindex M-x gnus-agent-regenerate-group
19031 The command @code{gnus-agent-regenerate-group} uses the local copies
19032 of individual articles to repair the local @acronym{NOV}(header) database. It
19033 then updates the internal data structures that document which articles
19034 are stored locally. An optional argument will mark articles in the
19037 @node Agent and IMAP
19038 @subsection Agent and IMAP
19040 The Agent works with any Gnus back end, including nnimap. However,
19041 since there are some conceptual differences between @acronym{NNTP} and
19042 @acronym{IMAP}, this section (should) provide you with some information to
19043 make Gnus Agent work smoother as a @acronym{IMAP} Disconnected Mode client.
19045 The first thing to keep in mind is that all flags (read, ticked, etc)
19046 are kept on the @acronym{IMAP} server, rather than in @file{.newsrc} as is the
19047 case for nntp. Thus Gnus need to remember flag changes when
19048 disconnected, and synchronize these flags when you plug back in.
19050 Gnus keeps track of flag changes when reading nnimap groups under the
19051 Agent. When you plug back in, Gnus will check if you have any changed
19052 any flags and ask if you wish to synchronize these with the server.
19053 The behavior is customizable by @code{gnus-agent-synchronize-flags}.
19055 @vindex gnus-agent-synchronize-flags
19056 If @code{gnus-agent-synchronize-flags} is @code{nil}, the Agent will
19057 never automatically synchronize flags. If it is @code{ask}, which is
19058 the default, the Agent will check if you made any changes and if so
19059 ask if you wish to synchronize these when you re-connect. If it has
19060 any other value, all flags will be synchronized automatically.
19062 If you do not wish to synchronize flags automatically when you
19063 re-connect, you can do it manually with the
19064 @code{gnus-agent-synchronize-flags} command that is bound to @kbd{J Y}
19065 in the group buffer.
19067 Some things are currently not implemented in the Agent that you'd might
19068 expect from a disconnected @acronym{IMAP} client, including:
19073 Copying/moving articles into nnimap groups when unplugged.
19076 Creating/deleting nnimap groups when unplugged.
19080 Technical note: the synchronization algorithm does not work by ``pushing''
19081 all local flags to the server, but rather incrementally update the
19082 server view of flags by changing only those flags that were changed by
19083 the user. Thus, if you set one flag on an article, quit the group and
19084 re-select the group and remove the flag; the flag will be set and
19085 removed from the server when you ``synchronize''. The queued flag
19086 operations can be found in the per-server @code{flags} file in the Agent
19087 directory. It's emptied when you synchronize flags.
19090 @node Outgoing Messages
19091 @subsection Outgoing Messages
19093 By default, when Gnus is unplugged, all outgoing messages (both mail
19094 and news) are stored in the draft group ``queue'' (@pxref{Drafts}).
19095 You can view them there after posting, and edit them at will.
19097 You can control the circumstances under which outgoing mail is queued
19098 (see @code{gnus-agent-queue-mail}, @pxref{Agent Variables}). Outgoing
19099 news is always queued when Gnus is unplugged, and never otherwise.
19101 You can send the messages either from the draft group with the special
19102 commands available there, or you can use the @kbd{J S} command in the
19103 group buffer to send all the sendable messages in the draft group.
19104 Posting news will only work when Gnus is plugged, but you can send
19107 If sending mail while unplugged does not work for you and you worry
19108 about hitting @kbd{J S} by accident when unplugged, you can have Gnus
19109 ask you to confirm your action (see
19110 @code{gnus-agent-prompt-send-queue}, @pxref{Agent Variables}).
19112 @node Agent Variables
19113 @subsection Agent Variables
19118 Is the agent enabled? The default is @code{t}. When first enabled,
19119 the agent will use @code{gnus-agent-auto-agentize-methods} to
19120 automatically mark some back ends as agentized. You may change which
19121 back ends are agentized using the agent commands in the server buffer.
19123 To enter the server buffer, use the @kbd{^}
19124 (@code{gnus-group-enter-server-mode}) command in the group buffer.
19127 @item gnus-agent-directory
19128 @vindex gnus-agent-directory
19129 Where the Gnus Agent will store its files. The default is
19130 @file{~/News/agent/}.
19132 @item gnus-agent-handle-level
19133 @vindex gnus-agent-handle-level
19134 Groups on levels (@pxref{Group Levels}) higher than this variable will
19135 be ignored by the Agent. The default is @code{gnus-level-subscribed},
19136 which means that only subscribed group will be considered by the Agent
19139 @item gnus-agent-plugged-hook
19140 @vindex gnus-agent-plugged-hook
19141 Hook run when connecting to the network.
19143 @item gnus-agent-unplugged-hook
19144 @vindex gnus-agent-unplugged-hook
19145 Hook run when disconnecting from the network.
19147 @item gnus-agent-fetched-hook
19148 @vindex gnus-agent-fetched-hook
19149 Hook run when finished fetching articles.
19151 @item gnus-agent-cache
19152 @vindex gnus-agent-cache
19153 Variable to control whether use the locally stored @acronym{NOV} and
19154 articles when plugged, e.g. essentially using the Agent as a cache.
19155 The default is non-@code{nil}, which means to use the Agent as a cache.
19157 @item gnus-agent-go-online
19158 @vindex gnus-agent-go-online
19159 If @code{gnus-agent-go-online} is @code{nil}, the Agent will never
19160 automatically switch offline servers into online status. If it is
19161 @code{ask}, the default, the Agent will ask if you wish to switch
19162 offline servers into online status when you re-connect. If it has any
19163 other value, all offline servers will be automatically switched into
19166 @item gnus-agent-mark-unread-after-downloaded
19167 @vindex gnus-agent-mark-unread-after-downloaded
19168 If @code{gnus-agent-mark-unread-after-downloaded} is non-@code{nil},
19169 mark articles as unread after downloading. This is usually a safe
19170 thing to do as the newly downloaded article has obviously not been
19171 read. The default is @code{t}.
19173 @item gnus-agent-consider-all-articles
19174 @vindex gnus-agent-consider-all-articles
19175 If @code{gnus-agent-consider-all-articles} is non-@code{nil}, the
19176 agent will let the agent predicate decide whether articles need to be
19177 downloaded or not, for all articles. When @code{nil}, the default,
19178 the agent will only let the predicate decide whether unread articles
19179 are downloaded or not. If you enable this, you may also want to look
19180 into the agent expiry settings (@pxref{Category Variables}), so that
19181 the agent doesn't download articles which the agent will later expire,
19182 over and over again.
19184 @item gnus-agent-max-fetch-size
19185 @vindex gnus-agent-max-fetch-size
19186 The agent fetches articles into a temporary buffer prior to parsing
19187 them into individual files. To avoid exceeding the max. buffer size,
19188 the agent alternates between fetching and parsing until all articles
19189 have been fetched. @code{gnus-agent-max-fetch-size} provides a size
19190 limit to control how often the cycling occurs. A large value improves
19191 performance. A small value minimizes the time lost should the
19192 connection be lost while fetching (You may need to run
19193 @code{gnus-agent-regenerate-group} to update the group's state.
19194 However, all articles parsed prior to loosing the connection will be
19195 available while unplugged). The default is 10M so it is unusual to
19198 @item gnus-server-unopen-status
19199 @vindex gnus-server-unopen-status
19200 Perhaps not an Agent variable, but closely related to the Agent, this
19201 variable says what will happen if Gnus cannot open a server. If the
19202 Agent is enabled, the default, @code{nil}, makes Gnus ask the user
19203 whether to deny the server or whether to unplug the agent. If the
19204 Agent is disabled, Gnus always simply deny the server. Other choices
19205 for this variable include @code{denied} and @code{offline} the latter
19206 is only valid if the Agent is used.
19208 @item gnus-auto-goto-ignores
19209 @vindex gnus-auto-goto-ignores
19210 Another variable that isn't an Agent variable, yet so closely related
19211 that most will look for it here, this variable tells the summary
19212 buffer how to maneuver around undownloaded (only headers stored in the
19213 agent) and unfetched (neither article nor headers stored) articles.
19215 The valid values are @code{nil} (maneuver to any article),
19216 @code{undownloaded} (maneuvering while unplugged ignores articles that
19217 have not been fetched), @code{always-undownloaded} (maneuvering always
19218 ignores articles that have not been fetched), @code{unfetched}
19219 (maneuvering ignores articles whose headers have not been fetched).
19221 @item gnus-agent-queue-mail
19222 @vindex gnus-agent-queue-mail
19223 When @code{gnus-agent-queue-mail} is @code{always}, Gnus will always
19224 queue mail rather than sending it straight away. When @code{t}, Gnus
19225 will queue mail when unplugged only. When @code{nil}, never queue
19226 mail. The default is @code{t}.
19228 @item gnus-agent-prompt-send-queue
19229 @vindex gnus-agent-prompt-send-queue
19230 When @code{gnus-agent-prompt-send-queue} is non-@code{nil} Gnus will
19231 prompt you to confirm that you really wish to proceed if you hit
19232 @kbd{J S} while unplugged. The default is @code{nil}.
19234 @item gnus-agent-auto-agentize-methods
19235 @vindex gnus-agent-auto-agentize-methods
19236 If you have never used the Agent before (or more technically, if
19237 @file{~/News/agent/lib/servers} does not exist), Gnus will
19238 automatically agentize a few servers for you. This variable control
19239 which back ends should be auto-agentized. It is typically only useful
19240 to agentize remote back ends. The auto-agentizing has the same effect
19241 as running @kbd{J a} on the servers (@pxref{Server Agent Commands}).
19242 If the file exist, you must manage the servers manually by adding or
19243 removing them, this variable is only applicable the first time you
19244 start Gnus. The default is @samp{(nntp nnimap)}.
19249 @node Example Setup
19250 @subsection Example Setup
19252 If you don't want to read this manual, and you have a fairly standard
19253 setup, you may be able to use something like the following as your
19254 @file{~/.gnus.el} file to get started.
19257 ;;; @r{Define how Gnus is to fetch news. We do this over @acronym{NNTP}}
19258 ;;; @r{from your ISP's server.}
19259 (setq gnus-select-method '(nntp "news.your-isp.com"))
19261 ;;; @r{Define how Gnus is to read your mail. We read mail from}
19262 ;;; @r{your ISP's @acronym{POP} server.}
19263 (setq mail-sources '((pop :server "pop.your-isp.com")))
19265 ;;; @r{Say how Gnus is to store the mail. We use nnml groups.}
19266 (setq gnus-secondary-select-methods '((nnml "")))
19268 ;;; @r{Make Gnus into an offline newsreader.}
19269 ;;; (gnus-agentize) ; @r{The obsolete setting.}
19270 ;;; (setq gnus-agent t) ; @r{Now the default.}
19273 That should be it, basically. Put that in your @file{~/.gnus.el} file,
19274 edit to suit your needs, start up PPP (or whatever), and type @kbd{M-x
19277 If this is the first time you've run Gnus, you will be subscribed
19278 automatically to a few default newsgroups. You'll probably want to
19279 subscribe to more groups, and to do that, you have to query the
19280 @acronym{NNTP} server for a complete list of groups with the @kbd{A A}
19281 command. This usually takes quite a while, but you only have to do it
19284 After reading and parsing a while, you'll be presented with a list of
19285 groups. Subscribe to the ones you want to read with the @kbd{u}
19286 command. @kbd{l} to make all the killed groups disappear after you've
19287 subscribe to all the groups you want to read. (@kbd{A k} will bring
19288 back all the killed groups.)
19290 You can now read the groups at once, or you can download the articles
19291 with the @kbd{J s} command. And then read the rest of this manual to
19292 find out which of the other gazillion things you want to customize.
19295 @node Batching Agents
19296 @subsection Batching Agents
19297 @findex gnus-agent-batch
19299 Having the Gnus Agent fetch articles (and post whatever messages you've
19300 written) is quite easy once you've gotten things set up properly. The
19301 following shell script will do everything that is necessary:
19303 You can run a complete batch command from the command line with the
19304 following incantation:
19308 emacs -batch -l ~/.emacs -l ~/.gnus.el gnus-agent-batch >/dev/null 2>&1
19312 @node Agent Caveats
19313 @subsection Agent Caveats
19315 The Gnus Agent doesn't seem to work like most other offline
19316 newsreaders. Here are some common questions that some imaginary people
19320 @item If I read an article while plugged, do they get entered into the Agent?
19322 @strong{No}. If you want this behavior, add
19323 @code{gnus-agent-fetch-selected-article} to
19324 @code{gnus-select-article-hook}.
19326 @item If I read an article while plugged, and the article already exists in
19327 the Agent, will it get downloaded once more?
19329 @strong{No}, unless @code{gnus-agent-cache} is @code{nil}.
19333 In short, when Gnus is unplugged, it only looks into the locally stored
19334 articles; when it's plugged, it talks to your ISP and may also use the
19335 locally stored articles.
19342 Other people use @dfn{kill files}, but we here at Gnus Towers like
19343 scoring better than killing, so we'd rather switch than fight. They do
19344 something completely different as well, so sit up straight and pay
19347 @vindex gnus-summary-mark-below
19348 All articles have a default score (@code{gnus-summary-default-score}),
19349 which is 0 by default. This score may be raised or lowered either
19350 interactively or by score files. Articles that have a score lower than
19351 @code{gnus-summary-mark-below} are marked as read.
19353 Gnus will read any @dfn{score files} that apply to the current group
19354 before generating the summary buffer.
19356 There are several commands in the summary buffer that insert score
19357 entries based on the current article. You can, for instance, ask Gnus to
19358 lower or increase the score of all articles with a certain subject.
19360 There are two sorts of scoring entries: Permanent and temporary.
19361 Temporary score entries are self-expiring entries. Any entries that are
19362 temporary and have not been used for, say, a week, will be removed
19363 silently to help keep the sizes of the score files down.
19366 * Summary Score Commands:: Adding score entries for the current group.
19367 * Group Score Commands:: General score commands.
19368 * Score Variables:: Customize your scoring. (My, what terminology).
19369 * Score File Format:: What a score file may contain.
19370 * Score File Editing:: You can edit score files by hand as well.
19371 * Adaptive Scoring:: Big Sister Gnus knows what you read.
19372 * Home Score File:: How to say where new score entries are to go.
19373 * Followups To Yourself:: Having Gnus notice when people answer you.
19374 * Scoring On Other Headers:: Scoring on non-standard headers.
19375 * Scoring Tips:: How to score effectively.
19376 * Reverse Scoring:: That problem child of old is not problem.
19377 * Global Score Files:: Earth-spanning, ear-splitting score files.
19378 * Kill Files:: They are still here, but they can be ignored.
19379 * Converting Kill Files:: Translating kill files to score files.
19380 * Advanced Scoring:: Using logical expressions to build score rules.
19381 * Score Decays:: It can be useful to let scores wither away.
19385 @node Summary Score Commands
19386 @section Summary Score Commands
19387 @cindex score commands
19389 The score commands that alter score entries do not actually modify real
19390 score files. That would be too inefficient. Gnus maintains a cache of
19391 previously loaded score files, one of which is considered the
19392 @dfn{current score file alist}. The score commands simply insert
19393 entries into this list, and upon group exit, this list is saved.
19395 The current score file is by default the group's local score file, even
19396 if no such score file actually exists. To insert score commands into
19397 some other score file (e.g. @file{all.SCORE}), you must first make this
19398 score file the current one.
19400 General score commands that don't actually change the score file:
19405 @kindex V s (Summary)
19406 @findex gnus-summary-set-score
19407 Set the score of the current article (@code{gnus-summary-set-score}).
19410 @kindex V S (Summary)
19411 @findex gnus-summary-current-score
19412 Display the score of the current article
19413 (@code{gnus-summary-current-score}).
19416 @kindex V t (Summary)
19417 @findex gnus-score-find-trace
19418 Display all score rules that have been used on the current article
19419 (@code{gnus-score-find-trace}). In the @code{*Score Trace*} buffer, you
19420 may type @kbd{e} to edit score file corresponding to the score rule on
19421 current line and @kbd{f} to format (@code{gnus-score-pretty-print}) the
19422 score file and edit it.
19425 @kindex V w (Summary)
19426 @findex gnus-score-find-favourite-words
19427 List words used in scoring (@code{gnus-score-find-favourite-words}).
19430 @kindex V R (Summary)
19431 @findex gnus-summary-rescore
19432 Run the current summary through the scoring process
19433 (@code{gnus-summary-rescore}). This might be useful if you're playing
19434 around with your score files behind Gnus' back and want to see the
19435 effect you're having.
19438 @kindex V c (Summary)
19439 @findex gnus-score-change-score-file
19440 Make a different score file the current
19441 (@code{gnus-score-change-score-file}).
19444 @kindex V e (Summary)
19445 @findex gnus-score-edit-current-scores
19446 Edit the current score file (@code{gnus-score-edit-current-scores}).
19447 You will be popped into a @code{gnus-score-mode} buffer (@pxref{Score
19451 @kindex V f (Summary)
19452 @findex gnus-score-edit-file
19453 Edit a score file and make this score file the current one
19454 (@code{gnus-score-edit-file}).
19457 @kindex V F (Summary)
19458 @findex gnus-score-flush-cache
19459 Flush the score cache (@code{gnus-score-flush-cache}). This is useful
19460 after editing score files.
19463 @kindex V C (Summary)
19464 @findex gnus-score-customize
19465 Customize a score file in a visually pleasing manner
19466 (@code{gnus-score-customize}).
19470 The rest of these commands modify the local score file.
19475 @kindex V m (Summary)
19476 @findex gnus-score-set-mark-below
19477 Prompt for a score, and mark all articles with a score below this as
19478 read (@code{gnus-score-set-mark-below}).
19481 @kindex V x (Summary)
19482 @findex gnus-score-set-expunge-below
19483 Prompt for a score, and add a score rule to the current score file to
19484 expunge all articles below this score
19485 (@code{gnus-score-set-expunge-below}).
19488 The keystrokes for actually making score entries follow a very regular
19489 pattern, so there's no need to list all the commands. (Hundreds of
19492 @findex gnus-summary-increase-score
19493 @findex gnus-summary-lower-score
19497 The first key is either @kbd{I} (upper case i) for increasing the score
19498 or @kbd{L} for lowering the score.
19500 The second key says what header you want to score on. The following
19501 keys are available:
19505 Score on the author name.
19508 Score on the subject line.
19511 Score on the @code{Xref} line---i.e., the cross-posting line.
19514 Score on the @code{References} line.
19520 Score on the number of lines.
19523 Score on the @code{Message-ID} header.
19526 Score on an ``extra'' header, that is, one of those in gnus-extra-headers,
19527 if your @acronym{NNTP} server tracks additional header data in overviews.
19530 Score on followups---this matches the author name, and adds scores to
19531 the followups to this author. (Using this key leads to the creation of
19532 @file{ADAPT} files.)
19541 Score on thread. (Using this key leads to the creation of @file{ADAPT}
19547 The third key is the match type. Which match types are valid depends on
19548 what headers you are scoring on.
19560 Substring matching.
19563 Fuzzy matching (@pxref{Fuzzy Matching}).
19592 Greater than number.
19597 The fourth and usually final key says whether this is a temporary (i.e.,
19598 expiring) score entry, or a permanent (i.e., non-expiring) score entry,
19599 or whether it is to be done immediately, without adding to the score
19604 Temporary score entry.
19607 Permanent score entry.
19610 Immediately scoring.
19614 If you are scoring on `e' (extra) headers, you will then be prompted for
19615 the header name on which you wish to score. This must be a header named
19616 in gnus-extra-headers, and @samp{TAB} completion is available.
19620 So, let's say you want to increase the score on the current author with
19621 exact matching permanently: @kbd{I a e p}. If you want to lower the
19622 score based on the subject line, using substring matching, and make a
19623 temporary score entry: @kbd{L s s t}. Pretty easy.
19625 To make things a bit more complicated, there are shortcuts. If you use
19626 a capital letter on either the second or third keys, Gnus will use
19627 defaults for the remaining one or two keystrokes. The defaults are
19628 ``substring'' and ``temporary''. So @kbd{I A} is the same as @kbd{I a s
19629 t}, and @kbd{I a R} is the same as @kbd{I a r t}.
19631 These functions take both the numerical prefix and the symbolic prefix
19632 (@pxref{Symbolic Prefixes}). A numerical prefix says how much to lower
19633 (or increase) the score of the article. A symbolic prefix of @code{a}
19634 says to use the @file{all.SCORE} file for the command instead of the
19635 current score file.
19637 @vindex gnus-score-mimic-keymap
19638 The @code{gnus-score-mimic-keymap} says whether these commands will
19639 pretend they are keymaps or not.
19642 @node Group Score Commands
19643 @section Group Score Commands
19644 @cindex group score commands
19646 There aren't many of these as yet, I'm afraid.
19651 @kindex W e (Group)
19652 @findex gnus-score-edit-all-score
19653 Edit the apply-to-all-groups all.SCORE file. You will be popped into
19654 a @code{gnus-score-mode} buffer (@pxref{Score File Editing}).
19657 @kindex W f (Group)
19658 @findex gnus-score-flush-cache
19659 Gnus maintains a cache of score alists to avoid having to reload them
19660 all the time. This command will flush the cache
19661 (@code{gnus-score-flush-cache}).
19665 You can do scoring from the command line by saying something like:
19667 @findex gnus-batch-score
19668 @cindex batch scoring
19670 $ emacs -batch -l ~/.emacs -l ~/.gnus.el -f gnus-batch-score
19674 @node Score Variables
19675 @section Score Variables
19676 @cindex score variables
19680 @item gnus-use-scoring
19681 @vindex gnus-use-scoring
19682 If @code{nil}, Gnus will not check for score files, and will not, in
19683 general, do any score-related work. This is @code{t} by default.
19685 @item gnus-kill-killed
19686 @vindex gnus-kill-killed
19687 If this variable is @code{nil}, Gnus will never apply score files to
19688 articles that have already been through the kill process. While this
19689 may save you lots of time, it also means that if you apply a kill file
19690 to a group, and then change the kill file and want to run it over you
19691 group again to kill more articles, it won't work. You have to set this
19692 variable to @code{t} to do that. (It is @code{t} by default.)
19694 @item gnus-kill-files-directory
19695 @vindex gnus-kill-files-directory
19696 All kill and score files will be stored in this directory, which is
19697 initialized from the @env{SAVEDIR} environment variable by default.
19698 This is @file{~/News/} by default.
19700 @item gnus-score-file-suffix
19701 @vindex gnus-score-file-suffix
19702 Suffix to add to the group name to arrive at the score file name
19703 (@file{SCORE} by default.)
19705 @item gnus-score-uncacheable-files
19706 @vindex gnus-score-uncacheable-files
19707 @cindex score cache
19708 All score files are normally cached to avoid excessive re-loading of
19709 score files. However, if this might make your Emacs grow big and
19710 bloated, so this regexp can be used to weed out score files unlikely
19711 to be needed again. It would be a bad idea to deny caching of
19712 @file{all.SCORE}, while it might be a good idea to not cache
19713 @file{comp.infosystems.www.authoring.misc.ADAPT}. In fact, this
19714 variable is @samp{ADAPT$} by default, so no adaptive score files will
19717 @item gnus-save-score
19718 @vindex gnus-save-score
19719 If you have really complicated score files, and do lots of batch
19720 scoring, then you might set this variable to @code{t}. This will make
19721 Gnus save the scores into the @file{.newsrc.eld} file.
19723 If you do not set this to @code{t}, then manual scores (like those set
19724 with @kbd{V s} (@code{gnus-summary-set-score})) will not be preserved
19725 across group visits.
19727 @item gnus-score-interactive-default-score
19728 @vindex gnus-score-interactive-default-score
19729 Score used by all the interactive raise/lower commands to raise/lower
19730 score with. Default is 1000, which may seem excessive, but this is to
19731 ensure that the adaptive scoring scheme gets enough room to play with.
19732 We don't want the small changes from the adaptive scoring to overwrite
19733 manually entered data.
19735 @item gnus-summary-default-score
19736 @vindex gnus-summary-default-score
19737 Default score of an article, which is 0 by default.
19739 @item gnus-summary-expunge-below
19740 @vindex gnus-summary-expunge-below
19741 Don't display the summary lines of articles that have scores lower than
19742 this variable. This is @code{nil} by default, which means that no
19743 articles will be hidden. This variable is local to the summary buffers,
19744 and has to be set from @code{gnus-summary-mode-hook}.
19746 @item gnus-score-over-mark
19747 @vindex gnus-score-over-mark
19748 Mark (in the third column) used for articles with a score over the
19749 default. Default is @samp{+}.
19751 @item gnus-score-below-mark
19752 @vindex gnus-score-below-mark
19753 Mark (in the third column) used for articles with a score below the
19754 default. Default is @samp{-}.
19756 @item gnus-score-find-score-files-function
19757 @vindex gnus-score-find-score-files-function
19758 Function used to find score files for the current group. This function
19759 is called with the name of the group as the argument.
19761 Predefined functions available are:
19764 @item gnus-score-find-single
19765 @findex gnus-score-find-single
19766 Only apply the group's own score file.
19768 @item gnus-score-find-bnews
19769 @findex gnus-score-find-bnews
19770 Apply all score files that match, using bnews syntax. This is the
19771 default. If the current group is @samp{gnu.emacs.gnus}, for instance,
19772 @file{all.emacs.all.SCORE}, @file{not.alt.all.SCORE} and
19773 @file{gnu.all.SCORE} would all apply. In short, the instances of
19774 @samp{all} in the score file names are translated into @samp{.*}, and
19775 then a regexp match is done.
19777 This means that if you have some score entries that you want to apply to
19778 all groups, then you put those entries in the @file{all.SCORE} file.
19780 The score files are applied in a semi-random order, although Gnus will
19781 try to apply the more general score files before the more specific score
19782 files. It does this by looking at the number of elements in the score
19783 file names---discarding the @samp{all} elements.
19785 @item gnus-score-find-hierarchical
19786 @findex gnus-score-find-hierarchical
19787 Apply all score files from all the parent groups. This means that you
19788 can't have score files like @file{all.SCORE}, but you can have
19789 @file{SCORE}, @file{comp.SCORE} and @file{comp.emacs.SCORE} for each
19793 This variable can also be a list of functions. In that case, all
19794 these functions will be called with the group name as argument, and
19795 all the returned lists of score files will be applied. These
19796 functions can also return lists of lists of score alists directly. In
19797 that case, the functions that return these non-file score alists
19798 should probably be placed before the ``real'' score file functions, to
19799 ensure that the last score file returned is the local score file.
19802 For example, to do hierarchical scoring but use a non-server-specific
19803 overall score file, you could use the value
19805 (list (lambda (group) ("all.SCORE"))
19806 'gnus-score-find-hierarchical)
19809 @item gnus-score-expiry-days
19810 @vindex gnus-score-expiry-days
19811 This variable says how many days should pass before an unused score file
19812 entry is expired. If this variable is @code{nil}, no score file entries
19813 are expired. It's 7 by default.
19815 @item gnus-update-score-entry-dates
19816 @vindex gnus-update-score-entry-dates
19817 If this variable is non-@code{nil}, temporary score entries that have
19818 been triggered (matched) will have their dates updated. (This is how Gnus
19819 controls expiry---all non-matched-entries will become too old while
19820 matched entries will stay fresh and young.) However, if you set this
19821 variable to @code{nil}, even matched entries will grow old and will
19822 have to face that oh-so grim reaper.
19824 @item gnus-score-after-write-file-function
19825 @vindex gnus-score-after-write-file-function
19826 Function called with the name of the score file just written.
19828 @item gnus-score-thread-simplify
19829 @vindex gnus-score-thread-simplify
19830 If this variable is non-@code{nil}, article subjects will be
19831 simplified for subject scoring purposes in the same manner as with
19832 threading---according to the current value of
19833 @code{gnus-simplify-subject-functions}. If the scoring entry uses
19834 @code{substring} or @code{exact} matching, the match will also be
19835 simplified in this manner.
19840 @node Score File Format
19841 @section Score File Format
19842 @cindex score file format
19844 A score file is an @code{emacs-lisp} file that normally contains just a
19845 single form. Casual users are not expected to edit these files;
19846 everything can be changed from the summary buffer.
19848 Anyway, if you'd like to dig into it yourself, here's an example:
19852 ("Lars Ingebrigtsen" -10000)
19854 ("larsi\\|lmi" -50000 nil R))
19856 ("Ding is Badd" nil 728373))
19858 ("alt.politics" -1000 728372 s))
19863 (mark-and-expunge -10)
19867 (files "/hom/larsi/News/gnu.SCORE")
19868 (exclude-files "all.SCORE")
19869 (local (gnus-newsgroup-auto-expire t)
19870 (gnus-summary-make-false-root empty))
19874 This example demonstrates most score file elements. @xref{Advanced
19875 Scoring}, for a different approach.
19877 Even though this looks much like Lisp code, nothing here is actually
19878 @code{eval}ed. The Lisp reader is used to read this form, though, so it
19879 has to be valid syntactically, if not semantically.
19881 Six keys are supported by this alist:
19886 If the key is a string, it is the name of the header to perform the
19887 match on. Scoring can only be performed on these eight headers:
19888 @code{From}, @code{Subject}, @code{References}, @code{Message-ID},
19889 @code{Xref}, @code{Lines}, @code{Chars} and @code{Date}. In addition to
19890 these headers, there are three strings to tell Gnus to fetch the entire
19891 article and do the match on larger parts of the article: @code{Body}
19892 will perform the match on the body of the article, @code{Head} will
19893 perform the match on the head of the article, and @code{All} will
19894 perform the match on the entire article. Note that using any of these
19895 last three keys will slow down group entry @emph{considerably}. The
19896 final ``header'' you can score on is @code{Followup}. These score
19897 entries will result in new score entries being added for all follow-ups
19898 to articles that matches these score entries.
19900 Following this key is an arbitrary number of score entries, where each
19901 score entry has one to four elements.
19905 The first element is the @dfn{match element}. On most headers this will
19906 be a string, but on the Lines and Chars headers, this must be an
19910 If the second element is present, it should be a number---the @dfn{score
19911 element}. This number should be an integer in the neginf to posinf
19912 interval. This number is added to the score of the article if the match
19913 is successful. If this element is not present, the
19914 @code{gnus-score-interactive-default-score} number will be used
19915 instead. This is 1000 by default.
19918 If the third element is present, it should be a number---the @dfn{date
19919 element}. This date says when the last time this score entry matched,
19920 which provides a mechanism for expiring the score entries. It this
19921 element is not present, the score entry is permanent. The date is
19922 represented by the number of days since December 31, 1 BCE.
19925 If the fourth element is present, it should be a symbol---the @dfn{type
19926 element}. This element specifies what function should be used to see
19927 whether this score entry matches the article. What match types that can
19928 be used depends on what header you wish to perform the match on.
19931 @item From, Subject, References, Xref, Message-ID
19932 For most header types, there are the @code{r} and @code{R} (regexp), as
19933 well as @code{s} and @code{S} (substring) types, and @code{e} and
19934 @code{E} (exact match), and @code{w} (word match) types. If this
19935 element is not present, Gnus will assume that substring matching should
19936 be used. @code{R}, @code{S}, and @code{E} differ from the others in
19937 that the matches will be done in a case-sensitive manner. All these
19938 one-letter types are really just abbreviations for the @code{regexp},
19939 @code{string}, @code{exact}, and @code{word} types, which you can use
19940 instead, if you feel like.
19943 Just as for the standard string overview headers, if you are using
19944 gnus-extra-headers, you can score on these headers' values. In this
19945 case, there is a 5th element in the score entry, being the name of the
19946 header to be scored. The following entry is useful in your
19947 @file{all.SCORE} file in case of spam attacks from a single origin
19948 host, if your @acronym{NNTP} server tracks @samp{NNTP-Posting-Host} in
19952 ("111.222.333.444" -1000 nil s
19953 "NNTP-Posting-Host")
19957 These two headers use different match types: @code{<}, @code{>},
19958 @code{=}, @code{>=} and @code{<=}.
19960 These predicates are true if
19963 (PREDICATE HEADER MATCH)
19966 evaluates to non-@code{nil}. For instance, the advanced match
19967 @code{("lines" 4 <)} (@pxref{Advanced Scoring}) will result in the
19974 Or to put it another way: When using @code{<} on @code{Lines} with 4 as
19975 the match, we get the score added if the article has less than 4 lines.
19976 (It's easy to get confused and think it's the other way around. But
19977 it's not. I think.)
19979 When matching on @code{Lines}, be careful because some back ends (like
19980 @code{nndir}) do not generate @code{Lines} header, so every article ends
19981 up being marked as having 0 lines. This can lead to strange results if
19982 you happen to lower score of the articles with few lines.
19985 For the Date header we have three kinda silly match types:
19986 @code{before}, @code{at} and @code{after}. I can't really imagine this
19987 ever being useful, but, like, it would feel kinda silly not to provide
19988 this function. Just in case. You never know. Better safe than sorry.
19989 Once burnt, twice shy. Don't judge a book by its cover. Never not have
19990 sex on a first date. (I have been told that at least one person, and I
19991 quote, ``found this function indispensable'', however.)
19995 A more useful match type is @code{regexp}. With it, you can match the
19996 date string using a regular expression. The date is normalized to
19997 ISO8601 compact format first---@var{YYYYMMDD}@code{T}@var{HHMMSS}. If
19998 you want to match all articles that have been posted on April 1st in
19999 every year, you could use @samp{....0401.........} as a match string,
20000 for instance. (Note that the date is kept in its original time zone, so
20001 this will match articles that were posted when it was April 1st where
20002 the article was posted from. Time zones are such wholesome fun for the
20005 @item Head, Body, All
20006 These three match keys use the same match types as the @code{From} (etc)
20010 This match key is somewhat special, in that it will match the
20011 @code{From} header, and affect the score of not only the matching
20012 articles, but also all followups to the matching articles. This allows
20013 you e.g. increase the score of followups to your own articles, or
20014 decrease the score of followups to the articles of some known
20015 trouble-maker. Uses the same match types as the @code{From} header
20016 uses. (Using this match key will lead to creation of @file{ADAPT}
20020 This match key works along the same lines as the @code{Followup} match
20021 key. If you say that you want to score on a (sub-)thread started by an
20022 article with a @code{Message-ID} @var{x}, then you add a @samp{thread}
20023 match. This will add a new @samp{thread} match for each article that
20024 has @var{x} in its @code{References} header. (These new @samp{thread}
20025 matches will use the @code{Message-ID}s of these matching articles.)
20026 This will ensure that you can raise/lower the score of an entire thread,
20027 even though some articles in the thread may not have complete
20028 @code{References} headers. Note that using this may lead to
20029 undeterministic scores of the articles in the thread. (Using this match
20030 key will lead to creation of @file{ADAPT} files.)
20034 @cindex score file atoms
20036 The value of this entry should be a number. Any articles with a score
20037 lower than this number will be marked as read.
20040 The value of this entry should be a number. Any articles with a score
20041 lower than this number will be removed from the summary buffer.
20043 @item mark-and-expunge
20044 The value of this entry should be a number. Any articles with a score
20045 lower than this number will be marked as read and removed from the
20048 @item thread-mark-and-expunge
20049 The value of this entry should be a number. All articles that belong to
20050 a thread that has a total score below this number will be marked as read
20051 and removed from the summary buffer. @code{gnus-thread-score-function}
20052 says how to compute the total score for a thread.
20055 The value of this entry should be any number of file names. These files
20056 are assumed to be score files as well, and will be loaded the same way
20059 @item exclude-files
20060 The clue of this entry should be any number of files. These files will
20061 not be loaded, even though they would normally be so, for some reason or
20065 The value of this entry will be @code{eval}el. This element will be
20066 ignored when handling global score files.
20069 Read-only score files will not be updated or saved. Global score files
20070 should feature this atom (@pxref{Global Score Files}). (Note:
20071 @dfn{Global} here really means @dfn{global}; not your personal
20072 apply-to-all-groups score files.)
20075 The value of this entry should be a number. Articles that do not have
20076 parents will get this number added to their scores. Imagine you follow
20077 some high-volume newsgroup, like @samp{comp.lang.c}. Most likely you
20078 will only follow a few of the threads, also want to see any new threads.
20080 You can do this with the following two score file entries:
20084 (mark-and-expunge -100)
20087 When you enter the group the first time, you will only see the new
20088 threads. You then raise the score of the threads that you find
20089 interesting (with @kbd{I T} or @kbd{I S}), and ignore (@kbd{C y}) the
20090 rest. Next time you enter the group, you will see new articles in the
20091 interesting threads, plus any new threads.
20093 I.e.---the orphan score atom is for high-volume groups where a few
20094 interesting threads which can't be found automatically by ordinary
20095 scoring rules exist.
20098 This entry controls the adaptive scoring. If it is @code{t}, the
20099 default adaptive scoring rules will be used. If it is @code{ignore}, no
20100 adaptive scoring will be performed on this group. If it is a list, this
20101 list will be used as the adaptive scoring rules. If it isn't present,
20102 or is something other than @code{t} or @code{ignore}, the default
20103 adaptive scoring rules will be used. If you want to use adaptive
20104 scoring on most groups, you'd set @code{gnus-use-adaptive-scoring} to
20105 @code{t}, and insert an @code{(adapt ignore)} in the groups where you do
20106 not want adaptive scoring. If you only want adaptive scoring in a few
20107 groups, you'd set @code{gnus-use-adaptive-scoring} to @code{nil}, and
20108 insert @code{(adapt t)} in the score files of the groups where you want
20112 All adaptive score entries will go to the file named by this entry. It
20113 will also be applied when entering the group. This atom might be handy
20114 if you want to adapt on several groups at once, using the same adaptive
20115 file for a number of groups.
20118 @cindex local variables
20119 The value of this entry should be a list of @code{(@var{var}
20120 @var{value})} pairs. Each @var{var} will be made buffer-local to the
20121 current summary buffer, and set to the value specified. This is a
20122 convenient, if somewhat strange, way of setting variables in some
20123 groups if you don't like hooks much. Note that the @var{value} won't
20128 @node Score File Editing
20129 @section Score File Editing
20131 You normally enter all scoring commands from the summary buffer, but you
20132 might feel the urge to edit them by hand as well, so we've supplied you
20133 with a mode for that.
20135 It's simply a slightly customized @code{emacs-lisp} mode, with these
20136 additional commands:
20141 @kindex C-c C-c (Score)
20142 @findex gnus-score-edit-done
20143 Save the changes you have made and return to the summary buffer
20144 (@code{gnus-score-edit-done}).
20147 @kindex C-c C-d (Score)
20148 @findex gnus-score-edit-insert-date
20149 Insert the current date in numerical format
20150 (@code{gnus-score-edit-insert-date}). This is really the day number, if
20151 you were wondering.
20154 @kindex C-c C-p (Score)
20155 @findex gnus-score-pretty-print
20156 The adaptive score files are saved in an unformatted fashion. If you
20157 intend to read one of these files, you want to @dfn{pretty print} it
20158 first. This command (@code{gnus-score-pretty-print}) does that for
20163 Type @kbd{M-x gnus-score-mode} to use this mode.
20165 @vindex gnus-score-mode-hook
20166 @code{gnus-score-menu-hook} is run in score mode buffers.
20168 In the summary buffer you can use commands like @kbd{V f}, @kbd{V e} and
20169 @kbd{V t} to begin editing score files.
20172 @node Adaptive Scoring
20173 @section Adaptive Scoring
20174 @cindex adaptive scoring
20176 If all this scoring is getting you down, Gnus has a way of making it all
20177 happen automatically---as if by magic. Or rather, as if by artificial
20178 stupidity, to be precise.
20180 @vindex gnus-use-adaptive-scoring
20181 When you read an article, or mark an article as read, or kill an
20182 article, you leave marks behind. On exit from the group, Gnus can sniff
20183 these marks and add score elements depending on what marks it finds.
20184 You turn on this ability by setting @code{gnus-use-adaptive-scoring} to
20185 @code{t} or @code{(line)}. If you want score adaptively on separate
20186 words appearing in the subjects, you should set this variable to
20187 @code{(word)}. If you want to use both adaptive methods, set this
20188 variable to @code{(word line)}.
20190 @vindex gnus-default-adaptive-score-alist
20191 To give you complete control over the scoring process, you can customize
20192 the @code{gnus-default-adaptive-score-alist} variable. For instance, it
20193 might look something like this:
20196 (setq gnus-default-adaptive-score-alist
20197 '((gnus-unread-mark)
20198 (gnus-ticked-mark (from 4))
20199 (gnus-dormant-mark (from 5))
20200 (gnus-del-mark (from -4) (subject -1))
20201 (gnus-read-mark (from 4) (subject 2))
20202 (gnus-expirable-mark (from -1) (subject -1))
20203 (gnus-killed-mark (from -1) (subject -3))
20204 (gnus-kill-file-mark)
20205 (gnus-ancient-mark)
20206 (gnus-low-score-mark)
20207 (gnus-catchup-mark (from -1) (subject -1))))
20210 As you see, each element in this alist has a mark as a key (either a
20211 variable name or a ``real'' mark---a character). Following this key is
20212 a arbitrary number of header/score pairs. If there are no header/score
20213 pairs following the key, no adaptive scoring will be done on articles
20214 that have that key as the article mark. For instance, articles with
20215 @code{gnus-unread-mark} in the example above will not get adaptive score
20218 Each article can have only one mark, so just a single of these rules
20219 will be applied to each article.
20221 To take @code{gnus-del-mark} as an example---this alist says that all
20222 articles that have that mark (i.e., are marked with @samp{e}) will have a
20223 score entry added to lower based on the @code{From} header by -4, and
20224 lowered by @code{Subject} by -1. Change this to fit your prejudices.
20226 If you have marked 10 articles with the same subject with
20227 @code{gnus-del-mark}, the rule for that mark will be applied ten times.
20228 That means that that subject will get a score of ten times -1, which
20229 should be, unless I'm much mistaken, -10.
20231 If you have auto-expirable (mail) groups (@pxref{Expiring Mail}), all
20232 the read articles will be marked with the @samp{E} mark. This'll
20233 probably make adaptive scoring slightly impossible, so auto-expiring and
20234 adaptive scoring doesn't really mix very well.
20236 The headers you can score on are @code{from}, @code{subject},
20237 @code{message-id}, @code{references}, @code{xref}, @code{lines},
20238 @code{chars} and @code{date}. In addition, you can score on
20239 @code{followup}, which will create an adaptive score entry that matches
20240 on the @code{References} header using the @code{Message-ID} of the
20241 current article, thereby matching the following thread.
20243 If you use this scheme, you should set the score file atom @code{mark}
20244 to something small---like -300, perhaps, to avoid having small random
20245 changes result in articles getting marked as read.
20247 After using adaptive scoring for a week or so, Gnus should start to
20248 become properly trained and enhance the authors you like best, and kill
20249 the authors you like least, without you having to say so explicitly.
20251 You can control what groups the adaptive scoring is to be performed on
20252 by using the score files (@pxref{Score File Format}). This will also
20253 let you use different rules in different groups.
20255 @vindex gnus-adaptive-file-suffix
20256 The adaptive score entries will be put into a file where the name is the
20257 group name with @code{gnus-adaptive-file-suffix} appended. The default
20260 @vindex gnus-adaptive-pretty-print
20261 Adaptive score files can get huge and are not meant to be edited by
20262 human hands. If @code{gnus-adaptive-pretty-print} is @code{nil} (the
20263 deafult) those files will not be written in a human readable way.
20265 @vindex gnus-score-exact-adapt-limit
20266 When doing adaptive scoring, substring or fuzzy matching would probably
20267 give you the best results in most cases. However, if the header one
20268 matches is short, the possibility for false positives is great, so if
20269 the length of the match is less than
20270 @code{gnus-score-exact-adapt-limit}, exact matching will be used. If
20271 this variable is @code{nil}, exact matching will always be used to avoid
20274 @vindex gnus-default-adaptive-word-score-alist
20275 As mentioned above, you can adapt either on individual words or entire
20276 headers. If you adapt on words, the
20277 @code{gnus-default-adaptive-word-score-alist} variable says what score
20278 each instance of a word should add given a mark.
20281 (setq gnus-default-adaptive-word-score-alist
20282 `((,gnus-read-mark . 30)
20283 (,gnus-catchup-mark . -10)
20284 (,gnus-killed-mark . -20)
20285 (,gnus-del-mark . -15)))
20288 This is the default value. If you have adaption on words enabled, every
20289 word that appears in subjects of articles marked with
20290 @code{gnus-read-mark} will result in a score rule that increase the
20291 score with 30 points.
20293 @vindex gnus-default-ignored-adaptive-words
20294 @vindex gnus-ignored-adaptive-words
20295 Words that appear in the @code{gnus-default-ignored-adaptive-words} list
20296 will be ignored. If you wish to add more words to be ignored, use the
20297 @code{gnus-ignored-adaptive-words} list instead.
20299 @vindex gnus-adaptive-word-length-limit
20300 Some may feel that short words shouldn't count when doing adaptive
20301 scoring. If so, you may set @code{gnus-adaptive-word-length-limit} to
20302 an integer. Words shorter than this number will be ignored. This
20303 variable defaults to @code{nil}.
20305 @vindex gnus-adaptive-word-syntax-table
20306 When the scoring is done, @code{gnus-adaptive-word-syntax-table} is the
20307 syntax table in effect. It is similar to the standard syntax table, but
20308 it considers numbers to be non-word-constituent characters.
20310 @vindex gnus-adaptive-word-minimum
20311 If @code{gnus-adaptive-word-minimum} is set to a number, the adaptive
20312 word scoring process will never bring down the score of an article to
20313 below this number. The default is @code{nil}.
20315 @vindex gnus-adaptive-word-no-group-words
20316 If @code{gnus-adaptive-word-no-group-words} is set to @code{t}, gnus
20317 won't adaptively word score any of the words in the group name. Useful
20318 for groups like @samp{comp.editors.emacs}, where most of the subject
20319 lines contain the word @samp{emacs}.
20321 After using this scheme for a while, it might be nice to write a
20322 @code{gnus-psychoanalyze-user} command to go through the rules and see
20323 what words you like and what words you don't like. Or perhaps not.
20325 Note that the adaptive word scoring thing is highly experimental and is
20326 likely to change in the future. Initial impressions seem to indicate
20327 that it's totally useless as it stands. Some more work (involving more
20328 rigorous statistical methods) will have to be done to make this useful.
20331 @node Home Score File
20332 @section Home Score File
20334 The score file where new score file entries will go is called the
20335 @dfn{home score file}. This is normally (and by default) the score file
20336 for the group itself. For instance, the home score file for
20337 @samp{gnu.emacs.gnus} is @file{gnu.emacs.gnus.SCORE}.
20339 However, this may not be what you want. It is often convenient to share
20340 a common home score file among many groups---all @samp{emacs} groups
20341 could perhaps use the same home score file.
20343 @vindex gnus-home-score-file
20344 The variable that controls this is @code{gnus-home-score-file}. It can
20349 A string. Then this file will be used as the home score file for all
20353 A function. The result of this function will be used as the home score
20354 file. The function will be called with the name of the group as the
20358 A list. The elements in this list can be:
20362 @code{(@var{regexp} @var{file-name})}. If the @var{regexp} matches the
20363 group name, the @var{file-name} will be used as the home score file.
20366 A function. If the function returns non-@code{nil}, the result will
20367 be used as the home score file.
20370 A string. Use the string as the home score file.
20373 The list will be traversed from the beginning towards the end looking
20378 So, if you want to use just a single score file, you could say:
20381 (setq gnus-home-score-file
20382 "my-total-score-file.SCORE")
20385 If you want to use @file{gnu.SCORE} for all @samp{gnu} groups and
20386 @file{rec.SCORE} for all @samp{rec} groups (and so on), you can say:
20388 @findex gnus-hierarchial-home-score-file
20390 (setq gnus-home-score-file
20391 'gnus-hierarchial-home-score-file)
20394 This is a ready-made function provided for your convenience.
20395 Other functions include
20398 @item gnus-current-home-score-file
20399 @findex gnus-current-home-score-file
20400 Return the ``current'' regular score file. This will make scoring
20401 commands add entry to the ``innermost'' matching score file.
20405 If you want to have one score file for the @samp{emacs} groups and
20406 another for the @samp{comp} groups, while letting all other groups use
20407 their own home score files:
20410 (setq gnus-home-score-file
20411 ;; @r{All groups that match the regexp @code{"\\.emacs"}}
20412 '(("\\.emacs" "emacs.SCORE")
20413 ;; @r{All the comp groups in one score file}
20414 ("^comp" "comp.SCORE")))
20417 @vindex gnus-home-adapt-file
20418 @code{gnus-home-adapt-file} works exactly the same way as
20419 @code{gnus-home-score-file}, but says what the home adaptive score file
20420 is instead. All new adaptive file entries will go into the file
20421 specified by this variable, and the same syntax is allowed.
20423 In addition to using @code{gnus-home-score-file} and
20424 @code{gnus-home-adapt-file}, you can also use group parameters
20425 (@pxref{Group Parameters}) and topic parameters (@pxref{Topic
20426 Parameters}) to achieve much the same. Group and topic parameters take
20427 precedence over this variable.
20430 @node Followups To Yourself
20431 @section Followups To Yourself
20433 Gnus offers two commands for picking out the @code{Message-ID} header in
20434 the current buffer. Gnus will then add a score rule that scores using
20435 this @code{Message-ID} on the @code{References} header of other
20436 articles. This will, in effect, increase the score of all articles that
20437 respond to the article in the current buffer. Quite useful if you want
20438 to easily note when people answer what you've said.
20442 @item gnus-score-followup-article
20443 @findex gnus-score-followup-article
20444 This will add a score to articles that directly follow up your own
20447 @item gnus-score-followup-thread
20448 @findex gnus-score-followup-thread
20449 This will add a score to all articles that appear in a thread ``below''
20453 @vindex message-sent-hook
20454 These two functions are both primarily meant to be used in hooks like
20455 @code{message-sent-hook}, like this:
20457 (add-hook 'message-sent-hook 'gnus-score-followup-thread)
20461 If you look closely at your own @code{Message-ID}, you'll notice that
20462 the first two or three characters are always the same. Here's two of
20466 <x6u3u47icf.fsf@@eyesore.no>
20467 <x6sp9o7ibw.fsf@@eyesore.no>
20470 So ``my'' ident on this machine is @samp{x6}. This can be
20471 exploited---the following rule will raise the score on all followups to
20476 ("<x6[0-9a-z]+\\.fsf\\(_-_\\)?@@.*eyesore\\.no>"
20480 Whether it's the first two or first three characters that are ``yours''
20481 is system-dependent.
20484 @node Scoring On Other Headers
20485 @section Scoring On Other Headers
20486 @cindex scoring on other headers
20488 Gnus is quite fast when scoring the ``traditional''
20489 headers---@samp{From}, @samp{Subject} and so on. However, scoring
20490 other headers requires writing a @code{head} scoring rule, which means
20491 that Gnus has to request every single article from the back end to find
20492 matches. This takes a long time in big groups.
20494 Now, there's not much you can do about this for news groups, but for
20495 mail groups, you have greater control. In @ref{To From Newsgroups},
20496 it's explained in greater detail what this mechanism does, but here's
20497 a cookbook example for @code{nnml} on how to allow scoring on the
20498 @samp{To} and @samp{Cc} headers.
20500 Put the following in your @file{~/.gnus.el} file.
20503 (setq gnus-extra-headers '(To Cc Newsgroups Keywords)
20504 nnmail-extra-headers gnus-extra-headers)
20507 Restart Gnus and rebuild your @code{nnml} overview files with the
20508 @kbd{M-x nnml-generate-nov-databases} command. This will take a long
20509 time if you have much mail.
20511 Now you can score on @samp{To} and @samp{Cc} as ``extra headers'' like
20512 so: @kbd{I e s p To RET <your name> RET}.
20518 @section Scoring Tips
20519 @cindex scoring tips
20525 @cindex scoring crossposts
20526 If you want to lower the score of crossposts, the line to match on is
20527 the @code{Xref} header.
20529 ("xref" (" talk.politics.misc:" -1000))
20532 @item Multiple crossposts
20533 If you want to lower the score of articles that have been crossposted to
20534 more than, say, 3 groups:
20537 ("[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+"
20541 @item Matching on the body
20542 This is generally not a very good idea---it takes a very long time.
20543 Gnus actually has to fetch each individual article from the server. But
20544 you might want to anyway, I guess. Even though there are three match
20545 keys (@code{Head}, @code{Body} and @code{All}), you should choose one
20546 and stick with it in each score file. If you use any two, each article
20547 will be fetched @emph{twice}. If you want to match a bit on the
20548 @code{Head} and a bit on the @code{Body}, just use @code{All} for all
20551 @item Marking as read
20552 You will probably want to mark articles that have scores below a certain
20553 number as read. This is most easily achieved by putting the following
20554 in your @file{all.SCORE} file:
20558 You may also consider doing something similar with @code{expunge}.
20560 @item Negated character classes
20561 If you say stuff like @code{[^abcd]*}, you may get unexpected results.
20562 That will match newlines, which might lead to, well, The Unknown. Say
20563 @code{[^abcd\n]*} instead.
20567 @node Reverse Scoring
20568 @section Reverse Scoring
20569 @cindex reverse scoring
20571 If you want to keep just articles that have @samp{Sex with Emacs} in the
20572 subject header, and expunge all other articles, you could put something
20573 like this in your score file:
20577 ("Sex with Emacs" 2))
20582 So, you raise all articles that match @samp{Sex with Emacs} and mark the
20583 rest as read, and expunge them to boot.
20586 @node Global Score Files
20587 @section Global Score Files
20588 @cindex global score files
20590 Sure, other newsreaders have ``global kill files''. These are usually
20591 nothing more than a single kill file that applies to all groups, stored
20592 in the user's home directory. Bah! Puny, weak newsreaders!
20594 What I'm talking about here are Global Score Files. Score files from
20595 all over the world, from users everywhere, uniting all nations in one
20596 big, happy score file union! Ange-score! New and untested!
20598 @vindex gnus-global-score-files
20599 All you have to do to use other people's score files is to set the
20600 @code{gnus-global-score-files} variable. One entry for each score file,
20601 or each score file directory. Gnus will decide by itself what score
20602 files are applicable to which group.
20604 To use the score file
20605 @file{/ftp@@ftp.gnus.org:/pub/larsi/ding/score/soc.motss.SCORE} and
20606 all score files in the @file{/ftp@@ftp.some-where:/pub/score} directory,
20610 (setq gnus-global-score-files
20611 '("/ftp@@ftp.gnus.org:/pub/larsi/ding/score/soc.motss.SCORE"
20612 "/ftp@@ftp.some-where:/pub/score/"))
20615 @findex gnus-score-search-global-directories
20617 Simple, eh? Directory names must end with a @samp{/}. These
20618 directories are typically scanned only once during each Gnus session.
20619 If you feel the need to manually re-scan the remote directories, you can
20620 use the @code{gnus-score-search-global-directories} command.
20622 Note that, at present, using this option will slow down group entry
20623 somewhat. (That is---a lot.)
20625 If you want to start maintaining score files for other people to use,
20626 just put your score file up for anonymous ftp and announce it to the
20627 world. Become a retro-moderator! Participate in the retro-moderator
20628 wars sure to ensue, where retro-moderators battle it out for the
20629 sympathy of the people, luring them to use their score files on false
20630 premises! Yay! The net is saved!
20632 Here are some tips for the would-be retro-moderator, off the top of my
20638 Articles heavily crossposted are probably junk.
20640 To lower a single inappropriate article, lower by @code{Message-ID}.
20642 Particularly brilliant authors can be raised on a permanent basis.
20644 Authors that repeatedly post off-charter for the group can safely be
20645 lowered out of existence.
20647 Set the @code{mark} and @code{expunge} atoms to obliterate the nastiest
20648 articles completely.
20651 Use expiring score entries to keep the size of the file down. You
20652 should probably have a long expiry period, though, as some sites keep
20653 old articles for a long time.
20656 @dots{} I wonder whether other newsreaders will support global score files
20657 in the future. @emph{Snicker}. Yup, any day now, newsreaders like Blue
20658 Wave, xrn and 1stReader are bound to implement scoring. Should we start
20659 holding our breath yet?
20663 @section Kill Files
20666 Gnus still supports those pesky old kill files. In fact, the kill file
20667 entries can now be expiring, which is something I wrote before Daniel
20668 Quinlan thought of doing score files, so I've left the code in there.
20670 In short, kill processing is a lot slower (and I do mean @emph{a lot})
20671 than score processing, so it might be a good idea to rewrite your kill
20672 files into score files.
20674 Anyway, a kill file is a normal @code{emacs-lisp} file. You can put any
20675 forms into this file, which means that you can use kill files as some
20676 sort of primitive hook function to be run on group entry, even though
20677 that isn't a very good idea.
20679 Normal kill files look like this:
20682 (gnus-kill "From" "Lars Ingebrigtsen")
20683 (gnus-kill "Subject" "ding")
20687 This will mark every article written by me as read, and remove the
20688 marked articles from the summary buffer. Very useful, you'll agree.
20690 Other programs use a totally different kill file syntax. If Gnus
20691 encounters what looks like a @code{rn} kill file, it will take a stab at
20694 Two summary functions for editing a @sc{gnus} kill file:
20699 @kindex M-k (Summary)
20700 @findex gnus-summary-edit-local-kill
20701 Edit this group's kill file (@code{gnus-summary-edit-local-kill}).
20704 @kindex M-K (Summary)
20705 @findex gnus-summary-edit-global-kill
20706 Edit the general kill file (@code{gnus-summary-edit-global-kill}).
20709 Two group mode functions for editing the kill files:
20714 @kindex M-k (Group)
20715 @findex gnus-group-edit-local-kill
20716 Edit this group's kill file (@code{gnus-group-edit-local-kill}).
20719 @kindex M-K (Group)
20720 @findex gnus-group-edit-global-kill
20721 Edit the general kill file (@code{gnus-group-edit-global-kill}).
20724 Kill file variables:
20727 @item gnus-kill-file-name
20728 @vindex gnus-kill-file-name
20729 A kill file for the group @samp{soc.motss} is normally called
20730 @file{soc.motss.KILL}. The suffix appended to the group name to get
20731 this file name is detailed by the @code{gnus-kill-file-name} variable.
20732 The ``global'' kill file (not in the score file sense of ``global'', of
20733 course) is just called @file{KILL}.
20735 @vindex gnus-kill-save-kill-file
20736 @item gnus-kill-save-kill-file
20737 If this variable is non-@code{nil}, Gnus will save the
20738 kill file after processing, which is necessary if you use expiring
20741 @item gnus-apply-kill-hook
20742 @vindex gnus-apply-kill-hook
20743 @findex gnus-apply-kill-file-unless-scored
20744 @findex gnus-apply-kill-file
20745 A hook called to apply kill files to a group. It is
20746 @code{(gnus-apply-kill-file)} by default. If you want to ignore the
20747 kill file if you have a score file for the same group, you can set this
20748 hook to @code{(gnus-apply-kill-file-unless-scored)}. If you don't want
20749 kill files to be processed, you should set this variable to @code{nil}.
20751 @item gnus-kill-file-mode-hook
20752 @vindex gnus-kill-file-mode-hook
20753 A hook called in kill-file mode buffers.
20758 @node Converting Kill Files
20759 @section Converting Kill Files
20761 @cindex converting kill files
20763 If you have loads of old kill files, you may want to convert them into
20764 score files. If they are ``regular'', you can use
20765 the @file{gnus-kill-to-score.el} package; if not, you'll have to do it
20768 The kill to score conversion package isn't included in Gnus by default.
20769 You can fetch it from
20770 @uref{http://www.stud.ifi.uio.no/~larsi/ding-various/gnus-kill-to-score.el}.
20772 If your old kill files are very complex---if they contain more
20773 non-@code{gnus-kill} forms than not, you'll have to convert them by
20774 hand. Or just let them be as they are. Gnus will still use them as
20778 @node Advanced Scoring
20779 @section Advanced Scoring
20781 Scoring on Subjects and From headers is nice enough, but what if you're
20782 really interested in what a person has to say only when she's talking
20783 about a particular subject? Or what if you really don't want to
20784 read what person A has to say when she's following up to person B, but
20785 want to read what she says when she's following up to person C?
20787 By using advanced scoring rules you may create arbitrarily complex
20791 * Advanced Scoring Syntax:: A definition.
20792 * Advanced Scoring Examples:: What they look like.
20793 * Advanced Scoring Tips:: Getting the most out of it.
20797 @node Advanced Scoring Syntax
20798 @subsection Advanced Scoring Syntax
20800 Ordinary scoring rules have a string as the first element in the rule.
20801 Advanced scoring rules have a list as the first element. The second
20802 element is the score to be applied if the first element evaluated to a
20803 non-@code{nil} value.
20805 These lists may consist of three logical operators, one redirection
20806 operator, and various match operators.
20813 This logical operator will evaluate each of its arguments until it finds
20814 one that evaluates to @code{false}, and then it'll stop. If all arguments
20815 evaluate to @code{true} values, then this operator will return
20820 This logical operator will evaluate each of its arguments until it finds
20821 one that evaluates to @code{true}. If no arguments are @code{true},
20822 then this operator will return @code{false}.
20827 This logical operator only takes a single argument. It returns the
20828 logical negation of the value of its argument.
20832 There is an @dfn{indirection operator} that will make its arguments
20833 apply to the ancestors of the current article being scored. For
20834 instance, @code{1-} will make score rules apply to the parent of the
20835 current article. @code{2-} will make score rules apply to the
20836 grandparent of the current article. Alternatively, you can write
20837 @code{^^}, where the number of @code{^}s (carets) says how far back into
20838 the ancestry you want to go.
20840 Finally, we have the match operators. These are the ones that do the
20841 real work. Match operators are header name strings followed by a match
20842 and a match type. A typical match operator looks like @samp{("from"
20843 "Lars Ingebrigtsen" s)}. The header names are the same as when using
20844 simple scoring, and the match types are also the same.
20847 @node Advanced Scoring Examples
20848 @subsection Advanced Scoring Examples
20850 Please note that the following examples are score file rules. To
20851 make a complete score file from them, surround them with another pair
20854 Let's say you want to increase the score of articles written by Lars
20855 when he's talking about Gnus:
20860 ("from" "Lars Ingebrigtsen")
20861 ("subject" "Gnus"))
20868 When he writes long articles, he sometimes has something nice to say:
20872 ("from" "Lars Ingebrigtsen")
20879 However, when he responds to things written by Reig Eigil Logge, you
20880 really don't want to read what he's written:
20884 ("from" "Lars Ingebrigtsen")
20885 (1- ("from" "Reig Eigir Logge")))
20889 Everybody that follows up Redmondo when he writes about disappearing
20890 socks should have their scores raised, but only when they talk about
20891 white socks. However, when Lars talks about socks, it's usually not
20898 ("from" "redmondo@@.*no" r)
20899 ("body" "disappearing.*socks" t)))
20900 (! ("from" "Lars Ingebrigtsen"))
20901 ("body" "white.*socks"))
20905 The possibilities are endless.
20908 @node Advanced Scoring Tips
20909 @subsection Advanced Scoring Tips
20911 The @code{&} and @code{|} logical operators do short-circuit logic.
20912 That is, they stop processing their arguments when it's clear what the
20913 result of the operation will be. For instance, if one of the arguments
20914 of an @code{&} evaluates to @code{false}, there's no point in evaluating
20915 the rest of the arguments. This means that you should put slow matches
20916 (@samp{body}, @samp{header}) last and quick matches (@samp{from},
20917 @samp{subject}) first.
20919 The indirection arguments (@code{1-} and so on) will make their
20920 arguments work on previous generations of the thread. If you say
20931 Then that means ``score on the from header of the grandparent of the
20932 current article''. An indirection is quite fast, but it's better to say:
20938 ("subject" "Gnus")))
20945 (1- ("from" "Lars"))
20946 (1- ("subject" "Gnus")))
20951 @section Score Decays
20952 @cindex score decays
20955 You may find that your scores have a tendency to grow without
20956 bounds, especially if you're using adaptive scoring. If scores get too
20957 big, they lose all meaning---they simply max out and it's difficult to
20958 use them in any sensible way.
20960 @vindex gnus-decay-scores
20961 @findex gnus-decay-score
20962 @vindex gnus-decay-score-function
20963 Gnus provides a mechanism for decaying scores to help with this problem.
20964 When score files are loaded and @code{gnus-decay-scores} is
20965 non-@code{nil}, Gnus will run the score files through the decaying
20966 mechanism thereby lowering the scores of all non-permanent score rules.
20967 If @code{gnus-decay-scores} is a regexp, only score files matching this
20968 regexp are treated. E.g. you may set it to @samp{\\.ADAPT\\'} if only
20969 @emph{adaptive} score files should be decayed. The decay itself if
20970 performed by the @code{gnus-decay-score-function} function, which is
20971 @code{gnus-decay-score} by default. Here's the definition of that
20975 (defun gnus-decay-score (score)
20976 "Decay SCORE according to `gnus-score-decay-constant'
20977 and `gnus-score-decay-scale'."
20979 (* (if (< score 0) -1 1)
20981 (max gnus-score-decay-constant
20983 gnus-score-decay-scale)))))))
20984 (if (and (featurep 'xemacs)
20985 ;; XEmacs' floor can handle only the floating point
20986 ;; number below the half of the maximum integer.
20987 (> (abs n) (lsh -1 -2)))
20989 (car (split-string (number-to-string n) "\\.")))
20993 @vindex gnus-score-decay-scale
20994 @vindex gnus-score-decay-constant
20995 @code{gnus-score-decay-constant} is 3 by default and
20996 @code{gnus-score-decay-scale} is 0.05. This should cause the following:
21000 Scores between -3 and 3 will be set to 0 when this function is called.
21003 Scores with magnitudes between 3 and 60 will be shrunk by 3.
21006 Scores with magnitudes greater than 60 will be shrunk by 5% of the
21010 If you don't like this decay function, write your own. It is called
21011 with the score to be decayed as its only parameter, and it should return
21012 the new score, which should be an integer.
21014 Gnus will try to decay scores once a day. If you haven't run Gnus for
21015 four days, Gnus will decay the scores four times, for instance.
21020 @include message.texi
21021 @chapter Emacs MIME
21022 @include emacs-mime.texi
21024 @include sieve.texi
21036 * Process/Prefix:: A convention used by many treatment commands.
21037 * Interactive:: Making Gnus ask you many questions.
21038 * Symbolic Prefixes:: How to supply some Gnus functions with options.
21039 * Formatting Variables:: You can specify what buffers should look like.
21040 * Window Layout:: Configuring the Gnus buffer windows.
21041 * Faces and Fonts:: How to change how faces look.
21042 * Compilation:: How to speed Gnus up.
21043 * Mode Lines:: Displaying information in the mode lines.
21044 * Highlighting and Menus:: Making buffers look all nice and cozy.
21045 * Buttons:: Get tendinitis in ten easy steps!
21046 * Daemons:: Gnus can do things behind your back.
21047 * NoCeM:: How to avoid spam and other fatty foods.
21048 * Undo:: Some actions can be undone.
21049 * Predicate Specifiers:: Specifying predicates.
21050 * Moderation:: What to do if you're a moderator.
21051 * Fetching a Group:: Starting Gnus just to read a group.
21052 * Image Enhancements:: Modern versions of Emacs/XEmacs can display images.
21053 * Fuzzy Matching:: What's the big fuzz?
21054 * Thwarting Email Spam:: A how-to on avoiding unsolicited commercial email.
21055 * Other modes:: Interaction with other modes.
21056 * Various Various:: Things that are really various.
21060 @node Process/Prefix
21061 @section Process/Prefix
21062 @cindex process/prefix convention
21064 Many functions, among them functions for moving, decoding and saving
21065 articles, use what is known as the @dfn{Process/Prefix convention}.
21067 This is a method for figuring out what articles the user wants the
21068 command to be performed on.
21072 If the numeric prefix is N, perform the operation on the next N
21073 articles, starting with the current one. If the numeric prefix is
21074 negative, perform the operation on the previous N articles, starting
21075 with the current one.
21077 @vindex transient-mark-mode
21078 If @code{transient-mark-mode} in non-@code{nil} and the region is
21079 active, all articles in the region will be worked upon.
21081 If there is no numeric prefix, but some articles are marked with the
21082 process mark, perform the operation on the articles marked with
21085 If there is neither a numeric prefix nor any articles marked with the
21086 process mark, just perform the operation on the current article.
21088 Quite simple, really, but it needs to be made clear so that surprises
21091 Commands that react to the process mark will push the current list of
21092 process marked articles onto a stack and will then clear all process
21093 marked articles. You can restore the previous configuration with the
21094 @kbd{M P y} command (@pxref{Setting Process Marks}).
21096 @vindex gnus-summary-goto-unread
21097 One thing that seems to shock & horrify lots of people is that, for
21098 instance, @kbd{3 d} does exactly the same as @kbd{d} @kbd{d} @kbd{d}.
21099 Since each @kbd{d} (which marks the current article as read) by default
21100 goes to the next unread article after marking, this means that @kbd{3 d}
21101 will mark the next three unread articles as read, no matter what the
21102 summary buffer looks like. Set @code{gnus-summary-goto-unread} to
21103 @code{nil} for a more straightforward action.
21105 Many commands do not use the process/prefix convention. All commands
21106 that do explicitly say so in this manual. To apply the process/prefix
21107 convention to commands that do not use it, you can use the @kbd{M-&}
21108 command. For instance, to mark all the articles in the group as
21109 expirable, you could say @kbd{M P b M-& E}.
21113 @section Interactive
21114 @cindex interaction
21118 @item gnus-novice-user
21119 @vindex gnus-novice-user
21120 If this variable is non-@code{nil}, you are either a newcomer to the
21121 World of Usenet, or you are very cautious, which is a nice thing to be,
21122 really. You will be given questions of the type ``Are you sure you want
21123 to do this?'' before doing anything dangerous. This is @code{t} by
21126 @item gnus-expert-user
21127 @vindex gnus-expert-user
21128 If this variable is non-@code{nil}, you will seldom be asked any
21129 questions by Gnus. It will simply assume you know what you're doing, no
21130 matter how strange.
21132 @item gnus-interactive-catchup
21133 @vindex gnus-interactive-catchup
21134 Require confirmation before catching up a group if non-@code{nil}. It
21135 is @code{t} by default.
21137 @item gnus-interactive-exit
21138 @vindex gnus-interactive-exit
21139 Require confirmation before exiting Gnus. This variable is @code{t} by
21144 @node Symbolic Prefixes
21145 @section Symbolic Prefixes
21146 @cindex symbolic prefixes
21148 Quite a lot of Emacs commands react to the (numeric) prefix. For
21149 instance, @kbd{C-u 4 C-f} moves point four characters forward, and
21150 @kbd{C-u 9 0 0 I s s p} adds a permanent @code{Subject} substring score
21151 rule of 900 to the current article.
21153 This is all nice and well, but what if you want to give a command some
21154 additional information? Well, what most commands do is interpret the
21155 ``raw'' prefix in some special way. @kbd{C-u 0 C-x C-s} means that one
21156 doesn't want a backup file to be created when saving the current buffer,
21157 for instance. But what if you want to save without making a backup
21158 file, and you want Emacs to flash lights and play a nice tune at the
21159 same time? You can't, and you're probably perfectly happy that way.
21161 @kindex M-i (Summary)
21162 @findex gnus-symbolic-argument
21163 I'm not, so I've added a second prefix---the @dfn{symbolic prefix}. The
21164 prefix key is @kbd{M-i} (@code{gnus-symbolic-argument}), and the next
21165 character typed in is the value. You can stack as many @kbd{M-i}
21166 prefixes as you want. @kbd{M-i a C-M-u} means ``feed the @kbd{C-M-u}
21167 command the symbolic prefix @code{a}''. @kbd{M-i a M-i b C-M-u} means
21168 ``feed the @kbd{C-M-u} command the symbolic prefixes @code{a} and
21169 @code{b}''. You get the drift.
21171 Typing in symbolic prefixes to commands that don't accept them doesn't
21172 hurt, but it doesn't do any good either. Currently not many Gnus
21173 functions make use of the symbolic prefix.
21175 If you're interested in how Gnus implements this, @pxref{Extended
21179 @node Formatting Variables
21180 @section Formatting Variables
21181 @cindex formatting variables
21183 Throughout this manual you've probably noticed lots of variables called
21184 things like @code{gnus-group-line-format} and
21185 @code{gnus-summary-mode-line-format}. These control how Gnus is to
21186 output lines in the various buffers. There's quite a lot of them.
21187 Fortunately, they all use the same syntax, so there's not that much to
21190 Here's an example format spec (from the group buffer): @samp{%M%S%5y:
21191 %(%g%)\n}. We see that it is indeed extremely ugly, and that there are
21192 lots of percentages everywhere.
21195 * Formatting Basics:: A formatting variable is basically a format string.
21196 * Mode Line Formatting:: Some rules about mode line formatting variables.
21197 * Advanced Formatting:: Modifying output in various ways.
21198 * User-Defined Specs:: Having Gnus call your own functions.
21199 * Formatting Fonts:: Making the formatting look colorful and nice.
21200 * Positioning Point:: Moving point to a position after an operation.
21201 * Tabulation:: Tabulating your output.
21202 * Wide Characters:: Dealing with wide characters.
21205 Currently Gnus uses the following formatting variables:
21206 @code{gnus-group-line-format}, @code{gnus-summary-line-format},
21207 @code{gnus-server-line-format}, @code{gnus-topic-line-format},
21208 @code{gnus-group-mode-line-format},
21209 @code{gnus-summary-mode-line-format},
21210 @code{gnus-article-mode-line-format},
21211 @code{gnus-server-mode-line-format}, and
21212 @code{gnus-summary-pick-line-format}.
21214 All these format variables can also be arbitrary elisp forms. In that
21215 case, they will be @code{eval}ed to insert the required lines.
21217 @kindex M-x gnus-update-format
21218 @findex gnus-update-format
21219 Gnus includes a command to help you while creating your own format
21220 specs. @kbd{M-x gnus-update-format} will @code{eval} the current form,
21221 update the spec in question and pop you to a buffer where you can
21222 examine the resulting Lisp code to be run to generate the line.
21226 @node Formatting Basics
21227 @subsection Formatting Basics
21229 Each @samp{%} element will be replaced by some string or other when the
21230 buffer in question is generated. @samp{%5y} means ``insert the @samp{y}
21231 spec, and pad with spaces to get a 5-character field''.
21233 As with normal C and Emacs Lisp formatting strings, the numerical
21234 modifier between the @samp{%} and the formatting type character will
21235 @dfn{pad} the output so that it is always at least that long.
21236 @samp{%5y} will make the field always (at least) five characters wide by
21237 padding with spaces to the left. If you say @samp{%-5y}, it will pad to
21240 You may also wish to limit the length of the field to protect against
21241 particularly wide values. For that you can say @samp{%4,6y}, which
21242 means that the field will never be more than 6 characters wide and never
21243 less than 4 characters wide.
21245 Also Gnus supports some extended format specifications, such as
21246 @samp{%&user-date;}.
21249 @node Mode Line Formatting
21250 @subsection Mode Line Formatting
21252 Mode line formatting variables (e.g.,
21253 @code{gnus-summary-mode-line-format}) follow the same rules as other,
21254 buffer line oriented formatting variables (@pxref{Formatting Basics})
21255 with the following two differences:
21260 There must be no newline (@samp{\n}) at the end.
21263 The special @samp{%%b} spec can be used to display the buffer name.
21264 Well, it's no spec at all, really---@samp{%%} is just a way to quote
21265 @samp{%} to allow it to pass through the formatting machinery unmangled,
21266 so that Emacs receives @samp{%b}, which is something the Emacs mode line
21267 display interprets to mean ``show the buffer name''. For a full list of
21268 mode line specs Emacs understands, see the documentation of the
21269 @code{mode-line-format} variable.
21274 @node Advanced Formatting
21275 @subsection Advanced Formatting
21277 It is frequently useful to post-process the fields in some way.
21278 Padding, limiting, cutting off parts and suppressing certain values can
21279 be achieved by using @dfn{tilde modifiers}. A typical tilde spec might
21280 look like @samp{%~(cut 3)~(ignore "0")y}.
21282 These are the valid modifiers:
21287 Pad the field to the left with spaces until it reaches the required
21291 Pad the field to the right with spaces until it reaches the required
21296 Cut off characters from the left until it reaches the specified length.
21299 Cut off characters from the right until it reaches the specified
21304 Cut off the specified number of characters from the left.
21307 Cut off the specified number of characters from the right.
21310 Return an empty string if the field is equal to the specified value.
21313 Use the specified form as the field value when the @samp{@@} spec is
21319 "~(form (current-time-string))@@"
21324 Let's take an example. The @samp{%o} spec in the summary mode lines
21325 will return a date in compact ISO8601 format---@samp{19960809T230410}.
21326 This is quite a mouthful, so we want to shave off the century number and
21327 the time, leaving us with a six-character date. That would be
21328 @samp{%~(cut-left 2)~(max-right 6)~(pad 6)o}. (Cutting is done before
21329 maxing, and we need the padding to ensure that the date is never less
21330 than 6 characters to make it look nice in columns.)
21332 Ignoring is done first; then cutting; then maxing; and then as the very
21333 last operation, padding.
21335 If you use lots of these advanced thingies, you'll find that Gnus gets
21336 quite slow. This can be helped enormously by running @kbd{M-x
21337 gnus-compile} when you are satisfied with the look of your lines.
21338 @xref{Compilation}.
21341 @node User-Defined Specs
21342 @subsection User-Defined Specs
21344 All the specs allow for inserting user defined specifiers---@samp{u}.
21345 The next character in the format string should be a letter. Gnus
21346 will call the function @code{gnus-user-format-function-}@samp{X}, where
21347 @samp{X} is the letter following @samp{%u}. The function will be passed
21348 a single parameter---what the parameter means depends on what buffer
21349 it's being called from. The function should return a string, which will
21350 be inserted into the buffer just like information from any other
21351 specifier. This function may also be called with dummy values, so it
21352 should protect against that.
21354 Also Gnus supports extended user-defined specs, such as @samp{%u&foo;}.
21355 Gnus will call the function @code{gnus-user-format-function-}@samp{foo}.
21357 You can also use tilde modifiers (@pxref{Advanced Formatting} to achieve
21358 much the same without defining new functions. Here's an example:
21359 @samp{%~(form (count-lines (point-min) (point)))@@}. The form
21360 given here will be evaluated to yield the current line number, and then
21364 @node Formatting Fonts
21365 @subsection Formatting Fonts
21367 There are specs for highlighting, and these are shared by all the format
21368 variables. Text inside the @samp{%(} and @samp{%)} specifiers will get
21369 the special @code{mouse-face} property set, which means that it will be
21370 highlighted (with @code{gnus-mouse-face}) when you put the mouse pointer
21373 Text inside the @samp{%@{} and @samp{%@}} specifiers will have their
21374 normal faces set using @code{gnus-face-0}, which is @code{bold} by
21375 default. If you say @samp{%1@{}, you'll get @code{gnus-face-1} instead,
21376 and so on. Create as many faces as you wish. The same goes for the
21377 @code{mouse-face} specs---you can say @samp{%3(hello%)} to have
21378 @samp{hello} mouse-highlighted with @code{gnus-mouse-face-3}.
21380 Text inside the @samp{%<<} and @samp{%>>} specifiers will get the
21381 special @code{balloon-help} property set to
21382 @code{gnus-balloon-face-0}. If you say @samp{%1<<}, you'll get
21383 @code{gnus-balloon-face-1} and so on. The @code{gnus-balloon-face-*}
21384 variables should be either strings or symbols naming functions that
21385 return a string. When the mouse passes over text with this property
21386 set, a balloon window will appear and display the string. Please
21387 refer to @ref{Tooltips, ,Tooltips, emacs, The Emacs Manual},
21388 (in GNU Emacs) or the doc string of @code{balloon-help-mode} (in
21389 XEmacs) for more information on this. (For technical reasons, the
21390 guillemets have been approximated as @samp{<<} and @samp{>>} in this
21393 Here's an alternative recipe for the group buffer:
21396 ;; @r{Create three face types.}
21397 (setq gnus-face-1 'bold)
21398 (setq gnus-face-3 'italic)
21400 ;; @r{We want the article count to be in}
21401 ;; @r{a bold and green face. So we create}
21402 ;; @r{a new face called @code{my-green-bold}.}
21403 (copy-face 'bold 'my-green-bold)
21404 ;; @r{Set the color.}
21405 (set-face-foreground 'my-green-bold "ForestGreen")
21406 (setq gnus-face-2 'my-green-bold)
21408 ;; @r{Set the new & fancy format.}
21409 (setq gnus-group-line-format
21410 "%M%S%3@{%5y%@}%2[:%] %(%1@{%g%@}%)\n")
21413 I'm sure you'll be able to use this scheme to create totally unreadable
21414 and extremely vulgar displays. Have fun!
21416 Note that the @samp{%(} specs (and friends) do not make any sense on the
21417 mode-line variables.
21419 @node Positioning Point
21420 @subsection Positioning Point
21422 Gnus usually moves point to a pre-defined place on each line in most
21423 buffers. By default, point move to the first colon character on the
21424 line. You can customize this behavior in three different ways.
21426 You can move the colon character to somewhere else on the line.
21428 @findex gnus-goto-colon
21429 You can redefine the function that moves the point to the colon. The
21430 function is called @code{gnus-goto-colon}.
21432 But perhaps the most convenient way to deal with this, if you don't want
21433 to have a colon in your line, is to use the @samp{%*} specifier. If you
21434 put a @samp{%*} somewhere in your format line definition, Gnus will
21439 @subsection Tabulation
21441 You can usually line up your displays by padding and cutting your
21442 strings. However, when combining various strings of different size, it
21443 can often be more convenient to just output the strings, and then worry
21444 about lining up the following text afterwards.
21446 To do that, Gnus supplies tabulator specs---@samp{%=}. There are two
21447 different types---@dfn{hard tabulators} and @dfn{soft tabulators}.
21449 @samp{%50=} will insert space characters to pad the line up to column
21450 50. If the text is already past column 50, nothing will be inserted.
21451 This is the soft tabulator.
21453 @samp{%-50=} will insert space characters to pad the line up to column
21454 50. If the text is already past column 50, the excess text past column
21455 50 will be removed. This is the hard tabulator.
21458 @node Wide Characters
21459 @subsection Wide Characters
21461 Fixed width fonts in most countries have characters of the same width.
21462 Some countries, however, use Latin characters mixed with wider
21463 characters---most notable East Asian countries.
21465 The problem is that when formatting, Gnus assumes that if a string is 10
21466 characters wide, it'll be 10 Latin characters wide on the screen. In
21467 these countries, that's not true.
21469 @vindex gnus-use-correct-string-widths
21470 To help fix this, you can set @code{gnus-use-correct-string-widths} to
21471 @code{t}. This makes buffer generation slower, but the results will be
21472 prettier. The default value under XEmacs is @code{t} but @code{nil}
21476 @node Window Layout
21477 @section Window Layout
21478 @cindex window layout
21480 No, there's nothing here about X, so be quiet.
21482 @vindex gnus-use-full-window
21483 If @code{gnus-use-full-window} non-@code{nil}, Gnus will delete all
21484 other windows and occupy the entire Emacs screen by itself. It is
21485 @code{t} by default.
21487 Setting this variable to @code{nil} kinda works, but there are
21488 glitches. Use at your own peril.
21490 @vindex gnus-buffer-configuration
21491 @code{gnus-buffer-configuration} describes how much space each Gnus
21492 buffer should be given. Here's an excerpt of this variable:
21495 ((group (vertical 1.0 (group 1.0 point)
21496 (if gnus-carpal (group-carpal 4))))
21497 (article (vertical 1.0 (summary 0.25 point)
21501 This is an alist. The @dfn{key} is a symbol that names some action or
21502 other. For instance, when displaying the group buffer, the window
21503 configuration function will use @code{group} as the key. A full list of
21504 possible names is listed below.
21506 The @dfn{value} (i.e., the @dfn{split}) says how much space each buffer
21507 should occupy. To take the @code{article} split as an example -
21510 (article (vertical 1.0 (summary 0.25 point)
21514 This @dfn{split} says that the summary buffer should occupy 25% of upper
21515 half of the screen, and that it is placed over the article buffer. As
21516 you may have noticed, 100% + 25% is actually 125% (yup, I saw y'all
21517 reaching for that calculator there). However, the special number
21518 @code{1.0} is used to signal that this buffer should soak up all the
21519 rest of the space available after the rest of the buffers have taken
21520 whatever they need. There should be only one buffer with the @code{1.0}
21521 size spec per split.
21523 Point will be put in the buffer that has the optional third element
21524 @code{point}. In a @code{frame} split, the last subsplit having a leaf
21525 split where the tag @code{frame-focus} is a member (i.e. is the third or
21526 fourth element in the list, depending on whether the @code{point} tag is
21527 present) gets focus.
21529 Here's a more complicated example:
21532 (article (vertical 1.0 (group 4)
21533 (summary 0.25 point)
21534 (if gnus-carpal (summary-carpal 4))
21538 If the size spec is an integer instead of a floating point number,
21539 then that number will be used to say how many lines a buffer should
21540 occupy, not a percentage.
21542 If the @dfn{split} looks like something that can be @code{eval}ed (to be
21543 precise---if the @code{car} of the split is a function or a subr), this
21544 split will be @code{eval}ed. If the result is non-@code{nil}, it will
21545 be used as a split. This means that there will be three buffers if
21546 @code{gnus-carpal} is @code{nil}, and four buffers if @code{gnus-carpal}
21549 Not complicated enough for you? Well, try this on for size:
21552 (article (horizontal 1.0
21557 (summary 0.25 point)
21562 Whoops. Two buffers with the mystery 100% tag. And what's that
21563 @code{horizontal} thingie?
21565 If the first element in one of the split is @code{horizontal}, Gnus will
21566 split the window horizontally, giving you two windows side-by-side.
21567 Inside each of these strips you may carry on all you like in the normal
21568 fashion. The number following @code{horizontal} says what percentage of
21569 the screen is to be given to this strip.
21571 For each split, there @emph{must} be one element that has the 100% tag.
21572 The splitting is never accurate, and this buffer will eat any leftover
21573 lines from the splits.
21575 To be slightly more formal, here's a definition of what a valid split
21580 split = frame | horizontal | vertical | buffer | form
21581 frame = "(frame " size *split ")"
21582 horizontal = "(horizontal " size *split ")"
21583 vertical = "(vertical " size *split ")"
21584 buffer = "(" buf-name " " size *[ "point" ] *[ "frame-focus"] ")"
21585 size = number | frame-params
21586 buf-name = group | article | summary ...
21590 The limitations are that the @code{frame} split can only appear as the
21591 top-level split. @var{form} should be an Emacs Lisp form that should
21592 return a valid split. We see that each split is fully recursive, and
21593 may contain any number of @code{vertical} and @code{horizontal} splits.
21595 @vindex gnus-window-min-width
21596 @vindex gnus-window-min-height
21597 @cindex window height
21598 @cindex window width
21599 Finding the right sizes can be a bit complicated. No window may be less
21600 than @code{gnus-window-min-height} (default 1) characters high, and all
21601 windows must be at least @code{gnus-window-min-width} (default 1)
21602 characters wide. Gnus will try to enforce this before applying the
21603 splits. If you want to use the normal Emacs window width/height limit,
21604 you can just set these two variables to @code{nil}.
21606 If you're not familiar with Emacs terminology, @code{horizontal} and
21607 @code{vertical} splits may work the opposite way of what you'd expect.
21608 Windows inside a @code{horizontal} split are shown side-by-side, and
21609 windows within a @code{vertical} split are shown above each other.
21611 @findex gnus-configure-frame
21612 If you want to experiment with window placement, a good tip is to call
21613 @code{gnus-configure-frame} directly with a split. This is the function
21614 that does all the real work when splitting buffers. Below is a pretty
21615 nonsensical configuration with 5 windows; two for the group buffer and
21616 three for the article buffer. (I said it was nonsensical.) If you
21617 @code{eval} the statement below, you can get an idea of how that would
21618 look straight away, without going through the normal Gnus channels.
21619 Play with it until you're satisfied, and then use
21620 @code{gnus-add-configuration} to add your new creation to the buffer
21621 configuration list.
21624 (gnus-configure-frame
21628 (article 0.3 point))
21636 You might want to have several frames as well. No prob---just use the
21637 @code{frame} split:
21640 (gnus-configure-frame
21643 (summary 0.25 point frame-focus)
21645 (vertical ((height . 5) (width . 15)
21646 (user-position . t)
21647 (left . -1) (top . 1))
21652 This split will result in the familiar summary/article window
21653 configuration in the first (or ``main'') frame, while a small additional
21654 frame will be created where picons will be shown. As you can see,
21655 instead of the normal @code{1.0} top-level spec, each additional split
21656 should have a frame parameter alist as the size spec.
21657 @xref{Frame Parameters, , Frame Parameters, elisp, The GNU Emacs Lisp
21658 Reference Manual}. Under XEmacs, a frame property list will be
21659 accepted, too---for instance, @code{(height 5 width 15 left -1 top 1)}
21661 The list of all possible keys for @code{gnus-buffer-configuration} can
21662 be found in its default value.
21664 Note that the @code{message} key is used for both
21665 @code{gnus-group-mail} and @code{gnus-summary-mail-other-window}. If
21666 it is desirable to distinguish between the two, something like this
21670 (message (horizontal 1.0
21671 (vertical 1.0 (message 1.0 point))
21673 (if (buffer-live-p gnus-summary-buffer)
21678 One common desire for a multiple frame split is to have a separate frame
21679 for composing mail and news while leaving the original frame intact. To
21680 accomplish that, something like the following can be done:
21685 (if (not (buffer-live-p gnus-summary-buffer))
21686 (car (cdr (assoc 'group gnus-buffer-configuration)))
21687 (car (cdr (assoc 'summary gnus-buffer-configuration))))
21688 (vertical ((user-position . t) (top . 1) (left . 1)
21689 (name . "Message"))
21690 (message 1.0 point))))
21693 @findex gnus-add-configuration
21694 Since the @code{gnus-buffer-configuration} variable is so long and
21695 complicated, there's a function you can use to ease changing the config
21696 of a single setting: @code{gnus-add-configuration}. If, for instance,
21697 you want to change the @code{article} setting, you could say:
21700 (gnus-add-configuration
21701 '(article (vertical 1.0
21703 (summary .25 point)
21707 You'd typically stick these @code{gnus-add-configuration} calls in your
21708 @file{~/.gnus.el} file or in some startup hook---they should be run after
21709 Gnus has been loaded.
21711 @vindex gnus-always-force-window-configuration
21712 If all windows mentioned in the configuration are already visible, Gnus
21713 won't change the window configuration. If you always want to force the
21714 ``right'' window configuration, you can set
21715 @code{gnus-always-force-window-configuration} to non-@code{nil}.
21717 If you're using tree displays (@pxref{Tree Display}), and the tree
21718 window is displayed vertically next to another window, you may also want
21719 to fiddle with @code{gnus-tree-minimize-window} to avoid having the
21722 @subsection Example Window Configurations
21726 Narrow left hand side occupied by group buffer. Right hand side split
21727 between summary buffer (top one-sixth) and article buffer (bottom).
21742 (gnus-add-configuration
21745 (vertical 25 (group 1.0))
21747 (summary 0.16 point)
21750 (gnus-add-configuration
21753 (vertical 25 (group 1.0))
21754 (vertical 1.0 (summary 1.0 point)))))
21760 @node Faces and Fonts
21761 @section Faces and Fonts
21766 Fiddling with fonts and faces used to be very difficult, but these days
21767 it is very simple. You simply say @kbd{M-x customize-face}, pick out
21768 the face you want to alter, and alter it via the standard Customize
21773 @section Compilation
21774 @cindex compilation
21775 @cindex byte-compilation
21777 @findex gnus-compile
21779 Remember all those line format specification variables?
21780 @code{gnus-summary-line-format}, @code{gnus-group-line-format}, and so
21781 on. Now, Gnus will of course heed whatever these variables are, but,
21782 unfortunately, changing them will mean a quite significant slow-down.
21783 (The default values of these variables have byte-compiled functions
21784 associated with them, while the user-generated versions do not, of
21787 To help with this, you can run @kbd{M-x gnus-compile} after you've
21788 fiddled around with the variables and feel that you're (kind of)
21789 satisfied. This will result in the new specs being byte-compiled, and
21790 you'll get top speed again. Gnus will save these compiled specs in the
21791 @file{.newsrc.eld} file. (User-defined functions aren't compiled by
21792 this function, though---you should compile them yourself by sticking
21793 them into the @file{~/.gnus.el} file and byte-compiling that file.)
21797 @section Mode Lines
21800 @vindex gnus-updated-mode-lines
21801 @code{gnus-updated-mode-lines} says what buffers should keep their mode
21802 lines updated. It is a list of symbols. Supported symbols include
21803 @code{group}, @code{article}, @code{summary}, @code{server},
21804 @code{browse}, and @code{tree}. If the corresponding symbol is present,
21805 Gnus will keep that mode line updated with information that may be
21806 pertinent. If this variable is @code{nil}, screen refresh may be
21809 @cindex display-time
21811 @vindex gnus-mode-non-string-length
21812 By default, Gnus displays information on the current article in the mode
21813 lines of the summary and article buffers. The information Gnus wishes
21814 to display (e.g. the subject of the article) is often longer than the
21815 mode lines, and therefore have to be cut off at some point. The
21816 @code{gnus-mode-non-string-length} variable says how long the other
21817 elements on the line is (i.e., the non-info part). If you put
21818 additional elements on the mode line (e.g. a clock), you should modify
21821 @c Hook written by Francesco Potorti` <pot@cnuce.cnr.it>
21823 (add-hook 'display-time-hook
21824 (lambda () (setq gnus-mode-non-string-length
21826 (if line-number-mode 5 0)
21827 (if column-number-mode 4 0)
21828 (length display-time-string)))))
21831 If this variable is @code{nil} (which is the default), the mode line
21832 strings won't be chopped off, and they won't be padded either. Note
21833 that the default is unlikely to be desirable, as even the percentage
21834 complete in the buffer may be crowded off the mode line; the user should
21835 configure this variable appropriately for her configuration.
21838 @node Highlighting and Menus
21839 @section Highlighting and Menus
21841 @cindex highlighting
21844 @vindex gnus-visual
21845 The @code{gnus-visual} variable controls most of the Gnus-prettifying
21846 aspects. If @code{nil}, Gnus won't attempt to create menus or use fancy
21847 colors or fonts. This will also inhibit loading the @file{gnus-vis.el}
21850 This variable can be a list of visual properties that are enabled. The
21851 following elements are valid, and are all included by default:
21854 @item group-highlight
21855 Do highlights in the group buffer.
21856 @item summary-highlight
21857 Do highlights in the summary buffer.
21858 @item article-highlight
21859 Do highlights in the article buffer.
21861 Turn on highlighting in all buffers.
21863 Create menus in the group buffer.
21865 Create menus in the summary buffers.
21867 Create menus in the article buffer.
21869 Create menus in the browse buffer.
21871 Create menus in the server buffer.
21873 Create menus in the score buffers.
21875 Create menus in all buffers.
21878 So if you only want highlighting in the article buffer and menus in all
21879 buffers, you could say something like:
21882 (setq gnus-visual '(article-highlight menu))
21885 If you want highlighting only and no menus whatsoever, you'd say:
21888 (setq gnus-visual '(highlight))
21891 If @code{gnus-visual} is @code{t}, highlighting and menus will be used
21892 in all Gnus buffers.
21894 Other general variables that influence the look of all buffers include:
21897 @item gnus-mouse-face
21898 @vindex gnus-mouse-face
21899 This is the face (i.e., font) used for mouse highlighting in Gnus. No
21900 mouse highlights will be done if @code{gnus-visual} is @code{nil}.
21904 There are hooks associated with the creation of all the different menus:
21908 @item gnus-article-menu-hook
21909 @vindex gnus-article-menu-hook
21910 Hook called after creating the article mode menu.
21912 @item gnus-group-menu-hook
21913 @vindex gnus-group-menu-hook
21914 Hook called after creating the group mode menu.
21916 @item gnus-summary-menu-hook
21917 @vindex gnus-summary-menu-hook
21918 Hook called after creating the summary mode menu.
21920 @item gnus-server-menu-hook
21921 @vindex gnus-server-menu-hook
21922 Hook called after creating the server mode menu.
21924 @item gnus-browse-menu-hook
21925 @vindex gnus-browse-menu-hook
21926 Hook called after creating the browse mode menu.
21928 @item gnus-score-menu-hook
21929 @vindex gnus-score-menu-hook
21930 Hook called after creating the score mode menu.
21941 Those new-fangled @dfn{mouse} contraptions is very popular with the
21942 young, hep kids who don't want to learn the proper way to do things
21943 these days. Why, I remember way back in the summer of '89, when I was
21944 using Emacs on a Tops 20 system. Three hundred users on one single
21945 machine, and every user was running Simula compilers. Bah!
21949 @vindex gnus-carpal
21950 Well, you can make Gnus display bufferfuls of buttons you can click to
21951 do anything by setting @code{gnus-carpal} to @code{t}. Pretty simple,
21952 really. Tell the chiropractor I sent you.
21957 @item gnus-carpal-mode-hook
21958 @vindex gnus-carpal-mode-hook
21959 Hook run in all carpal mode buffers.
21961 @item gnus-carpal-button-face
21962 @vindex gnus-carpal-button-face
21963 Face used on buttons.
21965 @item gnus-carpal-header-face
21966 @vindex gnus-carpal-header-face
21967 Face used on carpal buffer headers.
21969 @item gnus-carpal-group-buffer-buttons
21970 @vindex gnus-carpal-group-buffer-buttons
21971 Buttons in the group buffer.
21973 @item gnus-carpal-summary-buffer-buttons
21974 @vindex gnus-carpal-summary-buffer-buttons
21975 Buttons in the summary buffer.
21977 @item gnus-carpal-server-buffer-buttons
21978 @vindex gnus-carpal-server-buffer-buttons
21979 Buttons in the server buffer.
21981 @item gnus-carpal-browse-buffer-buttons
21982 @vindex gnus-carpal-browse-buffer-buttons
21983 Buttons in the browse buffer.
21986 All the @code{buttons} variables are lists. The elements in these list
21987 are either cons cells where the @code{car} contains a text to be displayed and
21988 the @code{cdr} contains a function symbol, or a simple string.
21996 Gnus, being larger than any program ever written (allegedly), does lots
21997 of strange stuff that you may wish to have done while you're not
21998 present. For instance, you may want it to check for new mail once in a
21999 while. Or you may want it to close down all connections to all servers
22000 when you leave Emacs idle. And stuff like that.
22002 Gnus will let you do stuff like that by defining various
22003 @dfn{handlers}. Each handler consists of three elements: A
22004 @var{function}, a @var{time}, and an @var{idle} parameter.
22006 Here's an example of a handler that closes connections when Emacs has
22007 been idle for thirty minutes:
22010 (gnus-demon-close-connections nil 30)
22013 Here's a handler that scans for @acronym{PGP} headers every hour when
22017 (gnus-demon-scan-pgp 60 t)
22020 This @var{time} parameter and that @var{idle} parameter work together
22021 in a strange, but wonderful fashion. Basically, if @var{idle} is
22022 @code{nil}, then the function will be called every @var{time} minutes.
22024 If @var{idle} is @code{t}, then the function will be called after
22025 @var{time} minutes only if Emacs is idle. So if Emacs is never idle,
22026 the function will never be called. But once Emacs goes idle, the
22027 function will be called every @var{time} minutes.
22029 If @var{idle} is a number and @var{time} is a number, the function will
22030 be called every @var{time} minutes only when Emacs has been idle for
22031 @var{idle} minutes.
22033 If @var{idle} is a number and @var{time} is @code{nil}, the function
22034 will be called once every time Emacs has been idle for @var{idle}
22037 And if @var{time} is a string, it should look like @samp{07:31}, and
22038 the function will then be called once every day somewhere near that
22039 time. Modified by the @var{idle} parameter, of course.
22041 @vindex gnus-demon-timestep
22042 (When I say ``minute'' here, I really mean @code{gnus-demon-timestep}
22043 seconds. This is 60 by default. If you change that variable,
22044 all the timings in the handlers will be affected.)
22046 So, if you want to add a handler, you could put something like this in
22047 your @file{~/.gnus.el} file:
22049 @findex gnus-demon-add-handler
22051 (gnus-demon-add-handler 'gnus-demon-close-connections 30 t)
22054 @findex gnus-demon-add-nocem
22055 @findex gnus-demon-add-scanmail
22056 @findex gnus-demon-add-rescan
22057 @findex gnus-demon-add-scan-timestamps
22058 @findex gnus-demon-add-disconnection
22059 Some ready-made functions to do this have been created:
22060 @code{gnus-demon-add-nocem}, @code{gnus-demon-add-disconnection},
22061 @code{gnus-demon-add-nntp-close-connection},
22062 @code{gnus-demon-add-scan-timestamps}, @code{gnus-demon-add-rescan}, and
22063 @code{gnus-demon-add-scanmail}. Just put those functions in your
22064 @file{~/.gnus.el} if you want those abilities.
22066 @findex gnus-demon-init
22067 @findex gnus-demon-cancel
22068 @vindex gnus-demon-handlers
22069 If you add handlers to @code{gnus-demon-handlers} directly, you should
22070 run @code{gnus-demon-init} to make the changes take hold. To cancel all
22071 daemons, you can use the @code{gnus-demon-cancel} function.
22073 Note that adding daemons can be pretty naughty if you over do it. Adding
22074 functions that scan all news and mail from all servers every two seconds
22075 is a sure-fire way of getting booted off any respectable system. So
22084 @dfn{Spamming} is posting the same article lots and lots of times.
22085 Spamming is bad. Spamming is evil.
22087 Spamming is usually canceled within a day or so by various anti-spamming
22088 agencies. These agencies usually also send out @dfn{NoCeM} messages.
22089 NoCeM is pronounced ``no see-'em'', and means what the name
22090 implies---these are messages that make the offending articles, like, go
22093 What use are these NoCeM messages if the articles are canceled anyway?
22094 Some sites do not honor cancel messages and some sites just honor cancels
22095 from a select few people. Then you may wish to make use of the NoCeM
22096 messages, which are distributed in the @samp{alt.nocem.misc} newsgroup.
22098 Gnus can read and parse the messages in this group automatically, and
22099 this will make spam disappear.
22101 There are some variables to customize, of course:
22104 @item gnus-use-nocem
22105 @vindex gnus-use-nocem
22106 Set this variable to @code{t} to set the ball rolling. It is @code{nil}
22109 @item gnus-nocem-groups
22110 @vindex gnus-nocem-groups
22111 Gnus will look for NoCeM messages in the groups in this list. The
22114 ("news.lists.filters" "news.admin.net-abuse.bulletins"
22115 "alt.nocem.misc" "news.admin.net-abuse.announce")
22118 @item gnus-nocem-issuers
22119 @vindex gnus-nocem-issuers
22120 There are many people issuing NoCeM messages. This list says what
22121 people you want to listen to. The default is
22123 ("Automoose-1" "clewis@@ferret.ocunix.on.ca"
22124 "cosmo.roadkill" "SpamHippo" "hweede@@snafu.de")
22126 fine, upstanding citizens all of them.
22128 Known despammers that you can put in this list are listed at@*
22129 @uref{http://www.xs4all.nl/~rosalind/nocemreg/nocemreg.html}.
22131 You do not have to heed NoCeM messages from all these people---just the
22132 ones you want to listen to. You also don't have to accept all NoCeM
22133 messages from the people you like. Each NoCeM message has a @dfn{type}
22134 header that gives the message a (more or less, usually less) rigorous
22135 definition. Common types are @samp{spam}, @samp{spew}, @samp{mmf},
22136 @samp{binary}, and @samp{troll}. To specify this, you have to use
22137 @code{(@var{issuer} @var{conditions} @dots{})} elements in the list.
22138 Each condition is either a string (which is a regexp that matches types
22139 you want to use) or a list on the form @code{(not @var{string})}, where
22140 @var{string} is a regexp that matches types you don't want to use.
22142 For instance, if you want all NoCeM messages from Chris Lewis except his
22143 @samp{troll} messages, you'd say:
22146 ("clewis@@ferret.ocunix.on.ca" ".*" (not "troll"))
22149 On the other hand, if you just want nothing but his @samp{spam} and
22150 @samp{spew} messages, you'd say:
22153 ("clewis@@ferret.ocunix.on.ca" (not ".*") "spew" "spam")
22156 The specs are applied left-to-right.
22159 @item gnus-nocem-verifyer
22160 @vindex gnus-nocem-verifyer
22162 This should be a function for verifying that the NoCeM issuer is who she
22163 says she is. The default is @code{pgg-verify}, which returns
22164 non-@code{nil} if the verification is successful, otherwise (including
22165 the case the NoCeM message was not signed) returns @code{nil}. If this
22166 is too slow and you don't care for verification (which may be dangerous),
22167 you can set this variable to @code{nil}.
22169 Formerly the default was @code{mc-verify}, which is a Mailcrypt
22170 function. While you can still use it, you can change it into
22171 @code{pgg-verify} running with GnuPG if you are willing to add the
22172 @acronym{PGP} public keys to GnuPG's keyring.
22174 @item gnus-nocem-directory
22175 @vindex gnus-nocem-directory
22176 This is where Gnus will store its NoCeM cache files. The default is@*
22177 @file{~/News/NoCeM/}.
22179 @item gnus-nocem-expiry-wait
22180 @vindex gnus-nocem-expiry-wait
22181 The number of days before removing old NoCeM entries from the cache.
22182 The default is 15. If you make it shorter Gnus will be faster, but you
22183 might then see old spam.
22185 @item gnus-nocem-check-from
22186 @vindex gnus-nocem-check-from
22187 Non-@code{nil} means check for valid issuers in message bodies.
22188 Otherwise don't bother fetching articles unless their author matches a
22189 valid issuer; that is much faster if you are selective about the
22192 @item gnus-nocem-check-article-limit
22193 @vindex gnus-nocem-check-article-limit
22194 If non-@code{nil}, the maximum number of articles to check in any NoCeM
22195 group. NoCeM groups can be huge and very slow to process.
22199 Using NoCeM could potentially be a memory hog. If you have many living
22200 (i. e., subscribed or unsubscribed groups), your Emacs process will grow
22201 big. If this is a problem, you should kill off all (or most) of your
22202 unsubscribed groups (@pxref{Subscription Commands}).
22209 It is very useful to be able to undo actions one has done. In normal
22210 Emacs buffers, it's easy enough---you just push the @code{undo} button.
22211 In Gnus buffers, however, it isn't that simple.
22213 The things Gnus displays in its buffer is of no value whatsoever to
22214 Gnus---it's all just data designed to look nice to the user.
22215 Killing a group in the group buffer with @kbd{C-k} makes the line
22216 disappear, but that's just a side-effect of the real action---the
22217 removal of the group in question from the internal Gnus structures.
22218 Undoing something like that can't be done by the normal Emacs
22219 @code{undo} function.
22221 Gnus tries to remedy this somewhat by keeping track of what the user
22222 does and coming up with actions that would reverse the actions the user
22223 takes. When the user then presses the @code{undo} key, Gnus will run
22224 the code to reverse the previous action, or the previous actions.
22225 However, not all actions are easily reversible, so Gnus currently offers
22226 a few key functions to be undoable. These include killing groups,
22227 yanking groups, and changing the list of read articles of groups.
22228 That's it, really. More functions may be added in the future, but each
22229 added function means an increase in data to be stored, so Gnus will
22230 never be totally undoable.
22232 @findex gnus-undo-mode
22233 @vindex gnus-use-undo
22235 The undoability is provided by the @code{gnus-undo-mode} minor mode. It
22236 is used if @code{gnus-use-undo} is non-@code{nil}, which is the
22237 default. The @kbd{C-M-_} key performs the @code{gnus-undo}
22238 command, which should feel kinda like the normal Emacs @code{undo}
22242 @node Predicate Specifiers
22243 @section Predicate Specifiers
22244 @cindex predicate specifiers
22246 Some Gnus variables are @dfn{predicate specifiers}. This is a special
22247 form that allows flexible specification of predicates without having
22248 to type all that much.
22250 These specifiers are lists consisting of functions, symbols and lists.
22255 (or gnus-article-unseen-p
22256 gnus-article-unread-p)
22259 The available symbols are @code{or}, @code{and} and @code{not}. The
22260 functions all take one parameter.
22262 @findex gnus-make-predicate
22263 Internally, Gnus calls @code{gnus-make-predicate} on these specifiers
22264 to create a function that can be called. This input parameter to this
22265 function will be passed along to all the functions in the predicate
22270 @section Moderation
22273 If you are a moderator, you can use the @file{gnus-mdrtn.el} package.
22274 It is not included in the standard Gnus package. Write a mail to
22275 @samp{larsi@@gnus.org} and state what group you moderate, and you'll
22278 The moderation package is implemented as a minor mode for summary
22282 (add-hook 'gnus-summary-mode-hook 'gnus-moderate)
22285 in your @file{~/.gnus.el} file.
22287 If you are the moderator of @samp{rec.zoofle}, this is how it's
22292 You split your incoming mail by matching on
22293 @samp{Newsgroups:.*rec.zoofle}, which will put all the to-be-posted
22294 articles in some mail group---for instance, @samp{nnml:rec.zoofle}.
22297 You enter that group once in a while and post articles using the @kbd{e}
22298 (edit-and-post) or @kbd{s} (just send unedited) commands.
22301 If, while reading the @samp{rec.zoofle} newsgroup, you happen upon some
22302 articles that weren't approved by you, you can cancel them with the
22306 To use moderation mode in these two groups, say:
22309 (setq gnus-moderated-list
22310 "^nnml:rec.zoofle$\\|^rec.zoofle$")
22314 @node Fetching a Group
22315 @section Fetching a Group
22316 @cindex fetching a group
22318 @findex gnus-fetch-group
22319 It is sometimes convenient to be able to just say ``I want to read this
22320 group and I don't care whether Gnus has been started or not''. This is
22321 perhaps more useful for people who write code than for users, but the
22322 command @code{gnus-fetch-group} provides this functionality in any case.
22323 It takes the group name as a parameter.
22326 @node Image Enhancements
22327 @section Image Enhancements
22329 XEmacs, as well as Emacs 21@footnote{Emacs 21 on MS Windows doesn't
22330 support images yet.}, is able to display pictures and stuff, so Gnus has
22331 taken advantage of that.
22334 * X-Face:: Display a funky, teensy black-and-white image.
22335 * Face:: Display a funkier, teensier colored image.
22336 * Smileys:: Show all those happy faces the way they were meant to be shown.
22337 * Picons:: How to display pictures of what you're reading.
22338 * XVarious:: Other XEmacsy Gnusey variables.
22346 @code{X-Face} headers describe a 48x48 pixel black-and-white (1 bit
22347 depth) image that's supposed to represent the author of the message.
22348 It seems to be supported by an ever-growing number of mail and news
22352 @findex gnus-article-display-x-face
22353 @vindex gnus-article-x-face-command
22354 @vindex gnus-article-x-face-too-ugly
22362 Decoding an @code{X-Face} header either requires an Emacs that has
22363 @samp{compface} support (which most XEmacs versions has), or that you
22364 have @samp{compface} installed on your system. If either is true,
22365 Gnus will default to displaying @code{X-Face} headers.
22367 The variable that controls this is the
22368 @code{gnus-article-x-face-command} variable. If this variable is a
22369 string, this string will be executed in a sub-shell. If it is a
22370 function, this function will be called with the face as the argument.
22371 If the @code{gnus-article-x-face-too-ugly} (which is a regexp) matches
22372 the @code{From} header, the face will not be shown.
22374 The default action under Emacs 20 is to fork off the @code{display}
22375 program@footnote{@code{display} is from the ImageMagick package. For
22376 the @code{uncompface} and @code{icontopbm} programs look for a package
22377 like @code{compface} or @code{faces-xface} on a GNU/Linux system.} to
22380 Under XEmacs or Emacs 21+ with suitable image support, the default
22381 action is to display the face before the @code{From} header. (It's
22382 nicer if XEmacs has been compiled with @code{X-Face} support---that
22383 will make display somewhat faster. If there's no native @code{X-Face}
22384 support, Gnus will try to convert the @code{X-Face} header using
22385 external programs from the @code{pbmplus} package and
22386 friends.@footnote{On a GNU/Linux system look for packages with names
22387 like @code{netpbm}, @code{libgr-progs} and @code{compface}.})
22389 (Note: @code{x-face} is used in the variable/function names, not
22397 @vindex gnus-x-face
22398 Face to show X-Face. The colors from this face are used as the
22399 foreground and background colors of the displayed X-Faces. The
22400 default colors are black and white.
22402 @item gnus-face-properties-alist
22403 @vindex gnus-face-properties-alist
22404 Alist of image types and properties applied to Face (@pxref{Face}) and
22405 X-Face images. The default value is @code{((pbm . (:face gnus-x-face))
22406 (png . nil))} for Emacs or @code{((xface . (:face gnus-x-face)))} for
22407 XEmacs. Here are examples:
22410 ;; Specify the altitude of Face and X-Face images in the From header.
22411 (setq gnus-face-properties-alist
22412 '((pbm . (:face gnus-x-face :ascent 80))
22413 (png . (:ascent 80))))
22415 ;; Show Face and X-Face images as pressed buttons.
22416 (setq gnus-face-properties-alist
22417 '((pbm . (:face gnus-x-face :relief -2))
22418 (png . (:relief -2))))
22421 @pxref{Image Descriptors, ,Image Descriptors, elisp, The Emacs Lisp
22422 Reference Manual} for the valid properties for various image types.
22423 Currently, @code{pbm} is used for X-Face images and @code{png} is used
22424 for Face images in Emacs. Only the @code{:face} property is effective
22425 on the @code{xface} image type in XEmacs if it is built with the
22426 @samp{libcompface} library.
22429 Gnus provides a few convenience functions and variables to allow
22430 easier insertion of X-Face headers in outgoing messages.
22432 @findex gnus-random-x-face
22433 @vindex gnus-convert-pbm-to-x-face-command
22434 @vindex gnus-x-face-directory
22435 @code{gnus-random-x-face} goes through all the @samp{pbm} files in
22436 @code{gnus-x-face-directory} and picks one at random, and then
22437 converts it to the X-Face format by using the
22438 @code{gnus-convert-pbm-to-x-face-command} shell command. The
22439 @samp{pbm} files should be 48x48 pixels big. It returns the X-Face
22440 header data as a string.
22442 @findex gnus-insert-random-x-face-header
22443 @code{gnus-insert-random-x-face-header} calls
22444 @code{gnus-random-x-face} and inserts a @samp{X-Face} header with the
22445 randomly generated data.
22447 @findex gnus-x-face-from-file
22448 @vindex gnus-convert-image-to-x-face-command
22449 @code{gnus-x-face-from-file} takes a GIF file as the parameter, and then
22450 converts the file to X-Face format by using the
22451 @code{gnus-convert-image-to-x-face-command} shell command.
22453 Here's how you would typically use the first function. Put something
22454 like the following in your @file{~/.gnus.el} file:
22457 (setq message-required-news-headers
22458 (nconc message-required-news-headers
22459 (list '(X-Face . gnus-random-x-face))))
22462 Using the last function would be something like this:
22465 (setq message-required-news-headers
22466 (nconc message-required-news-headers
22467 (list '(X-Face . (lambda ()
22468 (gnus-x-face-from-file
22469 "~/My-face.gif"))))))
22477 @c #### FIXME: faces and x-faces'implementations should really be harmonized.
22479 @code{Face} headers are essentially a funkier version of @code{X-Face}
22480 ones. They describe a 48x48 pixel colored image that's supposed to
22481 represent the author of the message.
22484 @findex gnus-article-display-face
22485 The contents of a @code{Face} header must be a base64 encoded PNG image.
22486 See @uref{http://quimby.gnus.org/circus/face/} for the precise
22489 The @code{gnus-face-properties-alist} variable affects the appearance of
22490 displayed Face images. @xref{X-Face}.
22492 Gnus provides a few convenience functions and variables to allow
22493 easier insertion of Face headers in outgoing messages.
22495 @findex gnus-convert-png-to-face
22496 @code{gnus-convert-png-to-face} takes a 48x48 PNG image, no longer than
22497 726 bytes long, and converts it to a face.
22499 @findex gnus-face-from-file
22500 @vindex gnus-convert-image-to-face-command
22501 @code{gnus-face-from-file} takes a JPEG file as the parameter, and then
22502 converts the file to Face format by using the
22503 @code{gnus-convert-image-to-face-command} shell command.
22505 Here's how you would typically use this function. Put something like the
22506 following in your @file{~/.gnus.el} file:
22509 (setq message-required-news-headers
22510 (nconc message-required-news-headers
22511 (list '(Face . (lambda ()
22512 (gnus-face-from-file "~/face.jpg"))))))
22517 @subsection Smileys
22522 \gnusfig{-3cm}{0.5cm}{\epsfig{figure=ps/BigFace,height=20cm}}
22527 @dfn{Smiley} is a package separate from Gnus, but since Gnus is
22528 currently the only package that uses Smiley, it is documented here.
22530 In short---to use Smiley in Gnus, put the following in your
22531 @file{~/.gnus.el} file:
22534 (setq gnus-treat-display-smileys t)
22537 Smiley maps text smiley faces---@samp{:-)}, @samp{8-)}, @samp{:-(} and
22538 the like---to pictures and displays those instead of the text smiley
22539 faces. The conversion is controlled by a list of regexps that matches
22540 text and maps that to file names.
22542 @vindex smiley-regexp-alist
22543 The alist used is specified by the @code{smiley-regexp-alist}
22544 variable. The first item in each element is the regexp to be matched;
22545 the second element is the regexp match group that is to be replaced by
22546 the picture; and the third element is the name of the file to be
22549 The following variables customize where Smiley will look for these
22554 @item smiley-data-directory
22555 @vindex smiley-data-directory
22556 Where Smiley will look for smiley faces files.
22558 @item gnus-smiley-file-types
22559 @vindex gnus-smiley-file-types
22560 List of suffixes on smiley file names to try.
22574 So@dots{} You want to slow down your news reader even more! This is a
22575 good way to do so. It's also a great way to impress people staring
22576 over your shoulder as you read news.
22578 What are Picons? To quote directly from the Picons Web site:
22587 @dfn{Picons} is short for ``personal icons''. They're small,
22588 constrained images used to represent users and domains on the net,
22589 organized into databases so that the appropriate image for a given
22590 e-mail address can be found. Besides users and domains, there are picon
22591 databases for Usenet newsgroups and weather forecasts. The picons are
22592 in either monochrome @code{XBM} format or color @code{XPM} and
22593 @code{GIF} formats.
22596 @vindex gnus-picon-databases
22597 For instructions on obtaining and installing the picons databases,
22598 point your Web browser at
22599 @uref{http://www.cs.indiana.edu/picons/ftp/index.html}.
22601 If you are using Debian GNU/Linux, saying @samp{apt-get install
22602 picons.*} will install the picons where Gnus can find them.
22604 To enable displaying picons, simply make sure that
22605 @code{gnus-picon-databases} points to the directory containing the
22608 @vindex gnus-picon-style
22609 The variable @code{gnus-picon-style} controls how picons are displayed.
22610 If @code{inline}, the textual representation is replaced. If
22611 @code{right}, picons are added right to the textual representation.
22613 The following variables offer control over where things are located.
22617 @item gnus-picon-databases
22618 @vindex gnus-picon-databases
22619 The location of the picons database. This is a list of directories
22620 containing the @file{news}, @file{domains}, @file{users} (and so on)
22621 subdirectories. Defaults to @code{("/usr/lib/picon"
22622 "/usr/local/faces")}.
22624 @item gnus-picon-news-directories
22625 @vindex gnus-picon-news-directories
22626 List of subdirectories to search in @code{gnus-picon-databases} for
22627 newsgroups faces. @code{("news")} is the default.
22629 @item gnus-picon-user-directories
22630 @vindex gnus-picon-user-directories
22631 List of subdirectories to search in @code{gnus-picon-databases} for user
22632 faces. @code{("users" "usenix" "local" "misc")} is the default.
22634 @item gnus-picon-domain-directories
22635 @vindex gnus-picon-domain-directories
22636 List of subdirectories to search in @code{gnus-picon-databases} for
22637 domain name faces. Defaults to @code{("domains")}. Some people may
22638 want to add @samp{"unknown"} to this list.
22640 @item gnus-picon-file-types
22641 @vindex gnus-picon-file-types
22642 Ordered list of suffixes on picon file names to try. Defaults to
22643 @code{("xpm" "gif" "xbm")} minus those not built-in your Emacs.
22649 @subsection Various XEmacs Variables
22652 @item gnus-xmas-glyph-directory
22653 @vindex gnus-xmas-glyph-directory
22654 This is where Gnus will look for pictures. Gnus will normally
22655 auto-detect this directory, but you may set it manually if you have an
22656 unusual directory structure.
22658 @item gnus-xmas-logo-color-alist
22659 @vindex gnus-xmas-logo-color-alist
22660 This is an alist where the key is a type symbol and the values are the
22661 foreground and background color of the splash page glyph.
22663 @item gnus-xmas-logo-color-style
22664 @vindex gnus-xmas-logo-color-style
22665 This is the key used to look up the color in the alist described above.
22666 Valid values include @code{flame}, @code{pine}, @code{moss},
22667 @code{irish}, @code{sky}, @code{tin}, @code{velvet}, @code{grape},
22668 @code{labia}, @code{berry}, @code{neutral}, and @code{september}.
22670 @item gnus-xmas-modeline-glyph
22671 @vindex gnus-xmas-modeline-glyph
22672 A glyph displayed in all Gnus mode lines. It is a tiny gnu head by
22677 @subsubsection Toolbar
22681 @item gnus-use-toolbar
22682 @vindex gnus-use-toolbar
22683 If @code{nil}, don't display toolbars. If non-@code{nil}, it should be
22684 one of @code{default-toolbar}, @code{top-toolbar}, @code{bottom-toolbar},
22685 @code{right-toolbar}, or @code{left-toolbar}.
22687 @item gnus-group-toolbar
22688 @vindex gnus-group-toolbar
22689 The toolbar in the group buffer.
22691 @item gnus-summary-toolbar
22692 @vindex gnus-summary-toolbar
22693 The toolbar in the summary buffer.
22695 @item gnus-summary-mail-toolbar
22696 @vindex gnus-summary-mail-toolbar
22697 The toolbar in the summary buffer of mail groups.
22708 @node Fuzzy Matching
22709 @section Fuzzy Matching
22710 @cindex fuzzy matching
22712 Gnus provides @dfn{fuzzy matching} of @code{Subject} lines when doing
22713 things like scoring, thread gathering and thread comparison.
22715 As opposed to regular expression matching, fuzzy matching is very fuzzy.
22716 It's so fuzzy that there's not even a definition of what @dfn{fuzziness}
22717 means, and the implementation has changed over time.
22719 Basically, it tries to remove all noise from lines before comparing.
22720 @samp{Re: }, parenthetical remarks, white space, and so on, are filtered
22721 out of the strings before comparing the results. This often leads to
22722 adequate results---even when faced with strings generated by text
22723 manglers masquerading as newsreaders.
22726 @node Thwarting Email Spam
22727 @section Thwarting Email Spam
22731 @cindex unsolicited commercial email
22733 In these last days of the Usenet, commercial vultures are hanging about
22734 and grepping through news like crazy to find email addresses they can
22735 foist off their scams and products to. As a reaction to this, many
22736 people have started putting nonsense addresses into their @code{From}
22737 lines. I think this is counterproductive---it makes it difficult for
22738 people to send you legitimate mail in response to things you write, as
22739 well as making it difficult to see who wrote what. This rewriting may
22740 perhaps be a bigger menace than the unsolicited commercial email itself
22743 The biggest problem I have with email spam is that it comes in under
22744 false pretenses. I press @kbd{g} and Gnus merrily informs me that I
22745 have 10 new emails. I say ``Golly gee! Happy is me!'' and select the
22746 mail group, only to find two pyramid schemes, seven advertisements
22747 (``New! Miracle tonic for growing full, lustrous hair on your toes!'')
22748 and one mail asking me to repent and find some god.
22750 This is annoying. Here's what you can do about it.
22753 * The problem of spam:: Some background, and some solutions
22754 * Anti-Spam Basics:: Simple steps to reduce the amount of spam.
22755 * SpamAssassin:: How to use external anti-spam tools.
22756 * Hashcash:: Reduce spam by burning CPU time.
22757 * Filtering Spam Using The Spam ELisp Package::
22758 * Filtering Spam Using Statistics with spam-stat::
22761 @node The problem of spam
22762 @subsection The problem of spam
22764 @cindex spam filtering approaches
22765 @cindex filtering approaches, spam
22767 @cindex unsolicited commercial email
22769 First, some background on spam.
22771 If you have access to e-mail, you are familiar with spam (technically
22772 termed @acronym{UCE}, Unsolicited Commercial E-mail). Simply put, it
22773 exists because e-mail delivery is very cheap compared to paper mail,
22774 so only a very small percentage of people need to respond to an UCE to
22775 make it worthwhile to the advertiser. Ironically, one of the most
22776 common spams is the one offering a database of e-mail addresses for
22777 further spamming. Senders of spam are usually called @emph{spammers},
22778 but terms like @emph{vermin}, @emph{scum}, @emph{sociopaths}, and
22779 @emph{morons} are in common use as well.
22781 Spam comes from a wide variety of sources. It is simply impossible to
22782 dispose of all spam without discarding useful messages. A good
22783 example is the TMDA system, which requires senders
22784 unknown to you to confirm themselves as legitimate senders before
22785 their e-mail can reach you. Without getting into the technical side
22786 of TMDA, a downside is clearly that e-mail from legitimate sources may
22787 be discarded if those sources can't or won't confirm themselves
22788 through the TMDA system. Another problem with TMDA is that it
22789 requires its users to have a basic understanding of e-mail delivery
22792 The simplest approach to filtering spam is filtering, at the mail
22793 server or when you sort through incoming mail. If you get 200 spam
22794 messages per day from @samp{random-address@@vmadmin.com}, you block
22795 @samp{vmadmin.com}. If you get 200 messages about @samp{VIAGRA}, you
22796 discard all messages with @samp{VIAGRA} in the message. If you get
22797 lots of spam from Bulgaria, for example, you try to filter all mail
22798 from Bulgarian IPs.
22800 This, unfortunately, is a great way to discard legitimate e-mail. The
22801 risks of blocking a whole country (Bulgaria, Norway, Nigeria, China,
22802 etc.) or even a continent (Asia, Africa, Europe, etc.) from contacting
22803 you should be obvious, so don't do it if you have the choice.
22805 In another instance, the very informative and useful RISKS digest has
22806 been blocked by overzealous mail filters because it @strong{contained}
22807 words that were common in spam messages. Nevertheless, in isolated
22808 cases, with great care, direct filtering of mail can be useful.
22810 Another approach to filtering e-mail is the distributed spam
22811 processing, for instance DCC implements such a system. In essence,
22812 @var{N} systems around the world agree that a machine @var{X} in
22813 Ghana, Estonia, or California is sending out spam e-mail, and these
22814 @var{N} systems enter @var{X} or the spam e-mail from @var{X} into a
22815 database. The criteria for spam detection vary---it may be the number
22816 of messages sent, the content of the messages, and so on. When a user
22817 of the distributed processing system wants to find out if a message is
22818 spam, he consults one of those @var{N} systems.
22820 Distributed spam processing works very well against spammers that send
22821 a large number of messages at once, but it requires the user to set up
22822 fairly complicated checks. There are commercial and free distributed
22823 spam processing systems. Distributed spam processing has its risks as
22824 well. For instance legitimate e-mail senders have been accused of
22825 sending spam, and their web sites and mailing lists have been shut
22826 down for some time because of the incident.
22828 The statistical approach to spam filtering is also popular. It is
22829 based on a statistical analysis of previous spam messages. Usually
22830 the analysis is a simple word frequency count, with perhaps pairs of
22831 words or 3-word combinations thrown into the mix. Statistical
22832 analysis of spam works very well in most of the cases, but it can
22833 classify legitimate e-mail as spam in some cases. It takes time to
22834 run the analysis, the full message must be analyzed, and the user has
22835 to store the database of spam analyses. Statistical analysis on the
22836 server is gaining popularity. This has the advantage of letting the
22837 user Just Read Mail, but has the disadvantage that it's harder to tell
22838 the server that it has misclassified mail.
22840 Fighting spam is not easy, no matter what anyone says. There is no
22841 magic switch that will distinguish Viagra ads from Mom's e-mails.
22842 Even people are having a hard time telling spam apart from non-spam,
22843 because spammers are actively looking to fool us into thinking they
22844 are Mom, essentially. Spamming is irritating, irresponsible, and
22845 idiotic behavior from a bunch of people who think the world owes them
22846 a favor. We hope the following sections will help you in fighting the
22849 @node Anti-Spam Basics
22850 @subsection Anti-Spam Basics
22854 @cindex unsolicited commercial email
22856 One way of dealing with spam is having Gnus split out all spam into a
22857 @samp{spam} mail group (@pxref{Splitting Mail}).
22859 First, pick one (1) valid mail address that you can be reached at, and
22860 put it in your @code{From} header of all your news articles. (I've
22861 chosen @samp{larsi@@trym.ifi.uio.no}, but for many addresses on the form
22862 @samp{larsi+usenet@@ifi.uio.no} will be a better choice. Ask your
22863 sysadmin whether your sendmail installation accepts keywords in the local
22864 part of the mail address.)
22867 (setq message-default-news-headers
22868 "From: Lars Magne Ingebrigtsen <larsi@@trym.ifi.uio.no>\n")
22871 Then put the following split rule in @code{nnmail-split-fancy}
22872 (@pxref{Fancy Mail Splitting}):
22876 (to "larsi@@trym.ifi.uio.no"
22877 (| ("subject" "re:.*" "misc")
22878 ("references" ".*@@.*" "misc")
22883 This says that all mail to this address is suspect, but if it has a
22884 @code{Subject} that starts with a @samp{Re:} or has a @code{References}
22885 header, it's probably ok. All the rest goes to the @samp{spam} group.
22886 (This idea probably comes from Tim Pierce.)
22888 In addition, many mail spammers talk directly to your @acronym{SMTP} server
22889 and do not include your email address explicitly in the @code{To}
22890 header. Why they do this is unknown---perhaps it's to thwart this
22891 thwarting scheme? In any case, this is trivial to deal with---you just
22892 put anything not addressed to you in the @samp{spam} group by ending
22893 your fancy split rule in this way:
22898 (to "larsi" "misc")
22902 In my experience, this will sort virtually everything into the right
22903 group. You still have to check the @samp{spam} group from time to time to
22904 check for legitimate mail, though. If you feel like being a good net
22905 citizen, you can even send off complaints to the proper authorities on
22906 each unsolicited commercial email---at your leisure.
22908 This works for me. It allows people an easy way to contact me (they can
22909 just press @kbd{r} in the usual way), and I'm not bothered at all with
22910 spam. It's a win-win situation. Forging @code{From} headers to point
22911 to non-existent domains is yucky, in my opinion.
22913 Be careful with this approach. Spammers are wise to it.
22917 @subsection SpamAssassin, Vipul's Razor, DCC, etc
22918 @cindex SpamAssassin
22919 @cindex Vipul's Razor
22922 The days where the hints in the previous section were sufficient in
22923 avoiding spam are coming to an end. There are many tools out there
22924 that claim to reduce the amount of spam you get. This section could
22925 easily become outdated fast, as new products replace old, but
22926 fortunately most of these tools seem to have similar interfaces. Even
22927 though this section will use SpamAssassin as an example, it should be
22928 easy to adapt it to most other tools.
22930 Note that this section does not involve the @code{spam.el} package,
22931 which is discussed in the next section. If you don't care for all
22932 the features of @code{spam.el}, you can make do with these simple
22935 If the tool you are using is not installed on the mail server, you
22936 need to invoke it yourself. Ideas on how to use the
22937 @code{:postscript} mail source parameter (@pxref{Mail Source
22938 Specifiers}) follow.
22942 '((file :prescript "formail -bs spamassassin < /var/mail/%u")
22946 "mv %t /tmp/foo; formail -bs spamc < /tmp/foo > %t")))
22949 Once you manage to process your incoming spool somehow, thus making
22950 the mail contain e.g.@: a header indicating it is spam, you are ready to
22951 filter it out. Using normal split methods (@pxref{Splitting Mail}):
22954 (setq nnmail-split-methods '(("spam" "^X-Spam-Flag: YES")
22958 Or using fancy split methods (@pxref{Fancy Mail Splitting}):
22961 (setq nnmail-split-methods 'nnmail-split-fancy
22962 nnmail-split-fancy '(| ("X-Spam-Flag" "YES" "spam")
22966 Some people might not like the idea of piping the mail through various
22967 programs using a @code{:prescript} (if some program is buggy, you
22968 might lose all mail). If you are one of them, another solution is to
22969 call the external tools during splitting. Example fancy split method:
22972 (setq nnmail-split-fancy '(| (: kevin-spamassassin)
22974 (defun kevin-spamassassin ()
22978 (if (eq 1 (call-process-region (point-min) (point-max)
22979 "spamc" nil nil nil "-c"))
22983 Note that with the nnimap back end, message bodies will not be
22984 downloaded by default. You need to set
22985 @code{nnimap-split-download-body} to @code{t} to do that
22986 (@pxref{Splitting in IMAP}).
22988 That is about it. As some spam is likely to get through anyway, you
22989 might want to have a nifty function to call when you happen to read
22990 spam. And here is the nifty function:
22993 (defun my-gnus-raze-spam ()
22994 "Submit SPAM to Vipul's Razor, then mark it as expirable."
22996 (gnus-summary-show-raw-article)
22997 (gnus-summary-save-in-pipe "razor-report -f -d")
22998 (gnus-summary-mark-as-expirable 1))
23002 @subsection Hashcash
23005 A novel technique to fight spam is to require senders to do something
23006 costly and demonstrably unique for each message they send. This has
23007 the obvious drawback that you cannot rely on everyone in the world
23008 using this technique, since it is not part of the Internet standards,
23009 but it may be useful in smaller communities.
23011 While the tools in the previous section work well in practice, they
23012 work only because the tools are constantly maintained and updated as
23013 new form of spam appears. This means that a small percentage of spam
23014 will always get through. It also means that somewhere, someone needs
23015 to read lots of spam to update these tools. Hashcash avoids that, but
23016 instead prefers that everyone you contact through e-mail supports the
23017 scheme. You can view the two approaches as pragmatic vs dogmatic.
23018 The approaches have their own advantages and disadvantages, but as
23019 often in the real world, a combination of them is stronger than either
23020 one of them separately.
23023 The ``something costly'' is to burn CPU time, more specifically to
23024 compute a hash collision up to a certain number of bits. The
23025 resulting hashcash cookie is inserted in a @samp{X-Hashcash:} header.
23026 For more details, and for the external application @code{hashcash} you
23027 need to install to use this feature, see
23028 @uref{http://www.hashcash.org/}. Even more information can be found
23029 at @uref{http://www.camram.org/}.
23031 If you wish to generate hashcash for each message you send, you can
23032 customize @code{message-generate-hashcash} (@pxref{Mail Headers, ,Mail
23033 Headers,message, The Message Manual}), as in:
23036 (setq message-generate-hashcash t)
23039 You will need to set up some additional variables as well:
23043 @item hashcash-default-payment
23044 @vindex hashcash-default-payment
23045 This variable indicates the default number of bits the hash collision
23046 should consist of. By default this is 20. Suggested useful values
23049 @item hashcash-payment-alist
23050 @vindex hashcash-payment-alist
23051 Some receivers may require you to spend burn more CPU time than the
23052 default. This variable contains a list of @samp{(@var{addr}
23053 @var{amount})} cells, where @var{addr} is the receiver (email address
23054 or newsgroup) and @var{amount} is the number of bits in the collision
23055 that is needed. It can also contain @samp{(@var{addr} @var{string}
23056 @var{amount})} cells, where the @var{string} is the string to use
23057 (normally the email address or newsgroup name is used).
23059 @item hashcash-path
23060 @vindex hashcash-path
23061 Where the @code{hashcash} binary is installed. This variable should
23062 be automatically set by @code{executable-find}, but if it's @code{nil}
23063 (usually because the @code{hashcash} binary is not in your path)
23064 you'll get a warning when you check hashcash payments and an error
23065 when you generate hashcash payments.
23069 Gnus can verify hashcash cookies, although this can also be done by
23070 hand customized mail filtering scripts. To verify a hashcash cookie
23071 in a message, use the @code{mail-check-payment} function in the
23072 @code{hashcash.el} library. You can also use the @code{spam.el}
23073 package with the @code{spam-use-hashcash} back end to validate hashcash
23074 cookies in incoming mail and filter mail accordingly (@pxref{Anti-spam
23075 Hashcash Payments}).
23077 @node Filtering Spam Using The Spam ELisp Package
23078 @subsection Filtering Spam Using The Spam ELisp Package
23079 @cindex spam filtering
23082 The idea behind @code{spam.el} is to have a control center for spam detection
23083 and filtering in Gnus. To that end, @code{spam.el} does two things: it
23084 filters new mail, and it analyzes mail known to be spam or ham.
23085 @dfn{Ham} is the name used throughout @code{spam.el} to indicate
23088 Make sure you read the section on the @code{spam.el} sequence of
23089 events. See @xref{Spam ELisp Package Sequence of Events}.
23091 @cindex spam-initialize
23092 To use @code{spam.el}, you @strong{must} run the function
23093 @code{spam-initialize} to autoload @file{spam.el} and to install the
23094 @code{spam.el} hooks. There is one exception: if you use the
23095 @code{spam-use-stat} (@pxref{spam-stat spam filtering}) setting, you
23096 should turn it on before @code{spam-initialize}:
23099 (setq spam-use-stat t) ;; if needed
23103 So, what happens when you load @file{spam.el}?
23105 First, some hooks will get installed by @code{spam-initialize}. There
23106 are some hooks for @code{spam-stat} so it can save its databases, and
23107 there are hooks so interesting things will happen when you enter and
23108 leave a group. More on the sequence of events later (@pxref{Spam
23109 ELisp Package Sequence of Events}).
23111 You get the following keyboard commands:
23121 @findex gnus-summary-mark-as-spam
23122 @code{gnus-summary-mark-as-spam}.
23124 Mark current article as spam, showing it with the @samp{$} mark.
23125 Whenever you see a spam article, make sure to mark its summary line
23126 with @kbd{M-d} before leaving the group. This is done automatically
23127 for unread articles in @emph{spam} groups.
23133 @findex spam-bogofilter-score
23134 @code{spam-bogofilter-score}.
23136 You must have Bogofilter installed for that command to work properly.
23142 Also, when you load @file{spam.el}, you will be able to customize its
23143 variables. Try @code{customize-group} on the @samp{spam} variable
23147 * Spam ELisp Package Sequence of Events::
23148 * Spam ELisp Package Filtering of Incoming Mail::
23149 * Spam ELisp Package Global Variables::
23150 * Spam ELisp Package Sorting and Score Display in Summary Buffer::
23151 * Spam ELisp Package Configuration Examples::
23152 * Blacklists and Whitelists::
23153 * BBDB Whitelists::
23154 * Gmane Spam Reporting::
23155 * Anti-spam Hashcash Payments::
23157 * Regular Expressions Header Matching::
23159 * SpamAssassin back end::
23160 * ifile spam filtering::
23161 * spam-stat spam filtering::
23163 * Extending the Spam ELisp package::
23166 @node Spam ELisp Package Sequence of Events
23167 @subsubsection Spam ELisp Package Sequence of Events
23168 @cindex spam filtering
23169 @cindex spam filtering sequence of events
23171 You must read this section to understand how @code{spam.el} works.
23172 Do not skip, speed-read, or glance through this section.
23174 There are two @emph{contact points}, if you will, between
23175 @code{spam.el} and the rest of Gnus: checking new mail for spam, and
23178 Getting new mail in Gnus is done in one of two ways. You can either
23179 split your incoming mail or you can classify new articles as ham or
23180 spam when you enter the group.
23182 Splitting incoming mail is better suited to mail back ends such as
23183 @code{nnml} or @code{nnimap} where new mail appears in a single file
23184 called a @dfn{Spool File}. See @xref{Spam ELisp Package Filtering of
23187 @vindex gnus-spam-autodetect
23188 @vindex gnus-spam-autodetect-methods
23189 For back ends such as @code{nntp} there is no incoming mail spool, so
23190 an alternate mechanism must be used. This may also happen for
23191 back ends where the server is in charge of splitting incoming mail, and
23192 Gnus does not do further splitting. The @code{spam-autodetect} and
23193 @code{spam-autodetect-methods} group parameters (accessible with
23194 @kbd{G c} and @kbd{G p} as usual), and the corresponding variables
23195 @code{gnus-spam-autodetect} and @code{gnus-spam-autodetect-methods}
23196 (accessible with @kbd{M-x customize-variable} as usual) can help.
23198 When @code{spam-autodetect} is used (you can turn it on for a
23199 group/topic or wholesale by regular expression matches, as needed), it
23200 hooks into the process of entering a group. Thus, entering a group
23201 with unseen or unread articles becomes the substitute for checking
23202 incoming mail. Whether only unseen articles or all unread articles
23203 will be processed is determined by the
23204 @code{spam-autodetect-recheck-messages}. When set to @code{t}, unread
23205 messages will be rechecked. You should probably stick with the
23206 default of only checking unseen messages.
23208 @code{spam-autodetect} grants the user at once more and less control
23209 of spam filtering. The user will have more control over each group's
23210 spam methods, so for instance the @samp{ding} group may have
23211 @code{spam-use-BBDB} as the autodetection method, while the
23212 @samp{suspect} group may have the @code{spam-use-blacklist} and
23213 @code{spam-use-bogofilter} methods enabled. Every article detected to
23214 be spam will be marked with the spam mark @samp{$} and processed on
23215 exit from the group as normal spam. The user has less control over
23216 the @emph{sequence} of checks, as he might with @code{spam-split}.
23218 When the newly split mail goes into groups, or messages are
23219 autodetected to be ham or spam, those groups must be exited (after
23220 entering, if needed) for further spam processing to happen. It
23221 matters whether the group is considered a ham group, a spam group, or
23222 is unclassified, based on its @code{spam-content} parameter
23223 (@pxref{Spam ELisp Package Global Variables}). Spam groups have the
23224 additional characteristic that, when entered, any unseen or unread
23225 articles (depending on the @code{spam-mark-only-unseen-as-spam}
23226 variable) will be marked as spam. Thus, mail split into a spam group
23227 gets automatically marked as spam when you enter the group.
23229 Thus, when you exit a group, the @code{spam-processors} are applied,
23230 if any are set, and the processed mail is moved to the
23231 @code{ham-process-destination} or the @code{spam-process-destination}
23232 depending on the article's classification. If the
23233 @code{ham-process-destination} or the @code{spam-process-destination},
23234 whichever is appropriate, are @code{nil}, the article is left in the
23237 If a spam is found in any group (this can be changed to only non-spam
23238 groups with @code{spam-move-spam-nonspam-groups-only}), it is
23239 processed by the active @code{spam-processors} (@pxref{Spam ELisp
23240 Package Global Variables}) when the group is exited. Furthermore, the
23241 spam is moved to the @code{spam-process-destination} (@pxref{Spam
23242 ELisp Package Global Variables}) for further training or deletion.
23243 You have to load the @code{gnus-registry.el} package and enable the
23244 @code{spam-log-to-registry} variable if you want spam to be processed
23245 no more than once. Thus, spam is detected and processed everywhere,
23246 which is what most people want. If the
23247 @code{spam-process-destination} is @code{nil}, the spam is marked as
23248 expired, which is usually the right thing to do.
23250 If spam can not be moved---because of a read-only back end such as
23251 @acronym{NNTP}, for example, it will be copied.
23253 If a ham mail is found in a ham group, as determined by the
23254 @code{ham-marks} parameter, it is processed as ham by the active ham
23255 @code{spam-processor} when the group is exited. With the variables
23256 @code{spam-process-ham-in-spam-groups} and
23257 @code{spam-process-ham-in-nonham-groups} the behavior can be further
23258 altered so ham found anywhere can be processed. You have to load the
23259 @code{gnus-registry.el} package and enable the
23260 @code{spam-log-to-registry} variable if you want ham to be processed
23261 no more than once. Thus, ham is detected and processed only when
23262 necessary, which is what most people want. More on this in
23263 @xref{Spam ELisp Package Configuration Examples}.
23265 If ham can not be moved---because of a read-only back end such as
23266 @acronym{NNTP}, for example, it will be copied.
23268 If all this seems confusing, don't worry. Soon it will be as natural
23269 as typing Lisp one-liners on a neural interface@dots{} err, sorry, that's
23270 50 years in the future yet. Just trust us, it's not so bad.
23272 @node Spam ELisp Package Filtering of Incoming Mail
23273 @subsubsection Spam ELisp Package Filtering of Incoming Mail
23274 @cindex spam filtering
23275 @cindex spam filtering incoming mail
23278 To use the @code{spam.el} facilities for incoming mail filtering, you
23279 must add the following to your fancy split list
23280 @code{nnmail-split-fancy} or @code{nnimap-split-fancy}:
23286 Note that the fancy split may be called @code{nnmail-split-fancy} or
23287 @code{nnimap-split-fancy}, depending on whether you use the nnmail or
23288 nnimap back ends to retrieve your mail.
23290 Also, @code{spam-split} will not modify incoming mail in any way.
23292 The @code{spam-split} function will process incoming mail and send the
23293 mail considered to be spam into the group name given by the variable
23294 @code{spam-split-group}. By default that group name is @samp{spam},
23295 but you can customize @code{spam-split-group}. Make sure the contents
23296 of @code{spam-split-group} are an @emph{unqualified} group name, for
23297 instance in an @code{nnimap} server @samp{your-server} the value
23298 @samp{spam} will turn out to be @samp{nnimap+your-server:spam}. The
23299 value @samp{nnimap+server:spam}, therefore, is wrong and will
23300 actually give you the group
23301 @samp{nnimap+your-server:nnimap+server:spam} which may or may not
23302 work depending on your server's tolerance for strange group names.
23304 You can also give @code{spam-split} a parameter,
23305 e.g. @code{spam-use-regex-headers} or @code{"maybe-spam"}. Why is
23308 Take these split rules (with @code{spam-use-regex-headers} and
23309 @code{spam-use-blackholes} set):
23312 nnimap-split-fancy '(|
23313 (any "ding" "ding")
23315 ;; @r{default mailbox}
23319 Now, the problem is that you want all ding messages to make it to the
23320 ding folder. But that will let obvious spam (for example, spam
23321 detected by SpamAssassin, and @code{spam-use-regex-headers}) through,
23322 when it's sent to the ding list. On the other hand, some messages to
23323 the ding list are from a mail server in the blackhole list, so the
23324 invocation of @code{spam-split} can't be before the ding rule.
23326 You can let SpamAssassin headers supersede ding rules, but all other
23327 @code{spam-split} rules (including a second invocation of the
23328 regex-headers check) will be after the ding rule:
23333 ;; @r{all spam detected by @code{spam-use-regex-headers} goes to @samp{regex-spam}}
23334 (: spam-split "regex-spam" 'spam-use-regex-headers)
23335 (any "ding" "ding")
23336 ;; @r{all other spam detected by spam-split goes to @code{spam-split-group}}
23338 ;; @r{default mailbox}
23342 This lets you invoke specific @code{spam-split} checks depending on
23343 your particular needs, and to target the results of those checks to a
23344 particular spam group. You don't have to throw all mail into all the
23345 spam tests. Another reason why this is nice is that messages to
23346 mailing lists you have rules for don't have to have resource-intensive
23347 blackhole checks performed on them. You could also specify different
23348 spam checks for your nnmail split vs. your nnimap split. Go crazy.
23350 You should still have specific checks such as
23351 @code{spam-use-regex-headers} set to @code{t}, even if you
23352 specifically invoke @code{spam-split} with the check. The reason is
23353 that when loading @file{spam.el}, some conditional loading is done
23354 depending on what @code{spam-use-xyz} variables you have set. This
23355 is usually not critical, though.
23357 @emph{Note for IMAP users}
23359 The boolean variable @code{nnimap-split-download-body} needs to be
23360 set, if you want to split based on the whole message instead of just
23361 the headers. By default, the nnimap back end will only retrieve the
23362 message headers. If you use a @emph{statistical} filter,
23363 e.g. @code{spam-check-bogofilter}, @code{spam-check-ifile}, or
23364 @code{spam-check-stat} (the splitters that can benefit from the full
23365 message body), this variable will be set automatically. It is not set
23366 for non-statistical back ends by default because it will slow
23367 @acronym{IMAP} down.
23369 @xref{Splitting in IMAP}.
23371 @node Spam ELisp Package Global Variables
23372 @subsubsection Spam ELisp Package Global Variables
23373 @cindex spam filtering
23374 @cindex spam filtering variables
23375 @cindex spam variables
23378 @vindex gnus-spam-process-newsgroups
23379 The concepts of ham processors and spam processors are very important.
23380 Ham processors and spam processors for a group can be set with the
23381 @code{spam-process} group parameter, or the
23382 @code{gnus-spam-process-newsgroups} variable. Ham processors take
23383 mail known to be non-spam (@emph{ham}) and process it in some way so
23384 that later similar mail will also be considered non-spam. Spam
23385 processors take mail known to be spam and process it so similar spam
23386 will be detected later.
23388 The format of the spam or ham processor entry used to be a symbol,
23389 but now it is a @sc{cons} cell. See the individual spam processor entries
23390 for more information.
23392 @vindex gnus-spam-newsgroup-contents
23393 Gnus learns from the spam you get. You have to collect your spam in
23394 one or more spam groups, and set or customize the variable
23395 @code{spam-junk-mailgroups} as appropriate. You can also declare
23396 groups to contain spam by setting their group parameter
23397 @code{spam-contents} to @code{gnus-group-spam-classification-spam}, or
23398 by customizing the corresponding variable
23399 @code{gnus-spam-newsgroup-contents}. The @code{spam-contents} group
23400 parameter and the @code{gnus-spam-newsgroup-contents} variable can
23401 also be used to declare groups as @emph{ham} groups if you set their
23402 classification to @code{gnus-group-spam-classification-ham}. If
23403 groups are not classified by means of @code{spam-junk-mailgroups},
23404 @code{spam-contents}, or @code{gnus-spam-newsgroup-contents}, they are
23405 considered @emph{unclassified}. All groups are unclassified by
23408 @vindex gnus-spam-mark
23410 In spam groups, all messages are considered to be spam by default:
23411 they get the @samp{$} mark (@code{gnus-spam-mark}) when you enter the
23412 group. If you have seen a message, had it marked as spam, then
23413 unmarked it, it won't be marked as spam when you enter the group
23414 thereafter. You can disable that behavior, so all unread messages
23415 will get the @samp{$} mark, if you set the
23416 @code{spam-mark-only-unseen-as-spam} parameter to @code{nil}. You
23417 should remove the @samp{$} mark when you are in the group summary
23418 buffer for every message that is not spam after all. To remove the
23419 @samp{$} mark, you can use @kbd{M-u} to ``unread'' the article, or
23420 @kbd{d} for declaring it read the non-spam way. When you leave a
23421 group, all spam-marked (@samp{$}) articles are sent to a spam
23422 processor which will study them as spam samples.
23424 Messages may also be deleted in various other ways, and unless
23425 @code{ham-marks} group parameter gets overridden below, marks @samp{R}
23426 and @samp{r} for default read or explicit delete, marks @samp{X} and
23427 @samp{K} for automatic or explicit kills, as well as mark @samp{Y} for
23428 low scores, are all considered to be associated with articles which
23429 are not spam. This assumption might be false, in particular if you
23430 use kill files or score files as means for detecting genuine spam, you
23431 should then adjust the @code{ham-marks} group parameter.
23434 You can customize this group or topic parameter to be the list of
23435 marks you want to consider ham. By default, the list contains the
23436 deleted, read, killed, kill-filed, and low-score marks (the idea is
23437 that these articles have been read, but are not spam). It can be
23438 useful to also include the tick mark in the ham marks. It is not
23439 recommended to make the unread mark a ham mark, because it normally
23440 indicates a lack of classification. But you can do it, and we'll be
23445 You can customize this group or topic parameter to be the list of
23446 marks you want to consider spam. By default, the list contains only
23447 the spam mark. It is not recommended to change that, but you can if
23448 you really want to.
23451 When you leave @emph{any} group, regardless of its
23452 @code{spam-contents} classification, all spam-marked articles are sent
23453 to a spam processor, which will study these as spam samples. If you
23454 explicit kill a lot, you might sometimes end up with articles marked
23455 @samp{K} which you never saw, and which might accidentally contain
23456 spam. Best is to make sure that real spam is marked with @samp{$},
23459 @vindex gnus-ham-process-destinations
23460 When you leave a @emph{spam} group, all spam-marked articles are
23461 marked as expired after processing with the spam processor. This is
23462 not done for @emph{unclassified} or @emph{ham} groups. Also, any
23463 @strong{ham} articles in a spam group will be moved to a location
23464 determined by either the @code{ham-process-destination} group
23465 parameter or a match in the @code{gnus-ham-process-destinations}
23466 variable, which is a list of regular expressions matched with group
23467 names (it's easiest to customize this variable with @kbd{M-x
23468 customize-variable @key{RET} gnus-ham-process-destinations}). Each
23469 group name list is a standard Lisp list, if you prefer to customize
23470 the variable manually. If the @code{ham-process-destination}
23471 parameter is not set, ham articles are left in place. If the
23472 @code{spam-mark-ham-unread-before-move-from-spam-group} parameter is
23473 set, the ham articles are marked as unread before being moved.
23475 If ham can not be moved---because of a read-only back end such as
23476 @acronym{NNTP}, for example, it will be copied.
23478 Note that you can use multiples destinations per group or regular
23479 expression! This enables you to send your ham to a regular mail
23480 group and to a @emph{ham training} group.
23482 When you leave a @emph{ham} group, all ham-marked articles are sent to
23483 a ham processor, which will study these as non-spam samples.
23485 @vindex spam-process-ham-in-spam-groups
23486 By default the variable @code{spam-process-ham-in-spam-groups} is
23487 @code{nil}. Set it to @code{t} if you want ham found in spam groups
23488 to be processed. Normally this is not done, you are expected instead
23489 to send your ham to a ham group and process it there.
23491 @vindex spam-process-ham-in-nonham-groups
23492 By default the variable @code{spam-process-ham-in-nonham-groups} is
23493 @code{nil}. Set it to @code{t} if you want ham found in non-ham (spam
23494 or unclassified) groups to be processed. Normally this is not done,
23495 you are expected instead to send your ham to a ham group and process
23498 @vindex gnus-spam-process-destinations
23499 When you leave a @emph{ham} or @emph{unclassified} group, all
23500 @strong{spam} articles are moved to a location determined by either
23501 the @code{spam-process-destination} group parameter or a match in the
23502 @code{gnus-spam-process-destinations} variable, which is a list of
23503 regular expressions matched with group names (it's easiest to
23504 customize this variable with @kbd{M-x customize-variable @key{RET}
23505 gnus-spam-process-destinations}). Each group name list is a standard
23506 Lisp list, if you prefer to customize the variable manually. If the
23507 @code{spam-process-destination} parameter is not set, the spam
23508 articles are only expired. The group name is fully qualified, meaning
23509 that if you see @samp{nntp:servername} before the group name in the
23510 group buffer then you need it here as well.
23512 If spam can not be moved---because of a read-only back end such as
23513 @acronym{NNTP}, for example, it will be copied.
23515 Note that you can use multiples destinations per group or regular
23516 expression! This enables you to send your spam to multiple @emph{spam
23519 @vindex spam-log-to-registry
23520 The problem with processing ham and spam is that Gnus doesn't track
23521 this processing by default. Enable the @code{spam-log-to-registry}
23522 variable so @code{spam.el} will use @code{gnus-registry.el} to track
23523 what articles have been processed, and avoid processing articles
23524 multiple times. Keep in mind that if you limit the number of registry
23525 entries, this won't work as well as it does without a limit.
23527 @vindex spam-mark-only-unseen-as-spam
23528 Set this variable if you want only unseen articles in spam groups to
23529 be marked as spam. By default, it is set. If you set it to
23530 @code{nil}, unread articles will also be marked as spam.
23532 @vindex spam-mark-ham-unread-before-move-from-spam-group
23533 Set this variable if you want ham to be unmarked before it is moved
23534 out of the spam group. This is very useful when you use something
23535 like the tick mark @samp{!} to mark ham---the article will be placed
23536 in your @code{ham-process-destination}, unmarked as if it came fresh
23537 from the mail server.
23539 @vindex spam-autodetect-recheck-messages
23540 When autodetecting spam, this variable tells @code{spam.el} whether
23541 only unseen articles or all unread articles should be checked for
23542 spam. It is recommended that you leave it off.
23544 @node Spam ELisp Package Sorting and Score Display in Summary Buffer
23545 @subsubsection Spam ELisp Package Sorting and Score Display in Summary Buffer
23546 @cindex spam scoring
23547 @cindex spam sorting
23548 @cindex spam score summary buffer
23549 @cindex spam sort summary buffer
23552 You can display the spam score of articles in your summary buffer, and
23553 you can sort articles by their spam score.
23555 First you need to decide which back end you will be using. If you use
23556 the @code{spam-use-spamassassin},
23557 @code{spam-use-spamassassin-headers}, or @code{spam-use-regex-headers}
23558 back end, the @code{X-Spam-Status} header will be used. If you use
23559 @code{spam-use-bogofilter}, the @code{X-Bogosity} header will be used.
23560 If you use @code{spam-use-crm114}, any header that matches the CRM114
23561 score format will be used. As long as you set the appropriate back end
23562 variable to t @emph{before} you load @file{spam.el}, you will be
23563 fine. @code{spam.el} will automatically add the right header to the
23564 internal Gnus list of required headers.
23566 To show the spam score in your summary buffer, add this line to your
23567 @code{gnus.el} file (note @code{spam.el} does not do that by default
23568 so it won't override any existing @code{S} formats you may have).
23571 (defalias 'gnus-user-format-function-S 'spam-user-format-function-S)
23574 Now just set your summary line format to use @code{%uS}. Here's an
23575 example that formats the spam score in a 5-character field:
23578 (setq gnus-summary-line-format
23579 "%U%R %10&user-date; $%5uS %6k %B %(%4L: %*%-25,25a%) %s \n")
23582 Finally, to sort by spam status, either do it globally:
23586 gnus-show-threads nil
23587 gnus-article-sort-functions
23588 '(spam-article-sort-by-spam-status))
23591 or per group (@pxref{Sorting the Summary Buffer}).
23593 @node Spam ELisp Package Configuration Examples
23594 @subsubsection Spam ELisp Package Configuration Examples
23595 @cindex spam filtering
23596 @cindex spam filtering configuration examples
23597 @cindex spam configuration examples
23600 @subsubheading Ted's setup
23602 From Ted Zlatanov <tzz@@lifelogs.com>.
23604 ;; @r{for @code{gnus-registry-split-fancy-with-parent} and spam autodetection}
23605 ;; @r{see @file{gnus-registry.el} for more information}
23606 (gnus-registry-initialize)
23609 ;; @r{I like @kbd{C-s} for marking spam}
23610 (define-key gnus-summary-mode-map "\C-s" 'gnus-summary-mark-as-spam)
23613 spam-log-to-registry t ; @r{for spam autodetection}
23615 spam-use-regex-headers t ; @r{catch X-Spam-Flag (SpamAssassin)}
23616 ;; @r{all groups with @samp{spam} in the name contain spam}
23617 gnus-spam-newsgroup-contents
23618 '(("spam" gnus-group-spam-classification-spam))
23619 ;; @r{see documentation for these}
23620 spam-move-spam-nonspam-groups-only nil
23621 spam-mark-only-unseen-as-spam t
23622 spam-mark-ham-unread-before-move-from-spam-group t
23623 nnimap-split-rule 'nnimap-split-fancy
23624 ;; @r{understand what this does before you copy it to your own setup!}
23625 nnimap-split-fancy '(|
23626 ;; @r{trace references to parents and put in their group}
23627 (: gnus-registry-split-fancy-with-parent)
23628 ;; @r{this will catch server-side SpamAssassin tags}
23629 (: spam-split 'spam-use-regex-headers)
23630 (any "ding" "ding")
23631 ;; @r{note that spam by default will go to @samp{spam}}
23633 ;; @r{default mailbox}
23636 ;; @r{my parameters, set with @kbd{G p}}
23638 ;; @r{all nnml groups, and all nnimap groups except}
23639 ;; @r{@samp{nnimap+mail.lifelogs.com:train} and}
23640 ;; @r{@samp{nnimap+mail.lifelogs.com:spam}: any spam goes to nnimap training,}
23641 ;; @r{because it must have been detected manually}
23643 ((spam-process-destination . "nnimap+mail.lifelogs.com:train"))
23645 ;; @r{all @acronym{NNTP} groups}
23646 ;; @r{autodetect spam with the blacklist and ham with the BBDB}
23647 ((spam-autodetect-methods spam-use-blacklist spam-use-BBDB)
23648 ;; @r{send all spam to the training group}
23649 (spam-process-destination . "nnimap+mail.lifelogs.com:train"))
23651 ;; @r{only some @acronym{NNTP} groups, where I want to autodetect spam}
23652 ((spam-autodetect . t))
23654 ;; @r{my nnimap @samp{nnimap+mail.lifelogs.com:spam} group}
23656 ;; @r{this is a spam group}
23657 ((spam-contents gnus-group-spam-classification-spam)
23659 ;; @r{any spam (which happens when I enter for all unseen messages,}
23660 ;; @r{because of the @code{gnus-spam-newsgroup-contents} setting above), goes to}
23661 ;; @r{@samp{nnimap+mail.lifelogs.com:train} unless I mark it as ham}
23663 (spam-process-destination "nnimap+mail.lifelogs.com:train")
23665 ;; @r{any ham goes to my @samp{nnimap+mail.lifelogs.com:mail} folder, but}
23666 ;; @r{also to my @samp{nnimap+mail.lifelogs.com:trainham} folder for training}
23668 (ham-process-destination "nnimap+mail.lifelogs.com:mail"
23669 "nnimap+mail.lifelogs.com:trainham")
23670 ;; @r{in this group, only @samp{!} marks are ham}
23672 (gnus-ticked-mark))
23673 ;; @r{remembers senders in the blacklist on the way out---this is}
23674 ;; @r{definitely not needed, it just makes me feel better}
23675 (spam-process (gnus-group-spam-exit-processor-blacklist)))
23677 ;; @r{Later, on the @acronym{IMAP} server I use the @samp{train} group for training}
23678 ;; @r{SpamAssassin to recognize spam, and the @samp{trainham} group fora}
23679 ;; @r{recognizing ham---but Gnus has nothing to do with it.}
23683 @subsubheading Using @code{spam.el} on an IMAP server with a statistical filter on the server
23684 From Reiner Steib <reiner.steib@@gmx.de>.
23686 My provider has set up bogofilter (in combination with @acronym{DCC}) on
23687 the mail server (@acronym{IMAP}). Recognized spam goes to
23688 @samp{spam.detected}, the rest goes through the normal filter rules,
23689 i.e. to @samp{some.folder} or to @samp{INBOX}. Training on false
23690 positives or negatives is done by copying or moving the article to
23691 @samp{training.ham} or @samp{training.spam} respectively. A cron job on
23692 the server feeds those to bogofilter with the suitable ham or spam
23693 options and deletes them from the @samp{training.ham} and
23694 @samp{training.spam} folders.
23696 With the following entries in @code{gnus-parameters}, @code{spam.el}
23697 does most of the job for me:
23700 ("nnimap:spam\\.detected"
23701 (gnus-article-sort-functions '(gnus-article-sort-by-chars))
23702 (ham-process-destination "nnimap:INBOX" "nnimap:training.ham")
23703 (spam-contents gnus-group-spam-classification-spam))
23704 ("nnimap:\\(INBOX\\|other-folders\\)"
23705 (spam-process-destination . "nnimap:training.spam")
23706 (spam-contents gnus-group-spam-classification-ham))
23711 @item @b{The Spam folder:}
23713 In the folder @samp{spam.detected}, I have to check for false positives
23714 (i.e. legitimate mails, that were wrongly judged as spam by
23715 bogofilter or DCC).
23717 Because of the @code{gnus-group-spam-classification-spam} entry, all
23718 messages are marked as spam (with @code{$}). When I find a false
23719 positive, I mark the message with some other ham mark (@code{ham-marks},
23720 @ref{Spam ELisp Package Global Variables}). On group exit, those
23721 messages are copied to both groups, @samp{INBOX} (where I want to have
23722 the article) and @samp{training.ham} (for training bogofilter) and
23723 deleted from the @samp{spam.detected} folder.
23725 The @code{gnus-article-sort-by-chars} entry simplifies detection of
23726 false positives for me. I receive lots of worms (sweN, @dots{}), that all
23727 have a similar size. Grouping them by size (i.e. chars) makes finding
23728 other false positives easier. (Of course worms aren't @i{spam}
23729 (@acronym{UCE}, @acronym{UBE}) strictly speaking. Anyhow, bogofilter is
23730 an excellent tool for filtering those unwanted mails for me.)
23732 @item @b{Ham folders:}
23734 In my ham folders, I just hit @kbd{S x}
23735 (@code{gnus-summary-mark-as-spam}) whenever I see an unrecognized spam
23736 mail (false negative). On group exit, those messages are moved to
23737 @samp{training.spam}.
23740 @subsubheading Reporting spam articles in Gmane groups with @code{spam-report.el}
23742 From Reiner Steib <reiner.steib@@gmx.de>.
23744 With following entry in @code{gnus-parameters}, @kbd{S x}
23745 (@code{gnus-summary-mark-as-spam}) marks articles in @code{gmane.*}
23746 groups as spam and reports the to Gmane at group exit:
23750 (spam-process (gnus-group-spam-exit-processor-report-gmane)))
23753 Additionally, I use @code{(setq spam-report-gmane-use-article-number nil)}
23754 because I don't read the groups directly from news.gmane.org, but
23755 through my local news server (leafnode). I.e. the article numbers are
23756 not the same as on news.gmane.org, thus @code{spam-report.el} has to check
23757 the @code{X-Report-Spam} header to find the correct number.
23759 @node Blacklists and Whitelists
23760 @subsubsection Blacklists and Whitelists
23761 @cindex spam filtering
23762 @cindex whitelists, spam filtering
23763 @cindex blacklists, spam filtering
23766 @defvar spam-use-blacklist
23768 Set this variable to @code{t} if you want to use blacklists when
23769 splitting incoming mail. Messages whose senders are in the blacklist
23770 will be sent to the @code{spam-split-group}. This is an explicit
23771 filter, meaning that it acts only on mail senders @emph{declared} to
23776 @defvar spam-use-whitelist
23778 Set this variable to @code{t} if you want to use whitelists when
23779 splitting incoming mail. Messages whose senders are not in the
23780 whitelist will be sent to the next spam-split rule. This is an
23781 explicit filter, meaning that unless someone is in the whitelist, their
23782 messages are not assumed to be spam or ham.
23786 @defvar spam-use-whitelist-exclusive
23788 Set this variable to @code{t} if you want to use whitelists as an
23789 implicit filter, meaning that every message will be considered spam
23790 unless the sender is in the whitelist. Use with care.
23794 @defvar gnus-group-spam-exit-processor-blacklist
23796 Add this symbol to a group's @code{spam-process} parameter by
23797 customizing the group parameters or the
23798 @code{gnus-spam-process-newsgroups} variable. When this symbol is
23799 added to a group's @code{spam-process} parameter, the senders of
23800 spam-marked articles will be added to the blacklist.
23804 Instead of the obsolete
23805 @code{gnus-group-spam-exit-processor-blacklist}, it is recommended
23806 that you use @code{'(spam spam-use-blacklist)}. Everything will work
23807 the same way, we promise.
23811 @defvar gnus-group-ham-exit-processor-whitelist
23813 Add this symbol to a group's @code{spam-process} parameter by
23814 customizing the group parameters or the
23815 @code{gnus-spam-process-newsgroups} variable. When this symbol is
23816 added to a group's @code{spam-process} parameter, the senders of
23817 ham-marked articles in @emph{ham} groups will be added to the
23822 Instead of the obsolete
23823 @code{gnus-group-ham-exit-processor-whitelist}, it is recommended
23824 that you use @code{'(ham spam-use-whitelist)}. Everything will work
23825 the same way, we promise.
23829 Blacklists are lists of regular expressions matching addresses you
23830 consider to be spam senders. For instance, to block mail from any
23831 sender at @samp{vmadmin.com}, you can put @samp{vmadmin.com} in your
23832 blacklist. You start out with an empty blacklist. Blacklist entries
23833 use the Emacs regular expression syntax.
23835 Conversely, whitelists tell Gnus what addresses are considered
23836 legitimate. All messages from whitelisted addresses are considered
23837 non-spam. Also see @ref{BBDB Whitelists}. Whitelist entries use the
23838 Emacs regular expression syntax.
23840 The blacklist and whitelist file locations can be customized with the
23841 @code{spam-directory} variable (@file{~/News/spam} by default), or
23842 the @code{spam-whitelist} and @code{spam-blacklist} variables
23843 directly. The whitelist and blacklist files will by default be in the
23844 @code{spam-directory} directory, named @file{whitelist} and
23845 @file{blacklist} respectively.
23847 @node BBDB Whitelists
23848 @subsubsection BBDB Whitelists
23849 @cindex spam filtering
23850 @cindex BBDB whitelists, spam filtering
23851 @cindex BBDB, spam filtering
23854 @defvar spam-use-BBDB
23856 Analogous to @code{spam-use-whitelist} (@pxref{Blacklists and
23857 Whitelists}), but uses the BBDB as the source of whitelisted
23858 addresses, without regular expressions. You must have the BBDB loaded
23859 for @code{spam-use-BBDB} to work properly. Messages whose senders are
23860 not in the BBDB will be sent to the next spam-split rule. This is an
23861 explicit filter, meaning that unless someone is in the BBDB, their
23862 messages are not assumed to be spam or ham.
23866 @defvar spam-use-BBDB-exclusive
23868 Set this variable to @code{t} if you want to use the BBDB as an
23869 implicit filter, meaning that every message will be considered spam
23870 unless the sender is in the BBDB. Use with care. Only sender
23871 addresses in the BBDB will be allowed through; all others will be
23872 classified as spammers.
23874 While @code{spam-use-BBDB-exclusive} @emph{can} be used as an alias
23875 for @code{spam-use-BBDB} as far as @code{spam.el} is concerned, it is
23876 @emph{not} a separate back end. If you set
23877 @code{spam-use-BBDB-exclusive} to t, @emph{all} your BBDB splitting
23882 @defvar gnus-group-ham-exit-processor-BBDB
23884 Add this symbol to a group's @code{spam-process} parameter by
23885 customizing the group parameters or the
23886 @code{gnus-spam-process-newsgroups} variable. When this symbol is
23887 added to a group's @code{spam-process} parameter, the senders of
23888 ham-marked articles in @emph{ham} groups will be added to the
23893 Instead of the obsolete
23894 @code{gnus-group-ham-exit-processor-BBDB}, it is recommended
23895 that you use @code{'(ham spam-use-BBDB)}. Everything will work
23896 the same way, we promise.
23900 @node Gmane Spam Reporting
23901 @subsubsection Gmane Spam Reporting
23902 @cindex spam reporting
23903 @cindex Gmane, spam reporting
23904 @cindex Gmane, spam reporting
23907 @defvar gnus-group-spam-exit-processor-report-gmane
23909 Add this symbol to a group's @code{spam-process} parameter by
23910 customizing the group parameters or the
23911 @code{gnus-spam-process-newsgroups} variable. When this symbol is
23912 added to a group's @code{spam-process} parameter, the spam-marked
23913 articles groups will be reported to the Gmane administrators via a
23916 Gmane can be found at @uref{http://gmane.org}.
23920 Instead of the obsolete
23921 @code{gnus-group-spam-exit-processor-report-gmane}, it is recommended
23922 that you use @code{'(spam spam-use-gmane)}. Everything will work the
23923 same way, we promise.
23927 @defvar spam-report-gmane-use-article-number
23929 This variable is @code{t} by default. Set it to @code{nil} if you are
23930 running your own news server, for instance, and the local article
23931 numbers don't correspond to the Gmane article numbers. When
23932 @code{spam-report-gmane-use-article-number} is @code{nil},
23933 @code{spam-report.el} will use the @code{X-Report-Spam} header that
23938 @node Anti-spam Hashcash Payments
23939 @subsubsection Anti-spam Hashcash Payments
23940 @cindex spam filtering
23941 @cindex hashcash, spam filtering
23944 @defvar spam-use-hashcash
23946 Similar to @code{spam-use-whitelist} (@pxref{Blacklists and
23947 Whitelists}), but uses hashcash tokens for whitelisting messages
23948 instead of the sender address. Messages without a hashcash payment
23949 token will be sent to the next spam-split rule. This is an explicit
23950 filter, meaning that unless a hashcash token is found, the messages
23951 are not assumed to be spam or ham.
23956 @subsubsection Blackholes
23957 @cindex spam filtering
23958 @cindex blackholes, spam filtering
23961 @defvar spam-use-blackholes
23963 This option is disabled by default. You can let Gnus consult the
23964 blackhole-type distributed spam processing systems (DCC, for instance)
23965 when you set this option. The variable @code{spam-blackhole-servers}
23966 holds the list of blackhole servers Gnus will consult. The current
23967 list is fairly comprehensive, but make sure to let us know if it
23968 contains outdated servers.
23970 The blackhole check uses the @code{dig.el} package, but you can tell
23971 @code{spam.el} to use @code{dns.el} instead for better performance if
23972 you set @code{spam-use-dig} to @code{nil}. It is not recommended at
23973 this time to set @code{spam-use-dig} to @code{nil} despite the
23974 possible performance improvements, because some users may be unable to
23975 use it, but you can try it and see if it works for you.
23979 @defvar spam-blackhole-servers
23981 The list of servers to consult for blackhole checks.
23985 @defvar spam-blackhole-good-server-regex
23987 A regular expression for IPs that should not be checked against the
23988 blackhole server list. When set to @code{nil}, it has no effect.
23992 @defvar spam-use-dig
23994 Use the @code{dig.el} package instead of the @code{dns.el} package.
23995 The default setting of @code{t} is recommended.
23999 Blackhole checks are done only on incoming mail. There is no spam or
24000 ham processor for blackholes.
24002 @node Regular Expressions Header Matching
24003 @subsubsection Regular Expressions Header Matching
24004 @cindex spam filtering
24005 @cindex regular expressions header matching, spam filtering
24008 @defvar spam-use-regex-headers
24010 This option is disabled by default. You can let Gnus check the
24011 message headers against lists of regular expressions when you set this
24012 option. The variables @code{spam-regex-headers-spam} and
24013 @code{spam-regex-headers-ham} hold the list of regular expressions.
24014 Gnus will check against the message headers to determine if the
24015 message is spam or ham, respectively.
24019 @defvar spam-regex-headers-spam
24021 The list of regular expressions that, when matched in the headers of
24022 the message, positively identify it as spam.
24026 @defvar spam-regex-headers-ham
24028 The list of regular expressions that, when matched in the headers of
24029 the message, positively identify it as ham.
24033 Regular expression header checks are done only on incoming mail.
24034 There is no specific spam or ham processor for regular expressions.
24037 @subsubsection Bogofilter
24038 @cindex spam filtering
24039 @cindex bogofilter, spam filtering
24042 @defvar spam-use-bogofilter
24044 Set this variable if you want @code{spam-split} to use Eric Raymond's
24047 With a minimum of care for associating the @samp{$} mark for spam
24048 articles only, Bogofilter training all gets fairly automatic. You
24049 should do this until you get a few hundreds of articles in each
24050 category, spam or not. The command @kbd{S t} in summary mode, either
24051 for debugging or for curiosity, shows the @emph{spamicity} score of
24052 the current article (between 0.0 and 1.0).
24054 Bogofilter determines if a message is spam based on a specific
24055 threshold. That threshold can be customized, consult the Bogofilter
24058 If the @code{bogofilter} executable is not in your path, Bogofilter
24059 processing will be turned off.
24061 You should not enable this if you use @code{spam-use-bogofilter-headers}.
24065 @defvar spam-use-bogofilter-headers
24067 Set this variable if you want @code{spam-split} to use Eric Raymond's
24068 speedy Bogofilter, looking only at the message headers. It works
24069 similarly to @code{spam-use-bogofilter}, but the @code{X-Bogosity} header
24070 must be in the message already. Normally you would do this with a
24071 procmail recipe or something similar; consult the Bogofilter
24072 installation documents for details.
24074 You should not enable this if you use @code{spam-use-bogofilter}.
24078 @defvar gnus-group-spam-exit-processor-bogofilter
24079 Add this symbol to a group's @code{spam-process} parameter by
24080 customizing the group parameters or the
24081 @code{gnus-spam-process-newsgroups} variable. When this symbol is
24082 added to a group's @code{spam-process} parameter, spam-marked articles
24083 will be added to the Bogofilter spam database.
24087 Instead of the obsolete
24088 @code{gnus-group-spam-exit-processor-bogofilter}, it is recommended
24089 that you use @code{'(spam spam-use-bogofilter)}. Everything will work
24090 the same way, we promise.
24093 @defvar gnus-group-ham-exit-processor-bogofilter
24094 Add this symbol to a group's @code{spam-process} parameter by
24095 customizing the group parameters or the
24096 @code{gnus-spam-process-newsgroups} variable. When this symbol is
24097 added to a group's @code{spam-process} parameter, the ham-marked
24098 articles in @emph{ham} groups will be added to the Bogofilter database
24099 of non-spam messages.
24103 Instead of the obsolete
24104 @code{gnus-group-ham-exit-processor-bogofilter}, it is recommended
24105 that you use @code{'(ham spam-use-bogofilter)}. Everything will work
24106 the same way, we promise.
24109 @defvar spam-bogofilter-database-directory
24111 This is the directory where Bogofilter will store its databases. It
24112 is not specified by default, so Bogofilter will use its own default
24113 database directory.
24117 The Bogofilter mail classifier is similar to @command{ifile} in intent and
24118 purpose. A ham and a spam processor are provided, plus the
24119 @code{spam-use-bogofilter} and @code{spam-use-bogofilter-headers}
24120 variables to indicate to spam-split that Bogofilter should either be
24121 used, or has already been used on the article. The 0.9.2.1 version of
24122 Bogofilter was used to test this functionality.
24124 @node SpamAssassin back end
24125 @subsubsection SpamAssassin back end
24126 @cindex spam filtering
24127 @cindex spamassassin, spam filtering
24130 @defvar spam-use-spamassassin
24132 Set this variable if you want @code{spam-split} to use SpamAssassin.
24134 SpamAssassin assigns a score to each article based on a set of rules
24135 and tests, including a Bayesian filter. The Bayesian filter can be
24136 trained by associating the @samp{$} mark for spam articles. The
24137 spam score can be viewed by using the command @kbd{S t} in summary
24140 If you set this variable, each article will be processed by
24141 SpamAssassin when @code{spam-split} is called. If your mail is
24142 preprocessed by SpamAssassin, and you want to just use the
24143 SpamAssassin headers, set @code{spam-use-spamassassin-headers}
24146 You should not enable this is you use
24147 @code{spam-use-spamassassin-headers}.
24151 @defvar spam-use-spamassassin-headers
24153 Set this variable if your mail is preprocessed by SpamAssassin and
24154 want @code{spam-split} to split based on the SpamAssassin headers.
24156 You should not enable this is you use @code{spam-use-spamassassin}.
24160 @defvar spam-spamassassin-path
24162 This variable points to the SpamAssassin executable. If you have
24163 @code{spamd} running, you can set this variable to the @code{spamc}
24164 executable for faster processing. See the SpamAssassin documentation
24165 for more information on @code{spamd}/@code{spamc}.
24169 SpamAssassin is a powerful and flexible spam filter that uses a wide
24170 variety of tests to identify spam. A ham and a spam processors are
24171 provided, plus the @code{spam-use-spamassassin} and
24172 @code{spam-use-spamassassin-headers} variables to indicate to
24173 spam-split that SpamAssassin should be either used, or has already
24174 been used on the article. The 2.63 version of SpamAssassin was used
24175 to test this functionality.
24177 @node ifile spam filtering
24178 @subsubsection ifile spam filtering
24179 @cindex spam filtering
24180 @cindex ifile, spam filtering
24183 @defvar spam-use-ifile
24185 Enable this variable if you want @code{spam-split} to use @command{ifile}, a
24186 statistical analyzer similar to Bogofilter.
24190 @defvar spam-ifile-all-categories
24192 Enable this variable if you want @code{spam-use-ifile} to give you all
24193 the ifile categories, not just spam/non-spam. If you use this, make
24194 sure you train ifile as described in its documentation.
24198 @defvar spam-ifile-spam-category
24200 This is the category of spam messages as far as ifile is concerned.
24201 The actual string used is irrelevant, but you probably want to leave
24202 the default value of @samp{spam}.
24205 @defvar spam-ifile-database-path
24207 This is the filename for the ifile database. It is not specified by
24208 default, so ifile will use its own default database name.
24212 The ifile mail classifier is similar to Bogofilter in intent and
24213 purpose. A ham and a spam processor are provided, plus the
24214 @code{spam-use-ifile} variable to indicate to spam-split that ifile
24215 should be used. The 1.2.1 version of ifile was used to test this
24218 @node spam-stat spam filtering
24219 @subsubsection spam-stat spam filtering
24220 @cindex spam filtering
24221 @cindex spam-stat, spam filtering
24225 @xref{Filtering Spam Using Statistics with spam-stat}.
24227 @defvar spam-use-stat
24229 Enable this variable if you want @code{spam-split} to use
24230 spam-stat.el, an Emacs Lisp statistical analyzer.
24234 @defvar gnus-group-spam-exit-processor-stat
24235 Add this symbol to a group's @code{spam-process} parameter by
24236 customizing the group parameters or the
24237 @code{gnus-spam-process-newsgroups} variable. When this symbol is
24238 added to a group's @code{spam-process} parameter, the spam-marked
24239 articles will be added to the spam-stat database of spam messages.
24243 Instead of the obsolete
24244 @code{gnus-group-spam-exit-processor-stat}, it is recommended
24245 that you use @code{'(spam spam-use-stat)}. Everything will work
24246 the same way, we promise.
24249 @defvar gnus-group-ham-exit-processor-stat
24250 Add this symbol to a group's @code{spam-process} parameter by
24251 customizing the group parameters or the
24252 @code{gnus-spam-process-newsgroups} variable. When this symbol is
24253 added to a group's @code{spam-process} parameter, the ham-marked
24254 articles in @emph{ham} groups will be added to the spam-stat database
24255 of non-spam messages.
24259 Instead of the obsolete
24260 @code{gnus-group-ham-exit-processor-stat}, it is recommended
24261 that you use @code{'(ham spam-use-stat)}. Everything will work
24262 the same way, we promise.
24265 This enables @code{spam.el} to cooperate with @file{spam-stat.el}.
24266 @file{spam-stat.el} provides an internal (Lisp-only) spam database,
24267 which unlike ifile or Bogofilter does not require external programs.
24268 A spam and a ham processor, and the @code{spam-use-stat} variable for
24269 @code{spam-split} are provided.
24272 @subsubsection Using SpamOracle with Gnus
24273 @cindex spam filtering
24277 An easy way to filter out spam is to use SpamOracle. SpamOracle is an
24278 statistical mail filtering tool written by Xavier Leroy and needs to be
24279 installed separately.
24281 There are several ways to use SpamOracle with Gnus. In all cases, your
24282 mail is piped through SpamOracle in its @emph{mark} mode. SpamOracle will
24283 then enter an @samp{X-Spam} header indicating whether it regards the
24284 mail as a spam mail or not.
24286 One possibility is to run SpamOracle as a @code{:prescript} from the
24287 @xref{Mail Source Specifiers}, (@pxref{SpamAssassin}). This method has
24288 the advantage that the user can see the @emph{X-Spam} headers.
24290 The easiest method is to make @code{spam.el} (@pxref{Filtering Spam
24291 Using The Spam ELisp Package}) call SpamOracle.
24293 @vindex spam-use-spamoracle
24294 To enable SpamOracle usage by @code{spam.el}, set the variable
24295 @code{spam-use-spamoracle} to @code{t} and configure the
24296 @code{nnmail-split-fancy} or @code{nnimap-split-fancy} as described in
24297 the section @xref{Filtering Spam Using The Spam ELisp Package}. In
24298 this example the @samp{INBOX} of an nnimap server is filtered using
24299 SpamOracle. Mails recognized as spam mails will be moved to
24300 @code{spam-split-group}, @samp{Junk} in this case. Ham messages stay
24304 (setq spam-use-spamoracle t
24305 spam-split-group "Junk"
24306 nnimap-split-inbox '("INBOX")
24307 nnimap-split-rule 'nnimap-split-fancy
24308 nnimap-split-fancy '(| (: spam-split) "INBOX"))
24311 @defvar spam-use-spamoracle
24312 Set to @code{t} if you want Gnus to enable spam filtering using
24316 @defvar spam-spamoracle-binary
24317 Gnus uses the SpamOracle binary called @file{spamoracle} found in the
24318 user's PATH. Using the variable @code{spam-spamoracle-binary}, this
24322 @defvar spam-spamoracle-database
24323 By default, SpamOracle uses the file @file{~/.spamoracle.db} as a database to
24324 store its analyses. This is controlled by the variable
24325 @code{spam-spamoracle-database} which defaults to @code{nil}. That means
24326 the default SpamOracle database will be used. In case you want your
24327 database to live somewhere special, set
24328 @code{spam-spamoracle-database} to this path.
24331 SpamOracle employs a statistical algorithm to determine whether a
24332 message is spam or ham. In order to get good results, meaning few
24333 false hits or misses, SpamOracle needs training. SpamOracle learns the
24334 characteristics of your spam mails. Using the @emph{add} mode
24335 (training mode) one has to feed good (ham) and spam mails to
24336 SpamOracle. This can be done by pressing @kbd{|} in the Summary buffer
24337 and pipe the mail to a SpamOracle process or using @code{spam.el}'s
24338 spam- and ham-processors, which is much more convenient. For a
24339 detailed description of spam- and ham-processors, @xref{Filtering Spam
24340 Using The Spam ELisp Package}.
24342 @defvar gnus-group-spam-exit-processor-spamoracle
24343 Add this symbol to a group's @code{spam-process} parameter by
24344 customizing the group parameter or the
24345 @code{gnus-spam-process-newsgroups} variable. When this symbol is added
24346 to a group's @code{spam-process} parameter, spam-marked articles will be
24347 sent to SpamOracle as spam samples.
24351 Instead of the obsolete
24352 @code{gnus-group-spam-exit-processor-spamoracle}, it is recommended
24353 that you use @code{'(spam spam-use-spamoracle)}. Everything will work
24354 the same way, we promise.
24357 @defvar gnus-group-ham-exit-processor-spamoracle
24358 Add this symbol to a group's @code{spam-process} parameter by
24359 customizing the group parameter or the
24360 @code{gnus-spam-process-newsgroups} variable. When this symbol is added
24361 to a group's @code{spam-process} parameter, the ham-marked articles in
24362 @emph{ham} groups will be sent to the SpamOracle as samples of ham
24367 Instead of the obsolete
24368 @code{gnus-group-ham-exit-processor-spamoracle}, it is recommended
24369 that you use @code{'(ham spam-use-spamoracle)}. Everything will work
24370 the same way, we promise.
24373 @emph{Example:} These are the Group Parameters of a group that has been
24374 classified as a ham group, meaning that it should only contain ham
24377 ((spam-contents gnus-group-spam-classification-ham)
24378 (spam-process ((ham spam-use-spamoracle)
24379 (spam spam-use-spamoracle))))
24381 For this group the @code{spam-use-spamoracle} is installed for both
24382 ham and spam processing. If the group contains spam message
24383 (e.g. because SpamOracle has not had enough sample messages yet) and
24384 the user marks some messages as spam messages, these messages will be
24385 processed by SpamOracle. The processor sends the messages to
24386 SpamOracle as new samples for spam.
24388 @node Extending the Spam ELisp package
24389 @subsubsection Extending the Spam ELisp package
24390 @cindex spam filtering
24391 @cindex spam elisp package, extending
24392 @cindex extending the spam elisp package
24394 Say you want to add a new back end called blackbox. For filtering
24395 incoming mail, provide the following:
24403 (defvar spam-use-blackbox nil
24404 "True if blackbox should be used.")
24407 Write @code{spam-check-blackbox} if Blackbox can check incoming mail.
24409 Write @code{spam-blackbox-register-routine} and
24410 @code{spam-blackbox-unregister-routine} using the bogofilter
24411 register/unregister routines as a start, or other restister/unregister
24412 routines more appropriate to Blackbox, if Blackbox can
24413 register/unregister spam and ham.
24418 The @code{spam-check-blackbox} function should return @samp{nil} or
24419 @code{spam-split-group}, observing the other conventions. See the
24420 existing @code{spam-check-*} functions for examples of what you can
24421 do, and stick to the template unless you fully understand the reasons
24426 For processing spam and ham messages, provide the following:
24433 Note you don't have to provide a spam or a ham processor. Only
24434 provide them if Blackbox supports spam or ham processing.
24436 Also, ham and spam processors are being phased out as single
24437 variables. Instead the form @code{'(spam spam-use-blackbox)} or
24438 @code{'(ham spam-use-blackbox)} is favored. For now, spam/ham
24439 processor variables are still around but they won't be for long.
24442 (defvar gnus-group-spam-exit-processor-blackbox "blackbox-spam"
24443 "The Blackbox summary exit spam processor.
24444 Only applicable to spam groups.")
24446 (defvar gnus-group-ham-exit-processor-blackbox "blackbox-ham"
24447 "The whitelist summary exit ham processor.
24448 Only applicable to non-spam (unclassified and ham) groups.")
24457 (const :tag "Spam: Blackbox" (spam spam-use-blackbox))
24458 (const :tag "Ham: Blackbox" (ham spam-use-blackbox))
24460 to the @code{spam-process} group parameter in @code{gnus.el}. Make
24461 sure you do it twice, once for the parameter and once for the
24462 variable customization.
24466 (variable-item spam-use-blackbox)
24468 to the @code{spam-autodetect-methods} group parameter in
24469 @code{gnus.el} if Blackbox can check incoming mail for spam contents.
24471 Finally, use the appropriate @code{spam-install-*-backend} function in
24472 @code{spam.el}. Here are the available functions.
24478 @code{spam-install-backend-alias}
24480 This function will simply install an alias for a back end that does
24481 everything like the original back end. It is currently only used to
24482 make @code{spam-use-BBDB-exclusive} act like @code{spam-use-BBDB}.
24485 @code{spam-install-nocheck-backend}
24487 This function installs a back end that has no check function, but can
24488 register/unregister ham or spam. The @code{spam-use-gmane} back end is
24492 @code{spam-install-checkonly-backend}
24494 This function will install a back end that can only check incoming mail
24495 for spam contents. It can't register or unregister messages.
24496 @code{spam-use-blackholes} and @code{spam-use-hashcash} are such
24500 @code{spam-install-statistical-checkonly-backend}
24502 This function installs a statistical back end (one which requires the
24503 full body of a message to check it) that can only check incoming mail
24504 for contents. @code{spam-use-regex-body} is such a filter.
24507 @code{spam-install-statistical-backend}
24509 This function install a statistical back end with incoming checks and
24510 registration/unregistration routines. @code{spam-use-bogofilter} is
24514 @code{spam-install-backend}
24516 This is the most normal back end installation, where a back end that can
24517 check and register/unregister messages is set up without statistical
24518 abilities. The @code{spam-use-BBDB} is such a back end.
24521 @code{spam-install-mover-backend}
24523 Mover back ends are internal to @code{spam.el} and specifically move
24524 articles around when the summary is exited. You will very probably
24525 never install such a back end.
24531 @node Filtering Spam Using Statistics with spam-stat
24532 @subsection Filtering Spam Using Statistics with spam-stat
24533 @cindex Paul Graham
24534 @cindex Graham, Paul
24535 @cindex naive Bayesian spam filtering
24536 @cindex Bayesian spam filtering, naive
24537 @cindex spam filtering, naive Bayesian
24539 Paul Graham has written an excellent essay about spam filtering using
24540 statistics: @uref{http://www.paulgraham.com/spam.html,A Plan for
24541 Spam}. In it he describes the inherent deficiency of rule-based
24542 filtering as used by SpamAssassin, for example: Somebody has to write
24543 the rules, and everybody else has to install these rules. You are
24544 always late. It would be much better, he argues, to filter mail based
24545 on whether it somehow resembles spam or non-spam. One way to measure
24546 this is word distribution. He then goes on to describe a solution
24547 that checks whether a new mail resembles any of your other spam mails
24550 The basic idea is this: Create a two collections of your mail, one
24551 with spam, one with non-spam. Count how often each word appears in
24552 either collection, weight this by the total number of mails in the
24553 collections, and store this information in a dictionary. For every
24554 word in a new mail, determine its probability to belong to a spam or a
24555 non-spam mail. Use the 15 most conspicuous words, compute the total
24556 probability of the mail being spam. If this probability is higher
24557 than a certain threshold, the mail is considered to be spam.
24559 Gnus supports this kind of filtering. But it needs some setting up.
24560 First, you need two collections of your mail, one with spam, one with
24561 non-spam. Then you need to create a dictionary using these two
24562 collections, and save it. And last but not least, you need to use
24563 this dictionary in your fancy mail splitting rules.
24566 * Creating a spam-stat dictionary::
24567 * Splitting mail using spam-stat::
24568 * Low-level interface to the spam-stat dictionary::
24571 @node Creating a spam-stat dictionary
24572 @subsubsection Creating a spam-stat dictionary
24574 Before you can begin to filter spam based on statistics, you must
24575 create these statistics based on two mail collections, one with spam,
24576 one with non-spam. These statistics are then stored in a dictionary
24577 for later use. In order for these statistics to be meaningful, you
24578 need several hundred emails in both collections.
24580 Gnus currently supports only the nnml back end for automated dictionary
24581 creation. The nnml back end stores all mails in a directory, one file
24582 per mail. Use the following:
24584 @defun spam-stat-process-spam-directory
24585 Create spam statistics for every file in this directory. Every file
24586 is treated as one spam mail.
24589 @defun spam-stat-process-non-spam-directory
24590 Create non-spam statistics for every file in this directory. Every
24591 file is treated as one non-spam mail.
24594 Usually you would call @code{spam-stat-process-spam-directory} on a
24595 directory such as @file{~/Mail/mail/spam} (this usually corresponds
24596 the the group @samp{nnml:mail.spam}), and you would call
24597 @code{spam-stat-process-non-spam-directory} on a directory such as
24598 @file{~/Mail/mail/misc} (this usually corresponds the the group
24599 @samp{nnml:mail.misc}).
24601 When you are using @acronym{IMAP}, you won't have the mails available
24602 locally, so that will not work. One solution is to use the Gnus Agent
24603 to cache the articles. Then you can use directories such as
24604 @file{"~/News/agent/nnimap/mail.yourisp.com/personal_spam"} for
24605 @code{spam-stat-process-spam-directory}. @xref{Agent as Cache}.
24608 This variable holds the hash-table with all the statistics---the
24609 dictionary we have been talking about. For every word in either
24610 collection, this hash-table stores a vector describing how often the
24611 word appeared in spam and often it appeared in non-spam mails.
24614 If you want to regenerate the statistics from scratch, you need to
24615 reset the dictionary.
24617 @defun spam-stat-reset
24618 Reset the @code{spam-stat} hash-table, deleting all the statistics.
24621 When you are done, you must save the dictionary. The dictionary may
24622 be rather large. If you will not update the dictionary incrementally
24623 (instead, you will recreate it once a month, for example), then you
24624 can reduce the size of the dictionary by deleting all words that did
24625 not appear often enough or that do not clearly belong to only spam or
24626 only non-spam mails.
24628 @defun spam-stat-reduce-size
24629 Reduce the size of the dictionary. Use this only if you do not want
24630 to update the dictionary incrementally.
24633 @defun spam-stat-save
24634 Save the dictionary.
24637 @defvar spam-stat-file
24638 The filename used to store the dictionary. This defaults to
24639 @file{~/.spam-stat.el}.
24642 @node Splitting mail using spam-stat
24643 @subsubsection Splitting mail using spam-stat
24645 In order to use @code{spam-stat} to split your mail, you need to add the
24646 following to your @file{~/.gnus.el} file:
24649 (require 'spam-stat)
24653 This will load the necessary Gnus code, and the dictionary you
24656 Next, you need to adapt your fancy splitting rules: You need to
24657 determine how to use @code{spam-stat}. The following examples are for
24658 the nnml back end. Using the nnimap back end works just as well. Just
24659 use @code{nnimap-split-fancy} instead of @code{nnmail-split-fancy}.
24661 In the simplest case, you only have two groups, @samp{mail.misc} and
24662 @samp{mail.spam}. The following expression says that mail is either
24663 spam or it should go into @samp{mail.misc}. If it is spam, then
24664 @code{spam-stat-split-fancy} will return @samp{mail.spam}.
24667 (setq nnmail-split-fancy
24668 `(| (: spam-stat-split-fancy)
24672 @defvar spam-stat-split-fancy-spam-group
24673 The group to use for spam. Default is @samp{mail.spam}.
24676 If you also filter mail with specific subjects into other groups, use
24677 the following expression. Only mails not matching the regular
24678 expression are considered potential spam.
24681 (setq nnmail-split-fancy
24682 `(| ("Subject" "\\bspam-stat\\b" "mail.emacs")
24683 (: spam-stat-split-fancy)
24687 If you want to filter for spam first, then you must be careful when
24688 creating the dictionary. Note that @code{spam-stat-split-fancy} must
24689 consider both mails in @samp{mail.emacs} and in @samp{mail.misc} as
24690 non-spam, therefore both should be in your collection of non-spam
24691 mails, when creating the dictionary!
24694 (setq nnmail-split-fancy
24695 `(| (: spam-stat-split-fancy)
24696 ("Subject" "\\bspam-stat\\b" "mail.emacs")
24700 You can combine this with traditional filtering. Here, we move all
24701 HTML-only mails into the @samp{mail.spam.filtered} group. Note that since
24702 @code{spam-stat-split-fancy} will never see them, the mails in
24703 @samp{mail.spam.filtered} should be neither in your collection of spam mails,
24704 nor in your collection of non-spam mails, when creating the
24708 (setq nnmail-split-fancy
24709 `(| ("Content-Type" "text/html" "mail.spam.filtered")
24710 (: spam-stat-split-fancy)
24711 ("Subject" "\\bspam-stat\\b" "mail.emacs")
24716 @node Low-level interface to the spam-stat dictionary
24717 @subsubsection Low-level interface to the spam-stat dictionary
24719 The main interface to using @code{spam-stat}, are the following functions:
24721 @defun spam-stat-buffer-is-spam
24722 Called in a buffer, that buffer is considered to be a new spam mail.
24723 Use this for new mail that has not been processed before.
24726 @defun spam-stat-buffer-is-no-spam
24727 Called in a buffer, that buffer is considered to be a new non-spam
24728 mail. Use this for new mail that has not been processed before.
24731 @defun spam-stat-buffer-change-to-spam
24732 Called in a buffer, that buffer is no longer considered to be normal
24733 mail but spam. Use this to change the status of a mail that has
24734 already been processed as non-spam.
24737 @defun spam-stat-buffer-change-to-non-spam
24738 Called in a buffer, that buffer is no longer considered to be spam but
24739 normal mail. Use this to change the status of a mail that has already
24740 been processed as spam.
24743 @defun spam-stat-save
24744 Save the hash table to the file. The filename used is stored in the
24745 variable @code{spam-stat-file}.
24748 @defun spam-stat-load
24749 Load the hash table from a file. The filename used is stored in the
24750 variable @code{spam-stat-file}.
24753 @defun spam-stat-score-word
24754 Return the spam score for a word.
24757 @defun spam-stat-score-buffer
24758 Return the spam score for a buffer.
24761 @defun spam-stat-split-fancy
24762 Use this function for fancy mail splitting. Add the rule @samp{(:
24763 spam-stat-split-fancy)} to @code{nnmail-split-fancy}
24766 Make sure you load the dictionary before using it. This requires the
24767 following in your @file{~/.gnus.el} file:
24770 (require 'spam-stat)
24774 Typical test will involve calls to the following functions:
24777 Reset: (setq spam-stat (make-hash-table :test 'equal))
24778 Learn spam: (spam-stat-process-spam-directory "~/Mail/mail/spam")
24779 Learn non-spam: (spam-stat-process-non-spam-directory "~/Mail/mail/misc")
24780 Save table: (spam-stat-save)
24781 File size: (nth 7 (file-attributes spam-stat-file))
24782 Number of words: (hash-table-count spam-stat)
24783 Test spam: (spam-stat-test-directory "~/Mail/mail/spam")
24784 Test non-spam: (spam-stat-test-directory "~/Mail/mail/misc")
24785 Reduce table size: (spam-stat-reduce-size)
24786 Save table: (spam-stat-save)
24787 File size: (nth 7 (file-attributes spam-stat-file))
24788 Number of words: (hash-table-count spam-stat)
24789 Test spam: (spam-stat-test-directory "~/Mail/mail/spam")
24790 Test non-spam: (spam-stat-test-directory "~/Mail/mail/misc")
24793 Here is how you would create your dictionary:
24796 Reset: (setq spam-stat (make-hash-table :test 'equal))
24797 Learn spam: (spam-stat-process-spam-directory "~/Mail/mail/spam")
24798 Learn non-spam: (spam-stat-process-non-spam-directory "~/Mail/mail/misc")
24799 Repeat for any other non-spam group you need...
24800 Reduce table size: (spam-stat-reduce-size)
24801 Save table: (spam-stat-save)
24805 @section Interaction with other modes
24810 @code{gnus-dired-minor-mode} provided some useful functions for dired
24811 buffers. It is enabled with
24813 (add-hook 'dired-mode-hook 'turn-on-gnus-dired-mode)
24818 @findex gnus-dired-attach
24819 Send dired's marked files as an attachment (@code{gnus-dired-attach}).
24820 You will be prompted for a message buffer.
24823 @findex gnus-dired-find-file-mailcap
24824 Visit a file according to the appropriate mailcap entry
24825 (@code{gnus-dired-find-file-mailcap}). With prefix, open file in a new
24829 @findex gnus-dired-print
24830 Print file according to the mailcap entry (@code{gnus-dired-print}). If
24831 there is no print command, print in a PostScript image.
24834 @node Various Various
24835 @section Various Various
24841 @item gnus-home-directory
24842 @vindex gnus-home-directory
24843 All Gnus file and directory variables will be initialized from this
24844 variable, which defaults to @file{~/}.
24846 @item gnus-directory
24847 @vindex gnus-directory
24848 Most Gnus storage file and directory variables will be initialized from
24849 this variable, which defaults to the @env{SAVEDIR} environment
24850 variable, or @file{~/News/} if that variable isn't set.
24852 Note that Gnus is mostly loaded when the @file{~/.gnus.el} file is read.
24853 This means that other directory variables that are initialized from this
24854 variable won't be set properly if you set this variable in
24855 @file{~/.gnus.el}. Set this variable in @file{.emacs} instead.
24857 @item gnus-default-directory
24858 @vindex gnus-default-directory
24859 Not related to the above variable at all---this variable says what the
24860 default directory of all Gnus buffers should be. If you issue commands
24861 like @kbd{C-x C-f}, the prompt you'll get starts in the current buffer's
24862 default directory. If this variable is @code{nil} (which is the
24863 default), the default directory will be the default directory of the
24864 buffer you were in when you started Gnus.
24867 @vindex gnus-verbose
24868 This variable is an integer between zero and ten. The higher the value,
24869 the more messages will be displayed. If this variable is zero, Gnus
24870 will never flash any messages, if it is seven (which is the default),
24871 most important messages will be shown, and if it is ten, Gnus won't ever
24872 shut up, but will flash so many messages it will make your head swim.
24874 @item gnus-verbose-backends
24875 @vindex gnus-verbose-backends
24876 This variable works the same way as @code{gnus-verbose}, but it applies
24877 to the Gnus back ends instead of Gnus proper.
24879 @item nnheader-max-head-length
24880 @vindex nnheader-max-head-length
24881 When the back ends read straight heads of articles, they all try to read
24882 as little as possible. This variable (default 4096) specifies
24883 the absolute max length the back ends will try to read before giving up
24884 on finding a separator line between the head and the body. If this
24885 variable is @code{nil}, there is no upper read bound. If it is
24886 @code{t}, the back ends won't try to read the articles piece by piece,
24887 but read the entire articles. This makes sense with some versions of
24888 @code{ange-ftp} or @code{efs}.
24890 @item nnheader-head-chop-length
24891 @vindex nnheader-head-chop-length
24892 This variable (default 2048) says how big a piece of each article to
24893 read when doing the operation described above.
24895 @item nnheader-file-name-translation-alist
24896 @vindex nnheader-file-name-translation-alist
24898 @cindex invalid characters in file names
24899 @cindex characters in file names
24900 This is an alist that says how to translate characters in file names.
24901 For instance, if @samp{:} is invalid as a file character in file names
24902 on your system (you OS/2 user you), you could say something like:
24906 (setq nnheader-file-name-translation-alist
24911 In fact, this is the default value for this variable on OS/2 and MS
24912 Windows (phooey) systems.
24914 @item gnus-hidden-properties
24915 @vindex gnus-hidden-properties
24916 This is a list of properties to use to hide ``invisible'' text. It is
24917 @code{(invisible t intangible t)} by default on most systems, which
24918 makes invisible text invisible and intangible.
24920 @item gnus-parse-headers-hook
24921 @vindex gnus-parse-headers-hook
24922 A hook called before parsing headers. It can be used, for instance, to
24923 gather statistics on the headers fetched, or perhaps you'd like to prune
24924 some headers. I don't see why you'd want that, though.
24926 @item gnus-shell-command-separator
24927 @vindex gnus-shell-command-separator
24928 String used to separate two shell commands. The default is @samp{;}.
24930 @item gnus-invalid-group-regexp
24931 @vindex gnus-invalid-group-regexp
24933 Regexp to match ``invalid'' group names when querying user for a group
24934 name. The default value catches some @strong{really} invalid group
24935 names who could possibly mess up Gnus internally (like allowing
24936 @samp{:} in a group name, which is normally used to delimit method and
24939 @acronym{IMAP} users might want to allow @samp{/} in group names though.
24947 Well, that's the manual---you can get on with your life now. Keep in
24948 touch. Say hello to your cats from me.
24950 My @strong{ghod}---I just can't stand goodbyes. Sniffle.
24952 Ol' Charles Reznikoff said it pretty well, so I leave the floor to him:
24958 Not because of victories @*
24961 but for the common sunshine,@*
24963 the largess of the spring.
24967 but for the day's work done@*
24968 as well as I was able;@*
24969 not for a seat upon the dais@*
24970 but at the common table.@*
24975 @chapter Appendices
24978 * XEmacs:: Requirements for installing under XEmacs.
24979 * History:: How Gnus got where it is today.
24980 * On Writing Manuals:: Why this is not a beginner's guide.
24981 * Terminology:: We use really difficult, like, words here.
24982 * Customization:: Tailoring Gnus to your needs.
24983 * Troubleshooting:: What you might try if things do not work.
24984 * Gnus Reference Guide:: Rilly, rilly technical stuff.
24985 * Emacs for Heathens:: A short introduction to Emacsian terms.
24986 * Frequently Asked Questions:: The Gnus FAQ
24993 @cindex installing under XEmacs
24995 XEmacs is distributed as a collection of packages. You should install
24996 whatever packages the Gnus XEmacs package requires. The current
24997 requirements are @samp{gnus}, @samp{mail-lib}, @samp{xemacs-base},
24998 @samp{eterm}, @samp{sh-script}, @samp{net-utils}, @samp{os-utils},
24999 @samp{dired}, @samp{mh-e}, @samp{sieve}, @samp{ps-print}, @samp{w3},
25000 @samp{pgg}, @samp{mailcrypt}, @samp{ecrypto}, and @samp{sasl}.
25007 @sc{gnus} was written by Masanobu @sc{Umeda}. When autumn crept up in
25008 '94, Lars Magne Ingebrigtsen grew bored and decided to rewrite Gnus.
25010 If you want to investigate the person responsible for this outrage,
25011 you can point your (feh!) web browser to
25012 @uref{http://quimby.gnus.org/}. This is also the primary
25013 distribution point for the new and spiffy versions of Gnus, and is
25014 known as The Site That Destroys Newsrcs And Drives People Mad.
25016 During the first extended alpha period of development, the new Gnus was
25017 called ``(ding) Gnus''. @dfn{(ding)} is, of course, short for
25018 @dfn{ding is not Gnus}, which is a total and utter lie, but who cares?
25019 (Besides, the ``Gnus'' in this abbreviation should probably be
25020 pronounced ``news'' as @sc{Umeda} intended, which makes it a more
25021 appropriate name, don't you think?)
25023 In any case, after spending all that energy on coming up with a new and
25024 spunky name, we decided that the name was @emph{too} spunky, so we
25025 renamed it back again to ``Gnus''. But in mixed case. ``Gnus'' vs.
25026 ``@sc{gnus}''. New vs. old.
25029 * Gnus Versions:: What Gnus versions have been released.
25030 * Other Gnus Versions:: Other Gnus versions that also have been released.
25031 * Why?:: What's the point of Gnus?
25032 * Compatibility:: Just how compatible is Gnus with @sc{gnus}?
25033 * Conformity:: Gnus tries to conform to all standards.
25034 * Emacsen:: Gnus can be run on a few modern Emacsen.
25035 * Gnus Development:: How Gnus is developed.
25036 * Contributors:: Oodles of people.
25037 * New Features:: Pointers to some of the new stuff in Gnus.
25041 @node Gnus Versions
25042 @subsection Gnus Versions
25044 @cindex September Gnus
25046 @cindex Quassia Gnus
25047 @cindex Pterodactyl Gnus
25050 @cindex Gnus versions
25052 The first ``proper'' release of Gnus 5 was done in November 1995 when it
25053 was included in the Emacs 19.30 distribution (132 (ding) Gnus releases
25054 plus 15 Gnus 5.0 releases).
25056 In May 1996 the next Gnus generation (aka. ``September Gnus'' (after 99
25057 releases)) was released under the name ``Gnus 5.2'' (40 releases).
25059 On July 28th 1996 work on Red Gnus was begun, and it was released on
25060 January 25th 1997 (after 84 releases) as ``Gnus 5.4'' (67 releases).
25062 On September 13th 1997, Quassia Gnus was started and lasted 37 releases.
25063 If was released as ``Gnus 5.6'' on March 8th 1998 (46 releases).
25065 Gnus 5.6 begat Pterodactyl Gnus on August 29th 1998 and was released as
25066 ``Gnus 5.8'' (after 99 releases and a CVS repository) on December 3rd
25069 On the 26th of October 2000, Oort Gnus was begun.
25071 If you happen upon a version of Gnus that has a prefixed name --
25072 ``(ding) Gnus'', ``September Gnus'', ``Red Gnus'', ``Quassia Gnus'',
25073 ``Pterodactyl Gnus'', ``Oort Gnus'' -- don't panic. Don't let it know
25074 that you're frightened. Back away. Slowly. Whatever you do, don't
25075 run. Walk away, calmly, until you're out of its reach. Find a proper
25076 released version of Gnus and snuggle up to that instead.
25079 @node Other Gnus Versions
25080 @subsection Other Gnus Versions
25083 In addition to the versions of Gnus which have had their releases
25084 coordinated by Lars, one major development has been Semi-gnus from
25085 Japan. It's based on a library called @acronym{SEMI}, which provides
25086 @acronym{MIME} capabilities.
25088 These Gnusae are based mainly on Gnus 5.6 and Pterodactyl Gnus.
25089 Collectively, they are called ``Semi-gnus'', and different strains are
25090 called T-gnus, ET-gnus, Nana-gnus and Chaos. These provide powerful
25091 @acronym{MIME} and multilingualization things, especially important for
25098 What's the point of Gnus?
25100 I want to provide a ``rad'', ``happening'', ``way cool'' and ``hep''
25101 newsreader, that lets you do anything you can think of. That was my
25102 original motivation, but while working on Gnus, it has become clear to
25103 me that this generation of newsreaders really belong in the stone age.
25104 Newsreaders haven't developed much since the infancy of the net. If the
25105 volume continues to rise with the current rate of increase, all current
25106 newsreaders will be pretty much useless. How do you deal with
25107 newsgroups that have thousands of new articles each day? How do you
25108 keep track of millions of people who post?
25110 Gnus offers no real solutions to these questions, but I would very much
25111 like to see Gnus being used as a testing ground for new methods of
25112 reading and fetching news. Expanding on @sc{Umeda}-san's wise decision
25113 to separate the newsreader from the back ends, Gnus now offers a simple
25114 interface for anybody who wants to write new back ends for fetching mail
25115 and news from different sources. I have added hooks for customizations
25116 everywhere I could imagine it being useful. By doing so, I'm inviting
25117 every one of you to explore and invent.
25119 May Gnus never be complete. @kbd{C-u 100 M-x all-hail-emacs} and
25120 @kbd{C-u 100 M-x all-hail-xemacs}.
25123 @node Compatibility
25124 @subsection Compatibility
25126 @cindex compatibility
25127 Gnus was designed to be fully compatible with @sc{gnus}. Almost all key
25128 bindings have been kept. More key bindings have been added, of course,
25129 but only in one or two obscure cases have old bindings been changed.
25134 @center In a cloud bones of steel.
25138 All commands have kept their names. Some internal functions have changed
25141 The @code{gnus-uu} package has changed drastically. @xref{Decoding
25144 One major compatibility question is the presence of several summary
25145 buffers. All variables relevant while reading a group are
25146 buffer-local to the summary buffer they belong in. Although many
25147 important variables have their values copied into their global
25148 counterparts whenever a command is executed in the summary buffer, this
25149 change might lead to incorrect values being used unless you are careful.
25151 All code that relies on knowledge of @sc{gnus} internals will probably
25152 fail. To take two examples: Sorting @code{gnus-newsrc-alist} (or
25153 changing it in any way, as a matter of fact) is strictly verboten. Gnus
25154 maintains a hash table that points to the entries in this alist (which
25155 speeds up many functions), and changing the alist directly will lead to
25159 @cindex highlighting
25160 Old hilit19 code does not work at all. In fact, you should probably
25161 remove all hilit code from all Gnus hooks
25162 (@code{gnus-group-prepare-hook} and @code{gnus-summary-prepare-hook}).
25163 Gnus provides various integrated functions for highlighting. These are
25164 faster and more accurate. To make life easier for everybody, Gnus will
25165 by default remove all hilit calls from all hilit hooks. Uncleanliness!
25168 Packages like @code{expire-kill} will no longer work. As a matter of
25169 fact, you should probably remove all old @sc{gnus} packages (and other
25170 code) when you start using Gnus. More likely than not, Gnus already
25171 does what you have written code to make @sc{gnus} do. (Snicker.)
25173 Even though old methods of doing things are still supported, only the
25174 new methods are documented in this manual. If you detect a new method of
25175 doing something while reading this manual, that does not mean you have
25176 to stop doing it the old way.
25178 Gnus understands all @sc{gnus} startup files.
25180 @kindex M-x gnus-bug
25182 @cindex reporting bugs
25184 Overall, a casual user who hasn't written much code that depends on
25185 @sc{gnus} internals should suffer no problems. If problems occur,
25186 please let me know by issuing that magic command @kbd{M-x gnus-bug}.
25188 @vindex gnus-bug-create-help-buffer
25189 If you are in the habit of sending bug reports @emph{very} often, you
25190 may find the helpful help buffer annoying after a while. If so, set
25191 @code{gnus-bug-create-help-buffer} to @code{nil} to avoid having it pop
25196 @subsection Conformity
25198 No rebels without a clue here, ma'am. We conform to all standards known
25199 to (wo)man. Except for those standards and/or conventions we disagree
25207 There are no known breaches of this standard.
25211 There are no known breaches of this standard, either.
25213 @item Son-of-RFC 1036
25214 @cindex Son-of-RFC 1036
25215 We do have some breaches to this one.
25221 These are considered to be ``vanity headers'', while I consider them
25222 to be consumer information. After seeing so many badly formatted
25223 articles coming from @code{tin} and @code{Netscape} I know not to use
25224 either of those for posting articles. I would not have known that if
25225 it wasn't for the @code{X-Newsreader} header.
25230 USEFOR is an IETF working group writing a successor to RFC 1036, based
25231 on Son-of-RFC 1036. They have produced a number of drafts proposing
25232 various changes to the format of news articles. The Gnus towers will
25233 look into implementing the changes when the draft is accepted as an RFC.
25235 @item MIME - RFC 2045-2049 etc
25236 @cindex @acronym{MIME}
25237 All the various @acronym{MIME} RFCs are supported.
25239 @item Disposition Notifications - RFC 2298
25240 Message Mode is able to request notifications from the receiver.
25242 @item PGP - RFC 1991 and RFC 2440
25245 RFC 1991 is the original @acronym{PGP} message specification,
25246 published as an informational RFC. RFC 2440 was the follow-up, now
25247 called Open PGP, and put on the Standards Track. Both document a
25248 non-@acronym{MIME} aware @acronym{PGP} format. Gnus supports both
25249 encoding (signing and encryption) and decoding (verification and
25252 @item PGP/MIME - RFC 2015/3156
25253 RFC 2015 (superseded by 3156 which references RFC 2440 instead of RFC
25254 1991) describes the @acronym{MIME}-wrapping around the RF 1991/2440 format.
25255 Gnus supports both encoding and decoding.
25257 @item S/MIME - RFC 2633
25258 RFC 2633 describes the @acronym{S/MIME} format.
25260 @item IMAP - RFC 1730/2060, RFC 2195, RFC 2086, RFC 2359, RFC 2595, RFC 1731
25261 RFC 1730 is @acronym{IMAP} version 4, updated somewhat by RFC 2060
25262 (@acronym{IMAP} 4 revision 1). RFC 2195 describes CRAM-MD5
25263 authentication for @acronym{IMAP}. RFC 2086 describes access control
25264 lists (ACLs) for @acronym{IMAP}. RFC 2359 describes a @acronym{IMAP}
25265 protocol enhancement. RFC 2595 describes the proper @acronym{TLS}
25266 integration (STARTTLS) with @acronym{IMAP}. RFC 1731 describes the
25267 GSSAPI/Kerberos4 mechanisms for @acronym{IMAP}.
25271 If you ever notice Gnus acting non-compliant with regards to the texts
25272 mentioned above, don't hesitate to drop a note to Gnus Towers and let us
25277 @subsection Emacsen
25283 Gnus should work on:
25291 XEmacs 21.4 and up.
25295 This Gnus version will absolutely not work on any Emacsen older than
25296 that. Not reliably, at least. Older versions of Gnus may work on older
25299 There are some vague differences between Gnus on the various
25300 platforms---XEmacs features more graphics (a logo and a toolbar)---but
25301 other than that, things should look pretty much the same under all
25305 @node Gnus Development
25306 @subsection Gnus Development
25308 Gnus is developed in a two-phased cycle. The first phase involves much
25309 discussion on the @samp{ding@@gnus.org} mailing list, where people
25310 propose changes and new features, post patches and new back ends. This
25311 phase is called the @dfn{alpha} phase, since the Gnusae released in this
25312 phase are @dfn{alpha releases}, or (perhaps more commonly in other
25313 circles) @dfn{snapshots}. During this phase, Gnus is assumed to be
25314 unstable and should not be used by casual users. Gnus alpha releases
25315 have names like ``Red Gnus'' and ``Quassia Gnus''.
25317 After futzing around for 50-100 alpha releases, Gnus is declared
25318 @dfn{frozen}, and only bug fixes are applied. Gnus loses the prefix,
25319 and is called things like ``Gnus 5.6.32'' instead. Normal people are
25320 supposed to be able to use these, and these are mostly discussed on the
25321 @samp{gnu.emacs.gnus} newsgroup.
25324 @vindex mail-source-delete-incoming
25325 Some variable defaults differ between alpha Gnusae and released Gnusae.
25326 In particular, @code{mail-source-delete-incoming} defaults to @code{nil} in
25327 alpha Gnusae and @code{t} in released Gnusae. This is to prevent
25328 lossage of mail if an alpha release hiccups while handling the mail.
25330 The division of discussion between the ding mailing list and the Gnus
25331 newsgroup is not purely based on publicity concerns. It's true that
25332 having people write about the horrible things that an alpha Gnus release
25333 can do (sometimes) in a public forum may scare people off, but more
25334 importantly, talking about new experimental features that have been
25335 introduced may confuse casual users. New features are frequently
25336 introduced, fiddled with, and judged to be found wanting, and then
25337 either discarded or totally rewritten. People reading the mailing list
25338 usually keep up with these rapid changes, while people on the newsgroup
25339 can't be assumed to do so.
25344 @subsection Contributors
25345 @cindex contributors
25347 The new Gnus version couldn't have been done without the help of all the
25348 people on the (ding) mailing list. Every day for over a year I have
25349 gotten billions of nice bug reports from them, filling me with joy,
25350 every single one of them. Smooches. The people on the list have been
25351 tried beyond endurance, what with my ``oh, that's a neat idea <type
25352 type>, yup, I'll release it right away <ship off> no wait, that doesn't
25353 work at all <type type>, yup, I'll ship that one off right away <ship
25354 off> no, wait, that absolutely does not work'' policy for releases.
25355 Micro$oft---bah. Amateurs. I'm @emph{much} worse. (Or is that
25356 ``worser''? ``much worser''? ``worsest''?)
25358 I would like to take this opportunity to thank the Academy for@dots{} oops,
25364 Masanobu @sc{Umeda}---the writer of the original @sc{gnus}.
25367 Shenghuo Zhu---uudecode.el, mm-uu.el, rfc1843.el, webmail.el,
25368 nnwarchive and many, many other things connected with @acronym{MIME} and
25369 other types of en/decoding, as well as general bug fixing, new
25370 functionality and stuff.
25373 Per Abrahamsen---custom, scoring, highlighting and @sc{soup} code (as
25374 well as numerous other things).
25377 Luis Fernandes---design and graphics.
25380 Joe Reiss---creator of the smiley faces.
25383 Justin Sheehy---the @acronym{FAQ} maintainer.
25386 Erik Naggum---help, ideas, support, code and stuff.
25389 Wes Hardaker---@file{gnus-picon.el} and the manual section on
25390 @dfn{picons} (@pxref{Picons}).
25393 Kim-Minh Kaplan---further work on the picon code.
25396 Brad Miller---@file{gnus-gl.el} and the GroupLens manual section.
25399 Sudish Joseph---innumerable bug fixes.
25402 Ilja Weis---@file{gnus-topic.el}.
25405 Steven L. Baur---lots and lots and lots of bugs detections and fixes.
25408 Vladimir Alexiev---the refcard and reference booklets.
25411 Felix Lee & Jamie Zawinski---I stole some pieces from the XGnus
25412 distribution by Felix Lee and JWZ.
25415 Scott Byer---@file{nnfolder.el} enhancements & rewrite.
25418 Peter Mutsaers---orphan article scoring code.
25421 Ken Raeburn---POP mail support.
25424 Hallvard B Furuseth---various bits and pieces, especially dealing with
25428 Brian Edmonds---@file{gnus-bbdb.el}.
25431 David Moore---rewrite of @file{nnvirtual.el} and many other things.
25434 Kevin Davidson---came up with the name @dfn{ding}, so blame him.
25437 Fran@,{c}ois Pinard---many, many interesting and thorough bug reports, as
25438 well as autoconf support.
25442 This manual was proof-read by Adrian Aichner, with Ricardo Nassif, Mark
25443 Borges, and Jost Krieger proof-reading parts of the manual.
25445 The following people have contributed many patches and suggestions:
25460 Jason L. Tibbitts, III,
25462 Katsumi Yamaoka, @c Yamaoka
25466 Also thanks to the following for patches and stuff:
25476 Alexei V. Barantsev,
25491 Massimo Campostrini,
25496 Jae-you Chung, @c ?
25497 James H. Cloos, Jr.,
25501 Andrew J. Cosgriff,
25504 Geoffrey T. Dairiki,
25510 Michael Welsh Duggan,
25515 Enami Tsugutomo, @c Enami
25519 Nelson Jose dos Santos Ferreira,
25527 Arne Georg Gleditsch,
25529 Michelangelo Grigni,
25533 Kenichi Handa, @c Handa
25535 Yoshiki Hayashi, @c Hayashi
25537 Hisashige Kenji, @c Hisashige
25544 Fran@,{c}ois Felix Ingrand,
25545 Tatsuya Ichikawa, @c Ichikawa
25546 Ishikawa Ichiro, @c Ishikawa
25548 Iwamuro Motonori, @c Iwamuro
25558 Peter Skov Knudsen,
25559 Shuhei Kobayashi, @c Kobayashi
25561 Koseki Yoshinori, @c Koseki
25562 Thor Kristoffersen,
25565 Seokchan Lee, @c Lee
25583 Morioka Tomohiko, @c Morioka
25584 Erik Toubro Nielsen,
25591 Masaharu Onishi, @c Onishi
25596 Jens-Ulrik Holger Petersen,
25600 John McClary Prevost,
25606 Lars Balker Rasmussen,
25611 Christian von Roques,
25614 Wolfgang Rupprecht,
25621 Philippe Schnoebelen,
25623 Randal L. Schwartz,
25637 Kiyokazu Suto, @c Suto
25642 Tozawa Akihiko, @c Tozawa
25662 For a full overview of what each person has done, the ChangeLogs
25663 included in the Gnus alpha distributions should give ample reading
25664 (550kB and counting).
25666 Apologies to everybody that I've forgotten, of which there are many, I'm
25669 Gee, that's quite a list of people. I guess that must mean that there
25670 actually are people who are using Gnus. Who'd'a thunk it!
25674 @subsection New Features
25675 @cindex new features
25678 * ding Gnus:: New things in Gnus 5.0/5.1, the first new Gnus.
25679 * September Gnus:: The Thing Formally Known As Gnus 5.2/5.3.
25680 * Red Gnus:: Third time best---Gnus 5.4/5.5.
25681 * Quassia Gnus:: Two times two is four, or Gnus 5.6/5.7.
25682 * Pterodactyl Gnus:: Pentad also starts with P, AKA Gnus 5.8/5.9.
25683 * Oort Gnus:: It's big. It's far out. Gnus 5.10/5.11.
25684 * No Gnus:: Lars, FIXME!
25687 These lists are, of course, just @emph{short} overviews of the
25688 @emph{most} important new features. No, really. There are tons more.
25689 Yes, we have feeping creaturism in full effect.
25692 @subsubsection (ding) Gnus
25694 New features in Gnus 5.0/5.1:
25699 The look of all buffers can be changed by setting format-like variables
25700 (@pxref{Group Buffer Format} and @pxref{Summary Buffer Format}).
25703 Local spool and several @acronym{NNTP} servers can be used at once
25704 (@pxref{Select Methods}).
25707 You can combine groups into virtual groups (@pxref{Virtual Groups}).
25710 You can read a number of different mail formats (@pxref{Getting Mail}).
25711 All the mail back ends implement a convenient mail expiry scheme
25712 (@pxref{Expiring Mail}).
25715 Gnus can use various strategies for gathering threads that have lost
25716 their roots (thereby gathering loose sub-threads into one thread) or it
25717 can go back and retrieve enough headers to build a complete thread
25718 (@pxref{Customizing Threading}).
25721 Killed groups can be displayed in the group buffer, and you can read
25722 them as well (@pxref{Listing Groups}).
25725 Gnus can do partial group updates---you do not have to retrieve the
25726 entire active file just to check for new articles in a few groups
25727 (@pxref{The Active File}).
25730 Gnus implements a sliding scale of subscribedness to groups
25731 (@pxref{Group Levels}).
25734 You can score articles according to any number of criteria
25735 (@pxref{Scoring}). You can even get Gnus to find out how to score
25736 articles for you (@pxref{Adaptive Scoring}).
25739 Gnus maintains a dribble buffer that is auto-saved the normal Emacs
25740 manner, so it should be difficult to lose much data on what you have
25741 read if your machine should go down (@pxref{Auto Save}).
25744 Gnus now has its own startup file (@file{~/.gnus.el}) to avoid
25745 cluttering up the @file{.emacs} file.
25748 You can set the process mark on both groups and articles and perform
25749 operations on all the marked items (@pxref{Process/Prefix}).
25752 You can grep through a subset of groups and create a group from the
25753 results (@pxref{Kibozed Groups}).
25756 You can list subsets of groups according to, well, anything
25757 (@pxref{Listing Groups}).
25760 You can browse foreign servers and subscribe to groups from those
25761 servers (@pxref{Browse Foreign Server}).
25764 Gnus can fetch articles, asynchronously, on a second connection to the
25765 server (@pxref{Asynchronous Fetching}).
25768 You can cache articles locally (@pxref{Article Caching}).
25771 The uudecode functions have been expanded and generalized
25772 (@pxref{Decoding Articles}).
25775 You can still post uuencoded articles, which was a little-known feature
25776 of @sc{gnus}' past (@pxref{Uuencoding and Posting}).
25779 Fetching parents (and other articles) now actually works without
25780 glitches (@pxref{Finding the Parent}).
25783 Gnus can fetch @acronym{FAQ}s and group descriptions (@pxref{Group Information}).
25786 Digests (and other files) can be used as the basis for groups
25787 (@pxref{Document Groups}).
25790 Articles can be highlighted and customized (@pxref{Customizing
25794 URLs and other external references can be buttonized (@pxref{Article
25798 You can do lots of strange stuff with the Gnus window & frame
25799 configuration (@pxref{Window Layout}).
25802 You can click on buttons instead of using the keyboard
25808 @node September Gnus
25809 @subsubsection September Gnus
25813 \gnusfig{-28cm}{0cm}{\epsfig{figure=ps/september,height=20cm}}
25817 New features in Gnus 5.2/5.3:
25822 A new message composition mode is used. All old customization variables
25823 for @code{mail-mode}, @code{rnews-reply-mode} and @code{gnus-msg} are
25827 Gnus is now able to generate @dfn{sparse} threads---threads where
25828 missing articles are represented by empty nodes (@pxref{Customizing
25832 (setq gnus-build-sparse-threads 'some)
25836 Outgoing articles are stored on a special archive server
25837 (@pxref{Archived Messages}).
25840 Partial thread regeneration now happens when articles are
25844 Gnus can make use of GroupLens predictions.
25847 Picons (personal icons) can be displayed under XEmacs (@pxref{Picons}).
25850 A @code{trn}-like tree buffer can be displayed (@pxref{Tree Display}).
25853 (setq gnus-use-trees t)
25857 An @code{nn}-like pick-and-read minor mode is available for the summary
25858 buffers (@pxref{Pick and Read}).
25861 (add-hook 'gnus-summary-mode-hook 'gnus-pick-mode)
25865 In binary groups you can use a special binary minor mode (@pxref{Binary
25869 Groups can be grouped in a folding topic hierarchy (@pxref{Group
25873 (add-hook 'gnus-group-mode-hook 'gnus-topic-mode)
25877 Gnus can re-send and bounce mail (@pxref{Summary Mail Commands}).
25880 Groups can now have a score, and bubbling based on entry frequency
25881 is possible (@pxref{Group Score}).
25884 (add-hook 'gnus-summary-exit-hook 'gnus-summary-bubble-group)
25888 Groups can be process-marked, and commands can be performed on
25889 groups of groups (@pxref{Marking Groups}).
25892 Caching is possible in virtual groups.
25895 @code{nndoc} now understands all kinds of digests, mail boxes, rnews
25896 news batches, ClariNet briefs collections, and just about everything
25897 else (@pxref{Document Groups}).
25900 Gnus has a new back end (@code{nnsoup}) to create/read SOUP packets
25904 The Gnus cache is much faster.
25907 Groups can be sorted according to many criteria (@pxref{Sorting
25911 New group parameters have been introduced to set list-addresses and
25912 expiry times (@pxref{Group Parameters}).
25915 All formatting specs allow specifying faces to be used
25916 (@pxref{Formatting Fonts}).
25919 There are several more commands for setting/removing/acting on process
25920 marked articles on the @kbd{M P} submap (@pxref{Setting Process Marks}).
25923 The summary buffer can be limited to show parts of the available
25924 articles based on a wide range of criteria. These commands have been
25925 bound to keys on the @kbd{/} submap (@pxref{Limiting}).
25928 Articles can be made persistent with the @kbd{*} command
25929 (@pxref{Persistent Articles}).
25932 All functions for hiding article elements are now toggles.
25935 Article headers can be buttonized (@pxref{Article Washing}).
25938 All mail back ends support fetching articles by @code{Message-ID}.
25941 Duplicate mail can now be treated properly (@pxref{Duplicates}).
25944 All summary mode commands are available directly from the article
25945 buffer (@pxref{Article Keymap}).
25948 Frames can be part of @code{gnus-buffer-configuration} (@pxref{Window
25952 Mail can be re-scanned by a daemonic process (@pxref{Daemons}).
25955 \marginpar[\mbox{}\hfill\epsfig{figure=ps/fseptember,height=5cm}]{\epsfig{figure=ps/fseptember,height=5cm}}
25960 Gnus can make use of NoCeM files to weed out spam (@pxref{NoCeM}).
25963 (setq gnus-use-nocem t)
25967 Groups can be made permanently visible (@pxref{Listing Groups}).
25970 (setq gnus-permanently-visible-groups "^nnml:")
25974 Many new hooks have been introduced to make customizing easier.
25977 Gnus respects the @code{Mail-Copies-To} header.
25980 Threads can be gathered by looking at the @code{References} header
25981 (@pxref{Customizing Threading}).
25984 (setq gnus-summary-thread-gathering-function
25985 'gnus-gather-threads-by-references)
25989 Read articles can be stored in a special backlog buffer to avoid
25990 refetching (@pxref{Article Backlog}).
25993 (setq gnus-keep-backlog 50)
25997 A clean copy of the current article is always stored in a separate
25998 buffer to allow easier treatment.
26001 Gnus can suggest where to save articles (@pxref{Saving Articles}).
26004 Gnus doesn't have to do as much prompting when saving (@pxref{Saving
26008 (setq gnus-prompt-before-saving t)
26012 @code{gnus-uu} can view decoded files asynchronously while fetching
26013 articles (@pxref{Other Decode Variables}).
26016 (setq gnus-uu-grabbed-file-functions 'gnus-uu-grab-view)
26020 Filling in the article buffer now works properly on cited text
26021 (@pxref{Article Washing}).
26024 Hiding cited text adds buttons to toggle hiding, and how much
26025 cited text to hide is now customizable (@pxref{Article Hiding}).
26028 (setq gnus-cited-lines-visible 2)
26032 Boring headers can be hidden (@pxref{Article Hiding}).
26035 Default scoring values can now be set from the menu bar.
26038 Further syntax checking of outgoing articles have been added.
26044 @subsubsection Red Gnus
26046 New features in Gnus 5.4/5.5:
26050 \gnusfig{-5.5cm}{-4cm}{\epsfig{figure=ps/red,height=20cm}}
26057 @file{nntp.el} has been totally rewritten in an asynchronous fashion.
26060 Article prefetching functionality has been moved up into
26061 Gnus (@pxref{Asynchronous Fetching}).
26064 Scoring can now be performed with logical operators like @code{and},
26065 @code{or}, @code{not}, and parent redirection (@pxref{Advanced
26069 Article washing status can be displayed in the
26070 article mode line (@pxref{Misc Article}).
26073 @file{gnus.el} has been split into many smaller files.
26076 Suppression of duplicate articles based on Message-ID can be done
26077 (@pxref{Duplicate Suppression}).
26080 (setq gnus-suppress-duplicates t)
26084 New variables for specifying what score and adapt files are to be
26085 considered home score and adapt files (@pxref{Home Score File}) have
26089 @code{nndoc} was rewritten to be easily extendable (@pxref{Document
26090 Server Internals}).
26093 Groups can inherit group parameters from parent topics (@pxref{Topic
26097 Article editing has been revamped and is now actually usable.
26100 Signatures can be recognized in more intelligent fashions
26101 (@pxref{Article Signature}).
26104 Summary pick mode has been made to look more @code{nn}-like. Line
26105 numbers are displayed and the @kbd{.} command can be used to pick
26106 articles (@code{Pick and Read}).
26109 Commands for moving the @file{.newsrc.eld} from one server to
26110 another have been added (@pxref{Changing Servers}).
26113 There's a way now to specify that ``uninteresting'' fields be suppressed
26114 when generating lines in buffers (@pxref{Advanced Formatting}).
26117 Several commands in the group buffer can be undone with @kbd{C-M-_}
26121 Scoring can be done on words using the new score type @code{w}
26122 (@pxref{Score File Format}).
26125 Adaptive scoring can be done on a Subject word-by-word basis
26126 (@pxref{Adaptive Scoring}).
26129 (setq gnus-use-adaptive-scoring '(word))
26133 Scores can be decayed (@pxref{Score Decays}).
26136 (setq gnus-decay-scores t)
26140 Scoring can be performed using a regexp on the Date header. The Date is
26141 normalized to compact ISO 8601 format first (@pxref{Score File Format}).
26144 A new command has been added to remove all data on articles from
26145 the native server (@pxref{Changing Servers}).
26148 A new command for reading collections of documents
26149 (@code{nndoc} with @code{nnvirtual} on top) has been added---@kbd{C-M-d}
26150 (@pxref{Really Various Summary Commands}).
26153 Process mark sets can be pushed and popped (@pxref{Setting Process
26157 A new mail-to-news back end makes it possible to post even when the @acronym{NNTP}
26158 server doesn't allow posting (@pxref{Mail-To-News Gateways}).
26161 A new back end for reading searches from Web search engines
26162 (@dfn{DejaNews}, @dfn{Alta Vista}, @dfn{InReference}) has been added
26163 (@pxref{Web Searches}).
26166 Groups inside topics can now be sorted using the standard sorting
26167 functions, and each topic can be sorted independently (@pxref{Topic
26171 Subsets of the groups can be sorted independently (@code{Sorting
26175 Cached articles can be pulled into the groups (@pxref{Summary Generation
26179 \marginpar[\mbox{}\hfill\epsfig{figure=ps/fred,width=3cm}]{\epsfig{figure=ps/fred,width=3cm}}
26184 Score files are now applied in a more reliable order (@pxref{Score
26188 Reports on where mail messages end up can be generated (@pxref{Splitting
26192 More hooks and functions have been added to remove junk from incoming
26193 mail before saving the mail (@pxref{Washing Mail}).
26196 Emphasized text can be properly fontisized:
26202 @subsubsection Quassia Gnus
26204 New features in Gnus 5.6:
26209 New functionality for using Gnus as an offline newsreader has been
26210 added. A plethora of new commands and modes have been added.
26211 @xref{Gnus Unplugged}, for the full story.
26214 The @code{nndraft} back end has returned, but works differently than
26215 before. All Message buffers are now also articles in the @code{nndraft}
26216 group, which is created automatically.
26219 @code{gnus-alter-header-function} can now be used to alter header
26223 @code{gnus-summary-goto-article} now accept Message-ID's.
26226 A new Message command for deleting text in the body of a message
26227 outside the region: @kbd{C-c C-v}.
26230 You can now post to component group in @code{nnvirtual} groups with
26234 @code{nntp-rlogin-program}---new variable to ease customization.
26237 @code{C-u C-c C-c} in @code{gnus-article-edit-mode} will now inhibit
26238 re-highlighting of the article buffer.
26241 New element in @code{gnus-boring-article-headers}---@code{long-to}.
26244 @kbd{M-i} symbolic prefix command. @xref{Symbolic Prefixes}, for
26248 @kbd{L} and @kbd{I} in the summary buffer now take the symbolic prefix
26249 @kbd{a} to add the score rule to the @file{all.SCORE} file.
26252 @code{gnus-simplify-subject-functions} variable to allow greater
26253 control over simplification.
26256 @kbd{A T}---new command for fetching the current thread.
26259 @kbd{/ T}---new command for including the current thread in the
26263 @kbd{M-RET} is a new Message command for breaking cited text.
26266 @samp{\\1}-expressions are now valid in @code{nnmail-split-methods}.
26269 The @code{custom-face-lookup} function has been removed.
26270 If you used this function in your initialization files, you must
26271 rewrite them to use @code{face-spec-set} instead.
26274 Canceling now uses the current select method. Symbolic prefix
26275 @kbd{a} forces normal posting method.
26278 New command to translate M******** sm*rtq**t*s into proper
26282 For easier debugging of @code{nntp}, you can set
26283 @code{nntp-record-commands} to a non-@code{nil} value.
26286 @code{nntp} now uses @file{~/.authinfo}, a @file{.netrc}-like file, for
26287 controlling where and how to send @sc{authinfo} to @acronym{NNTP} servers.
26290 A command for editing group parameters from the summary buffer
26294 A history of where mails have been split is available.
26297 A new article date command has been added---@code{article-date-iso8601}.
26300 Subjects can be simplified when threading by setting
26301 @code{gnus-score-thread-simplify}.
26304 A new function for citing in Message has been
26305 added---@code{message-cite-original-without-signature}.
26308 @code{article-strip-all-blank-lines}---new article command.
26311 A new Message command to kill to the end of the article has
26315 A minimum adaptive score can be specified by using the
26316 @code{gnus-adaptive-word-minimum} variable.
26319 The ``lapsed date'' article header can be kept continually
26320 updated by the @code{gnus-start-date-timer} command.
26323 Web listserv archives can be read with the @code{nnlistserv} back end.
26326 Old dejanews archives can now be read by @code{nnweb}.
26330 @node Pterodactyl Gnus
26331 @subsubsection Pterodactyl Gnus
26333 New features in Gnus 5.8:
26338 The mail-fetching functions have changed. See the manual for the
26339 many details. In particular, all procmail fetching variables are gone.
26341 If you used procmail like in
26344 (setq nnmail-use-procmail t)
26345 (setq nnmail-spool-file 'procmail)
26346 (setq nnmail-procmail-directory "~/mail/incoming/")
26347 (setq nnmail-procmail-suffix "\\.in")
26350 this now has changed to
26354 '((directory :path "~/mail/incoming/"
26358 @xref{Mail Source Specifiers}.
26361 Gnus is now a @acronym{MIME}-capable reader. This affects many parts of
26362 Gnus, and adds a slew of new commands. See the manual for details.
26365 Gnus has also been multilingualized. This also affects too
26366 many parts of Gnus to summarize here, and adds many new variables.
26369 @code{gnus-auto-select-first} can now be a function to be
26370 called to position point.
26373 The user can now decide which extra headers should be included in
26374 summary buffers and @acronym{NOV} files.
26377 @code{gnus-article-display-hook} has been removed. Instead, a number
26378 of variables starting with @code{gnus-treat-} have been added.
26381 The Gnus posting styles have been redone again and now works in a
26382 subtly different manner.
26385 New web-based back ends have been added: @code{nnslashdot},
26386 @code{nnwarchive} and @code{nnultimate}. nnweb has been revamped,
26387 again, to keep up with ever-changing layouts.
26390 Gnus can now read @acronym{IMAP} mail via @code{nnimap}.
26395 @subsubsection Oort Gnus
26398 New features in Gnus 5.10:
26403 @kbd{F} (@code{gnus-article-followup-with-original}) and @kbd{R}
26404 (@code{gnus-article-reply-with-original}) only yank the text in the
26405 region if the region is active.
26408 @code{gnus-group-read-ephemeral-group} can be called interactively,
26412 In draft groups, @kbd{e} is now bound to @code{gnus-draft-edit-message}.
26413 Use @kbd{B w} for @code{gnus-summary-edit-article} instead.
26416 The revised Gnus @acronym{FAQ} is included in the manual,
26417 @xref{Frequently Asked Questions}.
26420 Upgrading from previous (stable) version if you have used Oort.
26422 If you have tried Oort (the unstable Gnus branch leading to this
26423 release) but went back to a stable version, be careful when upgrading to
26424 this version. In particular, you will probably want to remove all
26425 @file{.marks} (nnml) and @file{.mrk} (nnfolder) files, so that flags are
26426 read from your @file{.newsrc.eld} instead of from the
26427 @file{.marks}/@file{.mrk} file where this release store flags. See a
26428 later entry for more information about marks. Note that downgrading
26429 isn't save in general.
26434 More buttons for URLs, mail addresses, Message-IDs, Info links, man
26435 pages and Emacs or Gnus related references. @xref{Article Buttons}. The
26436 variables @code{gnus-button-@var{*}-level} can be used to control the
26437 appearance of all article buttons. @xref{Article Button Levels}.
26442 @code{gnus-dired-minor-mode} (see @ref{Other modes}) installs key
26443 bindings in dired buffers to send a file as an attachment, open a file
26444 using the appropriate mailcap entry, and print a file using the mailcap
26448 Gnus can display RSS newsfeeds as a newsgroup. @xref{RSS}.
26451 Single-part yenc encoded attachments can be decoded.
26456 The picons code has been reimplemented to work in GNU Emacs---some of
26457 the previous options have been removed or renamed.
26459 Picons are small ``personal icons'' representing users, domain and
26460 newsgroups, which can be displayed in the Article buffer.
26464 If the new option @code{gnus-treat-body-boundary} is non-@code{nil}, a
26465 boundary line is drawn at the end of the headers.
26468 Retrieval of charters and control messages
26470 There are new commands for fetching newsgroup charters (@kbd{H c}) and
26471 control messages (@kbd{H C}).
26476 You can delay the sending of a message with @kbd{C-c C-j} in the Message
26477 buffer. The messages are delivered at specified time. This is useful
26478 for sending yourself reminders. @xref{Delayed Articles}.
26481 If @code{auto-compression-mode} is enabled, attachments are automatically
26482 decompressed when activated.
26485 If the new option @code{nnml-use-compressed-files} is non-@code{nil},
26486 the nnml back end allows compressed message files.
26489 Signed article headers (X-PGP-Sig) can be verified with @kbd{W p}.
26492 The Summary Buffer uses an arrow in the fringe to indicate the current
26493 article. Use @code{(setq gnus-summary-display-arrow nil)} to disable it.
26496 Warn about email replies to news
26498 Do you often find yourself replying to news by email by mistake? Then
26499 the new option @code{gnus-confirm-mail-reply-to-news} is just the thing for
26503 If the new option @code{gnus-summary-display-while-building} is
26504 non-@code{nil}, the summary buffer is shown and updated as it's being
26508 The new @code{recent} mark @samp{.} indicates newly arrived messages (as
26509 opposed to old but unread messages).
26512 The new option @code{gnus-gcc-mark-as-read} automatically marks
26513 Gcc articles as read.
26516 The nndoc back end now supports mailman digests and exim bounces.
26519 Gnus supports RFC 2369 mailing list headers, and adds a number of
26520 related commands in mailing list groups. @xref{Mailing List}.
26523 The Date header can be displayed in a format that can be read aloud
26524 in English. @xref{Article Date}.
26527 The envelope sender address can be customized when using Sendmail.
26528 @xref{Mail Variables, Mail Variables,, message, Message Manual}.
26531 diffs are automatically highlighted in groups matching
26532 @code{mm-uu-diff-groups-regexp}
26535 @acronym{TLS} wrapper shipped with Gnus
26537 @acronym{TLS}/@acronym{SSL} is now supported in @acronym{IMAP} and
26538 @acronym{NNTP} via @file{tls.el} and GNUTLS. The old
26539 @acronym{TLS}/@acronym{SSL} support via (external third party)
26540 @file{ssl.el} and OpenSSL still works.
26543 New @file{make.bat} for compiling and installing Gnus under MS Windows
26545 Use @file{make.bat} if you want to install Gnus under MS Windows, the
26546 first argument to the batch-program should be the directory where
26547 @file{xemacs.exe} respectively @file{emacs.exe} is located, iff you want
26548 to install Gnus after compiling it, give @file{make.bat} @code{/copy} as
26549 the second parameter.
26551 @file{make.bat} has been rewritten from scratch, it now features
26552 automatic recognition of XEmacs and GNU Emacs, generates
26553 @file{gnus-load.el}, checks if errors occur while compilation and
26554 generation of info files and reports them at the end of the build
26555 process. It now uses @code{makeinfo} if it is available and falls
26556 back to @file{infohack.el} otherwise. @file{make.bat} should now
26557 install all files which are necessary to run Gnus and be generally a
26558 complete replacement for the @code{configure; make; make install}
26559 cycle used under Unix systems.
26561 The new @file{make.bat} makes @file{make-x.bat} superfluous, so it has
26565 Support for non-@acronym{ASCII} domain names
26567 Message supports non-@acronym{ASCII} domain names in From:, To: and
26568 Cc: and will query you whether to perform encoding when you try to
26569 send a message. The variable @code{message-use-idna} controls this.
26570 Gnus will also decode non-@acronym{ASCII} domain names in From:, To:
26571 and Cc: when you view a message. The variable @code{gnus-use-idna}
26575 Better handling of Microsoft citation styles
26577 Gnus now tries to recognize the mangled header block that some Microsoft
26578 mailers use to indicate that the rest of the message is a citation, even
26579 though it is not quoted in any way. The variable
26580 @code{gnus-cite-unsightly-citation-regexp} matches the start of these
26584 @code{gnus-article-skip-boring}
26586 If you set @code{gnus-article-skip-boring} to @code{t}, then Gnus will
26587 not scroll down to show you a page that contains only boring text,
26588 which by default means cited text and signature. You can customize
26589 what is skippable using @code{gnus-article-boring-faces}.
26591 This feature is especially useful if you read many articles that
26592 consist of a little new content at the top with a long, untrimmed
26593 message cited below.
26596 The format spec @code{%C} for positioning point has changed to @code{%*}.
26599 The new variable @code{gnus-parameters} can be used to set group parameters.
26601 Earlier this was done only via @kbd{G p} (or @kbd{G c}), which stored
26602 the parameters in @file{~/.newsrc.eld}, but via this variable you can
26603 enjoy the powers of customize, and simplified backups since you set the
26604 variable in @file{~/.emacs} instead of @file{~/.newsrc.eld}. The
26605 variable maps regular expressions matching group names to group
26608 (setq gnus-parameters
26610 (gnus-show-threads nil)
26611 (gnus-use-scoring nil))
26612 ("^nnimap:\\(foo.bar\\)$"
26613 (to-group . "\\1"))))
26617 Smileys (@samp{:-)}, @samp{;-)} etc) are now iconized for Emacs too.
26619 Put @code{(setq gnus-treat-display-smileys nil)} in @file{~/.emacs} to
26623 Gnus no longer generate the Sender: header automatically.
26625 Earlier it was generated iff the user configurable email address was
26626 different from the Gnus guessed default user address. As the guessing
26627 algorithm is rarely correct these days, and (more controversially) the
26628 only use of the Sender: header was to check if you are entitled to
26629 cancel/supersede news (which is now solved by Cancel Locks instead,
26630 see another entry), generation of the header has been disabled by
26631 default. See the variables @code{message-required-headers},
26632 @code{message-required-news-headers}, and
26633 @code{message-required-mail-headers}.
26636 Features from third party @file{message-utils.el} added to @file{message.el}.
26638 Message now asks if you wish to remove @samp{(was: <old subject>)} from
26639 subject lines (see @code{message-subject-trailing-was-query}). @kbd{C-c
26640 M-m} and @kbd{C-c M-f} inserts markers indicating included text.
26641 @kbd{C-c C-f a} adds a X-No-Archive: header. @kbd{C-c C-f x} inserts
26642 appropriate headers and a note in the body for cross-postings and
26643 followups (see the variables @code{message-cross-post-@var{*}}).
26646 References and X-Draft-Headers are no longer generated when you start
26647 composing messages and @code{message-generate-headers-first} is
26651 Improved anti-spam features.
26653 Gnus is now able to take out spam from your mail and news streams
26654 using a wide variety of programs and filter rules. Among the supported
26655 methods are RBL blocklists, bogofilter and white/blacklists. Hooks
26656 for easy use of external packages such as SpamAssassin and Hashcash
26657 are also new. @xref{Thwarting Email Spam}.
26660 Easy inclusion of X-Faces headers.
26663 Face headers handling.
26666 In the summary buffer, the new command @kbd{/ N} inserts new messages
26667 and @kbd{/ o} inserts old messages.
26670 Gnus decodes morse encoded messages if you press @kbd{W m}.
26673 Unread count correct in nnimap groups.
26675 The estimated number of unread articles in the group buffer should now
26676 be correct for nnimap groups. This is achieved by calling
26677 @code{nnimap-fixup-unread-after-getting-new-news} from the
26678 @code{gnus-setup-news-hook} (called on startup) and
26679 @code{gnus-after-getting-new-news-hook}. (called after getting new
26680 mail). If you have modified those variables from the default, you may
26681 want to add @code{nnimap-fixup-unread-after-getting-new-news} again. If
26682 you were happy with the estimate and want to save some (minimal) time
26683 when getting new mail, remove the function.
26686 Group Carbon Copy (GCC) quoting
26688 To support groups that contains SPC and other weird characters, groups
26689 are quoted before they are placed in the Gcc: header. This means
26690 variables such as @code{gnus-message-archive-group} should no longer
26691 contain quote characters to make groups containing SPC work. Also, if
26692 you are using the string @samp{nnml:foo, nnml:bar} (indicating Gcc
26693 into two groups) you must change it to return the list
26694 @code{("nnml:foo" "nnml:bar")}, otherwise the Gcc: line will be quoted
26695 incorrectly. Note that returning the string @samp{nnml:foo, nnml:bar}
26696 was incorrect earlier, it just didn't generate any problems since it
26697 was inserted directly.
26700 @file{~/News/overview/} not used.
26702 As a result of the following change, the @file{~/News/overview/}
26703 directory is not used any more. You can safely delete the entire
26709 The Gnus Agent has seen a major updated and is now enabled by default,
26710 and all nntp and nnimap servers from @code{gnus-select-method} and
26711 @code{gnus-secondary-select-method} are agentized by default. Earlier
26712 only the server in @code{gnus-select-method} was agentized by the
26713 default, and the agent was disabled by default. When the agent is
26714 enabled, headers are now also retrieved from the Agent cache instead
26715 of the back ends when possible. Earlier this only happened in the
26716 unplugged state. You can enroll or remove servers with @kbd{J a} and
26717 @kbd{J r} in the server buffer. Gnus will not download articles into
26718 the Agent cache, unless you instruct it to do so, though, by using
26719 @kbd{J u} or @kbd{J s} from the Group buffer. You revert to the old
26720 behavior of having the Agent disabled with @code{(setq gnus-agent
26721 nil)}. Note that putting @code{(gnus-agentize)} in @file{~/.gnus.el}
26722 is not needed any more.
26725 @code{gnus-summary-line-format}
26727 The default value changed to @samp{%U%R%z%I%(%[%4L: %-23,23f%]%)
26728 %s\n}. Moreover @code{gnus-extra-headers},
26729 @code{nnmail-extra-headers} and @code{gnus-ignored-from-addresses}
26730 changed their default so that the users name will be replaced by the
26731 recipient's name or the group name posting to for @acronym{NNTP}
26735 @file{deuglify.el} (@code{gnus-article-outlook-deuglify-article})
26737 A new file from Raymond Scholz @email{rscholz@@zonix.de} for deuglifying
26738 broken Outlook (Express) articles.
26741 @code{(require 'gnus-load)}
26743 If you use a stand-alone Gnus distribution, you'd better add
26744 @code{(require 'gnus-load)} into your @file{~/.emacs} after adding the Gnus
26745 lisp directory into load-path.
26747 File @file{gnus-load.el} contains autoload commands, functions and variables,
26748 some of which may not be included in distributions of Emacsen.
26751 @code{gnus-slave-unplugged}
26753 A new command which starts Gnus offline in slave mode.
26756 @code{message-insinuate-rmail}
26758 Adding @code{(message-insinuate-rmail)} and @code{(setq
26759 mail-user-agent 'gnus-user-agent)} in @file{.emacs} convinces Rmail to
26760 compose, reply and forward messages in message-mode, where you can
26761 enjoy the power of @acronym{MML}.
26764 @code{message-minibuffer-local-map}
26766 The line below enables BBDB in resending a message:
26768 (define-key message-minibuffer-local-map [(tab)]
26769 'bbdb-complete-name)
26773 Externalizing and deleting of attachments.
26775 If @code{gnus-gcc-externalize-attachments} or
26776 @code{message-fcc-externalize-attachments} is non-@code{nil}, attach
26777 local files as external parts.
26779 The command @code{gnus-mime-save-part-and-strip} (bound to @kbd{C-o}
26780 on @acronym{MIME} buttons) saves a part and replaces the part with an
26781 external one. @code{gnus-mime-delete-part} (bound to @kbd{d} on
26782 @acronym{MIME} buttons) removes a part. It works only on back ends
26783 that support editing.
26786 @code{gnus-default-charset}
26788 The default value is determined from the
26789 @code{current-language-environment} variable, instead of
26790 @code{iso-8859-1}. Also the @samp{.*} item in
26791 @code{gnus-group-charset-alist} is removed.
26794 @code{gnus-posting-styles}
26796 Add a new format of match like
26798 ((header "to" "larsi.*org")
26799 (Organization "Somewhere, Inc."))
26801 The old format like the lines below is obsolete, but still accepted.
26803 (header "to" "larsi.*org"
26804 (Organization "Somewhere, Inc."))
26808 @code{message-ignored-news-headers} and @code{message-ignored-mail-headers}
26810 @samp{X-Draft-From} and @samp{X-Gnus-Agent-Meta-Information} have been
26811 added into these two variables. If you customized those, perhaps you
26812 need add those two headers too.
26815 Gnus reads the @acronym{NOV} and articles in the Agent if plugged.
26817 If one reads an article while plugged, and the article already exists
26818 in the Agent, it won't get downloaded once more. @code{(setq
26819 gnus-agent-cache nil)} reverts to the old behavior.
26822 Gnus supports the ``format=flowed'' (RFC 2646) parameter. On
26823 composing messages, it is enabled by @code{use-hard-newlines}.
26824 Decoding format=flowed was present but not documented in earlier
26828 Gnus supports the generation of RFC 2298 Disposition Notification requests.
26830 This is invoked with the @kbd{C-c M-n} key binding from message mode.
26833 Gnus supports Maildir groups.
26835 Gnus includes a new back end @file{nnmaildir.el}. @xref{Maildir}.
26838 Printing capabilities are enhanced.
26840 Gnus supports Muttprint natively with @kbd{O P} from the Summary and
26841 Article buffers. Also, each individual @acronym{MIME} part can be
26842 printed using @kbd{p} on the @acronym{MIME} button.
26845 Message supports the Importance: (RFC 2156) header.
26847 In the message buffer, @kbd{C-c C-f C-i} or @kbd{C-c C-u} cycles through
26851 Gnus supports Cancel Locks in News.
26853 This means a header @samp{Cancel-Lock} is inserted in news posting. It is
26854 used to determine if you wrote an article or not (for canceling and
26855 superseding). Gnus generates a random password string the first time
26856 you post a message, and saves it in your @file{~/.emacs} using the Custom
26857 system. While the variable is called @code{canlock-password}, it is not
26858 security sensitive data. Publishing your canlock string on the web
26859 will not allow anyone to be able to anything she could not already do.
26860 The behavior can be changed by customizing @code{message-insert-canlock}.
26863 Gnus supports server-side mail filtering using Sieve.
26865 Sieve rules can be added as Group Parameters for groups, and the
26866 complete Sieve script is generated using @kbd{D g} from the Group
26867 buffer, and then uploaded to the server using @kbd{C-c C-l} in the
26868 generated Sieve buffer. @xref{Sieve Commands}, and the new Sieve
26869 manual @ref{Top, , Top, sieve, Emacs Sieve}.
26872 Extended format specs.
26874 Format spec @samp{%&user-date;} is added into
26875 @code{gnus-summary-line-format-alist}. Also, user defined extended
26876 format specs are supported. The extended format specs look like
26877 @samp{%u&foo;}, which invokes function
26878 @code{gnus-user-format-function-@var{foo}}. Because @samp{&} is used as the
26879 escape character, old user defined format @samp{%u&} is no longer supported.
26882 @kbd{/ *} (@code{gnus-summary-limit-include-cached}) is rewritten.
26884 It was aliased to @kbd{Y c}
26885 (@code{gnus-summary-insert-cached-articles}). The new function filters
26886 out other articles.
26888 @item Some limiting commands accept a @kbd{C-u} prefix to negate the match.
26890 If @kbd{C-u} is used on subject, author or extra headers, i.e., @kbd{/
26891 s}, @kbd{/ a}, and @kbd{/ x}
26892 (@code{gnus-summary-limit-to-@{subject,author,extra@}}) respectively, the
26893 result will be to display all articles that do not match the expression.
26896 Group names are treated as UTF-8 by default.
26898 This is supposedly what USEFOR wanted to migrate to. See
26899 @code{gnus-group-name-charset-group-alist} and
26900 @code{gnus-group-name-charset-method-alist} for customization.
26903 The nnml and nnfolder back ends store marks for each groups.
26905 This makes it possible to take backup of nnml/nnfolder servers/groups
26906 separately of @file{~/.newsrc.eld}, while preserving marks. It also
26907 makes it possible to share articles and marks between users (without
26908 sharing the @file{~/.newsrc.eld} file) within e.g. a department. It
26909 works by storing the marks stored in @file{~/.newsrc.eld} in a per-group
26910 file @file{.marks} (for nnml) and @file{@var{groupname}.mrk} (for
26911 nnfolder, named @var{groupname}). If the nnml/nnfolder is moved to
26912 another machine, Gnus will automatically use the @file{.marks} or
26913 @file{.mrk} file instead of the information in @file{~/.newsrc.eld}.
26914 The new server variables @code{nnml-marks-is-evil} and
26915 @code{nnfolder-marks-is-evil} can be used to disable this feature.
26918 The menu bar item (in Group and Summary buffer) named ``Misc'' has
26919 been renamed to ``Gnus''.
26922 The menu bar item (in Message mode) named ``@acronym{MML}'' has been
26923 renamed to ``Attachments''. Note that this menu also contains security
26924 related stuff, like signing and encryption (@pxref{Security, Security,,
26925 message, Message Manual}).
26928 @code{gnus-group-charset-alist} and
26929 @code{gnus-group-ignored-charsets-alist}.
26931 The regexps in these variables are compared with full group names
26932 instead of real group names in 5.8. Users who customize these
26933 variables should change those regexps accordingly. For example:
26935 ("^han\\>" euc-kr) -> ("\\(^\\|:\\)han\\>" euc-kr)
26939 Gnus supports @acronym{PGP} (RFC 1991/2440), @acronym{PGP/MIME} (RFC
26940 2015/3156) and @acronym{S/MIME} (RFC 2630-2633).
26942 It needs an external @acronym{S/MIME} and OpenPGP implementation, but no
26943 additional Lisp libraries. This add several menu items to the
26944 Attachments menu, and @kbd{C-c RET} key bindings, when composing
26945 messages. This also obsoletes @code{gnus-article-hide-pgp-hook}.
26948 Gnus inlines external parts (message/external).
26951 @acronym{MML} (Mime compose) prefix changed from @kbd{M-m} to @kbd{C-c
26954 This change was made to avoid conflict with the standard binding of
26955 @code{back-to-indentation}, which is also useful in message mode.
26958 The default for @code{message-forward-show-mml} changed to symbol @code{best}.
26960 The behavior for the @code{best} value is to show @acronym{MML} (i.e.,
26961 convert to @acronym{MIME}) when appropriate. @acronym{MML} will not be
26962 used when forwarding signed or encrypted messages, as the conversion
26963 invalidate the digital signature.
26967 @subsubsection No Gnus
26970 New features in No Gnus:
26971 @c FIXME: Gnus 5.12?
26973 @include gnus-news.texi
26979 @section The Manual
26983 This manual was generated from a TeXinfo file and then run through
26984 either @code{texi2dvi}
26986 or my own home-brewed TeXinfo to \LaTeX\ transformer,
26987 and then run through @code{latex} and @code{dvips}
26989 to get what you hold in your hands now.
26991 The following conventions have been used:
26996 This is a @samp{string}
26999 This is a @kbd{keystroke}
27002 This is a @file{file}
27005 This is a @code{symbol}
27009 So if I were to say ``set @code{flargnoze} to @samp{yes}'', that would
27013 (setq flargnoze "yes")
27016 If I say ``set @code{flumphel} to @code{yes}'', that would mean:
27019 (setq flumphel 'yes)
27022 @samp{yes} and @code{yes} are two @emph{very} different things---don't
27023 ever get them confused.
27027 Of course, everything in this manual is of vital interest, so you should
27028 read it all. Several times. However, if you feel like skimming the
27029 manual, look for that gnu head you should see in the margin over
27030 there---it means that what's being discussed is of more importance than
27031 the rest of the stuff. (On the other hand, if everything is infinitely
27032 important, how can anything be more important than that? Just one more
27033 of the mysteries of this world, I guess.)
27039 @node On Writing Manuals
27040 @section On Writing Manuals
27042 I guess most manuals are written after-the-fact; documenting a program
27043 that's already there. This is not how this manual is written. When
27044 implementing something, I write the manual entry for that something
27045 straight away. I then see that it's difficult to explain the
27046 functionality, so I write how it's supposed to be, and then I change the
27047 implementation. Writing the documentation and writing the code goes
27050 This, of course, means that this manual has no, or little, flow. It
27051 documents absolutely everything in Gnus, but often not where you're
27052 looking for it. It is a reference manual, and not a guide to how to get
27055 That would be a totally different book, that should be written using the
27056 reference manual as source material. It would look quite differently.
27061 @section Terminology
27063 @cindex terminology
27068 This is what you are supposed to use this thing for---reading news.
27069 News is generally fetched from a nearby @acronym{NNTP} server, and is
27070 generally publicly available to everybody. If you post news, the entire
27071 world is likely to read just what you have written, and they'll all
27072 snigger mischievously. Behind your back.
27076 Everything that's delivered to you personally is mail. Some news/mail
27077 readers (like Gnus) blur the distinction between mail and news, but
27078 there is a difference. Mail is private. News is public. Mailing is
27079 not posting, and replying is not following up.
27083 Send a mail to the person who has written what you are reading.
27087 Post an article to the current newsgroup responding to the article you
27092 Gnus considers mail and news to be mostly the same, really. The only
27093 difference is how to access the actual articles. News articles are
27094 commonly fetched via the protocol @acronym{NNTP}, whereas mail
27095 messages could be read from a file on the local disk. The internal
27096 architecture of Gnus thus comprises a ``front end'' and a number of
27097 ``back ends''. Internally, when you enter a group (by hitting
27098 @key{RET}, say), you thereby invoke a function in the front end in
27099 Gnus. The front end then ``talks'' to a back end and says things like
27100 ``Give me the list of articles in the foo group'' or ``Show me article
27103 So a back end mainly defines either a protocol (the @code{nntp} back
27104 end accesses news via @acronym{NNTP}, the @code{nnimap} back end
27105 accesses mail via @acronym{IMAP}) or a file format and directory
27106 layout (the @code{nnspool} back end accesses news via the common
27107 ``spool directory'' format, the @code{nnml} back end access mail via a
27108 file format and directory layout that's quite similar).
27110 Gnus does not handle the underlying media, so to speak---this is all
27111 done by the back ends. A back end is a collection of functions to
27112 access the articles.
27114 However, sometimes the term ``back end'' is also used where ``server''
27115 would have been more appropriate. And then there is the term ``select
27116 method'' which can mean either. The Gnus terminology can be quite
27121 Gnus will always use one method (and back end) as the @dfn{native}, or
27122 default, way of getting news.
27126 You can also have any number of foreign groups active at the same time.
27127 These are groups that use non-native non-secondary back ends for getting
27132 Secondary back ends are somewhere half-way between being native and being
27133 foreign, but they mostly act like they are native.
27137 A message that has been posted as news.
27140 @cindex mail message
27141 A message that has been mailed.
27145 A mail message or news article
27149 The top part of a message, where administrative information (etc.) is
27154 The rest of an article. Everything not in the head is in the
27159 A line from the head of an article.
27163 A collection of such lines, or a collection of heads. Or even a
27164 collection of @acronym{NOV} lines.
27166 @item @acronym{NOV}
27167 @cindex @acronym{NOV}
27168 When Gnus enters a group, it asks the back end for the headers of all
27169 unread articles in the group. Most servers support the News OverView
27170 format, which is more compact and much faster to read and parse than the
27171 normal @sc{head} format.
27175 Each group is subscribed at some @dfn{level} or other (1-9). The ones
27176 that have a lower level are ``more'' subscribed than the groups with a
27177 higher level. In fact, groups on levels 1-5 are considered
27178 @dfn{subscribed}; 6-7 are @dfn{unsubscribed}; 8 are @dfn{zombies}; and 9
27179 are @dfn{killed}. Commands for listing groups and scanning for new
27180 articles will all use the numeric prefix as @dfn{working level}.
27182 @item killed groups
27183 @cindex killed groups
27184 No information on killed groups is stored or updated, which makes killed
27185 groups much easier to handle than subscribed groups.
27187 @item zombie groups
27188 @cindex zombie groups
27189 Just like killed groups, only slightly less dead.
27192 @cindex active file
27193 The news server has to keep track of what articles it carries, and what
27194 groups exist. All this information in stored in the active file, which
27195 is rather large, as you might surmise.
27198 @cindex bogus groups
27199 A group that exists in the @file{.newsrc} file, but isn't known to the
27200 server (i.e., it isn't in the active file), is a @emph{bogus group}.
27201 This means that the group probably doesn't exist (any more).
27204 @cindex activating groups
27205 The act of asking the server for info on a group and computing the
27206 number of unread articles is called @dfn{activating the group}.
27207 Un-activated groups are listed with @samp{*} in the group buffer.
27211 News servers store their articles locally in one fashion or other.
27212 One old-fashioned storage method is to have just one file per
27213 article. That's called a ``traditional spool''.
27217 A machine one can connect to and get news (or mail) from.
27219 @item select method
27220 @cindex select method
27221 A structure that specifies the back end, the server and the virtual
27224 @item virtual server
27225 @cindex virtual server
27226 A named select method. Since a select method defines all there is to
27227 know about connecting to a (physical) server, taking the thing as a
27228 whole is a virtual server.
27232 Taking a buffer and running it through a filter of some sort. The
27233 result will (more often than not) be cleaner and more pleasing than the
27236 @item ephemeral groups
27237 @cindex ephemeral groups
27238 @cindex temporary groups
27239 Most groups store data on what articles you have read. @dfn{Ephemeral}
27240 groups are groups that will have no data stored---when you exit the
27241 group, it'll disappear into the aether.
27244 @cindex solid groups
27245 This is the opposite of ephemeral groups. All groups listed in the
27246 group buffer are solid groups.
27248 @item sparse articles
27249 @cindex sparse articles
27250 These are article placeholders shown in the summary buffer when
27251 @code{gnus-build-sparse-threads} has been switched on.
27255 To put responses to articles directly after the articles they respond
27256 to---in a hierarchical fashion.
27260 @cindex thread root
27261 The first article in a thread is the root. It is the ancestor of all
27262 articles in the thread.
27266 An article that has responses.
27270 An article that responds to a different article---its parent.
27274 A collection of messages in one file. The most common digest format is
27275 specified by RFC 1153.
27278 @cindex splitting, terminolgy
27279 @cindex mail sorting
27280 @cindex mail filtering (splitting)
27281 The action of sorting your emails according to certain rules. Sometimes
27282 incorrectly called mail filtering.
27288 @node Customization
27289 @section Customization
27290 @cindex general customization
27292 All variables are properly documented elsewhere in this manual. This
27293 section is designed to give general pointers on how to customize Gnus
27294 for some quite common situations.
27297 * Slow/Expensive Connection:: You run a local Emacs and get the news elsewhere.
27298 * Slow Terminal Connection:: You run a remote Emacs.
27299 * Little Disk Space:: You feel that having large setup files is icky.
27300 * Slow Machine:: You feel like buying a faster machine.
27304 @node Slow/Expensive Connection
27305 @subsection Slow/Expensive NNTP Connection
27307 If you run Emacs on a machine locally, and get your news from a machine
27308 over some very thin strings, you want to cut down on the amount of data
27309 Gnus has to get from the @acronym{NNTP} server.
27313 @item gnus-read-active-file
27314 Set this to @code{nil}, which will inhibit Gnus from requesting the
27315 entire active file from the server. This file is often very large. You
27316 also have to set @code{gnus-check-new-newsgroups} and
27317 @code{gnus-check-bogus-newsgroups} to @code{nil} to make sure that Gnus
27318 doesn't suddenly decide to fetch the active file anyway.
27320 @item gnus-nov-is-evil
27321 This one has to be @code{nil}. If not, grabbing article headers from
27322 the @acronym{NNTP} server will not be very fast. Not all @acronym{NNTP} servers
27323 support @sc{xover}; Gnus will detect this by itself.
27327 @node Slow Terminal Connection
27328 @subsection Slow Terminal Connection
27330 Let's say you use your home computer for dialing up the system that runs
27331 Emacs and Gnus. If your modem is slow, you want to reduce (as much as
27332 possible) the amount of data sent over the wires.
27336 @item gnus-auto-center-summary
27337 Set this to @code{nil} to inhibit Gnus from re-centering the summary
27338 buffer all the time. If it is @code{vertical}, do only vertical
27339 re-centering. If it is neither @code{nil} nor @code{vertical}, do both
27340 horizontal and vertical recentering.
27342 @item gnus-visible-headers
27343 Cut down on the headers included in the articles to the
27344 minimum. You can, in fact, make do without them altogether---most of the
27345 useful data is in the summary buffer, anyway. Set this variable to
27346 @samp{^NEVVVVER} or @samp{From:}, or whatever you feel you need.
27348 Set this hook to all the available hiding commands:
27350 (setq gnus-treat-hide-headers 'head
27351 gnus-treat-hide-signature t
27352 gnus-treat-hide-citation t)
27355 @item gnus-use-full-window
27356 By setting this to @code{nil}, you can make all the windows smaller.
27357 While this doesn't really cut down much generally, it means that you
27358 have to see smaller portions of articles before deciding that you didn't
27359 want to read them anyway.
27361 @item gnus-thread-hide-subtree
27362 If this is non-@code{nil}, all threads in the summary buffer will be
27366 @item gnus-updated-mode-lines
27367 If this is @code{nil}, Gnus will not put information in the buffer mode
27368 lines, which might save some time.
27372 @node Little Disk Space
27373 @subsection Little Disk Space
27376 The startup files can get rather large, so you may want to cut their
27377 sizes a bit if you are running out of space.
27381 @item gnus-save-newsrc-file
27382 If this is @code{nil}, Gnus will never save @file{.newsrc}---it will
27383 only save @file{.newsrc.eld}. This means that you will not be able to
27384 use any other newsreaders than Gnus. This variable is @code{t} by
27387 @item gnus-read-newsrc-file
27388 If this is @code{nil}, Gnus will never read @file{.newsrc}---it will
27389 only read @file{.newsrc.eld}. This means that you will not be able to
27390 use any other newsreaders than Gnus. This variable is @code{t} by
27393 @item gnus-save-killed-list
27394 If this is @code{nil}, Gnus will not save the list of dead groups. You
27395 should also set @code{gnus-check-new-newsgroups} to @code{ask-server}
27396 and @code{gnus-check-bogus-newsgroups} to @code{nil} if you set this
27397 variable to @code{nil}. This variable is @code{t} by default.
27403 @subsection Slow Machine
27404 @cindex slow machine
27406 If you have a slow machine, or are just really impatient, there are a
27407 few things you can do to make Gnus run faster.
27409 Set @code{gnus-check-new-newsgroups} and
27410 @code{gnus-check-bogus-newsgroups} to @code{nil} to make startup faster.
27412 Set @code{gnus-show-threads}, @code{gnus-use-cross-reference} and
27413 @code{gnus-nov-is-evil} to @code{nil} to make entering and exiting the
27414 summary buffer faster.
27418 @node Troubleshooting
27419 @section Troubleshooting
27420 @cindex troubleshooting
27422 Gnus works @emph{so} well straight out of the box---I can't imagine any
27430 Make sure your computer is switched on.
27433 Make sure that you really load the current Gnus version. If you have
27434 been running @sc{gnus}, you need to exit Emacs and start it up again before
27438 Try doing an @kbd{M-x gnus-version}. If you get something that looks
27439 like @samp{Gnus v5.10.6} you have the right files loaded. Otherwise
27440 you have some old @file{.el} files lying around. Delete these.
27443 Read the help group (@kbd{G h} in the group buffer) for a
27444 @acronym{FAQ} and a how-to.
27447 @vindex max-lisp-eval-depth
27448 Gnus works on many recursive structures, and in some extreme (and very
27449 rare) cases Gnus may recurse down ``too deeply'' and Emacs will beep at
27450 you. If this happens to you, set @code{max-lisp-eval-depth} to 500 or
27451 something like that.
27454 If all else fails, report the problem as a bug.
27457 @cindex reporting bugs
27459 @kindex M-x gnus-bug
27461 If you find a bug in Gnus, you can report it with the @kbd{M-x gnus-bug}
27462 command. @kbd{M-x set-variable RET debug-on-error RET t RET}, and send
27463 me the backtrace. I will fix bugs, but I can only fix them if you send
27464 me a precise description as to how to reproduce the bug.
27466 You really can never be too detailed in a bug report. Always use the
27467 @kbd{M-x gnus-bug} command when you make bug reports, even if it creates
27468 a 10Kb mail each time you use it, and even if you have sent me your
27469 environment 500 times before. I don't care. I want the full info each
27472 It is also important to remember that I have no memory whatsoever. If
27473 you send a bug report, and I send you a reply, and then you just send
27474 back ``No, it's not! Moron!'', I will have no idea what you are
27475 insulting me about. Always over-explain everything. It's much easier
27476 for all of us---if I don't have all the information I need, I will just
27477 mail you and ask for more info, and everything takes more time.
27479 If the problem you're seeing is very visual, and you can't quite explain
27480 it, copy the Emacs window to a file (with @code{xwd}, for instance), put
27481 it somewhere it can be reached, and include the URL of the picture in
27485 If you would like to contribute a patch to fix bugs or make
27486 improvements, please produce the patch using @samp{diff -u}.
27489 If you want to debug your problem further before reporting, possibly
27490 in order to solve the problem yourself and send a patch, you can use
27491 edebug. Debugging Lisp code is documented in the Elisp manual
27492 (@pxref{Debugging, , Debugging Lisp Programs, elisp, The GNU Emacs
27493 Lisp Reference Manual}). To get you started with edebug, consider if
27494 you discover some weird behavior when pressing @kbd{c}, the first
27495 step is to do @kbd{C-h k c} and click on the hyperlink (Emacs only) in
27496 the documentation buffer that leads you to the function definition,
27497 then press @kbd{M-x edebug-defun RET} with point inside that function,
27498 return to Gnus and press @kbd{c} to invoke the code. You will be
27499 placed in the lisp buffer and can single step using @kbd{SPC} and
27500 evaluate expressions using @kbd{M-:} or inspect variables using
27501 @kbd{C-h v}, abort execution with @kbd{q}, and resume execution with
27502 @kbd{c} or @kbd{g}.
27507 Sometimes, a problem do not directly generate an elisp error but
27508 manifests itself by causing Gnus to be very slow. In these cases, you
27509 can use @kbd{M-x toggle-debug-on-quit} and press @kbd{C-g} when things are
27510 slow, and then try to analyze the backtrace (repeating the procedure
27511 helps isolating the real problem areas).
27513 A fancier approach is to use the elisp profiler, ELP. The profiler is
27514 (or should be) fully documented elsewhere, but to get you started
27515 there are a few steps that need to be followed. First, instrument the
27516 part of Gnus you are interested in for profiling, e.g. @kbd{M-x
27517 elp-instrument-package RET gnus} or @kbd{M-x elp-instrument-package
27518 RET message}. Then perform the operation that is slow and press
27519 @kbd{M-x elp-results}. You will then see which operations that takes
27520 time, and can debug them further. If the entire operation takes much
27521 longer than the time spent in the slowest function in the profiler
27522 output, you probably profiled the wrong part of Gnus. To reset
27523 profiling statistics, use @kbd{M-x elp-reset-all}. @kbd{M-x
27524 elp-restore-all} is supposed to remove profiling, but given the
27525 complexities and dynamic code generation in Gnus, it might not always
27528 @cindex gnu.emacs.gnus
27529 @cindex ding mailing list
27530 If you just need help, you are better off asking on
27531 @samp{gnu.emacs.gnus}. I'm not very helpful. You can also ask on
27532 @email{ding@@gnus.org, the ding mailing list}. Write to
27533 @email{ding-request@@gnus.org} to subscribe.
27537 @node Gnus Reference Guide
27538 @section Gnus Reference Guide
27540 It is my hope that other people will figure out smart stuff that Gnus
27541 can do, and that other people will write those smart things as well. To
27542 facilitate that I thought it would be a good idea to describe the inner
27543 workings of Gnus. And some of the not-so-inner workings, while I'm at
27546 You can never expect the internals of a program not to change, but I
27547 will be defining (in some details) the interface between Gnus and its
27548 back ends (this is written in stone), the format of the score files
27549 (ditto), data structures (some are less likely to change than others)
27550 and general methods of operation.
27553 * Gnus Utility Functions:: Common functions and variable to use.
27554 * Back End Interface:: How Gnus communicates with the servers.
27555 * Score File Syntax:: A BNF definition of the score file standard.
27556 * Headers:: How Gnus stores headers internally.
27557 * Ranges:: A handy format for storing mucho numbers.
27558 * Group Info:: The group info format.
27559 * Extended Interactive:: Symbolic prefixes and stuff.
27560 * Emacs/XEmacs Code:: Gnus can be run under all modern Emacsen.
27561 * Various File Formats:: Formats of files that Gnus use.
27565 @node Gnus Utility Functions
27566 @subsection Gnus Utility Functions
27567 @cindex Gnus utility functions
27568 @cindex utility functions
27570 @cindex internal variables
27572 When writing small functions to be run from hooks (and stuff), it's
27573 vital to have access to the Gnus internal functions and variables.
27574 Below is a list of the most common ones.
27578 @item gnus-newsgroup-name
27579 @vindex gnus-newsgroup-name
27580 This variable holds the name of the current newsgroup.
27582 @item gnus-find-method-for-group
27583 @findex gnus-find-method-for-group
27584 A function that returns the select method for @var{group}.
27586 @item gnus-group-real-name
27587 @findex gnus-group-real-name
27588 Takes a full (prefixed) Gnus group name, and returns the unprefixed
27591 @item gnus-group-prefixed-name
27592 @findex gnus-group-prefixed-name
27593 Takes an unprefixed group name and a select method, and returns the full
27594 (prefixed) Gnus group name.
27596 @item gnus-get-info
27597 @findex gnus-get-info
27598 Returns the group info list for @var{group}.
27600 @item gnus-group-unread
27601 @findex gnus-group-unread
27602 The number of unread articles in @var{group}, or @code{t} if that is
27606 @findex gnus-active
27607 The active entry for @var{group}.
27609 @item gnus-set-active
27610 @findex gnus-set-active
27611 Set the active entry for @var{group}.
27613 @item gnus-add-current-to-buffer-list
27614 @findex gnus-add-current-to-buffer-list
27615 Adds the current buffer to the list of buffers to be killed on Gnus
27618 @item gnus-continuum-version
27619 @findex gnus-continuum-version
27620 Takes a Gnus version string as a parameter and returns a floating point
27621 number. Earlier versions will always get a lower number than later
27624 @item gnus-group-read-only-p
27625 @findex gnus-group-read-only-p
27626 Says whether @var{group} is read-only or not.
27628 @item gnus-news-group-p
27629 @findex gnus-news-group-p
27630 Says whether @var{group} came from a news back end.
27632 @item gnus-ephemeral-group-p
27633 @findex gnus-ephemeral-group-p
27634 Says whether @var{group} is ephemeral or not.
27636 @item gnus-server-to-method
27637 @findex gnus-server-to-method
27638 Returns the select method corresponding to @var{server}.
27640 @item gnus-server-equal
27641 @findex gnus-server-equal
27642 Says whether two virtual servers are equal.
27644 @item gnus-group-native-p
27645 @findex gnus-group-native-p
27646 Says whether @var{group} is native or not.
27648 @item gnus-group-secondary-p
27649 @findex gnus-group-secondary-p
27650 Says whether @var{group} is secondary or not.
27652 @item gnus-group-foreign-p
27653 @findex gnus-group-foreign-p
27654 Says whether @var{group} is foreign or not.
27656 @item gnus-group-find-parameter
27657 @findex gnus-group-find-parameter
27658 Returns the parameter list of @var{group}. If given a second parameter,
27659 returns the value of that parameter for @var{group}.
27661 @item gnus-group-set-parameter
27662 @findex gnus-group-set-parameter
27663 Takes three parameters; @var{group}, @var{parameter} and @var{value}.
27665 @item gnus-narrow-to-body
27666 @findex gnus-narrow-to-body
27667 Narrows the current buffer to the body of the article.
27669 @item gnus-check-backend-function
27670 @findex gnus-check-backend-function
27671 Takes two parameters, @var{function} and @var{group}. If the back end
27672 @var{group} comes from supports @var{function}, return non-@code{nil}.
27675 (gnus-check-backend-function "request-scan" "nnml:misc")
27679 @item gnus-read-method
27680 @findex gnus-read-method
27681 Prompts the user for a select method.
27686 @node Back End Interface
27687 @subsection Back End Interface
27689 Gnus doesn't know anything about @acronym{NNTP}, spools, mail or virtual
27690 groups. It only knows how to talk to @dfn{virtual servers}. A virtual
27691 server is a @dfn{back end} and some @dfn{back end variables}. As examples
27692 of the first, we have @code{nntp}, @code{nnspool} and @code{nnmbox}. As
27693 examples of the latter we have @code{nntp-port-number} and
27694 @code{nnmbox-directory}.
27696 When Gnus asks for information from a back end---say @code{nntp}---on
27697 something, it will normally include a virtual server name in the
27698 function parameters. (If not, the back end should use the ``current''
27699 virtual server.) For instance, @code{nntp-request-list} takes a virtual
27700 server as its only (optional) parameter. If this virtual server hasn't
27701 been opened, the function should fail.
27703 Note that a virtual server name has no relation to some physical server
27704 name. Take this example:
27708 (nntp-address "ifi.uio.no")
27709 (nntp-port-number 4324))
27712 Here the virtual server name is @samp{odd-one} while the name of
27713 the physical server is @samp{ifi.uio.no}.
27715 The back ends should be able to switch between several virtual servers.
27716 The standard back ends implement this by keeping an alist of virtual
27717 server environments that they pull down/push up when needed.
27719 There are two groups of interface functions: @dfn{required functions},
27720 which must be present, and @dfn{optional functions}, which Gnus will
27721 always check for presence before attempting to call 'em.
27723 All these functions are expected to return data in the buffer
27724 @code{nntp-server-buffer} (@samp{ *nntpd*}), which is somewhat
27725 unfortunately named, but we'll have to live with it. When I talk about
27726 @dfn{resulting data}, I always refer to the data in that buffer. When I
27727 talk about @dfn{return value}, I talk about the function value returned by
27728 the function call. Functions that fail should return @code{nil} as the
27731 Some back ends could be said to be @dfn{server-forming} back ends, and
27732 some might be said not to be. The latter are back ends that generally
27733 only operate on one group at a time, and have no concept of ``server''
27734 ---they have a group, and they deliver info on that group and nothing
27737 Gnus identifies each message by way of group name and article number. A
27738 few remarks about these article numbers might be useful. First of all,
27739 the numbers are positive integers. Secondly, it is normally not
27740 possible for later articles to ``re-use'' older article numbers without
27741 confusing Gnus. That is, if a group has ever contained a message
27742 numbered 42, then no other message may get that number, or Gnus will get
27743 mightily confused.@footnote{See the function
27744 @code{nnchoke-request-update-info}, @ref{Optional Back End Functions}.}
27745 Third, article numbers must be assigned in order of arrival in the
27746 group; this is not necessarily the same as the date of the message.
27748 The previous paragraph already mentions all the ``hard'' restrictions that
27749 article numbers must fulfill. But it seems that it might be useful to
27750 assign @emph{consecutive} article numbers, for Gnus gets quite confused
27751 if there are holes in the article numbering sequence. However, due to
27752 the ``no-reuse'' restriction, holes cannot be avoided altogether. It's
27753 also useful for the article numbers to start at 1 to avoid running out
27754 of numbers as long as possible.
27756 Note that by convention, back ends are named @code{nnsomething}, but
27757 Gnus also comes with some @code{nnnotbackends}, such as
27758 @file{nnheader.el}, @file{nnmail.el} and @file{nnoo.el}.
27760 In the examples and definitions I will refer to the imaginary back end
27763 @cindex @code{nnchoke}
27766 * Required Back End Functions:: Functions that must be implemented.
27767 * Optional Back End Functions:: Functions that need not be implemented.
27768 * Error Messaging:: How to get messages and report errors.
27769 * Writing New Back Ends:: Extending old back ends.
27770 * Hooking New Back Ends Into Gnus:: What has to be done on the Gnus end.
27771 * Mail-like Back Ends:: Some tips on mail back ends.
27775 @node Required Back End Functions
27776 @subsubsection Required Back End Functions
27780 @item (nnchoke-retrieve-headers ARTICLES &optional GROUP SERVER FETCH-OLD)
27782 @var{articles} is either a range of article numbers or a list of
27783 @code{Message-ID}s. Current back ends do not fully support either---only
27784 sequences (lists) of article numbers, and most back ends do not support
27785 retrieval of @code{Message-ID}s. But they should try for both.
27787 The result data should either be HEADs or @acronym{NOV} lines, and the result
27788 value should either be @code{headers} or @code{nov} to reflect this.
27789 This might later be expanded to @code{various}, which will be a mixture
27790 of HEADs and @acronym{NOV} lines, but this is currently not supported by Gnus.
27792 If @var{fetch-old} is non-@code{nil} it says to try fetching ``extra
27793 headers'', in some meaning of the word. This is generally done by
27794 fetching (at most) @var{fetch-old} extra headers less than the smallest
27795 article number in @code{articles}, and filling the gaps as well. The
27796 presence of this parameter can be ignored if the back end finds it
27797 cumbersome to follow the request. If this is non-@code{nil} and not a
27798 number, do maximum fetches.
27800 Here's an example HEAD:
27803 221 1056 Article retrieved.
27804 Path: ifi.uio.no!sturles
27805 From: sturles@@ifi.uio.no (Sturle Sunde)
27806 Newsgroups: ifi.discussion
27807 Subject: Re: Something very droll
27808 Date: 27 Oct 1994 14:02:57 +0100
27809 Organization: Dept. of Informatics, University of Oslo, Norway
27811 Message-ID: <38o8e1$a0o@@holmenkollen.ifi.uio.no>
27812 References: <38jdmq$4qu@@visbur.ifi.uio.no>
27813 NNTP-Posting-Host: holmenkollen.ifi.uio.no
27817 So a @code{headers} return value would imply that there's a number of
27818 these in the data buffer.
27820 Here's a BNF definition of such a buffer:
27824 head = error / valid-head
27825 error-message = [ "4" / "5" ] 2number " " <error message> eol
27826 valid-head = valid-message *header "." eol
27827 valid-message = "221 " <number> " Article retrieved." eol
27828 header = <text> eol
27832 (The version of BNF used here is the one used in RFC822.)
27834 If the return value is @code{nov}, the data buffer should contain
27835 @dfn{network overview database} lines. These are basically fields
27839 nov-buffer = *nov-line
27840 nov-line = field 7*8[ <TAB> field ] eol
27841 field = <text except TAB>
27844 For a closer look at what should be in those fields,
27848 @item (nnchoke-open-server SERVER &optional DEFINITIONS)
27850 @var{server} is here the virtual server name. @var{definitions} is a
27851 list of @code{(VARIABLE VALUE)} pairs that define this virtual server.
27853 If the server can't be opened, no error should be signaled. The back end
27854 may then choose to refuse further attempts at connecting to this
27855 server. In fact, it should do so.
27857 If the server is opened already, this function should return a
27858 non-@code{nil} value. There should be no data returned.
27861 @item (nnchoke-close-server &optional SERVER)
27863 Close connection to @var{server} and free all resources connected
27864 to it. Return @code{nil} if the server couldn't be closed for some
27867 There should be no data returned.
27870 @item (nnchoke-request-close)
27872 Close connection to all servers and free all resources that the back end
27873 have reserved. All buffers that have been created by that back end
27874 should be killed. (Not the @code{nntp-server-buffer}, though.) This
27875 function is generally only called when Gnus is shutting down.
27877 There should be no data returned.
27880 @item (nnchoke-server-opened &optional SERVER)
27882 If @var{server} is the current virtual server, and the connection to the
27883 physical server is alive, then this function should return a
27884 non-@code{nil} value. This function should under no circumstances
27885 attempt to reconnect to a server we have lost connection to.
27887 There should be no data returned.
27890 @item (nnchoke-status-message &optional SERVER)
27892 This function should return the last error message from @var{server}.
27894 There should be no data returned.
27897 @item (nnchoke-request-article ARTICLE &optional GROUP SERVER TO-BUFFER)
27899 The result data from this function should be the article specified by
27900 @var{article}. This might either be a @code{Message-ID} or a number.
27901 It is optional whether to implement retrieval by @code{Message-ID}, but
27902 it would be nice if that were possible.
27904 If @var{to-buffer} is non-@code{nil}, the result data should be returned
27905 in this buffer instead of the normal data buffer. This is to make it
27906 possible to avoid copying large amounts of data from one buffer to
27907 another, while Gnus mainly requests articles to be inserted directly
27908 into its article buffer.
27910 If it is at all possible, this function should return a cons cell where
27911 the @code{car} is the group name the article was fetched from, and the @code{cdr} is
27912 the article number. This will enable Gnus to find out what the real
27913 group and article numbers are when fetching articles by
27914 @code{Message-ID}. If this isn't possible, @code{t} should be returned
27915 on successful article retrieval.
27918 @item (nnchoke-request-group GROUP &optional SERVER FAST)
27920 Get data on @var{group}. This function also has the side effect of
27921 making @var{group} the current group.
27923 If @var{fast}, don't bother to return useful data, just make @var{group}
27926 Here's an example of some result data and a definition of the same:
27929 211 56 1000 1059 ifi.discussion
27932 The first number is the status, which should be 211. Next is the
27933 total number of articles in the group, the lowest article number, the
27934 highest article number, and finally the group name. Note that the total
27935 number of articles may be less than one might think while just
27936 considering the highest and lowest article numbers, but some articles
27937 may have been canceled. Gnus just discards the total-number, so
27938 whether one should take the bother to generate it properly (if that is a
27939 problem) is left as an exercise to the reader. If the group contains no
27940 articles, the lowest article number should be reported as 1 and the
27944 group-status = [ error / info ] eol
27945 error = [ "4" / "5" ] 2<number> " " <Error message>
27946 info = "211 " 3* [ <number> " " ] <string>
27950 @item (nnchoke-close-group GROUP &optional SERVER)
27952 Close @var{group} and free any resources connected to it. This will be
27953 a no-op on most back ends.
27955 There should be no data returned.
27958 @item (nnchoke-request-list &optional SERVER)
27960 Return a list of all groups available on @var{server}. And that means
27963 Here's an example from a server that only carries two groups:
27966 ifi.test 0000002200 0000002000 y
27967 ifi.discussion 3324 3300 n
27970 On each line we have a group name, then the highest article number in
27971 that group, the lowest article number, and finally a flag. If the group
27972 contains no articles, the lowest article number should be reported as 1
27973 and the highest as 0.
27976 active-file = *active-line
27977 active-line = name " " <number> " " <number> " " flags eol
27979 flags = "n" / "y" / "m" / "x" / "j" / "=" name
27982 The flag says whether the group is read-only (@samp{n}), is moderated
27983 (@samp{m}), is dead (@samp{x}), is aliased to some other group
27984 (@samp{=other-group}) or none of the above (@samp{y}).
27987 @item (nnchoke-request-post &optional SERVER)
27989 This function should post the current buffer. It might return whether
27990 the posting was successful or not, but that's not required. If, for
27991 instance, the posting is done asynchronously, it has generally not been
27992 completed by the time this function concludes. In that case, this
27993 function should set up some kind of sentinel to beep the user loud and
27994 clear if the posting could not be completed.
27996 There should be no result data from this function.
28001 @node Optional Back End Functions
28002 @subsubsection Optional Back End Functions
28006 @item (nnchoke-retrieve-groups GROUPS &optional SERVER)
28008 @var{groups} is a list of groups, and this function should request data
28009 on all those groups. How it does it is of no concern to Gnus, but it
28010 should attempt to do this in a speedy fashion.
28012 The return value of this function can be either @code{active} or
28013 @code{group}, which says what the format of the result data is. The
28014 former is in the same format as the data from
28015 @code{nnchoke-request-list}, while the latter is a buffer full of lines
28016 in the same format as @code{nnchoke-request-group} gives.
28019 group-buffer = *active-line / *group-status
28023 @item (nnchoke-request-update-info GROUP INFO &optional SERVER)
28025 A Gnus group info (@pxref{Group Info}) is handed to the back end for
28026 alterations. This comes in handy if the back end really carries all
28027 the information (as is the case with virtual and imap groups). This
28028 function should destructively alter the info to suit its needs, and
28029 should return a non-@code{nil} value (exceptionally,
28030 @code{nntp-request-update-info} always returns @code{nil} not to waste
28031 the network resources).
28033 There should be no result data from this function.
28036 @item (nnchoke-request-type GROUP &optional ARTICLE)
28038 When the user issues commands for ``sending news'' (@kbd{F} in the
28039 summary buffer, for instance), Gnus has to know whether the article the
28040 user is following up on is news or mail. This function should return
28041 @code{news} if @var{article} in @var{group} is news, @code{mail} if it
28042 is mail and @code{unknown} if the type can't be decided. (The
28043 @var{article} parameter is necessary in @code{nnvirtual} groups which
28044 might very well combine mail groups and news groups.) Both @var{group}
28045 and @var{article} may be @code{nil}.
28047 There should be no result data from this function.
28050 @item (nnchoke-request-set-mark GROUP ACTION &optional SERVER)
28052 Set/remove/add marks on articles. Normally Gnus handles the article
28053 marks (such as read, ticked, expired etc) internally, and store them in
28054 @file{~/.newsrc.eld}. Some back ends (such as @acronym{IMAP}) however carry
28055 all information about the articles on the server, so Gnus need to
28056 propagate the mark information to the server.
28058 @var{action} is a list of mark setting requests, having this format:
28061 (RANGE ACTION MARK)
28064 @var{range} is a range of articles you wish to update marks on.
28065 @var{action} is @code{add} or @code{del}, used to add marks or remove
28066 marks (preserving all marks not mentioned). @var{mark} is a list of
28067 marks; where each mark is a symbol. Currently used marks are
28068 @code{read}, @code{tick}, @code{reply}, @code{expire}, @code{killed},
28069 @code{dormant}, @code{save}, @code{download}, @code{unsend},
28070 @code{forward} and @code{recent}, but your back end should, if
28071 possible, not limit itself to these.
28073 Given contradictory actions, the last action in the list should be the
28074 effective one. That is, if your action contains a request to add the
28075 @code{tick} mark on article 1 and, later in the list, a request to
28076 remove the mark on the same article, the mark should in fact be removed.
28078 An example action list:
28081 (((5 12 30) 'del '(tick))
28082 ((10 . 90) 'add '(read expire))
28083 ((92 94) 'del '(read)))
28086 The function should return a range of articles it wasn't able to set the
28087 mark on (currently not used for anything).
28089 There should be no result data from this function.
28091 @item (nnchoke-request-update-mark GROUP ARTICLE MARK)
28093 If the user tries to set a mark that the back end doesn't like, this
28094 function may change the mark. Gnus will use whatever this function
28095 returns as the mark for @var{article} instead of the original
28096 @var{mark}. If the back end doesn't care, it must return the original
28097 @var{mark}, and not @code{nil} or any other type of garbage.
28099 The only use for this I can see is what @code{nnvirtual} does with
28100 it---if a component group is auto-expirable, marking an article as read
28101 in the virtual group should result in the article being marked as
28104 There should be no result data from this function.
28107 @item (nnchoke-request-scan &optional GROUP SERVER)
28109 This function may be called at any time (by Gnus or anything else) to
28110 request that the back end check for incoming articles, in one way or
28111 another. A mail back end will typically read the spool file or query
28112 the @acronym{POP} server when this function is invoked. The
28113 @var{group} doesn't have to be heeded---if the back end decides that
28114 it is too much work just scanning for a single group, it may do a
28115 total scan of all groups. It would be nice, however, to keep things
28116 local if that's practical.
28118 There should be no result data from this function.
28121 @item (nnchoke-request-group-description GROUP &optional SERVER)
28123 The result data from this function should be a description of
28127 description-line = name <TAB> description eol
28129 description = <text>
28132 @item (nnchoke-request-list-newsgroups &optional SERVER)
28134 The result data from this function should be the description of all
28135 groups available on the server.
28138 description-buffer = *description-line
28142 @item (nnchoke-request-newgroups DATE &optional SERVER)
28144 The result data from this function should be all groups that were
28145 created after @samp{date}, which is in normal human-readable date format
28146 (i.e., the date format used in mail and news headers, and returned by
28147 the function @code{message-make-date} by default). The data should be
28148 in the active buffer format.
28150 It is okay for this function to return ``too many'' groups; some back ends
28151 might find it cheaper to return the full list of groups, rather than
28152 just the new groups. But don't do this for back ends with many groups.
28153 Normally, if the user creates the groups herself, there won't be too
28154 many groups, so @code{nnml} and the like are probably safe. But for
28155 back ends like @code{nntp}, where the groups have been created by the
28156 server, it is quite likely that there can be many groups.
28159 @item (nnchoke-request-create-group GROUP &optional SERVER)
28161 This function should create an empty group with name @var{group}.
28163 There should be no return data.
28166 @item (nnchoke-request-expire-articles ARTICLES &optional GROUP SERVER FORCE)
28168 This function should run the expiry process on all articles in the
28169 @var{articles} range (which is currently a simple list of article
28170 numbers.) It is left up to the back end to decide how old articles
28171 should be before they are removed by this function. If @var{force} is
28172 non-@code{nil}, all @var{articles} should be deleted, no matter how new
28175 This function should return a list of articles that it did not/was not
28178 There should be no result data returned.
28181 @item (nnchoke-request-move-article ARTICLE GROUP SERVER ACCEPT-FORM &optional LAST)
28183 This function should move @var{article} (which is a number) from
28184 @var{group} by calling @var{accept-form}.
28186 This function should ready the article in question for moving by
28187 removing any header lines it has added to the article, and generally
28188 should ``tidy up'' the article. Then it should @code{eval}
28189 @var{accept-form} in the buffer where the ``tidy'' article is. This
28190 will do the actual copying. If this @code{eval} returns a
28191 non-@code{nil} value, the article should be removed.
28193 If @var{last} is @code{nil}, that means that there is a high likelihood
28194 that there will be more requests issued shortly, so that allows some
28197 The function should return a cons where the @code{car} is the group name and
28198 the @code{cdr} is the article number that the article was entered as.
28200 There should be no data returned.
28203 @item (nnchoke-request-accept-article GROUP &optional SERVER LAST)
28205 This function takes the current buffer and inserts it into @var{group}.
28206 If @var{last} in @code{nil}, that means that there will be more calls to
28207 this function in short order.
28209 The function should return a cons where the @code{car} is the group name and
28210 the @code{cdr} is the article number that the article was entered as.
28212 The group should exist before the back end is asked to accept the
28213 article for that group.
28215 There should be no data returned.
28218 @item (nnchoke-request-replace-article ARTICLE GROUP BUFFER)
28220 This function should remove @var{article} (which is a number) from
28221 @var{group} and insert @var{buffer} there instead.
28223 There should be no data returned.
28226 @item (nnchoke-request-delete-group GROUP FORCE &optional SERVER)
28228 This function should delete @var{group}. If @var{force}, it should
28229 really delete all the articles in the group, and then delete the group
28230 itself. (If there is such a thing as ``the group itself''.)
28232 There should be no data returned.
28235 @item (nnchoke-request-rename-group GROUP NEW-NAME &optional SERVER)
28237 This function should rename @var{group} into @var{new-name}. All
28238 articles in @var{group} should move to @var{new-name}.
28240 There should be no data returned.
28245 @node Error Messaging
28246 @subsubsection Error Messaging
28248 @findex nnheader-report
28249 @findex nnheader-get-report
28250 The back ends should use the function @code{nnheader-report} to report
28251 error conditions---they should not raise errors when they aren't able to
28252 perform a request. The first argument to this function is the back end
28253 symbol, and the rest are interpreted as arguments to @code{format} if
28254 there are multiple of them, or just a string if there is one of them.
28255 This function must always returns @code{nil}.
28258 (nnheader-report 'nnchoke "You did something totally bogus")
28260 (nnheader-report 'nnchoke "Could not request group %s" group)
28263 Gnus, in turn, will call @code{nnheader-get-report} when it gets a
28264 @code{nil} back from a server, and this function returns the most
28265 recently reported message for the back end in question. This function
28266 takes one argument---the server symbol.
28268 Internally, these functions access @var{back-end}@code{-status-string},
28269 so the @code{nnchoke} back end will have its error message stored in
28270 @code{nnchoke-status-string}.
28273 @node Writing New Back Ends
28274 @subsubsection Writing New Back Ends
28276 Many back ends are quite similar. @code{nnml} is just like
28277 @code{nnspool}, but it allows you to edit the articles on the server.
28278 @code{nnmh} is just like @code{nnml}, but it doesn't use an active file,
28279 and it doesn't maintain overview databases. @code{nndir} is just like
28280 @code{nnml}, but it has no concept of ``groups'', and it doesn't allow
28283 It would make sense if it were possible to ``inherit'' functions from
28284 back ends when writing new back ends. And, indeed, you can do that if you
28285 want to. (You don't have to if you don't want to, of course.)
28287 All the back ends declare their public variables and functions by using a
28288 package called @code{nnoo}.
28290 To inherit functions from other back ends (and allow other back ends to
28291 inherit functions from the current back end), you should use the
28297 This macro declares the first parameter to be a child of the subsequent
28298 parameters. For instance:
28301 (nnoo-declare nndir
28305 @code{nndir} has declared here that it intends to inherit functions from
28306 both @code{nnml} and @code{nnmh}.
28309 This macro is equivalent to @code{defvar}, but registers the variable as
28310 a public server variable. Most state-oriented variables should be
28311 declared with @code{defvoo} instead of @code{defvar}.
28313 In addition to the normal @code{defvar} parameters, it takes a list of
28314 variables in the parent back ends to map the variable to when executing
28315 a function in those back ends.
28318 (defvoo nndir-directory nil
28319 "Where nndir will look for groups."
28320 nnml-current-directory nnmh-current-directory)
28323 This means that @code{nnml-current-directory} will be set to
28324 @code{nndir-directory} when an @code{nnml} function is called on behalf
28325 of @code{nndir}. (The same with @code{nnmh}.)
28327 @item nnoo-define-basics
28328 This macro defines some common functions that almost all back ends should
28332 (nnoo-define-basics nndir)
28336 This macro is just like @code{defun} and takes the same parameters. In
28337 addition to doing the normal @code{defun} things, it registers the
28338 function as being public so that other back ends can inherit it.
28340 @item nnoo-map-functions
28341 This macro allows mapping of functions from the current back end to
28342 functions from the parent back ends.
28345 (nnoo-map-functions nndir
28346 (nnml-retrieve-headers 0 nndir-current-group 0 0)
28347 (nnmh-request-article 0 nndir-current-group 0 0))
28350 This means that when @code{nndir-retrieve-headers} is called, the first,
28351 third, and fourth parameters will be passed on to
28352 @code{nnml-retrieve-headers}, while the second parameter is set to the
28353 value of @code{nndir-current-group}.
28356 This macro allows importing functions from back ends. It should be the
28357 last thing in the source file, since it will only define functions that
28358 haven't already been defined.
28364 nnmh-request-newgroups)
28368 This means that calls to @code{nndir-request-list} should just be passed
28369 on to @code{nnmh-request-list}, while all public functions from
28370 @code{nnml} that haven't been defined in @code{nndir} yet should be
28375 Below is a slightly shortened version of the @code{nndir} back end.
28378 ;;; @r{nndir.el --- single directory newsgroup access for Gnus}
28379 ;; @r{Copyright (C) 1995,96 Free Software Foundation, Inc.}
28383 (require 'nnheader)
28387 (eval-when-compile (require 'cl))
28389 (nnoo-declare nndir
28392 (defvoo nndir-directory nil
28393 "Where nndir will look for groups."
28394 nnml-current-directory nnmh-current-directory)
28396 (defvoo nndir-nov-is-evil nil
28397 "*Non-nil means that nndir will never retrieve NOV headers."
28400 (defvoo nndir-current-group ""
28402 nnml-current-group nnmh-current-group)
28403 (defvoo nndir-top-directory nil nil nnml-directory nnmh-directory)
28404 (defvoo nndir-get-new-mail nil nil nnml-get-new-mail nnmh-get-new-mail)
28406 (defvoo nndir-status-string "" nil nnmh-status-string)
28407 (defconst nndir-version "nndir 1.0")
28409 ;;; @r{Interface functions.}
28411 (nnoo-define-basics nndir)
28413 (deffoo nndir-open-server (server &optional defs)
28414 (setq nndir-directory
28415 (or (cadr (assq 'nndir-directory defs))
28417 (unless (assq 'nndir-directory defs)
28418 (push `(nndir-directory ,server) defs))
28419 (push `(nndir-current-group
28420 ,(file-name-nondirectory
28421 (directory-file-name nndir-directory)))
28423 (push `(nndir-top-directory
28424 ,(file-name-directory (directory-file-name nndir-directory)))
28426 (nnoo-change-server 'nndir server defs))
28428 (nnoo-map-functions nndir
28429 (nnml-retrieve-headers 0 nndir-current-group 0 0)
28430 (nnmh-request-article 0 nndir-current-group 0 0)
28431 (nnmh-request-group nndir-current-group 0 0)
28432 (nnmh-close-group nndir-current-group 0))
28436 nnmh-status-message
28438 nnmh-request-newgroups))
28444 @node Hooking New Back Ends Into Gnus
28445 @subsubsection Hooking New Back Ends Into Gnus
28447 @vindex gnus-valid-select-methods
28448 @findex gnus-declare-backend
28449 Having Gnus start using your new back end is rather easy---you just
28450 declare it with the @code{gnus-declare-backend} functions. This will
28451 enter the back end into the @code{gnus-valid-select-methods} variable.
28453 @code{gnus-declare-backend} takes two parameters---the back end name and
28454 an arbitrary number of @dfn{abilities}.
28459 (gnus-declare-backend "nnchoke" 'mail 'respool 'address)
28462 The above line would then go in the @file{nnchoke.el} file.
28464 The abilities can be:
28468 This is a mailish back end---followups should (probably) go via mail.
28470 This is a newsish back end---followups should (probably) go via news.
28472 This back end supports both mail and news.
28474 This is neither a post nor mail back end---it's something completely
28477 It supports respooling---or rather, it is able to modify its source
28478 articles and groups.
28480 The name of the server should be in the virtual server name. This is
28481 true for almost all back ends.
28482 @item prompt-address
28483 The user should be prompted for an address when doing commands like
28484 @kbd{B} in the group buffer. This is true for back ends like
28485 @code{nntp}, but not @code{nnmbox}, for instance.
28489 @node Mail-like Back Ends
28490 @subsubsection Mail-like Back Ends
28492 One of the things that separate the mail back ends from the rest of the
28493 back ends is the heavy dependence by most of the mail back ends on
28494 common functions in @file{nnmail.el}. For instance, here's the
28495 definition of @code{nnml-request-scan}:
28498 (deffoo nnml-request-scan (&optional group server)
28499 (setq nnml-article-file-alist nil)
28500 (nnmail-get-new-mail 'nnml 'nnml-save-nov nnml-directory group))
28503 It simply calls @code{nnmail-get-new-mail} with a few parameters,
28504 and @code{nnmail} takes care of all the moving and splitting of the
28507 This function takes four parameters.
28511 This should be a symbol to designate which back end is responsible for
28514 @item exit-function
28515 This function should be called after the splitting has been performed.
28517 @item temp-directory
28518 Where the temporary files should be stored.
28521 This optional argument should be a group name if the splitting is to be
28522 performed for one group only.
28525 @code{nnmail-get-new-mail} will call @var{back-end}@code{-save-mail} to
28526 save each article. @var{back-end}@code{-active-number} will be called to
28527 find the article number assigned to this article.
28529 The function also uses the following variables:
28530 @var{back-end}@code{-get-new-mail} (to see whether to get new mail for
28531 this back end); and @var{back-end}@code{-group-alist} and
28532 @var{back-end}@code{-active-file} to generate the new active file.
28533 @var{back-end}@code{-group-alist} should be a group-active alist, like
28537 (("a-group" (1 . 10))
28538 ("some-group" (34 . 39)))
28542 @node Score File Syntax
28543 @subsection Score File Syntax
28545 Score files are meant to be easily parseable, but yet extremely
28546 mallable. It was decided that something that had the same read syntax
28547 as an Emacs Lisp list would fit that spec.
28549 Here's a typical score file:
28553 ("win95" -10000 nil s)
28560 BNF definition of a score file:
28563 score-file = "" / "(" *element ")"
28564 element = rule / atom
28565 rule = string-rule / number-rule / date-rule
28566 string-rule = "(" quote string-header quote space *string-match ")"
28567 number-rule = "(" quote number-header quote space *number-match ")"
28568 date-rule = "(" quote date-header quote space *date-match ")"
28570 string-header = "subject" / "from" / "references" / "message-id" /
28571 "xref" / "body" / "head" / "all" / "followup"
28572 number-header = "lines" / "chars"
28573 date-header = "date"
28574 string-match = "(" quote <string> quote [ "" / [ space score [ "" /
28575 space date [ "" / [ space string-match-t ] ] ] ] ] ")"
28576 score = "nil" / <integer>
28577 date = "nil" / <natural number>
28578 string-match-t = "nil" / "s" / "substring" / "S" / "Substring" /
28579 "r" / "regex" / "R" / "Regex" /
28580 "e" / "exact" / "E" / "Exact" /
28581 "f" / "fuzzy" / "F" / "Fuzzy"
28582 number-match = "(" <integer> [ "" / [ space score [ "" /
28583 space date [ "" / [ space number-match-t ] ] ] ] ] ")"
28584 number-match-t = "nil" / "=" / "<" / ">" / ">=" / "<="
28585 date-match = "(" quote <string> quote [ "" / [ space score [ "" /
28586 space date [ "" / [ space date-match-t ] ] ] ] ")"
28587 date-match-t = "nil" / "at" / "before" / "after"
28588 atom = "(" [ required-atom / optional-atom ] ")"
28589 required-atom = mark / expunge / mark-and-expunge / files /
28590 exclude-files / read-only / touched
28591 optional-atom = adapt / local / eval
28592 mark = "mark" space nil-or-number
28593 nil-or-number = "nil" / <integer>
28594 expunge = "expunge" space nil-or-number
28595 mark-and-expunge = "mark-and-expunge" space nil-or-number
28596 files = "files" *[ space <string> ]
28597 exclude-files = "exclude-files" *[ space <string> ]
28598 read-only = "read-only" [ space "nil" / space "t" ]
28599 adapt = "adapt" [ space "ignore" / space "t" / space adapt-rule ]
28600 adapt-rule = "(" *[ <string> *[ "(" <string> <integer> ")" ] ")"
28601 local = "local" *[ space "(" <string> space <form> ")" ]
28602 eval = "eval" space <form>
28603 space = *[ " " / <TAB> / <NEWLINE> ]
28606 Any unrecognized elements in a score file should be ignored, but not
28609 As you can see, white space is needed, but the type and amount of white
28610 space is irrelevant. This means that formatting of the score file is
28611 left up to the programmer---if it's simpler to just spew it all out on
28612 one looong line, then that's ok.
28614 The meaning of the various atoms are explained elsewhere in this
28615 manual (@pxref{Score File Format}).
28619 @subsection Headers
28621 Internally Gnus uses a format for storing article headers that
28622 corresponds to the @acronym{NOV} format in a mysterious fashion. One could
28623 almost suspect that the author looked at the @acronym{NOV} specification and
28624 just shamelessly @emph{stole} the entire thing, and one would be right.
28626 @dfn{Header} is a severely overloaded term. ``Header'' is used in
28627 RFC 1036 to talk about lines in the head of an article (e.g.,
28628 @code{From}). It is used by many people as a synonym for
28629 ``head''---``the header and the body''. (That should be avoided, in my
28630 opinion.) And Gnus uses a format internally that it calls ``header'',
28631 which is what I'm talking about here. This is a 9-element vector,
28632 basically, with each header (ouch) having one slot.
28634 These slots are, in order: @code{number}, @code{subject}, @code{from},
28635 @code{date}, @code{id}, @code{references}, @code{chars}, @code{lines},
28636 @code{xref}, and @code{extra}. There are macros for accessing and
28637 setting these slots---they all have predictable names beginning with
28638 @code{mail-header-} and @code{mail-header-set-}, respectively.
28640 All these slots contain strings, except the @code{extra} slot, which
28641 contains an alist of header/value pairs (@pxref{To From Newsgroups}).
28647 @sc{gnus} introduced a concept that I found so useful that I've started
28648 using it a lot and have elaborated on it greatly.
28650 The question is simple: If you have a large amount of objects that are
28651 identified by numbers (say, articles, to take a @emph{wild} example)
28652 that you want to qualify as being ``included'', a normal sequence isn't
28653 very useful. (A 200,000 length sequence is a bit long-winded.)
28655 The solution is as simple as the question: You just collapse the
28659 (1 2 3 4 5 6 10 11 12)
28662 is transformed into
28665 ((1 . 6) (10 . 12))
28668 To avoid having those nasty @samp{(13 . 13)} elements to denote a
28669 lonesome object, a @samp{13} is a valid element:
28672 ((1 . 6) 7 (10 . 12))
28675 This means that comparing two ranges to find out whether they are equal
28676 is slightly tricky:
28679 ((1 . 5) 7 8 (10 . 12))
28685 ((1 . 5) (7 . 8) (10 . 12))
28688 are equal. In fact, any non-descending list is a range:
28694 is a perfectly valid range, although a pretty long-winded one. This is
28701 and is equal to the previous range.
28703 Here's a BNF definition of ranges. Of course, one must remember the
28704 semantic requirement that the numbers are non-descending. (Any number
28705 of repetition of the same number is allowed, but apt to disappear in
28709 range = simple-range / normal-range
28710 simple-range = "(" number " . " number ")"
28711 normal-range = "(" start-contents ")"
28712 contents = "" / simple-range *[ " " contents ] /
28713 number *[ " " contents ]
28716 Gnus currently uses ranges to keep track of read articles and article
28717 marks. I plan on implementing a number of range operators in C if The
28718 Powers That Be are willing to let me. (I haven't asked yet, because I
28719 need to do some more thinking on what operators I need to make life
28720 totally range-based without ever having to convert back to normal
28725 @subsection Group Info
28727 Gnus stores all permanent info on groups in a @dfn{group info} list.
28728 This list is from three to six elements (or more) long and exhaustively
28729 describes the group.
28731 Here are two example group infos; one is a very simple group while the
28732 second is a more complex one:
28735 ("no.group" 5 ((1 . 54324)))
28737 ("nnml:my.mail" 3 ((1 . 5) 9 (20 . 55))
28738 ((tick (15 . 19)) (replied 3 6 (19 . 3)))
28740 ((auto-expire . t) (to-address . "ding@@gnus.org")))
28743 The first element is the @dfn{group name}---as Gnus knows the group,
28744 anyway. The second element is the @dfn{subscription level}, which
28745 normally is a small integer. (It can also be the @dfn{rank}, which is a
28746 cons cell where the @code{car} is the level and the @code{cdr} is the
28747 score.) The third element is a list of ranges of read articles. The
28748 fourth element is a list of lists of article marks of various kinds.
28749 The fifth element is the select method (or virtual server, if you like).
28750 The sixth element is a list of @dfn{group parameters}, which is what
28751 this section is about.
28753 Any of the last three elements may be missing if they are not required.
28754 In fact, the vast majority of groups will normally only have the first
28755 three elements, which saves quite a lot of cons cells.
28757 Here's a BNF definition of the group info format:
28760 info = "(" group space ralevel space read
28761 [ "" / [ space marks-list [ "" / [ space method [ "" /
28762 space parameters ] ] ] ] ] ")"
28763 group = quote <string> quote
28764 ralevel = rank / level
28765 level = <integer in the range of 1 to inf>
28766 rank = "(" level "." score ")"
28767 score = <integer in the range of 1 to inf>
28769 marks-lists = nil / "(" *marks ")"
28770 marks = "(" <string> range ")"
28771 method = "(" <string> *elisp-forms ")"
28772 parameters = "(" *elisp-forms ")"
28775 Actually that @samp{marks} rule is a fib. A @samp{marks} is a
28776 @samp{<string>} consed on to a @samp{range}, but that's a bitch to say
28779 If you have a Gnus info and want to access the elements, Gnus offers a
28780 series of macros for getting/setting these elements.
28783 @item gnus-info-group
28784 @itemx gnus-info-set-group
28785 @findex gnus-info-group
28786 @findex gnus-info-set-group
28787 Get/set the group name.
28789 @item gnus-info-rank
28790 @itemx gnus-info-set-rank
28791 @findex gnus-info-rank
28792 @findex gnus-info-set-rank
28793 Get/set the group rank (@pxref{Group Score}).
28795 @item gnus-info-level
28796 @itemx gnus-info-set-level
28797 @findex gnus-info-level
28798 @findex gnus-info-set-level
28799 Get/set the group level.
28801 @item gnus-info-score
28802 @itemx gnus-info-set-score
28803 @findex gnus-info-score
28804 @findex gnus-info-set-score
28805 Get/set the group score (@pxref{Group Score}).
28807 @item gnus-info-read
28808 @itemx gnus-info-set-read
28809 @findex gnus-info-read
28810 @findex gnus-info-set-read
28811 Get/set the ranges of read articles.
28813 @item gnus-info-marks
28814 @itemx gnus-info-set-marks
28815 @findex gnus-info-marks
28816 @findex gnus-info-set-marks
28817 Get/set the lists of ranges of marked articles.
28819 @item gnus-info-method
28820 @itemx gnus-info-set-method
28821 @findex gnus-info-method
28822 @findex gnus-info-set-method
28823 Get/set the group select method.
28825 @item gnus-info-params
28826 @itemx gnus-info-set-params
28827 @findex gnus-info-params
28828 @findex gnus-info-set-params
28829 Get/set the group parameters.
28832 All the getter functions take one parameter---the info list. The setter
28833 functions take two parameters---the info list and the new value.
28835 The last three elements in the group info aren't mandatory, so it may be
28836 necessary to extend the group info before setting the element. If this
28837 is necessary, you can just pass on a non-@code{nil} third parameter to
28838 the three final setter functions to have this happen automatically.
28841 @node Extended Interactive
28842 @subsection Extended Interactive
28843 @cindex interactive
28844 @findex gnus-interactive
28846 Gnus extends the standard Emacs @code{interactive} specification
28847 slightly to allow easy use of the symbolic prefix (@pxref{Symbolic
28848 Prefixes}). Here's an example of how this is used:
28851 (defun gnus-summary-increase-score (&optional score symp)
28852 (interactive (gnus-interactive "P\ny"))
28857 The best thing to do would have been to implement
28858 @code{gnus-interactive} as a macro which would have returned an
28859 @code{interactive} form, but this isn't possible since Emacs checks
28860 whether a function is interactive or not by simply doing an @code{assq}
28861 on the lambda form. So, instead we have @code{gnus-interactive}
28862 function that takes a string and returns values that are usable to
28863 @code{interactive}.
28865 This function accepts (almost) all normal @code{interactive} specs, but
28870 @vindex gnus-current-prefix-symbol
28871 The current symbolic prefix---the @code{gnus-current-prefix-symbol}
28875 @vindex gnus-current-prefix-symbols
28876 A list of the current symbolic prefixes---the
28877 @code{gnus-current-prefix-symbol} variable.
28880 The current article number---the @code{gnus-summary-article-number}
28884 The current article header---the @code{gnus-summary-article-header}
28888 The current group name---the @code{gnus-group-group-name}
28894 @node Emacs/XEmacs Code
28895 @subsection Emacs/XEmacs Code
28899 While Gnus runs under Emacs, XEmacs and Mule, I decided that one of the
28900 platforms must be the primary one. I chose Emacs. Not because I don't
28901 like XEmacs or Mule, but because it comes first alphabetically.
28903 This means that Gnus will byte-compile under Emacs with nary a warning,
28904 while XEmacs will pump out gigabytes of warnings while byte-compiling.
28905 As I use byte-compilation warnings to help me root out trivial errors in
28906 Gnus, that's very useful.
28908 I've also consistently used Emacs function interfaces, but have used
28909 Gnusey aliases for the functions. To take an example: Emacs defines a
28910 @code{run-at-time} function while XEmacs defines a @code{start-itimer}
28911 function. I then define a function called @code{gnus-run-at-time} that
28912 takes the same parameters as the Emacs @code{run-at-time}. When running
28913 Gnus under Emacs, the former function is just an alias for the latter.
28914 However, when running under XEmacs, the former is an alias for the
28915 following function:
28918 (defun gnus-xmas-run-at-time (time repeat function &rest args)
28922 (,function ,@@args))
28926 This sort of thing has been done for bunches of functions. Gnus does
28927 not redefine any native Emacs functions while running under XEmacs---it
28928 does this @code{defalias} thing with Gnus equivalents instead. Cleaner
28931 In the cases where the XEmacs function interface was obviously cleaner,
28932 I used it instead. For example @code{gnus-region-active-p} is an alias
28933 for @code{region-active-p} in XEmacs, whereas in Emacs it is a function.
28935 Of course, I could have chosen XEmacs as my native platform and done
28936 mapping functions the other way around. But I didn't. The performance
28937 hit these indirections impose on Gnus under XEmacs should be slight.
28940 @node Various File Formats
28941 @subsection Various File Formats
28944 * Active File Format:: Information on articles and groups available.
28945 * Newsgroups File Format:: Group descriptions.
28949 @node Active File Format
28950 @subsubsection Active File Format
28952 The active file lists all groups available on the server in
28953 question. It also lists the highest and lowest current article numbers
28956 Here's an excerpt from a typical active file:
28959 soc.motss 296030 293865 y
28960 alt.binaries.pictures.fractals 3922 3913 n
28961 comp.sources.unix 1605 1593 m
28962 comp.binaries.ibm.pc 5097 5089 y
28963 no.general 1000 900 y
28966 Here's a pseudo-BNF definition of this file:
28969 active = *group-line
28970 group-line = group spc high-number spc low-number spc flag <NEWLINE>
28971 group = <non-white-space string>
28973 high-number = <non-negative integer>
28974 low-number = <positive integer>
28975 flag = "y" / "n" / "m" / "j" / "x" / "=" group
28978 For a full description of this file, see the manual pages for
28979 @samp{innd}, in particular @samp{active(5)}.
28982 @node Newsgroups File Format
28983 @subsubsection Newsgroups File Format
28985 The newsgroups file lists groups along with their descriptions. Not all
28986 groups on the server have to be listed, and not all groups in the file
28987 have to exist on the server. The file is meant purely as information to
28990 The format is quite simple; a group name, a tab, and the description.
28991 Here's the definition:
28995 line = group tab description <NEWLINE>
28996 group = <non-white-space string>
28998 description = <string>
29003 @node Emacs for Heathens
29004 @section Emacs for Heathens
29006 Believe it or not, but some people who use Gnus haven't really used
29007 Emacs much before they embarked on their journey on the Gnus Love Boat.
29008 If you are one of those unfortunates whom ``@kbd{C-M-a}'', ``kill the
29009 region'', and ``set @code{gnus-flargblossen} to an alist where the key
29010 is a regexp that is used for matching on the group name'' are magical
29011 phrases with little or no meaning, then this appendix is for you. If
29012 you are already familiar with Emacs, just ignore this and go fondle your
29016 * Keystrokes:: Entering text and executing commands.
29017 * Emacs Lisp:: The built-in Emacs programming language.
29022 @subsection Keystrokes
29026 Q: What is an experienced Emacs user?
29029 A: A person who wishes that the terminal had pedals.
29032 Yes, when you use Emacs, you are apt to use the control key, the shift
29033 key and the meta key a lot. This is very annoying to some people
29034 (notably @code{vi}le users), and the rest of us just love the hell out
29035 of it. Just give up and submit. Emacs really does stand for
29036 ``Escape-Meta-Alt-Control-Shift'', and not ``Editing Macros'', as you
29037 may have heard from other disreputable sources (like the Emacs author).
29039 The shift keys are normally located near your pinky fingers, and are
29040 normally used to get capital letters and stuff. You probably use it all
29041 the time. The control key is normally marked ``CTRL'' or something like
29042 that. The meta key is, funnily enough, never marked as such on any
29043 keyboard. The one I'm currently at has a key that's marked ``Alt'',
29044 which is the meta key on this keyboard. It's usually located somewhere
29045 to the left hand side of the keyboard, usually on the bottom row.
29047 Now, us Emacs people don't say ``press the meta-control-m key'',
29048 because that's just too inconvenient. We say ``press the @kbd{C-M-m}
29049 key''. @kbd{M-} is the prefix that means ``meta'' and ``C-'' is the
29050 prefix that means ``control''. So ``press @kbd{C-k}'' means ``press
29051 down the control key, and hold it down while you press @kbd{k}''.
29052 ``Press @kbd{C-M-k}'' means ``press down and hold down the meta key and
29053 the control key and then press @kbd{k}''. Simple, ay?
29055 This is somewhat complicated by the fact that not all keyboards have a
29056 meta key. In that case you can use the ``escape'' key. Then @kbd{M-k}
29057 means ``press escape, release escape, press @kbd{k}''. That's much more
29058 work than if you have a meta key, so if that's the case, I respectfully
29059 suggest you get a real keyboard with a meta key. You can't live without
29065 @subsection Emacs Lisp
29067 Emacs is the King of Editors because it's really a Lisp interpreter.
29068 Each and every key you tap runs some Emacs Lisp code snippet, and since
29069 Emacs Lisp is an interpreted language, that means that you can configure
29070 any key to run any arbitrary code. You just, like, do it.
29072 Gnus is written in Emacs Lisp, and is run as a bunch of interpreted
29073 functions. (These are byte-compiled for speed, but it's still
29074 interpreted.) If you decide that you don't like the way Gnus does
29075 certain things, it's trivial to have it do something a different way.
29076 (Well, at least if you know how to write Lisp code.) However, that's
29077 beyond the scope of this manual, so we are simply going to talk about
29078 some common constructs that you normally use in your @file{.emacs} file
29081 If you want to set the variable @code{gnus-florgbnize} to four (4), you
29082 write the following:
29085 (setq gnus-florgbnize 4)
29088 This function (really ``special form'') @code{setq} is the one that can
29089 set a variable to some value. This is really all you need to know. Now
29090 you can go and fill your @file{.emacs} file with lots of these to change
29093 If you have put that thing in your @file{.emacs} file, it will be read
29094 and @code{eval}ed (which is lisp-ese for ``run'') the next time you
29095 start Emacs. If you want to change the variable right away, simply say
29096 @kbd{C-x C-e} after the closing parenthesis. That will @code{eval} the
29097 previous ``form'', which is a simple @code{setq} statement here.
29099 Go ahead---just try it, if you're located at your Emacs. After you
29100 @kbd{C-x C-e}, you will see @samp{4} appear in the echo area, which
29101 is the return value of the form you @code{eval}ed.
29105 If the manual says ``set @code{gnus-read-active-file} to @code{some}'',
29109 (setq gnus-read-active-file 'some)
29112 On the other hand, if the manual says ``set @code{gnus-nntp-server} to
29113 @samp{nntp.ifi.uio.no}'', that means:
29116 (setq gnus-nntp-server "nntp.ifi.uio.no")
29119 So be careful not to mix up strings (the latter) with symbols (the
29120 former). The manual is unambiguous, but it can be confusing.
29123 @include gnus-faq.texi
29143 @c Local Variables:
29145 @c coding: iso-8859-1
29149 arch-tag: c9fa47e7-78ca-4681-bda9-9fef45d1c819