9 @documentencoding ISO-8859-1
12 Copyright @copyright{} 1995, 1996, 1997, 1998, 1999, 2000, 2001,
13 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc.
16 Permission is granted to copy, distribute and/or modify this document
17 under the terms of the GNU Free Documentation License, Version 1.2 or
18 any later version published by the Free Software Foundation; with no
19 Invariant Sections, with the Front-Cover texts being ``A GNU
20 Manual'', and with the Back-Cover Texts as in (a) below. A copy of the
21 license is included in the section entitled ``GNU Free Documentation
22 License'' in the Emacs manual.
24 (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
25 this GNU Manual, like GNU software. Copies published by the Free
26 Software Foundation raise funds for GNU development.''
28 This document is part of a collection distributed under the GNU Free
29 Documentation License. If you want to distribute this document
30 separately from the collection, you can do so by adding a copy of the
31 license to the document, as described in section 6 of the license.
37 \documentclass[twoside,a4paper,openright,11pt]{book}
38 \usepackage[latin1]{inputenc}
39 \usepackage{pagestyle}
42 \input{gnusconfig.tex}
44 \ifx\pdfoutput\undefined
46 \usepackage[pdftex,bookmarks,colorlinks=true]{hyperref}
54 % Adjust ../Makefile.in if you change the following line:
55 \newcommand{\gnusversionname}{No Gnus v0.4}
56 \newcommand{\gnuschaptername}{}
57 \newcommand{\gnussectionname}{}
59 \newcommand{\gnusbackslash}{/}
61 \newcommand{\gnusref}[1]{``#1'' on page \pageref{#1}}
62 \ifx\pdfoutput\undefined
63 \newcommand{\gnusuref}[1]{\gnustt{#1}}
65 \newcommand{\gnusuref}[1]{\href{#1}{\gnustt{#1}}}
67 \newcommand{\gnusxref}[1]{See ``#1'' on page \pageref{#1}}
68 \newcommand{\gnuspxref}[1]{see ``#1'' on page \pageref{#1}}
70 \newcommand{\gnuskindex}[1]{\index{#1}}
71 \newcommand{\gnusindex}[1]{\index{#1}}
73 \newcommand{\gnustt}[1]{{\gnusselectttfont{}#1}}
74 \newcommand{\gnuscode}[1]{\gnustt{#1}}
75 \newcommand{\gnusasis}[1]{\gnustt{#1}}
76 \newcommand{\gnusurl}[1]{\gnustt{#1}}
77 \newcommand{\gnuscommand}[1]{\gnustt{#1}}
78 \newcommand{\gnusenv}[1]{\gnustt{#1}}
79 \newcommand{\gnussamp}[1]{``{\fontencoding{OT1}\gnusselectttfont{}#1}''}
80 \newcommand{\gnuslisp}[1]{\gnustt{#1}}
81 \newcommand{\gnuskbd}[1]{`\gnustt{#1}'}
82 \newcommand{\gnuskey}[1]{`\gnustt{#1}'}
83 \newcommand{\gnusfile}[1]{`\gnustt{#1}'}
84 \newcommand{\gnusdfn}[1]{\textit{#1}}
85 \newcommand{\gnusi}[1]{\textit{#1}}
86 \newcommand{\gnusr}[1]{\textrm{#1}}
87 \newcommand{\gnusstrong}[1]{\textbf{#1}}
88 \newcommand{\gnusemph}[1]{\textit{#1}}
89 \newcommand{\gnusvar}[1]{{\fontsize{10pt}{10}\selectfont\textsl{\textsf{#1}}}}
90 \newcommand{\gnussc}[1]{\textsc{#1}}
91 \newcommand{\gnustitle}[1]{{\huge\textbf{#1}}}
92 \newcommand{\gnusversion}[1]{{\small\textit{#1}}}
93 \newcommand{\gnusauthor}[1]{{\large\textbf{#1}}}
94 \newcommand{\gnusresult}[1]{\gnustt{=> #1}}
95 \newcommand{\gnusacronym}[1]{\textsc{#1}}
96 \newcommand{\gnusemail}[1]{\textit{#1}}
98 \newcommand{\gnusbullet}{{${\bullet}$}}
99 \newcommand{\gnusdollar}{\$}
100 \newcommand{\gnusampersand}{\&}
101 \newcommand{\gnuspercent}{\%}
102 \newcommand{\gnushash}{\#}
103 \newcommand{\gnushat}{\symbol{"5E}}
104 \newcommand{\gnusunderline}{\symbol{"5F}}
105 \newcommand{\gnusnot}{$\neg$}
106 \newcommand{\gnustilde}{\symbol{"7E}}
107 \newcommand{\gnusless}{{$<$}}
108 \newcommand{\gnusgreater}{{$>$}}
109 \newcommand{\gnusbraceleft}{{$>$}}
110 \newcommand{\gnusbraceright}{{$>$}}
112 \newcommand{\gnushead}{\raisebox{-1cm}{\epsfig{figure=ps/gnus-head,height=1cm}}}
113 \newcommand{\gnusinteresting}{
114 \marginpar[\mbox{}\hfill\gnushead]{\gnushead}
117 \newcommand{\gnuscleardoublepage}{\ifodd\count0\mbox{}\clearpage\thispagestyle{empty}\mbox{}\clearpage\else\clearpage\fi}
119 \newcommand{\gnuspagechapter}[1]{
123 \newdimen{\gnusdimen}
126 \newcommand{\gnuschapter}[2]{
128 \ifdim \gnusdimen = 0pt\setcounter{page}{1}\pagestyle{gnus}\pagenumbering{arabic} \gnusdimen 1pt\fi
130 \renewcommand{\gnussectionname}{}
131 \renewcommand{\gnuschaptername}{#2}
132 \thispagestyle{empty}
134 \begin{picture}(500,500)(0,0)
135 \put(480,350){\makebox(0,0)[tr]{#1}}
136 \put(40,300){\makebox(500,50)[bl]{{\Huge\bf{#2}}}}
141 \newcommand{\gnusfigure}[3]{
143 \mbox{}\ifodd\count0\hspace*{-0.8cm}\else\hspace*{-3cm}\fi\begin{picture}(440,#2)
150 \newcommand{\gnusicon}[1]{
151 \marginpar[\mbox{}\hfill\raisebox{-1.5cm}{\epsfig{figure=ps/#1-up,height=1.5cm}}]{\raisebox{-1cm}{\epsfig{figure=ps/#1-up,height=1cm}}}
154 \newcommand{\gnuspicon}[1]{
155 \margindex{\epsfig{figure=#1,width=2cm}}
158 \newcommand{\gnusxface}[2]{
159 \margindex{\epsfig{figure=#1,width=1cm}\epsfig{figure=#2,width=1cm}}
162 \newcommand{\gnussmiley}[2]{
163 \margindex{\makebox[2cm]{\hfill\epsfig{figure=#1,width=0.5cm}\hfill\epsfig{figure=#2,width=0.5cm}\hfill}}
166 \newcommand{\gnusitemx}[1]{\mbox{}\vspace*{-\itemsep}\vspace*{-\parsep}\item#1}
168 \newcommand{\gnussection}[1]{
169 \renewcommand{\gnussectionname}{#1}
173 \newenvironment{codelist}%
178 \newenvironment{asislist}%
183 \newenvironment{kbdlist}%
189 \newenvironment{dfnlist}%
194 \newenvironment{stronglist}%
199 \newenvironment{samplist}%
204 \newenvironment{varlist}%
209 \newenvironment{emphlist}%
214 \newlength\gnusheadtextwidth
215 \setlength{\gnusheadtextwidth}{\headtextwidth}
216 \addtolength{\gnusheadtextwidth}{1cm}
218 \newpagestyle{gnuspreamble}%
223 \hspace*{-0.23cm}\underline{\makebox[\gnusheadtextwidth]{\mbox{}}\textbf{\hfill\roman{page}}}
227 \hspace*{-3.25cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\roman{page}\hfill\mbox{}}}
236 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
238 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
243 \newpagestyle{gnusindex}%
248 \hspace*{-0.23cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\gnuschaptername\hfill\arabic{page}}}}
252 \hspace*{-3.25cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{page}\hfill\gnuschaptername}}}
260 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
262 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
272 \makebox[12cm]{\hspace*{3.1cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{chapter}.\arabic{section}} \textbf{\gnussectionname\hfill\arabic{page}}}}}
276 \makebox[12cm]{\hspace*{-2.95cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{page}\hfill\gnuschaptername}}}}
284 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
286 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
291 \pagenumbering{roman}
292 \pagestyle{gnuspreamble}
303 %\addtolength{\oddsidemargin}{-5cm}
304 %\addtolength{\evensidemargin}{-5cm}
306 \addtolength{\textheight}{2cm}
308 \gnustitle{\gnustitlename}\hfill\gnusversion{\gnusversionname}\\
311 \hspace*{0cm}\epsfig{figure=ps/gnus-big-logo,height=15cm}
314 \gnusauthor{by Lars Magne Ingebrigtsen}
321 \thispagestyle{empty}
335 * Gnus: (gnus). The newsreader Gnus.
340 @setchapternewpage odd
347 @author by Lars Magne Ingebrigtsen
349 @vskip 0pt plus 1filll
355 @top The Gnus Newsreader
359 You can read news (and mail) from within Emacs by using Gnus. The news
360 can be gotten by any nefarious means you can think of---@acronym{NNTP}, local
361 spool or your mbox file. All at the same time, if you want to push your
364 @c Adjust ../Makefile.in if you change the following line:
365 This manual corresponds to No Gnus v0.4.
376 Gnus is the advanced, self-documenting, customizable, extensible
377 unreal-time newsreader for GNU Emacs.
379 Oops. That sounds oddly familiar, so let's start over again to avoid
380 being accused of plagiarism:
382 Gnus is a message-reading laboratory. It will let you look at just
383 about anything as if it were a newsgroup. You can read mail with it,
384 you can browse directories with it, you can @code{ftp} with it---you
385 can even read news with it!
387 Gnus tries to empower people who read news the same way Emacs empowers
388 people who edit text. Gnus sets no limits to what the user should be
389 allowed to do. Users are encouraged to extend Gnus to make it behave
390 like they want it to behave. A program should not control people;
391 people should be empowered to do what they want by using (or abusing)
397 * Starting Up:: Finding news can be a pain.
398 * Group Buffer:: Selecting, subscribing and killing groups.
399 * Summary Buffer:: Reading, saving and posting articles.
400 * Article Buffer:: Displaying and handling articles.
401 * Composing Messages:: Information on sending mail and news.
402 * Select Methods:: Gnus reads all messages from various select methods.
403 * Scoring:: Assigning values to articles.
404 * Various:: General purpose settings.
405 * The End:: Farewell and goodbye.
406 * Appendices:: Terminology, Emacs intro, @acronym{FAQ}, History, Internals.
407 * Index:: Variable, function and concept index.
408 * Key Index:: Key Index.
410 Other related manuals
412 * Message:(message). Composing messages.
413 * Emacs-MIME:(emacs-mime). Composing messages; @acronym{MIME}-specific parts.
414 * Sieve:(sieve). Managing Sieve scripts in Emacs.
415 * PGG:(pgg). @acronym{PGP/MIME} with Gnus.
416 * SASL:(sasl). @acronym{SASL} authentication in Emacs.
419 --- The Detailed Node Listing ---
423 * Finding the News:: Choosing a method for getting news.
424 * The First Time:: What does Gnus do the first time you start it?
425 * The Server is Down:: How can I read my mail then?
426 * Slave Gnusae:: You can have more than one Gnus active at a time.
427 * Fetching a Group:: Starting Gnus just to read a group.
428 * New Groups:: What is Gnus supposed to do with new groups?
429 * Changing Servers:: You may want to move from one server to another.
430 * Startup Files:: Those pesky startup files---@file{.newsrc}.
431 * Auto Save:: Recovering from a crash.
432 * The Active File:: Reading the active file over a slow line Takes Time.
433 * Startup Variables:: Other variables you might change.
437 * Checking New Groups:: Determining what groups are new.
438 * Subscription Methods:: What Gnus should do with new groups.
439 * Filtering New Groups:: Making Gnus ignore certain new groups.
443 * Group Buffer Format:: Information listed and how you can change it.
444 * Group Maneuvering:: Commands for moving in the group buffer.
445 * Selecting a Group:: Actually reading news.
446 * Subscription Commands:: Unsubscribing, killing, subscribing.
447 * Group Data:: Changing the info for a group.
448 * Group Levels:: Levels? What are those, then?
449 * Group Score:: A mechanism for finding out what groups you like.
450 * Marking Groups:: You can mark groups for later processing.
451 * Foreign Groups:: Creating and editing groups.
452 * Group Parameters:: Each group may have different parameters set.
453 * Listing Groups:: Gnus can list various subsets of the groups.
454 * Sorting Groups:: Re-arrange the group order.
455 * Group Maintenance:: Maintaining a tidy @file{.newsrc} file.
456 * Browse Foreign Server:: You can browse a server. See what it has to offer.
457 * Exiting Gnus:: Stop reading news and get some work done.
458 * Group Topics:: A folding group mode divided into topics.
459 * Misc Group Stuff:: Other stuff that you can to do.
463 * Group Line Specification:: Deciding how the group buffer is to look.
464 * Group Mode Line Specification:: The group buffer mode line.
465 * Group Highlighting:: Having nice colors in the group buffer.
469 * Topic Commands:: Interactive E-Z commands.
470 * Topic Variables:: How to customize the topics the Lisp Way.
471 * Topic Sorting:: Sorting each topic individually.
472 * Topic Topology:: A map of the world.
473 * Topic Parameters:: Parameters that apply to all groups in a topic.
477 * Scanning New Messages:: Asking Gnus to see whether new messages have arrived.
478 * Group Information:: Information and help on groups and Gnus.
479 * Group Timestamp:: Making Gnus keep track of when you last read a group.
480 * File Commands:: Reading and writing the Gnus files.
481 * Sieve Commands:: Managing Sieve scripts.
485 * Summary Buffer Format:: Deciding how the summary buffer is to look.
486 * Summary Maneuvering:: Moving around the summary buffer.
487 * Choosing Articles:: Reading articles.
488 * Paging the Article:: Scrolling the current article.
489 * Reply Followup and Post:: Posting articles.
490 * Delayed Articles:: Send articles at a later time.
491 * Marking Articles:: Marking articles as read, expirable, etc.
492 * Limiting:: You can limit the summary buffer.
493 * Threading:: How threads are made.
494 * Sorting the Summary Buffer:: How articles and threads are sorted.
495 * Asynchronous Fetching:: Gnus might be able to pre-fetch articles.
496 * Article Caching:: You may store articles in a cache.
497 * Persistent Articles:: Making articles expiry-resistant.
498 * Article Backlog:: Having already read articles hang around.
499 * Saving Articles:: Ways of customizing article saving.
500 * Decoding Articles:: Gnus can treat series of (uu)encoded articles.
501 * Article Treatment:: The article buffer can be mangled at will.
502 * MIME Commands:: Doing MIMEy things with the articles.
503 * Charsets:: Character set issues.
504 * Article Commands:: Doing various things with the article buffer.
505 * Summary Sorting:: Sorting the summary buffer in various ways.
506 * Finding the Parent:: No child support? Get the parent.
507 * Alternative Approaches:: Reading using non-default summaries.
508 * Tree Display:: A more visual display of threads.
509 * Mail Group Commands:: Some commands can only be used in mail groups.
510 * Various Summary Stuff:: What didn't fit anywhere else.
511 * Exiting the Summary Buffer:: Returning to the Group buffer,
512 or reselecting the current group.
513 * Crosspost Handling:: How crossposted articles are dealt with.
514 * Duplicate Suppression:: An alternative when crosspost handling fails.
515 * Security:: Decrypt and Verify.
516 * Mailing List:: Mailing list minor mode.
518 Summary Buffer Format
520 * Summary Buffer Lines:: You can specify how summary lines should look.
521 * To From Newsgroups:: How to not display your own name.
522 * Summary Buffer Mode Line:: You can say how the mode line should look.
523 * Summary Highlighting:: Making the summary buffer all pretty and nice.
527 * Choosing Commands:: Commands for choosing articles.
528 * Choosing Variables:: Variables that influence these commands.
530 Reply, Followup and Post
532 * Summary Mail Commands:: Sending mail.
533 * Summary Post Commands:: Sending news.
534 * Summary Message Commands:: Other Message-related commands.
535 * Canceling and Superseding::
539 * Unread Articles:: Marks for unread articles.
540 * Read Articles:: Marks for read articles.
541 * Other Marks:: Marks that do not affect readedness.
542 * Setting Marks:: How to set and remove marks.
543 * Generic Marking Commands:: How to customize the marking.
544 * Setting Process Marks:: How to mark articles for later processing.
548 * Customizing Threading:: Variables you can change to affect the threading.
549 * Thread Commands:: Thread based commands in the summary buffer.
551 Customizing Threading
553 * Loose Threads:: How Gnus gathers loose threads into bigger threads.
554 * Filling In Threads:: Making the threads displayed look fuller.
555 * More Threading:: Even more variables for fiddling with threads.
556 * Low-Level Threading:: You thought it was over@dots{} but you were wrong!
560 * Uuencoded Articles:: Uudecode articles.
561 * Shell Archives:: Unshar articles.
562 * PostScript Files:: Split PostScript.
563 * Other Files:: Plain save and binhex.
564 * Decoding Variables:: Variables for a happy decoding.
565 * Viewing Files:: You want to look at the result of the decoding?
569 * Rule Variables:: Variables that say how a file is to be viewed.
570 * Other Decode Variables:: Other decode variables.
571 * Uuencoding and Posting:: Variables for customizing uuencoding.
575 * Article Highlighting:: You want to make the article look like fruit salad.
576 * Article Fontisizing:: Making emphasized text look nice.
577 * Article Hiding:: You also want to make certain info go away.
578 * Article Washing:: Lots of way-neat functions to make life better.
579 * Article Header:: Doing various header transformations.
580 * Article Buttons:: Click on URLs, Message-IDs, addresses and the like.
581 * Article Button Levels:: Controlling appearance of buttons.
582 * Article Date:: Grumble, UT!
583 * Article Display:: Display various stuff---X-Face, Picons, Smileys
584 * Article Signature:: What is a signature?
585 * Article Miscellanea:: Various other stuff.
587 Alternative Approaches
589 * Pick and Read:: First mark articles and then read them.
590 * Binary Groups:: Auto-decode all articles.
592 Various Summary Stuff
594 * Summary Group Information:: Information oriented commands.
595 * Searching for Articles:: Multiple article commands.
596 * Summary Generation Commands::
597 * Really Various Summary Commands:: Those pesky non-conformant commands.
601 * Hiding Headers:: Deciding what headers should be displayed.
602 * Using MIME:: Pushing articles through @acronym{MIME} before reading them.
603 * Customizing Articles:: Tailoring the look of the articles.
604 * Article Keymap:: Keystrokes available in the article buffer.
605 * Misc Article:: Other stuff.
609 * Mail:: Mailing and replying.
610 * Posting Server:: What server should you post and mail via?
611 * POP before SMTP:: You cannot send a mail unless you read a mail.
612 * Mail and Post:: Mailing and posting at the same time.
613 * Archived Messages:: Where Gnus stores the messages you've sent.
614 * Posting Styles:: An easier way to specify who you are.
615 * Drafts:: Postponing messages and rejected messages.
616 * Rejected Articles:: What happens if the server doesn't like your article?
617 * Signing and encrypting:: How to compose secure messages.
621 * Server Buffer:: Making and editing virtual servers.
622 * Getting News:: Reading USENET news with Gnus.
623 * Getting Mail:: Reading your personal mail with Gnus.
624 * Browsing the Web:: Getting messages from a plethora of Web sources.
625 * IMAP:: Using Gnus as a @acronym{IMAP} client.
626 * Other Sources:: Reading directories, files, SOUP packets.
627 * Combined Groups:: Combining groups into one group.
628 * Email Based Diary:: Using mails to manage diary events in Gnus.
629 * Gnus Unplugged:: Reading news and mail offline.
633 * Server Buffer Format:: You can customize the look of this buffer.
634 * Server Commands:: Commands to manipulate servers.
635 * Example Methods:: Examples server specifications.
636 * Creating a Virtual Server:: An example session.
637 * Server Variables:: Which variables to set.
638 * Servers and Methods:: You can use server names as select methods.
639 * Unavailable Servers:: Some servers you try to contact may be down.
643 * NNTP:: Reading news from an @acronym{NNTP} server.
644 * News Spool:: Reading news from the local spool.
648 * Direct Functions:: Connecting directly to the server.
649 * Indirect Functions:: Connecting indirectly to the server.
650 * Common Variables:: Understood by several connection functions.
651 * NNTP marks:: Storing marks for @acronym{NNTP} servers.
655 * Mail in a Newsreader:: Important introductory notes.
656 * Getting Started Reading Mail:: A simple cookbook example.
657 * Splitting Mail:: How to create mail groups.
658 * Mail Sources:: How to tell Gnus where to get mail from.
659 * Mail Back End Variables:: Variables for customizing mail handling.
660 * Fancy Mail Splitting:: Gnus can do hairy splitting of incoming mail.
661 * Group Mail Splitting:: Use group customize to drive mail splitting.
662 * Incorporating Old Mail:: What about the old mail you have?
663 * Expiring Mail:: Getting rid of unwanted mail.
664 * Washing Mail:: Removing cruft from the mail you get.
665 * Duplicates:: Dealing with duplicated mail.
666 * Not Reading Mail:: Using mail back ends for reading other files.
667 * Choosing a Mail Back End:: Gnus can read a variety of mail formats.
671 * Mail Source Specifiers:: How to specify what a mail source is.
672 * Mail Source Customization:: Some variables that influence things.
673 * Fetching Mail:: Using the mail source specifiers.
675 Choosing a Mail Back End
677 * Unix Mail Box:: Using the (quite) standard Un*x mbox.
678 * Rmail Babyl:: Emacs programs use the Rmail Babyl format.
679 * Mail Spool:: Store your mail in a private spool?
680 * MH Spool:: An mhspool-like back end.
681 * Maildir:: Another one-file-per-message format.
682 * Mail Folders:: Having one file for each group.
683 * Comparing Mail Back Ends:: An in-depth looks at pros and cons.
688 * Web Searches:: Creating groups from articles that match a string.
689 * Slashdot:: Reading the Slashdot comments.
690 * Ultimate:: The Ultimate Bulletin Board systems.
691 * Web Archive:: Reading mailing list archived on web.
692 * RSS:: Reading RDF site summary.
693 * Customizing W3:: Doing stuff to Emacs/W3 from Gnus.
697 * Splitting in IMAP:: Splitting mail with nnimap.
698 * Expiring in IMAP:: Expiring mail with nnimap.
699 * Editing IMAP ACLs:: Limiting/enabling other users access to a mailbox.
700 * Expunging mailboxes:: Equivalent of a ``compress mailbox'' button.
701 * A note on namespaces:: How to (not) use @acronym{IMAP} namespace in Gnus.
702 * Debugging IMAP:: What to do when things don't work.
706 * Directory Groups:: You can read a directory as if it was a newsgroup.
707 * Anything Groups:: Dired? Who needs dired?
708 * Document Groups:: Single files can be the basis of a group.
709 * SOUP:: Reading @sc{soup} packets ``offline''.
710 * Mail-To-News Gateways:: Posting articles via mail-to-news gateways.
714 * Document Server Internals:: How to add your own document types.
718 * SOUP Commands:: Commands for creating and sending @sc{soup} packets
719 * SOUP Groups:: A back end for reading @sc{soup} packets.
720 * SOUP Replies:: How to enable @code{nnsoup} to take over mail and news.
724 * Virtual Groups:: Combining articles from many groups.
725 * Kibozed Groups:: Looking through parts of the newsfeed for articles.
729 * The NNDiary Back End:: Basic setup and usage.
730 * The Gnus Diary Library:: Utility toolkit on top of nndiary.
731 * Sending or Not Sending:: A final note on sending diary messages.
735 * Diary Messages:: What makes a message valid for nndiary.
736 * Running NNDiary:: NNDiary has two modes of operation.
737 * Customizing NNDiary:: Bells and whistles.
739 The Gnus Diary Library
741 * Diary Summary Line Format:: A nicer summary buffer line format.
742 * Diary Articles Sorting:: A nicer way to sort messages.
743 * Diary Headers Generation:: Not doing it manually.
744 * Diary Group Parameters:: Not handling them manually.
748 * Agent Basics:: How it all is supposed to work.
749 * Agent Categories:: How to tell the Gnus Agent what to download.
750 * Agent Commands:: New commands for all the buffers.
751 * Agent Visuals:: Ways that the agent may effect your summary buffer.
752 * Agent as Cache:: The Agent is a big cache too.
753 * Agent Expiry:: How to make old articles go away.
754 * Agent Regeneration:: How to recover from lost connections and other accidents.
755 * Agent and flags:: How the Agent maintains flags.
756 * Agent and IMAP:: How to use the Agent with @acronym{IMAP}.
757 * Outgoing Messages:: What happens when you post/mail something?
758 * Agent Variables:: Customizing is fun.
759 * Example Setup:: An example @file{~/.gnus.el} file for offline people.
760 * Batching Agents:: How to fetch news from a @code{cron} job.
761 * Agent Caveats:: What you think it'll do and what it does.
765 * Category Syntax:: What a category looks like.
766 * Category Buffer:: A buffer for maintaining categories.
767 * Category Variables:: Customize'r'Us.
771 * Group Agent Commands:: Configure groups and fetch their contents.
772 * Summary Agent Commands:: Manually select then fetch specific articles.
773 * Server Agent Commands:: Select the servers that are supported by the agent.
777 * Summary Score Commands:: Adding score entries for the current group.
778 * Group Score Commands:: General score commands.
779 * Score Variables:: Customize your scoring. (My, what terminology).
780 * Score File Format:: What a score file may contain.
781 * Score File Editing:: You can edit score files by hand as well.
782 * Adaptive Scoring:: Big Sister Gnus knows what you read.
783 * Home Score File:: How to say where new score entries are to go.
784 * Followups To Yourself:: Having Gnus notice when people answer you.
785 * Scoring On Other Headers:: Scoring on non-standard headers.
786 * Scoring Tips:: How to score effectively.
787 * Reverse Scoring:: That problem child of old is not problem.
788 * Global Score Files:: Earth-spanning, ear-splitting score files.
789 * Kill Files:: They are still here, but they can be ignored.
790 * Converting Kill Files:: Translating kill files to score files.
791 * Advanced Scoring:: Using logical expressions to build score rules.
792 * Score Decays:: It can be useful to let scores wither away.
796 * Advanced Scoring Syntax:: A definition.
797 * Advanced Scoring Examples:: What they look like.
798 * Advanced Scoring Tips:: Getting the most out of it.
802 * Process/Prefix:: A convention used by many treatment commands.
803 * Interactive:: Making Gnus ask you many questions.
804 * Symbolic Prefixes:: How to supply some Gnus functions with options.
805 * Formatting Variables:: You can specify what buffers should look like.
806 * Window Layout:: Configuring the Gnus buffer windows.
807 * Faces and Fonts:: How to change how faces look.
808 * Compilation:: How to speed Gnus up.
809 * Mode Lines:: Displaying information in the mode lines.
810 * Highlighting and Menus:: Making buffers look all nice and cozy.
811 * Buttons:: Get tendinitis in ten easy steps!
812 * Daemons:: Gnus can do things behind your back.
813 * NoCeM:: How to avoid spam and other fatty foods.
814 * Undo:: Some actions can be undone.
815 * Predicate Specifiers:: Specifying predicates.
816 * Moderation:: What to do if you're a moderator.
817 * Image Enhancements:: Modern versions of Emacs/XEmacs can display images.
818 * Fuzzy Matching:: What's the big fuzz?
819 * Thwarting Email Spam:: A how-to on avoiding unsolicited commercial email.
820 * Other modes:: Interaction with other modes.
821 * Various Various:: Things that are really various.
825 * Formatting Basics:: A formatting variable is basically a format string.
826 * Mode Line Formatting:: Some rules about mode line formatting variables.
827 * Advanced Formatting:: Modifying output in various ways.
828 * User-Defined Specs:: Having Gnus call your own functions.
829 * Formatting Fonts:: Making the formatting look colorful and nice.
830 * Positioning Point:: Moving point to a position after an operation.
831 * Tabulation:: Tabulating your output.
832 * Wide Characters:: Dealing with wide characters.
836 * X-Face:: Display a funky, teensy black-and-white image.
837 * Face:: Display a funkier, teensier colored image.
838 * Smileys:: Show all those happy faces the way they were meant to be shown.
839 * Picons:: How to display pictures of what you're reading.
840 * XVarious:: Other XEmacsy Gnusey variables.
844 * The problem of spam:: Some background, and some solutions
845 * Anti-Spam Basics:: Simple steps to reduce the amount of spam.
846 * SpamAssassin:: How to use external anti-spam tools.
847 * Hashcash:: Reduce spam by burning CPU time.
848 * Filtering Spam Using The Spam ELisp Package::
849 * Filtering Spam Using Statistics with spam-stat::
851 Filtering Spam Using The Spam ELisp Package
853 * Spam ELisp Package Sequence of Events::
854 * Spam ELisp Package Filtering of Incoming Mail::
855 * Spam ELisp Package Global Variables::
856 * Spam ELisp Package Configuration Examples::
857 * Blacklists and Whitelists::
859 * Gmane Spam Reporting::
860 * Anti-spam Hashcash Payments::
862 * Regular Expressions Header Matching::
864 * SpamAssassin back end::
865 * ifile spam filtering::
866 * spam-stat spam filtering::
868 * Extending the Spam ELisp package::
870 Filtering Spam Using Statistics with spam-stat
872 * Creating a spam-stat dictionary::
873 * Splitting mail using spam-stat::
874 * Low-level interface to the spam-stat dictionary::
878 * XEmacs:: Requirements for installing under XEmacs.
879 * History:: How Gnus got where it is today.
880 * On Writing Manuals:: Why this is not a beginner's guide.
881 * Terminology:: We use really difficult, like, words here.
882 * Customization:: Tailoring Gnus to your needs.
883 * Troubleshooting:: What you might try if things do not work.
884 * Gnus Reference Guide:: Rilly, rilly technical stuff.
885 * Emacs for Heathens:: A short introduction to Emacsian terms.
886 * Frequently Asked Questions:: The Gnus FAQ
890 * Gnus Versions:: What Gnus versions have been released.
891 * Other Gnus Versions:: Other Gnus versions that also have been released.
892 * Why?:: What's the point of Gnus?
893 * Compatibility:: Just how compatible is Gnus with @sc{gnus}?
894 * Conformity:: Gnus tries to conform to all standards.
895 * Emacsen:: Gnus can be run on a few modern Emacsen.
896 * Gnus Development:: How Gnus is developed.
897 * Contributors:: Oodles of people.
898 * New Features:: Pointers to some of the new stuff in Gnus.
902 * ding Gnus:: New things in Gnus 5.0/5.1, the first new Gnus.
903 * September Gnus:: The Thing Formally Known As Gnus 5.2/5.3.
904 * Red Gnus:: Third time best---Gnus 5.4/5.5.
905 * Quassia Gnus:: Two times two is four, or Gnus 5.6/5.7.
906 * Pterodactyl Gnus:: Pentad also starts with P, AKA Gnus 5.8/5.9.
907 * Oort Gnus:: It's big. It's far out. Gnus 5.10/5.11.
908 * No Gnus:: Very punny.
912 * Slow/Expensive Connection:: You run a local Emacs and get the news elsewhere.
913 * Slow Terminal Connection:: You run a remote Emacs.
914 * Little Disk Space:: You feel that having large setup files is icky.
915 * Slow Machine:: You feel like buying a faster machine.
919 * Gnus Utility Functions:: Common functions and variable to use.
920 * Back End Interface:: How Gnus communicates with the servers.
921 * Score File Syntax:: A BNF definition of the score file standard.
922 * Headers:: How Gnus stores headers internally.
923 * Ranges:: A handy format for storing mucho numbers.
924 * Group Info:: The group info format.
925 * Extended Interactive:: Symbolic prefixes and stuff.
926 * Emacs/XEmacs Code:: Gnus can be run under all modern Emacsen.
927 * Various File Formats:: Formats of files that Gnus use.
931 * Required Back End Functions:: Functions that must be implemented.
932 * Optional Back End Functions:: Functions that need not be implemented.
933 * Error Messaging:: How to get messages and report errors.
934 * Writing New Back Ends:: Extending old back ends.
935 * Hooking New Back Ends Into Gnus:: What has to be done on the Gnus end.
936 * Mail-like Back Ends:: Some tips on mail back ends.
940 * Active File Format:: Information on articles and groups available.
941 * Newsgroups File Format:: Group descriptions.
945 * Keystrokes:: Entering text and executing commands.
946 * Emacs Lisp:: The built-in Emacs programming language.
952 @chapter Starting Gnus
957 If your system administrator has set things up properly, starting Gnus
958 and reading news is extremely easy---you just type @kbd{M-x gnus} in
961 @findex gnus-other-frame
962 @kindex M-x gnus-other-frame
963 If you want to start Gnus in a different frame, you can use the command
964 @kbd{M-x gnus-other-frame} instead.
966 If things do not go smoothly at startup, you have to twiddle some
967 variables in your @file{~/.gnus.el} file. This file is similar to
968 @file{~/.emacs}, but is read when Gnus starts.
970 If you puzzle at any terms used in this manual, please refer to the
971 terminology section (@pxref{Terminology}).
974 * Finding the News:: Choosing a method for getting news.
975 * The First Time:: What does Gnus do the first time you start it?
976 * The Server is Down:: How can I read my mail then?
977 * Slave Gnusae:: You can have more than one Gnus active at a time.
978 * New Groups:: What is Gnus supposed to do with new groups?
979 * Changing Servers:: You may want to move from one server to another.
980 * Startup Files:: Those pesky startup files---@file{.newsrc}.
981 * Auto Save:: Recovering from a crash.
982 * The Active File:: Reading the active file over a slow line Takes Time.
983 * Startup Variables:: Other variables you might change.
987 @node Finding the News
988 @section Finding the News
991 @vindex gnus-select-method
993 The @code{gnus-select-method} variable says where Gnus should look for
994 news. This variable should be a list where the first element says
995 @dfn{how} and the second element says @dfn{where}. This method is your
996 native method. All groups not fetched with this method are
999 For instance, if the @samp{news.somewhere.edu} @acronym{NNTP} server is where
1000 you want to get your daily dosage of news from, you'd say:
1003 (setq gnus-select-method '(nntp "news.somewhere.edu"))
1006 If you want to read directly from the local spool, say:
1009 (setq gnus-select-method '(nnspool ""))
1012 If you can use a local spool, you probably should, as it will almost
1013 certainly be much faster. But do not use the local spool if your
1014 server is running Leafnode (which is a simple, standalone private news
1015 server); in this case, use @code{(nntp "localhost")}.
1017 @vindex gnus-nntpserver-file
1019 @cindex @acronym{NNTP} server
1020 If this variable is not set, Gnus will take a look at the
1021 @env{NNTPSERVER} environment variable. If that variable isn't set,
1022 Gnus will see whether @code{gnus-nntpserver-file}
1023 (@file{/etc/nntpserver} by default) has any opinions on the matter.
1024 If that fails as well, Gnus will try to use the machine running Emacs
1025 as an @acronym{NNTP} server. That's a long shot, though.
1027 @vindex gnus-nntp-server
1028 If @code{gnus-nntp-server} is set, this variable will override
1029 @code{gnus-select-method}. You should therefore set
1030 @code{gnus-nntp-server} to @code{nil}, which is what it is by default.
1032 @vindex gnus-secondary-servers
1033 @vindex gnus-nntp-server
1034 You can also make Gnus prompt you interactively for the name of an
1035 @acronym{NNTP} server. If you give a non-numerical prefix to @code{gnus}
1036 (i.e., @kbd{C-u M-x gnus}), Gnus will let you choose between the servers
1037 in the @code{gnus-secondary-servers} list (if any). You can also just
1038 type in the name of any server you feel like visiting. (Note that this
1039 will set @code{gnus-nntp-server}, which means that if you then @kbd{M-x
1040 gnus} later in the same Emacs session, Gnus will contact the same
1043 @findex gnus-group-browse-foreign-server
1045 However, if you use one @acronym{NNTP} server regularly and are just
1046 interested in a couple of groups from a different server, you would be
1047 better served by using the @kbd{B} command in the group buffer. It will
1048 let you have a look at what groups are available, and you can subscribe
1049 to any of the groups you want to. This also makes @file{.newsrc}
1050 maintenance much tidier. @xref{Foreign Groups}.
1052 @vindex gnus-secondary-select-methods
1054 A slightly different approach to foreign groups is to set the
1055 @code{gnus-secondary-select-methods} variable. The select methods
1056 listed in this variable are in many ways just as native as the
1057 @code{gnus-select-method} server. They will also be queried for active
1058 files during startup (if that's required), and new newsgroups that
1059 appear on these servers will be subscribed (or not) just as native
1062 For instance, if you use the @code{nnmbox} back end to read your mail,
1063 you would typically set this variable to
1066 (setq gnus-secondary-select-methods '((nnmbox "")))
1069 Note: the @acronym{NNTP} back end stores marks in marks files
1070 (@pxref{NNTP marks}). This feature makes it easy to share marks between
1071 several Gnus installations, but may slow down things a bit when fetching
1072 new articles. @xref{NNTP marks}, for more information.
1075 @node The First Time
1076 @section The First Time
1077 @cindex first time usage
1079 If no startup files exist (@pxref{Startup Files}), Gnus will try to
1080 determine what groups should be subscribed by default.
1082 @vindex gnus-default-subscribed-newsgroups
1083 If the variable @code{gnus-default-subscribed-newsgroups} is set, Gnus
1084 will subscribe you to just those groups in that list, leaving the rest
1085 killed. Your system administrator should have set this variable to
1088 Since she hasn't, Gnus will just subscribe you to a few arbitrarily
1089 picked groups (i.e., @samp{*.newusers}). (@dfn{Arbitrary} is defined
1090 here as @dfn{whatever Lars thinks you should read}.)
1092 You'll also be subscribed to the Gnus documentation group, which should
1093 help you with most common problems.
1095 If @code{gnus-default-subscribed-newsgroups} is @code{t}, Gnus will just
1096 use the normal functions for handling new groups, and not do anything
1100 @node The Server is Down
1101 @section The Server is Down
1102 @cindex server errors
1104 If the default server is down, Gnus will understandably have some
1105 problems starting. However, if you have some mail groups in addition to
1106 the news groups, you may want to start Gnus anyway.
1108 Gnus, being the trusting sort of program, will ask whether to proceed
1109 without a native select method if that server can't be contacted. This
1110 will happen whether the server doesn't actually exist (i.e., you have
1111 given the wrong address) or the server has just momentarily taken ill
1112 for some reason or other. If you decide to continue and have no foreign
1113 groups, you'll find it difficult to actually do anything in the group
1114 buffer. But, hey, that's your problem. Blllrph!
1116 @findex gnus-no-server
1117 @kindex M-x gnus-no-server
1119 If you know that the server is definitely down, or you just want to read
1120 your mail without bothering with the server at all, you can use the
1121 @code{gnus-no-server} command to start Gnus. That might come in handy
1122 if you're in a hurry as well. This command will not attempt to contact
1123 your primary server---instead, it will just activate all groups on level
1124 1 and 2. (You should preferably keep no native groups on those two
1125 levels.) Also @pxref{Group Levels}.
1129 @section Slave Gnusae
1132 You might want to run more than one Emacs with more than one Gnus at the
1133 same time. If you are using different @file{.newsrc} files (e.g., if you
1134 are using the two different Gnusae to read from two different servers),
1135 that is no problem whatsoever. You just do it.
1137 The problem appears when you want to run two Gnusae that use the same
1138 @file{.newsrc} file.
1140 To work around that problem some, we here at the Think-Tank at the Gnus
1141 Towers have come up with a new concept: @dfn{Masters} and
1142 @dfn{slaves}. (We have applied for a patent on this concept, and have
1143 taken out a copyright on those words. If you wish to use those words in
1144 conjunction with each other, you have to send $1 per usage instance to
1145 me. Usage of the patent (@dfn{Master/Slave Relationships In Computer
1146 Applications}) will be much more expensive, of course.)
1149 Anyway, you start one Gnus up the normal way with @kbd{M-x gnus} (or
1150 however you do it). Each subsequent slave Gnusae should be started with
1151 @kbd{M-x gnus-slave}. These slaves won't save normal @file{.newsrc}
1152 files, but instead save @dfn{slave files} that contain information only
1153 on what groups have been read in the slave session. When a master Gnus
1154 starts, it will read (and delete) these slave files, incorporating all
1155 information from them. (The slave files will be read in the sequence
1156 they were created, so the latest changes will have precedence.)
1158 Information from the slave files has, of course, precedence over the
1159 information in the normal (i.e., master) @file{.newsrc} file.
1161 If the @file{.newsrc*} files have not been saved in the master when the
1162 slave starts, you may be prompted as to whether to read an auto-save
1163 file. If you answer ``yes'', the unsaved changes to the master will be
1164 incorporated into the slave. If you answer ``no'', the slave may see some
1165 messages as unread that have been read in the master.
1172 @cindex subscription
1174 @vindex gnus-check-new-newsgroups
1175 If you are satisfied that you really never want to see any new groups,
1176 you can set @code{gnus-check-new-newsgroups} to @code{nil}. This will
1177 also save you some time at startup. Even if this variable is
1178 @code{nil}, you can always subscribe to the new groups just by pressing
1179 @kbd{U} in the group buffer (@pxref{Group Maintenance}). This variable
1180 is @code{ask-server} by default. If you set this variable to
1181 @code{always}, then Gnus will query the back ends for new groups even
1182 when you do the @kbd{g} command (@pxref{Scanning New Messages}).
1185 * Checking New Groups:: Determining what groups are new.
1186 * Subscription Methods:: What Gnus should do with new groups.
1187 * Filtering New Groups:: Making Gnus ignore certain new groups.
1191 @node Checking New Groups
1192 @subsection Checking New Groups
1194 Gnus normally determines whether a group is new or not by comparing the
1195 list of groups from the active file(s) with the lists of subscribed and
1196 dead groups. This isn't a particularly fast method. If
1197 @code{gnus-check-new-newsgroups} is @code{ask-server}, Gnus will ask the
1198 server for new groups since the last time. This is both faster and
1199 cheaper. This also means that you can get rid of the list of killed
1200 groups altogether, so you may set @code{gnus-save-killed-list} to
1201 @code{nil}, which will save time both at startup, at exit, and all over.
1202 Saves disk space, too. Why isn't this the default, then?
1203 Unfortunately, not all servers support this command.
1205 I bet I know what you're thinking now: How do I find out whether my
1206 server supports @code{ask-server}? No? Good, because I don't have a
1207 fail-safe answer. I would suggest just setting this variable to
1208 @code{ask-server} and see whether any new groups appear within the next
1209 few days. If any do, then it works. If none do, then it doesn't
1210 work. I could write a function to make Gnus guess whether the server
1211 supports @code{ask-server}, but it would just be a guess. So I won't.
1212 You could @code{telnet} to the server and say @code{HELP} and see
1213 whether it lists @samp{NEWGROUPS} among the commands it understands. If
1214 it does, then it might work. (But there are servers that lists
1215 @samp{NEWGROUPS} without supporting the function properly.)
1217 This variable can also be a list of select methods. If so, Gnus will
1218 issue an @code{ask-server} command to each of the select methods, and
1219 subscribe them (or not) using the normal methods. This might be handy
1220 if you are monitoring a few servers for new groups. A side effect is
1221 that startup will take much longer, so you can meditate while waiting.
1222 Use the mantra ``dingnusdingnusdingnus'' to achieve permanent bliss.
1225 @node Subscription Methods
1226 @subsection Subscription Methods
1228 @vindex gnus-subscribe-newsgroup-method
1229 What Gnus does when it encounters a new group is determined by the
1230 @code{gnus-subscribe-newsgroup-method} variable.
1232 This variable should contain a function. This function will be called
1233 with the name of the new group as the only parameter.
1235 Some handy pre-fab functions are:
1239 @item gnus-subscribe-zombies
1240 @vindex gnus-subscribe-zombies
1241 Make all new groups zombies. This is the default. You can browse the
1242 zombies later (with @kbd{A z}) and either kill them all off properly
1243 (with @kbd{S z}), or subscribe to them (with @kbd{u}).
1245 @item gnus-subscribe-randomly
1246 @vindex gnus-subscribe-randomly
1247 Subscribe all new groups in arbitrary order. This really means that all
1248 new groups will be added at ``the top'' of the group buffer.
1250 @item gnus-subscribe-alphabetically
1251 @vindex gnus-subscribe-alphabetically
1252 Subscribe all new groups in alphabetical order.
1254 @item gnus-subscribe-hierarchically
1255 @vindex gnus-subscribe-hierarchically
1256 Subscribe all new groups hierarchically. The difference between this
1257 function and @code{gnus-subscribe-alphabetically} is slight.
1258 @code{gnus-subscribe-alphabetically} will subscribe new groups in a strictly
1259 alphabetical fashion, while this function will enter groups into its
1260 hierarchy. So if you want to have the @samp{rec} hierarchy before the
1261 @samp{comp} hierarchy, this function will not mess that configuration
1262 up. Or something like that.
1264 @item gnus-subscribe-interactively
1265 @vindex gnus-subscribe-interactively
1266 Subscribe new groups interactively. This means that Gnus will ask
1267 you about @strong{all} new groups. The groups you choose to subscribe
1268 to will be subscribed hierarchically.
1270 @item gnus-subscribe-killed
1271 @vindex gnus-subscribe-killed
1272 Kill all new groups.
1274 @item gnus-subscribe-topics
1275 @vindex gnus-subscribe-topics
1276 Put the groups into the topic that has a matching @code{subscribe} topic
1277 parameter (@pxref{Topic Parameters}). For instance, a @code{subscribe}
1278 topic parameter that looks like
1284 will mean that all groups that match that regex will be subscribed under
1287 If no topics match the groups, the groups will be subscribed in the
1292 @vindex gnus-subscribe-hierarchical-interactive
1293 A closely related variable is
1294 @code{gnus-subscribe-hierarchical-interactive}. (That's quite a
1295 mouthful.) If this variable is non-@code{nil}, Gnus will ask you in a
1296 hierarchical fashion whether to subscribe to new groups or not. Gnus
1297 will ask you for each sub-hierarchy whether you want to descend the
1300 One common mistake is to set the variable a few paragraphs above
1301 (@code{gnus-subscribe-newsgroup-method}) to
1302 @code{gnus-subscribe-hierarchical-interactive}. This is an error. This
1303 will not work. This is ga-ga. So don't do it.
1306 @node Filtering New Groups
1307 @subsection Filtering New Groups
1309 A nice and portable way to control which new newsgroups should be
1310 subscribed (or ignored) is to put an @dfn{options} line at the start of
1311 the @file{.newsrc} file. Here's an example:
1314 options -n !alt.all !rec.all sci.all
1317 @vindex gnus-subscribe-options-newsgroup-method
1318 This line obviously belongs to a serious-minded intellectual scientific
1319 person (or she may just be plain old boring), because it says that all
1320 groups that have names beginning with @samp{alt} and @samp{rec} should
1321 be ignored, and all groups with names beginning with @samp{sci} should
1322 be subscribed. Gnus will not use the normal subscription method for
1323 subscribing these groups.
1324 @code{gnus-subscribe-options-newsgroup-method} is used instead. This
1325 variable defaults to @code{gnus-subscribe-alphabetically}.
1327 @vindex gnus-options-not-subscribe
1328 @vindex gnus-options-subscribe
1329 If you don't want to mess with your @file{.newsrc} file, you can just
1330 set the two variables @code{gnus-options-subscribe} and
1331 @code{gnus-options-not-subscribe}. These two variables do exactly the
1332 same as the @file{.newsrc} @samp{options -n} trick. Both are regexps,
1333 and if the new group matches the former, it will be unconditionally
1334 subscribed, and if it matches the latter, it will be ignored.
1336 @vindex gnus-auto-subscribed-groups
1337 Yet another variable that meddles here is
1338 @code{gnus-auto-subscribed-groups}. It works exactly like
1339 @code{gnus-options-subscribe}, and is therefore really superfluous,
1340 but I thought it would be nice to have two of these. This variable is
1341 more meant for setting some ground rules, while the other variable is
1342 used more for user fiddling. By default this variable makes all new
1343 groups that come from mail back ends (@code{nnml}, @code{nnbabyl},
1344 @code{nnfolder}, @code{nnmbox}, @code{nnmh}, and @code{nnmaildir})
1345 subscribed. If you don't like that, just set this variable to
1348 New groups that match this regexp are subscribed using
1349 @code{gnus-subscribe-options-newsgroup-method}.
1352 @node Changing Servers
1353 @section Changing Servers
1354 @cindex changing servers
1356 Sometimes it is necessary to move from one @acronym{NNTP} server to another.
1357 This happens very rarely, but perhaps you change jobs, or one server is
1358 very flaky and you want to use another.
1360 Changing the server is pretty easy, right? You just change
1361 @code{gnus-select-method} to point to the new server?
1365 Article numbers are not (in any way) kept synchronized between different
1366 @acronym{NNTP} servers, and the only way Gnus keeps track of what articles
1367 you have read is by keeping track of article numbers. So when you
1368 change @code{gnus-select-method}, your @file{.newsrc} file becomes
1371 Gnus provides a few functions to attempt to translate a @file{.newsrc}
1372 file from one server to another. They all have one thing in
1373 common---they take a looong time to run. You don't want to use these
1374 functions more than absolutely necessary.
1376 @kindex M-x gnus-change-server
1377 @findex gnus-change-server
1378 If you have access to both servers, Gnus can request the headers for all
1379 the articles you have read and compare @code{Message-ID}s and map the
1380 article numbers of the read articles and article marks. The @kbd{M-x
1381 gnus-change-server} command will do this for all your native groups. It
1382 will prompt for the method you want to move to.
1384 @kindex M-x gnus-group-move-group-to-server
1385 @findex gnus-group-move-group-to-server
1386 You can also move individual groups with the @kbd{M-x
1387 gnus-group-move-group-to-server} command. This is useful if you want to
1388 move a (foreign) group from one server to another.
1390 @kindex M-x gnus-group-clear-data-on-native-groups
1391 @findex gnus-group-clear-data-on-native-groups
1392 If you don't have access to both the old and new server, all your marks
1393 and read ranges have become worthless. You can use the @kbd{M-x
1394 gnus-group-clear-data-on-native-groups} command to clear out all data
1395 that you have on your native groups. Use with caution.
1397 @kindex M-x gnus-group-clear-data
1398 @findex gnus-group-clear-data
1399 Clear the data from the current group only---nix out marks and the
1400 list of read articles (@code{gnus-group-clear-data}).
1402 After changing servers, you @strong{must} move the cache hierarchy away,
1403 since the cached articles will have wrong article numbers, which will
1404 affect which articles Gnus thinks are read.
1405 @code{gnus-group-clear-data-on-native-groups} will ask you if you want
1406 to have it done automatically; for @code{gnus-group-clear-data}, you
1407 can use @kbd{M-x gnus-cache-move-cache} (but beware, it will move the
1408 cache for all groups).
1412 @section Startup Files
1413 @cindex startup files
1418 Most common Unix news readers use a shared startup file called
1419 @file{.newsrc}. This file contains all the information about what
1420 groups are subscribed, and which articles in these groups have been
1423 Things got a bit more complicated with @sc{gnus}. In addition to
1424 keeping the @file{.newsrc} file updated, it also used a file called
1425 @file{.newsrc.el} for storing all the information that didn't fit into
1426 the @file{.newsrc} file. (Actually, it also duplicated everything in
1427 the @file{.newsrc} file.) @sc{gnus} would read whichever one of these
1428 files was the most recently saved, which enabled people to swap between
1429 @sc{gnus} and other newsreaders.
1431 That was kinda silly, so Gnus went one better: In addition to the
1432 @file{.newsrc} and @file{.newsrc.el} files, Gnus also has a file called
1433 @file{.newsrc.eld}. It will read whichever of these files that are most
1434 recent, but it will never write a @file{.newsrc.el} file. You should
1435 never delete the @file{.newsrc.eld} file---it contains much information
1436 not stored in the @file{.newsrc} file.
1438 @vindex gnus-save-newsrc-file
1439 @vindex gnus-read-newsrc-file
1440 You can turn off writing the @file{.newsrc} file by setting
1441 @code{gnus-save-newsrc-file} to @code{nil}, which means you can delete
1442 the file and save some space, as well as exiting from Gnus faster.
1443 However, this will make it impossible to use other newsreaders than
1444 Gnus. But hey, who would want to, right? Similarly, setting
1445 @code{gnus-read-newsrc-file} to @code{nil} makes Gnus ignore the
1446 @file{.newsrc} file and any @file{.newsrc-SERVER} files, which can be
1447 convenient if you use a different news reader occasionally, and you
1448 want to read a different subset of the available groups with that
1451 @vindex gnus-save-killed-list
1452 If @code{gnus-save-killed-list} (default @code{t}) is @code{nil}, Gnus
1453 will not save the list of killed groups to the startup file. This will
1454 save both time (when starting and quitting) and space (on disk). It
1455 will also mean that Gnus has no record of what groups are new or old,
1456 so the automatic new groups subscription methods become meaningless.
1457 You should always set @code{gnus-check-new-newsgroups} to @code{nil} or
1458 @code{ask-server} if you set this variable to @code{nil} (@pxref{New
1459 Groups}). This variable can also be a regular expression. If that's
1460 the case, remove all groups that do not match this regexp before
1461 saving. This can be useful in certain obscure situations that involve
1462 several servers where not all servers support @code{ask-server}.
1464 @vindex gnus-startup-file
1465 @vindex gnus-backup-startup-file
1466 @vindex version-control
1467 The @code{gnus-startup-file} variable says where the startup files are.
1468 The default value is @file{~/.newsrc}, with the Gnus (El Dingo) startup
1469 file being whatever that one is, with a @samp{.eld} appended.
1470 If you want version control for this file, set
1471 @code{gnus-backup-startup-file}. It respects the same values as the
1472 @code{version-control} variable.
1474 @vindex gnus-save-newsrc-hook
1475 @vindex gnus-save-quick-newsrc-hook
1476 @vindex gnus-save-standard-newsrc-hook
1477 @code{gnus-save-newsrc-hook} is called before saving any of the newsrc
1478 files, while @code{gnus-save-quick-newsrc-hook} is called just before
1479 saving the @file{.newsrc.eld} file, and
1480 @code{gnus-save-standard-newsrc-hook} is called just before saving the
1481 @file{.newsrc} file. The latter two are commonly used to turn version
1482 control on or off. Version control is on by default when saving the
1483 startup files. If you want to turn backup creation off, say something like:
1486 (defun turn-off-backup ()
1487 (set (make-local-variable 'backup-inhibited) t))
1489 (add-hook 'gnus-save-quick-newsrc-hook 'turn-off-backup)
1490 (add-hook 'gnus-save-standard-newsrc-hook 'turn-off-backup)
1493 @vindex gnus-init-file
1494 @vindex gnus-site-init-file
1495 When Gnus starts, it will read the @code{gnus-site-init-file}
1496 (@file{.../site-lisp/gnus-init} by default) and @code{gnus-init-file}
1497 (@file{~/.gnus} by default) files. These are normal Emacs Lisp files
1498 and can be used to avoid cluttering your @file{~/.emacs} and
1499 @file{site-init} files with Gnus stuff. Gnus will also check for files
1500 with the same names as these, but with @file{.elc} and @file{.el}
1501 suffixes. In other words, if you have set @code{gnus-init-file} to
1502 @file{~/.gnus}, it will look for @file{~/.gnus.elc}, @file{~/.gnus.el},
1503 and finally @file{~/.gnus} (in this order). If Emacs was invoked with
1504 the @option{-q} or @option{--no-init-file} options (@pxref{Initial
1505 Options, ,Initial Options, emacs, The Emacs Manual}), Gnus doesn't read
1506 @code{gnus-init-file}.
1511 @cindex dribble file
1514 Whenever you do something that changes the Gnus data (reading articles,
1515 catching up, killing/subscribing groups), the change is added to a
1516 special @dfn{dribble buffer}. This buffer is auto-saved the normal
1517 Emacs way. If your Emacs should crash before you have saved the
1518 @file{.newsrc} files, all changes you have made can be recovered from
1521 If Gnus detects this file at startup, it will ask the user whether to
1522 read it. The auto save file is deleted whenever the real startup file is
1525 @vindex gnus-use-dribble-file
1526 If @code{gnus-use-dribble-file} is @code{nil}, Gnus won't create and
1527 maintain a dribble buffer. The default is @code{t}.
1529 @vindex gnus-dribble-directory
1530 Gnus will put the dribble file(s) in @code{gnus-dribble-directory}. If
1531 this variable is @code{nil}, which it is by default, Gnus will dribble
1532 into the directory where the @file{.newsrc} file is located. (This is
1533 normally the user's home directory.) The dribble file will get the same
1534 file permissions as the @file{.newsrc} file.
1536 @vindex gnus-always-read-dribble-file
1537 If @code{gnus-always-read-dribble-file} is non-@code{nil}, Gnus will
1538 read the dribble file on startup without querying the user.
1541 @node The Active File
1542 @section The Active File
1544 @cindex ignored groups
1546 When Gnus starts, or indeed whenever it tries to determine whether new
1547 articles have arrived, it reads the active file. This is a very large
1548 file that lists all the active groups and articles on the server.
1550 @vindex gnus-ignored-newsgroups
1551 Before examining the active file, Gnus deletes all lines that match the
1552 regexp @code{gnus-ignored-newsgroups}. This is done primarily to reject
1553 any groups with bogus names, but you can use this variable to make Gnus
1554 ignore hierarchies you aren't ever interested in. However, this is not
1555 recommended. In fact, it's highly discouraged. Instead, @pxref{New
1556 Groups} for an overview of other variables that can be used instead.
1559 @c @code{nil} by default, and will slow down active file handling somewhat
1560 @c if you set it to anything else.
1562 @vindex gnus-read-active-file
1564 The active file can be rather Huge, so if you have a slow network, you
1565 can set @code{gnus-read-active-file} to @code{nil} to prevent Gnus from
1566 reading the active file. This variable is @code{some} by default.
1568 Gnus will try to make do by getting information just on the groups that
1569 you actually subscribe to.
1571 Note that if you subscribe to lots and lots of groups, setting this
1572 variable to @code{nil} will probably make Gnus slower, not faster. At
1573 present, having this variable @code{nil} will slow Gnus down
1574 considerably, unless you read news over a 2400 baud modem.
1576 This variable can also have the value @code{some}. Gnus will then
1577 attempt to read active info only on the subscribed groups. On some
1578 servers this is quite fast (on sparkling, brand new INN servers that
1579 support the @code{LIST ACTIVE group} command), on others this isn't fast
1580 at all. In any case, @code{some} should be faster than @code{nil}, and
1581 is certainly faster than @code{t} over slow lines.
1583 Some news servers (old versions of Leafnode and old versions of INN, for
1584 instance) do not support the @code{LIST ACTIVE group}. For these
1585 servers, @code{nil} is probably the most efficient value for this
1588 If this variable is @code{nil}, Gnus will ask for group info in total
1589 lock-step, which isn't very fast. If it is @code{some} and you use an
1590 @acronym{NNTP} server, Gnus will pump out commands as fast as it can, and
1591 read all the replies in one swoop. This will normally result in better
1592 performance, but if the server does not support the aforementioned
1593 @code{LIST ACTIVE group} command, this isn't very nice to the server.
1595 If you think that starting up Gnus takes too long, try all the three
1596 different values for this variable and see what works best for you.
1598 In any case, if you use @code{some} or @code{nil}, you should definitely
1599 kill all groups that you aren't interested in to speed things up.
1601 Note that this variable also affects active file retrieval from
1602 secondary select methods.
1605 @node Startup Variables
1606 @section Startup Variables
1610 @item gnus-load-hook
1611 @vindex gnus-load-hook
1612 A hook run while Gnus is being loaded. Note that this hook will
1613 normally be run just once in each Emacs session, no matter how many
1614 times you start Gnus.
1616 @item gnus-before-startup-hook
1617 @vindex gnus-before-startup-hook
1618 A hook run after starting up Gnus successfully.
1620 @item gnus-startup-hook
1621 @vindex gnus-startup-hook
1622 A hook run as the very last thing after starting up Gnus
1624 @item gnus-started-hook
1625 @vindex gnus-started-hook
1626 A hook that is run as the very last thing after starting up Gnus
1629 @item gnus-setup-news-hook
1630 @vindex gnus-setup-news-hook
1631 A hook that is run after reading the @file{.newsrc} file(s), but before
1632 generating the group buffer.
1634 @item gnus-check-bogus-newsgroups
1635 @vindex gnus-check-bogus-newsgroups
1636 If non-@code{nil}, Gnus will check for and delete all bogus groups at
1637 startup. A @dfn{bogus group} is a group that you have in your
1638 @file{.newsrc} file, but doesn't exist on the news server. Checking for
1639 bogus groups can take quite a while, so to save time and resources it's
1640 best to leave this option off, and do the checking for bogus groups once
1641 in a while from the group buffer instead (@pxref{Group Maintenance}).
1643 @item gnus-inhibit-startup-message
1644 @vindex gnus-inhibit-startup-message
1645 If non-@code{nil}, the startup message won't be displayed. That way,
1646 your boss might not notice as easily that you are reading news instead
1647 of doing your job. Note that this variable is used before
1648 @file{~/.gnus.el} is loaded, so it should be set in @file{.emacs} instead.
1650 @item gnus-no-groups-message
1651 @vindex gnus-no-groups-message
1652 Message displayed by Gnus when no groups are available.
1654 @item gnus-play-startup-jingle
1655 @vindex gnus-play-startup-jingle
1656 If non-@code{nil}, play the Gnus jingle at startup.
1658 @item gnus-startup-jingle
1659 @vindex gnus-startup-jingle
1660 Jingle to be played if the above variable is non-@code{nil}. The
1661 default is @samp{Tuxedomoon.Jingle4.au}.
1667 @chapter Group Buffer
1668 @cindex group buffer
1670 @c Alex Schroeder suggests to rearrange this as follows:
1672 @c <kensanata> ok, just save it for reference. I'll go to bed in a minute.
1673 @c 1. Selecting a Group, 2. (new) Finding a Group, 3. Group Levels,
1674 @c 4. Subscription Commands, 5. Group Maneuvering, 6. Group Data,
1675 @c 7. Group Score, 8. Group Buffer Format
1676 @c <kensanata> Group Levels should have more information on levels 5 to 9. I
1677 @c suggest to split the 4th paragraph ("Gnus considers groups...") as follows:
1678 @c <kensanata> First, "Gnus considers groups... (default 9)."
1679 @c <kensanata> New, a table summarizing what levels 1 to 9 mean.
1680 @c <kensanata> Third, "Gnus treats subscribed ... reasons of efficiency"
1681 @c <kensanata> Then expand the next paragraph or add some more to it.
1682 @c This short one sentence explains levels 1 and 2, therefore I understand
1683 @c that I should keep important news at 3 and boring news at 4.
1684 @c Say so! Then go on to explain why I should bother with levels 6 to 9.
1685 @c Maybe keep those that you don't want to read temporarily at 6,
1686 @c those that you never want to read at 8, those that offend your
1687 @c human rights at 9...
1690 The @dfn{group buffer} lists all (or parts) of the available groups. It
1691 is the first buffer shown when Gnus starts, and will never be killed as
1692 long as Gnus is active.
1696 \gnusfigure{The Group Buffer}{320}{
1697 \put(75,50){\epsfig{figure=ps/group,height=9cm}}
1698 \put(120,37){\makebox(0,0)[t]{Buffer name}}
1699 \put(120,38){\vector(1,2){10}}
1700 \put(40,60){\makebox(0,0)[r]{Mode line}}
1701 \put(40,58){\vector(1,0){30}}
1702 \put(200,28){\makebox(0,0)[t]{Native select method}}
1703 \put(200,26){\vector(-1,2){15}}
1709 * Group Buffer Format:: Information listed and how you can change it.
1710 * Group Maneuvering:: Commands for moving in the group buffer.
1711 * Selecting a Group:: Actually reading news.
1712 * Subscription Commands:: Unsubscribing, killing, subscribing.
1713 * Group Data:: Changing the info for a group.
1714 * Group Levels:: Levels? What are those, then?
1715 * Group Score:: A mechanism for finding out what groups you like.
1716 * Marking Groups:: You can mark groups for later processing.
1717 * Foreign Groups:: Creating and editing groups.
1718 * Group Parameters:: Each group may have different parameters set.
1719 * Listing Groups:: Gnus can list various subsets of the groups.
1720 * Sorting Groups:: Re-arrange the group order.
1721 * Group Maintenance:: Maintaining a tidy @file{.newsrc} file.
1722 * Browse Foreign Server:: You can browse a server. See what it has to offer.
1723 * Exiting Gnus:: Stop reading news and get some work done.
1724 * Group Topics:: A folding group mode divided into topics.
1725 * Misc Group Stuff:: Other stuff that you can to do.
1729 @node Group Buffer Format
1730 @section Group Buffer Format
1733 * Group Line Specification:: Deciding how the group buffer is to look.
1734 * Group Mode Line Specification:: The group buffer mode line.
1735 * Group Highlighting:: Having nice colors in the group buffer.
1739 @node Group Line Specification
1740 @subsection Group Line Specification
1741 @cindex group buffer format
1743 The default format of the group buffer is nice and dull, but you can
1744 make it as exciting and ugly as you feel like.
1746 Here's a couple of example group lines:
1749 25: news.announce.newusers
1750 * 0: alt.fan.andrea-dworkin
1755 You can see that there are 25 unread articles in
1756 @samp{news.announce.newusers}. There are no unread articles, but some
1757 ticked articles, in @samp{alt.fan.andrea-dworkin} (see that little
1758 asterisk at the beginning of the line?).
1760 @vindex gnus-group-line-format
1761 You can change that format to whatever you want by fiddling with the
1762 @code{gnus-group-line-format} variable. This variable works along the
1763 lines of a @code{format} specification, which is pretty much the same as
1764 a @code{printf} specifications, for those of you who use (feh!) C.
1765 @xref{Formatting Variables}.
1767 @samp{%M%S%5y:%B%(%g%)\n} is the value that produced those lines above.
1769 There should always be a colon on the line; the cursor always moves to
1770 the colon after performing an operation. @xref{Positioning
1771 Point}. Nothing else is required---not even the group name. All
1772 displayed text is just window dressing, and is never examined by Gnus.
1773 Gnus stores all real information it needs using text properties.
1775 (Note that if you make a really strange, wonderful, spreadsheet-like
1776 layout, everybody will believe you are hard at work with the accounting
1777 instead of wasting time reading news.)
1779 Here's a list of all available format characters:
1784 An asterisk if the group only has marked articles.
1787 Whether the group is subscribed.
1790 Level of subscribedness.
1793 Number of unread articles.
1796 Number of dormant articles.
1799 Number of ticked articles.
1802 Number of read articles.
1805 Number of unseen articles.
1808 Estimated total number of articles. (This is really @var{max-number}
1809 minus @var{min-number} plus 1.)
1811 Gnus uses this estimation because the @acronym{NNTP} protocol provides
1812 efficient access to @var{max-number} and @var{min-number} but getting
1813 the true unread message count is not possible efficiently. For
1814 hysterical raisins, even the mail back ends, where the true number of
1815 unread messages might be available efficiently, use the same limited
1816 interface. To remove this restriction from Gnus means that the back
1817 end interface has to be changed, which is not an easy job. If you
1818 want to work on this, please contact the Gnus mailing list.
1821 Number of unread, unticked, non-dormant articles.
1824 Number of ticked and dormant articles.
1833 Group comment (@pxref{Group Parameters}) or group name if there is no
1834 comment element in the group parameters.
1837 Newsgroup description. You need to read the group descriptions
1838 before these will appear, and to do that, you either have to set
1839 @code{gnus-read-active-file} or use the group buffer @kbd{M-d}
1843 @samp{m} if moderated.
1846 @samp{(m)} if moderated.
1852 If the summary buffer for the group is open or not.
1858 A string that looks like @samp{<%s:%n>} if a foreign select method is
1862 Indentation based on the level of the topic (@pxref{Group Topics}).
1865 @vindex gnus-group-uncollapsed-levels
1866 Short (collapsed) group name. The @code{gnus-group-uncollapsed-levels}
1867 variable says how many levels to leave at the end of the group name.
1868 The default is 1---this will mean that group names like
1869 @samp{gnu.emacs.gnus} will be shortened to @samp{g.e.gnus}.
1872 @vindex gnus-new-mail-mark
1874 @samp{%} (@code{gnus-new-mail-mark}) if there has arrived new mail to
1878 @samp{#} (@code{gnus-process-mark}) if the group is process marked.
1881 A string that says when you last read the group (@pxref{Group
1885 The disk space used by the articles fetched by both the cache and
1886 agent. The value is automatically scaled to bytes(B), kilobytes(K),
1887 megabytes(M), or gigabytes(G) to minimize the column width. A format
1888 of %7F is sufficient for a fixed-width column.
1891 User defined specifier. The next character in the format string should
1892 be a letter. Gnus will call the function
1893 @code{gnus-user-format-function-}@samp{X}, where @samp{X} is the letter
1894 following @samp{%u}. The function will be passed a single dummy
1895 parameter as argument. The function should return a string, which will
1896 be inserted into the buffer just like information from any other
1901 All the ``number-of'' specs will be filled with an asterisk (@samp{*})
1902 if no info is available---for instance, if it is a non-activated foreign
1903 group, or a bogus native group.
1906 @node Group Mode Line Specification
1907 @subsection Group Mode Line Specification
1908 @cindex group mode line
1910 @vindex gnus-group-mode-line-format
1911 The mode line can be changed by setting
1912 @code{gnus-group-mode-line-format} (@pxref{Mode Line Formatting}). It
1913 doesn't understand that many format specifiers:
1917 The native news server.
1919 The native select method.
1923 @node Group Highlighting
1924 @subsection Group Highlighting
1925 @cindex highlighting
1926 @cindex group highlighting
1928 @vindex gnus-group-highlight
1929 Highlighting in the group buffer is controlled by the
1930 @code{gnus-group-highlight} variable. This is an alist with elements
1931 that look like @code{(@var{form} . @var{face})}. If @var{form} evaluates to
1932 something non-@code{nil}, the @var{face} will be used on the line.
1934 Here's an example value for this variable that might look nice if the
1938 (cond (window-system
1939 (setq custom-background-mode 'light)
1940 (defface my-group-face-1
1941 '((t (:foreground "Red" :bold t))) "First group face")
1942 (defface my-group-face-2
1943 '((t (:foreground "DarkSeaGreen4" :bold t)))
1944 "Second group face")
1945 (defface my-group-face-3
1946 '((t (:foreground "Green4" :bold t))) "Third group face")
1947 (defface my-group-face-4
1948 '((t (:foreground "SteelBlue" :bold t))) "Fourth group face")
1949 (defface my-group-face-5
1950 '((t (:foreground "Blue" :bold t))) "Fifth group face")))
1952 (setq gnus-group-highlight
1953 '(((> unread 200) . my-group-face-1)
1954 ((and (< level 3) (zerop unread)) . my-group-face-2)
1955 ((< level 3) . my-group-face-3)
1956 ((zerop unread) . my-group-face-4)
1957 (t . my-group-face-5)))
1960 Also @pxref{Faces and Fonts}.
1962 Variables that are dynamically bound when the forms are evaluated
1969 The number of unread articles in the group.
1973 Whether the group is a mail group.
1975 The level of the group.
1977 The score of the group.
1979 The number of ticked articles in the group.
1981 The total number of articles in the group. Or rather,
1982 @var{max-number} minus @var{min-number} plus one.
1984 When using the topic minor mode, this variable is bound to the current
1985 topic being inserted.
1988 When the forms are @code{eval}ed, point is at the beginning of the line
1989 of the group in question, so you can use many of the normal Gnus
1990 functions for snarfing info on the group.
1992 @vindex gnus-group-update-hook
1993 @findex gnus-group-highlight-line
1994 @code{gnus-group-update-hook} is called when a group line is changed.
1995 It will not be called when @code{gnus-visual} is @code{nil}. This hook
1996 calls @code{gnus-group-highlight-line} by default.
1999 @node Group Maneuvering
2000 @section Group Maneuvering
2001 @cindex group movement
2003 All movement commands understand the numeric prefix and will behave as
2004 expected, hopefully.
2010 @findex gnus-group-next-unread-group
2011 Go to the next group that has unread articles
2012 (@code{gnus-group-next-unread-group}).
2018 @findex gnus-group-prev-unread-group
2019 Go to the previous group that has unread articles
2020 (@code{gnus-group-prev-unread-group}).
2024 @findex gnus-group-next-group
2025 Go to the next group (@code{gnus-group-next-group}).
2029 @findex gnus-group-prev-group
2030 Go to the previous group (@code{gnus-group-prev-group}).
2034 @findex gnus-group-next-unread-group-same-level
2035 Go to the next unread group on the same (or lower) level
2036 (@code{gnus-group-next-unread-group-same-level}).
2040 @findex gnus-group-prev-unread-group-same-level
2041 Go to the previous unread group on the same (or lower) level
2042 (@code{gnus-group-prev-unread-group-same-level}).
2045 Three commands for jumping to groups:
2051 @findex gnus-group-jump-to-group
2052 Jump to a group (and make it visible if it isn't already)
2053 (@code{gnus-group-jump-to-group}). Killed groups can be jumped to, just
2058 @findex gnus-group-best-unread-group
2059 Jump to the unread group with the lowest level
2060 (@code{gnus-group-best-unread-group}).
2064 @findex gnus-group-first-unread-group
2065 Jump to the first group with unread articles
2066 (@code{gnus-group-first-unread-group}).
2069 @vindex gnus-group-goto-unread
2070 If @code{gnus-group-goto-unread} is @code{nil}, all the movement
2071 commands will move to the next group, not the next unread group. Even
2072 the commands that say they move to the next unread group. The default
2076 @node Selecting a Group
2077 @section Selecting a Group
2078 @cindex group selection
2083 @kindex SPACE (Group)
2084 @findex gnus-group-read-group
2085 Select the current group, switch to the summary buffer and display the
2086 first unread article (@code{gnus-group-read-group}). If there are no
2087 unread articles in the group, or if you give a non-numerical prefix to
2088 this command, Gnus will offer to fetch all the old articles in this
2089 group from the server. If you give a numerical prefix @var{n}, @var{n}
2090 determines the number of articles Gnus will fetch. If @var{n} is
2091 positive, Gnus fetches the @var{n} newest articles, if @var{n} is
2092 negative, Gnus fetches the @code{abs(@var{n})} oldest articles.
2094 Thus, @kbd{SPC} enters the group normally, @kbd{C-u SPC} offers old
2095 articles, @kbd{C-u 4 2 SPC} fetches the 42 newest articles, and @kbd{C-u
2096 - 4 2 SPC} fetches the 42 oldest ones.
2098 When you are in the group (in the Summary buffer), you can type
2099 @kbd{M-g} to fetch new articles, or @kbd{C-u M-g} to also show the old
2104 @findex gnus-group-select-group
2105 Select the current group and switch to the summary buffer
2106 (@code{gnus-group-select-group}). Takes the same arguments as
2107 @code{gnus-group-read-group}---the only difference is that this command
2108 does not display the first unread article automatically upon group
2112 @kindex M-RET (Group)
2113 @findex gnus-group-quick-select-group
2114 This does the same as the command above, but tries to do it with the
2115 minimum amount of fuzz (@code{gnus-group-quick-select-group}). No
2116 scoring/killing will be performed, there will be no highlights and no
2117 expunging. This might be useful if you're in a real hurry and have to
2118 enter some humongous group. If you give a 0 prefix to this command
2119 (i.e., @kbd{0 M-RET}), Gnus won't even generate the summary buffer,
2120 which is useful if you want to toggle threading before generating the
2121 summary buffer (@pxref{Summary Generation Commands}).
2124 @kindex M-SPACE (Group)
2125 @findex gnus-group-visible-select-group
2126 This is yet one more command that does the same as the @kbd{RET}
2127 command, but this one does it without expunging and hiding dormants
2128 (@code{gnus-group-visible-select-group}).
2131 @kindex C-M-RET (Group)
2132 @findex gnus-group-select-group-ephemerally
2133 Finally, this command selects the current group ephemerally without
2134 doing any processing of its contents
2135 (@code{gnus-group-select-group-ephemerally}). Even threading has been
2136 turned off. Everything you do in the group after selecting it in this
2137 manner will have no permanent effects.
2141 @vindex gnus-large-newsgroup
2142 The @code{gnus-large-newsgroup} variable says what Gnus should
2143 consider to be a big group. If it is @code{nil}, no groups are
2144 considered big. The default value is 200. If the group has more
2145 (unread and/or ticked) articles than this, Gnus will query the user
2146 before entering the group. The user can then specify how many
2147 articles should be fetched from the server. If the user specifies a
2148 negative number (@var{-n}), the @var{n} oldest articles will be
2149 fetched. If it is positive, the @var{n} articles that have arrived
2150 most recently will be fetched.
2152 @vindex gnus-large-ephemeral-newsgroup
2153 @code{gnus-large-ephemeral-newsgroup} is the same as
2154 @code{gnus-large-newsgroup}, but is only used for ephemeral
2157 @vindex gnus-select-group-hook
2158 @vindex gnus-auto-select-first
2159 @vindex gnus-auto-select-subject
2160 If @code{gnus-auto-select-first} is non-@code{nil}, select an article
2161 automatically when entering a group with the @kbd{SPACE} command.
2162 Which article this is is controlled by the
2163 @code{gnus-auto-select-subject} variable. Valid values for this
2169 Place point on the subject line of the first unread article.
2172 Place point on the subject line of the first article.
2175 Place point on the subject line of the first unseen article.
2177 @item unseen-or-unread
2178 Place point on the subject line of the first unseen article, and if
2179 there is no such article, place point on the subject line of the first
2183 Place point on the subject line of the highest-scored unread article.
2187 This variable can also be a function. In that case, that function
2188 will be called to place point on a subject line.
2190 If you want to prevent automatic selection in some group (say, in a
2191 binary group with Huge articles) you can set the
2192 @code{gnus-auto-select-first} variable to @code{nil} in
2193 @code{gnus-select-group-hook}, which is called when a group is
2197 @node Subscription Commands
2198 @section Subscription Commands
2199 @cindex subscription
2207 @findex gnus-group-unsubscribe-current-group
2208 @c @icon{gnus-group-unsubscribe}
2209 Toggle subscription to the current group
2210 (@code{gnus-group-unsubscribe-current-group}).
2216 @findex gnus-group-unsubscribe-group
2217 Prompt for a group to subscribe, and then subscribe it. If it was
2218 subscribed already, unsubscribe it instead
2219 (@code{gnus-group-unsubscribe-group}).
2225 @findex gnus-group-kill-group
2226 @c @icon{gnus-group-kill-group}
2227 Kill the current group (@code{gnus-group-kill-group}).
2233 @findex gnus-group-yank-group
2234 Yank the last killed group (@code{gnus-group-yank-group}).
2237 @kindex C-x C-t (Group)
2238 @findex gnus-group-transpose-groups
2239 Transpose two groups (@code{gnus-group-transpose-groups}). This isn't
2240 really a subscription command, but you can use it instead of a
2241 kill-and-yank sequence sometimes.
2247 @findex gnus-group-kill-region
2248 Kill all groups in the region (@code{gnus-group-kill-region}).
2252 @findex gnus-group-kill-all-zombies
2253 Kill all zombie groups (@code{gnus-group-kill-all-zombies}).
2256 @kindex S C-k (Group)
2257 @findex gnus-group-kill-level
2258 Kill all groups on a certain level (@code{gnus-group-kill-level}).
2259 These groups can't be yanked back after killing, so this command should
2260 be used with some caution. The only time where this command comes in
2261 really handy is when you have a @file{.newsrc} with lots of unsubscribed
2262 groups that you want to get rid off. @kbd{S C-k} on level 7 will
2263 kill off all unsubscribed groups that do not have message numbers in the
2264 @file{.newsrc} file.
2268 Also @pxref{Group Levels}.
2278 @findex gnus-group-catchup-current
2279 @vindex gnus-group-catchup-group-hook
2280 @c @icon{gnus-group-catchup-current}
2281 Mark all unticked articles in this group as read
2282 (@code{gnus-group-catchup-current}).
2283 @code{gnus-group-catchup-group-hook} is called when catching up a group from
2288 @findex gnus-group-catchup-current-all
2289 Mark all articles in this group, even the ticked ones, as read
2290 (@code{gnus-group-catchup-current-all}).
2294 @findex gnus-group-clear-data
2295 Clear the data from the current group---nix out marks and the list of
2296 read articles (@code{gnus-group-clear-data}).
2298 @item M-x gnus-group-clear-data-on-native-groups
2299 @kindex M-x gnus-group-clear-data-on-native-groups
2300 @findex gnus-group-clear-data-on-native-groups
2301 If you have switched from one @acronym{NNTP} server to another, all your marks
2302 and read ranges have become worthless. You can use this command to
2303 clear out all data that you have on your native groups. Use with
2310 @section Group Levels
2314 All groups have a level of @dfn{subscribedness}. For instance, if a
2315 group is on level 2, it is more subscribed than a group on level 5. You
2316 can ask Gnus to just list groups on a given level or lower
2317 (@pxref{Listing Groups}), or to just check for new articles in groups on
2318 a given level or lower (@pxref{Scanning New Messages}).
2320 Remember: The higher the level of the group, the less important it is.
2326 @findex gnus-group-set-current-level
2327 Set the level of the current group. If a numeric prefix is given, the
2328 next @var{n} groups will have their levels set. The user will be
2329 prompted for a level.
2332 @vindex gnus-level-killed
2333 @vindex gnus-level-zombie
2334 @vindex gnus-level-unsubscribed
2335 @vindex gnus-level-subscribed
2336 Gnus considers groups from levels 1 to
2337 @code{gnus-level-subscribed} (inclusive) (default 5) to be subscribed,
2338 @code{gnus-level-subscribed} (exclusive) and
2339 @code{gnus-level-unsubscribed} (inclusive) (default 7) to be
2340 unsubscribed, @code{gnus-level-zombie} to be zombies (walking dead)
2341 (default 8) and @code{gnus-level-killed} to be killed (completely dead)
2342 (default 9). Gnus treats subscribed and unsubscribed groups exactly the
2343 same, but zombie and killed groups have no information on what articles
2344 you have read, etc, stored. This distinction between dead and living
2345 groups isn't done because it is nice or clever, it is done purely for
2346 reasons of efficiency.
2348 It is recommended that you keep all your mail groups (if any) on quite
2349 low levels (e.g. 1 or 2).
2351 Maybe the following description of the default behavior of Gnus helps to
2352 understand what these levels are all about. By default, Gnus shows you
2353 subscribed nonempty groups, but by hitting @kbd{L} you can have it show
2354 empty subscribed groups and unsubscribed groups, too. Type @kbd{l} to
2355 go back to showing nonempty subscribed groups again. Thus, unsubscribed
2356 groups are hidden, in a way.
2358 Zombie and killed groups are similar to unsubscribed groups in that they
2359 are hidden by default. But they are different from subscribed and
2360 unsubscribed groups in that Gnus doesn't ask the news server for
2361 information (number of messages, number of unread messages) on zombie
2362 and killed groups. Normally, you use @kbd{C-k} to kill the groups you
2363 aren't interested in. If most groups are killed, Gnus is faster.
2365 Why does Gnus distinguish between zombie and killed groups? Well, when
2366 a new group arrives on the server, Gnus by default makes it a zombie
2367 group. This means that you are normally not bothered with new groups,
2368 but you can type @kbd{A z} to get a list of all new groups. Subscribe
2369 the ones you like and kill the ones you don't want. (@kbd{A k} shows a
2370 list of killed groups.)
2372 If you want to play with the level variables, you should show some care.
2373 Set them once, and don't touch them ever again. Better yet, don't touch
2374 them at all unless you know exactly what you're doing.
2376 @vindex gnus-level-default-unsubscribed
2377 @vindex gnus-level-default-subscribed
2378 Two closely related variables are @code{gnus-level-default-subscribed}
2379 (default 3) and @code{gnus-level-default-unsubscribed} (default 6),
2380 which are the levels that new groups will be put on if they are
2381 (un)subscribed. These two variables should, of course, be inside the
2382 relevant valid ranges.
2384 @vindex gnus-keep-same-level
2385 If @code{gnus-keep-same-level} is non-@code{nil}, some movement commands
2386 will only move to groups of the same level (or lower). In
2387 particular, going from the last article in one group to the next group
2388 will go to the next group of the same level (or lower). This might be
2389 handy if you want to read the most important groups before you read the
2392 If this variable is @code{best}, Gnus will make the next newsgroup the
2393 one with the best level.
2395 @vindex gnus-group-default-list-level
2396 All groups with a level less than or equal to
2397 @code{gnus-group-default-list-level} will be listed in the group buffer
2400 @vindex gnus-group-list-inactive-groups
2401 If @code{gnus-group-list-inactive-groups} is non-@code{nil}, non-active
2402 groups will be listed along with the unread groups. This variable is
2403 @code{t} by default. If it is @code{nil}, inactive groups won't be
2406 @vindex gnus-group-use-permanent-levels
2407 If @code{gnus-group-use-permanent-levels} is non-@code{nil}, once you
2408 give a level prefix to @kbd{g} or @kbd{l}, all subsequent commands will
2409 use this level as the ``work'' level.
2411 @vindex gnus-activate-level
2412 Gnus will normally just activate (i. e., query the server about) groups
2413 on level @code{gnus-activate-level} or less. If you don't want to
2414 activate unsubscribed groups, for instance, you might set this variable
2415 to 5. The default is 6.
2419 @section Group Score
2424 You would normally keep important groups on high levels, but that scheme
2425 is somewhat restrictive. Don't you wish you could have Gnus sort the
2426 group buffer according to how often you read groups, perhaps? Within
2429 This is what @dfn{group score} is for. You can have Gnus assign a score
2430 to each group through the mechanism described below. You can then sort
2431 the group buffer based on this score. Alternatively, you can sort on
2432 score and then level. (Taken together, the level and the score is
2433 called the @dfn{rank} of the group. A group that is on level 4 and has
2434 a score of 1 has a higher rank than a group on level 5 that has a score
2435 of 300. (The level is the most significant part and the score is the
2436 least significant part.))
2438 @findex gnus-summary-bubble-group
2439 If you want groups you read often to get higher scores than groups you
2440 read seldom you can add the @code{gnus-summary-bubble-group} function to
2441 the @code{gnus-summary-exit-hook} hook. This will result (after
2442 sorting) in a bubbling sort of action. If you want to see that in
2443 action after each summary exit, you can add
2444 @code{gnus-group-sort-groups-by-rank} or
2445 @code{gnus-group-sort-groups-by-score} to the same hook, but that will
2446 slow things down somewhat.
2449 @node Marking Groups
2450 @section Marking Groups
2451 @cindex marking groups
2453 If you want to perform some command on several groups, and they appear
2454 subsequently in the group buffer, you would normally just give a
2455 numerical prefix to the command. Most group commands will then do your
2456 bidding on those groups.
2458 However, if the groups are not in sequential order, you can still
2459 perform a command on several groups. You simply mark the groups first
2460 with the process mark and then execute the command.
2468 @findex gnus-group-mark-group
2469 Set the mark on the current group (@code{gnus-group-mark-group}).
2475 @findex gnus-group-unmark-group
2476 Remove the mark from the current group
2477 (@code{gnus-group-unmark-group}).
2481 @findex gnus-group-unmark-all-groups
2482 Remove the mark from all groups (@code{gnus-group-unmark-all-groups}).
2486 @findex gnus-group-mark-region
2487 Mark all groups between point and mark (@code{gnus-group-mark-region}).
2491 @findex gnus-group-mark-buffer
2492 Mark all groups in the buffer (@code{gnus-group-mark-buffer}).
2496 @findex gnus-group-mark-regexp
2497 Mark all groups that match some regular expression
2498 (@code{gnus-group-mark-regexp}).
2501 Also @pxref{Process/Prefix}.
2503 @findex gnus-group-universal-argument
2504 If you want to execute some command on all groups that have been marked
2505 with the process mark, you can use the @kbd{M-&}
2506 (@code{gnus-group-universal-argument}) command. It will prompt you for
2507 the command to be executed.
2510 @node Foreign Groups
2511 @section Foreign Groups
2512 @cindex foreign groups
2514 Below are some group mode commands for making and editing general foreign
2515 groups, as well as commands to ease the creation of a few
2516 special-purpose groups. All these commands insert the newly created
2517 groups under point---@code{gnus-subscribe-newsgroup-method} is not
2524 @findex gnus-group-make-group
2525 @cindex making groups
2526 Make a new group (@code{gnus-group-make-group}). Gnus will prompt you
2527 for a name, a method and possibly an @dfn{address}. For an easier way
2528 to subscribe to @acronym{NNTP} groups (@pxref{Browse Foreign Server}).
2532 @findex gnus-group-read-ephemeral-group
2533 Make an ephemeral group (@code{gnus-group-read-ephemeral-group}). Gnus
2534 will prompt you for a name, a method and an @dfn{address}.
2538 @findex gnus-group-rename-group
2539 @cindex renaming groups
2540 Rename the current group to something else
2541 (@code{gnus-group-rename-group}). This is valid only on some
2542 groups---mail groups mostly. This command might very well be quite slow
2548 @findex gnus-group-customize
2549 Customize the group parameters (@code{gnus-group-customize}).
2553 @findex gnus-group-edit-group-method
2554 @cindex renaming groups
2555 Enter a buffer where you can edit the select method of the current
2556 group (@code{gnus-group-edit-group-method}).
2560 @findex gnus-group-edit-group-parameters
2561 Enter a buffer where you can edit the group parameters
2562 (@code{gnus-group-edit-group-parameters}).
2566 @findex gnus-group-edit-group
2567 Enter a buffer where you can edit the group info
2568 (@code{gnus-group-edit-group}).
2572 @findex gnus-group-make-directory-group
2574 Make a directory group (@pxref{Directory Groups}). You will be prompted
2575 for a directory name (@code{gnus-group-make-directory-group}).
2580 @findex gnus-group-make-help-group
2581 Make the Gnus help group (@code{gnus-group-make-help-group}).
2585 @cindex (ding) archive
2586 @cindex archive group
2587 @findex gnus-group-make-archive-group
2588 @vindex gnus-group-archive-directory
2589 @vindex gnus-group-recent-archive-directory
2590 Make a Gnus archive group (@code{gnus-group-make-archive-group}). By
2591 default a group pointing to the most recent articles will be created
2592 (@code{gnus-group-recent-archive-directory}), but given a prefix, a full
2593 group will be created from @code{gnus-group-archive-directory}.
2597 @findex gnus-group-make-kiboze-group
2599 Make a kiboze group. You will be prompted for a name, for a regexp to
2600 match groups to be ``included'' in the kiboze group, and a series of
2601 strings to match on headers (@code{gnus-group-make-kiboze-group}).
2602 @xref{Kibozed Groups}.
2606 @findex gnus-group-enter-directory
2608 Read an arbitrary directory as if it were a newsgroup with the
2609 @code{nneething} back end (@code{gnus-group-enter-directory}).
2610 @xref{Anything Groups}.
2614 @findex gnus-group-make-doc-group
2615 @cindex ClariNet Briefs
2617 Make a group based on some file or other
2618 (@code{gnus-group-make-doc-group}). If you give a prefix to this
2619 command, you will be prompted for a file name and a file type.
2620 Currently supported types are @code{mbox}, @code{babyl},
2621 @code{digest}, @code{news}, @code{rnews}, @code{mmdf}, @code{forward},
2622 @code{rfc934}, @code{rfc822-forward}, @code{mime-parts},
2623 @code{standard-digest}, @code{slack-digest}, @code{clari-briefs},
2624 @code{nsmail}, @code{outlook}, @code{oe-dbx}, and @code{mailman}. If
2625 you run this command without a prefix, Gnus will guess at the file
2626 type. @xref{Document Groups}.
2630 @vindex gnus-useful-groups
2631 @findex gnus-group-make-useful-group
2632 Create one of the groups mentioned in @code{gnus-useful-groups}
2633 (@code{gnus-group-make-useful-group}).
2637 @findex gnus-group-make-web-group
2641 Make an ephemeral group based on a web search
2642 (@code{gnus-group-make-web-group}). If you give a prefix to this
2643 command, make a solid group instead. You will be prompted for the
2644 search engine type and the search string. Valid search engine types
2645 include @code{google}, @code{dejanews}, and @code{gmane}.
2646 @xref{Web Searches}.
2648 If you use the @code{google} search engine, you can limit the search
2649 to a particular group by using a match string like
2650 @samp{shaving group:alt.sysadmin.recovery}.
2654 @findex gnus-group-make-rss-group
2655 Make a group based on an @acronym{RSS} feed
2656 (@code{gnus-group-make-rss-group}). You will be prompted for an URL.
2660 @kindex G DEL (Group)
2661 @findex gnus-group-delete-group
2662 This function will delete the current group
2663 (@code{gnus-group-delete-group}). If given a prefix, this function will
2664 actually delete all the articles in the group, and forcibly remove the
2665 group itself from the face of the Earth. Use a prefix only if you are
2666 absolutely sure of what you are doing. This command can't be used on
2667 read-only groups (like @code{nntp} groups), though.
2671 @findex gnus-group-make-empty-virtual
2672 Make a new, fresh, empty @code{nnvirtual} group
2673 (@code{gnus-group-make-empty-virtual}). @xref{Virtual Groups}.
2677 @findex gnus-group-add-to-virtual
2678 Add the current group to an @code{nnvirtual} group
2679 (@code{gnus-group-add-to-virtual}). Uses the process/prefix convention.
2682 @xref{Select Methods}, for more information on the various select
2685 @vindex gnus-activate-foreign-newsgroups
2686 If @code{gnus-activate-foreign-newsgroups} is a positive number,
2687 Gnus will check all foreign groups with this level or lower at startup.
2688 This might take quite a while, especially if you subscribe to lots of
2689 groups from different @acronym{NNTP} servers. Also @pxref{Group Levels};
2690 @code{gnus-activate-level} also affects activation of foreign
2694 @node Group Parameters
2695 @section Group Parameters
2696 @cindex group parameters
2698 The group parameters store information local to a particular group.
2699 Here's an example group parameter list:
2702 ((to-address . "ding@@gnus.org")
2706 We see that each element consists of a ``dotted pair''---the thing before
2707 the dot is the key, while the thing after the dot is the value. All the
2708 parameters have this form @emph{except} local variable specs, which are
2709 not dotted pairs, but proper lists.
2711 Some parameters have correspondent customizable variables, each of which
2712 is an alist of regexps and values.
2714 The following group parameters can be used:
2719 Address used by when doing followups and new posts.
2722 (to-address . "some@@where.com")
2725 This is primarily useful in mail groups that represent closed mailing
2726 lists---mailing lists where it's expected that everybody that writes to
2727 the mailing list is subscribed to it. Since using this parameter
2728 ensures that the mail only goes to the mailing list itself, it means
2729 that members won't receive two copies of your followups.
2731 Using @code{to-address} will actually work whether the group is foreign
2732 or not. Let's say there's a group on the server that is called
2733 @samp{fa.4ad-l}. This is a real newsgroup, but the server has gotten
2734 the articles from a mail-to-news gateway. Posting directly to this
2735 group is therefore impossible---you have to send mail to the mailing
2736 list address instead.
2738 See also @code{gnus-parameter-to-address-alist}.
2742 Address used when doing @kbd{a} in that group.
2745 (to-list . "some@@where.com")
2748 It is totally ignored
2749 when doing a followup---except that if it is present in a news group,
2750 you'll get mail group semantics when doing @kbd{f}.
2752 If you do an @kbd{a} command in a mail group and you have neither a
2753 @code{to-list} group parameter nor a @code{to-address} group parameter,
2754 then a @code{to-list} group parameter will be added automatically upon
2755 sending the message if @code{gnus-add-to-list} is set to @code{t}.
2756 @vindex gnus-add-to-list
2758 @findex gnus-mailing-list-mode
2759 @cindex mail list groups
2760 If this variable is set, @code{gnus-mailing-list-mode} is turned on when
2761 entering summary buffer.
2763 See also @code{gnus-parameter-to-list-alist}.
2768 @cindex Mail-Followup-To
2769 @findex gnus-find-subscribed-addresses
2770 If this parameter is set to @code{t}, Gnus will consider the
2771 to-address and to-list parameters for this group as addresses of
2772 mailing lists you are subscribed to. Giving Gnus this information is
2773 (only) a first step in getting it to generate correct Mail-Followup-To
2774 headers for your posts to these lists. The second step is to put the
2775 following in your @file{.gnus.el}
2778 (setq message-subscribed-address-functions
2779 '(gnus-find-subscribed-addresses))
2782 @xref{Mailing Lists, ,Mailing Lists, message, The Message Manual}, for
2783 a complete treatment of available MFT support.
2787 If the group parameter list has the element @code{(visible . t)},
2788 that group will always be visible in the Group buffer, regardless
2789 of whether it has any unread articles.
2791 This parameter cannot be set via @code{gnus-parameters}. See
2792 @code{gnus-permanently-visible-groups} as an alternative.
2794 @item broken-reply-to
2795 @cindex broken-reply-to
2796 Elements like @code{(broken-reply-to . t)} signals that @code{Reply-To}
2797 headers in this group are to be ignored, and for the header to be hidden
2798 if @code{reply-to} is part of @code{gnus-boring-article-headers}. This
2799 can be useful if you're reading a mailing list group where the listserv
2800 has inserted @code{Reply-To} headers that point back to the listserv
2801 itself. That is broken behavior. So there!
2805 Elements like @code{(to-group . "some.group.name")} means that all
2806 posts in that group will be sent to @code{some.group.name}.
2810 If you have @code{(newsgroup . t)} in the group parameter list, Gnus
2811 will treat all responses as if they were responses to news articles.
2812 This can be useful if you have a mail group that's really a mirror of a
2817 If @code{(gcc-self . t)} is present in the group parameter list, newly
2818 composed messages will be @code{Gcc}'d to the current group. If
2819 @code{(gcc-self . none)} is present, no @code{Gcc:} header will be
2820 generated, if @code{(gcc-self . "string")} is present, this string will
2821 be inserted literally as a @code{gcc} header. This parameter takes
2822 precedence over any default @code{Gcc} rules as described later
2823 (@pxref{Archived Messages}).
2825 @strong{Caveat}: Adding @code{(gcc-self . t)} to the parameter list of
2826 @code{nntp} groups (or the like) isn't valid. An @code{nntp} server
2827 doesn't accept articles.
2831 If the group parameter has an element that looks like @code{(auto-expire
2832 . t)}, all articles read will be marked as expirable. For an
2833 alternative approach, @pxref{Expiring Mail}.
2835 See also @code{gnus-auto-expirable-newsgroups}.
2838 @cindex total-expire
2839 If the group parameter has an element that looks like
2840 @code{(total-expire . t)}, all read articles will be put through the
2841 expiry process, even if they are not marked as expirable. Use with
2842 caution. Unread, ticked and dormant articles are not eligible for
2845 See also @code{gnus-total-expirable-newsgroups}.
2849 @vindex nnmail-expiry-wait-function
2850 If the group parameter has an element that looks like
2851 @code{(expiry-wait . 10)}, this value will override any
2852 @code{nnmail-expiry-wait} and @code{nnmail-expiry-wait-function}
2853 (@pxref{Expiring Mail}) when expiring expirable messages. The value
2854 can either be a number of days (not necessarily an integer) or the
2855 symbols @code{never} or @code{immediate}.
2858 @cindex expiry-target
2859 Where expired messages end up. This parameter overrides
2860 @code{nnmail-expiry-target}.
2863 @cindex score file group parameter
2864 Elements that look like @code{(score-file . "file")} will make
2865 @file{file} into the current score file for the group in question. All
2866 interactive score entries will be put into this file.
2869 @cindex adapt file group parameter
2870 Elements that look like @code{(adapt-file . "file")} will make
2871 @file{file} into the current adaptive file for the group in question.
2872 All adaptive score entries will be put into this file.
2875 @cindex admin-address
2876 When unsubscribing from a mailing list you should never send the
2877 unsubscription notice to the mailing list itself. Instead, you'd send
2878 messages to the administrative address. This parameter allows you to
2879 put the admin address somewhere convenient.
2883 Elements that look like @code{(display . MODE)} say which articles to
2884 display on entering the group. Valid values are:
2888 Display all articles, both read and unread.
2891 Display the last @var{integer} articles in the group. This is the same as
2892 entering the group with @kbd{C-u @var{integer}}.
2895 Display the default visible articles, which normally includes unread and
2899 Display articles that satisfy a predicate.
2901 Here are some examples:
2905 Display only unread articles.
2908 Display everything except expirable articles.
2910 @item [and (not reply) (not expire)]
2911 Display everything except expirable and articles you've already
2915 The available operators are @code{not}, @code{and} and @code{or}.
2916 Predicates include @code{tick}, @code{unsend}, @code{undownload},
2917 @code{unread}, @code{dormant}, @code{expire}, @code{reply},
2918 @code{killed}, @code{bookmark}, @code{score}, @code{save},
2919 @code{cache}, @code{forward}, @code{unseen} and @code{recent}.
2923 The @code{display} parameter works by limiting the summary buffer to
2924 the subset specified. You can pop the limit by using the @kbd{/ w}
2925 command (@pxref{Limiting}).
2929 Elements that look like @code{(comment . "This is a comment")} are
2930 arbitrary comments on the group. You can display comments in the
2931 group line (@pxref{Group Line Specification}).
2935 Elements that look like @code{(charset . iso-8859-1)} will make
2936 @code{iso-8859-1} the default charset; that is, the charset that will be
2937 used for all articles that do not specify a charset.
2939 See also @code{gnus-group-charset-alist}.
2941 @item ignored-charsets
2942 @cindex ignored-charset
2943 Elements that look like @code{(ignored-charsets x-unknown iso-8859-1)}
2944 will make @code{iso-8859-1} and @code{x-unknown} ignored; that is, the
2945 default charset will be used for decoding articles.
2947 See also @code{gnus-group-ignored-charsets-alist}.
2950 @cindex posting-style
2951 You can store additional posting style information for this group
2952 here (@pxref{Posting Styles}). The format is that of an entry in the
2953 @code{gnus-posting-styles} alist, except that there's no regexp matching
2954 the group name (of course). Style elements in this group parameter will
2955 take precedence over the ones found in @code{gnus-posting-styles}.
2957 For instance, if you want a funky name and signature in this group only,
2958 instead of hacking @code{gnus-posting-styles}, you could put something
2959 like this in the group parameters:
2964 ("X-My-Header" "Funky Value")
2965 (signature "Funky Signature"))
2970 If it is set, the value is used as the method for posting message
2971 instead of @code{gnus-post-method}.
2975 An item like @code{(banner . @var{regexp})} causes any part of an article
2976 that matches the regular expression @var{regexp} to be stripped. Instead of
2977 @var{regexp}, you can also use the symbol @code{signature} which strips the
2978 last signature or any of the elements of the alist
2979 @code{gnus-article-banner-alist}.
2983 This parameter contains a Sieve test that should match incoming mail
2984 that should be placed in this group. From this group parameter, a
2985 Sieve @samp{IF} control structure is generated, having the test as the
2986 condition and @samp{fileinto "group.name";} as the body.
2988 For example, if the @samp{INBOX.list.sieve} group has the @code{(sieve
2989 address "sender" "sieve-admin@@extundo.com")} group parameter, when
2990 translating the group parameter into a Sieve script (@pxref{Sieve
2991 Commands}) the following Sieve code is generated:
2994 if address "sender" "sieve-admin@@extundo.com" @{
2995 fileinto "INBOX.list.sieve";
2999 To generate tests for multiple email-addresses use a group parameter
3000 like @code{(sieve address "sender" ("name@@one.org" else@@two.org"))}.
3001 When generating a sieve script (@pxref{Sieve Commands}) Sieve code
3002 like the following is generated:
3005 if address "sender" ["name@@one.org", "else@@two.org"] @{
3006 fileinto "INBOX.list.sieve";
3010 See @pxref{Sieve Commands} for commands and variables that might be of
3011 interest in relation to the sieve parameter.
3013 The Sieve language is described in RFC 3028. @xref{Top, Emacs Sieve,
3014 Top, sieve, Emacs Sieve}.
3016 @item (agent parameters)
3017 If the agent has been enabled, you can set any of the its parameters
3018 to control the behavior of the agent in individual groups. See Agent
3019 Parameters in @ref{Category Syntax}. Most users will choose to set
3020 agent parameters in either an agent category or group topic to
3021 minimize the configuration effort.
3023 @item (@var{variable} @var{form})
3024 You can use the group parameters to set variables local to the group you
3025 are entering. If you want to turn threading off in @samp{news.answers},
3026 you could put @code{(gnus-show-threads nil)} in the group parameters of
3027 that group. @code{gnus-show-threads} will be made into a local variable
3028 in the summary buffer you enter, and the form @code{nil} will be
3029 @code{eval}ed there.
3031 Note that this feature sets the variable locally to the summary buffer.
3032 But some variables are evaluated in the article buffer, or in the
3033 message buffer (of a reply or followup or otherwise newly created
3034 message). As a workaround, it might help to add the variable in
3035 question to @code{gnus-newsgroup-variables}. @xref{Various Summary
3036 Stuff}. So if you want to set @code{message-from-style} via the group
3037 parameters, then you may need the following statement elsewhere in your
3038 @file{~/.gnus} file:
3041 (add-to-list 'gnus-newsgroup-variables 'message-from-style)
3044 @vindex gnus-list-identifiers
3045 A use for this feature is to remove a mailing list identifier tag in
3046 the subject fields of articles. E.g. if the news group
3049 nntp+news.gnus.org:gmane.text.docbook.apps
3052 has the tag @samp{DOC-BOOK-APPS:} in the subject of all articles, this
3053 tag can be removed from the article subjects in the summary buffer for
3054 the group by putting @code{(gnus-list-identifiers "DOCBOOK-APPS:")}
3055 into the group parameters for the group.
3057 This can also be used as a group-specific hook function. If you want to
3058 hear a beep when you enter a group, you could put something like
3059 @code{(dummy-variable (ding))} in the parameters of that group.
3060 @code{dummy-variable} will be set to the (meaningless) result of the
3063 Alternatively, since the VARIABLE becomes local to the group, this
3064 pattern can be used to temporarily change a hook. For example, if the
3065 following is added to a group parameter
3068 (gnus-summary-prepared-hook
3069 '(lambda nil (local-set-key "d" (local-key-binding "n"))))
3072 when the group is entered, the 'd' key will not mark the article as
3077 Use the @kbd{G p} or the @kbd{G c} command to edit group parameters of a
3078 group. (@kbd{G p} presents you with a Lisp-based interface, @kbd{G c}
3079 presents you with a Customize-like interface. The latter helps avoid
3080 silly Lisp errors.) You might also be interested in reading about topic
3081 parameters (@pxref{Topic Parameters}).
3083 @vindex gnus-parameters
3084 Group parameters can be set via the @code{gnus-parameters} variable too.
3085 But some variables, such as @code{visible}, have no effect (For this
3086 case see @code{gnus-permanently-visible-groups} as an alternative.).
3090 (setq gnus-parameters
3092 (gnus-show-threads nil)
3093 (gnus-use-scoring nil)
3094 (gnus-summary-line-format
3095 "%U%R%z%I%(%[%d:%ub%-23,23f%]%) %s\n")
3099 ("^nnimap:\\(foo.bar\\)$"
3103 (gnus-use-scoring t))
3107 (broken-reply-to . t))))
3110 String value of parameters will be subjected to regexp substitution, as
3111 the @code{to-group} example shows.
3113 @vindex gnus-parameters-case-fold-search
3114 By default, whether comparing the group name and one of those regexps
3115 specified in @code{gnus-parameters} is done in a case-sensitive manner
3116 or a case-insensitive manner depends on the value of
3117 @code{case-fold-search} at the time when the comparison is done. The
3118 value of @code{case-fold-search} is typically @code{t}; it means, for
3119 example, the element @code{("INBOX\\.FOO" (total-expire . t))} might be
3120 applied to both the @samp{INBOX.FOO} group and the @samp{INBOX.foo}
3121 group. If you want to make those regexps always case-sensitive, set the
3122 value of the @code{gnus-parameters-case-fold-search} variable to
3123 @code{nil}. Otherwise, set it to @code{t} if you want to compare them
3124 always in a case-insensitive manner.
3126 You can define different sorting to different groups via
3127 @code{gnus-parameters}. Here is an example to sort an @acronym{NNTP}
3128 group by reverse date to see the latest news at the top and an
3129 @acronym{RSS} group by subject. In this example, the first group is the
3130 Debian daily news group @code{gmane.linux.debian.user.news} from
3131 news.gmane.org. The @acronym{RSS} group corresponds to the Debian
3132 weekly news RSS feed
3133 @url{http://packages.debian.org/unstable/newpkg_main.en.rdf},
3139 '(("nntp.*gmane\\.debian\\.user\\.news"
3140 (gnus-show-threads nil)
3141 (gnus-article-sort-functions '((not gnus-article-sort-by-date)))
3142 (gnus-use-adaptive-scoring nil)
3143 (gnus-use-scoring nil))
3145 (gnus-show-threads nil)
3146 (gnus-article-sort-functions 'gnus-article-sort-by-subject)
3147 (gnus-use-adaptive-scoring nil)
3148 (gnus-use-scoring t)
3149 (gnus-score-find-score-files-function 'gnus-score-find-single)
3150 (gnus-summary-line-format "%U%R%z%d %I%(%[ %s %]%)\n"))))
3154 @node Listing Groups
3155 @section Listing Groups
3156 @cindex group listing
3158 These commands all list various slices of the groups available.
3166 @findex gnus-group-list-groups
3167 List all groups that have unread articles
3168 (@code{gnus-group-list-groups}). If the numeric prefix is used, this
3169 command will list only groups of level ARG and lower. By default, it
3170 only lists groups of level five (i.e.,
3171 @code{gnus-group-default-list-level}) or lower (i.e., just subscribed
3178 @findex gnus-group-list-all-groups
3179 List all groups, whether they have unread articles or not
3180 (@code{gnus-group-list-all-groups}). If the numeric prefix is used,
3181 this command will list only groups of level ARG and lower. By default,
3182 it lists groups of level seven or lower (i.e., just subscribed and
3183 unsubscribed groups).
3187 @findex gnus-group-list-level
3188 List all unread groups on a specific level
3189 (@code{gnus-group-list-level}). If given a prefix, also list the groups
3190 with no unread articles.
3194 @findex gnus-group-list-killed
3195 List all killed groups (@code{gnus-group-list-killed}). If given a
3196 prefix argument, really list all groups that are available, but aren't
3197 currently (un)subscribed. This could entail reading the active file
3202 @findex gnus-group-list-zombies
3203 List all zombie groups (@code{gnus-group-list-zombies}).
3207 @findex gnus-group-list-matching
3208 List all unread, subscribed groups with names that match a regexp
3209 (@code{gnus-group-list-matching}).
3213 @findex gnus-group-list-all-matching
3214 List groups that match a regexp (@code{gnus-group-list-all-matching}).
3218 @findex gnus-group-list-active
3219 List absolutely all groups in the active file(s) of the
3220 server(s) you are connected to (@code{gnus-group-list-active}). This
3221 might very well take quite a while. It might actually be a better idea
3222 to do a @kbd{A M} to list all matching, and just give @samp{.} as the
3223 thing to match on. Also note that this command may list groups that
3224 don't exist (yet)---these will be listed as if they were killed groups.
3225 Take the output with some grains of salt.
3229 @findex gnus-group-apropos
3230 List all groups that have names that match a regexp
3231 (@code{gnus-group-apropos}).
3235 @findex gnus-group-description-apropos
3236 List all groups that have names or descriptions that match a regexp
3237 (@code{gnus-group-description-apropos}).
3241 @findex gnus-group-list-cached
3242 List all groups with cached articles (@code{gnus-group-list-cached}).
3246 @findex gnus-group-list-dormant
3247 List all groups with dormant articles (@code{gnus-group-list-dormant}).
3251 @findex gnus-group-list-limit
3252 List groups limited within the current selection
3253 (@code{gnus-group-list-limit}).
3257 @findex gnus-group-list-flush
3258 Flush groups from the current selection (@code{gnus-group-list-flush}).
3262 @findex gnus-group-list-plus
3263 List groups plus the current selection (@code{gnus-group-list-plus}).
3267 @vindex gnus-permanently-visible-groups
3268 @cindex visible group parameter
3269 Groups that match the @code{gnus-permanently-visible-groups} regexp will
3270 always be shown, whether they have unread articles or not. You can also
3271 add the @code{visible} element to the group parameters in question to
3272 get the same effect.
3274 @vindex gnus-list-groups-with-ticked-articles
3275 Groups that have just ticked articles in it are normally listed in the
3276 group buffer. If @code{gnus-list-groups-with-ticked-articles} is
3277 @code{nil}, these groups will be treated just like totally empty
3278 groups. It is @code{t} by default.
3281 @node Sorting Groups
3282 @section Sorting Groups
3283 @cindex sorting groups
3285 @kindex C-c C-s (Group)
3286 @findex gnus-group-sort-groups
3287 @vindex gnus-group-sort-function
3288 The @kbd{C-c C-s} (@code{gnus-group-sort-groups}) command sorts the
3289 group buffer according to the function(s) given by the
3290 @code{gnus-group-sort-function} variable. Available sorting functions
3295 @item gnus-group-sort-by-alphabet
3296 @findex gnus-group-sort-by-alphabet
3297 Sort the group names alphabetically. This is the default.
3299 @item gnus-group-sort-by-real-name
3300 @findex gnus-group-sort-by-real-name
3301 Sort the group alphabetically on the real (unprefixed) group names.
3303 @item gnus-group-sort-by-level
3304 @findex gnus-group-sort-by-level
3305 Sort by group level.
3307 @item gnus-group-sort-by-score
3308 @findex gnus-group-sort-by-score
3309 Sort by group score. @xref{Group Score}.
3311 @item gnus-group-sort-by-rank
3312 @findex gnus-group-sort-by-rank
3313 Sort by group score and then the group level. The level and the score
3314 are, when taken together, the group's @dfn{rank}. @xref{Group Score}.
3316 @item gnus-group-sort-by-unread
3317 @findex gnus-group-sort-by-unread
3318 Sort by number of unread articles.
3320 @item gnus-group-sort-by-method
3321 @findex gnus-group-sort-by-method
3322 Sort alphabetically on the select method.
3324 @item gnus-group-sort-by-server
3325 @findex gnus-group-sort-by-server
3326 Sort alphabetically on the Gnus server name.
3331 @code{gnus-group-sort-function} can also be a list of sorting
3332 functions. In that case, the most significant sort key function must be
3336 There are also a number of commands for sorting directly according to
3337 some sorting criteria:
3341 @kindex G S a (Group)
3342 @findex gnus-group-sort-groups-by-alphabet
3343 Sort the group buffer alphabetically by group name
3344 (@code{gnus-group-sort-groups-by-alphabet}).
3347 @kindex G S u (Group)
3348 @findex gnus-group-sort-groups-by-unread
3349 Sort the group buffer by the number of unread articles
3350 (@code{gnus-group-sort-groups-by-unread}).
3353 @kindex G S l (Group)
3354 @findex gnus-group-sort-groups-by-level
3355 Sort the group buffer by group level
3356 (@code{gnus-group-sort-groups-by-level}).
3359 @kindex G S v (Group)
3360 @findex gnus-group-sort-groups-by-score
3361 Sort the group buffer by group score
3362 (@code{gnus-group-sort-groups-by-score}). @xref{Group Score}.
3365 @kindex G S r (Group)
3366 @findex gnus-group-sort-groups-by-rank
3367 Sort the group buffer by group rank
3368 (@code{gnus-group-sort-groups-by-rank}). @xref{Group Score}.
3371 @kindex G S m (Group)
3372 @findex gnus-group-sort-groups-by-method
3373 Sort the group buffer alphabetically by back end name@*
3374 (@code{gnus-group-sort-groups-by-method}).
3377 @kindex G S n (Group)
3378 @findex gnus-group-sort-groups-by-real-name
3379 Sort the group buffer alphabetically by real (unprefixed) group name
3380 (@code{gnus-group-sort-groups-by-real-name}).
3384 All the commands below obey the process/prefix convention
3385 (@pxref{Process/Prefix}).
3387 When given a symbolic prefix (@pxref{Symbolic Prefixes}), all these
3388 commands will sort in reverse order.
3390 You can also sort a subset of the groups:
3394 @kindex G P a (Group)
3395 @findex gnus-group-sort-selected-groups-by-alphabet
3396 Sort the groups alphabetically by group name
3397 (@code{gnus-group-sort-selected-groups-by-alphabet}).
3400 @kindex G P u (Group)
3401 @findex gnus-group-sort-selected-groups-by-unread
3402 Sort the groups by the number of unread articles
3403 (@code{gnus-group-sort-selected-groups-by-unread}).
3406 @kindex G P l (Group)
3407 @findex gnus-group-sort-selected-groups-by-level
3408 Sort the groups by group level
3409 (@code{gnus-group-sort-selected-groups-by-level}).
3412 @kindex G P v (Group)
3413 @findex gnus-group-sort-selected-groups-by-score
3414 Sort the groups by group score
3415 (@code{gnus-group-sort-selected-groups-by-score}). @xref{Group Score}.
3418 @kindex G P r (Group)
3419 @findex gnus-group-sort-selected-groups-by-rank
3420 Sort the groups by group rank
3421 (@code{gnus-group-sort-selected-groups-by-rank}). @xref{Group Score}.
3424 @kindex G P m (Group)
3425 @findex gnus-group-sort-selected-groups-by-method
3426 Sort the groups alphabetically by back end name@*
3427 (@code{gnus-group-sort-selected-groups-by-method}).
3430 @kindex G P n (Group)
3431 @findex gnus-group-sort-selected-groups-by-real-name
3432 Sort the groups alphabetically by real (unprefixed) group name
3433 (@code{gnus-group-sort-selected-groups-by-real-name}).
3436 @kindex G P s (Group)
3437 @findex gnus-group-sort-selected-groups
3438 Sort the groups according to @code{gnus-group-sort-function}.
3442 And finally, note that you can use @kbd{C-k} and @kbd{C-y} to manually
3446 @node Group Maintenance
3447 @section Group Maintenance
3448 @cindex bogus groups
3453 @findex gnus-group-check-bogus-groups
3454 Find bogus groups and delete them
3455 (@code{gnus-group-check-bogus-groups}).
3459 @findex gnus-group-find-new-groups
3460 Find new groups and process them (@code{gnus-group-find-new-groups}).
3461 With 1 @kbd{C-u}, use the @code{ask-server} method to query the server
3462 for new groups. With 2 @kbd{C-u}'s, use most complete method possible
3463 to query the server for new groups, and subscribe the new groups as
3467 @kindex C-c C-x (Group)
3468 @findex gnus-group-expire-articles
3469 Run all expirable articles in the current group through the expiry
3470 process (if any) (@code{gnus-group-expire-articles}). That is, delete
3471 all expirable articles in the group that have been around for a while.
3472 (@pxref{Expiring Mail}).
3475 @kindex C-c C-M-x (Group)
3476 @findex gnus-group-expire-all-groups
3477 Run all expirable articles in all groups through the expiry process
3478 (@code{gnus-group-expire-all-groups}).
3483 @node Browse Foreign Server
3484 @section Browse Foreign Server
3485 @cindex foreign servers
3486 @cindex browsing servers
3491 @findex gnus-group-browse-foreign-server
3492 You will be queried for a select method and a server name. Gnus will
3493 then attempt to contact this server and let you browse the groups there
3494 (@code{gnus-group-browse-foreign-server}).
3497 @findex gnus-browse-mode
3498 A new buffer with a list of available groups will appear. This buffer
3499 will use the @code{gnus-browse-mode}. This buffer looks a bit (well,
3500 a lot) like a normal group buffer.
3502 Here's a list of keystrokes available in the browse mode:
3507 @findex gnus-group-next-group
3508 Go to the next group (@code{gnus-group-next-group}).
3512 @findex gnus-group-prev-group
3513 Go to the previous group (@code{gnus-group-prev-group}).
3516 @kindex SPACE (Browse)
3517 @findex gnus-browse-read-group
3518 Enter the current group and display the first article
3519 (@code{gnus-browse-read-group}).
3522 @kindex RET (Browse)
3523 @findex gnus-browse-select-group
3524 Enter the current group (@code{gnus-browse-select-group}).
3528 @findex gnus-browse-unsubscribe-current-group
3529 Unsubscribe to the current group, or, as will be the case here,
3530 subscribe to it (@code{gnus-browse-unsubscribe-current-group}).
3536 @findex gnus-browse-exit
3537 Exit browse mode (@code{gnus-browse-exit}).
3541 @findex gnus-browse-describe-group
3542 Describe the current group (@code{gnus-browse-describe-group}).
3546 @findex gnus-browse-describe-briefly
3547 Describe browse mode briefly (well, there's not much to describe, is
3548 there) (@code{gnus-browse-describe-briefly}).
3553 @section Exiting Gnus
3554 @cindex exiting Gnus
3556 Yes, Gnus is ex(c)iting.
3561 @findex gnus-group-suspend
3562 Suspend Gnus (@code{gnus-group-suspend}). This doesn't really exit Gnus,
3563 but it kills all buffers except the Group buffer. I'm not sure why this
3564 is a gain, but then who am I to judge?
3568 @findex gnus-group-exit
3569 @c @icon{gnus-group-exit}
3570 Quit Gnus (@code{gnus-group-exit}).
3574 @findex gnus-group-quit
3575 Quit Gnus without saving the @file{.newsrc} files (@code{gnus-group-quit}).
3576 The dribble file will be saved, though (@pxref{Auto Save}).
3579 @vindex gnus-exit-gnus-hook
3580 @vindex gnus-suspend-gnus-hook
3581 @vindex gnus-after-exiting-gnus-hook
3582 @code{gnus-suspend-gnus-hook} is called when you suspend Gnus and
3583 @code{gnus-exit-gnus-hook} is called when you quit Gnus, while
3584 @code{gnus-after-exiting-gnus-hook} is called as the final item when
3590 Miss Lisa Cannifax, while sitting in English class, felt her feet go
3591 numbly heavy and herself fall into a hazy trance as the boy sitting
3592 behind her drew repeated lines with his pencil across the back of her
3598 @section Group Topics
3601 If you read lots and lots of groups, it might be convenient to group
3602 them hierarchically according to topics. You put your Emacs groups over
3603 here, your sex groups over there, and the rest (what, two groups or so?)
3604 you put in some misc section that you never bother with anyway. You can
3605 even group the Emacs sex groups as a sub-topic to either the Emacs
3606 groups or the sex groups---or both! Go wild!
3610 \gnusfigure{Group Topics}{400}{
3611 \put(75,50){\epsfig{figure=ps/group-topic,height=9cm}}
3622 2: alt.religion.emacs
3625 0: comp.talk.emacs.recovery
3627 8: comp.binaries.fractals
3628 13: comp.sources.unix
3631 @findex gnus-topic-mode
3633 To get this @emph{fab} functionality you simply turn on (ooh!) the
3634 @code{gnus-topic} minor mode---type @kbd{t} in the group buffer. (This
3635 is a toggling command.)
3637 Go ahead, just try it. I'll still be here when you get back. La de
3638 dum@dots{} Nice tune, that@dots{} la la la@dots{} What, you're back?
3639 Yes, and now press @kbd{l}. There. All your groups are now listed
3640 under @samp{misc}. Doesn't that make you feel all warm and fuzzy?
3643 If you want this permanently enabled, you should add that minor mode to
3644 the hook for the group mode. Put the following line in your
3645 @file{~/.gnus.el} file:
3648 (add-hook 'gnus-group-mode-hook 'gnus-topic-mode)
3652 * Topic Commands:: Interactive E-Z commands.
3653 * Topic Variables:: How to customize the topics the Lisp Way.
3654 * Topic Sorting:: Sorting each topic individually.
3655 * Topic Topology:: A map of the world.
3656 * Topic Parameters:: Parameters that apply to all groups in a topic.
3660 @node Topic Commands
3661 @subsection Topic Commands
3662 @cindex topic commands
3664 When the topic minor mode is turned on, a new @kbd{T} submap will be
3665 available. In addition, a few of the standard keys change their
3666 definitions slightly.
3668 In general, the following kinds of operations are possible on topics.
3669 First of all, you want to create topics. Secondly, you want to put
3670 groups in topics and to move them around until you have an order you
3671 like. The third kind of operation is to show/hide parts of the whole
3672 shebang. You might want to hide a topic including its subtopics and
3673 groups, to get a better overview of the other groups.
3675 Here is a list of the basic keys that you might need to set up topics
3682 @findex gnus-topic-create-topic
3683 Prompt for a new topic name and create it
3684 (@code{gnus-topic-create-topic}).
3688 @kindex T TAB (Topic)
3690 @findex gnus-topic-indent
3691 ``Indent'' the current topic so that it becomes a sub-topic of the
3692 previous topic (@code{gnus-topic-indent}). If given a prefix,
3693 ``un-indent'' the topic instead.
3696 @kindex M-TAB (Topic)
3697 @findex gnus-topic-unindent
3698 ``Un-indent'' the current topic so that it becomes a sub-topic of the
3699 parent of its current parent (@code{gnus-topic-unindent}).
3703 The following two keys can be used to move groups and topics around.
3704 They work like the well-known cut and paste. @kbd{C-k} is like cut and
3705 @kbd{C-y} is like paste. Of course, this being Emacs, we use the terms
3706 kill and yank rather than cut and paste.
3712 @findex gnus-topic-kill-group
3713 Kill a group or topic (@code{gnus-topic-kill-group}). All groups in the
3714 topic will be removed along with the topic.
3718 @findex gnus-topic-yank-group
3719 Yank the previously killed group or topic
3720 (@code{gnus-topic-yank-group}). Note that all topics will be yanked
3723 So, to move a topic to the beginning of the list of topics, just hit
3724 @kbd{C-k} on it. This is like the ``cut'' part of cut and paste. Then,
3725 move the cursor to the beginning of the buffer (just below the ``Gnus''
3726 topic) and hit @kbd{C-y}. This is like the ``paste'' part of cut and
3727 paste. Like I said -- E-Z.
3729 You can use @kbd{C-k} and @kbd{C-y} on groups as well as on topics. So
3730 you can move topics around as well as groups.
3734 After setting up the topics the way you like them, you might wish to
3735 hide a topic, or to show it again. That's why we have the following
3742 @findex gnus-topic-select-group
3744 Either select a group or fold a topic (@code{gnus-topic-select-group}).
3745 When you perform this command on a group, you'll enter the group, as
3746 usual. When done on a topic line, the topic will be folded (if it was
3747 visible) or unfolded (if it was folded already). So it's basically a
3748 toggling command on topics. In addition, if you give a numerical
3749 prefix, group on that level (and lower) will be displayed.
3753 Now for a list of other commands, in no particular order.
3759 @findex gnus-topic-move-group
3760 Move the current group to some other topic
3761 (@code{gnus-topic-move-group}). This command uses the process/prefix
3762 convention (@pxref{Process/Prefix}).
3766 @findex gnus-topic-jump-to-topic
3767 Go to a topic (@code{gnus-topic-jump-to-topic}).
3771 @findex gnus-topic-copy-group
3772 Copy the current group to some other topic
3773 (@code{gnus-topic-copy-group}). This command uses the process/prefix
3774 convention (@pxref{Process/Prefix}).
3778 @findex gnus-topic-hide-topic
3779 Hide the current topic (@code{gnus-topic-hide-topic}). If given
3780 a prefix, hide the topic permanently.
3784 @findex gnus-topic-show-topic
3785 Show the current topic (@code{gnus-topic-show-topic}). If given
3786 a prefix, show the topic permanently.
3790 @findex gnus-topic-remove-group
3791 Remove a group from the current topic (@code{gnus-topic-remove-group}).
3792 This command is mainly useful if you have the same group in several
3793 topics and wish to remove it from one of the topics. You may also
3794 remove a group from all topics, but in that case, Gnus will add it to
3795 the root topic the next time you start Gnus. In fact, all new groups
3796 (which, naturally, don't belong to any topic) will show up in the root
3799 This command uses the process/prefix convention
3800 (@pxref{Process/Prefix}).
3804 @findex gnus-topic-move-matching
3805 Move all groups that match some regular expression to a topic
3806 (@code{gnus-topic-move-matching}).
3810 @findex gnus-topic-copy-matching
3811 Copy all groups that match some regular expression to a topic
3812 (@code{gnus-topic-copy-matching}).
3816 @findex gnus-topic-toggle-display-empty-topics
3817 Toggle hiding empty topics
3818 (@code{gnus-topic-toggle-display-empty-topics}).
3822 @findex gnus-topic-mark-topic
3823 Mark all groups in the current topic with the process mark
3824 (@code{gnus-topic-mark-topic}). This command works recursively on
3825 sub-topics unless given a prefix.
3828 @kindex T M-# (Topic)
3829 @findex gnus-topic-unmark-topic
3830 Remove the process mark from all groups in the current topic
3831 (@code{gnus-topic-unmark-topic}). This command works recursively on
3832 sub-topics unless given a prefix.
3835 @kindex C-c C-x (Topic)
3836 @findex gnus-topic-expire-articles
3837 Run all expirable articles in the current group or topic through the
3838 expiry process (if any)
3839 (@code{gnus-topic-expire-articles}). (@pxref{Expiring Mail}).
3843 @findex gnus-topic-rename
3844 Rename a topic (@code{gnus-topic-rename}).
3847 @kindex T DEL (Topic)
3848 @findex gnus-topic-delete
3849 Delete an empty topic (@code{gnus-topic-delete}).
3853 @findex gnus-topic-list-active
3854 List all groups that Gnus knows about in a topics-ified way
3855 (@code{gnus-topic-list-active}).
3858 @kindex T M-n (Topic)
3859 @findex gnus-topic-goto-next-topic
3860 Go to the next topic (@code{gnus-topic-goto-next-topic}).
3863 @kindex T M-p (Topic)
3864 @findex gnus-topic-goto-previous-topic
3865 Go to the previous topic (@code{gnus-topic-goto-previous-topic}).
3869 @findex gnus-topic-edit-parameters
3870 @cindex group parameters
3871 @cindex topic parameters
3873 Edit the topic parameters (@code{gnus-topic-edit-parameters}).
3874 @xref{Topic Parameters}.
3879 @node Topic Variables
3880 @subsection Topic Variables
3881 @cindex topic variables
3883 The previous section told you how to tell Gnus which topics to display.
3884 This section explains how to tell Gnus what to display about each topic.
3886 @vindex gnus-topic-line-format
3887 The topic lines themselves are created according to the
3888 @code{gnus-topic-line-format} variable (@pxref{Formatting Variables}).
3901 Number of groups in the topic.
3903 Number of unread articles in the topic.
3905 Number of unread articles in the topic and all its subtopics.
3908 @vindex gnus-topic-indent-level
3909 Each sub-topic (and the groups in the sub-topics) will be indented with
3910 @code{gnus-topic-indent-level} times the topic level number of spaces.
3913 @vindex gnus-topic-mode-hook
3914 @code{gnus-topic-mode-hook} is called in topic minor mode buffers.
3916 @vindex gnus-topic-display-empty-topics
3917 The @code{gnus-topic-display-empty-topics} says whether to display even
3918 topics that have no unread articles in them. The default is @code{t}.
3922 @subsection Topic Sorting
3923 @cindex topic sorting
3925 You can sort the groups in each topic individually with the following
3931 @kindex T S a (Topic)
3932 @findex gnus-topic-sort-groups-by-alphabet
3933 Sort the current topic alphabetically by group name
3934 (@code{gnus-topic-sort-groups-by-alphabet}).
3937 @kindex T S u (Topic)
3938 @findex gnus-topic-sort-groups-by-unread
3939 Sort the current topic by the number of unread articles
3940 (@code{gnus-topic-sort-groups-by-unread}).
3943 @kindex T S l (Topic)
3944 @findex gnus-topic-sort-groups-by-level
3945 Sort the current topic by group level
3946 (@code{gnus-topic-sort-groups-by-level}).
3949 @kindex T S v (Topic)
3950 @findex gnus-topic-sort-groups-by-score
3951 Sort the current topic by group score
3952 (@code{gnus-topic-sort-groups-by-score}). @xref{Group Score}.
3955 @kindex T S r (Topic)
3956 @findex gnus-topic-sort-groups-by-rank
3957 Sort the current topic by group rank
3958 (@code{gnus-topic-sort-groups-by-rank}). @xref{Group Score}.
3961 @kindex T S m (Topic)
3962 @findex gnus-topic-sort-groups-by-method
3963 Sort the current topic alphabetically by back end name
3964 (@code{gnus-topic-sort-groups-by-method}).
3967 @kindex T S e (Topic)
3968 @findex gnus-topic-sort-groups-by-server
3969 Sort the current topic alphabetically by server name
3970 (@code{gnus-topic-sort-groups-by-server}).
3973 @kindex T S s (Topic)
3974 @findex gnus-topic-sort-groups
3975 Sort the current topic according to the function(s) given by the
3976 @code{gnus-group-sort-function} variable
3977 (@code{gnus-topic-sort-groups}).
3981 When given a prefix argument, all these commands will sort in reverse
3982 order. @xref{Sorting Groups}, for more information about group
3986 @node Topic Topology
3987 @subsection Topic Topology
3988 @cindex topic topology
3991 So, let's have a look at an example group buffer:
3998 2: alt.religion.emacs
4001 0: comp.talk.emacs.recovery
4003 8: comp.binaries.fractals
4004 13: comp.sources.unix
4008 So, here we have one top-level topic (@samp{Gnus}), two topics under
4009 that, and one sub-topic under one of the sub-topics. (There is always
4010 just one (1) top-level topic). This topology can be expressed as
4015 (("Emacs -- I wuw it!" visible)
4016 (("Naughty Emacs" visible)))
4020 @vindex gnus-topic-topology
4021 This is in fact how the variable @code{gnus-topic-topology} would look
4022 for the display above. That variable is saved in the @file{.newsrc.eld}
4023 file, and shouldn't be messed with manually---unless you really want
4024 to. Since this variable is read from the @file{.newsrc.eld} file,
4025 setting it in any other startup files will have no effect.
4027 This topology shows what topics are sub-topics of what topics (right),
4028 and which topics are visible. Two settings are currently
4029 allowed---@code{visible} and @code{invisible}.
4032 @node Topic Parameters
4033 @subsection Topic Parameters
4034 @cindex topic parameters
4036 All groups in a topic will inherit group parameters from the parent
4037 (and ancestor) topic parameters. All valid group parameters are valid
4038 topic parameters (@pxref{Group Parameters}). When the agent is
4039 enabled, all agent parameters (See Agent Parameters in @ref{Category
4040 Syntax}) are also valid topic parameters.
4042 In addition, the following parameters are only valid as topic
4047 When subscribing new groups by topic (@pxref{Subscription Methods}), the
4048 @code{subscribe} topic parameter says what groups go in what topic. Its
4049 value should be a regexp to match the groups that should go in that
4052 @item subscribe-level
4053 When subscribing new groups by topic (see the @code{subscribe} parameter),
4054 the group will be subscribed with the level specified in the
4055 @code{subscribe-level} instead of @code{gnus-level-default-subscribed}.
4059 Group parameters (of course) override topic parameters, and topic
4060 parameters in sub-topics override topic parameters in super-topics. You
4061 know. Normal inheritance rules. (@dfn{Rules} is here a noun, not a
4062 verb, although you may feel free to disagree with me here.)
4069 2: alt.religion.emacs
4073 0: comp.talk.emacs.recovery
4075 8: comp.binaries.fractals
4076 13: comp.sources.unix
4081 The @samp{Emacs} topic has the topic parameter @code{(score-file
4082 . "emacs.SCORE")}; the @samp{Relief} topic has the topic parameter
4083 @code{(score-file . "relief.SCORE")}; and the @samp{Misc} topic has the
4084 topic parameter @code{(score-file . "emacs.SCORE")}. In addition,
4085 @* @samp{alt.religion.emacs} has the group parameter @code{(score-file
4086 . "religion.SCORE")}.
4088 Now, when you enter @samp{alt.sex.emacs} in the @samp{Relief} topic, you
4089 will get the @file{relief.SCORE} home score file. If you enter the same
4090 group in the @samp{Emacs} topic, you'll get the @file{emacs.SCORE} home
4091 score file. If you enter the group @samp{alt.religion.emacs}, you'll
4092 get the @file{religion.SCORE} home score file.
4094 This seems rather simple and self-evident, doesn't it? Well, yes. But
4095 there are some problems, especially with the @code{total-expiry}
4096 parameter. Say you have a mail group in two topics; one with
4097 @code{total-expiry} and one without. What happens when you do @kbd{M-x
4098 gnus-expire-all-expirable-groups}? Gnus has no way of telling which one
4099 of these topics you mean to expire articles from, so anything may
4100 happen. In fact, I hereby declare that it is @dfn{undefined} what
4101 happens. You just have to be careful if you do stuff like that.
4104 @node Misc Group Stuff
4105 @section Misc Group Stuff
4108 * Scanning New Messages:: Asking Gnus to see whether new messages have arrived.
4109 * Group Information:: Information and help on groups and Gnus.
4110 * Group Timestamp:: Making Gnus keep track of when you last read a group.
4111 * File Commands:: Reading and writing the Gnus files.
4112 * Sieve Commands:: Managing Sieve scripts.
4119 @cindex keys, reserved for users (Group)
4120 The key @kbd{v} is reserved for users. You can bind it key to some
4121 function or better use it as a prefix key. For example:
4124 (define-key gnus-group-mode-map (kbd "v j d")
4127 (gnus-group-jump-to-group "nndraft:drafts")))
4130 On keys reserved for users in Emacs and on keybindings in general
4131 @xref{Keymaps, Keymaps, , emacs, The Emacs Editor}.
4135 @findex gnus-group-enter-server-mode
4136 Enter the server buffer (@code{gnus-group-enter-server-mode}).
4137 @xref{Server Buffer}.
4141 @findex gnus-group-post-news
4142 Start composing a message (a news by default)
4143 (@code{gnus-group-post-news}). If given a prefix, post to the group
4144 under the point. If the prefix is 1, prompt for a group to post to.
4145 Contrary to what the name of this function suggests, the prepared
4146 article might be a mail instead of a news, if a mail group is specified
4147 with the prefix argument. @xref{Composing Messages}.
4151 @findex gnus-group-mail
4152 Mail a message somewhere (@code{gnus-group-mail}). If given a prefix,
4153 use the posting style of the group under the point. If the prefix is 1,
4154 prompt for a group name to find the posting style.
4155 @xref{Composing Messages}.
4159 @findex gnus-group-news
4160 Start composing a news (@code{gnus-group-news}). If given a prefix,
4161 post to the group under the point. If the prefix is 1, prompt
4162 for group to post to. @xref{Composing Messages}.
4164 This function actually prepares a news even when using mail groups.
4165 This is useful for ``posting'' messages to mail groups without actually
4166 sending them over the network: they're just saved directly to the group
4167 in question. The corresponding back end must have a request-post method
4168 for this to work though.
4172 Variables for the group buffer:
4176 @item gnus-group-mode-hook
4177 @vindex gnus-group-mode-hook
4178 is called after the group buffer has been
4181 @item gnus-group-prepare-hook
4182 @vindex gnus-group-prepare-hook
4183 is called after the group buffer is
4184 generated. It may be used to modify the buffer in some strange,
4187 @item gnus-group-prepared-hook
4188 @vindex gnus-group-prepare-hook
4189 is called as the very last thing after the group buffer has been
4190 generated. It may be used to move point around, for instance.
4192 @item gnus-permanently-visible-groups
4193 @vindex gnus-permanently-visible-groups
4194 Groups matching this regexp will always be listed in the group buffer,
4195 whether they are empty or not.
4197 @item gnus-group-name-charset-method-alist
4198 @vindex gnus-group-name-charset-method-alist
4199 An alist of method and the charset for group names. It is used to show
4200 non-@acronym{ASCII} group names.
4204 (setq gnus-group-name-charset-method-alist
4205 '(((nntp "news.com.cn") . cn-gb-2312)))
4208 @item gnus-group-name-charset-group-alist
4209 @cindex UTF-8 group names
4210 @vindex gnus-group-name-charset-group-alist
4211 An alist of regexp of group name and the charset for group names. It
4212 is used to show non-@acronym{ASCII} group names. @code{((".*"
4213 utf-8))} is the default value if UTF-8 is supported, otherwise the
4214 default is @code{nil}.
4218 (setq gnus-group-name-charset-group-alist
4219 '(("\\.com\\.cn:" . cn-gb-2312)))
4224 @node Scanning New Messages
4225 @subsection Scanning New Messages
4226 @cindex new messages
4227 @cindex scanning new news
4233 @findex gnus-group-get-new-news
4234 @c @icon{gnus-group-get-new-news}
4235 Check the server(s) for new articles. If the numerical prefix is used,
4236 this command will check only groups of level @var{arg} and lower
4237 (@code{gnus-group-get-new-news}). If given a non-numerical prefix, this
4238 command will force a total re-reading of the active file(s) from the
4243 @findex gnus-group-get-new-news-this-group
4244 @vindex gnus-goto-next-group-when-activating
4245 @c @icon{gnus-group-get-new-news-this-group}
4246 Check whether new articles have arrived in the current group
4247 (@code{gnus-group-get-new-news-this-group}).
4248 @code{gnus-goto-next-group-when-activating} says whether this command is
4249 to move point to the next group or not. It is @code{t} by default.
4251 @findex gnus-activate-all-groups
4252 @cindex activating groups
4254 @kindex C-c M-g (Group)
4255 Activate absolutely all groups (@code{gnus-activate-all-groups}).
4260 @findex gnus-group-restart
4261 Restart Gnus (@code{gnus-group-restart}). This saves the @file{.newsrc}
4262 file(s), closes the connection to all servers, clears up all run-time
4263 Gnus variables, and then starts Gnus all over again.
4267 @vindex gnus-get-new-news-hook
4268 @code{gnus-get-new-news-hook} is run just before checking for new news.
4270 @vindex gnus-after-getting-new-news-hook
4271 @code{gnus-after-getting-new-news-hook} is run after checking for new
4275 @node Group Information
4276 @subsection Group Information
4277 @cindex group information
4278 @cindex information on groups
4285 @findex gnus-group-fetch-faq
4286 @vindex gnus-group-faq-directory
4289 Try to fetch the @acronym{FAQ} for the current group
4290 (@code{gnus-group-fetch-faq}). Gnus will try to get the @acronym{FAQ}
4291 from @code{gnus-group-faq-directory}, which is usually a directory on
4292 a remote machine. This variable can also be a list of directories.
4293 In that case, giving a prefix to this command will allow you to choose
4294 between the various sites. @code{ange-ftp} (or @code{efs}) will be
4295 used for fetching the file.
4297 If fetching from the first site is unsuccessful, Gnus will attempt to go
4298 through @code{gnus-group-faq-directory} and try to open them one by one.
4302 @findex gnus-group-fetch-charter
4303 @vindex gnus-group-charter-alist
4305 Try to open the charter for the current group in a web browser
4306 (@code{gnus-group-fetch-charter}). Query for a group if given a
4309 Gnus will use @code{gnus-group-charter-alist} to find the location of
4310 the charter. If no location is known, Gnus will fetch the control
4311 messages for the group, which in some cases includes the charter.
4315 @findex gnus-group-fetch-control
4316 @vindex gnus-group-fetch-control-use-browse-url
4317 @cindex control message
4318 Fetch the control messages for the group from the archive at
4319 @code{ftp.isc.org} (@code{gnus-group-fetch-control}). Query for a
4320 group if given a prefix argument.
4322 If @code{gnus-group-fetch-control-use-browse-url} is non-@code{nil},
4323 Gnus will open the control messages in a browser using
4324 @code{browse-url}. Otherwise they are fetched using @code{ange-ftp}
4325 and displayed in an ephemeral group.
4327 Note that the control messages are compressed. To use this command
4328 you need to turn on @code{auto-compression-mode} (@pxref{Compressed
4329 Files, ,Compressed Files, emacs, The Emacs Manual}).
4333 @c @icon{gnus-group-describe-group}
4335 @kindex C-c C-d (Group)
4336 @cindex describing groups
4337 @cindex group description
4338 @findex gnus-group-describe-group
4339 Describe the current group (@code{gnus-group-describe-group}). If given
4340 a prefix, force Gnus to re-read the description from the server.
4344 @findex gnus-group-describe-all-groups
4345 Describe all groups (@code{gnus-group-describe-all-groups}). If given a
4346 prefix, force Gnus to re-read the description file from the server.
4353 @findex gnus-version
4354 Display current Gnus version numbers (@code{gnus-version}).
4358 @findex gnus-group-describe-briefly
4359 Give a very short help message (@code{gnus-group-describe-briefly}).
4362 @kindex C-c C-i (Group)
4365 @findex gnus-info-find-node
4366 Go to the Gnus info node (@code{gnus-info-find-node}).
4370 @node Group Timestamp
4371 @subsection Group Timestamp
4373 @cindex group timestamps
4375 It can be convenient to let Gnus keep track of when you last read a
4376 group. To set the ball rolling, you should add
4377 @code{gnus-group-set-timestamp} to @code{gnus-select-group-hook}:
4380 (add-hook 'gnus-select-group-hook 'gnus-group-set-timestamp)
4383 After doing this, each time you enter a group, it'll be recorded.
4385 This information can be displayed in various ways---the easiest is to
4386 use the @samp{%d} spec in the group line format:
4389 (setq gnus-group-line-format
4390 "%M\%S\%p\%P\%5y: %(%-40,40g%) %d\n")
4393 This will result in lines looking like:
4396 * 0: mail.ding 19961002T012943
4397 0: custom 19961002T012713
4400 As you can see, the date is displayed in compact ISO 8601 format. This
4401 may be a bit too much, so to just display the date, you could say
4405 (setq gnus-group-line-format
4406 "%M\%S\%p\%P\%5y: %(%-40,40g%) %6,6~(cut 2)d\n")
4409 If you would like greater control of the time format, you can use a
4410 user-defined format spec. Something like the following should do the
4414 (setq gnus-group-line-format
4415 "%M\%S\%p\%P\%5y: %(%-40,40g%) %ud\n")
4416 (defun gnus-user-format-function-d (headers)
4417 (let ((time (gnus-group-timestamp gnus-tmp-group)))
4419 (format-time-string "%b %d %H:%M" time)
4425 @subsection File Commands
4426 @cindex file commands
4432 @findex gnus-group-read-init-file
4433 @vindex gnus-init-file
4434 @cindex reading init file
4435 Re-read the init file (@code{gnus-init-file}, which defaults to
4436 @file{~/.gnus.el}) (@code{gnus-group-read-init-file}).
4440 @findex gnus-group-save-newsrc
4441 @cindex saving .newsrc
4442 Save the @file{.newsrc.eld} file (and @file{.newsrc} if wanted)
4443 (@code{gnus-group-save-newsrc}). If given a prefix, force saving the
4444 file(s) whether Gnus thinks it is necessary or not.
4447 @c @kindex Z (Group)
4448 @c @findex gnus-group-clear-dribble
4449 @c Clear the dribble buffer (@code{gnus-group-clear-dribble}).
4454 @node Sieve Commands
4455 @subsection Sieve Commands
4456 @cindex group sieve commands
4458 Sieve is a server-side mail filtering language. In Gnus you can use
4459 the @code{sieve} group parameter (@pxref{Group Parameters}) to specify
4460 sieve rules that should apply to each group. Gnus provides two
4461 commands to translate all these group parameters into a proper Sieve
4462 script that can be transfered to the server somehow.
4464 @vindex gnus-sieve-file
4465 @vindex gnus-sieve-region-start
4466 @vindex gnus-sieve-region-end
4467 The generated Sieve script is placed in @code{gnus-sieve-file} (by
4468 default @file{~/.sieve}). The Sieve code that Gnus generate is placed
4469 between two delimiters, @code{gnus-sieve-region-start} and
4470 @code{gnus-sieve-region-end}, so you may write additional Sieve code
4471 outside these delimiters that will not be removed the next time you
4472 regenerate the Sieve script.
4474 @vindex gnus-sieve-crosspost
4475 The variable @code{gnus-sieve-crosspost} controls how the Sieve script
4476 is generated. If it is non-@code{nil} (the default) articles is
4477 placed in all groups that have matching rules, otherwise the article
4478 is only placed in the group with the first matching rule. For
4479 example, the group parameter @samp{(sieve address "sender"
4480 "owner-ding@@hpc.uh.edu")} will generate the following piece of Sieve
4481 code if @code{gnus-sieve-crosspost} is @code{nil}. (When
4482 @code{gnus-sieve-crosspost} is non-@code{nil}, it looks the same
4483 except that the line containing the call to @code{stop} is removed.)
4486 if address "sender" "owner-ding@@hpc.uh.edu" @{
4487 fileinto "INBOX.ding";
4492 @xref{Top, Emacs Sieve, Top, sieve, Emacs Sieve}.
4498 @findex gnus-sieve-generate
4499 @vindex gnus-sieve-file
4500 @cindex generating sieve script
4501 Regenerate a Sieve script from the @code{sieve} group parameters and
4502 put you into the @code{gnus-sieve-file} without saving it.
4506 @findex gnus-sieve-update
4507 @vindex gnus-sieve-file
4508 @cindex updating sieve script
4509 Regenerates the Gnus managed part of @code{gnus-sieve-file} using the
4510 @code{sieve} group parameters, save the file and upload it to the
4511 server using the @code{sieveshell} program.
4516 @node Summary Buffer
4517 @chapter Summary Buffer
4518 @cindex summary buffer
4520 A line for each article is displayed in the summary buffer. You can
4521 move around, read articles, post articles and reply to articles.
4523 The most common way to a summary buffer is to select a group from the
4524 group buffer (@pxref{Selecting a Group}).
4526 You can have as many summary buffers open as you wish.
4529 @cindex keys, reserved for users (Summary)
4530 The key @kbd{v} is reserved for users. You can bind it key to some
4531 function or better use it as a prefix key. For example:
4533 (define-key gnus-summary-mode-map (kbd "v -") "LrS") ;; lower subthread
4537 * Summary Buffer Format:: Deciding how the summary buffer is to look.
4538 * Summary Maneuvering:: Moving around the summary buffer.
4539 * Choosing Articles:: Reading articles.
4540 * Paging the Article:: Scrolling the current article.
4541 * Reply Followup and Post:: Posting articles.
4542 * Delayed Articles:: Send articles at a later time.
4543 * Marking Articles:: Marking articles as read, expirable, etc.
4544 * Limiting:: You can limit the summary buffer.
4545 * Threading:: How threads are made.
4546 * Sorting the Summary Buffer:: How articles and threads are sorted.
4547 * Asynchronous Fetching:: Gnus might be able to pre-fetch articles.
4548 * Article Caching:: You may store articles in a cache.
4549 * Persistent Articles:: Making articles expiry-resistant.
4550 * Article Backlog:: Having already read articles hang around.
4551 * Saving Articles:: Ways of customizing article saving.
4552 * Decoding Articles:: Gnus can treat series of (uu)encoded articles.
4553 * Article Treatment:: The article buffer can be mangled at will.
4554 * MIME Commands:: Doing MIMEy things with the articles.
4555 * Charsets:: Character set issues.
4556 * Article Commands:: Doing various things with the article buffer.
4557 * Summary Sorting:: Sorting the summary buffer in various ways.
4558 * Finding the Parent:: No child support? Get the parent.
4559 * Alternative Approaches:: Reading using non-default summaries.
4560 * Tree Display:: A more visual display of threads.
4561 * Mail Group Commands:: Some commands can only be used in mail groups.
4562 * Various Summary Stuff:: What didn't fit anywhere else.
4563 * Exiting the Summary Buffer:: Returning to the Group buffer,
4564 or reselecting the current group.
4565 * Crosspost Handling:: How crossposted articles are dealt with.
4566 * Duplicate Suppression:: An alternative when crosspost handling fails.
4567 * Security:: Decrypt and Verify.
4568 * Mailing List:: Mailing list minor mode.
4572 @node Summary Buffer Format
4573 @section Summary Buffer Format
4574 @cindex summary buffer format
4578 \gnusfigure{The Summary Buffer}{180}{
4579 \put(0,0){\epsfig{figure=ps/summary,width=7.5cm}}
4580 \put(445,0){\makebox(0,0)[br]{\epsfig{figure=ps/summary-article,width=7.5cm}}}
4586 * Summary Buffer Lines:: You can specify how summary lines should look.
4587 * To From Newsgroups:: How to not display your own name.
4588 * Summary Buffer Mode Line:: You can say how the mode line should look.
4589 * Summary Highlighting:: Making the summary buffer all pretty and nice.
4592 @findex mail-extract-address-components
4593 @findex gnus-extract-address-components
4594 @vindex gnus-extract-address-components
4595 Gnus will use the value of the @code{gnus-extract-address-components}
4596 variable as a function for getting the name and address parts of a
4597 @code{From} header. Two pre-defined functions exist:
4598 @code{gnus-extract-address-components}, which is the default, quite
4599 fast, and too simplistic solution; and
4600 @code{mail-extract-address-components}, which works very nicely, but is
4601 slower. The default function will return the wrong answer in 5% of the
4602 cases. If this is unacceptable to you, use the other function instead:
4605 (setq gnus-extract-address-components
4606 'mail-extract-address-components)
4609 @vindex gnus-summary-same-subject
4610 @code{gnus-summary-same-subject} is a string indicating that the current
4611 article has the same subject as the previous. This string will be used
4612 with those specs that require it. The default is @code{""}.
4615 @node Summary Buffer Lines
4616 @subsection Summary Buffer Lines
4618 @vindex gnus-summary-line-format
4619 You can change the format of the lines in the summary buffer by changing
4620 the @code{gnus-summary-line-format} variable. It works along the same
4621 lines as a normal @code{format} string, with some extensions
4622 (@pxref{Formatting Variables}).
4624 There should always be a colon or a point position marker on the line;
4625 the cursor always moves to the point position marker or the colon after
4626 performing an operation. (Of course, Gnus wouldn't be Gnus if it wasn't
4627 possible to change this. Just write a new function
4628 @code{gnus-goto-colon} which does whatever you like with the cursor.)
4629 @xref{Positioning Point}.
4631 The default string is @samp{%U%R%z%I%(%[%4L: %-23,23f%]%) %s\n}.
4633 The following format specification characters and extended format
4634 specification(s) are understood:
4640 Subject string. List identifiers stripped,
4641 @code{gnus-list-identifies}. @xref{Article Hiding}.
4643 Subject if the article is the root of the thread or the previous article
4644 had a different subject, @code{gnus-summary-same-subject} otherwise.
4645 (@code{gnus-summary-same-subject} defaults to @code{""}.)
4647 Full @code{From} header.
4649 The name (from the @code{From} header).
4651 The name, @code{To} header or the @code{Newsgroups} header (@pxref{To
4654 The name (from the @code{From} header). This differs from the @code{n}
4655 spec in that it uses the function designated by the
4656 @code{gnus-extract-address-components} variable, which is slower, but
4657 may be more thorough.
4659 The address (from the @code{From} header). This works the same way as
4662 Number of lines in the article.
4664 Number of characters in the article. This specifier is not supported
4665 in some methods (like nnfolder).
4667 Pretty-printed version of the number of characters in the article;
4668 for example, @samp{1.2k} or @samp{0.4M}.
4670 Indentation based on thread level (@pxref{Customizing Threading}).
4672 A complex trn-style thread tree, showing response-connecting trace
4673 lines. A thread could be drawn like this:
4686 You can customize the appearance with the following options. Note
4687 that it is possible to make the thread display look really neat by
4688 replacing the default @acronym{ASCII} characters with graphic
4689 line-drawing glyphs.
4691 @item gnus-sum-thread-tree-root
4692 @vindex gnus-sum-thread-tree-root
4693 Used for the root of a thread. If @code{nil}, use subject
4694 instead. The default is @samp{> }.
4696 @item gnus-sum-thread-tree-false-root
4697 @vindex gnus-sum-thread-tree-false-root
4698 Used for the false root of a thread (@pxref{Loose Threads}). If
4699 @code{nil}, use subject instead. The default is @samp{> }.
4701 @item gnus-sum-thread-tree-single-indent
4702 @vindex gnus-sum-thread-tree-single-indent
4703 Used for a thread with just one message. If @code{nil}, use subject
4704 instead. The default is @samp{}.
4706 @item gnus-sum-thread-tree-vertical
4707 @vindex gnus-sum-thread-tree-vertical
4708 Used for drawing a vertical line. The default is @samp{| }.
4710 @item gnus-sum-thread-tree-indent
4711 @vindex gnus-sum-thread-tree-indent
4712 Used for indenting. The default is @samp{ }.
4714 @item gnus-sum-thread-tree-leaf-with-other
4715 @vindex gnus-sum-thread-tree-leaf-with-other
4716 Used for a leaf with brothers. The default is @samp{+-> }.
4718 @item gnus-sum-thread-tree-single-leaf
4719 @vindex gnus-sum-thread-tree-single-leaf
4720 Used for a leaf without brothers. The default is @samp{\-> }
4725 Nothing if the article is a root and lots of spaces if it isn't (it
4726 pushes everything after it off the screen).
4728 Opening bracket, which is normally @samp{[}, but can also be @samp{<}
4729 for adopted articles (@pxref{Customizing Threading}).
4731 Closing bracket, which is normally @samp{]}, but can also be @samp{>}
4732 for adopted articles.
4734 One space for each thread level.
4736 Twenty minus thread level spaces.
4738 Unread. @xref{Read Articles}.
4741 This misleadingly named specifier is the @dfn{secondary mark}. This
4742 mark will say whether the article has been replied to, has been cached,
4743 or has been saved. @xref{Other Marks}.
4746 Score as a number (@pxref{Scoring}).
4748 @vindex gnus-summary-zcore-fuzz
4749 Zcore, @samp{+} if above the default level and @samp{-} if below the
4750 default level. If the difference between
4751 @code{gnus-summary-default-score} and the score is less than
4752 @code{gnus-summary-zcore-fuzz}, this spec will not be used.
4760 The @code{Date} in @code{DD-MMM} format.
4762 The @code{Date} in @var{YYYYMMDD}@code{T}@var{HHMMSS} format.
4768 Number of articles in the current sub-thread. Using this spec will slow
4769 down summary buffer generation somewhat.
4771 An @samp{=} (@code{gnus-not-empty-thread-mark}) will be displayed if the
4772 article has any children.
4778 Desired cursor position (instead of after first colon).
4780 Age sensitive date format. Various date format is defined in
4781 @code{gnus-user-date-format-alist}.
4783 User defined specifier. The next character in the format string should
4784 be a letter. Gnus will call the function
4785 @code{gnus-user-format-function-@var{x}}, where @var{x} is the letter
4786 following @samp{%u}. The function will be passed the current header as
4787 argument. The function should return a string, which will be inserted
4788 into the summary just like information from any other summary specifier.
4791 Text between @samp{%(} and @samp{%)} will be highlighted with
4792 @code{gnus-mouse-face} when the mouse point is placed inside the area.
4793 There can only be one such area.
4795 The @samp{%U} (status), @samp{%R} (replied) and @samp{%z} (zcore) specs
4796 have to be handled with care. For reasons of efficiency, Gnus will
4797 compute what column these characters will end up in, and ``hard-code''
4798 that. This means that it is invalid to have these specs after a
4799 variable-length spec. Well, you might not be arrested, but your summary
4800 buffer will look strange, which is bad enough.
4802 The smart choice is to have these specs as far to the left as possible.
4803 (Isn't that the case with everything, though? But I digress.)
4805 This restriction may disappear in later versions of Gnus.
4808 @node To From Newsgroups
4809 @subsection To From Newsgroups
4813 In some groups (particularly in archive groups), the @code{From} header
4814 isn't very interesting, since all the articles there are written by
4815 you. To display the information in the @code{To} or @code{Newsgroups}
4816 headers instead, you need to decide three things: What information to
4817 gather; where to display it; and when to display it.
4821 @vindex gnus-extra-headers
4822 The reading of extra header information is controlled by the
4823 @code{gnus-extra-headers}. This is a list of header symbols. For
4827 (setq gnus-extra-headers
4828 '(To Newsgroups X-Newsreader))
4831 This will result in Gnus trying to obtain these three headers, and
4832 storing it in header structures for later easy retrieval.
4835 @findex gnus-extra-header
4836 The value of these extra headers can be accessed via the
4837 @code{gnus-extra-header} function. Here's a format line spec that will
4838 access the @code{X-Newsreader} header:
4841 "%~(form (gnus-extra-header 'X-Newsreader))@@"
4845 @vindex gnus-ignored-from-addresses
4846 The @code{gnus-ignored-from-addresses} variable says when the @samp{%f}
4847 summary line spec returns the @code{To}, @code{Newsreader} or
4848 @code{From} header. If this regexp matches the contents of the
4849 @code{From} header, the value of the @code{To} or @code{Newsreader}
4850 headers are used instead.
4852 To distinguish regular articles from those where the @code{From} field
4853 has been swapped, a string is prefixed to the @code{To} or
4854 @code{Newsgroups} header in the summary line. By default the string is
4855 @samp{-> } for @code{To} and @samp{=> } for @code{Newsgroups}, you can
4856 customize these strings with @code{gnus-summary-to-prefix} and
4857 @code{gnus-summary-newsgroup-prefix}.
4861 @vindex nnmail-extra-headers
4862 A related variable is @code{nnmail-extra-headers}, which controls when
4863 to include extra headers when generating overview (@acronym{NOV}) files.
4864 If you have old overview files, you should regenerate them after
4865 changing this variable, by entering the server buffer using @kbd{^},
4866 and then @kbd{g} on the appropriate mail server (e.g. nnml) to cause
4869 @vindex gnus-summary-line-format
4870 You also have to instruct Gnus to display the data by changing the
4871 @code{%n} spec to the @code{%f} spec in the
4872 @code{gnus-summary-line-format} variable.
4874 In summary, you'd typically put something like the following in
4878 (setq gnus-extra-headers
4880 (setq nnmail-extra-headers gnus-extra-headers)
4881 (setq gnus-summary-line-format
4882 "%U%R%z%I%(%[%4L: %-23,23f%]%) %s\n")
4883 (setq gnus-ignored-from-addresses
4887 (The values listed above are the default values in Gnus. Alter them
4890 A note for news server administrators, or for users who wish to try to
4891 convince their news server administrator to provide some additional
4894 The above is mostly useful for mail groups, where you have control over
4895 the @acronym{NOV} files that are created. However, if you can persuade your
4896 nntp admin to add (in the usual implementation, notably INN):
4902 to the end of her @file{overview.fmt} file, then you can use that just
4903 as you would the extra headers from the mail groups.
4906 @node Summary Buffer Mode Line
4907 @subsection Summary Buffer Mode Line
4909 @vindex gnus-summary-mode-line-format
4910 You can also change the format of the summary mode bar (@pxref{Mode Line
4911 Formatting}). Set @code{gnus-summary-mode-line-format} to whatever you
4912 like. The default is @samp{Gnus: %%b [%A] %Z}.
4914 Here are the elements you can play with:
4920 Unprefixed group name.
4922 Current article number.
4924 Current article score.
4928 Number of unread articles in this group.
4930 Number of unread articles in this group that aren't displayed in the
4933 A string with the number of unread and unselected articles represented
4934 either as @samp{<%U(+%e) more>} if there are both unread and unselected
4935 articles, and just as @samp{<%U more>} if there are just unread articles
4936 and no unselected ones.
4938 Shortish group name. For instance, @samp{rec.arts.anime} will be
4939 shortened to @samp{r.a.anime}.
4941 Subject of the current article.
4943 User-defined spec (@pxref{User-Defined Specs}).
4945 Name of the current score file (@pxref{Scoring}).
4947 Number of dormant articles (@pxref{Unread Articles}).
4949 Number of ticked articles (@pxref{Unread Articles}).
4951 Number of articles that have been marked as read in this session.
4953 Number of articles expunged by the score files.
4957 @node Summary Highlighting
4958 @subsection Summary Highlighting
4962 @item gnus-visual-mark-article-hook
4963 @vindex gnus-visual-mark-article-hook
4964 This hook is run after selecting an article. It is meant to be used for
4965 highlighting the article in some way. It is not run if
4966 @code{gnus-visual} is @code{nil}.
4968 @item gnus-summary-update-hook
4969 @vindex gnus-summary-update-hook
4970 This hook is called when a summary line is changed. It is not run if
4971 @code{gnus-visual} is @code{nil}.
4973 @item gnus-summary-selected-face
4974 @vindex gnus-summary-selected-face
4975 This is the face (or @dfn{font} as some people call it) used to
4976 highlight the current article in the summary buffer.
4978 @item gnus-summary-highlight
4979 @vindex gnus-summary-highlight
4980 Summary lines are highlighted according to this variable, which is a
4981 list where the elements are of the format @code{(@var{form}
4982 . @var{face})}. If you would, for instance, like ticked articles to be
4983 italic and high-scored articles to be bold, you could set this variable
4986 (((eq mark gnus-ticked-mark) . italic)
4987 ((> score default) . bold))
4989 As you may have guessed, if @var{form} returns a non-@code{nil} value,
4990 @var{face} will be applied to the line.
4994 @node Summary Maneuvering
4995 @section Summary Maneuvering
4996 @cindex summary movement
4998 All the straight movement commands understand the numeric prefix and
4999 behave pretty much as you'd expect.
5001 None of these commands select articles.
5006 @kindex M-n (Summary)
5007 @kindex G M-n (Summary)
5008 @findex gnus-summary-next-unread-subject
5009 Go to the next summary line of an unread article
5010 (@code{gnus-summary-next-unread-subject}).
5014 @kindex M-p (Summary)
5015 @kindex G M-p (Summary)
5016 @findex gnus-summary-prev-unread-subject
5017 Go to the previous summary line of an unread article
5018 (@code{gnus-summary-prev-unread-subject}).
5021 @kindex G g (Summary)
5022 @findex gnus-summary-goto-subject
5023 Ask for an article number and then go to the summary line of that article
5024 without displaying the article (@code{gnus-summary-goto-subject}).
5027 If Gnus asks you to press a key to confirm going to the next group, you
5028 can use the @kbd{C-n} and @kbd{C-p} keys to move around the group
5029 buffer, searching for the next group to read without actually returning
5030 to the group buffer.
5032 Variables related to summary movement:
5036 @vindex gnus-auto-select-next
5037 @item gnus-auto-select-next
5038 If you issue one of the movement commands (like @kbd{n}) and there are
5039 no more unread articles after the current one, Gnus will offer to go to
5040 the next group. If this variable is @code{t} and the next group is
5041 empty, Gnus will exit summary mode and return to the group buffer. If
5042 this variable is neither @code{t} nor @code{nil}, Gnus will select the
5043 next group with unread articles. As a special case, if this variable
5044 is @code{quietly}, Gnus will select the next group without asking for
5045 confirmation. If this variable is @code{almost-quietly}, the same
5046 will happen only if you are located on the last article in the group.
5047 Finally, if this variable is @code{slightly-quietly}, the @kbd{Z n}
5048 command will go to the next group without confirmation. Also
5049 @pxref{Group Levels}.
5051 @item gnus-auto-select-same
5052 @vindex gnus-auto-select-same
5053 If non-@code{nil}, all the movement commands will try to go to the next
5054 article with the same subject as the current. (@dfn{Same} here might
5055 mean @dfn{roughly equal}. See @code{gnus-summary-gather-subject-limit}
5056 for details (@pxref{Customizing Threading}).) If there are no more
5057 articles with the same subject, go to the first unread article.
5059 This variable is not particularly useful if you use a threaded display.
5061 @item gnus-summary-check-current
5062 @vindex gnus-summary-check-current
5063 If non-@code{nil}, all the ``unread'' movement commands will not proceed
5064 to the next (or previous) article if the current article is unread.
5065 Instead, they will choose the current article.
5067 @item gnus-auto-center-summary
5068 @vindex gnus-auto-center-summary
5069 If non-@code{nil}, Gnus will keep the point in the summary buffer
5070 centered at all times. This makes things quite tidy, but if you have a
5071 slow network connection, or simply do not like this un-Emacsism, you can
5072 set this variable to @code{nil} to get the normal Emacs scrolling
5073 action. This will also inhibit horizontal re-centering of the summary
5074 buffer, which might make it more inconvenient to read extremely long
5077 This variable can also be a number. In that case, center the window at
5078 the given number of lines from the top.
5083 @node Choosing Articles
5084 @section Choosing Articles
5085 @cindex selecting articles
5088 * Choosing Commands:: Commands for choosing articles.
5089 * Choosing Variables:: Variables that influence these commands.
5093 @node Choosing Commands
5094 @subsection Choosing Commands
5096 None of the following movement commands understand the numeric prefix,
5097 and they all select and display an article.
5099 If you want to fetch new articles or redisplay the group, see
5100 @ref{Exiting the Summary Buffer}.
5104 @kindex SPACE (Summary)
5105 @findex gnus-summary-next-page
5106 Select the current article, or, if that one's read already, the next
5107 unread article (@code{gnus-summary-next-page}).
5109 If you have an article window open already and you press @kbd{SPACE}
5110 again, the article will be scrolled. This lets you conveniently
5111 @kbd{SPACE} through an entire newsgroup. @xref{Paging the Article}.
5116 @kindex G n (Summary)
5117 @findex gnus-summary-next-unread-article
5118 @c @icon{gnus-summary-next-unread}
5119 Go to next unread article (@code{gnus-summary-next-unread-article}).
5124 @findex gnus-summary-prev-unread-article
5125 @c @icon{gnus-summary-prev-unread}
5126 Go to previous unread article (@code{gnus-summary-prev-unread-article}).
5131 @kindex G N (Summary)
5132 @findex gnus-summary-next-article
5133 Go to the next article (@code{gnus-summary-next-article}).
5138 @kindex G P (Summary)
5139 @findex gnus-summary-prev-article
5140 Go to the previous article (@code{gnus-summary-prev-article}).
5143 @kindex G C-n (Summary)
5144 @findex gnus-summary-next-same-subject
5145 Go to the next article with the same subject
5146 (@code{gnus-summary-next-same-subject}).
5149 @kindex G C-p (Summary)
5150 @findex gnus-summary-prev-same-subject
5151 Go to the previous article with the same subject
5152 (@code{gnus-summary-prev-same-subject}).
5156 @kindex G f (Summary)
5158 @findex gnus-summary-first-unread-article
5159 Go to the first unread article
5160 (@code{gnus-summary-first-unread-article}).
5164 @kindex G b (Summary)
5166 @findex gnus-summary-best-unread-article
5167 Go to the unread article with the highest score
5168 (@code{gnus-summary-best-unread-article}). If given a prefix argument,
5169 go to the first unread article that has a score over the default score.
5174 @kindex G l (Summary)
5175 @findex gnus-summary-goto-last-article
5176 Go to the previous article read (@code{gnus-summary-goto-last-article}).
5179 @kindex G o (Summary)
5180 @findex gnus-summary-pop-article
5182 @cindex article history
5183 Pop an article off the summary history and go to this article
5184 (@code{gnus-summary-pop-article}). This command differs from the
5185 command above in that you can pop as many previous articles off the
5186 history as you like, while @kbd{l} toggles the two last read articles.
5187 For a somewhat related issue (if you use these commands a lot),
5188 @pxref{Article Backlog}.
5193 @kindex G j (Summary)
5194 @findex gnus-summary-goto-article
5195 Ask for an article number or @code{Message-ID}, and then go to that
5196 article (@code{gnus-summary-goto-article}).
5201 @node Choosing Variables
5202 @subsection Choosing Variables
5204 Some variables relevant for moving and selecting articles:
5207 @item gnus-auto-extend-newsgroup
5208 @vindex gnus-auto-extend-newsgroup
5209 All the movement commands will try to go to the previous (or next)
5210 article, even if that article isn't displayed in the Summary buffer if
5211 this variable is non-@code{nil}. Gnus will then fetch the article from
5212 the server and display it in the article buffer.
5214 @item gnus-select-article-hook
5215 @vindex gnus-select-article-hook
5216 This hook is called whenever an article is selected. The default is
5217 @code{nil}. If you would like each article to be saved in the Agent as
5218 you read it, putting @code{gnus-agent-fetch-selected-article} on this
5221 @item gnus-mark-article-hook
5222 @vindex gnus-mark-article-hook
5223 @findex gnus-summary-mark-unread-as-read
5224 @findex gnus-summary-mark-read-and-unread-as-read
5225 @findex gnus-unread-mark
5226 This hook is called whenever an article is selected. It is intended to
5227 be used for marking articles as read. The default value is
5228 @code{gnus-summary-mark-read-and-unread-as-read}, and will change the
5229 mark of almost any article you read to @code{gnus-read-mark}. The only
5230 articles not affected by this function are ticked, dormant, and
5231 expirable articles. If you'd instead like to just have unread articles
5232 marked as read, you can use @code{gnus-summary-mark-unread-as-read}
5233 instead. It will leave marks like @code{gnus-low-score-mark},
5234 @code{gnus-del-mark} (and so on) alone.
5239 @node Paging the Article
5240 @section Scrolling the Article
5241 @cindex article scrolling
5246 @kindex SPACE (Summary)
5247 @findex gnus-summary-next-page
5248 Pressing @kbd{SPACE} will scroll the current article forward one page,
5249 or, if you have come to the end of the current article, will choose the
5250 next article (@code{gnus-summary-next-page}).
5252 @vindex gnus-article-boring-faces
5253 @vindex gnus-article-skip-boring
5254 If @code{gnus-article-skip-boring} is non-@code{nil} and the rest of
5255 the article consists only of citations and signature, then it will be
5256 skipped; the next article will be shown instead. You can customize
5257 what is considered uninteresting with
5258 @code{gnus-article-boring-faces}. You can manually view the article's
5259 pages, no matter how boring, using @kbd{C-M-v}.
5262 @kindex DEL (Summary)
5263 @findex gnus-summary-prev-page
5264 Scroll the current article back one page (@code{gnus-summary-prev-page}).
5267 @kindex RET (Summary)
5268 @findex gnus-summary-scroll-up
5269 Scroll the current article one line forward
5270 (@code{gnus-summary-scroll-up}).
5273 @kindex M-RET (Summary)
5274 @findex gnus-summary-scroll-down
5275 Scroll the current article one line backward
5276 (@code{gnus-summary-scroll-down}).
5280 @kindex A g (Summary)
5282 @findex gnus-summary-show-article
5283 @vindex gnus-summary-show-article-charset-alist
5284 (Re)fetch the current article (@code{gnus-summary-show-article}). If
5285 given a prefix, fetch the current article, but don't run any of the
5286 article treatment functions. This will give you a ``raw'' article, just
5287 the way it came from the server.
5289 If given a numerical prefix, you can do semi-manual charset stuff.
5290 @kbd{C-u 0 g cn-gb-2312 RET} will decode the message as if it were
5291 encoded in the @code{cn-gb-2312} charset. If you have
5294 (setq gnus-summary-show-article-charset-alist
5299 then you can say @kbd{C-u 1 g} to get the same effect.
5304 @kindex A < (Summary)
5305 @findex gnus-summary-beginning-of-article
5306 Scroll to the beginning of the article
5307 (@code{gnus-summary-beginning-of-article}).
5312 @kindex A > (Summary)
5313 @findex gnus-summary-end-of-article
5314 Scroll to the end of the article (@code{gnus-summary-end-of-article}).
5318 @kindex A s (Summary)
5320 @findex gnus-summary-isearch-article
5321 Perform an isearch in the article buffer
5322 (@code{gnus-summary-isearch-article}).
5326 @findex gnus-summary-select-article-buffer
5327 Select the article buffer (@code{gnus-summary-select-article-buffer}).
5332 @node Reply Followup and Post
5333 @section Reply, Followup and Post
5336 * Summary Mail Commands:: Sending mail.
5337 * Summary Post Commands:: Sending news.
5338 * Summary Message Commands:: Other Message-related commands.
5339 * Canceling and Superseding::
5343 @node Summary Mail Commands
5344 @subsection Summary Mail Commands
5346 @cindex composing mail
5348 Commands for composing a mail message:
5354 @kindex S r (Summary)
5356 @findex gnus-summary-reply
5357 @c @icon{gnus-summary-mail-reply}
5358 @c @icon{gnus-summary-reply}
5359 Mail a reply to the author of the current article
5360 (@code{gnus-summary-reply}).
5365 @kindex S R (Summary)
5366 @findex gnus-summary-reply-with-original
5367 @c @icon{gnus-summary-reply-with-original}
5368 Mail a reply to the author of the current article and include the
5369 original message (@code{gnus-summary-reply-with-original}). This
5370 command uses the process/prefix convention.
5373 @kindex S w (Summary)
5374 @findex gnus-summary-wide-reply
5375 Mail a wide reply to the author of the current article
5376 (@code{gnus-summary-wide-reply}). A @dfn{wide reply} is a reply that
5377 goes out to all people listed in the @code{To}, @code{From} (or
5378 @code{Reply-to}) and @code{Cc} headers. If @code{Mail-Followup-To} is
5379 present, that's used instead.
5382 @kindex S W (Summary)
5383 @findex gnus-summary-wide-reply-with-original
5384 Mail a wide reply to the current article and include the original
5385 message (@code{gnus-summary-wide-reply-with-original}). This command uses
5386 the process/prefix convention.
5389 @kindex S v (Summary)
5390 @findex gnus-summary-very-wide-reply
5391 Mail a very wide reply to the author of the current article
5392 (@code{gnus-summary-wide-reply}). A @dfn{very wide reply} is a reply
5393 that goes out to all people listed in the @code{To}, @code{From} (or
5394 @code{Reply-to}) and @code{Cc} headers in all the process/prefixed
5395 articles. This command uses the process/prefix convention.
5398 @kindex S V (Summary)
5399 @findex gnus-summary-very-wide-reply-with-original
5400 Mail a very wide reply to the author of the current article and include the
5401 original message (@code{gnus-summary-very-wide-reply-with-original}). This
5402 command uses the process/prefix convention.
5405 @kindex S B r (Summary)
5406 @findex gnus-summary-reply-broken-reply-to
5407 Mail a reply to the author of the current article but ignore the
5408 @code{Reply-To} field (@code{gnus-summary-reply-broken-reply-to}).
5409 If you need this because a mailing list incorrectly sets a
5410 @code{Reply-To} header pointing to the list, you probably want to set
5411 the @code{broken-reply-to} group parameter instead, so things will work
5412 correctly. @xref{Group Parameters}.
5415 @kindex S B R (Summary)
5416 @findex gnus-summary-reply-broken-reply-to-with-original
5417 Mail a reply to the author of the current article and include the
5418 original message but ignore the @code{Reply-To} field
5419 (@code{gnus-summary-reply-broken-reply-to-with-original}).
5423 @kindex S o m (Summary)
5424 @kindex C-c C-f (Summary)
5425 @findex gnus-summary-mail-forward
5426 @c @icon{gnus-summary-mail-forward}
5427 Forward the current article to some other person
5428 (@code{gnus-summary-mail-forward}). If no prefix is given, the message
5429 is forwarded according to the value of (@code{message-forward-as-mime})
5430 and (@code{message-forward-show-mml}); if the prefix is 1, decode the
5431 message and forward directly inline; if the prefix is 2, forward message
5432 as an rfc822 @acronym{MIME} section; if the prefix is 3, decode message and
5433 forward as an rfc822 @acronym{MIME} section; if the prefix is 4, forward message
5434 directly inline; otherwise, the message is forwarded as no prefix given
5435 but use the flipped value of (@code{message-forward-as-mime}). By
5436 default, the message is decoded and forwarded as an rfc822 @acronym{MIME}
5442 @kindex S m (Summary)
5443 @findex gnus-summary-mail-other-window
5444 @c @icon{gnus-summary-mail-originate}
5445 Prepare a mail (@code{gnus-summary-mail-other-window}). By default, use
5446 the posting style of the current group. If given a prefix, disable that.
5447 If the prefix is 1, prompt for a group name to find the posting style.
5452 @kindex S i (Summary)
5453 @findex gnus-summary-news-other-window
5454 Prepare a news (@code{gnus-summary-news-other-window}). By default,
5455 post to the current group. If given a prefix, disable that. If the
5456 prefix is 1, prompt for a group to post to.
5458 This function actually prepares a news even when using mail groups.
5459 This is useful for ``posting'' messages to mail groups without actually
5460 sending them over the network: they're just saved directly to the group
5461 in question. The corresponding back end must have a request-post method
5462 for this to work though.
5465 @kindex S D b (Summary)
5466 @findex gnus-summary-resend-bounced-mail
5467 @cindex bouncing mail
5468 If you have sent a mail, but the mail was bounced back to you for some
5469 reason (wrong address, transient failure), you can use this command to
5470 resend that bounced mail (@code{gnus-summary-resend-bounced-mail}). You
5471 will be popped into a mail buffer where you can edit the headers before
5472 sending the mail off again. If you give a prefix to this command, and
5473 the bounced mail is a reply to some other mail, Gnus will try to fetch
5474 that mail and display it for easy perusal of its headers. This might
5475 very well fail, though.
5478 @kindex S D r (Summary)
5479 @findex gnus-summary-resend-message
5480 Not to be confused with the previous command,
5481 @code{gnus-summary-resend-message} will prompt you for an address to
5482 send the current message off to, and then send it to that place. The
5483 headers of the message won't be altered---but lots of headers that say
5484 @code{Resent-To}, @code{Resent-From} and so on will be added. This
5485 means that you actually send a mail to someone that has a @code{To}
5486 header that (probably) points to yourself. This will confuse people.
5487 So, natcherly you'll only do that if you're really eVIl.
5489 This command is mainly used if you have several accounts and want to
5490 ship a mail to a different account of yours. (If you're both
5491 @code{root} and @code{postmaster} and get a mail for @code{postmaster}
5492 to the @code{root} account, you may want to resend it to
5493 @code{postmaster}. Ordnung muss sein!
5495 This command understands the process/prefix convention
5496 (@pxref{Process/Prefix}).
5499 @kindex S D e (Summary)
5500 @findex gnus-summary-resend-message-edit
5502 Like the previous command, but will allow you to edit the message as
5503 if it were a new message before resending.
5506 @kindex S O m (Summary)
5507 @findex gnus-uu-digest-mail-forward
5508 Digest the current series (@pxref{Decoding Articles}) and forward the
5509 result using mail (@code{gnus-uu-digest-mail-forward}). This command
5510 uses the process/prefix convention (@pxref{Process/Prefix}).
5513 @kindex S M-c (Summary)
5514 @findex gnus-summary-mail-crosspost-complaint
5515 @cindex crossposting
5516 @cindex excessive crossposting
5517 Send a complaint about excessive crossposting to the author of the
5518 current article (@code{gnus-summary-mail-crosspost-complaint}).
5520 @findex gnus-crosspost-complaint
5521 This command is provided as a way to fight back against the current
5522 crossposting pandemic that's sweeping Usenet. It will compose a reply
5523 using the @code{gnus-crosspost-complaint} variable as a preamble. This
5524 command understands the process/prefix convention
5525 (@pxref{Process/Prefix}) and will prompt you before sending each mail.
5529 Also @xref{Header Commands, ,Header Commands, message, The Message
5530 Manual}, for more information.
5533 @node Summary Post Commands
5534 @subsection Summary Post Commands
5536 @cindex composing news
5538 Commands for posting a news article:
5544 @kindex S p (Summary)
5545 @findex gnus-summary-post-news
5546 @c @icon{gnus-summary-post-news}
5547 Prepare for posting an article (@code{gnus-summary-post-news}). By
5548 default, post to the current group. If given a prefix, disable that.
5549 If the prefix is 1, prompt for another group instead.
5554 @kindex S f (Summary)
5555 @findex gnus-summary-followup
5556 @c @icon{gnus-summary-followup}
5557 Post a followup to the current article (@code{gnus-summary-followup}).
5561 @kindex S F (Summary)
5563 @c @icon{gnus-summary-followup-with-original}
5564 @findex gnus-summary-followup-with-original
5565 Post a followup to the current article and include the original message
5566 (@code{gnus-summary-followup-with-original}). This command uses the
5567 process/prefix convention.
5570 @kindex S n (Summary)
5571 @findex gnus-summary-followup-to-mail
5572 Post a followup to the current article via news, even if you got the
5573 message through mail (@code{gnus-summary-followup-to-mail}).
5576 @kindex S N (Summary)
5577 @findex gnus-summary-followup-to-mail-with-original
5578 Post a followup to the current article via news, even if you got the
5579 message through mail and include the original message
5580 (@code{gnus-summary-followup-to-mail-with-original}). This command uses
5581 the process/prefix convention.
5584 @kindex S o p (Summary)
5585 @findex gnus-summary-post-forward
5586 Forward the current article to a newsgroup
5587 (@code{gnus-summary-post-forward}).
5588 If no prefix is given, the message is forwarded according to the value
5589 of (@code{message-forward-as-mime}) and
5590 (@code{message-forward-show-mml}); if the prefix is 1, decode the
5591 message and forward directly inline; if the prefix is 2, forward message
5592 as an rfc822 @acronym{MIME} section; if the prefix is 3, decode message and
5593 forward as an rfc822 @acronym{MIME} section; if the prefix is 4, forward message
5594 directly inline; otherwise, the message is forwarded as no prefix given
5595 but use the flipped value of (@code{message-forward-as-mime}). By
5596 default, the message is decoded and forwarded as an rfc822 @acronym{MIME} section.
5599 @kindex S O p (Summary)
5600 @findex gnus-uu-digest-post-forward
5602 @cindex making digests
5603 Digest the current series and forward the result to a newsgroup
5604 (@code{gnus-uu-digest-post-forward}). This command uses the
5605 process/prefix convention.
5608 @kindex S u (Summary)
5609 @findex gnus-uu-post-news
5610 @c @icon{gnus-uu-post-news}
5611 Uuencode a file, split it into parts, and post it as a series
5612 (@code{gnus-uu-post-news}). (@pxref{Uuencoding and Posting}).
5615 Also @xref{Header Commands, ,Header Commands, message, The Message
5616 Manual}, for more information.
5619 @node Summary Message Commands
5620 @subsection Summary Message Commands
5624 @kindex S y (Summary)
5625 @findex gnus-summary-yank-message
5626 Yank the current article into an already existing Message composition
5627 buffer (@code{gnus-summary-yank-message}). This command prompts for
5628 what message buffer you want to yank into, and understands the
5629 process/prefix convention (@pxref{Process/Prefix}).
5634 @node Canceling and Superseding
5635 @subsection Canceling Articles
5636 @cindex canceling articles
5637 @cindex superseding articles
5639 Have you ever written something, and then decided that you really,
5640 really, really wish you hadn't posted that?
5642 Well, you can't cancel mail, but you can cancel posts.
5644 @findex gnus-summary-cancel-article
5646 @c @icon{gnus-summary-cancel-article}
5647 Find the article you wish to cancel (you can only cancel your own
5648 articles, so don't try any funny stuff). Then press @kbd{C} or @kbd{S
5649 c} (@code{gnus-summary-cancel-article}). Your article will be
5650 canceled---machines all over the world will be deleting your article.
5651 This command uses the process/prefix convention (@pxref{Process/Prefix}).
5653 Be aware, however, that not all sites honor cancels, so your article may
5654 live on here and there, while most sites will delete the article in
5657 Gnus will use the ``current'' select method when canceling. If you
5658 want to use the standard posting method, use the @samp{a} symbolic
5659 prefix (@pxref{Symbolic Prefixes}).
5661 Gnus ensures that only you can cancel your own messages using a
5662 @code{Cancel-Lock} header (@pxref{Canceling News, Canceling News, ,
5663 message, Message Manual}).
5665 If you discover that you have made some mistakes and want to do some
5666 corrections, you can post a @dfn{superseding} article that will replace
5667 your original article.
5669 @findex gnus-summary-supersede-article
5671 Go to the original article and press @kbd{S s}
5672 (@code{gnus-summary-supersede-article}). You will be put in a buffer
5673 where you can edit the article all you want before sending it off the
5676 The same goes for superseding as for canceling, only more so: Some
5677 sites do not honor superseding. On those sites, it will appear that you
5678 have posted almost the same article twice.
5680 If you have just posted the article, and change your mind right away,
5681 there is a trick you can use to cancel/supersede the article without
5682 waiting for the article to appear on your site first. You simply return
5683 to the post buffer (which is called @code{*sent ...*}). There you will
5684 find the article you just posted, with all the headers intact. Change
5685 the @code{Message-ID} header to a @code{Cancel} or @code{Supersedes}
5686 header by substituting one of those words for the word
5687 @code{Message-ID}. Then just press @kbd{C-c C-c} to send the article as
5688 you would do normally. The previous article will be
5689 canceled/superseded.
5691 Just remember, kids: There is no 'c' in 'supersede'.
5693 @node Delayed Articles
5694 @section Delayed Articles
5695 @cindex delayed sending
5696 @cindex send delayed
5698 Sometimes, you might wish to delay the sending of a message. For
5699 example, you might wish to arrange for a message to turn up just in time
5700 to remind your about the birthday of your Significant Other. For this,
5701 there is the @code{gnus-delay} package. Setup is simple:
5704 (gnus-delay-initialize)
5707 @findex gnus-delay-article
5708 Normally, to send a message you use the @kbd{C-c C-c} command from
5709 Message mode. To delay a message, use @kbd{C-c C-j}
5710 (@code{gnus-delay-article}) instead. This will ask you for how long the
5711 message should be delayed. Possible answers are:
5715 A time span. Consists of an integer and a letter. For example,
5716 @code{42d} means to delay for 42 days. Available letters are @code{m}
5717 (minutes), @code{h} (hours), @code{d} (days), @code{w} (weeks), @code{M}
5718 (months) and @code{Y} (years).
5721 A specific date. Looks like @code{YYYY-MM-DD}. The message will be
5722 delayed until that day, at a specific time (eight o'clock by default).
5723 See also @code{gnus-delay-default-hour}.
5726 A specific time of day. Given in @code{hh:mm} format, 24h, no am/pm
5727 stuff. The deadline will be at that time today, except if that time has
5728 already passed, then it's at the given time tomorrow. So if it's ten
5729 o'clock in the morning and you specify @code{11:15}, then the deadline
5730 is one hour and fifteen minutes hence. But if you specify @code{9:20},
5731 that means a time tomorrow.
5734 The action of the @code{gnus-delay-article} command is influenced by a
5735 couple of variables:
5738 @item gnus-delay-default-hour
5739 @vindex gnus-delay-default-hour
5740 When you specify a specific date, the message will be due on that hour
5741 on the given date. Possible values are integers 0 through 23.
5743 @item gnus-delay-default-delay
5744 @vindex gnus-delay-default-delay
5745 This is a string and gives the default delay. It can be of any of the
5746 formats described above.
5748 @item gnus-delay-group
5749 @vindex gnus-delay-group
5750 Delayed articles will be kept in this group on the drafts server until
5751 they are due. You probably don't need to change this. The default
5752 value is @code{"delayed"}.
5754 @item gnus-delay-header
5755 @vindex gnus-delay-header
5756 The deadline for each article will be stored in a header. This variable
5757 is a string and gives the header name. You probably don't need to
5758 change this. The default value is @code{"X-Gnus-Delayed"}.
5761 The way delaying works is like this: when you use the
5762 @code{gnus-delay-article} command, you give a certain delay. Gnus
5763 calculates the deadline of the message and stores it in the
5764 @code{X-Gnus-Delayed} header and puts the message in the
5765 @code{nndraft:delayed} group.
5767 @findex gnus-delay-send-queue
5768 And whenever you get new news, Gnus looks through the group for articles
5769 which are due and sends them. It uses the @code{gnus-delay-send-queue}
5770 function for this. By default, this function is added to the hook
5771 @code{gnus-get-new-news-hook}. But of course, you can change this.
5772 Maybe you want to use the demon to send drafts? Just tell the demon to
5773 execute the @code{gnus-delay-send-queue} function.
5776 @item gnus-delay-initialize
5777 @findex gnus-delay-initialize
5778 By default, this function installs @code{gnus-delay-send-queue} in
5779 @code{gnus-get-new-news-hook}. But it accepts the optional second
5780 argument @code{no-check}. If it is non-@code{nil},
5781 @code{gnus-get-new-news-hook} is not changed. The optional first
5782 argument is ignored.
5784 For example, @code{(gnus-delay-initialize nil t)} means to do nothing.
5785 Presumably, you want to use the demon for sending due delayed articles.
5786 Just don't forget to set that up :-)
5790 @node Marking Articles
5791 @section Marking Articles
5792 @cindex article marking
5793 @cindex article ticking
5796 There are several marks you can set on an article.
5798 You have marks that decide the @dfn{readedness} (whoo, neato-keano
5799 neologism ohoy!) of the article. Alphabetic marks generally mean
5800 @dfn{read}, while non-alphabetic characters generally mean @dfn{unread}.
5802 In addition, you also have marks that do not affect readedness.
5805 There's a plethora of commands for manipulating these marks.
5809 * Unread Articles:: Marks for unread articles.
5810 * Read Articles:: Marks for read articles.
5811 * Other Marks:: Marks that do not affect readedness.
5812 * Setting Marks:: How to set and remove marks.
5813 * Generic Marking Commands:: How to customize the marking.
5814 * Setting Process Marks:: How to mark articles for later processing.
5818 @node Unread Articles
5819 @subsection Unread Articles
5821 The following marks mark articles as (kinda) unread, in one form or
5826 @vindex gnus-ticked-mark
5827 Marked as ticked (@code{gnus-ticked-mark}).
5829 @dfn{Ticked articles} are articles that will remain visible always. If
5830 you see an article that you find interesting, or you want to put off
5831 reading it, or replying to it, until sometime later, you'd typically
5832 tick it. However, articles can be expired (from news servers by the
5833 news server software, Gnus itself never expires ticked messages), so if
5834 you want to keep an article forever, you'll have to make it persistent
5835 (@pxref{Persistent Articles}).
5838 @vindex gnus-dormant-mark
5839 Marked as dormant (@code{gnus-dormant-mark}).
5841 @dfn{Dormant articles} will only appear in the summary buffer if there
5842 are followups to it. If you want to see them even if they don't have
5843 followups, you can use the @kbd{/ D} command (@pxref{Limiting}).
5844 Otherwise (except for the visibility issue), they are just like ticked
5848 @vindex gnus-unread-mark
5849 Marked as unread (@code{gnus-unread-mark}).
5851 @dfn{Unread articles} are articles that haven't been read at all yet.
5856 @subsection Read Articles
5857 @cindex expirable mark
5859 All the following marks mark articles as read.
5864 @vindex gnus-del-mark
5865 These are articles that the user has marked as read with the @kbd{d}
5866 command manually, more or less (@code{gnus-del-mark}).
5869 @vindex gnus-read-mark
5870 Articles that have actually been read (@code{gnus-read-mark}).
5873 @vindex gnus-ancient-mark
5874 Articles that were marked as read in previous sessions and are now
5875 @dfn{old} (@code{gnus-ancient-mark}).
5878 @vindex gnus-killed-mark
5879 Marked as killed (@code{gnus-killed-mark}).
5882 @vindex gnus-kill-file-mark
5883 Marked as killed by kill files (@code{gnus-kill-file-mark}).
5886 @vindex gnus-low-score-mark
5887 Marked as read by having too low a score (@code{gnus-low-score-mark}).
5890 @vindex gnus-catchup-mark
5891 Marked as read by a catchup (@code{gnus-catchup-mark}).
5894 @vindex gnus-canceled-mark
5895 Canceled article (@code{gnus-canceled-mark})
5898 @vindex gnus-souped-mark
5899 @sc{soup}ed article (@code{gnus-souped-mark}). @xref{SOUP}.
5902 @vindex gnus-sparse-mark
5903 Sparsely reffed article (@code{gnus-sparse-mark}). @xref{Customizing
5907 @vindex gnus-duplicate-mark
5908 Article marked as read by duplicate suppression
5909 (@code{gnus-duplicate-mark}). @xref{Duplicate Suppression}.
5913 All these marks just mean that the article is marked as read, really.
5914 They are interpreted differently when doing adaptive scoring, though.
5916 One more special mark, though:
5920 @vindex gnus-expirable-mark
5921 Marked as expirable (@code{gnus-expirable-mark}).
5923 Marking articles as @dfn{expirable} (or have them marked as such
5924 automatically) doesn't make much sense in normal groups---a user doesn't
5925 control expiring of news articles, but in mail groups, for instance,
5926 articles marked as @dfn{expirable} can be deleted by Gnus at
5932 @subsection Other Marks
5933 @cindex process mark
5936 There are some marks that have nothing to do with whether the article is
5942 You can set a bookmark in the current article. Say you are reading a
5943 long thesis on cats' urinary tracts, and have to go home for dinner
5944 before you've finished reading the thesis. You can then set a bookmark
5945 in the article, and Gnus will jump to this bookmark the next time it
5946 encounters the article. @xref{Setting Marks}.
5949 @vindex gnus-replied-mark
5950 All articles that you have replied to or made a followup to (i.e., have
5951 answered) will be marked with an @samp{A} in the second column
5952 (@code{gnus-replied-mark}).
5955 @vindex gnus-forwarded-mark
5956 All articles that you have forwarded will be marked with an @samp{F} in
5957 the second column (@code{gnus-forwarded-mark}).
5960 @vindex gnus-cached-mark
5961 Articles stored in the article cache will be marked with an @samp{*} in
5962 the second column (@code{gnus-cached-mark}). @xref{Article Caching}.
5965 @vindex gnus-saved-mark
5966 Articles ``saved'' (in some manner or other; not necessarily
5967 religiously) are marked with an @samp{S} in the second column
5968 (@code{gnus-saved-mark}).
5971 @vindex gnus-recent-mark
5972 Articles that according to the server haven't been shown to the user
5973 before are marked with a @samp{N} in the second column
5974 (@code{gnus-recent-mark}). Note that not all servers support this
5975 mark, in which case it simply never appears. Compare with
5976 @code{gnus-unseen-mark}.
5979 @vindex gnus-unseen-mark
5980 Articles that haven't been seen before in Gnus by the user are marked
5981 with a @samp{.} in the second column (@code{gnus-unseen-mark}).
5982 Compare with @code{gnus-recent-mark}.
5985 @vindex gnus-downloaded-mark
5986 When using the Gnus agent (@pxref{Agent Basics}), articles may be
5987 downloaded for unplugged (offline) viewing. If you are using the
5988 @samp{%O} spec, these articles get the @samp{+} mark in that spec.
5989 (The variable @code{gnus-downloaded-mark} controls which character to
5993 @vindex gnus-undownloaded-mark
5994 When using the Gnus agent (@pxref{Agent Basics}), some articles might
5995 not have been downloaded. Such articles cannot be viewed while you
5996 are unplugged (offline). If you are using the @samp{%O} spec, these
5997 articles get the @samp{-} mark in that spec. (The variable
5998 @code{gnus-undownloaded-mark} controls which character to use.)
6001 @vindex gnus-downloadable-mark
6002 The Gnus agent (@pxref{Agent Basics}) downloads some articles
6003 automatically, but it is also possible to explicitly mark articles for
6004 download, even if they would not be downloaded automatically. Such
6005 explicitly-marked articles get the @samp{%} mark in the first column.
6006 (The variable @code{gnus-downloadable-mark} controls which character to
6010 @vindex gnus-not-empty-thread-mark
6011 @vindex gnus-empty-thread-mark
6012 If the @samp{%e} spec is used, the presence of threads or not will be
6013 marked with @code{gnus-not-empty-thread-mark} and
6014 @code{gnus-empty-thread-mark} in the third column, respectively.
6017 @vindex gnus-process-mark
6018 Finally we have the @dfn{process mark} (@code{gnus-process-mark}). A
6019 variety of commands react to the presence of the process mark. For
6020 instance, @kbd{X u} (@code{gnus-uu-decode-uu}) will uudecode and view
6021 all articles that have been marked with the process mark. Articles
6022 marked with the process mark have a @samp{#} in the second column.
6026 You might have noticed that most of these ``non-readedness'' marks
6027 appear in the second column by default. So if you have a cached, saved,
6028 replied article that you have process-marked, what will that look like?
6030 Nothing much. The precedence rules go as follows: process -> cache ->
6031 replied -> saved. So if the article is in the cache and is replied,
6032 you'll only see the cache mark and not the replied mark.
6036 @subsection Setting Marks
6037 @cindex setting marks
6039 All the marking commands understand the numeric prefix.
6044 @kindex M c (Summary)
6045 @kindex M-u (Summary)
6046 @findex gnus-summary-clear-mark-forward
6047 @cindex mark as unread
6048 Clear all readedness-marks from the current article
6049 (@code{gnus-summary-clear-mark-forward}). In other words, mark the
6055 @kindex M t (Summary)
6056 @findex gnus-summary-tick-article-forward
6057 Tick the current article (@code{gnus-summary-tick-article-forward}).
6058 @xref{Article Caching}.
6063 @kindex M ? (Summary)
6064 @findex gnus-summary-mark-as-dormant
6065 Mark the current article as dormant
6066 (@code{gnus-summary-mark-as-dormant}). @xref{Article Caching}.
6070 @kindex M d (Summary)
6072 @findex gnus-summary-mark-as-read-forward
6073 Mark the current article as read
6074 (@code{gnus-summary-mark-as-read-forward}).
6078 @findex gnus-summary-mark-as-read-backward
6079 Mark the current article as read and move point to the previous line
6080 (@code{gnus-summary-mark-as-read-backward}).
6085 @kindex M k (Summary)
6086 @findex gnus-summary-kill-same-subject-and-select
6087 Mark all articles that have the same subject as the current one as read,
6088 and then select the next unread article
6089 (@code{gnus-summary-kill-same-subject-and-select}).
6093 @kindex M K (Summary)
6094 @kindex C-k (Summary)
6095 @findex gnus-summary-kill-same-subject
6096 Mark all articles that have the same subject as the current one as read
6097 (@code{gnus-summary-kill-same-subject}).
6100 @kindex M C (Summary)
6101 @findex gnus-summary-catchup
6102 @c @icon{gnus-summary-catchup}
6103 Mark all unread articles as read (@code{gnus-summary-catchup}).
6106 @kindex M C-c (Summary)
6107 @findex gnus-summary-catchup-all
6108 Mark all articles in the group as read---even the ticked and dormant
6109 articles (@code{gnus-summary-catchup-all}).
6112 @kindex M H (Summary)
6113 @findex gnus-summary-catchup-to-here
6114 Catchup the current group to point (before the point)
6115 (@code{gnus-summary-catchup-to-here}).
6118 @kindex M h (Summary)
6119 @findex gnus-summary-catchup-from-here
6120 Catchup the current group from point (after the point)
6121 (@code{gnus-summary-catchup-from-here}).
6124 @kindex C-w (Summary)
6125 @findex gnus-summary-mark-region-as-read
6126 Mark all articles between point and mark as read
6127 (@code{gnus-summary-mark-region-as-read}).
6130 @kindex M V k (Summary)
6131 @findex gnus-summary-kill-below
6132 Kill all articles with scores below the default score (or below the
6133 numeric prefix) (@code{gnus-summary-kill-below}).
6137 @kindex M e (Summary)
6139 @findex gnus-summary-mark-as-expirable
6140 Mark the current article as expirable
6141 (@code{gnus-summary-mark-as-expirable}).
6144 @kindex M b (Summary)
6145 @findex gnus-summary-set-bookmark
6146 Set a bookmark in the current article
6147 (@code{gnus-summary-set-bookmark}).
6150 @kindex M B (Summary)
6151 @findex gnus-summary-remove-bookmark
6152 Remove the bookmark from the current article
6153 (@code{gnus-summary-remove-bookmark}).
6156 @kindex M V c (Summary)
6157 @findex gnus-summary-clear-above
6158 Clear all marks from articles with scores over the default score (or
6159 over the numeric prefix) (@code{gnus-summary-clear-above}).
6162 @kindex M V u (Summary)
6163 @findex gnus-summary-tick-above
6164 Tick all articles with scores over the default score (or over the
6165 numeric prefix) (@code{gnus-summary-tick-above}).
6168 @kindex M V m (Summary)
6169 @findex gnus-summary-mark-above
6170 Prompt for a mark, and mark all articles with scores over the default
6171 score (or over the numeric prefix) with this mark
6172 (@code{gnus-summary-clear-above}).
6175 @vindex gnus-summary-goto-unread
6176 The @code{gnus-summary-goto-unread} variable controls what action should
6177 be taken after setting a mark. If non-@code{nil}, point will move to
6178 the next/previous unread article. If @code{nil}, point will just move
6179 one line up or down. As a special case, if this variable is
6180 @code{never}, all the marking commands as well as other commands (like
6181 @kbd{SPACE}) will move to the next article, whether it is unread or not.
6182 The default is @code{t}.
6185 @node Generic Marking Commands
6186 @subsection Generic Marking Commands
6188 Some people would like the command that ticks an article (@kbd{!}) go to
6189 the next article. Others would like it to go to the next unread
6190 article. Yet others would like it to stay on the current article. And
6191 even though I haven't heard of anybody wanting it to go to the
6192 previous (unread) article, I'm sure there are people that want that as
6195 Multiply these five behaviors with five different marking commands, and
6196 you get a potentially complex set of variable to control what each
6199 To sidestep that mess, Gnus provides commands that do all these
6200 different things. They can be found on the @kbd{M M} map in the summary
6201 buffer. Type @kbd{M M C-h} to see them all---there are too many of them
6202 to list in this manual.
6204 While you can use these commands directly, most users would prefer
6205 altering the summary mode keymap. For instance, if you would like the
6206 @kbd{!} command to go to the next article instead of the next unread
6207 article, you could say something like:
6211 (add-hook 'gnus-summary-mode-hook 'my-alter-summary-map)
6212 (defun my-alter-summary-map ()
6213 (local-set-key "!" 'gnus-summary-put-mark-as-ticked-next))
6221 (defun my-alter-summary-map ()
6222 (local-set-key "!" "MM!n"))
6226 @node Setting Process Marks
6227 @subsection Setting Process Marks
6228 @cindex setting process marks
6230 Process marks are displayed as @code{#} in the summary buffer, and are
6231 used for marking articles in such a way that other commands will
6232 process these articles. For instance, if you process mark four
6233 articles and then use the @kbd{*} command, Gnus will enter these four
6234 commands into the cache. For more information,
6235 @pxref{Process/Prefix}.
6242 @kindex M P p (Summary)
6243 @findex gnus-summary-mark-as-processable
6244 Mark the current article with the process mark
6245 (@code{gnus-summary-mark-as-processable}).
6246 @findex gnus-summary-unmark-as-processable
6250 @kindex M P u (Summary)
6251 @kindex M-# (Summary)
6252 Remove the process mark, if any, from the current article
6253 (@code{gnus-summary-unmark-as-processable}).
6256 @kindex M P U (Summary)
6257 @findex gnus-summary-unmark-all-processable
6258 Remove the process mark from all articles
6259 (@code{gnus-summary-unmark-all-processable}).
6262 @kindex M P i (Summary)
6263 @findex gnus-uu-invert-processable
6264 Invert the list of process marked articles
6265 (@code{gnus-uu-invert-processable}).
6268 @kindex M P R (Summary)
6269 @findex gnus-uu-mark-by-regexp
6270 Mark articles that have a @code{Subject} header that matches a regular
6271 expression (@code{gnus-uu-mark-by-regexp}).
6274 @kindex M P G (Summary)
6275 @findex gnus-uu-unmark-by-regexp
6276 Unmark articles that have a @code{Subject} header that matches a regular
6277 expression (@code{gnus-uu-unmark-by-regexp}).
6280 @kindex M P r (Summary)
6281 @findex gnus-uu-mark-region
6282 Mark articles in region (@code{gnus-uu-mark-region}).
6285 @kindex M P g (Summary)
6286 @findex gnus-uu-unmark-region
6287 Unmark articles in region (@code{gnus-uu-unmark-region}).
6290 @kindex M P t (Summary)
6291 @findex gnus-uu-mark-thread
6292 Mark all articles in the current (sub)thread
6293 (@code{gnus-uu-mark-thread}).
6296 @kindex M P T (Summary)
6297 @findex gnus-uu-unmark-thread
6298 Unmark all articles in the current (sub)thread
6299 (@code{gnus-uu-unmark-thread}).
6302 @kindex M P v (Summary)
6303 @findex gnus-uu-mark-over
6304 Mark all articles that have a score above the prefix argument
6305 (@code{gnus-uu-mark-over}).
6308 @kindex M P s (Summary)
6309 @findex gnus-uu-mark-series
6310 Mark all articles in the current series (@code{gnus-uu-mark-series}).
6313 @kindex M P S (Summary)
6314 @findex gnus-uu-mark-sparse
6315 Mark all series that have already had some articles marked
6316 (@code{gnus-uu-mark-sparse}).
6319 @kindex M P a (Summary)
6320 @findex gnus-uu-mark-all
6321 Mark all articles in series order (@code{gnus-uu-mark-all}).
6324 @kindex M P b (Summary)
6325 @findex gnus-uu-mark-buffer
6326 Mark all articles in the buffer in the order they appear
6327 (@code{gnus-uu-mark-buffer}).
6330 @kindex M P k (Summary)
6331 @findex gnus-summary-kill-process-mark
6332 Push the current process mark set onto the stack and unmark all articles
6333 (@code{gnus-summary-kill-process-mark}).
6336 @kindex M P y (Summary)
6337 @findex gnus-summary-yank-process-mark
6338 Pop the previous process mark set from the stack and restore it
6339 (@code{gnus-summary-yank-process-mark}).
6342 @kindex M P w (Summary)
6343 @findex gnus-summary-save-process-mark
6344 Push the current process mark set onto the stack
6345 (@code{gnus-summary-save-process-mark}).
6349 Also see the @kbd{&} command in @ref{Searching for Articles}, for how to
6350 set process marks based on article body contents.
6357 It can be convenient to limit the summary buffer to just show some
6358 subset of the articles currently in the group. The effect most limit
6359 commands have is to remove a few (or many) articles from the summary
6362 All limiting commands work on subsets of the articles already fetched
6363 from the servers. None of these commands query the server for
6364 additional articles.
6370 @kindex / / (Summary)
6371 @findex gnus-summary-limit-to-subject
6372 Limit the summary buffer to articles that match some subject
6373 (@code{gnus-summary-limit-to-subject}). If given a prefix, exclude
6377 @kindex / a (Summary)
6378 @findex gnus-summary-limit-to-author
6379 Limit the summary buffer to articles that match some author
6380 (@code{gnus-summary-limit-to-author}). If given a prefix, exclude
6384 @kindex / R (Summary)
6385 @findex gnus-summary-limit-to-recipient
6386 Limit the summary buffer to articles that match some recipient
6387 (@code{gnus-summary-limit-to-recipient}). If given a prefix, exclude
6391 @kindex / x (Summary)
6392 @findex gnus-summary-limit-to-extra
6393 Limit the summary buffer to articles that match one of the ``extra''
6394 headers (@pxref{To From Newsgroups})
6395 (@code{gnus-summary-limit-to-extra}). If given a prefix, exclude
6400 @kindex / u (Summary)
6402 @findex gnus-summary-limit-to-unread
6403 Limit the summary buffer to articles not marked as read
6404 (@code{gnus-summary-limit-to-unread}). If given a prefix, limit the
6405 buffer to articles strictly unread. This means that ticked and
6406 dormant articles will also be excluded.
6409 @kindex / m (Summary)
6410 @findex gnus-summary-limit-to-marks
6411 Ask for a mark and then limit to all articles that have been marked
6412 with that mark (@code{gnus-summary-limit-to-marks}).
6415 @kindex / t (Summary)
6416 @findex gnus-summary-limit-to-age
6417 Ask for a number and then limit the summary buffer to articles older than (or equal to) that number of days
6418 (@code{gnus-summary-limit-to-age}). If given a prefix, limit to
6419 articles younger than that number of days.
6422 @kindex / n (Summary)
6423 @findex gnus-summary-limit-to-articles
6424 Limit the summary buffer to the current article
6425 (@code{gnus-summary-limit-to-articles}). Uses the process/prefix
6426 convention (@pxref{Process/Prefix}).
6429 @kindex / w (Summary)
6430 @findex gnus-summary-pop-limit
6431 Pop the previous limit off the stack and restore it
6432 (@code{gnus-summary-pop-limit}). If given a prefix, pop all limits off
6436 @kindex / . (Summary)
6437 @findex gnus-summary-limit-to-unseen
6438 Limit the summary buffer to the unseen articles
6439 (@code{gnus-summary-limit-to-unseen}).
6442 @kindex / v (Summary)
6443 @findex gnus-summary-limit-to-score
6444 Limit the summary buffer to articles that have a score at or above some
6445 score (@code{gnus-summary-limit-to-score}).
6448 @kindex / p (Summary)
6449 @findex gnus-summary-limit-to-display-predicate
6450 Limit the summary buffer to articles that satisfy the @code{display}
6451 group parameter predicate
6452 (@code{gnus-summary-limit-to-display-predicate}). @xref{Group
6453 Parameters}, for more on this predicate.
6456 @kindex / r (Summary)
6457 @findex gnus-summary-limit-to-replied
6458 Limit the summary buffer to replied articles
6459 (@code{gnus-summary-limit-to-replied}). If given a prefix, exclude
6464 @kindex M S (Summary)
6465 @kindex / E (Summary)
6466 @findex gnus-summary-limit-include-expunged
6467 Include all expunged articles in the limit
6468 (@code{gnus-summary-limit-include-expunged}).
6471 @kindex / D (Summary)
6472 @findex gnus-summary-limit-include-dormant
6473 Include all dormant articles in the limit
6474 (@code{gnus-summary-limit-include-dormant}).
6477 @kindex / * (Summary)
6478 @findex gnus-summary-limit-include-cached
6479 Include all cached articles in the limit
6480 (@code{gnus-summary-limit-include-cached}).
6483 @kindex / d (Summary)
6484 @findex gnus-summary-limit-exclude-dormant
6485 Exclude all dormant articles from the limit
6486 (@code{gnus-summary-limit-exclude-dormant}).
6489 @kindex / M (Summary)
6490 @findex gnus-summary-limit-exclude-marks
6491 Exclude all marked articles (@code{gnus-summary-limit-exclude-marks}).
6494 @kindex / T (Summary)
6495 @findex gnus-summary-limit-include-thread
6496 Include all the articles in the current thread in the limit.
6499 @kindex / c (Summary)
6500 @findex gnus-summary-limit-exclude-childless-dormant
6501 Exclude all dormant articles that have no children from the limit@*
6502 (@code{gnus-summary-limit-exclude-childless-dormant}).
6505 @kindex / C (Summary)
6506 @findex gnus-summary-limit-mark-excluded-as-read
6507 Mark all excluded unread articles as read
6508 (@code{gnus-summary-limit-mark-excluded-as-read}). If given a prefix,
6509 also mark excluded ticked and dormant articles as read.
6512 @kindex / N (Summary)
6513 @findex gnus-summary-insert-new-articles
6514 Insert all new articles in the summary buffer. It scans for new emails
6515 if @var{back-end}@code{-get-new-mail} is non-@code{nil}.
6518 @kindex / o (Summary)
6519 @findex gnus-summary-insert-old-articles
6520 Insert all old articles in the summary buffer. If given a numbered
6521 prefix, fetch this number of articles.
6529 @cindex article threading
6531 Gnus threads articles by default. @dfn{To thread} is to put responses
6532 to articles directly after the articles they respond to---in a
6533 hierarchical fashion.
6535 Threading is done by looking at the @code{References} headers of the
6536 articles. In a perfect world, this would be enough to build pretty
6537 trees, but unfortunately, the @code{References} header is often broken
6538 or simply missing. Weird news propagation exacerbates the problem,
6539 so one has to employ other heuristics to get pleasing results. A
6540 plethora of approaches exists, as detailed in horrible detail in
6541 @ref{Customizing Threading}.
6543 First, a quick overview of the concepts:
6547 The top-most article in a thread; the first article in the thread.
6550 A tree-like article structure.
6553 A small(er) section of this tree-like structure.
6556 Threads often lose their roots due to article expiry, or due to the root
6557 already having been read in a previous session, and not displayed in the
6558 summary buffer. We then typically have many sub-threads that really
6559 belong to one thread, but are without connecting roots. These are
6560 called loose threads.
6562 @item thread gathering
6563 An attempt to gather loose threads into bigger threads.
6565 @item sparse threads
6566 A thread where the missing articles have been ``guessed'' at, and are
6567 displayed as empty lines in the summary buffer.
6573 * Customizing Threading:: Variables you can change to affect the threading.
6574 * Thread Commands:: Thread based commands in the summary buffer.
6578 @node Customizing Threading
6579 @subsection Customizing Threading
6580 @cindex customizing threading
6583 * Loose Threads:: How Gnus gathers loose threads into bigger threads.
6584 * Filling In Threads:: Making the threads displayed look fuller.
6585 * More Threading:: Even more variables for fiddling with threads.
6586 * Low-Level Threading:: You thought it was over@dots{} but you were wrong!
6591 @subsubsection Loose Threads
6594 @cindex loose threads
6597 @item gnus-summary-make-false-root
6598 @vindex gnus-summary-make-false-root
6599 If non-@code{nil}, Gnus will gather all loose subtrees into one big tree
6600 and create a dummy root at the top. (Wait a minute. Root at the top?
6601 Yup.) Loose subtrees occur when the real root has expired, or you've
6602 read or killed the root in a previous session.
6604 When there is no real root of a thread, Gnus will have to fudge
6605 something. This variable says what fudging method Gnus should use.
6606 There are four possible values:
6610 \gnusfigure{The Summary Buffer}{390}{
6611 \put(0,0){\epsfig{figure=ps/summary-adopt,width=7.5cm}}
6612 \put(445,0){\makebox(0,0)[br]{\epsfig{figure=ps/summary-empty,width=7.5cm}}}
6613 \put(0,400){\makebox(0,0)[tl]{\epsfig{figure=ps/summary-none,width=7.5cm}}}
6614 \put(445,400){\makebox(0,0)[tr]{\epsfig{figure=ps/summary-dummy,width=7.5cm}}}
6619 @cindex adopting articles
6624 Gnus will make the first of the orphaned articles the parent. This
6625 parent will adopt all the other articles. The adopted articles will be
6626 marked as such by pointy brackets (@samp{<>}) instead of the standard
6627 square brackets (@samp{[]}). This is the default method.
6630 @vindex gnus-summary-dummy-line-format
6631 @vindex gnus-summary-make-false-root-always
6632 Gnus will create a dummy summary line that will pretend to be the
6633 parent. This dummy line does not correspond to any real article, so
6634 selecting it will just select the first real article after the dummy
6635 article. @code{gnus-summary-dummy-line-format} is used to specify the
6636 format of the dummy roots. It accepts only one format spec: @samp{S},
6637 which is the subject of the article. @xref{Formatting Variables}.
6638 If you want all threads to have a dummy root, even the non-gathered
6639 ones, set @code{gnus-summary-make-false-root-always} to @code{t}.
6642 Gnus won't actually make any article the parent, but simply leave the
6643 subject field of all orphans except the first empty. (Actually, it will
6644 use @code{gnus-summary-same-subject} as the subject (@pxref{Summary
6648 Don't make any article parent at all. Just gather the threads and
6649 display them after one another.
6652 Don't gather loose threads.
6655 @item gnus-summary-gather-subject-limit
6656 @vindex gnus-summary-gather-subject-limit
6657 Loose threads are gathered by comparing subjects of articles. If this
6658 variable is @code{nil}, Gnus requires an exact match between the
6659 subjects of the loose threads before gathering them into one big
6660 super-thread. This might be too strict a requirement, what with the
6661 presence of stupid newsreaders that chop off long subject lines. If
6662 you think so, set this variable to, say, 20 to require that only the
6663 first 20 characters of the subjects have to match. If you set this
6664 variable to a really low number, you'll find that Gnus will gather
6665 everything in sight into one thread, which isn't very helpful.
6667 @cindex fuzzy article gathering
6668 If you set this variable to the special value @code{fuzzy}, Gnus will
6669 use a fuzzy string comparison algorithm on the subjects (@pxref{Fuzzy
6672 @item gnus-simplify-subject-fuzzy-regexp
6673 @vindex gnus-simplify-subject-fuzzy-regexp
6674 This can either be a regular expression or list of regular expressions
6675 that match strings that will be removed from subjects if fuzzy subject
6676 simplification is used.
6678 @item gnus-simplify-ignored-prefixes
6679 @vindex gnus-simplify-ignored-prefixes
6680 If you set @code{gnus-summary-gather-subject-limit} to something as low
6681 as 10, you might consider setting this variable to something sensible:
6683 @c Written by Michael Ernst <mernst@cs.rice.edu>
6685 (setq gnus-simplify-ignored-prefixes
6691 "wanted" "followup" "summary\\( of\\)?"
6692 "help" "query" "problem" "question"
6693 "answer" "reference" "announce"
6694 "How can I" "How to" "Comparison of"
6699 (mapconcat 'identity
6700 '("for" "for reference" "with" "about")
6702 "\\)?\\]?:?[ \t]*"))
6705 All words that match this regexp will be removed before comparing two
6708 @item gnus-simplify-subject-functions
6709 @vindex gnus-simplify-subject-functions
6710 If non-@code{nil}, this variable overrides
6711 @code{gnus-summary-gather-subject-limit}. This variable should be a
6712 list of functions to apply to the @code{Subject} string iteratively to
6713 arrive at the simplified version of the string.
6715 Useful functions to put in this list include:
6718 @item gnus-simplify-subject-re
6719 @findex gnus-simplify-subject-re
6720 Strip the leading @samp{Re:}.
6722 @item gnus-simplify-subject-fuzzy
6723 @findex gnus-simplify-subject-fuzzy
6726 @item gnus-simplify-whitespace
6727 @findex gnus-simplify-whitespace
6728 Remove excessive whitespace.
6730 @item gnus-simplify-all-whitespace
6731 @findex gnus-simplify-all-whitespace
6732 Remove all whitespace.
6735 You may also write your own functions, of course.
6738 @item gnus-summary-gather-exclude-subject
6739 @vindex gnus-summary-gather-exclude-subject
6740 Since loose thread gathering is done on subjects only, that might lead
6741 to many false hits, especially with certain common subjects like
6742 @samp{} and @samp{(none)}. To make the situation slightly better,
6743 you can use the regexp @code{gnus-summary-gather-exclude-subject} to say
6744 what subjects should be excluded from the gathering process.@*
6745 The default is @samp{^ *$\\|^(none)$}.
6747 @item gnus-summary-thread-gathering-function
6748 @vindex gnus-summary-thread-gathering-function
6749 Gnus gathers threads by looking at @code{Subject} headers. This means
6750 that totally unrelated articles may end up in the same ``thread'', which
6751 is confusing. An alternate approach is to look at all the
6752 @code{Message-ID}s in all the @code{References} headers to find matches.
6753 This will ensure that no gathered threads ever include unrelated
6754 articles, but it also means that people who have posted with broken
6755 newsreaders won't be gathered properly. The choice is yours---plague or
6759 @item gnus-gather-threads-by-subject
6760 @findex gnus-gather-threads-by-subject
6761 This function is the default gathering function and looks at
6762 @code{Subject}s exclusively.
6764 @item gnus-gather-threads-by-references
6765 @findex gnus-gather-threads-by-references
6766 This function looks at @code{References} headers exclusively.
6769 If you want to test gathering by @code{References}, you could say
6773 (setq gnus-summary-thread-gathering-function
6774 'gnus-gather-threads-by-references)
6780 @node Filling In Threads
6781 @subsubsection Filling In Threads
6784 @item gnus-fetch-old-headers
6785 @vindex gnus-fetch-old-headers
6786 If non-@code{nil}, Gnus will attempt to build old threads by fetching
6787 more old headers---headers to articles marked as read. If you would
6788 like to display as few summary lines as possible, but still connect as
6789 many loose threads as possible, you should set this variable to
6790 @code{some} or a number. If you set it to a number, no more than that
6791 number of extra old headers will be fetched. In either case, fetching
6792 old headers only works if the back end you are using carries overview
6793 files---this would normally be @code{nntp}, @code{nnspool},
6794 @code{nnml}, and @code{nnmaildir}. Also remember that if the root of
6795 the thread has been expired by the server, there's not much Gnus can
6798 This variable can also be set to @code{invisible}. This won't have any
6799 visible effects, but is useful if you use the @kbd{A T} command a lot
6800 (@pxref{Finding the Parent}).
6802 @item gnus-fetch-old-ephemeral-headers
6803 @vindex gnus-fetch-old-ephemeral-headers
6804 Same as @code{gnus-fetch-old-headers}, but only used for ephemeral
6807 @item gnus-build-sparse-threads
6808 @vindex gnus-build-sparse-threads
6809 Fetching old headers can be slow. A low-rent similar effect can be
6810 gotten by setting this variable to @code{some}. Gnus will then look at
6811 the complete @code{References} headers of all articles and try to string
6812 together articles that belong in the same thread. This will leave
6813 @dfn{gaps} in the threading display where Gnus guesses that an article
6814 is missing from the thread. (These gaps appear like normal summary
6815 lines. If you select a gap, Gnus will try to fetch the article in
6816 question.) If this variable is @code{t}, Gnus will display all these
6817 ``gaps'' without regard for whether they are useful for completing the
6818 thread or not. Finally, if this variable is @code{more}, Gnus won't cut
6819 off sparse leaf nodes that don't lead anywhere. This variable is
6820 @code{nil} by default.
6822 @item gnus-read-all-available-headers
6823 @vindex gnus-read-all-available-headers
6824 This is a rather obscure variable that few will find useful. It's
6825 intended for those non-news newsgroups where the back end has to fetch
6826 quite a lot to present the summary buffer, and where it's impossible to
6827 go back to parents of articles. This is mostly the case in the
6828 web-based groups, like the @code{nnultimate} groups.
6830 If you don't use those, then it's safe to leave this as the default
6831 @code{nil}. If you want to use this variable, it should be a regexp
6832 that matches the group name, or @code{t} for all groups.
6837 @node More Threading
6838 @subsubsection More Threading
6841 @item gnus-show-threads
6842 @vindex gnus-show-threads
6843 If this variable is @code{nil}, no threading will be done, and all of
6844 the rest of the variables here will have no effect. Turning threading
6845 off will speed group selection up a bit, but it is sure to make reading
6846 slower and more awkward.
6848 @item gnus-thread-hide-subtree
6849 @vindex gnus-thread-hide-subtree
6850 If non-@code{nil}, all threads will be hidden when the summary buffer is
6853 This can also be a predicate specifier (@pxref{Predicate Specifiers}).
6854 Available predicates are @code{gnus-article-unread-p} and
6855 @code{gnus-article-unseen-p}.
6860 (setq gnus-thread-hide-subtree
6861 '(or gnus-article-unread-p
6862 gnus-article-unseen-p))
6865 (It's a pretty nonsensical example, since all unseen articles are also
6866 unread, but you get my drift.)
6869 @item gnus-thread-expunge-below
6870 @vindex gnus-thread-expunge-below
6871 All threads that have a total score (as defined by
6872 @code{gnus-thread-score-function}) less than this number will be
6873 expunged. This variable is @code{nil} by default, which means that no
6874 threads are expunged.
6876 @item gnus-thread-hide-killed
6877 @vindex gnus-thread-hide-killed
6878 if you kill a thread and this variable is non-@code{nil}, the subtree
6881 @item gnus-thread-ignore-subject
6882 @vindex gnus-thread-ignore-subject
6883 Sometimes somebody changes the subject in the middle of a thread. If
6884 this variable is non-@code{nil}, which is the default, the subject
6885 change is ignored. If it is @code{nil}, a change in the subject will
6886 result in a new thread.
6888 @item gnus-thread-indent-level
6889 @vindex gnus-thread-indent-level
6890 This is a number that says how much each sub-thread should be indented.
6893 @item gnus-sort-gathered-threads-function
6894 @vindex gnus-sort-gathered-threads-function
6895 Sometimes, particularly with mailing lists, the order in which mails
6896 arrive locally is not necessarily the same as the order in which they
6897 arrived on the mailing list. Consequently, when sorting sub-threads
6898 using the default @code{gnus-thread-sort-by-number}, responses can end
6899 up appearing before the article to which they are responding to.
6900 Setting this variable to an alternate value
6901 (e.g. @code{gnus-thread-sort-by-date}), in a group's parameters or in an
6902 appropriate hook (e.g. @code{gnus-summary-generate-hook}) can produce a
6903 more logical sub-thread ordering in such instances.
6908 @node Low-Level Threading
6909 @subsubsection Low-Level Threading
6913 @item gnus-parse-headers-hook
6914 @vindex gnus-parse-headers-hook
6915 Hook run before parsing any headers.
6917 @item gnus-alter-header-function
6918 @vindex gnus-alter-header-function
6919 If non-@code{nil}, this function will be called to allow alteration of
6920 article header structures. The function is called with one parameter,
6921 the article header vector, which it may alter in any way. For instance,
6922 if you have a mail-to-news gateway which alters the @code{Message-ID}s
6923 in systematic ways (by adding prefixes and such), you can use this
6924 variable to un-scramble the @code{Message-ID}s so that they are more
6925 meaningful. Here's one example:
6928 (setq gnus-alter-header-function 'my-alter-message-id)
6930 (defun my-alter-message-id (header)
6931 (let ((id (mail-header-id header)))
6933 "\\(<[^<>@@]*\\)\\.?cygnus\\..*@@\\([^<>@@]*>\\)" id)
6935 (concat (match-string 1 id) "@@" (match-string 2 id))
6942 @node Thread Commands
6943 @subsection Thread Commands
6944 @cindex thread commands
6950 @kindex T k (Summary)
6951 @kindex C-M-k (Summary)
6952 @findex gnus-summary-kill-thread
6953 Mark all articles in the current (sub-)thread as read
6954 (@code{gnus-summary-kill-thread}). If the prefix argument is positive,
6955 remove all marks instead. If the prefix argument is negative, tick
6960 @kindex T l (Summary)
6961 @kindex C-M-l (Summary)
6962 @findex gnus-summary-lower-thread
6963 Lower the score of the current (sub-)thread
6964 (@code{gnus-summary-lower-thread}).
6967 @kindex T i (Summary)
6968 @findex gnus-summary-raise-thread
6969 Increase the score of the current (sub-)thread
6970 (@code{gnus-summary-raise-thread}).
6973 @kindex T # (Summary)
6974 @findex gnus-uu-mark-thread
6975 Set the process mark on the current (sub-)thread
6976 (@code{gnus-uu-mark-thread}).
6979 @kindex T M-# (Summary)
6980 @findex gnus-uu-unmark-thread
6981 Remove the process mark from the current (sub-)thread
6982 (@code{gnus-uu-unmark-thread}).
6985 @kindex T T (Summary)
6986 @findex gnus-summary-toggle-threads
6987 Toggle threading (@code{gnus-summary-toggle-threads}).
6990 @kindex T s (Summary)
6991 @findex gnus-summary-show-thread
6992 Expose the (sub-)thread hidden under the current article, if any@*
6993 (@code{gnus-summary-show-thread}).
6996 @kindex T h (Summary)
6997 @findex gnus-summary-hide-thread
6998 Hide the current (sub-)thread (@code{gnus-summary-hide-thread}).
7001 @kindex T S (Summary)
7002 @findex gnus-summary-show-all-threads
7003 Expose all hidden threads (@code{gnus-summary-show-all-threads}).
7006 @kindex T H (Summary)
7007 @findex gnus-summary-hide-all-threads
7008 Hide all threads (@code{gnus-summary-hide-all-threads}).
7011 @kindex T t (Summary)
7012 @findex gnus-summary-rethread-current
7013 Re-thread the current article's thread
7014 (@code{gnus-summary-rethread-current}). This works even when the
7015 summary buffer is otherwise unthreaded.
7018 @kindex T ^ (Summary)
7019 @findex gnus-summary-reparent-thread
7020 Make the current article the child of the marked (or previous) article
7021 (@code{gnus-summary-reparent-thread}).
7024 @kindex T M-^ (Summary)
7025 @findex gnus-summary-reparent-children
7026 Make the current article the parent of the marked articles
7027 (@code{gnus-summary-reparent-children}).
7031 The following commands are thread movement commands. They all
7032 understand the numeric prefix.
7037 @kindex T n (Summary)
7039 @kindex C-M-n (Summary)
7041 @kindex M-down (Summary)
7042 @findex gnus-summary-next-thread
7043 Go to the next thread (@code{gnus-summary-next-thread}).
7046 @kindex T p (Summary)
7048 @kindex C-M-p (Summary)
7050 @kindex M-up (Summary)
7051 @findex gnus-summary-prev-thread
7052 Go to the previous thread (@code{gnus-summary-prev-thread}).
7055 @kindex T d (Summary)
7056 @findex gnus-summary-down-thread
7057 Descend the thread (@code{gnus-summary-down-thread}).
7060 @kindex T u (Summary)
7061 @findex gnus-summary-up-thread
7062 Ascend the thread (@code{gnus-summary-up-thread}).
7065 @kindex T o (Summary)
7066 @findex gnus-summary-top-thread
7067 Go to the top of the thread (@code{gnus-summary-top-thread}).
7070 @vindex gnus-thread-operation-ignore-subject
7071 If you ignore subject while threading, you'll naturally end up with
7072 threads that have several different subjects in them. If you then issue
7073 a command like @kbd{T k} (@code{gnus-summary-kill-thread}) you might not
7074 wish to kill the entire thread, but just those parts of the thread that
7075 have the same subject as the current article. If you like this idea,
7076 you can fiddle with @code{gnus-thread-operation-ignore-subject}. If it
7077 is non-@code{nil} (which it is by default), subjects will be ignored
7078 when doing thread commands. If this variable is @code{nil}, articles in
7079 the same thread with different subjects will not be included in the
7080 operation in question. If this variable is @code{fuzzy}, only articles
7081 that have subjects fuzzily equal will be included (@pxref{Fuzzy
7085 @node Sorting the Summary Buffer
7086 @section Sorting the Summary Buffer
7088 @findex gnus-thread-sort-by-total-score
7089 @findex gnus-thread-sort-by-date
7090 @findex gnus-thread-sort-by-date-reverse
7091 @findex gnus-thread-sort-by-score
7092 @findex gnus-thread-sort-by-subject
7093 @findex gnus-thread-sort-by-author
7094 @findex gnus-thread-sort-by-recipient
7095 @findex gnus-thread-sort-by-number
7096 @findex gnus-thread-sort-by-random
7097 @vindex gnus-thread-sort-functions
7098 @findex gnus-thread-sort-by-most-recent-number
7099 @findex gnus-thread-sort-by-most-recent-date
7100 If you are using a threaded summary display, you can sort the threads by
7101 setting @code{gnus-thread-sort-functions}, which can be either a single
7102 function, a list of functions, or a list containing functions and
7103 @code{(not some-function)} elements.
7105 By default, sorting is done on article numbers. Ready-made sorting
7106 predicate functions include @code{gnus-thread-sort-by-number},
7107 @code{gnus-thread-sort-by-author}, @code{gnus-thread-sort-by-recipient},
7108 @code{gnus-thread-sort-by-subject},
7109 @code{gnus-thread-sort-by-date}, @code{gnus-thread-sort-by-date-reverse},
7110 @code{gnus-thread-sort-by-score},
7111 @code{gnus-thread-sort-by-most-recent-number},
7112 @code{gnus-thread-sort-by-most-recent-date},
7113 @code{gnus-thread-sort-by-random} and
7114 @code{gnus-thread-sort-by-total-score}.
7116 Each function takes two threads and returns non-@code{nil} if the first
7117 thread should be sorted before the other. Note that sorting really is
7118 normally done by looking only at the roots of each thread.
7120 If you use more than one function, the primary sort key should be the
7121 last function in the list. You should probably always include
7122 @code{gnus-thread-sort-by-number} in the list of sorting
7123 functions---preferably first. This will ensure that threads that are
7124 equal with respect to the other sort criteria will be displayed in
7125 ascending article order.
7127 If you would like to sort by reverse score, then by subject, and finally
7128 by number, you could do something like:
7131 (setq gnus-thread-sort-functions
7132 '(gnus-thread-sort-by-number
7133 gnus-thread-sort-by-subject
7134 (not gnus-thread-sort-by-total-score)))
7137 The threads that have highest score will be displayed first in the
7138 summary buffer. When threads have the same score, they will be sorted
7139 alphabetically. The threads that have the same score and the same
7140 subject will be sorted by number, which is (normally) the sequence in
7141 which the articles arrived.
7143 If you want to sort by score and then reverse arrival order, you could
7147 (setq gnus-thread-sort-functions
7148 '((not gnus-thread-sort-by-number)
7149 gnus-thread-sort-by-score))
7152 @vindex gnus-thread-score-function
7153 The function in the @code{gnus-thread-score-function} variable (default
7154 @code{+}) is used for calculating the total score of a thread. Useful
7155 functions might be @code{max}, @code{min}, or squared means, or whatever
7158 @findex gnus-article-sort-functions
7159 @findex gnus-article-sort-by-date
7160 @findex gnus-article-sort-by-score
7161 @findex gnus-article-sort-by-subject
7162 @findex gnus-article-sort-by-author
7163 @findex gnus-article-sort-by-random
7164 @findex gnus-article-sort-by-number
7165 If you are using an unthreaded display for some strange reason or
7166 other, you have to fiddle with the @code{gnus-article-sort-functions}
7167 variable. It is very similar to the
7168 @code{gnus-thread-sort-functions}, except that it uses slightly
7169 different functions for article comparison. Available sorting
7170 predicate functions are @code{gnus-article-sort-by-number},
7171 @code{gnus-article-sort-by-author},
7172 @code{gnus-article-sort-by-subject}, @code{gnus-article-sort-by-date},
7173 @code{gnus-article-sort-by-random}, and
7174 @code{gnus-article-sort-by-score}.
7176 If you want to sort an unthreaded summary display by subject, you could
7180 (setq gnus-article-sort-functions
7181 '(gnus-article-sort-by-number
7182 gnus-article-sort-by-subject))
7185 You can define group specific sorting via @code{gnus-parameters},
7186 @xref{Group Parameters}.
7189 @node Asynchronous Fetching
7190 @section Asynchronous Article Fetching
7191 @cindex asynchronous article fetching
7192 @cindex article pre-fetch
7195 If you read your news from an @acronym{NNTP} server that's far away, the
7196 network latencies may make reading articles a chore. You have to wait
7197 for a while after pressing @kbd{n} to go to the next article before the
7198 article appears. Why can't Gnus just go ahead and fetch the article
7199 while you are reading the previous one? Why not, indeed.
7201 First, some caveats. There are some pitfalls to using asynchronous
7202 article fetching, especially the way Gnus does it.
7204 Let's say you are reading article 1, which is short, and article 2 is
7205 quite long, and you are not interested in reading that. Gnus does not
7206 know this, so it goes ahead and fetches article 2. You decide to read
7207 article 3, but since Gnus is in the process of fetching article 2, the
7208 connection is blocked.
7210 To avoid these situations, Gnus will open two (count 'em two)
7211 connections to the server. Some people may think this isn't a very nice
7212 thing to do, but I don't see any real alternatives. Setting up that
7213 extra connection takes some time, so Gnus startup will be slower.
7215 Gnus will fetch more articles than you will read. This will mean that
7216 the link between your machine and the @acronym{NNTP} server will become more
7217 loaded than if you didn't use article pre-fetch. The server itself will
7218 also become more loaded---both with the extra article requests, and the
7221 Ok, so now you know that you shouldn't really use this thing@dots{} unless
7224 @vindex gnus-asynchronous
7225 Here's how: Set @code{gnus-asynchronous} to @code{t}. The rest should
7226 happen automatically.
7228 @vindex gnus-use-article-prefetch
7229 You can control how many articles are to be pre-fetched by setting
7230 @code{gnus-use-article-prefetch}. This is 30 by default, which means
7231 that when you read an article in the group, the back end will pre-fetch
7232 the next 30 articles. If this variable is @code{t}, the back end will
7233 pre-fetch all the articles it can without bound. If it is
7234 @code{nil}, no pre-fetching will be done.
7236 @vindex gnus-async-prefetch-article-p
7237 @findex gnus-async-read-p
7238 There are probably some articles that you don't want to pre-fetch---read
7239 articles, for instance. The @code{gnus-async-prefetch-article-p}
7240 variable controls whether an article is to be pre-fetched. This
7241 function should return non-@code{nil} when the article in question is
7242 to be pre-fetched. The default is @code{gnus-async-read-p}, which
7243 returns @code{nil} on read articles. The function is called with an
7244 article data structure as the only parameter.
7246 If, for instance, you wish to pre-fetch only unread articles shorter
7247 than 100 lines, you could say something like:
7250 (defun my-async-short-unread-p (data)
7251 "Return non-nil for short, unread articles."
7252 (and (gnus-data-unread-p data)
7253 (< (mail-header-lines (gnus-data-header data))
7256 (setq gnus-async-prefetch-article-p 'my-async-short-unread-p)
7259 These functions will be called many, many times, so they should
7260 preferably be short and sweet to avoid slowing down Gnus too much.
7261 It's probably a good idea to byte-compile things like this.
7263 @vindex gnus-prefetched-article-deletion-strategy
7264 Articles have to be removed from the asynch buffer sooner or later. The
7265 @code{gnus-prefetched-article-deletion-strategy} says when to remove
7266 articles. This is a list that may contain the following elements:
7270 Remove articles when they are read.
7273 Remove articles when exiting the group.
7276 The default value is @code{(read exit)}.
7278 @c @vindex gnus-use-header-prefetch
7279 @c If @code{gnus-use-header-prefetch} is non-@code{nil}, prefetch articles
7280 @c from the next group.
7283 @node Article Caching
7284 @section Article Caching
7285 @cindex article caching
7288 If you have an @emph{extremely} slow @acronym{NNTP} connection, you may
7289 consider turning article caching on. Each article will then be stored
7290 locally under your home directory. As you may surmise, this could
7291 potentially use @emph{huge} amounts of disk space, as well as eat up all
7292 your inodes so fast it will make your head swim. In vodka.
7294 Used carefully, though, it could be just an easier way to save articles.
7296 @vindex gnus-use-long-file-name
7297 @vindex gnus-cache-directory
7298 @vindex gnus-use-cache
7299 To turn caching on, set @code{gnus-use-cache} to @code{t}. By default,
7300 all articles ticked or marked as dormant will then be copied
7301 over to your local cache (@code{gnus-cache-directory}). Whether this
7302 cache is flat or hierarchical is controlled by the
7303 @code{gnus-use-long-file-name} variable, as usual.
7305 When re-selecting a ticked or dormant article, it will be fetched from the
7306 cache instead of from the server. As articles in your cache will never
7307 expire, this might serve as a method of saving articles while still
7308 keeping them where they belong. Just mark all articles you want to save
7309 as dormant, and don't worry.
7311 When an article is marked as read, is it removed from the cache.
7313 @vindex gnus-cache-remove-articles
7314 @vindex gnus-cache-enter-articles
7315 The entering/removal of articles from the cache is controlled by the
7316 @code{gnus-cache-enter-articles} and @code{gnus-cache-remove-articles}
7317 variables. Both are lists of symbols. The first is @code{(ticked
7318 dormant)} by default, meaning that ticked and dormant articles will be
7319 put in the cache. The latter is @code{(read)} by default, meaning that
7320 articles marked as read are removed from the cache. Possibly
7321 symbols in these two lists are @code{ticked}, @code{dormant},
7322 @code{unread} and @code{read}.
7324 @findex gnus-jog-cache
7325 So where does the massive article-fetching and storing come into the
7326 picture? The @code{gnus-jog-cache} command will go through all
7327 subscribed newsgroups, request all unread articles, score them, and
7328 store them in the cache. You should only ever, ever ever ever, use this
7329 command if 1) your connection to the @acronym{NNTP} server is really, really,
7330 really slow and 2) you have a really, really, really huge disk.
7331 Seriously. One way to cut down on the number of articles downloaded is
7332 to score unwanted articles down and have them marked as read. They will
7333 not then be downloaded by this command.
7335 @vindex gnus-uncacheable-groups
7336 @vindex gnus-cacheable-groups
7337 It is likely that you do not want caching on all groups. For instance,
7338 if your @code{nnml} mail is located under your home directory, it makes no
7339 sense to cache it somewhere else under your home directory. Unless you
7340 feel that it's neat to use twice as much space.
7342 To limit the caching, you could set @code{gnus-cacheable-groups} to a
7343 regexp of groups to cache, @samp{^nntp} for instance, or set the
7344 @code{gnus-uncacheable-groups} regexp to @samp{^nnml}, for instance.
7345 Both variables are @code{nil} by default. If a group matches both
7346 variables, the group is not cached.
7348 @findex gnus-cache-generate-nov-databases
7349 @findex gnus-cache-generate-active
7350 @vindex gnus-cache-active-file
7351 The cache stores information on what articles it contains in its active
7352 file (@code{gnus-cache-active-file}). If this file (or any other parts
7353 of the cache) becomes all messed up for some reason or other, Gnus
7354 offers two functions that will try to set things right. @kbd{M-x
7355 gnus-cache-generate-nov-databases} will (re)build all the @acronym{NOV}
7356 files, and @kbd{gnus-cache-generate-active} will (re)generate the active
7359 @findex gnus-cache-move-cache
7360 @code{gnus-cache-move-cache} will move your whole
7361 @code{gnus-cache-directory} to some other location. You get asked to
7362 where, isn't that cool?
7364 @node Persistent Articles
7365 @section Persistent Articles
7366 @cindex persistent articles
7368 Closely related to article caching, we have @dfn{persistent articles}.
7369 In fact, it's just a different way of looking at caching, and much more
7370 useful in my opinion.
7372 Say you're reading a newsgroup, and you happen on to some valuable gem
7373 that you want to keep and treasure forever. You'd normally just save it
7374 (using one of the many saving commands) in some file. The problem with
7375 that is that it's just, well, yucky. Ideally you'd prefer just having
7376 the article remain in the group where you found it forever; untouched by
7377 the expiry going on at the news server.
7379 This is what a @dfn{persistent article} is---an article that just won't
7380 be deleted. It's implemented using the normal cache functions, but
7381 you use two explicit commands for managing persistent articles:
7387 @findex gnus-cache-enter-article
7388 Make the current article persistent (@code{gnus-cache-enter-article}).
7391 @kindex M-* (Summary)
7392 @findex gnus-cache-remove-article
7393 Remove the current article from the persistent articles
7394 (@code{gnus-cache-remove-article}). This will normally delete the
7398 Both these commands understand the process/prefix convention.
7400 To avoid having all ticked articles (and stuff) entered into the cache,
7401 you should set @code{gnus-use-cache} to @code{passive} if you're just
7402 interested in persistent articles:
7405 (setq gnus-use-cache 'passive)
7409 @node Article Backlog
7410 @section Article Backlog
7412 @cindex article backlog
7414 If you have a slow connection, but the idea of using caching seems
7415 unappealing to you (and it is, really), you can help the situation some
7416 by switching on the @dfn{backlog}. This is where Gnus will buffer
7417 already read articles so that it doesn't have to re-fetch articles
7418 you've already read. This only helps if you are in the habit of
7419 re-selecting articles you've recently read, of course. If you never do
7420 that, turning the backlog on will slow Gnus down a little bit, and
7421 increase memory usage some.
7423 @vindex gnus-keep-backlog
7424 If you set @code{gnus-keep-backlog} to a number @var{n}, Gnus will store
7425 at most @var{n} old articles in a buffer for later re-fetching. If this
7426 variable is non-@code{nil} and is not a number, Gnus will store
7427 @emph{all} read articles, which means that your Emacs will grow without
7428 bound before exploding and taking your machine down with you. I put
7429 that in there just to keep y'all on your toes.
7431 The default value is 20.
7434 @node Saving Articles
7435 @section Saving Articles
7436 @cindex saving articles
7438 Gnus can save articles in a number of ways. Below is the documentation
7439 for saving articles in a fairly straight-forward fashion (i.e., little
7440 processing of the article is done before it is saved). For a different
7441 approach (uudecoding, unsharing) you should use @code{gnus-uu}
7442 (@pxref{Decoding Articles}).
7444 For the commands listed here, the target is a file. If you want to
7445 save to a group, see the @kbd{B c} (@code{gnus-summary-copy-article})
7446 command (@pxref{Mail Group Commands}).
7448 @vindex gnus-save-all-headers
7449 If @code{gnus-save-all-headers} is non-@code{nil}, Gnus will not delete
7450 unwanted headers before saving the article.
7452 @vindex gnus-saved-headers
7453 If the preceding variable is @code{nil}, all headers that match the
7454 @code{gnus-saved-headers} regexp will be kept, while the rest will be
7455 deleted before saving.
7461 @kindex O o (Summary)
7463 @findex gnus-summary-save-article
7464 @c @icon{gnus-summary-save-article}
7465 Save the current article using the default article saver
7466 (@code{gnus-summary-save-article}).
7469 @kindex O m (Summary)
7470 @findex gnus-summary-save-article-mail
7471 Save the current article in mail format
7472 (@code{gnus-summary-save-article-mail}).
7475 @kindex O r (Summary)
7476 @findex gnus-summary-save-article-rmail
7477 Save the current article in Rmail format
7478 (@code{gnus-summary-save-article-rmail}).
7481 @kindex O f (Summary)
7482 @findex gnus-summary-save-article-file
7483 @c @icon{gnus-summary-save-article-file}
7484 Save the current article in plain file format
7485 (@code{gnus-summary-save-article-file}).
7488 @kindex O F (Summary)
7489 @findex gnus-summary-write-article-file
7490 Write the current article in plain file format, overwriting any previous
7491 file contents (@code{gnus-summary-write-article-file}).
7494 @kindex O b (Summary)
7495 @findex gnus-summary-save-article-body-file
7496 Save the current article body in plain file format
7497 (@code{gnus-summary-save-article-body-file}).
7500 @kindex O h (Summary)
7501 @findex gnus-summary-save-article-folder
7502 Save the current article in mh folder format
7503 (@code{gnus-summary-save-article-folder}).
7506 @kindex O v (Summary)
7507 @findex gnus-summary-save-article-vm
7508 Save the current article in a VM folder
7509 (@code{gnus-summary-save-article-vm}).
7513 @kindex O p (Summary)
7515 @findex gnus-summary-pipe-output
7516 Save the current article in a pipe. Uhm, like, what I mean is---Pipe
7517 the current article to a process (@code{gnus-summary-pipe-output}).
7518 If given a symbolic prefix (@pxref{Symbolic Prefixes}), include the
7519 complete headers in the piped output.
7522 @kindex O P (Summary)
7523 @findex gnus-summary-muttprint
7524 @vindex gnus-summary-muttprint-program
7525 Save the current article into muttprint. That is, print it using the
7526 external program @uref{http://muttprint.sourceforge.net/,
7527 Muttprint}. The program name and options to use is controlled by the
7528 variable @code{gnus-summary-muttprint-program}.
7529 (@code{gnus-summary-muttprint}).
7533 @vindex gnus-prompt-before-saving
7534 All these commands use the process/prefix convention
7535 (@pxref{Process/Prefix}). If you save bunches of articles using these
7536 functions, you might get tired of being prompted for files to save each
7537 and every article in. The prompting action is controlled by
7538 the @code{gnus-prompt-before-saving} variable, which is @code{always} by
7539 default, giving you that excessive prompting action you know and
7540 loathe. If you set this variable to @code{t} instead, you'll be prompted
7541 just once for each series of articles you save. If you like to really
7542 have Gnus do all your thinking for you, you can even set this variable
7543 to @code{nil}, which means that you will never be prompted for files to
7544 save articles in. Gnus will simply save all the articles in the default
7548 @vindex gnus-default-article-saver
7549 You can customize the @code{gnus-default-article-saver} variable to make
7550 Gnus do what you want it to. You can use any of the six ready-made
7551 functions below, or you can create your own.
7555 @item gnus-summary-save-in-rmail
7556 @findex gnus-summary-save-in-rmail
7557 @vindex gnus-rmail-save-name
7558 @findex gnus-plain-save-name
7559 This is the default format, @dfn{Babyl}. Uses the function in the
7560 @code{gnus-rmail-save-name} variable to get a file name to save the
7561 article in. The default is @code{gnus-plain-save-name}.
7563 @item gnus-summary-save-in-mail
7564 @findex gnus-summary-save-in-mail
7565 @vindex gnus-mail-save-name
7566 Save in a Unix mail (mbox) file. Uses the function in the
7567 @code{gnus-mail-save-name} variable to get a file name to save the
7568 article in. The default is @code{gnus-plain-save-name}.
7570 @item gnus-summary-save-in-file
7571 @findex gnus-summary-save-in-file
7572 @vindex gnus-file-save-name
7573 @findex gnus-numeric-save-name
7574 Append the article straight to an ordinary file. Uses the function in
7575 the @code{gnus-file-save-name} variable to get a file name to save the
7576 article in. The default is @code{gnus-numeric-save-name}.
7578 @item gnus-summary-write-to-file
7579 @findex gnus-summary-write-to-file
7580 Write the article straight to an ordinary file. The file is
7581 overwritten if it exists. Uses the function in the
7582 @code{gnus-file-save-name} variable to get a file name to save the
7583 article in. The default is @code{gnus-numeric-save-name}.
7585 @item gnus-summary-save-body-in-file
7586 @findex gnus-summary-save-body-in-file
7587 Append the article body to an ordinary file. Uses the function in the
7588 @code{gnus-file-save-name} variable to get a file name to save the
7589 article in. The default is @code{gnus-numeric-save-name}.
7591 @item gnus-summary-save-in-folder
7592 @findex gnus-summary-save-in-folder
7593 @findex gnus-folder-save-name
7594 @findex gnus-Folder-save-name
7595 @vindex gnus-folder-save-name
7598 Save the article to an MH folder using @code{rcvstore} from the MH
7599 library. Uses the function in the @code{gnus-folder-save-name} variable
7600 to get a file name to save the article in. The default is
7601 @code{gnus-folder-save-name}, but you can also use
7602 @code{gnus-Folder-save-name}, which creates capitalized names.
7604 @item gnus-summary-save-in-vm
7605 @findex gnus-summary-save-in-vm
7606 Save the article in a VM folder. You have to have the VM mail
7607 reader to use this setting.
7610 @vindex gnus-article-save-directory
7611 All of these functions, except for the last one, will save the article
7612 in the @code{gnus-article-save-directory}, which is initialized from the
7613 @env{SAVEDIR} environment variable. This is @file{~/News/} by
7616 As you can see above, the functions use different functions to find a
7617 suitable name of a file to save the article in. Below is a list of
7618 available functions that generate names:
7622 @item gnus-Numeric-save-name
7623 @findex gnus-Numeric-save-name
7624 File names like @file{~/News/Alt.andrea-dworkin/45}.
7626 @item gnus-numeric-save-name
7627 @findex gnus-numeric-save-name
7628 File names like @file{~/News/alt.andrea-dworkin/45}.
7630 @item gnus-Plain-save-name
7631 @findex gnus-Plain-save-name
7632 File names like @file{~/News/Alt.andrea-dworkin}.
7634 @item gnus-plain-save-name
7635 @findex gnus-plain-save-name
7636 File names like @file{~/News/alt.andrea-dworkin}.
7638 @item gnus-sender-save-name
7639 @findex gnus-sender-save-name
7640 File names like @file{~/News/larsi}.
7643 @vindex gnus-split-methods
7644 You can have Gnus suggest where to save articles by plonking a regexp into
7645 the @code{gnus-split-methods} alist. For instance, if you would like to
7646 save articles related to Gnus in the file @file{gnus-stuff}, and articles
7647 related to VM in @file{vm-stuff}, you could set this variable to something
7651 (("^Subject:.*gnus\\|^Newsgroups:.*gnus" "gnus-stuff")
7652 ("^Subject:.*vm\\|^Xref:.*vm" "vm-stuff")
7653 (my-choosing-function "../other-dir/my-stuff")
7654 ((equal gnus-newsgroup-name "mail.misc") "mail-stuff"))
7657 We see that this is a list where each element is a list that has two
7658 elements---the @dfn{match} and the @dfn{file}. The match can either be
7659 a string (in which case it is used as a regexp to match on the article
7660 head); it can be a symbol (which will be called as a function with the
7661 group name as a parameter); or it can be a list (which will be
7662 @code{eval}ed). If any of these actions have a non-@code{nil} result,
7663 the @dfn{file} will be used as a default prompt. In addition, the
7664 result of the operation itself will be used if the function or form
7665 called returns a string or a list of strings.
7667 You basically end up with a list of file names that might be used when
7668 saving the current article. (All ``matches'' will be used.) You will
7669 then be prompted for what you really want to use as a name, with file
7670 name completion over the results from applying this variable.
7672 This variable is @code{((gnus-article-archive-name))} by default, which
7673 means that Gnus will look at the articles it saves for an
7674 @code{Archive-name} line and use that as a suggestion for the file
7677 Here's an example function to clean up file names somewhat. If you have
7678 lots of mail groups called things like
7679 @samp{nnml:mail.whatever}, you may want to chop off the beginning of
7680 these group names before creating the file name to save to. The
7681 following will do just that:
7684 (defun my-save-name (group)
7685 (when (string-match "^nnml:mail." group)
7686 (substring group (match-end 0))))
7688 (setq gnus-split-methods
7689 '((gnus-article-archive-name)
7694 @vindex gnus-use-long-file-name
7695 Finally, you have the @code{gnus-use-long-file-name} variable. If it is
7696 @code{nil}, all the preceding functions will replace all periods
7697 (@samp{.}) in the group names with slashes (@samp{/})---which means that
7698 the functions will generate hierarchies of directories instead of having
7699 all the files in the top level directory
7700 (@file{~/News/alt/andrea-dworkin} instead of
7701 @file{~/News/alt.andrea-dworkin}.) This variable is @code{t} by default
7702 on most systems. However, for historical reasons, this is @code{nil} on
7703 Xenix and usg-unix-v machines by default.
7705 This function also affects kill and score file names. If this variable
7706 is a list, and the list contains the element @code{not-score}, long file
7707 names will not be used for score files, if it contains the element
7708 @code{not-save}, long file names will not be used for saving, and if it
7709 contains the element @code{not-kill}, long file names will not be used
7712 If you'd like to save articles in a hierarchy that looks something like
7716 (setq gnus-use-long-file-name '(not-save)) ; @r{to get a hierarchy}
7717 (setq gnus-default-article-saver
7718 'gnus-summary-save-in-file) ; @r{no encoding}
7721 Then just save with @kbd{o}. You'd then read this hierarchy with
7722 ephemeral @code{nneething} groups---@kbd{G D} in the group buffer, and
7723 the top level directory as the argument (@file{~/News/}). Then just walk
7724 around to the groups/directories with @code{nneething}.
7727 @node Decoding Articles
7728 @section Decoding Articles
7729 @cindex decoding articles
7731 Sometime users post articles (or series of articles) that have been
7732 encoded in some way or other. Gnus can decode them for you.
7735 * Uuencoded Articles:: Uudecode articles.
7736 * Shell Archives:: Unshar articles.
7737 * PostScript Files:: Split PostScript.
7738 * Other Files:: Plain save and binhex.
7739 * Decoding Variables:: Variables for a happy decoding.
7740 * Viewing Files:: You want to look at the result of the decoding?
7744 @cindex article series
7745 All these functions use the process/prefix convention
7746 (@pxref{Process/Prefix}) for finding out what articles to work on, with
7747 the extension that a ``single article'' means ``a single series''. Gnus
7748 can find out by itself what articles belong to a series, decode all the
7749 articles and unpack/view/save the resulting file(s).
7751 Gnus guesses what articles are in the series according to the following
7752 simplish rule: The subjects must be (nearly) identical, except for the
7753 last two numbers of the line. (Spaces are largely ignored, however.)
7755 For example: If you choose a subject called @samp{cat.gif (2/3)}, Gnus
7756 will find all the articles that match the regexp @samp{^cat.gif
7757 ([0-9]+/[0-9]+).*$}.
7759 Subjects that are non-standard, like @samp{cat.gif (2/3) Part 6 of a
7760 series}, will not be properly recognized by any of the automatic viewing
7761 commands, and you have to mark the articles manually with @kbd{#}.
7764 @node Uuencoded Articles
7765 @subsection Uuencoded Articles
7767 @cindex uuencoded articles
7772 @kindex X u (Summary)
7773 @findex gnus-uu-decode-uu
7774 @c @icon{gnus-uu-decode-uu}
7775 Uudecodes the current series (@code{gnus-uu-decode-uu}).
7778 @kindex X U (Summary)
7779 @findex gnus-uu-decode-uu-and-save
7780 Uudecodes and saves the current series
7781 (@code{gnus-uu-decode-uu-and-save}).
7784 @kindex X v u (Summary)
7785 @findex gnus-uu-decode-uu-view
7786 Uudecodes and views the current series (@code{gnus-uu-decode-uu-view}).
7789 @kindex X v U (Summary)
7790 @findex gnus-uu-decode-uu-and-save-view
7791 Uudecodes, views and saves the current series
7792 (@code{gnus-uu-decode-uu-and-save-view}).
7796 Remember that these all react to the presence of articles marked with
7797 the process mark. If, for instance, you'd like to decode and save an
7798 entire newsgroup, you'd typically do @kbd{M P a}
7799 (@code{gnus-uu-mark-all}) and then @kbd{X U}
7800 (@code{gnus-uu-decode-uu-and-save}).
7802 All this is very much different from how @code{gnus-uu} worked with
7803 @sc{gnus 4.1}, where you had explicit keystrokes for everything under
7804 the sun. This version of @code{gnus-uu} generally assumes that you mark
7805 articles in some way (@pxref{Setting Process Marks}) and then press
7808 @vindex gnus-uu-notify-files
7809 Note: When trying to decode articles that have names matching
7810 @code{gnus-uu-notify-files}, which is hard-coded to
7811 @samp{[Cc][Ii][Nn][Dd][Yy][0-9]+.\\(gif\\|jpg\\)}, @code{gnus-uu} will
7812 automatically post an article on @samp{comp.unix.wizards} saying that
7813 you have just viewed the file in question. This feature can't be turned
7817 @node Shell Archives
7818 @subsection Shell Archives
7820 @cindex shell archives
7821 @cindex shared articles
7823 Shell archives (``shar files'') used to be a popular way to distribute
7824 sources, but it isn't used all that much today. In any case, we have
7825 some commands to deal with these:
7830 @kindex X s (Summary)
7831 @findex gnus-uu-decode-unshar
7832 Unshars the current series (@code{gnus-uu-decode-unshar}).
7835 @kindex X S (Summary)
7836 @findex gnus-uu-decode-unshar-and-save
7837 Unshars and saves the current series (@code{gnus-uu-decode-unshar-and-save}).
7840 @kindex X v s (Summary)
7841 @findex gnus-uu-decode-unshar-view
7842 Unshars and views the current series (@code{gnus-uu-decode-unshar-view}).
7845 @kindex X v S (Summary)
7846 @findex gnus-uu-decode-unshar-and-save-view
7847 Unshars, views and saves the current series
7848 (@code{gnus-uu-decode-unshar-and-save-view}).
7852 @node PostScript Files
7853 @subsection PostScript Files
7859 @kindex X p (Summary)
7860 @findex gnus-uu-decode-postscript
7861 Unpack the current PostScript series (@code{gnus-uu-decode-postscript}).
7864 @kindex X P (Summary)
7865 @findex gnus-uu-decode-postscript-and-save
7866 Unpack and save the current PostScript series
7867 (@code{gnus-uu-decode-postscript-and-save}).
7870 @kindex X v p (Summary)
7871 @findex gnus-uu-decode-postscript-view
7872 View the current PostScript series
7873 (@code{gnus-uu-decode-postscript-view}).
7876 @kindex X v P (Summary)
7877 @findex gnus-uu-decode-postscript-and-save-view
7878 View and save the current PostScript series
7879 (@code{gnus-uu-decode-postscript-and-save-view}).
7884 @subsection Other Files
7888 @kindex X o (Summary)
7889 @findex gnus-uu-decode-save
7890 Save the current series
7891 (@code{gnus-uu-decode-save}).
7894 @kindex X b (Summary)
7895 @findex gnus-uu-decode-binhex
7896 Unbinhex the current series (@code{gnus-uu-decode-binhex}). This
7897 doesn't really work yet.
7901 @node Decoding Variables
7902 @subsection Decoding Variables
7904 Adjective, not verb.
7907 * Rule Variables:: Variables that say how a file is to be viewed.
7908 * Other Decode Variables:: Other decode variables.
7909 * Uuencoding and Posting:: Variables for customizing uuencoding.
7913 @node Rule Variables
7914 @subsubsection Rule Variables
7915 @cindex rule variables
7917 Gnus uses @dfn{rule variables} to decide how to view a file. All these
7918 variables are of the form
7921 (list '(regexp1 command2)
7928 @item gnus-uu-user-view-rules
7929 @vindex gnus-uu-user-view-rules
7931 This variable is consulted first when viewing files. If you wish to use,
7932 for instance, @code{sox} to convert an @file{.au} sound file, you could
7935 (setq gnus-uu-user-view-rules
7936 (list '("\\\\.au$" "sox %s -t .aiff > /dev/audio")))
7939 @item gnus-uu-user-view-rules-end
7940 @vindex gnus-uu-user-view-rules-end
7941 This variable is consulted if Gnus couldn't make any matches from the
7942 user and default view rules.
7944 @item gnus-uu-user-archive-rules
7945 @vindex gnus-uu-user-archive-rules
7946 This variable can be used to say what commands should be used to unpack
7951 @node Other Decode Variables
7952 @subsubsection Other Decode Variables
7955 @vindex gnus-uu-grabbed-file-functions
7957 @item gnus-uu-grabbed-file-functions
7958 All functions in this list will be called right after each file has been
7959 successfully decoded---so that you can move or view files right away,
7960 and don't have to wait for all files to be decoded before you can do
7961 anything. Ready-made functions you can put in this list are:
7965 @item gnus-uu-grab-view
7966 @findex gnus-uu-grab-view
7969 @item gnus-uu-grab-move
7970 @findex gnus-uu-grab-move
7971 Move the file (if you're using a saving function.)
7974 @item gnus-uu-be-dangerous
7975 @vindex gnus-uu-be-dangerous
7976 Specifies what to do if unusual situations arise during decoding. If
7977 @code{nil}, be as conservative as possible. If @code{t}, ignore things
7978 that didn't work, and overwrite existing files. Otherwise, ask each
7981 @item gnus-uu-ignore-files-by-name
7982 @vindex gnus-uu-ignore-files-by-name
7983 Files with name matching this regular expression won't be viewed.
7985 @item gnus-uu-ignore-files-by-type
7986 @vindex gnus-uu-ignore-files-by-type
7987 Files with a @acronym{MIME} type matching this variable won't be viewed.
7988 Note that Gnus tries to guess what type the file is based on the name.
7989 @code{gnus-uu} is not a @acronym{MIME} package (yet), so this is slightly
7992 @item gnus-uu-tmp-dir
7993 @vindex gnus-uu-tmp-dir
7994 Where @code{gnus-uu} does its work.
7996 @item gnus-uu-do-not-unpack-archives
7997 @vindex gnus-uu-do-not-unpack-archives
7998 Non-@code{nil} means that @code{gnus-uu} won't peek inside archives
7999 looking for files to display.
8001 @item gnus-uu-view-and-save
8002 @vindex gnus-uu-view-and-save
8003 Non-@code{nil} means that the user will always be asked to save a file
8006 @item gnus-uu-ignore-default-view-rules
8007 @vindex gnus-uu-ignore-default-view-rules
8008 Non-@code{nil} means that @code{gnus-uu} will ignore the default viewing
8011 @item gnus-uu-ignore-default-archive-rules
8012 @vindex gnus-uu-ignore-default-archive-rules
8013 Non-@code{nil} means that @code{gnus-uu} will ignore the default archive
8016 @item gnus-uu-kill-carriage-return
8017 @vindex gnus-uu-kill-carriage-return
8018 Non-@code{nil} means that @code{gnus-uu} will strip all carriage returns
8021 @item gnus-uu-unmark-articles-not-decoded
8022 @vindex gnus-uu-unmark-articles-not-decoded
8023 Non-@code{nil} means that @code{gnus-uu} will mark unsuccessfully
8024 decoded articles as unread.
8026 @item gnus-uu-correct-stripped-uucode
8027 @vindex gnus-uu-correct-stripped-uucode
8028 Non-@code{nil} means that @code{gnus-uu} will @emph{try} to fix
8029 uuencoded files that have had trailing spaces deleted.
8031 @item gnus-uu-pre-uudecode-hook
8032 @vindex gnus-uu-pre-uudecode-hook
8033 Hook run before sending a message to @code{uudecode}.
8035 @item gnus-uu-view-with-metamail
8036 @vindex gnus-uu-view-with-metamail
8038 Non-@code{nil} means that @code{gnus-uu} will ignore the viewing
8039 commands defined by the rule variables and just fudge a @acronym{MIME}
8040 content type based on the file name. The result will be fed to
8041 @code{metamail} for viewing.
8043 @item gnus-uu-save-in-digest
8044 @vindex gnus-uu-save-in-digest
8045 Non-@code{nil} means that @code{gnus-uu}, when asked to save without
8046 decoding, will save in digests. If this variable is @code{nil},
8047 @code{gnus-uu} will just save everything in a file without any
8048 embellishments. The digesting almost conforms to RFC 1153---no easy way
8049 to specify any meaningful volume and issue numbers were found, so I
8050 simply dropped them.
8055 @node Uuencoding and Posting
8056 @subsubsection Uuencoding and Posting
8060 @item gnus-uu-post-include-before-composing
8061 @vindex gnus-uu-post-include-before-composing
8062 Non-@code{nil} means that @code{gnus-uu} will ask for a file to encode
8063 before you compose the article. If this variable is @code{t}, you can
8064 either include an encoded file with @kbd{C-c C-i} or have one included
8065 for you when you post the article.
8067 @item gnus-uu-post-length
8068 @vindex gnus-uu-post-length
8069 Maximum length of an article. The encoded file will be split into how
8070 many articles it takes to post the entire file.
8072 @item gnus-uu-post-threaded
8073 @vindex gnus-uu-post-threaded
8074 Non-@code{nil} means that @code{gnus-uu} will post the encoded file in a
8075 thread. This may not be smart, as no other decoder I have seen is able
8076 to follow threads when collecting uuencoded articles. (Well, I have
8077 seen one package that does that---@code{gnus-uu}, but somehow, I don't
8078 think that counts@dots{}) Default is @code{nil}.
8080 @item gnus-uu-post-separate-description
8081 @vindex gnus-uu-post-separate-description
8082 Non-@code{nil} means that the description will be posted in a separate
8083 article. The first article will typically be numbered (0/x). If this
8084 variable is @code{nil}, the description the user enters will be included
8085 at the beginning of the first article, which will be numbered (1/x).
8086 Default is @code{t}.
8092 @subsection Viewing Files
8093 @cindex viewing files
8094 @cindex pseudo-articles
8096 After decoding, if the file is some sort of archive, Gnus will attempt
8097 to unpack the archive and see if any of the files in the archive can be
8098 viewed. For instance, if you have a gzipped tar file @file{pics.tar.gz}
8099 containing the files @file{pic1.jpg} and @file{pic2.gif}, Gnus will
8100 uncompress and de-tar the main file, and then view the two pictures.
8101 This unpacking process is recursive, so if the archive contains archives
8102 of archives, it'll all be unpacked.
8104 Finally, Gnus will normally insert a @dfn{pseudo-article} for each
8105 extracted file into the summary buffer. If you go to these
8106 ``articles'', you will be prompted for a command to run (usually Gnus
8107 will make a suggestion), and then the command will be run.
8109 @vindex gnus-view-pseudo-asynchronously
8110 If @code{gnus-view-pseudo-asynchronously} is @code{nil}, Emacs will wait
8111 until the viewing is done before proceeding.
8113 @vindex gnus-view-pseudos
8114 If @code{gnus-view-pseudos} is @code{automatic}, Gnus will not insert
8115 the pseudo-articles into the summary buffer, but view them
8116 immediately. If this variable is @code{not-confirm}, the user won't even
8117 be asked for a confirmation before viewing is done.
8119 @vindex gnus-view-pseudos-separately
8120 If @code{gnus-view-pseudos-separately} is non-@code{nil}, one
8121 pseudo-article will be created for each file to be viewed. If
8122 @code{nil}, all files that use the same viewing command will be given as
8123 a list of parameters to that command.
8125 @vindex gnus-insert-pseudo-articles
8126 If @code{gnus-insert-pseudo-articles} is non-@code{nil}, insert
8127 pseudo-articles when decoding. It is @code{t} by default.
8129 So; there you are, reading your @emph{pseudo-articles} in your
8130 @emph{virtual newsgroup} from the @emph{virtual server}; and you think:
8131 Why isn't anything real anymore? How did we get here?
8134 @node Article Treatment
8135 @section Article Treatment
8137 Reading through this huge manual, you may have quite forgotten that the
8138 object of newsreaders is to actually, like, read what people have
8139 written. Reading articles. Unfortunately, people are quite bad at
8140 writing, so there are tons of functions and variables to make reading
8141 these articles easier.
8144 * Article Highlighting:: You want to make the article look like fruit salad.
8145 * Article Fontisizing:: Making emphasized text look nice.
8146 * Article Hiding:: You also want to make certain info go away.
8147 * Article Washing:: Lots of way-neat functions to make life better.
8148 * Article Header:: Doing various header transformations.
8149 * Article Buttons:: Click on URLs, Message-IDs, addresses and the like.
8150 * Article Button Levels:: Controlling appearance of buttons.
8151 * Article Date:: Grumble, UT!
8152 * Article Display:: Display various stuff---X-Face, Picons, Smileys
8153 * Article Signature:: What is a signature?
8154 * Article Miscellanea:: Various other stuff.
8158 @node Article Highlighting
8159 @subsection Article Highlighting
8160 @cindex highlighting
8162 Not only do you want your article buffer to look like fruit salad, but
8163 you want it to look like technicolor fruit salad.
8168 @kindex W H a (Summary)
8169 @findex gnus-article-highlight
8170 @findex gnus-article-maybe-highlight
8171 Do much highlighting of the current article
8172 (@code{gnus-article-highlight}). This function highlights header, cited
8173 text, the signature, and adds buttons to the body and the head.
8176 @kindex W H h (Summary)
8177 @findex gnus-article-highlight-headers
8178 @vindex gnus-header-face-alist
8179 Highlight the headers (@code{gnus-article-highlight-headers}). The
8180 highlighting will be done according to the @code{gnus-header-face-alist}
8181 variable, which is a list where each element has the form
8182 @code{(@var{regexp} @var{name} @var{content})}.
8183 @var{regexp} is a regular expression for matching the
8184 header, @var{name} is the face used for highlighting the header name
8185 (@pxref{Faces and Fonts}) and @var{content} is the face for highlighting
8186 the header value. The first match made will be used. Note that
8187 @var{regexp} shouldn't have @samp{^} prepended---Gnus will add one.
8190 @kindex W H c (Summary)
8191 @findex gnus-article-highlight-citation
8192 Highlight cited text (@code{gnus-article-highlight-citation}).
8194 Some variables to customize the citation highlights:
8197 @vindex gnus-cite-parse-max-size
8199 @item gnus-cite-parse-max-size
8200 If the article size if bigger than this variable (which is 25000 by
8201 default), no citation highlighting will be performed.
8203 @item gnus-cite-max-prefix
8204 @vindex gnus-cite-max-prefix
8205 Maximum possible length for a citation prefix (default 20).
8207 @item gnus-cite-face-list
8208 @vindex gnus-cite-face-list
8209 List of faces used for highlighting citations (@pxref{Faces and Fonts}).
8210 When there are citations from multiple articles in the same message,
8211 Gnus will try to give each citation from each article its own face.
8212 This should make it easier to see who wrote what.
8214 @item gnus-supercite-regexp
8215 @vindex gnus-supercite-regexp
8216 Regexp matching normal Supercite attribution lines.
8218 @item gnus-supercite-secondary-regexp
8219 @vindex gnus-supercite-secondary-regexp
8220 Regexp matching mangled Supercite attribution lines.
8222 @item gnus-cite-minimum-match-count
8223 @vindex gnus-cite-minimum-match-count
8224 Minimum number of identical prefixes we have to see before we believe
8225 that it's a citation.
8227 @item gnus-cite-attribution-prefix
8228 @vindex gnus-cite-attribution-prefix
8229 Regexp matching the beginning of an attribution line.
8231 @item gnus-cite-attribution-suffix
8232 @vindex gnus-cite-attribution-suffix
8233 Regexp matching the end of an attribution line.
8235 @item gnus-cite-attribution-face
8236 @vindex gnus-cite-attribution-face
8237 Face used for attribution lines. It is merged with the face for the
8238 cited text belonging to the attribution.
8240 @item gnus-cite-ignore-quoted-from
8241 @vindex gnus-cite-ignore-quoted-from
8242 If non-@code{nil}, no citation highlighting will be performed on lines
8243 beginning with @samp{>From }. Those lines may have been quoted by MTAs
8244 in order not to mix up with the envelope From line. The default value
8251 @kindex W H s (Summary)
8252 @vindex gnus-signature-separator
8253 @vindex gnus-signature-face
8254 @findex gnus-article-highlight-signature
8255 Highlight the signature (@code{gnus-article-highlight-signature}).
8256 Everything after @code{gnus-signature-separator} (@pxref{Article
8257 Signature}) in an article will be considered a signature and will be
8258 highlighted with @code{gnus-signature-face}, which is @code{italic} by
8263 @xref{Customizing Articles}, for how to highlight articles automatically.
8266 @node Article Fontisizing
8267 @subsection Article Fontisizing
8269 @cindex article emphasis
8271 @findex gnus-article-emphasize
8272 @kindex W e (Summary)
8273 People commonly add emphasis to words in news articles by writing things
8274 like @samp{_this_} or @samp{*this*} or @samp{/this/}. Gnus can make
8275 this look nicer by running the article through the @kbd{W e}
8276 (@code{gnus-article-emphasize}) command.
8278 @vindex gnus-emphasis-alist
8279 How the emphasis is computed is controlled by the
8280 @code{gnus-emphasis-alist} variable. This is an alist where the first
8281 element is a regular expression to be matched. The second is a number
8282 that says what regular expression grouping is used to find the entire
8283 emphasized word. The third is a number that says what regexp grouping
8284 should be displayed and highlighted. (The text between these two
8285 groupings will be hidden.) The fourth is the face used for
8289 (setq gnus-emphasis-alist
8290 '(("_\\(\\w+\\)_" 0 1 gnus-emphasis-underline)
8291 ("\\*\\(\\w+\\)\\*" 0 1 gnus-emphasis-bold)))
8300 @vindex gnus-emphasis-underline
8301 @vindex gnus-emphasis-bold
8302 @vindex gnus-emphasis-italic
8303 @vindex gnus-emphasis-underline-bold
8304 @vindex gnus-emphasis-underline-italic
8305 @vindex gnus-emphasis-bold-italic
8306 @vindex gnus-emphasis-underline-bold-italic
8307 By default, there are seven rules, and they use the following faces:
8308 @code{gnus-emphasis-bold}, @code{gnus-emphasis-italic},
8309 @code{gnus-emphasis-underline}, @code{gnus-emphasis-bold-italic},
8310 @code{gnus-emphasis-underline-italic},
8311 @code{gnus-emphasis-underline-bold}, and
8312 @code{gnus-emphasis-underline-bold-italic}.
8314 If you want to change these faces, you can either use @kbd{M-x
8315 customize}, or you can use @code{copy-face}. For instance, if you want
8316 to make @code{gnus-emphasis-italic} use a red face instead, you could
8320 (copy-face 'red 'gnus-emphasis-italic)
8323 @vindex gnus-group-highlight-words-alist
8325 If you want to highlight arbitrary words, you can use the
8326 @code{gnus-group-highlight-words-alist} variable, which uses the same
8327 syntax as @code{gnus-emphasis-alist}. The @code{highlight-words} group
8328 parameter (@pxref{Group Parameters}) can also be used.
8330 @xref{Customizing Articles}, for how to fontize articles automatically.
8333 @node Article Hiding
8334 @subsection Article Hiding
8335 @cindex article hiding
8337 Or rather, hiding certain things in each article. There usually is much
8338 too much cruft in most articles.
8343 @kindex W W a (Summary)
8344 @findex gnus-article-hide
8345 Do quite a lot of hiding on the article buffer
8346 (@kbd{gnus-article-hide}). In particular, this function will hide
8347 headers, @acronym{PGP}, cited text and the signature.
8350 @kindex W W h (Summary)
8351 @findex gnus-article-hide-headers
8352 Hide headers (@code{gnus-article-hide-headers}). @xref{Hiding
8356 @kindex W W b (Summary)
8357 @findex gnus-article-hide-boring-headers
8358 Hide headers that aren't particularly interesting
8359 (@code{gnus-article-hide-boring-headers}). @xref{Hiding Headers}.
8362 @kindex W W s (Summary)
8363 @findex gnus-article-hide-signature
8364 Hide signature (@code{gnus-article-hide-signature}). @xref{Article
8368 @kindex W W l (Summary)
8369 @findex gnus-article-hide-list-identifiers
8370 @vindex gnus-list-identifiers
8371 Strip list identifiers specified in @code{gnus-list-identifiers}. These
8372 are strings some mailing list servers add to the beginning of all
8373 @code{Subject} headers---for example, @samp{[zebra 4711]}. Any leading
8374 @samp{Re: } is skipped before stripping. @code{gnus-list-identifiers}
8375 may not contain @code{\\(..\\)}.
8379 @item gnus-list-identifiers
8380 @vindex gnus-list-identifiers
8381 A regular expression that matches list identifiers to be removed from
8382 subject. This can also be a list of regular expressions.
8387 @kindex W W P (Summary)
8388 @findex gnus-article-hide-pem
8389 Hide @acronym{PEM} (privacy enhanced messages) cruft
8390 (@code{gnus-article-hide-pem}).
8393 @kindex W W B (Summary)
8394 @findex gnus-article-strip-banner
8395 @vindex gnus-article-banner-alist
8396 @vindex gnus-article-address-banner-alist
8399 @cindex stripping advertisements
8400 @cindex advertisements
8401 Strip the banner specified by the @code{banner} group parameter
8402 (@code{gnus-article-strip-banner}). This is mainly used to hide those
8403 annoying banners and/or signatures that some mailing lists and moderated
8404 groups adds to all the messages. The way to use this function is to add
8405 the @code{banner} group parameter (@pxref{Group Parameters}) to the
8406 group you want banners stripped from. The parameter either be a string,
8407 which will be interpreted as a regular expression matching text to be
8408 removed, or the symbol @code{signature}, meaning that the (last)
8409 signature should be removed, or other symbol, meaning that the
8410 corresponding regular expression in @code{gnus-article-banner-alist} is
8413 Regardless of a group, you can hide things like advertisements only when
8414 the sender of an article has a certain mail address specified in
8415 @code{gnus-article-address-banner-alist}.
8419 @item gnus-article-address-banner-alist
8420 @vindex gnus-article-address-banner-alist
8421 Alist of mail addresses and banners. Each element has the form
8422 @code{(@var{address} . @var{banner})}, where @var{address} is a regexp
8423 matching a mail address in the From header, @var{banner} is one of a
8424 symbol @code{signature}, an item in @code{gnus-article-banner-alist},
8425 a regexp and @code{nil}. If @var{address} matches author's mail
8426 address, it will remove things like advertisements. For example, if a
8427 sender has the mail address @samp{hail@@yoo-hoo.co.jp} and there is a
8428 banner something like @samp{Do You Yoo-hoo!?} in all articles he
8429 sends, you can use the following element to remove them:
8432 ("@@yoo-hoo\\.co\\.jp\\'" .
8433 "\n_+\nDo You Yoo-hoo!\\?\n.*\n.*\n")
8439 @kindex W W c (Summary)
8440 @findex gnus-article-hide-citation
8441 Hide citation (@code{gnus-article-hide-citation}). Some variables for
8442 customizing the hiding:
8446 @item gnus-cited-opened-text-button-line-format
8447 @itemx gnus-cited-closed-text-button-line-format
8448 @vindex gnus-cited-closed-text-button-line-format
8449 @vindex gnus-cited-opened-text-button-line-format
8450 Gnus adds buttons to show where the cited text has been hidden, and to
8451 allow toggle hiding the text. The format of the variable is specified
8452 by these format-like variable (@pxref{Formatting Variables}). These
8457 Starting point of the hidden text.
8459 Ending point of the hidden text.
8461 Number of characters in the hidden region.
8463 Number of lines of hidden text.
8466 @item gnus-cited-lines-visible
8467 @vindex gnus-cited-lines-visible
8468 The number of lines at the beginning of the cited text to leave
8469 shown. This can also be a cons cell with the number of lines at the top
8470 and bottom of the text, respectively, to remain visible.
8475 @kindex W W C-c (Summary)
8476 @findex gnus-article-hide-citation-maybe
8478 Hide citation (@code{gnus-article-hide-citation-maybe}) depending on the
8479 following two variables:
8482 @item gnus-cite-hide-percentage
8483 @vindex gnus-cite-hide-percentage
8484 If the cited text is of a bigger percentage than this variable (default
8485 50), hide the cited text.
8487 @item gnus-cite-hide-absolute
8488 @vindex gnus-cite-hide-absolute
8489 The cited text must have at least this length (default 10) before it
8494 @kindex W W C (Summary)
8495 @findex gnus-article-hide-citation-in-followups
8496 Hide cited text in articles that aren't roots
8497 (@code{gnus-article-hide-citation-in-followups}). This isn't very
8498 useful as an interactive command, but might be a handy function to stick
8499 have happen automatically (@pxref{Customizing Articles}).
8503 All these ``hiding'' commands are toggles, but if you give a negative
8504 prefix to these commands, they will show what they have previously
8505 hidden. If you give a positive prefix, they will always hide.
8507 Also @pxref{Article Highlighting} for further variables for
8508 citation customization.
8510 @xref{Customizing Articles}, for how to hide article elements
8514 @node Article Washing
8515 @subsection Article Washing
8517 @cindex article washing
8519 We call this ``article washing'' for a really good reason. Namely, the
8520 @kbd{A} key was taken, so we had to use the @kbd{W} key instead.
8522 @dfn{Washing} is defined by us as ``changing something from something to
8523 something else'', but normally results in something looking better.
8526 @xref{Customizing Articles}, if you want to change how Gnus displays
8527 articles by default.
8532 This is not really washing, it's sort of the opposite of washing. If
8533 you type this, you see the article exactly as it exists on disk or on
8537 Force redisplaying of the current article
8538 (@code{gnus-summary-show-article}). This is also not really washing.
8539 If you type this, you see the article without any previously applied
8540 interactive Washing functions but with all default treatments
8541 (@pxref{Customizing Articles}).
8544 @kindex W l (Summary)
8545 @findex gnus-summary-stop-page-breaking
8546 Remove page breaks from the current article
8547 (@code{gnus-summary-stop-page-breaking}). @xref{Misc Article}, for page
8551 @kindex W r (Summary)
8552 @findex gnus-summary-caesar-message
8553 @c @icon{gnus-summary-caesar-message}
8554 Do a Caesar rotate (rot13) on the article buffer
8555 (@code{gnus-summary-caesar-message}).
8556 Unreadable articles that tell you to read them with Caesar rotate or rot13.
8557 (Typically offensive jokes and such.)
8559 It's commonly called ``rot13'' because each letter is rotated 13
8560 positions in the alphabet, e. g. @samp{B} (letter #2) -> @samp{O} (letter
8561 #15). It is sometimes referred to as ``Caesar rotate'' because Caesar
8562 is rumored to have employed this form of, uh, somewhat weak encryption.
8565 @kindex W m (Summary)
8566 @findex gnus-summary-morse-message
8567 Morse decode the article buffer (@code{gnus-summary-morse-message}).
8570 @kindex W i (Summary)
8571 @findex gnus-summary-idna-message
8572 Decode IDNA encoded domain names in the current articles. IDNA
8573 encoded domain names looks like @samp{xn--bar}. If a string remain
8574 unencoded after running invoking this, it is likely an invalid IDNA
8575 string (@samp{xn--bar} is invalid). You must have GNU Libidn
8576 (@url{http://www.gnu.org/software/libidn/}) installed for this command
8581 @kindex W t (Summary)
8583 @findex gnus-summary-toggle-header
8584 Toggle whether to display all headers in the article buffer
8585 (@code{gnus-summary-toggle-header}).
8588 @kindex W v (Summary)
8589 @findex gnus-summary-verbose-headers
8590 Toggle whether to display all headers in the article buffer permanently
8591 (@code{gnus-summary-verbose-headers}).
8594 @kindex W o (Summary)
8595 @findex gnus-article-treat-overstrike
8596 Treat overstrike (@code{gnus-article-treat-overstrike}).
8599 @kindex W d (Summary)
8600 @findex gnus-article-treat-dumbquotes
8601 @vindex gnus-article-dumbquotes-map
8603 @cindex M****s*** sm*rtq**t*s
8605 Treat M****s*** sm*rtq**t*s according to
8606 @code{gnus-article-dumbquotes-map}
8607 (@code{gnus-article-treat-dumbquotes}). Note that this function guesses
8608 whether a character is a sm*rtq**t* or not, so it should only be used
8611 Sm*rtq**t*s are M****s***'s unilateral extension to the character map in
8612 an attempt to provide more quoting characters. If you see something
8613 like @code{\222} or @code{\264} where you're expecting some kind of
8614 apostrophe or quotation mark, then try this wash.
8617 @kindex W Y f (Summary)
8618 @findex gnus-article-outlook-deuglify-article
8619 @cindex Outlook Express
8620 Full deuglify of broken Outlook (Express) articles: Treat dumbquotes,
8621 unwrap lines, repair attribution and rearrange citation.
8622 (@code{gnus-article-outlook-deuglify-article}).
8625 @kindex W Y u (Summary)
8626 @findex gnus-article-outlook-unwrap-lines
8627 @vindex gnus-outlook-deuglify-unwrap-min
8628 @vindex gnus-outlook-deuglify-unwrap-max
8629 Unwrap lines that appear to be wrapped citation lines. You can control
8630 what lines will be unwrapped by frobbing
8631 @code{gnus-outlook-deuglify-unwrap-min} and
8632 @code{gnus-outlook-deuglify-unwrap-max}, indicating the minimum and
8633 maximum length of an unwrapped citation line.
8634 (@code{gnus-article-outlook-unwrap-lines}).
8637 @kindex W Y a (Summary)
8638 @findex gnus-article-outlook-repair-attribution
8639 Repair a broken attribution line.@*
8640 (@code{gnus-article-outlook-repair-attribution}).
8643 @kindex W Y c (Summary)
8644 @findex gnus-article-outlook-rearrange-citation
8645 Repair broken citations by rearranging the text.
8646 (@code{gnus-article-outlook-rearrange-citation}).
8649 @kindex W w (Summary)
8650 @findex gnus-article-fill-cited-article
8651 Do word wrap (@code{gnus-article-fill-cited-article}).
8653 You can give the command a numerical prefix to specify the width to use
8657 @kindex W Q (Summary)
8658 @findex gnus-article-fill-long-lines
8659 Fill long lines (@code{gnus-article-fill-long-lines}).
8662 @kindex W C (Summary)
8663 @findex gnus-article-capitalize-sentences
8664 Capitalize the first word in each sentence
8665 (@code{gnus-article-capitalize-sentences}).
8668 @kindex W c (Summary)
8669 @findex gnus-article-remove-cr
8670 Translate CRLF pairs (i. e., @samp{^M}s on the end of the lines) into LF
8671 (this takes care of DOS line endings), and then translate any remaining
8672 CRs into LF (this takes care of Mac line endings)
8673 (@code{gnus-article-remove-cr}).
8676 @kindex W q (Summary)
8677 @findex gnus-article-de-quoted-unreadable
8678 Treat quoted-printable (@code{gnus-article-de-quoted-unreadable}).
8679 Quoted-Printable is one common @acronym{MIME} encoding employed when
8680 sending non-@acronym{ASCII} (i.e., 8-bit) articles. It typically
8681 makes strings like @samp{d@'ej@`a vu} look like @samp{d=E9j=E0 vu},
8682 which doesn't look very readable to me. Note that this is usually
8683 done automatically by Gnus if the message in question has a
8684 @code{Content-Transfer-Encoding} header that says that this encoding
8685 has been done. If a prefix is given, a charset will be asked for.
8688 @kindex W 6 (Summary)
8689 @findex gnus-article-de-base64-unreadable
8690 Treat base64 (@code{gnus-article-de-base64-unreadable}). Base64 is
8691 one common @acronym{MIME} encoding employed when sending
8692 non-@acronym{ASCII} (i.e., 8-bit) articles. Note that this is
8693 usually done automatically by Gnus if the message in question has a
8694 @code{Content-Transfer-Encoding} header that says that this encoding
8695 has been done. If a prefix is given, a charset will be asked for.
8698 @kindex W Z (Summary)
8699 @findex gnus-article-decode-HZ
8700 Treat HZ or HZP (@code{gnus-article-decode-HZ}). HZ (or HZP) is one
8701 common encoding employed when sending Chinese articles. It typically
8702 makes strings look like @samp{~@{<:Ky2;S@{#,NpJ)l6HK!#~@}}.
8705 @kindex W A (Summary)
8706 @findex gnus-article-treat-ansi-sequences
8707 @cindex @acronym{ANSI} control sequences
8708 Translate @acronym{ANSI} SGR control sequences into overlays or
8709 extents (@code{gnus-article-treat-ansi-sequences}). @acronym{ANSI}
8710 sequences are used in some Chinese hierarchies for highlighting.
8713 @kindex W u (Summary)
8714 @findex gnus-article-unsplit-urls
8715 Remove newlines from within URLs. Some mailers insert newlines into
8716 outgoing email messages to keep lines short. This reformatting can
8717 split long URLs onto multiple lines. Repair those URLs by removing
8718 the newlines (@code{gnus-article-unsplit-urls}).
8721 @kindex W h (Summary)
8722 @findex gnus-article-wash-html
8723 Treat @acronym{HTML} (@code{gnus-article-wash-html}). Note that this is
8724 usually done automatically by Gnus if the message in question has a
8725 @code{Content-Type} header that says that the message is @acronym{HTML}.
8727 If a prefix is given, a charset will be asked for. If it is a number,
8728 the charset defined in @code{gnus-summary-show-article-charset-alist}
8729 (@pxref{Paging the Article}) will be used.
8731 @vindex gnus-article-wash-function
8732 The default is to use the function specified by
8733 @code{mm-text-html-renderer} (@pxref{Display Customization, ,Display
8734 Customization, emacs-mime, The Emacs MIME Manual}) to convert the
8735 @acronym{HTML}, but this is controlled by the
8736 @code{gnus-article-wash-function} variable. Pre-defined functions you
8744 Use @uref{http://emacs-w3m.namazu.org/, emacs-w3m}.
8746 @item w3m-standalone
8747 Use @uref{http://w3m.sourceforge.net/, w3m}.
8750 Use @uref{http://links.sf.net/, Links}.
8753 Use @uref{http://lynx.isc.org/, Lynx}.
8756 Use html2text---a simple @acronym{HTML} converter included with Gnus.
8761 @kindex W b (Summary)
8762 @findex gnus-article-add-buttons
8763 Add clickable buttons to the article (@code{gnus-article-add-buttons}).
8764 @xref{Article Buttons}.
8767 @kindex W B (Summary)
8768 @findex gnus-article-add-buttons-to-head
8769 Add clickable buttons to the article headers
8770 (@code{gnus-article-add-buttons-to-head}).
8773 @kindex W p (Summary)
8774 @findex gnus-article-verify-x-pgp-sig
8775 Verify a signed control message
8776 (@code{gnus-article-verify-x-pgp-sig}). Control messages such as
8777 @code{newgroup} and @code{checkgroups} are usually signed by the
8778 hierarchy maintainer. You need to add the @acronym{PGP} public key of
8779 the maintainer to your keyring to verify the
8780 message.@footnote{@acronym{PGP} keys for many hierarchies are
8781 available at @uref{ftp://ftp.isc.org/pub/pgpcontrol/README.html}}
8784 @kindex W s (Summary)
8785 @findex gnus-summary-force-verify-and-decrypt
8786 Verify a signed (@acronym{PGP}, @acronym{PGP/MIME} or
8787 @acronym{S/MIME}) message
8788 (@code{gnus-summary-force-verify-and-decrypt}). @xref{Security}.
8791 @kindex W a (Summary)
8792 @findex gnus-article-strip-headers-in-body
8793 Strip headers like the @code{X-No-Archive} header from the beginning of
8794 article bodies (@code{gnus-article-strip-headers-in-body}).
8797 @kindex W E l (Summary)
8798 @findex gnus-article-strip-leading-blank-lines
8799 Remove all blank lines from the beginning of the article
8800 (@code{gnus-article-strip-leading-blank-lines}).
8803 @kindex W E m (Summary)
8804 @findex gnus-article-strip-multiple-blank-lines
8805 Replace all blank lines with empty lines and then all multiple empty
8806 lines with a single empty line.
8807 (@code{gnus-article-strip-multiple-blank-lines}).
8810 @kindex W E t (Summary)
8811 @findex gnus-article-remove-trailing-blank-lines
8812 Remove all blank lines at the end of the article
8813 (@code{gnus-article-remove-trailing-blank-lines}).
8816 @kindex W E a (Summary)
8817 @findex gnus-article-strip-blank-lines
8818 Do all the three commands above
8819 (@code{gnus-article-strip-blank-lines}).
8822 @kindex W E A (Summary)
8823 @findex gnus-article-strip-all-blank-lines
8824 Remove all blank lines
8825 (@code{gnus-article-strip-all-blank-lines}).
8828 @kindex W E s (Summary)
8829 @findex gnus-article-strip-leading-space
8830 Remove all white space from the beginning of all lines of the article
8831 body (@code{gnus-article-strip-leading-space}).
8834 @kindex W E e (Summary)
8835 @findex gnus-article-strip-trailing-space
8836 Remove all white space from the end of all lines of the article
8837 body (@code{gnus-article-strip-trailing-space}).
8841 @xref{Customizing Articles}, for how to wash articles automatically.
8844 @node Article Header
8845 @subsection Article Header
8847 These commands perform various transformations of article header.
8852 @kindex W G u (Summary)
8853 @findex gnus-article-treat-unfold-headers
8854 Unfold folded header lines (@code{gnus-article-treat-unfold-headers}).
8857 @kindex W G n (Summary)
8858 @findex gnus-article-treat-fold-newsgroups
8859 Fold the @code{Newsgroups} and @code{Followup-To} headers
8860 (@code{gnus-article-treat-fold-newsgroups}).
8863 @kindex W G f (Summary)
8864 @findex gnus-article-treat-fold-headers
8865 Fold all the message headers
8866 (@code{gnus-article-treat-fold-headers}).
8869 @kindex W E w (Summary)
8870 @findex gnus-article-remove-leading-whitespace
8871 Remove excessive whitespace from all headers
8872 (@code{gnus-article-remove-leading-whitespace}).
8877 @node Article Buttons
8878 @subsection Article Buttons
8881 People often include references to other stuff in articles, and it would
8882 be nice if Gnus could just fetch whatever it is that people talk about
8883 with the minimum of fuzz when you hit @kbd{RET} or use the middle mouse
8884 button on these references.
8886 @vindex gnus-button-man-handler
8887 Gnus adds @dfn{buttons} to certain standard references by default:
8888 Well-formed URLs, mail addresses, Message-IDs, Info links, man pages and
8889 Emacs or Gnus related references. This is controlled by two variables,
8890 one that handles article bodies and one that handles article heads:
8894 @item gnus-button-alist
8895 @vindex gnus-button-alist
8896 This is an alist where each entry has this form:
8899 (@var{regexp} @var{button-par} @var{use-p} @var{function} @var{data-par})
8905 All text that match this regular expression (case insensitive) will be
8906 considered an external reference. Here's a typical regexp that matches
8907 embedded URLs: @samp{<URL:\\([^\n\r>]*\\)>}. This can also be a
8908 variable containing a regexp, useful variables to use include
8909 @code{gnus-button-url-regexp} and @code{gnus-button-mid-or-mail-regexp}.
8912 Gnus has to know which parts of the matches is to be highlighted. This
8913 is a number that says what sub-expression of the regexp is to be
8914 highlighted. If you want it all highlighted, you use 0 here.
8917 This form will be @code{eval}ed, and if the result is non-@code{nil},
8918 this is considered a match. This is useful if you want extra sifting to
8919 avoid false matches. Often variables named
8920 @code{gnus-button-@var{*}-level} are used here, @xref{Article Button
8921 Levels}, but any other form may be used too.
8923 @c @code{use-p} is @code{eval}ed only if @code{regexp} matches.
8926 This function will be called when you click on this button.
8929 As with @var{button-par}, this is a sub-expression number, but this one
8930 says which part of the match is to be sent as data to @var{function}.
8934 So the full entry for buttonizing URLs is then
8937 ("<URL:\\([^\n\r>]*\\)>" 0 t gnus-button-url 1)
8940 @item gnus-header-button-alist
8941 @vindex gnus-header-button-alist
8942 This is just like the other alist, except that it is applied to the
8943 article head only, and that each entry has an additional element that is
8944 used to say what headers to apply the buttonize coding to:
8947 (@var{header} @var{regexp} @var{button-par} @var{use-p} @var{function} @var{data-par})
8950 @var{header} is a regular expression.
8953 @subsubsection Related variables and functions
8956 @item gnus-button-@var{*}-level
8957 @xref{Article Button Levels}.
8959 @c Stuff related to gnus-button-browse-level
8961 @item gnus-button-url-regexp
8962 @vindex gnus-button-url-regexp
8963 A regular expression that matches embedded URLs. It is used in the
8964 default values of the variables above.
8966 @c Stuff related to gnus-button-man-level
8968 @item gnus-button-man-handler
8969 @vindex gnus-button-man-handler
8970 The function to use for displaying man pages. It must take at least one
8971 argument with a string naming the man page.
8973 @c Stuff related to gnus-button-message-level
8975 @item gnus-button-mid-or-mail-regexp
8976 @vindex gnus-button-mid-or-mail-regexp
8977 Regular expression that matches a message ID or a mail address.
8979 @item gnus-button-prefer-mid-or-mail
8980 @vindex gnus-button-prefer-mid-or-mail
8981 This variable determines what to do when the button on a string as
8982 @samp{foo123@@bar.invalid} is pushed. Strings like this can be either a
8983 message ID or a mail address. If it is one of the symbols @code{mid} or
8984 @code{mail}, Gnus will always assume that the string is a message ID or
8985 a mail address, respectively. If this variable is set to the symbol
8986 @code{ask}, always query the user what do do. If it is a function, this
8987 function will be called with the string as its only argument. The
8988 function must return @code{mid}, @code{mail}, @code{invalid} or
8989 @code{ask}. The default value is the function
8990 @code{gnus-button-mid-or-mail-heuristic}.
8992 @item gnus-button-mid-or-mail-heuristic
8993 @findex gnus-button-mid-or-mail-heuristic
8994 Function that guesses whether its argument is a message ID or a mail
8995 address. Returns @code{mid} if it's a message IDs, @code{mail} if
8996 it's a mail address, @code{ask} if unsure and @code{invalid} if the
8999 @item gnus-button-mid-or-mail-heuristic-alist
9000 @vindex gnus-button-mid-or-mail-heuristic-alist
9001 An alist of @code{(RATE . REGEXP)} pairs used by the function
9002 @code{gnus-button-mid-or-mail-heuristic}.
9004 @c Stuff related to gnus-button-tex-level
9006 @item gnus-button-ctan-handler
9007 @findex gnus-button-ctan-handler
9008 The function to use for displaying CTAN links. It must take one
9009 argument, the string naming the URL.
9012 @vindex gnus-ctan-url
9013 Top directory of a CTAN (Comprehensive TeX Archive Network) archive used
9014 by @code{gnus-button-ctan-handler}.
9018 @item gnus-article-button-face
9019 @vindex gnus-article-button-face
9020 Face used on buttons.
9022 @item gnus-article-mouse-face
9023 @vindex gnus-article-mouse-face
9024 Face used when the mouse cursor is over a button.
9028 @xref{Customizing Articles}, for how to buttonize articles automatically.
9031 @node Article Button Levels
9032 @subsection Article button levels
9033 @cindex button levels
9034 The higher the value of the variables @code{gnus-button-@var{*}-level},
9035 the more buttons will appear. If the level is zero, no corresponding
9036 buttons are displayed. With the default value (which is 5) you should
9037 already see quite a lot of buttons. With higher levels, you will see
9038 more buttons, but you may also get more false positives. To avoid them,
9039 you can set the variables @code{gnus-button-@var{*}-level} local to
9040 specific groups (@pxref{Group Parameters}). Here's an example for the
9041 variable @code{gnus-parameters}:
9044 ;; @r{increase @code{gnus-button-*-level} in some groups:}
9045 (setq gnus-parameters
9046 '(("\\<\\(emacs\\|gnus\\)\\>" (gnus-button-emacs-level 10))
9047 ("\\<unix\\>" (gnus-button-man-level 10))
9048 ("\\<tex\\>" (gnus-button-tex-level 10))))
9053 @item gnus-button-browse-level
9054 @vindex gnus-button-browse-level
9055 Controls the display of references to message IDs, mail addresses and
9056 news URLs. Related variables and functions include
9057 @code{gnus-button-url-regexp}, @code{browse-url}, and
9058 @code{browse-url-browser-function}.
9060 @item gnus-button-emacs-level
9061 @vindex gnus-button-emacs-level
9062 Controls the display of Emacs or Gnus references. Related functions are
9063 @code{gnus-button-handle-custom},
9064 @code{gnus-button-handle-describe-function},
9065 @code{gnus-button-handle-describe-variable},
9066 @code{gnus-button-handle-symbol},
9067 @code{gnus-button-handle-describe-key},
9068 @code{gnus-button-handle-apropos},
9069 @code{gnus-button-handle-apropos-command},
9070 @code{gnus-button-handle-apropos-variable},
9071 @code{gnus-button-handle-apropos-documentation}, and
9072 @code{gnus-button-handle-library}.
9074 @item gnus-button-man-level
9075 @vindex gnus-button-man-level
9076 Controls the display of references to (Unix) man pages.
9077 See @code{gnus-button-man-handler}.
9079 @item gnus-button-message-level
9080 @vindex gnus-button-message-level
9081 Controls the display of message IDs, mail addresses and news URLs.
9082 Related variables and functions include
9083 @code{gnus-button-mid-or-mail-regexp},
9084 @code{gnus-button-prefer-mid-or-mail},
9085 @code{gnus-button-mid-or-mail-heuristic}, and
9086 @code{gnus-button-mid-or-mail-heuristic-alist}.
9088 @item gnus-button-tex-level
9089 @vindex gnus-button-tex-level
9090 Controls the display of references to @TeX{} or LaTeX stuff, e.g. for CTAN
9091 URLs. See the variables @code{gnus-ctan-url},
9092 @code{gnus-button-ctan-handler},
9093 @code{gnus-button-ctan-directory-regexp}, and
9094 @code{gnus-button-handle-ctan-bogus-regexp}.
9100 @subsection Article Date
9102 The date is most likely generated in some obscure timezone you've never
9103 heard of, so it's quite nice to be able to find out what the time was
9104 when the article was sent.
9109 @kindex W T u (Summary)
9110 @findex gnus-article-date-ut
9111 Display the date in UT (aka. GMT, aka ZULU)
9112 (@code{gnus-article-date-ut}).
9115 @kindex W T i (Summary)
9116 @findex gnus-article-date-iso8601
9118 Display the date in international format, aka. ISO 8601
9119 (@code{gnus-article-date-iso8601}).
9122 @kindex W T l (Summary)
9123 @findex gnus-article-date-local
9124 Display the date in the local timezone (@code{gnus-article-date-local}).
9127 @kindex W T p (Summary)
9128 @findex gnus-article-date-english
9129 Display the date in a format that's easily pronounceable in English
9130 (@code{gnus-article-date-english}).
9133 @kindex W T s (Summary)
9134 @vindex gnus-article-time-format
9135 @findex gnus-article-date-user
9136 @findex format-time-string
9137 Display the date using a user-defined format
9138 (@code{gnus-article-date-user}). The format is specified by the
9139 @code{gnus-article-time-format} variable, and is a string that's passed
9140 to @code{format-time-string}. See the documentation of that variable
9141 for a list of possible format specs.
9144 @kindex W T e (Summary)
9145 @findex gnus-article-date-lapsed
9146 @findex gnus-start-date-timer
9147 @findex gnus-stop-date-timer
9148 Say how much time has elapsed between the article was posted and now
9149 (@code{gnus-article-date-lapsed}). It looks something like:
9152 X-Sent: 6 weeks, 4 days, 1 hour, 3 minutes, 8 seconds ago
9155 @vindex gnus-article-date-lapsed-new-header
9156 The value of @code{gnus-article-date-lapsed-new-header} determines
9157 whether this header will just be added below the old Date one, or will
9160 An advantage of using Gnus to read mail is that it converts simple bugs
9161 into wonderful absurdities.
9163 If you want to have this line updated continually, you can put
9166 (gnus-start-date-timer)
9169 in your @file{~/.gnus.el} file, or you can run it off of some hook. If
9170 you want to stop the timer, you can use the @code{gnus-stop-date-timer}
9174 @kindex W T o (Summary)
9175 @findex gnus-article-date-original
9176 Display the original date (@code{gnus-article-date-original}). This can
9177 be useful if you normally use some other conversion function and are
9178 worried that it might be doing something totally wrong. Say, claiming
9179 that the article was posted in 1854. Although something like that is
9180 @emph{totally} impossible. Don't you trust me? *titter*
9184 @xref{Customizing Articles}, for how to display the date in your
9185 preferred format automatically.
9188 @node Article Display
9189 @subsection Article Display
9194 These commands add various frivolous display gimmicks to the article
9195 buffer in Emacs versions that support them.
9197 @code{X-Face} headers are small black-and-white images supplied by the
9198 message headers (@pxref{X-Face}).
9200 @code{Face} headers are small colored images supplied by the message
9201 headers (@pxref{Face}).
9203 Smileys are those little @samp{:-)} symbols that people like to litter
9204 their messages with (@pxref{Smileys}).
9206 Picons, on the other hand, reside on your own system, and Gnus will
9207 try to match the headers to what you have (@pxref{Picons}).
9209 All these functions are toggles---if the elements already exist,
9214 @kindex W D x (Summary)
9215 @findex gnus-article-display-x-face
9216 Display an @code{X-Face} in the @code{From} header.
9217 (@code{gnus-article-display-x-face}).
9220 @kindex W D d (Summary)
9221 @findex gnus-article-display-face
9222 Display a @code{Face} in the @code{From} header.
9223 (@code{gnus-article-display-face}).
9226 @kindex W D s (Summary)
9227 @findex gnus-treat-smiley
9228 Display smileys (@code{gnus-treat-smiley}).
9231 @kindex W D f (Summary)
9232 @findex gnus-treat-from-picon
9233 Piconify the @code{From} header (@code{gnus-treat-from-picon}).
9236 @kindex W D m (Summary)
9237 @findex gnus-treat-mail-picon
9238 Piconify all mail headers (i. e., @code{Cc}, @code{To})
9239 (@code{gnus-treat-mail-picon}).
9242 @kindex W D n (Summary)
9243 @findex gnus-treat-newsgroups-picon
9244 Piconify all news headers (i. e., @code{Newsgroups} and
9245 @code{Followup-To}) (@code{gnus-treat-newsgroups-picon}).
9248 @kindex W D D (Summary)
9249 @findex gnus-article-remove-images
9250 Remove all images from the article buffer
9251 (@code{gnus-article-remove-images}).
9257 @node Article Signature
9258 @subsection Article Signature
9260 @cindex article signature
9262 @vindex gnus-signature-separator
9263 Each article is divided into two parts---the head and the body. The
9264 body can be divided into a signature part and a text part. The variable
9265 that says what is to be considered a signature is
9266 @code{gnus-signature-separator}. This is normally the standard
9267 @samp{^-- $} as mandated by son-of-RFC 1036. However, many people use
9268 non-standard signature separators, so this variable can also be a list
9269 of regular expressions to be tested, one by one. (Searches are done
9270 from the end of the body towards the beginning.) One likely value is:
9273 (setq gnus-signature-separator
9274 '("^-- $" ; @r{The standard}
9275 "^-- *$" ; @r{A common mangling}
9276 "^-------*$" ; @r{Many people just use a looong}
9277 ; @r{line of dashes. Shame!}
9278 "^ *--------*$" ; @r{Double-shame!}
9279 "^________*$" ; @r{Underscores are also popular}
9280 "^========*$")) ; @r{Pervert!}
9283 The more permissive you are, the more likely it is that you'll get false
9286 @vindex gnus-signature-limit
9287 @code{gnus-signature-limit} provides a limit to what is considered a
9288 signature when displaying articles.
9292 If it is an integer, no signature may be longer (in characters) than
9295 If it is a floating point number, no signature may be longer (in lines)
9298 If it is a function, the function will be called without any parameters,
9299 and if it returns @code{nil}, there is no signature in the buffer.
9301 If it is a string, it will be used as a regexp. If it matches, the text
9302 in question is not a signature.
9305 This variable can also be a list where the elements may be of the types
9306 listed above. Here's an example:
9309 (setq gnus-signature-limit
9310 '(200.0 "^---*Forwarded article"))
9313 This means that if there are more than 200 lines after the signature
9314 separator, or the text after the signature separator is matched by
9315 the regular expression @samp{^---*Forwarded article}, then it isn't a
9316 signature after all.
9319 @node Article Miscellanea
9320 @subsection Article Miscellanea
9324 @kindex A t (Summary)
9325 @findex gnus-article-babel
9326 Translate the article from one language to another
9327 (@code{gnus-article-babel}).
9333 @section MIME Commands
9334 @cindex MIME decoding
9336 @cindex viewing attachments
9338 The following commands all understand the numerical prefix. For
9339 instance, @kbd{3 K v} means ``view the third @acronym{MIME} part''.
9345 @kindex K v (Summary)
9346 View the @acronym{MIME} part.
9349 @kindex K o (Summary)
9350 Save the @acronym{MIME} part.
9353 @kindex K O (Summary)
9354 Prompt for a file name, then save the @acronym{MIME} part and strip it
9355 from the article. The stripped @acronym{MIME} object will be referred
9356 via the message/external-body @acronym{MIME} type.
9359 @kindex K r (Summary)
9360 Replace the @acronym{MIME} part with an external body.
9363 @kindex K d (Summary)
9364 Delete the @acronym{MIME} part and add some information about the
9368 @kindex K c (Summary)
9369 Copy the @acronym{MIME} part.
9372 @kindex K e (Summary)
9373 View the @acronym{MIME} part externally.
9376 @kindex K i (Summary)
9377 View the @acronym{MIME} part internally.
9380 @kindex K | (Summary)
9381 Pipe the @acronym{MIME} part to an external command.
9384 The rest of these @acronym{MIME} commands do not use the numerical prefix in
9389 @kindex K b (Summary)
9390 Make all the @acronym{MIME} parts have buttons in front of them. This is
9391 mostly useful if you wish to save (or perform other actions) on inlined
9395 @kindex K m (Summary)
9396 @findex gnus-summary-repair-multipart
9397 Some multipart messages are transmitted with missing or faulty headers.
9398 This command will attempt to ``repair'' these messages so that they can
9399 be viewed in a more pleasant manner
9400 (@code{gnus-summary-repair-multipart}).
9403 @kindex X m (Summary)
9404 @findex gnus-summary-save-parts
9405 Save all parts matching a @acronym{MIME} type to a directory
9406 (@code{gnus-summary-save-parts}). Understands the process/prefix
9407 convention (@pxref{Process/Prefix}).
9410 @kindex M-t (Summary)
9411 @findex gnus-summary-toggle-display-buttonized
9412 Toggle the buttonized display of the article buffer
9413 (@code{gnus-summary-toggle-display-buttonized}).
9416 @kindex W M w (Summary)
9417 @findex gnus-article-decode-mime-words
9418 Decode RFC 2047-encoded words in the article headers
9419 (@code{gnus-article-decode-mime-words}).
9422 @kindex W M c (Summary)
9423 @findex gnus-article-decode-charset
9424 Decode encoded article bodies as well as charsets
9425 (@code{gnus-article-decode-charset}).
9427 This command looks in the @code{Content-Type} header to determine the
9428 charset. If there is no such header in the article, you can give it a
9429 prefix, which will prompt for the charset to decode as. In regional
9430 groups where people post using some common encoding (but do not
9431 include @acronym{MIME} headers), you can set the @code{charset} group/topic
9432 parameter to the required charset (@pxref{Group Parameters}).
9435 @kindex W M v (Summary)
9436 @findex gnus-mime-view-all-parts
9437 View all the @acronym{MIME} parts in the current article
9438 (@code{gnus-mime-view-all-parts}).
9445 @item gnus-ignored-mime-types
9446 @vindex gnus-ignored-mime-types
9447 This is a list of regexps. @acronym{MIME} types that match a regexp from
9448 this list will be completely ignored by Gnus. The default value is
9451 To have all Vcards be ignored, you'd say something like this:
9454 (setq gnus-ignored-mime-types
9458 @item gnus-article-loose-mime
9459 @vindex gnus-article-loose-mime
9460 If non-@code{nil}, Gnus won't require the @samp{MIME-Version} header
9461 before interpreting the message as a @acronym{MIME} message. This helps
9462 when reading messages from certain broken mail user agents. The
9463 default is @code{nil}.
9465 @item gnus-article-emulate-mime
9466 @vindex gnus-article-emulate-mime
9467 There are other, non-@acronym{MIME} encoding methods used. The most common
9468 is @samp{uuencode}, but yEncode is also getting to be popular. If
9469 this variable is non-@code{nil}, Gnus will look in message bodies to
9470 see if it finds these encodings, and if so, it'll run them through the
9471 Gnus @acronym{MIME} machinery. The default is @code{t}.
9473 @item gnus-unbuttonized-mime-types
9474 @vindex gnus-unbuttonized-mime-types
9475 This is a list of regexps. @acronym{MIME} types that match a regexp from
9476 this list won't have @acronym{MIME} buttons inserted unless they aren't
9477 displayed or this variable is overridden by
9478 @code{gnus-buttonized-mime-types}. The default value is
9479 @code{(".*/.*")}. This variable is only used when
9480 @code{gnus-inhibit-mime-unbuttonizing} is @code{nil}.
9482 @item gnus-buttonized-mime-types
9483 @vindex gnus-buttonized-mime-types
9484 This is a list of regexps. @acronym{MIME} types that match a regexp from
9485 this list will have @acronym{MIME} buttons inserted unless they aren't
9486 displayed. This variable overrides
9487 @code{gnus-unbuttonized-mime-types}. The default value is @code{nil}.
9488 This variable is only used when @code{gnus-inhibit-mime-unbuttonizing}
9491 To see e.g. security buttons but no other buttons, you could set this
9492 variable to @code{("multipart/signed")} and leave
9493 @code{gnus-unbuttonized-mime-types} at the default value.
9495 You could also add @code{"multipart/alternative"} to this list to
9496 display radio buttons that allow you to choose one of two media types
9497 those mails include. See also @code{mm-discouraged-alternatives}
9498 (@pxref{Display Customization, ,Display Customization, emacs-mime, The
9499 Emacs MIME Manual}).
9501 @item gnus-inhibit-mime-unbuttonizing
9502 @vindex gnus-inhibit-mime-unbuttonizing
9503 If this is non-@code{nil}, then all @acronym{MIME} parts get buttons. The
9504 default value is @code{nil}.
9506 @item gnus-article-mime-part-function
9507 @vindex gnus-article-mime-part-function
9508 For each @acronym{MIME} part, this function will be called with the @acronym{MIME}
9509 handle as the parameter. The function is meant to be used to allow
9510 users to gather information from the article (e. g., add Vcard info to
9511 the bbdb database) or to do actions based on parts (e. g., automatically
9512 save all jpegs into some directory).
9514 Here's an example function the does the latter:
9517 (defun my-save-all-jpeg-parts (handle)
9518 (when (equal (car (mm-handle-type handle)) "image/jpeg")
9520 (insert (mm-get-part handle))
9521 (write-region (point-min) (point-max)
9522 (read-file-name "Save jpeg to: ")))))
9523 (setq gnus-article-mime-part-function
9524 'my-save-all-jpeg-parts)
9527 @vindex gnus-mime-multipart-functions
9528 @item gnus-mime-multipart-functions
9529 Alist of @acronym{MIME} multipart types and functions to handle them.
9531 @vindex gnus-mime-display-multipart-alternative-as-mixed
9532 @item gnus-mime-display-multipart-alternative-as-mixed
9533 Display "multipart/alternative" parts as "multipart/mixed".
9535 @vindex gnus-mime-display-multipart-related-as-mixed
9536 @item gnus-mime-display-multipart-related-as-mixed
9537 Display "multipart/related" parts as "multipart/mixed".
9539 If displaying "text/html" is discouraged, see
9540 @code{mm-discouraged-alternatives}, images or other material inside a
9541 "multipart/related" part might be overlooked when this variable is
9542 @code{nil}. @ref{Display Customization, Display Customization, ,
9543 emacs-mime, Emacs-Mime Manual}.
9545 @vindex gnus-mime-display-multipart-as-mixed
9546 @item gnus-mime-display-multipart-as-mixed
9547 Display "multipart" parts as "multipart/mixed". If @code{t}, it
9548 overrides @code{nil} values of
9549 @code{gnus-mime-display-multipart-alternative-as-mixed} and
9550 @code{gnus-mime-display-multipart-related-as-mixed}.
9552 @vindex mm-file-name-rewrite-functions
9553 @item mm-file-name-rewrite-functions
9554 List of functions used for rewriting file names of @acronym{MIME} parts.
9555 Each function takes a file name as input and returns a file name.
9557 Ready-made functions include@*
9558 @code{mm-file-name-delete-whitespace},
9559 @code{mm-file-name-trim-whitespace},
9560 @code{mm-file-name-collapse-whitespace}, and
9561 @code{mm-file-name-replace-whitespace}. The later uses the value of
9562 the variable @code{mm-file-name-replace-whitespace} to replace each
9563 whitespace character in a file name with that string; default value
9564 is @code{"_"} (a single underscore).
9565 @findex mm-file-name-delete-whitespace
9566 @findex mm-file-name-trim-whitespace
9567 @findex mm-file-name-collapse-whitespace
9568 @findex mm-file-name-replace-whitespace
9569 @vindex mm-file-name-replace-whitespace
9571 The standard functions @code{capitalize}, @code{downcase},
9572 @code{upcase}, and @code{upcase-initials} may be useful, too.
9574 Everybody knows that whitespace characters in file names are evil,
9575 except those who don't know. If you receive lots of attachments from
9576 such unenlightened users, you can make live easier by adding
9579 (setq mm-file-name-rewrite-functions
9580 '(mm-file-name-trim-whitespace
9581 mm-file-name-collapse-whitespace
9582 mm-file-name-replace-whitespace))
9586 to your @file{~/.gnus.el} file.
9595 People use different charsets, and we have @acronym{MIME} to let us know what
9596 charsets they use. Or rather, we wish we had. Many people use
9597 newsreaders and mailers that do not understand or use @acronym{MIME}, and
9598 just send out messages without saying what character sets they use. To
9599 help a bit with this, some local news hierarchies have policies that say
9600 what character set is the default. For instance, the @samp{fj}
9601 hierarchy uses @code{iso-2022-jp}.
9603 @vindex gnus-group-charset-alist
9604 This knowledge is encoded in the @code{gnus-group-charset-alist}
9605 variable, which is an alist of regexps (use the first item to match full
9606 group names) and default charsets to be used when reading these groups.
9608 @vindex gnus-newsgroup-ignored-charsets
9609 In addition, some people do use soi-disant @acronym{MIME}-aware agents that
9610 aren't. These blithely mark messages as being in @code{iso-8859-1}
9611 even if they really are in @code{koi-8}. To help here, the
9612 @code{gnus-newsgroup-ignored-charsets} variable can be used. The
9613 charsets that are listed here will be ignored. The variable can be
9614 set on a group-by-group basis using the group parameters (@pxref{Group
9615 Parameters}). The default value is @code{(unknown-8bit x-unknown)},
9616 which includes values some agents insist on having in there.
9618 @vindex gnus-group-posting-charset-alist
9619 When posting, @code{gnus-group-posting-charset-alist} is used to
9620 determine which charsets should not be encoded using the @acronym{MIME}
9621 encodings. For instance, some hierarchies discourage using
9622 quoted-printable header encoding.
9624 This variable is an alist of regexps and permitted unencoded charsets
9625 for posting. Each element of the alist has the form @code{(}@var{test
9626 header body-list}@code{)}, where:
9630 is either a regular expression matching the newsgroup header or a
9633 is the charset which may be left unencoded in the header (@code{nil}
9634 means encode all charsets),
9636 is a list of charsets which may be encoded using 8bit content-transfer
9637 encoding in the body, or one of the special values @code{nil} (always
9638 encode using quoted-printable) or @code{t} (always use 8bit).
9645 @cindex coding system aliases
9646 @cindex preferred charset
9648 @xref{Encoding Customization, , Encoding Customization, emacs-mime,
9649 The Emacs MIME Manual}, for additional variables that control which
9650 MIME charsets are used when sending messages.
9652 Other charset tricks that may be useful, although not Gnus-specific:
9654 If there are several @acronym{MIME} charsets that encode the same Emacs
9655 charset, you can choose what charset to use by saying the following:
9658 (put-charset-property 'cyrillic-iso8859-5
9659 'preferred-coding-system 'koi8-r)
9662 This means that Russian will be encoded using @code{koi8-r} instead of
9663 the default @code{iso-8859-5} @acronym{MIME} charset.
9665 If you want to read messages in @code{koi8-u}, you can cheat and say
9668 (define-coding-system-alias 'koi8-u 'koi8-r)
9671 This will almost do the right thing.
9673 And finally, to read charsets like @code{windows-1251}, you can say
9677 (codepage-setup 1251)
9678 (define-coding-system-alias 'windows-1251 'cp1251)
9682 @node Article Commands
9683 @section Article Commands
9690 @kindex A P (Summary)
9691 @vindex gnus-ps-print-hook
9692 @findex gnus-summary-print-article
9693 Generate and print a PostScript image of the article buffer
9694 (@code{gnus-summary-print-article}). @code{gnus-ps-print-hook} will
9695 be run just before printing the buffer. An alternative way to print
9696 article is to use Muttprint (@pxref{Saving Articles}).
9701 @node Summary Sorting
9702 @section Summary Sorting
9703 @cindex summary sorting
9705 You can have the summary buffer sorted in various ways, even though I
9706 can't really see why you'd want that.
9711 @kindex C-c C-s C-n (Summary)
9712 @findex gnus-summary-sort-by-number
9713 Sort by article number (@code{gnus-summary-sort-by-number}).
9716 @kindex C-c C-s C-a (Summary)
9717 @findex gnus-summary-sort-by-author
9718 Sort by author (@code{gnus-summary-sort-by-author}).
9721 @kindex C-c C-s C-t (Summary)
9722 @findex gnus-summary-sort-by-recipient
9723 Sort by recipient (@code{gnus-summary-sort-by-recipient}).
9726 @kindex C-c C-s C-s (Summary)
9727 @findex gnus-summary-sort-by-subject
9728 Sort by subject (@code{gnus-summary-sort-by-subject}).
9731 @kindex C-c C-s C-d (Summary)
9732 @findex gnus-summary-sort-by-date
9733 Sort by date (@code{gnus-summary-sort-by-date}).
9736 @kindex C-c C-s C-l (Summary)
9737 @findex gnus-summary-sort-by-lines
9738 Sort by lines (@code{gnus-summary-sort-by-lines}).
9741 @kindex C-c C-s C-c (Summary)
9742 @findex gnus-summary-sort-by-chars
9743 Sort by article length (@code{gnus-summary-sort-by-chars}).
9746 @kindex C-c C-s C-i (Summary)
9747 @findex gnus-summary-sort-by-score
9748 Sort by score (@code{gnus-summary-sort-by-score}).
9751 @kindex C-c C-s C-r (Summary)
9752 @findex gnus-summary-sort-by-random
9753 Randomize (@code{gnus-summary-sort-by-random}).
9756 @kindex C-c C-s C-o (Summary)
9757 @findex gnus-summary-sort-by-original
9758 Sort using the default sorting method
9759 (@code{gnus-summary-sort-by-original}).
9762 These functions will work both when you use threading and when you don't
9763 use threading. In the latter case, all summary lines will be sorted,
9764 line by line. In the former case, sorting will be done on a
9765 root-by-root basis, which might not be what you were looking for. To
9766 toggle whether to use threading, type @kbd{T T} (@pxref{Thread
9770 @node Finding the Parent
9771 @section Finding the Parent
9772 @cindex parent articles
9773 @cindex referring articles
9778 @findex gnus-summary-refer-parent-article
9779 If you'd like to read the parent of the current article, and it is not
9780 displayed in the summary buffer, you might still be able to. That is,
9781 if the current group is fetched by @acronym{NNTP}, the parent hasn't expired
9782 and the @code{References} in the current article are not mangled, you
9783 can just press @kbd{^} or @kbd{A r}
9784 (@code{gnus-summary-refer-parent-article}). If everything goes well,
9785 you'll get the parent. If the parent is already displayed in the
9786 summary buffer, point will just move to this article.
9788 If given a positive numerical prefix, fetch that many articles back into
9789 the ancestry. If given a negative numerical prefix, fetch just that
9790 ancestor. So if you say @kbd{3 ^}, Gnus will fetch the parent, the
9791 grandparent and the grandgrandparent of the current article. If you say
9792 @kbd{-3 ^}, Gnus will only fetch the grandgrandparent of the current
9796 @findex gnus-summary-refer-references
9797 @kindex A R (Summary)
9798 Fetch all articles mentioned in the @code{References} header of the
9799 article (@code{gnus-summary-refer-references}).
9802 @findex gnus-summary-refer-thread
9803 @kindex A T (Summary)
9804 Display the full thread where the current article appears
9805 (@code{gnus-summary-refer-thread}). This command has to fetch all the
9806 headers in the current group to work, so it usually takes a while. If
9807 you do it often, you may consider setting @code{gnus-fetch-old-headers}
9808 to @code{invisible} (@pxref{Filling In Threads}). This won't have any
9809 visible effects normally, but it'll make this command work a whole lot
9810 faster. Of course, it'll make group entry somewhat slow.
9812 @vindex gnus-refer-thread-limit
9813 The @code{gnus-refer-thread-limit} variable says how many old (i. e.,
9814 articles before the first displayed in the current group) headers to
9815 fetch when doing this command. The default is 200. If @code{t}, all
9816 the available headers will be fetched. This variable can be overridden
9817 by giving the @kbd{A T} command a numerical prefix.
9820 @findex gnus-summary-refer-article
9821 @kindex M-^ (Summary)
9823 @cindex fetching by Message-ID
9824 You can also ask Gnus for an arbitrary article, no matter what group it
9825 belongs to. @kbd{M-^} (@code{gnus-summary-refer-article}) will ask you
9826 for a @code{Message-ID}, which is one of those long, hard-to-read
9827 thingies that look something like @samp{<38o6up$6f2@@hymir.ifi.uio.no>}.
9828 You have to get it all exactly right. No fuzzy searches, I'm afraid.
9830 Gnus looks for the @code{Message-ID} in the headers that have already
9831 been fetched, but also tries all the select methods specified by
9832 @code{gnus-refer-article-method} if it is not found.
9835 @vindex gnus-refer-article-method
9836 If the group you are reading is located on a back end that does not
9837 support fetching by @code{Message-ID} very well (like @code{nnspool}),
9838 you can set @code{gnus-refer-article-method} to an @acronym{NNTP} method. It
9839 would, perhaps, be best if the @acronym{NNTP} server you consult is the one
9840 updating the spool you are reading from, but that's not really
9843 It can also be a list of select methods, as well as the special symbol
9844 @code{current}, which means to use the current select method. If it
9845 is a list, Gnus will try all the methods in the list until it finds a
9848 Here's an example setting that will first try the current method, and
9849 then ask Google if that fails:
9852 (setq gnus-refer-article-method
9854 (nnweb "google" (nnweb-type google))))
9857 Most of the mail back ends support fetching by @code{Message-ID}, but
9858 do not do a particularly excellent job at it. That is, @code{nnmbox},
9859 @code{nnbabyl}, @code{nnmaildir}, @code{nnml}, are able to locate
9860 articles from any groups, while @code{nnfolder}, and @code{nnimap} are
9861 only able to locate articles that have been posted to the current
9862 group. (Anything else would be too time consuming.) @code{nnmh} does
9863 not support this at all.
9866 @node Alternative Approaches
9867 @section Alternative Approaches
9869 Different people like to read news using different methods. This being
9870 Gnus, we offer a small selection of minor modes for the summary buffers.
9873 * Pick and Read:: First mark articles and then read them.
9874 * Binary Groups:: Auto-decode all articles.
9879 @subsection Pick and Read
9880 @cindex pick and read
9882 Some newsreaders (like @code{nn} and, uhm, @code{Netnews} on VM/CMS) use
9883 a two-phased reading interface. The user first marks in a summary
9884 buffer the articles she wants to read. Then she starts reading the
9885 articles with just an article buffer displayed.
9887 @findex gnus-pick-mode
9888 @kindex M-x gnus-pick-mode
9889 Gnus provides a summary buffer minor mode that allows
9890 this---@code{gnus-pick-mode}. This basically means that a few process
9891 mark commands become one-keystroke commands to allow easy marking, and
9892 it provides one additional command for switching to the summary buffer.
9894 Here are the available keystrokes when using pick mode:
9899 @findex gnus-pick-article-or-thread
9900 Pick the article or thread on the current line
9901 (@code{gnus-pick-article-or-thread}). If the variable
9902 @code{gnus-thread-hide-subtree} is true, then this key selects the
9903 entire thread when used at the first article of the thread. Otherwise,
9904 it selects just the article. If given a numerical prefix, go to that
9905 thread or article and pick it. (The line number is normally displayed
9906 at the beginning of the summary pick lines.)
9909 @kindex SPACE (Pick)
9910 @findex gnus-pick-next-page
9911 Scroll the summary buffer up one page (@code{gnus-pick-next-page}). If
9912 at the end of the buffer, start reading the picked articles.
9916 @findex gnus-pick-unmark-article-or-thread.
9917 Unpick the thread or article
9918 (@code{gnus-pick-unmark-article-or-thread}). If the variable
9919 @code{gnus-thread-hide-subtree} is true, then this key unpicks the
9920 thread if used at the first article of the thread. Otherwise it unpicks
9921 just the article. You can give this key a numerical prefix to unpick
9922 the thread or article at that line.
9926 @findex gnus-pick-start-reading
9927 @vindex gnus-pick-display-summary
9928 Start reading the picked articles (@code{gnus-pick-start-reading}). If
9929 given a prefix, mark all unpicked articles as read first. If
9930 @code{gnus-pick-display-summary} is non-@code{nil}, the summary buffer
9931 will still be visible when you are reading.
9935 All the normal summary mode commands are still available in the
9936 pick-mode, with the exception of @kbd{u}. However @kbd{!} is available
9937 which is mapped to the same function
9938 @code{gnus-summary-tick-article-forward}.
9940 If this sounds like a good idea to you, you could say:
9943 (add-hook 'gnus-summary-mode-hook 'gnus-pick-mode)
9946 @vindex gnus-pick-mode-hook
9947 @code{gnus-pick-mode-hook} is run in pick minor mode buffers.
9949 @vindex gnus-mark-unpicked-articles-as-read
9950 If @code{gnus-mark-unpicked-articles-as-read} is non-@code{nil}, mark
9951 all unpicked articles as read. The default is @code{nil}.
9953 @vindex gnus-summary-pick-line-format
9954 The summary line format in pick mode is slightly different from the
9955 standard format. At the beginning of each line the line number is
9956 displayed. The pick mode line format is controlled by the
9957 @code{gnus-summary-pick-line-format} variable (@pxref{Formatting
9958 Variables}). It accepts the same format specs that
9959 @code{gnus-summary-line-format} does (@pxref{Summary Buffer Lines}).
9963 @subsection Binary Groups
9964 @cindex binary groups
9966 @findex gnus-binary-mode
9967 @kindex M-x gnus-binary-mode
9968 If you spend much time in binary groups, you may grow tired of hitting
9969 @kbd{X u}, @kbd{n}, @kbd{RET} all the time. @kbd{M-x gnus-binary-mode}
9970 is a minor mode for summary buffers that makes all ordinary Gnus article
9971 selection functions uudecode series of articles and display the result
9972 instead of just displaying the articles the normal way.
9975 @findex gnus-binary-show-article
9976 The only way, in fact, to see the actual articles is the @kbd{g}
9977 command, when you have turned on this mode
9978 (@code{gnus-binary-show-article}).
9980 @vindex gnus-binary-mode-hook
9981 @code{gnus-binary-mode-hook} is called in binary minor mode buffers.
9985 @section Tree Display
9988 @vindex gnus-use-trees
9989 If you don't like the normal Gnus summary display, you might try setting
9990 @code{gnus-use-trees} to @code{t}. This will create (by default) an
9991 additional @dfn{tree buffer}. You can execute all summary mode commands
9994 There are a few variables to customize the tree display, of course:
9997 @item gnus-tree-mode-hook
9998 @vindex gnus-tree-mode-hook
9999 A hook called in all tree mode buffers.
10001 @item gnus-tree-mode-line-format
10002 @vindex gnus-tree-mode-line-format
10003 A format string for the mode bar in the tree mode buffers (@pxref{Mode
10004 Line Formatting}). The default is @samp{Gnus: %%b %S %Z}. For a list
10005 of valid specs, @pxref{Summary Buffer Mode Line}.
10007 @item gnus-selected-tree-face
10008 @vindex gnus-selected-tree-face
10009 Face used for highlighting the selected article in the tree buffer. The
10010 default is @code{modeline}.
10012 @item gnus-tree-line-format
10013 @vindex gnus-tree-line-format
10014 A format string for the tree nodes. The name is a bit of a misnomer,
10015 though---it doesn't define a line, but just the node. The default value
10016 is @samp{%(%[%3,3n%]%)}, which displays the first three characters of
10017 the name of the poster. It is vital that all nodes are of the same
10018 length, so you @emph{must} use @samp{%4,4n}-like specifiers.
10024 The name of the poster.
10026 The @code{From} header.
10028 The number of the article.
10030 The opening bracket.
10032 The closing bracket.
10037 @xref{Formatting Variables}.
10039 Variables related to the display are:
10042 @item gnus-tree-brackets
10043 @vindex gnus-tree-brackets
10044 This is used for differentiating between ``real'' articles and
10045 ``sparse'' articles. The format is
10047 ((@var{real-open} . @var{real-close})
10048 (@var{sparse-open} . @var{sparse-close})
10049 (@var{dummy-open} . @var{dummy-close}))
10051 and the default is @code{((?[ . ?]) (?( . ?)) (?@{ . ?@}) (?< . ?>))}.
10053 @item gnus-tree-parent-child-edges
10054 @vindex gnus-tree-parent-child-edges
10055 This is a list that contains the characters used for connecting parent
10056 nodes to their children. The default is @code{(?- ?\\ ?|)}.
10060 @item gnus-tree-minimize-window
10061 @vindex gnus-tree-minimize-window
10062 If this variable is non-@code{nil}, Gnus will try to keep the tree
10063 buffer as small as possible to allow more room for the other Gnus
10064 windows. If this variable is a number, the tree buffer will never be
10065 higher than that number. The default is @code{t}. Note that if you
10066 have several windows displayed side-by-side in a frame and the tree
10067 buffer is one of these, minimizing the tree window will also resize all
10068 other windows displayed next to it.
10070 You may also wish to add the following hook to keep the window minimized
10074 (add-hook 'gnus-configure-windows-hook
10075 'gnus-tree-perhaps-minimize)
10078 @item gnus-generate-tree-function
10079 @vindex gnus-generate-tree-function
10080 @findex gnus-generate-horizontal-tree
10081 @findex gnus-generate-vertical-tree
10082 The function that actually generates the thread tree. Two predefined
10083 functions are available: @code{gnus-generate-horizontal-tree} and
10084 @code{gnus-generate-vertical-tree} (which is the default).
10088 Here's an example from a horizontal tree buffer:
10091 @{***@}-(***)-[odd]-[Gun]
10101 Here's the same thread displayed in a vertical tree buffer:
10106 |--------------------------\-----\-----\
10107 (***) [Bjo] [Gun] [Gun]
10109 [odd] [Jan] [odd] (***) [Jor]
10111 [Gun] [Eri] [Eri] [odd]
10117 If you're using horizontal trees, it might be nice to display the trees
10118 side-by-side with the summary buffer. You could add something like the
10119 following to your @file{~/.gnus.el} file:
10122 (setq gnus-use-trees t
10123 gnus-generate-tree-function 'gnus-generate-horizontal-tree
10124 gnus-tree-minimize-window nil)
10125 (gnus-add-configuration
10129 (summary 0.75 point)
10134 @xref{Window Layout}.
10137 @node Mail Group Commands
10138 @section Mail Group Commands
10139 @cindex mail group commands
10141 Some commands only make sense in mail groups. If these commands are
10142 invalid in the current group, they will raise a hell and let you know.
10144 All these commands (except the expiry and edit commands) use the
10145 process/prefix convention (@pxref{Process/Prefix}).
10150 @kindex B e (Summary)
10151 @findex gnus-summary-expire-articles
10152 Run all expirable articles in the current group through the expiry
10153 process (@code{gnus-summary-expire-articles}). That is, delete all
10154 expirable articles in the group that have been around for a while.
10155 (@pxref{Expiring Mail}).
10158 @kindex B C-M-e (Summary)
10159 @findex gnus-summary-expire-articles-now
10160 Delete all the expirable articles in the group
10161 (@code{gnus-summary-expire-articles-now}). This means that @strong{all}
10162 articles eligible for expiry in the current group will
10163 disappear forever into that big @file{/dev/null} in the sky.
10166 @kindex B DEL (Summary)
10167 @findex gnus-summary-delete-article
10168 @c @icon{gnus-summary-mail-delete}
10169 Delete the mail article. This is ``delete'' as in ``delete it from your
10170 disk forever and ever, never to return again.'' Use with caution.
10171 (@code{gnus-summary-delete-article}).
10174 @kindex B m (Summary)
10176 @findex gnus-summary-move-article
10177 @vindex gnus-preserve-marks
10178 Move the article from one mail group to another
10179 (@code{gnus-summary-move-article}). Marks will be preserved if
10180 @code{gnus-preserve-marks} is non-@code{nil} (which is the default).
10183 @kindex B c (Summary)
10185 @findex gnus-summary-copy-article
10186 @c @icon{gnus-summary-mail-copy}
10187 Copy the article from one group (mail group or not) to a mail group
10188 (@code{gnus-summary-copy-article}). Marks will be preserved if
10189 @code{gnus-preserve-marks} is non-@code{nil} (which is the default).
10192 @kindex B B (Summary)
10193 @cindex crosspost mail
10194 @findex gnus-summary-crosspost-article
10195 Crosspost the current article to some other group
10196 (@code{gnus-summary-crosspost-article}). This will create a new copy of
10197 the article in the other group, and the Xref headers of the article will
10198 be properly updated.
10201 @kindex B i (Summary)
10202 @findex gnus-summary-import-article
10203 Import an arbitrary file into the current mail newsgroup
10204 (@code{gnus-summary-import-article}). You will be prompted for a file
10205 name, a @code{From} header and a @code{Subject} header.
10208 @kindex B I (Summary)
10209 @findex gnus-summary-create-article
10210 Create an empty article in the current mail newsgroups
10211 (@code{gnus-summary-create-article}). You will be prompted for a
10212 @code{From} header and a @code{Subject} header.
10215 @kindex B r (Summary)
10216 @findex gnus-summary-respool-article
10217 @vindex gnus-summary-respool-default-method
10218 Respool the mail article (@code{gnus-summary-respool-article}).
10219 @code{gnus-summary-respool-default-method} will be used as the default
10220 select method when respooling. This variable is @code{nil} by default,
10221 which means that the current group select method will be used instead.
10222 Marks will be preserved if @code{gnus-preserve-marks} is non-@code{nil}
10223 (which is the default).
10227 @kindex B w (Summary)
10228 @kindex e (Summary)
10229 @findex gnus-summary-edit-article
10230 @kindex C-c C-c (Article)
10231 @findex gnus-summary-edit-article-done
10232 Edit the current article (@code{gnus-summary-edit-article}). To finish
10233 editing and make the changes permanent, type @kbd{C-c C-c}
10234 (@code{gnus-summary-edit-article-done}). If you give a prefix to the
10235 @kbd{C-c C-c} command, Gnus won't re-highlight the article.
10238 @kindex B q (Summary)
10239 @findex gnus-summary-respool-query
10240 If you want to re-spool an article, you might be curious as to what group
10241 the article will end up in before you do the re-spooling. This command
10242 will tell you (@code{gnus-summary-respool-query}).
10245 @kindex B t (Summary)
10246 @findex gnus-summary-respool-trace
10247 Similarly, this command will display all fancy splitting patterns used
10248 when respooling, if any (@code{gnus-summary-respool-trace}).
10251 @kindex B p (Summary)
10252 @findex gnus-summary-article-posted-p
10253 Some people have a tendency to send you ``courtesy'' copies when they
10254 follow up to articles you have posted. These usually have a
10255 @code{Newsgroups} header in them, but not always. This command
10256 (@code{gnus-summary-article-posted-p}) will try to fetch the current
10257 article from your news server (or rather, from
10258 @code{gnus-refer-article-method} or @code{gnus-select-method}) and will
10259 report back whether it found the article or not. Even if it says that
10260 it didn't find the article, it may have been posted anyway---mail
10261 propagation is much faster than news propagation, and the news copy may
10262 just not have arrived yet.
10265 @kindex K E (Summary)
10266 @findex gnus-article-encrypt-body
10267 @vindex gnus-article-encrypt-protocol
10268 Encrypt the body of an article (@code{gnus-article-encrypt-body}).
10269 The body is encrypted with the encryption protocol specified by the
10270 variable @code{gnus-article-encrypt-protocol}.
10274 @vindex gnus-move-split-methods
10275 @cindex moving articles
10276 If you move (or copy) articles regularly, you might wish to have Gnus
10277 suggest where to put the articles. @code{gnus-move-split-methods} is a
10278 variable that uses the same syntax as @code{gnus-split-methods}
10279 (@pxref{Saving Articles}). You may customize that variable to create
10280 suggestions you find reasonable. (Note that
10281 @code{gnus-move-split-methods} uses group names where
10282 @code{gnus-split-methods} uses file names.)
10285 (setq gnus-move-split-methods
10286 '(("^From:.*Lars Magne" "nnml:junk")
10287 ("^Subject:.*gnus" "nnfolder:important")
10288 (".*" "nnml:misc")))
10292 @node Various Summary Stuff
10293 @section Various Summary Stuff
10296 * Summary Group Information:: Information oriented commands.
10297 * Searching for Articles:: Multiple article commands.
10298 * Summary Generation Commands::
10299 * Really Various Summary Commands:: Those pesky non-conformant commands.
10303 @vindex gnus-summary-display-while-building
10304 @item gnus-summary-display-while-building
10305 If non-@code{nil}, show and update the summary buffer as it's being
10306 built. If @code{t}, update the buffer after every line is inserted.
10307 If the value is an integer, @var{n}, update the display every @var{n}
10308 lines. The default is @code{nil}.
10310 @vindex gnus-summary-display-arrow
10311 @item gnus-summary-display-arrow
10312 If non-@code{nil}, display an arrow in the fringe to indicate the
10315 @vindex gnus-summary-mode-hook
10316 @item gnus-summary-mode-hook
10317 This hook is called when creating a summary mode buffer.
10319 @vindex gnus-summary-generate-hook
10320 @item gnus-summary-generate-hook
10321 This is called as the last thing before doing the threading and the
10322 generation of the summary buffer. It's quite convenient for customizing
10323 the threading variables based on what data the newsgroup has. This hook
10324 is called from the summary buffer after most summary buffer variables
10327 @vindex gnus-summary-prepare-hook
10328 @item gnus-summary-prepare-hook
10329 It is called after the summary buffer has been generated. You might use
10330 it to, for instance, highlight lines or modify the look of the buffer in
10331 some other ungodly manner. I don't care.
10333 @vindex gnus-summary-prepared-hook
10334 @item gnus-summary-prepared-hook
10335 A hook called as the very last thing after the summary buffer has been
10338 @vindex gnus-summary-ignore-duplicates
10339 @item gnus-summary-ignore-duplicates
10340 When Gnus discovers two articles that have the same @code{Message-ID},
10341 it has to do something drastic. No articles are allowed to have the
10342 same @code{Message-ID}, but this may happen when reading mail from some
10343 sources. Gnus allows you to customize what happens with this variable.
10344 If it is @code{nil} (which is the default), Gnus will rename the
10345 @code{Message-ID} (for display purposes only) and display the article as
10346 any other article. If this variable is @code{t}, it won't display the
10347 article---it'll be as if it never existed.
10349 @vindex gnus-alter-articles-to-read-function
10350 @item gnus-alter-articles-to-read-function
10351 This function, which takes two parameters (the group name and the list
10352 of articles to be selected), is called to allow the user to alter the
10353 list of articles to be selected.
10355 For instance, the following function adds the list of cached articles to
10356 the list in one particular group:
10359 (defun my-add-cached-articles (group articles)
10360 (if (string= group "some.group")
10361 (append gnus-newsgroup-cached articles)
10365 @vindex gnus-newsgroup-variables
10366 @item gnus-newsgroup-variables
10367 A list of newsgroup (summary buffer) local variables, or cons of
10368 variables and their default expressions to be evalled (when the default
10369 values are not @code{nil}), that should be made global while the summary
10372 Note: The default expressions will be evaluated (using function
10373 @code{eval}) before assignment to the local variable rather than just
10374 assigned to it. If the default expression is the symbol @code{global},
10375 that symbol will not be evaluated but the global value of the local
10376 variable will be used instead.
10378 These variables can be used to set variables in the group parameters
10379 while still allowing them to affect operations done in other
10380 buffers. For example:
10383 (setq gnus-newsgroup-variables
10384 '(message-use-followup-to
10385 (gnus-visible-headers .
10386 "^From:\\|^Newsgroups:\\|^Subject:\\|^Date:\\|^To:")))
10389 Also @pxref{Group Parameters}.
10393 @node Summary Group Information
10394 @subsection Summary Group Information
10399 @kindex H f (Summary)
10400 @findex gnus-summary-fetch-faq
10401 @vindex gnus-group-faq-directory
10402 Try to fetch the @acronym{FAQ} (list of frequently asked questions)
10403 for the current group (@code{gnus-summary-fetch-faq}). Gnus will try
10404 to get the @acronym{FAQ} from @code{gnus-group-faq-directory}, which
10405 is usually a directory on a remote machine. This variable can also be
10406 a list of directories. In that case, giving a prefix to this command
10407 will allow you to choose between the various sites. @code{ange-ftp}
10408 or @code{efs} will probably be used for fetching the file.
10411 @kindex H d (Summary)
10412 @findex gnus-summary-describe-group
10413 Give a brief description of the current group
10414 (@code{gnus-summary-describe-group}). If given a prefix, force
10415 rereading the description from the server.
10418 @kindex H h (Summary)
10419 @findex gnus-summary-describe-briefly
10420 Give an extremely brief description of the most important summary
10421 keystrokes (@code{gnus-summary-describe-briefly}).
10424 @kindex H i (Summary)
10425 @findex gnus-info-find-node
10426 Go to the Gnus info node (@code{gnus-info-find-node}).
10430 @node Searching for Articles
10431 @subsection Searching for Articles
10436 @kindex M-s (Summary)
10437 @findex gnus-summary-search-article-forward
10438 Search through all subsequent (raw) articles for a regexp
10439 (@code{gnus-summary-search-article-forward}).
10442 @kindex M-r (Summary)
10443 @findex gnus-summary-search-article-backward
10444 Search through all previous (raw) articles for a regexp
10445 (@code{gnus-summary-search-article-backward}).
10448 @kindex & (Summary)
10449 @findex gnus-summary-execute-command
10450 This command will prompt you for a header, a regular expression to match
10451 on this field, and a command to be executed if the match is made
10452 (@code{gnus-summary-execute-command}). If the header is an empty
10453 string, the match is done on the entire article. If given a prefix,
10454 search backward instead.
10456 For instance, @kbd{& RET some.*string RET #} will put the process mark on
10457 all articles that have heads or bodies that match @samp{some.*string}.
10460 @kindex M-& (Summary)
10461 @findex gnus-summary-universal-argument
10462 Perform any operation on all articles that have been marked with
10463 the process mark (@code{gnus-summary-universal-argument}).
10466 @node Summary Generation Commands
10467 @subsection Summary Generation Commands
10472 @kindex Y g (Summary)
10473 @findex gnus-summary-prepare
10474 Regenerate the current summary buffer (@code{gnus-summary-prepare}).
10477 @kindex Y c (Summary)
10478 @findex gnus-summary-insert-cached-articles
10479 Pull all cached articles (for the current group) into the summary buffer
10480 (@code{gnus-summary-insert-cached-articles}).
10483 @kindex Y d (Summary)
10484 @findex gnus-summary-insert-dormant-articles
10485 Pull all dormant articles (for the current group) into the summary buffer
10486 (@code{gnus-summary-insert-dormant-articles}).
10491 @node Really Various Summary Commands
10492 @subsection Really Various Summary Commands
10498 @kindex C-d (Summary)
10499 @kindex A D (Summary)
10500 @findex gnus-summary-enter-digest-group
10501 If the current article is a collection of other articles (for instance,
10502 a digest), you might use this command to enter a group based on the that
10503 article (@code{gnus-summary-enter-digest-group}). Gnus will try to
10504 guess what article type is currently displayed unless you give a prefix
10505 to this command, which forces a ``digest'' interpretation. Basically,
10506 whenever you see a message that is a collection of other messages of
10507 some format, you @kbd{C-d} and read these messages in a more convenient
10511 @kindex C-M-d (Summary)
10512 @findex gnus-summary-read-document
10513 This command is very similar to the one above, but lets you gather
10514 several documents into one biiig group
10515 (@code{gnus-summary-read-document}). It does this by opening several
10516 @code{nndoc} groups for each document, and then opening an
10517 @code{nnvirtual} group on top of these @code{nndoc} groups. This
10518 command understands the process/prefix convention
10519 (@pxref{Process/Prefix}).
10522 @kindex C-t (Summary)
10523 @findex gnus-summary-toggle-truncation
10524 Toggle truncation of summary lines
10525 (@code{gnus-summary-toggle-truncation}). This will probably confuse the
10526 line centering function in the summary buffer, so it's not a good idea
10527 to have truncation switched off while reading articles.
10530 @kindex = (Summary)
10531 @findex gnus-summary-expand-window
10532 Expand the summary buffer window (@code{gnus-summary-expand-window}).
10533 If given a prefix, force an @code{article} window configuration.
10536 @kindex C-M-e (Summary)
10537 @findex gnus-summary-edit-parameters
10538 Edit the group parameters (@pxref{Group Parameters}) of the current
10539 group (@code{gnus-summary-edit-parameters}).
10542 @kindex C-M-a (Summary)
10543 @findex gnus-summary-customize-parameters
10544 Customize the group parameters (@pxref{Group Parameters}) of the current
10545 group (@code{gnus-summary-customize-parameters}).
10550 @node Exiting the Summary Buffer
10551 @section Exiting the Summary Buffer
10552 @cindex summary exit
10553 @cindex exiting groups
10555 Exiting from the summary buffer will normally update all info on the
10556 group and return you to the group buffer.
10563 @kindex Z Z (Summary)
10564 @kindex Z Q (Summary)
10565 @kindex q (Summary)
10566 @findex gnus-summary-exit
10567 @vindex gnus-summary-exit-hook
10568 @vindex gnus-summary-prepare-exit-hook
10569 @vindex gnus-group-no-more-groups-hook
10570 @c @icon{gnus-summary-exit}
10571 Exit the current group and update all information on the group
10572 (@code{gnus-summary-exit}). @code{gnus-summary-prepare-exit-hook} is
10573 called before doing much of the exiting, which calls
10574 @code{gnus-summary-expire-articles} by default.
10575 @code{gnus-summary-exit-hook} is called after finishing the exit
10576 process. @code{gnus-group-no-more-groups-hook} is run when returning to
10577 group mode having no more (unread) groups.
10581 @kindex Z E (Summary)
10582 @kindex Q (Summary)
10583 @findex gnus-summary-exit-no-update
10584 Exit the current group without updating any information on the group
10585 (@code{gnus-summary-exit-no-update}).
10589 @kindex Z c (Summary)
10590 @kindex c (Summary)
10591 @findex gnus-summary-catchup-and-exit
10592 @c @icon{gnus-summary-catchup-and-exit}
10593 Mark all unticked articles in the group as read and then exit
10594 (@code{gnus-summary-catchup-and-exit}).
10597 @kindex Z C (Summary)
10598 @findex gnus-summary-catchup-all-and-exit
10599 Mark all articles, even the ticked ones, as read and then exit
10600 (@code{gnus-summary-catchup-all-and-exit}).
10603 @kindex Z n (Summary)
10604 @findex gnus-summary-catchup-and-goto-next-group
10605 Mark all articles as read and go to the next group
10606 (@code{gnus-summary-catchup-and-goto-next-group}).
10609 @kindex Z p (Summary)
10610 @findex gnus-summary-catchup-and-goto-prev-group
10611 Mark all articles as read and go to the previous group
10612 (@code{gnus-summary-catchup-and-goto-prev-group}).
10616 @kindex Z R (Summary)
10617 @kindex C-x C-s (Summary)
10618 @findex gnus-summary-reselect-current-group
10619 Exit this group, and then enter it again
10620 (@code{gnus-summary-reselect-current-group}). If given a prefix, select
10621 all articles, both read and unread.
10625 @kindex Z G (Summary)
10626 @kindex M-g (Summary)
10627 @findex gnus-summary-rescan-group
10628 @c @icon{gnus-summary-mail-get}
10629 Exit the group, check for new articles in the group, and select the
10630 group (@code{gnus-summary-rescan-group}). If given a prefix, select all
10631 articles, both read and unread.
10634 @kindex Z N (Summary)
10635 @findex gnus-summary-next-group
10636 Exit the group and go to the next group
10637 (@code{gnus-summary-next-group}).
10640 @kindex Z P (Summary)
10641 @findex gnus-summary-prev-group
10642 Exit the group and go to the previous group
10643 (@code{gnus-summary-prev-group}).
10646 @kindex Z s (Summary)
10647 @findex gnus-summary-save-newsrc
10648 Save the current number of read/marked articles in the dribble buffer
10649 and then save the dribble buffer (@code{gnus-summary-save-newsrc}). If
10650 given a prefix, also save the @file{.newsrc} file(s). Using this
10651 command will make exit without updating (the @kbd{Q} command) worthless.
10654 @vindex gnus-exit-group-hook
10655 @code{gnus-exit-group-hook} is called when you exit the current group
10656 with an ``updating'' exit. For instance @kbd{Q}
10657 (@code{gnus-summary-exit-no-update}) does not call this hook.
10659 @findex gnus-summary-wake-up-the-dead
10660 @findex gnus-dead-summary-mode
10661 @vindex gnus-kill-summary-on-exit
10662 If you're in the habit of exiting groups, and then changing your mind
10663 about it, you might set @code{gnus-kill-summary-on-exit} to @code{nil}.
10664 If you do that, Gnus won't kill the summary buffer when you exit it.
10665 (Quelle surprise!) Instead it will change the name of the buffer to
10666 something like @samp{*Dead Summary ... *} and install a minor mode
10667 called @code{gnus-dead-summary-mode}. Now, if you switch back to this
10668 buffer, you'll find that all keys are mapped to a function called
10669 @code{gnus-summary-wake-up-the-dead}. So tapping any keys in a dead
10670 summary buffer will result in a live, normal summary buffer.
10672 There will never be more than one dead summary buffer at any one time.
10674 @vindex gnus-use-cross-reference
10675 The data on the current group will be updated (which articles you have
10676 read, which articles you have replied to, etc.) when you exit the
10677 summary buffer. If the @code{gnus-use-cross-reference} variable is
10678 @code{t} (which is the default), articles that are cross-referenced to
10679 this group and are marked as read, will also be marked as read in the
10680 other subscribed groups they were cross-posted to. If this variable is
10681 neither @code{nil} nor @code{t}, the article will be marked as read in
10682 both subscribed and unsubscribed groups (@pxref{Crosspost Handling}).
10685 @node Crosspost Handling
10686 @section Crosspost Handling
10690 Marking cross-posted articles as read ensures that you'll never have to
10691 read the same article more than once. Unless, of course, somebody has
10692 posted it to several groups separately. Posting the same article to
10693 several groups (not cross-posting) is called @dfn{spamming}, and you are
10694 by law required to send nasty-grams to anyone who perpetrates such a
10695 heinous crime. You may want to try NoCeM handling to filter out spam
10698 Remember: Cross-posting is kinda ok, but posting the same article
10699 separately to several groups is not. Massive cross-posting (aka.
10700 @dfn{velveeta}) is to be avoided at all costs, and you can even use the
10701 @code{gnus-summary-mail-crosspost-complaint} command to complain about
10702 excessive crossposting (@pxref{Summary Mail Commands}).
10704 @cindex cross-posting
10706 @cindex @acronym{NOV}
10707 One thing that may cause Gnus to not do the cross-posting thing
10708 correctly is if you use an @acronym{NNTP} server that supports @sc{xover}
10709 (which is very nice, because it speeds things up considerably) which
10710 does not include the @code{Xref} header in its @acronym{NOV} lines. This is
10711 Evil, but all too common, alas, alack. Gnus tries to Do The Right Thing
10712 even with @sc{xover} by registering the @code{Xref} lines of all
10713 articles you actually read, but if you kill the articles, or just mark
10714 them as read without reading them, Gnus will not get a chance to snoop
10715 the @code{Xref} lines out of these articles, and will be unable to use
10716 the cross reference mechanism.
10718 @cindex LIST overview.fmt
10719 @cindex overview.fmt
10720 To check whether your @acronym{NNTP} server includes the @code{Xref} header
10721 in its overview files, try @samp{telnet your.nntp.server nntp},
10722 @samp{MODE READER} on @code{inn} servers, and then say @samp{LIST
10723 overview.fmt}. This may not work, but if it does, and the last line you
10724 get does not read @samp{Xref:full}, then you should shout and whine at
10725 your news admin until she includes the @code{Xref} header in the
10728 @vindex gnus-nov-is-evil
10729 If you want Gnus to get the @code{Xref}s right all the time, you have to
10730 set @code{gnus-nov-is-evil} to @code{t}, which slows things down
10735 For an alternative approach, @pxref{Duplicate Suppression}.
10738 @node Duplicate Suppression
10739 @section Duplicate Suppression
10741 By default, Gnus tries to make sure that you don't have to read the same
10742 article more than once by utilizing the crossposting mechanism
10743 (@pxref{Crosspost Handling}). However, that simple and efficient
10744 approach may not work satisfactory for some users for various
10749 The @acronym{NNTP} server may fail to generate the @code{Xref} header. This
10750 is evil and not very common.
10753 The @acronym{NNTP} server may fail to include the @code{Xref} header in the
10754 @file{.overview} data bases. This is evil and all too common, alas.
10757 You may be reading the same group (or several related groups) from
10758 different @acronym{NNTP} servers.
10761 You may be getting mail that duplicates articles posted to groups.
10764 I'm sure there are other situations where @code{Xref} handling fails as
10765 well, but these four are the most common situations.
10767 If, and only if, @code{Xref} handling fails for you, then you may
10768 consider switching on @dfn{duplicate suppression}. If you do so, Gnus
10769 will remember the @code{Message-ID}s of all articles you have read or
10770 otherwise marked as read, and then, as if by magic, mark them as read
10771 all subsequent times you see them---in @emph{all} groups. Using this
10772 mechanism is quite likely to be somewhat inefficient, but not overly
10773 so. It's certainly preferable to reading the same articles more than
10776 Duplicate suppression is not a very subtle instrument. It's more like a
10777 sledge hammer than anything else. It works in a very simple
10778 fashion---if you have marked an article as read, it adds this Message-ID
10779 to a cache. The next time it sees this Message-ID, it will mark the
10780 article as read with the @samp{M} mark. It doesn't care what group it
10781 saw the article in.
10784 @item gnus-suppress-duplicates
10785 @vindex gnus-suppress-duplicates
10786 If non-@code{nil}, suppress duplicates.
10788 @item gnus-save-duplicate-list
10789 @vindex gnus-save-duplicate-list
10790 If non-@code{nil}, save the list of duplicates to a file. This will
10791 make startup and shutdown take longer, so the default is @code{nil}.
10792 However, this means that only duplicate articles read in a single Gnus
10793 session are suppressed.
10795 @item gnus-duplicate-list-length
10796 @vindex gnus-duplicate-list-length
10797 This variable says how many @code{Message-ID}s to keep in the duplicate
10798 suppression list. The default is 10000.
10800 @item gnus-duplicate-file
10801 @vindex gnus-duplicate-file
10802 The name of the file to store the duplicate suppression list in. The
10803 default is @file{~/News/suppression}.
10806 If you have a tendency to stop and start Gnus often, setting
10807 @code{gnus-save-duplicate-list} to @code{t} is probably a good idea. If
10808 you leave Gnus running for weeks on end, you may have it @code{nil}. On
10809 the other hand, saving the list makes startup and shutdown much slower,
10810 so that means that if you stop and start Gnus often, you should set
10811 @code{gnus-save-duplicate-list} to @code{nil}. Uhm. I'll leave this up
10812 to you to figure out, I think.
10817 Gnus is able to verify signed messages or decrypt encrypted messages.
10818 The formats that are supported are @acronym{PGP}, @acronym{PGP/MIME}
10819 and @acronym{S/MIME}, however you need some external programs to get
10824 To handle @acronym{PGP} and @acronym{PGP/MIME} messages, you have to
10825 install an OpenPGP implementation such as GnuPG. The Lisp interface
10826 to GnuPG included with Gnus is called PGG (@pxref{Top, ,PGG, pgg, PGG
10827 Manual}), but Mailcrypt and gpg.el are also supported.
10830 To handle @acronym{S/MIME} message, you need to install OpenSSL. OpenSSL 0.9.6
10831 or newer is recommended.
10835 The variables that control security functionality on reading messages
10839 @item mm-verify-option
10840 @vindex mm-verify-option
10841 Option of verifying signed parts. @code{never}, not verify;
10842 @code{always}, always verify; @code{known}, only verify known
10843 protocols. Otherwise, ask user.
10845 @item mm-decrypt-option
10846 @vindex mm-decrypt-option
10847 Option of decrypting encrypted parts. @code{never}, no decryption;
10848 @code{always}, always decrypt; @code{known}, only decrypt known
10849 protocols. Otherwise, ask user.
10852 @vindex mml1991-use
10853 Symbol indicating elisp interface to OpenPGP implementation for
10854 @acronym{PGP} messages. The default is @code{pgg}, but
10855 @code{mailcrypt} and @code{gpg} are also supported although
10859 @vindex mml2015-use
10860 Symbol indicating elisp interface to OpenPGP implementation for
10861 @acronym{PGP/MIME} messages. The default is @code{pgg}, but
10862 @code{mailcrypt} and @code{gpg} are also supported although
10867 By default the buttons that display security information are not
10868 shown, because they clutter reading the actual e-mail. You can type
10869 @kbd{K b} manually to display the information. Use the
10870 @code{gnus-buttonized-mime-types} and
10871 @code{gnus-unbuttonized-mime-types} variables to control this
10872 permanently. @ref{MIME Commands} for further details, and hints on
10873 how to customize these variables to always display security
10876 @cindex snarfing keys
10877 @cindex importing PGP keys
10878 @cindex PGP key ring import
10879 Snarfing OpenPGP keys (i.e., importing keys from articles into your
10880 key ring) is not supported explicitly through a menu item or command,
10881 rather Gnus do detect and label keys as @samp{application/pgp-keys},
10882 allowing you to specify whatever action you think is appropriate
10883 through the usual @acronym{MIME} infrastructure. You can use a
10884 @file{~/.mailcap} entry (@pxref{mailcap, , mailcap, emacs-mime, The
10885 Emacs MIME Manual}) such as the following to import keys using GNU
10886 Privacy Guard when you click on the @acronym{MIME} button
10887 (@pxref{Using MIME}).
10890 application/pgp-keys; gpg --import --interactive --verbose; needsterminal
10893 This happens to also be the default action defined in
10894 @code{mailcap-mime-data}.
10896 More information on how to set things for sending outgoing signed and
10897 encrypted messages up can be found in the message manual
10898 (@pxref{Security, ,Security, message, Message Manual}).
10901 @section Mailing List
10902 @cindex mailing list
10905 @kindex A M (summary)
10906 @findex gnus-mailing-list-insinuate
10907 Gnus understands some mailing list fields of RFC 2369. To enable it,
10908 add a @code{to-list} group parameter (@pxref{Group Parameters}),
10909 possibly using @kbd{A M} (@code{gnus-mailing-list-insinuate}) in the
10912 That enables the following commands to the summary buffer:
10917 @kindex C-c C-n h (Summary)
10918 @findex gnus-mailing-list-help
10919 Send a message to fetch mailing list help, if List-Help field exists.
10922 @kindex C-c C-n s (Summary)
10923 @findex gnus-mailing-list-subscribe
10924 Send a message to subscribe the mailing list, if List-Subscribe field exists.
10927 @kindex C-c C-n u (Summary)
10928 @findex gnus-mailing-list-unsubscribe
10929 Send a message to unsubscribe the mailing list, if List-Unsubscribe
10933 @kindex C-c C-n p (Summary)
10934 @findex gnus-mailing-list-post
10935 Post to the mailing list, if List-Post field exists.
10938 @kindex C-c C-n o (Summary)
10939 @findex gnus-mailing-list-owner
10940 Send a message to the mailing list owner, if List-Owner field exists.
10943 @kindex C-c C-n a (Summary)
10944 @findex gnus-mailing-list-archive
10945 Browse the mailing list archive, if List-Archive field exists.
10950 @node Article Buffer
10951 @chapter Article Buffer
10952 @cindex article buffer
10954 The articles are displayed in the article buffer, of which there is only
10955 one. All the summary buffers share the same article buffer unless you
10956 tell Gnus otherwise.
10959 * Hiding Headers:: Deciding what headers should be displayed.
10960 * Using MIME:: Pushing articles through @acronym{MIME} before reading them.
10961 * Customizing Articles:: Tailoring the look of the articles.
10962 * Article Keymap:: Keystrokes available in the article buffer.
10963 * Misc Article:: Other stuff.
10967 @node Hiding Headers
10968 @section Hiding Headers
10969 @cindex hiding headers
10970 @cindex deleting headers
10972 The top section of each article is the @dfn{head}. (The rest is the
10973 @dfn{body}, but you may have guessed that already.)
10975 @vindex gnus-show-all-headers
10976 There is a lot of useful information in the head: the name of the person
10977 who wrote the article, the date it was written and the subject of the
10978 article. That's well and nice, but there's also lots of information
10979 most people do not want to see---what systems the article has passed
10980 through before reaching you, the @code{Message-ID}, the
10981 @code{References}, etc. ad nauseam---and you'll probably want to get rid
10982 of some of those lines. If you want to keep all those lines in the
10983 article buffer, you can set @code{gnus-show-all-headers} to @code{t}.
10985 Gnus provides you with two variables for sifting headers:
10989 @item gnus-visible-headers
10990 @vindex gnus-visible-headers
10991 If this variable is non-@code{nil}, it should be a regular expression
10992 that says what headers you wish to keep in the article buffer. All
10993 headers that do not match this variable will be hidden.
10995 For instance, if you only want to see the name of the person who wrote
10996 the article and the subject, you'd say:
10999 (setq gnus-visible-headers "^From:\\|^Subject:")
11002 This variable can also be a list of regexps to match headers to
11005 @item gnus-ignored-headers
11006 @vindex gnus-ignored-headers
11007 This variable is the reverse of @code{gnus-visible-headers}. If this
11008 variable is set (and @code{gnus-visible-headers} is @code{nil}), it
11009 should be a regular expression that matches all lines that you want to
11010 hide. All lines that do not match this variable will remain visible.
11012 For instance, if you just want to get rid of the @code{References} line
11013 and the @code{Xref} line, you might say:
11016 (setq gnus-ignored-headers "^References:\\|^Xref:")
11019 This variable can also be a list of regexps to match headers to
11022 Note that if @code{gnus-visible-headers} is non-@code{nil}, this
11023 variable will have no effect.
11027 @vindex gnus-sorted-header-list
11028 Gnus can also sort the headers for you. (It does this by default.) You
11029 can control the sorting by setting the @code{gnus-sorted-header-list}
11030 variable. It is a list of regular expressions that says in what order
11031 the headers are to be displayed.
11033 For instance, if you want the name of the author of the article first,
11034 and then the subject, you might say something like:
11037 (setq gnus-sorted-header-list '("^From:" "^Subject:"))
11040 Any headers that are to remain visible, but are not listed in this
11041 variable, will be displayed in random order after all the headers listed in this variable.
11043 @findex gnus-article-hide-boring-headers
11044 @vindex gnus-boring-article-headers
11045 You can hide further boring headers by setting
11046 @code{gnus-treat-hide-boring-headers} to @code{head}. What this function
11047 does depends on the @code{gnus-boring-article-headers} variable. It's a
11048 list, but this list doesn't actually contain header names. Instead it
11049 lists various @dfn{boring conditions} that Gnus can check and remove
11052 These conditions are:
11055 Remove all empty headers.
11057 Remove the @code{Followup-To} header if it is identical to the
11058 @code{Newsgroups} header.
11060 Remove the @code{Reply-To} header if it lists the same addresses as
11061 the @code{From} header, or if the @code{broken-reply-to} group
11064 Remove the @code{Newsgroups} header if it only contains the current group
11067 Remove the @code{To} header if it only contains the address identical to
11068 the current group's @code{to-address} parameter.
11070 Remove the @code{To} header if it only contains the address identical to
11071 the current group's @code{to-list} parameter.
11073 Remove the @code{CC} header if it only contains the address identical to
11074 the current group's @code{to-list} parameter.
11076 Remove the @code{Date} header if the article is less than three days
11079 Remove the @code{To} header if it is very long.
11081 Remove all @code{To} headers if there are more than one.
11084 To include these three elements, you could say something like:
11087 (setq gnus-boring-article-headers
11088 '(empty followup-to reply-to))
11091 This is also the default value for this variable.
11095 @section Using MIME
11096 @cindex @acronym{MIME}
11098 Mime is a standard for waving your hands through the air, aimlessly,
11099 while people stand around yawning.
11101 @acronym{MIME}, however, is a standard for encoding your articles, aimlessly,
11102 while all newsreaders die of fear.
11104 @acronym{MIME} may specify what character set the article uses, the encoding
11105 of the characters, and it also makes it possible to embed pictures and
11106 other naughty stuff in innocent-looking articles.
11108 @vindex gnus-display-mime-function
11109 @findex gnus-display-mime
11110 Gnus pushes @acronym{MIME} articles through @code{gnus-display-mime-function}
11111 to display the @acronym{MIME} parts. This is @code{gnus-display-mime} by
11112 default, which creates a bundle of clickable buttons that can be used to
11113 display, save and manipulate the @acronym{MIME} objects.
11115 The following commands are available when you have placed point over a
11116 @acronym{MIME} button:
11119 @findex gnus-article-press-button
11120 @item RET (Article)
11121 @kindex RET (Article)
11122 @itemx BUTTON-2 (Article)
11123 Toggle displaying of the @acronym{MIME} object
11124 (@code{gnus-article-press-button}). If built-in viewers can not display
11125 the object, Gnus resorts to external viewers in the @file{mailcap}
11126 files. If a viewer has the @samp{copiousoutput} specification, the
11127 object is displayed inline.
11129 @findex gnus-mime-view-part
11130 @item M-RET (Article)
11131 @kindex M-RET (Article)
11133 Prompt for a method, and then view the @acronym{MIME} object using this
11134 method (@code{gnus-mime-view-part}).
11136 @findex gnus-mime-view-part-as-type
11138 @kindex t (Article)
11139 View the @acronym{MIME} object as if it were a different @acronym{MIME} media type
11140 (@code{gnus-mime-view-part-as-type}).
11142 @findex gnus-mime-view-part-as-charset
11144 @kindex C (Article)
11145 Prompt for a charset, and then view the @acronym{MIME} object using this
11146 charset (@code{gnus-mime-view-part-as-charset}).
11148 @findex gnus-mime-save-part
11150 @kindex o (Article)
11151 Prompt for a file name, and then save the @acronym{MIME} object
11152 (@code{gnus-mime-save-part}).
11154 @findex gnus-mime-save-part-and-strip
11155 @item C-o (Article)
11156 @kindex C-o (Article)
11157 Prompt for a file name, then save the @acronym{MIME} object and strip it from
11158 the article. Then proceed to article editing, where a reasonable
11159 suggestion is being made on how the altered article should look
11160 like. The stripped @acronym{MIME} object will be referred via the
11161 message/external-body @acronym{MIME} type.
11162 (@code{gnus-mime-save-part-and-strip}).
11164 @findex gnus-mime-replace-part
11166 @kindex r (Article)
11167 Prompt for a file name, replace the @acronym{MIME} object with an
11168 external body refering to the file via the message/external-body
11169 @acronym{MIME} type. (@code{gnus-mime-replace-part}).
11171 @findex gnus-mime-delete-part
11173 @kindex d (Article)
11174 Delete the @acronym{MIME} object from the article and replace it with some
11175 information about the removed @acronym{MIME} object
11176 (@code{gnus-mime-delete-part}).
11178 @c FIXME: gnus-auto-select-part should be documented here
11180 @findex gnus-mime-copy-part
11182 @kindex c (Article)
11183 Copy the @acronym{MIME} object to a fresh buffer and display this buffer
11184 (@code{gnus-mime-copy-part}). If given a prefix, copy the raw contents
11185 without decoding. If given a numerical prefix, you can do semi-manual
11186 charset stuff (see @code{gnus-summary-show-article-charset-alist} in
11187 @ref{Paging the Article}). Compressed files like @file{.gz} and
11188 @file{.bz2} are automatically decompressed if
11189 @code{auto-compression-mode} is enabled (@pxref{Compressed Files,,
11190 Accessing Compressed Files, emacs, The Emacs Editor}).
11192 @findex gnus-mime-print-part
11194 @kindex p (Article)
11195 Print the @acronym{MIME} object (@code{gnus-mime-print-part}). This
11196 command respects the @samp{print=} specifications in the
11197 @file{.mailcap} file.
11199 @findex gnus-mime-inline-part
11201 @kindex i (Article)
11202 Insert the contents of the @acronym{MIME} object into the buffer
11203 (@code{gnus-mime-inline-part}) as text/plain. If given a prefix, insert
11204 the raw contents without decoding. If given a numerical prefix, you can
11205 do semi-manual charset stuff (see
11206 @code{gnus-summary-show-article-charset-alist} in @ref{Paging the
11207 Article}). Compressed files like @file{.gz} and @file{.bz2} are
11208 automatically decompressed depending on @code{jka-compr} regardless of
11209 @code{auto-compression-mode} (@pxref{Compressed Files,, Accessing
11210 Compressed Files, emacs, The Emacs Editor}).
11212 @findex gnus-mime-view-part-internally
11214 @kindex E (Article)
11215 View the @acronym{MIME} object with an internal viewer. If no internal
11216 viewer is available, use an external viewer
11217 (@code{gnus-mime-view-part-internally}).
11219 @findex gnus-mime-view-part-externally
11221 @kindex e (Article)
11222 View the @acronym{MIME} object with an external viewer.
11223 (@code{gnus-mime-view-part-externally}).
11225 @findex gnus-mime-pipe-part
11227 @kindex | (Article)
11228 Output the @acronym{MIME} object to a process (@code{gnus-mime-pipe-part}).
11230 @findex gnus-mime-action-on-part
11232 @kindex . (Article)
11233 Interactively run an action on the @acronym{MIME} object
11234 (@code{gnus-mime-action-on-part}).
11238 Gnus will display some @acronym{MIME} objects automatically. The way Gnus
11239 determines which parts to do this with is described in the Emacs
11240 @acronym{MIME} manual.
11242 It might be best to just use the toggling functions from the article
11243 buffer to avoid getting nasty surprises. (For instance, you enter the
11244 group @samp{alt.sing-a-long} and, before you know it, @acronym{MIME} has
11245 decoded the sound file in the article and some horrible sing-a-long song
11246 comes screaming out your speakers, and you can't find the volume button,
11247 because there isn't one, and people are starting to look at you, and you
11248 try to stop the program, but you can't, and you can't find the program
11249 to control the volume, and everybody else in the room suddenly decides
11250 to look at you disdainfully, and you'll feel rather stupid.)
11252 Any similarity to real events and people is purely coincidental. Ahem.
11254 Also @pxref{MIME Commands}.
11257 @node Customizing Articles
11258 @section Customizing Articles
11259 @cindex article customization
11261 A slew of functions for customizing how the articles are to look like
11262 exist. You can call these functions interactively
11263 (@pxref{Article Washing}), or you can have them
11264 called automatically when you select the articles.
11266 To have them called automatically, you should set the corresponding
11267 ``treatment'' variable. For instance, to have headers hidden, you'd set
11268 @code{gnus-treat-hide-headers}. Below is a list of variables that can
11269 be set, but first we discuss the values these variables can have.
11271 Note: Some values, while valid, make little sense. Check the list below
11272 for sensible values.
11276 @code{nil}: Don't do this treatment.
11279 @code{t}: Do this treatment on all body parts.
11282 @code{head}: Do the treatment on the headers.
11285 @code{first}: Do this treatment on the first body part.
11288 @code{last}: Do this treatment on the last body part.
11291 An integer: Do this treatment on all body parts that have a length less
11295 A list of strings: Do this treatment on all body parts that are in
11296 articles that are read in groups that have names that match one of the
11297 regexps in the list.
11300 A list where the first element is not a string:
11302 The list is evaluated recursively. The first element of the list is a
11303 predicate. The following predicates are recognized: @code{or},
11304 @code{and}, @code{not} and @code{typep}. Here's an example:
11308 (typep "text/x-vcard"))
11313 You may have noticed that the word @dfn{part} is used here. This refers
11314 to the fact that some messages are @acronym{MIME} multipart articles that may
11315 be divided into several parts. Articles that are not multiparts are
11316 considered to contain just a single part.
11318 @vindex gnus-article-treat-types
11319 Are the treatments applied to all sorts of multipart parts? Yes, if you
11320 want to, but by default, only @samp{text/plain} parts are given the
11321 treatment. This is controlled by the @code{gnus-article-treat-types}
11322 variable, which is a list of regular expressions that are matched to the
11323 type of the part. This variable is ignored if the value of the
11324 controlling variable is a predicate list, as described above.
11326 The following treatment options are available. The easiest way to
11327 customize this is to examine the @code{gnus-article-treat} customization
11328 group. Values in parenthesis are suggested sensible values. Others are
11329 possible but those listed are probably sufficient for most people.
11332 @item gnus-treat-buttonize (t, integer)
11333 @item gnus-treat-buttonize-head (head)
11335 @xref{Article Buttons}.
11337 @item gnus-treat-capitalize-sentences (t, integer)
11338 @item gnus-treat-overstrike (t, integer)
11339 @item gnus-treat-strip-cr (t, integer)
11340 @item gnus-treat-strip-headers-in-body (t, integer)
11341 @item gnus-treat-strip-leading-blank-lines (t, first, integer)
11342 @item gnus-treat-strip-multiple-blank-lines (t, integer)
11343 @item gnus-treat-strip-pem (t, last, integer)
11344 @item gnus-treat-strip-trailing-blank-lines (t, last, integer)
11345 @item gnus-treat-unsplit-urls (t, integer)
11346 @item gnus-treat-wash-html (t, integer)
11348 @xref{Article Washing}.
11350 @item gnus-treat-date-english (head)
11351 @item gnus-treat-date-iso8601 (head)
11352 @item gnus-treat-date-lapsed (head)
11353 @item gnus-treat-date-local (head)
11354 @item gnus-treat-date-original (head)
11355 @item gnus-treat-date-user-defined (head)
11356 @item gnus-treat-date-ut (head)
11358 @xref{Article Date}.
11360 @item gnus-treat-from-picon (head)
11361 @item gnus-treat-mail-picon (head)
11362 @item gnus-treat-newsgroups-picon (head)
11366 @item gnus-treat-display-smileys (t, integer)
11368 @item gnus-treat-body-boundary (head)
11370 @vindex gnus-body-boundary-delimiter
11371 Adds a delimiter between header and body, the string used as delimiter
11372 is controlled by @code{gnus-body-boundary-delimiter}.
11376 @item gnus-treat-display-x-face (head)
11380 @item gnus-treat-display-face (head)
11384 @item gnus-treat-emphasize (t, head, integer)
11385 @item gnus-treat-fill-article (t, integer)
11386 @item gnus-treat-fill-long-lines (t, integer)
11387 @item gnus-treat-hide-boring-headers (head)
11388 @item gnus-treat-hide-citation (t, integer)
11389 @item gnus-treat-hide-citation-maybe (t, integer)
11390 @item gnus-treat-hide-headers (head)
11391 @item gnus-treat-hide-signature (t, last)
11392 @item gnus-treat-strip-banner (t, last)
11393 @item gnus-treat-strip-list-identifiers (head)
11395 @xref{Article Hiding}.
11397 @item gnus-treat-highlight-citation (t, integer)
11398 @item gnus-treat-highlight-headers (head)
11399 @item gnus-treat-highlight-signature (t, last, integer)
11401 @xref{Article Highlighting}.
11403 @item gnus-treat-play-sounds
11404 @item gnus-treat-translate
11405 @item gnus-treat-ansi-sequences (t)
11406 @item gnus-treat-x-pgp-sig (head)
11408 @item gnus-treat-unfold-headers (head)
11409 @item gnus-treat-fold-headers (head)
11410 @item gnus-treat-fold-newsgroups (head)
11411 @item gnus-treat-leading-whitespace (head)
11413 @xref{Article Header}.
11418 @vindex gnus-part-display-hook
11419 You can, of course, write your own functions to be called from
11420 @code{gnus-part-display-hook}. The functions are called narrowed to the
11421 part, and you can do anything you like, pretty much. There is no
11422 information that you have to keep in the buffer---you can change
11426 @node Article Keymap
11427 @section Article Keymap
11429 Most of the keystrokes in the summary buffer can also be used in the
11430 article buffer. They should behave as if you typed them in the summary
11431 buffer, which means that you don't actually have to have a summary
11432 buffer displayed while reading. You can do it all from the article
11435 @kindex v (Article)
11436 @cindex keys, reserved for users (Article)
11437 The key @kbd{v} is reserved for users. You can bind it key to some
11438 function or better use it as a prefix key.
11440 A few additional keystrokes are available:
11445 @kindex SPACE (Article)
11446 @findex gnus-article-next-page
11447 Scroll forwards one page (@code{gnus-article-next-page}).
11448 This is exactly the same as @kbd{h SPACE h}.
11451 @kindex DEL (Article)
11452 @findex gnus-article-prev-page
11453 Scroll backwards one page (@code{gnus-article-prev-page}).
11454 This is exactly the same as @kbd{h DEL h}.
11457 @kindex C-c ^ (Article)
11458 @findex gnus-article-refer-article
11459 If point is in the neighborhood of a @code{Message-ID} and you press
11460 @kbd{C-c ^}, Gnus will try to get that article from the server
11461 (@code{gnus-article-refer-article}).
11464 @kindex C-c C-m (Article)
11465 @findex gnus-article-mail
11466 Send a reply to the address near point (@code{gnus-article-mail}). If
11467 given a prefix, include the mail.
11470 @kindex s (Article)
11471 @findex gnus-article-show-summary
11472 Reconfigure the buffers so that the summary buffer becomes visible
11473 (@code{gnus-article-show-summary}).
11476 @kindex ? (Article)
11477 @findex gnus-article-describe-briefly
11478 Give a very brief description of the available keystrokes
11479 (@code{gnus-article-describe-briefly}).
11482 @kindex TAB (Article)
11483 @findex gnus-article-next-button
11484 Go to the next button, if any (@code{gnus-article-next-button}). This
11485 only makes sense if you have buttonizing turned on.
11488 @kindex M-TAB (Article)
11489 @findex gnus-article-prev-button
11490 Go to the previous button, if any (@code{gnus-article-prev-button}).
11493 @kindex R (Article)
11494 @findex gnus-article-reply-with-original
11495 Send a reply to the current article and yank the current article
11496 (@code{gnus-article-reply-with-original}). If given a prefix, make a
11497 wide reply. If the region is active, only yank the text in the
11501 @kindex F (Article)
11502 @findex gnus-article-followup-with-original
11503 Send a followup to the current article and yank the current article
11504 (@code{gnus-article-followup-with-original}). If given a prefix, make
11505 a wide reply. If the region is active, only yank the text in the
11513 @section Misc Article
11517 @item gnus-single-article-buffer
11518 @vindex gnus-single-article-buffer
11519 If non-@code{nil}, use the same article buffer for all the groups.
11520 (This is the default.) If @code{nil}, each group will have its own
11523 @vindex gnus-article-decode-hook
11524 @item gnus-article-decode-hook
11525 @cindex @acronym{MIME}
11526 Hook used to decode @acronym{MIME} articles. The default value is
11527 @code{(article-decode-charset article-decode-encoded-words)}
11529 @vindex gnus-article-prepare-hook
11530 @item gnus-article-prepare-hook
11531 This hook is called right after the article has been inserted into the
11532 article buffer. It is mainly intended for functions that do something
11533 depending on the contents; it should probably not be used for changing
11534 the contents of the article buffer.
11536 @item gnus-article-mode-hook
11537 @vindex gnus-article-mode-hook
11538 Hook called in article mode buffers.
11540 @item gnus-article-mode-syntax-table
11541 @vindex gnus-article-mode-syntax-table
11542 Syntax table used in article buffers. It is initialized from
11543 @code{text-mode-syntax-table}.
11545 @vindex gnus-article-over-scroll
11546 @item gnus-article-over-scroll
11547 If non-@code{nil}, allow scrolling the article buffer even when there
11548 no more new text to scroll in. The default is @code{nil}.
11550 @vindex gnus-article-mode-line-format
11551 @item gnus-article-mode-line-format
11552 This variable is a format string along the same lines as
11553 @code{gnus-summary-mode-line-format} (@pxref{Summary Buffer Mode
11554 Line}). It accepts the same format specifications as that variable,
11555 with two extensions:
11560 The @dfn{wash status} of the article. This is a short string with one
11561 character for each possible article wash operation that may have been
11562 performed. The characters and their meaning:
11567 Displayed when cited text may be hidden in the article buffer.
11570 Displayed when headers are hidden in the article buffer.
11573 Displayed when article is digitally signed or encrypted, and Gnus has
11574 hidden the security headers. (N.B. does not tell anything about
11575 security status, i.e. good or bad signature.)
11578 Displayed when the signature has been hidden in the Article buffer.
11581 Displayed when Gnus has treated overstrike characters in the article buffer.
11584 Displayed when Gnus has treated emphasised strings in the article buffer.
11589 The number of @acronym{MIME} parts in the article.
11593 @vindex gnus-break-pages
11595 @item gnus-break-pages
11596 Controls whether @dfn{page breaking} is to take place. If this variable
11597 is non-@code{nil}, the articles will be divided into pages whenever a
11598 page delimiter appears in the article. If this variable is @code{nil},
11599 paging will not be done.
11601 @item gnus-page-delimiter
11602 @vindex gnus-page-delimiter
11603 This is the delimiter mentioned above. By default, it is @samp{^L}
11607 @cindex internationalized domain names
11608 @vindex gnus-use-idna
11609 @item gnus-use-idna
11610 This variable controls whether Gnus performs IDNA decoding of
11611 internationalized domain names inside @samp{From}, @samp{To} and
11612 @samp{Cc} headers. @xref{IDNA, ,IDNA,message, The Message Manual},
11613 for how to compose such messages. This requires
11614 @uref{http://www.gnu.org/software/libidn/, GNU Libidn}, and this
11615 variable is only enabled if you have installed it.
11620 @node Composing Messages
11621 @chapter Composing Messages
11622 @cindex composing messages
11625 @cindex sending mail
11630 @cindex using s/mime
11631 @cindex using smime
11633 @kindex C-c C-c (Post)
11634 All commands for posting and mailing will put you in a message buffer
11635 where you can edit the article all you like, before you send the
11636 article by pressing @kbd{C-c C-c}. @xref{Top, , Overview, message,
11637 Message Manual}. Where the message will be posted/mailed to depends
11638 on your setup (@pxref{Posting Server}).
11641 * Mail:: Mailing and replying.
11642 * Posting Server:: What server should you post and mail via?
11643 * POP before SMTP:: You cannot send a mail unless you read a mail.
11644 * Mail and Post:: Mailing and posting at the same time.
11645 * Archived Messages:: Where Gnus stores the messages you've sent.
11646 * Posting Styles:: An easier way to specify who you are.
11647 * Drafts:: Postponing messages and rejected messages.
11648 * Rejected Articles:: What happens if the server doesn't like your article?
11649 * Signing and encrypting:: How to compose secure messages.
11652 Also @pxref{Canceling and Superseding} for information on how to
11653 remove articles you shouldn't have posted.
11659 Variables for customizing outgoing mail:
11662 @item gnus-uu-digest-headers
11663 @vindex gnus-uu-digest-headers
11664 List of regexps to match headers included in digested messages. The
11665 headers will be included in the sequence they are matched. If
11666 @code{nil} include all headers.
11668 @item gnus-add-to-list
11669 @vindex gnus-add-to-list
11670 If non-@code{nil}, add a @code{to-list} group parameter to mail groups
11671 that have none when you do a @kbd{a}.
11673 @item gnus-confirm-mail-reply-to-news
11674 @vindex gnus-confirm-mail-reply-to-news
11675 If non-@code{nil}, Gnus will ask you for a confirmation when you are
11676 about to reply to news articles by mail. If it is @code{nil}, nothing
11677 interferes in what you want to do. This can also be a function
11678 receiving the group name as the only parameter which should return
11679 non-@code{nil} if a confirmation is needed, or a regular expression
11680 matching group names, where confirmation should be asked for.
11682 If you find yourself never wanting to reply to mail, but occasionally
11683 press @kbd{R} anyway, this variable might be for you.
11685 @item gnus-confirm-treat-mail-like-news
11686 @vindex gnus-confirm-treat-mail-like-news
11687 If non-@code{nil}, Gnus also requests confirmation according to
11688 @code{gnus-confirm-mail-reply-to-news} when replying to mail. This is
11689 useful for treating mailing lists like newsgroups.
11694 @node Posting Server
11695 @section Posting Server
11697 When you press those magical @kbd{C-c C-c} keys to ship off your latest
11698 (extremely intelligent, of course) article, where does it go?
11700 Thank you for asking. I hate you.
11702 It can be quite complicated.
11704 @vindex gnus-post-method
11705 When posting news, Message usually invokes @code{message-send-news}
11706 (@pxref{News Variables, , News Variables, message, Message Manual}).
11707 Normally, Gnus will post using the same select method as you're
11708 reading from (which might be convenient if you're reading lots of
11709 groups from different private servers). However. If the server
11710 you're reading from doesn't allow posting, just reading, you probably
11711 want to use some other server to post your (extremely intelligent and
11712 fabulously interesting) articles. You can then set the
11713 @code{gnus-post-method} to some other method:
11716 (setq gnus-post-method '(nnspool ""))
11719 Now, if you've done this, and then this server rejects your article, or
11720 this server is down, what do you do then? To override this variable you
11721 can use a non-zero prefix to the @kbd{C-c C-c} command to force using
11722 the ``current'' server, to get back the default behavior, for posting.
11724 If you give a zero prefix (i.e., @kbd{C-u 0 C-c C-c}) to that command,
11725 Gnus will prompt you for what method to use for posting.
11727 You can also set @code{gnus-post-method} to a list of select methods.
11728 If that's the case, Gnus will always prompt you for what method to use
11731 Finally, if you want to always post using the native select method,
11732 you can set this variable to @code{native}.
11734 When sending mail, Message invokes @code{message-send-mail-function}.
11735 The default function, @code{message-send-mail-with-sendmail}, pipes
11736 your article to the @code{sendmail} binary for further queuing and
11737 sending. When your local system is not configured for sending mail
11738 using @code{sendmail}, and you have access to a remote @acronym{SMTP}
11739 server, you can set @code{message-send-mail-function} to
11740 @code{smtpmail-send-it} and make sure to setup the @code{smtpmail}
11741 package correctly. An example:
11744 (setq message-send-mail-function 'smtpmail-send-it
11745 smtpmail-default-smtp-server "YOUR SMTP HOST")
11748 To the thing similar to this, there is
11749 @code{message-smtpmail-send-it}. It is useful if your @acronym{ISP}
11750 requires the @acronym{POP}-before-@acronym{SMTP} authentication.
11751 @xref{POP before SMTP}.
11753 Other possible choices for @code{message-send-mail-function} includes
11754 @code{message-send-mail-with-mh}, @code{message-send-mail-with-qmail},
11755 and @code{feedmail-send-it}.
11757 @node POP before SMTP
11758 @section POP before SMTP
11759 @cindex pop before smtp
11760 @findex message-smtpmail-send-it
11761 @findex mail-source-touch-pop
11763 Does your @acronym{ISP} require the @acronym{POP}-before-@acronym{SMTP}
11764 authentication? It is whether you need to connect to the @acronym{POP}
11765 mail server within a certain time before sending mails. If so, there is
11766 a convenient way. To do that, put the following lines in your
11767 @file{~/.gnus.el} file:
11770 (setq message-send-mail-function 'message-smtpmail-send-it)
11771 (add-hook 'message-send-mail-hook 'mail-source-touch-pop)
11775 It means to let Gnus connect to the @acronym{POP} mail server in advance
11776 whenever you send a mail. The @code{mail-source-touch-pop} function
11777 does only a @acronym{POP} authentication according to the value of
11778 @code{mail-sources} without fetching mails, just before sending a mail.
11779 Note that you have to use @code{message-smtpmail-send-it} which runs
11780 @code{message-send-mail-hook} rather than @code{smtpmail-send-it} and
11781 set the value of @code{mail-sources} for a @acronym{POP} connection
11782 correctly. @xref{Mail Sources}.
11784 If you have two or more @acronym{POP} mail servers set in
11785 @code{mail-sources}, you may want to specify one of them to
11786 @code{mail-source-primary-source} as the @acronym{POP} mail server to be
11787 used for the @acronym{POP}-before-@acronym{SMTP} authentication. If it
11788 is your primary @acronym{POP} mail server (i.e., you are fetching mails
11789 mainly from that server), you can set it permanently as follows:
11792 (setq mail-source-primary-source
11793 '(pop :server "pop3.mail.server"
11794 :password "secret"))
11798 Otherwise, bind it dynamically only when performing the
11799 @acronym{POP}-before-@acronym{SMTP} authentication as follows:
11802 (add-hook 'message-send-mail-hook
11804 (let ((mail-source-primary-source
11805 '(pop :server "pop3.mail.server"
11806 :password "secret")))
11807 (mail-source-touch-pop))))
11810 @node Mail and Post
11811 @section Mail and Post
11813 Here's a list of variables relevant to both mailing and
11817 @item gnus-mailing-list-groups
11818 @findex gnus-mailing-list-groups
11819 @cindex mailing lists
11821 If your news server offers groups that are really mailing lists
11822 gatewayed to the @acronym{NNTP} server, you can read those groups without
11823 problems, but you can't post/followup to them without some difficulty.
11824 One solution is to add a @code{to-address} to the group parameters
11825 (@pxref{Group Parameters}). An easier thing to do is set the
11826 @code{gnus-mailing-list-groups} to a regexp that matches the groups that
11827 really are mailing lists. Then, at least, followups to the mailing
11828 lists will work most of the time. Posting to these groups (@kbd{a}) is
11829 still a pain, though.
11831 @item gnus-user-agent
11832 @vindex gnus-user-agent
11835 This variable controls which information should be exposed in the
11836 User-Agent header. It can be one of the symbols @code{gnus} (show only
11837 Gnus version), @code{emacs-gnus} (show only Emacs and Gnus versions),
11838 @code{emacs-gnus-config} (same as @code{emacs-gnus} plus system
11839 configuration), @code{emacs-gnus-type} (same as @code{emacs-gnus} plus
11840 system type) or a custom string. If you set it to a string, be sure to
11841 use a valid format, see RFC 2616.
11845 You may want to do spell-checking on messages that you send out. Or, if
11846 you don't want to spell-check by hand, you could add automatic
11847 spell-checking via the @code{ispell} package:
11850 @findex ispell-message
11852 (add-hook 'message-send-hook 'ispell-message)
11855 If you want to change the @code{ispell} dictionary based on what group
11856 you're in, you could say something like the following:
11859 (add-hook 'gnus-select-group-hook
11863 "^de\\." (gnus-group-real-name gnus-newsgroup-name))
11864 (ispell-change-dictionary "deutsch"))
11866 (ispell-change-dictionary "english")))))
11869 Modify to suit your needs.
11872 @node Archived Messages
11873 @section Archived Messages
11874 @cindex archived messages
11875 @cindex sent messages
11877 Gnus provides a few different methods for storing the mail and news you
11878 send. The default method is to use the @dfn{archive virtual server} to
11879 store the messages. If you want to disable this completely, the
11880 @code{gnus-message-archive-group} variable should be @code{nil}, which
11883 For archiving interesting messages in a group you read, see the
11884 @kbd{B c} (@code{gnus-summary-copy-article}) command (@pxref{Mail
11887 @vindex gnus-message-archive-method
11888 @code{gnus-message-archive-method} says what virtual server Gnus is to
11889 use to store sent messages. The default is:
11892 (nnfolder "archive"
11893 (nnfolder-directory "~/Mail/archive")
11894 (nnfolder-active-file "~/Mail/archive/active")
11895 (nnfolder-get-new-mail nil)
11896 (nnfolder-inhibit-expiry t))
11899 You can, however, use any mail select method (@code{nnml},
11900 @code{nnmbox}, etc.). @code{nnfolder} is a quite likable select method
11901 for doing this sort of thing, though. If you don't like the default
11902 directory chosen, you could say something like:
11905 (setq gnus-message-archive-method
11906 '(nnfolder "archive"
11907 (nnfolder-inhibit-expiry t)
11908 (nnfolder-active-file "~/News/sent-mail/active")
11909 (nnfolder-directory "~/News/sent-mail/")))
11912 @vindex gnus-message-archive-group
11914 Gnus will insert @code{Gcc} headers in all outgoing messages that point
11915 to one or more group(s) on that server. Which group to use is
11916 determined by the @code{gnus-message-archive-group} variable.
11918 This variable can be used to do the following:
11922 Messages will be saved in that group.
11924 Note that you can include a select method in the group name, then the
11925 message will not be stored in the select method given by
11926 @code{gnus-message-archive-method}, but in the select method specified
11927 by the group name, instead. Suppose @code{gnus-message-archive-method}
11928 has the default value shown above. Then setting
11929 @code{gnus-message-archive-group} to @code{"foo"} means that outgoing
11930 messages are stored in @samp{nnfolder+archive:foo}, but if you use the
11931 value @code{"nnml:foo"}, then outgoing messages will be stored in
11934 @item a list of strings
11935 Messages will be saved in all those groups.
11937 @item an alist of regexps, functions and forms
11938 When a key ``matches'', the result is used.
11941 No message archiving will take place. This is the default.
11946 Just saving to a single group called @samp{MisK}:
11948 (setq gnus-message-archive-group "MisK")
11951 Saving to two groups, @samp{MisK} and @samp{safe}:
11953 (setq gnus-message-archive-group '("MisK" "safe"))
11956 Save to different groups based on what group you are in:
11958 (setq gnus-message-archive-group
11959 '(("^alt" "sent-to-alt")
11960 ("mail" "sent-to-mail")
11961 (".*" "sent-to-misc")))
11964 More complex stuff:
11966 (setq gnus-message-archive-group
11967 '((if (message-news-p)
11972 How about storing all news messages in one file, but storing all mail
11973 messages in one file per month:
11976 (setq gnus-message-archive-group
11977 '((if (message-news-p)
11979 (concat "mail." (format-time-string "%Y-%m")))))
11982 @c (XEmacs 19.13 doesn't have @code{format-time-string}, so you'll have to
11983 @c use a different value for @code{gnus-message-archive-group} there.)
11985 Now, when you send a message off, it will be stored in the appropriate
11986 group. (If you want to disable storing for just one particular message,
11987 you can just remove the @code{Gcc} header that has been inserted.) The
11988 archive group will appear in the group buffer the next time you start
11989 Gnus, or the next time you press @kbd{F} in the group buffer. You can
11990 enter it and read the articles in it just like you'd read any other
11991 group. If the group gets really big and annoying, you can simply rename
11992 if (using @kbd{G r} in the group buffer) to something
11993 nice---@samp{misc-mail-september-1995}, or whatever. New messages will
11994 continue to be stored in the old (now empty) group.
11996 That's the default method of archiving sent messages. Gnus offers a
11997 different way for the people who don't like the default method. In that
11998 case you should set @code{gnus-message-archive-group} to @code{nil};
11999 this will disable archiving.
12002 @item gnus-outgoing-message-group
12003 @vindex gnus-outgoing-message-group
12004 All outgoing messages will be put in this group. If you want to store
12005 all your outgoing mail and articles in the group @samp{nnml:archive},
12006 you set this variable to that value. This variable can also be a list of
12009 If you want to have greater control over what group to put each
12010 message in, you can set this variable to a function that checks the
12011 current newsgroup name and then returns a suitable group name (or list
12014 This variable can be used instead of @code{gnus-message-archive-group},
12015 but the latter is the preferred method.
12017 @item gnus-gcc-mark-as-read
12018 @vindex gnus-gcc-mark-as-read
12019 If non-@code{nil}, automatically mark @code{Gcc} articles as read.
12021 @item gnus-gcc-externalize-attachments
12022 @vindex gnus-gcc-externalize-attachments
12023 If @code{nil}, attach files as normal parts in Gcc copies; if a regexp
12024 and matches the Gcc group name, attach files as external parts; if it is
12025 @code{all}, attach local files as external parts; if it is other
12026 non-@code{nil}, the behavior is the same as @code{all}, but it may be
12027 changed in the future.
12032 @node Posting Styles
12033 @section Posting Styles
12034 @cindex posting styles
12037 All them variables, they make my head swim.
12039 So what if you want a different @code{Organization} and signature based
12040 on what groups you post to? And you post both from your home machine
12041 and your work machine, and you want different @code{From} lines, and so
12044 @vindex gnus-posting-styles
12045 One way to do stuff like that is to write clever hooks that change the
12046 variables you need to have changed. That's a bit boring, so somebody
12047 came up with the bright idea of letting the user specify these things in
12048 a handy alist. Here's an example of a @code{gnus-posting-styles}
12053 (signature "Peace and happiness")
12054 (organization "What me?"))
12056 (signature "Death to everybody"))
12057 ("comp.emacs.i-love-it"
12058 (organization "Emacs is it")))
12061 As you might surmise from this example, this alist consists of several
12062 @dfn{styles}. Each style will be applicable if the first element
12063 ``matches'', in some form or other. The entire alist will be iterated
12064 over, from the beginning towards the end, and each match will be
12065 applied, which means that attributes in later styles that match override
12066 the same attributes in earlier matching styles. So
12067 @samp{comp.programming.literate} will have the @samp{Death to everybody}
12068 signature and the @samp{What me?} @code{Organization} header.
12070 The first element in each style is called the @code{match}. If it's a
12071 string, then Gnus will try to regexp match it against the group name.
12072 If it is the form @code{(header @var{match} @var{regexp})}, then Gnus
12073 will look in the original article for a header whose name is
12074 @var{match} and compare that @var{regexp}. @var{match} and
12075 @var{regexp} are strings. (The original article is the one you are
12076 replying or following up to. If you are not composing a reply or a
12077 followup, then there is nothing to match against.) If the
12078 @code{match} is a function symbol, that function will be called with
12079 no arguments. If it's a variable symbol, then the variable will be
12080 referenced. If it's a list, then that list will be @code{eval}ed. In
12081 any case, if this returns a non-@code{nil} value, then the style is
12082 said to @dfn{match}.
12084 Each style may contain an arbitrary amount of @dfn{attributes}. Each
12085 attribute consists of a @code{(@var{name} @var{value})} pair. In
12086 addition, you can also use the @code{(@var{name} :file @var{value})}
12087 form or the @code{(@var{name} :value @var{value})} form. Where
12088 @code{:file} signifies @var{value} represents a file name and its
12089 contents should be used as the attribute value, @code{:value} signifies
12090 @var{value} does not represent a file name explicitly. The attribute
12091 name can be one of:
12094 @item @code{signature}
12095 @item @code{signature-file}
12096 @item @code{x-face-file}
12097 @item @code{address}, overriding @code{user-mail-address}
12098 @item @code{name}, overriding @code{(user-full-name)}
12102 The attribute name can also be a string or a symbol. In that case,
12103 this will be used as a header name, and the value will be inserted in
12104 the headers of the article; if the value is @code{nil}, the header
12105 name will be removed. If the attribute name is @code{eval}, the form
12106 is evaluated, and the result is thrown away.
12108 The attribute value can be a string (used verbatim), a function with
12109 zero arguments (the return value will be used), a variable (its value
12110 will be used) or a list (it will be @code{eval}ed and the return value
12111 will be used). The functions and sexps are called/@code{eval}ed in the
12112 message buffer that is being set up. The headers of the current article
12113 are available through the @code{message-reply-headers} variable, which
12114 is a vector of the following headers: number subject from date id
12115 references chars lines xref extra.
12117 @vindex message-reply-headers
12119 If you wish to check whether the message you are about to compose is
12120 meant to be a news article or a mail message, you can check the values
12121 of the @code{message-news-p} and @code{message-mail-p} functions.
12123 @findex message-mail-p
12124 @findex message-news-p
12126 So here's a new example:
12129 (setq gnus-posting-styles
12131 (signature-file "~/.signature")
12133 (x-face-file "~/.xface")
12134 (x-url (getenv "WWW_HOME"))
12135 (organization "People's Front Against MWM"))
12137 (signature my-funny-signature-randomizer))
12138 ((equal (system-name) "gnarly") ;; @r{A form}
12139 (signature my-quote-randomizer))
12140 (message-news-p ;; @r{A function symbol}
12141 (signature my-news-signature))
12142 (window-system ;; @r{A value symbol}
12143 ("X-Window-System" (format "%s" window-system)))
12144 ;; @r{If I'm replying to Larsi, set the Organization header.}
12145 ((header "from" "larsi.*org")
12146 (Organization "Somewhere, Inc."))
12147 ((posting-from-work-p) ;; @r{A user defined function}
12148 (signature-file "~/.work-signature")
12149 (address "user@@bar.foo")
12150 (body "You are fired.\n\nSincerely, your boss.")
12151 (organization "Important Work, Inc"))
12153 (From (save-excursion
12154 (set-buffer gnus-article-buffer)
12155 (message-fetch-field "to"))))
12157 (signature-file "~/.mail-signature"))))
12160 The @samp{nnml:.*} rule means that you use the @code{To} address as the
12161 @code{From} address in all your outgoing replies, which might be handy
12162 if you fill many roles.
12169 If you are writing a message (mail or news) and suddenly remember that
12170 you have a steak in the oven (or some pesto in the food processor, you
12171 craaazy vegetarians), you'll probably wish there was a method to save
12172 the message you are writing so that you can continue editing it some
12173 other day, and send it when you feel its finished.
12175 Well, don't worry about it. Whenever you start composing a message of
12176 some sort using the Gnus mail and post commands, the buffer you get will
12177 automatically associate to an article in a special @dfn{draft} group.
12178 If you save the buffer the normal way (@kbd{C-x C-s}, for instance), the
12179 article will be saved there. (Auto-save files also go to the draft
12183 @vindex nndraft-directory
12184 The draft group is a special group (which is implemented as an
12185 @code{nndraft} group, if you absolutely have to know) called
12186 @samp{nndraft:drafts}. The variable @code{nndraft-directory} says where
12187 @code{nndraft} is to store its files. What makes this group special is
12188 that you can't tick any articles in it or mark any articles as
12189 read---all articles in the group are permanently unread.
12191 If the group doesn't exist, it will be created and you'll be subscribed
12192 to it. The only way to make it disappear from the Group buffer is to
12193 unsubscribe it. The special properties of the draft group comes from
12194 a group property (@pxref{Group Parameters}), and if lost the group
12195 behaves like any other group. This means the commands below will not
12196 be available. To restore the special properties of the group, the
12197 simplest way is to kill the group, using @kbd{C-k}, and restart
12198 Gnus. The group is automatically created again with the
12199 correct parameters. The content of the group is not lost.
12201 @c @findex gnus-dissociate-buffer-from-draft
12202 @c @kindex C-c M-d (Mail)
12203 @c @kindex C-c M-d (Post)
12204 @c @findex gnus-associate-buffer-with-draft
12205 @c @kindex C-c C-d (Mail)
12206 @c @kindex C-c C-d (Post)
12207 @c If you're writing some super-secret message that you later want to
12208 @c encode with PGP before sending, you may wish to turn the auto-saving
12209 @c (and association with the draft group) off. You never know who might be
12210 @c interested in reading all your extremely valuable and terribly horrible
12211 @c and interesting secrets. The @kbd{C-c M-d}
12212 @c (@code{gnus-dissociate-buffer-from-draft}) command does that for you.
12213 @c If you change your mind and want to turn the auto-saving back on again,
12214 @c @kbd{C-c C-d} (@code{gnus-associate-buffer-with-draft} does that.
12216 @c @vindex gnus-use-draft
12217 @c To leave association with the draft group off by default, set
12218 @c @code{gnus-use-draft} to @code{nil}. It is @code{t} by default.
12220 @findex gnus-draft-edit-message
12221 @kindex D e (Draft)
12222 When you want to continue editing the article, you simply enter the
12223 draft group and push @kbd{D e} (@code{gnus-draft-edit-message}) to do
12224 that. You will be placed in a buffer where you left off.
12226 Rejected articles will also be put in this draft group (@pxref{Rejected
12229 @findex gnus-draft-send-all-messages
12230 @kindex D s (Draft)
12231 @findex gnus-draft-send-message
12232 @kindex D S (Draft)
12233 If you have lots of rejected messages you want to post (or mail) without
12234 doing further editing, you can use the @kbd{D s} command
12235 (@code{gnus-draft-send-message}). This command understands the
12236 process/prefix convention (@pxref{Process/Prefix}). The @kbd{D S}
12237 command (@code{gnus-draft-send-all-messages}) will ship off all messages
12240 @findex gnus-draft-toggle-sending
12241 @kindex D t (Draft)
12242 If you have some messages that you wish not to send, you can use the
12243 @kbd{D t} (@code{gnus-draft-toggle-sending}) command to mark the message
12244 as unsendable. This is a toggling command.
12247 @node Rejected Articles
12248 @section Rejected Articles
12249 @cindex rejected articles
12251 Sometimes a news server will reject an article. Perhaps the server
12252 doesn't like your face. Perhaps it just feels miserable. Perhaps
12253 @emph{there be demons}. Perhaps you have included too much cited text.
12254 Perhaps the disk is full. Perhaps the server is down.
12256 These situations are, of course, totally beyond the control of Gnus.
12257 (Gnus, of course, loves the way you look, always feels great, has angels
12258 fluttering around inside of it, doesn't care about how much cited text
12259 you include, never runs full and never goes down.) So Gnus saves these
12260 articles until some later time when the server feels better.
12262 The rejected articles will automatically be put in a special draft group
12263 (@pxref{Drafts}). When the server comes back up again, you'd then
12264 typically enter that group and send all the articles off.
12266 @node Signing and encrypting
12267 @section Signing and encrypting
12269 @cindex using s/mime
12270 @cindex using smime
12272 Gnus can digitally sign and encrypt your messages, using vanilla
12273 @acronym{PGP} format or @acronym{PGP/MIME} or @acronym{S/MIME}. For
12274 decoding such messages, see the @code{mm-verify-option} and
12275 @code{mm-decrypt-option} options (@pxref{Security}).
12277 @vindex gnus-message-replysign
12278 @vindex gnus-message-replyencrypt
12279 @vindex gnus-message-replysignencrypted
12280 Often, you would like to sign replies to people who send you signed
12281 messages. Even more often, you might want to encrypt messages which
12282 are in reply to encrypted messages. Gnus offers
12283 @code{gnus-message-replysign} to enable the former, and
12284 @code{gnus-message-replyencrypt} for the latter. In addition, setting
12285 @code{gnus-message-replysignencrypted} (on by default) will sign
12286 automatically encrypted messages.
12288 Instructing @acronym{MML} to perform security operations on a
12289 @acronym{MIME} part is done using the @kbd{C-c C-m s} key map for
12290 signing and the @kbd{C-c C-m c} key map for encryption, as follows.
12295 @kindex C-c C-m s s (Message)
12296 @findex mml-secure-message-sign-smime
12298 Digitally sign current message using @acronym{S/MIME}.
12301 @kindex C-c C-m s o (Message)
12302 @findex mml-secure-message-sign-pgp
12304 Digitally sign current message using @acronym{PGP}.
12307 @kindex C-c C-m s p (Message)
12308 @findex mml-secure-message-sign-pgp
12310 Digitally sign current message using @acronym{PGP/MIME}.
12313 @kindex C-c C-m c s (Message)
12314 @findex mml-secure-message-encrypt-smime
12316 Digitally encrypt current message using @acronym{S/MIME}.
12319 @kindex C-c C-m c o (Message)
12320 @findex mml-secure-message-encrypt-pgp
12322 Digitally encrypt current message using @acronym{PGP}.
12325 @kindex C-c C-m c p (Message)
12326 @findex mml-secure-message-encrypt-pgpmime
12328 Digitally encrypt current message using @acronym{PGP/MIME}.
12331 @kindex C-c C-m C-n (Message)
12332 @findex mml-unsecure-message
12333 Remove security related @acronym{MML} tags from message.
12337 @xref{Security, ,Security, message, Message Manual}, for more information.
12339 @node Select Methods
12340 @chapter Select Methods
12341 @cindex foreign groups
12342 @cindex select methods
12344 A @dfn{foreign group} is a group not read by the usual (or
12345 default) means. It could be, for instance, a group from a different
12346 @acronym{NNTP} server, it could be a virtual group, or it could be your own
12347 personal mail group.
12349 A foreign group (or any group, really) is specified by a @dfn{name} and
12350 a @dfn{select method}. To take the latter first, a select method is a
12351 list where the first element says what back end to use (e.g. @code{nntp},
12352 @code{nnspool}, @code{nnml}) and the second element is the @dfn{server
12353 name}. There may be additional elements in the select method, where the
12354 value may have special meaning for the back end in question.
12356 One could say that a select method defines a @dfn{virtual server}---so
12357 we do just that (@pxref{Server Buffer}).
12359 The @dfn{name} of the group is the name the back end will recognize the
12362 For instance, the group @samp{soc.motss} on the @acronym{NNTP} server
12363 @samp{some.where.edu} will have the name @samp{soc.motss} and select
12364 method @code{(nntp "some.where.edu")}. Gnus will call this group
12365 @samp{nntp+some.where.edu:soc.motss}, even though the @code{nntp}
12366 back end just knows this group as @samp{soc.motss}.
12368 The different methods all have their peculiarities, of course.
12371 * Server Buffer:: Making and editing virtual servers.
12372 * Getting News:: Reading USENET news with Gnus.
12373 * Getting Mail:: Reading your personal mail with Gnus.
12374 * Browsing the Web:: Getting messages from a plethora of Web sources.
12375 * IMAP:: Using Gnus as a @acronym{IMAP} client.
12376 * Other Sources:: Reading directories, files, SOUP packets.
12377 * Combined Groups:: Combining groups into one group.
12378 * Email Based Diary:: Using mails to manage diary events in Gnus.
12379 * Gnus Unplugged:: Reading news and mail offline.
12383 @node Server Buffer
12384 @section Server Buffer
12386 Traditionally, a @dfn{server} is a machine or a piece of software that
12387 one connects to, and then requests information from. Gnus does not
12388 connect directly to any real servers, but does all transactions through
12389 one back end or other. But that's just putting one layer more between
12390 the actual media and Gnus, so we might just as well say that each
12391 back end represents a virtual server.
12393 For instance, the @code{nntp} back end may be used to connect to several
12394 different actual @acronym{NNTP} servers, or, perhaps, to many different ports
12395 on the same actual @acronym{NNTP} server. You tell Gnus which back end to
12396 use, and what parameters to set by specifying a @dfn{select method}.
12398 These select method specifications can sometimes become quite
12399 complicated---say, for instance, that you want to read from the
12400 @acronym{NNTP} server @samp{news.funet.fi} on port number 13, which
12401 hangs if queried for @acronym{NOV} headers and has a buggy select. Ahem.
12402 Anyway, if you had to specify that for each group that used this
12403 server, that would be too much work, so Gnus offers a way of naming
12404 select methods, which is what you do in the server buffer.
12406 To enter the server buffer, use the @kbd{^}
12407 (@code{gnus-group-enter-server-mode}) command in the group buffer.
12410 * Server Buffer Format:: You can customize the look of this buffer.
12411 * Server Commands:: Commands to manipulate servers.
12412 * Example Methods:: Examples server specifications.
12413 * Creating a Virtual Server:: An example session.
12414 * Server Variables:: Which variables to set.
12415 * Servers and Methods:: You can use server names as select methods.
12416 * Unavailable Servers:: Some servers you try to contact may be down.
12419 @vindex gnus-server-mode-hook
12420 @code{gnus-server-mode-hook} is run when creating the server buffer.
12423 @node Server Buffer Format
12424 @subsection Server Buffer Format
12425 @cindex server buffer format
12427 @vindex gnus-server-line-format
12428 You can change the look of the server buffer lines by changing the
12429 @code{gnus-server-line-format} variable. This is a @code{format}-like
12430 variable, with some simple extensions:
12435 How the news is fetched---the back end name.
12438 The name of this server.
12441 Where the news is to be fetched from---the address.
12444 The opened/closed/denied status of the server.
12447 Whether this server is agentized.
12450 @vindex gnus-server-mode-line-format
12451 The mode line can also be customized by using the
12452 @code{gnus-server-mode-line-format} variable (@pxref{Mode Line
12453 Formatting}). The following specs are understood:
12463 Also @pxref{Formatting Variables}.
12466 @node Server Commands
12467 @subsection Server Commands
12468 @cindex server commands
12474 @cindex keys, reserved for users (Server)
12475 The key @kbd{v} is reserved for users. You can bind it key to some
12476 function or better use it as a prefix key.
12480 @findex gnus-server-add-server
12481 Add a new server (@code{gnus-server-add-server}).
12485 @findex gnus-server-edit-server
12486 Edit a server (@code{gnus-server-edit-server}).
12489 @kindex SPACE (Server)
12490 @findex gnus-server-read-server
12491 Browse the current server (@code{gnus-server-read-server}).
12495 @findex gnus-server-exit
12496 Return to the group buffer (@code{gnus-server-exit}).
12500 @findex gnus-server-kill-server
12501 Kill the current server (@code{gnus-server-kill-server}).
12505 @findex gnus-server-yank-server
12506 Yank the previously killed server (@code{gnus-server-yank-server}).
12510 @findex gnus-server-copy-server
12511 Copy the current server (@code{gnus-server-copy-server}).
12515 @findex gnus-server-list-servers
12516 List all servers (@code{gnus-server-list-servers}).
12520 @findex gnus-server-scan-server
12521 Request that the server scan its sources for new articles
12522 (@code{gnus-server-scan-server}). This is mainly sensible with mail
12527 @findex gnus-server-regenerate-server
12528 Request that the server regenerate all its data structures
12529 (@code{gnus-server-regenerate-server}). This can be useful if you have
12530 a mail back end that has gotten out of sync.
12535 @node Example Methods
12536 @subsection Example Methods
12538 Most select methods are pretty simple and self-explanatory:
12541 (nntp "news.funet.fi")
12544 Reading directly from the spool is even simpler:
12550 As you can see, the first element in a select method is the name of the
12551 back end, and the second is the @dfn{address}, or @dfn{name}, if you
12554 After these two elements, there may be an arbitrary number of
12555 @code{(@var{variable} @var{form})} pairs.
12557 To go back to the first example---imagine that you want to read from
12558 port 15 on that machine. This is what the select method should
12562 (nntp "news.funet.fi" (nntp-port-number 15))
12565 You should read the documentation to each back end to find out what
12566 variables are relevant, but here's an @code{nnmh} example:
12568 @code{nnmh} is a mail back end that reads a spool-like structure. Say
12569 you have two structures that you wish to access: One is your private
12570 mail spool, and the other is a public one. Here's the possible spec for
12574 (nnmh "private" (nnmh-directory "~/private/mail/"))
12577 (This server is then called @samp{private}, but you may have guessed
12580 Here's the method for a public spool:
12584 (nnmh-directory "/usr/information/spool/")
12585 (nnmh-get-new-mail nil))
12591 If you are behind a firewall and only have access to the @acronym{NNTP}
12592 server from the firewall machine, you can instruct Gnus to @code{rlogin}
12593 on the firewall machine and telnet from there to the @acronym{NNTP} server.
12594 Doing this can be rather fiddly, but your virtual server definition
12595 should probably look something like this:
12599 (nntp-open-connection-function nntp-open-via-rlogin-and-telnet)
12600 (nntp-via-address "the.firewall.machine")
12601 (nntp-address "the.real.nntp.host")
12602 (nntp-end-of-line "\n"))
12605 If you want to use the wonderful @code{ssh} program to provide a
12606 compressed connection over the modem line, you could add the following
12607 configuration to the example above:
12610 (nntp-via-rlogin-command "ssh")
12613 See also @code{nntp-via-rlogin-command-switches}. Here's an example for
12614 an indirect connection:
12616 (setq gnus-select-method
12618 (nntp-address "news.server.example")
12619 (nntp-via-user-name "intermediate_user_name")
12620 (nntp-via-address "intermediate.host.example")
12621 (nntp-via-rlogin-command "ssh")
12622 (nntp-end-of-line "\n")
12623 (nntp-via-rlogin-command-switches ("-C" "-t" "-e" "none"))
12624 (nntp-open-connection-function nntp-open-via-rlogin-and-telnet)))
12627 If you're behind a firewall, but have direct access to the outside world
12628 through a wrapper command like "runsocks", you could open a socksified
12629 telnet connection to the news server as follows:
12633 (nntp-pre-command "runsocks")
12634 (nntp-open-connection-function nntp-open-via-telnet)
12635 (nntp-address "the.news.server")
12636 (nntp-end-of-line "\n"))
12639 This means that you have to have set up @code{ssh-agent} correctly to
12640 provide automatic authorization, of course. And to get a compressed
12641 connection, you have to have the @samp{Compression} option in the
12642 @code{ssh} @file{config} file.
12645 @node Creating a Virtual Server
12646 @subsection Creating a Virtual Server
12648 If you're saving lots of articles in the cache by using persistent
12649 articles, you may want to create a virtual server to read the cache.
12651 First you need to add a new server. The @kbd{a} command does that. It
12652 would probably be best to use @code{nnml} to read the cache. You
12653 could also use @code{nnspool} or @code{nnmh}, though.
12655 Type @kbd{a nnml RET cache RET}.
12657 You should now have a brand new @code{nnml} virtual server called
12658 @samp{cache}. You now need to edit it to have the right definitions.
12659 Type @kbd{e} to edit the server. You'll be entered into a buffer that
12660 will contain the following:
12670 (nnml-directory "~/News/cache/")
12671 (nnml-active-file "~/News/cache/active"))
12674 Type @kbd{C-c C-c} to return to the server buffer. If you now press
12675 @kbd{RET} over this virtual server, you should be entered into a browse
12676 buffer, and you should be able to enter any of the groups displayed.
12679 @node Server Variables
12680 @subsection Server Variables
12681 @cindex server variables
12682 @cindex server parameters
12684 One sticky point when defining variables (both on back ends and in Emacs
12685 in general) is that some variables are typically initialized from other
12686 variables when the definition of the variables is being loaded. If you
12687 change the ``base'' variable after the variables have been loaded, you
12688 won't change the ``derived'' variables.
12690 This typically affects directory and file variables. For instance,
12691 @code{nnml-directory} is @file{~/Mail/} by default, and all @code{nnml}
12692 directory variables are initialized from that variable, so
12693 @code{nnml-active-file} will be @file{~/Mail/active}. If you define a
12694 new virtual @code{nnml} server, it will @emph{not} suffice to set just
12695 @code{nnml-directory}---you have to explicitly set all the file
12696 variables to be what you want them to be. For a complete list of
12697 variables for each back end, see each back end's section later in this
12698 manual, but here's an example @code{nnml} definition:
12702 (nnml-directory "~/my-mail/")
12703 (nnml-active-file "~/my-mail/active")
12704 (nnml-newsgroups-file "~/my-mail/newsgroups"))
12707 Server variables are often called @dfn{server parameters}.
12709 @node Servers and Methods
12710 @subsection Servers and Methods
12712 Wherever you would normally use a select method
12713 (e.g. @code{gnus-secondary-select-method}, in the group select method,
12714 when browsing a foreign server) you can use a virtual server name
12715 instead. This could potentially save lots of typing. And it's nice all
12719 @node Unavailable Servers
12720 @subsection Unavailable Servers
12722 If a server seems to be unreachable, Gnus will mark that server as
12723 @code{denied}. That means that any subsequent attempt to make contact
12724 with that server will just be ignored. ``It can't be opened,'' Gnus
12725 will tell you, without making the least effort to see whether that is
12726 actually the case or not.
12728 That might seem quite naughty, but it does make sense most of the time.
12729 Let's say you have 10 groups subscribed to on server
12730 @samp{nephelococcygia.com}. This server is located somewhere quite far
12731 away from you and the machine is quite slow, so it takes 1 minute just
12732 to find out that it refuses connection to you today. If Gnus were to
12733 attempt to do that 10 times, you'd be quite annoyed, so Gnus won't
12734 attempt to do that. Once it has gotten a single ``connection refused'',
12735 it will regard that server as ``down''.
12737 So, what happens if the machine was only feeling unwell temporarily?
12738 How do you test to see whether the machine has come up again?
12740 You jump to the server buffer (@pxref{Server Buffer}) and poke it
12741 with the following commands:
12747 @findex gnus-server-open-server
12748 Try to establish connection to the server on the current line
12749 (@code{gnus-server-open-server}).
12753 @findex gnus-server-close-server
12754 Close the connection (if any) to the server
12755 (@code{gnus-server-close-server}).
12759 @findex gnus-server-deny-server
12760 Mark the current server as unreachable
12761 (@code{gnus-server-deny-server}).
12764 @kindex M-o (Server)
12765 @findex gnus-server-open-all-servers
12766 Open the connections to all servers in the buffer
12767 (@code{gnus-server-open-all-servers}).
12770 @kindex M-c (Server)
12771 @findex gnus-server-close-all-servers
12772 Close the connections to all servers in the buffer
12773 (@code{gnus-server-close-all-servers}).
12777 @findex gnus-server-remove-denials
12778 Remove all marks to whether Gnus was denied connection from any servers
12779 (@code{gnus-server-remove-denials}).
12783 @findex gnus-server-offline-server
12784 Set server status to offline (@code{gnus-server-offline-server}).
12790 @section Getting News
12791 @cindex reading news
12792 @cindex news back ends
12794 A newsreader is normally used for reading news. Gnus currently provides
12795 only two methods of getting news---it can read from an @acronym{NNTP} server,
12796 or it can read from a local spool.
12799 * NNTP:: Reading news from an @acronym{NNTP} server.
12800 * News Spool:: Reading news from the local spool.
12808 Subscribing to a foreign group from an @acronym{NNTP} server is rather easy.
12809 You just specify @code{nntp} as method and the address of the @acronym{NNTP}
12810 server as the, uhm, address.
12812 If the @acronym{NNTP} server is located at a non-standard port, setting the
12813 third element of the select method to this port number should allow you
12814 to connect to the right port. You'll have to edit the group info for
12815 that (@pxref{Foreign Groups}).
12817 The name of the foreign group can be the same as a native group. In
12818 fact, you can subscribe to the same group from as many different servers
12819 you feel like. There will be no name collisions.
12821 The following variables can be used to create a virtual @code{nntp}
12826 @item nntp-server-opened-hook
12827 @vindex nntp-server-opened-hook
12828 @cindex @sc{mode reader}
12830 @cindex authentification
12831 @cindex nntp authentification
12832 @findex nntp-send-authinfo
12833 @findex nntp-send-mode-reader
12834 is run after a connection has been made. It can be used to send
12835 commands to the @acronym{NNTP} server after it has been contacted. By
12836 default it sends the command @code{MODE READER} to the server with the
12837 @code{nntp-send-mode-reader} function. This function should always be
12838 present in this hook.
12840 @item nntp-authinfo-function
12841 @vindex nntp-authinfo-function
12842 @findex nntp-send-authinfo
12843 @vindex nntp-authinfo-file
12844 This function will be used to send @samp{AUTHINFO} to the @acronym{NNTP}
12845 server. The default function is @code{nntp-send-authinfo}, which looks
12846 through your @file{~/.authinfo} (or whatever you've set the
12847 @code{nntp-authinfo-file} variable to) for applicable entries. If none
12848 are found, it will prompt you for a login name and a password. The
12849 format of the @file{~/.authinfo} file is (almost) the same as the
12850 @code{ftp} @file{~/.netrc} file, which is defined in the @code{ftp}
12851 manual page, but here are the salient facts:
12855 The file contains one or more line, each of which define one server.
12858 Each line may contain an arbitrary number of token/value pairs.
12860 The valid tokens include @samp{machine}, @samp{login}, @samp{password},
12861 @samp{default}. In addition Gnus introduces two new tokens, not present
12862 in the original @file{.netrc}/@code{ftp} syntax, namely @samp{port} and
12863 @samp{force}. (This is the only way the @file{.authinfo} file format
12864 deviates from the @file{.netrc} file format.) @samp{port} is used to
12865 indicate what port on the server the credentials apply to and
12866 @samp{force} is explained below.
12870 Here's an example file:
12873 machine news.uio.no login larsi password geheimnis
12874 machine nntp.ifi.uio.no login larsi force yes
12877 The token/value pairs may appear in any order; @samp{machine} doesn't
12878 have to be first, for instance.
12880 In this example, both login name and password have been supplied for the
12881 former server, while the latter has only the login name listed, and the
12882 user will be prompted for the password. The latter also has the
12883 @samp{force} tag, which means that the authinfo will be sent to the
12884 @var{nntp} server upon connection; the default (i.e., when there is not
12885 @samp{force} tag) is to not send authinfo to the @var{nntp} server
12886 until the @var{nntp} server asks for it.
12888 You can also add @samp{default} lines that will apply to all servers
12889 that don't have matching @samp{machine} lines.
12895 This will force sending @samp{AUTHINFO} commands to all servers not
12896 previously mentioned.
12898 Remember to not leave the @file{~/.authinfo} file world-readable.
12900 @item nntp-server-action-alist
12901 @vindex nntp-server-action-alist
12902 This is a list of regexps to match on server types and actions to be
12903 taken when matches are made. For instance, if you want Gnus to beep
12904 every time you connect to innd, you could say something like:
12907 (setq nntp-server-action-alist
12908 '(("innd" (ding))))
12911 You probably don't want to do that, though.
12913 The default value is
12916 '(("nntpd 1\\.5\\.11t"
12917 (remove-hook 'nntp-server-opened-hook
12918 'nntp-send-mode-reader)))
12921 This ensures that Gnus doesn't send the @code{MODE READER} command to
12922 nntpd 1.5.11t, since that command chokes that server, I've been told.
12924 @item nntp-maximum-request
12925 @vindex nntp-maximum-request
12926 If the @acronym{NNTP} server doesn't support @acronym{NOV} headers, this back end
12927 will collect headers by sending a series of @code{head} commands. To
12928 speed things up, the back end sends lots of these commands without
12929 waiting for reply, and then reads all the replies. This is controlled
12930 by the @code{nntp-maximum-request} variable, and is 400 by default. If
12931 your network is buggy, you should set this to 1.
12933 @item nntp-connection-timeout
12934 @vindex nntp-connection-timeout
12935 If you have lots of foreign @code{nntp} groups that you connect to
12936 regularly, you're sure to have problems with @acronym{NNTP} servers not
12937 responding properly, or being too loaded to reply within reasonable
12938 time. This is can lead to awkward problems, which can be helped
12939 somewhat by setting @code{nntp-connection-timeout}. This is an integer
12940 that says how many seconds the @code{nntp} back end should wait for a
12941 connection before giving up. If it is @code{nil}, which is the default,
12942 no timeouts are done.
12944 @item nntp-nov-is-evil
12945 @vindex nntp-nov-is-evil
12946 If the @acronym{NNTP} server does not support @acronym{NOV}, you could set this
12947 variable to @code{t}, but @code{nntp} usually checks automatically whether @acronym{NOV}
12950 @item nntp-xover-commands
12951 @vindex nntp-xover-commands
12952 @cindex @acronym{NOV}
12954 List of strings used as commands to fetch @acronym{NOV} lines from a
12955 server. The default value of this variable is @code{("XOVER"
12959 @vindex nntp-nov-gap
12960 @code{nntp} normally sends just one big request for @acronym{NOV} lines to
12961 the server. The server responds with one huge list of lines. However,
12962 if you have read articles 2-5000 in the group, and only want to read
12963 article 1 and 5001, that means that @code{nntp} will fetch 4999 @acronym{NOV}
12964 lines that you will not need. This variable says how
12965 big a gap between two consecutive articles is allowed to be before the
12966 @code{XOVER} request is split into several request. Note that if your
12967 network is fast, setting this variable to a really small number means
12968 that fetching will probably be slower. If this variable is @code{nil},
12969 @code{nntp} will never split requests. The default is 5.
12971 @item nntp-prepare-server-hook
12972 @vindex nntp-prepare-server-hook
12973 A hook run before attempting to connect to an @acronym{NNTP} server.
12975 @item nntp-record-commands
12976 @vindex nntp-record-commands
12977 If non-@code{nil}, @code{nntp} will log all commands it sends to the
12978 @acronym{NNTP} server (along with a timestamp) in the @samp{*nntp-log*}
12979 buffer. This is useful if you are debugging a Gnus/@acronym{NNTP} connection
12980 that doesn't seem to work.
12982 @item nntp-open-connection-function
12983 @vindex nntp-open-connection-function
12984 It is possible to customize how the connection to the nntp server will
12985 be opened. If you specify an @code{nntp-open-connection-function}
12986 parameter, Gnus will use that function to establish the connection.
12987 Seven pre-made functions are supplied. These functions can be grouped
12988 in two categories: direct connection functions (four pre-made), and
12989 indirect ones (three pre-made).
12991 @item nntp-prepare-post-hook
12992 @vindex nntp-prepare-post-hook
12993 A hook run just before posting an article. If there is no
12994 @code{Message-ID} header in the article and the news server provides the
12995 recommended ID, it will be added to the article before running this
12996 hook. It is useful to make @code{Cancel-Lock} headers even if you
12997 inhibit Gnus to add a @code{Message-ID} header, you could say:
13000 (add-hook 'nntp-prepare-post-hook 'canlock-insert-header)
13003 Note that not all servers support the recommended ID. This works for
13004 INN versions 2.3.0 and later, for instance.
13009 * Direct Functions:: Connecting directly to the server.
13010 * Indirect Functions:: Connecting indirectly to the server.
13011 * Common Variables:: Understood by several connection functions.
13012 * NNTP marks:: Storing marks for @acronym{NNTP} servers.
13016 @node Direct Functions
13017 @subsubsection Direct Functions
13018 @cindex direct connection functions
13020 These functions are called direct because they open a direct connection
13021 between your machine and the @acronym{NNTP} server. The behavior of these
13022 functions is also affected by commonly understood variables
13023 (@pxref{Common Variables}).
13026 @findex nntp-open-network-stream
13027 @item nntp-open-network-stream
13028 This is the default, and simply connects to some port or other on the
13031 @findex nntp-open-tls-stream
13032 @item nntp-open-tls-stream
13033 Opens a connection to a server over a @dfn{secure} channel. To use
13034 this you must have @uref{http://www.gnu.org/software/gnutls/, GNUTLS}
13035 installed. You then define a server as follows:
13038 ;; @r{"nntps" is port 563 and is predefined in our @file{/etc/services}}
13039 ;; @r{however, @samp{gnutls-cli -p} doesn't like named ports.}
13041 (nntp "snews.bar.com"
13042 (nntp-open-connection-function nntp-open-tls-stream)
13043 (nntp-port-number )
13044 (nntp-address "snews.bar.com"))
13047 @findex nntp-open-ssl-stream
13048 @item nntp-open-ssl-stream
13049 Opens a connection to a server over a @dfn{secure} channel. To use
13050 this you must have @uref{http://www.openssl.org, OpenSSL} or
13051 @uref{ftp://ftp.psy.uq.oz.au/pub/Crypto/SSL, SSLeay} installed. You
13052 then define a server as follows:
13055 ;; @r{"snews" is port 563 and is predefined in our @file{/etc/services}}
13056 ;; @r{however, @samp{openssl s_client -port} doesn't like named ports.}
13058 (nntp "snews.bar.com"
13059 (nntp-open-connection-function nntp-open-ssl-stream)
13060 (nntp-port-number 563)
13061 (nntp-address "snews.bar.com"))
13064 @findex nntp-open-telnet-stream
13065 @item nntp-open-telnet-stream
13066 Opens a connection to an @acronym{NNTP} server by simply @samp{telnet}'ing
13067 it. You might wonder why this function exists, since we have the
13068 default @code{nntp-open-network-stream} which would do the job. (One
13069 of) the reason(s) is that if you are behind a firewall but have direct
13070 connections to the outside world thanks to a command wrapper like
13071 @code{runsocks}, you can use it like this:
13075 (nntp-pre-command "runsocks")
13076 (nntp-open-connection-function nntp-open-telnet-stream)
13077 (nntp-address "the.news.server"))
13080 With the default method, you would need to wrap your whole Emacs
13081 session, which is not a good idea.
13085 @node Indirect Functions
13086 @subsubsection Indirect Functions
13087 @cindex indirect connection functions
13089 These functions are called indirect because they connect to an
13090 intermediate host before actually connecting to the @acronym{NNTP} server.
13091 All of these functions and related variables are also said to belong to
13092 the ``via'' family of connection: they're all prefixed with ``via'' to make
13093 things cleaner. The behavior of these functions is also affected by
13094 commonly understood variables (@pxref{Common Variables}).
13097 @item nntp-open-via-rlogin-and-telnet
13098 @findex nntp-open-via-rlogin-and-telnet
13099 Does an @samp{rlogin} on a remote system, and then does a @samp{telnet}
13100 to the real @acronym{NNTP} server from there. This is useful for instance if
13101 you need to connect to a firewall machine first.
13103 @code{nntp-open-via-rlogin-and-telnet}-specific variables:
13106 @item nntp-via-rlogin-command
13107 @vindex nntp-via-rlogin-command
13108 Command used to log in on the intermediate host. The default is
13109 @samp{rsh}, but @samp{ssh} is a popular alternative.
13111 @item nntp-via-rlogin-command-switches
13112 @vindex nntp-via-rlogin-command-switches
13113 List of strings to be used as the switches to
13114 @code{nntp-via-rlogin-command}. The default is @code{nil}. If you use
13115 @samp{ssh} for @code{nntp-via-rlogin-command}, you may set this to
13116 @samp{("-C")} in order to compress all data connections, otherwise set
13117 this to @samp{("-t" "-e" "none")} or @samp{("-C" "-t" "-e" "none")} if
13118 the telnet command requires a pseudo-tty allocation on an intermediate
13122 Note that you may want to change the value for @code{nntp-end-of-line}
13123 to @samp{\n} (@pxref{Common Variables}).
13125 @item nntp-open-via-rlogin-and-netcat
13126 @findex nntp-open-via-rlogin-and-netcat
13127 Does essentially the same, but uses
13128 @uref{http://netcat.sourceforge.net/, netcat} instead of @samp{telnet}
13129 to connect to the real @acronym{NNTP} server from the intermediate host.
13131 @code{nntp-open-via-rlogin-and-netcat}-specific variables:
13134 @item nntp-via-netcat-command
13135 @vindex nntp-via-netcat-command
13136 Command used to connect to the real @acronym{NNTP} server from the
13137 intermediate host. The default is @samp{nc}. You can also use other
13138 programs like @uref{http://www.imasy.or.jp/~gotoh/ssh/connect.html,
13141 @item nntp-via-netcat-switches
13142 @vindex nntp-via-netcat-switches
13143 List of strings to be used as the switches to the
13144 @code{nntp-via-telnet-command} command. The default is @code{nil}.
13146 @item nntp-via-rlogin-command
13147 @vindex nntp-via-rlogin-command
13148 Command used to log in on the intermediate host. The default is
13149 @samp{rsh}, but @samp{ssh} is a popular alternative.
13151 @item nntp-via-rlogin-command-switches
13152 @vindex nntp-via-rlogin-command-switches
13153 List of strings to be used as the switches to
13154 @code{nntp-via-rlogin-command}. The default is @code{nil}.
13157 @item nntp-open-via-telnet-and-telnet
13158 @findex nntp-open-via-telnet-and-telnet
13159 Does essentially the same, but uses @samp{telnet} instead of
13160 @samp{rlogin} to connect to the intermediate host.
13162 @code{nntp-open-via-telnet-and-telnet}-specific variables:
13165 @item nntp-via-telnet-command
13166 @vindex nntp-via-telnet-command
13167 Command used to @code{telnet} the intermediate host. The default is
13170 @item nntp-via-telnet-switches
13171 @vindex nntp-via-telnet-switches
13172 List of strings to be used as the switches to the
13173 @code{nntp-via-telnet-command} command. The default is @samp{("-8")}.
13175 @item nntp-via-user-password
13176 @vindex nntp-via-user-password
13177 Password to use when logging in on the intermediate host.
13179 @item nntp-via-envuser
13180 @vindex nntp-via-envuser
13181 If non-@code{nil}, the intermediate @code{telnet} session (client and
13182 server both) will support the @code{ENVIRON} option and not prompt for
13183 login name. This works for Solaris @code{telnet}, for instance.
13185 @item nntp-via-shell-prompt
13186 @vindex nntp-via-shell-prompt
13187 Regexp matching the shell prompt on the intermediate host. The default
13188 is @samp{bash\\|\$ *\r?$\\|> *\r?}.
13192 Note that you may want to change the value for @code{nntp-end-of-line}
13193 to @samp{\n} (@pxref{Common Variables}).
13197 Here are some additional variables that are understood by all the above
13202 @item nntp-via-user-name
13203 @vindex nntp-via-user-name
13204 User name to use when connecting to the intermediate host.
13206 @item nntp-via-address
13207 @vindex nntp-via-address
13208 Address of the intermediate host to connect to.
13213 @node Common Variables
13214 @subsubsection Common Variables
13216 The following variables affect the behavior of all, or several of the
13217 pre-made connection functions. When not specified, all functions are
13218 affected (the values of the following variables will be used as the
13219 default if each virtual @code{nntp} server doesn't specify those server
13220 variables individually).
13224 @item nntp-pre-command
13225 @vindex nntp-pre-command
13226 A command wrapper to use when connecting through a non native
13227 connection function (all except @code{nntp-open-network-stream},
13228 @code{nntp-open-tls-stream}, and @code{nntp-open-ssl-stream}). This is
13229 where you would put a @samp{SOCKS} wrapper for instance.
13232 @vindex nntp-address
13233 The address of the @acronym{NNTP} server.
13235 @item nntp-port-number
13236 @vindex nntp-port-number
13237 Port number to connect to the @acronym{NNTP} server. The default is
13238 @samp{nntp}. If you use @acronym{NNTP} over
13239 @acronym{TLS}/@acronym{SSL}, you may want to use integer ports rather
13240 than named ports (i.e, use @samp{563} instead of @samp{snews} or
13241 @samp{nntps}), because external @acronym{TLS}/@acronym{SSL} tools may
13242 not work with named ports.
13244 @item nntp-end-of-line
13245 @vindex nntp-end-of-line
13246 String to use as end-of-line marker when talking to the @acronym{NNTP}
13247 server. This is @samp{\r\n} by default, but should be @samp{\n} when
13248 using a non native telnet connection function.
13250 @item nntp-telnet-command
13251 @vindex nntp-telnet-command
13252 Command to use when connecting to the @acronym{NNTP} server through
13253 @samp{telnet}. This is @emph{not} for an intermediate host. This is
13254 just for the real @acronym{NNTP} server. The default is
13257 @item nntp-telnet-switches
13258 @vindex nntp-telnet-switches
13259 A list of switches to pass to @code{nntp-telnet-command}. The default
13265 @subsubsection NNTP marks
13266 @cindex storing NNTP marks
13268 Gnus stores marks (@pxref{Marking Articles}) for @acronym{NNTP}
13269 servers in marks files. A marks file records what marks you have set
13270 in a group and each file is specific to the corresponding server.
13271 Marks files are stored in @file{~/News/marks}
13272 (@code{nntp-marks-directory}) under a classic hierarchy resembling
13273 that of a news server, for example marks for the group
13274 @samp{gmane.discuss} on the news.gmane.org server will be stored in
13275 the file @file{~/News/marks/news.gmane.org/gmane/discuss/.marks}.
13277 Marks files are useful because you can copy the @file{~/News/marks}
13278 directory (using rsync, scp or whatever) to another Gnus installation,
13279 and it will realize what articles you have read and marked. The data
13280 in @file{~/News/marks} has priority over the same data in
13281 @file{~/.newsrc.eld}.
13283 Note that marks files are very much server-specific: Gnus remembers
13284 the article numbers so if you don't use the same servers on both
13285 installations things are most likely to break (most @acronym{NNTP}
13286 servers do not use the same article numbers as any other server).
13287 However, if you use servers A, B, C on one installation and servers A,
13288 D, E on the other, you can sync the marks files for A and then you'll
13289 get synchronization for that server between the two installations.
13291 Using @acronym{NNTP} marks can possibly incur a performance penalty so
13292 if Gnus feels sluggish, try setting the @code{nntp-marks-is-evil}
13293 variable to @code{t}. Marks will then be stored in @file{~/.newsrc.eld}.
13299 @item nntp-marks-is-evil
13300 @vindex nntp-marks-is-evil
13301 If non-@code{nil}, this back end will ignore any marks files. The
13302 default is @code{nil}.
13304 @item nntp-marks-directory
13305 @vindex nntp-marks-directory
13306 The directory where marks for nntp groups will be stored.
13312 @subsection News Spool
13316 Subscribing to a foreign group from the local spool is extremely easy,
13317 and might be useful, for instance, to speed up reading groups that
13318 contain very big articles---@samp{alt.binaries.pictures.furniture}, for
13321 Anyway, you just specify @code{nnspool} as the method and @code{""} (or
13322 anything else) as the address.
13324 If you have access to a local spool, you should probably use that as the
13325 native select method (@pxref{Finding the News}). It is normally faster
13326 than using an @code{nntp} select method, but might not be. It depends.
13327 You just have to try to find out what's best at your site.
13331 @item nnspool-inews-program
13332 @vindex nnspool-inews-program
13333 Program used to post an article.
13335 @item nnspool-inews-switches
13336 @vindex nnspool-inews-switches
13337 Parameters given to the inews program when posting an article.
13339 @item nnspool-spool-directory
13340 @vindex nnspool-spool-directory
13341 Where @code{nnspool} looks for the articles. This is normally
13342 @file{/usr/spool/news/}.
13344 @item nnspool-nov-directory
13345 @vindex nnspool-nov-directory
13346 Where @code{nnspool} will look for @acronym{NOV} files. This is normally@*
13347 @file{/usr/spool/news/over.view/}.
13349 @item nnspool-lib-dir
13350 @vindex nnspool-lib-dir
13351 Where the news lib dir is (@file{/usr/lib/news/} by default).
13353 @item nnspool-active-file
13354 @vindex nnspool-active-file
13355 The name of the active file.
13357 @item nnspool-newsgroups-file
13358 @vindex nnspool-newsgroups-file
13359 The name of the group descriptions file.
13361 @item nnspool-history-file
13362 @vindex nnspool-history-file
13363 The name of the news history file.
13365 @item nnspool-active-times-file
13366 @vindex nnspool-active-times-file
13367 The name of the active date file.
13369 @item nnspool-nov-is-evil
13370 @vindex nnspool-nov-is-evil
13371 If non-@code{nil}, @code{nnspool} won't try to use any @acronym{NOV} files
13374 @item nnspool-sift-nov-with-sed
13375 @vindex nnspool-sift-nov-with-sed
13377 If non-@code{nil}, which is the default, use @code{sed} to get the
13378 relevant portion from the overview file. If @code{nil},
13379 @code{nnspool} will load the entire file into a buffer and process it
13386 @section Getting Mail
13387 @cindex reading mail
13390 Reading mail with a newsreader---isn't that just plain WeIrD? But of
13394 * Mail in a Newsreader:: Important introductory notes.
13395 * Getting Started Reading Mail:: A simple cookbook example.
13396 * Splitting Mail:: How to create mail groups.
13397 * Mail Sources:: How to tell Gnus where to get mail from.
13398 * Mail Back End Variables:: Variables for customizing mail handling.
13399 * Fancy Mail Splitting:: Gnus can do hairy splitting of incoming mail.
13400 * Group Mail Splitting:: Use group customize to drive mail splitting.
13401 * Incorporating Old Mail:: What about the old mail you have?
13402 * Expiring Mail:: Getting rid of unwanted mail.
13403 * Washing Mail:: Removing cruft from the mail you get.
13404 * Duplicates:: Dealing with duplicated mail.
13405 * Not Reading Mail:: Using mail back ends for reading other files.
13406 * Choosing a Mail Back End:: Gnus can read a variety of mail formats.
13410 @node Mail in a Newsreader
13411 @subsection Mail in a Newsreader
13413 If you are used to traditional mail readers, but have decided to switch
13414 to reading mail with Gnus, you may find yourself experiencing something
13415 of a culture shock.
13417 Gnus does not behave like traditional mail readers. If you want to make
13418 it behave that way, you can, but it's an uphill battle.
13420 Gnus, by default, handles all its groups using the same approach. This
13421 approach is very newsreaderly---you enter a group, see the new/unread
13422 messages, and when you read the messages, they get marked as read, and
13423 you don't see them any more. (Unless you explicitly ask for them.)
13425 In particular, you do not do anything explicitly to delete messages.
13427 Does this mean that all the messages that have been marked as read are
13428 deleted? How awful!
13430 But, no, it means that old messages are @dfn{expired} according to some
13431 scheme or other. For news messages, the expire process is controlled by
13432 the news administrator; for mail, the expire process is controlled by
13433 you. The expire process for mail is covered in depth in @ref{Expiring
13436 What many Gnus users find, after using it a while for both news and
13437 mail, is that the transport mechanism has very little to do with how
13438 they want to treat a message.
13440 Many people subscribe to several mailing lists. These are transported
13441 via @acronym{SMTP}, and are therefore mail. But we might go for weeks without
13442 answering, or even reading these messages very carefully. We may not
13443 need to save them because if we should need to read one again, they are
13444 archived somewhere else.
13446 Some people have local news groups which have only a handful of readers.
13447 These are transported via @acronym{NNTP}, and are therefore news. But we may need
13448 to read and answer a large fraction of the messages very carefully in
13449 order to do our work. And there may not be an archive, so we may need
13450 to save the interesting messages the same way we would personal mail.
13452 The important distinction turns out to be not the transport mechanism,
13453 but other factors such as how interested we are in the subject matter,
13454 or how easy it is to retrieve the message if we need to read it again.
13456 Gnus provides many options for sorting mail into ``groups'' which behave
13457 like newsgroups, and for treating each group (whether mail or news)
13460 Some users never get comfortable using the Gnus (ahem) paradigm and wish
13461 that Gnus should grow up and be a male, er, mail reader. It is possible
13462 to whip Gnus into a more mailreaderly being, but, as said before, it's
13463 not easy. People who prefer proper mail readers should try @sc{vm}
13464 instead, which is an excellent, and proper, mail reader.
13466 I don't mean to scare anybody off, but I want to make it clear that you
13467 may be required to learn a new way of thinking about messages. After
13468 you've been subjected to The Gnus Way, you will come to love it. I can
13469 guarantee it. (At least the guy who sold me the Emacs Subliminal
13470 Brain-Washing Functions that I've put into Gnus did guarantee it. You
13471 Will Be Assimilated. You Love Gnus. You Love The Gnus Mail Way.
13475 @node Getting Started Reading Mail
13476 @subsection Getting Started Reading Mail
13478 It's quite easy to use Gnus to read your new mail. You just plonk the
13479 mail back end of your choice into @code{gnus-secondary-select-methods},
13480 and things will happen automatically.
13482 For instance, if you want to use @code{nnml} (which is a ``one file per
13483 mail'' back end), you could put the following in your @file{~/.gnus.el} file:
13486 (setq gnus-secondary-select-methods '((nnml "")))
13489 Now, the next time you start Gnus, this back end will be queried for new
13490 articles, and it will move all the messages in your spool file to its
13491 directory, which is @file{~/Mail/} by default. The new group that will
13492 be created (@samp{mail.misc}) will be subscribed, and you can read it
13493 like any other group.
13495 You will probably want to split the mail into several groups, though:
13498 (setq nnmail-split-methods
13499 '(("junk" "^From:.*Lars Ingebrigtsen")
13500 ("crazy" "^Subject:.*die\\|^Organization:.*flabby")
13504 This will result in three new @code{nnml} mail groups being created:
13505 @samp{nnml:junk}, @samp{nnml:crazy}, and @samp{nnml:other}. All the
13506 mail that doesn't fit into the first two groups will be placed in the
13509 This should be sufficient for reading mail with Gnus. You might want to
13510 give the other sections in this part of the manual a perusal, though.
13511 Especially @pxref{Choosing a Mail Back End} and @pxref{Expiring Mail}.
13514 @node Splitting Mail
13515 @subsection Splitting Mail
13516 @cindex splitting mail
13517 @cindex mail splitting
13518 @cindex mail filtering (splitting)
13520 @vindex nnmail-split-methods
13521 The @code{nnmail-split-methods} variable says how the incoming mail is
13522 to be split into groups.
13525 (setq nnmail-split-methods
13526 '(("mail.junk" "^From:.*Lars Ingebrigtsen")
13527 ("mail.crazy" "^Subject:.*die\\|^Organization:.*flabby")
13528 ("mail.other" "")))
13531 This variable is a list of lists, where the first element of each of
13532 these lists is the name of the mail group (they do not have to be called
13533 something beginning with @samp{mail}, by the way), and the second
13534 element is a regular expression used on the header of each mail to
13535 determine if it belongs in this mail group. The first string may
13536 contain @samp{\\1} forms, like the ones used by @code{replace-match} to
13537 insert sub-expressions from the matched text. For instance:
13540 ("list.\\1" "From:.* \\(.*\\)-list@@majordomo.com")
13544 In that case, @code{nnmail-split-lowercase-expanded} controls whether
13545 the inserted text should be made lowercase. @xref{Fancy Mail Splitting}.
13547 The second element can also be a function. In that case, it will be
13548 called narrowed to the headers with the first element of the rule as the
13549 argument. It should return a non-@code{nil} value if it thinks that the
13550 mail belongs in that group.
13552 @cindex @samp{bogus} group
13553 The last of these groups should always be a general one, and the regular
13554 expression should @emph{always} be @samp{""} so that it matches any mails
13555 that haven't been matched by any of the other regexps. (These rules are
13556 processed from the beginning of the alist toward the end. The first rule
13557 to make a match will ``win'', unless you have crossposting enabled. In
13558 that case, all matching rules will ``win''.) If no rule matched, the mail
13559 will end up in the @samp{bogus} group. When new groups are created by
13560 splitting mail, you may want to run @code{gnus-group-find-new-groups} to
13561 see the new groups. This also applies to the @samp{bogus} group.
13563 If you like to tinker with this yourself, you can set this variable to a
13564 function of your choice. This function will be called without any
13565 arguments in a buffer narrowed to the headers of an incoming mail
13566 message. The function should return a list of group names that it
13567 thinks should carry this mail message.
13569 Note that the mail back ends are free to maul the poor, innocent,
13570 incoming headers all they want to. They all add @code{Lines} headers;
13571 some add @code{X-Gnus-Group} headers; most rename the Unix mbox
13572 @code{From<SPACE>} line to something else.
13574 @vindex nnmail-crosspost
13575 The mail back ends all support cross-posting. If several regexps match,
13576 the mail will be ``cross-posted'' to all those groups.
13577 @code{nnmail-crosspost} says whether to use this mechanism or not. Note
13578 that no articles are crossposted to the general (@samp{""}) group.
13580 @vindex nnmail-crosspost-link-function
13583 @code{nnmh} and @code{nnml} makes crossposts by creating hard links to
13584 the crossposted articles. However, not all file systems support hard
13585 links. If that's the case for you, set
13586 @code{nnmail-crosspost-link-function} to @code{copy-file}. (This
13587 variable is @code{add-name-to-file} by default.)
13589 @kindex M-x nnmail-split-history
13590 @findex nnmail-split-history
13591 If you wish to see where the previous mail split put the messages, you
13592 can use the @kbd{M-x nnmail-split-history} command. If you wish to see
13593 where re-spooling messages would put the messages, you can use
13594 @code{gnus-summary-respool-trace} and related commands (@pxref{Mail
13597 @vindex nnmail-split-header-length-limit
13598 Header lines longer than the value of
13599 @code{nnmail-split-header-length-limit} are excluded from the split
13602 @vindex nnmail-mail-splitting-charset
13603 @vindex nnmail-mail-splitting-decodes
13604 By default the splitting codes @acronym{MIME} decodes headers so you
13605 can match on non-@acronym{ASCII} strings. The
13606 @code{nnmail-mail-splitting-charset} variable specifies the default
13607 charset for decoding. The behavior can be turned off completely by
13608 binding @code{nnmail-mail-splitting-decodes} to @code{nil}, which is
13609 useful if you want to match articles based on the raw header data.
13611 @vindex nnmail-resplit-incoming
13612 By default, splitting is performed on all incoming messages. If you
13613 specify a @code{directory} entry for the variable @code{mail-sources}
13614 (@pxref{Mail Source Specifiers}), however, then splitting does
13615 @emph{not} happen by default. You can set the variable
13616 @code{nnmail-resplit-incoming} to a non-@code{nil} value to make
13617 splitting happen even in this case. (This variable has no effect on
13618 other kinds of entries.)
13620 Gnus gives you all the opportunity you could possibly want for shooting
13621 yourself in the foot. Let's say you create a group that will contain
13622 all the mail you get from your boss. And then you accidentally
13623 unsubscribe from the group. Gnus will still put all the mail from your
13624 boss in the unsubscribed group, and so, when your boss mails you ``Have
13625 that report ready by Monday or you're fired!'', you'll never see it and,
13626 come Tuesday, you'll still believe that you're gainfully employed while
13627 you really should be out collecting empty bottles to save up for next
13628 month's rent money.
13632 @subsection Mail Sources
13634 Mail can be gotten from many different sources---the mail spool, from
13635 a @acronym{POP} mail server, from a procmail directory, or from a
13636 maildir, for instance.
13639 * Mail Source Specifiers:: How to specify what a mail source is.
13640 * Mail Source Customization:: Some variables that influence things.
13641 * Fetching Mail:: Using the mail source specifiers.
13645 @node Mail Source Specifiers
13646 @subsubsection Mail Source Specifiers
13648 @cindex mail server
13651 @cindex mail source
13653 You tell Gnus how to fetch mail by setting @code{mail-sources}
13654 (@pxref{Fetching Mail}) to a @dfn{mail source specifier}.
13659 (pop :server "pop3.mailserver.com" :user "myname")
13662 As can be observed, a mail source specifier is a list where the first
13663 element is a @dfn{mail source type}, followed by an arbitrary number of
13664 @dfn{keywords}. Keywords that are not explicitly specified are given
13667 The following mail source types are available:
13671 Get mail from a single file; typically from the mail spool.
13677 The file name. Defaults to the value of the @env{MAIL}
13678 environment variable or the value of @code{rmail-spool-directory}
13679 (usually something like @file{/usr/mail/spool/user-name}).
13683 Script run before/after fetching mail.
13686 An example file mail source:
13689 (file :path "/usr/spool/mail/user-name")
13692 Or using the default file name:
13698 If the mail spool file is not located on the local machine, it's best
13699 to use @acronym{POP} or @acronym{IMAP} or the like to fetch the mail.
13700 You can not use ange-ftp file names here---it has no way to lock the
13701 mail spool while moving the mail.
13703 If it's impossible to set up a proper server, you can use ssh instead.
13707 '((file :prescript "ssh host bin/getmail >%t")))
13710 The @samp{getmail} script would look something like the following:
13714 # getmail - move mail from spool to stdout
13717 MOVEMAIL=/usr/lib/emacs/20.3/i386-redhat-linux/movemail
13719 rm -f $TMP; $MOVEMAIL $MAIL $TMP >/dev/null && cat $TMP
13722 Alter this script to fit find the @samp{movemail} you want to use.
13726 @vindex nnmail-scan-directory-mail-source-once
13727 Get mail from several files in a directory. This is typically used
13728 when you have procmail split the incoming mail into several files.
13729 That is, there is a one-to-one correspondence between files in that
13730 directory and groups, so that mail from the file @file{foo.bar.spool}
13731 will be put in the group @code{foo.bar}. (You can change the suffix
13732 to be used instead of @code{.spool}.) Setting
13733 @code{nnmail-scan-directory-mail-source-once} to non-@code{nil} forces
13734 Gnus to scan the mail source only once. This is particularly useful
13735 if you want to scan mail groups at a specified level.
13737 @vindex nnmail-resplit-incoming
13738 There is also the variable @code{nnmail-resplit-incoming}, if you set
13739 that to a non-@code{nil} value, then the normal splitting process is
13740 applied to all the files from the directory, @ref{Splitting Mail}.
13746 The name of the directory where the files are. There is no default
13750 Only files ending with this suffix are used. The default is
13754 Only files that have this predicate return non-@code{nil} are returned.
13755 The default is @code{identity}. This is used as an additional
13756 filter---only files that have the right suffix @emph{and} satisfy this
13757 predicate are considered.
13761 Script run before/after fetching mail.
13765 An example directory mail source:
13768 (directory :path "/home/user-name/procmail-dir/"
13773 Get mail from a @acronym{POP} server.
13779 The name of the @acronym{POP} server. The default is taken from the
13780 @env{MAILHOST} environment variable.
13783 The port number of the @acronym{POP} server. This can be a number (eg,
13784 @samp{:port 1234}) or a string (eg, @samp{:port "pop3"}). If it is a
13785 string, it should be a service name as listed in @file{/etc/services} on
13786 Unix systems. The default is @samp{"pop3"}. On some systems you might
13787 need to specify it as @samp{"pop-3"} instead.
13790 The user name to give to the @acronym{POP} server. The default is the login
13794 The password to give to the @acronym{POP} server. If not specified,
13795 the user is prompted.
13798 The program to use to fetch mail from the @acronym{POP} server. This
13799 should be a @code{format}-like string. Here's an example:
13802 fetchmail %u@@%s -P %p %t
13805 The valid format specifier characters are:
13809 The name of the file the mail is to be moved to. This must always be
13810 included in this string.
13813 The name of the server.
13816 The port number of the server.
13819 The user name to use.
13822 The password to use.
13825 The values used for these specs are taken from the values you give the
13826 corresponding keywords.
13829 A script to be run before fetching the mail. The syntax is the same as
13830 the @code{:program} keyword. This can also be a function to be run.
13833 A script to be run after fetching the mail. The syntax is the same as
13834 the @code{:program} keyword. This can also be a function to be run.
13837 The function to use to fetch mail from the @acronym{POP} server. The
13838 function is called with one parameter---the name of the file where the
13839 mail should be moved to.
13841 @item :authentication
13842 This can be either the symbol @code{password} or the symbol @code{apop}
13843 and says what authentication scheme to use. The default is
13848 @vindex pop3-movemail
13849 @vindex pop3-leave-mail-on-server
13850 If the @code{:program} and @code{:function} keywords aren't specified,
13851 @code{pop3-movemail} will be used. If the
13852 @code{pop3-leave-mail-on-server} is non-@code{nil} the mail is to be
13853 left on the @acronym{POP} server after fetching when using
13854 @code{pop3-movemail}. Note that POP servers maintain no state
13855 information between sessions, so what the client believes is there and
13856 what is actually there may not match up. If they do not, then the whole
13857 thing can fall apart and leave you with a corrupt mailbox.
13859 Here are some examples. Fetch from the default @acronym{POP} server,
13860 using the default user name, and default fetcher:
13866 Fetch from a named server with a named user and password:
13869 (pop :server "my.pop.server"
13870 :user "user-name" :password "secret")
13873 Use @samp{movemail} to move the mail:
13876 (pop :program "movemail po:%u %t %p")
13880 Get mail from a maildir. This is a type of mailbox that is supported by
13881 at least qmail and postfix, where each file in a special directory
13882 contains exactly one mail.
13888 The name of the directory where the mails are stored. The default is
13889 taken from the @env{MAILDIR} environment variable or
13892 The subdirectories of the Maildir. The default is
13893 @samp{("new" "cur")}.
13895 @c If you sometimes look at your mail through a pop3 daemon before fetching
13896 @c them with Gnus, you may also have to fetch your mails from the
13897 @c @code{cur} directory inside the maildir, like in the first example
13900 You can also get mails from remote hosts (because maildirs don't suffer
13901 from locking problems).
13905 Two example maildir mail sources:
13908 (maildir :path "/home/user-name/Maildir/"
13909 :subdirs ("cur" "new"))
13913 (maildir :path "/user@@remotehost.org:~/Maildir/"
13918 Get mail from a @acronym{IMAP} server. If you don't want to use
13919 @acronym{IMAP} as intended, as a network mail reading protocol (ie
13920 with nnimap), for some reason or other, Gnus let you treat it similar
13921 to a @acronym{POP} server and fetches articles from a given
13922 @acronym{IMAP} mailbox. @xref{IMAP}, for more information.
13924 Note that for the Kerberos, GSSAPI, @acronym{TLS}/@acronym{SSL} and STARTTLS support you
13925 may need external programs and libraries, @xref{IMAP}.
13931 The name of the @acronym{IMAP} server. The default is taken from the
13932 @env{MAILHOST} environment variable.
13935 The port number of the @acronym{IMAP} server. The default is @samp{143}, or
13936 @samp{993} for @acronym{TLS}/@acronym{SSL} connections.
13939 The user name to give to the @acronym{IMAP} server. The default is the login
13943 The password to give to the @acronym{IMAP} server. If not specified, the user is
13947 What stream to use for connecting to the server, this is one of the
13948 symbols in @code{imap-stream-alist}. Right now, this means
13949 @samp{gssapi}, @samp{kerberos4}, @samp{starttls}, @samp{tls},
13950 @samp{ssl}, @samp{shell} or the default @samp{network}.
13952 @item :authentication
13953 Which authenticator to use for authenticating to the server, this is
13954 one of the symbols in @code{imap-authenticator-alist}. Right now,
13955 this means @samp{gssapi}, @samp{kerberos4}, @samp{digest-md5},
13956 @samp{cram-md5}, @samp{anonymous} or the default @samp{login}.
13959 When using the `shell' :stream, the contents of this variable is
13960 mapped into the @code{imap-shell-program} variable. This should be a
13961 @code{format}-like string (or list of strings). Here's an example:
13967 The valid format specifier characters are:
13971 The name of the server.
13974 User name from @code{imap-default-user}.
13977 The port number of the server.
13980 The values used for these specs are taken from the values you give the
13981 corresponding keywords.
13984 The name of the mailbox to get mail from. The default is @samp{INBOX}
13985 which normally is the mailbox which receive incoming mail.
13988 The predicate used to find articles to fetch. The default, @samp{UNSEEN
13989 UNDELETED}, is probably the best choice for most people, but if you
13990 sometimes peek in your mailbox with a @acronym{IMAP} client and mark some
13991 articles as read (or; SEEN) you might want to set this to @samp{1:*}.
13992 Then all articles in the mailbox is fetched, no matter what. For a
13993 complete list of predicates, see RFC 2060 section 6.4.4.
13996 How to flag fetched articles on the server, the default @samp{\Deleted}
13997 will mark them as deleted, an alternative would be @samp{\Seen} which
13998 would simply mark them as read. These are the two most likely choices,
13999 but more flags are defined in RFC 2060 section 2.3.2.
14002 If non-@code{nil}, don't remove all articles marked as deleted in the
14003 mailbox after finishing the fetch.
14007 An example @acronym{IMAP} mail source:
14010 (imap :server "mail.mycorp.com"
14012 :fetchflag "\\Seen")
14016 Get mail from a webmail server, such as @uref{http://www.hotmail.com/},
14017 @uref{http://webmail.netscape.com/}, @uref{http://www.netaddress.com/},
14018 @uref{http://mail.yahoo.com/}.
14020 NOTE: Webmail largely depends on cookies. A "one-line-cookie" patch is
14021 required for url "4.0pre.46".
14023 WARNING: Mails may be lost. NO WARRANTY.
14029 The type of the webmail server. The default is @code{hotmail}. The
14030 alternatives are @code{netscape}, @code{netaddress}, @code{my-deja}.
14033 The user name to give to the webmail server. The default is the login
14037 The password to give to the webmail server. If not specified, the user is
14041 If non-@code{nil}, only fetch unread articles and don't move them to
14042 trash folder after finishing the fetch.
14046 An example webmail source:
14049 (webmail :subtype 'hotmail
14051 :password "secret")
14056 @item Common Keywords
14057 Common keywords can be used in any type of mail source.
14063 If non-@code{nil}, fetch the mail even when Gnus is unplugged. If you
14064 use directory source to get mail, you can specify it as in this
14069 '((directory :path "/home/pavel/.Spool/"
14074 Gnus will then fetch your mail even when you are unplugged. This is
14075 useful when you use local mail and news.
14080 @subsubsection Function Interface
14082 Some of the above keywords specify a Lisp function to be executed.
14083 For each keyword @code{:foo}, the Lisp variable @code{foo} is bound to
14084 the value of the keyword while the function is executing. For example,
14085 consider the following mail-source setting:
14088 (setq mail-sources '((pop :user "jrl"
14089 :server "pophost" :function fetchfunc)))
14092 While the function @code{fetchfunc} is executing, the symbol @code{user}
14093 is bound to @code{"jrl"}, and the symbol @code{server} is bound to
14094 @code{"pophost"}. The symbols @code{port}, @code{password},
14095 @code{program}, @code{prescript}, @code{postscript}, @code{function},
14096 and @code{authentication} are also bound (to their default values).
14098 See above for a list of keywords for each type of mail source.
14101 @node Mail Source Customization
14102 @subsubsection Mail Source Customization
14104 The following is a list of variables that influence how the mail is
14105 fetched. You would normally not need to set or change any of these
14109 @item mail-source-crash-box
14110 @vindex mail-source-crash-box
14111 File where mail will be stored while processing it. The default is@*
14112 @file{~/.emacs-mail-crash-box}.
14114 @item mail-source-delete-incoming
14115 @vindex mail-source-delete-incoming
14116 If non-@code{nil}, delete incoming files after handling them. If
14117 @code{t}, delete the files immediately, if @code{nil}, never delete any
14118 files. If a positive number, delete files older than number of days
14119 (This will only happen, when receiving new mail). You may also set
14120 @code{mail-source-delete-incoming} to @code{nil} and call
14121 @code{mail-source-delete-old-incoming} from a hook or interactively.
14123 @item mail-source-delete-old-incoming-confirm
14124 @vindex mail-source-delete-old-incoming-confirm
14125 If non-@code{nil}, ask for for confirmation before deleting old incoming
14126 files. This variable only applies when
14127 @code{mail-source-delete-incoming} is a positive number.
14129 @item mail-source-ignore-errors
14130 @vindex mail-source-ignore-errors
14131 If non-@code{nil}, ignore errors when reading mail from a mail source.
14133 @item mail-source-directory
14134 @vindex mail-source-directory
14135 Directory where incoming mail source files (if any) will be stored. The
14136 default is @file{~/Mail/}. At present, the only thing this is used for
14137 is to say where the incoming files will be stored if the variable
14138 @code{mail-source-delete-incoming} is @code{nil} or a number.
14140 @item mail-source-incoming-file-prefix
14141 @vindex mail-source-incoming-file-prefix
14142 Prefix for file name for storing incoming mail. The default is
14143 @file{Incoming}, in which case files will end up with names like
14144 @file{Incoming30630D_} or @file{Incoming298602ZD}. This is really only
14145 relevant if @code{mail-source-delete-incoming} is @code{nil} or a
14148 @item mail-source-default-file-modes
14149 @vindex mail-source-default-file-modes
14150 All new mail files will get this file mode. The default is 384.
14152 @item mail-source-movemail-program
14153 @vindex mail-source-movemail-program
14154 If non-@code{nil}, name of program for fetching new mail. If
14155 @code{nil}, @code{movemail} in @var{exec-directory}.
14160 @node Fetching Mail
14161 @subsubsection Fetching Mail
14163 @vindex mail-sources
14164 @vindex nnmail-spool-file
14165 The way to actually tell Gnus where to get new mail from is to set
14166 @code{mail-sources} to a list of mail source specifiers
14167 (@pxref{Mail Source Specifiers}).
14169 If this variable (and the obsolescent @code{nnmail-spool-file}) is
14170 @code{nil}, the mail back ends will never attempt to fetch mail by
14173 If you want to fetch mail both from your local spool as well as a
14174 @acronym{POP} mail server, you'd say something like:
14179 (pop :server "pop3.mail.server"
14180 :password "secret")))
14183 Or, if you don't want to use any of the keyword defaults:
14187 '((file :path "/var/spool/mail/user-name")
14188 (pop :server "pop3.mail.server"
14191 :password "secret")))
14195 When you use a mail back end, Gnus will slurp all your mail from your
14196 inbox and plonk it down in your home directory. Gnus doesn't move any
14197 mail if you're not using a mail back end---you have to do a lot of magic
14198 invocations first. At the time when you have finished drawing the
14199 pentagram, lightened the candles, and sacrificed the goat, you really
14200 shouldn't be too surprised when Gnus moves your mail.
14204 @node Mail Back End Variables
14205 @subsection Mail Back End Variables
14207 These variables are (for the most part) pertinent to all the various
14211 @vindex nnmail-read-incoming-hook
14212 @item nnmail-read-incoming-hook
14213 The mail back ends all call this hook after reading new mail. You can
14214 use this hook to notify any mail watch programs, if you want to.
14216 @vindex nnmail-split-hook
14217 @item nnmail-split-hook
14218 @findex gnus-article-decode-encoded-words
14219 @cindex RFC 1522 decoding
14220 @cindex RFC 2047 decoding
14221 Hook run in the buffer where the mail headers of each message is kept
14222 just before the splitting based on these headers is done. The hook is
14223 free to modify the buffer contents in any way it sees fit---the buffer
14224 is discarded after the splitting has been done, and no changes performed
14225 in the buffer will show up in any files.
14226 @code{gnus-article-decode-encoded-words} is one likely function to add
14229 @vindex nnmail-pre-get-new-mail-hook
14230 @vindex nnmail-post-get-new-mail-hook
14231 @item nnmail-pre-get-new-mail-hook
14232 @itemx nnmail-post-get-new-mail-hook
14233 These are two useful hooks executed when treating new incoming
14234 mail---@code{nnmail-pre-get-new-mail-hook} (is called just before
14235 starting to handle the new mail) and
14236 @code{nnmail-post-get-new-mail-hook} (is called when the mail handling
14237 is done). Here's and example of using these two hooks to change the
14238 default file modes the new mail files get:
14241 (add-hook 'nnmail-pre-get-new-mail-hook
14242 (lambda () (set-default-file-modes 511)))
14244 (add-hook 'nnmail-post-get-new-mail-hook
14245 (lambda () (set-default-file-modes 551)))
14248 @item nnmail-use-long-file-names
14249 @vindex nnmail-use-long-file-names
14250 If non-@code{nil}, the mail back ends will use long file and directory
14251 names. Groups like @samp{mail.misc} will end up in directories
14252 (assuming use of @code{nnml} back end) or files (assuming use of
14253 @code{nnfolder} back end) like @file{mail.misc}. If it is @code{nil},
14254 the same group will end up in @file{mail/misc}.
14256 @item nnmail-delete-file-function
14257 @vindex nnmail-delete-file-function
14258 @findex delete-file
14259 Function called to delete files. It is @code{delete-file} by default.
14261 @item nnmail-cache-accepted-message-ids
14262 @vindex nnmail-cache-accepted-message-ids
14263 If non-@code{nil}, put the @code{Message-ID}s of articles imported into
14264 the back end (via @code{Gcc}, for instance) into the mail duplication
14265 discovery cache. The default is @code{nil}.
14267 @item nnmail-cache-ignore-groups
14268 @vindex nnmail-cache-ignore-groups
14269 This can be a regular expression or a list of regular expressions.
14270 Group names that match any of the regular expressions will never be
14271 recorded in the @code{Message-ID} cache.
14273 This can be useful, for example, when using Fancy Splitting
14274 (@pxref{Fancy Mail Splitting}) together with the function
14275 @code{nnmail-split-fancy-with-parent}.
14280 @node Fancy Mail Splitting
14281 @subsection Fancy Mail Splitting
14282 @cindex mail splitting
14283 @cindex fancy mail splitting
14285 @vindex nnmail-split-fancy
14286 @findex nnmail-split-fancy
14287 If the rather simple, standard method for specifying how to split mail
14288 doesn't allow you to do what you want, you can set
14289 @code{nnmail-split-methods} to @code{nnmail-split-fancy}. Then you can
14290 play with the @code{nnmail-split-fancy} variable.
14292 Let's look at an example value of this variable first:
14295 ;; @r{Messages from the mailer daemon are not crossposted to any of}
14296 ;; @r{the ordinary groups. Warnings are put in a separate group}
14297 ;; @r{from real errors.}
14298 (| ("from" mail (| ("subject" "warn.*" "mail.warning")
14300 ;; @r{Non-error messages are crossposted to all relevant}
14301 ;; @r{groups, but we don't crosspost between the group for the}
14302 ;; @r{(ding) list and the group for other (ding) related mail.}
14303 (& (| (any "ding@@ifi\\.uio\\.no" "ding.list")
14304 ("subject" "ding" "ding.misc"))
14305 ;; @r{Other mailing lists@dots{}}
14306 (any "procmail@@informatik\\.rwth-aachen\\.de" "procmail.list")
14307 (any "SmartList@@informatik\\.rwth-aachen\\.de" "SmartList.list")
14308 ;; @r{Both lists below have the same suffix, so prevent}
14309 ;; @r{cross-posting to mkpkg.list of messages posted only to}
14310 ;; @r{the bugs- list, but allow cross-posting when the}
14311 ;; @r{message was really cross-posted.}
14312 (any "bugs-mypackage@@somewhere" "mypkg.bugs")
14313 (any "mypackage@@somewhere" - "bugs-mypackage" "mypkg.list")
14314 ;; @r{People@dots{}}
14315 (any "larsi@@ifi\\.uio\\.no" "people.Lars_Magne_Ingebrigtsen"))
14316 ;; @r{Unmatched mail goes to the catch all group.}
14320 This variable has the format of a @dfn{split}. A split is a
14321 (possibly) recursive structure where each split may contain other
14322 splits. Here are the possible split syntaxes:
14327 If the split is a string, that will be taken as a group name. Normal
14328 regexp match expansion will be done. See below for examples.
14330 @c Don't fold this line.
14331 @item (@var{field} @var{value} [- @var{restrict} [@dots{}] ] @var{split} [@var{invert-partial}])
14332 The split can be a list containing at least three elements. If the
14333 first element @var{field} (a regexp matching a header) contains
14334 @var{value} (also a regexp) then store the message as specified by
14337 If @var{restrict} (yet another regexp) matches some string after
14338 @var{field} and before the end of the matched @var{value}, the
14339 @var{split} is ignored. If none of the @var{restrict} clauses match,
14340 @var{split} is processed.
14342 The last element @var{invert-partial} is optional. If it is
14343 non-@code{nil}, the match-partial-words behavior controlled by the
14344 variable @code{nnmail-split-fancy-match-partial-words} (see below) is
14345 be inverted. (New in Gnus 5.10.7)
14347 @item (| @var{split} @dots{})
14348 If the split is a list, and the first element is @code{|} (vertical
14349 bar), then process each @var{split} until one of them matches. A
14350 @var{split} is said to match if it will cause the mail message to be
14351 stored in one or more groups.
14353 @item (& @var{split} @dots{})
14354 If the split is a list, and the first element is @code{&}, then
14355 process all @var{split}s in the list.
14358 If the split is the symbol @code{junk}, then don't save (i.e., delete)
14359 this message. Use with extreme caution.
14361 @item (: @var{function} @var{arg1} @var{arg2} @dots{})
14362 If the split is a list, and the first element is @samp{:}, then the
14363 second element will be called as a function with @var{args} given as
14364 arguments. The function should return a @var{split}.
14367 For instance, the following function could be used to split based on the
14368 body of the messages:
14371 (defun split-on-body ()
14375 (goto-char (point-min))
14376 (when (re-search-forward "Some.*string" nil t)
14380 The buffer is narrowed to the message in question when @var{function}
14381 is run. That's why @code{(widen)} needs to be called after
14382 @code{save-excursion} and @code{save-restriction} in the example
14383 above. Also note that with the nnimap back end, message bodies will
14384 not be downloaded by default. You need to set
14385 @code{nnimap-split-download-body} to @code{t} to do that
14386 (@pxref{Splitting in IMAP}).
14388 @item (! @var{func} @var{split})
14389 If the split is a list, and the first element is @code{!}, then
14390 @var{split} will be processed, and @var{func} will be called as a
14391 function with the result of @var{split} as argument. @var{func}
14392 should return a split.
14395 If the split is @code{nil}, it is ignored.
14399 In these splits, @var{field} must match a complete field name.
14401 Normally, @var{value} in these splits must match a complete @emph{word}
14402 according to the fundamental mode syntax table. In other words, all
14403 @var{value}'s will be implicitly surrounded by @code{\<...\>} markers,
14404 which are word delimiters. Therefore, if you use the following split,
14408 (any "joe" "joemail")
14412 messages sent from @samp{joedavis@@foo.org} will normally not be filed
14413 in @samp{joemail}. If you want to alter this behavior, you can use any
14414 of the following three ways:
14418 @vindex nnmail-split-fancy-match-partial-words
14419 You can set the @code{nnmail-split-fancy-match-partial-words} variable
14420 to non-@code{nil} in order to ignore word boundaries and instead the
14421 match becomes more like a grep. This variable controls whether partial
14422 words are matched during fancy splitting. The default value is
14425 Note that it influences all @var{value}'s in your split rules.
14428 @var{value} beginning with @code{.*} ignores word boundaries in front of
14429 a word. Similarly, if @var{value} ends with @code{.*}, word boundaries
14430 in the rear of a word will be ignored. For example, the @var{value}
14431 @code{"@@example\\.com"} does not match @samp{foo@@example.com} but
14432 @code{".*@@example\\.com"} does.
14435 You can set the @var{invert-partial} flag in your split rules of the
14436 @samp{(@var{field} @var{value} @dots{})} types, aforementioned in this
14437 section. If the flag is set, word boundaries on both sides of a word
14438 are ignored even if @code{nnmail-split-fancy-match-partial-words} is
14439 @code{nil}. Contrarily, if the flag is set, word boundaries are not
14440 ignored even if @code{nnmail-split-fancy-match-partial-words} is
14441 non-@code{nil}. (New in Gnus 5.10.7)
14444 @vindex nnmail-split-abbrev-alist
14445 @var{field} and @var{value} can also be Lisp symbols, in that case
14446 they are expanded as specified by the variable
14447 @code{nnmail-split-abbrev-alist}. This is an alist of cons cells,
14448 where the @sc{car} of a cell contains the key, and the @sc{cdr}
14449 contains the associated value. Predefined entries in
14450 @code{nnmail-split-abbrev-alist} include:
14454 Matches the @samp{From}, @samp{Sender} and @samp{Resent-From} fields.
14456 Matches the @samp{To}, @samp{Cc}, @samp{Apparently-To},
14457 @samp{Resent-To} and @samp{Resent-Cc} fields.
14459 Is the union of the @code{from} and @code{to} entries.
14462 @vindex nnmail-split-fancy-syntax-table
14463 @code{nnmail-split-fancy-syntax-table} is the syntax table in effect
14464 when all this splitting is performed.
14466 If you want to have Gnus create groups dynamically based on some
14467 information in the headers (i.e., do @code{replace-match}-like
14468 substitutions in the group names), you can say things like:
14471 (any "debian-\\b\\(\\w+\\)@@lists.debian.org" "mail.debian.\\1")
14474 In this example, messages sent to @samp{debian-foo@@lists.debian.org}
14475 will be filed in @samp{mail.debian.foo}.
14477 If the string contains the element @samp{\&}, then the previously
14478 matched string will be substituted. Similarly, the elements @samp{\\1}
14479 up to @samp{\\9} will be substituted with the text matched by the
14480 groupings 1 through 9.
14482 @vindex nnmail-split-lowercase-expanded
14483 Where @code{nnmail-split-lowercase-expanded} controls whether the
14484 lowercase of the matched string should be used for the substitution.
14485 Setting it as non-@code{nil} is useful to avoid the creation of multiple
14486 groups when users send to an address using different case
14487 (i.e. mailing-list@@domain vs Mailing-List@@Domain). The default value
14490 @findex nnmail-split-fancy-with-parent
14491 @code{nnmail-split-fancy-with-parent} is a function which allows you to
14492 split followups into the same groups their parents are in. Sometimes
14493 you can't make splitting rules for all your mail. For example, your
14494 boss might send you personal mail regarding different projects you are
14495 working on, and as you can't tell your boss to put a distinguishing
14496 string into the subject line, you have to resort to manually moving the
14497 messages into the right group. With this function, you only have to do
14498 it once per thread.
14500 To use this feature, you have to set @code{nnmail-treat-duplicates}
14501 and @code{nnmail-cache-accepted-message-ids} to a non-@code{nil}
14502 value. And then you can include @code{nnmail-split-fancy-with-parent}
14503 using the colon feature, like so:
14505 (setq nnmail-treat-duplicates 'warn ; @r{or @code{delete}}
14506 nnmail-cache-accepted-message-ids t
14508 '(| (: nnmail-split-fancy-with-parent)
14509 ;; @r{other splits go here}
14513 This feature works as follows: when @code{nnmail-treat-duplicates} is
14514 non-@code{nil}, Gnus records the message id of every message it sees
14515 in the file specified by the variable
14516 @code{nnmail-message-id-cache-file}, together with the group it is in
14517 (the group is omitted for non-mail messages). When mail splitting is
14518 invoked, the function @code{nnmail-split-fancy-with-parent} then looks
14519 at the References (and In-Reply-To) header of each message to split
14520 and searches the file specified by @code{nnmail-message-id-cache-file}
14521 for the message ids. When it has found a parent, it returns the
14522 corresponding group name unless the group name matches the regexp
14523 @code{nnmail-split-fancy-with-parent-ignore-groups}. It is
14524 recommended that you set @code{nnmail-message-id-cache-length} to a
14525 somewhat higher number than the default so that the message ids are
14526 still in the cache. (A value of 5000 appears to create a file some
14527 300 kBytes in size.)
14528 @vindex nnmail-cache-accepted-message-ids
14529 When @code{nnmail-cache-accepted-message-ids} is non-@code{nil}, Gnus
14530 also records the message ids of moved articles, so that the followup
14531 messages goes into the new group.
14533 Also see the variable @code{nnmail-cache-ignore-groups} if you don't
14534 want certain groups to be recorded in the cache. For example, if all
14535 outgoing messages are written to an ``outgoing'' group, you could set
14536 @code{nnmail-cache-ignore-groups} to match that group name.
14537 Otherwise, answers to all your messages would end up in the
14538 ``outgoing'' group.
14541 @node Group Mail Splitting
14542 @subsection Group Mail Splitting
14543 @cindex mail splitting
14544 @cindex group mail splitting
14546 @findex gnus-group-split
14547 If you subscribe to dozens of mailing lists but you don't want to
14548 maintain mail splitting rules manually, group mail splitting is for you.
14549 You just have to set @code{to-list} and/or @code{to-address} in group
14550 parameters or group customization and set @code{nnmail-split-methods} to
14551 @code{gnus-group-split}. This splitting function will scan all groups
14552 for those parameters and split mail accordingly, i.e., messages posted
14553 from or to the addresses specified in the parameters @code{to-list} or
14554 @code{to-address} of a mail group will be stored in that group.
14556 Sometimes, mailing lists have multiple addresses, and you may want mail
14557 splitting to recognize them all: just set the @code{extra-aliases} group
14558 parameter to the list of additional addresses and it's done. If you'd
14559 rather use a regular expression, set @code{split-regexp}.
14561 All these parameters in a group will be used to create an
14562 @code{nnmail-split-fancy} split, in which the @var{field} is @samp{any},
14563 the @var{value} is a single regular expression that matches
14564 @code{to-list}, @code{to-address}, all of @code{extra-aliases} and all
14565 matches of @code{split-regexp}, and the @var{split} is the name of the
14566 group. @var{restrict}s are also supported: just set the
14567 @code{split-exclude} parameter to a list of regular expressions.
14569 If you can't get the right split to be generated using all these
14570 parameters, or you just need something fancier, you can set the
14571 parameter @code{split-spec} to an @code{nnmail-split-fancy} split. In
14572 this case, all other aforementioned parameters will be ignored by
14573 @code{gnus-group-split}. In particular, @code{split-spec} may be set to
14574 @code{nil}, in which case the group will be ignored by
14575 @code{gnus-group-split}.
14577 @vindex gnus-group-split-default-catch-all-group
14578 @code{gnus-group-split} will do cross-posting on all groups that match,
14579 by defining a single @code{&} fancy split containing one split for each
14580 group. If a message doesn't match any split, it will be stored in the
14581 group named in @code{gnus-group-split-default-catch-all-group}, unless
14582 some group has @code{split-spec} set to @code{catch-all}, in which case
14583 that group is used as the catch-all group. Even though this variable is
14584 often used just to name a group, it may also be set to an arbitrarily
14585 complex fancy split (after all, a group name is a fancy split), and this
14586 may be useful to split mail that doesn't go to any mailing list to
14587 personal mail folders. Note that this fancy split is added as the last
14588 element of a @code{|} split list that also contains a @code{&} split
14589 with the rules extracted from group parameters.
14591 It's time for an example. Assume the following group parameters have
14596 ((to-address . "bar@@femail.com")
14597 (split-regexp . ".*@@femail\\.com"))
14599 ((to-list . "foo@@nowhere.gov")
14600 (extra-aliases "foo@@localhost" "foo-redist@@home")
14601 (split-exclude "bugs-foo" "rambling-foo")
14602 (admin-address . "foo-request@@nowhere.gov"))
14604 ((split-spec . catch-all))
14607 Setting @code{nnmail-split-methods} to @code{gnus-group-split} will
14608 behave as if @code{nnmail-split-fancy} had been selected and variable
14609 @code{nnmail-split-fancy} had been set as follows:
14612 (| (& (any "\\(bar@@femail\\.com\\|.*@@femail\\.com\\)" "mail.bar")
14613 (any "\\(foo@@nowhere\\.gov\\|foo@@localhost\\|foo-redist@@home\\)"
14614 - "bugs-foo" - "rambling-foo" "mail.foo"))
14618 @findex gnus-group-split-fancy
14619 If you'd rather not use group splitting for all your mail groups, you
14620 may use it for only some of them, by using @code{nnmail-split-fancy}
14624 (: gnus-group-split-fancy @var{groups} @var{no-crosspost} @var{catch-all})
14627 @var{groups} may be a regular expression or a list of group names whose
14628 parameters will be scanned to generate the output split.
14629 @var{no-crosspost} can be used to disable cross-posting; in this case, a
14630 single @code{|} split will be output. @var{catch-all} is the fall back
14631 fancy split, used like @code{gnus-group-split-default-catch-all-group}.
14632 If @var{catch-all} is @code{nil}, or if @code{split-regexp} matches the
14633 empty string in any selected group, no catch-all split will be issued.
14634 Otherwise, if some group has @code{split-spec} set to @code{catch-all},
14635 this group will override the value of the @var{catch-all} argument.
14637 @findex gnus-group-split-setup
14638 Unfortunately, scanning all groups and their parameters can be quite
14639 slow, especially considering that it has to be done for every message.
14640 But don't despair! The function @code{gnus-group-split-setup} can be
14641 used to enable @code{gnus-group-split} in a much more efficient way. It
14642 sets @code{nnmail-split-methods} to @code{nnmail-split-fancy} and sets
14643 @code{nnmail-split-fancy} to the split produced by
14644 @code{gnus-group-split-fancy}. Thus, the group parameters are only
14645 scanned once, no matter how many messages are split.
14647 @findex gnus-group-split-update
14648 However, if you change group parameters, you'd have to update
14649 @code{nnmail-split-fancy} manually. You can do it by running
14650 @code{gnus-group-split-update}. If you'd rather have it updated
14651 automatically, just tell @code{gnus-group-split-setup} to do it for
14652 you. For example, add to your @file{~/.gnus.el}:
14655 (gnus-group-split-setup @var{auto-update} @var{catch-all})
14658 If @var{auto-update} is non-@code{nil}, @code{gnus-group-split-update}
14659 will be added to @code{nnmail-pre-get-new-mail-hook}, so you won't ever
14660 have to worry about updating @code{nnmail-split-fancy} again. If you
14661 don't omit @var{catch-all} (it's optional, equivalent to @code{nil}),
14662 @code{gnus-group-split-default-catch-all-group} will be set to its
14665 @vindex gnus-group-split-updated-hook
14666 Because you may want to change @code{nnmail-split-fancy} after it is set
14667 by @code{gnus-group-split-update}, this function will run
14668 @code{gnus-group-split-updated-hook} just before finishing.
14670 @node Incorporating Old Mail
14671 @subsection Incorporating Old Mail
14672 @cindex incorporating old mail
14673 @cindex import old mail
14675 Most people have lots of old mail stored in various file formats. If
14676 you have set up Gnus to read mail using one of the spiffy Gnus mail
14677 back ends, you'll probably wish to have that old mail incorporated into
14680 Doing so can be quite easy.
14682 To take an example: You're reading mail using @code{nnml}
14683 (@pxref{Mail Spool}), and have set @code{nnmail-split-methods} to a
14684 satisfactory value (@pxref{Splitting Mail}). You have an old Unix mbox
14685 file filled with important, but old, mail. You want to move it into
14686 your @code{nnml} groups.
14692 Go to the group buffer.
14695 Type @kbd{G f} and give the file name to the mbox file when prompted to create an
14696 @code{nndoc} group from the mbox file (@pxref{Foreign Groups}).
14699 Type @kbd{SPACE} to enter the newly created group.
14702 Type @kbd{M P b} to process-mark all articles in this group's buffer
14703 (@pxref{Setting Process Marks}).
14706 Type @kbd{B r} to respool all the process-marked articles, and answer
14707 @samp{nnml} when prompted (@pxref{Mail Group Commands}).
14710 All the mail messages in the mbox file will now also be spread out over
14711 all your @code{nnml} groups. Try entering them and check whether things
14712 have gone without a glitch. If things look ok, you may consider
14713 deleting the mbox file, but I wouldn't do that unless I was absolutely
14714 sure that all the mail has ended up where it should be.
14716 Respooling is also a handy thing to do if you're switching from one mail
14717 back end to another. Just respool all the mail in the old mail groups
14718 using the new mail back end.
14721 @node Expiring Mail
14722 @subsection Expiring Mail
14723 @cindex article expiry
14725 Traditional mail readers have a tendency to remove mail articles when
14726 you mark them as read, in some way. Gnus takes a fundamentally
14727 different approach to mail reading.
14729 Gnus basically considers mail just to be news that has been received in
14730 a rather peculiar manner. It does not think that it has the power to
14731 actually change the mail, or delete any mail messages. If you enter a
14732 mail group, and mark articles as ``read'', or kill them in some other
14733 fashion, the mail articles will still exist on the system. I repeat:
14734 Gnus will not delete your old, read mail. Unless you ask it to, of
14737 To make Gnus get rid of your unwanted mail, you have to mark the
14738 articles as @dfn{expirable}. (With the default key bindings, this means
14739 that you have to type @kbd{E}.) This does not mean that the articles
14740 will disappear right away, however. In general, a mail article will be
14741 deleted from your system if, 1) it is marked as expirable, AND 2) it is
14742 more than one week old. If you do not mark an article as expirable, it
14743 will remain on your system until hell freezes over. This bears
14744 repeating one more time, with some spurious capitalizations: IF you do
14745 NOT mark articles as EXPIRABLE, Gnus will NEVER delete those ARTICLES.
14747 You do not have to mark articles as expirable by hand. Gnus provides
14748 two features, called ``auto-expire'' and ``total-expire'', that can help you
14749 with this. In a nutshell, ``auto-expire'' means that Gnus hits @kbd{E}
14750 for you when you select an article. And ``total-expire'' means that Gnus
14751 considers all articles as expirable that are read. So, in addition to
14752 the articles marked @samp{E}, also the articles marked @samp{r},
14753 @samp{R}, @samp{O}, @samp{K}, @samp{Y} and so on are considered
14756 When should either auto-expire or total-expire be used? Most people
14757 who are subscribed to mailing lists split each list into its own group
14758 and then turn on auto-expire or total-expire for those groups.
14759 (@xref{Splitting Mail}, for more information on splitting each list
14760 into its own group.)
14762 Which one is better, auto-expire or total-expire? It's not easy to
14763 answer. Generally speaking, auto-expire is probably faster. Another
14764 advantage of auto-expire is that you get more marks to work with: for
14765 the articles that are supposed to stick around, you can still choose
14766 between tick and dormant and read marks. But with total-expire, you
14767 only have dormant and ticked to choose from. The advantage of
14768 total-expire is that it works well with adaptive scoring (@pxref{Adaptive
14769 Scoring}). Auto-expire works with normal scoring but not with adaptive
14772 @vindex gnus-auto-expirable-newsgroups
14773 Groups that match the regular expression
14774 @code{gnus-auto-expirable-newsgroups} will have all articles that you
14775 read marked as expirable automatically. All articles marked as
14776 expirable have an @samp{E} in the first column in the summary buffer.
14778 By default, if you have auto expiry switched on, Gnus will mark all the
14779 articles you read as expirable, no matter if they were read or unread
14780 before. To avoid having articles marked as read marked as expirable
14781 automatically, you can put something like the following in your
14782 @file{~/.gnus.el} file:
14784 @vindex gnus-mark-article-hook
14786 (remove-hook 'gnus-mark-article-hook
14787 'gnus-summary-mark-read-and-unread-as-read)
14788 (add-hook 'gnus-mark-article-hook 'gnus-summary-mark-unread-as-read)
14791 Note that making a group auto-expirable doesn't mean that all read
14792 articles are expired---only the articles marked as expirable
14793 will be expired. Also note that using the @kbd{d} command won't make
14794 articles expirable---only semi-automatic marking of articles as read will
14795 mark the articles as expirable in auto-expirable groups.
14797 Let's say you subscribe to a couple of mailing lists, and you want the
14798 articles you have read to disappear after a while:
14801 (setq gnus-auto-expirable-newsgroups
14802 "mail.nonsense-list\\|mail.nice-list")
14805 Another way to have auto-expiry happen is to have the element
14806 @code{auto-expire} in the group parameters of the group.
14808 If you use adaptive scoring (@pxref{Adaptive Scoring}) and
14809 auto-expiring, you'll have problems. Auto-expiring and adaptive scoring
14810 don't really mix very well.
14812 @vindex nnmail-expiry-wait
14813 The @code{nnmail-expiry-wait} variable supplies the default time an
14814 expirable article has to live. Gnus starts counting days from when the
14815 message @emph{arrived}, not from when it was sent. The default is seven
14818 Gnus also supplies a function that lets you fine-tune how long articles
14819 are to live, based on what group they are in. Let's say you want to
14820 have one month expiry period in the @samp{mail.private} group, a one day
14821 expiry period in the @samp{mail.junk} group, and a six day expiry period
14824 @vindex nnmail-expiry-wait-function
14826 (setq nnmail-expiry-wait-function
14828 (cond ((string= group "mail.private")
14830 ((string= group "mail.junk")
14832 ((string= group "important")
14838 The group names this function is fed are ``unadorned'' group
14839 names---no @samp{nnml:} prefixes and the like.
14841 The @code{nnmail-expiry-wait} variable and
14842 @code{nnmail-expiry-wait-function} function can either be a number (not
14843 necessarily an integer) or one of the symbols @code{immediate} or
14846 You can also use the @code{expiry-wait} group parameter to selectively
14847 change the expiry period (@pxref{Group Parameters}).
14849 @vindex nnmail-expiry-target
14850 The normal action taken when expiring articles is to delete them.
14851 However, in some circumstances it might make more sense to move them
14852 to other groups instead of deleting them. The variable
14853 @code{nnmail-expiry-target} (and the @code{expiry-target} group
14854 parameter) controls this. The variable supplies a default value for
14855 all groups, which can be overridden for specific groups by the group
14856 parameter. default value is @code{delete}, but this can also be a
14857 string (which should be the name of the group the message should be
14858 moved to), or a function (which will be called in a buffer narrowed to
14859 the message in question, and with the name of the group being moved
14860 from as its parameter) which should return a target---either a group
14861 name or @code{delete}.
14863 Here's an example for specifying a group name:
14865 (setq nnmail-expiry-target "nnml:expired")
14868 @findex nnmail-fancy-expiry-target
14869 @vindex nnmail-fancy-expiry-targets
14870 Gnus provides a function @code{nnmail-fancy-expiry-target} which will
14871 expire mail to groups according to the variable
14872 @code{nnmail-fancy-expiry-targets}. Here's an example:
14875 (setq nnmail-expiry-target 'nnmail-fancy-expiry-target
14876 nnmail-fancy-expiry-targets
14877 '((to-from "boss" "nnfolder:Work")
14878 ("subject" "IMPORTANT" "nnfolder:IMPORTANT.%Y.%b")
14879 ("from" ".*" "nnfolder:Archive-%Y")))
14882 With this setup, any mail that has @code{IMPORTANT} in its Subject
14883 header and was sent in the year @code{YYYY} and month @code{MMM}, will
14884 get expired to the group @code{nnfolder:IMPORTANT.YYYY.MMM}. If its
14885 From or To header contains the string @code{boss}, it will get expired
14886 to @code{nnfolder:Work}. All other mail will get expired to
14887 @code{nnfolder:Archive-YYYY}.
14889 @vindex nnmail-keep-last-article
14890 If @code{nnmail-keep-last-article} is non-@code{nil}, Gnus will never
14891 expire the final article in a mail newsgroup. This is to make life
14892 easier for procmail users.
14894 @vindex gnus-total-expirable-newsgroups
14895 By the way: That line up there, about Gnus never expiring non-expirable
14896 articles, is a lie. If you put @code{total-expire} in the group
14897 parameters, articles will not be marked as expirable, but all read
14898 articles will be put through the expiry process. Use with extreme
14899 caution. Even more dangerous is the
14900 @code{gnus-total-expirable-newsgroups} variable. All groups that match
14901 this regexp will have all read articles put through the expiry process,
14902 which means that @emph{all} old mail articles in the groups in question
14903 will be deleted after a while. Use with extreme caution, and don't come
14904 crying to me when you discover that the regexp you used matched the
14905 wrong group and all your important mail has disappeared. Be a
14906 @emph{man}! Or a @emph{woman}! Whatever you feel more comfortable
14909 Most people make most of their mail groups total-expirable, though.
14911 @vindex gnus-inhibit-user-auto-expire
14912 If @code{gnus-inhibit-user-auto-expire} is non-@code{nil}, user marking
14913 commands will not mark an article as expirable, even if the group has
14914 auto-expire turned on.
14918 @subsection Washing Mail
14919 @cindex mail washing
14920 @cindex list server brain damage
14921 @cindex incoming mail treatment
14923 Mailers and list servers are notorious for doing all sorts of really,
14924 really stupid things with mail. ``Hey, RFC 822 doesn't explicitly
14925 prohibit us from adding the string @code{wE aRe ElItE!!!!!1!!} to the
14926 end of all lines passing through our server, so let's do that!!!!1!''
14927 Yes, but RFC 822 wasn't designed to be read by morons. Things that were
14928 considered to be self-evident were not discussed. So. Here we are.
14930 Case in point: The German version of Microsoft Exchange adds @samp{AW:
14931 } to the subjects of replies instead of @samp{Re: }. I could pretend to
14932 be shocked and dismayed by this, but I haven't got the energy. It is to
14935 Gnus provides a plethora of functions for washing articles while
14936 displaying them, but it might be nicer to do the filtering before
14937 storing the mail to disk. For that purpose, we have three hooks and
14938 various functions that can be put in these hooks.
14941 @item nnmail-prepare-incoming-hook
14942 @vindex nnmail-prepare-incoming-hook
14943 This hook is called before doing anything with the mail and is meant for
14944 grand, sweeping gestures. It is called in a buffer that contains all
14945 the new, incoming mail. Functions to be used include:
14948 @item nnheader-ms-strip-cr
14949 @findex nnheader-ms-strip-cr
14950 Remove trailing carriage returns from each line. This is default on
14951 Emacs running on MS machines.
14955 @item nnmail-prepare-incoming-header-hook
14956 @vindex nnmail-prepare-incoming-header-hook
14957 This hook is called narrowed to each header. It can be used when
14958 cleaning up the headers. Functions that can be used include:
14961 @item nnmail-remove-leading-whitespace
14962 @findex nnmail-remove-leading-whitespace
14963 Clear leading white space that ``helpful'' listservs have added to the
14964 headers to make them look nice. Aaah.
14966 (Note that this function works on both the header on the body of all
14967 messages, so it is a potentially dangerous function to use (if a body
14968 of a message contains something that looks like a header line). So
14969 rather than fix the bug, it is of course the right solution to make it
14970 into a feature by documenting it.)
14972 @item nnmail-remove-list-identifiers
14973 @findex nnmail-remove-list-identifiers
14974 Some list servers add an identifier---for example, @samp{(idm)}---to the
14975 beginning of all @code{Subject} headers. I'm sure that's nice for
14976 people who use stone age mail readers. This function will remove
14977 strings that match the @code{nnmail-list-identifiers} regexp, which can
14978 also be a list of regexp. @code{nnmail-list-identifiers} may not contain
14981 For instance, if you want to remove the @samp{(idm)} and the
14982 @samp{nagnagnag} identifiers:
14985 (setq nnmail-list-identifiers
14986 '("(idm)" "nagnagnag"))
14989 This can also be done non-destructively with
14990 @code{gnus-list-identifiers}, @xref{Article Hiding}.
14992 @item nnmail-remove-tabs
14993 @findex nnmail-remove-tabs
14994 Translate all @samp{TAB} characters into @samp{SPACE} characters.
14996 @item nnmail-fix-eudora-headers
14997 @findex nnmail-fix-eudora-headers
14999 Eudora produces broken @code{References} headers, but OK
15000 @code{In-Reply-To} headers. This function will get rid of the
15001 @code{References} headers.
15005 @item nnmail-prepare-incoming-message-hook
15006 @vindex nnmail-prepare-incoming-message-hook
15007 This hook is called narrowed to each message. Functions to be used
15011 @item article-de-quoted-unreadable
15012 @findex article-de-quoted-unreadable
15013 Decode Quoted Readable encoding.
15020 @subsection Duplicates
15022 @vindex nnmail-treat-duplicates
15023 @vindex nnmail-message-id-cache-length
15024 @vindex nnmail-message-id-cache-file
15025 @cindex duplicate mails
15026 If you are a member of a couple of mailing lists, you will sometimes
15027 receive two copies of the same mail. This can be quite annoying, so
15028 @code{nnmail} checks for and treats any duplicates it might find. To do
15029 this, it keeps a cache of old @code{Message-ID}s---
15030 @code{nnmail-message-id-cache-file}, which is @file{~/.nnmail-cache} by
15031 default. The approximate maximum number of @code{Message-ID}s stored
15032 there is controlled by the @code{nnmail-message-id-cache-length}
15033 variable, which is 1000 by default. (So 1000 @code{Message-ID}s will be
15034 stored.) If all this sounds scary to you, you can set
15035 @code{nnmail-treat-duplicates} to @code{warn} (which is what it is by
15036 default), and @code{nnmail} won't delete duplicate mails. Instead it
15037 will insert a warning into the head of the mail saying that it thinks
15038 that this is a duplicate of a different message.
15040 This variable can also be a function. If that's the case, the function
15041 will be called from a buffer narrowed to the message in question with
15042 the @code{Message-ID} as a parameter. The function must return either
15043 @code{nil}, @code{warn}, or @code{delete}.
15045 You can turn this feature off completely by setting the variable to
15048 If you want all the duplicate mails to be put into a special
15049 @dfn{duplicates} group, you could do that using the normal mail split
15053 (setq nnmail-split-fancy
15054 '(| ;; @r{Messages duplicates go to a separate group.}
15055 ("gnus-warning" "duplicat\\(e\\|ion\\) of message" "duplicate")
15056 ;; @r{Message from daemons, postmaster, and the like to another.}
15057 (any mail "mail.misc")
15058 ;; @r{Other rules.}
15064 (setq nnmail-split-methods
15065 '(("duplicates" "^Gnus-Warning:.*duplicate")
15066 ;; @r{Other rules.}
15070 Here's a neat feature: If you know that the recipient reads her mail
15071 with Gnus, and that she has @code{nnmail-treat-duplicates} set to
15072 @code{delete}, you can send her as many insults as you like, just by
15073 using a @code{Message-ID} of a mail that you know that she's already
15074 received. Think of all the fun! She'll never see any of it! Whee!
15077 @node Not Reading Mail
15078 @subsection Not Reading Mail
15080 If you start using any of the mail back ends, they have the annoying
15081 habit of assuming that you want to read mail with them. This might not
15082 be unreasonable, but it might not be what you want.
15084 If you set @code{mail-sources} and @code{nnmail-spool-file} to
15085 @code{nil}, none of the back ends will ever attempt to read incoming
15086 mail, which should help.
15088 @vindex nnbabyl-get-new-mail
15089 @vindex nnmbox-get-new-mail
15090 @vindex nnml-get-new-mail
15091 @vindex nnmh-get-new-mail
15092 @vindex nnfolder-get-new-mail
15093 This might be too much, if, for instance, you are reading mail quite
15094 happily with @code{nnml} and just want to peek at some old Rmail
15095 file you have stashed away with @code{nnbabyl}. All back ends have
15096 variables called back-end-@code{get-new-mail}. If you want to disable
15097 the @code{nnbabyl} mail reading, you edit the virtual server for the
15098 group to have a setting where @code{nnbabyl-get-new-mail} to @code{nil}.
15100 All the mail back ends will call @code{nn}*@code{-prepare-save-mail-hook}
15101 narrowed to the article to be saved before saving it when reading
15105 @node Choosing a Mail Back End
15106 @subsection Choosing a Mail Back End
15108 Gnus will read the mail spool when you activate a mail group. The mail
15109 file is first copied to your home directory. What happens after that
15110 depends on what format you want to store your mail in.
15112 There are six different mail back ends in the standard Gnus, and more
15113 back ends are available separately. The mail back end most people use
15114 (because it is possibly the fastest) is @code{nnml} (@pxref{Mail
15118 * Unix Mail Box:: Using the (quite) standard Un*x mbox.
15119 * Rmail Babyl:: Emacs programs use the Rmail Babyl format.
15120 * Mail Spool:: Store your mail in a private spool?
15121 * MH Spool:: An mhspool-like back end.
15122 * Maildir:: Another one-file-per-message format.
15123 * Mail Folders:: Having one file for each group.
15124 * Comparing Mail Back Ends:: An in-depth looks at pros and cons.
15128 @node Unix Mail Box
15129 @subsubsection Unix Mail Box
15131 @cindex unix mail box
15133 @vindex nnmbox-active-file
15134 @vindex nnmbox-mbox-file
15135 The @dfn{nnmbox} back end will use the standard Un*x mbox file to store
15136 mail. @code{nnmbox} will add extra headers to each mail article to say
15137 which group it belongs in.
15139 Virtual server settings:
15142 @item nnmbox-mbox-file
15143 @vindex nnmbox-mbox-file
15144 The name of the mail box in the user's home directory. Default is
15147 @item nnmbox-active-file
15148 @vindex nnmbox-active-file
15149 The name of the active file for the mail box. Default is
15150 @file{~/.mbox-active}.
15152 @item nnmbox-get-new-mail
15153 @vindex nnmbox-get-new-mail
15154 If non-@code{nil}, @code{nnmbox} will read incoming mail and split it
15155 into groups. Default is @code{t}.
15160 @subsubsection Rmail Babyl
15164 @vindex nnbabyl-active-file
15165 @vindex nnbabyl-mbox-file
15166 The @dfn{nnbabyl} back end will use a Babyl mail box (aka. @dfn{Rmail
15167 mbox}) to store mail. @code{nnbabyl} will add extra headers to each
15168 mail article to say which group it belongs in.
15170 Virtual server settings:
15173 @item nnbabyl-mbox-file
15174 @vindex nnbabyl-mbox-file
15175 The name of the Rmail mbox file. The default is @file{~/RMAIL}
15177 @item nnbabyl-active-file
15178 @vindex nnbabyl-active-file
15179 The name of the active file for the rmail box. The default is
15180 @file{~/.rmail-active}
15182 @item nnbabyl-get-new-mail
15183 @vindex nnbabyl-get-new-mail
15184 If non-@code{nil}, @code{nnbabyl} will read incoming mail. Default is
15190 @subsubsection Mail Spool
15192 @cindex mail @acronym{NOV} spool
15194 The @dfn{nnml} spool mail format isn't compatible with any other known
15195 format. It should be used with some caution.
15197 @vindex nnml-directory
15198 If you use this back end, Gnus will split all incoming mail into files,
15199 one file for each mail, and put the articles into the corresponding
15200 directories under the directory specified by the @code{nnml-directory}
15201 variable. The default value is @file{~/Mail/}.
15203 You do not have to create any directories beforehand; Gnus will take
15206 If you have a strict limit as to how many files you are allowed to store
15207 in your account, you should not use this back end. As each mail gets its
15208 own file, you might very well occupy thousands of inodes within a few
15209 weeks. If this is no problem for you, and it isn't a problem for you
15210 having your friendly systems administrator walking around, madly,
15211 shouting ``Who is eating all my inodes?! Who? Who!?!'', then you should
15212 know that this is probably the fastest format to use. You do not have
15213 to trudge through a big mbox file just to read your new mail.
15215 @code{nnml} is probably the slowest back end when it comes to article
15216 splitting. It has to create lots of files, and it also generates
15217 @acronym{NOV} databases for the incoming mails. This makes it possibly the
15218 fastest back end when it comes to reading mail.
15220 @cindex self contained nnml servers
15222 When the marks file is used (which it is by default), @code{nnml}
15223 servers have the property that you may backup them using @code{tar} or
15224 similar, and later be able to restore them into Gnus (by adding the
15225 proper @code{nnml} server) and have all your marks be preserved. Marks
15226 for a group are usually stored in the @code{.marks} file (but see
15227 @code{nnml-marks-file-name}) within each @code{nnml} group's directory.
15228 Individual @code{nnml} groups are also possible to backup, use @kbd{G m}
15229 to restore the group (after restoring the backup into the nnml
15232 If for some reason you believe your @file{.marks} files are screwed
15233 up, you can just delete them all. Gnus will then correctly regenerate
15234 them next time it starts.
15236 Virtual server settings:
15239 @item nnml-directory
15240 @vindex nnml-directory
15241 All @code{nnml} directories will be placed under this directory. The
15242 default is the value of @code{message-directory} (whose default value
15245 @item nnml-active-file
15246 @vindex nnml-active-file
15247 The active file for the @code{nnml} server. The default is
15248 @file{~/Mail/active}.
15250 @item nnml-newsgroups-file
15251 @vindex nnml-newsgroups-file
15252 The @code{nnml} group descriptions file. @xref{Newsgroups File
15253 Format}. The default is @file{~/Mail/newsgroups}.
15255 @item nnml-get-new-mail
15256 @vindex nnml-get-new-mail
15257 If non-@code{nil}, @code{nnml} will read incoming mail. The default is
15260 @item nnml-nov-is-evil
15261 @vindex nnml-nov-is-evil
15262 If non-@code{nil}, this back end will ignore any @acronym{NOV} files. The
15263 default is @code{nil}.
15265 @item nnml-nov-file-name
15266 @vindex nnml-nov-file-name
15267 The name of the @acronym{NOV} files. The default is @file{.overview}.
15269 @item nnml-prepare-save-mail-hook
15270 @vindex nnml-prepare-save-mail-hook
15271 Hook run narrowed to an article before saving.
15273 @item nnml-marks-is-evil
15274 @vindex nnml-marks-is-evil
15275 If non-@code{nil}, this back end will ignore any @sc{marks} files. The
15276 default is @code{nil}.
15278 @item nnml-marks-file-name
15279 @vindex nnml-marks-file-name
15280 The name of the @dfn{marks} files. The default is @file{.marks}.
15282 @item nnml-use-compressed-files
15283 @vindex nnml-use-compressed-files
15284 If non-@code{nil}, @code{nnml} will allow using compressed message
15285 files. This requires @code{auto-compression-mode} to be enabled
15286 (@pxref{Compressed Files, ,Compressed Files, emacs, The Emacs Manual}).
15287 If the value of @code{nnml-use-compressed-files} is a string, it is used
15288 as the file extension specifying the comression program. You can set it
15289 to @samp{.bz2} if your Emacs supports it. A value of @code{t} is
15290 equivalent to @samp{.gz}.
15292 @item nnml-compressed-files-size-threshold
15293 @vindex nnml-compressed-files-size-threshold
15294 Default size threshold for compressed message files. Message files with
15295 bodies larger than that many characters will be automatically compressed
15296 if @code{nnml-use-compressed-files} is non-@code{nil}.
15300 @findex nnml-generate-nov-databases
15301 If your @code{nnml} groups and @acronym{NOV} files get totally out of
15302 whack, you can do a complete update by typing @kbd{M-x
15303 nnml-generate-nov-databases}. This command will trawl through the
15304 entire @code{nnml} hierarchy, looking at each and every article, so it
15305 might take a while to complete. A better interface to this
15306 functionality can be found in the server buffer (@pxref{Server
15311 @subsubsection MH Spool
15313 @cindex mh-e mail spool
15315 @code{nnmh} is just like @code{nnml}, except that is doesn't generate
15316 @acronym{NOV} databases and it doesn't keep an active file or marks
15317 file. This makes @code{nnmh} a @emph{much} slower back end than
15318 @code{nnml}, but it also makes it easier to write procmail scripts
15321 Virtual server settings:
15324 @item nnmh-directory
15325 @vindex nnmh-directory
15326 All @code{nnmh} directories will be located under this directory. The
15327 default is the value of @code{message-directory} (whose default is
15330 @item nnmh-get-new-mail
15331 @vindex nnmh-get-new-mail
15332 If non-@code{nil}, @code{nnmh} will read incoming mail. The default is
15336 @vindex nnmh-be-safe
15337 If non-@code{nil}, @code{nnmh} will go to ridiculous lengths to make
15338 sure that the articles in the folder are actually what Gnus thinks
15339 they are. It will check date stamps and stat everything in sight, so
15340 setting this to @code{t} will mean a serious slow-down. If you never
15341 use anything but Gnus to read the @code{nnmh} articles, you do not
15342 have to set this variable to @code{t}. The default is @code{nil}.
15347 @subsubsection Maildir
15351 @code{nnmaildir} stores mail in the maildir format, with each maildir
15352 corresponding to a group in Gnus. This format is documented here:
15353 @uref{http://cr.yp.to/proto/maildir.html} and here:
15354 @uref{http://www.qmail.org/man/man5/maildir.html}. @code{nnmaildir}
15355 also stores extra information in the @file{.nnmaildir/} directory
15358 Maildir format was designed to allow concurrent deliveries and
15359 reading, without needing locks. With other back ends, you would have
15360 your mail delivered to a spool of some kind, and then you would
15361 configure Gnus to split mail from that spool into your groups. You
15362 can still do that with @code{nnmaildir}, but the more common
15363 configuration is to have your mail delivered directly to the maildirs
15364 that appear as group in Gnus.
15366 @code{nnmaildir} is designed to be perfectly reliable: @kbd{C-g} will
15367 never corrupt its data in memory, and @code{SIGKILL} will never
15368 corrupt its data in the filesystem.
15370 @code{nnmaildir} stores article marks and @acronym{NOV} data in each
15371 maildir. So you can copy a whole maildir from one Gnus setup to
15372 another, and you will keep your marks.
15374 Virtual server settings:
15378 For each of your @code{nnmaildir} servers (it's very unlikely that
15379 you'd need more than one), you need to create a directory and populate
15380 it with maildirs or symlinks to maildirs (and nothing else; do not
15381 choose a directory already used for other purposes). Each maildir
15382 will be represented in Gnus as a newsgroup on that server; the
15383 filename of the symlink will be the name of the group. Any filenames
15384 in the directory starting with @samp{.} are ignored. The directory is
15385 scanned when you first start Gnus, and each time you type @kbd{g} in
15386 the group buffer; if any maildirs have been removed or added,
15387 @code{nnmaildir} notices at these times.
15389 The value of the @code{directory} parameter should be a Lisp form
15390 which is processed by @code{eval} and @code{expand-file-name} to get
15391 the path of the directory for this server. The form is @code{eval}ed
15392 only when the server is opened; the resulting string is used until the
15393 server is closed. (If you don't know about forms and @code{eval},
15394 don't worry---a simple string will work.) This parameter is not
15395 optional; you must specify it. I don't recommend using
15396 @code{"~/Mail"} or a subdirectory of it; several other parts of Gnus
15397 use that directory by default for various things, and may get confused
15398 if @code{nnmaildir} uses it too. @code{"~/.nnmaildir"} is a typical
15401 @item target-prefix
15402 This should be a Lisp form which is processed by @code{eval} and
15403 @code{expand-file-name}. The form is @code{eval}ed only when the
15404 server is opened; the resulting string is used until the server is
15407 When you create a group on an @code{nnmaildir} server, the maildir is
15408 created with @code{target-prefix} prepended to its name, and a symlink
15409 pointing to that maildir is created, named with the plain group name.
15410 So if @code{directory} is @code{"~/.nnmaildir"} and
15411 @code{target-prefix} is @code{"../maildirs/"}, then when you create
15412 the group @code{foo}, @code{nnmaildir} will create
15413 @file{~/.nnmaildir/../maildirs/foo} as a maildir, and will create
15414 @file{~/.nnmaildir/foo} as a symlink pointing to
15415 @file{../maildirs/foo}.
15417 You can set @code{target-prefix} to a string without any slashes to
15418 create both maildirs and symlinks in the same @code{directory}; in
15419 this case, any maildirs found in @code{directory} whose names start
15420 with @code{target-prefix} will not be listed as groups (but the
15421 symlinks pointing to them will be).
15423 As a special case, if @code{target-prefix} is @code{""} (the default),
15424 then when you create a group, the maildir will be created in
15425 @code{directory} without a corresponding symlink. Beware that you
15426 cannot use @code{gnus-group-delete-group} on such groups without the
15427 @code{force} argument.
15429 @item directory-files
15430 This should be a function with the same interface as
15431 @code{directory-files} (such as @code{directory-files} itself). It is
15432 used to scan the server's @code{directory} for maildirs. This
15433 parameter is optional; the default is
15434 @code{nnheader-directory-files-safe} if
15435 @code{nnheader-directory-files-is-safe} is @code{nil}, and
15436 @code{directory-files} otherwise.
15437 (@code{nnheader-directory-files-is-safe} is checked only once when the
15438 server is opened; if you want to check it each time the directory is
15439 scanned, you'll have to provide your own function that does that.)
15442 If non-@code{nil}, then after scanning for new mail in the group
15443 maildirs themselves as usual, this server will also incorporate mail
15444 the conventional Gnus way, from @code{mail-sources} according to
15445 @code{nnmail-split-methods} or @code{nnmail-split-fancy}. The default
15446 value is @code{nil}.
15448 Do @emph{not} use the same maildir both in @code{mail-sources} and as
15449 an @code{nnmaildir} group. The results might happen to be useful, but
15450 that would be by chance, not by design, and the results might be
15451 different in the future. If your split rules create new groups,
15452 remember to supply a @code{create-directory} server parameter.
15455 @subsubsection Group parameters
15457 @code{nnmaildir} uses several group parameters. It's safe to ignore
15458 all this; the default behavior for @code{nnmaildir} is the same as the
15459 default behavior for other mail back ends: articles are deleted after
15460 one week, etc. Except for the expiry parameters, all this
15461 functionality is unique to @code{nnmaildir}, so you can ignore it if
15462 you're just trying to duplicate the behavior you already have with
15465 If the value of any of these parameters is a vector, the first element
15466 is evaluated as a Lisp form and the result is used, rather than the
15467 original value. If the value is not a vector, the value itself is
15468 evaluated as a Lisp form. (This is why these parameters use names
15469 different from those of other, similar parameters supported by other
15470 back ends: they have different, though similar, meanings.) (For
15471 numbers, strings, @code{nil}, and @code{t}, you can ignore the
15472 @code{eval} business again; for other values, remember to use an extra
15473 quote and wrap the value in a vector when appropriate.)
15477 An integer specifying the minimum age, in seconds, of an article
15478 before it will be expired, or the symbol @code{never} to specify that
15479 articles should never be expired. If this parameter is not set,
15480 @code{nnmaildir} falls back to the usual
15481 @code{nnmail-expiry-wait}(@code{-function}) variables (the
15482 @code{expiry-wait} group parameter overrides @code{nnmail-expiry-wait}
15483 and makes @code{nnmail-expiry-wait-function} ineffective). If you
15484 wanted a value of 3 days, you could use something like @code{[(* 3 24
15485 60 60)]}; @code{nnmaildir} will evaluate the form and use the result.
15486 An article's age is measured starting from the article file's
15487 modification time. Normally, this is the same as the article's
15488 delivery time, but editing an article makes it younger. Moving an
15489 article (other than via expiry) may also make an article younger.
15492 If this is set to a string such as a full Gnus group name, like
15494 "backend+server.address.string:group.name"
15496 and if it is not the name of the same group that the parameter belongs
15497 to, then articles will be moved to the specified group during expiry
15498 before being deleted. @emph{If this is set to an @code{nnmaildir}
15499 group, the article will be just as old in the destination group as it
15500 was in the source group.} So be careful with @code{expire-age} in the
15501 destination group. If this is set to the name of the same group that
15502 the parameter belongs to, then the article is not expired at all. If
15503 you use the vector form, the first element is evaluated once for each
15504 article. So that form can refer to
15505 @code{nnmaildir-article-file-name}, etc., to decide where to put the
15506 article. @emph{Even if this parameter is not set, @code{nnmaildir}
15507 does not fall back to the @code{expiry-target} group parameter or the
15508 @code{nnmail-expiry-target} variable.}
15511 If this is set to @code{t}, @code{nnmaildir} will treat the articles
15512 in this maildir as read-only. This means: articles are not renamed
15513 from @file{new/} into @file{cur/}; articles are only found in
15514 @file{new/}, not @file{cur/}; articles are never deleted; articles
15515 cannot be edited. @file{new/} is expected to be a symlink to the
15516 @file{new/} directory of another maildir---e.g., a system-wide mailbox
15517 containing a mailing list of common interest. Everything in the
15518 maildir outside @file{new/} is @emph{not} treated as read-only, so for
15519 a shared mailbox, you do still need to set up your own maildir (or
15520 have write permission to the shared mailbox); your maildir just won't
15521 contain extra copies of the articles.
15523 @item directory-files
15524 A function with the same interface as @code{directory-files}. It is
15525 used to scan the directories in the maildir corresponding to this
15526 group to find articles. The default is the function specified by the
15527 server's @code{directory-files} parameter.
15529 @item distrust-Lines:
15530 If non-@code{nil}, @code{nnmaildir} will always count the lines of an
15531 article, rather than use the @code{Lines:} header field. If
15532 @code{nil}, the header field will be used if present.
15535 A list of mark symbols, such as @code{['(read expire)]}. Whenever
15536 Gnus asks @code{nnmaildir} for article marks, @code{nnmaildir} will
15537 say that all articles have these marks, regardless of whether the
15538 marks stored in the filesystem say so. This is a proof-of-concept
15539 feature that will probably be removed eventually; it ought to be done
15540 in Gnus proper, or abandoned if it's not worthwhile.
15543 A list of mark symbols, such as @code{['(tick expire)]}. Whenever
15544 Gnus asks @code{nnmaildir} for article marks, @code{nnmaildir} will
15545 say that no articles have these marks, regardless of whether the marks
15546 stored in the filesystem say so. @code{never-marks} overrides
15547 @code{always-marks}. This is a proof-of-concept feature that will
15548 probably be removed eventually; it ought to be done in Gnus proper, or
15549 abandoned if it's not worthwhile.
15551 @item nov-cache-size
15552 An integer specifying the size of the @acronym{NOV} memory cache. To
15553 speed things up, @code{nnmaildir} keeps @acronym{NOV} data in memory
15554 for a limited number of articles in each group. (This is probably not
15555 worthwhile, and will probably be removed in the future.) This
15556 parameter's value is noticed only the first time a group is seen after
15557 the server is opened---i.e., when you first start Gnus, typically.
15558 The @acronym{NOV} cache is never resized until the server is closed
15559 and reopened. The default is an estimate of the number of articles
15560 that would be displayed in the summary buffer: a count of articles
15561 that are either marked with @code{tick} or not marked with
15562 @code{read}, plus a little extra.
15565 @subsubsection Article identification
15566 Articles are stored in the @file{cur/} subdirectory of each maildir.
15567 Each article file is named like @code{uniq:info}, where @code{uniq}
15568 contains no colons. @code{nnmaildir} ignores, but preserves, the
15569 @code{:info} part. (Other maildir readers typically use this part of
15570 the filename to store marks.) The @code{uniq} part uniquely
15571 identifies the article, and is used in various places in the
15572 @file{.nnmaildir/} subdirectory of the maildir to store information
15573 about the corresponding article. The full pathname of an article is
15574 available in the variable @code{nnmaildir-article-file-name} after you
15575 request the article in the summary buffer.
15577 @subsubsection NOV data
15578 An article identified by @code{uniq} has its @acronym{NOV} data (used
15579 to generate lines in the summary buffer) stored in
15580 @code{.nnmaildir/nov/uniq}. There is no
15581 @code{nnmaildir-generate-nov-databases} function. (There isn't much
15582 need for it---an article's @acronym{NOV} data is updated automatically
15583 when the article or @code{nnmail-extra-headers} has changed.) You can
15584 force @code{nnmaildir} to regenerate the @acronym{NOV} data for a
15585 single article simply by deleting the corresponding @acronym{NOV}
15586 file, but @emph{beware}: this will also cause @code{nnmaildir} to
15587 assign a new article number for this article, which may cause trouble
15588 with @code{seen} marks, the Agent, and the cache.
15590 @subsubsection Article marks
15591 An article identified by @code{uniq} is considered to have the mark
15592 @code{flag} when the file @file{.nnmaildir/marks/flag/uniq} exists.
15593 When Gnus asks @code{nnmaildir} for a group's marks, @code{nnmaildir}
15594 looks for such files and reports the set of marks it finds. When Gnus
15595 asks @code{nnmaildir} to store a new set of marks, @code{nnmaildir}
15596 creates and deletes the corresponding files as needed. (Actually,
15597 rather than create a new file for each mark, it just creates hard
15598 links to @file{.nnmaildir/markfile}, to save inodes.)
15600 You can invent new marks by creating a new directory in
15601 @file{.nnmaildir/marks/}. You can tar up a maildir and remove it from
15602 your server, untar it later, and keep your marks. You can add and
15603 remove marks yourself by creating and deleting mark files. If you do
15604 this while Gnus is running and your @code{nnmaildir} server is open,
15605 it's best to exit all summary buffers for @code{nnmaildir} groups and
15606 type @kbd{s} in the group buffer first, and to type @kbd{g} or
15607 @kbd{M-g} in the group buffer afterwards. Otherwise, Gnus might not
15608 pick up the changes, and might undo them.
15612 @subsubsection Mail Folders
15614 @cindex mbox folders
15615 @cindex mail folders
15617 @code{nnfolder} is a back end for storing each mail group in a
15618 separate file. Each file is in the standard Un*x mbox format.
15619 @code{nnfolder} will add extra headers to keep track of article
15620 numbers and arrival dates.
15622 @cindex self contained nnfolder servers
15624 When the marks file is used (which it is by default), @code{nnfolder}
15625 servers have the property that you may backup them using @code{tar} or
15626 similar, and later be able to restore them into Gnus (by adding the
15627 proper @code{nnfolder} server) and have all your marks be preserved.
15628 Marks for a group are usually stored in a file named as the mbox file
15629 with @code{.mrk} concatenated to it (but see
15630 @code{nnfolder-marks-file-suffix}) within the @code{nnfolder}
15631 directory. Individual @code{nnfolder} groups are also possible to
15632 backup, use @kbd{G m} to restore the group (after restoring the backup
15633 into the @code{nnfolder} directory).
15635 Virtual server settings:
15638 @item nnfolder-directory
15639 @vindex nnfolder-directory
15640 All the @code{nnfolder} mail boxes will be stored under this
15641 directory. The default is the value of @code{message-directory}
15642 (whose default is @file{~/Mail})
15644 @item nnfolder-active-file
15645 @vindex nnfolder-active-file
15646 The name of the active file. The default is @file{~/Mail/active}.
15648 @item nnfolder-newsgroups-file
15649 @vindex nnfolder-newsgroups-file
15650 The name of the group descriptions file. @xref{Newsgroups File
15651 Format}. The default is @file{~/Mail/newsgroups}
15653 @item nnfolder-get-new-mail
15654 @vindex nnfolder-get-new-mail
15655 If non-@code{nil}, @code{nnfolder} will read incoming mail. The
15656 default is @code{t}
15658 @item nnfolder-save-buffer-hook
15659 @vindex nnfolder-save-buffer-hook
15660 @cindex backup files
15661 Hook run before saving the folders. Note that Emacs does the normal
15662 backup renaming of files even with the @code{nnfolder} buffers. If
15663 you wish to switch this off, you could say something like the
15664 following in your @file{.emacs} file:
15667 (defun turn-off-backup ()
15668 (set (make-local-variable 'backup-inhibited) t))
15670 (add-hook 'nnfolder-save-buffer-hook 'turn-off-backup)
15673 @item nnfolder-delete-mail-hook
15674 @vindex nnfolder-delete-mail-hook
15675 Hook run in a buffer narrowed to the message that is to be deleted.
15676 This function can be used to copy the message to somewhere else, or to
15677 extract some information from it before removing it.
15679 @item nnfolder-nov-is-evil
15680 @vindex nnfolder-nov-is-evil
15681 If non-@code{nil}, this back end will ignore any @acronym{NOV} files. The
15682 default is @code{nil}.
15684 @item nnfolder-nov-file-suffix
15685 @vindex nnfolder-nov-file-suffix
15686 The extension for @acronym{NOV} files. The default is @file{.nov}.
15688 @item nnfolder-nov-directory
15689 @vindex nnfolder-nov-directory
15690 The directory where the @acronym{NOV} files should be stored. If
15691 @code{nil}, @code{nnfolder-directory} is used.
15693 @item nnfolder-marks-is-evil
15694 @vindex nnfolder-marks-is-evil
15695 If non-@code{nil}, this back end will ignore any @sc{marks} files. The
15696 default is @code{nil}.
15698 @item nnfolder-marks-file-suffix
15699 @vindex nnfolder-marks-file-suffix
15700 The extension for @sc{marks} files. The default is @file{.mrk}.
15702 @item nnfolder-marks-directory
15703 @vindex nnfolder-marks-directory
15704 The directory where the @sc{marks} files should be stored. If
15705 @code{nil}, @code{nnfolder-directory} is used.
15710 @findex nnfolder-generate-active-file
15711 @kindex M-x nnfolder-generate-active-file
15712 If you have lots of @code{nnfolder}-like files you'd like to read with
15713 @code{nnfolder}, you can use the @kbd{M-x nnfolder-generate-active-file}
15714 command to make @code{nnfolder} aware of all likely files in
15715 @code{nnfolder-directory}. This only works if you use long file names,
15718 @node Comparing Mail Back Ends
15719 @subsubsection Comparing Mail Back Ends
15721 First, just for terminology, the @dfn{back end} is the common word for a
15722 low-level access method---a transport, if you will, by which something
15723 is acquired. The sense is that one's mail has to come from somewhere,
15724 and so selection of a suitable back end is required in order to get that
15725 mail within spitting distance of Gnus.
15727 The same concept exists for Usenet itself: Though access to articles is
15728 typically done by @acronym{NNTP} these days, once upon a midnight dreary, everyone
15729 in the world got at Usenet by running a reader on the machine where the
15730 articles lay (the machine which today we call an @acronym{NNTP} server), and
15731 access was by the reader stepping into the articles' directory spool
15732 area directly. One can still select between either the @code{nntp} or
15733 @code{nnspool} back ends, to select between these methods, if one happens
15734 actually to live on the server (or can see its spool directly, anyway,
15737 The goal in selecting a mail back end is to pick one which
15738 simultaneously represents a suitable way of dealing with the original
15739 format plus leaving mail in a form that is convenient to use in the
15740 future. Here are some high and low points on each:
15745 UNIX systems have historically had a single, very common, and well-
15746 defined format. All messages arrive in a single @dfn{spool file}, and
15747 they are delineated by a line whose regular expression matches
15748 @samp{^From_}. (My notational use of @samp{_} is to indicate a space,
15749 to make it clear in this instance that this is not the RFC-specified
15750 @samp{From:} header.) Because Emacs and therefore Gnus emanate
15751 historically from the Unix environment, it is simplest if one does not
15752 mess a great deal with the original mailbox format, so if one chooses
15753 this back end, Gnus' primary activity in getting mail from the real spool
15754 area to Gnus' preferred directory is simply to copy it, with no
15755 (appreciable) format change in the process. It is the ``dumbest'' way
15756 to move mail into availability in the Gnus environment. This makes it
15757 fast to move into place, but slow to parse, when Gnus has to look at
15762 Once upon a time, there was the DEC-10 and DEC-20, running operating
15763 systems called TOPS and related things, and the usual (only?) mail
15764 reading environment was a thing called Babyl. I don't know what format
15765 was used for mail landing on the system, but Babyl had its own internal
15766 format to which mail was converted, primarily involving creating a
15767 spool-file-like entity with a scheme for inserting Babyl-specific
15768 headers and status bits above the top of each message in the file.
15769 Rmail was Emacs' first mail reader, it was written by Richard Stallman,
15770 and Stallman came out of that TOPS/Babyl environment, so he wrote Rmail
15771 to understand the mail files folks already had in existence. Gnus (and
15772 VM, for that matter) continue to support this format because it's
15773 perceived as having some good qualities in those mailer-specific
15774 headers/status bits stuff. Rmail itself still exists as well, of
15775 course, and is still maintained by Stallman.
15777 Both of the above forms leave your mail in a single file on your
15778 file system, and they must parse that entire file each time you take a
15783 @code{nnml} is the back end which smells the most as though you were
15784 actually operating with an @code{nnspool}-accessed Usenet system. (In
15785 fact, I believe @code{nnml} actually derived from @code{nnspool} code,
15786 lo these years ago.) One's mail is taken from the original spool file,
15787 and is then cut up into individual message files, 1:1. It maintains a
15788 Usenet-style active file (analogous to what one finds in an INN- or
15789 CNews-based news system in (for instance) @file{/var/lib/news/active},
15790 or what is returned via the @samp{NNTP LIST} verb) and also creates
15791 @dfn{overview} files for efficient group entry, as has been defined for
15792 @acronym{NNTP} servers for some years now. It is slower in mail-splitting,
15793 due to the creation of lots of files, updates to the @code{nnml} active
15794 file, and additions to overview files on a per-message basis, but it is
15795 extremely fast on access because of what amounts to the indexing support
15796 provided by the active file and overviews.
15798 @code{nnml} costs @dfn{inodes} in a big way; that is, it soaks up the
15799 resource which defines available places in the file system to put new
15800 files. Sysadmins take a dim view of heavy inode occupation within
15801 tight, shared file systems. But if you live on a personal machine where
15802 the file system is your own and space is not at a premium, @code{nnml}
15805 It is also problematic using this back end if you are living in a
15806 FAT16-based Windows world, since much space will be wasted on all these
15811 The Rand MH mail-reading system has been around UNIX systems for a very
15812 long time; it operates by splitting one's spool file of messages into
15813 individual files, but with little or no indexing support---@code{nnmh}
15814 is considered to be semantically equivalent to ``@code{nnml} without
15815 active file or overviews''. This is arguably the worst choice, because
15816 one gets the slowness of individual file creation married to the
15817 slowness of access parsing when learning what's new in one's groups.
15821 Basically the effect of @code{nnfolder} is @code{nnmbox} (the first
15822 method described above) on a per-group basis. That is, @code{nnmbox}
15823 itself puts @emph{all} one's mail in one file; @code{nnfolder} provides a
15824 little bit of optimization to this so that each of one's mail groups has
15825 a Unix mail box file. It's faster than @code{nnmbox} because each group
15826 can be parsed separately, and still provides the simple Unix mail box
15827 format requiring minimal effort in moving the mail around. In addition,
15828 it maintains an ``active'' file making it much faster for Gnus to figure
15829 out how many messages there are in each separate group.
15831 If you have groups that are expected to have a massive amount of
15832 messages, @code{nnfolder} is not the best choice, but if you receive
15833 only a moderate amount of mail, @code{nnfolder} is probably the most
15834 friendly mail back end all over.
15838 For configuring expiry and other things, @code{nnmaildir} uses
15839 incompatible group parameters, slightly different from those of other
15842 @code{nnmaildir} is largely similar to @code{nnml}, with some notable
15843 differences. Each message is stored in a separate file, but the
15844 filename is unrelated to the article number in Gnus. @code{nnmaildir}
15845 also stores the equivalent of @code{nnml}'s overview files in one file
15846 per article, so it uses about twice as many inodes as @code{nnml}. (Use
15847 @code{df -i} to see how plentiful your inode supply is.) If this slows
15848 you down or takes up very much space, consider switching to
15849 @uref{http://www.namesys.com/, ReiserFS} or another non-block-structured
15852 Since maildirs don't require locking for delivery, the maildirs you use
15853 as groups can also be the maildirs your mail is directly delivered to.
15854 This means you can skip Gnus' mail splitting if your mail is already
15855 organized into different mailboxes during delivery. A @code{directory}
15856 entry in @code{mail-sources} would have a similar effect, but would
15857 require one set of mailboxes for spooling deliveries (in mbox format,
15858 thus damaging message bodies), and another set to be used as groups (in
15859 whatever format you like). A maildir has a built-in spool, in the
15860 @code{new/} subdirectory. Beware that currently, mail moved from
15861 @code{new/} to @code{cur/} instead of via mail splitting will not
15862 undergo treatment such as duplicate checking.
15864 @code{nnmaildir} stores article marks for a given group in the
15865 corresponding maildir, in a way designed so that it's easy to manipulate
15866 them from outside Gnus. You can tar up a maildir, unpack it somewhere
15867 else, and still have your marks. @code{nnml} also stores marks, but
15868 it's not as easy to work with them from outside Gnus as with
15871 @code{nnmaildir} uses a significant amount of memory to speed things up.
15872 (It keeps in memory some of the things that @code{nnml} stores in files
15873 and that @code{nnmh} repeatedly parses out of message files.) If this
15874 is a problem for you, you can set the @code{nov-cache-size} group
15875 parameter to something small (0 would probably not work, but 1 probably
15876 would) to make it use less memory. This caching will probably be
15877 removed in the future.
15879 Startup is likely to be slower with @code{nnmaildir} than with other
15880 back ends. Everything else is likely to be faster, depending in part
15881 on your file system.
15883 @code{nnmaildir} does not use @code{nnoo}, so you cannot use @code{nnoo}
15884 to write an @code{nnmaildir}-derived back end.
15889 @node Browsing the Web
15890 @section Browsing the Web
15892 @cindex browsing the web
15896 Web-based discussion forums are getting more and more popular. On many
15897 subjects, the web-based forums have become the most important forums,
15898 eclipsing the importance of mailing lists and news groups. The reason
15899 is easy to understand---they are friendly to new users; you just point
15900 and click, and there's the discussion. With mailing lists, you have to
15901 go through a cumbersome subscription procedure, and most people don't
15902 even know what a news group is.
15904 The problem with this scenario is that web browsers are not very good at
15905 being newsreaders. They do not keep track of what articles you've read;
15906 they do not allow you to score on subjects you're interested in; they do
15907 not allow off-line browsing; they require you to click around and drive
15908 you mad in the end.
15910 So---if web browsers suck at reading discussion forums, why not use Gnus
15913 Gnus has been getting a bit of a collection of back ends for providing
15914 interfaces to these sources.
15918 * Web Searches:: Creating groups from articles that match a string.
15919 * Slashdot:: Reading the Slashdot comments.
15920 * Ultimate:: The Ultimate Bulletin Board systems.
15921 * Web Archive:: Reading mailing list archived on web.
15922 * RSS:: Reading RDF site summary.
15923 * Customizing W3:: Doing stuff to Emacs/W3 from Gnus.
15926 All the web sources require Emacs/W3 and the url library or those
15927 alternatives to work.
15929 The main caveat with all these web sources is that they probably won't
15930 work for a very long time. Gleaning information from the @acronym{HTML} data
15931 is guesswork at best, and when the layout is altered, the Gnus back end
15932 will fail. If you have reasonably new versions of these back ends,
15933 though, you should be ok.
15935 One thing all these Web methods have in common is that the Web sources
15936 are often down, unavailable or just plain too slow to be fun. In those
15937 cases, it makes a lot of sense to let the Gnus Agent (@pxref{Gnus
15938 Unplugged}) handle downloading articles, and then you can read them at
15939 leisure from your local disk. No more World Wide Wait for you.
15941 @node Archiving Mail
15942 @subsection Archiving Mail
15943 @cindex archiving mail
15944 @cindex backup of mail
15946 Some of the back ends, notably @code{nnml}, @code{nnfolder}, and
15947 @code{nnmaildir}, now actually store the article marks with each group.
15948 For these servers, archiving and restoring a group while preserving
15949 marks is fairly simple.
15951 (Preserving the group level and group parameters as well still
15952 requires ritual dancing and sacrifices to the @file{.newsrc.eld} deity
15955 To archive an entire @code{nnml}, @code{nnfolder}, or @code{nnmaildir}
15956 server, take a recursive copy of the server directory. There is no need
15957 to shut down Gnus, so archiving may be invoked by @code{cron} or
15958 similar. You restore the data by restoring the directory tree, and
15959 adding a server definition pointing to that directory in Gnus. The
15960 @ref{Article Backlog}, @ref{Asynchronous Fetching} and other things
15961 might interfere with overwriting data, so you may want to shut down Gnus
15962 before you restore the data.
15964 It is also possible to archive individual @code{nnml},
15965 @code{nnfolder}, or @code{nnmaildir} groups, while preserving marks.
15966 For @code{nnml} or @code{nnmaildir}, you copy all files in the group's
15967 directory. For @code{nnfolder} you need to copy both the base folder
15968 file itself (@file{FOO}, say), and the marks file (@file{FOO.mrk} in
15969 this example). Restoring the group is done with @kbd{G m} from the Group
15970 buffer. The last step makes Gnus notice the new directory.
15971 @code{nnmaildir} notices the new directory automatically, so @kbd{G m}
15972 is unnecessary in that case.
15975 @subsection Web Searches
15980 @cindex Usenet searches
15981 @cindex searching the Usenet
15983 It's, like, too neat to search the Usenet for articles that match a
15984 string, but it, like, totally @emph{sucks}, like, totally, to use one of
15985 those, like, Web browsers, and you, like, have to, rilly, like, look at
15986 the commercials, so, like, with Gnus you can do @emph{rad}, rilly,
15987 searches without having to use a browser.
15989 The @code{nnweb} back end allows an easy interface to the mighty search
15990 engine. You create an @code{nnweb} group, enter a search pattern, and
15991 then enter the group and read the articles like you would any normal
15992 group. The @kbd{G w} command in the group buffer (@pxref{Foreign
15993 Groups}) will do this in an easy-to-use fashion.
15995 @code{nnweb} groups don't really lend themselves to being solid
15996 groups---they have a very fleeting idea of article numbers. In fact,
15997 each time you enter an @code{nnweb} group (not even changing the search
15998 pattern), you are likely to get the articles ordered in a different
15999 manner. Not even using duplicate suppression (@pxref{Duplicate
16000 Suppression}) will help, since @code{nnweb} doesn't even know the
16001 @code{Message-ID} of the articles before reading them using some search
16002 engines (Google, for instance). The only possible way to keep track
16003 of which articles you've read is by scoring on the @code{Date}
16004 header---mark all articles posted before the last date you read the
16007 If the search engine changes its output substantially, @code{nnweb}
16008 won't be able to parse it and will fail. One could hardly fault the Web
16009 providers if they were to do this---their @emph{raison d'@^etre} is to
16010 make money off of advertisements, not to provide services to the
16011 community. Since @code{nnweb} washes the ads off all the articles, one
16012 might think that the providers might be somewhat miffed. We'll see.
16014 You must have the @code{url} and @code{W3} package or those alternatives
16015 (try @code{customize-group} on the @samp{mm-url} variable group)
16016 installed to be able to use @code{nnweb}.
16018 Virtual server variables:
16023 What search engine type is being used. The currently supported types
16024 are @code{google}, @code{dejanews}, and @code{gmane}. Note that
16025 @code{dejanews} is an alias to @code{google}.
16028 @vindex nnweb-search
16029 The search string to feed to the search engine.
16031 @item nnweb-max-hits
16032 @vindex nnweb-max-hits
16033 Advisory maximum number of hits per search to display. The default is
16036 @item nnweb-type-definition
16037 @vindex nnweb-type-definition
16038 Type-to-definition alist. This alist says what @code{nnweb} should do
16039 with the various search engine types. The following elements must be
16044 Function to decode the article and provide something that Gnus
16048 Function to create an article number to message header and URL alist.
16051 Function to send the search string to the search engine.
16054 The address the aforementioned function should send the search string
16058 Format string URL to fetch an article by @code{Message-ID}.
16065 @subsection Slashdot
16069 @uref{http://slashdot.org/, Slashdot} is a popular news site, with
16070 lively discussion following the news articles. @code{nnslashdot} will
16071 let you read this forum in a convenient manner.
16073 The easiest way to read this source is to put something like the
16074 following in your @file{~/.gnus.el} file:
16077 (setq gnus-secondary-select-methods
16078 '((nnslashdot "")))
16081 This will make Gnus query the @code{nnslashdot} back end for new comments
16082 and groups. The @kbd{F} command will subscribe each new news article as
16083 a new Gnus group, and you can read the comments by entering these
16084 groups. (Note that the default subscription method is to subscribe new
16085 groups as zombies. Other methods are available (@pxref{Subscription
16088 If you want to remove an old @code{nnslashdot} group, the @kbd{G DEL}
16089 command is the most handy tool (@pxref{Foreign Groups}).
16091 When following up to @code{nnslashdot} comments (or posting new
16092 comments), some light @acronym{HTML}izations will be performed. In
16093 particular, text quoted with @samp{> } will be quoted with
16094 @samp{blockquote} instead, and signatures will have @samp{br} added to
16095 the end of each line. Other than that, you can just write @acronym{HTML}
16096 directly into the message buffer. Note that Slashdot filters out some
16097 @acronym{HTML} forms.
16099 The following variables can be altered to change its behavior:
16102 @item nnslashdot-threaded
16103 Whether @code{nnslashdot} should display threaded groups or not. The
16104 default is @code{t}. To be able to display threads, @code{nnslashdot}
16105 has to retrieve absolutely all comments in a group upon entry. If a
16106 threaded display is not required, @code{nnslashdot} will only retrieve
16107 the comments that are actually wanted by the user. Threading is nicer,
16108 but much, much slower than unthreaded.
16110 @item nnslashdot-login-name
16111 @vindex nnslashdot-login-name
16112 The login name to use when posting.
16114 @item nnslashdot-password
16115 @vindex nnslashdot-password
16116 The password to use when posting.
16118 @item nnslashdot-directory
16119 @vindex nnslashdot-directory
16120 Where @code{nnslashdot} will store its files. The default is
16121 @file{~/News/slashdot/}.
16123 @item nnslashdot-active-url
16124 @vindex nnslashdot-active-url
16125 The @acronym{URL} format string that will be used to fetch the
16126 information on news articles and comments. The default is@*
16127 @samp{http://slashdot.org/search.pl?section=&min=%d}.
16129 @item nnslashdot-comments-url
16130 @vindex nnslashdot-comments-url
16131 The @acronym{URL} format string that will be used to fetch comments.
16133 @item nnslashdot-article-url
16134 @vindex nnslashdot-article-url
16135 The @acronym{URL} format string that will be used to fetch the news
16136 article. The default is
16137 @samp{http://slashdot.org/article.pl?sid=%s&mode=nocomment}.
16139 @item nnslashdot-threshold
16140 @vindex nnslashdot-threshold
16141 The score threshold. The default is -1.
16143 @item nnslashdot-group-number
16144 @vindex nnslashdot-group-number
16145 The number of old groups, in addition to the ten latest, to keep
16146 updated. The default is 0.
16153 @subsection Ultimate
16155 @cindex Ultimate Bulletin Board
16157 @uref{http://www.ultimatebb.com/, The Ultimate Bulletin Board} is
16158 probably the most popular Web bulletin board system used. It has a
16159 quite regular and nice interface, and it's possible to get the
16160 information Gnus needs to keep groups updated.
16162 The easiest way to get started with @code{nnultimate} is to say
16163 something like the following in the group buffer: @kbd{B nnultimate RET
16164 http://www.tcj.com/messboard/ubbcgi/ RET}. (Substitute the @acronym{URL}
16165 (not including @samp{Ultimate.cgi} or the like at the end) for a forum
16166 you're interested in; there's quite a list of them on the Ultimate web
16167 site.) Then subscribe to the groups you're interested in from the
16168 server buffer, and read them from the group buffer.
16170 The following @code{nnultimate} variables can be altered:
16173 @item nnultimate-directory
16174 @vindex nnultimate-directory
16175 The directory where @code{nnultimate} stores its files. The default is@*
16176 @file{~/News/ultimate/}.
16181 @subsection Web Archive
16183 @cindex Web Archive
16185 Some mailing lists only have archives on Web servers, such as
16186 @uref{http://www.egroups.com/} and
16187 @uref{http://www.mail-archive.com/}. It has a quite regular and nice
16188 interface, and it's possible to get the information Gnus needs to keep
16191 @findex gnus-group-make-warchive-group
16192 The easiest way to get started with @code{nnwarchive} is to say
16193 something like the following in the group buffer: @kbd{M-x
16194 gnus-group-make-warchive-group RET @var{an_egroup} RET egroups RET
16195 www.egroups.com RET @var{your@@email.address} RET}. (Substitute the
16196 @var{an_egroup} with the mailing list you subscribed, the
16197 @var{your@@email.address} with your email address.), or to browse the
16198 back end by @kbd{B nnwarchive RET mail-archive RET}.
16200 The following @code{nnwarchive} variables can be altered:
16203 @item nnwarchive-directory
16204 @vindex nnwarchive-directory
16205 The directory where @code{nnwarchive} stores its files. The default is@*
16206 @file{~/News/warchive/}.
16208 @item nnwarchive-login
16209 @vindex nnwarchive-login
16210 The account name on the web server.
16212 @item nnwarchive-passwd
16213 @vindex nnwarchive-passwd
16214 The password for your account on the web server.
16222 Some web sites have an RDF Site Summary (@acronym{RSS}).
16223 @acronym{RSS} is a format for summarizing headlines from news related
16224 sites (such as BBC or CNN). But basically anything list-like can be
16225 presented as an @acronym{RSS} feed: weblogs, changelogs or recent
16226 changes to a wiki (e.g. @url{http://cliki.net/recent-changes.rdf}).
16228 @acronym{RSS} has a quite regular and nice interface, and it's
16229 possible to get the information Gnus needs to keep groups updated.
16231 Note: you had better use Emacs which supports the @code{utf-8} coding
16232 system because @acronym{RSS} uses UTF-8 for encoding non-@acronym{ASCII}
16233 text by default. It is also used by default for non-@acronym{ASCII}
16236 @kindex G R (Group)
16237 Use @kbd{G R} from the group buffer to subscribe to a feed---you will be
16238 prompted for the location, the title and the description of the feed.
16239 The title, which allows any characters, will be used for the group name
16240 and the name of the group data file. The description can be omitted.
16242 An easy way to get started with @code{nnrss} is to say something like
16243 the following in the group buffer: @kbd{B nnrss RET RET y}, then
16244 subscribe to groups.
16246 The @code{nnrss} back end saves the group data file in
16247 @code{nnrss-directory} (see below) for each @code{nnrss} group. File
16248 names containing non-@acronym{ASCII} characters will be encoded by the
16249 coding system specified with the @code{nnmail-pathname-coding-system}
16250 variable. If it is @code{nil}, in Emacs the coding system defaults to
16251 the value of @code{default-file-name-coding-system}. If you are using
16252 XEmacs and want to use non-@acronym{ASCII} group names, you should set
16253 the value for the @code{nnmail-pathname-coding-system} variable properly.
16255 The @code{nnrss} back end generates @samp{multipart/alternative}
16256 @acronym{MIME} articles in which each contains a @samp{text/plain} part
16257 and a @samp{text/html} part.
16260 You can also use the following commands to import and export your
16261 subscriptions from a file in @acronym{OPML} format (Outline Processor
16264 @defun nnrss-opml-import file
16265 Prompt for an @acronym{OPML} file, and subscribe to each feed in the
16269 @defun nnrss-opml-export
16270 Write your current @acronym{RSS} subscriptions to a buffer in
16271 @acronym{OPML} format.
16274 The following @code{nnrss} variables can be altered:
16277 @item nnrss-directory
16278 @vindex nnrss-directory
16279 The directory where @code{nnrss} stores its files. The default is
16280 @file{~/News/rss/}.
16282 @item nnrss-file-coding-system
16283 @vindex nnrss-file-coding-system
16284 The coding system used when reading and writing the @code{nnrss} groups
16285 data files. The default is the value of
16286 @code{mm-universal-coding-system} (which defaults to @code{emacs-mule}
16287 in Emacs or @code{escape-quoted} in XEmacs).
16289 @item nnrss-use-local
16290 @vindex nnrss-use-local
16291 @findex nnrss-generate-download-script
16292 If you set @code{nnrss-use-local} to @code{t}, @code{nnrss} will read
16293 the feeds from local files in @code{nnrss-directory}. You can use
16294 the command @code{nnrss-generate-download-script} to generate a
16295 download script using @command{wget}.
16297 @item nnrss-wash-html-in-text-plain-parts
16298 Non-@code{nil} means that @code{nnrss} renders text in @samp{text/plain}
16299 parts as @acronym{HTML}. The function specified by the
16300 @code{mm-text-html-renderer} variable (@pxref{Display Customization,
16301 ,Display Customization, emacs-mime, The Emacs MIME Manual}) will be used
16302 to render text. If it is @code{nil}, which is the default, text will
16303 simply be folded. Leave it @code{nil} if you prefer to see
16304 @samp{text/html} parts.
16307 The following code may be helpful, if you want to show the description in
16308 the summary buffer.
16311 (add-to-list 'nnmail-extra-headers nnrss-description-field)
16312 (setq gnus-summary-line-format "%U%R%z%I%(%[%4L: %-15,15f%]%) %s%uX\n")
16314 (defun gnus-user-format-function-X (header)
16316 (assq nnrss-description-field (mail-header-extra header))))
16317 (if descr (concat "\n\t" (cdr descr)) "")))
16320 The following code may be useful to open an nnrss url directly from the
16324 (require 'browse-url)
16326 (defun browse-nnrss-url( arg )
16328 (let ((url (assq nnrss-url-field
16331 (assq (gnus-summary-article-number)
16332 gnus-newsgroup-data))))))
16335 (browse-url (cdr url))
16336 (gnus-summary-mark-as-read-forward 1))
16337 (gnus-summary-scroll-up arg))))
16339 (eval-after-load "gnus"
16340 #'(define-key gnus-summary-mode-map
16341 (kbd "<RET>") 'browse-nnrss-url))
16342 (add-to-list 'nnmail-extra-headers nnrss-url-field)
16345 Even if you have added @code{"text/html"} to the
16346 @code{mm-discouraged-alternatives} variable (@pxref{Display
16347 Customization, ,Display Customization, emacs-mime, The Emacs MIME
16348 Manual}) since you don't want to see @acronym{HTML} parts, it might be
16349 more useful especially in @code{nnrss} groups to display
16350 @samp{text/html} parts. Here's an example of setting
16351 @code{mm-discouraged-alternatives} as a group parameter (@pxref{Group
16352 Parameters}) in order to display @samp{text/html} parts only in
16353 @code{nnrss} groups:
16356 ;; @r{Set the default value of @code{mm-discouraged-alternatives}.}
16357 (eval-after-load "gnus-sum"
16359 'gnus-newsgroup-variables
16360 '(mm-discouraged-alternatives
16361 . '("text/html" "image/.*"))))
16363 ;; @r{Display @samp{text/html} parts in @code{nnrss} groups.}
16366 '("\\`nnrss:" (mm-discouraged-alternatives nil)))
16370 @node Customizing W3
16371 @subsection Customizing W3
16377 Gnus uses the url library to fetch web pages and Emacs/W3 (or those
16378 alternatives) to display web pages. Emacs/W3 is documented in its own
16379 manual, but there are some things that may be more relevant for Gnus
16382 For instance, a common question is how to make Emacs/W3 follow links
16383 using the @code{browse-url} functions (which will call some external web
16384 browser like Netscape). Here's one way:
16387 (eval-after-load "w3"
16389 (fset 'w3-fetch-orig (symbol-function 'w3-fetch))
16390 (defun w3-fetch (&optional url target)
16391 (interactive (list (w3-read-url-with-default)))
16392 (if (eq major-mode 'gnus-article-mode)
16394 (w3-fetch-orig url target)))))
16397 Put that in your @file{.emacs} file, and hitting links in W3-rendered
16398 @acronym{HTML} in the Gnus article buffers will use @code{browse-url} to
16405 @cindex @acronym{IMAP}
16407 @acronym{IMAP} is a network protocol for reading mail (or news, or @dots{}),
16408 think of it as a modernized @acronym{NNTP}. Connecting to a @acronym{IMAP}
16409 server is much similar to connecting to a news server, you just
16410 specify the network address of the server.
16412 @acronym{IMAP} has two properties. First, @acronym{IMAP} can do
16413 everything that @acronym{POP} can, it can hence be viewed as a
16414 @acronym{POP++}. Secondly, @acronym{IMAP} is a mail storage protocol,
16415 similar to @acronym{NNTP} being a news storage protocol---however,
16416 @acronym{IMAP} offers more features than @acronym{NNTP} because news
16417 is more or less read-only whereas mail is read-write.
16419 If you want to use @acronym{IMAP} as a @acronym{POP++}, use an imap
16420 entry in @code{mail-sources}. With this, Gnus will fetch mails from
16421 the @acronym{IMAP} server and store them on the local disk. This is
16422 not the usage described in this section---@xref{Mail Sources}.
16424 If you want to use @acronym{IMAP} as a mail storage protocol, use an nnimap
16425 entry in @code{gnus-secondary-select-methods}. With this, Gnus will
16426 manipulate mails stored on the @acronym{IMAP} server. This is the kind of
16427 usage explained in this section.
16429 A server configuration in @file{~/.gnus.el} with a few @acronym{IMAP}
16430 servers might look something like the following. (Note that for
16431 @acronym{TLS}/@acronym{SSL}, you need external programs and libraries,
16435 (setq gnus-secondary-select-methods
16436 '((nnimap "simpleserver") ; @r{no special configuration}
16437 ; @r{perhaps a ssh port forwarded server:}
16439 (nnimap-address "localhost")
16440 (nnimap-server-port 1430))
16441 ; @r{a UW server running on localhost}
16443 (nnimap-server-port 143)
16444 (nnimap-address "localhost")
16445 (nnimap-list-pattern ("INBOX" "mail/*")))
16446 ; @r{anonymous public cyrus server:}
16447 (nnimap "cyrus.andrew.cmu.edu"
16448 (nnimap-authenticator anonymous)
16449 (nnimap-list-pattern "archive.*")
16450 (nnimap-stream network))
16451 ; @r{a ssl server on a non-standard port:}
16453 (nnimap-address "vic20.somewhere.com")
16454 (nnimap-server-port 9930)
16455 (nnimap-stream ssl))))
16458 After defining the new server, you can subscribe to groups on the
16459 server using normal Gnus commands such as @kbd{U} in the Group Buffer
16460 (@pxref{Subscription Commands}) or via the Server Buffer
16461 (@pxref{Server Buffer}).
16463 The following variables can be used to create a virtual @code{nnimap}
16468 @item nnimap-address
16469 @vindex nnimap-address
16471 The address of the remote @acronym{IMAP} server. Defaults to the virtual
16472 server name if not specified.
16474 @item nnimap-server-port
16475 @vindex nnimap-server-port
16476 Port on server to contact. Defaults to port 143, or 993 for @acronym{TLS}/@acronym{SSL}.
16478 Note that this should be an integer, example server specification:
16481 (nnimap "mail.server.com"
16482 (nnimap-server-port 4711))
16485 @item nnimap-list-pattern
16486 @vindex nnimap-list-pattern
16487 String or list of strings of mailboxes to limit available groups to.
16488 This is used when the server has very many mailboxes and you're only
16489 interested in a few---some servers export your home directory via
16490 @acronym{IMAP}, you'll probably want to limit the mailboxes to those in
16491 @file{~/Mail/*} then.
16493 The string can also be a cons of REFERENCE and the string as above, what
16494 REFERENCE is used for is server specific, but on the University of
16495 Washington server it's a directory that will be concatenated with the
16498 Example server specification:
16501 (nnimap "mail.server.com"
16502 (nnimap-list-pattern ("INBOX" "Mail/*" "alt.sex.*"
16503 ("~friend/Mail/" . "list/*"))))
16506 @item nnimap-stream
16507 @vindex nnimap-stream
16508 The type of stream used to connect to your server. By default, nnimap
16509 will detect and automatically use all of the below, with the exception
16510 of @acronym{TLS}/@acronym{SSL}. (@acronym{IMAP} over
16511 @acronym{TLS}/@acronym{SSL} is being replaced by STARTTLS, which can
16512 be automatically detected, but it's not widely deployed yet.)
16514 Example server specification:
16517 (nnimap "mail.server.com"
16518 (nnimap-stream ssl))
16521 Please note that the value of @code{nnimap-stream} is a symbol!
16525 @dfn{gssapi:} Connect with GSSAPI (usually Kerberos 5). Requires the
16526 @samp{gsasl} or @samp{imtest} program.
16528 @dfn{kerberos4:} Connect with Kerberos 4. Requires the @samp{imtest} program.
16530 @dfn{starttls:} Connect via the STARTTLS extension (similar to
16531 @acronym{TLS}/@acronym{SSL}). Requires the external library @samp{starttls.el} and program
16534 @dfn{tls:} Connect through @acronym{TLS}. Requires GNUTLS (the program
16535 @samp{gnutls-cli}).
16537 @dfn{ssl:} Connect through @acronym{SSL}. Requires OpenSSL (the program
16538 @samp{openssl}) or SSLeay (@samp{s_client}).
16540 @dfn{shell:} Use a shell command to start @acronym{IMAP} connection.
16542 @dfn{network:} Plain, TCP/IP network connection.
16545 @vindex imap-kerberos4-program
16546 The @samp{imtest} program is shipped with Cyrus IMAPD. If you're
16547 using @samp{imtest} from Cyrus IMAPD < 2.0.14 (which includes version
16548 1.5.x and 1.6.x) you need to frob @code{imap-process-connection-type}
16549 to make @code{imap.el} use a pty instead of a pipe when communicating
16550 with @samp{imtest}. You will then suffer from a line length
16551 restrictions on @acronym{IMAP} commands, which might make Gnus seem to hang
16552 indefinitely if you have many articles in a mailbox. The variable
16553 @code{imap-kerberos4-program} contain parameters to pass to the imtest
16556 For @acronym{TLS} connection, the @code{gnutls-cli} program from GNUTLS is
16557 needed. It is available from
16558 @uref{http://www.gnu.org/software/gnutls/}.
16560 @vindex imap-gssapi-program
16561 This parameter specifies a list of command lines that invoke a GSSAPI
16562 authenticated @acronym{IMAP} stream in a subshell. They are tried
16563 sequentially until a connection is made, or the list has been
16564 exhausted. By default, @samp{gsasl} from GNU SASL, available from
16565 @uref{http://www.gnu.org/software/gsasl/}, and the @samp{imtest}
16566 program from Cyrus IMAPD (see @code{imap-kerberos4-program}), are
16569 @vindex imap-ssl-program
16570 For @acronym{SSL} connections, the OpenSSL program is available from
16571 @uref{http://www.openssl.org/}. OpenSSL was formerly known as SSLeay,
16572 and nnimap support it too---although the most recent versions of
16573 SSLeay, 0.9.x, are known to have serious bugs making it
16574 useless. Earlier versions, especially 0.8.x, of SSLeay are known to
16575 work. The variable @code{imap-ssl-program} contain parameters to pass
16578 @vindex imap-shell-program
16579 @vindex imap-shell-host
16580 For @acronym{IMAP} connections using the @code{shell} stream, the variable
16581 @code{imap-shell-program} specify what program to call.
16583 @item nnimap-authenticator
16584 @vindex nnimap-authenticator
16586 The authenticator used to connect to the server. By default, nnimap
16587 will use the most secure authenticator your server is capable of.
16589 Example server specification:
16592 (nnimap "mail.server.com"
16593 (nnimap-authenticator anonymous))
16596 Please note that the value of @code{nnimap-authenticator} is a symbol!
16600 @dfn{gssapi:} GSSAPI (usually kerberos 5) authentication. Requires
16601 external program @code{gsasl} or @code{imtest}.
16603 @dfn{kerberos4:} Kerberos 4 authentication. Requires external program
16606 @dfn{digest-md5:} Encrypted username/password via DIGEST-MD5. Requires
16607 external library @code{digest-md5.el}.
16609 @dfn{cram-md5:} Encrypted username/password via CRAM-MD5.
16611 @dfn{login:} Plain-text username/password via LOGIN.
16613 @dfn{anonymous:} Login as ``anonymous'', supplying your email address as password.
16616 @item nnimap-expunge-on-close
16618 @vindex nnimap-expunge-on-close
16619 Unlike Parmenides the @acronym{IMAP} designers have decided things that
16620 don't exist actually do exist. More specifically, @acronym{IMAP} has
16621 this concept of marking articles @code{Deleted} which doesn't actually
16622 delete them, and this (marking them @code{Deleted}, that is) is what
16623 nnimap does when you delete an article in Gnus (with @kbd{B DEL} or
16626 Since the articles aren't really removed when we mark them with the
16627 @code{Deleted} flag we'll need a way to actually delete them. Feel like
16628 running in circles yet?
16630 Traditionally, nnimap has removed all articles marked as @code{Deleted}
16631 when closing a mailbox but this is now configurable by this server
16634 The possible options are:
16639 The default behavior, delete all articles marked as ``Deleted'' when
16642 Never actually delete articles. Currently there is no way of showing
16643 the articles marked for deletion in nnimap, but other @acronym{IMAP} clients
16644 may allow you to do this. If you ever want to run the EXPUNGE command
16645 manually, @xref{Expunging mailboxes}.
16647 When closing mailboxes, nnimap will ask if you wish to expunge deleted
16652 @item nnimap-importantize-dormant
16653 @vindex nnimap-importantize-dormant
16655 If non-@code{nil} (the default), marks dormant articles as ticked (as
16656 well), for other @acronym{IMAP} clients. Within Gnus, dormant articles will
16657 naturally still (only) be marked as dormant. This is to make dormant
16658 articles stand out, just like ticked articles, in other @acronym{IMAP}
16659 clients. (In other words, Gnus has two ``Tick'' marks and @acronym{IMAP}
16662 Probably the only reason for frobing this would be if you're trying
16663 enable per-user persistent dormant flags, using something like:
16666 (setcdr (assq 'dormant nnimap-mark-to-flag-alist)
16667 (format "gnus-dormant-%s" (user-login-name)))
16668 (setcdr (assq 'dormant nnimap-mark-to-predicate-alist)
16669 (format "KEYWORD gnus-dormant-%s" (user-login-name)))
16672 In this case, you would not want the per-user dormant flag showing up
16673 as ticked for other users.
16675 @item nnimap-expunge-search-string
16677 @vindex nnimap-expunge-search-string
16679 This variable contain the @acronym{IMAP} search command sent to server when
16680 searching for articles eligible for expiring. The default is
16681 @code{"UID %s NOT SINCE %s"}, where the first @code{%s} is replaced by
16682 UID set and the second @code{%s} is replaced by a date.
16684 Probably the only useful value to change this to is
16685 @code{"UID %s NOT SENTSINCE %s"}, which makes nnimap use the Date: in
16686 messages instead of the internal article date. See section 6.4.4 of
16687 RFC 2060 for more information on valid strings.
16689 @item nnimap-authinfo-file
16690 @vindex nnimap-authinfo-file
16692 A file containing credentials used to log in on servers. The format is
16693 (almost) the same as the @code{ftp} @file{~/.netrc} file. See the
16694 variable @code{nntp-authinfo-file} for exact syntax; also see
16695 @ref{NNTP}. An example of an .authinfo line for an IMAP server, is:
16698 machine students.uio.no login larsi password geheimnis port imap
16701 Note that it should be @code{port imap}, or @code{port 143}, if you
16702 use a @code{nnimap-stream} of @code{tls} or @code{ssl}, even if the
16703 actual port number used is port 993 for secured IMAP. For
16704 convenience, Gnus will accept @code{port imaps} as a synonym of
16707 @item nnimap-need-unselect-to-notice-new-mail
16708 @vindex nnimap-need-unselect-to-notice-new-mail
16710 Unselect mailboxes before looking for new mail in them. Some servers
16711 seem to need this under some circumstances; it was reported that
16717 * Splitting in IMAP:: Splitting mail with nnimap.
16718 * Expiring in IMAP:: Expiring mail with nnimap.
16719 * Editing IMAP ACLs:: Limiting/enabling other users access to a mailbox.
16720 * Expunging mailboxes:: Equivalent of a ``compress mailbox'' button.
16721 * A note on namespaces:: How to (not) use @acronym{IMAP} namespace in Gnus.
16722 * Debugging IMAP:: What to do when things don't work.
16727 @node Splitting in IMAP
16728 @subsection Splitting in IMAP
16729 @cindex splitting imap mail
16731 Splitting is something Gnus users have loved and used for years, and now
16732 the rest of the world is catching up. Yeah, dream on, not many
16733 @acronym{IMAP} servers have server side splitting and those that have
16734 splitting seem to use some non-standard protocol. This means that
16735 @acronym{IMAP} support for Gnus has to do its own splitting.
16739 (Incidentally, people seem to have been dreaming on, and Sieve has
16740 gaining a market share and is supported by several IMAP servers.
16741 Fortunately, Gnus support it too, @xref{Sieve Commands}.)
16743 Here are the variables of interest:
16747 @item nnimap-split-crosspost
16748 @cindex splitting, crosspost
16750 @vindex nnimap-split-crosspost
16752 If non-@code{nil}, do crossposting if several split methods match the
16753 mail. If @code{nil}, the first match in @code{nnimap-split-rule}
16754 found will be used.
16756 Nnmail equivalent: @code{nnmail-crosspost}.
16758 @item nnimap-split-inbox
16759 @cindex splitting, inbox
16761 @vindex nnimap-split-inbox
16763 A string or a list of strings that gives the name(s) of @acronym{IMAP}
16764 mailboxes to split from. Defaults to @code{nil}, which means that
16765 splitting is disabled!
16768 (setq nnimap-split-inbox
16769 '("INBOX" ("~/friend/Mail" . "lists/*") "lists.imap"))
16772 No nnmail equivalent.
16774 @item nnimap-split-rule
16775 @cindex splitting, rules
16776 @vindex nnimap-split-rule
16778 New mail found in @code{nnimap-split-inbox} will be split according to
16781 This variable contains a list of lists, where the first element in the
16782 sublist gives the name of the @acronym{IMAP} mailbox to move articles
16783 matching the regexp in the second element in the sublist. Got that?
16784 Neither did I, we need examples.
16787 (setq nnimap-split-rule
16789 "^Sender: owner-nnimap@@vic20.globalcom.se")
16790 ("INBOX.junk" "^Subject:.*MAKE MONEY")
16791 ("INBOX.private" "")))
16794 This will put all articles from the nnimap mailing list into mailbox
16795 INBOX.nnimap, all articles containing MAKE MONEY in the Subject: line
16796 into INBOX.junk and everything else in INBOX.private.
16798 The first string may contain @samp{\\1} forms, like the ones used by
16799 replace-match to insert sub-expressions from the matched text. For
16803 ("INBOX.lists.\\1" "^Sender: owner-\\([a-z-]+\\)@@")
16806 The first element can also be the symbol @code{junk} to indicate that
16807 matching messages should simply be deleted. Use with care.
16809 The second element can also be a function. In that case, it will be
16810 called with the first element of the rule as the argument, in a buffer
16811 containing the headers of the article. It should return a
16812 non-@code{nil} value if it thinks that the mail belongs in that group.
16814 Nnmail users might recollect that the last regexp had to be empty to
16815 match all articles (like in the example above). This is not required in
16816 nnimap. Articles not matching any of the regexps will not be moved out
16817 of your inbox. (This might affect performance if you keep lots of
16818 unread articles in your inbox, since the splitting code would go over
16819 them every time you fetch new mail.)
16821 These rules are processed from the beginning of the alist toward the
16822 end. The first rule to make a match will ``win'', unless you have
16823 crossposting enabled. In that case, all matching rules will ``win''.
16825 This variable can also have a function as its value, the function will
16826 be called with the headers narrowed and should return a group where it
16827 thinks the article should be split to. See @code{nnimap-split-fancy}.
16829 The splitting code tries to create mailboxes if it needs to.
16831 To allow for different split rules on different virtual servers, and
16832 even different split rules in different inboxes on the same server,
16833 the syntax of this variable have been extended along the lines of:
16836 (setq nnimap-split-rule
16837 '(("my1server" (".*" (("ding" "ding@@gnus.org")
16838 ("junk" "From:.*Simon"))))
16839 ("my2server" ("INBOX" nnimap-split-fancy))
16840 ("my[34]server" (".*" (("private" "To:.*Simon")
16841 ("junk" my-junk-func))))))
16844 The virtual server name is in fact a regexp, so that the same rules
16845 may apply to several servers. In the example, the servers
16846 @code{my3server} and @code{my4server} both use the same rules.
16847 Similarly, the inbox string is also a regexp. The actual splitting
16848 rules are as before, either a function, or a list with group/regexp or
16849 group/function elements.
16851 Nnmail equivalent: @code{nnmail-split-methods}.
16853 @item nnimap-split-predicate
16855 @vindex nnimap-split-predicate
16857 Mail matching this predicate in @code{nnimap-split-inbox} will be
16858 split, it is a string and the default is @samp{UNSEEN UNDELETED}.
16860 This might be useful if you use another @acronym{IMAP} client to read mail in
16861 your inbox but would like Gnus to split all articles in the inbox
16862 regardless of readedness. Then you might change this to
16865 @item nnimap-split-fancy
16866 @cindex splitting, fancy
16867 @findex nnimap-split-fancy
16868 @vindex nnimap-split-fancy
16870 It's possible to set @code{nnimap-split-rule} to
16871 @code{nnmail-split-fancy} if you want to use fancy
16872 splitting. @xref{Fancy Mail Splitting}.
16874 However, to be able to have different fancy split rules for nnmail and
16875 nnimap back ends you can set @code{nnimap-split-rule} to
16876 @code{nnimap-split-fancy} and define the nnimap specific fancy split
16877 rule in @code{nnimap-split-fancy}.
16882 (setq nnimap-split-rule 'nnimap-split-fancy
16883 nnimap-split-fancy ...)
16886 Nnmail equivalent: @code{nnmail-split-fancy}.
16888 @item nnimap-split-download-body
16889 @findex nnimap-split-download-body
16890 @vindex nnimap-split-download-body
16892 Set to non-@code{nil} to download entire articles during splitting.
16893 This is generally not required, and will slow things down
16894 considerably. You may need it if you want to use an advanced
16895 splitting function that analyzes the body to split the article.
16899 @node Expiring in IMAP
16900 @subsection Expiring in IMAP
16901 @cindex expiring imap mail
16903 Even though @code{nnimap} is not a proper @code{nnmail} derived back
16904 end, it supports most features in regular expiring (@pxref{Expiring
16905 Mail}). Unlike splitting in @acronym{IMAP} (@pxref{Splitting in
16906 IMAP}) it does not clone the @code{nnmail} variables (i.e., creating
16907 @var{nnimap-expiry-wait}) but reuse the @code{nnmail} variables. What
16908 follows below are the variables used by the @code{nnimap} expiry
16911 A note on how the expire mark is stored on the @acronym{IMAP} server is
16912 appropriate here as well. The expire mark is translated into a
16913 @code{imap} client specific mark, @code{gnus-expire}, and stored on the
16914 message. This means that likely only Gnus will understand and treat
16915 the @code{gnus-expire} mark properly, although other clients may allow
16916 you to view client specific flags on the message. It also means that
16917 your server must support permanent storage of client specific flags on
16918 messages. Most do, fortunately.
16922 @item nnmail-expiry-wait
16923 @item nnmail-expiry-wait-function
16925 These variables are fully supported. The expire value can be a
16926 number, the symbol @code{immediate} or @code{never}.
16928 @item nnmail-expiry-target
16930 This variable is supported, and internally implemented by calling the
16931 @code{nnmail} functions that handle this. It contains an optimization
16932 that if the destination is a @acronym{IMAP} group on the same server, the
16933 article is copied instead of appended (that is, uploaded again).
16937 @node Editing IMAP ACLs
16938 @subsection Editing IMAP ACLs
16939 @cindex editing imap acls
16940 @cindex Access Control Lists
16941 @cindex Editing @acronym{IMAP} ACLs
16942 @kindex G l (Group)
16943 @findex gnus-group-nnimap-edit-acl
16945 ACL stands for Access Control List. ACLs are used in @acronym{IMAP} for
16946 limiting (or enabling) other users access to your mail boxes. Not all
16947 @acronym{IMAP} servers support this, this function will give an error if it
16950 To edit an ACL for a mailbox, type @kbd{G l}
16951 (@code{gnus-group-edit-nnimap-acl}) and you'll be presented with an ACL
16952 editing window with detailed instructions.
16954 Some possible uses:
16958 Giving ``anyone'' the ``lrs'' rights (lookup, read, keep seen/unseen flags)
16959 on your mailing list mailboxes enables other users on the same server to
16960 follow the list without subscribing to it.
16962 At least with the Cyrus server, you are required to give the user
16963 ``anyone'' posting ("p") capabilities to have ``plussing'' work (that is,
16964 mail sent to user+mailbox@@domain ending up in the @acronym{IMAP} mailbox
16968 @node Expunging mailboxes
16969 @subsection Expunging mailboxes
16973 @cindex manual expunging
16974 @kindex G x (Group)
16975 @findex gnus-group-nnimap-expunge
16977 If you're using the @code{never} setting of @code{nnimap-expunge-on-close},
16978 you may want the option of expunging all deleted articles in a mailbox
16979 manually. This is exactly what @kbd{G x} does.
16981 Currently there is no way of showing deleted articles, you can just
16984 @node A note on namespaces
16985 @subsection A note on namespaces
16986 @cindex IMAP namespace
16989 The @acronym{IMAP} protocol has a concept called namespaces, described
16990 by the following text in the RFC2060:
16993 5.1.2. Mailbox Namespace Naming Convention
16995 By convention, the first hierarchical element of any mailbox name
16996 which begins with "#" identifies the "namespace" of the remainder of
16997 the name. This makes it possible to disambiguate between different
16998 types of mailbox stores, each of which have their own namespaces.
17000 For example, implementations which offer access to USENET
17001 newsgroups MAY use the "#news" namespace to partition the USENET
17002 newsgroup namespace from that of other mailboxes. Thus, the
17003 comp.mail.misc newsgroup would have an mailbox name of
17004 "#news.comp.mail.misc", and the name "comp.mail.misc" could refer
17005 to a different object (e.g. a user's private mailbox).
17008 While there is nothing in this text that warrants concern for the
17009 @acronym{IMAP} implementation in Gnus, some servers use namespace
17010 prefixes in a way that does not work with how Gnus uses mailbox names.
17012 Specifically, University of Washington's @acronym{IMAP} server uses
17013 mailbox names like @code{#driver.mbx/read-mail} which are valid only
17014 in the @sc{create} and @sc{append} commands. After the mailbox is
17015 created (or a messages is appended to a mailbox), it must be accessed
17016 without the namespace prefix, i.e. @code{read-mail}. Since Gnus do
17017 not make it possible for the user to guarantee that user entered
17018 mailbox names will only be used with the CREATE and APPEND commands,
17019 you should simply not use the namespace prefixed mailbox names in
17022 See the UoW IMAPD documentation for the @code{#driver.*/} prefix
17023 for more information on how to use the prefixes. They are a power
17024 tool and should be used only if you are sure what the effects are.
17026 @node Debugging IMAP
17027 @subsection Debugging IMAP
17028 @cindex IMAP debugging
17029 @cindex protocol dump (IMAP)
17031 @acronym{IMAP} is a complex protocol, more so than @acronym{NNTP} or
17032 @acronym{POP3}. Implementation bugs are not unlikely, and we do our
17033 best to fix them right away. If you encounter odd behavior, chances
17034 are that either the server or Gnus is buggy.
17036 If you are familiar with network protocols in general, you will
17037 probably be able to extract some clues from the protocol dump of the
17038 exchanges between Gnus and the server. Even if you are not familiar
17039 with network protocols, when you include the protocol dump in
17040 @acronym{IMAP}-related bug reports you are helping us with data
17041 critical to solving the problem. Therefore, we strongly encourage you
17042 to include the protocol dump when reporting IMAP bugs in Gnus.
17046 Because the protocol dump, when enabled, generates lots of data, it is
17047 disabled by default. You can enable it by setting @code{imap-log} as
17054 This instructs the @code{imap.el} package to log any exchanges with
17055 the server. The log is stored in the buffer @samp{*imap-log*}. Look
17056 for error messages, which sometimes are tagged with the keyword
17057 @code{BAD}---but when submitting a bug, make sure to include all the
17060 @node Other Sources
17061 @section Other Sources
17063 Gnus can do more than just read news or mail. The methods described
17064 below allow Gnus to view directories and files as if they were
17068 * Directory Groups:: You can read a directory as if it was a newsgroup.
17069 * Anything Groups:: Dired? Who needs dired?
17070 * Document Groups:: Single files can be the basis of a group.
17071 * SOUP:: Reading @sc{soup} packets ``offline''.
17072 * Mail-To-News Gateways:: Posting articles via mail-to-news gateways.
17076 @node Directory Groups
17077 @subsection Directory Groups
17079 @cindex directory groups
17081 If you have a directory that has lots of articles in separate files in
17082 it, you might treat it as a newsgroup. The files have to have numerical
17085 This might be an opportune moment to mention @code{ange-ftp} (and its
17086 successor @code{efs}), that most wonderful of all wonderful Emacs
17087 packages. When I wrote @code{nndir}, I didn't think much about it---a
17088 back end to read directories. Big deal.
17090 @code{ange-ftp} changes that picture dramatically. For instance, if you
17091 enter the @code{ange-ftp} file name
17092 @file{/ftp.hpc.uh.edu:/pub/emacs/ding-list/} as the directory name,
17093 @code{ange-ftp} or @code{efs} will actually allow you to read this
17094 directory over at @samp{sina} as a newsgroup. Distributed news ahoy!
17096 @code{nndir} will use @acronym{NOV} files if they are present.
17098 @code{nndir} is a ``read-only'' back end---you can't delete or expire
17099 articles with this method. You can use @code{nnmh} or @code{nnml} for
17100 whatever you use @code{nndir} for, so you could switch to any of those
17101 methods if you feel the need to have a non-read-only @code{nndir}.
17104 @node Anything Groups
17105 @subsection Anything Groups
17108 From the @code{nndir} back end (which reads a single spool-like
17109 directory), it's just a hop and a skip to @code{nneething}, which
17110 pretends that any arbitrary directory is a newsgroup. Strange, but
17113 When @code{nneething} is presented with a directory, it will scan this
17114 directory and assign article numbers to each file. When you enter such
17115 a group, @code{nneething} must create ``headers'' that Gnus can use.
17116 After all, Gnus is a newsreader, in case you're forgetting.
17117 @code{nneething} does this in a two-step process. First, it snoops each
17118 file in question. If the file looks like an article (i.e., the first
17119 few lines look like headers), it will use this as the head. If this is
17120 just some arbitrary file without a head (e.g. a C source file),
17121 @code{nneething} will cobble up a header out of thin air. It will use
17122 file ownership, name and date and do whatever it can with these
17125 All this should happen automatically for you, and you will be presented
17126 with something that looks very much like a newsgroup. Totally like a
17127 newsgroup, to be precise. If you select an article, it will be displayed
17128 in the article buffer, just as usual.
17130 If you select a line that represents a directory, Gnus will pop you into
17131 a new summary buffer for this @code{nneething} group. And so on. You can
17132 traverse the entire disk this way, if you feel like, but remember that
17133 Gnus is not dired, really, and does not intend to be, either.
17135 There are two overall modes to this action---ephemeral or solid. When
17136 doing the ephemeral thing (i.e., @kbd{G D} from the group buffer), Gnus
17137 will not store information on what files you have read, and what files
17138 are new, and so on. If you create a solid @code{nneething} group the
17139 normal way with @kbd{G m}, Gnus will store a mapping table between
17140 article numbers and file names, and you can treat this group like any
17141 other groups. When you activate a solid @code{nneething} group, you will
17142 be told how many unread articles it contains, etc., etc.
17147 @item nneething-map-file-directory
17148 @vindex nneething-map-file-directory
17149 All the mapping files for solid @code{nneething} groups will be stored
17150 in this directory, which defaults to @file{~/.nneething/}.
17152 @item nneething-exclude-files
17153 @vindex nneething-exclude-files
17154 All files that match this regexp will be ignored. Nice to use to exclude
17155 auto-save files and the like, which is what it does by default.
17157 @item nneething-include-files
17158 @vindex nneething-include-files
17159 Regexp saying what files to include in the group. If this variable is
17160 non-@code{nil}, only files matching this regexp will be included.
17162 @item nneething-map-file
17163 @vindex nneething-map-file
17164 Name of the map files.
17168 @node Document Groups
17169 @subsection Document Groups
17171 @cindex documentation group
17174 @code{nndoc} is a cute little thing that will let you read a single file
17175 as a newsgroup. Several files types are supported:
17181 The Babyl (Rmail) mail box.
17186 The standard Unix mbox file.
17188 @cindex MMDF mail box
17190 The MMDF mail box format.
17193 Several news articles appended into a file.
17195 @cindex rnews batch files
17197 The rnews batch transport format.
17200 Netscape mail boxes.
17203 @acronym{MIME} multipart messages.
17205 @item standard-digest
17206 The standard (RFC 1153) digest format.
17209 A @acronym{MIME} digest of messages.
17211 @item lanl-gov-announce
17212 Announcement messages from LANL Gov Announce.
17214 @cindex forwarded messages
17215 @item rfc822-forward
17216 A message forwarded according to RFC822.
17219 The Outlook mail box.
17222 The Outlook Express dbx mail box.
17225 A bounce message from the Exim MTA.
17228 A message forwarded according to informal rules.
17231 An RFC934-forwarded message.
17237 A digest of Clarinet brief news items.
17240 Non-standard digest format---matches most things, but does it badly.
17246 You can also use the special ``file type'' @code{guess}, which means
17247 that @code{nndoc} will try to guess what file type it is looking at.
17248 @code{digest} means that @code{nndoc} should guess what digest type the
17251 @code{nndoc} will not try to change the file or insert any extra headers into
17252 it---it will simply, like, let you use the file as the basis for a
17253 group. And that's it.
17255 If you have some old archived articles that you want to insert into your
17256 new & spiffy Gnus mail back end, @code{nndoc} can probably help you with
17257 that. Say you have an old @file{RMAIL} file with mail that you now want
17258 to split into your new @code{nnml} groups. You look at that file using
17259 @code{nndoc} (using the @kbd{G f} command in the group buffer
17260 (@pxref{Foreign Groups})), set the process mark on all the articles in
17261 the buffer (@kbd{M P b}, for instance), and then re-spool (@kbd{B r})
17262 using @code{nnml}. If all goes well, all the mail in the @file{RMAIL}
17263 file is now also stored in lots of @code{nnml} directories, and you can
17264 delete that pesky @file{RMAIL} file. If you have the guts!
17266 Virtual server variables:
17269 @item nndoc-article-type
17270 @vindex nndoc-article-type
17271 This should be one of @code{mbox}, @code{babyl}, @code{digest},
17272 @code{news}, @code{rnews}, @code{mmdf}, @code{forward}, @code{rfc934},
17273 @code{rfc822-forward}, @code{mime-parts}, @code{standard-digest},
17274 @code{slack-digest}, @code{clari-briefs}, @code{nsmail}, @code{outlook},
17275 @code{oe-dbx}, @code{mailman}, and @code{mail-in-mail} or @code{guess}.
17277 @item nndoc-post-type
17278 @vindex nndoc-post-type
17279 This variable says whether Gnus is to consider the group a news group or
17280 a mail group. There are two valid values: @code{mail} (the default)
17285 * Document Server Internals:: How to add your own document types.
17289 @node Document Server Internals
17290 @subsubsection Document Server Internals
17292 Adding new document types to be recognized by @code{nndoc} isn't
17293 difficult. You just have to whip up a definition of what the document
17294 looks like, write a predicate function to recognize that document type,
17295 and then hook into @code{nndoc}.
17297 First, here's an example document type definition:
17301 (article-begin . "^\^A\^A\^A\^A\n")
17302 (body-end . "^\^A\^A\^A\^A\n"))
17305 The definition is simply a unique @dfn{name} followed by a series of
17306 regexp pseudo-variable settings. Below are the possible
17307 variables---don't be daunted by the number of variables; most document
17308 types can be defined with very few settings:
17311 @item first-article
17312 If present, @code{nndoc} will skip past all text until it finds
17313 something that match this regexp. All text before this will be
17316 @item article-begin
17317 This setting has to be present in all document type definitions. It
17318 says what the beginning of each article looks like. To do more
17319 complicated things that cannot be dealt with a simple regexp, you can
17320 use @code{article-begin-function} instead of this.
17322 @item article-begin-function
17323 If present, this should be a function that moves point to the beginning
17324 of each article. This setting overrides @code{article-begin}.
17327 If present, this should be a regexp that matches the head of the
17328 article. To do more complicated things that cannot be dealt with a
17329 simple regexp, you can use @code{head-begin-function} instead of this.
17331 @item head-begin-function
17332 If present, this should be a function that moves point to the head of
17333 the article. This setting overrides @code{head-begin}.
17336 This should match the end of the head of the article. It defaults to
17337 @samp{^$}---the empty line.
17340 This should match the beginning of the body of the article. It defaults
17341 to @samp{^\n}. To do more complicated things that cannot be dealt with
17342 a simple regexp, you can use @code{body-begin-function} instead of this.
17344 @item body-begin-function
17345 If present, this function should move point to the beginning of the body
17346 of the article. This setting overrides @code{body-begin}.
17349 If present, this should match the end of the body of the article. To do
17350 more complicated things that cannot be dealt with a simple regexp, you
17351 can use @code{body-end-function} instead of this.
17353 @item body-end-function
17354 If present, this function should move point to the end of the body of
17355 the article. This setting overrides @code{body-end}.
17358 If present, this should match the beginning of the file. All text
17359 before this regexp will be totally ignored.
17362 If present, this should match the end of the file. All text after this
17363 regexp will be totally ignored.
17367 So, using these variables @code{nndoc} is able to dissect a document
17368 file into a series of articles, each with a head and a body. However, a
17369 few more variables are needed since not all document types are all that
17370 news-like---variables needed to transform the head or the body into
17371 something that's palatable for Gnus:
17374 @item prepare-body-function
17375 If present, this function will be called when requesting an article. It
17376 will be called with point at the start of the body, and is useful if the
17377 document has encoded some parts of its contents.
17379 @item article-transform-function
17380 If present, this function is called when requesting an article. It's
17381 meant to be used for more wide-ranging transformation of both head and
17382 body of the article.
17384 @item generate-head-function
17385 If present, this function is called to generate a head that Gnus can
17386 understand. It is called with the article number as a parameter, and is
17387 expected to generate a nice head for the article in question. It is
17388 called when requesting the headers of all articles.
17390 @item generate-article-function
17391 If present, this function is called to generate an entire article that
17392 Gnus can understand. It is called with the article number as a
17393 parameter when requesting all articles.
17395 @item dissection-function
17396 If present, this function is called to dissect a document by itself,
17397 overriding @code{first-article}, @code{article-begin},
17398 @code{article-begin-function}, @code{head-begin},
17399 @code{head-begin-function}, @code{head-end}, @code{body-begin},
17400 @code{body-begin-function}, @code{body-end}, @code{body-end-function},
17401 @code{file-begin}, and @code{file-end}.
17405 Let's look at the most complicated example I can come up with---standard
17410 (first-article . ,(concat "^" (make-string 70 ?-) "\n\n+"))
17411 (article-begin . ,(concat "\n\n" (make-string 30 ?-) "\n\n+"))
17412 (prepare-body-function . nndoc-unquote-dashes)
17413 (body-end-function . nndoc-digest-body-end)
17414 (head-end . "^ ?$")
17415 (body-begin . "^ ?\n")
17416 (file-end . "^End of .*digest.*[0-9].*\n\\*\\*\\|^End of.*Digest *$")
17417 (subtype digest guess))
17420 We see that all text before a 70-width line of dashes is ignored; all
17421 text after a line that starts with that @samp{^End of} is also ignored;
17422 each article begins with a 30-width line of dashes; the line separating
17423 the head from the body may contain a single space; and that the body is
17424 run through @code{nndoc-unquote-dashes} before being delivered.
17426 To hook your own document definition into @code{nndoc}, use the
17427 @code{nndoc-add-type} function. It takes two parameters---the first
17428 is the definition itself and the second (optional) parameter says
17429 where in the document type definition alist to put this definition.
17430 The alist is traversed sequentially, and
17431 @code{nndoc-@var{type}-type-p} is called for a given type @var{type}.
17432 So @code{nndoc-mmdf-type-p} is called to see whether a document is of
17433 @code{mmdf} type, and so on. These type predicates should return
17434 @code{nil} if the document is not of the correct type; @code{t} if it
17435 is of the correct type; and a number if the document might be of the
17436 correct type. A high number means high probability; a low number
17437 means low probability with @samp{0} being the lowest valid number.
17445 In the PC world people often talk about ``offline'' newsreaders. These
17446 are thingies that are combined reader/news transport monstrosities.
17447 With built-in modem programs. Yecchh!
17449 Of course, us Unix Weenie types of human beans use things like
17450 @code{uucp} and, like, @code{nntpd} and set up proper news and mail
17451 transport things like Ghod intended. And then we just use normal
17454 However, it can sometimes be convenient to do something that's a bit
17455 easier on the brain if you have a very slow modem, and you're not really
17456 that interested in doing things properly.
17458 A file format called @sc{soup} has been developed for transporting news
17459 and mail from servers to home machines and back again. It can be a bit
17462 First some terminology:
17467 This is the machine that is connected to the outside world and where you
17468 get news and/or mail from.
17471 This is the machine that you want to do the actual reading and responding
17472 on. It is typically not connected to the rest of the world in any way.
17475 Something that contains messages and/or commands. There are two kinds
17479 @item message packets
17480 These are packets made at the server, and typically contain lots of
17481 messages for you to read. These are called @file{SoupoutX.tgz} by
17482 default, where @var{x} is a number.
17484 @item response packets
17485 These are packets made at the home machine, and typically contains
17486 replies that you've written. These are called @file{SoupinX.tgz} by
17487 default, where @var{x} is a number.
17497 You log in on the server and create a @sc{soup} packet. You can either
17498 use a dedicated @sc{soup} thingie (like the @code{awk} program), or you
17499 can use Gnus to create the packet with its @sc{soup} commands (@kbd{O
17500 s} and/or @kbd{G s b}; and then @kbd{G s p}) (@pxref{SOUP Commands}).
17503 You transfer the packet home. Rail, boat, car or modem will do fine.
17506 You put the packet in your home directory.
17509 You fire up Gnus on your home machine using the @code{nnsoup} back end as
17510 the native or secondary server.
17513 You read articles and mail and answer and followup to the things you
17514 want (@pxref{SOUP Replies}).
17517 You do the @kbd{G s r} command to pack these replies into a @sc{soup}
17521 You transfer this packet to the server.
17524 You use Gnus to mail this packet out with the @kbd{G s s} command.
17527 You then repeat until you die.
17531 So you basically have a bipartite system---you use @code{nnsoup} for
17532 reading and Gnus for packing/sending these @sc{soup} packets.
17535 * SOUP Commands:: Commands for creating and sending @sc{soup} packets
17536 * SOUP Groups:: A back end for reading @sc{soup} packets.
17537 * SOUP Replies:: How to enable @code{nnsoup} to take over mail and news.
17541 @node SOUP Commands
17542 @subsubsection SOUP Commands
17544 These are commands for creating and manipulating @sc{soup} packets.
17548 @kindex G s b (Group)
17549 @findex gnus-group-brew-soup
17550 Pack all unread articles in the current group
17551 (@code{gnus-group-brew-soup}). This command understands the
17552 process/prefix convention.
17555 @kindex G s w (Group)
17556 @findex gnus-soup-save-areas
17557 Save all @sc{soup} data files (@code{gnus-soup-save-areas}).
17560 @kindex G s s (Group)
17561 @findex gnus-soup-send-replies
17562 Send all replies from the replies packet
17563 (@code{gnus-soup-send-replies}).
17566 @kindex G s p (Group)
17567 @findex gnus-soup-pack-packet
17568 Pack all files into a @sc{soup} packet (@code{gnus-soup-pack-packet}).
17571 @kindex G s r (Group)
17572 @findex nnsoup-pack-replies
17573 Pack all replies into a replies packet (@code{nnsoup-pack-replies}).
17576 @kindex O s (Summary)
17577 @findex gnus-soup-add-article
17578 This summary-mode command adds the current article to a @sc{soup} packet
17579 (@code{gnus-soup-add-article}). It understands the process/prefix
17580 convention (@pxref{Process/Prefix}).
17585 There are a few variables to customize where Gnus will put all these
17590 @item gnus-soup-directory
17591 @vindex gnus-soup-directory
17592 Directory where Gnus will save intermediate files while composing
17593 @sc{soup} packets. The default is @file{~/SoupBrew/}.
17595 @item gnus-soup-replies-directory
17596 @vindex gnus-soup-replies-directory
17597 This is what Gnus will use as a temporary directory while sending our
17598 reply packets. @file{~/SoupBrew/SoupReplies/} is the default.
17600 @item gnus-soup-prefix-file
17601 @vindex gnus-soup-prefix-file
17602 Name of the file where Gnus stores the last used prefix. The default is
17603 @samp{gnus-prefix}.
17605 @item gnus-soup-packer
17606 @vindex gnus-soup-packer
17607 A format string command for packing a @sc{soup} packet. The default is
17608 @samp{tar cf - %s | gzip > $HOME/Soupout%d.tgz}.
17610 @item gnus-soup-unpacker
17611 @vindex gnus-soup-unpacker
17612 Format string command for unpacking a @sc{soup} packet. The default is
17613 @samp{gunzip -c %s | tar xvf -}.
17615 @item gnus-soup-packet-directory
17616 @vindex gnus-soup-packet-directory
17617 Where Gnus will look for reply packets. The default is @file{~/}.
17619 @item gnus-soup-packet-regexp
17620 @vindex gnus-soup-packet-regexp
17621 Regular expression matching @sc{soup} reply packets in
17622 @code{gnus-soup-packet-directory}.
17628 @subsubsection SOUP Groups
17631 @code{nnsoup} is the back end for reading @sc{soup} packets. It will
17632 read incoming packets, unpack them, and put them in a directory where
17633 you can read them at leisure.
17635 These are the variables you can use to customize its behavior:
17639 @item nnsoup-tmp-directory
17640 @vindex nnsoup-tmp-directory
17641 When @code{nnsoup} unpacks a @sc{soup} packet, it does it in this
17642 directory. (@file{/tmp/} by default.)
17644 @item nnsoup-directory
17645 @vindex nnsoup-directory
17646 @code{nnsoup} then moves each message and index file to this directory.
17647 The default is @file{~/SOUP/}.
17649 @item nnsoup-replies-directory
17650 @vindex nnsoup-replies-directory
17651 All replies will be stored in this directory before being packed into a
17652 reply packet. The default is @file{~/SOUP/replies/}.
17654 @item nnsoup-replies-format-type
17655 @vindex nnsoup-replies-format-type
17656 The @sc{soup} format of the replies packets. The default is @samp{?n}
17657 (rnews), and I don't think you should touch that variable. I probably
17658 shouldn't even have documented it. Drats! Too late!
17660 @item nnsoup-replies-index-type
17661 @vindex nnsoup-replies-index-type
17662 The index type of the replies packet. The default is @samp{?n}, which
17663 means ``none''. Don't fiddle with this one either!
17665 @item nnsoup-active-file
17666 @vindex nnsoup-active-file
17667 Where @code{nnsoup} stores lots of information. This is not an ``active
17668 file'' in the @code{nntp} sense; it's an Emacs Lisp file. If you lose
17669 this file or mess it up in any way, you're dead. The default is
17670 @file{~/SOUP/active}.
17672 @item nnsoup-packer
17673 @vindex nnsoup-packer
17674 Format string command for packing a reply @sc{soup} packet. The default
17675 is @samp{tar cf - %s | gzip > $HOME/Soupin%d.tgz}.
17677 @item nnsoup-unpacker
17678 @vindex nnsoup-unpacker
17679 Format string command for unpacking incoming @sc{soup} packets. The
17680 default is @samp{gunzip -c %s | tar xvf -}.
17682 @item nnsoup-packet-directory
17683 @vindex nnsoup-packet-directory
17684 Where @code{nnsoup} will look for incoming packets. The default is
17687 @item nnsoup-packet-regexp
17688 @vindex nnsoup-packet-regexp
17689 Regular expression matching incoming @sc{soup} packets. The default is
17692 @item nnsoup-always-save
17693 @vindex nnsoup-always-save
17694 If non-@code{nil}, save the replies buffer after each posted message.
17700 @subsubsection SOUP Replies
17702 Just using @code{nnsoup} won't mean that your postings and mailings end
17703 up in @sc{soup} reply packets automagically. You have to work a bit
17704 more for that to happen.
17706 @findex nnsoup-set-variables
17707 The @code{nnsoup-set-variables} command will set the appropriate
17708 variables to ensure that all your followups and replies end up in the
17711 In specific, this is what it does:
17714 (setq message-send-news-function 'nnsoup-request-post)
17715 (setq message-send-mail-function 'nnsoup-request-mail)
17718 And that's it, really. If you only want news to go into the @sc{soup}
17719 system you just use the first line. If you only want mail to be
17720 @sc{soup}ed you use the second.
17723 @node Mail-To-News Gateways
17724 @subsection Mail-To-News Gateways
17725 @cindex mail-to-news gateways
17728 If your local @code{nntp} server doesn't allow posting, for some reason
17729 or other, you can post using one of the numerous mail-to-news gateways.
17730 The @code{nngateway} back end provides the interface.
17732 Note that you can't read anything from this back end---it can only be
17738 @item nngateway-address
17739 @vindex nngateway-address
17740 This is the address of the mail-to-news gateway.
17742 @item nngateway-header-transformation
17743 @vindex nngateway-header-transformation
17744 News headers often have to be transformed in some odd way or other
17745 for the mail-to-news gateway to accept it. This variable says what
17746 transformation should be called, and defaults to
17747 @code{nngateway-simple-header-transformation}. The function is called
17748 narrowed to the headers to be transformed and with one parameter---the
17751 This default function just inserts a new @code{To} header based on the
17752 @code{Newsgroups} header and the gateway address.
17753 For instance, an article with this @code{Newsgroups} header:
17756 Newsgroups: alt.religion.emacs
17759 will get this @code{To} header inserted:
17762 To: alt-religion-emacs@@GATEWAY
17765 The following pre-defined functions exist:
17767 @findex nngateway-simple-header-transformation
17770 @item nngateway-simple-header-transformation
17771 Creates a @code{To} header that looks like
17772 @var{newsgroup}@@@code{nngateway-address}.
17774 @findex nngateway-mail2news-header-transformation
17776 @item nngateway-mail2news-header-transformation
17777 Creates a @code{To} header that looks like
17778 @code{nngateway-address}.
17786 (setq gnus-post-method
17788 "mail2news@@replay.com"
17789 (nngateway-header-transformation
17790 nngateway-mail2news-header-transformation)))
17793 So, to use this, simply say something like:
17796 (setq gnus-post-method '(nngateway "GATEWAY.ADDRESS"))
17801 @node Combined Groups
17802 @section Combined Groups
17804 Gnus allows combining a mixture of all the other group types into bigger
17808 * Virtual Groups:: Combining articles from many groups.
17809 * Kibozed Groups:: Looking through parts of the newsfeed for articles.
17813 @node Virtual Groups
17814 @subsection Virtual Groups
17816 @cindex virtual groups
17817 @cindex merging groups
17819 An @dfn{nnvirtual group} is really nothing more than a collection of
17822 For instance, if you are tired of reading many small groups, you can
17823 put them all in one big group, and then grow tired of reading one
17824 big, unwieldy group. The joys of computing!
17826 You specify @code{nnvirtual} as the method. The address should be a
17827 regexp to match component groups.
17829 All marks in the virtual group will stick to the articles in the
17830 component groups. So if you tick an article in a virtual group, the
17831 article will also be ticked in the component group from whence it
17832 came. (And vice versa---marks from the component groups will also be
17833 shown in the virtual group.). To create an empty virtual group, run
17834 @kbd{G V} (@code{gnus-group-make-empty-virtual}) in the group buffer
17835 and edit the method regexp with @kbd{M-e}
17836 (@code{gnus-group-edit-group-method})
17838 Here's an example @code{nnvirtual} method that collects all Andrea Dworkin
17839 newsgroups into one, big, happy newsgroup:
17842 (nnvirtual "^alt\\.fan\\.andrea-dworkin$\\|^rec\\.dworkin.*")
17845 The component groups can be native or foreign; everything should work
17846 smoothly, but if your computer explodes, it was probably my fault.
17848 Collecting the same group from several servers might actually be a good
17849 idea if users have set the Distribution header to limit distribution.
17850 If you would like to read @samp{soc.motss} both from a server in Japan
17851 and a server in Norway, you could use the following as the group regexp:
17854 "^nntp\\+server\\.jp:soc\\.motss$\\|^nntp\\+server\\.no:soc\\.motss$"
17857 (Remember, though, that if you're creating the group with @kbd{G m}, you
17858 shouldn't double the backslashes, and you should leave off the quote
17859 characters at the beginning and the end of the string.)
17861 This should work kinda smoothly---all articles from both groups should
17862 end up in this one, and there should be no duplicates. Threading (and
17863 the rest) will still work as usual, but there might be problems with the
17864 sequence of articles. Sorting on date might be an option here
17865 (@pxref{Selecting a Group}).
17867 One limitation, however---all groups included in a virtual
17868 group have to be alive (i.e., subscribed or unsubscribed). Killed or
17869 zombie groups can't be component groups for @code{nnvirtual} groups.
17871 @vindex nnvirtual-always-rescan
17872 If the @code{nnvirtual-always-rescan} variable is non-@code{nil} (which
17873 is the default), @code{nnvirtual} will always scan groups for unread
17874 articles when entering a virtual group. If this variable is @code{nil}
17875 and you read articles in a component group after the virtual group has
17876 been activated, the read articles from the component group will show up
17877 when you enter the virtual group. You'll also see this effect if you
17878 have two virtual groups that have a component group in common. If
17879 that's the case, you should set this variable to @code{t}. Or you can
17880 just tap @code{M-g} on the virtual group every time before you enter
17881 it---it'll have much the same effect.
17883 @code{nnvirtual} can have both mail and news groups as component groups.
17884 When responding to articles in @code{nnvirtual} groups, @code{nnvirtual}
17885 has to ask the back end of the component group the article comes from
17886 whether it is a news or mail back end. However, when you do a @kbd{^},
17887 there is typically no sure way for the component back end to know this,
17888 and in that case @code{nnvirtual} tells Gnus that the article came from a
17889 not-news back end. (Just to be on the safe side.)
17891 @kbd{C-c C-n} in the message buffer will insert the @code{Newsgroups}
17892 line from the article you respond to in these cases.
17894 @code{nnvirtual} groups do not inherit anything but articles and marks
17895 from component groups---group parameters, for instance, are not
17899 @node Kibozed Groups
17900 @subsection Kibozed Groups
17904 @dfn{Kibozing} is defined by the @acronym{OED} as ``grepping through
17905 (parts of) the news feed''. @code{nnkiboze} is a back end that will
17906 do this for you. Oh joy! Now you can grind any @acronym{NNTP} server
17907 down to a halt with useless requests! Oh happiness!
17909 @kindex G k (Group)
17910 To create a kibozed group, use the @kbd{G k} command in the group
17913 The address field of the @code{nnkiboze} method is, as with
17914 @code{nnvirtual}, a regexp to match groups to be ``included'' in the
17915 @code{nnkiboze} group. That's where most similarities between
17916 @code{nnkiboze} and @code{nnvirtual} end.
17918 In addition to this regexp detailing component groups, an
17919 @code{nnkiboze} group must have a score file to say what articles are
17920 to be included in the group (@pxref{Scoring}).
17922 @kindex M-x nnkiboze-generate-groups
17923 @findex nnkiboze-generate-groups
17924 You must run @kbd{M-x nnkiboze-generate-groups} after creating the
17925 @code{nnkiboze} groups you want to have. This command will take time.
17926 Lots of time. Oodles and oodles of time. Gnus has to fetch the
17927 headers from all the articles in all the component groups and run them
17928 through the scoring process to determine if there are any articles in
17929 the groups that are to be part of the @code{nnkiboze} groups.
17931 Please limit the number of component groups by using restrictive
17932 regexps. Otherwise your sysadmin may become annoyed with you, and the
17933 @acronym{NNTP} site may throw you off and never let you back in again.
17934 Stranger things have happened.
17936 @code{nnkiboze} component groups do not have to be alive---they can be dead,
17937 and they can be foreign. No restrictions.
17939 @vindex nnkiboze-directory
17940 The generation of an @code{nnkiboze} group means writing two files in
17941 @code{nnkiboze-directory}, which is @file{~/News/kiboze/} by default.
17942 One contains the @acronym{NOV} header lines for all the articles in
17943 the group, and the other is an additional @file{.newsrc} file to store
17944 information on what groups have been searched through to find
17945 component articles.
17947 Articles marked as read in the @code{nnkiboze} group will have
17948 their @acronym{NOV} lines removed from the @acronym{NOV} file.
17951 @node Email Based Diary
17952 @section Email Based Diary
17954 @cindex email based diary
17957 This section describes a special mail back end called @code{nndiary},
17958 and its companion library @code{gnus-diary}. It is ``special'' in the
17959 sense that it is not meant to be one of the standard alternatives for
17960 reading mail with Gnus. See @ref{Choosing a Mail Back End} for that.
17961 Instead, it is used to treat @emph{some} of your mails in a special way,
17962 namely, as event reminders.
17964 Here is a typical scenario:
17968 You've got a date with Andy Mc Dowell or Bruce Willis (select according
17969 to your sexual preference) in one month. You don't want to forget it.
17971 So you send a ``reminder'' message (actually, a diary one) to yourself.
17973 You forget all about it and keep on getting and reading new mail, as usual.
17975 From time to time, as you type `g' in the group buffer and as the date
17976 is getting closer, the message will pop up again to remind you of your
17977 appointment, just as if it were new and unread.
17979 Read your ``new'' messages, this one included, and start dreaming again
17980 of the night you're gonna have.
17982 Once the date is over (you actually fell asleep just after dinner), the
17983 message will be automatically deleted if it is marked as expirable.
17986 The Gnus Diary back end has the ability to handle regular appointments
17987 (that wouldn't ever be deleted) as well as punctual ones, operates as a
17988 real mail back end and is configurable in many ways. All of this is
17989 explained in the sections below.
17992 * The NNDiary Back End:: Basic setup and usage.
17993 * The Gnus Diary Library:: Utility toolkit on top of nndiary.
17994 * Sending or Not Sending:: A final note on sending diary messages.
17998 @node The NNDiary Back End
17999 @subsection The NNDiary Back End
18001 @cindex the nndiary back end
18003 @code{nndiary} is a back end very similar to @code{nnml} (@pxref{Mail
18004 Spool}). Actually, it could appear as a mix of @code{nnml} and
18005 @code{nndraft}. If you know @code{nnml}, you're already familiar with
18006 the message storing scheme of @code{nndiary}: one file per message, one
18007 directory per group.
18009 Before anything, there is one requirement to be able to run
18010 @code{nndiary} properly: you @emph{must} use the group timestamp feature
18011 of Gnus. This adds a timestamp to each group's parameters. @ref{Group
18012 Timestamp} to see how it's done.
18015 * Diary Messages:: What makes a message valid for nndiary.
18016 * Running NNDiary:: NNDiary has two modes of operation.
18017 * Customizing NNDiary:: Bells and whistles.
18020 @node Diary Messages
18021 @subsubsection Diary Messages
18022 @cindex nndiary messages
18023 @cindex nndiary mails
18025 @code{nndiary} messages are just normal ones, except for the mandatory
18026 presence of 7 special headers. These headers are of the form
18027 @code{X-Diary-<something>}, @code{<something>} being one of
18028 @code{Minute}, @code{Hour}, @code{Dom}, @code{Month}, @code{Year},
18029 @code{Time-Zone} and @code{Dow}. @code{Dom} means ``Day of Month'', and
18030 @code{dow} means ``Day of Week''. These headers actually behave like
18031 crontab specifications and define the event date(s):
18035 For all headers except the @code{Time-Zone} one, a header value is
18036 either a star (meaning all possible values), or a list of fields
18037 (separated by a comma).
18039 A field is either an integer, or a range.
18041 A range is two integers separated by a dash.
18043 Possible integer values are 0--59 for @code{Minute}, 0--23 for
18044 @code{Hour}, 1--31 for @code{Dom}, 1--12 for @code{Month}, above 1971
18045 for @code{Year} and 0--6 for @code{Dow} (0 meaning Sunday).
18047 As a special case, a star in either @code{Dom} or @code{Dow} doesn't
18048 mean ``all possible values'', but ``use only the other field''. Note
18049 that if both are star'ed, the use of either one gives the same result.
18051 The @code{Time-Zone} header is special in that it can only have one
18052 value (@code{GMT}, for instance). A star doesn't mean ``all possible
18053 values'' (because it makes no sense), but ``the current local time
18054 zone''. Most of the time, you'll be using a star here. However, for a
18055 list of available time zone values, see the variable
18056 @code{nndiary-headers}.
18059 As a concrete example, here are the diary headers to add to your message
18060 for specifying ``Each Monday and each 1st of month, at 12:00, 20:00,
18061 21:00, 22:00, 23:00 and 24:00, from 1999 to 2010'' (I'll let you find
18066 X-Diary-Hour: 12, 20-24
18069 X-Diary-Year: 1999-2010
18071 X-Diary-Time-Zone: *
18074 @node Running NNDiary
18075 @subsubsection Running NNDiary
18076 @cindex running nndiary
18077 @cindex nndiary operation modes
18079 @code{nndiary} has two modes of operation: ``traditional'' (the default)
18080 and ``autonomous''. In traditional mode, @code{nndiary} does not get new
18081 mail by itself. You have to move (@kbd{B m}) or copy (@kbd{B c}) mails
18082 from your primary mail back end to nndiary groups in order to handle them
18083 as diary messages. In autonomous mode, @code{nndiary} retrieves its own
18084 mail and handles it independently from your primary mail back end.
18086 One should note that Gnus is not inherently designed to allow several
18087 ``master'' mail back ends at the same time. However, this does make
18088 sense with @code{nndiary}: you really want to send and receive diary
18089 messages to your diary groups directly. So, @code{nndiary} supports
18090 being sort of a ``second primary mail back end'' (to my knowledge, it is
18091 the only back end offering this feature). However, there is a limitation
18092 (which I hope to fix some day): respooling doesn't work in autonomous
18095 In order to use @code{nndiary} in autonomous mode, you have several
18100 Allow @code{nndiary} to retrieve new mail by itself. Put the following
18101 line in your @file{gnusrc} file:
18104 (setq nndiary-get-new-mail t)
18107 You must arrange for diary messages (those containing @code{X-Diary-*}
18108 headers) to be split in a private folder @emph{before} Gnus treat them.
18109 Again, this is needed because Gnus cannot (yet ?) properly handle
18110 multiple primary mail back ends. Getting those messages from a separate
18111 source will compensate this misfeature to some extent.
18113 As an example, here's my procmailrc entry to store diary files in
18114 @file{~/.nndiary} (the default @code{nndiary} mail source file):
18123 Once this is done, you might want to customize the following two options
18124 that affect the diary mail retrieval and splitting processes:
18126 @defvar nndiary-mail-sources
18127 This is the diary-specific replacement for the standard
18128 @code{mail-sources} variable. It obeys the same syntax, and defaults to
18129 @code{(file :path "~/.nndiary")}.
18132 @defvar nndiary-split-methods
18133 This is the diary-specific replacement for the standard
18134 @code{nnmail-split-methods} variable. It obeys the same syntax.
18137 Finally, you may add a permanent @code{nndiary} virtual server
18138 (something like @code{(nndiary "diary")} should do) to your
18139 @code{gnus-secondary-select-methods}.
18141 Hopefully, almost everything (see the TODO section in
18142 @file{nndiary.el}) will work as expected when you restart Gnus: in
18143 autonomous mode, typing @kbd{g} and @kbd{M-g} in the group buffer, will
18144 also get your new diary mails and split them according to your
18145 diary-specific rules, @kbd{F} will find your new diary groups etc.
18147 @node Customizing NNDiary
18148 @subsubsection Customizing NNDiary
18149 @cindex customizing nndiary
18150 @cindex nndiary customization
18152 Now that @code{nndiary} is up and running, it's time to customize it.
18153 The custom group is called @code{nndiary} (no, really ?!). You should
18154 browse it to figure out which options you'd like to tweak. The following
18155 two variables are probably the only ones you will want to change:
18157 @defvar nndiary-reminders
18158 This is the list of times when you want to be reminded of your
18159 appointements (e.g. 3 weeks before, then 2 days before, then 1 hour
18160 before and that's it). Remember that ``being reminded'' means that the
18161 diary message will pop up as brand new and unread again when you get new
18165 @defvar nndiary-week-starts-on-monday
18166 Rather self-explanatory. Otherwise, Sunday is assumed (this is the
18171 @node The Gnus Diary Library
18172 @subsection The Gnus Diary Library
18174 @cindex the gnus diary library
18176 Using @code{nndiary} manually (I mean, writing the headers by hand and
18177 so on) would be rather boring. Fortunately, there is a library called
18178 @code{gnus-diary} written on top of @code{nndiary}, that does many
18179 useful things for you.
18181 In order to use it, add the following line to your @file{gnusrc} file:
18184 (require 'gnus-diary)
18187 Also, you shouldn't use any @code{gnus-user-format-function-[d|D]}
18188 (@pxref{Summary Buffer Lines}). @code{gnus-diary} provides both of these
18189 (sorry if you used them before).
18193 * Diary Summary Line Format:: A nicer summary buffer line format.
18194 * Diary Articles Sorting:: A nicer way to sort messages.
18195 * Diary Headers Generation:: Not doing it manually.
18196 * Diary Group Parameters:: Not handling them manually.
18199 @node Diary Summary Line Format
18200 @subsubsection Diary Summary Line Format
18201 @cindex diary summary buffer line
18202 @cindex diary summary line format
18204 Displaying diary messages in standard summary line format (usually
18205 something like @samp{From Joe: Subject}) is pretty useless. Most of
18206 the time, you're the one who wrote the message, and you mostly want to
18207 see the event's date.
18209 @code{gnus-diary} provides two supplemental user formats to be used in
18210 summary line formats. @code{D} corresponds to a formatted time string
18211 for the next occurrence of the event (e.g. ``Sat, Sep 22 01, 12:00''),
18212 while @code{d} corresponds to an approximative remaining time until the
18213 next occurrence of the event (e.g. ``in 6 months, 1 week'').
18215 For example, here's how Joe's birthday is displayed in my
18216 @code{nndiary+diary:birthdays} summary buffer (note that the message is
18217 expirable, but will never be deleted, as it specifies a periodic event):
18220 E Sat, Sep 22 01, 12:00: Joe's birthday (in 6 months, 1 week)
18223 In order to get something like the above, you would normally add the
18224 following line to your diary groups'parameters:
18227 (gnus-summary-line-format "%U%R%z %uD: %(%s%) (%ud)\n")
18230 However, @code{gnus-diary} does it automatically (@pxref{Diary Group
18231 Parameters}). You can however customize the provided summary line format
18232 with the following user options:
18234 @defvar gnus-diary-summary-line-format
18235 Defines the summary line format used for diary groups (@pxref{Summary
18236 Buffer Lines}). @code{gnus-diary} uses it to automatically update the
18237 diary groups'parameters.
18240 @defvar gnus-diary-time-format
18241 Defines the format to display dates in diary summary buffers. This is
18242 used by the @code{D} user format. See the docstring for details.
18245 @defvar gnus-diary-delay-format-function
18246 Defines the format function to use for displaying delays (remaining
18247 times) in diary summary buffers. This is used by the @code{d} user
18248 format. There are currently built-in functions for English and French;
18249 you can also define your own. See the docstring for details.
18252 @node Diary Articles Sorting
18253 @subsubsection Diary Articles Sorting
18254 @cindex diary articles sorting
18255 @cindex diary summary lines sorting
18256 @findex gnus-summary-sort-by-schedule
18257 @findex gnus-thread-sort-by-schedule
18258 @findex gnus-article-sort-by-schedule
18260 @code{gnus-diary} provides new sorting functions (@pxref{Sorting the
18261 Summary Buffer} ) called @code{gnus-summary-sort-by-schedule},
18262 @code{gnus-thread-sort-by-schedule} and
18263 @code{gnus-article-sort-by-schedule}. These functions let you organize
18264 your diary summary buffers from the closest event to the farthest one.
18266 @code{gnus-diary} automatically installs
18267 @code{gnus-summary-sort-by-schedule} as a menu item in the summary
18268 buffer's ``sort'' menu, and the two others as the primary (hence
18269 default) sorting functions in the group parameters (@pxref{Diary Group
18272 @node Diary Headers Generation
18273 @subsubsection Diary Headers Generation
18274 @cindex diary headers generation
18275 @findex gnus-diary-check-message
18277 @code{gnus-diary} provides a function called
18278 @code{gnus-diary-check-message} to help you handle the @code{X-Diary-*}
18279 headers. This function ensures that the current message contains all the
18280 required diary headers, and prompts you for values or corrections if
18283 This function is hooked into the @code{nndiary} back end, so that
18284 moving or copying an article to a diary group will trigger it
18285 automatically. It is also bound to @kbd{C-c D c} in @code{message-mode}
18286 and @code{article-edit-mode} in order to ease the process of converting
18287 a usual mail to a diary one.
18289 This function takes a prefix argument which will force prompting of
18290 all diary headers, regardless of their presence or validity. That way,
18291 you can very easily reschedule an already valid diary message, for
18294 @node Diary Group Parameters
18295 @subsubsection Diary Group Parameters
18296 @cindex diary group parameters
18298 When you create a new diary group, or visit one, @code{gnus-diary}
18299 automatically checks your group parameters and if needed, sets the
18300 summary line format to the diary-specific value, installs the
18301 diary-specific sorting functions, and also adds the different
18302 @code{X-Diary-*} headers to the group's posting-style. It is then easier
18303 to send a diary message, because if you use @kbd{C-u a} or @kbd{C-u m}
18304 on a diary group to prepare a message, these headers will be inserted
18305 automatically (although not filled with proper values yet).
18307 @node Sending or Not Sending
18308 @subsection Sending or Not Sending
18310 Well, assuming you've read of of the above, here are two final notes on
18311 mail sending with @code{nndiary}:
18315 @code{nndiary} is a @emph{real} mail back end. You really send real diary
18316 messsages for real. This means for instance that you can give
18317 appointements to anybody (provided they use Gnus and @code{nndiary}) by
18318 sending the diary message to them as well.
18320 However, since @code{nndiary} also has a @code{request-post} method, you
18321 can also use @kbd{C-u a} instead of @kbd{C-u m} on a diary group and the
18322 message won't actually be sent; just stored locally in the group. This
18323 comes in very handy for private appointments.
18326 @node Gnus Unplugged
18327 @section Gnus Unplugged
18332 @cindex Gnus unplugged
18334 In olden times (ca. February '88), people used to run their newsreaders
18335 on big machines with permanent connections to the net. News transport
18336 was dealt with by news servers, and all the newsreaders had to do was to
18337 read news. Believe it or not.
18339 Nowadays most people read news and mail at home, and use some sort of
18340 modem to connect to the net. To avoid running up huge phone bills, it
18341 would be nice to have a way to slurp down all the news and mail, hang up
18342 the phone, read for several hours, and then upload any responses you
18343 have to make. And then you repeat the procedure.
18345 Of course, you can use news servers for doing this as well. I've used
18346 @code{inn} together with @code{slurp}, @code{pop} and @code{sendmail}
18347 for some years, but doing that's a bore. Moving the news server
18348 functionality up to the newsreader makes sense if you're the only person
18349 reading news on a machine.
18351 Setting up Gnus as an ``offline'' newsreader is quite simple. In
18352 fact, you don't have to configure anything as the agent is now enabled
18353 by default (@pxref{Agent Variables, gnus-agent}).
18355 Of course, to use it as such, you have to learn a few new commands.
18358 * Agent Basics:: How it all is supposed to work.
18359 * Agent Categories:: How to tell the Gnus Agent what to download.
18360 * Agent Commands:: New commands for all the buffers.
18361 * Agent Visuals:: Ways that the agent may effect your summary buffer.
18362 * Agent as Cache:: The Agent is a big cache too.
18363 * Agent Expiry:: How to make old articles go away.
18364 * Agent Regeneration:: How to recover from lost connections and other accidents.
18365 * Agent and flags:: How the Agent maintains flags.
18366 * Agent and IMAP:: How to use the Agent with @acronym{IMAP}.
18367 * Outgoing Messages:: What happens when you post/mail something?
18368 * Agent Variables:: Customizing is fun.
18369 * Example Setup:: An example @file{~/.gnus.el} file for offline people.
18370 * Batching Agents:: How to fetch news from a @code{cron} job.
18371 * Agent Caveats:: What you think it'll do and what it does.
18376 @subsection Agent Basics
18378 First, let's get some terminology out of the way.
18380 The Gnus Agent is said to be @dfn{unplugged} when you have severed the
18381 connection to the net (and notified the Agent that this is the case).
18382 When the connection to the net is up again (and Gnus knows this), the
18383 Agent is @dfn{plugged}.
18385 The @dfn{local} machine is the one you're running on, and which isn't
18386 connected to the net continuously.
18388 @dfn{Downloading} means fetching things from the net to your local
18389 machine. @dfn{Uploading} is doing the opposite.
18391 You know that Gnus gives you all the opportunity you'd ever want for
18392 shooting yourself in the foot. Some people call it flexibility. Gnus
18393 is also customizable to a great extent, which means that the user has a
18394 say on how Gnus behaves. Other newsreaders might unconditionally shoot
18395 you in your foot, but with Gnus, you have a choice!
18397 Gnus is never really in plugged or unplugged state. Rather, it applies
18398 that state to each server individually. This means that some servers
18399 can be plugged while others can be unplugged. Additionally, some
18400 servers can be ignored by the Agent altogether (which means that
18401 they're kinda like plugged always).
18403 So when you unplug the Agent and then wonder why is Gnus opening a
18404 connection to the Net, the next step to do is to look whether all
18405 servers are agentized. If there is an unagentized server, you found
18408 Another thing is the @dfn{offline} state. Sometimes, servers aren't
18409 reachable. When Gnus notices this, it asks you whether you want the
18410 server to be switched to offline state. If you say yes, then the
18411 server will behave somewhat as if it was unplugged, except that Gnus
18412 will ask you whether you want to switch it back online again.
18414 Let's take a typical Gnus session using the Agent.
18419 @findex gnus-unplugged
18420 You start Gnus with @code{gnus-unplugged}. This brings up the Gnus
18421 Agent in a disconnected state. You can read all the news that you have
18422 already fetched while in this mode.
18425 You then decide to see whether any new news has arrived. You connect
18426 your machine to the net (using PPP or whatever), and then hit @kbd{J j}
18427 to make Gnus become @dfn{plugged} and use @kbd{g} to check for new mail
18428 as usual. To check for new mail in unplugged mode (@pxref{Mail
18429 Source Specifiers}).
18432 You can then read the new news immediately, or you can download the
18433 news onto your local machine. If you want to do the latter, you press
18434 @kbd{g} to check if there are any new news and then @kbd{J s} to fetch
18435 all the eligible articles in all the groups. (To let Gnus know which
18436 articles you want to download, @pxref{Agent Categories}).
18439 After fetching the articles, you press @kbd{J j} to make Gnus become
18440 unplugged again, and you shut down the PPP thing (or whatever). And
18441 then you read the news offline.
18444 And then you go to step 2.
18447 Here are some things you should do the first time (or so) that you use
18453 Decide which servers should be covered by the Agent. If you have a mail
18454 back end, it would probably be nonsensical to have it covered by the
18455 Agent. Go to the server buffer (@kbd{^} in the group buffer) and press
18456 @kbd{J a} on the server (or servers) that you wish to have covered by the
18457 Agent (@pxref{Server Agent Commands}), or @kbd{J r} on automatically
18458 added servers you do not wish to have covered by the Agent. By default,
18459 all @code{nntp} and @code{nnimap} servers in @code{gnus-select-method} and
18460 @code{gnus-secondary-select-methods} are agentized.
18463 Decide on download policy. It's fairly simple once you decide whether
18464 you are going to use agent categories, topic parameters, and/or group
18465 parameters to implement your policy. If you're new to gnus, it
18466 is probably best to start with a category, @xref{Agent Categories}.
18468 Both topic parameters (@pxref{Topic Parameters}) and agent categories
18469 (@pxref{Agent Categories}) provide for setting a policy that applies
18470 to multiple groups. Which you use is entirely up to you. Topic
18471 parameters do override categories so, if you mix the two, you'll have
18472 to take that into account. If you have a few groups that deviate from
18473 your policy, you can use group parameters (@pxref{Group Parameters}) to
18477 Uhm@dots{} that's it.
18481 @node Agent Categories
18482 @subsection Agent Categories
18484 One of the main reasons to integrate the news transport layer into the
18485 newsreader is to allow greater control over what articles to download.
18486 There's not much point in downloading huge amounts of articles, just to
18487 find out that you're not interested in reading any of them. It's better
18488 to be somewhat more conservative in choosing what to download, and then
18489 mark the articles for downloading manually if it should turn out that
18490 you're interested in the articles anyway.
18492 One of the more effective methods for controlling what is to be
18493 downloaded is to create a @dfn{category} and then assign some (or all)
18494 groups to this category. Groups that do not belong in any other
18495 category belong to the @code{default} category. Gnus has its own
18496 buffer for creating and managing categories.
18498 If you prefer, you can also use group parameters (@pxref{Group
18499 Parameters}) and topic parameters (@pxref{Topic Parameters}) for an
18500 alternative approach to controlling the agent. The only real
18501 difference is that categories are specific to the agent (so there is
18502 less to learn) while group and topic parameters include the kitchen
18505 Since you can set agent parameters in several different places we have
18506 a rule to decide which source to believe. This rule specifies that
18507 the parameter sources are checked in the following order: group
18508 parameters, topic parameters, agent category, and finally customizable
18509 variables. So you can mix all of these sources to produce a wide range
18510 of behavior, just don't blame me if you don't remember where you put
18514 * Category Syntax:: What a category looks like.
18515 * Category Buffer:: A buffer for maintaining categories.
18516 * Category Variables:: Customize'r'Us.
18520 @node Category Syntax
18521 @subsubsection Category Syntax
18523 A category consists of a name, the list of groups belonging to the
18524 category, and a number of optional parameters that override the
18525 customizable variables. The complete list of agent parameters are
18528 @cindex Agent Parameters
18531 The list of groups that are in this category.
18533 @item agent-predicate
18534 A predicate which (generally) gives a rough outline of which articles
18535 are eligible for downloading; and
18538 a score rule which (generally) gives you a finer granularity when
18539 deciding what articles to download. (Note that this @dfn{download
18540 score} is not necessarily related to normal scores.)
18542 @item agent-enable-expiration
18543 a boolean indicating whether the agent should expire old articles in
18544 this group. Most groups should be expired to conserve disk space. In
18545 fact, its probably safe to say that the gnus.* hierarchy contains the
18546 only groups that should not be expired.
18548 @item agent-days-until-old
18549 an integer indicating the number of days that the agent should wait
18550 before deciding that a read article is safe to expire.
18552 @item agent-low-score
18553 an integer that overrides the value of @code{gnus-agent-low-score}.
18555 @item agent-high-score
18556 an integer that overrides the value of @code{gnus-agent-high-score}.
18558 @item agent-short-article
18559 an integer that overrides the value of
18560 @code{gnus-agent-short-article}.
18562 @item agent-long-article
18563 an integer that overrides the value of @code{gnus-agent-long-article}.
18565 @item agent-enable-undownloaded-faces
18566 a symbol indicating whether the summary buffer should display
18567 undownloaded articles using the @code{gnus-summary-*-undownloaded-face}
18568 faces. Any symbol other than @code{nil} will enable the use of
18569 undownloaded faces.
18572 The name of a category can not be changed once the category has been
18575 Each category maintains a list of groups that are exclusive members of
18576 that category. The exclusivity rule is automatically enforced, add a
18577 group to a new category and it is automatically removed from its old
18580 A predicate in its simplest form can be a single predicate such as
18581 @code{true} or @code{false}. These two will download every available
18582 article or nothing respectively. In the case of these two special
18583 predicates an additional score rule is superfluous.
18585 Predicates of @code{high} or @code{low} download articles in respect of
18586 their scores in relationship to @code{gnus-agent-high-score} and
18587 @code{gnus-agent-low-score} as described below.
18589 To gain even finer control of what is to be regarded eligible for
18590 download a predicate can consist of a number of predicates with logical
18591 operators sprinkled in between.
18593 Perhaps some examples are in order.
18595 Here's a simple predicate. (It's the default predicate, in fact, used
18596 for all groups that don't belong to any other category.)
18602 Quite simple, eh? This predicate is true if and only if the article is
18603 short (for some value of ``short'').
18605 Here's a more complex predicate:
18614 This means that an article should be downloaded if it has a high score,
18615 or if the score is not low and the article is not long. You get the
18618 The available logical operators are @code{or}, @code{and} and
18619 @code{not}. (If you prefer, you can use the more ``C''-ish operators
18620 @samp{|}, @code{&} and @code{!} instead.)
18622 The following predicates are pre-defined, but if none of these fit what
18623 you want to do, you can write your own.
18625 When evaluating each of these predicates, the named constant will be
18626 bound to the value determined by calling
18627 @code{gnus-agent-find-parameter} on the appropriate parameter. For
18628 example, gnus-agent-short-article will be bound to
18629 @code{(gnus-agent-find-parameter group 'agent-short-article)}. This
18630 means that you can specify a predicate in your category then tune that
18631 predicate to individual groups.
18635 True iff the article is shorter than @code{gnus-agent-short-article}
18636 lines; default 100.
18639 True iff the article is longer than @code{gnus-agent-long-article}
18640 lines; default 200.
18643 True iff the article has a download score less than
18644 @code{gnus-agent-low-score}; default 0.
18647 True iff the article has a download score greater than
18648 @code{gnus-agent-high-score}; default 0.
18651 True iff the Gnus Agent guesses that the article is spam. The
18652 heuristics may change over time, but at present it just computes a
18653 checksum and sees whether articles match.
18662 If you want to create your own predicate function, here's what you have
18663 to know: The functions are called with no parameters, but the
18664 @code{gnus-headers} and @code{gnus-score} dynamic variables are bound to
18667 For example, you could decide that you don't want to download articles
18668 that were posted more than a certain number of days ago (e.g. posted
18669 more than @code{gnus-agent-expire-days} ago) you might write a function
18670 something along the lines of the following:
18673 (defun my-article-old-p ()
18674 "Say whether an article is old."
18675 (< (time-to-days (date-to-time (mail-header-date gnus-headers)))
18676 (- (time-to-days (current-time)) gnus-agent-expire-days)))
18679 with the predicate then defined as:
18682 (not my-article-old-p)
18685 or you could append your predicate to the predefined
18686 @code{gnus-category-predicate-alist} in your @file{~/.gnus.el} or
18690 (require 'gnus-agent)
18691 (setq gnus-category-predicate-alist
18692 (append gnus-category-predicate-alist
18693 '((old . my-article-old-p))))
18696 and simply specify your predicate as:
18702 If/when using something like the above, be aware that there are many
18703 misconfigured systems/mailers out there and so an article's date is not
18704 always a reliable indication of when it was posted. Hell, some people
18705 just don't give a damn.
18707 The above predicates apply to @emph{all} the groups which belong to the
18708 category. However, if you wish to have a specific predicate for an
18709 individual group within a category, or you're just too lazy to set up a
18710 new category, you can enter a group's individual predicate in its group
18711 parameters like so:
18714 (agent-predicate . short)
18717 This is the group/topic parameter equivalent of the agent category default.
18718 Note that when specifying a single word predicate like this, the
18719 @code{agent-predicate} specification must be in dotted pair notation.
18721 The equivalent of the longer example from above would be:
18724 (agent-predicate or high (and (not low) (not long)))
18727 The outer parenthesis required in the category specification are not
18728 entered here as, not being in dotted pair notation, the value of the
18729 predicate is assumed to be a list.
18732 Now, the syntax of the download score is the same as the syntax of
18733 normal score files, except that all elements that require actually
18734 seeing the article itself are verboten. This means that only the
18735 following headers can be scored on: @code{Subject}, @code{From},
18736 @code{Date}, @code{Message-ID}, @code{References}, @code{Chars},
18737 @code{Lines}, and @code{Xref}.
18739 As with predicates, the specification of the @code{download score rule}
18740 to use in respect of a group can be in either the category definition if
18741 it's to be applicable to all groups in therein, or a group's parameters
18742 if it's to be specific to that group.
18744 In both of these places the @code{download score rule} can take one of
18751 This has the same syntax as a normal Gnus score file except only a
18752 subset of scoring keywords are available as mentioned above.
18758 Category specification
18762 ("Lars Ingebrigtsen" 1000000 nil s))
18768 Group/Topic Parameter specification
18771 (agent-score ("from"
18772 ("Lars Ingebrigtsen" 1000000 nil s))
18777 Again, note the omission of the outermost parenthesis here.
18783 These score files must @emph{only} contain the permitted scoring
18784 keywords stated above.
18790 Category specification
18793 ("~/News/agent.SCORE")
18799 ("~/News/agent.SCORE" "~/News/agent.group.SCORE")
18803 Group Parameter specification
18806 (agent-score "~/News/agent.SCORE")
18809 Additional score files can be specified as above. Need I say anything
18814 Use @code{normal} score files
18816 If you don't want to maintain two sets of scoring rules for a group, and
18817 your desired @code{downloading} criteria for a group are the same as your
18818 @code{reading} criteria then you can tell the agent to refer to your
18819 @code{normal} score files when deciding what to download.
18821 These directives in either the category definition or a group's
18822 parameters will cause the agent to read in all the applicable score
18823 files for a group, @emph{filtering out} those sections that do not
18824 relate to one of the permitted subset of scoring keywords.
18828 Category Specification
18835 Group Parameter specification
18838 (agent-score . file)
18843 @node Category Buffer
18844 @subsubsection Category Buffer
18846 You'd normally do all category maintenance from the category buffer.
18847 When you enter it for the first time (with the @kbd{J c} command from
18848 the group buffer), you'll only see the @code{default} category.
18850 The following commands are available in this buffer:
18854 @kindex q (Category)
18855 @findex gnus-category-exit
18856 Return to the group buffer (@code{gnus-category-exit}).
18859 @kindex e (Category)
18860 @findex gnus-category-customize-category
18861 Use a customization buffer to set all of the selected category's
18862 parameters at one time (@code{gnus-category-customize-category}).
18865 @kindex k (Category)
18866 @findex gnus-category-kill
18867 Kill the current category (@code{gnus-category-kill}).
18870 @kindex c (Category)
18871 @findex gnus-category-copy
18872 Copy the current category (@code{gnus-category-copy}).
18875 @kindex a (Category)
18876 @findex gnus-category-add
18877 Add a new category (@code{gnus-category-add}).
18880 @kindex p (Category)
18881 @findex gnus-category-edit-predicate
18882 Edit the predicate of the current category
18883 (@code{gnus-category-edit-predicate}).
18886 @kindex g (Category)
18887 @findex gnus-category-edit-groups
18888 Edit the list of groups belonging to the current category
18889 (@code{gnus-category-edit-groups}).
18892 @kindex s (Category)
18893 @findex gnus-category-edit-score
18894 Edit the download score rule of the current category
18895 (@code{gnus-category-edit-score}).
18898 @kindex l (Category)
18899 @findex gnus-category-list
18900 List all the categories (@code{gnus-category-list}).
18904 @node Category Variables
18905 @subsubsection Category Variables
18908 @item gnus-category-mode-hook
18909 @vindex gnus-category-mode-hook
18910 Hook run in category buffers.
18912 @item gnus-category-line-format
18913 @vindex gnus-category-line-format
18914 Format of the lines in the category buffer (@pxref{Formatting
18915 Variables}). Valid elements are:
18919 The name of the category.
18922 The number of groups in the category.
18925 @item gnus-category-mode-line-format
18926 @vindex gnus-category-mode-line-format
18927 Format of the category mode line (@pxref{Mode Line Formatting}).
18929 @item gnus-agent-short-article
18930 @vindex gnus-agent-short-article
18931 Articles that have fewer lines than this are short. Default 100.
18933 @item gnus-agent-long-article
18934 @vindex gnus-agent-long-article
18935 Articles that have more lines than this are long. Default 200.
18937 @item gnus-agent-low-score
18938 @vindex gnus-agent-low-score
18939 Articles that have a score lower than this have a low score. Default
18942 @item gnus-agent-high-score
18943 @vindex gnus-agent-high-score
18944 Articles that have a score higher than this have a high score. Default
18947 @item gnus-agent-expire-days
18948 @vindex gnus-agent-expire-days
18949 The number of days that a @samp{read} article must stay in the agent's
18950 local disk before becoming eligible for expiration (While the name is
18951 the same, this doesn't mean expiring the article on the server. It
18952 just means deleting the local copy of the article). What is also
18953 important to understand is that the counter starts with the time the
18954 article was written to the local disk and not the time the article was
18958 @item gnus-agent-enable-expiration
18959 @vindex gnus-agent-enable-expiration
18960 Determines whether articles in a group are, by default, expired or
18961 retained indefinitely. The default is @code{ENABLE} which means that
18962 you'll have to disable expiration when desired. On the other hand,
18963 you could set this to @code{DISABLE}. In that case, you would then
18964 have to enable expiration in selected groups.
18969 @node Agent Commands
18970 @subsection Agent Commands
18971 @findex gnus-agent-toggle-plugged
18972 @kindex J j (Agent)
18974 All the Gnus Agent commands are on the @kbd{J} submap. The @kbd{J j}
18975 (@code{gnus-agent-toggle-plugged}) command works in all modes, and
18976 toggles the plugged/unplugged state of the Gnus Agent.
18980 * Group Agent Commands:: Configure groups and fetch their contents.
18981 * Summary Agent Commands:: Manually select then fetch specific articles.
18982 * Server Agent Commands:: Select the servers that are supported by the agent.
18988 @node Group Agent Commands
18989 @subsubsection Group Agent Commands
18993 @kindex J u (Agent Group)
18994 @findex gnus-agent-fetch-groups
18995 Fetch all eligible articles in the current group
18996 (@code{gnus-agent-fetch-groups}).
18999 @kindex J c (Agent Group)
19000 @findex gnus-enter-category-buffer
19001 Enter the Agent category buffer (@code{gnus-enter-category-buffer}).
19004 @kindex J s (Agent Group)
19005 @findex gnus-agent-fetch-session
19006 Fetch all eligible articles in all groups
19007 (@code{gnus-agent-fetch-session}).
19010 @kindex J S (Agent Group)
19011 @findex gnus-group-send-queue
19012 Send all sendable messages in the queue group
19013 (@code{gnus-group-send-queue}). @xref{Drafts}.
19016 @kindex J a (Agent Group)
19017 @findex gnus-agent-add-group
19018 Add the current group to an Agent category
19019 (@code{gnus-agent-add-group}). This command understands the
19020 process/prefix convention (@pxref{Process/Prefix}).
19023 @kindex J r (Agent Group)
19024 @findex gnus-agent-remove-group
19025 Remove the current group from its category, if any
19026 (@code{gnus-agent-remove-group}). This command understands the
19027 process/prefix convention (@pxref{Process/Prefix}).
19030 @kindex J Y (Agent Group)
19031 @findex gnus-agent-synchronize-flags
19032 Synchronize flags changed while unplugged with remote server, if any.
19038 @node Summary Agent Commands
19039 @subsubsection Summary Agent Commands
19043 @kindex J # (Agent Summary)
19044 @findex gnus-agent-mark-article
19045 Mark the article for downloading (@code{gnus-agent-mark-article}).
19048 @kindex J M-# (Agent Summary)
19049 @findex gnus-agent-unmark-article
19050 Remove the downloading mark from the article
19051 (@code{gnus-agent-unmark-article}).
19055 @kindex @@ (Agent Summary)
19056 @findex gnus-agent-toggle-mark
19057 Toggle whether to download the article
19058 (@code{gnus-agent-toggle-mark}). The download mark is @samp{%} by
19062 @kindex J c (Agent Summary)
19063 @findex gnus-agent-catchup
19064 Mark all articles as read (@code{gnus-agent-catchup}) that are neither cached, downloaded, nor downloadable.
19067 @kindex J S (Agent Summary)
19068 @findex gnus-agent-fetch-group
19069 Download all eligible (@pxref{Agent Categories}) articles in this group.
19070 (@code{gnus-agent-fetch-group}).
19073 @kindex J s (Agent Summary)
19074 @findex gnus-agent-summary-fetch-series
19075 Download all processable articles in this group.
19076 (@code{gnus-agent-summary-fetch-series}).
19079 @kindex J u (Agent Summary)
19080 @findex gnus-agent-summary-fetch-group
19081 Download all downloadable articles in the current group
19082 (@code{gnus-agent-summary-fetch-group}).
19087 @node Server Agent Commands
19088 @subsubsection Server Agent Commands
19092 @kindex J a (Agent Server)
19093 @findex gnus-agent-add-server
19094 Add the current server to the list of servers covered by the Gnus Agent
19095 (@code{gnus-agent-add-server}).
19098 @kindex J r (Agent Server)
19099 @findex gnus-agent-remove-server
19100 Remove the current server from the list of servers covered by the Gnus
19101 Agent (@code{gnus-agent-remove-server}).
19106 @node Agent Visuals
19107 @subsection Agent Visuals
19109 If you open a summary while unplugged and, Gnus knows from the group's
19110 active range that there are more articles than the headers currently
19111 stored in the Agent, you may see some articles whose subject looks
19112 something like @samp{[Undownloaded article #####]}. These are
19113 placeholders for the missing headers. Aside from setting a mark,
19114 there is not much that can be done with one of these placeholders.
19115 When Gnus finally gets a chance to fetch the group's headers, the
19116 placeholders will automatically be replaced by the actual headers.
19117 You can configure the summary buffer's maneuvering to skip over the
19118 placeholders if you care (See @code{gnus-auto-goto-ignores}).
19120 While it may be obvious to all, the only headers and articles
19121 available while unplugged are those headers and articles that were
19122 fetched into the Agent while previously plugged. To put it another
19123 way, ``If you forget to fetch something while plugged, you might have a
19124 less than satisfying unplugged session''. For this reason, the Agent
19125 adds two visual effects to your summary buffer. These effects display
19126 the download status of each article so that you always know which
19127 articles will be available when unplugged.
19129 The first visual effect is the @samp{%O} spec. If you customize
19130 @code{gnus-summary-line-format} to include this specifier, you will add
19131 a single character field that indicates an article's download status.
19132 Articles that have been fetched into either the Agent or the Cache,
19133 will display @code{gnus-downloaded-mark} (defaults to @samp{+}). All
19134 other articles will display @code{gnus-undownloaded-mark} (defaults to
19135 @samp{-}). If you open a group that has not been agentized, a space
19136 (@samp{ }) will be displayed.
19138 The second visual effect are the undownloaded faces. The faces, there
19139 are three indicating the article's score (low, normal, high), seem to
19140 result in a love/hate response from many Gnus users. The problem is
19141 that the face selection is controlled by a list of condition tests and
19142 face names (See @code{gnus-summary-highlight}). Each condition is
19143 tested in the order in which it appears in the list so early
19144 conditions have precedence over later conditions. All of this means
19145 that, if you tick an undownloaded article, the article will continue
19146 to be displayed in the undownloaded face rather than the ticked face.
19148 If you use the Agent as a cache (to avoid downloading the same article
19149 each time you visit it or to minimize your connection time), the
19150 undownloaded face will probably seem like a good idea. The reason
19151 being that you do all of our work (marking, reading, deleting) with
19152 downloaded articles so the normal faces always appear. For those
19153 users using the agent to improve online performance by caching the NOV
19154 database (most users since 5.10.2), the undownloaded faces may appear
19155 to be an absolutely horrible idea. The issue being that, since none
19156 of their articles have been fetched into the Agent, all of the
19157 normal faces will be obscured by the undownloaded faces.
19159 If you would like to use the undownloaded faces, you must enable the
19160 undownloaded faces by setting the @code{agent-enable-undownloaded-faces}
19161 group parameter to @code{t}. This parameter, like all other agent
19162 parameters, may be set on an Agent Category (@pxref{Agent Categories}),
19163 a Group Topic (@pxref{Topic Parameters}), or an individual group
19164 (@pxref{Group Parameters}).
19166 The one problem common to all users using the agent is how quickly it
19167 can consume disk space. If you using the agent on many groups, it is
19168 even more difficult to effectively recover disk space. One solution
19169 is the @samp{%F} format available in @code{gnus-group-line-format}.
19170 This format will display the actual disk space used by articles
19171 fetched into both the agent and cache. By knowing which groups use
19172 the most space, users know where to focus their efforts when ``agent
19173 expiring'' articles.
19175 @node Agent as Cache
19176 @subsection Agent as Cache
19178 When Gnus is plugged, it is not efficient to download headers or
19179 articles from the server again, if they are already stored in the
19180 Agent. So, Gnus normally only downloads headers once, and stores them
19181 in the Agent. These headers are later used when generating the summary
19182 buffer, regardless of whether you are plugged or unplugged. Articles
19183 are not cached in the Agent by default though (that would potentially
19184 consume lots of disk space), but if you have already downloaded an
19185 article into the Agent, Gnus will not download the article from the
19186 server again but use the locally stored copy instead.
19188 If you so desire, you can configure the agent (see @code{gnus-agent-cache}
19189 @pxref{Agent Variables}) to always download headers and articles while
19190 plugged. Gnus will almost certainly be slower, but it will be kept
19191 synchronized with the server. That last point probably won't make any
19192 sense if you are using a nntp or nnimap back end.
19195 @subsection Agent Expiry
19197 @vindex gnus-agent-expire-days
19198 @findex gnus-agent-expire
19199 @kindex M-x gnus-agent-expire
19200 @kindex M-x gnus-agent-expire-group
19201 @findex gnus-agent-expire-group
19202 @cindex agent expiry
19203 @cindex Gnus agent expiry
19206 The Agent back end, @code{nnagent}, doesn't handle expiry. Well, at
19207 least it doesn't handle it like other back ends. Instead, there are
19208 special @code{gnus-agent-expire} and @code{gnus-agent-expire-group}
19209 commands that will expire all read articles that are older than
19210 @code{gnus-agent-expire-days} days. They can be run whenever you feel
19211 that you're running out of space. Neither are particularly fast or
19212 efficient, and it's not a particularly good idea to interrupt them (with
19213 @kbd{C-g} or anything else) once you've started one of them.
19215 Note that other functions, e.g. @code{gnus-request-expire-articles},
19216 might run @code{gnus-agent-expire} for you to keep the agent
19217 synchronized with the group.
19219 The agent parameter @code{agent-enable-expiration} may be used to
19220 prevent expiration in selected groups.
19222 @vindex gnus-agent-expire-all
19223 If @code{gnus-agent-expire-all} is non-@code{nil}, the agent
19224 expiration commands will expire all articles---unread, read, ticked
19225 and dormant. If @code{nil} (which is the default), only read articles
19226 are eligible for expiry, and unread, ticked and dormant articles will
19227 be kept indefinitely.
19229 If you find that some articles eligible for expiry are never expired,
19230 perhaps some Gnus Agent files are corrupted. There's are special
19231 commands, @code{gnus-agent-regenerate} and
19232 @code{gnus-agent-regenerate-group}, to fix possible problems.
19234 @node Agent Regeneration
19235 @subsection Agent Regeneration
19237 @cindex agent regeneration
19238 @cindex Gnus agent regeneration
19239 @cindex regeneration
19241 The local data structures used by @code{nnagent} may become corrupted
19242 due to certain exceptional conditions. When this happens,
19243 @code{nnagent} functionality may degrade or even fail. The solution
19244 to this problem is to repair the local data structures by removing all
19245 internal inconsistencies.
19247 For example, if your connection to your server is lost while
19248 downloaded articles into the agent, the local data structures will not
19249 know about articles successfully downloaded prior to the connection
19250 failure. Running @code{gnus-agent-regenerate} or
19251 @code{gnus-agent-regenerate-group} will update the data structures
19252 such that you don't need to download these articles a second time.
19254 @findex gnus-agent-regenerate
19255 @kindex M-x gnus-agent-regenerate
19256 The command @code{gnus-agent-regenerate} will perform
19257 @code{gnus-agent-regenerate-group} on every agentized group. While
19258 you can run @code{gnus-agent-regenerate} in any buffer, it is strongly
19259 recommended that you first close all summary buffers.
19261 @findex gnus-agent-regenerate-group
19262 @kindex M-x gnus-agent-regenerate-group
19263 The command @code{gnus-agent-regenerate-group} uses the local copies
19264 of individual articles to repair the local @acronym{NOV}(header) database. It
19265 then updates the internal data structures that document which articles
19266 are stored locally. An optional argument will mark articles in the
19269 @node Agent and flags
19270 @subsection Agent and flags
19272 The Agent works with any Gnus back end including those, such as
19273 nnimap, that store flags (read, ticked, etc) on the server. Sadly,
19274 the Agent does not actually know which backends keep their flags in
19275 the backend server rather than in @file{.newsrc}. This means that the
19276 Agent, while unplugged or disconnected, will always record all changes
19277 to the flags in its own files.
19279 When you plug back in, Gnus will then check to see if you have any
19280 changed any flags and ask if you wish to synchronize these with the
19281 server. This behavior is customizable by @code{gnus-agent-synchronize-flags}.
19283 @vindex gnus-agent-synchronize-flags
19284 If @code{gnus-agent-synchronize-flags} is @code{nil}, the Agent will
19285 never automatically synchronize flags. If it is @code{ask}, which is
19286 the default, the Agent will check if you made any changes and if so
19287 ask if you wish to synchronize these when you re-connect. If it has
19288 any other value, all flags will be synchronized automatically.
19290 If you do not wish to synchronize flags automatically when you
19291 re-connect, you can do it manually with the
19292 @code{gnus-agent-synchronize-flags} command that is bound to @kbd{J Y}
19293 in the group buffer.
19295 Technical note: the synchronization algorithm does not work by ``pushing''
19296 all local flags to the server, but rather by incrementally updated the
19297 server view of flags by changing only those flags that were changed by
19298 the user. Thus, if you set one flag on an article, quit the group then
19299 re-select the group and remove the flag; the flag will be set and
19300 removed from the server when you ``synchronize''. The queued flag
19301 operations can be found in the per-server @code{flags} file in the Agent
19302 directory. It's emptied when you synchronize flags.
19304 @node Agent and IMAP
19305 @subsection Agent and IMAP
19307 The Agent works with any Gnus back end, including nnimap. However,
19308 since there are some conceptual differences between @acronym{NNTP} and
19309 @acronym{IMAP}, this section (should) provide you with some information to
19310 make Gnus Agent work smoother as a @acronym{IMAP} Disconnected Mode client.
19312 Some things are currently not implemented in the Agent that you'd might
19313 expect from a disconnected @acronym{IMAP} client, including:
19318 Copying/moving articles into nnimap groups when unplugged.
19321 Creating/deleting nnimap groups when unplugged.
19325 @node Outgoing Messages
19326 @subsection Outgoing Messages
19328 By default, when Gnus is unplugged, all outgoing messages (both mail
19329 and news) are stored in the draft group ``queue'' (@pxref{Drafts}).
19330 You can view them there after posting, and edit them at will.
19332 You can control the circumstances under which outgoing mail is queued
19333 (see @code{gnus-agent-queue-mail}, @pxref{Agent Variables}). Outgoing
19334 news is always queued when Gnus is unplugged, and never otherwise.
19336 You can send the messages either from the draft group with the special
19337 commands available there, or you can use the @kbd{J S} command in the
19338 group buffer to send all the sendable messages in the draft group.
19339 Posting news will only work when Gnus is plugged, but you can send
19342 If sending mail while unplugged does not work for you and you worry
19343 about hitting @kbd{J S} by accident when unplugged, you can have Gnus
19344 ask you to confirm your action (see
19345 @code{gnus-agent-prompt-send-queue}, @pxref{Agent Variables}).
19347 @node Agent Variables
19348 @subsection Agent Variables
19353 Is the agent enabled? The default is @code{t}. When first enabled,
19354 the agent will use @code{gnus-agent-auto-agentize-methods} to
19355 automatically mark some back ends as agentized. You may change which
19356 back ends are agentized using the agent commands in the server buffer.
19358 To enter the server buffer, use the @kbd{^}
19359 (@code{gnus-group-enter-server-mode}) command in the group buffer.
19362 @item gnus-agent-directory
19363 @vindex gnus-agent-directory
19364 Where the Gnus Agent will store its files. The default is
19365 @file{~/News/agent/}.
19367 @item gnus-agent-handle-level
19368 @vindex gnus-agent-handle-level
19369 Groups on levels (@pxref{Group Levels}) higher than this variable will
19370 be ignored by the Agent. The default is @code{gnus-level-subscribed},
19371 which means that only subscribed group will be considered by the Agent
19374 @item gnus-agent-plugged-hook
19375 @vindex gnus-agent-plugged-hook
19376 Hook run when connecting to the network.
19378 @item gnus-agent-unplugged-hook
19379 @vindex gnus-agent-unplugged-hook
19380 Hook run when disconnecting from the network.
19382 @item gnus-agent-fetched-hook
19383 @vindex gnus-agent-fetched-hook
19384 Hook run when finished fetching articles.
19386 @item gnus-agent-cache
19387 @vindex gnus-agent-cache
19388 Variable to control whether use the locally stored @acronym{NOV} and
19389 articles when plugged, e.g. essentially using the Agent as a cache.
19390 The default is non-@code{nil}, which means to use the Agent as a cache.
19392 @item gnus-agent-go-online
19393 @vindex gnus-agent-go-online
19394 If @code{gnus-agent-go-online} is @code{nil}, the Agent will never
19395 automatically switch offline servers into online status. If it is
19396 @code{ask}, the default, the Agent will ask if you wish to switch
19397 offline servers into online status when you re-connect. If it has any
19398 other value, all offline servers will be automatically switched into
19401 @item gnus-agent-mark-unread-after-downloaded
19402 @vindex gnus-agent-mark-unread-after-downloaded
19403 If @code{gnus-agent-mark-unread-after-downloaded} is non-@code{nil},
19404 mark articles as unread after downloading. This is usually a safe
19405 thing to do as the newly downloaded article has obviously not been
19406 read. The default is @code{t}.
19408 @item gnus-agent-synchronize-flags
19409 @vindex gnus-agent-synchronize-flags
19410 If @code{gnus-agent-synchronize-flags} is @code{nil}, the Agent will
19411 never automatically synchronize flags. If it is @code{ask}, which is
19412 the default, the Agent will check if you made any changes and if so
19413 ask if you wish to synchronize these when you re-connect. If it has
19414 any other value, all flags will be synchronized automatically.
19416 @item gnus-agent-consider-all-articles
19417 @vindex gnus-agent-consider-all-articles
19418 If @code{gnus-agent-consider-all-articles} is non-@code{nil}, the
19419 agent will let the agent predicate decide whether articles need to be
19420 downloaded or not, for all articles. When @code{nil}, the default,
19421 the agent will only let the predicate decide whether unread articles
19422 are downloaded or not. If you enable this, you may also want to look
19423 into the agent expiry settings (@pxref{Category Variables}), so that
19424 the agent doesn't download articles which the agent will later expire,
19425 over and over again.
19427 @item gnus-agent-max-fetch-size
19428 @vindex gnus-agent-max-fetch-size
19429 The agent fetches articles into a temporary buffer prior to parsing
19430 them into individual files. To avoid exceeding the max. buffer size,
19431 the agent alternates between fetching and parsing until all articles
19432 have been fetched. @code{gnus-agent-max-fetch-size} provides a size
19433 limit to control how often the cycling occurs. A large value improves
19434 performance. A small value minimizes the time lost should the
19435 connection be lost while fetching (You may need to run
19436 @code{gnus-agent-regenerate-group} to update the group's state.
19437 However, all articles parsed prior to loosing the connection will be
19438 available while unplugged). The default is 10M so it is unusual to
19441 @item gnus-server-unopen-status
19442 @vindex gnus-server-unopen-status
19443 Perhaps not an Agent variable, but closely related to the Agent, this
19444 variable says what will happen if Gnus cannot open a server. If the
19445 Agent is enabled, the default, @code{nil}, makes Gnus ask the user
19446 whether to deny the server or whether to unplug the agent. If the
19447 Agent is disabled, Gnus always simply deny the server. Other choices
19448 for this variable include @code{denied} and @code{offline} the latter
19449 is only valid if the Agent is used.
19451 @item gnus-auto-goto-ignores
19452 @vindex gnus-auto-goto-ignores
19453 Another variable that isn't an Agent variable, yet so closely related
19454 that most will look for it here, this variable tells the summary
19455 buffer how to maneuver around undownloaded (only headers stored in the
19456 agent) and unfetched (neither article nor headers stored) articles.
19458 The valid values are @code{nil} (maneuver to any article),
19459 @code{undownloaded} (maneuvering while unplugged ignores articles that
19460 have not been fetched), @code{always-undownloaded} (maneuvering always
19461 ignores articles that have not been fetched), @code{unfetched}
19462 (maneuvering ignores articles whose headers have not been fetched).
19464 @item gnus-agent-queue-mail
19465 @vindex gnus-agent-queue-mail
19466 When @code{gnus-agent-queue-mail} is @code{always}, Gnus will always
19467 queue mail rather than sending it straight away. When @code{t}, Gnus
19468 will queue mail when unplugged only. When @code{nil}, never queue
19469 mail. The default is @code{t}.
19471 @item gnus-agent-prompt-send-queue
19472 @vindex gnus-agent-prompt-send-queue
19473 When @code{gnus-agent-prompt-send-queue} is non-@code{nil} Gnus will
19474 prompt you to confirm that you really wish to proceed if you hit
19475 @kbd{J S} while unplugged. The default is @code{nil}.
19477 @item gnus-agent-auto-agentize-methods
19478 @vindex gnus-agent-auto-agentize-methods
19479 If you have never used the Agent before (or more technically, if
19480 @file{~/News/agent/lib/servers} does not exist), Gnus will
19481 automatically agentize a few servers for you. This variable control
19482 which back ends should be auto-agentized. It is typically only useful
19483 to agentize remote back ends. The auto-agentizing has the same effect
19484 as running @kbd{J a} on the servers (@pxref{Server Agent Commands}).
19485 If the file exist, you must manage the servers manually by adding or
19486 removing them, this variable is only applicable the first time you
19487 start Gnus. The default is @samp{(nntp nnimap)}.
19492 @node Example Setup
19493 @subsection Example Setup
19495 If you don't want to read this manual, and you have a fairly standard
19496 setup, you may be able to use something like the following as your
19497 @file{~/.gnus.el} file to get started.
19500 ;;; @r{Define how Gnus is to fetch news. We do this over @acronym{NNTP}}
19501 ;;; @r{from your ISP's server.}
19502 (setq gnus-select-method '(nntp "news.your-isp.com"))
19504 ;;; @r{Define how Gnus is to read your mail. We read mail from}
19505 ;;; @r{your ISP's @acronym{POP} server.}
19506 (setq mail-sources '((pop :server "pop.your-isp.com")))
19508 ;;; @r{Say how Gnus is to store the mail. We use nnml groups.}
19509 (setq gnus-secondary-select-methods '((nnml "")))
19511 ;;; @r{Make Gnus into an offline newsreader.}
19512 ;;; (gnus-agentize) ; @r{The obsolete setting.}
19513 ;;; (setq gnus-agent t) ; @r{Now the default.}
19516 That should be it, basically. Put that in your @file{~/.gnus.el} file,
19517 edit to suit your needs, start up PPP (or whatever), and type @kbd{M-x
19520 If this is the first time you've run Gnus, you will be subscribed
19521 automatically to a few default newsgroups. You'll probably want to
19522 subscribe to more groups, and to do that, you have to query the
19523 @acronym{NNTP} server for a complete list of groups with the @kbd{A A}
19524 command. This usually takes quite a while, but you only have to do it
19527 After reading and parsing a while, you'll be presented with a list of
19528 groups. Subscribe to the ones you want to read with the @kbd{u}
19529 command. @kbd{l} to make all the killed groups disappear after you've
19530 subscribe to all the groups you want to read. (@kbd{A k} will bring
19531 back all the killed groups.)
19533 You can now read the groups at once, or you can download the articles
19534 with the @kbd{J s} command. And then read the rest of this manual to
19535 find out which of the other gazillion things you want to customize.
19538 @node Batching Agents
19539 @subsection Batching Agents
19540 @findex gnus-agent-batch
19542 Having the Gnus Agent fetch articles (and post whatever messages you've
19543 written) is quite easy once you've gotten things set up properly. The
19544 following shell script will do everything that is necessary:
19546 You can run a complete batch command from the command line with the
19547 following incantation:
19551 emacs -batch -l ~/.emacs -l ~/.gnus.el gnus-agent-batch >/dev/null 2>&1
19555 @node Agent Caveats
19556 @subsection Agent Caveats
19558 The Gnus Agent doesn't seem to work like most other offline
19559 newsreaders. Here are some common questions that some imaginary people
19563 @item If I read an article while plugged, do they get entered into the Agent?
19565 @strong{No}. If you want this behavior, add
19566 @code{gnus-agent-fetch-selected-article} to
19567 @code{gnus-select-article-hook}.
19569 @item If I read an article while plugged, and the article already exists in
19570 the Agent, will it get downloaded once more?
19572 @strong{No}, unless @code{gnus-agent-cache} is @code{nil}.
19576 In short, when Gnus is unplugged, it only looks into the locally stored
19577 articles; when it's plugged, it talks to your ISP and may also use the
19578 locally stored articles.
19585 Other people use @dfn{kill files}, but we here at Gnus Towers like
19586 scoring better than killing, so we'd rather switch than fight. They do
19587 something completely different as well, so sit up straight and pay
19590 @vindex gnus-summary-mark-below
19591 All articles have a default score (@code{gnus-summary-default-score}),
19592 which is 0 by default. This score may be raised or lowered either
19593 interactively or by score files. Articles that have a score lower than
19594 @code{gnus-summary-mark-below} are marked as read.
19596 Gnus will read any @dfn{score files} that apply to the current group
19597 before generating the summary buffer.
19599 There are several commands in the summary buffer that insert score
19600 entries based on the current article. You can, for instance, ask Gnus to
19601 lower or increase the score of all articles with a certain subject.
19603 There are two sorts of scoring entries: Permanent and temporary.
19604 Temporary score entries are self-expiring entries. Any entries that are
19605 temporary and have not been used for, say, a week, will be removed
19606 silently to help keep the sizes of the score files down.
19609 * Summary Score Commands:: Adding score entries for the current group.
19610 * Group Score Commands:: General score commands.
19611 * Score Variables:: Customize your scoring. (My, what terminology).
19612 * Score File Format:: What a score file may contain.
19613 * Score File Editing:: You can edit score files by hand as well.
19614 * Adaptive Scoring:: Big Sister Gnus knows what you read.
19615 * Home Score File:: How to say where new score entries are to go.
19616 * Followups To Yourself:: Having Gnus notice when people answer you.
19617 * Scoring On Other Headers:: Scoring on non-standard headers.
19618 * Scoring Tips:: How to score effectively.
19619 * Reverse Scoring:: That problem child of old is not problem.
19620 * Global Score Files:: Earth-spanning, ear-splitting score files.
19621 * Kill Files:: They are still here, but they can be ignored.
19622 * Converting Kill Files:: Translating kill files to score files.
19623 * Advanced Scoring:: Using logical expressions to build score rules.
19624 * Score Decays:: It can be useful to let scores wither away.
19628 @node Summary Score Commands
19629 @section Summary Score Commands
19630 @cindex score commands
19632 The score commands that alter score entries do not actually modify real
19633 score files. That would be too inefficient. Gnus maintains a cache of
19634 previously loaded score files, one of which is considered the
19635 @dfn{current score file alist}. The score commands simply insert
19636 entries into this list, and upon group exit, this list is saved.
19638 The current score file is by default the group's local score file, even
19639 if no such score file actually exists. To insert score commands into
19640 some other score file (e.g. @file{all.SCORE}), you must first make this
19641 score file the current one.
19643 General score commands that don't actually change the score file:
19648 @kindex V s (Summary)
19649 @findex gnus-summary-set-score
19650 Set the score of the current article (@code{gnus-summary-set-score}).
19653 @kindex V S (Summary)
19654 @findex gnus-summary-current-score
19655 Display the score of the current article
19656 (@code{gnus-summary-current-score}).
19659 @kindex V t (Summary)
19660 @findex gnus-score-find-trace
19661 Display all score rules that have been used on the current article
19662 (@code{gnus-score-find-trace}). In the @code{*Score Trace*} buffer, you
19663 may type @kbd{e} to edit score file corresponding to the score rule on
19664 current line and @kbd{f} to format (@code{gnus-score-pretty-print}) the
19665 score file and edit it.
19668 @kindex V w (Summary)
19669 @findex gnus-score-find-favourite-words
19670 List words used in scoring (@code{gnus-score-find-favourite-words}).
19673 @kindex V R (Summary)
19674 @findex gnus-summary-rescore
19675 Run the current summary through the scoring process
19676 (@code{gnus-summary-rescore}). This might be useful if you're playing
19677 around with your score files behind Gnus' back and want to see the
19678 effect you're having.
19681 @kindex V c (Summary)
19682 @findex gnus-score-change-score-file
19683 Make a different score file the current
19684 (@code{gnus-score-change-score-file}).
19687 @kindex V e (Summary)
19688 @findex gnus-score-edit-current-scores
19689 Edit the current score file (@code{gnus-score-edit-current-scores}).
19690 You will be popped into a @code{gnus-score-mode} buffer (@pxref{Score
19694 @kindex V f (Summary)
19695 @findex gnus-score-edit-file
19696 Edit a score file and make this score file the current one
19697 (@code{gnus-score-edit-file}).
19700 @kindex V F (Summary)
19701 @findex gnus-score-flush-cache
19702 Flush the score cache (@code{gnus-score-flush-cache}). This is useful
19703 after editing score files.
19706 @kindex V C (Summary)
19707 @findex gnus-score-customize
19708 Customize a score file in a visually pleasing manner
19709 (@code{gnus-score-customize}).
19713 The rest of these commands modify the local score file.
19718 @kindex V m (Summary)
19719 @findex gnus-score-set-mark-below
19720 Prompt for a score, and mark all articles with a score below this as
19721 read (@code{gnus-score-set-mark-below}).
19724 @kindex V x (Summary)
19725 @findex gnus-score-set-expunge-below
19726 Prompt for a score, and add a score rule to the current score file to
19727 expunge all articles below this score
19728 (@code{gnus-score-set-expunge-below}).
19731 The keystrokes for actually making score entries follow a very regular
19732 pattern, so there's no need to list all the commands. (Hundreds of
19735 @findex gnus-summary-increase-score
19736 @findex gnus-summary-lower-score
19740 The first key is either @kbd{I} (upper case i) for increasing the score
19741 or @kbd{L} for lowering the score.
19743 The second key says what header you want to score on. The following
19744 keys are available:
19748 Score on the author name.
19751 Score on the subject line.
19754 Score on the @code{Xref} line---i.e., the cross-posting line.
19757 Score on the @code{References} line.
19763 Score on the number of lines.
19766 Score on the @code{Message-ID} header.
19769 Score on an ``extra'' header, that is, one of those in gnus-extra-headers,
19770 if your @acronym{NNTP} server tracks additional header data in overviews.
19773 Score on followups---this matches the author name, and adds scores to
19774 the followups to this author. (Using this key leads to the creation of
19775 @file{ADAPT} files.)
19784 Score on thread. (Using this key leads to the creation of @file{ADAPT}
19790 The third key is the match type. Which match types are valid depends on
19791 what headers you are scoring on.
19803 Substring matching.
19806 Fuzzy matching (@pxref{Fuzzy Matching}).
19835 Greater than number.
19840 The fourth and usually final key says whether this is a temporary (i.e.,
19841 expiring) score entry, or a permanent (i.e., non-expiring) score entry,
19842 or whether it is to be done immediately, without adding to the score
19847 Temporary score entry.
19850 Permanent score entry.
19853 Immediately scoring.
19857 If you are scoring on `e' (extra) headers, you will then be prompted for
19858 the header name on which you wish to score. This must be a header named
19859 in gnus-extra-headers, and @samp{TAB} completion is available.
19863 So, let's say you want to increase the score on the current author with
19864 exact matching permanently: @kbd{I a e p}. If you want to lower the
19865 score based on the subject line, using substring matching, and make a
19866 temporary score entry: @kbd{L s s t}. Pretty easy.
19868 To make things a bit more complicated, there are shortcuts. If you use
19869 a capital letter on either the second or third keys, Gnus will use
19870 defaults for the remaining one or two keystrokes. The defaults are
19871 ``substring'' and ``temporary''. So @kbd{I A} is the same as @kbd{I a s
19872 t}, and @kbd{I a R} is the same as @kbd{I a r t}.
19874 These functions take both the numerical prefix and the symbolic prefix
19875 (@pxref{Symbolic Prefixes}). A numerical prefix says how much to lower
19876 (or increase) the score of the article. A symbolic prefix of @code{a}
19877 says to use the @file{all.SCORE} file for the command instead of the
19878 current score file.
19880 @vindex gnus-score-mimic-keymap
19881 The @code{gnus-score-mimic-keymap} says whether these commands will
19882 pretend they are keymaps or not.
19885 @node Group Score Commands
19886 @section Group Score Commands
19887 @cindex group score commands
19889 There aren't many of these as yet, I'm afraid.
19894 @kindex W e (Group)
19895 @findex gnus-score-edit-all-score
19896 Edit the apply-to-all-groups all.SCORE file. You will be popped into
19897 a @code{gnus-score-mode} buffer (@pxref{Score File Editing}).
19900 @kindex W f (Group)
19901 @findex gnus-score-flush-cache
19902 Gnus maintains a cache of score alists to avoid having to reload them
19903 all the time. This command will flush the cache
19904 (@code{gnus-score-flush-cache}).
19908 You can do scoring from the command line by saying something like:
19910 @findex gnus-batch-score
19911 @cindex batch scoring
19913 $ emacs -batch -l ~/.emacs -l ~/.gnus.el -f gnus-batch-score
19917 @node Score Variables
19918 @section Score Variables
19919 @cindex score variables
19923 @item gnus-use-scoring
19924 @vindex gnus-use-scoring
19925 If @code{nil}, Gnus will not check for score files, and will not, in
19926 general, do any score-related work. This is @code{t} by default.
19928 @item gnus-kill-killed
19929 @vindex gnus-kill-killed
19930 If this variable is @code{nil}, Gnus will never apply score files to
19931 articles that have already been through the kill process. While this
19932 may save you lots of time, it also means that if you apply a kill file
19933 to a group, and then change the kill file and want to run it over you
19934 group again to kill more articles, it won't work. You have to set this
19935 variable to @code{t} to do that. (It is @code{t} by default.)
19937 @item gnus-kill-files-directory
19938 @vindex gnus-kill-files-directory
19939 All kill and score files will be stored in this directory, which is
19940 initialized from the @env{SAVEDIR} environment variable by default.
19941 This is @file{~/News/} by default.
19943 @item gnus-score-file-suffix
19944 @vindex gnus-score-file-suffix
19945 Suffix to add to the group name to arrive at the score file name
19946 (@file{SCORE} by default.)
19948 @item gnus-score-uncacheable-files
19949 @vindex gnus-score-uncacheable-files
19950 @cindex score cache
19951 All score files are normally cached to avoid excessive re-loading of
19952 score files. However, if this might make your Emacs grow big and
19953 bloated, so this regexp can be used to weed out score files unlikely
19954 to be needed again. It would be a bad idea to deny caching of
19955 @file{all.SCORE}, while it might be a good idea to not cache
19956 @file{comp.infosystems.www.authoring.misc.ADAPT}. In fact, this
19957 variable is @samp{ADAPT$} by default, so no adaptive score files will
19960 @item gnus-save-score
19961 @vindex gnus-save-score
19962 If you have really complicated score files, and do lots of batch
19963 scoring, then you might set this variable to @code{t}. This will make
19964 Gnus save the scores into the @file{.newsrc.eld} file.
19966 If you do not set this to @code{t}, then manual scores (like those set
19967 with @kbd{V s} (@code{gnus-summary-set-score})) will not be preserved
19968 across group visits.
19970 @item gnus-score-interactive-default-score
19971 @vindex gnus-score-interactive-default-score
19972 Score used by all the interactive raise/lower commands to raise/lower
19973 score with. Default is 1000, which may seem excessive, but this is to
19974 ensure that the adaptive scoring scheme gets enough room to play with.
19975 We don't want the small changes from the adaptive scoring to overwrite
19976 manually entered data.
19978 @item gnus-summary-default-score
19979 @vindex gnus-summary-default-score
19980 Default score of an article, which is 0 by default.
19982 @item gnus-summary-expunge-below
19983 @vindex gnus-summary-expunge-below
19984 Don't display the summary lines of articles that have scores lower than
19985 this variable. This is @code{nil} by default, which means that no
19986 articles will be hidden. This variable is local to the summary buffers,
19987 and has to be set from @code{gnus-summary-mode-hook}.
19989 @item gnus-score-over-mark
19990 @vindex gnus-score-over-mark
19991 Mark (in the third column) used for articles with a score over the
19992 default. Default is @samp{+}.
19994 @item gnus-score-below-mark
19995 @vindex gnus-score-below-mark
19996 Mark (in the third column) used for articles with a score below the
19997 default. Default is @samp{-}.
19999 @item gnus-score-find-score-files-function
20000 @vindex gnus-score-find-score-files-function
20001 Function used to find score files for the current group. This function
20002 is called with the name of the group as the argument.
20004 Predefined functions available are:
20007 @item gnus-score-find-single
20008 @findex gnus-score-find-single
20009 Only apply the group's own score file.
20011 @item gnus-score-find-bnews
20012 @findex gnus-score-find-bnews
20013 Apply all score files that match, using bnews syntax. This is the
20014 default. If the current group is @samp{gnu.emacs.gnus}, for instance,
20015 @file{all.emacs.all.SCORE}, @file{not.alt.all.SCORE} and
20016 @file{gnu.all.SCORE} would all apply. In short, the instances of
20017 @samp{all} in the score file names are translated into @samp{.*}, and
20018 then a regexp match is done.
20020 This means that if you have some score entries that you want to apply to
20021 all groups, then you put those entries in the @file{all.SCORE} file.
20023 The score files are applied in a semi-random order, although Gnus will
20024 try to apply the more general score files before the more specific score
20025 files. It does this by looking at the number of elements in the score
20026 file names---discarding the @samp{all} elements.
20028 @item gnus-score-find-hierarchical
20029 @findex gnus-score-find-hierarchical
20030 Apply all score files from all the parent groups. This means that you
20031 can't have score files like @file{all.SCORE}, but you can have
20032 @file{SCORE}, @file{comp.SCORE} and @file{comp.emacs.SCORE} for each
20036 This variable can also be a list of functions. In that case, all
20037 these functions will be called with the group name as argument, and
20038 all the returned lists of score files will be applied. These
20039 functions can also return lists of lists of score alists directly. In
20040 that case, the functions that return these non-file score alists
20041 should probably be placed before the ``real'' score file functions, to
20042 ensure that the last score file returned is the local score file.
20045 For example, to do hierarchical scoring but use a non-server-specific
20046 overall score file, you could use the value
20048 (list (lambda (group) ("all.SCORE"))
20049 'gnus-score-find-hierarchical)
20052 @item gnus-score-expiry-days
20053 @vindex gnus-score-expiry-days
20054 This variable says how many days should pass before an unused score file
20055 entry is expired. If this variable is @code{nil}, no score file entries
20056 are expired. It's 7 by default.
20058 @item gnus-update-score-entry-dates
20059 @vindex gnus-update-score-entry-dates
20060 If this variable is non-@code{nil}, temporary score entries that have
20061 been triggered (matched) will have their dates updated. (This is how Gnus
20062 controls expiry---all non-matched-entries will become too old while
20063 matched entries will stay fresh and young.) However, if you set this
20064 variable to @code{nil}, even matched entries will grow old and will
20065 have to face that oh-so grim reaper.
20067 @item gnus-score-after-write-file-function
20068 @vindex gnus-score-after-write-file-function
20069 Function called with the name of the score file just written.
20071 @item gnus-score-thread-simplify
20072 @vindex gnus-score-thread-simplify
20073 If this variable is non-@code{nil}, article subjects will be
20074 simplified for subject scoring purposes in the same manner as with
20075 threading---according to the current value of
20076 @code{gnus-simplify-subject-functions}. If the scoring entry uses
20077 @code{substring} or @code{exact} matching, the match will also be
20078 simplified in this manner.
20083 @node Score File Format
20084 @section Score File Format
20085 @cindex score file format
20087 A score file is an @code{emacs-lisp} file that normally contains just a
20088 single form. Casual users are not expected to edit these files;
20089 everything can be changed from the summary buffer.
20091 Anyway, if you'd like to dig into it yourself, here's an example:
20095 ("Lars Ingebrigtsen" -10000)
20097 ("larsi\\|lmi" -50000 nil R))
20099 ("Ding is Badd" nil 728373))
20101 ("alt.politics" -1000 728372 s))
20106 (mark-and-expunge -10)
20110 (files "/hom/larsi/News/gnu.SCORE")
20111 (exclude-files "all.SCORE")
20112 (local (gnus-newsgroup-auto-expire t)
20113 (gnus-summary-make-false-root empty))
20117 This example demonstrates most score file elements. @xref{Advanced
20118 Scoring}, for a different approach.
20120 Even though this looks much like Lisp code, nothing here is actually
20121 @code{eval}ed. The Lisp reader is used to read this form, though, so it
20122 has to be valid syntactically, if not semantically.
20124 Six keys are supported by this alist:
20129 If the key is a string, it is the name of the header to perform the
20130 match on. Scoring can only be performed on these eight headers:
20131 @code{From}, @code{Subject}, @code{References}, @code{Message-ID},
20132 @code{Xref}, @code{Lines}, @code{Chars} and @code{Date}. In addition to
20133 these headers, there are three strings to tell Gnus to fetch the entire
20134 article and do the match on larger parts of the article: @code{Body}
20135 will perform the match on the body of the article, @code{Head} will
20136 perform the match on the head of the article, and @code{All} will
20137 perform the match on the entire article. Note that using any of these
20138 last three keys will slow down group entry @emph{considerably}. The
20139 final ``header'' you can score on is @code{Followup}. These score
20140 entries will result in new score entries being added for all follow-ups
20141 to articles that matches these score entries.
20143 Following this key is an arbitrary number of score entries, where each
20144 score entry has one to four elements.
20148 The first element is the @dfn{match element}. On most headers this will
20149 be a string, but on the Lines and Chars headers, this must be an
20153 If the second element is present, it should be a number---the @dfn{score
20154 element}. This number should be an integer in the neginf to posinf
20155 interval. This number is added to the score of the article if the match
20156 is successful. If this element is not present, the
20157 @code{gnus-score-interactive-default-score} number will be used
20158 instead. This is 1000 by default.
20161 If the third element is present, it should be a number---the @dfn{date
20162 element}. This date says when the last time this score entry matched,
20163 which provides a mechanism for expiring the score entries. It this
20164 element is not present, the score entry is permanent. The date is
20165 represented by the number of days since December 31, 1 BCE.
20168 If the fourth element is present, it should be a symbol---the @dfn{type
20169 element}. This element specifies what function should be used to see
20170 whether this score entry matches the article. What match types that can
20171 be used depends on what header you wish to perform the match on.
20174 @item From, Subject, References, Xref, Message-ID
20175 For most header types, there are the @code{r} and @code{R} (regexp), as
20176 well as @code{s} and @code{S} (substring) types, and @code{e} and
20177 @code{E} (exact match), and @code{w} (word match) types. If this
20178 element is not present, Gnus will assume that substring matching should
20179 be used. @code{R}, @code{S}, and @code{E} differ from the others in
20180 that the matches will be done in a case-sensitive manner. All these
20181 one-letter types are really just abbreviations for the @code{regexp},
20182 @code{string}, @code{exact}, and @code{word} types, which you can use
20183 instead, if you feel like.
20186 Just as for the standard string overview headers, if you are using
20187 gnus-extra-headers, you can score on these headers' values. In this
20188 case, there is a 5th element in the score entry, being the name of the
20189 header to be scored. The following entry is useful in your
20190 @file{all.SCORE} file in case of spam attacks from a single origin
20191 host, if your @acronym{NNTP} server tracks @samp{NNTP-Posting-Host} in
20195 ("111.222.333.444" -1000 nil s
20196 "NNTP-Posting-Host")
20200 These two headers use different match types: @code{<}, @code{>},
20201 @code{=}, @code{>=} and @code{<=}.
20203 These predicates are true if
20206 (PREDICATE HEADER MATCH)
20209 evaluates to non-@code{nil}. For instance, the advanced match
20210 @code{("lines" 4 <)} (@pxref{Advanced Scoring}) will result in the
20217 Or to put it another way: When using @code{<} on @code{Lines} with 4 as
20218 the match, we get the score added if the article has less than 4 lines.
20219 (It's easy to get confused and think it's the other way around. But
20220 it's not. I think.)
20222 When matching on @code{Lines}, be careful because some back ends (like
20223 @code{nndir}) do not generate @code{Lines} header, so every article ends
20224 up being marked as having 0 lines. This can lead to strange results if
20225 you happen to lower score of the articles with few lines.
20228 For the Date header we have three kinda silly match types:
20229 @code{before}, @code{at} and @code{after}. I can't really imagine this
20230 ever being useful, but, like, it would feel kinda silly not to provide
20231 this function. Just in case. You never know. Better safe than sorry.
20232 Once burnt, twice shy. Don't judge a book by its cover. Never not have
20233 sex on a first date. (I have been told that at least one person, and I
20234 quote, ``found this function indispensable'', however.)
20238 A more useful match type is @code{regexp}. With it, you can match the
20239 date string using a regular expression. The date is normalized to
20240 ISO8601 compact format first---@var{YYYYMMDD}@code{T}@var{HHMMSS}. If
20241 you want to match all articles that have been posted on April 1st in
20242 every year, you could use @samp{....0401.........} as a match string,
20243 for instance. (Note that the date is kept in its original time zone, so
20244 this will match articles that were posted when it was April 1st where
20245 the article was posted from. Time zones are such wholesome fun for the
20248 @item Head, Body, All
20249 These three match keys use the same match types as the @code{From} (etc)
20253 This match key is somewhat special, in that it will match the
20254 @code{From} header, and affect the score of not only the matching
20255 articles, but also all followups to the matching articles. This allows
20256 you e.g. increase the score of followups to your own articles, or
20257 decrease the score of followups to the articles of some known
20258 trouble-maker. Uses the same match types as the @code{From} header
20259 uses. (Using this match key will lead to creation of @file{ADAPT}
20263 This match key works along the same lines as the @code{Followup} match
20264 key. If you say that you want to score on a (sub-)thread started by an
20265 article with a @code{Message-ID} @var{x}, then you add a @samp{thread}
20266 match. This will add a new @samp{thread} match for each article that
20267 has @var{x} in its @code{References} header. (These new @samp{thread}
20268 matches will use the @code{Message-ID}s of these matching articles.)
20269 This will ensure that you can raise/lower the score of an entire thread,
20270 even though some articles in the thread may not have complete
20271 @code{References} headers. Note that using this may lead to
20272 undeterministic scores of the articles in the thread. (Using this match
20273 key will lead to creation of @file{ADAPT} files.)
20277 @cindex score file atoms
20279 The value of this entry should be a number. Any articles with a score
20280 lower than this number will be marked as read.
20283 The value of this entry should be a number. Any articles with a score
20284 lower than this number will be removed from the summary buffer.
20286 @item mark-and-expunge
20287 The value of this entry should be a number. Any articles with a score
20288 lower than this number will be marked as read and removed from the
20291 @item thread-mark-and-expunge
20292 The value of this entry should be a number. All articles that belong to
20293 a thread that has a total score below this number will be marked as read
20294 and removed from the summary buffer. @code{gnus-thread-score-function}
20295 says how to compute the total score for a thread.
20298 The value of this entry should be any number of file names. These files
20299 are assumed to be score files as well, and will be loaded the same way
20302 @item exclude-files
20303 The clue of this entry should be any number of files. These files will
20304 not be loaded, even though they would normally be so, for some reason or
20308 The value of this entry will be @code{eval}el. This element will be
20309 ignored when handling global score files.
20312 Read-only score files will not be updated or saved. Global score files
20313 should feature this atom (@pxref{Global Score Files}). (Note:
20314 @dfn{Global} here really means @dfn{global}; not your personal
20315 apply-to-all-groups score files.)
20318 The value of this entry should be a number. Articles that do not have
20319 parents will get this number added to their scores. Imagine you follow
20320 some high-volume newsgroup, like @samp{comp.lang.c}. Most likely you
20321 will only follow a few of the threads, also want to see any new threads.
20323 You can do this with the following two score file entries:
20327 (mark-and-expunge -100)
20330 When you enter the group the first time, you will only see the new
20331 threads. You then raise the score of the threads that you find
20332 interesting (with @kbd{I T} or @kbd{I S}), and ignore (@kbd{C y}) the
20333 rest. Next time you enter the group, you will see new articles in the
20334 interesting threads, plus any new threads.
20336 I.e.---the orphan score atom is for high-volume groups where a few
20337 interesting threads which can't be found automatically by ordinary
20338 scoring rules exist.
20341 This entry controls the adaptive scoring. If it is @code{t}, the
20342 default adaptive scoring rules will be used. If it is @code{ignore}, no
20343 adaptive scoring will be performed on this group. If it is a list, this
20344 list will be used as the adaptive scoring rules. If it isn't present,
20345 or is something other than @code{t} or @code{ignore}, the default
20346 adaptive scoring rules will be used. If you want to use adaptive
20347 scoring on most groups, you'd set @code{gnus-use-adaptive-scoring} to
20348 @code{t}, and insert an @code{(adapt ignore)} in the groups where you do
20349 not want adaptive scoring. If you only want adaptive scoring in a few
20350 groups, you'd set @code{gnus-use-adaptive-scoring} to @code{nil}, and
20351 insert @code{(adapt t)} in the score files of the groups where you want
20355 All adaptive score entries will go to the file named by this entry. It
20356 will also be applied when entering the group. This atom might be handy
20357 if you want to adapt on several groups at once, using the same adaptive
20358 file for a number of groups.
20361 @cindex local variables
20362 The value of this entry should be a list of @code{(@var{var}
20363 @var{value})} pairs. Each @var{var} will be made buffer-local to the
20364 current summary buffer, and set to the value specified. This is a
20365 convenient, if somewhat strange, way of setting variables in some
20366 groups if you don't like hooks much. Note that the @var{value} won't
20371 @node Score File Editing
20372 @section Score File Editing
20374 You normally enter all scoring commands from the summary buffer, but you
20375 might feel the urge to edit them by hand as well, so we've supplied you
20376 with a mode for that.
20378 It's simply a slightly customized @code{emacs-lisp} mode, with these
20379 additional commands:
20384 @kindex C-c C-c (Score)
20385 @findex gnus-score-edit-done
20386 Save the changes you have made and return to the summary buffer
20387 (@code{gnus-score-edit-done}).
20390 @kindex C-c C-d (Score)
20391 @findex gnus-score-edit-insert-date
20392 Insert the current date in numerical format
20393 (@code{gnus-score-edit-insert-date}). This is really the day number, if
20394 you were wondering.
20397 @kindex C-c C-p (Score)
20398 @findex gnus-score-pretty-print
20399 The adaptive score files are saved in an unformatted fashion. If you
20400 intend to read one of these files, you want to @dfn{pretty print} it
20401 first. This command (@code{gnus-score-pretty-print}) does that for
20406 Type @kbd{M-x gnus-score-mode} to use this mode.
20408 @vindex gnus-score-mode-hook
20409 @code{gnus-score-menu-hook} is run in score mode buffers.
20411 In the summary buffer you can use commands like @kbd{V f}, @kbd{V e} and
20412 @kbd{V t} to begin editing score files.
20415 @node Adaptive Scoring
20416 @section Adaptive Scoring
20417 @cindex adaptive scoring
20419 If all this scoring is getting you down, Gnus has a way of making it all
20420 happen automatically---as if by magic. Or rather, as if by artificial
20421 stupidity, to be precise.
20423 @vindex gnus-use-adaptive-scoring
20424 When you read an article, or mark an article as read, or kill an
20425 article, you leave marks behind. On exit from the group, Gnus can sniff
20426 these marks and add score elements depending on what marks it finds.
20427 You turn on this ability by setting @code{gnus-use-adaptive-scoring} to
20428 @code{t} or @code{(line)}. If you want score adaptively on separate
20429 words appearing in the subjects, you should set this variable to
20430 @code{(word)}. If you want to use both adaptive methods, set this
20431 variable to @code{(word line)}.
20433 @vindex gnus-default-adaptive-score-alist
20434 To give you complete control over the scoring process, you can customize
20435 the @code{gnus-default-adaptive-score-alist} variable. For instance, it
20436 might look something like this:
20439 (setq gnus-default-adaptive-score-alist
20440 '((gnus-unread-mark)
20441 (gnus-ticked-mark (from 4))
20442 (gnus-dormant-mark (from 5))
20443 (gnus-del-mark (from -4) (subject -1))
20444 (gnus-read-mark (from 4) (subject 2))
20445 (gnus-expirable-mark (from -1) (subject -1))
20446 (gnus-killed-mark (from -1) (subject -3))
20447 (gnus-kill-file-mark)
20448 (gnus-ancient-mark)
20449 (gnus-low-score-mark)
20450 (gnus-catchup-mark (from -1) (subject -1))))
20453 As you see, each element in this alist has a mark as a key (either a
20454 variable name or a ``real'' mark---a character). Following this key is
20455 a arbitrary number of header/score pairs. If there are no header/score
20456 pairs following the key, no adaptive scoring will be done on articles
20457 that have that key as the article mark. For instance, articles with
20458 @code{gnus-unread-mark} in the example above will not get adaptive score
20461 Each article can have only one mark, so just a single of these rules
20462 will be applied to each article.
20464 To take @code{gnus-del-mark} as an example---this alist says that all
20465 articles that have that mark (i.e., are marked with @samp{e}) will have a
20466 score entry added to lower based on the @code{From} header by -4, and
20467 lowered by @code{Subject} by -1. Change this to fit your prejudices.
20469 If you have marked 10 articles with the same subject with
20470 @code{gnus-del-mark}, the rule for that mark will be applied ten times.
20471 That means that that subject will get a score of ten times -1, which
20472 should be, unless I'm much mistaken, -10.
20474 If you have auto-expirable (mail) groups (@pxref{Expiring Mail}), all
20475 the read articles will be marked with the @samp{E} mark. This'll
20476 probably make adaptive scoring slightly impossible, so auto-expiring and
20477 adaptive scoring doesn't really mix very well.
20479 The headers you can score on are @code{from}, @code{subject},
20480 @code{message-id}, @code{references}, @code{xref}, @code{lines},
20481 @code{chars} and @code{date}. In addition, you can score on
20482 @code{followup}, which will create an adaptive score entry that matches
20483 on the @code{References} header using the @code{Message-ID} of the
20484 current article, thereby matching the following thread.
20486 If you use this scheme, you should set the score file atom @code{mark}
20487 to something small---like -300, perhaps, to avoid having small random
20488 changes result in articles getting marked as read.
20490 After using adaptive scoring for a week or so, Gnus should start to
20491 become properly trained and enhance the authors you like best, and kill
20492 the authors you like least, without you having to say so explicitly.
20494 You can control what groups the adaptive scoring is to be performed on
20495 by using the score files (@pxref{Score File Format}). This will also
20496 let you use different rules in different groups.
20498 @vindex gnus-adaptive-file-suffix
20499 The adaptive score entries will be put into a file where the name is the
20500 group name with @code{gnus-adaptive-file-suffix} appended. The default
20503 @vindex gnus-adaptive-pretty-print
20504 Adaptive score files can get huge and are not meant to be edited by
20505 human hands. If @code{gnus-adaptive-pretty-print} is @code{nil} (the
20506 deafult) those files will not be written in a human readable way.
20508 @vindex gnus-score-exact-adapt-limit
20509 When doing adaptive scoring, substring or fuzzy matching would probably
20510 give you the best results in most cases. However, if the header one
20511 matches is short, the possibility for false positives is great, so if
20512 the length of the match is less than
20513 @code{gnus-score-exact-adapt-limit}, exact matching will be used. If
20514 this variable is @code{nil}, exact matching will always be used to avoid
20517 @vindex gnus-default-adaptive-word-score-alist
20518 As mentioned above, you can adapt either on individual words or entire
20519 headers. If you adapt on words, the
20520 @code{gnus-default-adaptive-word-score-alist} variable says what score
20521 each instance of a word should add given a mark.
20524 (setq gnus-default-adaptive-word-score-alist
20525 `((,gnus-read-mark . 30)
20526 (,gnus-catchup-mark . -10)
20527 (,gnus-killed-mark . -20)
20528 (,gnus-del-mark . -15)))
20531 This is the default value. If you have adaption on words enabled, every
20532 word that appears in subjects of articles marked with
20533 @code{gnus-read-mark} will result in a score rule that increase the
20534 score with 30 points.
20536 @vindex gnus-default-ignored-adaptive-words
20537 @vindex gnus-ignored-adaptive-words
20538 Words that appear in the @code{gnus-default-ignored-adaptive-words} list
20539 will be ignored. If you wish to add more words to be ignored, use the
20540 @code{gnus-ignored-adaptive-words} list instead.
20542 @vindex gnus-adaptive-word-length-limit
20543 Some may feel that short words shouldn't count when doing adaptive
20544 scoring. If so, you may set @code{gnus-adaptive-word-length-limit} to
20545 an integer. Words shorter than this number will be ignored. This
20546 variable defaults to @code{nil}.
20548 @vindex gnus-adaptive-word-syntax-table
20549 When the scoring is done, @code{gnus-adaptive-word-syntax-table} is the
20550 syntax table in effect. It is similar to the standard syntax table, but
20551 it considers numbers to be non-word-constituent characters.
20553 @vindex gnus-adaptive-word-minimum
20554 If @code{gnus-adaptive-word-minimum} is set to a number, the adaptive
20555 word scoring process will never bring down the score of an article to
20556 below this number. The default is @code{nil}.
20558 @vindex gnus-adaptive-word-no-group-words
20559 If @code{gnus-adaptive-word-no-group-words} is set to @code{t}, gnus
20560 won't adaptively word score any of the words in the group name. Useful
20561 for groups like @samp{comp.editors.emacs}, where most of the subject
20562 lines contain the word @samp{emacs}.
20564 After using this scheme for a while, it might be nice to write a
20565 @code{gnus-psychoanalyze-user} command to go through the rules and see
20566 what words you like and what words you don't like. Or perhaps not.
20568 Note that the adaptive word scoring thing is highly experimental and is
20569 likely to change in the future. Initial impressions seem to indicate
20570 that it's totally useless as it stands. Some more work (involving more
20571 rigorous statistical methods) will have to be done to make this useful.
20574 @node Home Score File
20575 @section Home Score File
20577 The score file where new score file entries will go is called the
20578 @dfn{home score file}. This is normally (and by default) the score file
20579 for the group itself. For instance, the home score file for
20580 @samp{gnu.emacs.gnus} is @file{gnu.emacs.gnus.SCORE}.
20582 However, this may not be what you want. It is often convenient to share
20583 a common home score file among many groups---all @samp{emacs} groups
20584 could perhaps use the same home score file.
20586 @vindex gnus-home-score-file
20587 The variable that controls this is @code{gnus-home-score-file}. It can
20592 A string. Then this file will be used as the home score file for all
20596 A function. The result of this function will be used as the home score
20597 file. The function will be called with the name of the group as the
20601 A list. The elements in this list can be:
20605 @code{(@var{regexp} @var{file-name})}. If the @var{regexp} matches the
20606 group name, the @var{file-name} will be used as the home score file.
20609 A function. If the function returns non-@code{nil}, the result will
20610 be used as the home score file. The function will be called with the
20611 name of the group as the parameter.
20614 A string. Use the string as the home score file.
20617 The list will be traversed from the beginning towards the end looking
20622 So, if you want to use just a single score file, you could say:
20625 (setq gnus-home-score-file
20626 "my-total-score-file.SCORE")
20629 If you want to use @file{gnu.SCORE} for all @samp{gnu} groups and
20630 @file{rec.SCORE} for all @samp{rec} groups (and so on), you can say:
20632 @findex gnus-hierarchial-home-score-file
20634 (setq gnus-home-score-file
20635 'gnus-hierarchial-home-score-file)
20638 This is a ready-made function provided for your convenience.
20639 Other functions include
20642 @item gnus-current-home-score-file
20643 @findex gnus-current-home-score-file
20644 Return the ``current'' regular score file. This will make scoring
20645 commands add entry to the ``innermost'' matching score file.
20649 If you want to have one score file for the @samp{emacs} groups and
20650 another for the @samp{comp} groups, while letting all other groups use
20651 their own home score files:
20654 (setq gnus-home-score-file
20655 ;; @r{All groups that match the regexp @code{"\\.emacs"}}
20656 '(("\\.emacs" "emacs.SCORE")
20657 ;; @r{All the comp groups in one score file}
20658 ("^comp" "comp.SCORE")))
20661 @vindex gnus-home-adapt-file
20662 @code{gnus-home-adapt-file} works exactly the same way as
20663 @code{gnus-home-score-file}, but says what the home adaptive score file
20664 is instead. All new adaptive file entries will go into the file
20665 specified by this variable, and the same syntax is allowed.
20667 In addition to using @code{gnus-home-score-file} and
20668 @code{gnus-home-adapt-file}, you can also use group parameters
20669 (@pxref{Group Parameters}) and topic parameters (@pxref{Topic
20670 Parameters}) to achieve much the same. Group and topic parameters take
20671 precedence over this variable.
20674 @node Followups To Yourself
20675 @section Followups To Yourself
20677 Gnus offers two commands for picking out the @code{Message-ID} header in
20678 the current buffer. Gnus will then add a score rule that scores using
20679 this @code{Message-ID} on the @code{References} header of other
20680 articles. This will, in effect, increase the score of all articles that
20681 respond to the article in the current buffer. Quite useful if you want
20682 to easily note when people answer what you've said.
20686 @item gnus-score-followup-article
20687 @findex gnus-score-followup-article
20688 This will add a score to articles that directly follow up your own
20691 @item gnus-score-followup-thread
20692 @findex gnus-score-followup-thread
20693 This will add a score to all articles that appear in a thread ``below''
20697 @vindex message-sent-hook
20698 These two functions are both primarily meant to be used in hooks like
20699 @code{message-sent-hook}, like this:
20701 (add-hook 'message-sent-hook 'gnus-score-followup-thread)
20705 If you look closely at your own @code{Message-ID}, you'll notice that
20706 the first two or three characters are always the same. Here's two of
20710 <x6u3u47icf.fsf@@eyesore.no>
20711 <x6sp9o7ibw.fsf@@eyesore.no>
20714 So ``my'' ident on this machine is @samp{x6}. This can be
20715 exploited---the following rule will raise the score on all followups to
20720 ("<x6[0-9a-z]+\\.fsf\\(_-_\\)?@@.*eyesore\\.no>"
20724 Whether it's the first two or first three characters that are ``yours''
20725 is system-dependent.
20728 @node Scoring On Other Headers
20729 @section Scoring On Other Headers
20730 @cindex scoring on other headers
20732 Gnus is quite fast when scoring the ``traditional''
20733 headers---@samp{From}, @samp{Subject} and so on. However, scoring
20734 other headers requires writing a @code{head} scoring rule, which means
20735 that Gnus has to request every single article from the back end to find
20736 matches. This takes a long time in big groups.
20738 Now, there's not much you can do about this for news groups, but for
20739 mail groups, you have greater control. In @ref{To From Newsgroups},
20740 it's explained in greater detail what this mechanism does, but here's
20741 a cookbook example for @code{nnml} on how to allow scoring on the
20742 @samp{To} and @samp{Cc} headers.
20744 Put the following in your @file{~/.gnus.el} file.
20747 (setq gnus-extra-headers '(To Cc Newsgroups Keywords)
20748 nnmail-extra-headers gnus-extra-headers)
20751 Restart Gnus and rebuild your @code{nnml} overview files with the
20752 @kbd{M-x nnml-generate-nov-databases} command. This will take a long
20753 time if you have much mail.
20755 Now you can score on @samp{To} and @samp{Cc} as ``extra headers'' like
20756 so: @kbd{I e s p To RET <your name> RET}.
20762 @section Scoring Tips
20763 @cindex scoring tips
20769 @cindex scoring crossposts
20770 If you want to lower the score of crossposts, the line to match on is
20771 the @code{Xref} header.
20773 ("xref" (" talk.politics.misc:" -1000))
20776 @item Multiple crossposts
20777 If you want to lower the score of articles that have been crossposted to
20778 more than, say, 3 groups:
20781 ("[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+"
20785 @item Matching on the body
20786 This is generally not a very good idea---it takes a very long time.
20787 Gnus actually has to fetch each individual article from the server. But
20788 you might want to anyway, I guess. Even though there are three match
20789 keys (@code{Head}, @code{Body} and @code{All}), you should choose one
20790 and stick with it in each score file. If you use any two, each article
20791 will be fetched @emph{twice}. If you want to match a bit on the
20792 @code{Head} and a bit on the @code{Body}, just use @code{All} for all
20795 @item Marking as read
20796 You will probably want to mark articles that have scores below a certain
20797 number as read. This is most easily achieved by putting the following
20798 in your @file{all.SCORE} file:
20802 You may also consider doing something similar with @code{expunge}.
20804 @item Negated character classes
20805 If you say stuff like @code{[^abcd]*}, you may get unexpected results.
20806 That will match newlines, which might lead to, well, The Unknown. Say
20807 @code{[^abcd\n]*} instead.
20811 @node Reverse Scoring
20812 @section Reverse Scoring
20813 @cindex reverse scoring
20815 If you want to keep just articles that have @samp{Sex with Emacs} in the
20816 subject header, and expunge all other articles, you could put something
20817 like this in your score file:
20821 ("Sex with Emacs" 2))
20826 So, you raise all articles that match @samp{Sex with Emacs} and mark the
20827 rest as read, and expunge them to boot.
20830 @node Global Score Files
20831 @section Global Score Files
20832 @cindex global score files
20834 Sure, other newsreaders have ``global kill files''. These are usually
20835 nothing more than a single kill file that applies to all groups, stored
20836 in the user's home directory. Bah! Puny, weak newsreaders!
20838 What I'm talking about here are Global Score Files. Score files from
20839 all over the world, from users everywhere, uniting all nations in one
20840 big, happy score file union! Ange-score! New and untested!
20842 @vindex gnus-global-score-files
20843 All you have to do to use other people's score files is to set the
20844 @code{gnus-global-score-files} variable. One entry for each score file,
20845 or each score file directory. Gnus will decide by itself what score
20846 files are applicable to which group.
20848 To use the score file
20849 @file{/ftp@@ftp.gnus.org:/pub/larsi/ding/score/soc.motss.SCORE} and
20850 all score files in the @file{/ftp@@ftp.some-where:/pub/score} directory,
20854 (setq gnus-global-score-files
20855 '("/ftp@@ftp.gnus.org:/pub/larsi/ding/score/soc.motss.SCORE"
20856 "/ftp@@ftp.some-where:/pub/score/"))
20859 @findex gnus-score-search-global-directories
20861 Simple, eh? Directory names must end with a @samp{/}. These
20862 directories are typically scanned only once during each Gnus session.
20863 If you feel the need to manually re-scan the remote directories, you can
20864 use the @code{gnus-score-search-global-directories} command.
20866 Note that, at present, using this option will slow down group entry
20867 somewhat. (That is---a lot.)
20869 If you want to start maintaining score files for other people to use,
20870 just put your score file up for anonymous ftp and announce it to the
20871 world. Become a retro-moderator! Participate in the retro-moderator
20872 wars sure to ensue, where retro-moderators battle it out for the
20873 sympathy of the people, luring them to use their score files on false
20874 premises! Yay! The net is saved!
20876 Here are some tips for the would-be retro-moderator, off the top of my
20882 Articles heavily crossposted are probably junk.
20884 To lower a single inappropriate article, lower by @code{Message-ID}.
20886 Particularly brilliant authors can be raised on a permanent basis.
20888 Authors that repeatedly post off-charter for the group can safely be
20889 lowered out of existence.
20891 Set the @code{mark} and @code{expunge} atoms to obliterate the nastiest
20892 articles completely.
20895 Use expiring score entries to keep the size of the file down. You
20896 should probably have a long expiry period, though, as some sites keep
20897 old articles for a long time.
20900 @dots{} I wonder whether other newsreaders will support global score files
20901 in the future. @emph{Snicker}. Yup, any day now, newsreaders like Blue
20902 Wave, xrn and 1stReader are bound to implement scoring. Should we start
20903 holding our breath yet?
20907 @section Kill Files
20910 Gnus still supports those pesky old kill files. In fact, the kill file
20911 entries can now be expiring, which is something I wrote before Daniel
20912 Quinlan thought of doing score files, so I've left the code in there.
20914 In short, kill processing is a lot slower (and I do mean @emph{a lot})
20915 than score processing, so it might be a good idea to rewrite your kill
20916 files into score files.
20918 Anyway, a kill file is a normal @code{emacs-lisp} file. You can put any
20919 forms into this file, which means that you can use kill files as some
20920 sort of primitive hook function to be run on group entry, even though
20921 that isn't a very good idea.
20923 Normal kill files look like this:
20926 (gnus-kill "From" "Lars Ingebrigtsen")
20927 (gnus-kill "Subject" "ding")
20931 This will mark every article written by me as read, and remove the
20932 marked articles from the summary buffer. Very useful, you'll agree.
20934 Other programs use a totally different kill file syntax. If Gnus
20935 encounters what looks like a @code{rn} kill file, it will take a stab at
20938 Two summary functions for editing a @sc{gnus} kill file:
20943 @kindex M-k (Summary)
20944 @findex gnus-summary-edit-local-kill
20945 Edit this group's kill file (@code{gnus-summary-edit-local-kill}).
20948 @kindex M-K (Summary)
20949 @findex gnus-summary-edit-global-kill
20950 Edit the general kill file (@code{gnus-summary-edit-global-kill}).
20953 Two group mode functions for editing the kill files:
20958 @kindex M-k (Group)
20959 @findex gnus-group-edit-local-kill
20960 Edit this group's kill file (@code{gnus-group-edit-local-kill}).
20963 @kindex M-K (Group)
20964 @findex gnus-group-edit-global-kill
20965 Edit the general kill file (@code{gnus-group-edit-global-kill}).
20968 Kill file variables:
20971 @item gnus-kill-file-name
20972 @vindex gnus-kill-file-name
20973 A kill file for the group @samp{soc.motss} is normally called
20974 @file{soc.motss.KILL}. The suffix appended to the group name to get
20975 this file name is detailed by the @code{gnus-kill-file-name} variable.
20976 The ``global'' kill file (not in the score file sense of ``global'', of
20977 course) is just called @file{KILL}.
20979 @vindex gnus-kill-save-kill-file
20980 @item gnus-kill-save-kill-file
20981 If this variable is non-@code{nil}, Gnus will save the
20982 kill file after processing, which is necessary if you use expiring
20985 @item gnus-apply-kill-hook
20986 @vindex gnus-apply-kill-hook
20987 @findex gnus-apply-kill-file-unless-scored
20988 @findex gnus-apply-kill-file
20989 A hook called to apply kill files to a group. It is
20990 @code{(gnus-apply-kill-file)} by default. If you want to ignore the
20991 kill file if you have a score file for the same group, you can set this
20992 hook to @code{(gnus-apply-kill-file-unless-scored)}. If you don't want
20993 kill files to be processed, you should set this variable to @code{nil}.
20995 @item gnus-kill-file-mode-hook
20996 @vindex gnus-kill-file-mode-hook
20997 A hook called in kill-file mode buffers.
21002 @node Converting Kill Files
21003 @section Converting Kill Files
21005 @cindex converting kill files
21007 If you have loads of old kill files, you may want to convert them into
21008 score files. If they are ``regular'', you can use
21009 the @file{gnus-kill-to-score.el} package; if not, you'll have to do it
21012 The kill to score conversion package isn't included in Gnus by default.
21013 You can fetch it from
21014 @uref{http://www.stud.ifi.uio.no/~larsi/ding-various/gnus-kill-to-score.el}.
21016 If your old kill files are very complex---if they contain more
21017 non-@code{gnus-kill} forms than not, you'll have to convert them by
21018 hand. Or just let them be as they are. Gnus will still use them as
21022 @node Advanced Scoring
21023 @section Advanced Scoring
21025 Scoring on Subjects and From headers is nice enough, but what if you're
21026 really interested in what a person has to say only when she's talking
21027 about a particular subject? Or what if you really don't want to
21028 read what person A has to say when she's following up to person B, but
21029 want to read what she says when she's following up to person C?
21031 By using advanced scoring rules you may create arbitrarily complex
21035 * Advanced Scoring Syntax:: A definition.
21036 * Advanced Scoring Examples:: What they look like.
21037 * Advanced Scoring Tips:: Getting the most out of it.
21041 @node Advanced Scoring Syntax
21042 @subsection Advanced Scoring Syntax
21044 Ordinary scoring rules have a string as the first element in the rule.
21045 Advanced scoring rules have a list as the first element. The second
21046 element is the score to be applied if the first element evaluated to a
21047 non-@code{nil} value.
21049 These lists may consist of three logical operators, one redirection
21050 operator, and various match operators.
21057 This logical operator will evaluate each of its arguments until it finds
21058 one that evaluates to @code{false}, and then it'll stop. If all arguments
21059 evaluate to @code{true} values, then this operator will return
21064 This logical operator will evaluate each of its arguments until it finds
21065 one that evaluates to @code{true}. If no arguments are @code{true},
21066 then this operator will return @code{false}.
21071 This logical operator only takes a single argument. It returns the
21072 logical negation of the value of its argument.
21076 There is an @dfn{indirection operator} that will make its arguments
21077 apply to the ancestors of the current article being scored. For
21078 instance, @code{1-} will make score rules apply to the parent of the
21079 current article. @code{2-} will make score rules apply to the
21080 grandparent of the current article. Alternatively, you can write
21081 @code{^^}, where the number of @code{^}s (carets) says how far back into
21082 the ancestry you want to go.
21084 Finally, we have the match operators. These are the ones that do the
21085 real work. Match operators are header name strings followed by a match
21086 and a match type. A typical match operator looks like @samp{("from"
21087 "Lars Ingebrigtsen" s)}. The header names are the same as when using
21088 simple scoring, and the match types are also the same.
21091 @node Advanced Scoring Examples
21092 @subsection Advanced Scoring Examples
21094 Please note that the following examples are score file rules. To
21095 make a complete score file from them, surround them with another pair
21098 Let's say you want to increase the score of articles written by Lars
21099 when he's talking about Gnus:
21104 ("from" "Lars Ingebrigtsen")
21105 ("subject" "Gnus"))
21112 When he writes long articles, he sometimes has something nice to say:
21116 ("from" "Lars Ingebrigtsen")
21123 However, when he responds to things written by Reig Eigil Logge, you
21124 really don't want to read what he's written:
21128 ("from" "Lars Ingebrigtsen")
21129 (1- ("from" "Reig Eigir Logge")))
21133 Everybody that follows up Redmondo when he writes about disappearing
21134 socks should have their scores raised, but only when they talk about
21135 white socks. However, when Lars talks about socks, it's usually not
21142 ("from" "redmondo@@.*no" r)
21143 ("body" "disappearing.*socks" t)))
21144 (! ("from" "Lars Ingebrigtsen"))
21145 ("body" "white.*socks"))
21149 Suppose you're reading a high volume group and you're only interested
21150 in replies. The plan is to score down all articles that don't have
21151 subject that begin with "Re:", "Fw:" or "Fwd:" and then score up all
21152 parents of articles that have subjects that begin with reply marks.
21155 ((! ("subject" "re:\\|fwd?:" r))
21157 ((1- ("subject" "re:\\|fwd?:" r))
21161 The possibilities are endless.
21163 @node Advanced Scoring Tips
21164 @subsection Advanced Scoring Tips
21166 The @code{&} and @code{|} logical operators do short-circuit logic.
21167 That is, they stop processing their arguments when it's clear what the
21168 result of the operation will be. For instance, if one of the arguments
21169 of an @code{&} evaluates to @code{false}, there's no point in evaluating
21170 the rest of the arguments. This means that you should put slow matches
21171 (@samp{body}, @samp{header}) last and quick matches (@samp{from},
21172 @samp{subject}) first.
21174 The indirection arguments (@code{1-} and so on) will make their
21175 arguments work on previous generations of the thread. If you say
21186 Then that means ``score on the from header of the grandparent of the
21187 current article''. An indirection is quite fast, but it's better to say:
21193 ("subject" "Gnus")))
21200 (1- ("from" "Lars"))
21201 (1- ("subject" "Gnus")))
21206 @section Score Decays
21207 @cindex score decays
21210 You may find that your scores have a tendency to grow without
21211 bounds, especially if you're using adaptive scoring. If scores get too
21212 big, they lose all meaning---they simply max out and it's difficult to
21213 use them in any sensible way.
21215 @vindex gnus-decay-scores
21216 @findex gnus-decay-score
21217 @vindex gnus-decay-score-function
21218 Gnus provides a mechanism for decaying scores to help with this problem.
21219 When score files are loaded and @code{gnus-decay-scores} is
21220 non-@code{nil}, Gnus will run the score files through the decaying
21221 mechanism thereby lowering the scores of all non-permanent score rules.
21222 If @code{gnus-decay-scores} is a regexp, only score files matching this
21223 regexp are treated. E.g. you may set it to @samp{\\.ADAPT\\'} if only
21224 @emph{adaptive} score files should be decayed. The decay itself if
21225 performed by the @code{gnus-decay-score-function} function, which is
21226 @code{gnus-decay-score} by default. Here's the definition of that
21230 (defun gnus-decay-score (score)
21231 "Decay SCORE according to `gnus-score-decay-constant'
21232 and `gnus-score-decay-scale'."
21234 (* (if (< score 0) -1 1)
21236 (max gnus-score-decay-constant
21238 gnus-score-decay-scale)))))))
21239 (if (and (featurep 'xemacs)
21240 ;; XEmacs' floor can handle only the floating point
21241 ;; number below the half of the maximum integer.
21242 (> (abs n) (lsh -1 -2)))
21244 (car (split-string (number-to-string n) "\\.")))
21248 @vindex gnus-score-decay-scale
21249 @vindex gnus-score-decay-constant
21250 @code{gnus-score-decay-constant} is 3 by default and
21251 @code{gnus-score-decay-scale} is 0.05. This should cause the following:
21255 Scores between -3 and 3 will be set to 0 when this function is called.
21258 Scores with magnitudes between 3 and 60 will be shrunk by 3.
21261 Scores with magnitudes greater than 60 will be shrunk by 5% of the
21265 If you don't like this decay function, write your own. It is called
21266 with the score to be decayed as its only parameter, and it should return
21267 the new score, which should be an integer.
21269 Gnus will try to decay scores once a day. If you haven't run Gnus for
21270 four days, Gnus will decay the scores four times, for instance.
21275 @include message.texi
21276 @chapter Emacs MIME
21277 @include emacs-mime.texi
21279 @include sieve.texi
21291 * Process/Prefix:: A convention used by many treatment commands.
21292 * Interactive:: Making Gnus ask you many questions.
21293 * Symbolic Prefixes:: How to supply some Gnus functions with options.
21294 * Formatting Variables:: You can specify what buffers should look like.
21295 * Window Layout:: Configuring the Gnus buffer windows.
21296 * Faces and Fonts:: How to change how faces look.
21297 * Compilation:: How to speed Gnus up.
21298 * Mode Lines:: Displaying information in the mode lines.
21299 * Highlighting and Menus:: Making buffers look all nice and cozy.
21300 * Buttons:: Get tendinitis in ten easy steps!
21301 * Daemons:: Gnus can do things behind your back.
21302 * NoCeM:: How to avoid spam and other fatty foods.
21303 * Undo:: Some actions can be undone.
21304 * Predicate Specifiers:: Specifying predicates.
21305 * Moderation:: What to do if you're a moderator.
21306 * Fetching a Group:: Starting Gnus just to read a group.
21307 * Image Enhancements:: Modern versions of Emacs/XEmacs can display images.
21308 * Fuzzy Matching:: What's the big fuzz?
21309 * Thwarting Email Spam:: A how-to on avoiding unsolicited commercial email.
21310 * Other modes:: Interaction with other modes.
21311 * Various Various:: Things that are really various.
21315 @node Process/Prefix
21316 @section Process/Prefix
21317 @cindex process/prefix convention
21319 Many functions, among them functions for moving, decoding and saving
21320 articles, use what is known as the @dfn{Process/Prefix convention}.
21322 This is a method for figuring out what articles the user wants the
21323 command to be performed on.
21327 If the numeric prefix is N, perform the operation on the next N
21328 articles, starting with the current one. If the numeric prefix is
21329 negative, perform the operation on the previous N articles, starting
21330 with the current one.
21332 @vindex transient-mark-mode
21333 If @code{transient-mark-mode} in non-@code{nil} and the region is
21334 active, all articles in the region will be worked upon.
21336 If there is no numeric prefix, but some articles are marked with the
21337 process mark, perform the operation on the articles marked with
21340 If there is neither a numeric prefix nor any articles marked with the
21341 process mark, just perform the operation on the current article.
21343 Quite simple, really, but it needs to be made clear so that surprises
21346 Commands that react to the process mark will push the current list of
21347 process marked articles onto a stack and will then clear all process
21348 marked articles. You can restore the previous configuration with the
21349 @kbd{M P y} command (@pxref{Setting Process Marks}).
21351 @vindex gnus-summary-goto-unread
21352 One thing that seems to shock & horrify lots of people is that, for
21353 instance, @kbd{3 d} does exactly the same as @kbd{d} @kbd{d} @kbd{d}.
21354 Since each @kbd{d} (which marks the current article as read) by default
21355 goes to the next unread article after marking, this means that @kbd{3 d}
21356 will mark the next three unread articles as read, no matter what the
21357 summary buffer looks like. Set @code{gnus-summary-goto-unread} to
21358 @code{nil} for a more straightforward action.
21360 Many commands do not use the process/prefix convention. All commands
21361 that do explicitly say so in this manual. To apply the process/prefix
21362 convention to commands that do not use it, you can use the @kbd{M-&}
21363 command. For instance, to mark all the articles in the group as
21364 expirable, you could say @kbd{M P b M-& E}.
21368 @section Interactive
21369 @cindex interaction
21373 @item gnus-novice-user
21374 @vindex gnus-novice-user
21375 If this variable is non-@code{nil}, you are either a newcomer to the
21376 World of Usenet, or you are very cautious, which is a nice thing to be,
21377 really. You will be given questions of the type ``Are you sure you want
21378 to do this?'' before doing anything dangerous. This is @code{t} by
21381 @item gnus-expert-user
21382 @vindex gnus-expert-user
21383 If this variable is non-@code{nil}, you will seldom be asked any
21384 questions by Gnus. It will simply assume you know what you're doing, no
21385 matter how strange.
21387 @item gnus-interactive-catchup
21388 @vindex gnus-interactive-catchup
21389 Require confirmation before catching up a group if non-@code{nil}. It
21390 is @code{t} by default.
21392 @item gnus-interactive-exit
21393 @vindex gnus-interactive-exit
21394 Require confirmation before exiting Gnus. This variable is @code{t} by
21399 @node Symbolic Prefixes
21400 @section Symbolic Prefixes
21401 @cindex symbolic prefixes
21403 Quite a lot of Emacs commands react to the (numeric) prefix. For
21404 instance, @kbd{C-u 4 C-f} moves point four characters forward, and
21405 @kbd{C-u 9 0 0 I s s p} adds a permanent @code{Subject} substring score
21406 rule of 900 to the current article.
21408 This is all nice and well, but what if you want to give a command some
21409 additional information? Well, what most commands do is interpret the
21410 ``raw'' prefix in some special way. @kbd{C-u 0 C-x C-s} means that one
21411 doesn't want a backup file to be created when saving the current buffer,
21412 for instance. But what if you want to save without making a backup
21413 file, and you want Emacs to flash lights and play a nice tune at the
21414 same time? You can't, and you're probably perfectly happy that way.
21416 @kindex M-i (Summary)
21417 @findex gnus-symbolic-argument
21418 I'm not, so I've added a second prefix---the @dfn{symbolic prefix}. The
21419 prefix key is @kbd{M-i} (@code{gnus-symbolic-argument}), and the next
21420 character typed in is the value. You can stack as many @kbd{M-i}
21421 prefixes as you want. @kbd{M-i a C-M-u} means ``feed the @kbd{C-M-u}
21422 command the symbolic prefix @code{a}''. @kbd{M-i a M-i b C-M-u} means
21423 ``feed the @kbd{C-M-u} command the symbolic prefixes @code{a} and
21424 @code{b}''. You get the drift.
21426 Typing in symbolic prefixes to commands that don't accept them doesn't
21427 hurt, but it doesn't do any good either. Currently not many Gnus
21428 functions make use of the symbolic prefix.
21430 If you're interested in how Gnus implements this, @pxref{Extended
21434 @node Formatting Variables
21435 @section Formatting Variables
21436 @cindex formatting variables
21438 Throughout this manual you've probably noticed lots of variables called
21439 things like @code{gnus-group-line-format} and
21440 @code{gnus-summary-mode-line-format}. These control how Gnus is to
21441 output lines in the various buffers. There's quite a lot of them.
21442 Fortunately, they all use the same syntax, so there's not that much to
21445 Here's an example format spec (from the group buffer): @samp{%M%S%5y:
21446 %(%g%)\n}. We see that it is indeed extremely ugly, and that there are
21447 lots of percentages everywhere.
21450 * Formatting Basics:: A formatting variable is basically a format string.
21451 * Mode Line Formatting:: Some rules about mode line formatting variables.
21452 * Advanced Formatting:: Modifying output in various ways.
21453 * User-Defined Specs:: Having Gnus call your own functions.
21454 * Formatting Fonts:: Making the formatting look colorful and nice.
21455 * Positioning Point:: Moving point to a position after an operation.
21456 * Tabulation:: Tabulating your output.
21457 * Wide Characters:: Dealing with wide characters.
21460 Currently Gnus uses the following formatting variables:
21461 @code{gnus-group-line-format}, @code{gnus-summary-line-format},
21462 @code{gnus-server-line-format}, @code{gnus-topic-line-format},
21463 @code{gnus-group-mode-line-format},
21464 @code{gnus-summary-mode-line-format},
21465 @code{gnus-article-mode-line-format},
21466 @code{gnus-server-mode-line-format}, and
21467 @code{gnus-summary-pick-line-format}.
21469 All these format variables can also be arbitrary elisp forms. In that
21470 case, they will be @code{eval}ed to insert the required lines.
21472 @kindex M-x gnus-update-format
21473 @findex gnus-update-format
21474 Gnus includes a command to help you while creating your own format
21475 specs. @kbd{M-x gnus-update-format} will @code{eval} the current form,
21476 update the spec in question and pop you to a buffer where you can
21477 examine the resulting Lisp code to be run to generate the line.
21481 @node Formatting Basics
21482 @subsection Formatting Basics
21484 Each @samp{%} element will be replaced by some string or other when the
21485 buffer in question is generated. @samp{%5y} means ``insert the @samp{y}
21486 spec, and pad with spaces to get a 5-character field''.
21488 As with normal C and Emacs Lisp formatting strings, the numerical
21489 modifier between the @samp{%} and the formatting type character will
21490 @dfn{pad} the output so that it is always at least that long.
21491 @samp{%5y} will make the field always (at least) five characters wide by
21492 padding with spaces to the left. If you say @samp{%-5y}, it will pad to
21495 You may also wish to limit the length of the field to protect against
21496 particularly wide values. For that you can say @samp{%4,6y}, which
21497 means that the field will never be more than 6 characters wide and never
21498 less than 4 characters wide.
21500 Also Gnus supports some extended format specifications, such as
21501 @samp{%&user-date;}.
21504 @node Mode Line Formatting
21505 @subsection Mode Line Formatting
21507 Mode line formatting variables (e.g.,
21508 @code{gnus-summary-mode-line-format}) follow the same rules as other,
21509 buffer line oriented formatting variables (@pxref{Formatting Basics})
21510 with the following two differences:
21515 There must be no newline (@samp{\n}) at the end.
21518 The special @samp{%%b} spec can be used to display the buffer name.
21519 Well, it's no spec at all, really---@samp{%%} is just a way to quote
21520 @samp{%} to allow it to pass through the formatting machinery unmangled,
21521 so that Emacs receives @samp{%b}, which is something the Emacs mode line
21522 display interprets to mean ``show the buffer name''. For a full list of
21523 mode line specs Emacs understands, see the documentation of the
21524 @code{mode-line-format} variable.
21529 @node Advanced Formatting
21530 @subsection Advanced Formatting
21532 It is frequently useful to post-process the fields in some way.
21533 Padding, limiting, cutting off parts and suppressing certain values can
21534 be achieved by using @dfn{tilde modifiers}. A typical tilde spec might
21535 look like @samp{%~(cut 3)~(ignore "0")y}.
21537 These are the valid modifiers:
21542 Pad the field to the left with spaces until it reaches the required
21546 Pad the field to the right with spaces until it reaches the required
21551 Cut off characters from the left until it reaches the specified length.
21554 Cut off characters from the right until it reaches the specified
21559 Cut off the specified number of characters from the left.
21562 Cut off the specified number of characters from the right.
21565 Return an empty string if the field is equal to the specified value.
21568 Use the specified form as the field value when the @samp{@@} spec is
21574 "~(form (current-time-string))@@"
21579 Let's take an example. The @samp{%o} spec in the summary mode lines
21580 will return a date in compact ISO8601 format---@samp{19960809T230410}.
21581 This is quite a mouthful, so we want to shave off the century number and
21582 the time, leaving us with a six-character date. That would be
21583 @samp{%~(cut-left 2)~(max-right 6)~(pad 6)o}. (Cutting is done before
21584 maxing, and we need the padding to ensure that the date is never less
21585 than 6 characters to make it look nice in columns.)
21587 Ignoring is done first; then cutting; then maxing; and then as the very
21588 last operation, padding.
21590 If you use lots of these advanced thingies, you'll find that Gnus gets
21591 quite slow. This can be helped enormously by running @kbd{M-x
21592 gnus-compile} when you are satisfied with the look of your lines.
21593 @xref{Compilation}.
21596 @node User-Defined Specs
21597 @subsection User-Defined Specs
21599 All the specs allow for inserting user defined specifiers---@samp{u}.
21600 The next character in the format string should be a letter. Gnus
21601 will call the function @code{gnus-user-format-function-}@samp{X}, where
21602 @samp{X} is the letter following @samp{%u}. The function will be passed
21603 a single parameter---what the parameter means depends on what buffer
21604 it's being called from. The function should return a string, which will
21605 be inserted into the buffer just like information from any other
21606 specifier. This function may also be called with dummy values, so it
21607 should protect against that.
21609 Also Gnus supports extended user-defined specs, such as @samp{%u&foo;}.
21610 Gnus will call the function @code{gnus-user-format-function-}@samp{foo}.
21612 You can also use tilde modifiers (@pxref{Advanced Formatting} to achieve
21613 much the same without defining new functions. Here's an example:
21614 @samp{%~(form (count-lines (point-min) (point)))@@}. The form
21615 given here will be evaluated to yield the current line number, and then
21619 @node Formatting Fonts
21620 @subsection Formatting Fonts
21622 There are specs for highlighting, and these are shared by all the format
21623 variables. Text inside the @samp{%(} and @samp{%)} specifiers will get
21624 the special @code{mouse-face} property set, which means that it will be
21625 highlighted (with @code{gnus-mouse-face}) when you put the mouse pointer
21628 Text inside the @samp{%@{} and @samp{%@}} specifiers will have their
21629 normal faces set using @code{gnus-face-0}, which is @code{bold} by
21630 default. If you say @samp{%1@{}, you'll get @code{gnus-face-1} instead,
21631 and so on. Create as many faces as you wish. The same goes for the
21632 @code{mouse-face} specs---you can say @samp{%3(hello%)} to have
21633 @samp{hello} mouse-highlighted with @code{gnus-mouse-face-3}.
21635 Text inside the @samp{%<<} and @samp{%>>} specifiers will get the
21636 special @code{balloon-help} property set to
21637 @code{gnus-balloon-face-0}. If you say @samp{%1<<}, you'll get
21638 @code{gnus-balloon-face-1} and so on. The @code{gnus-balloon-face-*}
21639 variables should be either strings or symbols naming functions that
21640 return a string. When the mouse passes over text with this property
21641 set, a balloon window will appear and display the string. Please
21642 refer to @ref{Tooltips, ,Tooltips, emacs, The Emacs Manual},
21643 (in GNU Emacs) or the doc string of @code{balloon-help-mode} (in
21644 XEmacs) for more information on this. (For technical reasons, the
21645 guillemets have been approximated as @samp{<<} and @samp{>>} in this
21648 Here's an alternative recipe for the group buffer:
21651 ;; @r{Create three face types.}
21652 (setq gnus-face-1 'bold)
21653 (setq gnus-face-3 'italic)
21655 ;; @r{We want the article count to be in}
21656 ;; @r{a bold and green face. So we create}
21657 ;; @r{a new face called @code{my-green-bold}.}
21658 (copy-face 'bold 'my-green-bold)
21659 ;; @r{Set the color.}
21660 (set-face-foreground 'my-green-bold "ForestGreen")
21661 (setq gnus-face-2 'my-green-bold)
21663 ;; @r{Set the new & fancy format.}
21664 (setq gnus-group-line-format
21665 "%M%S%3@{%5y%@}%2[:%] %(%1@{%g%@}%)\n")
21668 I'm sure you'll be able to use this scheme to create totally unreadable
21669 and extremely vulgar displays. Have fun!
21671 Note that the @samp{%(} specs (and friends) do not make any sense on the
21672 mode-line variables.
21674 @node Positioning Point
21675 @subsection Positioning Point
21677 Gnus usually moves point to a pre-defined place on each line in most
21678 buffers. By default, point move to the first colon character on the
21679 line. You can customize this behavior in three different ways.
21681 You can move the colon character to somewhere else on the line.
21683 @findex gnus-goto-colon
21684 You can redefine the function that moves the point to the colon. The
21685 function is called @code{gnus-goto-colon}.
21687 But perhaps the most convenient way to deal with this, if you don't want
21688 to have a colon in your line, is to use the @samp{%*} specifier. If you
21689 put a @samp{%*} somewhere in your format line definition, Gnus will
21694 @subsection Tabulation
21696 You can usually line up your displays by padding and cutting your
21697 strings. However, when combining various strings of different size, it
21698 can often be more convenient to just output the strings, and then worry
21699 about lining up the following text afterwards.
21701 To do that, Gnus supplies tabulator specs---@samp{%=}. There are two
21702 different types---@dfn{hard tabulators} and @dfn{soft tabulators}.
21704 @samp{%50=} will insert space characters to pad the line up to column
21705 50. If the text is already past column 50, nothing will be inserted.
21706 This is the soft tabulator.
21708 @samp{%-50=} will insert space characters to pad the line up to column
21709 50. If the text is already past column 50, the excess text past column
21710 50 will be removed. This is the hard tabulator.
21713 @node Wide Characters
21714 @subsection Wide Characters
21716 Fixed width fonts in most countries have characters of the same width.
21717 Some countries, however, use Latin characters mixed with wider
21718 characters---most notable East Asian countries.
21720 The problem is that when formatting, Gnus assumes that if a string is 10
21721 characters wide, it'll be 10 Latin characters wide on the screen. In
21722 these countries, that's not true.
21724 @vindex gnus-use-correct-string-widths
21725 To help fix this, you can set @code{gnus-use-correct-string-widths} to
21726 @code{t}. This makes buffer generation slower, but the results will be
21727 prettier. The default value under XEmacs is @code{t} but @code{nil}
21731 @node Window Layout
21732 @section Window Layout
21733 @cindex window layout
21735 No, there's nothing here about X, so be quiet.
21737 @vindex gnus-use-full-window
21738 If @code{gnus-use-full-window} non-@code{nil}, Gnus will delete all
21739 other windows and occupy the entire Emacs screen by itself. It is
21740 @code{t} by default.
21742 Setting this variable to @code{nil} kinda works, but there are
21743 glitches. Use at your own peril.
21745 @vindex gnus-buffer-configuration
21746 @code{gnus-buffer-configuration} describes how much space each Gnus
21747 buffer should be given. Here's an excerpt of this variable:
21750 ((group (vertical 1.0 (group 1.0 point)
21751 (if gnus-carpal (group-carpal 4))))
21752 (article (vertical 1.0 (summary 0.25 point)
21756 This is an alist. The @dfn{key} is a symbol that names some action or
21757 other. For instance, when displaying the group buffer, the window
21758 configuration function will use @code{group} as the key. A full list of
21759 possible names is listed below.
21761 The @dfn{value} (i.e., the @dfn{split}) says how much space each buffer
21762 should occupy. To take the @code{article} split as an example -
21765 (article (vertical 1.0 (summary 0.25 point)
21769 This @dfn{split} says that the summary buffer should occupy 25% of upper
21770 half of the screen, and that it is placed over the article buffer. As
21771 you may have noticed, 100% + 25% is actually 125% (yup, I saw y'all
21772 reaching for that calculator there). However, the special number
21773 @code{1.0} is used to signal that this buffer should soak up all the
21774 rest of the space available after the rest of the buffers have taken
21775 whatever they need. There should be only one buffer with the @code{1.0}
21776 size spec per split.
21778 Point will be put in the buffer that has the optional third element
21779 @code{point}. In a @code{frame} split, the last subsplit having a leaf
21780 split where the tag @code{frame-focus} is a member (i.e. is the third or
21781 fourth element in the list, depending on whether the @code{point} tag is
21782 present) gets focus.
21784 Here's a more complicated example:
21787 (article (vertical 1.0 (group 4)
21788 (summary 0.25 point)
21789 (if gnus-carpal (summary-carpal 4))
21793 If the size spec is an integer instead of a floating point number,
21794 then that number will be used to say how many lines a buffer should
21795 occupy, not a percentage.
21797 If the @dfn{split} looks like something that can be @code{eval}ed (to be
21798 precise---if the @code{car} of the split is a function or a subr), this
21799 split will be @code{eval}ed. If the result is non-@code{nil}, it will
21800 be used as a split. This means that there will be three buffers if
21801 @code{gnus-carpal} is @code{nil}, and four buffers if @code{gnus-carpal}
21804 Not complicated enough for you? Well, try this on for size:
21807 (article (horizontal 1.0
21812 (summary 0.25 point)
21817 Whoops. Two buffers with the mystery 100% tag. And what's that
21818 @code{horizontal} thingie?
21820 If the first element in one of the split is @code{horizontal}, Gnus will
21821 split the window horizontally, giving you two windows side-by-side.
21822 Inside each of these strips you may carry on all you like in the normal
21823 fashion. The number following @code{horizontal} says what percentage of
21824 the screen is to be given to this strip.
21826 For each split, there @emph{must} be one element that has the 100% tag.
21827 The splitting is never accurate, and this buffer will eat any leftover
21828 lines from the splits.
21830 To be slightly more formal, here's a definition of what a valid split
21835 split = frame | horizontal | vertical | buffer | form
21836 frame = "(frame " size *split ")"
21837 horizontal = "(horizontal " size *split ")"
21838 vertical = "(vertical " size *split ")"
21839 buffer = "(" buf-name " " size *[ "point" ] *[ "frame-focus"] ")"
21840 size = number | frame-params
21841 buf-name = group | article | summary ...
21845 The limitations are that the @code{frame} split can only appear as the
21846 top-level split. @var{form} should be an Emacs Lisp form that should
21847 return a valid split. We see that each split is fully recursive, and
21848 may contain any number of @code{vertical} and @code{horizontal} splits.
21850 @vindex gnus-window-min-width
21851 @vindex gnus-window-min-height
21852 @cindex window height
21853 @cindex window width
21854 Finding the right sizes can be a bit complicated. No window may be less
21855 than @code{gnus-window-min-height} (default 1) characters high, and all
21856 windows must be at least @code{gnus-window-min-width} (default 1)
21857 characters wide. Gnus will try to enforce this before applying the
21858 splits. If you want to use the normal Emacs window width/height limit,
21859 you can just set these two variables to @code{nil}.
21861 If you're not familiar with Emacs terminology, @code{horizontal} and
21862 @code{vertical} splits may work the opposite way of what you'd expect.
21863 Windows inside a @code{horizontal} split are shown side-by-side, and
21864 windows within a @code{vertical} split are shown above each other.
21866 @findex gnus-configure-frame
21867 If you want to experiment with window placement, a good tip is to call
21868 @code{gnus-configure-frame} directly with a split. This is the function
21869 that does all the real work when splitting buffers. Below is a pretty
21870 nonsensical configuration with 5 windows; two for the group buffer and
21871 three for the article buffer. (I said it was nonsensical.) If you
21872 @code{eval} the statement below, you can get an idea of how that would
21873 look straight away, without going through the normal Gnus channels.
21874 Play with it until you're satisfied, and then use
21875 @code{gnus-add-configuration} to add your new creation to the buffer
21876 configuration list.
21879 (gnus-configure-frame
21883 (article 0.3 point))
21891 You might want to have several frames as well. No prob---just use the
21892 @code{frame} split:
21895 (gnus-configure-frame
21898 (summary 0.25 point frame-focus)
21900 (vertical ((height . 5) (width . 15)
21901 (user-position . t)
21902 (left . -1) (top . 1))
21907 This split will result in the familiar summary/article window
21908 configuration in the first (or ``main'') frame, while a small additional
21909 frame will be created where picons will be shown. As you can see,
21910 instead of the normal @code{1.0} top-level spec, each additional split
21911 should have a frame parameter alist as the size spec.
21912 @xref{Frame Parameters, , Frame Parameters, elisp, The GNU Emacs Lisp
21913 Reference Manual}. Under XEmacs, a frame property list will be
21914 accepted, too---for instance, @code{(height 5 width 15 left -1 top 1)}
21916 The list of all possible keys for @code{gnus-buffer-configuration} can
21917 be found in its default value.
21919 Note that the @code{message} key is used for both
21920 @code{gnus-group-mail} and @code{gnus-summary-mail-other-window}. If
21921 it is desirable to distinguish between the two, something like this
21925 (message (horizontal 1.0
21926 (vertical 1.0 (message 1.0 point))
21928 (if (buffer-live-p gnus-summary-buffer)
21933 One common desire for a multiple frame split is to have a separate frame
21934 for composing mail and news while leaving the original frame intact. To
21935 accomplish that, something like the following can be done:
21940 (if (not (buffer-live-p gnus-summary-buffer))
21941 (car (cdr (assoc 'group gnus-buffer-configuration)))
21942 (car (cdr (assoc 'summary gnus-buffer-configuration))))
21943 (vertical ((user-position . t) (top . 1) (left . 1)
21944 (name . "Message"))
21945 (message 1.0 point))))
21948 @findex gnus-add-configuration
21949 Since the @code{gnus-buffer-configuration} variable is so long and
21950 complicated, there's a function you can use to ease changing the config
21951 of a single setting: @code{gnus-add-configuration}. If, for instance,
21952 you want to change the @code{article} setting, you could say:
21955 (gnus-add-configuration
21956 '(article (vertical 1.0
21958 (summary .25 point)
21962 You'd typically stick these @code{gnus-add-configuration} calls in your
21963 @file{~/.gnus.el} file or in some startup hook---they should be run after
21964 Gnus has been loaded.
21966 @vindex gnus-always-force-window-configuration
21967 If all windows mentioned in the configuration are already visible, Gnus
21968 won't change the window configuration. If you always want to force the
21969 ``right'' window configuration, you can set
21970 @code{gnus-always-force-window-configuration} to non-@code{nil}.
21972 If you're using tree displays (@pxref{Tree Display}), and the tree
21973 window is displayed vertically next to another window, you may also want
21974 to fiddle with @code{gnus-tree-minimize-window} to avoid having the
21977 @subsection Example Window Configurations
21981 Narrow left hand side occupied by group buffer. Right hand side split
21982 between summary buffer (top one-sixth) and article buffer (bottom).
21997 (gnus-add-configuration
22000 (vertical 25 (group 1.0))
22002 (summary 0.16 point)
22005 (gnus-add-configuration
22008 (vertical 25 (group 1.0))
22009 (vertical 1.0 (summary 1.0 point)))))
22015 @node Faces and Fonts
22016 @section Faces and Fonts
22021 Fiddling with fonts and faces used to be very difficult, but these days
22022 it is very simple. You simply say @kbd{M-x customize-face}, pick out
22023 the face you want to alter, and alter it via the standard Customize
22028 @section Compilation
22029 @cindex compilation
22030 @cindex byte-compilation
22032 @findex gnus-compile
22034 Remember all those line format specification variables?
22035 @code{gnus-summary-line-format}, @code{gnus-group-line-format}, and so
22036 on. Now, Gnus will of course heed whatever these variables are, but,
22037 unfortunately, changing them will mean a quite significant slow-down.
22038 (The default values of these variables have byte-compiled functions
22039 associated with them, while the user-generated versions do not, of
22042 To help with this, you can run @kbd{M-x gnus-compile} after you've
22043 fiddled around with the variables and feel that you're (kind of)
22044 satisfied. This will result in the new specs being byte-compiled, and
22045 you'll get top speed again. Gnus will save these compiled specs in the
22046 @file{.newsrc.eld} file. (User-defined functions aren't compiled by
22047 this function, though---you should compile them yourself by sticking
22048 them into the @file{~/.gnus.el} file and byte-compiling that file.)
22052 @section Mode Lines
22055 @vindex gnus-updated-mode-lines
22056 @code{gnus-updated-mode-lines} says what buffers should keep their mode
22057 lines updated. It is a list of symbols. Supported symbols include
22058 @code{group}, @code{article}, @code{summary}, @code{server},
22059 @code{browse}, and @code{tree}. If the corresponding symbol is present,
22060 Gnus will keep that mode line updated with information that may be
22061 pertinent. If this variable is @code{nil}, screen refresh may be
22064 @cindex display-time
22066 @vindex gnus-mode-non-string-length
22067 By default, Gnus displays information on the current article in the mode
22068 lines of the summary and article buffers. The information Gnus wishes
22069 to display (e.g. the subject of the article) is often longer than the
22070 mode lines, and therefore have to be cut off at some point. The
22071 @code{gnus-mode-non-string-length} variable says how long the other
22072 elements on the line is (i.e., the non-info part). If you put
22073 additional elements on the mode line (e.g. a clock), you should modify
22076 @c Hook written by Francesco Potorti` <pot@cnuce.cnr.it>
22078 (add-hook 'display-time-hook
22079 (lambda () (setq gnus-mode-non-string-length
22081 (if line-number-mode 5 0)
22082 (if column-number-mode 4 0)
22083 (length display-time-string)))))
22086 If this variable is @code{nil} (which is the default), the mode line
22087 strings won't be chopped off, and they won't be padded either. Note
22088 that the default is unlikely to be desirable, as even the percentage
22089 complete in the buffer may be crowded off the mode line; the user should
22090 configure this variable appropriately for her configuration.
22093 @node Highlighting and Menus
22094 @section Highlighting and Menus
22096 @cindex highlighting
22099 @vindex gnus-visual
22100 The @code{gnus-visual} variable controls most of the Gnus-prettifying
22101 aspects. If @code{nil}, Gnus won't attempt to create menus or use fancy
22102 colors or fonts. This will also inhibit loading the @file{gnus-vis.el}
22105 This variable can be a list of visual properties that are enabled. The
22106 following elements are valid, and are all included by default:
22109 @item group-highlight
22110 Do highlights in the group buffer.
22111 @item summary-highlight
22112 Do highlights in the summary buffer.
22113 @item article-highlight
22114 Do highlights in the article buffer.
22116 Turn on highlighting in all buffers.
22118 Create menus in the group buffer.
22120 Create menus in the summary buffers.
22122 Create menus in the article buffer.
22124 Create menus in the browse buffer.
22126 Create menus in the server buffer.
22128 Create menus in the score buffers.
22130 Create menus in all buffers.
22133 So if you only want highlighting in the article buffer and menus in all
22134 buffers, you could say something like:
22137 (setq gnus-visual '(article-highlight menu))
22140 If you want highlighting only and no menus whatsoever, you'd say:
22143 (setq gnus-visual '(highlight))
22146 If @code{gnus-visual} is @code{t}, highlighting and menus will be used
22147 in all Gnus buffers.
22149 Other general variables that influence the look of all buffers include:
22152 @item gnus-mouse-face
22153 @vindex gnus-mouse-face
22154 This is the face (i.e., font) used for mouse highlighting in Gnus. No
22155 mouse highlights will be done if @code{gnus-visual} is @code{nil}.
22159 There are hooks associated with the creation of all the different menus:
22163 @item gnus-article-menu-hook
22164 @vindex gnus-article-menu-hook
22165 Hook called after creating the article mode menu.
22167 @item gnus-group-menu-hook
22168 @vindex gnus-group-menu-hook
22169 Hook called after creating the group mode menu.
22171 @item gnus-summary-menu-hook
22172 @vindex gnus-summary-menu-hook
22173 Hook called after creating the summary mode menu.
22175 @item gnus-server-menu-hook
22176 @vindex gnus-server-menu-hook
22177 Hook called after creating the server mode menu.
22179 @item gnus-browse-menu-hook
22180 @vindex gnus-browse-menu-hook
22181 Hook called after creating the browse mode menu.
22183 @item gnus-score-menu-hook
22184 @vindex gnus-score-menu-hook
22185 Hook called after creating the score mode menu.
22196 Those new-fangled @dfn{mouse} contraptions is very popular with the
22197 young, hep kids who don't want to learn the proper way to do things
22198 these days. Why, I remember way back in the summer of '89, when I was
22199 using Emacs on a Tops 20 system. Three hundred users on one single
22200 machine, and every user was running Simula compilers. Bah!
22204 @vindex gnus-carpal
22205 Well, you can make Gnus display bufferfuls of buttons you can click to
22206 do anything by setting @code{gnus-carpal} to @code{t}. Pretty simple,
22207 really. Tell the chiropractor I sent you.
22212 @item gnus-carpal-mode-hook
22213 @vindex gnus-carpal-mode-hook
22214 Hook run in all carpal mode buffers.
22216 @item gnus-carpal-button-face
22217 @vindex gnus-carpal-button-face
22218 Face used on buttons.
22220 @item gnus-carpal-header-face
22221 @vindex gnus-carpal-header-face
22222 Face used on carpal buffer headers.
22224 @item gnus-carpal-group-buffer-buttons
22225 @vindex gnus-carpal-group-buffer-buttons
22226 Buttons in the group buffer.
22228 @item gnus-carpal-summary-buffer-buttons
22229 @vindex gnus-carpal-summary-buffer-buttons
22230 Buttons in the summary buffer.
22232 @item gnus-carpal-server-buffer-buttons
22233 @vindex gnus-carpal-server-buffer-buttons
22234 Buttons in the server buffer.
22236 @item gnus-carpal-browse-buffer-buttons
22237 @vindex gnus-carpal-browse-buffer-buttons
22238 Buttons in the browse buffer.
22241 All the @code{buttons} variables are lists. The elements in these list
22242 are either cons cells where the @code{car} contains a text to be displayed and
22243 the @code{cdr} contains a function symbol, or a simple string.
22251 Gnus, being larger than any program ever written (allegedly), does lots
22252 of strange stuff that you may wish to have done while you're not
22253 present. For instance, you may want it to check for new mail once in a
22254 while. Or you may want it to close down all connections to all servers
22255 when you leave Emacs idle. And stuff like that.
22257 Gnus will let you do stuff like that by defining various
22258 @dfn{handlers}. Each handler consists of three elements: A
22259 @var{function}, a @var{time}, and an @var{idle} parameter.
22261 Here's an example of a handler that closes connections when Emacs has
22262 been idle for thirty minutes:
22265 (gnus-demon-close-connections nil 30)
22268 Here's a handler that scans for @acronym{PGP} headers every hour when
22272 (gnus-demon-scan-pgp 60 t)
22275 This @var{time} parameter and that @var{idle} parameter work together
22276 in a strange, but wonderful fashion. Basically, if @var{idle} is
22277 @code{nil}, then the function will be called every @var{time} minutes.
22279 If @var{idle} is @code{t}, then the function will be called after
22280 @var{time} minutes only if Emacs is idle. So if Emacs is never idle,
22281 the function will never be called. But once Emacs goes idle, the
22282 function will be called every @var{time} minutes.
22284 If @var{idle} is a number and @var{time} is a number, the function will
22285 be called every @var{time} minutes only when Emacs has been idle for
22286 @var{idle} minutes.
22288 If @var{idle} is a number and @var{time} is @code{nil}, the function
22289 will be called once every time Emacs has been idle for @var{idle}
22292 And if @var{time} is a string, it should look like @samp{07:31}, and
22293 the function will then be called once every day somewhere near that
22294 time. Modified by the @var{idle} parameter, of course.
22296 @vindex gnus-demon-timestep
22297 (When I say ``minute'' here, I really mean @code{gnus-demon-timestep}
22298 seconds. This is 60 by default. If you change that variable,
22299 all the timings in the handlers will be affected.)
22301 So, if you want to add a handler, you could put something like this in
22302 your @file{~/.gnus.el} file:
22304 @findex gnus-demon-add-handler
22306 (gnus-demon-add-handler 'gnus-demon-close-connections 30 t)
22309 @findex gnus-demon-add-nocem
22310 @findex gnus-demon-add-scanmail
22311 @findex gnus-demon-add-rescan
22312 @findex gnus-demon-add-scan-timestamps
22313 @findex gnus-demon-add-disconnection
22314 Some ready-made functions to do this have been created:
22315 @code{gnus-demon-add-nocem}, @code{gnus-demon-add-disconnection},
22316 @code{gnus-demon-add-nntp-close-connection},
22317 @code{gnus-demon-add-scan-timestamps}, @code{gnus-demon-add-rescan}, and
22318 @code{gnus-demon-add-scanmail}. Just put those functions in your
22319 @file{~/.gnus.el} if you want those abilities.
22321 @findex gnus-demon-init
22322 @findex gnus-demon-cancel
22323 @vindex gnus-demon-handlers
22324 If you add handlers to @code{gnus-demon-handlers} directly, you should
22325 run @code{gnus-demon-init} to make the changes take hold. To cancel all
22326 daemons, you can use the @code{gnus-demon-cancel} function.
22328 Note that adding daemons can be pretty naughty if you over do it. Adding
22329 functions that scan all news and mail from all servers every two seconds
22330 is a sure-fire way of getting booted off any respectable system. So
22339 @dfn{Spamming} is posting the same article lots and lots of times.
22340 Spamming is bad. Spamming is evil.
22342 Spamming is usually canceled within a day or so by various anti-spamming
22343 agencies. These agencies usually also send out @dfn{NoCeM} messages.
22344 NoCeM is pronounced ``no see-'em'', and means what the name
22345 implies---these are messages that make the offending articles, like, go
22348 What use are these NoCeM messages if the articles are canceled anyway?
22349 Some sites do not honor cancel messages and some sites just honor cancels
22350 from a select few people. Then you may wish to make use of the NoCeM
22351 messages, which are distributed in the @samp{alt.nocem.misc} newsgroup.
22353 Gnus can read and parse the messages in this group automatically, and
22354 this will make spam disappear.
22356 There are some variables to customize, of course:
22359 @item gnus-use-nocem
22360 @vindex gnus-use-nocem
22361 Set this variable to @code{t} to set the ball rolling. It is @code{nil}
22364 You can also set this variable to a positive number as a group level.
22365 In that case, Gnus scans NoCeM messages when checking new news if this
22366 value is not exceeding a group level that you specify as the prefix
22367 argument to some commands, e.g. @code{gnus},
22368 @code{gnus-group-get-new-news}, etc. Otherwise, Gnus does not scan
22369 NoCeM messages if you specify a group level to those commands. For
22370 example, if you use 1 or 2 on the mail groups and the levels on the news
22371 groups remain the default, 3 is the best choice.
22373 @item gnus-nocem-groups
22374 @vindex gnus-nocem-groups
22375 Gnus will look for NoCeM messages in the groups in this list. The
22378 ("news.lists.filters" "news.admin.net-abuse.bulletins"
22379 "alt.nocem.misc" "news.admin.net-abuse.announce")
22382 @item gnus-nocem-issuers
22383 @vindex gnus-nocem-issuers
22384 There are many people issuing NoCeM messages. This list says what
22385 people you want to listen to. The default is
22387 ("Automoose-1" "clewis@@ferret.ocunix.on.ca"
22388 "cosmo.roadkill" "SpamHippo" "hweede@@snafu.de")
22390 fine, upstanding citizens all of them.
22392 Known despammers that you can put in this list are listed at@*
22393 @uref{http://www.xs4all.nl/~rosalind/nocemreg/nocemreg.html}.
22395 You do not have to heed NoCeM messages from all these people---just the
22396 ones you want to listen to. You also don't have to accept all NoCeM
22397 messages from the people you like. Each NoCeM message has a @dfn{type}
22398 header that gives the message a (more or less, usually less) rigorous
22399 definition. Common types are @samp{spam}, @samp{spew}, @samp{mmf},
22400 @samp{binary}, and @samp{troll}. To specify this, you have to use
22401 @code{(@var{issuer} @var{conditions} @dots{})} elements in the list.
22402 Each condition is either a string (which is a regexp that matches types
22403 you want to use) or a list on the form @code{(not @var{string})}, where
22404 @var{string} is a regexp that matches types you don't want to use.
22406 For instance, if you want all NoCeM messages from Chris Lewis except his
22407 @samp{troll} messages, you'd say:
22410 ("clewis@@ferret.ocunix.on.ca" ".*" (not "troll"))
22413 On the other hand, if you just want nothing but his @samp{spam} and
22414 @samp{spew} messages, you'd say:
22417 ("clewis@@ferret.ocunix.on.ca" (not ".*") "spew" "spam")
22420 The specs are applied left-to-right.
22423 @item gnus-nocem-verifyer
22424 @vindex gnus-nocem-verifyer
22426 This should be a function for verifying that the NoCeM issuer is who she
22427 says she is. The default is @code{pgg-verify}, which returns
22428 non-@code{nil} if the verification is successful, otherwise (including
22429 the case the NoCeM message was not signed) returns @code{nil}. If this
22430 is too slow and you don't care for verification (which may be dangerous),
22431 you can set this variable to @code{nil}.
22433 Formerly the default was @code{mc-verify}, which is a Mailcrypt
22434 function. While you can still use it, you can change it into
22435 @code{pgg-verify} running with GnuPG if you are willing to add the
22436 @acronym{PGP} public keys to GnuPG's keyring.
22438 @item gnus-nocem-directory
22439 @vindex gnus-nocem-directory
22440 This is where Gnus will store its NoCeM cache files. The default is@*
22441 @file{~/News/NoCeM/}.
22443 @item gnus-nocem-expiry-wait
22444 @vindex gnus-nocem-expiry-wait
22445 The number of days before removing old NoCeM entries from the cache.
22446 The default is 15. If you make it shorter Gnus will be faster, but you
22447 might then see old spam.
22449 @item gnus-nocem-check-from
22450 @vindex gnus-nocem-check-from
22451 Non-@code{nil} means check for valid issuers in message bodies.
22452 Otherwise don't bother fetching articles unless their author matches a
22453 valid issuer; that is much faster if you are selective about the
22456 @item gnus-nocem-check-article-limit
22457 @vindex gnus-nocem-check-article-limit
22458 If non-@code{nil}, the maximum number of articles to check in any NoCeM
22459 group. NoCeM groups can be huge and very slow to process.
22463 Using NoCeM could potentially be a memory hog. If you have many living
22464 (i. e., subscribed or unsubscribed groups), your Emacs process will grow
22465 big. If this is a problem, you should kill off all (or most) of your
22466 unsubscribed groups (@pxref{Subscription Commands}).
22473 It is very useful to be able to undo actions one has done. In normal
22474 Emacs buffers, it's easy enough---you just push the @code{undo} button.
22475 In Gnus buffers, however, it isn't that simple.
22477 The things Gnus displays in its buffer is of no value whatsoever to
22478 Gnus---it's all just data designed to look nice to the user.
22479 Killing a group in the group buffer with @kbd{C-k} makes the line
22480 disappear, but that's just a side-effect of the real action---the
22481 removal of the group in question from the internal Gnus structures.
22482 Undoing something like that can't be done by the normal Emacs
22483 @code{undo} function.
22485 Gnus tries to remedy this somewhat by keeping track of what the user
22486 does and coming up with actions that would reverse the actions the user
22487 takes. When the user then presses the @code{undo} key, Gnus will run
22488 the code to reverse the previous action, or the previous actions.
22489 However, not all actions are easily reversible, so Gnus currently offers
22490 a few key functions to be undoable. These include killing groups,
22491 yanking groups, and changing the list of read articles of groups.
22492 That's it, really. More functions may be added in the future, but each
22493 added function means an increase in data to be stored, so Gnus will
22494 never be totally undoable.
22496 @findex gnus-undo-mode
22497 @vindex gnus-use-undo
22499 The undoability is provided by the @code{gnus-undo-mode} minor mode. It
22500 is used if @code{gnus-use-undo} is non-@code{nil}, which is the
22501 default. The @kbd{C-M-_} key performs the @code{gnus-undo}
22502 command, which should feel kinda like the normal Emacs @code{undo}
22506 @node Predicate Specifiers
22507 @section Predicate Specifiers
22508 @cindex predicate specifiers
22510 Some Gnus variables are @dfn{predicate specifiers}. This is a special
22511 form that allows flexible specification of predicates without having
22512 to type all that much.
22514 These specifiers are lists consisting of functions, symbols and lists.
22519 (or gnus-article-unseen-p
22520 gnus-article-unread-p)
22523 The available symbols are @code{or}, @code{and} and @code{not}. The
22524 functions all take one parameter.
22526 @findex gnus-make-predicate
22527 Internally, Gnus calls @code{gnus-make-predicate} on these specifiers
22528 to create a function that can be called. This input parameter to this
22529 function will be passed along to all the functions in the predicate
22534 @section Moderation
22537 If you are a moderator, you can use the @file{gnus-mdrtn.el} package.
22538 It is not included in the standard Gnus package. Write a mail to
22539 @samp{larsi@@gnus.org} and state what group you moderate, and you'll
22542 The moderation package is implemented as a minor mode for summary
22546 (add-hook 'gnus-summary-mode-hook 'gnus-moderate)
22549 in your @file{~/.gnus.el} file.
22551 If you are the moderator of @samp{rec.zoofle}, this is how it's
22556 You split your incoming mail by matching on
22557 @samp{Newsgroups:.*rec.zoofle}, which will put all the to-be-posted
22558 articles in some mail group---for instance, @samp{nnml:rec.zoofle}.
22561 You enter that group once in a while and post articles using the @kbd{e}
22562 (edit-and-post) or @kbd{s} (just send unedited) commands.
22565 If, while reading the @samp{rec.zoofle} newsgroup, you happen upon some
22566 articles that weren't approved by you, you can cancel them with the
22570 To use moderation mode in these two groups, say:
22573 (setq gnus-moderated-list
22574 "^nnml:rec.zoofle$\\|^rec.zoofle$")
22578 @node Fetching a Group
22579 @section Fetching a Group
22580 @cindex fetching a group
22582 @findex gnus-fetch-group
22583 It is sometimes convenient to be able to just say ``I want to read this
22584 group and I don't care whether Gnus has been started or not''. This is
22585 perhaps more useful for people who write code than for users, but the
22586 command @code{gnus-fetch-group} provides this functionality in any case.
22587 It takes the group name as a parameter.
22590 @node Image Enhancements
22591 @section Image Enhancements
22593 XEmacs, as well as Emacs 21@footnote{Emacs 21 on MS Windows doesn't
22594 support images yet.}, is able to display pictures and stuff, so Gnus has
22595 taken advantage of that.
22598 * X-Face:: Display a funky, teensy black-and-white image.
22599 * Face:: Display a funkier, teensier colored image.
22600 * Smileys:: Show all those happy faces the way they were meant to be shown.
22601 * Picons:: How to display pictures of what you're reading.
22602 * XVarious:: Other XEmacsy Gnusey variables.
22610 @code{X-Face} headers describe a 48x48 pixel black-and-white (1 bit
22611 depth) image that's supposed to represent the author of the message.
22612 It seems to be supported by an ever-growing number of mail and news
22616 @findex gnus-article-display-x-face
22617 @vindex gnus-article-x-face-command
22618 @vindex gnus-article-x-face-too-ugly
22626 Viewing an @code{X-Face} header either requires an Emacs that has
22627 @samp{compface} support (which most XEmacs versions has), or that you
22628 have suitable conversion or display programs installed. If your Emacs
22629 has image support the default action is to display the face before the
22630 @code{From} header. If there's no native @code{X-Face} support, Gnus
22631 will try to convert the @code{X-Face} header using external programs
22632 from the @code{pbmplus} package and friends. For XEmacs it's faster if
22633 XEmacs has been compiled with @code{X-Face} support. The default action
22634 under Emacs without image support is to fork off the @code{display}
22637 On a GNU/Linux system, the @code{display} program is from the
22638 ImageMagick package. For external conversion programs look for packages
22639 with names like @code{netpbm}, @code{libgr-progs} and @code{compface}.
22641 The variable that controls this is the
22642 @code{gnus-article-x-face-command} variable. If this variable is a
22643 string, this string will be executed in a sub-shell. If it is a
22644 function, this function will be called with the face as the argument.
22645 If the @code{gnus-article-x-face-too-ugly} (which is a regexp) matches
22646 the @code{From} header, the face will not be shown.
22648 (Note: @code{x-face} is used in the variable/function names, not
22656 @vindex gnus-x-face
22657 Face to show X-Face. The colors from this face are used as the
22658 foreground and background colors of the displayed X-Faces. The
22659 default colors are black and white.
22661 @item gnus-face-properties-alist
22662 @vindex gnus-face-properties-alist
22663 Alist of image types and properties applied to Face (@pxref{Face}) and
22664 X-Face images. The default value is @code{((pbm . (:face gnus-x-face))
22665 (png . nil))} for Emacs or @code{((xface . (:face gnus-x-face)))} for
22666 XEmacs. Here are examples:
22669 ;; Specify the altitude of Face and X-Face images in the From header.
22670 (setq gnus-face-properties-alist
22671 '((pbm . (:face gnus-x-face :ascent 80))
22672 (png . (:ascent 80))))
22674 ;; Show Face and X-Face images as pressed buttons.
22675 (setq gnus-face-properties-alist
22676 '((pbm . (:face gnus-x-face :relief -2))
22677 (png . (:relief -2))))
22680 @pxref{Image Descriptors, ,Image Descriptors, elisp, The Emacs Lisp
22681 Reference Manual} for the valid properties for various image types.
22682 Currently, @code{pbm} is used for X-Face images and @code{png} is used
22683 for Face images in Emacs. Only the @code{:face} property is effective
22684 on the @code{xface} image type in XEmacs if it is built with the
22685 @samp{libcompface} library.
22688 If you use posting styles, you can use an @code{x-face-file} entry in
22689 @code{gnus-posting-styles}, @xref{Posting Styles}. If you don't, Gnus
22690 provides a few convenience functions and variables to allow easier
22691 insertion of X-Face headers in outgoing messages. You also need the
22692 above mentioned ImageMagick, netpbm or other image conversion packages
22693 (depending the values of the variables below) for these functions.
22695 @findex gnus-random-x-face
22696 @vindex gnus-convert-pbm-to-x-face-command
22697 @vindex gnus-x-face-directory
22698 @code{gnus-random-x-face} goes through all the @samp{pbm} files in
22699 @code{gnus-x-face-directory} and picks one at random, and then
22700 converts it to the X-Face format by using the
22701 @code{gnus-convert-pbm-to-x-face-command} shell command. The
22702 @samp{pbm} files should be 48x48 pixels big. It returns the X-Face
22703 header data as a string.
22705 @findex gnus-insert-random-x-face-header
22706 @code{gnus-insert-random-x-face-header} calls
22707 @code{gnus-random-x-face} and inserts a @samp{X-Face} header with the
22708 randomly generated data.
22710 @findex gnus-x-face-from-file
22711 @vindex gnus-convert-image-to-x-face-command
22712 @code{gnus-x-face-from-file} takes a GIF file as the parameter, and then
22713 converts the file to X-Face format by using the
22714 @code{gnus-convert-image-to-x-face-command} shell command.
22716 Here's how you would typically use the first function. Put something
22717 like the following in your @file{~/.gnus.el} file:
22720 (setq message-required-news-headers
22721 (nconc message-required-news-headers
22722 (list '(X-Face . gnus-random-x-face))))
22725 Using the last function would be something like this:
22728 (setq message-required-news-headers
22729 (nconc message-required-news-headers
22730 (list '(X-Face . (lambda ()
22731 (gnus-x-face-from-file
22732 "~/My-face.gif"))))))
22740 @c #### FIXME: faces and x-faces' implementations should really be harmonized.
22742 @code{Face} headers are essentially a funkier version of @code{X-Face}
22743 ones. They describe a 48x48 pixel colored image that's supposed to
22744 represent the author of the message.
22747 @findex gnus-article-display-face
22748 The contents of a @code{Face} header must be a base64 encoded PNG image.
22749 See @uref{http://quimby.gnus.org/circus/face/} for the precise
22752 The @code{gnus-face-properties-alist} variable affects the appearance of
22753 displayed Face images. @xref{X-Face}.
22755 Viewing an @code{Face} header requires an Emacs that is able to display
22758 @c (if (featurep 'xemacs)
22760 @c (image-type-available-p 'png))
22762 Gnus provides a few convenience functions and variables to allow
22763 easier insertion of Face headers in outgoing messages.
22765 @findex gnus-convert-png-to-face
22766 @code{gnus-convert-png-to-face} takes a 48x48 PNG image, no longer than
22767 726 bytes long, and converts it to a face.
22769 @findex gnus-face-from-file
22770 @vindex gnus-convert-image-to-face-command
22771 @code{gnus-face-from-file} takes a JPEG file as the parameter, and then
22772 converts the file to Face format by using the
22773 @code{gnus-convert-image-to-face-command} shell command.
22775 Here's how you would typically use this function. Put something like the
22776 following in your @file{~/.gnus.el} file:
22779 (setq message-required-news-headers
22780 (nconc message-required-news-headers
22781 (list '(Face . (lambda ()
22782 (gnus-face-from-file "~/face.jpg"))))))
22787 @subsection Smileys
22792 \gnusfig{-3cm}{0.5cm}{\epsfig{figure=ps/BigFace,height=20cm}}
22797 @dfn{Smiley} is a package separate from Gnus, but since Gnus is
22798 currently the only package that uses Smiley, it is documented here.
22800 In short---to use Smiley in Gnus, put the following in your
22801 @file{~/.gnus.el} file:
22804 (setq gnus-treat-display-smileys t)
22807 Smiley maps text smiley faces---@samp{:-)}, @samp{8-)}, @samp{:-(} and
22808 the like---to pictures and displays those instead of the text smiley
22809 faces. The conversion is controlled by a list of regexps that matches
22810 text and maps that to file names.
22812 @vindex smiley-regexp-alist
22813 The alist used is specified by the @code{smiley-regexp-alist}
22814 variable. The first item in each element is the regexp to be matched;
22815 the second element is the regexp match group that is to be replaced by
22816 the picture; and the third element is the name of the file to be
22819 The following variables customize where Smiley will look for these
22824 @item smiley-data-directory
22825 @vindex smiley-data-directory
22826 Where Smiley will look for smiley faces files.
22828 @item gnus-smiley-file-types
22829 @vindex gnus-smiley-file-types
22830 List of suffixes on smiley file names to try.
22844 So@dots{} You want to slow down your news reader even more! This is a
22845 good way to do so. It's also a great way to impress people staring
22846 over your shoulder as you read news.
22848 What are Picons? To quote directly from the Picons Web site:
22857 @dfn{Picons} is short for ``personal icons''. They're small,
22858 constrained images used to represent users and domains on the net,
22859 organized into databases so that the appropriate image for a given
22860 e-mail address can be found. Besides users and domains, there are picon
22861 databases for Usenet newsgroups and weather forecasts. The picons are
22862 in either monochrome @code{XBM} format or color @code{XPM} and
22863 @code{GIF} formats.
22866 @vindex gnus-picon-databases
22867 For instructions on obtaining and installing the picons databases,
22868 point your Web browser at
22869 @uref{http://www.cs.indiana.edu/picons/ftp/index.html}.
22871 If you are using Debian GNU/Linux, saying @samp{apt-get install
22872 picons.*} will install the picons where Gnus can find them.
22874 To enable displaying picons, simply make sure that
22875 @code{gnus-picon-databases} points to the directory containing the
22878 @vindex gnus-picon-style
22879 The variable @code{gnus-picon-style} controls how picons are displayed.
22880 If @code{inline}, the textual representation is replaced. If
22881 @code{right}, picons are added right to the textual representation.
22883 The following variables offer control over where things are located.
22887 @item gnus-picon-databases
22888 @vindex gnus-picon-databases
22889 The location of the picons database. This is a list of directories
22890 containing the @file{news}, @file{domains}, @file{users} (and so on)
22891 subdirectories. Defaults to @code{("/usr/lib/picon"
22892 "/usr/local/faces")}.
22894 @item gnus-picon-news-directories
22895 @vindex gnus-picon-news-directories
22896 List of subdirectories to search in @code{gnus-picon-databases} for
22897 newsgroups faces. @code{("news")} is the default.
22899 @item gnus-picon-user-directories
22900 @vindex gnus-picon-user-directories
22901 List of subdirectories to search in @code{gnus-picon-databases} for user
22902 faces. @code{("users" "usenix" "local" "misc")} is the default.
22904 @item gnus-picon-domain-directories
22905 @vindex gnus-picon-domain-directories
22906 List of subdirectories to search in @code{gnus-picon-databases} for
22907 domain name faces. Defaults to @code{("domains")}. Some people may
22908 want to add @samp{"unknown"} to this list.
22910 @item gnus-picon-file-types
22911 @vindex gnus-picon-file-types
22912 Ordered list of suffixes on picon file names to try. Defaults to
22913 @code{("xpm" "gif" "xbm")} minus those not built-in your Emacs.
22919 @subsection Various XEmacs Variables
22922 @item gnus-xmas-glyph-directory
22923 @vindex gnus-xmas-glyph-directory
22924 This is where Gnus will look for pictures. Gnus will normally
22925 auto-detect this directory, but you may set it manually if you have an
22926 unusual directory structure.
22928 @item gnus-xmas-modeline-glyph
22929 @vindex gnus-xmas-modeline-glyph
22930 A glyph displayed in all Gnus mode lines. It is a tiny gnu head by
22935 @subsubsection Toolbar
22939 @item gnus-use-toolbar
22940 @vindex gnus-use-toolbar
22941 This variable specifies the position to display the toolbar. If
22942 @code{nil}, don't display toolbars. If it is non-@code{nil}, it should
22943 be one of the symbols @code{default}, @code{top}, @code{bottom},
22944 @code{right}, and @code{left}. @code{default} means to use the default
22945 toolbar, the rest mean to display the toolbar on the place which those
22946 names show. The default is @code{default}.
22948 @item gnus-toolbar-thickness
22949 @vindex gnus-toolbar-thickness
22950 Cons of the height and the width specifying the thickness of a toolbar.
22951 The height is used for the toolbar displayed on the top or the bottom,
22952 the width is used for the toolbar displayed on the right or the left.
22953 The default is that of the default toolbar.
22955 @item gnus-group-toolbar
22956 @vindex gnus-group-toolbar
22957 The toolbar in the group buffer.
22959 @item gnus-summary-toolbar
22960 @vindex gnus-summary-toolbar
22961 The toolbar in the summary buffer.
22963 @item gnus-summary-mail-toolbar
22964 @vindex gnus-summary-mail-toolbar
22965 The toolbar in the summary buffer of mail groups.
22976 @node Fuzzy Matching
22977 @section Fuzzy Matching
22978 @cindex fuzzy matching
22980 Gnus provides @dfn{fuzzy matching} of @code{Subject} lines when doing
22981 things like scoring, thread gathering and thread comparison.
22983 As opposed to regular expression matching, fuzzy matching is very fuzzy.
22984 It's so fuzzy that there's not even a definition of what @dfn{fuzziness}
22985 means, and the implementation has changed over time.
22987 Basically, it tries to remove all noise from lines before comparing.
22988 @samp{Re: }, parenthetical remarks, white space, and so on, are filtered
22989 out of the strings before comparing the results. This often leads to
22990 adequate results---even when faced with strings generated by text
22991 manglers masquerading as newsreaders.
22994 @node Thwarting Email Spam
22995 @section Thwarting Email Spam
22999 @cindex unsolicited commercial email
23001 In these last days of the Usenet, commercial vultures are hanging about
23002 and grepping through news like crazy to find email addresses they can
23003 foist off their scams and products to. As a reaction to this, many
23004 people have started putting nonsense addresses into their @code{From}
23005 lines. I think this is counterproductive---it makes it difficult for
23006 people to send you legitimate mail in response to things you write, as
23007 well as making it difficult to see who wrote what. This rewriting may
23008 perhaps be a bigger menace than the unsolicited commercial email itself
23011 The biggest problem I have with email spam is that it comes in under
23012 false pretenses. I press @kbd{g} and Gnus merrily informs me that I
23013 have 10 new emails. I say ``Golly gee! Happy is me!'' and select the
23014 mail group, only to find two pyramid schemes, seven advertisements
23015 (``New! Miracle tonic for growing full, lustrous hair on your toes!'')
23016 and one mail asking me to repent and find some god.
23018 This is annoying. Here's what you can do about it.
23021 * The problem of spam:: Some background, and some solutions
23022 * Anti-Spam Basics:: Simple steps to reduce the amount of spam.
23023 * SpamAssassin:: How to use external anti-spam tools.
23024 * Hashcash:: Reduce spam by burning CPU time.
23025 * Filtering Spam Using The Spam ELisp Package::
23026 * Filtering Spam Using Statistics with spam-stat::
23029 @node The problem of spam
23030 @subsection The problem of spam
23032 @cindex spam filtering approaches
23033 @cindex filtering approaches, spam
23035 @cindex unsolicited commercial email
23037 First, some background on spam.
23039 If you have access to e-mail, you are familiar with spam (technically
23040 termed @acronym{UCE}, Unsolicited Commercial E-mail). Simply put, it
23041 exists because e-mail delivery is very cheap compared to paper mail,
23042 so only a very small percentage of people need to respond to an UCE to
23043 make it worthwhile to the advertiser. Ironically, one of the most
23044 common spams is the one offering a database of e-mail addresses for
23045 further spamming. Senders of spam are usually called @emph{spammers},
23046 but terms like @emph{vermin}, @emph{scum}, @emph{sociopaths}, and
23047 @emph{morons} are in common use as well.
23049 Spam comes from a wide variety of sources. It is simply impossible to
23050 dispose of all spam without discarding useful messages. A good
23051 example is the TMDA system, which requires senders
23052 unknown to you to confirm themselves as legitimate senders before
23053 their e-mail can reach you. Without getting into the technical side
23054 of TMDA, a downside is clearly that e-mail from legitimate sources may
23055 be discarded if those sources can't or won't confirm themselves
23056 through the TMDA system. Another problem with TMDA is that it
23057 requires its users to have a basic understanding of e-mail delivery
23060 The simplest approach to filtering spam is filtering, at the mail
23061 server or when you sort through incoming mail. If you get 200 spam
23062 messages per day from @samp{random-address@@vmadmin.com}, you block
23063 @samp{vmadmin.com}. If you get 200 messages about @samp{VIAGRA}, you
23064 discard all messages with @samp{VIAGRA} in the message. If you get
23065 lots of spam from Bulgaria, for example, you try to filter all mail
23066 from Bulgarian IPs.
23068 This, unfortunately, is a great way to discard legitimate e-mail. The
23069 risks of blocking a whole country (Bulgaria, Norway, Nigeria, China,
23070 etc.) or even a continent (Asia, Africa, Europe, etc.) from contacting
23071 you should be obvious, so don't do it if you have the choice.
23073 In another instance, the very informative and useful RISKS digest has
23074 been blocked by overzealous mail filters because it @strong{contained}
23075 words that were common in spam messages. Nevertheless, in isolated
23076 cases, with great care, direct filtering of mail can be useful.
23078 Another approach to filtering e-mail is the distributed spam
23079 processing, for instance DCC implements such a system. In essence,
23080 @var{N} systems around the world agree that a machine @var{X} in
23081 Ghana, Estonia, or California is sending out spam e-mail, and these
23082 @var{N} systems enter @var{X} or the spam e-mail from @var{X} into a
23083 database. The criteria for spam detection vary---it may be the number
23084 of messages sent, the content of the messages, and so on. When a user
23085 of the distributed processing system wants to find out if a message is
23086 spam, he consults one of those @var{N} systems.
23088 Distributed spam processing works very well against spammers that send
23089 a large number of messages at once, but it requires the user to set up
23090 fairly complicated checks. There are commercial and free distributed
23091 spam processing systems. Distributed spam processing has its risks as
23092 well. For instance legitimate e-mail senders have been accused of
23093 sending spam, and their web sites and mailing lists have been shut
23094 down for some time because of the incident.
23096 The statistical approach to spam filtering is also popular. It is
23097 based on a statistical analysis of previous spam messages. Usually
23098 the analysis is a simple word frequency count, with perhaps pairs of
23099 words or 3-word combinations thrown into the mix. Statistical
23100 analysis of spam works very well in most of the cases, but it can
23101 classify legitimate e-mail as spam in some cases. It takes time to
23102 run the analysis, the full message must be analyzed, and the user has
23103 to store the database of spam analyses. Statistical analysis on the
23104 server is gaining popularity. This has the advantage of letting the
23105 user Just Read Mail, but has the disadvantage that it's harder to tell
23106 the server that it has misclassified mail.
23108 Fighting spam is not easy, no matter what anyone says. There is no
23109 magic switch that will distinguish Viagra ads from Mom's e-mails.
23110 Even people are having a hard time telling spam apart from non-spam,
23111 because spammers are actively looking to fool us into thinking they
23112 are Mom, essentially. Spamming is irritating, irresponsible, and
23113 idiotic behavior from a bunch of people who think the world owes them
23114 a favor. We hope the following sections will help you in fighting the
23117 @node Anti-Spam Basics
23118 @subsection Anti-Spam Basics
23122 @cindex unsolicited commercial email
23124 One way of dealing with spam is having Gnus split out all spam into a
23125 @samp{spam} mail group (@pxref{Splitting Mail}).
23127 First, pick one (1) valid mail address that you can be reached at, and
23128 put it in your @code{From} header of all your news articles. (I've
23129 chosen @samp{larsi@@trym.ifi.uio.no}, but for many addresses on the form
23130 @samp{larsi+usenet@@ifi.uio.no} will be a better choice. Ask your
23131 sysadmin whether your sendmail installation accepts keywords in the local
23132 part of the mail address.)
23135 (setq message-default-news-headers
23136 "From: Lars Magne Ingebrigtsen <larsi@@trym.ifi.uio.no>\n")
23139 Then put the following split rule in @code{nnmail-split-fancy}
23140 (@pxref{Fancy Mail Splitting}):
23144 (to "larsi@@trym.ifi.uio.no"
23145 (| ("subject" "re:.*" "misc")
23146 ("references" ".*@@.*" "misc")
23151 This says that all mail to this address is suspect, but if it has a
23152 @code{Subject} that starts with a @samp{Re:} or has a @code{References}
23153 header, it's probably ok. All the rest goes to the @samp{spam} group.
23154 (This idea probably comes from Tim Pierce.)
23156 In addition, many mail spammers talk directly to your @acronym{SMTP} server
23157 and do not include your email address explicitly in the @code{To}
23158 header. Why they do this is unknown---perhaps it's to thwart this
23159 thwarting scheme? In any case, this is trivial to deal with---you just
23160 put anything not addressed to you in the @samp{spam} group by ending
23161 your fancy split rule in this way:
23166 (to "larsi" "misc")
23170 In my experience, this will sort virtually everything into the right
23171 group. You still have to check the @samp{spam} group from time to time to
23172 check for legitimate mail, though. If you feel like being a good net
23173 citizen, you can even send off complaints to the proper authorities on
23174 each unsolicited commercial email---at your leisure.
23176 This works for me. It allows people an easy way to contact me (they can
23177 just press @kbd{r} in the usual way), and I'm not bothered at all with
23178 spam. It's a win-win situation. Forging @code{From} headers to point
23179 to non-existent domains is yucky, in my opinion.
23181 Be careful with this approach. Spammers are wise to it.
23185 @subsection SpamAssassin, Vipul's Razor, DCC, etc
23186 @cindex SpamAssassin
23187 @cindex Vipul's Razor
23190 The days where the hints in the previous section were sufficient in
23191 avoiding spam are coming to an end. There are many tools out there
23192 that claim to reduce the amount of spam you get. This section could
23193 easily become outdated fast, as new products replace old, but
23194 fortunately most of these tools seem to have similar interfaces. Even
23195 though this section will use SpamAssassin as an example, it should be
23196 easy to adapt it to most other tools.
23198 Note that this section does not involve the @code{spam.el} package,
23199 which is discussed in the next section. If you don't care for all
23200 the features of @code{spam.el}, you can make do with these simple
23203 If the tool you are using is not installed on the mail server, you
23204 need to invoke it yourself. Ideas on how to use the
23205 @code{:postscript} mail source parameter (@pxref{Mail Source
23206 Specifiers}) follow.
23210 '((file :prescript "formail -bs spamassassin < /var/mail/%u")
23214 "mv %t /tmp/foo; formail -bs spamc < /tmp/foo > %t")))
23217 Once you manage to process your incoming spool somehow, thus making
23218 the mail contain e.g.@: a header indicating it is spam, you are ready to
23219 filter it out. Using normal split methods (@pxref{Splitting Mail}):
23222 (setq nnmail-split-methods '(("spam" "^X-Spam-Flag: YES")
23226 Or using fancy split methods (@pxref{Fancy Mail Splitting}):
23229 (setq nnmail-split-methods 'nnmail-split-fancy
23230 nnmail-split-fancy '(| ("X-Spam-Flag" "YES" "spam")
23234 Some people might not like the idea of piping the mail through various
23235 programs using a @code{:prescript} (if some program is buggy, you
23236 might lose all mail). If you are one of them, another solution is to
23237 call the external tools during splitting. Example fancy split method:
23240 (setq nnmail-split-fancy '(| (: kevin-spamassassin)
23242 (defun kevin-spamassassin ()
23246 (if (eq 1 (call-process-region (point-min) (point-max)
23247 "spamc" nil nil nil "-c"))
23251 Note that with the nnimap back end, message bodies will not be
23252 downloaded by default. You need to set
23253 @code{nnimap-split-download-body} to @code{t} to do that
23254 (@pxref{Splitting in IMAP}).
23256 That is about it. As some spam is likely to get through anyway, you
23257 might want to have a nifty function to call when you happen to read
23258 spam. And here is the nifty function:
23261 (defun my-gnus-raze-spam ()
23262 "Submit SPAM to Vipul's Razor, then mark it as expirable."
23264 (gnus-summary-show-raw-article)
23265 (gnus-summary-save-in-pipe "razor-report -f -d")
23266 (gnus-summary-mark-as-expirable 1))
23270 @subsection Hashcash
23273 A novel technique to fight spam is to require senders to do something
23274 costly and demonstrably unique for each message they send. This has
23275 the obvious drawback that you cannot rely on everyone in the world
23276 using this technique, since it is not part of the Internet standards,
23277 but it may be useful in smaller communities.
23279 While the tools in the previous section work well in practice, they
23280 work only because the tools are constantly maintained and updated as
23281 new form of spam appears. This means that a small percentage of spam
23282 will always get through. It also means that somewhere, someone needs
23283 to read lots of spam to update these tools. Hashcash avoids that, but
23284 instead prefers that everyone you contact through e-mail supports the
23285 scheme. You can view the two approaches as pragmatic vs dogmatic.
23286 The approaches have their own advantages and disadvantages, but as
23287 often in the real world, a combination of them is stronger than either
23288 one of them separately.
23291 The ``something costly'' is to burn CPU time, more specifically to
23292 compute a hash collision up to a certain number of bits. The
23293 resulting hashcash cookie is inserted in a @samp{X-Hashcash:} header.
23294 For more details, and for the external application @code{hashcash} you
23295 need to install to use this feature, see
23296 @uref{http://www.hashcash.org/}. Even more information can be found
23297 at @uref{http://www.camram.org/}.
23299 If you wish to generate hashcash for each message you send, you can
23300 customize @code{message-generate-hashcash} (@pxref{Mail Headers, ,Mail
23301 Headers,message, The Message Manual}), as in:
23304 (setq message-generate-hashcash t)
23307 You will need to set up some additional variables as well:
23311 @item hashcash-default-payment
23312 @vindex hashcash-default-payment
23313 This variable indicates the default number of bits the hash collision
23314 should consist of. By default this is 20. Suggested useful values
23317 @item hashcash-payment-alist
23318 @vindex hashcash-payment-alist
23319 Some receivers may require you to spend burn more CPU time than the
23320 default. This variable contains a list of @samp{(@var{addr}
23321 @var{amount})} cells, where @var{addr} is the receiver (email address
23322 or newsgroup) and @var{amount} is the number of bits in the collision
23323 that is needed. It can also contain @samp{(@var{addr} @var{string}
23324 @var{amount})} cells, where the @var{string} is the string to use
23325 (normally the email address or newsgroup name is used).
23327 @item hashcash-path
23328 @vindex hashcash-path
23329 Where the @code{hashcash} binary is installed. This variable should
23330 be automatically set by @code{executable-find}, but if it's @code{nil}
23331 (usually because the @code{hashcash} binary is not in your path)
23332 you'll get a warning when you check hashcash payments and an error
23333 when you generate hashcash payments.
23337 Gnus can verify hashcash cookies, although this can also be done by
23338 hand customized mail filtering scripts. To verify a hashcash cookie
23339 in a message, use the @code{mail-check-payment} function in the
23340 @code{hashcash.el} library. You can also use the @code{spam.el}
23341 package with the @code{spam-use-hashcash} back end to validate hashcash
23342 cookies in incoming mail and filter mail accordingly (@pxref{Anti-spam
23343 Hashcash Payments}).
23345 @node Filtering Spam Using The Spam ELisp Package
23346 @subsection Filtering Spam Using The Spam ELisp Package
23347 @cindex spam filtering
23350 The idea behind @code{spam.el} is to have a control center for spam detection
23351 and filtering in Gnus. To that end, @code{spam.el} does two things: it
23352 filters new mail, and it analyzes mail known to be spam or ham.
23353 @dfn{Ham} is the name used throughout @code{spam.el} to indicate
23356 Make sure you read the section on the @code{spam.el} sequence of
23357 events. See @xref{Spam ELisp Package Sequence of Events}.
23359 @cindex spam-initialize
23360 To use @code{spam.el}, you @strong{must} run the function
23361 @code{spam-initialize} to autoload @file{spam.el} and to install the
23362 @code{spam.el} hooks. There is one exception: if you use the
23363 @code{spam-use-stat} (@pxref{spam-stat spam filtering}) setting, you
23364 should turn it on before @code{spam-initialize}:
23367 (setq spam-use-stat t) ;; if needed
23371 So, what happens when you load @file{spam.el}?
23373 First, some hooks will get installed by @code{spam-initialize}. There
23374 are some hooks for @code{spam-stat} so it can save its databases, and
23375 there are hooks so interesting things will happen when you enter and
23376 leave a group. More on the sequence of events later (@pxref{Spam
23377 ELisp Package Sequence of Events}).
23379 You get the following keyboard commands:
23389 @findex gnus-summary-mark-as-spam
23390 @code{gnus-summary-mark-as-spam}.
23392 Mark current article as spam, showing it with the @samp{$} mark.
23393 Whenever you see a spam article, make sure to mark its summary line
23394 with @kbd{M-d} before leaving the group. This is done automatically
23395 for unread articles in @emph{spam} groups.
23401 @findex spam-bogofilter-score
23402 @code{spam-bogofilter-score}.
23404 You must have Bogofilter installed for that command to work properly.
23410 Also, when you load @file{spam.el}, you will be able to customize its
23411 variables. Try @code{customize-group} on the @samp{spam} variable
23415 * Spam ELisp Package Sequence of Events::
23416 * Spam ELisp Package Filtering of Incoming Mail::
23417 * Spam ELisp Package Global Variables::
23418 * Spam ELisp Package Sorting and Score Display in Summary Buffer::
23419 * Spam ELisp Package Configuration Examples::
23420 * Blacklists and Whitelists::
23421 * BBDB Whitelists::
23422 * Gmane Spam Reporting::
23423 * Anti-spam Hashcash Payments::
23425 * Regular Expressions Header Matching::
23427 * SpamAssassin back end::
23428 * ifile spam filtering::
23429 * spam-stat spam filtering::
23431 * Extending the Spam ELisp package::
23434 @node Spam ELisp Package Sequence of Events
23435 @subsubsection Spam ELisp Package Sequence of Events
23436 @cindex spam filtering
23437 @cindex spam filtering sequence of events
23439 You must read this section to understand how @code{spam.el} works.
23440 Do not skip, speed-read, or glance through this section.
23442 There are two @emph{contact points}, if you will, between
23443 @code{spam.el} and the rest of Gnus: checking new mail for spam, and
23446 Getting new mail in Gnus is done in one of two ways. You can either
23447 split your incoming mail or you can classify new articles as ham or
23448 spam when you enter the group.
23450 Splitting incoming mail is better suited to mail back ends such as
23451 @code{nnml} or @code{nnimap} where new mail appears in a single file
23452 called a @dfn{Spool File}. See @xref{Spam ELisp Package Filtering of
23455 @vindex gnus-spam-autodetect
23456 @vindex gnus-spam-autodetect-methods
23457 For back ends such as @code{nntp} there is no incoming mail spool, so
23458 an alternate mechanism must be used. This may also happen for
23459 back ends where the server is in charge of splitting incoming mail, and
23460 Gnus does not do further splitting. The @code{spam-autodetect} and
23461 @code{spam-autodetect-methods} group parameters (accessible with
23462 @kbd{G c} and @kbd{G p} as usual), and the corresponding variables
23463 @code{gnus-spam-autodetect} and @code{gnus-spam-autodetect-methods}
23464 (accessible with @kbd{M-x customize-variable} as usual) can help.
23466 When @code{spam-autodetect} is used (you can turn it on for a
23467 group/topic or wholesale by regular expression matches, as needed), it
23468 hooks into the process of entering a group. Thus, entering a group
23469 with unseen or unread articles becomes the substitute for checking
23470 incoming mail. Whether only unseen articles or all unread articles
23471 will be processed is determined by the
23472 @code{spam-autodetect-recheck-messages}. When set to @code{t}, unread
23473 messages will be rechecked. You should probably stick with the
23474 default of only checking unseen messages.
23476 @code{spam-autodetect} grants the user at once more and less control
23477 of spam filtering. The user will have more control over each group's
23478 spam methods, so for instance the @samp{ding} group may have
23479 @code{spam-use-BBDB} as the autodetection method, while the
23480 @samp{suspect} group may have the @code{spam-use-blacklist} and
23481 @code{spam-use-bogofilter} methods enabled. Every article detected to
23482 be spam will be marked with the spam mark @samp{$} and processed on
23483 exit from the group as normal spam. The user has less control over
23484 the @emph{sequence} of checks, as he might with @code{spam-split}.
23486 When the newly split mail goes into groups, or messages are
23487 autodetected to be ham or spam, those groups must be exited (after
23488 entering, if needed) for further spam processing to happen. It
23489 matters whether the group is considered a ham group, a spam group, or
23490 is unclassified, based on its @code{spam-content} parameter
23491 (@pxref{Spam ELisp Package Global Variables}). Spam groups have the
23492 additional characteristic that, when entered, any unseen or unread
23493 articles (depending on the @code{spam-mark-only-unseen-as-spam}
23494 variable) will be marked as spam. Thus, mail split into a spam group
23495 gets automatically marked as spam when you enter the group.
23497 Thus, when you exit a group, the @code{spam-processors} are applied,
23498 if any are set, and the processed mail is moved to the
23499 @code{ham-process-destination} or the @code{spam-process-destination}
23500 depending on the article's classification. If the
23501 @code{ham-process-destination} or the @code{spam-process-destination},
23502 whichever is appropriate, are @code{nil}, the article is left in the
23505 If a spam is found in any group (this can be changed to only non-spam
23506 groups with @code{spam-move-spam-nonspam-groups-only}), it is
23507 processed by the active @code{spam-processors} (@pxref{Spam ELisp
23508 Package Global Variables}) when the group is exited. Furthermore, the
23509 spam is moved to the @code{spam-process-destination} (@pxref{Spam
23510 ELisp Package Global Variables}) for further training or deletion.
23511 You have to load the @code{gnus-registry.el} package and enable the
23512 @code{spam-log-to-registry} variable if you want spam to be processed
23513 no more than once. Thus, spam is detected and processed everywhere,
23514 which is what most people want. If the
23515 @code{spam-process-destination} is @code{nil}, the spam is marked as
23516 expired, which is usually the right thing to do.
23518 If spam can not be moved---because of a read-only back end such as
23519 @acronym{NNTP}, for example, it will be copied.
23521 If a ham mail is found in a ham group, as determined by the
23522 @code{ham-marks} parameter, it is processed as ham by the active ham
23523 @code{spam-processor} when the group is exited. With the variables
23524 @code{spam-process-ham-in-spam-groups} and
23525 @code{spam-process-ham-in-nonham-groups} the behavior can be further
23526 altered so ham found anywhere can be processed. You have to load the
23527 @code{gnus-registry.el} package and enable the
23528 @code{spam-log-to-registry} variable if you want ham to be processed
23529 no more than once. Thus, ham is detected and processed only when
23530 necessary, which is what most people want. More on this in
23531 @xref{Spam ELisp Package Configuration Examples}.
23533 If ham can not be moved---because of a read-only back end such as
23534 @acronym{NNTP}, for example, it will be copied.
23536 If all this seems confusing, don't worry. Soon it will be as natural
23537 as typing Lisp one-liners on a neural interface@dots{} err, sorry, that's
23538 50 years in the future yet. Just trust us, it's not so bad.
23540 @node Spam ELisp Package Filtering of Incoming Mail
23541 @subsubsection Spam ELisp Package Filtering of Incoming Mail
23542 @cindex spam filtering
23543 @cindex spam filtering incoming mail
23546 To use the @code{spam.el} facilities for incoming mail filtering, you
23547 must add the following to your fancy split list
23548 @code{nnmail-split-fancy} or @code{nnimap-split-fancy}:
23554 Note that the fancy split may be called @code{nnmail-split-fancy} or
23555 @code{nnimap-split-fancy}, depending on whether you use the nnmail or
23556 nnimap back ends to retrieve your mail.
23558 Also, @code{spam-split} will not modify incoming mail in any way.
23560 The @code{spam-split} function will process incoming mail and send the
23561 mail considered to be spam into the group name given by the variable
23562 @code{spam-split-group}. By default that group name is @samp{spam},
23563 but you can customize @code{spam-split-group}. Make sure the contents
23564 of @code{spam-split-group} are an @emph{unqualified} group name, for
23565 instance in an @code{nnimap} server @samp{your-server} the value
23566 @samp{spam} will turn out to be @samp{nnimap+your-server:spam}. The
23567 value @samp{nnimap+server:spam}, therefore, is wrong and will
23568 actually give you the group
23569 @samp{nnimap+your-server:nnimap+server:spam} which may or may not
23570 work depending on your server's tolerance for strange group names.
23572 You can also give @code{spam-split} a parameter,
23573 e.g. @code{spam-use-regex-headers} or @code{"maybe-spam"}. Why is
23576 Take these split rules (with @code{spam-use-regex-headers} and
23577 @code{spam-use-blackholes} set):
23580 nnimap-split-fancy '(|
23581 (any "ding" "ding")
23583 ;; @r{default mailbox}
23587 Now, the problem is that you want all ding messages to make it to the
23588 ding folder. But that will let obvious spam (for example, spam
23589 detected by SpamAssassin, and @code{spam-use-regex-headers}) through,
23590 when it's sent to the ding list. On the other hand, some messages to
23591 the ding list are from a mail server in the blackhole list, so the
23592 invocation of @code{spam-split} can't be before the ding rule.
23594 You can let SpamAssassin headers supersede ding rules, but all other
23595 @code{spam-split} rules (including a second invocation of the
23596 regex-headers check) will be after the ding rule:
23601 ;; @r{all spam detected by @code{spam-use-regex-headers} goes to @samp{regex-spam}}
23602 (: spam-split "regex-spam" 'spam-use-regex-headers)
23603 (any "ding" "ding")
23604 ;; @r{all other spam detected by spam-split goes to @code{spam-split-group}}
23606 ;; @r{default mailbox}
23610 This lets you invoke specific @code{spam-split} checks depending on
23611 your particular needs, and to target the results of those checks to a
23612 particular spam group. You don't have to throw all mail into all the
23613 spam tests. Another reason why this is nice is that messages to
23614 mailing lists you have rules for don't have to have resource-intensive
23615 blackhole checks performed on them. You could also specify different
23616 spam checks for your nnmail split vs. your nnimap split. Go crazy.
23618 You should still have specific checks such as
23619 @code{spam-use-regex-headers} set to @code{t}, even if you
23620 specifically invoke @code{spam-split} with the check. The reason is
23621 that when loading @file{spam.el}, some conditional loading is done
23622 depending on what @code{spam-use-xyz} variables you have set. This
23623 is usually not critical, though.
23625 @emph{Note for IMAP users}
23627 The boolean variable @code{nnimap-split-download-body} needs to be
23628 set, if you want to split based on the whole message instead of just
23629 the headers. By default, the nnimap back end will only retrieve the
23630 message headers. If you use a @emph{statistical} filter,
23631 e.g. @code{spam-check-bogofilter}, @code{spam-check-ifile}, or
23632 @code{spam-check-stat} (the splitters that can benefit from the full
23633 message body), this variable will be set automatically. It is not set
23634 for non-statistical back ends by default because it will slow
23635 @acronym{IMAP} down.
23637 @xref{Splitting in IMAP}.
23639 @node Spam ELisp Package Global Variables
23640 @subsubsection Spam ELisp Package Global Variables
23641 @cindex spam filtering
23642 @cindex spam filtering variables
23643 @cindex spam variables
23646 @vindex gnus-spam-process-newsgroups
23647 The concepts of ham processors and spam processors are very important.
23648 Ham processors and spam processors for a group can be set with the
23649 @code{spam-process} group parameter, or the
23650 @code{gnus-spam-process-newsgroups} variable. Ham processors take
23651 mail known to be non-spam (@emph{ham}) and process it in some way so
23652 that later similar mail will also be considered non-spam. Spam
23653 processors take mail known to be spam and process it so similar spam
23654 will be detected later.
23656 The format of the spam or ham processor entry used to be a symbol,
23657 but now it is a @sc{cons} cell. See the individual spam processor entries
23658 for more information.
23660 @vindex gnus-spam-newsgroup-contents
23661 Gnus learns from the spam you get. You have to collect your spam in
23662 one or more spam groups, and set or customize the variable
23663 @code{spam-junk-mailgroups} as appropriate. You can also declare
23664 groups to contain spam by setting their group parameter
23665 @code{spam-contents} to @code{gnus-group-spam-classification-spam}, or
23666 by customizing the corresponding variable
23667 @code{gnus-spam-newsgroup-contents}. The @code{spam-contents} group
23668 parameter and the @code{gnus-spam-newsgroup-contents} variable can
23669 also be used to declare groups as @emph{ham} groups if you set their
23670 classification to @code{gnus-group-spam-classification-ham}. If
23671 groups are not classified by means of @code{spam-junk-mailgroups},
23672 @code{spam-contents}, or @code{gnus-spam-newsgroup-contents}, they are
23673 considered @emph{unclassified}. All groups are unclassified by
23676 @vindex gnus-spam-mark
23678 In spam groups, all messages are considered to be spam by default:
23679 they get the @samp{$} mark (@code{gnus-spam-mark}) when you enter the
23680 group. If you have seen a message, had it marked as spam, then
23681 unmarked it, it won't be marked as spam when you enter the group
23682 thereafter. You can disable that behavior, so all unread messages
23683 will get the @samp{$} mark, if you set the
23684 @code{spam-mark-only-unseen-as-spam} parameter to @code{nil}. You
23685 should remove the @samp{$} mark when you are in the group summary
23686 buffer for every message that is not spam after all. To remove the
23687 @samp{$} mark, you can use @kbd{M-u} to ``unread'' the article, or
23688 @kbd{d} for declaring it read the non-spam way. When you leave a
23689 group, all spam-marked (@samp{$}) articles are sent to a spam
23690 processor which will study them as spam samples.
23692 Messages may also be deleted in various other ways, and unless
23693 @code{ham-marks} group parameter gets overridden below, marks @samp{R}
23694 and @samp{r} for default read or explicit delete, marks @samp{X} and
23695 @samp{K} for automatic or explicit kills, as well as mark @samp{Y} for
23696 low scores, are all considered to be associated with articles which
23697 are not spam. This assumption might be false, in particular if you
23698 use kill files or score files as means for detecting genuine spam, you
23699 should then adjust the @code{ham-marks} group parameter.
23702 You can customize this group or topic parameter to be the list of
23703 marks you want to consider ham. By default, the list contains the
23704 deleted, read, killed, kill-filed, and low-score marks (the idea is
23705 that these articles have been read, but are not spam). It can be
23706 useful to also include the tick mark in the ham marks. It is not
23707 recommended to make the unread mark a ham mark, because it normally
23708 indicates a lack of classification. But you can do it, and we'll be
23713 You can customize this group or topic parameter to be the list of
23714 marks you want to consider spam. By default, the list contains only
23715 the spam mark. It is not recommended to change that, but you can if
23716 you really want to.
23719 When you leave @emph{any} group, regardless of its
23720 @code{spam-contents} classification, all spam-marked articles are sent
23721 to a spam processor, which will study these as spam samples. If you
23722 explicit kill a lot, you might sometimes end up with articles marked
23723 @samp{K} which you never saw, and which might accidentally contain
23724 spam. Best is to make sure that real spam is marked with @samp{$},
23727 @vindex gnus-ham-process-destinations
23728 When you leave a @emph{spam} group, all spam-marked articles are
23729 marked as expired after processing with the spam processor. This is
23730 not done for @emph{unclassified} or @emph{ham} groups. Also, any
23731 @strong{ham} articles in a spam group will be moved to a location
23732 determined by either the @code{ham-process-destination} group
23733 parameter or a match in the @code{gnus-ham-process-destinations}
23734 variable, which is a list of regular expressions matched with group
23735 names (it's easiest to customize this variable with @kbd{M-x
23736 customize-variable @key{RET} gnus-ham-process-destinations}). Each
23737 group name list is a standard Lisp list, if you prefer to customize
23738 the variable manually. If the @code{ham-process-destination}
23739 parameter is not set, ham articles are left in place. If the
23740 @code{spam-mark-ham-unread-before-move-from-spam-group} parameter is
23741 set, the ham articles are marked as unread before being moved.
23743 If ham can not be moved---because of a read-only back end such as
23744 @acronym{NNTP}, for example, it will be copied.
23746 Note that you can use multiples destinations per group or regular
23747 expression! This enables you to send your ham to a regular mail
23748 group and to a @emph{ham training} group.
23750 When you leave a @emph{ham} group, all ham-marked articles are sent to
23751 a ham processor, which will study these as non-spam samples.
23753 @vindex spam-process-ham-in-spam-groups
23754 By default the variable @code{spam-process-ham-in-spam-groups} is
23755 @code{nil}. Set it to @code{t} if you want ham found in spam groups
23756 to be processed. Normally this is not done, you are expected instead
23757 to send your ham to a ham group and process it there.
23759 @vindex spam-process-ham-in-nonham-groups
23760 By default the variable @code{spam-process-ham-in-nonham-groups} is
23761 @code{nil}. Set it to @code{t} if you want ham found in non-ham (spam
23762 or unclassified) groups to be processed. Normally this is not done,
23763 you are expected instead to send your ham to a ham group and process
23766 @vindex gnus-spam-process-destinations
23767 When you leave a @emph{ham} or @emph{unclassified} group, all
23768 @strong{spam} articles are moved to a location determined by either
23769 the @code{spam-process-destination} group parameter or a match in the
23770 @code{gnus-spam-process-destinations} variable, which is a list of
23771 regular expressions matched with group names (it's easiest to
23772 customize this variable with @kbd{M-x customize-variable @key{RET}
23773 gnus-spam-process-destinations}). Each group name list is a standard
23774 Lisp list, if you prefer to customize the variable manually. If the
23775 @code{spam-process-destination} parameter is not set, the spam
23776 articles are only expired. The group name is fully qualified, meaning
23777 that if you see @samp{nntp:servername} before the group name in the
23778 group buffer then you need it here as well.
23780 If spam can not be moved---because of a read-only back end such as
23781 @acronym{NNTP}, for example, it will be copied.
23783 Note that you can use multiples destinations per group or regular
23784 expression! This enables you to send your spam to multiple @emph{spam
23787 @vindex spam-log-to-registry
23788 The problem with processing ham and spam is that Gnus doesn't track
23789 this processing by default. Enable the @code{spam-log-to-registry}
23790 variable so @code{spam.el} will use @code{gnus-registry.el} to track
23791 what articles have been processed, and avoid processing articles
23792 multiple times. Keep in mind that if you limit the number of registry
23793 entries, this won't work as well as it does without a limit.
23795 @vindex spam-mark-only-unseen-as-spam
23796 Set this variable if you want only unseen articles in spam groups to
23797 be marked as spam. By default, it is set. If you set it to
23798 @code{nil}, unread articles will also be marked as spam.
23800 @vindex spam-mark-ham-unread-before-move-from-spam-group
23801 Set this variable if you want ham to be unmarked before it is moved
23802 out of the spam group. This is very useful when you use something
23803 like the tick mark @samp{!} to mark ham---the article will be placed
23804 in your @code{ham-process-destination}, unmarked as if it came fresh
23805 from the mail server.
23807 @vindex spam-autodetect-recheck-messages
23808 When autodetecting spam, this variable tells @code{spam.el} whether
23809 only unseen articles or all unread articles should be checked for
23810 spam. It is recommended that you leave it off.
23812 @node Spam ELisp Package Sorting and Score Display in Summary Buffer
23813 @subsubsection Spam ELisp Package Sorting and Score Display in Summary Buffer
23814 @cindex spam scoring
23815 @cindex spam sorting
23816 @cindex spam score summary buffer
23817 @cindex spam sort summary buffer
23820 You can display the spam score of articles in your summary buffer, and
23821 you can sort articles by their spam score.
23823 First you need to decide which back end you will be using. If you use
23824 the @code{spam-use-spamassassin},
23825 @code{spam-use-spamassassin-headers}, or @code{spam-use-regex-headers}
23826 back end, the @code{X-Spam-Status} header will be used. If you use
23827 @code{spam-use-bogofilter}, the @code{X-Bogosity} header will be used.
23828 If you use @code{spam-use-crm114}, any header that matches the CRM114
23829 score format will be used. As long as you set the appropriate back end
23830 variable to t @emph{before} you load @file{spam.el}, you will be
23831 fine. @code{spam.el} will automatically add the right header to the
23832 internal Gnus list of required headers.
23834 To show the spam score in your summary buffer, add this line to your
23835 @code{gnus.el} file (note @code{spam.el} does not do that by default
23836 so it won't override any existing @code{S} formats you may have).
23839 (defalias 'gnus-user-format-function-S 'spam-user-format-function-S)
23842 Now just set your summary line format to use @code{%uS}. Here's an
23843 example that formats the spam score in a 5-character field:
23846 (setq gnus-summary-line-format
23847 "%U%R %10&user-date; $%5uS %6k %B %(%4L: %*%-25,25a%) %s \n")
23850 Finally, to sort by spam status, either do it globally:
23854 gnus-show-threads nil
23855 gnus-article-sort-functions
23856 '(spam-article-sort-by-spam-status))
23859 or per group (@pxref{Sorting the Summary Buffer}).
23861 @node Spam ELisp Package Configuration Examples
23862 @subsubsection Spam ELisp Package Configuration Examples
23863 @cindex spam filtering
23864 @cindex spam filtering configuration examples
23865 @cindex spam configuration examples
23868 @subsubheading Ted's setup
23870 From Ted Zlatanov <tzz@@lifelogs.com>.
23872 ;; @r{for @code{gnus-registry-split-fancy-with-parent} and spam autodetection}
23873 ;; @r{see @file{gnus-registry.el} for more information}
23874 (gnus-registry-initialize)
23877 ;; @r{I like @kbd{C-s} for marking spam}
23878 (define-key gnus-summary-mode-map "\C-s" 'gnus-summary-mark-as-spam)
23881 spam-log-to-registry t ; @r{for spam autodetection}
23883 spam-use-regex-headers t ; @r{catch X-Spam-Flag (SpamAssassin)}
23884 ;; @r{all groups with @samp{spam} in the name contain spam}
23885 gnus-spam-newsgroup-contents
23886 '(("spam" gnus-group-spam-classification-spam))
23887 ;; @r{see documentation for these}
23888 spam-move-spam-nonspam-groups-only nil
23889 spam-mark-only-unseen-as-spam t
23890 spam-mark-ham-unread-before-move-from-spam-group t
23891 nnimap-split-rule 'nnimap-split-fancy
23892 ;; @r{understand what this does before you copy it to your own setup!}
23893 nnimap-split-fancy '(|
23894 ;; @r{trace references to parents and put in their group}
23895 (: gnus-registry-split-fancy-with-parent)
23896 ;; @r{this will catch server-side SpamAssassin tags}
23897 (: spam-split 'spam-use-regex-headers)
23898 (any "ding" "ding")
23899 ;; @r{note that spam by default will go to @samp{spam}}
23901 ;; @r{default mailbox}
23904 ;; @r{my parameters, set with @kbd{G p}}
23906 ;; @r{all nnml groups, and all nnimap groups except}
23907 ;; @r{@samp{nnimap+mail.lifelogs.com:train} and}
23908 ;; @r{@samp{nnimap+mail.lifelogs.com:spam}: any spam goes to nnimap training,}
23909 ;; @r{because it must have been detected manually}
23911 ((spam-process-destination . "nnimap+mail.lifelogs.com:train"))
23913 ;; @r{all @acronym{NNTP} groups}
23914 ;; @r{autodetect spam with the blacklist and ham with the BBDB}
23915 ((spam-autodetect-methods spam-use-blacklist spam-use-BBDB)
23916 ;; @r{send all spam to the training group}
23917 (spam-process-destination . "nnimap+mail.lifelogs.com:train"))
23919 ;; @r{only some @acronym{NNTP} groups, where I want to autodetect spam}
23920 ((spam-autodetect . t))
23922 ;; @r{my nnimap @samp{nnimap+mail.lifelogs.com:spam} group}
23924 ;; @r{this is a spam group}
23925 ((spam-contents gnus-group-spam-classification-spam)
23927 ;; @r{any spam (which happens when I enter for all unseen messages,}
23928 ;; @r{because of the @code{gnus-spam-newsgroup-contents} setting above), goes to}
23929 ;; @r{@samp{nnimap+mail.lifelogs.com:train} unless I mark it as ham}
23931 (spam-process-destination "nnimap+mail.lifelogs.com:train")
23933 ;; @r{any ham goes to my @samp{nnimap+mail.lifelogs.com:mail} folder, but}
23934 ;; @r{also to my @samp{nnimap+mail.lifelogs.com:trainham} folder for training}
23936 (ham-process-destination "nnimap+mail.lifelogs.com:mail"
23937 "nnimap+mail.lifelogs.com:trainham")
23938 ;; @r{in this group, only @samp{!} marks are ham}
23940 (gnus-ticked-mark))
23941 ;; @r{remembers senders in the blacklist on the way out---this is}
23942 ;; @r{definitely not needed, it just makes me feel better}
23943 (spam-process (gnus-group-spam-exit-processor-blacklist)))
23945 ;; @r{Later, on the @acronym{IMAP} server I use the @samp{train} group for training}
23946 ;; @r{SpamAssassin to recognize spam, and the @samp{trainham} group fora}
23947 ;; @r{recognizing ham---but Gnus has nothing to do with it.}
23951 @subsubheading Using @code{spam.el} on an IMAP server with a statistical filter on the server
23952 From Reiner Steib <reiner.steib@@gmx.de>.
23954 My provider has set up bogofilter (in combination with @acronym{DCC}) on
23955 the mail server (@acronym{IMAP}). Recognized spam goes to
23956 @samp{spam.detected}, the rest goes through the normal filter rules,
23957 i.e. to @samp{some.folder} or to @samp{INBOX}. Training on false
23958 positives or negatives is done by copying or moving the article to
23959 @samp{training.ham} or @samp{training.spam} respectively. A cron job on
23960 the server feeds those to bogofilter with the suitable ham or spam
23961 options and deletes them from the @samp{training.ham} and
23962 @samp{training.spam} folders.
23964 With the following entries in @code{gnus-parameters}, @code{spam.el}
23965 does most of the job for me:
23968 ("nnimap:spam\\.detected"
23969 (gnus-article-sort-functions '(gnus-article-sort-by-chars))
23970 (ham-process-destination "nnimap:INBOX" "nnimap:training.ham")
23971 (spam-contents gnus-group-spam-classification-spam))
23972 ("nnimap:\\(INBOX\\|other-folders\\)"
23973 (spam-process-destination . "nnimap:training.spam")
23974 (spam-contents gnus-group-spam-classification-ham))
23979 @item @b{The Spam folder:}
23981 In the folder @samp{spam.detected}, I have to check for false positives
23982 (i.e. legitimate mails, that were wrongly judged as spam by
23983 bogofilter or DCC).
23985 Because of the @code{gnus-group-spam-classification-spam} entry, all
23986 messages are marked as spam (with @code{$}). When I find a false
23987 positive, I mark the message with some other ham mark (@code{ham-marks},
23988 @ref{Spam ELisp Package Global Variables}). On group exit, those
23989 messages are copied to both groups, @samp{INBOX} (where I want to have
23990 the article) and @samp{training.ham} (for training bogofilter) and
23991 deleted from the @samp{spam.detected} folder.
23993 The @code{gnus-article-sort-by-chars} entry simplifies detection of
23994 false positives for me. I receive lots of worms (sweN, @dots{}), that all
23995 have a similar size. Grouping them by size (i.e. chars) makes finding
23996 other false positives easier. (Of course worms aren't @i{spam}
23997 (@acronym{UCE}, @acronym{UBE}) strictly speaking. Anyhow, bogofilter is
23998 an excellent tool for filtering those unwanted mails for me.)
24000 @item @b{Ham folders:}
24002 In my ham folders, I just hit @kbd{S x}
24003 (@code{gnus-summary-mark-as-spam}) whenever I see an unrecognized spam
24004 mail (false negative). On group exit, those messages are moved to
24005 @samp{training.spam}.
24008 @subsubheading Reporting spam articles in Gmane groups with @code{spam-report.el}
24010 From Reiner Steib <reiner.steib@@gmx.de>.
24012 With following entry in @code{gnus-parameters}, @kbd{S x}
24013 (@code{gnus-summary-mark-as-spam}) marks articles in @code{gmane.*}
24014 groups as spam and reports the to Gmane at group exit:
24018 (spam-process (gnus-group-spam-exit-processor-report-gmane)))
24021 Additionally, I use @code{(setq spam-report-gmane-use-article-number nil)}
24022 because I don't read the groups directly from news.gmane.org, but
24023 through my local news server (leafnode). I.e. the article numbers are
24024 not the same as on news.gmane.org, thus @code{spam-report.el} has to check
24025 the @code{X-Report-Spam} header to find the correct number.
24027 @node Blacklists and Whitelists
24028 @subsubsection Blacklists and Whitelists
24029 @cindex spam filtering
24030 @cindex whitelists, spam filtering
24031 @cindex blacklists, spam filtering
24034 @defvar spam-use-blacklist
24036 Set this variable to @code{t} if you want to use blacklists when
24037 splitting incoming mail. Messages whose senders are in the blacklist
24038 will be sent to the @code{spam-split-group}. This is an explicit
24039 filter, meaning that it acts only on mail senders @emph{declared} to
24044 @defvar spam-use-whitelist
24046 Set this variable to @code{t} if you want to use whitelists when
24047 splitting incoming mail. Messages whose senders are not in the
24048 whitelist will be sent to the next spam-split rule. This is an
24049 explicit filter, meaning that unless someone is in the whitelist, their
24050 messages are not assumed to be spam or ham.
24054 @defvar spam-use-whitelist-exclusive
24056 Set this variable to @code{t} if you want to use whitelists as an
24057 implicit filter, meaning that every message will be considered spam
24058 unless the sender is in the whitelist. Use with care.
24062 @defvar gnus-group-spam-exit-processor-blacklist
24064 Add this symbol to a group's @code{spam-process} parameter by
24065 customizing the group parameters or the
24066 @code{gnus-spam-process-newsgroups} variable. When this symbol is
24067 added to a group's @code{spam-process} parameter, the senders of
24068 spam-marked articles will be added to the blacklist.
24072 Instead of the obsolete
24073 @code{gnus-group-spam-exit-processor-blacklist}, it is recommended
24074 that you use @code{(spam spam-use-blacklist)}. Everything will work
24075 the same way, we promise.
24079 @defvar gnus-group-ham-exit-processor-whitelist
24081 Add this symbol to a group's @code{spam-process} parameter by
24082 customizing the group parameters or the
24083 @code{gnus-spam-process-newsgroups} variable. When this symbol is
24084 added to a group's @code{spam-process} parameter, the senders of
24085 ham-marked articles in @emph{ham} groups will be added to the
24090 Instead of the obsolete
24091 @code{gnus-group-ham-exit-processor-whitelist}, it is recommended
24092 that you use @code{(ham spam-use-whitelist)}. Everything will work
24093 the same way, we promise.
24097 Blacklists are lists of regular expressions matching addresses you
24098 consider to be spam senders. For instance, to block mail from any
24099 sender at @samp{vmadmin.com}, you can put @samp{vmadmin.com} in your
24100 blacklist. You start out with an empty blacklist. Blacklist entries
24101 use the Emacs regular expression syntax.
24103 Conversely, whitelists tell Gnus what addresses are considered
24104 legitimate. All messages from whitelisted addresses are considered
24105 non-spam. Also see @ref{BBDB Whitelists}. Whitelist entries use the
24106 Emacs regular expression syntax.
24108 The blacklist and whitelist file locations can be customized with the
24109 @code{spam-directory} variable (@file{~/News/spam} by default), or
24110 the @code{spam-whitelist} and @code{spam-blacklist} variables
24111 directly. The whitelist and blacklist files will by default be in the
24112 @code{spam-directory} directory, named @file{whitelist} and
24113 @file{blacklist} respectively.
24115 @node BBDB Whitelists
24116 @subsubsection BBDB Whitelists
24117 @cindex spam filtering
24118 @cindex BBDB whitelists, spam filtering
24119 @cindex BBDB, spam filtering
24122 @defvar spam-use-BBDB
24124 Analogous to @code{spam-use-whitelist} (@pxref{Blacklists and
24125 Whitelists}), but uses the BBDB as the source of whitelisted
24126 addresses, without regular expressions. You must have the BBDB loaded
24127 for @code{spam-use-BBDB} to work properly. Messages whose senders are
24128 not in the BBDB will be sent to the next spam-split rule. This is an
24129 explicit filter, meaning that unless someone is in the BBDB, their
24130 messages are not assumed to be spam or ham.
24134 @defvar spam-use-BBDB-exclusive
24136 Set this variable to @code{t} if you want to use the BBDB as an
24137 implicit filter, meaning that every message will be considered spam
24138 unless the sender is in the BBDB. Use with care. Only sender
24139 addresses in the BBDB will be allowed through; all others will be
24140 classified as spammers.
24142 While @code{spam-use-BBDB-exclusive} @emph{can} be used as an alias
24143 for @code{spam-use-BBDB} as far as @code{spam.el} is concerned, it is
24144 @emph{not} a separate back end. If you set
24145 @code{spam-use-BBDB-exclusive} to t, @emph{all} your BBDB splitting
24150 @defvar gnus-group-ham-exit-processor-BBDB
24152 Add this symbol to a group's @code{spam-process} parameter by
24153 customizing the group parameters or the
24154 @code{gnus-spam-process-newsgroups} variable. When this symbol is
24155 added to a group's @code{spam-process} parameter, the senders of
24156 ham-marked articles in @emph{ham} groups will be added to the
24161 Instead of the obsolete
24162 @code{gnus-group-ham-exit-processor-BBDB}, it is recommended
24163 that you use @code{(ham spam-use-BBDB)}. Everything will work
24164 the same way, we promise.
24168 @node Gmane Spam Reporting
24169 @subsubsection Gmane Spam Reporting
24170 @cindex spam reporting
24171 @cindex Gmane, spam reporting
24172 @cindex Gmane, spam reporting
24175 @defvar gnus-group-spam-exit-processor-report-gmane
24177 Add this symbol to a group's @code{spam-process} parameter by
24178 customizing the group parameters or the
24179 @code{gnus-spam-process-newsgroups} variable. When this symbol is
24180 added to a group's @code{spam-process} parameter, the spam-marked
24181 articles groups will be reported to the Gmane administrators via a
24184 Gmane can be found at @uref{http://gmane.org}.
24188 Instead of the obsolete
24189 @code{gnus-group-spam-exit-processor-report-gmane}, it is recommended
24190 that you use @code{(spam spam-use-gmane)}. Everything will work the
24191 same way, we promise.
24195 @defvar spam-report-gmane-use-article-number
24197 This variable is @code{t} by default. Set it to @code{nil} if you are
24198 running your own news server, for instance, and the local article
24199 numbers don't correspond to the Gmane article numbers. When
24200 @code{spam-report-gmane-use-article-number} is @code{nil},
24201 @code{spam-report.el} will fetch the number from the article headers.
24205 @defvar spam-report-user-mail-address
24207 Mail address exposed in the User-Agent spam reports to Gmane. It allows
24208 the Gmane administrators to contact you in case of misreports. The
24209 default is @code{user-mail-address}.
24213 @node Anti-spam Hashcash Payments
24214 @subsubsection Anti-spam Hashcash Payments
24215 @cindex spam filtering
24216 @cindex hashcash, spam filtering
24219 @defvar spam-use-hashcash
24221 Similar to @code{spam-use-whitelist} (@pxref{Blacklists and
24222 Whitelists}), but uses hashcash tokens for whitelisting messages
24223 instead of the sender address. Messages without a hashcash payment
24224 token will be sent to the next spam-split rule. This is an explicit
24225 filter, meaning that unless a hashcash token is found, the messages
24226 are not assumed to be spam or ham.
24231 @subsubsection Blackholes
24232 @cindex spam filtering
24233 @cindex blackholes, spam filtering
24236 @defvar spam-use-blackholes
24238 This option is disabled by default. You can let Gnus consult the
24239 blackhole-type distributed spam processing systems (DCC, for instance)
24240 when you set this option. The variable @code{spam-blackhole-servers}
24241 holds the list of blackhole servers Gnus will consult. The current
24242 list is fairly comprehensive, but make sure to let us know if it
24243 contains outdated servers.
24245 The blackhole check uses the @code{dig.el} package, but you can tell
24246 @code{spam.el} to use @code{dns.el} instead for better performance if
24247 you set @code{spam-use-dig} to @code{nil}. It is not recommended at
24248 this time to set @code{spam-use-dig} to @code{nil} despite the
24249 possible performance improvements, because some users may be unable to
24250 use it, but you can try it and see if it works for you.
24254 @defvar spam-blackhole-servers
24256 The list of servers to consult for blackhole checks.
24260 @defvar spam-blackhole-good-server-regex
24262 A regular expression for IPs that should not be checked against the
24263 blackhole server list. When set to @code{nil}, it has no effect.
24267 @defvar spam-use-dig
24269 Use the @code{dig.el} package instead of the @code{dns.el} package.
24270 The default setting of @code{t} is recommended.
24274 Blackhole checks are done only on incoming mail. There is no spam or
24275 ham processor for blackholes.
24277 @node Regular Expressions Header Matching
24278 @subsubsection Regular Expressions Header Matching
24279 @cindex spam filtering
24280 @cindex regular expressions header matching, spam filtering
24283 @defvar spam-use-regex-headers
24285 This option is disabled by default. You can let Gnus check the
24286 message headers against lists of regular expressions when you set this
24287 option. The variables @code{spam-regex-headers-spam} and
24288 @code{spam-regex-headers-ham} hold the list of regular expressions.
24289 Gnus will check against the message headers to determine if the
24290 message is spam or ham, respectively.
24294 @defvar spam-regex-headers-spam
24296 The list of regular expressions that, when matched in the headers of
24297 the message, positively identify it as spam.
24301 @defvar spam-regex-headers-ham
24303 The list of regular expressions that, when matched in the headers of
24304 the message, positively identify it as ham.
24308 Regular expression header checks are done only on incoming mail.
24309 There is no specific spam or ham processor for regular expressions.
24312 @subsubsection Bogofilter
24313 @cindex spam filtering
24314 @cindex bogofilter, spam filtering
24317 @defvar spam-use-bogofilter
24319 Set this variable if you want @code{spam-split} to use Eric Raymond's
24322 With a minimum of care for associating the @samp{$} mark for spam
24323 articles only, Bogofilter training all gets fairly automatic. You
24324 should do this until you get a few hundreds of articles in each
24325 category, spam or not. The command @kbd{S t} in summary mode, either
24326 for debugging or for curiosity, shows the @emph{spamicity} score of
24327 the current article (between 0.0 and 1.0).
24329 Bogofilter determines if a message is spam based on a specific
24330 threshold. That threshold can be customized, consult the Bogofilter
24333 If the @code{bogofilter} executable is not in your path, Bogofilter
24334 processing will be turned off.
24336 You should not enable this if you use @code{spam-use-bogofilter-headers}.
24340 @defvar spam-use-bogofilter-headers
24342 Set this variable if you want @code{spam-split} to use Eric Raymond's
24343 speedy Bogofilter, looking only at the message headers. It works
24344 similarly to @code{spam-use-bogofilter}, but the @code{X-Bogosity} header
24345 must be in the message already. Normally you would do this with a
24346 procmail recipe or something similar; consult the Bogofilter
24347 installation documents for details.
24349 You should not enable this if you use @code{spam-use-bogofilter}.
24353 @defvar gnus-group-spam-exit-processor-bogofilter
24354 Add this symbol to a group's @code{spam-process} parameter by
24355 customizing the group parameters or the
24356 @code{gnus-spam-process-newsgroups} variable. When this symbol is
24357 added to a group's @code{spam-process} parameter, spam-marked articles
24358 will be added to the Bogofilter spam database.
24362 Instead of the obsolete
24363 @code{gnus-group-spam-exit-processor-bogofilter}, it is recommended
24364 that you use @code{(spam spam-use-bogofilter)}. Everything will work
24365 the same way, we promise.
24368 @defvar gnus-group-ham-exit-processor-bogofilter
24369 Add this symbol to a group's @code{spam-process} parameter by
24370 customizing the group parameters or the
24371 @code{gnus-spam-process-newsgroups} variable. When this symbol is
24372 added to a group's @code{spam-process} parameter, the ham-marked
24373 articles in @emph{ham} groups will be added to the Bogofilter database
24374 of non-spam messages.
24378 Instead of the obsolete
24379 @code{gnus-group-ham-exit-processor-bogofilter}, it is recommended
24380 that you use @code{(ham spam-use-bogofilter)}. Everything will work
24381 the same way, we promise.
24384 @defvar spam-bogofilter-database-directory
24386 This is the directory where Bogofilter will store its databases. It
24387 is not specified by default, so Bogofilter will use its own default
24388 database directory.
24392 The Bogofilter mail classifier is similar to @command{ifile} in intent and
24393 purpose. A ham and a spam processor are provided, plus the
24394 @code{spam-use-bogofilter} and @code{spam-use-bogofilter-headers}
24395 variables to indicate to spam-split that Bogofilter should either be
24396 used, or has already been used on the article. The 0.9.2.1 version of
24397 Bogofilter was used to test this functionality.
24399 @node SpamAssassin back end
24400 @subsubsection SpamAssassin back end
24401 @cindex spam filtering
24402 @cindex spamassassin, spam filtering
24405 @defvar spam-use-spamassassin
24407 Set this variable if you want @code{spam-split} to use SpamAssassin.
24409 SpamAssassin assigns a score to each article based on a set of rules
24410 and tests, including a Bayesian filter. The Bayesian filter can be
24411 trained by associating the @samp{$} mark for spam articles. The
24412 spam score can be viewed by using the command @kbd{S t} in summary
24415 If you set this variable, each article will be processed by
24416 SpamAssassin when @code{spam-split} is called. If your mail is
24417 preprocessed by SpamAssassin, and you want to just use the
24418 SpamAssassin headers, set @code{spam-use-spamassassin-headers}
24421 You should not enable this is you use
24422 @code{spam-use-spamassassin-headers}.
24426 @defvar spam-use-spamassassin-headers
24428 Set this variable if your mail is preprocessed by SpamAssassin and
24429 want @code{spam-split} to split based on the SpamAssassin headers.
24431 You should not enable this is you use @code{spam-use-spamassassin}.
24435 @defvar spam-spamassassin-path
24437 This variable points to the SpamAssassin executable. If you have
24438 @code{spamd} running, you can set this variable to the @code{spamc}
24439 executable for faster processing. See the SpamAssassin documentation
24440 for more information on @code{spamd}/@code{spamc}.
24444 SpamAssassin is a powerful and flexible spam filter that uses a wide
24445 variety of tests to identify spam. A ham and a spam processors are
24446 provided, plus the @code{spam-use-spamassassin} and
24447 @code{spam-use-spamassassin-headers} variables to indicate to
24448 spam-split that SpamAssassin should be either used, or has already
24449 been used on the article. The 2.63 version of SpamAssassin was used
24450 to test this functionality.
24452 @node ifile spam filtering
24453 @subsubsection ifile spam filtering
24454 @cindex spam filtering
24455 @cindex ifile, spam filtering
24458 @defvar spam-use-ifile
24460 Enable this variable if you want @code{spam-split} to use @command{ifile}, a
24461 statistical analyzer similar to Bogofilter.
24465 @defvar spam-ifile-all-categories
24467 Enable this variable if you want @code{spam-use-ifile} to give you all
24468 the ifile categories, not just spam/non-spam. If you use this, make
24469 sure you train ifile as described in its documentation.
24473 @defvar spam-ifile-spam-category
24475 This is the category of spam messages as far as ifile is concerned.
24476 The actual string used is irrelevant, but you probably want to leave
24477 the default value of @samp{spam}.
24480 @defvar spam-ifile-database-path
24482 This is the filename for the ifile database. It is not specified by
24483 default, so ifile will use its own default database name.
24487 The ifile mail classifier is similar to Bogofilter in intent and
24488 purpose. A ham and a spam processor are provided, plus the
24489 @code{spam-use-ifile} variable to indicate to spam-split that ifile
24490 should be used. The 1.2.1 version of ifile was used to test this
24493 @node spam-stat spam filtering
24494 @subsubsection spam-stat spam filtering
24495 @cindex spam filtering
24496 @cindex spam-stat, spam filtering
24500 @xref{Filtering Spam Using Statistics with spam-stat}.
24502 @defvar spam-use-stat
24504 Enable this variable if you want @code{spam-split} to use
24505 spam-stat.el, an Emacs Lisp statistical analyzer.
24509 @defvar gnus-group-spam-exit-processor-stat
24510 Add this symbol to a group's @code{spam-process} parameter by
24511 customizing the group parameters or the
24512 @code{gnus-spam-process-newsgroups} variable. When this symbol is
24513 added to a group's @code{spam-process} parameter, the spam-marked
24514 articles will be added to the spam-stat database of spam messages.
24518 Instead of the obsolete
24519 @code{gnus-group-spam-exit-processor-stat}, it is recommended
24520 that you use @code{(spam spam-use-stat)}. Everything will work
24521 the same way, we promise.
24524 @defvar gnus-group-ham-exit-processor-stat
24525 Add this symbol to a group's @code{spam-process} parameter by
24526 customizing the group parameters or the
24527 @code{gnus-spam-process-newsgroups} variable. When this symbol is
24528 added to a group's @code{spam-process} parameter, the ham-marked
24529 articles in @emph{ham} groups will be added to the spam-stat database
24530 of non-spam messages.
24534 Instead of the obsolete
24535 @code{gnus-group-ham-exit-processor-stat}, it is recommended
24536 that you use @code{(ham spam-use-stat)}. Everything will work
24537 the same way, we promise.
24540 This enables @code{spam.el} to cooperate with @file{spam-stat.el}.
24541 @file{spam-stat.el} provides an internal (Lisp-only) spam database,
24542 which unlike ifile or Bogofilter does not require external programs.
24543 A spam and a ham processor, and the @code{spam-use-stat} variable for
24544 @code{spam-split} are provided.
24547 @subsubsection Using SpamOracle with Gnus
24548 @cindex spam filtering
24552 An easy way to filter out spam is to use SpamOracle. SpamOracle is an
24553 statistical mail filtering tool written by Xavier Leroy and needs to be
24554 installed separately.
24556 There are several ways to use SpamOracle with Gnus. In all cases, your
24557 mail is piped through SpamOracle in its @emph{mark} mode. SpamOracle will
24558 then enter an @samp{X-Spam} header indicating whether it regards the
24559 mail as a spam mail or not.
24561 One possibility is to run SpamOracle as a @code{:prescript} from the
24562 @xref{Mail Source Specifiers}, (@pxref{SpamAssassin}). This method has
24563 the advantage that the user can see the @emph{X-Spam} headers.
24565 The easiest method is to make @code{spam.el} (@pxref{Filtering Spam
24566 Using The Spam ELisp Package}) call SpamOracle.
24568 @vindex spam-use-spamoracle
24569 To enable SpamOracle usage by @code{spam.el}, set the variable
24570 @code{spam-use-spamoracle} to @code{t} and configure the
24571 @code{nnmail-split-fancy} or @code{nnimap-split-fancy} as described in
24572 the section @xref{Filtering Spam Using The Spam ELisp Package}. In
24573 this example the @samp{INBOX} of an nnimap server is filtered using
24574 SpamOracle. Mails recognized as spam mails will be moved to
24575 @code{spam-split-group}, @samp{Junk} in this case. Ham messages stay
24579 (setq spam-use-spamoracle t
24580 spam-split-group "Junk"
24581 nnimap-split-inbox '("INBOX")
24582 nnimap-split-rule 'nnimap-split-fancy
24583 nnimap-split-fancy '(| (: spam-split) "INBOX"))
24586 @defvar spam-use-spamoracle
24587 Set to @code{t} if you want Gnus to enable spam filtering using
24591 @defvar spam-spamoracle-binary
24592 Gnus uses the SpamOracle binary called @file{spamoracle} found in the
24593 user's PATH. Using the variable @code{spam-spamoracle-binary}, this
24597 @defvar spam-spamoracle-database
24598 By default, SpamOracle uses the file @file{~/.spamoracle.db} as a database to
24599 store its analyses. This is controlled by the variable
24600 @code{spam-spamoracle-database} which defaults to @code{nil}. That means
24601 the default SpamOracle database will be used. In case you want your
24602 database to live somewhere special, set
24603 @code{spam-spamoracle-database} to this path.
24606 SpamOracle employs a statistical algorithm to determine whether a
24607 message is spam or ham. In order to get good results, meaning few
24608 false hits or misses, SpamOracle needs training. SpamOracle learns the
24609 characteristics of your spam mails. Using the @emph{add} mode
24610 (training mode) one has to feed good (ham) and spam mails to
24611 SpamOracle. This can be done by pressing @kbd{|} in the Summary buffer
24612 and pipe the mail to a SpamOracle process or using @code{spam.el}'s
24613 spam- and ham-processors, which is much more convenient. For a
24614 detailed description of spam- and ham-processors, @xref{Filtering Spam
24615 Using The Spam ELisp Package}.
24617 @defvar gnus-group-spam-exit-processor-spamoracle
24618 Add this symbol to a group's @code{spam-process} parameter by
24619 customizing the group parameter or the
24620 @code{gnus-spam-process-newsgroups} variable. When this symbol is added
24621 to a group's @code{spam-process} parameter, spam-marked articles will be
24622 sent to SpamOracle as spam samples.
24626 Instead of the obsolete
24627 @code{gnus-group-spam-exit-processor-spamoracle}, it is recommended
24628 that you use @code{(spam spam-use-spamoracle)}. Everything will work
24629 the same way, we promise.
24632 @defvar gnus-group-ham-exit-processor-spamoracle
24633 Add this symbol to a group's @code{spam-process} parameter by
24634 customizing the group parameter or the
24635 @code{gnus-spam-process-newsgroups} variable. When this symbol is added
24636 to a group's @code{spam-process} parameter, the ham-marked articles in
24637 @emph{ham} groups will be sent to the SpamOracle as samples of ham
24642 Instead of the obsolete
24643 @code{gnus-group-ham-exit-processor-spamoracle}, it is recommended
24644 that you use @code{(ham spam-use-spamoracle)}. Everything will work
24645 the same way, we promise.
24648 @emph{Example:} These are the Group Parameters of a group that has been
24649 classified as a ham group, meaning that it should only contain ham
24652 ((spam-contents gnus-group-spam-classification-ham)
24653 (spam-process ((ham spam-use-spamoracle)
24654 (spam spam-use-spamoracle))))
24656 For this group the @code{spam-use-spamoracle} is installed for both
24657 ham and spam processing. If the group contains spam message
24658 (e.g. because SpamOracle has not had enough sample messages yet) and
24659 the user marks some messages as spam messages, these messages will be
24660 processed by SpamOracle. The processor sends the messages to
24661 SpamOracle as new samples for spam.
24663 @node Extending the Spam ELisp package
24664 @subsubsection Extending the Spam ELisp package
24665 @cindex spam filtering
24666 @cindex spam elisp package, extending
24667 @cindex extending the spam elisp package
24669 Say you want to add a new back end called blackbox. For filtering
24670 incoming mail, provide the following:
24678 (defvar spam-use-blackbox nil
24679 "True if blackbox should be used.")
24682 Write @code{spam-check-blackbox} if Blackbox can check incoming mail.
24684 Write @code{spam-blackbox-register-routine} and
24685 @code{spam-blackbox-unregister-routine} using the bogofilter
24686 register/unregister routines as a start, or other restister/unregister
24687 routines more appropriate to Blackbox, if Blackbox can
24688 register/unregister spam and ham.
24693 The @code{spam-check-blackbox} function should return @samp{nil} or
24694 @code{spam-split-group}, observing the other conventions. See the
24695 existing @code{spam-check-*} functions for examples of what you can
24696 do, and stick to the template unless you fully understand the reasons
24701 For processing spam and ham messages, provide the following:
24708 Note you don't have to provide a spam or a ham processor. Only
24709 provide them if Blackbox supports spam or ham processing.
24711 Also, ham and spam processors are being phased out as single
24712 variables. Instead the form @code{(spam spam-use-blackbox)} or
24713 @code{(ham spam-use-blackbox)} is favored. For now, spam/ham
24714 processor variables are still around but they won't be for long.
24717 (defvar gnus-group-spam-exit-processor-blackbox "blackbox-spam"
24718 "The Blackbox summary exit spam processor.
24719 Only applicable to spam groups.")
24721 (defvar gnus-group-ham-exit-processor-blackbox "blackbox-ham"
24722 "The whitelist summary exit ham processor.
24723 Only applicable to non-spam (unclassified and ham) groups.")
24732 (const :tag "Spam: Blackbox" (spam spam-use-blackbox))
24733 (const :tag "Ham: Blackbox" (ham spam-use-blackbox))
24735 to the @code{spam-process} group parameter in @code{gnus.el}. Make
24736 sure you do it twice, once for the parameter and once for the
24737 variable customization.
24741 (variable-item spam-use-blackbox)
24743 to the @code{spam-autodetect-methods} group parameter in
24744 @code{gnus.el} if Blackbox can check incoming mail for spam contents.
24746 Finally, use the appropriate @code{spam-install-*-backend} function in
24747 @code{spam.el}. Here are the available functions.
24753 @code{spam-install-backend-alias}
24755 This function will simply install an alias for a back end that does
24756 everything like the original back end. It is currently only used to
24757 make @code{spam-use-BBDB-exclusive} act like @code{spam-use-BBDB}.
24760 @code{spam-install-nocheck-backend}
24762 This function installs a back end that has no check function, but can
24763 register/unregister ham or spam. The @code{spam-use-gmane} back end is
24767 @code{spam-install-checkonly-backend}
24769 This function will install a back end that can only check incoming mail
24770 for spam contents. It can't register or unregister messages.
24771 @code{spam-use-blackholes} and @code{spam-use-hashcash} are such
24775 @code{spam-install-statistical-checkonly-backend}
24777 This function installs a statistical back end (one which requires the
24778 full body of a message to check it) that can only check incoming mail
24779 for contents. @code{spam-use-regex-body} is such a filter.
24782 @code{spam-install-statistical-backend}
24784 This function install a statistical back end with incoming checks and
24785 registration/unregistration routines. @code{spam-use-bogofilter} is
24789 @code{spam-install-backend}
24791 This is the most normal back end installation, where a back end that can
24792 check and register/unregister messages is set up without statistical
24793 abilities. The @code{spam-use-BBDB} is such a back end.
24796 @code{spam-install-mover-backend}
24798 Mover back ends are internal to @code{spam.el} and specifically move
24799 articles around when the summary is exited. You will very probably
24800 never install such a back end.
24806 @node Filtering Spam Using Statistics with spam-stat
24807 @subsection Filtering Spam Using Statistics with spam-stat
24808 @cindex Paul Graham
24809 @cindex Graham, Paul
24810 @cindex naive Bayesian spam filtering
24811 @cindex Bayesian spam filtering, naive
24812 @cindex spam filtering, naive Bayesian
24814 Paul Graham has written an excellent essay about spam filtering using
24815 statistics: @uref{http://www.paulgraham.com/spam.html,A Plan for
24816 Spam}. In it he describes the inherent deficiency of rule-based
24817 filtering as used by SpamAssassin, for example: Somebody has to write
24818 the rules, and everybody else has to install these rules. You are
24819 always late. It would be much better, he argues, to filter mail based
24820 on whether it somehow resembles spam or non-spam. One way to measure
24821 this is word distribution. He then goes on to describe a solution
24822 that checks whether a new mail resembles any of your other spam mails
24825 The basic idea is this: Create a two collections of your mail, one
24826 with spam, one with non-spam. Count how often each word appears in
24827 either collection, weight this by the total number of mails in the
24828 collections, and store this information in a dictionary. For every
24829 word in a new mail, determine its probability to belong to a spam or a
24830 non-spam mail. Use the 15 most conspicuous words, compute the total
24831 probability of the mail being spam. If this probability is higher
24832 than a certain threshold, the mail is considered to be spam.
24834 Gnus supports this kind of filtering. But it needs some setting up.
24835 First, you need two collections of your mail, one with spam, one with
24836 non-spam. Then you need to create a dictionary using these two
24837 collections, and save it. And last but not least, you need to use
24838 this dictionary in your fancy mail splitting rules.
24841 * Creating a spam-stat dictionary::
24842 * Splitting mail using spam-stat::
24843 * Low-level interface to the spam-stat dictionary::
24846 @node Creating a spam-stat dictionary
24847 @subsubsection Creating a spam-stat dictionary
24849 Before you can begin to filter spam based on statistics, you must
24850 create these statistics based on two mail collections, one with spam,
24851 one with non-spam. These statistics are then stored in a dictionary
24852 for later use. In order for these statistics to be meaningful, you
24853 need several hundred emails in both collections.
24855 Gnus currently supports only the nnml back end for automated dictionary
24856 creation. The nnml back end stores all mails in a directory, one file
24857 per mail. Use the following:
24859 @defun spam-stat-process-spam-directory
24860 Create spam statistics for every file in this directory. Every file
24861 is treated as one spam mail.
24864 @defun spam-stat-process-non-spam-directory
24865 Create non-spam statistics for every file in this directory. Every
24866 file is treated as one non-spam mail.
24869 Usually you would call @code{spam-stat-process-spam-directory} on a
24870 directory such as @file{~/Mail/mail/spam} (this usually corresponds
24871 the the group @samp{nnml:mail.spam}), and you would call
24872 @code{spam-stat-process-non-spam-directory} on a directory such as
24873 @file{~/Mail/mail/misc} (this usually corresponds the the group
24874 @samp{nnml:mail.misc}).
24876 When you are using @acronym{IMAP}, you won't have the mails available
24877 locally, so that will not work. One solution is to use the Gnus Agent
24878 to cache the articles. Then you can use directories such as
24879 @file{"~/News/agent/nnimap/mail.yourisp.com/personal_spam"} for
24880 @code{spam-stat-process-spam-directory}. @xref{Agent as Cache}.
24883 This variable holds the hash-table with all the statistics---the
24884 dictionary we have been talking about. For every word in either
24885 collection, this hash-table stores a vector describing how often the
24886 word appeared in spam and often it appeared in non-spam mails.
24889 If you want to regenerate the statistics from scratch, you need to
24890 reset the dictionary.
24892 @defun spam-stat-reset
24893 Reset the @code{spam-stat} hash-table, deleting all the statistics.
24896 When you are done, you must save the dictionary. The dictionary may
24897 be rather large. If you will not update the dictionary incrementally
24898 (instead, you will recreate it once a month, for example), then you
24899 can reduce the size of the dictionary by deleting all words that did
24900 not appear often enough or that do not clearly belong to only spam or
24901 only non-spam mails.
24903 @defun spam-stat-reduce-size
24904 Reduce the size of the dictionary. Use this only if you do not want
24905 to update the dictionary incrementally.
24908 @defun spam-stat-save
24909 Save the dictionary.
24912 @defvar spam-stat-file
24913 The filename used to store the dictionary. This defaults to
24914 @file{~/.spam-stat.el}.
24917 @node Splitting mail using spam-stat
24918 @subsubsection Splitting mail using spam-stat
24920 In order to use @code{spam-stat} to split your mail, you need to add the
24921 following to your @file{~/.gnus.el} file:
24924 (require 'spam-stat)
24928 This will load the necessary Gnus code, and the dictionary you
24931 Next, you need to adapt your fancy splitting rules: You need to
24932 determine how to use @code{spam-stat}. The following examples are for
24933 the nnml back end. Using the nnimap back end works just as well. Just
24934 use @code{nnimap-split-fancy} instead of @code{nnmail-split-fancy}.
24936 In the simplest case, you only have two groups, @samp{mail.misc} and
24937 @samp{mail.spam}. The following expression says that mail is either
24938 spam or it should go into @samp{mail.misc}. If it is spam, then
24939 @code{spam-stat-split-fancy} will return @samp{mail.spam}.
24942 (setq nnmail-split-fancy
24943 `(| (: spam-stat-split-fancy)
24947 @defvar spam-stat-split-fancy-spam-group
24948 The group to use for spam. Default is @samp{mail.spam}.
24951 If you also filter mail with specific subjects into other groups, use
24952 the following expression. Only mails not matching the regular
24953 expression are considered potential spam.
24956 (setq nnmail-split-fancy
24957 `(| ("Subject" "\\bspam-stat\\b" "mail.emacs")
24958 (: spam-stat-split-fancy)
24962 If you want to filter for spam first, then you must be careful when
24963 creating the dictionary. Note that @code{spam-stat-split-fancy} must
24964 consider both mails in @samp{mail.emacs} and in @samp{mail.misc} as
24965 non-spam, therefore both should be in your collection of non-spam
24966 mails, when creating the dictionary!
24969 (setq nnmail-split-fancy
24970 `(| (: spam-stat-split-fancy)
24971 ("Subject" "\\bspam-stat\\b" "mail.emacs")
24975 You can combine this with traditional filtering. Here, we move all
24976 HTML-only mails into the @samp{mail.spam.filtered} group. Note that since
24977 @code{spam-stat-split-fancy} will never see them, the mails in
24978 @samp{mail.spam.filtered} should be neither in your collection of spam mails,
24979 nor in your collection of non-spam mails, when creating the
24983 (setq nnmail-split-fancy
24984 `(| ("Content-Type" "text/html" "mail.spam.filtered")
24985 (: spam-stat-split-fancy)
24986 ("Subject" "\\bspam-stat\\b" "mail.emacs")
24991 @node Low-level interface to the spam-stat dictionary
24992 @subsubsection Low-level interface to the spam-stat dictionary
24994 The main interface to using @code{spam-stat}, are the following functions:
24996 @defun spam-stat-buffer-is-spam
24997 Called in a buffer, that buffer is considered to be a new spam mail.
24998 Use this for new mail that has not been processed before.
25001 @defun spam-stat-buffer-is-no-spam
25002 Called in a buffer, that buffer is considered to be a new non-spam
25003 mail. Use this for new mail that has not been processed before.
25006 @defun spam-stat-buffer-change-to-spam
25007 Called in a buffer, that buffer is no longer considered to be normal
25008 mail but spam. Use this to change the status of a mail that has
25009 already been processed as non-spam.
25012 @defun spam-stat-buffer-change-to-non-spam
25013 Called in a buffer, that buffer is no longer considered to be spam but
25014 normal mail. Use this to change the status of a mail that has already
25015 been processed as spam.
25018 @defun spam-stat-save
25019 Save the hash table to the file. The filename used is stored in the
25020 variable @code{spam-stat-file}.
25023 @defun spam-stat-load
25024 Load the hash table from a file. The filename used is stored in the
25025 variable @code{spam-stat-file}.
25028 @defun spam-stat-score-word
25029 Return the spam score for a word.
25032 @defun spam-stat-score-buffer
25033 Return the spam score for a buffer.
25036 @defun spam-stat-split-fancy
25037 Use this function for fancy mail splitting. Add the rule @samp{(:
25038 spam-stat-split-fancy)} to @code{nnmail-split-fancy}
25041 Make sure you load the dictionary before using it. This requires the
25042 following in your @file{~/.gnus.el} file:
25045 (require 'spam-stat)
25049 Typical test will involve calls to the following functions:
25052 Reset: (setq spam-stat (make-hash-table :test 'equal))
25053 Learn spam: (spam-stat-process-spam-directory "~/Mail/mail/spam")
25054 Learn non-spam: (spam-stat-process-non-spam-directory "~/Mail/mail/misc")
25055 Save table: (spam-stat-save)
25056 File size: (nth 7 (file-attributes spam-stat-file))
25057 Number of words: (hash-table-count spam-stat)
25058 Test spam: (spam-stat-test-directory "~/Mail/mail/spam")
25059 Test non-spam: (spam-stat-test-directory "~/Mail/mail/misc")
25060 Reduce table size: (spam-stat-reduce-size)
25061 Save table: (spam-stat-save)
25062 File size: (nth 7 (file-attributes spam-stat-file))
25063 Number of words: (hash-table-count spam-stat)
25064 Test spam: (spam-stat-test-directory "~/Mail/mail/spam")
25065 Test non-spam: (spam-stat-test-directory "~/Mail/mail/misc")
25068 Here is how you would create your dictionary:
25071 Reset: (setq spam-stat (make-hash-table :test 'equal))
25072 Learn spam: (spam-stat-process-spam-directory "~/Mail/mail/spam")
25073 Learn non-spam: (spam-stat-process-non-spam-directory "~/Mail/mail/misc")
25074 Repeat for any other non-spam group you need...
25075 Reduce table size: (spam-stat-reduce-size)
25076 Save table: (spam-stat-save)
25080 @section Interaction with other modes
25085 @code{gnus-dired-minor-mode} provided some useful functions for dired
25086 buffers. It is enabled with
25088 (add-hook 'dired-mode-hook 'turn-on-gnus-dired-mode)
25093 @findex gnus-dired-attach
25094 Send dired's marked files as an attachment (@code{gnus-dired-attach}).
25095 You will be prompted for a message buffer.
25098 @findex gnus-dired-find-file-mailcap
25099 Visit a file according to the appropriate mailcap entry
25100 (@code{gnus-dired-find-file-mailcap}). With prefix, open file in a new
25104 @findex gnus-dired-print
25105 Print file according to the mailcap entry (@code{gnus-dired-print}). If
25106 there is no print command, print in a PostScript image.
25109 @node Various Various
25110 @section Various Various
25116 @item gnus-home-directory
25117 @vindex gnus-home-directory
25118 All Gnus file and directory variables will be initialized from this
25119 variable, which defaults to @file{~/}.
25121 @item gnus-directory
25122 @vindex gnus-directory
25123 Most Gnus storage file and directory variables will be initialized from
25124 this variable, which defaults to the @env{SAVEDIR} environment
25125 variable, or @file{~/News/} if that variable isn't set.
25127 Note that Gnus is mostly loaded when the @file{~/.gnus.el} file is read.
25128 This means that other directory variables that are initialized from this
25129 variable won't be set properly if you set this variable in
25130 @file{~/.gnus.el}. Set this variable in @file{.emacs} instead.
25132 @item gnus-default-directory
25133 @vindex gnus-default-directory
25134 Not related to the above variable at all---this variable says what the
25135 default directory of all Gnus buffers should be. If you issue commands
25136 like @kbd{C-x C-f}, the prompt you'll get starts in the current buffer's
25137 default directory. If this variable is @code{nil} (which is the
25138 default), the default directory will be the default directory of the
25139 buffer you were in when you started Gnus.
25142 @vindex gnus-verbose
25143 This variable is an integer between zero and ten. The higher the value,
25144 the more messages will be displayed. If this variable is zero, Gnus
25145 will never flash any messages, if it is seven (which is the default),
25146 most important messages will be shown, and if it is ten, Gnus won't ever
25147 shut up, but will flash so many messages it will make your head swim.
25149 @item gnus-verbose-backends
25150 @vindex gnus-verbose-backends
25151 This variable works the same way as @code{gnus-verbose}, but it applies
25152 to the Gnus back ends instead of Gnus proper.
25154 @item nnheader-max-head-length
25155 @vindex nnheader-max-head-length
25156 When the back ends read straight heads of articles, they all try to read
25157 as little as possible. This variable (default 8192) specifies
25158 the absolute max length the back ends will try to read before giving up
25159 on finding a separator line between the head and the body. If this
25160 variable is @code{nil}, there is no upper read bound. If it is
25161 @code{t}, the back ends won't try to read the articles piece by piece,
25162 but read the entire articles. This makes sense with some versions of
25163 @code{ange-ftp} or @code{efs}.
25165 @item nnheader-head-chop-length
25166 @vindex nnheader-head-chop-length
25167 This variable (default 2048) says how big a piece of each article to
25168 read when doing the operation described above.
25170 @item nnheader-file-name-translation-alist
25171 @vindex nnheader-file-name-translation-alist
25173 @cindex invalid characters in file names
25174 @cindex characters in file names
25175 This is an alist that says how to translate characters in file names.
25176 For instance, if @samp{:} is invalid as a file character in file names
25177 on your system (you OS/2 user you), you could say something like:
25181 (setq nnheader-file-name-translation-alist
25186 In fact, this is the default value for this variable on OS/2 and MS
25187 Windows (phooey) systems.
25189 @item gnus-hidden-properties
25190 @vindex gnus-hidden-properties
25191 This is a list of properties to use to hide ``invisible'' text. It is
25192 @code{(invisible t intangible t)} by default on most systems, which
25193 makes invisible text invisible and intangible.
25195 @item gnus-parse-headers-hook
25196 @vindex gnus-parse-headers-hook
25197 A hook called before parsing headers. It can be used, for instance, to
25198 gather statistics on the headers fetched, or perhaps you'd like to prune
25199 some headers. I don't see why you'd want that, though.
25201 @item gnus-shell-command-separator
25202 @vindex gnus-shell-command-separator
25203 String used to separate two shell commands. The default is @samp{;}.
25205 @item gnus-invalid-group-regexp
25206 @vindex gnus-invalid-group-regexp
25208 Regexp to match ``invalid'' group names when querying user for a group
25209 name. The default value catches some @strong{really} invalid group
25210 names who could possibly mess up Gnus internally (like allowing
25211 @samp{:} in a group name, which is normally used to delimit method and
25214 @acronym{IMAP} users might want to allow @samp{/} in group names though.
25222 Well, that's the manual---you can get on with your life now. Keep in
25223 touch. Say hello to your cats from me.
25225 My @strong{ghod}---I just can't stand goodbyes. Sniffle.
25227 Ol' Charles Reznikoff said it pretty well, so I leave the floor to him:
25233 Not because of victories @*
25236 but for the common sunshine,@*
25238 the largess of the spring.
25242 but for the day's work done@*
25243 as well as I was able;@*
25244 not for a seat upon the dais@*
25245 but at the common table.@*
25250 @chapter Appendices
25253 * XEmacs:: Requirements for installing under XEmacs.
25254 * History:: How Gnus got where it is today.
25255 * On Writing Manuals:: Why this is not a beginner's guide.
25256 * Terminology:: We use really difficult, like, words here.
25257 * Customization:: Tailoring Gnus to your needs.
25258 * Troubleshooting:: What you might try if things do not work.
25259 * Gnus Reference Guide:: Rilly, rilly technical stuff.
25260 * Emacs for Heathens:: A short introduction to Emacsian terms.
25261 * Frequently Asked Questions:: The Gnus FAQ
25268 @cindex installing under XEmacs
25270 XEmacs is distributed as a collection of packages. You should install
25271 whatever packages the Gnus XEmacs package requires. The current
25272 requirements are @samp{gnus}, @samp{mail-lib}, @samp{xemacs-base},
25273 @samp{eterm}, @samp{sh-script}, @samp{net-utils}, @samp{os-utils},
25274 @samp{dired}, @samp{mh-e}, @samp{sieve}, @samp{ps-print}, @samp{W3},
25275 @samp{pgg}, @samp{mailcrypt}, @samp{ecrypto}, and @samp{sasl}.
25282 @sc{gnus} was written by Masanobu @sc{Umeda}. When autumn crept up in
25283 '94, Lars Magne Ingebrigtsen grew bored and decided to rewrite Gnus.
25285 If you want to investigate the person responsible for this outrage,
25286 you can point your (feh!) web browser to
25287 @uref{http://quimby.gnus.org/}. This is also the primary
25288 distribution point for the new and spiffy versions of Gnus, and is
25289 known as The Site That Destroys Newsrcs And Drives People Mad.
25291 During the first extended alpha period of development, the new Gnus was
25292 called ``(ding) Gnus''. @dfn{(ding)} is, of course, short for
25293 @dfn{ding is not Gnus}, which is a total and utter lie, but who cares?
25294 (Besides, the ``Gnus'' in this abbreviation should probably be
25295 pronounced ``news'' as @sc{Umeda} intended, which makes it a more
25296 appropriate name, don't you think?)
25298 In any case, after spending all that energy on coming up with a new and
25299 spunky name, we decided that the name was @emph{too} spunky, so we
25300 renamed it back again to ``Gnus''. But in mixed case. ``Gnus'' vs.
25301 ``@sc{gnus}''. New vs. old.
25304 * Gnus Versions:: What Gnus versions have been released.
25305 * Other Gnus Versions:: Other Gnus versions that also have been released.
25306 * Why?:: What's the point of Gnus?
25307 * Compatibility:: Just how compatible is Gnus with @sc{gnus}?
25308 * Conformity:: Gnus tries to conform to all standards.
25309 * Emacsen:: Gnus can be run on a few modern Emacsen.
25310 * Gnus Development:: How Gnus is developed.
25311 * Contributors:: Oodles of people.
25312 * New Features:: Pointers to some of the new stuff in Gnus.
25316 @node Gnus Versions
25317 @subsection Gnus Versions
25319 @cindex September Gnus
25321 @cindex Quassia Gnus
25322 @cindex Pterodactyl Gnus
25325 @cindex Gnus versions
25327 The first ``proper'' release of Gnus 5 was done in November 1995 when it
25328 was included in the Emacs 19.30 distribution (132 (ding) Gnus releases
25329 plus 15 Gnus 5.0 releases).
25331 In May 1996 the next Gnus generation (aka. ``September Gnus'' (after 99
25332 releases)) was released under the name ``Gnus 5.2'' (40 releases).
25334 On July 28th 1996 work on Red Gnus was begun, and it was released on
25335 January 25th 1997 (after 84 releases) as ``Gnus 5.4'' (67 releases).
25337 On September 13th 1997, Quassia Gnus was started and lasted 37 releases.
25338 It was released as ``Gnus 5.6'' on March 8th 1998 (46 releases).
25340 Gnus 5.6 begat Pterodactyl Gnus on August 29th 1998 and was released as
25341 ``Gnus 5.8'' (after 99 releases and a CVS repository) on December 3rd
25344 On the 26th of October 2000, Oort Gnus was begun and was released as
25345 Gnus 5.10 on May 1st 2003 (24 releases).
25347 On the January 4th 2004, No Gnus was begun.
25349 If you happen upon a version of Gnus that has a prefixed name --
25350 ``(ding) Gnus'', ``September Gnus'', ``Red Gnus'', ``Quassia Gnus'',
25351 ``Pterodactyl Gnus'', ``Oort Gnus'', ``No Gnus'' -- don't panic.
25352 Don't let it know that you're frightened. Back away. Slowly. Whatever
25353 you do, don't run. Walk away, calmly, until you're out of its reach.
25354 Find a proper released version of Gnus and snuggle up to that instead.
25357 @node Other Gnus Versions
25358 @subsection Other Gnus Versions
25361 In addition to the versions of Gnus which have had their releases
25362 coordinated by Lars, one major development has been Semi-gnus from
25363 Japan. It's based on a library called @acronym{SEMI}, which provides
25364 @acronym{MIME} capabilities.
25366 These Gnusae are based mainly on Gnus 5.6 and Pterodactyl Gnus.
25367 Collectively, they are called ``Semi-gnus'', and different strains are
25368 called T-gnus, ET-gnus, Nana-gnus and Chaos. These provide powerful
25369 @acronym{MIME} and multilingualization things, especially important for
25376 What's the point of Gnus?
25378 I want to provide a ``rad'', ``happening'', ``way cool'' and ``hep''
25379 newsreader, that lets you do anything you can think of. That was my
25380 original motivation, but while working on Gnus, it has become clear to
25381 me that this generation of newsreaders really belong in the stone age.
25382 Newsreaders haven't developed much since the infancy of the net. If the
25383 volume continues to rise with the current rate of increase, all current
25384 newsreaders will be pretty much useless. How do you deal with
25385 newsgroups that have thousands of new articles each day? How do you
25386 keep track of millions of people who post?
25388 Gnus offers no real solutions to these questions, but I would very much
25389 like to see Gnus being used as a testing ground for new methods of
25390 reading and fetching news. Expanding on @sc{Umeda}-san's wise decision
25391 to separate the newsreader from the back ends, Gnus now offers a simple
25392 interface for anybody who wants to write new back ends for fetching mail
25393 and news from different sources. I have added hooks for customizations
25394 everywhere I could imagine it being useful. By doing so, I'm inviting
25395 every one of you to explore and invent.
25397 May Gnus never be complete. @kbd{C-u 100 M-x all-hail-emacs} and
25398 @kbd{C-u 100 M-x all-hail-xemacs}.
25401 @node Compatibility
25402 @subsection Compatibility
25404 @cindex compatibility
25405 Gnus was designed to be fully compatible with @sc{gnus}. Almost all key
25406 bindings have been kept. More key bindings have been added, of course,
25407 but only in one or two obscure cases have old bindings been changed.
25412 @center In a cloud bones of steel.
25416 All commands have kept their names. Some internal functions have changed
25419 The @code{gnus-uu} package has changed drastically. @xref{Decoding
25422 One major compatibility question is the presence of several summary
25423 buffers. All variables relevant while reading a group are
25424 buffer-local to the summary buffer they belong in. Although many
25425 important variables have their values copied into their global
25426 counterparts whenever a command is executed in the summary buffer, this
25427 change might lead to incorrect values being used unless you are careful.
25429 All code that relies on knowledge of @sc{gnus} internals will probably
25430 fail. To take two examples: Sorting @code{gnus-newsrc-alist} (or
25431 changing it in any way, as a matter of fact) is strictly verboten. Gnus
25432 maintains a hash table that points to the entries in this alist (which
25433 speeds up many functions), and changing the alist directly will lead to
25437 @cindex highlighting
25438 Old hilit19 code does not work at all. In fact, you should probably
25439 remove all hilit code from all Gnus hooks
25440 (@code{gnus-group-prepare-hook} and @code{gnus-summary-prepare-hook}).
25441 Gnus provides various integrated functions for highlighting. These are
25442 faster and more accurate. To make life easier for everybody, Gnus will
25443 by default remove all hilit calls from all hilit hooks. Uncleanliness!
25446 Packages like @code{expire-kill} will no longer work. As a matter of
25447 fact, you should probably remove all old @sc{gnus} packages (and other
25448 code) when you start using Gnus. More likely than not, Gnus already
25449 does what you have written code to make @sc{gnus} do. (Snicker.)
25451 Even though old methods of doing things are still supported, only the
25452 new methods are documented in this manual. If you detect a new method of
25453 doing something while reading this manual, that does not mean you have
25454 to stop doing it the old way.
25456 Gnus understands all @sc{gnus} startup files.
25458 @kindex M-x gnus-bug
25460 @cindex reporting bugs
25462 Overall, a casual user who hasn't written much code that depends on
25463 @sc{gnus} internals should suffer no problems. If problems occur,
25464 please let me know by issuing that magic command @kbd{M-x gnus-bug}.
25466 @vindex gnus-bug-create-help-buffer
25467 If you are in the habit of sending bug reports @emph{very} often, you
25468 may find the helpful help buffer annoying after a while. If so, set
25469 @code{gnus-bug-create-help-buffer} to @code{nil} to avoid having it pop
25474 @subsection Conformity
25476 No rebels without a clue here, ma'am. We conform to all standards known
25477 to (wo)man. Except for those standards and/or conventions we disagree
25485 There are no known breaches of this standard.
25489 There are no known breaches of this standard, either.
25491 @item Son-of-RFC 1036
25492 @cindex Son-of-RFC 1036
25493 We do have some breaches to this one.
25499 These are considered to be ``vanity headers'', while I consider them
25500 to be consumer information. After seeing so many badly formatted
25501 articles coming from @code{tin} and @code{Netscape} I know not to use
25502 either of those for posting articles. I would not have known that if
25503 it wasn't for the @code{X-Newsreader} header.
25508 USEFOR is an IETF working group writing a successor to RFC 1036, based
25509 on Son-of-RFC 1036. They have produced a number of drafts proposing
25510 various changes to the format of news articles. The Gnus towers will
25511 look into implementing the changes when the draft is accepted as an RFC.
25513 @item MIME - RFC 2045-2049 etc
25514 @cindex @acronym{MIME}
25515 All the various @acronym{MIME} RFCs are supported.
25517 @item Disposition Notifications - RFC 2298
25518 Message Mode is able to request notifications from the receiver.
25520 @item PGP - RFC 1991 and RFC 2440
25523 RFC 1991 is the original @acronym{PGP} message specification,
25524 published as an informational RFC. RFC 2440 was the follow-up, now
25525 called Open PGP, and put on the Standards Track. Both document a
25526 non-@acronym{MIME} aware @acronym{PGP} format. Gnus supports both
25527 encoding (signing and encryption) and decoding (verification and
25530 @item PGP/MIME - RFC 2015/3156
25531 RFC 2015 (superseded by 3156 which references RFC 2440 instead of RFC
25532 1991) describes the @acronym{MIME}-wrapping around the RFC 1991/2440 format.
25533 Gnus supports both encoding and decoding.
25535 @item S/MIME - RFC 2633
25536 RFC 2633 describes the @acronym{S/MIME} format.
25538 @item IMAP - RFC 1730/2060, RFC 2195, RFC 2086, RFC 2359, RFC 2595, RFC 1731
25539 RFC 1730 is @acronym{IMAP} version 4, updated somewhat by RFC 2060
25540 (@acronym{IMAP} 4 revision 1). RFC 2195 describes CRAM-MD5
25541 authentication for @acronym{IMAP}. RFC 2086 describes access control
25542 lists (ACLs) for @acronym{IMAP}. RFC 2359 describes a @acronym{IMAP}
25543 protocol enhancement. RFC 2595 describes the proper @acronym{TLS}
25544 integration (STARTTLS) with @acronym{IMAP}. RFC 1731 describes the
25545 GSSAPI/Kerberos4 mechanisms for @acronym{IMAP}.
25549 If you ever notice Gnus acting non-compliant with regards to the texts
25550 mentioned above, don't hesitate to drop a note to Gnus Towers and let us
25555 @subsection Emacsen
25561 Gnus should work on:
25569 XEmacs 21.4 and up.
25573 This Gnus version will absolutely not work on any Emacsen older than
25574 that. Not reliably, at least. Older versions of Gnus may work on older
25577 There are some vague differences between Gnus on the various
25578 platforms---XEmacs features more graphics (a logo and a toolbar)---but
25579 other than that, things should look pretty much the same under all
25583 @node Gnus Development
25584 @subsection Gnus Development
25586 Gnus is developed in a two-phased cycle. The first phase involves much
25587 discussion on the @samp{ding@@gnus.org} mailing list, where people
25588 propose changes and new features, post patches and new back ends. This
25589 phase is called the @dfn{alpha} phase, since the Gnusae released in this
25590 phase are @dfn{alpha releases}, or (perhaps more commonly in other
25591 circles) @dfn{snapshots}. During this phase, Gnus is assumed to be
25592 unstable and should not be used by casual users. Gnus alpha releases
25593 have names like ``Red Gnus'' and ``Quassia Gnus''.
25595 After futzing around for 50-100 alpha releases, Gnus is declared
25596 @dfn{frozen}, and only bug fixes are applied. Gnus loses the prefix,
25597 and is called things like ``Gnus 5.6.32'' instead. Normal people are
25598 supposed to be able to use these, and these are mostly discussed on the
25599 @samp{gnu.emacs.gnus} newsgroup.
25602 @vindex mail-source-delete-incoming
25603 Some variable defaults differ between alpha Gnusae and released Gnusae.
25604 In particular, @code{mail-source-delete-incoming} defaults to @code{nil} in
25605 alpha Gnusae and @code{t} in released Gnusae. This is to prevent
25606 lossage of mail if an alpha release hiccups while handling the mail.
25608 The division of discussion between the ding mailing list and the Gnus
25609 newsgroup is not purely based on publicity concerns. It's true that
25610 having people write about the horrible things that an alpha Gnus release
25611 can do (sometimes) in a public forum may scare people off, but more
25612 importantly, talking about new experimental features that have been
25613 introduced may confuse casual users. New features are frequently
25614 introduced, fiddled with, and judged to be found wanting, and then
25615 either discarded or totally rewritten. People reading the mailing list
25616 usually keep up with these rapid changes, while people on the newsgroup
25617 can't be assumed to do so.
25622 @subsection Contributors
25623 @cindex contributors
25625 The new Gnus version couldn't have been done without the help of all the
25626 people on the (ding) mailing list. Every day for over a year I have
25627 gotten billions of nice bug reports from them, filling me with joy,
25628 every single one of them. Smooches. The people on the list have been
25629 tried beyond endurance, what with my ``oh, that's a neat idea <type
25630 type>, yup, I'll release it right away <ship off> no wait, that doesn't
25631 work at all <type type>, yup, I'll ship that one off right away <ship
25632 off> no, wait, that absolutely does not work'' policy for releases.
25633 Micro$oft---bah. Amateurs. I'm @emph{much} worse. (Or is that
25634 ``worser''? ``much worser''? ``worsest''?)
25636 I would like to take this opportunity to thank the Academy for@dots{} oops,
25642 Masanobu @sc{Umeda}---the writer of the original @sc{gnus}.
25645 Shenghuo Zhu---uudecode.el, mm-uu.el, rfc1843.el, webmail.el,
25646 nnwarchive and many, many other things connected with @acronym{MIME} and
25647 other types of en/decoding, as well as general bug fixing, new
25648 functionality and stuff.
25651 Per Abrahamsen---custom, scoring, highlighting and @sc{soup} code (as
25652 well as numerous other things).
25655 Luis Fernandes---design and graphics.
25658 Joe Reiss---creator of the smiley faces.
25661 Justin Sheehy---the @acronym{FAQ} maintainer.
25664 Erik Naggum---help, ideas, support, code and stuff.
25667 Wes Hardaker---@file{gnus-picon.el} and the manual section on
25668 @dfn{picons} (@pxref{Picons}).
25671 Kim-Minh Kaplan---further work on the picon code.
25674 Brad Miller---@file{gnus-gl.el} and the GroupLens manual section.
25677 Sudish Joseph---innumerable bug fixes.
25680 Ilja Weis---@file{gnus-topic.el}.
25683 Steven L. Baur---lots and lots and lots of bugs detections and fixes.
25686 Vladimir Alexiev---the refcard and reference booklets.
25689 Felix Lee & Jamie Zawinski---I stole some pieces from the XGnus
25690 distribution by Felix Lee and JWZ.
25693 Scott Byer---@file{nnfolder.el} enhancements & rewrite.
25696 Peter Mutsaers---orphan article scoring code.
25699 Ken Raeburn---POP mail support.
25702 Hallvard B Furuseth---various bits and pieces, especially dealing with
25706 Brian Edmonds---@file{gnus-bbdb.el}.
25709 David Moore---rewrite of @file{nnvirtual.el} and many other things.
25712 Kevin Davidson---came up with the name @dfn{ding}, so blame him.
25715 Fran@,{c}ois Pinard---many, many interesting and thorough bug reports, as
25716 well as autoconf support.
25720 This manual was proof-read by Adrian Aichner, with Ricardo Nassif, Mark
25721 Borges, and Jost Krieger proof-reading parts of the manual.
25723 The following people have contributed many patches and suggestions:
25738 Jason L. Tibbitts, III,
25740 Katsumi Yamaoka, @c Yamaoka
25744 Also thanks to the following for patches and stuff:
25754 Alexei V. Barantsev,
25769 Massimo Campostrini,
25774 Jae-you Chung, @c ?
25775 James H. Cloos, Jr.,
25779 Andrew J. Cosgriff,
25782 Geoffrey T. Dairiki,
25788 Michael Welsh Duggan,
25793 Enami Tsugutomo, @c Enami
25797 Nelson Jose dos Santos Ferreira,
25805 Arne Georg Gleditsch,
25807 Michelangelo Grigni,
25811 Kenichi Handa, @c Handa
25813 Yoshiki Hayashi, @c Hayashi
25815 Hisashige Kenji, @c Hisashige
25822 Fran@,{c}ois Felix Ingrand,
25823 Tatsuya Ichikawa, @c Ichikawa
25824 Ishikawa Ichiro, @c Ishikawa
25826 Iwamuro Motonori, @c Iwamuro
25836 Peter Skov Knudsen,
25837 Shuhei Kobayashi, @c Kobayashi
25839 Koseki Yoshinori, @c Koseki
25840 Thor Kristoffersen,
25843 Seokchan Lee, @c Lee
25861 Morioka Tomohiko, @c Morioka
25862 Erik Toubro Nielsen,
25869 Masaharu Onishi, @c Onishi
25874 Jens-Ulrik Holger Petersen,
25878 John McClary Prevost,
25884 Lars Balker Rasmussen,
25889 Christian von Roques,
25892 Wolfgang Rupprecht,
25899 Philippe Schnoebelen,
25901 Randal L. Schwartz,
25915 Kiyokazu Suto, @c Suto
25920 Tozawa Akihiko, @c Tozawa
25940 For a full overview of what each person has done, the ChangeLogs
25941 included in the Gnus alpha distributions should give ample reading
25942 (550kB and counting).
25944 Apologies to everybody that I've forgotten, of which there are many, I'm
25947 Gee, that's quite a list of people. I guess that must mean that there
25948 actually are people who are using Gnus. Who'd'a thunk it!
25952 @subsection New Features
25953 @cindex new features
25956 * ding Gnus:: New things in Gnus 5.0/5.1, the first new Gnus.
25957 * September Gnus:: The Thing Formally Known As Gnus 5.2/5.3.
25958 * Red Gnus:: Third time best---Gnus 5.4/5.5.
25959 * Quassia Gnus:: Two times two is four, or Gnus 5.6/5.7.
25960 * Pterodactyl Gnus:: Pentad also starts with P, AKA Gnus 5.8/5.9.
25961 * Oort Gnus:: It's big. It's far out. Gnus 5.10/5.11.
25962 * No Gnus:: Very punny.
25965 These lists are, of course, just @emph{short} overviews of the
25966 @emph{most} important new features. No, really. There are tons more.
25967 Yes, we have feeping creaturism in full effect.
25970 @subsubsection (ding) Gnus
25972 New features in Gnus 5.0/5.1:
25977 The look of all buffers can be changed by setting format-like variables
25978 (@pxref{Group Buffer Format} and @pxref{Summary Buffer Format}).
25981 Local spool and several @acronym{NNTP} servers can be used at once
25982 (@pxref{Select Methods}).
25985 You can combine groups into virtual groups (@pxref{Virtual Groups}).
25988 You can read a number of different mail formats (@pxref{Getting Mail}).
25989 All the mail back ends implement a convenient mail expiry scheme
25990 (@pxref{Expiring Mail}).
25993 Gnus can use various strategies for gathering threads that have lost
25994 their roots (thereby gathering loose sub-threads into one thread) or it
25995 can go back and retrieve enough headers to build a complete thread
25996 (@pxref{Customizing Threading}).
25999 Killed groups can be displayed in the group buffer, and you can read
26000 them as well (@pxref{Listing Groups}).
26003 Gnus can do partial group updates---you do not have to retrieve the
26004 entire active file just to check for new articles in a few groups
26005 (@pxref{The Active File}).
26008 Gnus implements a sliding scale of subscribedness to groups
26009 (@pxref{Group Levels}).
26012 You can score articles according to any number of criteria
26013 (@pxref{Scoring}). You can even get Gnus to find out how to score
26014 articles for you (@pxref{Adaptive Scoring}).
26017 Gnus maintains a dribble buffer that is auto-saved the normal Emacs
26018 manner, so it should be difficult to lose much data on what you have
26019 read if your machine should go down (@pxref{Auto Save}).
26022 Gnus now has its own startup file (@file{~/.gnus.el}) to avoid
26023 cluttering up the @file{.emacs} file.
26026 You can set the process mark on both groups and articles and perform
26027 operations on all the marked items (@pxref{Process/Prefix}).
26030 You can grep through a subset of groups and create a group from the
26031 results (@pxref{Kibozed Groups}).
26034 You can list subsets of groups according to, well, anything
26035 (@pxref{Listing Groups}).
26038 You can browse foreign servers and subscribe to groups from those
26039 servers (@pxref{Browse Foreign Server}).
26042 Gnus can fetch articles, asynchronously, on a second connection to the
26043 server (@pxref{Asynchronous Fetching}).
26046 You can cache articles locally (@pxref{Article Caching}).
26049 The uudecode functions have been expanded and generalized
26050 (@pxref{Decoding Articles}).
26053 You can still post uuencoded articles, which was a little-known feature
26054 of @sc{gnus}' past (@pxref{Uuencoding and Posting}).
26057 Fetching parents (and other articles) now actually works without
26058 glitches (@pxref{Finding the Parent}).
26061 Gnus can fetch @acronym{FAQ}s and group descriptions (@pxref{Group Information}).
26064 Digests (and other files) can be used as the basis for groups
26065 (@pxref{Document Groups}).
26068 Articles can be highlighted and customized (@pxref{Customizing
26072 URLs and other external references can be buttonized (@pxref{Article
26076 You can do lots of strange stuff with the Gnus window & frame
26077 configuration (@pxref{Window Layout}).
26080 You can click on buttons instead of using the keyboard
26086 @node September Gnus
26087 @subsubsection September Gnus
26091 \gnusfig{-28cm}{0cm}{\epsfig{figure=ps/september,height=20cm}}
26095 New features in Gnus 5.2/5.3:
26100 A new message composition mode is used. All old customization variables
26101 for @code{mail-mode}, @code{rnews-reply-mode} and @code{gnus-msg} are
26105 Gnus is now able to generate @dfn{sparse} threads---threads where
26106 missing articles are represented by empty nodes (@pxref{Customizing
26110 (setq gnus-build-sparse-threads 'some)
26114 Outgoing articles are stored on a special archive server
26115 (@pxref{Archived Messages}).
26118 Partial thread regeneration now happens when articles are
26122 Gnus can make use of GroupLens predictions.
26125 Picons (personal icons) can be displayed under XEmacs (@pxref{Picons}).
26128 A @code{trn}-like tree buffer can be displayed (@pxref{Tree Display}).
26131 (setq gnus-use-trees t)
26135 An @code{nn}-like pick-and-read minor mode is available for the summary
26136 buffers (@pxref{Pick and Read}).
26139 (add-hook 'gnus-summary-mode-hook 'gnus-pick-mode)
26143 In binary groups you can use a special binary minor mode (@pxref{Binary
26147 Groups can be grouped in a folding topic hierarchy (@pxref{Group
26151 (add-hook 'gnus-group-mode-hook 'gnus-topic-mode)
26155 Gnus can re-send and bounce mail (@pxref{Summary Mail Commands}).
26158 Groups can now have a score, and bubbling based on entry frequency
26159 is possible (@pxref{Group Score}).
26162 (add-hook 'gnus-summary-exit-hook 'gnus-summary-bubble-group)
26166 Groups can be process-marked, and commands can be performed on
26167 groups of groups (@pxref{Marking Groups}).
26170 Caching is possible in virtual groups.
26173 @code{nndoc} now understands all kinds of digests, mail boxes, rnews
26174 news batches, ClariNet briefs collections, and just about everything
26175 else (@pxref{Document Groups}).
26178 Gnus has a new back end (@code{nnsoup}) to create/read SOUP packets
26182 The Gnus cache is much faster.
26185 Groups can be sorted according to many criteria (@pxref{Sorting
26189 New group parameters have been introduced to set list-addresses and
26190 expiry times (@pxref{Group Parameters}).
26193 All formatting specs allow specifying faces to be used
26194 (@pxref{Formatting Fonts}).
26197 There are several more commands for setting/removing/acting on process
26198 marked articles on the @kbd{M P} submap (@pxref{Setting Process Marks}).
26201 The summary buffer can be limited to show parts of the available
26202 articles based on a wide range of criteria. These commands have been
26203 bound to keys on the @kbd{/} submap (@pxref{Limiting}).
26206 Articles can be made persistent with the @kbd{*} command
26207 (@pxref{Persistent Articles}).
26210 All functions for hiding article elements are now toggles.
26213 Article headers can be buttonized (@pxref{Article Washing}).
26216 All mail back ends support fetching articles by @code{Message-ID}.
26219 Duplicate mail can now be treated properly (@pxref{Duplicates}).
26222 All summary mode commands are available directly from the article
26223 buffer (@pxref{Article Keymap}).
26226 Frames can be part of @code{gnus-buffer-configuration} (@pxref{Window
26230 Mail can be re-scanned by a daemonic process (@pxref{Daemons}).
26233 \marginpar[\mbox{}\hfill\epsfig{figure=ps/fseptember,height=5cm}]{\epsfig{figure=ps/fseptember,height=5cm}}
26238 Gnus can make use of NoCeM files to weed out spam (@pxref{NoCeM}).
26241 (setq gnus-use-nocem t)
26245 Groups can be made permanently visible (@pxref{Listing Groups}).
26248 (setq gnus-permanently-visible-groups "^nnml:")
26252 Many new hooks have been introduced to make customizing easier.
26255 Gnus respects the @code{Mail-Copies-To} header.
26258 Threads can be gathered by looking at the @code{References} header
26259 (@pxref{Customizing Threading}).
26262 (setq gnus-summary-thread-gathering-function
26263 'gnus-gather-threads-by-references)
26267 Read articles can be stored in a special backlog buffer to avoid
26268 refetching (@pxref{Article Backlog}).
26271 (setq gnus-keep-backlog 50)
26275 A clean copy of the current article is always stored in a separate
26276 buffer to allow easier treatment.
26279 Gnus can suggest where to save articles (@pxref{Saving Articles}).
26282 Gnus doesn't have to do as much prompting when saving (@pxref{Saving
26286 (setq gnus-prompt-before-saving t)
26290 @code{gnus-uu} can view decoded files asynchronously while fetching
26291 articles (@pxref{Other Decode Variables}).
26294 (setq gnus-uu-grabbed-file-functions 'gnus-uu-grab-view)
26298 Filling in the article buffer now works properly on cited text
26299 (@pxref{Article Washing}).
26302 Hiding cited text adds buttons to toggle hiding, and how much
26303 cited text to hide is now customizable (@pxref{Article Hiding}).
26306 (setq gnus-cited-lines-visible 2)
26310 Boring headers can be hidden (@pxref{Article Hiding}).
26313 Default scoring values can now be set from the menu bar.
26316 Further syntax checking of outgoing articles have been added.
26322 @subsubsection Red Gnus
26324 New features in Gnus 5.4/5.5:
26328 \gnusfig{-5.5cm}{-4cm}{\epsfig{figure=ps/red,height=20cm}}
26335 @file{nntp.el} has been totally rewritten in an asynchronous fashion.
26338 Article prefetching functionality has been moved up into
26339 Gnus (@pxref{Asynchronous Fetching}).
26342 Scoring can now be performed with logical operators like @code{and},
26343 @code{or}, @code{not}, and parent redirection (@pxref{Advanced
26347 Article washing status can be displayed in the
26348 article mode line (@pxref{Misc Article}).
26351 @file{gnus.el} has been split into many smaller files.
26354 Suppression of duplicate articles based on Message-ID can be done
26355 (@pxref{Duplicate Suppression}).
26358 (setq gnus-suppress-duplicates t)
26362 New variables for specifying what score and adapt files are to be
26363 considered home score and adapt files (@pxref{Home Score File}) have
26367 @code{nndoc} was rewritten to be easily extendable (@pxref{Document
26368 Server Internals}).
26371 Groups can inherit group parameters from parent topics (@pxref{Topic
26375 Article editing has been revamped and is now actually usable.
26378 Signatures can be recognized in more intelligent fashions
26379 (@pxref{Article Signature}).
26382 Summary pick mode has been made to look more @code{nn}-like. Line
26383 numbers are displayed and the @kbd{.} command can be used to pick
26384 articles (@code{Pick and Read}).
26387 Commands for moving the @file{.newsrc.eld} from one server to
26388 another have been added (@pxref{Changing Servers}).
26391 There's a way now to specify that ``uninteresting'' fields be suppressed
26392 when generating lines in buffers (@pxref{Advanced Formatting}).
26395 Several commands in the group buffer can be undone with @kbd{C-M-_}
26399 Scoring can be done on words using the new score type @code{w}
26400 (@pxref{Score File Format}).
26403 Adaptive scoring can be done on a Subject word-by-word basis
26404 (@pxref{Adaptive Scoring}).
26407 (setq gnus-use-adaptive-scoring '(word))
26411 Scores can be decayed (@pxref{Score Decays}).
26414 (setq gnus-decay-scores t)
26418 Scoring can be performed using a regexp on the Date header. The Date is
26419 normalized to compact ISO 8601 format first (@pxref{Score File Format}).
26422 A new command has been added to remove all data on articles from
26423 the native server (@pxref{Changing Servers}).
26426 A new command for reading collections of documents
26427 (@code{nndoc} with @code{nnvirtual} on top) has been added---@kbd{C-M-d}
26428 (@pxref{Really Various Summary Commands}).
26431 Process mark sets can be pushed and popped (@pxref{Setting Process
26435 A new mail-to-news back end makes it possible to post even when the @acronym{NNTP}
26436 server doesn't allow posting (@pxref{Mail-To-News Gateways}).
26439 A new back end for reading searches from Web search engines
26440 (@dfn{DejaNews}, @dfn{Alta Vista}, @dfn{InReference}) has been added
26441 (@pxref{Web Searches}).
26444 Groups inside topics can now be sorted using the standard sorting
26445 functions, and each topic can be sorted independently (@pxref{Topic
26449 Subsets of the groups can be sorted independently (@code{Sorting
26453 Cached articles can be pulled into the groups (@pxref{Summary Generation
26457 \marginpar[\mbox{}\hfill\epsfig{figure=ps/fred,width=3cm}]{\epsfig{figure=ps/fred,width=3cm}}
26462 Score files are now applied in a more reliable order (@pxref{Score
26466 Reports on where mail messages end up can be generated (@pxref{Splitting
26470 More hooks and functions have been added to remove junk from incoming
26471 mail before saving the mail (@pxref{Washing Mail}).
26474 Emphasized text can be properly fontisized:
26480 @subsubsection Quassia Gnus
26482 New features in Gnus 5.6:
26487 New functionality for using Gnus as an offline newsreader has been
26488 added. A plethora of new commands and modes have been added.
26489 @xref{Gnus Unplugged}, for the full story.
26492 The @code{nndraft} back end has returned, but works differently than
26493 before. All Message buffers are now also articles in the @code{nndraft}
26494 group, which is created automatically.
26497 @code{gnus-alter-header-function} can now be used to alter header
26501 @code{gnus-summary-goto-article} now accept Message-ID's.
26504 A new Message command for deleting text in the body of a message
26505 outside the region: @kbd{C-c C-v}.
26508 You can now post to component group in @code{nnvirtual} groups with
26512 @code{nntp-rlogin-program}---new variable to ease customization.
26515 @code{C-u C-c C-c} in @code{gnus-article-edit-mode} will now inhibit
26516 re-highlighting of the article buffer.
26519 New element in @code{gnus-boring-article-headers}---@code{long-to}.
26522 @kbd{M-i} symbolic prefix command. @xref{Symbolic Prefixes}, for
26526 @kbd{L} and @kbd{I} in the summary buffer now take the symbolic prefix
26527 @kbd{a} to add the score rule to the @file{all.SCORE} file.
26530 @code{gnus-simplify-subject-functions} variable to allow greater
26531 control over simplification.
26534 @kbd{A T}---new command for fetching the current thread.
26537 @kbd{/ T}---new command for including the current thread in the
26541 @kbd{M-RET} is a new Message command for breaking cited text.
26544 @samp{\\1}-expressions are now valid in @code{nnmail-split-methods}.
26547 The @code{custom-face-lookup} function has been removed.
26548 If you used this function in your initialization files, you must
26549 rewrite them to use @code{face-spec-set} instead.
26552 Canceling now uses the current select method. Symbolic prefix
26553 @kbd{a} forces normal posting method.
26556 New command to translate M******** sm*rtq**t*s into proper
26560 For easier debugging of @code{nntp}, you can set
26561 @code{nntp-record-commands} to a non-@code{nil} value.
26564 @code{nntp} now uses @file{~/.authinfo}, a @file{.netrc}-like file, for
26565 controlling where and how to send @sc{authinfo} to @acronym{NNTP} servers.
26568 A command for editing group parameters from the summary buffer
26572 A history of where mails have been split is available.
26575 A new article date command has been added---@code{article-date-iso8601}.
26578 Subjects can be simplified when threading by setting
26579 @code{gnus-score-thread-simplify}.
26582 A new function for citing in Message has been
26583 added---@code{message-cite-original-without-signature}.
26586 @code{article-strip-all-blank-lines}---new article command.
26589 A new Message command to kill to the end of the article has
26593 A minimum adaptive score can be specified by using the
26594 @code{gnus-adaptive-word-minimum} variable.
26597 The ``lapsed date'' article header can be kept continually
26598 updated by the @code{gnus-start-date-timer} command.
26601 Web listserv archives can be read with the @code{nnlistserv} back end.
26604 Old dejanews archives can now be read by @code{nnweb}.
26608 @node Pterodactyl Gnus
26609 @subsubsection Pterodactyl Gnus
26611 New features in Gnus 5.8:
26616 The mail-fetching functions have changed. See the manual for the
26617 many details. In particular, all procmail fetching variables are gone.
26619 If you used procmail like in
26622 (setq nnmail-use-procmail t)
26623 (setq nnmail-spool-file 'procmail)
26624 (setq nnmail-procmail-directory "~/mail/incoming/")
26625 (setq nnmail-procmail-suffix "\\.in")
26628 this now has changed to
26632 '((directory :path "~/mail/incoming/"
26636 @xref{Mail Source Specifiers}.
26639 Gnus is now a @acronym{MIME}-capable reader. This affects many parts of
26640 Gnus, and adds a slew of new commands. See the manual for details.
26643 Gnus has also been multilingualized. This also affects too
26644 many parts of Gnus to summarize here, and adds many new variables.
26647 @code{gnus-auto-select-first} can now be a function to be
26648 called to position point.
26651 The user can now decide which extra headers should be included in
26652 summary buffers and @acronym{NOV} files.
26655 @code{gnus-article-display-hook} has been removed. Instead, a number
26656 of variables starting with @code{gnus-treat-} have been added.
26659 The Gnus posting styles have been redone again and now works in a
26660 subtly different manner.
26663 New web-based back ends have been added: @code{nnslashdot},
26664 @code{nnwarchive} and @code{nnultimate}. nnweb has been revamped,
26665 again, to keep up with ever-changing layouts.
26668 Gnus can now read @acronym{IMAP} mail via @code{nnimap}.
26673 @subsubsection Oort Gnus
26676 New features in Gnus 5.10:
26681 @kbd{F} (@code{gnus-article-followup-with-original}) and @kbd{R}
26682 (@code{gnus-article-reply-with-original}) only yank the text in the
26683 region if the region is active.
26686 @code{gnus-group-read-ephemeral-group} can be called interactively,
26690 In draft groups, @kbd{e} is now bound to @code{gnus-draft-edit-message}.
26691 Use @kbd{B w} for @code{gnus-summary-edit-article} instead.
26694 The revised Gnus @acronym{FAQ} is included in the manual,
26695 @xref{Frequently Asked Questions}.
26698 Upgrading from previous (stable) version if you have used Oort.
26700 If you have tried Oort (the unstable Gnus branch leading to this
26701 release) but went back to a stable version, be careful when upgrading to
26702 this version. In particular, you will probably want to remove all
26703 @file{.marks} (nnml) and @file{.mrk} (nnfolder) files, so that flags are
26704 read from your @file{.newsrc.eld} instead of from the
26705 @file{.marks}/@file{.mrk} file where this release store flags. See a
26706 later entry for more information about marks. Note that downgrading
26707 isn't save in general.
26712 More buttons for URLs, mail addresses, Message-IDs, Info links, man
26713 pages and Emacs or Gnus related references. @xref{Article Buttons}. The
26714 variables @code{gnus-button-@var{*}-level} can be used to control the
26715 appearance of all article buttons. @xref{Article Button Levels}.
26720 @code{gnus-dired-minor-mode} (see @ref{Other modes}) installs key
26721 bindings in dired buffers to send a file as an attachment, open a file
26722 using the appropriate mailcap entry, and print a file using the mailcap
26726 Gnus can display RSS newsfeeds as a newsgroup. @xref{RSS}.
26729 Single-part yenc encoded attachments can be decoded.
26734 The picons code has been reimplemented to work in GNU Emacs---some of
26735 the previous options have been removed or renamed.
26737 Picons are small ``personal icons'' representing users, domain and
26738 newsgroups, which can be displayed in the Article buffer.
26742 If the new option @code{gnus-treat-body-boundary} is non-@code{nil}, a
26743 boundary line is drawn at the end of the headers.
26746 Retrieval of charters and control messages
26748 There are new commands for fetching newsgroup charters (@kbd{H c}) and
26749 control messages (@kbd{H C}).
26754 You can delay the sending of a message with @kbd{C-c C-j} in the Message
26755 buffer. The messages are delivered at specified time. This is useful
26756 for sending yourself reminders. @xref{Delayed Articles}.
26759 If @code{auto-compression-mode} is enabled, attachments are automatically
26760 decompressed when activated.
26763 If the new option @code{nnml-use-compressed-files} is non-@code{nil},
26764 the nnml back end allows compressed message files.
26767 Signed article headers (X-PGP-Sig) can be verified with @kbd{W p}.
26770 The Summary Buffer uses an arrow in the fringe to indicate the current
26771 article. Use @code{(setq gnus-summary-display-arrow nil)} to disable it.
26774 Warn about email replies to news
26776 Do you often find yourself replying to news by email by mistake? Then
26777 the new option @code{gnus-confirm-mail-reply-to-news} is just the thing for
26781 If the new option @code{gnus-summary-display-while-building} is
26782 non-@code{nil}, the summary buffer is shown and updated as it's being
26786 The new @code{recent} mark @samp{.} indicates newly arrived messages (as
26787 opposed to old but unread messages).
26790 The new option @code{gnus-gcc-mark-as-read} automatically marks
26791 Gcc articles as read.
26794 The nndoc back end now supports mailman digests and exim bounces.
26797 Gnus supports RFC 2369 mailing list headers, and adds a number of
26798 related commands in mailing list groups. @xref{Mailing List}.
26801 The Date header can be displayed in a format that can be read aloud
26802 in English. @xref{Article Date}.
26805 The envelope sender address can be customized when using Sendmail.
26806 @xref{Mail Variables, Mail Variables,, message, Message Manual}.
26809 diffs are automatically highlighted in groups matching
26810 @code{mm-uu-diff-groups-regexp}
26813 @acronym{TLS} wrapper shipped with Gnus
26815 @acronym{TLS}/@acronym{SSL} is now supported in @acronym{IMAP} and
26816 @acronym{NNTP} via @file{tls.el} and GNUTLS. The old
26817 @acronym{TLS}/@acronym{SSL} support via (external third party)
26818 @file{ssl.el} and OpenSSL still works.
26821 New @file{make.bat} for compiling and installing Gnus under MS Windows
26823 Use @file{make.bat} if you want to install Gnus under MS Windows, the
26824 first argument to the batch-program should be the directory where
26825 @file{xemacs.exe} respectively @file{emacs.exe} is located, iff you want
26826 to install Gnus after compiling it, give @file{make.bat} @code{/copy} as
26827 the second parameter.
26829 @file{make.bat} has been rewritten from scratch, it now features
26830 automatic recognition of XEmacs and GNU Emacs, generates
26831 @file{gnus-load.el}, checks if errors occur while compilation and
26832 generation of info files and reports them at the end of the build
26833 process. It now uses @code{makeinfo} if it is available and falls
26834 back to @file{infohack.el} otherwise. @file{make.bat} should now
26835 install all files which are necessary to run Gnus and be generally a
26836 complete replacement for the @code{configure; make; make install}
26837 cycle used under Unix systems.
26839 The new @file{make.bat} makes @file{make-x.bat} superfluous, so it has
26843 Support for non-@acronym{ASCII} domain names
26845 Message supports non-@acronym{ASCII} domain names in From:, To: and
26846 Cc: and will query you whether to perform encoding when you try to
26847 send a message. The variable @code{message-use-idna} controls this.
26848 Gnus will also decode non-@acronym{ASCII} domain names in From:, To:
26849 and Cc: when you view a message. The variable @code{gnus-use-idna}
26853 Better handling of Microsoft citation styles
26855 Gnus now tries to recognize the mangled header block that some Microsoft
26856 mailers use to indicate that the rest of the message is a citation, even
26857 though it is not quoted in any way. The variable
26858 @code{gnus-cite-unsightly-citation-regexp} matches the start of these
26862 @code{gnus-article-skip-boring}
26864 If you set @code{gnus-article-skip-boring} to @code{t}, then Gnus will
26865 not scroll down to show you a page that contains only boring text,
26866 which by default means cited text and signature. You can customize
26867 what is skippable using @code{gnus-article-boring-faces}.
26869 This feature is especially useful if you read many articles that
26870 consist of a little new content at the top with a long, untrimmed
26871 message cited below.
26874 The format spec @code{%C} for positioning point has changed to @code{%*}.
26877 The new variable @code{gnus-parameters} can be used to set group parameters.
26879 Earlier this was done only via @kbd{G p} (or @kbd{G c}), which stored
26880 the parameters in @file{~/.newsrc.eld}, but via this variable you can
26881 enjoy the powers of customize, and simplified backups since you set the
26882 variable in @file{~/.gnus.el} instead of @file{~/.newsrc.eld}. The
26883 variable maps regular expressions matching group names to group
26886 (setq gnus-parameters
26888 (gnus-show-threads nil)
26889 (gnus-use-scoring nil))
26890 ("^nnimap:\\(foo.bar\\)$"
26891 (to-group . "\\1"))))
26895 Smileys (@samp{:-)}, @samp{;-)} etc) are now iconized for Emacs too.
26897 Put @code{(setq gnus-treat-display-smileys nil)} in @file{~/.gnus.el} to
26901 Gnus no longer generate the Sender: header automatically.
26903 Earlier it was generated iff the user configurable email address was
26904 different from the Gnus guessed default user address. As the guessing
26905 algorithm is rarely correct these days, and (more controversially) the
26906 only use of the Sender: header was to check if you are entitled to
26907 cancel/supersede news (which is now solved by Cancel Locks instead,
26908 see another entry), generation of the header has been disabled by
26909 default. See the variables @code{message-required-headers},
26910 @code{message-required-news-headers}, and
26911 @code{message-required-mail-headers}.
26914 Features from third party @file{message-utils.el} added to @file{message.el}.
26916 Message now asks if you wish to remove @samp{(was: <old subject>)} from
26917 subject lines (see @code{message-subject-trailing-was-query}). @kbd{C-c
26918 M-m} and @kbd{C-c M-f} inserts markers indicating included text.
26919 @kbd{C-c C-f a} adds a X-No-Archive: header. @kbd{C-c C-f x} inserts
26920 appropriate headers and a note in the body for cross-postings and
26921 followups (see the variables @code{message-cross-post-@var{*}}).
26924 References and X-Draft-From headers are no longer generated when you
26925 start composing messages and @code{message-generate-headers-first} is
26929 Improved anti-spam features.
26931 Gnus is now able to take out spam from your mail and news streams
26932 using a wide variety of programs and filter rules. Among the supported
26933 methods are RBL blocklists, bogofilter and white/blacklists. Hooks
26934 for easy use of external packages such as SpamAssassin and Hashcash
26935 are also new. @xref{Thwarting Email Spam}.
26938 Easy inclusion of X-Faces headers.
26941 Face headers handling.
26944 In the summary buffer, the new command @kbd{/ N} inserts new messages
26945 and @kbd{/ o} inserts old messages.
26948 Gnus decodes morse encoded messages if you press @kbd{W m}.
26951 Unread count correct in nnimap groups.
26953 The estimated number of unread articles in the group buffer should now
26954 be correct for nnimap groups. This is achieved by calling
26955 @code{nnimap-fixup-unread-after-getting-new-news} from the
26956 @code{gnus-setup-news-hook} (called on startup) and
26957 @code{gnus-after-getting-new-news-hook}. (called after getting new
26958 mail). If you have modified those variables from the default, you may
26959 want to add @code{nnimap-fixup-unread-after-getting-new-news} again. If
26960 you were happy with the estimate and want to save some (minimal) time
26961 when getting new mail, remove the function.
26964 Group Carbon Copy (GCC) quoting
26966 To support groups that contains SPC and other weird characters, groups
26967 are quoted before they are placed in the Gcc: header. This means
26968 variables such as @code{gnus-message-archive-group} should no longer
26969 contain quote characters to make groups containing SPC work. Also, if
26970 you are using the string @samp{nnml:foo, nnml:bar} (indicating Gcc
26971 into two groups) you must change it to return the list
26972 @code{("nnml:foo" "nnml:bar")}, otherwise the Gcc: line will be quoted
26973 incorrectly. Note that returning the string @samp{nnml:foo, nnml:bar}
26974 was incorrect earlier, it just didn't generate any problems since it
26975 was inserted directly.
26978 @file{~/News/overview/} not used.
26980 As a result of the following change, the @file{~/News/overview/}
26981 directory is not used any more. You can safely delete the entire
26987 The Gnus Agent has seen a major updated and is now enabled by default,
26988 and all nntp and nnimap servers from @code{gnus-select-method} and
26989 @code{gnus-secondary-select-method} are agentized by default. Earlier
26990 only the server in @code{gnus-select-method} was agentized by the
26991 default, and the agent was disabled by default. When the agent is
26992 enabled, headers are now also retrieved from the Agent cache instead
26993 of the back ends when possible. Earlier this only happened in the
26994 unplugged state. You can enroll or remove servers with @kbd{J a} and
26995 @kbd{J r} in the server buffer. Gnus will not download articles into
26996 the Agent cache, unless you instruct it to do so, though, by using
26997 @kbd{J u} or @kbd{J s} from the Group buffer. You revert to the old
26998 behavior of having the Agent disabled with @code{(setq gnus-agent
26999 nil)}. Note that putting @code{(gnus-agentize)} in @file{~/.gnus.el}
27000 is not needed any more.
27003 @code{gnus-summary-line-format}
27005 The default value changed to @samp{%U%R%z%I%(%[%4L: %-23,23f%]%)
27006 %s\n}. Moreover @code{gnus-extra-headers},
27007 @code{nnmail-extra-headers} and @code{gnus-ignored-from-addresses}
27008 changed their default so that the users name will be replaced by the
27009 recipient's name or the group name posting to for @acronym{NNTP}
27013 @file{deuglify.el} (@code{gnus-article-outlook-deuglify-article})
27015 A new file from Raymond Scholz @email{rscholz@@zonix.de} for deuglifying
27016 broken Outlook (Express) articles.
27018 @c FIXME: `gnus-load' is mentioned in README, which is not included in
27019 @c CVS. We should find a better place for this item.
27021 @code{(require 'gnus-load)}
27023 If you use a stand-alone Gnus distribution, you'd better add
27024 @code{(require 'gnus-load)} into your @file{~/.emacs} after adding the Gnus
27025 lisp directory into load-path.
27027 File @file{gnus-load.el} contains autoload commands, functions and variables,
27028 some of which may not be included in distributions of Emacsen.
27031 @code{gnus-slave-unplugged}
27033 A new command which starts Gnus offline in slave mode.
27036 @code{message-insinuate-rmail}
27038 Adding @code{(message-insinuate-rmail)} and @code{(setq
27039 mail-user-agent 'gnus-user-agent)} in @file{.emacs} convinces Rmail to
27040 compose, reply and forward messages in message-mode, where you can
27041 enjoy the power of @acronym{MML}.
27044 @code{message-minibuffer-local-map}
27046 The line below enables BBDB in resending a message:
27048 (define-key message-minibuffer-local-map [(tab)]
27049 'bbdb-complete-name)
27053 Externalizing and deleting of attachments.
27055 If @code{gnus-gcc-externalize-attachments} or
27056 @code{message-fcc-externalize-attachments} is non-@code{nil}, attach
27057 local files as external parts.
27059 The command @code{gnus-mime-save-part-and-strip} (bound to @kbd{C-o}
27060 on @acronym{MIME} buttons) saves a part and replaces the part with an
27061 external one. @code{gnus-mime-delete-part} (bound to @kbd{d} on
27062 @acronym{MIME} buttons) removes a part. It works only on back ends
27063 that support editing.
27066 @code{gnus-default-charset}
27068 The default value is determined from the
27069 @code{current-language-environment} variable, instead of
27070 @code{iso-8859-1}. Also the @samp{.*} item in
27071 @code{gnus-group-charset-alist} is removed.
27074 @code{gnus-posting-styles}
27076 Add a new format of match like
27078 ((header "to" "larsi.*org")
27079 (Organization "Somewhere, Inc."))
27081 The old format like the lines below is obsolete, but still accepted.
27083 (header "to" "larsi.*org"
27084 (Organization "Somewhere, Inc."))
27088 @code{message-ignored-news-headers} and @code{message-ignored-mail-headers}
27090 @samp{X-Draft-From} and @samp{X-Gnus-Agent-Meta-Information} have been
27091 added into these two variables. If you customized those, perhaps you
27092 need add those two headers too.
27095 Gnus reads the @acronym{NOV} and articles in the Agent if plugged.
27097 If one reads an article while plugged, and the article already exists
27098 in the Agent, it won't get downloaded once more. @code{(setq
27099 gnus-agent-cache nil)} reverts to the old behavior.
27102 Gnus supports the ``format=flowed'' (RFC 2646) parameter. On
27103 composing messages, it is enabled by @code{use-hard-newlines}.
27104 Decoding format=flowed was present but not documented in earlier
27108 The option @code{mm-fill-flowed} can be used to disable treatment of
27109 ``format=flowed'' messages. Also, flowed text is disabled when sending
27110 inline PGP signed messages. (New in Gnus 5.10.7)
27113 Gnus supports the generation of RFC 2298 Disposition Notification requests.
27115 This is invoked with the @kbd{C-c M-n} key binding from message mode.
27118 Gnus supports Maildir groups.
27120 Gnus includes a new back end @file{nnmaildir.el}. @xref{Maildir}.
27123 Printing capabilities are enhanced.
27125 Gnus supports Muttprint natively with @kbd{O P} from the Summary and
27126 Article buffers. Also, each individual @acronym{MIME} part can be
27127 printed using @kbd{p} on the @acronym{MIME} button.
27130 Message supports the Importance: (RFC 2156) header.
27132 In the message buffer, @kbd{C-c C-f C-i} or @kbd{C-c C-u} cycles through
27136 Gnus supports Cancel Locks in News.
27138 This means a header @samp{Cancel-Lock} is inserted in news posting. It is
27139 used to determine if you wrote an article or not (for canceling and
27140 superseding). Gnus generates a random password string the first time
27141 you post a message, and saves it in your @file{~/.emacs} using the Custom
27142 system. While the variable is called @code{canlock-password}, it is not
27143 security sensitive data. Publishing your canlock string on the web
27144 will not allow anyone to be able to anything she could not already do.
27145 The behavior can be changed by customizing @code{message-insert-canlock}.
27148 Gnus supports server-side mail filtering using Sieve.
27150 Sieve rules can be added as Group Parameters for groups, and the
27151 complete Sieve script is generated using @kbd{D g} from the Group
27152 buffer, and then uploaded to the server using @kbd{C-c C-l} in the
27153 generated Sieve buffer. @xref{Sieve Commands}, and the new Sieve
27154 manual @ref{Top, , Top, sieve, Emacs Sieve}.
27157 Extended format specs.
27159 Format spec @samp{%&user-date;} is added into
27160 @code{gnus-summary-line-format-alist}. Also, user defined extended
27161 format specs are supported. The extended format specs look like
27162 @samp{%u&foo;}, which invokes function
27163 @code{gnus-user-format-function-@var{foo}}. Because @samp{&} is used as the
27164 escape character, old user defined format @samp{%u&} is no longer supported.
27167 @kbd{/ *} (@code{gnus-summary-limit-include-cached}) is rewritten.
27169 It was aliased to @kbd{Y c}
27170 (@code{gnus-summary-insert-cached-articles}). The new function filters
27171 out other articles.
27174 Some limiting commands accept a @kbd{C-u} prefix to negate the match.
27176 If @kbd{C-u} is used on subject, author or extra headers, i.e., @kbd{/
27177 s}, @kbd{/ a}, and @kbd{/ x}
27178 (@code{gnus-summary-limit-to-@{subject,author,extra@}}) respectively, the
27179 result will be to display all articles that do not match the expression.
27182 Group names are treated as UTF-8 by default.
27184 This is supposedly what USEFOR wanted to migrate to. See
27185 @code{gnus-group-name-charset-group-alist} and
27186 @code{gnus-group-name-charset-method-alist} for customization.
27189 The nnml and nnfolder back ends store marks for each groups.
27191 This makes it possible to take backup of nnml/nnfolder servers/groups
27192 separately of @file{~/.newsrc.eld}, while preserving marks. It also
27193 makes it possible to share articles and marks between users (without
27194 sharing the @file{~/.newsrc.eld} file) within e.g. a department. It
27195 works by storing the marks stored in @file{~/.newsrc.eld} in a per-group
27196 file @file{.marks} (for nnml) and @file{@var{groupname}.mrk} (for
27197 nnfolder, named @var{groupname}). If the nnml/nnfolder is moved to
27198 another machine, Gnus will automatically use the @file{.marks} or
27199 @file{.mrk} file instead of the information in @file{~/.newsrc.eld}.
27200 The new server variables @code{nnml-marks-is-evil} and
27201 @code{nnfolder-marks-is-evil} can be used to disable this feature.
27204 The menu bar item (in Group and Summary buffer) named ``Misc'' has
27205 been renamed to ``Gnus''.
27208 The menu bar item (in Message mode) named ``@acronym{MML}'' has been
27209 renamed to ``Attachments''. Note that this menu also contains security
27210 related stuff, like signing and encryption (@pxref{Security, Security,,
27211 message, Message Manual}).
27214 @code{gnus-group-charset-alist} and
27215 @code{gnus-group-ignored-charsets-alist}.
27217 The regexps in these variables are compared with full group names
27218 instead of real group names in 5.8. Users who customize these
27219 variables should change those regexps accordingly. For example:
27221 ("^han\\>" euc-kr) -> ("\\(^\\|:\\)han\\>" euc-kr)
27225 Gnus supports @acronym{PGP} (RFC 1991/2440), @acronym{PGP/MIME} (RFC
27226 2015/3156) and @acronym{S/MIME} (RFC 2630-2633).
27228 It needs an external @acronym{S/MIME} and OpenPGP implementation, but no
27229 additional Lisp libraries. This add several menu items to the
27230 Attachments menu, and @kbd{C-c RET} key bindings, when composing
27231 messages. This also obsoletes @code{gnus-article-hide-pgp-hook}.
27234 Gnus inlines external parts (message/external).
27237 @acronym{MML} (Mime compose) prefix changed from @kbd{M-m} to @kbd{C-c
27240 This change was made to avoid conflict with the standard binding of
27241 @code{back-to-indentation}, which is also useful in message mode.
27244 The default for @code{message-forward-show-mml} changed to symbol @code{best}.
27246 The behavior for the @code{best} value is to show @acronym{MML} (i.e.,
27247 convert to @acronym{MIME}) when appropriate. @acronym{MML} will not be
27248 used when forwarding signed or encrypted messages, as the conversion
27249 invalidate the digital signature.
27253 @subsubsection No Gnus
27256 New features in No Gnus:
27257 @c FIXME: Gnus 5.12?
27259 @include gnus-news.texi
27265 @section The Manual
27269 This manual was generated from a TeXinfo file and then run through
27270 either @code{texi2dvi}
27272 or my own home-brewed TeXinfo to \LaTeX\ transformer,
27273 and then run through @code{latex} and @code{dvips}
27275 to get what you hold in your hands now.
27277 The following conventions have been used:
27282 This is a @samp{string}
27285 This is a @kbd{keystroke}
27288 This is a @file{file}
27291 This is a @code{symbol}
27295 So if I were to say ``set @code{flargnoze} to @samp{yes}'', that would
27299 (setq flargnoze "yes")
27302 If I say ``set @code{flumphel} to @code{yes}'', that would mean:
27305 (setq flumphel 'yes)
27308 @samp{yes} and @code{yes} are two @emph{very} different things---don't
27309 ever get them confused.
27313 Of course, everything in this manual is of vital interest, so you should
27314 read it all. Several times. However, if you feel like skimming the
27315 manual, look for that gnu head you should see in the margin over
27316 there---it means that what's being discussed is of more importance than
27317 the rest of the stuff. (On the other hand, if everything is infinitely
27318 important, how can anything be more important than that? Just one more
27319 of the mysteries of this world, I guess.)
27325 @node On Writing Manuals
27326 @section On Writing Manuals
27328 I guess most manuals are written after-the-fact; documenting a program
27329 that's already there. This is not how this manual is written. When
27330 implementing something, I write the manual entry for that something
27331 straight away. I then see that it's difficult to explain the
27332 functionality, so I write how it's supposed to be, and then I change the
27333 implementation. Writing the documentation and writing the code goes
27336 This, of course, means that this manual has no, or little, flow. It
27337 documents absolutely everything in Gnus, but often not where you're
27338 looking for it. It is a reference manual, and not a guide to how to get
27341 That would be a totally different book, that should be written using the
27342 reference manual as source material. It would look quite differently.
27347 @section Terminology
27349 @cindex terminology
27354 This is what you are supposed to use this thing for---reading news.
27355 News is generally fetched from a nearby @acronym{NNTP} server, and is
27356 generally publicly available to everybody. If you post news, the entire
27357 world is likely to read just what you have written, and they'll all
27358 snigger mischievously. Behind your back.
27362 Everything that's delivered to you personally is mail. Some news/mail
27363 readers (like Gnus) blur the distinction between mail and news, but
27364 there is a difference. Mail is private. News is public. Mailing is
27365 not posting, and replying is not following up.
27369 Send a mail to the person who has written what you are reading.
27373 Post an article to the current newsgroup responding to the article you
27378 Gnus considers mail and news to be mostly the same, really. The only
27379 difference is how to access the actual articles. News articles are
27380 commonly fetched via the protocol @acronym{NNTP}, whereas mail
27381 messages could be read from a file on the local disk. The internal
27382 architecture of Gnus thus comprises a ``front end'' and a number of
27383 ``back ends''. Internally, when you enter a group (by hitting
27384 @key{RET}, say), you thereby invoke a function in the front end in
27385 Gnus. The front end then ``talks'' to a back end and says things like
27386 ``Give me the list of articles in the foo group'' or ``Show me article
27389 So a back end mainly defines either a protocol (the @code{nntp} back
27390 end accesses news via @acronym{NNTP}, the @code{nnimap} back end
27391 accesses mail via @acronym{IMAP}) or a file format and directory
27392 layout (the @code{nnspool} back end accesses news via the common
27393 ``spool directory'' format, the @code{nnml} back end access mail via a
27394 file format and directory layout that's quite similar).
27396 Gnus does not handle the underlying media, so to speak---this is all
27397 done by the back ends. A back end is a collection of functions to
27398 access the articles.
27400 However, sometimes the term ``back end'' is also used where ``server''
27401 would have been more appropriate. And then there is the term ``select
27402 method'' which can mean either. The Gnus terminology can be quite
27407 Gnus will always use one method (and back end) as the @dfn{native}, or
27408 default, way of getting news.
27412 You can also have any number of foreign groups active at the same time.
27413 These are groups that use non-native non-secondary back ends for getting
27418 Secondary back ends are somewhere half-way between being native and being
27419 foreign, but they mostly act like they are native.
27423 A message that has been posted as news.
27426 @cindex mail message
27427 A message that has been mailed.
27431 A mail message or news article
27435 The top part of a message, where administrative information (etc.) is
27440 The rest of an article. Everything not in the head is in the
27445 A line from the head of an article.
27449 A collection of such lines, or a collection of heads. Or even a
27450 collection of @acronym{NOV} lines.
27452 @item @acronym{NOV}
27453 @cindex @acronym{NOV}
27454 When Gnus enters a group, it asks the back end for the headers of all
27455 unread articles in the group. Most servers support the News OverView
27456 format, which is more compact and much faster to read and parse than the
27457 normal @sc{head} format.
27461 Each group is subscribed at some @dfn{level} or other (1-9). The ones
27462 that have a lower level are ``more'' subscribed than the groups with a
27463 higher level. In fact, groups on levels 1-5 are considered
27464 @dfn{subscribed}; 6-7 are @dfn{unsubscribed}; 8 are @dfn{zombies}; and 9
27465 are @dfn{killed}. Commands for listing groups and scanning for new
27466 articles will all use the numeric prefix as @dfn{working level}.
27468 @item killed groups
27469 @cindex killed groups
27470 No information on killed groups is stored or updated, which makes killed
27471 groups much easier to handle than subscribed groups.
27473 @item zombie groups
27474 @cindex zombie groups
27475 Just like killed groups, only slightly less dead.
27478 @cindex active file
27479 The news server has to keep track of what articles it carries, and what
27480 groups exist. All this information in stored in the active file, which
27481 is rather large, as you might surmise.
27484 @cindex bogus groups
27485 A group that exists in the @file{.newsrc} file, but isn't known to the
27486 server (i.e., it isn't in the active file), is a @emph{bogus group}.
27487 This means that the group probably doesn't exist (any more).
27490 @cindex activating groups
27491 The act of asking the server for info on a group and computing the
27492 number of unread articles is called @dfn{activating the group}.
27493 Un-activated groups are listed with @samp{*} in the group buffer.
27497 News servers store their articles locally in one fashion or other.
27498 One old-fashioned storage method is to have just one file per
27499 article. That's called a ``traditional spool''.
27503 A machine one can connect to and get news (or mail) from.
27505 @item select method
27506 @cindex select method
27507 A structure that specifies the back end, the server and the virtual
27510 @item virtual server
27511 @cindex virtual server
27512 A named select method. Since a select method defines all there is to
27513 know about connecting to a (physical) server, taking the thing as a
27514 whole is a virtual server.
27518 Taking a buffer and running it through a filter of some sort. The
27519 result will (more often than not) be cleaner and more pleasing than the
27522 @item ephemeral groups
27523 @cindex ephemeral groups
27524 @cindex temporary groups
27525 Most groups store data on what articles you have read. @dfn{Ephemeral}
27526 groups are groups that will have no data stored---when you exit the
27527 group, it'll disappear into the aether.
27530 @cindex solid groups
27531 This is the opposite of ephemeral groups. All groups listed in the
27532 group buffer are solid groups.
27534 @item sparse articles
27535 @cindex sparse articles
27536 These are article placeholders shown in the summary buffer when
27537 @code{gnus-build-sparse-threads} has been switched on.
27541 To put responses to articles directly after the articles they respond
27542 to---in a hierarchical fashion.
27546 @cindex thread root
27547 The first article in a thread is the root. It is the ancestor of all
27548 articles in the thread.
27552 An article that has responses.
27556 An article that responds to a different article---its parent.
27560 A collection of messages in one file. The most common digest format is
27561 specified by RFC 1153.
27564 @cindex splitting, terminolgy
27565 @cindex mail sorting
27566 @cindex mail filtering (splitting)
27567 The action of sorting your emails according to certain rules. Sometimes
27568 incorrectly called mail filtering.
27574 @node Customization
27575 @section Customization
27576 @cindex general customization
27578 All variables are properly documented elsewhere in this manual. This
27579 section is designed to give general pointers on how to customize Gnus
27580 for some quite common situations.
27583 * Slow/Expensive Connection:: You run a local Emacs and get the news elsewhere.
27584 * Slow Terminal Connection:: You run a remote Emacs.
27585 * Little Disk Space:: You feel that having large setup files is icky.
27586 * Slow Machine:: You feel like buying a faster machine.
27590 @node Slow/Expensive Connection
27591 @subsection Slow/Expensive NNTP Connection
27593 If you run Emacs on a machine locally, and get your news from a machine
27594 over some very thin strings, you want to cut down on the amount of data
27595 Gnus has to get from the @acronym{NNTP} server.
27599 @item gnus-read-active-file
27600 Set this to @code{nil}, which will inhibit Gnus from requesting the
27601 entire active file from the server. This file is often very large. You
27602 also have to set @code{gnus-check-new-newsgroups} and
27603 @code{gnus-check-bogus-newsgroups} to @code{nil} to make sure that Gnus
27604 doesn't suddenly decide to fetch the active file anyway.
27606 @item gnus-nov-is-evil
27607 This one has to be @code{nil}. If not, grabbing article headers from
27608 the @acronym{NNTP} server will not be very fast. Not all @acronym{NNTP} servers
27609 support @sc{xover}; Gnus will detect this by itself.
27613 @node Slow Terminal Connection
27614 @subsection Slow Terminal Connection
27616 Let's say you use your home computer for dialing up the system that runs
27617 Emacs and Gnus. If your modem is slow, you want to reduce (as much as
27618 possible) the amount of data sent over the wires.
27622 @item gnus-auto-center-summary
27623 Set this to @code{nil} to inhibit Gnus from re-centering the summary
27624 buffer all the time. If it is @code{vertical}, do only vertical
27625 re-centering. If it is neither @code{nil} nor @code{vertical}, do both
27626 horizontal and vertical recentering.
27628 @item gnus-visible-headers
27629 Cut down on the headers included in the articles to the
27630 minimum. You can, in fact, make do without them altogether---most of the
27631 useful data is in the summary buffer, anyway. Set this variable to
27632 @samp{^NEVVVVER} or @samp{From:}, or whatever you feel you need.
27634 Use the following to enable all the available hiding features:
27636 (setq gnus-treat-hide-headers 'head
27637 gnus-treat-hide-signature t
27638 gnus-treat-hide-citation t)
27641 @item gnus-use-full-window
27642 By setting this to @code{nil}, you can make all the windows smaller.
27643 While this doesn't really cut down much generally, it means that you
27644 have to see smaller portions of articles before deciding that you didn't
27645 want to read them anyway.
27647 @item gnus-thread-hide-subtree
27648 If this is non-@code{nil}, all threads in the summary buffer will be
27652 @item gnus-updated-mode-lines
27653 If this is @code{nil}, Gnus will not put information in the buffer mode
27654 lines, which might save some time.
27658 @node Little Disk Space
27659 @subsection Little Disk Space
27662 The startup files can get rather large, so you may want to cut their
27663 sizes a bit if you are running out of space.
27667 @item gnus-save-newsrc-file
27668 If this is @code{nil}, Gnus will never save @file{.newsrc}---it will
27669 only save @file{.newsrc.eld}. This means that you will not be able to
27670 use any other newsreaders than Gnus. This variable is @code{t} by
27673 @item gnus-read-newsrc-file
27674 If this is @code{nil}, Gnus will never read @file{.newsrc}---it will
27675 only read @file{.newsrc.eld}. This means that you will not be able to
27676 use any other newsreaders than Gnus. This variable is @code{t} by
27679 @item gnus-save-killed-list
27680 If this is @code{nil}, Gnus will not save the list of dead groups. You
27681 should also set @code{gnus-check-new-newsgroups} to @code{ask-server}
27682 and @code{gnus-check-bogus-newsgroups} to @code{nil} if you set this
27683 variable to @code{nil}. This variable is @code{t} by default.
27689 @subsection Slow Machine
27690 @cindex slow machine
27692 If you have a slow machine, or are just really impatient, there are a
27693 few things you can do to make Gnus run faster.
27695 Set @code{gnus-check-new-newsgroups} and
27696 @code{gnus-check-bogus-newsgroups} to @code{nil} to make startup faster.
27698 Set @code{gnus-show-threads}, @code{gnus-use-cross-reference} and
27699 @code{gnus-nov-is-evil} to @code{nil} to make entering and exiting the
27700 summary buffer faster.
27704 @node Troubleshooting
27705 @section Troubleshooting
27706 @cindex troubleshooting
27708 Gnus works @emph{so} well straight out of the box---I can't imagine any
27716 Make sure your computer is switched on.
27719 Make sure that you really load the current Gnus version. If you have
27720 been running @sc{gnus}, you need to exit Emacs and start it up again before
27724 Try doing an @kbd{M-x gnus-version}. If you get something that looks
27725 like @samp{Gnus v5.10.6} you have the right files loaded. Otherwise
27726 you have some old @file{.el} files lying around. Delete these.
27729 Read the help group (@kbd{G h} in the group buffer) for a
27730 @acronym{FAQ} and a how-to.
27733 @vindex max-lisp-eval-depth
27734 Gnus works on many recursive structures, and in some extreme (and very
27735 rare) cases Gnus may recurse down ``too deeply'' and Emacs will beep at
27736 you. If this happens to you, set @code{max-lisp-eval-depth} to 500 or
27737 something like that.
27740 If all else fails, report the problem as a bug.
27743 @cindex reporting bugs
27745 @kindex M-x gnus-bug
27747 If you find a bug in Gnus, you can report it with the @kbd{M-x gnus-bug}
27748 command. @kbd{M-x set-variable RET debug-on-error RET t RET}, and send
27749 me the backtrace. I will fix bugs, but I can only fix them if you send
27750 me a precise description as to how to reproduce the bug.
27752 You really can never be too detailed in a bug report. Always use the
27753 @kbd{M-x gnus-bug} command when you make bug reports, even if it creates
27754 a 10Kb mail each time you use it, and even if you have sent me your
27755 environment 500 times before. I don't care. I want the full info each
27758 It is also important to remember that I have no memory whatsoever. If
27759 you send a bug report, and I send you a reply, and then you just send
27760 back ``No, it's not! Moron!'', I will have no idea what you are
27761 insulting me about. Always over-explain everything. It's much easier
27762 for all of us---if I don't have all the information I need, I will just
27763 mail you and ask for more info, and everything takes more time.
27765 If the problem you're seeing is very visual, and you can't quite explain
27766 it, copy the Emacs window to a file (with @code{xwd}, for instance), put
27767 it somewhere it can be reached, and include the URL of the picture in
27771 If you would like to contribute a patch to fix bugs or make
27772 improvements, please produce the patch using @samp{diff -u}.
27775 If you want to debug your problem further before reporting, possibly
27776 in order to solve the problem yourself and send a patch, you can use
27777 edebug. Debugging Lisp code is documented in the Elisp manual
27778 (@pxref{Debugging, , Debugging Lisp Programs, elisp, The GNU Emacs
27779 Lisp Reference Manual}). To get you started with edebug, consider if
27780 you discover some weird behavior when pressing @kbd{c}, the first
27781 step is to do @kbd{C-h k c} and click on the hyperlink (Emacs only) in
27782 the documentation buffer that leads you to the function definition,
27783 then press @kbd{M-x edebug-defun RET} with point inside that function,
27784 return to Gnus and press @kbd{c} to invoke the code. You will be
27785 placed in the lisp buffer and can single step using @kbd{SPC} and
27786 evaluate expressions using @kbd{M-:} or inspect variables using
27787 @kbd{C-h v}, abort execution with @kbd{q}, and resume execution with
27788 @kbd{c} or @kbd{g}.
27793 Sometimes, a problem do not directly generate an elisp error but
27794 manifests itself by causing Gnus to be very slow. In these cases, you
27795 can use @kbd{M-x toggle-debug-on-quit} and press @kbd{C-g} when things are
27796 slow, and then try to analyze the backtrace (repeating the procedure
27797 helps isolating the real problem areas).
27799 A fancier approach is to use the elisp profiler, ELP. The profiler is
27800 (or should be) fully documented elsewhere, but to get you started
27801 there are a few steps that need to be followed. First, instrument the
27802 part of Gnus you are interested in for profiling, e.g. @kbd{M-x
27803 elp-instrument-package RET gnus} or @kbd{M-x elp-instrument-package
27804 RET message}. Then perform the operation that is slow and press
27805 @kbd{M-x elp-results}. You will then see which operations that takes
27806 time, and can debug them further. If the entire operation takes much
27807 longer than the time spent in the slowest function in the profiler
27808 output, you probably profiled the wrong part of Gnus. To reset
27809 profiling statistics, use @kbd{M-x elp-reset-all}. @kbd{M-x
27810 elp-restore-all} is supposed to remove profiling, but given the
27811 complexities and dynamic code generation in Gnus, it might not always
27814 @cindex gnu.emacs.gnus
27815 @cindex ding mailing list
27816 If you just need help, you are better off asking on
27817 @samp{gnu.emacs.gnus}. I'm not very helpful. You can also ask on
27818 @email{ding@@gnus.org, the ding mailing list}. Write to
27819 @email{ding-request@@gnus.org} to subscribe.
27823 @node Gnus Reference Guide
27824 @section Gnus Reference Guide
27826 It is my hope that other people will figure out smart stuff that Gnus
27827 can do, and that other people will write those smart things as well. To
27828 facilitate that I thought it would be a good idea to describe the inner
27829 workings of Gnus. And some of the not-so-inner workings, while I'm at
27832 You can never expect the internals of a program not to change, but I
27833 will be defining (in some details) the interface between Gnus and its
27834 back ends (this is written in stone), the format of the score files
27835 (ditto), data structures (some are less likely to change than others)
27836 and general methods of operation.
27839 * Gnus Utility Functions:: Common functions and variable to use.
27840 * Back End Interface:: How Gnus communicates with the servers.
27841 * Score File Syntax:: A BNF definition of the score file standard.
27842 * Headers:: How Gnus stores headers internally.
27843 * Ranges:: A handy format for storing mucho numbers.
27844 * Group Info:: The group info format.
27845 * Extended Interactive:: Symbolic prefixes and stuff.
27846 * Emacs/XEmacs Code:: Gnus can be run under all modern Emacsen.
27847 * Various File Formats:: Formats of files that Gnus use.
27851 @node Gnus Utility Functions
27852 @subsection Gnus Utility Functions
27853 @cindex Gnus utility functions
27854 @cindex utility functions
27856 @cindex internal variables
27858 When writing small functions to be run from hooks (and stuff), it's
27859 vital to have access to the Gnus internal functions and variables.
27860 Below is a list of the most common ones.
27864 @item gnus-newsgroup-name
27865 @vindex gnus-newsgroup-name
27866 This variable holds the name of the current newsgroup.
27868 @item gnus-find-method-for-group
27869 @findex gnus-find-method-for-group
27870 A function that returns the select method for @var{group}.
27872 @item gnus-group-real-name
27873 @findex gnus-group-real-name
27874 Takes a full (prefixed) Gnus group name, and returns the unprefixed
27877 @item gnus-group-prefixed-name
27878 @findex gnus-group-prefixed-name
27879 Takes an unprefixed group name and a select method, and returns the full
27880 (prefixed) Gnus group name.
27882 @item gnus-get-info
27883 @findex gnus-get-info
27884 Returns the group info list for @var{group}.
27886 @item gnus-group-unread
27887 @findex gnus-group-unread
27888 The number of unread articles in @var{group}, or @code{t} if that is
27892 @findex gnus-active
27893 The active entry for @var{group}.
27895 @item gnus-set-active
27896 @findex gnus-set-active
27897 Set the active entry for @var{group}.
27899 @item gnus-add-current-to-buffer-list
27900 @findex gnus-add-current-to-buffer-list
27901 Adds the current buffer to the list of buffers to be killed on Gnus
27904 @item gnus-continuum-version
27905 @findex gnus-continuum-version
27906 Takes a Gnus version string as a parameter and returns a floating point
27907 number. Earlier versions will always get a lower number than later
27910 @item gnus-group-read-only-p
27911 @findex gnus-group-read-only-p
27912 Says whether @var{group} is read-only or not.
27914 @item gnus-news-group-p
27915 @findex gnus-news-group-p
27916 Says whether @var{group} came from a news back end.
27918 @item gnus-ephemeral-group-p
27919 @findex gnus-ephemeral-group-p
27920 Says whether @var{group} is ephemeral or not.
27922 @item gnus-server-to-method
27923 @findex gnus-server-to-method
27924 Returns the select method corresponding to @var{server}.
27926 @item gnus-server-equal
27927 @findex gnus-server-equal
27928 Says whether two virtual servers are equal.
27930 @item gnus-group-native-p
27931 @findex gnus-group-native-p
27932 Says whether @var{group} is native or not.
27934 @item gnus-group-secondary-p
27935 @findex gnus-group-secondary-p
27936 Says whether @var{group} is secondary or not.
27938 @item gnus-group-foreign-p
27939 @findex gnus-group-foreign-p
27940 Says whether @var{group} is foreign or not.
27942 @item gnus-group-find-parameter
27943 @findex gnus-group-find-parameter
27944 Returns the parameter list of @var{group}. If given a second parameter,
27945 returns the value of that parameter for @var{group}.
27947 @item gnus-group-set-parameter
27948 @findex gnus-group-set-parameter
27949 Takes three parameters; @var{group}, @var{parameter} and @var{value}.
27951 @item gnus-narrow-to-body
27952 @findex gnus-narrow-to-body
27953 Narrows the current buffer to the body of the article.
27955 @item gnus-check-backend-function
27956 @findex gnus-check-backend-function
27957 Takes two parameters, @var{function} and @var{group}. If the back end
27958 @var{group} comes from supports @var{function}, return non-@code{nil}.
27961 (gnus-check-backend-function "request-scan" "nnml:misc")
27965 @item gnus-read-method
27966 @findex gnus-read-method
27967 Prompts the user for a select method.
27972 @node Back End Interface
27973 @subsection Back End Interface
27975 Gnus doesn't know anything about @acronym{NNTP}, spools, mail or virtual
27976 groups. It only knows how to talk to @dfn{virtual servers}. A virtual
27977 server is a @dfn{back end} and some @dfn{back end variables}. As examples
27978 of the first, we have @code{nntp}, @code{nnspool} and @code{nnmbox}. As
27979 examples of the latter we have @code{nntp-port-number} and
27980 @code{nnmbox-directory}.
27982 When Gnus asks for information from a back end---say @code{nntp}---on
27983 something, it will normally include a virtual server name in the
27984 function parameters. (If not, the back end should use the ``current''
27985 virtual server.) For instance, @code{nntp-request-list} takes a virtual
27986 server as its only (optional) parameter. If this virtual server hasn't
27987 been opened, the function should fail.
27989 Note that a virtual server name has no relation to some physical server
27990 name. Take this example:
27994 (nntp-address "ifi.uio.no")
27995 (nntp-port-number 4324))
27998 Here the virtual server name is @samp{odd-one} while the name of
27999 the physical server is @samp{ifi.uio.no}.
28001 The back ends should be able to switch between several virtual servers.
28002 The standard back ends implement this by keeping an alist of virtual
28003 server environments that they pull down/push up when needed.
28005 There are two groups of interface functions: @dfn{required functions},
28006 which must be present, and @dfn{optional functions}, which Gnus will
28007 always check for presence before attempting to call 'em.
28009 All these functions are expected to return data in the buffer
28010 @code{nntp-server-buffer} (@samp{ *nntpd*}), which is somewhat
28011 unfortunately named, but we'll have to live with it. When I talk about
28012 @dfn{resulting data}, I always refer to the data in that buffer. When I
28013 talk about @dfn{return value}, I talk about the function value returned by
28014 the function call. Functions that fail should return @code{nil} as the
28017 Some back ends could be said to be @dfn{server-forming} back ends, and
28018 some might be said not to be. The latter are back ends that generally
28019 only operate on one group at a time, and have no concept of ``server''
28020 ---they have a group, and they deliver info on that group and nothing
28023 Gnus identifies each message by way of group name and article number. A
28024 few remarks about these article numbers might be useful. First of all,
28025 the numbers are positive integers. Secondly, it is normally not
28026 possible for later articles to ``re-use'' older article numbers without
28027 confusing Gnus. That is, if a group has ever contained a message
28028 numbered 42, then no other message may get that number, or Gnus will get
28029 mightily confused.@footnote{See the function
28030 @code{nnchoke-request-update-info}, @ref{Optional Back End Functions}.}
28031 Third, article numbers must be assigned in order of arrival in the
28032 group; this is not necessarily the same as the date of the message.
28034 The previous paragraph already mentions all the ``hard'' restrictions that
28035 article numbers must fulfill. But it seems that it might be useful to
28036 assign @emph{consecutive} article numbers, for Gnus gets quite confused
28037 if there are holes in the article numbering sequence. However, due to
28038 the ``no-reuse'' restriction, holes cannot be avoided altogether. It's
28039 also useful for the article numbers to start at 1 to avoid running out
28040 of numbers as long as possible.
28042 Note that by convention, back ends are named @code{nnsomething}, but
28043 Gnus also comes with some @code{nnnotbackends}, such as
28044 @file{nnheader.el}, @file{nnmail.el} and @file{nnoo.el}.
28046 In the examples and definitions I will refer to the imaginary back end
28049 @cindex @code{nnchoke}
28052 * Required Back End Functions:: Functions that must be implemented.
28053 * Optional Back End Functions:: Functions that need not be implemented.
28054 * Error Messaging:: How to get messages and report errors.
28055 * Writing New Back Ends:: Extending old back ends.
28056 * Hooking New Back Ends Into Gnus:: What has to be done on the Gnus end.
28057 * Mail-like Back Ends:: Some tips on mail back ends.
28061 @node Required Back End Functions
28062 @subsubsection Required Back End Functions
28066 @item (nnchoke-retrieve-headers ARTICLES &optional GROUP SERVER FETCH-OLD)
28068 @var{articles} is either a range of article numbers or a list of
28069 @code{Message-ID}s. Current back ends do not fully support either---only
28070 sequences (lists) of article numbers, and most back ends do not support
28071 retrieval of @code{Message-ID}s. But they should try for both.
28073 The result data should either be HEADs or @acronym{NOV} lines, and the result
28074 value should either be @code{headers} or @code{nov} to reflect this.
28075 This might later be expanded to @code{various}, which will be a mixture
28076 of HEADs and @acronym{NOV} lines, but this is currently not supported by Gnus.
28078 If @var{fetch-old} is non-@code{nil} it says to try fetching ``extra
28079 headers'', in some meaning of the word. This is generally done by
28080 fetching (at most) @var{fetch-old} extra headers less than the smallest
28081 article number in @code{articles}, and filling the gaps as well. The
28082 presence of this parameter can be ignored if the back end finds it
28083 cumbersome to follow the request. If this is non-@code{nil} and not a
28084 number, do maximum fetches.
28086 Here's an example HEAD:
28089 221 1056 Article retrieved.
28090 Path: ifi.uio.no!sturles
28091 From: sturles@@ifi.uio.no (Sturle Sunde)
28092 Newsgroups: ifi.discussion
28093 Subject: Re: Something very droll
28094 Date: 27 Oct 1994 14:02:57 +0100
28095 Organization: Dept. of Informatics, University of Oslo, Norway
28097 Message-ID: <38o8e1$a0o@@holmenkollen.ifi.uio.no>
28098 References: <38jdmq$4qu@@visbur.ifi.uio.no>
28099 NNTP-Posting-Host: holmenkollen.ifi.uio.no
28103 So a @code{headers} return value would imply that there's a number of
28104 these in the data buffer.
28106 Here's a BNF definition of such a buffer:
28110 head = error / valid-head
28111 error-message = [ "4" / "5" ] 2number " " <error message> eol
28112 valid-head = valid-message *header "." eol
28113 valid-message = "221 " <number> " Article retrieved." eol
28114 header = <text> eol
28118 (The version of BNF used here is the one used in RFC822.)
28120 If the return value is @code{nov}, the data buffer should contain
28121 @dfn{network overview database} lines. These are basically fields
28125 nov-buffer = *nov-line
28126 nov-line = field 7*8[ <TAB> field ] eol
28127 field = <text except TAB>
28130 For a closer look at what should be in those fields,
28134 @item (nnchoke-open-server SERVER &optional DEFINITIONS)
28136 @var{server} is here the virtual server name. @var{definitions} is a
28137 list of @code{(VARIABLE VALUE)} pairs that define this virtual server.
28139 If the server can't be opened, no error should be signaled. The back end
28140 may then choose to refuse further attempts at connecting to this
28141 server. In fact, it should do so.
28143 If the server is opened already, this function should return a
28144 non-@code{nil} value. There should be no data returned.
28147 @item (nnchoke-close-server &optional SERVER)
28149 Close connection to @var{server} and free all resources connected
28150 to it. Return @code{nil} if the server couldn't be closed for some
28153 There should be no data returned.
28156 @item (nnchoke-request-close)
28158 Close connection to all servers and free all resources that the back end
28159 have reserved. All buffers that have been created by that back end
28160 should be killed. (Not the @code{nntp-server-buffer}, though.) This
28161 function is generally only called when Gnus is shutting down.
28163 There should be no data returned.
28166 @item (nnchoke-server-opened &optional SERVER)
28168 If @var{server} is the current virtual server, and the connection to the
28169 physical server is alive, then this function should return a
28170 non-@code{nil} value. This function should under no circumstances
28171 attempt to reconnect to a server we have lost connection to.
28173 There should be no data returned.
28176 @item (nnchoke-status-message &optional SERVER)
28178 This function should return the last error message from @var{server}.
28180 There should be no data returned.
28183 @item (nnchoke-request-article ARTICLE &optional GROUP SERVER TO-BUFFER)
28185 The result data from this function should be the article specified by
28186 @var{article}. This might either be a @code{Message-ID} or a number.
28187 It is optional whether to implement retrieval by @code{Message-ID}, but
28188 it would be nice if that were possible.
28190 If @var{to-buffer} is non-@code{nil}, the result data should be returned
28191 in this buffer instead of the normal data buffer. This is to make it
28192 possible to avoid copying large amounts of data from one buffer to
28193 another, while Gnus mainly requests articles to be inserted directly
28194 into its article buffer.
28196 If it is at all possible, this function should return a cons cell where
28197 the @code{car} is the group name the article was fetched from, and the @code{cdr} is
28198 the article number. This will enable Gnus to find out what the real
28199 group and article numbers are when fetching articles by
28200 @code{Message-ID}. If this isn't possible, @code{t} should be returned
28201 on successful article retrieval.
28204 @item (nnchoke-request-group GROUP &optional SERVER FAST)
28206 Get data on @var{group}. This function also has the side effect of
28207 making @var{group} the current group.
28209 If @var{fast}, don't bother to return useful data, just make @var{group}
28212 Here's an example of some result data and a definition of the same:
28215 211 56 1000 1059 ifi.discussion
28218 The first number is the status, which should be 211. Next is the
28219 total number of articles in the group, the lowest article number, the
28220 highest article number, and finally the group name. Note that the total
28221 number of articles may be less than one might think while just
28222 considering the highest and lowest article numbers, but some articles
28223 may have been canceled. Gnus just discards the total-number, so
28224 whether one should take the bother to generate it properly (if that is a
28225 problem) is left as an exercise to the reader. If the group contains no
28226 articles, the lowest article number should be reported as 1 and the
28230 group-status = [ error / info ] eol
28231 error = [ "4" / "5" ] 2<number> " " <Error message>
28232 info = "211 " 3* [ <number> " " ] <string>
28236 @item (nnchoke-close-group GROUP &optional SERVER)
28238 Close @var{group} and free any resources connected to it. This will be
28239 a no-op on most back ends.
28241 There should be no data returned.
28244 @item (nnchoke-request-list &optional SERVER)
28246 Return a list of all groups available on @var{server}. And that means
28249 Here's an example from a server that only carries two groups:
28252 ifi.test 0000002200 0000002000 y
28253 ifi.discussion 3324 3300 n
28256 On each line we have a group name, then the highest article number in
28257 that group, the lowest article number, and finally a flag. If the group
28258 contains no articles, the lowest article number should be reported as 1
28259 and the highest as 0.
28262 active-file = *active-line
28263 active-line = name " " <number> " " <number> " " flags eol
28265 flags = "n" / "y" / "m" / "x" / "j" / "=" name
28268 The flag says whether the group is read-only (@samp{n}), is moderated
28269 (@samp{m}), is dead (@samp{x}), is aliased to some other group
28270 (@samp{=other-group}) or none of the above (@samp{y}).
28273 @item (nnchoke-request-post &optional SERVER)
28275 This function should post the current buffer. It might return whether
28276 the posting was successful or not, but that's not required. If, for
28277 instance, the posting is done asynchronously, it has generally not been
28278 completed by the time this function concludes. In that case, this
28279 function should set up some kind of sentinel to beep the user loud and
28280 clear if the posting could not be completed.
28282 There should be no result data from this function.
28287 @node Optional Back End Functions
28288 @subsubsection Optional Back End Functions
28292 @item (nnchoke-retrieve-groups GROUPS &optional SERVER)
28294 @var{groups} is a list of groups, and this function should request data
28295 on all those groups. How it does it is of no concern to Gnus, but it
28296 should attempt to do this in a speedy fashion.
28298 The return value of this function can be either @code{active} or
28299 @code{group}, which says what the format of the result data is. The
28300 former is in the same format as the data from
28301 @code{nnchoke-request-list}, while the latter is a buffer full of lines
28302 in the same format as @code{nnchoke-request-group} gives.
28305 group-buffer = *active-line / *group-status
28309 @item (nnchoke-request-update-info GROUP INFO &optional SERVER)
28311 A Gnus group info (@pxref{Group Info}) is handed to the back end for
28312 alterations. This comes in handy if the back end really carries all
28313 the information (as is the case with virtual and imap groups). This
28314 function should destructively alter the info to suit its needs, and
28315 should return a non-@code{nil} value (exceptionally,
28316 @code{nntp-request-update-info} always returns @code{nil} not to waste
28317 the network resources).
28319 There should be no result data from this function.
28322 @item (nnchoke-request-type GROUP &optional ARTICLE)
28324 When the user issues commands for ``sending news'' (@kbd{F} in the
28325 summary buffer, for instance), Gnus has to know whether the article the
28326 user is following up on is news or mail. This function should return
28327 @code{news} if @var{article} in @var{group} is news, @code{mail} if it
28328 is mail and @code{unknown} if the type can't be decided. (The
28329 @var{article} parameter is necessary in @code{nnvirtual} groups which
28330 might very well combine mail groups and news groups.) Both @var{group}
28331 and @var{article} may be @code{nil}.
28333 There should be no result data from this function.
28336 @item (nnchoke-request-set-mark GROUP ACTION &optional SERVER)
28338 Set/remove/add marks on articles. Normally Gnus handles the article
28339 marks (such as read, ticked, expired etc) internally, and store them in
28340 @file{~/.newsrc.eld}. Some back ends (such as @acronym{IMAP}) however carry
28341 all information about the articles on the server, so Gnus need to
28342 propagate the mark information to the server.
28344 @var{action} is a list of mark setting requests, having this format:
28347 (RANGE ACTION MARK)
28350 @var{range} is a range of articles you wish to update marks on.
28351 @var{action} is @code{add} or @code{del}, used to add marks or remove
28352 marks (preserving all marks not mentioned). @var{mark} is a list of
28353 marks; where each mark is a symbol. Currently used marks are
28354 @code{read}, @code{tick}, @code{reply}, @code{expire}, @code{killed},
28355 @code{dormant}, @code{save}, @code{download}, @code{unsend},
28356 @code{forward} and @code{recent}, but your back end should, if
28357 possible, not limit itself to these.
28359 Given contradictory actions, the last action in the list should be the
28360 effective one. That is, if your action contains a request to add the
28361 @code{tick} mark on article 1 and, later in the list, a request to
28362 remove the mark on the same article, the mark should in fact be removed.
28364 An example action list:
28367 (((5 12 30) 'del '(tick))
28368 ((10 . 90) 'add '(read expire))
28369 ((92 94) 'del '(read)))
28372 The function should return a range of articles it wasn't able to set the
28373 mark on (currently not used for anything).
28375 There should be no result data from this function.
28377 @item (nnchoke-request-update-mark GROUP ARTICLE MARK)
28379 If the user tries to set a mark that the back end doesn't like, this
28380 function may change the mark. Gnus will use whatever this function
28381 returns as the mark for @var{article} instead of the original
28382 @var{mark}. If the back end doesn't care, it must return the original
28383 @var{mark}, and not @code{nil} or any other type of garbage.
28385 The only use for this I can see is what @code{nnvirtual} does with
28386 it---if a component group is auto-expirable, marking an article as read
28387 in the virtual group should result in the article being marked as
28390 There should be no result data from this function.
28393 @item (nnchoke-request-scan &optional GROUP SERVER)
28395 This function may be called at any time (by Gnus or anything else) to
28396 request that the back end check for incoming articles, in one way or
28397 another. A mail back end will typically read the spool file or query
28398 the @acronym{POP} server when this function is invoked. The
28399 @var{group} doesn't have to be heeded---if the back end decides that
28400 it is too much work just scanning for a single group, it may do a
28401 total scan of all groups. It would be nice, however, to keep things
28402 local if that's practical.
28404 There should be no result data from this function.
28407 @item (nnchoke-request-group-description GROUP &optional SERVER)
28409 The result data from this function should be a description of
28413 description-line = name <TAB> description eol
28415 description = <text>
28418 @item (nnchoke-request-list-newsgroups &optional SERVER)
28420 The result data from this function should be the description of all
28421 groups available on the server.
28424 description-buffer = *description-line
28428 @item (nnchoke-request-newgroups DATE &optional SERVER)
28430 The result data from this function should be all groups that were
28431 created after @samp{date}, which is in normal human-readable date format
28432 (i.e., the date format used in mail and news headers, and returned by
28433 the function @code{message-make-date} by default). The data should be
28434 in the active buffer format.
28436 It is okay for this function to return ``too many'' groups; some back ends
28437 might find it cheaper to return the full list of groups, rather than
28438 just the new groups. But don't do this for back ends with many groups.
28439 Normally, if the user creates the groups herself, there won't be too
28440 many groups, so @code{nnml} and the like are probably safe. But for
28441 back ends like @code{nntp}, where the groups have been created by the
28442 server, it is quite likely that there can be many groups.
28445 @item (nnchoke-request-create-group GROUP &optional SERVER)
28447 This function should create an empty group with name @var{group}.
28449 There should be no return data.
28452 @item (nnchoke-request-expire-articles ARTICLES &optional GROUP SERVER FORCE)
28454 This function should run the expiry process on all articles in the
28455 @var{articles} range (which is currently a simple list of article
28456 numbers.) It is left up to the back end to decide how old articles
28457 should be before they are removed by this function. If @var{force} is
28458 non-@code{nil}, all @var{articles} should be deleted, no matter how new
28461 This function should return a list of articles that it did not/was not
28464 There should be no result data returned.
28467 @item (nnchoke-request-move-article ARTICLE GROUP SERVER ACCEPT-FORM &optional LAST)
28469 This function should move @var{article} (which is a number) from
28470 @var{group} by calling @var{accept-form}.
28472 This function should ready the article in question for moving by
28473 removing any header lines it has added to the article, and generally
28474 should ``tidy up'' the article. Then it should @code{eval}
28475 @var{accept-form} in the buffer where the ``tidy'' article is. This
28476 will do the actual copying. If this @code{eval} returns a
28477 non-@code{nil} value, the article should be removed.
28479 If @var{last} is @code{nil}, that means that there is a high likelihood
28480 that there will be more requests issued shortly, so that allows some
28483 The function should return a cons where the @code{car} is the group name and
28484 the @code{cdr} is the article number that the article was entered as.
28486 There should be no data returned.
28489 @item (nnchoke-request-accept-article GROUP &optional SERVER LAST)
28491 This function takes the current buffer and inserts it into @var{group}.
28492 If @var{last} in @code{nil}, that means that there will be more calls to
28493 this function in short order.
28495 The function should return a cons where the @code{car} is the group name and
28496 the @code{cdr} is the article number that the article was entered as.
28498 The group should exist before the back end is asked to accept the
28499 article for that group.
28501 There should be no data returned.
28504 @item (nnchoke-request-replace-article ARTICLE GROUP BUFFER)
28506 This function should remove @var{article} (which is a number) from
28507 @var{group} and insert @var{buffer} there instead.
28509 There should be no data returned.
28512 @item (nnchoke-request-delete-group GROUP FORCE &optional SERVER)
28514 This function should delete @var{group}. If @var{force}, it should
28515 really delete all the articles in the group, and then delete the group
28516 itself. (If there is such a thing as ``the group itself''.)
28518 There should be no data returned.
28521 @item (nnchoke-request-rename-group GROUP NEW-NAME &optional SERVER)
28523 This function should rename @var{group} into @var{new-name}. All
28524 articles in @var{group} should move to @var{new-name}.
28526 There should be no data returned.
28531 @node Error Messaging
28532 @subsubsection Error Messaging
28534 @findex nnheader-report
28535 @findex nnheader-get-report
28536 The back ends should use the function @code{nnheader-report} to report
28537 error conditions---they should not raise errors when they aren't able to
28538 perform a request. The first argument to this function is the back end
28539 symbol, and the rest are interpreted as arguments to @code{format} if
28540 there are multiple of them, or just a string if there is one of them.
28541 This function must always returns @code{nil}.
28544 (nnheader-report 'nnchoke "You did something totally bogus")
28546 (nnheader-report 'nnchoke "Could not request group %s" group)
28549 Gnus, in turn, will call @code{nnheader-get-report} when it gets a
28550 @code{nil} back from a server, and this function returns the most
28551 recently reported message for the back end in question. This function
28552 takes one argument---the server symbol.
28554 Internally, these functions access @var{back-end}@code{-status-string},
28555 so the @code{nnchoke} back end will have its error message stored in
28556 @code{nnchoke-status-string}.
28559 @node Writing New Back Ends
28560 @subsubsection Writing New Back Ends
28562 Many back ends are quite similar. @code{nnml} is just like
28563 @code{nnspool}, but it allows you to edit the articles on the server.
28564 @code{nnmh} is just like @code{nnml}, but it doesn't use an active file,
28565 and it doesn't maintain overview databases. @code{nndir} is just like
28566 @code{nnml}, but it has no concept of ``groups'', and it doesn't allow
28569 It would make sense if it were possible to ``inherit'' functions from
28570 back ends when writing new back ends. And, indeed, you can do that if you
28571 want to. (You don't have to if you don't want to, of course.)
28573 All the back ends declare their public variables and functions by using a
28574 package called @code{nnoo}.
28576 To inherit functions from other back ends (and allow other back ends to
28577 inherit functions from the current back end), you should use the
28583 This macro declares the first parameter to be a child of the subsequent
28584 parameters. For instance:
28587 (nnoo-declare nndir
28591 @code{nndir} has declared here that it intends to inherit functions from
28592 both @code{nnml} and @code{nnmh}.
28595 This macro is equivalent to @code{defvar}, but registers the variable as
28596 a public server variable. Most state-oriented variables should be
28597 declared with @code{defvoo} instead of @code{defvar}.
28599 In addition to the normal @code{defvar} parameters, it takes a list of
28600 variables in the parent back ends to map the variable to when executing
28601 a function in those back ends.
28604 (defvoo nndir-directory nil
28605 "Where nndir will look for groups."
28606 nnml-current-directory nnmh-current-directory)
28609 This means that @code{nnml-current-directory} will be set to
28610 @code{nndir-directory} when an @code{nnml} function is called on behalf
28611 of @code{nndir}. (The same with @code{nnmh}.)
28613 @item nnoo-define-basics
28614 This macro defines some common functions that almost all back ends should
28618 (nnoo-define-basics nndir)
28622 This macro is just like @code{defun} and takes the same parameters. In
28623 addition to doing the normal @code{defun} things, it registers the
28624 function as being public so that other back ends can inherit it.
28626 @item nnoo-map-functions
28627 This macro allows mapping of functions from the current back end to
28628 functions from the parent back ends.
28631 (nnoo-map-functions nndir
28632 (nnml-retrieve-headers 0 nndir-current-group 0 0)
28633 (nnmh-request-article 0 nndir-current-group 0 0))
28636 This means that when @code{nndir-retrieve-headers} is called, the first,
28637 third, and fourth parameters will be passed on to
28638 @code{nnml-retrieve-headers}, while the second parameter is set to the
28639 value of @code{nndir-current-group}.
28642 This macro allows importing functions from back ends. It should be the
28643 last thing in the source file, since it will only define functions that
28644 haven't already been defined.
28650 nnmh-request-newgroups)
28654 This means that calls to @code{nndir-request-list} should just be passed
28655 on to @code{nnmh-request-list}, while all public functions from
28656 @code{nnml} that haven't been defined in @code{nndir} yet should be
28661 Below is a slightly shortened version of the @code{nndir} back end.
28664 ;;; @r{nndir.el --- single directory newsgroup access for Gnus}
28665 ;; @r{Copyright (C) 1995,96 Free Software Foundation, Inc.}
28669 (require 'nnheader)
28673 (eval-when-compile (require 'cl))
28675 (nnoo-declare nndir
28678 (defvoo nndir-directory nil
28679 "Where nndir will look for groups."
28680 nnml-current-directory nnmh-current-directory)
28682 (defvoo nndir-nov-is-evil nil
28683 "*Non-nil means that nndir will never retrieve NOV headers."
28686 (defvoo nndir-current-group ""
28688 nnml-current-group nnmh-current-group)
28689 (defvoo nndir-top-directory nil nil nnml-directory nnmh-directory)
28690 (defvoo nndir-get-new-mail nil nil nnml-get-new-mail nnmh-get-new-mail)
28692 (defvoo nndir-status-string "" nil nnmh-status-string)
28693 (defconst nndir-version "nndir 1.0")
28695 ;;; @r{Interface functions.}
28697 (nnoo-define-basics nndir)
28699 (deffoo nndir-open-server (server &optional defs)
28700 (setq nndir-directory
28701 (or (cadr (assq 'nndir-directory defs))
28703 (unless (assq 'nndir-directory defs)
28704 (push `(nndir-directory ,server) defs))
28705 (push `(nndir-current-group
28706 ,(file-name-nondirectory
28707 (directory-file-name nndir-directory)))
28709 (push `(nndir-top-directory
28710 ,(file-name-directory (directory-file-name nndir-directory)))
28712 (nnoo-change-server 'nndir server defs))
28714 (nnoo-map-functions nndir
28715 (nnml-retrieve-headers 0 nndir-current-group 0 0)
28716 (nnmh-request-article 0 nndir-current-group 0 0)
28717 (nnmh-request-group nndir-current-group 0 0)
28718 (nnmh-close-group nndir-current-group 0))
28722 nnmh-status-message
28724 nnmh-request-newgroups))
28730 @node Hooking New Back Ends Into Gnus
28731 @subsubsection Hooking New Back Ends Into Gnus
28733 @vindex gnus-valid-select-methods
28734 @findex gnus-declare-backend
28735 Having Gnus start using your new back end is rather easy---you just
28736 declare it with the @code{gnus-declare-backend} functions. This will
28737 enter the back end into the @code{gnus-valid-select-methods} variable.
28739 @code{gnus-declare-backend} takes two parameters---the back end name and
28740 an arbitrary number of @dfn{abilities}.
28745 (gnus-declare-backend "nnchoke" 'mail 'respool 'address)
28748 The above line would then go in the @file{nnchoke.el} file.
28750 The abilities can be:
28754 This is a mailish back end---followups should (probably) go via mail.
28756 This is a newsish back end---followups should (probably) go via news.
28758 This back end supports both mail and news.
28760 This is neither a post nor mail back end---it's something completely
28763 It supports respooling---or rather, it is able to modify its source
28764 articles and groups.
28766 The name of the server should be in the virtual server name. This is
28767 true for almost all back ends.
28768 @item prompt-address
28769 The user should be prompted for an address when doing commands like
28770 @kbd{B} in the group buffer. This is true for back ends like
28771 @code{nntp}, but not @code{nnmbox}, for instance.
28775 @node Mail-like Back Ends
28776 @subsubsection Mail-like Back Ends
28778 One of the things that separate the mail back ends from the rest of the
28779 back ends is the heavy dependence by most of the mail back ends on
28780 common functions in @file{nnmail.el}. For instance, here's the
28781 definition of @code{nnml-request-scan}:
28784 (deffoo nnml-request-scan (&optional group server)
28785 (setq nnml-article-file-alist nil)
28786 (nnmail-get-new-mail 'nnml 'nnml-save-nov nnml-directory group))
28789 It simply calls @code{nnmail-get-new-mail} with a few parameters,
28790 and @code{nnmail} takes care of all the moving and splitting of the
28793 This function takes four parameters.
28797 This should be a symbol to designate which back end is responsible for
28800 @item exit-function
28801 This function should be called after the splitting has been performed.
28803 @item temp-directory
28804 Where the temporary files should be stored.
28807 This optional argument should be a group name if the splitting is to be
28808 performed for one group only.
28811 @code{nnmail-get-new-mail} will call @var{back-end}@code{-save-mail} to
28812 save each article. @var{back-end}@code{-active-number} will be called to
28813 find the article number assigned to this article.
28815 The function also uses the following variables:
28816 @var{back-end}@code{-get-new-mail} (to see whether to get new mail for
28817 this back end); and @var{back-end}@code{-group-alist} and
28818 @var{back-end}@code{-active-file} to generate the new active file.
28819 @var{back-end}@code{-group-alist} should be a group-active alist, like
28823 (("a-group" (1 . 10))
28824 ("some-group" (34 . 39)))
28828 @node Score File Syntax
28829 @subsection Score File Syntax
28831 Score files are meant to be easily parseable, but yet extremely
28832 mallable. It was decided that something that had the same read syntax
28833 as an Emacs Lisp list would fit that spec.
28835 Here's a typical score file:
28839 ("win95" -10000 nil s)
28846 BNF definition of a score file:
28849 score-file = "" / "(" *element ")"
28850 element = rule / atom
28851 rule = string-rule / number-rule / date-rule
28852 string-rule = "(" quote string-header quote space *string-match ")"
28853 number-rule = "(" quote number-header quote space *number-match ")"
28854 date-rule = "(" quote date-header quote space *date-match ")"
28856 string-header = "subject" / "from" / "references" / "message-id" /
28857 "xref" / "body" / "head" / "all" / "followup"
28858 number-header = "lines" / "chars"
28859 date-header = "date"
28860 string-match = "(" quote <string> quote [ "" / [ space score [ "" /
28861 space date [ "" / [ space string-match-t ] ] ] ] ] ")"
28862 score = "nil" / <integer>
28863 date = "nil" / <natural number>
28864 string-match-t = "nil" / "s" / "substring" / "S" / "Substring" /
28865 "r" / "regex" / "R" / "Regex" /
28866 "e" / "exact" / "E" / "Exact" /
28867 "f" / "fuzzy" / "F" / "Fuzzy"
28868 number-match = "(" <integer> [ "" / [ space score [ "" /
28869 space date [ "" / [ space number-match-t ] ] ] ] ] ")"
28870 number-match-t = "nil" / "=" / "<" / ">" / ">=" / "<="
28871 date-match = "(" quote <string> quote [ "" / [ space score [ "" /
28872 space date [ "" / [ space date-match-t ] ] ] ] ")"
28873 date-match-t = "nil" / "at" / "before" / "after"
28874 atom = "(" [ required-atom / optional-atom ] ")"
28875 required-atom = mark / expunge / mark-and-expunge / files /
28876 exclude-files / read-only / touched
28877 optional-atom = adapt / local / eval
28878 mark = "mark" space nil-or-number
28879 nil-or-number = "nil" / <integer>
28880 expunge = "expunge" space nil-or-number
28881 mark-and-expunge = "mark-and-expunge" space nil-or-number
28882 files = "files" *[ space <string> ]
28883 exclude-files = "exclude-files" *[ space <string> ]
28884 read-only = "read-only" [ space "nil" / space "t" ]
28885 adapt = "adapt" [ space "ignore" / space "t" / space adapt-rule ]
28886 adapt-rule = "(" *[ <string> *[ "(" <string> <integer> ")" ] ")"
28887 local = "local" *[ space "(" <string> space <form> ")" ]
28888 eval = "eval" space <form>
28889 space = *[ " " / <TAB> / <NEWLINE> ]
28892 Any unrecognized elements in a score file should be ignored, but not
28895 As you can see, white space is needed, but the type and amount of white
28896 space is irrelevant. This means that formatting of the score file is
28897 left up to the programmer---if it's simpler to just spew it all out on
28898 one looong line, then that's ok.
28900 The meaning of the various atoms are explained elsewhere in this
28901 manual (@pxref{Score File Format}).
28905 @subsection Headers
28907 Internally Gnus uses a format for storing article headers that
28908 corresponds to the @acronym{NOV} format in a mysterious fashion. One could
28909 almost suspect that the author looked at the @acronym{NOV} specification and
28910 just shamelessly @emph{stole} the entire thing, and one would be right.
28912 @dfn{Header} is a severely overloaded term. ``Header'' is used in
28913 RFC 1036 to talk about lines in the head of an article (e.g.,
28914 @code{From}). It is used by many people as a synonym for
28915 ``head''---``the header and the body''. (That should be avoided, in my
28916 opinion.) And Gnus uses a format internally that it calls ``header'',
28917 which is what I'm talking about here. This is a 9-element vector,
28918 basically, with each header (ouch) having one slot.
28920 These slots are, in order: @code{number}, @code{subject}, @code{from},
28921 @code{date}, @code{id}, @code{references}, @code{chars}, @code{lines},
28922 @code{xref}, and @code{extra}. There are macros for accessing and
28923 setting these slots---they all have predictable names beginning with
28924 @code{mail-header-} and @code{mail-header-set-}, respectively.
28926 All these slots contain strings, except the @code{extra} slot, which
28927 contains an alist of header/value pairs (@pxref{To From Newsgroups}).
28933 @sc{gnus} introduced a concept that I found so useful that I've started
28934 using it a lot and have elaborated on it greatly.
28936 The question is simple: If you have a large amount of objects that are
28937 identified by numbers (say, articles, to take a @emph{wild} example)
28938 that you want to qualify as being ``included'', a normal sequence isn't
28939 very useful. (A 200,000 length sequence is a bit long-winded.)
28941 The solution is as simple as the question: You just collapse the
28945 (1 2 3 4 5 6 10 11 12)
28948 is transformed into
28951 ((1 . 6) (10 . 12))
28954 To avoid having those nasty @samp{(13 . 13)} elements to denote a
28955 lonesome object, a @samp{13} is a valid element:
28958 ((1 . 6) 7 (10 . 12))
28961 This means that comparing two ranges to find out whether they are equal
28962 is slightly tricky:
28965 ((1 . 5) 7 8 (10 . 12))
28971 ((1 . 5) (7 . 8) (10 . 12))
28974 are equal. In fact, any non-descending list is a range:
28980 is a perfectly valid range, although a pretty long-winded one. This is
28987 and is equal to the previous range.
28989 Here's a BNF definition of ranges. Of course, one must remember the
28990 semantic requirement that the numbers are non-descending. (Any number
28991 of repetition of the same number is allowed, but apt to disappear in
28995 range = simple-range / normal-range
28996 simple-range = "(" number " . " number ")"
28997 normal-range = "(" start-contents ")"
28998 contents = "" / simple-range *[ " " contents ] /
28999 number *[ " " contents ]
29002 Gnus currently uses ranges to keep track of read articles and article
29003 marks. I plan on implementing a number of range operators in C if The
29004 Powers That Be are willing to let me. (I haven't asked yet, because I
29005 need to do some more thinking on what operators I need to make life
29006 totally range-based without ever having to convert back to normal
29011 @subsection Group Info
29013 Gnus stores all permanent info on groups in a @dfn{group info} list.
29014 This list is from three to six elements (or more) long and exhaustively
29015 describes the group.
29017 Here are two example group infos; one is a very simple group while the
29018 second is a more complex one:
29021 ("no.group" 5 ((1 . 54324)))
29023 ("nnml:my.mail" 3 ((1 . 5) 9 (20 . 55))
29024 ((tick (15 . 19)) (replied 3 6 (19 . 3)))
29026 ((auto-expire . t) (to-address . "ding@@gnus.org")))
29029 The first element is the @dfn{group name}---as Gnus knows the group,
29030 anyway. The second element is the @dfn{subscription level}, which
29031 normally is a small integer. (It can also be the @dfn{rank}, which is a
29032 cons cell where the @code{car} is the level and the @code{cdr} is the
29033 score.) The third element is a list of ranges of read articles. The
29034 fourth element is a list of lists of article marks of various kinds.
29035 The fifth element is the select method (or virtual server, if you like).
29036 The sixth element is a list of @dfn{group parameters}, which is what
29037 this section is about.
29039 Any of the last three elements may be missing if they are not required.
29040 In fact, the vast majority of groups will normally only have the first
29041 three elements, which saves quite a lot of cons cells.
29043 Here's a BNF definition of the group info format:
29046 info = "(" group space ralevel space read
29047 [ "" / [ space marks-list [ "" / [ space method [ "" /
29048 space parameters ] ] ] ] ] ")"
29049 group = quote <string> quote
29050 ralevel = rank / level
29051 level = <integer in the range of 1 to inf>
29052 rank = "(" level "." score ")"
29053 score = <integer in the range of 1 to inf>
29055 marks-lists = nil / "(" *marks ")"
29056 marks = "(" <string> range ")"
29057 method = "(" <string> *elisp-forms ")"
29058 parameters = "(" *elisp-forms ")"
29061 Actually that @samp{marks} rule is a fib. A @samp{marks} is a
29062 @samp{<string>} consed on to a @samp{range}, but that's a bitch to say
29065 If you have a Gnus info and want to access the elements, Gnus offers a
29066 series of macros for getting/setting these elements.
29069 @item gnus-info-group
29070 @itemx gnus-info-set-group
29071 @findex gnus-info-group
29072 @findex gnus-info-set-group
29073 Get/set the group name.
29075 @item gnus-info-rank
29076 @itemx gnus-info-set-rank
29077 @findex gnus-info-rank
29078 @findex gnus-info-set-rank
29079 Get/set the group rank (@pxref{Group Score}).
29081 @item gnus-info-level
29082 @itemx gnus-info-set-level
29083 @findex gnus-info-level
29084 @findex gnus-info-set-level
29085 Get/set the group level.
29087 @item gnus-info-score
29088 @itemx gnus-info-set-score
29089 @findex gnus-info-score
29090 @findex gnus-info-set-score
29091 Get/set the group score (@pxref{Group Score}).
29093 @item gnus-info-read
29094 @itemx gnus-info-set-read
29095 @findex gnus-info-read
29096 @findex gnus-info-set-read
29097 Get/set the ranges of read articles.
29099 @item gnus-info-marks
29100 @itemx gnus-info-set-marks
29101 @findex gnus-info-marks
29102 @findex gnus-info-set-marks
29103 Get/set the lists of ranges of marked articles.
29105 @item gnus-info-method
29106 @itemx gnus-info-set-method
29107 @findex gnus-info-method
29108 @findex gnus-info-set-method
29109 Get/set the group select method.
29111 @item gnus-info-params
29112 @itemx gnus-info-set-params
29113 @findex gnus-info-params
29114 @findex gnus-info-set-params
29115 Get/set the group parameters.
29118 All the getter functions take one parameter---the info list. The setter
29119 functions take two parameters---the info list and the new value.
29121 The last three elements in the group info aren't mandatory, so it may be
29122 necessary to extend the group info before setting the element. If this
29123 is necessary, you can just pass on a non-@code{nil} third parameter to
29124 the three final setter functions to have this happen automatically.
29127 @node Extended Interactive
29128 @subsection Extended Interactive
29129 @cindex interactive
29130 @findex gnus-interactive
29132 Gnus extends the standard Emacs @code{interactive} specification
29133 slightly to allow easy use of the symbolic prefix (@pxref{Symbolic
29134 Prefixes}). Here's an example of how this is used:
29137 (defun gnus-summary-increase-score (&optional score symp)
29138 (interactive (gnus-interactive "P\ny"))
29143 The best thing to do would have been to implement
29144 @code{gnus-interactive} as a macro which would have returned an
29145 @code{interactive} form, but this isn't possible since Emacs checks
29146 whether a function is interactive or not by simply doing an @code{assq}
29147 on the lambda form. So, instead we have @code{gnus-interactive}
29148 function that takes a string and returns values that are usable to
29149 @code{interactive}.
29151 This function accepts (almost) all normal @code{interactive} specs, but
29156 @vindex gnus-current-prefix-symbol
29157 The current symbolic prefix---the @code{gnus-current-prefix-symbol}
29161 @vindex gnus-current-prefix-symbols
29162 A list of the current symbolic prefixes---the
29163 @code{gnus-current-prefix-symbol} variable.
29166 The current article number---the @code{gnus-summary-article-number}
29170 The current article header---the @code{gnus-summary-article-header}
29174 The current group name---the @code{gnus-group-group-name}
29180 @node Emacs/XEmacs Code
29181 @subsection Emacs/XEmacs Code
29185 While Gnus runs under Emacs, XEmacs and Mule, I decided that one of the
29186 platforms must be the primary one. I chose Emacs. Not because I don't
29187 like XEmacs or Mule, but because it comes first alphabetically.
29189 This means that Gnus will byte-compile under Emacs with nary a warning,
29190 while XEmacs will pump out gigabytes of warnings while byte-compiling.
29191 As I use byte-compilation warnings to help me root out trivial errors in
29192 Gnus, that's very useful.
29194 I've also consistently used Emacs function interfaces, but have used
29195 Gnusey aliases for the functions. To take an example: Emacs defines a
29196 @code{run-at-time} function while XEmacs defines a @code{start-itimer}
29197 function. I then define a function called @code{gnus-run-at-time} that
29198 takes the same parameters as the Emacs @code{run-at-time}. When running
29199 Gnus under Emacs, the former function is just an alias for the latter.
29200 However, when running under XEmacs, the former is an alias for the
29201 following function:
29204 (defun gnus-xmas-run-at-time (time repeat function &rest args)
29208 (,function ,@@args))
29212 This sort of thing has been done for bunches of functions. Gnus does
29213 not redefine any native Emacs functions while running under XEmacs---it
29214 does this @code{defalias} thing with Gnus equivalents instead. Cleaner
29217 In the cases where the XEmacs function interface was obviously cleaner,
29218 I used it instead. For example @code{gnus-region-active-p} is an alias
29219 for @code{region-active-p} in XEmacs, whereas in Emacs it is a function.
29221 Of course, I could have chosen XEmacs as my native platform and done
29222 mapping functions the other way around. But I didn't. The performance
29223 hit these indirections impose on Gnus under XEmacs should be slight.
29226 @node Various File Formats
29227 @subsection Various File Formats
29230 * Active File Format:: Information on articles and groups available.
29231 * Newsgroups File Format:: Group descriptions.
29235 @node Active File Format
29236 @subsubsection Active File Format
29238 The active file lists all groups available on the server in
29239 question. It also lists the highest and lowest current article numbers
29242 Here's an excerpt from a typical active file:
29245 soc.motss 296030 293865 y
29246 alt.binaries.pictures.fractals 3922 3913 n
29247 comp.sources.unix 1605 1593 m
29248 comp.binaries.ibm.pc 5097 5089 y
29249 no.general 1000 900 y
29252 Here's a pseudo-BNF definition of this file:
29255 active = *group-line
29256 group-line = group spc high-number spc low-number spc flag <NEWLINE>
29257 group = <non-white-space string>
29259 high-number = <non-negative integer>
29260 low-number = <positive integer>
29261 flag = "y" / "n" / "m" / "j" / "x" / "=" group
29264 For a full description of this file, see the manual pages for
29265 @samp{innd}, in particular @samp{active(5)}.
29268 @node Newsgroups File Format
29269 @subsubsection Newsgroups File Format
29271 The newsgroups file lists groups along with their descriptions. Not all
29272 groups on the server have to be listed, and not all groups in the file
29273 have to exist on the server. The file is meant purely as information to
29276 The format is quite simple; a group name, a tab, and the description.
29277 Here's the definition:
29281 line = group tab description <NEWLINE>
29282 group = <non-white-space string>
29284 description = <string>
29289 @node Emacs for Heathens
29290 @section Emacs for Heathens
29292 Believe it or not, but some people who use Gnus haven't really used
29293 Emacs much before they embarked on their journey on the Gnus Love Boat.
29294 If you are one of those unfortunates whom ``@kbd{C-M-a}'', ``kill the
29295 region'', and ``set @code{gnus-flargblossen} to an alist where the key
29296 is a regexp that is used for matching on the group name'' are magical
29297 phrases with little or no meaning, then this appendix is for you. If
29298 you are already familiar with Emacs, just ignore this and go fondle your
29302 * Keystrokes:: Entering text and executing commands.
29303 * Emacs Lisp:: The built-in Emacs programming language.
29308 @subsection Keystrokes
29312 Q: What is an experienced Emacs user?
29315 A: A person who wishes that the terminal had pedals.
29318 Yes, when you use Emacs, you are apt to use the control key, the shift
29319 key and the meta key a lot. This is very annoying to some people
29320 (notably @code{vi}le users), and the rest of us just love the hell out
29321 of it. Just give up and submit. Emacs really does stand for
29322 ``Escape-Meta-Alt-Control-Shift'', and not ``Editing Macros'', as you
29323 may have heard from other disreputable sources (like the Emacs author).
29325 The shift keys are normally located near your pinky fingers, and are
29326 normally used to get capital letters and stuff. You probably use it all
29327 the time. The control key is normally marked ``CTRL'' or something like
29328 that. The meta key is, funnily enough, never marked as such on any
29329 keyboard. The one I'm currently at has a key that's marked ``Alt'',
29330 which is the meta key on this keyboard. It's usually located somewhere
29331 to the left hand side of the keyboard, usually on the bottom row.
29333 Now, us Emacs people don't say ``press the meta-control-m key'',
29334 because that's just too inconvenient. We say ``press the @kbd{C-M-m}
29335 key''. @kbd{M-} is the prefix that means ``meta'' and ``C-'' is the
29336 prefix that means ``control''. So ``press @kbd{C-k}'' means ``press
29337 down the control key, and hold it down while you press @kbd{k}''.
29338 ``Press @kbd{C-M-k}'' means ``press down and hold down the meta key and
29339 the control key and then press @kbd{k}''. Simple, ay?
29341 This is somewhat complicated by the fact that not all keyboards have a
29342 meta key. In that case you can use the ``escape'' key. Then @kbd{M-k}
29343 means ``press escape, release escape, press @kbd{k}''. That's much more
29344 work than if you have a meta key, so if that's the case, I respectfully
29345 suggest you get a real keyboard with a meta key. You can't live without
29351 @subsection Emacs Lisp
29353 Emacs is the King of Editors because it's really a Lisp interpreter.
29354 Each and every key you tap runs some Emacs Lisp code snippet, and since
29355 Emacs Lisp is an interpreted language, that means that you can configure
29356 any key to run any arbitrary code. You just, like, do it.
29358 Gnus is written in Emacs Lisp, and is run as a bunch of interpreted
29359 functions. (These are byte-compiled for speed, but it's still
29360 interpreted.) If you decide that you don't like the way Gnus does
29361 certain things, it's trivial to have it do something a different way.
29362 (Well, at least if you know how to write Lisp code.) However, that's
29363 beyond the scope of this manual, so we are simply going to talk about
29364 some common constructs that you normally use in your @file{~/.gnus.el}
29365 file to customize Gnus. (You can also use the @file{~/.emacs} file, but
29366 in order to set things of Gnus up, it is much better to use the
29367 @file{~/.gnus.el} file, @xref{Startup Files}.)
29369 If you want to set the variable @code{gnus-florgbnize} to four (4), you
29370 write the following:
29373 (setq gnus-florgbnize 4)
29376 This function (really ``special form'') @code{setq} is the one that can
29377 set a variable to some value. This is really all you need to know. Now
29378 you can go and fill your @file{~/.gnus.el} file with lots of these to
29379 change how Gnus works.
29381 If you have put that thing in your @file{~/.gnus.el} file, it will be
29382 read and @code{eval}ed (which is Lisp-ese for ``run'') the next time you
29383 start Gnus. If you want to change the variable right away, simply say
29384 @kbd{C-x C-e} after the closing parenthesis. That will @code{eval} the
29385 previous ``form'', which is a simple @code{setq} statement here.
29387 Go ahead---just try it, if you're located at your Emacs. After you
29388 @kbd{C-x C-e}, you will see @samp{4} appear in the echo area, which
29389 is the return value of the form you @code{eval}ed.
29393 If the manual says ``set @code{gnus-read-active-file} to @code{some}'',
29397 (setq gnus-read-active-file 'some)
29400 On the other hand, if the manual says ``set @code{gnus-nntp-server} to
29401 @samp{nntp.ifi.uio.no}'', that means:
29404 (setq gnus-nntp-server "nntp.ifi.uio.no")
29407 So be careful not to mix up strings (the latter) with symbols (the
29408 former). The manual is unambiguous, but it can be confusing.
29411 @include gnus-faq.texi
29431 @c Local Variables:
29433 @c coding: iso-8859-1
29437 arch-tag: c9fa47e7-78ca-4681-bda9-9fef45d1c819