4 @settitle T-gnus 6.15 Manual
10 * Gnus: (gnus). The newsreader Gnus.
15 @setchapternewpage odd
19 \documentclass[twoside,a4paper,openright,11pt]{book}
20 \usepackage[latin1]{inputenc}
21 \usepackage{pagestyle}
24 \input{gnusconfig.tex}
26 \ifx\pdfoutput\undefined
28 \usepackage[pdftex,bookmarks,colorlinks=true]{hyperref}
36 \newcommand{\gnusversionname}{Oort Gnus v0.12}
37 \newcommand{\gnuschaptername}{}
38 \newcommand{\gnussectionname}{}
40 \newcommand{\gnusbackslash}{/}
42 \newcommand{\gnusref}[1]{``#1'' on page \pageref{#1}}
43 \ifx\pdfoutput\undefined
44 \newcommand{\gnusuref}[1]{\gnustt{#1}}
46 \newcommand{\gnusuref}[1]{\href{#1}{\gnustt{#1}}}
48 \newcommand{\gnusxref}[1]{See ``#1'' on page \pageref{#1}}
49 \newcommand{\gnuspxref}[1]{see ``#1'' on page \pageref{#1}}
51 \newcommand{\gnuskindex}[1]{\index{#1}}
52 \newcommand{\gnusindex}[1]{\index{#1}}
54 \newcommand{\gnustt}[1]{{\gnusselectttfont{}#1}}
55 \newcommand{\gnuscode}[1]{\gnustt{#1}}
56 \newcommand{\gnussamp}[1]{``{\fontencoding{OT1}\gnusselectttfont{}#1}''}
57 \newcommand{\gnuslisp}[1]{\gnustt{#1}}
58 \newcommand{\gnuskbd}[1]{`\gnustt{#1}'}
59 \newcommand{\gnuskey}[1]{`\gnustt{#1}'}
60 \newcommand{\gnusfile}[1]{`\gnustt{#1}'}
61 \newcommand{\gnusdfn}[1]{\textit{#1}}
62 \newcommand{\gnusi}[1]{\textit{#1}}
63 \newcommand{\gnusstrong}[1]{\textbf{#1}}
64 \newcommand{\gnusemph}[1]{\textit{#1}}
65 \newcommand{\gnusvar}[1]{{\fontsize{10pt}{10}\selectfont\textsl{\textsf{#1}}}}
66 \newcommand{\gnussc}[1]{\textsc{#1}}
67 \newcommand{\gnustitle}[1]{{\huge\textbf{#1}}}
68 \newcommand{\gnusversion}[1]{{\small\textit{#1}}}
69 \newcommand{\gnusauthor}[1]{{\large\textbf{#1}}}
70 \newcommand{\gnusresult}[1]{\gnustt{=> #1}}
72 \newcommand{\gnusbullet}{{${\bullet}$}}
73 \newcommand{\gnusdollar}{\$}
74 \newcommand{\gnusampersand}{\&}
75 \newcommand{\gnuspercent}{\%}
76 \newcommand{\gnushash}{\#}
77 \newcommand{\gnushat}{\symbol{"5E}}
78 \newcommand{\gnusunderline}{\symbol{"5F}}
79 \newcommand{\gnusnot}{$\neg$}
80 \newcommand{\gnustilde}{\symbol{"7E}}
81 \newcommand{\gnusless}{{$<$}}
82 \newcommand{\gnusgreater}{{$>$}}
83 \newcommand{\gnusbraceleft}{{$>$}}
84 \newcommand{\gnusbraceright}{{$>$}}
86 \newcommand{\gnushead}{\raisebox{-1cm}{\epsfig{figure=ps/gnus-head,height=1cm}}}
87 \newcommand{\gnusinteresting}{
88 \marginpar[\mbox{}\hfill\gnushead]{\gnushead}
91 \newcommand{\gnuscleardoublepage}{\ifodd\count0\mbox{}\clearpage\thispagestyle{empty}\mbox{}\clearpage\else\clearpage\fi}
93 \newcommand{\gnuspagechapter}[1]{
100 \newcommand{\gnuschapter}[2]{
102 \ifdim \gnusdimen = 0pt\setcounter{page}{1}\pagestyle{gnus}\pagenumbering{arabic} \gnusdimen 1pt\fi
104 \renewcommand{\gnussectionname}{}
105 \renewcommand{\gnuschaptername}{#2}
106 \thispagestyle{empty}
108 \begin{picture}(500,500)(0,0)
109 \put(480,350){\makebox(0,0)[tr]{#1}}
110 \put(40,300){\makebox(500,50)[bl]{{\Huge\bf{#2}}}}
115 \newcommand{\gnusfigure}[3]{
117 \mbox{}\ifodd\count0\hspace*{-0.8cm}\else\hspace*{-3cm}\fi\begin{picture}(440,#2)
124 \newcommand{\gnusicon}[1]{
125 \marginpar[\mbox{}\hfill\raisebox{-1.5cm}{\epsfig{figure=ps/#1-up,height=1.5cm}}]{\raisebox{-1cm}{\epsfig{figure=ps/#1-up,height=1cm}}}
128 \newcommand{\gnuspicon}[1]{
129 \margindex{\epsfig{figure=#1,width=2cm}}
132 \newcommand{\gnusxface}[2]{
133 \margindex{\epsfig{figure=#1,width=1cm}\epsfig{figure=#2,width=1cm}}
136 \newcommand{\gnussmiley}[2]{
137 \margindex{\makebox[2cm]{\hfill\epsfig{figure=#1,width=0.5cm}\hfill\epsfig{figure=#2,width=0.5cm}\hfill}}
140 \newcommand{\gnusitemx}[1]{\mbox{}\vspace*{-\itemsep}\vspace*{-\parsep}\item#1}
142 \newcommand{\gnussection}[1]{
143 \renewcommand{\gnussectionname}{#1}
147 \newenvironment{codelist}%
152 \newenvironment{kbdlist}%
158 \newenvironment{dfnlist}%
163 \newenvironment{stronglist}%
168 \newenvironment{samplist}%
173 \newenvironment{varlist}%
178 \newenvironment{emphlist}%
183 \newlength\gnusheadtextwidth
184 \setlength{\gnusheadtextwidth}{\headtextwidth}
185 \addtolength{\gnusheadtextwidth}{1cm}
187 \newpagestyle{gnuspreamble}%
192 \hspace*{-0.23cm}\underline{\makebox[\gnusheadtextwidth]{\mbox{}}\textbf{\hfill\roman{page}}}
196 \hspace*{-3.25cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\roman{page}\hfill\mbox{}}}
205 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
207 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
212 \newpagestyle{gnusindex}%
217 \hspace*{-0.23cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\gnuschaptername\hfill\arabic{page}}}}
221 \hspace*{-3.25cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{page}\hfill\gnuschaptername}}}
229 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
231 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
241 \makebox[12cm]{\hspace*{3.1cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{chapter}.\arabic{section}} \textbf{\gnussectionname\hfill\arabic{page}}}}}
245 \makebox[12cm]{\hspace*{-2.95cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{page}\hfill\gnuschaptername}}}}
253 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
255 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
260 \pagenumbering{roman}
261 \pagestyle{gnuspreamble}
271 %\addtolength{\oddsidemargin}{-5cm}
272 %\addtolength{\evensidemargin}{-5cm}
274 \addtolength{\textheight}{2cm}
276 \gnustitle{\gnustitlename}\hfill\gnusversion{\gnusversionname}\\
279 \hspace*{0cm}\epsfig{figure=ps/gnus-big-logo,height=15cm}
282 \gnusauthor{by Lars Magne Ingebrigtsen}
289 \thispagestyle{empty}
291 Copyright \copyright{} 1995, 1996, 1997, 1998, 1999, 2000, 2001,
293 Free Software Foundation, Inc.
296 Permission is granted to copy, distribute and/or modify this document
297 under the terms of the GNU Free Documentation License, Version 1.1 or
298 any later version published by the Free Software Foundation; with no
299 Invariant Sections, with the Front-Cover texts being ``A GNU
300 Manual'', and with the Back-Cover Texts as in (a) below. A copy of the
301 license is included in the section entitled ``GNU Free Documentation
302 License'' in the Emacs manual.
304 (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
305 this GNU Manual, like GNU software. Copies published by the Free
306 Software Foundation raise funds for GNU development.''
308 This document is part of a collection distributed under the GNU Free
309 Documentation License. If you want to distribute this document
310 separately from the collection, you can do so by adding a copy of the
311 license to the document, as described in section 6 of the license.
319 This file documents gnus, the GNU Emacs newsreader.
321 Copyright (C) 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003
322 Free Software Foundation, Inc.
324 Permission is granted to copy, distribute and/or modify this document
325 under the terms of the GNU Free Documentation License, Version 1.1 or
326 any later version published by the Free Software Foundation; with the
327 Invariant Sections being none, with the Front-Cover texts being ``A GNU
328 Manual'', and with the Back-Cover Texts as in (a) below. A copy of the
329 license is included in the section entitled ``GNU Free Documentation
330 License'' in the Emacs manual.
332 (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
333 this GNU Manual, like GNU software. Copies published by the Free
334 Software Foundation raise funds for GNU development.''
336 This document is part of a collection distributed under the GNU Free
337 Documentation License. If you want to distribute this document
338 separately from the collection, you can do so by adding a copy of the
339 license to the document, as described in section 6 of the license.
345 @title T-gnus 6.15 Manual
347 @author by Lars Magne Ingebrigtsen
350 @vskip 0pt plus 1filll
351 Copyright @copyright{} 1995, 1996, 1997, 1998, 1999, 2000, 2001,
353 Free Software Foundation, Inc.
355 Permission is granted to copy, distribute and/or modify this document
356 under the terms of the GNU Free Documentation License, Version 1.1 or
357 any later version published by the Free Software Foundation; with no
358 Invariant Sections, with the Front-Cover texts being ``A GNU
359 Manual'', and with the Back-Cover Texts as in (a) below. A copy of the
360 license is included in the section entitled ``GNU Free Documentation
361 License'' in the Emacs manual.
363 (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
364 this GNU Manual, like GNU software. Copies published by the Free
365 Software Foundation raise funds for GNU development.''
367 This document is part of a collection distributed under the GNU Free
368 Documentation License. If you want to distribute this document
369 separately from the collection, you can do so by adding a copy of the
370 license to the document, as described in section 6 of the license.
379 @top The gnus Newsreader
383 You can read news (and mail) from within Emacs by using gnus. The news
384 can be gotten by any nefarious means you can think of---@sc{nntp}, local
385 spool or your mbox file. All at the same time, if you want to push your
388 T-gnus provides @sc{mime} features based on @sc{semi} API. So T-gnus
389 supports your right to read strange messages including big images or
390 other various kinds of formats. T-gnus also supports
391 internationalization/localization and multiscript features based on MULE
392 API. So T-gnus does not discriminate various language communities.
393 Oh, if you are a Klingon, please wait Unicode Next Generation.
395 This manual corresponds to T-gnus 6.15.
406 Gnus is the advanced, self-documenting, customizable, extensible
407 unreal-time newsreader for GNU Emacs.
409 Oops. That sounds oddly familiar, so let's start over again to avoid
410 being accused of plagiarism:
412 Gnus is a message-reading laboratory. It will let you look at just
413 about anything as if it were a newsgroup. You can read mail with it,
414 you can browse directories with it, you can @code{ftp} with it---you
415 can even read news with it!
417 Gnus tries to empower people who read news the same way Emacs empowers
418 people who edit text. Gnus sets no limits to what the user should be
419 allowed to do. Users are encouraged to extend gnus to make it behave
420 like they want it to behave. A program should not control people;
421 people should be empowered to do what they want by using (or abusing)
427 * Starting Up:: Finding news can be a pain.
428 * Group Buffer:: Selecting, subscribing and killing groups.
429 * Summary Buffer:: Reading, saving and posting articles.
430 * Article Buffer:: Displaying and handling articles.
431 * Composing Messages:: Information on sending mail and news.
432 * Select Methods:: Gnus reads all messages from various select methods.
433 * Scoring:: Assigning values to articles.
434 * Various:: General purpose settings.
435 * The End:: Farewell and goodbye.
436 * Appendices:: Terminology, Emacs intro, FAQ, History, Internals.
437 * Index:: Variable, function and concept index.
438 * Key Index:: Key Index.
440 Other related manuals
442 * Message:(message). Composing messages.
443 * Emacs-MIME:(emacs-mime). Composing messages; MIME-specific parts.
444 * Sieve:(sieve). Managing Sieve scripts in Emacs.
445 * PGG:(pgg). PGP/MIME with Gnus.
448 --- The Detailed Node Listing ---
452 * Finding the News:: Choosing a method for getting news.
453 * The First Time:: What does Gnus do the first time you start it?
454 * The Server is Down:: How can I read my mail then?
455 * Slave Gnusae:: You can have more than one Gnus active at a time.
456 * Fetching a Group:: Starting Gnus just to read a group.
457 * New Groups:: What is Gnus supposed to do with new groups?
458 * Changing Servers:: You may want to move from one server to another.
459 * Startup Files:: Those pesky startup files---@file{.newsrc}.
460 * Auto Save:: Recovering from a crash.
461 * The Active File:: Reading the active file over a slow line Takes Time.
462 * Startup Variables:: Other variables you might change.
466 * Checking New Groups:: Determining what groups are new.
467 * Subscription Methods:: What Gnus should do with new groups.
468 * Filtering New Groups:: Making Gnus ignore certain new groups.
472 * Group Buffer Format:: Information listed and how you can change it.
473 * Group Maneuvering:: Commands for moving in the group buffer.
474 * Selecting a Group:: Actually reading news.
475 * Subscription Commands:: Unsubscribing, killing, subscribing.
476 * Group Data:: Changing the info for a group.
477 * Group Levels:: Levels? What are those, then?
478 * Group Score:: A mechanism for finding out what groups you like.
479 * Marking Groups:: You can mark groups for later processing.
480 * Foreign Groups:: Creating and editing groups.
481 * Group Parameters:: Each group may have different parameters set.
482 * Listing Groups:: Gnus can list various subsets of the groups.
483 * Sorting Groups:: Re-arrange the group order.
484 * Group Maintenance:: Maintaining a tidy @file{.newsrc} file.
485 * Browse Foreign Server:: You can browse a server. See what it has to offer.
486 * Exiting Gnus:: Stop reading news and get some work done.
487 * Group Topics:: A folding group mode divided into topics.
488 * Misc Group Stuff:: Other stuff that you can to do.
492 * Group Line Specification:: Deciding how the group buffer is to look.
493 * Group Modeline Specification:: The group buffer modeline.
494 * Group Highlighting:: Having nice colors in the group buffer.
498 * Topic Commands:: Interactive E-Z commands.
499 * Topic Variables:: How to customize the topics the Lisp Way.
500 * Topic Sorting:: Sorting each topic individually.
501 * Topic Topology:: A map of the world.
502 * Topic Parameters:: Parameters that apply to all groups in a topic.
506 * Scanning New Messages:: Asking Gnus to see whether new messages have arrived.
507 * Group Information:: Information and help on groups and Gnus.
508 * Group Timestamp:: Making Gnus keep track of when you last read a group.
509 * File Commands:: Reading and writing the Gnus files.
510 * Sieve Commands:: Managing Sieve scripts.
514 * Summary Buffer Format:: Deciding how the summary buffer is to look.
515 * Summary Maneuvering:: Moving around the summary buffer.
516 * Choosing Articles:: Reading articles.
517 * Paging the Article:: Scrolling the current article.
518 * Reply Followup and Post:: Posting articles.
519 * Delayed Articles:: Send articles at a later time.
520 * Marking Articles:: Marking articles as read, expirable, etc.
521 * Limiting:: You can limit the summary buffer.
522 * Threading:: How threads are made.
523 * Sorting the Summary Buffer:: How articles and threads are sorted.
524 * Asynchronous Fetching:: Gnus might be able to pre-fetch articles.
525 * Article Caching:: You may store articles in a cache.
526 * Persistent Articles:: Making articles expiry-resistant.
527 * Article Backlog:: Having already read articles hang around.
528 * Saving Articles:: Ways of customizing article saving.
529 * Decoding Articles:: Gnus can treat series of (uu)encoded articles.
530 * Article Treatment:: The article buffer can be mangled at will.
531 * MIME Commands:: Doing MIMEy things with the articles.
532 * Charsets:: Character set issues.
533 * Article Commands:: Doing various things with the article buffer.
534 * Summary Sorting:: Sorting the summary buffer in various ways.
535 * Finding the Parent:: No child support? Get the parent.
536 * Alternative Approaches:: Reading using non-default summaries.
537 * Tree Display:: A more visual display of threads.
538 * Mail Group Commands:: Some commands can only be used in mail groups.
539 * Various Summary Stuff:: What didn't fit anywhere else.
540 * Exiting the Summary Buffer:: Returning to the Group buffer,
541 or reselecting the current group.
542 * Crosspost Handling:: How crossposted articles are dealt with.
543 * Duplicate Suppression:: An alternative when crosspost handling fails.
544 * Security:: Decrypt and Verify.
545 * Mailing List:: Mailing list minor mode.
547 Summary Buffer Format
549 * Summary Buffer Lines:: You can specify how summary lines should look.
550 * To From Newsgroups:: How to not display your own name.
551 * Summary Buffer Mode Line:: You can say how the mode line should look.
552 * Summary Highlighting:: Making the summary buffer all pretty and nice.
556 * Choosing Commands:: Commands for choosing articles.
557 * Choosing Variables:: Variables that influence these commands.
559 Reply, Followup and Post
561 * Summary Mail Commands:: Sending mail.
562 * Summary Post Commands:: Sending news.
563 * Summary Message Commands:: Other Message-related commands.
564 * Canceling and Superseding::
568 * Unread Articles:: Marks for unread articles.
569 * Read Articles:: Marks for read articles.
570 * Other Marks:: Marks that do not affect readedness.
572 * Generic Marking Commands::
573 * Setting Process Marks::
577 * Setting Marks:: How to set and remove marks.
578 * Generic Marking Commands:: How to customize the marking.
579 * Setting Process Marks:: How to mark articles for later processing.
583 * Customizing Threading:: Variables you can change to affect the threading.
584 * Thread Commands:: Thread based commands in the summary buffer.
586 Customizing Threading
588 * Loose Threads:: How Gnus gathers loose threads into bigger threads.
589 * Filling In Threads:: Making the threads displayed look fuller.
590 * More Threading:: Even more variables for fiddling with threads.
591 * Low-Level Threading:: You thought it was over... but you were wrong!
595 * Uuencoded Articles:: Uudecode articles.
596 * Shell Archives:: Unshar articles.
597 * PostScript Files:: Split PostScript.
598 * Other Files:: Plain save and binhex.
599 * Decoding Variables:: Variables for a happy decoding.
600 * Viewing Files:: You want to look at the result of the decoding?
604 * Rule Variables:: Variables that say how a file is to be viewed.
605 * Other Decode Variables:: Other decode variables.
606 * Uuencoding and Posting:: Variables for customizing uuencoding.
610 * Article Highlighting:: You want to make the article look like fruit salad.
611 * Article Fontisizing:: Making emphasized text look nice.
612 * Article Hiding:: You also want to make certain info go away.
613 * Article Washing:: Lots of way-neat functions to make life better.
614 * Article Header:: Doing various header transformations.
615 * Article Buttons:: Click on URLs, Message-IDs, addresses and the like.
616 * Article Date:: Grumble, UT!
617 * Article Display:: Display various stuff---X-Face, Picons, Smileys
618 * Article Signature:: What is a signature?
619 * Article Miscellania:: Various other stuff.
621 Alternative Approaches
623 * Pick and Read:: First mark articles and then read them.
624 * Binary Groups:: Auto-decode all articles.
626 Various Summary Stuff
628 * Summary Group Information:: Information oriented commands.
629 * Searching for Articles:: Multiple article commands.
630 * Summary Generation Commands::
631 * Really Various Summary Commands:: Those pesky non-conformant commands.
635 * Hiding Headers:: Deciding what headers should be displayed.
636 * Using MIME:: Pushing articles through @sc{mime} before reading them.
637 * Customizing Articles:: Tailoring the look of the articles.
638 * Article Keymap:: Keystrokes available in the article buffer.
639 * Misc Article:: Other stuff.
643 * Mail:: Mailing and replying.
644 * Posting Server:: What server should you post and mail via?
645 * Mail and Post:: Mailing and posting at the same time.
646 * Archived Messages:: Where Gnus stores the messages you've sent.
647 * Posting Styles:: An easier way to specify who you are.
648 * Drafts:: Postponing messages and rejected messages.
649 * Rejected Articles:: What happens if the server doesn't like your article?
650 * Signing and encrypting:: How to compose secure messages.
654 * Server Buffer:: Making and editing virtual servers.
655 * Getting News:: Reading USENET news with Gnus.
656 * Getting Mail:: Reading your personal mail with Gnus.
657 * Browsing the Web:: Getting messages from a plethora of Web sources.
658 * IMAP:: Using Gnus as a @sc{imap} client.
659 * Other Sources:: Reading directories, files, SOUP packets.
660 * Combined Groups:: Combining groups into one group.
661 * Gnus Unplugged:: Reading news and mail offline.
665 * Server Buffer Format:: You can customize the look of this buffer.
666 * Server Commands:: Commands to manipulate servers.
667 * Example Methods:: Examples server specifications.
668 * Creating a Virtual Server:: An example session.
669 * Server Variables:: Which variables to set.
670 * Servers and Methods:: You can use server names as select methods.
671 * Unavailable Servers:: Some servers you try to contact may be down.
675 * NNTP:: Reading news from an @sc{nntp} server.
676 * News Spool:: Reading news from the local spool.
680 * Direct Functions:: Connecting directly to the server.
681 * Indirect Functions:: Connecting indirectly to the server.
682 * Common Variables:: Understood by several connection functions.
686 * Mail in a Newsreader:: Important introductory notes.
687 * Getting Started Reading Mail:: A simple cookbook example.
688 * Splitting Mail:: How to create mail groups.
689 * Mail Sources:: How to tell Gnus where to get mail from.
690 * Mail Back End Variables:: Variables for customizing mail handling.
691 * Fancy Mail Splitting:: Gnus can do hairy splitting of incoming mail.
692 * Group Mail Splitting:: Use group customize to drive mail splitting.
693 * Incorporating Old Mail:: What about the old mail you have?
694 * Expiring Mail:: Getting rid of unwanted mail.
695 * Washing Mail:: Removing gruft from the mail you get.
696 * Duplicates:: Dealing with duplicated mail.
697 * Not Reading Mail:: Using mail back ends for reading other files.
698 * Choosing a Mail Back End:: Gnus can read a variety of mail formats.
702 * Mail Source Specifiers:: How to specify what a mail source is.
703 * Mail Source Customization:: Some variables that influence things.
704 * Fetching Mail:: Using the mail source specifiers.
706 Choosing a Mail Back End
708 * Unix Mail Box:: Using the (quite) standard Un*x mbox.
709 * Rmail Babyl:: Emacs programs use the rmail babyl format.
710 * Mail Spool:: Store your mail in a private spool?
711 * MH Spool:: An mhspool-like back end.
712 * Mail Folders:: Having one file for each group.
713 * Comparing Mail Back Ends:: An in-depth looks at pros and cons.
718 * Web Searches:: Creating groups from articles that match a string.
719 * Slashdot:: Reading the Slashdot comments.
720 * Ultimate:: The Ultimate Bulletin Board systems.
721 * Web Archive:: Reading mailing list archived on web.
722 * RSS:: Reading RDF site summary.
723 * Customizing w3:: Doing stuff to Emacs/w3 from Gnus.
727 * Splitting in IMAP:: Splitting mail with nnimap.
728 * Expiring in IMAP:: Expiring mail with nnimap.
729 * Editing IMAP ACLs:: Limiting/enabling other users access to a mailbox.
730 * Expunging mailboxes:: Equivalent of a "compress mailbox" button.
731 * A note on namespaces:: How to (not) use IMAP namespace in Gnus.
735 * Directory Groups:: You can read a directory as if it was a newsgroup.
736 * Anything Groups:: Dired? Who needs dired?
737 * Document Groups:: Single files can be the basis of a group.
738 * SOUP:: Reading @sc{soup} packets ``offline''.
739 * Mail-To-News Gateways:: Posting articles via mail-to-news gateways.
743 * Document Server Internals:: How to add your own document types.
747 * SOUP Commands:: Commands for creating and sending @sc{soup} packets
748 * SOUP Groups:: A back end for reading @sc{soup} packets.
749 * SOUP Replies:: How to enable @code{nnsoup} to take over mail and news.
753 * Virtual Groups:: Combining articles from many groups.
754 * Kibozed Groups:: Looking through parts of the newsfeed for articles.
758 * Agent Basics:: How it all is supposed to work.
759 * Agent Categories:: How to tell the Gnus Agent what to download.
760 * Agent Commands:: New commands for all the buffers.
761 * Agent as Cache:: The Agent is a big cache too.
762 * Agent Expiry:: How to make old articles go away.
763 * Agent and IMAP:: How to use the Agent with IMAP.
764 * Outgoing Messages:: What happens when you post/mail something?
765 * Agent Variables:: Customizing is fun.
766 * Example Setup:: An example @file{.gnus.el} file for offline people.
767 * Batching Agents:: How to fetch news from a @code{cron} job.
768 * Agent Caveats:: What you think it'll do and what it does.
772 * Category Syntax:: What a category looks like.
773 * Category Buffer:: A buffer for maintaining categories.
774 * Category Variables:: Customize'r'Us.
778 * Group Agent Commands::
779 * Summary Agent Commands::
780 * Server Agent Commands::
784 * Summary Score Commands:: Adding score entries for the current group.
785 * Group Score Commands:: General score commands.
786 * Score Variables:: Customize your scoring. (My, what terminology).
787 * Score File Format:: What a score file may contain.
788 * Score File Editing:: You can edit score files by hand as well.
789 * Adaptive Scoring:: Big Sister Gnus knows what you read.
790 * Home Score File:: How to say where new score entries are to go.
791 * Followups To Yourself:: Having Gnus notice when people answer you.
792 * Scoring On Other Headers:: Scoring on non-standard headers.
793 * Scoring Tips:: How to score effectively.
794 * Reverse Scoring:: That problem child of old is not problem.
795 * Global Score Files:: Earth-spanning, ear-splitting score files.
796 * Kill Files:: They are still here, but they can be ignored.
797 * Converting Kill Files:: Translating kill files to score files.
798 * GroupLens:: Getting predictions on what you like to read.
799 * Advanced Scoring:: Using logical expressions to build score rules.
800 * Score Decays:: It can be useful to let scores wither away.
804 * Using GroupLens:: How to make Gnus use GroupLens.
805 * Rating Articles:: Letting GroupLens know how you rate articles.
806 * Displaying Predictions:: Displaying predictions given by GroupLens.
807 * GroupLens Variables:: Customizing GroupLens.
811 * Advanced Scoring Syntax:: A definition.
812 * Advanced Scoring Examples:: What they look like.
813 * Advanced Scoring Tips:: Getting the most out of it.
817 * Process/Prefix:: A convention used by many treatment commands.
818 * Interactive:: Making Gnus ask you many questions.
819 * Symbolic Prefixes:: How to supply some Gnus functions with options.
820 * Formatting Variables:: You can specify what buffers should look like.
821 * Window Layout:: Configuring the Gnus buffer windows.
822 * Faces and Fonts:: How to change how faces look.
823 * Compilation:: How to speed Gnus up.
824 * Mode Lines:: Displaying information in the mode lines.
825 * Highlighting and Menus:: Making buffers look all nice and cozy.
826 * Buttons:: Get tendinitis in ten easy steps!
827 * Daemons:: Gnus can do things behind your back.
828 * NoCeM:: How to avoid spam and other fatty foods.
829 * Undo:: Some actions can be undone.
830 * Predicate Specifiers:: Specifying predicates.
831 * Moderation:: What to do if you're a moderator.
832 * Image Enhancements:: Modern versions of Emacs/XEmacs can display images.
833 * Fuzzy Matching:: What's the big fuzz?
834 * Thwarting Email Spam:: A how-to on avoiding unsolicited commercial email.
835 * Various Various:: Things that are really various.
839 * Formatting Basics:: A formatting variable is basically a format string.
840 * Mode Line Formatting:: Some rules about mode line formatting variables.
841 * Advanced Formatting:: Modifying output in various ways.
842 * User-Defined Specs:: Having Gnus call your own functions.
843 * Formatting Fonts:: Making the formatting look colorful and nice.
844 * Positioning Point:: Moving point to a position after an operation.
845 * Tabulation:: Tabulating your output.
846 * Wide Characters:: Dealing with wide characters.
850 * Picons:: How to display pictures of what you're reading.
851 * Smileys:: Show all those happy faces the way they were meant to be shown.
852 * X-Face:: Display a funky, teensy black-and-white image.
853 * Toolbar:: Click'n'drool.
854 * XVarious:: Other XEmacsy Gnusey variables.
858 * Picon Basics:: What are picons and How do I get them.
859 * Picon Requirements:: Don't go further if you aren't using XEmacs.
860 * Easy Picons:: Displaying Picons---the easy way.
861 * Hard Picons:: The way you should do it. You'll learn something.
862 * Picon Useless Configuration:: Other variables you can trash/tweak/munge/play with.
866 * The problem of spam:: Some background, and some solutions
867 * Anti-Spam Basics:: Simple steps to reduce the amount of spam.
868 * SpamAssassin:: How to use external anti-spam tools.
869 * Hashcash:: Reduce spam by burning CPU time.
870 * Filtering Spam Using spam.el::
871 * Filtering Spam Using Statistics (spam-stat.el)::
875 * XEmacs:: Requirements for installing under XEmacs.
876 * History:: How Gnus got where it is today.
877 * On Writing Manuals:: Why this is not a beginner's guide.
878 * Terminology:: We use really difficult, like, words here.
879 * Customization:: Tailoring Gnus to your needs.
880 * Troubleshooting:: What you might try if things do not work.
881 * Gnus Reference Guide:: Rilly, rilly technical stuff.
882 * Emacs for Heathens:: A short introduction to Emacsian terms.
883 * Frequently Asked Questions::
887 * Gnus Versions:: What Gnus versions have been released.
888 * Other Gnus Versions:: Other Gnus versions that also have been released.
889 * Why?:: What's the point of Gnus?
890 * Compatibility:: Just how compatible is Gnus with @sc{gnus}?
891 * Conformity:: Gnus tries to conform to all standards.
892 * Emacsen:: Gnus can be run on a few modern Emacsen.
893 * Gnus Development:: How Gnus is developed.
894 * Contributors:: Oodles of people.
895 * New Features:: Pointers to some of the new stuff in Gnus.
899 * ding Gnus:: New things in Gnus 5.0/5.1, the first new Gnus.
900 * September Gnus:: The Thing Formally Known As Gnus 5.2/5.3.
901 * Red Gnus:: Third time best---Gnus 5.4/5.5.
902 * Quassia Gnus:: Two times two is four, or Gnus 5.6/5.7.
903 * Pterodactyl Gnus:: Pentad also starts with P, AKA Gnus 5.8/5.9.
907 * Slow/Expensive Connection:: You run a local Emacs and get the news elsewhere.
908 * Slow Terminal Connection:: You run a remote Emacs.
909 * Little Disk Space:: You feel that having large setup files is icky.
910 * Slow Machine:: You feel like buying a faster machine.
914 * Gnus Utility Functions:: Common functions and variable to use.
915 * Back End Interface:: How Gnus communicates with the servers.
916 * Score File Syntax:: A BNF definition of the score file standard.
917 * Headers:: How Gnus stores headers internally.
918 * Ranges:: A handy format for storing mucho numbers.
919 * Group Info:: The group info format.
920 * Extended Interactive:: Symbolic prefixes and stuff.
921 * Emacs/XEmacs Code:: Gnus can be run under all modern Emacsen.
922 * Various File Formats:: Formats of files that Gnus use.
926 * Required Back End Functions:: Functions that must be implemented.
927 * Optional Back End Functions:: Functions that need not be implemented.
928 * Error Messaging:: How to get messages and report errors.
929 * Writing New Back Ends:: Extending old back ends.
930 * Hooking New Back Ends Into Gnus:: What has to be done on the Gnus end.
931 * Mail-like Back Ends:: Some tips on mail back ends.
935 * Active File Format:: Information on articles and groups available.
936 * Newsgroups File Format:: Group descriptions.
940 * Keystrokes:: Entering text and executing commands.
941 * Emacs Lisp:: The built-in Emacs programming language.
947 @chapter Starting gnus
952 If your system administrator has set things up properly, starting gnus
953 and reading news is extremely easy---you just type @kbd{M-x gnus} in
956 @findex gnus-other-frame
957 @kindex M-x gnus-other-frame
958 If you want to start gnus in a different frame, you can use the command
959 @kbd{M-x gnus-other-frame} instead.
961 If things do not go smoothly at startup, you have to twiddle some
962 variables in your @file{~/.gnus} file. This file is similar to
963 @file{~/.emacs}, but is read when gnus starts.
965 If you puzzle at any terms used in this manual, please refer to the
966 terminology section (@pxref{Terminology}).
969 * Finding the News:: Choosing a method for getting news.
970 * The First Time:: What does Gnus do the first time you start it?
971 * The Server is Down:: How can I read my mail then?
972 * Slave Gnusae:: You can have more than one Gnus active at a time.
973 * Fetching a Group:: Starting Gnus just to read a group.
974 * New Groups:: What is Gnus supposed to do with new groups?
975 * Changing Servers:: You may want to move from one server to another.
976 * Startup Files:: Those pesky startup files---@file{.newsrc}.
977 * Auto Save:: Recovering from a crash.
978 * The Active File:: Reading the active file over a slow line Takes Time.
979 * Startup Variables:: Other variables you might change.
983 @node Finding the News
984 @section Finding the News
987 @vindex gnus-select-method
989 The @code{gnus-select-method} variable says where gnus should look for
990 news. This variable should be a list where the first element says
991 @dfn{how} and the second element says @dfn{where}. This method is your
992 native method. All groups not fetched with this method are
995 For instance, if the @samp{news.somewhere.edu} @sc{nntp} server is where
996 you want to get your daily dosage of news from, you'd say:
999 (setq gnus-select-method '(nntp "news.somewhere.edu"))
1002 If you want to read directly from the local spool, say:
1005 (setq gnus-select-method '(nnspool ""))
1008 If you can use a local spool, you probably should, as it will almost
1009 certainly be much faster. But do not use the local spool if your
1010 server is running Leafnode; in this case, use @code{(nntp "localhost")}.
1012 @vindex gnus-nntpserver-file
1014 @cindex @sc{nntp} server
1015 If this variable is not set, gnus will take a look at the
1016 @code{NNTPSERVER} environment variable. If that variable isn't set,
1017 gnus will see whether @code{gnus-nntpserver-file}
1018 (@file{/etc/nntpserver} by default) has any opinions on the matter. If
1019 that fails as well, gnus will try to use the machine running Emacs as an @sc{nntp} server. That's a long shot, though.
1021 @vindex gnus-nntp-server
1022 If @code{gnus-nntp-server} is set, this variable will override
1023 @code{gnus-select-method}. You should therefore set
1024 @code{gnus-nntp-server} to @code{nil}, which is what it is by default.
1026 @vindex gnus-secondary-servers
1027 @vindex gnus-nntp-server
1028 You can also make gnus prompt you interactively for the name of an
1029 @sc{nntp} server. If you give a non-numerical prefix to @code{gnus}
1030 (i.e., @kbd{C-u M-x gnus}), gnus will let you choose between the servers
1031 in the @code{gnus-secondary-servers} list (if any). You can also just
1032 type in the name of any server you feel like visiting. (Note that this
1033 will set @code{gnus-nntp-server}, which means that if you then @kbd{M-x
1034 gnus} later in the same Emacs session, Gnus will contact the same
1037 @findex gnus-group-browse-foreign-server
1039 However, if you use one @sc{nntp} server regularly and are just
1040 interested in a couple of groups from a different server, you would be
1041 better served by using the @kbd{B} command in the group buffer. It will
1042 let you have a look at what groups are available, and you can subscribe
1043 to any of the groups you want to. This also makes @file{.newsrc}
1044 maintenance much tidier. @xref{Foreign Groups}.
1046 @vindex gnus-secondary-select-methods
1048 A slightly different approach to foreign groups is to set the
1049 @code{gnus-secondary-select-methods} variable. The select methods
1050 listed in this variable are in many ways just as native as the
1051 @code{gnus-select-method} server. They will also be queried for active
1052 files during startup (if that's required), and new newsgroups that
1053 appear on these servers will be subscribed (or not) just as native
1056 For instance, if you use the @code{nnmbox} back end to read your mail,
1057 you would typically set this variable to
1060 (setq gnus-secondary-select-methods '((nnmbox "")))
1064 @node The First Time
1065 @section The First Time
1066 @cindex first time usage
1068 If no startup files exist, gnus will try to determine what groups should
1069 be subscribed by default.
1071 @vindex gnus-default-subscribed-newsgroups
1072 If the variable @code{gnus-default-subscribed-newsgroups} is set, gnus
1073 will subscribe you to just those groups in that list, leaving the rest
1074 killed. Your system administrator should have set this variable to
1077 Since she hasn't, gnus will just subscribe you to a few arbitrarily
1078 picked groups (i.e., @samp{*.newusers}). (@dfn{Arbitrary} is defined
1079 here as @dfn{whatever Lars thinks you should read}.)
1081 You'll also be subscribed to the gnus documentation group, which should
1082 help you with most common problems.
1084 If @code{gnus-default-subscribed-newsgroups} is @code{t}, gnus will just
1085 use the normal functions for handling new groups, and not do anything
1089 @node The Server is Down
1090 @section The Server is Down
1091 @cindex server errors
1093 If the default server is down, gnus will understandably have some
1094 problems starting. However, if you have some mail groups in addition to
1095 the news groups, you may want to start gnus anyway.
1097 Gnus, being the trusting sort of program, will ask whether to proceed
1098 without a native select method if that server can't be contacted. This
1099 will happen whether the server doesn't actually exist (i.e., you have
1100 given the wrong address) or the server has just momentarily taken ill
1101 for some reason or other. If you decide to continue and have no foreign
1102 groups, you'll find it difficult to actually do anything in the group
1103 buffer. But, hey, that's your problem. Blllrph!
1105 @findex gnus-no-server
1106 @kindex M-x gnus-no-server
1108 If you know that the server is definitely down, or you just want to read
1109 your mail without bothering with the server at all, you can use the
1110 @code{gnus-no-server} command to start gnus. That might come in handy
1111 if you're in a hurry as well. This command will not attempt to contact
1112 your primary server---instead, it will just activate all groups on level
1113 1 and 2. (You should preferably keep no native groups on those two
1114 levels.) Also @pxref{Group Levels}.
1118 @section Slave Gnusae
1121 You might want to run more than one Emacs with more than one gnus at the
1122 same time. If you are using different @file{.newsrc} files (e.g., if you
1123 are using the two different gnusae to read from two different servers),
1124 that is no problem whatsoever. You just do it.
1126 The problem appears when you want to run two Gnusae that use the same
1127 @code{.newsrc} file.
1129 To work around that problem some, we here at the Think-Tank at the gnus
1130 Towers have come up with a new concept: @dfn{Masters} and
1131 @dfn{slaves}. (We have applied for a patent on this concept, and have
1132 taken out a copyright on those words. If you wish to use those words in
1133 conjunction with each other, you have to send $1 per usage instance to
1134 me. Usage of the patent (@dfn{Master/Slave Relationships In Computer
1135 Applications}) will be much more expensive, of course.)
1137 Anyway, you start one gnus up the normal way with @kbd{M-x gnus} (or
1138 however you do it). Each subsequent slave gnusae should be started with
1139 @kbd{M-x gnus-slave}. These slaves won't save normal @file{.newsrc}
1140 files, but instead save @dfn{slave files} that contain information only
1141 on what groups have been read in the slave session. When a master gnus
1142 starts, it will read (and delete) these slave files, incorporating all
1143 information from them. (The slave files will be read in the sequence
1144 they were created, so the latest changes will have precedence.)
1146 Information from the slave files has, of course, precedence over the
1147 information in the normal (i.e., master) @code{.newsrc} file.
1149 If the @code{.newsrc*} files have not been saved in the master when the
1150 slave starts, you may be prompted as to whether to read an auto-save
1151 file. If you answer "yes", the unsaved changes to the master will be
1152 incorporated into the slave. If you answer "no", the slave may see some
1153 messages as unread that have been read in the master.
1155 @node Fetching a Group
1156 @section Fetching a Group
1157 @cindex fetching a group
1159 @findex gnus-fetch-group
1160 It is sometimes convenient to be able to just say ``I want to read this
1161 group and I don't care whether gnus has been started or not''. This is
1162 perhaps more useful for people who write code than for users, but the
1163 command @code{gnus-fetch-group} provides this functionality in any case.
1164 It takes the group name as a parameter.
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, but I
1338 thought it would be nice to have two of these. This variable is more
1339 meant for setting some ground rules, while the other variable is used
1340 more for user fiddling. By default this variable makes all new groups
1341 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 @sc{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 @sc{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 Now, you all know about the @file{.newsrc} file. All subscription
1417 information is traditionally stored in this file.
1419 Things got a bit more complicated with @sc{gnus}. In addition to
1420 keeping the @file{.newsrc} file updated, it also used a file called
1421 @file{.newsrc.el} for storing all the information that didn't fit into
1422 the @file{.newsrc} file. (Actually, it also duplicated everything in
1423 the @file{.newsrc} file.) @sc{gnus} would read whichever one of these
1424 files was the most recently saved, which enabled people to swap between
1425 @sc{gnus} and other newsreaders.
1427 That was kinda silly, so Gnus went one better: In addition to the
1428 @file{.newsrc} and @file{.newsrc.el} files, Gnus also has a file called
1429 @file{.newsrc.eld}. It will read whichever of these files that are most
1430 recent, but it will never write a @file{.newsrc.el} file. You should
1431 never delete the @file{.newsrc.eld} file---it contains much information
1432 not stored in the @file{.newsrc} file.
1434 @vindex gnus-save-newsrc-file
1435 @vindex gnus-read-newsrc-file
1436 You can turn off writing the @file{.newsrc} file by setting
1437 @code{gnus-save-newsrc-file} to @code{nil}, which means you can delete
1438 the file and save some space, as well as exiting from gnus faster.
1439 However, this will make it impossible to use other newsreaders than
1440 gnus. But hey, who would want to, right? Similarly, setting
1441 @code{gnus-read-newsrc-file} to @code{nil} makes gnus ignore the
1442 @file{.newsrc} file and any @file{.newsrc-SERVER} files, which is
1443 convenient if you have a tendency to use Netscape once in a while.
1445 @vindex gnus-save-killed-list
1446 If @code{gnus-save-killed-list} (default @code{t}) is @code{nil}, Gnus
1447 will not save the list of killed groups to the startup file. This will
1448 save both time (when starting and quitting) and space (on disk). It
1449 will also mean that Gnus has no record of what groups are new or old,
1450 so the automatic new groups subscription methods become meaningless.
1451 You should always set @code{gnus-check-new-newsgroups} to @code{nil} or
1452 @code{ask-server} if you set this variable to @code{nil} (@pxref{New
1453 Groups}). This variable can also be a regular expression. If that's
1454 the case, remove all groups that do not match this regexp before
1455 saving. This can be useful in certain obscure situations that involve
1456 several servers where not all servers support @code{ask-server}.
1458 @vindex gnus-startup-file
1459 The @code{gnus-startup-file} variable says where the startup files are.
1460 The default value is @file{~/.newsrc}, with the Gnus (El Dingo) startup
1461 file being whatever that one is, with a @samp{.eld} appended.
1463 @vindex gnus-save-newsrc-hook
1464 @vindex gnus-save-quick-newsrc-hook
1465 @vindex gnus-save-standard-newsrc-hook
1466 @code{gnus-save-newsrc-hook} is called before saving any of the newsrc
1467 files, while @code{gnus-save-quick-newsrc-hook} is called just before
1468 saving the @file{.newsrc.eld} file, and
1469 @code{gnus-save-standard-newsrc-hook} is called just before saving the
1470 @file{.newsrc} file. The latter two are commonly used to turn version
1471 control on or off. Version control is on by default when saving the
1472 startup files. If you want to turn backup creation off, say something like:
1475 (defun turn-off-backup ()
1476 (set (make-local-variable 'backup-inhibited) t))
1478 (add-hook 'gnus-save-quick-newsrc-hook 'turn-off-backup)
1479 (add-hook 'gnus-save-standard-newsrc-hook 'turn-off-backup)
1482 @vindex gnus-init-file
1483 When gnus starts, it will read the @code{gnus-site-init-file}
1484 (@file{.../site-lisp/gnus} by default) and @code{gnus-init-file}
1485 (@file{~/.gnus} by default) files. These are normal Emacs Lisp files
1486 and can be used to avoid cluttering your @file{~/.emacs} and
1487 @file{site-init} files with gnus stuff. Gnus will also check for files
1488 with the same names as these, but with @file{.elc} and @file{.el}
1489 suffixes. In other words, if you have set @code{gnus-init-file} to
1490 @file{~/.gnus}, it will look for @file{~/.gnus.elc}, @file{~/.gnus.el},
1491 and finally @file{~/.gnus} (in this order).
1497 @cindex dribble file
1500 Whenever you do something that changes the gnus data (reading articles,
1501 catching up, killing/subscribing groups), the change is added to a
1502 special @dfn{dribble buffer}. This buffer is auto-saved the normal
1503 Emacs way. If your Emacs should crash before you have saved the
1504 @file{.newsrc} files, all changes you have made can be recovered from
1507 If gnus detects this file at startup, it will ask the user whether to
1508 read it. The auto save file is deleted whenever the real startup file is
1511 @vindex gnus-use-dribble-file
1512 If @code{gnus-use-dribble-file} is @code{nil}, gnus won't create and
1513 maintain a dribble buffer. The default is @code{t}.
1515 @vindex gnus-dribble-directory
1516 Gnus will put the dribble file(s) in @code{gnus-dribble-directory}. If
1517 this variable is @code{nil}, which it is by default, gnus will dribble
1518 into the directory where the @file{.newsrc} file is located. (This is
1519 normally the user's home directory.) The dribble file will get the same
1520 file permissions as the @code{.newsrc} file.
1522 @vindex gnus-always-read-dribble-file
1523 If @code{gnus-always-read-dribble-file} is non-@code{nil}, Gnus will
1524 read the dribble file on startup without querying the user.
1527 @node The Active File
1528 @section The Active File
1530 @cindex ignored groups
1532 When gnus starts, or indeed whenever it tries to determine whether new
1533 articles have arrived, it reads the active file. This is a very large
1534 file that lists all the active groups and articles on the server.
1536 @vindex gnus-ignored-newsgroups
1537 Before examining the active file, gnus deletes all lines that match the
1538 regexp @code{gnus-ignored-newsgroups}. This is done primarily to reject
1539 any groups with bogus names, but you can use this variable to make gnus
1540 ignore hierarchies you aren't ever interested in. However, this is not
1541 recommended. In fact, it's highly discouraged. Instead, @pxref{New
1542 Groups} for an overview of other variables that can be used instead.
1545 @c @code{nil} by default, and will slow down active file handling somewhat
1546 @c if you set it to anything else.
1548 @vindex gnus-read-active-file
1550 The active file can be rather Huge, so if you have a slow network, you
1551 can set @code{gnus-read-active-file} to @code{nil} to prevent gnus from
1552 reading the active file. This variable is @code{some} by default.
1554 Gnus will try to make do by getting information just on the groups that
1555 you actually subscribe to.
1557 Note that if you subscribe to lots and lots of groups, setting this
1558 variable to @code{nil} will probably make gnus slower, not faster. At
1559 present, having this variable @code{nil} will slow gnus down
1560 considerably, unless you read news over a 2400 baud modem.
1562 This variable can also have the value @code{some}. Gnus will then
1563 attempt to read active info only on the subscribed groups. On some
1564 servers this is quite fast (on sparkling, brand new INN servers that
1565 support the @code{LIST ACTIVE group} command), on others this isn't fast
1566 at all. In any case, @code{some} should be faster than @code{nil}, and
1567 is certainly faster than @code{t} over slow lines.
1569 Some news servers (old versions of Leafnode and old versions of INN, for
1570 instance) do not support the @code{LIST ACTIVE group}. For these
1571 servers, @code{nil} is probably the most efficient value for this
1574 If this variable is @code{nil}, gnus will ask for group info in total
1575 lock-step, which isn't very fast. If it is @code{some} and you use an
1576 @sc{nntp} server, gnus will pump out commands as fast as it can, and
1577 read all the replies in one swoop. This will normally result in better
1578 performance, but if the server does not support the aforementioned
1579 @code{LIST ACTIVE group} command, this isn't very nice to the server.
1581 If you think that starting up Gnus takes too long, try all the three
1582 different values for this variable and see what works best for you.
1584 In any case, if you use @code{some} or @code{nil}, you should definitely
1585 kill all groups that you aren't interested in to speed things up.
1587 Note that this variable also affects active file retrieval from
1588 secondary select methods.
1591 @node Startup Variables
1592 @section Startup Variables
1596 @item gnus-load-hook
1597 @vindex gnus-load-hook
1598 A hook run while gnus is being loaded. Note that this hook will
1599 normally be run just once in each Emacs session, no matter how many
1600 times you start gnus.
1602 @item gnus-before-startup-hook
1603 @vindex gnus-before-startup-hook
1604 A hook run after starting up gnus successfully.
1606 @item gnus-startup-hook
1607 @vindex gnus-startup-hook
1608 A hook run as the very last thing after starting up gnus
1610 @item gnus-started-hook
1611 @vindex gnus-started-hook
1612 A hook that is run as the very last thing after starting up gnus
1615 @item gnus-setup-news-hook
1616 @vindex gnus-setup-news-hook
1617 A hook that is run after reading the @file{.newsrc} file(s), but before
1618 generating the group buffer.
1620 @item gnus-check-bogus-newsgroups
1621 @vindex gnus-check-bogus-newsgroups
1622 If non-@code{nil}, gnus will check for and delete all bogus groups at
1623 startup. A @dfn{bogus group} is a group that you have in your
1624 @file{.newsrc} file, but doesn't exist on the news server. Checking for
1625 bogus groups can take quite a while, so to save time and resources it's
1626 best to leave this option off, and do the checking for bogus groups once
1627 in a while from the group buffer instead (@pxref{Group Maintenance}).
1629 @item gnus-inhibit-startup-message
1630 @vindex gnus-inhibit-startup-message
1631 If non-@code{nil}, the startup message won't be displayed. That way,
1632 your boss might not notice as easily that you are reading news instead
1633 of doing your job. Note that this variable is used before
1634 @file{.gnus.el} is loaded, so it should be set in @code{.emacs} instead.
1636 @item gnus-no-groups-message
1637 @vindex gnus-no-groups-message
1638 Message displayed by gnus when no groups are available.
1640 @item gnus-play-startup-jingle
1641 @vindex gnus-play-startup-jingle
1642 If non-@code{nil}, play the gnus jingle at startup.
1644 @item gnus-startup-jingle
1645 @vindex gnus-startup-jingle
1646 Jingle to be played if the above variable is non-@code{nil}. The
1647 default is @samp{Tuxedomoon.Jingle4.au}.
1653 @chapter Group Buffer
1654 @cindex group buffer
1656 @c Alex Schroeder suggests to rearrange this as follows:
1658 @c <kensanata> ok, just save it for reference. I'll go to bed in a minute.
1659 @c 1. Selecting a Group, 2. (new) Finding a Group, 3. Group Levels,
1660 @c 4. Subscription Commands, 5. Group Maneuvering, 6. Group Data,
1661 @c 7. Group Score, 8. Group Buffer Format
1662 @c <kensanata> Group Levels should have more information on levels 5 to 9. I
1663 @c suggest to split the 4th paragraph ("Gnus considers groups...") as follows:
1664 @c <kensanata> First, "Gnus considers groups... (default 9)."
1665 @c <kensanata> New, a table summarizing what levels 1 to 9 mean.
1666 @c <kensanata> Third, "Gnus treats subscribed ... reasons of efficiency"
1667 @c <kensanata> Then expand the next paragraph or add some more to it.
1668 @c This short one sentence explains levels 1 and 2, therefore I understand
1669 @c that I should keep important news at 3 and boring news at 4.
1670 @c Say so! Then go on to explain why I should bother with levels 6 to 9.
1671 @c Maybe keep those that you don't want to read temporarily at 6,
1672 @c those that you never want to read at 8, those that offend your
1673 @c human rights at 9...
1676 The @dfn{group buffer} lists all (or parts) of the available groups. It
1677 is the first buffer shown when gnus starts, and will never be killed as
1678 long as gnus is active.
1682 \gnusfigure{The Group Buffer}{320}{
1683 \put(75,50){\epsfig{figure=ps/group,height=9cm}}
1684 \put(120,37){\makebox(0,0)[t]{Buffer name}}
1685 \put(120,38){\vector(1,2){10}}
1686 \put(40,60){\makebox(0,0)[r]{Mode line}}
1687 \put(40,58){\vector(1,0){30}}
1688 \put(200,28){\makebox(0,0)[t]{Native select method}}
1689 \put(200,26){\vector(-1,2){15}}
1695 * Group Buffer Format:: Information listed and how you can change it.
1696 * Group Maneuvering:: Commands for moving in the group buffer.
1697 * Selecting a Group:: Actually reading news.
1698 * Subscription Commands:: Unsubscribing, killing, subscribing.
1699 * Group Data:: Changing the info for a group.
1700 * Group Levels:: Levels? What are those, then?
1701 * Group Score:: A mechanism for finding out what groups you like.
1702 * Marking Groups:: You can mark groups for later processing.
1703 * Foreign Groups:: Creating and editing groups.
1704 * Group Parameters:: Each group may have different parameters set.
1705 * Listing Groups:: Gnus can list various subsets of the groups.
1706 * Sorting Groups:: Re-arrange the group order.
1707 * Group Maintenance:: Maintaining a tidy @file{.newsrc} file.
1708 * Browse Foreign Server:: You can browse a server. See what it has to offer.
1709 * Exiting Gnus:: Stop reading news and get some work done.
1710 * Group Topics:: A folding group mode divided into topics.
1711 * Misc Group Stuff:: Other stuff that you can to do.
1715 @node Group Buffer Format
1716 @section Group Buffer Format
1719 * Group Line Specification:: Deciding how the group buffer is to look.
1720 * Group Modeline Specification:: The group buffer modeline.
1721 * Group Highlighting:: Having nice colors in the group buffer.
1725 @node Group Line Specification
1726 @subsection Group Line Specification
1727 @cindex group buffer format
1729 The default format of the group buffer is nice and dull, but you can
1730 make it as exciting and ugly as you feel like.
1732 Here's a couple of example group lines:
1735 25: news.announce.newusers
1736 * 0: alt.fan.andrea-dworkin
1741 You can see that there are 25 unread articles in
1742 @samp{news.announce.newusers}. There are no unread articles, but some
1743 ticked articles, in @samp{alt.fan.andrea-dworkin} (see that little
1744 asterisk at the beginning of the line?).
1746 @vindex gnus-group-line-format
1747 You can change that format to whatever you want by fiddling with the
1748 @code{gnus-group-line-format} variable. This variable works along the
1749 lines of a @code{format} specification, which is pretty much the same as
1750 a @code{printf} specifications, for those of you who use (feh!) C.
1751 @xref{Formatting Variables}.
1753 @samp{%M%S%5y:%B%(%g%)\n} is the value that produced those lines above.
1755 There should always be a colon on the line; the cursor always moves to
1756 the colon after performing an operation. @xref{Positioning
1757 Point}. Nothing else is required---not even the group name. All
1758 displayed text is just window dressing, and is never examined by Gnus.
1759 Gnus stores all real information it needs using text properties.
1761 (Note that if you make a really strange, wonderful, spreadsheet-like
1762 layout, everybody will believe you are hard at work with the accounting
1763 instead of wasting time reading news.)
1765 Here's a list of all available format characters:
1770 An asterisk if the group only has marked articles.
1773 Whether the group is subscribed.
1776 Level of subscribedness.
1779 Number of unread articles.
1782 Number of dormant articles.
1785 Number of ticked articles.
1788 Number of read articles.
1791 Number of unseen articles.
1794 Estimated total number of articles. (This is really @var{max-number}
1795 minus @var{min-number} plus 1.)
1797 Gnus uses this estimation because the @sc{nntp} protocol provides
1798 efficient access to @var{max-number} and @var{min-number} but getting
1799 the true unread message count is not possible efficiently. For
1800 hysterical raisins, even the mail back ends, where the true number of
1801 unread messages might be available efficiently, use the same limited
1802 interface. To remove this restriction from Gnus means that the back
1803 end interface has to be changed, which is not an easy job. If you
1804 want to work on this, please contact the Gnus mailing list.
1807 Number of unread, unticked, non-dormant articles.
1810 Number of ticked and dormant articles.
1819 Group comment (@pxref{Group Parameters}) or group name if there is no
1820 comment element in the group parameters.
1823 Newsgroup description.
1826 @samp{m} if moderated.
1829 @samp{(m)} if moderated.
1835 If the summary buffer for the group is open or not.
1841 A string that looks like @samp{<%s:%n>} if a foreign select method is
1845 Indentation based on the level of the topic (@pxref{Group Topics}).
1848 @vindex gnus-group-uncollapsed-levels
1849 Short (collapsed) group name. The @code{gnus-group-uncollapsed-levels}
1850 variable says how many levels to leave at the end of the group name.
1851 The default is 1---this will mean that group names like
1852 @samp{gnu.emacs.gnus} will be shortened to @samp{g.e.gnus}.
1855 @vindex gnus-new-mail-mark
1857 @samp{%} (@code{gnus-new-mail-mark}) if there has arrived new mail to
1861 @samp{#} (@code{gnus-process-mark}) if the group is process marked.
1864 A string that says when you last read the group (@pxref{Group
1868 User defined specifier. The next character in the format string should
1869 be a letter. Gnus will call the function
1870 @code{gnus-user-format-function-}@samp{X}, where @samp{X} is the letter
1871 following @samp{%u}. The function will be passed a single dummy
1872 parameter as argument. The function should return a string, which will
1873 be inserted into the buffer just like information from any other
1878 All the ``number-of'' specs will be filled with an asterisk (@samp{*})
1879 if no info is available---for instance, if it is a non-activated foreign
1880 group, or a bogus native group.
1883 @node Group Modeline Specification
1884 @subsection Group Modeline Specification
1885 @cindex group modeline
1887 @vindex gnus-group-mode-line-format
1888 The mode line can be changed by setting
1889 @code{gnus-group-mode-line-format} (@pxref{Mode Line Formatting}). It
1890 doesn't understand that many format specifiers:
1894 The native news server.
1896 The native select method.
1900 @node Group Highlighting
1901 @subsection Group Highlighting
1902 @cindex highlighting
1903 @cindex group highlighting
1905 @vindex gnus-group-highlight
1906 Highlighting in the group buffer is controlled by the
1907 @code{gnus-group-highlight} variable. This is an alist with elements
1908 that look like @code{(@var{form} . @var{face})}. If @var{form} evaluates to
1909 something non-@code{nil}, the @var{face} will be used on the line.
1911 Here's an example value for this variable that might look nice if the
1915 (cond (window-system
1916 (setq custom-background-mode 'light)
1917 (defface my-group-face-1
1918 '((t (:foreground "Red" :bold t))) "First group face")
1919 (defface my-group-face-2
1920 '((t (:foreground "DarkSeaGreen4" :bold t))) "Second group face")
1921 (defface my-group-face-3
1922 '((t (:foreground "Green4" :bold t))) "Third group face")
1923 (defface my-group-face-4
1924 '((t (:foreground "SteelBlue" :bold t))) "Fourth group face")
1925 (defface my-group-face-5
1926 '((t (:foreground "Blue" :bold t))) "Fifth group face")))
1928 (setq gnus-group-highlight
1929 '(((> unread 200) . my-group-face-1)
1930 ((and (< level 3) (zerop unread)) . my-group-face-2)
1931 ((< level 3) . my-group-face-3)
1932 ((zerop unread) . my-group-face-4)
1933 (t . my-group-face-5)))
1936 Also @pxref{Faces and Fonts}.
1938 Variables that are dynamically bound when the forms are evaluated
1945 The number of unread articles in the group.
1949 Whether the group is a mail group.
1951 The level of the group.
1953 The score of the group.
1955 The number of ticked articles in the group.
1957 The total number of articles in the group. Or rather, MAX-NUMBER minus
1958 MIN-NUMBER plus one.
1960 When using the topic minor mode, this variable is bound to the current
1961 topic being inserted.
1964 When the forms are @code{eval}ed, point is at the beginning of the line
1965 of the group in question, so you can use many of the normal gnus
1966 functions for snarfing info on the group.
1968 @vindex gnus-group-update-hook
1969 @findex gnus-group-highlight-line
1970 @code{gnus-group-update-hook} is called when a group line is changed.
1971 It will not be called when @code{gnus-visual} is @code{nil}. This hook
1972 calls @code{gnus-group-highlight-line} by default.
1975 @node Group Maneuvering
1976 @section Group Maneuvering
1977 @cindex group movement
1979 All movement commands understand the numeric prefix and will behave as
1980 expected, hopefully.
1986 @findex gnus-group-next-unread-group
1987 Go to the next group that has unread articles
1988 (@code{gnus-group-next-unread-group}).
1994 @findex gnus-group-prev-unread-group
1995 Go to the previous group that has unread articles
1996 (@code{gnus-group-prev-unread-group}).
2000 @findex gnus-group-next-group
2001 Go to the next group (@code{gnus-group-next-group}).
2005 @findex gnus-group-prev-group
2006 Go to the previous group (@code{gnus-group-prev-group}).
2010 @findex gnus-group-next-unread-group-same-level
2011 Go to the next unread group on the same (or lower) level
2012 (@code{gnus-group-next-unread-group-same-level}).
2016 @findex gnus-group-prev-unread-group-same-level
2017 Go to the previous unread group on the same (or lower) level
2018 (@code{gnus-group-prev-unread-group-same-level}).
2021 Three commands for jumping to groups:
2027 @findex gnus-group-jump-to-group
2028 Jump to a group (and make it visible if it isn't already)
2029 (@code{gnus-group-jump-to-group}). Killed groups can be jumped to, just
2034 @findex gnus-group-best-unread-group
2035 Jump to the unread group with the lowest level
2036 (@code{gnus-group-best-unread-group}).
2040 @findex gnus-group-first-unread-group
2041 Jump to the first group with unread articles
2042 (@code{gnus-group-first-unread-group}).
2045 @vindex gnus-group-goto-unread
2046 If @code{gnus-group-goto-unread} is @code{nil}, all the movement
2047 commands will move to the next group, not the next unread group. Even
2048 the commands that say they move to the next unread group. The default
2052 @node Selecting a Group
2053 @section Selecting a Group
2054 @cindex group selection
2059 @kindex SPACE (Group)
2060 @findex gnus-group-read-group
2061 Select the current group, switch to the summary buffer and display the
2062 first unread article (@code{gnus-group-read-group}). If there are no
2063 unread articles in the group, or if you give a non-numerical prefix to
2064 this command, gnus will offer to fetch all the old articles in this
2065 group from the server. If you give a numerical prefix @var{N}, @var{N}
2066 determines the number of articles gnus will fetch. If @var{N} is
2067 positive, gnus fetches the @var{N} newest articles, if @var{N} is
2068 negative, Gnus fetches the @code{abs(@var{N})} oldest articles.
2070 Thus, @kbd{SPC} enters the group normally, @kbd{C-u SPC} offers old
2071 articles, @kbd{C-u 4 2 SPC} fetches the 42 newest articles, and @kbd{C-u
2072 - 4 2 SPC} fetches the 42 oldest ones.
2074 When you are in the group (in the Summary buffer), you can type
2075 @kbd{M-g} to fetch new articles, or @kbd{C-u M-g} to also show the old
2080 @findex gnus-group-select-group
2081 Select the current group and switch to the summary buffer
2082 (@code{gnus-group-select-group}). Takes the same arguments as
2083 @code{gnus-group-read-group}---the only difference is that this command
2084 does not display the first unread article automatically upon group
2088 @kindex M-RET (Group)
2089 @findex gnus-group-quick-select-group
2090 This does the same as the command above, but tries to do it with the
2091 minimum amount of fuzz (@code{gnus-group-quick-select-group}). No
2092 scoring/killing will be performed, there will be no highlights and no
2093 expunging. This might be useful if you're in a real hurry and have to
2094 enter some humongous group. If you give a 0 prefix to this command
2095 (i.e., @kbd{0 M-RET}), gnus won't even generate the summary buffer,
2096 which is useful if you want to toggle threading before generating the
2097 summary buffer (@pxref{Summary Generation Commands}).
2100 @kindex M-SPACE (Group)
2101 @findex gnus-group-visible-select-group
2102 This is yet one more command that does the same as the @kbd{RET}
2103 command, but this one does it without expunging and hiding dormants
2104 (@code{gnus-group-visible-select-group}).
2107 @kindex C-M-RET (Group)
2108 @findex gnus-group-select-group-ephemerally
2109 Finally, this command selects the current group ephemerally without
2110 doing any processing of its contents
2111 (@code{gnus-group-select-group-ephemerally}). Even threading has been
2112 turned off. Everything you do in the group after selecting it in this
2113 manner will have no permanent effects.
2117 @vindex gnus-large-newsgroup
2118 The @code{gnus-large-newsgroup} variable says what gnus should consider
2119 to be a big group. This is 200 by default. If the group has more
2120 (unread and/or ticked) articles than this, gnus will query the user
2121 before entering the group. The user can then specify how many articles
2122 should be fetched from the server. If the user specifies a negative
2123 number (@code{-n}), the @code{n} oldest articles will be fetched. If it
2124 is positive, the @code{n} articles that have arrived most recently will
2127 @vindex gnus-select-group-hook
2128 @vindex gnus-auto-select-first
2129 If @code{gnus-auto-select-first} is non-@code{nil}, select an article
2130 automatically when entering a group with the @kbd{SPACE} command.
2131 Which article this is is controlled by the
2132 @code{gnus-auto-select-subject} variable. Valid values for this
2138 Place point on the subject line of the first unread article.
2141 Place point on the subject line of the first article.
2144 Place point on the subject line of the first unseen article.
2146 @item unseen-or-unread
2147 Place point on the subject line of the first unseen article, and if
2148 there is no such article, place point on the subject line of the first
2152 Place point on the subject line of the highest-scored unread article.
2156 This variable can also be a function. In that case, that function
2157 will be called to place point on a subject line.
2159 If you want to prevent automatic selection in some group (say, in a
2160 binary group with Huge articles) you can set the
2161 @code{gnus-auto-select-first} variable to @code{nil} in
2162 @code{gnus-select-group-hook}, which is called when a group is
2166 @node Subscription Commands
2167 @section Subscription Commands
2168 @cindex subscription
2176 @findex gnus-group-unsubscribe-current-group
2177 @c @icon{gnus-group-unsubscribe}
2178 Toggle subscription to the current group
2179 (@code{gnus-group-unsubscribe-current-group}).
2185 @findex gnus-group-unsubscribe-group
2186 Prompt for a group to subscribe, and then subscribe it. If it was
2187 subscribed already, unsubscribe it instead
2188 (@code{gnus-group-unsubscribe-group}).
2194 @findex gnus-group-kill-group
2195 @c @icon{gnus-group-kill-group}
2196 Kill the current group (@code{gnus-group-kill-group}).
2202 @findex gnus-group-yank-group
2203 Yank the last killed group (@code{gnus-group-yank-group}).
2206 @kindex C-x C-t (Group)
2207 @findex gnus-group-transpose-groups
2208 Transpose two groups (@code{gnus-group-transpose-groups}). This isn't
2209 really a subscription command, but you can use it instead of a
2210 kill-and-yank sequence sometimes.
2216 @findex gnus-group-kill-region
2217 Kill all groups in the region (@code{gnus-group-kill-region}).
2221 @findex gnus-group-kill-all-zombies
2222 Kill all zombie groups (@code{gnus-group-kill-all-zombies}).
2225 @kindex S C-k (Group)
2226 @findex gnus-group-kill-level
2227 Kill all groups on a certain level (@code{gnus-group-kill-level}).
2228 These groups can't be yanked back after killing, so this command should
2229 be used with some caution. The only time where this command comes in
2230 really handy is when you have a @file{.newsrc} with lots of unsubscribed
2231 groups that you want to get rid off. @kbd{S C-k} on level 7 will
2232 kill off all unsubscribed groups that do not have message numbers in the
2233 @file{.newsrc} file.
2237 Also @pxref{Group Levels}.
2247 @findex gnus-group-catchup-current
2248 @vindex gnus-group-catchup-group-hook
2249 @c @icon{gnus-group-catchup-current}
2250 Mark all unticked articles in this group as read
2251 (@code{gnus-group-catchup-current}).
2252 @code{gnus-group-catchup-group-hook} is called when catching up a group from
2257 @findex gnus-group-catchup-current-all
2258 Mark all articles in this group, even the ticked ones, as read
2259 (@code{gnus-group-catchup-current-all}).
2263 @findex gnus-group-clear-data
2264 Clear the data from the current group---nix out marks and the list of
2265 read articles (@code{gnus-group-clear-data}).
2267 @item M-x gnus-group-clear-data-on-native-groups
2268 @kindex M-x gnus-group-clear-data-on-native-groups
2269 @findex gnus-group-clear-data-on-native-groups
2270 If you have switched from one @sc{nntp} server to another, all your marks
2271 and read ranges have become worthless. You can use this command to
2272 clear out all data that you have on your native groups. Use with
2279 @section Group Levels
2283 All groups have a level of @dfn{subscribedness}. For instance, if a
2284 group is on level 2, it is more subscribed than a group on level 5. You
2285 can ask gnus to just list groups on a given level or lower
2286 (@pxref{Listing Groups}), or to just check for new articles in groups on
2287 a given level or lower (@pxref{Scanning New Messages}).
2289 Remember: The higher the level of the group, the less important it is.
2295 @findex gnus-group-set-current-level
2296 Set the level of the current group. If a numeric prefix is given, the
2297 next @var{n} groups will have their levels set. The user will be
2298 prompted for a level.
2301 @vindex gnus-level-killed
2302 @vindex gnus-level-zombie
2303 @vindex gnus-level-unsubscribed
2304 @vindex gnus-level-subscribed
2305 Gnus considers groups from levels 1 to
2306 @code{gnus-level-subscribed} (inclusive) (default 5) to be subscribed,
2307 @code{gnus-level-subscribed} (exclusive) and
2308 @code{gnus-level-unsubscribed} (inclusive) (default 7) to be
2309 unsubscribed, @code{gnus-level-zombie} to be zombies (walking dead)
2310 (default 8) and @code{gnus-level-killed} to be killed (completely dead)
2311 (default 9). Gnus treats subscribed and unsubscribed groups exactly the
2312 same, but zombie and killed groups have no information on what articles
2313 you have read, etc, stored. This distinction between dead and living
2314 groups isn't done because it is nice or clever, it is done purely for
2315 reasons of efficiency.
2317 It is recommended that you keep all your mail groups (if any) on quite
2318 low levels (e.g. 1 or 2).
2320 Maybe the following description of the default behavior of Gnus helps to
2321 understand what these levels are all about. By default, Gnus shows you
2322 subscribed nonempty groups, but by hitting @kbd{L} you can have it show
2323 empty subscribed groups and unsubscribed groups, too. Type @kbd{l} to
2324 go back to showing nonempty subscribed groups again. Thus, unsubscribed
2325 groups are hidden, in a way.
2327 Zombie and killed groups are similar to unsubscribed groups in that they
2328 are hidden by default. But they are different from subscribed and
2329 unsubscribed groups in that Gnus doesn't ask the news server for
2330 information (number of messages, number of unread messages) on zombie
2331 and killed groups. Normally, you use @kbd{C-k} to kill the groups you
2332 aren't interested in. If most groups are killed, Gnus is faster.
2334 Why does Gnus distinguish between zombie and killed groups? Well, when
2335 a new group arrives on the server, Gnus by default makes it a zombie
2336 group. This means that you are normally not bothered with new groups,
2337 but you can type @kbd{A z} to get a list of all new groups. Subscribe
2338 the ones you like and kill the ones you don't want. (@kbd{A k} shows a
2339 list of killed groups.)
2341 If you want to play with the level variables, you should show some care.
2342 Set them once, and don't touch them ever again. Better yet, don't touch
2343 them at all unless you know exactly what you're doing.
2345 @vindex gnus-level-default-unsubscribed
2346 @vindex gnus-level-default-subscribed
2347 Two closely related variables are @code{gnus-level-default-subscribed}
2348 (default 3) and @code{gnus-level-default-unsubscribed} (default 6),
2349 which are the levels that new groups will be put on if they are
2350 (un)subscribed. These two variables should, of course, be inside the
2351 relevant valid ranges.
2353 @vindex gnus-keep-same-level
2354 If @code{gnus-keep-same-level} is non-@code{nil}, some movement commands
2355 will only move to groups of the same level (or lower). In
2356 particular, going from the last article in one group to the next group
2357 will go to the next group of the same level (or lower). This might be
2358 handy if you want to read the most important groups before you read the
2361 If this variable is @code{best}, Gnus will make the next newsgroup the
2362 one with the best level.
2364 @vindex gnus-group-default-list-level
2365 All groups with a level less than or equal to
2366 @code{gnus-group-default-list-level} will be listed in the group buffer
2369 @vindex gnus-group-list-inactive-groups
2370 If @code{gnus-group-list-inactive-groups} is non-@code{nil}, non-active
2371 groups will be listed along with the unread groups. This variable is
2372 @code{t} by default. If it is @code{nil}, inactive groups won't be
2375 @vindex gnus-group-use-permanent-levels
2376 If @code{gnus-group-use-permanent-levels} is non-@code{nil}, once you
2377 give a level prefix to @kbd{g} or @kbd{l}, all subsequent commands will
2378 use this level as the ``work'' level.
2380 @vindex gnus-activate-level
2381 Gnus will normally just activate (i. e., query the server about) groups
2382 on level @code{gnus-activate-level} or less. If you don't want to
2383 activate unsubscribed groups, for instance, you might set this variable
2384 to 5. The default is 6.
2388 @section Group Score
2393 You would normally keep important groups on high levels, but that scheme
2394 is somewhat restrictive. Don't you wish you could have Gnus sort the
2395 group buffer according to how often you read groups, perhaps? Within
2398 This is what @dfn{group score} is for. You can have Gnus assign a score
2399 to each group through the mechanism described below. You can then sort
2400 the group buffer based on this score. Alternatively, you can sort on
2401 score and then level. (Taken together, the level and the score is
2402 called the @dfn{rank} of the group. A group that is on level 4 and has
2403 a score of 1 has a higher rank than a group on level 5 that has a score
2404 of 300. (The level is the most significant part and the score is the
2405 least significant part.))
2407 @findex gnus-summary-bubble-group
2408 If you want groups you read often to get higher scores than groups you
2409 read seldom you can add the @code{gnus-summary-bubble-group} function to
2410 the @code{gnus-summary-exit-hook} hook. This will result (after
2411 sorting) in a bubbling sort of action. If you want to see that in
2412 action after each summary exit, you can add
2413 @code{gnus-group-sort-groups-by-rank} or
2414 @code{gnus-group-sort-groups-by-score} to the same hook, but that will
2415 slow things down somewhat.
2418 @node Marking Groups
2419 @section Marking Groups
2420 @cindex marking groups
2422 If you want to perform some command on several groups, and they appear
2423 subsequently in the group buffer, you would normally just give a
2424 numerical prefix to the command. Most group commands will then do your
2425 bidding on those groups.
2427 However, if the groups are not in sequential order, you can still
2428 perform a command on several groups. You simply mark the groups first
2429 with the process mark and then execute the command.
2437 @findex gnus-group-mark-group
2438 Set the mark on the current group (@code{gnus-group-mark-group}).
2444 @findex gnus-group-unmark-group
2445 Remove the mark from the current group
2446 (@code{gnus-group-unmark-group}).
2450 @findex gnus-group-unmark-all-groups
2451 Remove the mark from all groups (@code{gnus-group-unmark-all-groups}).
2455 @findex gnus-group-mark-region
2456 Mark all groups between point and mark (@code{gnus-group-mark-region}).
2460 @findex gnus-group-mark-buffer
2461 Mark all groups in the buffer (@code{gnus-group-mark-buffer}).
2465 @findex gnus-group-mark-regexp
2466 Mark all groups that match some regular expression
2467 (@code{gnus-group-mark-regexp}).
2470 Also @pxref{Process/Prefix}.
2472 @findex gnus-group-universal-argument
2473 If you want to execute some command on all groups that have been marked
2474 with the process mark, you can use the @kbd{M-&}
2475 (@code{gnus-group-universal-argument}) command. It will prompt you for
2476 the command to be executed.
2479 @node Foreign Groups
2480 @section Foreign Groups
2481 @cindex foreign groups
2483 Below are some group mode commands for making and editing general foreign
2484 groups, as well as commands to ease the creation of a few
2485 special-purpose groups. All these commands insert the newly created
2486 groups under point---@code{gnus-subscribe-newsgroup-method} is not
2493 @findex gnus-group-make-group
2494 @cindex making groups
2495 Make a new group (@code{gnus-group-make-group}). Gnus will prompt you
2496 for a name, a method and possibly an @dfn{address}. For an easier way
2497 to subscribe to @sc{nntp} groups, @pxref{Browse Foreign Server}.
2501 @findex gnus-group-rename-group
2502 @cindex renaming groups
2503 Rename the current group to something else
2504 (@code{gnus-group-rename-group}). This is valid only on some
2505 groups---mail groups mostly. This command might very well be quite slow
2511 @findex gnus-group-customize
2512 Customize the group parameters (@code{gnus-group-customize}).
2516 @findex gnus-group-edit-group-method
2517 @cindex renaming groups
2518 Enter a buffer where you can edit the select method of the current
2519 group (@code{gnus-group-edit-group-method}).
2523 @findex gnus-group-edit-group-parameters
2524 Enter a buffer where you can edit the group parameters
2525 (@code{gnus-group-edit-group-parameters}).
2529 @findex gnus-group-edit-group
2530 Enter a buffer where you can edit the group info
2531 (@code{gnus-group-edit-group}).
2535 @findex gnus-group-make-directory-group
2537 Make a directory group (@pxref{Directory Groups}). You will be prompted
2538 for a directory name (@code{gnus-group-make-directory-group}).
2543 @findex gnus-group-make-help-group
2544 Make the gnus help group (@code{gnus-group-make-help-group}).
2548 @cindex (ding) archive
2549 @cindex archive group
2550 @findex gnus-group-make-archive-group
2551 @vindex gnus-group-archive-directory
2552 @vindex gnus-group-recent-archive-directory
2553 Make a gnus archive group (@code{gnus-group-make-archive-group}). By
2554 default a group pointing to the most recent articles will be created
2555 (@code{gnus-group-recent-archive-directory}), but given a prefix, a full
2556 group will be created from @code{gnus-group-archive-directory}.
2560 @findex gnus-group-make-kiboze-group
2562 Make a kiboze group. You will be prompted for a name, for a regexp to
2563 match groups to be ``included'' in the kiboze group, and a series of
2564 strings to match on headers (@code{gnus-group-make-kiboze-group}).
2565 @xref{Kibozed Groups}.
2569 @findex gnus-group-enter-directory
2571 Read an arbitrary directory as if it were a newsgroup with the
2572 @code{nneething} back end (@code{gnus-group-enter-directory}).
2573 @xref{Anything Groups}.
2577 @findex gnus-group-make-doc-group
2578 @cindex ClariNet Briefs
2580 Make a group based on some file or other
2581 (@code{gnus-group-make-doc-group}). If you give a prefix to this
2582 command, you will be prompted for a file name and a file type.
2583 Currently supported types are @code{mbox}, @code{babyl},
2584 @code{digest}, @code{news}, @code{rnews}, @code{mmdf}, @code{forward},
2585 @code{rfc934}, @code{rfc822-forward}, @code{mime-parts},
2586 @code{standard-digest}, @code{slack-digest}, @code{clari-briefs},
2587 @code{nsmail}, @code{outlook}, @code{oe-dbx}, and @code{mailman}. If
2588 you run this command without a prefix, Gnus will guess at the file
2589 type. @xref{Document Groups}.
2593 @vindex gnus-useful-groups
2594 @findex gnus-group-make-useful-group
2595 Create one of the groups mentioned in @code{gnus-useful-groups}
2596 (@code{gnus-group-make-useful-group}).
2600 @findex gnus-group-make-web-group
2604 Make an ephemeral group based on a web search
2605 (@code{gnus-group-make-web-group}). If you give a prefix to this
2606 command, make a solid group instead. You will be prompted for the
2607 search engine type and the search string. Valid search engine types
2608 include @code{google}, @code{dejanews}, and @code{gmane}.
2609 @xref{Web Searches}.
2611 If you use the @code{google} search engine, you can limit the search
2612 to a particular group by using a match string like
2613 @samp{shaving group:alt.sysadmin.recovery}.
2616 @kindex G DEL (Group)
2617 @findex gnus-group-delete-group
2618 This function will delete the current group
2619 (@code{gnus-group-delete-group}). If given a prefix, this function will
2620 actually delete all the articles in the group, and forcibly remove the
2621 group itself from the face of the Earth. Use a prefix only if you are
2622 absolutely sure of what you are doing. This command can't be used on
2623 read-only groups (like @code{nntp} group), though.
2627 @findex gnus-group-make-empty-virtual
2628 Make a new, fresh, empty @code{nnvirtual} group
2629 (@code{gnus-group-make-empty-virtual}). @xref{Virtual Groups}.
2633 @findex gnus-group-add-to-virtual
2634 Add the current group to an @code{nnvirtual} group
2635 (@code{gnus-group-add-to-virtual}). Uses the process/prefix convention.
2638 @xref{Select Methods}, for more information on the various select
2641 @vindex gnus-activate-foreign-newsgroups
2642 If @code{gnus-activate-foreign-newsgroups} is a positive number,
2643 gnus will check all foreign groups with this level or lower at startup.
2644 This might take quite a while, especially if you subscribe to lots of
2645 groups from different @sc{nntp} servers. Also @pxref{Group Levels};
2646 @code{gnus-activate-level} also affects activation of foreign
2650 @node Group Parameters
2651 @section Group Parameters
2652 @cindex group parameters
2654 The group parameters store information local to a particular group.
2655 Here's an example group parameter list:
2658 ((to-address . "ding@@gnus.org")
2662 We see that each element consists of a "dotted pair"---the thing before
2663 the dot is the key, while the thing after the dot is the value. All the
2664 parameters have this form @emph{except} local variable specs, which are
2665 not dotted pairs, but proper lists.
2667 Some parameters have correspondant customizable variables, each of which
2668 is an alist of regexps and values.
2670 The following group parameters can be used:
2675 Address used by when doing followups and new posts.
2678 (to-address . "some@@where.com")
2681 This is primarily useful in mail groups that represent closed mailing
2682 lists---mailing lists where it's expected that everybody that writes to
2683 the mailing list is subscribed to it. Since using this parameter
2684 ensures that the mail only goes to the mailing list itself, it means
2685 that members won't receive two copies of your followups.
2687 Using @code{to-address} will actually work whether the group is foreign
2688 or not. Let's say there's a group on the server that is called
2689 @samp{fa.4ad-l}. This is a real newsgroup, but the server has gotten
2690 the articles from a mail-to-news gateway. Posting directly to this
2691 group is therefore impossible---you have to send mail to the mailing
2692 list address instead.
2694 See also @code{gnus-parameter-to-address-alist}.
2698 Address used when doing @kbd{a} in that group.
2701 (to-list . "some@@where.com")
2704 It is totally ignored
2705 when doing a followup---except that if it is present in a news group,
2706 you'll get mail group semantics when doing @kbd{f}.
2708 If you do an @kbd{a} command in a mail group and you have neither a
2709 @code{to-list} group parameter nor a @code{to-address} group parameter,
2710 then a @code{to-list} group parameter will be added automatically upon
2711 sending the message if @code{gnus-add-to-list} is set to @code{t}.
2712 @vindex gnus-add-to-list
2714 If you do an @kbd{a} command in a mail group and you don't have a
2715 @code{to-list} group parameter, one will be added automatically upon
2716 sending the message.
2718 @findex gnus-mailing-list-mode
2719 @cindex Mail List Groups
2720 If this variable is set, @code{gnus-mailing-list-mode} is turned on when
2721 entering summary buffer.
2723 See also @code{gnus-parameter-to-list-alist}.
2728 If this parameter is set to @code{t}, Gnus will consider the
2729 to-address and to-list parameters for this group as addresses of
2730 mailing lists you are subscribed to. Giving Gnus this information is
2731 (only) a first step in getting it to generate correct Mail-Followup-To
2732 headers for your posts to these lists. Look here @pxref{(message)Mailing
2733 Lists} for a complete treatment of available MFT support.
2735 See also @code{gnus-find-subscribed-addresses}, the function that
2736 directly uses this group parameter.
2740 If the group parameter list has the element @code{(visible . t)},
2741 that group will always be visible in the Group buffer, regardless
2742 of whether it has any unread articles.
2744 @item broken-reply-to
2745 @cindex broken-reply-to
2746 Elements like @code{(broken-reply-to . t)} signals that @code{Reply-To}
2747 headers in this group are to be ignored. This can be useful if you're
2748 reading a mailing list group where the listserv has inserted
2749 @code{Reply-To} headers that point back to the listserv itself. This is
2750 broken behavior. So there!
2754 Elements like @code{(to-group . "some.group.name")} means that all
2755 posts in that group will be sent to @code{some.group.name}.
2759 If you have @code{(newsgroup . t)} in the group parameter list, gnus
2760 will treat all responses as if they were responses to news articles.
2761 This can be useful if you have a mail group that's really a mirror of a
2766 If @code{(gcc-self . t)} is present in the group parameter list, newly
2767 composed messages will be @code{Gcc}'d to the current group. If
2768 @code{(gcc-self . none)} is present, no @code{Gcc:} header will be
2769 generated, if @code{(gcc-self . "string")} is present, this string will
2770 be inserted literally as a @code{gcc} header. This parameter takes
2771 precedence over any default @code{Gcc} rules as described later
2772 (@pxref{Archived Messages}). CAVEAT:: It yields an error putting
2773 @code{(gcc-self . t)} in groups of a @code{nntp} server or so, because
2774 a @code{nntp} server doesn't accept articles.
2778 If the group parameter has an element that looks like @code{(auto-expire
2779 . t)}, all articles read will be marked as expirable. For an
2780 alternative approach, @pxref{Expiring Mail}.
2782 See also @code{gnus-auto-expirable-newsgroups}.
2785 @cindex total-expire
2786 If the group parameter has an element that looks like
2787 @code{(total-expire . t)}, all read articles will be put through the
2788 expiry process, even if they are not marked as expirable. Use with
2789 caution. Unread, ticked and dormant articles are not eligible for
2792 See also @code{gnus-total-expirable-newsgroups}.
2796 @vindex nnmail-expiry-wait-function
2797 If the group parameter has an element that looks like
2798 @code{(expiry-wait . 10)}, this value will override any
2799 @code{nnmail-expiry-wait} and @code{nnmail-expiry-wait-function}
2800 (@pxref{Expiring Mail}) when expiring expirable messages. The value
2801 can either be a number of days (not necessarily an integer) or the
2802 symbols @code{never} or @code{immediate}.
2805 @cindex score file group parameter
2806 Elements that look like @code{(score-file . "file")} will make
2807 @file{file} into the current score file for the group in question. All
2808 interactive score entries will be put into this file.
2811 @cindex adapt file group parameter
2812 Elements that look like @code{(adapt-file . "file")} will make
2813 @file{file} into the current adaptive file for the group in question.
2814 All adaptive score entries will be put into this file.
2817 @cindex admin-address
2818 When unsubscribing from a mailing list you should never send the
2819 unsubscription notice to the mailing list itself. Instead, you'd send
2820 messages to the administrative address. This parameter allows you to
2821 put the admin address somewhere convenient.
2825 Elements that look like @code{(display . MODE)} say which articles to
2826 display on entering the group. Valid values are:
2830 Display all articles, both read and unread.
2833 Display the last INTEGER articles in the group. This is the same as
2834 entering the group with C-u INTEGER.
2837 Display the default visible articles, which normally includes unread and
2841 Display articles that satisfy a predicate.
2843 Here are some examples:
2847 Display only unread articles.
2850 Display everything except expirable articles.
2852 @item [and (not reply) (not expire)]
2853 Display everything except expirable and articles you've already
2857 The available operators are @code{not}, @code{and} and @code{or}.
2858 Predicates include @code{tick}, @code{unsend}, @code{undownload},
2859 @code{unread}, @code{dormant}, @code{expire}, @code{reply},
2860 @code{killed}, @code{bookmark}, @code{score}, @code{save},
2861 @code{cache}, @code{forward}, @code{unseen} and @code{recent}.
2865 The @code{display} parameter works by limiting the summary buffer to
2866 the subset specified. You can pop the limit by using the @kbd{/ w}
2867 command (@pxref{Limiting}).
2871 Elements that look like @code{(comment . "This is a comment")} are
2872 arbitrary comments on the group. You can display comments in the
2873 group line (@pxref{Group Line Specification}).
2877 Elements that look like @code{(charset . iso-8859-1)} will make
2878 @code{iso-8859-1} the default charset; that is, the charset that will be
2879 used for all articles that do not specify a charset.
2881 See also @code{gnus-group-charset-alist}.
2883 @item ignored-charsets
2884 @cindex ignored-charset
2885 Elements that look like @code{(ignored-charsets x-unknown iso-8859-1)}
2886 will make @code{iso-8859-1} and @code{x-unknown} ignored; that is, the
2887 default charset will be used for decoding articles.
2889 See also @code{gnus-group-ignored-charsets-alist}.
2892 @cindex posting-style
2893 You can store additional posting style information for this group
2894 here (@pxref{Posting Styles}). The format is that of an entry in the
2895 @code{gnus-posting-styles} alist, except that there's no regexp matching
2896 the group name (of course). Style elements in this group parameter will
2897 take precedence over the ones found in @code{gnus-posting-styles}.
2899 For instance, if you want a funky name and signature in this group only,
2900 instead of hacking @code{gnus-posting-styles}, you could put something
2901 like this in the group parameters:
2906 ("X-My-Header" "Funky Value")
2907 (signature "Funky Signature"))
2912 If it is set, the value is used as the method for posting message
2913 instead of @code{gnus-post-method}.
2917 An item like @code{(banner . "regex")} causes any part of an article
2918 that matches the regular expression "regex" to be stripped. Instead of
2919 "regex", you can also use the symbol @code{signature} which strips the
2920 last signature or any of the elements of the alist
2921 @code{gnus-article-banner-alist}.
2925 This parameter contains a Sieve test that should match incoming mail
2926 that should be placed in this group. From this group parameter, a
2927 Sieve @samp{IF} control structure is generated, having the test as the
2928 condition and @samp{fileinto "group.name";} as the body.
2930 For example, if the INBOX.list.sieve group has the @code{(sieve
2931 address "sender" "sieve-admin@@extundo.com")} group parameter, when
2932 translating the group parameter into a Sieve script (@pxref{Sieve
2933 Commands}) the following Sieve code is generated:
2936 if address \"sender\" \"sieve-admin@@extundo.com\" @{
2937 fileinto \"INBOX.list.sieve\";
2941 The Sieve language is described in RFC 3028. @xref{Top, , Top, sieve,
2944 @item (@var{variable} @var{form})
2945 You can use the group parameters to set variables local to the group you
2946 are entering. If you want to turn threading off in @samp{news.answers},
2947 you could put @code{(gnus-show-threads nil)} in the group parameters of
2948 that group. @code{gnus-show-threads} will be made into a local variable
2949 in the summary buffer you enter, and the form @code{nil} will be
2950 @code{eval}ed there.
2952 @vindex gnus-list-identifiers
2953 A use for this feature, is to remove a mailing list identifier tag in
2954 the subject fields of articles. E.g. if the news group
2955 @samp{nntp+news.gnus.org:gmane.text.docbook.apps} has the tag
2956 @samp{DOC-BOOK-APPS:} in the subject of all articles, this tag can be
2957 removed from the article subjects in the summary buffer for the group by
2958 putting @code{(gnus-list-identifiers "DOCBOOK-APPS:")} into the group
2959 parameters for the group.
2962 This can also be used as a group-specific hook function, if you'd like.
2963 If you want to hear a beep when you enter a group, you could put
2964 something like @code{(dummy-variable (ding))} in the parameters of that
2965 group. @code{dummy-variable} will be set to the result of the
2966 @code{(ding)} form, but who cares?
2970 Use the @kbd{G p} or the @kbd{G c} command to edit group parameters of a
2971 group. (@kbd{G p} presents you with a Lisp-based interface, @kbd{G c}
2972 presents you with a Customize-like interface. The latter helps avoid
2973 silly Lisp errors.) You might also be interested in reading about topic
2974 parameters (@pxref{Topic Parameters}).
2976 Group parameters can be set via the @code{gnus-parameters} variable too.
2977 But some variables, such as @code{visible}, have no effect. For
2981 (setq gnus-parameters
2983 (gnus-show-threads nil)
2984 (gnus-use-scoring nil)
2985 (gnus-summary-line-format
2986 "%U%R%z%I%(%[%d:%ub%-23,23f%]%) %s\n")
2990 ("^nnimap:\\(foo.bar\\)$"
2994 (gnus-use-scoring t))
2998 (broken-reply-to . t))))
3001 String value of parameters will be subjected to regexp substitution, as
3002 the @code{to-group} example shows.
3005 @node Listing Groups
3006 @section Listing Groups
3007 @cindex group listing
3009 These commands all list various slices of the groups available.
3017 @findex gnus-group-list-groups
3018 List all groups that have unread articles
3019 (@code{gnus-group-list-groups}). If the numeric prefix is used, this
3020 command will list only groups of level ARG and lower. By default, it
3021 only lists groups of level five (i. e.,
3022 @code{gnus-group-default-list-level}) or lower (i.e., just subscribed
3029 @findex gnus-group-list-all-groups
3030 List all groups, whether they have unread articles or not
3031 (@code{gnus-group-list-all-groups}). If the numeric prefix is used,
3032 this command will list only groups of level ARG and lower. By default,
3033 it lists groups of level seven or lower (i.e., just subscribed and
3034 unsubscribed groups).
3038 @findex gnus-group-list-level
3039 List all unread groups on a specific level
3040 (@code{gnus-group-list-level}). If given a prefix, also list the groups
3041 with no unread articles.
3045 @findex gnus-group-list-killed
3046 List all killed groups (@code{gnus-group-list-killed}). If given a
3047 prefix argument, really list all groups that are available, but aren't
3048 currently (un)subscribed. This could entail reading the active file
3053 @findex gnus-group-list-zombies
3054 List all zombie groups (@code{gnus-group-list-zombies}).
3058 @findex gnus-group-list-matching
3059 List all unread, subscribed groups with names that match a regexp
3060 (@code{gnus-group-list-matching}).
3064 @findex gnus-group-list-all-matching
3065 List groups that match a regexp (@code{gnus-group-list-all-matching}).
3069 @findex gnus-group-list-active
3070 List absolutely all groups in the active file(s) of the
3071 server(s) you are connected to (@code{gnus-group-list-active}). This
3072 might very well take quite a while. It might actually be a better idea
3073 to do a @kbd{A M} to list all matching, and just give @samp{.} as the
3074 thing to match on. Also note that this command may list groups that
3075 don't exist (yet)---these will be listed as if they were killed groups.
3076 Take the output with some grains of salt.
3080 @findex gnus-group-apropos
3081 List all groups that have names that match a regexp
3082 (@code{gnus-group-apropos}).
3086 @findex gnus-group-description-apropos
3087 List all groups that have names or descriptions that match a regexp
3088 (@code{gnus-group-description-apropos}).
3092 @findex gnus-group-list-cached
3093 List all groups with cached articles (@code{gnus-group-list-cached}).
3097 @findex gnus-group-list-dormant
3098 List all groups with dormant articles (@code{gnus-group-list-dormant}).
3102 @findex gnus-group-list-limit
3103 List groups limited within the current selection
3104 (@code{gnus-group-list-limit}).
3108 @findex gnus-group-list-flush
3109 Flush groups from the current selection (@code{gnus-group-list-flush}).
3113 @findex gnus-group-list-plus
3114 List groups plus the current selection (@code{gnus-group-list-plus}).
3118 @vindex gnus-permanently-visible-groups
3119 @cindex visible group parameter
3120 Groups that match the @code{gnus-permanently-visible-groups} regexp will
3121 always be shown, whether they have unread articles or not. You can also
3122 add the @code{visible} element to the group parameters in question to
3123 get the same effect.
3125 @vindex gnus-list-groups-with-ticked-articles
3126 Groups that have just ticked articles in it are normally listed in the
3127 group buffer. If @code{gnus-list-groups-with-ticked-articles} is
3128 @code{nil}, these groups will be treated just like totally empty
3129 groups. It is @code{t} by default.
3132 @node Sorting Groups
3133 @section Sorting Groups
3134 @cindex sorting groups
3136 @kindex C-c C-s (Group)
3137 @findex gnus-group-sort-groups
3138 @vindex gnus-group-sort-function
3139 The @kbd{C-c C-s} (@code{gnus-group-sort-groups}) command sorts the
3140 group buffer according to the function(s) given by the
3141 @code{gnus-group-sort-function} variable. Available sorting functions
3146 @item gnus-group-sort-by-alphabet
3147 @findex gnus-group-sort-by-alphabet
3148 Sort the group names alphabetically. This is the default.
3150 @item gnus-group-sort-by-real-name
3151 @findex gnus-group-sort-by-real-name
3152 Sort the group alphabetically on the real (unprefixed) group names.
3154 @item gnus-group-sort-by-level
3155 @findex gnus-group-sort-by-level
3156 Sort by group level.
3158 @item gnus-group-sort-by-score
3159 @findex gnus-group-sort-by-score
3160 Sort by group score. @xref{Group Score}.
3162 @item gnus-group-sort-by-rank
3163 @findex gnus-group-sort-by-rank
3164 Sort by group score and then the group level. The level and the score
3165 are, when taken together, the group's @dfn{rank}. @xref{Group Score}.
3167 @item gnus-group-sort-by-unread
3168 @findex gnus-group-sort-by-unread
3169 Sort by number of unread articles.
3171 @item gnus-group-sort-by-method
3172 @findex gnus-group-sort-by-method
3173 Sort alphabetically on the select method.
3175 @item gnus-group-sort-by-server
3176 @findex gnus-group-sort-by-server
3177 Sort alphabetically on the Gnus server name.
3182 @code{gnus-group-sort-function} can also be a list of sorting
3183 functions. In that case, the most significant sort key function must be
3187 There are also a number of commands for sorting directly according to
3188 some sorting criteria:
3192 @kindex G S a (Group)
3193 @findex gnus-group-sort-groups-by-alphabet
3194 Sort the group buffer alphabetically by group name
3195 (@code{gnus-group-sort-groups-by-alphabet}).
3198 @kindex G S u (Group)
3199 @findex gnus-group-sort-groups-by-unread
3200 Sort the group buffer by the number of unread articles
3201 (@code{gnus-group-sort-groups-by-unread}).
3204 @kindex G S l (Group)
3205 @findex gnus-group-sort-groups-by-level
3206 Sort the group buffer by group level
3207 (@code{gnus-group-sort-groups-by-level}).
3210 @kindex G S v (Group)
3211 @findex gnus-group-sort-groups-by-score
3212 Sort the group buffer by group score
3213 (@code{gnus-group-sort-groups-by-score}). @xref{Group Score}.
3216 @kindex G S r (Group)
3217 @findex gnus-group-sort-groups-by-rank
3218 Sort the group buffer by group rank
3219 (@code{gnus-group-sort-groups-by-rank}). @xref{Group Score}.
3222 @kindex G S m (Group)
3223 @findex gnus-group-sort-groups-by-method
3224 Sort the group buffer alphabetically by back end name
3225 (@code{gnus-group-sort-groups-by-method}).
3228 @kindex G S n (Group)
3229 @findex gnus-group-sort-groups-by-real-name
3230 Sort the group buffer alphabetically by real (unprefixed) group name
3231 (@code{gnus-group-sort-groups-by-real-name}).
3235 All the commands below obey the process/prefix convention
3236 (@pxref{Process/Prefix}).
3238 When given a symbolic prefix (@pxref{Symbolic Prefixes}), all these
3239 commands will sort in reverse order.
3241 You can also sort a subset of the groups:
3245 @kindex G P a (Group)
3246 @findex gnus-group-sort-selected-groups-by-alphabet
3247 Sort the groups alphabetically by group name
3248 (@code{gnus-group-sort-selected-groups-by-alphabet}).
3251 @kindex G P u (Group)
3252 @findex gnus-group-sort-selected-groups-by-unread
3253 Sort the groups by the number of unread articles
3254 (@code{gnus-group-sort-selected-groups-by-unread}).
3257 @kindex G P l (Group)
3258 @findex gnus-group-sort-selected-groups-by-level
3259 Sort the groups by group level
3260 (@code{gnus-group-sort-selected-groups-by-level}).
3263 @kindex G P v (Group)
3264 @findex gnus-group-sort-selected-groups-by-score
3265 Sort the groups by group score
3266 (@code{gnus-group-sort-selected-groups-by-score}). @xref{Group Score}.
3269 @kindex G P r (Group)
3270 @findex gnus-group-sort-selected-groups-by-rank
3271 Sort the groups by group rank
3272 (@code{gnus-group-sort-selected-groups-by-rank}). @xref{Group Score}.
3275 @kindex G P m (Group)
3276 @findex gnus-group-sort-selected-groups-by-method
3277 Sort the groups alphabetically by back end name
3278 (@code{gnus-group-sort-selected-groups-by-method}).
3281 @kindex G P n (Group)
3282 @findex gnus-group-sort-selected-groups-by-real-name
3283 Sort the groups alphabetically by real (unprefixed) group name
3284 (@code{gnus-group-sort-selected-groups-by-real-name}).
3287 @kindex G P s (Group)
3288 @findex gnus-group-sort-selected-groups
3289 Sort the groups according to @code{gnus-group-sort-function}.
3293 And finally, note that you can use @kbd{C-k} and @kbd{C-y} to manually
3297 @node Group Maintenance
3298 @section Group Maintenance
3299 @cindex bogus groups
3304 @findex gnus-group-check-bogus-groups
3305 Find bogus groups and delete them
3306 (@code{gnus-group-check-bogus-groups}).
3310 @findex gnus-group-find-new-groups
3311 Find new groups and process them (@code{gnus-group-find-new-groups}).
3312 With 1 @kbd{C-u}, use the @code{ask-server} method to query the server
3313 for new groups. With 2 @kbd{C-u}'s, use most complete method possible
3314 to query the server for new groups, and subscribe the new groups as
3318 @kindex C-c C-x (Group)
3319 @findex gnus-group-expire-articles
3320 Run all expirable articles in the current group through the expiry
3321 process (if any) (@code{gnus-group-expire-articles}). That is, delete
3322 all expirable articles in the group that have been around for a while.
3323 (@pxref{Expiring Mail}).
3326 @kindex C-c C-M-x (Group)
3327 @findex gnus-group-expire-all-groups
3328 Run all expirable articles in all groups through the expiry process
3329 (@code{gnus-group-expire-all-groups}).
3334 @node Browse Foreign Server
3335 @section Browse Foreign Server
3336 @cindex foreign servers
3337 @cindex browsing servers
3342 @findex gnus-group-browse-foreign-server
3343 You will be queried for a select method and a server name. Gnus will
3344 then attempt to contact this server and let you browse the groups there
3345 (@code{gnus-group-browse-foreign-server}).
3348 @findex gnus-browse-mode
3349 A new buffer with a list of available groups will appear. This buffer
3350 will use the @code{gnus-browse-mode}. This buffer looks a bit (well,
3351 a lot) like a normal group buffer.
3353 Here's a list of keystrokes available in the browse mode:
3358 @findex gnus-group-next-group
3359 Go to the next group (@code{gnus-group-next-group}).
3363 @findex gnus-group-prev-group
3364 Go to the previous group (@code{gnus-group-prev-group}).
3367 @kindex SPACE (Browse)
3368 @findex gnus-browse-read-group
3369 Enter the current group and display the first article
3370 (@code{gnus-browse-read-group}).
3373 @kindex RET (Browse)
3374 @findex gnus-browse-select-group
3375 Enter the current group (@code{gnus-browse-select-group}).
3379 @findex gnus-browse-unsubscribe-current-group
3380 Unsubscribe to the current group, or, as will be the case here,
3381 subscribe to it (@code{gnus-browse-unsubscribe-current-group}).
3387 @findex gnus-browse-exit
3388 Exit browse mode (@code{gnus-browse-exit}).
3392 @findex gnus-browse-describe-group
3393 Describe the current group (@code{gnus-browse-describe-group}).
3397 @findex gnus-browse-describe-briefly
3398 Describe browse mode briefly (well, there's not much to describe, is
3399 there) (@code{gnus-browse-describe-briefly}).
3404 @section Exiting gnus
3405 @cindex exiting gnus
3407 Yes, gnus is ex(c)iting.
3412 @findex gnus-group-suspend
3413 Suspend gnus (@code{gnus-group-suspend}). This doesn't really exit gnus,
3414 but it kills all buffers except the Group buffer. I'm not sure why this
3415 is a gain, but then who am I to judge?
3419 @findex gnus-group-exit
3420 @c @icon{gnus-group-exit}
3421 Quit gnus (@code{gnus-group-exit}).
3425 @findex gnus-group-quit
3426 Quit gnus without saving the @file{.newsrc} files (@code{gnus-group-quit}).
3427 The dribble file will be saved, though (@pxref{Auto Save}).
3430 @vindex gnus-exit-gnus-hook
3431 @vindex gnus-suspend-gnus-hook
3432 @code{gnus-suspend-gnus-hook} is called when you suspend gnus and
3433 @code{gnus-exit-gnus-hook} is called when you quit gnus, while
3434 @code{gnus-after-exiting-gnus-hook} is called as the final item when
3439 If you wish to completely unload gnus and all its adherents, you can use
3440 the @code{gnus-unload} command. This command is also very handy when
3441 trying to customize meta-variables.
3446 Miss Lisa Cannifax, while sitting in English class, felt her feet go
3447 numbly heavy and herself fall into a hazy trance as the boy sitting
3448 behind her drew repeated lines with his pencil across the back of her
3454 @section Group Topics
3457 If you read lots and lots of groups, it might be convenient to group
3458 them hierarchically according to topics. You put your Emacs groups over
3459 here, your sex groups over there, and the rest (what, two groups or so?)
3460 you put in some misc section that you never bother with anyway. You can
3461 even group the Emacs sex groups as a sub-topic to either the Emacs
3462 groups or the sex groups---or both! Go wild!
3466 \gnusfigure{Group Topics}{400}{
3467 \put(75,50){\epsfig{figure=ps/group-topic,height=9cm}}
3478 2: alt.religion.emacs
3481 0: comp.talk.emacs.recovery
3483 8: comp.binaries.fractals
3484 13: comp.sources.unix
3487 @findex gnus-topic-mode
3489 To get this @emph{fab} functionality you simply turn on (ooh!) the
3490 @code{gnus-topic} minor mode---type @kbd{t} in the group buffer. (This
3491 is a toggling command.)
3493 Go ahead, just try it. I'll still be here when you get back. La de
3494 dum... Nice tune, that... la la la... What, you're back? Yes, and
3495 now press @kbd{l}. There. All your groups are now listed under
3496 @samp{misc}. Doesn't that make you feel all warm and fuzzy? Hot and
3499 If you want this permanently enabled, you should add that minor mode to
3500 the hook for the group mode. Put the following line in your
3501 @file{~/.gnus} file:
3504 (add-hook 'gnus-group-mode-hook 'gnus-topic-mode)
3508 * Topic Commands:: Interactive E-Z commands.
3509 * Topic Variables:: How to customize the topics the Lisp Way.
3510 * Topic Sorting:: Sorting each topic individually.
3511 * Topic Topology:: A map of the world.
3512 * Topic Parameters:: Parameters that apply to all groups in a topic.
3516 @node Topic Commands
3517 @subsection Topic Commands
3518 @cindex topic commands
3520 When the topic minor mode is turned on, a new @kbd{T} submap will be
3521 available. In addition, a few of the standard keys change their
3522 definitions slightly.
3524 In general, the following kinds of operations are possible on topics.
3525 First of all, you want to create topics. Secondly, you want to put
3526 groups in topics and to move them around until you have an order you
3527 like. The third kind of operation is to show/hide parts of the whole
3528 shebang. You might want to hide a topic including its subtopics and
3529 groups, to get a better overview of the other groups.
3531 Here is a list of the basic keys that you might need to set up topics
3538 @findex gnus-topic-create-topic
3539 Prompt for a new topic name and create it
3540 (@code{gnus-topic-create-topic}).
3544 @kindex T TAB (Topic)
3546 @findex gnus-topic-indent
3547 ``Indent'' the current topic so that it becomes a sub-topic of the
3548 previous topic (@code{gnus-topic-indent}). If given a prefix,
3549 ``un-indent'' the topic instead.
3552 @kindex M-TAB (Topic)
3553 @findex gnus-topic-unindent
3554 ``Un-indent'' the current topic so that it becomes a sub-topic of the
3555 parent of its current parent (@code{gnus-topic-unindent}).
3559 The following two keys can be used to move groups and topics around.
3560 They work like the well-known cut and paste. @kbd{C-k} is like cut and
3561 @kbd{C-y} is like paste. Of course, this being Emacs, we use the terms
3562 kill and yank rather than cut and paste.
3568 @findex gnus-topic-kill-group
3569 Kill a group or topic (@code{gnus-topic-kill-group}). All groups in the
3570 topic will be removed along with the topic.
3574 @findex gnus-topic-yank-group
3575 Yank the previously killed group or topic
3576 (@code{gnus-topic-yank-group}). Note that all topics will be yanked
3579 So, to move a topic to the beginning of the list of topics, just hit
3580 @kbd{C-k} on it. This is like the `cut' part of cut and paste. Then,
3581 move the cursor to the beginning of the buffer (just below the `Gnus'
3582 topic) and hit @kbd{C-y}. This is like the `paste' part of cut and
3583 paste. Like I said -- E-Z.
3585 You can use @kbd{C-k} and @kbd{C-y} on groups as well as on topics. So
3586 you can move topics around as well as groups.
3590 After setting up the topics the way you like them, you might wish to
3591 hide a topic, or to show it again. That's why we have the following
3598 @findex gnus-topic-select-group
3600 Either select a group or fold a topic (@code{gnus-topic-select-group}).
3601 When you perform this command on a group, you'll enter the group, as
3602 usual. When done on a topic line, the topic will be folded (if it was
3603 visible) or unfolded (if it was folded already). So it's basically a
3604 toggling command on topics. In addition, if you give a numerical
3605 prefix, group on that level (and lower) will be displayed.
3609 Now for a list of other commands, in no particular order.
3615 @findex gnus-topic-move-group
3616 Move the current group to some other topic
3617 (@code{gnus-topic-move-group}). This command uses the process/prefix
3618 convention (@pxref{Process/Prefix}).
3622 @findex gnus-topic-jump-to-topic
3623 Go to a topic (@code{gnus-topic-jump-to-topic}).
3627 @findex gnus-topic-copy-group
3628 Copy the current group to some other topic
3629 (@code{gnus-topic-copy-group}). This command uses the process/prefix
3630 convention (@pxref{Process/Prefix}).
3634 @findex gnus-topic-hide-topic
3635 Hide the current topic (@code{gnus-topic-hide-topic}). If given
3636 a prefix, hide the topic permanently.
3640 @findex gnus-topic-show-topic
3641 Show the current topic (@code{gnus-topic-show-topic}). If given
3642 a prefix, show the topic permanently.
3646 @findex gnus-topic-remove-group
3647 Remove a group from the current topic (@code{gnus-topic-remove-group}).
3648 This command is mainly useful if you have the same group in several
3649 topics and wish to remove it from one of the topics. You may also
3650 remove a group from all topics, but in that case, Gnus will add it to
3651 the root topic the next time you start Gnus. In fact, all new groups
3652 (which, naturally, don't belong to any topic) will show up in the root
3655 This command uses the process/prefix convention
3656 (@pxref{Process/Prefix}).
3660 @findex gnus-topic-move-matching
3661 Move all groups that match some regular expression to a topic
3662 (@code{gnus-topic-move-matching}).
3666 @findex gnus-topic-copy-matching
3667 Copy all groups that match some regular expression to a topic
3668 (@code{gnus-topic-copy-matching}).
3672 @findex gnus-topic-toggle-display-empty-topics
3673 Toggle hiding empty topics
3674 (@code{gnus-topic-toggle-display-empty-topics}).
3678 @findex gnus-topic-mark-topic
3679 Mark all groups in the current topic with the process mark
3680 (@code{gnus-topic-mark-topic}).
3683 @kindex T M-# (Topic)
3684 @findex gnus-topic-unmark-topic
3685 Remove the process mark from all groups in the current topic
3686 (@code{gnus-topic-unmark-topic}).
3689 @kindex C-c C-x (Topic)
3690 @findex gnus-topic-expire-articles
3691 Run all expirable articles in the current group or topic through the
3692 expiry process (if any)
3693 (@code{gnus-topic-expire-articles}). (@pxref{Expiring Mail}).
3697 @findex gnus-topic-rename
3698 Rename a topic (@code{gnus-topic-rename}).
3701 @kindex T DEL (Topic)
3702 @findex gnus-topic-delete
3703 Delete an empty topic (@code{gnus-topic-delete}).
3707 @findex gnus-topic-list-active
3708 List all groups that gnus knows about in a topics-ified way
3709 (@code{gnus-topic-list-active}).
3712 @kindex T M-n (Topic)
3713 @findex gnus-topic-goto-next-topic
3714 Go to the next topic (@code{gnus-topic-goto-next-topic}).
3717 @kindex T M-p (Topic)
3718 @findex gnus-topic-goto-previous-topic
3719 Go to the next topic (@code{gnus-topic-goto-previous-topic}).
3723 @findex gnus-topic-edit-parameters
3724 @cindex group parameters
3725 @cindex topic parameters
3727 Edit the topic parameters (@code{gnus-topic-edit-parameters}).
3728 @xref{Topic Parameters}.
3733 @node Topic Variables
3734 @subsection Topic Variables
3735 @cindex topic variables
3737 The previous section told you how to tell Gnus which topics to display.
3738 This section explains how to tell Gnus what to display about each topic.
3740 @vindex gnus-topic-line-format
3741 The topic lines themselves are created according to the
3742 @code{gnus-topic-line-format} variable (@pxref{Formatting Variables}).
3755 Number of groups in the topic.
3757 Number of unread articles in the topic.
3759 Number of unread articles in the topic and all its subtopics.
3762 @vindex gnus-topic-indent-level
3763 Each sub-topic (and the groups in the sub-topics) will be indented with
3764 @code{gnus-topic-indent-level} times the topic level number of spaces.
3767 @vindex gnus-topic-mode-hook
3768 @code{gnus-topic-mode-hook} is called in topic minor mode buffers.
3770 @vindex gnus-topic-display-empty-topics
3771 The @code{gnus-topic-display-empty-topics} says whether to display even
3772 topics that have no unread articles in them. The default is @code{t}.
3776 @subsection Topic Sorting
3777 @cindex topic sorting
3779 You can sort the groups in each topic individually with the following
3785 @kindex T S a (Topic)
3786 @findex gnus-topic-sort-groups-by-alphabet
3787 Sort the current topic alphabetically by group name
3788 (@code{gnus-topic-sort-groups-by-alphabet}).
3791 @kindex T S u (Topic)
3792 @findex gnus-topic-sort-groups-by-unread
3793 Sort the current topic by the number of unread articles
3794 (@code{gnus-topic-sort-groups-by-unread}).
3797 @kindex T S l (Topic)
3798 @findex gnus-topic-sort-groups-by-level
3799 Sort the current topic by group level
3800 (@code{gnus-topic-sort-groups-by-level}).
3803 @kindex T S v (Topic)
3804 @findex gnus-topic-sort-groups-by-score
3805 Sort the current topic by group score
3806 (@code{gnus-topic-sort-groups-by-score}). @xref{Group Score}.
3809 @kindex T S r (Topic)
3810 @findex gnus-topic-sort-groups-by-rank
3811 Sort the current topic by group rank
3812 (@code{gnus-topic-sort-groups-by-rank}). @xref{Group Score}.
3815 @kindex T S m (Topic)
3816 @findex gnus-topic-sort-groups-by-method
3817 Sort the current topic alphabetically by back end name
3818 (@code{gnus-topic-sort-groups-by-method}).
3821 @kindex T S e (Topic)
3822 @findex gnus-topic-sort-groups-by-server
3823 Sort the current topic alphabetically by server name
3824 (@code{gnus-topic-sort-groups-by-server}).
3828 @findex gnus-topic-sort-groups
3829 Sort the current topic according to the function(s) given by the
3830 @code{gnus-group-sort-function} variable
3831 (@code{gnus-topic-sort-groups}).
3835 When given a prefix argument, all these commands will sort in reverse
3836 order. @xref{Sorting Groups}, for more information about group
3840 @node Topic Topology
3841 @subsection Topic Topology
3842 @cindex topic topology
3845 So, let's have a look at an example group buffer:
3851 2: alt.religion.emacs
3854 0: comp.talk.emacs.recovery
3856 8: comp.binaries.fractals
3857 13: comp.sources.unix
3860 So, here we have one top-level topic (@samp{Gnus}), two topics under
3861 that, and one sub-topic under one of the sub-topics. (There is always
3862 just one (1) top-level topic). This topology can be expressed as
3867 (("Emacs -- I wuw it!" visible)
3868 (("Naughty Emacs" visible)))
3872 @vindex gnus-topic-topology
3873 This is in fact how the variable @code{gnus-topic-topology} would look
3874 for the display above. That variable is saved in the @file{.newsrc.eld}
3875 file, and shouldn't be messed with manually---unless you really want
3876 to. Since this variable is read from the @file{.newsrc.eld} file,
3877 setting it in any other startup files will have no effect.
3879 This topology shows what topics are sub-topics of what topics (right),
3880 and which topics are visible. Two settings are currently
3881 allowed---@code{visible} and @code{invisible}.
3884 @node Topic Parameters
3885 @subsection Topic Parameters
3886 @cindex topic parameters
3888 All groups in a topic will inherit group parameters from the parent (and
3889 ancestor) topic parameters. All valid group parameters are valid topic
3890 parameters (@pxref{Group Parameters}).
3892 In addition, the following parameters are only valid as topic
3897 When subscribing new groups by topic (@pxref{Subscription Methods}), the
3898 @code{subscribe} topic parameter says what groups go in what topic. Its
3899 value should be a regexp to match the groups that should go in that
3902 @item subscribe-level
3903 When subscribing new groups by topic (see the @code{subscribe} parameter),
3904 the group will be subscribed with the level specified in the
3905 @code{subscribe-level} instead of @code{gnus-level-default-subscribed}.
3909 Group parameters (of course) override topic parameters, and topic
3910 parameters in sub-topics override topic parameters in super-topics. You
3911 know. Normal inheritance rules. (@dfn{Rules} is here a noun, not a
3912 verb, although you may feel free to disagree with me here.)
3918 2: alt.religion.emacs
3922 0: comp.talk.emacs.recovery
3924 8: comp.binaries.fractals
3925 13: comp.sources.unix
3929 The @samp{Emacs} topic has the topic parameter @code{(score-file
3930 . "emacs.SCORE")}; the @samp{Relief} topic has the topic parameter
3931 @code{(score-file . "relief.SCORE")}; and the @samp{Misc} topic has the
3932 topic parameter @code{(score-file . "emacs.SCORE")}. In addition,
3933 @* @samp{alt.religion.emacs} has the group parameter @code{(score-file
3934 . "religion.SCORE")}.
3936 Now, when you enter @samp{alt.sex.emacs} in the @samp{Relief} topic, you
3937 will get the @file{relief.SCORE} home score file. If you enter the same
3938 group in the @samp{Emacs} topic, you'll get the @file{emacs.SCORE} home
3939 score file. If you enter the group @samp{alt.religion.emacs}, you'll
3940 get the @file{religion.SCORE} home score file.
3942 This seems rather simple and self-evident, doesn't it? Well, yes. But
3943 there are some problems, especially with the @code{total-expiry}
3944 parameter. Say you have a mail group in two topics; one with
3945 @code{total-expiry} and one without. What happens when you do @kbd{M-x
3946 gnus-expire-all-expirable-groups}? Gnus has no way of telling which one
3947 of these topics you mean to expire articles from, so anything may
3948 happen. In fact, I hereby declare that it is @dfn{undefined} what
3949 happens. You just have to be careful if you do stuff like that.
3952 @node Misc Group Stuff
3953 @section Misc Group Stuff
3956 * Scanning New Messages:: Asking Gnus to see whether new messages have arrived.
3957 * Group Information:: Information and help on groups and Gnus.
3958 * Group Timestamp:: Making Gnus keep track of when you last read a group.
3959 * File Commands:: Reading and writing the Gnus files.
3960 * Sieve Commands:: Managing Sieve scripts.
3967 @findex gnus-group-enter-server-mode
3968 Enter the server buffer (@code{gnus-group-enter-server-mode}).
3969 @xref{Server Buffer}.
3973 @findex gnus-group-post-news
3974 Start composing a message (a news by default)
3975 (@code{gnus-group-post-news}). If given a prefix, post to the group
3976 under the point. If the prefix is 1, prompt for a group to post to.
3977 Contrary to what the name of this function suggests, the prepared
3978 article might be a mail instead of a news, if a mail group is specified
3979 with the prefix argument. @xref{Composing Messages}.
3983 @findex gnus-group-mail
3984 Mail a message somewhere (@code{gnus-group-mail}). If given a prefix,
3985 use the posting style of the group under the point. If the prefix is 1,
3986 prompt for a group name to find the posting style.
3987 @xref{Composing Messages}.
3991 @findex gnus-group-news
3992 Start composing a news (@code{gnus-group-news}). If given a prefix,
3993 post to the group under the point. If the prefix is 1, prompt
3994 for group to post to. @xref{Composing Messages}.
3996 This function actually prepares a news even when using mail groups.
3997 This is useful for "posting" messages to mail groups without actually
3998 sending them over the network: they're just saved directly to the group
3999 in question. The corresponding back end must have a request-post method
4000 for this to work though.
4004 Variables for the group buffer:
4008 @item gnus-group-mode-hook
4009 @vindex gnus-group-mode-hook
4010 is called after the group buffer has been
4013 @item gnus-group-prepare-hook
4014 @vindex gnus-group-prepare-hook
4015 is called after the group buffer is
4016 generated. It may be used to modify the buffer in some strange,
4019 @item gnus-group-prepared-hook
4020 @vindex gnus-group-prepare-hook
4021 is called as the very last thing after the group buffer has been
4022 generated. It may be used to move point around, for instance.
4024 @item gnus-permanently-visible-groups
4025 @vindex gnus-permanently-visible-groups
4026 Groups matching this regexp will always be listed in the group buffer,
4027 whether they are empty or not.
4029 @item gnus-group-name-charset-method-alist
4030 @vindex gnus-group-name-charset-method-alist
4031 An alist of method and the charset for group names. It is used to show
4032 non-ASCII group names.
4036 (setq gnus-group-name-charset-method-alist
4037 '(((nntp "news.com.cn") . cn-gb-2312)))
4040 @item gnus-group-name-charset-group-alist
4041 @cindex UTF-8 group names
4042 @vindex gnus-group-name-charset-group-alist
4043 An alist of regexp of group name and the charset for group names. It
4044 is used to show non-ASCII group names. @code{((".*" utf-8))} is the
4045 default value if UTF-8 is supported, otherwise the default is nil.
4049 (setq gnus-group-name-charset-group-alist
4050 '(("\\.com\\.cn:" . cn-gb-2312)))
4055 @node Scanning New Messages
4056 @subsection Scanning New Messages
4057 @cindex new messages
4058 @cindex scanning new news
4064 @findex gnus-group-get-new-news
4065 @c @icon{gnus-group-get-new-news}
4066 Check the server(s) for new articles. If the numerical prefix is used,
4067 this command will check only groups of level @var{arg} and lower
4068 (@code{gnus-group-get-new-news}). If given a non-numerical prefix, this
4069 command will force a total re-reading of the active file(s) from the
4074 @findex gnus-group-get-new-news-this-group
4075 @vindex gnus-goto-next-group-when-activating
4076 @c @icon{gnus-group-get-new-news-this-group}
4077 Check whether new articles have arrived in the current group
4078 (@code{gnus-group-get-new-news-this-group}).
4079 @code{gnus-goto-next-group-when-activating} says whether this command is
4080 to move point to the next group or not. It is @code{t} by default.
4082 @findex gnus-activate-all-groups
4083 @cindex activating groups
4085 @kindex C-c M-g (Group)
4086 Activate absolutely all groups (@code{gnus-activate-all-groups}).
4091 @findex gnus-group-restart
4092 Restart gnus (@code{gnus-group-restart}). This saves the @file{.newsrc}
4093 file(s), closes the connection to all servers, clears up all run-time
4094 gnus variables, and then starts gnus all over again.
4098 @vindex gnus-get-new-news-hook
4099 @code{gnus-get-new-news-hook} is run just before checking for new news.
4101 @vindex gnus-after-getting-new-news-hook
4102 @code{gnus-after-getting-new-news-hook} is run after checking for new
4106 @node Group Information
4107 @subsection Group Information
4108 @cindex group information
4109 @cindex information on groups
4116 @findex gnus-group-fetch-faq
4117 @vindex gnus-group-faq-directory
4120 Try to fetch the FAQ for the current group
4121 (@code{gnus-group-fetch-faq}). Gnus will try to get the FAQ from
4122 @code{gnus-group-faq-directory}, which is usually a directory on a
4123 remote machine. This variable can also be a list of directories. In
4124 that case, giving a prefix to this command will allow you to choose
4125 between the various sites. @code{ange-ftp} (or @code{efs}) will be used
4126 for fetching the file.
4128 If fetching from the first site is unsuccessful, gnus will attempt to go
4129 through @code{gnus-group-faq-directory} and try to open them one by one.
4133 @findex gnus-group-fetch-charter
4134 @vindex gnus-group-charter-alist
4136 Try to open the charter for the current group in a web browser
4137 (@code{gnus-group-fetch-charter}). Query for a group if given a
4140 Gnus will use @code{gnus-group-charter-alist} to find the location of
4141 the charter. If no location is known, Gnus will fetch the control
4142 messages for the group, which in some cases includes the charter.
4146 @findex gnus-group-fetch-control
4147 @vindex gnus-group-fetch-control-use-browse-url
4148 @cindex control message
4149 Fetch the control messages for the group from the archive at
4150 @code{ftp.isc.org} (@code{gnus-group-fetch-control}). Query for a
4151 group if given a prefix argument.
4153 If @code{gnus-group-fetch-control-use-browse-url} is non-nil, Gnus
4154 will open the control messages in a browser using @code{browse-url}.
4155 Otherwise they are fetched using @code{ange-ftp} and displayed in an
4158 Note that the control messages are compressed. To use this command
4159 you need to turn on @code{auto-compression-mode}
4160 (@pxref{(emacs)Compressed Files}).
4164 @c @icon{gnus-group-describe-group}
4166 @kindex C-c C-d (Group)
4167 @cindex describing groups
4168 @cindex group description
4169 @findex gnus-group-describe-group
4170 Describe the current group (@code{gnus-group-describe-group}). If given
4171 a prefix, force Gnus to re-read the description from the server.
4175 @findex gnus-group-describe-all-groups
4176 Describe all groups (@code{gnus-group-describe-all-groups}). If given a
4177 prefix, force gnus to re-read the description file from the server.
4184 @findex gnus-version
4185 Display current gnus version numbers (@code{gnus-version}).
4189 @findex gnus-group-describe-briefly
4190 Give a very short help message (@code{gnus-group-describe-briefly}).
4193 @kindex C-c C-i (Group)
4196 @findex gnus-info-find-node
4197 Go to the gnus info node (@code{gnus-info-find-node}).
4201 @node Group Timestamp
4202 @subsection Group Timestamp
4204 @cindex group timestamps
4206 It can be convenient to let gnus keep track of when you last read a
4207 group. To set the ball rolling, you should add
4208 @code{gnus-group-set-timestamp} to @code{gnus-select-group-hook}:
4211 (add-hook 'gnus-select-group-hook 'gnus-group-set-timestamp)
4214 After doing this, each time you enter a group, it'll be recorded.
4216 This information can be displayed in various ways---the easiest is to
4217 use the @samp{%d} spec in the group line format:
4220 (setq gnus-group-line-format
4221 "%M\%S\%p\%P\%5y: %(%-40,40g%) %d\n")
4224 This will result in lines looking like:
4227 * 0: mail.ding 19961002T012943
4228 0: custom 19961002T012713
4231 As you can see, the date is displayed in compact ISO 8601 format. This
4232 may be a bit too much, so to just display the date, you could say
4236 (setq gnus-group-line-format
4237 "%M\%S\%p\%P\%5y: %(%-40,40g%) %6,6~(cut 2)d\n")
4240 If you would like greater control of the time format, you can use a
4241 user-defined format spec. Something like the following should do the
4245 (setq gnus-group-line-format
4246 "%M\%S\%p\%P\%5y: %(%-40,40g%) %ud\n")
4247 (defun gnus-user-format-function-d (headers)
4248 (let ((time (gnus-group-timestamp gnus-tmp-group)))
4250 (format-time-string "%b %d %H:%M" time)
4256 @subsection File Commands
4257 @cindex file commands
4263 @findex gnus-group-read-init-file
4264 @vindex gnus-init-file
4265 @cindex reading init file
4266 Re-read the init file (@code{gnus-init-file}, which defaults to
4267 @file{~/.gnus}) (@code{gnus-group-read-init-file}).
4271 @findex gnus-group-save-newsrc
4272 @cindex saving .newsrc
4273 Save the @file{.newsrc.eld} file (and @file{.newsrc} if wanted)
4274 (@code{gnus-group-save-newsrc}). If given a prefix, force saving the
4275 file(s) whether Gnus thinks it is necessary or not.
4278 @c @kindex Z (Group)
4279 @c @findex gnus-group-clear-dribble
4280 @c Clear the dribble buffer (@code{gnus-group-clear-dribble}).
4285 @node Sieve Commands
4286 @subsection Sieve Commands
4287 @cindex group sieve commands
4289 Sieve is a server-side mail filtering language. In Gnus you can use
4290 the @code{sieve} group parameter (@pxref{Group Parameters}) to specify
4291 sieve rules that should apply to each group. Gnus provides two
4292 commands to translate all these group parameters into a proper Sieve
4293 script that can be transfered to the server somehow.
4295 @vindex gnus-sieve-file
4296 @vindex gnus-sieve-region-start
4297 @vindex gnus-sieve-region-end
4298 The generated Sieve script is placed in @code{gnus-sieve-file} (by
4299 default @file{~/.sieve}). The Sieve code that Gnus generate is placed
4300 between two delimiters, @code{gnus-sieve-region-start} and
4301 @code{gnus-sieve-region-end}, so you may write additional Sieve code
4302 outside these delimiters that will not be removed the next time you
4303 regenerate the Sieve script.
4305 @vindex gnus-sieve-crosspost
4306 The variable @code{gnus-sieve-crosspost} controls how the Sieve script
4307 is generated. If it is non-nil (the default) articles is placed in
4308 all groups that have matching rules, otherwise the article is only
4309 placed in the group with the first matching rule. For example, the
4310 group parameter @samp{(sieve address "sender"
4311 "owner-ding@@hpc.uh.edu")} will generate the following piece of Sieve
4312 code if @code{gnus-sieve-crosspost} is nil. (When
4313 @code{gnus-sieve-crosspost} is non-nil, it looks the same except that
4314 the line containing the call to @code{stop} is removed.)
4317 if address "sender" "owner-ding@@hpc.uh.edu" @{
4318 fileinto "INBOX.ding";
4323 @xref{Top, ,Top, sieve, Emacs Sieve}.
4329 @findex gnus-sieve-generate
4330 @vindex gnus-sieve-file
4331 @cindex generating sieve script
4332 Regenerate a Sieve script from the @code{sieve} group parameters and
4333 put you into the @code{gnus-sieve-file} without saving it.
4337 @findex gnus-sieve-update
4338 @vindex gnus-sieve-file
4339 @cindex updating sieve script
4340 Regenerates the Gnus managed part of @code{gnus-sieve-file} using the
4341 @code{sieve} group parameters, save the file and upload it to the
4342 server using the @code{sieveshell} program.
4347 @node Summary Buffer
4348 @chapter Summary Buffer
4349 @cindex summary buffer
4351 A line for each article is displayed in the summary buffer. You can
4352 move around, read articles, post articles and reply to articles.
4354 The most common way to a summary buffer is to select a group from the
4355 group buffer (@pxref{Selecting a Group}).
4357 You can have as many summary buffers open as you wish.
4360 * Summary Buffer Format:: Deciding how the summary buffer is to look.
4361 * Summary Maneuvering:: Moving around the summary buffer.
4362 * Choosing Articles:: Reading articles.
4363 * Paging the Article:: Scrolling the current article.
4364 * Reply Followup and Post:: Posting articles.
4365 * Delayed Articles:: Send articles at a later time.
4366 * Marking Articles:: Marking articles as read, expirable, etc.
4367 * Limiting:: You can limit the summary buffer.
4368 * Threading:: How threads are made.
4369 * Sorting the Summary Buffer:: How articles and threads are sorted.
4370 * Asynchronous Fetching:: Gnus might be able to pre-fetch articles.
4371 * Article Caching:: You may store articles in a cache.
4372 * Persistent Articles:: Making articles expiry-resistant.
4373 * Article Backlog:: Having already read articles hang around.
4374 * Saving Articles:: Ways of customizing article saving.
4375 * Decoding Articles:: Gnus can treat series of (uu)encoded articles.
4376 * Article Treatment:: The article buffer can be mangled at will.
4377 * MIME Commands:: Doing MIMEy things with the articles.
4378 * Charsets:: Character set issues.
4379 * Article Commands:: Doing various things with the article buffer.
4380 * Summary Sorting:: Sorting the summary buffer in various ways.
4381 * Finding the Parent:: No child support? Get the parent.
4382 * Alternative Approaches:: Reading using non-default summaries.
4383 * Tree Display:: A more visual display of threads.
4384 * Mail Group Commands:: Some commands can only be used in mail groups.
4385 * Various Summary Stuff:: What didn't fit anywhere else.
4386 * Exiting the Summary Buffer:: Returning to the Group buffer,
4387 or reselecting the current group.
4388 * Crosspost Handling:: How crossposted articles are dealt with.
4389 * Duplicate Suppression:: An alternative when crosspost handling fails.
4390 * Security:: Decrypt and Verify.
4391 * Mailing List:: Mailing list minor mode.
4395 @node Summary Buffer Format
4396 @section Summary Buffer Format
4397 @cindex summary buffer format
4401 \gnusfigure{The Summary Buffer}{180}{
4402 \put(0,0){\epsfig{figure=ps/summary,width=7.5cm}}
4403 \put(445,0){\makebox(0,0)[br]{\epsfig{figure=ps/summary-article,width=7.5cm}}}
4409 * Summary Buffer Lines:: You can specify how summary lines should look.
4410 * To From Newsgroups:: How to not display your own name.
4411 * Summary Buffer Mode Line:: You can say how the mode line should look.
4412 * Summary Highlighting:: Making the summary buffer all pretty and nice.
4415 @findex mail-extract-address-components
4416 @findex gnus-extract-address-components
4417 @vindex gnus-extract-address-components
4418 Gnus will use the value of the @code{gnus-extract-address-components}
4419 variable as a function for getting the name and address parts of a
4420 @code{From} header. Three pre-defined functions exist:
4421 @code{gnus-extract-address-components}, which is the default, quite
4422 fast, and too simplistic solution;
4423 @code{mail-extract-address-components}, which works nicely, but is
4424 slower; and @code{std11-extract-address-components}, which works very
4425 nicely, but is slower. The default function will return the wrong
4426 answer in 5% of the cases. If this is unacceptable to you, use the
4427 other function instead:
4430 (setq gnus-extract-address-components
4431 'mail-extract-address-components)
4434 @vindex gnus-summary-same-subject
4435 @code{gnus-summary-same-subject} is a string indicating that the current
4436 article has the same subject as the previous. This string will be used
4437 with those specs that require it. The default is @code{""}.
4440 @node Summary Buffer Lines
4441 @subsection Summary Buffer Lines
4443 @vindex gnus-summary-line-format
4444 You can change the format of the lines in the summary buffer by changing
4445 the @code{gnus-summary-line-format} variable. It works along the same
4446 lines as a normal @code{format} string, with some extensions
4447 (@pxref{Formatting Variables}).
4449 There should always be a colon or a point position marker on the line;
4450 the cursor always moves to the point position marker or the colon after
4451 performing an operation. (Of course, Gnus wouldn't be Gnus if it wasn't
4452 possible to change this. Just write a new function
4453 @code{gnus-goto-colon} which does whatever you like with the cursor.)
4454 @xref{Positioning Point}.
4456 The default string is @samp{%U%R%z%I%(%[%4L: %-23,23f%]%) %s\n}.
4458 The following format specification characters and extended format
4459 specification(s) are understood:
4465 Subject string. List identifiers stripped,
4466 @code{gnus-list-identifies}. @xref{Article Hiding}.
4468 Subject if the article is the root of the thread or the previous article
4469 had a different subject, @code{gnus-summary-same-subject} otherwise.
4470 (@code{gnus-summary-same-subject} defaults to @code{""}.)
4472 Full @code{From} header.
4474 The name (from the @code{From} header).
4476 The name, @code{To} header or the @code{Newsgroups} header (@pxref{To
4479 The name (from the @code{From} header). This differs from the @code{n}
4480 spec in that it uses the function designated by the
4481 @code{gnus-extract-address-components} variable, which is slower, but
4482 may be more thorough.
4484 The address (from the @code{From} header). This works the same way as
4487 Number of lines in the article.
4489 Number of characters in the article. This specifier is not supported
4490 in some methods (like nnfolder).
4492 Pretty-printed version of the number of characters in the article;
4493 for example, @samp{1.2k} or @samp{0.4M}.
4495 Indentation based on thread level (@pxref{Customizing Threading}).
4497 A complex trn-style thread tree, showing response-connecting trace
4500 Nothing if the article is a root and lots of spaces if it isn't (it
4501 pushes everything after it off the screen).
4503 Opening bracket, which is normally @samp{[}, but can also be @samp{<}
4504 for adopted articles (@pxref{Customizing Threading}).
4506 Closing bracket, which is normally @samp{]}, but can also be @samp{>}
4507 for adopted articles.
4509 One space for each thread level.
4511 Twenty minus thread level spaces.
4513 Unread. @xref{Read Articles}.
4516 This misleadingly named specifier is the @dfn{secondary mark}. This
4517 mark will say whether the article has been replied to, has been cached,
4518 or has been saved. @xref{Other Marks}.
4521 Score as a number (@pxref{Scoring}).
4523 @vindex gnus-summary-zcore-fuzz
4524 Zcore, @samp{+} if above the default level and @samp{-} if below the
4525 default level. If the difference between
4526 @code{gnus-summary-default-score} and the score is less than
4527 @code{gnus-summary-zcore-fuzz}, this spec will not be used.
4535 The @code{Date} in @code{DD-MMM} format.
4537 The @code{Date} in @var{YYYYMMDD}@code{T}@var{HHMMSS} format.
4543 Number of articles in the current sub-thread. Using this spec will slow
4544 down summary buffer generation somewhat.
4546 An @samp{=} (@code{gnus-not-empty-thread-mark}) will be displayed if the
4547 article has any children.
4553 Age sensitive date format. Various date format is defined in
4554 @code{gnus-user-date-format-alist}.
4556 User defined specifier. The next character in the format string should
4557 be a letter. Gnus will call the function
4558 @code{gnus-user-format-function-}@samp{X}, where @samp{X} is the letter
4559 following @samp{%u}. The function will be passed the current header as
4560 argument. The function should return a string, which will be inserted
4561 into the summary just like information from any other summary specifier.
4564 Text between @samp{%(} and @samp{%)} will be highlighted with
4565 @code{gnus-mouse-face} when the mouse point is placed inside the area.
4566 There can only be one such area.
4568 The @samp{%U} (status), @samp{%R} (replied) and @samp{%z} (zcore) specs
4569 have to be handled with care. For reasons of efficiency, gnus will
4570 compute what column these characters will end up in, and ``hard-code''
4571 that. This means that it is invalid to have these specs after a
4572 variable-length spec. Well, you might not be arrested, but your summary
4573 buffer will look strange, which is bad enough.
4575 The smart choice is to have these specs as far to the left as possible.
4576 (Isn't that the case with everything, though? But I digress.)
4578 This restriction may disappear in later versions of gnus.
4581 @node To From Newsgroups
4582 @subsection To From Newsgroups
4586 In some groups (particularly in archive groups), the @code{From} header
4587 isn't very interesting, since all the articles there are written by
4588 you. To display the information in the @code{To} or @code{Newsgroups}
4589 headers instead, you need to decide three things: What information to
4590 gather; where to display it; and when to display it.
4594 @vindex gnus-extra-headers
4595 The reading of extra header information is controlled by the
4596 @code{gnus-extra-headers}. This is a list of header symbols. For
4600 (setq gnus-extra-headers
4601 '(To Newsgroups X-Newsreader))
4604 This will result in Gnus trying to obtain these three headers, and
4605 storing it in header structures for later easy retrieval.
4608 @findex gnus-extra-header
4609 The value of these extra headers can be accessed via the
4610 @code{gnus-extra-header} function. Here's a format line spec that will
4611 access the @code{X-Newsreader} header:
4614 "%~(form (gnus-extra-header 'X-Newsreader))@@"
4618 @vindex gnus-ignored-from-addresses
4619 The @code{gnus-ignored-from-addresses} variable says when the @samp{%f}
4620 summary line spec returns the @code{To}, @code{Newsreader} or
4621 @code{From} header. If this regexp matches the contents of the
4622 @code{From} header, the value of the @code{To} or @code{Newsreader}
4623 headers are used instead.
4627 @vindex nnmail-extra-headers
4628 A related variable is @code{nnmail-extra-headers}, which controls when
4629 to include extra headers when generating overview (@sc{nov}) files. If
4630 you have old overview files, you should regenerate them after changing
4631 this variable, by entering the server buffer using `^', and then `g' on
4632 the appropriate mail server (e.g. nnml) to cause regeneration.
4634 @vindex gnus-summary-line-format
4635 You also have to instruct Gnus to display the data by changing the
4636 @code{%n} spec to the @code{%f} spec in the
4637 @code{gnus-summary-line-format} variable.
4639 In summary, you'd typically put something like the following in
4643 (setq gnus-extra-headers
4645 (setq nnmail-extra-headers gnus-extra-headers)
4646 (setq gnus-summary-line-format
4647 "%U%R%z%I%(%[%4L: %-23,23f%]%) %s\n")
4648 (setq gnus-ignored-from-addresses
4652 (The values listed above are the default values in Gnus. Alter them
4655 A note for news server administrators, or for users who wish to try to
4656 convince their news server administrator to provide some additional
4659 The above is mostly useful for mail groups, where you have control over
4660 the @sc{nov} files that are created. However, if you can persuade your
4661 nntp admin to add (in the usual implementation, notably INN):
4667 to the end of her @file{overview.fmt} file, then you can use that just
4668 as you would the extra headers from the mail groups.
4671 @node Summary Buffer Mode Line
4672 @subsection Summary Buffer Mode Line
4674 @vindex gnus-summary-mode-line-format
4675 You can also change the format of the summary mode bar (@pxref{Mode Line
4676 Formatting}). Set @code{gnus-summary-mode-line-format} to whatever you
4677 like. The default is @samp{Gnus: %%b [%A] %Z}.
4679 Here are the elements you can play with:
4685 Unprefixed group name.
4687 Current article number.
4689 Current article score.
4693 Number of unread articles in this group.
4695 Number of unread articles in this group that aren't displayed in the
4698 A string with the number of unread and unselected articles represented
4699 either as @samp{<%U(+%e) more>} if there are both unread and unselected
4700 articles, and just as @samp{<%U more>} if there are just unread articles
4701 and no unselected ones.
4703 Shortish group name. For instance, @samp{rec.arts.anime} will be
4704 shortened to @samp{r.a.anime}.
4706 Subject of the current article.
4708 User-defined spec (@pxref{User-Defined Specs}).
4710 Name of the current score file (@pxref{Scoring}).
4712 Number of dormant articles (@pxref{Unread Articles}).
4714 Number of ticked articles (@pxref{Unread Articles}).
4716 Number of articles that have been marked as read in this session.
4718 Number of articles expunged by the score files.
4722 @node Summary Highlighting
4723 @subsection Summary Highlighting
4727 @item gnus-visual-mark-article-hook
4728 @vindex gnus-visual-mark-article-hook
4729 This hook is run after selecting an article. It is meant to be used for
4730 highlighting the article in some way. It is not run if
4731 @code{gnus-visual} is @code{nil}.
4733 @item gnus-summary-update-hook
4734 @vindex gnus-summary-update-hook
4735 This hook is called when a summary line is changed. It is not run if
4736 @code{gnus-visual} is @code{nil}.
4738 @item gnus-summary-selected-face
4739 @vindex gnus-summary-selected-face
4740 This is the face (or @dfn{font} as some people call it) used to
4741 highlight the current article in the summary buffer.
4743 @item gnus-summary-highlight
4744 @vindex gnus-summary-highlight
4745 Summary lines are highlighted according to this variable, which is a
4746 list where the elements are of the format @code{(@var{form}
4747 . @var{face})}. If you would, for instance, like ticked articles to be
4748 italic and high-scored articles to be bold, you could set this variable
4751 (((eq mark gnus-ticked-mark) . italic)
4752 ((> score default) . bold))
4754 As you may have guessed, if @var{form} returns a non-@code{nil} value,
4755 @var{face} will be applied to the line.
4759 @node Summary Maneuvering
4760 @section Summary Maneuvering
4761 @cindex summary movement
4763 All the straight movement commands understand the numeric prefix and
4764 behave pretty much as you'd expect.
4766 None of these commands select articles.
4771 @kindex M-n (Summary)
4772 @kindex G M-n (Summary)
4773 @findex gnus-summary-next-unread-subject
4774 Go to the next summary line of an unread article
4775 (@code{gnus-summary-next-unread-subject}).
4779 @kindex M-p (Summary)
4780 @kindex G M-p (Summary)
4781 @findex gnus-summary-prev-unread-subject
4782 Go to the previous summary line of an unread article
4783 (@code{gnus-summary-prev-unread-subject}).
4786 @kindex G g (Summary)
4787 @findex gnus-summary-goto-subject
4788 Ask for an article number and then go to the summary line of that article
4789 without displaying the article (@code{gnus-summary-goto-subject}).
4792 If gnus asks you to press a key to confirm going to the next group, you
4793 can use the @kbd{C-n} and @kbd{C-p} keys to move around the group
4794 buffer, searching for the next group to read without actually returning
4795 to the group buffer.
4797 Variables related to summary movement:
4801 @vindex gnus-auto-select-next
4802 @item gnus-auto-select-next
4803 If you issue one of the movement commands (like @kbd{n}) and there are
4804 no more unread articles after the current one, gnus will offer to go to
4805 the next group. If this variable is @code{t} and the next group is
4806 empty, gnus will exit summary mode and return to the group buffer. If
4807 this variable is neither @code{t} nor @code{nil}, gnus will select the
4808 next group with unread articles. As a special case, if this variable
4809 is @code{quietly}, Gnus will select the next group without asking for
4810 confirmation. If this variable is @code{almost-quietly}, the same
4811 will happen only if you are located on the last article in the group.
4812 Finally, if this variable is @code{slightly-quietly}, the @kbd{Z n}
4813 command will go to the next group without confirmation. Also
4814 @pxref{Group Levels}.
4816 @item gnus-auto-select-same
4817 @vindex gnus-auto-select-same
4818 If non-@code{nil}, all the movement commands will try to go to the next
4819 article with the same subject as the current. (@dfn{Same} here might
4820 mean @dfn{roughly equal}. See @code{gnus-summary-gather-subject-limit}
4821 for details (@pxref{Customizing Threading}).) If there are no more
4822 articles with the same subject, go to the first unread article.
4824 This variable is not particularly useful if you use a threaded display.
4826 @item gnus-summary-check-current
4827 @vindex gnus-summary-check-current
4828 If non-@code{nil}, all the ``unread'' movement commands will not proceed
4829 to the next (or previous) article if the current article is unread.
4830 Instead, they will choose the current article.
4832 @item gnus-auto-center-summary
4833 @vindex gnus-auto-center-summary
4834 If non-@code{nil}, gnus will keep the point in the summary buffer
4835 centered at all times. This makes things quite tidy, but if you have a
4836 slow network connection, or simply do not like this un-Emacsism, you can
4837 set this variable to @code{nil} to get the normal Emacs scrolling
4838 action. This will also inhibit horizontal re-centering of the summary
4839 buffer, which might make it more inconvenient to read extremely long
4842 This variable can also be a number. In that case, center the window at
4843 the given number of lines from the top.
4848 @node Choosing Articles
4849 @section Choosing Articles
4850 @cindex selecting articles
4853 * Choosing Commands:: Commands for choosing articles.
4854 * Choosing Variables:: Variables that influence these commands.
4858 @node Choosing Commands
4859 @subsection Choosing Commands
4861 None of the following movement commands understand the numeric prefix,
4862 and they all select and display an article.
4864 If you want to fetch new articles or redisplay the group, see
4865 @ref{Exiting the Summary Buffer}.
4869 @kindex SPACE (Summary)
4870 @findex gnus-summary-next-page
4871 Select the current article, or, if that one's read already, the next
4872 unread article (@code{gnus-summary-next-page}).
4877 @kindex G n (Summary)
4878 @findex gnus-summary-next-unread-article
4879 @c @icon{gnus-summary-next-unread}
4880 Go to next unread article (@code{gnus-summary-next-unread-article}).
4885 @findex gnus-summary-prev-unread-article
4886 @c @icon{gnus-summary-prev-unread}
4887 Go to previous unread article (@code{gnus-summary-prev-unread-article}).
4892 @kindex G N (Summary)
4893 @findex gnus-summary-next-article
4894 Go to the next article (@code{gnus-summary-next-article}).
4899 @kindex G P (Summary)
4900 @findex gnus-summary-prev-article
4901 Go to the previous article (@code{gnus-summary-prev-article}).
4904 @kindex G C-n (Summary)
4905 @findex gnus-summary-next-same-subject
4906 Go to the next article with the same subject
4907 (@code{gnus-summary-next-same-subject}).
4910 @kindex G C-p (Summary)
4911 @findex gnus-summary-prev-same-subject
4912 Go to the previous article with the same subject
4913 (@code{gnus-summary-prev-same-subject}).
4917 @kindex G f (Summary)
4919 @findex gnus-summary-first-unread-article
4920 Go to the first unread article
4921 (@code{gnus-summary-first-unread-article}).
4925 @kindex G b (Summary)
4927 @findex gnus-summary-best-unread-article
4928 Go to the unread article with the highest score
4929 (@code{gnus-summary-best-unread-article}). If given a prefix argument,
4930 go to the first unread article that has a score over the default score.
4935 @kindex G l (Summary)
4936 @findex gnus-summary-goto-last-article
4937 Go to the previous article read (@code{gnus-summary-goto-last-article}).
4940 @kindex G o (Summary)
4941 @findex gnus-summary-pop-article
4943 @cindex article history
4944 Pop an article off the summary history and go to this article
4945 (@code{gnus-summary-pop-article}). This command differs from the
4946 command above in that you can pop as many previous articles off the
4947 history as you like, while @kbd{l} toggles the two last read articles.
4948 For a somewhat related issue (if you use these commands a lot),
4949 @pxref{Article Backlog}.
4954 @kindex G j (Summary)
4955 @findex gnus-summary-goto-article
4956 Ask for an article number or @code{Message-ID}, and then go to that
4957 article (@code{gnus-summary-goto-article}).
4962 @node Choosing Variables
4963 @subsection Choosing Variables
4965 Some variables relevant for moving and selecting articles:
4968 @item gnus-auto-extend-newsgroup
4969 @vindex gnus-auto-extend-newsgroup
4970 All the movement commands will try to go to the previous (or next)
4971 article, even if that article isn't displayed in the Summary buffer if
4972 this variable is non-@code{nil}. Gnus will then fetch the article from
4973 the server and display it in the article buffer.
4975 @item gnus-select-article-hook
4976 @vindex gnus-select-article-hook
4977 This hook is called whenever an article is selected. By default it
4978 exposes any threads hidden under the selected article. If you wish
4979 that the Agent saves all articles you read, putting
4980 @code{gnus-agent-fetch-selected-article} on this hook should do it.
4982 @item gnus-mark-article-hook
4983 @vindex gnus-mark-article-hook
4984 @findex gnus-summary-mark-unread-as-read
4985 @findex gnus-summary-mark-read-and-unread-as-read
4986 @findex gnus-unread-mark
4987 This hook is called whenever an article is selected. It is intended to
4988 be used for marking articles as read. The default value is
4989 @code{gnus-summary-mark-read-and-unread-as-read}, and will change the
4990 mark of almost any article you read to @code{gnus-unread-mark}. The
4991 only articles not affected by this function are ticked, dormant, and
4992 expirable articles. If you'd instead like to just have unread articles
4993 marked as read, you can use @code{gnus-summary-mark-unread-as-read}
4994 instead. It will leave marks like @code{gnus-low-score-mark},
4995 @code{gnus-del-mark} (and so on) alone.
5000 @node Paging the Article
5001 @section Scrolling the Article
5002 @cindex article scrolling
5007 @kindex SPACE (Summary)
5008 @findex gnus-summary-next-page
5009 Pressing @kbd{SPACE} will scroll the current article forward one page,
5010 or, if you have come to the end of the current article, will choose the
5011 next article (@code{gnus-summary-next-page}).
5014 @kindex DEL (Summary)
5015 @findex gnus-summary-prev-page
5016 Scroll the current article back one page (@code{gnus-summary-prev-page}).
5019 @kindex RET (Summary)
5020 @findex gnus-summary-scroll-up
5021 Scroll the current article one line forward
5022 (@code{gnus-summary-scroll-up}).
5025 @kindex M-RET (Summary)
5026 @findex gnus-summary-scroll-down
5027 Scroll the current article one line backward
5028 (@code{gnus-summary-scroll-down}).
5032 @kindex A g (Summary)
5034 @findex gnus-summary-show-article
5035 @vindex gnus-summary-show-article-charset-alist
5036 (Re)fetch the current article (@code{gnus-summary-show-article}). If
5037 given a prefix, fetch the current article, but don't run any of the
5038 article treatment functions. This will give you a ``raw'' article, just
5039 the way it came from the server.
5041 If given a numerical prefix, you can do semi-manual charset stuff.
5042 @kbd{C-u 0 g cn-gb-2312 RET} will decode the message as if it were
5043 encoded in the @code{cn-gb-2312} charset. If you have
5046 (setq gnus-summary-show-article-charset-alist
5051 then you can say @kbd{C-u 1 g} to get the same effect.
5056 @kindex A < (Summary)
5057 @findex gnus-summary-beginning-of-article
5058 Scroll to the beginning of the article
5059 (@code{gnus-summary-beginning-of-article}).
5064 @kindex A > (Summary)
5065 @findex gnus-summary-end-of-article
5066 Scroll to the end of the article (@code{gnus-summary-end-of-article}).
5070 @kindex A s (Summary)
5072 @findex gnus-summary-isearch-article
5073 Perform an isearch in the article buffer
5074 (@code{gnus-summary-isearch-article}).
5078 @findex gnus-summary-select-article-buffer
5079 Select the article buffer (@code{gnus-summary-select-article-buffer}).
5084 @node Reply Followup and Post
5085 @section Reply, Followup and Post
5088 * Summary Mail Commands:: Sending mail.
5089 * Summary Post Commands:: Sending news.
5090 * Summary Message Commands:: Other Message-related commands.
5091 * Canceling and Superseding::
5095 @node Summary Mail Commands
5096 @subsection Summary Mail Commands
5098 @cindex composing mail
5100 Commands for composing a mail message:
5106 @kindex S r (Summary)
5108 @findex gnus-summary-reply
5109 @c @icon{gnus-summary-mail-reply}
5110 @c @icon{gnus-summary-reply}
5111 Mail a reply to the author of the current article
5112 (@code{gnus-summary-reply}).
5117 @kindex S R (Summary)
5118 @findex gnus-summary-reply-with-original
5119 @c @icon{gnus-summary-reply-with-original}
5120 Mail a reply to the author of the current article and include the
5121 original message (@code{gnus-summary-reply-with-original}). This
5122 command uses the process/prefix convention.
5125 @kindex S w (Summary)
5126 @findex gnus-summary-wide-reply
5127 Mail a wide reply to the author of the current article
5128 (@code{gnus-summary-wide-reply}). A @dfn{wide reply} is a reply that
5129 goes out to all people listed in the @code{To}, @code{From} (or
5130 @code{Reply-to}) and @code{Cc} headers.
5133 @kindex S W (Summary)
5134 @findex gnus-summary-wide-reply-with-original
5135 Mail a wide reply to the current article and include the original
5136 message (@code{gnus-summary-wide-reply-with-original}). This command uses
5137 the process/prefix convention.
5140 @kindex S v (Summary)
5141 @findex gnus-summary-very-wide-reply
5142 Mail a very wide reply to the author of the current article
5143 (@code{gnus-summary-wide-reply}). A @dfn{very wide reply} is a reply
5144 that goes out to all people listed in the @code{To}, @code{From} (or
5145 @code{Reply-to}) and @code{Cc} headers in all the process/prefixed
5146 articles. This command uses the process/prefix convention.
5149 @kindex S V (Summary)
5150 @findex gnus-summary-very-wide-reply-with-original
5151 Mail a very wide reply to the author of the current article and include the
5152 original message (@code{gnus-summary-very-wide-reply-with-original}). This
5153 command uses the process/prefix convention.
5156 @kindex S B r (Summary)
5157 @findex gnus-summary-reply-broken-reply-to
5158 Mail a reply to the author of the current article but ignore the
5159 @code{Reply-To} field (@code{gnus-summary-reply-broken-reply-to}).
5162 @kindex S B R (Summary)
5163 @findex gnus-summary-reply-broken-reply-to-with-original
5164 Mail a reply to the author of the current article and include the
5165 original message but ignore the @code{Reply-To} field
5166 (@code{gnus-summary-reply-broken-reply-to-with-original}).
5170 @kindex S o m (Summary)
5171 @kindex C-c C-f (Summary)
5172 @findex gnus-summary-mail-forward
5173 @c @icon{gnus-summary-mail-forward}
5174 Forward the current article to some other person
5175 (@code{gnus-summary-mail-forward}). If given a prefix, include the full
5176 headers of the forwarded article.
5181 @kindex S m (Summary)
5182 @findex gnus-summary-mail-other-window
5183 @c @icon{gnus-summary-mail-originate}
5184 Prepare a mail (@code{gnus-summary-mail-other-window}). By default, use
5185 the posting style of the current group. If given a prefix, disable that.
5186 If the prefix is 1, prompt for a group name to find the posting style.
5191 @kindex S i (Summary)
5192 @findex gnus-summary-news-other-window
5193 Prepare a news (@code{gnus-summary-news-other-window}). By default,
5194 post to the current group. If given a prefix, disable that. If the
5195 prefix is 1, prompt for a group to post to.
5197 This function actually prepares a news even when using mail groups.
5198 This is useful for "posting" messages to mail groups without actually
5199 sending them over the network: they're just saved directly to the group
5200 in question. The corresponding back end must have a request-post method
5201 for this to work though.
5204 @kindex S D b (Summary)
5205 @findex gnus-summary-resend-bounced-mail
5206 @cindex bouncing mail
5207 If you have sent a mail, but the mail was bounced back to you for some
5208 reason (wrong address, transient failure), you can use this command to
5209 resend that bounced mail (@code{gnus-summary-resend-bounced-mail}). You
5210 will be popped into a mail buffer where you can edit the headers before
5211 sending the mail off again. If you give a prefix to this command, and
5212 the bounced mail is a reply to some other mail, gnus will try to fetch
5213 that mail and display it for easy perusal of its headers. This might
5214 very well fail, though.
5217 @kindex S D r (Summary)
5218 @findex gnus-summary-resend-message
5219 Not to be confused with the previous command,
5220 @code{gnus-summary-resend-message} will prompt you for an address to
5221 send the current message off to, and then send it to that place. The
5222 headers of the message won't be altered---but lots of headers that say
5223 @code{Resent-To}, @code{Resent-From} and so on will be added. This
5224 means that you actually send a mail to someone that has a @code{To}
5225 header that (probably) points to yourself. This will confuse people.
5226 So, natcherly you'll only do that if you're really eVIl.
5228 This command is mainly used if you have several accounts and want to
5229 ship a mail to a different account of yours. (If you're both
5230 @code{root} and @code{postmaster} and get a mail for @code{postmaster}
5231 to the @code{root} account, you may want to resend it to
5232 @code{postmaster}. Ordnung muss sein!
5234 This command understands the process/prefix convention
5235 (@pxref{Process/Prefix}).
5238 @kindex S O m (Summary)
5239 @findex gnus-summary-digest-mail-forward
5240 Digest the current series (@pxref{Decoding Articles}) and forward the
5241 result using mail (@code{gnus-summary-digest-mail-forward}). This
5242 command uses the process/prefix convention (@pxref{Process/Prefix}).
5245 @kindex S M-c (Summary)
5246 @findex gnus-summary-mail-crosspost-complaint
5247 @cindex crossposting
5248 @cindex excessive crossposting
5249 Send a complaint about excessive crossposting to the author of the
5250 current article (@code{gnus-summary-mail-crosspost-complaint}).
5252 @findex gnus-crosspost-complaint
5253 This command is provided as a way to fight back against the current
5254 crossposting pandemic that's sweeping Usenet. It will compose a reply
5255 using the @code{gnus-crosspost-complaint} variable as a preamble. This
5256 command understands the process/prefix convention
5257 (@pxref{Process/Prefix}) and will prompt you before sending each mail.
5261 Also @xref{Header Commands, ,Header Commands, message, The Message
5262 Manual}, for more information.
5265 @node Summary Post Commands
5266 @subsection Summary Post Commands
5268 @cindex composing news
5270 Commands for posting a news article:
5276 @kindex S p (Summary)
5277 @findex gnus-summary-post-news
5278 @c @icon{gnus-summary-post-news}
5279 Prepare for posting an article (@code{gnus-summary-post-news}). By
5280 default, post to the current group. If given a prefix, disable that.
5281 If the prefix is 1, prompt for another group instead.
5286 @kindex S f (Summary)
5287 @findex gnus-summary-followup
5288 @c @icon{gnus-summary-followup}
5289 Post a followup to the current article (@code{gnus-summary-followup}).
5293 @kindex S F (Summary)
5295 @c @icon{gnus-summary-followup-with-original}
5296 @findex gnus-summary-followup-with-original
5297 Post a followup to the current article and include the original message
5298 (@code{gnus-summary-followup-with-original}). This command uses the
5299 process/prefix convention.
5302 @kindex S n (Summary)
5303 @findex gnus-summary-followup-to-mail
5304 Post a followup to the current article via news, even if you got the
5305 message through mail (@code{gnus-summary-followup-to-mail}).
5308 @kindex S N (Summary)
5309 @findex gnus-summary-followup-to-mail-with-original
5310 Post a followup to the current article via news, even if you got the
5311 message through mail and include the original message
5312 (@code{gnus-summary-followup-to-mail-with-original}). This command uses
5313 the process/prefix convention.
5316 @kindex S o p (Summary)
5317 @findex gnus-summary-post-forward
5318 Forward the current article to a newsgroup
5319 (@code{gnus-summary-post-forward}). If given a prefix, include the full
5320 headers of the forwarded article.
5323 @kindex S O p (Summary)
5324 @findex gnus-summary-digest-post-forward
5326 @cindex making digests
5327 Digest the current series and forward the result to a newsgroup
5328 (@code{gnus-summary-digest-post-forward}). This command uses the
5329 process/prefix convention.
5332 @kindex S u (Summary)
5333 @findex gnus-uu-post-news
5334 @c @icon{gnus-uu-post-news}
5335 Uuencode a file, split it into parts, and post it as a series
5336 (@code{gnus-uu-post-news}). (@pxref{Uuencoding and Posting}).
5339 Also @xref{Header Commands, ,Header Commands, message, The Message
5340 Manual}, for more information.
5343 @node Summary Message Commands
5344 @subsection Summary Message Commands
5348 @kindex S y (Summary)
5349 @findex gnus-summary-yank-message
5350 Yank the current article into an already existing Message composition
5351 buffer (@code{gnus-summary-yank-message}). This command prompts for
5352 what message buffer you want to yank into, and understands the
5353 process/prefix convention (@pxref{Process/Prefix}).
5358 @node Canceling and Superseding
5359 @subsection Canceling Articles
5360 @cindex canceling articles
5361 @cindex superseding articles
5363 Have you ever written something, and then decided that you really,
5364 really, really wish you hadn't posted that?
5366 Well, you can't cancel mail, but you can cancel posts.
5368 @findex gnus-summary-cancel-article
5370 @c @icon{gnus-summary-cancel-article}
5371 Find the article you wish to cancel (you can only cancel your own
5372 articles, so don't try any funny stuff). Then press @kbd{C} or @kbd{S
5373 c} (@code{gnus-summary-cancel-article}). Your article will be
5374 canceled---machines all over the world will be deleting your article.
5375 This command uses the process/prefix convention (@pxref{Process/Prefix}).
5377 Be aware, however, that not all sites honor cancels, so your article may
5378 live on here and there, while most sites will delete the article in
5381 Gnus will use the ``current'' select method when canceling. If you
5382 want to use the standard posting method, use the @samp{a} symbolic
5383 prefix (@pxref{Symbolic Prefixes}).
5385 If you discover that you have made some mistakes and want to do some
5386 corrections, you can post a @dfn{superseding} article that will replace
5387 your original article.
5389 @findex gnus-summary-supersede-article
5391 Go to the original article and press @kbd{S s}
5392 (@code{gnus-summary-supersede-article}). You will be put in a buffer
5393 where you can edit the article all you want before sending it off the
5396 The same goes for superseding as for canceling, only more so: Some
5397 sites do not honor superseding. On those sites, it will appear that you
5398 have posted almost the same article twice.
5400 If you have just posted the article, and change your mind right away,
5401 there is a trick you can use to cancel/supersede the article without
5402 waiting for the article to appear on your site first. You simply return
5403 to the post buffer (which is called @code{*sent ...*}). There you will
5404 find the article you just posted, with all the headers intact. Change
5405 the @code{Message-ID} header to a @code{Cancel} or @code{Supersedes}
5406 header by substituting one of those words for the word
5407 @code{Message-ID}. Then just press @kbd{C-c C-c} to send the article as
5408 you would do normally. The previous article will be
5409 canceled/superseded.
5411 Just remember, kids: There is no 'c' in 'supersede'.
5413 @node Delayed Articles
5414 @section Delayed Articles
5415 @cindex delayed sending
5416 @cindex send delayed
5418 Sometimes, you might wish to delay the sending of a message. For
5419 example, you might wish to arrange for a message to turn up just in time
5420 to remind your about the birthday of your Significant Other. For this,
5421 there is the @code{gnus-delay} package. Setup is simple:
5424 (gnus-delay-initialize)
5427 @findex gnus-delay-article
5428 Normally, to send a message you use the @kbd{C-c C-c} command from
5429 Message mode. To delay a message, use @kbd{C-c C-j}
5430 (@code{gnus-delay-article}) instead. This will ask you for how long the
5431 message should be delayed. Possible answers are:
5435 A time span. Consists of an integer and a letter. For example,
5436 @code{42d} means to delay for 42 days. Available letters are @code{m}
5437 (minutes), @code{h} (hours), @code{d} (days), @code{w} (weeks), @code{M}
5438 (months) and @code{Y} (years).
5441 A specific date. Looks like @code{YYYYY-MM-DD}. The message will be
5442 delayed until that day, at a specific time (eight o'clock by default).
5443 See also @code{gnus-delay-default-hour}.
5446 A specific time of day. Given in @code{hh:mm} format, 24h, no am/pm
5447 stuff. The deadline will be at that time today, except if that time has
5448 already passed, then it's at the given time tomorrow. So if it's ten
5449 o'clock in the morning and you specify @code{11:15}, then the deadline
5450 is one hour and fifteen minutes hence. But if you specify @code{9:20},
5451 that means a time tomorrow.
5454 The action of the @code{gnus-delay-article} command is influenced by a
5455 couple of variables:
5458 @item gnus-delay-default-hour
5459 @vindex gnus-delay-default-hour
5460 When you specify a specific date, the message will be due on that hour
5461 on the given date. Possible values are integers 0 through 23.
5463 @item gnus-delay-default-delay
5464 @vindex gnus-delay-default-delay
5465 This is a string and gives the default delay. It can be of any of the
5466 formats described above.
5468 @item gnus-delay-group
5469 @vindex gnus-delay-group
5470 Delayed articles will be kept in this group on the drafts server until
5471 they are due. You probably don't need to change this. The default
5472 value is @code{"delayed"}.
5474 @item gnus-delay-header
5475 @vindex gnus-delay-header
5476 The deadline for each article will be stored in a header. This variable
5477 is a string and gives the header name. You probably don't need to
5478 change this. The default value is @code{"X-Gnus-Delayed"}.
5481 The way delaying works is like this: when you use the
5482 @code{gnus-delay-article} command, you give a certain delay. Gnus
5483 calculates the deadline of the message and stores it in the
5484 @code{X-Gnus-Delayed} header and puts the message in the
5485 @code{nndraft:delayed} group.
5487 And whenever you get new news, Gnus looks through the group for articles
5488 which are due and sends them. It uses the @code{gnus-delay-send-queue}
5489 function for this. By default, this function is added to the hook
5490 @code{gnus-get-new-news-hook}. But of course, you can change this.
5491 Maybe you want to use the demon to send drafts? Just tell the demon to
5492 execute the @code{gnus-delay-send-queue} function.
5495 @item gnus-delay-initialize
5496 @findex gnus-delay-initialize
5498 By default, this function installs @code{gnus-delay-send-queue} in
5499 @code{gnus-get-new-news-hook}. But it accepts the optional second
5500 argument @code{no-check}. If it is non-nil,
5501 @code{gnus-get-new-news-hook} is not changed. The optional first
5502 argument is ignored.
5504 For example, @code{(gnus-delay-initialize nil t)} means to do nothing.
5505 Presumably, you want to use the demon for sending due delayed articles.
5506 Just don't forget to set that up :-)
5510 @node Marking Articles
5511 @section Marking Articles
5512 @cindex article marking
5513 @cindex article ticking
5516 There are several marks you can set on an article.
5518 You have marks that decide the @dfn{readedness} (whoo, neato-keano
5519 neologism ohoy!) of the article. Alphabetic marks generally mean
5520 @dfn{read}, while non-alphabetic characters generally mean @dfn{unread}.
5522 In addition, you also have marks that do not affect readedness.
5525 * Unread Articles:: Marks for unread articles.
5526 * Read Articles:: Marks for read articles.
5527 * Other Marks:: Marks that do not affect readedness.
5531 There's a plethora of commands for manipulating these marks:
5535 * Setting Marks:: How to set and remove marks.
5536 * Generic Marking Commands:: How to customize the marking.
5537 * Setting Process Marks:: How to mark articles for later processing.
5541 @node Unread Articles
5542 @subsection Unread Articles
5544 The following marks mark articles as (kinda) unread, in one form or
5549 @vindex gnus-ticked-mark
5550 Marked as ticked (@code{gnus-ticked-mark}).
5552 @dfn{Ticked articles} are articles that will remain visible always. If
5553 you see an article that you find interesting, or you want to put off
5554 reading it, or replying to it, until sometime later, you'd typically
5555 tick it. However, articles can be expired (from news servers by the
5556 news server software, Gnus itself never expires ticked messages), so if
5557 you want to keep an article forever, you'll have to make it persistent
5558 (@pxref{Persistent Articles}).
5561 @vindex gnus-dormant-mark
5562 Marked as dormant (@code{gnus-dormant-mark}).
5564 @dfn{Dormant articles} will only appear in the summary buffer if there
5565 are followups to it. If you want to see them even if they don't have
5566 followups, you can use the @kbd{/ D} command (@pxref{Limiting}).
5567 Otherwise (except for the visibility issue), they are just like ticked
5571 @vindex gnus-unread-mark
5572 Marked as unread (@code{gnus-unread-mark}).
5574 @dfn{Unread articles} are articles that haven't been read at all yet.
5579 @subsection Read Articles
5580 @cindex expirable mark
5582 All the following marks mark articles as read.
5587 @vindex gnus-del-mark
5588 These are articles that the user has marked as read with the @kbd{d}
5589 command manually, more or less (@code{gnus-del-mark}).
5592 @vindex gnus-read-mark
5593 Articles that have actually been read (@code{gnus-read-mark}).
5596 @vindex gnus-ancient-mark
5597 Articles that were marked as read in previous sessions and are now
5598 @dfn{old} (@code{gnus-ancient-mark}).
5601 @vindex gnus-killed-mark
5602 Marked as killed (@code{gnus-killed-mark}).
5605 @vindex gnus-kill-file-mark
5606 Marked as killed by kill files (@code{gnus-kill-file-mark}).
5609 @vindex gnus-low-score-mark
5610 Marked as read by having too low a score (@code{gnus-low-score-mark}).
5613 @vindex gnus-catchup-mark
5614 Marked as read by a catchup (@code{gnus-catchup-mark}).
5617 @vindex gnus-canceled-mark
5618 Canceled article (@code{gnus-canceled-mark})
5621 @vindex gnus-souped-mark
5622 @sc{soup}ed article (@code{gnus-souped-mark}). @xref{SOUP}.
5625 @vindex gnus-sparse-mark
5626 Sparsely reffed article (@code{gnus-sparse-mark}). @xref{Customizing
5630 @vindex gnus-duplicate-mark
5631 Article marked as read by duplicate suppression
5632 (@code{gnus-duplicate-mark}). @xref{Duplicate Suppression}.
5636 All these marks just mean that the article is marked as read, really.
5637 They are interpreted differently when doing adaptive scoring, though.
5639 One more special mark, though:
5643 @vindex gnus-expirable-mark
5644 Marked as expirable (@code{gnus-expirable-mark}).
5646 Marking articles as @dfn{expirable} (or have them marked as such
5647 automatically) doesn't make much sense in normal groups---a user doesn't
5648 control expiring of news articles, but in mail groups, for instance,
5649 articles marked as @dfn{expirable} can be deleted by gnus at
5655 @subsection Other Marks
5656 @cindex process mark
5659 There are some marks that have nothing to do with whether the article is
5665 You can set a bookmark in the current article. Say you are reading a
5666 long thesis on cats' urinary tracts, and have to go home for dinner
5667 before you've finished reading the thesis. You can then set a bookmark
5668 in the article, and gnus will jump to this bookmark the next time it
5669 encounters the article. @xref{Setting Marks}.
5672 @vindex gnus-replied-mark
5673 All articles that you have replied to or made a followup to (i.e., have
5674 answered) will be marked with an @samp{A} in the second column
5675 (@code{gnus-replied-mark}).
5678 @vindex gnus-forwarded-mark
5679 All articles that you have forwarded will be marked with an @samp{F} in
5680 the second column (@code{gnus-forwarded-mark}).
5683 @vindex gnus-cached-mark
5684 Articles stored in the article cache will be marked with an @samp{*} in
5685 the second column (@code{gnus-cached-mark}). @xref{Article Caching}.
5688 @vindex gnus-saved-mark
5689 Articles ``saved'' (in some manner or other; not necessarily
5690 religiously) are marked with an @samp{S} in the second column
5691 (@code{gnus-saved-mark}).
5694 @vindex gnus-recent-mark
5695 Articles that according to the server haven't been shown to the user
5696 before are marked with a @samp{N} in the second column
5697 (@code{gnus-recent-mark}). Note that not all servers support this
5698 mark, in which case it simply never appears. Compare with
5699 @code{gnus-unseen-mark}.
5702 @vindex gnus-unseen-mark
5703 Articles that haven't been seen before in Gnus by the user are marked
5704 with a @samp{.} in the second column (@code{gnus-unseen-mark}).
5705 Compare with @code{gnus-recent-mark}.
5708 @vindex gnus-undownloaded-mark
5709 When using the Gnus agent @pxref{Agent Basics}, some articles might not
5710 have been downloaded. Such articles cannot be viewed while you are
5711 offline (unplugged). These articles get the @samp{@@} mark in the
5712 first column. (The variable @code{gnus-undownloaded-mark} controls
5713 which character to use.)
5716 @vindex gnus-downloadable-mark
5717 The Gnus agent @pxref{Agent Basics} downloads some articles
5718 automatically, but it is also possible to explicitly mark articles for
5719 download, even if they would not be downloaded automatically. Such
5720 explicitly-marked articles get the @samp{%} mark in the first column.
5721 (The variable @code{gnus-downloadable-mark} controls which character to
5725 @vindex gnus-not-empty-thread-mark
5726 @vindex gnus-empty-thread-mark
5727 If the @samp{%e} spec is used, the presence of threads or not will be
5728 marked with @code{gnus-not-empty-thread-mark} and
5729 @code{gnus-empty-thread-mark} in the third column, respectively.
5732 @vindex gnus-process-mark
5733 Finally we have the @dfn{process mark} (@code{gnus-process-mark}). A
5734 variety of commands react to the presence of the process mark. For
5735 instance, @kbd{X u} (@code{gnus-uu-decode-uu}) will uudecode and view
5736 all articles that have been marked with the process mark. Articles
5737 marked with the process mark have a @samp{#} in the second column.
5741 You might have noticed that most of these ``non-readedness'' marks
5742 appear in the second column by default. So if you have a cached, saved,
5743 replied article that you have process-marked, what will that look like?
5745 Nothing much. The precedence rules go as follows: process -> cache ->
5746 replied -> saved. So if the article is in the cache and is replied,
5747 you'll only see the cache mark and not the replied mark.
5751 @subsection Setting Marks
5752 @cindex setting marks
5754 All the marking commands understand the numeric prefix.
5759 @kindex M c (Summary)
5760 @kindex M-u (Summary)
5761 @findex gnus-summary-clear-mark-forward
5762 @cindex mark as unread
5763 Clear all readedness-marks from the current article
5764 (@code{gnus-summary-clear-mark-forward}). In other words, mark the
5770 @kindex M t (Summary)
5771 @findex gnus-summary-tick-article-forward
5772 Tick the current article (@code{gnus-summary-tick-article-forward}).
5773 @xref{Article Caching}.
5778 @kindex M ? (Summary)
5779 @findex gnus-summary-mark-as-dormant
5780 Mark the current article as dormant
5781 (@code{gnus-summary-mark-as-dormant}). @xref{Article Caching}.
5785 @kindex M d (Summary)
5787 @findex gnus-summary-mark-as-read-forward
5788 Mark the current article as read
5789 (@code{gnus-summary-mark-as-read-forward}).
5793 @findex gnus-summary-mark-as-read-backward
5794 Mark the current article as read and move point to the previous line
5795 (@code{gnus-summary-mark-as-read-backward}).
5800 @kindex M k (Summary)
5801 @findex gnus-summary-kill-same-subject-and-select
5802 Mark all articles that have the same subject as the current one as read,
5803 and then select the next unread article
5804 (@code{gnus-summary-kill-same-subject-and-select}).
5808 @kindex M K (Summary)
5809 @kindex C-k (Summary)
5810 @findex gnus-summary-kill-same-subject
5811 Mark all articles that have the same subject as the current one as read
5812 (@code{gnus-summary-kill-same-subject}).
5815 @kindex M C (Summary)
5816 @findex gnus-summary-catchup
5817 @c @icon{gnus-summary-catchup}
5818 Mark all unread articles as read (@code{gnus-summary-catchup}).
5821 @kindex M C-c (Summary)
5822 @findex gnus-summary-catchup-all
5823 Mark all articles in the group as read---even the ticked and dormant
5824 articles (@code{gnus-summary-catchup-all}).
5827 @kindex M H (Summary)
5828 @findex gnus-summary-catchup-to-here
5829 Catchup the current group to point (before the point)
5830 (@code{gnus-summary-catchup-to-here}).
5833 @kindex M h (Summary)
5834 @findex gnus-summary-catchup-from-here
5835 Catchup the current group from point (after the point)
5836 (@code{gnus-summary-catchup-from-here}).
5839 @kindex C-w (Summary)
5840 @findex gnus-summary-mark-region-as-read
5841 Mark all articles between point and mark as read
5842 (@code{gnus-summary-mark-region-as-read}).
5845 @kindex M V k (Summary)
5846 @findex gnus-summary-kill-below
5847 Kill all articles with scores below the default score (or below the
5848 numeric prefix) (@code{gnus-summary-kill-below}).
5852 @kindex M e (Summary)
5854 @findex gnus-summary-mark-as-expirable
5855 Mark the current article as expirable
5856 (@code{gnus-summary-mark-as-expirable}).
5859 @kindex M b (Summary)
5860 @findex gnus-summary-set-bookmark
5861 Set a bookmark in the current article
5862 (@code{gnus-summary-set-bookmark}).
5865 @kindex M B (Summary)
5866 @findex gnus-summary-remove-bookmark
5867 Remove the bookmark from the current article
5868 (@code{gnus-summary-remove-bookmark}).
5871 @kindex M V c (Summary)
5872 @findex gnus-summary-clear-above
5873 Clear all marks from articles with scores over the default score (or
5874 over the numeric prefix) (@code{gnus-summary-clear-above}).
5877 @kindex M V u (Summary)
5878 @findex gnus-summary-tick-above
5879 Tick all articles with scores over the default score (or over the
5880 numeric prefix) (@code{gnus-summary-tick-above}).
5883 @kindex M V m (Summary)
5884 @findex gnus-summary-mark-above
5885 Prompt for a mark, and mark all articles with scores over the default
5886 score (or over the numeric prefix) with this mark
5887 (@code{gnus-summary-clear-above}).
5890 @vindex gnus-summary-goto-unread
5891 The @code{gnus-summary-goto-unread} variable controls what action should
5892 be taken after setting a mark. If non-@code{nil}, point will move to
5893 the next/previous unread article. If @code{nil}, point will just move
5894 one line up or down. As a special case, if this variable is
5895 @code{never}, all the marking commands as well as other commands (like
5896 @kbd{SPACE}) will move to the next article, whether it is unread or not.
5897 The default is @code{t}.
5900 @node Generic Marking Commands
5901 @subsection Generic Marking Commands
5903 Some people would like the command that ticks an article (@kbd{!}) go to
5904 the next article. Others would like it to go to the next unread
5905 article. Yet others would like it to stay on the current article. And
5906 even though I haven't heard of anybody wanting it to go to the
5907 previous (unread) article, I'm sure there are people that want that as
5910 Multiply these five behaviors with five different marking commands, and
5911 you get a potentially complex set of variable to control what each
5914 To sidestep that mess, Gnus provides commands that do all these
5915 different things. They can be found on the @kbd{M M} map in the summary
5916 buffer. Type @kbd{M M C-h} to see them all---there are too many of them
5917 to list in this manual.
5919 While you can use these commands directly, most users would prefer
5920 altering the summary mode keymap. For instance, if you would like the
5921 @kbd{!} command to go to the next article instead of the next unread
5922 article, you could say something like:
5925 (add-hook 'gnus-summary-mode-hook 'my-alter-summary-map)
5926 (defun my-alter-summary-map ()
5927 (local-set-key "!" 'gnus-summary-put-mark-as-ticked-next))
5933 (defun my-alter-summary-map ()
5934 (local-set-key "!" "MM!n"))
5938 @node Setting Process Marks
5939 @subsection Setting Process Marks
5940 @cindex setting process marks
5942 Process marks are displayed as @code{#} in the summary buffer, and are
5943 used for marking articles in such a way that other commands will
5944 process these articles. For instance, if you process mark four
5945 articles and then use the @kbd{*} command, Gnus will enter these four
5946 commands into the cache. For more information,
5947 @pxref{Process/Prefix}.
5954 @kindex M P p (Summary)
5955 @findex gnus-summary-mark-as-processable
5956 Mark the current article with the process mark
5957 (@code{gnus-summary-mark-as-processable}).
5958 @findex gnus-summary-unmark-as-processable
5962 @kindex M P u (Summary)
5963 @kindex M-# (Summary)
5964 Remove the process mark, if any, from the current article
5965 (@code{gnus-summary-unmark-as-processable}).
5968 @kindex M P U (Summary)
5969 @findex gnus-summary-unmark-all-processable
5970 Remove the process mark from all articles
5971 (@code{gnus-summary-unmark-all-processable}).
5974 @kindex M P i (Summary)
5975 @findex gnus-uu-invert-processable
5976 Invert the list of process marked articles
5977 (@code{gnus-uu-invert-processable}).
5980 @kindex M P R (Summary)
5981 @findex gnus-uu-mark-by-regexp
5982 Mark articles that have a @code{Subject} header that matches a regular
5983 expression (@code{gnus-uu-mark-by-regexp}).
5986 @kindex M P G (Summary)
5987 @findex gnus-uu-unmark-by-regexp
5988 Unmark articles that have a @code{Subject} header that matches a regular
5989 expression (@code{gnus-uu-unmark-by-regexp}).
5992 @kindex M P r (Summary)
5993 @findex gnus-uu-mark-region
5994 Mark articles in region (@code{gnus-uu-mark-region}).
5998 @findex gnus-uu-unmark-region
5999 Unmark articles in region (@code{gnus-uu-unmark-region}).
6002 @kindex M P t (Summary)
6003 @findex gnus-uu-mark-thread
6004 Mark all articles in the current (sub)thread
6005 (@code{gnus-uu-mark-thread}).
6008 @kindex M P T (Summary)
6009 @findex gnus-uu-unmark-thread
6010 Unmark all articles in the current (sub)thread
6011 (@code{gnus-uu-unmark-thread}).
6014 @kindex M P v (Summary)
6015 @findex gnus-uu-mark-over
6016 Mark all articles that have a score above the prefix argument
6017 (@code{gnus-uu-mark-over}).
6020 @kindex M P s (Summary)
6021 @findex gnus-uu-mark-series
6022 Mark all articles in the current series (@code{gnus-uu-mark-series}).
6025 @kindex M P S (Summary)
6026 @findex gnus-uu-mark-sparse
6027 Mark all series that have already had some articles marked
6028 (@code{gnus-uu-mark-sparse}).
6031 @kindex M P a (Summary)
6032 @findex gnus-uu-mark-all
6033 Mark all articles in series order (@code{gnus-uu-mark-series}).
6036 @kindex M P b (Summary)
6037 @findex gnus-uu-mark-buffer
6038 Mark all articles in the buffer in the order they appear
6039 (@code{gnus-uu-mark-buffer}).
6042 @kindex M P k (Summary)
6043 @findex gnus-summary-kill-process-mark
6044 Push the current process mark set onto the stack and unmark all articles
6045 (@code{gnus-summary-kill-process-mark}).
6048 @kindex M P y (Summary)
6049 @findex gnus-summary-yank-process-mark
6050 Pop the previous process mark set from the stack and restore it
6051 (@code{gnus-summary-yank-process-mark}).
6054 @kindex M P w (Summary)
6055 @findex gnus-summary-save-process-mark
6056 Push the current process mark set onto the stack
6057 (@code{gnus-summary-save-process-mark}).
6061 Also see the @kbd{&} command in @pxref{Searching for Articles} for how to
6062 set process marks based on article body contents.
6069 It can be convenient to limit the summary buffer to just show some
6070 subset of the articles currently in the group. The effect most limit
6071 commands have is to remove a few (or many) articles from the summary
6074 All limiting commands work on subsets of the articles already fetched
6075 from the servers. None of these commands query the server for
6076 additional articles.
6082 @kindex / / (Summary)
6083 @findex gnus-summary-limit-to-subject
6084 Limit the summary buffer to articles that match some subject
6085 (@code{gnus-summary-limit-to-subject}). If given a prefix, exclude
6089 @kindex / a (Summary)
6090 @findex gnus-summary-limit-to-author
6091 Limit the summary buffer to articles that match some author
6092 (@code{gnus-summary-limit-to-author}). If given a prefix, exclude
6096 @kindex / x (Summary)
6097 @findex gnus-summary-limit-to-extra
6098 Limit the summary buffer to articles that match one of the ``extra''
6099 headers (@pxref{To From Newsgroups})
6100 (@code{gnus-summary-limit-to-extra}). If given a prefix, exclude
6105 @kindex / u (Summary)
6107 @findex gnus-summary-limit-to-unread
6108 Limit the summary buffer to articles not marked as read
6109 (@code{gnus-summary-limit-to-unread}). If given a prefix, limit the
6110 buffer to articles strictly unread. This means that ticked and
6111 dormant articles will also be excluded.
6114 @kindex / m (Summary)
6115 @findex gnus-summary-limit-to-marks
6116 Ask for a mark and then limit to all articles that have been marked
6117 with that mark (@code{gnus-summary-limit-to-marks}).
6120 @kindex / t (Summary)
6121 @findex gnus-summary-limit-to-age
6122 Ask for a number and then limit the summary buffer to articles older than (or equal to) that number of days
6123 (@code{gnus-summary-limit-to-age}). If given a prefix, limit to
6124 articles younger than that number of days.
6127 @kindex / n (Summary)
6128 @findex gnus-summary-limit-to-articles
6129 Limit the summary buffer to the current article
6130 (@code{gnus-summary-limit-to-articles}). Uses the process/prefix
6131 convention (@pxref{Process/Prefix}).
6134 @kindex / w (Summary)
6135 @findex gnus-summary-pop-limit
6136 Pop the previous limit off the stack and restore it
6137 (@code{gnus-summary-pop-limit}). If given a prefix, pop all limits off
6141 @kindex / . (Summary)
6142 @findex gnus-summary-limit-to-unseen
6143 Limit the summary buffer to the unseen articles
6144 (@code{gnus-summary-limit-to-unseen}).
6147 @kindex / v (Summary)
6148 @findex gnus-summary-limit-to-score
6149 Limit the summary buffer to articles that have a score at or above some
6150 score (@code{gnus-summary-limit-to-score}).
6153 @kindex / p (Summary)
6154 @findex gnus-summary-limit-to-display-predicate
6155 Limit the summary buffer to articles that satisfy the @code{display}
6156 group parameter predicate
6157 (@code{gnus-summary-limit-to-display-predicate}). See @pxref{Group
6158 Parameters} for more on this predicate.
6162 @kindex M S (Summary)
6163 @kindex / E (Summary)
6164 @findex gnus-summary-limit-include-expunged
6165 Include all expunged articles in the limit
6166 (@code{gnus-summary-limit-include-expunged}).
6169 @kindex / D (Summary)
6170 @findex gnus-summary-limit-include-dormant
6171 Include all dormant articles in the limit
6172 (@code{gnus-summary-limit-include-dormant}).
6175 @kindex / * (Summary)
6176 @findex gnus-summary-limit-include-cached
6177 Include all cached articles in the limit
6178 (@code{gnus-summary-limit-include-cached}).
6181 @kindex / d (Summary)
6182 @findex gnus-summary-limit-exclude-dormant
6183 Exclude all dormant articles from the limit
6184 (@code{gnus-summary-limit-exclude-dormant}).
6187 @kindex / M (Summary)
6188 @findex gnus-summary-limit-exclude-marks
6189 Exclude all marked articles (@code{gnus-summary-limit-exclude-marks}).
6192 @kindex / T (Summary)
6193 @findex gnus-summary-limit-include-thread
6194 Include all the articles in the current thread in the limit.
6197 @kindex / c (Summary)
6198 @findex gnus-summary-limit-exclude-childless-dormant
6199 Exclude all dormant articles that have no children from the limit
6200 (@code{gnus-summary-limit-exclude-childless-dormant}).
6203 @kindex / C (Summary)
6204 @findex gnus-summary-limit-mark-excluded-as-read
6205 Mark all excluded unread articles as read
6206 (@code{gnus-summary-limit-mark-excluded-as-read}). If given a prefix,
6207 also mark excluded ticked and dormant articles as read.
6210 @kindex / N (Summary)
6211 @findex gnus-summary-insert-new-articles
6212 Insert all new articles in the summary buffer. It scans for new emails
6213 if @var{back-end}@code{-get-new-mail} is non-@code{nil}.
6216 @kindex / o (Summary)
6217 @findex gnus-summary-insert-old-articles
6218 Insert all old articles in the summary buffer. If given a numbered
6219 prefix, fetch this number of articles.
6227 @cindex article threading
6229 Gnus threads articles by default. @dfn{To thread} is to put responses
6230 to articles directly after the articles they respond to---in a
6231 hierarchical fashion.
6233 Threading is done by looking at the @code{References} headers of the
6234 articles. In a perfect world, this would be enough to build pretty
6235 trees, but unfortunately, the @code{References} header is often broken
6236 or simply missing. Weird news propagation exacerbates the problem,
6237 so one has to employ other heuristics to get pleasing results. A
6238 plethora of approaches exists, as detailed in horrible detail in
6239 @pxref{Customizing Threading}.
6241 First, a quick overview of the concepts:
6245 The top-most article in a thread; the first article in the thread.
6248 A tree-like article structure.
6251 A small(er) section of this tree-like structure.
6254 Threads often lose their roots due to article expiry, or due to the root
6255 already having been read in a previous session, and not displayed in the
6256 summary buffer. We then typically have many sub-threads that really
6257 belong to one thread, but are without connecting roots. These are
6258 called loose threads.
6260 @item thread gathering
6261 An attempt to gather loose threads into bigger threads.
6263 @item sparse threads
6264 A thread where the missing articles have been ``guessed'' at, and are
6265 displayed as empty lines in the summary buffer.
6271 * Customizing Threading:: Variables you can change to affect the threading.
6272 * Thread Commands:: Thread based commands in the summary buffer.
6276 @node Customizing Threading
6277 @subsection Customizing Threading
6278 @cindex customizing threading
6281 * Loose Threads:: How Gnus gathers loose threads into bigger threads.
6282 * Filling In Threads:: Making the threads displayed look fuller.
6283 * More Threading:: Even more variables for fiddling with threads.
6284 * Low-Level Threading:: You thought it was over... but you were wrong!
6289 @subsubsection Loose Threads
6292 @cindex loose threads
6295 @item gnus-summary-make-false-root
6296 @vindex gnus-summary-make-false-root
6297 If non-@code{nil}, gnus will gather all loose subtrees into one big tree
6298 and create a dummy root at the top. (Wait a minute. Root at the top?
6299 Yup.) Loose subtrees occur when the real root has expired, or you've
6300 read or killed the root in a previous session.
6302 When there is no real root of a thread, gnus will have to fudge
6303 something. This variable says what fudging method gnus should use.
6304 There are four possible values:
6308 \gnusfigure{The Summary Buffer}{390}{
6309 \put(0,0){\epsfig{figure=ps/summary-adopt,width=7.5cm}}
6310 \put(445,0){\makebox(0,0)[br]{\epsfig{figure=ps/summary-empty,width=7.5cm}}}
6311 \put(0,400){\makebox(0,0)[tl]{\epsfig{figure=ps/summary-none,width=7.5cm}}}
6312 \put(445,400){\makebox(0,0)[tr]{\epsfig{figure=ps/summary-dummy,width=7.5cm}}}
6317 @cindex adopting articles
6322 Gnus will make the first of the orphaned articles the parent. This
6323 parent will adopt all the other articles. The adopted articles will be
6324 marked as such by pointy brackets (@samp{<>}) instead of the standard
6325 square brackets (@samp{[]}). This is the default method.
6328 @vindex gnus-summary-dummy-line-format
6329 @vindex gnus-summary-make-false-root-always
6330 Gnus will create a dummy summary line that will pretend to be the
6331 parent. This dummy line does not correspond to any real article, so
6332 selecting it will just select the first real article after the dummy
6333 article. @code{gnus-summary-dummy-line-format} is used to specify the
6334 format of the dummy roots. It accepts only one format spec: @samp{S},
6335 which is the subject of the article. @xref{Formatting Variables}.
6336 If you want all threads to have a dummy root, even the non-gathered
6337 ones, set @code{gnus-summary-make-false-root-always} to t.
6340 Gnus won't actually make any article the parent, but simply leave the
6341 subject field of all orphans except the first empty. (Actually, it will
6342 use @code{gnus-summary-same-subject} as the subject (@pxref{Summary
6346 Don't make any article parent at all. Just gather the threads and
6347 display them after one another.
6350 Don't gather loose threads.
6353 @item gnus-summary-gather-subject-limit
6354 @vindex gnus-summary-gather-subject-limit
6355 Loose threads are gathered by comparing subjects of articles. If this
6356 variable is @code{nil}, gnus requires an exact match between the
6357 subjects of the loose threads before gathering them into one big
6358 super-thread. This might be too strict a requirement, what with the
6359 presence of stupid newsreaders that chop off long subject lines. If
6360 you think so, set this variable to, say, 20 to require that only the
6361 first 20 characters of the subjects have to match. If you set this
6362 variable to a really low number, you'll find that gnus will gather
6363 everything in sight into one thread, which isn't very helpful.
6365 @cindex fuzzy article gathering
6366 If you set this variable to the special value @code{fuzzy}, gnus will
6367 use a fuzzy string comparison algorithm on the subjects (@pxref{Fuzzy
6370 @item gnus-simplify-subject-fuzzy-regexp
6371 @vindex gnus-simplify-subject-fuzzy-regexp
6372 This can either be a regular expression or list of regular expressions
6373 that match strings that will be removed from subjects if fuzzy subject
6374 simplification is used.
6376 @item gnus-simplify-ignored-prefixes
6377 @vindex gnus-simplify-ignored-prefixes
6378 If you set @code{gnus-summary-gather-subject-limit} to something as low
6379 as 10, you might consider setting this variable to something sensible:
6381 @c Written by Michael Ernst <mernst@cs.rice.edu>
6383 (setq gnus-simplify-ignored-prefixes
6389 "wanted" "followup" "summary\\( of\\)?"
6390 "help" "query" "problem" "question"
6391 "answer" "reference" "announce"
6392 "How can I" "How to" "Comparison of"
6397 (mapconcat 'identity
6398 '("for" "for reference" "with" "about")
6400 "\\)?\\]?:?[ \t]*"))
6403 All words that match this regexp will be removed before comparing two
6406 @item gnus-simplify-subject-functions
6407 @vindex gnus-simplify-subject-functions
6408 If non-@code{nil}, this variable overrides
6409 @code{gnus-summary-gather-subject-limit}. This variable should be a
6410 list of functions to apply to the @code{Subject} string iteratively to
6411 arrive at the simplified version of the string.
6413 Useful functions to put in this list include:
6416 @item gnus-simplify-subject-re
6417 @findex gnus-simplify-subject-re
6418 Strip the leading @samp{Re:}.
6420 @item gnus-simplify-subject-fuzzy
6421 @findex gnus-simplify-subject-fuzzy
6424 @item gnus-simplify-whitespace
6425 @findex gnus-simplify-whitespace
6426 Remove excessive whitespace.
6428 @item gnus-simplify-all-whitespace
6429 @findex gnus-simplify-all-whitespace
6430 Remove all whitespace.
6433 You may also write your own functions, of course.
6436 @item gnus-summary-gather-exclude-subject
6437 @vindex gnus-summary-gather-exclude-subject
6438 Since loose thread gathering is done on subjects only, that might lead
6439 to many false hits, especially with certain common subjects like
6440 @samp{} and @samp{(none)}. To make the situation slightly better,
6441 you can use the regexp @code{gnus-summary-gather-exclude-subject} to say
6442 what subjects should be excluded from the gathering process.@*
6443 The default is @samp{^ *$\\|^(none)$}.
6445 @item gnus-summary-thread-gathering-function
6446 @vindex gnus-summary-thread-gathering-function
6447 Gnus gathers threads by looking at @code{Subject} headers. This means
6448 that totally unrelated articles may end up in the same ``thread'', which
6449 is confusing. An alternate approach is to look at all the
6450 @code{Message-ID}s in all the @code{References} headers to find matches.
6451 This will ensure that no gathered threads ever include unrelated
6452 articles, but it also means that people who have posted with broken
6453 newsreaders won't be gathered properly. The choice is yours---plague or
6457 @item gnus-gather-threads-by-subject
6458 @findex gnus-gather-threads-by-subject
6459 This function is the default gathering function and looks at
6460 @code{Subject}s exclusively.
6462 @item gnus-gather-threads-by-references
6463 @findex gnus-gather-threads-by-references
6464 This function looks at @code{References} headers exclusively.
6467 If you want to test gathering by @code{References}, you could say
6471 (setq gnus-summary-thread-gathering-function
6472 'gnus-gather-threads-by-references)
6478 @node Filling In Threads
6479 @subsubsection Filling In Threads
6482 @item gnus-fetch-old-headers
6483 @vindex gnus-fetch-old-headers
6484 If non-@code{nil}, gnus will attempt to build old threads by fetching
6485 more old headers---headers to articles marked as read. If you
6486 would like to display as few summary lines as possible, but still
6487 connect as many loose threads as possible, you should set this variable
6488 to @code{some} or a number. If you set it to a number, no more than
6489 that number of extra old headers will be fetched. In either case,
6490 fetching old headers only works if the back end you are using carries
6491 overview files---this would normally be @code{nntp}, @code{nnspool},
6492 @code{nnml}, and @code{nnmaildir}. Also remember that if the root of
6493 the thread has been expired by the server, there's not much Gnus can do
6496 This variable can also be set to @code{invisible}. This won't have any
6497 visible effects, but is useful if you use the @kbd{A T} command a lot
6498 (@pxref{Finding the Parent}).
6500 @item gnus-build-sparse-threads
6501 @vindex gnus-build-sparse-threads
6502 Fetching old headers can be slow. A low-rent similar effect can be
6503 gotten by setting this variable to @code{some}. Gnus will then look at
6504 the complete @code{References} headers of all articles and try to string
6505 together articles that belong in the same thread. This will leave
6506 @dfn{gaps} in the threading display where gnus guesses that an article
6507 is missing from the thread. (These gaps appear like normal summary
6508 lines. If you select a gap, gnus will try to fetch the article in
6509 question.) If this variable is @code{t}, gnus will display all these
6510 ``gaps'' without regard for whether they are useful for completing the
6511 thread or not. Finally, if this variable is @code{more}, gnus won't cut
6512 off sparse leaf nodes that don't lead anywhere. This variable is
6513 @code{nil} by default.
6515 @item gnus-read-all-available-headers
6516 @vindex gnus-read-all-available-headers
6517 This is a rather obscure variable that few will find useful. It's
6518 intended for those non-news newsgroups where the back end has to fetch
6519 quite a lot to present the summary buffer, and where it's impossible to
6520 go back to parents of articles. This is mostly the case in the
6521 web-based groups, like the @code{nnultimate} groups.
6523 If you don't use those, then it's safe to leave this as the default
6524 @code{nil}. If you want to use this variable, it should be a regexp
6525 that matches the group name, or @code{t} for all groups.
6530 @node More Threading
6531 @subsubsection More Threading
6534 @item gnus-show-threads
6535 @vindex gnus-show-threads
6536 If this variable is @code{nil}, no threading will be done, and all of
6537 the rest of the variables here will have no effect. Turning threading
6538 off will speed group selection up a bit, but it is sure to make reading
6539 slower and more awkward.
6541 @item gnus-thread-hide-subtree
6542 @vindex gnus-thread-hide-subtree
6543 If non-@code{nil}, all threads will be hidden when the summary buffer is
6546 This can also be a predicate specifier (@pxref{Predicate Specifiers}).
6547 Available predicates are @code{gnus-article-unread-p} and
6548 @code{gnus-article-unseen-p}).
6553 (setq gnus-thread-hide-subtree
6554 '(or gnus-article-unread-p
6555 gnus-article-unseen-p))
6558 (It's a pretty nonsensical example, since all unseen articles are also
6559 unread, but you get my drift.)
6562 @item gnus-thread-expunge-below
6563 @vindex gnus-thread-expunge-below
6564 All threads that have a total score (as defined by
6565 @code{gnus-thread-score-function}) less than this number will be
6566 expunged. This variable is @code{nil} by default, which means that no
6567 threads are expunged.
6569 @item gnus-thread-hide-killed
6570 @vindex gnus-thread-hide-killed
6571 if you kill a thread and this variable is non-@code{nil}, the subtree
6574 @item gnus-thread-ignore-subject
6575 @vindex gnus-thread-ignore-subject
6576 Sometimes somebody changes the subject in the middle of a thread. If
6577 this variable is non-@code{nil}, which is the default, the subject
6578 change is ignored. If it is @code{nil}, a change in the subject will
6579 result in a new thread.
6581 @item gnus-thread-indent-level
6582 @vindex gnus-thread-indent-level
6583 This is a number that says how much each sub-thread should be indented.
6586 @item gnus-sort-gathered-threads-function
6587 @vindex gnus-sort-gathered-threads-function
6588 Sometimes, particularly with mailing lists, the order in which mails
6589 arrive locally is not necessarily the same as the order in which they
6590 arrived on the mailing list. Consequently, when sorting sub-threads
6591 using the default @code{gnus-thread-sort-by-number}, responses can end
6592 up appearing before the article to which they are responding to.
6593 Setting this variable to an alternate value
6594 (e.g. @code{gnus-thread-sort-by-date}), in a group's parameters or in an
6595 appropriate hook (e.g. @code{gnus-summary-generate-hook}) can produce a
6596 more logical sub-thread ordering in such instances.
6601 @node Low-Level Threading
6602 @subsubsection Low-Level Threading
6606 @item gnus-parse-headers-hook
6607 @vindex gnus-parse-headers-hook
6608 Hook run before parsing any headers. The default value is
6609 @code{(gnus-set-summary-default-charset)}, which sets up local value of
6610 @code{default-mime-charset} in summary buffer based on variable
6611 @code{gnus-newsgroup-default-charset-alist}.
6613 @item gnus-alter-header-function
6614 @vindex gnus-alter-header-function
6615 If non-@code{nil}, this function will be called to allow alteration of
6616 article header structures. The function is called with one parameter,
6617 the article header vector, which it may alter in any way. For instance,
6618 if you have a mail-to-news gateway which alters the @code{Message-ID}s
6619 in systematic ways (by adding prefixes and such), you can use this
6620 variable to un-scramble the @code{Message-ID}s so that they are more
6621 meaningful. Here's one example:
6624 (setq gnus-alter-header-function 'my-alter-message-id)
6626 (defun my-alter-message-id (header)
6627 (let ((id (mail-header-id header)))
6629 "\\(<[^<>@@]*\\)\\.?cygnus\\..*@@\\([^<>@@]*>\\)" id)
6631 (concat (match-string 1 id) "@@" (match-string 2 id))
6638 @node Thread Commands
6639 @subsection Thread Commands
6640 @cindex thread commands
6646 @kindex T k (Summary)
6647 @kindex C-M-k (Summary)
6648 @findex gnus-summary-kill-thread
6649 Mark all articles in the current (sub-)thread as read
6650 (@code{gnus-summary-kill-thread}). If the prefix argument is positive,
6651 remove all marks instead. If the prefix argument is negative, tick
6656 @kindex T l (Summary)
6657 @kindex C-M-l (Summary)
6658 @findex gnus-summary-lower-thread
6659 Lower the score of the current (sub-)thread
6660 (@code{gnus-summary-lower-thread}).
6663 @kindex T i (Summary)
6664 @findex gnus-summary-raise-thread
6665 Increase the score of the current (sub-)thread
6666 (@code{gnus-summary-raise-thread}).
6669 @kindex T # (Summary)
6670 @findex gnus-uu-mark-thread
6671 Set the process mark on the current (sub-)thread
6672 (@code{gnus-uu-mark-thread}).
6675 @kindex T M-# (Summary)
6676 @findex gnus-uu-unmark-thread
6677 Remove the process mark from the current (sub-)thread
6678 (@code{gnus-uu-unmark-thread}).
6681 @kindex T T (Summary)
6682 @findex gnus-summary-toggle-threads
6683 Toggle threading (@code{gnus-summary-toggle-threads}).
6686 @kindex T s (Summary)
6687 @findex gnus-summary-show-thread
6688 Expose the (sub-)thread hidden under the current article, if any
6689 (@code{gnus-summary-show-thread}).
6692 @kindex T h (Summary)
6693 @findex gnus-summary-hide-thread
6694 Hide the current (sub-)thread (@code{gnus-summary-hide-thread}).
6697 @kindex T S (Summary)
6698 @findex gnus-summary-show-all-threads
6699 Expose all hidden threads (@code{gnus-summary-show-all-threads}).
6702 @kindex T H (Summary)
6703 @findex gnus-summary-hide-all-threads
6704 Hide all threads (@code{gnus-summary-hide-all-threads}).
6707 @kindex T t (Summary)
6708 @findex gnus-summary-rethread-current
6709 Re-thread the current article's thread
6710 (@code{gnus-summary-rethread-current}). This works even when the
6711 summary buffer is otherwise unthreaded.
6714 @kindex T ^ (Summary)
6715 @findex gnus-summary-reparent-thread
6716 Make the current article the child of the marked (or previous) article
6717 (@code{gnus-summary-reparent-thread}).
6721 The following commands are thread movement commands. They all
6722 understand the numeric prefix.
6727 @kindex T n (Summary)
6729 @kindex C-M-n (Summary)
6731 @kindex M-down (Summary)
6732 @findex gnus-summary-next-thread
6733 Go to the next thread (@code{gnus-summary-next-thread}).
6736 @kindex T p (Summary)
6738 @kindex C-M-p (Summary)
6740 @kindex M-up (Summary)
6741 @findex gnus-summary-prev-thread
6742 Go to the previous thread (@code{gnus-summary-prev-thread}).
6745 @kindex T d (Summary)
6746 @findex gnus-summary-down-thread
6747 Descend the thread (@code{gnus-summary-down-thread}).
6750 @kindex T u (Summary)
6751 @findex gnus-summary-up-thread
6752 Ascend the thread (@code{gnus-summary-up-thread}).
6755 @kindex T o (Summary)
6756 @findex gnus-summary-top-thread
6757 Go to the top of the thread (@code{gnus-summary-top-thread}).
6760 @vindex gnus-thread-operation-ignore-subject
6761 If you ignore subject while threading, you'll naturally end up with
6762 threads that have several different subjects in them. If you then issue
6763 a command like `T k' (@code{gnus-summary-kill-thread}) you might not
6764 wish to kill the entire thread, but just those parts of the thread that
6765 have the same subject as the current article. If you like this idea,
6766 you can fiddle with @code{gnus-thread-operation-ignore-subject}. If it
6767 is non-@code{nil} (which it is by default), subjects will be ignored
6768 when doing thread commands. If this variable is @code{nil}, articles in
6769 the same thread with different subjects will not be included in the
6770 operation in question. If this variable is @code{fuzzy}, only articles
6771 that have subjects fuzzily equal will be included (@pxref{Fuzzy
6775 @node Sorting the Summary Buffer
6776 @section Sorting the Summary Buffer
6778 @findex gnus-thread-sort-by-total-score
6779 @findex gnus-thread-sort-by-date
6780 @findex gnus-thread-sort-by-score
6781 @findex gnus-thread-sort-by-subject
6782 @findex gnus-thread-sort-by-author
6783 @findex gnus-thread-sort-by-number
6784 @findex gnus-thread-sort-by-random
6785 @vindex gnus-thread-sort-functions
6786 @findex gnus-thread-sort-by-most-recent-thread
6787 If you are using a threaded summary display, you can sort the threads by
6788 setting @code{gnus-thread-sort-functions}, which can be either a single
6789 function, a list of functions, or a list containing functions and
6790 @code{(not some-function)} elements.
6792 By default, sorting is done on article numbers. Ready-made sorting
6793 predicate functions include @code{gnus-thread-sort-by-number},
6794 @code{gnus-thread-sort-by-author}, @code{gnus-thread-sort-by-subject},
6795 @code{gnus-thread-sort-by-date}, @code{gnus-thread-sort-by-score},
6796 @code{gnus-thread-sort-by-most-recent-number},
6797 @code{gnus-thread-sort-by-most-recent-date},
6798 @code{gnus-thread-sort-by-random} and
6799 @code{gnus-thread-sort-by-total-score}.
6801 Each function takes two threads and returns non-@code{nil} if the first
6802 thread should be sorted before the other. Note that sorting really is
6803 normally done by looking only at the roots of each thread.
6805 If you use more than one function, the primary sort key should be the
6806 last function in the list. You should probably always include
6807 @code{gnus-thread-sort-by-number} in the list of sorting
6808 functions---preferably first. This will ensure that threads that are
6809 equal with respect to the other sort criteria will be displayed in
6810 ascending article order.
6812 If you would like to sort by reverse score, then by subject, and finally
6813 by number, you could do something like:
6816 (setq gnus-thread-sort-functions
6817 '(gnus-thread-sort-by-number
6818 gnus-thread-sort-by-subject
6819 (not gnus-thread-sort-by-total-score)))
6822 The threads that have highest score will be displayed first in the
6823 summary buffer. When threads have the same score, they will be sorted
6824 alphabetically. The threads that have the same score and the same
6825 subject will be sorted by number, which is (normally) the sequence in
6826 which the articles arrived.
6828 If you want to sort by score and then reverse arrival order, you could
6832 (setq gnus-thread-sort-functions
6834 (not (gnus-thread-sort-by-number t1 t2)))
6835 gnus-thread-sort-by-score))
6838 @vindex gnus-thread-score-function
6839 The function in the @code{gnus-thread-score-function} variable (default
6840 @code{+}) is used for calculating the total score of a thread. Useful
6841 functions might be @code{max}, @code{min}, or squared means, or whatever
6844 @findex gnus-article-sort-functions
6845 @findex gnus-article-sort-by-date
6846 @findex gnus-article-sort-by-score
6847 @findex gnus-article-sort-by-subject
6848 @findex gnus-article-sort-by-author
6849 @findex gnus-article-sort-by-random
6850 @findex gnus-article-sort-by-number
6851 If you are using an unthreaded display for some strange reason or
6852 other, you have to fiddle with the @code{gnus-article-sort-functions}
6853 variable. It is very similar to the
6854 @code{gnus-thread-sort-functions}, except that it uses slightly
6855 different functions for article comparison. Available sorting
6856 predicate functions are @code{gnus-article-sort-by-number},
6857 @code{gnus-article-sort-by-author},
6858 @code{gnus-article-sort-by-subject}, @code{gnus-article-sort-by-date},
6859 @code{gnus-article-sort-by-random}, and
6860 @code{gnus-article-sort-by-score}.
6862 If you want to sort an unthreaded summary display by subject, you could
6866 (setq gnus-article-sort-functions
6867 '(gnus-article-sort-by-number
6868 gnus-article-sort-by-subject))
6873 @node Asynchronous Fetching
6874 @section Asynchronous Article Fetching
6875 @cindex asynchronous article fetching
6876 @cindex article pre-fetch
6879 If you read your news from an @sc{nntp} server that's far away, the
6880 network latencies may make reading articles a chore. You have to wait
6881 for a while after pressing @kbd{n} to go to the next article before the
6882 article appears. Why can't gnus just go ahead and fetch the article
6883 while you are reading the previous one? Why not, indeed.
6885 First, some caveats. There are some pitfalls to using asynchronous
6886 article fetching, especially the way gnus does it.
6888 Let's say you are reading article 1, which is short, and article 2 is
6889 quite long, and you are not interested in reading that. Gnus does not
6890 know this, so it goes ahead and fetches article 2. You decide to read
6891 article 3, but since gnus is in the process of fetching article 2, the
6892 connection is blocked.
6894 To avoid these situations, gnus will open two (count 'em two)
6895 connections to the server. Some people may think this isn't a very nice
6896 thing to do, but I don't see any real alternatives. Setting up that
6897 extra connection takes some time, so gnus startup will be slower.
6899 Gnus will fetch more articles than you will read. This will mean that
6900 the link between your machine and the @sc{nntp} server will become more
6901 loaded than if you didn't use article pre-fetch. The server itself will
6902 also become more loaded---both with the extra article requests, and the
6905 Ok, so now you know that you shouldn't really use this thing... unless
6908 @vindex gnus-asynchronous
6909 Here's how: Set @code{gnus-asynchronous} to @code{t}. The rest should
6910 happen automatically.
6912 @vindex gnus-use-article-prefetch
6913 You can control how many articles are to be pre-fetched by setting
6914 @code{gnus-use-article-prefetch}. This is 30 by default, which means
6915 that when you read an article in the group, the back end will pre-fetch
6916 the next 30 articles. If this variable is @code{t}, the back end will
6917 pre-fetch all the articles it can without bound. If it is
6918 @code{nil}, no pre-fetching will be done.
6920 @vindex gnus-async-prefetch-article-p
6921 @findex gnus-async-read-p
6922 There are probably some articles that you don't want to pre-fetch---read
6923 articles, for instance. The @code{gnus-async-prefetch-article-p} variable controls whether an article is to be pre-fetched. This function should
6924 return non-@code{nil} when the article in question is to be
6925 pre-fetched. The default is @code{gnus-async-read-p}, which returns
6926 @code{nil} on read articles. The function is called with an article
6927 data structure as the only parameter.
6929 If, for instance, you wish to pre-fetch only unread articles shorter than 100 lines, you could say something like:
6932 (defun my-async-short-unread-p (data)
6933 "Return non-nil for short, unread articles."
6934 (and (gnus-data-unread-p data)
6935 (< (mail-header-lines (gnus-data-header data))
6938 (setq gnus-async-prefetch-article-p 'my-async-short-unread-p)
6941 These functions will be called many, many times, so they should
6942 preferably be short and sweet to avoid slowing down gnus too much.
6943 It's probably a good idea to byte-compile things like this.
6945 @vindex gnus-prefetched-article-deletion-strategy
6946 Articles have to be removed from the asynch buffer sooner or later. The
6947 @code{gnus-prefetched-article-deletion-strategy} says when to remove
6948 articles. This is a list that may contain the following elements:
6952 Remove articles when they are read.
6955 Remove articles when exiting the group.
6958 The default value is @code{(read exit)}.
6960 @c @vindex gnus-use-header-prefetch
6961 @c If @code{gnus-use-header-prefetch} is non-@code{nil}, prefetch articles
6962 @c from the next group.
6965 @node Article Caching
6966 @section Article Caching
6967 @cindex article caching
6970 If you have an @emph{extremely} slow @sc{nntp} connection, you may
6971 consider turning article caching on. Each article will then be stored
6972 locally under your home directory. As you may surmise, this could
6973 potentially use @emph{huge} amounts of disk space, as well as eat up all
6974 your inodes so fast it will make your head swim. In vodka.
6976 Used carefully, though, it could be just an easier way to save articles.
6978 @vindex gnus-use-long-file-name
6979 @vindex gnus-cache-directory
6980 @vindex gnus-use-cache
6981 To turn caching on, set @code{gnus-use-cache} to @code{t}. By default,
6982 all articles ticked or marked as dormant will then be copied
6983 over to your local cache (@code{gnus-cache-directory}). Whether this
6984 cache is flat or hierarchical is controlled by the
6985 @code{gnus-use-long-file-name} variable, as usual.
6987 When re-selecting a ticked or dormant article, it will be fetched from the
6988 cache instead of from the server. As articles in your cache will never
6989 expire, this might serve as a method of saving articles while still
6990 keeping them where they belong. Just mark all articles you want to save
6991 as dormant, and don't worry.
6993 When an article is marked as read, is it removed from the cache.
6995 @vindex gnus-cache-remove-articles
6996 @vindex gnus-cache-enter-articles
6997 The entering/removal of articles from the cache is controlled by the
6998 @code{gnus-cache-enter-articles} and @code{gnus-cache-remove-articles}
6999 variables. Both are lists of symbols. The first is @code{(ticked
7000 dormant)} by default, meaning that ticked and dormant articles will be
7001 put in the cache. The latter is @code{(read)} by default, meaning that
7002 articles marked as read are removed from the cache. Possibly
7003 symbols in these two lists are @code{ticked}, @code{dormant},
7004 @code{unread} and @code{read}.
7006 @findex gnus-jog-cache
7007 So where does the massive article-fetching and storing come into the
7008 picture? The @code{gnus-jog-cache} command will go through all
7009 subscribed newsgroups, request all unread articles, score them, and
7010 store them in the cache. You should only ever, ever ever ever, use this
7011 command if 1) your connection to the @sc{nntp} server is really, really,
7012 really slow and 2) you have a really, really, really huge disk.
7013 Seriously. One way to cut down on the number of articles downloaded is
7014 to score unwanted articles down and have them marked as read. They will
7015 not then be downloaded by this command.
7017 @vindex gnus-uncacheable-groups
7018 @vindex gnus-cacheable-groups
7019 It is likely that you do not want caching on all groups. For instance,
7020 if your @code{nnml} mail is located under your home directory, it makes no
7021 sense to cache it somewhere else under your home directory. Unless you
7022 feel that it's neat to use twice as much space.
7024 To limit the caching, you could set @code{gnus-cacheable-groups} to a
7025 regexp of groups to cache, @samp{^nntp} for instance, or set the
7026 @code{gnus-uncacheable-groups} regexp to @samp{^nnml}, for instance.
7027 Both variables are @code{nil} by default. If a group matches both
7028 variables, the group is not cached.
7030 @findex gnus-cache-generate-nov-databases
7031 @findex gnus-cache-generate-active
7032 @vindex gnus-cache-active-file
7033 The cache stores information on what articles it contains in its active
7034 file (@code{gnus-cache-active-file}). If this file (or any other parts
7035 of the cache) becomes all messed up for some reason or other, gnus
7036 offers two functions that will try to set things right. @kbd{M-x
7037 gnus-cache-generate-nov-databases} will (re)build all the @sc{nov}
7038 files, and @kbd{gnus-cache-generate-active} will (re)generate the active
7041 @findex gnus-cache-move-cache
7042 @code{gnus-cache-move-cache} will move your whole
7043 @code{gnus-cache-directory} to some other location. You get asked to
7044 where, isn't that cool?
7046 @node Persistent Articles
7047 @section Persistent Articles
7048 @cindex persistent articles
7050 Closely related to article caching, we have @dfn{persistent articles}.
7051 In fact, it's just a different way of looking at caching, and much more
7052 useful in my opinion.
7054 Say you're reading a newsgroup, and you happen on to some valuable gem
7055 that you want to keep and treasure forever. You'd normally just save it
7056 (using one of the many saving commands) in some file. The problem with
7057 that is that it's just, well, yucky. Ideally you'd prefer just having
7058 the article remain in the group where you found it forever; untouched by
7059 the expiry going on at the news server.
7061 This is what a @dfn{persistent article} is---an article that just won't
7062 be deleted. It's implemented using the normal cache functions, but
7063 you use two explicit commands for managing persistent articles:
7069 @findex gnus-cache-enter-article
7070 Make the current article persistent (@code{gnus-cache-enter-article}).
7073 @kindex M-* (Summary)
7074 @findex gnus-cache-remove-article
7075 Remove the current article from the persistent articles
7076 (@code{gnus-cache-remove-article}). This will normally delete the
7080 Both these commands understand the process/prefix convention.
7082 To avoid having all ticked articles (and stuff) entered into the cache,
7083 you should set @code{gnus-use-cache} to @code{passive} if you're just
7084 interested in persistent articles:
7087 (setq gnus-use-cache 'passive)
7091 @node Article Backlog
7092 @section Article Backlog
7094 @cindex article backlog
7096 If you have a slow connection, but the idea of using caching seems
7097 unappealing to you (and it is, really), you can help the situation some
7098 by switching on the @dfn{backlog}. This is where gnus will buffer
7099 already read articles so that it doesn't have to re-fetch articles
7100 you've already read. This only helps if you are in the habit of
7101 re-selecting articles you've recently read, of course. If you never do
7102 that, turning the backlog on will slow gnus down a little bit, and
7103 increase memory usage some.
7105 @vindex gnus-keep-backlog
7106 If you set @code{gnus-keep-backlog} to a number @var{n}, gnus will store
7107 at most @var{n} old articles in a buffer for later re-fetching. If this
7108 variable is non-@code{nil} and is not a number, gnus will store
7109 @emph{all} read articles, which means that your Emacs will grow without
7110 bound before exploding and taking your machine down with you. I put
7111 that in there just to keep y'all on your toes.
7113 This variable is @code{nil} by default.
7116 @node Saving Articles
7117 @section Saving Articles
7118 @cindex saving articles
7120 Gnus can save articles in a number of ways. Below is the documentation
7121 for saving articles in a fairly straight-forward fashion (i.e., little
7122 processing of the article is done before it is saved). For a different
7123 approach (uudecoding, unsharing) you should use @code{gnus-uu}
7124 (@pxref{Decoding Articles}).
7126 For the commands listed here, the target is a file. If you want to
7127 save to a group, see the @kbd{B c} (@code{gnus-summary-copy-article})
7128 command (@pxref{Mail Group Commands}).
7130 @vindex gnus-save-all-headers
7131 If @code{gnus-save-all-headers} is non-@code{nil}, gnus will not delete
7132 unwanted headers before saving the article.
7134 @vindex gnus-saved-headers
7135 If the preceding variable is @code{nil}, all headers that match the
7136 @code{gnus-saved-headers} regexp will be kept, while the rest will be
7137 deleted before saving.
7143 @kindex O o (Summary)
7145 @findex gnus-summary-save-article
7146 @c @icon{gnus-summary-save-article}
7147 Save the current article using the default article saver
7148 (@code{gnus-summary-save-article}).
7151 @kindex O m (Summary)
7152 @findex gnus-summary-save-article-mail
7153 Save the current article in mail format
7154 (@code{gnus-summary-save-article-mail}).
7157 @kindex O r (Summary)
7158 @findex gnus-summary-save-article-rmail
7159 Save the current article in rmail format
7160 (@code{gnus-summary-save-article-rmail}).
7163 @kindex O f (Summary)
7164 @findex gnus-summary-save-article-file
7165 @c @icon{gnus-summary-save-article-file}
7166 Save the current article in plain file format
7167 (@code{gnus-summary-save-article-file}).
7170 @kindex O F (Summary)
7171 @findex gnus-summary-write-article-file
7172 Write the current article in plain file format, overwriting any previous
7173 file contents (@code{gnus-summary-write-article-file}).
7176 @kindex O b (Summary)
7177 @findex gnus-summary-save-article-body-file
7178 Save the current article body in plain file format
7179 (@code{gnus-summary-save-article-body-file}).
7182 @kindex O h (Summary)
7183 @findex gnus-summary-save-article-folder
7184 Save the current article in mh folder format
7185 (@code{gnus-summary-save-article-folder}).
7188 @kindex O v (Summary)
7189 @findex gnus-summary-save-article-vm
7190 Save the current article in a VM folder
7191 (@code{gnus-summary-save-article-vm}).
7195 @kindex O p (Summary)
7197 @findex gnus-summary-pipe-output
7198 Save the current article in a pipe. Uhm, like, what I mean is---Pipe
7199 the current article to a process (@code{gnus-summary-pipe-output}).
7200 If given a symbolic prefix (@pxref{Symbolic Prefixes}), include the
7201 complete headers in the piped output.
7204 @kindex O P (Summary)
7205 @findex gnus-summary-muttprint
7206 @vindex gnus-summary-muttprint-program
7207 Save the current article into muttprint. That is, print it using the
7208 external program Muttprint (see
7209 @uref{http://muttprint.sourceforge.net/}). The program name and
7210 options to use is controlled by the variable
7211 @code{gnus-summary-muttprint-program}. (@code{gnus-summary-muttprint}).
7215 @vindex gnus-prompt-before-saving
7216 All these commands use the process/prefix convention
7217 (@pxref{Process/Prefix}). If you save bunches of articles using these
7218 functions, you might get tired of being prompted for files to save each
7219 and every article in. The prompting action is controlled by
7220 the @code{gnus-prompt-before-saving} variable, which is @code{always} by
7221 default, giving you that excessive prompting action you know and
7222 loathe. If you set this variable to @code{t} instead, you'll be prompted
7223 just once for each series of articles you save. If you like to really
7224 have Gnus do all your thinking for you, you can even set this variable
7225 to @code{nil}, which means that you will never be prompted for files to
7226 save articles in. Gnus will simply save all the articles in the default
7230 @vindex gnus-default-article-saver
7231 You can customize the @code{gnus-default-article-saver} variable to make
7232 gnus do what you want it to. You can use any of the six ready-made
7233 functions below, or you can create your own.
7237 @item gnus-summary-save-in-rmail
7238 @findex gnus-summary-save-in-rmail
7239 @vindex gnus-rmail-save-name
7240 @findex gnus-plain-save-name
7241 This is the default format, @dfn{babyl}. Uses the function in the
7242 @code{gnus-rmail-save-name} variable to get a file name to save the
7243 article in. The default is @code{gnus-plain-save-name}.
7245 @item gnus-summary-save-in-mail
7246 @findex gnus-summary-save-in-mail
7247 @vindex gnus-mail-save-name
7248 Save in a Unix mail (mbox) file. Uses the function in the
7249 @code{gnus-mail-save-name} variable to get a file name to save the
7250 article in. The default is @code{gnus-plain-save-name}.
7252 @item gnus-summary-save-in-file
7253 @findex gnus-summary-save-in-file
7254 @vindex gnus-file-save-name
7255 @findex gnus-numeric-save-name
7256 Append the article straight to an ordinary file. Uses the function in
7257 the @code{gnus-file-save-name} variable to get a file name to save the
7258 article in. The default is @code{gnus-numeric-save-name}.
7260 @item gnus-summary-write-to-file
7261 @findex gnus-summary-write-to-file
7262 Write the article straight to an ordinary file. The file is
7263 overwritten if it exists. Uses the function in the
7264 @code{gnus-file-save-name} variable to get a file name to save the
7265 article in. The default is @code{gnus-numeric-save-name}.
7267 @item gnus-summary-save-body-in-file
7268 @findex gnus-summary-save-body-in-file
7269 Append the article body to an ordinary file. Uses the function in the
7270 @code{gnus-file-save-name} variable to get a file name to save the
7271 article in. The default is @code{gnus-numeric-save-name}.
7273 @item gnus-summary-save-in-folder
7274 @findex gnus-summary-save-in-folder
7275 @findex gnus-folder-save-name
7276 @findex gnus-Folder-save-name
7277 @vindex gnus-folder-save-name
7280 Save the article to an MH folder using @code{rcvstore} from the MH
7281 library. Uses the function in the @code{gnus-folder-save-name} variable
7282 to get a file name to save the article in. The default is
7283 @code{gnus-folder-save-name}, but you can also use
7284 @code{gnus-Folder-save-name}, which creates capitalized names.
7286 @item gnus-summary-save-in-vm
7287 @findex gnus-summary-save-in-vm
7288 Save the article in a VM folder. You have to have the VM mail
7289 reader to use this setting.
7292 @vindex gnus-article-save-directory
7293 All of these functions, except for the last one, will save the article
7294 in the @code{gnus-article-save-directory}, which is initialized from the
7295 @code{SAVEDIR} environment variable. This is @file{~/News/} by
7298 As you can see above, the functions use different functions to find a
7299 suitable name of a file to save the article in. Below is a list of
7300 available functions that generate names:
7304 @item gnus-Numeric-save-name
7305 @findex gnus-Numeric-save-name
7306 File names like @file{~/News/Alt.andrea-dworkin/45}.
7308 @item gnus-numeric-save-name
7309 @findex gnus-numeric-save-name
7310 File names like @file{~/News/alt.andrea-dworkin/45}.
7312 @item gnus-Plain-save-name
7313 @findex gnus-Plain-save-name
7314 File names like @file{~/News/Alt.andrea-dworkin}.
7316 @item gnus-plain-save-name
7317 @findex gnus-plain-save-name
7318 File names like @file{~/News/alt.andrea-dworkin}.
7320 @item gnus-sender-save-name
7321 @findex gnus-sender-save-name
7322 File names like @file{~/News/larsi}.
7325 @vindex gnus-split-methods
7326 You can have gnus suggest where to save articles by plonking a regexp into
7327 the @code{gnus-split-methods} alist. For instance, if you would like to
7328 save articles related to gnus in the file @file{gnus-stuff}, and articles
7329 related to VM in @code{vm-stuff}, you could set this variable to something
7333 (("^Subject:.*gnus\\|^Newsgroups:.*gnus" "gnus-stuff")
7334 ("^Subject:.*vm\\|^Xref:.*vm" "vm-stuff")
7335 (my-choosing-function "../other-dir/my-stuff")
7336 ((equal gnus-newsgroup-name "mail.misc") "mail-stuff"))
7339 We see that this is a list where each element is a list that has two
7340 elements---the @dfn{match} and the @dfn{file}. The match can either be
7341 a string (in which case it is used as a regexp to match on the article
7342 head); it can be a symbol (which will be called as a function with the
7343 group name as a parameter); or it can be a list (which will be
7344 @code{eval}ed). If any of these actions have a non-@code{nil} result,
7345 the @dfn{file} will be used as a default prompt. In addition, the
7346 result of the operation itself will be used if the function or form
7347 called returns a string or a list of strings.
7349 You basically end up with a list of file names that might be used when
7350 saving the current article. (All ``matches'' will be used.) You will
7351 then be prompted for what you really want to use as a name, with file
7352 name completion over the results from applying this variable.
7354 This variable is @code{((gnus-article-archive-name))} by default, which
7355 means that gnus will look at the articles it saves for an
7356 @code{Archive-name} line and use that as a suggestion for the file
7359 Here's an example function to clean up file names somewhat. If you have
7360 lots of mail groups called things like
7361 @samp{nnml:mail.whatever}, you may want to chop off the beginning of
7362 these group names before creating the file name to save to. The
7363 following will do just that:
7366 (defun my-save-name (group)
7367 (when (string-match "^nnml:mail." group)
7368 (substring group (match-end 0))))
7370 (setq gnus-split-methods
7371 '((gnus-article-archive-name)
7376 @vindex gnus-use-long-file-name
7377 Finally, you have the @code{gnus-use-long-file-name} variable. If it is
7378 @code{nil}, all the preceding functions will replace all periods
7379 (@samp{.}) in the group names with slashes (@samp{/})---which means that
7380 the functions will generate hierarchies of directories instead of having
7381 all the files in the top level directory
7382 (@file{~/News/alt/andrea-dworkin} instead of
7383 @file{~/News/alt.andrea-dworkin}.) This variable is @code{t} by default
7384 on most systems. However, for historical reasons, this is @code{nil} on
7385 Xenix and usg-unix-v machines by default.
7387 This function also affects kill and score file names. If this variable
7388 is a list, and the list contains the element @code{not-score}, long file
7389 names will not be used for score files, if it contains the element
7390 @code{not-save}, long file names will not be used for saving, and if it
7391 contains the element @code{not-kill}, long file names will not be used
7394 If you'd like to save articles in a hierarchy that looks something like
7398 (setq gnus-use-long-file-name '(not-save)) ; to get a hierarchy
7399 (setq gnus-default-article-saver
7400 'gnus-summary-save-in-file) ; no encoding
7403 Then just save with @kbd{o}. You'd then read this hierarchy with
7404 ephemeral @code{nneething} groups---@kbd{G D} in the group buffer, and
7405 the top level directory as the argument (@file{~/News/}). Then just walk
7406 around to the groups/directories with @code{nneething}.
7409 @node Decoding Articles
7410 @section Decoding Articles
7411 @cindex decoding articles
7413 Sometime users post articles (or series of articles) that have been
7414 encoded in some way or other. Gnus can decode them for you.
7417 * Uuencoded Articles:: Uudecode articles.
7418 * Shell Archives:: Unshar articles.
7419 * PostScript Files:: Split PostScript.
7420 * Other Files:: Plain save and binhex.
7421 * Decoding Variables:: Variables for a happy decoding.
7422 * Viewing Files:: You want to look at the result of the decoding?
7426 @cindex article series
7427 All these functions use the process/prefix convention
7428 (@pxref{Process/Prefix}) for finding out what articles to work on, with
7429 the extension that a ``single article'' means ``a single series''. Gnus
7430 can find out by itself what articles belong to a series, decode all the
7431 articles and unpack/view/save the resulting file(s).
7433 Gnus guesses what articles are in the series according to the following
7434 simplish rule: The subjects must be (nearly) identical, except for the
7435 last two numbers of the line. (Spaces are largely ignored, however.)
7437 For example: If you choose a subject called @samp{cat.gif (2/3)}, gnus
7438 will find all the articles that match the regexp @samp{^cat.gif
7439 ([0-9]+/[0-9]+).*$}.
7441 Subjects that are non-standard, like @samp{cat.gif (2/3) Part 6 of a
7442 series}, will not be properly recognized by any of the automatic viewing
7443 commands, and you have to mark the articles manually with @kbd{#}.
7446 @node Uuencoded Articles
7447 @subsection Uuencoded Articles
7449 @cindex uuencoded articles
7454 @kindex X u (Summary)
7455 @findex gnus-uu-decode-uu
7456 @c @icon{gnus-uu-decode-uu}
7457 Uudecodes the current series (@code{gnus-uu-decode-uu}).
7460 @kindex X U (Summary)
7461 @findex gnus-uu-decode-uu-and-save
7462 Uudecodes and saves the current series
7463 (@code{gnus-uu-decode-uu-and-save}).
7466 @kindex X v u (Summary)
7467 @findex gnus-uu-decode-uu-view
7468 Uudecodes and views the current series (@code{gnus-uu-decode-uu-view}).
7471 @kindex X v U (Summary)
7472 @findex gnus-uu-decode-uu-and-save-view
7473 Uudecodes, views and saves the current series
7474 (@code{gnus-uu-decode-uu-and-save-view}).
7478 Remember that these all react to the presence of articles marked with
7479 the process mark. If, for instance, you'd like to decode and save an
7480 entire newsgroup, you'd typically do @kbd{M P a}
7481 (@code{gnus-uu-mark-all}) and then @kbd{X U}
7482 (@code{gnus-uu-decode-uu-and-save}).
7484 All this is very much different from how @code{gnus-uu} worked with
7485 @sc{gnus 4.1}, where you had explicit keystrokes for everything under
7486 the sun. This version of @code{gnus-uu} generally assumes that you mark
7487 articles in some way (@pxref{Setting Process Marks}) and then press
7490 @vindex gnus-uu-notify-files
7491 Note: When trying to decode articles that have names matching
7492 @code{gnus-uu-notify-files}, which is hard-coded to
7493 @samp{[Cc][Ii][Nn][Dd][Yy][0-9]+.\\(gif\\|jpg\\)}, @code{gnus-uu} will
7494 automatically post an article on @samp{comp.unix.wizards} saying that
7495 you have just viewed the file in question. This feature can't be turned
7499 @node Shell Archives
7500 @subsection Shell Archives
7502 @cindex shell archives
7503 @cindex shared articles
7505 Shell archives (``shar files'') used to be a popular way to distribute
7506 sources, but it isn't used all that much today. In any case, we have
7507 some commands to deal with these:
7512 @kindex X s (Summary)
7513 @findex gnus-uu-decode-unshar
7514 Unshars the current series (@code{gnus-uu-decode-unshar}).
7517 @kindex X S (Summary)
7518 @findex gnus-uu-decode-unshar-and-save
7519 Unshars and saves the current series (@code{gnus-uu-decode-unshar-and-save}).
7522 @kindex X v s (Summary)
7523 @findex gnus-uu-decode-unshar-view
7524 Unshars and views the current series (@code{gnus-uu-decode-unshar-view}).
7527 @kindex X v S (Summary)
7528 @findex gnus-uu-decode-unshar-and-save-view
7529 Unshars, views and saves the current series
7530 (@code{gnus-uu-decode-unshar-and-save-view}).
7534 @node PostScript Files
7535 @subsection PostScript Files
7541 @kindex X p (Summary)
7542 @findex gnus-uu-decode-postscript
7543 Unpack the current PostScript series (@code{gnus-uu-decode-postscript}).
7546 @kindex X P (Summary)
7547 @findex gnus-uu-decode-postscript-and-save
7548 Unpack and save the current PostScript series
7549 (@code{gnus-uu-decode-postscript-and-save}).
7552 @kindex X v p (Summary)
7553 @findex gnus-uu-decode-postscript-view
7554 View the current PostScript series
7555 (@code{gnus-uu-decode-postscript-view}).
7558 @kindex X v P (Summary)
7559 @findex gnus-uu-decode-postscript-and-save-view
7560 View and save the current PostScript series
7561 (@code{gnus-uu-decode-postscript-and-save-view}).
7566 @subsection Other Files
7570 @kindex X o (Summary)
7571 @findex gnus-uu-decode-save
7572 Save the current series
7573 (@code{gnus-uu-decode-save}).
7576 @kindex X b (Summary)
7577 @findex gnus-uu-decode-binhex
7578 Unbinhex the current series (@code{gnus-uu-decode-binhex}). This
7579 doesn't really work yet.
7583 @node Decoding Variables
7584 @subsection Decoding Variables
7586 Adjective, not verb.
7589 * Rule Variables:: Variables that say how a file is to be viewed.
7590 * Other Decode Variables:: Other decode variables.
7591 * Uuencoding and Posting:: Variables for customizing uuencoding.
7595 @node Rule Variables
7596 @subsubsection Rule Variables
7597 @cindex rule variables
7599 Gnus uses @dfn{rule variables} to decide how to view a file. All these
7600 variables are of the form
7603 (list '(regexp1 command2)
7610 @item gnus-uu-user-view-rules
7611 @vindex gnus-uu-user-view-rules
7613 This variable is consulted first when viewing files. If you wish to use,
7614 for instance, @code{sox} to convert an @samp{.au} sound file, you could
7617 (setq gnus-uu-user-view-rules
7618 (list '("\\\\.au$" "sox %s -t .aiff > /dev/audio")))
7621 @item gnus-uu-user-view-rules-end
7622 @vindex gnus-uu-user-view-rules-end
7623 This variable is consulted if gnus couldn't make any matches from the
7624 user and default view rules.
7626 @item gnus-uu-user-archive-rules
7627 @vindex gnus-uu-user-archive-rules
7628 This variable can be used to say what commands should be used to unpack
7633 @node Other Decode Variables
7634 @subsubsection Other Decode Variables
7637 @vindex gnus-uu-grabbed-file-functions
7639 @item gnus-uu-grabbed-file-functions
7640 All functions in this list will be called right after each file has been
7641 successfully decoded---so that you can move or view files right away,
7642 and don't have to wait for all files to be decoded before you can do
7643 anything. Ready-made functions you can put in this list are:
7647 @item gnus-uu-grab-view
7648 @findex gnus-uu-grab-view
7651 @item gnus-uu-grab-move
7652 @findex gnus-uu-grab-move
7653 Move the file (if you're using a saving function.)
7656 @item gnus-uu-be-dangerous
7657 @vindex gnus-uu-be-dangerous
7658 Specifies what to do if unusual situations arise during decoding. If
7659 @code{nil}, be as conservative as possible. If @code{t}, ignore things
7660 that didn't work, and overwrite existing files. Otherwise, ask each
7663 @item gnus-uu-ignore-files-by-name
7664 @vindex gnus-uu-ignore-files-by-name
7665 Files with name matching this regular expression won't be viewed.
7667 @item gnus-uu-ignore-files-by-type
7668 @vindex gnus-uu-ignore-files-by-type
7669 Files with a @sc{mime} type matching this variable won't be viewed.
7670 Note that Gnus tries to guess what type the file is based on the name.
7671 @code{gnus-uu} is not a @sc{mime} package (yet), so this is slightly
7674 @item gnus-uu-tmp-dir
7675 @vindex gnus-uu-tmp-dir
7676 Where @code{gnus-uu} does its work.
7678 @item gnus-uu-do-not-unpack-archives
7679 @vindex gnus-uu-do-not-unpack-archives
7680 Non-@code{nil} means that @code{gnus-uu} won't peek inside archives
7681 looking for files to display.
7683 @item gnus-uu-view-and-save
7684 @vindex gnus-uu-view-and-save
7685 Non-@code{nil} means that the user will always be asked to save a file
7688 @item gnus-uu-ignore-default-view-rules
7689 @vindex gnus-uu-ignore-default-view-rules
7690 Non-@code{nil} means that @code{gnus-uu} will ignore the default viewing
7693 @item gnus-uu-ignore-default-archive-rules
7694 @vindex gnus-uu-ignore-default-archive-rules
7695 Non-@code{nil} means that @code{gnus-uu} will ignore the default archive
7698 @item gnus-uu-kill-carriage-return
7699 @vindex gnus-uu-kill-carriage-return
7700 Non-@code{nil} means that @code{gnus-uu} will strip all carriage returns
7703 @item gnus-uu-unmark-articles-not-decoded
7704 @vindex gnus-uu-unmark-articles-not-decoded
7705 Non-@code{nil} means that @code{gnus-uu} will mark unsuccessfully
7706 decoded articles as unread.
7708 @item gnus-uu-correct-stripped-uucode
7709 @vindex gnus-uu-correct-stripped-uucode
7710 Non-@code{nil} means that @code{gnus-uu} will @emph{try} to fix
7711 uuencoded files that have had trailing spaces deleted.
7713 @item gnus-uu-pre-uudecode-hook
7714 @vindex gnus-uu-pre-uudecode-hook
7715 Hook run before sending a message to @code{uudecode}.
7717 @item gnus-uu-view-with-metamail
7718 @vindex gnus-uu-view-with-metamail
7720 Non-@code{nil} means that @code{gnus-uu} will ignore the viewing
7721 commands defined by the rule variables and just fudge a @sc{mime}
7722 content type based on the file name. The result will be fed to
7723 @code{metamail} for viewing.
7725 @item gnus-uu-save-in-digest
7726 @vindex gnus-uu-save-in-digest
7727 Non-@code{nil} means that @code{gnus-uu}, when asked to save without
7728 decoding, will save in digests. If this variable is @code{nil},
7729 @code{gnus-uu} will just save everything in a file without any
7730 embellishments. The digesting almost conforms to RFC 1153---no easy way
7731 to specify any meaningful volume and issue numbers were found, so I
7732 simply dropped them.
7737 @node Uuencoding and Posting
7738 @subsubsection Uuencoding and Posting
7742 @item gnus-uu-post-include-before-composing
7743 @vindex gnus-uu-post-include-before-composing
7744 Non-@code{nil} means that @code{gnus-uu} will ask for a file to encode
7745 before you compose the article. If this variable is @code{t}, you can
7746 either include an encoded file with @kbd{C-c C-i} or have one included
7747 for you when you post the article.
7749 @item gnus-uu-post-length
7750 @vindex gnus-uu-post-length
7751 Maximum length of an article. The encoded file will be split into how
7752 many articles it takes to post the entire file.
7754 @item gnus-uu-post-threaded
7755 @vindex gnus-uu-post-threaded
7756 Non-@code{nil} means that @code{gnus-uu} will post the encoded file in a
7757 thread. This may not be smart, as no other decoder I have seen is able
7758 to follow threads when collecting uuencoded articles. (Well, I have
7759 seen one package that does that---@code{gnus-uu}, but somehow, I don't
7760 think that counts...) Default is @code{nil}.
7762 @item gnus-uu-post-separate-description
7763 @vindex gnus-uu-post-separate-description
7764 Non-@code{nil} means that the description will be posted in a separate
7765 article. The first article will typically be numbered (0/x). If this
7766 variable is @code{nil}, the description the user enters will be included
7767 at the beginning of the first article, which will be numbered (1/x).
7768 Default is @code{t}.
7774 @subsection Viewing Files
7775 @cindex viewing files
7776 @cindex pseudo-articles
7778 After decoding, if the file is some sort of archive, gnus will attempt
7779 to unpack the archive and see if any of the files in the archive can be
7780 viewed. For instance, if you have a gzipped tar file @file{pics.tar.gz}
7781 containing the files @file{pic1.jpg} and @file{pic2.gif}, gnus will
7782 uncompress and de-tar the main file, and then view the two pictures.
7783 This unpacking process is recursive, so if the archive contains archives
7784 of archives, it'll all be unpacked.
7786 Finally, gnus will normally insert a @dfn{pseudo-article} for each
7787 extracted file into the summary buffer. If you go to these
7788 ``articles'', you will be prompted for a command to run (usually Gnus
7789 will make a suggestion), and then the command will be run.
7791 @vindex gnus-view-pseudo-asynchronously
7792 If @code{gnus-view-pseudo-asynchronously} is @code{nil}, Emacs will wait
7793 until the viewing is done before proceeding.
7795 @vindex gnus-view-pseudos
7796 If @code{gnus-view-pseudos} is @code{automatic}, Gnus will not insert
7797 the pseudo-articles into the summary buffer, but view them
7798 immediately. If this variable is @code{not-confirm}, the user won't even
7799 be asked for a confirmation before viewing is done.
7801 @vindex gnus-view-pseudos-separately
7802 If @code{gnus-view-pseudos-separately} is non-@code{nil}, one
7803 pseudo-article will be created for each file to be viewed. If
7804 @code{nil}, all files that use the same viewing command will be given as
7805 a list of parameters to that command.
7807 @vindex gnus-insert-pseudo-articles
7808 If @code{gnus-insert-pseudo-articles} is non-@code{nil}, insert
7809 pseudo-articles when decoding. It is @code{t} by default.
7811 So; there you are, reading your @emph{pseudo-articles} in your
7812 @emph{virtual newsgroup} from the @emph{virtual server}; and you think:
7813 Why isn't anything real anymore? How did we get here?
7816 @node Article Treatment
7817 @section Article Treatment
7819 Reading through this huge manual, you may have quite forgotten that the
7820 object of newsreaders is to actually, like, read what people have
7821 written. Reading articles. Unfortunately, people are quite bad at
7822 writing, so there are tons of functions and variables to make reading
7823 these articles easier.
7826 * Article Highlighting:: You want to make the article look like fruit salad.
7827 * Article Fontisizing:: Making emphasized text look nice.
7828 * Article Hiding:: You also want to make certain info go away.
7829 * Article Washing:: Lots of way-neat functions to make life better.
7830 * Article Header:: Doing various header transformations.
7831 * Article Buttons:: Click on URLs, Message-IDs, addresses and the like.
7832 * Article Date:: Grumble, UT!
7833 * Article Display:: Display various stuff---X-Face, Picons, Smileys
7834 * Article Signature:: What is a signature?
7835 * Article Miscellania:: Various other stuff.
7839 @node Article Highlighting
7840 @subsection Article Highlighting
7841 @cindex highlighting
7843 Not only do you want your article buffer to look like fruit salad, but
7844 you want it to look like technicolor fruit salad.
7849 @kindex W H a (Summary)
7850 @findex gnus-article-highlight
7851 @findex gnus-article-maybe-highlight
7852 Do much highlighting of the current article
7853 (@code{gnus-article-highlight}). This function highlights header, cited
7854 text, the signature, and adds buttons to the body and the head.
7857 @kindex W H h (Summary)
7858 @findex gnus-article-highlight-headers
7859 @vindex gnus-header-face-alist
7860 Highlight the headers (@code{gnus-article-highlight-headers}). The
7861 highlighting will be done according to the @code{gnus-header-face-alist}
7862 variable, which is a list where each element has the form
7863 @code{(@var{regexp} @var{name} @var{content})}.
7864 @var{regexp} is a regular expression for matching the
7865 header, @var{name} is the face used for highlighting the header name
7866 (@pxref{Faces and Fonts}) and @var{content} is the face for highlighting
7867 the header value. The first match made will be used. Note that
7868 @var{regexp} shouldn't have @samp{^} prepended---Gnus will add one.
7871 @kindex W H c (Summary)
7872 @findex gnus-article-highlight-citation
7873 Highlight cited text (@code{gnus-article-highlight-citation}).
7875 Some variables to customize the citation highlights:
7878 @vindex gnus-cite-parse-max-size
7880 @item gnus-cite-parse-max-size
7881 If the article size if bigger than this variable (which is 25000 by
7882 default), no citation highlighting will be performed.
7884 @item gnus-cite-max-prefix
7885 @vindex gnus-cite-max-prefix
7886 Maximum possible length for a citation prefix (default 20).
7888 @item gnus-cite-face-list
7889 @vindex gnus-cite-face-list
7890 List of faces used for highlighting citations (@pxref{Faces and Fonts}).
7891 When there are citations from multiple articles in the same message,
7892 gnus will try to give each citation from each article its own face.
7893 This should make it easier to see who wrote what.
7895 @item gnus-supercite-regexp
7896 @vindex gnus-supercite-regexp
7897 Regexp matching normal Supercite attribution lines.
7899 @item gnus-supercite-secondary-regexp
7900 @vindex gnus-supercite-secondary-regexp
7901 Regexp matching mangled Supercite attribution lines.
7903 @item gnus-cite-minimum-match-count
7904 @vindex gnus-cite-minimum-match-count
7905 Minimum number of identical prefixes we have to see before we believe
7906 that it's a citation.
7908 @item gnus-cite-attribution-prefix
7909 @vindex gnus-cite-attribution-prefix
7910 Regexp matching the beginning of an attribution line.
7912 @item gnus-cite-attribution-suffix
7913 @vindex gnus-cite-attribution-suffix
7914 Regexp matching the end of an attribution line.
7916 @item gnus-cite-attribution-face
7917 @vindex gnus-cite-attribution-face
7918 Face used for attribution lines. It is merged with the face for the
7919 cited text belonging to the attribution.
7925 @kindex W H s (Summary)
7926 @vindex gnus-signature-separator
7927 @vindex gnus-signature-face
7928 @findex gnus-article-highlight-signature
7929 Highlight the signature (@code{gnus-article-highlight-signature}).
7930 Everything after @code{gnus-signature-separator} (@pxref{Article
7931 Signature}) in an article will be considered a signature and will be
7932 highlighted with @code{gnus-signature-face}, which is @code{italic} by
7937 @xref{Customizing Articles}, for how to highlight articles automatically.
7940 @node Article Fontisizing
7941 @subsection Article Fontisizing
7943 @cindex article emphasis
7945 @findex gnus-article-emphasize
7946 @kindex W e (Summary)
7947 People commonly add emphasis to words in news articles by writing things
7948 like @samp{_this_} or @samp{*this*} or @samp{/this/}. Gnus can make
7949 this look nicer by running the article through the @kbd{W e}
7950 (@code{gnus-article-emphasize}) command.
7952 @vindex gnus-emphasis-alist
7953 How the emphasis is computed is controlled by the
7954 @code{gnus-emphasis-alist} variable. This is an alist where the first
7955 element is a regular expression to be matched. The second is a number
7956 that says what regular expression grouping is used to find the entire
7957 emphasized word. The third is a number that says what regexp grouping
7958 should be displayed and highlighted. (The text between these two
7959 groupings will be hidden.) The fourth is the face used for
7963 (setq gnus-emphasis-alist
7964 '(("_\\(\\w+\\)_" 0 1 gnus-emphasis-underline)
7965 ("\\*\\(\\w+\\)\\*" 0 1 gnus-emphasis-bold)))
7974 @vindex gnus-emphasis-underline
7975 @vindex gnus-emphasis-bold
7976 @vindex gnus-emphasis-italic
7977 @vindex gnus-emphasis-underline-bold
7978 @vindex gnus-emphasis-underline-italic
7979 @vindex gnus-emphasis-bold-italic
7980 @vindex gnus-emphasis-underline-bold-italic
7981 By default, there are seven rules, and they use the following faces:
7982 @code{gnus-emphasis-bold}, @code{gnus-emphasis-italic},
7983 @code{gnus-emphasis-underline}, @code{gnus-emphasis-bold-italic},
7984 @code{gnus-emphasis-underline-italic},
7985 @code{gnus-emphasis-underline-bold}, and
7986 @code{gnus-emphasis-underline-bold-italic}.
7988 If you want to change these faces, you can either use @kbd{M-x
7989 customize}, or you can use @code{copy-face}. For instance, if you want
7990 to make @code{gnus-emphasis-italic} use a red face instead, you could
7994 (copy-face 'red 'gnus-emphasis-italic)
7997 @vindex gnus-group-highlight-words-alist
7999 If you want to highlight arbitrary words, you can use the
8000 @code{gnus-group-highlight-words-alist} variable, which uses the same
8001 syntax as @code{gnus-emphasis-alist}. The @code{highlight-words} group
8002 parameter (@pxref{Group Parameters}) can also be used.
8004 @xref{Customizing Articles}, for how to fontize articles automatically.
8007 @node Article Hiding
8008 @subsection Article Hiding
8009 @cindex article hiding
8011 Or rather, hiding certain things in each article. There usually is much
8012 too much cruft in most articles.
8017 @kindex W W a (Summary)
8018 @findex gnus-article-hide
8019 Do quite a lot of hiding on the article buffer
8020 (@kbd{gnus-article-hide}). In particular, this function will hide
8021 headers, PGP, cited text and the signature.
8024 @kindex W W h (Summary)
8025 @findex gnus-article-hide-headers
8026 Hide headers (@code{gnus-article-hide-headers}). @xref{Hiding
8030 @kindex W W b (Summary)
8031 @findex gnus-article-hide-boring-headers
8032 Hide headers that aren't particularly interesting
8033 (@code{gnus-article-hide-boring-headers}). @xref{Hiding Headers}.
8036 @kindex W W s (Summary)
8037 @findex gnus-article-hide-signature
8038 Hide signature (@code{gnus-article-hide-signature}). @xref{Article
8042 @kindex W W l (Summary)
8043 @findex gnus-article-hide-list-identifiers
8044 @vindex gnus-list-identifiers
8045 Strip list identifiers specified in @code{gnus-list-identifiers}. These
8046 are strings some mailing list servers add to the beginning of all
8047 @code{Subject} headers---for example, @samp{[zebra 4711]}. Any leading
8048 @samp{Re: } is skipped before stripping. @code{gnus-list-identifiers}
8049 may not contain @code{\\(..\\)}.
8053 @item gnus-list-identifiers
8054 @vindex gnus-list-identifiers
8055 A regular expression that matches list identifiers to be removed from
8056 subject. This can also be a list of regular expressions.
8061 @kindex W W p (Summary)
8062 @findex gnus-article-hide-pgp
8063 @vindex gnus-article-hide-pgp-hook
8064 Hide @sc{pgp} signatures (@code{gnus-article-hide-pgp}). The
8065 @code{gnus-article-hide-pgp-hook} hook will be run after a @sc{pgp}
8066 signature has been hidden. For example, to automatically verify
8067 articles that have signatures in them do:
8069 ;;; Hide pgp cruft if any.
8071 (setq gnus-treat-strip-pgp t)
8073 ;;; After hiding pgp, verify the message;
8074 ;;; only happens if pgp signature is found.
8076 (add-hook 'gnus-article-hide-pgp-hook
8079 (set-buffer gnus-original-article-buffer)
8084 @kindex W W P (Summary)
8085 @findex gnus-article-hide-pem
8086 Hide @sc{pem} (privacy enhanced messages) cruft
8087 (@code{gnus-article-hide-pem}).
8090 @kindex W W B (Summary)
8091 @findex gnus-article-strip-banner
8092 @vindex gnus-article-banner-alist
8093 @vindex gnus-article-address-banner-alist
8096 @cindex stripping advertisements
8097 @cindex advertisements
8098 Strip the banner specified by the @code{banner} group parameter
8099 (@code{gnus-article-strip-banner}). This is mainly used to hide those
8100 annoying banners and/or signatures that some mailing lists and moderated
8101 groups adds to all the messages. The way to use this function is to add
8102 the @code{banner} group parameter (@pxref{Group Parameters}) to the
8103 group you want banners stripped from. The parameter either be a string,
8104 which will be interpreted as a regular expression matching text to be
8105 removed, or the symbol @code{signature}, meaning that the (last)
8106 signature should be removed, or other symbol, meaning that the
8107 corresponding regular expression in @code{gnus-article-banner-alist} is
8110 Regardless of a group, you can hide things like advertisements only when
8111 the sender of an article has a certain mail address specified in
8112 @code{gnus-article-address-banner-alist}.
8116 @item gnus-article-address-banner-alist
8117 @vindex gnus-article-address-banner-alist
8118 Alist of mail addresses and banners. Each element has the form
8119 @code{(ADDRESS . BANNER)}, where ADDRESS is a regexp matching a mail
8120 address in the From header, BANNER is one of a symbol @code{signature},
8121 an item in @code{gnus-article-banner-alist}, a regexp and @code{nil}.
8122 If ADDRESS matches author's mail address, it will remove things like
8123 advertisements. For example, if a sender has the mail address
8124 @samp{hail@@yoo-hoo.co.jp} and there is a banner something like
8125 @samp{Do You Yoo-hoo!?} in all articles he sends, you can use the
8126 following element to remove them:
8129 ("@@yoo-hoo\\.co\\.jp\\'" . "\n_+\nDo You Yoo-hoo!\\?\n.*\n.*\n")
8135 @kindex W W c (Summary)
8136 @findex gnus-article-hide-citation
8137 Hide citation (@code{gnus-article-hide-citation}). Some variables for
8138 customizing the hiding:
8142 @item gnus-cited-opened-text-button-line-format
8143 @itemx gnus-cited-closed-text-button-line-format
8144 @vindex gnus-cited-closed-text-button-line-format
8145 @vindex gnus-cited-opened-text-button-line-format
8146 Gnus adds buttons to show where the cited text has been hidden, and to
8147 allow toggle hiding the text. The format of the variable is specified
8148 by these format-like variable (@pxref{Formatting Variables}). These
8153 Starting point of the hidden text.
8155 Ending point of the hidden text.
8157 Number of characters in the hidden region.
8159 Number of lines of hidden text.
8162 @item gnus-cited-lines-visible
8163 @vindex gnus-cited-lines-visible
8164 The number of lines at the beginning of the cited text to leave
8165 shown. This can also be a cons cell with the number of lines at the top
8166 and bottom of the text, respectively, to remain visible.
8171 @kindex W W C-c (Summary)
8172 @findex gnus-article-hide-citation-maybe
8174 Hide citation (@code{gnus-article-hide-citation-maybe}) depending on the
8175 following two variables:
8178 @item gnus-cite-hide-percentage
8179 @vindex gnus-cite-hide-percentage
8180 If the cited text is of a bigger percentage than this variable (default
8181 50), hide the cited text.
8183 @item gnus-cite-hide-absolute
8184 @vindex gnus-cite-hide-absolute
8185 The cited text must have at least this length (default 10) before it
8190 @kindex W W C (Summary)
8191 @findex gnus-article-hide-citation-in-followups
8192 Hide cited text in articles that aren't roots
8193 (@code{gnus-article-hide-citation-in-followups}). This isn't very
8194 useful as an interactive command, but might be a handy function to stick
8195 have happen automatically (@pxref{Customizing Articles}).
8199 All these ``hiding'' commands are toggles, but if you give a negative
8200 prefix to these commands, they will show what they have previously
8201 hidden. If you give a positive prefix, they will always hide.
8203 Also @pxref{Article Highlighting} for further variables for
8204 citation customization.
8206 @xref{Customizing Articles}, for how to hide article elements
8210 @node Article Washing
8211 @subsection Article Washing
8213 @cindex article washing
8215 We call this ``article washing'' for a really good reason. Namely, the
8216 @kbd{A} key was taken, so we had to use the @kbd{W} key instead.
8218 @dfn{Washing} is defined by us as ``changing something from something to
8219 something else'', but normally results in something looking better.
8222 @xref{Customizing Articles}, if you want to change how Gnus displays
8223 articles by default.
8228 This is not really washing, it's sort of the opposite of washing. If
8229 you type this, you see the article exactly as it exists on disk or on
8233 @kindex W l (Summary)
8234 @findex gnus-summary-stop-page-breaking
8235 Remove page breaks from the current article
8236 (@code{gnus-summary-stop-page-breaking}). @xref{Misc Article}, for page
8240 @kindex W r (Summary)
8241 @findex gnus-summary-caesar-message
8242 @c @icon{gnus-summary-caesar-message}
8243 Do a Caesar rotate (rot13) on the article buffer
8244 (@code{gnus-summary-caesar-message}).
8245 Unreadable articles that tell you to read them with Caesar rotate or rot13.
8246 (Typically offensive jokes and such.)
8248 It's commonly called ``rot13'' because each letter is rotated 13
8249 positions in the alphabet, e. g. @samp{B} (letter #2) -> @samp{O} (letter
8250 #15). It is sometimes referred to as ``Caesar rotate'' because Caesar
8251 is rumored to have employed this form of, uh, somewhat weak encryption.
8254 @kindex W m (Summary)
8255 @findex gnus-summary-morse-message
8256 @c @icon{gnus-summary-morse-message}
8257 Morse decode the article buffer (@code{gnus-summary-morse-message}).
8261 @kindex W t (Summary)
8263 @findex gnus-summary-toggle-header
8264 Toggle whether to display all headers in the article buffer
8265 (@code{gnus-summary-toggle-header}).
8268 @kindex W v (Summary)
8269 @findex gnus-summary-verbose-headers
8270 Toggle whether to display all headers in the article buffer permanently
8271 (@code{gnus-summary-verbose-headers}).
8274 @kindex W m (Summary)
8275 @findex gnus-summary-toggle-mime
8276 Toggle whether to run the article through @sc{mime} before displaying
8277 (@code{gnus-summary-toggle-mime}).
8280 @kindex W o (Summary)
8281 @findex gnus-article-treat-overstrike
8282 Treat overstrike (@code{gnus-article-treat-overstrike}).
8285 @kindex W d (Summary)
8286 @findex gnus-article-treat-dumbquotes
8287 @vindex gnus-article-dumbquotes-map
8289 @cindex M****s*** sm*rtq**t*s
8291 Treat M****s*** sm*rtq**t*s according to
8292 @code{gnus-article-dumbquotes-map}
8293 (@code{gnus-article-treat-dumbquotes}). Note that this function guesses
8294 whether a character is a sm*rtq**t* or not, so it should only be used
8297 Sm*rtq**t*s are M****s***'s unilateral extension to the character map in
8298 an attempt to provide more quoting characters. If you see something
8299 like @code{\222} or @code{\264} where you're expecting some kind of
8300 apostrophe or quotation mark, then try this wash.
8303 @kindex W k (Summary)
8304 @kindex W Y f (Summary)
8305 @findex gnus-article-outlook-deuglify-article
8306 @cindex Outlook Express
8307 Deuglify broken Outlook (Express) articles.
8308 (@code{gnus-article-outlook-deuglify-article}).
8311 @kindex W Y u (Summary)
8312 @findex gnus-outlook-unwrap-lines
8313 Unwrap lines that appear to be wrapped citation lines. You can control
8314 what lines will be unwrapped by frobbing
8315 @code{gnus-outlook-deuglify-unwrap-min} and
8316 @code{gnus-outlook-deuglify-unwrap-max}, indicating the miminum and
8317 maximum length of an unwrapped citation line.
8318 (@code{gnus-outlook-deuglify-article}).
8321 @kindex W Y a (Summary)
8322 @findex gnus-outlook-repair-attribution
8323 Repair a broken attribution line
8324 (@code{gnus-outlook-repair-attribution}).
8327 @kindex W Y c (Summary)
8328 @findex gnus-outlook-rearrange-citation
8329 Repair broken citations by rearranging the text.
8330 (@code{gnus-outlook-rearrange-citation}).
8333 @kindex W w (Summary)
8334 @findex gnus-article-fill-cited-article
8335 Do word wrap (@code{gnus-article-fill-cited-article}).
8337 You can give the command a numerical prefix to specify the width to use
8341 @kindex W Q (Summary)
8342 @findex gnus-article-fill-long-lines
8343 Fill long lines (@code{gnus-article-fill-long-lines}).
8346 @kindex W C (Summary)
8347 @findex gnus-article-capitalize-sentences
8348 Capitalize the first word in each sentence
8349 (@code{gnus-article-capitalize-sentences}).
8352 @kindex W c (Summary)
8353 @findex gnus-article-remove-cr
8354 Translate CRLF pairs (i. e., @samp{^M}s on the end of the lines) into LF
8355 (this takes care of DOS line endings), and then translate any remaining
8356 CRs into LF (this takes care of Mac line endings)
8357 (@code{gnus-article-remove-cr}).
8360 @kindex W 6 (Summary)
8361 @findex gnus-article-de-base64-unreadable
8362 Treat base64 (@code{gnus-article-de-base64-unreadable}).
8363 Base64 is one common @sc{mime} encoding employed when sending non-ASCII
8364 (i. e., 8-bit) articles. Note that this is usually done
8365 automatically by Gnus if the message in question has a
8366 @code{Content-Transfer-Encoding} header that says that this encoding has
8368 If a prefix is given, a charset will be asked for.
8371 @kindex W Z (Summary)
8372 @findex gnus-article-decode-HZ
8373 Treat HZ or HZP (@code{gnus-article-decode-HZ}). HZ (or HZP) is one
8374 common encoding employed when sending Chinese articles. It typically
8375 makes strings look like @samp{~@{<:Ky2;S@{#,NpJ)l6HK!#~@}}.
8378 @kindex W u (Summary)
8379 @findex gnus-article-unsplit-urls
8380 Remove newlines from within URLs. Some mailers insert newlines into
8381 outgoing email messages to keep lines short. This reformatting can
8382 split long URLs onto multiple lines. Repair those URLs by removing
8383 the newlines (@code{gnus-article-unsplit-urls}).
8386 @kindex W h (Summary)
8387 @findex gnus-article-wash-html
8388 Treat @sc{html} (@code{gnus-article-wash-html}). Note that this is
8389 usually done automatically by Gnus if the message in question has a
8390 @code{Content-Type} header that says that the message is @sc{html}.
8392 If a prefix is given, a charset will be asked for.
8394 @vindex gnus-article-wash-function
8395 The default is to use the function specified by
8396 @code{mm-text-html-renderer} (@pxref{(emacs-mime)Display
8397 Customization}) to convert the @sc{html}, but this is controlled by
8398 the @code{gnus-article-wash-function} variable. Pre-defined functions
8399 you can use include:
8406 Use emacs-w3m (see @uref{http://emacs-w3m.namazu.org/} for more
8410 Use Links (see @uref{http://artax.karlin.mff.cuni.cz/~mikulas/links/}).
8413 Use Lynx (see @uref{http://lynx.browser.org/}).
8416 Use html2text -- a simple @sc{html} converter included with Gnus.
8421 @kindex W b (Summary)
8422 @findex gnus-article-add-buttons
8423 Add clickable buttons to the article (@code{gnus-article-add-buttons}).
8424 @xref{Article Buttons}.
8427 @kindex W B (Summary)
8428 @findex gnus-article-add-buttons-to-head
8429 Add clickable buttons to the article headers
8430 (@code{gnus-article-add-buttons-to-head}).
8433 @kindex W p (Summary)
8434 @findex gnus-article-verify-x-pgp-sig
8435 Verify a signed control message (@code{gnus-article-verify-x-pgp-sig}).
8436 Control messages such as @code{newgroup} and @code{checkgroups} are
8437 usually signed by the hierarchy maintainer. You need to add the PGP
8438 public key of the maintainer to your keyring to verify the
8439 message.@footnote{PGP keys for many hierarchies are available at
8440 @uref{ftp://ftp.isc.org/pub/pgpcontrol/README.html}}
8443 @kindex W s (Summary)
8444 @findex gnus-summary-force-verify-and-decrypt
8445 Verify a signed (PGP, @sc{pgp/mime} or @sc{s/mime}) message
8446 (@code{gnus-summary-force-verify-and-decrypt}). @xref{Security}.
8449 @kindex W a (Summary)
8450 @findex gnus-article-strip-headers-in-body
8451 Strip headers like the @code{X-No-Archive} header from the beginning of
8452 article bodies (@code{gnus-article-strip-headers-in-body}).
8455 @kindex W E l (Summary)
8456 @findex gnus-article-strip-leading-blank-lines
8457 Remove all blank lines from the beginning of the article
8458 (@code{gnus-article-strip-leading-blank-lines}).
8461 @kindex W E m (Summary)
8462 @findex gnus-article-strip-multiple-blank-lines
8463 Replace all blank lines with empty lines and then all multiple empty
8464 lines with a single empty line.
8465 (@code{gnus-article-strip-multiple-blank-lines}).
8468 @kindex W E t (Summary)
8469 @findex gnus-article-remove-trailing-blank-lines
8470 Remove all blank lines at the end of the article
8471 (@code{gnus-article-remove-trailing-blank-lines}).
8474 @kindex W E a (Summary)
8475 @findex gnus-article-strip-blank-lines
8476 Do all the three commands above
8477 (@code{gnus-article-strip-blank-lines}).
8480 @kindex W E A (Summary)
8481 @findex gnus-article-strip-all-blank-lines
8482 Remove all blank lines
8483 (@code{gnus-article-strip-all-blank-lines}).
8486 @kindex W E s (Summary)
8487 @findex gnus-article-strip-leading-space
8488 Remove all white space from the beginning of all lines of the article
8489 body (@code{gnus-article-strip-leading-space}).
8492 @kindex W E e (Summary)
8493 @findex gnus-article-strip-trailing-space
8494 Remove all white space from the end of all lines of the article
8495 body (@code{gnus-article-strip-trailing-space}).
8499 @xref{Customizing Articles}, for how to wash articles automatically.
8502 @node Article Header
8503 @subsection Article Header
8505 These commands perform various transformations of article header.
8510 @kindex W G u (Summary)
8511 @findex gnus-article-treat-unfold-headers
8512 Unfold folded header lines (@code{gnus-article-treat-unfold-headers}).
8515 @kindex W G n (Summary)
8516 @findex gnus-article-treat-fold-newsgroups
8517 Fold the @code{Newsgroups} and @code{Followup-To} headers
8518 (@code{gnus-article-treat-fold-newsgroups}).
8521 @kindex W G f (Summary)
8522 @findex gnus-article-treat-fold-headers
8523 Fold all the message headers
8524 (@code{gnus-article-treat-fold-headers}).
8528 @findex gnus-article-remove-leading-whitespace
8529 Remove excessive whitespace from all headers
8530 (@code{gnus-article-remove-leading-whitespace}).
8535 @node Article Buttons
8536 @subsection Article Buttons
8539 People often include references to other stuff in articles, and it would
8540 be nice if Gnus could just fetch whatever it is that people talk about
8541 with the minimum of fuzz when you hit @kbd{RET} or use the middle mouse
8542 button on these references.
8544 @vindex gnus-button-man-handler
8545 Gnus adds @dfn{buttons} to certain standard references by default:
8546 Well-formed URLs, mail addresses, Message-IDs, Info links and man pages.
8547 This is controlled by two variables, one that handles article bodies and
8548 one that handles article heads:
8552 @item gnus-button-alist
8553 @vindex gnus-button-alist
8554 This is an alist where each entry has this form:
8557 (REGEXP BUTTON-PAR USE-P FUNCTION DATA-PAR)
8563 All text that match this regular expression (case insensitive) will be
8564 considered an external reference. Here's a typical regexp that matches
8565 embedded URLs: @samp{<URL:\\([^\n\r>]*\\)>}. This can also be a
8566 variable containing a regexp, useful variables to use include
8567 @code{gnus-button-url-regexp}.
8570 Gnus has to know which parts of the matches is to be highlighted. This
8571 is a number that says what sub-expression of the regexp is to be
8572 highlighted. If you want it all highlighted, you use 0 here.
8575 This form will be @code{eval}ed, and if the result is non-@code{nil},
8576 this is considered a match. This is useful if you want extra sifting to
8577 avoid false matches.
8580 This function will be called when you click on this button.
8583 As with @var{button-par}, this is a sub-expression number, but this one
8584 says which part of the match is to be sent as data to @var{function}.
8588 So the full entry for buttonizing URLs is then
8591 ("<URL:\\([^\n\r>]*\\)>" 0 t gnus-button-url 1)
8594 @item gnus-header-button-alist
8595 @vindex gnus-header-button-alist
8596 This is just like the other alist, except that it is applied to the
8597 article head only, and that each entry has an additional element that is
8598 used to say what headers to apply the buttonize coding to:
8601 (HEADER REGEXP BUTTON-PAR USE-P FUNCTION DATA-PAR)
8604 @var{header} is a regular expression.
8606 @item gnus-button-url-regexp
8607 @vindex gnus-button-url-regexp
8608 A regular expression that matches embedded URLs. It is used in the
8609 default values of the variables above.
8611 @item gnus-article-button-face
8612 @vindex gnus-article-button-face
8613 Face used on buttons.
8615 @item gnus-article-mouse-face
8616 @vindex gnus-article-mouse-face
8617 Face used when the mouse cursor is over a button.
8621 @xref{Customizing Articles}, for how to buttonize articles automatically.
8625 @subsection Article Date
8627 The date is most likely generated in some obscure timezone you've never
8628 heard of, so it's quite nice to be able to find out what the time was
8629 when the article was sent.
8634 @kindex W T u (Summary)
8635 @findex gnus-article-date-ut
8636 Display the date in UT (aka. GMT, aka ZULU)
8637 (@code{gnus-article-date-ut}).
8640 @kindex W T i (Summary)
8641 @findex gnus-article-date-iso8601
8643 Display the date in international format, aka. ISO 8601
8644 (@code{gnus-article-date-iso8601}).
8647 @kindex W T l (Summary)
8648 @findex gnus-article-date-local
8649 Display the date in the local timezone (@code{gnus-article-date-local}).
8652 @kindex W T p (Summary)
8653 @findex gnus-article-date-english
8654 Display the date in a format that's easily pronounceable in English
8655 (@code{gnus-article-date-english}).
8658 @kindex W T s (Summary)
8659 @vindex gnus-article-time-format
8660 @findex gnus-article-date-user
8661 @findex format-time-string
8662 Display the date using a user-defined format
8663 (@code{gnus-article-date-user}). The format is specified by the
8664 @code{gnus-article-time-format} variable, and is a string that's passed
8665 to @code{format-time-string}. See the documentation of that variable
8666 for a list of possible format specs.
8669 @kindex W T e (Summary)
8670 @findex gnus-article-date-lapsed
8671 @findex gnus-start-date-timer
8672 @findex gnus-stop-date-timer
8673 Say how much time has elapsed between the article was posted and now
8674 (@code{gnus-article-date-lapsed}). It looks something like:
8677 X-Sent: 6 weeks, 4 days, 1 hour, 3 minutes, 8 seconds ago
8680 The value of @code{gnus-article-date-lapsed-new-header} determines
8681 whether this header will just be added below the old Date one, or will
8684 An advantage of using Gnus to read mail is that it converts simple bugs
8685 into wonderful absurdities.
8687 If you want to have this line updated continually, you can put
8690 (gnus-start-date-timer)
8693 in your @file{.gnus.el} file, or you can run it off of some hook. If
8694 you want to stop the timer, you can use the @code{gnus-stop-date-timer}
8698 @kindex W T o (Summary)
8699 @findex gnus-article-date-original
8700 Display the original date (@code{gnus-article-date-original}). This can
8701 be useful if you normally use some other conversion function and are
8702 worried that it might be doing something totally wrong. Say, claiming
8703 that the article was posted in 1854. Although something like that is
8704 @emph{totally} impossible. Don't you trust me? *titter*
8708 @xref{Customizing Articles}, for how to display the date in your
8709 preferred format automatically.
8712 @node Article Display
8713 @subsection Article Display
8718 These commands add various frivolous display gimmicks to the article
8719 buffer in Emacs versions that support them.
8721 @code{X-Face} headers are small black-and-white images supplied by the
8722 message headers (@pxref{X-Face}).
8724 Picons, on the other hand, reside on your own system, and Gnus will
8725 try to match the headers to what you have (@pxref{Picons}).
8727 Smileys are those little @samp{:-)} symbols that people like to litter
8728 their messages with (@pxref{Smileys}).
8730 All these functions are toggles--if the elements already exist,
8735 @kindex W D x (Summary)
8736 @findex gnus-article-display-x-face
8737 Display an @code{X-Face} in the @code{From} header.
8738 (@code{gnus-article-display-x-face}).
8741 @kindex W D d (Summary)
8742 @findex gnus-article-display-face
8743 Display a @code{Face} in the @code{From} header.
8744 (@code{gnus-article-display-face}).
8747 @kindex W D s (Summary)
8748 @findex gnus-treat-smiley
8749 Display smileys (@code{gnus-treat-smiley}).
8752 @kindex W D f (Summary)
8753 @findex gnus-treat-from-picon
8754 Piconify the @code{From} header (@code{gnus-treat-from-picon}).
8757 @kindex W D m (Summary)
8758 @findex gnus-treat-mail-picon
8759 Piconify all mail headers (i. e., @code{Cc}, @code{To})
8760 (@code{gnus-treat-mail-picon}).
8763 @kindex W D n (Summary)
8764 @findex gnus-treat-newsgroups-picon
8765 Piconify all news headers (i. e., @code{Newsgroups} and
8766 @code{Followup-To}) (@code{gnus-treat-newsgroups-picon}).
8769 @kindex W D D (Summary)
8770 @findex gnus-article-remove-images
8771 Remove all images from the article buffer
8772 (@code{gnus-article-remove-images}).
8778 @node Article Signature
8779 @subsection Article Signature
8781 @cindex article signature
8783 @vindex gnus-signature-separator
8784 Each article is divided into two parts---the head and the body. The
8785 body can be divided into a signature part and a text part. The variable
8786 that says what is to be considered a signature is
8787 @code{gnus-signature-separator}. This is normally the standard
8788 @samp{^-- $} as mandated by son-of-RFC 1036. However, many people use
8789 non-standard signature separators, so this variable can also be a list
8790 of regular expressions to be tested, one by one. (Searches are done
8791 from the end of the body towards the beginning.) One likely value is:
8794 (setq gnus-signature-separator
8795 '("^-- $" ; The standard
8796 "^-- *$" ; A common mangling
8797 "^-------*$" ; Many people just use a looong
8798 ; line of dashes. Shame!
8799 "^ *--------*$" ; Double-shame!
8800 "^________*$" ; Underscores are also popular
8801 "^========*$")) ; Pervert!
8804 The more permissive you are, the more likely it is that you'll get false
8807 @vindex gnus-signature-limit
8808 @code{gnus-signature-limit} provides a limit to what is considered a
8809 signature when displaying articles.
8813 If it is an integer, no signature may be longer (in characters) than
8816 If it is a floating point number, no signature may be longer (in lines)
8819 If it is a function, the function will be called without any parameters,
8820 and if it returns @code{nil}, there is no signature in the buffer.
8822 If it is a string, it will be used as a regexp. If it matches, the text
8823 in question is not a signature.
8826 This variable can also be a list where the elements may be of the types
8827 listed above. Here's an example:
8830 (setq gnus-signature-limit
8831 '(200.0 "^---*Forwarded article"))
8834 This means that if there are more than 200 lines after the signature
8835 separator, or the text after the signature separator is matched by
8836 the regular expression @samp{^---*Forwarded article}, then it isn't a
8837 signature after all.
8840 @node Article Miscellania
8841 @subsection Article Miscellania
8845 @kindex A t (Summary)
8846 @findex gnus-article-babel
8847 Translate the article from one language to another
8848 (@code{gnus-article-babel}).
8854 @section MIME Commands
8855 @cindex MIME decoding
8857 @cindex viewing attachments
8859 The following commands all understand the numerical prefix. For
8860 instance, @kbd{3 b} means ``view the third @sc{mime} part''.
8866 @kindex K v (Summary)
8867 View the @sc{mime} part.
8870 @kindex K o (Summary)
8871 Save the @sc{mime} part.
8874 @kindex K c (Summary)
8875 Copy the @sc{mime} part.
8878 @kindex K e (Summary)
8879 View the @sc{mime} part externally.
8882 @kindex K i (Summary)
8883 View the @sc{mime} part internally.
8886 @kindex K | (Summary)
8887 Pipe the @sc{mime} part to an external command.
8890 The rest of these @sc{mime} commands do not use the numerical prefix in
8895 @kindex K b (Summary)
8896 Make all the @sc{mime} parts have buttons in front of them. This is
8897 mostly useful if you wish to save (or perform other actions) on inlined
8901 @kindex K m (Summary)
8902 @findex gnus-summary-repair-multipart
8903 Some multipart messages are transmitted with missing or faulty headers.
8904 This command will attempt to ``repair'' these messages so that they can
8905 be viewed in a more pleasant manner
8906 (@code{gnus-summary-repair-multipart}).
8909 @kindex X m (Summary)
8910 @findex gnus-summary-save-parts
8911 Save all parts matching a @sc{mime} type to a directory
8912 (@code{gnus-summary-save-parts}). Understands the process/prefix
8913 convention (@pxref{Process/Prefix}).
8916 @kindex M-t (Summary)
8917 @findex gnus-summary-toggle-display-buttonized
8918 Toggle the buttonized display of the article buffer
8919 (@code{gnus-summary-toggle-display-buttonized}).
8922 @kindex W M w (Summary)
8923 @findex gnus-article-decode-mime-words
8924 Decode RFC 2047-encoded words in the article headers
8925 (@code{gnus-article-decode-mime-words}).
8928 @kindex W M c (Summary)
8929 @findex gnus-article-decode-charset
8930 Decode encoded article bodies as well as charsets
8931 (@code{gnus-article-decode-charset}).
8933 This command looks in the @code{Content-Type} header to determine the
8934 charset. If there is no such header in the article, you can give it a
8935 prefix, which will prompt for the charset to decode as. In regional
8936 groups where people post using some common encoding (but do not
8937 include @sc{mime} headers), you can set the @code{charset} group/topic
8938 parameter to the required charset (@pxref{Group Parameters}).
8941 @kindex W M v (Summary)
8942 @findex gnus-mime-view-all-parts
8943 View all the @sc{mime} parts in the current article
8944 (@code{gnus-mime-view-all-parts}).
8951 @item gnus-ignored-mime-types
8952 @vindex gnus-ignored-mime-types
8953 This is a list of regexps. @sc{mime} types that match a regexp from
8954 this list will be completely ignored by Gnus. The default value is
8957 To have all Vcards be ignored, you'd say something like this:
8960 (setq gnus-ignored-mime-types
8964 @item gnus-article-loose-mime
8965 @vindex gnus-article-loose-mime
8966 If non-@code{nil}, Gnus won't required the @samp{MIME-Version} header
8967 before interpreting the message as a @sc{mime} message. This helps
8968 when reading messages from certain broken mail user agents. The
8969 default is @code{nil}.
8971 @item gnus-article-emulate-mime
8972 @vindex gnus-article-emulate-mime
8973 There are other, non-@sc{mime} encoding methods used. The most common
8974 is @samp{uuencode}, but yEncode is also getting to be popular. If
8975 This variable is non-@code{nil}, Gnus will look in message bodies to
8976 see if it finds these encodings, and if so, it'll run them through the
8977 Gnus @sc{mime} machinery. The default is @code{t}.
8979 @item gnus-unbuttonized-mime-types
8980 @vindex gnus-unbuttonized-mime-types
8981 This is a list of regexps. @sc{mime} types that match a regexp from
8982 this list won't have @sc{mime} buttons inserted unless they aren't
8983 displayed or this variable is overridden by
8984 @code{gnus-buttonized-mime-types}. The default value is
8985 @code{(".*/.*")}. This variable is only used when
8986 @code{gnus-inhibit-mime-unbuttonizing} is nil.
8988 @item gnus-buttonized-mime-types
8989 @vindex gnus-buttonized-mime-types
8990 This is a list of regexps. @sc{mime} types that match a regexp from
8991 this list will have @sc{mime} buttons inserted unless they aren't
8992 displayed. This variable overrides
8993 @code{gnus-unbuttonized-mime-types}. The default value is @code{nil}.
8994 This variable is only used when @code{gnus-inhibit-mime-unbuttonizing}
8997 To see e.g. security buttons but no other buttons, you could set this
8998 variable to @code{("multipart/signed")} and leave
8999 @code{gnus-unbuttonized-mime-types} at the default value.
9001 @item gnus-inhibit-mime-unbuttonizing
9002 @vindex gnus-inhibit-mime-unbuttonizing
9003 If this is non-nil, then all @sc{mime} parts get buttons. The default
9004 value is @code{nil}.
9006 @item gnus-article-mime-part-function
9007 @vindex gnus-article-mime-part-function
9008 For each @sc{mime} part, this function will be called with the @sc{mime}
9009 handle as the parameter. The function is meant to be used to allow
9010 users to gather information from the article (e. g., add Vcard info to
9011 the bbdb database) or to do actions based on parts (e. g., automatically
9012 save all jpegs into some directory).
9014 Here's an example function the does the latter:
9017 (defun my-save-all-jpeg-parts (handle)
9018 (when (equal (car (mm-handle-type handle)) "image/jpeg")
9020 (insert (mm-get-part handle))
9021 (write-region (point-min) (point-max)
9022 (read-file-name "Save jpeg to: ")))))
9023 (setq gnus-article-mime-part-function
9024 'my-save-all-jpeg-parts)
9027 @vindex gnus-mime-multipart-functions
9028 @item gnus-mime-multipart-functions
9029 Alist of @sc{mime} multipart types and functions to handle them.
9031 @vindex mm-file-name-rewrite-functions
9032 @item mm-file-name-rewrite-functions
9033 List of functions used for rewriting file names of @sc{mime} parts.
9034 Each function takes a file name as input and returns a file name.
9036 Ready-made functions include@*
9037 @code{mm-file-name-delete-whitespace},
9038 @code{mm-file-name-trim-whitespace},
9039 @code{mm-file-name-collapse-whitespace}, and
9040 @code{mm-file-name-replace-whitespace}. The later uses the value of
9041 the variable @code{mm-file-name-replace-whitespace} to replace each
9042 whitespace character in a file name with that string; default value
9043 is @code{"_"} (a single underscore).
9044 @findex mm-file-name-delete-whitespace
9045 @findex mm-file-name-trim-whitespace
9046 @findex mm-file-name-collapse-whitespace
9047 @findex mm-file-name-replace-whitespace
9048 @vindex mm-file-name-replace-whitespace
9050 The standard functions @code{capitalize}, @code{downcase},
9051 @code{upcase}, and @code{upcase-initials} may be useful, too.
9053 Everybody knows that whitespace characters in file names are evil,
9054 except those who don't know. If you receive lots of attachments from
9055 such unenlightened users, you can make live easier by adding
9058 (setq mm-file-name-rewrite-functions
9059 '(mm-file-name-trim-whitespace
9060 mm-file-name-collapse-whitespace
9061 mm-file-name-replace-whitespace))
9065 to your @file{.gnus.el} file.
9074 People use different charsets, and we have @sc{mime} to let us know what
9075 charsets they use. Or rather, we wish we had. Many people use
9076 newsreaders and mailers that do not understand or use @sc{mime}, and
9077 just send out messages without saying what character sets they use. To
9078 help a bit with this, some local news hierarchies have policies that say
9079 what character set is the default. For instance, the @samp{fj}
9080 hierarchy uses @code{iso-2022-jp-2}.
9082 @vindex gnus-group-charset-alist
9083 This knowledge is encoded in the @code{gnus-group-charset-alist}
9084 variable, which is an alist of regexps (use the first item to match full
9085 group names) and default charsets to be used when reading these groups.
9087 In addition, some people do use soi-disant @sc{mime}-aware agents that
9088 aren't. These blithely mark messages as being in @code{iso-8859-1}
9089 even if they really are in @code{koi-8}. To help here, the
9090 @code{gnus-newsgroup-ignored-charsets} variable can be used. The
9091 charsets that are listed here will be ignored. The variable can be
9092 set on a group-by-group basis using the group parameters (@pxref{Group
9093 Parameters}). The default value is @code{(unknown-8bit x-unknown)},
9094 which includes values some agents insist on having in there.
9096 @vindex gnus-group-posting-charset-alist
9097 When posting, @code{gnus-group-posting-charset-alist} is used to
9098 determine which charsets should not be encoded using the @sc{mime}
9099 encodings. For instance, some hierarchies discourage using
9100 quoted-printable header encoding.
9102 This variable is an alist of regexps and permitted unencoded charsets
9103 for posting. Each element of the alist has the form @code{(}@var{test
9104 header body-list}@code{)}, where:
9108 is either a regular expression matching the newsgroup header or a
9111 is the charset which may be left unencoded in the header (@code{nil}
9112 means encode all charsets),
9114 is a list of charsets which may be encoded using 8bit content-transfer
9115 encoding in the body, or one of the special values @code{nil} (always
9116 encode using quoted-printable) or @code{t} (always use 8bit).
9123 @cindex coding system aliases
9124 @cindex preferred charset
9126 Other charset tricks that may be useful, although not Gnus-specific:
9128 If there are several @sc{mime} charsets that encode the same Emacs
9129 charset, you can choose what charset to use by saying the following:
9132 (put-charset-property 'cyrillic-iso8859-5
9133 'preferred-coding-system 'koi8-r)
9136 This means that Russian will be encoded using @code{koi8-r} instead of
9137 the default @code{iso-8859-5} @sc{mime} charset.
9139 If you want to read messages in @code{koi8-u}, you can cheat and say
9142 (define-coding-system-alias 'koi8-u 'koi8-r)
9145 This will almost do the right thing.
9147 And finally, to read charsets like @code{windows-1251}, you can say
9151 (codepage-setup 1251)
9152 (define-coding-system-alias 'windows-1251 'cp1251)
9156 @node Article Commands
9157 @section Article Commands
9164 @kindex A P (Summary)
9165 @vindex gnus-ps-print-hook
9166 @findex gnus-summary-print-article
9167 Generate and print a PostScript image of the article buffer
9168 (@code{gnus-summary-print-article}). @code{gnus-ps-print-hook} will
9169 be run just before printing the buffer. An alternative way to print
9170 article is to use Muttprint (@pxref{Saving Articles}).
9175 @node Summary Sorting
9176 @section Summary Sorting
9177 @cindex summary sorting
9179 You can have the summary buffer sorted in various ways, even though I
9180 can't really see why you'd want that.
9185 @kindex C-c C-s C-n (Summary)
9186 @findex gnus-summary-sort-by-number
9187 Sort by article number (@code{gnus-summary-sort-by-number}).
9190 @kindex C-c C-s C-a (Summary)
9191 @findex gnus-summary-sort-by-author
9192 Sort by author (@code{gnus-summary-sort-by-author}).
9195 @kindex C-c C-s C-s (Summary)
9196 @findex gnus-summary-sort-by-subject
9197 Sort by subject (@code{gnus-summary-sort-by-subject}).
9200 @kindex C-c C-s C-d (Summary)
9201 @findex gnus-summary-sort-by-date
9202 Sort by date (@code{gnus-summary-sort-by-date}).
9205 @kindex C-c C-s C-l (Summary)
9206 @findex gnus-summary-sort-by-lines
9207 Sort by lines (@code{gnus-summary-sort-by-lines}).
9210 @kindex C-c C-s C-c (Summary)
9211 @findex gnus-summary-sort-by-chars
9212 Sort by article length (@code{gnus-summary-sort-by-chars}).
9215 @kindex C-c C-s C-i (Summary)
9216 @findex gnus-summary-sort-by-score
9217 Sort by score (@code{gnus-summary-sort-by-score}).
9220 @kindex C-c C-s C-r (Summary)
9221 @findex gnus-summary-sort-by-random
9222 Randomize (@code{gnus-summary-sort-by-random}).
9225 @kindex C-c C-s C-o (Summary)
9226 @findex gnus-summary-sort-by-original
9227 Sort using the default sorting method
9228 (@code{gnus-summary-sort-by-original}).
9231 These functions will work both when you use threading and when you don't
9232 use threading. In the latter case, all summary lines will be sorted,
9233 line by line. In the former case, sorting will be done on a
9234 root-by-root basis, which might not be what you were looking for. To
9235 toggle whether to use threading, type @kbd{T T} (@pxref{Thread
9239 @node Finding the Parent
9240 @section Finding the Parent
9241 @cindex parent articles
9242 @cindex referring articles
9247 @findex gnus-summary-refer-parent-article
9248 If you'd like to read the parent of the current article, and it is not
9249 displayed in the summary buffer, you might still be able to. That is,
9250 if the current group is fetched by @sc{nntp}, the parent hasn't expired
9251 and the @code{References} in the current article are not mangled, you
9252 can just press @kbd{^} or @kbd{A r}
9253 (@code{gnus-summary-refer-parent-article}). If everything goes well,
9254 you'll get the parent. If the parent is already displayed in the
9255 summary buffer, point will just move to this article.
9257 If given a positive numerical prefix, fetch that many articles back into
9258 the ancestry. If given a negative numerical prefix, fetch just that
9259 ancestor. So if you say @kbd{3 ^}, gnus will fetch the parent, the
9260 grandparent and the grandgrandparent of the current article. If you say
9261 @kbd{-3 ^}, gnus will only fetch the grandgrandparent of the current
9265 @findex gnus-summary-refer-references
9266 @kindex A R (Summary)
9267 Fetch all articles mentioned in the @code{References} header of the
9268 article (@code{gnus-summary-refer-references}).
9271 @findex gnus-summary-refer-thread
9272 @kindex A T (Summary)
9273 Display the full thread where the current article appears
9274 (@code{gnus-summary-refer-thread}). This command has to fetch all the
9275 headers in the current group to work, so it usually takes a while. If
9276 you do it often, you may consider setting @code{gnus-fetch-old-headers}
9277 to @code{invisible} (@pxref{Filling In Threads}). This won't have any
9278 visible effects normally, but it'll make this command work a whole lot
9279 faster. Of course, it'll make group entry somewhat slow.
9281 @vindex gnus-refer-thread-limit
9282 The @code{gnus-refer-thread-limit} variable says how many old (i. e.,
9283 articles before the first displayed in the current group) headers to
9284 fetch when doing this command. The default is 200. If @code{t}, all
9285 the available headers will be fetched. This variable can be overridden
9286 by giving the @kbd{A T} command a numerical prefix.
9289 @findex gnus-summary-refer-article
9290 @kindex M-^ (Summary)
9292 @cindex fetching by Message-ID
9293 You can also ask the @sc{nntp} server for an arbitrary article, no
9294 matter what group it belongs to. @kbd{M-^}
9295 (@code{gnus-summary-refer-article}) will ask you for a
9296 @code{Message-ID}, which is one of those long, hard-to-read thingies
9297 that look something like @samp{<38o6up$6f2@@hymir.ifi.uio.no>}. You
9298 have to get it all exactly right. No fuzzy searches, I'm afraid.
9301 The current select method will be used when fetching by
9302 @code{Message-ID} from non-news select method, but you can override this
9303 by giving this command a prefix.
9305 @vindex gnus-refer-article-method
9306 If the group you are reading is located on a back end that does not
9307 support fetching by @code{Message-ID} very well (like @code{nnspool}),
9308 you can set @code{gnus-refer-article-method} to an @sc{nntp} method. It
9309 would, perhaps, be best if the @sc{nntp} server you consult is the one
9310 updating the spool you are reading from, but that's not really
9313 It can also be a list of select methods, as well as the special symbol
9314 @code{current}, which means to use the current select method. If it
9315 is a list, Gnus will try all the methods in the list until it finds a
9318 Here's an example setting that will first try the current method, and
9319 then ask Google if that fails:
9322 (setq gnus-refer-article-method
9324 (nnweb "google" (nnweb-type google))))
9327 Most of the mail back ends support fetching by @code{Message-ID}, but
9328 do not do a particularly excellent job at it. That is, @code{nnmbox},
9329 @code{nnbabyl}, and @code{nnmaildir} are able to locate articles from
9330 any groups, while @code{nnml}, @code{nnfolder}, and @code{nnimap} are
9331 only able to locate articles that have been posted to the current group.
9332 (Anything else would be too time consuming.) @code{nnmh} does not
9333 support this at all.
9336 @node Alternative Approaches
9337 @section Alternative Approaches
9339 Different people like to read news using different methods. This being
9340 gnus, we offer a small selection of minor modes for the summary buffers.
9343 * Pick and Read:: First mark articles and then read them.
9344 * Binary Groups:: Auto-decode all articles.
9349 @subsection Pick and Read
9350 @cindex pick and read
9352 Some newsreaders (like @code{nn} and, uhm, @code{Netnews} on VM/CMS) use
9353 a two-phased reading interface. The user first marks in a summary
9354 buffer the articles she wants to read. Then she starts reading the
9355 articles with just an article buffer displayed.
9357 @findex gnus-pick-mode
9358 @kindex M-x gnus-pick-mode
9359 Gnus provides a summary buffer minor mode that allows
9360 this---@code{gnus-pick-mode}. This basically means that a few process
9361 mark commands become one-keystroke commands to allow easy marking, and
9362 it provides one additional command for switching to the summary buffer.
9364 Here are the available keystrokes when using pick mode:
9369 @findex gnus-pick-article-or-thread
9370 Pick the article or thread on the current line
9371 (@code{gnus-pick-article-or-thread}). If the variable
9372 @code{gnus-thread-hide-subtree} is true, then this key selects the
9373 entire thread when used at the first article of the thread. Otherwise,
9374 it selects just the article. If given a numerical prefix, go to that
9375 thread or article and pick it. (The line number is normally displayed
9376 at the beginning of the summary pick lines.)
9379 @kindex SPACE (Pick)
9380 @findex gnus-pick-next-page
9381 Scroll the summary buffer up one page (@code{gnus-pick-next-page}). If
9382 at the end of the buffer, start reading the picked articles.
9386 @findex gnus-pick-unmark-article-or-thread.
9387 Unpick the thread or article
9388 (@code{gnus-pick-unmark-article-or-thread}). If the variable
9389 @code{gnus-thread-hide-subtree} is true, then this key unpicks the
9390 thread if used at the first article of the thread. Otherwise it unpicks
9391 just the article. You can give this key a numerical prefix to unpick
9392 the thread or article at that line.
9396 @findex gnus-pick-start-reading
9397 @vindex gnus-pick-display-summary
9398 Start reading the picked articles (@code{gnus-pick-start-reading}). If
9399 given a prefix, mark all unpicked articles as read first. If
9400 @code{gnus-pick-display-summary} is non-@code{nil}, the summary buffer
9401 will still be visible when you are reading.
9405 All the normal summary mode commands are still available in the
9406 pick-mode, with the exception of @kbd{u}. However @kbd{!} is available
9407 which is mapped to the same function
9408 @code{gnus-summary-tick-article-forward}.
9410 If this sounds like a good idea to you, you could say:
9413 (add-hook 'gnus-summary-mode-hook 'gnus-pick-mode)
9416 @vindex gnus-pick-mode-hook
9417 @code{gnus-pick-mode-hook} is run in pick minor mode buffers.
9419 @vindex gnus-mark-unpicked-articles-as-read
9420 If @code{gnus-mark-unpicked-articles-as-read} is non-@code{nil}, mark
9421 all unpicked articles as read. The default is @code{nil}.
9423 @vindex gnus-summary-pick-line-format
9424 The summary line format in pick mode is slightly different from the
9425 standard format. At the beginning of each line the line number is
9426 displayed. The pick mode line format is controlled by the
9427 @code{gnus-summary-pick-line-format} variable (@pxref{Formatting
9428 Variables}). It accepts the same format specs that
9429 @code{gnus-summary-line-format} does (@pxref{Summary Buffer Lines}).
9433 @subsection Binary Groups
9434 @cindex binary groups
9436 @findex gnus-binary-mode
9437 @kindex M-x gnus-binary-mode
9438 If you spend much time in binary groups, you may grow tired of hitting
9439 @kbd{X u}, @kbd{n}, @kbd{RET} all the time. @kbd{M-x gnus-binary-mode}
9440 is a minor mode for summary buffers that makes all ordinary Gnus article
9441 selection functions uudecode series of articles and display the result
9442 instead of just displaying the articles the normal way.
9445 @findex gnus-binary-show-article
9446 The only way, in fact, to see the actual articles is the @kbd{g}
9447 command, when you have turned on this mode
9448 (@code{gnus-binary-show-article}).
9450 @vindex gnus-binary-mode-hook
9451 @code{gnus-binary-mode-hook} is called in binary minor mode buffers.
9455 @section Tree Display
9458 @vindex gnus-use-trees
9459 If you don't like the normal gnus summary display, you might try setting
9460 @code{gnus-use-trees} to @code{t}. This will create (by default) an
9461 additional @dfn{tree buffer}. You can execute all summary mode commands
9464 There are a few variables to customize the tree display, of course:
9467 @item gnus-tree-mode-hook
9468 @vindex gnus-tree-mode-hook
9469 A hook called in all tree mode buffers.
9471 @item gnus-tree-mode-line-format
9472 @vindex gnus-tree-mode-line-format
9473 A format string for the mode bar in the tree mode buffers (@pxref{Mode
9474 Line Formatting}). The default is @samp{Gnus: %%b %S %Z}. For a list
9475 of valid specs, @pxref{Summary Buffer Mode Line}.
9477 @item gnus-selected-tree-face
9478 @vindex gnus-selected-tree-face
9479 Face used for highlighting the selected article in the tree buffer. The
9480 default is @code{modeline}.
9482 @item gnus-tree-line-format
9483 @vindex gnus-tree-line-format
9484 A format string for the tree nodes. The name is a bit of a misnomer,
9485 though---it doesn't define a line, but just the node. The default value
9486 is @samp{%(%[%3,3n%]%)}, which displays the first three characters of
9487 the name of the poster. It is vital that all nodes are of the same
9488 length, so you @emph{must} use @samp{%4,4n}-like specifiers.
9494 The name of the poster.
9496 The @code{From} header.
9498 The number of the article.
9500 The opening bracket.
9502 The closing bracket.
9507 @xref{Formatting Variables}.
9509 Variables related to the display are:
9512 @item gnus-tree-brackets
9513 @vindex gnus-tree-brackets
9514 This is used for differentiating between ``real'' articles and
9515 ``sparse'' articles. The format is @code{((@var{real-open} . @var{real-close})
9516 (@var{sparse-open} . @var{sparse-close}) (@var{dummy-open} . @var{dummy-close}))}, and the
9517 default is @code{((?[ . ?]) (?( . ?)) (?@{ . ?@}) (?< . ?>))}.
9519 @item gnus-tree-parent-child-edges
9520 @vindex gnus-tree-parent-child-edges
9521 This is a list that contains the characters used for connecting parent
9522 nodes to their children. The default is @code{(?- ?\\ ?|)}.
9526 @item gnus-tree-minimize-window
9527 @vindex gnus-tree-minimize-window
9528 If this variable is non-@code{nil}, gnus will try to keep the tree
9529 buffer as small as possible to allow more room for the other gnus
9530 windows. If this variable is a number, the tree buffer will never be
9531 higher than that number. The default is @code{t}. Note that if you
9532 have several windows displayed side-by-side in a frame and the tree
9533 buffer is one of these, minimizing the tree window will also resize all
9534 other windows displayed next to it.
9536 You may also wish to add the following hook to keep the window minimized
9540 (add-hook 'gnus-configure-windows-hook
9541 'gnus-tree-perhaps-minimize)
9544 @item gnus-generate-tree-function
9545 @vindex gnus-generate-tree-function
9546 @findex gnus-generate-horizontal-tree
9547 @findex gnus-generate-vertical-tree
9548 The function that actually generates the thread tree. Two predefined
9549 functions are available: @code{gnus-generate-horizontal-tree} and
9550 @code{gnus-generate-vertical-tree} (which is the default).
9554 Here's an example from a horizontal tree buffer:
9557 @{***@}-(***)-[odd]-[Gun]
9567 Here's the same thread displayed in a vertical tree buffer:
9571 |--------------------------\-----\-----\
9572 (***) [Bjo] [Gun] [Gun]
9574 [odd] [Jan] [odd] (***) [Jor]
9576 [Gun] [Eri] [Eri] [odd]
9581 If you're using horizontal trees, it might be nice to display the trees
9582 side-by-side with the summary buffer. You could add something like the
9583 following to your @file{.gnus.el} file:
9586 (setq gnus-use-trees t
9587 gnus-generate-tree-function 'gnus-generate-horizontal-tree
9588 gnus-tree-minimize-window nil)
9589 (gnus-add-configuration
9593 (summary 0.75 point)
9598 @xref{Window Layout}.
9601 @node Mail Group Commands
9602 @section Mail Group Commands
9603 @cindex mail group commands
9605 Some commands only make sense in mail groups. If these commands are
9606 invalid in the current group, they will raise a hell and let you know.
9608 All these commands (except the expiry and edit commands) use the
9609 process/prefix convention (@pxref{Process/Prefix}).
9614 @kindex B e (Summary)
9615 @findex gnus-summary-expire-articles
9616 Run all expirable articles in the current group through the expiry
9617 process (@code{gnus-summary-expire-articles}). That is, delete all
9618 expirable articles in the group that have been around for a while.
9619 (@pxref{Expiring Mail}).
9622 @kindex B C-M-e (Summary)
9623 @findex gnus-summary-expire-articles-now
9624 Delete all the expirable articles in the group
9625 (@code{gnus-summary-expire-articles-now}). This means that @strong{all}
9626 articles eligible for expiry in the current group will
9627 disappear forever into that big @file{/dev/null} in the sky.
9630 @kindex B DEL (Summary)
9631 @findex gnus-summary-delete-article
9632 @c @icon{gnus-summary-mail-delete}
9633 Delete the mail article. This is ``delete'' as in ``delete it from your
9634 disk forever and ever, never to return again.'' Use with caution.
9635 (@code{gnus-summary-delete-article}).
9638 @kindex B m (Summary)
9640 @findex gnus-summary-move-article
9641 @vindex gnus-preserve-marks
9642 Move the article from one mail group to another
9643 (@code{gnus-summary-move-article}). Marks will be preserved if
9644 @code{gnus-preserve-marks} is non-@code{nil} (which is the default).
9647 @kindex B c (Summary)
9649 @findex gnus-summary-copy-article
9650 @c @icon{gnus-summary-mail-copy}
9651 Copy the article from one group (mail group or not) to a mail group
9652 (@code{gnus-summary-copy-article}). Marks will be preserved if
9653 @code{gnus-preserve-marks} is non-@code{nil} (which is the default).
9656 @kindex B B (Summary)
9657 @cindex crosspost mail
9658 @findex gnus-summary-crosspost-article
9659 Crosspost the current article to some other group
9660 (@code{gnus-summary-crosspost-article}). This will create a new copy of
9661 the article in the other group, and the Xref headers of the article will
9662 be properly updated.
9665 @kindex B i (Summary)
9666 @findex gnus-summary-import-article
9667 Import an arbitrary file into the current mail newsgroup
9668 (@code{gnus-summary-import-article}). You will be prompted for a file
9669 name, a @code{From} header and a @code{Subject} header.
9672 @kindex B I (Summary)
9673 @findex gnus-summary-create-article
9674 Create an empty article in the current mail newsgroups
9675 (@code{gnus-summary-create-article}). You will be prompted for a
9676 @code{From} header and a @code{Subject} header.
9679 @kindex B r (Summary)
9680 @findex gnus-summary-respool-article
9681 Respool the mail article (@code{gnus-summary-respool-article}).
9682 @code{gnus-summary-respool-default-method} will be used as the default
9683 select method when respooling. This variable is @code{nil} by default,
9684 which means that the current group select method will be used instead.
9685 Marks will be preserved if @code{gnus-preserve-marks} is non-@code{nil}
9686 (which is the default).
9690 @kindex B w (Summary)
9692 @findex gnus-summary-edit-article
9693 @kindex C-c C-c (Article)
9694 @findex gnus-summary-edit-article-done
9695 Edit the current article (@code{gnus-summary-edit-article}). To finish
9696 editing and make the changes permanent, type @kbd{C-c C-c}
9697 (@code{gnus-summary-edit-article-done}). If you give a prefix to the
9698 @kbd{C-c C-c} command, gnus won't re-highlight the article.
9701 @kindex B q (Summary)
9702 @findex gnus-summary-respool-query
9703 If you want to re-spool an article, you might be curious as to what group
9704 the article will end up in before you do the re-spooling. This command
9705 will tell you (@code{gnus-summary-respool-query}).
9708 @kindex B t (Summary)
9709 @findex gnus-summary-respool-trace
9710 Similarly, this command will display all fancy splitting patterns used
9711 when respooling, if any (@code{gnus-summary-respool-trace}).
9714 @kindex B p (Summary)
9715 @findex gnus-summary-article-posted-p
9716 Some people have a tendency to send you "courtesy" copies when they
9717 follow up to articles you have posted. These usually have a
9718 @code{Newsgroups} header in them, but not always. This command
9719 (@code{gnus-summary-article-posted-p}) will try to fetch the current
9720 article from your news server (or rather, from
9721 @code{gnus-refer-article-method} or @code{gnus-select-method}) and will
9722 report back whether it found the article or not. Even if it says that
9723 it didn't find the article, it may have been posted anyway---mail
9724 propagation is much faster than news propagation, and the news copy may
9725 just not have arrived yet.
9728 @kindex K E (Summary)
9729 @findex gnus-article-encrypt-body
9730 @vindex gnus-article-encrypt-protocol
9731 Encrypt the body of an article (@code{gnus-article-encrypt-body}).
9732 The body is encrypted with the encryption protocol specified by the
9733 variable @code{gnus-article-encrypt-protocol}.
9737 @vindex gnus-move-split-methods
9738 @cindex moving articles
9739 If you move (or copy) articles regularly, you might wish to have gnus
9740 suggest where to put the articles. @code{gnus-move-split-methods} is a
9741 variable that uses the same syntax as @code{gnus-split-methods}
9742 (@pxref{Saving Articles}). You may customize that variable to create
9743 suggestions you find reasonable. (Note that
9744 @code{gnus-move-split-methods} uses group names where
9745 @code{gnus-split-methods} uses file names.)
9748 (setq gnus-move-split-methods
9749 '(("^From:.*Lars Magne" "nnml:junk")
9750 ("^Subject:.*gnus" "nnfolder:important")
9751 (".*" "nnml:misc")))
9755 @node Various Summary Stuff
9756 @section Various Summary Stuff
9759 * Summary Group Information:: Information oriented commands.
9760 * Searching for Articles:: Multiple article commands.
9761 * Summary Generation Commands::
9762 * Really Various Summary Commands:: Those pesky non-conformant commands.
9766 @vindex gnus-summary-mode-hook
9767 @item gnus-summary-mode-hook
9768 This hook is called when creating a summary mode buffer.
9770 @vindex gnus-summary-generate-hook
9771 @item gnus-summary-generate-hook
9772 This is called as the last thing before doing the threading and the
9773 generation of the summary buffer. It's quite convenient for customizing
9774 the threading variables based on what data the newsgroup has. This hook
9775 is called from the summary buffer after most summary buffer variables
9778 @vindex gnus-summary-prepare-hook
9779 @item gnus-summary-prepare-hook
9780 It is called after the summary buffer has been generated. You might use
9781 it to, for instance, highlight lines or modify the look of the buffer in
9782 some other ungodly manner. I don't care.
9784 @vindex gnus-summary-prepared-hook
9785 @item gnus-summary-prepared-hook
9786 A hook called as the very last thing after the summary buffer has been
9789 @vindex gnus-summary-ignore-duplicates
9790 @item gnus-summary-ignore-duplicates
9791 When gnus discovers two articles that have the same @code{Message-ID},
9792 it has to do something drastic. No articles are allowed to have the
9793 same @code{Message-ID}, but this may happen when reading mail from some
9794 sources. Gnus allows you to customize what happens with this variable.
9795 If it is @code{nil} (which is the default), gnus will rename the
9796 @code{Message-ID} (for display purposes only) and display the article as
9797 any other article. If this variable is @code{t}, it won't display the
9798 article---it'll be as if it never existed.
9800 @vindex gnus-alter-articles-to-read-function
9801 @item gnus-alter-articles-to-read-function
9802 This function, which takes two parameters (the group name and the list
9803 of articles to be selected), is called to allow the user to alter the
9804 list of articles to be selected.
9806 For instance, the following function adds the list of cached articles to
9807 the list in one particular group:
9810 (defun my-add-cached-articles (group articles)
9811 (if (string= group "some.group")
9812 (append gnus-newsgroup-cached articles)
9816 @vindex gnus-newsgroup-variables
9817 @item gnus-newsgroup-variables
9818 A list of newsgroup (summary buffer) local variables, or cons of
9819 variables and their default values (when the default values are not
9820 nil), that should be made global while the summary buffer is active.
9821 These variables can be used to set variables in the group parameters
9822 while still allowing them to affect operations done in other
9823 buffers. For example:
9826 (setq gnus-newsgroup-variables
9827 '(message-use-followup-to
9828 (gnus-visible-headers .
9829 "^From:\\|^Newsgroups:\\|^Subject:\\|^Date:\\|^To:")))
9835 @node Summary Group Information
9836 @subsection Summary Group Information
9841 @kindex H f (Summary)
9842 @findex gnus-summary-fetch-faq
9843 @vindex gnus-group-faq-directory
9844 Try to fetch the FAQ (list of frequently asked questions) for the
9845 current group (@code{gnus-summary-fetch-faq}). Gnus will try to get the
9846 FAQ from @code{gnus-group-faq-directory}, which is usually a directory
9847 on a remote machine. This variable can also be a list of directories.
9848 In that case, giving a prefix to this command will allow you to choose
9849 between the various sites. @code{ange-ftp} or @code{efs} will probably
9850 be used for fetching the file.
9853 @kindex H d (Summary)
9854 @findex gnus-summary-describe-group
9855 Give a brief description of the current group
9856 (@code{gnus-summary-describe-group}). If given a prefix, force
9857 rereading the description from the server.
9860 @kindex H h (Summary)
9861 @findex gnus-summary-describe-briefly
9862 Give an extremely brief description of the most important summary
9863 keystrokes (@code{gnus-summary-describe-briefly}).
9866 @kindex H i (Summary)
9867 @findex gnus-info-find-node
9868 Go to the gnus info node (@code{gnus-info-find-node}).
9872 @node Searching for Articles
9873 @subsection Searching for Articles
9878 @kindex M-s (Summary)
9879 @findex gnus-summary-search-article-forward
9880 Search through all subsequent (raw) articles for a regexp
9881 (@code{gnus-summary-search-article-forward}).
9884 @kindex M-r (Summary)
9885 @findex gnus-summary-search-article-backward
9886 Search through all previous (raw) articles for a regexp
9887 (@code{gnus-summary-search-article-backward}).
9891 @findex gnus-summary-execute-command
9892 This command will prompt you for a header, a regular expression to match
9893 on this field, and a command to be executed if the match is made
9894 (@code{gnus-summary-execute-command}). If the header is an empty
9895 string, the match is done on the entire article. If given a prefix,
9896 search backward instead.
9898 For instance, @kbd{& RET some.*string #} will put the process mark on
9899 all articles that have heads or bodies that match @samp{some.*string}.
9902 @kindex M-& (Summary)
9903 @findex gnus-summary-universal-argument
9904 Perform any operation on all articles that have been marked with
9905 the process mark (@code{gnus-summary-universal-argument}).
9908 @node Summary Generation Commands
9909 @subsection Summary Generation Commands
9914 @kindex Y g (Summary)
9915 @findex gnus-summary-prepare
9916 Regenerate the current summary buffer (@code{gnus-summary-prepare}).
9919 @kindex Y c (Summary)
9920 @findex gnus-summary-insert-cached-articles
9921 Pull all cached articles (for the current group) into the summary buffer
9922 (@code{gnus-summary-insert-cached-articles}).
9925 @kindex Y d (Summary)
9926 @findex gnus-summary-insert-dormant-articles
9927 Pull all dormant articles (for the current group) into the summary buffer
9928 (@code{gnus-summary-insert-dormant-articles}).
9933 @node Really Various Summary Commands
9934 @subsection Really Various Summary Commands
9940 @kindex C-d (Summary)
9941 @kindex A D (Summary)
9942 @findex gnus-summary-enter-digest-group
9943 If the current article is a collection of other articles (for instance,
9944 a digest), you might use this command to enter a group based on the that
9945 article (@code{gnus-summary-enter-digest-group}). Gnus will try to
9946 guess what article type is currently displayed unless you give a prefix
9947 to this command, which forces a ``digest'' interpretation. Basically,
9948 whenever you see a message that is a collection of other messages of
9949 some format, you @kbd{C-d} and read these messages in a more convenient
9953 @kindex C-M-d (Summary)
9954 @findex gnus-summary-read-document
9955 This command is very similar to the one above, but lets you gather
9956 several documents into one biiig group
9957 (@code{gnus-summary-read-document}). It does this by opening several
9958 @code{nndoc} groups for each document, and then opening an
9959 @code{nnvirtual} group on top of these @code{nndoc} groups. This
9960 command understands the process/prefix convention
9961 (@pxref{Process/Prefix}).
9964 @kindex C-t (Summary)
9965 @findex gnus-summary-toggle-truncation
9966 Toggle truncation of summary lines
9967 (@code{gnus-summary-toggle-truncation}). This will probably confuse the
9968 line centering function in the summary buffer, so it's not a good idea
9969 to have truncation switched off while reading articles.
9973 @findex gnus-summary-expand-window
9974 Expand the summary buffer window (@code{gnus-summary-expand-window}).
9975 If given a prefix, force an @code{article} window configuration.
9978 @kindex C-M-e (Summary)
9979 @findex gnus-summary-edit-parameters
9980 Edit the group parameters (@pxref{Group Parameters}) of the current
9981 group (@code{gnus-summary-edit-parameters}).
9984 @kindex C-M-a (Summary)
9985 @findex gnus-summary-customize-parameters
9986 Customize the group parameters (@pxref{Group Parameters}) of the current
9987 group (@code{gnus-summary-customize-parameters}).
9992 @node Exiting the Summary Buffer
9993 @section Exiting the Summary Buffer
9994 @cindex summary exit
9995 @cindex exiting groups
9997 Exiting from the summary buffer will normally update all info on the
9998 group and return you to the group buffer.
10004 @kindex Z Z (Summary)
10005 @kindex q (Summary)
10006 @findex gnus-summary-exit
10007 @vindex gnus-summary-exit-hook
10008 @vindex gnus-summary-prepare-exit-hook
10009 @c @icon{gnus-summary-exit}
10010 Exit the current group and update all information on the group
10011 (@code{gnus-summary-exit}). @code{gnus-summary-prepare-exit-hook} is
10012 called before doing much of the exiting, which calls
10013 @code{gnus-summary-expire-articles} by default.
10014 @code{gnus-summary-exit-hook} is called after finishing the exit
10015 process. @code{gnus-group-no-more-groups-hook} is run when returning to
10016 group mode having no more (unread) groups.
10020 @kindex Z E (Summary)
10021 @kindex Q (Summary)
10022 @findex gnus-summary-exit-no-update
10023 Exit the current group without updating any information on the group
10024 (@code{gnus-summary-exit-no-update}).
10028 @kindex Z c (Summary)
10029 @kindex c (Summary)
10030 @findex gnus-summary-catchup-and-exit
10031 @c @icon{gnus-summary-catchup-and-exit}
10032 Mark all unticked articles in the group as read and then exit
10033 (@code{gnus-summary-catchup-and-exit}).
10036 @kindex Z C (Summary)
10037 @findex gnus-summary-catchup-all-and-exit
10038 Mark all articles, even the ticked ones, as read and then exit
10039 (@code{gnus-summary-catchup-all-and-exit}).
10042 @kindex Z n (Summary)
10043 @findex gnus-summary-catchup-and-goto-next-group
10044 Mark all articles as read and go to the next group
10045 (@code{gnus-summary-catchup-and-goto-next-group}).
10048 @kindex Z R (Summary)
10049 @findex gnus-summary-reselect-current-group
10050 Exit this group, and then enter it again
10051 (@code{gnus-summary-reselect-current-group}). If given a prefix, select
10052 all articles, both read and unread.
10056 @kindex Z G (Summary)
10057 @kindex M-g (Summary)
10058 @findex gnus-summary-rescan-group
10059 @c @icon{gnus-summary-mail-get}
10060 Exit the group, check for new articles in the group, and select the
10061 group (@code{gnus-summary-rescan-group}). If given a prefix, select all
10062 articles, both read and unread.
10065 @kindex Z N (Summary)
10066 @findex gnus-summary-next-group
10067 Exit the group and go to the next group
10068 (@code{gnus-summary-next-group}).
10071 @kindex Z P (Summary)
10072 @findex gnus-summary-prev-group
10073 Exit the group and go to the previous group
10074 (@code{gnus-summary-prev-group}).
10077 @kindex Z s (Summary)
10078 @findex gnus-summary-save-newsrc
10079 Save the current number of read/marked articles in the dribble buffer
10080 and then save the dribble buffer (@code{gnus-summary-save-newsrc}). If
10081 given a prefix, also save the @file{.newsrc} file(s). Using this
10082 command will make exit without updating (the @kbd{Q} command) worthless.
10085 @vindex gnus-exit-group-hook
10086 @code{gnus-exit-group-hook} is called when you exit the current group
10087 with an ``updating'' exit. For instance @kbd{Q}
10088 (@code{gnus-summary-exit-no-update}) does not call this hook.
10090 @findex gnus-summary-wake-up-the-dead
10091 @findex gnus-dead-summary-mode
10092 @vindex gnus-kill-summary-on-exit
10093 If you're in the habit of exiting groups, and then changing your mind
10094 about it, you might set @code{gnus-kill-summary-on-exit} to @code{nil}.
10095 If you do that, gnus won't kill the summary buffer when you exit it.
10096 (Quelle surprise!) Instead it will change the name of the buffer to
10097 something like @samp{*Dead Summary ... *} and install a minor mode
10098 called @code{gnus-dead-summary-mode}. Now, if you switch back to this
10099 buffer, you'll find that all keys are mapped to a function called
10100 @code{gnus-summary-wake-up-the-dead}. So tapping any keys in a dead
10101 summary buffer will result in a live, normal summary buffer.
10103 There will never be more than one dead summary buffer at any one time.
10105 @vindex gnus-use-cross-reference
10106 The data on the current group will be updated (which articles you have
10107 read, which articles you have replied to, etc.) when you exit the
10108 summary buffer. If the @code{gnus-use-cross-reference} variable is
10109 @code{t} (which is the default), articles that are cross-referenced to
10110 this group and are marked as read, will also be marked as read in the
10111 other subscribed groups they were cross-posted to. If this variable is
10112 neither @code{nil} nor @code{t}, the article will be marked as read in
10113 both subscribed and unsubscribed groups (@pxref{Crosspost Handling}).
10116 @node Crosspost Handling
10117 @section Crosspost Handling
10121 Marking cross-posted articles as read ensures that you'll never have to
10122 read the same article more than once. Unless, of course, somebody has
10123 posted it to several groups separately. Posting the same article to
10124 several groups (not cross-posting) is called @dfn{spamming}, and you are
10125 by law required to send nasty-grams to anyone who perpetrates such a
10126 heinous crime. You may want to try NoCeM handling to filter out spam
10129 Remember: Cross-posting is kinda ok, but posting the same article
10130 separately to several groups is not. Massive cross-posting (aka.
10131 @dfn{velveeta}) is to be avoided at all costs, and you can even use the
10132 @code{gnus-summary-mail-crosspost-complaint} command to complain about
10133 excessive crossposting (@pxref{Summary Mail Commands}).
10135 @cindex cross-posting
10138 One thing that may cause Gnus to not do the cross-posting thing
10139 correctly is if you use an @sc{nntp} server that supports @sc{xover}
10140 (which is very nice, because it speeds things up considerably) which
10141 does not include the @code{Xref} header in its @sc{nov} lines. This is
10142 Evil, but all too common, alas, alack. Gnus tries to Do The Right Thing
10143 even with @sc{xover} by registering the @code{Xref} lines of all
10144 articles you actually read, but if you kill the articles, or just mark
10145 them as read without reading them, Gnus will not get a chance to snoop
10146 the @code{Xref} lines out of these articles, and will be unable to use
10147 the cross reference mechanism.
10149 @cindex LIST overview.fmt
10150 @cindex overview.fmt
10151 To check whether your @sc{nntp} server includes the @code{Xref} header
10152 in its overview files, try @samp{telnet your.nntp.server nntp},
10153 @samp{MODE READER} on @code{inn} servers, and then say @samp{LIST
10154 overview.fmt}. This may not work, but if it does, and the last line you
10155 get does not read @samp{Xref:full}, then you should shout and whine at
10156 your news admin until she includes the @code{Xref} header in the
10159 @vindex gnus-nov-is-evil
10160 If you want Gnus to get the @code{Xref}s right all the time, you have to
10161 set @code{gnus-nov-is-evil} to @code{t}, which slows things down
10166 For an alternative approach, @pxref{Duplicate Suppression}.
10169 @node Duplicate Suppression
10170 @section Duplicate Suppression
10172 By default, gnus tries to make sure that you don't have to read the same
10173 article more than once by utilizing the crossposting mechanism
10174 (@pxref{Crosspost Handling}). However, that simple and efficient
10175 approach may not work satisfactory for some users for various
10180 The @sc{nntp} server may fail to generate the @code{Xref} header. This
10181 is evil and not very common.
10184 The @sc{nntp} server may fail to include the @code{Xref} header in the
10185 @file{.overview} data bases. This is evil and all too common, alas.
10188 You may be reading the same group (or several related groups) from
10189 different @sc{nntp} servers.
10192 You may be getting mail that duplicates articles posted to groups.
10195 I'm sure there are other situations where @code{Xref} handling fails as
10196 well, but these four are the most common situations.
10198 If, and only if, @code{Xref} handling fails for you, then you may
10199 consider switching on @dfn{duplicate suppression}. If you do so, Gnus
10200 will remember the @code{Message-ID}s of all articles you have read or
10201 otherwise marked as read, and then, as if by magic, mark them as read
10202 all subsequent times you see them---in @emph{all} groups. Using this
10203 mechanism is quite likely to be somewhat inefficient, but not overly
10204 so. It's certainly preferable to reading the same articles more than
10207 Duplicate suppression is not a very subtle instrument. It's more like a
10208 sledge hammer than anything else. It works in a very simple
10209 fashion---if you have marked an article as read, it adds this Message-ID
10210 to a cache. The next time it sees this Message-ID, it will mark the
10211 article as read with the @samp{M} mark. It doesn't care what group it
10212 saw the article in.
10215 @item gnus-suppress-duplicates
10216 @vindex gnus-suppress-duplicates
10217 If non-@code{nil}, suppress duplicates.
10219 @item gnus-save-duplicate-list
10220 @vindex gnus-save-duplicate-list
10221 If non-@code{nil}, save the list of duplicates to a file. This will
10222 make startup and shutdown take longer, so the default is @code{nil}.
10223 However, this means that only duplicate articles read in a single gnus
10224 session are suppressed.
10226 @item gnus-duplicate-list-length
10227 @vindex gnus-duplicate-list-length
10228 This variable says how many @code{Message-ID}s to keep in the duplicate
10229 suppression list. The default is 10000.
10231 @item gnus-duplicate-file
10232 @vindex gnus-duplicate-file
10233 The name of the file to store the duplicate suppression list in. The
10234 default is @file{~/News/suppression}.
10237 If you have a tendency to stop and start gnus often, setting
10238 @code{gnus-save-duplicate-list} to @code{t} is probably a good idea. If
10239 you leave gnus running for weeks on end, you may have it @code{nil}. On
10240 the other hand, saving the list makes startup and shutdown much slower,
10241 so that means that if you stop and start gnus often, you should set
10242 @code{gnus-save-duplicate-list} to @code{nil}. Uhm. I'll leave this up
10243 to you to figure out, I think.
10248 Gnus is able to verify signed messages or decrypt encrypted messages.
10249 The formats that are supported are PGP, @sc{pgp/mime} and @sc{s/mime},
10250 however you need some external programs to get things to work:
10254 To handle PGP messages, you have to install mailcrypt or gpg.el as
10255 well as a OpenPGP implementation (such as GnuPG).
10258 To handle @sc{s/mime} message, you need to install OpenSSL. OpenSSL 0.9.6
10259 or newer is recommended.
10263 More information on how to set things up can be found in the message
10264 manual (@pxref{Security, ,Security, message, Message Manual}).
10267 @item mm-verify-option
10268 @vindex mm-verify-option
10269 Option of verifying signed parts. @code{never}, not verify;
10270 @code{always}, always verify; @code{known}, only verify known
10271 protocols. Otherwise, ask user.
10273 @item mm-decrypt-option
10274 @vindex mm-decrypt-option
10275 Option of decrypting encrypted parts. @code{never}, no decryption;
10276 @code{always}, always decrypt; @code{known}, only decrypt known
10277 protocols. Otherwise, ask user.
10282 @section Mailing List
10284 @kindex A M (summary)
10285 @findex gnus-mailing-list-insinuate
10286 Gnus understands some mailing list fields of RFC 2369. To enable it,
10287 either add a `to-list' group parameter (@pxref{Group Parameters}),
10288 possibly using @kbd{A M} (@code{gnus-mailing-list-insinuate}) in the
10289 summary buffer, or say:
10292 (add-hook 'gnus-summary-mode-hook 'turn-on-gnus-mailing-list-mode)
10295 That enables the following commands to the summary buffer:
10300 @kindex C-c C-n h (Summary)
10301 @findex gnus-mailing-list-help
10302 Send a message to fetch mailing list help, if List-Help field exists.
10305 @kindex C-c C-n s (Summary)
10306 @findex gnus-mailing-list-subscribe
10307 Send a message to subscribe the mailing list, if List-Subscribe field exists.
10310 @kindex C-c C-n u (Summary)
10311 @findex gnus-mailing-list-unsubscribe
10312 Send a message to unsubscribe the mailing list, if List-Unsubscribe
10316 @kindex C-c C-n p (Summary)
10317 @findex gnus-mailing-list-post
10318 Post to the mailing list, if List-Post field exists.
10321 @kindex C-c C-n o (Summary)
10322 @findex gnus-mailing-list-owner
10323 Send a message to the mailing list owner, if List-Owner field exists.
10326 @kindex C-c C-n a (Summary)
10327 @findex gnus-mailing-list-owner
10328 Browse the mailing list archive, if List-Archive field exists.
10332 @node Article Buffer
10333 @chapter Article Buffer
10334 @cindex article buffer
10336 The articles are displayed in the article buffer, of which there is only
10337 one. All the summary buffers share the same article buffer unless you
10338 tell gnus otherwise.
10341 * Hiding Headers:: Deciding what headers should be displayed.
10342 * Using MIME:: Pushing articles through @sc{mime} before reading them.
10343 * Customizing Articles:: Tailoring the look of the articles.
10344 * Article Keymap:: Keystrokes available in the article buffer.
10345 * Misc Article:: Other stuff.
10349 @node Hiding Headers
10350 @section Hiding Headers
10351 @cindex hiding headers
10352 @cindex deleting headers
10354 The top section of each article is the @dfn{head}. (The rest is the
10355 @dfn{body}, but you may have guessed that already.)
10357 @vindex gnus-show-all-headers
10358 There is a lot of useful information in the head: the name of the person
10359 who wrote the article, the date it was written and the subject of the
10360 article. That's well and nice, but there's also lots of information
10361 most people do not want to see---what systems the article has passed
10362 through before reaching you, the @code{Message-ID}, the
10363 @code{References}, etc. ad nauseum---and you'll probably want to get rid
10364 of some of those lines. If you want to keep all those lines in the
10365 article buffer, you can set @code{gnus-show-all-headers} to @code{t}.
10367 Gnus provides you with two variables for sifting headers:
10371 @item gnus-visible-headers
10372 @vindex gnus-visible-headers
10373 If this variable is non-@code{nil}, it should be a regular expression
10374 that says what headers you wish to keep in the article buffer. All
10375 headers that do not match this variable will be hidden.
10377 For instance, if you only want to see the name of the person who wrote
10378 the article and the subject, you'd say:
10381 (setq gnus-visible-headers "^From:\\|^Subject:")
10384 This variable can also be a list of regexps to match headers to
10387 @item gnus-ignored-headers
10388 @vindex gnus-ignored-headers
10389 This variable is the reverse of @code{gnus-visible-headers}. If this
10390 variable is set (and @code{gnus-visible-headers} is @code{nil}), it
10391 should be a regular expression that matches all lines that you want to
10392 hide. All lines that do not match this variable will remain visible.
10394 For instance, if you just want to get rid of the @code{References} field
10395 and the @code{Xref} field, you might say:
10398 (setq gnus-ignored-headers "^References:\\|^Xref:")
10401 This variable can also be a list of regexps to match headers to
10404 Note that if @code{gnus-visible-headers} is non-@code{nil}, this
10405 variable will have no effect.
10409 @vindex gnus-sorted-header-list
10410 Gnus can also sort the headers for you. (It does this by default.) You
10411 can control the sorting by setting the @code{gnus-sorted-header-list}
10412 variable. It is a list of regular expressions that says in what order
10413 the headers are to be displayed.
10415 For instance, if you want the name of the author of the article first,
10416 and then the subject, you might say something like:
10419 (setq gnus-sorted-header-list '("^From:" "^Subject:"))
10422 Any headers that are to remain visible, but are not listed in this
10423 variable, will be displayed in random order after all the headers listed in this variable.
10425 @findex gnus-article-hide-boring-headers
10426 @vindex gnus-boring-article-headers
10427 You can hide further boring headers by setting
10428 @code{gnus-treat-hide-boring-headers} to @code{head}. What this function
10429 does depends on the @code{gnus-boring-article-headers} variable. It's a
10430 list, but this list doesn't actually contain header names. Instead is
10431 lists various @dfn{boring conditions} that Gnus can check and remove
10434 These conditions are:
10437 Remove all empty headers.
10439 Remove the @code{Followup-To} header if it is identical to the
10440 @code{Newsgroups} header.
10442 Remove the @code{Reply-To} header if it lists the same address as the
10443 @code{From} header.
10445 Remove the @code{Newsgroups} header if it only contains the current group
10448 Remove the @code{To} header if it only contains the address identical to
10449 the current groups's @code{to-address} parameter.
10451 Remove the @code{Date} header if the article is less than three days
10454 Remove the @code{To} header if it is very long.
10456 Remove all @code{To} headers if there are more than one.
10459 To include these three elements, you could say something like:
10462 (setq gnus-boring-article-headers
10463 '(empty followup-to reply-to))
10466 This is also the default value for this variable.
10470 @section Using MIME
10473 Mime is a standard for waving your hands through the air, aimlessly,
10474 while people stand around yawning.
10476 @sc{mime}, however, is a standard for encoding your articles, aimlessly,
10477 while all newsreaders die of fear.
10479 @sc{mime} may specify what character set the article uses, the encoding
10480 of the characters, and it also makes it possible to embed pictures and
10481 other naughty stuff in innocent-looking articles.
10483 @vindex gnus-show-mime
10484 @vindex gnus-article-display-method-for-mime
10485 @findex gnus-article-display-mime-message
10486 Gnus handles @sc{mime} by pushing the articles through
10487 @code{gnus-article-display-method-for-mime}, which is
10488 @code{gnus-article-display-mime-message} by default. This function
10489 calls the @sc{semi} MIME-View program to actually do the work. For more
10490 information on @sc{semi} MIME-View, see its manual page (however it is
10491 not existed yet, sorry).
10493 Set @code{gnus-show-mime} to @code{t} if you want to use
10494 @sc{mime} all the time. If you have @code{gnus-show-mime} set, then
10495 you'll see some unfortunate display glitches in the article buffer.
10496 These can't be avoided.
10498 In GNUS or Gnus, it might be best to just use the toggling functions
10499 from the summary buffer to avoid getting nasty surprises. (For instance,
10500 you enter the group @samp{alt.sing-a-long} and, before you know it,
10501 @sc{mime} has decoded the sound file in the article and some horrible
10502 sing-a-long song comes screaming out your speakers, and you can't find
10503 the volume button, because there isn't one, and people are starting to
10504 look at you, and you try to stop the program, but you can't, and you
10505 can't find the program to control the volume, and everybody else in the
10506 room suddenly decides to look at you disdainfully, and you'll feel
10509 Any similarity to real events and people is purely coincidental. Ahem.
10511 To avoid such kind of situation, gnus stops to use
10512 @code{metamail-buffer}. So now, you can set @code{gnus-show-mime} to
10513 non-@code{nil} every-time, then you can push button in the article
10514 buffer when there are nobody else.
10516 Also see @pxref{MIME Commands}.
10519 @node Customizing Articles
10520 @section Customizing Articles
10521 @cindex article customization
10523 A slew of functions for customizing how the articles are to look like
10524 exist. You can call these functions interactively, or you can have them
10525 called automatically when you select the articles.
10527 To have them called automatically, you should set the corresponding
10528 ``treatment'' variable. For instance, to have headers hidden, you'd set
10529 @code{gnus-treat-hide-headers}. Below is a list of variables that can
10530 be set, but first we discuss the values these variables can have.
10532 Note: Some values, while valid, make little sense. Check the list below
10533 for sensible values.
10537 @code{nil}: Don't do this treatment.
10540 @code{t}: Do this treatment on all body parts.
10543 @code{head}: Do the treatment on the headers.
10546 @code{last}: Do this treatment on the last part.
10549 An integer: Do this treatment on all body parts that have a length less
10553 A list of strings: Do this treatment on all body parts that are in
10554 articles that are read in groups that have names that match one of the
10555 regexps in the list.
10558 A list where the first element is not a string:
10560 The list is evaluated recursively. The first element of the list is a
10561 predicate. The following predicates are recognized: @code{or},
10562 @code{and}, @code{not} and @code{typep}. Here's an example:
10566 (typep "text/x-vcard"))
10570 @code{mime}: Do this treatment if the value of @code{gnus-show-mime}' is
10575 You may have noticed that the word @dfn{part} is used here. This refers
10576 to the fact that some messages are @sc{mime} multipart articles that may
10577 be divided into several parts. Articles that are not multiparts are
10578 considered to contain just a single part.
10580 @vindex gnus-article-treat-types
10581 Are the treatments applied to all sorts of multipart parts? Yes, if you
10582 want to, but by default, only @samp{text/plain} parts are given the
10583 treatment. This is controlled by the @code{gnus-article-treat-types}
10584 variable, which is a list of regular expressions that are matched to the
10585 type of the part. This variable is ignored if the value of the
10586 controlling variable is a predicate list, as described above.
10588 The following treatment options are available. The easiest way to
10589 customize this is to examine the @code{gnus-article-treat} customization
10590 group. Values in parenthesis are suggested sensible values. Others are
10591 possible but those listed are probably sufficient for most people.
10594 @item gnus-treat-buttonize (t, integer)
10595 @item gnus-treat-buttonize-head (head)
10597 @xref{Article Buttons}.
10599 @item gnus-treat-capitalize-sentences (t, integer)
10600 @item gnus-treat-overstrike (t, integer)
10601 @item gnus-treat-strip-cr (t, integer)
10602 @item gnus-treat-strip-headers-in-body (t, integer)
10603 @item gnus-treat-strip-leading-blank-lines (t, integer)
10604 @item gnus-treat-strip-multiple-blank-lines (t, integer)
10605 @item gnus-treat-strip-pem (t, last, integer)
10606 @item gnus-treat-strip-pgp (t, last, integer)
10607 @item gnus-treat-strip-trailing-blank-lines (t, last, integer)
10608 @item gnus-treat-unsplit-urls (t, integer)
10609 @item gnus-treat-wash-html (t, integer)
10610 @item gnus-treat-decode-article-as-default-mime-charset (t, integer)
10612 @xref{Article Washing}.
10614 @item gnus-treat-date-english (head)
10615 @item gnus-treat-date-iso8601 (head)
10616 @item gnus-treat-date-lapsed (head)
10617 @item gnus-treat-date-local (head)
10618 @item gnus-treat-date-original (head)
10619 @item gnus-treat-date-user-defined (head)
10620 @item gnus-treat-date-ut (head)
10622 @xref{Article Date}.
10624 @item gnus-treat-from-picon (head)
10625 @item gnus-treat-mail-picon (head)
10626 @item gnus-treat-newsgroups-picon (head)
10630 @item gnus-treat-display-smileys (t, integer)
10632 @item gnus-treat-body-boundary (head)
10634 @vindex gnus-body-boundary-delimiter
10635 Adds a delimiter between header and body, the string used as delimiter
10636 is controlled by @code{gnus-body-boundary-delimiter}.
10640 @item gnus-treat-display-xface (head)
10644 @item gnus-treat-emphasize (t, head, integer)
10645 @item gnus-treat-fill-article (t, integer)
10646 @item gnus-treat-fill-long-lines (t, integer)
10647 @item gnus-treat-hide-boring-headers (head)
10648 @item gnus-treat-hide-citation (t, integer)
10649 @item gnus-treat-hide-citation-maybe (t, integer)
10650 @item gnus-treat-hide-headers (head)
10651 @item gnus-treat-hide-signature (t, last)
10653 @xref{Article Hiding}.
10655 @item gnus-treat-highlight-citation (t, integer)
10656 @item gnus-treat-highlight-headers (head)
10657 @item gnus-treat-highlight-signature (t, last, integer)
10659 @xref{Article Highlighting}.
10661 @item gnus-treat-play-sounds
10662 @item gnus-treat-translate
10663 @item gnus-treat-x-pgp-sig (head)
10665 @item gnus-treat-unfold-headers (head)
10666 @item gnus-treat-fold-headers (head)
10667 @item gnus-treat-fold-newsgroups (head)
10668 @item gnus-treat-leading-whitespace (head)
10670 @xref{Article Header}.
10675 @vindex gnus-part-display-hook
10676 You can, of course, write your own functions to be called from
10677 @code{gnus-part-display-hook}. The functions are called narrowed to the
10678 part, and you can do anything you like, pretty much. There is no
10679 information that you have to keep in the buffer---you can change
10683 @node Article Keymap
10684 @section Article Keymap
10686 Most of the keystrokes in the summary buffer can also be used in the
10687 article buffer. They should behave as if you typed them in the summary
10688 buffer, which means that you don't actually have to have a summary
10689 buffer displayed while reading. You can do it all from the article
10692 A few additional keystrokes are available:
10697 @kindex SPACE (Article)
10698 @findex gnus-article-next-page
10699 Scroll forwards one page (@code{gnus-article-next-page}).
10702 @kindex DEL (Article)
10703 @findex gnus-article-prev-page
10704 Scroll backwards one page (@code{gnus-article-prev-page}).
10707 @kindex C-c ^ (Article)
10708 @findex gnus-article-refer-article
10709 If point is in the neighborhood of a @code{Message-ID} and you press
10710 @kbd{C-c ^}, Gnus will try to get that article from the server
10711 (@code{gnus-article-refer-article}).
10714 @kindex C-c C-m (Article)
10715 @findex gnus-article-mail
10716 Send a reply to the address near point (@code{gnus-article-mail}). If
10717 given a prefix, include the mail.
10720 @kindex s (Article)
10721 @findex gnus-article-show-summary
10722 Reconfigure the buffers so that the summary buffer becomes visible
10723 (@code{gnus-article-show-summary}).
10726 @kindex ? (Article)
10727 @findex gnus-article-describe-briefly
10728 Give a very brief description of the available keystrokes
10729 (@code{gnus-article-describe-briefly}).
10732 @kindex TAB (Article)
10733 @findex gnus-article-next-button
10734 Go to the next button, if any (@code{gnus-article-next-button}). This
10735 only makes sense if you have buttonizing turned on.
10738 @kindex M-TAB (Article)
10739 @findex gnus-article-prev-button
10740 Go to the previous button, if any (@code{gnus-article-prev-button}).
10743 @kindex R (Article)
10744 @findex gnus-article-reply-with-original
10745 Send a reply to the current article and yank the current article
10746 (@code{gnus-article-reply-with-original}). If given a prefix, make a
10747 wide reply. If the region is active, only yank the text in the
10751 @kindex F (Article)
10752 @findex gnus-article-followup-with-original
10753 Send a followup to the current article and yank the current article
10754 (@code{gnus-article-followup-with-original}). If given a prefix, make
10755 a wide reply. If the region is active, only yank the text in the
10763 @section Misc Article
10767 @item gnus-single-article-buffer
10768 @vindex gnus-single-article-buffer
10769 If non-@code{nil}, use the same article buffer for all the groups.
10770 (This is the default.) If @code{nil}, each group will have its own
10773 @vindex gnus-article-decode-hook
10774 @item gnus-article-decode-hook
10776 Hook used to decode @sc{mime} articles. The default value is
10777 @code{(article-decode-charset article-decode-encoded-words)}
10779 @vindex gnus-article-prepare-hook
10780 @item gnus-article-prepare-hook
10781 This hook is called right after the article has been inserted into the
10782 article buffer. It is mainly intended for functions that do something
10783 depending on the contents; it should probably not be used for changing
10784 the contents of the article buffer.
10786 @item gnus-article-mode-hook
10787 @vindex gnus-article-mode-hook
10788 Hook called in article mode buffers.
10790 @item gnus-article-mode-syntax-table
10791 @vindex gnus-article-mode-syntax-table
10792 Syntax table used in article buffers. It is initialized from
10793 @code{text-mode-syntax-table}.
10795 @vindex gnus-article-mode-line-format
10796 @item gnus-article-mode-line-format
10797 This variable is a format string along the same lines as
10798 @code{gnus-summary-mode-line-format} (@pxref{Mode Line Formatting}). It
10799 accepts the same format specifications as that variable, with two
10805 The @dfn{wash status} of the article. This is a short string with one
10806 character for each possible article wash operation that may have been
10807 performed. The characters and their meaning:
10812 Displayed when cited text may be hidden in the article buffer.
10815 Displayed when headers are hidden in the article buffer.
10818 Displayed when article is digitally signed or encrypted, and Gnus has
10819 hidden the security headers. (N.B. does not tell anything about
10820 security status, i.e. good or bad signature.)
10823 Displayed when the signature has been hidden in the Article buffer.
10826 Displayed when Gnus has treated overstrike characters in the article buffer.
10829 Displayed when Gnus has treated emphasised strings in the article buffer.
10834 The number of @sc{mime} parts in the article.
10838 @vindex gnus-break-pages
10840 @item gnus-break-pages
10841 Controls whether @dfn{page breaking} is to take place. If this variable
10842 is non-@code{nil}, the articles will be divided into pages whenever a
10843 page delimiter appears in the article. If this variable is @code{nil},
10844 paging will not be done.
10846 @item gnus-page-delimiter
10847 @vindex gnus-page-delimiter
10848 This is the delimiter mentioned above. By default, it is @samp{^L}
10853 @node Composing Messages
10854 @chapter Composing Messages
10855 @cindex composing messages
10858 @cindex sending mail
10863 @cindex using s/mime
10864 @cindex using smime
10866 @kindex C-c C-c (Post)
10867 All commands for posting and mailing will put you in a message buffer
10868 where you can edit the article all you like, before you send the
10869 article by pressing @kbd{C-c C-c}. @xref{Top, , Overview, message,
10870 Message Manual}. Where the message will be posted/mailed to depends
10871 on your setup (@pxref{Posting Server}).
10874 * Mail:: Mailing and replying.
10875 * Posting Server:: What server should you post and mail via?
10876 * Mail and Post:: Mailing and posting at the same time.
10877 * Archived Messages:: Where Gnus stores the messages you've sent.
10878 * Posting Styles:: An easier way to specify who you are.
10879 * Drafts:: Postponing messages and rejected messages.
10880 * Rejected Articles:: What happens if the server doesn't like your article?
10881 * Signing and encrypting:: How to compose secure messages.
10884 Also see @pxref{Canceling and Superseding} for information on how to
10885 remove articles you shouldn't have posted.
10891 Variables for customizing outgoing mail:
10894 @item gnus-uu-digest-headers
10895 @vindex gnus-uu-digest-headers
10896 List of regexps to match headers included in digested messages. The
10897 headers will be included in the sequence they are matched. If
10898 @code{nil} include all headers.
10900 @item gnus-add-to-list
10901 @vindex gnus-add-to-list
10902 If non-@code{nil}, add a @code{to-list} group parameter to mail groups
10903 that have none when you do a @kbd{a}.
10905 @item gnus-confirm-mail-reply-to-news
10906 @vindex gnus-confirm-mail-reply-to-news
10907 This can also be a function receiving the group name as the only
10908 parameter which should return non-@code{nil} if a confirmation is
10909 needed, or a regular expression matching group names, where
10910 confirmation is should be asked for.
10912 If you find yourself never wanting to reply to mail, but occasionally
10913 press R anyway, this variable might be for you.
10915 @item gnus-confirm-treat-mail-like-news
10916 @vindex gnus-confirm-treat-mail-like-news
10917 If non-@code{nil}, Gnus also requests confirmation according to
10918 @code{gnus-confirm-mail-reply-to-news} when replying to mail. This is
10919 useful for treating mailing lists like newsgroups.
10924 @node Posting Server
10925 @section Posting Server
10927 When you press those magical @kbd{C-c C-c} keys to ship off your latest
10928 (extremely intelligent, of course) article, where does it go?
10930 Thank you for asking. I hate you.
10932 It can be quite complicated.
10934 @vindex gnus-post-method
10935 When posting news, Message usually invokes @code{message-send-news}
10936 (@pxref{News Variables, , News Variables, message, Message Manual}).
10937 Normally, Gnus will post using the same select method as you're
10938 reading from (which might be convenient if you're reading lots of
10939 groups from different private servers). However. If the server
10940 you're reading from doesn't allow posting, just reading, you probably
10941 want to use some other server to post your (extremely intelligent and
10942 fabulously interesting) articles. You can then set the
10943 @code{gnus-post-method} to some other method:
10946 (setq gnus-post-method '(nnspool ""))
10949 Now, if you've done this, and then this server rejects your article, or
10950 this server is down, what do you do then? To override this variable you
10951 can use a non-zero prefix to the @kbd{C-c C-c} command to force using
10952 the ``current'' server, to get back the default behavior, for posting.
10954 If you give a zero prefix (i.e., @kbd{C-u 0 C-c C-c}) to that command,
10955 gnus will prompt you for what method to use for posting.
10957 You can also set @code{gnus-post-method} to a list of select methods.
10958 If that's the case, gnus will always prompt you for what method to use
10961 Finally, if you want to always post using the native select method,
10962 you can set this variable to @code{native}.
10964 When sending mail, Message invokes @code{message-send-mail-function}.
10965 The default function, @code{message-send-mail-with-sendmail}, pipes
10966 your article to the @code{sendmail} binary for further queuing and
10967 sending. When your local system is not configured for sending mail
10968 using @code{sendmail}, and you have access to a remote @sc{smtp}
10969 server, you can set @code{message-send-mail-function} to
10970 @code{smtpmail-send-it} and make sure to setup the @code{smtpmail}
10971 package correctly. An example:
10974 (setq message-send-mail-function 'smtpmail-send-it
10975 smtpmail-default-smtp-server "YOUR SMTP HOST")
10976 ;; The following variable needs to be set because of the FLIM version of
10977 ;; smtpmail.el. Which smtpmail.el is used depends on the `load-path'.
10978 (setq smtp-default-smtp-server "YOUR SMTP HOST")
10981 To the thing similar to this, there is @code{message-smtpmail-send-it}.
10982 It is useful if your ISP requires the POP-before-SMTP authentication.
10983 See the documentation for the function @code{mail-source-touch-pop}.
10985 Other possible choices for @code{message-send-mail-function} includes
10986 @code{message-send-mail-with-mh}, @code{message-send-mail-with-qmail},
10987 and @code{feedmail-send-it}.
10989 @node Mail and Post
10990 @section Mail and Post
10992 Here's a list of variables relevant to both mailing and
10996 @item gnus-mailing-list-groups
10997 @findex gnus-mailing-list-groups
10998 @cindex mailing lists
11000 If your news server offers groups that are really mailing lists
11001 gatewayed to the @sc{nntp} server, you can read those groups without
11002 problems, but you can't post/followup to them without some difficulty.
11003 One solution is to add a @code{to-address} to the group parameters
11004 (@pxref{Group Parameters}). An easier thing to do is set the
11005 @code{gnus-mailing-list-groups} to a regexp that matches the groups that
11006 really are mailing lists. Then, at least, followups to the mailing
11007 lists will work most of the time. Posting to these groups (@kbd{a}) is
11008 still a pain, though.
11012 You may want to do spell-checking on messages that you send out. Or, if
11013 you don't want to spell-check by hand, you could add automatic
11014 spell-checking via the @code{ispell} package:
11017 @findex ispell-message
11019 (add-hook 'message-send-hook 'ispell-message)
11022 If you want to change the @code{ispell} dictionary based on what group
11023 you're in, you could say something like the following:
11026 (add-hook 'gnus-select-group-hook
11030 "^de\\." (gnus-group-real-name gnus-newsgroup-name))
11031 (ispell-change-dictionary "deutsch"))
11033 (ispell-change-dictionary "english")))))
11036 Modify to suit your needs.
11039 @node Archived Messages
11040 @section Archived Messages
11041 @cindex archived messages
11042 @cindex sent messages
11044 Gnus provides a few different methods for storing the mail and news you
11045 send. The default method is to use the @dfn{archive virtual server} to
11046 store the messages. If you want to disable this completely, the
11047 @code{gnus-message-archive-group} variable should be @code{nil}, which
11050 For archiving interesting messages in a group you read, see the
11051 @kbd{B c} (@code{gnus-summary-copy-article}) command (@pxref{Mail
11054 @vindex gnus-message-archive-method
11055 @code{gnus-message-archive-method} says what virtual server gnus is to
11056 use to store sent messages. The default is:
11059 (nnfolder "archive"
11060 (nnfolder-directory "~/Mail/archive")
11061 (nnfolder-active-file "~/Mail/archive/active")
11062 (nnfolder-get-new-mail nil)
11063 (nnfolder-inhibit-expiry t))
11066 You can, however, use any mail select method (@code{nnml},
11067 @code{nnmbox}, etc.). @code{nnfolder} is a quite likable select method
11068 for doing this sort of thing, though. If you don't like the default
11069 directory chosen, you could say something like:
11072 (setq gnus-message-archive-method
11073 '(nnfolder "archive"
11074 (nnfolder-inhibit-expiry t)
11075 (nnfolder-active-file "~/News/sent-mail/active")
11076 (nnfolder-directory "~/News/sent-mail/")))
11079 @vindex gnus-message-archive-group
11081 Gnus will insert @code{Gcc} headers in all outgoing messages that point
11082 to one or more group(s) on that server. Which group to use is
11083 determined by the @code{gnus-message-archive-group} variable.
11085 This variable can be used to do the following:
11090 Messages will be saved in that group.
11092 Note that you can include a select method in the group name, then the
11093 message will not be stored in the select method given by
11094 @code{gnus-message-archive-method}, but in the select method specified
11095 by the group name, instead. Suppose @code{gnus-message-archive-method}
11096 has the default value shown above. Then setting
11097 @code{gnus-message-archive-group} to @code{"foo"} means that outgoing
11098 messages are stored in @samp{nnfolder+archive:foo}, but if you use the
11099 value @code{"nnml:foo"}, then outgoing messages will be stored in
11103 Messages will be saved in all those groups.
11105 an alist of regexps, functions and forms
11106 When a key ``matches'', the result is used.
11109 No message archiving will take place. This is the default.
11114 Just saving to a single group called @samp{MisK}:
11116 (setq gnus-message-archive-group "MisK")
11119 Saving to two groups, @samp{MisK} and @samp{safe}:
11121 (setq gnus-message-archive-group '("MisK" "safe"))
11124 Save to different groups based on what group you are in:
11126 (setq gnus-message-archive-group
11127 '(("^alt" "sent-to-alt")
11128 ("mail" "sent-to-mail")
11129 (".*" "sent-to-misc")))
11132 More complex stuff:
11134 (setq gnus-message-archive-group
11135 '((if (message-news-p)
11140 How about storing all news messages in one file, but storing all mail
11141 messages in one file per month:
11144 (setq gnus-message-archive-group
11145 '((if (message-news-p)
11147 (concat "mail." (format-time-string "%Y-%m")))))
11150 @c (XEmacs 19.13 doesn't have @code{format-time-string}, so you'll have to
11151 @c use a different value for @code{gnus-message-archive-group} there.)
11153 Now, when you send a message off, it will be stored in the appropriate
11154 group. (If you want to disable storing for just one particular message,
11155 you can just remove the @code{Gcc} header that has been inserted.) The
11156 archive group will appear in the group buffer the next time you start
11157 gnus, or the next time you press @kbd{F} in the group buffer. You can
11158 enter it and read the articles in it just like you'd read any other
11159 group. If the group gets really big and annoying, you can simply rename
11160 if (using @kbd{G r} in the group buffer) to something
11161 nice---@samp{misc-mail-september-1995}, or whatever. New messages will
11162 continue to be stored in the old (now empty) group.
11164 That's the default method of archiving sent messages. Gnus offers a
11165 different way for the people who don't like the default method. In that
11166 case you should set @code{gnus-message-archive-group} to @code{nil};
11167 this will disable archiving.
11170 @item gnus-outgoing-message-group
11171 @vindex gnus-outgoing-message-group
11172 All outgoing messages will be put in this group. If you want to store
11173 all your outgoing mail and articles in the group @samp{nnml:archive},
11174 you set this variable to that value. This variable can also be a list of
11177 If you want to have greater control over what group to put each
11178 message in, you can set this variable to a function that checks the
11179 current newsgroup name and then returns a suitable group name (or list
11182 This variable can be used instead of @code{gnus-message-archive-group},
11183 but the latter is the preferred method.
11185 @item gnus-gcc-mark-as-read
11186 @vindex gnus-gcc-mark-as-read
11187 If non-@code{nil}, automatically mark @code{Gcc} articles as read.
11189 @item gnus-gcc-externalize-attachments
11190 @vindex gnus-gcc-externalize-attachments
11191 If @code{nil}, attach files as normal parts in Gcc copies; if a regexp
11192 and matches the Gcc group name, attach files as external parts; if it is
11193 @code{all}, attach local files as external parts; if it is other
11194 non-@code{nil}, the behavior is the same as @code{all}, but it may be
11195 changed in the future.
11200 @node Posting Styles
11201 @section Posting Styles
11202 @cindex posting styles
11205 All them variables, they make my head swim.
11207 So what if you want a different @code{Organization} and signature based
11208 on what groups you post to? And you post both from your home machine
11209 and your work machine, and you want different @code{From} lines, and so
11212 @vindex gnus-posting-styles
11213 One way to do stuff like that is to write clever hooks that change the
11214 variables you need to have changed. That's a bit boring, so somebody
11215 came up with the bright idea of letting the user specify these things in
11216 a handy alist. Here's an example of a @code{gnus-posting-styles}
11221 (signature "Peace and happiness")
11222 (organization "What me?"))
11224 (signature "Death to everybody"))
11225 ("comp.emacs.i-love-it"
11226 (organization "Emacs is it")))
11229 As you might surmise from this example, this alist consists of several
11230 @dfn{styles}. Each style will be applicable if the first element
11231 ``matches'', in some form or other. The entire alist will be iterated
11232 over, from the beginning towards the end, and each match will be
11233 applied, which means that attributes in later styles that match override
11234 the same attributes in earlier matching styles. So
11235 @samp{comp.programming.literate} will have the @samp{Death to everybody}
11236 signature and the @samp{What me?} @code{Organization} header.
11238 The first element in each style is called the @code{match}. If it's a
11239 string, then Gnus will try to regexp match it against the group name.
11240 If it is the form @code{(header MATCH REGEXP)}, then Gnus will look in
11241 the original article for a header whose name is MATCH and compare that
11242 REGEXP. MATCH and REGEXP are strings. (There original article is the
11243 one you are replying or following up to. If you are not composing a
11244 reply or a followup, then there is nothing to match against.) If the
11245 @code{match} is a function symbol, that function will be called with no
11246 arguments. If it's a variable symbol, then the variable will be
11247 referenced. If it's a list, then that list will be @code{eval}ed. In
11248 any case, if this returns a non-@code{nil} value, then the style is said
11251 Each style may contain an arbitrary amount of @dfn{attributes}. Each
11252 attribute consists of a @code{(@var{name} @var{value})} pair. The
11253 attribute name can be one of @code{signature}, @code{signature-file},
11254 @code{x-face-file}, @code{address} (overriding
11255 @code{user-mail-address}), @code{name} (overriding
11256 @code{(user-full-name)}) or @code{body}. The attribute name can also
11257 be a string or a symbol. In that case, this will be used as a header
11258 name, and the value will be inserted in the headers of the article; if
11259 the value is @code{nil}, the header name will be removed. If the
11260 attribute name is @code{eval}, the form is evaluated, and the result
11263 The attribute value can be a string (used verbatim), a function with
11264 zero arguments (the return value will be used), a variable (its value
11265 will be used) or a list (it will be @code{eval}ed and the return value
11266 will be used). The functions and sexps are called/@code{eval}ed in the
11267 message buffer that is being set up. The headers of the current article
11268 are available through the @code{message-reply-headers} variable, which
11269 is a vector of the following headers: number subject from date id
11270 references chars lines xref extra.
11272 @vindex message-reply-headers
11274 If you wish to check whether the message you are about to compose is
11275 meant to be a news article or a mail message, you can check the values
11276 of the @code{message-news-p} and @code{message-mail-p} functions.
11278 @findex message-mail-p
11279 @findex message-news-p
11281 So here's a new example:
11284 (setq gnus-posting-styles
11286 (signature-file "~/.signature")
11288 ("X-Home-Page" (getenv "WWW_HOME"))
11289 (organization "People's Front Against MWM"))
11291 (signature my-funny-signature-randomizer))
11292 ((equal (system-name) "gnarly") ;; A form
11293 (signature my-quote-randomizer))
11294 (message-news-p ;; A function symbol
11295 (signature my-news-signature))
11296 (window-system ;; A value symbol
11297 ("X-Window-System" (format "%s" window-system)))
11298 ;; If I'm replying to Larsi, set the Organization header.
11299 ((header "from" "larsi.*org")
11300 (Organization "Somewhere, Inc."))
11301 ((posting-from-work-p) ;; A user defined function
11302 (signature-file "~/.work-signature")
11303 (address "user@@bar.foo")
11304 (body "You are fired.\n\nSincerely, your boss.")
11305 (organization "Important Work, Inc"))
11307 (From (save-excursion
11308 (set-buffer gnus-article-buffer)
11309 (message-fetch-field "to"))))
11311 (signature-file "~/.mail-signature"))))
11314 The @samp{nnml:.*} rule means that you use the @code{To} address as the
11315 @code{From} address in all your outgoing replies, which might be handy
11316 if you fill many roles.
11318 Setting the @code{gnus-named-posting-styles} variable will make
11319 posting-styles allow to have distinctive names. You can specify an
11320 arbitrary posting-style when article posting with @kbd{S P} in the
11321 summary buffer. @code{gnus-named-posting-styles} is an alist which maps
11322 the names to styles. Once a posting-style is added to the alist, we can
11323 import it from @code{gnus-posting-styles}. If an attribute whose name
11324 is @code{import} is found, Gnus will look for the attribute value in
11325 @code{gnus-named-posting-styles} and expand it in place.
11330 (setq gnus-named-posting-styles
11332 (signature-file "~/.signature")
11334 ("X-Home-Page" (getenv "WWW_HOME"))
11335 (organization "People's Front Against MWM"))
11338 (organization "The Church of Emacs"))))
11341 The posting-style named "Emacs" will inherit all the attributes from
11342 "Default" except @code{organization}.
11349 If you are writing a message (mail or news) and suddenly remember that
11350 you have a steak in the oven (or some pesto in the food processor, you
11351 craaazy vegetarians), you'll probably wish there was a method to save
11352 the message you are writing so that you can continue editing it some
11353 other day, and send it when you feel its finished.
11355 Well, don't worry about it. Whenever you start composing a message of
11356 some sort using the gnus mail and post commands, the buffer you get will
11357 automatically associate to an article in a special @dfn{draft} group.
11358 If you save the buffer the normal way (@kbd{C-x C-s}, for instance), the
11359 article will be saved there. (Auto-save files also go to the draft
11363 @vindex nndraft-directory
11364 The draft group is a special group (which is implemented as an
11365 @code{nndraft} group, if you absolutely have to know) called
11366 @samp{nndraft:drafts}. The variable @code{nndraft-directory} says where
11367 @code{nndraft} is to store its files. What makes this group special is
11368 that you can't tick any articles in it or mark any articles as
11369 read---all articles in the group are permanently unread.
11371 If the group doesn't exist, it will be created and you'll be subscribed
11372 to it. The only way to make it disappear from the Group buffer is to
11375 @c @findex gnus-dissociate-buffer-from-draft
11376 @c @kindex C-c M-d (Mail)
11377 @c @kindex C-c M-d (Post)
11378 @c @findex gnus-associate-buffer-with-draft
11379 @c @kindex C-c C-d (Mail)
11380 @c @kindex C-c C-d (Post)
11381 @c If you're writing some super-secret message that you later want to
11382 @c encode with PGP before sending, you may wish to turn the auto-saving
11383 @c (and association with the draft group) off. You never know who might be
11384 @c interested in reading all your extremely valuable and terribly horrible
11385 @c and interesting secrets. The @kbd{C-c M-d}
11386 @c (@code{gnus-dissociate-buffer-from-draft}) command does that for you.
11387 @c If you change your mind and want to turn the auto-saving back on again,
11388 @c @kbd{C-c C-d} (@code{gnus-associate-buffer-with-draft} does that.
11390 @c @vindex gnus-use-draft
11391 @c To leave association with the draft group off by default, set
11392 @c @code{gnus-use-draft} to @code{nil}. It is @code{t} by default.
11394 @findex gnus-draft-edit-message
11395 @kindex D e (Draft)
11396 When you want to continue editing the article, you simply enter the
11397 draft group and push @kbd{D e} (@code{gnus-draft-edit-message}) to do
11398 that. You will be placed in a buffer where you left off.
11400 Rejected articles will also be put in this draft group (@pxref{Rejected
11403 @findex gnus-draft-send-all-messages
11404 @findex gnus-draft-send-message
11405 If you have lots of rejected messages you want to post (or mail) without
11406 doing further editing, you can use the @kbd{D s} command
11407 (@code{gnus-draft-send-message}). This command understands the
11408 process/prefix convention (@pxref{Process/Prefix}). The @kbd{D S}
11409 command (@code{gnus-draft-send-all-messages}) will ship off all messages
11412 If you have some messages that you wish not to send, you can use the
11413 @kbd{D t} (@code{gnus-draft-toggle-sending}) command to mark the message
11414 as unsendable. This is a toggling command.
11417 @node Rejected Articles
11418 @section Rejected Articles
11419 @cindex rejected articles
11421 Sometimes a news server will reject an article. Perhaps the server
11422 doesn't like your face. Perhaps it just feels miserable. Perhaps
11423 @emph{there be demons}. Perhaps you have included too much cited text.
11424 Perhaps the disk is full. Perhaps the server is down.
11426 These situations are, of course, totally beyond the control of gnus.
11427 (Gnus, of course, loves the way you look, always feels great, has angels
11428 fluttering around inside of it, doesn't care about how much cited text
11429 you include, never runs full and never goes down.) So gnus saves these
11430 articles until some later time when the server feels better.
11432 The rejected articles will automatically be put in a special draft group
11433 (@pxref{Drafts}). When the server comes back up again, you'd then
11434 typically enter that group and send all the articles off.
11436 @node Signing and encrypting
11437 @section Signing and encrypting
11439 @cindex using s/mime
11440 @cindex using smime
11442 Gnus can digitally sign and encrypt your messages, using vanilla PGP
11443 format or @sc{pgp/mime} or @sc{s/mime}. For decoding such messages,
11444 see the @code{mm-verify-option} and @code{mm-decrypt-option} options
11445 (@pxref{Security}).
11447 For PGP, Gnus supports two external libraries, @sc{gpg.el} and
11448 @sc{Mailcrypt}, you need to install at least one of them. The
11449 @sc{s/mime} support in Gnus requires the external program OpenSSL.
11451 Often, you would like to sign replies to people who send you signed
11452 messages. Even more often, you might want to encrypt messages which
11453 are in reply to encrypted messages. Gnus offers
11454 @code{gnus-message-replysign} to enable the former, and
11455 @code{gnus-message-replyencrypt} for the latter. In addition, setting
11456 @code{gnus-message-replysignencrypted} (on by default) will sign
11457 automatically encrypted messages.
11459 Instructing MML to perform security operations on a @sc{mime} part is
11460 done using the @kbd{C-c C-m s} key map for signing and the @kbd{C-c
11461 C-m c} key map for encryption, as follows.
11466 @kindex C-c C-m s s
11467 @findex mml-secure-message-sign-smime
11469 Digitally sign current message using @sc{s/mime}.
11472 @kindex C-c C-m s o
11473 @findex mml-secure-message-sign-pgp
11475 Digitally sign current message using PGP.
11478 @kindex C-c C-m s p
11479 @findex mml-secure-message-sign-pgp
11481 Digitally sign current message using @sc{pgp/mime}.
11484 @kindex C-c C-m c s
11485 @findex mml-secure-message-encrypt-smime
11487 Digitally encrypt current message using @sc{s/mime}.
11490 @kindex C-c C-m c o
11491 @findex mml-secure-message-encrypt-pgp
11493 Digitally encrypt current message using PGP.
11496 @kindex C-c C-m c p
11497 @findex mml-secure-message-encrypt-pgpmime
11499 Digitally encrypt current message using @sc{pgp/mime}.
11502 @kindex C-c C-m C-n
11503 @findex mml-unsecure-message
11504 Remove security related MML tags from message.
11508 Also @xref{Security, ,Security, message, Message Manual}.
11510 @node Select Methods
11511 @chapter Select Methods
11512 @cindex foreign groups
11513 @cindex select methods
11515 A @dfn{foreign group} is a group not read by the usual (or
11516 default) means. It could be, for instance, a group from a different
11517 @sc{nntp} server, it could be a virtual group, or it could be your own
11518 personal mail group.
11520 A foreign group (or any group, really) is specified by a @dfn{name} and
11521 a @dfn{select method}. To take the latter first, a select method is a
11522 list where the first element says what back end to use (e.g. @code{nntp},
11523 @code{nnspool}, @code{nnml}) and the second element is the @dfn{server
11524 name}. There may be additional elements in the select method, where the
11525 value may have special meaning for the back end in question.
11527 One could say that a select method defines a @dfn{virtual server}---so
11528 we do just that (@pxref{Server Buffer}).
11530 The @dfn{name} of the group is the name the back end will recognize the
11533 For instance, the group @samp{soc.motss} on the @sc{nntp} server
11534 @samp{some.where.edu} will have the name @samp{soc.motss} and select
11535 method @code{(nntp "some.where.edu")}. Gnus will call this group
11536 @samp{nntp+some.where.edu:soc.motss}, even though the @code{nntp}
11537 back end just knows this group as @samp{soc.motss}.
11539 The different methods all have their peculiarities, of course.
11542 * Server Buffer:: Making and editing virtual servers.
11543 * Getting News:: Reading USENET news with Gnus.
11544 * Getting Mail:: Reading your personal mail with Gnus.
11545 * Browsing the Web:: Getting messages from a plethora of Web sources.
11546 * IMAP:: Using Gnus as a @sc{imap} client.
11547 * Other Sources:: Reading directories, files, SOUP packets.
11548 * Combined Groups:: Combining groups into one group.
11549 * Gnus Unplugged:: Reading news and mail offline.
11553 @node Server Buffer
11554 @section Server Buffer
11556 Traditionally, a @dfn{server} is a machine or a piece of software that
11557 one connects to, and then requests information from. Gnus does not
11558 connect directly to any real servers, but does all transactions through
11559 one back end or other. But that's just putting one layer more between
11560 the actual media and Gnus, so we might just as well say that each
11561 back end represents a virtual server.
11563 For instance, the @code{nntp} back end may be used to connect to several
11564 different actual @sc{nntp} servers, or, perhaps, to many different ports
11565 on the same actual @sc{nntp} server. You tell Gnus which back end to
11566 use, and what parameters to set by specifying a @dfn{select method}.
11568 These select method specifications can sometimes become quite
11569 complicated---say, for instance, that you want to read from the
11570 @sc{nntp} server @samp{news.funet.fi} on port number 13, which
11571 hangs if queried for @sc{nov} headers and has a buggy select. Ahem.
11572 Anyway, if you had to specify that for each group that used this
11573 server, that would be too much work, so Gnus offers a way of naming
11574 select methods, which is what you do in the server buffer.
11576 To enter the server buffer, use the @kbd{^}
11577 (@code{gnus-group-enter-server-mode}) command in the group buffer.
11580 * Server Buffer Format:: You can customize the look of this buffer.
11581 * Server Commands:: Commands to manipulate servers.
11582 * Example Methods:: Examples server specifications.
11583 * Creating a Virtual Server:: An example session.
11584 * Server Variables:: Which variables to set.
11585 * Servers and Methods:: You can use server names as select methods.
11586 * Unavailable Servers:: Some servers you try to contact may be down.
11589 @vindex gnus-server-mode-hook
11590 @code{gnus-server-mode-hook} is run when creating the server buffer.
11593 @node Server Buffer Format
11594 @subsection Server Buffer Format
11595 @cindex server buffer format
11597 @vindex gnus-server-line-format
11598 You can change the look of the server buffer lines by changing the
11599 @code{gnus-server-line-format} variable. This is a @code{format}-like
11600 variable, with some simple extensions:
11605 How the news is fetched---the back end name.
11608 The name of this server.
11611 Where the news is to be fetched from---the address.
11614 The opened/closed/denied status of the server.
11617 @vindex gnus-server-mode-line-format
11618 The mode line can also be customized by using the
11619 @code{gnus-server-mode-line-format} variable (@pxref{Mode Line
11620 Formatting}). The following specs are understood:
11630 Also @pxref{Formatting Variables}.
11633 @node Server Commands
11634 @subsection Server Commands
11635 @cindex server commands
11641 @findex gnus-server-add-server
11642 Add a new server (@code{gnus-server-add-server}).
11646 @findex gnus-server-edit-server
11647 Edit a server (@code{gnus-server-edit-server}).
11650 @kindex SPACE (Server)
11651 @findex gnus-server-read-server
11652 Browse the current server (@code{gnus-server-read-server}).
11656 @findex gnus-server-exit
11657 Return to the group buffer (@code{gnus-server-exit}).
11661 @findex gnus-server-kill-server
11662 Kill the current server (@code{gnus-server-kill-server}).
11666 @findex gnus-server-yank-server
11667 Yank the previously killed server (@code{gnus-server-yank-server}).
11671 @findex gnus-server-copy-server
11672 Copy the current server (@code{gnus-server-copy-server}).
11676 @findex gnus-server-list-servers
11677 List all servers (@code{gnus-server-list-servers}).
11681 @findex gnus-server-scan-server
11682 Request that the server scan its sources for new articles
11683 (@code{gnus-server-scan-server}). This is mainly sensible with mail
11688 @findex gnus-server-regenerate-server
11689 Request that the server regenerate all its data structures
11690 (@code{gnus-server-regenerate-server}). This can be useful if you have
11691 a mail back end that has gotten out of sync.
11696 @node Example Methods
11697 @subsection Example Methods
11699 Most select methods are pretty simple and self-explanatory:
11702 (nntp "news.funet.fi")
11705 Reading directly from the spool is even simpler:
11711 As you can see, the first element in a select method is the name of the
11712 back end, and the second is the @dfn{address}, or @dfn{name}, if you
11715 After these two elements, there may be an arbitrary number of
11716 @code{(@var{variable} @var{form})} pairs.
11718 To go back to the first example---imagine that you want to read from
11719 port 15 on that machine. This is what the select method should
11723 (nntp "news.funet.fi" (nntp-port-number 15))
11726 You should read the documentation to each back end to find out what
11727 variables are relevant, but here's an @code{nnmh} example:
11729 @code{nnmh} is a mail back end that reads a spool-like structure. Say
11730 you have two structures that you wish to access: One is your private
11731 mail spool, and the other is a public one. Here's the possible spec for
11735 (nnmh "private" (nnmh-directory "~/private/mail/"))
11738 (This server is then called @samp{private}, but you may have guessed
11741 Here's the method for a public spool:
11745 (nnmh-directory "/usr/information/spool/")
11746 (nnmh-get-new-mail nil))
11752 If you are behind a firewall and only have access to the @sc{nntp}
11753 server from the firewall machine, you can instruct Gnus to @code{rlogin}
11754 on the firewall machine and telnet from there to the @sc{nntp} server.
11755 Doing this can be rather fiddly, but your virtual server definition
11756 should probably look something like this:
11760 (nntp-open-connection-function nntp-open-via-rlogin-and-telnet)
11761 (nntp-via-address "the.firewall.machine")
11762 (nntp-address "the.real.nntp.host")
11763 (nntp-end-of-line "\n"))
11766 If you want to use the wonderful @code{ssh} program to provide a
11767 compressed connection over the modem line, you could add the following
11768 configuration to the example above:
11771 (nntp-via-rlogin-command "ssh")
11774 See also @code{nntp-via-rlogin-command-switches}.
11776 If you're behind a firewall, but have direct access to the outside world
11777 through a wrapper command like "runsocks", you could open a socksified
11778 telnet connection to the news server as follows:
11782 (nntp-pre-command "runsocks")
11783 (nntp-open-connection-function nntp-open-via-telnet)
11784 (nntp-address "the.news.server")
11785 (nntp-end-of-line "\n"))
11788 This means that you have to have set up @code{ssh-agent} correctly to
11789 provide automatic authorization, of course. And to get a compressed
11790 connection, you have to have the @samp{Compression} option in the
11791 @code{ssh} @file{config} file.
11794 @node Creating a Virtual Server
11795 @subsection Creating a Virtual Server
11797 If you're saving lots of articles in the cache by using persistent
11798 articles, you may want to create a virtual server to read the cache.
11800 First you need to add a new server. The @kbd{a} command does that. It
11801 would probably be best to use @code{nnspool} to read the cache. You
11802 could also use @code{nnml} or @code{nnmh}, though.
11804 Type @kbd{a nnspool RET cache RET}.
11806 You should now have a brand new @code{nnspool} virtual server called
11807 @samp{cache}. You now need to edit it to have the right definitions.
11808 Type @kbd{e} to edit the server. You'll be entered into a buffer that
11809 will contain the following:
11819 (nnspool-spool-directory "~/News/cache/")
11820 (nnspool-nov-directory "~/News/cache/")
11821 (nnspool-active-file "~/News/cache/active"))
11824 Type @kbd{C-c C-c} to return to the server buffer. If you now press
11825 @kbd{RET} over this virtual server, you should be entered into a browse
11826 buffer, and you should be able to enter any of the groups displayed.
11829 @node Server Variables
11830 @subsection Server Variables
11832 One sticky point when defining variables (both on back ends and in Emacs
11833 in general) is that some variables are typically initialized from other
11834 variables when the definition of the variables is being loaded. If you
11835 change the "base" variable after the variables have been loaded, you
11836 won't change the "derived" variables.
11838 This typically affects directory and file variables. For instance,
11839 @code{nnml-directory} is @file{~/Mail/} by default, and all @code{nnml}
11840 directory variables are initialized from that variable, so
11841 @code{nnml-active-file} will be @file{~/Mail/active}. If you define a
11842 new virtual @code{nnml} server, it will @emph{not} suffice to set just
11843 @code{nnml-directory}---you have to explicitly set all the file
11844 variables to be what you want them to be. For a complete list of
11845 variables for each back end, see each back end's section later in this
11846 manual, but here's an example @code{nnml} definition:
11850 (nnml-directory "~/my-mail/")
11851 (nnml-active-file "~/my-mail/active")
11852 (nnml-newsgroups-file "~/my-mail/newsgroups"))
11856 @node Servers and Methods
11857 @subsection Servers and Methods
11859 Wherever you would normally use a select method
11860 (e.g. @code{gnus-secondary-select-method}, in the group select method,
11861 when browsing a foreign server) you can use a virtual server name
11862 instead. This could potentially save lots of typing. And it's nice all
11866 @node Unavailable Servers
11867 @subsection Unavailable Servers
11869 If a server seems to be unreachable, Gnus will mark that server as
11870 @code{denied}. That means that any subsequent attempt to make contact
11871 with that server will just be ignored. ``It can't be opened,'' Gnus
11872 will tell you, without making the least effort to see whether that is
11873 actually the case or not.
11875 That might seem quite naughty, but it does make sense most of the time.
11876 Let's say you have 10 groups subscribed to on server
11877 @samp{nephelococcygia.com}. This server is located somewhere quite far
11878 away from you and the machine is quite slow, so it takes 1 minute just
11879 to find out that it refuses connection to you today. If Gnus were to
11880 attempt to do that 10 times, you'd be quite annoyed, so Gnus won't
11881 attempt to do that. Once it has gotten a single ``connection refused'',
11882 it will regard that server as ``down''.
11884 So, what happens if the machine was only feeling unwell temporarily?
11885 How do you test to see whether the machine has come up again?
11887 You jump to the server buffer (@pxref{Server Buffer}) and poke it
11888 with the following commands:
11894 @findex gnus-server-open-server
11895 Try to establish connection to the server on the current line
11896 (@code{gnus-server-open-server}).
11900 @findex gnus-server-close-server
11901 Close the connection (if any) to the server
11902 (@code{gnus-server-close-server}).
11906 @findex gnus-server-deny-server
11907 Mark the current server as unreachable
11908 (@code{gnus-server-deny-server}).
11911 @kindex M-o (Server)
11912 @findex gnus-server-open-all-servers
11913 Open the connections to all servers in the buffer
11914 (@code{gnus-server-open-all-servers}).
11917 @kindex M-c (Server)
11918 @findex gnus-server-close-all-servers
11919 Close the connections to all servers in the buffer
11920 (@code{gnus-server-close-all-servers}).
11924 @findex gnus-server-remove-denials
11925 Remove all marks to whether Gnus was denied connection from any servers
11926 (@code{gnus-server-remove-denials}).
11930 @findex gnus-server-offline-server
11931 Set server status to offline (@code{gnus-server-offline-server}).
11937 @section Getting News
11938 @cindex reading news
11939 @cindex news back ends
11941 A newsreader is normally used for reading news. Gnus currently provides
11942 only two methods of getting news---it can read from an @sc{nntp} server,
11943 or it can read from a local spool.
11946 * NNTP:: Reading news from an @sc{nntp} server.
11947 * News Spool:: Reading news from the local spool.
11955 Subscribing to a foreign group from an @sc{nntp} server is rather easy.
11956 You just specify @code{nntp} as method and the address of the @sc{nntp}
11957 server as the, uhm, address.
11959 If the @sc{nntp} server is located at a non-standard port, setting the
11960 third element of the select method to this port number should allow you
11961 to connect to the right port. You'll have to edit the group info for
11962 that (@pxref{Foreign Groups}).
11964 The name of the foreign group can be the same as a native group. In
11965 fact, you can subscribe to the same group from as many different servers
11966 you feel like. There will be no name collisions.
11968 The following variables can be used to create a virtual @code{nntp}
11973 @item nntp-server-opened-hook
11974 @vindex nntp-server-opened-hook
11975 @cindex @sc{mode reader}
11977 @cindex authentification
11978 @cindex nntp authentification
11979 @findex nntp-send-authinfo
11980 @findex nntp-send-mode-reader
11981 is run after a connection has been made. It can be used to send
11982 commands to the @sc{nntp} server after it has been contacted. By
11983 default it sends the command @code{MODE READER} to the server with the
11984 @code{nntp-send-mode-reader} function. This function should always be
11985 present in this hook.
11987 @item nntp-authinfo-function
11988 @vindex nntp-authinfo-function
11989 @findex nntp-send-authinfo
11990 @vindex nntp-authinfo-file
11991 This function will be used to send @samp{AUTHINFO} to the @sc{nntp}
11992 server. The default function is @code{nntp-send-authinfo}, which looks
11993 through your @file{~/.authinfo} (or whatever you've set the
11994 @code{nntp-authinfo-file} variable to) for applicable entries. If none
11995 are found, it will prompt you for a login name and a password. The
11996 format of the @file{~/.authinfo} file is (almost) the same as the
11997 @code{ftp} @file{~/.netrc} file, which is defined in the @code{ftp}
11998 manual page, but here are the salient facts:
12002 The file contains one or more line, each of which define one server.
12005 Each line may contain an arbitrary number of token/value pairs.
12007 The valid tokens include @samp{machine}, @samp{login}, @samp{password},
12008 @samp{default}. In addition Gnus introduces two new tokens, not present
12009 in the original @file{.netrc}/@code{ftp} syntax, namely @samp{port} and
12010 @samp{force}. (This is the only way the @file{.authinfo} file format
12011 deviates from the @file{.netrc} file format.) @samp{port} is used to
12012 indicate what port on the server the credentials apply to and
12013 @samp{force} is explained below.
12017 Here's an example file:
12020 machine news.uio.no login larsi password geheimnis
12021 machine nntp.ifi.uio.no login larsi force yes
12024 The token/value pairs may appear in any order; @samp{machine} doesn't
12025 have to be first, for instance.
12027 In this example, both login name and password have been supplied for the
12028 former server, while the latter has only the login name listed, and the
12029 user will be prompted for the password. The latter also has the
12030 @samp{force} tag, which means that the authinfo will be sent to the
12031 @var{nntp} server upon connection; the default (i.e., when there is not
12032 @samp{force} tag) is to not send authinfo to the @var{nntp} server
12033 until the @var{nntp} server asks for it.
12035 You can also add @samp{default} lines that will apply to all servers
12036 that don't have matching @samp{machine} lines.
12042 This will force sending @samp{AUTHINFO} commands to all servers not
12043 previously mentioned.
12045 Remember to not leave the @file{~/.authinfo} file world-readable.
12047 @item nntp-server-action-alist
12048 @vindex nntp-server-action-alist
12049 This is a list of regexps to match on server types and actions to be
12050 taken when matches are made. For instance, if you want Gnus to beep
12051 every time you connect to innd, you could say something like:
12054 (setq nntp-server-action-alist
12055 '(("innd" (ding))))
12058 You probably don't want to do that, though.
12060 The default value is
12063 '(("nntpd 1\\.5\\.11t"
12064 (remove-hook 'nntp-server-opened-hook
12065 'nntp-send-mode-reader)))
12068 This ensures that Gnus doesn't send the @code{MODE READER} command to
12069 nntpd 1.5.11t, since that command chokes that server, I've been told.
12071 @item nntp-maximum-request
12072 @vindex nntp-maximum-request
12073 If the @sc{nntp} server doesn't support @sc{nov} headers, this back end
12074 will collect headers by sending a series of @code{head} commands. To
12075 speed things up, the back end sends lots of these commands without
12076 waiting for reply, and then reads all the replies. This is controlled
12077 by the @code{nntp-maximum-request} variable, and is 400 by default. If
12078 your network is buggy, you should set this to 1.
12080 @item nntp-connection-timeout
12081 @vindex nntp-connection-timeout
12082 If you have lots of foreign @code{nntp} groups that you connect to
12083 regularly, you're sure to have problems with @sc{nntp} servers not
12084 responding properly, or being too loaded to reply within reasonable
12085 time. This is can lead to awkward problems, which can be helped
12086 somewhat by setting @code{nntp-connection-timeout}. This is an integer
12087 that says how many seconds the @code{nntp} back end should wait for a
12088 connection before giving up. If it is @code{nil}, which is the default,
12089 no timeouts are done.
12091 @c @item nntp-command-timeout
12092 @c @vindex nntp-command-timeout
12093 @c @cindex PPP connections
12094 @c @cindex dynamic IP addresses
12095 @c If you're running Gnus on a machine that has a dynamically assigned
12096 @c address, Gnus may become confused. If the address of your machine
12097 @c changes after connecting to the @sc{nntp} server, Gnus will simply sit
12098 @c waiting forever for replies from the server. To help with this
12099 @c unfortunate problem, you can set this command to a number. Gnus will
12100 @c then, if it sits waiting for a reply from the server longer than that
12101 @c number of seconds, shut down the connection, start a new one, and resend
12102 @c the command. This should hopefully be transparent to the user. A
12103 @c likely number is 30 seconds.
12105 @c @item nntp-retry-on-break
12106 @c @vindex nntp-retry-on-break
12107 @c If this variable is non-@code{nil}, you can also @kbd{C-g} if Gnus
12108 @c hangs. This will have much the same effect as the command timeout
12109 @c described above.
12111 @item nntp-server-hook
12112 @vindex nntp-server-hook
12113 This hook is run as the last step when connecting to an @sc{nntp}
12116 @item nntp-buggy-select
12117 @vindex nntp-buggy-select
12118 Set this to non-@code{nil} if your select routine is buggy.
12120 @item nntp-nov-is-evil
12121 @vindex nntp-nov-is-evil
12122 If the @sc{nntp} server does not support @sc{nov}, you could set this
12123 variable to @code{t}, but @code{nntp} usually checks automatically whether @sc{nov}
12126 @item nntp-xover-commands
12127 @vindex nntp-xover-commands
12130 List of strings used as commands to fetch @sc{nov} lines from a
12131 server. The default value of this variable is @code{("XOVER"
12135 @vindex nntp-nov-gap
12136 @code{nntp} normally sends just one big request for @sc{nov} lines to
12137 the server. The server responds with one huge list of lines. However,
12138 if you have read articles 2-5000 in the group, and only want to read
12139 article 1 and 5001, that means that @code{nntp} will fetch 4999 @sc{nov}
12140 lines that you will not need. This variable says how
12141 big a gap between two consecutive articles is allowed to be before the
12142 @code{XOVER} request is split into several request. Note that if your
12143 network is fast, setting this variable to a really small number means
12144 that fetching will probably be slower. If this variable is @code{nil},
12145 @code{nntp} will never split requests. The default is 5.
12147 @item nntp-prepare-server-hook
12148 @vindex nntp-prepare-server-hook
12149 A hook run before attempting to connect to an @sc{nntp} server.
12151 @item nntp-warn-about-losing-connection
12152 @vindex nntp-warn-about-losing-connection
12153 If this variable is non-@code{nil}, some noise will be made when a
12154 server closes connection.
12156 @item nntp-record-commands
12157 @vindex nntp-record-commands
12158 If non-@code{nil}, @code{nntp} will log all commands it sends to the
12159 @sc{nntp} server (along with a timestamp) in the @samp{*nntp-log*}
12160 buffer. This is useful if you are debugging a Gnus/@sc{nntp} connection
12161 that doesn't seem to work.
12163 @item nntp-open-connection-function
12164 @vindex nntp-open-connection-function
12165 It is possible to customize how the connection to the nntp server will
12166 be opened. If you specify an @code{nntp-open-connection-function}
12167 parameter, Gnus will use that function to establish the connection.
12168 Five pre-made functions are supplied. These functions can be grouped in
12169 two categories: direct connection functions (three pre-made), and
12170 indirect ones (two pre-made).
12172 @item nntp-prepare-post-hook
12173 @vindex nntp-prepare-post-hook
12174 A hook run just before posting an article. If there is no
12175 @code{Message-ID} header in the article and the news server provides the
12176 recommended ID, it will be added to the article before running this
12177 hook. It is useful to make @code{Cancel-Lock} headers even if you
12178 inhibit Gnus to add a @code{Message-ID} header, you could say:
12181 (add-hook 'nntp-prepare-post-hook 'canlock-insert-header)
12184 Note that not all servers support the recommended ID. This works for
12185 INN versions 2.3.0 and later, for instance.
12187 @item nntp-list-options
12188 @vindex nntp-list-options
12189 List of newsgroup name used for a option of the LIST command to restrict
12190 the listing output to only the specified newsgroups. Each newsgroup name
12191 can be a shell-style wildcard, for instance, @dfn{fj.*}, @dfn{japan.*},
12192 etc. Fortunately, if the server can accept such a option, it will
12193 probably make gnus run faster. You may use it as a server variable as
12197 (setq gnus-select-method
12198 '(nntp "news.somewhere.edu"
12199 (nntp-list-options ("fj.*" "japan.*"))))
12202 @item nntp-options-subscribe
12203 @vindex nntp-options-subscribe
12204 Regexp matching the newsgroup names which will be subscribed
12205 unconditionally. Use @dfn{ } instead of @dfn{$} for a regexp string.
12206 It may be effective as well as @code{nntp-list-options} even though the
12207 server could not accept a shell-style wildcard as a option of the LIST
12208 command. You may use it as a server variable as follows:
12211 (setq gnus-select-method
12212 '(nntp "news.somewhere.edu"
12213 (nntp-options-subscribe "^fj\\.\\|^japan\\.")))
12216 @item nntp-options-not-subscribe
12217 @vindex nntp-options-not-subscribe
12218 Regexp matching the newsgroup names which will not be subscribed
12219 unconditionally. Use @dfn{ } instead of @dfn{$} for a regexp string.
12220 It may be effective as well as @code{nntp-list-options} even though the
12221 server could not accept a shell-style wildcard as a option of the LIST
12222 command. You may use it as a server variable as follows:
12225 (setq gnus-select-method
12226 '(nntp "news.somewhere.edu"
12227 (nntp-options-not-subscribe "\\.binaries\\.")))
12232 * Direct Functions:: Connecting directly to the server.
12233 * Indirect Functions:: Connecting indirectly to the server.
12234 * Common Variables:: Understood by several connection functions.
12238 @node Direct Functions
12239 @subsubsection Direct Functions
12240 @cindex direct connection functions
12242 These functions are called direct because they open a direct connection
12243 between your machine and the @sc{nntp} server. The behavior of these
12244 functions is also affected by commonly understood variables
12245 (@pxref{Common Variables}).
12248 @findex nntp-open-network-stream
12249 @item nntp-open-network-stream
12250 This is the default, and simply connects to some port or other on the
12253 @findex nntp-open-ssl-stream
12254 @item nntp-open-ssl-stream
12255 Opens a connection to a server over a @dfn{secure} channel. To use
12256 this you must have OpenSSL (@uref{http://www.openssl.org}) or SSLeay
12257 installed (@uref{ftp://ftp.psy.uq.oz.au/pub/Crypto/SSL}, and you also
12258 need @file{ssl.el} (from the W3 distribution, for instance). You then
12259 define a server as follows:
12262 ;; Type `C-c C-c' after you've finished editing.
12264 ;; "snews" is port 563 and is predefined in our /etc/services
12265 ;; however, openssl s_client -port doesn't like named ports
12267 (nntp "snews.bar.com"
12268 (nntp-open-connection-function nntp-open-ssl-stream)
12269 (nntp-port-number 563)
12270 (nntp-address "snews.bar.com"))
12273 @findex nntp-open-telnet-stream
12274 @item nntp-open-telnet-stream
12275 Opens a connection to an @sc{nntp} server by simply @samp{telnet}'ing
12276 it. You might wonder why this function exists, since we have the
12277 default @code{nntp-open-network-stream} which would do the job. (One
12278 of) the reason(s) is that if you are behind a firewall but have direct
12279 connections to the outside world thanks to a command wrapper like
12280 @code{runsocks}, you can use it like this:
12284 (nntp-pre-command "runsocks")
12285 (nntp-open-connection-function nntp-open-telnet-stream)
12286 (nntp-address "the.news.server"))
12289 With the default method, you would need to wrap your whole Emacs
12290 session, which is not a good idea.
12294 @node Indirect Functions
12295 @subsubsection Indirect Functions
12296 @cindex indirect connection functions
12298 These functions are called indirect because they connect to an
12299 intermediate host before actually connecting to the @sc{nntp} server.
12300 All of these functions and related variables are also said to belong to
12301 the "via" family of connection: they're all prefixed with "via" to make
12302 things cleaner. The behavior of these functions is also affected by
12303 commonly understood variables (@pxref{Common Variables}).
12306 @item nntp-open-via-rlogin-and-telnet
12307 @findex nntp-open-via-rlogin-and-telnet
12308 Does an @samp{rlogin} on a remote system, and then does a @samp{telnet}
12309 to the real @sc{nntp} server from there. This is useful for instance if
12310 you need to connect to a firewall machine first.
12312 @code{nntp-open-via-rlogin-and-telnet}-specific variables:
12315 @item nntp-via-rlogin-command
12316 @vindex nntp-via-rlogin-command
12317 Command used to log in on the intermediate host. The default is
12318 @samp{rsh}, but @samp{ssh} is a popular alternative.
12320 @item nntp-via-rlogin-command-switches
12321 @vindex nntp-via-rlogin-command-switches
12322 List of strings to be used as the switches to
12323 @code{nntp-via-rlogin-command}. The default is @code{nil}. If you use
12324 @samp{ssh} for `nntp-via-rlogin-command', you may set this to
12325 @samp{("-C")} in order to compress all data connections, otherwise set
12326 this to @samp{("-t")} or @samp{("-C" "-t")} if the telnet command
12327 requires a pseudo-tty allocation on an intermediate host.
12330 @item nntp-open-via-telnet-and-telnet
12331 @findex nntp-open-via-telnet-and-telnet
12332 Does essentially the same, but uses @samp{telnet} instead of
12333 @samp{rlogin} to connect to the intermediate host.
12335 @code{nntp-open-via-telnet-and-telnet}-specific variables:
12338 @item nntp-via-telnet-command
12339 @vindex nntp-via-telnet-command
12340 Command used to @code{telnet} the intermediate host. The default is
12343 @item nntp-via-telnet-switches
12344 @vindex nntp-via-telnet-switches
12345 List of strings to be used as the switches to the
12346 @code{nntp-via-telnet-command} command. The default is @samp{("-8")}.
12348 @item nntp-via-user-password
12349 @vindex nntp-via-user-password
12350 Password to use when logging in on the intermediate host.
12352 @item nntp-via-envuser
12353 @vindex nntp-via-envuser
12354 If non-@code{nil}, the intermediate @code{telnet} session (client and
12355 server both) will support the @code{ENVIRON} option and not prompt for
12356 login name. This works for Solaris @code{telnet}, for instance.
12358 @item nntp-via-shell-prompt
12359 @vindex nntp-via-shell-prompt
12360 Regexp matching the shell prompt on the intermediate host. The default
12361 is @samp{bash\\|\$ *\r?$\\|> *\r?}.
12368 Here are some additional variables that are understood by all the above
12373 @item nntp-via-user-name
12374 @vindex nntp-via-user-name
12375 User name to use when connecting to the intermediate host.
12377 @item nntp-via-address
12378 @vindex nntp-via-address
12379 Address of the intermediate host to connect to.
12384 @node Common Variables
12385 @subsubsection Common Variables
12387 The following variables affect the behavior of all, or several of the
12388 pre-made connection functions. When not specified, all functions are
12393 @item nntp-pre-command
12394 @vindex nntp-pre-command
12395 A command wrapper to use when connecting through a non native connection
12396 function (all except @code{nntp-open-network-stream} and
12397 @code{nntp-open-ssl-stream}. This is where you would put a @samp{SOCKS}
12398 wrapper for instance.
12401 @vindex nntp-address
12402 The address of the @sc{nntp} server.
12404 @item nntp-port-number
12405 @vindex nntp-port-number
12406 Port number to connect to the @sc{nntp} server. The default is @samp{nntp}.
12407 If you use @sc{nntp} over @sc{ssl}, you may want to use integer ports rather
12408 than named ports (i.e, use @samp{563} instead of @samp{snews}), because
12409 external SSL tools may not work with named ports.
12411 @item nntp-end-of-line
12412 @vindex nntp-end-of-line
12413 String to use as end-of-line marker when talking to the @sc{nntp}
12414 server. This is @samp{\r\n} by default, but should be @samp{\n} when
12415 using a non native connection function.
12417 @item nntp-telnet-command
12418 @vindex nntp-telnet-command
12419 Command to use when connecting to the @sc{nntp} server through
12420 @samp{telnet}. This is NOT for an intermediate host. This is just for
12421 the real @sc{nntp} server. The default is @samp{telnet}.
12423 @item nntp-telnet-switches
12424 @vindex nntp-telnet-switches
12425 A list of switches to pass to @code{nntp-telnet-command}. The default
12432 @subsection News Spool
12436 Subscribing to a foreign group from the local spool is extremely easy,
12437 and might be useful, for instance, to speed up reading groups that
12438 contain very big articles---@samp{alt.binaries.pictures.furniture}, for
12441 Anyway, you just specify @code{nnspool} as the method and @code{""} (or
12442 anything else) as the address.
12444 If you have access to a local spool, you should probably use that as the
12445 native select method (@pxref{Finding the News}). It is normally faster
12446 than using an @code{nntp} select method, but might not be. It depends.
12447 You just have to try to find out what's best at your site.
12451 @item nnspool-inews-program
12452 @vindex nnspool-inews-program
12453 Program used to post an article.
12455 @item nnspool-inews-switches
12456 @vindex nnspool-inews-switches
12457 Parameters given to the inews program when posting an article.
12459 @item nnspool-spool-directory
12460 @vindex nnspool-spool-directory
12461 Where @code{nnspool} looks for the articles. This is normally
12462 @file{/usr/spool/news/}.
12464 @item nnspool-nov-directory
12465 @vindex nnspool-nov-directory
12466 Where @code{nnspool} will look for @sc{nov} files. This is normally
12467 @file{/usr/spool/news/over.view/}.
12469 @item nnspool-lib-dir
12470 @vindex nnspool-lib-dir
12471 Where the news lib dir is (@file{/usr/lib/news/} by default).
12473 @item nnspool-active-file
12474 @vindex nnspool-active-file
12475 The path to the active file.
12477 @item nnspool-newsgroups-file
12478 @vindex nnspool-newsgroups-file
12479 The path to the group descriptions file.
12481 @item nnspool-history-file
12482 @vindex nnspool-history-file
12483 The path to the news history file.
12485 @item nnspool-active-times-file
12486 @vindex nnspool-active-times-file
12487 The path to the active date file.
12489 @item nnspool-nov-is-evil
12490 @vindex nnspool-nov-is-evil
12491 If non-@code{nil}, @code{nnspool} won't try to use any @sc{nov} files
12494 @item nnspool-sift-nov-with-sed
12495 @vindex nnspool-sift-nov-with-sed
12497 If non-@code{nil}, which is the default, use @code{sed} to get the
12498 relevant portion from the overview file. If nil, @code{nnspool} will
12499 load the entire file into a buffer and process it there.
12505 @section Getting Mail
12506 @cindex reading mail
12509 Reading mail with a newsreader---isn't that just plain WeIrD? But of
12513 * Mail in a Newsreader:: Important introductory notes.
12514 * Getting Started Reading Mail:: A simple cookbook example.
12515 * Splitting Mail:: How to create mail groups.
12516 * Mail Sources:: How to tell Gnus where to get mail from.
12517 * Mail Back End Variables:: Variables for customizing mail handling.
12518 * Fancy Mail Splitting:: Gnus can do hairy splitting of incoming mail.
12519 * Group Mail Splitting:: Use group customize to drive mail splitting.
12520 * Incorporating Old Mail:: What about the old mail you have?
12521 * Expiring Mail:: Getting rid of unwanted mail.
12522 * Washing Mail:: Removing gruft from the mail you get.
12523 * Duplicates:: Dealing with duplicated mail.
12524 * Not Reading Mail:: Using mail back ends for reading other files.
12525 * Choosing a Mail Back End:: Gnus can read a variety of mail formats.
12529 @node Mail in a Newsreader
12530 @subsection Mail in a Newsreader
12532 If you are used to traditional mail readers, but have decided to switch
12533 to reading mail with Gnus, you may find yourself experiencing something
12534 of a culture shock.
12536 Gnus does not behave like traditional mail readers. If you want to make
12537 it behave that way, you can, but it's an uphill battle.
12539 Gnus, by default, handles all its groups using the same approach. This
12540 approach is very newsreaderly---you enter a group, see the new/unread
12541 messages, and when you read the messages, they get marked as read, and
12542 you don't see them any more. (Unless you explicitly ask for them.)
12544 In particular, you do not do anything explicitly to delete messages.
12546 Does this mean that all the messages that have been marked as read are
12547 deleted? How awful!
12549 But, no, it means that old messages are @dfn{expired} according to some
12550 scheme or other. For news messages, the expire process is controlled by
12551 the news administrator; for mail, the expire process is controlled by
12552 you. The expire process for mail is covered in depth in @pxref{Expiring
12555 What many Gnus users find, after using it a while for both news and
12556 mail, is that the transport mechanism has very little to do with how
12557 they want to treat a message.
12559 Many people subscribe to several mailing lists. These are transported
12560 via @sc{smtp}, and are therefore mail. But we might go for weeks without
12561 answering, or even reading these messages very carefully. We may not
12562 need to save them because if we should need to read one again, they are
12563 archived somewhere else.
12565 Some people have local news groups which have only a handful of readers.
12566 These are transported via @sc{nntp}, and are therefore news. But we may need
12567 to read and answer a large fraction of the messages very carefully in
12568 order to do our work. And there may not be an archive, so we may need
12569 to save the interesting messages the same way we would personal mail.
12571 The important distinction turns out to be not the transport mechanism,
12572 but other factors such as how interested we are in the subject matter,
12573 or how easy it is to retrieve the message if we need to read it again.
12575 Gnus provides many options for sorting mail into ``groups'' which behave
12576 like newsgroups, and for treating each group (whether mail or news)
12579 Some users never get comfortable using the Gnus (ahem) paradigm and wish
12580 that Gnus should grow up and be a male, er, mail reader. It is possible
12581 to whip Gnus into a more mailreaderly being, but, as said before, it's
12582 not easy. People who prefer proper mail readers should try @sc{vm}
12583 instead, which is an excellent, and proper, mail reader.
12585 I don't mean to scare anybody off, but I want to make it clear that you
12586 may be required to learn a new way of thinking about messages. After
12587 you've been subjected to The Gnus Way, you will come to love it. I can
12588 guarantee it. (At least the guy who sold me the Emacs Subliminal
12589 Brain-Washing Functions that I've put into Gnus did guarantee it. You
12590 Will Be Assimilated. You Love Gnus. You Love The Gnus Mail Way.
12594 @node Getting Started Reading Mail
12595 @subsection Getting Started Reading Mail
12597 It's quite easy to use Gnus to read your new mail. You just plonk the
12598 mail back end of your choice into @code{gnus-secondary-select-methods},
12599 and things will happen automatically.
12601 For instance, if you want to use @code{nnml} (which is a "one file per
12602 mail" back end), you could put the following in your @file{.gnus.el} file:
12605 (setq gnus-secondary-select-methods '((nnml "")))
12608 Now, the next time you start Gnus, this back end will be queried for new
12609 articles, and it will move all the messages in your spool file to its
12610 directory, which is @code{~/Mail/} by default. The new group that will
12611 be created (@samp{mail.misc}) will be subscribed, and you can read it
12612 like any other group.
12614 You will probably want to split the mail into several groups, though:
12617 (setq nnmail-split-methods
12618 '(("junk" "^From:.*Lars Ingebrigtsen")
12619 ("crazy" "^Subject:.*die\\|^Organization:.*flabby")
12623 This will result in three new @code{nnml} mail groups being created:
12624 @samp{nnml:junk}, @samp{nnml:crazy}, and @samp{nnml:other}. All the
12625 mail that doesn't fit into the first two groups will be placed in the
12628 This should be sufficient for reading mail with Gnus. You might want to
12629 give the other sections in this part of the manual a perusal, though.
12630 Especially @pxref{Choosing a Mail Back End} and @pxref{Expiring Mail}.
12633 @node Splitting Mail
12634 @subsection Splitting Mail
12635 @cindex splitting mail
12636 @cindex mail splitting
12638 @vindex nnmail-split-methods
12639 The @code{nnmail-split-methods} variable says how the incoming mail is
12640 to be split into groups.
12643 (setq nnmail-split-methods
12644 '(("mail.junk" "^From:.*Lars Ingebrigtsen")
12645 ("mail.crazy" "^Subject:.*die\\|^Organization:.*flabby")
12646 ("mail.other" "")))
12649 This variable is a list of lists, where the first element of each of
12650 these lists is the name of the mail group (they do not have to be called
12651 something beginning with @samp{mail}, by the way), and the second
12652 element is a regular expression used on the header of each mail to
12653 determine if it belongs in this mail group. The first string may
12654 contain @samp{\\1} forms, like the ones used by @code{replace-match} to
12655 insert sub-expressions from the matched text. For instance:
12658 ("list.\\1" "From:.* \\(.*\\)-list@@majordomo.com")
12661 The second element can also be a function. In that case, it will be
12662 called narrowed to the headers with the first element of the rule as the
12663 argument. It should return a non-@code{nil} value if it thinks that the
12664 mail belongs in that group.
12666 The last of these groups should always be a general one, and the regular
12667 expression should @emph{always} be @samp{} so that it matches any mails
12668 that haven't been matched by any of the other regexps. (These rules are
12669 processed from the beginning of the alist toward the end. The first
12670 rule to make a match will "win", unless you have crossposting enabled.
12671 In that case, all matching rules will "win".)
12673 If you like to tinker with this yourself, you can set this variable to a
12674 function of your choice. This function will be called without any
12675 arguments in a buffer narrowed to the headers of an incoming mail
12676 message. The function should return a list of group names that it
12677 thinks should carry this mail message.
12679 Note that the mail back ends are free to maul the poor, innocent,
12680 incoming headers all they want to. They all add @code{Lines} headers;
12681 some add @code{X-Gnus-Group} headers; most rename the Unix mbox
12682 @code{From<SPACE>} line to something else.
12684 @vindex nnmail-crosspost
12685 The mail back ends all support cross-posting. If several regexps match,
12686 the mail will be ``cross-posted'' to all those groups.
12687 @code{nnmail-crosspost} says whether to use this mechanism or not. Note
12688 that no articles are crossposted to the general (@samp{}) group.
12690 @vindex nnmail-crosspost-link-function
12693 @code{nnmh} and @code{nnml} makes crossposts by creating hard links to
12694 the crossposted articles. However, not all file systems support hard
12695 links. If that's the case for you, set
12696 @code{nnmail-crosspost-link-function} to @code{copy-file}. (This
12697 variable is @code{add-name-to-file} by default.)
12699 @kindex M-x nnmail-split-history
12700 @kindex nnmail-split-history
12701 If you wish to see where the previous mail split put the messages, you
12702 can use the @kbd{M-x nnmail-split-history} command. If you wish to see
12703 where re-spooling messages would put the messages, you can use
12704 @code{gnus-summary-respool-trace} and related commands (@pxref{Mail
12707 @vindex nnmail-split-header-length-limit
12708 Header lines longer than the value of
12709 @code{nnmail-split-header-length-limit} are excluded from the split
12712 @vindex nnmail-mail-splitting-charset
12713 @vindex nnmail-mail-splitting-decodes
12714 By default the splitting codes MIME decodes headers so you can match
12715 on non-ASCII strings. The @code{nnmail-mail-splitting-charset}
12716 variable specifies the default charset for decoding. The behaviour
12717 can be turned off completely by binding
12718 @code{nnmail-mail-splitting-decodes} to nil, which is useful if you
12719 want to match articles based on the raw header data.
12721 @vindex nnmail-resplit-incoming
12722 By default, splitting is performed on all incoming messages. If
12723 you specify a @code{directory} entry for the variable
12724 @code{mail-sources} @pxref{Mail Source Specifiers}, however, then
12725 splitting does @emph{not} happen by default. You can set the variable
12726 @code{nnmail-resplit-incoming} to a non-nil value to make splitting
12727 happen even in this case. (This variable has no effect on other kinds
12730 Gnus gives you all the opportunity you could possibly want for shooting
12731 yourself in the foot. Let's say you create a group that will contain
12732 all the mail you get from your boss. And then you accidentally
12733 unsubscribe from the group. Gnus will still put all the mail from your
12734 boss in the unsubscribed group, and so, when your boss mails you ``Have
12735 that report ready by Monday or you're fired!'', you'll never see it and,
12736 come Tuesday, you'll still believe that you're gainfully employed while
12737 you really should be out collecting empty bottles to save up for next
12738 month's rent money.
12742 @subsection Mail Sources
12744 Mail can be gotten from many different sources---the mail spool, from a
12745 POP mail server, from a procmail directory, or from a maildir, for
12749 * Mail Source Specifiers:: How to specify what a mail source is.
12750 * Mail Source Customization:: Some variables that influence things.
12751 * Fetching Mail:: Using the mail source specifiers.
12755 @node Mail Source Specifiers
12756 @subsubsection Mail Source Specifiers
12758 @cindex mail server
12761 @cindex mail source
12763 You tell Gnus how to fetch mail by setting @code{mail-sources}
12764 (@pxref{Fetching Mail}) to a @dfn{mail source specifier}.
12769 (pop :server "pop3.mailserver.com" :user "myname")
12772 As can be observed, a mail source specifier is a list where the first
12773 element is a @dfn{mail source type}, followed by an arbitrary number of
12774 @dfn{keywords}. Keywords that are not explicitly specified are given
12777 The following mail source types are available:
12781 Get mail from a single file; typically from the mail spool.
12787 The path of the file. Defaults to the value of the @code{MAIL}
12788 environment variable or the value of @code{rmail-spool-directory}
12789 (usually something like @file{/usr/mail/spool/user-name}).
12792 An example file mail source:
12795 (file :path "/usr/spool/mail/user-name")
12798 Or using the default path:
12804 If the mail spool file is not located on the local machine, it's best to
12805 use POP or @sc{imap} or the like to fetch the mail. You can not use ange-ftp
12806 file names here---it has no way to lock the mail spool while moving the
12809 If it's impossible to set up a proper server, you can use ssh instead.
12813 '((file :prescript "ssh host bin/getmail >%t")))
12816 The @samp{getmail} script would look something like the following:
12820 # getmail - move mail from spool to stdout
12823 MOVEMAIL=/usr/lib/emacs/20.3/i386-redhat-linux/movemail
12825 rm -f $TMP; $MOVEMAIL $MAIL $TMP >/dev/null && cat $TMP
12828 Alter this script to fit find the @samp{movemail} you want to use.
12832 @vindex nnmail-scan-directory-mail-source-once
12833 Get mail from several files in a directory. This is typically used when
12834 you have procmail split the incoming mail into several files. That is,
12835 there is a one-to-one correspondence between files in that directory and
12836 groups, so that mail from the file @file{foo.bar.spool} will be put in
12837 the group @code{foo.bar}. (You can change the suffix to be used instead
12838 of @code{.spool}.) Setting
12839 @code{nnmail-scan-directory-mail-source-once} to non-nil forces Gnus to
12840 scan the mail source only once. This is particularly useful if you want
12841 to scan mail groups at a specified level.
12843 @vindex nnmail-resplit-incoming
12844 There is also the variable @code{nnmail-resplit-incoming}, if you set
12845 that to a non-nil value, then the normal splitting process is applied
12846 to all the files from the directory, @ref{Splitting Mail}.
12852 The path of the directory where the files are. There is no default
12856 Only files ending with this suffix are used. The default is
12860 Only files that have this predicate return non-@code{nil} are returned.
12861 The default is @code{identity}. This is used as an additional
12862 filter---only files that have the right suffix @emph{and} satisfy this
12863 predicate are considered.
12867 Script run before/after fetching mail.
12871 An example directory mail source:
12874 (directory :path "/home/user-name/procmail-dir/"
12879 Get mail from a POP server.
12885 The name of the POP server. The default is taken from the
12886 @code{MAILHOST} environment variable.
12889 The port number of the POP server. This can be a number (eg,
12890 @samp{:port 1234}) or a string (eg, @samp{:port "pop3"}). If it is a
12891 string, it should be a service name as listed in @file{/etc/services} on
12892 Unix systems. The default is @samp{"pop3"}. On some systems you might
12893 need to specify it as @samp{"pop-3"} instead.
12896 The user name to give to the POP server. The default is the login
12900 The password to give to the POP server. If not specified, the user is
12904 The program to use to fetch mail from the POP server. This should be
12905 a @code{format}-like string. Here's an example:
12908 fetchmail %u@@%s -P %p %t
12911 The valid format specifier characters are:
12915 The name of the file the mail is to be moved to. This must always be
12916 included in this string.
12919 The name of the server.
12922 The port number of the server.
12925 The user name to use.
12928 The password to use.
12931 The values used for these specs are taken from the values you give the
12932 corresponding keywords.
12935 A script to be run before fetching the mail. The syntax is the same as
12936 the @code{:program} keyword. This can also be a function to be run.
12939 A script to be run after fetching the mail. The syntax is the same as
12940 the @code{:program} keyword. This can also be a function to be run.
12943 The function to use to fetch mail from the POP server. The function is
12944 called with one parameter---the name of the file where the mail should
12947 @item :authentication
12948 This can be either the symbol @code{password} or the symbol @code{apop}
12949 and says what authentication scheme to use. The default is
12953 What stream to use for connecting to the server, this can be the symbol
12954 @code{ssl}, the symbol @code{tls} or others. The default is @code{nil}
12955 and use insecure connections. Note that for SSL/TLS, you need external
12956 programs and libraries:
12960 @dfn{ssl:} Connect through SSL@. Requires OpenSSL (the program
12961 @samp{openssl}) or SSLeay (@samp{s_client}) as well as the external
12962 library @samp{ssl.el}.
12964 @dfn{starttls:} Connect via the STARTTLS extension (similar to SSL)@.
12965 Requires the external library @samp{starttls.el} and program
12970 Non-@code{nil} if mail is to be left on the server and UIDL used for
12971 message retrieval. The default is @code{nil}.
12975 If the @code{:program} and @code{:function} keywords aren't specified,
12976 @code{pop3-movemail} will be used.
12978 Here are some examples. Fetch from the default POP server, using the
12979 default user name, and default fetcher:
12985 Fetch from a named server with a named user and password:
12988 (pop :server "my.pop.server"
12989 :user "user-name" :password "secret")
12992 Use @samp{movemail} to move the mail:
12995 (pop :program "movemail po:%u %t %p")
12999 Get mail from a maildir. This is a type of mailbox that is supported by
13000 at least qmail and postfix, where each file in a special directory
13001 contains exactly one mail.
13007 The path of the directory where the mails are stored. The default is
13008 taken from the @code{MAILDIR} environment variable or
13011 The subdirectories of the Maildir. The default is
13012 @samp{("new" "cur")}.
13014 @c If you sometimes look at your mail through a pop3 daemon before fetching
13015 @c them with Gnus, you may also have to fetch your mails from the
13016 @c @code{cur} directory inside the maildir, like in the first example
13019 You can also get mails from remote hosts (because maildirs don't suffer
13020 from locking problems).
13024 Two example maildir mail sources:
13027 (maildir :path "/home/user-name/Maildir/"
13028 :subdirs ("cur" "new"))
13032 (maildir :path "/user@@remotehost.org:~/Maildir/"
13037 Get mail from a @sc{imap} server. If you don't want to use @sc{imap}
13038 as intended, as a network mail reading protocol (ie with nnimap), for
13039 some reason or other, Gnus let you treat it similar to a POP server
13040 and fetches articles from a given @sc{imap} mailbox. @xref{IMAP}, for
13043 Note that for the Kerberos, GSSAPI, SSL/TLS and STARTTLS support you
13044 may need external programs and libraries, @xref{IMAP}.
13050 The name of the @sc{imap} server. The default is taken from the
13051 @code{MAILHOST} environment variable.
13054 The port number of the @sc{imap} server. The default is @samp{143}, or
13055 @samp{993} for SSL/TLS connections.
13058 The user name to give to the @sc{imap} server. The default is the login
13062 The password to give to the @sc{imap} server. If not specified, the user is
13066 What stream to use for connecting to the server, this is one of the
13067 symbols in @code{imap-stream-alist}. Right now, this means
13068 @samp{gssapi}, @samp{kerberos4}, @samp{starttls}, @samp{ssl},
13069 @samp{shell} or the default @samp{network}.
13071 @item :authentication
13072 Which authenticator to use for authenticating to the server, this is
13073 one of the symbols in @code{imap-authenticator-alist}. Right now,
13074 this means @samp{gssapi}, @samp{kerberos4}, @samp{digest-md5},
13075 @samp{cram-md5}, @samp{anonymous} or the default @samp{login}.
13078 When using the `shell' :stream, the contents of this variable is
13079 mapped into the `imap-shell-program' variable. This should be a
13080 @code{format}-like string (or list of strings). Here's an example:
13086 The valid format specifier characters are:
13090 The name of the server.
13093 User name from `imap-default-user'.
13096 The port number of the server.
13099 The values used for these specs are taken from the values you give the
13100 corresponding keywords.
13103 The name of the mailbox to get mail from. The default is @samp{INBOX}
13104 which normally is the mailbox which receive incoming mail.
13107 The predicate used to find articles to fetch. The default, @samp{UNSEEN
13108 UNDELETED}, is probably the best choice for most people, but if you
13109 sometimes peek in your mailbox with a @sc{imap} client and mark some
13110 articles as read (or; SEEN) you might want to set this to @samp{1:*}.
13111 Then all articles in the mailbox is fetched, no matter what. For a
13112 complete list of predicates, see RFC 2060 section 6.4.4.
13115 How to flag fetched articles on the server, the default @samp{\Deleted}
13116 will mark them as deleted, an alternative would be @samp{\Seen} which
13117 would simply mark them as read. These are the two most likely choices,
13118 but more flags are defined in RFC 2060 section 2.3.2.
13121 If non-nil, don't remove all articles marked as deleted in the mailbox
13122 after finishing the fetch.
13126 An example @sc{imap} mail source:
13129 (imap :server "mail.mycorp.com"
13131 :fetchflag "\\Seen")
13135 Get mail from a webmail server, such as @uref{www.hotmail.com},
13136 @uref{webmail.netscape.com}, @uref{www.netaddress.com},
13137 @uref{mail.yahoo..com}.
13139 NOTE: Webmail largely depends cookies. A "one-line-cookie" patch is
13140 required for url "4.0pre.46".
13142 WARNING: Mails may be lost. NO WARRANTY.
13148 The type of the webmail server. The default is @code{hotmail}. The
13149 alternatives are @code{netscape}, @code{netaddress}, @code{my-deja}.
13152 The user name to give to the webmail server. The default is the login
13156 The password to give to the webmail server. If not specified, the user is
13160 If non-nil, only fetch unread articles and don't move them to trash
13161 folder after finishing the fetch.
13165 An example webmail source:
13168 (webmail :subtype 'hotmail
13170 :password "secret")
13175 @item Common Keywords
13176 Common keywords can be used in any type of mail source.
13182 If non-nil, fetch the mail even when Gnus is unplugged. If you use
13183 directory source to get mail, you can specify it as in this example:
13187 '((directory :path "/home/pavel/.Spool/"
13192 Gnus will then fetch your mail even when you are unplugged. This is
13193 useful when you use local mail and news.
13198 @subsubsection Function Interface
13200 Some of the above keywords specify a Lisp function to be executed.
13201 For each keyword @code{:foo}, the Lisp variable @code{foo} is bound to
13202 the value of the keyword while the function is executing. For example,
13203 consider the following mail-source setting:
13206 (setq mail-sources '((pop :user "jrl"
13207 :server "pophost" :function fetchfunc)))
13210 While the function @code{fetchfunc} is executing, the symbol @code{user}
13211 is bound to @code{"jrl"}, and the symbol @code{server} is bound to
13212 @code{"pophost"}. The symbols @code{port}, @code{password},
13213 @code{program}, @code{prescript}, @code{postscript}, @code{function},
13214 and @code{authentication} are also bound (to their default values).
13216 See above for a list of keywords for each type of mail source.
13219 @node Mail Source Customization
13220 @subsubsection Mail Source Customization
13222 The following is a list of variables that influence how the mail is
13223 fetched. You would normally not need to set or change any of these
13227 @item mail-source-crash-box
13228 @vindex mail-source-crash-box
13229 File where mail will be stored while processing it. The default is
13230 @file{~/.emacs-mail-crash-box}.
13232 @item mail-source-delete-incoming
13233 @vindex mail-source-delete-incoming
13234 If non-@code{nil}, delete incoming files after handling them.
13236 @item mail-source-directory
13237 @vindex mail-source-directory
13238 Directory where files (if any) will be stored. The default is
13239 @file{~/Mail/}. At present, the only thing this is used for is to say
13240 where the incoming files will be stored if the previous variable is
13243 @item mail-source-incoming-file-prefix
13244 @vindex mail-source-incoming-file-prefix
13245 Prefix for file name for storing incoming mail. The default is
13246 @file{Incoming}, in which case files will end up with names like
13247 @file{Incoming30630D_} or @file{Incoming298602ZD}. This is really only
13248 relevant if @code{mail-source-delete-incoming} is @code{nil}.
13250 @item mail-source-default-file-modes
13251 @vindex mail-source-default-file-modes
13252 All new mail files will get this file mode. The default is 384.
13254 @item mail-source-movemail-program
13255 @vindex mail-source-movemail-program
13256 If non-nil, name of program for fetching new mail. If nil,
13257 @code{movemail} in @var{exec-directory}.
13262 @node Fetching Mail
13263 @subsubsection Fetching Mail
13265 @vindex mail-sources
13266 @vindex nnmail-spool-file
13267 The way to actually tell Gnus where to get new mail from is to set
13268 @code{mail-sources} to a list of mail source specifiers
13269 (@pxref{Mail Source Specifiers}).
13271 If this variable (and the obsolescent @code{nnmail-spool-file}) is
13272 @code{nil}, the mail back ends will never attempt to fetch mail by
13275 If you want to fetch mail both from your local spool as well as a POP
13276 mail server, you'd say something like:
13281 (pop :server "pop3.mail.server"
13282 :password "secret")))
13285 Or, if you don't want to use any of the keyword defaults:
13289 '((file :path "/var/spool/mail/user-name")
13290 (pop :server "pop3.mail.server"
13293 :password "secret")))
13297 When you use a mail back end, Gnus will slurp all your mail from your
13298 inbox and plonk it down in your home directory. Gnus doesn't move any
13299 mail if you're not using a mail back end---you have to do a lot of magic
13300 invocations first. At the time when you have finished drawing the
13301 pentagram, lightened the candles, and sacrificed the goat, you really
13302 shouldn't be too surprised when Gnus moves your mail.
13306 @node Mail Back End Variables
13307 @subsection Mail Back End Variables
13309 These variables are (for the most part) pertinent to all the various
13313 @vindex nnmail-read-incoming-hook
13314 @item nnmail-read-incoming-hook
13315 The mail back ends all call this hook after reading new mail. You can
13316 use this hook to notify any mail watch programs, if you want to.
13318 @vindex nnmail-split-hook
13319 @item nnmail-split-hook
13320 @findex article-decode-encoded-words
13321 @findex RFC 1522 decoding
13322 @findex RFC 2047 decoding
13323 Hook run in the buffer where the mail headers of each message is kept
13324 just before the splitting based on these headers is done. The hook is
13325 free to modify the buffer contents in any way it sees fit---the buffer
13326 is discarded after the splitting has been done, and no changes performed
13327 in the buffer will show up in any files.
13328 @code{gnus-article-decode-encoded-words} is one likely function to add
13331 @vindex nnmail-pre-get-new-mail-hook
13332 @vindex nnmail-post-get-new-mail-hook
13333 @item nnmail-pre-get-new-mail-hook
13334 @itemx nnmail-post-get-new-mail-hook
13335 These are two useful hooks executed when treating new incoming
13336 mail---@code{nnmail-pre-get-new-mail-hook} (is called just before
13337 starting to handle the new mail) and
13338 @code{nnmail-post-get-new-mail-hook} (is called when the mail handling
13339 is done). Here's and example of using these two hooks to change the
13340 default file modes the new mail files get:
13343 (add-hook 'nnmail-pre-get-new-mail-hook
13344 (lambda () (set-default-file-modes 511)))
13346 (add-hook 'nnmail-post-get-new-mail-hook
13347 (lambda () (set-default-file-modes 551)))
13350 @item nnmail-use-long-file-names
13351 @vindex nnmail-use-long-file-names
13352 If non-@code{nil}, the mail back ends will use long file and directory
13353 names. Groups like @samp{mail.misc} will end up in directories
13354 (assuming use of @code{nnml} back end) or files (assuming use of
13355 @code{nnfolder} back end) like @file{mail.misc}. If it is @code{nil},
13356 the same group will end up in @file{mail/misc}.
13358 @item nnmail-delete-file-function
13359 @vindex nnmail-delete-file-function
13360 @findex delete-file
13361 Function called to delete files. It is @code{delete-file} by default.
13363 @item nnmail-cache-accepted-message-ids
13364 @vindex nnmail-cache-accepted-message-ids
13365 If non-@code{nil}, put the @code{Message-ID}s of articles imported into
13366 the back end (via @code{Gcc}, for instance) into the mail duplication
13367 discovery cache. The default is @code{nil}.
13369 @item nnmail-cache-ignore-groups
13370 @vindex nnmail-cache-ignore-groups
13371 This can be a regular expression or a list of regular expressions.
13372 Group names that match any of the regular expressions will never be
13373 recorded in the @code{Message-ID} cache.
13375 This can be useful, for example, when using Fancy Splitting
13376 (@pxref{Fancy Mail Splitting}) together with the function
13377 @code{nnmail-split-fancy-with-parent}.
13382 @node Fancy Mail Splitting
13383 @subsection Fancy Mail Splitting
13384 @cindex mail splitting
13385 @cindex fancy mail splitting
13387 @vindex nnmail-split-fancy
13388 @findex nnmail-split-fancy
13389 If the rather simple, standard method for specifying how to split mail
13390 doesn't allow you to do what you want, you can set
13391 @code{nnmail-split-methods} to @code{nnmail-split-fancy}. Then you can
13392 play with the @code{nnmail-split-fancy} variable.
13394 Let's look at an example value of this variable first:
13397 ;; Messages from the mailer daemon are not crossposted to any of
13398 ;; the ordinary groups. Warnings are put in a separate group
13399 ;; from real errors.
13400 (| ("from" mail (| ("subject" "warn.*" "mail.warning")
13402 ;; Non-error messages are crossposted to all relevant
13403 ;; groups, but we don't crosspost between the group for the
13404 ;; (ding) list and the group for other (ding) related mail.
13405 (& (| (any "ding@@ifi\\.uio\\.no" "ding.list")
13406 ("subject" "ding" "ding.misc"))
13407 ;; Other mailing lists...
13408 (any "procmail@@informatik\\.rwth-aachen\\.de" "procmail.list")
13409 (any "SmartList@@informatik\\.rwth-aachen\\.de" "SmartList.list")
13410 ;; Both lists below have the same suffix, so prevent
13411 ;; cross-posting to mkpkg.list of messages posted only to
13412 ;; the bugs- list, but allow cross-posting when the
13413 ;; message was really cross-posted.
13414 (any "bugs-mypackage@@somewhere" "mypkg.bugs")
13415 (any "mypackage@@somewhere\" - "bugs-mypackage" "mypkg.list")
13417 (any "larsi@@ifi\\.uio\\.no" "people.Lars_Magne_Ingebrigtsen"))
13418 ;; Unmatched mail goes to the catch all group.
13422 This variable has the format of a @dfn{split}. A split is a (possibly)
13423 recursive structure where each split may contain other splits. Here are
13424 the five possible split syntaxes:
13429 @samp{group}: If the split is a string, that will be taken as a group
13430 name. Normal regexp match expansion will be done. See below for
13434 @code{(@var{field} @var{value} @code{[-} @var{restrict}
13435 @code{[@dots{}]}@code{]} @var{split})}: If the split is a list, the
13436 first element of which is a string, then store the message as
13437 specified by @var{split}, if header @var{field} (a regexp) contains
13438 @var{value} (also a regexp). If @var{restrict} (yet another regexp)
13439 matches some string after @var{field} and before the end of the
13440 matched @var{value}, the @var{split} is ignored. If none of the
13441 @var{restrict} clauses match, @var{split} is processed.
13444 @code{(| @var{split}@dots{})}: If the split is a list, and the first
13445 element is @code{|} (vertical bar), then process each @var{split} until
13446 one of them matches. A @var{split} is said to match if it will cause
13447 the mail message to be stored in one or more groups.
13450 @code{(& @var{split}@dots{})}: If the split is a list, and the first
13451 element is @code{&}, then process all @var{split}s in the list.
13454 @code{junk}: If the split is the symbol @code{junk}, then don't save
13455 (i.e., delete) this message. Use with extreme caution.
13458 @code{(: @var{function} @var{arg1} @var{arg2} @dots{})}: If the split is
13459 a list, and the first element is @code{:}, then the second element will
13460 be called as a function with @var{args} given as arguments. The
13461 function should return a @var{split}.
13464 For instance, the following function could be used to split based on the
13465 body of the messages:
13468 (defun split-on-body ()
13470 (set-buffer " *nnmail incoming*")
13471 (goto-char (point-min))
13472 (when (re-search-forward "Some.*string" nil t)
13476 The @samp{" *nnmail incoming*"} is narrowed to the message in question
13477 when the @code{:} function is run.
13480 @code{(! @var{func} @var{split})}: If the split is a list, and the first
13481 element is @code{!}, then SPLIT will be processed, and FUNC will be
13482 called as a function with the result of SPLIT as argument. FUNC should
13486 @code{nil}: If the split is @code{nil}, it is ignored.
13490 In these splits, @var{field} must match a complete field name.
13491 @var{value} must match a complete word according to the fundamental mode
13492 syntax table. You can use @code{.*} in the regexps to match partial
13493 field names or words. In other words, all @var{value}'s are wrapped in
13494 @samp{\<} and @samp{\>} pairs.
13496 @vindex nnmail-split-abbrev-alist
13497 @var{field} and @var{value} can also be lisp symbols, in that case they
13498 are expanded as specified by the variable
13499 @code{nnmail-split-abbrev-alist}. This is an alist of cons cells, where
13500 the @code{car} of a cell contains the key, and the @code{cdr} contains the associated
13503 @vindex nnmail-split-fancy-syntax-table
13504 @code{nnmail-split-fancy-syntax-table} is the syntax table in effect
13505 when all this splitting is performed.
13507 If you want to have Gnus create groups dynamically based on some
13508 information in the headers (i.e., do @code{replace-match}-like
13509 substitutions in the group names), you can say things like:
13512 (any "debian-\\b\\(\\w+\\)@@lists.debian.org" "mail.debian.\\1")
13515 In this example, messages sent to @samp{debian-foo@@lists.debian.org}
13516 will be filed in @samp{mail.debian.foo}.
13518 If the string contains the element @samp{\&}, then the previously
13519 matched string will be substituted. Similarly, the elements @samp{\\1}
13520 up to @samp{\\9} will be substituted with the text matched by the
13521 groupings 1 through 9.
13523 @findex nnmail-split-fancy-with-parent
13524 @code{nnmail-split-fancy-with-parent} is a function which allows you to
13525 split followups into the same groups their parents are in. Sometimes
13526 you can't make splitting rules for all your mail. For example, your
13527 boss might send you personal mail regarding different projects you are
13528 working on, and as you can't tell your boss to put a distinguishing
13529 string into the subject line, you have to resort to manually moving the
13530 messages into the right group. With this function, you only have to do
13531 it once per thread.
13533 To use this feature, you have to set @code{nnmail-treat-duplicates} and
13534 @code{nnmail-cache-accepted-message-ids} to a non-nil value. And then
13535 you can include @code{nnmail-split-fancy-with-parent} using the colon
13538 (setq nnmail-treat-duplicates 'warn ; or 'delete
13539 nnmail-cache-accepted-message-ids t
13541 '(| (: nnmail-split-fancy-with-parent)
13542 ;; other splits go here
13546 This feature works as follows: when @code{nnmail-treat-duplicates} is
13547 non-nil, Gnus records the message id of every message it sees in the
13548 file specified by the variable @code{nnmail-message-id-cache-file},
13549 together with the group it is in (the group is omitted for non-mail
13550 messages). When mail splitting is invoked, the function
13551 @code{nnmail-split-fancy-with-parent} then looks at the References (and
13552 In-Reply-To) header of each message to split and searches the file
13553 specified by @code{nnmail-message-id-cache-file} for the message ids.
13554 When it has found a parent, it returns the corresponding group name
13555 unless the group name matches the regexp
13556 @code{nnmail-split-fancy-with-parent-ignore-groups}. It is recommended
13557 that you set @code{nnmail-message-id-cache-length} to a somewhat higher
13558 number than the default so that the message ids are still in the cache.
13559 (A value of 5000 appears to create a file some 300 kBytes in size.)
13560 @vindex nnmail-cache-accepted-message-ids
13561 When @code{nnmail-cache-accepted-message-ids} is non-@code{nil}, Gnus
13562 also records the message ids of moved articles, so that the followup
13563 messages goes into the new group.
13565 Also see the variable @code{nnmail-cache-ignore-groups} if you don't
13566 want certain groups to be recorded in the cache. For example, if all
13567 outgoing messages are written to an `outgoing' group, you could set
13568 @code{nnmail-cache-ignore-groups} to match that group name.
13569 Otherwise, answers to all your messages would end up in the
13573 @node Group Mail Splitting
13574 @subsection Group Mail Splitting
13575 @cindex mail splitting
13576 @cindex group mail splitting
13578 @findex gnus-group-split
13579 If you subscribe to dozens of mailing lists but you don't want to
13580 maintain mail splitting rules manually, group mail splitting is for you.
13581 You just have to set @var{to-list} and/or @var{to-address} in group
13582 parameters or group customization and set @code{nnmail-split-methods} to
13583 @code{gnus-group-split}. This splitting function will scan all groups
13584 for those parameters and split mail accordingly, i.e., messages posted
13585 from or to the addresses specified in the parameters @var{to-list} or
13586 @var{to-address} of a mail group will be stored in that group.
13588 Sometimes, mailing lists have multiple addresses, and you may want mail
13589 splitting to recognize them all: just set the @var{extra-aliases} group
13590 parameter to the list of additional addresses and it's done. If you'd
13591 rather use a regular expression, set @var{split-regexp}.
13593 All these parameters in a group will be used to create an
13594 @code{nnmail-split-fancy} split, in which the @var{field} is @samp{any},
13595 the @var{value} is a single regular expression that matches
13596 @var{to-list}, @var{to-address}, all of @var{extra-aliases} and all
13597 matches of @var{split-regexp}, and the @var{split} is the name of the
13598 group. @var{restrict}s are also supported: just set the
13599 @var{split-exclude} parameter to a list of regular expressions.
13601 If you can't get the right split to be generated using all these
13602 parameters, or you just need something fancier, you can set the
13603 parameter @var{split-spec} to an @code{nnmail-split-fancy} split. In
13604 this case, all other aforementioned parameters will be ignored by
13605 @code{gnus-group-split}. In particular, @var{split-spec} may be set to
13606 @code{nil}, in which case the group will be ignored by
13607 @code{gnus-group-split}.
13609 @vindex gnus-group-split-default-catch-all-group
13610 @code{gnus-group-split} will do cross-posting on all groups that match,
13611 by defining a single @code{&} fancy split containing one split for each
13612 group. If a message doesn't match any split, it will be stored in the
13613 group named in @code{gnus-group-split-default-catch-all-group}, unless
13614 some group has @var{split-spec} set to @code{catch-all}, in which case
13615 that group is used as the catch-all group. Even though this variable is
13616 often used just to name a group, it may also be set to an arbitrarily
13617 complex fancy split (after all, a group name is a fancy split), and this
13618 may be useful to split mail that doesn't go to any mailing list to
13619 personal mail folders. Note that this fancy split is added as the last
13620 element of a @code{|} split list that also contains a @code{&} split
13621 with the rules extracted from group parameters.
13623 It's time for an example. Assume the following group parameters have
13628 ((to-address . "bar@@femail.com")
13629 (split-regexp . ".*@@femail\\.com"))
13631 ((to-list . "foo@@nowhere.gov")
13632 (extra-aliases "foo@@localhost" "foo-redist@@home")
13633 (split-exclude "bugs-foo" "rambling-foo")
13634 (admin-address . "foo-request@@nowhere.gov"))
13636 ((split-spec . catch-all))
13639 Setting @code{nnmail-split-methods} to @code{gnus-group-split} will
13640 behave as if @code{nnmail-split-fancy} had been selected and variable
13641 @code{nnmail-split-fancy} had been set as follows:
13644 (| (& (any "\\(bar@@femail\\.com\\|.*@@femail\\.com\\)" "mail.bar")
13645 (any "\\(foo@@nowhere\\.gov\\|foo@@localhost\\|foo-redist@@home\\)"
13646 - "bugs-foo" - "rambling-foo" "mail.foo"))
13650 @findex gnus-group-split-fancy
13651 If you'd rather not use group splitting for all your mail groups, you
13652 may use it for only some of them, by using @code{nnmail-split-fancy}
13656 (: gnus-group-split-fancy GROUPS NO-CROSSPOST CATCH-ALL)
13659 @var{groups} may be a regular expression or a list of group names whose
13660 parameters will be scanned to generate the output split.
13661 @var{no-crosspost} can be used to disable cross-posting; in this case, a
13662 single @code{|} split will be output. @var{catch-all} is the fallback
13663 fancy split, used like @var{gnus-group-split-default-catch-all-group}.
13664 If @var{catch-all} is @code{nil}, or if @var{split-regexp} matches the
13665 empty string in any selected group, no catch-all split will be issued.
13666 Otherwise, if some group has @var{split-spec} set to @code{catch-all},
13667 this group will override the value of the @var{catch-all} argument.
13669 @findex gnus-group-split-setup
13670 Unfortunately, scanning all groups and their parameters can be quite
13671 slow, especially considering that it has to be done for every message.
13672 But don't despair! The function @code{gnus-group-split-setup} can be
13673 used to enable @code{gnus-group-split} in a much more efficient way. It
13674 sets @code{nnmail-split-methods} to @code{nnmail-split-fancy} and sets
13675 @code{nnmail-split-fancy} to the split produced by
13676 @code{gnus-group-split-fancy}. Thus, the group parameters are only
13677 scanned once, no matter how many messages are split.
13679 @findex gnus-group-split-update
13680 However, if you change group parameters, you'd have to update
13681 @code{nnmail-split-fancy} manually. You can do it by running
13682 @code{gnus-group-split-update}. If you'd rather have it updated
13683 automatically, just tell @code{gnus-group-split-setup} to do it for
13684 you. For example, add to your @file{.gnus.el}:
13687 (gnus-group-split-setup AUTO-UPDATE CATCH-ALL)
13690 If @var{auto-update} is non-@code{nil}, @code{gnus-group-split-update}
13691 will be added to @code{nnmail-pre-get-new-mail-hook}, so you won't ever
13692 have to worry about updating @code{nnmail-split-fancy} again. If you
13693 don't omit @var{catch-all} (it's optional, equivalent to @code{nil}),
13694 @code{gnus-group-split-default-catch-all-group} will be set to its
13697 @vindex gnus-group-split-updated-hook
13698 Because you may want to change @code{nnmail-split-fancy} after it is set
13699 by @code{gnus-group-split-update}, this function will run
13700 @code{gnus-group-split-updated-hook} just before finishing.
13702 @node Incorporating Old Mail
13703 @subsection Incorporating Old Mail
13704 @cindex incorporating old mail
13705 @cindex import old mail
13707 Most people have lots of old mail stored in various file formats. If
13708 you have set up Gnus to read mail using one of the spiffy Gnus mail
13709 back ends, you'll probably wish to have that old mail incorporated into
13712 Doing so can be quite easy.
13714 To take an example: You're reading mail using @code{nnml}
13715 (@pxref{Mail Spool}), and have set @code{nnmail-split-methods} to a
13716 satisfactory value (@pxref{Splitting Mail}). You have an old Unix mbox
13717 file filled with important, but old, mail. You want to move it into
13718 your @code{nnml} groups.
13724 Go to the group buffer.
13727 Type `G f' and give the path to the mbox file when prompted to create an
13728 @code{nndoc} group from the mbox file (@pxref{Foreign Groups}).
13731 Type `SPACE' to enter the newly created group.
13734 Type `M P b' to process-mark all articles in this group's buffer
13735 (@pxref{Setting Process Marks}).
13738 Type `B r' to respool all the process-marked articles, and answer
13739 @samp{nnml} when prompted (@pxref{Mail Group Commands}).
13742 All the mail messages in the mbox file will now also be spread out over
13743 all your @code{nnml} groups. Try entering them and check whether things
13744 have gone without a glitch. If things look ok, you may consider
13745 deleting the mbox file, but I wouldn't do that unless I was absolutely
13746 sure that all the mail has ended up where it should be.
13748 Respooling is also a handy thing to do if you're switching from one mail
13749 back end to another. Just respool all the mail in the old mail groups
13750 using the new mail back end.
13753 @node Expiring Mail
13754 @subsection Expiring Mail
13755 @cindex article expiry
13757 Traditional mail readers have a tendency to remove mail articles when
13758 you mark them as read, in some way. Gnus takes a fundamentally
13759 different approach to mail reading.
13761 Gnus basically considers mail just to be news that has been received in
13762 a rather peculiar manner. It does not think that it has the power to
13763 actually change the mail, or delete any mail messages. If you enter a
13764 mail group, and mark articles as ``read'', or kill them in some other
13765 fashion, the mail articles will still exist on the system. I repeat:
13766 Gnus will not delete your old, read mail. Unless you ask it to, of
13769 To make Gnus get rid of your unwanted mail, you have to mark the
13770 articles as @dfn{expirable}. (With the default keybindings, this means
13771 that you have to type @kbd{E}.) This does not mean that the articles
13772 will disappear right away, however. In general, a mail article will be
13773 deleted from your system if, 1) it is marked as expirable, AND 2) it is
13774 more than one week old. If you do not mark an article as expirable, it
13775 will remain on your system until hell freezes over. This bears
13776 repeating one more time, with some spurious capitalizations: IF you do
13777 NOT mark articles as EXPIRABLE, Gnus will NEVER delete those ARTICLES.
13779 You do not have to mark articles as expirable by hand. Gnus provides
13780 two features, called `auto-expire' and `total-expire', that can help you
13781 with this. In a nutshell, `auto-expire' means that Gnus hits @kbd{E}
13782 for you when you select an article. And `total-expire' means that Gnus
13783 considers all articles as expirable that are read. So, in addition to
13784 the articles marked @samp{E}, also the articles marked @samp{r},
13785 @samp{R}, @samp{O}, @samp{K}, @samp{Y} and so on are considered
13788 When should either auto-expire or total-expire be used? Most people
13789 who are subscribed to mailing lists split each list into its own group
13790 and then turn on auto-expire or total-expire for those groups.
13791 (@xref{Splitting Mail}, for more information on splitting each list
13792 into its own group.)
13794 Which one is better, auto-expire or total-expire? It's not easy to
13795 answer. Generally speaking, auto-expire is probably faster. Another
13796 advantage of auto-expire is that you get more marks to work with: for
13797 the articles that are supposed to stick around, you can still choose
13798 between tick and dormant and read marks. But with total-expire, you
13799 only have dormant and ticked to choose from. The advantage of
13800 total-expire is that it works well with adaptive scoring @pxref{Adaptive
13801 Scoring}. Auto-expire works with normal scoring but not with adaptive
13804 @vindex gnus-auto-expirable-newsgroups
13805 Groups that match the regular expression
13806 @code{gnus-auto-expirable-newsgroups} will have all articles that you
13807 read marked as expirable automatically. All articles marked as
13808 expirable have an @samp{E} in the first column in the summary buffer.
13810 By default, if you have auto expiry switched on, Gnus will mark all the
13811 articles you read as expirable, no matter if they were read or unread
13812 before. To avoid having articles marked as read marked as expirable
13813 automatically, you can put something like the following in your
13814 @file{.gnus.el} file:
13816 @vindex gnus-mark-article-hook
13818 (remove-hook 'gnus-mark-article-hook
13819 'gnus-summary-mark-read-and-unread-as-read)
13820 (add-hook 'gnus-mark-article-hook 'gnus-summary-mark-unread-as-read)
13823 Note that making a group auto-expirable doesn't mean that all read
13824 articles are expired---only the articles marked as expirable
13825 will be expired. Also note that using the @kbd{d} command won't make
13826 articles expirable---only semi-automatic marking of articles as read will
13827 mark the articles as expirable in auto-expirable groups.
13829 Let's say you subscribe to a couple of mailing lists, and you want the
13830 articles you have read to disappear after a while:
13833 (setq gnus-auto-expirable-newsgroups
13834 "mail.nonsense-list\\|mail.nice-list")
13837 Another way to have auto-expiry happen is to have the element
13838 @code{auto-expire} in the group parameters of the group.
13840 If you use adaptive scoring (@pxref{Adaptive Scoring}) and
13841 auto-expiring, you'll have problems. Auto-expiring and adaptive scoring
13842 don't really mix very well.
13844 @vindex nnmail-expiry-wait
13845 The @code{nnmail-expiry-wait} variable supplies the default time an
13846 expirable article has to live. Gnus starts counting days from when the
13847 message @emph{arrived}, not from when it was sent. The default is seven
13850 Gnus also supplies a function that lets you fine-tune how long articles
13851 are to live, based on what group they are in. Let's say you want to
13852 have one month expiry period in the @samp{mail.private} group, a one day
13853 expiry period in the @samp{mail.junk} group, and a six day expiry period
13856 @vindex nnmail-expiry-wait-function
13858 (setq nnmail-expiry-wait-function
13860 (cond ((string= group "mail.private")
13862 ((string= group "mail.junk")
13864 ((string= group "important")
13870 The group names this function is fed are ``unadorned'' group
13871 names---no @samp{nnml:} prefixes and the like.
13873 The @code{nnmail-expiry-wait} variable and
13874 @code{nnmail-expiry-wait-function} function can either be a number (not
13875 necessarily an integer) or one of the symbols @code{immediate} or
13878 You can also use the @code{expiry-wait} group parameter to selectively
13879 change the expiry period (@pxref{Group Parameters}).
13881 @vindex nnmail-expiry-target
13882 The normal action taken when expiring articles is to delete them.
13883 However, in some circumstances it might make more sense to move them
13884 to other groups instead of deleting them. The variable
13885 @code{nnmail-expiry-target} (and the @code{expiry-target} group
13886 parameter) controls this. The variable supplies a default value for
13887 all groups, which can be overridden for specific groups by the group
13888 parameter. default value is @code{delete}, but this can also be a
13889 string (which should be the name of the group the message should be
13890 moved to), or a function (which will be called in a buffer narrowed to
13891 the message in question, and with the name of the group being moved
13892 from as its parameter) which should return a target -- either a group
13893 name or @code{delete}.
13895 Here's an example for specifying a group name:
13897 (setq nnmail-expiry-target "nnml:expired")
13900 @findex nnmail-fancy-expiry-target
13901 @vindex nnmail-fancy-expiry-targets
13902 Gnus provides a function @code{nnmail-fancy-expiry-target} which will
13903 expire mail to groups according to the variable
13904 @code{nnmail-fancy-expiry-targets}. Here's an example:
13907 (setq nnmail-expiry-target 'nnmail-fancy-expiry-target
13908 nnmail-fancy-expiry-targets
13909 '((to-from "boss" "nnfolder:Work")
13910 ("subject" "IMPORTANT" "nnfolder:IMPORTANT.%Y.%b")
13911 ("from" ".*" "nnfolder:Archive-%Y")))
13914 With this setup, any mail that has @code{IMPORTANT} in its Subject
13915 header and was sent in the year @code{YYYY} and month @code{MMM}, will
13916 get expired to the group @code{nnfolder:IMPORTANT.YYYY.MMM}. If its
13917 From or To header contains the string @code{boss}, it will get expired
13918 to @code{nnfolder:Work}. All other mail will get expired to
13919 @code{nnfolder:Archive-YYYY}.
13921 @vindex nnmail-keep-last-article
13922 If @code{nnmail-keep-last-article} is non-@code{nil}, Gnus will never
13923 expire the final article in a mail newsgroup. This is to make life
13924 easier for procmail users.
13926 @vindex gnus-total-expirable-newsgroups
13927 By the way: That line up there, about Gnus never expiring non-expirable
13928 articles, is a lie. If you put @code{total-expire} in the group
13929 parameters, articles will not be marked as expirable, but all read
13930 articles will be put through the expiry process. Use with extreme
13931 caution. Even more dangerous is the
13932 @code{gnus-total-expirable-newsgroups} variable. All groups that match
13933 this regexp will have all read articles put through the expiry process,
13934 which means that @emph{all} old mail articles in the groups in question
13935 will be deleted after a while. Use with extreme caution, and don't come
13936 crying to me when you discover that the regexp you used matched the
13937 wrong group and all your important mail has disappeared. Be a
13938 @emph{man}! Or a @emph{woman}! Whatever you feel more comfortable
13941 Most people make most of their mail groups total-expirable, though.
13943 @vindex gnus-inhibit-user-auto-expire
13944 If @code{gnus-inhibit-user-auto-expire} is non-@code{nil}, user marking
13945 commands will not mark an article as expirable, even if the group has
13946 auto-expire turned on.
13950 @subsection Washing Mail
13951 @cindex mail washing
13952 @cindex list server brain damage
13953 @cindex incoming mail treatment
13955 Mailers and list servers are notorious for doing all sorts of really,
13956 really stupid things with mail. ``Hey, RFC 822 doesn't explicitly
13957 prohibit us from adding the string @code{wE aRe ElItE!!!!!1!!} to the
13958 end of all lines passing through our server, so let's do that!!!!1!''
13959 Yes, but RFC 822 wasn't designed to be read by morons. Things that were
13960 considered to be self-evident were not discussed. So. Here we are.
13962 Case in point: The German version of Microsoft Exchange adds @samp{AW:
13963 } to the subjects of replies instead of @samp{Re: }. I could pretend to
13964 be shocked and dismayed by this, but I haven't got the energy. It is to
13967 Gnus provides a plethora of functions for washing articles while
13968 displaying them, but it might be nicer to do the filtering before
13969 storing the mail to disk. For that purpose, we have three hooks and
13970 various functions that can be put in these hooks.
13973 @item nnmail-prepare-incoming-hook
13974 @vindex nnmail-prepare-incoming-hook
13975 This hook is called before doing anything with the mail and is meant for
13976 grand, sweeping gestures. It is called in a buffer that contains all
13977 the new, incoming mail. Functions to be used include:
13980 @item nnheader-ms-strip-cr
13981 @findex nnheader-ms-strip-cr
13982 Remove trailing carriage returns from each line. This is default on
13983 Emacs running on MS machines.
13987 @item nnmail-prepare-incoming-header-hook
13988 @vindex nnmail-prepare-incoming-header-hook
13989 This hook is called narrowed to each header. It can be used when
13990 cleaning up the headers. Functions that can be used include:
13993 @item nnmail-remove-leading-whitespace
13994 @findex nnmail-remove-leading-whitespace
13995 Clear leading white space that ``helpful'' listservs have added to the
13996 headers to make them look nice. Aaah.
13998 (Note that this function works on both the header on the body of all
13999 messages, so it is a potentially dangerous function to use (if a body
14000 of a message contains something that looks like a header line). So
14001 rather than fix the bug, it is of course the right solution to make it
14002 into a feature by documenting it.)
14004 @item nnmail-remove-list-identifiers
14005 @findex nnmail-remove-list-identifiers
14006 Some list servers add an identifier---for example, @samp{(idm)}---to the
14007 beginning of all @code{Subject} headers. I'm sure that's nice for
14008 people who use stone age mail readers. This function will remove
14009 strings that match the @code{nnmail-list-identifiers} regexp, which can
14010 also be a list of regexp. @code{nnmail-list-identifiers} may not contain
14013 For instance, if you want to remove the @samp{(idm)} and the
14014 @samp{nagnagnag} identifiers:
14017 (setq nnmail-list-identifiers
14018 '("(idm)" "nagnagnag"))
14021 This can also be done non-destructively with
14022 @code{gnus-list-identifiers}, @xref{Article Hiding}.
14024 @item nnmail-remove-tabs
14025 @findex nnmail-remove-tabs
14026 Translate all @samp{TAB} characters into @samp{SPACE} characters.
14028 @item nnmail-fix-eudora-headers
14029 @findex nnmail-fix-eudora-headers
14031 Eudora produces broken @code{References} headers, but OK
14032 @code{In-Reply-To} headers. This function will get rid of the
14033 @code{References} headers.
14037 @item nnmail-prepare-incoming-message-hook
14038 @vindex nnmail-prepare-incoming-message-hook
14039 This hook is called narrowed to each message. Functions to be used
14043 @item article-de-quoted-unreadable
14044 @findex article-de-quoted-unreadable
14045 Decode Quoted Readable encoding.
14052 @subsection Duplicates
14054 @vindex nnmail-treat-duplicates
14055 @vindex nnmail-message-id-cache-length
14056 @vindex nnmail-message-id-cache-file
14057 @cindex duplicate mails
14058 If you are a member of a couple of mailing lists, you will sometimes
14059 receive two copies of the same mail. This can be quite annoying, so
14060 @code{nnmail} checks for and treats any duplicates it might find. To do
14061 this, it keeps a cache of old @code{Message-ID}s---
14062 @code{nnmail-message-id-cache-file}, which is @file{~/.nnmail-cache} by
14063 default. The approximate maximum number of @code{Message-ID}s stored
14064 there is controlled by the @code{nnmail-message-id-cache-length}
14065 variable, which is 1000 by default. (So 1000 @code{Message-ID}s will be
14066 stored.) If all this sounds scary to you, you can set
14067 @code{nnmail-treat-duplicates} to @code{warn} (which is what it is by
14068 default), and @code{nnmail} won't delete duplicate mails. Instead it
14069 will insert a warning into the head of the mail saying that it thinks
14070 that this is a duplicate of a different message.
14072 This variable can also be a function. If that's the case, the function
14073 will be called from a buffer narrowed to the message in question with
14074 the @code{Message-ID} as a parameter. The function must return either
14075 @code{nil}, @code{warn}, or @code{delete}.
14077 You can turn this feature off completely by setting the variable to
14080 If you want all the duplicate mails to be put into a special
14081 @dfn{duplicates} group, you could do that using the normal mail split
14085 (setq nnmail-split-fancy
14086 '(| ;; Messages duplicates go to a separate group.
14087 ("gnus-warning" "duplicat\\(e\\|ion\\) of message" "duplicate")
14088 ;; Message from daemons, postmaster, and the like to another.
14089 (any mail "mail.misc")
14096 (setq nnmail-split-methods
14097 '(("duplicates" "^Gnus-Warning:.*duplicate")
14102 Here's a neat feature: If you know that the recipient reads her mail
14103 with Gnus, and that she has @code{nnmail-treat-duplicates} set to
14104 @code{delete}, you can send her as many insults as you like, just by
14105 using a @code{Message-ID} of a mail that you know that she's already
14106 received. Think of all the fun! She'll never see any of it! Whee!
14109 @node Not Reading Mail
14110 @subsection Not Reading Mail
14112 If you start using any of the mail back ends, they have the annoying
14113 habit of assuming that you want to read mail with them. This might not
14114 be unreasonable, but it might not be what you want.
14116 If you set @code{mail-sources} and @code{nnmail-spool-file} to
14117 @code{nil}, none of the back ends will ever attempt to read incoming
14118 mail, which should help.
14120 @vindex nnbabyl-get-new-mail
14121 @vindex nnmbox-get-new-mail
14122 @vindex nnml-get-new-mail
14123 @vindex nnmh-get-new-mail
14124 @vindex nnfolder-get-new-mail
14125 This might be too much, if, for instance, you are reading mail quite
14126 happily with @code{nnml} and just want to peek at some old @sc{rmail}
14127 file you have stashed away with @code{nnbabyl}. All back ends have
14128 variables called back-end-@code{get-new-mail}. If you want to disable
14129 the @code{nnbabyl} mail reading, you edit the virtual server for the
14130 group to have a setting where @code{nnbabyl-get-new-mail} to @code{nil}.
14132 All the mail back ends will call @code{nn}*@code{-prepare-save-mail-hook}
14133 narrowed to the article to be saved before saving it when reading
14137 @node Choosing a Mail Back End
14138 @subsection Choosing a Mail Back End
14140 Gnus will read the mail spool when you activate a mail group. The mail
14141 file is first copied to your home directory. What happens after that
14142 depends on what format you want to store your mail in.
14144 There are six different mail back ends in the standard Gnus, and more
14145 back ends are available separately. The mail back end most people use
14146 (because it is possibly the fastest) is @code{nnml} (@pxref{Mail
14147 Spool}). You might notice that only five back ends are listed below;
14148 @code{nnmaildir}'s documentation has not yet been completely
14149 incorporated into this manual. Until it is, you can find it at
14150 @uref{http://multivac.cwru.edu./nnmaildir/}.
14153 * Unix Mail Box:: Using the (quite) standard Un*x mbox.
14154 * Rmail Babyl:: Emacs programs use the rmail babyl format.
14155 * Mail Spool:: Store your mail in a private spool?
14156 * MH Spool:: An mhspool-like back end.
14157 * Mail Folders:: Having one file for each group.
14158 * Comparing Mail Back Ends:: An in-depth looks at pros and cons.
14162 @node Unix Mail Box
14163 @subsubsection Unix Mail Box
14165 @cindex unix mail box
14167 @vindex nnmbox-active-file
14168 @vindex nnmbox-mbox-file
14169 The @dfn{nnmbox} back end will use the standard Un*x mbox file to store
14170 mail. @code{nnmbox} will add extra headers to each mail article to say
14171 which group it belongs in.
14173 Virtual server settings:
14176 @item nnmbox-mbox-file
14177 @vindex nnmbox-mbox-file
14178 The name of the mail box in the user's home directory. Default is
14181 @item nnmbox-active-file
14182 @vindex nnmbox-active-file
14183 The name of the active file for the mail box. Default is
14184 @file{~/.mbox-active}.
14186 @item nnmbox-get-new-mail
14187 @vindex nnmbox-get-new-mail
14188 If non-@code{nil}, @code{nnmbox} will read incoming mail and split it
14189 into groups. Default is @code{t}.
14194 @subsubsection Rmail Babyl
14198 @vindex nnbabyl-active-file
14199 @vindex nnbabyl-mbox-file
14200 The @dfn{nnbabyl} back end will use a babyl mail box (aka. @dfn{rmail
14201 mbox}) to store mail. @code{nnbabyl} will add extra headers to each
14202 mail article to say which group it belongs in.
14204 Virtual server settings:
14207 @item nnbabyl-mbox-file
14208 @vindex nnbabyl-mbox-file
14209 The name of the rmail mbox file. The default is @file{~/RMAIL}
14211 @item nnbabyl-active-file
14212 @vindex nnbabyl-active-file
14213 The name of the active file for the rmail box. The default is
14214 @file{~/.rmail-active}
14216 @item nnbabyl-get-new-mail
14217 @vindex nnbabyl-get-new-mail
14218 If non-@code{nil}, @code{nnbabyl} will read incoming mail. Default is
14224 @subsubsection Mail Spool
14226 @cindex mail @sc{nov} spool
14228 The @dfn{nnml} spool mail format isn't compatible with any other known
14229 format. It should be used with some caution.
14231 @vindex nnml-directory
14232 If you use this back end, Gnus will split all incoming mail into files,
14233 one file for each mail, and put the articles into the corresponding
14234 directories under the directory specified by the @code{nnml-directory}
14235 variable. The default value is @file{~/Mail/}.
14237 You do not have to create any directories beforehand; Gnus will take
14240 If you have a strict limit as to how many files you are allowed to store
14241 in your account, you should not use this back end. As each mail gets its
14242 own file, you might very well occupy thousands of inodes within a few
14243 weeks. If this is no problem for you, and it isn't a problem for you
14244 having your friendly systems administrator walking around, madly,
14245 shouting ``Who is eating all my inodes?! Who? Who!?!'', then you should
14246 know that this is probably the fastest format to use. You do not have
14247 to trudge through a big mbox file just to read your new mail.
14249 @code{nnml} is probably the slowest back end when it comes to article
14250 splitting. It has to create lots of files, and it also generates
14251 @sc{nov} databases for the incoming mails. This makes it possibly the
14252 fastest back end when it comes to reading mail.
14254 @cindex self contained nnml servers
14256 When the marks file is used (which it is by default), @code{nnml}
14257 servers have the property that you may backup them using @code{tar} or
14258 similar, and later be able to restore them into Gnus (by adding the
14259 proper @code{nnml} server) and have all your marks be preserved. Marks
14260 for a group is usually stored in the @code{.marks} file (but see
14261 @code{nnml-marks-file-name}) within each @code{nnml} group's directory.
14262 Individual @code{nnml} groups are also possible to backup, use @kbd{G m}
14263 to restore the group (after restoring the backup into the nnml
14266 If for some reason you believe your @file{.marks} files are screwed
14267 up, you can just delete them all. Gnus will then correctly regenerate
14268 them next time it starts.
14270 Virtual server settings:
14273 @item nnml-directory
14274 @vindex nnml-directory
14275 All @code{nnml} directories will be placed under this directory.
14276 The default is the value of `message-directory' (whose default value is
14279 @item nnml-active-file
14280 @vindex nnml-active-file
14281 The active file for the @code{nnml} server. The default is
14282 @file{~/Mail/active"}.
14284 @item nnml-newsgroups-file
14285 @vindex nnml-newsgroups-file
14286 The @code{nnml} group descriptions file. @xref{Newsgroups File
14287 Format}. The default is @file{~/Mail/newsgroups"}.
14289 @item nnml-get-new-mail
14290 @vindex nnml-get-new-mail
14291 If non-@code{nil}, @code{nnml} will read incoming mail. The default is
14294 @item nnml-nov-is-evil
14295 @vindex nnml-nov-is-evil
14296 If non-@code{nil}, this back end will ignore any @sc{nov} files. The
14297 default is @code{nil}.
14299 @item nnml-nov-file-name
14300 @vindex nnml-nov-file-name
14301 The name of the @sc{nov} files. The default is @file{.overview}.
14303 @item nnml-prepare-save-mail-hook
14304 @vindex nnml-prepare-save-mail-hook
14305 Hook run narrowed to an article before saving.
14307 @item nnml-marks-is-evil
14308 @vindex nnml-marks-is-evil
14309 If non-@code{nil}, this back end will ignore any @sc{marks} files. The
14310 default is @code{nil}.
14312 @item nnml-marks-file-name
14313 @vindex nnml-marks-file-name
14314 The name of the @dfn{marks} files. The default is @file{.marks}.
14316 @item nnml-use-compressed-files
14317 @vindex nnml-use-compressed-files
14318 If non-@code{nil}, @code{nnml} will allow using compressed message
14323 @findex nnml-generate-nov-databases
14324 If your @code{nnml} groups and @sc{nov} files get totally out of whack,
14325 you can do a complete update by typing @kbd{M-x
14326 nnml-generate-nov-databases}. This command will trawl through the
14327 entire @code{nnml} hierarchy, looking at each and every article, so it
14328 might take a while to complete. A better interface to this
14329 functionality can be found in the server buffer (@pxref{Server
14334 @subsubsection MH Spool
14336 @cindex mh-e mail spool
14338 @code{nnmh} is just like @code{nnml}, except that is doesn't generate
14339 @sc{nov} databases and it doesn't keep an active file or marks file.
14340 This makes @code{nnmh} a @emph{much} slower back end than @code{nnml},
14341 but it also makes it easier to write procmail scripts for.
14343 Virtual server settings:
14346 @item nnmh-directory
14347 @vindex nnmh-directory
14348 All @code{nnmh} directories will be located under this directory. The
14349 default is the value of @code{message-directory} (whose default is
14352 @item nnmh-get-new-mail
14353 @vindex nnmh-get-new-mail
14354 If non-@code{nil}, @code{nnmh} will read incoming mail. The default is
14358 @vindex nnmh-be-safe
14359 If non-@code{nil}, @code{nnmh} will go to ridiculous lengths to make
14360 sure that the articles in the folder are actually what Gnus thinks they
14361 are. It will check date stamps and stat everything in sight, so
14362 setting this to @code{t} will mean a serious slow-down. If you never
14363 use anything but Gnus to read the @code{nnmh} articles, you do not have
14364 to set this variable to @code{t}. The default is @code{nil}.
14369 @subsubsection Mail Folders
14371 @cindex mbox folders
14372 @cindex mail folders
14374 @code{nnfolder} is a back end for storing each mail group in a separate
14375 file. Each file is in the standard Un*x mbox format. @code{nnfolder}
14376 will add extra headers to keep track of article numbers and arrival
14379 @cindex self contained nnfolder servers
14381 When the marks file is used (which it is by default), @code{nnfolder}
14382 servers have the property that you may backup them using @code{tar} or
14383 similar, and later be able to restore them into Gnus (by adding the
14384 proper @code{nnfolder} server) and have all your marks be preserved.
14385 Marks for a group is usually stored in a file named as the mbox file
14386 with @code{.mrk} concatenated to it (but see
14387 @code{nnfolder-marks-file-suffix}) within the @code{nnfolder} directory.
14388 Individual @code{nnfolder} groups are also possible to backup, use
14389 @kbd{G m} to restore the group (after restoring the backup into the
14390 @code{nnfolder} directory).
14392 Virtual server settings:
14395 @item nnfolder-directory
14396 @vindex nnfolder-directory
14397 All the @code{nnfolder} mail boxes will be stored under this directory.
14398 The default is the value of @code{message-directory} (whose default is
14401 @item nnfolder-active-file
14402 @vindex nnfolder-active-file
14403 The name of the active file. The default is @file{~/Mail/active}.
14405 @item nnfolder-newsgroups-file
14406 @vindex nnfolder-newsgroups-file
14407 The name of the group descriptions file. @xref{Newsgroups File
14408 Format}. The default is @file{~/Mail/newsgroups"}
14410 @item nnfolder-get-new-mail
14411 @vindex nnfolder-get-new-mail
14412 If non-@code{nil}, @code{nnfolder} will read incoming mail. The default
14415 @item nnfolder-save-buffer-hook
14416 @vindex nnfolder-save-buffer-hook
14417 @cindex backup files
14418 Hook run before saving the folders. Note that Emacs does the normal
14419 backup renaming of files even with the @code{nnfolder} buffers. If you
14420 wish to switch this off, you could say something like the following in
14421 your @file{.emacs} file:
14424 (defun turn-off-backup ()
14425 (set (make-local-variable 'backup-inhibited) t))
14427 (add-hook 'nnfolder-save-buffer-hook 'turn-off-backup)
14430 @item nnfolder-delete-mail-hook
14431 @vindex nnfolder-delete-mail-hook
14432 Hook run in a buffer narrowed to the message that is to be deleted.
14433 This function can be used to copy the message to somewhere else, or to
14434 extract some information from it before removing it.
14436 @item nnfolder-nov-is-evil
14437 @vindex nnfolder-nov-is-evil
14438 If non-@code{nil}, this back end will ignore any @sc{nov} files. The
14439 default is @code{nil}.
14441 @item nnfolder-nov-file-suffix
14442 @vindex nnfolder-nov-file-suffix
14443 The extension for @sc{nov} files. The default is @file{.nov}.
14445 @item nnfolder-nov-directory
14446 @vindex nnfolder-nov-directory
14447 The directory where the @sc{nov} files should be stored. If nil,
14448 @code{nnfolder-directory} is used.
14450 @item nnfolder-marks-is-evil
14451 @vindex nnfolder-marks-is-evil
14452 If non-@code{nil}, this back end will ignore any @sc{marks} files. The
14453 default is @code{nil}.
14455 @item nnfolder-marks-file-suffix
14456 @vindex nnfolder-marks-file-suffix
14457 The extension for @sc{marks} files. The default is @file{.mrk}.
14459 @item nnfolder-marks-directory
14460 @vindex nnfolder-marks-directory
14461 The directory where the @sc{marks} files should be stored. If nil,
14462 @code{nnfolder-directory} is used.
14467 @findex nnfolder-generate-active-file
14468 @kindex M-x nnfolder-generate-active-file
14469 If you have lots of @code{nnfolder}-like files you'd like to read with
14470 @code{nnfolder}, you can use the @kbd{M-x nnfolder-generate-active-file}
14471 command to make @code{nnfolder} aware of all likely files in
14472 @code{nnfolder-directory}. This only works if you use long file names,
14475 @node Comparing Mail Back Ends
14476 @subsubsection Comparing Mail Back Ends
14478 First, just for terminology, the @dfn{back end} is the common word for a
14479 low-level access method---a transport, if you will, by which something
14480 is acquired. The sense is that one's mail has to come from somewhere,
14481 and so selection of a suitable back end is required in order to get that
14482 mail within spitting distance of Gnus.
14484 The same concept exists for Usenet itself: Though access to articles is
14485 typically done by @sc{nntp} these days, once upon a midnight dreary, everyone
14486 in the world got at Usenet by running a reader on the machine where the
14487 articles lay (the machine which today we call an @sc{nntp} server), and
14488 access was by the reader stepping into the articles' directory spool
14489 area directly. One can still select between either the @code{nntp} or
14490 @code{nnspool} back ends, to select between these methods, if one happens
14491 actually to live on the server (or can see its spool directly, anyway,
14494 The goal in selecting a mail back end is to pick one which
14495 simultaneously represents a suitable way of dealing with the original
14496 format plus leaving mail in a form that is convenient to use in the
14497 future. Here are some high and low points on each:
14502 UNIX systems have historically had a single, very common, and well-
14503 defined format. All messages arrive in a single @dfn{spool file}, and
14504 they are delineated by a line whose regular expression matches
14505 @samp{^From_}. (My notational use of @samp{_} is to indicate a space,
14506 to make it clear in this instance that this is not the RFC-specified
14507 @samp{From:} header.) Because Emacs and therefore Gnus emanate
14508 historically from the Unix environment, it is simplest if one does not
14509 mess a great deal with the original mailbox format, so if one chooses
14510 this back end, Gnus' primary activity in getting mail from the real spool
14511 area to Gnus' preferred directory is simply to copy it, with no
14512 (appreciable) format change in the process. It is the ``dumbest'' way
14513 to move mail into availability in the Gnus environment. This makes it
14514 fast to move into place, but slow to parse, when Gnus has to look at
14519 Once upon a time, there was the DEC-10 and DEC-20, running operating
14520 systems called TOPS and related things, and the usual (only?) mail
14521 reading environment was a thing called Babyl. I don't know what format
14522 was used for mail landing on the system, but Babyl had its own internal
14523 format to which mail was converted, primarily involving creating a
14524 spool-file-like entity with a scheme for inserting Babyl-specific
14525 headers and status bits above the top of each message in the file.
14526 RMAIL was Emacs' first mail reader, it was written by Richard Stallman,
14527 and Stallman came out of that TOPS/Babyl environment, so he wrote RMAIL
14528 to understand the mail files folks already had in existence. Gnus (and
14529 VM, for that matter) continue to support this format because it's
14530 perceived as having some good qualities in those mailer-specific
14531 headers/status bits stuff. RMAIL itself still exists as well, of
14532 course, and is still maintained by Stallman.
14534 Both of the above forms leave your mail in a single file on your
14535 file system, and they must parse that entire file each time you take a
14540 @code{nnml} is the back end which smells the most as though you were
14541 actually operating with an @code{nnspool}-accessed Usenet system. (In
14542 fact, I believe @code{nnml} actually derived from @code{nnspool} code,
14543 lo these years ago.) One's mail is taken from the original spool file,
14544 and is then cut up into individual message files, 1:1. It maintains a
14545 Usenet-style active file (analogous to what one finds in an INN- or
14546 CNews-based news system in (for instance) @file{/var/lib/news/active},
14547 or what is returned via the @samp{NNTP LIST} verb) and also creates
14548 @dfn{overview} files for efficient group entry, as has been defined for
14549 @sc{nntp} servers for some years now. It is slower in mail-splitting,
14550 due to the creation of lots of files, updates to the @code{nnml} active
14551 file, and additions to overview files on a per-message basis, but it is
14552 extremely fast on access because of what amounts to the indexing support
14553 provided by the active file and overviews.
14555 @code{nnml} costs @dfn{inodes} in a big way; that is, it soaks up the
14556 resource which defines available places in the file system to put new
14557 files. Sysadmins take a dim view of heavy inode occupation within
14558 tight, shared file systems. But if you live on a personal machine where
14559 the file system is your own and space is not at a premium, @code{nnml}
14562 It is also problematic using this back end if you are living in a
14563 FAT16-based Windows world, since much space will be wasted on all these
14568 The Rand MH mail-reading system has been around UNIX systems for a very
14569 long time; it operates by splitting one's spool file of messages into
14570 individual files, but with little or no indexing support -- @code{nnmh}
14571 is considered to be semantically equivalent to ``@code{nnml} without
14572 active file or overviews''. This is arguably the worst choice, because
14573 one gets the slowness of individual file creation married to the
14574 slowness of access parsing when learning what's new in one's groups.
14578 Basically the effect of @code{nnfolder} is @code{nnmbox} (the first
14579 method described above) on a per-group basis. That is, @code{nnmbox}
14580 itself puts *all* one's mail in one file; @code{nnfolder} provides a
14581 little bit of optimization to this so that each of one's mail groups has
14582 a Unix mail box file. It's faster than @code{nnmbox} because each group
14583 can be parsed separately, and still provides the simple Unix mail box
14584 format requiring minimal effort in moving the mail around. In addition,
14585 it maintains an ``active'' file making it much faster for Gnus to figure
14586 out how many messages there are in each separate group.
14588 If you have groups that are expected to have a massive amount of
14589 messages, @code{nnfolder} is not the best choice, but if you receive
14590 only a moderate amount of mail, @code{nnfolder} is probably the most
14591 friendly mail back end all over.
14595 @code{nnmaildir} is largely similar to @code{nnml}, with some notable
14596 differences. Each message is stored in a separate file, but the
14597 filename is unrelated to the article number in Gnus. @code{nnmaildir}
14598 also stores the equivalent of @code{nnml}'s overview files in one file
14599 per article, so it uses about twice as many inodes as @code{nnml}. (Use
14600 @code{df -i} to see how plentiful your inode supply is.) If this slows
14601 you down or takes up very much space, consider switching to ReiserFS
14602 (@uref{http://www.namesys.com/}) or another non-block-structured
14605 Since maildirs don't require locking for delivery, the maildirs you use
14606 as groups can also be the maildirs your mail is directly delivered to.
14607 This means you can skip Gnus's mail splitting if your mail is already
14608 organized into different mailboxes during delivery. A @code{directory}
14609 entry in @code{mail-sources} would have a similar effect, but would
14610 require one set of mailboxes for spooling deliveries (in mbox format,
14611 thus damaging message bodies), and another set to be used as groups (in
14612 whatever format you like). A maildir has a built-in spool, in the
14613 @code{new/} subdirectory. Beware that currently, mail moved from
14614 @code{new/} to @code{cur/} instead of via mail splitting will undergo
14615 treatment such as duplicate checking.
14617 An article will not necessarily keep the same number across Gnus
14618 sessions; articles are renumbered starting from 1 for each Gnus session
14619 (more precisely, each time you open the @code{nnmaildir} server). This
14620 way, you don't get gaps in your article number ranges, and when entering
14621 large groups, Gnus is likely to give a more accurate article count. The
14622 price is that @code{nnmaildir} doesn't work with the cache or agent.
14623 This will probably be changed in the future.
14625 @code{nnmaildir} stores article marks for a given group in the
14626 corresponding maildir, in a way designed so that it's easy to manipulate
14627 them from outside Gnus. You can tar up a maildir, unpack it somewhere
14628 else, and still have your marks. @code{nnml} also stores marks, but
14629 it's not as easy to work with them from outside Gnus as with
14632 For configuring expiry and other things, @code{nnmaildir} uses group
14633 parameters slightly different from those of other mail back ends.
14635 @code{nnmaildir} uses a significant amount of memory to speed things up.
14636 (It keeps in memory some of the things that @code{nnml} stores in files
14637 and that @code{nnmh} repeatedly parses out of message files.) If this
14638 is a problem for you, you can set the @code{nov-cache-size} group
14639 parameter to something small (0 would probably not work, but 1 probably
14640 would) to make it use less memory.
14642 Startup and shutdown are likely to be slower with @code{nnmaildir} than
14643 with other back ends. Everything in between is likely to be faster,
14644 depending in part on your file system.
14646 @code{nnmaildir} does not use @code{nnoo}, so you cannot use @code{nnoo}
14647 to write an @code{nnmaildir}-derived back end.
14652 @node Browsing the Web
14653 @section Browsing the Web
14655 @cindex browsing the web
14659 Web-based discussion forums are getting more and more popular. On many
14660 subjects, the web-based forums have become the most important forums,
14661 eclipsing the importance of mailing lists and news groups. The reason
14662 is easy to understand---they are friendly to new users; you just point
14663 and click, and there's the discussion. With mailing lists, you have to
14664 go through a cumbersome subscription procedure, and most people don't
14665 even know what a news group is.
14667 The problem with this scenario is that web browsers are not very good at
14668 being newsreaders. They do not keep track of what articles you've read;
14669 they do not allow you to score on subjects you're interested in; they do
14670 not allow off-line browsing; they require you to click around and drive
14671 you mad in the end.
14673 So---if web browsers suck at reading discussion forums, why not use Gnus
14676 Gnus has been getting a bit of a collection of back ends for providing
14677 interfaces to these sources.
14681 * Web Searches:: Creating groups from articles that match a string.
14682 * Slashdot:: Reading the Slashdot comments.
14683 * Ultimate:: The Ultimate Bulletin Board systems.
14684 * Web Archive:: Reading mailing list archived on web.
14685 * RSS:: Reading RDF site summary.
14686 * Customizing w3:: Doing stuff to Emacs/w3 from Gnus.
14689 All the web sources require Emacs/w3 and the url library to work.
14691 The main caveat with all these web sources is that they probably won't
14692 work for a very long time. Gleaning information from the @sc{html} data
14693 is guesswork at best, and when the layout is altered, the Gnus back end
14694 will fail. If you have reasonably new versions of these back ends,
14695 though, you should be ok.
14697 One thing all these Web methods have in common is that the Web sources
14698 are often down, unavailable or just plain too slow to be fun. In those
14699 cases, it makes a lot of sense to let the Gnus Agent (@pxref{Gnus
14700 Unplugged}) handle downloading articles, and then you can read them at
14701 leisure from your local disk. No more World Wide Wait for you.
14703 @node Archiving Mail
14704 @subsection Archiving Mail
14705 @cindex archiving mail
14706 @cindex backup of mail
14708 Some of the back ends, notably @code{nnml}, @code{nnfolder}, and
14709 @code{nnmaildir}, now actually store the article marks with each group.
14710 For these servers, archiving and restoring a group while preserving
14711 marks is fairly simple.
14713 (Preserving the group level and group parameters as well still
14714 requires ritual dancing and sacrifices to the @file{.newsrc.eld} deity
14717 To archive an entire @code{nnml}, @code{nnfolder}, or @code{nnmaildir}
14718 server, take a recursive copy of the server directory. There is no need
14719 to shut down Gnus, so archiving may be invoked by @code{cron} or
14720 similar. You restore the data by restoring the directory tree, and
14721 adding a server definition pointing to that directory in Gnus. The
14722 @ref{Article Backlog}, @ref{Asynchronous Fetching} and other things
14723 might interfere with overwriting data, so you may want to shut down Gnus
14724 before you restore the data.
14726 It is also possible to archive individual @code{nnml},
14727 @code{nnfolder}, or @code{nnmaildir} groups, while preserving marks.
14728 For @code{nnml} or @code{nnmaildir}, you copy all files in the group's
14729 directory. For @code{nnfolder} you need to copy both the base folder
14730 file itself (@file{FOO}, say), and the marks file (@file{FOO.mrk} in
14731 this example). Restoring the group is done with @kbd{G m} from the Group
14732 buffer. The last step makes Gnus notice the new directory.
14733 @code{nnmaildir} notices the new directory automatically, so @kbd{G m}
14734 is unnecessary in that case.
14737 @subsection Web Searches
14742 @cindex Usenet searches
14743 @cindex searching the Usenet
14745 It's, like, too neat to search the Usenet for articles that match a
14746 string, but it, like, totally @emph{sucks}, like, totally, to use one of
14747 those, like, Web browsers, and you, like, have to, rilly, like, look at
14748 the commercials, so, like, with Gnus you can do @emph{rad}, rilly,
14749 searches without having to use a browser.
14751 The @code{nnweb} back end allows an easy interface to the mighty search
14752 engine. You create an @code{nnweb} group, enter a search pattern, and
14753 then enter the group and read the articles like you would any normal
14754 group. The @kbd{G w} command in the group buffer (@pxref{Foreign
14755 Groups}) will do this in an easy-to-use fashion.
14757 @code{nnweb} groups don't really lend themselves to being solid
14758 groups---they have a very fleeting idea of article numbers. In fact,
14759 each time you enter an @code{nnweb} group (not even changing the search
14760 pattern), you are likely to get the articles ordered in a different
14761 manner. Not even using duplicate suppression (@pxref{Duplicate
14762 Suppression}) will help, since @code{nnweb} doesn't even know the
14763 @code{Message-ID} of the articles before reading them using some search
14764 engines (Google, for instance). The only possible way to keep track
14765 of which articles you've read is by scoring on the @code{Date}
14766 header---mark all articles posted before the last date you read the
14769 If the search engine changes its output substantially, @code{nnweb}
14770 won't be able to parse it and will fail. One could hardly fault the Web
14771 providers if they were to do this---their @emph{raison d'être} is to
14772 make money off of advertisements, not to provide services to the
14773 community. Since @code{nnweb} washes the ads off all the articles, one
14774 might think that the providers might be somewhat miffed. We'll see.
14776 You must have the @code{url} and @code{w3} package installed to be able
14777 to use @code{nnweb}.
14779 Virtual server variables:
14784 What search engine type is being used. The currently supported types
14785 are @code{google}, @code{dejanews}, and @code{gmane}. Note that
14786 @code{dejanews} is an alias to @code{google}.
14789 @vindex nnweb-search
14790 The search string to feed to the search engine.
14792 @item nnweb-max-hits
14793 @vindex nnweb-max-hits
14794 Advisory maximum number of hits per search to display. The default is
14797 @item nnweb-type-definition
14798 @vindex nnweb-type-definition
14799 Type-to-definition alist. This alist says what @code{nnweb} should do
14800 with the various search engine types. The following elements must be
14805 Function to decode the article and provide something that Gnus
14809 Function to create an article number to message header and URL alist.
14812 Function to send the search string to the search engine.
14815 The address the aforementioned function should send the search string
14819 Format string URL to fetch an article by @code{Message-ID}.
14826 @subsection Slashdot
14830 Slashdot (@uref{http://slashdot.org/}) is a popular news site, with
14831 lively discussion following the news articles. @code{nnslashdot} will
14832 let you read this forum in a convenient manner.
14834 The easiest way to read this source is to put something like the
14835 following in your @file{.gnus.el} file:
14838 (setq gnus-secondary-select-methods
14839 '((nnslashdot "")))
14842 This will make Gnus query the @code{nnslashdot} back end for new comments
14843 and groups. The @kbd{F} command will subscribe each new news article as
14844 a new Gnus group, and you can read the comments by entering these
14845 groups. (Note that the default subscription method is to subscribe new
14846 groups as zombies. Other methods are available (@pxref{Subscription
14849 If you want to remove an old @code{nnslashdot} group, the @kbd{G DEL}
14850 command is the most handy tool (@pxref{Foreign Groups}).
14852 When following up to @code{nnslashdot} comments (or posting new
14853 comments), some light @sc{html}izations will be performed. In
14854 particular, text quoted with @samp{> } will be quoted with
14855 @code{blockquote} instead, and signatures will have @code{br} added to
14856 the end of each line. Other than that, you can just write @sc{html}
14857 directly into the message buffer. Note that Slashdot filters out some
14860 The following variables can be altered to change its behavior:
14863 @item nnslashdot-threaded
14864 Whether @code{nnslashdot} should display threaded groups or not. The
14865 default is @code{t}. To be able to display threads, @code{nnslashdot}
14866 has to retrieve absolutely all comments in a group upon entry. If a
14867 threaded display is not required, @code{nnslashdot} will only retrieve
14868 the comments that are actually wanted by the user. Threading is nicer,
14869 but much, much slower than unthreaded.
14871 @item nnslashdot-login-name
14872 @vindex nnslashdot-login-name
14873 The login name to use when posting.
14875 @item nnslashdot-password
14876 @vindex nnslashdot-password
14877 The password to use when posting.
14879 @item nnslashdot-directory
14880 @vindex nnslashdot-directory
14881 Where @code{nnslashdot} will store its files. The default is
14882 @samp{~/News/slashdot/}.
14884 @item nnslashdot-active-url
14885 @vindex nnslashdot-active-url
14886 The @sc{url} format string that will be used to fetch the information on
14887 news articles and comments. The default is
14888 @samp{http://slashdot.org/search.pl?section=&min=%d}.
14890 @item nnslashdot-comments-url
14891 @vindex nnslashdot-comments-url
14892 The @sc{url} format string that will be used to fetch comments. The
14894 @samp{http://slashdot.org/comments.pl?sid=%s&threshold=%d&commentsort=%d&mode=flat&startat=%d}.
14896 @item nnslashdot-article-url
14897 @vindex nnslashdot-article-url
14898 The @sc{url} format string that will be used to fetch the news article. The
14900 @samp{http://slashdot.org/article.pl?sid=%s&mode=nocomment}.
14902 @item nnslashdot-threshold
14903 @vindex nnslashdot-threshold
14904 The score threshold. The default is -1.
14906 @item nnslashdot-group-number
14907 @vindex nnslashdot-group-number
14908 The number of old groups, in addition to the ten latest, to keep
14909 updated. The default is 0.
14916 @subsection Ultimate
14918 @cindex Ultimate Bulletin Board
14920 The Ultimate Bulletin Board (@uref{http://www.ultimatebb.com/}) is
14921 probably the most popular Web bulletin board system used. It has a
14922 quite regular and nice interface, and it's possible to get the
14923 information Gnus needs to keep groups updated.
14925 The easiest way to get started with @code{nnultimate} is to say
14926 something like the following in the group buffer: @kbd{B nnultimate RET
14927 http://www.tcj.com/messboard/ubbcgi/ RET}. (Substitute the @sc{url}
14928 (not including @samp{Ultimate.cgi} or the like at the end) for a forum
14929 you're interested in; there's quite a list of them on the Ultimate web
14930 site.) Then subscribe to the groups you're interested in from the
14931 server buffer, and read them from the group buffer.
14933 The following @code{nnultimate} variables can be altered:
14936 @item nnultimate-directory
14937 @vindex nnultimate-directory
14938 The directory where @code{nnultimate} stores its files. The default is
14939 @samp{~/News/ultimate/}.
14944 @subsection Web Archive
14946 @cindex Web Archive
14948 Some mailing lists only have archives on Web servers, such as
14949 @uref{http://www.egroups.com/} and
14950 @uref{http://www.mail-archive.com/}. It has a quite regular and nice
14951 interface, and it's possible to get the information Gnus needs to keep
14954 The easiest way to get started with @code{nnwarchive} is to say
14955 something like the following in the group buffer: @kbd{M-x
14956 gnus-group-make-warchive-group RET an_egroup RET egroups RET
14957 www.egroups.com RET your@@email.address RET}. (Substitute the
14958 @sc{an_egroup} with the mailing list you subscribed, the
14959 @sc{your@@email.address} with your email address.), or to browse the
14960 back end by @kbd{B nnwarchive RET mail-archive RET}.
14962 The following @code{nnwarchive} variables can be altered:
14965 @item nnwarchive-directory
14966 @vindex nnwarchive-directory
14967 The directory where @code{nnwarchive} stores its files. The default is
14968 @samp{~/News/warchive/}.
14970 @item nnwarchive-login
14971 @vindex nnwarchive-login
14972 The account name on the web server.
14974 @item nnwarchive-passwd
14975 @vindex nnwarchive-passwd
14976 The password for your account on the web server.
14984 Some sites have RDF site summary (RSS)
14985 @uref{http://purl.org/rss/1.0/spec}. It has a quite regular and nice
14986 interface, and it's possible to get the information Gnus needs to keep
14989 The easiest way to get started with @code{nnrss} is to say something
14990 like the following in the group buffer: @kbd{B nnrss RET RET}, then
14993 The following @code{nnrss} variables can be altered:
14996 @item nnrss-directory
14997 @vindex nnrss-directory
14998 The directory where @code{nnrss} stores its files. The default is
14999 @samp{~/News/rss/}.
15003 The following code may be helpful, if you want to show the description in
15004 the summary buffer.
15007 (add-to-list 'nnmail-extra-headers nnrss-description-field)
15008 (setq gnus-summary-line-format "%U%R%z%I%(%[%4L: %-15,15f%]%) %s%uX\n")
15010 (defun gnus-user-format-function-X (header)
15012 (assq nnrss-description-field (mail-header-extra header))))
15013 (if descr (concat "\n\t" (cdr descr)) "")))
15016 The following code may be useful to open an nnrss url directly from the
15019 (require 'browse-url)
15021 (defun browse-nnrss-url( arg )
15023 (let ((url (assq nnrss-url-field
15026 (assq (gnus-summary-article-number)
15027 gnus-newsgroup-data))))))
15030 (browse-url (cdr url))
15031 (gnus-summary-mark-as-read-forward 1))
15032 (gnus-summary-scroll-up arg))))
15034 (eval-after-load "gnus"
15035 #'(define-key gnus-summary-mode-map
15036 (kbd "<RET>") 'browse-nnrss-url))
15037 (add-to-list 'nnmail-extra-headers nnrss-url-field)
15040 @node Customizing w3
15041 @subsection Customizing w3
15047 Gnus uses the url library to fetch web pages and Emacs/w3 to display web
15048 pages. Emacs/w3 is documented in its own manual, but there are some
15049 things that may be more relevant for Gnus users.
15051 For instance, a common question is how to make Emacs/w3 follow links
15052 using the @code{browse-url} functions (which will call some external web
15053 browser like Netscape). Here's one way:
15056 (eval-after-load "w3"
15058 (fset 'w3-fetch-orig (symbol-function 'w3-fetch))
15059 (defun w3-fetch (&optional url target)
15060 (interactive (list (w3-read-url-with-default)))
15061 (if (eq major-mode 'gnus-article-mode)
15063 (w3-fetch-orig url target)))))
15066 Put that in your @file{.emacs} file, and hitting links in w3-rendered
15067 @sc{html} in the Gnus article buffers will use @code{browse-url} to
15076 @sc{imap} is a network protocol for reading mail (or news, or ...),
15077 think of it as a modernized @sc{nntp}. Connecting to a @sc{imap}
15078 server is much similar to connecting to a news server, you just
15079 specify the network address of the server.
15081 @sc{imap} has two properties. First, @sc{imap} can do everything that
15082 POP can, it can hence be viewed as a POP++. Secondly, @sc{imap} is a
15083 mail storage protocol, similar to @sc{nntp} being a news storage
15084 protocol -- however, @sc{imap} offers more features than @sc{nntp}
15085 because news is more or less read-only whereas mail is read-write.
15087 If you want to use @sc{imap} as a POP++, use an imap entry in
15088 @code{mail-sources}. With this, Gnus will fetch mails from the
15089 @sc{imap} server and store them on the local disk. This is not the
15090 usage described in this section--@xref{Mail Sources}.
15092 If you want to use @sc{imap} as a mail storage protocol, use an nnimap
15093 entry in @code{gnus-secondary-select-methods}. With this, Gnus will
15094 manipulate mails stored on the @sc{imap} server. This is the kind of
15095 usage explained in this section.
15097 A server configuration in @code{~/.gnus} with a few @sc{imap} servers
15098 might look something like the following. (Note that for SSL/TLS, you
15099 need external programs and libraries, see below.)
15102 (setq gnus-secondary-select-methods
15103 '((nnimap "simpleserver") ; no special configuration
15104 ; perhaps a ssh port forwarded server:
15106 (nnimap-address "localhost")
15107 (nnimap-server-port 1430))
15108 ; a UW server running on localhost
15110 (nnimap-server-port 143)
15111 (nnimap-address "localhost")
15112 (nnimap-list-pattern ("INBOX" "mail/*")))
15113 ; anonymous public cyrus server:
15114 (nnimap "cyrus.andrew.cmu.edu"
15115 (nnimap-authenticator anonymous)
15116 (nnimap-list-pattern "archive.*")
15117 (nnimap-stream network))
15118 ; a ssl server on a non-standard port:
15120 (nnimap-address "vic20.somewhere.com")
15121 (nnimap-server-port 9930)
15122 (nnimap-stream ssl))))
15125 The following variables can be used to create a virtual @code{nnimap}
15130 @item nnimap-address
15131 @vindex nnimap-address
15133 The address of the remote @sc{imap} server. Defaults to the virtual
15134 server name if not specified.
15136 @item nnimap-server-port
15137 @vindex nnimap-server-port
15138 Port on server to contact. Defaults to port 143, or 993 for SSL.
15140 Note that this should be an integer, example server specification:
15143 (nnimap "mail.server.com"
15144 (nnimap-server-port 4711))
15147 @item nnimap-list-pattern
15148 @vindex nnimap-list-pattern
15149 String or list of strings of mailboxes to limit available groups to.
15150 This is used when the server has very many mailboxes and you're only
15151 interested in a few -- some servers export your home directory via
15152 @sc{imap}, you'll probably want to limit the mailboxes to those in
15153 @file{~/Mail/*} then.
15155 The string can also be a cons of REFERENCE and the string as above, what
15156 REFERENCE is used for is server specific, but on the University of
15157 Washington server it's a directory that will be concatenated with the
15160 Example server specification:
15163 (nnimap "mail.server.com"
15164 (nnimap-list-pattern ("INBOX" "Mail/*" "alt.sex.*"
15165 ("~friend/Mail/" . "list/*"))))
15168 @item nnimap-stream
15169 @vindex nnimap-stream
15170 The type of stream used to connect to your server. By default, nnimap
15171 will detect and automatically use all of the below, with the exception
15172 of SSL/TLS. (@sc{imap} over SSL/TLS is being replaced by STARTTLS, which
15173 can be automatically detected, but it's not widely deployed yet.)
15175 Example server specification:
15178 (nnimap "mail.server.com"
15179 (nnimap-stream ssl))
15182 Please note that the value of @code{nnimap-stream} is a symbol!
15186 @dfn{gssapi:} Connect with GSSAPI (usually Kerberos 5). Requires the
15187 @samp{imtest} program.
15189 @dfn{kerberos4:} Connect with Kerberos 4. Requires the @samp{imtest} program.
15191 @dfn{starttls:} Connect via the STARTTLS extension (similar to
15192 SSL). Requires the external library @samp{starttls.el} and program
15195 @dfn{ssl:} Connect through SSL. Requires OpenSSL (the program
15196 @samp{openssl}) or SSLeay (@samp{s_client}) as well as the external
15197 library @samp{ssl.el}.
15199 @dfn{shell:} Use a shell command to start @sc{imap} connection.
15201 @dfn{network:} Plain, TCP/IP network connection.
15204 @vindex imap-kerberos4-program
15205 The @samp{imtest} program is shipped with Cyrus IMAPD. If you're
15206 using @samp{imtest} from Cyrus IMAPD < 2.0.14 (which includes version
15207 1.5.x and 1.6.x) you need to frob @code{imap-process-connection-type}
15208 to make @code{imap.el} use a pty instead of a pipe when communicating
15209 with @samp{imtest}. You will then suffer from a line length
15210 restrictions on @sc{imap} commands, which might make Gnus seem to hang
15211 indefinitely if you have many articles in a mailbox. The variable
15212 @code{imap-kerberos4-program} contain parameters to pass to the imtest
15215 @vindex imap-ssl-program
15216 For SSL connections, the OpenSSL program is available from
15217 @uref{http://www.openssl.org/}. OpenSSL was formerly known as SSLeay,
15218 and nnimap support it too - although the most recent versions of
15219 SSLeay, 0.9.x, are known to have serious bugs making it
15220 useless. Earlier versions, especially 0.8.x, of SSLeay are known to
15221 work. The variable @code{imap-ssl-program} contain parameters to pass
15222 to OpenSSL/SSLeay. You also need @samp{ssl.el} (from the W3
15223 distribution, for instance).
15225 @vindex imap-shell-program
15226 @vindex imap-shell-host
15227 For @sc{imap} connections using the @code{shell} stream, the variable
15228 @code{imap-shell-program} specify what program to call.
15230 @item nnimap-authenticator
15231 @vindex nnimap-authenticator
15233 The authenticator used to connect to the server. By default, nnimap
15234 will use the most secure authenticator your server is capable of.
15236 Example server specification:
15239 (nnimap "mail.server.com"
15240 (nnimap-authenticator anonymous))
15243 Please note that the value of @code{nnimap-authenticator} is a symbol!
15247 @dfn{gssapi:} GSSAPI (usually kerberos 5) authentication. Requires
15248 external program @code{imtest}.
15250 @dfn{kerberos4:} Kerberos 4 authentication. Requires external program
15253 @dfn{digest-md5:} Encrypted username/password via DIGEST-MD5. Requires
15254 external library @code{digest-md5.el}.
15256 @dfn{cram-md5:} Encrypted username/password via CRAM-MD5.
15258 @dfn{login:} Plain-text username/password via LOGIN.
15260 @dfn{anonymous:} Login as `anonymous', supplying your email address as password.
15263 @item nnimap-expunge-on-close
15265 @vindex nnimap-expunge-on-close
15266 Unlike Parmenides the @sc{imap} designers has decided that things that
15267 doesn't exist actually does exist. More specifically, @sc{imap} has
15268 this concept of marking articles @code{Deleted} which doesn't actually
15269 delete them, and this (marking them @code{Deleted}, that is) is what
15270 nnimap does when you delete a article in Gnus (with @kbd{B DEL} or
15273 Since the articles aren't really removed when we mark them with the
15274 @code{Deleted} flag we'll need a way to actually delete them. Feel like
15275 running in circles yet?
15277 Traditionally, nnimap has removed all articles marked as @code{Deleted}
15278 when closing a mailbox but this is now configurable by this server
15281 The possible options are:
15286 The default behavior, delete all articles marked as "Deleted" when
15289 Never actually delete articles. Currently there is no way of showing
15290 the articles marked for deletion in nnimap, but other @sc{imap} clients
15291 may allow you to do this. If you ever want to run the EXPUNGE command
15292 manually, @xref{Expunging mailboxes}.
15294 When closing mailboxes, nnimap will ask if you wish to expunge deleted
15299 @item nnimap-importantize-dormant
15300 @vindex nnimap-importantize-dormant
15302 If non-nil (the default), marks dormant articles as ticked (as well),
15303 for other @sc{imap} clients. Within Gnus, dormant articles will
15304 naturally still (only) be marked as dormant. This is to make dormant
15305 articles stand out, just like ticked articles, in other @sc{imap}
15306 clients. (In other words, Gnus has two ``Tick'' marks and @sc{imap}
15309 Probably the only reason for frobing this would be if you're trying
15310 enable per-user persistant dormant flags, using something like:
15313 (setcdr (assq 'dormant nnimap-mark-to-flag-alist)
15314 (format "gnus-dormant-%s" (user-login-name)))
15315 (setcdr (assq 'dormant nnimap-mark-to-predicate-alist)
15316 (format "KEYWORD gnus-dormant-%s" (user-login-name)))
15319 In this case, you would not want the per-user dormant flag showing up
15320 as ticked for other users.
15322 @item nnimap-expunge-search-string
15324 @vindex nnimap-expunge-search-string
15326 This variable contain the @sc{imap} search command sent to server when
15327 searching for articles eligible for expiring. The default is
15328 @code{"UID %s NOT SINCE %s"}, where the first @code{%s} is replaced by
15329 UID set and the second @code{%s} is replaced by a date.
15331 Probably the only useful value to change this to is
15332 @code{"UID %s NOT SENTSINCE %s"}, which makes nnimap use the Date: in
15333 messages instead of the internal article date. See section 6.4.4 of
15334 RFC 2060 for more information on valid strings.
15336 @item nnimap-authinfo-file
15337 @vindex nnimap-authinfo-file
15339 A file containing credentials used to log in on servers. The format is
15340 (almost) the same as the @code{ftp} @file{~/.netrc} file. See the
15341 variable @code{nntp-authinfo-file} for exact syntax; also see
15347 * Splitting in IMAP:: Splitting mail with nnimap.
15348 * Expiring in IMAP:: Expiring mail with nnimap.
15349 * Editing IMAP ACLs:: Limiting/enabling other users access to a mailbox.
15350 * Expunging mailboxes:: Equivalent of a "compress mailbox" button.
15351 * A note on namespaces:: How to (not) use IMAP namespace in Gnus.
15356 @node Splitting in IMAP
15357 @subsection Splitting in IMAP
15358 @cindex splitting imap mail
15360 Splitting is something Gnus users has loved and used for years, and now
15361 the rest of the world is catching up. Yeah, dream on, not many
15362 @sc{imap} server has server side splitting and those that have splitting
15363 seem to use some non-standard protocol. This means that @sc{imap}
15364 support for Gnus has to do it's own splitting.
15368 Here are the variables of interest:
15372 @item nnimap-split-crosspost
15373 @cindex splitting, crosspost
15375 @vindex nnimap-split-crosspost
15377 If non-nil, do crossposting if several split methods match the mail. If
15378 nil, the first match in @code{nnimap-split-rule} found will be used.
15380 Nnmail equivalent: @code{nnmail-crosspost}.
15382 @item nnimap-split-inbox
15383 @cindex splitting, inbox
15385 @vindex nnimap-split-inbox
15387 A string or a list of strings that gives the name(s) of @sc{imap}
15388 mailboxes to split from. Defaults to nil, which means that splitting is
15392 (setq nnimap-split-inbox
15393 '("INBOX" ("~/friend/Mail" . "lists/*") "lists.imap"))
15396 No nnmail equivalent.
15398 @item nnimap-split-rule
15399 @cindex Splitting, rules
15400 @vindex nnimap-split-rule
15402 New mail found in @code{nnimap-split-inbox} will be split according to
15405 This variable contains a list of lists, where the first element in the
15406 sublist gives the name of the @sc{imap} mailbox to move articles
15407 matching the regexp in the second element in the sublist. Got that?
15408 Neither did I, we need examples.
15411 (setq nnimap-split-rule
15413 "^Sender: owner-nnimap@@vic20.globalcom.se")
15414 ("INBOX.junk" "^Subject:.*MAKE MONEY")
15415 ("INBOX.private" "")))
15418 This will put all articles from the nnimap mailing list into mailbox
15419 INBOX.nnimap, all articles containing MAKE MONEY in the Subject: line
15420 into INBOX.junk and everything else in INBOX.private.
15422 The first string may contain `\\1' forms, like the ones used by
15423 replace-match to insert sub-expressions from the matched text. For
15427 ("INBOX.lists.\\1" "^Sender: owner-\\([a-z-]+\\)@@")
15430 The first element can also be the symbol @code{junk} to indicate that
15431 matching messages should simply be deleted. Use with care.
15433 The second element can also be a function. In that case, it will be
15434 called with the first element of the rule as the argument, in a buffer
15435 containing the headers of the article. It should return a non-nil value
15436 if it thinks that the mail belongs in that group.
15438 Nnmail users might recollect that the last regexp had to be empty to
15439 match all articles (like in the example above). This is not required in
15440 nnimap. Articles not matching any of the regexps will not be moved out
15441 of your inbox. (This might affect performance if you keep lots of
15442 unread articles in your inbox, since the splitting code would go over
15443 them every time you fetch new mail.)
15445 These rules are processed from the beginning of the alist toward the
15446 end. The first rule to make a match will "win", unless you have
15447 crossposting enabled. In that case, all matching rules will "win".
15449 This variable can also have a function as its value, the function will
15450 be called with the headers narrowed and should return a group where it
15451 thinks the article should be split to. See @code{nnimap-split-fancy}.
15453 The splitting code tries to create mailboxes if it needs to.
15455 To allow for different split rules on different virtual servers, and
15456 even different split rules in different inboxes on the same server,
15457 the syntax of this variable have been extended along the lines of:
15460 (setq nnimap-split-rule
15461 '(("my1server" (".*" (("ding" "ding@@gnus.org")
15462 ("junk" "From:.*Simon")))
15463 ("my2server" ("INBOX" nnimap-split-fancy))
15464 ("my[34]server" (".*" (("private" "To:.*Simon")
15465 ("junk" my-junk-func)))))
15468 The virtual server name is in fact a regexp, so that the same rules
15469 may apply to several servers. In the example, the servers
15470 @code{my3server} and @code{my4server} both use the same rules.
15471 Similarly, the inbox string is also a regexp. The actual splitting
15472 rules are as before, either a function, or a list with group/regexp or
15473 group/function elements.
15475 Nnmail equivalent: @code{nnmail-split-methods}.
15477 @item nnimap-split-predicate
15479 @vindex nnimap-split-predicate
15481 Mail matching this predicate in @code{nnimap-split-inbox} will be
15482 split, it is a string and the default is @samp{UNSEEN UNDELETED}.
15484 This might be useful if you use another @sc{imap} client to read mail in
15485 your inbox but would like Gnus to split all articles in the inbox
15486 regardless of readedness. Then you might change this to
15489 @item nnimap-split-fancy
15490 @cindex splitting, fancy
15491 @findex nnimap-split-fancy
15492 @vindex nnimap-split-fancy
15494 It's possible to set @code{nnimap-split-rule} to
15495 @code{nnmail-split-fancy} if you want to use fancy
15496 splitting. @xref{Fancy Mail Splitting}.
15498 However, to be able to have different fancy split rules for nnmail and
15499 nnimap back ends you can set @code{nnimap-split-rule} to
15500 @code{nnimap-split-fancy} and define the nnimap specific fancy split
15501 rule in @code{nnimap-split-fancy}.
15506 (setq nnimap-split-rule 'nnimap-split-fancy
15507 nnimap-split-fancy ...)
15510 Nnmail equivalent: @code{nnmail-split-fancy}.
15514 @node Expiring in IMAP
15515 @subsection Expiring in IMAP
15516 @cindex expiring imap mail
15518 Even though @sc{nnimap} is not a proper @sc{nnmail} derived back end,
15519 it supports most features in regular expiring (@pxref{Expiring Mail}).
15520 Unlike splitting in IMAP (@pxref{Splitting in IMAP}) it do not clone
15521 the @sc{nnmail} variables (i.e., creating @var{nnimap-expiry-wait})
15522 but reuse the @sc{nnmail} variables. What follows below are the
15523 variables used by the @sc{nnimap} expiry process.
15525 A note on how the expire mark is stored on the @sc{imap} server is
15526 appropriate here as well. The expire mark is translated into a
15527 @sc{imap} client specific mark, @code{gnus-expire}, and stored on the
15528 message. This means that likely only Gnus will understand and treat
15529 the @code{gnus-expire} mark properly, although other clients may allow
15530 you to view client specific flags on the message. It also means that
15531 your server must support permanent storage of client specific flags on
15532 messages. Most do, fortunately.
15536 @item nnmail-expiry-wait
15537 @item nnmail-expiry-wait-function
15539 These variables are fully supported. The expire value can be a
15540 number, the symbol @var{immediate} or @var{never}.
15542 @item nnmail-expiry-target
15544 This variable is supported, and internally implemented by calling the
15545 @sc{nnmail} functions that handle this. It contains an optimization
15546 that if the destination is a IMAP group on the same server, the
15547 article is copied instead of appended (that is, uploaded again).
15551 @node Editing IMAP ACLs
15552 @subsection Editing IMAP ACLs
15553 @cindex editing imap acls
15554 @cindex Access Control Lists
15555 @cindex Editing @sc{imap} ACLs
15557 @findex gnus-group-nnimap-edit-acl
15559 ACL stands for Access Control List. ACLs are used in @sc{imap} for
15560 limiting (or enabling) other users access to your mail boxes. Not all
15561 @sc{imap} servers support this, this function will give an error if it
15564 To edit a ACL for a mailbox, type @kbd{G l}
15565 (@code{gnus-group-edit-nnimap-acl}) and you'll be presented with a ACL
15566 editing window with detailed instructions.
15568 Some possible uses:
15572 Giving "anyone" the "lrs" rights (lookup, read, keep seen/unseen flags)
15573 on your mailing list mailboxes enables other users on the same server to
15574 follow the list without subscribing to it.
15576 At least with the Cyrus server, you are required to give the user
15577 "anyone" posting ("p") capabilities to have "plussing" work (that is,
15578 mail sent to user+mailbox@@domain ending up in the @sc{imap} mailbox
15582 @node Expunging mailboxes
15583 @subsection Expunging mailboxes
15587 @cindex Manual expunging
15589 @findex gnus-group-nnimap-expunge
15591 If you're using the @code{never} setting of @code{nnimap-expunge-on-close},
15592 you may want the option of expunging all deleted articles in a mailbox
15593 manually. This is exactly what @kbd{G x} does.
15595 Currently there is no way of showing deleted articles, you can just
15598 @node A note on namespaces
15599 @subsection A note on namespaces
15600 @cindex IMAP namespace
15603 The IMAP protocol has a concept called namespaces, described by the
15604 following text in the RFC:
15607 5.1.2. Mailbox Namespace Naming Convention
15609 By convention, the first hierarchical element of any mailbox name
15610 which begins with "#" identifies the "namespace" of the remainder of
15611 the name. This makes it possible to disambiguate between different
15612 types of mailbox stores, each of which have their own namespaces.
15614 For example, implementations which offer access to USENET
15615 newsgroups MAY use the "#news" namespace to partition the USENET
15616 newsgroup namespace from that of other mailboxes. Thus, the
15617 comp.mail.misc newsgroup would have an mailbox name of
15618 "#news.comp.mail.misc", and the name "comp.mail.misc" could refer
15619 to a different object (e.g. a user's private mailbox).
15622 While there is nothing in this text that warrants concern for the IMAP
15623 implementation in Gnus, some servers use namespace prefixes in a way
15624 that does not work with how Gnus uses mailbox names.
15626 Specifically, University of Washington's IMAP server uses mailbox
15627 names like @code{#driver.mbx/read-mail} which are valid only in the
15628 @sc{create} and @sc{append} commands. After the mailbox is created
15629 (or a messages is appended to a mailbox), it must be accessed without
15630 the namespace prefix, i.e @code{read-mail}. Since Gnus do not make it
15631 possible for the user to guarantee that user entered mailbox names
15632 will only be used with the CREATE and APPEND commands, you should
15633 simply not use the namespace prefixed mailbox names in Gnus.
15635 See the UoW @sc{imapd} documentation for the @code{#driver.*/} prefix
15636 for more information on how to use the prefixes. They are a power
15637 tool and should be used only if you are sure what the effects are.
15639 @node Other Sources
15640 @section Other Sources
15642 Gnus can do more than just read news or mail. The methods described
15643 below allow Gnus to view directories and files as if they were
15647 * Directory Groups:: You can read a directory as if it was a newsgroup.
15648 * Anything Groups:: Dired? Who needs dired?
15649 * Document Groups:: Single files can be the basis of a group.
15650 * SOUP:: Reading @sc{soup} packets ``offline''.
15651 * Mail-To-News Gateways:: Posting articles via mail-to-news gateways.
15655 @node Directory Groups
15656 @subsection Directory Groups
15658 @cindex directory groups
15660 If you have a directory that has lots of articles in separate files in
15661 it, you might treat it as a newsgroup. The files have to have numerical
15664 This might be an opportune moment to mention @code{ange-ftp} (and its
15665 successor @code{efs}), that most wonderful of all wonderful Emacs
15666 packages. When I wrote @code{nndir}, I didn't think much about it---a
15667 back end to read directories. Big deal.
15669 @code{ange-ftp} changes that picture dramatically. For instance, if you
15670 enter the @code{ange-ftp} file name
15671 @file{/ftp.hpc.uh.edu:/pub/emacs/ding-list/} as the directory name,
15672 @code{ange-ftp} or @code{efs} will actually allow you to read this
15673 directory over at @samp{sina} as a newsgroup. Distributed news ahoy!
15675 @code{nndir} will use @sc{nov} files if they are present.
15677 @code{nndir} is a ``read-only'' back end---you can't delete or expire
15678 articles with this method. You can use @code{nnmh} or @code{nnml} for
15679 whatever you use @code{nndir} for, so you could switch to any of those
15680 methods if you feel the need to have a non-read-only @code{nndir}.
15683 @node Anything Groups
15684 @subsection Anything Groups
15687 From the @code{nndir} back end (which reads a single spool-like
15688 directory), it's just a hop and a skip to @code{nneething}, which
15689 pretends that any arbitrary directory is a newsgroup. Strange, but
15692 When @code{nneething} is presented with a directory, it will scan this
15693 directory and assign article numbers to each file. When you enter such
15694 a group, @code{nneething} must create ``headers'' that Gnus can use.
15695 After all, Gnus is a newsreader, in case you're forgetting.
15696 @code{nneething} does this in a two-step process. First, it snoops each
15697 file in question. If the file looks like an article (i.e., the first
15698 few lines look like headers), it will use this as the head. If this is
15699 just some arbitrary file without a head (e.g. a C source file),
15700 @code{nneething} will cobble up a header out of thin air. It will use
15701 file ownership, name and date and do whatever it can with these
15704 All this should happen automatically for you, and you will be presented
15705 with something that looks very much like a newsgroup. Totally like a
15706 newsgroup, to be precise. If you select an article, it will be displayed
15707 in the article buffer, just as usual.
15709 If you select a line that represents a directory, Gnus will pop you into
15710 a new summary buffer for this @code{nneething} group. And so on. You can
15711 traverse the entire disk this way, if you feel like, but remember that
15712 Gnus is not dired, really, and does not intend to be, either.
15714 There are two overall modes to this action---ephemeral or solid. When
15715 doing the ephemeral thing (i.e., @kbd{G D} from the group buffer), Gnus
15716 will not store information on what files you have read, and what files
15717 are new, and so on. If you create a solid @code{nneething} group the
15718 normal way with @kbd{G m}, Gnus will store a mapping table between
15719 article numbers and file names, and you can treat this group like any
15720 other groups. When you activate a solid @code{nneething} group, you will
15721 be told how many unread articles it contains, etc., etc.
15726 @item nneething-map-file-directory
15727 @vindex nneething-map-file-directory
15728 All the mapping files for solid @code{nneething} groups will be stored
15729 in this directory, which defaults to @file{~/.nneething/}.
15731 @item nneething-exclude-files
15732 @vindex nneething-exclude-files
15733 All files that match this regexp will be ignored. Nice to use to exclude
15734 auto-save files and the like, which is what it does by default.
15736 @item nneething-include-files
15737 @vindex nneething-include-files
15738 Regexp saying what files to include in the group. If this variable is
15739 non-@code{nil}, only files matching this regexp will be included.
15741 @item nneething-map-file
15742 @vindex nneething-map-file
15743 Name of the map files.
15747 @node Document Groups
15748 @subsection Document Groups
15750 @cindex documentation group
15753 @code{nndoc} is a cute little thing that will let you read a single file
15754 as a newsgroup. Several files types are supported:
15761 The babyl (rmail) mail box.
15766 The standard Unix mbox file.
15768 @cindex MMDF mail box
15770 The MMDF mail box format.
15773 Several news articles appended into a file.
15776 @cindex rnews batch files
15777 The rnews batch transport format.
15778 @cindex forwarded messages
15781 Forwarded articles.
15784 Netscape mail boxes.
15787 @sc{mime} multipart messages.
15789 @item standard-digest
15790 The standard (RFC 1153) digest format.
15793 A @sc{mime} digest of messages.
15795 @item lanl-gov-announce
15796 Announcement messages from LANL Gov Announce.
15798 @item rfc822-forward
15799 A message forwarded according to RFC822.
15802 The Outlook mail box.
15805 The Outlook Express dbx mail box.
15808 A bounce message from the Exim MTA.
15811 A message forwarded according to informal rules.
15814 An RFC934-forwarded message.
15820 A digest of Clarinet brief news items.
15823 Non-standard digest format---matches most things, but does it badly.
15829 You can also use the special ``file type'' @code{guess}, which means
15830 that @code{nndoc} will try to guess what file type it is looking at.
15831 @code{digest} means that @code{nndoc} should guess what digest type the
15834 @code{nndoc} will not try to change the file or insert any extra headers into
15835 it---it will simply, like, let you use the file as the basis for a
15836 group. And that's it.
15838 If you have some old archived articles that you want to insert into your
15839 new & spiffy Gnus mail back end, @code{nndoc} can probably help you with
15840 that. Say you have an old @file{RMAIL} file with mail that you now want
15841 to split into your new @code{nnml} groups. You look at that file using
15842 @code{nndoc} (using the @kbd{G f} command in the group buffer
15843 (@pxref{Foreign Groups})), set the process mark on all the articles in
15844 the buffer (@kbd{M P b}, for instance), and then re-spool (@kbd{B r})
15845 using @code{nnml}. If all goes well, all the mail in the @file{RMAIL}
15846 file is now also stored in lots of @code{nnml} directories, and you can
15847 delete that pesky @file{RMAIL} file. If you have the guts!
15849 Virtual server variables:
15852 @item nndoc-article-type
15853 @vindex nndoc-article-type
15854 This should be one of @code{mbox}, @code{babyl}, @code{digest},
15855 @code{news}, @code{rnews}, @code{mmdf}, @code{forward}, @code{rfc934},
15856 @code{rfc822-forward}, @code{mime-parts}, @code{standard-digest},
15857 @code{slack-digest}, @code{clari-briefs}, @code{nsmail}, @code{outlook},
15858 @code{oe-dbx}, @code{mailman}, and @code{mail-in-mail} or @code{guess}.
15860 @item nndoc-post-type
15861 @vindex nndoc-post-type
15862 This variable says whether Gnus is to consider the group a news group or
15863 a mail group. There are two valid values: @code{mail} (the default)
15868 * Document Server Internals:: How to add your own document types.
15872 @node Document Server Internals
15873 @subsubsection Document Server Internals
15875 Adding new document types to be recognized by @code{nndoc} isn't
15876 difficult. You just have to whip up a definition of what the document
15877 looks like, write a predicate function to recognize that document type,
15878 and then hook into @code{nndoc}.
15880 First, here's an example document type definition:
15884 (article-begin . "^\^A\^A\^A\^A\n")
15885 (body-end . "^\^A\^A\^A\^A\n"))
15888 The definition is simply a unique @dfn{name} followed by a series of
15889 regexp pseudo-variable settings. Below are the possible
15890 variables---don't be daunted by the number of variables; most document
15891 types can be defined with very few settings:
15894 @item first-article
15895 If present, @code{nndoc} will skip past all text until it finds
15896 something that match this regexp. All text before this will be
15899 @item article-begin
15900 This setting has to be present in all document type definitions. It
15901 says what the beginning of each article looks like.
15903 @item head-begin-function
15904 If present, this should be a function that moves point to the head of
15907 @item nndoc-head-begin
15908 If present, this should be a regexp that matches the head of the
15911 @item nndoc-head-end
15912 This should match the end of the head of the article. It defaults to
15913 @samp{^$}---the empty line.
15915 @item body-begin-function
15916 If present, this function should move point to the beginning of the body
15920 This should match the beginning of the body of the article. It defaults
15923 @item body-end-function
15924 If present, this function should move point to the end of the body of
15928 If present, this should match the end of the body of the article.
15931 If present, this should match the end of the file. All text after this
15932 regexp will be totally ignored.
15936 So, using these variables @code{nndoc} is able to dissect a document
15937 file into a series of articles, each with a head and a body. However, a
15938 few more variables are needed since not all document types are all that
15939 news-like---variables needed to transform the head or the body into
15940 something that's palatable for Gnus:
15943 @item prepare-body-function
15944 If present, this function will be called when requesting an article. It
15945 will be called with point at the start of the body, and is useful if the
15946 document has encoded some parts of its contents.
15948 @item article-transform-function
15949 If present, this function is called when requesting an article. It's
15950 meant to be used for more wide-ranging transformation of both head and
15951 body of the article.
15953 @item generate-head-function
15954 If present, this function is called to generate a head that Gnus can
15955 understand. It is called with the article number as a parameter, and is
15956 expected to generate a nice head for the article in question. It is
15957 called when requesting the headers of all articles.
15961 Let's look at the most complicated example I can come up with---standard
15966 (first-article . ,(concat "^" (make-string 70 ?-) "\n\n+"))
15967 (article-begin . ,(concat "\n\n" (make-string 30 ?-) "\n\n+"))
15968 (prepare-body-function . nndoc-unquote-dashes)
15969 (body-end-function . nndoc-digest-body-end)
15970 (head-end . "^ ?$")
15971 (body-begin . "^ ?\n")
15972 (file-end . "^End of .*digest.*[0-9].*\n\\*\\*\\|^End of.*Digest *$")
15973 (subtype digest guess))
15976 We see that all text before a 70-width line of dashes is ignored; all
15977 text after a line that starts with that @samp{^End of} is also ignored;
15978 each article begins with a 30-width line of dashes; the line separating
15979 the head from the body may contain a single space; and that the body is
15980 run through @code{nndoc-unquote-dashes} before being delivered.
15982 To hook your own document definition into @code{nndoc}, use the
15983 @code{nndoc-add-type} function. It takes two parameters---the first is
15984 the definition itself and the second (optional) parameter says where in
15985 the document type definition alist to put this definition. The alist is
15986 traversed sequentially, and @code{nndoc-TYPE-type-p} is called for a given type @code{TYPE}. So @code{nndoc-mmdf-type-p} is called to see whether a document
15987 is of @code{mmdf} type, and so on. These type predicates should return
15988 @code{nil} if the document is not of the correct type; @code{t} if it is
15989 of the correct type; and a number if the document might be of the
15990 correct type. A high number means high probability; a low number means
15991 low probability with @samp{0} being the lowest valid number.
15999 In the PC world people often talk about ``offline'' newsreaders. These
16000 are thingies that are combined reader/news transport monstrosities.
16001 With built-in modem programs. Yecchh!
16003 Of course, us Unix Weenie types of human beans use things like
16004 @code{uucp} and, like, @code{nntpd} and set up proper news and mail
16005 transport things like Ghod intended. And then we just use normal
16008 However, it can sometimes be convenient to do something that's a bit
16009 easier on the brain if you have a very slow modem, and you're not really
16010 that interested in doing things properly.
16012 A file format called @sc{soup} has been developed for transporting news
16013 and mail from servers to home machines and back again. It can be a bit
16016 First some terminology:
16021 This is the machine that is connected to the outside world and where you
16022 get news and/or mail from.
16025 This is the machine that you want to do the actual reading and responding
16026 on. It is typically not connected to the rest of the world in any way.
16029 Something that contains messages and/or commands. There are two kinds
16033 @item message packets
16034 These are packets made at the server, and typically contain lots of
16035 messages for you to read. These are called @file{SoupoutX.tgz} by
16036 default, where @var{x} is a number.
16038 @item response packets
16039 These are packets made at the home machine, and typically contains
16040 replies that you've written. These are called @file{SoupinX.tgz} by
16041 default, where @var{x} is a number.
16051 You log in on the server and create a @sc{soup} packet. You can either
16052 use a dedicated @sc{soup} thingie (like the @code{awk} program), or you
16053 can use Gnus to create the packet with its @sc{soup} commands (@kbd{O
16054 s} and/or @kbd{G s b}; and then @kbd{G s p}) (@pxref{SOUP Commands}).
16057 You transfer the packet home. Rail, boat, car or modem will do fine.
16060 You put the packet in your home directory.
16063 You fire up Gnus on your home machine using the @code{nnsoup} back end as
16064 the native or secondary server.
16067 You read articles and mail and answer and followup to the things you
16068 want (@pxref{SOUP Replies}).
16071 You do the @kbd{G s r} command to pack these replies into a @sc{soup}
16075 You transfer this packet to the server.
16078 You use Gnus to mail this packet out with the @kbd{G s s} command.
16081 You then repeat until you die.
16085 So you basically have a bipartite system---you use @code{nnsoup} for
16086 reading and Gnus for packing/sending these @sc{soup} packets.
16089 * SOUP Commands:: Commands for creating and sending @sc{soup} packets
16090 * SOUP Groups:: A back end for reading @sc{soup} packets.
16091 * SOUP Replies:: How to enable @code{nnsoup} to take over mail and news.
16095 @node SOUP Commands
16096 @subsubsection SOUP Commands
16098 These are commands for creating and manipulating @sc{soup} packets.
16102 @kindex G s b (Group)
16103 @findex gnus-group-brew-soup
16104 Pack all unread articles in the current group
16105 (@code{gnus-group-brew-soup}). This command understands the
16106 process/prefix convention.
16109 @kindex G s w (Group)
16110 @findex gnus-soup-save-areas
16111 Save all @sc{soup} data files (@code{gnus-soup-save-areas}).
16114 @kindex G s s (Group)
16115 @findex gnus-soup-send-replies
16116 Send all replies from the replies packet
16117 (@code{gnus-soup-send-replies}).
16120 @kindex G s p (Group)
16121 @findex gnus-soup-pack-packet
16122 Pack all files into a @sc{soup} packet (@code{gnus-soup-pack-packet}).
16125 @kindex G s r (Group)
16126 @findex nnsoup-pack-replies
16127 Pack all replies into a replies packet (@code{nnsoup-pack-replies}).
16130 @kindex O s (Summary)
16131 @findex gnus-soup-add-article
16132 This summary-mode command adds the current article to a @sc{soup} packet
16133 (@code{gnus-soup-add-article}). It understands the process/prefix
16134 convention (@pxref{Process/Prefix}).
16139 There are a few variables to customize where Gnus will put all these
16144 @item gnus-soup-directory
16145 @vindex gnus-soup-directory
16146 Directory where Gnus will save intermediate files while composing
16147 @sc{soup} packets. The default is @file{~/SoupBrew/}.
16149 @item gnus-soup-replies-directory
16150 @vindex gnus-soup-replies-directory
16151 This is what Gnus will use as a temporary directory while sending our
16152 reply packets. @file{~/SoupBrew/SoupReplies/} is the default.
16154 @item gnus-soup-prefix-file
16155 @vindex gnus-soup-prefix-file
16156 Name of the file where Gnus stores the last used prefix. The default is
16157 @samp{gnus-prefix}.
16159 @item gnus-soup-packer
16160 @vindex gnus-soup-packer
16161 A format string command for packing a @sc{soup} packet. The default is
16162 @samp{tar cf - %s | gzip > $HOME/Soupout%d.tgz}.
16164 @item gnus-soup-unpacker
16165 @vindex gnus-soup-unpacker
16166 Format string command for unpacking a @sc{soup} packet. The default is
16167 @samp{gunzip -c %s | tar xvf -}.
16169 @item gnus-soup-packet-directory
16170 @vindex gnus-soup-packet-directory
16171 Where Gnus will look for reply packets. The default is @file{~/}.
16173 @item gnus-soup-packet-regexp
16174 @vindex gnus-soup-packet-regexp
16175 Regular expression matching @sc{soup} reply packets in
16176 @code{gnus-soup-packet-directory}.
16182 @subsubsection SOUP Groups
16185 @code{nnsoup} is the back end for reading @sc{soup} packets. It will
16186 read incoming packets, unpack them, and put them in a directory where
16187 you can read them at leisure.
16189 These are the variables you can use to customize its behavior:
16193 @item nnsoup-tmp-directory
16194 @vindex nnsoup-tmp-directory
16195 When @code{nnsoup} unpacks a @sc{soup} packet, it does it in this
16196 directory. (@file{/tmp/} by default.)
16198 @item nnsoup-directory
16199 @vindex nnsoup-directory
16200 @code{nnsoup} then moves each message and index file to this directory.
16201 The default is @file{~/SOUP/}.
16203 @item nnsoup-replies-directory
16204 @vindex nnsoup-replies-directory
16205 All replies will be stored in this directory before being packed into a
16206 reply packet. The default is @file{~/SOUP/replies/"}.
16208 @item nnsoup-replies-format-type
16209 @vindex nnsoup-replies-format-type
16210 The @sc{soup} format of the replies packets. The default is @samp{?n}
16211 (rnews), and I don't think you should touch that variable. I probably
16212 shouldn't even have documented it. Drats! Too late!
16214 @item nnsoup-replies-index-type
16215 @vindex nnsoup-replies-index-type
16216 The index type of the replies packet. The default is @samp{?n}, which
16217 means ``none''. Don't fiddle with this one either!
16219 @item nnsoup-active-file
16220 @vindex nnsoup-active-file
16221 Where @code{nnsoup} stores lots of information. This is not an ``active
16222 file'' in the @code{nntp} sense; it's an Emacs Lisp file. If you lose
16223 this file or mess it up in any way, you're dead. The default is
16224 @file{~/SOUP/active}.
16226 @item nnsoup-packer
16227 @vindex nnsoup-packer
16228 Format string command for packing a reply @sc{soup} packet. The default
16229 is @samp{tar cf - %s | gzip > $HOME/Soupin%d.tgz}.
16231 @item nnsoup-unpacker
16232 @vindex nnsoup-unpacker
16233 Format string command for unpacking incoming @sc{soup} packets. The
16234 default is @samp{gunzip -c %s | tar xvf -}.
16236 @item nnsoup-packet-directory
16237 @vindex nnsoup-packet-directory
16238 Where @code{nnsoup} will look for incoming packets. The default is
16241 @item nnsoup-packet-regexp
16242 @vindex nnsoup-packet-regexp
16243 Regular expression matching incoming @sc{soup} packets. The default is
16246 @item nnsoup-always-save
16247 @vindex nnsoup-always-save
16248 If non-@code{nil}, save the replies buffer after each posted message.
16254 @subsubsection SOUP Replies
16256 Just using @code{nnsoup} won't mean that your postings and mailings end
16257 up in @sc{soup} reply packets automagically. You have to work a bit
16258 more for that to happen.
16260 @findex nnsoup-set-variables
16261 The @code{nnsoup-set-variables} command will set the appropriate
16262 variables to ensure that all your followups and replies end up in the
16265 In specific, this is what it does:
16268 (setq message-send-news-function 'nnsoup-request-post)
16269 (setq message-send-mail-function 'nnsoup-request-mail)
16272 And that's it, really. If you only want news to go into the @sc{soup}
16273 system you just use the first line. If you only want mail to be
16274 @sc{soup}ed you use the second.
16277 @node Mail-To-News Gateways
16278 @subsection Mail-To-News Gateways
16279 @cindex mail-to-news gateways
16282 If your local @code{nntp} server doesn't allow posting, for some reason
16283 or other, you can post using one of the numerous mail-to-news gateways.
16284 The @code{nngateway} back end provides the interface.
16286 Note that you can't read anything from this back end---it can only be
16292 @item nngateway-address
16293 @vindex nngateway-address
16294 This is the address of the mail-to-news gateway.
16296 @item nngateway-header-transformation
16297 @vindex nngateway-header-transformation
16298 News headers often have to be transformed in some odd way or other
16299 for the mail-to-news gateway to accept it. This variable says what
16300 transformation should be called, and defaults to
16301 @code{nngateway-simple-header-transformation}. The function is called
16302 narrowed to the headers to be transformed and with one parameter---the
16305 This default function just inserts a new @code{To} header based on the
16306 @code{Newsgroups} header and the gateway address.
16307 For instance, an article with this @code{Newsgroups} header:
16310 Newsgroups: alt.religion.emacs
16313 will get this @code{To} header inserted:
16316 To: alt-religion-emacs@@GATEWAY
16319 The following pre-defined functions exist:
16321 @findex nngateway-simple-header-transformation
16324 @item nngateway-simple-header-transformation
16325 Creates a @code{To} header that looks like
16326 @var{newsgroup}@@@code{nngateway-address}.
16328 @findex nngateway-mail2news-header-transformation
16330 @item nngateway-mail2news-header-transformation
16331 Creates a @code{To} header that looks like
16332 @code{nngateway-address}.
16337 (setq gnus-post-method
16339 "mail2news@@replay.com"
16340 (nngateway-header-transformation
16341 nngateway-mail2news-header-transformation)))
16349 So, to use this, simply say something like:
16352 (setq gnus-post-method '(nngateway "GATEWAY.ADDRESS"))
16357 @node Combined Groups
16358 @section Combined Groups
16360 Gnus allows combining a mixture of all the other group types into bigger
16364 * Virtual Groups:: Combining articles from many groups.
16365 * Kibozed Groups:: Looking through parts of the newsfeed for articles.
16369 @node Virtual Groups
16370 @subsection Virtual Groups
16372 @cindex virtual groups
16373 @cindex merging groups
16375 An @dfn{nnvirtual group} is really nothing more than a collection of
16378 For instance, if you are tired of reading many small groups, you can
16379 put them all in one big group, and then grow tired of reading one
16380 big, unwieldy group. The joys of computing!
16382 You specify @code{nnvirtual} as the method. The address should be a
16383 regexp to match component groups.
16385 All marks in the virtual group will stick to the articles in the
16386 component groups. So if you tick an article in a virtual group, the
16387 article will also be ticked in the component group from whence it
16388 came. (And vice versa---marks from the component groups will also be
16389 shown in the virtual group.). To create an empty virtual group, run
16390 @kbd{G V} (@code{gnus-group-make-empty-virtual}) in the group buffer
16391 and edit the method regexp with @kbd{M-e}
16392 (@code{gnus-group-edit-group-method})
16394 Here's an example @code{nnvirtual} method that collects all Andrea Dworkin
16395 newsgroups into one, big, happy newsgroup:
16398 (nnvirtual "^alt\\.fan\\.andrea-dworkin$\\|^rec\\.dworkin.*")
16401 The component groups can be native or foreign; everything should work
16402 smoothly, but if your computer explodes, it was probably my fault.
16404 Collecting the same group from several servers might actually be a good
16405 idea if users have set the Distribution header to limit distribution.
16406 If you would like to read @samp{soc.motss} both from a server in Japan
16407 and a server in Norway, you could use the following as the group regexp:
16410 "^nntp\\+server\\.jp:soc\\.motss$\\|^nntp\\+server\\.no:soc\\.motss$"
16413 (Remember, though, that if you're creating the group with @kbd{G m}, you
16414 shouldn't double the backslashes, and you should leave off the quote
16415 characters at the beginning and the end of the string.)
16417 This should work kinda smoothly---all articles from both groups should
16418 end up in this one, and there should be no duplicates. Threading (and
16419 the rest) will still work as usual, but there might be problems with the
16420 sequence of articles. Sorting on date might be an option here
16421 (@pxref{Selecting a Group}).
16423 One limitation, however---all groups included in a virtual
16424 group have to be alive (i.e., subscribed or unsubscribed). Killed or
16425 zombie groups can't be component groups for @code{nnvirtual} groups.
16427 @vindex nnvirtual-always-rescan
16428 If the @code{nnvirtual-always-rescan} is non-@code{nil},
16429 @code{nnvirtual} will always scan groups for unread articles when
16430 entering a virtual group. If this variable is @code{nil} (which is the
16431 default) and you read articles in a component group after the virtual
16432 group has been activated, the read articles from the component group
16433 will show up when you enter the virtual group. You'll also see this
16434 effect if you have two virtual groups that have a component group in
16435 common. If that's the case, you should set this variable to @code{t}.
16436 Or you can just tap @code{M-g} on the virtual group every time before
16437 you enter it---it'll have much the same effect.
16439 @code{nnvirtual} can have both mail and news groups as component groups.
16440 When responding to articles in @code{nnvirtual} groups, @code{nnvirtual}
16441 has to ask the back end of the component group the article comes from
16442 whether it is a news or mail back end. However, when you do a @kbd{^},
16443 there is typically no sure way for the component back end to know this,
16444 and in that case @code{nnvirtual} tells Gnus that the article came from a
16445 not-news back end. (Just to be on the safe side.)
16447 @kbd{C-c C-n} in the message buffer will insert the @code{Newsgroups}
16448 line from the article you respond to in these cases.
16450 @code{nnvirtual} groups do not inherit anything but articles and marks
16451 from component groups---group parameters, for instance, are not
16455 @node Kibozed Groups
16456 @subsection Kibozed Groups
16460 @dfn{Kibozing} is defined by @sc{oed} as ``grepping through (parts of)
16461 the news feed''. @code{nnkiboze} is a back end that will do this for
16462 you. Oh joy! Now you can grind any @sc{nntp} server down to a halt
16463 with useless requests! Oh happiness!
16465 @kindex G k (Group)
16466 To create a kibozed group, use the @kbd{G k} command in the group
16469 The address field of the @code{nnkiboze} method is, as with
16470 @code{nnvirtual}, a regexp to match groups to be ``included'' in the
16471 @code{nnkiboze} group. That's where most similarities between @code{nnkiboze}
16472 and @code{nnvirtual} end.
16474 In addition to this regexp detailing component groups, an @code{nnkiboze} group
16475 must have a score file to say what articles are to be included in
16476 the group (@pxref{Scoring}).
16478 @kindex M-x nnkiboze-generate-groups
16479 @findex nnkiboze-generate-groups
16480 You must run @kbd{M-x nnkiboze-generate-groups} after creating the
16481 @code{nnkiboze} groups you want to have. This command will take time. Lots of
16482 time. Oodles and oodles of time. Gnus has to fetch the headers from
16483 all the articles in all the component groups and run them through the
16484 scoring process to determine if there are any articles in the groups
16485 that are to be part of the @code{nnkiboze} groups.
16487 Please limit the number of component groups by using restrictive
16488 regexps. Otherwise your sysadmin may become annoyed with you, and the
16489 @sc{nntp} site may throw you off and never let you back in again.
16490 Stranger things have happened.
16492 @code{nnkiboze} component groups do not have to be alive---they can be dead,
16493 and they can be foreign. No restrictions.
16495 @vindex nnkiboze-directory
16496 The generation of an @code{nnkiboze} group means writing two files in
16497 @code{nnkiboze-directory}, which is @file{~/News/} by default. One
16498 contains the @sc{nov} header lines for all the articles in the group,
16499 and the other is an additional @file{.newsrc} file to store information
16500 on what groups have been searched through to find component articles.
16502 Articles marked as read in the @code{nnkiboze} group will have
16503 their @sc{nov} lines removed from the @sc{nov} file.
16506 @node Gnus Unplugged
16507 @section Gnus Unplugged
16512 @cindex Gnus Unplugged
16514 In olden times (ca. February '88), people used to run their newsreaders
16515 on big machines with permanent connections to the net. News transport
16516 was dealt with by news servers, and all the newsreaders had to do was to
16517 read news. Believe it or not.
16519 Nowadays most people read news and mail at home, and use some sort of
16520 modem to connect to the net. To avoid running up huge phone bills, it
16521 would be nice to have a way to slurp down all the news and mail, hang up
16522 the phone, read for several hours, and then upload any responses you
16523 have to make. And then you repeat the procedure.
16525 Of course, you can use news servers for doing this as well. I've used
16526 @code{inn} together with @code{slurp}, @code{pop} and @code{sendmail}
16527 for some years, but doing that's a bore. Moving the news server
16528 functionality up to the newsreader makes sense if you're the only person
16529 reading news on a machine.
16531 Setting up Gnus as an ``offline'' newsreader is quite simple. In
16532 fact, you don't even have to configure anything.
16534 Of course, to use it as such, you have to learn a few new commands.
16537 * Agent Basics:: How it all is supposed to work.
16538 * Agent Categories:: How to tell the Gnus Agent what to download.
16539 * Agent Commands:: New commands for all the buffers.
16540 * Agent as Cache:: The Agent is a big cache too.
16541 * Agent Expiry:: How to make old articles go away.
16542 * Agent and IMAP:: How to use the Agent with IMAP.
16543 * Outgoing Messages:: What happens when you post/mail something?
16544 * Agent Variables:: Customizing is fun.
16545 * Example Setup:: An example @file{.gnus.el} file for offline people.
16546 * Batching Agents:: How to fetch news from a @code{cron} job.
16547 * Agent Caveats:: What you think it'll do and what it does.
16552 @subsection Agent Basics
16554 First, let's get some terminology out of the way.
16556 The Gnus Agent is said to be @dfn{unplugged} when you have severed the
16557 connection to the net (and notified the Agent that this is the case).
16558 When the connection to the net is up again (and Gnus knows this), the
16559 Agent is @dfn{plugged}.
16561 The @dfn{local} machine is the one you're running on, and which isn't
16562 connected to the net continuously.
16564 @dfn{Downloading} means fetching things from the net to your local
16565 machine. @dfn{Uploading} is doing the opposite.
16567 Let's take a typical Gnus session using the Agent.
16572 You start Gnus with @code{gnus-unplugged}. This brings up the Gnus
16573 Agent in a disconnected state. You can read all the news that you have
16574 already fetched while in this mode.
16577 You then decide to see whether any new news has arrived. You connect
16578 your machine to the net (using PPP or whatever), and then hit @kbd{J j}
16579 to make Gnus become @dfn{plugged} and use @kbd{g} to check for new mail
16580 as usual. To check for new mail in unplugged mode, see (@pxref{Mail
16581 Source Specifiers}).
16584 You can then read the new news immediately, or you can download the news
16585 onto your local machine. If you want to do the latter, you press @kbd{g}
16586 to check if there are any new news and then @kbd{J
16587 s} to fetch all the eligible articles in all the groups. (To let Gnus
16588 know which articles you want to download, @pxref{Agent Categories}.)
16591 After fetching the articles, you press @kbd{J j} to make Gnus become
16592 unplugged again, and you shut down the PPP thing (or whatever). And
16593 then you read the news offline.
16596 And then you go to step 2.
16599 Here are some things you should do the first time (or so) that you use
16605 Decide which servers should be covered by the Agent. If you have a mail
16606 back end, it would probably be nonsensical to have it covered by the
16607 Agent. Go to the server buffer (@kbd{^} in the group buffer) and press
16608 @kbd{J a} on the server (or servers) that you wish to have covered by the
16609 Agent (@pxref{Server Agent Commands}), or @kbd{J r} on automatically
16610 added servers you do not wish to have covered by the Agent. By default,
16611 all @code{nntp} and @code{nnimap} groups in @code{gnus-select-method} and
16612 @code{gnus-secondary-select-methods} are agentized.
16615 Decide on download policy. @xref{Agent Categories}.
16622 @node Agent Categories
16623 @subsection Agent Categories
16625 One of the main reasons to integrate the news transport layer into the
16626 newsreader is to allow greater control over what articles to download.
16627 There's not much point in downloading huge amounts of articles, just to
16628 find out that you're not interested in reading any of them. It's better
16629 to be somewhat more conservative in choosing what to download, and then
16630 mark the articles for downloading manually if it should turn out that
16631 you're interested in the articles anyway.
16633 The main way to control what is to be downloaded is to create a
16634 @dfn{category} and then assign some (or all) groups to this category.
16635 Groups that do not belong in any other category belong to the
16636 @code{default} category. Gnus has its own buffer for creating and
16637 managing categories.
16640 * Category Syntax:: What a category looks like.
16641 * Category Buffer:: A buffer for maintaining categories.
16642 * Category Variables:: Customize'r'Us.
16646 @node Category Syntax
16647 @subsubsection Category Syntax
16649 A category consists of two things.
16653 A predicate which (generally) gives a rough outline of which articles
16654 are eligible for downloading; and
16657 a score rule which (generally) gives you a finer granularity when
16658 deciding what articles to download. (Note that this @dfn{download
16659 score} is not necessarily related to normal scores.)
16662 A predicate in its simplest form can be a single predicate such as
16663 @code{true} or @code{false}. These two will download every available
16664 article or nothing respectively. In the case of these two special
16665 predicates an additional score rule is superfluous.
16667 Predicates of @code{high} or @code{low} download articles in respect of
16668 their scores in relationship to @code{gnus-agent-high-score} and
16669 @code{gnus-agent-low-score} as described below.
16671 To gain even finer control of what is to be regarded eligible for
16672 download a predicate can consist of a number of predicates with logical
16673 operators sprinkled in between.
16675 Perhaps some examples are in order.
16677 Here's a simple predicate. (It's the default predicate, in fact, used
16678 for all groups that don't belong to any other category.)
16684 Quite simple, eh? This predicate is true if and only if the article is
16685 short (for some value of ``short'').
16687 Here's a more complex predicate:
16696 This means that an article should be downloaded if it has a high score,
16697 or if the score is not low and the article is not long. You get the
16700 The available logical operators are @code{or}, @code{and} and
16701 @code{not}. (If you prefer, you can use the more ``C''-ish operators
16702 @samp{|}, @code{&} and @code{!} instead.)
16704 The following predicates are pre-defined, but if none of these fit what
16705 you want to do, you can write your own.
16709 True iff the article is shorter than @code{gnus-agent-short-article}
16710 lines; default 100.
16713 True iff the article is longer than @code{gnus-agent-long-article}
16714 lines; default 200.
16717 True iff the article has a download score less than
16718 @code{gnus-agent-low-score}; default 0.
16721 True iff the article has a download score greater than
16722 @code{gnus-agent-high-score}; default 0.
16725 True iff the Gnus Agent guesses that the article is spam. The
16726 heuristics may change over time, but at present it just computes a
16727 checksum and sees whether articles match.
16736 If you want to create your own predicate function, here's what you have
16737 to know: The functions are called with no parameters, but the
16738 @code{gnus-headers} and @code{gnus-score} dynamic variables are bound to
16741 For example, you could decide that you don't want to download articles
16742 that were posted more than a certain number of days ago (e.g. posted
16743 more than @code{gnus-agent-expire-days} ago) you might write a function
16744 something along the lines of the following:
16747 (defun my-article-old-p ()
16748 "Say whether an article is old."
16749 (< (time-to-days (date-to-time (mail-header-date gnus-headers)))
16750 (- (time-to-days (current-time)) gnus-agent-expire-days)))
16753 with the predicate then defined as:
16756 (not my-article-old-p)
16759 or you could append your predicate to the predefined
16760 @code{gnus-category-predicate-alist} in your @file{~/.gnus.el} or
16764 (require 'gnus-agent)
16765 (setq gnus-category-predicate-alist
16766 (append gnus-category-predicate-alist
16767 '((old . my-article-old-p))))
16770 and simply specify your predicate as:
16776 If/when using something like the above, be aware that there are many
16777 misconfigured systems/mailers out there and so an article's date is not
16778 always a reliable indication of when it was posted. Hell, some people
16779 just don't give a damn.
16781 The above predicates apply to *all* the groups which belong to the
16782 category. However, if you wish to have a specific predicate for an
16783 individual group within a category, or you're just too lazy to set up a
16784 new category, you can enter a group's individual predicate in it's group
16785 parameters like so:
16788 (agent-predicate . short)
16791 This is the group parameter equivalent of the agent category default.
16792 Note that when specifying a single word predicate like this, the
16793 @code{agent-predicate} specification must be in dotted pair notation.
16795 The equivalent of the longer example from above would be:
16798 (agent-predicate or high (and (not low) (not long)))
16801 The outer parenthesis required in the category specification are not
16802 entered here as, not being in dotted pair notation, the value of the
16803 predicate is assumed to be a list.
16806 Now, the syntax of the download score is the same as the syntax of
16807 normal score files, except that all elements that require actually
16808 seeing the article itself are verboten. This means that only the
16809 following headers can be scored on: @code{Subject}, @code{From},
16810 @code{Date}, @code{Message-ID}, @code{References}, @code{Chars},
16811 @code{Lines}, and @code{Xref}.
16813 As with predicates, the specification of the @code{download score rule}
16814 to use in respect of a group can be in either the category definition if
16815 it's to be applicable to all groups in therein, or a group's parameters
16816 if it's to be specific to that group.
16818 In both of these places the @code{download score rule} can take one of
16825 This has the same syntax as a normal gnus score file except only a
16826 subset of scoring keywords are available as mentioned above.
16832 Category specification
16836 ("Lars Ingebrigtsen" 1000000 nil s))
16842 Group Parameter specification
16845 (agent-score ("from"
16846 ("Lars Ingebrigtsen" 1000000 nil s))
16851 Again, note the omission of the outermost parenthesis here.
16857 These score files must *only* contain the permitted scoring keywords
16864 Category specification
16867 ("~/News/agent.SCORE")
16873 ("~/News/agent.SCORE" "~/News/agent.group.SCORE")
16877 Group Parameter specification
16880 (agent-score "~/News/agent.SCORE")
16883 Additional score files can be specified as above. Need I say anything
16888 Use @code{normal} score files
16890 If you don't want to maintain two sets of scoring rules for a group, and
16891 your desired @code{downloading} criteria for a group are the same as your
16892 @code{reading} criteria then you can tell the agent to refer to your
16893 @code{normal} score files when deciding what to download.
16895 These directives in either the category definition or a group's
16896 parameters will cause the agent to read in all the applicable score
16897 files for a group, *filtering out* those sections that do not
16898 relate to one of the permitted subset of scoring keywords.
16902 Category Specification
16909 Group Parameter specification
16912 (agent-score . file)
16917 @node Category Buffer
16918 @subsubsection Category Buffer
16920 You'd normally do all category maintenance from the category buffer.
16921 When you enter it for the first time (with the @kbd{J c} command from
16922 the group buffer), you'll only see the @code{default} category.
16924 The following commands are available in this buffer:
16928 @kindex q (Category)
16929 @findex gnus-category-exit
16930 Return to the group buffer (@code{gnus-category-exit}).
16933 @kindex k (Category)
16934 @findex gnus-category-kill
16935 Kill the current category (@code{gnus-category-kill}).
16938 @kindex c (Category)
16939 @findex gnus-category-copy
16940 Copy the current category (@code{gnus-category-copy}).
16943 @kindex a (Category)
16944 @findex gnus-category-add
16945 Add a new category (@code{gnus-category-add}).
16948 @kindex p (Category)
16949 @findex gnus-category-edit-predicate
16950 Edit the predicate of the current category
16951 (@code{gnus-category-edit-predicate}).
16954 @kindex g (Category)
16955 @findex gnus-category-edit-groups
16956 Edit the list of groups belonging to the current category
16957 (@code{gnus-category-edit-groups}).
16960 @kindex s (Category)
16961 @findex gnus-category-edit-score
16962 Edit the download score rule of the current category
16963 (@code{gnus-category-edit-score}).
16966 @kindex l (Category)
16967 @findex gnus-category-list
16968 List all the categories (@code{gnus-category-list}).
16972 @node Category Variables
16973 @subsubsection Category Variables
16976 @item gnus-category-mode-hook
16977 @vindex gnus-category-mode-hook
16978 Hook run in category buffers.
16980 @item gnus-category-line-format
16981 @vindex gnus-category-line-format
16982 Format of the lines in the category buffer (@pxref{Formatting
16983 Variables}). Valid elements are:
16987 The name of the category.
16990 The number of groups in the category.
16993 @item gnus-category-mode-line-format
16994 @vindex gnus-category-mode-line-format
16995 Format of the category mode line (@pxref{Mode Line Formatting}).
16997 @item gnus-agent-short-article
16998 @vindex gnus-agent-short-article
16999 Articles that have fewer lines than this are short. Default 100.
17001 @item gnus-agent-long-article
17002 @vindex gnus-agent-long-article
17003 Articles that have more lines than this are long. Default 200.
17005 @item gnus-agent-low-score
17006 @vindex gnus-agent-low-score
17007 Articles that have a score lower than this have a low score. Default
17010 @item gnus-agent-high-score
17011 @vindex gnus-agent-high-score
17012 Articles that have a score higher than this have a high score. Default
17018 @node Agent Commands
17019 @subsection Agent Commands
17021 All the Gnus Agent commands are on the @kbd{J} submap. The @kbd{J j}
17022 (@code{gnus-agent-toggle-plugged}) command works in all modes, and
17023 toggles the plugged/unplugged state of the Gnus Agent.
17027 * Group Agent Commands::
17028 * Summary Agent Commands::
17029 * Server Agent Commands::
17035 @node Group Agent Commands
17036 @subsubsection Group Agent Commands
17040 @kindex J u (Agent Group)
17041 @findex gnus-agent-fetch-groups
17042 Fetch all eligible articles in the current group
17043 (@code{gnus-agent-fetch-groups}).
17046 @kindex J c (Agent Group)
17047 @findex gnus-enter-category-buffer
17048 Enter the Agent category buffer (@code{gnus-enter-category-buffer}).
17051 @kindex J s (Agent Group)
17052 @findex gnus-agent-fetch-session
17053 Fetch all eligible articles in all groups
17054 (@code{gnus-agent-fetch-session}).
17057 @kindex J S (Agent Group)
17058 @findex gnus-group-send-queue
17059 Send all sendable messages in the queue group
17060 (@code{gnus-group-send-queue}). @xref{Drafts}.
17063 @kindex J a (Agent Group)
17064 @findex gnus-agent-add-group
17065 Add the current group to an Agent category
17066 (@code{gnus-agent-add-group}). This command understands the
17067 process/prefix convention (@pxref{Process/Prefix}).
17070 @kindex J r (Agent Group)
17071 @findex gnus-agent-remove-group
17072 Remove the current group from its category, if any
17073 (@code{gnus-agent-remove-group}). This command understands the
17074 process/prefix convention (@pxref{Process/Prefix}).
17077 @kindex J Y (Agent Group)
17078 @findex gnus-agent-synchronize-flags
17079 Synchronize flags changed while unplugged with remote server, if any.
17085 @node Summary Agent Commands
17086 @subsubsection Summary Agent Commands
17090 @kindex J # (Agent Summary)
17091 @findex gnus-agent-mark-article
17092 Mark the article for downloading (@code{gnus-agent-mark-article}).
17095 @kindex J M-# (Agent Summary)
17096 @findex gnus-agent-unmark-article
17097 Remove the downloading mark from the article
17098 (@code{gnus-agent-unmark-article}).
17101 @kindex @@ (Agent Summary)
17102 @findex gnus-agent-toggle-mark
17103 Toggle whether to download the article (@code{gnus-agent-toggle-mark}).
17106 @kindex J c (Agent Summary)
17107 @findex gnus-agent-catchup
17108 Mark all undownloaded articles as read (@code{gnus-agent-catchup}).
17111 @kindex J u (Agent Summary)
17112 @findex gnus-agent-summary-fetch-group
17113 Download all downloadable articles in the current group
17114 (@code{gnus-agent-summary-fetch-group}).
17119 @node Server Agent Commands
17120 @subsubsection Server Agent Commands
17124 @kindex J a (Agent Server)
17125 @findex gnus-agent-add-server
17126 Add the current server to the list of servers covered by the Gnus Agent
17127 (@code{gnus-agent-add-server}).
17130 @kindex J r (Agent Server)
17131 @findex gnus-agent-remove-server
17132 Remove the current server from the list of servers covered by the Gnus
17133 Agent (@code{gnus-agent-remove-server}).
17138 @node Agent as Cache
17139 @subsection Agent as Cache
17141 When Gnus is plugged, it is not efficient to download headers or
17142 articles from the server again, if they are already stored in the
17143 Agent. So, Gnus normally only downloads headers once, and stores them
17144 in the Agent. These headers are later used when generating the summary
17145 buffer, regardless of whether you are plugged or unplugged. Articles
17146 are not cached in the Agent by default though (that would potentially
17147 consume lots of disk space), but if you have already downloaded an
17148 article into the Agent, Gnus will not download the article from the
17149 server again but use the locally stored copy instead.
17151 This behaviour can be controlled by @code{gnus-agent-cache}
17152 (@pxref{Agent Variables}).
17155 @subsection Agent Expiry
17157 @vindex gnus-agent-expire-days
17158 @findex gnus-agent-expire
17159 @kindex M-x gnus-agent-expire
17160 @cindex Agent expiry
17161 @cindex Gnus Agent expiry
17164 @code{nnagent} doesn't handle expiry. Instead, there's a special
17165 @code{gnus-agent-expire} command that will expire all read articles that
17166 are older than @code{gnus-agent-expire-days} days. It can be run
17167 whenever you feel that you're running out of space. It's not
17168 particularly fast or efficient, and it's not a particularly good idea to
17169 interrupt it (with @kbd{C-g} or anything else) once you've started it.
17171 @code{gnus-agent-expire-days} can also be a list of regexp/day pairs.
17172 The regexps will be matched against group names to allow differing
17173 expiry in different groups.
17176 (setq gnus-agent-expire-days
17182 If you use the list form, the last element must always be the default
17183 method---it must always match all groups.
17185 @vindex gnus-agent-expire-all
17186 If @code{gnus-agent-expire-all} is non-@code{nil}, this command will
17187 expire all articles---unread, read, ticked and dormant. If @code{nil}
17188 (which is the default), only read articles are eligible for expiry, and
17189 unread, ticked and dormant articles will be kept indefinitely.
17191 @findex gnus-agent-regenerate
17192 If you find that some articles eligible for expiry are never expired,
17193 perhaps some Gnus Agent files are corrupted. There's a special
17194 @code{gnus-agent-regenerate} command to fix possible problems.
17196 @node Agent and IMAP
17197 @subsection Agent and IMAP
17199 The Agent work with any Gnus back end, including nnimap. However,
17200 since there are some conceptual differences between @sc{nntp} and
17201 @sc{imap}, this section (should) provide you with some information to
17202 make Gnus Agent work smoother as a @sc{imap} Disconnected Mode client.
17204 The first thing to keep in mind is that all flags (read, ticked, etc)
17205 are kept on the @sc{imap} server, rather than in @code{.newsrc} as is the
17206 case for nntp. Thus Gnus need to remember flag changes when
17207 disconnected, and synchronize these flags when you plug back in.
17209 Gnus keeps track of flag changes when reading nnimap groups under the
17210 Agent. When you plug back in, Gnus will check if you have any changed
17211 any flags and ask if you wish to synchronize these with the server.
17212 The behavior is customizable by @code{gnus-agent-synchronize-flags}.
17214 @vindex gnus-agent-synchronize-flags
17215 If @code{gnus-agent-synchronize-flags} is @code{nil}, the Agent will
17216 never automatically synchronize flags. If it is @code{ask}, which is
17217 the default, the Agent will check if you made any changes and if so
17218 ask if you wish to synchronize these when you re-connect. If it has
17219 any other value, all flags will be synchronized automatically.
17221 If you do not wish to synchronize flags automatically when you
17222 re-connect, you can do it manually with the
17223 @code{gnus-agent-synchronize-flags} command that is bound to @kbd{J Y}
17224 in the group buffer.
17226 Some things are currently not implemented in the Agent that you'd might
17227 expect from a disconnected @sc{imap} client, including:
17232 Copying/moving articles into nnimap groups when unplugged.
17235 Creating/deleting nnimap groups when unplugged.
17239 Technical note: the synchronization algorithm does not work by "pushing"
17240 all local flags to the server, but rather incrementally update the
17241 server view of flags by changing only those flags that were changed by
17242 the user. Thus, if you set one flag on a article, quit the group and
17243 re-select the group and remove the flag; the flag will be set and
17244 removed from the server when you "synchronize". The queued flag
17245 operations can be found in the per-server @code{flags} file in the Agent
17246 directory. It's emptied when you synchronize flags.
17249 @node Outgoing Messages
17250 @subsection Outgoing Messages
17252 When Gnus is unplugged, all outgoing messages (both mail and news) are
17253 stored in the draft group ``queue'' (@pxref{Drafts}). You can view
17254 them there after posting, and edit them at will.
17256 When Gnus is plugged again, you can send the messages either from the
17257 draft group with the special commands available there, or you can use
17258 the @kbd{J S} command in the group buffer to send all the sendable
17259 messages in the draft group.
17263 @node Agent Variables
17264 @subsection Agent Variables
17267 @item gnus-agent-directory
17268 @vindex gnus-agent-directory
17269 Where the Gnus Agent will store its files. The default is
17270 @file{~/News/agent/}.
17272 @item gnus-agent-handle-level
17273 @vindex gnus-agent-handle-level
17274 Groups on levels (@pxref{Group Levels}) higher than this variable will
17275 be ignored by the Agent. The default is @code{gnus-level-subscribed},
17276 which means that only subscribed group will be considered by the Agent
17279 @item gnus-agent-plugged-hook
17280 @vindex gnus-agent-plugged-hook
17281 Hook run when connecting to the network.
17283 @item gnus-agent-unplugged-hook
17284 @vindex gnus-agent-unplugged-hook
17285 Hook run when disconnecting from the network.
17287 @item gnus-agent-fetched-hook
17288 @vindex gnus-agent-fetched-hook
17289 Hook run when after finishing fetching articles.
17291 @item gnus-agent-cache
17292 @vindex gnus-agent-cache
17293 Variable to control whether use the locally stored @sc{nov} and
17294 articles when plugged, e.g. essentially using the Agent as a cache.
17295 The default is non-nil, which means to use the Agent as a cache.
17297 @item gnus-agent-go-online
17298 @vindex gnus-agent-go-online
17299 If @code{gnus-agent-go-online} is @code{nil}, the Agent will never
17300 automatically switch offline servers into online status. If it is
17301 @code{ask}, the default, the Agent will ask if you wish to switch
17302 offline servers into online status when you re-connect. If it has any
17303 other value, all offline servers will be automatically switched into
17306 @item gnus-server-unopen-status
17307 @vindex gnus-server-unopen-status
17308 Perhaps not a Agent variable, but closely related to the Agent, this
17309 variable says what will happen if Gnus cannot open a server. If the
17310 Agent is enabled, the default, @code{nil}, makes Gnus ask the user
17311 whether to deny the server or whether to unplug the agent. If the
17312 Agent is disabled, Gnus always simply deny the server. Other choices
17313 for this variable include @code{denied} and @code{offline} the latter
17314 is only valid if the Agent is used.
17319 @node Example Setup
17320 @subsection Example Setup
17322 If you don't want to read this manual, and you have a fairly standard
17323 setup, you may be able to use something like the following as your
17324 @file{.gnus.el} file to get started.
17327 ;;; Define how Gnus is to fetch news. We do this over @sc{nntp}
17328 ;;; from your ISP's server.
17329 (setq gnus-select-method '(nntp "news.your-isp.com"))
17331 ;;; Define how Gnus is to read your mail. We read mail from
17332 ;;; your ISP's POP server.
17333 (setq mail-sources '((pop :server "pop.your-isp.com")))
17335 ;;; Say how Gnus is to store the mail. We use nnml groups.
17336 (setq gnus-secondary-select-methods '((nnml "")))
17338 ;;; Make Gnus into an offline newsreader.
17339 ;;; (gnus-agentize) ; The obsolete setting.
17340 ;;; (setq gnus-agent t) ; Now the default.
17343 That should be it, basically. Put that in your @file{~/.gnus.el} file,
17344 edit to suit your needs, start up PPP (or whatever), and type @kbd{M-x
17347 If this is the first time you've run Gnus, you will be subscribed
17348 automatically to a few default newsgroups. You'll probably want to
17349 subscribe to more groups, and to do that, you have to query the
17350 @sc{nntp} server for a complete list of groups with the @kbd{A A}
17351 command. This usually takes quite a while, but you only have to do it
17354 After reading and parsing a while, you'll be presented with a list of
17355 groups. Subscribe to the ones you want to read with the @kbd{u}
17356 command. @kbd{l} to make all the killed groups disappear after you've
17357 subscribe to all the groups you want to read. (@kbd{A k} will bring
17358 back all the killed groups.)
17360 You can now read the groups at once, or you can download the articles
17361 with the @kbd{J s} command. And then read the rest of this manual to
17362 find out which of the other gazillion things you want to customize.
17365 @node Batching Agents
17366 @subsection Batching Agents
17368 Having the Gnus Agent fetch articles (and post whatever messages you've
17369 written) is quite easy once you've gotten things set up properly. The
17370 following shell script will do everything that is necessary:
17372 You can run a complete batch command from the command line with the
17373 following incantation:
17377 emacs -batch -l ~/.emacs -f -l ~/.gnus.el gnus-agent-batch >/dev/null 2>&1
17381 @node Agent Caveats
17382 @subsection Agent Caveats
17384 The Gnus Agent doesn't seem to work like most other offline
17385 newsreaders. Here are some common questions that some imaginary people
17389 @item If I read an article while plugged, do they get entered into the Agent?
17391 @strong{No}. If you want this behaviour, add
17392 @code{gnus-agent-fetch-selected-article} to
17393 @code{gnus-select-article-hook}.
17395 @item If I read an article while plugged, and the article already exists in the Agent, will it get downloaded once more?
17397 @strong{No}, unless @code{gnus-agent-cache} is `nil'.
17401 In short, when Gnus is unplugged, it only looks into the locally stored
17402 articles; when it's plugged, it only talks to your ISP and also uses the
17403 locally stored articles.
17410 Other people use @dfn{kill files}, but we here at Gnus Towers like
17411 scoring better than killing, so we'd rather switch than fight. They do
17412 something completely different as well, so sit up straight and pay
17415 @vindex gnus-summary-mark-below
17416 All articles have a default score (@code{gnus-summary-default-score}),
17417 which is 0 by default. This score may be raised or lowered either
17418 interactively or by score files. Articles that have a score lower than
17419 @code{gnus-summary-mark-below} are marked as read.
17421 Gnus will read any @dfn{score files} that apply to the current group
17422 before generating the summary buffer.
17424 There are several commands in the summary buffer that insert score
17425 entries based on the current article. You can, for instance, ask Gnus to
17426 lower or increase the score of all articles with a certain subject.
17428 There are two sorts of scoring entries: Permanent and temporary.
17429 Temporary score entries are self-expiring entries. Any entries that are
17430 temporary and have not been used for, say, a week, will be removed
17431 silently to help keep the sizes of the score files down.
17434 * Summary Score Commands:: Adding score entries for the current group.
17435 * Group Score Commands:: General score commands.
17436 * Score Variables:: Customize your scoring. (My, what terminology).
17437 * Score File Format:: What a score file may contain.
17438 * Score File Editing:: You can edit score files by hand as well.
17439 * Adaptive Scoring:: Big Sister Gnus knows what you read.
17440 * Home Score File:: How to say where new score entries are to go.
17441 * Followups To Yourself:: Having Gnus notice when people answer you.
17442 * Scoring On Other Headers:: Scoring on non-standard headers.
17443 * Scoring Tips:: How to score effectively.
17444 * Reverse Scoring:: That problem child of old is not problem.
17445 * Global Score Files:: Earth-spanning, ear-splitting score files.
17446 * Kill Files:: They are still here, but they can be ignored.
17447 * Converting Kill Files:: Translating kill files to score files.
17448 * GroupLens:: Getting predictions on what you like to read.
17449 * Advanced Scoring:: Using logical expressions to build score rules.
17450 * Score Decays:: It can be useful to let scores wither away.
17454 @node Summary Score Commands
17455 @section Summary Score Commands
17456 @cindex score commands
17458 The score commands that alter score entries do not actually modify real
17459 score files. That would be too inefficient. Gnus maintains a cache of
17460 previously loaded score files, one of which is considered the
17461 @dfn{current score file alist}. The score commands simply insert
17462 entries into this list, and upon group exit, this list is saved.
17464 The current score file is by default the group's local score file, even
17465 if no such score file actually exists. To insert score commands into
17466 some other score file (e.g. @file{all.SCORE}), you must first make this
17467 score file the current one.
17469 General score commands that don't actually change the score file:
17474 @kindex V s (Summary)
17475 @findex gnus-summary-set-score
17476 Set the score of the current article (@code{gnus-summary-set-score}).
17479 @kindex V S (Summary)
17480 @findex gnus-summary-current-score
17481 Display the score of the current article
17482 (@code{gnus-summary-current-score}).
17485 @kindex V t (Summary)
17486 @findex gnus-score-find-trace
17487 Display all score rules that have been used on the current article
17488 (@code{gnus-score-find-trace}).
17491 @kindex V w (Summary)
17492 @findex gnus-score-find-favourite-words
17493 List words used in scoring (@code{gnus-score-find-favourite-words}).
17496 @kindex V R (Summary)
17497 @findex gnus-summary-rescore
17498 Run the current summary through the scoring process
17499 (@code{gnus-summary-rescore}). This might be useful if you're playing
17500 around with your score files behind Gnus' back and want to see the
17501 effect you're having.
17504 @kindex V c (Summary)
17505 @findex gnus-score-change-score-file
17506 Make a different score file the current
17507 (@code{gnus-score-change-score-file}).
17510 @kindex V e (Summary)
17511 @findex gnus-score-edit-current-scores
17512 Edit the current score file (@code{gnus-score-edit-current-scores}).
17513 You will be popped into a @code{gnus-score-mode} buffer (@pxref{Score
17517 @kindex V f (Summary)
17518 @findex gnus-score-edit-file
17519 Edit a score file and make this score file the current one
17520 (@code{gnus-score-edit-file}).
17523 @kindex V F (Summary)
17524 @findex gnus-score-flush-cache
17525 Flush the score cache (@code{gnus-score-flush-cache}). This is useful
17526 after editing score files.
17529 @kindex V C (Summary)
17530 @findex gnus-score-customize
17531 Customize a score file in a visually pleasing manner
17532 (@code{gnus-score-customize}).
17536 The rest of these commands modify the local score file.
17541 @kindex V m (Summary)
17542 @findex gnus-score-set-mark-below
17543 Prompt for a score, and mark all articles with a score below this as
17544 read (@code{gnus-score-set-mark-below}).
17547 @kindex V x (Summary)
17548 @findex gnus-score-set-expunge-below
17549 Prompt for a score, and add a score rule to the current score file to
17550 expunge all articles below this score
17551 (@code{gnus-score-set-expunge-below}).
17554 The keystrokes for actually making score entries follow a very regular
17555 pattern, so there's no need to list all the commands. (Hundreds of
17558 @findex gnus-summary-increase-score
17559 @findex gnus-summary-lower-score
17563 The first key is either @kbd{I} (upper case i) for increasing the score
17564 or @kbd{L} for lowering the score.
17566 The second key says what header you want to score on. The following
17567 keys are available:
17571 Score on the author name.
17574 Score on the subject line.
17577 Score on the @code{Xref} line---i.e., the cross-posting line.
17580 Score on the @code{References} line.
17586 Score on the number of lines.
17589 Score on the @code{Message-ID} header.
17592 Score on an "extra" header, that is, one of those in gnus-extra-headers,
17593 if your @sc{nntp} server tracks additional header data in overviews.
17596 Score on followups---this matches the author name, and adds scores to
17597 the followups to this author. (Using this key leads to the creation of
17598 @file{ADAPT} files.)
17607 Score on thread. (Using this key leads to the creation of @file{ADAPT}
17613 The third key is the match type. Which match types are valid depends on
17614 what headers you are scoring on.
17626 Substring matching.
17629 Fuzzy matching (@pxref{Fuzzy Matching}).
17658 Greater than number.
17663 The fourth and usually final key says whether this is a temporary (i.e.,
17664 expiring) score entry, or a permanent (i.e., non-expiring) score entry,
17665 or whether it is to be done immediately, without adding to the score
17670 Temporary score entry.
17673 Permanent score entry.
17676 Immediately scoring.
17680 If you are scoring on `e' (extra) headers, you will then be prompted for
17681 the header name on which you wish to score. This must be a header named
17682 in gnus-extra-headers, and @samp{TAB} completion is available.
17686 So, let's say you want to increase the score on the current author with
17687 exact matching permanently: @kbd{I a e p}. If you want to lower the
17688 score based on the subject line, using substring matching, and make a
17689 temporary score entry: @kbd{L s s t}. Pretty easy.
17691 To make things a bit more complicated, there are shortcuts. If you use
17692 a capital letter on either the second or third keys, Gnus will use
17693 defaults for the remaining one or two keystrokes. The defaults are
17694 ``substring'' and ``temporary''. So @kbd{I A} is the same as @kbd{I a s
17695 t}, and @kbd{I a R} is the same as @kbd{I a r t}.
17697 These functions take both the numerical prefix and the symbolic prefix
17698 (@pxref{Symbolic Prefixes}). A numerical prefix says how much to lower
17699 (or increase) the score of the article. A symbolic prefix of @code{a}
17700 says to use the @file{all.SCORE} file for the command instead of the
17701 current score file.
17703 @vindex gnus-score-mimic-keymap
17704 The @code{gnus-score-mimic-keymap} says whether these commands will
17705 pretend they are keymaps or not.
17708 @node Group Score Commands
17709 @section Group Score Commands
17710 @cindex group score commands
17712 There aren't many of these as yet, I'm afraid.
17717 @kindex W f (Group)
17718 @findex gnus-score-flush-cache
17719 Gnus maintains a cache of score alists to avoid having to reload them
17720 all the time. This command will flush the cache
17721 (@code{gnus-score-flush-cache}).
17725 You can do scoring from the command line by saying something like:
17727 @findex gnus-batch-score
17728 @cindex batch scoring
17730 $ emacs -batch -l ~/.emacs -l ~/.gnus.el -f gnus-batch-score
17734 @node Score Variables
17735 @section Score Variables
17736 @cindex score variables
17740 @item gnus-use-scoring
17741 @vindex gnus-use-scoring
17742 If @code{nil}, Gnus will not check for score files, and will not, in
17743 general, do any score-related work. This is @code{t} by default.
17745 @item gnus-kill-killed
17746 @vindex gnus-kill-killed
17747 If this variable is @code{nil}, Gnus will never apply score files to
17748 articles that have already been through the kill process. While this
17749 may save you lots of time, it also means that if you apply a kill file
17750 to a group, and then change the kill file and want to run it over you
17751 group again to kill more articles, it won't work. You have to set this
17752 variable to @code{t} to do that. (It is @code{t} by default.)
17754 @item gnus-kill-files-directory
17755 @vindex gnus-kill-files-directory
17756 All kill and score files will be stored in this directory, which is
17757 initialized from the @code{SAVEDIR} environment variable by default.
17758 This is @file{~/News/} by default.
17760 @item gnus-score-file-suffix
17761 @vindex gnus-score-file-suffix
17762 Suffix to add to the group name to arrive at the score file name
17763 (@samp{SCORE} by default.)
17765 @item gnus-score-uncacheable-files
17766 @vindex gnus-score-uncacheable-files
17767 @cindex score cache
17768 All score files are normally cached to avoid excessive re-loading of
17769 score files. However, if this might make your Emacs grow big and
17770 bloated, so this regexp can be used to weed out score files unlikely to be needed again. It would be a bad idea to deny caching of
17771 @file{all.SCORE}, while it might be a good idea to not cache
17772 @file{comp.infosystems.www.authoring.misc.ADAPT}. In fact, this
17773 variable is @samp{ADAPT$} by default, so no adaptive score files will
17776 @item gnus-save-score
17777 @vindex gnus-save-score
17778 If you have really complicated score files, and do lots of batch
17779 scoring, then you might set this variable to @code{t}. This will make
17780 Gnus save the scores into the @file{.newsrc.eld} file.
17782 If you do not set this to @code{t}, then manual scores (like those set
17783 with @kbd{V s} (@code{gnus-summary-set-score})) will not be preserved
17784 across group visits.
17786 @item gnus-score-interactive-default-score
17787 @vindex gnus-score-interactive-default-score
17788 Score used by all the interactive raise/lower commands to raise/lower
17789 score with. Default is 1000, which may seem excessive, but this is to
17790 ensure that the adaptive scoring scheme gets enough room to play with.
17791 We don't want the small changes from the adaptive scoring to overwrite
17792 manually entered data.
17794 @item gnus-summary-default-score
17795 @vindex gnus-summary-default-score
17796 Default score of an article, which is 0 by default.
17798 @item gnus-summary-expunge-below
17799 @vindex gnus-summary-expunge-below
17800 Don't display the summary lines of articles that have scores lower than
17801 this variable. This is @code{nil} by default, which means that no
17802 articles will be hidden. This variable is local to the summary buffers,
17803 and has to be set from @code{gnus-summary-mode-hook}.
17805 @item gnus-score-over-mark
17806 @vindex gnus-score-over-mark
17807 Mark (in the third column) used for articles with a score over the
17808 default. Default is @samp{+}.
17810 @item gnus-score-below-mark
17811 @vindex gnus-score-below-mark
17812 Mark (in the third column) used for articles with a score below the
17813 default. Default is @samp{-}.
17815 @item gnus-score-find-score-files-function
17816 @vindex gnus-score-find-score-files-function
17817 Function used to find score files for the current group. This function
17818 is called with the name of the group as the argument.
17820 Predefined functions available are:
17823 @item gnus-score-find-single
17824 @findex gnus-score-find-single
17825 Only apply the group's own score file.
17827 @item gnus-score-find-bnews
17828 @findex gnus-score-find-bnews
17829 Apply all score files that match, using bnews syntax. This is the
17830 default. If the current group is @samp{gnu.emacs.gnus}, for instance,
17831 @file{all.emacs.all.SCORE}, @file{not.alt.all.SCORE} and
17832 @file{gnu.all.SCORE} would all apply. In short, the instances of
17833 @samp{all} in the score file names are translated into @samp{.*}, and
17834 then a regexp match is done.
17836 This means that if you have some score entries that you want to apply to
17837 all groups, then you put those entries in the @file{all.SCORE} file.
17839 The score files are applied in a semi-random order, although Gnus will
17840 try to apply the more general score files before the more specific score
17841 files. It does this by looking at the number of elements in the score
17842 file names---discarding the @samp{all} elements.
17844 @item gnus-score-find-hierarchical
17845 @findex gnus-score-find-hierarchical
17846 Apply all score files from all the parent groups. This means that you
17847 can't have score files like @file{all.SCORE}, but you can have
17848 @file{SCORE}, @file{comp.SCORE} and @file{comp.emacs.SCORE} for each
17852 This variable can also be a list of functions. In that case, all
17853 these functions will be called with the group name as argument, and
17854 all the returned lists of score files will be applied. These
17855 functions can also return lists of lists of score alists directly. In
17856 that case, the functions that return these non-file score alists
17857 should probably be placed before the ``real'' score file functions, to
17858 ensure that the last score file returned is the local score file.
17861 For example, to do hierarchical scoring but use a non-server-specific
17862 overall score file, you could use the value
17864 (list (lambda (group) ("all.SCORE"))
17865 'gnus-score-find-hierarchical)
17868 @item gnus-score-expiry-days
17869 @vindex gnus-score-expiry-days
17870 This variable says how many days should pass before an unused score file
17871 entry is expired. If this variable is @code{nil}, no score file entries
17872 are expired. It's 7 by default.
17874 @item gnus-update-score-entry-dates
17875 @vindex gnus-update-score-entry-dates
17876 If this variable is non-@code{nil}, temporary score entries that have
17877 been triggered (matched) will have their dates updated. (This is how Gnus
17878 controls expiry---all non-matched-entries will become too old while
17879 matched entries will stay fresh and young.) However, if you set this
17880 variable to @code{nil}, even matched entries will grow old and will
17881 have to face that oh-so grim reaper.
17883 @item gnus-score-after-write-file-function
17884 @vindex gnus-score-after-write-file-function
17885 Function called with the name of the score file just written.
17887 @item gnus-score-thread-simplify
17888 @vindex gnus-score-thread-simplify
17889 If this variable is non-@code{nil}, article subjects will be simplified
17890 for subject scoring purposes in the same manner as with
17891 threading---according to the current value of
17892 gnus-simplify-subject-functions. If the scoring entry uses
17893 @code{substring} or @code{exact} matching, the match will also be
17894 simplified in this manner.
17899 @node Score File Format
17900 @section Score File Format
17901 @cindex score file format
17903 A score file is an @code{emacs-lisp} file that normally contains just a
17904 single form. Casual users are not expected to edit these files;
17905 everything can be changed from the summary buffer.
17907 Anyway, if you'd like to dig into it yourself, here's an example:
17911 ("Lars Ingebrigtsen" -10000)
17913 ("larsi\\|lmi" -50000 nil R))
17915 ("Ding is Badd" nil 728373))
17917 ("alt.politics" -1000 728372 s))
17922 (mark-and-expunge -10)
17926 (files "/hom/larsi/News/gnu.SCORE")
17927 (exclude-files "all.SCORE")
17928 (local (gnus-newsgroup-auto-expire t)
17929 (gnus-summary-make-false-root empty))
17933 This example demonstrates most score file elements. For a different
17934 approach, see @pxref{Advanced Scoring}.
17936 Even though this looks much like lisp code, nothing here is actually
17937 @code{eval}ed. The lisp reader is used to read this form, though, so it
17938 has to be valid syntactically, if not semantically.
17940 Six keys are supported by this alist:
17945 If the key is a string, it is the name of the header to perform the
17946 match on. Scoring can only be performed on these eight headers:
17947 @code{From}, @code{Subject}, @code{References}, @code{Message-ID},
17948 @code{Xref}, @code{Lines}, @code{Chars} and @code{Date}. In addition to
17949 these headers, there are three strings to tell Gnus to fetch the entire
17950 article and do the match on larger parts of the article: @code{Body}
17951 will perform the match on the body of the article, @code{Head} will
17952 perform the match on the head of the article, and @code{All} will
17953 perform the match on the entire article. Note that using any of these
17954 last three keys will slow down group entry @emph{considerably}. The
17955 final ``header'' you can score on is @code{Followup}. These score
17956 entries will result in new score entries being added for all follow-ups
17957 to articles that matches these score entries.
17959 Following this key is a arbitrary number of score entries, where each
17960 score entry has one to four elements.
17964 The first element is the @dfn{match element}. On most headers this will
17965 be a string, but on the Lines and Chars headers, this must be an
17969 If the second element is present, it should be a number---the @dfn{score
17970 element}. This number should be an integer in the neginf to posinf
17971 interval. This number is added to the score of the article if the match
17972 is successful. If this element is not present, the
17973 @code{gnus-score-interactive-default-score} number will be used
17974 instead. This is 1000 by default.
17977 If the third element is present, it should be a number---the @dfn{date
17978 element}. This date says when the last time this score entry matched,
17979 which provides a mechanism for expiring the score entries. It this
17980 element is not present, the score entry is permanent. The date is
17981 represented by the number of days since December 31, 1 BCE.
17984 If the fourth element is present, it should be a symbol---the @dfn{type
17985 element}. This element specifies what function should be used to see
17986 whether this score entry matches the article. What match types that can
17987 be used depends on what header you wish to perform the match on.
17990 @item From, Subject, References, Xref, Message-ID
17991 For most header types, there are the @code{r} and @code{R} (regexp), as
17992 well as @code{s} and @code{S} (substring) types, and @code{e} and
17993 @code{E} (exact match), and @code{w} (word match) types. If this
17994 element is not present, Gnus will assume that substring matching should
17995 be used. @code{R}, @code{S}, and @code{E} differ from the others in
17996 that the matches will be done in a case-sensitive manner. All these
17997 one-letter types are really just abbreviations for the @code{regexp},
17998 @code{string}, @code{exact}, and @code{word} types, which you can use
17999 instead, if you feel like.
18002 Just as for the standard string overview headers, if you are using
18003 gnus-extra-headers, you can score on these headers' values. In this
18004 case, there is a 5th element in the score entry, being the name of the
18005 header to be scored. The following entry is useful in your
18006 @file{all.SCORE} file in case of spam attacks from a single origin host,
18007 if your @sc{nntp} server tracks NNTP-Posting-Host in overviews:
18010 ("111.222.333.444" -1000 nil s "NNTP-Posting-Host")
18014 These two headers use different match types: @code{<}, @code{>},
18015 @code{=}, @code{>=} and @code{<=}.
18017 These predicates are true if
18020 (PREDICATE HEADER MATCH)
18023 evaluates to non-@code{nil}. For instance, the advanced match
18024 @code{("lines" 4 <)} (@pxref{Advanced Scoring}) will result in the
18031 Or to put it another way: When using @code{<} on @code{Lines} with 4 as
18032 the match, we get the score added if the article has less than 4 lines.
18033 (It's easy to get confused and think it's the other way around. But
18034 it's not. I think.)
18036 When matching on @code{Lines}, be careful because some back ends (like
18037 @code{nndir}) do not generate @code{Lines} header, so every article ends
18038 up being marked as having 0 lines. This can lead to strange results if
18039 you happen to lower score of the articles with few lines.
18042 For the Date header we have three kinda silly match types:
18043 @code{before}, @code{at} and @code{after}. I can't really imagine this
18044 ever being useful, but, like, it would feel kinda silly not to provide
18045 this function. Just in case. You never know. Better safe than sorry.
18046 Once burnt, twice shy. Don't judge a book by its cover. Never not have
18047 sex on a first date. (I have been told that at least one person, and I
18048 quote, ``found this function indispensable'', however.)
18052 A more useful match type is @code{regexp}. With it, you can match the
18053 date string using a regular expression. The date is normalized to
18054 ISO8601 compact format first---@var{YYYYMMDD}@code{T}@var{HHMMSS}. If
18055 you want to match all articles that have been posted on April 1st in
18056 every year, you could use @samp{....0401.........} as a match string,
18057 for instance. (Note that the date is kept in its original time zone, so
18058 this will match articles that were posted when it was April 1st where
18059 the article was posted from. Time zones are such wholesome fun for the
18062 @item Head, Body, All
18063 These three match keys use the same match types as the @code{From} (etc)
18067 This match key is somewhat special, in that it will match the
18068 @code{From} header, and affect the score of not only the matching
18069 articles, but also all followups to the matching articles. This allows
18070 you e.g. increase the score of followups to your own articles, or
18071 decrease the score of followups to the articles of some known
18072 trouble-maker. Uses the same match types as the @code{From} header
18073 uses. (Using this match key will lead to creation of @file{ADAPT}
18077 This match key works along the same lines as the @code{Followup} match
18078 key. If you say that you want to score on a (sub-)thread started by an
18079 article with a @code{Message-ID} @var{x}, then you add a @samp{thread}
18080 match. This will add a new @samp{thread} match for each article that
18081 has @var{x} in its @code{References} header. (These new @samp{thread}
18082 matches will use the @code{Message-ID}s of these matching articles.)
18083 This will ensure that you can raise/lower the score of an entire thread,
18084 even though some articles in the thread may not have complete
18085 @code{References} headers. Note that using this may lead to
18086 undeterministic scores of the articles in the thread. (Using this match
18087 key will lead to creation of @file{ADAPT} files.)
18091 @cindex Score File Atoms
18093 The value of this entry should be a number. Any articles with a score
18094 lower than this number will be marked as read.
18097 The value of this entry should be a number. Any articles with a score
18098 lower than this number will be removed from the summary buffer.
18100 @item mark-and-expunge
18101 The value of this entry should be a number. Any articles with a score
18102 lower than this number will be marked as read and removed from the
18105 @item thread-mark-and-expunge
18106 The value of this entry should be a number. All articles that belong to
18107 a thread that has a total score below this number will be marked as read
18108 and removed from the summary buffer. @code{gnus-thread-score-function}
18109 says how to compute the total score for a thread.
18112 The value of this entry should be any number of file names. These files
18113 are assumed to be score files as well, and will be loaded the same way
18116 @item exclude-files
18117 The clue of this entry should be any number of files. These files will
18118 not be loaded, even though they would normally be so, for some reason or
18122 The value of this entry will be @code{eval}el. This element will be
18123 ignored when handling global score files.
18126 Read-only score files will not be updated or saved. Global score files
18127 should feature this atom (@pxref{Global Score Files}). (Note:
18128 @dfn{Global} here really means @dfn{global}; not your personal
18129 apply-to-all-groups score files.)
18132 The value of this entry should be a number. Articles that do not have
18133 parents will get this number added to their scores. Imagine you follow
18134 some high-volume newsgroup, like @samp{comp.lang.c}. Most likely you
18135 will only follow a few of the threads, also want to see any new threads.
18137 You can do this with the following two score file entries:
18141 (mark-and-expunge -100)
18144 When you enter the group the first time, you will only see the new
18145 threads. You then raise the score of the threads that you find
18146 interesting (with @kbd{I T} or @kbd{I S}), and ignore (@kbd{C y}) the
18147 rest. Next time you enter the group, you will see new articles in the
18148 interesting threads, plus any new threads.
18150 I.e.---the orphan score atom is for high-volume groups where a few
18151 interesting threads which can't be found automatically by ordinary
18152 scoring rules exist.
18155 This entry controls the adaptive scoring. If it is @code{t}, the
18156 default adaptive scoring rules will be used. If it is @code{ignore}, no
18157 adaptive scoring will be performed on this group. If it is a list, this
18158 list will be used as the adaptive scoring rules. If it isn't present,
18159 or is something other than @code{t} or @code{ignore}, the default
18160 adaptive scoring rules will be used. If you want to use adaptive
18161 scoring on most groups, you'd set @code{gnus-use-adaptive-scoring} to
18162 @code{t}, and insert an @code{(adapt ignore)} in the groups where you do
18163 not want adaptive scoring. If you only want adaptive scoring in a few
18164 groups, you'd set @code{gnus-use-adaptive-scoring} to @code{nil}, and
18165 insert @code{(adapt t)} in the score files of the groups where you want
18169 All adaptive score entries will go to the file named by this entry. It
18170 will also be applied when entering the group. This atom might be handy
18171 if you want to adapt on several groups at once, using the same adaptive
18172 file for a number of groups.
18175 @cindex local variables
18176 The value of this entry should be a list of @code{(VAR VALUE)} pairs.
18177 Each @var{var} will be made buffer-local to the current summary buffer,
18178 and set to the value specified. This is a convenient, if somewhat
18179 strange, way of setting variables in some groups if you don't like hooks
18180 much. Note that the @var{value} won't be evaluated.
18184 @node Score File Editing
18185 @section Score File Editing
18187 You normally enter all scoring commands from the summary buffer, but you
18188 might feel the urge to edit them by hand as well, so we've supplied you
18189 with a mode for that.
18191 It's simply a slightly customized @code{emacs-lisp} mode, with these
18192 additional commands:
18197 @kindex C-c C-c (Score)
18198 @findex gnus-score-edit-done
18199 Save the changes you have made and return to the summary buffer
18200 (@code{gnus-score-edit-done}).
18203 @kindex C-c C-d (Score)
18204 @findex gnus-score-edit-insert-date
18205 Insert the current date in numerical format
18206 (@code{gnus-score-edit-insert-date}). This is really the day number, if
18207 you were wondering.
18210 @kindex C-c C-p (Score)
18211 @findex gnus-score-pretty-print
18212 The adaptive score files are saved in an unformatted fashion. If you
18213 intend to read one of these files, you want to @dfn{pretty print} it
18214 first. This command (@code{gnus-score-pretty-print}) does that for
18219 Type @kbd{M-x gnus-score-mode} to use this mode.
18221 @vindex gnus-score-mode-hook
18222 @code{gnus-score-menu-hook} is run in score mode buffers.
18224 In the summary buffer you can use commands like @kbd{V f} and @kbd{V
18225 e} to begin editing score files.
18228 @node Adaptive Scoring
18229 @section Adaptive Scoring
18230 @cindex adaptive scoring
18232 If all this scoring is getting you down, Gnus has a way of making it all
18233 happen automatically---as if by magic. Or rather, as if by artificial
18234 stupidity, to be precise.
18236 @vindex gnus-use-adaptive-scoring
18237 When you read an article, or mark an article as read, or kill an
18238 article, you leave marks behind. On exit from the group, Gnus can sniff
18239 these marks and add score elements depending on what marks it finds.
18240 You turn on this ability by setting @code{gnus-use-adaptive-scoring} to
18241 @code{t} or @code{(line)}. If you want score adaptively on separate
18242 words appearing in the subjects, you should set this variable to
18243 @code{(word)}. If you want to use both adaptive methods, set this
18244 variable to @code{(word line)}.
18246 @vindex gnus-default-adaptive-score-alist
18247 To give you complete control over the scoring process, you can customize
18248 the @code{gnus-default-adaptive-score-alist} variable. For instance, it
18249 might look something like this:
18252 (setq gnus-default-adaptive-score-alist
18253 '((gnus-unread-mark)
18254 (gnus-ticked-mark (from 4))
18255 (gnus-dormant-mark (from 5))
18256 (gnus-del-mark (from -4) (subject -1))
18257 (gnus-read-mark (from 4) (subject 2))
18258 (gnus-expirable-mark (from -1) (subject -1))
18259 (gnus-killed-mark (from -1) (subject -3))
18260 (gnus-kill-file-mark)
18261 (gnus-ancient-mark)
18262 (gnus-low-score-mark)
18263 (gnus-catchup-mark (from -1) (subject -1))))
18266 As you see, each element in this alist has a mark as a key (either a
18267 variable name or a ``real'' mark---a character). Following this key is
18268 a arbitrary number of header/score pairs. If there are no header/score
18269 pairs following the key, no adaptive scoring will be done on articles
18270 that have that key as the article mark. For instance, articles with
18271 @code{gnus-unread-mark} in the example above will not get adaptive score
18274 Each article can have only one mark, so just a single of these rules
18275 will be applied to each article.
18277 To take @code{gnus-del-mark} as an example---this alist says that all
18278 articles that have that mark (i.e., are marked with @samp{D}) will have a
18279 score entry added to lower based on the @code{From} header by -4, and
18280 lowered by @code{Subject} by -1. Change this to fit your prejudices.
18282 If you have marked 10 articles with the same subject with
18283 @code{gnus-del-mark}, the rule for that mark will be applied ten times.
18284 That means that that subject will get a score of ten times -1, which
18285 should be, unless I'm much mistaken, -10.
18287 If you have auto-expirable (mail) groups (@pxref{Expiring Mail}), all
18288 the read articles will be marked with the @samp{E} mark. This'll
18289 probably make adaptive scoring slightly impossible, so auto-expiring and
18290 adaptive scoring doesn't really mix very well.
18292 The headers you can score on are @code{from}, @code{subject},
18293 @code{message-id}, @code{references}, @code{xref}, @code{lines},
18294 @code{chars} and @code{date}. In addition, you can score on
18295 @code{followup}, which will create an adaptive score entry that matches
18296 on the @code{References} header using the @code{Message-ID} of the
18297 current article, thereby matching the following thread.
18299 You can also score on @code{thread}, which will try to score all
18300 articles that appear in a thread. @code{thread} matches uses a
18301 @code{Message-ID} to match on the @code{References} header of the
18302 article. If the match is made, the @code{Message-ID} of the article is
18303 added to the @code{thread} rule. (Think about it. I'd recommend two
18304 aspirins afterwards.)
18306 If you use this scheme, you should set the score file atom @code{mark}
18307 to something small---like -300, perhaps, to avoid having small random
18308 changes result in articles getting marked as read.
18310 After using adaptive scoring for a week or so, Gnus should start to
18311 become properly trained and enhance the authors you like best, and kill
18312 the authors you like least, without you having to say so explicitly.
18314 You can control what groups the adaptive scoring is to be performed on
18315 by using the score files (@pxref{Score File Format}). This will also
18316 let you use different rules in different groups.
18318 @vindex gnus-adaptive-file-suffix
18319 The adaptive score entries will be put into a file where the name is the
18320 group name with @code{gnus-adaptive-file-suffix} appended. The default
18323 @vindex gnus-score-exact-adapt-limit
18324 When doing adaptive scoring, substring or fuzzy matching would probably
18325 give you the best results in most cases. However, if the header one
18326 matches is short, the possibility for false positives is great, so if
18327 the length of the match is less than
18328 @code{gnus-score-exact-adapt-limit}, exact matching will be used. If
18329 this variable is @code{nil}, exact matching will always be used to avoid
18332 @vindex gnus-default-adaptive-word-score-alist
18333 As mentioned above, you can adapt either on individual words or entire
18334 headers. If you adapt on words, the
18335 @code{gnus-default-adaptive-word-score-alist} variable says what score
18336 each instance of a word should add given a mark.
18339 (setq gnus-default-adaptive-word-score-alist
18340 `((,gnus-read-mark . 30)
18341 (,gnus-catchup-mark . -10)
18342 (,gnus-killed-mark . -20)
18343 (,gnus-del-mark . -15)))
18346 This is the default value. If you have adaption on words enabled, every
18347 word that appears in subjects of articles marked with
18348 @code{gnus-read-mark} will result in a score rule that increase the
18349 score with 30 points.
18351 @vindex gnus-default-ignored-adaptive-words
18352 @vindex gnus-ignored-adaptive-words
18353 Words that appear in the @code{gnus-default-ignored-adaptive-words} list
18354 will be ignored. If you wish to add more words to be ignored, use the
18355 @code{gnus-ignored-adaptive-words} list instead.
18357 @vindex gnus-adaptive-word-length-limit
18358 Some may feel that short words shouldn't count when doing adaptive
18359 scoring. If so, you may set @code{gnus-adaptive-word-length-limit} to
18360 an integer. Words shorter than this number will be ignored. This
18361 variable defaults to @code{nil}.
18363 @vindex gnus-adaptive-word-syntax-table
18364 When the scoring is done, @code{gnus-adaptive-word-syntax-table} is the
18365 syntax table in effect. It is similar to the standard syntax table, but
18366 it considers numbers to be non-word-constituent characters.
18368 @vindex gnus-adaptive-word-minimum
18369 If @code{gnus-adaptive-word-minimum} is set to a number, the adaptive
18370 word scoring process will never bring down the score of an article to
18371 below this number. The default is @code{nil}.
18373 @vindex gnus-adaptive-word-no-group-words
18374 If @code{gnus-adaptive-word-no-group-words} is set to @code{t}, gnus
18375 won't adaptively word score any of the words in the group name. Useful
18376 for groups like @samp{comp.editors.emacs}, where most of the subject
18377 lines contain the word @samp{emacs}.
18379 After using this scheme for a while, it might be nice to write a
18380 @code{gnus-psychoanalyze-user} command to go through the rules and see
18381 what words you like and what words you don't like. Or perhaps not.
18383 Note that the adaptive word scoring thing is highly experimental and is
18384 likely to change in the future. Initial impressions seem to indicate
18385 that it's totally useless as it stands. Some more work (involving more
18386 rigorous statistical methods) will have to be done to make this useful.
18389 @node Home Score File
18390 @section Home Score File
18392 The score file where new score file entries will go is called the
18393 @dfn{home score file}. This is normally (and by default) the score file
18394 for the group itself. For instance, the home score file for
18395 @samp{gnu.emacs.gnus} is @file{gnu.emacs.gnus.SCORE}.
18397 However, this may not be what you want. It is often convenient to share
18398 a common home score file among many groups---all @samp{emacs} groups
18399 could perhaps use the same home score file.
18401 @vindex gnus-home-score-file
18402 The variable that controls this is @code{gnus-home-score-file}. It can
18407 A string. Then this file will be used as the home score file for all
18411 A function. The result of this function will be used as the home score
18412 file. The function will be called with the name of the group as the
18416 A list. The elements in this list can be:
18420 @code{(@var{regexp} @var{file-name})}. If the @var{regexp} matches the
18421 group name, the @var{file-name} will be used as the home score file.
18424 A function. If the function returns non-nil, the result will be used as
18425 the home score file.
18428 A string. Use the string as the home score file.
18431 The list will be traversed from the beginning towards the end looking
18436 So, if you want to use just a single score file, you could say:
18439 (setq gnus-home-score-file
18440 "my-total-score-file.SCORE")
18443 If you want to use @file{gnu.SCORE} for all @samp{gnu} groups and
18444 @file{rec.SCORE} for all @samp{rec} groups (and so on), you can say:
18446 @findex gnus-hierarchial-home-score-file
18448 (setq gnus-home-score-file
18449 'gnus-hierarchial-home-score-file)
18452 This is a ready-made function provided for your convenience.
18453 Other functions include
18456 @item gnus-current-home-score-file
18457 @findex gnus-current-home-score-file
18458 Return the ``current'' regular score file. This will make scoring
18459 commands add entry to the ``innermost'' matching score file.
18463 If you want to have one score file for the @samp{emacs} groups and
18464 another for the @samp{comp} groups, while letting all other groups use
18465 their own home score files:
18468 (setq gnus-home-score-file
18469 ;; All groups that match the regexp "\\.emacs"
18470 '(("\\.emacs" "emacs.SCORE")
18471 ;; All the comp groups in one score file
18472 ("^comp" "comp.SCORE")))
18475 @vindex gnus-home-adapt-file
18476 @code{gnus-home-adapt-file} works exactly the same way as
18477 @code{gnus-home-score-file}, but says what the home adaptive score file
18478 is instead. All new adaptive file entries will go into the file
18479 specified by this variable, and the same syntax is allowed.
18481 In addition to using @code{gnus-home-score-file} and
18482 @code{gnus-home-adapt-file}, you can also use group parameters
18483 (@pxref{Group Parameters}) and topic parameters (@pxref{Topic
18484 Parameters}) to achieve much the same. Group and topic parameters take
18485 precedence over this variable.
18488 @node Followups To Yourself
18489 @section Followups To Yourself
18491 Gnus offers two commands for picking out the @code{Message-ID} header in
18492 the current buffer. Gnus will then add a score rule that scores using
18493 this @code{Message-ID} on the @code{References} header of other
18494 articles. This will, in effect, increase the score of all articles that
18495 respond to the article in the current buffer. Quite useful if you want
18496 to easily note when people answer what you've said.
18500 @item gnus-score-followup-article
18501 @findex gnus-score-followup-article
18502 This will add a score to articles that directly follow up your own
18505 @item gnus-score-followup-thread
18506 @findex gnus-score-followup-thread
18507 This will add a score to all articles that appear in a thread ``below''
18511 @vindex message-sent-hook
18512 These two functions are both primarily meant to be used in hooks like
18513 @code{message-sent-hook}, like this:
18515 (add-hook 'message-sent-hook 'gnus-score-followup-thread)
18519 If you look closely at your own @code{Message-ID}, you'll notice that
18520 the first two or three characters are always the same. Here's two of
18524 <x6u3u47icf.fsf@@eyesore.no>
18525 <x6sp9o7ibw.fsf@@eyesore.no>
18528 So ``my'' ident on this machine is @samp{x6}. This can be
18529 exploited---the following rule will raise the score on all followups to
18534 ("<x6[0-9a-z]+\\.fsf\\(_-_\\)?@@.*eyesore\\.no>"
18538 Whether it's the first two or first three characters that are ``yours''
18539 is system-dependent.
18542 @node Scoring On Other Headers
18543 @section Scoring On Other Headers
18544 @cindex scoring on other headers
18546 Gnus is quite fast when scoring the ``traditional''
18547 headers---@samp{From}, @samp{Subject} and so on. However, scoring
18548 other headers requires writing a @code{head} scoring rule, which means
18549 that Gnus has to request every single article from the back end to find
18550 matches. This takes a long time in big groups.
18552 Now, there's not much you can do about this for news groups, but for
18553 mail groups, you have greater control. In the @pxref{To From
18554 Newsgroups} section of the manual, it's explained in greater detail what
18555 this mechanism does, but here's a cookbook example for @code{nnml} on
18556 how to allow scoring on the @samp{To} and @samp{Cc} headers.
18558 Put the following in your @file{.gnus.el} file.
18561 (setq gnus-extra-headers '(To Cc Newsgroups Keywords)
18562 nnmail-extra-headers gnus-extra-headers)
18565 Restart Gnus and rebuild your @code{nnml} overview files with the
18566 @kbd{M-x nnml-generate-nov-databases} command. This will take a long
18567 time if you have much mail.
18569 Now you can score on @samp{To} and @samp{Cc} as ``extra headers'' like
18570 so: @kbd{I e s p To RET <your name> RET}.
18576 @section Scoring Tips
18577 @cindex scoring tips
18583 @cindex scoring crossposts
18584 If you want to lower the score of crossposts, the line to match on is
18585 the @code{Xref} header.
18587 ("xref" (" talk.politics.misc:" -1000))
18590 @item Multiple crossposts
18591 If you want to lower the score of articles that have been crossposted to
18592 more than, say, 3 groups:
18595 ("[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+"
18599 @item Matching on the body
18600 This is generally not a very good idea---it takes a very long time.
18601 Gnus actually has to fetch each individual article from the server. But
18602 you might want to anyway, I guess. Even though there are three match
18603 keys (@code{Head}, @code{Body} and @code{All}), you should choose one
18604 and stick with it in each score file. If you use any two, each article
18605 will be fetched @emph{twice}. If you want to match a bit on the
18606 @code{Head} and a bit on the @code{Body}, just use @code{All} for all
18609 @item Marking as read
18610 You will probably want to mark articles that have scores below a certain
18611 number as read. This is most easily achieved by putting the following
18612 in your @file{all.SCORE} file:
18616 You may also consider doing something similar with @code{expunge}.
18618 @item Negated character classes
18619 If you say stuff like @code{[^abcd]*}, you may get unexpected results.
18620 That will match newlines, which might lead to, well, The Unknown. Say
18621 @code{[^abcd\n]*} instead.
18625 @node Reverse Scoring
18626 @section Reverse Scoring
18627 @cindex reverse scoring
18629 If you want to keep just articles that have @samp{Sex with Emacs} in the
18630 subject header, and expunge all other articles, you could put something
18631 like this in your score file:
18635 ("Sex with Emacs" 2))
18640 So, you raise all articles that match @samp{Sex with Emacs} and mark the
18641 rest as read, and expunge them to boot.
18644 @node Global Score Files
18645 @section Global Score Files
18646 @cindex global score files
18648 Sure, other newsreaders have ``global kill files''. These are usually
18649 nothing more than a single kill file that applies to all groups, stored
18650 in the user's home directory. Bah! Puny, weak newsreaders!
18652 What I'm talking about here are Global Score Files. Score files from
18653 all over the world, from users everywhere, uniting all nations in one
18654 big, happy score file union! Ange-score! New and untested!
18656 @vindex gnus-global-score-files
18657 All you have to do to use other people's score files is to set the
18658 @code{gnus-global-score-files} variable. One entry for each score file,
18659 or each score file directory. Gnus will decide by itself what score
18660 files are applicable to which group.
18662 To use the score file
18663 @file{/ftp@@ftp.gnus.org:/pub/larsi/ding/score/soc.motss.SCORE} and
18664 all score files in the @file{/ftp@@ftp.some-where:/pub/score} directory,
18668 (setq gnus-global-score-files
18669 '("/ftp@@ftp.gnus.org:/pub/larsi/ding/score/soc.motss.SCORE"
18670 "/ftp@@ftp.some-where:/pub/score/"))
18673 @findex gnus-score-search-global-directories
18675 Simple, eh? Directory names must end with a @samp{/}. These
18676 directories are typically scanned only once during each Gnus session.
18677 If you feel the need to manually re-scan the remote directories, you can
18678 use the @code{gnus-score-search-global-directories} command.
18680 Note that, at present, using this option will slow down group entry
18681 somewhat. (That is---a lot.)
18683 If you want to start maintaining score files for other people to use,
18684 just put your score file up for anonymous ftp and announce it to the
18685 world. Become a retro-moderator! Participate in the retro-moderator
18686 wars sure to ensue, where retro-moderators battle it out for the
18687 sympathy of the people, luring them to use their score files on false
18688 premises! Yay! The net is saved!
18690 Here are some tips for the would-be retro-moderator, off the top of my
18696 Articles heavily crossposted are probably junk.
18698 To lower a single inappropriate article, lower by @code{Message-ID}.
18700 Particularly brilliant authors can be raised on a permanent basis.
18702 Authors that repeatedly post off-charter for the group can safely be
18703 lowered out of existence.
18705 Set the @code{mark} and @code{expunge} atoms to obliterate the nastiest
18706 articles completely.
18709 Use expiring score entries to keep the size of the file down. You
18710 should probably have a long expiry period, though, as some sites keep
18711 old articles for a long time.
18714 ... I wonder whether other newsreaders will support global score files
18715 in the future. @emph{Snicker}. Yup, any day now, newsreaders like Blue
18716 Wave, xrn and 1stReader are bound to implement scoring. Should we start
18717 holding our breath yet?
18721 @section Kill Files
18724 Gnus still supports those pesky old kill files. In fact, the kill file
18725 entries can now be expiring, which is something I wrote before Daniel
18726 Quinlan thought of doing score files, so I've left the code in there.
18728 In short, kill processing is a lot slower (and I do mean @emph{a lot})
18729 than score processing, so it might be a good idea to rewrite your kill
18730 files into score files.
18732 Anyway, a kill file is a normal @code{emacs-lisp} file. You can put any
18733 forms into this file, which means that you can use kill files as some
18734 sort of primitive hook function to be run on group entry, even though
18735 that isn't a very good idea.
18737 Normal kill files look like this:
18740 (gnus-kill "From" "Lars Ingebrigtsen")
18741 (gnus-kill "Subject" "ding")
18745 This will mark every article written by me as read, and remove the
18746 marked articles from the summary buffer. Very useful, you'll agree.
18748 Other programs use a totally different kill file syntax. If Gnus
18749 encounters what looks like a @code{rn} kill file, it will take a stab at
18752 Two summary functions for editing a GNUS kill file:
18757 @kindex M-k (Summary)
18758 @findex gnus-summary-edit-local-kill
18759 Edit this group's kill file (@code{gnus-summary-edit-local-kill}).
18762 @kindex M-K (Summary)
18763 @findex gnus-summary-edit-global-kill
18764 Edit the general kill file (@code{gnus-summary-edit-global-kill}).
18767 Two group mode functions for editing the kill files:
18772 @kindex M-k (Group)
18773 @findex gnus-group-edit-local-kill
18774 Edit this group's kill file (@code{gnus-group-edit-local-kill}).
18777 @kindex M-K (Group)
18778 @findex gnus-group-edit-global-kill
18779 Edit the general kill file (@code{gnus-group-edit-global-kill}).
18782 Kill file variables:
18785 @item gnus-kill-file-name
18786 @vindex gnus-kill-file-name
18787 A kill file for the group @samp{soc.motss} is normally called
18788 @file{soc.motss.KILL}. The suffix appended to the group name to get
18789 this file name is detailed by the @code{gnus-kill-file-name} variable.
18790 The ``global'' kill file (not in the score file sense of ``global'', of
18791 course) is just called @file{KILL}.
18793 @vindex gnus-kill-save-kill-file
18794 @item gnus-kill-save-kill-file
18795 If this variable is non-@code{nil}, Gnus will save the
18796 kill file after processing, which is necessary if you use expiring
18799 @item gnus-apply-kill-hook
18800 @vindex gnus-apply-kill-hook
18801 @findex gnus-apply-kill-file-unless-scored
18802 @findex gnus-apply-kill-file
18803 A hook called to apply kill files to a group. It is
18804 @code{(gnus-apply-kill-file)} by default. If you want to ignore the
18805 kill file if you have a score file for the same group, you can set this
18806 hook to @code{(gnus-apply-kill-file-unless-scored)}. If you don't want
18807 kill files to be processed, you should set this variable to @code{nil}.
18809 @item gnus-kill-file-mode-hook
18810 @vindex gnus-kill-file-mode-hook
18811 A hook called in kill-file mode buffers.
18816 @node Converting Kill Files
18817 @section Converting Kill Files
18819 @cindex converting kill files
18821 If you have loads of old kill files, you may want to convert them into
18822 score files. If they are ``regular'', you can use
18823 the @file{gnus-kill-to-score.el} package; if not, you'll have to do it
18826 The kill to score conversion package isn't included in Gnus by default.
18827 You can fetch it from
18828 @uref{http://www.stud.ifi.uio.no/~larsi/ding-various/gnus-kill-to-score.el}.
18830 If your old kill files are very complex---if they contain more
18831 non-@code{gnus-kill} forms than not, you'll have to convert them by
18832 hand. Or just let them be as they are. Gnus will still use them as
18840 GroupLens (@uref{http://www.cs.umn.edu/Research/GroupLens/}) is a
18841 collaborative filtering system that helps you work together with other
18842 people to find the quality news articles out of the huge volume of
18843 news articles generated every day.
18845 To accomplish this the GroupLens system combines your opinions about
18846 articles you have already read with the opinions of others who have done
18847 likewise and gives you a personalized prediction for each unread news
18848 article. Think of GroupLens as a matchmaker. GroupLens watches how you
18849 rate articles, and finds other people that rate articles the same way.
18850 Once it has found some people you agree with it tells you, in the form
18851 of a prediction, what they thought of the article. You can use this
18852 prediction to help you decide whether or not you want to read the
18855 @sc{Note:} Unfortunately the GroupLens system seems to have shut down,
18856 so this section is mostly of historical interest.
18859 * Using GroupLens:: How to make Gnus use GroupLens.
18860 * Rating Articles:: Letting GroupLens know how you rate articles.
18861 * Displaying Predictions:: Displaying predictions given by GroupLens.
18862 * GroupLens Variables:: Customizing GroupLens.
18866 @node Using GroupLens
18867 @subsection Using GroupLens
18869 To use GroupLens you must register a pseudonym with your local Better
18871 @uref{http://www.cs.umn.edu/Research/GroupLens/bbb.html} is the only
18872 better bit in town at the moment.
18874 Once you have registered you'll need to set a couple of variables.
18878 @item gnus-use-grouplens
18879 @vindex gnus-use-grouplens
18880 Setting this variable to a non-@code{nil} value will make Gnus hook into
18881 all the relevant GroupLens functions.
18883 @item grouplens-pseudonym
18884 @vindex grouplens-pseudonym
18885 This variable should be set to the pseudonym you got when registering
18886 with the Better Bit Bureau.
18888 @item grouplens-newsgroups
18889 @vindex grouplens-newsgroups
18890 A list of groups that you want to get GroupLens predictions for.
18894 That's the minimum of what you need to get up and running with GroupLens.
18895 Once you've registered, GroupLens will start giving you scores for
18896 articles based on the average of what other people think. But, to get
18897 the real benefit of GroupLens you need to start rating articles
18898 yourself. Then the scores GroupLens gives you will be personalized for
18899 you, based on how the people you usually agree with have already rated.
18902 @node Rating Articles
18903 @subsection Rating Articles
18905 In GroupLens, an article is rated on a scale from 1 to 5, inclusive.
18906 Where 1 means something like this article is a waste of bandwidth and 5
18907 means that the article was really good. The basic question to ask
18908 yourself is, "on a scale from 1 to 5 would I like to see more articles
18911 There are four ways to enter a rating for an article in GroupLens.
18916 @kindex r (GroupLens)
18917 @findex bbb-summary-rate-article
18918 This function will prompt you for a rating on a scale of one to five.
18921 @kindex k (GroupLens)
18922 @findex grouplens-score-thread
18923 This function will prompt you for a rating, and rate all the articles in
18924 the thread. This is really useful for some of those long running giant
18925 threads in rec.humor.
18929 The next two commands, @kbd{n} and @kbd{,} take a numerical prefix to be
18930 the score of the article you're reading.
18935 @kindex n (GroupLens)
18936 @findex grouplens-next-unread-article
18937 Rate the article and go to the next unread article.
18940 @kindex , (GroupLens)
18941 @findex grouplens-best-unread-article
18942 Rate the article and go to the next unread article with the highest score.
18946 If you want to give the current article a score of 4 and then go to the
18947 next article, just type @kbd{4 n}.
18950 @node Displaying Predictions
18951 @subsection Displaying Predictions
18953 GroupLens makes a prediction for you about how much you will like a
18954 news article. The predictions from GroupLens are on a scale from 1 to
18955 5, where 1 is the worst and 5 is the best. You can use the predictions
18956 from GroupLens in one of three ways controlled by the variable
18957 @code{gnus-grouplens-override-scoring}.
18959 @vindex gnus-grouplens-override-scoring
18960 There are three ways to display predictions in grouplens. You may
18961 choose to have the GroupLens scores contribute to, or override the
18962 regular gnus scoring mechanism. override is the default; however, some
18963 people prefer to see the Gnus scores plus the grouplens scores. To get
18964 the separate scoring behavior you need to set
18965 @code{gnus-grouplens-override-scoring} to @code{'separate}. To have the
18966 GroupLens predictions combined with the grouplens scores set it to
18967 @code{'override} and to combine the scores set
18968 @code{gnus-grouplens-override-scoring} to @code{'combine}. When you use
18969 the combine option you will also want to set the values for
18970 @code{grouplens-prediction-offset} and
18971 @code{grouplens-score-scale-factor}.
18973 @vindex grouplens-prediction-display
18974 In either case, GroupLens gives you a few choices for how you would like
18975 to see your predictions displayed. The display of predictions is
18976 controlled by the @code{grouplens-prediction-display} variable.
18978 The following are valid values for that variable.
18981 @item prediction-spot
18982 The higher the prediction, the further to the right an @samp{*} is
18985 @item confidence-interval
18986 A numeric confidence interval.
18988 @item prediction-bar
18989 The higher the prediction, the longer the bar.
18991 @item confidence-bar
18992 Numerical confidence.
18994 @item confidence-spot
18995 The spot gets bigger with more confidence.
18997 @item prediction-num
18998 Plain-old numeric value.
19000 @item confidence-plus-minus
19001 Prediction +/- confidence.
19006 @node GroupLens Variables
19007 @subsection GroupLens Variables
19011 @item gnus-summary-grouplens-line-format
19012 The summary line format used in GroupLens-enhanced summary buffers. It
19013 accepts the same specs as the normal summary line format (@pxref{Summary
19014 Buffer Lines}). The default is @samp{%U%R%z%l%I%(%[%4L: %-23,23n%]%)
19017 @item grouplens-bbb-host
19018 Host running the bbbd server. @samp{grouplens.cs.umn.edu} is the
19021 @item grouplens-bbb-port
19022 Port of the host running the bbbd server. The default is 9000.
19024 @item grouplens-score-offset
19025 Offset the prediction by this value. In other words, subtract the
19026 prediction value by this number to arrive at the effective score. The
19029 @item grouplens-score-scale-factor
19030 This variable allows the user to magnify the effect of GroupLens scores.
19031 The scale factor is applied after the offset. The default is 1.
19036 @node Advanced Scoring
19037 @section Advanced Scoring
19039 Scoring on Subjects and From headers is nice enough, but what if you're
19040 really interested in what a person has to say only when she's talking
19041 about a particular subject? Or what if you really don't want to
19042 read what person A has to say when she's following up to person B, but
19043 want to read what she says when she's following up to person C?
19045 By using advanced scoring rules you may create arbitrarily complex
19049 * Advanced Scoring Syntax:: A definition.
19050 * Advanced Scoring Examples:: What they look like.
19051 * Advanced Scoring Tips:: Getting the most out of it.
19055 @node Advanced Scoring Syntax
19056 @subsection Advanced Scoring Syntax
19058 Ordinary scoring rules have a string as the first element in the rule.
19059 Advanced scoring rules have a list as the first element. The second
19060 element is the score to be applied if the first element evaluated to a
19061 non-@code{nil} value.
19063 These lists may consist of three logical operators, one redirection
19064 operator, and various match operators.
19071 This logical operator will evaluate each of its arguments until it finds
19072 one that evaluates to @code{false}, and then it'll stop. If all arguments
19073 evaluate to @code{true} values, then this operator will return
19078 This logical operator will evaluate each of its arguments until it finds
19079 one that evaluates to @code{true}. If no arguments are @code{true},
19080 then this operator will return @code{false}.
19085 This logical operator only takes a single argument. It returns the
19086 logical negation of the value of its argument.
19090 There is an @dfn{indirection operator} that will make its arguments
19091 apply to the ancestors of the current article being scored. For
19092 instance, @code{1-} will make score rules apply to the parent of the
19093 current article. @code{2-} will make score rules apply to the
19094 grandparent of the current article. Alternatively, you can write
19095 @code{^^}, where the number of @code{^}s (carets) says how far back into
19096 the ancestry you want to go.
19098 Finally, we have the match operators. These are the ones that do the
19099 real work. Match operators are header name strings followed by a match
19100 and a match type. A typical match operator looks like @samp{("from"
19101 "Lars Ingebrigtsen" s)}. The header names are the same as when using
19102 simple scoring, and the match types are also the same.
19105 @node Advanced Scoring Examples
19106 @subsection Advanced Scoring Examples
19108 Please note that the following examples are score file rules. To
19109 make a complete score file from them, surround them with another pair
19112 Let's say you want to increase the score of articles written by Lars
19113 when he's talking about Gnus:
19117 ("from" "Lars Ingebrigtsen")
19118 ("subject" "Gnus"))
19124 When he writes long articles, he sometimes has something nice to say:
19128 ("from" "Lars Ingebrigtsen")
19135 However, when he responds to things written by Reig Eigil Logge, you
19136 really don't want to read what he's written:
19140 ("from" "Lars Ingebrigtsen")
19141 (1- ("from" "Reig Eigir Logge")))
19145 Everybody that follows up Redmondo when he writes about disappearing
19146 socks should have their scores raised, but only when they talk about
19147 white socks. However, when Lars talks about socks, it's usually not
19154 ("from" "redmondo@@.*no" r)
19155 ("body" "disappearing.*socks" t)))
19156 (! ("from" "Lars Ingebrigtsen"))
19157 ("body" "white.*socks"))
19161 The possibilities are endless.
19164 @node Advanced Scoring Tips
19165 @subsection Advanced Scoring Tips
19167 The @code{&} and @code{|} logical operators do short-circuit logic.
19168 That is, they stop processing their arguments when it's clear what the
19169 result of the operation will be. For instance, if one of the arguments
19170 of an @code{&} evaluates to @code{false}, there's no point in evaluating
19171 the rest of the arguments. This means that you should put slow matches
19172 (@samp{body}, @samp{header}) last and quick matches (@samp{from},
19173 @samp{subject}) first.
19175 The indirection arguments (@code{1-} and so on) will make their
19176 arguments work on previous generations of the thread. If you say
19187 Then that means "score on the from header of the grandparent of the
19188 current article". An indirection is quite fast, but it's better to say:
19194 ("subject" "Gnus")))
19201 (1- ("from" "Lars"))
19202 (1- ("subject" "Gnus")))
19207 @section Score Decays
19208 @cindex score decays
19211 You may find that your scores have a tendency to grow without
19212 bounds, especially if you're using adaptive scoring. If scores get too
19213 big, they lose all meaning---they simply max out and it's difficult to
19214 use them in any sensible way.
19216 @vindex gnus-decay-scores
19217 @findex gnus-decay-score
19218 @vindex gnus-decay-score-function
19219 Gnus provides a mechanism for decaying scores to help with this problem.
19220 When score files are loaded and @code{gnus-decay-scores} is
19221 non-@code{nil}, Gnus will run the score files through the decaying
19222 mechanism thereby lowering the scores of all non-permanent score rules.
19223 The decay itself if performed by the @code{gnus-decay-score-function}
19224 function, which is @code{gnus-decay-score} by default. Here's the
19225 definition of that function:
19228 (defun gnus-decay-score (score)
19230 This is done according to `gnus-score-decay-constant'
19231 and `gnus-score-decay-scale'."
19234 (* (if (< score 0) 1 -1)
19236 (max gnus-score-decay-constant
19238 gnus-score-decay-scale)))))))
19241 @vindex gnus-score-decay-scale
19242 @vindex gnus-score-decay-constant
19243 @code{gnus-score-decay-constant} is 3 by default and
19244 @code{gnus-score-decay-scale} is 0.05. This should cause the following:
19248 Scores between -3 and 3 will be set to 0 when this function is called.
19251 Scores with magnitudes between 3 and 60 will be shrunk by 3.
19254 Scores with magnitudes greater than 60 will be shrunk by 5% of the
19258 If you don't like this decay function, write your own. It is called
19259 with the score to be decayed as its only parameter, and it should return
19260 the new score, which should be an integer.
19262 Gnus will try to decay scores once a day. If you haven't run Gnus for
19263 four days, Gnus will decay the scores four times, for instance.
19268 @include message.texi
19269 @chapter Emacs MIME
19270 @include emacs-mime.texi
19272 @include sieve.texi
19274 @c @include pgg.texi
19282 * Process/Prefix:: A convention used by many treatment commands.
19283 * Interactive:: Making Gnus ask you many questions.
19284 * Symbolic Prefixes:: How to supply some Gnus functions with options.
19285 * Formatting Variables:: You can specify what buffers should look like.
19286 * Window Layout:: Configuring the Gnus buffer windows.
19287 * Faces and Fonts:: How to change how faces look.
19288 * Compilation:: How to speed Gnus up.
19289 * Mode Lines:: Displaying information in the mode lines.
19290 * Highlighting and Menus:: Making buffers look all nice and cozy.
19291 * Buttons:: Get tendinitis in ten easy steps!
19292 * Daemons:: Gnus can do things behind your back.
19293 * NoCeM:: How to avoid spam and other fatty foods.
19294 * Undo:: Some actions can be undone.
19295 * Predicate Specifiers:: Specifying predicates.
19296 * Moderation:: What to do if you're a moderator.
19297 * Image Enhancements:: Modern versions of Emacs/XEmacs can display images.
19298 * Fuzzy Matching:: What's the big fuzz?
19299 * Thwarting Email Spam:: A how-to on avoiding unsolicited commercial email.
19300 * Various Various:: Things that are really various.
19304 @node Process/Prefix
19305 @section Process/Prefix
19306 @cindex process/prefix convention
19308 Many functions, among them functions for moving, decoding and saving
19309 articles, use what is known as the @dfn{Process/Prefix convention}.
19311 This is a method for figuring out what articles the user wants the
19312 command to be performed on.
19316 If the numeric prefix is N, perform the operation on the next N
19317 articles, starting with the current one. If the numeric prefix is
19318 negative, perform the operation on the previous N articles, starting
19319 with the current one.
19321 @vindex transient-mark-mode
19322 If @code{transient-mark-mode} in non-@code{nil} and the region is
19323 active, all articles in the region will be worked upon.
19325 If there is no numeric prefix, but some articles are marked with the
19326 process mark, perform the operation on the articles marked with
19329 If there is neither a numeric prefix nor any articles marked with the
19330 process mark, just perform the operation on the current article.
19332 Quite simple, really, but it needs to be made clear so that surprises
19335 Commands that react to the process mark will push the current list of
19336 process marked articles onto a stack and will then clear all process
19337 marked articles. You can restore the previous configuration with the
19338 @kbd{M P y} command (@pxref{Setting Process Marks}).
19340 @vindex gnus-summary-goto-unread
19341 One thing that seems to shock & horrify lots of people is that, for
19342 instance, @kbd{3 d} does exactly the same as @kbd{d} @kbd{d} @kbd{d}.
19343 Since each @kbd{d} (which marks the current article as read) by default
19344 goes to the next unread article after marking, this means that @kbd{3 d}
19345 will mark the next three unread articles as read, no matter what the
19346 summary buffer looks like. Set @code{gnus-summary-goto-unread} to
19347 @code{nil} for a more straightforward action.
19349 Many commands do not use the process/prefix convention. All commands
19350 that do explicitly say so in this manual. To apply the process/prefix
19351 convention to commands that do not use it, you can use the @kbd{M-&}
19352 command. For instance, to mark all the articles in the group as
19353 expirable, you could say `M P b M-& E'.
19357 @section Interactive
19358 @cindex interaction
19362 @item gnus-novice-user
19363 @vindex gnus-novice-user
19364 If this variable is non-@code{nil}, you are either a newcomer to the
19365 World of Usenet, or you are very cautious, which is a nice thing to be,
19366 really. You will be given questions of the type ``Are you sure you want
19367 to do this?'' before doing anything dangerous. This is @code{t} by
19370 @item gnus-expert-user
19371 @vindex gnus-expert-user
19372 If this variable is non-@code{nil}, you will seldom be asked any
19373 questions by Gnus. It will simply assume you know what you're doing, no
19374 matter how strange.
19376 @item gnus-interactive-catchup
19377 @vindex gnus-interactive-catchup
19378 Require confirmation before catching up a group if non-@code{nil}. It
19379 is @code{t} by default.
19381 @item gnus-interactive-exit
19382 @vindex gnus-interactive-exit
19383 Require confirmation before exiting Gnus. This variable is @code{t} by
19388 @node Symbolic Prefixes
19389 @section Symbolic Prefixes
19390 @cindex symbolic prefixes
19392 Quite a lot of Emacs commands react to the (numeric) prefix. For
19393 instance, @kbd{C-u 4 C-f} moves point four characters forward, and
19394 @kbd{C-u 9 0 0 I s s p} adds a permanent @code{Subject} substring score
19395 rule of 900 to the current article.
19397 This is all nice and well, but what if you want to give a command some
19398 additional information? Well, what most commands do is interpret the
19399 ``raw'' prefix in some special way. @kbd{C-u 0 C-x C-s} means that one
19400 doesn't want a backup file to be created when saving the current buffer,
19401 for instance. But what if you want to save without making a backup
19402 file, and you want Emacs to flash lights and play a nice tune at the
19403 same time? You can't, and you're probably perfectly happy that way.
19405 @kindex M-i (Summary)
19406 @findex gnus-symbolic-argument
19407 I'm not, so I've added a second prefix---the @dfn{symbolic prefix}. The
19408 prefix key is @kbd{M-i} (@code{gnus-symbolic-argument}), and the next
19409 character typed in is the value. You can stack as many @kbd{M-i}
19410 prefixes as you want. @kbd{M-i a C-M-u} means ``feed the @kbd{C-M-u}
19411 command the symbolic prefix @code{a}''. @kbd{M-i a M-i b C-M-u} means
19412 ``feed the @kbd{C-M-u} command the symbolic prefixes @code{a} and
19413 @code{b}''. You get the drift.
19415 Typing in symbolic prefixes to commands that don't accept them doesn't
19416 hurt, but it doesn't do any good either. Currently not many Gnus
19417 functions make use of the symbolic prefix.
19419 If you're interested in how Gnus implements this, @pxref{Extended
19423 @node Formatting Variables
19424 @section Formatting Variables
19425 @cindex formatting variables
19427 Throughout this manual you've probably noticed lots of variables called
19428 things like @code{gnus-group-line-format} and
19429 @code{gnus-summary-mode-line-format}. These control how Gnus is to
19430 output lines in the various buffers. There's quite a lot of them.
19431 Fortunately, they all use the same syntax, so there's not that much to
19434 Here's an example format spec (from the group buffer): @samp{%M%S%5y:
19435 %(%g%)\n}. We see that it is indeed extremely ugly, and that there are
19436 lots of percentages everywhere.
19439 * Formatting Basics:: A formatting variable is basically a format string.
19440 * Mode Line Formatting:: Some rules about mode line formatting variables.
19441 * Advanced Formatting:: Modifying output in various ways.
19442 * User-Defined Specs:: Having Gnus call your own functions.
19443 * Formatting Fonts:: Making the formatting look colorful and nice.
19444 * Positioning Point:: Moving point to a position after an operation.
19445 * Tabulation:: Tabulating your output.
19446 * Wide Characters:: Dealing with wide characters.
19449 Currently Gnus uses the following formatting variables:
19450 @code{gnus-group-line-format}, @code{gnus-summary-line-format},
19451 @code{gnus-server-line-format}, @code{gnus-topic-line-format},
19452 @code{gnus-group-mode-line-format},
19453 @code{gnus-summary-mode-line-format},
19454 @code{gnus-article-mode-line-format},
19455 @code{gnus-server-mode-line-format}, and
19456 @code{gnus-summary-pick-line-format}.
19458 All these format variables can also be arbitrary elisp forms. In that
19459 case, they will be @code{eval}ed to insert the required lines.
19461 @kindex M-x gnus-update-format
19462 @findex gnus-update-format
19463 Gnus includes a command to help you while creating your own format
19464 specs. @kbd{M-x gnus-update-format} will @code{eval} the current form,
19465 update the spec in question and pop you to a buffer where you can
19466 examine the resulting lisp code to be run to generate the line.
19470 @node Formatting Basics
19471 @subsection Formatting Basics
19473 Each @samp{%} element will be replaced by some string or other when the
19474 buffer in question is generated. @samp{%5y} means ``insert the @samp{y}
19475 spec, and pad with spaces to get a 5-character field''.
19477 As with normal C and Emacs Lisp formatting strings, the numerical
19478 modifier between the @samp{%} and the formatting type character will
19479 @dfn{pad} the output so that it is always at least that long.
19480 @samp{%5y} will make the field always (at least) five characters wide by
19481 padding with spaces to the left. If you say @samp{%-5y}, it will pad to
19484 You may also wish to limit the length of the field to protect against
19485 particularly wide values. For that you can say @samp{%4,6y}, which
19486 means that the field will never be more than 6 characters wide and never
19487 less than 4 characters wide.
19489 Also Gnus supports some extended format specifications, such as
19490 @samp{%&user-date;}.
19493 @node Mode Line Formatting
19494 @subsection Mode Line Formatting
19496 Mode line formatting variables (e.g.,
19497 @code{gnus-summary-mode-line-format}) follow the same rules as other,
19498 buffer line oriented formatting variables (@pxref{Formatting Basics})
19499 with the following two differences:
19504 There must be no newline (@samp{\n}) at the end.
19507 The special @samp{%%b} spec can be used to display the buffer name.
19508 Well, it's no spec at all, really---@samp{%%} is just a way to quote
19509 @samp{%} to allow it to pass through the formatting machinery unmangled,
19510 so that Emacs receives @samp{%b}, which is something the Emacs mode line
19511 display interprets to mean ``show the buffer name''. For a full list of
19512 mode line specs Emacs understands, see the documentation of the
19513 @code{mode-line-format} variable.
19518 @node Advanced Formatting
19519 @subsection Advanced Formatting
19521 It is frequently useful to post-process the fields in some way.
19522 Padding, limiting, cutting off parts and suppressing certain values can
19523 be achieved by using @dfn{tilde modifiers}. A typical tilde spec might
19524 look like @samp{%~(cut 3)~(ignore "0")y}.
19526 These are the valid modifiers:
19531 Pad the field to the left with spaces until it reaches the required
19535 Pad the field to the right with spaces until it reaches the required
19540 Cut off characters from the left until it reaches the specified length.
19543 Cut off characters from the right until it reaches the specified
19548 Cut off the specified number of characters from the left.
19551 Cut off the specified number of characters from the right.
19554 Return an empty string if the field is equal to the specified value.
19557 Use the specified form as the field value when the @samp{@@} spec is
19563 "~(form (current-time-string))@@"
19568 Let's take an example. The @samp{%o} spec in the summary mode lines
19569 will return a date in compact ISO8601 format---@samp{19960809T230410}.
19570 This is quite a mouthful, so we want to shave off the century number and
19571 the time, leaving us with a six-character date. That would be
19572 @samp{%~(cut-left 2)~(max-right 6)~(pad 6)o}. (Cutting is done before
19573 maxing, and we need the padding to ensure that the date is never less
19574 than 6 characters to make it look nice in columns.)
19576 Ignoring is done first; then cutting; then maxing; and then as the very
19577 last operation, padding.
19579 @vindex gnus-compile-user-specs
19580 If @code{gnus-compile-user-specs} is set to @code{nil} (@code{t} by
19581 default) with your strong personality, and use a lots of these advanced
19582 thingies, you'll find that Gnus gets quite slow. This can be helped
19583 enormously by running @kbd{M-x gnus-compile} when you are satisfied with
19584 the look of your lines.
19585 @xref{Compilation}.
19588 @node User-Defined Specs
19589 @subsection User-Defined Specs
19591 All the specs allow for inserting user defined specifiers---@samp{u}.
19592 The next character in the format string should be a letter. Gnus
19593 will call the function @code{gnus-user-format-function-}@samp{X}, where
19594 @samp{X} is the letter following @samp{%u}. The function will be passed
19595 a single parameter---what the parameter means depends on what buffer
19596 it's being called from. The function should return a string, which will
19597 be inserted into the buffer just like information from any other
19598 specifier. This function may also be called with dummy values, so it
19599 should protect against that.
19601 Also Gnus supports extended user-defined specs, such as @samp{%u&foo;}.
19602 Gnus will call the function @code{gnus-user-format-function-}@samp{foo}.
19604 You can also use tilde modifiers (@pxref{Advanced Formatting} to achieve
19605 much the same without defining new functions. Here's an example:
19606 @samp{%~(form (count-lines (point-min) (point)))@@}. The form
19607 given here will be evaluated to yield the current line number, and then
19611 @node Formatting Fonts
19612 @subsection Formatting Fonts
19614 There are specs for highlighting, and these are shared by all the format
19615 variables. Text inside the @samp{%(} and @samp{%)} specifiers will get
19616 the special @code{mouse-face} property set, which means that it will be
19617 highlighted (with @code{gnus-mouse-face}) when you put the mouse pointer
19620 Text inside the @samp{%@{} and @samp{%@}} specifiers will have their
19621 normal faces set using @code{gnus-face-0}, which is @code{bold} by
19622 default. If you say @samp{%1@{}, you'll get @code{gnus-face-1} instead,
19623 and so on. Create as many faces as you wish. The same goes for the
19624 @code{mouse-face} specs---you can say @samp{%3(hello%)} to have
19625 @samp{hello} mouse-highlighted with @code{gnus-mouse-face-3}.
19627 Text inside the @samp{%<<} and @samp{%>>} specifiers will get the
19628 special @code{balloon-help} property set to @code{gnus-balloon-face-0}.
19629 If you say @samp{%1<<}, you'll get @code{gnus-balloon-face-1} and so on.
19630 The @code{gnus-balloon-face-*} variables should be either strings or
19631 symbols naming functions that return a string. When the mouse passes
19632 over text with this property set, a balloon window will appear and
19633 display the string. Please refer to @ref{(emacs)Help Echo} (in GNU
19634 Emacs) or the doc string of @code{balloon-help-mode} (in XEmacs) for
19635 more information on this. (For technical reasons, the guillemets have
19636 been approximated as @samp{<<} and @samp{>>} in this paragraph.)
19638 Here's an alternative recipe for the group buffer:
19641 ;; Create three face types.
19642 (setq gnus-face-1 'bold)
19643 (setq gnus-face-3 'italic)
19645 ;; We want the article count to be in
19646 ;; a bold and green face. So we create
19647 ;; a new face called `my-green-bold'.
19648 (copy-face 'bold 'my-green-bold)
19650 (set-face-foreground 'my-green-bold "ForestGreen")
19651 (setq gnus-face-2 'my-green-bold)
19653 ;; Set the new & fancy format.
19654 (setq gnus-group-line-format
19655 "%M%S%3@{%5y%@}%2[:%] %(%1@{%g%@}%)\n")
19658 I'm sure you'll be able to use this scheme to create totally unreadable
19659 and extremely vulgar displays. Have fun!
19661 Note that the @samp{%(} specs (and friends) do not make any sense on the
19662 mode-line variables.
19664 @node Positioning Point
19665 @subsection Positioning Point
19667 Gnus usually moves point to a pre-defined place on each line in most
19668 buffers. By default, point move to the first colon character on the
19669 line. You can customize this behaviour in three different ways.
19671 You can move the colon character to somewhere else on the line.
19673 @findex gnus-goto-colon
19674 You can redefine the function that moves the point to the colon. The
19675 function is called @code{gnus-goto-colon}.
19677 But perhaps the most convenient way to deal with this, if you don't want
19678 to have a colon in your line, is to use the @samp{%*} specifier. If you
19679 put a @samp{%*} somewhere in your format line definition, Gnus will
19684 @subsection Tabulation
19686 You can usually line up your displays by padding and cutting your
19687 strings. However, when combining various strings of different size, it
19688 can often be more convenient to just output the strings, and then worry
19689 about lining up the following text afterwards.
19691 To do that, Gnus supplies tabulator specs--@samp{%=}. There are two
19692 different types---@dfn{hard tabulators} and @dfn{soft tabulators}.
19694 @samp{%50=} will insert space characters to pad the line up to column
19695 50. If the text is already past column 50, nothing will be inserted.
19696 This is the soft tabulator.
19698 @samp{%-50=} will insert space characters to pad the line up to column
19699 50. If the text is already past column 50, the excess text past column
19700 50 will be removed. This is the hard tabulator.
19703 @node Wide Characters
19704 @subsection Wide Characters
19706 Proportional fonts in most countries have characters of the same width.
19707 Some countries, however, use Latin characters mixed with wider
19708 characters---most notable East Asian countries.
19710 The problem is that when formatting, Gnus assumes that if a string is 10
19711 characters wide, it'll be 10 Latin characters wide on the screen. In
19712 these countries, that's not true.
19714 @vindex gnus-use-correct-string-widths
19715 To help fix this, you can set @code{gnus-use-correct-string-widths} to
19716 @code{t}. This makes buffer generation slower, but the results will be
19717 prettier. The default value under XEmacs is @code{t} but @code{nil}
19721 @node Window Layout
19722 @section Window Layout
19723 @cindex window layout
19725 No, there's nothing here about X, so be quiet.
19727 @vindex gnus-use-full-window
19728 If @code{gnus-use-full-window} non-@code{nil}, Gnus will delete all
19729 other windows and occupy the entire Emacs screen by itself. It is
19730 @code{t} by default.
19732 Setting this variable to @code{nil} kinda works, but there are
19733 glitches. Use at your own peril.
19735 @vindex gnus-buffer-configuration
19736 @code{gnus-buffer-configuration} describes how much space each Gnus
19737 buffer should be given. Here's an excerpt of this variable:
19740 ((group (vertical 1.0 (group 1.0 point)
19741 (if gnus-carpal (group-carpal 4))))
19742 (article (vertical 1.0 (summary 0.25 point)
19746 This is an alist. The @dfn{key} is a symbol that names some action or
19747 other. For instance, when displaying the group buffer, the window
19748 configuration function will use @code{group} as the key. A full list of
19749 possible names is listed below.
19751 The @dfn{value} (i.e., the @dfn{split}) says how much space each buffer
19752 should occupy. To take the @code{article} split as an example -
19755 (article (vertical 1.0 (summary 0.25 point)
19759 This @dfn{split} says that the summary buffer should occupy 25% of upper
19760 half of the screen, and that it is placed over the article buffer. As
19761 you may have noticed, 100% + 25% is actually 125% (yup, I saw y'all
19762 reaching for that calculator there). However, the special number
19763 @code{1.0} is used to signal that this buffer should soak up all the
19764 rest of the space available after the rest of the buffers have taken
19765 whatever they need. There should be only one buffer with the @code{1.0}
19766 size spec per split.
19768 Point will be put in the buffer that has the optional third element
19769 @code{point}. In a @code{frame} split, the last subsplit having a leaf
19770 split where the tag @code{frame-focus} is a member (i.e. is the third or
19771 fourth element in the list, depending on whether the @code{point} tag is
19772 present) gets focus.
19774 Here's a more complicated example:
19777 (article (vertical 1.0 (group 4)
19778 (summary 0.25 point)
19779 (if gnus-carpal (summary-carpal 4))
19783 If the size spec is an integer instead of a floating point number,
19784 then that number will be used to say how many lines a buffer should
19785 occupy, not a percentage.
19787 If the @dfn{split} looks like something that can be @code{eval}ed (to be
19788 precise---if the @code{car} of the split is a function or a subr), this
19789 split will be @code{eval}ed. If the result is non-@code{nil}, it will
19790 be used as a split. This means that there will be three buffers if
19791 @code{gnus-carpal} is @code{nil}, and four buffers if @code{gnus-carpal}
19794 Not complicated enough for you? Well, try this on for size:
19797 (article (horizontal 1.0
19802 (summary 0.25 point)
19807 Whoops. Two buffers with the mystery 100% tag. And what's that
19808 @code{horizontal} thingie?
19810 If the first element in one of the split is @code{horizontal}, Gnus will
19811 split the window horizontally, giving you two windows side-by-side.
19812 Inside each of these strips you may carry on all you like in the normal
19813 fashion. The number following @code{horizontal} says what percentage of
19814 the screen is to be given to this strip.
19816 For each split, there @emph{must} be one element that has the 100% tag.
19817 The splitting is never accurate, and this buffer will eat any leftover
19818 lines from the splits.
19820 To be slightly more formal, here's a definition of what a valid split
19824 split = frame | horizontal | vertical | buffer | form
19825 frame = "(frame " size *split ")"
19826 horizontal = "(horizontal " size *split ")"
19827 vertical = "(vertical " size *split ")"
19828 buffer = "(" buf-name " " size *[ "point" ] *[ "frame-focus"] ")"
19829 size = number | frame-params
19830 buf-name = group | article | summary ...
19833 The limitations are that the @code{frame} split can only appear as the
19834 top-level split. @var{form} should be an Emacs Lisp form that should
19835 return a valid split. We see that each split is fully recursive, and
19836 may contain any number of @code{vertical} and @code{horizontal} splits.
19838 @vindex gnus-window-min-width
19839 @vindex gnus-window-min-height
19840 @cindex window height
19841 @cindex window width
19842 Finding the right sizes can be a bit complicated. No window may be less
19843 than @code{gnus-window-min-height} (default 1) characters high, and all
19844 windows must be at least @code{gnus-window-min-width} (default 1)
19845 characters wide. Gnus will try to enforce this before applying the
19846 splits. If you want to use the normal Emacs window width/height limit,
19847 you can just set these two variables to @code{nil}.
19849 If you're not familiar with Emacs terminology, @code{horizontal} and
19850 @code{vertical} splits may work the opposite way of what you'd expect.
19851 Windows inside a @code{horizontal} split are shown side-by-side, and
19852 windows within a @code{vertical} split are shown above each other.
19854 @findex gnus-configure-frame
19855 If you want to experiment with window placement, a good tip is to call
19856 @code{gnus-configure-frame} directly with a split. This is the function
19857 that does all the real work when splitting buffers. Below is a pretty
19858 nonsensical configuration with 5 windows; two for the group buffer and
19859 three for the article buffer. (I said it was nonsensical.) If you
19860 @code{eval} the statement below, you can get an idea of how that would
19861 look straight away, without going through the normal Gnus channels.
19862 Play with it until you're satisfied, and then use
19863 @code{gnus-add-configuration} to add your new creation to the buffer
19864 configuration list.
19867 (gnus-configure-frame
19871 (article 0.3 point))
19879 You might want to have several frames as well. No prob---just use the
19880 @code{frame} split:
19883 (gnus-configure-frame
19886 (summary 0.25 point frame-focus)
19888 (vertical ((height . 5) (width . 15)
19889 (user-position . t)
19890 (left . -1) (top . 1))
19895 This split will result in the familiar summary/article window
19896 configuration in the first (or ``main'') frame, while a small additional
19897 frame will be created where picons will be shown. As you can see,
19898 instead of the normal @code{1.0} top-level spec, each additional split
19899 should have a frame parameter alist as the size spec.
19900 @xref{Frame Parameters, , Frame Parameters, elisp, The GNU Emacs Lisp
19901 Reference Manual}. Under XEmacs, a frame property list will be
19902 accepted, too---for instance, @code{(height 5 width 15 left -1 top 1)}
19904 The list of all possible keys for @code{gnus-buffer-configuration} can
19905 be found in its default value.
19907 Note that the @code{message} key is used for both
19908 @code{gnus-group-mail} and @code{gnus-summary-mail-other-window}. If
19909 it is desirable to distinguish between the two, something like this
19913 (message (horizontal 1.0
19914 (vertical 1.0 (message 1.0 point))
19916 (if (buffer-live-p gnus-summary-buffer)
19921 One common desire for a multiple frame split is to have a separate frame
19922 for composing mail and news while leaving the original frame intact. To
19923 accomplish that, something like the following can be done:
19928 (if (not (buffer-live-p gnus-summary-buffer))
19929 (car (cdr (assoc 'group gnus-buffer-configuration)))
19930 (car (cdr (assoc 'summary gnus-buffer-configuration))))
19931 (vertical ((user-position . t) (top . 1) (left . 1)
19932 (name . "Message"))
19933 (message 1.0 point))))
19936 @findex gnus-add-configuration
19937 Since the @code{gnus-buffer-configuration} variable is so long and
19938 complicated, there's a function you can use to ease changing the config
19939 of a single setting: @code{gnus-add-configuration}. If, for instance,
19940 you want to change the @code{article} setting, you could say:
19943 (gnus-add-configuration
19944 '(article (vertical 1.0
19946 (summary .25 point)
19950 You'd typically stick these @code{gnus-add-configuration} calls in your
19951 @file{.gnus.el} file or in some startup hook---they should be run after
19952 Gnus has been loaded.
19954 @vindex gnus-always-force-window-configuration
19955 If all windows mentioned in the configuration are already visible, Gnus
19956 won't change the window configuration. If you always want to force the
19957 ``right'' window configuration, you can set
19958 @code{gnus-always-force-window-configuration} to non-@code{nil}.
19960 If you're using tree displays (@pxref{Tree Display}), and the tree
19961 window is displayed vertically next to another window, you may also want
19962 to fiddle with @code{gnus-tree-minimize-window} to avoid having the
19965 @subsection Example Window Configurations
19969 Narrow left hand side occupied by group buffer. Right hand side split
19970 between summary buffer (top one-sixth) and article buffer (bottom).
19985 (gnus-add-configuration
19988 (vertical 25 (group 1.0))
19990 (summary 0.16 point)
19993 (gnus-add-configuration
19996 (vertical 25 (group 1.0))
19997 (vertical 1.0 (summary 1.0 point)))))
20003 @node Faces and Fonts
20004 @section Faces and Fonts
20009 Fiddling with fonts and faces used to be very difficult, but these days
20010 it is very simple. You simply say @kbd{M-x customize-face}, pick out
20011 the face you want to alter, and alter it via the standard Customize
20016 @section Compilation
20017 @cindex compilation
20018 @cindex byte-compilation
20020 @findex gnus-compile
20022 Remember all those line format specification variables?
20023 @code{gnus-summary-line-format}, @code{gnus-group-line-format}, and so
20024 on. By default, T-gnus will use the byte-compiled codes of these
20025 variables and we can keep a slow-down to a minimum. However, if you set
20026 @code{gnus-compile-user-specs} to @code{nil} (@code{t} by default),
20027 unfortunately, changing them will mean a quite significant slow-down.
20028 (The default values of these variables have byte-compiled functions
20029 associated with them, while the user-generated versions do not, of
20032 To help with this, you can run @kbd{M-x gnus-compile} after you've
20033 fiddled around with the variables and feel that you're (kind of)
20034 satisfied. This will result in the new specs being byte-compiled, and
20035 you'll get top speed again. Note that T-gnus will not save these
20036 compiled specs in the @file{.newsrc.eld} file.
20039 @item gnus-compile-user-specs
20040 @vindex gnus-compile-user-specs
20041 If it is non-nil, the user-defined format specs will be byte-compiled
20042 automatically. The default value of this variable is @code{t}. It has
20043 an effect on the values of @code{gnus-*-line-format-spec}.
20048 @section Mode Lines
20051 @vindex gnus-updated-mode-lines
20052 @code{gnus-updated-mode-lines} says what buffers should keep their mode
20053 lines updated. It is a list of symbols. Supported symbols include
20054 @code{group}, @code{article}, @code{summary}, @code{server},
20055 @code{browse}, and @code{tree}. If the corresponding symbol is present,
20056 Gnus will keep that mode line updated with information that may be
20057 pertinent. If this variable is @code{nil}, screen refresh may be
20060 @cindex display-time
20062 @vindex gnus-mode-non-string-length
20063 By default, Gnus displays information on the current article in the mode
20064 lines of the summary and article buffers. The information Gnus wishes
20065 to display (e.g. the subject of the article) is often longer than the
20066 mode lines, and therefore have to be cut off at some point. The
20067 @code{gnus-mode-non-string-length} variable says how long the other
20068 elements on the line is (i.e., the non-info part). If you put
20069 additional elements on the mode line (e.g. a clock), you should modify
20072 @c Hook written by Francesco Potorti` <pot@cnuce.cnr.it>
20074 (add-hook 'display-time-hook
20075 (lambda () (setq gnus-mode-non-string-length
20077 (if line-number-mode 5 0)
20078 (if column-number-mode 4 0)
20079 (length display-time-string)))))
20082 If this variable is @code{nil} (which is the default), the mode line
20083 strings won't be chopped off, and they won't be padded either. Note
20084 that the default is unlikely to be desirable, as even the percentage
20085 complete in the buffer may be crowded off the mode line; the user should
20086 configure this variable appropriately for her configuration.
20089 @node Highlighting and Menus
20090 @section Highlighting and Menus
20092 @cindex highlighting
20095 @vindex gnus-visual
20096 The @code{gnus-visual} variable controls most of the Gnus-prettifying
20097 aspects. If @code{nil}, Gnus won't attempt to create menus or use fancy
20098 colors or fonts. This will also inhibit loading the @file{gnus-vis.el}
20101 This variable can be a list of visual properties that are enabled. The
20102 following elements are valid, and are all included by default:
20105 @item group-highlight
20106 Do highlights in the group buffer.
20107 @item summary-highlight
20108 Do highlights in the summary buffer.
20109 @item article-highlight
20110 Do highlights in the article buffer.
20112 Turn on highlighting in all buffers.
20114 Create menus in the group buffer.
20116 Create menus in the summary buffers.
20118 Create menus in the article buffer.
20120 Create menus in the browse buffer.
20122 Create menus in the server buffer.
20124 Create menus in the score buffers.
20126 Create menus in all buffers.
20129 So if you only want highlighting in the article buffer and menus in all
20130 buffers, you could say something like:
20133 (setq gnus-visual '(article-highlight menu))
20136 If you want highlighting only and no menus whatsoever, you'd say:
20139 (setq gnus-visual '(highlight))
20142 If @code{gnus-visual} is @code{t}, highlighting and menus will be used
20143 in all Gnus buffers.
20145 Other general variables that influence the look of all buffers include:
20148 @item gnus-mouse-face
20149 @vindex gnus-mouse-face
20150 This is the face (i.e., font) used for mouse highlighting in Gnus. No
20151 mouse highlights will be done if @code{gnus-visual} is @code{nil}.
20155 There are hooks associated with the creation of all the different menus:
20159 @item gnus-article-menu-hook
20160 @vindex gnus-article-menu-hook
20161 Hook called after creating the article mode menu.
20163 @item gnus-group-menu-hook
20164 @vindex gnus-group-menu-hook
20165 Hook called after creating the group mode menu.
20167 @item gnus-summary-menu-hook
20168 @vindex gnus-summary-menu-hook
20169 Hook called after creating the summary mode menu.
20171 @item gnus-server-menu-hook
20172 @vindex gnus-server-menu-hook
20173 Hook called after creating the server mode menu.
20175 @item gnus-browse-menu-hook
20176 @vindex gnus-browse-menu-hook
20177 Hook called after creating the browse mode menu.
20179 @item gnus-score-menu-hook
20180 @vindex gnus-score-menu-hook
20181 Hook called after creating the score mode menu.
20192 Those new-fangled @dfn{mouse} contraptions is very popular with the
20193 young, hep kids who don't want to learn the proper way to do things
20194 these days. Why, I remember way back in the summer of '89, when I was
20195 using Emacs on a Tops 20 system. Three hundred users on one single
20196 machine, and every user was running Simula compilers. Bah!
20200 @vindex gnus-carpal
20201 Well, you can make Gnus display bufferfuls of buttons you can click to
20202 do anything by setting @code{gnus-carpal} to @code{t}. Pretty simple,
20203 really. Tell the chiropractor I sent you.
20208 @item gnus-carpal-mode-hook
20209 @vindex gnus-carpal-mode-hook
20210 Hook run in all carpal mode buffers.
20212 @item gnus-carpal-button-face
20213 @vindex gnus-carpal-button-face
20214 Face used on buttons.
20216 @item gnus-carpal-header-face
20217 @vindex gnus-carpal-header-face
20218 Face used on carpal buffer headers.
20220 @item gnus-carpal-group-buffer-buttons
20221 @vindex gnus-carpal-group-buffer-buttons
20222 Buttons in the group buffer.
20224 @item gnus-carpal-summary-buffer-buttons
20225 @vindex gnus-carpal-summary-buffer-buttons
20226 Buttons in the summary buffer.
20228 @item gnus-carpal-server-buffer-buttons
20229 @vindex gnus-carpal-server-buffer-buttons
20230 Buttons in the server buffer.
20232 @item gnus-carpal-browse-buffer-buttons
20233 @vindex gnus-carpal-browse-buffer-buttons
20234 Buttons in the browse buffer.
20237 All the @code{buttons} variables are lists. The elements in these list
20238 are either cons cells where the @code{car} contains a text to be displayed and
20239 the @code{cdr} contains a function symbol, or a simple string.
20247 Gnus, being larger than any program ever written (allegedly), does lots
20248 of strange stuff that you may wish to have done while you're not
20249 present. For instance, you may want it to check for new mail once in a
20250 while. Or you may want it to close down all connections to all servers
20251 when you leave Emacs idle. And stuff like that.
20253 Gnus will let you do stuff like that by defining various
20254 @dfn{handlers}. Each handler consists of three elements: A
20255 @var{function}, a @var{time}, and an @var{idle} parameter.
20257 Here's an example of a handler that closes connections when Emacs has
20258 been idle for thirty minutes:
20261 (gnus-demon-close-connections nil 30)
20264 Here's a handler that scans for PGP headers every hour when Emacs is
20268 (gnus-demon-scan-pgp 60 t)
20271 This @var{time} parameter and than @var{idle} parameter work together
20272 in a strange, but wonderful fashion. Basically, if @var{idle} is
20273 @code{nil}, then the function will be called every @var{time} minutes.
20275 If @var{idle} is @code{t}, then the function will be called after
20276 @var{time} minutes only if Emacs is idle. So if Emacs is never idle,
20277 the function will never be called. But once Emacs goes idle, the
20278 function will be called every @var{time} minutes.
20280 If @var{idle} is a number and @var{time} is a number, the function will
20281 be called every @var{time} minutes only when Emacs has been idle for
20282 @var{idle} minutes.
20284 If @var{idle} is a number and @var{time} is @code{nil}, the function
20285 will be called once every time Emacs has been idle for @var{idle}
20288 And if @var{time} is a string, it should look like @samp{07:31}, and
20289 the function will then be called once every day somewhere near that
20290 time. Modified by the @var{idle} parameter, of course.
20292 @vindex gnus-demon-timestep
20293 (When I say ``minute'' here, I really mean @code{gnus-demon-timestep}
20294 seconds. This is 60 by default. If you change that variable,
20295 all the timings in the handlers will be affected.)
20297 So, if you want to add a handler, you could put something like this in
20298 your @file{.gnus.el} file:
20300 @findex gnus-demon-add-handler
20302 (gnus-demon-add-handler 'gnus-demon-close-connections 30 t)
20305 @findex gnus-demon-add-nocem
20306 @findex gnus-demon-add-scanmail
20307 @findex gnus-demon-add-rescan
20308 @findex gnus-demon-add-scan-timestamps
20309 @findex gnus-demon-add-disconnection
20310 Some ready-made functions to do this have been created:
20311 @code{gnus-demon-add-nocem}, @code{gnus-demon-add-disconnection},
20312 @code{gnus-demon-add-nntp-close-connection},
20313 @code{gnus-demon-add-scan-timestamps}, @code{gnus-demon-add-rescan}, and
20314 @code{gnus-demon-add-scanmail}. Just put those functions in your
20315 @file{.gnus.el} if you want those abilities.
20317 @findex gnus-demon-init
20318 @findex gnus-demon-cancel
20319 @vindex gnus-demon-handlers
20320 If you add handlers to @code{gnus-demon-handlers} directly, you should
20321 run @code{gnus-demon-init} to make the changes take hold. To cancel all
20322 daemons, you can use the @code{gnus-demon-cancel} function.
20324 Note that adding daemons can be pretty naughty if you over do it. Adding
20325 functions that scan all news and mail from all servers every two seconds
20326 is a sure-fire way of getting booted off any respectable system. So
20335 @dfn{Spamming} is posting the same article lots and lots of times.
20336 Spamming is bad. Spamming is evil.
20338 Spamming is usually canceled within a day or so by various anti-spamming
20339 agencies. These agencies usually also send out @dfn{NoCeM} messages.
20340 NoCeM is pronounced ``no see-'em'', and means what the name
20341 implies---these are messages that make the offending articles, like, go
20344 What use are these NoCeM messages if the articles are canceled anyway?
20345 Some sites do not honor cancel messages and some sites just honor cancels
20346 from a select few people. Then you may wish to make use of the NoCeM
20347 messages, which are distributed in the @samp{alt.nocem.misc} newsgroup.
20349 Gnus can read and parse the messages in this group automatically, and
20350 this will make spam disappear.
20352 There are some variables to customize, of course:
20355 @item gnus-use-nocem
20356 @vindex gnus-use-nocem
20357 Set this variable to @code{t} to set the ball rolling. It is @code{nil}
20360 @item gnus-nocem-groups
20361 @vindex gnus-nocem-groups
20362 Gnus will look for NoCeM messages in the groups in this list. The
20363 default is @code{("news.lists.filters" "news.admin.net-abuse.bulletins"
20364 "alt.nocem.misc" "news.admin.net-abuse.announce")}.
20366 @item gnus-nocem-issuers
20367 @vindex gnus-nocem-issuers
20368 There are many people issuing NoCeM messages. This list says what
20369 people you want to listen to. The default is @code{("Automoose-1"
20370 "clewis@@ferret.ocunix.on.ca" "cosmo.roadkill" "SpamHippo"
20371 "hweede@@snafu.de")}; fine, upstanding citizens all of them.
20373 Known despammers that you can put in this list are listed at
20374 @uref{http://www.xs4all.nl/~rosalind/nocemreg/nocemreg.html}.
20376 You do not have to heed NoCeM messages from all these people---just the
20377 ones you want to listen to. You also don't have to accept all NoCeM
20378 messages from the people you like. Each NoCeM message has a @dfn{type}
20379 header that gives the message a (more or less, usually less) rigorous
20380 definition. Common types are @samp{spam}, @samp{spew}, @samp{mmf},
20381 @samp{binary}, and @samp{troll}. To specify this, you have to use
20382 @code{(@var{issuer} @var{conditions} @dots{})} elements in the list.
20383 Each condition is either a string (which is a regexp that matches types
20384 you want to use) or a list on the form @code{(not @var{string})}, where
20385 @var{string} is a regexp that matches types you don't want to use.
20387 For instance, if you want all NoCeM messages from Chris Lewis except his
20388 @samp{troll} messages, you'd say:
20391 ("clewis@@ferret.ocunix.on.ca" ".*" (not "troll"))
20394 On the other hand, if you just want nothing but his @samp{spam} and
20395 @samp{spew} messages, you'd say:
20398 ("clewis@@ferret.ocunix.on.ca" (not ".*") "spew" "spam")
20401 The specs are applied left-to-right.
20404 @item gnus-nocem-verifyer
20405 @vindex gnus-nocem-verifyer
20407 This should be a function for verifying that the NoCeM issuer is who she
20408 says she is. The default is @code{mc-verify}, which is a Mailcrypt
20409 function. If this is too slow and you don't care for verification
20410 (which may be dangerous), you can set this variable to @code{nil}.
20412 If you want signed NoCeM messages to be verified and unsigned messages
20413 not to be verified (but used anyway), you could do something like:
20416 (setq gnus-nocem-verifyer 'my-gnus-mc-verify)
20418 (defun my-gnus-mc-verify ()
20426 This might be dangerous, though.
20428 @item gnus-nocem-directory
20429 @vindex gnus-nocem-directory
20430 This is where Gnus will store its NoCeM cache files. The default is
20431 @file{~/News/NoCeM/}.
20433 @item gnus-nocem-expiry-wait
20434 @vindex gnus-nocem-expiry-wait
20435 The number of days before removing old NoCeM entries from the cache.
20436 The default is 15. If you make it shorter Gnus will be faster, but you
20437 might then see old spam.
20439 @item gnus-nocem-check-from
20440 @vindex gnus-nocem-check-from
20441 Non-@code{nil} means check for valid issuers in message bodies.
20442 Otherwise don't bother fetching articles unless their author matches a
20443 valid issuer; that is much faster if you are selective about the
20446 @item gnus-nocem-check-article-limit
20447 @vindex gnus-nocem-check-article-limit
20448 If non-@code{nil}, the maximum number of articles to check in any NoCeM
20449 group. NoCeM groups can be huge and very slow to process.
20453 Using NoCeM could potentially be a memory hog. If you have many living
20454 (i. e., subscribed or unsubscribed groups), your Emacs process will grow
20455 big. If this is a problem, you should kill off all (or most) of your
20456 unsubscribed groups (@pxref{Subscription Commands}).
20463 It is very useful to be able to undo actions one has done. In normal
20464 Emacs buffers, it's easy enough---you just push the @code{undo} button.
20465 In Gnus buffers, however, it isn't that simple.
20467 The things Gnus displays in its buffer is of no value whatsoever to
20468 Gnus---it's all just data designed to look nice to the user.
20469 Killing a group in the group buffer with @kbd{C-k} makes the line
20470 disappear, but that's just a side-effect of the real action---the
20471 removal of the group in question from the internal Gnus structures.
20472 Undoing something like that can't be done by the normal Emacs
20473 @code{undo} function.
20475 Gnus tries to remedy this somewhat by keeping track of what the user
20476 does and coming up with actions that would reverse the actions the user
20477 takes. When the user then presses the @code{undo} key, Gnus will run
20478 the code to reverse the previous action, or the previous actions.
20479 However, not all actions are easily reversible, so Gnus currently offers
20480 a few key functions to be undoable. These include killing groups,
20481 yanking groups, and changing the list of read articles of groups.
20482 That's it, really. More functions may be added in the future, but each
20483 added function means an increase in data to be stored, so Gnus will
20484 never be totally undoable.
20486 @findex gnus-undo-mode
20487 @vindex gnus-use-undo
20489 The undoability is provided by the @code{gnus-undo-mode} minor mode. It
20490 is used if @code{gnus-use-undo} is non-@code{nil}, which is the
20491 default. The @kbd{C-M-_} key performs the @code{gnus-undo}
20492 command, which should feel kinda like the normal Emacs @code{undo}
20496 @node Predicate Specifiers
20497 @section Predicate Specifiers
20498 @cindex predicate specifiers
20500 Some Gnus variables are @dfn{predicate specifiers}. This is a special
20501 form that allows flexible specification of predicates without having
20502 to type all that much.
20504 These specifiers are lists consisting of functions, symbols and lists.
20509 (or gnus-article-unseen-p
20510 gnus-article-unread-p)
20513 The available symbols are @code{or}, @code{and} and @code{not}. The
20514 functions all take one parameter.
20516 @findex gnus-make-predicate
20517 Internally, Gnus calls @code{gnus-make-predicate} on these specifiers
20518 to create a function that can be called. This input parameter to this
20519 function will be passed along to all the functions in the predicate
20524 @section Moderation
20527 If you are a moderator, you can use the @file{gnus-mdrtn.el} package.
20528 It is not included in the standard Gnus package. Write a mail to
20529 @samp{larsi@@gnus.org} and state what group you moderate, and you'll
20532 The moderation package is implemented as a minor mode for summary
20536 (add-hook 'gnus-summary-mode-hook 'gnus-moderate)
20539 in your @file{.gnus.el} file.
20541 If you are the moderator of @samp{rec.zoofle}, this is how it's
20546 You split your incoming mail by matching on
20547 @samp{Newsgroups:.*rec.zoofle}, which will put all the to-be-posted
20548 articles in some mail group---for instance, @samp{nnml:rec.zoofle}.
20551 You enter that group once in a while and post articles using the @kbd{e}
20552 (edit-and-post) or @kbd{s} (just send unedited) commands.
20555 If, while reading the @samp{rec.zoofle} newsgroup, you happen upon some
20556 articles that weren't approved by you, you can cancel them with the
20560 To use moderation mode in these two groups, say:
20563 (setq gnus-moderated-list
20564 "^nnml:rec.zoofle$\\|^rec.zoofle$")
20568 @node Image Enhancements
20569 @section Image Enhancements
20571 XEmacs, as well as Emacs 21, is able to display pictures and stuff, so
20572 Gnus has taken advantage of that.
20575 * Picons:: How to display pictures of what you're reading.
20576 * Smileys:: Show all those happy faces the way they were meant to be shown.
20577 * X-Face:: Display a funky, teensy black-and-white image.
20578 * Toolbar:: Click'n'drool.
20579 * XVarious:: Other XEmacsy Gnusey variables.
20592 So@dots{} You want to slow down your news reader even more! This is a
20593 good way to do so. Its also a great way to impress people staring
20594 over your shoulder as you read news.
20597 * Picon Basics:: What are picons and How do I get them.
20598 * Picon Requirements:: Don't go further if you aren't using XEmacs.
20599 * Easy Picons:: Displaying Picons---the easy way.
20600 * Hard Picons:: The way you should do it. You'll learn something.
20601 * Picon Useless Configuration:: Other variables you can trash/tweak/munge/play with.
20606 @subsubsection Picon Basics
20608 What are Picons? To quote directly from the Picons Web site:
20617 @dfn{Picons} is short for ``personal icons''. They're small,
20618 constrained images used to represent users and domains on the net,
20619 organized into databases so that the appropriate image for a given
20620 e-mail address can be found. Besides users and domains, there are picon
20621 databases for Usenet newsgroups and weather forecasts. The picons are
20622 in either monochrome @code{XBM} format or color @code{XPM} and
20623 @code{GIF} formats.
20626 @vindex gnus-picons-piconsearch-url
20627 If you have a permanent connection to the Internet you can use Steve
20628 Kinzler's Picons Search engine by setting
20629 @code{gnus-picons-piconsearch-url} to the string @*
20630 @uref{http://www.cs.indiana.edu/picons/search.html}.
20632 @vindex gnus-picons-database
20633 Otherwise you need a local copy of his database. For instructions on
20634 obtaining and installing the picons databases, point your Web browser at @*
20635 @uref{http://www.cs.indiana.edu/picons/ftp/index.html}. Gnus expects
20636 picons to be installed into a location pointed to by
20637 @code{gnus-picons-database}.
20639 If you are using Debian GNU/Linux, saying @samp{apt-get install
20640 picons.*} will install the picons where Gnus can find them.
20643 @node Picon Requirements
20644 @subsubsection Picon Requirements
20646 To have Gnus display Picons for you, you must have @code{x} support
20647 compiled into XEmacs. To display color picons which are much nicer
20648 than the black & white one, you also need one of @code{xpm} or
20649 @code{gif} compiled into XEmacs.
20651 @vindex gnus-picons-convert-x-face
20652 If you want to display faces from @code{X-Face} headers, you should have
20653 the @code{xface} support compiled into XEmacs. Otherwise you must have
20654 the @code{netpbm} utilities installed, or munge the
20655 @code{gnus-picons-convert-x-face} variable to use something else.
20656 (NOTE: @code{x-face} is used in the variable name, not @code{xface})
20659 @subsubsection Easy Picons
20661 To enable displaying picons, simply put the following line in your
20662 @file{~/.gnus} file and start Gnus.
20665 (setq gnus-use-picons t)
20666 (setq gnus-treat-display-picons t)
20669 and make sure @code{gnus-picons-database} points to the directory
20670 containing the Picons databases.
20672 Alternatively if you want to use the web piconsearch engine add this:
20675 (setq gnus-picons-piconsearch-url
20676 "http://www.cs.indiana.edu:800/piconsearch")
20681 @subsubsection Hard Picons
20689 Gnus can display picons for you as you enter and leave groups and
20690 articles. It knows how to interact with three sections of the picons
20691 database. Namely, it can display the picons newsgroup pictures,
20692 author's face picture(s), and the authors domain. To enable this
20693 feature, you need to select where to get the picons from, and where to
20698 @item gnus-picons-database
20699 @vindex gnus-picons-database
20700 The location of the picons database. Should point to a directory
20701 containing the @file{news}, @file{domains}, @file{users} (and so on)
20702 subdirectories. This is only useful if
20703 @code{gnus-picons-piconsearch-url} is @code{nil}. Defaults to
20704 @file{/usr/local/faces/}.
20706 @item gnus-picons-piconsearch-url
20707 @vindex gnus-picons-piconsearch-url
20708 The URL for the web picons search engine. The only currently known
20709 engine is @uref{http://www.cs.indiana.edu:800/piconsearch}. To
20710 workaround network delays, icons will be fetched in the background. If
20711 this is @code{nil} 'the default), then picons are fetched from local
20712 database indicated by @code{gnus-picons-database}.
20714 @item gnus-picons-display-where
20715 @vindex gnus-picons-display-where
20716 Where the picon images should be displayed. It is @code{picons} by
20717 default (which by default maps to the buffer @samp{*Picons*}). Other
20718 valid places could be @code{article}, @code{summary}, or
20719 @samp{*scratch*} for all I care. Just make sure that you've made the
20720 buffer visible using the standard Gnus window configuration
20721 routines---@pxref{Window Layout}.
20723 @item gnus-picons-group-excluded-groups
20724 @vindex gnus-picons-group-excluded-groups
20725 Groups that are matched by this regexp won't have their group icons
20730 Note: If you set @code{gnus-use-picons} to @code{t}, it will set up your
20731 window configuration for you to include the @code{picons} buffer.
20733 Now that you've made those decision, you need to add the following
20734 functions to the appropriate hooks so these pictures will get displayed
20737 @vindex gnus-picons-display-where
20739 @item gnus-article-display-picons
20740 @findex gnus-article-display-picons
20741 Looks up and displays the picons for the author and the author's domain
20742 in the @code{gnus-picons-display-where} buffer.
20744 @item gnus-picons-article-display-x-face
20745 @findex gnus-picons-article-display-x-face
20746 Decodes and displays the X-Face header if present.
20747 (NOTE: @code{x-face} is used in the function name, not @code{xface})
20753 @node Picon Useless Configuration
20754 @subsubsection Picon Useless Configuration
20762 The following variables offer further control over how things are
20763 done, where things are located, and other useless stuff you really
20764 don't need to worry about.
20768 @item gnus-picons-news-directories
20769 @vindex gnus-picons-news-directories
20770 List of subdirectories to search in @code{gnus-picons-database} for
20771 newsgroups faces. @code{("news")} is the default.
20773 @item gnus-picons-user-directories
20774 @vindex gnus-picons-user-directories
20775 List of subdirectories to search in @code{gnus-picons-database} for user
20776 faces. @code{("local" "users" "usenix" "misc")} is the default.
20778 @item gnus-picons-domain-directories
20779 @vindex gnus-picons-domain-directories
20780 List of subdirectories to search in @code{gnus-picons-database} for
20781 domain name faces. Defaults to @code{("domains")}. Some people may
20782 want to add @samp{"unknown"} to this list.
20784 @item gnus-picons-convert-x-face
20785 @vindex gnus-picons-convert-x-face
20786 If you don't have @code{xface} support builtin XEmacs, this is the
20787 command to use to convert the @code{X-Face} header to an X bitmap
20788 (@code{xbm}). Defaults to @code{(format "@{ echo '/* Width=48,
20789 Height=48 */'; uncompface; @} | icontopbm | pbmtoxbm > %s"
20790 gnus-picons-x-face-file-name)}
20791 (NOTE: @code{x-face} is used in the variable name, not @code{xface})
20793 @item gnus-picons-x-face-file-name
20794 @vindex gnus-picons-x-face-file-name
20795 Names a temporary file to store the @code{X-Face} bitmap in. Defaults
20796 to @code{(format "/tmp/picon-xface.%s.xbm" (user-login-name))}.
20797 (NOTE: @code{x-face} is used in the variable name, not @code{xface})
20799 @item gnus-picons-has-modeline-p
20800 @vindex gnus-picons-has-modeline-p
20801 If you have set @code{gnus-picons-display-where} to @code{picons}, your
20802 XEmacs frame will become really cluttered. To alleviate this a bit you
20803 can set @code{gnus-picons-has-modeline-p} to @code{nil}; this will
20804 remove the mode line from the Picons buffer. This is only useful if
20805 @code{gnus-picons-display-where} is @code{picons}.
20807 @item gnus-picons-refresh-before-display
20808 @vindex gnus-picons-refresh-before-display
20809 If non-nil, display the article buffer before computing the picons.
20810 Defaults to @code{nil}.
20812 @item gnus-picons-display-as-address
20813 @vindex gnus-picons-display-as-address
20814 If @code{t} display textual email addresses along with pictures.
20815 Defaults to @code{t}.
20817 @item gnus-picons-file-suffixes
20818 @vindex gnus-picons-file-suffixes
20819 Ordered list of suffixes on picon file names to try. Defaults to
20820 @code{("xpm" "gif" "xbm")} minus those not builtin your XEmacs.
20822 @item gnus-picons-setup-hook
20823 @vindex gnus-picons-setup-hook
20824 Hook run in the picon buffer, if that is displayed.
20826 @item gnus-picons-display-article-move-p
20827 @vindex gnus-picons-display-article-move-p
20828 Whether to move point to first empty line when displaying picons. This
20829 has only an effect if `gnus-picons-display-where' has value `article'.
20831 If @code{nil}, display the picons in the @code{From} and
20832 @code{Newsgroups} lines. This is the default.
20834 @item gnus-picons-clear-cache-on-shutdown
20835 @vindex gnus-picons-clear-cache-on-shutdown
20836 Whether to clear the picons cache when exiting gnus. Gnus caches every
20837 picons it finds while it is running. This saves some time in the search
20838 process but eats some memory. If this variable is set to @code{nil},
20839 Gnus will never clear the cache itself; you will have to manually call
20840 @code{gnus-picons-clear-cache} to clear it. Otherwise the cache will be
20841 cleared every time you exit Gnus. Defaults to @code{t}.
20852 @subsection Smileys
20857 \gnusfig{-3cm}{0.5cm}{\epsfig{figure=ps/BigFace,height=20cm}}
20862 @dfn{Smiley} is a package separate from Gnus, but since Gnus is
20863 currently the only package that uses Smiley, it is documented here.
20865 In short---to use Smiley in Gnus, put the following in your
20866 @file{.gnus.el} file:
20869 (setq gnus-treat-display-smileys t)
20872 Smiley maps text smiley faces---@samp{:-)}, @samp{:-=}, @samp{:-(} and
20873 the like---to pictures and displays those instead of the text smiley
20874 faces. The conversion is controlled by a list of regexps that matches
20875 text and maps that to file names.
20877 @vindex smiley-nosey-regexp-alist
20878 @vindex smiley-deformed-regexp-alist
20879 Smiley supplies two example conversion alists by default:
20880 @code{smiley-deformed-regexp-alist} (which matches @samp{:)}, @samp{:(}
20881 and so on), and @code{smiley-nosey-regexp-alist} (which matches
20882 @samp{:-)}, @samp{:-(} and so on).
20884 The alist used is specified by the @code{smiley-regexp-alist} variable,
20885 which defaults to the value of @code{smiley-deformed-regexp-alist}.
20887 The first item in each element is the regexp to be matched; the second
20888 element is the regexp match group that is to be replaced by the picture;
20889 and the third element is the name of the file to be displayed.
20891 The following variables customize where Smiley will look for these
20892 files, as well as the color to be used and stuff:
20896 @item smiley-data-directory
20897 @vindex smiley-data-directory
20898 Where Smiley will look for smiley faces files.
20900 @item smiley-flesh-color
20901 @vindex smiley-flesh-color
20902 Skin color. The default is @samp{yellow}, which is really racist.
20904 @item smiley-features-color
20905 @vindex smiley-features-color
20906 Color of the features of the face. The default is @samp{black}.
20908 @item smiley-tongue-color
20909 @vindex smiley-tongue-color
20910 Color of the tongue. The default is @samp{red}.
20912 @item smiley-circle-color
20913 @vindex smiley-circle-color
20914 Color of the circle around the face. The default is @samp{black}.
20916 @item smiley-mouse-face
20917 @vindex smiley-mouse-face
20918 Face used for mouse highlighting over the smiley face.
20927 @code{X-Face} headers describe a 48x48 pixel black-and-white (1 bit
20928 depth) image that's supposed to represent the author of the message.
20929 It seems to be supported by an ever-growing number of mail and news
20933 @findex gnus-article-display-x-face
20934 @findex gnus-article-x-face-command
20935 @vindex gnus-article-x-face-command
20936 @vindex gnus-article-x-face-too-ugly
20944 Decoding an @code{X-Face} header either requires an Emacs that has
20945 @samp{compface} support (which most XEmacs versions has), or that you
20946 have @samp{compface} installed on your system. If either is true,
20947 Gnus will default to displaying @code{X-Face} headers.
20949 The variable that controls this is the
20950 @code{gnus-article-x-face-command} variable. If this variable is a
20951 string, this string will be executed in a sub-shell. If it is a
20952 function, this function will be called with the face as the argument.
20953 If the @code{gnus-article-x-face-too-ugly} (which is a regexp) matches
20954 the @code{From} header, the face will not be shown.
20956 The default action under Emacs 20 is to fork off the @code{display}
20957 program@footnote{@code{display} is from the ImageMagick package. For
20958 the @code{uncompface} and @code{icontopbm} programs look for a package
20959 like @code{compface} or @code{faces-xface} on a GNU/Linux system.} to
20962 Under XEmacs or Emacs 21+ with suitable image support, the default
20963 action is to display the face before the @code{From} header. (It's
20964 nicer if XEmacs has been compiled with @code{X-Face} support---that
20965 will make display somewhat faster. If there's no native @code{X-Face}
20966 support, Gnus will try to convert the @code{X-Face} header using
20967 external programs from the @code{pbmplus} package and
20968 friends.@footnote{On a GNU/Linux system look for packages with names
20969 like @code{netpbm}, @code{libgr-progs} and @code{compface}.})
20971 (NOTE: @code{x-face} is used in the variable/function names, not
20974 Gnus provides a few convenience functions and variables to allow
20975 easier insertion of X-Face headers in outgoing messages.
20977 @findex gnus-random-x-face
20978 @code{gnus-random-x-face} goes through all the @samp{pbm} files
20979 in @code{gnus-x-face-directory} and picks one at random, and then
20980 converts it to the X-Face format by using the
20981 @code{gnus-convert-pbm-to-x-face-command} shell command. The
20982 @samp{pbm} files should be 48x48 pixels big.
20984 @code{gnus-x-face-from-file} takes a GIF file as the parameter, and then
20985 converts the file to X-Face format by using the
20986 @code{gnus-convert-image-to-x-face-command} shell command.
20988 Here's how you would typically use the former function. Put something
20989 like the following in your @file{.gnus.el} file:
20992 (setq message-required-news-headers
20993 (nconc message-required-news-headers
20994 (list '(X-Face . gnus-random-x-face))))
20997 Using the latter function would be something like this:
21000 (setq message-required-news-headers
21001 (nconc message-required-news-headers
21002 (list '(X-Face . (lambda ()
21003 (gnus-x-face-from-file
21004 "~/My-face.gif"))))))
21009 @subsection Toolbar
21019 @item gnus-use-toolbar
21020 @vindex gnus-use-toolbar
21021 If @code{nil}, don't display toolbars. If non-@code{nil}, it should be
21022 one of @code{default-toolbar}, @code{top-toolbar}, @code{bottom-toolbar},
21023 @code{right-toolbar}, or @code{left-toolbar}.
21025 @item gnus-group-toolbar
21026 @vindex gnus-group-toolbar
21027 The toolbar in the group buffer.
21029 @item gnus-summary-toolbar
21030 @vindex gnus-summary-toolbar
21031 The toolbar in the summary buffer.
21033 @item gnus-summary-mail-toolbar
21034 @vindex gnus-summary-mail-toolbar
21035 The toolbar in the summary buffer of mail groups.
21041 @subsection Various XEmacs Variables
21044 @item gnus-xmas-glyph-directory
21045 @vindex gnus-xmas-glyph-directory
21046 This is where Gnus will look for pictures. Gnus will normally
21047 auto-detect this directory, but you may set it manually if you have an
21048 unusual directory structure.
21050 @item gnus-xmas-logo-color-alist
21051 @vindex gnus-xmas-logo-color-alist
21052 This is an alist where the key is a type symbol and the values are the
21053 foreground and background color of the splash page glyph.
21055 @item gnus-xmas-logo-color-style
21056 @vindex gnus-xmas-logo-color-style
21057 This is the key used to look up the color in the alist described above.
21058 Valid values include @code{flame}, @code{pine}, @code{moss},
21059 @code{irish}, @code{sky}, @code{tin}, @code{velvet}, @code{grape},
21060 @code{labia}, @code{berry}, @code{neutral}, and @code{september}.
21062 @item gnus-xmas-modeline-glyph
21063 @vindex gnus-xmas-modeline-glyph
21064 A glyph displayed in all Gnus mode lines. It is a tiny gnu head by
21078 @node Fuzzy Matching
21079 @section Fuzzy Matching
21080 @cindex fuzzy matching
21082 Gnus provides @dfn{fuzzy matching} of @code{Subject} lines when doing
21083 things like scoring, thread gathering and thread comparison.
21085 As opposed to regular expression matching, fuzzy matching is very fuzzy.
21086 It's so fuzzy that there's not even a definition of what @dfn{fuzziness}
21087 means, and the implementation has changed over time.
21089 Basically, it tries to remove all noise from lines before comparing.
21090 @samp{Re: }, parenthetical remarks, white space, and so on, are filtered
21091 out of the strings before comparing the results. This often leads to
21092 adequate results---even when faced with strings generated by text
21093 manglers masquerading as newsreaders.
21096 @node Thwarting Email Spam
21097 @section Thwarting Email Spam
21101 @cindex unsolicited commercial email
21103 In these last days of the Usenet, commercial vultures are hanging about
21104 and grepping through news like crazy to find email addresses they can
21105 foist off their scams and products to. As a reaction to this, many
21106 people have started putting nonsense addresses into their @code{From}
21107 lines. I think this is counterproductive---it makes it difficult for
21108 people to send you legitimate mail in response to things you write, as
21109 well as making it difficult to see who wrote what. This rewriting may
21110 perhaps be a bigger menace than the unsolicited commercial email itself
21113 The biggest problem I have with email spam is that it comes in under
21114 false pretenses. I press @kbd{g} and Gnus merrily informs me that I
21115 have 10 new emails. I say ``Golly gee! Happy is me!'' and select the
21116 mail group, only to find two pyramid schemes, seven advertisements
21117 (``New! Miracle tonic for growing full, lustrous hair on your toes!'')
21118 and one mail asking me to repent and find some god.
21120 This is annoying. Here's what you can do about it.
21123 * The problem of spam:: Some background, and some solutions
21124 * Anti-Spam Basics:: Simple steps to reduce the amount of spam.
21125 * SpamAssassin:: How to use external anti-spam tools.
21126 * Hashcash:: Reduce spam by burning CPU time.
21127 * Filtering Spam Using spam.el::
21128 * Filtering Spam Using Statistics (spam-stat.el)::
21131 @node The problem of spam
21132 @subsection The problem of spam
21134 @cindex spam filtering approaches
21135 @cindex filtering approaches, spam
21137 @cindex unsolicited commercial email
21139 First, some background on spam.
21141 If you have access to e-mail, you are familiar with spam (technically
21142 termed @acronym{UCE}, Unsolicited Commercial E-mail). Simply put, it exists
21143 because e-mail delivery is very cheap compared to paper mail, so only
21144 a very small percentage of people need to respond to an UCE to make it
21145 worthwhile to the advertiser. Ironically, one of the most common
21146 spams is the one offering a database of e-mail addresses for further
21147 spamming. Senders of spam are usually called @emph{spammers}, but terms like
21148 @emph{vermin}, @emph{scum}, and @emph{morons} are in common use as well.
21150 Spam comes from a wide variety of sources. It is simply impossible to
21151 dispose of all spam without discarding useful messages. A good
21152 example is the TMDA system, which requires senders
21153 unknown to you to confirm themselves as legitimate senders before
21154 their e-mail can reach you. Without getting into the technical side
21155 of TMDA, a downside is clearly that e-mail from legitimate sources may
21156 be discarded if those sources can't or won't confirm themselves
21157 through the TMDA system. Another problem with TMDA is that it
21158 requires its users to have a basic understanding of e-mail delivery
21161 The simplest approach to filtering spam is filtering. If you get 200
21162 spam messages per day from @email{random-address@@vmadmin.com}, you
21163 block @samp{vmadmin.com}. If you get 200 messages about
21164 @samp{VIAGRA}, you discard all messages with @samp{VIAGRA} in the
21165 message. This, unfortunately, is a great way to discard legitimate
21166 e-mail. For instance, the very informative and useful RISKS digest
21167 has been blocked by overzealous mail filters because it
21168 @strong{contained} words that were common in spam messages.
21169 Nevertheless, in isolated cases, with great care, direct filtering of
21170 mail can be useful.
21172 Another approach to filtering e-mail is the distributed spam
21173 processing, for instance DCC implements such a system. In essence,
21174 @code{N} systems around the world agree that a machine @samp{X} in
21175 China, Ghana, or California is sending out spam e-mail, and these
21176 @code{N} systems enter @samp{X} or the spam e-mail from @samp{X} into
21177 a database. The criteria for spam detection vary - it may be the
21178 number of messages sent, the content of the messages, and so on. When
21179 a user of the distributed processing system wants to find out if a
21180 message is spam, he consults one of those @code{N} systems.
21182 Distributed spam processing works very well against spammers that send
21183 a large number of messages at once, but it requires the user to set up
21184 fairly complicated checks. There are commercial and free distributed
21185 spam processing systems. Distributed spam processing has its risks as
21186 well. For instance legitimate e-mail senders have been accused of
21187 sending spam, and their web sites have been shut down for some time
21188 because of the incident.
21190 The statistical approach to spam filtering is also popular. It is
21191 based on a statistical analysis of previous spam messages. Usually
21192 the analysis is a simple word frequency count, with perhaps pairs of
21193 words or 3-word combinations thrown into the mix. Statistical
21194 analysis of spam works very well in most of the cases, but it can
21195 classify legitimate e-mail as spam in some cases. It takes time to
21196 run the analysis, the full message must be analyzed, and the user has
21197 to store the database of spam analyses.
21199 @node Anti-Spam Basics
21200 @subsection Anti-Spam Basics
21204 @cindex unsolicited commercial email
21206 One way of dealing with spam is having Gnus split out all spam into a
21207 @samp{spam} mail group (@pxref{Splitting Mail}).
21209 First, pick one (1) valid mail address that you can be reached at, and
21210 put it in your @code{From} header of all your news articles. (I've
21211 chosen @samp{larsi@@trym.ifi.uio.no}, but for many addresses on the form
21212 @samp{larsi+usenet@@ifi.uio.no} will be a better choice. Ask your
21213 sysadmin whether your sendmail installation accepts keywords in the local
21214 part of the mail address.)
21217 (setq message-default-news-headers
21218 "From: Lars Magne Ingebrigtsen <larsi@@trym.ifi.uio.no>\n")
21221 Then put the following split rule in @code{nnmail-split-fancy}
21222 (@pxref{Fancy Mail Splitting}):
21227 (to "larsi@@trym.ifi.uio.no"
21228 (| ("subject" "re:.*" "misc")
21229 ("references" ".*@@.*" "misc")
21235 This says that all mail to this address is suspect, but if it has a
21236 @code{Subject} that starts with a @samp{Re:} or has a @code{References}
21237 header, it's probably ok. All the rest goes to the @samp{spam} group.
21238 (This idea probably comes from Tim Pierce.)
21240 In addition, many mail spammers talk directly to your @sc{smtp} server
21241 and do not include your email address explicitly in the @code{To}
21242 header. Why they do this is unknown---perhaps it's to thwart this
21243 thwarting scheme? In any case, this is trivial to deal with---you just
21244 put anything not addressed to you in the @samp{spam} group by ending
21245 your fancy split rule in this way:
21250 (to "larsi" "misc")
21254 In my experience, this will sort virtually everything into the right
21255 group. You still have to check the @samp{spam} group from time to time to
21256 check for legitimate mail, though. If you feel like being a good net
21257 citizen, you can even send off complaints to the proper authorities on
21258 each unsolicited commercial email---at your leisure.
21260 If you are also a lazy net citizen, you will probably prefer complaining
21261 automatically with the @file{gnus-junk.el} package, available FOR FREE
21262 at @* @uref{http://stud2.tuwien.ac.at/~e9426626/gnus-junk.html}.
21263 Since most e-mail spam is sent automatically, this may reconcile the
21264 cosmic balance somewhat.
21266 This works for me. It allows people an easy way to contact me (they can
21267 just press @kbd{r} in the usual way), and I'm not bothered at all with
21268 spam. It's a win-win situation. Forging @code{From} headers to point
21269 to non-existent domains is yucky, in my opinion.
21274 @subsection SpamAssassin, Vipul's Razor, DCC, etc
21275 @cindex SpamAssassin
21276 @cindex Vipul's Razor
21279 The days where the hints in the previous section was sufficient in
21280 avoiding spam is coming to an end. There are many tools out there
21281 that claim to reduce the amount of spam you get. This section could
21282 easily become outdated fast, as new products replace old, but
21283 fortunately most of these tools seem to have similar interfaces. Even
21284 though this section will use SpamAssassin as an example, it should be
21285 easy to adapt it to most other tools.
21287 If the tool you are using is not installed on the mail server, you
21288 need to invoke it yourself. Ideas on how to use the
21289 @code{:postscript} mail source parameter (@pxref{Mail Source
21290 Specifiers}) follows.
21294 '((file :prescript "formail -bs spamassassin < /var/mail/%u")
21297 :postscript "mv %t /tmp/foo; formail -bs spamc < /tmp/foo > %t")))
21300 Once you managed to process your incoming spool somehow, thus making
21301 the mail contain e.g. a header indicating it is spam, you are ready to
21302 filter it out. Using normal split methods (@pxref{Splitting Mail}):
21305 (setq nnmail-split-methods '(("spam" "^X-Spam-Flag: YES")
21309 Or using fancy split methods (@pxref{Fancy Mail Splitting}):
21312 (setq nnmail-split-methods 'nnmail-split-fancy
21313 nnmail-split-fancy '(| ("X-Spam-Flag" "YES" "spam")
21317 Some people might not like the idea of piping the mail through various
21318 programs using a @code{:prescript} (if some program is buggy, you
21319 might lose all mail). If you are one of them, another solution is to
21320 call the external tools during splitting. Example fancy split method:
21323 (setq nnmail-split-fancy '(| (: kevin-spamassassin)
21325 (defun kevin-spamassassin ()
21327 (let ((buf (or (get-buffer " *nnmail incoming*")
21328 (get-buffer " *nnml move*"))))
21330 (progn (message "Oops, cannot find message buffer") nil)
21332 (if (eq 1 (call-process-region (point-min) (point-max)
21333 "spamc" nil nil nil "-c"))
21337 That is about it. As some spam is likely to get through anyway, you
21338 might want to have a nifty function to call when you happen to read
21339 spam. And here is the nifty function:
21342 (defun my-gnus-raze-spam ()
21343 "Submit SPAM to Vipul's Razor, then mark it as expirable."
21345 (gnus-summary-show-raw-article)
21346 (gnus-summary-save-in-pipe "razor-report -f -d")
21347 (gnus-summary-mark-as-expirable 1))
21351 @subsection Hashcash
21354 A novel technique to fight spam is to require senders to do something
21355 costly for each message they send. This has the obvious drawback that
21356 you cannot rely on that everyone in the world uses this technique,
21357 since it is not part of the Internet standards, but it may be useful
21358 in smaller communities.
21360 While the tools in the previous section work well in practice, they
21361 work only because the tools are constantly maintained and updated as
21362 new form of spam appears. This means that a small percentage of spam
21363 will always get through. It also means that somewhere, someone needs
21364 to read lots of spam to update these tools. Hashcash avoids that, but
21365 instead requires that everyone you communicate with supports the
21366 scheme. You can view the two approaches as pragmatic vs dogmatic.
21367 The approaches have their own advantages and disadvantages, but as
21368 often in the real world, a combination of them is stronger than either
21369 one of them separately.
21372 The ``something costly'' is to burn CPU time, more specifically to
21373 compute a hash collision up to a certain number of bits. The
21374 resulting hashcash cookie is inserted in a @samp{X-Hashcash:}
21375 header. For more details, and for the external application
21376 @code{hashcash} you need to install to use this feature, see
21377 @uref{http://www.cypherspace.org/~adam/hashcash/}. Even more
21378 information can be found at @uref{http://www.camram.org/}.
21380 If you wish to call hashcash for each message you send, say something
21384 (require 'hashcash)
21385 (add-hook 'message-send-hook 'mail-add-payment)
21388 The @code{hashcash.el} library can be found at
21389 @uref{http://users.actrix.gen.nz/mycroft/hashcash.el}, or in the Gnus
21390 development contrib directory.
21392 You will need to set up some additional variables as well:
21396 @item hashcash-default-payment
21397 @vindex hashcash-default-payment
21398 This variable indicates the default number of bits the hash collision
21399 should consist of. By default this is 0, meaning nothing will be
21400 done. Suggested useful values include 17 to 29.
21402 @item hashcash-payment-alist
21403 @vindex hashcash-payment-alist
21404 Some receivers may require you to spend burn more CPU time than the
21405 default. This variable contains a list of @samp{(ADDR AMOUNT)} cells,
21406 where ADDR is the receiver (email address or newsgroup) and AMOUNT is
21407 the number of bits in the collision that is needed. It can also
21408 contain @samp{(ADDR STRING AMOUNT)} cells, where the STRING is the
21409 string to use (normally the email address or newsgroup name is used).
21413 Where the @code{hashcash} binary is installed.
21417 Currently there is no built in functionality in Gnus to verify
21418 hashcash cookies, it is expected that this is performed by your hand
21419 customized mail filtering scripts. Improvements in this area would be
21420 a useful contribution, however.
21422 @node Filtering Spam Using spam.el
21423 @subsection Filtering Spam Using spam.el
21424 @cindex spam filtering
21427 The idea behind @code{spam.el} is to have a control center for spam detection
21428 and filtering in Gnus. To that end, @code{spam.el} does two things: it
21429 filters incoming mail, and it analyzes mail known to be spam or ham.
21430 @emph{Ham} is the name used throughout @code{spam.el} to indicate
21433 So, what happens when you load @code{spam.el}? First of all, you get
21434 the following keyboard commands:
21444 @findex gnus-summary-mark-as-spam
21445 @code{gnus-summary-mark-as-spam}.
21447 Mark current article as spam, showing it with the @samp{H} mark.
21448 Whenever you see a spam article, make sure to mark its summary line
21449 with @kbd{M-d} before leaving the group. This is done automatically
21450 for unread articles in @emph{spam} groups.
21456 @findex spam-bogofilter-score
21457 @code{spam-bogofilter-score}.
21459 You must have bogofilter processing enabled for that command to work
21466 Also, when you load @code{spam.el}, you will be able to customize its
21467 variables. Try @code{customize-group} on the @samp{spam} variable
21470 The concepts of ham processors and spam processors are very important.
21471 Ham processors and spam processors for a group can be set with the
21472 @code{spam-process} group parameter, or the
21473 @code{gnus-spam-process-newsgroups} variable. Ham processors take
21474 mail known to be non-spam (@emph{ham}) and process it in some way so
21475 that later similar mail will also be considered non-spam. Spam
21476 processors take mail known to be spam and process it so similar spam
21477 will be detected later.
21479 Gnus learns from the spam you get. You have to collect your spam in
21480 one or more spam groups, and set or customize the variable
21481 @code{spam-junk-mailgroups} as appropriate. You can also declare
21482 groups to contain spam by setting their group parameter
21483 @code{spam-contents} to @code{gnus-group-spam-classification-spam}, or
21484 by customizing the corresponding variable
21485 @code{gnus-spam-newsgroup-contents}. The @code{spam-contents} group
21486 parameter and the @code{gnus-spam-newsgroup-contents} variable can
21487 also be used to declare groups as @emph{ham} groups if you set their
21488 classification to @code{gnus-group-spam-classification-ham}. If
21489 groups are not classified by means of @code{spam-junk-mailgroups},
21490 @code{spam-contents}, or @code{gnus-spam-newsgroup-contents}, they are
21491 considered @emph{unclassified}. All groups are unclassified by
21494 In spam groups, all messages are considered to be spam by default:
21495 they get the @samp{H} mark when you enter the group. You must review
21496 these messages from time to time and remove the @samp{H} mark for
21497 every message that is not spam after all. To remove the @samp{H}
21498 mark, you can use @kbd{M-u} to "unread" the article, or @kbd{d} for
21499 declaring it read the non-spam way. When you leave a group, all
21500 spam-marked (@samp{H}) articles are sent to a spam processor which
21501 will study them as spam samples.
21503 Messages may also be deleted in various other ways, and unless
21504 @code{spam-ham-marks} gets overridden below, marks @samp{R} and
21505 @samp{r} for default read or explicit delete, marks @samp{X} and
21506 @samp{K} for automatic or explicit kills, as well as mark @samp{Y} for
21507 low scores, are all considered to be associated with articles which
21508 are not spam. This assumption might be false, in particular if you
21509 use kill files or score files as means for detecting genuine spam, you
21510 should then adjust the @code{spam-ham-marks} variable.
21512 @defvar spam-ham-marks
21513 You can customize this variable to be the list of marks you want to
21514 consider ham. By default, the list contains the deleted, read,
21515 killed, kill-filed, and low-score marks.
21518 @defvar spam-spam-marks
21519 You can customize this variable to be the list of marks you want to
21520 consider spam. By default, the list contains only the spam mark.
21523 When you leave @emph{any} group, regardless of its
21524 @code{spam-contents} classification, all spam-marked articles are sent
21525 to a spam processor, which will study these as spam samples. If you
21526 explicit kill a lot, you might sometimes end up with articles marked
21527 @samp{K} which you never saw, and which might accidentally contain
21528 spam. Best is to make sure that real spam is marked with @samp{H},
21531 When you leave a @emph{spam} group, all spam-marked articles are
21532 marked as expired after processing with the spam processor. This is
21533 not done for @emph{unclassified} or @emph{ham} groups. Also, any
21534 @strong{ham} articles in a spam group will be moved to a location
21535 determined by either the @code{ham-process-destination} group
21536 parameter or the @code{gnus-ham-process-destinations} variable. The
21537 location is a group name. If the @code{ham-process-destination}
21538 parameter is not set, spam articles are only expired.
21540 When you leave a @emph{ham} group, all ham-marked articles are sent to
21541 a ham processor, which will study these as non-spam samples.
21543 When you leave a @emph{ham} or @emph{unclassified} group, all
21544 @strong{spam} articles are moved to a location determined by either
21545 the @code{spam-process-destination} group parameter or the
21546 @code{gnus-spam-process-destinations} variable. The location is a
21547 group name. If the @code{spam-process-destination} parameter is not
21548 set, the spam articles are only expired.
21550 To use the @code{spam.el} facilities for incoming mail filtering, you
21551 must add the following to your fancy split list
21552 @code{nnmail-split-fancy} or @code{nnimap-split-fancy}:
21558 Note that the fancy split may be called @code{nnmail-split-fancy} or
21559 @code{nnimap-split-fancy}, depending on whether you use the nnmail or
21560 nnimap back ends to retrieve your mail.
21562 The @code{spam-split} function will process incoming mail and send the
21563 mail considered to be spam into the group name given by the variable
21564 @code{spam-split-group}. By default that group name is @samp{spam},
21565 but you can customize it.
21567 @emph{TODO: Currently, spam.el only supports insertion of articles
21568 into a backend. There is no way to tell spam.el that an article is no
21569 longer spam or ham.}
21571 @emph{TODO: spam.el needs to provide a uniform way of training all the
21572 statistical databases. Some have that functionality built-in, others
21575 The following are the methods you can use to control the behavior of
21576 @code{spam-split} and their corresponding spam and ham processors:
21579 * Blacklists and Whitelists::
21580 * BBDB Whitelists::
21583 * ifile spam filtering::
21584 * spam-stat spam filtering::
21585 * Extending spam.el::
21588 @node Blacklists and Whitelists
21589 @subsubsection Blacklists and Whitelists
21590 @cindex spam filtering
21591 @cindex whitelists, spam filtering
21592 @cindex blacklists, spam filtering
21595 @defvar spam-use-blacklist
21596 Set this variable to t if you want to use blacklists when splitting
21597 incoming mail. Messages whose senders are in the blacklist will be
21598 sent to the @code{spam-split-group}. This is an explicit filter,
21599 meaning that it acts only on mail senders @emph{declared} to be
21603 @defvar spam-use-whitelist
21604 Set this variable to t if you want to use whitelists when splitting
21605 incoming mail. Messages whose senders are not in the whitelist will
21606 be sent to the @code{spam-split-group}. This is an implicit filter,
21607 meaning it believes everyone to be a spammer unless told otherwise.
21611 @defvar gnus-group-spam-exit-processor-blacklist
21612 Add this symbol to a group's @code{spam-process} parameter by
21613 customizing the group parameters or the
21614 @code{gnus-spam-process-newsgroups} variable. When this symbol is
21615 added to a group's @code{spam-process} parameter, the senders of
21616 spam-marked articles will be added to the blacklist.
21619 @defvar gnus-group-ham-exit-processor-whitelist
21620 Add this symbol to a group's @code{spam-process} parameter by
21621 customizing the group parameters or the
21622 @code{gnus-spam-process-newsgroups} variable. When this symbol is
21623 added to a group's @code{spam-process} parameter, the senders of
21624 ham-marked articles in @emph{ham} groups will be added to the
21625 whitelist. Note that this ham processor has no effect in @emph{spam}
21626 or @emph{unclassified} groups.
21629 Blacklists are lists of regular expressions matching addresses you
21630 consider to be spam senders. For instance, to block mail from any
21631 sender at @samp{vmadmin.com}, you can put @samp{vmadmin.com} in your
21632 blacklist. You start out with an empty blacklist. Blacklist entries
21633 use the Emacs regular expression syntax.
21635 Conversely, whitelists tell Gnus what addresses are considered
21636 legitimate. All non-whitelisted addresses are considered spammers.
21637 This option is probably not useful for most Gnus users unless the
21638 whitelists is very comprehensive or permissive. Also see @ref{BBDB
21639 Whitelists}. Whitelist entries use the Emacs regular expression
21642 The blacklist and whitelist file locations can be customized with the
21643 @code{spam-directory} variable (@file{~/News/spam} by default), or
21644 the @code{spam-whitelist} and @code{spam-blacklist} variables
21645 directly. The whitelist and blacklist files will by default be in the
21646 @code{spam-directory} directory, named @file{whitelist} and
21647 @file{blacklist} respectively.
21649 @node BBDB Whitelists
21650 @subsubsection BBDB Whitelists
21651 @cindex spam filtering
21652 @cindex BBDB whitelists, spam filtering
21653 @cindex BBDB, spam filtering
21656 @defvar spam-use-BBDB
21658 Analogous to @code{spam-use-whitelist} (@pxref{Blacklists and
21659 Whitelists}), but uses the BBDB as the source of whitelisted addresses,
21660 without regular expressions. You must have the BBDB loaded for
21661 @code{spam-use-BBDB} to work properly. Only addresses in the BBDB
21662 will be allowed through; all others will be classified as spam.
21666 @defvar gnus-group-ham-exit-processor-BBDB
21667 Add this symbol to a group's @code{spam-process} parameter by
21668 customizing the group parameters or the
21669 @code{gnus-spam-process-newsgroups} variable. When this symbol is
21670 added to a group's @code{spam-process} parameter, the senders of
21671 ham-marked articles in @emph{ham} groups will be added to the
21672 BBDB. Note that this ham processor has no effect in @emph{spam}
21673 or @emph{unclassified} groups.
21677 @subsubsection Blackholes
21678 @cindex spam filtering
21679 @cindex blackholes, spam filtering
21682 @defvar spam-use-blackholes
21684 This option is disabled by default. You can let Gnus consult the
21685 blackhole-type distributed spam processing systems (DCC, for instance)
21686 when you set this option. The variable @code{spam-blackhole-servers}
21687 holds the list of blackhole servers Gnus will consult. The current
21688 list is fairly comprehensive, but make sure to let us know if it
21689 contains outdated servers.
21691 The blackhole check uses the @code{dig.el} package, but you can tell
21692 @code{spam.el} to use @code{dns.el} instead for better performance if
21693 you set @code{spam-use-dig} to nil. It is not recommended at this
21694 time to set @code{spam-use-dig} to nil despite the possible
21695 performance improvements, because some users may be unable to use it,
21696 but you can try it and see if it works for you.
21700 @defvar spam-blackhole-servers
21702 The list of servers to consult for blackhole checks.
21706 @defvar spam-use-dig
21708 Use the @code{dig.el} package instead of the @code{dns.el} package.
21709 The default setting of t is recommended.
21713 Blackhole checks are done only on incoming mail. There is no spam or
21714 ham processor for blackholes.
21717 @subsubsection Bogofilter
21718 @cindex spam filtering
21719 @cindex bogofilter, spam filtering
21722 @defvar spam-use-bogofilter
21724 Set this variable if you want @code{spam-split} to use Eric Raymond's
21725 speedy Bogofilter. This has been tested with a locally patched copy
21726 of version 0.4. Make sure to read the installation comments in
21729 With a minimum of care for associating the @samp{H} mark for spam
21730 articles only, Bogofilter training all gets fairly automatic. You
21731 should do this until you get a few hundreds of articles in each
21732 category, spam or not. The shell command @command{head -1
21733 ~/.bogofilter/*} shows both article counts. The command @kbd{S t} in
21734 summary mode, either for debugging or for curiosity, triggers
21735 Bogofilter into displaying in another buffer the @emph{spamicity}
21736 score of the current article (between 0.0 and 1.0), together with the
21737 article words which most significantly contribute to the score.
21739 If the @code{bogofilter} executable is not in your path, Bogofilter
21740 processing will be turned off.
21745 @defvar gnus-group-spam-exit-processor-bogofilter
21746 Add this symbol to a group's @code{spam-process} parameter by
21747 customizing the group parameters or the
21748 @code{gnus-spam-process-newsgroups} variable. When this symbol is
21749 added to a group's @code{spam-process} parameter, spam-marked articles
21750 will be added to the bogofilter spam database, and ham-marked articles
21751 will be added to the bogofilter ham database. @strong{Note that the
21752 Bogofilter spam processor is the only spam processor to also do ham
21756 @node ifile spam filtering
21757 @subsubsection ifile spam filtering
21758 @cindex spam filtering
21759 @cindex ifile, spam filtering
21762 @defvar spam-use-ifile
21764 Enable this variable if you want @code{spam-split} to use ifile, a
21765 statistical analyzer similar to Bogofilter.
21769 @defvar spam-ifile-all-categories
21771 Enable this variable if you want @code{spam-use-ifile} to give you all
21772 the ifile categories, not just spam/non-spam. If you use this, make
21773 sure you train ifile as described in its documentation.
21777 @defvar spam-ifile-spam-category
21779 This is the category of spam messages as far as ifile is concerned.
21780 The actual string used is irrelevant, but you probably want to leave
21781 the default value of @samp{spam}.
21784 @defvar spam-ifile-database-path
21786 This is the filename for the ifile database. It is not specified by
21787 default, so ifile will use its own default database name.
21791 The ifile mail classifier is similar to Bogofilter in intent and
21792 purpose. A ham and a spam processor are provided, plus the
21793 @code{spam-use-ifile} variable to indicate to spam-split that ifile
21794 should be used. The 1.2.1 version of ifile was used to test this
21797 @node spam-stat spam filtering
21798 @subsubsection spam-stat spam filtering
21799 @cindex spam filtering
21800 @cindex spam-stat, spam filtering
21801 @cindex spam-stat.el
21804 @xref{Filtering Spam Using Statistics (spam-stat.el)}.
21806 @defvar spam-use-stat
21808 Enable this variable if you want @code{spam-split} to use
21809 spam-stat.el, an Emacs Lisp statistical analyzer.
21813 @defvar gnus-group-spam-exit-processor-stat
21814 Add this symbol to a group's @code{spam-process} parameter by
21815 customizing the group parameters or the
21816 @code{gnus-spam-process-newsgroups} variable. When this symbol is
21817 added to a group's @code{spam-process} parameter, the spam-marked
21818 articles will be added to the spam-stat database of spam messages.
21821 @defvar gnus-group-ham-exit-processor-stat
21822 Add this symbol to a group's @code{spam-process} parameter by
21823 customizing the group parameters or the
21824 @code{gnus-spam-process-newsgroups} variable. When this symbol is
21825 added to a group's @code{spam-process} parameter, the ham-marked
21826 articles in @emph{ham} groups will be added to the spam-stat database
21827 of non-spam messages. Note that this ham processor has no effect in
21828 @emph{spam} or @emph{unclassified} groups.
21831 This enables spam.el to cooperate with spam-stat.el. spam-stat.el
21832 provides an internal (Lisp-only) spam database, which unlike ifile or
21833 Bogofilter does not require external programs. A spam and a ham
21834 processor, and the @code{spam-use-stat} variable for @code{spam-split}
21837 @node Extending spam.el
21838 @subsubsection Extending spam.el
21839 @cindex spam filtering
21840 @cindex spam.el, extending
21841 @cindex extending spam.el
21843 Say you want to add a new back end called blackbox. For filtering
21844 incoming mail, provide the following:
21852 (defvar spam-use-blackbox nil
21853 "True if blackbox should be used.")
21858 (spam-use-blackbox . spam-check-blackbox)
21860 to @code{spam-list-of-checks}.
21865 Write the @code{spam-check-blackbox} function. It should return
21866 @samp{nil} or @code{spam-split-group}. See the existing
21867 @code{spam-check-*} functions for examples of what you can do.
21870 For processing spam and ham messages, provide the following:
21877 Note you don't have to provide a spam or a ham processor. Only
21878 provide them if Blackbox supports spam or ham processing.
21881 (defvar gnus-group-spam-exit-processor-blackbox "blackbox"
21882 "The Blackbox summary exit spam processor.
21883 Only applicable to spam groups.")
21885 (defvar gnus-group-ham-exit-processor-blackbox "blackbox"
21886 "The whitelist summary exit ham processor.
21887 Only applicable to non-spam (unclassified and ham) groups.")
21895 (defun spam-blackbox-register-spam-routine ()
21896 (spam-generic-register-routine
21897 ;; the spam function
21899 (let ((from (spam-fetch-field-from-fast article)))
21900 (when (stringp from)
21901 (blackbox-do-something-with-this-spammer from))))
21902 ;; the ham function
21905 (defun spam-blackbox-register-ham-routine ()
21906 (spam-generic-register-routine
21907 ;; the spam function
21909 ;; the ham function
21911 (let ((from (spam-fetch-field-from-fast article)))
21912 (when (stringp from)
21913 (blackbox-do-something-with-this-ham-sender from))))))
21916 Write the @code{blackbox-do-something-with-this-ham-sender} and
21917 @code{blackbox-do-something-with-this-spammer} functions. You can add
21918 more complex code than fetching the message sender, but keep in mind
21919 that retrieving the whole message takes significantly longer than the
21920 sender through @code{spam-fetch-field-from-fast}, because the message
21921 senders are kept in memory by Gnus.
21926 @node Filtering Spam Using Statistics (spam-stat.el)
21927 @subsection Filtering Spam Using Statistics (spam-stat.el)
21928 @cindex Paul Graham
21929 @cindex Graham, Paul
21930 @cindex naive Bayesian spam filtering
21931 @cindex Bayesian spam filtering, naive
21932 @cindex spam filtering, naive Bayesian
21934 Paul Graham has written an excellent essay about spam filtering using
21935 statistics: @uref{http://www.paulgraham.com/spam.html,A Plan for
21936 Spam}. In it he describes the inherent deficiency of rule-based
21937 filtering as used by SpamAssassin, for example: Somebody has to write
21938 the rules, and everybody else has to install these rules. You are
21939 always late. It would be much better, he argues, to filter mail based
21940 on whether it somehow resembles spam or non-spam. One way to measure
21941 this is word distribution. He then goes on to describe a solution
21942 that checks whether a new mail resembles any of your other spam mails
21945 The basic idea is this: Create a two collections of your mail, one
21946 with spam, one with non-spam. Count how often each word appears in
21947 either collection, weight this by the total number of mails in the
21948 collections, and store this information in a dictionary. For every
21949 word in a new mail, determine its probability to belong to a spam or a
21950 non-spam mail. Use the 15 most conspicuous words, compute the total
21951 probability of the mail being spam. If this probability is higher
21952 than a certain threshold, the mail is considered to be spam.
21954 Gnus supports this kind of filtering. But it needs some setting up.
21955 First, you need two collections of your mail, one with spam, one with
21956 non-spam. Then you need to create a dictionary using these two
21957 collections, and save it. And last but not least, you need to use
21958 this dictionary in your fancy mail splitting rules.
21961 * Creating a spam-stat dictionary::
21962 * Splitting mail using spam-stat::
21963 * Low-level interface to the spam-stat dictionary::
21966 @node Creating a spam-stat dictionary
21967 @subsubsection Creating a spam-stat dictionary
21969 Before you can begin to filter spam based on statistics, you must
21970 create these statistics based on two mail collections, one with spam,
21971 one with non-spam. These statistics are then stored in a dictionary
21972 for later use. In order for these statistics to be meaningful, you
21973 need several hundred emails in both collections.
21975 Gnus currently supports only the nnml back end for automated dictionary
21976 creation. The nnml back end stores all mails in a directory, one file
21977 per mail. Use the following:
21979 @defun spam-stat-process-spam-directory
21980 Create spam statistics for every file in this directory. Every file
21981 is treated as one spam mail.
21984 @defun spam-stat-process-non-spam-directory
21985 Create non-spam statistics for every file in this directory. Every
21986 file is treated as one non-spam mail.
21989 Usually you would call @code{spam-stat-process-spam-directory} on a
21990 directory such as @file{~/Mail/mail/spam} (this usually corresponds
21991 the the group @samp{nnml:mail.spam}), and you would call
21992 @code{spam-stat-process-non-spam-directory} on a directory such as
21993 @file{~/Mail/mail/misc} (this usually corresponds the the group
21994 @samp{nnml:mail.misc}).
21996 When you are using IMAP, you won't have the mails available locally,
21997 so that will not work. One solution is to use the Gnus Agent to cache
21998 the articles. Then you can use directories such as
21999 @file{"~/News/agent/nnimap/mail.yourisp.com/personal_spam"} for
22000 @code{spam-stat-process-spam-directory}. @xref{Agent as Cache}.
22003 This variable holds the hash-table with all the statistics -- the
22004 dictionary we have been talking about. For every word in either
22005 collection, this hash-table stores a vector describing how often the
22006 word appeared in spam and often it appeared in non-spam mails.
22009 If you want to regenerate the statistics from scratch, you need to
22010 reset the dictionary.
22012 @defun spam-stat-reset
22013 Reset the @code{spam-stat} hash-table, deleting all the statistics.
22016 When you are done, you must save the dictionary. The dictionary may
22017 be rather large. If you will not update the dictionary incrementally
22018 (instead, you will recreate it once a month, for example), then you
22019 can reduce the size of the dictionary by deleting all words that did
22020 not appear often enough or that do not clearly belong to only spam or
22021 only non-spam mails.
22023 @defun spam-stat-reduce-size
22024 Reduce the size of the dictionary. Use this only if you do not want
22025 to update the dictionary incrementally.
22028 @defun spam-stat-save
22029 Save the dictionary.
22032 @defvar spam-stat-file
22033 The filename used to store the dictionary. This defaults to
22034 @file{~/.spam-stat.el}.
22037 @node Splitting mail using spam-stat
22038 @subsubsection Splitting mail using spam-stat
22040 In order to use @code{spam-stat} to split your mail, you need to add the
22041 following to your @file{~/.gnus} file:
22044 (require 'spam-stat)
22048 This will load the necessary Gnus code, and the dictionary you
22051 Next, you need to adapt your fancy splitting rules: You need to
22052 determine how to use @code{spam-stat}. The following examples are for
22053 the nnml back end. Using the nnimap back end works just as well. Just
22054 use @code{nnimap-split-fancy} instead of @code{nnmail-split-fancy}.
22056 In the simplest case, you only have two groups, @samp{mail.misc} and
22057 @samp{mail.spam}. The following expression says that mail is either
22058 spam or it should go into @samp{mail.misc}. If it is spam, then
22059 @code{spam-stat-split-fancy} will return @samp{mail.spam}.
22062 (setq nnmail-split-fancy
22063 `(| (: spam-stat-split-fancy)
22067 @defvar spam-stat-split-fancy-spam-group
22068 The group to use for spam. Default is @samp{mail.spam}.
22071 If you also filter mail with specific subjects into other groups, use
22072 the following expression. Only mails not matching the regular
22073 expression are considered potential spam.
22076 (setq nnmail-split-fancy
22077 `(| ("Subject" "\\bspam-stat\\b" "mail.emacs")
22078 (: spam-stat-split-fancy)
22082 If you want to filter for spam first, then you must be careful when
22083 creating the dictionary. Note that @code{spam-stat-split-fancy} must
22084 consider both mails in @samp{mail.emacs} and in @samp{mail.misc} as
22085 non-spam, therefore both should be in your collection of non-spam
22086 mails, when creating the dictionary!
22089 (setq nnmail-split-fancy
22090 `(| (: spam-stat-split-fancy)
22091 ("Subject" "\\bspam-stat\\b" "mail.emacs")
22095 You can combine this with traditional filtering. Here, we move all
22096 HTML-only mails into the @samp{mail.spam.filtered} group. Note that since
22097 @code{spam-stat-split-fancy} will never see them, the mails in
22098 @samp{mail.spam.filtered} should be neither in your collection of spam mails,
22099 nor in your collection of non-spam mails, when creating the
22103 (setq nnmail-split-fancy
22104 `(| ("Content-Type" "text/html" "mail.spam.filtered")
22105 (: spam-stat-split-fancy)
22106 ("Subject" "\\bspam-stat\\b" "mail.emacs")
22111 @node Low-level interface to the spam-stat dictionary
22112 @subsubsection Low-level interface to the spam-stat dictionary
22114 The main interface to using @code{spam-stat}, are the following functions:
22116 @defun spam-stat-buffer-is-spam
22117 Called in a buffer, that buffer is considered to be a new spam mail.
22118 Use this for new mail that has not been processed before.
22121 @defun spam-stat-buffer-is-no-spam
22122 Called in a buffer, that buffer is considered to be a new non-spam
22123 mail. Use this for new mail that has not been processed before.
22126 @defun spam-stat-buffer-change-to-spam
22127 Called in a buffer, that buffer is no longer considered to be normal
22128 mail but spam. Use this to change the status of a mail that has
22129 already been processed as non-spam.
22132 @defun spam-stat-buffer-change-to-non-spam
22133 Called in a buffer, that buffer is no longer considered to be spam but
22134 normal mail. Use this to change the status of a mail that has already
22135 been processed as spam.
22138 @defun spam-stat-save
22139 Save the hash table to the file. The filename used is stored in the
22140 variable @code{spam-stat-file}.
22143 @defun spam-stat-load
22144 Load the hash table from a file. The filename used is stored in the
22145 variable @code{spam-stat-file}.
22148 @defun spam-stat-score-word
22149 Return the spam score for a word.
22152 @defun spam-stat-score-buffer
22153 Return the spam score for a buffer.
22156 @defun spam-stat-split-fancy
22157 Use this function for fancy mail splitting. Add the rule @samp{(:
22158 spam-stat-split-fancy)} to @code{nnmail-split-fancy}
22161 Make sure you load the dictionary before using it. This requires the
22162 following in your @file{~/.gnus} file:
22165 (require 'spam-stat)
22169 Typical test will involve calls to the following functions:
22172 Reset: (setq spam-stat (make-hash-table :test 'equal))
22173 Learn spam: (spam-stat-process-spam-directory "~/Mail/mail/spam")
22174 Learn non-spam: (spam-stat-process-non-spam-directory "~/Mail/mail/misc")
22175 Save table: (spam-stat-save)
22176 File size: (nth 7 (file-attributes spam-stat-file))
22177 Number of words: (hash-table-count spam-stat)
22178 Test spam: (spam-stat-test-directory "~/Mail/mail/spam")
22179 Test non-spam: (spam-stat-test-directory "~/Mail/mail/misc")
22180 Reduce table size: (spam-stat-reduce-size)
22181 Save table: (spam-stat-save)
22182 File size: (nth 7 (file-attributes spam-stat-file))
22183 Number of words: (hash-table-count spam-stat)
22184 Test spam: (spam-stat-test-directory "~/Mail/mail/spam")
22185 Test non-spam: (spam-stat-test-directory "~/Mail/mail/misc")
22188 Here is how you would create your dictionary:
22191 Reset: (setq spam-stat (make-hash-table :test 'equal))
22192 Learn spam: (spam-stat-process-spam-directory "~/Mail/mail/spam")
22193 Learn non-spam: (spam-stat-process-non-spam-directory "~/Mail/mail/misc")
22194 Repeat for any other non-spam group you need...
22195 Reduce table size: (spam-stat-reduce-size)
22196 Save table: (spam-stat-save)
22199 @node Various Various
22200 @section Various Various
22206 @item gnus-home-directory
22207 All Gnus path variables will be initialized from this variable, which
22208 defaults to @file{~/}.
22210 @item gnus-directory
22211 @vindex gnus-directory
22212 Most Gnus storage path variables will be initialized from this variable,
22213 which defaults to the @samp{SAVEDIR} environment variable, or
22214 @file{~/News/} if that variable isn't set.
22216 Note that gnus is mostly loaded when the @file{.gnus.el} file is read.
22217 This means that other directory variables that are initialized from this
22218 variable won't be set properly if you set this variable in
22219 @file{.gnus.el}. Set this variable in @file{.emacs} instead.
22221 @item gnus-default-directory
22222 @vindex gnus-default-directory
22223 Not related to the above variable at all---this variable says what the
22224 default directory of all Gnus buffers should be. If you issue commands
22225 like @kbd{C-x C-f}, the prompt you'll get starts in the current buffer's
22226 default directory. If this variable is @code{nil} (which is the
22227 default), the default directory will be the default directory of the
22228 buffer you were in when you started Gnus.
22231 @vindex gnus-verbose
22232 This variable is an integer between zero and ten. The higher the value,
22233 the more messages will be displayed. If this variable is zero, Gnus
22234 will never flash any messages, if it is seven (which is the default),
22235 most important messages will be shown, and if it is ten, Gnus won't ever
22236 shut up, but will flash so many messages it will make your head swim.
22238 @item gnus-verbose-backends
22239 @vindex gnus-verbose-backends
22240 This variable works the same way as @code{gnus-verbose}, but it applies
22241 to the Gnus back ends instead of Gnus proper.
22243 @item nnheader-max-head-length
22244 @vindex nnheader-max-head-length
22245 When the back ends read straight heads of articles, they all try to read
22246 as little as possible. This variable (default 4096) specifies
22247 the absolute max length the back ends will try to read before giving up
22248 on finding a separator line between the head and the body. If this
22249 variable is @code{nil}, there is no upper read bound. If it is
22250 @code{t}, the back ends won't try to read the articles piece by piece,
22251 but read the entire articles. This makes sense with some versions of
22252 @code{ange-ftp} or @code{efs}.
22254 @item nnheader-head-chop-length
22255 @vindex nnheader-head-chop-length
22256 This variable (default 2048) says how big a piece of each article to
22257 read when doing the operation described above.
22259 @item nnheader-file-name-translation-alist
22260 @vindex nnheader-file-name-translation-alist
22262 @cindex invalid characters in file names
22263 @cindex characters in file names
22264 This is an alist that says how to translate characters in file names.
22265 For instance, if @samp{:} is invalid as a file character in file names
22266 on your system (you OS/2 user you), you could say something like:
22269 (setq nnheader-file-name-translation-alist
22273 In fact, this is the default value for this variable on OS/2 and MS
22274 Windows (phooey) systems.
22276 @item gnus-hidden-properties
22277 @vindex gnus-hidden-properties
22278 This is a list of properties to use to hide ``invisible'' text. It is
22279 @code{(invisible t intangible t)} by default on most systems, which
22280 makes invisible text invisible and intangible.
22282 @item gnus-parse-headers-hook
22283 @vindex gnus-parse-headers-hook
22284 A hook called before parsing headers. It can be used, for instance, to
22285 gather statistics on the headers fetched, or perhaps you'd like to prune
22286 some headers. I don't see why you'd want that, though.
22288 @item gnus-shell-command-separator
22289 @vindex gnus-shell-command-separator
22290 String used to separate two shell commands. The default is @samp{;}.
22292 @item gnus-invalid-group-regexp
22293 @vindex gnus-invalid-group-regexp
22295 Regexp to match ``invalid'' group names when querying user for a group
22296 name. The default value catches some @strong{really} invalid group
22297 names who could possibly mess up Gnus internally (like allowing
22298 @samp{:} in a group name, which is normally used to delimit method and
22301 @sc{imap} users might want to allow @samp{/} in group names though.
22309 Well, that's the manual---you can get on with your life now. Keep in
22310 touch. Say hello to your cats from me.
22312 My @strong{ghod}---I just can't stand goodbyes. Sniffle.
22314 Ol' Charles Reznikoff said it pretty well, so I leave the floor to him:
22320 Not because of victories @*
22323 but for the common sunshine,@*
22325 the largess of the spring.
22329 but for the day's work done@*
22330 as well as I was able;@*
22331 not for a seat upon the dais@*
22332 but at the common table.@*
22337 @chapter Appendices
22340 * XEmacs:: Requirements for installing under XEmacs.
22341 * History:: How Gnus got where it is today.
22342 * On Writing Manuals:: Why this is not a beginner's guide.
22343 * Terminology:: We use really difficult, like, words here.
22344 * Customization:: Tailoring Gnus to your needs.
22345 * Troubleshooting:: What you might try if things do not work.
22346 * Gnus Reference Guide:: Rilly, rilly technical stuff.
22347 * Emacs for Heathens:: A short introduction to Emacsian terms.
22348 * Frequently Asked Questions::
22355 @cindex Installing under XEmacs
22357 XEmacs is distributed as a collection of packages. You should install
22358 whatever packages the Gnus XEmacs package requires. The current
22359 requirements are @samp{gnus}, @samp{w3}, @samp{mh-e},
22360 @samp{mailcrypt}, @samp{rmail}, @samp{eterm}, @samp{mail-lib},
22361 @samp{xemacs-base}, @samp{sh-script} and @samp{fsf-compat}. The
22362 @samp{misc-games} package is required for Morse decoding.
22369 @sc{gnus} was written by Masanobu @sc{Umeda}. When autumn crept up in
22370 '94, Lars Magne Ingebrigtsen grew bored and decided to rewrite Gnus.
22372 If you want to investigate the person responsible for this outrage,
22373 you can point your (feh!) web browser to
22374 @uref{http://quimby.gnus.org/}. This is also the primary
22375 distribution point for the new and spiffy versions of Gnus, and is
22376 known as The Site That Destroys Newsrcs And Drives People Mad.
22378 During the first extended alpha period of development, the new Gnus was
22379 called ``(ding) Gnus''. @dfn{(ding)} is, of course, short for
22380 @dfn{ding is not Gnus}, which is a total and utter lie, but who cares?
22381 (Besides, the ``Gnus'' in this abbreviation should probably be
22382 pronounced ``news'' as @sc{Umeda} intended, which makes it a more
22383 appropriate name, don't you think?)
22385 In any case, after spending all that energy on coming up with a new and
22386 spunky name, we decided that the name was @emph{too} spunky, so we
22387 renamed it back again to ``Gnus''. But in mixed case. ``Gnus'' vs.
22388 ``@sc{gnus}''. New vs. old.
22391 * Gnus Versions:: What Gnus versions have been released.
22392 * Other Gnus Versions:: Other Gnus versions that also have been released.
22393 * Why?:: What's the point of Gnus?
22394 * Compatibility:: Just how compatible is Gnus with @sc{gnus}?
22395 * Conformity:: Gnus tries to conform to all standards.
22396 * Emacsen:: Gnus can be run on a few modern Emacsen.
22397 * Gnus Development:: How Gnus is developed.
22398 * Contributors:: Oodles of people.
22399 * New Features:: Pointers to some of the new stuff in Gnus.
22403 @node Gnus Versions
22404 @subsection Gnus Versions
22406 @cindex September Gnus
22408 @cindex Quassia Gnus
22409 @cindex Pterodactyl Gnus
22413 The first ``proper'' release of Gnus 5 was done in November 1995 when it
22414 was included in the Emacs 19.30 distribution (132 (ding) Gnus releases
22415 plus 15 Gnus 5.0 releases).
22417 In May 1996 the next Gnus generation (aka. ``September Gnus'' (after 99
22418 releases)) was released under the name ``Gnus 5.2'' (40 releases).
22420 On July 28th 1996 work on Red Gnus was begun, and it was released on
22421 January 25th 1997 (after 84 releases) as ``Gnus 5.4'' (67 releases).
22423 On September 13th 1997, Quassia Gnus was started and lasted 37 releases.
22424 If was released as ``Gnus 5.6'' on March 8th 1998 (46 releases).
22426 Gnus 5.6 begat Pterodactyl Gnus on August 29th 1998 and was released as
22427 ``Gnus 5.8'' (after 99 releases and a CVS repository) on December 3rd
22430 On the 26th of October 2000, Oort Gnus was begun.
22432 If you happen upon a version of Gnus that has a prefixed name --
22433 ``(ding) Gnus'', ``September Gnus'', ``Red Gnus'', ``Quassia Gnus'',
22434 ``Pterodactyl Gnus'', ``Oort Gnus'' -- don't panic. Don't let it know
22435 that you're frightened. Back away. Slowly. Whatever you do, don't
22436 run. Walk away, calmly, until you're out of its reach. Find a proper
22437 released version of Gnus and snuggle up to that instead.
22440 @node Other Gnus Versions
22441 @subsection Other Gnus Versions
22444 In addition to the versions of Gnus which have had their releases
22445 coordinated by Lars, one major development has been Semi-gnus from
22446 Japan. It's based on a library called @sc{semi}, which provides
22447 @sc{mime} capabilities.
22449 These Gnusae are based mainly on Gnus 5.6 and Pterodactyl Gnus.
22450 Collectively, they are called ``Semi-gnus'', and different strains are
22451 called T-gnus, ET-gnus, Nana-gnus and Chaos. These provide powerful
22452 @sc{mime} and multilingualization things, especially important for
22459 What's the point of Gnus?
22461 I want to provide a ``rad'', ``happening'', ``way cool'' and ``hep''
22462 newsreader, that lets you do anything you can think of. That was my
22463 original motivation, but while working on Gnus, it has become clear to
22464 me that this generation of newsreaders really belong in the stone age.
22465 Newsreaders haven't developed much since the infancy of the net. If the
22466 volume continues to rise with the current rate of increase, all current
22467 newsreaders will be pretty much useless. How do you deal with
22468 newsgroups that have thousands of new articles each day? How do you
22469 keep track of millions of people who post?
22471 Gnus offers no real solutions to these questions, but I would very much
22472 like to see Gnus being used as a testing ground for new methods of
22473 reading and fetching news. Expanding on @sc{Umeda}-san's wise decision
22474 to separate the newsreader from the back ends, Gnus now offers a simple
22475 interface for anybody who wants to write new back ends for fetching mail
22476 and news from different sources. I have added hooks for customizations
22477 everywhere I could imagine it being useful. By doing so, I'm inviting
22478 every one of you to explore and invent.
22480 May Gnus never be complete. @kbd{C-u 100 M-x all-hail-emacs} and
22481 @kbd{C-u 100 M-x all-hail-xemacs}.
22484 @node Compatibility
22485 @subsection Compatibility
22487 @cindex compatibility
22488 Gnus was designed to be fully compatible with @sc{gnus}. Almost all key
22489 bindings have been kept. More key bindings have been added, of course,
22490 but only in one or two obscure cases have old bindings been changed.
22495 @center In a cloud bones of steel.
22499 All commands have kept their names. Some internal functions have changed
22502 The @code{gnus-uu} package has changed drastically. @xref{Decoding
22505 One major compatibility question is the presence of several summary
22506 buffers. All variables relevant while reading a group are
22507 buffer-local to the summary buffer they belong in. Although many
22508 important variables have their values copied into their global
22509 counterparts whenever a command is executed in the summary buffer, this
22510 change might lead to incorrect values being used unless you are careful.
22512 All code that relies on knowledge of @sc{gnus} internals will probably
22513 fail. To take two examples: Sorting @code{gnus-newsrc-alist} (or
22514 changing it in any way, as a matter of fact) is strictly verboten. Gnus
22515 maintains a hash table that points to the entries in this alist (which
22516 speeds up many functions), and changing the alist directly will lead to
22520 @cindex highlighting
22521 Old hilit19 code does not work at all. In fact, you should probably
22522 remove all hilit code from all Gnus hooks
22523 (@code{gnus-group-prepare-hook} and @code{gnus-summary-prepare-hook}).
22524 Gnus provides various integrated functions for highlighting. These are
22525 faster and more accurate. To make life easier for everybody, Gnus will
22526 by default remove all hilit calls from all hilit hooks. Uncleanliness!
22529 Packages like @code{expire-kill} will no longer work. As a matter of
22530 fact, you should probably remove all old @sc{gnus} packages (and other
22531 code) when you start using Gnus. More likely than not, Gnus already
22532 does what you have written code to make @sc{gnus} do. (Snicker.)
22534 Even though old methods of doing things are still supported, only the
22535 new methods are documented in this manual. If you detect a new method of
22536 doing something while reading this manual, that does not mean you have
22537 to stop doing it the old way.
22539 Gnus understands all @sc{gnus} startup files.
22541 @kindex M-x gnus-bug
22543 @cindex reporting bugs
22545 Overall, a casual user who hasn't written much code that depends on
22546 @sc{gnus} internals should suffer no problems. If problems occur,
22547 please let me know by issuing that magic command @kbd{M-x gnus-bug}.
22549 @vindex gnus-bug-create-help-buffer
22550 If you are in the habit of sending bug reports @emph{very} often, you
22551 may find the helpful help buffer annoying after a while. If so, set
22552 @code{gnus-bug-create-help-buffer} to @code{nil} to avoid having it pop
22557 @subsection Conformity
22559 No rebels without a clue here, ma'am. We conform to all standards known
22560 to (wo)man. Except for those standards and/or conventions we disagree
22568 There are no known breaches of this standard.
22572 There are no known breaches of this standard, either.
22574 @item Son-of-RFC 1036
22575 @cindex Son-of-RFC 1036
22576 We do have some breaches to this one.
22582 These are considered to be ``vanity headers'', while I consider them
22583 to be consumer information. After seeing so many badly formatted
22584 articles coming from @code{tin} and @code{Netscape} I know not to use
22585 either of those for posting articles. I would not have known that if
22586 it wasn't for the @code{X-Newsreader} header.
22591 USEFOR is an IETF working group writing a successor to RFC 1036, based
22592 on Son-of-RFC 1036. They have produced a number of drafts proposing
22593 various changes to the format of news articles. The Gnus towers will
22594 look into implementing the changes when the draft is accepted as an RFC.
22596 @item MIME - RFC 2045-2049 etc
22598 All the various @sc{mime} RFCs are supported.
22600 @item Disposition Notifications - RFC 2298
22601 Message Mode is able to request notifications from the receiver.
22603 @item PGP - RFC 1991 and RFC 2440
22606 RFC 1991 is the original PGP message specification, published as a
22607 Information RFC. RFC 2440 was the follow-up, now called Open PGP, and
22608 put on the Standards Track. Both document a non-@sc{mime} aware PGP
22609 format. Gnus supports both encoding (signing and encryption) and
22610 decoding (verification and decryption).
22612 @item PGP/MIME - RFC 2015/3156
22613 RFC 2015 (superseded by 3156 which references RFC 2440 instead of RFC
22614 1991) describes the @sc{mime}-wrapping around the RF 1991/2440 format.
22615 Gnus supports both encoding and decoding.
22617 @item S/MIME - RFC 2633
22618 RFC 2633 describes the @sc{s/mime} format.
22620 @item IMAP - RFC 1730/2060, RFC 2195, RFC 2086, RFC 2359, RFC 2595, RFC 1731
22621 RFC 1730 is @sc{imap} version 4, updated somewhat by RFC 2060 (@sc{imap} 4
22622 revision 1). RFC 2195 describes CRAM-MD5 authentication for @sc{imap}. RFC
22623 2086 describes access control lists (ACLs) for @sc{imap}. RFC 2359
22624 describes a @sc{imap} protocol enhancement. RFC 2595 describes the proper
22625 TLS integration (STARTTLS) with @sc{imap}. RFC 1731 describes the
22626 GSSAPI/Kerberos4 mechanisms for @sc{imap}.
22630 If you ever notice Gnus acting non-compliant with regards to the texts
22631 mentioned above, don't hesitate to drop a note to Gnus Towers and let us
22636 @subsection Emacsen
22642 Gnus should work on :
22650 XEmacs 21.1.1 and up.
22654 This Gnus version will absolutely not work on any Emacsen older than
22655 that. Not reliably, at least. Older versions of Gnus may work on older
22656 Emacs versions. However, T-gnus does support ``Mule 2.3 based on Emacs
22657 19.34'' and possibly the versions of XEmacs prior to 21.1.1, e.g. 20.4.
22658 See the file ``README'' in the T-gnus distribution for more details.
22660 There are some vague differences between Gnus on the various
22661 platforms---XEmacs features more graphics (a logo and a toolbar)---but
22662 other than that, things should look pretty much the same under all
22666 @node Gnus Development
22667 @subsection Gnus Development
22669 Gnus is developed in a two-phased cycle. The first phase involves much
22670 discussion on the @samp{ding@@gnus.org} mailing list, where people
22671 propose changes and new features, post patches and new back ends. This
22672 phase is called the @dfn{alpha} phase, since the Gnusae released in this
22673 phase are @dfn{alpha releases}, or (perhaps more commonly in other
22674 circles) @dfn{snapshots}. During this phase, Gnus is assumed to be
22675 unstable and should not be used by casual users. Gnus alpha releases
22676 have names like ``Red Gnus'' and ``Quassia Gnus''.
22678 After futzing around for 50-100 alpha releases, Gnus is declared
22679 @dfn{frozen}, and only bug fixes are applied. Gnus loses the prefix,
22680 and is called things like ``Gnus 5.6.32'' instead. Normal people are
22681 supposed to be able to use these, and these are mostly discussed on the
22682 @samp{gnu.emacs.gnus} newsgroup.
22685 @vindex mail-source-delete-incoming
22686 Some variable defaults differ between alpha Gnusae and released Gnusae.
22687 In particular, @code{mail-source-delete-incoming} defaults to @code{nil} in
22688 alpha Gnusae and @code{t} in released Gnusae. This is to prevent
22689 lossage of mail if an alpha release hiccups while handling the mail.
22691 The division of discussion between the ding mailing list and the Gnus
22692 newsgroup is not purely based on publicity concerns. It's true that
22693 having people write about the horrible things that an alpha Gnus release
22694 can do (sometimes) in a public forum may scare people off, but more
22695 importantly, talking about new experimental features that have been
22696 introduced may confuse casual users. New features are frequently
22697 introduced, fiddled with, and judged to be found wanting, and then
22698 either discarded or totally rewritten. People reading the mailing list
22699 usually keep up with these rapid changes, while people on the newsgroup
22700 can't be assumed to do so.
22705 @subsection Contributors
22706 @cindex contributors
22708 The new Gnus version couldn't have been done without the help of all the
22709 people on the (ding) mailing list. Every day for over a year I have
22710 gotten billions of nice bug reports from them, filling me with joy,
22711 every single one of them. Smooches. The people on the list have been
22712 tried beyond endurance, what with my ``oh, that's a neat idea <type
22713 type>, yup, I'll release it right away <ship off> no wait, that doesn't
22714 work at all <type type>, yup, I'll ship that one off right away <ship
22715 off> no, wait, that absolutely does not work'' policy for releases.
22716 Micro$oft---bah. Amateurs. I'm @emph{much} worse. (Or is that
22717 ``worser''? ``much worser''? ``worsest''?)
22719 I would like to take this opportunity to thank the Academy for... oops,
22725 Masanobu @sc{Umeda}---the writer of the original @sc{gnus}.
22728 Shenghuo Zhu---uudecode.el, mm-uu.el, rfc1843.el, webmail.el,
22729 nnwarchive and many, many other things connected with @sc{mime} and
22730 other types of en/decoding, as well as general bug fixing, new
22731 functionality and stuff.
22734 Per Abrahamsen---custom, scoring, highlighting and @sc{soup} code (as
22735 well as numerous other things).
22738 Luis Fernandes---design and graphics.
22741 Joe Reiss---creator of the smiley faces.
22744 Justin Sheehy--the FAQ maintainer.
22747 Erik Naggum---help, ideas, support, code and stuff.
22750 Wes Hardaker---@file{gnus-picon.el} and the manual section on
22751 @dfn{picons} (@pxref{Picons}).
22754 Kim-Minh Kaplan---further work on the picon code.
22757 Brad Miller---@file{gnus-gl.el} and the GroupLens manual section
22758 (@pxref{GroupLens}).
22761 Sudish Joseph---innumerable bug fixes.
22764 Ilja Weis---@file{gnus-topic.el}.
22767 Steven L. Baur---lots and lots and lots of bugs detections and fixes.
22770 Vladimir Alexiev---the refcard and reference booklets.
22773 Felix Lee & Jamie Zawinski---I stole some pieces from the XGnus
22774 distribution by Felix Lee and JWZ.
22777 Scott Byer---@file{nnfolder.el} enhancements & rewrite.
22780 Peter Mutsaers---orphan article scoring code.
22783 Ken Raeburn---POP mail support.
22786 Hallvard B Furuseth---various bits and pieces, especially dealing with
22790 Brian Edmonds---@file{gnus-bbdb.el}.
22793 David Moore---rewrite of @file{nnvirtual.el} and many other things.
22796 Kevin Davidson---came up with the name @dfn{ding}, so blame him.
22799 François Pinard---many, many interesting and thorough bug reports, as
22800 well as autoconf support.
22804 This manual was proof-read by Adrian Aichner, with Ricardo Nassif, Mark
22805 Borges, and Jost Krieger proof-reading parts of the manual.
22807 The following people have contributed many patches and suggestions:
22816 Jason L. Tibbitts, III,
22820 Also thanks to the following for patches and stuff:
22830 Alexei V. Barantsev,
22845 Massimo Campostrini,
22850 Jae-you Chung, @c ?
22851 James H. Cloos, Jr.,
22855 Andrew J. Cosgriff,
22858 Geoffrey T. Dairiki,
22864 Michael Welsh Duggan,
22869 Enami Tsugutomo, @c Enami
22873 Nelson Jose dos Santos Ferreira,
22881 Arne Georg Gleditsch,
22883 Michelangelo Grigni,
22887 Kenichi Handa, @c Handa
22889 Yoshiki Hayashi, @c ?
22891 Hisashige Kenji, @c Hisashige
22898 François Felix Ingrand,
22899 Tatsuya Ichikawa, @c ?
22900 Ishikawa Ichiro, @c Ishikawa
22902 Iwamuro Motonori, @c Iwamuro
22913 Peter Skov Knudsen,
22914 Shuhei Kobayashi, @c Kobayashi
22916 Koseki Yoshinori, @c Koseki
22917 Thor Kristoffersen,
22920 Seokchan Lee, @c Lee
22938 Morioka Tomohiko, @c Morioka
22939 Erik Toubro Nielsen,
22946 Masaharu Onishi, @c Onishi
22951 Jens-Ulrik Holger Petersen,
22955 John McClary Prevost,
22961 Lars Balker Rasmussen,
22966 Christian von Roques,
22969 Wolfgang Rupprecht,
22976 Philippe Schnoebelen,
22978 Randal L. Schwartz,
22992 Kiyokazu Suto, @c Suto
22997 Tozawa Akihiko, @c Tozawa
23013 Katsumi Yamaoka @c Yamaoka
23018 For a full overview of what each person has done, the ChangeLogs
23019 included in the Gnus alpha distributions should give ample reading
23020 (550kB and counting).
23022 Apologies to everybody that I've forgotten, of which there are many, I'm
23025 Gee, that's quite a list of people. I guess that must mean that there
23026 actually are people who are using Gnus. Who'd'a thunk it!
23030 @subsection New Features
23031 @cindex new features
23034 * ding Gnus:: New things in Gnus 5.0/5.1, the first new Gnus.
23035 * September Gnus:: The Thing Formally Known As Gnus 5.2/5.3.
23036 * Red Gnus:: Third time best---Gnus 5.4/5.5.
23037 * Quassia Gnus:: Two times two is four, or Gnus 5.6/5.7.
23038 * Pterodactyl Gnus:: Pentad also starts with P, AKA Gnus 5.8/5.9.
23041 These lists are, of course, just @emph{short} overviews of the
23042 @emph{most} important new features. No, really. There are tons more.
23043 Yes, we have feeping creaturism in full effect.
23046 @subsubsection (ding) Gnus
23048 New features in Gnus 5.0/5.1:
23053 The look of all buffers can be changed by setting format-like variables
23054 (@pxref{Group Buffer Format} and @pxref{Summary Buffer Format}).
23057 Local spool and several @sc{nntp} servers can be used at once
23058 (@pxref{Select Methods}).
23061 You can combine groups into virtual groups (@pxref{Virtual Groups}).
23064 You can read a number of different mail formats (@pxref{Getting Mail}).
23065 All the mail back ends implement a convenient mail expiry scheme
23066 (@pxref{Expiring Mail}).
23069 Gnus can use various strategies for gathering threads that have lost
23070 their roots (thereby gathering loose sub-threads into one thread) or it
23071 can go back and retrieve enough headers to build a complete thread
23072 (@pxref{Customizing Threading}).
23075 Killed groups can be displayed in the group buffer, and you can read
23076 them as well (@pxref{Listing Groups}).
23079 Gnus can do partial group updates---you do not have to retrieve the
23080 entire active file just to check for new articles in a few groups
23081 (@pxref{The Active File}).
23084 Gnus implements a sliding scale of subscribedness to groups
23085 (@pxref{Group Levels}).
23088 You can score articles according to any number of criteria
23089 (@pxref{Scoring}). You can even get Gnus to find out how to score
23090 articles for you (@pxref{Adaptive Scoring}).
23093 Gnus maintains a dribble buffer that is auto-saved the normal Emacs
23094 manner, so it should be difficult to lose much data on what you have
23095 read if your machine should go down (@pxref{Auto Save}).
23098 Gnus now has its own startup file (@file{.gnus.el}) to avoid cluttering up
23099 the @file{.emacs} file.
23102 You can set the process mark on both groups and articles and perform
23103 operations on all the marked items (@pxref{Process/Prefix}).
23106 You can grep through a subset of groups and create a group from the
23107 results (@pxref{Kibozed Groups}).
23110 You can list subsets of groups according to, well, anything
23111 (@pxref{Listing Groups}).
23114 You can browse foreign servers and subscribe to groups from those
23115 servers (@pxref{Browse Foreign Server}).
23118 Gnus can fetch articles, asynchronously, on a second connection to the
23119 server (@pxref{Asynchronous Fetching}).
23122 You can cache articles locally (@pxref{Article Caching}).
23125 The uudecode functions have been expanded and generalized
23126 (@pxref{Decoding Articles}).
23129 You can still post uuencoded articles, which was a little-known feature
23130 of @sc{gnus}' past (@pxref{Uuencoding and Posting}).
23133 Fetching parents (and other articles) now actually works without
23134 glitches (@pxref{Finding the Parent}).
23137 Gnus can fetch FAQs and group descriptions (@pxref{Group Information}).
23140 Digests (and other files) can be used as the basis for groups
23141 (@pxref{Document Groups}).
23144 Articles can be highlighted and customized (@pxref{Customizing
23148 URLs and other external references can be buttonized (@pxref{Article
23152 You can do lots of strange stuff with the Gnus window & frame
23153 configuration (@pxref{Window Layout}).
23156 You can click on buttons instead of using the keyboard
23162 @node September Gnus
23163 @subsubsection September Gnus
23167 \gnusfig{-28cm}{0cm}{\epsfig{figure=ps/september,height=20cm}}
23171 New features in Gnus 5.2/5.3:
23176 A new message composition mode is used. All old customization variables
23177 for @code{mail-mode}, @code{rnews-reply-mode} and @code{gnus-msg} are
23181 Gnus is now able to generate @dfn{sparse} threads---threads where
23182 missing articles are represented by empty nodes (@pxref{Customizing
23186 (setq gnus-build-sparse-threads 'some)
23190 Outgoing articles are stored on a special archive server
23191 (@pxref{Archived Messages}).
23194 Partial thread regeneration now happens when articles are
23198 Gnus can make use of GroupLens predictions (@pxref{GroupLens}).
23201 Picons (personal icons) can be displayed under XEmacs (@pxref{Picons}).
23204 A @code{trn}-like tree buffer can be displayed (@pxref{Tree Display}).
23207 (setq gnus-use-trees t)
23211 An @code{nn}-like pick-and-read minor mode is available for the summary
23212 buffers (@pxref{Pick and Read}).
23215 (add-hook 'gnus-summary-mode-hook 'gnus-pick-mode)
23219 In binary groups you can use a special binary minor mode (@pxref{Binary
23223 Groups can be grouped in a folding topic hierarchy (@pxref{Group
23227 (add-hook 'gnus-group-mode-hook 'gnus-topic-mode)
23231 Gnus can re-send and bounce mail (@pxref{Summary Mail Commands}).
23234 Groups can now have a score, and bubbling based on entry frequency
23235 is possible (@pxref{Group Score}).
23238 (add-hook 'gnus-summary-exit-hook 'gnus-summary-bubble-group)
23242 Groups can be process-marked, and commands can be performed on
23243 groups of groups (@pxref{Marking Groups}).
23246 Caching is possible in virtual groups.
23249 @code{nndoc} now understands all kinds of digests, mail boxes, rnews
23250 news batches, ClariNet briefs collections, and just about everything
23251 else (@pxref{Document Groups}).
23254 Gnus has a new back end (@code{nnsoup}) to create/read SOUP packets
23258 The Gnus cache is much faster.
23261 Groups can be sorted according to many criteria (@pxref{Sorting
23265 New group parameters have been introduced to set list-addresses and
23266 expiry times (@pxref{Group Parameters}).
23269 All formatting specs allow specifying faces to be used
23270 (@pxref{Formatting Fonts}).
23273 There are several more commands for setting/removing/acting on process
23274 marked articles on the @kbd{M P} submap (@pxref{Setting Process Marks}).
23277 The summary buffer can be limited to show parts of the available
23278 articles based on a wide range of criteria. These commands have been
23279 bound to keys on the @kbd{/} submap (@pxref{Limiting}).
23282 Articles can be made persistent with the @kbd{*} command
23283 (@pxref{Persistent Articles}).
23286 All functions for hiding article elements are now toggles.
23289 Article headers can be buttonized (@pxref{Article Washing}).
23292 All mail back ends support fetching articles by @code{Message-ID}.
23295 Duplicate mail can now be treated properly (@pxref{Duplicates}).
23298 All summary mode commands are available directly from the article
23299 buffer (@pxref{Article Keymap}).
23302 Frames can be part of @code{gnus-buffer-configuration} (@pxref{Window
23306 Mail can be re-scanned by a daemonic process (@pxref{Daemons}).
23309 \marginpar[\mbox{}\hfill\epsfig{figure=ps/fseptember,height=5cm}]{\epsfig{figure=ps/fseptember,height=5cm}}
23314 Gnus can make use of NoCeM files to weed out spam (@pxref{NoCeM}).
23317 (setq gnus-use-nocem t)
23321 Groups can be made permanently visible (@pxref{Listing Groups}).
23324 (setq gnus-permanently-visible-groups "^nnml:")
23328 Many new hooks have been introduced to make customizing easier.
23331 Gnus respects the @code{Mail-Copies-To} header.
23334 Threads can be gathered by looking at the @code{References} header
23335 (@pxref{Customizing Threading}).
23338 (setq gnus-summary-thread-gathering-function
23339 'gnus-gather-threads-by-references)
23343 Read articles can be stored in a special backlog buffer to avoid
23344 refetching (@pxref{Article Backlog}).
23347 (setq gnus-keep-backlog 50)
23351 A clean copy of the current article is always stored in a separate
23352 buffer to allow easier treatment.
23355 Gnus can suggest where to save articles (@pxref{Saving Articles}).
23358 Gnus doesn't have to do as much prompting when saving (@pxref{Saving
23362 (setq gnus-prompt-before-saving t)
23366 @code{gnus-uu} can view decoded files asynchronously while fetching
23367 articles (@pxref{Other Decode Variables}).
23370 (setq gnus-uu-grabbed-file-functions 'gnus-uu-grab-view)
23374 Filling in the article buffer now works properly on cited text
23375 (@pxref{Article Washing}).
23378 Hiding cited text adds buttons to toggle hiding, and how much
23379 cited text to hide is now customizable (@pxref{Article Hiding}).
23382 (setq gnus-cited-lines-visible 2)
23386 Boring headers can be hidden (@pxref{Article Hiding}).
23389 Default scoring values can now be set from the menu bar.
23392 Further syntax checking of outgoing articles have been added.
23398 @subsubsection Red Gnus
23400 New features in Gnus 5.4/5.5:
23404 \gnusfig{-5.5cm}{-4cm}{\epsfig{figure=ps/red,height=20cm}}
23411 @file{nntp.el} has been totally rewritten in an asynchronous fashion.
23414 Article prefetching functionality has been moved up into
23415 Gnus (@pxref{Asynchronous Fetching}).
23418 Scoring can now be performed with logical operators like @code{and},
23419 @code{or}, @code{not}, and parent redirection (@pxref{Advanced
23423 Article washing status can be displayed in the
23424 article mode line (@pxref{Misc Article}).
23427 @file{gnus.el} has been split into many smaller files.
23430 Suppression of duplicate articles based on Message-ID can be done
23431 (@pxref{Duplicate Suppression}).
23434 (setq gnus-suppress-duplicates t)
23438 New variables for specifying what score and adapt files are to be
23439 considered home score and adapt files (@pxref{Home Score File}) have
23443 @code{nndoc} was rewritten to be easily extendable (@pxref{Document
23444 Server Internals}).
23447 Groups can inherit group parameters from parent topics (@pxref{Topic
23451 Article editing has been revamped and is now actually usable.
23454 Signatures can be recognized in more intelligent fashions
23455 (@pxref{Article Signature}).
23458 Summary pick mode has been made to look more @code{nn}-like. Line
23459 numbers are displayed and the @kbd{.} command can be used to pick
23460 articles (@code{Pick and Read}).
23463 Commands for moving the @file{.newsrc.eld} from one server to
23464 another have been added (@pxref{Changing Servers}).
23467 There's a way now to specify that ``uninteresting'' fields be suppressed
23468 when generating lines in buffers (@pxref{Advanced Formatting}).
23471 Several commands in the group buffer can be undone with @kbd{C-M-_}
23475 Scoring can be done on words using the new score type @code{w}
23476 (@pxref{Score File Format}).
23479 Adaptive scoring can be done on a Subject word-by-word basis
23480 (@pxref{Adaptive Scoring}).
23483 (setq gnus-use-adaptive-scoring '(word))
23487 Scores can be decayed (@pxref{Score Decays}).
23490 (setq gnus-decay-scores t)
23494 Scoring can be performed using a regexp on the Date header. The Date is
23495 normalized to compact ISO 8601 format first (@pxref{Score File Format}).
23498 A new command has been added to remove all data on articles from
23499 the native server (@pxref{Changing Servers}).
23502 A new command for reading collections of documents
23503 (@code{nndoc} with @code{nnvirtual} on top) has been added---@kbd{C-M-d}
23504 (@pxref{Really Various Summary Commands}).
23507 Process mark sets can be pushed and popped (@pxref{Setting Process
23511 A new mail-to-news back end makes it possible to post even when the @sc{nntp}
23512 server doesn't allow posting (@pxref{Mail-To-News Gateways}).
23515 A new back end for reading searches from Web search engines
23516 (@dfn{DejaNews}, @dfn{Alta Vista}, @dfn{InReference}) has been added
23517 (@pxref{Web Searches}).
23520 Groups inside topics can now be sorted using the standard sorting
23521 functions, and each topic can be sorted independently (@pxref{Topic
23525 Subsets of the groups can be sorted independently (@code{Sorting
23529 Cached articles can be pulled into the groups (@pxref{Summary Generation
23533 \marginpar[\mbox{}\hfill\epsfig{figure=ps/fred,width=3cm}]{\epsfig{figure=ps/fred,width=3cm}}
23538 Score files are now applied in a more reliable order (@pxref{Score
23542 Reports on where mail messages end up can be generated (@pxref{Splitting
23546 More hooks and functions have been added to remove junk from incoming
23547 mail before saving the mail (@pxref{Washing Mail}).
23550 Emphasized text can be properly fontisized:
23556 @subsubsection Quassia Gnus
23558 New features in Gnus 5.6:
23563 New functionality for using Gnus as an offline newsreader has been
23564 added. A plethora of new commands and modes have been added. See
23565 @pxref{Gnus Unplugged} for the full story.
23568 The @code{nndraft} back end has returned, but works differently than
23569 before. All Message buffers are now also articles in the @code{nndraft}
23570 group, which is created automatically.
23573 @code{gnus-alter-header-function} can now be used to alter header
23577 @code{gnus-summary-goto-article} now accept Message-ID's.
23580 A new Message command for deleting text in the body of a message
23581 outside the region: @kbd{C-c C-v}.
23584 You can now post to component group in @code{nnvirtual} groups with
23588 @code{nntp-rlogin-program}---new variable to ease customization.
23591 @code{C-u C-c C-c} in @code{gnus-article-edit-mode} will now inhibit
23592 re-highlighting of the article buffer.
23595 New element in @code{gnus-boring-article-headers}---@code{long-to}.
23598 @kbd{M-i} symbolic prefix command. See the section "Symbolic
23599 Prefixes" in the Gnus manual for details.
23602 @kbd{L} and @kbd{I} in the summary buffer now take the symbolic prefix
23603 @kbd{a} to add the score rule to the "all.SCORE" file.
23606 @code{gnus-simplify-subject-functions} variable to allow greater
23607 control over simplification.
23610 @kbd{A T}---new command for fetching the current thread.
23613 @kbd{/ T}---new command for including the current thread in the
23617 @kbd{M-RET} is a new Message command for breaking cited text.
23620 @samp{\\1}-expressions are now valid in @code{nnmail-split-methods}.
23623 The @code{custom-face-lookup} function has been removed.
23624 If you used this function in your initialization files, you must
23625 rewrite them to use @code{face-spec-set} instead.
23628 Canceling now uses the current select method. Symbolic prefix
23629 @kbd{a} forces normal posting method.
23632 New command to translate M******** sm*rtq**t*s into proper
23636 For easier debugging of @code{nntp}, you can set
23637 @code{nntp-record-commands} to a non-@code{nil} value.
23640 @code{nntp} now uses @file{~/.authinfo}, a @file{.netrc}-like file, for
23641 controlling where and how to send @sc{authinfo} to @sc{nntp} servers.
23644 A command for editing group parameters from the summary buffer
23648 A history of where mails have been split is available.
23651 A new article date command has been added---@code{article-date-iso8601}.
23654 Subjects can be simplified when threading by setting
23655 @code{gnus-score-thread-simplify}.
23658 A new function for citing in Message has been
23659 added---@code{message-cite-original-without-signature}.
23662 @code{article-strip-all-blank-lines}---new article command.
23665 A new Message command to kill to the end of the article has
23669 A minimum adaptive score can be specified by using the
23670 @code{gnus-adaptive-word-minimum} variable.
23673 The "lapsed date" article header can be kept continually
23674 updated by the @code{gnus-start-date-timer} command.
23677 Web listserv archives can be read with the @code{nnlistserv} back end.
23680 Old dejanews archives can now be read by @code{nnweb}.
23684 @node Pterodactyl Gnus
23685 @subsubsection Pterodactyl Gnus
23687 New features in Gnus 5.8:
23692 The mail-fetching functions have changed. See the manual for the
23693 many details. In particular, all procmail fetching variables are gone.
23695 If you used procmail like in
23698 (setq nnmail-use-procmail t)
23699 (setq nnmail-spool-file 'procmail)
23700 (setq nnmail-procmail-directory "~/mail/incoming/")
23701 (setq nnmail-procmail-suffix "\\.in")
23704 this now has changed to
23708 '((directory :path "~/mail/incoming/"
23712 More information is available in the info doc at Select Methods ->
23713 Getting Mail -> Mail Sources
23716 Gnus is now a @sc{mime}-capable reader. This affects many parts of
23717 Gnus, and adds a slew of new commands. See the manual for details.
23720 Gnus has also been multilingualized. This also affects too
23721 many parts of Gnus to summarize here, and adds many new variables.
23724 @code{gnus-auto-select-first} can now be a function to be
23725 called to position point.
23728 The user can now decide which extra headers should be included in
23729 summary buffers and @sc{nov} files.
23732 @code{gnus-article-display-hook} has been removed. Instead, a number
23733 of variables starting with @code{gnus-treat-} have been added.
23736 The Gnus posting styles have been redone again and now works in a
23737 subtly different manner.
23740 New web-based back ends have been added: @code{nnslashdot},
23741 @code{nnwarchive} and @code{nnultimate}. nnweb has been revamped,
23742 again, to keep up with ever-changing layouts.
23745 Gnus can now read @sc{imap} mail via @code{nnimap}.
23753 @section The Manual
23757 This manual was generated from a TeXinfo file and then run through
23758 either @code{texi2dvi}
23760 or my own home-brewed TeXinfo to \LaTeX\ transformer,
23761 and then run through @code{latex} and @code{dvips}
23763 to get what you hold in your hands now.
23765 The following conventions have been used:
23770 This is a @samp{string}
23773 This is a @kbd{keystroke}
23776 This is a @file{file}
23779 This is a @code{symbol}
23783 So if I were to say ``set @code{flargnoze} to @samp{yes}'', that would
23787 (setq flargnoze "yes")
23790 If I say ``set @code{flumphel} to @code{yes}'', that would mean:
23793 (setq flumphel 'yes)
23796 @samp{yes} and @code{yes} are two @emph{very} different things---don't
23797 ever get them confused.
23801 Of course, everything in this manual is of vital interest, so you should
23802 read it all. Several times. However, if you feel like skimming the
23803 manual, look for that gnu head you should see in the margin over
23804 there---it means that what's being discussed is of more importance than
23805 the rest of the stuff. (On the other hand, if everything is infinitely
23806 important, how can anything be more important than that? Just one more
23807 of the mysteries of this world, I guess.)
23813 @node On Writing Manuals
23814 @section On Writing Manuals
23816 I guess most manuals are written after-the-fact; documenting a program
23817 that's already there. This is not how this manual is written. When
23818 implementing something, I write the manual entry for that something
23819 straight away. I then see that it's difficult to explain the
23820 functionality, so I write how it's supposed to be, and then I change the
23821 implementation. Writing the documentation and writing the code goes
23824 This, of course, means that this manual has no, or little, flow. It
23825 documents absolutely everything in Gnus, but often not where you're
23826 looking for it. It is a reference manual, and not a guide to how to get
23829 That would be a totally different book, that should be written using the
23830 reference manual as source material. It would look quite differently.
23835 @section Terminology
23837 @cindex terminology
23842 This is what you are supposed to use this thing for---reading news.
23843 News is generally fetched from a nearby @sc{nntp} server, and is
23844 generally publicly available to everybody. If you post news, the entire
23845 world is likely to read just what you have written, and they'll all
23846 snigger mischievously. Behind your back.
23850 Everything that's delivered to you personally is mail. Some news/mail
23851 readers (like Gnus) blur the distinction between mail and news, but
23852 there is a difference. Mail is private. News is public. Mailing is
23853 not posting, and replying is not following up.
23857 Send a mail to the person who has written what you are reading.
23861 Post an article to the current newsgroup responding to the article you
23866 Gnus considers mail and news to be mostly the same, really. The only
23867 difference is how to access the actual articles. News articles are
23868 commonly fetched via the protocol NNTP, whereas mail messages could be
23869 read from a file on the local disk. The internal architecture of Gnus
23870 thus comprises a `front end' and a number of `back ends'. Internally,
23871 when you enter a group (by hitting @key{RET}, say), you thereby invoke
23872 a function in the front end in Gnus. The front end then `talks' to a
23873 back end and says things like ``Give me the list of articles in the foo
23874 group'' or ``Show me article number 4711''.
23876 So a back end mainly defines either a protocol (the @code{nntp} back end
23877 accesses news via NNTP, the @code{nnimap} back end accesses mail via
23878 IMAP) or a file format and directory layout (the @code{nnspool} back end
23879 accesses news via the common `spool directory' format, the @code{nnml}
23880 back end access mail via a file format and directory layout that's
23883 Gnus does not handle the underlying media, so to speak---this is all
23884 done by the back ends. A back end is a collection of functions to
23885 access the articles.
23887 However, sometimes the term `back end' is also used where `server'
23888 would have been more appropriate. And then there is the term `select
23889 method' which can mean either. The Gnus terminology can be quite
23894 Gnus will always use one method (and back end) as the @dfn{native}, or
23895 default, way of getting news.
23899 You can also have any number of foreign groups active at the same time.
23900 These are groups that use non-native non-secondary back ends for getting
23905 Secondary back ends are somewhere half-way between being native and being
23906 foreign, but they mostly act like they are native.
23910 A message that has been posted as news.
23913 @cindex mail message
23914 A message that has been mailed.
23918 A mail message or news article
23922 The top part of a message, where administrative information (etc.) is
23927 The rest of an article. Everything not in the head is in the
23932 A line from the head of an article.
23936 A collection of such lines, or a collection of heads. Or even a
23937 collection of @sc{nov} lines.
23941 When Gnus enters a group, it asks the back end for the headers of all
23942 unread articles in the group. Most servers support the News OverView
23943 format, which is more compact and much faster to read and parse than the
23944 normal @sc{head} format.
23948 Each group is subscribed at some @dfn{level} or other (1-9). The ones
23949 that have a lower level are ``more'' subscribed than the groups with a
23950 higher level. In fact, groups on levels 1-5 are considered
23951 @dfn{subscribed}; 6-7 are @dfn{unsubscribed}; 8 are @dfn{zombies}; and 9
23952 are @dfn{killed}. Commands for listing groups and scanning for new
23953 articles will all use the numeric prefix as @dfn{working level}.
23955 @item killed groups
23956 @cindex killed groups
23957 No information on killed groups is stored or updated, which makes killed
23958 groups much easier to handle than subscribed groups.
23960 @item zombie groups
23961 @cindex zombie groups
23962 Just like killed groups, only slightly less dead.
23965 @cindex active file
23966 The news server has to keep track of what articles it carries, and what
23967 groups exist. All this information in stored in the active file, which
23968 is rather large, as you might surmise.
23971 @cindex bogus groups
23972 A group that exists in the @file{.newsrc} file, but isn't known to the
23973 server (i.e., it isn't in the active file), is a @emph{bogus group}.
23974 This means that the group probably doesn't exist (any more).
23977 @cindex activating groups
23978 The act of asking the server for info on a group and computing the
23979 number of unread articles is called @dfn{activating the group}.
23980 Un-activated groups are listed with @samp{*} in the group buffer.
23984 A machine one can connect to and get news (or mail) from.
23986 @item select method
23987 @cindex select method
23988 A structure that specifies the back end, the server and the virtual
23991 @item virtual server
23992 @cindex virtual server
23993 A named select method. Since a select method defines all there is to
23994 know about connecting to a (physical) server, taking the thing as a
23995 whole is a virtual server.
23999 Taking a buffer and running it through a filter of some sort. The
24000 result will (more often than not) be cleaner and more pleasing than the
24003 @item ephemeral groups
24004 @cindex ephemeral groups
24005 Most groups store data on what articles you have read. @dfn{Ephemeral}
24006 groups are groups that will have no data stored---when you exit the
24007 group, it'll disappear into the aether.
24010 @cindex solid groups
24011 This is the opposite of ephemeral groups. All groups listed in the
24012 group buffer are solid groups.
24014 @item sparse articles
24015 @cindex sparse articles
24016 These are article placeholders shown in the summary buffer when
24017 @code{gnus-build-sparse-threads} has been switched on.
24021 To put responses to articles directly after the articles they respond
24022 to---in a hierarchical fashion.
24026 @cindex thread root
24027 The first article in a thread is the root. It is the ancestor of all
24028 articles in the thread.
24032 An article that has responses.
24036 An article that responds to a different article---its parent.
24040 A collection of messages in one file. The most common digest format is
24041 specified by RFC 1153.
24047 @node Customization
24048 @section Customization
24049 @cindex general customization
24051 All variables are properly documented elsewhere in this manual. This
24052 section is designed to give general pointers on how to customize Gnus
24053 for some quite common situations.
24056 * Slow/Expensive Connection:: You run a local Emacs and get the news elsewhere.
24057 * Slow Terminal Connection:: You run a remote Emacs.
24058 * Little Disk Space:: You feel that having large setup files is icky.
24059 * Slow Machine:: You feel like buying a faster machine.
24063 @node Slow/Expensive Connection
24064 @subsection Slow/Expensive NNTP Connection
24066 If you run Emacs on a machine locally, and get your news from a machine
24067 over some very thin strings, you want to cut down on the amount of data
24068 Gnus has to get from the @sc{nntp} server.
24072 @item gnus-read-active-file
24073 Set this to @code{nil}, which will inhibit Gnus from requesting the
24074 entire active file from the server. This file is often v. large. You
24075 also have to set @code{gnus-check-new-newsgroups} and
24076 @code{gnus-check-bogus-newsgroups} to @code{nil} to make sure that Gnus
24077 doesn't suddenly decide to fetch the active file anyway.
24079 @item gnus-nov-is-evil
24080 This one has to be @code{nil}. If not, grabbing article headers from
24081 the @sc{nntp} server will not be very fast. Not all @sc{nntp} servers
24082 support @sc{xover}; Gnus will detect this by itself.
24086 @node Slow Terminal Connection
24087 @subsection Slow Terminal Connection
24089 Let's say you use your home computer for dialing up the system that runs
24090 Emacs and Gnus. If your modem is slow, you want to reduce (as much as
24091 possible) the amount of data sent over the wires.
24095 @item gnus-auto-center-summary
24096 Set this to @code{nil} to inhibit Gnus from re-centering the summary
24097 buffer all the time. If it is @code{vertical}, do only vertical
24098 re-centering. If it is neither @code{nil} nor @code{vertical}, do both
24099 horizontal and vertical recentering.
24101 @item gnus-visible-headers
24102 Cut down on the headers included in the articles to the
24103 minimum. You can, in fact, make do without them altogether---most of the
24104 useful data is in the summary buffer, anyway. Set this variable to
24105 @samp{^NEVVVVER} or @samp{From:}, or whatever you feel you need.
24107 Set this hook to all the available hiding commands:
24109 (setq gnus-treat-hide-headers 'head
24110 gnus-treat-hide-signature t
24111 gnus-treat-hide-citation t)
24114 @item gnus-use-full-window
24115 By setting this to @code{nil}, you can make all the windows smaller.
24116 While this doesn't really cut down much generally, it means that you
24117 have to see smaller portions of articles before deciding that you didn't
24118 want to read them anyway.
24120 @item gnus-thread-hide-subtree
24121 If this is non-@code{nil}, all threads in the summary buffer will be
24125 @item gnus-updated-mode-lines
24126 If this is @code{nil}, Gnus will not put information in the buffer mode
24127 lines, which might save some time.
24131 @node Little Disk Space
24132 @subsection Little Disk Space
24135 The startup files can get rather large, so you may want to cut their
24136 sizes a bit if you are running out of space.
24140 @item gnus-save-newsrc-file
24141 If this is @code{nil}, Gnus will never save @file{.newsrc}---it will
24142 only save @file{.newsrc.eld}. This means that you will not be able to
24143 use any other newsreaders than Gnus. This variable is @code{t} by
24146 @item gnus-read-newsrc-file
24147 If this is @code{nil}, Gnus will never read @file{.newsrc}---it will
24148 only read @file{.newsrc.eld}. This means that you will not be able to
24149 use any other newsreaders than Gnus. This variable is @code{t} by
24152 @item gnus-save-killed-list
24153 If this is @code{nil}, Gnus will not save the list of dead groups. You
24154 should also set @code{gnus-check-new-newsgroups} to @code{ask-server}
24155 and @code{gnus-check-bogus-newsgroups} to @code{nil} if you set this
24156 variable to @code{nil}. This variable is @code{t} by default.
24162 @subsection Slow Machine
24163 @cindex slow machine
24165 If you have a slow machine, or are just really impatient, there are a
24166 few things you can do to make Gnus run faster.
24168 Set @code{gnus-check-new-newsgroups} and
24169 @code{gnus-check-bogus-newsgroups} to @code{nil} to make startup faster.
24171 Set @code{gnus-show-threads}, @code{gnus-use-cross-reference} and
24172 @code{gnus-nov-is-evil} to @code{nil} to make entering and exiting the
24173 summary buffer faster.
24177 @node Troubleshooting
24178 @section Troubleshooting
24179 @cindex troubleshooting
24181 Gnus works @emph{so} well straight out of the box---I can't imagine any
24189 Make sure your computer is switched on.
24192 Make sure that you really load the current Gnus version. If you have
24193 been running @sc{gnus}, you need to exit Emacs and start it up again before
24197 Try doing an @kbd{M-x gnus-version}. If you get something that looks
24198 like @samp{T-gnus 6.15.* (based on Oort Gnus v0.*; for SEMI 1.1*, FLIM
24199 1.1*)} you have the right files loaded. If, on the other hand, you get
24200 something like @samp{NNTP 3.x} or @samp{nntp flee}, you have some old
24201 @file{.el} files lying around. Delete these.
24204 Read the help group (@kbd{G h} in the group buffer) for a FAQ and a
24208 @vindex max-lisp-eval-depth
24209 Gnus works on many recursive structures, and in some extreme (and very
24210 rare) cases Gnus may recurse down ``too deeply'' and Emacs will beep at
24211 you. If this happens to you, set @code{max-lisp-eval-depth} to 500 or
24212 something like that.
24215 If all else fails, report the problem as a bug.
24218 @cindex reporting bugs
24220 @kindex M-x gnus-bug
24222 If you find a bug in Gnus, you can report it with the @kbd{M-x gnus-bug}
24223 command. @kbd{M-x set-variable RET debug-on-error RET t RET}, and send
24224 me the backtrace. I will fix bugs, but I can only fix them if you send
24225 me a precise description as to how to reproduce the bug.
24227 You really can never be too detailed in a bug report. Always use the
24228 @kbd{M-x gnus-bug} command when you make bug reports, even if it creates
24229 a 10Kb mail each time you use it, and even if you have sent me your
24230 environment 500 times before. I don't care. I want the full info each
24233 It is also important to remember that I have no memory whatsoever. If
24234 you send a bug report, and I send you a reply, and then you just send
24235 back ``No, it's not! Moron!'', I will have no idea what you are
24236 insulting me about. Always over-explain everything. It's much easier
24237 for all of us---if I don't have all the information I need, I will just
24238 mail you and ask for more info, and everything takes more time.
24240 If the problem you're seeing is very visual, and you can't quite explain
24241 it, copy the Emacs window to a file (with @code{xwd}, for instance), put
24242 it somewhere it can be reached, and include the URL of the picture in
24246 If you would like to contribute a patch to fix bugs or make
24247 improvements, please produce the patch using @samp{diff -u}.
24250 If you want to debug your problem further before reporting, possibly
24251 in order to solve the problem yourself and send a patch, you can use
24252 edebug. Debugging lisp code is documented in the Elisp manual
24253 (@pxref{Debugging, , Debugging Lisp Programs, elisp, The GNU Emacs
24254 Lisp Reference Manual}). To get you started with edebug, consider if
24255 you discover some weird behaviour when pressing @kbd{c}, the first
24256 step is to do @kbd{C-h k c} and click on the hyperlink (Emacs only) in
24257 the documentation buffer that leads you to the function definition,
24258 then press @kbd{M-x edebug-defun RET} with point inside that function,
24259 return to Gnus and press @kbd{c} to invoke the code. You will be
24260 placed in the lisp buffer and can single step using @kbd{SPC} and
24261 evaluate expressions using @kbd{M-:} or inspect variables using
24262 @kbd{C-h v}, abort execution with @kbd{q}, and resume execution with
24263 @kbd{c} or @kbd{g}.
24268 Sometimes, a problem do not directly generate a elisp error but
24269 manifests itself by causing Gnus to be very slow. In these cases, you
24270 can use @kbd{M-x toggle-debug-on-quit} and press C-j when things are
24271 slow, and then try to analyze the backtrace (repeating the procedure
24272 helps isolating the real problem areas). A fancier approach is to use
24273 the elisp profiler, ELP. The profiler is (or should be) fully
24274 documented elsewhere, but to get you started there are a few steps
24275 that need to be followed. First, instrument the part of Gnus you are
24276 interested in for profiling, e.g. @kbd{M-x elp-instrument-package RET
24277 gnus} or @kbd{M-x elp-instrument-packagre RET message}. Then perform
24278 the operation that is slow and press @kbd{M-x elp-results}. You will
24279 then see which operations that takes time, and can debug them further.
24280 If the entire operation takes much longer than the time spent in the
24281 slowest function in the profiler output, you probably profiled the
24282 wrong part of Gnus. To reset profiling statistics, use @kbd{M-x
24283 elp-reset-all}. @kbd{M-x elp-restore-all} is supposed to remove
24284 profiling, but given the complexities and dynamic code generation in
24285 Gnus, it might not always work perfectly.
24287 If you just need help, you are better off asking on
24288 @samp{gnu.emacs.gnus}. I'm not very helpful.
24290 @cindex gnu.emacs.gnus
24291 @cindex ding mailing list
24292 You can also ask on the ding mailing list---@samp{ding@@gnus.org}.
24293 Write to @samp{ding-request@@gnus.org} to subscribe.
24297 @node Gnus Reference Guide
24298 @section Gnus Reference Guide
24300 It is my hope that other people will figure out smart stuff that Gnus
24301 can do, and that other people will write those smart things as well. To
24302 facilitate that I thought it would be a good idea to describe the inner
24303 workings of Gnus. And some of the not-so-inner workings, while I'm at
24306 You can never expect the internals of a program not to change, but I
24307 will be defining (in some details) the interface between Gnus and its
24308 back ends (this is written in stone), the format of the score files
24309 (ditto), data structures (some are less likely to change than others)
24310 and general methods of operation.
24313 * Gnus Utility Functions:: Common functions and variable to use.
24314 * Back End Interface:: How Gnus communicates with the servers.
24315 * Score File Syntax:: A BNF definition of the score file standard.
24316 * Headers:: How Gnus stores headers internally.
24317 * Ranges:: A handy format for storing mucho numbers.
24318 * Group Info:: The group info format.
24319 * Extended Interactive:: Symbolic prefixes and stuff.
24320 * Emacs/XEmacs Code:: Gnus can be run under all modern Emacsen.
24321 * Various File Formats:: Formats of files that Gnus use.
24325 @node Gnus Utility Functions
24326 @subsection Gnus Utility Functions
24327 @cindex Gnus utility functions
24328 @cindex utility functions
24330 @cindex internal variables
24332 When writing small functions to be run from hooks (and stuff), it's
24333 vital to have access to the Gnus internal functions and variables.
24334 Below is a list of the most common ones.
24338 @item gnus-newsgroup-name
24339 @vindex gnus-newsgroup-name
24340 This variable holds the name of the current newsgroup.
24342 @item gnus-find-method-for-group
24343 @findex gnus-find-method-for-group
24344 A function that returns the select method for @var{group}.
24346 @item gnus-group-real-name
24347 @findex gnus-group-real-name
24348 Takes a full (prefixed) Gnus group name, and returns the unprefixed
24351 @item gnus-group-prefixed-name
24352 @findex gnus-group-prefixed-name
24353 Takes an unprefixed group name and a select method, and returns the full
24354 (prefixed) Gnus group name.
24356 @item gnus-get-info
24357 @findex gnus-get-info
24358 Returns the group info list for @var{group}.
24360 @item gnus-group-unread
24361 @findex gnus-group-unread
24362 The number of unread articles in @var{group}, or @code{t} if that is
24366 @findex gnus-active
24367 The active entry for @var{group}.
24369 @item gnus-set-active
24370 @findex gnus-set-active
24371 Set the active entry for @var{group}.
24373 @item gnus-add-current-to-buffer-list
24374 @findex gnus-add-current-to-buffer-list
24375 Adds the current buffer to the list of buffers to be killed on Gnus
24378 @item gnus-continuum-version
24379 @findex gnus-continuum-version
24380 Takes a Gnus version string as a parameter and returns a floating point
24381 number. Earlier versions will always get a lower number than later
24384 @item gnus-group-read-only-p
24385 @findex gnus-group-read-only-p
24386 Says whether @var{group} is read-only or not.
24388 @item gnus-news-group-p
24389 @findex gnus-news-group-p
24390 Says whether @var{group} came from a news back end.
24392 @item gnus-ephemeral-group-p
24393 @findex gnus-ephemeral-group-p
24394 Says whether @var{group} is ephemeral or not.
24396 @item gnus-server-to-method
24397 @findex gnus-server-to-method
24398 Returns the select method corresponding to @var{server}.
24400 @item gnus-server-equal
24401 @findex gnus-server-equal
24402 Says whether two virtual servers are equal.
24404 @item gnus-group-native-p
24405 @findex gnus-group-native-p
24406 Says whether @var{group} is native or not.
24408 @item gnus-group-secondary-p
24409 @findex gnus-group-secondary-p
24410 Says whether @var{group} is secondary or not.
24412 @item gnus-group-foreign-p
24413 @findex gnus-group-foreign-p
24414 Says whether @var{group} is foreign or not.
24416 @item group-group-find-parameter
24417 @findex group-group-find-parameter
24418 Returns the parameter list of @var{group}. If given a second parameter,
24419 returns the value of that parameter for @var{group}.
24421 @item gnus-group-set-parameter
24422 @findex gnus-group-set-parameter
24423 Takes three parameters; @var{group}, @var{parameter} and @var{value}.
24425 @item gnus-narrow-to-body
24426 @findex gnus-narrow-to-body
24427 Narrows the current buffer to the body of the article.
24429 @item gnus-check-backend-function
24430 @findex gnus-check-backend-function
24431 Takes two parameters, @var{function} and @var{group}. If the back end
24432 @var{group} comes from supports @var{function}, return non-@code{nil}.
24435 (gnus-check-backend-function "request-scan" "nnml:misc")
24439 @item gnus-read-method
24440 @findex gnus-read-method
24441 Prompts the user for a select method.
24446 @node Back End Interface
24447 @subsection Back End Interface
24449 Gnus doesn't know anything about @sc{nntp}, spools, mail or virtual
24450 groups. It only knows how to talk to @dfn{virtual servers}. A virtual
24451 server is a @dfn{back end} and some @dfn{back end variables}. As examples
24452 of the first, we have @code{nntp}, @code{nnspool} and @code{nnmbox}. As
24453 examples of the latter we have @code{nntp-port-number} and
24454 @code{nnmbox-directory}.
24456 When Gnus asks for information from a back end---say @code{nntp}---on
24457 something, it will normally include a virtual server name in the
24458 function parameters. (If not, the back end should use the ``current''
24459 virtual server.) For instance, @code{nntp-request-list} takes a virtual
24460 server as its only (optional) parameter. If this virtual server hasn't
24461 been opened, the function should fail.
24463 Note that a virtual server name has no relation to some physical server
24464 name. Take this example:
24468 (nntp-address "ifi.uio.no")
24469 (nntp-port-number 4324))
24472 Here the virtual server name is @samp{odd-one} while the name of
24473 the physical server is @samp{ifi.uio.no}.
24475 The back ends should be able to switch between several virtual servers.
24476 The standard back ends implement this by keeping an alist of virtual
24477 server environments that they pull down/push up when needed.
24479 There are two groups of interface functions: @dfn{required functions},
24480 which must be present, and @dfn{optional functions}, which Gnus will
24481 always check for presence before attempting to call 'em.
24483 All these functions are expected to return data in the buffer
24484 @code{nntp-server-buffer} (@samp{ *nntpd*}), which is somewhat
24485 unfortunately named, but we'll have to live with it. When I talk about
24486 @dfn{resulting data}, I always refer to the data in that buffer. When I
24487 talk about @dfn{return value}, I talk about the function value returned by
24488 the function call. Functions that fail should return @code{nil} as the
24491 Some back ends could be said to be @dfn{server-forming} back ends, and
24492 some might be said not to be. The latter are back ends that generally
24493 only operate on one group at a time, and have no concept of ``server''
24494 -- they have a group, and they deliver info on that group and nothing
24497 Gnus identifies each message by way of group name and article number. A
24498 few remarks about these article numbers might be useful. First of all,
24499 the numbers are positive integers. Secondly, it is normally not
24500 possible for later articles to `re-use' older article numbers without
24501 confusing Gnus. That is, if a group has ever contained a message
24502 numbered 42, then no other message may get that number, or Gnus will get
24503 mightily confused.@footnote{See the function
24504 @code{nnchoke-request-update-info}, @ref{Optional Back End Functions}.}
24505 Third, article numbers must be assigned in order of arrival in the
24506 group; this is not necessarily the same as the date of the message.
24508 The previous paragraph already mentions all the `hard' restrictions that
24509 article numbers must fulfill. But it seems that it might be useful to
24510 assign @emph{consecutive} article numbers, for Gnus gets quite confused
24511 if there are holes in the article numbering sequence. However, due to
24512 the `no-reuse' restriction, holes cannot be avoided altogether. It's
24513 also useful for the article numbers to start at 1 to avoid running out
24514 of numbers as long as possible.
24516 Note that by convention, backends are named @code{nnsomething}, but
24517 Gnus also comes with some @code{nnnotbackends}, such as
24518 @file{nnheader.el}, @file{nnmail.el} and @file{nnoo.el}.
24520 In the examples and definitions I will refer to the imaginary back end
24523 @cindex @code{nnchoke}
24526 * Required Back End Functions:: Functions that must be implemented.
24527 * Optional Back End Functions:: Functions that need not be implemented.
24528 * Error Messaging:: How to get messages and report errors.
24529 * Writing New Back Ends:: Extending old back ends.
24530 * Hooking New Back Ends Into Gnus:: What has to be done on the Gnus end.
24531 * Mail-like Back Ends:: Some tips on mail back ends.
24535 @node Required Back End Functions
24536 @subsubsection Required Back End Functions
24540 @item (nnchoke-retrieve-headers ARTICLES &optional GROUP SERVER FETCH-OLD)
24542 @var{articles} is either a range of article numbers or a list of
24543 @code{Message-ID}s. Current back ends do not fully support either---only
24544 sequences (lists) of article numbers, and most back ends do not support
24545 retrieval of @code{Message-ID}s. But they should try for both.
24547 The result data should either be HEADs or @sc{nov} lines, and the result
24548 value should either be @code{headers} or @code{nov} to reflect this.
24549 This might later be expanded to @code{various}, which will be a mixture
24550 of HEADs and @sc{nov} lines, but this is currently not supported by Gnus.
24552 If @var{fetch-old} is non-@code{nil} it says to try fetching "extra
24553 headers", in some meaning of the word. This is generally done by
24554 fetching (at most) @var{fetch-old} extra headers less than the smallest
24555 article number in @code{articles}, and filling the gaps as well. The
24556 presence of this parameter can be ignored if the back end finds it
24557 cumbersome to follow the request. If this is non-@code{nil} and not a
24558 number, do maximum fetches.
24560 Here's an example HEAD:
24563 221 1056 Article retrieved.
24564 Path: ifi.uio.no!sturles
24565 From: sturles@@ifi.uio.no (Sturle Sunde)
24566 Newsgroups: ifi.discussion
24567 Subject: Re: Something very droll
24568 Date: 27 Oct 1994 14:02:57 +0100
24569 Organization: Dept. of Informatics, University of Oslo, Norway
24571 Message-ID: <38o8e1$a0o@@holmenkollen.ifi.uio.no>
24572 References: <38jdmq$4qu@@visbur.ifi.uio.no>
24573 NNTP-Posting-Host: holmenkollen.ifi.uio.no
24577 So a @code{headers} return value would imply that there's a number of
24578 these in the data buffer.
24580 Here's a BNF definition of such a buffer:
24584 head = error / valid-head
24585 error-message = [ "4" / "5" ] 2number " " <error message> eol
24586 valid-head = valid-message *header "." eol
24587 valid-message = "221 " <number> " Article retrieved." eol
24588 header = <text> eol
24591 If the return value is @code{nov}, the data buffer should contain
24592 @dfn{network overview database} lines. These are basically fields
24596 nov-buffer = *nov-line
24597 nov-line = 8*9 [ field <TAB> ] eol
24598 field = <text except TAB>
24601 For a closer look at what should be in those fields,
24605 @item (nnchoke-open-server SERVER &optional DEFINITIONS)
24607 @var{server} is here the virtual server name. @var{definitions} is a
24608 list of @code{(VARIABLE VALUE)} pairs that define this virtual server.
24610 If the server can't be opened, no error should be signaled. The back end
24611 may then choose to refuse further attempts at connecting to this
24612 server. In fact, it should do so.
24614 If the server is opened already, this function should return a
24615 non-@code{nil} value. There should be no data returned.
24618 @item (nnchoke-close-server &optional SERVER)
24620 Close connection to @var{server} and free all resources connected
24621 to it. Return @code{nil} if the server couldn't be closed for some
24624 There should be no data returned.
24627 @item (nnchoke-request-close)
24629 Close connection to all servers and free all resources that the back end
24630 have reserved. All buffers that have been created by that back end
24631 should be killed. (Not the @code{nntp-server-buffer}, though.) This
24632 function is generally only called when Gnus is shutting down.
24634 There should be no data returned.
24637 @item (nnchoke-server-opened &optional SERVER)
24639 If @var{server} is the current virtual server, and the connection to the
24640 physical server is alive, then this function should return a
24641 non-@code{nil} vlue. This function should under no circumstances
24642 attempt to reconnect to a server we have lost connection to.
24644 There should be no data returned.
24647 @item (nnchoke-status-message &optional SERVER)
24649 This function should return the last error message from @var{server}.
24651 There should be no data returned.
24654 @item (nnchoke-request-article ARTICLE &optional GROUP SERVER TO-BUFFER)
24656 The result data from this function should be the article specified by
24657 @var{article}. This might either be a @code{Message-ID} or a number.
24658 It is optional whether to implement retrieval by @code{Message-ID}, but
24659 it would be nice if that were possible.
24661 If @var{to-buffer} is non-@code{nil}, the result data should be returned
24662 in this buffer instead of the normal data buffer. This is to make it
24663 possible to avoid copying large amounts of data from one buffer to
24664 another, while Gnus mainly requests articles to be inserted directly
24665 into its article buffer.
24667 If it is at all possible, this function should return a cons cell where
24668 the @code{car} is the group name the article was fetched from, and the @code{cdr} is
24669 the article number. This will enable Gnus to find out what the real
24670 group and article numbers are when fetching articles by
24671 @code{Message-ID}. If this isn't possible, @code{t} should be returned
24672 on successful article retrieval.
24675 @item (nnchoke-request-group GROUP &optional SERVER FAST)
24677 Get data on @var{group}. This function also has the side effect of
24678 making @var{group} the current group.
24680 If @var{fast}, don't bother to return useful data, just make @var{group}
24683 Here's an example of some result data and a definition of the same:
24686 211 56 1000 1059 ifi.discussion
24689 The first number is the status, which should be 211. Next is the
24690 total number of articles in the group, the lowest article number, the
24691 highest article number, and finally the group name. Note that the total
24692 number of articles may be less than one might think while just
24693 considering the highest and lowest article numbers, but some articles
24694 may have been canceled. Gnus just discards the total-number, so
24695 whether one should take the bother to generate it properly (if that is a
24696 problem) is left as an exercise to the reader. If the group contains no
24697 articles, the lowest article number should be reported as 1 and the
24701 group-status = [ error / info ] eol
24702 error = [ "4" / "5" ] 2<number> " " <Error message>
24703 info = "211 " 3* [ <number> " " ] <string>
24707 @item (nnchoke-close-group GROUP &optional SERVER)
24709 Close @var{group} and free any resources connected to it. This will be
24710 a no-op on most back ends.
24712 There should be no data returned.
24715 @item (nnchoke-request-list &optional SERVER)
24717 Return a list of all groups available on @var{server}. And that means
24720 Here's an example from a server that only carries two groups:
24723 ifi.test 0000002200 0000002000 y
24724 ifi.discussion 3324 3300 n
24727 On each line we have a group name, then the highest article number in
24728 that group, the lowest article number, and finally a flag. If the group
24729 contains no articles, the lowest article number should be reported as 1
24730 and the highest as 0.
24733 active-file = *active-line
24734 active-line = name " " <number> " " <number> " " flags eol
24736 flags = "n" / "y" / "m" / "x" / "j" / "=" name
24739 The flag says whether the group is read-only (@samp{n}), is moderated
24740 (@samp{m}), is dead (@samp{x}), is aliased to some other group
24741 (@samp{=other-group}) or none of the above (@samp{y}).
24744 @item (nnchoke-request-post &optional SERVER)
24746 This function should post the current buffer. It might return whether
24747 the posting was successful or not, but that's not required. If, for
24748 instance, the posting is done asynchronously, it has generally not been
24749 completed by the time this function concludes. In that case, this
24750 function should set up some kind of sentinel to beep the user loud and
24751 clear if the posting could not be completed.
24753 There should be no result data from this function.
24758 @node Optional Back End Functions
24759 @subsubsection Optional Back End Functions
24763 @item (nnchoke-retrieve-groups GROUPS &optional SERVER)
24765 @var{groups} is a list of groups, and this function should request data
24766 on all those groups. How it does it is of no concern to Gnus, but it
24767 should attempt to do this in a speedy fashion.
24769 The return value of this function can be either @code{active} or
24770 @code{group}, which says what the format of the result data is. The
24771 former is in the same format as the data from
24772 @code{nnchoke-request-list}, while the latter is a buffer full of lines
24773 in the same format as @code{nnchoke-request-group} gives.
24776 group-buffer = *active-line / *group-status
24780 @item (nnchoke-request-update-info GROUP INFO &optional SERVER)
24782 A Gnus group info (@pxref{Group Info}) is handed to the back end for
24783 alterations. This comes in handy if the back end really carries all the
24784 information (as is the case with virtual and imap groups). This
24785 function should destructively alter the info to suit its needs, and
24786 should return a non-nil value.
24788 There should be no result data from this function.
24791 @item (nnchoke-request-type GROUP &optional ARTICLE)
24793 When the user issues commands for ``sending news'' (@kbd{F} in the
24794 summary buffer, for instance), Gnus has to know whether the article the
24795 user is following up on is news or mail. This function should return
24796 @code{news} if @var{article} in @var{group} is news, @code{mail} if it
24797 is mail and @code{unknown} if the type can't be decided. (The
24798 @var{article} parameter is necessary in @code{nnvirtual} groups which
24799 might very well combine mail groups and news groups.) Both @var{group}
24800 and @var{article} may be @code{nil}.
24802 There should be no result data from this function.
24805 @item (nnchoke-request-set-mark GROUP ACTION &optional SERVER)
24807 Set/remove/add marks on articles. Normally Gnus handles the article
24808 marks (such as read, ticked, expired etc) internally, and store them in
24809 @code{~/.newsrc.eld}. Some back ends (such as @sc{imap}) however carry
24810 all information about the articles on the server, so Gnus need to
24811 propagate the mark information to the server.
24813 ACTION is a list of mark setting requests, having this format:
24816 (RANGE ACTION MARK)
24819 RANGE is a range of articles you wish to update marks on. ACTION is
24820 @code{add} or @code{del}, used to add marks or remove marks
24821 (preserving all marks not mentioned). MARK is a list of marks; where
24822 each mark is a symbol. Currently used marks are @code{read},
24823 @code{tick}, @code{reply}, @code{expire}, @code{killed},
24824 @code{dormant}, @code{save}, @code{download}, @code{unsend},
24825 @code{forward} and @code{recent}, but your back end should, if
24826 possible, not limit itself to these.
24828 Given contradictory actions, the last action in the list should be the
24829 effective one. That is, if your action contains a request to add the
24830 @code{tick} mark on article 1 and, later in the list, a request to
24831 remove the mark on the same article, the mark should in fact be removed.
24833 An example action list:
24836 (((5 12 30) 'del '(tick))
24837 ((10 . 90) 'add '(read expire))
24838 ((92 94) 'del '(read)))
24841 The function should return a range of articles it wasn't able to set the
24842 mark on (currently not used for anything).
24844 There should be no result data from this function.
24846 @item (nnchoke-request-update-mark GROUP ARTICLE MARK)
24848 If the user tries to set a mark that the back end doesn't like, this
24849 function may change the mark. Gnus will use whatever this function
24850 returns as the mark for @var{article} instead of the original
24851 @var{mark}. If the back end doesn't care, it must return the original
24852 @var{mark}, and not @code{nil} or any other type of garbage.
24854 The only use for this I can see is what @code{nnvirtual} does with
24855 it---if a component group is auto-expirable, marking an article as read
24856 in the virtual group should result in the article being marked as
24859 There should be no result data from this function.
24862 @item (nnchoke-request-scan &optional GROUP SERVER)
24864 This function may be called at any time (by Gnus or anything else) to
24865 request that the back end check for incoming articles, in one way or
24866 another. A mail back end will typically read the spool file or query the
24867 POP server when this function is invoked. The @var{group} doesn't have
24868 to be heeded---if the back end decides that it is too much work just
24869 scanning for a single group, it may do a total scan of all groups. It
24870 would be nice, however, to keep things local if that's practical.
24872 There should be no result data from this function.
24875 @item (nnchoke-request-group-description GROUP &optional SERVER)
24877 The result data from this function should be a description of
24881 description-line = name <TAB> description eol
24883 description = <text>
24886 @item (nnchoke-request-list-newsgroups &optional SERVER)
24888 The result data from this function should be the description of all
24889 groups available on the server.
24892 description-buffer = *description-line
24896 @item (nnchoke-request-newgroups DATE &optional SERVER)
24898 The result data from this function should be all groups that were
24899 created after @samp{date}, which is in normal human-readable date format
24900 (i.e., the date format used in mail and news headers, and returned by
24901 the function @code{message-make-date} by default). The data should be
24902 in the active buffer format.
24904 It is okay for this function to return `too many' groups; some back ends
24905 might find it cheaper to return the full list of groups, rather than
24906 just the new groups. But don't do this for back ends with many groups.
24907 Normally, if the user creates the groups herself, there won't be too
24908 many groups, so @code{nnml} and the like are probably safe. But for
24909 back ends like @code{nntp}, where the groups have been created by the
24910 server, it is quite likely that there can be many groups.
24913 @item (nnchoke-request-create-group GROUP &optional SERVER)
24915 This function should create an empty group with name @var{group}.
24917 There should be no return data.
24920 @item (nnchoke-request-expire-articles ARTICLES &optional GROUP SERVER FORCE)
24922 This function should run the expiry process on all articles in the
24923 @var{articles} range (which is currently a simple list of article
24924 numbers.) It is left up to the back end to decide how old articles
24925 should be before they are removed by this function. If @var{force} is
24926 non-@code{nil}, all @var{articles} should be deleted, no matter how new
24929 This function should return a list of articles that it did not/was not
24932 There should be no result data returned.
24935 @item (nnchoke-request-move-article ARTICLE GROUP SERVER ACCEPT-FORM
24938 This function should move @var{article} (which is a number) from
24939 @var{group} by calling @var{accept-form}.
24941 This function should ready the article in question for moving by
24942 removing any header lines it has added to the article, and generally
24943 should ``tidy up'' the article. Then it should @code{eval}
24944 @var{accept-form} in the buffer where the ``tidy'' article is. This
24945 will do the actual copying. If this @code{eval} returns a
24946 non-@code{nil} value, the article should be removed.
24948 If @var{last} is @code{nil}, that means that there is a high likelihood
24949 that there will be more requests issued shortly, so that allows some
24952 The function should return a cons where the @code{car} is the group name and
24953 the @code{cdr} is the article number that the article was entered as.
24955 The group should exist before the backend is asked to accept the
24956 article for that group.
24958 There should be no data returned.
24961 @item (nnchoke-request-accept-article GROUP &optional SERVER LAST)
24963 This function takes the current buffer and inserts it into @var{group}.
24964 If @var{last} in @code{nil}, that means that there will be more calls to
24965 this function in short order.
24967 The function should return a cons where the @code{car} is the group name and
24968 the @code{cdr} is the article number that the article was entered as.
24970 There should be no data returned.
24973 @item (nnchoke-request-replace-article ARTICLE GROUP BUFFER)
24975 This function should remove @var{article} (which is a number) from
24976 @var{group} and insert @var{buffer} there instead.
24978 There should be no data returned.
24981 @item (nnchoke-request-delete-group GROUP FORCE &optional SERVER)
24983 This function should delete @var{group}. If @var{force}, it should
24984 really delete all the articles in the group, and then delete the group
24985 itself. (If there is such a thing as ``the group itself''.)
24987 There should be no data returned.
24990 @item (nnchoke-request-rename-group GROUP NEW-NAME &optional SERVER)
24992 This function should rename @var{group} into @var{new-name}. All
24993 articles in @var{group} should move to @var{new-name}.
24995 There should be no data returned.
25000 @node Error Messaging
25001 @subsubsection Error Messaging
25003 @findex nnheader-report
25004 @findex nnheader-get-report
25005 The back ends should use the function @code{nnheader-report} to report
25006 error conditions---they should not raise errors when they aren't able to
25007 perform a request. The first argument to this function is the back end
25008 symbol, and the rest are interpreted as arguments to @code{format} if
25009 there are multiple of them, or just a string if there is one of them.
25010 This function must always returns @code{nil}.
25013 (nnheader-report 'nnchoke "You did something totally bogus")
25015 (nnheader-report 'nnchoke "Could not request group %s" group)
25018 Gnus, in turn, will call @code{nnheader-get-report} when it gets a
25019 @code{nil} back from a server, and this function returns the most
25020 recently reported message for the back end in question. This function
25021 takes one argument---the server symbol.
25023 Internally, these functions access @var{back-end}@code{-status-string},
25024 so the @code{nnchoke} back end will have its error message stored in
25025 @code{nnchoke-status-string}.
25028 @node Writing New Back Ends
25029 @subsubsection Writing New Back Ends
25031 Many back ends are quite similar. @code{nnml} is just like
25032 @code{nnspool}, but it allows you to edit the articles on the server.
25033 @code{nnmh} is just like @code{nnml}, but it doesn't use an active file,
25034 and it doesn't maintain overview databases. @code{nndir} is just like
25035 @code{nnml}, but it has no concept of ``groups'', and it doesn't allow
25038 It would make sense if it were possible to ``inherit'' functions from
25039 back ends when writing new back ends. And, indeed, you can do that if you
25040 want to. (You don't have to if you don't want to, of course.)
25042 All the back ends declare their public variables and functions by using a
25043 package called @code{nnoo}.
25045 To inherit functions from other back ends (and allow other back ends to
25046 inherit functions from the current back end), you should use the
25052 This macro declares the first parameter to be a child of the subsequent
25053 parameters. For instance:
25056 (nnoo-declare nndir
25060 @code{nndir} has declared here that it intends to inherit functions from
25061 both @code{nnml} and @code{nnmh}.
25064 This macro is equivalent to @code{defvar}, but registers the variable as
25065 a public server variable. Most state-oriented variables should be
25066 declared with @code{defvoo} instead of @code{defvar}.
25068 In addition to the normal @code{defvar} parameters, it takes a list of
25069 variables in the parent back ends to map the variable to when executing
25070 a function in those back ends.
25073 (defvoo nndir-directory nil
25074 "Where nndir will look for groups."
25075 nnml-current-directory nnmh-current-directory)
25078 This means that @code{nnml-current-directory} will be set to
25079 @code{nndir-directory} when an @code{nnml} function is called on behalf
25080 of @code{nndir}. (The same with @code{nnmh}.)
25082 @item nnoo-define-basics
25083 This macro defines some common functions that almost all back ends should
25087 (nnoo-define-basics nndir)
25091 This macro is just like @code{defun} and takes the same parameters. In
25092 addition to doing the normal @code{defun} things, it registers the
25093 function as being public so that other back ends can inherit it.
25095 @item nnoo-map-functions
25096 This macro allows mapping of functions from the current back end to
25097 functions from the parent back ends.
25100 (nnoo-map-functions nndir
25101 (nnml-retrieve-headers 0 nndir-current-group 0 0)
25102 (nnmh-request-article 0 nndir-current-group 0 0))
25105 This means that when @code{nndir-retrieve-headers} is called, the first,
25106 third, and fourth parameters will be passed on to
25107 @code{nnml-retrieve-headers}, while the second parameter is set to the
25108 value of @code{nndir-current-group}.
25111 This macro allows importing functions from back ends. It should be the
25112 last thing in the source file, since it will only define functions that
25113 haven't already been defined.
25119 nnmh-request-newgroups)
25123 This means that calls to @code{nndir-request-list} should just be passed
25124 on to @code{nnmh-request-list}, while all public functions from
25125 @code{nnml} that haven't been defined in @code{nndir} yet should be
25130 Below is a slightly shortened version of the @code{nndir} back end.
25133 ;;; nndir.el --- single directory newsgroup access for Gnus
25134 ;; Copyright (C) 1995,96 Free Software Foundation, Inc.
25138 (require 'nnheader)
25142 (eval-when-compile (require 'cl))
25144 (nnoo-declare nndir
25147 (defvoo nndir-directory nil
25148 "Where nndir will look for groups."
25149 nnml-current-directory nnmh-current-directory)
25151 (defvoo nndir-nov-is-evil nil
25152 "*Non-nil means that nndir will never retrieve NOV headers."
25155 (defvoo nndir-current-group ""
25157 nnml-current-group nnmh-current-group)
25158 (defvoo nndir-top-directory nil nil nnml-directory nnmh-directory)
25159 (defvoo nndir-get-new-mail nil nil nnml-get-new-mail nnmh-get-new-mail)
25161 (defvoo nndir-status-string "" nil nnmh-status-string)
25162 (defconst nndir-version "nndir 1.0")
25164 ;;; Interface functions.
25166 (nnoo-define-basics nndir)
25168 (deffoo nndir-open-server (server &optional defs)
25169 (setq nndir-directory
25170 (or (cadr (assq 'nndir-directory defs))
25172 (unless (assq 'nndir-directory defs)
25173 (push `(nndir-directory ,server) defs))
25174 (push `(nndir-current-group
25175 ,(file-name-nondirectory
25176 (directory-file-name nndir-directory)))
25178 (push `(nndir-top-directory
25179 ,(file-name-directory (directory-file-name nndir-directory)))
25181 (nnoo-change-server 'nndir server defs))
25183 (nnoo-map-functions nndir
25184 (nnml-retrieve-headers 0 nndir-current-group 0 0)
25185 (nnmh-request-article 0 nndir-current-group 0 0)
25186 (nnmh-request-group nndir-current-group 0 0)
25187 (nnmh-close-group nndir-current-group 0))
25191 nnmh-status-message
25193 nnmh-request-newgroups))
25199 @node Hooking New Back Ends Into Gnus
25200 @subsubsection Hooking New Back Ends Into Gnus
25202 @vindex gnus-valid-select-methods
25203 @findex gnus-declare-backend
25204 Having Gnus start using your new back end is rather easy---you just
25205 declare it with the @code{gnus-declare-backend} functions. This will
25206 enter the back end into the @code{gnus-valid-select-methods} variable.
25208 @code{gnus-declare-backend} takes two parameters---the back end name and
25209 an arbitrary number of @dfn{abilities}.
25214 (gnus-declare-backend "nnchoke" 'mail 'respool 'address)
25217 The above line would then go in the @file{nnchoke.el} file.
25219 The abilities can be:
25223 This is a mailish back end---followups should (probably) go via mail.
25225 This is a newsish back end---followups should (probably) go via news.
25227 This back end supports both mail and news.
25229 This is neither a post nor mail back end---it's something completely
25232 It supports respooling---or rather, it is able to modify its source
25233 articles and groups.
25235 The name of the server should be in the virtual server name. This is
25236 true for almost all back ends.
25237 @item prompt-address
25238 The user should be prompted for an address when doing commands like
25239 @kbd{B} in the group buffer. This is true for back ends like
25240 @code{nntp}, but not @code{nnmbox}, for instance.
25244 @node Mail-like Back Ends
25245 @subsubsection Mail-like Back Ends
25247 One of the things that separate the mail back ends from the rest of the
25248 back ends is the heavy dependence by most of the mail back ends on
25249 common functions in @file{nnmail.el}. For instance, here's the
25250 definition of @code{nnml-request-scan}:
25253 (deffoo nnml-request-scan (&optional group server)
25254 (setq nnml-article-file-alist nil)
25255 (nnmail-get-new-mail 'nnml 'nnml-save-nov nnml-directory group))
25258 It simply calls @code{nnmail-get-new-mail} with a few parameters,
25259 and @code{nnmail} takes care of all the moving and splitting of the
25262 This function takes four parameters.
25266 This should be a symbol to designate which back end is responsible for
25269 @item exit-function
25270 This function should be called after the splitting has been performed.
25272 @item temp-directory
25273 Where the temporary files should be stored.
25276 This optional argument should be a group name if the splitting is to be
25277 performed for one group only.
25280 @code{nnmail-get-new-mail} will call @var{back-end}@code{-save-mail} to
25281 save each article. @var{back-end}@code{-active-number} will be called to
25282 find the article number assigned to this article.
25284 The function also uses the following variables:
25285 @var{back-end}@code{-get-new-mail} (to see whether to get new mail for
25286 this back end); and @var{back-end}@code{-group-alist} and
25287 @var{back-end}@code{-active-file} to generate the new active file.
25288 @var{back-end}@code{-group-alist} should be a group-active alist, like
25292 (("a-group" (1 . 10))
25293 ("some-group" (34 . 39)))
25297 @node Score File Syntax
25298 @subsection Score File Syntax
25300 Score files are meant to be easily parseable, but yet extremely
25301 mallable. It was decided that something that had the same read syntax
25302 as an Emacs Lisp list would fit that spec.
25304 Here's a typical score file:
25308 ("win95" -10000 nil s)
25315 BNF definition of a score file:
25318 score-file = "" / "(" *element ")"
25319 element = rule / atom
25320 rule = string-rule / number-rule / date-rule
25321 string-rule = "(" quote string-header quote space *string-match ")"
25322 number-rule = "(" quote number-header quote space *number-match ")"
25323 date-rule = "(" quote date-header quote space *date-match ")"
25325 string-header = "subject" / "from" / "references" / "message-id" /
25326 "xref" / "body" / "head" / "all" / "followup"
25327 number-header = "lines" / "chars"
25328 date-header = "date"
25329 string-match = "(" quote <string> quote [ "" / [ space score [ "" /
25330 space date [ "" / [ space string-match-t ] ] ] ] ] ")"
25331 score = "nil" / <integer>
25332 date = "nil" / <natural number>
25333 string-match-t = "nil" / "s" / "substring" / "S" / "Substring" /
25334 "r" / "regex" / "R" / "Regex" /
25335 "e" / "exact" / "E" / "Exact" /
25336 "f" / "fuzzy" / "F" / "Fuzzy"
25337 number-match = "(" <integer> [ "" / [ space score [ "" /
25338 space date [ "" / [ space number-match-t ] ] ] ] ] ")"
25339 number-match-t = "nil" / "=" / "<" / ">" / ">=" / "<="
25340 date-match = "(" quote <string> quote [ "" / [ space score [ "" /
25341 space date [ "" / [ space date-match-t ] ] ] ] ")"
25342 date-match-t = "nil" / "at" / "before" / "after"
25343 atom = "(" [ required-atom / optional-atom ] ")"
25344 required-atom = mark / expunge / mark-and-expunge / files /
25345 exclude-files / read-only / touched
25346 optional-atom = adapt / local / eval
25347 mark = "mark" space nil-or-number
25348 nil-or-number = "nil" / <integer>
25349 expunge = "expunge" space nil-or-number
25350 mark-and-expunge = "mark-and-expunge" space nil-or-number
25351 files = "files" *[ space <string> ]
25352 exclude-files = "exclude-files" *[ space <string> ]
25353 read-only = "read-only" [ space "nil" / space "t" ]
25354 adapt = "adapt" [ space "ignore" / space "t" / space adapt-rule ]
25355 adapt-rule = "(" *[ <string> *[ "(" <string> <integer> ")" ] ")"
25356 local = "local" *[ space "(" <string> space <form> ")" ]
25357 eval = "eval" space <form>
25358 space = *[ " " / <TAB> / <NEWLINE> ]
25361 Any unrecognized elements in a score file should be ignored, but not
25364 As you can see, white space is needed, but the type and amount of white
25365 space is irrelevant. This means that formatting of the score file is
25366 left up to the programmer---if it's simpler to just spew it all out on
25367 one looong line, then that's ok.
25369 The meaning of the various atoms are explained elsewhere in this
25370 manual (@pxref{Score File Format}).
25374 @subsection Headers
25376 Internally Gnus uses a format for storing article headers that
25377 corresponds to the @sc{nov} format in a mysterious fashion. One could
25378 almost suspect that the author looked at the @sc{nov} specification and
25379 just shamelessly @emph{stole} the entire thing, and one would be right.
25381 @dfn{Header} is a severely overloaded term. ``Header'' is used in
25382 RFC 1036 to talk about lines in the head of an article (e.g.,
25383 @code{From}). It is used by many people as a synonym for
25384 ``head''---``the header and the body''. (That should be avoided, in my
25385 opinion.) And Gnus uses a format internally that it calls ``header'',
25386 which is what I'm talking about here. This is a 9-element vector,
25387 basically, with each header (ouch) having one slot.
25389 These slots are, in order: @code{number}, @code{subject}, @code{from},
25390 @code{date}, @code{id}, @code{references}, @code{chars}, @code{lines},
25391 @code{xref}, and @code{extra}. There are macros for accessing and
25392 setting these slots---they all have predictable names beginning with
25393 @code{mail-header-} and @code{mail-header-set-}, respectively.
25395 All these slots contain strings, except the @code{extra} slot, which
25396 contains an alist of header/value pairs (@pxref{To From Newsgroups}).
25402 @sc{gnus} introduced a concept that I found so useful that I've started
25403 using it a lot and have elaborated on it greatly.
25405 The question is simple: If you have a large amount of objects that are
25406 identified by numbers (say, articles, to take a @emph{wild} example)
25407 that you want to qualify as being ``included'', a normal sequence isn't
25408 very useful. (A 200,000 length sequence is a bit long-winded.)
25410 The solution is as simple as the question: You just collapse the
25414 (1 2 3 4 5 6 10 11 12)
25417 is transformed into
25420 ((1 . 6) (10 . 12))
25423 To avoid having those nasty @samp{(13 . 13)} elements to denote a
25424 lonesome object, a @samp{13} is a valid element:
25427 ((1 . 6) 7 (10 . 12))
25430 This means that comparing two ranges to find out whether they are equal
25431 is slightly tricky:
25434 ((1 . 5) 7 8 (10 . 12))
25440 ((1 . 5) (7 . 8) (10 . 12))
25443 are equal. In fact, any non-descending list is a range:
25449 is a perfectly valid range, although a pretty long-winded one. This is
25456 and is equal to the previous range.
25458 Here's a BNF definition of ranges. Of course, one must remember the
25459 semantic requirement that the numbers are non-descending. (Any number
25460 of repetition of the same number is allowed, but apt to disappear in
25464 range = simple-range / normal-range
25465 simple-range = "(" number " . " number ")"
25466 normal-range = "(" start-contents ")"
25467 contents = "" / simple-range *[ " " contents ] /
25468 number *[ " " contents ]
25471 Gnus currently uses ranges to keep track of read articles and article
25472 marks. I plan on implementing a number of range operators in C if The
25473 Powers That Be are willing to let me. (I haven't asked yet, because I
25474 need to do some more thinking on what operators I need to make life
25475 totally range-based without ever having to convert back to normal
25480 @subsection Group Info
25482 Gnus stores all permanent info on groups in a @dfn{group info} list.
25483 This list is from three to six elements (or more) long and exhaustively
25484 describes the group.
25486 Here are two example group infos; one is a very simple group while the
25487 second is a more complex one:
25490 ("no.group" 5 ((1 . 54324)))
25492 ("nnml:my.mail" 3 ((1 . 5) 9 (20 . 55))
25493 ((tick (15 . 19)) (replied 3 6 (19 . 3)))
25495 ((auto-expire . t) (to-address . "ding@@gnus.org")))
25498 The first element is the @dfn{group name}---as Gnus knows the group,
25499 anyway. The second element is the @dfn{subscription level}, which
25500 normally is a small integer. (It can also be the @dfn{rank}, which is a
25501 cons cell where the @code{car} is the level and the @code{cdr} is the
25502 score.) The third element is a list of ranges of read articles. The
25503 fourth element is a list of lists of article marks of various kinds.
25504 The fifth element is the select method (or virtual server, if you like).
25505 The sixth element is a list of @dfn{group parameters}, which is what
25506 this section is about.
25508 Any of the last three elements may be missing if they are not required.
25509 In fact, the vast majority of groups will normally only have the first
25510 three elements, which saves quite a lot of cons cells.
25512 Here's a BNF definition of the group info format:
25515 info = "(" group space ralevel space read
25516 [ "" / [ space marks-list [ "" / [ space method [ "" /
25517 space parameters ] ] ] ] ] ")"
25518 group = quote <string> quote
25519 ralevel = rank / level
25520 level = <integer in the range of 1 to inf>
25521 rank = "(" level "." score ")"
25522 score = <integer in the range of 1 to inf>
25524 marks-lists = nil / "(" *marks ")"
25525 marks = "(" <string> range ")"
25526 method = "(" <string> *elisp-forms ")"
25527 parameters = "(" *elisp-forms ")"
25530 Actually that @samp{marks} rule is a fib. A @samp{marks} is a
25531 @samp{<string>} consed on to a @samp{range}, but that's a bitch to say
25534 If you have a Gnus info and want to access the elements, Gnus offers a
25535 series of macros for getting/setting these elements.
25538 @item gnus-info-group
25539 @itemx gnus-info-set-group
25540 @findex gnus-info-group
25541 @findex gnus-info-set-group
25542 Get/set the group name.
25544 @item gnus-info-rank
25545 @itemx gnus-info-set-rank
25546 @findex gnus-info-rank
25547 @findex gnus-info-set-rank
25548 Get/set the group rank (@pxref{Group Score}).
25550 @item gnus-info-level
25551 @itemx gnus-info-set-level
25552 @findex gnus-info-level
25553 @findex gnus-info-set-level
25554 Get/set the group level.
25556 @item gnus-info-score
25557 @itemx gnus-info-set-score
25558 @findex gnus-info-score
25559 @findex gnus-info-set-score
25560 Get/set the group score (@pxref{Group Score}).
25562 @item gnus-info-read
25563 @itemx gnus-info-set-read
25564 @findex gnus-info-read
25565 @findex gnus-info-set-read
25566 Get/set the ranges of read articles.
25568 @item gnus-info-marks
25569 @itemx gnus-info-set-marks
25570 @findex gnus-info-marks
25571 @findex gnus-info-set-marks
25572 Get/set the lists of ranges of marked articles.
25574 @item gnus-info-method
25575 @itemx gnus-info-set-method
25576 @findex gnus-info-method
25577 @findex gnus-info-set-method
25578 Get/set the group select method.
25580 @item gnus-info-params
25581 @itemx gnus-info-set-params
25582 @findex gnus-info-params
25583 @findex gnus-info-set-params
25584 Get/set the group parameters.
25587 All the getter functions take one parameter---the info list. The setter
25588 functions take two parameters---the info list and the new value.
25590 The last three elements in the group info aren't mandatory, so it may be
25591 necessary to extend the group info before setting the element. If this
25592 is necessary, you can just pass on a non-@code{nil} third parameter to
25593 the three final setter functions to have this happen automatically.
25596 @node Extended Interactive
25597 @subsection Extended Interactive
25598 @cindex interactive
25599 @findex gnus-interactive
25601 Gnus extends the standard Emacs @code{interactive} specification
25602 slightly to allow easy use of the symbolic prefix (@pxref{Symbolic
25603 Prefixes}). Here's an example of how this is used:
25606 (defun gnus-summary-increase-score (&optional score symp)
25607 (interactive (gnus-interactive "P\ny"))
25612 The best thing to do would have been to implement
25613 @code{gnus-interactive} as a macro which would have returned an
25614 @code{interactive} form, but this isn't possible since Emacs checks
25615 whether a function is interactive or not by simply doing an @code{assq}
25616 on the lambda form. So, instead we have @code{gnus-interactive}
25617 function that takes a string and returns values that are usable to
25618 @code{interactive}.
25620 This function accepts (almost) all normal @code{interactive} specs, but
25625 @vindex gnus-current-prefix-symbol
25626 The current symbolic prefix---the @code{gnus-current-prefix-symbol}
25630 @vindex gnus-current-prefix-symbols
25631 A list of the current symbolic prefixes---the
25632 @code{gnus-current-prefix-symbol} variable.
25635 The current article number---the @code{gnus-summary-article-number}
25639 The current article header---the @code{gnus-summary-article-header}
25643 The current group name---the @code{gnus-group-group-name}
25649 @node Emacs/XEmacs Code
25650 @subsection Emacs/XEmacs Code
25654 While Gnus runs under Emacs, XEmacs and Mule, I decided that one of the
25655 platforms must be the primary one. I chose Emacs. Not because I don't
25656 like XEmacs or Mule, but because it comes first alphabetically.
25658 This means that Gnus will byte-compile under Emacs with nary a warning,
25659 while XEmacs will pump out gigabytes of warnings while byte-compiling.
25660 As I use byte-compilation warnings to help me root out trivial errors in
25661 Gnus, that's very useful.
25663 I've also consistently used Emacs function interfaces, but have used
25664 Gnusey aliases for the functions. To take an example: Emacs defines a
25665 @code{run-at-time} function while XEmacs defines a @code{start-itimer}
25666 function. I then define a function called @code{gnus-run-at-time} that
25667 takes the same parameters as the Emacs @code{run-at-time}. When running
25668 Gnus under Emacs, the former function is just an alias for the latter.
25669 However, when running under XEmacs, the former is an alias for the
25670 following function:
25673 (defun gnus-xmas-run-at-time (time repeat function &rest args)
25677 (,function ,@@args))
25681 This sort of thing has been done for bunches of functions. Gnus does
25682 not redefine any native Emacs functions while running under XEmacs---it
25683 does this @code{defalias} thing with Gnus equivalents instead. Cleaner
25686 In the cases where the XEmacs function interface was obviously cleaner,
25687 I used it instead. For example @code{gnus-region-active-p} is an alias
25688 for @code{region-active-p} in XEmacs, whereas in Emacs it is a function.
25690 Of course, I could have chosen XEmacs as my native platform and done
25691 mapping functions the other way around. But I didn't. The performance
25692 hit these indirections impose on Gnus under XEmacs should be slight.
25695 @node Various File Formats
25696 @subsection Various File Formats
25699 * Active File Format:: Information on articles and groups available.
25700 * Newsgroups File Format:: Group descriptions.
25704 @node Active File Format
25705 @subsubsection Active File Format
25707 The active file lists all groups available on the server in
25708 question. It also lists the highest and lowest current article numbers
25711 Here's an excerpt from a typical active file:
25714 soc.motss 296030 293865 y
25715 alt.binaries.pictures.fractals 3922 3913 n
25716 comp.sources.unix 1605 1593 m
25717 comp.binaries.ibm.pc 5097 5089 y
25718 no.general 1000 900 y
25721 Here's a pseudo-BNF definition of this file:
25724 active = *group-line
25725 group-line = group spc high-number spc low-number spc flag <NEWLINE>
25726 group = <non-white-space string>
25728 high-number = <non-negative integer>
25729 low-number = <positive integer>
25730 flag = "y" / "n" / "m" / "j" / "x" / "=" group
25733 For a full description of this file, see the manual pages for
25734 @samp{innd}, in particular @samp{active(5)}.
25737 @node Newsgroups File Format
25738 @subsubsection Newsgroups File Format
25740 The newsgroups file lists groups along with their descriptions. Not all
25741 groups on the server have to be listed, and not all groups in the file
25742 have to exist on the server. The file is meant purely as information to
25745 The format is quite simple; a group name, a tab, and the description.
25746 Here's the definition:
25750 line = group tab description <NEWLINE>
25751 group = <non-white-space string>
25753 description = <string>
25758 @node Emacs for Heathens
25759 @section Emacs for Heathens
25761 Believe it or not, but some people who use Gnus haven't really used
25762 Emacs much before they embarked on their journey on the Gnus Love Boat.
25763 If you are one of those unfortunates whom ``@kbd{C-M-a}'', ``kill the
25764 region'', and ``set @code{gnus-flargblossen} to an alist where the key
25765 is a regexp that is used for matching on the group name'' are magical
25766 phrases with little or no meaning, then this appendix is for you. If
25767 you are already familiar with Emacs, just ignore this and go fondle your
25771 * Keystrokes:: Entering text and executing commands.
25772 * Emacs Lisp:: The built-in Emacs programming language.
25777 @subsection Keystrokes
25781 Q: What is an experienced Emacs user?
25784 A: A person who wishes that the terminal had pedals.
25787 Yes, when you use Emacs, you are apt to use the control key, the shift
25788 key and the meta key a lot. This is very annoying to some people
25789 (notably @code{vi}le users), and the rest of us just love the hell out
25790 of it. Just give up and submit. Emacs really does stand for
25791 ``Escape-Meta-Alt-Control-Shift'', and not ``Editing Macros'', as you
25792 may have heard from other disreputable sources (like the Emacs author).
25794 The shift keys are normally located near your pinky fingers, and are
25795 normally used to get capital letters and stuff. You probably use it all
25796 the time. The control key is normally marked ``CTRL'' or something like
25797 that. The meta key is, funnily enough, never marked as such on any
25798 keyboard. The one I'm currently at has a key that's marked ``Alt'',
25799 which is the meta key on this keyboard. It's usually located somewhere
25800 to the left hand side of the keyboard, usually on the bottom row.
25802 Now, us Emacs people don't say ``press the meta-control-m key'',
25803 because that's just too inconvenient. We say ``press the @kbd{C-M-m}
25804 key''. @kbd{M-} is the prefix that means ``meta'' and ``C-'' is the
25805 prefix that means ``control''. So ``press @kbd{C-k}'' means ``press
25806 down the control key, and hold it down while you press @kbd{k}''.
25807 ``Press @kbd{C-M-k}'' means ``press down and hold down the meta key and
25808 the control key and then press @kbd{k}''. Simple, ay?
25810 This is somewhat complicated by the fact that not all keyboards have a
25811 meta key. In that case you can use the ``escape'' key. Then @kbd{M-k}
25812 means ``press escape, release escape, press @kbd{k}''. That's much more
25813 work than if you have a meta key, so if that's the case, I respectfully
25814 suggest you get a real keyboard with a meta key. You can't live without
25820 @subsection Emacs Lisp
25822 Emacs is the King of Editors because it's really a Lisp interpreter.
25823 Each and every key you tap runs some Emacs Lisp code snippet, and since
25824 Emacs Lisp is an interpreted language, that means that you can configure
25825 any key to run any arbitrary code. You just, like, do it.
25827 Gnus is written in Emacs Lisp, and is run as a bunch of interpreted
25828 functions. (These are byte-compiled for speed, but it's still
25829 interpreted.) If you decide that you don't like the way Gnus does
25830 certain things, it's trivial to have it do something a different way.
25831 (Well, at least if you know how to write Lisp code.) However, that's
25832 beyond the scope of this manual, so we are simply going to talk about
25833 some common constructs that you normally use in your @file{.emacs} file
25836 If you want to set the variable @code{gnus-florgbnize} to four (4), you
25837 write the following:
25840 (setq gnus-florgbnize 4)
25843 This function (really ``special form'') @code{setq} is the one that can
25844 set a variable to some value. This is really all you need to know. Now
25845 you can go and fill your @code{.emacs} file with lots of these to change
25848 If you have put that thing in your @code{.emacs} file, it will be read
25849 and @code{eval}ed (which is lisp-ese for ``run'') the next time you
25850 start Emacs. If you want to change the variable right away, simply say
25851 @kbd{C-x C-e} after the closing parenthesis. That will @code{eval} the
25852 previous ``form'', which is a simple @code{setq} statement here.
25854 Go ahead---just try it, if you're located at your Emacs. After you
25855 @kbd{C-x C-e}, you will see @samp{4} appear in the echo area, which
25856 is the return value of the form you @code{eval}ed.
25860 If the manual says ``set @code{gnus-read-active-file} to @code{some}'',
25864 (setq gnus-read-active-file 'some)
25867 On the other hand, if the manual says ``set @code{gnus-nntp-server} to
25868 @samp{nntp.ifi.uio.no}'', that means:
25871 (setq gnus-nntp-server "nntp.ifi.uio.no")
25874 So be careful not to mix up strings (the latter) with symbols (the
25875 former). The manual is unambiguous, but it can be confusing.
25878 @include gnus-faq.texi
25898 @c Local Variables:
25900 @c coding: iso-8859-1
25902 % LocalWords: BNF mucho detailmenu cindex kindex kbd
25903 % LocalWords: findex Gnusae vindex dfn dfn samp nntp setq nnspool nntpserver
25904 % LocalWords: nnmbox newusers Blllrph NEWGROUPS dingnusdingnusdingnus
25905 % LocalWords: pre fab rec comp nnslashdot regex ga ga sci nnml nnbabyl nnmh
25906 % LocalWords: nnfolder emph looong eld newsreaders defun init elc pxref