9 @documentencoding ISO-8859-1
12 Copyright @copyright{} 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
13 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 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.3 or
18 any later version published by the Free Software Foundation; with no
19 Invariant Sections, with the Front-Cover texts being ``A GNU Manual'',
20 and with the Back-Cover Texts as in (a) below. A copy of the license
21 is included in the section entitled ``GNU Free Documentation License''.
23 (a) The FSF's Back-Cover Text is: ``You have the freedom to copy and
24 modify this GNU manual. Buying copies from the FSF supports it in
25 developing GNU and promoting software freedom.''
31 \documentclass[twoside,a4paper,openright,11pt]{book}
32 \usepackage[latin1]{inputenc}
33 \usepackage{pagestyle}
36 \input{gnusconfig.tex}
38 \ifx\pdfoutput\undefined
40 \usepackage[pdftex,bookmarks,colorlinks=true]{hyperref}
48 % Adjust ../Makefile.in if you change the following line:
49 \newcommand{\gnusversionname}{No Gnus v0.11}
50 \newcommand{\gnuschaptername}{}
51 \newcommand{\gnussectionname}{}
53 \newcommand{\gnusbackslash}{/}
55 \newcommand{\gnusref}[1]{``#1'' on page \pageref{#1}}
56 \ifx\pdfoutput\undefined
57 \newcommand{\gnusuref}[1]{\gnustt{#1}}
59 \newcommand{\gnusuref}[1]{\href{#1}{\gnustt{#1}}}
61 \newcommand{\gnusxref}[1]{See ``#1'' on page \pageref{#1}}
62 \newcommand{\gnuspxref}[1]{see ``#1'' on page \pageref{#1}}
64 \newcommand{\gnuskindex}[1]{\index{#1}}
65 \newcommand{\gnusindex}[1]{\index{#1}}
67 \newcommand{\gnustt}[1]{{\gnusselectttfont{}#1}}
68 \newcommand{\gnuscode}[1]{\gnustt{#1}}
69 \newcommand{\gnusasis}[1]{\gnustt{#1}}
70 \newcommand{\gnusurl}[1]{\gnustt{#1}}
71 \newcommand{\gnuscommand}[1]{\gnustt{#1}}
72 \newcommand{\gnusenv}[1]{\gnustt{#1}}
73 \newcommand{\gnussamp}[1]{``{\fontencoding{OT1}\gnusselectttfont{}#1}''}
74 \newcommand{\gnuslisp}[1]{\gnustt{#1}}
75 \newcommand{\gnuskbd}[1]{`\gnustt{#1}'}
76 \newcommand{\gnuskey}[1]{`\gnustt{#1}'}
77 \newcommand{\gnusfile}[1]{`\gnustt{#1}'}
78 \newcommand{\gnusdfn}[1]{\textit{#1}}
79 \newcommand{\gnusi}[1]{\textit{#1}}
80 \newcommand{\gnusr}[1]{\textrm{#1}}
81 \newcommand{\gnusstrong}[1]{\textbf{#1}}
82 \newcommand{\gnusemph}[1]{\textit{#1}}
83 \newcommand{\gnusvar}[1]{{\fontsize{10pt}{10}\selectfont\textsl{\textsf{#1}}}}
84 \newcommand{\gnussc}[1]{\textsc{#1}}
85 \newcommand{\gnustitle}[1]{{\huge\textbf{#1}}}
86 \newcommand{\gnusversion}[1]{{\small\textit{#1}}}
87 \newcommand{\gnusauthor}[1]{{\large\textbf{#1}}}
88 \newcommand{\gnusresult}[1]{\gnustt{=> #1}}
89 \newcommand{\gnusacronym}[1]{\textsc{#1}}
90 \newcommand{\gnusemail}[1]{\textit{#1}}
92 \newcommand{\gnusbullet}{{${\bullet}$}}
93 \newcommand{\gnusdollar}{\$}
94 \newcommand{\gnusampersand}{\&}
95 \newcommand{\gnuspercent}{\%}
96 \newcommand{\gnushash}{\#}
97 \newcommand{\gnushat}{\symbol{"5E}}
98 \newcommand{\gnusunderline}{\symbol{"5F}}
99 \newcommand{\gnusnot}{$\neg$}
100 \newcommand{\gnustilde}{\symbol{"7E}}
101 \newcommand{\gnusless}{{$<$}}
102 \newcommand{\gnusgreater}{{$>$}}
103 \newcommand{\gnusbraceleft}{{$>$}}
104 \newcommand{\gnusbraceright}{{$>$}}
106 \newcommand{\gnushead}{\raisebox{-1cm}{\epsfig{figure=ps/gnus-head,height=1cm}}}
107 \newcommand{\gnusinteresting}{
108 \marginpar[\mbox{}\hfill\gnushead]{\gnushead}
111 \newcommand{\gnuscleardoublepage}{\ifodd\count0\mbox{}\clearpage\thispagestyle{empty}\mbox{}\clearpage\else\clearpage\fi}
113 \newcommand{\gnuspagechapter}[1]{
117 \newdimen{\gnusdimen}
120 \newcommand{\gnuschapter}[2]{
122 \ifdim \gnusdimen = 0pt\setcounter{page}{1}\pagestyle{gnus}\pagenumbering{arabic} \gnusdimen 1pt\fi
124 \renewcommand{\gnussectionname}{}
125 \renewcommand{\gnuschaptername}{#2}
126 \thispagestyle{empty}
128 \begin{picture}(500,500)(0,0)
129 \put(480,350){\makebox(0,0)[tr]{#1}}
130 \put(40,300){\makebox(500,50)[bl]{{\Huge\bf{#2}}}}
135 \newcommand{\gnusfigure}[3]{
137 \mbox{}\ifodd\count0\hspace*{-0.8cm}\else\hspace*{-3cm}\fi\begin{picture}(440,#2)
144 \newcommand{\gnusicon}[1]{
145 \marginpar[\mbox{}\hfill\raisebox{-1.5cm}{\epsfig{figure=ps/#1-up,height=1.5cm}}]{\raisebox{-1cm}{\epsfig{figure=ps/#1-up,height=1cm}}}
148 \newcommand{\gnuspicon}[1]{
149 \margindex{\epsfig{figure=#1,width=2cm}}
152 \newcommand{\gnusxface}[2]{
153 \margindex{\epsfig{figure=#1,width=1cm}\epsfig{figure=#2,width=1cm}}
156 \newcommand{\gnussmiley}[2]{
157 \margindex{\makebox[2cm]{\hfill\epsfig{figure=#1,width=0.5cm}\hfill\epsfig{figure=#2,width=0.5cm}\hfill}}
160 \newcommand{\gnusitemx}[1]{\mbox{}\vspace*{-\itemsep}\vspace*{-\parsep}\item#1}
162 \newcommand{\gnussection}[1]{
163 \renewcommand{\gnussectionname}{#1}
167 \newenvironment{codelist}%
172 \newenvironment{asislist}%
177 \newenvironment{kbdlist}%
183 \newenvironment{dfnlist}%
188 \newenvironment{stronglist}%
193 \newenvironment{samplist}%
198 \newenvironment{varlist}%
203 \newenvironment{emphlist}%
208 \newlength\gnusheadtextwidth
209 \setlength{\gnusheadtextwidth}{\headtextwidth}
210 \addtolength{\gnusheadtextwidth}{1cm}
212 \newpagestyle{gnuspreamble}%
217 \hspace*{-0.23cm}\underline{\makebox[\gnusheadtextwidth]{\mbox{}}\textbf{\hfill\roman{page}}}
221 \hspace*{-3.25cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\roman{page}\hfill\mbox{}}}
230 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
232 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
237 \newpagestyle{gnusindex}%
242 \hspace*{-0.23cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\gnuschaptername\hfill\arabic{page}}}}
246 \hspace*{-3.25cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{page}\hfill\gnuschaptername}}}
254 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
256 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
266 \makebox[12cm]{\hspace*{3.1cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{chapter}.\arabic{section}} \textbf{\gnussectionname\hfill\arabic{page}}}}}
270 \makebox[12cm]{\hspace*{-2.95cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{page}\hfill\gnuschaptername}}}}
278 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
280 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
285 \pagenumbering{roman}
286 \pagestyle{gnuspreamble}
297 %\addtolength{\oddsidemargin}{-5cm}
298 %\addtolength{\evensidemargin}{-5cm}
300 \addtolength{\textheight}{2cm}
302 \gnustitle{\gnustitlename}\hfill\gnusversion{\gnusversionname}\\
305 \hspace*{0cm}\epsfig{figure=ps/gnus-big-logo,height=15cm}
308 \gnusauthor{by Lars Magne Ingebrigtsen}
315 \thispagestyle{empty}
325 * Gnus: (gnus). The newsreader Gnus.
335 @author by Lars Magne Ingebrigtsen
337 @vskip 0pt plus 1filll
345 @top The Gnus Newsreader
349 You can read news (and mail) from within Emacs by using Gnus. The news
350 can be gotten by any nefarious means you can think of---@acronym{NNTP}, local
351 spool or your mbox file. All at the same time, if you want to push your
354 @c Adjust ../Makefile.in if you change the following line:
355 This manual corresponds to No Gnus v0.11.
370 Gnus is the advanced, self-documenting, customizable, extensible
371 unreal-time newsreader for GNU Emacs.
373 Oops. That sounds oddly familiar, so let's start over again to avoid
374 being accused of plagiarism:
376 Gnus is a message-reading laboratory. It will let you look at just
377 about anything as if it were a newsgroup. You can read mail with it,
378 you can browse directories with it, you can @code{ftp} with it---you
379 can even read news with it!
381 Gnus tries to empower people who read news the same way Emacs empowers
382 people who edit text. Gnus sets no limits to what the user should be
383 allowed to do. Users are encouraged to extend Gnus to make it behave
384 like they want it to behave. A program should not control people;
385 people should be empowered to do what they want by using (or abusing)
388 @c Adjust ../Makefile.in if you change the following line:
389 This manual corresponds to No Gnus v0.11.
391 @heading Other related manuals
393 @item Message manual: Composing messages
394 @item Emacs-MIME: Composing messages; @acronym{MIME}-specific parts.
395 @item Sieve: Managing Sieve scripts in Emacs.
396 @item PGG: @acronym{PGP/MIME} with Gnus.
397 @item SASL: @acronym{SASL} authentication in Emacs.
403 * Starting Up:: Finding news can be a pain.
404 * Group Buffer:: Selecting, subscribing and killing groups.
405 * Summary Buffer:: Reading, saving and posting articles.
406 * Article Buffer:: Displaying and handling articles.
407 * Composing Messages:: Information on sending mail and news.
408 * Select Methods:: Gnus reads all messages from various select methods.
409 * Scoring:: Assigning values to articles.
410 * Various:: General purpose settings.
411 * The End:: Farewell and goodbye.
412 * Appendices:: Terminology, Emacs intro, @acronym{FAQ}, History, Internals.
413 * GNU Free Documentation License:: The license for this documentation.
414 * Index:: Variable, function and concept index.
415 * Key Index:: Key Index.
417 Other related manuals
419 * Message:(message). Composing messages.
420 * Emacs-MIME:(emacs-mime). Composing messages; @acronym{MIME}-specific parts.
421 * Sieve:(sieve). Managing Sieve scripts in Emacs.
422 * PGG:(pgg). @acronym{PGP/MIME} with Gnus.
423 * SASL:(sasl). @acronym{SASL} authentication in Emacs.
426 --- The Detailed Node Listing ---
430 * Finding the News:: Choosing a method for getting news.
431 * The First Time:: What does Gnus do the first time you start it?
432 * The Server is Down:: How can I read my mail then?
433 * Slave Gnusae:: You can have more than one Gnus active at a time.
434 * Fetching a Group:: Starting Gnus just to read a group.
435 * New Groups:: What is Gnus supposed to do with new groups?
436 * Changing Servers:: You may want to move from one server to another.
437 * Startup Files:: Those pesky startup files---@file{.newsrc}.
438 * Auto Save:: Recovering from a crash.
439 * The Active File:: Reading the active file over a slow line Takes Time.
440 * Startup Variables:: Other variables you might change.
444 * Checking New Groups:: Determining what groups are new.
445 * Subscription Methods:: What Gnus should do with new groups.
446 * Filtering New Groups:: Making Gnus ignore certain new groups.
450 * Group Buffer Format:: Information listed and how you can change it.
451 * Group Maneuvering:: Commands for moving in the group buffer.
452 * Selecting a Group:: Actually reading news.
453 * Subscription Commands:: Unsubscribing, killing, subscribing.
454 * Group Data:: Changing the info for a group.
455 * Group Levels:: Levels? What are those, then?
456 * Group Score:: A mechanism for finding out what groups you like.
457 * Marking Groups:: You can mark groups for later processing.
458 * Foreign Groups:: Creating and editing groups.
459 * Group Parameters:: Each group may have different parameters set.
460 * Listing Groups:: Gnus can list various subsets of the groups.
461 * Sorting Groups:: Re-arrange the group order.
462 * Group Maintenance:: Maintaining a tidy @file{.newsrc} file.
463 * Browse Foreign Server:: You can browse a server. See what it has to offer.
464 * Exiting Gnus:: Stop reading news and get some work done.
465 * Group Topics:: A folding group mode divided into topics.
466 * Non-ASCII Group Names:: Accessing groups of non-English names.
467 * Misc Group Stuff:: Other stuff that you can to do.
471 * Group Line Specification:: Deciding how the group buffer is to look.
472 * Group Mode Line Specification:: The group buffer mode line.
473 * Group Highlighting:: Having nice colors in the group buffer.
477 * Topic Commands:: Interactive E-Z commands.
478 * Topic Variables:: How to customize the topics the Lisp Way.
479 * Topic Sorting:: Sorting each topic individually.
480 * Topic Topology:: A map of the world.
481 * Topic Parameters:: Parameters that apply to all groups in a topic.
485 * Scanning New Messages:: Asking Gnus to see whether new messages have arrived.
486 * Group Information:: Information and help on groups and Gnus.
487 * Group Timestamp:: Making Gnus keep track of when you last read a group.
488 * File Commands:: Reading and writing the Gnus files.
489 * Sieve Commands:: Managing Sieve scripts.
493 * Summary Buffer Format:: Deciding how the summary buffer is to look.
494 * Summary Maneuvering:: Moving around the summary buffer.
495 * Choosing Articles:: Reading articles.
496 * Paging the Article:: Scrolling the current article.
497 * Reply Followup and Post:: Posting articles.
498 * Delayed Articles:: Send articles at a later time.
499 * Marking Articles:: Marking articles as read, expirable, etc.
500 * Limiting:: You can limit the summary buffer.
501 * Threading:: How threads are made.
502 * Sorting the Summary Buffer:: How articles and threads are sorted.
503 * Asynchronous Fetching:: Gnus might be able to pre-fetch articles.
504 * Article Caching:: You may store articles in a cache.
505 * Persistent Articles:: Making articles expiry-resistant.
506 * Sticky Articles:: Article buffers that are not reused.
507 * Article Backlog:: Having already read articles hang around.
508 * Saving Articles:: Ways of customizing article saving.
509 * Decoding Articles:: Gnus can treat series of (uu)encoded articles.
510 * Article Treatment:: The article buffer can be mangled at will.
511 * MIME Commands:: Doing MIMEy things with the articles.
512 * Charsets:: Character set issues.
513 * Article Commands:: Doing various things with the article buffer.
514 * Summary Sorting:: Sorting the summary buffer in various ways.
515 * Finding the Parent:: No child support? Get the parent.
516 * Alternative Approaches:: Reading using non-default summaries.
517 * Tree Display:: A more visual display of threads.
518 * Mail Group Commands:: Some commands can only be used in mail groups.
519 * Various Summary Stuff:: What didn't fit anywhere else.
520 * Exiting the Summary Buffer:: Returning to the Group buffer,
521 or reselecting the current group.
522 * Crosspost Handling:: How crossposted articles are dealt with.
523 * Duplicate Suppression:: An alternative when crosspost handling fails.
524 * Security:: Decrypt and Verify.
525 * Mailing List:: Mailing list minor mode.
527 Summary Buffer Format
529 * Summary Buffer Lines:: You can specify how summary lines should look.
530 * To From Newsgroups:: How to not display your own name.
531 * Summary Buffer Mode Line:: You can say how the mode line should look.
532 * Summary Highlighting:: Making the summary buffer all pretty and nice.
536 * Choosing Commands:: Commands for choosing articles.
537 * Choosing Variables:: Variables that influence these commands.
539 Reply, Followup and Post
541 * Summary Mail Commands:: Sending mail.
542 * Summary Post Commands:: Sending news.
543 * Summary Message Commands:: Other Message-related commands.
544 * Canceling and Superseding::
548 * Unread Articles:: Marks for unread articles.
549 * Read Articles:: Marks for read articles.
550 * Other Marks:: Marks that do not affect readedness.
551 * Setting Marks:: How to set and remove marks.
552 * Generic Marking Commands:: How to customize the marking.
553 * Setting Process Marks:: How to mark articles for later processing.
557 * Customizing Threading:: Variables you can change to affect the threading.
558 * Thread Commands:: Thread based commands in the summary buffer.
560 Customizing Threading
562 * Loose Threads:: How Gnus gathers loose threads into bigger threads.
563 * Filling In Threads:: Making the threads displayed look fuller.
564 * More Threading:: Even more variables for fiddling with threads.
565 * Low-Level Threading:: You thought it was over@dots{} but you were wrong!
569 * Uuencoded Articles:: Uudecode articles.
570 * Shell Archives:: Unshar articles.
571 * PostScript Files:: Split PostScript.
572 * Other Files:: Plain save and binhex.
573 * Decoding Variables:: Variables for a happy decoding.
574 * Viewing Files:: You want to look at the result of the decoding?
578 * Rule Variables:: Variables that say how a file is to be viewed.
579 * Other Decode Variables:: Other decode variables.
580 * Uuencoding and Posting:: Variables for customizing uuencoding.
584 * Article Highlighting:: You want to make the article look like fruit salad.
585 * Article Fontisizing:: Making emphasized text look nice.
586 * Article Hiding:: You also want to make certain info go away.
587 * Article Washing:: Lots of way-neat functions to make life better.
588 * Article Header:: Doing various header transformations.
589 * Article Buttons:: Click on URLs, Message-IDs, addresses and the like.
590 * Article Button Levels:: Controlling appearance of buttons.
591 * Article Date:: Grumble, UT!
592 * Article Display:: Display various stuff---X-Face, Picons, Smileys
593 * Article Signature:: What is a signature?
594 * Article Miscellanea:: Various other stuff.
596 Alternative Approaches
598 * Pick and Read:: First mark articles and then read them.
599 * Binary Groups:: Auto-decode all articles.
601 Various Summary Stuff
603 * Summary Group Information:: Information oriented commands.
604 * Searching for Articles:: Multiple article commands.
605 * Summary Generation Commands::
606 * Really Various Summary Commands:: Those pesky non-conformant commands.
610 * Hiding Headers:: Deciding what headers should be displayed.
611 * Using MIME:: Pushing articles through @acronym{MIME} before reading them.
612 * Customizing Articles:: Tailoring the look of the articles.
613 * Article Keymap:: Keystrokes available in the article buffer.
614 * Misc Article:: Other stuff.
618 * Mail:: Mailing and replying.
619 * Posting Server:: What server should you post and mail via?
620 * POP before SMTP:: You cannot send a mail unless you read a mail.
621 * Mail and Post:: Mailing and posting at the same time.
622 * Archived Messages:: Where Gnus stores the messages you've sent.
623 * Posting Styles:: An easier way to specify who you are.
624 * Drafts:: Postponing messages and rejected messages.
625 * Rejected Articles:: What happens if the server doesn't like your article?
626 * Signing and encrypting:: How to compose secure messages.
630 * Server Buffer:: Making and editing virtual servers.
631 * Getting News:: Reading USENET news with Gnus.
632 * Getting Mail:: Reading your personal mail with Gnus.
633 * Browsing the Web:: Getting messages from a plethora of Web sources.
634 * IMAP:: Using Gnus as a @acronym{IMAP} client.
635 * Other Sources:: Reading directories, files, SOUP packets.
636 * Combined Groups:: Combining groups into one group.
637 * Email Based Diary:: Using mails to manage diary events in Gnus.
638 * Gnus Unplugged:: Reading news and mail offline.
642 * Server Buffer Format:: You can customize the look of this buffer.
643 * Server Commands:: Commands to manipulate servers.
644 * Example Methods:: Examples server specifications.
645 * Creating a Virtual Server:: An example session.
646 * Server Variables:: Which variables to set.
647 * Servers and Methods:: You can use server names as select methods.
648 * Unavailable Servers:: Some servers you try to contact may be down.
652 * NNTP:: Reading news from an @acronym{NNTP} server.
653 * News Spool:: Reading news from the local spool.
657 * Direct Functions:: Connecting directly to the server.
658 * Indirect Functions:: Connecting indirectly to the server.
659 * Common Variables:: Understood by several connection functions.
660 * NNTP marks:: Storing marks for @acronym{NNTP} servers.
664 * Mail in a Newsreader:: Important introductory notes.
665 * Getting Started Reading Mail:: A simple cookbook example.
666 * Splitting Mail:: How to create mail groups.
667 * Mail Sources:: How to tell Gnus where to get mail from.
668 * Mail Back End Variables:: Variables for customizing mail handling.
669 * Fancy Mail Splitting:: Gnus can do hairy splitting of incoming mail.
670 * Group Mail Splitting:: Use group customize to drive mail splitting.
671 * Incorporating Old Mail:: What about the old mail you have?
672 * Expiring Mail:: Getting rid of unwanted mail.
673 * Washing Mail:: Removing cruft from the mail you get.
674 * Duplicates:: Dealing with duplicated mail.
675 * Not Reading Mail:: Using mail back ends for reading other files.
676 * Choosing a Mail Back End:: Gnus can read a variety of mail formats.
680 * Mail Source Specifiers:: How to specify what a mail source is.
681 * Mail Source Customization:: Some variables that influence things.
682 * Fetching Mail:: Using the mail source specifiers.
684 Choosing a Mail Back End
686 * Unix Mail Box:: Using the (quite) standard Un*x mbox.
687 * Babyl:: Babyl was used by older versions of Rmail.
688 * Mail Spool:: Store your mail in a private spool?
689 * MH Spool:: An mhspool-like back end.
690 * Maildir:: Another one-file-per-message format.
691 * Mail Folders:: Having one file for each group.
692 * Comparing Mail Back Ends:: An in-depth looks at pros and cons.
697 * Web Searches:: Creating groups from articles that match a string.
698 * Slashdot:: Reading the Slashdot comments.
699 * Ultimate:: The Ultimate Bulletin Board systems.
700 * Web Archive:: Reading mailing list archived on web.
701 * RSS:: Reading RDF site summary.
702 * Customizing W3:: Doing stuff to Emacs/W3 from Gnus.
706 * Splitting in IMAP:: Splitting mail with nnimap.
707 * Expiring in IMAP:: Expiring mail with nnimap.
708 * Editing IMAP ACLs:: Limiting/enabling other users access to a mailbox.
709 * Expunging mailboxes:: Equivalent of a ``compress mailbox'' button.
710 * A note on namespaces:: How to (not) use @acronym{IMAP} namespace in Gnus.
711 * Debugging IMAP:: What to do when things don't work.
715 * Directory Groups:: You can read a directory as if it was a newsgroup.
716 * Anything Groups:: Dired? Who needs dired?
717 * Document Groups:: Single files can be the basis of a group.
718 * SOUP:: Reading @sc{soup} packets ``offline''.
719 * Mail-To-News Gateways:: Posting articles via mail-to-news gateways.
723 * Document Server Internals:: How to add your own document types.
727 * SOUP Commands:: Commands for creating and sending @sc{soup} packets
728 * SOUP Groups:: A back end for reading @sc{soup} packets.
729 * SOUP Replies:: How to enable @code{nnsoup} to take over mail and news.
733 * Virtual Groups:: Combining articles from many groups.
734 * Kibozed Groups:: Looking through parts of the newsfeed for articles.
738 * The NNDiary Back End:: Basic setup and usage.
739 * The Gnus Diary Library:: Utility toolkit on top of nndiary.
740 * Sending or Not Sending:: A final note on sending diary messages.
744 * Diary Messages:: What makes a message valid for nndiary.
745 * Running NNDiary:: NNDiary has two modes of operation.
746 * Customizing NNDiary:: Bells and whistles.
748 The Gnus Diary Library
750 * Diary Summary Line Format:: A nicer summary buffer line format.
751 * Diary Articles Sorting:: A nicer way to sort messages.
752 * Diary Headers Generation:: Not doing it manually.
753 * Diary Group Parameters:: Not handling them manually.
757 * Agent Basics:: How it all is supposed to work.
758 * Agent Categories:: How to tell the Gnus Agent what to download.
759 * Agent Commands:: New commands for all the buffers.
760 * Agent Visuals:: Ways that the agent may effect your summary buffer.
761 * Agent as Cache:: The Agent is a big cache too.
762 * Agent Expiry:: How to make old articles go away.
763 * Agent Regeneration:: How to recover from lost connections and other accidents.
764 * Agent and flags:: How the Agent maintains flags.
765 * Agent and IMAP:: How to use the Agent with @acronym{IMAP}.
766 * Outgoing Messages:: What happens when you post/mail something?
767 * Agent Variables:: Customizing is fun.
768 * Example Setup:: An example @file{~/.gnus.el} file for offline people.
769 * Batching Agents:: How to fetch news from a @code{cron} job.
770 * Agent Caveats:: What you think it'll do and what it does.
774 * Category Syntax:: What a category looks like.
775 * Category Buffer:: A buffer for maintaining categories.
776 * Category Variables:: Customize'r'Us.
780 * Group Agent Commands:: Configure groups and fetch their contents.
781 * Summary Agent Commands:: Manually select then fetch specific articles.
782 * Server Agent Commands:: Select the servers that are supported by the agent.
786 * Summary Score Commands:: Adding score entries for the current group.
787 * Group Score Commands:: General score commands.
788 * Score Variables:: Customize your scoring. (My, what terminology).
789 * Score File Format:: What a score file may contain.
790 * Score File Editing:: You can edit score files by hand as well.
791 * Adaptive Scoring:: Big Sister Gnus knows what you read.
792 * Home Score File:: How to say where new score entries are to go.
793 * Followups To Yourself:: Having Gnus notice when people answer you.
794 * Scoring On Other Headers:: Scoring on non-standard headers.
795 * Scoring Tips:: How to score effectively.
796 * Reverse Scoring:: That problem child of old is not problem.
797 * Global Score Files:: Earth-spanning, ear-splitting score files.
798 * Kill Files:: They are still here, but they can be ignored.
799 * Converting Kill Files:: Translating kill files to score files.
800 * Advanced Scoring:: Using logical expressions to build score rules.
801 * Score Decays:: It can be useful to let scores wither away.
805 * Advanced Scoring Syntax:: A definition.
806 * Advanced Scoring Examples:: What they look like.
807 * Advanced Scoring Tips:: Getting the most out of it.
811 * Process/Prefix:: A convention used by many treatment commands.
812 * Interactive:: Making Gnus ask you many questions.
813 * Symbolic Prefixes:: How to supply some Gnus functions with options.
814 * Formatting Variables:: You can specify what buffers should look like.
815 * Window Layout:: Configuring the Gnus buffer windows.
816 * Faces and Fonts:: How to change how faces look.
817 * Compilation:: How to speed Gnus up.
818 * Mode Lines:: Displaying information in the mode lines.
819 * Highlighting and Menus:: Making buffers look all nice and cozy.
820 * Buttons:: Get tendinitis in ten easy steps!
821 * Daemons:: Gnus can do things behind your back.
822 * NoCeM:: How to avoid spam and other fatty foods.
823 * Undo:: Some actions can be undone.
824 * Predicate Specifiers:: Specifying predicates.
825 * Moderation:: What to do if you're a moderator.
826 * Image Enhancements:: Modern versions of Emacs/XEmacs can display images.
827 * Fuzzy Matching:: What's the big fuzz?
828 * Thwarting Email Spam:: Simple ways to avoid unsolicited commercial email.
829 * Spam Package:: A package for filtering and processing spam.
830 * The Gnus Registry:: A package for tracking messages by Message-ID.
831 * Other modes:: Interaction with other modes.
832 * Various Various:: Things that are really various.
836 * Formatting Basics:: A formatting variable is basically a format string.
837 * Mode Line Formatting:: Some rules about mode line formatting variables.
838 * Advanced Formatting:: Modifying output in various ways.
839 * User-Defined Specs:: Having Gnus call your own functions.
840 * Formatting Fonts:: Making the formatting look colorful and nice.
841 * Positioning Point:: Moving point to a position after an operation.
842 * Tabulation:: Tabulating your output.
843 * Wide Characters:: Dealing with wide characters.
847 * X-Face:: Display a funky, teensy black-and-white image.
848 * Face:: Display a funkier, teensier colored image.
849 * Smileys:: Show all those happy faces the way they were
851 * Picons:: How to display pictures of what you're reading.
852 * XVarious:: Other XEmacsy Gnusey variables.
856 * The problem of spam:: Some background, and some solutions
857 * Anti-Spam Basics:: Simple steps to reduce the amount of spam.
858 * SpamAssassin:: How to use external anti-spam tools.
859 * Hashcash:: Reduce spam by burning CPU time.
863 * Spam Package Introduction::
864 * Filtering Incoming Mail::
865 * Detecting Spam in Groups::
866 * Spam and Ham Processors::
867 * Spam Package Configuration Examples::
869 * Extending the Spam package::
870 * Spam Statistics Package::
872 Spam Statistics Package
874 * Creating a spam-stat dictionary::
875 * Splitting mail using spam-stat::
876 * Low-level interface to the spam-stat dictionary::
880 * XEmacs:: Requirements for installing under XEmacs.
881 * History:: How Gnus got where it is today.
882 * On Writing Manuals:: Why this is not a beginner's guide.
883 * Terminology:: We use really difficult, like, words here.
884 * Customization:: Tailoring Gnus to your needs.
885 * Troubleshooting:: What you might try if things do not work.
886 * Gnus Reference Guide:: Rilly, rilly technical stuff.
887 * Emacs for Heathens:: A short introduction to Emacsian terms.
888 * Frequently Asked Questions:: The Gnus FAQ
892 * Gnus Versions:: What Gnus versions have been released.
893 * Other Gnus Versions:: Other Gnus versions that also have been released.
894 * Why?:: What's the point of Gnus?
895 * Compatibility:: Just how compatible is Gnus with @sc{gnus}?
896 * Conformity:: Gnus tries to conform to all standards.
897 * Emacsen:: Gnus can be run on a few modern Emacsen.
898 * Gnus Development:: How Gnus is developed.
899 * Contributors:: Oodles of people.
900 * New Features:: Pointers to some of the new stuff in Gnus.
904 * ding Gnus:: New things in Gnus 5.0/5.1, the first new Gnus.
905 * September Gnus:: The Thing Formally Known As Gnus 5.2/5.3.
906 * Red Gnus:: Third time best---Gnus 5.4/5.5.
907 * Quassia Gnus:: Two times two is four, or Gnus 5.6/5.7.
908 * Pterodactyl Gnus:: Pentad also starts with P, AKA Gnus 5.8/5.9.
909 * Oort Gnus:: It's big. It's far out. Gnus 5.10/5.11.
910 * No Gnus:: Very punny.
914 * Slow/Expensive Connection:: You run a local Emacs and get the news elsewhere.
915 * Slow Terminal Connection:: You run a remote Emacs.
916 * Little Disk Space:: You feel that having large setup files is icky.
917 * Slow Machine:: You feel like buying a faster machine.
921 * Gnus Utility Functions:: Common functions and variable to use.
922 * Back End Interface:: How Gnus communicates with the servers.
923 * Score File Syntax:: A BNF definition of the score file standard.
924 * Headers:: How Gnus stores headers internally.
925 * Ranges:: A handy format for storing mucho numbers.
926 * Group Info:: The group info format.
927 * Extended Interactive:: Symbolic prefixes and stuff.
928 * Emacs/XEmacs Code:: Gnus can be run under all modern Emacsen.
929 * Various File Formats:: Formats of files that Gnus use.
933 * Required Back End Functions:: Functions that must be implemented.
934 * Optional Back End Functions:: Functions that need not be implemented.
935 * Error Messaging:: How to get messages and report errors.
936 * Writing New Back Ends:: Extending old back ends.
937 * Hooking New Back Ends Into Gnus:: What has to be done on the Gnus end.
938 * Mail-like Back Ends:: Some tips on mail back ends.
942 * Active File Format:: Information on articles and groups available.
943 * Newsgroups File Format:: Group descriptions.
947 * Keystrokes:: Entering text and executing commands.
948 * Emacs Lisp:: The built-in Emacs programming language.
954 @chapter Starting Gnus
957 If you haven't used Emacs much before using Gnus, read @ref{Emacs for
962 If your system administrator has set things up properly, starting Gnus
963 and reading news is extremely easy---you just type @kbd{M-x gnus} in
964 your Emacs. If not, you should customize the variable
965 @code{gnus-select-method} as described in @ref{Finding the News}. For a
966 minimal setup for posting should also customize the variables
967 @code{user-full-name} and @code{user-mail-address}.
969 @findex gnus-other-frame
970 @kindex M-x gnus-other-frame
971 If you want to start Gnus in a different frame, you can use the command
972 @kbd{M-x gnus-other-frame} instead.
974 If things do not go smoothly at startup, you have to twiddle some
975 variables in your @file{~/.gnus.el} file. This file is similar to
976 @file{~/.emacs}, but is read when Gnus starts.
978 If you puzzle at any terms used in this manual, please refer to the
979 terminology section (@pxref{Terminology}).
982 * Finding the News:: Choosing a method for getting news.
983 * The First Time:: What does Gnus do the first time you start it?
984 * The Server is Down:: How can I read my mail then?
985 * Slave Gnusae:: You can have more than one Gnus active at a time.
986 * New Groups:: What is Gnus supposed to do with new groups?
987 * Changing Servers:: You may want to move from one server to another.
988 * Startup Files:: Those pesky startup files---@file{.newsrc}.
989 * Auto Save:: Recovering from a crash.
990 * The Active File:: Reading the active file over a slow line Takes Time.
991 * Startup Variables:: Other variables you might change.
995 @node Finding the News
996 @section Finding the News
999 First of all, you should know that there is a special buffer called
1000 @code{*Server*} that lists all the servers Gnus knows about. You can
1001 press @kbd{^} from the Group buffer to see it. In the Server buffer,
1002 you can press @kbd{RET} on a defined server to see all the groups it
1003 serves (subscribed or not!). You can also add or delete servers, edit
1004 a foreign server's definition, agentize or de-agentize a server, and
1005 do many other neat things. @xref{Server Buffer}.
1006 @xref{Foreign Groups}. @xref{Agent Basics}.
1008 @vindex gnus-select-method
1010 The @code{gnus-select-method} variable says where Gnus should look for
1011 news. This variable should be a list where the first element says
1012 @dfn{how} and the second element says @dfn{where}. This method is your
1013 native method. All groups not fetched with this method are
1016 For instance, if the @samp{news.somewhere.edu} @acronym{NNTP} server is where
1017 you want to get your daily dosage of news from, you'd say:
1020 (setq gnus-select-method '(nntp "news.somewhere.edu"))
1023 If you want to read directly from the local spool, say:
1026 (setq gnus-select-method '(nnspool ""))
1029 If you can use a local spool, you probably should, as it will almost
1030 certainly be much faster. But do not use the local spool if your
1031 server is running Leafnode (which is a simple, standalone private news
1032 server); in this case, use @code{(nntp "localhost")}.
1034 @vindex gnus-nntpserver-file
1036 @cindex @acronym{NNTP} server
1037 If this variable is not set, Gnus will take a look at the
1038 @env{NNTPSERVER} environment variable. If that variable isn't set,
1039 Gnus will see whether @code{gnus-nntpserver-file}
1040 (@file{/etc/nntpserver} by default) has any opinions on the matter.
1041 If that fails as well, Gnus will try to use the machine running Emacs
1042 as an @acronym{NNTP} server. That's a long shot, though.
1044 @vindex gnus-nntp-server
1045 If @code{gnus-nntp-server} is set, this variable will override
1046 @code{gnus-select-method}. You should therefore set
1047 @code{gnus-nntp-server} to @code{nil}, which is what it is by default.
1049 @vindex gnus-secondary-servers
1050 @vindex gnus-nntp-server
1051 You can also make Gnus prompt you interactively for the name of an
1052 @acronym{NNTP} server. If you give a non-numerical prefix to @code{gnus}
1053 (i.e., @kbd{C-u M-x gnus}), Gnus will let you choose between the servers
1054 in the @code{gnus-secondary-servers} list (if any). You can also just
1055 type in the name of any server you feel like visiting. (Note that this
1056 will set @code{gnus-nntp-server}, which means that if you then @kbd{M-x
1057 gnus} later in the same Emacs session, Gnus will contact the same
1060 @findex gnus-group-browse-foreign-server
1062 However, if you use one @acronym{NNTP} server regularly and are just
1063 interested in a couple of groups from a different server, you would be
1064 better served by using the @kbd{B} command in the group buffer. It will
1065 let you have a look at what groups are available, and you can subscribe
1066 to any of the groups you want to. This also makes @file{.newsrc}
1067 maintenance much tidier. @xref{Foreign Groups}.
1069 @vindex gnus-secondary-select-methods
1071 A slightly different approach to foreign groups is to set the
1072 @code{gnus-secondary-select-methods} variable. The select methods
1073 listed in this variable are in many ways just as native as the
1074 @code{gnus-select-method} server. They will also be queried for active
1075 files during startup (if that's required), and new newsgroups that
1076 appear on these servers will be subscribed (or not) just as native
1079 For instance, if you use the @code{nnmbox} back end to read your mail,
1080 you would typically set this variable to
1083 (setq gnus-secondary-select-methods '((nnmbox "")))
1086 Note: the @acronym{NNTP} back end stores marks in marks files
1087 (@pxref{NNTP marks}). This feature makes it easy to share marks between
1088 several Gnus installations, but may slow down things a bit when fetching
1089 new articles. @xref{NNTP marks}, for more information.
1092 @node The First Time
1093 @section The First Time
1094 @cindex first time usage
1096 If no startup files exist (@pxref{Startup Files}), Gnus will try to
1097 determine what groups should be subscribed by default.
1099 @vindex gnus-default-subscribed-newsgroups
1100 If the variable @code{gnus-default-subscribed-newsgroups} is set, Gnus
1101 will subscribe you to just those groups in that list, leaving the rest
1102 killed. Your system administrator should have set this variable to
1105 Since she hasn't, Gnus will just subscribe you to a few arbitrarily
1106 picked groups (i.e., @samp{*.newusers}). (@dfn{Arbitrary} is defined
1107 here as @dfn{whatever Lars thinks you should read}.)
1109 You'll also be subscribed to the Gnus documentation group, which should
1110 help you with most common problems.
1112 If @code{gnus-default-subscribed-newsgroups} is @code{t}, Gnus will just
1113 use the normal functions for handling new groups, and not do anything
1117 @node The Server is Down
1118 @section The Server is Down
1119 @cindex server errors
1121 If the default server is down, Gnus will understandably have some
1122 problems starting. However, if you have some mail groups in addition to
1123 the news groups, you may want to start Gnus anyway.
1125 Gnus, being the trusting sort of program, will ask whether to proceed
1126 without a native select method if that server can't be contacted. This
1127 will happen whether the server doesn't actually exist (i.e., you have
1128 given the wrong address) or the server has just momentarily taken ill
1129 for some reason or other. If you decide to continue and have no foreign
1130 groups, you'll find it difficult to actually do anything in the group
1131 buffer. But, hey, that's your problem. Blllrph!
1133 @findex gnus-no-server
1134 @kindex M-x gnus-no-server
1136 If you know that the server is definitely down, or you just want to read
1137 your mail without bothering with the server at all, you can use the
1138 @code{gnus-no-server} command to start Gnus. That might come in handy
1139 if you're in a hurry as well. This command will not attempt to contact
1140 your primary server---instead, it will just activate all groups on level
1141 1 and 2. (You should preferably keep no native groups on those two
1142 levels.) Also @pxref{Group Levels}.
1146 @section Slave Gnusae
1149 You might want to run more than one Emacs with more than one Gnus at the
1150 same time. If you are using different @file{.newsrc} files (e.g., if you
1151 are using the two different Gnusae to read from two different servers),
1152 that is no problem whatsoever. You just do it.
1154 The problem appears when you want to run two Gnusae that use the same
1155 @file{.newsrc} file.
1157 To work around that problem some, we here at the Think-Tank at the Gnus
1158 Towers have come up with a new concept: @dfn{Masters} and
1159 @dfn{slaves}. (We have applied for a patent on this concept, and have
1160 taken out a copyright on those words. If you wish to use those words in
1161 conjunction with each other, you have to send $1 per usage instance to
1162 me. Usage of the patent (@dfn{Master/Slave Relationships In Computer
1163 Applications}) will be much more expensive, of course.)
1166 Anyway, you start one Gnus up the normal way with @kbd{M-x gnus} (or
1167 however you do it). Each subsequent slave Gnusae should be started with
1168 @kbd{M-x gnus-slave}. These slaves won't save normal @file{.newsrc}
1169 files, but instead save @dfn{slave files} that contain information only
1170 on what groups have been read in the slave session. When a master Gnus
1171 starts, it will read (and delete) these slave files, incorporating all
1172 information from them. (The slave files will be read in the sequence
1173 they were created, so the latest changes will have precedence.)
1175 Information from the slave files has, of course, precedence over the
1176 information in the normal (i.e., master) @file{.newsrc} file.
1178 If the @file{.newsrc*} files have not been saved in the master when the
1179 slave starts, you may be prompted as to whether to read an auto-save
1180 file. If you answer ``yes'', the unsaved changes to the master will be
1181 incorporated into the slave. If you answer ``no'', the slave may see some
1182 messages as unread that have been read in the master.
1189 @cindex subscription
1191 @vindex gnus-check-new-newsgroups
1192 If you are satisfied that you really never want to see any new groups,
1193 you can set @code{gnus-check-new-newsgroups} to @code{nil}. This will
1194 also save you some time at startup. Even if this variable is
1195 @code{nil}, you can always subscribe to the new groups just by pressing
1196 @kbd{U} in the group buffer (@pxref{Group Maintenance}). This variable
1197 is @code{ask-server} by default. If you set this variable to
1198 @code{always}, then Gnus will query the back ends for new groups even
1199 when you do the @kbd{g} command (@pxref{Scanning New Messages}).
1202 * Checking New Groups:: Determining what groups are new.
1203 * Subscription Methods:: What Gnus should do with new groups.
1204 * Filtering New Groups:: Making Gnus ignore certain new groups.
1208 @node Checking New Groups
1209 @subsection Checking New Groups
1211 Gnus normally determines whether a group is new or not by comparing the
1212 list of groups from the active file(s) with the lists of subscribed and
1213 dead groups. This isn't a particularly fast method. If
1214 @code{gnus-check-new-newsgroups} is @code{ask-server}, Gnus will ask the
1215 server for new groups since the last time. This is both faster and
1216 cheaper. This also means that you can get rid of the list of killed
1217 groups altogether, so you may set @code{gnus-save-killed-list} to
1218 @code{nil}, which will save time both at startup, at exit, and all over.
1219 Saves disk space, too. Why isn't this the default, then?
1220 Unfortunately, not all servers support this command.
1222 I bet I know what you're thinking now: How do I find out whether my
1223 server supports @code{ask-server}? No? Good, because I don't have a
1224 fail-safe answer. I would suggest just setting this variable to
1225 @code{ask-server} and see whether any new groups appear within the next
1226 few days. If any do, then it works. If none do, then it doesn't
1227 work. I could write a function to make Gnus guess whether the server
1228 supports @code{ask-server}, but it would just be a guess. So I won't.
1229 You could @code{telnet} to the server and say @code{HELP} and see
1230 whether it lists @samp{NEWGROUPS} among the commands it understands. If
1231 it does, then it might work. (But there are servers that lists
1232 @samp{NEWGROUPS} without supporting the function properly.)
1234 This variable can also be a list of select methods. If so, Gnus will
1235 issue an @code{ask-server} command to each of the select methods, and
1236 subscribe them (or not) using the normal methods. This might be handy
1237 if you are monitoring a few servers for new groups. A side effect is
1238 that startup will take much longer, so you can meditate while waiting.
1239 Use the mantra ``dingnusdingnusdingnus'' to achieve permanent bliss.
1242 @node Subscription Methods
1243 @subsection Subscription Methods
1245 @vindex gnus-subscribe-newsgroup-method
1246 What Gnus does when it encounters a new group is determined by the
1247 @code{gnus-subscribe-newsgroup-method} variable.
1249 This variable should contain a function. This function will be called
1250 with the name of the new group as the only parameter.
1252 Some handy pre-fab functions are:
1256 @item gnus-subscribe-zombies
1257 @vindex gnus-subscribe-zombies
1258 Make all new groups zombies. This is the default. You can browse the
1259 zombies later (with @kbd{A z}) and either kill them all off properly
1260 (with @kbd{S z}), or subscribe to them (with @kbd{u}).
1262 @item gnus-subscribe-randomly
1263 @vindex gnus-subscribe-randomly
1264 Subscribe all new groups in arbitrary order. This really means that all
1265 new groups will be added at ``the top'' of the group buffer.
1267 @item gnus-subscribe-alphabetically
1268 @vindex gnus-subscribe-alphabetically
1269 Subscribe all new groups in alphabetical order.
1271 @item gnus-subscribe-hierarchically
1272 @vindex gnus-subscribe-hierarchically
1273 Subscribe all new groups hierarchically. The difference between this
1274 function and @code{gnus-subscribe-alphabetically} is slight.
1275 @code{gnus-subscribe-alphabetically} will subscribe new groups in a strictly
1276 alphabetical fashion, while this function will enter groups into its
1277 hierarchy. So if you want to have the @samp{rec} hierarchy before the
1278 @samp{comp} hierarchy, this function will not mess that configuration
1279 up. Or something like that.
1281 @item gnus-subscribe-interactively
1282 @vindex gnus-subscribe-interactively
1283 Subscribe new groups interactively. This means that Gnus will ask
1284 you about @strong{all} new groups. The groups you choose to subscribe
1285 to will be subscribed hierarchically.
1287 @item gnus-subscribe-killed
1288 @vindex gnus-subscribe-killed
1289 Kill all new groups.
1291 @item gnus-subscribe-topics
1292 @vindex gnus-subscribe-topics
1293 Put the groups into the topic that has a matching @code{subscribe} topic
1294 parameter (@pxref{Topic Parameters}). For instance, a @code{subscribe}
1295 topic parameter that looks like
1301 will mean that all groups that match that regex will be subscribed under
1304 If no topics match the groups, the groups will be subscribed in the
1309 @vindex gnus-subscribe-hierarchical-interactive
1310 A closely related variable is
1311 @code{gnus-subscribe-hierarchical-interactive}. (That's quite a
1312 mouthful.) If this variable is non-@code{nil}, Gnus will ask you in a
1313 hierarchical fashion whether to subscribe to new groups or not. Gnus
1314 will ask you for each sub-hierarchy whether you want to descend the
1317 One common mistake is to set the variable a few paragraphs above
1318 (@code{gnus-subscribe-newsgroup-method}) to
1319 @code{gnus-subscribe-hierarchical-interactive}. This is an error. This
1320 will not work. This is ga-ga. So don't do it.
1323 @node Filtering New Groups
1324 @subsection Filtering New Groups
1326 A nice and portable way to control which new newsgroups should be
1327 subscribed (or ignored) is to put an @dfn{options} line at the start of
1328 the @file{.newsrc} file. Here's an example:
1331 options -n !alt.all !rec.all sci.all
1334 @vindex gnus-subscribe-options-newsgroup-method
1335 This line obviously belongs to a serious-minded intellectual scientific
1336 person (or she may just be plain old boring), because it says that all
1337 groups that have names beginning with @samp{alt} and @samp{rec} should
1338 be ignored, and all groups with names beginning with @samp{sci} should
1339 be subscribed. Gnus will not use the normal subscription method for
1340 subscribing these groups.
1341 @code{gnus-subscribe-options-newsgroup-method} is used instead. This
1342 variable defaults to @code{gnus-subscribe-alphabetically}.
1344 @vindex gnus-options-not-subscribe
1345 @vindex gnus-options-subscribe
1346 If you don't want to mess with your @file{.newsrc} file, you can just
1347 set the two variables @code{gnus-options-subscribe} and
1348 @code{gnus-options-not-subscribe}. These two variables do exactly the
1349 same as the @file{.newsrc} @samp{options -n} trick. Both are regexps,
1350 and if the new group matches the former, it will be unconditionally
1351 subscribed, and if it matches the latter, it will be ignored.
1353 @vindex gnus-auto-subscribed-groups
1354 Yet another variable that meddles here is
1355 @code{gnus-auto-subscribed-groups}. It works exactly like
1356 @code{gnus-options-subscribe}, and is therefore really superfluous,
1357 but I thought it would be nice to have two of these. This variable is
1358 more meant for setting some ground rules, while the other variable is
1359 used more for user fiddling. By default this variable makes all new
1360 groups that come from mail back ends (@code{nnml}, @code{nnbabyl},
1361 @code{nnfolder}, @code{nnmbox}, @code{nnmh}, and @code{nnmaildir})
1362 subscribed. If you don't like that, just set this variable to
1365 New groups that match this regexp are subscribed using
1366 @code{gnus-subscribe-options-newsgroup-method}.
1369 @node Changing Servers
1370 @section Changing Servers
1371 @cindex changing servers
1373 Sometimes it is necessary to move from one @acronym{NNTP} server to another.
1374 This happens very rarely, but perhaps you change jobs, or one server is
1375 very flaky and you want to use another.
1377 Changing the server is pretty easy, right? You just change
1378 @code{gnus-select-method} to point to the new server?
1382 Article numbers are not (in any way) kept synchronized between different
1383 @acronym{NNTP} servers, and the only way Gnus keeps track of what articles
1384 you have read is by keeping track of article numbers. So when you
1385 change @code{gnus-select-method}, your @file{.newsrc} file becomes
1388 Gnus provides a few functions to attempt to translate a @file{.newsrc}
1389 file from one server to another. They all have one thing in
1390 common---they take a looong time to run. You don't want to use these
1391 functions more than absolutely necessary.
1393 @kindex M-x gnus-change-server
1394 @findex gnus-change-server
1395 If you have access to both servers, Gnus can request the headers for all
1396 the articles you have read and compare @code{Message-ID}s and map the
1397 article numbers of the read articles and article marks. The @kbd{M-x
1398 gnus-change-server} command will do this for all your native groups. It
1399 will prompt for the method you want to move to.
1401 @kindex M-x gnus-group-move-group-to-server
1402 @findex gnus-group-move-group-to-server
1403 You can also move individual groups with the @kbd{M-x
1404 gnus-group-move-group-to-server} command. This is useful if you want to
1405 move a (foreign) group from one server to another.
1407 @kindex M-x gnus-group-clear-data-on-native-groups
1408 @findex gnus-group-clear-data-on-native-groups
1409 If you don't have access to both the old and new server, all your marks
1410 and read ranges have become worthless. You can use the @kbd{M-x
1411 gnus-group-clear-data-on-native-groups} command to clear out all data
1412 that you have on your native groups. Use with caution.
1414 @kindex M-x gnus-group-clear-data
1415 @findex gnus-group-clear-data
1416 Clear the data from the current group only---nix out marks and the
1417 list of read articles (@code{gnus-group-clear-data}).
1419 After changing servers, you @strong{must} move the cache hierarchy away,
1420 since the cached articles will have wrong article numbers, which will
1421 affect which articles Gnus thinks are read.
1422 @code{gnus-group-clear-data-on-native-groups} will ask you if you want
1423 to have it done automatically; for @code{gnus-group-clear-data}, you
1424 can use @kbd{M-x gnus-cache-move-cache} (but beware, it will move the
1425 cache for all groups).
1429 @section Startup Files
1430 @cindex startup files
1435 Most common Unix news readers use a shared startup file called
1436 @file{.newsrc}. This file contains all the information about what
1437 groups are subscribed, and which articles in these groups have been
1440 Things got a bit more complicated with @sc{gnus}. In addition to
1441 keeping the @file{.newsrc} file updated, it also used a file called
1442 @file{.newsrc.el} for storing all the information that didn't fit into
1443 the @file{.newsrc} file. (Actually, it also duplicated everything in
1444 the @file{.newsrc} file.) @sc{gnus} would read whichever one of these
1445 files was the most recently saved, which enabled people to swap between
1446 @sc{gnus} and other newsreaders.
1448 That was kinda silly, so Gnus went one better: In addition to the
1449 @file{.newsrc} and @file{.newsrc.el} files, Gnus also has a file called
1450 @file{.newsrc.eld}. It will read whichever of these files that are most
1451 recent, but it will never write a @file{.newsrc.el} file. You should
1452 never delete the @file{.newsrc.eld} file---it contains much information
1453 not stored in the @file{.newsrc} file.
1455 @vindex gnus-save-newsrc-file
1456 @vindex gnus-read-newsrc-file
1457 You can turn off writing the @file{.newsrc} file by setting
1458 @code{gnus-save-newsrc-file} to @code{nil}, which means you can delete
1459 the file and save some space, as well as exiting from Gnus faster.
1460 However, this will make it impossible to use other newsreaders than
1461 Gnus. But hey, who would want to, right? Similarly, setting
1462 @code{gnus-read-newsrc-file} to @code{nil} makes Gnus ignore the
1463 @file{.newsrc} file and any @file{.newsrc-SERVER} files, which can be
1464 convenient if you use a different news reader occasionally, and you
1465 want to read a different subset of the available groups with that
1468 @vindex gnus-save-killed-list
1469 If @code{gnus-save-killed-list} (default @code{t}) is @code{nil}, Gnus
1470 will not save the list of killed groups to the startup file. This will
1471 save both time (when starting and quitting) and space (on disk). It
1472 will also mean that Gnus has no record of what groups are new or old,
1473 so the automatic new groups subscription methods become meaningless.
1474 You should always set @code{gnus-check-new-newsgroups} to @code{nil} or
1475 @code{ask-server} if you set this variable to @code{nil} (@pxref{New
1476 Groups}). This variable can also be a regular expression. If that's
1477 the case, remove all groups that do not match this regexp before
1478 saving. This can be useful in certain obscure situations that involve
1479 several servers where not all servers support @code{ask-server}.
1481 @vindex gnus-startup-file
1482 @vindex gnus-backup-startup-file
1483 @vindex version-control
1484 The @code{gnus-startup-file} variable says where the startup files are.
1485 The default value is @file{~/.newsrc}, with the Gnus (El Dingo) startup
1486 file being whatever that one is, with a @samp{.eld} appended.
1487 If you want version control for this file, set
1488 @code{gnus-backup-startup-file}. It respects the same values as the
1489 @code{version-control} variable.
1491 @vindex gnus-save-newsrc-hook
1492 @vindex gnus-save-quick-newsrc-hook
1493 @vindex gnus-save-standard-newsrc-hook
1494 @code{gnus-save-newsrc-hook} is called before saving any of the newsrc
1495 files, while @code{gnus-save-quick-newsrc-hook} is called just before
1496 saving the @file{.newsrc.eld} file, and
1497 @code{gnus-save-standard-newsrc-hook} is called just before saving the
1498 @file{.newsrc} file. The latter two are commonly used to turn version
1499 control on or off. Version control is on by default when saving the
1500 startup files. If you want to turn backup creation off, say something like:
1503 (defun turn-off-backup ()
1504 (set (make-local-variable 'backup-inhibited) t))
1506 (add-hook 'gnus-save-quick-newsrc-hook 'turn-off-backup)
1507 (add-hook 'gnus-save-standard-newsrc-hook 'turn-off-backup)
1510 @vindex gnus-init-file
1511 @vindex gnus-site-init-file
1512 When Gnus starts, it will read the @code{gnus-site-init-file}
1513 (@file{.../site-lisp/gnus-init} by default) and @code{gnus-init-file}
1514 (@file{~/.gnus} by default) files. These are normal Emacs Lisp files
1515 and can be used to avoid cluttering your @file{~/.emacs} and
1516 @file{site-init} files with Gnus stuff. Gnus will also check for files
1517 with the same names as these, but with @file{.elc} and @file{.el}
1518 suffixes. In other words, if you have set @code{gnus-init-file} to
1519 @file{~/.gnus}, it will look for @file{~/.gnus.elc}, @file{~/.gnus.el},
1520 and finally @file{~/.gnus} (in this order). If Emacs was invoked with
1521 the @option{-q} or @option{--no-init-file} options (@pxref{Initial
1522 Options, ,Initial Options, emacs, The Emacs Manual}), Gnus doesn't read
1523 @code{gnus-init-file}.
1528 @cindex dribble file
1531 Whenever you do something that changes the Gnus data (reading articles,
1532 catching up, killing/subscribing groups), the change is added to a
1533 special @dfn{dribble buffer}. This buffer is auto-saved the normal
1534 Emacs way. If your Emacs should crash before you have saved the
1535 @file{.newsrc} files, all changes you have made can be recovered from
1538 If Gnus detects this file at startup, it will ask the user whether to
1539 read it. The auto save file is deleted whenever the real startup file is
1542 @vindex gnus-use-dribble-file
1543 If @code{gnus-use-dribble-file} is @code{nil}, Gnus won't create and
1544 maintain a dribble buffer. The default is @code{t}.
1546 @vindex gnus-dribble-directory
1547 Gnus will put the dribble file(s) in @code{gnus-dribble-directory}. If
1548 this variable is @code{nil}, which it is by default, Gnus will dribble
1549 into the directory where the @file{.newsrc} file is located. (This is
1550 normally the user's home directory.) The dribble file will get the same
1551 file permissions as the @file{.newsrc} file.
1553 @vindex gnus-always-read-dribble-file
1554 If @code{gnus-always-read-dribble-file} is non-@code{nil}, Gnus will
1555 read the dribble file on startup without querying the user.
1558 @node The Active File
1559 @section The Active File
1561 @cindex ignored groups
1563 When Gnus starts, or indeed whenever it tries to determine whether new
1564 articles have arrived, it reads the active file. This is a very large
1565 file that lists all the active groups and articles on the server.
1567 @vindex gnus-ignored-newsgroups
1568 Before examining the active file, Gnus deletes all lines that match the
1569 regexp @code{gnus-ignored-newsgroups}. This is done primarily to reject
1570 any groups with bogus names, but you can use this variable to make Gnus
1571 ignore hierarchies you aren't ever interested in. However, this is not
1572 recommended. In fact, it's highly discouraged. Instead, @pxref{New
1573 Groups} for an overview of other variables that can be used instead.
1576 @c @code{nil} by default, and will slow down active file handling somewhat
1577 @c if you set it to anything else.
1579 @vindex gnus-read-active-file
1581 The active file can be rather Huge, so if you have a slow network, you
1582 can set @code{gnus-read-active-file} to @code{nil} to prevent Gnus from
1583 reading the active file. This variable is @code{some} by default.
1585 Gnus will try to make do by getting information just on the groups that
1586 you actually subscribe to.
1588 Note that if you subscribe to lots and lots of groups, setting this
1589 variable to @code{nil} will probably make Gnus slower, not faster. At
1590 present, having this variable @code{nil} will slow Gnus down
1591 considerably, unless you read news over a 2400 baud modem.
1593 This variable can also have the value @code{some}. Gnus will then
1594 attempt to read active info only on the subscribed groups. On some
1595 servers this is quite fast (on sparkling, brand new INN servers that
1596 support the @code{LIST ACTIVE group} command), on others this isn't fast
1597 at all. In any case, @code{some} should be faster than @code{nil}, and
1598 is certainly faster than @code{t} over slow lines.
1600 Some news servers (old versions of Leafnode and old versions of INN, for
1601 instance) do not support the @code{LIST ACTIVE group}. For these
1602 servers, @code{nil} is probably the most efficient value for this
1605 If this variable is @code{nil}, Gnus will ask for group info in total
1606 lock-step, which isn't very fast. If it is @code{some} and you use an
1607 @acronym{NNTP} server, Gnus will pump out commands as fast as it can, and
1608 read all the replies in one swoop. This will normally result in better
1609 performance, but if the server does not support the aforementioned
1610 @code{LIST ACTIVE group} command, this isn't very nice to the server.
1612 If you think that starting up Gnus takes too long, try all the three
1613 different values for this variable and see what works best for you.
1615 In any case, if you use @code{some} or @code{nil}, you should definitely
1616 kill all groups that you aren't interested in to speed things up.
1618 Note that this variable also affects active file retrieval from
1619 secondary select methods.
1622 @node Startup Variables
1623 @section Startup Variables
1627 @item gnus-load-hook
1628 @vindex gnus-load-hook
1629 A hook run while Gnus is being loaded. Note that this hook will
1630 normally be run just once in each Emacs session, no matter how many
1631 times you start Gnus.
1633 @item gnus-before-startup-hook
1634 @vindex gnus-before-startup-hook
1635 A hook called as the first thing when Gnus is started.
1637 @item gnus-startup-hook
1638 @vindex gnus-startup-hook
1639 A hook run as the very last thing after starting up Gnus
1641 @item gnus-started-hook
1642 @vindex gnus-started-hook
1643 A hook that is run as the very last thing after starting up Gnus
1646 @item gnus-setup-news-hook
1647 @vindex gnus-setup-news-hook
1648 A hook that is run after reading the @file{.newsrc} file(s), but before
1649 generating the group buffer.
1651 @item gnus-check-bogus-newsgroups
1652 @vindex gnus-check-bogus-newsgroups
1653 If non-@code{nil}, Gnus will check for and delete all bogus groups at
1654 startup. A @dfn{bogus group} is a group that you have in your
1655 @file{.newsrc} file, but doesn't exist on the news server. Checking for
1656 bogus groups can take quite a while, so to save time and resources it's
1657 best to leave this option off, and do the checking for bogus groups once
1658 in a while from the group buffer instead (@pxref{Group Maintenance}).
1660 @item gnus-inhibit-startup-message
1661 @vindex gnus-inhibit-startup-message
1662 If non-@code{nil}, the startup message won't be displayed. That way,
1663 your boss might not notice as easily that you are reading news instead
1664 of doing your job. Note that this variable is used before
1665 @file{~/.gnus.el} is loaded, so it should be set in @file{.emacs} instead.
1667 @item gnus-no-groups-message
1668 @vindex gnus-no-groups-message
1669 Message displayed by Gnus when no groups are available.
1671 @item gnus-play-startup-jingle
1672 @vindex gnus-play-startup-jingle
1673 If non-@code{nil}, play the Gnus jingle at startup.
1675 @item gnus-startup-jingle
1676 @vindex gnus-startup-jingle
1677 Jingle to be played if the above variable is non-@code{nil}. The
1678 default is @samp{Tuxedomoon.Jingle4.au}.
1684 @chapter Group Buffer
1685 @cindex group buffer
1687 @c Alex Schroeder suggests to rearrange this as follows:
1689 @c <kensanata> ok, just save it for reference. I'll go to bed in a minute.
1690 @c 1. Selecting a Group, 2. (new) Finding a Group, 3. Group Levels,
1691 @c 4. Subscription Commands, 5. Group Maneuvering, 6. Group Data,
1692 @c 7. Group Score, 8. Group Buffer Format
1693 @c <kensanata> Group Levels should have more information on levels 5 to 9. I
1694 @c suggest to split the 4th paragraph ("Gnus considers groups...") as follows:
1695 @c <kensanata> First, "Gnus considers groups... (default 9)."
1696 @c <kensanata> New, a table summarizing what levels 1 to 9 mean.
1697 @c <kensanata> Third, "Gnus treats subscribed ... reasons of efficiency"
1698 @c <kensanata> Then expand the next paragraph or add some more to it.
1699 @c This short one sentence explains levels 1 and 2, therefore I understand
1700 @c that I should keep important news at 3 and boring news at 4.
1701 @c Say so! Then go on to explain why I should bother with levels 6 to 9.
1702 @c Maybe keep those that you don't want to read temporarily at 6,
1703 @c those that you never want to read at 8, those that offend your
1704 @c human rights at 9...
1707 The @dfn{group buffer} lists all (or parts) of the available groups. It
1708 is the first buffer shown when Gnus starts, and will never be killed as
1709 long as Gnus is active.
1713 \gnusfigure{The Group Buffer}{320}{
1714 \put(75,50){\epsfig{figure=ps/group,height=9cm}}
1715 \put(120,37){\makebox(0,0)[t]{Buffer name}}
1716 \put(120,38){\vector(1,2){10}}
1717 \put(40,60){\makebox(0,0)[r]{Mode line}}
1718 \put(40,58){\vector(1,0){30}}
1719 \put(200,28){\makebox(0,0)[t]{Native select method}}
1720 \put(200,26){\vector(-1,2){15}}
1726 * Group Buffer Format:: Information listed and how you can change it.
1727 * Group Maneuvering:: Commands for moving in the group buffer.
1728 * Selecting a Group:: Actually reading news.
1729 * Subscription Commands:: Unsubscribing, killing, subscribing.
1730 * Group Data:: Changing the info for a group.
1731 * Group Levels:: Levels? What are those, then?
1732 * Group Score:: A mechanism for finding out what groups you like.
1733 * Marking Groups:: You can mark groups for later processing.
1734 * Foreign Groups:: Creating and editing groups.
1735 * Group Parameters:: Each group may have different parameters set.
1736 * Listing Groups:: Gnus can list various subsets of the groups.
1737 * Sorting Groups:: Re-arrange the group order.
1738 * Group Maintenance:: Maintaining a tidy @file{.newsrc} file.
1739 * Browse Foreign Server:: You can browse a server. See what it has to offer.
1740 * Exiting Gnus:: Stop reading news and get some work done.
1741 * Group Topics:: A folding group mode divided into topics.
1742 * Non-ASCII Group Names:: Accessing groups of non-English names.
1743 * Searching:: Mail search engines.
1744 * Misc Group Stuff:: Other stuff that you can to do.
1748 @node Group Buffer Format
1749 @section Group Buffer Format
1752 * Group Line Specification:: Deciding how the group buffer is to look.
1753 * Group Mode Line Specification:: The group buffer mode line.
1754 * Group Highlighting:: Having nice colors in the group buffer.
1757 You can customize the Group Mode tool bar, see @kbd{M-x
1758 customize-apropos RET gnus-group-tool-bar}. This feature is only
1761 The tool bar icons are now (de)activated correctly depending on the
1762 cursor position. Therefore, moving around in the Group Buffer is
1763 slower. You can disable this via the variable
1764 @code{gnus-group-update-tool-bar}. Its default value depends on your
1767 @node Group Line Specification
1768 @subsection Group Line Specification
1769 @cindex group buffer format
1771 The default format of the group buffer is nice and dull, but you can
1772 make it as exciting and ugly as you feel like.
1774 Here's a couple of example group lines:
1777 25: news.announce.newusers
1778 * 0: alt.fan.andrea-dworkin
1783 You can see that there are 25 unread articles in
1784 @samp{news.announce.newusers}. There are no unread articles, but some
1785 ticked articles, in @samp{alt.fan.andrea-dworkin} (see that little
1786 asterisk at the beginning of the line?).
1788 @vindex gnus-group-line-format
1789 You can change that format to whatever you want by fiddling with the
1790 @code{gnus-group-line-format} variable. This variable works along the
1791 lines of a @code{format} specification, which is pretty much the same as
1792 a @code{printf} specifications, for those of you who use (feh!) C.
1793 @xref{Formatting Variables}.
1795 @samp{%M%S%5y:%B%(%g%)\n} is the value that produced those lines above.
1797 There should always be a colon on the line; the cursor always moves to
1798 the colon after performing an operation. @xref{Positioning
1799 Point}. Nothing else is required---not even the group name. All
1800 displayed text is just window dressing, and is never examined by Gnus.
1801 Gnus stores all real information it needs using text properties.
1803 (Note that if you make a really strange, wonderful, spreadsheet-like
1804 layout, everybody will believe you are hard at work with the accounting
1805 instead of wasting time reading news.)
1807 Here's a list of all available format characters:
1812 An asterisk if the group only has marked articles.
1815 Whether the group is subscribed.
1818 Level of subscribedness.
1821 Number of unread articles.
1824 Number of dormant articles.
1827 Number of ticked articles.
1830 Number of read articles.
1833 Number of unseen articles.
1836 Estimated total number of articles. (This is really @var{max-number}
1837 minus @var{min-number} plus 1.)
1839 Gnus uses this estimation because the @acronym{NNTP} protocol provides
1840 efficient access to @var{max-number} and @var{min-number} but getting
1841 the true unread message count is not possible efficiently. For
1842 hysterical raisins, even the mail back ends, where the true number of
1843 unread messages might be available efficiently, use the same limited
1844 interface. To remove this restriction from Gnus means that the back
1845 end interface has to be changed, which is not an easy job.
1847 The nnml backend (@pxref{Mail Spool}) has a feature called ``group
1848 compaction'' which circumvents this deficiency: the idea is to
1849 renumber all articles from 1, removing all gaps between numbers, hence
1850 getting a correct total count. Other backends may support this in the
1851 future. In order to keep your total article count relatively up to
1852 date, you might want to compact your groups (or even directly your
1853 server) from time to time. @xref{Misc Group Stuff}, @xref{Server Commands}.
1856 Number of unread, unticked, non-dormant articles.
1859 Number of ticked and dormant articles.
1868 Group comment (@pxref{Group Parameters}) or group name if there is no
1869 comment element in the group parameters.
1872 Newsgroup description. You need to read the group descriptions
1873 before these will appear, and to do that, you either have to set
1874 @code{gnus-read-active-file} or use the group buffer @kbd{M-d}
1878 @samp{m} if moderated.
1881 @samp{(m)} if moderated.
1887 If the summary buffer for the group is open or not.
1893 A string that looks like @samp{<%s:%n>} if a foreign select method is
1897 Indentation based on the level of the topic (@pxref{Group Topics}).
1900 @vindex gnus-group-uncollapsed-levels
1901 Short (collapsed) group name. The @code{gnus-group-uncollapsed-levels}
1902 variable says how many levels to leave at the end of the group name.
1903 The default is 1---this will mean that group names like
1904 @samp{gnu.emacs.gnus} will be shortened to @samp{g.e.gnus}.
1907 @vindex gnus-new-mail-mark
1909 @samp{%} (@code{gnus-new-mail-mark}) if there has arrived new mail to
1913 @samp{#} (@code{gnus-process-mark}) if the group is process marked.
1916 A string that says when you last read the group (@pxref{Group
1920 The disk space used by the articles fetched by both the cache and
1921 agent. The value is automatically scaled to bytes(B), kilobytes(K),
1922 megabytes(M), or gigabytes(G) to minimize the column width. A format
1923 of %7F is sufficient for a fixed-width column.
1926 User defined specifier. The next character in the format string should
1927 be a letter. Gnus will call the function
1928 @code{gnus-user-format-function-}@samp{X}, where @samp{X} is the letter
1929 following @samp{%u}. The function will be passed a single dummy
1930 parameter as argument. The function should return a string, which will
1931 be inserted into the buffer just like information from any other
1936 All the ``number-of'' specs will be filled with an asterisk (@samp{*})
1937 if no info is available---for instance, if it is a non-activated foreign
1938 group, or a bogus native group.
1941 @node Group Mode Line Specification
1942 @subsection Group Mode Line Specification
1943 @cindex group mode line
1945 @vindex gnus-group-mode-line-format
1946 The mode line can be changed by setting
1947 @code{gnus-group-mode-line-format} (@pxref{Mode Line Formatting}). It
1948 doesn't understand that many format specifiers:
1952 The native news server.
1954 The native select method.
1958 @node Group Highlighting
1959 @subsection Group Highlighting
1960 @cindex highlighting
1961 @cindex group highlighting
1963 @vindex gnus-group-highlight
1964 Highlighting in the group buffer is controlled by the
1965 @code{gnus-group-highlight} variable. This is an alist with elements
1966 that look like @code{(@var{form} . @var{face})}. If @var{form} evaluates to
1967 something non-@code{nil}, the @var{face} will be used on the line.
1969 Here's an example value for this variable that might look nice if the
1973 (cond (window-system
1974 (setq custom-background-mode 'light)
1975 (defface my-group-face-1
1976 '((t (:foreground "Red" :bold t))) "First group face")
1977 (defface my-group-face-2
1978 '((t (:foreground "DarkSeaGreen4" :bold t)))
1979 "Second group face")
1980 (defface my-group-face-3
1981 '((t (:foreground "Green4" :bold t))) "Third group face")
1982 (defface my-group-face-4
1983 '((t (:foreground "SteelBlue" :bold t))) "Fourth group face")
1984 (defface my-group-face-5
1985 '((t (:foreground "Blue" :bold t))) "Fifth group face")))
1987 (setq gnus-group-highlight
1988 '(((> unread 200) . my-group-face-1)
1989 ((and (< level 3) (zerop unread)) . my-group-face-2)
1990 ((< level 3) . my-group-face-3)
1991 ((zerop unread) . my-group-face-4)
1992 (t . my-group-face-5)))
1995 Also @pxref{Faces and Fonts}.
1997 Variables that are dynamically bound when the forms are evaluated
2004 The number of unread articles in the group.
2008 Whether the group is a mail group.
2010 The level of the group.
2012 The score of the group.
2014 The number of ticked articles in the group.
2016 The total number of articles in the group. Or rather,
2017 @var{max-number} minus @var{min-number} plus one.
2019 When using the topic minor mode, this variable is bound to the current
2020 topic being inserted.
2023 When the forms are @code{eval}ed, point is at the beginning of the line
2024 of the group in question, so you can use many of the normal Gnus
2025 functions for snarfing info on the group.
2027 @vindex gnus-group-update-hook
2028 @findex gnus-group-highlight-line
2029 @code{gnus-group-update-hook} is called when a group line is changed.
2030 It will not be called when @code{gnus-visual} is @code{nil}. This hook
2031 calls @code{gnus-group-highlight-line} by default.
2034 @node Group Maneuvering
2035 @section Group Maneuvering
2036 @cindex group movement
2038 All movement commands understand the numeric prefix and will behave as
2039 expected, hopefully.
2045 @findex gnus-group-next-unread-group
2046 Go to the next group that has unread articles
2047 (@code{gnus-group-next-unread-group}).
2053 @findex gnus-group-prev-unread-group
2054 Go to the previous group that has unread articles
2055 (@code{gnus-group-prev-unread-group}).
2059 @findex gnus-group-next-group
2060 Go to the next group (@code{gnus-group-next-group}).
2064 @findex gnus-group-prev-group
2065 Go to the previous group (@code{gnus-group-prev-group}).
2069 @findex gnus-group-next-unread-group-same-level
2070 Go to the next unread group on the same (or lower) level
2071 (@code{gnus-group-next-unread-group-same-level}).
2075 @findex gnus-group-prev-unread-group-same-level
2076 Go to the previous unread group on the same (or lower) level
2077 (@code{gnus-group-prev-unread-group-same-level}).
2080 Three commands for jumping to groups:
2086 @findex gnus-group-jump-to-group
2087 Jump to a group (and make it visible if it isn't already)
2088 (@code{gnus-group-jump-to-group}). Killed groups can be jumped to, just
2093 @findex gnus-group-best-unread-group
2094 Jump to the unread group with the lowest level
2095 (@code{gnus-group-best-unread-group}).
2099 @findex gnus-group-first-unread-group
2100 Jump to the first group with unread articles
2101 (@code{gnus-group-first-unread-group}).
2104 @vindex gnus-group-goto-unread
2105 If @code{gnus-group-goto-unread} is @code{nil}, all the movement
2106 commands will move to the next group, not the next unread group. Even
2107 the commands that say they move to the next unread group. The default
2110 @vindex gnus-summary-next-group-on-exit
2111 If @code{gnus-summary-next-group-on-exit} is @code{t}, when a summary is
2112 exited, the point in the group buffer is moved to the next unread group.
2113 Otherwise, the point is set to the group just exited. The default is
2116 @node Selecting a Group
2117 @section Selecting a Group
2118 @cindex group selection
2123 @kindex SPACE (Group)
2124 @findex gnus-group-read-group
2125 Select the current group, switch to the summary buffer and display the
2126 first unread article (@code{gnus-group-read-group}). If there are no
2127 unread articles in the group, or if you give a non-numerical prefix to
2128 this command, Gnus will offer to fetch all the old articles in this
2129 group from the server. If you give a numerical prefix @var{n}, @var{n}
2130 determines the number of articles Gnus will fetch. If @var{n} is
2131 positive, Gnus fetches the @var{n} newest articles, if @var{n} is
2132 negative, Gnus fetches the @code{abs(@var{n})} oldest articles.
2134 Thus, @kbd{SPC} enters the group normally, @kbd{C-u SPC} offers old
2135 articles, @kbd{C-u 4 2 SPC} fetches the 42 newest articles, and @kbd{C-u
2136 - 4 2 SPC} fetches the 42 oldest ones.
2138 When you are in the group (in the Summary buffer), you can type
2139 @kbd{M-g} to fetch new articles, or @kbd{C-u M-g} to also show the old
2144 @findex gnus-group-select-group
2145 Select the current group and switch to the summary buffer
2146 (@code{gnus-group-select-group}). Takes the same arguments as
2147 @code{gnus-group-read-group}---the only difference is that this command
2148 does not display the first unread article automatically upon group
2152 @kindex M-RET (Group)
2153 @findex gnus-group-quick-select-group
2154 This does the same as the command above, but tries to do it with the
2155 minimum amount of fuzz (@code{gnus-group-quick-select-group}). No
2156 scoring/killing will be performed, there will be no highlights and no
2157 expunging. This might be useful if you're in a real hurry and have to
2158 enter some humongous group. If you give a 0 prefix to this command
2159 (i.e., @kbd{0 M-RET}), Gnus won't even generate the summary buffer,
2160 which is useful if you want to toggle threading before generating the
2161 summary buffer (@pxref{Summary Generation Commands}).
2164 @kindex M-SPACE (Group)
2165 @findex gnus-group-visible-select-group
2166 This is yet one more command that does the same as the @kbd{RET}
2167 command, but this one does it without expunging and hiding dormants
2168 (@code{gnus-group-visible-select-group}).
2171 @kindex C-M-RET (Group)
2172 @findex gnus-group-select-group-ephemerally
2173 Finally, this command selects the current group ephemerally without
2174 doing any processing of its contents
2175 (@code{gnus-group-select-group-ephemerally}). Even threading has been
2176 turned off. Everything you do in the group after selecting it in this
2177 manner will have no permanent effects.
2181 @vindex gnus-large-newsgroup
2182 The @code{gnus-large-newsgroup} variable says what Gnus should
2183 consider to be a big group. If it is @code{nil}, no groups are
2184 considered big. The default value is 200. If the group has more
2185 (unread and/or ticked) articles than this, Gnus will query the user
2186 before entering the group. The user can then specify how many
2187 articles should be fetched from the server. If the user specifies a
2188 negative number (@var{-n}), the @var{n} oldest articles will be
2189 fetched. If it is positive, the @var{n} articles that have arrived
2190 most recently will be fetched.
2192 @vindex gnus-large-ephemeral-newsgroup
2193 @code{gnus-large-ephemeral-newsgroup} is the same as
2194 @code{gnus-large-newsgroup}, but is only used for ephemeral
2197 @vindex gnus-newsgroup-maximum-articles
2198 In groups in some news servers, there might be a big gap between a few
2199 very old articles that will never be expired and the recent ones. In
2200 such a case, the server will return the data like @code{(1 . 30000000)}
2201 for the @code{LIST ACTIVE group} command, for example. Even if there
2202 are actually only the articles 1-10 and 29999900-30000000, Gnus doesn't
2203 know it at first and prepares for getting 30000000 articles. However,
2204 it will consume hundreds megabytes of memories and might make Emacs get
2205 stuck as the case may be. If you use such news servers, set the
2206 variable @code{gnus-newsgroup-maximum-articles} to a positive number.
2207 The value means that Gnus ignores articles other than this number of the
2208 latest ones in every group. For instance, the value 10000 makes Gnus
2209 get only the articles 29990001-30000000 (if the latest article number is
2210 30000000 in a group). Note that setting this variable to a number might
2211 prevent you from reading very old articles. The default value of the
2212 variable @code{gnus-newsgroup-maximum-articles} is @code{nil}, which
2213 means Gnus never ignores old articles.
2215 @vindex gnus-select-group-hook
2216 @vindex gnus-auto-select-first
2217 @vindex gnus-auto-select-subject
2218 If @code{gnus-auto-select-first} is non-@code{nil}, select an article
2219 automatically when entering a group with the @kbd{SPACE} command.
2220 Which article this is controlled by the
2221 @code{gnus-auto-select-subject} variable. Valid values for this
2227 Place point on the subject line of the first unread article.
2230 Place point on the subject line of the first article.
2233 Place point on the subject line of the first unseen article.
2235 @item unseen-or-unread
2236 Place point on the subject line of the first unseen article, and if
2237 there is no such article, place point on the subject line of the first
2241 Place point on the subject line of the highest-scored unread article.
2245 This variable can also be a function. In that case, that function
2246 will be called to place point on a subject line.
2248 If you want to prevent automatic selection in some group (say, in a
2249 binary group with Huge articles) you can set the
2250 @code{gnus-auto-select-first} variable to @code{nil} in
2251 @code{gnus-select-group-hook}, which is called when a group is
2255 @node Subscription Commands
2256 @section Subscription Commands
2257 @cindex subscription
2265 @findex gnus-group-unsubscribe-current-group
2266 @c @icon{gnus-group-unsubscribe}
2267 Toggle subscription to the current group
2268 (@code{gnus-group-unsubscribe-current-group}).
2274 @findex gnus-group-unsubscribe-group
2275 Prompt for a group to subscribe, and then subscribe it. If it was
2276 subscribed already, unsubscribe it instead
2277 (@code{gnus-group-unsubscribe-group}).
2283 @findex gnus-group-kill-group
2284 @c @icon{gnus-group-kill-group}
2285 Kill the current group (@code{gnus-group-kill-group}).
2291 @findex gnus-group-yank-group
2292 Yank the last killed group (@code{gnus-group-yank-group}).
2295 @kindex C-x C-t (Group)
2296 @findex gnus-group-transpose-groups
2297 Transpose two groups (@code{gnus-group-transpose-groups}). This isn't
2298 really a subscription command, but you can use it instead of a
2299 kill-and-yank sequence sometimes.
2305 @findex gnus-group-kill-region
2306 Kill all groups in the region (@code{gnus-group-kill-region}).
2310 @findex gnus-group-kill-all-zombies
2311 Kill all zombie groups (@code{gnus-group-kill-all-zombies}).
2314 @kindex S C-k (Group)
2315 @findex gnus-group-kill-level
2316 Kill all groups on a certain level (@code{gnus-group-kill-level}).
2317 These groups can't be yanked back after killing, so this command should
2318 be used with some caution. The only time where this command comes in
2319 really handy is when you have a @file{.newsrc} with lots of unsubscribed
2320 groups that you want to get rid off. @kbd{S C-k} on level 7 will
2321 kill off all unsubscribed groups that do not have message numbers in the
2322 @file{.newsrc} file.
2326 Also @pxref{Group Levels}.
2336 @findex gnus-group-catchup-current
2337 @vindex gnus-group-catchup-group-hook
2338 @c @icon{gnus-group-catchup-current}
2339 Mark all unticked articles in this group as read
2340 (@code{gnus-group-catchup-current}).
2341 @code{gnus-group-catchup-group-hook} is called when catching up a group from
2346 @findex gnus-group-catchup-current-all
2347 Mark all articles in this group, even the ticked ones, as read
2348 (@code{gnus-group-catchup-current-all}).
2352 @findex gnus-group-clear-data
2353 Clear the data from the current group---nix out marks and the list of
2354 read articles (@code{gnus-group-clear-data}).
2356 @item M-x gnus-group-clear-data-on-native-groups
2357 @kindex M-x gnus-group-clear-data-on-native-groups
2358 @findex gnus-group-clear-data-on-native-groups
2359 If you have switched from one @acronym{NNTP} server to another, all your marks
2360 and read ranges have become worthless. You can use this command to
2361 clear out all data that you have on your native groups. Use with
2368 @section Group Levels
2372 All groups have a level of @dfn{subscribedness}. For instance, if a
2373 group is on level 2, it is more subscribed than a group on level 5. You
2374 can ask Gnus to just list groups on a given level or lower
2375 (@pxref{Listing Groups}), or to just check for new articles in groups on
2376 a given level or lower (@pxref{Scanning New Messages}).
2378 Remember: The higher the level of the group, the less important it is.
2384 @findex gnus-group-set-current-level
2385 Set the level of the current group. If a numeric prefix is given, the
2386 next @var{n} groups will have their levels set. The user will be
2387 prompted for a level.
2390 @vindex gnus-level-killed
2391 @vindex gnus-level-zombie
2392 @vindex gnus-level-unsubscribed
2393 @vindex gnus-level-subscribed
2394 Gnus considers groups from levels 1 to
2395 @code{gnus-level-subscribed} (inclusive) (default 5) to be subscribed,
2396 @code{gnus-level-subscribed} (exclusive) and
2397 @code{gnus-level-unsubscribed} (inclusive) (default 7) to be
2398 unsubscribed, @code{gnus-level-zombie} to be zombies (walking dead)
2399 (default 8) and @code{gnus-level-killed} to be killed (completely dead)
2400 (default 9). Gnus treats subscribed and unsubscribed groups exactly the
2401 same, but zombie and killed groups have no information on what articles
2402 you have read, etc, stored. This distinction between dead and living
2403 groups isn't done because it is nice or clever, it is done purely for
2404 reasons of efficiency.
2406 It is recommended that you keep all your mail groups (if any) on quite
2407 low levels (e.g. 1 or 2).
2409 Maybe the following description of the default behavior of Gnus helps to
2410 understand what these levels are all about. By default, Gnus shows you
2411 subscribed nonempty groups, but by hitting @kbd{L} you can have it show
2412 empty subscribed groups and unsubscribed groups, too. Type @kbd{l} to
2413 go back to showing nonempty subscribed groups again. Thus, unsubscribed
2414 groups are hidden, in a way.
2416 Zombie and killed groups are similar to unsubscribed groups in that they
2417 are hidden by default. But they are different from subscribed and
2418 unsubscribed groups in that Gnus doesn't ask the news server for
2419 information (number of messages, number of unread messages) on zombie
2420 and killed groups. Normally, you use @kbd{C-k} to kill the groups you
2421 aren't interested in. If most groups are killed, Gnus is faster.
2423 Why does Gnus distinguish between zombie and killed groups? Well, when
2424 a new group arrives on the server, Gnus by default makes it a zombie
2425 group. This means that you are normally not bothered with new groups,
2426 but you can type @kbd{A z} to get a list of all new groups. Subscribe
2427 the ones you like and kill the ones you don't want. (@kbd{A k} shows a
2428 list of killed groups.)
2430 If you want to play with the level variables, you should show some care.
2431 Set them once, and don't touch them ever again. Better yet, don't touch
2432 them at all unless you know exactly what you're doing.
2434 @vindex gnus-level-default-unsubscribed
2435 @vindex gnus-level-default-subscribed
2436 Two closely related variables are @code{gnus-level-default-subscribed}
2437 (default 3) and @code{gnus-level-default-unsubscribed} (default 6),
2438 which are the levels that new groups will be put on if they are
2439 (un)subscribed. These two variables should, of course, be inside the
2440 relevant valid ranges.
2442 @vindex gnus-keep-same-level
2443 If @code{gnus-keep-same-level} is non-@code{nil}, some movement commands
2444 will only move to groups of the same level (or lower). In
2445 particular, going from the last article in one group to the next group
2446 will go to the next group of the same level (or lower). This might be
2447 handy if you want to read the most important groups before you read the
2450 If this variable is @code{best}, Gnus will make the next newsgroup the
2451 one with the best level.
2453 @vindex gnus-group-default-list-level
2454 All groups with a level less than or equal to
2455 @code{gnus-group-default-list-level} will be listed in the group buffer
2458 @vindex gnus-group-list-inactive-groups
2459 If @code{gnus-group-list-inactive-groups} is non-@code{nil}, non-active
2460 groups will be listed along with the unread groups. This variable is
2461 @code{t} by default. If it is @code{nil}, inactive groups won't be
2464 @vindex gnus-group-use-permanent-levels
2465 If @code{gnus-group-use-permanent-levels} is non-@code{nil}, once you
2466 give a level prefix to @kbd{g} or @kbd{l}, all subsequent commands will
2467 use this level as the ``work'' level.
2469 @vindex gnus-activate-level
2470 Gnus will normally just activate (i. e., query the server about) groups
2471 on level @code{gnus-activate-level} or less. If you don't want to
2472 activate unsubscribed groups, for instance, you might set this variable
2473 to 5. The default is 6.
2477 @section Group Score
2482 You would normally keep important groups on high levels, but that scheme
2483 is somewhat restrictive. Don't you wish you could have Gnus sort the
2484 group buffer according to how often you read groups, perhaps? Within
2487 This is what @dfn{group score} is for. You can have Gnus assign a score
2488 to each group through the mechanism described below. You can then sort
2489 the group buffer based on this score. Alternatively, you can sort on
2490 score and then level. (Taken together, the level and the score is
2491 called the @dfn{rank} of the group. A group that is on level 4 and has
2492 a score of 1 has a higher rank than a group on level 5 that has a score
2493 of 300. (The level is the most significant part and the score is the
2494 least significant part.))
2496 @findex gnus-summary-bubble-group
2497 If you want groups you read often to get higher scores than groups you
2498 read seldom you can add the @code{gnus-summary-bubble-group} function to
2499 the @code{gnus-summary-exit-hook} hook. This will result (after
2500 sorting) in a bubbling sort of action. If you want to see that in
2501 action after each summary exit, you can add
2502 @code{gnus-group-sort-groups-by-rank} or
2503 @code{gnus-group-sort-groups-by-score} to the same hook, but that will
2504 slow things down somewhat.
2507 @node Marking Groups
2508 @section Marking Groups
2509 @cindex marking groups
2511 If you want to perform some command on several groups, and they appear
2512 subsequently in the group buffer, you would normally just give a
2513 numerical prefix to the command. Most group commands will then do your
2514 bidding on those groups.
2516 However, if the groups are not in sequential order, you can still
2517 perform a command on several groups. You simply mark the groups first
2518 with the process mark and then execute the command.
2526 @findex gnus-group-mark-group
2527 Set the mark on the current group (@code{gnus-group-mark-group}).
2533 @findex gnus-group-unmark-group
2534 Remove the mark from the current group
2535 (@code{gnus-group-unmark-group}).
2539 @findex gnus-group-unmark-all-groups
2540 Remove the mark from all groups (@code{gnus-group-unmark-all-groups}).
2544 @findex gnus-group-mark-region
2545 Mark all groups between point and mark (@code{gnus-group-mark-region}).
2549 @findex gnus-group-mark-buffer
2550 Mark all groups in the buffer (@code{gnus-group-mark-buffer}).
2554 @findex gnus-group-mark-regexp
2555 Mark all groups that match some regular expression
2556 (@code{gnus-group-mark-regexp}).
2559 Also @pxref{Process/Prefix}.
2561 @findex gnus-group-universal-argument
2562 If you want to execute some command on all groups that have been marked
2563 with the process mark, you can use the @kbd{M-&}
2564 (@code{gnus-group-universal-argument}) command. It will prompt you for
2565 the command to be executed.
2568 @node Foreign Groups
2569 @section Foreign Groups
2570 @cindex foreign groups
2572 Below are some group mode commands for making and editing general foreign
2573 groups, as well as commands to ease the creation of a few
2574 special-purpose groups. All these commands insert the newly created
2575 groups under point---@code{gnus-subscribe-newsgroup-method} is not
2578 Changes from the group editing commands are stored in
2579 @file{~/.newsrc.eld} (@code{gnus-startup-file}). An alternative is the
2580 variable @code{gnus-parameters}, @xref{Group Parameters}.
2586 @findex gnus-group-make-group
2587 @cindex making groups
2588 Make a new group (@code{gnus-group-make-group}). Gnus will prompt you
2589 for a name, a method and possibly an @dfn{address}. For an easier way
2590 to subscribe to @acronym{NNTP} groups (@pxref{Browse Foreign Server}).
2594 @findex gnus-group-read-ephemeral-group
2595 Make an ephemeral group (@code{gnus-group-read-ephemeral-group}). Gnus
2596 will prompt you for a name, a method and an @dfn{address}.
2600 @findex gnus-group-rename-group
2601 @cindex renaming groups
2602 Rename the current group to something else
2603 (@code{gnus-group-rename-group}). This is valid only on some
2604 groups---mail groups mostly. This command might very well be quite slow
2610 @findex gnus-group-customize
2611 Customize the group parameters (@code{gnus-group-customize}).
2615 @findex gnus-group-edit-group-method
2616 @cindex renaming groups
2617 Enter a buffer where you can edit the select method of the current
2618 group (@code{gnus-group-edit-group-method}).
2622 @findex gnus-group-edit-group-parameters
2623 Enter a buffer where you can edit the group parameters
2624 (@code{gnus-group-edit-group-parameters}).
2628 @findex gnus-group-edit-group
2629 Enter a buffer where you can edit the group info
2630 (@code{gnus-group-edit-group}).
2634 @findex gnus-group-make-directory-group
2636 Make a directory group (@pxref{Directory Groups}). You will be prompted
2637 for a directory name (@code{gnus-group-make-directory-group}).
2642 @findex gnus-group-make-help-group
2643 Make the Gnus help group (@code{gnus-group-make-help-group}).
2647 @cindex (ding) archive
2648 @cindex archive group
2649 @findex gnus-group-make-archive-group
2650 @vindex gnus-group-archive-directory
2651 @vindex gnus-group-recent-archive-directory
2652 Make a Gnus archive group (@code{gnus-group-make-archive-group}). By
2653 default a group pointing to the most recent articles will be created
2654 (@code{gnus-group-recent-archive-directory}), but given a prefix, a full
2655 group will be created from @code{gnus-group-archive-directory}.
2659 @findex gnus-group-make-kiboze-group
2661 Make a kiboze group. You will be prompted for a name, for a regexp to
2662 match groups to be ``included'' in the kiboze group, and a series of
2663 strings to match on headers (@code{gnus-group-make-kiboze-group}).
2664 @xref{Kibozed Groups}.
2668 @findex gnus-group-enter-directory
2670 Read an arbitrary directory as if it were a newsgroup with the
2671 @code{nneething} back end (@code{gnus-group-enter-directory}).
2672 @xref{Anything Groups}.
2676 @findex gnus-group-make-doc-group
2677 @cindex ClariNet Briefs
2679 Make a group based on some file or other
2680 (@code{gnus-group-make-doc-group}). If you give a prefix to this
2681 command, you will be prompted for a file name and a file type.
2682 Currently supported types are @code{mbox}, @code{babyl},
2683 @code{digest}, @code{news}, @code{rnews}, @code{mmdf}, @code{forward},
2684 @code{rfc934}, @code{rfc822-forward}, @code{mime-parts},
2685 @code{standard-digest}, @code{slack-digest}, @code{clari-briefs},
2686 @code{nsmail}, @code{outlook}, @code{oe-dbx}, and @code{mailman}. If
2687 you run this command without a prefix, Gnus will guess at the file
2688 type. @xref{Document Groups}.
2692 @vindex gnus-useful-groups
2693 @findex gnus-group-make-useful-group
2694 Create one of the groups mentioned in @code{gnus-useful-groups}
2695 (@code{gnus-group-make-useful-group}).
2699 @findex gnus-group-make-web-group
2703 Make an ephemeral group based on a web search
2704 (@code{gnus-group-make-web-group}). If you give a prefix to this
2705 command, make a solid group instead. You will be prompted for the
2706 search engine type and the search string. Valid search engine types
2707 include @code{google}, @code{dejanews}, and @code{gmane}.
2708 @xref{Web Searches}.
2710 If you use the @code{google} search engine, you can limit the search
2711 to a particular group by using a match string like
2712 @samp{shaving group:alt.sysadmin.recovery}.
2716 @findex gnus-group-make-rss-group
2717 Make a group based on an @acronym{RSS} feed
2718 (@code{gnus-group-make-rss-group}). You will be prompted for an URL.
2722 @kindex G DEL (Group)
2723 @findex gnus-group-delete-group
2724 This function will delete the current group
2725 (@code{gnus-group-delete-group}). If given a prefix, this function will
2726 actually delete all the articles in the group, and forcibly remove the
2727 group itself from the face of the Earth. Use a prefix only if you are
2728 absolutely sure of what you are doing. This command can't be used on
2729 read-only groups (like @code{nntp} groups), though.
2733 @findex gnus-group-make-empty-virtual
2734 Make a new, fresh, empty @code{nnvirtual} group
2735 (@code{gnus-group-make-empty-virtual}). @xref{Virtual Groups}.
2739 @findex gnus-group-add-to-virtual
2740 Add the current group to an @code{nnvirtual} group
2741 (@code{gnus-group-add-to-virtual}). Uses the process/prefix convention.
2744 @xref{Select Methods}, for more information on the various select
2747 @vindex gnus-activate-foreign-newsgroups
2748 If @code{gnus-activate-foreign-newsgroups} is a positive number,
2749 Gnus will check all foreign groups with this level or lower at startup.
2750 This might take quite a while, especially if you subscribe to lots of
2751 groups from different @acronym{NNTP} servers. Also @pxref{Group Levels};
2752 @code{gnus-activate-level} also affects activation of foreign
2756 The following commands create ephemeral groups. They can be called not
2757 only from the Group buffer, but in any Gnus buffer.
2760 @item gnus-read-ephemeral-gmane-group
2761 @findex gnus-read-ephemeral-gmane-group
2762 @vindex gnus-gmane-group-download-format
2763 Read an ephemeral group on Gmane.org. The articles are downloaded via
2764 HTTP using the URL specified by @code{gnus-gmane-group-download-format}.
2765 Gnus will prompt you for a group name, the start article number and an
2768 @item gnus-read-ephemeral-gmane-group-url
2769 @findex gnus-read-ephemeral-gmane-group-url
2770 This command is similar to @code{gnus-read-ephemeral-gmane-group}, but
2771 the group name and the article number and range are constructed from a
2772 given @acronym{URL}. Supported @acronym{URL} formats include e.g.
2773 @url{http://thread.gmane.org/gmane.foo.bar/12300/focus=12399},
2774 @url{http://thread.gmane.org/gmane.foo.bar/12345/},
2775 @url{http://article.gmane.org/gmane.foo.bar/12345/},
2776 @url{http://permalink.gmane.org/gmane.foo.bar/12345/}, and
2777 @url{http://news.gmane.org/group/gmane.foo.bar/thread=12345}.
2779 @item gnus-read-ephemeral-emacs-bug-group
2780 @findex gnus-read-ephemeral-emacs-bug-group
2781 Read an Emacs bug report in an ephemeral group. Gnus will prompt for a
2782 bug number. The default is the number at point. The @acronym{URL} is
2783 specified in @code{gnus-bug-group-download-format-alist}.
2785 @item gnus-read-ephemeral-debian-bug-group
2786 @findex gnus-read-ephemeral-debian-bug-group
2787 Read a Debian bug report in an ephemeral group. Analog to
2788 @code{gnus-read-ephemeral-emacs-bug-group}.
2791 Some of these command are also useful for article buttons, @xref{Article
2799 '("#\\([0-9]+\\)\\>" 1
2800 (string-match "\\<emacs\\>" (or gnus-newsgroup-name ""))
2801 gnus-read-ephemeral-emacs-bug-group 1))
2805 @node Group Parameters
2806 @section Group Parameters
2807 @cindex group parameters
2809 The group parameters store information local to a particular group.
2811 Use the @kbd{G p} or the @kbd{G c} command to edit group parameters of a
2812 group. (@kbd{G p} presents you with a Lisp-based interface, @kbd{G c}
2813 presents you with a Customize-like interface. The latter helps avoid
2814 silly Lisp errors.) You might also be interested in reading about topic
2815 parameters (@pxref{Topic Parameters}).
2816 Additionally, you can set group parameters via the
2817 @code{gnus-parameters} variable, see below.
2819 Here's an example group parameter list:
2822 ((to-address . "ding@@gnus.org")
2826 We see that each element consists of a ``dotted pair''---the thing before
2827 the dot is the key, while the thing after the dot is the value. All the
2828 parameters have this form @emph{except} local variable specs, which are
2829 not dotted pairs, but proper lists.
2831 Some parameters have correspondent customizable variables, each of which
2832 is an alist of regexps and values.
2834 The following group parameters can be used:
2839 Address used by when doing followups and new posts.
2842 (to-address . "some@@where.com")
2845 This is primarily useful in mail groups that represent closed mailing
2846 lists---mailing lists where it's expected that everybody that writes to
2847 the mailing list is subscribed to it. Since using this parameter
2848 ensures that the mail only goes to the mailing list itself, it means
2849 that members won't receive two copies of your followups.
2851 Using @code{to-address} will actually work whether the group is foreign
2852 or not. Let's say there's a group on the server that is called
2853 @samp{fa.4ad-l}. This is a real newsgroup, but the server has gotten
2854 the articles from a mail-to-news gateway. Posting directly to this
2855 group is therefore impossible---you have to send mail to the mailing
2856 list address instead.
2858 See also @code{gnus-parameter-to-address-alist}.
2862 Address used when doing @kbd{a} in that group.
2865 (to-list . "some@@where.com")
2868 It is totally ignored
2869 when doing a followup---except that if it is present in a news group,
2870 you'll get mail group semantics when doing @kbd{f}.
2872 If you do an @kbd{a} command in a mail group and you have neither a
2873 @code{to-list} group parameter nor a @code{to-address} group parameter,
2874 then a @code{to-list} group parameter will be added automatically upon
2875 sending the message if @code{gnus-add-to-list} is set to @code{t}.
2876 @vindex gnus-add-to-list
2878 @findex gnus-mailing-list-mode
2879 @cindex mail list groups
2880 If this variable is set, @code{gnus-mailing-list-mode} is turned on when
2881 entering summary buffer.
2883 See also @code{gnus-parameter-to-list-alist}.
2888 @cindex Mail-Followup-To
2889 @findex gnus-find-subscribed-addresses
2890 If this parameter is set to @code{t}, Gnus will consider the
2891 to-address and to-list parameters for this group as addresses of
2892 mailing lists you are subscribed to. Giving Gnus this information is
2893 (only) a first step in getting it to generate correct Mail-Followup-To
2894 headers for your posts to these lists. The second step is to put the
2895 following in your @file{.gnus.el}
2898 (setq message-subscribed-address-functions
2899 '(gnus-find-subscribed-addresses))
2902 @xref{Mailing Lists, ,Mailing Lists, message, The Message Manual}, for
2903 a complete treatment of available MFT support.
2907 If the group parameter list has the element @code{(visible . t)},
2908 that group will always be visible in the Group buffer, regardless
2909 of whether it has any unread articles.
2911 This parameter cannot be set via @code{gnus-parameters}. See
2912 @code{gnus-permanently-visible-groups} as an alternative.
2914 @item broken-reply-to
2915 @cindex broken-reply-to
2916 Elements like @code{(broken-reply-to . t)} signals that @code{Reply-To}
2917 headers in this group are to be ignored, and for the header to be hidden
2918 if @code{reply-to} is part of @code{gnus-boring-article-headers}. This
2919 can be useful if you're reading a mailing list group where the listserv
2920 has inserted @code{Reply-To} headers that point back to the listserv
2921 itself. That is broken behavior. So there!
2925 Elements like @code{(to-group . "some.group.name")} means that all
2926 posts in that group will be sent to @code{some.group.name}.
2930 If you have @code{(newsgroup . t)} in the group parameter list, Gnus
2931 will treat all responses as if they were responses to news articles.
2932 This can be useful if you have a mail group that's really a mirror of a
2937 If @code{(gcc-self . t)} is present in the group parameter list, newly
2938 composed messages will be @code{Gcc}'d to the current group. If
2939 @code{(gcc-self . none)} is present, no @code{Gcc:} header will be
2940 generated, if @code{(gcc-self . "string")} is present, this string will
2941 be inserted literally as a @code{gcc} header. This parameter takes
2942 precedence over any default @code{Gcc} rules as described later
2943 (@pxref{Archived Messages}).
2945 @strong{Caveat}: Adding @code{(gcc-self . t)} to the parameter list of
2946 @code{nntp} groups (or the like) isn't valid. An @code{nntp} server
2947 doesn't accept articles.
2951 @cindex expiring mail
2952 If the group parameter has an element that looks like @code{(auto-expire
2953 . t)}, all articles read will be marked as expirable. For an
2954 alternative approach, @pxref{Expiring Mail}.
2956 See also @code{gnus-auto-expirable-newsgroups}.
2959 @cindex total-expire
2960 @cindex expiring mail
2961 If the group parameter has an element that looks like
2962 @code{(total-expire . t)}, all read articles will be put through the
2963 expiry process, even if they are not marked as expirable. Use with
2964 caution. Unread, ticked and dormant articles are not eligible for
2967 See also @code{gnus-total-expirable-newsgroups}.
2971 @vindex nnmail-expiry-wait-function
2972 If the group parameter has an element that looks like
2973 @code{(expiry-wait . 10)}, this value will override any
2974 @code{nnmail-expiry-wait} and @code{nnmail-expiry-wait-function}
2975 (@pxref{Expiring Mail}) when expiring expirable messages. The value
2976 can either be a number of days (not necessarily an integer) or the
2977 symbols @code{never} or @code{immediate}.
2980 @cindex expiry-target
2981 Where expired messages end up. This parameter overrides
2982 @code{nnmail-expiry-target}.
2985 @cindex score file group parameter
2986 Elements that look like @code{(score-file . "file")} will make
2987 @file{file} into the current score file for the group in question. All
2988 interactive score entries will be put into this file.
2991 @cindex adapt file group parameter
2992 Elements that look like @code{(adapt-file . "file")} will make
2993 @file{file} into the current adaptive file for the group in question.
2994 All adaptive score entries will be put into this file.
2997 @cindex admin-address
2998 When unsubscribing from a mailing list you should never send the
2999 unsubscription notice to the mailing list itself. Instead, you'd send
3000 messages to the administrative address. This parameter allows you to
3001 put the admin address somewhere convenient.
3005 Elements that look like @code{(display . MODE)} say which articles to
3006 display on entering the group. Valid values are:
3010 Display all articles, both read and unread.
3013 Display the last @var{integer} articles in the group. This is the same as
3014 entering the group with @kbd{C-u @var{integer}}.
3017 Display the default visible articles, which normally includes unread and
3021 Display articles that satisfy a predicate.
3023 Here are some examples:
3027 Display only unread articles.
3030 Display everything except expirable articles.
3032 @item [and (not reply) (not expire)]
3033 Display everything except expirable and articles you've already
3037 The available operators are @code{not}, @code{and} and @code{or}.
3038 Predicates include @code{tick}, @code{unsend}, @code{undownload},
3039 @code{unread}, @code{dormant}, @code{expire}, @code{reply},
3040 @code{killed}, @code{bookmark}, @code{score}, @code{save},
3041 @code{cache}, @code{forward}, @code{unseen} and @code{recent}.
3045 The @code{display} parameter works by limiting the summary buffer to
3046 the subset specified. You can pop the limit by using the @kbd{/ w}
3047 command (@pxref{Limiting}).
3051 Elements that look like @code{(comment . "This is a comment")} are
3052 arbitrary comments on the group. You can display comments in the
3053 group line (@pxref{Group Line Specification}).
3057 Elements that look like @code{(charset . iso-8859-1)} will make
3058 @code{iso-8859-1} the default charset; that is, the charset that will be
3059 used for all articles that do not specify a charset.
3061 See also @code{gnus-group-charset-alist}.
3063 @item ignored-charsets
3064 @cindex ignored-charset
3065 Elements that look like @code{(ignored-charsets x-unknown iso-8859-1)}
3066 will make @code{iso-8859-1} and @code{x-unknown} ignored; that is, the
3067 default charset will be used for decoding articles.
3069 See also @code{gnus-group-ignored-charsets-alist}.
3072 @cindex posting-style
3073 You can store additional posting style information for this group
3074 here (@pxref{Posting Styles}). The format is that of an entry in the
3075 @code{gnus-posting-styles} alist, except that there's no regexp matching
3076 the group name (of course). Style elements in this group parameter will
3077 take precedence over the ones found in @code{gnus-posting-styles}.
3079 For instance, if you want a funky name and signature in this group only,
3080 instead of hacking @code{gnus-posting-styles}, you could put something
3081 like this in the group parameters:
3086 ("X-My-Header" "Funky Value")
3087 (signature "Funky Signature"))
3090 If you're using topics to organize your group buffer
3091 (@pxref{Group Topics}), note that posting styles can also be set in
3092 the topics parameters. Posting styles in topic parameters apply to all
3093 groups in this topic. More precisely, the posting-style settings for a
3094 group result from the hierarchical merging of all posting-style
3095 entries in the parameters of this group and all the topics it belongs
3101 If it is set, the value is used as the method for posting message
3102 instead of @code{gnus-post-method}.
3106 If it is set, and the setting of @code{mail-sources} includes a
3107 @code{group} mail source (@pxref{Mail Sources}), the value is a
3108 mail source for this group.
3112 An item like @code{(banner . @var{regexp})} causes any part of an article
3113 that matches the regular expression @var{regexp} to be stripped. Instead of
3114 @var{regexp}, you can also use the symbol @code{signature} which strips the
3115 last signature or any of the elements of the alist
3116 @code{gnus-article-banner-alist}.
3120 This parameter contains a Sieve test that should match incoming mail
3121 that should be placed in this group. From this group parameter, a
3122 Sieve @samp{IF} control structure is generated, having the test as the
3123 condition and @samp{fileinto "group.name";} as the body.
3125 For example, if the @samp{INBOX.list.sieve} group has the @code{(sieve
3126 address "sender" "sieve-admin@@extundo.com")} group parameter, when
3127 translating the group parameter into a Sieve script (@pxref{Sieve
3128 Commands}) the following Sieve code is generated:
3131 if address "sender" "sieve-admin@@extundo.com" @{
3132 fileinto "INBOX.list.sieve";
3136 To generate tests for multiple email-addresses use a group parameter
3137 like @code{(sieve address "sender" ("name@@one.org" else@@two.org"))}.
3138 When generating a sieve script (@pxref{Sieve Commands}) Sieve code
3139 like the following is generated:
3142 if address "sender" ["name@@one.org", "else@@two.org"] @{
3143 fileinto "INBOX.list.sieve";
3147 See @pxref{Sieve Commands} for commands and variables that might be of
3148 interest in relation to the sieve parameter.
3150 The Sieve language is described in RFC 3028. @xref{Top, Emacs Sieve,
3151 Top, sieve, Emacs Sieve}.
3153 @item (agent parameters)
3154 If the agent has been enabled, you can set any of the its parameters
3155 to control the behavior of the agent in individual groups. See Agent
3156 Parameters in @ref{Category Syntax}. Most users will choose to set
3157 agent parameters in either an agent category or group topic to
3158 minimize the configuration effort.
3160 @item (@var{variable} @var{form})
3161 You can use the group parameters to set variables local to the group you
3162 are entering. If you want to turn threading off in @samp{news.answers},
3163 you could put @code{(gnus-show-threads nil)} in the group parameters of
3164 that group. @code{gnus-show-threads} will be made into a local variable
3165 in the summary buffer you enter, and the form @code{nil} will be
3166 @code{eval}ed there.
3168 Note that this feature sets the variable locally to the summary buffer
3169 if and only if @var{variable} has been bound as a variable. Otherwise,
3170 only evaluating the form will take place. So, you may want to bind the
3171 variable in advance using @code{defvar} or other if the result of the
3172 form needs to be set to it.
3174 But some variables are evaluated in the article buffer, or in the
3175 message buffer (of a reply or followup or otherwise newly created
3176 message). As a workaround, it might help to add the variable in
3177 question to @code{gnus-newsgroup-variables}. @xref{Various Summary
3178 Stuff}. So if you want to set @code{message-from-style} via the group
3179 parameters, then you may need the following statement elsewhere in your
3180 @file{~/.gnus.el} file:
3183 (add-to-list 'gnus-newsgroup-variables 'message-from-style)
3186 @vindex gnus-list-identifiers
3187 A use for this feature is to remove a mailing list identifier tag in
3188 the subject fields of articles. E.g. if the news group
3191 nntp+news.gnus.org:gmane.text.docbook.apps
3194 has the tag @samp{DOC-BOOK-APPS:} in the subject of all articles, this
3195 tag can be removed from the article subjects in the summary buffer for
3196 the group by putting @code{(gnus-list-identifiers "DOCBOOK-APPS:")}
3197 into the group parameters for the group.
3199 This can also be used as a group-specific hook function. If you want to
3200 hear a beep when you enter a group, you could put something like
3201 @code{(dummy-variable (ding))} in the parameters of that group. If
3202 @code{dummy-variable} has been bound (see above), it will be set to the
3203 (meaningless) result of the @code{(ding)} form.
3205 Alternatively, since the VARIABLE becomes local to the group, this
3206 pattern can be used to temporarily change a hook. For example, if the
3207 following is added to a group parameter
3210 (gnus-summary-prepared-hook
3211 '(lambda nil (local-set-key "d" (local-key-binding "n"))))
3214 when the group is entered, the 'd' key will not mark the article as
3219 @vindex gnus-parameters
3220 Group parameters can be set via the @code{gnus-parameters} variable too.
3221 But some variables, such as @code{visible}, have no effect (For this
3222 case see @code{gnus-permanently-visible-groups} as an alternative.).
3226 (setq gnus-parameters
3228 (gnus-show-threads nil)
3229 (gnus-use-scoring nil)
3230 (gnus-summary-line-format
3231 "%U%R%z%I%(%[%d:%ub%-23,23f%]%) %s\n")
3235 ("^nnimap:\\(foo.bar\\)$"
3239 (gnus-use-scoring t))
3243 (broken-reply-to . t))))
3246 String value of parameters will be subjected to regexp substitution, as
3247 the @code{to-group} example shows.
3249 @vindex gnus-parameters-case-fold-search
3250 By default, whether comparing the group name and one of those regexps
3251 specified in @code{gnus-parameters} is done in a case-sensitive manner
3252 or a case-insensitive manner depends on the value of
3253 @code{case-fold-search} at the time when the comparison is done. The
3254 value of @code{case-fold-search} is typically @code{t}; it means, for
3255 example, the element @code{("INBOX\\.FOO" (total-expire . t))} might be
3256 applied to both the @samp{INBOX.FOO} group and the @samp{INBOX.foo}
3257 group. If you want to make those regexps always case-sensitive, set the
3258 value of the @code{gnus-parameters-case-fold-search} variable to
3259 @code{nil}. Otherwise, set it to @code{t} if you want to compare them
3260 always in a case-insensitive manner.
3262 You can define different sorting to different groups via
3263 @code{gnus-parameters}. Here is an example to sort an @acronym{NNTP}
3264 group by reverse date to see the latest news at the top and an
3265 @acronym{RSS} group by subject. In this example, the first group is the
3266 Debian daily news group @code{gmane.linux.debian.user.news} from
3267 news.gmane.org. The @acronym{RSS} group corresponds to the Debian
3268 weekly news RSS feed
3269 @url{http://packages.debian.org/unstable/newpkg_main.en.rdf},
3275 '(("nntp.*gmane\\.debian\\.user\\.news"
3276 (gnus-show-threads nil)
3277 (gnus-article-sort-functions '((not gnus-article-sort-by-date)))
3278 (gnus-use-adaptive-scoring nil)
3279 (gnus-use-scoring nil))
3281 (gnus-show-threads nil)
3282 (gnus-article-sort-functions 'gnus-article-sort-by-subject)
3283 (gnus-use-adaptive-scoring nil)
3284 (gnus-use-scoring t)
3285 (gnus-score-find-score-files-function 'gnus-score-find-single)
3286 (gnus-summary-line-format "%U%R%z%d %I%(%[ %s %]%)\n"))))
3290 @node Listing Groups
3291 @section Listing Groups
3292 @cindex group listing
3294 These commands all list various slices of the groups available.
3302 @findex gnus-group-list-groups
3303 List all groups that have unread articles
3304 (@code{gnus-group-list-groups}). If the numeric prefix is used, this
3305 command will list only groups of level ARG and lower. By default, it
3306 only lists groups of level five (i.e.,
3307 @code{gnus-group-default-list-level}) or lower (i.e., just subscribed
3314 @findex gnus-group-list-all-groups
3315 List all groups, whether they have unread articles or not
3316 (@code{gnus-group-list-all-groups}). If the numeric prefix is used,
3317 this command will list only groups of level ARG and lower. By default,
3318 it lists groups of level seven or lower (i.e., just subscribed and
3319 unsubscribed groups).
3323 @findex gnus-group-list-level
3324 List all unread groups on a specific level
3325 (@code{gnus-group-list-level}). If given a prefix, also list the groups
3326 with no unread articles.
3330 @findex gnus-group-list-killed
3331 List all killed groups (@code{gnus-group-list-killed}). If given a
3332 prefix argument, really list all groups that are available, but aren't
3333 currently (un)subscribed. This could entail reading the active file
3338 @findex gnus-group-list-zombies
3339 List all zombie groups (@code{gnus-group-list-zombies}).
3343 @findex gnus-group-list-matching
3344 List all unread, subscribed groups with names that match a regexp
3345 (@code{gnus-group-list-matching}).
3349 @findex gnus-group-list-all-matching
3350 List groups that match a regexp (@code{gnus-group-list-all-matching}).
3354 @findex gnus-group-list-active
3355 List absolutely all groups in the active file(s) of the
3356 server(s) you are connected to (@code{gnus-group-list-active}). This
3357 might very well take quite a while. It might actually be a better idea
3358 to do a @kbd{A M} to list all matching, and just give @samp{.} as the
3359 thing to match on. Also note that this command may list groups that
3360 don't exist (yet)---these will be listed as if they were killed groups.
3361 Take the output with some grains of salt.
3365 @findex gnus-group-apropos
3366 List all groups that have names that match a regexp
3367 (@code{gnus-group-apropos}).
3371 @findex gnus-group-description-apropos
3372 List all groups that have names or descriptions that match a regexp
3373 (@code{gnus-group-description-apropos}).
3377 @findex gnus-group-list-cached
3378 List all groups with cached articles (@code{gnus-group-list-cached}).
3382 @findex gnus-group-list-dormant
3383 List all groups with dormant articles (@code{gnus-group-list-dormant}).
3387 @findex gnus-group-list-limit
3388 List groups limited within the current selection
3389 (@code{gnus-group-list-limit}).
3393 @findex gnus-group-list-flush
3394 Flush groups from the current selection (@code{gnus-group-list-flush}).
3398 @findex gnus-group-list-plus
3399 List groups plus the current selection (@code{gnus-group-list-plus}).
3403 @vindex gnus-permanently-visible-groups
3404 @cindex visible group parameter
3405 Groups that match the @code{gnus-permanently-visible-groups} regexp will
3406 always be shown, whether they have unread articles or not. You can also
3407 add the @code{visible} element to the group parameters in question to
3408 get the same effect.
3410 @vindex gnus-list-groups-with-ticked-articles
3411 Groups that have just ticked articles in it are normally listed in the
3412 group buffer. If @code{gnus-list-groups-with-ticked-articles} is
3413 @code{nil}, these groups will be treated just like totally empty
3414 groups. It is @code{t} by default.
3417 @node Sorting Groups
3418 @section Sorting Groups
3419 @cindex sorting groups
3421 @kindex C-c C-s (Group)
3422 @findex gnus-group-sort-groups
3423 @vindex gnus-group-sort-function
3424 The @kbd{C-c C-s} (@code{gnus-group-sort-groups}) command sorts the
3425 group buffer according to the function(s) given by the
3426 @code{gnus-group-sort-function} variable. Available sorting functions
3431 @item gnus-group-sort-by-alphabet
3432 @findex gnus-group-sort-by-alphabet
3433 Sort the group names alphabetically. This is the default.
3435 @item gnus-group-sort-by-real-name
3436 @findex gnus-group-sort-by-real-name
3437 Sort the group alphabetically on the real (unprefixed) group names.
3439 @item gnus-group-sort-by-level
3440 @findex gnus-group-sort-by-level
3441 Sort by group level.
3443 @item gnus-group-sort-by-score
3444 @findex gnus-group-sort-by-score
3445 Sort by group score. @xref{Group Score}.
3447 @item gnus-group-sort-by-rank
3448 @findex gnus-group-sort-by-rank
3449 Sort by group score and then the group level. The level and the score
3450 are, when taken together, the group's @dfn{rank}. @xref{Group Score}.
3452 @item gnus-group-sort-by-unread
3453 @findex gnus-group-sort-by-unread
3454 Sort by number of unread articles.
3456 @item gnus-group-sort-by-method
3457 @findex gnus-group-sort-by-method
3458 Sort alphabetically on the select method.
3460 @item gnus-group-sort-by-server
3461 @findex gnus-group-sort-by-server
3462 Sort alphabetically on the Gnus server name.
3467 @code{gnus-group-sort-function} can also be a list of sorting
3468 functions. In that case, the most significant sort key function must be
3472 There are also a number of commands for sorting directly according to
3473 some sorting criteria:
3477 @kindex G S a (Group)
3478 @findex gnus-group-sort-groups-by-alphabet
3479 Sort the group buffer alphabetically by group name
3480 (@code{gnus-group-sort-groups-by-alphabet}).
3483 @kindex G S u (Group)
3484 @findex gnus-group-sort-groups-by-unread
3485 Sort the group buffer by the number of unread articles
3486 (@code{gnus-group-sort-groups-by-unread}).
3489 @kindex G S l (Group)
3490 @findex gnus-group-sort-groups-by-level
3491 Sort the group buffer by group level
3492 (@code{gnus-group-sort-groups-by-level}).
3495 @kindex G S v (Group)
3496 @findex gnus-group-sort-groups-by-score
3497 Sort the group buffer by group score
3498 (@code{gnus-group-sort-groups-by-score}). @xref{Group Score}.
3501 @kindex G S r (Group)
3502 @findex gnus-group-sort-groups-by-rank
3503 Sort the group buffer by group rank
3504 (@code{gnus-group-sort-groups-by-rank}). @xref{Group Score}.
3507 @kindex G S m (Group)
3508 @findex gnus-group-sort-groups-by-method
3509 Sort the group buffer alphabetically by back end name@*
3510 (@code{gnus-group-sort-groups-by-method}).
3513 @kindex G S n (Group)
3514 @findex gnus-group-sort-groups-by-real-name
3515 Sort the group buffer alphabetically by real (unprefixed) group name
3516 (@code{gnus-group-sort-groups-by-real-name}).
3520 All the commands below obey the process/prefix convention
3521 (@pxref{Process/Prefix}).
3523 When given a symbolic prefix (@pxref{Symbolic Prefixes}), all these
3524 commands will sort in reverse order.
3526 You can also sort a subset of the groups:
3530 @kindex G P a (Group)
3531 @findex gnus-group-sort-selected-groups-by-alphabet
3532 Sort the groups alphabetically by group name
3533 (@code{gnus-group-sort-selected-groups-by-alphabet}).
3536 @kindex G P u (Group)
3537 @findex gnus-group-sort-selected-groups-by-unread
3538 Sort the groups by the number of unread articles
3539 (@code{gnus-group-sort-selected-groups-by-unread}).
3542 @kindex G P l (Group)
3543 @findex gnus-group-sort-selected-groups-by-level
3544 Sort the groups by group level
3545 (@code{gnus-group-sort-selected-groups-by-level}).
3548 @kindex G P v (Group)
3549 @findex gnus-group-sort-selected-groups-by-score
3550 Sort the groups by group score
3551 (@code{gnus-group-sort-selected-groups-by-score}). @xref{Group Score}.
3554 @kindex G P r (Group)
3555 @findex gnus-group-sort-selected-groups-by-rank
3556 Sort the groups by group rank
3557 (@code{gnus-group-sort-selected-groups-by-rank}). @xref{Group Score}.
3560 @kindex G P m (Group)
3561 @findex gnus-group-sort-selected-groups-by-method
3562 Sort the groups alphabetically by back end name@*
3563 (@code{gnus-group-sort-selected-groups-by-method}).
3566 @kindex G P n (Group)
3567 @findex gnus-group-sort-selected-groups-by-real-name
3568 Sort the groups alphabetically by real (unprefixed) group name
3569 (@code{gnus-group-sort-selected-groups-by-real-name}).
3572 @kindex G P s (Group)
3573 @findex gnus-group-sort-selected-groups
3574 Sort the groups according to @code{gnus-group-sort-function}.
3578 And finally, note that you can use @kbd{C-k} and @kbd{C-y} to manually
3582 @node Group Maintenance
3583 @section Group Maintenance
3584 @cindex bogus groups
3589 @findex gnus-group-check-bogus-groups
3590 Find bogus groups and delete them
3591 (@code{gnus-group-check-bogus-groups}).
3595 @findex gnus-group-find-new-groups
3596 Find new groups and process them (@code{gnus-group-find-new-groups}).
3597 With 1 @kbd{C-u}, use the @code{ask-server} method to query the server
3598 for new groups. With 2 @kbd{C-u}'s, use most complete method possible
3599 to query the server for new groups, and subscribe the new groups as
3603 @kindex C-c C-x (Group)
3604 @findex gnus-group-expire-articles
3605 @cindex expiring mail
3606 Run all expirable articles in the current group through the expiry
3607 process (if any) (@code{gnus-group-expire-articles}). That is, delete
3608 all expirable articles in the group that have been around for a while.
3609 (@pxref{Expiring Mail}).
3612 @kindex C-c C-M-x (Group)
3613 @findex gnus-group-expire-all-groups
3614 @cindex expiring mail
3615 Run all expirable articles in all groups through the expiry process
3616 (@code{gnus-group-expire-all-groups}).
3621 @node Browse Foreign Server
3622 @section Browse Foreign Server
3623 @cindex foreign servers
3624 @cindex browsing servers
3629 @findex gnus-group-browse-foreign-server
3630 You will be queried for a select method and a server name. Gnus will
3631 then attempt to contact this server and let you browse the groups there
3632 (@code{gnus-group-browse-foreign-server}).
3635 @findex gnus-browse-mode
3636 A new buffer with a list of available groups will appear. This buffer
3637 will use the @code{gnus-browse-mode}. This buffer looks a bit (well,
3638 a lot) like a normal group buffer.
3640 Here's a list of keystrokes available in the browse mode:
3645 @findex gnus-group-next-group
3646 Go to the next group (@code{gnus-group-next-group}).
3650 @findex gnus-group-prev-group
3651 Go to the previous group (@code{gnus-group-prev-group}).
3654 @kindex SPACE (Browse)
3655 @findex gnus-browse-read-group
3656 Enter the current group and display the first article
3657 (@code{gnus-browse-read-group}).
3660 @kindex RET (Browse)
3661 @findex gnus-browse-select-group
3662 Enter the current group (@code{gnus-browse-select-group}).
3666 @findex gnus-browse-unsubscribe-current-group
3667 Unsubscribe to the current group, or, as will be the case here,
3668 subscribe to it (@code{gnus-browse-unsubscribe-current-group}).
3674 @findex gnus-browse-exit
3675 Exit browse mode (@code{gnus-browse-exit}).
3679 @findex gnus-browse-describe-group
3680 Describe the current group (@code{gnus-browse-describe-group}).
3684 @findex gnus-browse-describe-briefly
3685 Describe browse mode briefly (well, there's not much to describe, is
3686 there) (@code{gnus-browse-describe-briefly}).
3691 @section Exiting Gnus
3692 @cindex exiting Gnus
3694 Yes, Gnus is ex(c)iting.
3699 @findex gnus-group-suspend
3700 Suspend Gnus (@code{gnus-group-suspend}). This doesn't really exit Gnus,
3701 but it kills all buffers except the Group buffer. I'm not sure why this
3702 is a gain, but then who am I to judge?
3706 @findex gnus-group-exit
3707 @c @icon{gnus-group-exit}
3708 Quit Gnus (@code{gnus-group-exit}).
3712 @findex gnus-group-quit
3713 Quit Gnus without saving the @file{.newsrc} files (@code{gnus-group-quit}).
3714 The dribble file will be saved, though (@pxref{Auto Save}).
3717 @vindex gnus-exit-gnus-hook
3718 @vindex gnus-suspend-gnus-hook
3719 @vindex gnus-after-exiting-gnus-hook
3720 @code{gnus-suspend-gnus-hook} is called when you suspend Gnus and
3721 @code{gnus-exit-gnus-hook} is called when you quit Gnus, while
3722 @code{gnus-after-exiting-gnus-hook} is called as the final item when
3728 Miss Lisa Cannifax, while sitting in English class, felt her feet go
3729 numbly heavy and herself fall into a hazy trance as the boy sitting
3730 behind her drew repeated lines with his pencil across the back of her
3736 @section Group Topics
3739 If you read lots and lots of groups, it might be convenient to group
3740 them hierarchically according to topics. You put your Emacs groups over
3741 here, your sex groups over there, and the rest (what, two groups or so?)
3742 you put in some misc section that you never bother with anyway. You can
3743 even group the Emacs sex groups as a sub-topic to either the Emacs
3744 groups or the sex groups---or both! Go wild!
3748 \gnusfigure{Group Topics}{400}{
3749 \put(75,50){\epsfig{figure=ps/group-topic,height=9cm}}
3760 2: alt.religion.emacs
3763 0: comp.talk.emacs.recovery
3765 8: comp.binaries.fractals
3766 13: comp.sources.unix
3769 @findex gnus-topic-mode
3771 To get this @emph{fab} functionality you simply turn on (ooh!) the
3772 @code{gnus-topic} minor mode---type @kbd{t} in the group buffer. (This
3773 is a toggling command.)
3775 Go ahead, just try it. I'll still be here when you get back. La de
3776 dum@dots{} Nice tune, that@dots{} la la la@dots{} What, you're back?
3777 Yes, and now press @kbd{l}. There. All your groups are now listed
3778 under @samp{misc}. Doesn't that make you feel all warm and fuzzy?
3781 If you want this permanently enabled, you should add that minor mode to
3782 the hook for the group mode. Put the following line in your
3783 @file{~/.gnus.el} file:
3786 (add-hook 'gnus-group-mode-hook 'gnus-topic-mode)
3790 * Topic Commands:: Interactive E-Z commands.
3791 * Topic Variables:: How to customize the topics the Lisp Way.
3792 * Topic Sorting:: Sorting each topic individually.
3793 * Topic Topology:: A map of the world.
3794 * Topic Parameters:: Parameters that apply to all groups in a topic.
3798 @node Topic Commands
3799 @subsection Topic Commands
3800 @cindex topic commands
3802 When the topic minor mode is turned on, a new @kbd{T} submap will be
3803 available. In addition, a few of the standard keys change their
3804 definitions slightly.
3806 In general, the following kinds of operations are possible on topics.
3807 First of all, you want to create topics. Secondly, you want to put
3808 groups in topics and to move them around until you have an order you
3809 like. The third kind of operation is to show/hide parts of the whole
3810 shebang. You might want to hide a topic including its subtopics and
3811 groups, to get a better overview of the other groups.
3813 Here is a list of the basic keys that you might need to set up topics
3820 @findex gnus-topic-create-topic
3821 Prompt for a new topic name and create it
3822 (@code{gnus-topic-create-topic}).
3826 @kindex T TAB (Topic)
3828 @findex gnus-topic-indent
3829 ``Indent'' the current topic so that it becomes a sub-topic of the
3830 previous topic (@code{gnus-topic-indent}). If given a prefix,
3831 ``un-indent'' the topic instead.
3834 @kindex M-TAB (Topic)
3835 @findex gnus-topic-unindent
3836 ``Un-indent'' the current topic so that it becomes a sub-topic of the
3837 parent of its current parent (@code{gnus-topic-unindent}).
3841 The following two keys can be used to move groups and topics around.
3842 They work like the well-known cut and paste. @kbd{C-k} is like cut and
3843 @kbd{C-y} is like paste. Of course, this being Emacs, we use the terms
3844 kill and yank rather than cut and paste.
3850 @findex gnus-topic-kill-group
3851 Kill a group or topic (@code{gnus-topic-kill-group}). All groups in the
3852 topic will be removed along with the topic.
3856 @findex gnus-topic-yank-group
3857 Yank the previously killed group or topic
3858 (@code{gnus-topic-yank-group}). Note that all topics will be yanked
3861 So, to move a topic to the beginning of the list of topics, just hit
3862 @kbd{C-k} on it. This is like the ``cut'' part of cut and paste. Then,
3863 move the cursor to the beginning of the buffer (just below the ``Gnus''
3864 topic) and hit @kbd{C-y}. This is like the ``paste'' part of cut and
3865 paste. Like I said -- E-Z.
3867 You can use @kbd{C-k} and @kbd{C-y} on groups as well as on topics. So
3868 you can move topics around as well as groups.
3872 After setting up the topics the way you like them, you might wish to
3873 hide a topic, or to show it again. That's why we have the following
3880 @findex gnus-topic-select-group
3882 Either select a group or fold a topic (@code{gnus-topic-select-group}).
3883 When you perform this command on a group, you'll enter the group, as
3884 usual. When done on a topic line, the topic will be folded (if it was
3885 visible) or unfolded (if it was folded already). So it's basically a
3886 toggling command on topics. In addition, if you give a numerical
3887 prefix, group on that level (and lower) will be displayed.
3891 Now for a list of other commands, in no particular order.
3897 @findex gnus-topic-move-group
3898 Move the current group to some other topic
3899 (@code{gnus-topic-move-group}). This command uses the process/prefix
3900 convention (@pxref{Process/Prefix}).
3904 @findex gnus-topic-jump-to-topic
3905 Go to a topic (@code{gnus-topic-jump-to-topic}).
3909 @findex gnus-topic-copy-group
3910 Copy the current group to some other topic
3911 (@code{gnus-topic-copy-group}). This command uses the process/prefix
3912 convention (@pxref{Process/Prefix}).
3916 @findex gnus-topic-hide-topic
3917 Hide the current topic (@code{gnus-topic-hide-topic}). If given
3918 a prefix, hide the topic permanently.
3922 @findex gnus-topic-show-topic
3923 Show the current topic (@code{gnus-topic-show-topic}). If given
3924 a prefix, show the topic permanently.
3928 @findex gnus-topic-remove-group
3929 Remove a group from the current topic (@code{gnus-topic-remove-group}).
3930 This command is mainly useful if you have the same group in several
3931 topics and wish to remove it from one of the topics. You may also
3932 remove a group from all topics, but in that case, Gnus will add it to
3933 the root topic the next time you start Gnus. In fact, all new groups
3934 (which, naturally, don't belong to any topic) will show up in the root
3937 This command uses the process/prefix convention
3938 (@pxref{Process/Prefix}).
3942 @findex gnus-topic-move-matching
3943 Move all groups that match some regular expression to a topic
3944 (@code{gnus-topic-move-matching}).
3948 @findex gnus-topic-copy-matching
3949 Copy all groups that match some regular expression to a topic
3950 (@code{gnus-topic-copy-matching}).
3954 @findex gnus-topic-toggle-display-empty-topics
3955 Toggle hiding empty topics
3956 (@code{gnus-topic-toggle-display-empty-topics}).
3960 @findex gnus-topic-mark-topic
3961 Mark all groups in the current topic with the process mark
3962 (@code{gnus-topic-mark-topic}). This command works recursively on
3963 sub-topics unless given a prefix.
3966 @kindex T M-# (Topic)
3967 @findex gnus-topic-unmark-topic
3968 Remove the process mark from all groups in the current topic
3969 (@code{gnus-topic-unmark-topic}). This command works recursively on
3970 sub-topics unless given a prefix.
3973 @kindex C-c C-x (Topic)
3974 @findex gnus-topic-expire-articles
3975 @cindex expiring mail
3976 Run all expirable articles in the current group or topic through the
3977 expiry process (if any)
3978 (@code{gnus-topic-expire-articles}). (@pxref{Expiring Mail}).
3982 @findex gnus-topic-rename
3983 Rename a topic (@code{gnus-topic-rename}).
3986 @kindex T DEL (Topic)
3987 @findex gnus-topic-delete
3988 Delete an empty topic (@code{gnus-topic-delete}).
3992 @findex gnus-topic-list-active
3993 List all groups that Gnus knows about in a topics-ified way
3994 (@code{gnus-topic-list-active}).
3997 @kindex T M-n (Topic)
3998 @findex gnus-topic-goto-next-topic
3999 Go to the next topic (@code{gnus-topic-goto-next-topic}).
4002 @kindex T M-p (Topic)
4003 @findex gnus-topic-goto-previous-topic
4004 Go to the previous topic (@code{gnus-topic-goto-previous-topic}).
4008 @findex gnus-topic-edit-parameters
4009 @cindex group parameters
4010 @cindex topic parameters
4012 Edit the topic parameters (@code{gnus-topic-edit-parameters}).
4013 @xref{Topic Parameters}.
4018 @node Topic Variables
4019 @subsection Topic Variables
4020 @cindex topic variables
4022 The previous section told you how to tell Gnus which topics to display.
4023 This section explains how to tell Gnus what to display about each topic.
4025 @vindex gnus-topic-line-format
4026 The topic lines themselves are created according to the
4027 @code{gnus-topic-line-format} variable (@pxref{Formatting Variables}).
4040 Number of groups in the topic.
4042 Number of unread articles in the topic.
4044 Number of unread articles in the topic and all its subtopics.
4047 @vindex gnus-topic-indent-level
4048 Each sub-topic (and the groups in the sub-topics) will be indented with
4049 @code{gnus-topic-indent-level} times the topic level number of spaces.
4052 @vindex gnus-topic-mode-hook
4053 @code{gnus-topic-mode-hook} is called in topic minor mode buffers.
4055 @vindex gnus-topic-display-empty-topics
4056 The @code{gnus-topic-display-empty-topics} says whether to display even
4057 topics that have no unread articles in them. The default is @code{t}.
4061 @subsection Topic Sorting
4062 @cindex topic sorting
4064 You can sort the groups in each topic individually with the following
4070 @kindex T S a (Topic)
4071 @findex gnus-topic-sort-groups-by-alphabet
4072 Sort the current topic alphabetically by group name
4073 (@code{gnus-topic-sort-groups-by-alphabet}).
4076 @kindex T S u (Topic)
4077 @findex gnus-topic-sort-groups-by-unread
4078 Sort the current topic by the number of unread articles
4079 (@code{gnus-topic-sort-groups-by-unread}).
4082 @kindex T S l (Topic)
4083 @findex gnus-topic-sort-groups-by-level
4084 Sort the current topic by group level
4085 (@code{gnus-topic-sort-groups-by-level}).
4088 @kindex T S v (Topic)
4089 @findex gnus-topic-sort-groups-by-score
4090 Sort the current topic by group score
4091 (@code{gnus-topic-sort-groups-by-score}). @xref{Group Score}.
4094 @kindex T S r (Topic)
4095 @findex gnus-topic-sort-groups-by-rank
4096 Sort the current topic by group rank
4097 (@code{gnus-topic-sort-groups-by-rank}). @xref{Group Score}.
4100 @kindex T S m (Topic)
4101 @findex gnus-topic-sort-groups-by-method
4102 Sort the current topic alphabetically by back end name
4103 (@code{gnus-topic-sort-groups-by-method}).
4106 @kindex T S e (Topic)
4107 @findex gnus-topic-sort-groups-by-server
4108 Sort the current topic alphabetically by server name
4109 (@code{gnus-topic-sort-groups-by-server}).
4112 @kindex T S s (Topic)
4113 @findex gnus-topic-sort-groups
4114 Sort the current topic according to the function(s) given by the
4115 @code{gnus-group-sort-function} variable
4116 (@code{gnus-topic-sort-groups}).
4120 When given a prefix argument, all these commands will sort in reverse
4121 order. @xref{Sorting Groups}, for more information about group
4125 @node Topic Topology
4126 @subsection Topic Topology
4127 @cindex topic topology
4130 So, let's have a look at an example group buffer:
4137 2: alt.religion.emacs
4140 0: comp.talk.emacs.recovery
4142 8: comp.binaries.fractals
4143 13: comp.sources.unix
4147 So, here we have one top-level topic (@samp{Gnus}), two topics under
4148 that, and one sub-topic under one of the sub-topics. (There is always
4149 just one (1) top-level topic). This topology can be expressed as
4154 (("Emacs -- I wuw it!" visible)
4155 (("Naughty Emacs" visible)))
4159 @vindex gnus-topic-topology
4160 This is in fact how the variable @code{gnus-topic-topology} would look
4161 for the display above. That variable is saved in the @file{.newsrc.eld}
4162 file, and shouldn't be messed with manually---unless you really want
4163 to. Since this variable is read from the @file{.newsrc.eld} file,
4164 setting it in any other startup files will have no effect.
4166 This topology shows what topics are sub-topics of what topics (right),
4167 and which topics are visible. Two settings are currently
4168 allowed---@code{visible} and @code{invisible}.
4171 @node Topic Parameters
4172 @subsection Topic Parameters
4173 @cindex topic parameters
4175 All groups in a topic will inherit group parameters from the parent
4176 (and ancestor) topic parameters. All valid group parameters are valid
4177 topic parameters (@pxref{Group Parameters}). When the agent is
4178 enabled, all agent parameters (See Agent Parameters in @ref{Category
4179 Syntax}) are also valid topic parameters.
4181 In addition, the following parameters are only valid as topic
4186 When subscribing new groups by topic (@pxref{Subscription Methods}), the
4187 @code{subscribe} topic parameter says what groups go in what topic. Its
4188 value should be a regexp to match the groups that should go in that
4191 @item subscribe-level
4192 When subscribing new groups by topic (see the @code{subscribe} parameter),
4193 the group will be subscribed with the level specified in the
4194 @code{subscribe-level} instead of @code{gnus-level-default-subscribed}.
4198 Group parameters (of course) override topic parameters, and topic
4199 parameters in sub-topics override topic parameters in super-topics. You
4200 know. Normal inheritance rules. (@dfn{Rules} is here a noun, not a
4201 verb, although you may feel free to disagree with me here.)
4208 2: alt.religion.emacs
4212 0: comp.talk.emacs.recovery
4214 8: comp.binaries.fractals
4215 13: comp.sources.unix
4220 The @samp{Emacs} topic has the topic parameter @code{(score-file
4221 . "emacs.SCORE")}; the @samp{Relief} topic has the topic parameter
4222 @code{(score-file . "relief.SCORE")}; and the @samp{Misc} topic has the
4223 topic parameter @code{(score-file . "emacs.SCORE")}. In addition,
4224 @* @samp{alt.religion.emacs} has the group parameter @code{(score-file
4225 . "religion.SCORE")}.
4227 Now, when you enter @samp{alt.sex.emacs} in the @samp{Relief} topic, you
4228 will get the @file{relief.SCORE} home score file. If you enter the same
4229 group in the @samp{Emacs} topic, you'll get the @file{emacs.SCORE} home
4230 score file. If you enter the group @samp{alt.religion.emacs}, you'll
4231 get the @file{religion.SCORE} home score file.
4233 This seems rather simple and self-evident, doesn't it? Well, yes. But
4234 there are some problems, especially with the @code{total-expiry}
4235 parameter. Say you have a mail group in two topics; one with
4236 @code{total-expiry} and one without. What happens when you do @kbd{M-x
4237 gnus-expire-all-expirable-groups}? Gnus has no way of telling which one
4238 of these topics you mean to expire articles from, so anything may
4239 happen. In fact, I hereby declare that it is @dfn{undefined} what
4240 happens. You just have to be careful if you do stuff like that.
4243 @node Non-ASCII Group Names
4244 @section Accessing groups of non-English names
4245 @cindex non-ascii group names
4247 There are some news servers that provide groups of which the names are
4248 expressed with their native languages in the world. For instance, in a
4249 certain news server there are some newsgroups of which the names are
4250 spelled in Chinese, where people are talking in Chinese. You can, of
4251 course, subscribe to such news groups using Gnus. Currently Gnus
4252 supports non-@acronym{ASCII} group names not only with the @code{nntp}
4253 back end but also with the @code{nnml} back end and the @code{nnrss}
4256 Every such group name is encoded by a certain charset in the server
4257 side (in an @acronym{NNTP} server its administrator determines the
4258 charset, but for groups in the other back ends it is determined by you).
4259 Gnus has to display the decoded ones for you in the group buffer and the
4260 article buffer, and needs to use the encoded ones when communicating
4261 with servers. However, Gnus doesn't know what charset is used for each
4262 non-@acronym{ASCII} group name. The following two variables are just
4263 the ones for telling Gnus what charset should be used for each group:
4266 @item gnus-group-name-charset-method-alist
4267 @vindex gnus-group-name-charset-method-alist
4268 An alist of select methods and charsets. The default value is
4269 @code{nil}. The names of groups in the server specified by that select
4270 method are all supposed to use the corresponding charset. For example:
4273 (setq gnus-group-name-charset-method-alist
4274 '(((nntp "news.com.cn") . cn-gb-2312)))
4277 Charsets specified for groups with this variable are preferred to the
4278 ones specified for the same groups with the
4279 @code{gnus-group-name-charset-group-alist} variable (see below).
4281 A select method can be very long, like:
4285 (nntp-address "news.gmane.org")
4286 (nntp-end-of-line "\n")
4287 (nntp-open-connection-function
4288 nntp-open-via-rlogin-and-telnet)
4289 (nntp-via-rlogin-command "ssh")
4290 (nntp-via-rlogin-command-switches
4291 ("-C" "-t" "-e" "none"))
4292 (nntp-via-address @dots{}))
4295 In that case, you can truncate it into @code{(nntp "gmane")} in this
4296 variable. That is, it is enough to contain only the back end name and
4299 @item gnus-group-name-charset-group-alist
4300 @cindex UTF-8 group names
4301 @vindex gnus-group-name-charset-group-alist
4302 An alist of regexp of group name and the charset for group names.
4303 @code{((".*" . utf-8))} is the default value if UTF-8 is supported,
4304 otherwise the default is @code{nil}. For example:
4307 (setq gnus-group-name-charset-group-alist
4308 '(("\\.com\\.cn:" . cn-gb-2312)
4312 Note that this variable is ignored if the match is made with
4313 @code{gnus-group-name-charset-method-alist}.
4316 Those two variables are used also to determine the charset for encoding
4317 and decoding non-@acronym{ASCII} group names that are in the back ends
4318 other than @code{nntp}. It means that it is you who determine it. If
4319 you do nothing, the charset used for group names in those back ends will
4320 all be @code{utf-8} because of the last element of
4321 @code{gnus-group-name-charset-group-alist}.
4323 There is one more important variable for non-@acronym{ASCII} group
4327 @item nnmail-pathname-coding-system
4328 @vindex nnmail-pathname-coding-system
4329 The value of this variable should be a coding system or @code{nil}. The
4330 default is @code{nil} in Emacs, or is the aliasee of the coding system
4331 named @code{file-name} (a certain coding system of which an alias is
4332 @code{file-name}) in XEmacs.
4334 The @code{nnml} back end, the @code{nnrss} back end, the @acronym{NNTP}
4335 marks feature (@pxref{NNTP marks}), the agent, and the cache use
4336 non-@acronym{ASCII} group names in those files and directories. This
4337 variable overrides the value of @code{file-name-coding-system} which
4338 specifies the coding system used when encoding and decoding those file
4339 names and directory names.
4341 In XEmacs (with the @code{mule} feature), @code{file-name-coding-system}
4342 is the only means to specify the coding system used to encode and decode
4343 file names. On the other hand, Emacs uses the value of
4344 @code{default-file-name-coding-system} if @code{file-name-coding-system}
4345 is @code{nil} or it is bound to the value of
4346 @code{nnmail-pathname-coding-system} which is @code{nil}.
4348 Normally the value of @code{default-file-name-coding-system} in Emacs or
4349 @code{nnmail-pathname-coding-system} in XEmacs is initialized according
4350 to the locale, so you will need to do nothing if the value is suitable
4351 to encode and decode non-@acronym{ASCII} group names.
4353 The value of this variable (or @code{default-file-name-coding-system})
4354 does not necessarily need to be the same value that is determined by
4355 @code{gnus-group-name-charset-method-alist} and
4356 @code{gnus-group-name-charset-group-alist}.
4358 If @code{default-file-name-coding-system} or this variable is
4359 initialized by default to @code{iso-latin-1} for example, although you
4360 want to subscribe to the groups spelled in Chinese, that is the most
4361 typical case where you have to customize
4362 @code{nnmail-pathname-coding-system}. The @code{utf-8} coding system is
4363 a good candidate for it. Otherwise, you may change the locale in your
4364 system so that @code{default-file-name-coding-system} or this variable
4365 may be initialized to an appropriate value.
4368 Note that when you copy or move articles from a non-@acronym{ASCII}
4369 group to another group, the charset used to encode and decode group
4370 names should be the same in both groups. Otherwise the Newsgroups
4371 header will be displayed incorrectly in the article buffer.
4378 * nnir:: Searching on IMAP, with swish, namazu, etc.
4379 * nnmairix:: Searching maildir, MH or mbox with Mairix.
4384 FIXME: This node is a stub.
4386 FIXME: Add a brief overview of Gnus search capabilities. A brief
4387 comparison of nnir, nnmairix, contrib/gnus-namazu would be nice
4390 FIXME: Explain difference to @ref{Searching for Articles}, add reference
4396 FIXME: As a first step, convert the commentary of @file{nnir} to texi.
4400 @subsection nnmairix
4404 This paragraph describes how to set up mairix and the back end
4405 @code{nnmairix} for indexing and searching your mail from within
4406 Gnus. Additionally, you can create permanent ``smart'' groups which are
4407 bound to mairix searches and are automatically updated.
4410 * About mairix:: About the mairix mail search engine
4411 * nnmairix requirements:: What you will need for using nnmairix
4412 * What nnmairix does:: What does nnmairix actually do?
4413 * Setting up mairix:: Set up your mairix installation
4414 * Configuring nnmairix:: Set up the nnmairix back end
4415 * nnmairix keyboard shortcuts:: List of available keyboard shortcuts
4416 * Propagating marks:: How to propagate marks from nnmairix groups
4417 * nnmairix tips and tricks:: Some tips, tricks and examples
4418 * nnmairix caveats:: Some more stuff you might want to know
4421 @c FIXME: The markup in this section might need improvement.
4422 @c E.g. adding @samp, @var, @file, @command, etc.
4423 @c Cf. (info "(texinfo)Indicating")
4426 @subsubsection About mairix
4428 Mairix is a tool for indexing and searching words in locally stored
4429 mail. It was written by Richard Curnow and is licensed under the
4430 GPL. Mairix comes with most popular GNU/Linux distributions, but it also
4431 runs under Windows (with cygwin), Mac OS X and Solaris. The homepage can
4433 @uref{http://www.rpcurnow.force9.co.uk/mairix/index.html}
4435 Though mairix might not be as flexible as other search tools like
4436 swish++ or namazu, which you can use via the @code{nnir} back end, it
4437 has the prime advantage of being incredibly fast. On current systems, it
4438 can easily search through headers and message bodies of thousands and
4439 thousands of mails in well under a second. Building the database
4440 necessary for searching might take a minute or two, but only has to be
4441 done once fully. Afterwards, the updates are done incrementally and
4442 therefore are really fast, too. Additionally, mairix is very easy to set
4445 For maximum speed though, mairix should be used with mails stored in
4446 @code{Maildir} or @code{MH} format (this includes the @code{nnml} back
4447 end), although it also works with mbox. Mairix presents the search
4448 results by populating a @emph{virtual} maildir/MH folder with symlinks
4449 which point to the ``real'' message files (if mbox is used, copies are
4450 made). Since mairix already presents search results in such a virtual
4451 mail folder, it is very well suited for using it as an external program
4452 for creating @emph{smart} mail folders, which represent certain mail
4453 searches. This is similar to a Kiboze group (@pxref{Kibozed Groups}),
4456 @node nnmairix requirements
4457 @subsubsection nnmairix requirements
4459 Mairix searches local mail---that means, mairix absolutely must have
4460 direct access to your mail folders. If your mail resides on another
4461 server (e.g. an @acronym{IMAP} server) and you happen to have shell
4462 access, @code{nnmairix} supports running mairix remotely, e.g. via ssh.
4464 Additionally, @code{nnmairix} only supports the following Gnus back
4465 ends: @code{nnml}, @code{nnmaildir}, and @code{nnimap}. You must use
4466 one of these back ends for using @code{nnmairix}. Other back ends, like
4467 @code{nnmbox}, @code{nnfolder} or @code{nnmh}, won't work.
4469 If you absolutely must use mbox and still want to use @code{nnmairix},
4470 you can set up a local @acronym{IMAP} server, which you then access via
4471 @code{nnimap}. This is a rather massive setup for accessing some mbox
4472 files, so just change to MH or Maildir already... However, if you're
4473 really, really passionate about using mbox, you might want to look into
4474 the package @file{mairix.el}, which comes with Emacs 23.
4476 @node What nnmairix does
4477 @subsubsection What nnmairix does
4479 The back end @code{nnmairix} enables you to call mairix from within Gnus,
4480 either to query mairix with a search term or to update the
4481 database. While visiting a message in the summary buffer, you can use
4482 several pre-defined shortcuts for calling mairix, e.g. to quickly
4483 search for all mails from the sender of the current message or to
4484 display the whole thread associated with the message, even if the
4485 mails are in different folders.
4487 Additionally, you can create permanent @code{nnmairix} groups which are bound
4488 to certain mairix searches. This way, you can easily create a group
4489 containing mails from a certain sender, with a certain subject line or
4490 even for one specific thread based on the Message-ID. If you check for
4491 new mail in these folders (e.g. by pressing @kbd{g} or @kbd{M-g}), they
4492 automatically update themselves by calling mairix.
4494 You might ask why you need @code{nnmairix} at all, since mairix already
4495 creates the group, populates it with links to the mails so that you can
4496 then access it with Gnus, right? Well, this @emph{might} work, but often
4497 does not---at least not without problems. Most probably you will get
4498 strange article counts, and sometimes you might see mails which Gnus
4499 claims have already been canceled and are inaccessible. This is due to
4500 the fact that Gnus isn't really amused when things are happening behind
4501 its back. Another problem can be the mail back end itself, e.g. if you
4502 use mairix with an @acronym{IMAP} server (I had Dovecot complaining
4503 about corrupt index files when mairix changed the contents of the search
4504 group). Using @code{nnmairix} should circumvent these problems.
4506 @code{nnmairix} is not really a mail back end---it's actually more like
4507 a wrapper, sitting between a ``real'' mail back end where mairix stores
4508 the searches and the Gnus front end. You can choose between three
4509 different mail back ends for the mairix folders: @code{nnml},
4510 @code{nnmaildir} or @code{nnimap}. @code{nnmairix} will call the mairix
4511 binary so that the search results are stored in folders named
4512 @code{zz_mairix-<NAME>-<NUMBER>} on this mail back end, but it will
4513 present these folders in the Gnus front end only with @code{<NAME>}.
4514 You can use an existing mail back end where you already store your mail,
4515 but if you're uncomfortable with @code{nnmairix} creating new mail
4516 groups alongside your other mail, you can also create e.g. a new
4517 @code{nnmaildir} or @code{nnml} server exclusively for mairix, but then
4518 make sure those servers do not accidentally receive your new mail
4519 (@pxref{nnmairix caveats}). A special case exists if you want to use
4520 mairix remotely on an IMAP server with @code{nnimap}---here the mairix
4521 folders and your other mail must be on the same @code{nnimap} back end.
4523 @node Setting up mairix
4524 @subsubsection Setting up mairix
4526 First: create a backup of your mail folders (@pxref{nnmairix caveats}).
4528 Setting up mairix is easy: simply create a @file{.mairixrc} file with
4529 (at least) the following entries:
4532 # Your Maildir/MH base folder
4536 This is the base folder for your mails. All the following directories
4537 are relative to this base folder. If you want to use @code{nnmairix}
4538 with @code{nnimap}, this base directory has to point to the mail
4539 directory where the @acronym{IMAP} server stores the mail folders!
4542 maildir= ... your maildir folders which should be indexed ...
4543 mh= ... your nnml/mh folders which should be indexed ...
4544 mbox = ... your mbox files which should be indexed ...
4547 This specifies all your mail folders and mbox files (relative to the
4548 base directory!) you want to index with mairix. Note that the
4549 @code{nnml} back end saves mails in MH format, so you have to put those
4550 directories in the @code{mh} line. See the example at the end of this
4551 section and mairixrc's man-page for further details.
4557 @vindex nnmairix-group-prefix
4558 This should make sure that you don't accidentally index the mairix
4559 search results. You can change the prefix of these folders with the
4560 variable @code{nnmairix-group-prefix}.
4563 mformat= ... 'maildir' or 'mh' ...
4564 database= ... location of database file ...
4567 The @code{format} setting specifies the output format for the mairix
4568 search folder. Set this to @code{mh} if you want to access search results
4569 with @code{nnml}. Otherwise choose @code{maildir}.
4571 To summarize, here is my shortened @file{.mairixrc} file as an example:
4575 maildir=.personal:.work:.logcheck:.sent
4576 mh=../Mail/nnml/*...
4577 mbox=../mboxmail/mailarchive_year*
4580 database=~/.mairixdatabase
4583 In this case, the base directory is @file{~/Maildir}, where all my Maildir
4584 folders are stored. As you can see, the folders are separated by
4585 colons. If you wonder why every folder begins with a dot: this is
4586 because I use Dovecot as @acronym{IMAP} server, which again uses
4587 @code{Maildir++} folders. For testing nnmairix, I also have some
4588 @code{nnml} mail, which is saved in @file{~/Mail/nnml}. Since this has
4589 to be specified relative to the @code{base} directory, the @code{../Mail}
4590 notation is needed. Note that the line ends in @code{*...}, which means
4591 to recursively scan all files under this directory. Without the three
4592 dots, the wildcard @code{*} will not work recursively. I also have some
4593 old mbox files with archived mail lying around in @file{~/mboxmail}.
4594 The other lines should be obvious.
4596 See the man page for @code{mairixrc} for details and further options,
4597 especially regarding wildcard usage, which may be a little different
4598 than you are used to.
4600 Now simply call @code{mairix} to create the index for the first time.
4601 Note that this may take a few minutes, but every following index will do
4602 the updates incrementally and hence is very fast.
4604 @node Configuring nnmairix
4605 @subsubsection Configuring nnmairix
4607 In group mode, type @kbd{G b c}
4608 (@code{nnmairix-create-server-and-default-group}). This will ask you for all
4609 necessary information and create a @code{nnmairix} server as a foreign
4610 server. You will have to specify the following:
4615 The @strong{name} of the @code{nnmairix} server---choose whatever you
4619 The name of the @strong{back end server} where mairix should store its
4620 searches. This must be a full server name, like @code{nnml:mymail}.
4621 Just hit @kbd{TAB} to see the available servers. Currently, servers
4622 which are accessed through @code{nnmaildir}, @code{nnimap} and
4623 @code{nnml} are supported. As explained above, for locally stored
4624 mails, this can be an existing server where you store your mails.
4625 However, you can also create e.g. a new @code{nnmaildir} or @code{nnml}
4626 server exclusively for @code{nnmairix} in your secondary select methods
4627 (@pxref{Finding the News}). If you use a secondary @code{nnml} server
4628 just for mairix, make sure that you explicitly set the server variable
4629 @code{nnml-get-new-mail} to @code{nil}, or you might loose mail
4630 (@pxref{nnmairix caveats}). If you want to use mairix remotely on an
4631 @acronym{IMAP} server, you have to choose the corresponding
4632 @code{nnimap} server here.
4635 @vindex nnmairix-mairix-search-options
4636 The @strong{command} to call the mairix binary. This will usually just
4637 be @code{mairix}, but you can also choose something like @code{ssh
4638 SERVER mairix} if you want to call mairix remotely, e.g. on your
4639 @acronym{IMAP} server. If you want to add some default options to
4640 mairix, you could do this here, but better use the variable
4641 @code{nnmairix-mairix-search-options} instead.
4644 The name of the @strong{default search group}. This will be the group
4645 where all temporary mairix searches are stored, i.e. all searches which
4646 are not bound to permanent @code{nnmairix} groups. Choose whatever you
4650 If the mail back end is @code{nnimap} or @code{nnmaildir}, you will be
4651 asked if you work with @strong{Maildir++}, i.e. with hidden maildir
4652 folders (=beginning with a dot). For example, you have to answer
4653 @samp{yes} here if you work with the Dovecot @acronym{IMAP}
4654 server. Otherwise, you should answer @samp{no} here.
4658 @node nnmairix keyboard shortcuts
4659 @subsubsection nnmairix keyboard shortcuts
4666 @kindex G b c (Group)
4667 @findex nnmairix-create-server-and-default-group
4668 Creates @code{nnmairix} server and default search group for this server
4669 (@code{nnmairix-create-server-and-default-group}). You should have done
4670 this by now (@pxref{Configuring nnmairix}).
4673 @kindex G b s (Group)
4674 @findex nnmairix-search
4675 Prompts for query which is then sent to the mairix binary. Search
4676 results are put into the default search group which is automatically
4677 displayed (@code{nnmairix-search}).
4680 @kindex G b m (Group)
4681 @findex nnmairix-widget-search
4682 Allows you to create a mairix search or a permanent group more
4683 comfortably using graphical widgets, similar to a customization
4684 group. Just try it to see how it works (@code{nnmairix-widget-search}).
4687 @kindex G b i (Group)
4688 @findex nnmairix-search-interactive
4689 Another command for creating a mairix query more comfortably, but uses
4690 only the minibuffer (@code{nnmairix-search-interactive}).
4693 @kindex G b g (Group)
4694 @findex nnmairix-create-search-group
4695 Creates a permanent group which is associated with a search query
4696 (@code{nnmairix-create-search-group}). The @code{nnmairix} back end
4697 automatically calls mairix when you update this group with @kbd{g} or
4701 @kindex G b q (Group)
4702 @findex nnmairix-group-change-query-this-group
4703 Changes the search query for the @code{nnmairix} group under cursor
4704 (@code{nnmairix-group-change-query-this-group}).
4707 @kindex G b t (Group)
4708 @findex nnmairix-group-toggle-threads-this-group
4709 Toggles the 'threads' parameter for the @code{nnmairix} group under cursor,
4710 i.e. if you want see the whole threads of the found messages
4711 (@code{nnmairix-group-toggle-threads-this-group}).
4714 @kindex G b u (Group)
4715 @findex nnmairix-update-database
4716 @vindex nnmairix-mairix-update-options
4717 Calls mairix binary for updating the database
4718 (@code{nnmairix-update-database}). The default parameters are @code{-F}
4719 and @code{-Q} for making this as fast as possible (see variable
4720 @code{nnmairix-mairix-update-options} for defining these default
4724 @kindex G b r (Group)
4725 @findex nnmairix-group-toggle-readmarks-this-group
4726 Keep articles in this @code{nnmairix} group always read or unread, or leave the
4727 marks unchanged (@code{nnmairix-group-toggle-readmarks-this-group}).
4730 @kindex G b d (Group)
4731 @findex nnmairix-group-delete-recreate-this-group
4732 Recreate @code{nnmairix} group on the ``real'' mail back end
4733 (@code{nnmairix-group-delete-recreate-this-group}). You can do this if
4734 you always get wrong article counts with a @code{nnmairix} group.
4737 @kindex G b a (Group)
4738 @findex nnmairix-group-toggle-allowfast-this-group
4739 Toggles the @code{allow-fast} parameters for group under cursor
4740 (@code{nnmairix-group-toggle-allowfast-this-group}). The default
4741 behavior of @code{nnmairix} is to do a mairix search every time you
4742 update or enter the group. With the @code{allow-fast} parameter set,
4743 mairix will only be called when you explicitly update the group, but not
4744 upon entering. This makes entering the group faster, but it may also
4745 lead to dangling symlinks if something changed between updating and
4746 entering the group which is not yet in the mairix database.
4749 @kindex G b p (Group)
4750 @findex nnmairix-group-toggle-propmarks-this-group
4751 Toggle marks propagation for this group
4752 (@code{nnmairix-group-toggle-propmarks-this-group}). (@pxref{Propagating
4756 @kindex G b o (Group)
4757 @findex nnmairix-propagate-marks
4758 Manually propagate marks (@code{nnmairix-propagate-marks}); needed only when
4759 @code{nnmairix-propagate-marks-upon-close} is set to @code{nil}.
4768 @kindex $ m (Summary)
4769 @findex nnmairix-widget-search-from-this-article
4770 Allows you to create a mairix query or group based on the current
4771 message using graphical widgets (same as @code{nnmairix-widget-search})
4772 (@code{nnmairix-widget-search-from-this-article}).
4775 @kindex $ g (Summary)
4776 @findex nnmairix-create-search-group-from-message
4777 Interactively creates a new search group with query based on the current
4778 message, but uses the minibuffer instead of graphical widgets
4779 (@code{nnmairix-create-search-group-from-message}).
4782 @kindex $ t (Summary)
4783 @findex nnmairix-search-thread-this-article
4784 Searches thread for the current article
4785 (@code{nnmairix-search-thread-this-article}). This is effectively a
4786 shortcut for calling @code{nnmairix-search} with @samp{m:msgid} of the
4787 current article and enabled threads.
4790 @kindex $ f (Summary)
4791 @findex nnmairix-search-from-this-article
4792 Searches all messages from sender of the current article
4793 (@code{nnmairix-search-from-this-article}). This is a shortcut for
4794 calling @code{nnmairix-search} with @samp{f:From}.
4797 @kindex $ o (Summary)
4798 @findex nnmairix-goto-original-article
4799 (Only in @code{nnmairix} groups!) Tries determine the group this article
4800 originally came from and displays the article in this group, so that
4801 e.g. replying to this article the correct posting styles/group
4802 parameters are applied (@code{nnmairix-goto-original-article}). This
4803 function will use the registry if available, but can also parse the
4804 article file name as a fallback method.
4807 @kindex $ u (Summary)
4808 @findex nnmairix-remove-tick-mark-original-article
4809 Remove possibly existing tick mark from original article
4810 (@code{nnmairix-remove-tick-mark-original-article}). (@pxref{nnmairix
4815 @node Propagating marks
4816 @subsubsection Propagating marks
4818 First of: you really need a patched mairix binary for using the marks
4819 propagation feature efficiently. Otherwise, you would have to update
4820 the mairix database all the time. You can get the patch at
4822 @uref{http://www.randomsample.de/mairix-maildir-patch.tar}
4824 You need the mairix v0.21 source code for this patch; everything else
4825 is explained in the accompanied readme file. If you don't want to use
4826 marks propagation, you don't have to apply these patches, but they also
4827 fix some annoyances regarding changing maildir flags, so it might still
4830 With the patched mairix binary, you can use @code{nnmairix} as an
4831 alternative to mail splitting (@pxref{Fancy Mail Splitting}). For
4832 example, instead of splitting all mails from @samp{david@@foobar.com}
4833 into a group, you can simply create a search group with the query
4834 @samp{f:david@@foobar.com}. This is actually what ``smart folders'' are
4835 all about: simply put everything in one mail folder and dynamically
4836 create searches instead of splitting. This is more flexible, since you
4837 can dynamically change your folders any time you want to. This also
4838 implies that you will usually read your mails in the @code{nnmairix}
4839 groups instead of your ``real'' mail groups.
4841 There is one problem, though: say you got a new mail from
4842 @samp{david@@foobar.com}; it will now show up in two groups, the
4843 ``real'' group (your INBOX, for example) and in the @code{nnmairix}
4844 search group (provided you have updated the mairix database). Now you
4845 enter the @code{nnmairix} group and read the mail. The mail will be
4846 marked as read, but only in the @code{nnmairix} group---in the ``real''
4847 mail group it will be still shown as unread.
4849 You could now catch up the mail group (@pxref{Group Data}), but this is
4850 tedious and error prone, since you may overlook mails you don't have
4851 created @code{nnmairix} groups for. Of course, you could first use
4852 @code{nnmairix-goto-original-article} (@pxref{nnmairix keyboard
4853 shortcuts}) and then read the mail in the original group, but that's
4854 even more cumbersome.
4856 Clearly, the easiest way would be if marks could somehow be
4857 automatically set for the original article. This is exactly what
4858 @emph{marks propagation} is about.
4860 Marks propagation is deactivated by default. You can activate it for a
4861 certain @code{nnmairix} group with
4862 @code{nnmairix-group-toggle-propmarks-this-group} (bound to @kbd{G b
4863 p}). This function will warn you if you try to use it with your default
4864 search group; the reason is that the default search group is used for
4865 temporary searches, and it's easy to accidentally propagate marks from
4866 this group. However, you can ignore this warning if you really want to.
4868 With marks propagation enabled, all the marks you set in a @code{nnmairix}
4869 group should now be propagated to the original article. For example,
4870 you can now tick an article (by default with @kbd{!}) and this mark should
4871 magically be set for the original article, too.
4873 A few more remarks which you may or may not want to know:
4875 @vindex nnmairix-propagate-marks-upon-close
4876 Marks will not be set immediately, but only upon closing a group. This
4877 not only makes marks propagation faster, it also avoids problems with
4878 dangling symlinks when dealing with maildir files (since changing flags
4879 will change the file name). You can also control when to propagate marks
4880 via @code{nnmairix-propagate-marks-upon-close} (see the doc-string for
4883 Obviously, @code{nnmairix} will have to look up the original group for every
4884 article you want to set marks for. If available, @code{nnmairix} will first use
4885 the registry for determining the original group. The registry is very
4886 fast, hence you should really, really enable the registry when using
4887 marks propagation. If you don't have to worry about RAM and disc space,
4888 set @code{gnus-registry-max-entries} to a large enough value; to be on
4889 the safe side, choose roughly the amount of mails you index with mairix.
4891 @vindex nnmairix-only-use-registry
4892 If you don't want to use the registry or the registry hasn't seen the
4893 original article yet, @code{nnmairix} will use an additional mairix
4894 search for determining the file name of the article. This, of course, is
4895 way slower than the registry---if you set hundreds or even thousands of
4896 marks this way, it might take some time. You can avoid this situation by
4897 setting @code{nnmairix-only-use-registry} to t.
4899 Maybe you also want to propagate marks the other way round, i.e. if you
4900 tick an article in a "real" mail group, you'd like to have the same
4901 article in a @code{nnmairix} group ticked, too. For several good
4902 reasons, this can only be done efficiently if you use maildir. To
4903 immediately contradict myself, let me mention that it WON'T work with
4904 @code{nnmaildir}, since @code{nnmaildir} stores the marks externally and
4905 not in the file name. Therefore, propagating marks to @code{nnmairix}
4906 groups will usually only work if you use an IMAP server which uses
4907 maildir as its file format.
4909 @vindex nnmairix-propagate-marks-to-nnmairix-groups
4910 If you work with this setup, just set
4911 @code{nnmairix-propagate-marks-to-nnmairix-groups} to @code{t} and see what
4912 happens. If you don't like what you see, just set it to @code{nil} again. One
4913 problem might be that you get a wrong number of unread articles; this
4914 usually happens when you delete or expire articles in the original
4915 groups. When this happens, you can recreate the @code{nnmairix} group on the
4916 back end using @kbd{G b d}.
4918 @node nnmairix tips and tricks
4919 @subsubsection nnmairix tips and tricks
4925 @findex nnmairix-update-groups
4926 I put all my important mail groups at group level 1. The mairix groups
4927 have group level 5, so they do not get checked at start up (@pxref{Group
4930 I use the following to check for mails:
4933 (defun my-check-mail-mairix-update (level)
4935 ;; if no prefix given, set level=1
4936 (gnus-group-get-new-news (or level 1))
4937 (nnmairix-update-groups "mairixsearch" t t)
4938 (gnus-group-list-groups))
4940 (define-key gnus-group-mode-map "g" 'my-check-mail-mairix-update)
4943 Instead of @samp{"mairixsearch"} use the name of your @code{nnmairix}
4944 server. See the doc string for @code{nnmairix-update-groups} for
4948 Example: search group for ticked articles
4950 For example, you can create a group for all ticked articles, where the
4951 articles always stay unread:
4953 Hit @kbd{G b g}, enter group name (e.g. @samp{important}), use
4954 @samp{F:f} as query and do not include threads.
4956 Now activate marks propagation for this group by using @kbd{G b p}. Then
4957 activate the always-unread feature by using @kbd{G b r} twice.
4959 So far so good---but how do you remove the tick marks in the @code{nnmairix}
4960 group? There are two options: You may simply use
4961 @code{nnmairix-remove-tick-mark-original-article} (bound to @kbd{$ u}) to remove
4962 tick marks from the original article. The other possibility is to set
4963 @code{nnmairix-propagate-marks-to-nnmairix-groups} to @code{t}, but see the above
4964 comments about this option. If it works for you, the tick marks should
4965 also exist in the @code{nnmairix} group and you can remove them as usual,
4966 e.g. by marking an article as read.
4968 When you have removed a tick mark from the original article, this
4969 article should vanish from the @code{nnmairix} group after you have updated the
4970 mairix database and updated the group. Fortunately, there is a function
4971 for doing exactly that: @code{nnmairix-update-groups}. See the previous code
4972 snippet and the doc string for details.
4975 Dealing with auto-subscription of mail groups
4977 As described before, all @code{nnmairix} groups are in fact stored on
4978 the mail back end in the form @samp{zz_mairix-<NAME>-<NUMBER>}. You can
4979 see them when you enter the back end server in the server buffer. You
4980 should not subscribe these groups! Unfortunately, these groups will
4981 usually get @emph{auto-subscribed} when you use @code{nnmaildir} or
4982 @code{nnml}, i.e. you will suddenly see groups of the form
4983 @samp{zz_mairix*} pop up in your group buffer. If this happens to you,
4984 simply kill these groups with C-k. For avoiding this, turn off
4985 auto-subscription completely by setting the variable
4986 @code{gnus-auto-subscribed-groups} to @code{nil} (@pxref{Filtering New
4987 Groups}), or if you like to keep this feature use the following kludge
4988 for turning it off for all groups beginning with @samp{zz_}:
4991 (setq gnus-auto-subscribed-groups
4992 "^\\(nnml\\|nnfolder\\|nnmbox\\|nnmh\\|nnbabyl\\|nnmaildir\\).*:\\([^z]\\|z$\\|\\z[^z]\\|zz$\\|zz[^_]\\|zz_$\\).*")
4997 @node nnmairix caveats
4998 @subsubsection nnmairix caveats
5002 You can create a secondary @code{nnml} server just for nnmairix, but then
5003 you have to explicitly set the corresponding server variable
5004 @code{nnml-get-new-mail} to @code{nil}. Otherwise, new mail might get
5005 put into this secondary server (and would never show up again). Here's
5006 an example server definition:
5009 (nnml "mairix" (nnml-directory "mairix") (nnml-get-new-mail nil))
5012 (The @code{nnmaildir} back end also has a server variabe
5013 @code{get-new-mail}, but its default value is @code{nil}, so you don't
5014 have to explicitly set it if you use a @code{nnmaildir} server just for
5018 If you use the Gnus registry: don't use the registry with
5019 @code{nnmairix} groups (put them in
5020 @code{gnus-registry-unfollowed-groups}). Be @emph{extra careful} if
5021 you use @code{gnus-registry-split-fancy-with-parent}; mails which are
5022 split into @code{nnmairix} groups are usually gone for good as soon as
5023 you check the group for new mail (yes, it has happened to me...).
5026 Therefore: @emph{Never ever} put ``real'' mails into @code{nnmairix}
5027 groups (you shouldn't be able to, anyway).
5030 If you use the Gnus agent (@pxref{Gnus Unplugged}): don't agentize
5031 @code{nnmairix} groups (though I have no idea what happens if you do).
5034 mairix does only support us-ascii characters.
5037 @code{nnmairix} uses a rather brute force method to force Gnus to
5038 completely reread the group on the mail back end after mairix was
5039 called---it simply deletes and re-creates the group on the mail
5040 back end. So far, this has worked for me without any problems, and I
5041 don't see how @code{nnmairix} could delete other mail groups than its
5042 own, but anyway: you really should have a backup of your mail
5046 All necessary information is stored in the group parameters
5047 (@pxref{Group Parameters}). This has the advantage that no active file
5048 is needed, but also implies that when you kill a @code{nnmairix} group,
5049 it is gone for good.
5052 @findex nnmairix-purge-old-groups
5053 If you create and kill a lot of @code{nnmairix} groups, the
5054 ``zz_mairix-*'' groups will accumulate on the mail back end server. To
5055 delete old groups which are no longer needed, call
5056 @code{nnmairix-purge-old-groups}. Note that this assumes that you don't
5057 save any ``real'' mail in folders of the form
5058 @code{zz_mairix-<NAME>-<NUMBER>}. You can change the prefix of
5059 @code{nnmairix} groups by changing the variable
5060 @code{nnmairix-group-prefix}.
5063 The following only applies if you @emph{don't} use the mentioned patch
5064 for mairix (@pxref{Propagating marks}):
5066 A problem can occur when using @code{nnmairix} with maildir folders and
5067 comes with the fact that maildir stores mail flags like @samp{Seen} or
5068 @samp{Replied} by appending chars @samp{S} and @samp{R} to the message
5069 file name, respectively. This implies that currently you would have to
5070 update the mairix database not only when new mail arrives, but also when
5071 mail flags are changing. The same applies to new mails which are indexed
5072 while they are still in the @samp{new} folder but then get moved to
5073 @samp{cur} when Gnus has seen the mail. If you don't update the database
5074 after this has happened, a mairix query can lead to symlinks pointing to
5075 non-existing files. In Gnus, these messages will usually appear with
5076 ``(none)'' entries in the header and can't be accessed. If this happens
5077 to you, using @kbd{G b u} and updating the group will usually fix this.
5081 @node Misc Group Stuff
5082 @section Misc Group Stuff
5085 * Scanning New Messages:: Asking Gnus to see whether new messages have arrived.
5086 * Group Information:: Information and help on groups and Gnus.
5087 * Group Timestamp:: Making Gnus keep track of when you last read a group.
5088 * File Commands:: Reading and writing the Gnus files.
5089 * Sieve Commands:: Managing Sieve scripts.
5096 @cindex keys, reserved for users (Group)
5097 The key @kbd{v} is reserved for users. You can bind it to some
5098 command or better use it as a prefix key. For example:
5101 (define-key gnus-group-mode-map (kbd "v j d")
5104 (gnus-group-jump-to-group "nndraft:drafts")))
5107 On keys reserved for users in Emacs and on keybindings in general
5108 @xref{Keymaps, Keymaps, , emacs, The Emacs Editor}.
5112 @findex gnus-group-enter-server-mode
5113 Enter the server buffer (@code{gnus-group-enter-server-mode}).
5114 @xref{Server Buffer}.
5118 @findex gnus-group-post-news
5119 Start composing a message (a news by default)
5120 (@code{gnus-group-post-news}). If given a prefix, post to the group
5121 under the point. If the prefix is 1, prompt for a group to post to.
5122 Contrary to what the name of this function suggests, the prepared
5123 article might be a mail instead of a news, if a mail group is specified
5124 with the prefix argument. @xref{Composing Messages}.
5128 @findex gnus-group-mail
5129 Mail a message somewhere (@code{gnus-group-mail}). If given a prefix,
5130 use the posting style of the group under the point. If the prefix is 1,
5131 prompt for a group name to find the posting style.
5132 @xref{Composing Messages}.
5136 @findex gnus-group-news
5137 Start composing a news (@code{gnus-group-news}). If given a prefix,
5138 post to the group under the point. If the prefix is 1, prompt
5139 for group to post to. @xref{Composing Messages}.
5141 This function actually prepares a news even when using mail groups.
5142 This is useful for ``posting'' messages to mail groups without actually
5143 sending them over the network: they're just saved directly to the group
5144 in question. The corresponding back end must have a request-post method
5145 for this to work though.
5149 @findex gnus-group-compact-group
5151 Compact the group under point (@code{gnus-group-compact-group}).
5152 Currently implemented only in nnml (@pxref{Mail Spool}). This removes
5153 gaps between article numbers, hence getting a correct total article
5158 Variables for the group buffer:
5162 @item gnus-group-mode-hook
5163 @vindex gnus-group-mode-hook
5164 is called after the group buffer has been
5167 @item gnus-group-prepare-hook
5168 @vindex gnus-group-prepare-hook
5169 is called after the group buffer is
5170 generated. It may be used to modify the buffer in some strange,
5173 @item gnus-group-prepared-hook
5174 @vindex gnus-group-prepare-hook
5175 is called as the very last thing after the group buffer has been
5176 generated. It may be used to move point around, for instance.
5178 @item gnus-permanently-visible-groups
5179 @vindex gnus-permanently-visible-groups
5180 Groups matching this regexp will always be listed in the group buffer,
5181 whether they are empty or not.
5185 @node Scanning New Messages
5186 @subsection Scanning New Messages
5187 @cindex new messages
5188 @cindex scanning new news
5194 @findex gnus-group-get-new-news
5195 @c @icon{gnus-group-get-new-news}
5196 Check the server(s) for new articles. If the numerical prefix is used,
5197 this command will check only groups of level @var{arg} and lower
5198 (@code{gnus-group-get-new-news}). If given a non-numerical prefix, this
5199 command will force a total re-reading of the active file(s) from the
5204 @findex gnus-group-get-new-news-this-group
5205 @vindex gnus-goto-next-group-when-activating
5206 @c @icon{gnus-group-get-new-news-this-group}
5207 Check whether new articles have arrived in the current group
5208 (@code{gnus-group-get-new-news-this-group}).
5209 @code{gnus-goto-next-group-when-activating} says whether this command is
5210 to move point to the next group or not. It is @code{t} by default.
5212 @findex gnus-activate-all-groups
5213 @cindex activating groups
5215 @kindex C-c M-g (Group)
5216 Activate absolutely all groups (@code{gnus-activate-all-groups}).
5221 @findex gnus-group-restart
5222 Restart Gnus (@code{gnus-group-restart}). This saves the @file{.newsrc}
5223 file(s), closes the connection to all servers, clears up all run-time
5224 Gnus variables, and then starts Gnus all over again.
5228 @vindex gnus-get-new-news-hook
5229 @code{gnus-get-new-news-hook} is run just before checking for new news.
5231 @vindex gnus-after-getting-new-news-hook
5232 @code{gnus-after-getting-new-news-hook} is run after checking for new
5236 @node Group Information
5237 @subsection Group Information
5238 @cindex group information
5239 @cindex information on groups
5246 @findex gnus-group-fetch-faq
5247 @vindex gnus-group-faq-directory
5250 Try to fetch the @acronym{FAQ} for the current group
5251 (@code{gnus-group-fetch-faq}). Gnus will try to get the @acronym{FAQ}
5252 from @code{gnus-group-faq-directory}, which is usually a directory on
5253 a remote machine. This variable can also be a list of directories.
5254 In that case, giving a prefix to this command will allow you to choose
5255 between the various sites. @code{ange-ftp} (or @code{efs}) will be
5256 used for fetching the file.
5258 If fetching from the first site is unsuccessful, Gnus will attempt to go
5259 through @code{gnus-group-faq-directory} and try to open them one by one.
5263 @findex gnus-group-fetch-charter
5264 @vindex gnus-group-charter-alist
5266 Try to open the charter for the current group in a web browser
5267 (@code{gnus-group-fetch-charter}). Query for a group if given a
5270 Gnus will use @code{gnus-group-charter-alist} to find the location of
5271 the charter. If no location is known, Gnus will fetch the control
5272 messages for the group, which in some cases includes the charter.
5276 @findex gnus-group-fetch-control
5277 @vindex gnus-group-fetch-control-use-browse-url
5278 @cindex control message
5279 Fetch the control messages for the group from the archive at
5280 @code{ftp.isc.org} (@code{gnus-group-fetch-control}). Query for a
5281 group if given a prefix argument.
5283 If @code{gnus-group-fetch-control-use-browse-url} is non-@code{nil},
5284 Gnus will open the control messages in a browser using
5285 @code{browse-url}. Otherwise they are fetched using @code{ange-ftp}
5286 and displayed in an ephemeral group.
5288 Note that the control messages are compressed. To use this command
5289 you need to turn on @code{auto-compression-mode} (@pxref{Compressed
5290 Files, ,Compressed Files, emacs, The Emacs Manual}).
5294 @c @icon{gnus-group-describe-group}
5296 @kindex C-c C-d (Group)
5297 @cindex describing groups
5298 @cindex group description
5299 @findex gnus-group-describe-group
5300 Describe the current group (@code{gnus-group-describe-group}). If given
5301 a prefix, force Gnus to re-read the description from the server.
5305 @findex gnus-group-describe-all-groups
5306 Describe all groups (@code{gnus-group-describe-all-groups}). If given a
5307 prefix, force Gnus to re-read the description file from the server.
5314 @findex gnus-version
5315 Display current Gnus version numbers (@code{gnus-version}).
5319 @findex gnus-group-describe-briefly
5320 Give a very short help message (@code{gnus-group-describe-briefly}).
5323 @kindex C-c C-i (Group)
5326 @findex gnus-info-find-node
5327 Go to the Gnus info node (@code{gnus-info-find-node}).
5331 @node Group Timestamp
5332 @subsection Group Timestamp
5334 @cindex group timestamps
5336 It can be convenient to let Gnus keep track of when you last read a
5337 group. To set the ball rolling, you should add
5338 @code{gnus-group-set-timestamp} to @code{gnus-select-group-hook}:
5341 (add-hook 'gnus-select-group-hook 'gnus-group-set-timestamp)
5344 After doing this, each time you enter a group, it'll be recorded.
5346 This information can be displayed in various ways---the easiest is to
5347 use the @samp{%d} spec in the group line format:
5350 (setq gnus-group-line-format
5351 "%M\%S\%p\%P\%5y: %(%-40,40g%) %d\n")
5354 This will result in lines looking like:
5357 * 0: mail.ding 19961002T012943
5358 0: custom 19961002T012713
5361 As you can see, the date is displayed in compact ISO 8601 format. This
5362 may be a bit too much, so to just display the date, you could say
5366 (setq gnus-group-line-format
5367 "%M\%S\%p\%P\%5y: %(%-40,40g%) %6,6~(cut 2)d\n")
5370 If you would like greater control of the time format, you can use a
5371 user-defined format spec. Something like the following should do the
5375 (setq gnus-group-line-format
5376 "%M\%S\%p\%P\%5y: %(%-40,40g%) %ud\n")
5377 (defun gnus-user-format-function-d (headers)
5378 (let ((time (gnus-group-timestamp gnus-tmp-group)))
5380 (format-time-string "%b %d %H:%M" time)
5386 @subsection File Commands
5387 @cindex file commands
5393 @findex gnus-group-read-init-file
5394 @vindex gnus-init-file
5395 @cindex reading init file
5396 Re-read the init file (@code{gnus-init-file}, which defaults to
5397 @file{~/.gnus.el}) (@code{gnus-group-read-init-file}).
5401 @findex gnus-group-save-newsrc
5402 @cindex saving .newsrc
5403 Save the @file{.newsrc.eld} file (and @file{.newsrc} if wanted)
5404 (@code{gnus-group-save-newsrc}). If given a prefix, force saving the
5405 file(s) whether Gnus thinks it is necessary or not.
5408 @c @kindex Z (Group)
5409 @c @findex gnus-group-clear-dribble
5410 @c Clear the dribble buffer (@code{gnus-group-clear-dribble}).
5415 @node Sieve Commands
5416 @subsection Sieve Commands
5417 @cindex group sieve commands
5419 Sieve is a server-side mail filtering language. In Gnus you can use
5420 the @code{sieve} group parameter (@pxref{Group Parameters}) to specify
5421 sieve rules that should apply to each group. Gnus provides two
5422 commands to translate all these group parameters into a proper Sieve
5423 script that can be transfered to the server somehow.
5425 @vindex gnus-sieve-file
5426 @vindex gnus-sieve-region-start
5427 @vindex gnus-sieve-region-end
5428 The generated Sieve script is placed in @code{gnus-sieve-file} (by
5429 default @file{~/.sieve}). The Sieve code that Gnus generate is placed
5430 between two delimiters, @code{gnus-sieve-region-start} and
5431 @code{gnus-sieve-region-end}, so you may write additional Sieve code
5432 outside these delimiters that will not be removed the next time you
5433 regenerate the Sieve script.
5435 @vindex gnus-sieve-crosspost
5436 The variable @code{gnus-sieve-crosspost} controls how the Sieve script
5437 is generated. If it is non-@code{nil} (the default) articles is
5438 placed in all groups that have matching rules, otherwise the article
5439 is only placed in the group with the first matching rule. For
5440 example, the group parameter @samp{(sieve address "sender"
5441 "owner-ding@@hpc.uh.edu")} will generate the following piece of Sieve
5442 code if @code{gnus-sieve-crosspost} is @code{nil}. (When
5443 @code{gnus-sieve-crosspost} is non-@code{nil}, it looks the same
5444 except that the line containing the call to @code{stop} is removed.)
5447 if address "sender" "owner-ding@@hpc.uh.edu" @{
5448 fileinto "INBOX.ding";
5453 @xref{Top, Emacs Sieve, Top, sieve, Emacs Sieve}.
5459 @findex gnus-sieve-generate
5460 @vindex gnus-sieve-file
5461 @cindex generating sieve script
5462 Regenerate a Sieve script from the @code{sieve} group parameters and
5463 put you into the @code{gnus-sieve-file} without saving it.
5467 @findex gnus-sieve-update
5468 @vindex gnus-sieve-file
5469 @cindex updating sieve script
5470 Regenerates the Gnus managed part of @code{gnus-sieve-file} using the
5471 @code{sieve} group parameters, save the file and upload it to the
5472 server using the @code{sieveshell} program.
5477 @node Summary Buffer
5478 @chapter Summary Buffer
5479 @cindex summary buffer
5481 A line for each article is displayed in the summary buffer. You can
5482 move around, read articles, post articles and reply to articles.
5484 The most common way to a summary buffer is to select a group from the
5485 group buffer (@pxref{Selecting a Group}).
5487 You can have as many summary buffers open as you wish.
5489 You can customize the Summary Mode tool bar, see @kbd{M-x
5490 customize-apropos RET gnus-summary-tool-bar}. This feature is only
5494 @cindex keys, reserved for users (Summary)
5495 The key @kbd{v} is reserved for users. You can bind it to some
5496 command or better use it as a prefix key. For example:
5498 (define-key gnus-summary-mode-map (kbd "v -") "LrS") ;; lower subthread
5502 * Summary Buffer Format:: Deciding how the summary buffer is to look.
5503 * Summary Maneuvering:: Moving around the summary buffer.
5504 * Choosing Articles:: Reading articles.
5505 * Paging the Article:: Scrolling the current article.
5506 * Reply Followup and Post:: Posting articles.
5507 * Delayed Articles:: Send articles at a later time.
5508 * Marking Articles:: Marking articles as read, expirable, etc.
5509 * Limiting:: You can limit the summary buffer.
5510 * Threading:: How threads are made.
5511 * Sorting the Summary Buffer:: How articles and threads are sorted.
5512 * Asynchronous Fetching:: Gnus might be able to pre-fetch articles.
5513 * Article Caching:: You may store articles in a cache.
5514 * Persistent Articles:: Making articles expiry-resistant.
5515 * Sticky Articles:: Article buffers that are not reused.
5516 * Article Backlog:: Having already read articles hang around.
5517 * Saving Articles:: Ways of customizing article saving.
5518 * Decoding Articles:: Gnus can treat series of (uu)encoded articles.
5519 * Article Treatment:: The article buffer can be mangled at will.
5520 * MIME Commands:: Doing MIMEy things with the articles.
5521 * Charsets:: Character set issues.
5522 * Article Commands:: Doing various things with the article buffer.
5523 * Summary Sorting:: Sorting the summary buffer in various ways.
5524 * Finding the Parent:: No child support? Get the parent.
5525 * Alternative Approaches:: Reading using non-default summaries.
5526 * Tree Display:: A more visual display of threads.
5527 * Mail Group Commands:: Some commands can only be used in mail groups.
5528 * Various Summary Stuff:: What didn't fit anywhere else.
5529 * Exiting the Summary Buffer:: Returning to the Group buffer,
5530 or reselecting the current group.
5531 * Crosspost Handling:: How crossposted articles are dealt with.
5532 * Duplicate Suppression:: An alternative when crosspost handling fails.
5533 * Security:: Decrypt and Verify.
5534 * Mailing List:: Mailing list minor mode.
5538 @node Summary Buffer Format
5539 @section Summary Buffer Format
5540 @cindex summary buffer format
5544 \gnusfigure{The Summary Buffer}{180}{
5545 \put(0,0){\epsfig{figure=ps/summary,width=7.5cm}}
5546 \put(445,0){\makebox(0,0)[br]{\epsfig{figure=ps/summary-article,width=7.5cm}}}
5552 * Summary Buffer Lines:: You can specify how summary lines should look.
5553 * To From Newsgroups:: How to not display your own name.
5554 * Summary Buffer Mode Line:: You can say how the mode line should look.
5555 * Summary Highlighting:: Making the summary buffer all pretty and nice.
5558 @findex mail-extract-address-components
5559 @findex gnus-extract-address-components
5560 @vindex gnus-extract-address-components
5561 Gnus will use the value of the @code{gnus-extract-address-components}
5562 variable as a function for getting the name and address parts of a
5563 @code{From} header. Two pre-defined functions exist:
5564 @code{gnus-extract-address-components}, which is the default, quite
5565 fast, and too simplistic solution; and
5566 @code{mail-extract-address-components}, which works very nicely, but is
5567 slower. The default function will return the wrong answer in 5% of the
5568 cases. If this is unacceptable to you, use the other function instead:
5571 (setq gnus-extract-address-components
5572 'mail-extract-address-components)
5575 @vindex gnus-summary-same-subject
5576 @code{gnus-summary-same-subject} is a string indicating that the current
5577 article has the same subject as the previous. This string will be used
5578 with those specs that require it. The default is @code{""}.
5581 @node Summary Buffer Lines
5582 @subsection Summary Buffer Lines
5584 @vindex gnus-summary-line-format
5585 You can change the format of the lines in the summary buffer by changing
5586 the @code{gnus-summary-line-format} variable. It works along the same
5587 lines as a normal @code{format} string, with some extensions
5588 (@pxref{Formatting Variables}).
5590 There should always be a colon or a point position marker on the line;
5591 the cursor always moves to the point position marker or the colon after
5592 performing an operation. (Of course, Gnus wouldn't be Gnus if it wasn't
5593 possible to change this. Just write a new function
5594 @code{gnus-goto-colon} which does whatever you like with the cursor.)
5595 @xref{Positioning Point}.
5597 The default string is @samp{%U%R%z%I%(%[%4L: %-23,23f%]%) %s\n}.
5599 The following format specification characters and extended format
5600 specification(s) are understood:
5606 Subject string. List identifiers stripped,
5607 @code{gnus-list-identifiers}. @xref{Article Hiding}.
5609 Subject if the article is the root of the thread or the previous article
5610 had a different subject, @code{gnus-summary-same-subject} otherwise.
5611 (@code{gnus-summary-same-subject} defaults to @code{""}.)
5613 Full @code{From} header.
5615 The name (from the @code{From} header).
5617 The name, @code{To} header or the @code{Newsgroups} header (@pxref{To
5620 The name (from the @code{From} header). This differs from the @code{n}
5621 spec in that it uses the function designated by the
5622 @code{gnus-extract-address-components} variable, which is slower, but
5623 may be more thorough.
5625 The address (from the @code{From} header). This works the same way as
5628 Number of lines in the article.
5630 Number of characters in the article. This specifier is not supported
5631 in some methods (like nnfolder).
5633 Pretty-printed version of the number of characters in the article;
5634 for example, @samp{1.2k} or @samp{0.4M}.
5636 Indentation based on thread level (@pxref{Customizing Threading}).
5638 A complex trn-style thread tree, showing response-connecting trace
5639 lines. A thread could be drawn like this:
5652 You can customize the appearance with the following options. Note
5653 that it is possible to make the thread display look really neat by
5654 replacing the default @acronym{ASCII} characters with graphic
5655 line-drawing glyphs.
5657 @item gnus-sum-thread-tree-root
5658 @vindex gnus-sum-thread-tree-root
5659 Used for the root of a thread. If @code{nil}, use subject
5660 instead. The default is @samp{> }.
5662 @item gnus-sum-thread-tree-false-root
5663 @vindex gnus-sum-thread-tree-false-root
5664 Used for the false root of a thread (@pxref{Loose Threads}). If
5665 @code{nil}, use subject instead. The default is @samp{> }.
5667 @item gnus-sum-thread-tree-single-indent
5668 @vindex gnus-sum-thread-tree-single-indent
5669 Used for a thread with just one message. If @code{nil}, use subject
5670 instead. The default is @samp{}.
5672 @item gnus-sum-thread-tree-vertical
5673 @vindex gnus-sum-thread-tree-vertical
5674 Used for drawing a vertical line. The default is @samp{| }.
5676 @item gnus-sum-thread-tree-indent
5677 @vindex gnus-sum-thread-tree-indent
5678 Used for indenting. The default is @samp{ }.
5680 @item gnus-sum-thread-tree-leaf-with-other
5681 @vindex gnus-sum-thread-tree-leaf-with-other
5682 Used for a leaf with brothers. The default is @samp{+-> }.
5684 @item gnus-sum-thread-tree-single-leaf
5685 @vindex gnus-sum-thread-tree-single-leaf
5686 Used for a leaf without brothers. The default is @samp{\-> }
5691 Nothing if the article is a root and lots of spaces if it isn't (it
5692 pushes everything after it off the screen).
5694 Opening bracket, which is normally @samp{[}, but can also be @samp{<}
5695 for adopted articles (@pxref{Customizing Threading}).
5697 Closing bracket, which is normally @samp{]}, but can also be @samp{>}
5698 for adopted articles.
5700 One space for each thread level.
5702 Twenty minus thread level spaces.
5704 Unread. @xref{Read Articles}.
5707 This misleadingly named specifier is the @dfn{secondary mark}. This
5708 mark will say whether the article has been replied to, has been cached,
5709 or has been saved. @xref{Other Marks}.
5712 Score as a number (@pxref{Scoring}).
5714 @vindex gnus-summary-zcore-fuzz
5715 Zcore, @samp{+} if above the default level and @samp{-} if below the
5716 default level. If the difference between
5717 @code{gnus-summary-default-score} and the score is less than
5718 @code{gnus-summary-zcore-fuzz}, this spec will not be used.
5726 The @code{Date} in @code{DD-MMM} format.
5728 The @code{Date} in @var{YYYYMMDD}@code{T}@var{HHMMSS} format.
5734 Number of articles in the current sub-thread. Using this spec will slow
5735 down summary buffer generation somewhat.
5737 An @samp{=} (@code{gnus-not-empty-thread-mark}) will be displayed if the
5738 article has any children.
5744 Desired cursor position (instead of after first colon).
5746 Age sensitive date format. Various date format is defined in
5747 @code{gnus-user-date-format-alist}.
5749 User defined specifier. The next character in the format string should
5750 be a letter. Gnus will call the function
5751 @code{gnus-user-format-function-@var{x}}, where @var{x} is the letter
5752 following @samp{%u}. The function will be passed the current header as
5753 argument. The function should return a string, which will be inserted
5754 into the summary just like information from any other summary specifier.
5757 Text between @samp{%(} and @samp{%)} will be highlighted with
5758 @code{gnus-mouse-face} when the mouse point is placed inside the area.
5759 There can only be one such area.
5761 The @samp{%U} (status), @samp{%R} (replied) and @samp{%z} (zcore) specs
5762 have to be handled with care. For reasons of efficiency, Gnus will
5763 compute what column these characters will end up in, and ``hard-code''
5764 that. This means that it is invalid to have these specs after a
5765 variable-length spec. Well, you might not be arrested, but your summary
5766 buffer will look strange, which is bad enough.
5768 The smart choice is to have these specs as far to the left as possible.
5769 (Isn't that the case with everything, though? But I digress.)
5771 This restriction may disappear in later versions of Gnus.
5774 @node To From Newsgroups
5775 @subsection To From Newsgroups
5779 In some groups (particularly in archive groups), the @code{From} header
5780 isn't very interesting, since all the articles there are written by
5781 you. To display the information in the @code{To} or @code{Newsgroups}
5782 headers instead, you need to decide three things: What information to
5783 gather; where to display it; and when to display it.
5787 @vindex gnus-extra-headers
5788 The reading of extra header information is controlled by the
5789 @code{gnus-extra-headers}. This is a list of header symbols. For
5793 (setq gnus-extra-headers
5794 '(To Newsgroups X-Newsreader))
5797 This will result in Gnus trying to obtain these three headers, and
5798 storing it in header structures for later easy retrieval.
5801 @findex gnus-extra-header
5802 The value of these extra headers can be accessed via the
5803 @code{gnus-extra-header} function. Here's a format line spec that will
5804 access the @code{X-Newsreader} header:
5807 "%~(form (gnus-extra-header 'X-Newsreader))@@"
5811 @vindex gnus-ignored-from-addresses
5812 The @code{gnus-ignored-from-addresses} variable says when the @samp{%f}
5813 summary line spec returns the @code{To}, @code{Newsreader} or
5814 @code{From} header. If this regexp matches the contents of the
5815 @code{From} header, the value of the @code{To} or @code{Newsreader}
5816 headers are used instead.
5818 To distinguish regular articles from those where the @code{From} field
5819 has been swapped, a string is prefixed to the @code{To} or
5820 @code{Newsgroups} header in the summary line. By default the string is
5821 @samp{-> } for @code{To} and @samp{=> } for @code{Newsgroups}, you can
5822 customize these strings with @code{gnus-summary-to-prefix} and
5823 @code{gnus-summary-newsgroup-prefix}.
5827 @vindex nnmail-extra-headers
5828 A related variable is @code{nnmail-extra-headers}, which controls when
5829 to include extra headers when generating overview (@acronym{NOV}) files.
5830 If you have old overview files, you should regenerate them after
5831 changing this variable, by entering the server buffer using @kbd{^},
5832 and then @kbd{g} on the appropriate mail server (e.g. nnml) to cause
5835 @vindex gnus-summary-line-format
5836 You also have to instruct Gnus to display the data by changing the
5837 @code{%n} spec to the @code{%f} spec in the
5838 @code{gnus-summary-line-format} variable.
5840 In summary, you'd typically put something like the following in
5844 (setq gnus-extra-headers
5846 (setq nnmail-extra-headers gnus-extra-headers)
5847 (setq gnus-summary-line-format
5848 "%U%R%z%I%(%[%4L: %-23,23f%]%) %s\n")
5849 (setq gnus-ignored-from-addresses
5853 (The values listed above are the default values in Gnus. Alter them
5856 A note for news server administrators, or for users who wish to try to
5857 convince their news server administrator to provide some additional
5860 The above is mostly useful for mail groups, where you have control over
5861 the @acronym{NOV} files that are created. However, if you can persuade your
5862 nntp admin to add (in the usual implementation, notably INN):
5868 to the end of her @file{overview.fmt} file, then you can use that just
5869 as you would the extra headers from the mail groups.
5872 @node Summary Buffer Mode Line
5873 @subsection Summary Buffer Mode Line
5875 @vindex gnus-summary-mode-line-format
5876 You can also change the format of the summary mode bar (@pxref{Mode Line
5877 Formatting}). Set @code{gnus-summary-mode-line-format} to whatever you
5878 like. The default is @samp{Gnus: %%b [%A] %Z}.
5880 Here are the elements you can play with:
5886 Unprefixed group name.
5888 Current article number.
5890 Current article score.
5894 Number of unread articles in this group.
5896 Number of unread articles in this group that aren't displayed in the
5899 A string with the number of unread and unselected articles represented
5900 either as @samp{<%U(+%e) more>} if there are both unread and unselected
5901 articles, and just as @samp{<%U more>} if there are just unread articles
5902 and no unselected ones.
5904 Shortish group name. For instance, @samp{rec.arts.anime} will be
5905 shortened to @samp{r.a.anime}.
5907 Subject of the current article.
5909 User-defined spec (@pxref{User-Defined Specs}).
5911 Name of the current score file (@pxref{Scoring}).
5913 Number of dormant articles (@pxref{Unread Articles}).
5915 Number of ticked articles (@pxref{Unread Articles}).
5917 Number of articles that have been marked as read in this session.
5919 Number of articles expunged by the score files.
5923 @node Summary Highlighting
5924 @subsection Summary Highlighting
5928 @item gnus-visual-mark-article-hook
5929 @vindex gnus-visual-mark-article-hook
5930 This hook is run after selecting an article. It is meant to be used for
5931 highlighting the article in some way. It is not run if
5932 @code{gnus-visual} is @code{nil}.
5934 @item gnus-summary-update-hook
5935 @vindex gnus-summary-update-hook
5936 This hook is called when a summary line is changed. It is not run if
5937 @code{gnus-visual} is @code{nil}.
5939 @item gnus-summary-selected-face
5940 @vindex gnus-summary-selected-face
5941 This is the face (or @dfn{font} as some people call it) used to
5942 highlight the current article in the summary buffer.
5944 @item gnus-summary-highlight
5945 @vindex gnus-summary-highlight
5946 Summary lines are highlighted according to this variable, which is a
5947 list where the elements are of the format @code{(@var{form}
5948 . @var{face})}. If you would, for instance, like ticked articles to be
5949 italic and high-scored articles to be bold, you could set this variable
5952 (((eq mark gnus-ticked-mark) . italic)
5953 ((> score default) . bold))
5955 As you may have guessed, if @var{form} returns a non-@code{nil} value,
5956 @var{face} will be applied to the line.
5960 @node Summary Maneuvering
5961 @section Summary Maneuvering
5962 @cindex summary movement
5964 All the straight movement commands understand the numeric prefix and
5965 behave pretty much as you'd expect.
5967 None of these commands select articles.
5972 @kindex M-n (Summary)
5973 @kindex G M-n (Summary)
5974 @findex gnus-summary-next-unread-subject
5975 Go to the next summary line of an unread article
5976 (@code{gnus-summary-next-unread-subject}).
5980 @kindex M-p (Summary)
5981 @kindex G M-p (Summary)
5982 @findex gnus-summary-prev-unread-subject
5983 Go to the previous summary line of an unread article
5984 (@code{gnus-summary-prev-unread-subject}).
5987 @kindex G g (Summary)
5988 @findex gnus-summary-goto-subject
5989 Ask for an article number and then go to the summary line of that article
5990 without displaying the article (@code{gnus-summary-goto-subject}).
5993 If Gnus asks you to press a key to confirm going to the next group, you
5994 can use the @kbd{C-n} and @kbd{C-p} keys to move around the group
5995 buffer, searching for the next group to read without actually returning
5996 to the group buffer.
5998 Variables related to summary movement:
6002 @vindex gnus-auto-select-next
6003 @item gnus-auto-select-next
6004 If you issue one of the movement commands (like @kbd{n}) and there are
6005 no more unread articles after the current one, Gnus will offer to go to
6006 the next group. If this variable is @code{t} and the next group is
6007 empty, Gnus will exit summary mode and return to the group buffer. If
6008 this variable is neither @code{t} nor @code{nil}, Gnus will select the
6009 next group with unread articles. As a special case, if this variable
6010 is @code{quietly}, Gnus will select the next group without asking for
6011 confirmation. If this variable is @code{almost-quietly}, the same
6012 will happen only if you are located on the last article in the group.
6013 Finally, if this variable is @code{slightly-quietly}, the @kbd{Z n}
6014 command will go to the next group without confirmation. Also
6015 @pxref{Group Levels}.
6017 @item gnus-auto-select-same
6018 @vindex gnus-auto-select-same
6019 If non-@code{nil}, all the movement commands will try to go to the next
6020 article with the same subject as the current. (@dfn{Same} here might
6021 mean @dfn{roughly equal}. See @code{gnus-summary-gather-subject-limit}
6022 for details (@pxref{Customizing Threading}).) If there are no more
6023 articles with the same subject, go to the first unread article.
6025 This variable is not particularly useful if you use a threaded display.
6027 @item gnus-summary-check-current
6028 @vindex gnus-summary-check-current
6029 If non-@code{nil}, all the ``unread'' movement commands will not proceed
6030 to the next (or previous) article if the current article is unread.
6031 Instead, they will choose the current article.
6033 @item gnus-auto-center-summary
6034 @vindex gnus-auto-center-summary
6035 If non-@code{nil}, Gnus will keep the point in the summary buffer
6036 centered at all times. This makes things quite tidy, but if you have a
6037 slow network connection, or simply do not like this un-Emacsism, you can
6038 set this variable to @code{nil} to get the normal Emacs scrolling
6039 action. This will also inhibit horizontal re-centering of the summary
6040 buffer, which might make it more inconvenient to read extremely long
6043 This variable can also be a number. In that case, center the window at
6044 the given number of lines from the top.
6049 @node Choosing Articles
6050 @section Choosing Articles
6051 @cindex selecting articles
6054 * Choosing Commands:: Commands for choosing articles.
6055 * Choosing Variables:: Variables that influence these commands.
6059 @node Choosing Commands
6060 @subsection Choosing Commands
6062 None of the following movement commands understand the numeric prefix,
6063 and they all select and display an article.
6065 If you want to fetch new articles or redisplay the group, see
6066 @ref{Exiting the Summary Buffer}.
6070 @kindex SPACE (Summary)
6071 @findex gnus-summary-next-page
6072 Select the current article, or, if that one's read already, the next
6073 unread article (@code{gnus-summary-next-page}).
6075 If you have an article window open already and you press @kbd{SPACE}
6076 again, the article will be scrolled. This lets you conveniently
6077 @kbd{SPACE} through an entire newsgroup. @xref{Paging the Article}.
6082 @kindex G n (Summary)
6083 @findex gnus-summary-next-unread-article
6084 @c @icon{gnus-summary-next-unread}
6085 Go to next unread article (@code{gnus-summary-next-unread-article}).
6090 @findex gnus-summary-prev-unread-article
6091 @c @icon{gnus-summary-prev-unread}
6092 Go to previous unread article (@code{gnus-summary-prev-unread-article}).
6097 @kindex G N (Summary)
6098 @findex gnus-summary-next-article
6099 Go to the next article (@code{gnus-summary-next-article}).
6104 @kindex G P (Summary)
6105 @findex gnus-summary-prev-article
6106 Go to the previous article (@code{gnus-summary-prev-article}).
6109 @kindex G C-n (Summary)
6110 @findex gnus-summary-next-same-subject
6111 Go to the next article with the same subject
6112 (@code{gnus-summary-next-same-subject}).
6115 @kindex G C-p (Summary)
6116 @findex gnus-summary-prev-same-subject
6117 Go to the previous article with the same subject
6118 (@code{gnus-summary-prev-same-subject}).
6122 @kindex G f (Summary)
6124 @findex gnus-summary-first-unread-article
6125 Go to the first unread article
6126 (@code{gnus-summary-first-unread-article}).
6130 @kindex G b (Summary)
6132 @findex gnus-summary-best-unread-article
6133 Go to the unread article with the highest score
6134 (@code{gnus-summary-best-unread-article}). If given a prefix argument,
6135 go to the first unread article that has a score over the default score.
6140 @kindex G l (Summary)
6141 @findex gnus-summary-goto-last-article
6142 Go to the previous article read (@code{gnus-summary-goto-last-article}).
6145 @kindex G o (Summary)
6146 @findex gnus-summary-pop-article
6148 @cindex article history
6149 Pop an article off the summary history and go to this article
6150 (@code{gnus-summary-pop-article}). This command differs from the
6151 command above in that you can pop as many previous articles off the
6152 history as you like, while @kbd{l} toggles the two last read articles.
6153 For a somewhat related issue (if you use these commands a lot),
6154 @pxref{Article Backlog}.
6159 @kindex G j (Summary)
6160 @findex gnus-summary-goto-article
6161 Ask for an article number or @code{Message-ID}, and then go to that
6162 article (@code{gnus-summary-goto-article}).
6167 @node Choosing Variables
6168 @subsection Choosing Variables
6170 Some variables relevant for moving and selecting articles:
6173 @item gnus-auto-extend-newsgroup
6174 @vindex gnus-auto-extend-newsgroup
6175 All the movement commands will try to go to the previous (or next)
6176 article, even if that article isn't displayed in the Summary buffer if
6177 this variable is non-@code{nil}. Gnus will then fetch the article from
6178 the server and display it in the article buffer.
6180 @item gnus-select-article-hook
6181 @vindex gnus-select-article-hook
6182 This hook is called whenever an article is selected. The default is
6183 @code{nil}. If you would like each article to be saved in the Agent as
6184 you read it, putting @code{gnus-agent-fetch-selected-article} on this
6187 @item gnus-mark-article-hook
6188 @vindex gnus-mark-article-hook
6189 @findex gnus-summary-mark-unread-as-read
6190 @findex gnus-summary-mark-read-and-unread-as-read
6191 @findex gnus-unread-mark
6192 This hook is called whenever an article is selected. It is intended to
6193 be used for marking articles as read. The default value is
6194 @code{gnus-summary-mark-read-and-unread-as-read}, and will change the
6195 mark of almost any article you read to @code{gnus-read-mark}. The only
6196 articles not affected by this function are ticked, dormant, and
6197 expirable articles. If you'd instead like to just have unread articles
6198 marked as read, you can use @code{gnus-summary-mark-unread-as-read}
6199 instead. It will leave marks like @code{gnus-low-score-mark},
6200 @code{gnus-del-mark} (and so on) alone.
6205 @node Paging the Article
6206 @section Scrolling the Article
6207 @cindex article scrolling
6212 @kindex SPACE (Summary)
6213 @findex gnus-summary-next-page
6214 Pressing @kbd{SPACE} will scroll the current article forward one page,
6215 or, if you have come to the end of the current article, will choose the
6216 next article (@code{gnus-summary-next-page}).
6218 @vindex gnus-article-boring-faces
6219 @vindex gnus-article-skip-boring
6220 If @code{gnus-article-skip-boring} is non-@code{nil} and the rest of
6221 the article consists only of citations and signature, then it will be
6222 skipped; the next article will be shown instead. You can customize
6223 what is considered uninteresting with
6224 @code{gnus-article-boring-faces}. You can manually view the article's
6225 pages, no matter how boring, using @kbd{C-M-v}.
6228 @kindex DEL (Summary)
6229 @findex gnus-summary-prev-page
6230 Scroll the current article back one page (@code{gnus-summary-prev-page}).
6233 @kindex RET (Summary)
6234 @findex gnus-summary-scroll-up
6235 Scroll the current article one line forward
6236 (@code{gnus-summary-scroll-up}).
6239 @kindex M-RET (Summary)
6240 @findex gnus-summary-scroll-down
6241 Scroll the current article one line backward
6242 (@code{gnus-summary-scroll-down}).
6246 @kindex A g (Summary)
6248 @findex gnus-summary-show-article
6249 @vindex gnus-summary-show-article-charset-alist
6250 (Re)fetch the current article (@code{gnus-summary-show-article}). If
6251 given a prefix, fetch the current article, but don't run any of the
6252 article treatment functions. This will give you a ``raw'' article, just
6253 the way it came from the server.
6255 @cindex charset, view article with different charset
6256 If given a numerical prefix, you can do semi-manual charset stuff.
6257 @kbd{C-u 0 g cn-gb-2312 RET} will decode the message as if it were
6258 encoded in the @code{cn-gb-2312} charset. If you have
6261 (setq gnus-summary-show-article-charset-alist
6266 then you can say @kbd{C-u 1 g} to get the same effect.
6271 @kindex A < (Summary)
6272 @findex gnus-summary-beginning-of-article
6273 Scroll to the beginning of the article
6274 (@code{gnus-summary-beginning-of-article}).
6279 @kindex A > (Summary)
6280 @findex gnus-summary-end-of-article
6281 Scroll to the end of the article (@code{gnus-summary-end-of-article}).
6285 @kindex A s (Summary)
6287 @findex gnus-summary-isearch-article
6288 Perform an isearch in the article buffer
6289 (@code{gnus-summary-isearch-article}).
6293 @findex gnus-summary-select-article-buffer
6294 Select the article buffer (@code{gnus-summary-select-article-buffer}).
6299 @node Reply Followup and Post
6300 @section Reply, Followup and Post
6303 * Summary Mail Commands:: Sending mail.
6304 * Summary Post Commands:: Sending news.
6305 * Summary Message Commands:: Other Message-related commands.
6306 * Canceling and Superseding::
6310 @node Summary Mail Commands
6311 @subsection Summary Mail Commands
6313 @cindex composing mail
6315 Commands for composing a mail message:
6321 @kindex S r (Summary)
6323 @findex gnus-summary-reply
6324 @c @icon{gnus-summary-mail-reply}
6325 @c @icon{gnus-summary-reply}
6326 Mail a reply to the author of the current article
6327 (@code{gnus-summary-reply}).
6332 @kindex S R (Summary)
6333 @findex gnus-summary-reply-with-original
6334 @c @icon{gnus-summary-reply-with-original}
6335 Mail a reply to the author of the current article and include the
6336 original message (@code{gnus-summary-reply-with-original}). This
6337 command uses the process/prefix convention.
6340 @kindex S w (Summary)
6341 @findex gnus-summary-wide-reply
6342 Mail a wide reply to the author of the current article
6343 (@code{gnus-summary-wide-reply}). A @dfn{wide reply} is a reply that
6344 goes out to all people listed in the @code{To}, @code{From} (or
6345 @code{Reply-to}) and @code{Cc} headers. If @code{Mail-Followup-To} is
6346 present, that's used instead.
6349 @kindex S W (Summary)
6350 @findex gnus-summary-wide-reply-with-original
6351 Mail a wide reply to the current article and include the original
6352 message (@code{gnus-summary-wide-reply-with-original}). This command uses
6353 the process/prefix convention.
6356 @kindex S v (Summary)
6357 @findex gnus-summary-very-wide-reply
6358 Mail a very wide reply to the author of the current article
6359 (@code{gnus-summary-wide-reply}). A @dfn{very wide reply} is a reply
6360 that goes out to all people listed in the @code{To}, @code{From} (or
6361 @code{Reply-to}) and @code{Cc} headers in all the process/prefixed
6362 articles. This command uses the process/prefix convention.
6365 @kindex S V (Summary)
6366 @findex gnus-summary-very-wide-reply-with-original
6367 Mail a very wide reply to the author of the current article and include the
6368 original message (@code{gnus-summary-very-wide-reply-with-original}). This
6369 command uses the process/prefix convention.
6372 @kindex S B r (Summary)
6373 @findex gnus-summary-reply-broken-reply-to
6374 Mail a reply to the author of the current article but ignore the
6375 @code{Reply-To} field (@code{gnus-summary-reply-broken-reply-to}).
6376 If you need this because a mailing list incorrectly sets a
6377 @code{Reply-To} header pointing to the list, you probably want to set
6378 the @code{broken-reply-to} group parameter instead, so things will work
6379 correctly. @xref{Group Parameters}.
6382 @kindex S B R (Summary)
6383 @findex gnus-summary-reply-broken-reply-to-with-original
6384 Mail a reply to the author of the current article and include the
6385 original message but ignore the @code{Reply-To} field
6386 (@code{gnus-summary-reply-broken-reply-to-with-original}).
6390 @kindex S o m (Summary)
6391 @kindex C-c C-f (Summary)
6392 @findex gnus-summary-mail-forward
6393 @c @icon{gnus-summary-mail-forward}
6394 Forward the current article to some other person
6395 (@code{gnus-summary-mail-forward}). If no prefix is given, the message
6396 is forwarded according to the value of (@code{message-forward-as-mime})
6397 and (@code{message-forward-show-mml}); if the prefix is 1, decode the
6398 message and forward directly inline; if the prefix is 2, forward message
6399 as an rfc822 @acronym{MIME} section; if the prefix is 3, decode message and
6400 forward as an rfc822 @acronym{MIME} section; if the prefix is 4, forward message
6401 directly inline; otherwise, the message is forwarded as no prefix given
6402 but use the flipped value of (@code{message-forward-as-mime}). By
6403 default, the message is decoded and forwarded as an rfc822 @acronym{MIME}
6409 @kindex S m (Summary)
6410 @findex gnus-summary-mail-other-window
6411 @c @icon{gnus-summary-mail-originate}
6412 Prepare a mail (@code{gnus-summary-mail-other-window}). By default, use
6413 the posting style of the current group. If given a prefix, disable that.
6414 If the prefix is 1, prompt for a group name to find the posting style.
6419 @kindex S i (Summary)
6420 @findex gnus-summary-news-other-window
6421 Prepare a news (@code{gnus-summary-news-other-window}). By default,
6422 post to the current group. If given a prefix, disable that. If the
6423 prefix is 1, prompt for a group to post to.
6425 This function actually prepares a news even when using mail groups.
6426 This is useful for ``posting'' messages to mail groups without actually
6427 sending them over the network: they're just saved directly to the group
6428 in question. The corresponding back end must have a request-post method
6429 for this to work though.
6432 @kindex S D b (Summary)
6433 @findex gnus-summary-resend-bounced-mail
6434 @cindex bouncing mail
6435 If you have sent a mail, but the mail was bounced back to you for some
6436 reason (wrong address, transient failure), you can use this command to
6437 resend that bounced mail (@code{gnus-summary-resend-bounced-mail}). You
6438 will be popped into a mail buffer where you can edit the headers before
6439 sending the mail off again. If you give a prefix to this command, and
6440 the bounced mail is a reply to some other mail, Gnus will try to fetch
6441 that mail and display it for easy perusal of its headers. This might
6442 very well fail, though.
6445 @kindex S D r (Summary)
6446 @findex gnus-summary-resend-message
6447 Not to be confused with the previous command,
6448 @code{gnus-summary-resend-message} will prompt you for an address to
6449 send the current message off to, and then send it to that place. The
6450 headers of the message won't be altered---but lots of headers that say
6451 @code{Resent-To}, @code{Resent-From} and so on will be added. This
6452 means that you actually send a mail to someone that has a @code{To}
6453 header that (probably) points to yourself. This will confuse people.
6454 So, natcherly you'll only do that if you're really eVIl.
6456 This command is mainly used if you have several accounts and want to
6457 ship a mail to a different account of yours. (If you're both
6458 @code{root} and @code{postmaster} and get a mail for @code{postmaster}
6459 to the @code{root} account, you may want to resend it to
6460 @code{postmaster}. Ordnung muss sein!
6462 This command understands the process/prefix convention
6463 (@pxref{Process/Prefix}).
6466 @kindex S D e (Summary)
6467 @findex gnus-summary-resend-message-edit
6469 Like the previous command, but will allow you to edit the message as
6470 if it were a new message before resending.
6473 @kindex S O m (Summary)
6474 @findex gnus-uu-digest-mail-forward
6475 Digest the current series (@pxref{Decoding Articles}) and forward the
6476 result using mail (@code{gnus-uu-digest-mail-forward}). This command
6477 uses the process/prefix convention (@pxref{Process/Prefix}).
6480 @kindex S M-c (Summary)
6481 @findex gnus-summary-mail-crosspost-complaint
6482 @cindex crossposting
6483 @cindex excessive crossposting
6484 Send a complaint about excessive crossposting to the author of the
6485 current article (@code{gnus-summary-mail-crosspost-complaint}).
6487 @findex gnus-crosspost-complaint
6488 This command is provided as a way to fight back against the current
6489 crossposting pandemic that's sweeping Usenet. It will compose a reply
6490 using the @code{gnus-crosspost-complaint} variable as a preamble. This
6491 command understands the process/prefix convention
6492 (@pxref{Process/Prefix}) and will prompt you before sending each mail.
6496 Also @xref{Header Commands, ,Header Commands, message, The Message
6497 Manual}, for more information.
6500 @node Summary Post Commands
6501 @subsection Summary Post Commands
6503 @cindex composing news
6505 Commands for posting a news article:
6511 @kindex S p (Summary)
6512 @findex gnus-summary-post-news
6513 @c @icon{gnus-summary-post-news}
6514 Prepare for posting an article (@code{gnus-summary-post-news}). By
6515 default, post to the current group. If given a prefix, disable that.
6516 If the prefix is 1, prompt for another group instead.
6521 @kindex S f (Summary)
6522 @findex gnus-summary-followup
6523 @c @icon{gnus-summary-followup}
6524 Post a followup to the current article (@code{gnus-summary-followup}).
6528 @kindex S F (Summary)
6530 @c @icon{gnus-summary-followup-with-original}
6531 @findex gnus-summary-followup-with-original
6532 Post a followup to the current article and include the original message
6533 (@code{gnus-summary-followup-with-original}). This command uses the
6534 process/prefix convention.
6537 @kindex S n (Summary)
6538 @findex gnus-summary-followup-to-mail
6539 Post a followup to the current article via news, even if you got the
6540 message through mail (@code{gnus-summary-followup-to-mail}).
6543 @kindex S N (Summary)
6544 @findex gnus-summary-followup-to-mail-with-original
6545 Post a followup to the current article via news, even if you got the
6546 message through mail and include the original message
6547 (@code{gnus-summary-followup-to-mail-with-original}). This command uses
6548 the process/prefix convention.
6551 @kindex S o p (Summary)
6552 @findex gnus-summary-post-forward
6553 Forward the current article to a newsgroup
6554 (@code{gnus-summary-post-forward}).
6555 If no prefix is given, the message is forwarded according to the value
6556 of (@code{message-forward-as-mime}) and
6557 (@code{message-forward-show-mml}); if the prefix is 1, decode the
6558 message and forward directly inline; if the prefix is 2, forward message
6559 as an rfc822 @acronym{MIME} section; if the prefix is 3, decode message and
6560 forward as an rfc822 @acronym{MIME} section; if the prefix is 4, forward message
6561 directly inline; otherwise, the message is forwarded as no prefix given
6562 but use the flipped value of (@code{message-forward-as-mime}). By
6563 default, the message is decoded and forwarded as an rfc822 @acronym{MIME} section.
6566 @kindex S O p (Summary)
6567 @findex gnus-uu-digest-post-forward
6569 @cindex making digests
6570 Digest the current series and forward the result to a newsgroup
6571 (@code{gnus-uu-digest-post-forward}). This command uses the
6572 process/prefix convention.
6575 @kindex S u (Summary)
6576 @findex gnus-uu-post-news
6577 @c @icon{gnus-uu-post-news}
6578 Uuencode a file, split it into parts, and post it as a series
6579 (@code{gnus-uu-post-news}). (@pxref{Uuencoding and Posting}).
6582 Also @xref{Header Commands, ,Header Commands, message, The Message
6583 Manual}, for more information.
6586 @node Summary Message Commands
6587 @subsection Summary Message Commands
6591 @kindex S y (Summary)
6592 @findex gnus-summary-yank-message
6593 Yank the current article into an already existing Message composition
6594 buffer (@code{gnus-summary-yank-message}). This command prompts for
6595 what message buffer you want to yank into, and understands the
6596 process/prefix convention (@pxref{Process/Prefix}).
6601 @node Canceling and Superseding
6602 @subsection Canceling Articles
6603 @cindex canceling articles
6604 @cindex superseding articles
6606 Have you ever written something, and then decided that you really,
6607 really, really wish you hadn't posted that?
6609 Well, you can't cancel mail, but you can cancel posts.
6611 @findex gnus-summary-cancel-article
6613 @c @icon{gnus-summary-cancel-article}
6614 Find the article you wish to cancel (you can only cancel your own
6615 articles, so don't try any funny stuff). Then press @kbd{C} or @kbd{S
6616 c} (@code{gnus-summary-cancel-article}). Your article will be
6617 canceled---machines all over the world will be deleting your article.
6618 This command uses the process/prefix convention (@pxref{Process/Prefix}).
6620 Be aware, however, that not all sites honor cancels, so your article may
6621 live on here and there, while most sites will delete the article in
6624 Gnus will use the ``current'' select method when canceling. If you
6625 want to use the standard posting method, use the @samp{a} symbolic
6626 prefix (@pxref{Symbolic Prefixes}).
6628 Gnus ensures that only you can cancel your own messages using a
6629 @code{Cancel-Lock} header (@pxref{Canceling News, Canceling News, ,
6630 message, Message Manual}).
6632 If you discover that you have made some mistakes and want to do some
6633 corrections, you can post a @dfn{superseding} article that will replace
6634 your original article.
6636 @findex gnus-summary-supersede-article
6638 Go to the original article and press @kbd{S s}
6639 (@code{gnus-summary-supersede-article}). You will be put in a buffer
6640 where you can edit the article all you want before sending it off the
6643 The same goes for superseding as for canceling, only more so: Some
6644 sites do not honor superseding. On those sites, it will appear that you
6645 have posted almost the same article twice.
6647 If you have just posted the article, and change your mind right away,
6648 there is a trick you can use to cancel/supersede the article without
6649 waiting for the article to appear on your site first. You simply return
6650 to the post buffer (which is called @code{*sent ...*}). There you will
6651 find the article you just posted, with all the headers intact. Change
6652 the @code{Message-ID} header to a @code{Cancel} or @code{Supersedes}
6653 header by substituting one of those words for the word
6654 @code{Message-ID}. Then just press @kbd{C-c C-c} to send the article as
6655 you would do normally. The previous article will be
6656 canceled/superseded.
6658 Just remember, kids: There is no 'c' in 'supersede'.
6660 @node Delayed Articles
6661 @section Delayed Articles
6662 @cindex delayed sending
6663 @cindex send delayed
6665 Sometimes, you might wish to delay the sending of a message. For
6666 example, you might wish to arrange for a message to turn up just in time
6667 to remind your about the birthday of your Significant Other. For this,
6668 there is the @code{gnus-delay} package. Setup is simple:
6671 (gnus-delay-initialize)
6674 @findex gnus-delay-article
6675 Normally, to send a message you use the @kbd{C-c C-c} command from
6676 Message mode. To delay a message, use @kbd{C-c C-j}
6677 (@code{gnus-delay-article}) instead. This will ask you for how long the
6678 message should be delayed. Possible answers are:
6682 A time span. Consists of an integer and a letter. For example,
6683 @code{42d} means to delay for 42 days. Available letters are @code{m}
6684 (minutes), @code{h} (hours), @code{d} (days), @code{w} (weeks), @code{M}
6685 (months) and @code{Y} (years).
6688 A specific date. Looks like @code{YYYY-MM-DD}. The message will be
6689 delayed until that day, at a specific time (eight o'clock by default).
6690 See also @code{gnus-delay-default-hour}.
6693 A specific time of day. Given in @code{hh:mm} format, 24h, no am/pm
6694 stuff. The deadline will be at that time today, except if that time has
6695 already passed, then it's at the given time tomorrow. So if it's ten
6696 o'clock in the morning and you specify @code{11:15}, then the deadline
6697 is one hour and fifteen minutes hence. But if you specify @code{9:20},
6698 that means a time tomorrow.
6701 The action of the @code{gnus-delay-article} command is influenced by a
6702 couple of variables:
6705 @item gnus-delay-default-hour
6706 @vindex gnus-delay-default-hour
6707 When you specify a specific date, the message will be due on that hour
6708 on the given date. Possible values are integers 0 through 23.
6710 @item gnus-delay-default-delay
6711 @vindex gnus-delay-default-delay
6712 This is a string and gives the default delay. It can be of any of the
6713 formats described above.
6715 @item gnus-delay-group
6716 @vindex gnus-delay-group
6717 Delayed articles will be kept in this group on the drafts server until
6718 they are due. You probably don't need to change this. The default
6719 value is @code{"delayed"}.
6721 @item gnus-delay-header
6722 @vindex gnus-delay-header
6723 The deadline for each article will be stored in a header. This variable
6724 is a string and gives the header name. You probably don't need to
6725 change this. The default value is @code{"X-Gnus-Delayed"}.
6728 The way delaying works is like this: when you use the
6729 @code{gnus-delay-article} command, you give a certain delay. Gnus
6730 calculates the deadline of the message and stores it in the
6731 @code{X-Gnus-Delayed} header and puts the message in the
6732 @code{nndraft:delayed} group.
6734 @findex gnus-delay-send-queue
6735 And whenever you get new news, Gnus looks through the group for articles
6736 which are due and sends them. It uses the @code{gnus-delay-send-queue}
6737 function for this. By default, this function is added to the hook
6738 @code{gnus-get-new-news-hook}. But of course, you can change this.
6739 Maybe you want to use the demon to send drafts? Just tell the demon to
6740 execute the @code{gnus-delay-send-queue} function.
6743 @item gnus-delay-initialize
6744 @findex gnus-delay-initialize
6745 By default, this function installs @code{gnus-delay-send-queue} in
6746 @code{gnus-get-new-news-hook}. But it accepts the optional second
6747 argument @code{no-check}. If it is non-@code{nil},
6748 @code{gnus-get-new-news-hook} is not changed. The optional first
6749 argument is ignored.
6751 For example, @code{(gnus-delay-initialize nil t)} means to do nothing.
6752 Presumably, you want to use the demon for sending due delayed articles.
6753 Just don't forget to set that up :-)
6757 @node Marking Articles
6758 @section Marking Articles
6759 @cindex article marking
6760 @cindex article ticking
6763 There are several marks you can set on an article.
6765 You have marks that decide the @dfn{readedness} (whoo, neato-keano
6766 neologism ohoy!) of the article. Alphabetic marks generally mean
6767 @dfn{read}, while non-alphabetic characters generally mean @dfn{unread}.
6769 In addition, you also have marks that do not affect readedness.
6772 There's a plethora of commands for manipulating these marks.
6776 * Unread Articles:: Marks for unread articles.
6777 * Read Articles:: Marks for read articles.
6778 * Other Marks:: Marks that do not affect readedness.
6779 * Setting Marks:: How to set and remove marks.
6780 * Generic Marking Commands:: How to customize the marking.
6781 * Setting Process Marks:: How to mark articles for later processing.
6785 @node Unread Articles
6786 @subsection Unread Articles
6788 The following marks mark articles as (kinda) unread, in one form or
6793 @vindex gnus-ticked-mark
6794 Marked as ticked (@code{gnus-ticked-mark}).
6796 @dfn{Ticked articles} are articles that will remain visible always. If
6797 you see an article that you find interesting, or you want to put off
6798 reading it, or replying to it, until sometime later, you'd typically
6799 tick it. However, articles can be expired (from news servers by the
6800 news server software, Gnus itself never expires ticked messages), so if
6801 you want to keep an article forever, you'll have to make it persistent
6802 (@pxref{Persistent Articles}).
6805 @vindex gnus-dormant-mark
6806 Marked as dormant (@code{gnus-dormant-mark}).
6808 @dfn{Dormant articles} will only appear in the summary buffer if there
6809 are followups to it. If you want to see them even if they don't have
6810 followups, you can use the @kbd{/ D} command (@pxref{Limiting}).
6811 Otherwise (except for the visibility issue), they are just like ticked
6815 @vindex gnus-unread-mark
6816 Marked as unread (@code{gnus-unread-mark}).
6818 @dfn{Unread articles} are articles that haven't been read at all yet.
6823 @subsection Read Articles
6824 @cindex expirable mark
6826 All the following marks mark articles as read.
6831 @vindex gnus-del-mark
6832 These are articles that the user has marked as read with the @kbd{d}
6833 command manually, more or less (@code{gnus-del-mark}).
6836 @vindex gnus-read-mark
6837 Articles that have actually been read (@code{gnus-read-mark}).
6840 @vindex gnus-ancient-mark
6841 Articles that were marked as read in previous sessions and are now
6842 @dfn{old} (@code{gnus-ancient-mark}).
6845 @vindex gnus-killed-mark
6846 Marked as killed (@code{gnus-killed-mark}).
6849 @vindex gnus-kill-file-mark
6850 Marked as killed by kill files (@code{gnus-kill-file-mark}).
6853 @vindex gnus-low-score-mark
6854 Marked as read by having too low a score (@code{gnus-low-score-mark}).
6857 @vindex gnus-catchup-mark
6858 Marked as read by a catchup (@code{gnus-catchup-mark}).
6861 @vindex gnus-canceled-mark
6862 Canceled article (@code{gnus-canceled-mark})
6865 @vindex gnus-souped-mark
6866 @sc{soup}ed article (@code{gnus-souped-mark}). @xref{SOUP}.
6869 @vindex gnus-sparse-mark
6870 Sparsely reffed article (@code{gnus-sparse-mark}). @xref{Customizing
6874 @vindex gnus-duplicate-mark
6875 Article marked as read by duplicate suppression
6876 (@code{gnus-duplicate-mark}). @xref{Duplicate Suppression}.
6880 All these marks just mean that the article is marked as read, really.
6881 They are interpreted differently when doing adaptive scoring, though.
6883 One more special mark, though:
6887 @vindex gnus-expirable-mark
6888 Marked as expirable (@code{gnus-expirable-mark}).
6890 Marking articles as @dfn{expirable} (or have them marked as such
6891 automatically) doesn't make much sense in normal groups---a user doesn't
6892 control expiring of news articles, but in mail groups, for instance,
6893 articles marked as @dfn{expirable} can be deleted by Gnus at
6899 @subsection Other Marks
6900 @cindex process mark
6903 There are some marks that have nothing to do with whether the article is
6909 You can set a bookmark in the current article. Say you are reading a
6910 long thesis on cats' urinary tracts, and have to go home for dinner
6911 before you've finished reading the thesis. You can then set a bookmark
6912 in the article, and Gnus will jump to this bookmark the next time it
6913 encounters the article. @xref{Setting Marks}.
6916 @vindex gnus-replied-mark
6917 All articles that you have replied to or made a followup to (i.e., have
6918 answered) will be marked with an @samp{A} in the second column
6919 (@code{gnus-replied-mark}).
6922 @vindex gnus-forwarded-mark
6923 All articles that you have forwarded will be marked with an @samp{F} in
6924 the second column (@code{gnus-forwarded-mark}).
6927 @vindex gnus-cached-mark
6928 Articles stored in the article cache will be marked with an @samp{*} in
6929 the second column (@code{gnus-cached-mark}). @xref{Article Caching}.
6932 @vindex gnus-saved-mark
6933 Articles ``saved'' (in some manner or other; not necessarily
6934 religiously) are marked with an @samp{S} in the second column
6935 (@code{gnus-saved-mark}).
6938 @vindex gnus-recent-mark
6939 Articles that according to the server haven't been shown to the user
6940 before are marked with a @samp{N} in the second column
6941 (@code{gnus-recent-mark}). Note that not all servers support this
6942 mark, in which case it simply never appears. Compare with
6943 @code{gnus-unseen-mark}.
6946 @vindex gnus-unseen-mark
6947 Articles that haven't been seen before in Gnus by the user are marked
6948 with a @samp{.} in the second column (@code{gnus-unseen-mark}).
6949 Compare with @code{gnus-recent-mark}.
6952 @vindex gnus-downloaded-mark
6953 When using the Gnus agent (@pxref{Agent Basics}), articles may be
6954 downloaded for unplugged (offline) viewing. If you are using the
6955 @samp{%O} spec, these articles get the @samp{+} mark in that spec.
6956 (The variable @code{gnus-downloaded-mark} controls which character to
6960 @vindex gnus-undownloaded-mark
6961 When using the Gnus agent (@pxref{Agent Basics}), some articles might
6962 not have been downloaded. Such articles cannot be viewed while you
6963 are unplugged (offline). If you are using the @samp{%O} spec, these
6964 articles get the @samp{-} mark in that spec. (The variable
6965 @code{gnus-undownloaded-mark} controls which character to use.)
6968 @vindex gnus-downloadable-mark
6969 The Gnus agent (@pxref{Agent Basics}) downloads some articles
6970 automatically, but it is also possible to explicitly mark articles for
6971 download, even if they would not be downloaded automatically. Such
6972 explicitly-marked articles get the @samp{%} mark in the first column.
6973 (The variable @code{gnus-downloadable-mark} controls which character to
6977 @vindex gnus-not-empty-thread-mark
6978 @vindex gnus-empty-thread-mark
6979 If the @samp{%e} spec is used, the presence of threads or not will be
6980 marked with @code{gnus-not-empty-thread-mark} and
6981 @code{gnus-empty-thread-mark} in the third column, respectively.
6984 @vindex gnus-process-mark
6985 Finally we have the @dfn{process mark} (@code{gnus-process-mark}). A
6986 variety of commands react to the presence of the process mark. For
6987 instance, @kbd{X u} (@code{gnus-uu-decode-uu}) will uudecode and view
6988 all articles that have been marked with the process mark. Articles
6989 marked with the process mark have a @samp{#} in the second column.
6993 You might have noticed that most of these ``non-readedness'' marks
6994 appear in the second column by default. So if you have a cached, saved,
6995 replied article that you have process-marked, what will that look like?
6997 Nothing much. The precedence rules go as follows: process -> cache ->
6998 replied -> saved. So if the article is in the cache and is replied,
6999 you'll only see the cache mark and not the replied mark.
7003 @subsection Setting Marks
7004 @cindex setting marks
7006 All the marking commands understand the numeric prefix.
7011 @kindex M c (Summary)
7012 @kindex M-u (Summary)
7013 @findex gnus-summary-clear-mark-forward
7014 @cindex mark as unread
7015 Clear all readedness-marks from the current article
7016 (@code{gnus-summary-clear-mark-forward}). In other words, mark the
7022 @kindex M t (Summary)
7023 @findex gnus-summary-tick-article-forward
7024 Tick the current article (@code{gnus-summary-tick-article-forward}).
7025 @xref{Article Caching}.
7030 @kindex M ? (Summary)
7031 @findex gnus-summary-mark-as-dormant
7032 Mark the current article as dormant
7033 (@code{gnus-summary-mark-as-dormant}). @xref{Article Caching}.
7037 @kindex M d (Summary)
7039 @findex gnus-summary-mark-as-read-forward
7040 Mark the current article as read
7041 (@code{gnus-summary-mark-as-read-forward}).
7045 @findex gnus-summary-mark-as-read-backward
7046 Mark the current article as read and move point to the previous line
7047 (@code{gnus-summary-mark-as-read-backward}).
7052 @kindex M k (Summary)
7053 @findex gnus-summary-kill-same-subject-and-select
7054 Mark all articles that have the same subject as the current one as read,
7055 and then select the next unread article
7056 (@code{gnus-summary-kill-same-subject-and-select}).
7060 @kindex M K (Summary)
7061 @kindex C-k (Summary)
7062 @findex gnus-summary-kill-same-subject
7063 Mark all articles that have the same subject as the current one as read
7064 (@code{gnus-summary-kill-same-subject}).
7067 @kindex M C (Summary)
7068 @findex gnus-summary-catchup
7069 @c @icon{gnus-summary-catchup}
7070 Mark all unread articles as read (@code{gnus-summary-catchup}).
7073 @kindex M C-c (Summary)
7074 @findex gnus-summary-catchup-all
7075 Mark all articles in the group as read---even the ticked and dormant
7076 articles (@code{gnus-summary-catchup-all}).
7079 @kindex M H (Summary)
7080 @findex gnus-summary-catchup-to-here
7081 Catchup the current group to point (before the point)
7082 (@code{gnus-summary-catchup-to-here}).
7085 @kindex M h (Summary)
7086 @findex gnus-summary-catchup-from-here
7087 Catchup the current group from point (after the point)
7088 (@code{gnus-summary-catchup-from-here}).
7091 @kindex C-w (Summary)
7092 @findex gnus-summary-mark-region-as-read
7093 Mark all articles between point and mark as read
7094 (@code{gnus-summary-mark-region-as-read}).
7097 @kindex M V k (Summary)
7098 @findex gnus-summary-kill-below
7099 Kill all articles with scores below the default score (or below the
7100 numeric prefix) (@code{gnus-summary-kill-below}).
7104 @kindex M e (Summary)
7106 @findex gnus-summary-mark-as-expirable
7107 Mark the current article as expirable
7108 (@code{gnus-summary-mark-as-expirable}).
7111 @kindex M b (Summary)
7112 @findex gnus-summary-set-bookmark
7113 Set a bookmark in the current article
7114 (@code{gnus-summary-set-bookmark}).
7117 @kindex M B (Summary)
7118 @findex gnus-summary-remove-bookmark
7119 Remove the bookmark from the current article
7120 (@code{gnus-summary-remove-bookmark}).
7123 @kindex M V c (Summary)
7124 @findex gnus-summary-clear-above
7125 Clear all marks from articles with scores over the default score (or
7126 over the numeric prefix) (@code{gnus-summary-clear-above}).
7129 @kindex M V u (Summary)
7130 @findex gnus-summary-tick-above
7131 Tick all articles with scores over the default score (or over the
7132 numeric prefix) (@code{gnus-summary-tick-above}).
7135 @kindex M V m (Summary)
7136 @findex gnus-summary-mark-above
7137 Prompt for a mark, and mark all articles with scores over the default
7138 score (or over the numeric prefix) with this mark
7139 (@code{gnus-summary-clear-above}).
7142 @vindex gnus-summary-goto-unread
7143 The @code{gnus-summary-goto-unread} variable controls what action should
7144 be taken after setting a mark. If non-@code{nil}, point will move to
7145 the next/previous unread article. If @code{nil}, point will just move
7146 one line up or down. As a special case, if this variable is
7147 @code{never}, all the marking commands as well as other commands (like
7148 @kbd{SPACE}) will move to the next article, whether it is unread or not.
7149 The default is @code{t}.
7152 @node Generic Marking Commands
7153 @subsection Generic Marking Commands
7155 Some people would like the command that ticks an article (@kbd{!}) go to
7156 the next article. Others would like it to go to the next unread
7157 article. Yet others would like it to stay on the current article. And
7158 even though I haven't heard of anybody wanting it to go to the
7159 previous (unread) article, I'm sure there are people that want that as
7162 Multiply these five behaviors with five different marking commands, and
7163 you get a potentially complex set of variable to control what each
7166 To sidestep that mess, Gnus provides commands that do all these
7167 different things. They can be found on the @kbd{M M} map in the summary
7168 buffer. Type @kbd{M M C-h} to see them all---there are too many of them
7169 to list in this manual.
7171 While you can use these commands directly, most users would prefer
7172 altering the summary mode keymap. For instance, if you would like the
7173 @kbd{!} command to go to the next article instead of the next unread
7174 article, you could say something like:
7178 (add-hook 'gnus-summary-mode-hook 'my-alter-summary-map)
7179 (defun my-alter-summary-map ()
7180 (local-set-key "!" 'gnus-summary-put-mark-as-ticked-next))
7188 (defun my-alter-summary-map ()
7189 (local-set-key "!" "MM!n"))
7193 @node Setting Process Marks
7194 @subsection Setting Process Marks
7195 @cindex setting process marks
7197 Process marks are displayed as @code{#} in the summary buffer, and are
7198 used for marking articles in such a way that other commands will
7199 process these articles. For instance, if you process mark four
7200 articles and then use the @kbd{*} command, Gnus will enter these four
7201 articles into the cache. For more information,
7202 @pxref{Process/Prefix}.
7209 @kindex M P p (Summary)
7210 @findex gnus-summary-mark-as-processable
7211 Mark the current article with the process mark
7212 (@code{gnus-summary-mark-as-processable}).
7213 @findex gnus-summary-unmark-as-processable
7217 @kindex M P u (Summary)
7218 @kindex M-# (Summary)
7219 Remove the process mark, if any, from the current article
7220 (@code{gnus-summary-unmark-as-processable}).
7223 @kindex M P U (Summary)
7224 @findex gnus-summary-unmark-all-processable
7225 Remove the process mark from all articles
7226 (@code{gnus-summary-unmark-all-processable}).
7229 @kindex M P i (Summary)
7230 @findex gnus-uu-invert-processable
7231 Invert the list of process marked articles
7232 (@code{gnus-uu-invert-processable}).
7235 @kindex M P R (Summary)
7236 @findex gnus-uu-mark-by-regexp
7237 Mark articles that have a @code{Subject} header that matches a regular
7238 expression (@code{gnus-uu-mark-by-regexp}).
7241 @kindex M P G (Summary)
7242 @findex gnus-uu-unmark-by-regexp
7243 Unmark articles that have a @code{Subject} header that matches a regular
7244 expression (@code{gnus-uu-unmark-by-regexp}).
7247 @kindex M P r (Summary)
7248 @findex gnus-uu-mark-region
7249 Mark articles in region (@code{gnus-uu-mark-region}).
7252 @kindex M P g (Summary)
7253 @findex gnus-uu-unmark-region
7254 Unmark articles in region (@code{gnus-uu-unmark-region}).
7257 @kindex M P t (Summary)
7258 @findex gnus-uu-mark-thread
7259 Mark all articles in the current (sub)thread
7260 (@code{gnus-uu-mark-thread}).
7263 @kindex M P T (Summary)
7264 @findex gnus-uu-unmark-thread
7265 Unmark all articles in the current (sub)thread
7266 (@code{gnus-uu-unmark-thread}).
7269 @kindex M P v (Summary)
7270 @findex gnus-uu-mark-over
7271 Mark all articles that have a score above the prefix argument
7272 (@code{gnus-uu-mark-over}).
7275 @kindex M P s (Summary)
7276 @findex gnus-uu-mark-series
7277 Mark all articles in the current series (@code{gnus-uu-mark-series}).
7280 @kindex M P S (Summary)
7281 @findex gnus-uu-mark-sparse
7282 Mark all series that have already had some articles marked
7283 (@code{gnus-uu-mark-sparse}).
7286 @kindex M P a (Summary)
7287 @findex gnus-uu-mark-all
7288 Mark all articles in series order (@code{gnus-uu-mark-all}).
7291 @kindex M P b (Summary)
7292 @findex gnus-uu-mark-buffer
7293 Mark all articles in the buffer in the order they appear
7294 (@code{gnus-uu-mark-buffer}).
7297 @kindex M P k (Summary)
7298 @findex gnus-summary-kill-process-mark
7299 Push the current process mark set onto the stack and unmark all articles
7300 (@code{gnus-summary-kill-process-mark}).
7303 @kindex M P y (Summary)
7304 @findex gnus-summary-yank-process-mark
7305 Pop the previous process mark set from the stack and restore it
7306 (@code{gnus-summary-yank-process-mark}).
7309 @kindex M P w (Summary)
7310 @findex gnus-summary-save-process-mark
7311 Push the current process mark set onto the stack
7312 (@code{gnus-summary-save-process-mark}).
7316 Also see the @kbd{&} command in @ref{Searching for Articles}, for how to
7317 set process marks based on article body contents.
7324 It can be convenient to limit the summary buffer to just show some
7325 subset of the articles currently in the group. The effect most limit
7326 commands have is to remove a few (or many) articles from the summary
7329 Limiting commands work on subsets of the articles already fetched from
7330 the servers. These commands don't query the server for additional
7337 @kindex / / (Summary)
7338 @findex gnus-summary-limit-to-subject
7339 Limit the summary buffer to articles that match some subject
7340 (@code{gnus-summary-limit-to-subject}). If given a prefix, exclude
7344 @kindex / a (Summary)
7345 @findex gnus-summary-limit-to-author
7346 Limit the summary buffer to articles that match some author
7347 (@code{gnus-summary-limit-to-author}). If given a prefix, exclude
7351 @kindex / R (Summary)
7352 @findex gnus-summary-limit-to-recipient
7353 Limit the summary buffer to articles that match some recipient
7354 (@code{gnus-summary-limit-to-recipient}). If given a prefix, exclude
7358 @kindex / A (Summary)
7359 @findex gnus-summary-limit-to-address
7360 Limit the summary buffer to articles in which contents of From, To or Cc
7361 header match a given address (@code{gnus-summary-limit-to-address}). If
7362 given a prefix, exclude matching articles.
7365 @kindex / S (Summary)
7366 @findex gnus-summary-limit-to-singletons
7367 Limit the summary buffer to articles that aren't part of any displayed
7368 threads (@code{gnus-summary-limit-to-singletons}). If given a prefix,
7369 limit to articles that are part of displayed threads.
7372 @kindex / x (Summary)
7373 @findex gnus-summary-limit-to-extra
7374 Limit the summary buffer to articles that match one of the ``extra''
7375 headers (@pxref{To From Newsgroups})
7376 (@code{gnus-summary-limit-to-extra}). If given a prefix, exclude
7381 @kindex / u (Summary)
7383 @findex gnus-summary-limit-to-unread
7384 Limit the summary buffer to articles not marked as read
7385 (@code{gnus-summary-limit-to-unread}). If given a prefix, limit the
7386 buffer to articles strictly unread. This means that ticked and
7387 dormant articles will also be excluded.
7390 @kindex / m (Summary)
7391 @findex gnus-summary-limit-to-marks
7392 Ask for a mark and then limit to all articles that have been marked
7393 with that mark (@code{gnus-summary-limit-to-marks}).
7396 @kindex / t (Summary)
7397 @findex gnus-summary-limit-to-age
7398 Ask for a number and then limit the summary buffer to articles older than (or equal to) that number of days
7399 (@code{gnus-summary-limit-to-age}). If given a prefix, limit to
7400 articles younger than that number of days.
7403 @kindex / n (Summary)
7404 @findex gnus-summary-limit-to-articles
7405 With prefix @samp{n}, limit the summary buffer to the next @samp{n}
7406 articles. If not given a prefix, use the process marked articles
7407 instead. (@code{gnus-summary-limit-to-articles}).
7410 @kindex / w (Summary)
7411 @findex gnus-summary-pop-limit
7412 Pop the previous limit off the stack and restore it
7413 (@code{gnus-summary-pop-limit}). If given a prefix, pop all limits off
7417 @kindex / . (Summary)
7418 @findex gnus-summary-limit-to-unseen
7419 Limit the summary buffer to the unseen articles
7420 (@code{gnus-summary-limit-to-unseen}).
7423 @kindex / v (Summary)
7424 @findex gnus-summary-limit-to-score
7425 Limit the summary buffer to articles that have a score at or above some
7426 score (@code{gnus-summary-limit-to-score}).
7429 @kindex / p (Summary)
7430 @findex gnus-summary-limit-to-display-predicate
7431 Limit the summary buffer to articles that satisfy the @code{display}
7432 group parameter predicate
7433 (@code{gnus-summary-limit-to-display-predicate}). @xref{Group
7434 Parameters}, for more on this predicate.
7437 @kindex / r (Summary)
7438 @findex gnus-summary-limit-to-replied
7439 Limit the summary buffer to replied articles
7440 (@code{gnus-summary-limit-to-replied}). If given a prefix, exclude
7445 @kindex M S (Summary)
7446 @kindex / E (Summary)
7447 @findex gnus-summary-limit-include-expunged
7448 Include all expunged articles in the limit
7449 (@code{gnus-summary-limit-include-expunged}).
7452 @kindex / D (Summary)
7453 @findex gnus-summary-limit-include-dormant
7454 Include all dormant articles in the limit
7455 (@code{gnus-summary-limit-include-dormant}).
7458 @kindex / * (Summary)
7459 @findex gnus-summary-limit-include-cached
7460 Include all cached articles in the limit
7461 (@code{gnus-summary-limit-include-cached}).
7464 @kindex / d (Summary)
7465 @findex gnus-summary-limit-exclude-dormant
7466 Exclude all dormant articles from the limit
7467 (@code{gnus-summary-limit-exclude-dormant}).
7470 @kindex / M (Summary)
7471 @findex gnus-summary-limit-exclude-marks
7472 Exclude all marked articles (@code{gnus-summary-limit-exclude-marks}).
7475 @kindex / T (Summary)
7476 @findex gnus-summary-limit-include-thread
7477 Include all the articles in the current thread in the limit.
7480 @kindex / c (Summary)
7481 @findex gnus-summary-limit-exclude-childless-dormant
7482 Exclude all dormant articles that have no children from the limit@*
7483 (@code{gnus-summary-limit-exclude-childless-dormant}).
7486 @kindex / C (Summary)
7487 @findex gnus-summary-limit-mark-excluded-as-read
7488 Mark all excluded unread articles as read
7489 (@code{gnus-summary-limit-mark-excluded-as-read}). If given a prefix,
7490 also mark excluded ticked and dormant articles as read.
7493 @kindex / b (Summary)
7494 @findex gnus-summary-limit-to-bodies
7495 Limit the summary buffer to articles that have bodies that match a
7496 certain regexp (@code{gnus-summary-limit-to-bodies}). If given a
7497 prefix, reverse the limit. This command is quite slow since it
7498 requires selecting each article to find the matches.
7501 @kindex / h (Summary)
7502 @findex gnus-summary-limit-to-headers
7503 Like the previous command, only limit to headers instead
7504 (@code{gnus-summary-limit-to-headers}).
7509 The following commands aren't limiting commands, but use the @kbd{/}
7514 @kindex / N (Summary)
7515 @findex gnus-summary-insert-new-articles
7516 Insert all new articles in the summary buffer. It scans for new emails
7517 if @var{back-end}@code{-get-new-mail} is non-@code{nil}.
7520 @kindex / o (Summary)
7521 @findex gnus-summary-insert-old-articles
7522 Insert all old articles in the summary buffer. If given a numbered
7523 prefix, fetch this number of articles.
7531 @cindex article threading
7533 Gnus threads articles by default. @dfn{To thread} is to put responses
7534 to articles directly after the articles they respond to---in a
7535 hierarchical fashion.
7537 Threading is done by looking at the @code{References} headers of the
7538 articles. In a perfect world, this would be enough to build pretty
7539 trees, but unfortunately, the @code{References} header is often broken
7540 or simply missing. Weird news propagation exacerbates the problem,
7541 so one has to employ other heuristics to get pleasing results. A
7542 plethora of approaches exists, as detailed in horrible detail in
7543 @ref{Customizing Threading}.
7545 First, a quick overview of the concepts:
7549 The top-most article in a thread; the first article in the thread.
7552 A tree-like article structure.
7555 A small(er) section of this tree-like structure.
7558 Threads often lose their roots due to article expiry, or due to the root
7559 already having been read in a previous session, and not displayed in the
7560 summary buffer. We then typically have many sub-threads that really
7561 belong to one thread, but are without connecting roots. These are
7562 called loose threads.
7564 @item thread gathering
7565 An attempt to gather loose threads into bigger threads.
7567 @item sparse threads
7568 A thread where the missing articles have been ``guessed'' at, and are
7569 displayed as empty lines in the summary buffer.
7575 * Customizing Threading:: Variables you can change to affect the threading.
7576 * Thread Commands:: Thread based commands in the summary buffer.
7580 @node Customizing Threading
7581 @subsection Customizing Threading
7582 @cindex customizing threading
7585 * Loose Threads:: How Gnus gathers loose threads into bigger threads.
7586 * Filling In Threads:: Making the threads displayed look fuller.
7587 * More Threading:: Even more variables for fiddling with threads.
7588 * Low-Level Threading:: You thought it was over@dots{} but you were wrong!
7593 @subsubsection Loose Threads
7596 @cindex loose threads
7599 @item gnus-summary-make-false-root
7600 @vindex gnus-summary-make-false-root
7601 If non-@code{nil}, Gnus will gather all loose subtrees into one big tree
7602 and create a dummy root at the top. (Wait a minute. Root at the top?
7603 Yup.) Loose subtrees occur when the real root has expired, or you've
7604 read or killed the root in a previous session.
7606 When there is no real root of a thread, Gnus will have to fudge
7607 something. This variable says what fudging method Gnus should use.
7608 There are four possible values:
7612 \gnusfigure{The Summary Buffer}{390}{
7613 \put(0,0){\epsfig{figure=ps/summary-adopt,width=7.5cm}}
7614 \put(445,0){\makebox(0,0)[br]{\epsfig{figure=ps/summary-empty,width=7.5cm}}}
7615 \put(0,400){\makebox(0,0)[tl]{\epsfig{figure=ps/summary-none,width=7.5cm}}}
7616 \put(445,400){\makebox(0,0)[tr]{\epsfig{figure=ps/summary-dummy,width=7.5cm}}}
7621 @cindex adopting articles
7626 Gnus will make the first of the orphaned articles the parent. This
7627 parent will adopt all the other articles. The adopted articles will be
7628 marked as such by pointy brackets (@samp{<>}) instead of the standard
7629 square brackets (@samp{[]}). This is the default method.
7632 @vindex gnus-summary-dummy-line-format
7633 @vindex gnus-summary-make-false-root-always
7634 Gnus will create a dummy summary line that will pretend to be the
7635 parent. This dummy line does not correspond to any real article, so
7636 selecting it will just select the first real article after the dummy
7637 article. @code{gnus-summary-dummy-line-format} is used to specify the
7638 format of the dummy roots. It accepts only one format spec: @samp{S},
7639 which is the subject of the article. @xref{Formatting Variables}.
7640 If you want all threads to have a dummy root, even the non-gathered
7641 ones, set @code{gnus-summary-make-false-root-always} to @code{t}.
7644 Gnus won't actually make any article the parent, but simply leave the
7645 subject field of all orphans except the first empty. (Actually, it will
7646 use @code{gnus-summary-same-subject} as the subject (@pxref{Summary
7650 Don't make any article parent at all. Just gather the threads and
7651 display them after one another.
7654 Don't gather loose threads.
7657 @item gnus-summary-gather-subject-limit
7658 @vindex gnus-summary-gather-subject-limit
7659 Loose threads are gathered by comparing subjects of articles. If this
7660 variable is @code{nil}, Gnus requires an exact match between the
7661 subjects of the loose threads before gathering them into one big
7662 super-thread. This might be too strict a requirement, what with the
7663 presence of stupid newsreaders that chop off long subject lines. If
7664 you think so, set this variable to, say, 20 to require that only the
7665 first 20 characters of the subjects have to match. If you set this
7666 variable to a really low number, you'll find that Gnus will gather
7667 everything in sight into one thread, which isn't very helpful.
7669 @cindex fuzzy article gathering
7670 If you set this variable to the special value @code{fuzzy}, Gnus will
7671 use a fuzzy string comparison algorithm on the subjects (@pxref{Fuzzy
7674 @item gnus-simplify-subject-fuzzy-regexp
7675 @vindex gnus-simplify-subject-fuzzy-regexp
7676 This can either be a regular expression or list of regular expressions
7677 that match strings that will be removed from subjects if fuzzy subject
7678 simplification is used.
7680 @item gnus-simplify-ignored-prefixes
7681 @vindex gnus-simplify-ignored-prefixes
7682 If you set @code{gnus-summary-gather-subject-limit} to something as low
7683 as 10, you might consider setting this variable to something sensible:
7685 @c Written by Michael Ernst <mernst@cs.rice.edu>
7687 (setq gnus-simplify-ignored-prefixes
7693 "wanted" "followup" "summary\\( of\\)?"
7694 "help" "query" "problem" "question"
7695 "answer" "reference" "announce"
7696 "How can I" "How to" "Comparison of"
7701 (mapconcat 'identity
7702 '("for" "for reference" "with" "about")
7704 "\\)?\\]?:?[ \t]*"))
7707 All words that match this regexp will be removed before comparing two
7710 @item gnus-simplify-subject-functions
7711 @vindex gnus-simplify-subject-functions
7712 If non-@code{nil}, this variable overrides
7713 @code{gnus-summary-gather-subject-limit}. This variable should be a
7714 list of functions to apply to the @code{Subject} string iteratively to
7715 arrive at the simplified version of the string.
7717 Useful functions to put in this list include:
7720 @item gnus-simplify-subject-re
7721 @findex gnus-simplify-subject-re
7722 Strip the leading @samp{Re:}.
7724 @item gnus-simplify-subject-fuzzy
7725 @findex gnus-simplify-subject-fuzzy
7728 @item gnus-simplify-whitespace
7729 @findex gnus-simplify-whitespace
7730 Remove excessive whitespace.
7732 @item gnus-simplify-all-whitespace
7733 @findex gnus-simplify-all-whitespace
7734 Remove all whitespace.
7737 You may also write your own functions, of course.
7740 @item gnus-summary-gather-exclude-subject
7741 @vindex gnus-summary-gather-exclude-subject
7742 Since loose thread gathering is done on subjects only, that might lead
7743 to many false hits, especially with certain common subjects like
7744 @samp{} and @samp{(none)}. To make the situation slightly better,
7745 you can use the regexp @code{gnus-summary-gather-exclude-subject} to say
7746 what subjects should be excluded from the gathering process.@*
7747 The default is @samp{^ *$\\|^(none)$}.
7749 @item gnus-summary-thread-gathering-function
7750 @vindex gnus-summary-thread-gathering-function
7751 Gnus gathers threads by looking at @code{Subject} headers. This means
7752 that totally unrelated articles may end up in the same ``thread'', which
7753 is confusing. An alternate approach is to look at all the
7754 @code{Message-ID}s in all the @code{References} headers to find matches.
7755 This will ensure that no gathered threads ever include unrelated
7756 articles, but it also means that people who have posted with broken
7757 newsreaders won't be gathered properly. The choice is yours---plague or
7761 @item gnus-gather-threads-by-subject
7762 @findex gnus-gather-threads-by-subject
7763 This function is the default gathering function and looks at
7764 @code{Subject}s exclusively.
7766 @item gnus-gather-threads-by-references
7767 @findex gnus-gather-threads-by-references
7768 This function looks at @code{References} headers exclusively.
7771 If you want to test gathering by @code{References}, you could say
7775 (setq gnus-summary-thread-gathering-function
7776 'gnus-gather-threads-by-references)
7782 @node Filling In Threads
7783 @subsubsection Filling In Threads
7786 @item gnus-fetch-old-headers
7787 @vindex gnus-fetch-old-headers
7788 If non-@code{nil}, Gnus will attempt to build old threads by fetching
7789 more old headers---headers to articles marked as read. If you would
7790 like to display as few summary lines as possible, but still connect as
7791 many loose threads as possible, you should set this variable to
7792 @code{some} or a number. If you set it to a number, no more than that
7793 number of extra old headers will be fetched. In either case, fetching
7794 old headers only works if the back end you are using carries overview
7795 files---this would normally be @code{nntp}, @code{nnspool},
7796 @code{nnml}, and @code{nnmaildir}. Also remember that if the root of
7797 the thread has been expired by the server, there's not much Gnus can
7800 This variable can also be set to @code{invisible}. This won't have any
7801 visible effects, but is useful if you use the @kbd{A T} command a lot
7802 (@pxref{Finding the Parent}).
7804 The server has to support @acronym{NOV} for any of this to work.
7806 @cindex Gmane, gnus-fetch-old-headers
7807 This feature can seriously impact performance it ignores all locally
7808 cached header entries. Setting it to @code{t} for groups for a server
7809 that doesn't expire articles (such as news.gmane.org), leads to very
7810 slow summary generation.
7812 @item gnus-fetch-old-ephemeral-headers
7813 @vindex gnus-fetch-old-ephemeral-headers
7814 Same as @code{gnus-fetch-old-headers}, but only used for ephemeral
7817 @item gnus-build-sparse-threads
7818 @vindex gnus-build-sparse-threads
7819 Fetching old headers can be slow. A low-rent similar effect can be
7820 gotten by setting this variable to @code{some}. Gnus will then look at
7821 the complete @code{References} headers of all articles and try to string
7822 together articles that belong in the same thread. This will leave
7823 @dfn{gaps} in the threading display where Gnus guesses that an article
7824 is missing from the thread. (These gaps appear like normal summary
7825 lines. If you select a gap, Gnus will try to fetch the article in
7826 question.) If this variable is @code{t}, Gnus will display all these
7827 ``gaps'' without regard for whether they are useful for completing the
7828 thread or not. Finally, if this variable is @code{more}, Gnus won't cut
7829 off sparse leaf nodes that don't lead anywhere. This variable is
7830 @code{nil} by default.
7832 @item gnus-read-all-available-headers
7833 @vindex gnus-read-all-available-headers
7834 This is a rather obscure variable that few will find useful. It's
7835 intended for those non-news newsgroups where the back end has to fetch
7836 quite a lot to present the summary buffer, and where it's impossible to
7837 go back to parents of articles. This is mostly the case in the
7838 web-based groups, like the @code{nnultimate} groups.
7840 If you don't use those, then it's safe to leave this as the default
7841 @code{nil}. If you want to use this variable, it should be a regexp
7842 that matches the group name, or @code{t} for all groups.
7847 @node More Threading
7848 @subsubsection More Threading
7851 @item gnus-show-threads
7852 @vindex gnus-show-threads
7853 If this variable is @code{nil}, no threading will be done, and all of
7854 the rest of the variables here will have no effect. Turning threading
7855 off will speed group selection up a bit, but it is sure to make reading
7856 slower and more awkward.
7858 @item gnus-thread-hide-subtree
7859 @vindex gnus-thread-hide-subtree
7860 If non-@code{nil}, all threads will be hidden when the summary buffer is
7863 This can also be a predicate specifier (@pxref{Predicate Specifiers}).
7864 Available predicates are @code{gnus-article-unread-p} and
7865 @code{gnus-article-unseen-p}.
7870 (setq gnus-thread-hide-subtree
7871 '(or gnus-article-unread-p
7872 gnus-article-unseen-p))
7875 (It's a pretty nonsensical example, since all unseen articles are also
7876 unread, but you get my drift.)
7879 @item gnus-thread-expunge-below
7880 @vindex gnus-thread-expunge-below
7881 All threads that have a total score (as defined by
7882 @code{gnus-thread-score-function}) less than this number will be
7883 expunged. This variable is @code{nil} by default, which means that no
7884 threads are expunged.
7886 @item gnus-thread-hide-killed
7887 @vindex gnus-thread-hide-killed
7888 if you kill a thread and this variable is non-@code{nil}, the subtree
7891 @item gnus-thread-ignore-subject
7892 @vindex gnus-thread-ignore-subject
7893 Sometimes somebody changes the subject in the middle of a thread. If
7894 this variable is non-@code{nil}, which is the default, the subject
7895 change is ignored. If it is @code{nil}, a change in the subject will
7896 result in a new thread.
7898 @item gnus-thread-indent-level
7899 @vindex gnus-thread-indent-level
7900 This is a number that says how much each sub-thread should be indented.
7903 @item gnus-sort-gathered-threads-function
7904 @vindex gnus-sort-gathered-threads-function
7905 Sometimes, particularly with mailing lists, the order in which mails
7906 arrive locally is not necessarily the same as the order in which they
7907 arrived on the mailing list. Consequently, when sorting sub-threads
7908 using the default @code{gnus-thread-sort-by-number}, responses can end
7909 up appearing before the article to which they are responding to.
7910 Setting this variable to an alternate value
7911 (e.g. @code{gnus-thread-sort-by-date}), in a group's parameters or in an
7912 appropriate hook (e.g. @code{gnus-summary-generate-hook}) can produce a
7913 more logical sub-thread ordering in such instances.
7918 @node Low-Level Threading
7919 @subsubsection Low-Level Threading
7923 @item gnus-parse-headers-hook
7924 @vindex gnus-parse-headers-hook
7925 Hook run before parsing any headers.
7927 @item gnus-alter-header-function
7928 @vindex gnus-alter-header-function
7929 If non-@code{nil}, this function will be called to allow alteration of
7930 article header structures. The function is called with one parameter,
7931 the article header vector, which it may alter in any way. For instance,
7932 if you have a mail-to-news gateway which alters the @code{Message-ID}s
7933 in systematic ways (by adding prefixes and such), you can use this
7934 variable to un-scramble the @code{Message-ID}s so that they are more
7935 meaningful. Here's one example:
7938 (setq gnus-alter-header-function 'my-alter-message-id)
7940 (defun my-alter-message-id (header)
7941 (let ((id (mail-header-id header)))
7943 "\\(<[^<>@@]*\\)\\.?cygnus\\..*@@\\([^<>@@]*>\\)" id)
7945 (concat (match-string 1 id) "@@" (match-string 2 id))
7952 @node Thread Commands
7953 @subsection Thread Commands
7954 @cindex thread commands
7960 @kindex T k (Summary)
7961 @kindex C-M-k (Summary)
7962 @findex gnus-summary-kill-thread
7963 Mark all articles in the current (sub-)thread as read
7964 (@code{gnus-summary-kill-thread}). If the prefix argument is positive,
7965 remove all marks instead. If the prefix argument is negative, tick
7970 @kindex T l (Summary)
7971 @kindex C-M-l (Summary)
7972 @findex gnus-summary-lower-thread
7973 Lower the score of the current (sub-)thread
7974 (@code{gnus-summary-lower-thread}).
7977 @kindex T i (Summary)
7978 @findex gnus-summary-raise-thread
7979 Increase the score of the current (sub-)thread
7980 (@code{gnus-summary-raise-thread}).
7983 @kindex T # (Summary)
7984 @findex gnus-uu-mark-thread
7985 Set the process mark on the current (sub-)thread
7986 (@code{gnus-uu-mark-thread}).
7989 @kindex T M-# (Summary)
7990 @findex gnus-uu-unmark-thread
7991 Remove the process mark from the current (sub-)thread
7992 (@code{gnus-uu-unmark-thread}).
7995 @kindex T T (Summary)
7996 @findex gnus-summary-toggle-threads
7997 Toggle threading (@code{gnus-summary-toggle-threads}).
8000 @kindex T s (Summary)
8001 @findex gnus-summary-show-thread
8002 Expose the (sub-)thread hidden under the current article, if any@*
8003 (@code{gnus-summary-show-thread}).
8006 @kindex T h (Summary)
8007 @findex gnus-summary-hide-thread
8008 Hide the current (sub-)thread (@code{gnus-summary-hide-thread}).
8011 @kindex T S (Summary)
8012 @findex gnus-summary-show-all-threads
8013 Expose all hidden threads (@code{gnus-summary-show-all-threads}).
8016 @kindex T H (Summary)
8017 @findex gnus-summary-hide-all-threads
8018 Hide all threads (@code{gnus-summary-hide-all-threads}).
8021 @kindex T t (Summary)
8022 @findex gnus-summary-rethread-current
8023 Re-thread the current article's thread
8024 (@code{gnus-summary-rethread-current}). This works even when the
8025 summary buffer is otherwise unthreaded.
8028 @kindex T ^ (Summary)
8029 @findex gnus-summary-reparent-thread
8030 Make the current article the child of the marked (or previous) article
8031 (@code{gnus-summary-reparent-thread}).
8034 @kindex T M-^ (Summary)
8035 @findex gnus-summary-reparent-children
8036 Make the current article the parent of the marked articles
8037 (@code{gnus-summary-reparent-children}).
8041 The following commands are thread movement commands. They all
8042 understand the numeric prefix.
8047 @kindex T n (Summary)
8049 @kindex C-M-n (Summary)
8051 @kindex M-down (Summary)
8052 @findex gnus-summary-next-thread
8053 Go to the next thread (@code{gnus-summary-next-thread}).
8056 @kindex T p (Summary)
8058 @kindex C-M-p (Summary)
8060 @kindex M-up (Summary)
8061 @findex gnus-summary-prev-thread
8062 Go to the previous thread (@code{gnus-summary-prev-thread}).
8065 @kindex T d (Summary)
8066 @findex gnus-summary-down-thread
8067 Descend the thread (@code{gnus-summary-down-thread}).
8070 @kindex T u (Summary)
8071 @findex gnus-summary-up-thread
8072 Ascend the thread (@code{gnus-summary-up-thread}).
8075 @kindex T o (Summary)
8076 @findex gnus-summary-top-thread
8077 Go to the top of the thread (@code{gnus-summary-top-thread}).
8080 @vindex gnus-thread-operation-ignore-subject
8081 If you ignore subject while threading, you'll naturally end up with
8082 threads that have several different subjects in them. If you then issue
8083 a command like @kbd{T k} (@code{gnus-summary-kill-thread}) you might not
8084 wish to kill the entire thread, but just those parts of the thread that
8085 have the same subject as the current article. If you like this idea,
8086 you can fiddle with @code{gnus-thread-operation-ignore-subject}. If it
8087 is non-@code{nil} (which it is by default), subjects will be ignored
8088 when doing thread commands. If this variable is @code{nil}, articles in
8089 the same thread with different subjects will not be included in the
8090 operation in question. If this variable is @code{fuzzy}, only articles
8091 that have subjects fuzzily equal will be included (@pxref{Fuzzy
8095 @node Sorting the Summary Buffer
8096 @section Sorting the Summary Buffer
8098 @findex gnus-thread-sort-by-total-score
8099 @findex gnus-thread-sort-by-date
8100 @findex gnus-thread-sort-by-score
8101 @findex gnus-thread-sort-by-subject
8102 @findex gnus-thread-sort-by-author
8103 @findex gnus-thread-sort-by-recipient
8104 @findex gnus-thread-sort-by-number
8105 @findex gnus-thread-sort-by-random
8106 @vindex gnus-thread-sort-functions
8107 @findex gnus-thread-sort-by-most-recent-number
8108 @findex gnus-thread-sort-by-most-recent-date
8109 If you are using a threaded summary display, you can sort the threads by
8110 setting @code{gnus-thread-sort-functions}, which can be either a single
8111 function, a list of functions, or a list containing functions and
8112 @code{(not some-function)} elements.
8114 By default, sorting is done on article numbers. Ready-made sorting
8115 predicate functions include @code{gnus-thread-sort-by-number},
8116 @code{gnus-thread-sort-by-author}, @code{gnus-thread-sort-by-recipient},
8117 @code{gnus-thread-sort-by-subject},
8118 @code{gnus-thread-sort-by-date},
8119 @code{gnus-thread-sort-by-score},
8120 @code{gnus-thread-sort-by-most-recent-number},
8121 @code{gnus-thread-sort-by-most-recent-date},
8122 @code{gnus-thread-sort-by-random} and
8123 @code{gnus-thread-sort-by-total-score}.
8125 Each function takes two threads and returns non-@code{nil} if the first
8126 thread should be sorted before the other. Note that sorting really is
8127 normally done by looking only at the roots of each thread.
8129 If you use more than one function, the primary sort key should be the
8130 last function in the list. You should probably always include
8131 @code{gnus-thread-sort-by-number} in the list of sorting
8132 functions---preferably first. This will ensure that threads that are
8133 equal with respect to the other sort criteria will be displayed in
8134 ascending article order.
8136 If you would like to sort by reverse score, then by subject, and finally
8137 by number, you could do something like:
8140 (setq gnus-thread-sort-functions
8141 '(gnus-thread-sort-by-number
8142 gnus-thread-sort-by-subject
8143 (not gnus-thread-sort-by-total-score)))
8146 The threads that have highest score will be displayed first in the
8147 summary buffer. When threads have the same score, they will be sorted
8148 alphabetically. The threads that have the same score and the same
8149 subject will be sorted by number, which is (normally) the sequence in
8150 which the articles arrived.
8152 If you want to sort by score and then reverse arrival order, you could
8156 (setq gnus-thread-sort-functions
8157 '((not gnus-thread-sort-by-number)
8158 gnus-thread-sort-by-score))
8161 @vindex gnus-thread-score-function
8162 The function in the @code{gnus-thread-score-function} variable (default
8163 @code{+}) is used for calculating the total score of a thread. Useful
8164 functions might be @code{max}, @code{min}, or squared means, or whatever
8167 @findex gnus-article-sort-functions
8168 @findex gnus-article-sort-by-date
8169 @findex gnus-article-sort-by-most-recent-date
8170 @findex gnus-article-sort-by-score
8171 @findex gnus-article-sort-by-subject
8172 @findex gnus-article-sort-by-author
8173 @findex gnus-article-sort-by-random
8174 @findex gnus-article-sort-by-number
8175 @findex gnus-article-sort-by-most-recent-number
8176 If you are using an unthreaded display for some strange reason or
8177 other, you have to fiddle with the @code{gnus-article-sort-functions}
8178 variable. It is very similar to the
8179 @code{gnus-thread-sort-functions}, except that it uses slightly
8180 different functions for article comparison. Available sorting
8181 predicate functions are @code{gnus-article-sort-by-number},
8182 @code{gnus-article-sort-by-author},
8183 @code{gnus-article-sort-by-subject}, @code{gnus-article-sort-by-date},
8184 @code{gnus-article-sort-by-random}, and
8185 @code{gnus-article-sort-by-score}.
8187 If you want to sort an unthreaded summary display by subject, you could
8191 (setq gnus-article-sort-functions
8192 '(gnus-article-sort-by-number
8193 gnus-article-sort-by-subject))
8196 You can define group specific sorting via @code{gnus-parameters},
8197 @xref{Group Parameters}.
8200 @node Asynchronous Fetching
8201 @section Asynchronous Article Fetching
8202 @cindex asynchronous article fetching
8203 @cindex article pre-fetch
8206 If you read your news from an @acronym{NNTP} server that's far away, the
8207 network latencies may make reading articles a chore. You have to wait
8208 for a while after pressing @kbd{n} to go to the next article before the
8209 article appears. Why can't Gnus just go ahead and fetch the article
8210 while you are reading the previous one? Why not, indeed.
8212 First, some caveats. There are some pitfalls to using asynchronous
8213 article fetching, especially the way Gnus does it.
8215 Let's say you are reading article 1, which is short, and article 2 is
8216 quite long, and you are not interested in reading that. Gnus does not
8217 know this, so it goes ahead and fetches article 2. You decide to read
8218 article 3, but since Gnus is in the process of fetching article 2, the
8219 connection is blocked.
8221 To avoid these situations, Gnus will open two (count 'em two)
8222 connections to the server. Some people may think this isn't a very nice
8223 thing to do, but I don't see any real alternatives. Setting up that
8224 extra connection takes some time, so Gnus startup will be slower.
8226 Gnus will fetch more articles than you will read. This will mean that
8227 the link between your machine and the @acronym{NNTP} server will become more
8228 loaded than if you didn't use article pre-fetch. The server itself will
8229 also become more loaded---both with the extra article requests, and the
8232 Ok, so now you know that you shouldn't really use this thing@dots{} unless
8235 @vindex gnus-asynchronous
8236 Here's how: Set @code{gnus-asynchronous} to @code{t}. The rest should
8237 happen automatically.
8239 @vindex gnus-use-article-prefetch
8240 You can control how many articles are to be pre-fetched by setting
8241 @code{gnus-use-article-prefetch}. This is 30 by default, which means
8242 that when you read an article in the group, the back end will pre-fetch
8243 the next 30 articles. If this variable is @code{t}, the back end will
8244 pre-fetch all the articles it can without bound. If it is
8245 @code{nil}, no pre-fetching will be done.
8247 @vindex gnus-async-prefetch-article-p
8248 @findex gnus-async-unread-p
8249 There are probably some articles that you don't want to pre-fetch---read
8250 articles, for instance. The @code{gnus-async-prefetch-article-p}
8251 variable controls whether an article is to be pre-fetched. This
8252 function should return non-@code{nil} when the article in question is
8253 to be pre-fetched. The default is @code{gnus-async-unread-p}, which
8254 returns @code{nil} on read articles. The function is called with an
8255 article data structure as the only parameter.
8257 If, for instance, you wish to pre-fetch only unread articles shorter
8258 than 100 lines, you could say something like:
8261 (defun my-async-short-unread-p (data)
8262 "Return non-nil for short, unread articles."
8263 (and (gnus-data-unread-p data)
8264 (< (mail-header-lines (gnus-data-header data))
8267 (setq gnus-async-prefetch-article-p 'my-async-short-unread-p)
8270 These functions will be called many, many times, so they should
8271 preferably be short and sweet to avoid slowing down Gnus too much.
8272 It's probably a good idea to byte-compile things like this.
8274 @vindex gnus-async-post-fetch-function
8275 @findex gnus-html-prefetch-images
8276 After an article has been prefetched, this
8277 @code{gnus-async-post-fetch-function} will be called. The buffer will
8278 be narrowed to the region of the article that was fetched. A useful
8279 value would be @code{gnus-html-prefetch-images}, which will prefetch
8280 and store images referenced in the article, so that you don't have to
8281 wait for them to be fetched when you read the article. This is useful
8282 for @acronym{HTML} messages that have external images.
8284 @vindex gnus-prefetched-article-deletion-strategy
8285 Articles have to be removed from the asynch buffer sooner or later. The
8286 @code{gnus-prefetched-article-deletion-strategy} says when to remove
8287 articles. This is a list that may contain the following elements:
8291 Remove articles when they are read.
8294 Remove articles when exiting the group.
8297 The default value is @code{(read exit)}.
8299 @c @vindex gnus-use-header-prefetch
8300 @c If @code{gnus-use-header-prefetch} is non-@code{nil}, prefetch articles
8301 @c from the next group.
8304 @node Article Caching
8305 @section Article Caching
8306 @cindex article caching
8309 If you have an @emph{extremely} slow @acronym{NNTP} connection, you may
8310 consider turning article caching on. Each article will then be stored
8311 locally under your home directory. As you may surmise, this could
8312 potentially use @emph{huge} amounts of disk space, as well as eat up all
8313 your inodes so fast it will make your head swim. In vodka.
8315 Used carefully, though, it could be just an easier way to save articles.
8317 @vindex gnus-use-long-file-name
8318 @vindex gnus-cache-directory
8319 @vindex gnus-use-cache
8320 To turn caching on, set @code{gnus-use-cache} to @code{t}. By default,
8321 all articles ticked or marked as dormant will then be copied
8322 over to your local cache (@code{gnus-cache-directory}). Whether this
8323 cache is flat or hierarchical is controlled by the
8324 @code{gnus-use-long-file-name} variable, as usual.
8326 When re-selecting a ticked or dormant article, it will be fetched from the
8327 cache instead of from the server. As articles in your cache will never
8328 expire, this might serve as a method of saving articles while still
8329 keeping them where they belong. Just mark all articles you want to save
8330 as dormant, and don't worry.
8332 When an article is marked as read, is it removed from the cache.
8334 @vindex gnus-cache-remove-articles
8335 @vindex gnus-cache-enter-articles
8336 The entering/removal of articles from the cache is controlled by the
8337 @code{gnus-cache-enter-articles} and @code{gnus-cache-remove-articles}
8338 variables. Both are lists of symbols. The first is @code{(ticked
8339 dormant)} by default, meaning that ticked and dormant articles will be
8340 put in the cache. The latter is @code{(read)} by default, meaning that
8341 articles marked as read are removed from the cache. Possibly
8342 symbols in these two lists are @code{ticked}, @code{dormant},
8343 @code{unread} and @code{read}.
8345 @findex gnus-jog-cache
8346 So where does the massive article-fetching and storing come into the
8347 picture? The @code{gnus-jog-cache} command will go through all
8348 subscribed newsgroups, request all unread articles, score them, and
8349 store them in the cache. You should only ever, ever ever ever, use this
8350 command if 1) your connection to the @acronym{NNTP} server is really, really,
8351 really slow and 2) you have a really, really, really huge disk.
8352 Seriously. One way to cut down on the number of articles downloaded is
8353 to score unwanted articles down and have them marked as read. They will
8354 not then be downloaded by this command.
8356 @vindex gnus-uncacheable-groups
8357 @vindex gnus-cacheable-groups
8358 It is likely that you do not want caching on all groups. For instance,
8359 if your @code{nnml} mail is located under your home directory, it makes no
8360 sense to cache it somewhere else under your home directory. Unless you
8361 feel that it's neat to use twice as much space.
8363 To limit the caching, you could set @code{gnus-cacheable-groups} to a
8364 regexp of groups to cache, @samp{^nntp} for instance, or set the
8365 @code{gnus-uncacheable-groups} regexp to @samp{^nnml}, for instance.
8366 Both variables are @code{nil} by default. If a group matches both
8367 variables, the group is not cached.
8369 @findex gnus-cache-generate-nov-databases
8370 @findex gnus-cache-generate-active
8371 @vindex gnus-cache-active-file
8372 The cache stores information on what articles it contains in its active
8373 file (@code{gnus-cache-active-file}). If this file (or any other parts
8374 of the cache) becomes all messed up for some reason or other, Gnus
8375 offers two functions that will try to set things right. @kbd{M-x
8376 gnus-cache-generate-nov-databases} will (re)build all the @acronym{NOV}
8377 files, and @kbd{gnus-cache-generate-active} will (re)generate the active
8380 @findex gnus-cache-move-cache
8381 @code{gnus-cache-move-cache} will move your whole
8382 @code{gnus-cache-directory} to some other location. You get asked to
8383 where, isn't that cool?
8385 @node Persistent Articles
8386 @section Persistent Articles
8387 @cindex persistent articles
8389 Closely related to article caching, we have @dfn{persistent articles}.
8390 In fact, it's just a different way of looking at caching, and much more
8391 useful in my opinion.
8393 Say you're reading a newsgroup, and you happen on to some valuable gem
8394 that you want to keep and treasure forever. You'd normally just save it
8395 (using one of the many saving commands) in some file. The problem with
8396 that is that it's just, well, yucky. Ideally you'd prefer just having
8397 the article remain in the group where you found it forever; untouched by
8398 the expiry going on at the news server.
8400 This is what a @dfn{persistent article} is---an article that just won't
8401 be deleted. It's implemented using the normal cache functions, but
8402 you use two explicit commands for managing persistent articles:
8408 @findex gnus-cache-enter-article
8409 Make the current article persistent (@code{gnus-cache-enter-article}).
8412 @kindex M-* (Summary)
8413 @findex gnus-cache-remove-article
8414 Remove the current article from the persistent articles
8415 (@code{gnus-cache-remove-article}). This will normally delete the
8419 Both these commands understand the process/prefix convention.
8421 To avoid having all ticked articles (and stuff) entered into the cache,
8422 you should set @code{gnus-use-cache} to @code{passive} if you're just
8423 interested in persistent articles:
8426 (setq gnus-use-cache 'passive)
8429 @node Sticky Articles
8430 @section Sticky Articles
8431 @cindex sticky articles
8433 When you select an article the current article buffer will be reused
8434 according to the value of the variable
8435 @code{gnus-single-article-buffer}. If its value is non-@code{nil} (the
8436 default) all articles reuse the same article buffer. Else each group
8437 has its own article buffer.
8439 This implies that it's not possible to have more than one article buffer
8440 in a group at a time. But sometimes you might want to display all the
8441 latest emails from your mother, your father, your aunt, your uncle and
8442 your 17 cousins to coordinate the next christmas party.
8444 That's where sticky articles come in handy. A sticky article buffer
8445 basically is a normal article buffer, but it won't be reused when you
8446 select another article. You can make an article sticky with:
8450 @kindex A S (Summary)
8451 @findex gnus-sticky-article
8452 Make the current article sticky. If a prefix arg is given, ask for a
8453 name for this sticky article buffer.
8456 To close a sticky article buffer you can use these commands:
8462 Puts this sticky article buffer at the end of the list of all buffers.
8466 @findex gnus-kill-sticky-article-buffer
8467 Kills this sticky article buffer.
8470 To kill all sticky article buffers you can use:
8472 @defun gnus-kill-sticky-article-buffers ARG
8473 Kill all sticky article buffers.
8474 If a prefix ARG is given, ask for confirmation.
8477 @node Article Backlog
8478 @section Article Backlog
8480 @cindex article backlog
8482 If you have a slow connection, but the idea of using caching seems
8483 unappealing to you (and it is, really), you can help the situation some
8484 by switching on the @dfn{backlog}. This is where Gnus will buffer
8485 already read articles so that it doesn't have to re-fetch articles
8486 you've already read. This only helps if you are in the habit of
8487 re-selecting articles you've recently read, of course. If you never do
8488 that, turning the backlog on will slow Gnus down a little bit, and
8489 increase memory usage some.
8491 @vindex gnus-keep-backlog
8492 If you set @code{gnus-keep-backlog} to a number @var{n}, Gnus will store
8493 at most @var{n} old articles in a buffer for later re-fetching. If this
8494 variable is non-@code{nil} and is not a number, Gnus will store
8495 @emph{all} read articles, which means that your Emacs will grow without
8496 bound before exploding and taking your machine down with you. I put
8497 that in there just to keep y'all on your toes.
8499 The default value is 20.
8502 @node Saving Articles
8503 @section Saving Articles
8504 @cindex saving articles
8506 Gnus can save articles in a number of ways. Below is the documentation
8507 for saving articles in a fairly straight-forward fashion (i.e., little
8508 processing of the article is done before it is saved). For a different
8509 approach (uudecoding, unsharing) you should use @code{gnus-uu}
8510 (@pxref{Decoding Articles}).
8512 For the commands listed here, the target is a file. If you want to
8513 save to a group, see the @kbd{B c} (@code{gnus-summary-copy-article})
8514 command (@pxref{Mail Group Commands}).
8516 @vindex gnus-save-all-headers
8517 If @code{gnus-save-all-headers} is non-@code{nil}, Gnus will not delete
8518 unwanted headers before saving the article.
8520 @vindex gnus-saved-headers
8521 If the preceding variable is @code{nil}, all headers that match the
8522 @code{gnus-saved-headers} regexp will be kept, while the rest will be
8523 deleted before saving.
8529 @kindex O o (Summary)
8531 @findex gnus-summary-save-article
8532 @c @icon{gnus-summary-save-article}
8533 Save the current article using the default article saver
8534 (@code{gnus-summary-save-article}).
8537 @kindex O m (Summary)
8538 @findex gnus-summary-save-article-mail
8539 Save the current article in a Unix mail box (mbox) file
8540 (@code{gnus-summary-save-article-mail}).
8543 @kindex O r (Summary)
8544 @findex gnus-summary-save-article-rmail
8545 Save the current article in Rmail format
8546 (@code{gnus-summary-save-article-rmail}). This is mbox since Emacs 23,
8547 Babyl in older versions.
8550 @kindex O f (Summary)
8551 @findex gnus-summary-save-article-file
8552 @c @icon{gnus-summary-save-article-file}
8553 Save the current article in plain file format
8554 (@code{gnus-summary-save-article-file}).
8557 @kindex O F (Summary)
8558 @findex gnus-summary-write-article-file
8559 Write the current article in plain file format, overwriting any previous
8560 file contents (@code{gnus-summary-write-article-file}).
8563 @kindex O b (Summary)
8564 @findex gnus-summary-save-article-body-file
8565 Save the current article body in plain file format
8566 (@code{gnus-summary-save-article-body-file}).
8569 @kindex O h (Summary)
8570 @findex gnus-summary-save-article-folder
8571 Save the current article in mh folder format
8572 (@code{gnus-summary-save-article-folder}).
8575 @kindex O v (Summary)
8576 @findex gnus-summary-save-article-vm
8577 Save the current article in a VM folder
8578 (@code{gnus-summary-save-article-vm}).
8582 @kindex O p (Summary)
8584 @findex gnus-summary-pipe-output
8585 @vindex gnus-summary-pipe-output-default-command
8586 Save the current article in a pipe. Uhm, like, what I mean is---Pipe
8587 the current article to a process (@code{gnus-summary-pipe-output}).
8588 If given a symbolic prefix (@pxref{Symbolic Prefixes}), include the
8589 complete headers in the piped output. The symbolic prefix @code{r} is
8590 special; it lets this command pipe a raw article including all headers.
8591 The @code{gnus-summary-pipe-output-default-command} variable can be set
8592 to a string containing the default command and options (default
8596 @kindex O P (Summary)
8597 @findex gnus-summary-muttprint
8598 @vindex gnus-summary-muttprint-program
8599 Save the current article into muttprint. That is, print it using the
8600 external program @uref{http://muttprint.sourceforge.net/,
8601 Muttprint}. The program name and options to use is controlled by the
8602 variable @code{gnus-summary-muttprint-program}.
8603 (@code{gnus-summary-muttprint}).
8607 @vindex gnus-prompt-before-saving
8608 All these commands use the process/prefix convention
8609 (@pxref{Process/Prefix}). If you save bunches of articles using these
8610 functions, you might get tired of being prompted for files to save each
8611 and every article in. The prompting action is controlled by
8612 the @code{gnus-prompt-before-saving} variable, which is @code{always} by
8613 default, giving you that excessive prompting action you know and
8614 loathe. If you set this variable to @code{t} instead, you'll be prompted
8615 just once for each series of articles you save. If you like to really
8616 have Gnus do all your thinking for you, you can even set this variable
8617 to @code{nil}, which means that you will never be prompted for files to
8618 save articles in. Gnus will simply save all the articles in the default
8622 @vindex gnus-default-article-saver
8623 You can customize the @code{gnus-default-article-saver} variable to make
8624 Gnus do what you want it to. You can use any of the eight ready-made
8625 functions below, or you can create your own.
8629 @item gnus-summary-save-in-rmail
8630 @findex gnus-summary-save-in-rmail
8631 @vindex gnus-rmail-save-name
8632 @findex gnus-plain-save-name
8633 This is the default format, that used by the Rmail package. Since Emacs
8634 23, Rmail uses standard mbox format. Before this, it used the
8635 @dfn{Babyl} format. Accordingly, this command writes mbox format since
8636 Emacs 23, unless appending to an existing Babyl file. In older versions
8637 of Emacs, it always uses Babyl format. Uses the function in the
8638 @code{gnus-rmail-save-name} variable to get a file name to save the
8639 article in. The default is @code{gnus-plain-save-name}.
8641 @item gnus-summary-save-in-mail
8642 @findex gnus-summary-save-in-mail
8643 @vindex gnus-mail-save-name
8644 Save in a Unix mail (mbox) file. Uses the function in the
8645 @code{gnus-mail-save-name} variable to get a file name to save the
8646 article in. The default is @code{gnus-plain-save-name}.
8648 @item gnus-summary-save-in-file
8649 @findex gnus-summary-save-in-file
8650 @vindex gnus-file-save-name
8651 @findex gnus-numeric-save-name
8652 Append the article straight to an ordinary file. Uses the function in
8653 the @code{gnus-file-save-name} variable to get a file name to save the
8654 article in. The default is @code{gnus-numeric-save-name}.
8656 @item gnus-summary-write-to-file
8657 @findex gnus-summary-write-to-file
8658 Write the article straight to an ordinary file. The file is
8659 overwritten if it exists. Uses the function in the
8660 @code{gnus-file-save-name} variable to get a file name to save the
8661 article in. The default is @code{gnus-numeric-save-name}.
8663 @item gnus-summary-save-body-in-file
8664 @findex gnus-summary-save-body-in-file
8665 Append the article body to an ordinary file. Uses the function in the
8666 @code{gnus-file-save-name} variable to get a file name to save the
8667 article in. The default is @code{gnus-numeric-save-name}.
8669 @item gnus-summary-write-body-to-file
8670 @findex gnus-summary-write-body-to-file
8671 Write the article body straight to an ordinary file. The file is
8672 overwritten if it exists. Uses the function in the
8673 @code{gnus-file-save-name} variable to get a file name to save the
8674 article in. The default is @code{gnus-numeric-save-name}.
8676 @item gnus-summary-save-in-folder
8677 @findex gnus-summary-save-in-folder
8678 @findex gnus-folder-save-name
8679 @findex gnus-Folder-save-name
8680 @vindex gnus-folder-save-name
8683 Save the article to an MH folder using @code{rcvstore} from the MH
8684 library. Uses the function in the @code{gnus-folder-save-name} variable
8685 to get a file name to save the article in. The default is
8686 @code{gnus-folder-save-name}, but you can also use
8687 @code{gnus-Folder-save-name}, which creates capitalized names.
8689 @item gnus-summary-save-in-vm
8690 @findex gnus-summary-save-in-vm
8691 Save the article in a VM folder. You have to have the VM mail
8692 reader to use this setting.
8694 @item gnus-summary-save-in-pipe
8695 @findex gnus-summary-save-in-pipe
8696 Pipe the article to a shell command. This function takes optional two
8697 arguments COMMAND and RAW. Valid values for COMMAND include:
8701 The executable command name and possibly arguments.
8703 You will be prompted for the command in the minibuffer.
8704 @item the symbol @code{default}@*
8705 It will be replaced with the command which the variable
8706 @code{gnus-summary-pipe-output-default-command} holds or the command
8707 last used for saving.
8710 Non-@code{nil} value for RAW overrides @code{:decode} and
8711 @code{:headers} properties (see below) and the raw article including all
8712 headers will be piped.
8715 The symbol of each function may have the following properties:
8719 The value non-@code{nil} means save decoded articles. This is
8720 meaningful only with @code{gnus-summary-save-in-file},
8721 @code{gnus-summary-save-body-in-file},
8722 @code{gnus-summary-write-to-file},
8723 @code{gnus-summary-write-body-to-file}, and
8724 @code{gnus-summary-save-in-pipe}.
8727 The value specifies an alternative function which appends, not
8728 overwrites, articles to a file. This implies that when saving many
8729 articles at a time, @code{gnus-prompt-before-saving} is bound to
8730 @code{t} and all articles are saved in a single file. This is
8731 meaningful only with @code{gnus-summary-write-to-file} and
8732 @code{gnus-summary-write-body-to-file}.
8735 The value specifies the symbol of a variable of which the value
8736 specifies headers to be saved. If it is omitted,
8737 @code{gnus-save-all-headers} and @code{gnus-saved-headers} control what
8738 headers should be saved.
8741 @vindex gnus-article-save-directory
8742 All of these functions, except for the last one, will save the article
8743 in the @code{gnus-article-save-directory}, which is initialized from the
8744 @env{SAVEDIR} environment variable. This is @file{~/News/} by
8747 As you can see above, the functions use different functions to find a
8748 suitable name of a file to save the article in. Below is a list of
8749 available functions that generate names:
8753 @item gnus-Numeric-save-name
8754 @findex gnus-Numeric-save-name
8755 File names like @file{~/News/Alt.andrea-dworkin/45}.
8757 @item gnus-numeric-save-name
8758 @findex gnus-numeric-save-name
8759 File names like @file{~/News/alt.andrea-dworkin/45}.
8761 @item gnus-Plain-save-name
8762 @findex gnus-Plain-save-name
8763 File names like @file{~/News/Alt.andrea-dworkin}.
8765 @item gnus-plain-save-name
8766 @findex gnus-plain-save-name
8767 File names like @file{~/News/alt.andrea-dworkin}.
8769 @item gnus-sender-save-name
8770 @findex gnus-sender-save-name
8771 File names like @file{~/News/larsi}.
8774 @vindex gnus-split-methods
8775 You can have Gnus suggest where to save articles by plonking a regexp into
8776 the @code{gnus-split-methods} alist. For instance, if you would like to
8777 save articles related to Gnus in the file @file{gnus-stuff}, and articles
8778 related to VM in @file{vm-stuff}, you could set this variable to something
8782 (("^Subject:.*gnus\\|^Newsgroups:.*gnus" "gnus-stuff")
8783 ("^Subject:.*vm\\|^Xref:.*vm" "vm-stuff")
8784 (my-choosing-function "../other-dir/my-stuff")
8785 ((equal gnus-newsgroup-name "mail.misc") "mail-stuff"))
8788 We see that this is a list where each element is a list that has two
8789 elements---the @dfn{match} and the @dfn{file}. The match can either be
8790 a string (in which case it is used as a regexp to match on the article
8791 head); it can be a symbol (which will be called as a function with the
8792 group name as a parameter); or it can be a list (which will be
8793 @code{eval}ed). If any of these actions have a non-@code{nil} result,
8794 the @dfn{file} will be used as a default prompt. In addition, the
8795 result of the operation itself will be used if the function or form
8796 called returns a string or a list of strings.
8798 You basically end up with a list of file names that might be used when
8799 saving the current article. (All ``matches'' will be used.) You will
8800 then be prompted for what you really want to use as a name, with file
8801 name completion over the results from applying this variable.
8803 This variable is @code{((gnus-article-archive-name))} by default, which
8804 means that Gnus will look at the articles it saves for an
8805 @code{Archive-name} line and use that as a suggestion for the file
8808 Here's an example function to clean up file names somewhat. If you have
8809 lots of mail groups called things like
8810 @samp{nnml:mail.whatever}, you may want to chop off the beginning of
8811 these group names before creating the file name to save to. The
8812 following will do just that:
8815 (defun my-save-name (group)
8816 (when (string-match "^nnml:mail." group)
8817 (substring group (match-end 0))))
8819 (setq gnus-split-methods
8820 '((gnus-article-archive-name)
8825 @vindex gnus-use-long-file-name
8826 Finally, you have the @code{gnus-use-long-file-name} variable. If it is
8827 @code{nil}, all the preceding functions will replace all periods
8828 (@samp{.}) in the group names with slashes (@samp{/})---which means that
8829 the functions will generate hierarchies of directories instead of having
8830 all the files in the top level directory
8831 (@file{~/News/alt/andrea-dworkin} instead of
8832 @file{~/News/alt.andrea-dworkin}.) This variable is @code{t} by default
8833 on most systems. However, for historical reasons, this is @code{nil} on
8834 Xenix and usg-unix-v machines by default.
8836 This function also affects kill and score file names. If this variable
8837 is a list, and the list contains the element @code{not-score}, long file
8838 names will not be used for score files, if it contains the element
8839 @code{not-save}, long file names will not be used for saving, and if it
8840 contains the element @code{not-kill}, long file names will not be used
8843 If you'd like to save articles in a hierarchy that looks something like
8847 (setq gnus-use-long-file-name '(not-save)) ; @r{to get a hierarchy}
8848 (setq gnus-default-article-saver
8849 'gnus-summary-save-in-file) ; @r{no encoding}
8852 Then just save with @kbd{o}. You'd then read this hierarchy with
8853 ephemeral @code{nneething} groups---@kbd{G D} in the group buffer, and
8854 the top level directory as the argument (@file{~/News/}). Then just walk
8855 around to the groups/directories with @code{nneething}.
8858 @node Decoding Articles
8859 @section Decoding Articles
8860 @cindex decoding articles
8862 Sometime users post articles (or series of articles) that have been
8863 encoded in some way or other. Gnus can decode them for you.
8866 * Uuencoded Articles:: Uudecode articles.
8867 * Shell Archives:: Unshar articles.
8868 * PostScript Files:: Split PostScript.
8869 * Other Files:: Plain save and binhex.
8870 * Decoding Variables:: Variables for a happy decoding.
8871 * Viewing Files:: You want to look at the result of the decoding?
8875 @cindex article series
8876 All these functions use the process/prefix convention
8877 (@pxref{Process/Prefix}) for finding out what articles to work on, with
8878 the extension that a ``single article'' means ``a single series''. Gnus
8879 can find out by itself what articles belong to a series, decode all the
8880 articles and unpack/view/save the resulting file(s).
8882 Gnus guesses what articles are in the series according to the following
8883 simplish rule: The subjects must be (nearly) identical, except for the
8884 last two numbers of the line. (Spaces are largely ignored, however.)
8886 For example: If you choose a subject called @samp{cat.gif (2/3)}, Gnus
8887 will find all the articles that match the regexp @samp{^cat.gif
8888 ([0-9]+/[0-9]+).*$}.
8890 Subjects that are non-standard, like @samp{cat.gif (2/3) Part 6 of a
8891 series}, will not be properly recognized by any of the automatic viewing
8892 commands, and you have to mark the articles manually with @kbd{#}.
8895 @node Uuencoded Articles
8896 @subsection Uuencoded Articles
8898 @cindex uuencoded articles
8903 @kindex X u (Summary)
8904 @findex gnus-uu-decode-uu
8905 @c @icon{gnus-uu-decode-uu}
8906 Uudecodes the current series (@code{gnus-uu-decode-uu}).
8909 @kindex X U (Summary)
8910 @findex gnus-uu-decode-uu-and-save
8911 Uudecodes and saves the current series
8912 (@code{gnus-uu-decode-uu-and-save}).
8915 @kindex X v u (Summary)
8916 @findex gnus-uu-decode-uu-view
8917 Uudecodes and views the current series (@code{gnus-uu-decode-uu-view}).
8920 @kindex X v U (Summary)
8921 @findex gnus-uu-decode-uu-and-save-view
8922 Uudecodes, views and saves the current series
8923 (@code{gnus-uu-decode-uu-and-save-view}).
8927 Remember that these all react to the presence of articles marked with
8928 the process mark. If, for instance, you'd like to decode and save an
8929 entire newsgroup, you'd typically do @kbd{M P a}
8930 (@code{gnus-uu-mark-all}) and then @kbd{X U}
8931 (@code{gnus-uu-decode-uu-and-save}).
8933 All this is very much different from how @code{gnus-uu} worked with
8934 @sc{gnus 4.1}, where you had explicit keystrokes for everything under
8935 the sun. This version of @code{gnus-uu} generally assumes that you mark
8936 articles in some way (@pxref{Setting Process Marks}) and then press
8939 @vindex gnus-uu-notify-files
8940 Note: When trying to decode articles that have names matching
8941 @code{gnus-uu-notify-files}, which is hard-coded to
8942 @samp{[Cc][Ii][Nn][Dd][Yy][0-9]+.\\(gif\\|jpg\\)}, @code{gnus-uu} will
8943 automatically post an article on @samp{comp.unix.wizards} saying that
8944 you have just viewed the file in question. This feature can't be turned
8948 @node Shell Archives
8949 @subsection Shell Archives
8951 @cindex shell archives
8952 @cindex shared articles
8954 Shell archives (``shar files'') used to be a popular way to distribute
8955 sources, but it isn't used all that much today. In any case, we have
8956 some commands to deal with these:
8961 @kindex X s (Summary)
8962 @findex gnus-uu-decode-unshar
8963 Unshars the current series (@code{gnus-uu-decode-unshar}).
8966 @kindex X S (Summary)
8967 @findex gnus-uu-decode-unshar-and-save
8968 Unshars and saves the current series (@code{gnus-uu-decode-unshar-and-save}).
8971 @kindex X v s (Summary)
8972 @findex gnus-uu-decode-unshar-view
8973 Unshars and views the current series (@code{gnus-uu-decode-unshar-view}).
8976 @kindex X v S (Summary)
8977 @findex gnus-uu-decode-unshar-and-save-view
8978 Unshars, views and saves the current series
8979 (@code{gnus-uu-decode-unshar-and-save-view}).
8983 @node PostScript Files
8984 @subsection PostScript Files
8990 @kindex X p (Summary)
8991 @findex gnus-uu-decode-postscript
8992 Unpack the current PostScript series (@code{gnus-uu-decode-postscript}).
8995 @kindex X P (Summary)
8996 @findex gnus-uu-decode-postscript-and-save
8997 Unpack and save the current PostScript series
8998 (@code{gnus-uu-decode-postscript-and-save}).
9001 @kindex X v p (Summary)
9002 @findex gnus-uu-decode-postscript-view
9003 View the current PostScript series
9004 (@code{gnus-uu-decode-postscript-view}).
9007 @kindex X v P (Summary)
9008 @findex gnus-uu-decode-postscript-and-save-view
9009 View and save the current PostScript series
9010 (@code{gnus-uu-decode-postscript-and-save-view}).
9015 @subsection Other Files
9019 @kindex X o (Summary)
9020 @findex gnus-uu-decode-save
9021 Save the current series
9022 (@code{gnus-uu-decode-save}).
9025 @kindex X b (Summary)
9026 @findex gnus-uu-decode-binhex
9027 Unbinhex the current series (@code{gnus-uu-decode-binhex}). This
9028 doesn't really work yet.
9031 @kindex X Y (Summary)
9032 @findex gnus-uu-decode-yenc
9033 yEnc-decode the current series and save it (@code{gnus-uu-decode-yenc}).
9037 @node Decoding Variables
9038 @subsection Decoding Variables
9040 Adjective, not verb.
9043 * Rule Variables:: Variables that say how a file is to be viewed.
9044 * Other Decode Variables:: Other decode variables.
9045 * Uuencoding and Posting:: Variables for customizing uuencoding.
9049 @node Rule Variables
9050 @subsubsection Rule Variables
9051 @cindex rule variables
9053 Gnus uses @dfn{rule variables} to decide how to view a file. All these
9054 variables are of the form
9057 (list '(regexp1 command2)
9064 @item gnus-uu-user-view-rules
9065 @vindex gnus-uu-user-view-rules
9067 This variable is consulted first when viewing files. If you wish to use,
9068 for instance, @code{sox} to convert an @file{.au} sound file, you could
9071 (setq gnus-uu-user-view-rules
9072 (list '("\\\\.au$" "sox %s -t .aiff > /dev/audio")))
9075 @item gnus-uu-user-view-rules-end
9076 @vindex gnus-uu-user-view-rules-end
9077 This variable is consulted if Gnus couldn't make any matches from the
9078 user and default view rules.
9080 @item gnus-uu-user-archive-rules
9081 @vindex gnus-uu-user-archive-rules
9082 This variable can be used to say what commands should be used to unpack
9087 @node Other Decode Variables
9088 @subsubsection Other Decode Variables
9091 @vindex gnus-uu-grabbed-file-functions
9093 @item gnus-uu-grabbed-file-functions
9094 All functions in this list will be called right after each file has been
9095 successfully decoded---so that you can move or view files right away,
9096 and don't have to wait for all files to be decoded before you can do
9097 anything. Ready-made functions you can put in this list are:
9101 @item gnus-uu-grab-view
9102 @findex gnus-uu-grab-view
9105 @item gnus-uu-grab-move
9106 @findex gnus-uu-grab-move
9107 Move the file (if you're using a saving function.)
9110 @item gnus-uu-be-dangerous
9111 @vindex gnus-uu-be-dangerous
9112 Specifies what to do if unusual situations arise during decoding. If
9113 @code{nil}, be as conservative as possible. If @code{t}, ignore things
9114 that didn't work, and overwrite existing files. Otherwise, ask each
9117 @item gnus-uu-ignore-files-by-name
9118 @vindex gnus-uu-ignore-files-by-name
9119 Files with name matching this regular expression won't be viewed.
9121 @item gnus-uu-ignore-files-by-type
9122 @vindex gnus-uu-ignore-files-by-type
9123 Files with a @acronym{MIME} type matching this variable won't be viewed.
9124 Note that Gnus tries to guess what type the file is based on the name.
9125 @code{gnus-uu} is not a @acronym{MIME} package (yet), so this is slightly
9128 @item gnus-uu-tmp-dir
9129 @vindex gnus-uu-tmp-dir
9130 Where @code{gnus-uu} does its work.
9132 @item gnus-uu-do-not-unpack-archives
9133 @vindex gnus-uu-do-not-unpack-archives
9134 Non-@code{nil} means that @code{gnus-uu} won't peek inside archives
9135 looking for files to display.
9137 @item gnus-uu-view-and-save
9138 @vindex gnus-uu-view-and-save
9139 Non-@code{nil} means that the user will always be asked to save a file
9142 @item gnus-uu-ignore-default-view-rules
9143 @vindex gnus-uu-ignore-default-view-rules
9144 Non-@code{nil} means that @code{gnus-uu} will ignore the default viewing
9147 @item gnus-uu-ignore-default-archive-rules
9148 @vindex gnus-uu-ignore-default-archive-rules
9149 Non-@code{nil} means that @code{gnus-uu} will ignore the default archive
9152 @item gnus-uu-kill-carriage-return
9153 @vindex gnus-uu-kill-carriage-return
9154 Non-@code{nil} means that @code{gnus-uu} will strip all carriage returns
9157 @item gnus-uu-unmark-articles-not-decoded
9158 @vindex gnus-uu-unmark-articles-not-decoded
9159 Non-@code{nil} means that @code{gnus-uu} will mark unsuccessfully
9160 decoded articles as unread.
9162 @item gnus-uu-correct-stripped-uucode
9163 @vindex gnus-uu-correct-stripped-uucode
9164 Non-@code{nil} means that @code{gnus-uu} will @emph{try} to fix
9165 uuencoded files that have had trailing spaces deleted.
9167 @item gnus-uu-pre-uudecode-hook
9168 @vindex gnus-uu-pre-uudecode-hook
9169 Hook run before sending a message to @code{uudecode}.
9171 @item gnus-uu-view-with-metamail
9172 @vindex gnus-uu-view-with-metamail
9174 Non-@code{nil} means that @code{gnus-uu} will ignore the viewing
9175 commands defined by the rule variables and just fudge a @acronym{MIME}
9176 content type based on the file name. The result will be fed to
9177 @code{metamail} for viewing.
9179 @item gnus-uu-save-in-digest
9180 @vindex gnus-uu-save-in-digest
9181 Non-@code{nil} means that @code{gnus-uu}, when asked to save without
9182 decoding, will save in digests. If this variable is @code{nil},
9183 @code{gnus-uu} will just save everything in a file without any
9184 embellishments. The digesting almost conforms to RFC 1153---no easy way
9185 to specify any meaningful volume and issue numbers were found, so I
9186 simply dropped them.
9191 @node Uuencoding and Posting
9192 @subsubsection Uuencoding and Posting
9196 @item gnus-uu-post-include-before-composing
9197 @vindex gnus-uu-post-include-before-composing
9198 Non-@code{nil} means that @code{gnus-uu} will ask for a file to encode
9199 before you compose the article. If this variable is @code{t}, you can
9200 either include an encoded file with @kbd{C-c C-i} or have one included
9201 for you when you post the article.
9203 @item gnus-uu-post-length
9204 @vindex gnus-uu-post-length
9205 Maximum length of an article. The encoded file will be split into how
9206 many articles it takes to post the entire file.
9208 @item gnus-uu-post-threaded
9209 @vindex gnus-uu-post-threaded
9210 Non-@code{nil} means that @code{gnus-uu} will post the encoded file in a
9211 thread. This may not be smart, as no other decoder I have seen is able
9212 to follow threads when collecting uuencoded articles. (Well, I have
9213 seen one package that does that---@code{gnus-uu}, but somehow, I don't
9214 think that counts@dots{}) Default is @code{nil}.
9216 @item gnus-uu-post-separate-description
9217 @vindex gnus-uu-post-separate-description
9218 Non-@code{nil} means that the description will be posted in a separate
9219 article. The first article will typically be numbered (0/x). If this
9220 variable is @code{nil}, the description the user enters will be included
9221 at the beginning of the first article, which will be numbered (1/x).
9222 Default is @code{t}.
9228 @subsection Viewing Files
9229 @cindex viewing files
9230 @cindex pseudo-articles
9232 After decoding, if the file is some sort of archive, Gnus will attempt
9233 to unpack the archive and see if any of the files in the archive can be
9234 viewed. For instance, if you have a gzipped tar file @file{pics.tar.gz}
9235 containing the files @file{pic1.jpg} and @file{pic2.gif}, Gnus will
9236 uncompress and de-tar the main file, and then view the two pictures.
9237 This unpacking process is recursive, so if the archive contains archives
9238 of archives, it'll all be unpacked.
9240 Finally, Gnus will normally insert a @dfn{pseudo-article} for each
9241 extracted file into the summary buffer. If you go to these
9242 ``articles'', you will be prompted for a command to run (usually Gnus
9243 will make a suggestion), and then the command will be run.
9245 @vindex gnus-view-pseudo-asynchronously
9246 If @code{gnus-view-pseudo-asynchronously} is @code{nil}, Emacs will wait
9247 until the viewing is done before proceeding.
9249 @vindex gnus-view-pseudos
9250 If @code{gnus-view-pseudos} is @code{automatic}, Gnus will not insert
9251 the pseudo-articles into the summary buffer, but view them
9252 immediately. If this variable is @code{not-confirm}, the user won't even
9253 be asked for a confirmation before viewing is done.
9255 @vindex gnus-view-pseudos-separately
9256 If @code{gnus-view-pseudos-separately} is non-@code{nil}, one
9257 pseudo-article will be created for each file to be viewed. If
9258 @code{nil}, all files that use the same viewing command will be given as
9259 a list of parameters to that command.
9261 @vindex gnus-insert-pseudo-articles
9262 If @code{gnus-insert-pseudo-articles} is non-@code{nil}, insert
9263 pseudo-articles when decoding. It is @code{t} by default.
9265 So; there you are, reading your @emph{pseudo-articles} in your
9266 @emph{virtual newsgroup} from the @emph{virtual server}; and you think:
9267 Why isn't anything real anymore? How did we get here?
9270 @node Article Treatment
9271 @section Article Treatment
9273 Reading through this huge manual, you may have quite forgotten that the
9274 object of newsreaders is to actually, like, read what people have
9275 written. Reading articles. Unfortunately, people are quite bad at
9276 writing, so there are tons of functions and variables to make reading
9277 these articles easier.
9280 * Article Highlighting:: You want to make the article look like fruit salad.
9281 * Article Fontisizing:: Making emphasized text look nice.
9282 * Article Hiding:: You also want to make certain info go away.
9283 * Article Washing:: Lots of way-neat functions to make life better.
9284 * Article Header:: Doing various header transformations.
9285 * Article Buttons:: Click on URLs, Message-IDs, addresses and the like.
9286 * Article Button Levels:: Controlling appearance of buttons.
9287 * Article Date:: Grumble, UT!
9288 * Article Display:: Display various stuff---X-Face, Picons, Smileys
9289 * Article Signature:: What is a signature?
9290 * Article Miscellanea:: Various other stuff.
9294 @node Article Highlighting
9295 @subsection Article Highlighting
9296 @cindex highlighting
9298 Not only do you want your article buffer to look like fruit salad, but
9299 you want it to look like technicolor fruit salad.
9304 @kindex W H a (Summary)
9305 @findex gnus-article-highlight
9306 @findex gnus-article-maybe-highlight
9307 Do much highlighting of the current article
9308 (@code{gnus-article-highlight}). This function highlights header, cited
9309 text, the signature, and adds buttons to the body and the head.
9312 @kindex W H h (Summary)
9313 @findex gnus-article-highlight-headers
9314 @vindex gnus-header-face-alist
9315 Highlight the headers (@code{gnus-article-highlight-headers}). The
9316 highlighting will be done according to the @code{gnus-header-face-alist}
9317 variable, which is a list where each element has the form
9318 @code{(@var{regexp} @var{name} @var{content})}.
9319 @var{regexp} is a regular expression for matching the
9320 header, @var{name} is the face used for highlighting the header name
9321 (@pxref{Faces and Fonts}) and @var{content} is the face for highlighting
9322 the header value. The first match made will be used. Note that
9323 @var{regexp} shouldn't have @samp{^} prepended---Gnus will add one.
9326 @kindex W H c (Summary)
9327 @findex gnus-article-highlight-citation
9328 Highlight cited text (@code{gnus-article-highlight-citation}).
9330 Some variables to customize the citation highlights:
9333 @vindex gnus-cite-parse-max-size
9335 @item gnus-cite-parse-max-size
9336 If the article size in bytes is bigger than this variable (which is
9337 25000 by default), no citation highlighting will be performed.
9339 @item gnus-cite-max-prefix
9340 @vindex gnus-cite-max-prefix
9341 Maximum possible length for a citation prefix (default 20).
9343 @item gnus-cite-face-list
9344 @vindex gnus-cite-face-list
9345 List of faces used for highlighting citations (@pxref{Faces and Fonts}).
9346 When there are citations from multiple articles in the same message,
9347 Gnus will try to give each citation from each article its own face.
9348 This should make it easier to see who wrote what.
9350 @item gnus-supercite-regexp
9351 @vindex gnus-supercite-regexp
9352 Regexp matching normal Supercite attribution lines.
9354 @item gnus-supercite-secondary-regexp
9355 @vindex gnus-supercite-secondary-regexp
9356 Regexp matching mangled Supercite attribution lines.
9358 @item gnus-cite-minimum-match-count
9359 @vindex gnus-cite-minimum-match-count
9360 Minimum number of identical prefixes we have to see before we believe
9361 that it's a citation.
9363 @item gnus-cite-attribution-prefix
9364 @vindex gnus-cite-attribution-prefix
9365 Regexp matching the beginning of an attribution line.
9367 @item gnus-cite-attribution-suffix
9368 @vindex gnus-cite-attribution-suffix
9369 Regexp matching the end of an attribution line.
9371 @item gnus-cite-attribution-face
9372 @vindex gnus-cite-attribution-face
9373 Face used for attribution lines. It is merged with the face for the
9374 cited text belonging to the attribution.
9376 @item gnus-cite-ignore-quoted-from
9377 @vindex gnus-cite-ignore-quoted-from
9378 If non-@code{nil}, no citation highlighting will be performed on lines
9379 beginning with @samp{>From }. Those lines may have been quoted by MTAs
9380 in order not to mix up with the envelope From line. The default value
9387 @kindex W H s (Summary)
9388 @vindex gnus-signature-separator
9389 @vindex gnus-signature-face
9390 @findex gnus-article-highlight-signature
9391 Highlight the signature (@code{gnus-article-highlight-signature}).
9392 Everything after @code{gnus-signature-separator} (@pxref{Article
9393 Signature}) in an article will be considered a signature and will be
9394 highlighted with @code{gnus-signature-face}, which is @code{italic} by
9399 @xref{Customizing Articles}, for how to highlight articles automatically.
9402 @node Article Fontisizing
9403 @subsection Article Fontisizing
9405 @cindex article emphasis
9407 @findex gnus-article-emphasize
9408 @kindex W e (Summary)
9409 People commonly add emphasis to words in news articles by writing things
9410 like @samp{_this_} or @samp{*this*} or @samp{/this/}. Gnus can make
9411 this look nicer by running the article through the @kbd{W e}
9412 (@code{gnus-article-emphasize}) command.
9414 @vindex gnus-emphasis-alist
9415 How the emphasis is computed is controlled by the
9416 @code{gnus-emphasis-alist} variable. This is an alist where the first
9417 element is a regular expression to be matched. The second is a number
9418 that says what regular expression grouping is used to find the entire
9419 emphasized word. The third is a number that says what regexp grouping
9420 should be displayed and highlighted. (The text between these two
9421 groupings will be hidden.) The fourth is the face used for
9425 (setq gnus-emphasis-alist
9426 '(("_\\(\\w+\\)_" 0 1 gnus-emphasis-underline)
9427 ("\\*\\(\\w+\\)\\*" 0 1 gnus-emphasis-bold)))
9436 @vindex gnus-emphasis-underline
9437 @vindex gnus-emphasis-bold
9438 @vindex gnus-emphasis-italic
9439 @vindex gnus-emphasis-underline-bold
9440 @vindex gnus-emphasis-underline-italic
9441 @vindex gnus-emphasis-bold-italic
9442 @vindex gnus-emphasis-underline-bold-italic
9443 By default, there are seven rules, and they use the following faces:
9444 @code{gnus-emphasis-bold}, @code{gnus-emphasis-italic},
9445 @code{gnus-emphasis-underline}, @code{gnus-emphasis-bold-italic},
9446 @code{gnus-emphasis-underline-italic},
9447 @code{gnus-emphasis-underline-bold}, and
9448 @code{gnus-emphasis-underline-bold-italic}.
9450 If you want to change these faces, you can either use @kbd{M-x
9451 customize}, or you can use @code{copy-face}. For instance, if you want
9452 to make @code{gnus-emphasis-italic} use a red face instead, you could
9456 (copy-face 'red 'gnus-emphasis-italic)
9459 @vindex gnus-group-highlight-words-alist
9461 If you want to highlight arbitrary words, you can use the
9462 @code{gnus-group-highlight-words-alist} variable, which uses the same
9463 syntax as @code{gnus-emphasis-alist}. The @code{highlight-words} group
9464 parameter (@pxref{Group Parameters}) can also be used.
9466 @xref{Customizing Articles}, for how to fontize articles automatically.
9469 @node Article Hiding
9470 @subsection Article Hiding
9471 @cindex article hiding
9473 Or rather, hiding certain things in each article. There usually is much
9474 too much cruft in most articles.
9479 @kindex W W a (Summary)
9480 @findex gnus-article-hide
9481 Do quite a lot of hiding on the article buffer
9482 (@kbd{gnus-article-hide}). In particular, this function will hide
9483 headers, @acronym{PGP}, cited text and the signature.
9486 @kindex W W h (Summary)
9487 @findex gnus-article-hide-headers
9488 Hide headers (@code{gnus-article-hide-headers}). @xref{Hiding
9492 @kindex W W b (Summary)
9493 @findex gnus-article-hide-boring-headers
9494 Hide headers that aren't particularly interesting
9495 (@code{gnus-article-hide-boring-headers}). @xref{Hiding Headers}.
9498 @kindex W W s (Summary)
9499 @findex gnus-article-hide-signature
9500 Hide signature (@code{gnus-article-hide-signature}). @xref{Article
9504 @kindex W W l (Summary)
9505 @findex gnus-article-hide-list-identifiers
9506 @vindex gnus-list-identifiers
9507 Strip list identifiers specified in @code{gnus-list-identifiers}. These
9508 are strings some mailing list servers add to the beginning of all
9509 @code{Subject} headers---for example, @samp{[zebra 4711]}. Any leading
9510 @samp{Re: } is skipped before stripping. @code{gnus-list-identifiers}
9511 may not contain @code{\\(..\\)}.
9515 @item gnus-list-identifiers
9516 @vindex gnus-list-identifiers
9517 A regular expression that matches list identifiers to be removed from
9518 subject. This can also be a list of regular expressions.
9523 @kindex W W P (Summary)
9524 @findex gnus-article-hide-pem
9525 Hide @acronym{PEM} (privacy enhanced messages) cruft
9526 (@code{gnus-article-hide-pem}).
9529 @kindex W W B (Summary)
9530 @findex gnus-article-strip-banner
9531 @vindex gnus-article-banner-alist
9532 @vindex gnus-article-address-banner-alist
9535 @cindex stripping advertisements
9536 @cindex advertisements
9537 Strip the banner specified by the @code{banner} group parameter
9538 (@code{gnus-article-strip-banner}). This is mainly used to hide those
9539 annoying banners and/or signatures that some mailing lists and moderated
9540 groups adds to all the messages. The way to use this function is to add
9541 the @code{banner} group parameter (@pxref{Group Parameters}) to the
9542 group you want banners stripped from. The parameter either be a string,
9543 which will be interpreted as a regular expression matching text to be
9544 removed, or the symbol @code{signature}, meaning that the (last)
9545 signature should be removed, or other symbol, meaning that the
9546 corresponding regular expression in @code{gnus-article-banner-alist} is
9549 Regardless of a group, you can hide things like advertisements only when
9550 the sender of an article has a certain mail address specified in
9551 @code{gnus-article-address-banner-alist}.
9555 @item gnus-article-address-banner-alist
9556 @vindex gnus-article-address-banner-alist
9557 Alist of mail addresses and banners. Each element has the form
9558 @code{(@var{address} . @var{banner})}, where @var{address} is a regexp
9559 matching a mail address in the From header, @var{banner} is one of a
9560 symbol @code{signature}, an item in @code{gnus-article-banner-alist},
9561 a regexp and @code{nil}. If @var{address} matches author's mail
9562 address, it will remove things like advertisements. For example, if a
9563 sender has the mail address @samp{hail@@yoo-hoo.co.jp} and there is a
9564 banner something like @samp{Do You Yoo-hoo!?} in all articles he
9565 sends, you can use the following element to remove them:
9568 ("@@yoo-hoo\\.co\\.jp\\'" .
9569 "\n_+\nDo You Yoo-hoo!\\?\n.*\n.*\n")
9575 @kindex W W c (Summary)
9576 @findex gnus-article-hide-citation
9577 Hide citation (@code{gnus-article-hide-citation}). Some variables for
9578 customizing the hiding:
9582 @item gnus-cited-opened-text-button-line-format
9583 @itemx gnus-cited-closed-text-button-line-format
9584 @vindex gnus-cited-closed-text-button-line-format
9585 @vindex gnus-cited-opened-text-button-line-format
9586 Gnus adds buttons to show where the cited text has been hidden, and to
9587 allow toggle hiding the text. The format of the variable is specified
9588 by these format-like variable (@pxref{Formatting Variables}). These
9593 Starting point of the hidden text.
9595 Ending point of the hidden text.
9597 Number of characters in the hidden region.
9599 Number of lines of hidden text.
9602 @item gnus-cited-lines-visible
9603 @vindex gnus-cited-lines-visible
9604 The number of lines at the beginning of the cited text to leave
9605 shown. This can also be a cons cell with the number of lines at the top
9606 and bottom of the text, respectively, to remain visible.
9611 @kindex W W C-c (Summary)
9612 @findex gnus-article-hide-citation-maybe
9614 Hide citation (@code{gnus-article-hide-citation-maybe}) depending on the
9615 following two variables:
9618 @item gnus-cite-hide-percentage
9619 @vindex gnus-cite-hide-percentage
9620 If the cited text is of a bigger percentage than this variable (default
9621 50), hide the cited text.
9623 @item gnus-cite-hide-absolute
9624 @vindex gnus-cite-hide-absolute
9625 The cited text must have at least this length (default 10) before it
9630 @kindex W W C (Summary)
9631 @findex gnus-article-hide-citation-in-followups
9632 Hide cited text in articles that aren't roots
9633 (@code{gnus-article-hide-citation-in-followups}). This isn't very
9634 useful as an interactive command, but might be a handy function to stick
9635 have happen automatically (@pxref{Customizing Articles}).
9639 All these ``hiding'' commands are toggles, but if you give a negative
9640 prefix to these commands, they will show what they have previously
9641 hidden. If you give a positive prefix, they will always hide.
9643 Also @pxref{Article Highlighting} for further variables for
9644 citation customization.
9646 @xref{Customizing Articles}, for how to hide article elements
9650 @node Article Washing
9651 @subsection Article Washing
9653 @cindex article washing
9655 We call this ``article washing'' for a really good reason. Namely, the
9656 @kbd{A} key was taken, so we had to use the @kbd{W} key instead.
9658 @dfn{Washing} is defined by us as ``changing something from something to
9659 something else'', but normally results in something looking better.
9662 @xref{Customizing Articles}, if you want to change how Gnus displays
9663 articles by default.
9668 This is not really washing, it's sort of the opposite of washing. If
9669 you type this, you see the article exactly as it exists on disk or on
9673 Force redisplaying of the current article
9674 (@code{gnus-summary-show-article}). This is also not really washing.
9675 If you type this, you see the article without any previously applied
9676 interactive Washing functions but with all default treatments
9677 (@pxref{Customizing Articles}).
9680 @kindex W l (Summary)
9681 @findex gnus-summary-stop-page-breaking
9682 Remove page breaks from the current article
9683 (@code{gnus-summary-stop-page-breaking}). @xref{Misc Article}, for page
9687 @kindex W r (Summary)
9688 @findex gnus-summary-caesar-message
9689 @c @icon{gnus-summary-caesar-message}
9690 Do a Caesar rotate (rot13) on the article buffer
9691 (@code{gnus-summary-caesar-message}).
9692 Unreadable articles that tell you to read them with Caesar rotate or rot13.
9693 (Typically offensive jokes and such.)
9695 It's commonly called ``rot13'' because each letter is rotated 13
9696 positions in the alphabet, e. g. @samp{B} (letter #2) -> @samp{O} (letter
9697 #15). It is sometimes referred to as ``Caesar rotate'' because Caesar
9698 is rumored to have employed this form of, uh, somewhat weak encryption.
9701 @kindex W m (Summary)
9702 @findex gnus-summary-morse-message
9703 Morse decode the article buffer (@code{gnus-summary-morse-message}).
9706 @kindex W i (Summary)
9707 @findex gnus-summary-idna-message
9708 Decode IDNA encoded domain names in the current articles. IDNA
9709 encoded domain names looks like @samp{xn--bar}. If a string remain
9710 unencoded after running invoking this, it is likely an invalid IDNA
9711 string (@samp{xn--bar} is invalid). You must have GNU Libidn
9712 (@url{http://www.gnu.org/software/libidn/}) installed for this command
9717 @kindex W t (Summary)
9719 @findex gnus-summary-toggle-header
9720 Toggle whether to display all headers in the article buffer
9721 (@code{gnus-summary-toggle-header}).
9724 @kindex W v (Summary)
9725 @findex gnus-summary-verbose-headers
9726 Toggle whether to display all headers in the article buffer permanently
9727 (@code{gnus-summary-verbose-headers}).
9730 @kindex W o (Summary)
9731 @findex gnus-article-treat-overstrike
9732 Treat overstrike (@code{gnus-article-treat-overstrike}).
9735 @kindex W d (Summary)
9736 @findex gnus-article-treat-dumbquotes
9737 @vindex gnus-article-dumbquotes-map
9739 @cindex M****s*** sm*rtq**t*s
9741 Treat M****s*** sm*rtq**t*s according to
9742 @code{gnus-article-dumbquotes-map}
9743 (@code{gnus-article-treat-dumbquotes}). Note that this function guesses
9744 whether a character is a sm*rtq**t* or not, so it should only be used
9747 Sm*rtq**t*s are M****s***'s unilateral extension to the character map in
9748 an attempt to provide more quoting characters. If you see something
9749 like @code{\222} or @code{\264} where you're expecting some kind of
9750 apostrophe or quotation mark, then try this wash.
9753 @kindex W Y f (Summary)
9754 @findex gnus-article-outlook-deuglify-article
9755 @cindex Outlook Express
9756 Full deuglify of broken Outlook (Express) articles: Treat dumbquotes,
9757 unwrap lines, repair attribution and rearrange citation.
9758 (@code{gnus-article-outlook-deuglify-article}).
9761 @kindex W Y u (Summary)
9762 @findex gnus-article-outlook-unwrap-lines
9763 @vindex gnus-outlook-deuglify-unwrap-min
9764 @vindex gnus-outlook-deuglify-unwrap-max
9765 Unwrap lines that appear to be wrapped citation lines. You can control
9766 what lines will be unwrapped by frobbing
9767 @code{gnus-outlook-deuglify-unwrap-min} and
9768 @code{gnus-outlook-deuglify-unwrap-max}, indicating the minimum and
9769 maximum length of an unwrapped citation line.
9770 (@code{gnus-article-outlook-unwrap-lines}).
9773 @kindex W Y a (Summary)
9774 @findex gnus-article-outlook-repair-attribution
9775 Repair a broken attribution line.@*
9776 (@code{gnus-article-outlook-repair-attribution}).
9779 @kindex W Y c (Summary)
9780 @findex gnus-article-outlook-rearrange-citation
9781 Repair broken citations by rearranging the text.
9782 (@code{gnus-article-outlook-rearrange-citation}).
9785 @kindex W w (Summary)
9786 @findex gnus-article-fill-cited-article
9787 Do word wrap (@code{gnus-article-fill-cited-article}).
9789 You can give the command a numerical prefix to specify the width to use
9793 @kindex W Q (Summary)
9794 @findex gnus-article-fill-long-lines
9795 Fill long lines (@code{gnus-article-fill-long-lines}).
9798 @kindex W C (Summary)
9799 @findex gnus-article-capitalize-sentences
9800 Capitalize the first word in each sentence
9801 (@code{gnus-article-capitalize-sentences}).
9804 @kindex W c (Summary)
9805 @findex gnus-article-remove-cr
9806 Translate CRLF pairs (i. e., @samp{^M}s on the end of the lines) into LF
9807 (this takes care of DOS line endings), and then translate any remaining
9808 CRs into LF (this takes care of Mac line endings)
9809 (@code{gnus-article-remove-cr}).
9812 @kindex W q (Summary)
9813 @findex gnus-article-de-quoted-unreadable
9814 Treat quoted-printable (@code{gnus-article-de-quoted-unreadable}).
9815 Quoted-Printable is one common @acronym{MIME} encoding employed when
9816 sending non-@acronym{ASCII} (i.e., 8-bit) articles. It typically
9817 makes strings like @samp{d@'ej@`a vu} look like @samp{d=E9j=E0 vu},
9818 which doesn't look very readable to me. Note that this is usually
9819 done automatically by Gnus if the message in question has a
9820 @code{Content-Transfer-Encoding} header that says that this encoding
9821 has been done. If a prefix is given, a charset will be asked for.
9824 @kindex W 6 (Summary)
9825 @findex gnus-article-de-base64-unreadable
9826 Treat base64 (@code{gnus-article-de-base64-unreadable}). Base64 is
9827 one common @acronym{MIME} encoding employed when sending
9828 non-@acronym{ASCII} (i.e., 8-bit) articles. Note that this is
9829 usually done automatically by Gnus if the message in question has a
9830 @code{Content-Transfer-Encoding} header that says that this encoding
9831 has been done. If a prefix is given, a charset will be asked for.
9834 @kindex W Z (Summary)
9835 @findex gnus-article-decode-HZ
9836 Treat HZ or HZP (@code{gnus-article-decode-HZ}). HZ (or HZP) is one
9837 common encoding employed when sending Chinese articles. It typically
9838 makes strings look like @samp{~@{<:Ky2;S@{#,NpJ)l6HK!#~@}}.
9841 @kindex W A (Summary)
9842 @findex gnus-article-treat-ansi-sequences
9843 @cindex @acronym{ANSI} control sequences
9844 Translate @acronym{ANSI} SGR control sequences into overlays or
9845 extents (@code{gnus-article-treat-ansi-sequences}). @acronym{ANSI}
9846 sequences are used in some Chinese hierarchies for highlighting.
9849 @kindex W u (Summary)
9850 @findex gnus-article-unsplit-urls
9851 Remove newlines from within URLs. Some mailers insert newlines into
9852 outgoing email messages to keep lines short. This reformatting can
9853 split long URLs onto multiple lines. Repair those URLs by removing
9854 the newlines (@code{gnus-article-unsplit-urls}).
9857 @kindex W h (Summary)
9858 @findex gnus-article-wash-html
9859 Treat @acronym{HTML} (@code{gnus-article-wash-html}). Note that this is
9860 usually done automatically by Gnus if the message in question has a
9861 @code{Content-Type} header that says that the message is @acronym{HTML}.
9863 If a prefix is given, a charset will be asked for. If it is a number,
9864 the charset defined in @code{gnus-summary-show-article-charset-alist}
9865 (@pxref{Paging the Article}) will be used.
9867 @vindex gnus-article-wash-function
9868 The default is to use the function specified by
9869 @code{mm-text-html-renderer} (@pxref{Display Customization, ,Display
9870 Customization, emacs-mime, The Emacs MIME Manual}) to convert the
9871 @acronym{HTML}, but this is controlled by the
9872 @code{gnus-article-wash-function} variable. Pre-defined functions you
9880 Use @uref{http://emacs-w3m.namazu.org/, emacs-w3m}.
9882 @item w3m-standalone
9883 Use @uref{http://w3m.sourceforge.net/, w3m}.
9886 Use @uref{http://links.sf.net/, Links}.
9889 Use @uref{http://lynx.isc.org/, Lynx}.
9892 Use html2text---a simple @acronym{HTML} converter included with Gnus.
9897 @kindex W b (Summary)
9898 @findex gnus-article-add-buttons
9899 Add clickable buttons to the article (@code{gnus-article-add-buttons}).
9900 @xref{Article Buttons}.
9903 @kindex W B (Summary)
9904 @findex gnus-article-add-buttons-to-head
9905 Add clickable buttons to the article headers
9906 (@code{gnus-article-add-buttons-to-head}).
9909 @kindex W p (Summary)
9910 @findex gnus-article-verify-x-pgp-sig
9911 Verify a signed control message
9912 (@code{gnus-article-verify-x-pgp-sig}). Control messages such as
9913 @code{newgroup} and @code{checkgroups} are usually signed by the
9914 hierarchy maintainer. You need to add the @acronym{PGP} public key of
9915 the maintainer to your keyring to verify the
9916 message.@footnote{@acronym{PGP} keys for many hierarchies are
9917 available at @uref{ftp://ftp.isc.org/pub/pgpcontrol/README.html}}
9920 @kindex W s (Summary)
9921 @findex gnus-summary-force-verify-and-decrypt
9922 Verify a signed (@acronym{PGP}, @acronym{PGP/MIME} or
9923 @acronym{S/MIME}) message
9924 (@code{gnus-summary-force-verify-and-decrypt}). @xref{Security}.
9927 @kindex W a (Summary)
9928 @findex gnus-article-strip-headers-in-body
9929 Strip headers like the @code{X-No-Archive} header from the beginning of
9930 article bodies (@code{gnus-article-strip-headers-in-body}).
9933 @kindex W E l (Summary)
9934 @findex gnus-article-strip-leading-blank-lines
9935 Remove all blank lines from the beginning of the article
9936 (@code{gnus-article-strip-leading-blank-lines}).
9939 @kindex W E m (Summary)
9940 @findex gnus-article-strip-multiple-blank-lines
9941 Replace all blank lines with empty lines and then all multiple empty
9942 lines with a single empty line.
9943 (@code{gnus-article-strip-multiple-blank-lines}).
9946 @kindex W E t (Summary)
9947 @findex gnus-article-remove-trailing-blank-lines
9948 Remove all blank lines at the end of the article
9949 (@code{gnus-article-remove-trailing-blank-lines}).
9952 @kindex W E a (Summary)
9953 @findex gnus-article-strip-blank-lines
9954 Do all the three commands above
9955 (@code{gnus-article-strip-blank-lines}).
9958 @kindex W E A (Summary)
9959 @findex gnus-article-strip-all-blank-lines
9960 Remove all blank lines
9961 (@code{gnus-article-strip-all-blank-lines}).
9964 @kindex W E s (Summary)
9965 @findex gnus-article-strip-leading-space
9966 Remove all white space from the beginning of all lines of the article
9967 body (@code{gnus-article-strip-leading-space}).
9970 @kindex W E e (Summary)
9971 @findex gnus-article-strip-trailing-space
9972 Remove all white space from the end of all lines of the article
9973 body (@code{gnus-article-strip-trailing-space}).
9977 @xref{Customizing Articles}, for how to wash articles automatically.
9980 @node Article Header
9981 @subsection Article Header
9983 These commands perform various transformations of article header.
9988 @kindex W G u (Summary)
9989 @findex gnus-article-treat-unfold-headers
9990 Unfold folded header lines (@code{gnus-article-treat-unfold-headers}).
9993 @kindex W G n (Summary)
9994 @findex gnus-article-treat-fold-newsgroups
9995 Fold the @code{Newsgroups} and @code{Followup-To} headers
9996 (@code{gnus-article-treat-fold-newsgroups}).
9999 @kindex W G f (Summary)
10000 @findex gnus-article-treat-fold-headers
10001 Fold all the message headers
10002 (@code{gnus-article-treat-fold-headers}).
10005 @kindex W E w (Summary)
10006 @findex gnus-article-remove-leading-whitespace
10007 Remove excessive whitespace from all headers
10008 (@code{gnus-article-remove-leading-whitespace}).
10013 @node Article Buttons
10014 @subsection Article Buttons
10017 People often include references to other stuff in articles, and it would
10018 be nice if Gnus could just fetch whatever it is that people talk about
10019 with the minimum of fuzz when you hit @kbd{RET} or use the middle mouse
10020 button on these references.
10022 @vindex gnus-button-man-handler
10023 Gnus adds @dfn{buttons} to certain standard references by default:
10024 Well-formed URLs, mail addresses, Message-IDs, Info links, man pages and
10025 Emacs or Gnus related references. This is controlled by two variables,
10026 one that handles article bodies and one that handles article heads:
10030 @item gnus-button-alist
10031 @vindex gnus-button-alist
10032 This is an alist where each entry has this form:
10035 (@var{regexp} @var{button-par} @var{use-p} @var{function} @var{data-par})
10041 All text that match this regular expression (case insensitive) will be
10042 considered an external reference. Here's a typical regexp that matches
10043 embedded URLs: @samp{<URL:\\([^\n\r>]*\\)>}. This can also be a
10044 variable containing a regexp, useful variables to use include
10045 @code{gnus-button-url-regexp} and @code{gnus-button-mid-or-mail-regexp}.
10048 Gnus has to know which parts of the matches is to be highlighted. This
10049 is a number that says what sub-expression of the regexp is to be
10050 highlighted. If you want it all highlighted, you use 0 here.
10053 This form will be @code{eval}ed, and if the result is non-@code{nil},
10054 this is considered a match. This is useful if you want extra sifting to
10055 avoid false matches. Often variables named
10056 @code{gnus-button-@var{*}-level} are used here, @xref{Article Button
10057 Levels}, but any other form may be used too.
10059 @c @code{use-p} is @code{eval}ed only if @code{regexp} matches.
10062 This function will be called when you click on this button.
10065 As with @var{button-par}, this is a sub-expression number, but this one
10066 says which part of the match is to be sent as data to @var{function}.
10070 So the full entry for buttonizing URLs is then
10073 ("<URL:\\([^\n\r>]*\\)>" 0 t gnus-button-url 1)
10076 @item gnus-header-button-alist
10077 @vindex gnus-header-button-alist
10078 This is just like the other alist, except that it is applied to the
10079 article head only, and that each entry has an additional element that is
10080 used to say what headers to apply the buttonize coding to:
10083 (@var{header} @var{regexp} @var{button-par} @var{use-p} @var{function} @var{data-par})
10086 @var{header} is a regular expression.
10089 @subsubsection Related variables and functions
10092 @item gnus-button-@var{*}-level
10093 @xref{Article Button Levels}.
10095 @c Stuff related to gnus-button-browse-level
10097 @item gnus-button-url-regexp
10098 @vindex gnus-button-url-regexp
10099 A regular expression that matches embedded URLs. It is used in the
10100 default values of the variables above.
10102 @c Stuff related to gnus-button-man-level
10104 @item gnus-button-man-handler
10105 @vindex gnus-button-man-handler
10106 The function to use for displaying man pages. It must take at least one
10107 argument with a string naming the man page.
10109 @c Stuff related to gnus-button-message-level
10111 @item gnus-button-mid-or-mail-regexp
10112 @vindex gnus-button-mid-or-mail-regexp
10113 Regular expression that matches a message ID or a mail address.
10115 @item gnus-button-prefer-mid-or-mail
10116 @vindex gnus-button-prefer-mid-or-mail
10117 This variable determines what to do when the button on a string as
10118 @samp{foo123@@bar.invalid} is pushed. Strings like this can be either a
10119 message ID or a mail address. If it is one of the symbols @code{mid} or
10120 @code{mail}, Gnus will always assume that the string is a message ID or
10121 a mail address, respectively. If this variable is set to the symbol
10122 @code{ask}, always query the user what to do. If it is a function, this
10123 function will be called with the string as its only argument. The
10124 function must return @code{mid}, @code{mail}, @code{invalid} or
10125 @code{ask}. The default value is the function
10126 @code{gnus-button-mid-or-mail-heuristic}.
10128 @item gnus-button-mid-or-mail-heuristic
10129 @findex gnus-button-mid-or-mail-heuristic
10130 Function that guesses whether its argument is a message ID or a mail
10131 address. Returns @code{mid} if it's a message IDs, @code{mail} if
10132 it's a mail address, @code{ask} if unsure and @code{invalid} if the
10135 @item gnus-button-mid-or-mail-heuristic-alist
10136 @vindex gnus-button-mid-or-mail-heuristic-alist
10137 An alist of @code{(RATE . REGEXP)} pairs used by the function
10138 @code{gnus-button-mid-or-mail-heuristic}.
10140 @c Stuff related to gnus-button-tex-level
10142 @item gnus-button-ctan-handler
10143 @findex gnus-button-ctan-handler
10144 The function to use for displaying CTAN links. It must take one
10145 argument, the string naming the URL.
10147 @item gnus-ctan-url
10148 @vindex gnus-ctan-url
10149 Top directory of a CTAN (Comprehensive TeX Archive Network) archive used
10150 by @code{gnus-button-ctan-handler}.
10154 @item gnus-article-button-face
10155 @vindex gnus-article-button-face
10156 Face used on buttons.
10158 @item gnus-article-mouse-face
10159 @vindex gnus-article-mouse-face
10160 Face used when the mouse cursor is over a button.
10164 @xref{Customizing Articles}, for how to buttonize articles automatically.
10167 @node Article Button Levels
10168 @subsection Article button levels
10169 @cindex button levels
10170 The higher the value of the variables @code{gnus-button-@var{*}-level},
10171 the more buttons will appear. If the level is zero, no corresponding
10172 buttons are displayed. With the default value (which is 5) you should
10173 already see quite a lot of buttons. With higher levels, you will see
10174 more buttons, but you may also get more false positives. To avoid them,
10175 you can set the variables @code{gnus-button-@var{*}-level} local to
10176 specific groups (@pxref{Group Parameters}). Here's an example for the
10177 variable @code{gnus-parameters}:
10180 ;; @r{increase @code{gnus-button-*-level} in some groups:}
10181 (setq gnus-parameters
10182 '(("\\<\\(emacs\\|gnus\\)\\>" (gnus-button-emacs-level 10))
10183 ("\\<unix\\>" (gnus-button-man-level 10))
10184 ("\\<tex\\>" (gnus-button-tex-level 10))))
10189 @item gnus-button-browse-level
10190 @vindex gnus-button-browse-level
10191 Controls the display of references to message IDs, mail addresses and
10192 news URLs. Related variables and functions include
10193 @code{gnus-button-url-regexp}, @code{browse-url}, and
10194 @code{browse-url-browser-function}.
10196 @item gnus-button-emacs-level
10197 @vindex gnus-button-emacs-level
10198 Controls the display of Emacs or Gnus references. Related functions are
10199 @code{gnus-button-handle-custom},
10200 @code{gnus-button-handle-describe-function},
10201 @code{gnus-button-handle-describe-variable},
10202 @code{gnus-button-handle-symbol},
10203 @code{gnus-button-handle-describe-key},
10204 @code{gnus-button-handle-apropos},
10205 @code{gnus-button-handle-apropos-command},
10206 @code{gnus-button-handle-apropos-variable},
10207 @code{gnus-button-handle-apropos-documentation}, and
10208 @code{gnus-button-handle-library}.
10210 @item gnus-button-man-level
10211 @vindex gnus-button-man-level
10212 Controls the display of references to (Unix) man pages.
10213 See @code{gnus-button-man-handler}.
10215 @item gnus-button-message-level
10216 @vindex gnus-button-message-level
10217 Controls the display of message IDs, mail addresses and news URLs.
10218 Related variables and functions include
10219 @code{gnus-button-mid-or-mail-regexp},
10220 @code{gnus-button-prefer-mid-or-mail},
10221 @code{gnus-button-mid-or-mail-heuristic}, and
10222 @code{gnus-button-mid-or-mail-heuristic-alist}.
10224 @item gnus-button-tex-level
10225 @vindex gnus-button-tex-level
10226 Controls the display of references to @TeX{} or LaTeX stuff, e.g. for CTAN
10227 URLs. See the variables @code{gnus-ctan-url},
10228 @code{gnus-button-ctan-handler},
10229 @code{gnus-button-ctan-directory-regexp}, and
10230 @code{gnus-button-handle-ctan-bogus-regexp}.
10236 @subsection Article Date
10238 The date is most likely generated in some obscure timezone you've never
10239 heard of, so it's quite nice to be able to find out what the time was
10240 when the article was sent.
10245 @kindex W T u (Summary)
10246 @findex gnus-article-date-ut
10247 Display the date in UT (aka. GMT, aka ZULU)
10248 (@code{gnus-article-date-ut}).
10251 @kindex W T i (Summary)
10252 @findex gnus-article-date-iso8601
10254 Display the date in international format, aka. ISO 8601
10255 (@code{gnus-article-date-iso8601}).
10258 @kindex W T l (Summary)
10259 @findex gnus-article-date-local
10260 Display the date in the local timezone (@code{gnus-article-date-local}).
10263 @kindex W T p (Summary)
10264 @findex gnus-article-date-english
10265 Display the date in a format that's easily pronounceable in English
10266 (@code{gnus-article-date-english}).
10269 @kindex W T s (Summary)
10270 @vindex gnus-article-time-format
10271 @findex gnus-article-date-user
10272 @findex format-time-string
10273 Display the date using a user-defined format
10274 (@code{gnus-article-date-user}). The format is specified by the
10275 @code{gnus-article-time-format} variable, and is a string that's passed
10276 to @code{format-time-string}. See the documentation of that variable
10277 for a list of possible format specs.
10280 @kindex W T e (Summary)
10281 @findex gnus-article-date-lapsed
10282 @findex gnus-start-date-timer
10283 @findex gnus-stop-date-timer
10284 Say how much time has elapsed between the article was posted and now
10285 (@code{gnus-article-date-lapsed}). It looks something like:
10288 X-Sent: 6 weeks, 4 days, 1 hour, 3 minutes, 8 seconds ago
10291 @vindex gnus-article-date-lapsed-new-header
10292 The value of @code{gnus-article-date-lapsed-new-header} determines
10293 whether this header will just be added below the old Date one, or will
10296 An advantage of using Gnus to read mail is that it converts simple bugs
10297 into wonderful absurdities.
10299 If you want to have this line updated continually, you can put
10302 (gnus-start-date-timer)
10305 in your @file{~/.gnus.el} file, or you can run it off of some hook. If
10306 you want to stop the timer, you can use the @code{gnus-stop-date-timer}
10310 @kindex W T o (Summary)
10311 @findex gnus-article-date-original
10312 Display the original date (@code{gnus-article-date-original}). This can
10313 be useful if you normally use some other conversion function and are
10314 worried that it might be doing something totally wrong. Say, claiming
10315 that the article was posted in 1854. Although something like that is
10316 @emph{totally} impossible. Don't you trust me? *titter*
10320 @xref{Customizing Articles}, for how to display the date in your
10321 preferred format automatically.
10324 @node Article Display
10325 @subsection Article Display
10330 These commands add various frivolous display gimmicks to the article
10331 buffer in Emacs versions that support them.
10333 @code{X-Face} headers are small black-and-white images supplied by the
10334 message headers (@pxref{X-Face}).
10336 @code{Face} headers are small colored images supplied by the message
10337 headers (@pxref{Face}).
10339 Smileys are those little @samp{:-)} symbols that people like to litter
10340 their messages with (@pxref{Smileys}).
10342 Picons, on the other hand, reside on your own system, and Gnus will
10343 try to match the headers to what you have (@pxref{Picons}).
10345 All these functions are toggles---if the elements already exist,
10346 they'll be removed.
10350 @kindex W D x (Summary)
10351 @findex gnus-article-display-x-face
10352 Display an @code{X-Face} in the @code{From} header.
10353 (@code{gnus-article-display-x-face}).
10356 @kindex W D d (Summary)
10357 @findex gnus-article-display-face
10358 Display a @code{Face} in the @code{From} header.
10359 (@code{gnus-article-display-face}).
10362 @kindex W D s (Summary)
10363 @findex gnus-treat-smiley
10364 Display smileys (@code{gnus-treat-smiley}).
10367 @kindex W D f (Summary)
10368 @findex gnus-treat-from-picon
10369 Piconify the @code{From} header (@code{gnus-treat-from-picon}).
10372 @kindex W D m (Summary)
10373 @findex gnus-treat-mail-picon
10374 Piconify all mail headers (i. e., @code{Cc}, @code{To})
10375 (@code{gnus-treat-mail-picon}).
10378 @kindex W D n (Summary)
10379 @findex gnus-treat-newsgroups-picon
10380 Piconify all news headers (i. e., @code{Newsgroups} and
10381 @code{Followup-To}) (@code{gnus-treat-newsgroups-picon}).
10384 @kindex W D D (Summary)
10385 @findex gnus-article-remove-images
10386 Remove all images from the article buffer
10387 (@code{gnus-article-remove-images}).
10393 @node Article Signature
10394 @subsection Article Signature
10396 @cindex article signature
10398 @vindex gnus-signature-separator
10399 Each article is divided into two parts---the head and the body. The
10400 body can be divided into a signature part and a text part. The variable
10401 that says what is to be considered a signature is
10402 @code{gnus-signature-separator}. This is normally the standard
10403 @samp{^-- $} as mandated by son-of-RFC 1036. However, many people use
10404 non-standard signature separators, so this variable can also be a list
10405 of regular expressions to be tested, one by one. (Searches are done
10406 from the end of the body towards the beginning.) One likely value is:
10409 (setq gnus-signature-separator
10410 '("^-- $" ; @r{The standard}
10411 "^-- *$" ; @r{A common mangling}
10412 "^-------*$" ; @r{Many people just use a looong}
10413 ; @r{line of dashes. Shame!}
10414 "^ *--------*$" ; @r{Double-shame!}
10415 "^________*$" ; @r{Underscores are also popular}
10416 "^========*$")) ; @r{Pervert!}
10419 The more permissive you are, the more likely it is that you'll get false
10422 @vindex gnus-signature-limit
10423 @code{gnus-signature-limit} provides a limit to what is considered a
10424 signature when displaying articles.
10428 If it is an integer, no signature may be longer (in characters) than
10431 If it is a floating point number, no signature may be longer (in lines)
10434 If it is a function, the function will be called without any parameters,
10435 and if it returns @code{nil}, there is no signature in the buffer.
10437 If it is a string, it will be used as a regexp. If it matches, the text
10438 in question is not a signature.
10441 This variable can also be a list where the elements may be of the types
10442 listed above. Here's an example:
10445 (setq gnus-signature-limit
10446 '(200.0 "^---*Forwarded article"))
10449 This means that if there are more than 200 lines after the signature
10450 separator, or the text after the signature separator is matched by
10451 the regular expression @samp{^---*Forwarded article}, then it isn't a
10452 signature after all.
10455 @node Article Miscellanea
10456 @subsection Article Miscellanea
10460 @kindex A t (Summary)
10461 @findex gnus-article-babel
10462 Translate the article from one language to another
10463 (@code{gnus-article-babel}).
10468 @node MIME Commands
10469 @section MIME Commands
10470 @cindex MIME decoding
10471 @cindex attachments
10472 @cindex viewing attachments
10474 The following commands all understand the numerical prefix. For
10475 instance, @kbd{3 K v} means ``view the third @acronym{MIME} part''.
10480 @kindex b (Summary)
10481 @kindex K v (Summary)
10482 View the @acronym{MIME} part.
10485 @kindex K o (Summary)
10486 Save the @acronym{MIME} part.
10489 @kindex K O (Summary)
10490 Prompt for a file name, then save the @acronym{MIME} part and strip it
10491 from the article. The stripped @acronym{MIME} object will be referred
10492 via the message/external-body @acronym{MIME} type.
10495 @kindex K r (Summary)
10496 Replace the @acronym{MIME} part with an external body.
10499 @kindex K d (Summary)
10500 Delete the @acronym{MIME} part and add some information about the
10504 @kindex K c (Summary)
10505 Copy the @acronym{MIME} part.
10508 @kindex K e (Summary)
10509 View the @acronym{MIME} part externally.
10512 @kindex K i (Summary)
10513 View the @acronym{MIME} part internally.
10516 @kindex K | (Summary)
10517 Pipe the @acronym{MIME} part to an external command.
10520 The rest of these @acronym{MIME} commands do not use the numerical prefix in
10525 @kindex K H (Summary)
10526 @findex gnus-article-browse-html-article
10527 View @samp{text/html} parts of the current article with a WWW browser.
10528 Inline images embedded in a message using the @code{cid} scheme, as they
10529 are generally considered to be safe, will be processed properly. The
10530 message header is added to the beginning of every @acronym{HTML} part
10531 unless the prefix argument is given.
10533 Warning: Spammers use links to images (using the @code{http} scheme) in
10534 @acronym{HTML} articles to verify whether you have read the message. As
10535 this command passes the @acronym{HTML} content to the browser without
10536 eliminating these ``web bugs'' you should only use it for mails from
10539 If you always want to display @acronym{HTML} parts in the browser, set
10540 @code{mm-text-html-renderer} to @code{nil}.
10542 This command creates temporary files to pass @acronym{HTML} contents
10543 including images if any to the browser, and deletes them when exiting
10544 the group (if you want).
10547 @kindex K b (Summary)
10548 Make all the @acronym{MIME} parts have buttons in front of them. This is
10549 mostly useful if you wish to save (or perform other actions) on inlined
10553 @kindex K m (Summary)
10554 @findex gnus-summary-repair-multipart
10555 Some multipart messages are transmitted with missing or faulty headers.
10556 This command will attempt to ``repair'' these messages so that they can
10557 be viewed in a more pleasant manner
10558 (@code{gnus-summary-repair-multipart}).
10561 @kindex X m (Summary)
10562 @findex gnus-summary-save-parts
10563 Save all parts matching a @acronym{MIME} type to a directory
10564 (@code{gnus-summary-save-parts}). Understands the process/prefix
10565 convention (@pxref{Process/Prefix}).
10568 @kindex M-t (Summary)
10569 @findex gnus-summary-toggle-display-buttonized
10570 Toggle the buttonized display of the article buffer
10571 (@code{gnus-summary-toggle-display-buttonized}).
10574 @kindex W M w (Summary)
10575 @findex gnus-article-decode-mime-words
10576 Decode RFC 2047-encoded words in the article headers
10577 (@code{gnus-article-decode-mime-words}).
10580 @kindex W M c (Summary)
10581 @findex gnus-article-decode-charset
10582 Decode encoded article bodies as well as charsets
10583 (@code{gnus-article-decode-charset}).
10585 This command looks in the @code{Content-Type} header to determine the
10586 charset. If there is no such header in the article, you can give it a
10587 prefix, which will prompt for the charset to decode as. In regional
10588 groups where people post using some common encoding (but do not
10589 include @acronym{MIME} headers), you can set the @code{charset} group/topic
10590 parameter to the required charset (@pxref{Group Parameters}).
10593 @kindex W M v (Summary)
10594 @findex gnus-mime-view-all-parts
10595 View all the @acronym{MIME} parts in the current article
10596 (@code{gnus-mime-view-all-parts}).
10600 Relevant variables:
10603 @item gnus-ignored-mime-types
10604 @vindex gnus-ignored-mime-types
10605 This is a list of regexps. @acronym{MIME} types that match a regexp from
10606 this list will be completely ignored by Gnus. The default value is
10609 To have all Vcards be ignored, you'd say something like this:
10612 (setq gnus-ignored-mime-types
10616 @item gnus-article-loose-mime
10617 @vindex gnus-article-loose-mime
10618 If non-@code{nil}, Gnus won't require the @samp{MIME-Version} header
10619 before interpreting the message as a @acronym{MIME} message. This helps
10620 when reading messages from certain broken mail user agents. The
10621 default is @code{t}.
10623 @item gnus-article-emulate-mime
10624 @vindex gnus-article-emulate-mime
10627 There are other, non-@acronym{MIME} encoding methods used. The most common
10628 is @samp{uuencode}, but yEncode is also getting to be popular. If
10629 this variable is non-@code{nil}, Gnus will look in message bodies to
10630 see if it finds these encodings, and if so, it'll run them through the
10631 Gnus @acronym{MIME} machinery. The default is @code{t}. Only
10632 single-part yEnc encoded attachments can be decoded. There's no support
10633 for encoding in Gnus.
10635 @item gnus-unbuttonized-mime-types
10636 @vindex gnus-unbuttonized-mime-types
10637 This is a list of regexps. @acronym{MIME} types that match a regexp from
10638 this list won't have @acronym{MIME} buttons inserted unless they aren't
10639 displayed or this variable is overridden by
10640 @code{gnus-buttonized-mime-types}. The default value is
10641 @code{(".*/.*")}. This variable is only used when
10642 @code{gnus-inhibit-mime-unbuttonizing} is @code{nil}.
10644 @item gnus-buttonized-mime-types
10645 @vindex gnus-buttonized-mime-types
10646 This is a list of regexps. @acronym{MIME} types that match a regexp from
10647 this list will have @acronym{MIME} buttons inserted unless they aren't
10648 displayed. This variable overrides
10649 @code{gnus-unbuttonized-mime-types}. The default value is @code{nil}.
10650 This variable is only used when @code{gnus-inhibit-mime-unbuttonizing}
10653 To see e.g. security buttons but no other buttons, you could set this
10654 variable to @code{("multipart/signed")} and leave
10655 @code{gnus-unbuttonized-mime-types} at the default value.
10657 You could also add @code{"multipart/alternative"} to this list to
10658 display radio buttons that allow you to choose one of two media types
10659 those mails include. See also @code{mm-discouraged-alternatives}
10660 (@pxref{Display Customization, ,Display Customization, emacs-mime, The
10661 Emacs MIME Manual}).
10663 @item gnus-inhibit-mime-unbuttonizing
10664 @vindex gnus-inhibit-mime-unbuttonizing
10665 If this is non-@code{nil}, then all @acronym{MIME} parts get buttons. The
10666 default value is @code{nil}.
10668 @item gnus-article-mime-part-function
10669 @vindex gnus-article-mime-part-function
10670 For each @acronym{MIME} part, this function will be called with the @acronym{MIME}
10671 handle as the parameter. The function is meant to be used to allow
10672 users to gather information from the article (e. g., add Vcard info to
10673 the bbdb database) or to do actions based on parts (e. g., automatically
10674 save all jpegs into some directory).
10676 Here's an example function the does the latter:
10679 (defun my-save-all-jpeg-parts (handle)
10680 (when (equal (car (mm-handle-type handle)) "image/jpeg")
10682 (insert (mm-get-part handle))
10683 (write-region (point-min) (point-max)
10684 (read-file-name "Save jpeg to: ")))))
10685 (setq gnus-article-mime-part-function
10686 'my-save-all-jpeg-parts)
10689 @vindex gnus-mime-multipart-functions
10690 @item gnus-mime-multipart-functions
10691 Alist of @acronym{MIME} multipart types and functions to handle them.
10693 @vindex gnus-mime-display-multipart-alternative-as-mixed
10694 @item gnus-mime-display-multipart-alternative-as-mixed
10695 Display "multipart/alternative" parts as "multipart/mixed".
10697 @vindex gnus-mime-display-multipart-related-as-mixed
10698 @item gnus-mime-display-multipart-related-as-mixed
10699 Display "multipart/related" parts as "multipart/mixed".
10701 If displaying @samp{text/html} is discouraged, see
10702 @code{mm-discouraged-alternatives}, images or other material inside a
10703 "multipart/related" part might be overlooked when this variable is
10704 @code{nil}. @ref{Display Customization, Display Customization, ,
10705 emacs-mime, Emacs-Mime Manual}.
10707 @vindex gnus-mime-display-multipart-as-mixed
10708 @item gnus-mime-display-multipart-as-mixed
10709 Display "multipart" parts as "multipart/mixed". If @code{t}, it
10710 overrides @code{nil} values of
10711 @code{gnus-mime-display-multipart-alternative-as-mixed} and
10712 @code{gnus-mime-display-multipart-related-as-mixed}.
10714 @vindex mm-file-name-rewrite-functions
10715 @item mm-file-name-rewrite-functions
10716 List of functions used for rewriting file names of @acronym{MIME} parts.
10717 Each function takes a file name as input and returns a file name.
10719 Ready-made functions include@*
10720 @code{mm-file-name-delete-whitespace},
10721 @code{mm-file-name-trim-whitespace},
10722 @code{mm-file-name-collapse-whitespace}, and
10723 @code{mm-file-name-replace-whitespace}. The later uses the value of
10724 the variable @code{mm-file-name-replace-whitespace} to replace each
10725 whitespace character in a file name with that string; default value
10726 is @code{"_"} (a single underscore).
10727 @findex mm-file-name-delete-whitespace
10728 @findex mm-file-name-trim-whitespace
10729 @findex mm-file-name-collapse-whitespace
10730 @findex mm-file-name-replace-whitespace
10731 @vindex mm-file-name-replace-whitespace
10733 The standard functions @code{capitalize}, @code{downcase},
10734 @code{upcase}, and @code{upcase-initials} may be useful, too.
10736 Everybody knows that whitespace characters in file names are evil,
10737 except those who don't know. If you receive lots of attachments from
10738 such unenlightened users, you can make live easier by adding
10741 (setq mm-file-name-rewrite-functions
10742 '(mm-file-name-trim-whitespace
10743 mm-file-name-collapse-whitespace
10744 mm-file-name-replace-whitespace))
10748 to your @file{~/.gnus.el} file.
10757 People use different charsets, and we have @acronym{MIME} to let us know what
10758 charsets they use. Or rather, we wish we had. Many people use
10759 newsreaders and mailers that do not understand or use @acronym{MIME}, and
10760 just send out messages without saying what character sets they use. To
10761 help a bit with this, some local news hierarchies have policies that say
10762 what character set is the default. For instance, the @samp{fj}
10763 hierarchy uses @code{iso-2022-jp}.
10765 @vindex gnus-group-charset-alist
10766 This knowledge is encoded in the @code{gnus-group-charset-alist}
10767 variable, which is an alist of regexps (use the first item to match full
10768 group names) and default charsets to be used when reading these groups.
10770 @vindex gnus-newsgroup-ignored-charsets
10771 In addition, some people do use soi-disant @acronym{MIME}-aware agents that
10772 aren't. These blithely mark messages as being in @code{iso-8859-1}
10773 even if they really are in @code{koi-8}. To help here, the
10774 @code{gnus-newsgroup-ignored-charsets} variable can be used. The
10775 charsets that are listed here will be ignored. The variable can be
10776 set on a group-by-group basis using the group parameters (@pxref{Group
10777 Parameters}). The default value is @code{(unknown-8bit x-unknown)},
10778 which includes values some agents insist on having in there.
10780 @vindex gnus-group-posting-charset-alist
10781 When posting, @code{gnus-group-posting-charset-alist} is used to
10782 determine which charsets should not be encoded using the @acronym{MIME}
10783 encodings. For instance, some hierarchies discourage using
10784 quoted-printable header encoding.
10786 This variable is an alist of regexps and permitted unencoded charsets
10787 for posting. Each element of the alist has the form @code{(}@var{test
10788 header body-list}@code{)}, where:
10792 is either a regular expression matching the newsgroup header or a
10795 is the charset which may be left unencoded in the header (@code{nil}
10796 means encode all charsets),
10798 is a list of charsets which may be encoded using 8bit content-transfer
10799 encoding in the body, or one of the special values @code{nil} (always
10800 encode using quoted-printable) or @code{t} (always use 8bit).
10807 @cindex coding system aliases
10808 @cindex preferred charset
10810 @xref{Encoding Customization, , Encoding Customization, emacs-mime,
10811 The Emacs MIME Manual}, for additional variables that control which
10812 MIME charsets are used when sending messages.
10814 Other charset tricks that may be useful, although not Gnus-specific:
10816 If there are several @acronym{MIME} charsets that encode the same Emacs
10817 charset, you can choose what charset to use by saying the following:
10820 (put-charset-property 'cyrillic-iso8859-5
10821 'preferred-coding-system 'koi8-r)
10824 This means that Russian will be encoded using @code{koi8-r} instead of
10825 the default @code{iso-8859-5} @acronym{MIME} charset.
10827 If you want to read messages in @code{koi8-u}, you can cheat and say
10830 (define-coding-system-alias 'koi8-u 'koi8-r)
10833 This will almost do the right thing.
10835 And finally, to read charsets like @code{windows-1251}, you can say
10839 (codepage-setup 1251)
10840 (define-coding-system-alias 'windows-1251 'cp1251)
10844 @node Article Commands
10845 @section Article Commands
10852 @kindex A P (Summary)
10853 @vindex gnus-ps-print-hook
10854 @findex gnus-summary-print-article
10855 Generate and print a PostScript image of the article buffer
10856 (@code{gnus-summary-print-article}). @code{gnus-ps-print-hook} will
10857 be run just before printing the buffer. An alternative way to print
10858 article is to use Muttprint (@pxref{Saving Articles}).
10863 @node Summary Sorting
10864 @section Summary Sorting
10865 @cindex summary sorting
10867 You can have the summary buffer sorted in various ways, even though I
10868 can't really see why you'd want that.
10873 @kindex C-c C-s C-n (Summary)
10874 @findex gnus-summary-sort-by-number
10875 Sort by article number (@code{gnus-summary-sort-by-number}).
10877 @item C-c C-s C-m C-n
10878 @kindex C-c C-s C-n (Summary)
10879 @findex gnus-summary-sort-by-most-recent-number
10880 Sort by most recent article number
10881 (@code{gnus-summary-sort-by-most-recent-number}).
10884 @kindex C-c C-s C-a (Summary)
10885 @findex gnus-summary-sort-by-author
10886 Sort by author (@code{gnus-summary-sort-by-author}).
10889 @kindex C-c C-s C-t (Summary)
10890 @findex gnus-summary-sort-by-recipient
10891 Sort by recipient (@code{gnus-summary-sort-by-recipient}).
10894 @kindex C-c C-s C-s (Summary)
10895 @findex gnus-summary-sort-by-subject
10896 Sort by subject (@code{gnus-summary-sort-by-subject}).
10899 @kindex C-c C-s C-d (Summary)
10900 @findex gnus-summary-sort-by-date
10901 Sort by date (@code{gnus-summary-sort-by-date}).
10903 @item C-c C-s C-m C-d
10904 @kindex C-c C-s C-m C-d (Summary)
10905 @findex gnus-summary-sort-by-most-recent-date
10906 Sort by most recent date (@code{gnus-summary-sort-by-most-recent-date}).
10909 @kindex C-c C-s C-l (Summary)
10910 @findex gnus-summary-sort-by-lines
10911 Sort by lines (@code{gnus-summary-sort-by-lines}).
10914 @kindex C-c C-s C-c (Summary)
10915 @findex gnus-summary-sort-by-chars
10916 Sort by article length (@code{gnus-summary-sort-by-chars}).
10919 @kindex C-c C-s C-i (Summary)
10920 @findex gnus-summary-sort-by-score
10921 Sort by score (@code{gnus-summary-sort-by-score}).
10924 @kindex C-c C-s C-r (Summary)
10925 @findex gnus-summary-sort-by-random
10926 Randomize (@code{gnus-summary-sort-by-random}).
10929 @kindex C-c C-s C-o (Summary)
10930 @findex gnus-summary-sort-by-original
10931 Sort using the default sorting method
10932 (@code{gnus-summary-sort-by-original}).
10935 These functions will work both when you use threading and when you don't
10936 use threading. In the latter case, all summary lines will be sorted,
10937 line by line. In the former case, sorting will be done on a
10938 root-by-root basis, which might not be what you were looking for. To
10939 toggle whether to use threading, type @kbd{T T} (@pxref{Thread
10942 If a prefix argument if given, the sort order is reversed.
10945 @node Finding the Parent
10946 @section Finding the Parent
10947 @cindex parent articles
10948 @cindex referring articles
10952 @kindex ^ (Summary)
10953 @findex gnus-summary-refer-parent-article
10954 If you'd like to read the parent of the current article, and it is not
10955 displayed in the summary buffer, you might still be able to. That is,
10956 if the current group is fetched by @acronym{NNTP}, the parent hasn't expired
10957 and the @code{References} in the current article are not mangled, you
10958 can just press @kbd{^} or @kbd{A r}
10959 (@code{gnus-summary-refer-parent-article}). If everything goes well,
10960 you'll get the parent. If the parent is already displayed in the
10961 summary buffer, point will just move to this article.
10963 If given a positive numerical prefix, fetch that many articles back into
10964 the ancestry. If given a negative numerical prefix, fetch just that
10965 ancestor. So if you say @kbd{3 ^}, Gnus will fetch the parent, the
10966 grandparent and the grandgrandparent of the current article. If you say
10967 @kbd{-3 ^}, Gnus will only fetch the grandgrandparent of the current
10970 @item A R (Summary)
10971 @findex gnus-summary-refer-references
10972 @kindex A R (Summary)
10973 Fetch all articles mentioned in the @code{References} header of the
10974 article (@code{gnus-summary-refer-references}).
10976 @item A T (Summary)
10977 @findex gnus-summary-refer-thread
10978 @kindex A T (Summary)
10979 Display the full thread where the current article appears
10980 (@code{gnus-summary-refer-thread}). This command has to fetch all the
10981 headers in the current group to work, so it usually takes a while. If
10982 you do it often, you may consider setting @code{gnus-fetch-old-headers}
10983 to @code{invisible} (@pxref{Filling In Threads}). This won't have any
10984 visible effects normally, but it'll make this command work a whole lot
10985 faster. Of course, it'll make group entry somewhat slow.
10987 @vindex gnus-refer-thread-limit
10988 The @code{gnus-refer-thread-limit} variable says how many old (i. e.,
10989 articles before the first displayed in the current group) headers to
10990 fetch when doing this command. The default is 200. If @code{t}, all
10991 the available headers will be fetched. This variable can be overridden
10992 by giving the @kbd{A T} command a numerical prefix.
10994 @item M-^ (Summary)
10995 @findex gnus-summary-refer-article
10996 @kindex M-^ (Summary)
10998 @cindex fetching by Message-ID
10999 You can also ask Gnus for an arbitrary article, no matter what group it
11000 belongs to. @kbd{M-^} (@code{gnus-summary-refer-article}) will ask you
11001 for a @code{Message-ID}, which is one of those long, hard-to-read
11002 thingies that look something like @samp{<38o6up$6f2@@hymir.ifi.uio.no>}.
11003 You have to get it all exactly right. No fuzzy searches, I'm afraid.
11005 Gnus looks for the @code{Message-ID} in the headers that have already
11006 been fetched, but also tries all the select methods specified by
11007 @code{gnus-refer-article-method} if it is not found.
11010 @vindex gnus-refer-article-method
11011 If the group you are reading is located on a back end that does not
11012 support fetching by @code{Message-ID} very well (like @code{nnspool}),
11013 you can set @code{gnus-refer-article-method} to an @acronym{NNTP} method. It
11014 would, perhaps, be best if the @acronym{NNTP} server you consult is the one
11015 updating the spool you are reading from, but that's not really
11018 It can also be a list of select methods, as well as the special symbol
11019 @code{current}, which means to use the current select method. If it
11020 is a list, Gnus will try all the methods in the list until it finds a
11023 Here's an example setting that will first try the current method, and
11024 then ask Google if that fails:
11027 (setq gnus-refer-article-method
11029 (nnweb "google" (nnweb-type google))))
11032 Most of the mail back ends support fetching by @code{Message-ID}, but
11033 do not do a particularly excellent job at it. That is, @code{nnmbox},
11034 @code{nnbabyl}, @code{nnmaildir}, @code{nnml}, are able to locate
11035 articles from any groups, while @code{nnfolder}, and @code{nnimap} are
11036 only able to locate articles that have been posted to the current
11037 group. (Anything else would be too time consuming.) @code{nnmh} does
11038 not support this at all.
11041 @node Alternative Approaches
11042 @section Alternative Approaches
11044 Different people like to read news using different methods. This being
11045 Gnus, we offer a small selection of minor modes for the summary buffers.
11048 * Pick and Read:: First mark articles and then read them.
11049 * Binary Groups:: Auto-decode all articles.
11053 @node Pick and Read
11054 @subsection Pick and Read
11055 @cindex pick and read
11057 Some newsreaders (like @code{nn} and, uhm, @code{Netnews} on VM/CMS) use
11058 a two-phased reading interface. The user first marks in a summary
11059 buffer the articles she wants to read. Then she starts reading the
11060 articles with just an article buffer displayed.
11062 @findex gnus-pick-mode
11063 @kindex M-x gnus-pick-mode
11064 Gnus provides a summary buffer minor mode that allows
11065 this---@code{gnus-pick-mode}. This basically means that a few process
11066 mark commands become one-keystroke commands to allow easy marking, and
11067 it provides one additional command for switching to the summary buffer.
11069 Here are the available keystrokes when using pick mode:
11074 @findex gnus-pick-article-or-thread
11075 Pick the article or thread on the current line
11076 (@code{gnus-pick-article-or-thread}). If the variable
11077 @code{gnus-thread-hide-subtree} is true, then this key selects the
11078 entire thread when used at the first article of the thread. Otherwise,
11079 it selects just the article. If given a numerical prefix, go to that
11080 thread or article and pick it. (The line number is normally displayed
11081 at the beginning of the summary pick lines.)
11084 @kindex SPACE (Pick)
11085 @findex gnus-pick-next-page
11086 Scroll the summary buffer up one page (@code{gnus-pick-next-page}). If
11087 at the end of the buffer, start reading the picked articles.
11091 @findex gnus-pick-unmark-article-or-thread.
11092 Unpick the thread or article
11093 (@code{gnus-pick-unmark-article-or-thread}). If the variable
11094 @code{gnus-thread-hide-subtree} is true, then this key unpicks the
11095 thread if used at the first article of the thread. Otherwise it unpicks
11096 just the article. You can give this key a numerical prefix to unpick
11097 the thread or article at that line.
11101 @findex gnus-pick-start-reading
11102 @vindex gnus-pick-display-summary
11103 Start reading the picked articles (@code{gnus-pick-start-reading}). If
11104 given a prefix, mark all unpicked articles as read first. If
11105 @code{gnus-pick-display-summary} is non-@code{nil}, the summary buffer
11106 will still be visible when you are reading.
11110 All the normal summary mode commands are still available in the
11111 pick-mode, with the exception of @kbd{u}. However @kbd{!} is available
11112 which is mapped to the same function
11113 @code{gnus-summary-tick-article-forward}.
11115 If this sounds like a good idea to you, you could say:
11118 (add-hook 'gnus-summary-mode-hook 'gnus-pick-mode)
11121 @vindex gnus-pick-mode-hook
11122 @code{gnus-pick-mode-hook} is run in pick minor mode buffers.
11124 @vindex gnus-mark-unpicked-articles-as-read
11125 If @code{gnus-mark-unpicked-articles-as-read} is non-@code{nil}, mark
11126 all unpicked articles as read. The default is @code{nil}.
11128 @vindex gnus-summary-pick-line-format
11129 The summary line format in pick mode is slightly different from the
11130 standard format. At the beginning of each line the line number is
11131 displayed. The pick mode line format is controlled by the
11132 @code{gnus-summary-pick-line-format} variable (@pxref{Formatting
11133 Variables}). It accepts the same format specs that
11134 @code{gnus-summary-line-format} does (@pxref{Summary Buffer Lines}).
11137 @node Binary Groups
11138 @subsection Binary Groups
11139 @cindex binary groups
11141 @findex gnus-binary-mode
11142 @kindex M-x gnus-binary-mode
11143 If you spend much time in binary groups, you may grow tired of hitting
11144 @kbd{X u}, @kbd{n}, @kbd{RET} all the time. @kbd{M-x gnus-binary-mode}
11145 is a minor mode for summary buffers that makes all ordinary Gnus article
11146 selection functions uudecode series of articles and display the result
11147 instead of just displaying the articles the normal way.
11150 @findex gnus-binary-show-article
11151 The only way, in fact, to see the actual articles is the @kbd{g}
11152 command, when you have turned on this mode
11153 (@code{gnus-binary-show-article}).
11155 @vindex gnus-binary-mode-hook
11156 @code{gnus-binary-mode-hook} is called in binary minor mode buffers.
11160 @section Tree Display
11163 @vindex gnus-use-trees
11164 If you don't like the normal Gnus summary display, you might try setting
11165 @code{gnus-use-trees} to @code{t}. This will create (by default) an
11166 additional @dfn{tree buffer}. You can execute all summary mode commands
11167 in the tree buffer.
11169 There are a few variables to customize the tree display, of course:
11172 @item gnus-tree-mode-hook
11173 @vindex gnus-tree-mode-hook
11174 A hook called in all tree mode buffers.
11176 @item gnus-tree-mode-line-format
11177 @vindex gnus-tree-mode-line-format
11178 A format string for the mode bar in the tree mode buffers (@pxref{Mode
11179 Line Formatting}). The default is @samp{Gnus: %%b %S %Z}. For a list
11180 of valid specs, @pxref{Summary Buffer Mode Line}.
11182 @item gnus-selected-tree-face
11183 @vindex gnus-selected-tree-face
11184 Face used for highlighting the selected article in the tree buffer. The
11185 default is @code{modeline}.
11187 @item gnus-tree-line-format
11188 @vindex gnus-tree-line-format
11189 A format string for the tree nodes. The name is a bit of a misnomer,
11190 though---it doesn't define a line, but just the node. The default value
11191 is @samp{%(%[%3,3n%]%)}, which displays the first three characters of
11192 the name of the poster. It is vital that all nodes are of the same
11193 length, so you @emph{must} use @samp{%4,4n}-like specifiers.
11199 The name of the poster.
11201 The @code{From} header.
11203 The number of the article.
11205 The opening bracket.
11207 The closing bracket.
11212 @xref{Formatting Variables}.
11214 Variables related to the display are:
11217 @item gnus-tree-brackets
11218 @vindex gnus-tree-brackets
11219 This is used for differentiating between ``real'' articles and
11220 ``sparse'' articles. The format is
11222 ((@var{real-open} . @var{real-close})
11223 (@var{sparse-open} . @var{sparse-close})
11224 (@var{dummy-open} . @var{dummy-close}))
11226 and the default is @code{((?[ . ?]) (?( . ?)) (?@{ . ?@}) (?< . ?>))}.
11228 @item gnus-tree-parent-child-edges
11229 @vindex gnus-tree-parent-child-edges
11230 This is a list that contains the characters used for connecting parent
11231 nodes to their children. The default is @code{(?- ?\\ ?|)}.
11235 @item gnus-tree-minimize-window
11236 @vindex gnus-tree-minimize-window
11237 If this variable is non-@code{nil}, Gnus will try to keep the tree
11238 buffer as small as possible to allow more room for the other Gnus
11239 windows. If this variable is a number, the tree buffer will never be
11240 higher than that number. The default is @code{t}. Note that if you
11241 have several windows displayed side-by-side in a frame and the tree
11242 buffer is one of these, minimizing the tree window will also resize all
11243 other windows displayed next to it.
11245 You may also wish to add the following hook to keep the window minimized
11249 (add-hook 'gnus-configure-windows-hook
11250 'gnus-tree-perhaps-minimize)
11253 @item gnus-generate-tree-function
11254 @vindex gnus-generate-tree-function
11255 @findex gnus-generate-horizontal-tree
11256 @findex gnus-generate-vertical-tree
11257 The function that actually generates the thread tree. Two predefined
11258 functions are available: @code{gnus-generate-horizontal-tree} and
11259 @code{gnus-generate-vertical-tree} (which is the default).
11263 Here's an example from a horizontal tree buffer:
11266 @{***@}-(***)-[odd]-[Gun]
11276 Here's the same thread displayed in a vertical tree buffer:
11281 |--------------------------\-----\-----\
11282 (***) [Bjo] [Gun] [Gun]
11284 [odd] [Jan] [odd] (***) [Jor]
11286 [Gun] [Eri] [Eri] [odd]
11292 If you're using horizontal trees, it might be nice to display the trees
11293 side-by-side with the summary buffer. You could add something like the
11294 following to your @file{~/.gnus.el} file:
11297 (setq gnus-use-trees t
11298 gnus-generate-tree-function 'gnus-generate-horizontal-tree
11299 gnus-tree-minimize-window nil)
11300 (gnus-add-configuration
11304 (summary 0.75 point)
11309 @xref{Window Layout}.
11312 @node Mail Group Commands
11313 @section Mail Group Commands
11314 @cindex mail group commands
11316 Some commands only make sense in mail groups. If these commands are
11317 invalid in the current group, they will raise a hell and let you know.
11319 All these commands (except the expiry and edit commands) use the
11320 process/prefix convention (@pxref{Process/Prefix}).
11325 @kindex B e (Summary)
11326 @findex gnus-summary-expire-articles
11327 @cindex expiring mail
11328 Run all expirable articles in the current group through the expiry
11329 process (@code{gnus-summary-expire-articles}). That is, delete all
11330 expirable articles in the group that have been around for a while.
11331 (@pxref{Expiring Mail}).
11334 @kindex B C-M-e (Summary)
11335 @findex gnus-summary-expire-articles-now
11336 @cindex expiring mail
11337 Delete all the expirable articles in the group
11338 (@code{gnus-summary-expire-articles-now}). This means that @strong{all}
11339 articles eligible for expiry in the current group will
11340 disappear forever into that big @file{/dev/null} in the sky.
11343 @kindex B DEL (Summary)
11344 @cindex deleting mail
11345 @findex gnus-summary-delete-article
11346 @c @icon{gnus-summary-mail-delete}
11347 Delete the mail article. This is ``delete'' as in ``delete it from your
11348 disk forever and ever, never to return again.'' Use with caution.
11349 (@code{gnus-summary-delete-article}).
11352 @kindex B m (Summary)
11354 @findex gnus-summary-move-article
11355 @vindex gnus-preserve-marks
11356 Move the article from one mail group to another
11357 (@code{gnus-summary-move-article}). Marks will be preserved if
11358 @code{gnus-preserve-marks} is non-@code{nil} (which is the default).
11361 @kindex B c (Summary)
11363 @findex gnus-summary-copy-article
11364 @c @icon{gnus-summary-mail-copy}
11365 Copy the article from one group (mail group or not) to a mail group
11366 (@code{gnus-summary-copy-article}). Marks will be preserved if
11367 @code{gnus-preserve-marks} is non-@code{nil} (which is the default).
11370 @kindex B B (Summary)
11371 @cindex crosspost mail
11372 @findex gnus-summary-crosspost-article
11373 Crosspost the current article to some other group
11374 (@code{gnus-summary-crosspost-article}). This will create a new copy of
11375 the article in the other group, and the Xref headers of the article will
11376 be properly updated.
11379 @kindex B i (Summary)
11380 @findex gnus-summary-import-article
11381 Import an arbitrary file into the current mail newsgroup
11382 (@code{gnus-summary-import-article}). You will be prompted for a file
11383 name, a @code{From} header and a @code{Subject} header.
11386 @kindex B I (Summary)
11387 @findex gnus-summary-create-article
11388 Create an empty article in the current mail newsgroups
11389 (@code{gnus-summary-create-article}). You will be prompted for a
11390 @code{From} header and a @code{Subject} header.
11393 @kindex B r (Summary)
11394 @findex gnus-summary-respool-article
11395 @vindex gnus-summary-respool-default-method
11396 Respool the mail article (@code{gnus-summary-respool-article}).
11397 @code{gnus-summary-respool-default-method} will be used as the default
11398 select method when respooling. This variable is @code{nil} by default,
11399 which means that the current group select method will be used instead.
11400 Marks will be preserved if @code{gnus-preserve-marks} is non-@code{nil}
11401 (which is the default).
11405 @kindex B w (Summary)
11406 @kindex e (Summary)
11407 @findex gnus-summary-edit-article
11408 @kindex C-c C-c (Article)
11409 @findex gnus-summary-edit-article-done
11410 Edit the current article (@code{gnus-summary-edit-article}). To finish
11411 editing and make the changes permanent, type @kbd{C-c C-c}
11412 (@code{gnus-summary-edit-article-done}). If you give a prefix to the
11413 @kbd{C-c C-c} command, Gnus won't re-highlight the article.
11416 @kindex B q (Summary)
11417 @findex gnus-summary-respool-query
11418 If you want to re-spool an article, you might be curious as to what group
11419 the article will end up in before you do the re-spooling. This command
11420 will tell you (@code{gnus-summary-respool-query}).
11423 @kindex B t (Summary)
11424 @findex gnus-summary-respool-trace
11425 Similarly, this command will display all fancy splitting patterns used
11426 when respooling, if any (@code{gnus-summary-respool-trace}).
11429 @kindex B p (Summary)
11430 @findex gnus-summary-article-posted-p
11431 Some people have a tendency to send you ``courtesy'' copies when they
11432 follow up to articles you have posted. These usually have a
11433 @code{Newsgroups} header in them, but not always. This command
11434 (@code{gnus-summary-article-posted-p}) will try to fetch the current
11435 article from your news server (or rather, from
11436 @code{gnus-refer-article-method} or @code{gnus-select-method}) and will
11437 report back whether it found the article or not. Even if it says that
11438 it didn't find the article, it may have been posted anyway---mail
11439 propagation is much faster than news propagation, and the news copy may
11440 just not have arrived yet.
11443 @kindex K E (Summary)
11444 @findex gnus-article-encrypt-body
11445 @vindex gnus-article-encrypt-protocol
11446 Encrypt the body of an article (@code{gnus-article-encrypt-body}).
11447 The body is encrypted with the encryption protocol specified by the
11448 variable @code{gnus-article-encrypt-protocol}.
11452 @vindex gnus-move-split-methods
11453 @cindex moving articles
11454 If you move (or copy) articles regularly, you might wish to have Gnus
11455 suggest where to put the articles. @code{gnus-move-split-methods} is a
11456 variable that uses the same syntax as @code{gnus-split-methods}
11457 (@pxref{Saving Articles}). You may customize that variable to create
11458 suggestions you find reasonable. (Note that
11459 @code{gnus-move-split-methods} uses group names where
11460 @code{gnus-split-methods} uses file names.)
11463 (setq gnus-move-split-methods
11464 '(("^From:.*Lars Magne" "nnml:junk")
11465 ("^Subject:.*gnus" "nnfolder:important")
11466 (".*" "nnml:misc")))
11470 @node Various Summary Stuff
11471 @section Various Summary Stuff
11474 * Summary Group Information:: Information oriented commands.
11475 * Searching for Articles:: Multiple article commands.
11476 * Summary Generation Commands::
11477 * Really Various Summary Commands:: Those pesky non-conformant commands.
11481 @vindex gnus-summary-display-while-building
11482 @item gnus-summary-display-while-building
11483 If non-@code{nil}, show and update the summary buffer as it's being
11484 built. If @code{t}, update the buffer after every line is inserted.
11485 If the value is an integer, @var{n}, update the display every @var{n}
11486 lines. The default is @code{nil}.
11488 @vindex gnus-summary-display-arrow
11489 @item gnus-summary-display-arrow
11490 If non-@code{nil}, display an arrow in the fringe to indicate the
11493 @vindex gnus-summary-mode-hook
11494 @item gnus-summary-mode-hook
11495 This hook is called when creating a summary mode buffer.
11497 @vindex gnus-summary-generate-hook
11498 @item gnus-summary-generate-hook
11499 This is called as the last thing before doing the threading and the
11500 generation of the summary buffer. It's quite convenient for customizing
11501 the threading variables based on what data the newsgroup has. This hook
11502 is called from the summary buffer after most summary buffer variables
11505 @vindex gnus-summary-prepare-hook
11506 @item gnus-summary-prepare-hook
11507 It is called after the summary buffer has been generated. You might use
11508 it to, for instance, highlight lines or modify the look of the buffer in
11509 some other ungodly manner. I don't care.
11511 @vindex gnus-summary-prepared-hook
11512 @item gnus-summary-prepared-hook
11513 A hook called as the very last thing after the summary buffer has been
11516 @vindex gnus-summary-ignore-duplicates
11517 @item gnus-summary-ignore-duplicates
11518 When Gnus discovers two articles that have the same @code{Message-ID},
11519 it has to do something drastic. No articles are allowed to have the
11520 same @code{Message-ID}, but this may happen when reading mail from some
11521 sources. Gnus allows you to customize what happens with this variable.
11522 If it is @code{nil} (which is the default), Gnus will rename the
11523 @code{Message-ID} (for display purposes only) and display the article as
11524 any other article. If this variable is @code{t}, it won't display the
11525 article---it'll be as if it never existed.
11527 @vindex gnus-alter-articles-to-read-function
11528 @item gnus-alter-articles-to-read-function
11529 This function, which takes two parameters (the group name and the list
11530 of articles to be selected), is called to allow the user to alter the
11531 list of articles to be selected.
11533 For instance, the following function adds the list of cached articles to
11534 the list in one particular group:
11537 (defun my-add-cached-articles (group articles)
11538 (if (string= group "some.group")
11539 (append gnus-newsgroup-cached articles)
11543 @vindex gnus-newsgroup-variables
11544 @item gnus-newsgroup-variables
11545 A list of newsgroup (summary buffer) local variables, or cons of
11546 variables and their default expressions to be evalled (when the default
11547 values are not @code{nil}), that should be made global while the summary
11550 Note: The default expressions will be evaluated (using function
11551 @code{eval}) before assignment to the local variable rather than just
11552 assigned to it. If the default expression is the symbol @code{global},
11553 that symbol will not be evaluated but the global value of the local
11554 variable will be used instead.
11556 These variables can be used to set variables in the group parameters
11557 while still allowing them to affect operations done in other
11558 buffers. For example:
11561 (setq gnus-newsgroup-variables
11562 '(message-use-followup-to
11563 (gnus-visible-headers .
11564 "^From:\\|^Newsgroups:\\|^Subject:\\|^Date:\\|^To:")))
11567 Also @pxref{Group Parameters}.
11569 @vindex gnus-propagate-marks
11570 @item gnus-propagate-marks
11571 If non-@code{nil}, propagate marks to the backends for possible
11572 storing. @xref{NNTP marks}, and friends, for a more fine-grained
11578 @node Summary Group Information
11579 @subsection Summary Group Information
11584 @kindex H f (Summary)
11585 @findex gnus-summary-fetch-faq
11586 @vindex gnus-group-faq-directory
11587 Try to fetch the @acronym{FAQ} (list of frequently asked questions)
11588 for the current group (@code{gnus-summary-fetch-faq}). Gnus will try
11589 to get the @acronym{FAQ} from @code{gnus-group-faq-directory}, which
11590 is usually a directory on a remote machine. This variable can also be
11591 a list of directories. In that case, giving a prefix to this command
11592 will allow you to choose between the various sites. @code{ange-ftp}
11593 or @code{efs} will probably be used for fetching the file.
11596 @kindex H d (Summary)
11597 @findex gnus-summary-describe-group
11598 Give a brief description of the current group
11599 (@code{gnus-summary-describe-group}). If given a prefix, force
11600 rereading the description from the server.
11603 @kindex H h (Summary)
11604 @findex gnus-summary-describe-briefly
11605 Give an extremely brief description of the most important summary
11606 keystrokes (@code{gnus-summary-describe-briefly}).
11609 @kindex H i (Summary)
11610 @findex gnus-info-find-node
11611 Go to the Gnus info node (@code{gnus-info-find-node}).
11615 @node Searching for Articles
11616 @subsection Searching for Articles
11621 @kindex M-s (Summary)
11622 @findex gnus-summary-search-article-forward
11623 Search through all subsequent (raw) articles for a regexp
11624 (@code{gnus-summary-search-article-forward}).
11627 @kindex M-r (Summary)
11628 @findex gnus-summary-search-article-backward
11629 Search through all previous (raw) articles for a regexp
11630 (@code{gnus-summary-search-article-backward}).
11633 @kindex M-S (Summary)
11634 @findex gnus-summary-repeat-search-article-forward
11635 Repeat the previous search forwards
11636 (@code{gnus-summary-repeat-search-article-forward}).
11639 @kindex M-R (Summary)
11640 @findex gnus-summary-repeat-search-article-backward
11641 Repeat the previous search backwards
11642 (@code{gnus-summary-repeat-search-article-backward}).
11645 @kindex & (Summary)
11646 @findex gnus-summary-execute-command
11647 This command will prompt you for a header, a regular expression to match
11648 on this field, and a command to be executed if the match is made
11649 (@code{gnus-summary-execute-command}). If the header is an empty
11650 string, the match is done on the entire article. If given a prefix,
11651 search backward instead.
11653 For instance, @kbd{& RET some.*string RET #} will put the process mark on
11654 all articles that have heads or bodies that match @samp{some.*string}.
11657 @kindex M-& (Summary)
11658 @findex gnus-summary-universal-argument
11659 Perform any operation on all articles that have been marked with
11660 the process mark (@code{gnus-summary-universal-argument}).
11663 @node Summary Generation Commands
11664 @subsection Summary Generation Commands
11669 @kindex Y g (Summary)
11670 @findex gnus-summary-prepare
11671 Regenerate the current summary buffer (@code{gnus-summary-prepare}).
11674 @kindex Y c (Summary)
11675 @findex gnus-summary-insert-cached-articles
11676 Pull all cached articles (for the current group) into the summary buffer
11677 (@code{gnus-summary-insert-cached-articles}).
11680 @kindex Y d (Summary)
11681 @findex gnus-summary-insert-dormant-articles
11682 Pull all dormant articles (for the current group) into the summary buffer
11683 (@code{gnus-summary-insert-dormant-articles}).
11686 @kindex Y t (Summary)
11687 @findex gnus-summary-insert-ticked-articles
11688 Pull all ticked articles (for the current group) into the summary buffer
11689 (@code{gnus-summary-insert-ticked-articles}).
11694 @node Really Various Summary Commands
11695 @subsection Really Various Summary Commands
11701 @kindex C-d (Summary)
11702 @kindex A D (Summary)
11703 @findex gnus-summary-enter-digest-group
11704 If the current article is a collection of other articles (for instance,
11705 a digest), you might use this command to enter a group based on the that
11706 article (@code{gnus-summary-enter-digest-group}). Gnus will try to
11707 guess what article type is currently displayed unless you give a prefix
11708 to this command, which forces a ``digest'' interpretation. Basically,
11709 whenever you see a message that is a collection of other messages of
11710 some format, you @kbd{C-d} and read these messages in a more convenient
11713 @vindex gnus-auto-select-on-ephemeral-exit
11714 The variable @code{gnus-auto-select-on-ephemeral-exit} controls what
11715 article should be selected after exiting a digest group. Valid values
11720 Select the next article.
11723 Select the next unread article.
11725 @item next-noselect
11726 Move the cursor to the next article. This is the default.
11728 @item next-unread-noselect
11729 Move the cursor to the next unread article.
11732 If it has any other value or there is no next (unread) article, the
11733 article selected before entering to the digest group will appear.
11736 @kindex C-M-d (Summary)
11737 @findex gnus-summary-read-document
11738 This command is very similar to the one above, but lets you gather
11739 several documents into one biiig group
11740 (@code{gnus-summary-read-document}). It does this by opening several
11741 @code{nndoc} groups for each document, and then opening an
11742 @code{nnvirtual} group on top of these @code{nndoc} groups. This
11743 command understands the process/prefix convention
11744 (@pxref{Process/Prefix}).
11747 @kindex C-t (Summary)
11748 @findex gnus-summary-toggle-truncation
11749 Toggle truncation of summary lines
11750 (@code{gnus-summary-toggle-truncation}). This will probably confuse the
11751 line centering function in the summary buffer, so it's not a good idea
11752 to have truncation switched off while reading articles.
11755 @kindex = (Summary)
11756 @findex gnus-summary-expand-window
11757 Expand the summary buffer window (@code{gnus-summary-expand-window}).
11758 If given a prefix, force an @code{article} window configuration.
11761 @kindex C-M-e (Summary)
11762 @findex gnus-summary-edit-parameters
11763 Edit the group parameters (@pxref{Group Parameters}) of the current
11764 group (@code{gnus-summary-edit-parameters}).
11767 @kindex C-M-a (Summary)
11768 @findex gnus-summary-customize-parameters
11769 Customize the group parameters (@pxref{Group Parameters}) of the current
11770 group (@code{gnus-summary-customize-parameters}).
11775 @node Exiting the Summary Buffer
11776 @section Exiting the Summary Buffer
11777 @cindex summary exit
11778 @cindex exiting groups
11780 Exiting from the summary buffer will normally update all info on the
11781 group and return you to the group buffer.
11788 @kindex Z Z (Summary)
11789 @kindex Z Q (Summary)
11790 @kindex q (Summary)
11791 @findex gnus-summary-exit
11792 @vindex gnus-summary-exit-hook
11793 @vindex gnus-summary-prepare-exit-hook
11794 @vindex gnus-group-no-more-groups-hook
11795 @c @icon{gnus-summary-exit}
11796 Exit the current group and update all information on the group
11797 (@code{gnus-summary-exit}). @code{gnus-summary-prepare-exit-hook} is
11798 called before doing much of the exiting, which calls
11799 @code{gnus-summary-expire-articles} by default.
11800 @code{gnus-summary-exit-hook} is called after finishing the exit
11801 process. @code{gnus-group-no-more-groups-hook} is run when returning to
11802 group mode having no more (unread) groups.
11806 @kindex Z E (Summary)
11807 @kindex Q (Summary)
11808 @findex gnus-summary-exit-no-update
11809 Exit the current group without updating any information on the group
11810 (@code{gnus-summary-exit-no-update}).
11814 @kindex Z c (Summary)
11815 @kindex c (Summary)
11816 @findex gnus-summary-catchup-and-exit
11817 @c @icon{gnus-summary-catchup-and-exit}
11818 Mark all unticked articles in the group as read and then exit
11819 (@code{gnus-summary-catchup-and-exit}).
11822 @kindex Z C (Summary)
11823 @findex gnus-summary-catchup-all-and-exit
11824 Mark all articles, even the ticked ones, as read and then exit
11825 (@code{gnus-summary-catchup-all-and-exit}).
11828 @kindex Z n (Summary)
11829 @findex gnus-summary-catchup-and-goto-next-group
11830 Mark all articles as read and go to the next group
11831 (@code{gnus-summary-catchup-and-goto-next-group}).
11834 @kindex Z p (Summary)
11835 @findex gnus-summary-catchup-and-goto-prev-group
11836 Mark all articles as read and go to the previous group
11837 (@code{gnus-summary-catchup-and-goto-prev-group}).
11841 @kindex Z R (Summary)
11842 @kindex C-x C-s (Summary)
11843 @findex gnus-summary-reselect-current-group
11844 Exit this group, and then enter it again
11845 (@code{gnus-summary-reselect-current-group}). If given a prefix, select
11846 all articles, both read and unread.
11850 @kindex Z G (Summary)
11851 @kindex M-g (Summary)
11852 @findex gnus-summary-rescan-group
11853 @c @icon{gnus-summary-mail-get}
11854 Exit the group, check for new articles in the group, and select the
11855 group (@code{gnus-summary-rescan-group}). If given a prefix, select all
11856 articles, both read and unread.
11859 @kindex Z N (Summary)
11860 @findex gnus-summary-next-group
11861 Exit the group and go to the next group
11862 (@code{gnus-summary-next-group}).
11865 @kindex Z P (Summary)
11866 @findex gnus-summary-prev-group
11867 Exit the group and go to the previous group
11868 (@code{gnus-summary-prev-group}).
11871 @kindex Z s (Summary)
11872 @findex gnus-summary-save-newsrc
11873 Save the current number of read/marked articles in the dribble buffer
11874 and then save the dribble buffer (@code{gnus-summary-save-newsrc}). If
11875 given a prefix, also save the @file{.newsrc} file(s). Using this
11876 command will make exit without updating (the @kbd{Q} command) worthless.
11879 @vindex gnus-exit-group-hook
11880 @code{gnus-exit-group-hook} is called when you exit the current group
11881 with an ``updating'' exit. For instance @kbd{Q}
11882 (@code{gnus-summary-exit-no-update}) does not call this hook.
11884 @findex gnus-summary-wake-up-the-dead
11885 @findex gnus-dead-summary-mode
11886 @vindex gnus-kill-summary-on-exit
11887 If you're in the habit of exiting groups, and then changing your mind
11888 about it, you might set @code{gnus-kill-summary-on-exit} to @code{nil}.
11889 If you do that, Gnus won't kill the summary buffer when you exit it.
11890 (Quelle surprise!) Instead it will change the name of the buffer to
11891 something like @samp{*Dead Summary ... *} and install a minor mode
11892 called @code{gnus-dead-summary-mode}. Now, if you switch back to this
11893 buffer, you'll find that all keys are mapped to a function called
11894 @code{gnus-summary-wake-up-the-dead}. So tapping any keys in a dead
11895 summary buffer will result in a live, normal summary buffer.
11897 There will never be more than one dead summary buffer at any one time.
11899 @vindex gnus-use-cross-reference
11900 The data on the current group will be updated (which articles you have
11901 read, which articles you have replied to, etc.) when you exit the
11902 summary buffer. If the @code{gnus-use-cross-reference} variable is
11903 @code{t} (which is the default), articles that are cross-referenced to
11904 this group and are marked as read, will also be marked as read in the
11905 other subscribed groups they were cross-posted to. If this variable is
11906 neither @code{nil} nor @code{t}, the article will be marked as read in
11907 both subscribed and unsubscribed groups (@pxref{Crosspost Handling}).
11910 @node Crosspost Handling
11911 @section Crosspost Handling
11915 Marking cross-posted articles as read ensures that you'll never have to
11916 read the same article more than once. Unless, of course, somebody has
11917 posted it to several groups separately. Posting the same article to
11918 several groups (not cross-posting) is called @dfn{spamming}, and you are
11919 by law required to send nasty-grams to anyone who perpetrates such a
11920 heinous crime. You may want to try NoCeM handling to filter out spam
11923 Remember: Cross-posting is kinda ok, but posting the same article
11924 separately to several groups is not. Massive cross-posting (aka.
11925 @dfn{velveeta}) is to be avoided at all costs, and you can even use the
11926 @code{gnus-summary-mail-crosspost-complaint} command to complain about
11927 excessive crossposting (@pxref{Summary Mail Commands}).
11929 @cindex cross-posting
11931 @cindex @acronym{NOV}
11932 One thing that may cause Gnus to not do the cross-posting thing
11933 correctly is if you use an @acronym{NNTP} server that supports @sc{xover}
11934 (which is very nice, because it speeds things up considerably) which
11935 does not include the @code{Xref} header in its @acronym{NOV} lines. This is
11936 Evil, but all too common, alas, alack. Gnus tries to Do The Right Thing
11937 even with @sc{xover} by registering the @code{Xref} lines of all
11938 articles you actually read, but if you kill the articles, or just mark
11939 them as read without reading them, Gnus will not get a chance to snoop
11940 the @code{Xref} lines out of these articles, and will be unable to use
11941 the cross reference mechanism.
11943 @cindex LIST overview.fmt
11944 @cindex overview.fmt
11945 To check whether your @acronym{NNTP} server includes the @code{Xref} header
11946 in its overview files, try @samp{telnet your.nntp.server nntp},
11947 @samp{MODE READER} on @code{inn} servers, and then say @samp{LIST
11948 overview.fmt}. This may not work, but if it does, and the last line you
11949 get does not read @samp{Xref:full}, then you should shout and whine at
11950 your news admin until she includes the @code{Xref} header in the
11953 If you want Gnus to get the @code{Xref}s right all the time, you have to
11954 set @code{nntp-nov-is-evil} to @code{t}, which slows things down
11955 considerably. Also @pxref{Slow/Expensive Connection}.
11959 For an alternative approach, @pxref{Duplicate Suppression}.
11962 @node Duplicate Suppression
11963 @section Duplicate Suppression
11965 By default, Gnus tries to make sure that you don't have to read the same
11966 article more than once by utilizing the crossposting mechanism
11967 (@pxref{Crosspost Handling}). However, that simple and efficient
11968 approach may not work satisfactory for some users for various
11973 The @acronym{NNTP} server may fail to generate the @code{Xref} header. This
11974 is evil and not very common.
11977 The @acronym{NNTP} server may fail to include the @code{Xref} header in the
11978 @file{.overview} data bases. This is evil and all too common, alas.
11981 You may be reading the same group (or several related groups) from
11982 different @acronym{NNTP} servers.
11985 You may be getting mail that duplicates articles posted to groups.
11988 I'm sure there are other situations where @code{Xref} handling fails as
11989 well, but these four are the most common situations.
11991 If, and only if, @code{Xref} handling fails for you, then you may
11992 consider switching on @dfn{duplicate suppression}. If you do so, Gnus
11993 will remember the @code{Message-ID}s of all articles you have read or
11994 otherwise marked as read, and then, as if by magic, mark them as read
11995 all subsequent times you see them---in @emph{all} groups. Using this
11996 mechanism is quite likely to be somewhat inefficient, but not overly
11997 so. It's certainly preferable to reading the same articles more than
12000 Duplicate suppression is not a very subtle instrument. It's more like a
12001 sledge hammer than anything else. It works in a very simple
12002 fashion---if you have marked an article as read, it adds this Message-ID
12003 to a cache. The next time it sees this Message-ID, it will mark the
12004 article as read with the @samp{M} mark. It doesn't care what group it
12005 saw the article in.
12008 @item gnus-suppress-duplicates
12009 @vindex gnus-suppress-duplicates
12010 If non-@code{nil}, suppress duplicates.
12012 @item gnus-save-duplicate-list
12013 @vindex gnus-save-duplicate-list
12014 If non-@code{nil}, save the list of duplicates to a file. This will
12015 make startup and shutdown take longer, so the default is @code{nil}.
12016 However, this means that only duplicate articles read in a single Gnus
12017 session are suppressed.
12019 @item gnus-duplicate-list-length
12020 @vindex gnus-duplicate-list-length
12021 This variable says how many @code{Message-ID}s to keep in the duplicate
12022 suppression list. The default is 10000.
12024 @item gnus-duplicate-file
12025 @vindex gnus-duplicate-file
12026 The name of the file to store the duplicate suppression list in. The
12027 default is @file{~/News/suppression}.
12030 If you have a tendency to stop and start Gnus often, setting
12031 @code{gnus-save-duplicate-list} to @code{t} is probably a good idea. If
12032 you leave Gnus running for weeks on end, you may have it @code{nil}. On
12033 the other hand, saving the list makes startup and shutdown much slower,
12034 so that means that if you stop and start Gnus often, you should set
12035 @code{gnus-save-duplicate-list} to @code{nil}. Uhm. I'll leave this up
12036 to you to figure out, I think.
12041 Gnus is able to verify signed messages or decrypt encrypted messages.
12042 The formats that are supported are @acronym{PGP}, @acronym{PGP/MIME}
12043 and @acronym{S/MIME}, however you need some external programs to get
12048 To handle @acronym{PGP} and @acronym{PGP/MIME} messages, you have to
12049 install an OpenPGP implementation such as GnuPG. The Lisp interface
12050 to GnuPG included with Emacs is called EasyPG (@pxref{Top, ,EasyPG,
12051 epa, EasyPG Assistant user's manual}), but PGG (@pxref{Top, ,PGG, pgg,
12052 PGG Manual}), Mailcrypt, and gpg.el are also supported.
12055 To handle @acronym{S/MIME} message, you need to install OpenSSL. OpenSSL 0.9.6
12056 or newer is recommended.
12060 The variables that control security functionality on reading/composing
12064 @item mm-verify-option
12065 @vindex mm-verify-option
12066 Option of verifying signed parts. @code{never}, not verify;
12067 @code{always}, always verify; @code{known}, only verify known
12068 protocols. Otherwise, ask user.
12070 @item mm-decrypt-option
12071 @vindex mm-decrypt-option
12072 Option of decrypting encrypted parts. @code{never}, no decryption;
12073 @code{always}, always decrypt; @code{known}, only decrypt known
12074 protocols. Otherwise, ask user.
12076 @item mm-sign-option
12077 @vindex mm-sign-option
12078 Option of creating signed parts. @code{nil}, use default signing
12079 keys; @code{guided}, ask user to select signing keys from the menu.
12081 @item mm-encrypt-option
12082 @vindex mm-encrypt-option
12083 Option of creating encrypted parts. @code{nil}, use the first
12084 public-key matching the @samp{From:} header as the recipient;
12085 @code{guided}, ask user to select recipient keys from the menu.
12088 @vindex mml1991-use
12089 Symbol indicating elisp interface to OpenPGP implementation for
12090 @acronym{PGP} messages. The default is @code{epg}, but @code{pgg},
12091 @code{mailcrypt}, and @code{gpg} are also supported although
12092 deprecated. By default, Gnus uses the first available interface in
12096 @vindex mml2015-use
12097 Symbol indicating elisp interface to OpenPGP implementation for
12098 @acronym{PGP/MIME} messages. The default is @code{epg}, but
12099 @code{pgg}, @code{mailcrypt}, and @code{gpg} are also supported
12100 although deprecated. By default, Gnus uses the first available
12101 interface in this order.
12105 By default the buttons that display security information are not
12106 shown, because they clutter reading the actual e-mail. You can type
12107 @kbd{K b} manually to display the information. Use the
12108 @code{gnus-buttonized-mime-types} and
12109 @code{gnus-unbuttonized-mime-types} variables to control this
12110 permanently. @ref{MIME Commands} for further details, and hints on
12111 how to customize these variables to always display security
12114 @cindex snarfing keys
12115 @cindex importing PGP keys
12116 @cindex PGP key ring import
12117 Snarfing OpenPGP keys (i.e., importing keys from articles into your
12118 key ring) is not supported explicitly through a menu item or command,
12119 rather Gnus do detect and label keys as @samp{application/pgp-keys},
12120 allowing you to specify whatever action you think is appropriate
12121 through the usual @acronym{MIME} infrastructure. You can use a
12122 @file{~/.mailcap} entry (@pxref{mailcap, , mailcap, emacs-mime, The
12123 Emacs MIME Manual}) such as the following to import keys using GNU
12124 Privacy Guard when you click on the @acronym{MIME} button
12125 (@pxref{Using MIME}).
12128 application/pgp-keys; gpg --import --interactive --verbose; needsterminal
12131 This happens to also be the default action defined in
12132 @code{mailcap-mime-data}.
12134 More information on how to set things for sending outgoing signed and
12135 encrypted messages up can be found in the message manual
12136 (@pxref{Security, ,Security, message, Message Manual}).
12139 @section Mailing List
12140 @cindex mailing list
12143 @kindex A M (summary)
12144 @findex gnus-mailing-list-insinuate
12145 Gnus understands some mailing list fields of RFC 2369. To enable it,
12146 add a @code{to-list} group parameter (@pxref{Group Parameters}),
12147 possibly using @kbd{A M} (@code{gnus-mailing-list-insinuate}) in the
12150 That enables the following commands to the summary buffer:
12155 @kindex C-c C-n h (Summary)
12156 @findex gnus-mailing-list-help
12157 Send a message to fetch mailing list help, if List-Help field exists.
12160 @kindex C-c C-n s (Summary)
12161 @findex gnus-mailing-list-subscribe
12162 Send a message to subscribe the mailing list, if List-Subscribe field exists.
12165 @kindex C-c C-n u (Summary)
12166 @findex gnus-mailing-list-unsubscribe
12167 Send a message to unsubscribe the mailing list, if List-Unsubscribe
12171 @kindex C-c C-n p (Summary)
12172 @findex gnus-mailing-list-post
12173 Post to the mailing list, if List-Post field exists.
12176 @kindex C-c C-n o (Summary)
12177 @findex gnus-mailing-list-owner
12178 Send a message to the mailing list owner, if List-Owner field exists.
12181 @kindex C-c C-n a (Summary)
12182 @findex gnus-mailing-list-archive
12183 Browse the mailing list archive, if List-Archive field exists.
12188 @node Article Buffer
12189 @chapter Article Buffer
12190 @cindex article buffer
12192 The articles are displayed in the article buffer, of which there is only
12193 one. All the summary buffers share the same article buffer unless you
12194 tell Gnus otherwise.
12197 * Hiding Headers:: Deciding what headers should be displayed.
12198 * Using MIME:: Pushing articles through @acronym{MIME} before reading them.
12199 * Customizing Articles:: Tailoring the look of the articles.
12200 * Article Keymap:: Keystrokes available in the article buffer.
12201 * Misc Article:: Other stuff.
12205 @node Hiding Headers
12206 @section Hiding Headers
12207 @cindex hiding headers
12208 @cindex deleting headers
12210 The top section of each article is the @dfn{head}. (The rest is the
12211 @dfn{body}, but you may have guessed that already.)
12213 @vindex gnus-show-all-headers
12214 There is a lot of useful information in the head: the name of the person
12215 who wrote the article, the date it was written and the subject of the
12216 article. That's well and nice, but there's also lots of information
12217 most people do not want to see---what systems the article has passed
12218 through before reaching you, the @code{Message-ID}, the
12219 @code{References}, etc. ad nauseam---and you'll probably want to get rid
12220 of some of those lines. If you want to keep all those lines in the
12221 article buffer, you can set @code{gnus-show-all-headers} to @code{t}.
12223 Gnus provides you with two variables for sifting headers:
12227 @item gnus-visible-headers
12228 @vindex gnus-visible-headers
12229 If this variable is non-@code{nil}, it should be a regular expression
12230 that says what headers you wish to keep in the article buffer. All
12231 headers that do not match this variable will be hidden.
12233 For instance, if you only want to see the name of the person who wrote
12234 the article and the subject, you'd say:
12237 (setq gnus-visible-headers "^From:\\|^Subject:")
12240 This variable can also be a list of regexps to match headers to
12243 @item gnus-ignored-headers
12244 @vindex gnus-ignored-headers
12245 This variable is the reverse of @code{gnus-visible-headers}. If this
12246 variable is set (and @code{gnus-visible-headers} is @code{nil}), it
12247 should be a regular expression that matches all lines that you want to
12248 hide. All lines that do not match this variable will remain visible.
12250 For instance, if you just want to get rid of the @code{References} line
12251 and the @code{Xref} line, you might say:
12254 (setq gnus-ignored-headers "^References:\\|^Xref:")
12257 This variable can also be a list of regexps to match headers to
12260 Note that if @code{gnus-visible-headers} is non-@code{nil}, this
12261 variable will have no effect.
12265 @vindex gnus-sorted-header-list
12266 Gnus can also sort the headers for you. (It does this by default.) You
12267 can control the sorting by setting the @code{gnus-sorted-header-list}
12268 variable. It is a list of regular expressions that says in what order
12269 the headers are to be displayed.
12271 For instance, if you want the name of the author of the article first,
12272 and then the subject, you might say something like:
12275 (setq gnus-sorted-header-list '("^From:" "^Subject:"))
12278 Any headers that are to remain visible, but are not listed in this
12279 variable, will be displayed in random order after all the headers listed in this variable.
12281 @findex gnus-article-hide-boring-headers
12282 @vindex gnus-boring-article-headers
12283 You can hide further boring headers by setting
12284 @code{gnus-treat-hide-boring-headers} to @code{head}. What this function
12285 does depends on the @code{gnus-boring-article-headers} variable. It's a
12286 list, but this list doesn't actually contain header names. Instead it
12287 lists various @dfn{boring conditions} that Gnus can check and remove
12290 These conditions are:
12293 Remove all empty headers.
12295 Remove the @code{Followup-To} header if it is identical to the
12296 @code{Newsgroups} header.
12298 Remove the @code{Reply-To} header if it lists the same addresses as
12299 the @code{From} header, or if the @code{broken-reply-to} group
12302 Remove the @code{Newsgroups} header if it only contains the current group
12305 Remove the @code{To} header if it only contains the address identical to
12306 the current group's @code{to-address} parameter.
12308 Remove the @code{To} header if it only contains the address identical to
12309 the current group's @code{to-list} parameter.
12311 Remove the @code{Cc} header if it only contains the address identical to
12312 the current group's @code{to-list} parameter.
12314 Remove the @code{Date} header if the article is less than three days
12317 Remove the @code{To} and/or @code{Cc} header if it is very long.
12319 Remove all @code{To} and/or @code{Cc} headers if there are more than one.
12322 To include these three elements, you could say something like:
12325 (setq gnus-boring-article-headers
12326 '(empty followup-to reply-to))
12329 This is also the default value for this variable.
12333 @section Using MIME
12334 @cindex @acronym{MIME}
12336 Mime is a standard for waving your hands through the air, aimlessly,
12337 while people stand around yawning.
12339 @acronym{MIME}, however, is a standard for encoding your articles, aimlessly,
12340 while all newsreaders die of fear.
12342 @acronym{MIME} may specify what character set the article uses, the encoding
12343 of the characters, and it also makes it possible to embed pictures and
12344 other naughty stuff in innocent-looking articles.
12346 @vindex gnus-display-mime-function
12347 @findex gnus-display-mime
12348 Gnus pushes @acronym{MIME} articles through @code{gnus-display-mime-function}
12349 to display the @acronym{MIME} parts. This is @code{gnus-display-mime} by
12350 default, which creates a bundle of clickable buttons that can be used to
12351 display, save and manipulate the @acronym{MIME} objects.
12353 The following commands are available when you have placed point over a
12354 @acronym{MIME} button:
12357 @findex gnus-article-press-button
12358 @item RET (Article)
12359 @kindex RET (Article)
12360 @itemx BUTTON-2 (Article)
12361 Toggle displaying of the @acronym{MIME} object
12362 (@code{gnus-article-press-button}). If built-in viewers can not display
12363 the object, Gnus resorts to external viewers in the @file{mailcap}
12364 files. If a viewer has the @samp{copiousoutput} specification, the
12365 object is displayed inline.
12367 @findex gnus-mime-view-part
12368 @item M-RET (Article)
12369 @kindex M-RET (Article)
12371 Prompt for a method, and then view the @acronym{MIME} object using this
12372 method (@code{gnus-mime-view-part}).
12374 @findex gnus-mime-view-part-as-type
12376 @kindex t (Article)
12377 View the @acronym{MIME} object as if it were a different @acronym{MIME} media type
12378 (@code{gnus-mime-view-part-as-type}).
12380 @findex gnus-mime-view-part-as-charset
12382 @kindex C (Article)
12383 Prompt for a charset, and then view the @acronym{MIME} object using this
12384 charset (@code{gnus-mime-view-part-as-charset}).
12386 @findex gnus-mime-save-part
12388 @kindex o (Article)
12389 Prompt for a file name, and then save the @acronym{MIME} object
12390 (@code{gnus-mime-save-part}).
12392 @findex gnus-mime-save-part-and-strip
12393 @item C-o (Article)
12394 @kindex C-o (Article)
12395 Prompt for a file name, then save the @acronym{MIME} object and strip it from
12396 the article. Then proceed to article editing, where a reasonable
12397 suggestion is being made on how the altered article should look
12398 like. The stripped @acronym{MIME} object will be referred via the
12399 message/external-body @acronym{MIME} type.
12400 (@code{gnus-mime-save-part-and-strip}).
12402 @findex gnus-mime-replace-part
12404 @kindex r (Article)
12405 Prompt for a file name, replace the @acronym{MIME} object with an
12406 external body refering to the file via the message/external-body
12407 @acronym{MIME} type. (@code{gnus-mime-replace-part}).
12409 @findex gnus-mime-delete-part
12411 @kindex d (Article)
12412 Delete the @acronym{MIME} object from the article and replace it with some
12413 information about the removed @acronym{MIME} object
12414 (@code{gnus-mime-delete-part}).
12416 @c FIXME: gnus-auto-select-part should be documented here
12418 @findex gnus-mime-copy-part
12420 @kindex c (Article)
12421 Copy the @acronym{MIME} object to a fresh buffer and display this buffer
12422 (@code{gnus-mime-copy-part}). If given a prefix, copy the raw contents
12423 without decoding. If given a numerical prefix, you can do semi-manual
12424 charset stuff (see @code{gnus-summary-show-article-charset-alist} in
12425 @ref{Paging the Article}). Compressed files like @file{.gz} and
12426 @file{.bz2} are automatically decompressed if
12427 @code{auto-compression-mode} is enabled (@pxref{Compressed Files,,
12428 Accessing Compressed Files, emacs, The Emacs Editor}).
12430 @findex gnus-mime-print-part
12432 @kindex p (Article)
12433 Print the @acronym{MIME} object (@code{gnus-mime-print-part}). This
12434 command respects the @samp{print=} specifications in the
12435 @file{.mailcap} file.
12437 @findex gnus-mime-inline-part
12439 @kindex i (Article)
12440 Insert the contents of the @acronym{MIME} object into the buffer
12441 (@code{gnus-mime-inline-part}) as @samp{text/plain}. If given a prefix, insert
12442 the raw contents without decoding. If given a numerical prefix, you can
12443 do semi-manual charset stuff (see
12444 @code{gnus-summary-show-article-charset-alist} in @ref{Paging the
12445 Article}). Compressed files like @file{.gz} and @file{.bz2} are
12446 automatically decompressed depending on @code{jka-compr} regardless of
12447 @code{auto-compression-mode} (@pxref{Compressed Files,, Accessing
12448 Compressed Files, emacs, The Emacs Editor}).
12450 @findex gnus-mime-view-part-internally
12452 @kindex E (Article)
12453 View the @acronym{MIME} object with an internal viewer. If no internal
12454 viewer is available, use an external viewer
12455 (@code{gnus-mime-view-part-internally}).
12457 @findex gnus-mime-view-part-externally
12459 @kindex e (Article)
12460 View the @acronym{MIME} object with an external viewer.
12461 (@code{gnus-mime-view-part-externally}).
12463 @findex gnus-mime-pipe-part
12465 @kindex | (Article)
12466 Output the @acronym{MIME} object to a process (@code{gnus-mime-pipe-part}).
12468 @findex gnus-mime-action-on-part
12470 @kindex . (Article)
12471 Interactively run an action on the @acronym{MIME} object
12472 (@code{gnus-mime-action-on-part}).
12477 If you have @code{w3m} installed on your system, Gnus can display
12478 @acronym{HTML} articles in the article buffer. The following
12479 variables are relevant:
12482 @item gnus-html-cache-directory
12483 @vindex gnus-html-cache-directory
12484 Gnus will download and cache images according to how
12485 @code{mm-w3m-safe-url-regexp} is set. These images will be stored in
12488 @item gnus-html-cache-size
12489 @vindex gnus-html-cache-size
12490 When @code{gnus-html-cache-size} bytes have been used in that
12491 directory, the oldest files will be deleted. The default is 500MB.
12493 @item gnus-html-frame-width
12494 @vindex gnus-html-frame-width
12495 The width to use when rendering HTML. The default is 70.
12500 Gnus will display some @acronym{MIME} objects automatically. The way Gnus
12501 determines which parts to do this with is described in the Emacs
12502 @acronym{MIME} manual.
12504 It might be best to just use the toggling functions from the article
12505 buffer to avoid getting nasty surprises. (For instance, you enter the
12506 group @samp{alt.sing-a-long} and, before you know it, @acronym{MIME} has
12507 decoded the sound file in the article and some horrible sing-a-long song
12508 comes screaming out your speakers, and you can't find the volume button,
12509 because there isn't one, and people are starting to look at you, and you
12510 try to stop the program, but you can't, and you can't find the program
12511 to control the volume, and everybody else in the room suddenly decides
12512 to look at you disdainfully, and you'll feel rather stupid.)
12514 Any similarity to real events and people is purely coincidental. Ahem.
12516 Also @pxref{MIME Commands}.
12519 @node Customizing Articles
12520 @section Customizing Articles
12521 @cindex article customization
12523 A slew of functions for customizing how the articles are to look like
12524 exist. You can call these functions interactively
12525 (@pxref{Article Washing}), or you can have them
12526 called automatically when you select the articles.
12528 To have them called automatically, you should set the corresponding
12529 ``treatment'' variable. For instance, to have headers hidden, you'd set
12530 @code{gnus-treat-hide-headers}. Below is a list of variables that can
12531 be set, but first we discuss the values these variables can have.
12533 Note: Some values, while valid, make little sense. Check the list below
12534 for sensible values.
12538 @code{nil}: Don't do this treatment.
12541 @code{t}: Do this treatment on all body parts.
12544 @code{head}: Do the treatment on the headers.
12547 @code{first}: Do this treatment on the first body part.
12550 @code{last}: Do this treatment on the last body part.
12553 An integer: Do this treatment on all body parts that have a length less
12557 A list of strings: Do this treatment on all body parts that are in
12558 articles that are read in groups that have names that match one of the
12559 regexps in the list.
12562 A list where the first element is not a string:
12564 The list is evaluated recursively. The first element of the list is a
12565 predicate. The following predicates are recognized: @code{or},
12566 @code{and}, @code{not} and @code{typep}. Here's an example:
12570 (typep "text/x-vcard"))
12575 You may have noticed that the word @dfn{part} is used here. This refers
12576 to the fact that some messages are @acronym{MIME} multipart articles that may
12577 be divided into several parts. Articles that are not multiparts are
12578 considered to contain just a single part.
12580 @vindex gnus-article-treat-types
12581 Are the treatments applied to all sorts of multipart parts? Yes, if you
12582 want to, but by default, only @samp{text/plain} parts are given the
12583 treatment. This is controlled by the @code{gnus-article-treat-types}
12584 variable, which is a list of regular expressions that are matched to the
12585 type of the part. This variable is ignored if the value of the
12586 controlling variable is a predicate list, as described above.
12589 @c Avoid sort of redundant entries in the same section for the printed
12590 @c manual, but add them in info to allow `i gnus-treat-foo-bar RET' or
12592 @vindex gnus-treat-buttonize
12593 @vindex gnus-treat-buttonize-head
12594 @vindex gnus-treat-capitalize-sentences
12595 @vindex gnus-treat-overstrike
12596 @vindex gnus-treat-strip-cr
12597 @vindex gnus-treat-strip-headers-in-body
12598 @vindex gnus-treat-strip-leading-blank-lines
12599 @vindex gnus-treat-strip-multiple-blank-lines
12600 @vindex gnus-treat-strip-pem
12601 @vindex gnus-treat-strip-trailing-blank-lines
12602 @vindex gnus-treat-unsplit-urls
12603 @vindex gnus-treat-wash-html
12604 @vindex gnus-treat-date-english
12605 @vindex gnus-treat-date-iso8601
12606 @vindex gnus-treat-date-lapsed
12607 @vindex gnus-treat-date-local
12608 @vindex gnus-treat-date-original
12609 @vindex gnus-treat-date-user-defined
12610 @vindex gnus-treat-date-ut
12611 @vindex gnus-treat-from-picon
12612 @vindex gnus-treat-mail-picon
12613 @vindex gnus-treat-newsgroups-picon
12614 @vindex gnus-treat-display-smileys
12615 @vindex gnus-treat-body-boundary
12616 @vindex gnus-treat-display-x-face
12617 @vindex gnus-treat-display-face
12618 @vindex gnus-treat-emphasize
12619 @vindex gnus-treat-fill-article
12620 @vindex gnus-treat-fill-long-lines
12621 @vindex gnus-treat-hide-boring-headers
12622 @vindex gnus-treat-hide-citation
12623 @vindex gnus-treat-hide-citation-maybe
12624 @vindex gnus-treat-hide-headers
12625 @vindex gnus-treat-hide-signature
12626 @vindex gnus-treat-strip-banner
12627 @vindex gnus-treat-strip-list-identifiers
12628 @vindex gnus-treat-highlight-citation
12629 @vindex gnus-treat-highlight-headers
12630 @vindex gnus-treat-highlight-signature
12631 @vindex gnus-treat-play-sounds
12632 @vindex gnus-treat-translate
12633 @vindex gnus-treat-x-pgp-sig
12634 @vindex gnus-treat-unfold-headers
12635 @vindex gnus-treat-fold-headers
12636 @vindex gnus-treat-fold-newsgroups
12637 @vindex gnus-treat-leading-whitespace
12640 The following treatment options are available. The easiest way to
12641 customize this is to examine the @code{gnus-article-treat} customization
12642 group. Values in parenthesis are suggested sensible values. Others are
12643 possible but those listed are probably sufficient for most people.
12646 @item gnus-treat-buttonize (t, integer)
12647 @item gnus-treat-buttonize-head (head)
12649 @xref{Article Buttons}.
12651 @item gnus-treat-capitalize-sentences (t, integer)
12652 @item gnus-treat-overstrike (t, integer)
12653 @item gnus-treat-strip-cr (t, integer)
12654 @item gnus-treat-strip-headers-in-body (t, integer)
12655 @item gnus-treat-strip-leading-blank-lines (t, first, integer)
12656 @item gnus-treat-strip-multiple-blank-lines (t, integer)
12657 @item gnus-treat-strip-pem (t, last, integer)
12658 @item gnus-treat-strip-trailing-blank-lines (t, last, integer)
12659 @item gnus-treat-unsplit-urls (t, integer)
12660 @item gnus-treat-wash-html (t, integer)
12662 @xref{Article Washing}.
12664 @item gnus-treat-date-english (head)
12665 @item gnus-treat-date-iso8601 (head)
12666 @item gnus-treat-date-lapsed (head)
12667 @item gnus-treat-date-local (head)
12668 @item gnus-treat-date-original (head)
12669 @item gnus-treat-date-user-defined (head)
12670 @item gnus-treat-date-ut (head)
12672 @xref{Article Date}.
12674 @item gnus-treat-from-picon (head)
12675 @item gnus-treat-mail-picon (head)
12676 @item gnus-treat-newsgroups-picon (head)
12680 @item gnus-treat-display-smileys (t, integer)
12682 @item gnus-treat-body-boundary (head)
12684 @vindex gnus-body-boundary-delimiter
12685 Adds a delimiter between header and body, the string used as delimiter
12686 is controlled by @code{gnus-body-boundary-delimiter}.
12690 @vindex gnus-treat-display-x-face
12691 @item gnus-treat-display-x-face (head)
12695 @vindex gnus-treat-display-face
12696 @item gnus-treat-display-face (head)
12700 @vindex gnus-treat-emphasize
12701 @item gnus-treat-emphasize (t, head, integer)
12702 @vindex gnus-treat-fill-article
12703 @item gnus-treat-fill-article (t, integer)
12704 @vindex gnus-treat-fill-long-lines
12705 @item gnus-treat-fill-long-lines (t, integer)
12706 @vindex gnus-treat-hide-boring-headers
12707 @item gnus-treat-hide-boring-headers (head)
12708 @vindex gnus-treat-hide-citation
12709 @item gnus-treat-hide-citation (t, integer)
12710 @vindex gnus-treat-hide-citation-maybe
12711 @item gnus-treat-hide-citation-maybe (t, integer)
12712 @vindex gnus-treat-hide-headers
12713 @item gnus-treat-hide-headers (head)
12714 @vindex gnus-treat-hide-signature
12715 @item gnus-treat-hide-signature (t, last)
12716 @vindex gnus-treat-strip-banner
12717 @item gnus-treat-strip-banner (t, last)
12718 @vindex gnus-treat-strip-list-identifiers
12719 @item gnus-treat-strip-list-identifiers (head)
12721 @xref{Article Hiding}.
12723 @vindex gnus-treat-highlight-citation
12724 @item gnus-treat-highlight-citation (t, integer)
12725 @vindex gnus-treat-highlight-headers
12726 @item gnus-treat-highlight-headers (head)
12727 @vindex gnus-treat-highlight-signature
12728 @item gnus-treat-highlight-signature (t, last, integer)
12730 @xref{Article Highlighting}.
12732 @vindex gnus-treat-play-sounds
12733 @item gnus-treat-play-sounds
12734 @vindex gnus-treat-translate
12735 @item gnus-treat-translate
12736 @item gnus-treat-ansi-sequences (t)
12737 @vindex gnus-treat-x-pgp-sig
12738 @item gnus-treat-x-pgp-sig (head)
12740 @vindex gnus-treat-unfold-headers
12741 @item gnus-treat-unfold-headers (head)
12742 @vindex gnus-treat-fold-headers
12743 @item gnus-treat-fold-headers (head)
12744 @vindex gnus-treat-fold-newsgroups
12745 @item gnus-treat-fold-newsgroups (head)
12746 @vindex gnus-treat-leading-whitespace
12747 @item gnus-treat-leading-whitespace (head)
12749 @xref{Article Header}.
12754 @vindex gnus-part-display-hook
12755 You can, of course, write your own functions to be called from
12756 @code{gnus-part-display-hook}. The functions are called narrowed to the
12757 part, and you can do anything you like, pretty much. There is no
12758 information that you have to keep in the buffer---you can change
12762 @node Article Keymap
12763 @section Article Keymap
12765 Most of the keystrokes in the summary buffer can also be used in the
12766 article buffer. They should behave as if you typed them in the summary
12767 buffer, which means that you don't actually have to have a summary
12768 buffer displayed while reading. You can do it all from the article
12771 @kindex v (Article)
12772 @cindex keys, reserved for users (Article)
12773 The key @kbd{v} is reserved for users. You can bind it to some
12774 command or better use it as a prefix key.
12776 A few additional keystrokes are available:
12781 @kindex SPACE (Article)
12782 @findex gnus-article-next-page
12783 Scroll forwards one page (@code{gnus-article-next-page}).
12784 This is exactly the same as @kbd{h SPACE h}.
12787 @kindex DEL (Article)
12788 @findex gnus-article-prev-page
12789 Scroll backwards one page (@code{gnus-article-prev-page}).
12790 This is exactly the same as @kbd{h DEL h}.
12793 @kindex C-c ^ (Article)
12794 @findex gnus-article-refer-article
12795 If point is in the neighborhood of a @code{Message-ID} and you press
12796 @kbd{C-c ^}, Gnus will try to get that article from the server
12797 (@code{gnus-article-refer-article}).
12800 @kindex C-c C-m (Article)
12801 @findex gnus-article-mail
12802 Send a reply to the address near point (@code{gnus-article-mail}). If
12803 given a prefix, include the mail.
12806 @kindex s (Article)
12807 @findex gnus-article-show-summary
12808 Reconfigure the buffers so that the summary buffer becomes visible
12809 (@code{gnus-article-show-summary}).
12812 @kindex ? (Article)
12813 @findex gnus-article-describe-briefly
12814 Give a very brief description of the available keystrokes
12815 (@code{gnus-article-describe-briefly}).
12818 @kindex TAB (Article)
12819 @findex gnus-article-next-button
12820 Go to the next button, if any (@code{gnus-article-next-button}). This
12821 only makes sense if you have buttonizing turned on.
12824 @kindex M-TAB (Article)
12825 @findex gnus-article-prev-button
12826 Go to the previous button, if any (@code{gnus-article-prev-button}).
12829 @kindex R (Article)
12830 @findex gnus-article-reply-with-original
12831 Send a reply to the current article and yank the current article
12832 (@code{gnus-article-reply-with-original}). If the region is active,
12833 only yank the text in the region.
12836 @kindex S W (Article)
12837 @findex gnus-article-wide-reply-with-original
12838 Send a wide reply to the current article and yank the current article
12839 (@code{gnus-article-wide-reply-with-original}). If the region is
12840 active, only yank the text in the region.
12843 @kindex F (Article)
12844 @findex gnus-article-followup-with-original
12845 Send a followup to the current article and yank the current article
12846 (@code{gnus-article-followup-with-original}). If the region is active,
12847 only yank the text in the region.
12854 @section Misc Article
12858 @item gnus-single-article-buffer
12859 @vindex gnus-single-article-buffer
12860 @cindex article buffers, several
12861 If non-@code{nil}, use the same article buffer for all the groups.
12862 (This is the default.) If @code{nil}, each group will have its own
12865 @vindex gnus-article-decode-hook
12866 @item gnus-article-decode-hook
12867 @cindex @acronym{MIME}
12868 Hook used to decode @acronym{MIME} articles. The default value is
12869 @code{(article-decode-charset article-decode-encoded-words)}
12871 @vindex gnus-article-prepare-hook
12872 @item gnus-article-prepare-hook
12873 This hook is called right after the article has been inserted into the
12874 article buffer. It is mainly intended for functions that do something
12875 depending on the contents; it should probably not be used for changing
12876 the contents of the article buffer.
12878 @item gnus-article-mode-hook
12879 @vindex gnus-article-mode-hook
12880 Hook called in article mode buffers.
12882 @item gnus-article-mode-syntax-table
12883 @vindex gnus-article-mode-syntax-table
12884 Syntax table used in article buffers. It is initialized from
12885 @code{text-mode-syntax-table}.
12887 @vindex gnus-article-over-scroll
12888 @item gnus-article-over-scroll
12889 If non-@code{nil}, allow scrolling the article buffer even when there
12890 no more new text to scroll in. The default is @code{nil}.
12892 @vindex gnus-article-mode-line-format
12893 @item gnus-article-mode-line-format
12894 This variable is a format string along the same lines as
12895 @code{gnus-summary-mode-line-format} (@pxref{Summary Buffer Mode
12896 Line}). It accepts the same format specifications as that variable,
12897 with two extensions:
12902 The @dfn{wash status} of the article. This is a short string with one
12903 character for each possible article wash operation that may have been
12904 performed. The characters and their meaning:
12909 Displayed when cited text may be hidden in the article buffer.
12912 Displayed when headers are hidden in the article buffer.
12915 Displayed when article is digitally signed or encrypted, and Gnus has
12916 hidden the security headers. (N.B. does not tell anything about
12917 security status, i.e. good or bad signature.)
12920 Displayed when the signature has been hidden in the Article buffer.
12923 Displayed when Gnus has treated overstrike characters in the article buffer.
12926 Displayed when Gnus has treated emphasized strings in the article buffer.
12931 The number of @acronym{MIME} parts in the article.
12935 @vindex gnus-break-pages
12937 @item gnus-break-pages
12938 Controls whether @dfn{page breaking} is to take place. If this variable
12939 is non-@code{nil}, the articles will be divided into pages whenever a
12940 page delimiter appears in the article. If this variable is @code{nil},
12941 paging will not be done.
12943 @item gnus-page-delimiter
12944 @vindex gnus-page-delimiter
12945 This is the delimiter mentioned above. By default, it is @samp{^L}
12949 @cindex internationalized domain names
12950 @vindex gnus-use-idna
12951 @item gnus-use-idna
12952 This variable controls whether Gnus performs IDNA decoding of
12953 internationalized domain names inside @samp{From}, @samp{To} and
12954 @samp{Cc} headers. @xref{IDNA, ,IDNA,message, The Message Manual},
12955 for how to compose such messages. This requires
12956 @uref{http://www.gnu.org/software/libidn/, GNU Libidn}, and this
12957 variable is only enabled if you have installed it.
12962 @node Composing Messages
12963 @chapter Composing Messages
12964 @cindex composing messages
12967 @cindex sending mail
12972 @cindex using s/mime
12973 @cindex using smime
12975 @kindex C-c C-c (Post)
12976 All commands for posting and mailing will put you in a message buffer
12977 where you can edit the article all you like, before you send the
12978 article by pressing @kbd{C-c C-c}. @xref{Top, , Overview, message,
12979 Message Manual}. Where the message will be posted/mailed to depends
12980 on your setup (@pxref{Posting Server}).
12983 * Mail:: Mailing and replying.
12984 * Posting Server:: What server should you post and mail via?
12985 * POP before SMTP:: You cannot send a mail unless you read a mail.
12986 * Mail and Post:: Mailing and posting at the same time.
12987 * Archived Messages:: Where Gnus stores the messages you've sent.
12988 * Posting Styles:: An easier way to specify who you are.
12989 * Drafts:: Postponing messages and rejected messages.
12990 * Rejected Articles:: What happens if the server doesn't like your article?
12991 * Signing and encrypting:: How to compose secure messages.
12994 Also @pxref{Canceling and Superseding} for information on how to
12995 remove articles you shouldn't have posted.
13001 Variables for customizing outgoing mail:
13004 @item gnus-uu-digest-headers
13005 @vindex gnus-uu-digest-headers
13006 List of regexps to match headers included in digested messages. The
13007 headers will be included in the sequence they are matched. If
13008 @code{nil} include all headers.
13010 @item gnus-add-to-list
13011 @vindex gnus-add-to-list
13012 If non-@code{nil}, add a @code{to-list} group parameter to mail groups
13013 that have none when you do a @kbd{a}.
13015 @item gnus-confirm-mail-reply-to-news
13016 @vindex gnus-confirm-mail-reply-to-news
13017 If non-@code{nil}, Gnus will ask you for a confirmation when you are
13018 about to reply to news articles by mail. If it is @code{nil}, nothing
13019 interferes in what you want to do. This can also be a function
13020 receiving the group name as the only parameter which should return
13021 non-@code{nil} if a confirmation is needed, or a regular expression
13022 matching group names, where confirmation should be asked for.
13024 If you find yourself never wanting to reply to mail, but occasionally
13025 press @kbd{R} anyway, this variable might be for you.
13027 @item gnus-confirm-treat-mail-like-news
13028 @vindex gnus-confirm-treat-mail-like-news
13029 If non-@code{nil}, Gnus also requests confirmation according to
13030 @code{gnus-confirm-mail-reply-to-news} when replying to mail. This is
13031 useful for treating mailing lists like newsgroups.
13036 @node Posting Server
13037 @section Posting Server
13039 When you press those magical @kbd{C-c C-c} keys to ship off your latest
13040 (extremely intelligent, of course) article, where does it go?
13042 Thank you for asking. I hate you.
13044 It can be quite complicated.
13046 @vindex gnus-post-method
13047 When posting news, Message usually invokes @code{message-send-news}
13048 (@pxref{News Variables, , News Variables, message, Message Manual}).
13049 Normally, Gnus will post using the same select method as you're
13050 reading from (which might be convenient if you're reading lots of
13051 groups from different private servers). However. If the server
13052 you're reading from doesn't allow posting, just reading, you probably
13053 want to use some other server to post your (extremely intelligent and
13054 fabulously interesting) articles. You can then set the
13055 @code{gnus-post-method} to some other method:
13058 (setq gnus-post-method '(nnspool ""))
13061 Now, if you've done this, and then this server rejects your article, or
13062 this server is down, what do you do then? To override this variable you
13063 can use a non-zero prefix to the @kbd{C-c C-c} command to force using
13064 the ``current'' server, to get back the default behavior, for posting.
13066 If you give a zero prefix (i.e., @kbd{C-u 0 C-c C-c}) to that command,
13067 Gnus will prompt you for what method to use for posting.
13069 You can also set @code{gnus-post-method} to a list of select methods.
13070 If that's the case, Gnus will always prompt you for what method to use
13073 Finally, if you want to always post using the native select method,
13074 you can set this variable to @code{native}.
13076 @vindex message-send-mail-function
13077 When sending mail, Message invokes the function specified by the
13078 variable @code{message-send-mail-function}. Gnus tries to set it to a
13079 value suitable for your system.
13080 @xref{Mail Variables, ,Mail Variables,message,Message manual}, for more
13083 @node POP before SMTP
13084 @section POP before SMTP
13085 @cindex pop before smtp
13086 @findex message-smtpmail-send-it
13087 @findex mail-source-touch-pop
13089 Does your @acronym{ISP} require the @acronym{POP}-before-@acronym{SMTP}
13090 authentication? It is whether you need to connect to the @acronym{POP}
13091 mail server within a certain time before sending mails. If so, there is
13092 a convenient way. To do that, put the following lines in your
13093 @file{~/.gnus.el} file:
13096 (setq message-send-mail-function 'message-smtpmail-send-it)
13097 (add-hook 'message-send-mail-hook 'mail-source-touch-pop)
13101 It means to let Gnus connect to the @acronym{POP} mail server in advance
13102 whenever you send a mail. The @code{mail-source-touch-pop} function
13103 does only a @acronym{POP} authentication according to the value of
13104 @code{mail-sources} without fetching mails, just before sending a mail.
13105 Note that you have to use @code{message-smtpmail-send-it} which runs
13106 @code{message-send-mail-hook} rather than @code{smtpmail-send-it} and
13107 set the value of @code{mail-sources} for a @acronym{POP} connection
13108 correctly. @xref{Mail Sources}.
13110 If you have two or more @acronym{POP} mail servers set in
13111 @code{mail-sources}, you may want to specify one of them to
13112 @code{mail-source-primary-source} as the @acronym{POP} mail server to be
13113 used for the @acronym{POP}-before-@acronym{SMTP} authentication. If it
13114 is your primary @acronym{POP} mail server (i.e., you are fetching mails
13115 mainly from that server), you can set it permanently as follows:
13118 (setq mail-source-primary-source
13119 '(pop :server "pop3.mail.server"
13120 :password "secret"))
13124 Otherwise, bind it dynamically only when performing the
13125 @acronym{POP}-before-@acronym{SMTP} authentication as follows:
13128 (add-hook 'message-send-mail-hook
13130 (let ((mail-source-primary-source
13131 '(pop :server "pop3.mail.server"
13132 :password "secret")))
13133 (mail-source-touch-pop))))
13136 @node Mail and Post
13137 @section Mail and Post
13139 Here's a list of variables relevant to both mailing and
13143 @item gnus-mailing-list-groups
13144 @findex gnus-mailing-list-groups
13145 @cindex mailing lists
13147 If your news server offers groups that are really mailing lists
13148 gatewayed to the @acronym{NNTP} server, you can read those groups without
13149 problems, but you can't post/followup to them without some difficulty.
13150 One solution is to add a @code{to-address} to the group parameters
13151 (@pxref{Group Parameters}). An easier thing to do is set the
13152 @code{gnus-mailing-list-groups} to a regexp that matches the groups that
13153 really are mailing lists. Then, at least, followups to the mailing
13154 lists will work most of the time. Posting to these groups (@kbd{a}) is
13155 still a pain, though.
13157 @item gnus-user-agent
13158 @vindex gnus-user-agent
13161 This variable controls which information should be exposed in the
13162 User-Agent header. It can be a list of symbols or a string. Valid
13163 symbols are @code{gnus} (show Gnus version) and @code{emacs} (show Emacs
13164 version). In addition to the Emacs version, you can add @code{codename}
13165 (show (S)XEmacs codename) or either @code{config} (show system
13166 configuration) or @code{type} (show system type). If you set it to a
13167 string, be sure to use a valid format, see RFC 2616.
13171 You may want to do spell-checking on messages that you send out. Or, if
13172 you don't want to spell-check by hand, you could add automatic
13173 spell-checking via the @code{ispell} package:
13176 @findex ispell-message
13178 (add-hook 'message-send-hook 'ispell-message)
13181 If you want to change the @code{ispell} dictionary based on what group
13182 you're in, you could say something like the following:
13185 (add-hook 'gnus-select-group-hook
13189 "^de\\." (gnus-group-real-name gnus-newsgroup-name))
13190 (ispell-change-dictionary "deutsch"))
13192 (ispell-change-dictionary "english")))))
13195 Modify to suit your needs.
13197 @vindex gnus-message-highlight-citation
13198 If @code{gnus-message-highlight-citation} is t, different levels of
13199 citations are highlighted like in Gnus article buffers also in message
13202 @node Archived Messages
13203 @section Archived Messages
13204 @cindex archived messages
13205 @cindex sent messages
13207 Gnus provides a few different methods for storing the mail and news you
13208 send. The default method is to use the @dfn{archive virtual server} to
13209 store the messages. If you want to disable this completely, the
13210 @code{gnus-message-archive-group} variable should be @code{nil}, which
13213 For archiving interesting messages in a group you read, see the
13214 @kbd{B c} (@code{gnus-summary-copy-article}) command (@pxref{Mail
13217 @vindex gnus-message-archive-method
13218 @code{gnus-message-archive-method} says what virtual server Gnus is to
13219 use to store sent messages. The default is @code{"archive"}, and when
13220 actually being used it is expanded into:
13223 (nnfolder "archive"
13224 (nnfolder-directory "~/Mail/archive")
13225 (nnfolder-active-file "~/Mail/archive/active")
13226 (nnfolder-get-new-mail nil)
13227 (nnfolder-inhibit-expiry t))
13231 @vindex gnus-update-message-archive-method
13232 Note: a server like this is saved in the @file{~/.newsrc.eld} file first
13233 so that it may be used as a real method of the server which is named
13234 @code{"archive"} (that is, for the case where
13235 @code{gnus-message-archive-method} is set to @code{"archive"}) ever
13236 since. If it once has been saved, it will never be updated by default
13237 even if you change the value of @code{gnus-message-archive-method}
13238 afterward. Therefore, the server @code{"archive"} doesn't necessarily
13239 mean the @code{nnfolder} server like this at all times. If you want the
13240 saved method to reflect always the value of
13241 @code{gnus-message-archive-method}, set the
13242 @code{gnus-update-message-archive-method} variable to a non-@code{nil}
13243 value. The default value of this variable is @code{nil}.
13246 You can, however, use any mail select method (@code{nnml},
13247 @code{nnmbox}, etc.). @code{nnfolder} is a quite likable select method
13248 for doing this sort of thing, though. If you don't like the default
13249 directory chosen, you could say something like:
13252 (setq gnus-message-archive-method
13253 '(nnfolder "archive"
13254 (nnfolder-inhibit-expiry t)
13255 (nnfolder-active-file "~/News/sent-mail/active")
13256 (nnfolder-directory "~/News/sent-mail/")))
13259 @vindex gnus-message-archive-group
13261 Gnus will insert @code{Gcc} headers in all outgoing messages that point
13262 to one or more group(s) on that server. Which group to use is
13263 determined by the @code{gnus-message-archive-group} variable.
13265 This variable can be used to do the following:
13269 Messages will be saved in that group.
13271 Note that you can include a select method in the group name, then the
13272 message will not be stored in the select method given by
13273 @code{gnus-message-archive-method}, but in the select method specified
13274 by the group name, instead. Suppose @code{gnus-message-archive-method}
13275 has the default value shown above. Then setting
13276 @code{gnus-message-archive-group} to @code{"foo"} means that outgoing
13277 messages are stored in @samp{nnfolder+archive:foo}, but if you use the
13278 value @code{"nnml:foo"}, then outgoing messages will be stored in
13281 @item a list of strings
13282 Messages will be saved in all those groups.
13284 @item an alist of regexps, functions and forms
13285 When a key ``matches'', the result is used.
13288 No message archiving will take place. This is the default.
13293 Just saving to a single group called @samp{MisK}:
13295 (setq gnus-message-archive-group "MisK")
13298 Saving to two groups, @samp{MisK} and @samp{safe}:
13300 (setq gnus-message-archive-group '("MisK" "safe"))
13303 Save to different groups based on what group you are in:
13305 (setq gnus-message-archive-group
13306 '(("^alt" "sent-to-alt")
13307 ("mail" "sent-to-mail")
13308 (".*" "sent-to-misc")))
13311 More complex stuff:
13313 (setq gnus-message-archive-group
13314 '((if (message-news-p)
13319 How about storing all news messages in one file, but storing all mail
13320 messages in one file per month:
13323 (setq gnus-message-archive-group
13324 '((if (message-news-p)
13326 (concat "mail." (format-time-string "%Y-%m")))))
13329 @c (XEmacs 19.13 doesn't have @code{format-time-string}, so you'll have to
13330 @c use a different value for @code{gnus-message-archive-group} there.)
13332 Now, when you send a message off, it will be stored in the appropriate
13333 group. (If you want to disable storing for just one particular message,
13334 you can just remove the @code{Gcc} header that has been inserted.) The
13335 archive group will appear in the group buffer the next time you start
13336 Gnus, or the next time you press @kbd{F} in the group buffer. You can
13337 enter it and read the articles in it just like you'd read any other
13338 group. If the group gets really big and annoying, you can simply rename
13339 if (using @kbd{G r} in the group buffer) to something
13340 nice---@samp{misc-mail-september-1995}, or whatever. New messages will
13341 continue to be stored in the old (now empty) group.
13343 That's the default method of archiving sent messages. Gnus offers a
13344 different way for the people who don't like the default method. In that
13345 case you should set @code{gnus-message-archive-group} to @code{nil};
13346 this will disable archiving.
13349 @item gnus-outgoing-message-group
13350 @vindex gnus-outgoing-message-group
13351 All outgoing messages will be put in this group. If you want to store
13352 all your outgoing mail and articles in the group @samp{nnml:archive},
13353 you set this variable to that value. This variable can also be a list of
13356 If you want to have greater control over what group to put each
13357 message in, you can set this variable to a function that checks the
13358 current newsgroup name and then returns a suitable group name (or list
13361 This variable can be used instead of @code{gnus-message-archive-group},
13362 but the latter is the preferred method.
13364 @item gnus-gcc-mark-as-read
13365 @vindex gnus-gcc-mark-as-read
13366 If non-@code{nil}, automatically mark @code{Gcc} articles as read.
13368 @item gnus-gcc-externalize-attachments
13369 @vindex gnus-gcc-externalize-attachments
13370 If @code{nil}, attach files as normal parts in Gcc copies; if a regexp
13371 and matches the Gcc group name, attach files as external parts; if it is
13372 @code{all}, attach local files as external parts; if it is other
13373 non-@code{nil}, the behavior is the same as @code{all}, but it may be
13374 changed in the future.
13379 @node Posting Styles
13380 @section Posting Styles
13381 @cindex posting styles
13384 All them variables, they make my head swim.
13386 So what if you want a different @code{Organization} and signature based
13387 on what groups you post to? And you post both from your home machine
13388 and your work machine, and you want different @code{From} lines, and so
13391 @vindex gnus-posting-styles
13392 One way to do stuff like that is to write clever hooks that change the
13393 variables you need to have changed. That's a bit boring, so somebody
13394 came up with the bright idea of letting the user specify these things in
13395 a handy alist. Here's an example of a @code{gnus-posting-styles}
13400 (signature "Peace and happiness")
13401 (organization "What me?"))
13403 (signature "Death to everybody"))
13404 ("comp.emacs.i-love-it"
13405 (organization "Emacs is it")))
13408 As you might surmise from this example, this alist consists of several
13409 @dfn{styles}. Each style will be applicable if the first element
13410 ``matches'', in some form or other. The entire alist will be iterated
13411 over, from the beginning towards the end, and each match will be
13412 applied, which means that attributes in later styles that match override
13413 the same attributes in earlier matching styles. So
13414 @samp{comp.programming.literate} will have the @samp{Death to everybody}
13415 signature and the @samp{What me?} @code{Organization} header.
13417 The first element in each style is called the @code{match}. If it's a
13418 string, then Gnus will try to regexp match it against the group name.
13419 If it is the form @code{(header @var{match} @var{regexp})}, then Gnus
13420 will look in the original article for a header whose name is
13421 @var{match} and compare that @var{regexp}. @var{match} and
13422 @var{regexp} are strings. (The original article is the one you are
13423 replying or following up to. If you are not composing a reply or a
13424 followup, then there is nothing to match against.) If the
13425 @code{match} is a function symbol, that function will be called with
13426 no arguments. If it's a variable symbol, then the variable will be
13427 referenced. If it's a list, then that list will be @code{eval}ed. In
13428 any case, if this returns a non-@code{nil} value, then the style is
13429 said to @dfn{match}.
13431 Each style may contain an arbitrary amount of @dfn{attributes}. Each
13432 attribute consists of a @code{(@var{name} @var{value})} pair. In
13433 addition, you can also use the @code{(@var{name} :file @var{value})}
13434 form or the @code{(@var{name} :value @var{value})} form. Where
13435 @code{:file} signifies @var{value} represents a file name and its
13436 contents should be used as the attribute value, @code{:value} signifies
13437 @var{value} does not represent a file name explicitly. The attribute
13438 name can be one of:
13441 @item @code{signature}
13442 @item @code{signature-file}
13443 @item @code{x-face-file}
13444 @item @code{address}, overriding @code{user-mail-address}
13445 @item @code{name}, overriding @code{(user-full-name)}
13449 Note that the @code{signature-file} attribute honors the variable
13450 @code{message-signature-directory}.
13452 The attribute name can also be a string or a symbol. In that case,
13453 this will be used as a header name, and the value will be inserted in
13454 the headers of the article; if the value is @code{nil}, the header
13455 name will be removed. If the attribute name is @code{eval}, the form
13456 is evaluated, and the result is thrown away.
13458 The attribute value can be a string (used verbatim), a function with
13459 zero arguments (the return value will be used), a variable (its value
13460 will be used) or a list (it will be @code{eval}ed and the return value
13461 will be used). The functions and sexps are called/@code{eval}ed in the
13462 message buffer that is being set up. The headers of the current article
13463 are available through the @code{message-reply-headers} variable, which
13464 is a vector of the following headers: number subject from date id
13465 references chars lines xref extra.
13467 @vindex message-reply-headers
13469 If you wish to check whether the message you are about to compose is
13470 meant to be a news article or a mail message, you can check the values
13471 of the @code{message-news-p} and @code{message-mail-p} functions.
13473 @findex message-mail-p
13474 @findex message-news-p
13476 So here's a new example:
13479 (setq gnus-posting-styles
13481 (signature-file "~/.signature")
13483 (x-face-file "~/.xface")
13484 (x-url (getenv "WWW_HOME"))
13485 (organization "People's Front Against MWM"))
13487 (signature my-funny-signature-randomizer))
13488 ((equal (system-name) "gnarly") ;; @r{A form}
13489 (signature my-quote-randomizer))
13490 (message-news-p ;; @r{A function symbol}
13491 (signature my-news-signature))
13492 (window-system ;; @r{A value symbol}
13493 ("X-Window-System" (format "%s" window-system)))
13494 ;; @r{If I'm replying to Larsi, set the Organization header.}
13495 ((header "from" "larsi.*org")
13496 (Organization "Somewhere, Inc."))
13497 ((posting-from-work-p) ;; @r{A user defined function}
13498 (signature-file "~/.work-signature")
13499 (address "user@@bar.foo")
13500 (body "You are fired.\n\nSincerely, your boss.")
13501 (organization "Important Work, Inc"))
13503 (From (with-current-buffer gnus-article-buffer
13504 (message-fetch-field "to"))))
13506 (signature-file "~/.mail-signature"))))
13509 The @samp{nnml:.*} rule means that you use the @code{To} address as the
13510 @code{From} address in all your outgoing replies, which might be handy
13511 if you fill many roles.
13512 You may also use @code{message-alternative-emails} instead.
13513 @xref{Message Headers, ,Message Headers, message, Message Manual}.
13519 If you are writing a message (mail or news) and suddenly remember that
13520 you have a steak in the oven (or some pesto in the food processor, you
13521 craaazy vegetarians), you'll probably wish there was a method to save
13522 the message you are writing so that you can continue editing it some
13523 other day, and send it when you feel its finished.
13525 Well, don't worry about it. Whenever you start composing a message of
13526 some sort using the Gnus mail and post commands, the buffer you get will
13527 automatically associate to an article in a special @dfn{draft} group.
13528 If you save the buffer the normal way (@kbd{C-x C-s}, for instance), the
13529 article will be saved there. (Auto-save files also go to the draft
13533 @vindex nndraft-directory
13534 The draft group is a special group (which is implemented as an
13535 @code{nndraft} group, if you absolutely have to know) called
13536 @samp{nndraft:drafts}. The variable @code{nndraft-directory} says where
13537 @code{nndraft} is to store its files. What makes this group special is
13538 that you can't tick any articles in it or mark any articles as
13539 read---all articles in the group are permanently unread.
13541 If the group doesn't exist, it will be created and you'll be subscribed
13542 to it. The only way to make it disappear from the Group buffer is to
13543 unsubscribe it. The special properties of the draft group comes from
13544 a group property (@pxref{Group Parameters}), and if lost the group
13545 behaves like any other group. This means the commands below will not
13546 be available. To restore the special properties of the group, the
13547 simplest way is to kill the group, using @kbd{C-k}, and restart
13548 Gnus. The group is automatically created again with the
13549 correct parameters. The content of the group is not lost.
13551 @c @findex gnus-dissociate-buffer-from-draft
13552 @c @kindex C-c M-d (Mail)
13553 @c @kindex C-c M-d (Post)
13554 @c @findex gnus-associate-buffer-with-draft
13555 @c @kindex C-c C-d (Mail)
13556 @c @kindex C-c C-d (Post)
13557 @c If you're writing some super-secret message that you later want to
13558 @c encode with PGP before sending, you may wish to turn the auto-saving
13559 @c (and association with the draft group) off. You never know who might be
13560 @c interested in reading all your extremely valuable and terribly horrible
13561 @c and interesting secrets. The @kbd{C-c M-d}
13562 @c (@code{gnus-dissociate-buffer-from-draft}) command does that for you.
13563 @c If you change your mind and want to turn the auto-saving back on again,
13564 @c @kbd{C-c C-d} (@code{gnus-associate-buffer-with-draft} does that.
13566 @c @vindex gnus-use-draft
13567 @c To leave association with the draft group off by default, set
13568 @c @code{gnus-use-draft} to @code{nil}. It is @code{t} by default.
13570 @findex gnus-draft-edit-message
13571 @kindex D e (Draft)
13572 When you want to continue editing the article, you simply enter the
13573 draft group and push @kbd{D e} (@code{gnus-draft-edit-message}) to do
13574 that. You will be placed in a buffer where you left off.
13576 Rejected articles will also be put in this draft group (@pxref{Rejected
13579 @findex gnus-draft-send-all-messages
13580 @kindex D s (Draft)
13581 @findex gnus-draft-send-message
13582 @kindex D S (Draft)
13583 If you have lots of rejected messages you want to post (or mail) without
13584 doing further editing, you can use the @kbd{D s} command
13585 (@code{gnus-draft-send-message}). This command understands the
13586 process/prefix convention (@pxref{Process/Prefix}). The @kbd{D S}
13587 command (@code{gnus-draft-send-all-messages}) will ship off all messages
13590 @findex gnus-draft-toggle-sending
13591 @kindex D t (Draft)
13592 If you have some messages that you wish not to send, you can use the
13593 @kbd{D t} (@code{gnus-draft-toggle-sending}) command to mark the message
13594 as unsendable. This is a toggling command.
13597 @node Rejected Articles
13598 @section Rejected Articles
13599 @cindex rejected articles
13601 Sometimes a news server will reject an article. Perhaps the server
13602 doesn't like your face. Perhaps it just feels miserable. Perhaps
13603 @emph{there be demons}. Perhaps you have included too much cited text.
13604 Perhaps the disk is full. Perhaps the server is down.
13606 These situations are, of course, totally beyond the control of Gnus.
13607 (Gnus, of course, loves the way you look, always feels great, has angels
13608 fluttering around inside of it, doesn't care about how much cited text
13609 you include, never runs full and never goes down.) So Gnus saves these
13610 articles until some later time when the server feels better.
13612 The rejected articles will automatically be put in a special draft group
13613 (@pxref{Drafts}). When the server comes back up again, you'd then
13614 typically enter that group and send all the articles off.
13616 @node Signing and encrypting
13617 @section Signing and encrypting
13619 @cindex using s/mime
13620 @cindex using smime
13622 Gnus can digitally sign and encrypt your messages, using vanilla
13623 @acronym{PGP} format or @acronym{PGP/MIME} or @acronym{S/MIME}. For
13624 decoding such messages, see the @code{mm-verify-option} and
13625 @code{mm-decrypt-option} options (@pxref{Security}).
13627 @vindex gnus-message-replysign
13628 @vindex gnus-message-replyencrypt
13629 @vindex gnus-message-replysignencrypted
13630 Often, you would like to sign replies to people who send you signed
13631 messages. Even more often, you might want to encrypt messages which
13632 are in reply to encrypted messages. Gnus offers
13633 @code{gnus-message-replysign} to enable the former, and
13634 @code{gnus-message-replyencrypt} for the latter. In addition, setting
13635 @code{gnus-message-replysignencrypted} (on by default) will sign
13636 automatically encrypted messages.
13638 Instructing @acronym{MML} to perform security operations on a
13639 @acronym{MIME} part is done using the @kbd{C-c C-m s} key map for
13640 signing and the @kbd{C-c C-m c} key map for encryption, as follows.
13645 @kindex C-c C-m s s (Message)
13646 @findex mml-secure-message-sign-smime
13648 Digitally sign current message using @acronym{S/MIME}.
13651 @kindex C-c C-m s o (Message)
13652 @findex mml-secure-message-sign-pgp
13654 Digitally sign current message using @acronym{PGP}.
13657 @kindex C-c C-m s p (Message)
13658 @findex mml-secure-message-sign-pgp
13660 Digitally sign current message using @acronym{PGP/MIME}.
13663 @kindex C-c C-m c s (Message)
13664 @findex mml-secure-message-encrypt-smime
13666 Digitally encrypt current message using @acronym{S/MIME}.
13669 @kindex C-c C-m c o (Message)
13670 @findex mml-secure-message-encrypt-pgp
13672 Digitally encrypt current message using @acronym{PGP}.
13675 @kindex C-c C-m c p (Message)
13676 @findex mml-secure-message-encrypt-pgpmime
13678 Digitally encrypt current message using @acronym{PGP/MIME}.
13681 @kindex C-c C-m C-n (Message)
13682 @findex mml-unsecure-message
13683 Remove security related @acronym{MML} tags from message.
13687 @xref{Security, ,Security, message, Message Manual}, for more information.
13689 @node Select Methods
13690 @chapter Select Methods
13691 @cindex foreign groups
13692 @cindex select methods
13694 A @dfn{foreign group} is a group not read by the usual (or
13695 default) means. It could be, for instance, a group from a different
13696 @acronym{NNTP} server, it could be a virtual group, or it could be your own
13697 personal mail group.
13699 A foreign group (or any group, really) is specified by a @dfn{name} and
13700 a @dfn{select method}. To take the latter first, a select method is a
13701 list where the first element says what back end to use (e.g. @code{nntp},
13702 @code{nnspool}, @code{nnml}) and the second element is the @dfn{server
13703 name}. There may be additional elements in the select method, where the
13704 value may have special meaning for the back end in question.
13706 One could say that a select method defines a @dfn{virtual server}---so
13707 we do just that (@pxref{Server Buffer}).
13709 The @dfn{name} of the group is the name the back end will recognize the
13712 For instance, the group @samp{soc.motss} on the @acronym{NNTP} server
13713 @samp{some.where.edu} will have the name @samp{soc.motss} and select
13714 method @code{(nntp "some.where.edu")}. Gnus will call this group
13715 @samp{nntp+some.where.edu:soc.motss}, even though the @code{nntp}
13716 back end just knows this group as @samp{soc.motss}.
13718 The different methods all have their peculiarities, of course.
13721 * Server Buffer:: Making and editing virtual servers.
13722 * Getting News:: Reading USENET news with Gnus.
13723 * Getting Mail:: Reading your personal mail with Gnus.
13724 * Browsing the Web:: Getting messages from a plethora of Web sources.
13725 * IMAP:: Using Gnus as a @acronym{IMAP} client.
13726 * Other Sources:: Reading directories, files, SOUP packets.
13727 * Combined Groups:: Combining groups into one group.
13728 * Email Based Diary:: Using mails to manage diary events in Gnus.
13729 * Gnus Unplugged:: Reading news and mail offline.
13733 @node Server Buffer
13734 @section Server Buffer
13736 Traditionally, a @dfn{server} is a machine or a piece of software that
13737 one connects to, and then requests information from. Gnus does not
13738 connect directly to any real servers, but does all transactions through
13739 one back end or other. But that's just putting one layer more between
13740 the actual media and Gnus, so we might just as well say that each
13741 back end represents a virtual server.
13743 For instance, the @code{nntp} back end may be used to connect to several
13744 different actual @acronym{NNTP} servers, or, perhaps, to many different ports
13745 on the same actual @acronym{NNTP} server. You tell Gnus which back end to
13746 use, and what parameters to set by specifying a @dfn{select method}.
13748 These select method specifications can sometimes become quite
13749 complicated---say, for instance, that you want to read from the
13750 @acronym{NNTP} server @samp{news.funet.fi} on port number 13, which
13751 hangs if queried for @acronym{NOV} headers and has a buggy select. Ahem.
13752 Anyway, if you had to specify that for each group that used this
13753 server, that would be too much work, so Gnus offers a way of naming
13754 select methods, which is what you do in the server buffer.
13756 To enter the server buffer, use the @kbd{^}
13757 (@code{gnus-group-enter-server-mode}) command in the group buffer.
13760 * Server Buffer Format:: You can customize the look of this buffer.
13761 * Server Commands:: Commands to manipulate servers.
13762 * Example Methods:: Examples server specifications.
13763 * Creating a Virtual Server:: An example session.
13764 * Server Variables:: Which variables to set.
13765 * Servers and Methods:: You can use server names as select methods.
13766 * Unavailable Servers:: Some servers you try to contact may be down.
13769 @vindex gnus-server-mode-hook
13770 @code{gnus-server-mode-hook} is run when creating the server buffer.
13773 @node Server Buffer Format
13774 @subsection Server Buffer Format
13775 @cindex server buffer format
13777 @vindex gnus-server-line-format
13778 You can change the look of the server buffer lines by changing the
13779 @code{gnus-server-line-format} variable. This is a @code{format}-like
13780 variable, with some simple extensions:
13785 How the news is fetched---the back end name.
13788 The name of this server.
13791 Where the news is to be fetched from---the address.
13794 The opened/closed/denied status of the server.
13797 Whether this server is agentized.
13800 @vindex gnus-server-mode-line-format
13801 The mode line can also be customized by using the
13802 @code{gnus-server-mode-line-format} variable (@pxref{Mode Line
13803 Formatting}). The following specs are understood:
13813 Also @pxref{Formatting Variables}.
13816 @node Server Commands
13817 @subsection Server Commands
13818 @cindex server commands
13824 @cindex keys, reserved for users (Server)
13825 The key @kbd{v} is reserved for users. You can bind it to some
13826 command or better use it as a prefix key.
13830 @findex gnus-server-add-server
13831 Add a new server (@code{gnus-server-add-server}).
13835 @findex gnus-server-edit-server
13836 Edit a server (@code{gnus-server-edit-server}).
13839 @kindex SPACE (Server)
13840 @findex gnus-server-read-server
13841 Browse the current server (@code{gnus-server-read-server}).
13845 @findex gnus-server-exit
13846 Return to the group buffer (@code{gnus-server-exit}).
13850 @findex gnus-server-kill-server
13851 Kill the current server (@code{gnus-server-kill-server}).
13855 @findex gnus-server-yank-server
13856 Yank the previously killed server (@code{gnus-server-yank-server}).
13860 @findex gnus-server-copy-server
13861 Copy the current server (@code{gnus-server-copy-server}).
13865 @findex gnus-server-list-servers
13866 List all servers (@code{gnus-server-list-servers}).
13870 @findex gnus-server-scan-server
13871 Request that the server scan its sources for new articles
13872 (@code{gnus-server-scan-server}). This is mainly sensible with mail
13877 @findex gnus-server-regenerate-server
13878 Request that the server regenerate all its data structures
13879 (@code{gnus-server-regenerate-server}). This can be useful if you have
13880 a mail back end that has gotten out of sync.
13884 @findex gnus-server-compact-server
13886 Compact all groups in the server under point
13887 (@code{gnus-server-compact-server}). Currently implemented only in
13888 nnml (@pxref{Mail Spool}). This removes gaps between article numbers,
13889 hence getting a correct total article count.
13894 @node Example Methods
13895 @subsection Example Methods
13897 Most select methods are pretty simple and self-explanatory:
13900 (nntp "news.funet.fi")
13903 Reading directly from the spool is even simpler:
13909 As you can see, the first element in a select method is the name of the
13910 back end, and the second is the @dfn{address}, or @dfn{name}, if you
13913 After these two elements, there may be an arbitrary number of
13914 @code{(@var{variable} @var{form})} pairs.
13916 To go back to the first example---imagine that you want to read from
13917 port 15 on that machine. This is what the select method should
13921 (nntp "news.funet.fi" (nntp-port-number 15))
13924 You should read the documentation to each back end to find out what
13925 variables are relevant, but here's an @code{nnmh} example:
13927 @code{nnmh} is a mail back end that reads a spool-like structure. Say
13928 you have two structures that you wish to access: One is your private
13929 mail spool, and the other is a public one. Here's the possible spec for
13933 (nnmh "private" (nnmh-directory "~/private/mail/"))
13936 (This server is then called @samp{private}, but you may have guessed
13939 Here's the method for a public spool:
13943 (nnmh-directory "/usr/information/spool/")
13944 (nnmh-get-new-mail nil))
13950 If you are behind a firewall and only have access to the @acronym{NNTP}
13951 server from the firewall machine, you can instruct Gnus to @code{rlogin}
13952 on the firewall machine and connect with
13953 @uref{http://netcat.sourceforge.net/, netcat} from there to the
13954 @acronym{NNTP} server.
13955 Doing this can be rather fiddly, but your virtual server definition
13956 should probably look something like this:
13960 (nntp-open-connection-function nntp-open-via-rlogin-and-netcat)
13961 (nntp-via-address "the.firewall.machine")
13962 (nntp-address "the.real.nntp.host"))
13965 If you want to use the wonderful @code{ssh} program to provide a
13966 compressed connection over the modem line, you could add the following
13967 configuration to the example above:
13970 (nntp-via-rlogin-command "ssh")
13973 See also @code{nntp-via-rlogin-command-switches}. Here's an example for
13974 an indirect connection:
13977 (setq gnus-select-method
13979 (nntp-address "news.server.example")
13980 (nntp-via-user-name "intermediate_user_name")
13981 (nntp-via-address "intermediate.host.example")
13982 (nntp-via-rlogin-command "ssh")
13983 (nntp-via-rlogin-command-switches ("-C"))
13984 (nntp-open-connection-function nntp-open-via-rlogin-and-netcat)))
13987 This means that you have to have set up @code{ssh-agent} correctly to
13988 provide automatic authorization, of course.
13990 If you're behind a firewall, but have direct access to the outside world
13991 through a wrapper command like "runsocks", you could open a socksified
13992 netcat connection to the news server as follows:
13996 (nntp-pre-command "runsocks")
13997 (nntp-open-connection-function nntp-open-netcat-stream)
13998 (nntp-address "the.news.server"))
14002 @node Creating a Virtual Server
14003 @subsection Creating a Virtual Server
14005 If you're saving lots of articles in the cache by using persistent
14006 articles, you may want to create a virtual server to read the cache.
14008 First you need to add a new server. The @kbd{a} command does that. It
14009 would probably be best to use @code{nnml} to read the cache. You
14010 could also use @code{nnspool} or @code{nnmh}, though.
14012 Type @kbd{a nnml RET cache RET}.
14014 You should now have a brand new @code{nnml} virtual server called
14015 @samp{cache}. You now need to edit it to have the right definitions.
14016 Type @kbd{e} to edit the server. You'll be entered into a buffer that
14017 will contain the following:
14027 (nnml-directory "~/News/cache/")
14028 (nnml-active-file "~/News/cache/active"))
14031 Type @kbd{C-c C-c} to return to the server buffer. If you now press
14032 @kbd{RET} over this virtual server, you should be entered into a browse
14033 buffer, and you should be able to enter any of the groups displayed.
14036 @node Server Variables
14037 @subsection Server Variables
14038 @cindex server variables
14039 @cindex server parameters
14041 One sticky point when defining variables (both on back ends and in Emacs
14042 in general) is that some variables are typically initialized from other
14043 variables when the definition of the variables is being loaded. If you
14044 change the ``base'' variable after the variables have been loaded, you
14045 won't change the ``derived'' variables.
14047 This typically affects directory and file variables. For instance,
14048 @code{nnml-directory} is @file{~/Mail/} by default, and all @code{nnml}
14049 directory variables are initialized from that variable, so
14050 @code{nnml-active-file} will be @file{~/Mail/active}. If you define a
14051 new virtual @code{nnml} server, it will @emph{not} suffice to set just
14052 @code{nnml-directory}---you have to explicitly set all the file
14053 variables to be what you want them to be. For a complete list of
14054 variables for each back end, see each back end's section later in this
14055 manual, but here's an example @code{nnml} definition:
14059 (nnml-directory "~/my-mail/")
14060 (nnml-active-file "~/my-mail/active")
14061 (nnml-newsgroups-file "~/my-mail/newsgroups"))
14064 Server variables are often called @dfn{server parameters}.
14066 @node Servers and Methods
14067 @subsection Servers and Methods
14069 Wherever you would normally use a select method
14070 (e.g. @code{gnus-secondary-select-method}, in the group select method,
14071 when browsing a foreign server) you can use a virtual server name
14072 instead. This could potentially save lots of typing. And it's nice all
14076 @node Unavailable Servers
14077 @subsection Unavailable Servers
14079 If a server seems to be unreachable, Gnus will mark that server as
14080 @code{denied}. That means that any subsequent attempt to make contact
14081 with that server will just be ignored. ``It can't be opened,'' Gnus
14082 will tell you, without making the least effort to see whether that is
14083 actually the case or not.
14085 That might seem quite naughty, but it does make sense most of the time.
14086 Let's say you have 10 groups subscribed to on server
14087 @samp{nephelococcygia.com}. This server is located somewhere quite far
14088 away from you and the machine is quite slow, so it takes 1 minute just
14089 to find out that it refuses connection to you today. If Gnus were to
14090 attempt to do that 10 times, you'd be quite annoyed, so Gnus won't
14091 attempt to do that. Once it has gotten a single ``connection refused'',
14092 it will regard that server as ``down''.
14094 So, what happens if the machine was only feeling unwell temporarily?
14095 How do you test to see whether the machine has come up again?
14097 You jump to the server buffer (@pxref{Server Buffer}) and poke it
14098 with the following commands:
14104 @findex gnus-server-open-server
14105 Try to establish connection to the server on the current line
14106 (@code{gnus-server-open-server}).
14110 @findex gnus-server-close-server
14111 Close the connection (if any) to the server
14112 (@code{gnus-server-close-server}).
14116 @findex gnus-server-deny-server
14117 Mark the current server as unreachable
14118 (@code{gnus-server-deny-server}).
14121 @kindex M-o (Server)
14122 @findex gnus-server-open-all-servers
14123 Open the connections to all servers in the buffer
14124 (@code{gnus-server-open-all-servers}).
14127 @kindex M-c (Server)
14128 @findex gnus-server-close-all-servers
14129 Close the connections to all servers in the buffer
14130 (@code{gnus-server-close-all-servers}).
14134 @findex gnus-server-remove-denials
14135 Remove all marks to whether Gnus was denied connection from any servers
14136 (@code{gnus-server-remove-denials}).
14140 @findex gnus-server-offline-server
14141 Set server status to offline (@code{gnus-server-offline-server}).
14147 @section Getting News
14148 @cindex reading news
14149 @cindex news back ends
14151 A newsreader is normally used for reading news. Gnus currently provides
14152 only two methods of getting news---it can read from an @acronym{NNTP} server,
14153 or it can read from a local spool.
14156 * NNTP:: Reading news from an @acronym{NNTP} server.
14157 * News Spool:: Reading news from the local spool.
14165 Subscribing to a foreign group from an @acronym{NNTP} server is rather easy.
14166 You just specify @code{nntp} as method and the address of the @acronym{NNTP}
14167 server as the, uhm, address.
14169 If the @acronym{NNTP} server is located at a non-standard port, setting the
14170 third element of the select method to this port number should allow you
14171 to connect to the right port. You'll have to edit the group info for
14172 that (@pxref{Foreign Groups}).
14174 The name of the foreign group can be the same as a native group. In
14175 fact, you can subscribe to the same group from as many different servers
14176 you feel like. There will be no name collisions.
14178 The following variables can be used to create a virtual @code{nntp}
14183 @item nntp-server-opened-hook
14184 @vindex nntp-server-opened-hook
14185 @cindex @sc{mode reader}
14187 @cindex authentication
14188 @cindex nntp authentication
14189 @findex nntp-send-authinfo
14190 @findex nntp-send-mode-reader
14191 is run after a connection has been made. It can be used to send
14192 commands to the @acronym{NNTP} server after it has been contacted. By
14193 default it sends the command @code{MODE READER} to the server with the
14194 @code{nntp-send-mode-reader} function. This function should always be
14195 present in this hook.
14197 @item nntp-authinfo-function
14198 @vindex nntp-authinfo-function
14199 @findex nntp-send-authinfo
14200 @vindex nntp-authinfo-file
14201 This function will be used to send @samp{AUTHINFO} to the @acronym{NNTP}
14202 server. The default function is @code{nntp-send-authinfo}, which looks
14203 through your @file{~/.authinfo} (or whatever you've set the
14204 @code{nntp-authinfo-file} variable to) for applicable entries. If none
14205 are found, it will prompt you for a login name and a password. The
14206 format of the @file{~/.authinfo} file is (almost) the same as the
14207 @code{ftp} @file{~/.netrc} file, which is defined in the @code{ftp}
14208 manual page, but here are the salient facts:
14212 The file contains one or more line, each of which define one server.
14215 Each line may contain an arbitrary number of token/value pairs.
14217 The valid tokens include @samp{machine}, @samp{login}, @samp{password},
14218 @samp{default}. In addition Gnus introduces two new tokens, not present
14219 in the original @file{.netrc}/@code{ftp} syntax, namely @samp{port} and
14220 @samp{force}. (This is the only way the @file{.authinfo} file format
14221 deviates from the @file{.netrc} file format.) @samp{port} is used to
14222 indicate what port on the server the credentials apply to and
14223 @samp{force} is explained below.
14227 Here's an example file:
14230 machine news.uio.no login larsi password geheimnis
14231 machine nntp.ifi.uio.no login larsi force yes
14234 The token/value pairs may appear in any order; @samp{machine} doesn't
14235 have to be first, for instance.
14237 In this example, both login name and password have been supplied for the
14238 former server, while the latter has only the login name listed, and the
14239 user will be prompted for the password. The latter also has the
14240 @samp{force} tag, which means that the authinfo will be sent to the
14241 @var{nntp} server upon connection; the default (i.e., when there is not
14242 @samp{force} tag) is to not send authinfo to the @var{nntp} server
14243 until the @var{nntp} server asks for it.
14245 You can also add @samp{default} lines that will apply to all servers
14246 that don't have matching @samp{machine} lines.
14252 This will force sending @samp{AUTHINFO} commands to all servers not
14253 previously mentioned.
14255 Remember to not leave the @file{~/.authinfo} file world-readable.
14257 @item nntp-server-action-alist
14258 @vindex nntp-server-action-alist
14259 This is a list of regexps to match on server types and actions to be
14260 taken when matches are made. For instance, if you want Gnus to beep
14261 every time you connect to innd, you could say something like:
14264 (setq nntp-server-action-alist
14265 '(("innd" (ding))))
14268 You probably don't want to do that, though.
14270 The default value is
14273 '(("nntpd 1\\.5\\.11t"
14274 (remove-hook 'nntp-server-opened-hook
14275 'nntp-send-mode-reader)))
14278 This ensures that Gnus doesn't send the @code{MODE READER} command to
14279 nntpd 1.5.11t, since that command chokes that server, I've been told.
14281 @item nntp-maximum-request
14282 @vindex nntp-maximum-request
14283 If the @acronym{NNTP} server doesn't support @acronym{NOV} headers, this back end
14284 will collect headers by sending a series of @code{head} commands. To
14285 speed things up, the back end sends lots of these commands without
14286 waiting for reply, and then reads all the replies. This is controlled
14287 by the @code{nntp-maximum-request} variable, and is 400 by default. If
14288 your network is buggy, you should set this to 1.
14290 @item nntp-connection-timeout
14291 @vindex nntp-connection-timeout
14292 If you have lots of foreign @code{nntp} groups that you connect to
14293 regularly, you're sure to have problems with @acronym{NNTP} servers not
14294 responding properly, or being too loaded to reply within reasonable
14295 time. This is can lead to awkward problems, which can be helped
14296 somewhat by setting @code{nntp-connection-timeout}. This is an integer
14297 that says how many seconds the @code{nntp} back end should wait for a
14298 connection before giving up. If it is @code{nil}, which is the default,
14299 no timeouts are done.
14301 @item nntp-nov-is-evil
14302 @vindex nntp-nov-is-evil
14303 If the @acronym{NNTP} server does not support @acronym{NOV}, you could set this
14304 variable to @code{t}, but @code{nntp} usually checks automatically whether @acronym{NOV}
14307 @item nntp-xover-commands
14308 @vindex nntp-xover-commands
14309 @cindex @acronym{NOV}
14311 List of strings used as commands to fetch @acronym{NOV} lines from a
14312 server. The default value of this variable is @code{("XOVER"
14316 @vindex nntp-nov-gap
14317 @code{nntp} normally sends just one big request for @acronym{NOV} lines to
14318 the server. The server responds with one huge list of lines. However,
14319 if you have read articles 2-5000 in the group, and only want to read
14320 article 1 and 5001, that means that @code{nntp} will fetch 4999 @acronym{NOV}
14321 lines that you will not need. This variable says how
14322 big a gap between two consecutive articles is allowed to be before the
14323 @code{XOVER} request is split into several request. Note that if your
14324 network is fast, setting this variable to a really small number means
14325 that fetching will probably be slower. If this variable is @code{nil},
14326 @code{nntp} will never split requests. The default is 5.
14328 @item nntp-xref-number-is-evil
14329 @vindex nntp-xref-number-is-evil
14330 When Gnus refers to an article having the @code{Message-ID} that a user
14331 specifies or having the @code{Message-ID} of the parent article of the
14332 current one (@pxref{Finding the Parent}), Gnus sends a @code{HEAD}
14333 command to the @acronym{NNTP} server to know where it is, and the server
14334 returns the data containing the pairs of a group and an article number
14335 in the @code{Xref} header. Gnus normally uses the article number to
14336 refer to the article if the data shows that that article is in the
14337 current group, while it uses the @code{Message-ID} otherwise. However,
14338 some news servers, e.g., ones running Diablo, run multiple engines
14339 having the same articles but article numbers are not kept synchronized
14340 between them. In that case, the article number that appears in the
14341 @code{Xref} header varies by which engine is chosen, so you cannot refer
14342 to the parent article that is in the current group, for instance. If
14343 you connect to such a server, set this variable to a non-@code{nil}
14344 value, and Gnus never uses article numbers. For example:
14347 (setq gnus-select-method
14349 (nntp-address "newszilla.example.com")
14350 (nntp-xref-number-is-evil t)
14354 The default value of this server variable is @code{nil}.
14356 @item nntp-prepare-server-hook
14357 @vindex nntp-prepare-server-hook
14358 A hook run before attempting to connect to an @acronym{NNTP} server.
14360 @item nntp-record-commands
14361 @vindex nntp-record-commands
14362 If non-@code{nil}, @code{nntp} will log all commands it sends to the
14363 @acronym{NNTP} server (along with a timestamp) in the @samp{*nntp-log*}
14364 buffer. This is useful if you are debugging a Gnus/@acronym{NNTP} connection
14365 that doesn't seem to work.
14367 @item nntp-open-connection-function
14368 @vindex nntp-open-connection-function
14369 It is possible to customize how the connection to the nntp server will
14370 be opened. If you specify an @code{nntp-open-connection-function}
14371 parameter, Gnus will use that function to establish the connection.
14372 Seven pre-made functions are supplied. These functions can be grouped
14373 in two categories: direct connection functions (four pre-made), and
14374 indirect ones (three pre-made).
14376 @item nntp-never-echoes-commands
14377 @vindex nntp-never-echoes-commands
14378 Non-@code{nil} means the nntp server never echoes commands. It is
14379 reported that some nntps server doesn't echo commands. So, you may want
14380 to set this to non-@code{nil} in the method for such a server setting
14381 @code{nntp-open-connection-function} to @code{nntp-open-ssl-stream} for
14382 example. The default value is @code{nil}. Note that the
14383 @code{nntp-open-connection-functions-never-echo-commands} variable
14384 overrides the @code{nil} value of this variable.
14386 @item nntp-open-connection-functions-never-echo-commands
14387 @vindex nntp-open-connection-functions-never-echo-commands
14388 List of functions that never echo commands. Add or set a function which
14389 you set to @code{nntp-open-connection-function} to this list if it does
14390 not echo commands. Note that a non-@code{nil} value of the
14391 @code{nntp-never-echoes-commands} variable overrides this variable. The
14392 default value is @code{(nntp-open-network-stream)}.
14394 @item nntp-prepare-post-hook
14395 @vindex nntp-prepare-post-hook
14396 A hook run just before posting an article. If there is no
14397 @code{Message-ID} header in the article and the news server provides the
14398 recommended ID, it will be added to the article before running this
14399 hook. It is useful to make @code{Cancel-Lock} headers even if you
14400 inhibit Gnus to add a @code{Message-ID} header, you could say:
14403 (add-hook 'nntp-prepare-post-hook 'canlock-insert-header)
14406 Note that not all servers support the recommended ID. This works for
14407 INN versions 2.3.0 and later, for instance.
14412 * Direct Functions:: Connecting directly to the server.
14413 * Indirect Functions:: Connecting indirectly to the server.
14414 * Common Variables:: Understood by several connection functions.
14415 * NNTP marks:: Storing marks for @acronym{NNTP} servers.
14419 @node Direct Functions
14420 @subsubsection Direct Functions
14421 @cindex direct connection functions
14423 These functions are called direct because they open a direct connection
14424 between your machine and the @acronym{NNTP} server. The behavior of these
14425 functions is also affected by commonly understood variables
14426 (@pxref{Common Variables}).
14429 @findex nntp-open-network-stream
14430 @item nntp-open-network-stream
14431 This is the default, and simply connects to some port or other on the
14434 @findex nntp-open-tls-stream
14435 @item nntp-open-tls-stream
14436 Opens a connection to a server over a @dfn{secure} channel. To use
14437 this you must have @uref{http://www.gnu.org/software/gnutls/, GNUTLS}
14438 installed. You then define a server as follows:
14441 ;; @r{"nntps" is port 563 and is predefined in our @file{/etc/services}}
14442 ;; @r{however, @samp{gnutls-cli -p} doesn't like named ports.}
14444 (nntp "snews.bar.com"
14445 (nntp-open-connection-function nntp-open-tls-stream)
14446 (nntp-port-number 563)
14447 (nntp-address "snews.bar.com"))
14450 @findex nntp-open-ssl-stream
14451 @item nntp-open-ssl-stream
14452 Opens a connection to a server over a @dfn{secure} channel. To use
14453 this you must have @uref{http://www.openssl.org, OpenSSL} or
14454 @uref{ftp://ftp.psy.uq.oz.au/pub/Crypto/SSL, SSLeay} installed. You
14455 then define a server as follows:
14458 ;; @r{"snews" is port 563 and is predefined in our @file{/etc/services}}
14459 ;; @r{however, @samp{openssl s_client -port} doesn't like named ports.}
14461 (nntp "snews.bar.com"
14462 (nntp-open-connection-function nntp-open-ssl-stream)
14463 (nntp-port-number 563)
14464 (nntp-address "snews.bar.com"))
14467 @findex nntp-open-netcat-stream
14468 @item nntp-open-netcat-stream
14469 Opens a connection to an @acronym{NNTP} server using the @code{netcat}
14470 program. You might wonder why this function exists, since we have
14471 the default @code{nntp-open-network-stream} which would do the job. (One
14472 of) the reason(s) is that if you are behind a firewall but have direct
14473 connections to the outside world thanks to a command wrapper like
14474 @code{runsocks}, you can use it like this:
14478 (nntp-pre-command "runsocks")
14479 (nntp-open-connection-function nntp-open-netcat-stream)
14480 (nntp-address "the.news.server"))
14483 With the default method, you would need to wrap your whole Emacs
14484 session, which is not a good idea.
14486 @findex nntp-open-telnet-stream
14487 @item nntp-open-telnet-stream
14488 Like @code{nntp-open-netcat-stream}, but uses @code{telnet} rather than
14489 @code{netcat}. @code{telnet} is a bit less robust because of things
14490 like line-end-conversion, but sometimes netcat is simply
14491 not available. The previous example would turn into:
14495 (nntp-pre-command "runsocks")
14496 (nntp-open-connection-function nntp-open-telnet-stream)
14497 (nntp-address "the.news.server")
14498 (nntp-end-of-line "\n"))
14503 @node Indirect Functions
14504 @subsubsection Indirect Functions
14505 @cindex indirect connection functions
14507 These functions are called indirect because they connect to an
14508 intermediate host before actually connecting to the @acronym{NNTP} server.
14509 All of these functions and related variables are also said to belong to
14510 the ``via'' family of connection: they're all prefixed with ``via'' to make
14511 things cleaner. The behavior of these functions is also affected by
14512 commonly understood variables (@pxref{Common Variables}).
14515 @item nntp-open-via-rlogin-and-netcat
14516 @findex nntp-open-via-rlogin-and-netcat
14517 Does an @samp{rlogin} on a remote system, and then uses @code{netcat} to connect
14518 to the real @acronym{NNTP} server from there. This is useful for instance if
14519 you need to connect to a firewall machine first.
14521 @code{nntp-open-via-rlogin-and-netcat}-specific variables:
14524 @item nntp-via-rlogin-command
14525 @vindex nntp-via-rlogin-command
14526 Command used to log in on the intermediate host. The default is
14527 @samp{rsh}, but @samp{ssh} is a popular alternative.
14529 @item nntp-via-rlogin-command-switches
14530 @vindex nntp-via-rlogin-command-switches
14531 List of strings to be used as the switches to
14532 @code{nntp-via-rlogin-command}. The default is @code{nil}. If you use
14533 @samp{ssh} for @code{nntp-via-rlogin-command}, you may set this to
14534 @samp{("-C")} in order to compress all data connections.
14537 @item nntp-open-via-rlogin-and-telnet
14538 @findex nntp-open-via-rlogin-and-telnet
14539 Does essentially the same, but uses @code{telnet} instead of @samp{netcat}
14540 to connect to the real @acronym{NNTP} server from the intermediate host.
14541 @code{telnet} is a bit less robust because of things like
14542 line-end-conversion, but sometimes @code{netcat} is simply not available.
14544 @code{nntp-open-via-rlogin-and-telnet}-specific variables:
14547 @item nntp-telnet-command
14548 @vindex nntp-telnet-command
14549 Command used to connect to the real @acronym{NNTP} server from the
14550 intermediate host. The default is @samp{telnet}.
14552 @item nntp-telnet-switches
14553 @vindex nntp-telnet-switches
14554 List of strings to be used as the switches to the
14555 @code{nntp-telnet-command} command. The default is @code{("-8")}.
14557 @item nntp-via-rlogin-command
14558 @vindex nntp-via-rlogin-command
14559 Command used to log in on the intermediate host. The default is
14560 @samp{rsh}, but @samp{ssh} is a popular alternative.
14562 @item nntp-via-rlogin-command-switches
14563 @vindex nntp-via-rlogin-command-switches
14564 List of strings to be used as the switches to
14565 @code{nntp-via-rlogin-command}. If you use @samp{ssh}, you may need to set
14566 this to @samp{("-t" "-e" "none")} or @samp{("-C" "-t" "-e" "none")} if
14567 the telnet command requires a pseudo-tty allocation on an intermediate
14568 host. The default is @code{nil}.
14571 Note that you may want to change the value for @code{nntp-end-of-line}
14572 to @samp{\n} (@pxref{Common Variables}).
14574 @item nntp-open-via-telnet-and-telnet
14575 @findex nntp-open-via-telnet-and-telnet
14576 Does essentially the same, but uses @samp{telnet} instead of
14577 @samp{rlogin} to connect to the intermediate host.
14579 @code{nntp-open-via-telnet-and-telnet}-specific variables:
14582 @item nntp-via-telnet-command
14583 @vindex nntp-via-telnet-command
14584 Command used to @code{telnet} the intermediate host. The default is
14587 @item nntp-via-telnet-switches
14588 @vindex nntp-via-telnet-switches
14589 List of strings to be used as the switches to the
14590 @code{nntp-via-telnet-command} command. The default is @samp{("-8")}.
14592 @item nntp-via-user-password
14593 @vindex nntp-via-user-password
14594 Password to use when logging in on the intermediate host.
14596 @item nntp-via-envuser
14597 @vindex nntp-via-envuser
14598 If non-@code{nil}, the intermediate @code{telnet} session (client and
14599 server both) will support the @code{ENVIRON} option and not prompt for
14600 login name. This works for Solaris @code{telnet}, for instance.
14602 @item nntp-via-shell-prompt
14603 @vindex nntp-via-shell-prompt
14604 Regexp matching the shell prompt on the intermediate host. The default
14605 is @samp{bash\\|\$ *\r?$\\|> *\r?}.
14609 Note that you may want to change the value for @code{nntp-end-of-line}
14610 to @samp{\n} (@pxref{Common Variables}).
14614 Here are some additional variables that are understood by all the above
14619 @item nntp-via-user-name
14620 @vindex nntp-via-user-name
14621 User name to use when connecting to the intermediate host.
14623 @item nntp-via-address
14624 @vindex nntp-via-address
14625 Address of the intermediate host to connect to.
14630 @node Common Variables
14631 @subsubsection Common Variables
14633 The following variables affect the behavior of all, or several of the
14634 pre-made connection functions. When not specified, all functions are
14635 affected (the values of the following variables will be used as the
14636 default if each virtual @code{nntp} server doesn't specify those server
14637 variables individually).
14641 @item nntp-pre-command
14642 @vindex nntp-pre-command
14643 A command wrapper to use when connecting through a non native
14644 connection function (all except @code{nntp-open-network-stream},
14645 @code{nntp-open-tls-stream}, and @code{nntp-open-ssl-stream}). This is
14646 where you would put a @samp{SOCKS} wrapper for instance.
14649 @vindex nntp-address
14650 The address of the @acronym{NNTP} server.
14652 @item nntp-port-number
14653 @vindex nntp-port-number
14654 Port number to connect to the @acronym{NNTP} server. The default is
14655 @samp{nntp}. If you use @acronym{NNTP} over
14656 @acronym{TLS}/@acronym{SSL}, you may want to use integer ports rather
14657 than named ports (i.e, use @samp{563} instead of @samp{snews} or
14658 @samp{nntps}), because external @acronym{TLS}/@acronym{SSL} tools may
14659 not work with named ports.
14661 @item nntp-end-of-line
14662 @vindex nntp-end-of-line
14663 String to use as end-of-line marker when talking to the @acronym{NNTP}
14664 server. This is @samp{\r\n} by default, but should be @samp{\n} when
14665 using a non native telnet connection function.
14667 @item nntp-netcat-command
14668 @vindex nntp-netcat-command
14669 Command to use when connecting to the @acronym{NNTP} server through
14670 @samp{netcat}. This is @emph{not} for an intermediate host. This is
14671 just for the real @acronym{NNTP} server. The default is
14674 @item nntp-netcat-switches
14675 @vindex nntp-netcat-switches
14676 A list of switches to pass to @code{nntp-netcat-command}. The default
14682 @subsubsection NNTP marks
14683 @cindex storing NNTP marks
14685 Gnus stores marks (@pxref{Marking Articles}) for @acronym{NNTP}
14686 servers in marks files. A marks file records what marks you have set
14687 in a group and each file is specific to the corresponding server.
14688 Marks files are stored in @file{~/News/marks}
14689 (@code{nntp-marks-directory}) under a classic hierarchy resembling
14690 that of a news server, for example marks for the group
14691 @samp{gmane.discuss} on the news.gmane.org server will be stored in
14692 the file @file{~/News/marks/news.gmane.org/gmane/discuss/.marks}.
14694 Marks files are useful because you can copy the @file{~/News/marks}
14695 directory (using rsync, scp or whatever) to another Gnus installation,
14696 and it will realize what articles you have read and marked. The data
14697 in @file{~/News/marks} has priority over the same data in
14698 @file{~/.newsrc.eld}.
14700 Note that marks files are very much server-specific: Gnus remembers
14701 the article numbers so if you don't use the same servers on both
14702 installations things are most likely to break (most @acronym{NNTP}
14703 servers do not use the same article numbers as any other server).
14704 However, if you use servers A, B, C on one installation and servers A,
14705 D, E on the other, you can sync the marks files for A and then you'll
14706 get synchronization for that server between the two installations.
14708 Using @acronym{NNTP} marks can possibly incur a performance penalty so
14709 if Gnus feels sluggish, try setting the @code{nntp-marks-is-evil}
14710 variable to @code{t}. Marks will then be stored in @file{~/.newsrc.eld}.
14716 @item nntp-marks-is-evil
14717 @vindex nntp-marks-is-evil
14718 If non-@code{nil}, this back end will ignore any marks files. The
14719 default is @code{nil}.
14721 @item nntp-marks-directory
14722 @vindex nntp-marks-directory
14723 The directory where marks for nntp groups will be stored.
14729 @subsection News Spool
14733 Subscribing to a foreign group from the local spool is extremely easy,
14734 and might be useful, for instance, to speed up reading groups that
14735 contain very big articles---@samp{alt.binaries.pictures.furniture}, for
14738 Anyway, you just specify @code{nnspool} as the method and @code{""} (or
14739 anything else) as the address.
14741 If you have access to a local spool, you should probably use that as the
14742 native select method (@pxref{Finding the News}). It is normally faster
14743 than using an @code{nntp} select method, but might not be. It depends.
14744 You just have to try to find out what's best at your site.
14748 @item nnspool-inews-program
14749 @vindex nnspool-inews-program
14750 Program used to post an article.
14752 @item nnspool-inews-switches
14753 @vindex nnspool-inews-switches
14754 Parameters given to the inews program when posting an article.
14756 @item nnspool-spool-directory
14757 @vindex nnspool-spool-directory
14758 Where @code{nnspool} looks for the articles. This is normally
14759 @file{/usr/spool/news/}.
14761 @item nnspool-nov-directory
14762 @vindex nnspool-nov-directory
14763 Where @code{nnspool} will look for @acronym{NOV} files. This is normally@*
14764 @file{/usr/spool/news/over.view/}.
14766 @item nnspool-lib-dir
14767 @vindex nnspool-lib-dir
14768 Where the news lib dir is (@file{/usr/lib/news/} by default).
14770 @item nnspool-active-file
14771 @vindex nnspool-active-file
14772 The name of the active file.
14774 @item nnspool-newsgroups-file
14775 @vindex nnspool-newsgroups-file
14776 The name of the group descriptions file.
14778 @item nnspool-history-file
14779 @vindex nnspool-history-file
14780 The name of the news history file.
14782 @item nnspool-active-times-file
14783 @vindex nnspool-active-times-file
14784 The name of the active date file.
14786 @item nnspool-nov-is-evil
14787 @vindex nnspool-nov-is-evil
14788 If non-@code{nil}, @code{nnspool} won't try to use any @acronym{NOV} files
14791 @item nnspool-sift-nov-with-sed
14792 @vindex nnspool-sift-nov-with-sed
14794 If non-@code{nil}, which is the default, use @code{sed} to get the
14795 relevant portion from the overview file. If @code{nil},
14796 @code{nnspool} will load the entire file into a buffer and process it
14803 @section Getting Mail
14804 @cindex reading mail
14807 Reading mail with a newsreader---isn't that just plain WeIrD? But of
14811 * Mail in a Newsreader:: Important introductory notes.
14812 * Getting Started Reading Mail:: A simple cookbook example.
14813 * Splitting Mail:: How to create mail groups.
14814 * Mail Sources:: How to tell Gnus where to get mail from.
14815 * Mail Back End Variables:: Variables for customizing mail handling.
14816 * Fancy Mail Splitting:: Gnus can do hairy splitting of incoming mail.
14817 * Group Mail Splitting:: Use group customize to drive mail splitting.
14818 * Incorporating Old Mail:: What about the old mail you have?
14819 * Expiring Mail:: Getting rid of unwanted mail.
14820 * Washing Mail:: Removing cruft from the mail you get.
14821 * Duplicates:: Dealing with duplicated mail.
14822 * Not Reading Mail:: Using mail back ends for reading other files.
14823 * Choosing a Mail Back End:: Gnus can read a variety of mail formats.
14827 @node Mail in a Newsreader
14828 @subsection Mail in a Newsreader
14830 If you are used to traditional mail readers, but have decided to switch
14831 to reading mail with Gnus, you may find yourself experiencing something
14832 of a culture shock.
14834 Gnus does not behave like traditional mail readers. If you want to make
14835 it behave that way, you can, but it's an uphill battle.
14837 Gnus, by default, handles all its groups using the same approach. This
14838 approach is very newsreaderly---you enter a group, see the new/unread
14839 messages, and when you read the messages, they get marked as read, and
14840 you don't see them any more. (Unless you explicitly ask for them.)
14842 In particular, you do not do anything explicitly to delete messages.
14844 Does this mean that all the messages that have been marked as read are
14845 deleted? How awful!
14847 But, no, it means that old messages are @dfn{expired} according to some
14848 scheme or other. For news messages, the expire process is controlled by
14849 the news administrator; for mail, the expire process is controlled by
14850 you. The expire process for mail is covered in depth in @ref{Expiring
14853 What many Gnus users find, after using it a while for both news and
14854 mail, is that the transport mechanism has very little to do with how
14855 they want to treat a message.
14857 Many people subscribe to several mailing lists. These are transported
14858 via @acronym{SMTP}, and are therefore mail. But we might go for weeks without
14859 answering, or even reading these messages very carefully. We may not
14860 need to save them because if we should need to read one again, they are
14861 archived somewhere else.
14863 Some people have local news groups which have only a handful of readers.
14864 These are transported via @acronym{NNTP}, and are therefore news. But we may need
14865 to read and answer a large fraction of the messages very carefully in
14866 order to do our work. And there may not be an archive, so we may need
14867 to save the interesting messages the same way we would personal mail.
14869 The important distinction turns out to be not the transport mechanism,
14870 but other factors such as how interested we are in the subject matter,
14871 or how easy it is to retrieve the message if we need to read it again.
14873 Gnus provides many options for sorting mail into ``groups'' which behave
14874 like newsgroups, and for treating each group (whether mail or news)
14877 Some users never get comfortable using the Gnus (ahem) paradigm and wish
14878 that Gnus should grow up and be a male, er, mail reader. It is possible
14879 to whip Gnus into a more mailreaderly being, but, as said before, it's
14880 not easy. People who prefer proper mail readers should try @sc{vm}
14881 instead, which is an excellent, and proper, mail reader.
14883 I don't mean to scare anybody off, but I want to make it clear that you
14884 may be required to learn a new way of thinking about messages. After
14885 you've been subjected to The Gnus Way, you will come to love it. I can
14886 guarantee it. (At least the guy who sold me the Emacs Subliminal
14887 Brain-Washing Functions that I've put into Gnus did guarantee it. You
14888 Will Be Assimilated. You Love Gnus. You Love The Gnus Mail Way.
14892 @node Getting Started Reading Mail
14893 @subsection Getting Started Reading Mail
14895 It's quite easy to use Gnus to read your new mail. You just plonk the
14896 mail back end of your choice into @code{gnus-secondary-select-methods},
14897 and things will happen automatically.
14899 For instance, if you want to use @code{nnml} (which is a ``one file per
14900 mail'' back end), you could put the following in your @file{~/.gnus.el} file:
14903 (setq gnus-secondary-select-methods '((nnml "")))
14906 Now, the next time you start Gnus, this back end will be queried for new
14907 articles, and it will move all the messages in your spool file to its
14908 directory, which is @file{~/Mail/} by default. The new group that will
14909 be created (@samp{mail.misc}) will be subscribed, and you can read it
14910 like any other group.
14912 You will probably want to split the mail into several groups, though:
14915 (setq nnmail-split-methods
14916 '(("junk" "^From:.*Lars Ingebrigtsen")
14917 ("crazy" "^Subject:.*die\\|^Organization:.*flabby")
14921 This will result in three new @code{nnml} mail groups being created:
14922 @samp{nnml:junk}, @samp{nnml:crazy}, and @samp{nnml:other}. All the
14923 mail that doesn't fit into the first two groups will be placed in the
14926 This should be sufficient for reading mail with Gnus. You might want to
14927 give the other sections in this part of the manual a perusal, though.
14928 Especially @pxref{Choosing a Mail Back End} and @pxref{Expiring Mail}.
14931 @node Splitting Mail
14932 @subsection Splitting Mail
14933 @cindex splitting mail
14934 @cindex mail splitting
14935 @cindex mail filtering (splitting)
14937 @vindex nnmail-split-methods
14938 The @code{nnmail-split-methods} variable says how the incoming mail is
14939 to be split into groups.
14942 (setq nnmail-split-methods
14943 '(("mail.junk" "^From:.*Lars Ingebrigtsen")
14944 ("mail.crazy" "^Subject:.*die\\|^Organization:.*flabby")
14945 ("mail.other" "")))
14948 This variable is a list of lists, where the first element of each of
14949 these lists is the name of the mail group (they do not have to be called
14950 something beginning with @samp{mail}, by the way), and the second
14951 element is a regular expression used on the header of each mail to
14952 determine if it belongs in this mail group. The first string may
14953 contain @samp{\\1} forms, like the ones used by @code{replace-match} to
14954 insert sub-expressions from the matched text. For instance:
14957 ("list.\\1" "From:.* \\(.*\\)-list@@majordomo.com")
14961 In that case, @code{nnmail-split-lowercase-expanded} controls whether
14962 the inserted text should be made lowercase. @xref{Fancy Mail Splitting}.
14964 The second element can also be a function. In that case, it will be
14965 called narrowed to the headers with the first element of the rule as the
14966 argument. It should return a non-@code{nil} value if it thinks that the
14967 mail belongs in that group.
14969 @cindex @samp{bogus} group
14970 The last of these groups should always be a general one, and the regular
14971 expression should @emph{always} be @samp{""} so that it matches any mails
14972 that haven't been matched by any of the other regexps. (These rules are
14973 processed from the beginning of the alist toward the end. The first rule
14974 to make a match will ``win'', unless you have crossposting enabled. In
14975 that case, all matching rules will ``win''.) If no rule matched, the mail
14976 will end up in the @samp{bogus} group. When new groups are created by
14977 splitting mail, you may want to run @code{gnus-group-find-new-groups} to
14978 see the new groups. This also applies to the @samp{bogus} group.
14980 If you like to tinker with this yourself, you can set this variable to a
14981 function of your choice. This function will be called without any
14982 arguments in a buffer narrowed to the headers of an incoming mail
14983 message. The function should return a list of group names that it
14984 thinks should carry this mail message.
14986 Note that the mail back ends are free to maul the poor, innocent,
14987 incoming headers all they want to. They all add @code{Lines} headers;
14988 some add @code{X-Gnus-Group} headers; most rename the Unix mbox
14989 @code{From<SPACE>} line to something else.
14991 @vindex nnmail-crosspost
14992 The mail back ends all support cross-posting. If several regexps match,
14993 the mail will be ``cross-posted'' to all those groups.
14994 @code{nnmail-crosspost} says whether to use this mechanism or not. Note
14995 that no articles are crossposted to the general (@samp{""}) group.
14997 @vindex nnmail-crosspost-link-function
15000 @code{nnmh} and @code{nnml} makes crossposts by creating hard links to
15001 the crossposted articles. However, not all file systems support hard
15002 links. If that's the case for you, set
15003 @code{nnmail-crosspost-link-function} to @code{copy-file}. (This
15004 variable is @code{add-name-to-file} by default.)
15006 @kindex M-x nnmail-split-history
15007 @findex nnmail-split-history
15008 If you wish to see where the previous mail split put the messages, you
15009 can use the @kbd{M-x nnmail-split-history} command. If you wish to see
15010 where re-spooling messages would put the messages, you can use
15011 @code{gnus-summary-respool-trace} and related commands (@pxref{Mail
15014 @vindex nnmail-split-header-length-limit
15015 Header lines longer than the value of
15016 @code{nnmail-split-header-length-limit} are excluded from the split
15019 @vindex nnmail-mail-splitting-decodes
15020 @vindex nnmail-mail-splitting-charset
15021 By default, splitting does not decode headers, so you can not match on
15022 non-@acronym{ASCII} strings. But it is useful if you want to match
15023 articles based on the raw header data. To enable it, set the
15024 @code{nnmail-mail-splitting-decodes} variable to a non-@code{nil} value.
15025 In addition, the value of the @code{nnmail-mail-splitting-charset}
15026 variable is used for decoding non-@acronym{MIME} encoded string when
15027 @code{nnmail-mail-splitting-decodes} is non-@code{nil}. The default
15028 value is @code{nil} which means not to decode non-@acronym{MIME} encoded
15029 string. A suitable value for you will be @code{undecided} or be the
15030 charset used normally in mails you are interested in.
15032 @vindex nnmail-resplit-incoming
15033 By default, splitting is performed on all incoming messages. If you
15034 specify a @code{directory} entry for the variable @code{mail-sources}
15035 (@pxref{Mail Source Specifiers}), however, then splitting does
15036 @emph{not} happen by default. You can set the variable
15037 @code{nnmail-resplit-incoming} to a non-@code{nil} value to make
15038 splitting happen even in this case. (This variable has no effect on
15039 other kinds of entries.)
15041 Gnus gives you all the opportunity you could possibly want for shooting
15042 yourself in the foot. Let's say you create a group that will contain
15043 all the mail you get from your boss. And then you accidentally
15044 unsubscribe from the group. Gnus will still put all the mail from your
15045 boss in the unsubscribed group, and so, when your boss mails you ``Have
15046 that report ready by Monday or you're fired!'', you'll never see it and,
15047 come Tuesday, you'll still believe that you're gainfully employed while
15048 you really should be out collecting empty bottles to save up for next
15049 month's rent money.
15053 @subsection Mail Sources
15055 Mail can be gotten from many different sources---the mail spool, from
15056 a @acronym{POP} mail server, from a procmail directory, or from a
15057 maildir, for instance.
15060 * Mail Source Specifiers:: How to specify what a mail source is.
15061 * Mail Source Customization:: Some variables that influence things.
15062 * Fetching Mail:: Using the mail source specifiers.
15066 @node Mail Source Specifiers
15067 @subsubsection Mail Source Specifiers
15069 @cindex mail server
15072 @cindex mail source
15074 You tell Gnus how to fetch mail by setting @code{mail-sources}
15075 (@pxref{Fetching Mail}) to a @dfn{mail source specifier}.
15080 (pop :server "pop3.mailserver.com" :user "myname")
15083 As can be observed, a mail source specifier is a list where the first
15084 element is a @dfn{mail source type}, followed by an arbitrary number of
15085 @dfn{keywords}. Keywords that are not explicitly specified are given
15088 The @code{mail-sources} is global for all mail groups. You can specify
15089 an additional mail source for a particular group by including the
15090 @code{group} mail specifier in @code{mail-sources}, and setting a
15091 @code{mail-source} group parameter (@pxref{Group Parameters}) specifying
15092 a single mail source. When this is used, @code{mail-sources} is
15093 typically just @code{(group)}; the @code{mail-source} parameter for a
15094 group might look like this:
15097 (mail-source . (file :path "home/user/spools/foo.spool"))
15100 This means that the group's (and only this group's) messages will be
15101 fetched from the spool file @samp{/user/spools/foo.spool}.
15103 The following mail source types are available:
15107 Get mail from a single file; typically from the mail spool.
15113 The file name. Defaults to the value of the @env{MAIL}
15114 environment variable or the value of @code{rmail-spool-directory}
15115 (usually something like @file{/usr/mail/spool/user-name}).
15119 Script run before/after fetching mail.
15122 An example file mail source:
15125 (file :path "/usr/spool/mail/user-name")
15128 Or using the default file name:
15134 If the mail spool file is not located on the local machine, it's best
15135 to use @acronym{POP} or @acronym{IMAP} or the like to fetch the mail.
15136 You can not use ange-ftp file names here---it has no way to lock the
15137 mail spool while moving the mail.
15139 If it's impossible to set up a proper server, you can use ssh instead.
15143 '((file :prescript "ssh host bin/getmail >%t")))
15146 The @samp{getmail} script would look something like the following:
15150 # getmail - move mail from spool to stdout
15153 MOVEMAIL=/usr/lib/emacs/20.3/i386-redhat-linux/movemail
15155 rm -f $TMP; $MOVEMAIL $MAIL $TMP >/dev/null && cat $TMP
15158 Alter this script to fit the @samp{movemail} and temporary
15159 file you want to use.
15163 @vindex nnmail-scan-directory-mail-source-once
15164 Get mail from several files in a directory. This is typically used
15165 when you have procmail split the incoming mail into several files.
15166 That is, there is a one-to-one correspondence between files in that
15167 directory and groups, so that mail from the file @file{foo.bar.spool}
15168 will be put in the group @code{foo.bar}. (You can change the suffix
15169 to be used instead of @code{.spool}.) Setting
15170 @code{nnmail-scan-directory-mail-source-once} to non-@code{nil} forces
15171 Gnus to scan the mail source only once. This is particularly useful
15172 if you want to scan mail groups at a specified level.
15174 @vindex nnmail-resplit-incoming
15175 There is also the variable @code{nnmail-resplit-incoming}, if you set
15176 that to a non-@code{nil} value, then the normal splitting process is
15177 applied to all the files from the directory, @ref{Splitting Mail}.
15183 The name of the directory where the files are. There is no default
15187 Only files ending with this suffix are used. The default is
15191 Only files that have this predicate return non-@code{nil} are returned.
15192 The default is @code{identity}. This is used as an additional
15193 filter---only files that have the right suffix @emph{and} satisfy this
15194 predicate are considered.
15198 Script run before/after fetching mail.
15202 An example directory mail source:
15205 (directory :path "/home/user-name/procmail-dir/"
15210 Get mail from a @acronym{POP} server.
15216 The name of the @acronym{POP} server. The default is taken from the
15217 @env{MAILHOST} environment variable.
15220 The port number of the @acronym{POP} server. This can be a number (eg,
15221 @samp{:port 1234}) or a string (eg, @samp{:port "pop3"}). If it is a
15222 string, it should be a service name as listed in @file{/etc/services} on
15223 Unix systems. The default is @samp{"pop3"}. On some systems you might
15224 need to specify it as @samp{"pop-3"} instead.
15227 The user name to give to the @acronym{POP} server. The default is the login
15231 The password to give to the @acronym{POP} server. If not specified,
15232 the user is prompted.
15235 The program to use to fetch mail from the @acronym{POP} server. This
15236 should be a @code{format}-like string. Here's an example:
15239 fetchmail %u@@%s -P %p %t
15242 The valid format specifier characters are:
15246 The name of the file the mail is to be moved to. This must always be
15247 included in this string.
15250 The name of the server.
15253 The port number of the server.
15256 The user name to use.
15259 The password to use.
15262 The values used for these specs are taken from the values you give the
15263 corresponding keywords.
15266 A script to be run before fetching the mail. The syntax is the same as
15267 the @code{:program} keyword. This can also be a function to be run.
15270 A script to be run after fetching the mail. The syntax is the same as
15271 the @code{:program} keyword. This can also be a function to be run.
15274 The function to use to fetch mail from the @acronym{POP} server. The
15275 function is called with one parameter---the name of the file where the
15276 mail should be moved to.
15278 @item :authentication
15279 This can be either the symbol @code{password} or the symbol @code{apop}
15280 and says what authentication scheme to use. The default is
15285 @vindex pop3-movemail
15286 @vindex pop3-leave-mail-on-server
15287 If the @code{:program} and @code{:function} keywords aren't specified,
15288 @code{pop3-movemail} will be used. If @code{pop3-leave-mail-on-server}
15289 is non-@code{nil} the mail is to be left on the @acronym{POP} server
15290 after fetching when using @code{pop3-movemail}. Note that POP servers
15291 maintain no state information between sessions, so what the client
15292 believes is there and what is actually there may not match up. If they
15293 do not, then you may get duplicate mails or the whole thing can fall
15294 apart and leave you with a corrupt mailbox.
15296 Here are some examples for getting mail from a @acronym{POP} server.
15297 Fetch from the default @acronym{POP} server, using the default user
15298 name, and default fetcher:
15304 Fetch from a named server with a named user and password:
15307 (pop :server "my.pop.server"
15308 :user "user-name" :password "secret")
15311 Use @samp{movemail} to move the mail:
15314 (pop :program "movemail po:%u %t %p")
15318 Get mail from a maildir. This is a type of mailbox that is supported by
15319 at least qmail and postfix, where each file in a special directory
15320 contains exactly one mail.
15326 The name of the directory where the mails are stored. The default is
15327 taken from the @env{MAILDIR} environment variable or
15330 The subdirectories of the Maildir. The default is
15331 @samp{("new" "cur")}.
15333 @c If you sometimes look at your mail through a pop3 daemon before fetching
15334 @c them with Gnus, you may also have to fetch your mails from the
15335 @c @code{cur} directory inside the maildir, like in the first example
15338 You can also get mails from remote hosts (because maildirs don't suffer
15339 from locking problems).
15343 Two example maildir mail sources:
15346 (maildir :path "/home/user-name/Maildir/"
15347 :subdirs ("cur" "new"))
15351 (maildir :path "/user@@remotehost.org:~/Maildir/"
15356 Get mail from a @acronym{IMAP} server. If you don't want to use
15357 @acronym{IMAP} as intended, as a network mail reading protocol (ie
15358 with nnimap), for some reason or other, Gnus let you treat it similar
15359 to a @acronym{POP} server and fetches articles from a given
15360 @acronym{IMAP} mailbox. @xref{IMAP}, for more information.
15362 Note that for the Kerberos, GSSAPI, @acronym{TLS}/@acronym{SSL} and STARTTLS support you
15363 may need external programs and libraries, @xref{IMAP}.
15369 The name of the @acronym{IMAP} server. The default is taken from the
15370 @env{MAILHOST} environment variable.
15373 The port number of the @acronym{IMAP} server. The default is @samp{143}, or
15374 @samp{993} for @acronym{TLS}/@acronym{SSL} connections.
15377 The user name to give to the @acronym{IMAP} server. The default is the login
15381 The password to give to the @acronym{IMAP} server. If not specified, the user is
15385 What stream to use for connecting to the server, this is one of the
15386 symbols in @code{imap-stream-alist}. Right now, this means
15387 @samp{gssapi}, @samp{kerberos4}, @samp{starttls}, @samp{tls},
15388 @samp{ssl}, @samp{shell} or the default @samp{network}.
15390 @item :authentication
15391 Which authenticator to use for authenticating to the server, this is
15392 one of the symbols in @code{imap-authenticator-alist}. Right now,
15393 this means @samp{gssapi}, @samp{kerberos4}, @samp{digest-md5},
15394 @samp{cram-md5}, @samp{anonymous} or the default @samp{login}.
15397 When using the `shell' :stream, the contents of this variable is
15398 mapped into the @code{imap-shell-program} variable. This should be a
15399 @code{format}-like string (or list of strings). Here's an example:
15405 Make sure nothing is interfering with the output of the program, e.g.,
15406 don't forget to redirect the error output to the void. The valid format
15407 specifier characters are:
15411 The name of the server.
15414 User name from @code{imap-default-user}.
15417 The port number of the server.
15420 The values used for these specs are taken from the values you give the
15421 corresponding keywords.
15424 The name of the mailbox to get mail from. The default is @samp{INBOX}
15425 which normally is the mailbox which receives incoming mail.
15428 The predicate used to find articles to fetch. The default, @samp{UNSEEN
15429 UNDELETED}, is probably the best choice for most people, but if you
15430 sometimes peek in your mailbox with a @acronym{IMAP} client and mark some
15431 articles as read (or; SEEN) you might want to set this to @samp{1:*}.
15432 Then all articles in the mailbox is fetched, no matter what. For a
15433 complete list of predicates, see RFC 2060 section 6.4.4.
15436 How to flag fetched articles on the server, the default @samp{\Deleted}
15437 will mark them as deleted, an alternative would be @samp{\Seen} which
15438 would simply mark them as read. These are the two most likely choices,
15439 but more flags are defined in RFC 2060 section 2.3.2.
15442 If non-@code{nil}, don't remove all articles marked as deleted in the
15443 mailbox after finishing the fetch.
15447 An example @acronym{IMAP} mail source:
15450 (imap :server "mail.mycorp.com"
15452 :fetchflag "\\Seen")
15456 Get mail from a webmail server, such as @uref{http://www.hotmail.com/},
15457 @uref{http://webmail.netscape.com/}, @uref{http://www.netaddress.com/},
15458 @uref{http://mail.yahoo.com/}.
15460 NOTE: Webmail largely depends on cookies. A "one-line-cookie" patch is
15461 required for url "4.0pre.46".
15463 WARNING: Mails may be lost. NO WARRANTY.
15469 The type of the webmail server. The default is @code{hotmail}. The
15470 alternatives are @code{netscape}, @code{netaddress}, @code{my-deja}.
15473 The user name to give to the webmail server. The default is the login
15477 The password to give to the webmail server. If not specified, the user is
15481 If non-@code{nil}, only fetch unread articles and don't move them to
15482 trash folder after finishing the fetch.
15486 An example webmail source:
15489 (webmail :subtype 'hotmail
15491 :password "secret")
15495 Get the actual mail source from the @code{mail-source} group parameter,
15496 @xref{Group Parameters}.
15501 @item Common Keywords
15502 Common keywords can be used in any type of mail source.
15508 If non-@code{nil}, fetch the mail even when Gnus is unplugged. If you
15509 use directory source to get mail, you can specify it as in this
15514 '((directory :path "/home/pavel/.Spool/"
15519 Gnus will then fetch your mail even when you are unplugged. This is
15520 useful when you use local mail and news.
15525 @subsubsection Function Interface
15527 Some of the above keywords specify a Lisp function to be executed.
15528 For each keyword @code{:foo}, the Lisp variable @code{foo} is bound to
15529 the value of the keyword while the function is executing. For example,
15530 consider the following mail-source setting:
15533 (setq mail-sources '((pop :user "jrl"
15534 :server "pophost" :function fetchfunc)))
15537 While the function @code{fetchfunc} is executing, the symbol @code{user}
15538 is bound to @code{"jrl"}, and the symbol @code{server} is bound to
15539 @code{"pophost"}. The symbols @code{port}, @code{password},
15540 @code{program}, @code{prescript}, @code{postscript}, @code{function},
15541 and @code{authentication} are also bound (to their default values).
15543 See above for a list of keywords for each type of mail source.
15546 @node Mail Source Customization
15547 @subsubsection Mail Source Customization
15549 The following is a list of variables that influence how the mail is
15550 fetched. You would normally not need to set or change any of these
15554 @item mail-source-crash-box
15555 @vindex mail-source-crash-box
15556 File where mail will be stored while processing it. The default is@*
15557 @file{~/.emacs-mail-crash-box}.
15560 @item mail-source-delete-incoming
15561 @vindex mail-source-delete-incoming
15562 If non-@code{nil}, delete incoming files after handling them. If
15563 @code{t}, delete the files immediately, if @code{nil}, never delete any
15564 files. If a positive number, delete files older than number of days
15565 (the deletion will only happen when receiving new mail). You may also
15566 set @code{mail-source-delete-incoming} to @code{nil} and call
15567 @code{mail-source-delete-old-incoming} from a hook or interactively.
15568 @code{mail-source-delete-incoming} defaults to @code{10} in alpha Gnusae
15569 and @code{2} in released Gnusae. @xref{Gnus Development}.
15571 @item mail-source-delete-old-incoming-confirm
15572 @vindex mail-source-delete-old-incoming-confirm
15573 If non-@code{nil}, ask for confirmation before deleting old incoming
15574 files. This variable only applies when
15575 @code{mail-source-delete-incoming} is a positive number.
15577 @item mail-source-ignore-errors
15578 @vindex mail-source-ignore-errors
15579 If non-@code{nil}, ignore errors when reading mail from a mail source.
15581 @item mail-source-directory
15582 @vindex mail-source-directory
15583 Directory where incoming mail source files (if any) will be stored. The
15584 default is @file{~/Mail/}. At present, the only thing this is used for
15585 is to say where the incoming files will be stored if the variable
15586 @code{mail-source-delete-incoming} is @code{nil} or a number.
15588 @item mail-source-incoming-file-prefix
15589 @vindex mail-source-incoming-file-prefix
15590 Prefix for file name for storing incoming mail. The default is
15591 @file{Incoming}, in which case files will end up with names like
15592 @file{Incoming30630D_} or @file{Incoming298602ZD}. This is really only
15593 relevant if @code{mail-source-delete-incoming} is @code{nil} or a
15596 @item mail-source-default-file-modes
15597 @vindex mail-source-default-file-modes
15598 All new mail files will get this file mode. The default is 384.
15600 @item mail-source-movemail-program
15601 @vindex mail-source-movemail-program
15602 If non-@code{nil}, name of program for fetching new mail. If
15603 @code{nil}, @code{movemail} in @var{exec-directory}.
15608 @node Fetching Mail
15609 @subsubsection Fetching Mail
15611 @vindex mail-sources
15612 The way to actually tell Gnus where to get new mail from is to set
15613 @code{mail-sources} to a list of mail source specifiers
15614 (@pxref{Mail Source Specifiers}).
15616 If this variable is @code{nil}, the mail back ends will never attempt to
15617 fetch mail by themselves.
15619 If you want to fetch mail both from your local spool as well as a
15620 @acronym{POP} mail server, you'd say something like:
15625 (pop :server "pop3.mail.server"
15626 :password "secret")))
15629 Or, if you don't want to use any of the keyword defaults:
15633 '((file :path "/var/spool/mail/user-name")
15634 (pop :server "pop3.mail.server"
15637 :password "secret")))
15641 When you use a mail back end, Gnus will slurp all your mail from your
15642 inbox and plonk it down in your home directory. Gnus doesn't move any
15643 mail if you're not using a mail back end---you have to do a lot of magic
15644 invocations first. At the time when you have finished drawing the
15645 pentagram, lightened the candles, and sacrificed the goat, you really
15646 shouldn't be too surprised when Gnus moves your mail.
15650 @node Mail Back End Variables
15651 @subsection Mail Back End Variables
15653 These variables are (for the most part) pertinent to all the various
15657 @vindex nnmail-read-incoming-hook
15658 @item nnmail-read-incoming-hook
15659 The mail back ends all call this hook after reading new mail. You can
15660 use this hook to notify any mail watch programs, if you want to.
15662 @vindex nnmail-split-hook
15663 @item nnmail-split-hook
15664 @findex gnus-article-decode-encoded-words
15665 @cindex RFC 1522 decoding
15666 @cindex RFC 2047 decoding
15667 Hook run in the buffer where the mail headers of each message is kept
15668 just before the splitting based on these headers is done. The hook is
15669 free to modify the buffer contents in any way it sees fit---the buffer
15670 is discarded after the splitting has been done, and no changes performed
15671 in the buffer will show up in any files.
15672 @code{gnus-article-decode-encoded-words} is one likely function to add
15675 @vindex nnmail-pre-get-new-mail-hook
15676 @vindex nnmail-post-get-new-mail-hook
15677 @item nnmail-pre-get-new-mail-hook
15678 @itemx nnmail-post-get-new-mail-hook
15679 These are two useful hooks executed when treating new incoming
15680 mail---@code{nnmail-pre-get-new-mail-hook} (is called just before
15681 starting to handle the new mail) and
15682 @code{nnmail-post-get-new-mail-hook} (is called when the mail handling
15683 is done). Here's and example of using these two hooks to change the
15684 default file modes the new mail files get:
15687 (add-hook 'nnmail-pre-get-new-mail-hook
15688 (lambda () (set-default-file-modes 511)))
15690 (add-hook 'nnmail-post-get-new-mail-hook
15691 (lambda () (set-default-file-modes 551)))
15694 @item nnmail-use-long-file-names
15695 @vindex nnmail-use-long-file-names
15696 If non-@code{nil}, the mail back ends will use long file and directory
15697 names. Groups like @samp{mail.misc} will end up in directories
15698 (assuming use of @code{nnml} back end) or files (assuming use of
15699 @code{nnfolder} back end) like @file{mail.misc}. If it is @code{nil},
15700 the same group will end up in @file{mail/misc}.
15702 @item nnmail-delete-file-function
15703 @vindex nnmail-delete-file-function
15704 @findex delete-file
15705 Function called to delete files. It is @code{delete-file} by default.
15707 @item nnmail-cache-accepted-message-ids
15708 @vindex nnmail-cache-accepted-message-ids
15709 If non-@code{nil}, put the @code{Message-ID}s of articles imported into
15710 the back end (via @code{Gcc}, for instance) into the mail duplication
15711 discovery cache. The default is @code{nil}.
15713 @item nnmail-cache-ignore-groups
15714 @vindex nnmail-cache-ignore-groups
15715 This can be a regular expression or a list of regular expressions.
15716 Group names that match any of the regular expressions will never be
15717 recorded in the @code{Message-ID} cache.
15719 This can be useful, for example, when using Fancy Splitting
15720 (@pxref{Fancy Mail Splitting}) together with the function
15721 @code{nnmail-split-fancy-with-parent}.
15726 @node Fancy Mail Splitting
15727 @subsection Fancy Mail Splitting
15728 @cindex mail splitting
15729 @cindex fancy mail splitting
15731 @vindex nnmail-split-fancy
15732 @findex nnmail-split-fancy
15733 If the rather simple, standard method for specifying how to split mail
15734 doesn't allow you to do what you want, you can set
15735 @code{nnmail-split-methods} to @code{nnmail-split-fancy}. Then you can
15736 play with the @code{nnmail-split-fancy} variable.
15738 Let's look at an example value of this variable first:
15741 ;; @r{Messages from the mailer daemon are not crossposted to any of}
15742 ;; @r{the ordinary groups. Warnings are put in a separate group}
15743 ;; @r{from real errors.}
15744 (| ("from" mail (| ("subject" "warn.*" "mail.warning")
15746 ;; @r{Non-error messages are crossposted to all relevant}
15747 ;; @r{groups, but we don't crosspost between the group for the}
15748 ;; @r{(ding) list and the group for other (ding) related mail.}
15749 (& (| (any "ding@@ifi\\.uio\\.no" "ding.list")
15750 ("subject" "ding" "ding.misc"))
15751 ;; @r{Other mailing lists@dots{}}
15752 (any "procmail@@informatik\\.rwth-aachen\\.de" "procmail.list")
15753 (any "SmartList@@informatik\\.rwth-aachen\\.de" "SmartList.list")
15754 ;; @r{Both lists below have the same suffix, so prevent}
15755 ;; @r{cross-posting to mkpkg.list of messages posted only to}
15756 ;; @r{the bugs- list, but allow cross-posting when the}
15757 ;; @r{message was really cross-posted.}
15758 (any "bugs-mypackage@@somewhere" "mypkg.bugs")
15759 (any "mypackage@@somewhere" - "bugs-mypackage" "mypkg.list")
15760 ;; @r{People@dots{}}
15761 (any "larsi@@ifi\\.uio\\.no" "people.Lars_Magne_Ingebrigtsen"))
15762 ;; @r{Unmatched mail goes to the catch all group.}
15766 This variable has the format of a @dfn{split}. A split is a
15767 (possibly) recursive structure where each split may contain other
15768 splits. Here are the possible split syntaxes:
15773 If the split is a string, that will be taken as a group name. Normal
15774 regexp match expansion will be done. See below for examples.
15776 @c Don't fold this line.
15777 @item (@var{field} @var{value} [- @var{restrict} [@dots{}] ] @var{split} [@var{invert-partial}])
15778 The split can be a list containing at least three elements. If the
15779 first element @var{field} (a regexp matching a header) contains
15780 @var{value} (also a regexp) then store the message as specified by
15783 If @var{restrict} (yet another regexp) matches some string after
15784 @var{field} and before the end of the matched @var{value}, the
15785 @var{split} is ignored. If none of the @var{restrict} clauses match,
15786 @var{split} is processed.
15788 The last element @var{invert-partial} is optional. If it is
15789 non-@code{nil}, the match-partial-words behavior controlled by the
15790 variable @code{nnmail-split-fancy-match-partial-words} (see below) is
15791 be inverted. (New in Gnus 5.10.7)
15793 @item (| @var{split} @dots{})
15794 If the split is a list, and the first element is @code{|} (vertical
15795 bar), then process each @var{split} until one of them matches. A
15796 @var{split} is said to match if it will cause the mail message to be
15797 stored in one or more groups.
15799 @item (& @var{split} @dots{})
15800 If the split is a list, and the first element is @code{&}, then
15801 process all @var{split}s in the list.
15804 If the split is the symbol @code{junk}, then don't save (i.e., delete)
15805 this message. Use with extreme caution.
15807 @item (: @var{function} @var{arg1} @var{arg2} @dots{})
15808 If the split is a list, and the first element is @samp{:}, then the
15809 second element will be called as a function with @var{args} given as
15810 arguments. The function should return a @var{split}.
15813 For instance, the following function could be used to split based on the
15814 body of the messages:
15817 (defun split-on-body ()
15821 (goto-char (point-min))
15822 (when (re-search-forward "Some.*string" nil t)
15826 The buffer is narrowed to the header of the message in question when
15827 @var{function} is run. That's why @code{(widen)} needs to be called
15828 after @code{save-excursion} and @code{save-restriction} in the example
15829 above. Also note that with the nnimap backend, message bodies will
15830 not be downloaded by default. You need to set
15831 @code{nnimap-split-download-body} to @code{t} to do that
15832 (@pxref{Splitting in IMAP}).
15834 @item (! @var{func} @var{split})
15835 If the split is a list, and the first element is @code{!}, then
15836 @var{split} will be processed, and @var{func} will be called as a
15837 function with the result of @var{split} as argument. @var{func}
15838 should return a split.
15841 If the split is @code{nil}, it is ignored.
15845 In these splits, @var{field} must match a complete field name.
15847 Normally, @var{value} in these splits must match a complete @emph{word}
15848 according to the fundamental mode syntax table. In other words, all
15849 @var{value}'s will be implicitly surrounded by @code{\<...\>} markers,
15850 which are word delimiters. Therefore, if you use the following split,
15854 (any "joe" "joemail")
15858 messages sent from @samp{joedavis@@foo.org} will normally not be filed
15859 in @samp{joemail}. If you want to alter this behavior, you can use any
15860 of the following three ways:
15864 @vindex nnmail-split-fancy-match-partial-words
15865 You can set the @code{nnmail-split-fancy-match-partial-words} variable
15866 to non-@code{nil} in order to ignore word boundaries and instead the
15867 match becomes more like a grep. This variable controls whether partial
15868 words are matched during fancy splitting. The default value is
15871 Note that it influences all @var{value}'s in your split rules.
15874 @var{value} beginning with @code{.*} ignores word boundaries in front of
15875 a word. Similarly, if @var{value} ends with @code{.*}, word boundaries
15876 in the rear of a word will be ignored. For example, the @var{value}
15877 @code{"@@example\\.com"} does not match @samp{foo@@example.com} but
15878 @code{".*@@example\\.com"} does.
15881 You can set the @var{invert-partial} flag in your split rules of the
15882 @samp{(@var{field} @var{value} @dots{})} types, aforementioned in this
15883 section. If the flag is set, word boundaries on both sides of a word
15884 are ignored even if @code{nnmail-split-fancy-match-partial-words} is
15885 @code{nil}. Contrarily, if the flag is set, word boundaries are not
15886 ignored even if @code{nnmail-split-fancy-match-partial-words} is
15887 non-@code{nil}. (New in Gnus 5.10.7)
15890 @vindex nnmail-split-abbrev-alist
15891 @var{field} and @var{value} can also be Lisp symbols, in that case
15892 they are expanded as specified by the variable
15893 @code{nnmail-split-abbrev-alist}. This is an alist of cons cells,
15894 where the @sc{car} of a cell contains the key, and the @sc{cdr}
15895 contains the associated value. Predefined entries in
15896 @code{nnmail-split-abbrev-alist} include:
15900 Matches the @samp{From}, @samp{Sender} and @samp{Resent-From} fields.
15902 Matches the @samp{To}, @samp{Cc}, @samp{Apparently-To},
15903 @samp{Resent-To} and @samp{Resent-Cc} fields.
15905 Is the union of the @code{from} and @code{to} entries.
15908 @vindex nnmail-split-fancy-syntax-table
15909 @code{nnmail-split-fancy-syntax-table} is the syntax table in effect
15910 when all this splitting is performed.
15912 If you want to have Gnus create groups dynamically based on some
15913 information in the headers (i.e., do @code{replace-match}-like
15914 substitutions in the group names), you can say things like:
15917 (any "debian-\\b\\(\\w+\\)@@lists.debian.org" "mail.debian.\\1")
15920 In this example, messages sent to @samp{debian-foo@@lists.debian.org}
15921 will be filed in @samp{mail.debian.foo}.
15923 If the string contains the element @samp{\&}, then the previously
15924 matched string will be substituted. Similarly, the elements @samp{\\1}
15925 up to @samp{\\9} will be substituted with the text matched by the
15926 groupings 1 through 9.
15928 @vindex nnmail-split-lowercase-expanded
15929 Where @code{nnmail-split-lowercase-expanded} controls whether the
15930 lowercase of the matched string should be used for the substitution.
15931 Setting it as non-@code{nil} is useful to avoid the creation of multiple
15932 groups when users send to an address using different case
15933 (i.e. mailing-list@@domain vs Mailing-List@@Domain). The default value
15936 @findex nnmail-split-fancy-with-parent
15937 @code{nnmail-split-fancy-with-parent} is a function which allows you to
15938 split followups into the same groups their parents are in. Sometimes
15939 you can't make splitting rules for all your mail. For example, your
15940 boss might send you personal mail regarding different projects you are
15941 working on, and as you can't tell your boss to put a distinguishing
15942 string into the subject line, you have to resort to manually moving the
15943 messages into the right group. With this function, you only have to do
15944 it once per thread.
15946 To use this feature, you have to set @code{nnmail-treat-duplicates}
15947 and @code{nnmail-cache-accepted-message-ids} to a non-@code{nil}
15948 value. And then you can include @code{nnmail-split-fancy-with-parent}
15949 using the colon feature, like so:
15951 (setq nnmail-treat-duplicates 'warn ; @r{or @code{delete}}
15952 nnmail-cache-accepted-message-ids t
15954 '(| (: nnmail-split-fancy-with-parent)
15955 ;; @r{other splits go here}
15959 This feature works as follows: when @code{nnmail-treat-duplicates} is
15960 non-@code{nil}, Gnus records the message id of every message it sees
15961 in the file specified by the variable
15962 @code{nnmail-message-id-cache-file}, together with the group it is in
15963 (the group is omitted for non-mail messages). When mail splitting is
15964 invoked, the function @code{nnmail-split-fancy-with-parent} then looks
15965 at the References (and In-Reply-To) header of each message to split
15966 and searches the file specified by @code{nnmail-message-id-cache-file}
15967 for the message ids. When it has found a parent, it returns the
15968 corresponding group name unless the group name matches the regexp
15969 @code{nnmail-split-fancy-with-parent-ignore-groups}. It is
15970 recommended that you set @code{nnmail-message-id-cache-length} to a
15971 somewhat higher number than the default so that the message ids are
15972 still in the cache. (A value of 5000 appears to create a file some
15973 300 kBytes in size.)
15974 @vindex nnmail-cache-accepted-message-ids
15975 When @code{nnmail-cache-accepted-message-ids} is non-@code{nil}, Gnus
15976 also records the message ids of moved articles, so that the followup
15977 messages goes into the new group.
15979 Also see the variable @code{nnmail-cache-ignore-groups} if you don't
15980 want certain groups to be recorded in the cache. For example, if all
15981 outgoing messages are written to an ``outgoing'' group, you could set
15982 @code{nnmail-cache-ignore-groups} to match that group name.
15983 Otherwise, answers to all your messages would end up in the
15984 ``outgoing'' group.
15987 @node Group Mail Splitting
15988 @subsection Group Mail Splitting
15989 @cindex mail splitting
15990 @cindex group mail splitting
15992 @findex gnus-group-split
15993 If you subscribe to dozens of mailing lists but you don't want to
15994 maintain mail splitting rules manually, group mail splitting is for you.
15995 You just have to set @code{to-list} and/or @code{to-address} in group
15996 parameters or group customization and set @code{nnmail-split-methods} to
15997 @code{gnus-group-split}. This splitting function will scan all groups
15998 for those parameters and split mail accordingly, i.e., messages posted
15999 from or to the addresses specified in the parameters @code{to-list} or
16000 @code{to-address} of a mail group will be stored in that group.
16002 Sometimes, mailing lists have multiple addresses, and you may want mail
16003 splitting to recognize them all: just set the @code{extra-aliases} group
16004 parameter to the list of additional addresses and it's done. If you'd
16005 rather use a regular expression, set @code{split-regexp}.
16007 All these parameters in a group will be used to create an
16008 @code{nnmail-split-fancy} split, in which the @var{field} is @samp{any},
16009 the @var{value} is a single regular expression that matches
16010 @code{to-list}, @code{to-address}, all of @code{extra-aliases} and all
16011 matches of @code{split-regexp}, and the @var{split} is the name of the
16012 group. @var{restrict}s are also supported: just set the
16013 @code{split-exclude} parameter to a list of regular expressions.
16015 If you can't get the right split to be generated using all these
16016 parameters, or you just need something fancier, you can set the
16017 parameter @code{split-spec} to an @code{nnmail-split-fancy} split. In
16018 this case, all other aforementioned parameters will be ignored by
16019 @code{gnus-group-split}. In particular, @code{split-spec} may be set to
16020 @code{nil}, in which case the group will be ignored by
16021 @code{gnus-group-split}.
16023 @vindex gnus-group-split-default-catch-all-group
16024 @code{gnus-group-split} will do cross-posting on all groups that match,
16025 by defining a single @code{&} fancy split containing one split for each
16026 group. If a message doesn't match any split, it will be stored in the
16027 group named in @code{gnus-group-split-default-catch-all-group}, unless
16028 some group has @code{split-spec} set to @code{catch-all}, in which case
16029 that group is used as the catch-all group. Even though this variable is
16030 often used just to name a group, it may also be set to an arbitrarily
16031 complex fancy split (after all, a group name is a fancy split), and this
16032 may be useful to split mail that doesn't go to any mailing list to
16033 personal mail folders. Note that this fancy split is added as the last
16034 element of a @code{|} split list that also contains a @code{&} split
16035 with the rules extracted from group parameters.
16037 It's time for an example. Assume the following group parameters have
16042 ((to-address . "bar@@femail.com")
16043 (split-regexp . ".*@@femail\\.com"))
16045 ((to-list . "foo@@nowhere.gov")
16046 (extra-aliases "foo@@localhost" "foo-redist@@home")
16047 (split-exclude "bugs-foo" "rambling-foo")
16048 (admin-address . "foo-request@@nowhere.gov"))
16050 ((split-spec . catch-all))
16053 Setting @code{nnmail-split-methods} to @code{gnus-group-split} will
16054 behave as if @code{nnmail-split-fancy} had been selected and variable
16055 @code{nnmail-split-fancy} had been set as follows:
16058 (| (& (any "\\(bar@@femail\\.com\\|.*@@femail\\.com\\)" "mail.bar")
16059 (any "\\(foo@@nowhere\\.gov\\|foo@@localhost\\|foo-redist@@home\\)"
16060 - "bugs-foo" - "rambling-foo" "mail.foo"))
16064 @findex gnus-group-split-fancy
16065 If you'd rather not use group splitting for all your mail groups, you
16066 may use it for only some of them, by using @code{nnmail-split-fancy}
16070 (: gnus-group-split-fancy @var{groups} @var{no-crosspost} @var{catch-all})
16073 @var{groups} may be a regular expression or a list of group names whose
16074 parameters will be scanned to generate the output split.
16075 @var{no-crosspost} can be used to disable cross-posting; in this case, a
16076 single @code{|} split will be output. @var{catch-all} is the fall back
16077 fancy split, used like @code{gnus-group-split-default-catch-all-group}.
16078 If @var{catch-all} is @code{nil}, or if @code{split-regexp} matches the
16079 empty string in any selected group, no catch-all split will be issued.
16080 Otherwise, if some group has @code{split-spec} set to @code{catch-all},
16081 this group will override the value of the @var{catch-all} argument.
16083 @findex gnus-group-split-setup
16084 Unfortunately, scanning all groups and their parameters can be quite
16085 slow, especially considering that it has to be done for every message.
16086 But don't despair! The function @code{gnus-group-split-setup} can be
16087 used to enable @code{gnus-group-split} in a much more efficient way. It
16088 sets @code{nnmail-split-methods} to @code{nnmail-split-fancy} and sets
16089 @code{nnmail-split-fancy} to the split produced by
16090 @code{gnus-group-split-fancy}. Thus, the group parameters are only
16091 scanned once, no matter how many messages are split.
16093 @findex gnus-group-split-update
16094 However, if you change group parameters, you'd have to update
16095 @code{nnmail-split-fancy} manually. You can do it by running
16096 @code{gnus-group-split-update}. If you'd rather have it updated
16097 automatically, just tell @code{gnus-group-split-setup} to do it for
16098 you. For example, add to your @file{~/.gnus.el}:
16101 (gnus-group-split-setup @var{auto-update} @var{catch-all})
16104 If @var{auto-update} is non-@code{nil}, @code{gnus-group-split-update}
16105 will be added to @code{nnmail-pre-get-new-mail-hook}, so you won't ever
16106 have to worry about updating @code{nnmail-split-fancy} again. If you
16107 don't omit @var{catch-all} (it's optional, equivalent to @code{nil}),
16108 @code{gnus-group-split-default-catch-all-group} will be set to its
16111 @vindex gnus-group-split-updated-hook
16112 Because you may want to change @code{nnmail-split-fancy} after it is set
16113 by @code{gnus-group-split-update}, this function will run
16114 @code{gnus-group-split-updated-hook} just before finishing.
16116 @node Incorporating Old Mail
16117 @subsection Incorporating Old Mail
16118 @cindex incorporating old mail
16119 @cindex import old mail
16121 Most people have lots of old mail stored in various file formats. If
16122 you have set up Gnus to read mail using one of the spiffy Gnus mail
16123 back ends, you'll probably wish to have that old mail incorporated into
16126 Doing so can be quite easy.
16128 To take an example: You're reading mail using @code{nnml}
16129 (@pxref{Mail Spool}), and have set @code{nnmail-split-methods} to a
16130 satisfactory value (@pxref{Splitting Mail}). You have an old Unix mbox
16131 file filled with important, but old, mail. You want to move it into
16132 your @code{nnml} groups.
16138 Go to the group buffer.
16141 Type @kbd{G f} and give the file name to the mbox file when prompted to create an
16142 @code{nndoc} group from the mbox file (@pxref{Foreign Groups}).
16145 Type @kbd{SPACE} to enter the newly created group.
16148 Type @kbd{M P b} to process-mark all articles in this group's buffer
16149 (@pxref{Setting Process Marks}).
16152 Type @kbd{B r} to respool all the process-marked articles, and answer
16153 @samp{nnml} when prompted (@pxref{Mail Group Commands}).
16156 All the mail messages in the mbox file will now also be spread out over
16157 all your @code{nnml} groups. Try entering them and check whether things
16158 have gone without a glitch. If things look ok, you may consider
16159 deleting the mbox file, but I wouldn't do that unless I was absolutely
16160 sure that all the mail has ended up where it should be.
16162 Respooling is also a handy thing to do if you're switching from one mail
16163 back end to another. Just respool all the mail in the old mail groups
16164 using the new mail back end.
16167 @node Expiring Mail
16168 @subsection Expiring Mail
16169 @cindex article expiry
16170 @cindex expiring mail
16172 Traditional mail readers have a tendency to remove mail articles when
16173 you mark them as read, in some way. Gnus takes a fundamentally
16174 different approach to mail reading.
16176 Gnus basically considers mail just to be news that has been received in
16177 a rather peculiar manner. It does not think that it has the power to
16178 actually change the mail, or delete any mail messages. If you enter a
16179 mail group, and mark articles as ``read'', or kill them in some other
16180 fashion, the mail articles will still exist on the system. I repeat:
16181 Gnus will not delete your old, read mail. Unless you ask it to, of
16184 To make Gnus get rid of your unwanted mail, you have to mark the
16185 articles as @dfn{expirable}. (With the default key bindings, this means
16186 that you have to type @kbd{E}.) This does not mean that the articles
16187 will disappear right away, however. In general, a mail article will be
16188 deleted from your system if, 1) it is marked as expirable, AND 2) it is
16189 more than one week old. If you do not mark an article as expirable, it
16190 will remain on your system until hell freezes over. This bears
16191 repeating one more time, with some spurious capitalizations: IF you do
16192 NOT mark articles as EXPIRABLE, Gnus will NEVER delete those ARTICLES.
16194 You do not have to mark articles as expirable by hand. Gnus provides
16195 two features, called ``auto-expire'' and ``total-expire'', that can help you
16196 with this. In a nutshell, ``auto-expire'' means that Gnus hits @kbd{E}
16197 for you when you select an article. And ``total-expire'' means that Gnus
16198 considers all articles as expirable that are read. So, in addition to
16199 the articles marked @samp{E}, also the articles marked @samp{r},
16200 @samp{R}, @samp{O}, @samp{K}, @samp{Y} and so on are considered
16203 When should either auto-expire or total-expire be used? Most people
16204 who are subscribed to mailing lists split each list into its own group
16205 and then turn on auto-expire or total-expire for those groups.
16206 (@xref{Splitting Mail}, for more information on splitting each list
16207 into its own group.)
16209 Which one is better, auto-expire or total-expire? It's not easy to
16210 answer. Generally speaking, auto-expire is probably faster. Another
16211 advantage of auto-expire is that you get more marks to work with: for
16212 the articles that are supposed to stick around, you can still choose
16213 between tick and dormant and read marks. But with total-expire, you
16214 only have dormant and ticked to choose from. The advantage of
16215 total-expire is that it works well with adaptive scoring (@pxref{Adaptive
16216 Scoring}). Auto-expire works with normal scoring but not with adaptive
16219 @vindex gnus-auto-expirable-newsgroups
16220 Groups that match the regular expression
16221 @code{gnus-auto-expirable-newsgroups} will have all articles that you
16222 read marked as expirable automatically. All articles marked as
16223 expirable have an @samp{E} in the first column in the summary buffer.
16225 By default, if you have auto expiry switched on, Gnus will mark all the
16226 articles you read as expirable, no matter if they were read or unread
16227 before. To avoid having articles marked as read marked as expirable
16228 automatically, you can put something like the following in your
16229 @file{~/.gnus.el} file:
16231 @vindex gnus-mark-article-hook
16233 (remove-hook 'gnus-mark-article-hook
16234 'gnus-summary-mark-read-and-unread-as-read)
16235 (add-hook 'gnus-mark-article-hook 'gnus-summary-mark-unread-as-read)
16238 Note that making a group auto-expirable doesn't mean that all read
16239 articles are expired---only the articles marked as expirable
16240 will be expired. Also note that using the @kbd{d} command won't make
16241 articles expirable---only semi-automatic marking of articles as read will
16242 mark the articles as expirable in auto-expirable groups.
16244 Let's say you subscribe to a couple of mailing lists, and you want the
16245 articles you have read to disappear after a while:
16248 (setq gnus-auto-expirable-newsgroups
16249 "mail.nonsense-list\\|mail.nice-list")
16252 Another way to have auto-expiry happen is to have the element
16253 @code{auto-expire} in the group parameters of the group.
16255 If you use adaptive scoring (@pxref{Adaptive Scoring}) and
16256 auto-expiring, you'll have problems. Auto-expiring and adaptive scoring
16257 don't really mix very well.
16259 @vindex nnmail-expiry-wait
16260 The @code{nnmail-expiry-wait} variable supplies the default time an
16261 expirable article has to live. Gnus starts counting days from when the
16262 message @emph{arrived}, not from when it was sent. The default is seven
16265 Gnus also supplies a function that lets you fine-tune how long articles
16266 are to live, based on what group they are in. Let's say you want to
16267 have one month expiry period in the @samp{mail.private} group, a one day
16268 expiry period in the @samp{mail.junk} group, and a six day expiry period
16271 @vindex nnmail-expiry-wait-function
16273 (setq nnmail-expiry-wait-function
16275 (cond ((string= group "mail.private")
16277 ((string= group "mail.junk")
16279 ((string= group "important")
16285 The group names this function is fed are ``unadorned'' group
16286 names---no @samp{nnml:} prefixes and the like.
16288 The @code{nnmail-expiry-wait} variable and
16289 @code{nnmail-expiry-wait-function} function can either be a number (not
16290 necessarily an integer) or one of the symbols @code{immediate} or
16293 You can also use the @code{expiry-wait} group parameter to selectively
16294 change the expiry period (@pxref{Group Parameters}).
16296 @vindex nnmail-expiry-target
16297 The normal action taken when expiring articles is to delete them.
16298 However, in some circumstances it might make more sense to move them
16299 to other groups instead of deleting them. The variable
16300 @code{nnmail-expiry-target} (and the @code{expiry-target} group
16301 parameter) controls this. The variable supplies a default value for
16302 all groups, which can be overridden for specific groups by the group
16303 parameter. default value is @code{delete}, but this can also be a
16304 string (which should be the name of the group the message should be
16305 moved to), or a function (which will be called in a buffer narrowed to
16306 the message in question, and with the name of the group being moved
16307 from as its parameter) which should return a target---either a group
16308 name or @code{delete}.
16310 Here's an example for specifying a group name:
16312 (setq nnmail-expiry-target "nnml:expired")
16315 @findex nnmail-fancy-expiry-target
16316 @vindex nnmail-fancy-expiry-targets
16317 Gnus provides a function @code{nnmail-fancy-expiry-target} which will
16318 expire mail to groups according to the variable
16319 @code{nnmail-fancy-expiry-targets}. Here's an example:
16322 (setq nnmail-expiry-target 'nnmail-fancy-expiry-target
16323 nnmail-fancy-expiry-targets
16324 '((to-from "boss" "nnfolder:Work")
16325 ("subject" "IMPORTANT" "nnfolder:IMPORTANT.%Y.%b")
16326 ("from" ".*" "nnfolder:Archive-%Y")))
16329 With this setup, any mail that has @code{IMPORTANT} in its Subject
16330 header and was sent in the year @code{YYYY} and month @code{MMM}, will
16331 get expired to the group @code{nnfolder:IMPORTANT.YYYY.MMM}. If its
16332 From or To header contains the string @code{boss}, it will get expired
16333 to @code{nnfolder:Work}. All other mail will get expired to
16334 @code{nnfolder:Archive-YYYY}.
16336 @vindex nnmail-keep-last-article
16337 If @code{nnmail-keep-last-article} is non-@code{nil}, Gnus will never
16338 expire the final article in a mail newsgroup. This is to make life
16339 easier for procmail users.
16341 @vindex gnus-total-expirable-newsgroups
16342 By the way: That line up there, about Gnus never expiring non-expirable
16343 articles, is a lie. If you put @code{total-expire} in the group
16344 parameters, articles will not be marked as expirable, but all read
16345 articles will be put through the expiry process. Use with extreme
16346 caution. Even more dangerous is the
16347 @code{gnus-total-expirable-newsgroups} variable. All groups that match
16348 this regexp will have all read articles put through the expiry process,
16349 which means that @emph{all} old mail articles in the groups in question
16350 will be deleted after a while. Use with extreme caution, and don't come
16351 crying to me when you discover that the regexp you used matched the
16352 wrong group and all your important mail has disappeared. Be a
16353 @emph{man}! Or a @emph{woman}! Whatever you feel more comfortable
16356 Most people make most of their mail groups total-expirable, though.
16358 @vindex gnus-inhibit-user-auto-expire
16359 If @code{gnus-inhibit-user-auto-expire} is non-@code{nil}, user marking
16360 commands will not mark an article as expirable, even if the group has
16361 auto-expire turned on.
16363 @vindex gnus-mark-copied-or-moved-articles-as-expirable
16364 The expirable marks of articles will be removed when copying or moving
16365 them to a group in which auto-expire is not turned on. This is for
16366 preventing articles from being expired unintentionally. On the other
16367 hand, to a group that has turned auto-expire on, the expirable marks of
16368 articles that are copied or moved will not be changed by default. I.e.,
16369 when copying or moving to such a group, articles that were expirable
16370 will be left expirable and ones that were not expirable will not be
16371 marked as expirable. So, even though in auto-expire groups, some
16372 articles will never get expired (unless you read them again). If you
16373 don't side with that behavior that unexpirable articles may be mixed
16374 into auto-expire groups, you can set
16375 @code{gnus-mark-copied-or-moved-articles-as-expirable} to a
16376 non-@code{nil} value. In that case, articles that have been read will
16377 be marked as expirable automatically when being copied or moved to a
16378 group that has auto-expire turned on. The default value is @code{nil}.
16382 @subsection Washing Mail
16383 @cindex mail washing
16384 @cindex list server brain damage
16385 @cindex incoming mail treatment
16387 Mailers and list servers are notorious for doing all sorts of really,
16388 really stupid things with mail. ``Hey, RFC 822 doesn't explicitly
16389 prohibit us from adding the string @code{wE aRe ElItE!!!!!1!!} to the
16390 end of all lines passing through our server, so let's do that!!!!1!''
16391 Yes, but RFC 822 wasn't designed to be read by morons. Things that were
16392 considered to be self-evident were not discussed. So. Here we are.
16394 Case in point: The German version of Microsoft Exchange adds @samp{AW:
16395 } to the subjects of replies instead of @samp{Re: }. I could pretend to
16396 be shocked and dismayed by this, but I haven't got the energy. It is to
16399 Gnus provides a plethora of functions for washing articles while
16400 displaying them, but it might be nicer to do the filtering before
16401 storing the mail to disk. For that purpose, we have three hooks and
16402 various functions that can be put in these hooks.
16405 @item nnmail-prepare-incoming-hook
16406 @vindex nnmail-prepare-incoming-hook
16407 This hook is called before doing anything with the mail and is meant for
16408 grand, sweeping gestures. It is called in a buffer that contains all
16409 the new, incoming mail. Functions to be used include:
16412 @item nnheader-ms-strip-cr
16413 @findex nnheader-ms-strip-cr
16414 Remove trailing carriage returns from each line. This is default on
16415 Emacs running on MS machines.
16419 @item nnmail-prepare-incoming-header-hook
16420 @vindex nnmail-prepare-incoming-header-hook
16421 This hook is called narrowed to each header. It can be used when
16422 cleaning up the headers. Functions that can be used include:
16425 @item nnmail-remove-leading-whitespace
16426 @findex nnmail-remove-leading-whitespace
16427 Clear leading white space that ``helpful'' listservs have added to the
16428 headers to make them look nice. Aaah.
16430 (Note that this function works on both the header on the body of all
16431 messages, so it is a potentially dangerous function to use (if a body
16432 of a message contains something that looks like a header line). So
16433 rather than fix the bug, it is of course the right solution to make it
16434 into a feature by documenting it.)
16436 @item nnmail-remove-list-identifiers
16437 @findex nnmail-remove-list-identifiers
16438 Some list servers add an identifier---for example, @samp{(idm)}---to the
16439 beginning of all @code{Subject} headers. I'm sure that's nice for
16440 people who use stone age mail readers. This function will remove
16441 strings that match the @code{nnmail-list-identifiers} regexp, which can
16442 also be a list of regexp. @code{nnmail-list-identifiers} may not contain
16445 For instance, if you want to remove the @samp{(idm)} and the
16446 @samp{nagnagnag} identifiers:
16449 (setq nnmail-list-identifiers
16450 '("(idm)" "nagnagnag"))
16453 This can also be done non-destructively with
16454 @code{gnus-list-identifiers}, @xref{Article Hiding}.
16456 @item nnmail-remove-tabs
16457 @findex nnmail-remove-tabs
16458 Translate all @samp{TAB} characters into @samp{SPACE} characters.
16460 @item nnmail-ignore-broken-references
16461 @findex nnmail-ignore-broken-references
16462 @c @findex nnmail-fix-eudora-headers
16465 Some mail user agents (e.g. Eudora and Pegasus) produce broken
16466 @code{References} headers, but correct @code{In-Reply-To} headers. This
16467 function will get rid of the @code{References} header if the headers
16468 contain a line matching the regular expression
16469 @code{nnmail-broken-references-mailers}.
16473 @item nnmail-prepare-incoming-message-hook
16474 @vindex nnmail-prepare-incoming-message-hook
16475 This hook is called narrowed to each message. Functions to be used
16479 @item article-de-quoted-unreadable
16480 @findex article-de-quoted-unreadable
16481 Decode Quoted Readable encoding.
16488 @subsection Duplicates
16490 @vindex nnmail-treat-duplicates
16491 @vindex nnmail-message-id-cache-length
16492 @vindex nnmail-message-id-cache-file
16493 @cindex duplicate mails
16494 If you are a member of a couple of mailing lists, you will sometimes
16495 receive two copies of the same mail. This can be quite annoying, so
16496 @code{nnmail} checks for and treats any duplicates it might find. To do
16497 this, it keeps a cache of old @code{Message-ID}s---
16498 @code{nnmail-message-id-cache-file}, which is @file{~/.nnmail-cache} by
16499 default. The approximate maximum number of @code{Message-ID}s stored
16500 there is controlled by the @code{nnmail-message-id-cache-length}
16501 variable, which is 1000 by default. (So 1000 @code{Message-ID}s will be
16502 stored.) If all this sounds scary to you, you can set
16503 @code{nnmail-treat-duplicates} to @code{warn} (which is what it is by
16504 default), and @code{nnmail} won't delete duplicate mails. Instead it
16505 will insert a warning into the head of the mail saying that it thinks
16506 that this is a duplicate of a different message.
16508 This variable can also be a function. If that's the case, the function
16509 will be called from a buffer narrowed to the message in question with
16510 the @code{Message-ID} as a parameter. The function must return either
16511 @code{nil}, @code{warn}, or @code{delete}.
16513 You can turn this feature off completely by setting the variable to
16516 If you want all the duplicate mails to be put into a special
16517 @dfn{duplicates} group, you could do that using the normal mail split
16521 (setq nnmail-split-fancy
16522 '(| ;; @r{Messages duplicates go to a separate group.}
16523 ("gnus-warning" "duplicat\\(e\\|ion\\) of message" "duplicate")
16524 ;; @r{Message from daemons, postmaster, and the like to another.}
16525 (any mail "mail.misc")
16526 ;; @r{Other rules.}
16532 (setq nnmail-split-methods
16533 '(("duplicates" "^Gnus-Warning:.*duplicate")
16534 ;; @r{Other rules.}
16538 Here's a neat feature: If you know that the recipient reads her mail
16539 with Gnus, and that she has @code{nnmail-treat-duplicates} set to
16540 @code{delete}, you can send her as many insults as you like, just by
16541 using a @code{Message-ID} of a mail that you know that she's already
16542 received. Think of all the fun! She'll never see any of it! Whee!
16545 @node Not Reading Mail
16546 @subsection Not Reading Mail
16548 If you start using any of the mail back ends, they have the annoying
16549 habit of assuming that you want to read mail with them. This might not
16550 be unreasonable, but it might not be what you want.
16552 If you set @code{mail-sources} and @code{nnmail-spool-file} to
16553 @code{nil}, none of the back ends will ever attempt to read incoming
16554 mail, which should help.
16556 @vindex nnbabyl-get-new-mail
16557 @vindex nnmbox-get-new-mail
16558 @vindex nnml-get-new-mail
16559 @vindex nnmh-get-new-mail
16560 @vindex nnfolder-get-new-mail
16561 This might be too much, if, for instance, you are reading mail quite
16562 happily with @code{nnml} and just want to peek at some old (pre-Emacs
16563 23) Rmail file you have stashed away with @code{nnbabyl}. All back ends have
16564 variables called back-end-@code{get-new-mail}. If you want to disable
16565 the @code{nnbabyl} mail reading, you edit the virtual server for the
16566 group to have a setting where @code{nnbabyl-get-new-mail} to @code{nil}.
16568 All the mail back ends will call @code{nn}*@code{-prepare-save-mail-hook}
16569 narrowed to the article to be saved before saving it when reading
16573 @node Choosing a Mail Back End
16574 @subsection Choosing a Mail Back End
16576 Gnus will read the mail spool when you activate a mail group. The mail
16577 file is first copied to your home directory. What happens after that
16578 depends on what format you want to store your mail in.
16580 There are six different mail back ends in the standard Gnus, and more
16581 back ends are available separately. The mail back end most people use
16582 (because it is possibly the fastest) is @code{nnml} (@pxref{Mail
16586 * Unix Mail Box:: Using the (quite) standard Un*x mbox.
16587 * Babyl:: Babyl was used by older versions of Rmail.
16588 * Mail Spool:: Store your mail in a private spool?
16589 * MH Spool:: An mhspool-like back end.
16590 * Maildir:: Another one-file-per-message format.
16591 * Mail Folders:: Having one file for each group.
16592 * Comparing Mail Back Ends:: An in-depth looks at pros and cons.
16596 @node Unix Mail Box
16597 @subsubsection Unix Mail Box
16599 @cindex unix mail box
16601 @vindex nnmbox-active-file
16602 @vindex nnmbox-mbox-file
16603 The @dfn{nnmbox} back end will use the standard Un*x mbox file to store
16604 mail. @code{nnmbox} will add extra headers to each mail article to say
16605 which group it belongs in.
16607 Virtual server settings:
16610 @item nnmbox-mbox-file
16611 @vindex nnmbox-mbox-file
16612 The name of the mail box in the user's home directory. Default is
16615 @item nnmbox-active-file
16616 @vindex nnmbox-active-file
16617 The name of the active file for the mail box. Default is
16618 @file{~/.mbox-active}.
16620 @item nnmbox-get-new-mail
16621 @vindex nnmbox-get-new-mail
16622 If non-@code{nil}, @code{nnmbox} will read incoming mail and split it
16623 into groups. Default is @code{t}.
16628 @subsubsection Babyl
16631 @vindex nnbabyl-active-file
16632 @vindex nnbabyl-mbox-file
16633 The @dfn{nnbabyl} back end will use a Babyl mail box to store mail.
16634 @code{nnbabyl} will add extra headers to each mail article to say which
16635 group it belongs in.
16637 Virtual server settings:
16640 @item nnbabyl-mbox-file
16641 @vindex nnbabyl-mbox-file
16642 The name of the Babyl file. The default is @file{~/RMAIL}
16644 @item nnbabyl-active-file
16645 @vindex nnbabyl-active-file
16646 The name of the active file for the Babyl file. The default is
16647 @file{~/.rmail-active}
16649 @item nnbabyl-get-new-mail
16650 @vindex nnbabyl-get-new-mail
16651 If non-@code{nil}, @code{nnbabyl} will read incoming mail. Default is
16657 @subsubsection Mail Spool
16659 @cindex mail @acronym{NOV} spool
16661 The @dfn{nnml} spool mail format isn't compatible with any other known
16662 format. It should be used with some caution.
16664 @vindex nnml-directory
16665 If you use this back end, Gnus will split all incoming mail into files,
16666 one file for each mail, and put the articles into the corresponding
16667 directories under the directory specified by the @code{nnml-directory}
16668 variable. The default value is @file{~/Mail/}.
16670 You do not have to create any directories beforehand; Gnus will take
16673 If you have a strict limit as to how many files you are allowed to store
16674 in your account, you should not use this back end. As each mail gets its
16675 own file, you might very well occupy thousands of inodes within a few
16676 weeks. If this is no problem for you, and it isn't a problem for you
16677 having your friendly systems administrator walking around, madly,
16678 shouting ``Who is eating all my inodes?! Who? Who!?!'', then you should
16679 know that this is probably the fastest format to use. You do not have
16680 to trudge through a big mbox file just to read your new mail.
16682 @code{nnml} is probably the slowest back end when it comes to article
16683 splitting. It has to create lots of files, and it also generates
16684 @acronym{NOV} databases for the incoming mails. This makes it possibly the
16685 fastest back end when it comes to reading mail.
16687 @cindex self contained nnml servers
16689 When the marks file is used (which it is by default), @code{nnml}
16690 servers have the property that you may backup them using @code{tar} or
16691 similar, and later be able to restore them into Gnus (by adding the
16692 proper @code{nnml} server) and have all your marks be preserved. Marks
16693 for a group are usually stored in the @code{.marks} file (but see
16694 @code{nnml-marks-file-name}) within each @code{nnml} group's directory.
16695 Individual @code{nnml} groups are also possible to backup, use @kbd{G m}
16696 to restore the group (after restoring the backup into the nnml
16699 If for some reason you believe your @file{.marks} files are screwed
16700 up, you can just delete them all. Gnus will then correctly regenerate
16701 them next time it starts.
16703 Virtual server settings:
16706 @item nnml-directory
16707 @vindex nnml-directory
16708 All @code{nnml} directories will be placed under this directory. The
16709 default is the value of @code{message-directory} (whose default value
16712 @item nnml-active-file
16713 @vindex nnml-active-file
16714 The active file for the @code{nnml} server. The default is
16715 @file{~/Mail/active}.
16717 @item nnml-newsgroups-file
16718 @vindex nnml-newsgroups-file
16719 The @code{nnml} group descriptions file. @xref{Newsgroups File
16720 Format}. The default is @file{~/Mail/newsgroups}.
16722 @item nnml-get-new-mail
16723 @vindex nnml-get-new-mail
16724 If non-@code{nil}, @code{nnml} will read incoming mail. The default is
16727 @item nnml-nov-is-evil
16728 @vindex nnml-nov-is-evil
16729 If non-@code{nil}, this back end will ignore any @acronym{NOV} files. The
16730 default is @code{nil}.
16732 @item nnml-nov-file-name
16733 @vindex nnml-nov-file-name
16734 The name of the @acronym{NOV} files. The default is @file{.overview}.
16736 @item nnml-prepare-save-mail-hook
16737 @vindex nnml-prepare-save-mail-hook
16738 Hook run narrowed to an article before saving.
16740 @item nnml-marks-is-evil
16741 @vindex nnml-marks-is-evil
16742 If non-@code{nil}, this back end will ignore any @sc{marks} files. The
16743 default is @code{nil}.
16745 @item nnml-marks-file-name
16746 @vindex nnml-marks-file-name
16747 The name of the @dfn{marks} files. The default is @file{.marks}.
16749 @item nnml-use-compressed-files
16750 @vindex nnml-use-compressed-files
16751 If non-@code{nil}, @code{nnml} will allow using compressed message
16752 files. This requires @code{auto-compression-mode} to be enabled
16753 (@pxref{Compressed Files, ,Compressed Files, emacs, The Emacs Manual}).
16754 If the value of @code{nnml-use-compressed-files} is a string, it is used
16755 as the file extension specifying the compression program. You can set it
16756 to @samp{.bz2} if your Emacs supports it. A value of @code{t} is
16757 equivalent to @samp{.gz}.
16759 @item nnml-compressed-files-size-threshold
16760 @vindex nnml-compressed-files-size-threshold
16761 Default size threshold for compressed message files. Message files with
16762 bodies larger than that many characters will be automatically compressed
16763 if @code{nnml-use-compressed-files} is non-@code{nil}.
16767 @findex nnml-generate-nov-databases
16768 If your @code{nnml} groups and @acronym{NOV} files get totally out of
16769 whack, you can do a complete update by typing @kbd{M-x
16770 nnml-generate-nov-databases}. This command will trawl through the
16771 entire @code{nnml} hierarchy, looking at each and every article, so it
16772 might take a while to complete. A better interface to this
16773 functionality can be found in the server buffer (@pxref{Server
16778 @subsubsection MH Spool
16780 @cindex mh-e mail spool
16782 @code{nnmh} is just like @code{nnml}, except that is doesn't generate
16783 @acronym{NOV} databases and it doesn't keep an active file or marks
16784 file. This makes @code{nnmh} a @emph{much} slower back end than
16785 @code{nnml}, but it also makes it easier to write procmail scripts
16788 Virtual server settings:
16791 @item nnmh-directory
16792 @vindex nnmh-directory
16793 All @code{nnmh} directories will be located under this directory. The
16794 default is the value of @code{message-directory} (whose default is
16797 @item nnmh-get-new-mail
16798 @vindex nnmh-get-new-mail
16799 If non-@code{nil}, @code{nnmh} will read incoming mail. The default is
16803 @vindex nnmh-be-safe
16804 If non-@code{nil}, @code{nnmh} will go to ridiculous lengths to make
16805 sure that the articles in the folder are actually what Gnus thinks
16806 they are. It will check date stamps and stat everything in sight, so
16807 setting this to @code{t} will mean a serious slow-down. If you never
16808 use anything but Gnus to read the @code{nnmh} articles, you do not
16809 have to set this variable to @code{t}. The default is @code{nil}.
16814 @subsubsection Maildir
16818 @code{nnmaildir} stores mail in the maildir format, with each maildir
16819 corresponding to a group in Gnus. This format is documented here:
16820 @uref{http://cr.yp.to/proto/maildir.html} and here:
16821 @uref{http://www.qmail.org/man/man5/maildir.html}. @code{nnmaildir}
16822 also stores extra information in the @file{.nnmaildir/} directory
16825 Maildir format was designed to allow concurrent deliveries and
16826 reading, without needing locks. With other back ends, you would have
16827 your mail delivered to a spool of some kind, and then you would
16828 configure Gnus to split mail from that spool into your groups. You
16829 can still do that with @code{nnmaildir}, but the more common
16830 configuration is to have your mail delivered directly to the maildirs
16831 that appear as group in Gnus.
16833 @code{nnmaildir} is designed to be perfectly reliable: @kbd{C-g} will
16834 never corrupt its data in memory, and @code{SIGKILL} will never
16835 corrupt its data in the filesystem.
16837 @code{nnmaildir} stores article marks and @acronym{NOV} data in each
16838 maildir. So you can copy a whole maildir from one Gnus setup to
16839 another, and you will keep your marks.
16841 Virtual server settings:
16845 For each of your @code{nnmaildir} servers (it's very unlikely that
16846 you'd need more than one), you need to create a directory and populate
16847 it with maildirs or symlinks to maildirs (and nothing else; do not
16848 choose a directory already used for other purposes). Each maildir
16849 will be represented in Gnus as a newsgroup on that server; the
16850 filename of the symlink will be the name of the group. Any filenames
16851 in the directory starting with @samp{.} are ignored. The directory is
16852 scanned when you first start Gnus, and each time you type @kbd{g} in
16853 the group buffer; if any maildirs have been removed or added,
16854 @code{nnmaildir} notices at these times.
16856 The value of the @code{directory} parameter should be a Lisp form
16857 which is processed by @code{eval} and @code{expand-file-name} to get
16858 the path of the directory for this server. The form is @code{eval}ed
16859 only when the server is opened; the resulting string is used until the
16860 server is closed. (If you don't know about forms and @code{eval},
16861 don't worry---a simple string will work.) This parameter is not
16862 optional; you must specify it. I don't recommend using
16863 @code{"~/Mail"} or a subdirectory of it; several other parts of Gnus
16864 use that directory by default for various things, and may get confused
16865 if @code{nnmaildir} uses it too. @code{"~/.nnmaildir"} is a typical
16868 @item target-prefix
16869 This should be a Lisp form which is processed by @code{eval} and
16870 @code{expand-file-name}. The form is @code{eval}ed only when the
16871 server is opened; the resulting string is used until the server is
16874 When you create a group on an @code{nnmaildir} server, the maildir is
16875 created with @code{target-prefix} prepended to its name, and a symlink
16876 pointing to that maildir is created, named with the plain group name.
16877 So if @code{directory} is @code{"~/.nnmaildir"} and
16878 @code{target-prefix} is @code{"../maildirs/"}, then when you create
16879 the group @code{foo}, @code{nnmaildir} will create
16880 @file{~/.nnmaildir/../maildirs/foo} as a maildir, and will create
16881 @file{~/.nnmaildir/foo} as a symlink pointing to
16882 @file{../maildirs/foo}.
16884 You can set @code{target-prefix} to a string without any slashes to
16885 create both maildirs and symlinks in the same @code{directory}; in
16886 this case, any maildirs found in @code{directory} whose names start
16887 with @code{target-prefix} will not be listed as groups (but the
16888 symlinks pointing to them will be).
16890 As a special case, if @code{target-prefix} is @code{""} (the default),
16891 then when you create a group, the maildir will be created in
16892 @code{directory} without a corresponding symlink. Beware that you
16893 cannot use @code{gnus-group-delete-group} on such groups without the
16894 @code{force} argument.
16896 @item directory-files
16897 This should be a function with the same interface as
16898 @code{directory-files} (such as @code{directory-files} itself). It is
16899 used to scan the server's @code{directory} for maildirs. This
16900 parameter is optional; the default is
16901 @code{nnheader-directory-files-safe} if
16902 @code{nnheader-directory-files-is-safe} is @code{nil}, and
16903 @code{directory-files} otherwise.
16904 (@code{nnheader-directory-files-is-safe} is checked only once when the
16905 server is opened; if you want to check it each time the directory is
16906 scanned, you'll have to provide your own function that does that.)
16909 If non-@code{nil}, then after scanning for new mail in the group
16910 maildirs themselves as usual, this server will also incorporate mail
16911 the conventional Gnus way, from @code{mail-sources} according to
16912 @code{nnmail-split-methods} or @code{nnmail-split-fancy}. The default
16913 value is @code{nil}.
16915 Do @emph{not} use the same maildir both in @code{mail-sources} and as
16916 an @code{nnmaildir} group. The results might happen to be useful, but
16917 that would be by chance, not by design, and the results might be
16918 different in the future. If your split rules create new groups,
16919 remember to supply a @code{create-directory} server parameter.
16922 @subsubsection Group parameters
16924 @code{nnmaildir} uses several group parameters. It's safe to ignore
16925 all this; the default behavior for @code{nnmaildir} is the same as the
16926 default behavior for other mail back ends: articles are deleted after
16927 one week, etc. Except for the expiry parameters, all this
16928 functionality is unique to @code{nnmaildir}, so you can ignore it if
16929 you're just trying to duplicate the behavior you already have with
16932 If the value of any of these parameters is a vector, the first element
16933 is evaluated as a Lisp form and the result is used, rather than the
16934 original value. If the value is not a vector, the value itself is
16935 evaluated as a Lisp form. (This is why these parameters use names
16936 different from those of other, similar parameters supported by other
16937 back ends: they have different, though similar, meanings.) (For
16938 numbers, strings, @code{nil}, and @code{t}, you can ignore the
16939 @code{eval} business again; for other values, remember to use an extra
16940 quote and wrap the value in a vector when appropriate.)
16944 An integer specifying the minimum age, in seconds, of an article
16945 before it will be expired, or the symbol @code{never} to specify that
16946 articles should never be expired. If this parameter is not set,
16947 @code{nnmaildir} falls back to the usual
16948 @code{nnmail-expiry-wait}(@code{-function}) variables (the
16949 @code{expiry-wait} group parameter overrides @code{nnmail-expiry-wait}
16950 and makes @code{nnmail-expiry-wait-function} ineffective). If you
16951 wanted a value of 3 days, you could use something like @code{[(* 3 24
16952 60 60)]}; @code{nnmaildir} will evaluate the form and use the result.
16953 An article's age is measured starting from the article file's
16954 modification time. Normally, this is the same as the article's
16955 delivery time, but editing an article makes it younger. Moving an
16956 article (other than via expiry) may also make an article younger.
16959 If this is set to a string such as a full Gnus group name, like
16961 "backend+server.address.string:group.name"
16963 and if it is not the name of the same group that the parameter belongs
16964 to, then articles will be moved to the specified group during expiry
16965 before being deleted. @emph{If this is set to an @code{nnmaildir}
16966 group, the article will be just as old in the destination group as it
16967 was in the source group.} So be careful with @code{expire-age} in the
16968 destination group. If this is set to the name of the same group that
16969 the parameter belongs to, then the article is not expired at all. If
16970 you use the vector form, the first element is evaluated once for each
16971 article. So that form can refer to
16972 @code{nnmaildir-article-file-name}, etc., to decide where to put the
16973 article. @emph{Even if this parameter is not set, @code{nnmaildir}
16974 does not fall back to the @code{expiry-target} group parameter or the
16975 @code{nnmail-expiry-target} variable.}
16978 If this is set to @code{t}, @code{nnmaildir} will treat the articles
16979 in this maildir as read-only. This means: articles are not renamed
16980 from @file{new/} into @file{cur/}; articles are only found in
16981 @file{new/}, not @file{cur/}; articles are never deleted; articles
16982 cannot be edited. @file{new/} is expected to be a symlink to the
16983 @file{new/} directory of another maildir---e.g., a system-wide mailbox
16984 containing a mailing list of common interest. Everything in the
16985 maildir outside @file{new/} is @emph{not} treated as read-only, so for
16986 a shared mailbox, you do still need to set up your own maildir (or
16987 have write permission to the shared mailbox); your maildir just won't
16988 contain extra copies of the articles.
16990 @item directory-files
16991 A function with the same interface as @code{directory-files}. It is
16992 used to scan the directories in the maildir corresponding to this
16993 group to find articles. The default is the function specified by the
16994 server's @code{directory-files} parameter.
16996 @item distrust-Lines:
16997 If non-@code{nil}, @code{nnmaildir} will always count the lines of an
16998 article, rather than use the @code{Lines:} header field. If
16999 @code{nil}, the header field will be used if present.
17002 A list of mark symbols, such as @code{['(read expire)]}. Whenever
17003 Gnus asks @code{nnmaildir} for article marks, @code{nnmaildir} will
17004 say that all articles have these marks, regardless of whether the
17005 marks stored in the filesystem say so. This is a proof-of-concept
17006 feature that will probably be removed eventually; it ought to be done
17007 in Gnus proper, or abandoned if it's not worthwhile.
17010 A list of mark symbols, such as @code{['(tick expire)]}. Whenever
17011 Gnus asks @code{nnmaildir} for article marks, @code{nnmaildir} will
17012 say that no articles have these marks, regardless of whether the marks
17013 stored in the filesystem say so. @code{never-marks} overrides
17014 @code{always-marks}. This is a proof-of-concept feature that will
17015 probably be removed eventually; it ought to be done in Gnus proper, or
17016 abandoned if it's not worthwhile.
17018 @item nov-cache-size
17019 An integer specifying the size of the @acronym{NOV} memory cache. To
17020 speed things up, @code{nnmaildir} keeps @acronym{NOV} data in memory
17021 for a limited number of articles in each group. (This is probably not
17022 worthwhile, and will probably be removed in the future.) This
17023 parameter's value is noticed only the first time a group is seen after
17024 the server is opened---i.e., when you first start Gnus, typically.
17025 The @acronym{NOV} cache is never resized until the server is closed
17026 and reopened. The default is an estimate of the number of articles
17027 that would be displayed in the summary buffer: a count of articles
17028 that are either marked with @code{tick} or not marked with
17029 @code{read}, plus a little extra.
17032 @subsubsection Article identification
17033 Articles are stored in the @file{cur/} subdirectory of each maildir.
17034 Each article file is named like @code{uniq:info}, where @code{uniq}
17035 contains no colons. @code{nnmaildir} ignores, but preserves, the
17036 @code{:info} part. (Other maildir readers typically use this part of
17037 the filename to store marks.) The @code{uniq} part uniquely
17038 identifies the article, and is used in various places in the
17039 @file{.nnmaildir/} subdirectory of the maildir to store information
17040 about the corresponding article. The full pathname of an article is
17041 available in the variable @code{nnmaildir-article-file-name} after you
17042 request the article in the summary buffer.
17044 @subsubsection NOV data
17045 An article identified by @code{uniq} has its @acronym{NOV} data (used
17046 to generate lines in the summary buffer) stored in
17047 @code{.nnmaildir/nov/uniq}. There is no
17048 @code{nnmaildir-generate-nov-databases} function. (There isn't much
17049 need for it---an article's @acronym{NOV} data is updated automatically
17050 when the article or @code{nnmail-extra-headers} has changed.) You can
17051 force @code{nnmaildir} to regenerate the @acronym{NOV} data for a
17052 single article simply by deleting the corresponding @acronym{NOV}
17053 file, but @emph{beware}: this will also cause @code{nnmaildir} to
17054 assign a new article number for this article, which may cause trouble
17055 with @code{seen} marks, the Agent, and the cache.
17057 @subsubsection Article marks
17058 An article identified by @code{uniq} is considered to have the mark
17059 @code{flag} when the file @file{.nnmaildir/marks/flag/uniq} exists.
17060 When Gnus asks @code{nnmaildir} for a group's marks, @code{nnmaildir}
17061 looks for such files and reports the set of marks it finds. When Gnus
17062 asks @code{nnmaildir} to store a new set of marks, @code{nnmaildir}
17063 creates and deletes the corresponding files as needed. (Actually,
17064 rather than create a new file for each mark, it just creates hard
17065 links to @file{.nnmaildir/markfile}, to save inodes.)
17067 You can invent new marks by creating a new directory in
17068 @file{.nnmaildir/marks/}. You can tar up a maildir and remove it from
17069 your server, untar it later, and keep your marks. You can add and
17070 remove marks yourself by creating and deleting mark files. If you do
17071 this while Gnus is running and your @code{nnmaildir} server is open,
17072 it's best to exit all summary buffers for @code{nnmaildir} groups and
17073 type @kbd{s} in the group buffer first, and to type @kbd{g} or
17074 @kbd{M-g} in the group buffer afterwards. Otherwise, Gnus might not
17075 pick up the changes, and might undo them.
17079 @subsubsection Mail Folders
17081 @cindex mbox folders
17082 @cindex mail folders
17084 @code{nnfolder} is a back end for storing each mail group in a
17085 separate file. Each file is in the standard Un*x mbox format.
17086 @code{nnfolder} will add extra headers to keep track of article
17087 numbers and arrival dates.
17089 @cindex self contained nnfolder servers
17091 When the marks file is used (which it is by default), @code{nnfolder}
17092 servers have the property that you may backup them using @code{tar} or
17093 similar, and later be able to restore them into Gnus (by adding the
17094 proper @code{nnfolder} server) and have all your marks be preserved.
17095 Marks for a group are usually stored in a file named as the mbox file
17096 with @code{.mrk} concatenated to it (but see
17097 @code{nnfolder-marks-file-suffix}) within the @code{nnfolder}
17098 directory. Individual @code{nnfolder} groups are also possible to
17099 backup, use @kbd{G m} to restore the group (after restoring the backup
17100 into the @code{nnfolder} directory).
17102 Virtual server settings:
17105 @item nnfolder-directory
17106 @vindex nnfolder-directory
17107 All the @code{nnfolder} mail boxes will be stored under this
17108 directory. The default is the value of @code{message-directory}
17109 (whose default is @file{~/Mail})
17111 @item nnfolder-active-file
17112 @vindex nnfolder-active-file
17113 The name of the active file. The default is @file{~/Mail/active}.
17115 @item nnfolder-newsgroups-file
17116 @vindex nnfolder-newsgroups-file
17117 The name of the group descriptions file. @xref{Newsgroups File
17118 Format}. The default is @file{~/Mail/newsgroups}
17120 @item nnfolder-get-new-mail
17121 @vindex nnfolder-get-new-mail
17122 If non-@code{nil}, @code{nnfolder} will read incoming mail. The
17123 default is @code{t}
17125 @item nnfolder-save-buffer-hook
17126 @vindex nnfolder-save-buffer-hook
17127 @cindex backup files
17128 Hook run before saving the folders. Note that Emacs does the normal
17129 backup renaming of files even with the @code{nnfolder} buffers. If
17130 you wish to switch this off, you could say something like the
17131 following in your @file{.emacs} file:
17134 (defun turn-off-backup ()
17135 (set (make-local-variable 'backup-inhibited) t))
17137 (add-hook 'nnfolder-save-buffer-hook 'turn-off-backup)
17140 @item nnfolder-delete-mail-hook
17141 @vindex nnfolder-delete-mail-hook
17142 Hook run in a buffer narrowed to the message that is to be deleted.
17143 This function can be used to copy the message to somewhere else, or to
17144 extract some information from it before removing it.
17146 @item nnfolder-nov-is-evil
17147 @vindex nnfolder-nov-is-evil
17148 If non-@code{nil}, this back end will ignore any @acronym{NOV} files. The
17149 default is @code{nil}.
17151 @item nnfolder-nov-file-suffix
17152 @vindex nnfolder-nov-file-suffix
17153 The extension for @acronym{NOV} files. The default is @file{.nov}.
17155 @item nnfolder-nov-directory
17156 @vindex nnfolder-nov-directory
17157 The directory where the @acronym{NOV} files should be stored. If
17158 @code{nil}, @code{nnfolder-directory} is used.
17160 @item nnfolder-marks-is-evil
17161 @vindex nnfolder-marks-is-evil
17162 If non-@code{nil}, this back end will ignore any @sc{marks} files. The
17163 default is @code{nil}.
17165 @item nnfolder-marks-file-suffix
17166 @vindex nnfolder-marks-file-suffix
17167 The extension for @sc{marks} files. The default is @file{.mrk}.
17169 @item nnfolder-marks-directory
17170 @vindex nnfolder-marks-directory
17171 The directory where the @sc{marks} files should be stored. If
17172 @code{nil}, @code{nnfolder-directory} is used.
17177 @findex nnfolder-generate-active-file
17178 @kindex M-x nnfolder-generate-active-file
17179 If you have lots of @code{nnfolder}-like files you'd like to read with
17180 @code{nnfolder}, you can use the @kbd{M-x nnfolder-generate-active-file}
17181 command to make @code{nnfolder} aware of all likely files in
17182 @code{nnfolder-directory}. This only works if you use long file names,
17185 @node Comparing Mail Back Ends
17186 @subsubsection Comparing Mail Back Ends
17188 First, just for terminology, the @dfn{back end} is the common word for a
17189 low-level access method---a transport, if you will, by which something
17190 is acquired. The sense is that one's mail has to come from somewhere,
17191 and so selection of a suitable back end is required in order to get that
17192 mail within spitting distance of Gnus.
17194 The same concept exists for Usenet itself: Though access to articles is
17195 typically done by @acronym{NNTP} these days, once upon a midnight dreary, everyone
17196 in the world got at Usenet by running a reader on the machine where the
17197 articles lay (the machine which today we call an @acronym{NNTP} server), and
17198 access was by the reader stepping into the articles' directory spool
17199 area directly. One can still select between either the @code{nntp} or
17200 @code{nnspool} back ends, to select between these methods, if one happens
17201 actually to live on the server (or can see its spool directly, anyway,
17204 The goal in selecting a mail back end is to pick one which
17205 simultaneously represents a suitable way of dealing with the original
17206 format plus leaving mail in a form that is convenient to use in the
17207 future. Here are some high and low points on each:
17212 UNIX systems have historically had a single, very common, and well-
17213 defined format. All messages arrive in a single @dfn{spool file}, and
17214 they are delineated by a line whose regular expression matches
17215 @samp{^From_}. (My notational use of @samp{_} is to indicate a space,
17216 to make it clear in this instance that this is not the RFC-specified
17217 @samp{From:} header.) Because Emacs and therefore Gnus emanate
17218 historically from the Unix environment, it is simplest if one does not
17219 mess a great deal with the original mailbox format, so if one chooses
17220 this back end, Gnus' primary activity in getting mail from the real spool
17221 area to Gnus' preferred directory is simply to copy it, with no
17222 (appreciable) format change in the process. It is the ``dumbest'' way
17223 to move mail into availability in the Gnus environment. This makes it
17224 fast to move into place, but slow to parse, when Gnus has to look at
17229 Once upon a time, there was the DEC-10 and DEC-20, running operating
17230 systems called TOPS and related things, and the usual (only?) mail
17231 reading environment was a thing called Babyl. I don't know what format
17232 was used for mail landing on the system, but Babyl had its own internal
17233 format to which mail was converted, primarily involving creating a
17234 spool-file-like entity with a scheme for inserting Babyl-specific
17235 headers and status bits above the top of each message in the file.
17236 Rmail was Emacs' first mail reader, it was written by Richard Stallman,
17237 and Stallman came out of that TOPS/Babyl environment, so he wrote Rmail
17238 to understand the mail files folks already had in existence. Gnus (and
17239 VM, for that matter) continue to support this format because it's
17240 perceived as having some good qualities in those mailer-specific
17241 headers/status bits stuff. Rmail itself still exists as well, of
17242 course, and is still maintained within Emacs. Since Emacs 23, it
17243 uses standard mbox format rather than Babyl.
17245 Both of the above forms leave your mail in a single file on your
17246 file system, and they must parse that entire file each time you take a
17251 @code{nnml} is the back end which smells the most as though you were
17252 actually operating with an @code{nnspool}-accessed Usenet system. (In
17253 fact, I believe @code{nnml} actually derived from @code{nnspool} code,
17254 lo these years ago.) One's mail is taken from the original spool file,
17255 and is then cut up into individual message files, 1:1. It maintains a
17256 Usenet-style active file (analogous to what one finds in an INN- or
17257 CNews-based news system in (for instance) @file{/var/lib/news/active},
17258 or what is returned via the @samp{NNTP LIST} verb) and also creates
17259 @dfn{overview} files for efficient group entry, as has been defined for
17260 @acronym{NNTP} servers for some years now. It is slower in mail-splitting,
17261 due to the creation of lots of files, updates to the @code{nnml} active
17262 file, and additions to overview files on a per-message basis, but it is
17263 extremely fast on access because of what amounts to the indexing support
17264 provided by the active file and overviews.
17266 @code{nnml} costs @dfn{inodes} in a big way; that is, it soaks up the
17267 resource which defines available places in the file system to put new
17268 files. Sysadmins take a dim view of heavy inode occupation within
17269 tight, shared file systems. But if you live on a personal machine where
17270 the file system is your own and space is not at a premium, @code{nnml}
17273 It is also problematic using this back end if you are living in a
17274 FAT16-based Windows world, since much space will be wasted on all these
17279 The Rand MH mail-reading system has been around UNIX systems for a very
17280 long time; it operates by splitting one's spool file of messages into
17281 individual files, but with little or no indexing support---@code{nnmh}
17282 is considered to be semantically equivalent to ``@code{nnml} without
17283 active file or overviews''. This is arguably the worst choice, because
17284 one gets the slowness of individual file creation married to the
17285 slowness of access parsing when learning what's new in one's groups.
17289 Basically the effect of @code{nnfolder} is @code{nnmbox} (the first
17290 method described above) on a per-group basis. That is, @code{nnmbox}
17291 itself puts @emph{all} one's mail in one file; @code{nnfolder} provides a
17292 little bit of optimization to this so that each of one's mail groups has
17293 a Unix mail box file. It's faster than @code{nnmbox} because each group
17294 can be parsed separately, and still provides the simple Unix mail box
17295 format requiring minimal effort in moving the mail around. In addition,
17296 it maintains an ``active'' file making it much faster for Gnus to figure
17297 out how many messages there are in each separate group.
17299 If you have groups that are expected to have a massive amount of
17300 messages, @code{nnfolder} is not the best choice, but if you receive
17301 only a moderate amount of mail, @code{nnfolder} is probably the most
17302 friendly mail back end all over.
17306 For configuring expiry and other things, @code{nnmaildir} uses
17307 incompatible group parameters, slightly different from those of other
17310 @code{nnmaildir} is largely similar to @code{nnml}, with some notable
17311 differences. Each message is stored in a separate file, but the
17312 filename is unrelated to the article number in Gnus. @code{nnmaildir}
17313 also stores the equivalent of @code{nnml}'s overview files in one file
17314 per article, so it uses about twice as many inodes as @code{nnml}. (Use
17315 @code{df -i} to see how plentiful your inode supply is.) If this slows
17316 you down or takes up very much space, consider switching to
17317 @uref{http://www.namesys.com/, ReiserFS} or another non-block-structured
17320 Since maildirs don't require locking for delivery, the maildirs you use
17321 as groups can also be the maildirs your mail is directly delivered to.
17322 This means you can skip Gnus' mail splitting if your mail is already
17323 organized into different mailboxes during delivery. A @code{directory}
17324 entry in @code{mail-sources} would have a similar effect, but would
17325 require one set of mailboxes for spooling deliveries (in mbox format,
17326 thus damaging message bodies), and another set to be used as groups (in
17327 whatever format you like). A maildir has a built-in spool, in the
17328 @code{new/} subdirectory. Beware that currently, mail moved from
17329 @code{new/} to @code{cur/} instead of via mail splitting will not
17330 undergo treatment such as duplicate checking.
17332 @code{nnmaildir} stores article marks for a given group in the
17333 corresponding maildir, in a way designed so that it's easy to manipulate
17334 them from outside Gnus. You can tar up a maildir, unpack it somewhere
17335 else, and still have your marks. @code{nnml} also stores marks, but
17336 it's not as easy to work with them from outside Gnus as with
17339 @code{nnmaildir} uses a significant amount of memory to speed things up.
17340 (It keeps in memory some of the things that @code{nnml} stores in files
17341 and that @code{nnmh} repeatedly parses out of message files.) If this
17342 is a problem for you, you can set the @code{nov-cache-size} group
17343 parameter to something small (0 would probably not work, but 1 probably
17344 would) to make it use less memory. This caching will probably be
17345 removed in the future.
17347 Startup is likely to be slower with @code{nnmaildir} than with other
17348 back ends. Everything else is likely to be faster, depending in part
17349 on your file system.
17351 @code{nnmaildir} does not use @code{nnoo}, so you cannot use @code{nnoo}
17352 to write an @code{nnmaildir}-derived back end.
17357 @node Browsing the Web
17358 @section Browsing the Web
17360 @cindex browsing the web
17364 Web-based discussion forums are getting more and more popular. On many
17365 subjects, the web-based forums have become the most important forums,
17366 eclipsing the importance of mailing lists and news groups. The reason
17367 is easy to understand---they are friendly to new users; you just point
17368 and click, and there's the discussion. With mailing lists, you have to
17369 go through a cumbersome subscription procedure, and most people don't
17370 even know what a news group is.
17372 The problem with this scenario is that web browsers are not very good at
17373 being newsreaders. They do not keep track of what articles you've read;
17374 they do not allow you to score on subjects you're interested in; they do
17375 not allow off-line browsing; they require you to click around and drive
17376 you mad in the end.
17378 So---if web browsers suck at reading discussion forums, why not use Gnus
17381 Gnus has been getting a bit of a collection of back ends for providing
17382 interfaces to these sources.
17386 * Web Searches:: Creating groups from articles that match a string.
17387 * Slashdot:: Reading the Slashdot comments.
17388 * Ultimate:: The Ultimate Bulletin Board systems.
17389 * Web Archive:: Reading mailing list archived on web.
17390 * RSS:: Reading RDF site summary.
17391 * Customizing W3:: Doing stuff to Emacs/W3 from Gnus.
17394 All the web sources require Emacs/W3 and the url library or those
17395 alternatives to work.
17397 The main caveat with all these web sources is that they probably won't
17398 work for a very long time. Gleaning information from the @acronym{HTML} data
17399 is guesswork at best, and when the layout is altered, the Gnus back end
17400 will fail. If you have reasonably new versions of these back ends,
17401 though, you should be ok.
17403 One thing all these Web methods have in common is that the Web sources
17404 are often down, unavailable or just plain too slow to be fun. In those
17405 cases, it makes a lot of sense to let the Gnus Agent (@pxref{Gnus
17406 Unplugged}) handle downloading articles, and then you can read them at
17407 leisure from your local disk. No more World Wide Wait for you.
17409 @node Archiving Mail
17410 @subsection Archiving Mail
17411 @cindex archiving mail
17412 @cindex backup of mail
17414 Some of the back ends, notably @code{nnml}, @code{nnfolder}, and
17415 @code{nnmaildir}, now actually store the article marks with each group.
17416 For these servers, archiving and restoring a group while preserving
17417 marks is fairly simple.
17419 (Preserving the group level and group parameters as well still
17420 requires ritual dancing and sacrifices to the @file{.newsrc.eld} deity
17423 To archive an entire @code{nnml}, @code{nnfolder}, or @code{nnmaildir}
17424 server, take a recursive copy of the server directory. There is no need
17425 to shut down Gnus, so archiving may be invoked by @code{cron} or
17426 similar. You restore the data by restoring the directory tree, and
17427 adding a server definition pointing to that directory in Gnus. The
17428 @ref{Article Backlog}, @ref{Asynchronous Fetching} and other things
17429 might interfere with overwriting data, so you may want to shut down Gnus
17430 before you restore the data.
17432 It is also possible to archive individual @code{nnml},
17433 @code{nnfolder}, or @code{nnmaildir} groups, while preserving marks.
17434 For @code{nnml} or @code{nnmaildir}, you copy all files in the group's
17435 directory. For @code{nnfolder} you need to copy both the base folder
17436 file itself (@file{FOO}, say), and the marks file (@file{FOO.mrk} in
17437 this example). Restoring the group is done with @kbd{G m} from the Group
17438 buffer. The last step makes Gnus notice the new directory.
17439 @code{nnmaildir} notices the new directory automatically, so @kbd{G m}
17440 is unnecessary in that case.
17443 @subsection Web Searches
17448 @cindex Usenet searches
17449 @cindex searching the Usenet
17451 It's, like, too neat to search the Usenet for articles that match a
17452 string, but it, like, totally @emph{sucks}, like, totally, to use one of
17453 those, like, Web browsers, and you, like, have to, rilly, like, look at
17454 the commercials, so, like, with Gnus you can do @emph{rad}, rilly,
17455 searches without having to use a browser.
17457 The @code{nnweb} back end allows an easy interface to the mighty search
17458 engine. You create an @code{nnweb} group, enter a search pattern, and
17459 then enter the group and read the articles like you would any normal
17460 group. The @kbd{G w} command in the group buffer (@pxref{Foreign
17461 Groups}) will do this in an easy-to-use fashion.
17463 @code{nnweb} groups don't really lend themselves to being solid
17464 groups---they have a very fleeting idea of article numbers. In fact,
17465 each time you enter an @code{nnweb} group (not even changing the search
17466 pattern), you are likely to get the articles ordered in a different
17467 manner. Not even using duplicate suppression (@pxref{Duplicate
17468 Suppression}) will help, since @code{nnweb} doesn't even know the
17469 @code{Message-ID} of the articles before reading them using some search
17470 engines (Google, for instance). The only possible way to keep track
17471 of which articles you've read is by scoring on the @code{Date}
17472 header---mark all articles posted before the last date you read the
17475 If the search engine changes its output substantially, @code{nnweb}
17476 won't be able to parse it and will fail. One could hardly fault the Web
17477 providers if they were to do this---their @emph{raison d'@^etre} is to
17478 make money off of advertisements, not to provide services to the
17479 community. Since @code{nnweb} washes the ads off all the articles, one
17480 might think that the providers might be somewhat miffed. We'll see.
17482 You must have the @code{url} and @code{W3} package or those alternatives
17483 (try @code{customize-group} on the @samp{mm-url} variable group)
17484 installed to be able to use @code{nnweb}.
17486 Virtual server variables:
17491 What search engine type is being used. The currently supported types
17492 are @code{google}, @code{dejanews}, and @code{gmane}. Note that
17493 @code{dejanews} is an alias to @code{google}.
17496 @vindex nnweb-search
17497 The search string to feed to the search engine.
17499 @item nnweb-max-hits
17500 @vindex nnweb-max-hits
17501 Advisory maximum number of hits per search to display. The default is
17504 @item nnweb-type-definition
17505 @vindex nnweb-type-definition
17506 Type-to-definition alist. This alist says what @code{nnweb} should do
17507 with the various search engine types. The following elements must be
17512 Function to decode the article and provide something that Gnus
17516 Function to create an article number to message header and URL alist.
17519 Function to send the search string to the search engine.
17522 The address the aforementioned function should send the search string
17526 Format string URL to fetch an article by @code{Message-ID}.
17533 @subsection Slashdot
17537 @uref{http://slashdot.org/, Slashdot} is a popular news site, with
17538 lively discussion following the news articles. @code{nnslashdot} will
17539 let you read this forum in a convenient manner.
17541 The easiest way to read this source is to put something like the
17542 following in your @file{~/.gnus.el} file:
17545 (setq gnus-secondary-select-methods
17546 '((nnslashdot "")))
17549 This will make Gnus query the @code{nnslashdot} back end for new comments
17550 and groups. The @kbd{F} command will subscribe each new news article as
17551 a new Gnus group, and you can read the comments by entering these
17552 groups. (Note that the default subscription method is to subscribe new
17553 groups as zombies. Other methods are available (@pxref{Subscription
17556 If you want to remove an old @code{nnslashdot} group, the @kbd{G DEL}
17557 command is the most handy tool (@pxref{Foreign Groups}).
17559 When following up to @code{nnslashdot} comments (or posting new
17560 comments), some light @acronym{HTML}izations will be performed. In
17561 particular, text quoted with @samp{> } will be quoted with
17562 @samp{blockquote} instead, and signatures will have @samp{br} added to
17563 the end of each line. Other than that, you can just write @acronym{HTML}
17564 directly into the message buffer. Note that Slashdot filters out some
17565 @acronym{HTML} forms.
17567 The following variables can be altered to change its behavior:
17570 @item nnslashdot-threaded
17571 Whether @code{nnslashdot} should display threaded groups or not. The
17572 default is @code{t}. To be able to display threads, @code{nnslashdot}
17573 has to retrieve absolutely all comments in a group upon entry. If a
17574 threaded display is not required, @code{nnslashdot} will only retrieve
17575 the comments that are actually wanted by the user. Threading is nicer,
17576 but much, much slower than unthreaded.
17578 @item nnslashdot-login-name
17579 @vindex nnslashdot-login-name
17580 The login name to use when posting.
17582 @item nnslashdot-password
17583 @vindex nnslashdot-password
17584 The password to use when posting.
17586 @item nnslashdot-directory
17587 @vindex nnslashdot-directory
17588 Where @code{nnslashdot} will store its files. The default is
17589 @file{~/News/slashdot/}.
17591 @item nnslashdot-active-url
17592 @vindex nnslashdot-active-url
17593 The @acronym{URL} format string that will be used to fetch the
17594 information on news articles and comments. The default is@*
17595 @samp{http://slashdot.org/search.pl?section=&min=%d}.
17597 @item nnslashdot-comments-url
17598 @vindex nnslashdot-comments-url
17599 The @acronym{URL} format string that will be used to fetch comments.
17601 @item nnslashdot-article-url
17602 @vindex nnslashdot-article-url
17603 The @acronym{URL} format string that will be used to fetch the news
17604 article. The default is
17605 @samp{http://slashdot.org/article.pl?sid=%s&mode=nocomment}.
17607 @item nnslashdot-threshold
17608 @vindex nnslashdot-threshold
17609 The score threshold. The default is -1.
17611 @item nnslashdot-group-number
17612 @vindex nnslashdot-group-number
17613 The number of old groups, in addition to the ten latest, to keep
17614 updated. The default is 0.
17621 @subsection Ultimate
17623 @cindex Ultimate Bulletin Board
17625 @uref{http://www.ultimatebb.com/, The Ultimate Bulletin Board} is
17626 probably the most popular Web bulletin board system used. It has a
17627 quite regular and nice interface, and it's possible to get the
17628 information Gnus needs to keep groups updated.
17630 The easiest way to get started with @code{nnultimate} is to say
17631 something like the following in the group buffer: @kbd{B nnultimate RET
17632 http://www.tcj.com/messboard/ubbcgi/ RET}. (Substitute the @acronym{URL}
17633 (not including @samp{Ultimate.cgi} or the like at the end) for a forum
17634 you're interested in; there's quite a list of them on the Ultimate web
17635 site.) Then subscribe to the groups you're interested in from the
17636 server buffer, and read them from the group buffer.
17638 The following @code{nnultimate} variables can be altered:
17641 @item nnultimate-directory
17642 @vindex nnultimate-directory
17643 The directory where @code{nnultimate} stores its files. The default is@*
17644 @file{~/News/ultimate/}.
17649 @subsection Web Archive
17651 @cindex Web Archive
17653 Some mailing lists only have archives on Web servers, such as
17654 @uref{http://www.egroups.com/} and
17655 @uref{http://www.mail-archive.com/}. It has a quite regular and nice
17656 interface, and it's possible to get the information Gnus needs to keep
17659 @findex gnus-group-make-warchive-group
17660 The easiest way to get started with @code{nnwarchive} is to say
17661 something like the following in the group buffer: @kbd{M-x
17662 gnus-group-make-warchive-group RET @var{an_egroup} RET egroups RET
17663 www.egroups.com RET @var{your@@email.address} RET}. (Substitute the
17664 @var{an_egroup} with the mailing list you subscribed, the
17665 @var{your@@email.address} with your email address.), or to browse the
17666 back end by @kbd{B nnwarchive RET mail-archive RET}.
17668 The following @code{nnwarchive} variables can be altered:
17671 @item nnwarchive-directory
17672 @vindex nnwarchive-directory
17673 The directory where @code{nnwarchive} stores its files. The default is@*
17674 @file{~/News/warchive/}.
17676 @item nnwarchive-login
17677 @vindex nnwarchive-login
17678 The account name on the web server.
17680 @item nnwarchive-passwd
17681 @vindex nnwarchive-passwd
17682 The password for your account on the web server.
17690 Some web sites have an RDF Site Summary (@acronym{RSS}).
17691 @acronym{RSS} is a format for summarizing headlines from news related
17692 sites (such as BBC or CNN). But basically anything list-like can be
17693 presented as an @acronym{RSS} feed: weblogs, changelogs or recent
17694 changes to a wiki (e.g. @url{http://cliki.net/recent-changes.rdf}).
17696 @acronym{RSS} has a quite regular and nice interface, and it's
17697 possible to get the information Gnus needs to keep groups updated.
17699 Note: you had better use Emacs which supports the @code{utf-8} coding
17700 system because @acronym{RSS} uses UTF-8 for encoding non-@acronym{ASCII}
17701 text by default. It is also used by default for non-@acronym{ASCII}
17704 @kindex G R (Group)
17705 Use @kbd{G R} from the group buffer to subscribe to a feed---you will be
17706 prompted for the location, the title and the description of the feed.
17707 The title, which allows any characters, will be used for the group name
17708 and the name of the group data file. The description can be omitted.
17710 An easy way to get started with @code{nnrss} is to say something like
17711 the following in the group buffer: @kbd{B nnrss RET RET y}, then
17712 subscribe to groups.
17714 The @code{nnrss} back end saves the group data file in
17715 @code{nnrss-directory} (see below) for each @code{nnrss} group. File
17716 names containing non-@acronym{ASCII} characters will be encoded by the
17717 coding system specified with the @code{nnmail-pathname-coding-system}
17718 variable or other. Also @xref{Non-ASCII Group Names}, for more
17721 The @code{nnrss} back end generates @samp{multipart/alternative}
17722 @acronym{MIME} articles in which each contains a @samp{text/plain} part
17723 and a @samp{text/html} part.
17726 You can also use the following commands to import and export your
17727 subscriptions from a file in @acronym{OPML} format (Outline Processor
17730 @defun nnrss-opml-import file
17731 Prompt for an @acronym{OPML} file, and subscribe to each feed in the
17735 @defun nnrss-opml-export
17736 Write your current @acronym{RSS} subscriptions to a buffer in
17737 @acronym{OPML} format.
17740 The following @code{nnrss} variables can be altered:
17743 @item nnrss-directory
17744 @vindex nnrss-directory
17745 The directory where @code{nnrss} stores its files. The default is
17746 @file{~/News/rss/}.
17748 @item nnrss-file-coding-system
17749 @vindex nnrss-file-coding-system
17750 The coding system used when reading and writing the @code{nnrss} groups
17751 data files. The default is the value of
17752 @code{mm-universal-coding-system} (which defaults to @code{emacs-mule}
17753 in Emacs or @code{escape-quoted} in XEmacs).
17755 @item nnrss-ignore-article-fields
17756 @vindex nnrss-ignore-article-fields
17757 Some feeds update constantly article fields during their publications,
17758 e.g. to indicate the number of comments. However, if there is
17759 a difference between the local article and the distant one, the latter
17760 is considered to be new. To avoid this and discard some fields, set this
17761 variable to the list of fields to be ignored. The default is
17762 @code{'(slash:comments)}.
17764 @item nnrss-use-local
17765 @vindex nnrss-use-local
17766 @findex nnrss-generate-download-script
17767 If you set @code{nnrss-use-local} to @code{t}, @code{nnrss} will read
17768 the feeds from local files in @code{nnrss-directory}. You can use
17769 the command @code{nnrss-generate-download-script} to generate a
17770 download script using @command{wget}.
17772 @item nnrss-wash-html-in-text-plain-parts
17773 Non-@code{nil} means that @code{nnrss} renders text in @samp{text/plain}
17774 parts as @acronym{HTML}. The function specified by the
17775 @code{mm-text-html-renderer} variable (@pxref{Display Customization,
17776 ,Display Customization, emacs-mime, The Emacs MIME Manual}) will be used
17777 to render text. If it is @code{nil}, which is the default, text will
17778 simply be folded. Leave it @code{nil} if you prefer to see
17779 @samp{text/html} parts.
17782 The following code may be helpful, if you want to show the description in
17783 the summary buffer.
17786 (add-to-list 'nnmail-extra-headers nnrss-description-field)
17787 (setq gnus-summary-line-format "%U%R%z%I%(%[%4L: %-15,15f%]%) %s%uX\n")
17789 (defun gnus-user-format-function-X (header)
17791 (assq nnrss-description-field (mail-header-extra header))))
17792 (if descr (concat "\n\t" (cdr descr)) "")))
17795 The following code may be useful to open an nnrss url directly from the
17799 (require 'browse-url)
17801 (defun browse-nnrss-url (arg)
17803 (let ((url (assq nnrss-url-field
17806 (assq (gnus-summary-article-number)
17807 gnus-newsgroup-data))))))
17810 (browse-url (cdr url))
17811 (gnus-summary-mark-as-read-forward 1))
17812 (gnus-summary-scroll-up arg))))
17814 (eval-after-load "gnus"
17815 #'(define-key gnus-summary-mode-map
17816 (kbd "<RET>") 'browse-nnrss-url))
17817 (add-to-list 'nnmail-extra-headers nnrss-url-field)
17820 Even if you have added @samp{text/html} to the
17821 @code{mm-discouraged-alternatives} variable (@pxref{Display
17822 Customization, ,Display Customization, emacs-mime, The Emacs MIME
17823 Manual}) since you don't want to see @acronym{HTML} parts, it might be
17824 more useful especially in @code{nnrss} groups to display
17825 @samp{text/html} parts. Here's an example of setting
17826 @code{mm-discouraged-alternatives} as a group parameter (@pxref{Group
17827 Parameters}) in order to display @samp{text/html} parts only in
17828 @code{nnrss} groups:
17831 ;; @r{Set the default value of @code{mm-discouraged-alternatives}.}
17832 (eval-after-load "gnus-sum"
17834 'gnus-newsgroup-variables
17835 '(mm-discouraged-alternatives
17836 . '("text/html" "image/.*"))))
17838 ;; @r{Display @samp{text/html} parts in @code{nnrss} groups.}
17841 '("\\`nnrss:" (mm-discouraged-alternatives nil)))
17845 @node Customizing W3
17846 @subsection Customizing W3
17852 Gnus uses the url library to fetch web pages and Emacs/W3 (or those
17853 alternatives) to display web pages. Emacs/W3 is documented in its own
17854 manual, but there are some things that may be more relevant for Gnus
17857 For instance, a common question is how to make Emacs/W3 follow links
17858 using the @code{browse-url} functions (which will call some external web
17859 browser like Netscape). Here's one way:
17862 (eval-after-load "w3"
17864 (fset 'w3-fetch-orig (symbol-function 'w3-fetch))
17865 (defun w3-fetch (&optional url target)
17866 (interactive (list (w3-read-url-with-default)))
17867 (if (eq major-mode 'gnus-article-mode)
17869 (w3-fetch-orig url target)))))
17872 Put that in your @file{.emacs} file, and hitting links in W3-rendered
17873 @acronym{HTML} in the Gnus article buffers will use @code{browse-url} to
17880 @cindex @acronym{IMAP}
17882 @acronym{IMAP} is a network protocol for reading mail (or news, or @dots{}),
17883 think of it as a modernized @acronym{NNTP}. Connecting to a @acronym{IMAP}
17884 server is much similar to connecting to a news server, you just
17885 specify the network address of the server.
17887 @acronym{IMAP} has two properties. First, @acronym{IMAP} can do
17888 everything that @acronym{POP} can, it can hence be viewed as a
17889 @acronym{POP++}. Secondly, @acronym{IMAP} is a mail storage protocol,
17890 similar to @acronym{NNTP} being a news storage protocol---however,
17891 @acronym{IMAP} offers more features than @acronym{NNTP} because news
17892 is more or less read-only whereas mail is read-write.
17894 If you want to use @acronym{IMAP} as a @acronym{POP++}, use an imap
17895 entry in @code{mail-sources}. With this, Gnus will fetch mails from
17896 the @acronym{IMAP} server and store them on the local disk. This is
17897 not the usage described in this section---@xref{Mail Sources}.
17899 If you want to use @acronym{IMAP} as a mail storage protocol, use an nnimap
17900 entry in @code{gnus-secondary-select-methods}. With this, Gnus will
17901 manipulate mails stored on the @acronym{IMAP} server. This is the kind of
17902 usage explained in this section.
17904 A server configuration in @file{~/.gnus.el} with a few @acronym{IMAP}
17905 servers might look something like the following. (Note that for
17906 @acronym{TLS}/@acronym{SSL}, you need external programs and libraries,
17910 (setq gnus-secondary-select-methods
17911 '((nnimap "simpleserver") ; @r{no special configuration}
17912 ; @r{perhaps a ssh port forwarded server:}
17914 (nnimap-address "localhost")
17915 (nnimap-server-port 1430))
17916 ; @r{a UW server running on localhost}
17918 (nnimap-server-port 143)
17919 (nnimap-address "localhost")
17920 (nnimap-list-pattern ("INBOX" "mail/*")))
17921 ; @r{anonymous public cyrus server:}
17922 (nnimap "cyrus.andrew.cmu.edu"
17923 (nnimap-authenticator anonymous)
17924 (nnimap-list-pattern "archive.*")
17925 (nnimap-stream network))
17926 ; @r{a ssl server on a non-standard port:}
17928 (nnimap-address "vic20.somewhere.com")
17929 (nnimap-server-port 9930)
17930 (nnimap-stream ssl))))
17933 After defining the new server, you can subscribe to groups on the
17934 server using normal Gnus commands such as @kbd{U} in the Group Buffer
17935 (@pxref{Subscription Commands}) or via the Server Buffer
17936 (@pxref{Server Buffer}).
17938 The following variables can be used to create a virtual @code{nnimap}
17943 @item nnimap-address
17944 @vindex nnimap-address
17946 The address of the remote @acronym{IMAP} server. Defaults to the virtual
17947 server name if not specified.
17949 @item nnimap-server-port
17950 @vindex nnimap-server-port
17951 Port on server to contact. Defaults to port 143, or 993 for @acronym{TLS}/@acronym{SSL}.
17953 Note that this should be an integer, example server specification:
17956 (nnimap "mail.server.com"
17957 (nnimap-server-port 4711))
17960 @item nnimap-list-pattern
17961 @vindex nnimap-list-pattern
17962 String or list of strings of mailboxes to limit available groups to.
17963 This is used when the server has very many mailboxes and you're only
17964 interested in a few---some servers export your home directory via
17965 @acronym{IMAP}, you'll probably want to limit the mailboxes to those in
17966 @file{~/Mail/*} then.
17968 The string can also be a cons of REFERENCE and the string as above, what
17969 REFERENCE is used for is server specific, but on the University of
17970 Washington server it's a directory that will be concatenated with the
17973 Example server specification:
17976 (nnimap "mail.server.com"
17977 (nnimap-list-pattern ("INBOX" "Mail/*" "alt.sex.*"
17978 ("~friend/Mail/" . "list/*"))))
17981 @item nnimap-stream
17982 @vindex nnimap-stream
17983 The type of stream used to connect to your server. By default, nnimap
17984 will detect and automatically use all of the below, with the exception
17985 of @acronym{TLS}/@acronym{SSL}. (@acronym{IMAP} over
17986 @acronym{TLS}/@acronym{SSL} is being replaced by STARTTLS, which can
17987 be automatically detected, but it's not widely deployed yet.)
17989 Example server specification:
17992 (nnimap "mail.server.com"
17993 (nnimap-stream ssl))
17996 Please note that the value of @code{nnimap-stream} is a symbol!
18000 @dfn{gssapi:} Connect with GSSAPI (usually Kerberos 5). Requires the
18001 @samp{gsasl} or @samp{imtest} program.
18003 @dfn{kerberos4:} Connect with Kerberos 4. Requires the @samp{imtest} program.
18005 @dfn{starttls:} Connect via the STARTTLS extension (similar to
18006 @acronym{TLS}/@acronym{SSL}). Requires the external library @samp{starttls.el} and program
18009 @dfn{tls:} Connect through @acronym{TLS}. Requires GNUTLS (the program
18010 @samp{gnutls-cli}).
18012 @dfn{ssl:} Connect through @acronym{SSL}. Requires OpenSSL (the program
18013 @samp{openssl}) or SSLeay (@samp{s_client}).
18015 @dfn{shell:} Use a shell command to start @acronym{IMAP} connection.
18017 @dfn{network:} Plain, TCP/IP network connection.
18020 @vindex imap-kerberos4-program
18021 The @samp{imtest} program is shipped with Cyrus IMAPD. If you're
18022 using @samp{imtest} from Cyrus IMAPD < 2.0.14 (which includes version
18023 1.5.x and 1.6.x) you need to frob @code{imap-process-connection-type}
18024 to make @code{imap.el} use a pty instead of a pipe when communicating
18025 with @samp{imtest}. You will then suffer from a line length
18026 restrictions on @acronym{IMAP} commands, which might make Gnus seem to hang
18027 indefinitely if you have many articles in a mailbox. The variable
18028 @code{imap-kerberos4-program} contain parameters to pass to the imtest
18031 For @acronym{TLS} connection, the @code{gnutls-cli} program from GNUTLS is
18032 needed. It is available from
18033 @uref{http://www.gnu.org/software/gnutls/}.
18035 @vindex imap-gssapi-program
18036 This parameter specifies a list of command lines that invoke a GSSAPI
18037 authenticated @acronym{IMAP} stream in a subshell. They are tried
18038 sequentially until a connection is made, or the list has been
18039 exhausted. By default, @samp{gsasl} from GNU SASL, available from
18040 @uref{http://www.gnu.org/software/gsasl/}, and the @samp{imtest}
18041 program from Cyrus IMAPD (see @code{imap-kerberos4-program}), are
18044 @vindex imap-ssl-program
18045 For @acronym{SSL} connections, the OpenSSL program is available from
18046 @uref{http://www.openssl.org/}. OpenSSL was formerly known as SSLeay,
18047 and nnimap support it too---although the most recent versions of
18048 SSLeay, 0.9.x, are known to have serious bugs making it
18049 useless. Earlier versions, especially 0.8.x, of SSLeay are known to
18050 work. The variable @code{imap-ssl-program} contain parameters to pass
18053 @vindex imap-shell-program
18054 @vindex imap-shell-host
18055 For @acronym{IMAP} connections using the @code{shell} stream, the
18056 variable @code{imap-shell-program} specify what program to call. Make
18057 sure nothing is interfering with the output of the program, e.g., don't
18058 forget to redirect the error output to the void.
18060 @item nnimap-authenticator
18061 @vindex nnimap-authenticator
18063 The authenticator used to connect to the server. By default, nnimap
18064 will use the most secure authenticator your server is capable of.
18066 Example server specification:
18069 (nnimap "mail.server.com"
18070 (nnimap-authenticator anonymous))
18073 Please note that the value of @code{nnimap-authenticator} is a symbol!
18077 @dfn{gssapi:} GSSAPI (usually kerberos 5) authentication. Requires
18078 external program @code{gsasl} or @code{imtest}.
18080 @dfn{kerberos4:} Kerberos 4 authentication. Requires external program
18083 @dfn{digest-md5:} Encrypted username/password via DIGEST-MD5. Requires
18084 external library @code{digest-md5.el}.
18086 @dfn{cram-md5:} Encrypted username/password via CRAM-MD5.
18088 @dfn{login:} Plain-text username/password via LOGIN.
18090 @dfn{anonymous:} Login as ``anonymous'', supplying your email address as password.
18093 @item nnimap-expunge-on-close
18095 @vindex nnimap-expunge-on-close
18096 Unlike Parmenides the @acronym{IMAP} designers have decided things that
18097 don't exist actually do exist. More specifically, @acronym{IMAP} has
18098 this concept of marking articles @code{Deleted} which doesn't actually
18099 delete them, and this (marking them @code{Deleted}, that is) is what
18100 nnimap does when you delete an article in Gnus (with @kbd{B DEL} or
18103 Since the articles aren't really removed when we mark them with the
18104 @code{Deleted} flag we'll need a way to actually delete them. Feel like
18105 running in circles yet?
18107 Traditionally, nnimap has removed all articles marked as @code{Deleted}
18108 when closing a mailbox but this is now configurable by this server
18111 The possible options are:
18116 The default behavior, delete all articles marked as ``Deleted'' when
18119 Never actually delete articles. Currently there is no way of showing
18120 the articles marked for deletion in nnimap, but other @acronym{IMAP} clients
18121 may allow you to do this. If you ever want to run the EXPUNGE command
18122 manually, @xref{Expunging mailboxes}.
18124 When closing mailboxes, nnimap will ask if you wish to expunge deleted
18129 @item nnimap-importantize-dormant
18130 @vindex nnimap-importantize-dormant
18132 If non-@code{nil} (the default), marks dormant articles as ticked (as
18133 well), for other @acronym{IMAP} clients. Within Gnus, dormant articles will
18134 naturally still (only) be marked as dormant. This is to make dormant
18135 articles stand out, just like ticked articles, in other @acronym{IMAP}
18136 clients. (In other words, Gnus has two ``Tick'' marks and @acronym{IMAP}
18139 Probably the only reason for frobbing this would be if you're trying
18140 enable per-user persistent dormant flags, using something like:
18143 (setcdr (assq 'dormant nnimap-mark-to-flag-alist)
18144 (format "gnus-dormant-%s" (user-login-name)))
18145 (setcdr (assq 'dormant nnimap-mark-to-predicate-alist)
18146 (format "KEYWORD gnus-dormant-%s" (user-login-name)))
18149 In this case, you would not want the per-user dormant flag showing up
18150 as ticked for other users.
18152 @item nnimap-expunge-search-string
18154 @vindex nnimap-expunge-search-string
18155 @cindex expiring @acronym{IMAP} mail
18157 This variable contain the @acronym{IMAP} search command sent to server when
18158 searching for articles eligible for expiring. The default is
18159 @code{"UID %s NOT SINCE %s"}, where the first @code{%s} is replaced by
18160 UID set and the second @code{%s} is replaced by a date.
18162 Probably the only useful value to change this to is
18163 @code{"UID %s NOT SENTSINCE %s"}, which makes nnimap use the Date: in
18164 messages instead of the internal article date. See section 6.4.4 of
18165 RFC 2060 for more information on valid strings.
18167 However, if @code{nnimap-search-uids-not-since-is-evil}
18168 is true, this variable has no effect since the search logic
18169 is reversed, as described below.
18171 @item nnimap-authinfo-file
18172 @vindex nnimap-authinfo-file
18174 A file containing credentials used to log in on servers. The format is
18175 (almost) the same as the @code{ftp} @file{~/.netrc} file. See the
18176 variable @code{nntp-authinfo-file} for exact syntax; also see
18177 @ref{NNTP}. An example of an .authinfo line for an IMAP server, is:
18180 machine students.uio.no login larsi password geheimnis port imap
18183 Note that it should be @code{port imap}, or @code{port 143}, if you
18184 use a @code{nnimap-stream} of @code{tls} or @code{ssl}, even if the
18185 actual port number used is port 993 for secured IMAP. For
18186 convenience, Gnus will accept @code{port imaps} as a synonym of
18189 @item nnimap-need-unselect-to-notice-new-mail
18190 @vindex nnimap-need-unselect-to-notice-new-mail
18192 Unselect mailboxes before looking for new mail in them. Some servers
18193 seem to need this under some circumstances; it was reported that
18196 @item nnimap-nov-is-evil
18197 @vindex nnimap-nov-is-evil
18198 @cindex Courier @acronym{IMAP} server
18199 @cindex @acronym{NOV}
18201 Never generate or use a local @acronym{NOV} database. Defaults to the
18202 value of @code{gnus-agent}.
18204 Using a @acronym{NOV} database usually makes header fetching much
18205 faster, but it uses the @code{UID SEARCH UID} command, which is very
18206 slow on some servers (notably some versions of Courier). Since the Gnus
18207 Agent caches the information in the @acronym{NOV} database without using
18208 the slow command, this variable defaults to true if the Agent is in use,
18209 and false otherwise.
18211 @item nnimap-search-uids-not-since-is-evil
18212 @vindex nnimap-search-uids-not-since-is-evil
18213 @cindex Courier @acronym{IMAP} server
18214 @cindex expiring @acronym{IMAP} mail
18216 Avoid the @code{UID SEARCH UID @var{message numbers} NOT SINCE
18217 @var{date}} command, which is slow on some @acronym{IMAP} servers
18218 (notably, some versions of Courier). Instead, use @code{UID SEARCH SINCE
18219 @var{date}} and prune the list of expirable articles within Gnus.
18221 When Gnus expires your mail (@pxref{Expiring Mail}), it starts with a
18222 list of expirable articles and asks the IMAP server questions like ``Of
18223 these articles, which ones are older than a week?'' While this seems
18224 like a perfectly reasonable question, some IMAP servers take a long time
18225 to answer it, since they seemingly go looking into every old article to
18226 see if it is one of the expirable ones. Curiously, the question ``Of
18227 @emph{all} articles, which ones are newer than a week?'' seems to be
18228 much faster to answer, so setting this variable causes Gnus to ask this
18229 question and figure out the answer to the real question itself.
18231 This problem can really sneak up on you: when you first configure Gnus,
18232 everything works fine, but once you accumulate a couple thousand
18233 messages, you start cursing Gnus for being so slow. On the other hand,
18234 if you get a lot of email within a week, setting this variable will
18235 cause a lot of network traffic between Gnus and the IMAP server.
18237 @item nnimap-logout-timeout
18238 @vindex nnimap-logout-timeout
18240 There is a case where a connection to a @acronym{IMAP} server is unable
18241 to close, when connecting to the server via a certain kind of network,
18242 e.g. @acronym{VPN}. In that case, it will be observed that a connection
18243 between Emacs and the local network looks alive even if the server has
18244 closed a connection for some reason (typically, a timeout).
18245 Consequently, Emacs continues waiting for a response from the server for
18246 the @code{LOGOUT} command that Emacs sent, or hangs in other words. If
18247 you are in such a network, setting this variable to a number of seconds
18248 will be helpful. If it is set, a hung connection will be closed
18249 forcibly, after this number of seconds from the time Emacs sends the
18250 @code{LOGOUT} command. It should not be too small value but too large
18251 value will be inconvenient too. Perhaps the value 1.0 will be a good
18252 candidate but it might be worth trying some other values.
18254 Example server specification:
18257 (nnimap "mail.server.com"
18258 (nnimap-logout-timeout 1.0))
18264 * Splitting in IMAP:: Splitting mail with nnimap.
18265 * Expiring in IMAP:: Expiring mail with nnimap.
18266 * Editing IMAP ACLs:: Limiting/enabling other users access to a mailbox.
18267 * Expunging mailboxes:: Equivalent of a ``compress mailbox'' button.
18268 * A note on namespaces:: How to (not) use @acronym{IMAP} namespace in Gnus.
18269 * Debugging IMAP:: What to do when things don't work.
18274 @node Splitting in IMAP
18275 @subsection Splitting in IMAP
18276 @cindex splitting imap mail
18278 Splitting is something Gnus users have loved and used for years, and now
18279 the rest of the world is catching up. Yeah, dream on, not many
18280 @acronym{IMAP} servers have server side splitting and those that have
18281 splitting seem to use some non-standard protocol. This means that
18282 @acronym{IMAP} support for Gnus has to do its own splitting.
18286 (Incidentally, people seem to have been dreaming on, and Sieve has
18287 gaining a market share and is supported by several IMAP servers.
18288 Fortunately, Gnus support it too, @xref{Sieve Commands}.)
18290 Here are the variables of interest:
18294 @item nnimap-split-crosspost
18295 @cindex splitting, crosspost
18297 @vindex nnimap-split-crosspost
18299 If non-@code{nil}, do crossposting if several split methods match the
18300 mail. If @code{nil}, the first match in @code{nnimap-split-rule}
18301 found will be used.
18303 Nnmail equivalent: @code{nnmail-crosspost}.
18305 @item nnimap-split-inbox
18306 @cindex splitting, inbox
18308 @vindex nnimap-split-inbox
18310 A string or a list of strings that gives the name(s) of @acronym{IMAP}
18311 mailboxes to split from. Defaults to @code{nil}, which means that
18312 splitting is disabled!
18315 (setq nnimap-split-inbox
18316 '("INBOX" ("~/friend/Mail" . "lists/*") "lists.imap"))
18319 No nnmail equivalent.
18321 @item nnimap-split-rule
18322 @cindex splitting, rules
18323 @vindex nnimap-split-rule
18325 New mail found in @code{nnimap-split-inbox} will be split according to
18328 This variable contains a list of lists, where the first element in the
18329 sublist gives the name of the @acronym{IMAP} mailbox to move articles
18330 matching the regexp in the second element in the sublist. Got that?
18331 Neither did I, we need examples.
18334 (setq nnimap-split-rule
18336 "^Sender: owner-nnimap@@vic20.globalcom.se")
18337 ("INBOX.junk" "^Subject:.*MAKE MONEY")
18338 ("INBOX.private" "")))
18341 This will put all articles from the nnimap mailing list into mailbox
18342 INBOX.nnimap, all articles containing MAKE MONEY in the Subject: line
18343 into INBOX.junk and everything else in INBOX.private.
18345 The first string may contain @samp{\\1} forms, like the ones used by
18346 replace-match to insert sub-expressions from the matched text. For
18350 ("INBOX.lists.\\1" "^Sender: owner-\\([a-z-]+\\)@@")
18353 The first element can also be the symbol @code{junk} to indicate that
18354 matching messages should simply be deleted. Use with care.
18356 The second element can also be a function. In that case, it will be
18357 called with the first element of the rule as the argument, in a buffer
18358 containing the headers of the article. It should return a
18359 non-@code{nil} value if it thinks that the mail belongs in that group.
18361 Nnmail users might recollect that the last regexp had to be empty to
18362 match all articles (like in the example above). This is not required in
18363 nnimap. Articles not matching any of the regexps will not be moved out
18364 of your inbox. (This might affect performance if you keep lots of
18365 unread articles in your inbox, since the splitting code would go over
18366 them every time you fetch new mail.)
18368 These rules are processed from the beginning of the alist toward the
18369 end. The first rule to make a match will ``win'', unless you have
18370 crossposting enabled. In that case, all matching rules will ``win''.
18372 This variable can also have a function as its value, the function will
18373 be called with the headers narrowed and should return a group where it
18374 thinks the article should be split to. See @code{nnimap-split-fancy}.
18376 The splitting code tries to create mailboxes if it needs to.
18378 To allow for different split rules on different virtual servers, and
18379 even different split rules in different inboxes on the same server,
18380 the syntax of this variable have been extended along the lines of:
18383 (setq nnimap-split-rule
18384 '(("my1server" (".*" (("ding" "ding@@gnus.org")
18385 ("junk" "From:.*Simon"))))
18386 ("my2server" ("INBOX" nnimap-split-fancy))
18387 ("my[34]server" (".*" (("private" "To:.*Simon")
18388 ("junk" my-junk-func))))))
18391 The virtual server name is in fact a regexp, so that the same rules
18392 may apply to several servers. In the example, the servers
18393 @code{my3server} and @code{my4server} both use the same rules.
18394 Similarly, the inbox string is also a regexp. The actual splitting
18395 rules are as before, either a function, or a list with group/regexp or
18396 group/function elements.
18398 Nnmail equivalent: @code{nnmail-split-methods}.
18400 @item nnimap-split-predicate
18402 @vindex nnimap-split-predicate
18404 Mail matching this predicate in @code{nnimap-split-inbox} will be
18405 split, it is a string and the default is @samp{UNSEEN UNDELETED}.
18407 This might be useful if you use another @acronym{IMAP} client to read mail in
18408 your inbox but would like Gnus to split all articles in the inbox
18409 regardless of readedness. Then you might change this to
18412 @item nnimap-split-fancy
18413 @cindex splitting, fancy
18414 @findex nnimap-split-fancy
18415 @vindex nnimap-split-fancy
18417 It's possible to set @code{nnimap-split-rule} to
18418 @code{nnmail-split-fancy} if you want to use fancy
18419 splitting. @xref{Fancy Mail Splitting}.
18421 However, to be able to have different fancy split rules for nnmail and
18422 nnimap back ends you can set @code{nnimap-split-rule} to
18423 @code{nnimap-split-fancy} and define the nnimap specific fancy split
18424 rule in @code{nnimap-split-fancy}.
18429 (setq nnimap-split-rule 'nnimap-split-fancy
18430 nnimap-split-fancy ...)
18433 Nnmail equivalent: @code{nnmail-split-fancy}.
18435 @item nnimap-split-download-body
18436 @findex nnimap-split-download-body
18437 @vindex nnimap-split-download-body
18439 Set to non-@code{nil} to download entire articles during splitting.
18440 This is generally not required, and will slow things down
18441 considerably. You may need it if you want to use an advanced
18442 splitting function that analyzes the body to split the article.
18446 @node Expiring in IMAP
18447 @subsection Expiring in IMAP
18448 @cindex expiring @acronym{IMAP} mail
18450 Even though @code{nnimap} is not a proper @code{nnmail} derived back
18451 end, it supports most features in regular expiring (@pxref{Expiring
18452 Mail}). Unlike splitting in @acronym{IMAP} (@pxref{Splitting in
18453 IMAP}) it does not clone the @code{nnmail} variables (i.e., creating
18454 @var{nnimap-expiry-wait}) but reuse the @code{nnmail} variables. What
18455 follows below are the variables used by the @code{nnimap} expiry
18458 A note on how the expire mark is stored on the @acronym{IMAP} server is
18459 appropriate here as well. The expire mark is translated into a
18460 @code{imap} client specific mark, @code{gnus-expire}, and stored on the
18461 message. This means that likely only Gnus will understand and treat
18462 the @code{gnus-expire} mark properly, although other clients may allow
18463 you to view client specific flags on the message. It also means that
18464 your server must support permanent storage of client specific flags on
18465 messages. Most do, fortunately.
18467 If expiring @acronym{IMAP} mail seems very slow, try setting the server
18468 variable @code{nnimap-search-uids-not-since-is-evil}.
18472 @item nnmail-expiry-wait
18473 @item nnmail-expiry-wait-function
18475 These variables are fully supported. The expire value can be a
18476 number, the symbol @code{immediate} or @code{never}.
18478 @item nnmail-expiry-target
18480 This variable is supported, and internally implemented by calling the
18481 @code{nnmail} functions that handle this. It contains an optimization
18482 that if the destination is a @acronym{IMAP} group on the same server, the
18483 article is copied instead of appended (that is, uploaded again).
18487 @node Editing IMAP ACLs
18488 @subsection Editing IMAP ACLs
18489 @cindex editing imap acls
18490 @cindex Access Control Lists
18491 @cindex Editing @acronym{IMAP} ACLs
18492 @kindex G l (Group)
18493 @findex gnus-group-nnimap-edit-acl
18495 ACL stands for Access Control List. ACLs are used in @acronym{IMAP} for
18496 limiting (or enabling) other users access to your mail boxes. Not all
18497 @acronym{IMAP} servers support this, this function will give an error if it
18500 To edit an ACL for a mailbox, type @kbd{G l}
18501 (@code{gnus-group-edit-nnimap-acl}) and you'll be presented with an ACL
18502 editing window with detailed instructions.
18504 Some possible uses:
18508 Giving ``anyone'' the ``lrs'' rights (lookup, read, keep seen/unseen flags)
18509 on your mailing list mailboxes enables other users on the same server to
18510 follow the list without subscribing to it.
18512 At least with the Cyrus server, you are required to give the user
18513 ``anyone'' posting ("p") capabilities to have ``plussing'' work (that is,
18514 mail sent to user+mailbox@@domain ending up in the @acronym{IMAP} mailbox
18518 @node Expunging mailboxes
18519 @subsection Expunging mailboxes
18523 @cindex manual expunging
18524 @kindex G x (Group)
18525 @findex gnus-group-nnimap-expunge
18527 If you're using the @code{never} setting of @code{nnimap-expunge-on-close},
18528 you may want the option of expunging all deleted articles in a mailbox
18529 manually. This is exactly what @kbd{G x} does.
18531 Currently there is no way of showing deleted articles, you can just
18534 @node A note on namespaces
18535 @subsection A note on namespaces
18536 @cindex IMAP namespace
18539 The @acronym{IMAP} protocol has a concept called namespaces, described
18540 by the following text in the RFC2060:
18543 5.1.2. Mailbox Namespace Naming Convention
18545 By convention, the first hierarchical element of any mailbox name
18546 which begins with "#" identifies the "namespace" of the remainder of
18547 the name. This makes it possible to disambiguate between different
18548 types of mailbox stores, each of which have their own namespaces.
18550 For example, implementations which offer access to USENET
18551 newsgroups MAY use the "#news" namespace to partition the USENET
18552 newsgroup namespace from that of other mailboxes. Thus, the
18553 comp.mail.misc newsgroup would have an mailbox name of
18554 "#news.comp.mail.misc", and the name "comp.mail.misc" could refer
18555 to a different object (e.g. a user's private mailbox).
18558 While there is nothing in this text that warrants concern for the
18559 @acronym{IMAP} implementation in Gnus, some servers use namespace
18560 prefixes in a way that does not work with how Gnus uses mailbox names.
18562 Specifically, University of Washington's @acronym{IMAP} server uses
18563 mailbox names like @code{#driver.mbx/read-mail} which are valid only
18564 in the @sc{create} and @sc{append} commands. After the mailbox is
18565 created (or a messages is appended to a mailbox), it must be accessed
18566 without the namespace prefix, i.e. @code{read-mail}. Since Gnus do
18567 not make it possible for the user to guarantee that user entered
18568 mailbox names will only be used with the CREATE and APPEND commands,
18569 you should simply not use the namespace prefixed mailbox names in
18572 See the UoW IMAPD documentation for the @code{#driver.*/} prefix
18573 for more information on how to use the prefixes. They are a power
18574 tool and should be used only if you are sure what the effects are.
18576 @node Debugging IMAP
18577 @subsection Debugging IMAP
18578 @cindex IMAP debugging
18579 @cindex protocol dump (IMAP)
18581 @acronym{IMAP} is a complex protocol, more so than @acronym{NNTP} or
18582 @acronym{POP3}. Implementation bugs are not unlikely, and we do our
18583 best to fix them right away. If you encounter odd behavior, chances
18584 are that either the server or Gnus is buggy.
18586 If you are familiar with network protocols in general, you will
18587 probably be able to extract some clues from the protocol dump of the
18588 exchanges between Gnus and the server. Even if you are not familiar
18589 with network protocols, when you include the protocol dump in
18590 @acronym{IMAP}-related bug reports you are helping us with data
18591 critical to solving the problem. Therefore, we strongly encourage you
18592 to include the protocol dump when reporting IMAP bugs in Gnus.
18596 Because the protocol dump, when enabled, generates lots of data, it is
18597 disabled by default. You can enable it by setting @code{imap-log} as
18604 This instructs the @code{imap.el} package to log any exchanges with
18605 the server. The log is stored in the buffer @samp{*imap-log*}. Look
18606 for error messages, which sometimes are tagged with the keyword
18607 @code{BAD}---but when submitting a bug, make sure to include all the
18610 @node Other Sources
18611 @section Other Sources
18613 Gnus can do more than just read news or mail. The methods described
18614 below allow Gnus to view directories and files as if they were
18618 * Directory Groups:: You can read a directory as if it was a newsgroup.
18619 * Anything Groups:: Dired? Who needs dired?
18620 * Document Groups:: Single files can be the basis of a group.
18621 * SOUP:: Reading @sc{soup} packets ``offline''.
18622 * Mail-To-News Gateways:: Posting articles via mail-to-news gateways.
18626 @node Directory Groups
18627 @subsection Directory Groups
18629 @cindex directory groups
18631 If you have a directory that has lots of articles in separate files in
18632 it, you might treat it as a newsgroup. The files have to have numerical
18635 This might be an opportune moment to mention @code{ange-ftp} (and its
18636 successor @code{efs}), that most wonderful of all wonderful Emacs
18637 packages. When I wrote @code{nndir}, I didn't think much about it---a
18638 back end to read directories. Big deal.
18640 @code{ange-ftp} changes that picture dramatically. For instance, if you
18641 enter the @code{ange-ftp} file name
18642 @file{/ftp.hpc.uh.edu:/pub/emacs/ding-list/} as the directory name,
18643 @code{ange-ftp} or @code{efs} will actually allow you to read this
18644 directory over at @samp{sina} as a newsgroup. Distributed news ahoy!
18646 @code{nndir} will use @acronym{NOV} files if they are present.
18648 @code{nndir} is a ``read-only'' back end---you can't delete or expire
18649 articles with this method. You can use @code{nnmh} or @code{nnml} for
18650 whatever you use @code{nndir} for, so you could switch to any of those
18651 methods if you feel the need to have a non-read-only @code{nndir}.
18654 @node Anything Groups
18655 @subsection Anything Groups
18658 From the @code{nndir} back end (which reads a single spool-like
18659 directory), it's just a hop and a skip to @code{nneething}, which
18660 pretends that any arbitrary directory is a newsgroup. Strange, but
18663 When @code{nneething} is presented with a directory, it will scan this
18664 directory and assign article numbers to each file. When you enter such
18665 a group, @code{nneething} must create ``headers'' that Gnus can use.
18666 After all, Gnus is a newsreader, in case you're forgetting.
18667 @code{nneething} does this in a two-step process. First, it snoops each
18668 file in question. If the file looks like an article (i.e., the first
18669 few lines look like headers), it will use this as the head. If this is
18670 just some arbitrary file without a head (e.g. a C source file),
18671 @code{nneething} will cobble up a header out of thin air. It will use
18672 file ownership, name and date and do whatever it can with these
18675 All this should happen automatically for you, and you will be presented
18676 with something that looks very much like a newsgroup. Totally like a
18677 newsgroup, to be precise. If you select an article, it will be displayed
18678 in the article buffer, just as usual.
18680 If you select a line that represents a directory, Gnus will pop you into
18681 a new summary buffer for this @code{nneething} group. And so on. You can
18682 traverse the entire disk this way, if you feel like, but remember that
18683 Gnus is not dired, really, and does not intend to be, either.
18685 There are two overall modes to this action---ephemeral or solid. When
18686 doing the ephemeral thing (i.e., @kbd{G D} from the group buffer), Gnus
18687 will not store information on what files you have read, and what files
18688 are new, and so on. If you create a solid @code{nneething} group the
18689 normal way with @kbd{G m}, Gnus will store a mapping table between
18690 article numbers and file names, and you can treat this group like any
18691 other groups. When you activate a solid @code{nneething} group, you will
18692 be told how many unread articles it contains, etc., etc.
18697 @item nneething-map-file-directory
18698 @vindex nneething-map-file-directory
18699 All the mapping files for solid @code{nneething} groups will be stored
18700 in this directory, which defaults to @file{~/.nneething/}.
18702 @item nneething-exclude-files
18703 @vindex nneething-exclude-files
18704 All files that match this regexp will be ignored. Nice to use to exclude
18705 auto-save files and the like, which is what it does by default.
18707 @item nneething-include-files
18708 @vindex nneething-include-files
18709 Regexp saying what files to include in the group. If this variable is
18710 non-@code{nil}, only files matching this regexp will be included.
18712 @item nneething-map-file
18713 @vindex nneething-map-file
18714 Name of the map files.
18718 @node Document Groups
18719 @subsection Document Groups
18721 @cindex documentation group
18724 @code{nndoc} is a cute little thing that will let you read a single file
18725 as a newsgroup. Several files types are supported:
18735 The standard Unix mbox file.
18737 @cindex MMDF mail box
18739 The MMDF mail box format.
18742 Several news articles appended into a file.
18744 @cindex rnews batch files
18746 The rnews batch transport format.
18749 Netscape mail boxes.
18752 @acronym{MIME} multipart messages.
18754 @item standard-digest
18755 The standard (RFC 1153) digest format.
18758 A @acronym{MIME} digest of messages.
18760 @item lanl-gov-announce
18761 Announcement messages from LANL Gov Announce.
18763 @cindex forwarded messages
18764 @item rfc822-forward
18765 A message forwarded according to RFC822.
18768 The Outlook mail box.
18771 The Outlook Express dbx mail box.
18774 A bounce message from the Exim MTA.
18777 A message forwarded according to informal rules.
18780 An RFC934-forwarded message.
18786 A digest of Clarinet brief news items.
18789 Non-standard digest format---matches most things, but does it badly.
18795 You can also use the special ``file type'' @code{guess}, which means
18796 that @code{nndoc} will try to guess what file type it is looking at.
18797 @code{digest} means that @code{nndoc} should guess what digest type the
18800 @code{nndoc} will not try to change the file or insert any extra headers into
18801 it---it will simply, like, let you use the file as the basis for a
18802 group. And that's it.
18804 If you have some old archived articles that you want to insert into your
18805 new & spiffy Gnus mail back end, @code{nndoc} can probably help you with
18806 that. Say you have an old @file{RMAIL} file with mail that you now want
18807 to split into your new @code{nnml} groups. You look at that file using
18808 @code{nndoc} (using the @kbd{G f} command in the group buffer
18809 (@pxref{Foreign Groups})), set the process mark on all the articles in
18810 the buffer (@kbd{M P b}, for instance), and then re-spool (@kbd{B r})
18811 using @code{nnml}. If all goes well, all the mail in the @file{RMAIL}
18812 file is now also stored in lots of @code{nnml} directories, and you can
18813 delete that pesky @file{RMAIL} file. If you have the guts!
18815 Virtual server variables:
18818 @item nndoc-article-type
18819 @vindex nndoc-article-type
18820 This should be one of @code{mbox}, @code{babyl}, @code{digest},
18821 @code{news}, @code{rnews}, @code{mmdf}, @code{forward}, @code{rfc934},
18822 @code{rfc822-forward}, @code{mime-parts}, @code{standard-digest},
18823 @code{slack-digest}, @code{clari-briefs}, @code{nsmail}, @code{outlook},
18824 @code{oe-dbx}, @code{mailman}, and @code{mail-in-mail} or @code{guess}.
18826 @item nndoc-post-type
18827 @vindex nndoc-post-type
18828 This variable says whether Gnus is to consider the group a news group or
18829 a mail group. There are two valid values: @code{mail} (the default)
18834 * Document Server Internals:: How to add your own document types.
18838 @node Document Server Internals
18839 @subsubsection Document Server Internals
18841 Adding new document types to be recognized by @code{nndoc} isn't
18842 difficult. You just have to whip up a definition of what the document
18843 looks like, write a predicate function to recognize that document type,
18844 and then hook into @code{nndoc}.
18846 First, here's an example document type definition:
18850 (article-begin . "^\^A\^A\^A\^A\n")
18851 (body-end . "^\^A\^A\^A\^A\n"))
18854 The definition is simply a unique @dfn{name} followed by a series of
18855 regexp pseudo-variable settings. Below are the possible
18856 variables---don't be daunted by the number of variables; most document
18857 types can be defined with very few settings:
18860 @item first-article
18861 If present, @code{nndoc} will skip past all text until it finds
18862 something that match this regexp. All text before this will be
18865 @item article-begin
18866 This setting has to be present in all document type definitions. It
18867 says what the beginning of each article looks like. To do more
18868 complicated things that cannot be dealt with a simple regexp, you can
18869 use @code{article-begin-function} instead of this.
18871 @item article-begin-function
18872 If present, this should be a function that moves point to the beginning
18873 of each article. This setting overrides @code{article-begin}.
18876 If present, this should be a regexp that matches the head of the
18877 article. To do more complicated things that cannot be dealt with a
18878 simple regexp, you can use @code{head-begin-function} instead of this.
18880 @item head-begin-function
18881 If present, this should be a function that moves point to the head of
18882 the article. This setting overrides @code{head-begin}.
18885 This should match the end of the head of the article. It defaults to
18886 @samp{^$}---the empty line.
18889 This should match the beginning of the body of the article. It defaults
18890 to @samp{^\n}. To do more complicated things that cannot be dealt with
18891 a simple regexp, you can use @code{body-begin-function} instead of this.
18893 @item body-begin-function
18894 If present, this function should move point to the beginning of the body
18895 of the article. This setting overrides @code{body-begin}.
18898 If present, this should match the end of the body of the article. To do
18899 more complicated things that cannot be dealt with a simple regexp, you
18900 can use @code{body-end-function} instead of this.
18902 @item body-end-function
18903 If present, this function should move point to the end of the body of
18904 the article. This setting overrides @code{body-end}.
18907 If present, this should match the beginning of the file. All text
18908 before this regexp will be totally ignored.
18911 If present, this should match the end of the file. All text after this
18912 regexp will be totally ignored.
18916 So, using these variables @code{nndoc} is able to dissect a document
18917 file into a series of articles, each with a head and a body. However, a
18918 few more variables are needed since not all document types are all that
18919 news-like---variables needed to transform the head or the body into
18920 something that's palatable for Gnus:
18923 @item prepare-body-function
18924 If present, this function will be called when requesting an article. It
18925 will be called with point at the start of the body, and is useful if the
18926 document has encoded some parts of its contents.
18928 @item article-transform-function
18929 If present, this function is called when requesting an article. It's
18930 meant to be used for more wide-ranging transformation of both head and
18931 body of the article.
18933 @item generate-head-function
18934 If present, this function is called to generate a head that Gnus can
18935 understand. It is called with the article number as a parameter, and is
18936 expected to generate a nice head for the article in question. It is
18937 called when requesting the headers of all articles.
18939 @item generate-article-function
18940 If present, this function is called to generate an entire article that
18941 Gnus can understand. It is called with the article number as a
18942 parameter when requesting all articles.
18944 @item dissection-function
18945 If present, this function is called to dissect a document by itself,
18946 overriding @code{first-article}, @code{article-begin},
18947 @code{article-begin-function}, @code{head-begin},
18948 @code{head-begin-function}, @code{head-end}, @code{body-begin},
18949 @code{body-begin-function}, @code{body-end}, @code{body-end-function},
18950 @code{file-begin}, and @code{file-end}.
18954 Let's look at the most complicated example I can come up with---standard
18959 (first-article . ,(concat "^" (make-string 70 ?-) "\n\n+"))
18960 (article-begin . ,(concat "\n\n" (make-string 30 ?-) "\n\n+"))
18961 (prepare-body-function . nndoc-unquote-dashes)
18962 (body-end-function . nndoc-digest-body-end)
18963 (head-end . "^ ?$")
18964 (body-begin . "^ ?\n")
18965 (file-end . "^End of .*digest.*[0-9].*\n\\*\\*\\|^End of.*Digest *$")
18966 (subtype digest guess))
18969 We see that all text before a 70-width line of dashes is ignored; all
18970 text after a line that starts with that @samp{^End of} is also ignored;
18971 each article begins with a 30-width line of dashes; the line separating
18972 the head from the body may contain a single space; and that the body is
18973 run through @code{nndoc-unquote-dashes} before being delivered.
18975 To hook your own document definition into @code{nndoc}, use the
18976 @code{nndoc-add-type} function. It takes two parameters---the first
18977 is the definition itself and the second (optional) parameter says
18978 where in the document type definition alist to put this definition.
18979 The alist is traversed sequentially, and
18980 @code{nndoc-@var{type}-type-p} is called for a given type @var{type}.
18981 So @code{nndoc-mmdf-type-p} is called to see whether a document is of
18982 @code{mmdf} type, and so on. These type predicates should return
18983 @code{nil} if the document is not of the correct type; @code{t} if it
18984 is of the correct type; and a number if the document might be of the
18985 correct type. A high number means high probability; a low number
18986 means low probability with @samp{0} being the lowest valid number.
18994 In the PC world people often talk about ``offline'' newsreaders. These
18995 are thingies that are combined reader/news transport monstrosities.
18996 With built-in modem programs. Yecchh!
18998 Of course, us Unix Weenie types of human beans use things like
18999 @code{uucp} and, like, @code{nntpd} and set up proper news and mail
19000 transport things like Ghod intended. And then we just use normal
19003 However, it can sometimes be convenient to do something that's a bit
19004 easier on the brain if you have a very slow modem, and you're not really
19005 that interested in doing things properly.
19007 A file format called @sc{soup} has been developed for transporting news
19008 and mail from servers to home machines and back again. It can be a bit
19011 First some terminology:
19016 This is the machine that is connected to the outside world and where you
19017 get news and/or mail from.
19020 This is the machine that you want to do the actual reading and responding
19021 on. It is typically not connected to the rest of the world in any way.
19024 Something that contains messages and/or commands. There are two kinds
19028 @item message packets
19029 These are packets made at the server, and typically contain lots of
19030 messages for you to read. These are called @file{SoupoutX.tgz} by
19031 default, where @var{x} is a number.
19033 @item response packets
19034 These are packets made at the home machine, and typically contains
19035 replies that you've written. These are called @file{SoupinX.tgz} by
19036 default, where @var{x} is a number.
19046 You log in on the server and create a @sc{soup} packet. You can either
19047 use a dedicated @sc{soup} thingie (like the @code{awk} program), or you
19048 can use Gnus to create the packet with its @sc{soup} commands (@kbd{O
19049 s} and/or @kbd{G s b}; and then @kbd{G s p}) (@pxref{SOUP Commands}).
19052 You transfer the packet home. Rail, boat, car or modem will do fine.
19055 You put the packet in your home directory.
19058 You fire up Gnus on your home machine using the @code{nnsoup} back end as
19059 the native or secondary server.
19062 You read articles and mail and answer and followup to the things you
19063 want (@pxref{SOUP Replies}).
19066 You do the @kbd{G s r} command to pack these replies into a @sc{soup}
19070 You transfer this packet to the server.
19073 You use Gnus to mail this packet out with the @kbd{G s s} command.
19076 You then repeat until you die.
19080 So you basically have a bipartite system---you use @code{nnsoup} for
19081 reading and Gnus for packing/sending these @sc{soup} packets.
19084 * SOUP Commands:: Commands for creating and sending @sc{soup} packets
19085 * SOUP Groups:: A back end for reading @sc{soup} packets.
19086 * SOUP Replies:: How to enable @code{nnsoup} to take over mail and news.
19090 @node SOUP Commands
19091 @subsubsection SOUP Commands
19093 These are commands for creating and manipulating @sc{soup} packets.
19097 @kindex G s b (Group)
19098 @findex gnus-group-brew-soup
19099 Pack all unread articles in the current group
19100 (@code{gnus-group-brew-soup}). This command understands the
19101 process/prefix convention.
19104 @kindex G s w (Group)
19105 @findex gnus-soup-save-areas
19106 Save all @sc{soup} data files (@code{gnus-soup-save-areas}).
19109 @kindex G s s (Group)
19110 @findex gnus-soup-send-replies
19111 Send all replies from the replies packet
19112 (@code{gnus-soup-send-replies}).
19115 @kindex G s p (Group)
19116 @findex gnus-soup-pack-packet
19117 Pack all files into a @sc{soup} packet (@code{gnus-soup-pack-packet}).
19120 @kindex G s r (Group)
19121 @findex nnsoup-pack-replies
19122 Pack all replies into a replies packet (@code{nnsoup-pack-replies}).
19125 @kindex O s (Summary)
19126 @findex gnus-soup-add-article
19127 This summary-mode command adds the current article to a @sc{soup} packet
19128 (@code{gnus-soup-add-article}). It understands the process/prefix
19129 convention (@pxref{Process/Prefix}).
19134 There are a few variables to customize where Gnus will put all these
19139 @item gnus-soup-directory
19140 @vindex gnus-soup-directory
19141 Directory where Gnus will save intermediate files while composing
19142 @sc{soup} packets. The default is @file{~/SoupBrew/}.
19144 @item gnus-soup-replies-directory
19145 @vindex gnus-soup-replies-directory
19146 This is what Gnus will use as a temporary directory while sending our
19147 reply packets. @file{~/SoupBrew/SoupReplies/} is the default.
19149 @item gnus-soup-prefix-file
19150 @vindex gnus-soup-prefix-file
19151 Name of the file where Gnus stores the last used prefix. The default is
19152 @samp{gnus-prefix}.
19154 @item gnus-soup-packer
19155 @vindex gnus-soup-packer
19156 A format string command for packing a @sc{soup} packet. The default is
19157 @samp{tar cf - %s | gzip > $HOME/Soupout%d.tgz}.
19159 @item gnus-soup-unpacker
19160 @vindex gnus-soup-unpacker
19161 Format string command for unpacking a @sc{soup} packet. The default is
19162 @samp{gunzip -c %s | tar xvf -}.
19164 @item gnus-soup-packet-directory
19165 @vindex gnus-soup-packet-directory
19166 Where Gnus will look for reply packets. The default is @file{~/}.
19168 @item gnus-soup-packet-regexp
19169 @vindex gnus-soup-packet-regexp
19170 Regular expression matching @sc{soup} reply packets in
19171 @code{gnus-soup-packet-directory}.
19177 @subsubsection SOUP Groups
19180 @code{nnsoup} is the back end for reading @sc{soup} packets. It will
19181 read incoming packets, unpack them, and put them in a directory where
19182 you can read them at leisure.
19184 These are the variables you can use to customize its behavior:
19188 @item nnsoup-tmp-directory
19189 @vindex nnsoup-tmp-directory
19190 When @code{nnsoup} unpacks a @sc{soup} packet, it does it in this
19191 directory. (@file{/tmp/} by default.)
19193 @item nnsoup-directory
19194 @vindex nnsoup-directory
19195 @code{nnsoup} then moves each message and index file to this directory.
19196 The default is @file{~/SOUP/}.
19198 @item nnsoup-replies-directory
19199 @vindex nnsoup-replies-directory
19200 All replies will be stored in this directory before being packed into a
19201 reply packet. The default is @file{~/SOUP/replies/}.
19203 @item nnsoup-replies-format-type
19204 @vindex nnsoup-replies-format-type
19205 The @sc{soup} format of the replies packets. The default is @samp{?n}
19206 (rnews), and I don't think you should touch that variable. I probably
19207 shouldn't even have documented it. Drats! Too late!
19209 @item nnsoup-replies-index-type
19210 @vindex nnsoup-replies-index-type
19211 The index type of the replies packet. The default is @samp{?n}, which
19212 means ``none''. Don't fiddle with this one either!
19214 @item nnsoup-active-file
19215 @vindex nnsoup-active-file
19216 Where @code{nnsoup} stores lots of information. This is not an ``active
19217 file'' in the @code{nntp} sense; it's an Emacs Lisp file. If you lose
19218 this file or mess it up in any way, you're dead. The default is
19219 @file{~/SOUP/active}.
19221 @item nnsoup-packer
19222 @vindex nnsoup-packer
19223 Format string command for packing a reply @sc{soup} packet. The default
19224 is @samp{tar cf - %s | gzip > $HOME/Soupin%d.tgz}.
19226 @item nnsoup-unpacker
19227 @vindex nnsoup-unpacker
19228 Format string command for unpacking incoming @sc{soup} packets. The
19229 default is @samp{gunzip -c %s | tar xvf -}.
19231 @item nnsoup-packet-directory
19232 @vindex nnsoup-packet-directory
19233 Where @code{nnsoup} will look for incoming packets. The default is
19236 @item nnsoup-packet-regexp
19237 @vindex nnsoup-packet-regexp
19238 Regular expression matching incoming @sc{soup} packets. The default is
19241 @item nnsoup-always-save
19242 @vindex nnsoup-always-save
19243 If non-@code{nil}, save the replies buffer after each posted message.
19249 @subsubsection SOUP Replies
19251 Just using @code{nnsoup} won't mean that your postings and mailings end
19252 up in @sc{soup} reply packets automagically. You have to work a bit
19253 more for that to happen.
19255 @findex nnsoup-set-variables
19256 The @code{nnsoup-set-variables} command will set the appropriate
19257 variables to ensure that all your followups and replies end up in the
19260 In specific, this is what it does:
19263 (setq message-send-news-function 'nnsoup-request-post)
19264 (setq message-send-mail-function 'nnsoup-request-mail)
19267 And that's it, really. If you only want news to go into the @sc{soup}
19268 system you just use the first line. If you only want mail to be
19269 @sc{soup}ed you use the second.
19272 @node Mail-To-News Gateways
19273 @subsection Mail-To-News Gateways
19274 @cindex mail-to-news gateways
19277 If your local @code{nntp} server doesn't allow posting, for some reason
19278 or other, you can post using one of the numerous mail-to-news gateways.
19279 The @code{nngateway} back end provides the interface.
19281 Note that you can't read anything from this back end---it can only be
19287 @item nngateway-address
19288 @vindex nngateway-address
19289 This is the address of the mail-to-news gateway.
19291 @item nngateway-header-transformation
19292 @vindex nngateway-header-transformation
19293 News headers often have to be transformed in some odd way or other
19294 for the mail-to-news gateway to accept it. This variable says what
19295 transformation should be called, and defaults to
19296 @code{nngateway-simple-header-transformation}. The function is called
19297 narrowed to the headers to be transformed and with one parameter---the
19300 This default function just inserts a new @code{To} header based on the
19301 @code{Newsgroups} header and the gateway address.
19302 For instance, an article with this @code{Newsgroups} header:
19305 Newsgroups: alt.religion.emacs
19308 will get this @code{To} header inserted:
19311 To: alt-religion-emacs@@GATEWAY
19314 The following pre-defined functions exist:
19316 @findex nngateway-simple-header-transformation
19319 @item nngateway-simple-header-transformation
19320 Creates a @code{To} header that looks like
19321 @var{newsgroup}@@@code{nngateway-address}.
19323 @findex nngateway-mail2news-header-transformation
19325 @item nngateway-mail2news-header-transformation
19326 Creates a @code{To} header that looks like
19327 @code{nngateway-address}.
19335 (setq gnus-post-method
19337 "mail2news@@replay.com"
19338 (nngateway-header-transformation
19339 nngateway-mail2news-header-transformation)))
19342 So, to use this, simply say something like:
19345 (setq gnus-post-method '(nngateway "GATEWAY.ADDRESS"))
19350 @node Combined Groups
19351 @section Combined Groups
19353 Gnus allows combining a mixture of all the other group types into bigger
19357 * Virtual Groups:: Combining articles from many groups.
19358 * Kibozed Groups:: Looking through parts of the newsfeed for articles.
19362 @node Virtual Groups
19363 @subsection Virtual Groups
19365 @cindex virtual groups
19366 @cindex merging groups
19368 An @dfn{nnvirtual group} is really nothing more than a collection of
19371 For instance, if you are tired of reading many small groups, you can
19372 put them all in one big group, and then grow tired of reading one
19373 big, unwieldy group. The joys of computing!
19375 You specify @code{nnvirtual} as the method. The address should be a
19376 regexp to match component groups.
19378 All marks in the virtual group will stick to the articles in the
19379 component groups. So if you tick an article in a virtual group, the
19380 article will also be ticked in the component group from whence it
19381 came. (And vice versa---marks from the component groups will also be
19382 shown in the virtual group.). To create an empty virtual group, run
19383 @kbd{G V} (@code{gnus-group-make-empty-virtual}) in the group buffer
19384 and edit the method regexp with @kbd{M-e}
19385 (@code{gnus-group-edit-group-method})
19387 Here's an example @code{nnvirtual} method that collects all Andrea Dworkin
19388 newsgroups into one, big, happy newsgroup:
19391 (nnvirtual "^alt\\.fan\\.andrea-dworkin$\\|^rec\\.dworkin.*")
19394 The component groups can be native or foreign; everything should work
19395 smoothly, but if your computer explodes, it was probably my fault.
19397 Collecting the same group from several servers might actually be a good
19398 idea if users have set the Distribution header to limit distribution.
19399 If you would like to read @samp{soc.motss} both from a server in Japan
19400 and a server in Norway, you could use the following as the group regexp:
19403 "^nntp\\+server\\.jp:soc\\.motss$\\|^nntp\\+server\\.no:soc\\.motss$"
19406 (Remember, though, that if you're creating the group with @kbd{G m}, you
19407 shouldn't double the backslashes, and you should leave off the quote
19408 characters at the beginning and the end of the string.)
19410 This should work kinda smoothly---all articles from both groups should
19411 end up in this one, and there should be no duplicates. Threading (and
19412 the rest) will still work as usual, but there might be problems with the
19413 sequence of articles. Sorting on date might be an option here
19414 (@pxref{Selecting a Group}).
19416 One limitation, however---all groups included in a virtual
19417 group have to be alive (i.e., subscribed or unsubscribed). Killed or
19418 zombie groups can't be component groups for @code{nnvirtual} groups.
19420 @vindex nnvirtual-always-rescan
19421 If the @code{nnvirtual-always-rescan} variable is non-@code{nil} (which
19422 is the default), @code{nnvirtual} will always scan groups for unread
19423 articles when entering a virtual group. If this variable is @code{nil}
19424 and you read articles in a component group after the virtual group has
19425 been activated, the read articles from the component group will show up
19426 when you enter the virtual group. You'll also see this effect if you
19427 have two virtual groups that have a component group in common. If
19428 that's the case, you should set this variable to @code{t}. Or you can
19429 just tap @code{M-g} on the virtual group every time before you enter
19430 it---it'll have much the same effect.
19432 @code{nnvirtual} can have both mail and news groups as component groups.
19433 When responding to articles in @code{nnvirtual} groups, @code{nnvirtual}
19434 has to ask the back end of the component group the article comes from
19435 whether it is a news or mail back end. However, when you do a @kbd{^},
19436 there is typically no sure way for the component back end to know this,
19437 and in that case @code{nnvirtual} tells Gnus that the article came from a
19438 not-news back end. (Just to be on the safe side.)
19440 @kbd{C-c C-n} in the message buffer will insert the @code{Newsgroups}
19441 line from the article you respond to in these cases.
19443 @code{nnvirtual} groups do not inherit anything but articles and marks
19444 from component groups---group parameters, for instance, are not
19448 @node Kibozed Groups
19449 @subsection Kibozed Groups
19453 @dfn{Kibozing} is defined by the @acronym{OED} as ``grepping through
19454 (parts of) the news feed''. @code{nnkiboze} is a back end that will
19455 do this for you. Oh joy! Now you can grind any @acronym{NNTP} server
19456 down to a halt with useless requests! Oh happiness!
19458 @kindex G k (Group)
19459 To create a kibozed group, use the @kbd{G k} command in the group
19462 The address field of the @code{nnkiboze} method is, as with
19463 @code{nnvirtual}, a regexp to match groups to be ``included'' in the
19464 @code{nnkiboze} group. That's where most similarities between
19465 @code{nnkiboze} and @code{nnvirtual} end.
19467 In addition to this regexp detailing component groups, an
19468 @code{nnkiboze} group must have a score file to say what articles are
19469 to be included in the group (@pxref{Scoring}).
19471 @kindex M-x nnkiboze-generate-groups
19472 @findex nnkiboze-generate-groups
19473 You must run @kbd{M-x nnkiboze-generate-groups} after creating the
19474 @code{nnkiboze} groups you want to have. This command will take time.
19475 Lots of time. Oodles and oodles of time. Gnus has to fetch the
19476 headers from all the articles in all the component groups and run them
19477 through the scoring process to determine if there are any articles in
19478 the groups that are to be part of the @code{nnkiboze} groups.
19480 Please limit the number of component groups by using restrictive
19481 regexps. Otherwise your sysadmin may become annoyed with you, and the
19482 @acronym{NNTP} site may throw you off and never let you back in again.
19483 Stranger things have happened.
19485 @code{nnkiboze} component groups do not have to be alive---they can be dead,
19486 and they can be foreign. No restrictions.
19488 @vindex nnkiboze-directory
19489 The generation of an @code{nnkiboze} group means writing two files in
19490 @code{nnkiboze-directory}, which is @file{~/News/kiboze/} by default.
19491 One contains the @acronym{NOV} header lines for all the articles in
19492 the group, and the other is an additional @file{.newsrc} file to store
19493 information on what groups have been searched through to find
19494 component articles.
19496 Articles marked as read in the @code{nnkiboze} group will have
19497 their @acronym{NOV} lines removed from the @acronym{NOV} file.
19500 @node Email Based Diary
19501 @section Email Based Diary
19503 @cindex email based diary
19506 This section describes a special mail back end called @code{nndiary},
19507 and its companion library @code{gnus-diary}. It is ``special'' in the
19508 sense that it is not meant to be one of the standard alternatives for
19509 reading mail with Gnus. See @ref{Choosing a Mail Back End} for that.
19510 Instead, it is used to treat @emph{some} of your mails in a special way,
19511 namely, as event reminders.
19513 Here is a typical scenario:
19517 You've got a date with Andy Mc Dowell or Bruce Willis (select according
19518 to your sexual preference) in one month. You don't want to forget it.
19520 So you send a ``reminder'' message (actually, a diary one) to yourself.
19522 You forget all about it and keep on getting and reading new mail, as usual.
19524 From time to time, as you type `g' in the group buffer and as the date
19525 is getting closer, the message will pop up again to remind you of your
19526 appointment, just as if it were new and unread.
19528 Read your ``new'' messages, this one included, and start dreaming again
19529 of the night you're gonna have.
19531 Once the date is over (you actually fell asleep just after dinner), the
19532 message will be automatically deleted if it is marked as expirable.
19535 The Gnus Diary back end has the ability to handle regular appointments
19536 (that wouldn't ever be deleted) as well as punctual ones, operates as a
19537 real mail back end and is configurable in many ways. All of this is
19538 explained in the sections below.
19541 * The NNDiary Back End:: Basic setup and usage.
19542 * The Gnus Diary Library:: Utility toolkit on top of nndiary.
19543 * Sending or Not Sending:: A final note on sending diary messages.
19547 @node The NNDiary Back End
19548 @subsection The NNDiary Back End
19550 @cindex the nndiary back end
19552 @code{nndiary} is a back end very similar to @code{nnml} (@pxref{Mail
19553 Spool}). Actually, it could appear as a mix of @code{nnml} and
19554 @code{nndraft}. If you know @code{nnml}, you're already familiar with
19555 the message storing scheme of @code{nndiary}: one file per message, one
19556 directory per group.
19558 Before anything, there is one requirement to be able to run
19559 @code{nndiary} properly: you @emph{must} use the group timestamp feature
19560 of Gnus. This adds a timestamp to each group's parameters. @ref{Group
19561 Timestamp} to see how it's done.
19564 * Diary Messages:: What makes a message valid for nndiary.
19565 * Running NNDiary:: NNDiary has two modes of operation.
19566 * Customizing NNDiary:: Bells and whistles.
19569 @node Diary Messages
19570 @subsubsection Diary Messages
19571 @cindex nndiary messages
19572 @cindex nndiary mails
19574 @code{nndiary} messages are just normal ones, except for the mandatory
19575 presence of 7 special headers. These headers are of the form
19576 @code{X-Diary-<something>}, @code{<something>} being one of
19577 @code{Minute}, @code{Hour}, @code{Dom}, @code{Month}, @code{Year},
19578 @code{Time-Zone} and @code{Dow}. @code{Dom} means ``Day of Month'', and
19579 @code{dow} means ``Day of Week''. These headers actually behave like
19580 crontab specifications and define the event date(s):
19584 For all headers except the @code{Time-Zone} one, a header value is
19585 either a star (meaning all possible values), or a list of fields
19586 (separated by a comma).
19588 A field is either an integer, or a range.
19590 A range is two integers separated by a dash.
19592 Possible integer values are 0--59 for @code{Minute}, 0--23 for
19593 @code{Hour}, 1--31 for @code{Dom}, 1--12 for @code{Month}, above 1971
19594 for @code{Year} and 0--6 for @code{Dow} (0 meaning Sunday).
19596 As a special case, a star in either @code{Dom} or @code{Dow} doesn't
19597 mean ``all possible values'', but ``use only the other field''. Note
19598 that if both are star'ed, the use of either one gives the same result.
19600 The @code{Time-Zone} header is special in that it can only have one
19601 value (@code{GMT}, for instance). A star doesn't mean ``all possible
19602 values'' (because it makes no sense), but ``the current local time
19603 zone''. Most of the time, you'll be using a star here. However, for a
19604 list of available time zone values, see the variable
19605 @code{nndiary-headers}.
19608 As a concrete example, here are the diary headers to add to your message
19609 for specifying ``Each Monday and each 1st of month, at 12:00, 20:00,
19610 21:00, 22:00, 23:00 and 24:00, from 1999 to 2010'' (I'll let you find
19615 X-Diary-Hour: 12, 20-24
19618 X-Diary-Year: 1999-2010
19620 X-Diary-Time-Zone: *
19623 @node Running NNDiary
19624 @subsubsection Running NNDiary
19625 @cindex running nndiary
19626 @cindex nndiary operation modes
19628 @code{nndiary} has two modes of operation: ``traditional'' (the default)
19629 and ``autonomous''. In traditional mode, @code{nndiary} does not get new
19630 mail by itself. You have to move (@kbd{B m}) or copy (@kbd{B c}) mails
19631 from your primary mail back end to nndiary groups in order to handle them
19632 as diary messages. In autonomous mode, @code{nndiary} retrieves its own
19633 mail and handles it independently from your primary mail back end.
19635 One should note that Gnus is not inherently designed to allow several
19636 ``master'' mail back ends at the same time. However, this does make
19637 sense with @code{nndiary}: you really want to send and receive diary
19638 messages to your diary groups directly. So, @code{nndiary} supports
19639 being sort of a ``second primary mail back end'' (to my knowledge, it is
19640 the only back end offering this feature). However, there is a limitation
19641 (which I hope to fix some day): respooling doesn't work in autonomous
19644 In order to use @code{nndiary} in autonomous mode, you have several
19649 Allow @code{nndiary} to retrieve new mail by itself. Put the following
19650 line in your @file{~/.gnus.el} file:
19653 (setq nndiary-get-new-mail t)
19656 You must arrange for diary messages (those containing @code{X-Diary-*}
19657 headers) to be split in a private folder @emph{before} Gnus treat them.
19658 Again, this is needed because Gnus cannot (yet ?) properly handle
19659 multiple primary mail back ends. Getting those messages from a separate
19660 source will compensate this misfeature to some extent.
19662 As an example, here's my procmailrc entry to store diary files in
19663 @file{~/.nndiary} (the default @code{nndiary} mail source file):
19672 Once this is done, you might want to customize the following two options
19673 that affect the diary mail retrieval and splitting processes:
19675 @defvar nndiary-mail-sources
19676 This is the diary-specific replacement for the standard
19677 @code{mail-sources} variable. It obeys the same syntax, and defaults to
19678 @code{(file :path "~/.nndiary")}.
19681 @defvar nndiary-split-methods
19682 This is the diary-specific replacement for the standard
19683 @code{nnmail-split-methods} variable. It obeys the same syntax.
19686 Finally, you may add a permanent @code{nndiary} virtual server
19687 (something like @code{(nndiary "diary")} should do) to your
19688 @code{gnus-secondary-select-methods}.
19690 Hopefully, almost everything (see the TODO section in
19691 @file{nndiary.el}) will work as expected when you restart Gnus: in
19692 autonomous mode, typing @kbd{g} and @kbd{M-g} in the group buffer, will
19693 also get your new diary mails and split them according to your
19694 diary-specific rules, @kbd{F} will find your new diary groups etc.
19696 @node Customizing NNDiary
19697 @subsubsection Customizing NNDiary
19698 @cindex customizing nndiary
19699 @cindex nndiary customization
19701 Now that @code{nndiary} is up and running, it's time to customize it.
19702 The custom group is called @code{nndiary} (no, really ?!). You should
19703 browse it to figure out which options you'd like to tweak. The following
19704 two variables are probably the only ones you will want to change:
19706 @defvar nndiary-reminders
19707 This is the list of times when you want to be reminded of your
19708 appointments (e.g. 3 weeks before, then 2 days before, then 1 hour
19709 before and that's it). Remember that ``being reminded'' means that the
19710 diary message will pop up as brand new and unread again when you get new
19714 @defvar nndiary-week-starts-on-monday
19715 Rather self-explanatory. Otherwise, Sunday is assumed (this is the
19720 @node The Gnus Diary Library
19721 @subsection The Gnus Diary Library
19723 @cindex the gnus diary library
19725 Using @code{nndiary} manually (I mean, writing the headers by hand and
19726 so on) would be rather boring. Fortunately, there is a library called
19727 @code{gnus-diary} written on top of @code{nndiary}, that does many
19728 useful things for you.
19730 In order to use it, add the following line to your @file{~/.gnus.el} file:
19733 (require 'gnus-diary)
19736 Also, you shouldn't use any @code{gnus-user-format-function-[d|D]}
19737 (@pxref{Summary Buffer Lines}). @code{gnus-diary} provides both of these
19738 (sorry if you used them before).
19742 * Diary Summary Line Format:: A nicer summary buffer line format.
19743 * Diary Articles Sorting:: A nicer way to sort messages.
19744 * Diary Headers Generation:: Not doing it manually.
19745 * Diary Group Parameters:: Not handling them manually.
19748 @node Diary Summary Line Format
19749 @subsubsection Diary Summary Line Format
19750 @cindex diary summary buffer line
19751 @cindex diary summary line format
19753 Displaying diary messages in standard summary line format (usually
19754 something like @samp{From Joe: Subject}) is pretty useless. Most of
19755 the time, you're the one who wrote the message, and you mostly want to
19756 see the event's date.
19758 @code{gnus-diary} provides two supplemental user formats to be used in
19759 summary line formats. @code{D} corresponds to a formatted time string
19760 for the next occurrence of the event (e.g. ``Sat, Sep 22 01, 12:00''),
19761 while @code{d} corresponds to an approximative remaining time until the
19762 next occurrence of the event (e.g. ``in 6 months, 1 week'').
19764 For example, here's how Joe's birthday is displayed in my
19765 @code{nndiary+diary:birthdays} summary buffer (note that the message is
19766 expirable, but will never be deleted, as it specifies a periodic event):
19769 E Sat, Sep 22 01, 12:00: Joe's birthday (in 6 months, 1 week)
19772 In order to get something like the above, you would normally add the
19773 following line to your diary groups'parameters:
19776 (gnus-summary-line-format "%U%R%z %uD: %(%s%) (%ud)\n")
19779 However, @code{gnus-diary} does it automatically (@pxref{Diary Group
19780 Parameters}). You can however customize the provided summary line format
19781 with the following user options:
19783 @defvar gnus-diary-summary-line-format
19784 Defines the summary line format used for diary groups (@pxref{Summary
19785 Buffer Lines}). @code{gnus-diary} uses it to automatically update the
19786 diary groups'parameters.
19789 @defvar gnus-diary-time-format
19790 Defines the format to display dates in diary summary buffers. This is
19791 used by the @code{D} user format. See the docstring for details.
19794 @defvar gnus-diary-delay-format-function
19795 Defines the format function to use for displaying delays (remaining
19796 times) in diary summary buffers. This is used by the @code{d} user
19797 format. There are currently built-in functions for English and French;
19798 you can also define your own. See the docstring for details.
19801 @node Diary Articles Sorting
19802 @subsubsection Diary Articles Sorting
19803 @cindex diary articles sorting
19804 @cindex diary summary lines sorting
19805 @findex gnus-summary-sort-by-schedule
19806 @findex gnus-thread-sort-by-schedule
19807 @findex gnus-article-sort-by-schedule
19809 @code{gnus-diary} provides new sorting functions (@pxref{Sorting the
19810 Summary Buffer} ) called @code{gnus-summary-sort-by-schedule},
19811 @code{gnus-thread-sort-by-schedule} and
19812 @code{gnus-article-sort-by-schedule}. These functions let you organize
19813 your diary summary buffers from the closest event to the farthest one.
19815 @code{gnus-diary} automatically installs
19816 @code{gnus-summary-sort-by-schedule} as a menu item in the summary
19817 buffer's ``sort'' menu, and the two others as the primary (hence
19818 default) sorting functions in the group parameters (@pxref{Diary Group
19821 @node Diary Headers Generation
19822 @subsubsection Diary Headers Generation
19823 @cindex diary headers generation
19824 @findex gnus-diary-check-message
19826 @code{gnus-diary} provides a function called
19827 @code{gnus-diary-check-message} to help you handle the @code{X-Diary-*}
19828 headers. This function ensures that the current message contains all the
19829 required diary headers, and prompts you for values or corrections if
19832 This function is hooked into the @code{nndiary} back end, so that
19833 moving or copying an article to a diary group will trigger it
19834 automatically. It is also bound to @kbd{C-c C-f d} in
19835 @code{message-mode} and @code{article-edit-mode} in order to ease the
19836 process of converting a usual mail to a diary one.
19838 This function takes a prefix argument which will force prompting of
19839 all diary headers, regardless of their presence or validity. That way,
19840 you can very easily reschedule an already valid diary message, for
19843 @node Diary Group Parameters
19844 @subsubsection Diary Group Parameters
19845 @cindex diary group parameters
19847 When you create a new diary group, or visit one, @code{gnus-diary}
19848 automatically checks your group parameters and if needed, sets the
19849 summary line format to the diary-specific value, installs the
19850 diary-specific sorting functions, and also adds the different
19851 @code{X-Diary-*} headers to the group's posting-style. It is then easier
19852 to send a diary message, because if you use @kbd{C-u a} or @kbd{C-u m}
19853 on a diary group to prepare a message, these headers will be inserted
19854 automatically (although not filled with proper values yet).
19856 @node Sending or Not Sending
19857 @subsection Sending or Not Sending
19859 Well, assuming you've read all of the above, here are two final notes on
19860 mail sending with @code{nndiary}:
19864 @code{nndiary} is a @emph{real} mail back end. You really send real diary
19865 messsages for real. This means for instance that you can give
19866 appointments to anybody (provided they use Gnus and @code{nndiary}) by
19867 sending the diary message to them as well.
19869 However, since @code{nndiary} also has a @code{request-post} method, you
19870 can also use @kbd{C-u a} instead of @kbd{C-u m} on a diary group and the
19871 message won't actually be sent; just stored locally in the group. This
19872 comes in very handy for private appointments.
19875 @node Gnus Unplugged
19876 @section Gnus Unplugged
19881 @cindex Gnus unplugged
19883 In olden times (ca. February '88), people used to run their newsreaders
19884 on big machines with permanent connections to the net. News transport
19885 was dealt with by news servers, and all the newsreaders had to do was to
19886 read news. Believe it or not.
19888 Nowadays most people read news and mail at home, and use some sort of
19889 modem to connect to the net. To avoid running up huge phone bills, it
19890 would be nice to have a way to slurp down all the news and mail, hang up
19891 the phone, read for several hours, and then upload any responses you
19892 have to make. And then you repeat the procedure.
19894 Of course, you can use news servers for doing this as well. I've used
19895 @code{inn} together with @code{slurp}, @code{pop} and @code{sendmail}
19896 for some years, but doing that's a bore. Moving the news server
19897 functionality up to the newsreader makes sense if you're the only person
19898 reading news on a machine.
19900 Setting up Gnus as an ``offline'' newsreader is quite simple. In
19901 fact, you don't have to configure anything as the agent is now enabled
19902 by default (@pxref{Agent Variables, gnus-agent}).
19904 Of course, to use it as such, you have to learn a few new commands.
19907 * Agent Basics:: How it all is supposed to work.
19908 * Agent Categories:: How to tell the Gnus Agent what to download.
19909 * Agent Commands:: New commands for all the buffers.
19910 * Agent Visuals:: Ways that the agent may effect your summary buffer.
19911 * Agent as Cache:: The Agent is a big cache too.
19912 * Agent Expiry:: How to make old articles go away.
19913 * Agent Regeneration:: How to recover from lost connections and other accidents.
19914 * Agent and flags:: How the Agent maintains flags.
19915 * Agent and IMAP:: How to use the Agent with @acronym{IMAP}.
19916 * Outgoing Messages:: What happens when you post/mail something?
19917 * Agent Variables:: Customizing is fun.
19918 * Example Setup:: An example @file{~/.gnus.el} file for offline people.
19919 * Batching Agents:: How to fetch news from a @code{cron} job.
19920 * Agent Caveats:: What you think it'll do and what it does.
19925 @subsection Agent Basics
19927 First, let's get some terminology out of the way.
19929 The Gnus Agent is said to be @dfn{unplugged} when you have severed the
19930 connection to the net (and notified the Agent that this is the case).
19931 When the connection to the net is up again (and Gnus knows this), the
19932 Agent is @dfn{plugged}.
19934 The @dfn{local} machine is the one you're running on, and which isn't
19935 connected to the net continuously.
19937 @dfn{Downloading} means fetching things from the net to your local
19938 machine. @dfn{Uploading} is doing the opposite.
19940 You know that Gnus gives you all the opportunity you'd ever want for
19941 shooting yourself in the foot. Some people call it flexibility. Gnus
19942 is also customizable to a great extent, which means that the user has a
19943 say on how Gnus behaves. Other newsreaders might unconditionally shoot
19944 you in your foot, but with Gnus, you have a choice!
19946 Gnus is never really in plugged or unplugged state. Rather, it applies
19947 that state to each server individually. This means that some servers
19948 can be plugged while others can be unplugged. Additionally, some
19949 servers can be ignored by the Agent altogether (which means that
19950 they're kinda like plugged always).
19952 So when you unplug the Agent and then wonder why is Gnus opening a
19953 connection to the Net, the next step to do is to look whether all
19954 servers are agentized. If there is an unagentized server, you found
19957 Another thing is the @dfn{offline} state. Sometimes, servers aren't
19958 reachable. When Gnus notices this, it asks you whether you want the
19959 server to be switched to offline state. If you say yes, then the
19960 server will behave somewhat as if it was unplugged, except that Gnus
19961 will ask you whether you want to switch it back online again.
19963 Let's take a typical Gnus session using the Agent.
19968 @findex gnus-unplugged
19969 You start Gnus with @code{gnus-unplugged}. This brings up the Gnus
19970 Agent in a disconnected state. You can read all the news that you have
19971 already fetched while in this mode.
19974 You then decide to see whether any new news has arrived. You connect
19975 your machine to the net (using PPP or whatever), and then hit @kbd{J j}
19976 to make Gnus become @dfn{plugged} and use @kbd{g} to check for new mail
19977 as usual. To check for new mail in unplugged mode (@pxref{Mail
19978 Source Specifiers}).
19981 You can then read the new news immediately, or you can download the
19982 news onto your local machine. If you want to do the latter, you press
19983 @kbd{g} to check if there are any new news and then @kbd{J s} to fetch
19984 all the eligible articles in all the groups. (To let Gnus know which
19985 articles you want to download, @pxref{Agent Categories}).
19988 After fetching the articles, you press @kbd{J j} to make Gnus become
19989 unplugged again, and you shut down the PPP thing (or whatever). And
19990 then you read the news offline.
19993 And then you go to step 2.
19996 Here are some things you should do the first time (or so) that you use
20002 Decide which servers should be covered by the Agent. If you have a mail
20003 back end, it would probably be nonsensical to have it covered by the
20004 Agent. Go to the server buffer (@kbd{^} in the group buffer) and press
20005 @kbd{J a} on the server (or servers) that you wish to have covered by the
20006 Agent (@pxref{Server Agent Commands}), or @kbd{J r} on automatically
20007 added servers you do not wish to have covered by the Agent. By default,
20008 all @code{nntp} and @code{nnimap} servers in @code{gnus-select-method} and
20009 @code{gnus-secondary-select-methods} are agentized.
20012 Decide on download policy. It's fairly simple once you decide whether
20013 you are going to use agent categories, topic parameters, and/or group
20014 parameters to implement your policy. If you're new to gnus, it
20015 is probably best to start with a category, @xref{Agent Categories}.
20017 Both topic parameters (@pxref{Topic Parameters}) and agent categories
20018 (@pxref{Agent Categories}) provide for setting a policy that applies
20019 to multiple groups. Which you use is entirely up to you. Topic
20020 parameters do override categories so, if you mix the two, you'll have
20021 to take that into account. If you have a few groups that deviate from
20022 your policy, you can use group parameters (@pxref{Group Parameters}) to
20026 Uhm@dots{} that's it.
20030 @node Agent Categories
20031 @subsection Agent Categories
20033 One of the main reasons to integrate the news transport layer into the
20034 newsreader is to allow greater control over what articles to download.
20035 There's not much point in downloading huge amounts of articles, just to
20036 find out that you're not interested in reading any of them. It's better
20037 to be somewhat more conservative in choosing what to download, and then
20038 mark the articles for downloading manually if it should turn out that
20039 you're interested in the articles anyway.
20041 One of the more effective methods for controlling what is to be
20042 downloaded is to create a @dfn{category} and then assign some (or all)
20043 groups to this category. Groups that do not belong in any other
20044 category belong to the @code{default} category. Gnus has its own
20045 buffer for creating and managing categories.
20047 If you prefer, you can also use group parameters (@pxref{Group
20048 Parameters}) and topic parameters (@pxref{Topic Parameters}) for an
20049 alternative approach to controlling the agent. The only real
20050 difference is that categories are specific to the agent (so there is
20051 less to learn) while group and topic parameters include the kitchen
20054 Since you can set agent parameters in several different places we have
20055 a rule to decide which source to believe. This rule specifies that
20056 the parameter sources are checked in the following order: group
20057 parameters, topic parameters, agent category, and finally customizable
20058 variables. So you can mix all of these sources to produce a wide range
20059 of behavior, just don't blame me if you don't remember where you put
20063 * Category Syntax:: What a category looks like.
20064 * Category Buffer:: A buffer for maintaining categories.
20065 * Category Variables:: Customize'r'Us.
20069 @node Category Syntax
20070 @subsubsection Category Syntax
20072 A category consists of a name, the list of groups belonging to the
20073 category, and a number of optional parameters that override the
20074 customizable variables. The complete list of agent parameters are
20077 @cindex Agent Parameters
20080 The list of groups that are in this category.
20082 @item agent-predicate
20083 A predicate which (generally) gives a rough outline of which articles
20084 are eligible for downloading; and
20087 a score rule which (generally) gives you a finer granularity when
20088 deciding what articles to download. (Note that this @dfn{download
20089 score} is not necessarily related to normal scores.)
20091 @item agent-enable-expiration
20092 a boolean indicating whether the agent should expire old articles in
20093 this group. Most groups should be expired to conserve disk space. In
20094 fact, its probably safe to say that the gnus.* hierarchy contains the
20095 only groups that should not be expired.
20097 @item agent-days-until-old
20098 an integer indicating the number of days that the agent should wait
20099 before deciding that a read article is safe to expire.
20101 @item agent-low-score
20102 an integer that overrides the value of @code{gnus-agent-low-score}.
20104 @item agent-high-score
20105 an integer that overrides the value of @code{gnus-agent-high-score}.
20107 @item agent-short-article
20108 an integer that overrides the value of
20109 @code{gnus-agent-short-article}.
20111 @item agent-long-article
20112 an integer that overrides the value of @code{gnus-agent-long-article}.
20114 @item agent-enable-undownloaded-faces
20115 a symbol indicating whether the summary buffer should display
20116 undownloaded articles using the @code{gnus-summary-*-undownloaded-face}
20117 faces. Any symbol other than @code{nil} will enable the use of
20118 undownloaded faces.
20121 The name of a category can not be changed once the category has been
20124 Each category maintains a list of groups that are exclusive members of
20125 that category. The exclusivity rule is automatically enforced, add a
20126 group to a new category and it is automatically removed from its old
20129 A predicate in its simplest form can be a single predicate such as
20130 @code{true} or @code{false}. These two will download every available
20131 article or nothing respectively. In the case of these two special
20132 predicates an additional score rule is superfluous.
20134 Predicates of @code{high} or @code{low} download articles in respect of
20135 their scores in relationship to @code{gnus-agent-high-score} and
20136 @code{gnus-agent-low-score} as described below.
20138 To gain even finer control of what is to be regarded eligible for
20139 download a predicate can consist of a number of predicates with logical
20140 operators sprinkled in between.
20142 Perhaps some examples are in order.
20144 Here's a simple predicate. (It's the default predicate, in fact, used
20145 for all groups that don't belong to any other category.)
20151 Quite simple, eh? This predicate is true if and only if the article is
20152 short (for some value of ``short'').
20154 Here's a more complex predicate:
20163 This means that an article should be downloaded if it has a high score,
20164 or if the score is not low and the article is not long. You get the
20167 The available logical operators are @code{or}, @code{and} and
20168 @code{not}. (If you prefer, you can use the more ``C''-ish operators
20169 @samp{|}, @code{&} and @code{!} instead.)
20171 The following predicates are pre-defined, but if none of these fit what
20172 you want to do, you can write your own.
20174 When evaluating each of these predicates, the named constant will be
20175 bound to the value determined by calling
20176 @code{gnus-agent-find-parameter} on the appropriate parameter. For
20177 example, gnus-agent-short-article will be bound to
20178 @code{(gnus-agent-find-parameter group 'agent-short-article)}. This
20179 means that you can specify a predicate in your category then tune that
20180 predicate to individual groups.
20184 True if the article is shorter than @code{gnus-agent-short-article}
20185 lines; default 100.
20188 True if the article is longer than @code{gnus-agent-long-article}
20189 lines; default 200.
20192 True if the article has a download score less than
20193 @code{gnus-agent-low-score}; default 0.
20196 True if the article has a download score greater than
20197 @code{gnus-agent-high-score}; default 0.
20200 True if the Gnus Agent guesses that the article is spam. The
20201 heuristics may change over time, but at present it just computes a
20202 checksum and sees whether articles match.
20211 If you want to create your own predicate function, here's what you have
20212 to know: The functions are called with no parameters, but the
20213 @code{gnus-headers} and @code{gnus-score} dynamic variables are bound to
20216 For example, you could decide that you don't want to download articles
20217 that were posted more than a certain number of days ago (e.g. posted
20218 more than @code{gnus-agent-expire-days} ago) you might write a function
20219 something along the lines of the following:
20222 (defun my-article-old-p ()
20223 "Say whether an article is old."
20224 (< (time-to-days (date-to-time (mail-header-date gnus-headers)))
20225 (- (time-to-days (current-time)) gnus-agent-expire-days)))
20228 with the predicate then defined as:
20231 (not my-article-old-p)
20234 or you could append your predicate to the predefined
20235 @code{gnus-category-predicate-alist} in your @file{~/.gnus.el} or
20239 (require 'gnus-agent)
20240 (setq gnus-category-predicate-alist
20241 (append gnus-category-predicate-alist
20242 '((old . my-article-old-p))))
20245 and simply specify your predicate as:
20251 If/when using something like the above, be aware that there are many
20252 misconfigured systems/mailers out there and so an article's date is not
20253 always a reliable indication of when it was posted. Hell, some people
20254 just don't give a damn.
20256 The above predicates apply to @emph{all} the groups which belong to the
20257 category. However, if you wish to have a specific predicate for an
20258 individual group within a category, or you're just too lazy to set up a
20259 new category, you can enter a group's individual predicate in its group
20260 parameters like so:
20263 (agent-predicate . short)
20266 This is the group/topic parameter equivalent of the agent category default.
20267 Note that when specifying a single word predicate like this, the
20268 @code{agent-predicate} specification must be in dotted pair notation.
20270 The equivalent of the longer example from above would be:
20273 (agent-predicate or high (and (not low) (not long)))
20276 The outer parenthesis required in the category specification are not
20277 entered here as, not being in dotted pair notation, the value of the
20278 predicate is assumed to be a list.
20281 Now, the syntax of the download score is the same as the syntax of
20282 normal score files, except that all elements that require actually
20283 seeing the article itself are verboten. This means that only the
20284 following headers can be scored on: @code{Subject}, @code{From},
20285 @code{Date}, @code{Message-ID}, @code{References}, @code{Chars},
20286 @code{Lines}, and @code{Xref}.
20288 As with predicates, the specification of the @code{download score rule}
20289 to use in respect of a group can be in either the category definition if
20290 it's to be applicable to all groups in therein, or a group's parameters
20291 if it's to be specific to that group.
20293 In both of these places the @code{download score rule} can take one of
20300 This has the same syntax as a normal Gnus score file except only a
20301 subset of scoring keywords are available as mentioned above.
20307 Category specification
20311 ("Lars Ingebrigtsen" 1000000 nil s))
20317 Group/Topic Parameter specification
20320 (agent-score ("from"
20321 ("Lars Ingebrigtsen" 1000000 nil s))
20326 Again, note the omission of the outermost parenthesis here.
20332 These score files must @emph{only} contain the permitted scoring
20333 keywords stated above.
20339 Category specification
20342 ("~/News/agent.SCORE")
20348 ("~/News/agent.SCORE" "~/News/agent.group.SCORE")
20352 Group Parameter specification
20355 (agent-score "~/News/agent.SCORE")
20358 Additional score files can be specified as above. Need I say anything
20363 Use @code{normal} score files
20365 If you don't want to maintain two sets of scoring rules for a group, and
20366 your desired @code{downloading} criteria for a group are the same as your
20367 @code{reading} criteria then you can tell the agent to refer to your
20368 @code{normal} score files when deciding what to download.
20370 These directives in either the category definition or a group's
20371 parameters will cause the agent to read in all the applicable score
20372 files for a group, @emph{filtering out} those sections that do not
20373 relate to one of the permitted subset of scoring keywords.
20377 Category Specification
20384 Group Parameter specification
20387 (agent-score . file)
20392 @node Category Buffer
20393 @subsubsection Category Buffer
20395 You'd normally do all category maintenance from the category buffer.
20396 When you enter it for the first time (with the @kbd{J c} command from
20397 the group buffer), you'll only see the @code{default} category.
20399 The following commands are available in this buffer:
20403 @kindex q (Category)
20404 @findex gnus-category-exit
20405 Return to the group buffer (@code{gnus-category-exit}).
20408 @kindex e (Category)
20409 @findex gnus-category-customize-category
20410 Use a customization buffer to set all of the selected category's
20411 parameters at one time (@code{gnus-category-customize-category}).
20414 @kindex k (Category)
20415 @findex gnus-category-kill
20416 Kill the current category (@code{gnus-category-kill}).
20419 @kindex c (Category)
20420 @findex gnus-category-copy
20421 Copy the current category (@code{gnus-category-copy}).
20424 @kindex a (Category)
20425 @findex gnus-category-add
20426 Add a new category (@code{gnus-category-add}).
20429 @kindex p (Category)
20430 @findex gnus-category-edit-predicate
20431 Edit the predicate of the current category
20432 (@code{gnus-category-edit-predicate}).
20435 @kindex g (Category)
20436 @findex gnus-category-edit-groups
20437 Edit the list of groups belonging to the current category
20438 (@code{gnus-category-edit-groups}).
20441 @kindex s (Category)
20442 @findex gnus-category-edit-score
20443 Edit the download score rule of the current category
20444 (@code{gnus-category-edit-score}).
20447 @kindex l (Category)
20448 @findex gnus-category-list
20449 List all the categories (@code{gnus-category-list}).
20453 @node Category Variables
20454 @subsubsection Category Variables
20457 @item gnus-category-mode-hook
20458 @vindex gnus-category-mode-hook
20459 Hook run in category buffers.
20461 @item gnus-category-line-format
20462 @vindex gnus-category-line-format
20463 Format of the lines in the category buffer (@pxref{Formatting
20464 Variables}). Valid elements are:
20468 The name of the category.
20471 The number of groups in the category.
20474 @item gnus-category-mode-line-format
20475 @vindex gnus-category-mode-line-format
20476 Format of the category mode line (@pxref{Mode Line Formatting}).
20478 @item gnus-agent-short-article
20479 @vindex gnus-agent-short-article
20480 Articles that have fewer lines than this are short. Default 100.
20482 @item gnus-agent-long-article
20483 @vindex gnus-agent-long-article
20484 Articles that have more lines than this are long. Default 200.
20486 @item gnus-agent-low-score
20487 @vindex gnus-agent-low-score
20488 Articles that have a score lower than this have a low score. Default
20491 @item gnus-agent-high-score
20492 @vindex gnus-agent-high-score
20493 Articles that have a score higher than this have a high score. Default
20496 @item gnus-agent-expire-days
20497 @vindex gnus-agent-expire-days
20498 The number of days that a @samp{read} article must stay in the agent's
20499 local disk before becoming eligible for expiration (While the name is
20500 the same, this doesn't mean expiring the article on the server. It
20501 just means deleting the local copy of the article). What is also
20502 important to understand is that the counter starts with the time the
20503 article was written to the local disk and not the time the article was
20507 @item gnus-agent-enable-expiration
20508 @vindex gnus-agent-enable-expiration
20509 Determines whether articles in a group are, by default, expired or
20510 retained indefinitely. The default is @code{ENABLE} which means that
20511 you'll have to disable expiration when desired. On the other hand,
20512 you could set this to @code{DISABLE}. In that case, you would then
20513 have to enable expiration in selected groups.
20518 @node Agent Commands
20519 @subsection Agent Commands
20520 @findex gnus-agent-toggle-plugged
20521 @kindex J j (Agent)
20523 All the Gnus Agent commands are on the @kbd{J} submap. The @kbd{J j}
20524 (@code{gnus-agent-toggle-plugged}) command works in all modes, and
20525 toggles the plugged/unplugged state of the Gnus Agent.
20529 * Group Agent Commands:: Configure groups and fetch their contents.
20530 * Summary Agent Commands:: Manually select then fetch specific articles.
20531 * Server Agent Commands:: Select the servers that are supported by the agent.
20537 @node Group Agent Commands
20538 @subsubsection Group Agent Commands
20542 @kindex J u (Agent Group)
20543 @findex gnus-agent-fetch-groups
20544 Fetch all eligible articles in the current group
20545 (@code{gnus-agent-fetch-groups}).
20548 @kindex J c (Agent Group)
20549 @findex gnus-enter-category-buffer
20550 Enter the Agent category buffer (@code{gnus-enter-category-buffer}).
20553 @kindex J s (Agent Group)
20554 @findex gnus-agent-fetch-session
20555 Fetch all eligible articles in all groups
20556 (@code{gnus-agent-fetch-session}).
20559 @kindex J S (Agent Group)
20560 @findex gnus-group-send-queue
20561 Send all sendable messages in the queue group
20562 (@code{gnus-group-send-queue}). @xref{Drafts}.
20565 @kindex J a (Agent Group)
20566 @findex gnus-agent-add-group
20567 Add the current group to an Agent category
20568 (@code{gnus-agent-add-group}). This command understands the
20569 process/prefix convention (@pxref{Process/Prefix}).
20572 @kindex J r (Agent Group)
20573 @findex gnus-agent-remove-group
20574 Remove the current group from its category, if any
20575 (@code{gnus-agent-remove-group}). This command understands the
20576 process/prefix convention (@pxref{Process/Prefix}).
20579 @kindex J Y (Agent Group)
20580 @findex gnus-agent-synchronize-flags
20581 Synchronize flags changed while unplugged with remote server, if any.
20587 @node Summary Agent Commands
20588 @subsubsection Summary Agent Commands
20592 @kindex J # (Agent Summary)
20593 @findex gnus-agent-mark-article
20594 Mark the article for downloading (@code{gnus-agent-mark-article}).
20597 @kindex J M-# (Agent Summary)
20598 @findex gnus-agent-unmark-article
20599 Remove the downloading mark from the article
20600 (@code{gnus-agent-unmark-article}).
20604 @kindex @@ (Agent Summary)
20605 @findex gnus-agent-toggle-mark
20606 Toggle whether to download the article
20607 (@code{gnus-agent-toggle-mark}). The download mark is @samp{%} by
20611 @kindex J c (Agent Summary)
20612 @findex gnus-agent-catchup
20613 Mark all articles as read (@code{gnus-agent-catchup}) that are neither cached, downloaded, nor downloadable.
20616 @kindex J S (Agent Summary)
20617 @findex gnus-agent-fetch-group
20618 Download all eligible (@pxref{Agent Categories}) articles in this group.
20619 (@code{gnus-agent-fetch-group}).
20622 @kindex J s (Agent Summary)
20623 @findex gnus-agent-summary-fetch-series
20624 Download all processable articles in this group.
20625 (@code{gnus-agent-summary-fetch-series}).
20628 @kindex J u (Agent Summary)
20629 @findex gnus-agent-summary-fetch-group
20630 Download all downloadable articles in the current group
20631 (@code{gnus-agent-summary-fetch-group}).
20636 @node Server Agent Commands
20637 @subsubsection Server Agent Commands
20641 @kindex J a (Agent Server)
20642 @findex gnus-agent-add-server
20643 Add the current server to the list of servers covered by the Gnus Agent
20644 (@code{gnus-agent-add-server}).
20647 @kindex J r (Agent Server)
20648 @findex gnus-agent-remove-server
20649 Remove the current server from the list of servers covered by the Gnus
20650 Agent (@code{gnus-agent-remove-server}).
20655 @node Agent Visuals
20656 @subsection Agent Visuals
20658 If you open a summary while unplugged and, Gnus knows from the group's
20659 active range that there are more articles than the headers currently
20660 stored in the Agent, you may see some articles whose subject looks
20661 something like @samp{[Undownloaded article #####]}. These are
20662 placeholders for the missing headers. Aside from setting a mark,
20663 there is not much that can be done with one of these placeholders.
20664 When Gnus finally gets a chance to fetch the group's headers, the
20665 placeholders will automatically be replaced by the actual headers.
20666 You can configure the summary buffer's maneuvering to skip over the
20667 placeholders if you care (See @code{gnus-auto-goto-ignores}).
20669 While it may be obvious to all, the only headers and articles
20670 available while unplugged are those headers and articles that were
20671 fetched into the Agent while previously plugged. To put it another
20672 way, ``If you forget to fetch something while plugged, you might have a
20673 less than satisfying unplugged session''. For this reason, the Agent
20674 adds two visual effects to your summary buffer. These effects display
20675 the download status of each article so that you always know which
20676 articles will be available when unplugged.
20678 The first visual effect is the @samp{%O} spec. If you customize
20679 @code{gnus-summary-line-format} to include this specifier, you will add
20680 a single character field that indicates an article's download status.
20681 Articles that have been fetched into either the Agent or the Cache,
20682 will display @code{gnus-downloaded-mark} (defaults to @samp{+}). All
20683 other articles will display @code{gnus-undownloaded-mark} (defaults to
20684 @samp{-}). If you open a group that has not been agentized, a space
20685 (@samp{ }) will be displayed.
20687 The second visual effect are the undownloaded faces. The faces, there
20688 are three indicating the article's score (low, normal, high), seem to
20689 result in a love/hate response from many Gnus users. The problem is
20690 that the face selection is controlled by a list of condition tests and
20691 face names (See @code{gnus-summary-highlight}). Each condition is
20692 tested in the order in which it appears in the list so early
20693 conditions have precedence over later conditions. All of this means
20694 that, if you tick an undownloaded article, the article will continue
20695 to be displayed in the undownloaded face rather than the ticked face.
20697 If you use the Agent as a cache (to avoid downloading the same article
20698 each time you visit it or to minimize your connection time), the
20699 undownloaded face will probably seem like a good idea. The reason
20700 being that you do all of our work (marking, reading, deleting) with
20701 downloaded articles so the normal faces always appear. For those
20702 users using the agent to improve online performance by caching the NOV
20703 database (most users since 5.10.2), the undownloaded faces may appear
20704 to be an absolutely horrible idea. The issue being that, since none
20705 of their articles have been fetched into the Agent, all of the
20706 normal faces will be obscured by the undownloaded faces.
20708 If you would like to use the undownloaded faces, you must enable the
20709 undownloaded faces by setting the @code{agent-enable-undownloaded-faces}
20710 group parameter to @code{t}. This parameter, like all other agent
20711 parameters, may be set on an Agent Category (@pxref{Agent Categories}),
20712 a Group Topic (@pxref{Topic Parameters}), or an individual group
20713 (@pxref{Group Parameters}).
20715 The one problem common to all users using the agent is how quickly it
20716 can consume disk space. If you using the agent on many groups, it is
20717 even more difficult to effectively recover disk space. One solution
20718 is the @samp{%F} format available in @code{gnus-group-line-format}.
20719 This format will display the actual disk space used by articles
20720 fetched into both the agent and cache. By knowing which groups use
20721 the most space, users know where to focus their efforts when ``agent
20722 expiring'' articles.
20724 @node Agent as Cache
20725 @subsection Agent as Cache
20727 When Gnus is plugged, it is not efficient to download headers or
20728 articles from the server again, if they are already stored in the
20729 Agent. So, Gnus normally only downloads headers once, and stores them
20730 in the Agent. These headers are later used when generating the summary
20731 buffer, regardless of whether you are plugged or unplugged. Articles
20732 are not cached in the Agent by default though (that would potentially
20733 consume lots of disk space), but if you have already downloaded an
20734 article into the Agent, Gnus will not download the article from the
20735 server again but use the locally stored copy instead.
20737 If you so desire, you can configure the agent (see @code{gnus-agent-cache}
20738 @pxref{Agent Variables}) to always download headers and articles while
20739 plugged. Gnus will almost certainly be slower, but it will be kept
20740 synchronized with the server. That last point probably won't make any
20741 sense if you are using a nntp or nnimap back end.
20744 @subsection Agent Expiry
20746 @vindex gnus-agent-expire-days
20747 @findex gnus-agent-expire
20748 @kindex M-x gnus-agent-expire
20749 @kindex M-x gnus-agent-expire-group
20750 @findex gnus-agent-expire-group
20751 @cindex agent expiry
20752 @cindex Gnus agent expiry
20753 @cindex expiry, in Gnus agent
20755 The Agent back end, @code{nnagent}, doesn't handle expiry. Well, at
20756 least it doesn't handle it like other back ends. Instead, there are
20757 special @code{gnus-agent-expire} and @code{gnus-agent-expire-group}
20758 commands that will expire all read articles that are older than
20759 @code{gnus-agent-expire-days} days. They can be run whenever you feel
20760 that you're running out of space. Neither are particularly fast or
20761 efficient, and it's not a particularly good idea to interrupt them (with
20762 @kbd{C-g} or anything else) once you've started one of them.
20764 Note that other functions, e.g. @code{gnus-request-expire-articles},
20765 might run @code{gnus-agent-expire} for you to keep the agent
20766 synchronized with the group.
20768 The agent parameter @code{agent-enable-expiration} may be used to
20769 prevent expiration in selected groups.
20771 @vindex gnus-agent-expire-all
20772 If @code{gnus-agent-expire-all} is non-@code{nil}, the agent
20773 expiration commands will expire all articles---unread, read, ticked
20774 and dormant. If @code{nil} (which is the default), only read articles
20775 are eligible for expiry, and unread, ticked and dormant articles will
20776 be kept indefinitely.
20778 If you find that some articles eligible for expiry are never expired,
20779 perhaps some Gnus Agent files are corrupted. There's are special
20780 commands, @code{gnus-agent-regenerate} and
20781 @code{gnus-agent-regenerate-group}, to fix possible problems.
20783 @node Agent Regeneration
20784 @subsection Agent Regeneration
20786 @cindex agent regeneration
20787 @cindex Gnus agent regeneration
20788 @cindex regeneration
20790 The local data structures used by @code{nnagent} may become corrupted
20791 due to certain exceptional conditions. When this happens,
20792 @code{nnagent} functionality may degrade or even fail. The solution
20793 to this problem is to repair the local data structures by removing all
20794 internal inconsistencies.
20796 For example, if your connection to your server is lost while
20797 downloaded articles into the agent, the local data structures will not
20798 know about articles successfully downloaded prior to the connection
20799 failure. Running @code{gnus-agent-regenerate} or
20800 @code{gnus-agent-regenerate-group} will update the data structures
20801 such that you don't need to download these articles a second time.
20803 @findex gnus-agent-regenerate
20804 @kindex M-x gnus-agent-regenerate
20805 The command @code{gnus-agent-regenerate} will perform
20806 @code{gnus-agent-regenerate-group} on every agentized group. While
20807 you can run @code{gnus-agent-regenerate} in any buffer, it is strongly
20808 recommended that you first close all summary buffers.
20810 @findex gnus-agent-regenerate-group
20811 @kindex M-x gnus-agent-regenerate-group
20812 The command @code{gnus-agent-regenerate-group} uses the local copies
20813 of individual articles to repair the local @acronym{NOV}(header) database. It
20814 then updates the internal data structures that document which articles
20815 are stored locally. An optional argument will mark articles in the
20818 @node Agent and flags
20819 @subsection Agent and flags
20821 The Agent works with any Gnus back end including those, such as
20822 nnimap, that store flags (read, ticked, etc) on the server. Sadly,
20823 the Agent does not actually know which backends keep their flags in
20824 the backend server rather than in @file{.newsrc}. This means that the
20825 Agent, while unplugged or disconnected, will always record all changes
20826 to the flags in its own files.
20828 When you plug back in, Gnus will then check to see if you have any
20829 changed any flags and ask if you wish to synchronize these with the
20830 server. This behavior is customizable by @code{gnus-agent-synchronize-flags}.
20832 @vindex gnus-agent-synchronize-flags
20833 If @code{gnus-agent-synchronize-flags} is @code{nil}, the Agent will
20834 never automatically synchronize flags. If it is @code{ask}, which is
20835 the default, the Agent will check if you made any changes and if so
20836 ask if you wish to synchronize these when you re-connect. If it has
20837 any other value, all flags will be synchronized automatically.
20839 If you do not wish to synchronize flags automatically when you
20840 re-connect, you can do it manually with the
20841 @code{gnus-agent-synchronize-flags} command that is bound to @kbd{J Y}
20842 in the group buffer.
20844 Technical note: the synchronization algorithm does not work by ``pushing''
20845 all local flags to the server, but rather by incrementally updated the
20846 server view of flags by changing only those flags that were changed by
20847 the user. Thus, if you set one flag on an article, quit the group then
20848 re-select the group and remove the flag; the flag will be set and
20849 removed from the server when you ``synchronize''. The queued flag
20850 operations can be found in the per-server @code{flags} file in the Agent
20851 directory. It's emptied when you synchronize flags.
20853 @node Agent and IMAP
20854 @subsection Agent and IMAP
20856 The Agent works with any Gnus back end, including nnimap. However,
20857 since there are some conceptual differences between @acronym{NNTP} and
20858 @acronym{IMAP}, this section (should) provide you with some information to
20859 make Gnus Agent work smoother as a @acronym{IMAP} Disconnected Mode client.
20861 Some things are currently not implemented in the Agent that you'd might
20862 expect from a disconnected @acronym{IMAP} client, including:
20867 Copying/moving articles into nnimap groups when unplugged.
20870 Creating/deleting nnimap groups when unplugged.
20874 @node Outgoing Messages
20875 @subsection Outgoing Messages
20877 By default, when Gnus is unplugged, all outgoing messages (both mail
20878 and news) are stored in the draft group ``queue'' (@pxref{Drafts}).
20879 You can view them there after posting, and edit them at will.
20881 You can control the circumstances under which outgoing mail is queued
20882 (see @code{gnus-agent-queue-mail}, @pxref{Agent Variables}). Outgoing
20883 news is always queued when Gnus is unplugged, and never otherwise.
20885 You can send the messages either from the draft group with the special
20886 commands available there, or you can use the @kbd{J S} command in the
20887 group buffer to send all the sendable messages in the draft group.
20888 Posting news will only work when Gnus is plugged, but you can send
20891 If sending mail while unplugged does not work for you and you worry
20892 about hitting @kbd{J S} by accident when unplugged, you can have Gnus
20893 ask you to confirm your action (see
20894 @code{gnus-agent-prompt-send-queue}, @pxref{Agent Variables}).
20896 @node Agent Variables
20897 @subsection Agent Variables
20902 Is the agent enabled? The default is @code{t}. When first enabled,
20903 the agent will use @code{gnus-agent-auto-agentize-methods} to
20904 automatically mark some back ends as agentized. You may change which
20905 back ends are agentized using the agent commands in the server buffer.
20907 To enter the server buffer, use the @kbd{^}
20908 (@code{gnus-group-enter-server-mode}) command in the group buffer.
20911 @item gnus-agent-directory
20912 @vindex gnus-agent-directory
20913 Where the Gnus Agent will store its files. The default is
20914 @file{~/News/agent/}.
20916 @item gnus-agent-handle-level
20917 @vindex gnus-agent-handle-level
20918 Groups on levels (@pxref{Group Levels}) higher than this variable will
20919 be ignored by the Agent. The default is @code{gnus-level-subscribed},
20920 which means that only subscribed group will be considered by the Agent
20923 @item gnus-agent-plugged-hook
20924 @vindex gnus-agent-plugged-hook
20925 Hook run when connecting to the network.
20927 @item gnus-agent-unplugged-hook
20928 @vindex gnus-agent-unplugged-hook
20929 Hook run when disconnecting from the network.
20931 @item gnus-agent-fetched-hook
20932 @vindex gnus-agent-fetched-hook
20933 Hook run when finished fetching articles.
20935 @item gnus-agent-cache
20936 @vindex gnus-agent-cache
20937 Variable to control whether use the locally stored @acronym{NOV} and
20938 articles when plugged, e.g. essentially using the Agent as a cache.
20939 The default is non-@code{nil}, which means to use the Agent as a cache.
20941 @item gnus-agent-go-online
20942 @vindex gnus-agent-go-online
20943 If @code{gnus-agent-go-online} is @code{nil}, the Agent will never
20944 automatically switch offline servers into online status. If it is
20945 @code{ask}, the default, the Agent will ask if you wish to switch
20946 offline servers into online status when you re-connect. If it has any
20947 other value, all offline servers will be automatically switched into
20950 @item gnus-agent-mark-unread-after-downloaded
20951 @vindex gnus-agent-mark-unread-after-downloaded
20952 If @code{gnus-agent-mark-unread-after-downloaded} is non-@code{nil},
20953 mark articles as unread after downloading. This is usually a safe
20954 thing to do as the newly downloaded article has obviously not been
20955 read. The default is @code{t}.
20957 @item gnus-agent-synchronize-flags
20958 @vindex gnus-agent-synchronize-flags
20959 If @code{gnus-agent-synchronize-flags} is @code{nil}, the Agent will
20960 never automatically synchronize flags. If it is @code{ask}, which is
20961 the default, the Agent will check if you made any changes and if so
20962 ask if you wish to synchronize these when you re-connect. If it has
20963 any other value, all flags will be synchronized automatically.
20965 @item gnus-agent-consider-all-articles
20966 @vindex gnus-agent-consider-all-articles
20967 If @code{gnus-agent-consider-all-articles} is non-@code{nil}, the
20968 agent will let the agent predicate decide whether articles need to be
20969 downloaded or not, for all articles. When @code{nil}, the default,
20970 the agent will only let the predicate decide whether unread articles
20971 are downloaded or not. If you enable this, you may also want to look
20972 into the agent expiry settings (@pxref{Category Variables}), so that
20973 the agent doesn't download articles which the agent will later expire,
20974 over and over again.
20976 @item gnus-agent-max-fetch-size
20977 @vindex gnus-agent-max-fetch-size
20978 The agent fetches articles into a temporary buffer prior to parsing
20979 them into individual files. To avoid exceeding the max. buffer size,
20980 the agent alternates between fetching and parsing until all articles
20981 have been fetched. @code{gnus-agent-max-fetch-size} provides a size
20982 limit to control how often the cycling occurs. A large value improves
20983 performance. A small value minimizes the time lost should the
20984 connection be lost while fetching (You may need to run
20985 @code{gnus-agent-regenerate-group} to update the group's state.
20986 However, all articles parsed prior to loosing the connection will be
20987 available while unplugged). The default is 10M so it is unusual to
20990 @item gnus-server-unopen-status
20991 @vindex gnus-server-unopen-status
20992 Perhaps not an Agent variable, but closely related to the Agent, this
20993 variable says what will happen if Gnus cannot open a server. If the
20994 Agent is enabled, the default, @code{nil}, makes Gnus ask the user
20995 whether to deny the server or whether to unplug the agent. If the
20996 Agent is disabled, Gnus always simply deny the server. Other choices
20997 for this variable include @code{denied} and @code{offline} the latter
20998 is only valid if the Agent is used.
21000 @item gnus-auto-goto-ignores
21001 @vindex gnus-auto-goto-ignores
21002 Another variable that isn't an Agent variable, yet so closely related
21003 that most will look for it here, this variable tells the summary
21004 buffer how to maneuver around undownloaded (only headers stored in the
21005 agent) and unfetched (neither article nor headers stored) articles.
21007 The valid values are @code{nil} (maneuver to any article),
21008 @code{undownloaded} (maneuvering while unplugged ignores articles that
21009 have not been fetched), @code{always-undownloaded} (maneuvering always
21010 ignores articles that have not been fetched), @code{unfetched}
21011 (maneuvering ignores articles whose headers have not been fetched).
21013 @item gnus-agent-queue-mail
21014 @vindex gnus-agent-queue-mail
21015 When @code{gnus-agent-queue-mail} is @code{always}, Gnus will always
21016 queue mail rather than sending it straight away. When @code{t}, Gnus
21017 will queue mail when unplugged only. When @code{nil}, never queue
21018 mail. The default is @code{t}.
21020 @item gnus-agent-prompt-send-queue
21021 @vindex gnus-agent-prompt-send-queue
21022 When @code{gnus-agent-prompt-send-queue} is non-@code{nil} Gnus will
21023 prompt you to confirm that you really wish to proceed if you hit
21024 @kbd{J S} while unplugged. The default is @code{nil}.
21026 @item gnus-agent-auto-agentize-methods
21027 @vindex gnus-agent-auto-agentize-methods
21028 If you have never used the Agent before (or more technically, if
21029 @file{~/News/agent/lib/servers} does not exist), Gnus will
21030 automatically agentize a few servers for you. This variable control
21031 which back ends should be auto-agentized. It is typically only useful
21032 to agentize remote back ends. The auto-agentizing has the same effect
21033 as running @kbd{J a} on the servers (@pxref{Server Agent Commands}).
21034 If the file exist, you must manage the servers manually by adding or
21035 removing them, this variable is only applicable the first time you
21036 start Gnus. The default is @samp{(nntp nnimap)}.
21041 @node Example Setup
21042 @subsection Example Setup
21044 If you don't want to read this manual, and you have a fairly standard
21045 setup, you may be able to use something like the following as your
21046 @file{~/.gnus.el} file to get started.
21049 ;; @r{Define how Gnus is to fetch news. We do this over @acronym{NNTP}}
21050 ;; @r{from your ISP's server.}
21051 (setq gnus-select-method '(nntp "news.your-isp.com"))
21053 ;; @r{Define how Gnus is to read your mail. We read mail from}
21054 ;; @r{your ISP's @acronym{POP} server.}
21055 (setq mail-sources '((pop :server "pop.your-isp.com")))
21057 ;; @r{Say how Gnus is to store the mail. We use nnml groups.}
21058 (setq gnus-secondary-select-methods '((nnml "")))
21060 ;; @r{Make Gnus into an offline newsreader.}
21061 ;; (gnus-agentize) ; @r{The obsolete setting.}
21062 ;; (setq gnus-agent t) ; @r{Now the default.}
21065 That should be it, basically. Put that in your @file{~/.gnus.el} file,
21066 edit to suit your needs, start up PPP (or whatever), and type @kbd{M-x
21069 If this is the first time you've run Gnus, you will be subscribed
21070 automatically to a few default newsgroups. You'll probably want to
21071 subscribe to more groups, and to do that, you have to query the
21072 @acronym{NNTP} server for a complete list of groups with the @kbd{A A}
21073 command. This usually takes quite a while, but you only have to do it
21076 After reading and parsing a while, you'll be presented with a list of
21077 groups. Subscribe to the ones you want to read with the @kbd{u}
21078 command. @kbd{l} to make all the killed groups disappear after you've
21079 subscribe to all the groups you want to read. (@kbd{A k} will bring
21080 back all the killed groups.)
21082 You can now read the groups at once, or you can download the articles
21083 with the @kbd{J s} command. And then read the rest of this manual to
21084 find out which of the other gazillion things you want to customize.
21087 @node Batching Agents
21088 @subsection Batching Agents
21089 @findex gnus-agent-batch
21091 Having the Gnus Agent fetch articles (and post whatever messages you've
21092 written) is quite easy once you've gotten things set up properly. The
21093 following shell script will do everything that is necessary:
21095 You can run a complete batch command from the command line with the
21096 following incantation:
21100 emacs -batch -l ~/.emacs -l ~/.gnus.el -f gnus-agent-batch >/dev/null 2>&1
21104 @node Agent Caveats
21105 @subsection Agent Caveats
21107 The Gnus Agent doesn't seem to work like most other offline
21108 newsreaders. Here are some common questions that some imaginary people
21112 @item If I read an article while plugged, do they get entered into the Agent?
21114 @strong{No}. If you want this behavior, add
21115 @code{gnus-agent-fetch-selected-article} to
21116 @code{gnus-select-article-hook}.
21118 @item If I read an article while plugged, and the article already exists in
21119 the Agent, will it get downloaded once more?
21121 @strong{No}, unless @code{gnus-agent-cache} is @code{nil}.
21125 In short, when Gnus is unplugged, it only looks into the locally stored
21126 articles; when it's plugged, it talks to your ISP and may also use the
21127 locally stored articles.
21134 Other people use @dfn{kill files}, but we here at Gnus Towers like
21135 scoring better than killing, so we'd rather switch than fight. They do
21136 something completely different as well, so sit up straight and pay
21139 @vindex gnus-summary-mark-below
21140 All articles have a default score (@code{gnus-summary-default-score}),
21141 which is 0 by default. This score may be raised or lowered either
21142 interactively or by score files. Articles that have a score lower than
21143 @code{gnus-summary-mark-below} are marked as read.
21145 Gnus will read any @dfn{score files} that apply to the current group
21146 before generating the summary buffer.
21148 There are several commands in the summary buffer that insert score
21149 entries based on the current article. You can, for instance, ask Gnus to
21150 lower or increase the score of all articles with a certain subject.
21152 There are two sorts of scoring entries: Permanent and temporary.
21153 Temporary score entries are self-expiring entries. Any entries that are
21154 temporary and have not been used for, say, a week, will be removed
21155 silently to help keep the sizes of the score files down.
21158 * Summary Score Commands:: Adding score entries for the current group.
21159 * Group Score Commands:: General score commands.
21160 * Score Variables:: Customize your scoring. (My, what terminology).
21161 * Score File Format:: What a score file may contain.
21162 * Score File Editing:: You can edit score files by hand as well.
21163 * Adaptive Scoring:: Big Sister Gnus knows what you read.
21164 * Home Score File:: How to say where new score entries are to go.
21165 * Followups To Yourself:: Having Gnus notice when people answer you.
21166 * Scoring On Other Headers:: Scoring on non-standard headers.
21167 * Scoring Tips:: How to score effectively.
21168 * Reverse Scoring:: That problem child of old is not problem.
21169 * Global Score Files:: Earth-spanning, ear-splitting score files.
21170 * Kill Files:: They are still here, but they can be ignored.
21171 * Converting Kill Files:: Translating kill files to score files.
21172 * Advanced Scoring:: Using logical expressions to build score rules.
21173 * Score Decays:: It can be useful to let scores wither away.
21177 @node Summary Score Commands
21178 @section Summary Score Commands
21179 @cindex score commands
21181 The score commands that alter score entries do not actually modify real
21182 score files. That would be too inefficient. Gnus maintains a cache of
21183 previously loaded score files, one of which is considered the
21184 @dfn{current score file alist}. The score commands simply insert
21185 entries into this list, and upon group exit, this list is saved.
21187 The current score file is by default the group's local score file, even
21188 if no such score file actually exists. To insert score commands into
21189 some other score file (e.g. @file{all.SCORE}), you must first make this
21190 score file the current one.
21192 General score commands that don't actually change the score file:
21197 @kindex V s (Summary)
21198 @findex gnus-summary-set-score
21199 Set the score of the current article (@code{gnus-summary-set-score}).
21202 @kindex V S (Summary)
21203 @findex gnus-summary-current-score
21204 Display the score of the current article
21205 (@code{gnus-summary-current-score}).
21208 @kindex V t (Summary)
21209 @findex gnus-score-find-trace
21210 Display all score rules that have been used on the current article
21211 (@code{gnus-score-find-trace}). In the @code{*Score Trace*} buffer, you
21212 may type @kbd{e} to edit score file corresponding to the score rule on
21213 current line and @kbd{f} to format (@code{gnus-score-pretty-print}) the
21214 score file and edit it.
21217 @kindex V w (Summary)
21218 @findex gnus-score-find-favourite-words
21219 List words used in scoring (@code{gnus-score-find-favourite-words}).
21222 @kindex V R (Summary)
21223 @findex gnus-summary-rescore
21224 Run the current summary through the scoring process
21225 (@code{gnus-summary-rescore}). This might be useful if you're playing
21226 around with your score files behind Gnus' back and want to see the
21227 effect you're having.
21230 @kindex V c (Summary)
21231 @findex gnus-score-change-score-file
21232 Make a different score file the current
21233 (@code{gnus-score-change-score-file}).
21236 @kindex V e (Summary)
21237 @findex gnus-score-edit-current-scores
21238 Edit the current score file (@code{gnus-score-edit-current-scores}).
21239 You will be popped into a @code{gnus-score-mode} buffer (@pxref{Score
21243 @kindex V f (Summary)
21244 @findex gnus-score-edit-file
21245 Edit a score file and make this score file the current one
21246 (@code{gnus-score-edit-file}).
21249 @kindex V F (Summary)
21250 @findex gnus-score-flush-cache
21251 Flush the score cache (@code{gnus-score-flush-cache}). This is useful
21252 after editing score files.
21255 @kindex V C (Summary)
21256 @findex gnus-score-customize
21257 Customize a score file in a visually pleasing manner
21258 (@code{gnus-score-customize}).
21262 The rest of these commands modify the local score file.
21267 @kindex V m (Summary)
21268 @findex gnus-score-set-mark-below
21269 Prompt for a score, and mark all articles with a score below this as
21270 read (@code{gnus-score-set-mark-below}).
21273 @kindex V x (Summary)
21274 @findex gnus-score-set-expunge-below
21275 Prompt for a score, and add a score rule to the current score file to
21276 expunge all articles below this score
21277 (@code{gnus-score-set-expunge-below}).
21280 The keystrokes for actually making score entries follow a very regular
21281 pattern, so there's no need to list all the commands. (Hundreds of
21284 @findex gnus-summary-increase-score
21285 @findex gnus-summary-lower-score
21289 The first key is either @kbd{I} (upper case i) for increasing the score
21290 or @kbd{L} for lowering the score.
21292 The second key says what header you want to score on. The following
21293 keys are available:
21297 Score on the author name.
21300 Score on the subject line.
21303 Score on the @code{Xref} line---i.e., the cross-posting line.
21306 Score on the @code{References} line.
21312 Score on the number of lines.
21315 Score on the @code{Message-ID} header.
21318 Score on an ``extra'' header, that is, one of those in gnus-extra-headers,
21319 if your @acronym{NNTP} server tracks additional header data in overviews.
21322 Score on followups---this matches the author name, and adds scores to
21323 the followups to this author. (Using this key leads to the creation of
21324 @file{ADAPT} files.)
21333 Score on thread. (Using this key leads to the creation of @file{ADAPT}
21339 The third key is the match type. Which match types are valid depends on
21340 what headers you are scoring on.
21352 Substring matching.
21355 Fuzzy matching (@pxref{Fuzzy Matching}).
21384 Greater than number.
21389 The fourth and usually final key says whether this is a temporary (i.e.,
21390 expiring) score entry, or a permanent (i.e., non-expiring) score entry,
21391 or whether it is to be done immediately, without adding to the score
21396 Temporary score entry.
21399 Permanent score entry.
21402 Immediately scoring.
21406 If you are scoring on `e' (extra) headers, you will then be prompted for
21407 the header name on which you wish to score. This must be a header named
21408 in gnus-extra-headers, and @samp{TAB} completion is available.
21412 So, let's say you want to increase the score on the current author with
21413 exact matching permanently: @kbd{I a e p}. If you want to lower the
21414 score based on the subject line, using substring matching, and make a
21415 temporary score entry: @kbd{L s s t}. Pretty easy.
21417 To make things a bit more complicated, there are shortcuts. If you use
21418 a capital letter on either the second or third keys, Gnus will use
21419 defaults for the remaining one or two keystrokes. The defaults are
21420 ``substring'' and ``temporary''. So @kbd{I A} is the same as @kbd{I a s
21421 t}, and @kbd{I a R} is the same as @kbd{I a r t}.
21423 These functions take both the numerical prefix and the symbolic prefix
21424 (@pxref{Symbolic Prefixes}). A numerical prefix says how much to lower
21425 (or increase) the score of the article. A symbolic prefix of @code{a}
21426 says to use the @file{all.SCORE} file for the command instead of the
21427 current score file.
21429 @vindex gnus-score-mimic-keymap
21430 The @code{gnus-score-mimic-keymap} says whether these commands will
21431 pretend they are keymaps or not.
21434 @node Group Score Commands
21435 @section Group Score Commands
21436 @cindex group score commands
21438 There aren't many of these as yet, I'm afraid.
21443 @kindex W e (Group)
21444 @findex gnus-score-edit-all-score
21445 Edit the apply-to-all-groups all.SCORE file. You will be popped into
21446 a @code{gnus-score-mode} buffer (@pxref{Score File Editing}).
21449 @kindex W f (Group)
21450 @findex gnus-score-flush-cache
21451 Gnus maintains a cache of score alists to avoid having to reload them
21452 all the time. This command will flush the cache
21453 (@code{gnus-score-flush-cache}).
21457 You can do scoring from the command line by saying something like:
21459 @findex gnus-batch-score
21460 @cindex batch scoring
21462 $ emacs -batch -l ~/.emacs -l ~/.gnus.el -f gnus-batch-score
21466 @node Score Variables
21467 @section Score Variables
21468 @cindex score variables
21472 @item gnus-use-scoring
21473 @vindex gnus-use-scoring
21474 If @code{nil}, Gnus will not check for score files, and will not, in
21475 general, do any score-related work. This is @code{t} by default.
21477 @item gnus-kill-killed
21478 @vindex gnus-kill-killed
21479 If this variable is @code{nil}, Gnus will never apply score files to
21480 articles that have already been through the kill process. While this
21481 may save you lots of time, it also means that if you apply a kill file
21482 to a group, and then change the kill file and want to run it over you
21483 group again to kill more articles, it won't work. You have to set this
21484 variable to @code{t} to do that. (It is @code{t} by default.)
21486 @item gnus-kill-files-directory
21487 @vindex gnus-kill-files-directory
21488 All kill and score files will be stored in this directory, which is
21489 initialized from the @env{SAVEDIR} environment variable by default.
21490 This is @file{~/News/} by default.
21492 @item gnus-score-file-suffix
21493 @vindex gnus-score-file-suffix
21494 Suffix to add to the group name to arrive at the score file name
21495 (@file{SCORE} by default.)
21497 @item gnus-score-uncacheable-files
21498 @vindex gnus-score-uncacheable-files
21499 @cindex score cache
21500 All score files are normally cached to avoid excessive re-loading of
21501 score files. However, this might make your Emacs grow big and
21502 bloated, so this regexp can be used to weed out score files unlikely
21503 to be needed again. It would be a bad idea to deny caching of
21504 @file{all.SCORE}, while it might be a good idea to not cache
21505 @file{comp.infosystems.www.authoring.misc.ADAPT}. In fact, this
21506 variable is @samp{ADAPT$} by default, so no adaptive score files will
21509 @item gnus-save-score
21510 @vindex gnus-save-score
21511 If you have really complicated score files, and do lots of batch
21512 scoring, then you might set this variable to @code{t}. This will make
21513 Gnus save the scores into the @file{.newsrc.eld} file.
21515 If you do not set this to @code{t}, then manual scores (like those set
21516 with @kbd{V s} (@code{gnus-summary-set-score})) will not be preserved
21517 across group visits.
21519 @item gnus-score-interactive-default-score
21520 @vindex gnus-score-interactive-default-score
21521 Score used by all the interactive raise/lower commands to raise/lower
21522 score with. Default is 1000, which may seem excessive, but this is to
21523 ensure that the adaptive scoring scheme gets enough room to play with.
21524 We don't want the small changes from the adaptive scoring to overwrite
21525 manually entered data.
21527 @item gnus-summary-default-score
21528 @vindex gnus-summary-default-score
21529 Default score of an article, which is 0 by default.
21531 @item gnus-summary-expunge-below
21532 @vindex gnus-summary-expunge-below
21533 Don't display the summary lines of articles that have scores lower than
21534 this variable. This is @code{nil} by default, which means that no
21535 articles will be hidden. This variable is local to the summary buffers,
21536 and has to be set from @code{gnus-summary-mode-hook}.
21538 @item gnus-score-over-mark
21539 @vindex gnus-score-over-mark
21540 Mark (in the third column) used for articles with a score over the
21541 default. Default is @samp{+}.
21543 @item gnus-score-below-mark
21544 @vindex gnus-score-below-mark
21545 Mark (in the third column) used for articles with a score below the
21546 default. Default is @samp{-}.
21548 @item gnus-score-find-score-files-function
21549 @vindex gnus-score-find-score-files-function
21550 Function used to find score files for the current group. This function
21551 is called with the name of the group as the argument.
21553 Predefined functions available are:
21556 @item gnus-score-find-single
21557 @findex gnus-score-find-single
21558 Only apply the group's own score file.
21560 @item gnus-score-find-bnews
21561 @findex gnus-score-find-bnews
21562 Apply all score files that match, using bnews syntax. This is the
21563 default. If the current group is @samp{gnu.emacs.gnus}, for instance,
21564 @file{all.emacs.all.SCORE}, @file{not.alt.all.SCORE} and
21565 @file{gnu.all.SCORE} would all apply. In short, the instances of
21566 @samp{all} in the score file names are translated into @samp{.*}, and
21567 then a regexp match is done.
21569 This means that if you have some score entries that you want to apply to
21570 all groups, then you put those entries in the @file{all.SCORE} file.
21572 The score files are applied in a semi-random order, although Gnus will
21573 try to apply the more general score files before the more specific score
21574 files. It does this by looking at the number of elements in the score
21575 file names---discarding the @samp{all} elements.
21577 @item gnus-score-find-hierarchical
21578 @findex gnus-score-find-hierarchical
21579 Apply all score files from all the parent groups. This means that you
21580 can't have score files like @file{all.SCORE}, but you can have
21581 @file{SCORE}, @file{comp.SCORE} and @file{comp.emacs.SCORE} for each
21585 This variable can also be a list of functions. In that case, all
21586 these functions will be called with the group name as argument, and
21587 all the returned lists of score files will be applied. These
21588 functions can also return lists of lists of score alists directly. In
21589 that case, the functions that return these non-file score alists
21590 should probably be placed before the ``real'' score file functions, to
21591 ensure that the last score file returned is the local score file.
21594 For example, to do hierarchical scoring but use a non-server-specific
21595 overall score file, you could use the value
21597 (list (lambda (group) ("all.SCORE"))
21598 'gnus-score-find-hierarchical)
21601 @item gnus-score-expiry-days
21602 @vindex gnus-score-expiry-days
21603 This variable says how many days should pass before an unused score file
21604 entry is expired. If this variable is @code{nil}, no score file entries
21605 are expired. It's 7 by default.
21607 @item gnus-update-score-entry-dates
21608 @vindex gnus-update-score-entry-dates
21609 If this variable is non-@code{nil}, temporary score entries that have
21610 been triggered (matched) will have their dates updated. (This is how Gnus
21611 controls expiry---all non-matched-entries will become too old while
21612 matched entries will stay fresh and young.) However, if you set this
21613 variable to @code{nil}, even matched entries will grow old and will
21614 have to face that oh-so grim reaper.
21616 @item gnus-score-after-write-file-function
21617 @vindex gnus-score-after-write-file-function
21618 Function called with the name of the score file just written.
21620 @item gnus-score-thread-simplify
21621 @vindex gnus-score-thread-simplify
21622 If this variable is non-@code{nil}, article subjects will be
21623 simplified for subject scoring purposes in the same manner as with
21624 threading---according to the current value of
21625 @code{gnus-simplify-subject-functions}. If the scoring entry uses
21626 @code{substring} or @code{exact} matching, the match will also be
21627 simplified in this manner.
21632 @node Score File Format
21633 @section Score File Format
21634 @cindex score file format
21636 A score file is an @code{emacs-lisp} file that normally contains just a
21637 single form. Casual users are not expected to edit these files;
21638 everything can be changed from the summary buffer.
21640 Anyway, if you'd like to dig into it yourself, here's an example:
21644 ("Lars Ingebrigtsen" -10000)
21646 ("larsi\\|lmi" -50000 nil R))
21648 ("Ding is Badd" nil 728373))
21650 ("alt.politics" -1000 728372 s))
21655 (mark-and-expunge -10)
21659 (files "/hom/larsi/News/gnu.SCORE")
21660 (exclude-files "all.SCORE")
21661 (local (gnus-newsgroup-auto-expire t)
21662 (gnus-summary-make-false-root empty))
21666 This example demonstrates most score file elements. @xref{Advanced
21667 Scoring}, for a different approach.
21669 Even though this looks much like Lisp code, nothing here is actually
21670 @code{eval}ed. The Lisp reader is used to read this form, though, so it
21671 has to be valid syntactically, if not semantically.
21673 Six keys are supported by this alist:
21678 If the key is a string, it is the name of the header to perform the
21679 match on. Scoring can only be performed on these eight headers:
21680 @code{From}, @code{Subject}, @code{References}, @code{Message-ID},
21681 @code{Xref}, @code{Lines}, @code{Chars} and @code{Date}. In addition to
21682 these headers, there are three strings to tell Gnus to fetch the entire
21683 article and do the match on larger parts of the article: @code{Body}
21684 will perform the match on the body of the article, @code{Head} will
21685 perform the match on the head of the article, and @code{All} will
21686 perform the match on the entire article. Note that using any of these
21687 last three keys will slow down group entry @emph{considerably}. The
21688 final ``header'' you can score on is @code{Followup}. These score
21689 entries will result in new score entries being added for all follow-ups
21690 to articles that matches these score entries.
21692 Following this key is an arbitrary number of score entries, where each
21693 score entry has one to four elements.
21697 The first element is the @dfn{match element}. On most headers this will
21698 be a string, but on the Lines and Chars headers, this must be an
21702 If the second element is present, it should be a number---the @dfn{score
21703 element}. This number should be an integer in the neginf to posinf
21704 interval. This number is added to the score of the article if the match
21705 is successful. If this element is not present, the
21706 @code{gnus-score-interactive-default-score} number will be used
21707 instead. This is 1000 by default.
21710 If the third element is present, it should be a number---the @dfn{date
21711 element}. This date says when the last time this score entry matched,
21712 which provides a mechanism for expiring the score entries. It this
21713 element is not present, the score entry is permanent. The date is
21714 represented by the number of days since December 31, 1 BCE.
21717 If the fourth element is present, it should be a symbol---the @dfn{type
21718 element}. This element specifies what function should be used to see
21719 whether this score entry matches the article. What match types that can
21720 be used depends on what header you wish to perform the match on.
21723 @item From, Subject, References, Xref, Message-ID
21724 For most header types, there are the @code{r} and @code{R} (regexp), as
21725 well as @code{s} and @code{S} (substring) types, and @code{e} and
21726 @code{E} (exact match), and @code{w} (word match) types. If this
21727 element is not present, Gnus will assume that substring matching should
21728 be used. @code{R}, @code{S}, and @code{E} differ from the others in
21729 that the matches will be done in a case-sensitive manner. All these
21730 one-letter types are really just abbreviations for the @code{regexp},
21731 @code{string}, @code{exact}, and @code{word} types, which you can use
21732 instead, if you feel like.
21735 Just as for the standard string overview headers, if you are using
21736 gnus-extra-headers, you can score on these headers' values. In this
21737 case, there is a 5th element in the score entry, being the name of the
21738 header to be scored. The following entry is useful in your
21739 @file{all.SCORE} file in case of spam attacks from a single origin
21740 host, if your @acronym{NNTP} server tracks @samp{NNTP-Posting-Host} in
21744 ("111.222.333.444" -1000 nil s
21745 "NNTP-Posting-Host")
21749 These two headers use different match types: @code{<}, @code{>},
21750 @code{=}, @code{>=} and @code{<=}.
21752 These predicates are true if
21755 (PREDICATE HEADER MATCH)
21758 evaluates to non-@code{nil}. For instance, the advanced match
21759 @code{("lines" 4 <)} (@pxref{Advanced Scoring}) will result in the
21766 Or to put it another way: When using @code{<} on @code{Lines} with 4 as
21767 the match, we get the score added if the article has less than 4 lines.
21768 (It's easy to get confused and think it's the other way around. But
21769 it's not. I think.)
21771 When matching on @code{Lines}, be careful because some back ends (like
21772 @code{nndir}) do not generate @code{Lines} header, so every article ends
21773 up being marked as having 0 lines. This can lead to strange results if
21774 you happen to lower score of the articles with few lines.
21777 For the Date header we have three kinda silly match types:
21778 @code{before}, @code{at} and @code{after}. I can't really imagine this
21779 ever being useful, but, like, it would feel kinda silly not to provide
21780 this function. Just in case. You never know. Better safe than sorry.
21781 Once burnt, twice shy. Don't judge a book by its cover. Never not have
21782 sex on a first date. (I have been told that at least one person, and I
21783 quote, ``found this function indispensable'', however.)
21787 A more useful match type is @code{regexp}. With it, you can match the
21788 date string using a regular expression. The date is normalized to
21789 ISO8601 compact format first---@var{YYYYMMDD}@code{T}@var{HHMMSS}. If
21790 you want to match all articles that have been posted on April 1st in
21791 every year, you could use @samp{....0401.........} as a match string,
21792 for instance. (Note that the date is kept in its original time zone, so
21793 this will match articles that were posted when it was April 1st where
21794 the article was posted from. Time zones are such wholesome fun for the
21797 @item Head, Body, All
21798 These three match keys use the same match types as the @code{From} (etc)
21802 This match key is somewhat special, in that it will match the
21803 @code{From} header, and affect the score of not only the matching
21804 articles, but also all followups to the matching articles. This allows
21805 you e.g. increase the score of followups to your own articles, or
21806 decrease the score of followups to the articles of some known
21807 trouble-maker. Uses the same match types as the @code{From} header
21808 uses. (Using this match key will lead to creation of @file{ADAPT}
21812 This match key works along the same lines as the @code{Followup} match
21813 key. If you say that you want to score on a (sub-)thread started by an
21814 article with a @code{Message-ID} @var{x}, then you add a @samp{thread}
21815 match. This will add a new @samp{thread} match for each article that
21816 has @var{x} in its @code{References} header. (These new @samp{thread}
21817 matches will use the @code{Message-ID}s of these matching articles.)
21818 This will ensure that you can raise/lower the score of an entire thread,
21819 even though some articles in the thread may not have complete
21820 @code{References} headers. Note that using this may lead to
21821 undeterministic scores of the articles in the thread. (Using this match
21822 key will lead to creation of @file{ADAPT} files.)
21826 @cindex score file atoms
21828 The value of this entry should be a number. Any articles with a score
21829 lower than this number will be marked as read.
21832 The value of this entry should be a number. Any articles with a score
21833 lower than this number will be removed from the summary buffer.
21835 @item mark-and-expunge
21836 The value of this entry should be a number. Any articles with a score
21837 lower than this number will be marked as read and removed from the
21840 @item thread-mark-and-expunge
21841 The value of this entry should be a number. All articles that belong to
21842 a thread that has a total score below this number will be marked as read
21843 and removed from the summary buffer. @code{gnus-thread-score-function}
21844 says how to compute the total score for a thread.
21847 The value of this entry should be any number of file names. These files
21848 are assumed to be score files as well, and will be loaded the same way
21851 @item exclude-files
21852 The clue of this entry should be any number of files. These files will
21853 not be loaded, even though they would normally be so, for some reason or
21857 The value of this entry will be @code{eval}ed. This element will be
21858 ignored when handling global score files.
21861 Read-only score files will not be updated or saved. Global score files
21862 should feature this atom (@pxref{Global Score Files}). (Note:
21863 @dfn{Global} here really means @dfn{global}; not your personal
21864 apply-to-all-groups score files.)
21867 The value of this entry should be a number. Articles that do not have
21868 parents will get this number added to their scores. Imagine you follow
21869 some high-volume newsgroup, like @samp{comp.lang.c}. Most likely you
21870 will only follow a few of the threads, also want to see any new threads.
21872 You can do this with the following two score file entries:
21876 (mark-and-expunge -100)
21879 When you enter the group the first time, you will only see the new
21880 threads. You then raise the score of the threads that you find
21881 interesting (with @kbd{I T} or @kbd{I S}), and ignore (@kbd{c y}) the
21882 rest. Next time you enter the group, you will see new articles in the
21883 interesting threads, plus any new threads.
21885 I.e.---the orphan score atom is for high-volume groups where a few
21886 interesting threads which can't be found automatically by ordinary
21887 scoring rules exist.
21890 This entry controls the adaptive scoring. If it is @code{t}, the
21891 default adaptive scoring rules will be used. If it is @code{ignore}, no
21892 adaptive scoring will be performed on this group. If it is a list, this
21893 list will be used as the adaptive scoring rules. If it isn't present,
21894 or is something other than @code{t} or @code{ignore}, the default
21895 adaptive scoring rules will be used. If you want to use adaptive
21896 scoring on most groups, you'd set @code{gnus-use-adaptive-scoring} to
21897 @code{t}, and insert an @code{(adapt ignore)} in the groups where you do
21898 not want adaptive scoring. If you only want adaptive scoring in a few
21899 groups, you'd set @code{gnus-use-adaptive-scoring} to @code{nil}, and
21900 insert @code{(adapt t)} in the score files of the groups where you want
21904 All adaptive score entries will go to the file named by this entry. It
21905 will also be applied when entering the group. This atom might be handy
21906 if you want to adapt on several groups at once, using the same adaptive
21907 file for a number of groups.
21910 @cindex local variables
21911 The value of this entry should be a list of @code{(@var{var}
21912 @var{value})} pairs. Each @var{var} will be made buffer-local to the
21913 current summary buffer, and set to the value specified. This is a
21914 convenient, if somewhat strange, way of setting variables in some
21915 groups if you don't like hooks much. Note that the @var{value} won't
21920 @node Score File Editing
21921 @section Score File Editing
21923 You normally enter all scoring commands from the summary buffer, but you
21924 might feel the urge to edit them by hand as well, so we've supplied you
21925 with a mode for that.
21927 It's simply a slightly customized @code{emacs-lisp} mode, with these
21928 additional commands:
21933 @kindex C-c C-c (Score)
21934 @findex gnus-score-edit-exit
21935 Save the changes you have made and return to the summary buffer
21936 (@code{gnus-score-edit-exit}).
21939 @kindex C-c C-d (Score)
21940 @findex gnus-score-edit-insert-date
21941 Insert the current date in numerical format
21942 (@code{gnus-score-edit-insert-date}). This is really the day number, if
21943 you were wondering.
21946 @kindex C-c C-p (Score)
21947 @findex gnus-score-pretty-print
21948 The adaptive score files are saved in an unformatted fashion. If you
21949 intend to read one of these files, you want to @dfn{pretty print} it
21950 first. This command (@code{gnus-score-pretty-print}) does that for
21955 Type @kbd{M-x gnus-score-mode} to use this mode.
21957 @vindex gnus-score-mode-hook
21958 @code{gnus-score-menu-hook} is run in score mode buffers.
21960 In the summary buffer you can use commands like @kbd{V f}, @kbd{V e} and
21961 @kbd{V t} to begin editing score files.
21964 @node Adaptive Scoring
21965 @section Adaptive Scoring
21966 @cindex adaptive scoring
21968 If all this scoring is getting you down, Gnus has a way of making it all
21969 happen automatically---as if by magic. Or rather, as if by artificial
21970 stupidity, to be precise.
21972 @vindex gnus-use-adaptive-scoring
21973 When you read an article, or mark an article as read, or kill an
21974 article, you leave marks behind. On exit from the group, Gnus can sniff
21975 these marks and add score elements depending on what marks it finds.
21976 You turn on this ability by setting @code{gnus-use-adaptive-scoring} to
21977 @code{t} or @code{(line)}. If you want score adaptively on separate
21978 words appearing in the subjects, you should set this variable to
21979 @code{(word)}. If you want to use both adaptive methods, set this
21980 variable to @code{(word line)}.
21982 @vindex gnus-default-adaptive-score-alist
21983 To give you complete control over the scoring process, you can customize
21984 the @code{gnus-default-adaptive-score-alist} variable. For instance, it
21985 might look something like this:
21988 (setq gnus-default-adaptive-score-alist
21989 '((gnus-unread-mark)
21990 (gnus-ticked-mark (from 4))
21991 (gnus-dormant-mark (from 5))
21992 (gnus-del-mark (from -4) (subject -1))
21993 (gnus-read-mark (from 4) (subject 2))
21994 (gnus-expirable-mark (from -1) (subject -1))
21995 (gnus-killed-mark (from -1) (subject -3))
21996 (gnus-kill-file-mark)
21997 (gnus-ancient-mark)
21998 (gnus-low-score-mark)
21999 (gnus-catchup-mark (from -1) (subject -1))))
22002 As you see, each element in this alist has a mark as a key (either a
22003 variable name or a ``real'' mark---a character). Following this key is
22004 a arbitrary number of header/score pairs. If there are no header/score
22005 pairs following the key, no adaptive scoring will be done on articles
22006 that have that key as the article mark. For instance, articles with
22007 @code{gnus-unread-mark} in the example above will not get adaptive score
22010 Each article can have only one mark, so just a single of these rules
22011 will be applied to each article.
22013 To take @code{gnus-del-mark} as an example---this alist says that all
22014 articles that have that mark (i.e., are marked with @samp{e}) will have a
22015 score entry added to lower based on the @code{From} header by -4, and
22016 lowered by @code{Subject} by -1. Change this to fit your prejudices.
22018 If you have marked 10 articles with the same subject with
22019 @code{gnus-del-mark}, the rule for that mark will be applied ten times.
22020 That means that that subject will get a score of ten times -1, which
22021 should be, unless I'm much mistaken, -10.
22023 If you have auto-expirable (mail) groups (@pxref{Expiring Mail}), all
22024 the read articles will be marked with the @samp{E} mark. This'll
22025 probably make adaptive scoring slightly impossible, so auto-expiring and
22026 adaptive scoring doesn't really mix very well.
22028 The headers you can score on are @code{from}, @code{subject},
22029 @code{message-id}, @code{references}, @code{xref}, @code{lines},
22030 @code{chars} and @code{date}. In addition, you can score on
22031 @code{followup}, which will create an adaptive score entry that matches
22032 on the @code{References} header using the @code{Message-ID} of the
22033 current article, thereby matching the following thread.
22035 If you use this scheme, you should set the score file atom @code{mark}
22036 to something small---like -300, perhaps, to avoid having small random
22037 changes result in articles getting marked as read.
22039 After using adaptive scoring for a week or so, Gnus should start to
22040 become properly trained and enhance the authors you like best, and kill
22041 the authors you like least, without you having to say so explicitly.
22043 You can control what groups the adaptive scoring is to be performed on
22044 by using the score files (@pxref{Score File Format}). This will also
22045 let you use different rules in different groups.
22047 @vindex gnus-adaptive-file-suffix
22048 The adaptive score entries will be put into a file where the name is the
22049 group name with @code{gnus-adaptive-file-suffix} appended. The default
22052 @vindex gnus-adaptive-pretty-print
22053 Adaptive score files can get huge and are not meant to be edited by
22054 human hands. If @code{gnus-adaptive-pretty-print} is @code{nil} (the
22055 deafult) those files will not be written in a human readable way.
22057 @vindex gnus-score-exact-adapt-limit
22058 When doing adaptive scoring, substring or fuzzy matching would probably
22059 give you the best results in most cases. However, if the header one
22060 matches is short, the possibility for false positives is great, so if
22061 the length of the match is less than
22062 @code{gnus-score-exact-adapt-limit}, exact matching will be used. If
22063 this variable is @code{nil}, exact matching will always be used to avoid
22066 @vindex gnus-default-adaptive-word-score-alist
22067 As mentioned above, you can adapt either on individual words or entire
22068 headers. If you adapt on words, the
22069 @code{gnus-default-adaptive-word-score-alist} variable says what score
22070 each instance of a word should add given a mark.
22073 (setq gnus-default-adaptive-word-score-alist
22074 `((,gnus-read-mark . 30)
22075 (,gnus-catchup-mark . -10)
22076 (,gnus-killed-mark . -20)
22077 (,gnus-del-mark . -15)))
22080 This is the default value. If you have adaption on words enabled, every
22081 word that appears in subjects of articles marked with
22082 @code{gnus-read-mark} will result in a score rule that increase the
22083 score with 30 points.
22085 @vindex gnus-default-ignored-adaptive-words
22086 @vindex gnus-ignored-adaptive-words
22087 Words that appear in the @code{gnus-default-ignored-adaptive-words} list
22088 will be ignored. If you wish to add more words to be ignored, use the
22089 @code{gnus-ignored-adaptive-words} list instead.
22091 @vindex gnus-adaptive-word-length-limit
22092 Some may feel that short words shouldn't count when doing adaptive
22093 scoring. If so, you may set @code{gnus-adaptive-word-length-limit} to
22094 an integer. Words shorter than this number will be ignored. This
22095 variable defaults to @code{nil}.
22097 @vindex gnus-adaptive-word-syntax-table
22098 When the scoring is done, @code{gnus-adaptive-word-syntax-table} is the
22099 syntax table in effect. It is similar to the standard syntax table, but
22100 it considers numbers to be non-word-constituent characters.
22102 @vindex gnus-adaptive-word-minimum
22103 If @code{gnus-adaptive-word-minimum} is set to a number, the adaptive
22104 word scoring process will never bring down the score of an article to
22105 below this number. The default is @code{nil}.
22107 @vindex gnus-adaptive-word-no-group-words
22108 If @code{gnus-adaptive-word-no-group-words} is set to @code{t}, gnus
22109 won't adaptively word score any of the words in the group name. Useful
22110 for groups like @samp{comp.editors.emacs}, where most of the subject
22111 lines contain the word @samp{emacs}.
22113 After using this scheme for a while, it might be nice to write a
22114 @code{gnus-psychoanalyze-user} command to go through the rules and see
22115 what words you like and what words you don't like. Or perhaps not.
22117 Note that the adaptive word scoring thing is highly experimental and is
22118 likely to change in the future. Initial impressions seem to indicate
22119 that it's totally useless as it stands. Some more work (involving more
22120 rigorous statistical methods) will have to be done to make this useful.
22123 @node Home Score File
22124 @section Home Score File
22126 The score file where new score file entries will go is called the
22127 @dfn{home score file}. This is normally (and by default) the score file
22128 for the group itself. For instance, the home score file for
22129 @samp{gnu.emacs.gnus} is @file{gnu.emacs.gnus.SCORE}.
22131 However, this may not be what you want. It is often convenient to share
22132 a common home score file among many groups---all @samp{emacs} groups
22133 could perhaps use the same home score file.
22135 @vindex gnus-home-score-file
22136 The variable that controls this is @code{gnus-home-score-file}. It can
22141 A string. Then this file will be used as the home score file for all
22145 A function. The result of this function will be used as the home score
22146 file. The function will be called with the name of the group as the
22150 A list. The elements in this list can be:
22154 @code{(@var{regexp} @var{file-name})}. If the @var{regexp} matches the
22155 group name, the @var{file-name} will be used as the home score file.
22158 A function. If the function returns non-@code{nil}, the result will
22159 be used as the home score file. The function will be called with the
22160 name of the group as the parameter.
22163 A string. Use the string as the home score file.
22166 The list will be traversed from the beginning towards the end looking
22171 So, if you want to use just a single score file, you could say:
22174 (setq gnus-home-score-file
22175 "my-total-score-file.SCORE")
22178 If you want to use @file{gnu.SCORE} for all @samp{gnu} groups and
22179 @file{rec.SCORE} for all @samp{rec} groups (and so on), you can say:
22181 @findex gnus-hierarchial-home-score-file
22183 (setq gnus-home-score-file
22184 'gnus-hierarchial-home-score-file)
22187 This is a ready-made function provided for your convenience.
22188 Other functions include
22191 @item gnus-current-home-score-file
22192 @findex gnus-current-home-score-file
22193 Return the ``current'' regular score file. This will make scoring
22194 commands add entry to the ``innermost'' matching score file.
22198 If you want to have one score file for the @samp{emacs} groups and
22199 another for the @samp{comp} groups, while letting all other groups use
22200 their own home score files:
22203 (setq gnus-home-score-file
22204 ;; @r{All groups that match the regexp @code{"\\.emacs"}}
22205 '(("\\.emacs" "emacs.SCORE")
22206 ;; @r{All the comp groups in one score file}
22207 ("^comp" "comp.SCORE")))
22210 @vindex gnus-home-adapt-file
22211 @code{gnus-home-adapt-file} works exactly the same way as
22212 @code{gnus-home-score-file}, but says what the home adaptive score file
22213 is instead. All new adaptive file entries will go into the file
22214 specified by this variable, and the same syntax is allowed.
22216 In addition to using @code{gnus-home-score-file} and
22217 @code{gnus-home-adapt-file}, you can also use group parameters
22218 (@pxref{Group Parameters}) and topic parameters (@pxref{Topic
22219 Parameters}) to achieve much the same. Group and topic parameters take
22220 precedence over this variable.
22223 @node Followups To Yourself
22224 @section Followups To Yourself
22226 Gnus offers two commands for picking out the @code{Message-ID} header in
22227 the current buffer. Gnus will then add a score rule that scores using
22228 this @code{Message-ID} on the @code{References} header of other
22229 articles. This will, in effect, increase the score of all articles that
22230 respond to the article in the current buffer. Quite useful if you want
22231 to easily note when people answer what you've said.
22235 @item gnus-score-followup-article
22236 @findex gnus-score-followup-article
22237 This will add a score to articles that directly follow up your own
22240 @item gnus-score-followup-thread
22241 @findex gnus-score-followup-thread
22242 This will add a score to all articles that appear in a thread ``below''
22246 @vindex message-sent-hook
22247 These two functions are both primarily meant to be used in hooks like
22248 @code{message-sent-hook}, like this:
22250 (add-hook 'message-sent-hook 'gnus-score-followup-thread)
22254 If you look closely at your own @code{Message-ID}, you'll notice that
22255 the first two or three characters are always the same. Here's two of
22259 <x6u3u47icf.fsf@@eyesore.no>
22260 <x6sp9o7ibw.fsf@@eyesore.no>
22263 So ``my'' ident on this machine is @samp{x6}. This can be
22264 exploited---the following rule will raise the score on all followups to
22269 ("<x6[0-9a-z]+\\.fsf\\(_-_\\)?@@.*eyesore\\.no>"
22273 Whether it's the first two or first three characters that are ``yours''
22274 is system-dependent.
22277 @node Scoring On Other Headers
22278 @section Scoring On Other Headers
22279 @cindex scoring on other headers
22281 Gnus is quite fast when scoring the ``traditional''
22282 headers---@samp{From}, @samp{Subject} and so on. However, scoring
22283 other headers requires writing a @code{head} scoring rule, which means
22284 that Gnus has to request every single article from the back end to find
22285 matches. This takes a long time in big groups.
22287 @vindex gnus-inhibit-slow-scoring
22288 You can inhibit this slow scoring on headers or body by setting the
22289 variable @code{gnus-inhibit-slow-scoring}. If
22290 @code{gnus-inhibit-slow-scoring} is regexp, slow scoring is inhibited if
22291 the group matches the regexp. If it is t, slow scoring on it is
22292 inhibited for all groups.
22294 Now, there's not much you can do about the slowness for news groups, but for
22295 mail groups, you have greater control. In @ref{To From Newsgroups},
22296 it's explained in greater detail what this mechanism does, but here's
22297 a cookbook example for @code{nnml} on how to allow scoring on the
22298 @samp{To} and @samp{Cc} headers.
22300 Put the following in your @file{~/.gnus.el} file.
22303 (setq gnus-extra-headers '(To Cc Newsgroups Keywords)
22304 nnmail-extra-headers gnus-extra-headers)
22307 Restart Gnus and rebuild your @code{nnml} overview files with the
22308 @kbd{M-x nnml-generate-nov-databases} command. This will take a long
22309 time if you have much mail.
22311 Now you can score on @samp{To} and @samp{Cc} as ``extra headers'' like
22312 so: @kbd{I e s p To RET <your name> RET}.
22318 @section Scoring Tips
22319 @cindex scoring tips
22325 @cindex scoring crossposts
22326 If you want to lower the score of crossposts, the line to match on is
22327 the @code{Xref} header.
22329 ("xref" (" talk.politics.misc:" -1000))
22332 @item Multiple crossposts
22333 If you want to lower the score of articles that have been crossposted to
22334 more than, say, 3 groups:
22337 ("[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+"
22341 @item Matching on the body
22342 This is generally not a very good idea---it takes a very long time.
22343 Gnus actually has to fetch each individual article from the server. But
22344 you might want to anyway, I guess. Even though there are three match
22345 keys (@code{Head}, @code{Body} and @code{All}), you should choose one
22346 and stick with it in each score file. If you use any two, each article
22347 will be fetched @emph{twice}. If you want to match a bit on the
22348 @code{Head} and a bit on the @code{Body}, just use @code{All} for all
22351 @item Marking as read
22352 You will probably want to mark articles that have scores below a certain
22353 number as read. This is most easily achieved by putting the following
22354 in your @file{all.SCORE} file:
22358 You may also consider doing something similar with @code{expunge}.
22360 @item Negated character classes
22361 If you say stuff like @code{[^abcd]*}, you may get unexpected results.
22362 That will match newlines, which might lead to, well, The Unknown. Say
22363 @code{[^abcd\n]*} instead.
22367 @node Reverse Scoring
22368 @section Reverse Scoring
22369 @cindex reverse scoring
22371 If you want to keep just articles that have @samp{Sex with Emacs} in the
22372 subject header, and expunge all other articles, you could put something
22373 like this in your score file:
22377 ("Sex with Emacs" 2))
22382 So, you raise all articles that match @samp{Sex with Emacs} and mark the
22383 rest as read, and expunge them to boot.
22386 @node Global Score Files
22387 @section Global Score Files
22388 @cindex global score files
22390 Sure, other newsreaders have ``global kill files''. These are usually
22391 nothing more than a single kill file that applies to all groups, stored
22392 in the user's home directory. Bah! Puny, weak newsreaders!
22394 What I'm talking about here are Global Score Files. Score files from
22395 all over the world, from users everywhere, uniting all nations in one
22396 big, happy score file union! Ange-score! New and untested!
22398 @vindex gnus-global-score-files
22399 All you have to do to use other people's score files is to set the
22400 @code{gnus-global-score-files} variable. One entry for each score file,
22401 or each score file directory. Gnus will decide by itself what score
22402 files are applicable to which group.
22404 To use the score file
22405 @file{/ftp@@ftp.gnus.org:/pub/larsi/ding/score/soc.motss.SCORE} and
22406 all score files in the @file{/ftp@@ftp.some-where:/pub/score} directory,
22410 (setq gnus-global-score-files
22411 '("/ftp@@ftp.gnus.org:/pub/larsi/ding/score/soc.motss.SCORE"
22412 "/ftp@@ftp.some-where:/pub/score/"))
22415 @findex gnus-score-search-global-directories
22417 Simple, eh? Directory names must end with a @samp{/}. These
22418 directories are typically scanned only once during each Gnus session.
22419 If you feel the need to manually re-scan the remote directories, you can
22420 use the @code{gnus-score-search-global-directories} command.
22422 Note that, at present, using this option will slow down group entry
22423 somewhat. (That is---a lot.)
22425 If you want to start maintaining score files for other people to use,
22426 just put your score file up for anonymous ftp and announce it to the
22427 world. Become a retro-moderator! Participate in the retro-moderator
22428 wars sure to ensue, where retro-moderators battle it out for the
22429 sympathy of the people, luring them to use their score files on false
22430 premises! Yay! The net is saved!
22432 Here are some tips for the would-be retro-moderator, off the top of my
22438 Articles heavily crossposted are probably junk.
22440 To lower a single inappropriate article, lower by @code{Message-ID}.
22442 Particularly brilliant authors can be raised on a permanent basis.
22444 Authors that repeatedly post off-charter for the group can safely be
22445 lowered out of existence.
22447 Set the @code{mark} and @code{expunge} atoms to obliterate the nastiest
22448 articles completely.
22451 Use expiring score entries to keep the size of the file down. You
22452 should probably have a long expiry period, though, as some sites keep
22453 old articles for a long time.
22456 @dots{} I wonder whether other newsreaders will support global score files
22457 in the future. @emph{Snicker}. Yup, any day now, newsreaders like Blue
22458 Wave, xrn and 1stReader are bound to implement scoring. Should we start
22459 holding our breath yet?
22463 @section Kill Files
22466 Gnus still supports those pesky old kill files. In fact, the kill file
22467 entries can now be expiring, which is something I wrote before Daniel
22468 Quinlan thought of doing score files, so I've left the code in there.
22470 In short, kill processing is a lot slower (and I do mean @emph{a lot})
22471 than score processing, so it might be a good idea to rewrite your kill
22472 files into score files.
22474 Anyway, a kill file is a normal @code{emacs-lisp} file. You can put any
22475 forms into this file, which means that you can use kill files as some
22476 sort of primitive hook function to be run on group entry, even though
22477 that isn't a very good idea.
22479 Normal kill files look like this:
22482 (gnus-kill "From" "Lars Ingebrigtsen")
22483 (gnus-kill "Subject" "ding")
22487 This will mark every article written by me as read, and remove the
22488 marked articles from the summary buffer. Very useful, you'll agree.
22490 Other programs use a totally different kill file syntax. If Gnus
22491 encounters what looks like a @code{rn} kill file, it will take a stab at
22494 Two summary functions for editing a @sc{gnus} kill file:
22499 @kindex M-k (Summary)
22500 @findex gnus-summary-edit-local-kill
22501 Edit this group's kill file (@code{gnus-summary-edit-local-kill}).
22504 @kindex M-K (Summary)
22505 @findex gnus-summary-edit-global-kill
22506 Edit the general kill file (@code{gnus-summary-edit-global-kill}).
22509 Two group mode functions for editing the kill files:
22514 @kindex M-k (Group)
22515 @findex gnus-group-edit-local-kill
22516 Edit this group's kill file (@code{gnus-group-edit-local-kill}).
22519 @kindex M-K (Group)
22520 @findex gnus-group-edit-global-kill
22521 Edit the general kill file (@code{gnus-group-edit-global-kill}).
22524 Kill file variables:
22527 @item gnus-kill-file-name
22528 @vindex gnus-kill-file-name
22529 A kill file for the group @samp{soc.motss} is normally called
22530 @file{soc.motss.KILL}. The suffix appended to the group name to get
22531 this file name is detailed by the @code{gnus-kill-file-name} variable.
22532 The ``global'' kill file (not in the score file sense of ``global'', of
22533 course) is just called @file{KILL}.
22535 @vindex gnus-kill-save-kill-file
22536 @item gnus-kill-save-kill-file
22537 If this variable is non-@code{nil}, Gnus will save the
22538 kill file after processing, which is necessary if you use expiring
22541 @item gnus-apply-kill-hook
22542 @vindex gnus-apply-kill-hook
22543 @findex gnus-apply-kill-file-unless-scored
22544 @findex gnus-apply-kill-file
22545 A hook called to apply kill files to a group. It is
22546 @code{(gnus-apply-kill-file)} by default. If you want to ignore the
22547 kill file if you have a score file for the same group, you can set this
22548 hook to @code{(gnus-apply-kill-file-unless-scored)}. If you don't want
22549 kill files to be processed, you should set this variable to @code{nil}.
22551 @item gnus-kill-file-mode-hook
22552 @vindex gnus-kill-file-mode-hook
22553 A hook called in kill-file mode buffers.
22558 @node Converting Kill Files
22559 @section Converting Kill Files
22561 @cindex converting kill files
22563 If you have loads of old kill files, you may want to convert them into
22564 score files. If they are ``regular'', you can use
22565 the @file{gnus-kill-to-score.el} package; if not, you'll have to do it
22568 The kill to score conversion package isn't included in Emacs by default.
22569 You can fetch it from the contrib directory of the Gnus distribution or
22571 @uref{http://heim.ifi.uio.no/~larsi/ding-various/gnus-kill-to-score.el}.
22573 If your old kill files are very complex---if they contain more
22574 non-@code{gnus-kill} forms than not, you'll have to convert them by
22575 hand. Or just let them be as they are. Gnus will still use them as
22579 @node Advanced Scoring
22580 @section Advanced Scoring
22582 Scoring on Subjects and From headers is nice enough, but what if you're
22583 really interested in what a person has to say only when she's talking
22584 about a particular subject? Or what if you really don't want to
22585 read what person A has to say when she's following up to person B, but
22586 want to read what she says when she's following up to person C?
22588 By using advanced scoring rules you may create arbitrarily complex
22592 * Advanced Scoring Syntax:: A definition.
22593 * Advanced Scoring Examples:: What they look like.
22594 * Advanced Scoring Tips:: Getting the most out of it.
22598 @node Advanced Scoring Syntax
22599 @subsection Advanced Scoring Syntax
22601 Ordinary scoring rules have a string as the first element in the rule.
22602 Advanced scoring rules have a list as the first element. The second
22603 element is the score to be applied if the first element evaluated to a
22604 non-@code{nil} value.
22606 These lists may consist of three logical operators, one redirection
22607 operator, and various match operators.
22614 This logical operator will evaluate each of its arguments until it finds
22615 one that evaluates to @code{false}, and then it'll stop. If all arguments
22616 evaluate to @code{true} values, then this operator will return
22621 This logical operator will evaluate each of its arguments until it finds
22622 one that evaluates to @code{true}. If no arguments are @code{true},
22623 then this operator will return @code{false}.
22628 This logical operator only takes a single argument. It returns the
22629 logical negation of the value of its argument.
22633 There is an @dfn{indirection operator} that will make its arguments
22634 apply to the ancestors of the current article being scored. For
22635 instance, @code{1-} will make score rules apply to the parent of the
22636 current article. @code{2-} will make score rules apply to the
22637 grandparent of the current article. Alternatively, you can write
22638 @code{^^}, where the number of @code{^}s (carets) says how far back into
22639 the ancestry you want to go.
22641 Finally, we have the match operators. These are the ones that do the
22642 real work. Match operators are header name strings followed by a match
22643 and a match type. A typical match operator looks like @samp{("from"
22644 "Lars Ingebrigtsen" s)}. The header names are the same as when using
22645 simple scoring, and the match types are also the same.
22648 @node Advanced Scoring Examples
22649 @subsection Advanced Scoring Examples
22651 Please note that the following examples are score file rules. To
22652 make a complete score file from them, surround them with another pair
22655 Let's say you want to increase the score of articles written by Lars
22656 when he's talking about Gnus:
22661 ("from" "Lars Ingebrigtsen")
22662 ("subject" "Gnus"))
22669 When he writes long articles, he sometimes has something nice to say:
22673 ("from" "Lars Ingebrigtsen")
22680 However, when he responds to things written by Reig Eigil Logge, you
22681 really don't want to read what he's written:
22685 ("from" "Lars Ingebrigtsen")
22686 (1- ("from" "Reig Eigil Logge")))
22690 Everybody that follows up Redmondo when he writes about disappearing
22691 socks should have their scores raised, but only when they talk about
22692 white socks. However, when Lars talks about socks, it's usually not
22699 ("from" "redmondo@@.*no" r)
22700 ("body" "disappearing.*socks" t)))
22701 (! ("from" "Lars Ingebrigtsen"))
22702 ("body" "white.*socks"))
22706 Suppose you're reading a high volume group and you're only interested
22707 in replies. The plan is to score down all articles that don't have
22708 subject that begin with "Re:", "Fw:" or "Fwd:" and then score up all
22709 parents of articles that have subjects that begin with reply marks.
22712 ((! ("subject" "re:\\|fwd?:" r))
22714 ((1- ("subject" "re:\\|fwd?:" r))
22718 The possibilities are endless.
22720 @node Advanced Scoring Tips
22721 @subsection Advanced Scoring Tips
22723 The @code{&} and @code{|} logical operators do short-circuit logic.
22724 That is, they stop processing their arguments when it's clear what the
22725 result of the operation will be. For instance, if one of the arguments
22726 of an @code{&} evaluates to @code{false}, there's no point in evaluating
22727 the rest of the arguments. This means that you should put slow matches
22728 (@samp{body}, @samp{header}) last and quick matches (@samp{from},
22729 @samp{subject}) first.
22731 The indirection arguments (@code{1-} and so on) will make their
22732 arguments work on previous generations of the thread. If you say
22743 Then that means ``score on the from header of the grandparent of the
22744 current article''. An indirection is quite fast, but it's better to say:
22750 ("subject" "Gnus")))
22757 (1- ("from" "Lars"))
22758 (1- ("subject" "Gnus")))
22763 @section Score Decays
22764 @cindex score decays
22767 You may find that your scores have a tendency to grow without
22768 bounds, especially if you're using adaptive scoring. If scores get too
22769 big, they lose all meaning---they simply max out and it's difficult to
22770 use them in any sensible way.
22772 @vindex gnus-decay-scores
22773 @findex gnus-decay-score
22774 @vindex gnus-decay-score-function
22775 Gnus provides a mechanism for decaying scores to help with this problem.
22776 When score files are loaded and @code{gnus-decay-scores} is
22777 non-@code{nil}, Gnus will run the score files through the decaying
22778 mechanism thereby lowering the scores of all non-permanent score rules.
22779 If @code{gnus-decay-scores} is a regexp, only score files matching this
22780 regexp are treated. E.g. you may set it to @samp{\\.ADAPT\\'} if only
22781 @emph{adaptive} score files should be decayed. The decay itself if
22782 performed by the @code{gnus-decay-score-function} function, which is
22783 @code{gnus-decay-score} by default. Here's the definition of that
22787 (defun gnus-decay-score (score)
22788 "Decay SCORE according to `gnus-score-decay-constant'
22789 and `gnus-score-decay-scale'."
22791 (* (if (< score 0) -1 1)
22793 (max gnus-score-decay-constant
22795 gnus-score-decay-scale)))))))
22796 (if (and (featurep 'xemacs)
22797 ;; XEmacs' floor can handle only the floating point
22798 ;; number below the half of the maximum integer.
22799 (> (abs n) (lsh -1 -2)))
22801 (car (split-string (number-to-string n) "\\.")))
22805 @vindex gnus-score-decay-scale
22806 @vindex gnus-score-decay-constant
22807 @code{gnus-score-decay-constant} is 3 by default and
22808 @code{gnus-score-decay-scale} is 0.05. This should cause the following:
22812 Scores between -3 and 3 will be set to 0 when this function is called.
22815 Scores with magnitudes between 3 and 60 will be shrunk by 3.
22818 Scores with magnitudes greater than 60 will be shrunk by 5% of the
22822 If you don't like this decay function, write your own. It is called
22823 with the score to be decayed as its only parameter, and it should return
22824 the new score, which should be an integer.
22826 Gnus will try to decay scores once a day. If you haven't run Gnus for
22827 four days, Gnus will decay the scores four times, for instance.
22832 @include message.texi
22833 @chapter Emacs MIME
22834 @include emacs-mime.texi
22836 @include sieve.texi
22848 * Process/Prefix:: A convention used by many treatment commands.
22849 * Interactive:: Making Gnus ask you many questions.
22850 * Symbolic Prefixes:: How to supply some Gnus functions with options.
22851 * Formatting Variables:: You can specify what buffers should look like.
22852 * Window Layout:: Configuring the Gnus buffer windows.
22853 * Faces and Fonts:: How to change how faces look.
22854 * Compilation:: How to speed Gnus up.
22855 * Mode Lines:: Displaying information in the mode lines.
22856 * Highlighting and Menus:: Making buffers look all nice and cozy.
22857 * Buttons:: Get tendinitis in ten easy steps!
22858 * Daemons:: Gnus can do things behind your back.
22859 * NoCeM:: How to avoid spam and other fatty foods.
22860 * Undo:: Some actions can be undone.
22861 * Predicate Specifiers:: Specifying predicates.
22862 * Moderation:: What to do if you're a moderator.
22863 * Fetching a Group:: Starting Gnus just to read a group.
22864 * Image Enhancements:: Modern versions of Emacs/XEmacs can display images.
22865 * Fuzzy Matching:: What's the big fuzz?
22866 * Thwarting Email Spam:: Simple ways to avoid unsolicited commercial email.
22867 * Spam Package:: A package for filtering and processing spam.
22868 * The Gnus Registry:: A package for tracking messages by Message-ID.
22869 * Other modes:: Interaction with other modes.
22870 * Various Various:: Things that are really various.
22874 @node Process/Prefix
22875 @section Process/Prefix
22876 @cindex process/prefix convention
22878 Many functions, among them functions for moving, decoding and saving
22879 articles, use what is known as the @dfn{Process/Prefix convention}.
22881 This is a method for figuring out what articles the user wants the
22882 command to be performed on.
22886 If the numeric prefix is N, perform the operation on the next N
22887 articles, starting with the current one. If the numeric prefix is
22888 negative, perform the operation on the previous N articles, starting
22889 with the current one.
22891 @vindex transient-mark-mode
22892 If @code{transient-mark-mode} in non-@code{nil} and the region is
22893 active, all articles in the region will be worked upon.
22895 If there is no numeric prefix, but some articles are marked with the
22896 process mark, perform the operation on the articles marked with
22899 If there is neither a numeric prefix nor any articles marked with the
22900 process mark, just perform the operation on the current article.
22902 Quite simple, really, but it needs to be made clear so that surprises
22905 Commands that react to the process mark will push the current list of
22906 process marked articles onto a stack and will then clear all process
22907 marked articles. You can restore the previous configuration with the
22908 @kbd{M P y} command (@pxref{Setting Process Marks}).
22910 @vindex gnus-summary-goto-unread
22911 One thing that seems to shock & horrify lots of people is that, for
22912 instance, @kbd{3 d} does exactly the same as @kbd{d} @kbd{d} @kbd{d}.
22913 Since each @kbd{d} (which marks the current article as read) by default
22914 goes to the next unread article after marking, this means that @kbd{3 d}
22915 will mark the next three unread articles as read, no matter what the
22916 summary buffer looks like. Set @code{gnus-summary-goto-unread} to
22917 @code{nil} for a more straightforward action.
22919 Many commands do not use the process/prefix convention. All commands
22920 that do explicitly say so in this manual. To apply the process/prefix
22921 convention to commands that do not use it, you can use the @kbd{M-&}
22922 command. For instance, to mark all the articles in the group as
22923 expirable, you could say @kbd{M P b M-& E}.
22927 @section Interactive
22928 @cindex interaction
22932 @item gnus-novice-user
22933 @vindex gnus-novice-user
22934 If this variable is non-@code{nil}, you are either a newcomer to the
22935 World of Usenet, or you are very cautious, which is a nice thing to be,
22936 really. You will be given questions of the type ``Are you sure you want
22937 to do this?'' before doing anything dangerous. This is @code{t} by
22940 @item gnus-expert-user
22941 @vindex gnus-expert-user
22942 If this variable is non-@code{nil}, you will seldom be asked any
22943 questions by Gnus. It will simply assume you know what you're doing,
22944 no matter how strange. For example, quitting Gnus, exiting a group
22945 without an update, catching up with a group, deleting expired
22946 articles, and replying by mail to a news message will not require
22949 @item gnus-interactive-catchup
22950 @vindex gnus-interactive-catchup
22951 Require confirmation before catching up a group if non-@code{nil}. It
22952 is @code{t} by default.
22954 @item gnus-interactive-exit
22955 @vindex gnus-interactive-exit
22956 Require confirmation before exiting Gnus. This variable is @code{t} by
22961 @node Symbolic Prefixes
22962 @section Symbolic Prefixes
22963 @cindex symbolic prefixes
22965 Quite a lot of Emacs commands react to the (numeric) prefix. For
22966 instance, @kbd{C-u 4 C-f} moves point four characters forward, and
22967 @kbd{C-u 9 0 0 I s s p} adds a permanent @code{Subject} substring score
22968 rule of 900 to the current article.
22970 This is all nice and well, but what if you want to give a command some
22971 additional information? Well, what most commands do is interpret the
22972 ``raw'' prefix in some special way. @kbd{C-u 0 C-x C-s} means that one
22973 doesn't want a backup file to be created when saving the current buffer,
22974 for instance. But what if you want to save without making a backup
22975 file, and you want Emacs to flash lights and play a nice tune at the
22976 same time? You can't, and you're probably perfectly happy that way.
22978 @kindex M-i (Summary)
22979 @findex gnus-symbolic-argument
22980 I'm not, so I've added a second prefix---the @dfn{symbolic prefix}. The
22981 prefix key is @kbd{M-i} (@code{gnus-symbolic-argument}), and the next
22982 character typed in is the value. You can stack as many @kbd{M-i}
22983 prefixes as you want. @kbd{M-i a C-M-u} means ``feed the @kbd{C-M-u}
22984 command the symbolic prefix @code{a}''. @kbd{M-i a M-i b C-M-u} means
22985 ``feed the @kbd{C-M-u} command the symbolic prefixes @code{a} and
22986 @code{b}''. You get the drift.
22988 Typing in symbolic prefixes to commands that don't accept them doesn't
22989 hurt, but it doesn't do any good either. Currently not many Gnus
22990 functions make use of the symbolic prefix.
22992 If you're interested in how Gnus implements this, @pxref{Extended
22996 @node Formatting Variables
22997 @section Formatting Variables
22998 @cindex formatting variables
23000 Throughout this manual you've probably noticed lots of variables called
23001 things like @code{gnus-group-line-format} and
23002 @code{gnus-summary-mode-line-format}. These control how Gnus is to
23003 output lines in the various buffers. There's quite a lot of them.
23004 Fortunately, they all use the same syntax, so there's not that much to
23007 Here's an example format spec (from the group buffer): @samp{%M%S%5y:
23008 %(%g%)\n}. We see that it is indeed extremely ugly, and that there are
23009 lots of percentages everywhere.
23012 * Formatting Basics:: A formatting variable is basically a format string.
23013 * Mode Line Formatting:: Some rules about mode line formatting variables.
23014 * Advanced Formatting:: Modifying output in various ways.
23015 * User-Defined Specs:: Having Gnus call your own functions.
23016 * Formatting Fonts:: Making the formatting look colorful and nice.
23017 * Positioning Point:: Moving point to a position after an operation.
23018 * Tabulation:: Tabulating your output.
23019 * Wide Characters:: Dealing with wide characters.
23022 Currently Gnus uses the following formatting variables:
23023 @code{gnus-group-line-format}, @code{gnus-summary-line-format},
23024 @code{gnus-server-line-format}, @code{gnus-topic-line-format},
23025 @code{gnus-group-mode-line-format},
23026 @code{gnus-summary-mode-line-format},
23027 @code{gnus-article-mode-line-format},
23028 @code{gnus-server-mode-line-format}, and
23029 @code{gnus-summary-pick-line-format}.
23031 All these format variables can also be arbitrary elisp forms. In that
23032 case, they will be @code{eval}ed to insert the required lines.
23034 @kindex M-x gnus-update-format
23035 @findex gnus-update-format
23036 Gnus includes a command to help you while creating your own format
23037 specs. @kbd{M-x gnus-update-format} will @code{eval} the current form,
23038 update the spec in question and pop you to a buffer where you can
23039 examine the resulting Lisp code to be run to generate the line.
23043 @node Formatting Basics
23044 @subsection Formatting Basics
23046 Each @samp{%} element will be replaced by some string or other when the
23047 buffer in question is generated. @samp{%5y} means ``insert the @samp{y}
23048 spec, and pad with spaces to get a 5-character field''.
23050 As with normal C and Emacs Lisp formatting strings, the numerical
23051 modifier between the @samp{%} and the formatting type character will
23052 @dfn{pad} the output so that it is always at least that long.
23053 @samp{%5y} will make the field always (at least) five characters wide by
23054 padding with spaces to the left. If you say @samp{%-5y}, it will pad to
23057 You may also wish to limit the length of the field to protect against
23058 particularly wide values. For that you can say @samp{%4,6y}, which
23059 means that the field will never be more than 6 characters wide and never
23060 less than 4 characters wide.
23062 Also Gnus supports some extended format specifications, such as
23063 @samp{%&user-date;}.
23066 @node Mode Line Formatting
23067 @subsection Mode Line Formatting
23069 Mode line formatting variables (e.g.,
23070 @code{gnus-summary-mode-line-format}) follow the same rules as other,
23071 buffer line oriented formatting variables (@pxref{Formatting Basics})
23072 with the following two differences:
23077 There must be no newline (@samp{\n}) at the end.
23080 The special @samp{%%b} spec can be used to display the buffer name.
23081 Well, it's no spec at all, really---@samp{%%} is just a way to quote
23082 @samp{%} to allow it to pass through the formatting machinery unmangled,
23083 so that Emacs receives @samp{%b}, which is something the Emacs mode line
23084 display interprets to mean ``show the buffer name''. For a full list of
23085 mode line specs Emacs understands, see the documentation of the
23086 @code{mode-line-format} variable.
23091 @node Advanced Formatting
23092 @subsection Advanced Formatting
23094 It is frequently useful to post-process the fields in some way.
23095 Padding, limiting, cutting off parts and suppressing certain values can
23096 be achieved by using @dfn{tilde modifiers}. A typical tilde spec might
23097 look like @samp{%~(cut 3)~(ignore "0")y}.
23099 These are the valid modifiers:
23104 Pad the field to the left with spaces until it reaches the required
23108 Pad the field to the right with spaces until it reaches the required
23113 Cut off characters from the left until it reaches the specified length.
23116 Cut off characters from the right until it reaches the specified
23121 Cut off the specified number of characters from the left.
23124 Cut off the specified number of characters from the right.
23127 Return an empty string if the field is equal to the specified value.
23130 Use the specified form as the field value when the @samp{@@} spec is
23136 "~(form (current-time-string))@@"
23141 Let's take an example. The @samp{%o} spec in the summary mode lines
23142 will return a date in compact ISO8601 format---@samp{19960809T230410}.
23143 This is quite a mouthful, so we want to shave off the century number and
23144 the time, leaving us with a six-character date. That would be
23145 @samp{%~(cut-left 2)~(max-right 6)~(pad 6)o}. (Cutting is done before
23146 maxing, and we need the padding to ensure that the date is never less
23147 than 6 characters to make it look nice in columns.)
23149 Ignoring is done first; then cutting; then maxing; and then as the very
23150 last operation, padding.
23152 If you use lots of these advanced thingies, you'll find that Gnus gets
23153 quite slow. This can be helped enormously by running @kbd{M-x
23154 gnus-compile} when you are satisfied with the look of your lines.
23155 @xref{Compilation}.
23158 @node User-Defined Specs
23159 @subsection User-Defined Specs
23161 All the specs allow for inserting user defined specifiers---@samp{u}.
23162 The next character in the format string should be a letter. Gnus
23163 will call the function @code{gnus-user-format-function-}@samp{X}, where
23164 @samp{X} is the letter following @samp{%u}. The function will be passed
23165 a single parameter---what the parameter means depends on what buffer
23166 it's being called from. The function should return a string, which will
23167 be inserted into the buffer just like information from any other
23168 specifier. This function may also be called with dummy values, so it
23169 should protect against that.
23171 Also Gnus supports extended user-defined specs, such as @samp{%u&foo;}.
23172 Gnus will call the function @code{gnus-user-format-function-}@samp{foo}.
23174 You can also use tilde modifiers (@pxref{Advanced Formatting} to achieve
23175 much the same without defining new functions. Here's an example:
23176 @samp{%~(form (count-lines (point-min) (point)))@@}. The form
23177 given here will be evaluated to yield the current line number, and then
23181 @node Formatting Fonts
23182 @subsection Formatting Fonts
23185 @vindex gnus-mouse-face
23186 There are specs for highlighting, and these are shared by all the format
23187 variables. Text inside the @samp{%(} and @samp{%)} specifiers will get
23188 the special @code{mouse-face} property set, which means that it will be
23189 highlighted (with @code{gnus-mouse-face}) when you put the mouse pointer
23193 @vindex gnus-face-0
23194 Text inside the @samp{%@{} and @samp{%@}} specifiers will have their
23195 normal faces set using @code{gnus-face-0}, which is @code{bold} by
23196 default. If you say @samp{%1@{}, you'll get @code{gnus-face-1} instead,
23197 and so on. Create as many faces as you wish. The same goes for the
23198 @code{mouse-face} specs---you can say @samp{%3(hello%)} to have
23199 @samp{hello} mouse-highlighted with @code{gnus-mouse-face-3}.
23201 @cindex %<<, %>>, guillemets
23202 @c @cindex %<<, %>>, %«, %», guillemets
23203 @vindex gnus-balloon-face-0
23204 Text inside the @samp{%<<} and @samp{%>>} specifiers will get the
23205 special @code{balloon-help} property set to
23206 @code{gnus-balloon-face-0}. If you say @samp{%1<<}, you'll get
23207 @code{gnus-balloon-face-1} and so on. The @code{gnus-balloon-face-*}
23208 variables should be either strings or symbols naming functions that
23209 return a string. When the mouse passes over text with this property
23210 set, a balloon window will appear and display the string. Please
23211 refer to @ref{Tooltips, ,Tooltips, emacs, The Emacs Manual},
23212 (in GNU Emacs) or the doc string of @code{balloon-help-mode} (in
23213 XEmacs) for more information on this. (For technical reasons, the
23214 guillemets have been approximated as @samp{<<} and @samp{>>} in this
23217 Here's an alternative recipe for the group buffer:
23220 ;; @r{Create three face types.}
23221 (setq gnus-face-1 'bold)
23222 (setq gnus-face-3 'italic)
23224 ;; @r{We want the article count to be in}
23225 ;; @r{a bold and green face. So we create}
23226 ;; @r{a new face called @code{my-green-bold}.}
23227 (copy-face 'bold 'my-green-bold)
23228 ;; @r{Set the color.}
23229 (set-face-foreground 'my-green-bold "ForestGreen")
23230 (setq gnus-face-2 'my-green-bold)
23232 ;; @r{Set the new & fancy format.}
23233 (setq gnus-group-line-format
23234 "%M%S%3@{%5y%@}%2[:%] %(%1@{%g%@}%)\n")
23237 I'm sure you'll be able to use this scheme to create totally unreadable
23238 and extremely vulgar displays. Have fun!
23240 Note that the @samp{%(} specs (and friends) do not make any sense on the
23241 mode-line variables.
23243 @node Positioning Point
23244 @subsection Positioning Point
23246 Gnus usually moves point to a pre-defined place on each line in most
23247 buffers. By default, point move to the first colon character on the
23248 line. You can customize this behavior in three different ways.
23250 You can move the colon character to somewhere else on the line.
23252 @findex gnus-goto-colon
23253 You can redefine the function that moves the point to the colon. The
23254 function is called @code{gnus-goto-colon}.
23256 But perhaps the most convenient way to deal with this, if you don't want
23257 to have a colon in your line, is to use the @samp{%*} specifier. If you
23258 put a @samp{%*} somewhere in your format line definition, Gnus will
23263 @subsection Tabulation
23265 You can usually line up your displays by padding and cutting your
23266 strings. However, when combining various strings of different size, it
23267 can often be more convenient to just output the strings, and then worry
23268 about lining up the following text afterwards.
23270 To do that, Gnus supplies tabulator specs---@samp{%=}. There are two
23271 different types---@dfn{hard tabulators} and @dfn{soft tabulators}.
23273 @samp{%50=} will insert space characters to pad the line up to column
23274 50. If the text is already past column 50, nothing will be inserted.
23275 This is the soft tabulator.
23277 @samp{%-50=} will insert space characters to pad the line up to column
23278 50. If the text is already past column 50, the excess text past column
23279 50 will be removed. This is the hard tabulator.
23282 @node Wide Characters
23283 @subsection Wide Characters
23285 Fixed width fonts in most countries have characters of the same width.
23286 Some countries, however, use Latin characters mixed with wider
23287 characters---most notable East Asian countries.
23289 The problem is that when formatting, Gnus assumes that if a string is 10
23290 characters wide, it'll be 10 Latin characters wide on the screen. In
23291 these countries, that's not true.
23293 @vindex gnus-use-correct-string-widths
23294 To help fix this, you can set @code{gnus-use-correct-string-widths} to
23295 @code{t}. This makes buffer generation slower, but the results will be
23296 prettier. The default value under XEmacs is @code{t} but @code{nil}
23300 @node Window Layout
23301 @section Window Layout
23302 @cindex window layout
23304 No, there's nothing here about X, so be quiet.
23306 @vindex gnus-use-full-window
23307 If @code{gnus-use-full-window} non-@code{nil}, Gnus will delete all
23308 other windows and occupy the entire Emacs screen by itself. It is
23309 @code{t} by default.
23311 Setting this variable to @code{nil} kinda works, but there are
23312 glitches. Use at your own peril.
23314 @vindex gnus-buffer-configuration
23315 @code{gnus-buffer-configuration} describes how much space each Gnus
23316 buffer should be given. Here's an excerpt of this variable:
23319 ((group (vertical 1.0 (group 1.0 point)
23320 (if gnus-carpal (group-carpal 4))))
23321 (article (vertical 1.0 (summary 0.25 point)
23325 This is an alist. The @dfn{key} is a symbol that names some action or
23326 other. For instance, when displaying the group buffer, the window
23327 configuration function will use @code{group} as the key. A full list of
23328 possible names is listed below.
23330 The @dfn{value} (i.e., the @dfn{split}) says how much space each buffer
23331 should occupy. To take the @code{article} split as an example -
23334 (article (vertical 1.0 (summary 0.25 point)
23338 This @dfn{split} says that the summary buffer should occupy 25% of upper
23339 half of the screen, and that it is placed over the article buffer. As
23340 you may have noticed, 100% + 25% is actually 125% (yup, I saw y'all
23341 reaching for that calculator there). However, the special number
23342 @code{1.0} is used to signal that this buffer should soak up all the
23343 rest of the space available after the rest of the buffers have taken
23344 whatever they need. There should be only one buffer with the @code{1.0}
23345 size spec per split.
23347 Point will be put in the buffer that has the optional third element
23348 @code{point}. In a @code{frame} split, the last subsplit having a leaf
23349 split where the tag @code{frame-focus} is a member (i.e. is the third or
23350 fourth element in the list, depending on whether the @code{point} tag is
23351 present) gets focus.
23353 Here's a more complicated example:
23356 (article (vertical 1.0 (group 4)
23357 (summary 0.25 point)
23358 (if gnus-carpal (summary-carpal 4))
23362 If the size spec is an integer instead of a floating point number,
23363 then that number will be used to say how many lines a buffer should
23364 occupy, not a percentage.
23366 If the @dfn{split} looks like something that can be @code{eval}ed (to be
23367 precise---if the @code{car} of the split is a function or a subr), this
23368 split will be @code{eval}ed. If the result is non-@code{nil}, it will
23369 be used as a split. This means that there will be three buffers if
23370 @code{gnus-carpal} is @code{nil}, and four buffers if @code{gnus-carpal}
23373 Not complicated enough for you? Well, try this on for size:
23376 (article (horizontal 1.0
23381 (summary 0.25 point)
23386 Whoops. Two buffers with the mystery 100% tag. And what's that
23387 @code{horizontal} thingie?
23389 If the first element in one of the split is @code{horizontal}, Gnus will
23390 split the window horizontally, giving you two windows side-by-side.
23391 Inside each of these strips you may carry on all you like in the normal
23392 fashion. The number following @code{horizontal} says what percentage of
23393 the screen is to be given to this strip.
23395 For each split, there @emph{must} be one element that has the 100% tag.
23396 The splitting is never accurate, and this buffer will eat any leftover
23397 lines from the splits.
23399 To be slightly more formal, here's a definition of what a valid split
23404 split = frame | horizontal | vertical | buffer | form
23405 frame = "(frame " size *split ")"
23406 horizontal = "(horizontal " size *split ")"
23407 vertical = "(vertical " size *split ")"
23408 buffer = "(" buf-name " " size *[ "point" ] *[ "frame-focus"] ")"
23409 size = number | frame-params
23410 buf-name = group | article | summary ...
23414 The limitations are that the @code{frame} split can only appear as the
23415 top-level split. @var{form} should be an Emacs Lisp form that should
23416 return a valid split. We see that each split is fully recursive, and
23417 may contain any number of @code{vertical} and @code{horizontal} splits.
23419 @vindex gnus-window-min-width
23420 @vindex gnus-window-min-height
23421 @cindex window height
23422 @cindex window width
23423 Finding the right sizes can be a bit complicated. No window may be less
23424 than @code{gnus-window-min-height} (default 1) characters high, and all
23425 windows must be at least @code{gnus-window-min-width} (default 1)
23426 characters wide. Gnus will try to enforce this before applying the
23427 splits. If you want to use the normal Emacs window width/height limit,
23428 you can just set these two variables to @code{nil}.
23430 If you're not familiar with Emacs terminology, @code{horizontal} and
23431 @code{vertical} splits may work the opposite way of what you'd expect.
23432 Windows inside a @code{horizontal} split are shown side-by-side, and
23433 windows within a @code{vertical} split are shown above each other.
23435 @findex gnus-configure-frame
23436 If you want to experiment with window placement, a good tip is to call
23437 @code{gnus-configure-frame} directly with a split. This is the function
23438 that does all the real work when splitting buffers. Below is a pretty
23439 nonsensical configuration with 5 windows; two for the group buffer and
23440 three for the article buffer. (I said it was nonsensical.) If you
23441 @code{eval} the statement below, you can get an idea of how that would
23442 look straight away, without going through the normal Gnus channels.
23443 Play with it until you're satisfied, and then use
23444 @code{gnus-add-configuration} to add your new creation to the buffer
23445 configuration list.
23448 (gnus-configure-frame
23452 (article 0.3 point))
23460 You might want to have several frames as well. No prob---just use the
23461 @code{frame} split:
23464 (gnus-configure-frame
23467 (summary 0.25 point frame-focus)
23469 (vertical ((height . 5) (width . 15)
23470 (user-position . t)
23471 (left . -1) (top . 1))
23476 This split will result in the familiar summary/article window
23477 configuration in the first (or ``main'') frame, while a small additional
23478 frame will be created where picons will be shown. As you can see,
23479 instead of the normal @code{1.0} top-level spec, each additional split
23480 should have a frame parameter alist as the size spec.
23481 @xref{Frame Parameters, , Frame Parameters, elisp, The GNU Emacs Lisp
23482 Reference Manual}. Under XEmacs, a frame property list will be
23483 accepted, too---for instance, @code{(height 5 width 15 left -1 top 1)}
23485 The list of all possible keys for @code{gnus-buffer-configuration} can
23486 be found in its default value.
23488 Note that the @code{message} key is used for both
23489 @code{gnus-group-mail} and @code{gnus-summary-mail-other-window}. If
23490 it is desirable to distinguish between the two, something like this
23494 (message (horizontal 1.0
23495 (vertical 1.0 (message 1.0 point))
23497 (if (buffer-live-p gnus-summary-buffer)
23502 One common desire for a multiple frame split is to have a separate frame
23503 for composing mail and news while leaving the original frame intact. To
23504 accomplish that, something like the following can be done:
23509 (if (not (buffer-live-p gnus-summary-buffer))
23510 (car (cdr (assoc 'group gnus-buffer-configuration)))
23511 (car (cdr (assoc 'summary gnus-buffer-configuration))))
23512 (vertical ((user-position . t) (top . 1) (left . 1)
23513 (name . "Message"))
23514 (message 1.0 point))))
23517 @findex gnus-add-configuration
23518 Since the @code{gnus-buffer-configuration} variable is so long and
23519 complicated, there's a function you can use to ease changing the config
23520 of a single setting: @code{gnus-add-configuration}. If, for instance,
23521 you want to change the @code{article} setting, you could say:
23524 (gnus-add-configuration
23525 '(article (vertical 1.0
23527 (summary .25 point)
23531 You'd typically stick these @code{gnus-add-configuration} calls in your
23532 @file{~/.gnus.el} file or in some startup hook---they should be run after
23533 Gnus has been loaded.
23535 @vindex gnus-always-force-window-configuration
23536 If all windows mentioned in the configuration are already visible, Gnus
23537 won't change the window configuration. If you always want to force the
23538 ``right'' window configuration, you can set
23539 @code{gnus-always-force-window-configuration} to non-@code{nil}.
23541 If you're using tree displays (@pxref{Tree Display}), and the tree
23542 window is displayed vertically next to another window, you may also want
23543 to fiddle with @code{gnus-tree-minimize-window} to avoid having the
23546 @subsection Example Window Configurations
23550 Narrow left hand side occupied by group buffer. Right hand side split
23551 between summary buffer (top one-sixth) and article buffer (bottom).
23566 (gnus-add-configuration
23569 (vertical 25 (group 1.0))
23571 (summary 0.16 point)
23574 (gnus-add-configuration
23577 (vertical 25 (group 1.0))
23578 (vertical 1.0 (summary 1.0 point)))))
23584 @node Faces and Fonts
23585 @section Faces and Fonts
23590 Fiddling with fonts and faces used to be very difficult, but these days
23591 it is very simple. You simply say @kbd{M-x customize-face}, pick out
23592 the face you want to alter, and alter it via the standard Customize
23597 @section Compilation
23598 @cindex compilation
23599 @cindex byte-compilation
23601 @findex gnus-compile
23603 Remember all those line format specification variables?
23604 @code{gnus-summary-line-format}, @code{gnus-group-line-format}, and so
23605 on. Now, Gnus will of course heed whatever these variables are, but,
23606 unfortunately, changing them will mean a quite significant slow-down.
23607 (The default values of these variables have byte-compiled functions
23608 associated with them, while the user-generated versions do not, of
23611 To help with this, you can run @kbd{M-x gnus-compile} after you've
23612 fiddled around with the variables and feel that you're (kind of)
23613 satisfied. This will result in the new specs being byte-compiled, and
23614 you'll get top speed again. Gnus will save these compiled specs in the
23615 @file{.newsrc.eld} file. (User-defined functions aren't compiled by
23616 this function, though---you should compile them yourself by sticking
23617 them into the @file{~/.gnus.el} file and byte-compiling that file.)
23621 @section Mode Lines
23624 @vindex gnus-updated-mode-lines
23625 @code{gnus-updated-mode-lines} says what buffers should keep their mode
23626 lines updated. It is a list of symbols. Supported symbols include
23627 @code{group}, @code{article}, @code{summary}, @code{server},
23628 @code{browse}, and @code{tree}. If the corresponding symbol is present,
23629 Gnus will keep that mode line updated with information that may be
23630 pertinent. If this variable is @code{nil}, screen refresh may be
23633 @cindex display-time
23635 @vindex gnus-mode-non-string-length
23636 By default, Gnus displays information on the current article in the mode
23637 lines of the summary and article buffers. The information Gnus wishes
23638 to display (e.g. the subject of the article) is often longer than the
23639 mode lines, and therefore have to be cut off at some point. The
23640 @code{gnus-mode-non-string-length} variable says how long the other
23641 elements on the line is (i.e., the non-info part). If you put
23642 additional elements on the mode line (e.g. a clock), you should modify
23645 @c Hook written by Francesco Potorti` <pot@cnuce.cnr.it>
23647 (add-hook 'display-time-hook
23648 (lambda () (setq gnus-mode-non-string-length
23650 (if line-number-mode 5 0)
23651 (if column-number-mode 4 0)
23652 (length display-time-string)))))
23655 If this variable is @code{nil} (which is the default), the mode line
23656 strings won't be chopped off, and they won't be padded either. Note
23657 that the default is unlikely to be desirable, as even the percentage
23658 complete in the buffer may be crowded off the mode line; the user should
23659 configure this variable appropriately for her configuration.
23662 @node Highlighting and Menus
23663 @section Highlighting and Menus
23665 @cindex highlighting
23668 @vindex gnus-visual
23669 The @code{gnus-visual} variable controls most of the Gnus-prettifying
23670 aspects. If @code{nil}, Gnus won't attempt to create menus or use fancy
23671 colors or fonts. This will also inhibit loading the @file{gnus-vis.el}
23674 This variable can be a list of visual properties that are enabled. The
23675 following elements are valid, and are all included by default:
23678 @item group-highlight
23679 Do highlights in the group buffer.
23680 @item summary-highlight
23681 Do highlights in the summary buffer.
23682 @item article-highlight
23683 Do highlights in the article buffer.
23685 Turn on highlighting in all buffers.
23687 Create menus in the group buffer.
23689 Create menus in the summary buffers.
23691 Create menus in the article buffer.
23693 Create menus in the browse buffer.
23695 Create menus in the server buffer.
23697 Create menus in the score buffers.
23699 Create menus in all buffers.
23702 So if you only want highlighting in the article buffer and menus in all
23703 buffers, you could say something like:
23706 (setq gnus-visual '(article-highlight menu))
23709 If you want highlighting only and no menus whatsoever, you'd say:
23712 (setq gnus-visual '(highlight))
23715 If @code{gnus-visual} is @code{t}, highlighting and menus will be used
23716 in all Gnus buffers.
23718 Other general variables that influence the look of all buffers include:
23721 @item gnus-mouse-face
23722 @vindex gnus-mouse-face
23723 This is the face (i.e., font) used for mouse highlighting in Gnus. No
23724 mouse highlights will be done if @code{gnus-visual} is @code{nil}.
23728 There are hooks associated with the creation of all the different menus:
23732 @item gnus-article-menu-hook
23733 @vindex gnus-article-menu-hook
23734 Hook called after creating the article mode menu.
23736 @item gnus-group-menu-hook
23737 @vindex gnus-group-menu-hook
23738 Hook called after creating the group mode menu.
23740 @item gnus-summary-menu-hook
23741 @vindex gnus-summary-menu-hook
23742 Hook called after creating the summary mode menu.
23744 @item gnus-server-menu-hook
23745 @vindex gnus-server-menu-hook
23746 Hook called after creating the server mode menu.
23748 @item gnus-browse-menu-hook
23749 @vindex gnus-browse-menu-hook
23750 Hook called after creating the browse mode menu.
23752 @item gnus-score-menu-hook
23753 @vindex gnus-score-menu-hook
23754 Hook called after creating the score mode menu.
23765 Those new-fangled @dfn{mouse} contraptions is very popular with the
23766 young, hep kids who don't want to learn the proper way to do things
23767 these days. Why, I remember way back in the summer of '89, when I was
23768 using Emacs on a Tops 20 system. Three hundred users on one single
23769 machine, and every user was running Simula compilers. Bah!
23773 @vindex gnus-carpal
23774 Well, you can make Gnus display bufferfuls of buttons you can click to
23775 do anything by setting @code{gnus-carpal} to @code{t}. Pretty simple,
23776 really. Tell the chiropractor I sent you.
23781 @item gnus-carpal-mode-hook
23782 @vindex gnus-carpal-mode-hook
23783 Hook run in all carpal mode buffers.
23785 @item gnus-carpal-button-face
23786 @vindex gnus-carpal-button-face
23787 Face used on buttons.
23789 @item gnus-carpal-header-face
23790 @vindex gnus-carpal-header-face
23791 Face used on carpal buffer headers.
23793 @item gnus-carpal-group-buffer-buttons
23794 @vindex gnus-carpal-group-buffer-buttons
23795 Buttons in the group buffer.
23797 @item gnus-carpal-summary-buffer-buttons
23798 @vindex gnus-carpal-summary-buffer-buttons
23799 Buttons in the summary buffer.
23801 @item gnus-carpal-server-buffer-buttons
23802 @vindex gnus-carpal-server-buffer-buttons
23803 Buttons in the server buffer.
23805 @item gnus-carpal-browse-buffer-buttons
23806 @vindex gnus-carpal-browse-buffer-buttons
23807 Buttons in the browse buffer.
23810 All the @code{buttons} variables are lists. The elements in these list
23811 are either cons cells where the @code{car} contains a text to be displayed and
23812 the @code{cdr} contains a function symbol, or a simple string.
23820 Gnus, being larger than any program ever written (allegedly), does lots
23821 of strange stuff that you may wish to have done while you're not
23822 present. For instance, you may want it to check for new mail once in a
23823 while. Or you may want it to close down all connections to all servers
23824 when you leave Emacs idle. And stuff like that.
23826 Gnus will let you do stuff like that by defining various
23827 @dfn{handlers}. Each handler consists of three elements: A
23828 @var{function}, a @var{time}, and an @var{idle} parameter.
23830 Here's an example of a handler that closes connections when Emacs has
23831 been idle for thirty minutes:
23834 (gnus-demon-close-connections nil 30)
23837 Here's a handler that scans for @acronym{PGP} headers every hour when
23841 (gnus-demon-scan-pgp 60 t)
23844 This @var{time} parameter and that @var{idle} parameter work together
23845 in a strange, but wonderful fashion. Basically, if @var{idle} is
23846 @code{nil}, then the function will be called every @var{time} minutes.
23848 If @var{idle} is @code{t}, then the function will be called after
23849 @var{time} minutes only if Emacs is idle. So if Emacs is never idle,
23850 the function will never be called. But once Emacs goes idle, the
23851 function will be called every @var{time} minutes.
23853 If @var{idle} is a number and @var{time} is a number, the function will
23854 be called every @var{time} minutes only when Emacs has been idle for
23855 @var{idle} minutes.
23857 If @var{idle} is a number and @var{time} is @code{nil}, the function
23858 will be called once every time Emacs has been idle for @var{idle}
23861 And if @var{time} is a string, it should look like @samp{07:31}, and
23862 the function will then be called once every day somewhere near that
23863 time. Modified by the @var{idle} parameter, of course.
23865 @vindex gnus-demon-timestep
23866 (When I say ``minute'' here, I really mean @code{gnus-demon-timestep}
23867 seconds. This is 60 by default. If you change that variable,
23868 all the timings in the handlers will be affected.)
23870 So, if you want to add a handler, you could put something like this in
23871 your @file{~/.gnus.el} file:
23873 @findex gnus-demon-add-handler
23875 (gnus-demon-add-handler 'gnus-demon-close-connections 30 t)
23878 @findex gnus-demon-add-nocem
23879 @findex gnus-demon-add-scanmail
23880 @findex gnus-demon-add-rescan
23881 @findex gnus-demon-add-scan-timestamps
23882 @findex gnus-demon-add-disconnection
23883 Some ready-made functions to do this have been created:
23884 @code{gnus-demon-add-nocem}, @code{gnus-demon-add-disconnection},
23885 @code{gnus-demon-add-nntp-close-connection},
23886 @code{gnus-demon-add-scan-timestamps}, @code{gnus-demon-add-rescan}, and
23887 @code{gnus-demon-add-scanmail}. Just put those functions in your
23888 @file{~/.gnus.el} if you want those abilities.
23890 @findex gnus-demon-init
23891 @findex gnus-demon-cancel
23892 @vindex gnus-demon-handlers
23893 If you add handlers to @code{gnus-demon-handlers} directly, you should
23894 run @code{gnus-demon-init} to make the changes take hold. To cancel all
23895 daemons, you can use the @code{gnus-demon-cancel} function.
23897 Note that adding daemons can be pretty naughty if you over do it. Adding
23898 functions that scan all news and mail from all servers every two seconds
23899 is a sure-fire way of getting booted off any respectable system. So
23908 @dfn{Spamming} is posting the same article lots and lots of times.
23909 Spamming is bad. Spamming is evil.
23911 Spamming is usually canceled within a day or so by various anti-spamming
23912 agencies. These agencies usually also send out @dfn{NoCeM} messages.
23913 NoCeM is pronounced ``no see-'em'', and means what the name
23914 implies---these are messages that make the offending articles, like, go
23917 What use are these NoCeM messages if the articles are canceled anyway?
23918 Some sites do not honor cancel messages and some sites just honor cancels
23919 from a select few people. Then you may wish to make use of the NoCeM
23920 messages, which are distributed in the newsgroups
23921 @samp{news.lists.filters}, @samp{alt.nocem.misc}, etc.
23923 Gnus can read and parse the messages in this group automatically, and
23924 this will make spam disappear.
23926 There are some variables to customize, of course:
23929 @item gnus-use-nocem
23930 @vindex gnus-use-nocem
23931 Set this variable to @code{t} to set the ball rolling. It is @code{nil}
23934 You can also set this variable to a positive number as a group level.
23935 In that case, Gnus scans NoCeM messages when checking new news if this
23936 value is not exceeding a group level that you specify as the prefix
23937 argument to some commands, e.g. @code{gnus},
23938 @code{gnus-group-get-new-news}, etc. Otherwise, Gnus does not scan
23939 NoCeM messages if you specify a group level that is smaller than this
23940 value to those commands. For example, if you use 1 or 2 on the mail
23941 groups and the levels on the news groups remain the default, 3 is the
23944 @item gnus-nocem-groups
23945 @vindex gnus-nocem-groups
23946 Gnus will look for NoCeM messages in the groups in this list. The
23949 ("news.lists.filters" "alt.nocem.misc")
23952 @item gnus-nocem-issuers
23953 @vindex gnus-nocem-issuers
23954 There are many people issuing NoCeM messages. This list says what
23955 people you want to listen to. The default is:
23959 "alba-nocem@@albasani.net"
23960 "bleachbot@@httrack.com"
23961 "news@@arcor-online.net"
23962 "news@@uni-berlin.de"
23964 "pgpmoose@@killfile.org"
23968 Known despammers that you can put in this list are listed at@*
23969 @uref{http://www.xs4all.nl/~rosalind/nocemreg/nocemreg.html}.
23971 You do not have to heed NoCeM messages from all these people---just the
23972 ones you want to listen to. You also don't have to accept all NoCeM
23973 messages from the people you like. Each NoCeM message has a @dfn{type}
23974 header that gives the message a (more or less, usually less) rigorous
23975 definition. Common types are @samp{spam}, @samp{spew}, @samp{mmf},
23976 @samp{binary}, and @samp{troll}. To specify this, you have to use
23977 @code{(@var{issuer} @var{conditions} @dots{})} elements in the list.
23978 Each condition is either a string (which is a regexp that matches types
23979 you want to use) or a list on the form @code{(not @var{string})}, where
23980 @var{string} is a regexp that matches types you don't want to use.
23982 For instance, if you want all NoCeM messages from Chris Lewis except his
23983 @samp{troll} messages, you'd say:
23986 ("clewis@@ferret.ocunix.on.ca" ".*" (not "troll"))
23989 On the other hand, if you just want nothing but his @samp{spam} and
23990 @samp{spew} messages, you'd say:
23993 ("clewis@@ferret.ocunix.on.ca" (not ".*") "spew" "spam")
23996 The specs are applied left-to-right.
23999 @item gnus-nocem-verifyer
24000 @vindex gnus-nocem-verifyer
24001 @findex gnus-nocem-epg-verify
24003 This should be a function for verifying that the NoCeM issuer is who she
24004 says she is. This variable defaults to @code{gnus-nocem-epg-verify} if
24005 EasyPG is available, otherwise defaults to @code{pgg-verify}. The
24006 function should return non-@code{nil} if the verification is successful,
24007 otherwise (including the case the NoCeM message was not signed) should
24008 return @code{nil}. If this is too slow and you don't care for
24009 verification (which may be dangerous), you can set this variable to
24012 Formerly the default was @code{mc-verify}, which is a Mailcrypt
24013 function. While you can still use it, you can change it into
24014 @code{gnus-nocem-epg-verify} or @code{pgg-verify} running with GnuPG if
24015 you are willing to add the @acronym{PGP} public keys to GnuPG's keyring.
24017 @item gnus-nocem-directory
24018 @vindex gnus-nocem-directory
24019 This is where Gnus will store its NoCeM cache files. The default is@*
24020 @file{~/News/NoCeM/}.
24022 @item gnus-nocem-expiry-wait
24023 @vindex gnus-nocem-expiry-wait
24024 The number of days before removing old NoCeM entries from the cache.
24025 The default is 15. If you make it shorter Gnus will be faster, but you
24026 might then see old spam.
24028 @item gnus-nocem-check-from
24029 @vindex gnus-nocem-check-from
24030 Non-@code{nil} means check for valid issuers in message bodies.
24031 Otherwise don't bother fetching articles unless their author matches a
24032 valid issuer; that is much faster if you are selective about the
24035 @item gnus-nocem-check-article-limit
24036 @vindex gnus-nocem-check-article-limit
24037 If non-@code{nil}, the maximum number of articles to check in any NoCeM
24038 group. @code{nil} means no restriction. NoCeM groups can be huge and
24039 very slow to process.
24043 Using NoCeM could potentially be a memory hog. If you have many living
24044 (i. e., subscribed or unsubscribed groups), your Emacs process will grow
24045 big. If this is a problem, you should kill off all (or most) of your
24046 unsubscribed groups (@pxref{Subscription Commands}).
24053 It is very useful to be able to undo actions one has done. In normal
24054 Emacs buffers, it's easy enough---you just push the @code{undo} button.
24055 In Gnus buffers, however, it isn't that simple.
24057 The things Gnus displays in its buffer is of no value whatsoever to
24058 Gnus---it's all just data designed to look nice to the user.
24059 Killing a group in the group buffer with @kbd{C-k} makes the line
24060 disappear, but that's just a side-effect of the real action---the
24061 removal of the group in question from the internal Gnus structures.
24062 Undoing something like that can't be done by the normal Emacs
24063 @code{undo} function.
24065 Gnus tries to remedy this somewhat by keeping track of what the user
24066 does and coming up with actions that would reverse the actions the user
24067 takes. When the user then presses the @code{undo} key, Gnus will run
24068 the code to reverse the previous action, or the previous actions.
24069 However, not all actions are easily reversible, so Gnus currently offers
24070 a few key functions to be undoable. These include killing groups,
24071 yanking groups, and changing the list of read articles of groups.
24072 That's it, really. More functions may be added in the future, but each
24073 added function means an increase in data to be stored, so Gnus will
24074 never be totally undoable.
24076 @findex gnus-undo-mode
24077 @vindex gnus-use-undo
24079 The undoability is provided by the @code{gnus-undo-mode} minor mode. It
24080 is used if @code{gnus-use-undo} is non-@code{nil}, which is the
24081 default. The @kbd{C-M-_} key performs the @code{gnus-undo}
24082 command, which should feel kinda like the normal Emacs @code{undo}
24086 @node Predicate Specifiers
24087 @section Predicate Specifiers
24088 @cindex predicate specifiers
24090 Some Gnus variables are @dfn{predicate specifiers}. This is a special
24091 form that allows flexible specification of predicates without having
24092 to type all that much.
24094 These specifiers are lists consisting of functions, symbols and lists.
24099 (or gnus-article-unseen-p
24100 gnus-article-unread-p)
24103 The available symbols are @code{or}, @code{and} and @code{not}. The
24104 functions all take one parameter.
24106 @findex gnus-make-predicate
24107 Internally, Gnus calls @code{gnus-make-predicate} on these specifiers
24108 to create a function that can be called. This input parameter to this
24109 function will be passed along to all the functions in the predicate
24114 @section Moderation
24117 If you are a moderator, you can use the @file{gnus-mdrtn.el} package.
24118 It is not included in the standard Gnus package. Write a mail to
24119 @samp{larsi@@gnus.org} and state what group you moderate, and you'll
24122 The moderation package is implemented as a minor mode for summary
24126 (add-hook 'gnus-summary-mode-hook 'gnus-moderate)
24129 in your @file{~/.gnus.el} file.
24131 If you are the moderator of @samp{rec.zoofle}, this is how it's
24136 You split your incoming mail by matching on
24137 @samp{Newsgroups:.*rec.zoofle}, which will put all the to-be-posted
24138 articles in some mail group---for instance, @samp{nnml:rec.zoofle}.
24141 You enter that group once in a while and post articles using the @kbd{e}
24142 (edit-and-post) or @kbd{s} (just send unedited) commands.
24145 If, while reading the @samp{rec.zoofle} newsgroup, you happen upon some
24146 articles that weren't approved by you, you can cancel them with the
24150 To use moderation mode in these two groups, say:
24153 (setq gnus-moderated-list
24154 "^nnml:rec.zoofle$\\|^rec.zoofle$")
24158 @node Fetching a Group
24159 @section Fetching a Group
24160 @cindex fetching a group
24162 @findex gnus-fetch-group
24163 It is sometimes convenient to be able to just say ``I want to read this
24164 group and I don't care whether Gnus has been started or not''. This is
24165 perhaps more useful for people who write code than for users, but the
24166 command @code{gnus-fetch-group} provides this functionality in any case.
24167 It takes the group name as a parameter.
24170 @node Image Enhancements
24171 @section Image Enhancements
24173 XEmacs, as well as Emacs 21@footnote{Emacs 21 on MS Windows doesn't
24174 support images, Emacs 22 does.} and up, are able to display pictures and
24175 stuff, so Gnus has taken advantage of that.
24178 * X-Face:: Display a funky, teensy black-and-white image.
24179 * Face:: Display a funkier, teensier colored image.
24180 * Smileys:: Show all those happy faces the way they were meant to be shown.
24181 * Picons:: How to display pictures of what you're reading.
24182 * XVarious:: Other XEmacsy Gnusey variables.
24190 @code{X-Face} headers describe a 48x48 pixel black-and-white (1 bit
24191 depth) image that's supposed to represent the author of the message.
24192 It seems to be supported by an ever-growing number of mail and news
24196 @findex gnus-article-display-x-face
24197 @vindex gnus-article-x-face-command
24198 @vindex gnus-article-x-face-too-ugly
24206 Viewing an @code{X-Face} header either requires an Emacs that has
24207 @samp{compface} support (which most XEmacs versions have), or that you
24208 have suitable conversion or display programs installed. If your Emacs
24209 has image support the default action is to display the face before the
24210 @code{From} header. If there's no native @code{X-Face} support, Gnus
24211 will try to convert the @code{X-Face} header using external programs
24212 from the @code{pbmplus} package and friends, see below. For XEmacs it's
24213 faster if XEmacs has been compiled with @code{X-Face} support. The
24214 default action under Emacs without image support is to fork off the
24215 @code{display} program.
24217 On a GNU/Linux system, the @code{display} program is included in the
24218 ImageMagick package. For external conversion programs look for packages
24219 with names like @code{netpbm}, @code{libgr-progs} and @code{compface}.
24220 On Windows, you may use the packages @code{netpbm} and @code{compface}
24221 from @url{http://gnuwin32.sourceforge.net}. You need to add the
24222 @code{bin} directory to your @code{PATH} environment variable.
24223 @c In fact only the following DLLs and binaries seem to be required:
24224 @c compface1.dll uncompface.exe libnetpbm10.dll icontopbm.exe
24226 The variable @code{gnus-article-x-face-command} controls which programs
24227 are used to display the @code{X-Face} header. If this variable is a
24228 string, this string will be executed in a sub-shell. If it is a
24229 function, this function will be called with the face as the argument.
24230 If @code{gnus-article-x-face-too-ugly} (which is a regexp) matches the
24231 @code{From} header, the face will not be shown.
24233 (Note: @code{x-face} is used in the variable/function names, not
24241 @vindex gnus-x-face
24242 Face to show X-Face. The colors from this face are used as the
24243 foreground and background colors of the displayed X-Faces. The
24244 default colors are black and white.
24246 @item gnus-face-properties-alist
24247 @vindex gnus-face-properties-alist
24248 Alist of image types and properties applied to Face (@pxref{Face}) and
24249 X-Face images. The default value is @code{((pbm . (:face gnus-x-face))
24250 (png . nil))} for Emacs or @code{((xface . (:face gnus-x-face)))} for
24251 XEmacs. Here are examples:
24254 ;; Specify the altitude of Face and X-Face images in the From header.
24255 (setq gnus-face-properties-alist
24256 '((pbm . (:face gnus-x-face :ascent 80))
24257 (png . (:ascent 80))))
24259 ;; Show Face and X-Face images as pressed buttons.
24260 (setq gnus-face-properties-alist
24261 '((pbm . (:face gnus-x-face :relief -2))
24262 (png . (:relief -2))))
24265 @pxref{Image Descriptors, ,Image Descriptors, elisp, The Emacs Lisp
24266 Reference Manual} for the valid properties for various image types.
24267 Currently, @code{pbm} is used for X-Face images and @code{png} is used
24268 for Face images in Emacs. Only the @code{:face} property is effective
24269 on the @code{xface} image type in XEmacs if it is built with the
24270 @samp{libcompface} library.
24273 If you use posting styles, you can use an @code{x-face-file} entry in
24274 @code{gnus-posting-styles}, @xref{Posting Styles}. If you don't, Gnus
24275 provides a few convenience functions and variables to allow easier
24276 insertion of X-Face headers in outgoing messages. You also need the
24277 above mentioned ImageMagick, netpbm or other image conversion packages
24278 (depending the values of the variables below) for these functions.
24280 @findex gnus-random-x-face
24281 @vindex gnus-convert-pbm-to-x-face-command
24282 @vindex gnus-x-face-directory
24283 @code{gnus-random-x-face} goes through all the @samp{pbm} files in
24284 @code{gnus-x-face-directory} and picks one at random, and then
24285 converts it to the X-Face format by using the
24286 @code{gnus-convert-pbm-to-x-face-command} shell command. The
24287 @samp{pbm} files should be 48x48 pixels big. It returns the X-Face
24288 header data as a string.
24290 @findex gnus-insert-random-x-face-header
24291 @code{gnus-insert-random-x-face-header} calls
24292 @code{gnus-random-x-face} and inserts a @samp{X-Face} header with the
24293 randomly generated data.
24295 @findex gnus-x-face-from-file
24296 @vindex gnus-convert-image-to-x-face-command
24297 @code{gnus-x-face-from-file} takes a GIF file as the parameter, and then
24298 converts the file to X-Face format by using the
24299 @code{gnus-convert-image-to-x-face-command} shell command.
24301 Here's how you would typically use the first function. Put something
24302 like the following in your @file{~/.gnus.el} file:
24305 (setq message-required-news-headers
24306 (nconc message-required-news-headers
24307 (list '(X-Face . gnus-random-x-face))))
24310 Using the last function would be something like this:
24313 (setq message-required-news-headers
24314 (nconc message-required-news-headers
24315 (list '(X-Face . (lambda ()
24316 (gnus-x-face-from-file
24317 "~/My-face.gif"))))))
24325 @c #### FIXME: faces and x-faces' implementations should really be harmonized.
24327 @code{Face} headers are essentially a funkier version of @code{X-Face}
24328 ones. They describe a 48x48 pixel colored image that's supposed to
24329 represent the author of the message.
24332 @findex gnus-article-display-face
24333 The contents of a @code{Face} header must be a base64 encoded PNG image.
24334 See @uref{http://quimby.gnus.org/circus/face/} for the precise
24337 The @code{gnus-face-properties-alist} variable affects the appearance of
24338 displayed Face images. @xref{X-Face}.
24340 Viewing an @code{Face} header requires an Emacs that is able to display
24343 @c (if (featurep 'xemacs)
24345 @c (image-type-available-p 'png))
24347 Gnus provides a few convenience functions and variables to allow
24348 easier insertion of Face headers in outgoing messages.
24350 @findex gnus-convert-png-to-face
24351 @code{gnus-convert-png-to-face} takes a 48x48 PNG image, no longer than
24352 726 bytes long, and converts it to a face.
24354 @findex gnus-face-from-file
24355 @vindex gnus-convert-image-to-face-command
24356 @code{gnus-face-from-file} takes a JPEG file as the parameter, and then
24357 converts the file to Face format by using the
24358 @code{gnus-convert-image-to-face-command} shell command.
24360 Here's how you would typically use this function. Put something like the
24361 following in your @file{~/.gnus.el} file:
24364 (setq message-required-news-headers
24365 (nconc message-required-news-headers
24366 (list '(Face . (lambda ()
24367 (gnus-face-from-file "~/face.jpg"))))))
24372 @subsection Smileys
24377 \gnusfig{-3cm}{0.5cm}{\epsfig{figure=ps/BigFace,height=20cm}}
24382 @dfn{Smiley} is a package separate from Gnus, but since Gnus is
24383 currently the only package that uses Smiley, it is documented here.
24385 In short---to use Smiley in Gnus, put the following in your
24386 @file{~/.gnus.el} file:
24389 (setq gnus-treat-display-smileys t)
24392 Smiley maps text smiley faces---@samp{:-)}, @samp{8-)}, @samp{:-(} and
24393 the like---to pictures and displays those instead of the text smiley
24394 faces. The conversion is controlled by a list of regexps that matches
24395 text and maps that to file names.
24397 @vindex smiley-regexp-alist
24398 The alist used is specified by the @code{smiley-regexp-alist}
24399 variable. The first item in each element is the regexp to be matched;
24400 the second element is the regexp match group that is to be replaced by
24401 the picture; and the third element is the name of the file to be
24404 The following variables customize the appearance of the smileys:
24409 @vindex smiley-style
24410 Specifies the smiley style. Predefined smiley styles include
24411 @code{low-color} (small 13x14 pixel, three-color images), @code{medium}
24412 (more colorful images, 16x16 pixel), and @code{grayscale} (grayscale
24413 images, 14x14 pixel). The default depends on the height of the default
24416 @item smiley-data-directory
24417 @vindex smiley-data-directory
24418 Where Smiley will look for smiley faces files. You shouldn't set this
24419 variable anymore. Customize @code{smiley-style} instead.
24421 @item gnus-smiley-file-types
24422 @vindex gnus-smiley-file-types
24423 List of suffixes on smiley file names to try.
24437 So@dots{} You want to slow down your news reader even more! This is a
24438 good way to do so. It's also a great way to impress people staring
24439 over your shoulder as you read news.
24441 What are Picons? To quote directly from the Picons Web site:
24450 @dfn{Picons} is short for ``personal icons''. They're small,
24451 constrained images used to represent users and domains on the net,
24452 organized into databases so that the appropriate image for a given
24453 e-mail address can be found. Besides users and domains, there are picon
24454 databases for Usenet newsgroups and weather forecasts. The picons are
24455 in either monochrome @code{XBM} format or color @code{XPM} and
24456 @code{GIF} formats.
24459 @vindex gnus-picon-databases
24460 For instructions on obtaining and installing the picons databases,
24461 point your Web browser at
24462 @uref{http://www.cs.indiana.edu/picons/ftp/index.html}.
24464 If you are using Debian GNU/Linux, saying @samp{apt-get install
24465 picons.*} will install the picons where Gnus can find them.
24467 To enable displaying picons, simply make sure that
24468 @code{gnus-picon-databases} points to the directory containing the
24471 @vindex gnus-picon-style
24472 The variable @code{gnus-picon-style} controls how picons are displayed.
24473 If @code{inline}, the textual representation is replaced. If
24474 @code{right}, picons are added right to the textual representation.
24476 The following variables offer control over where things are located.
24480 @item gnus-picon-databases
24481 @vindex gnus-picon-databases
24482 The location of the picons database. This is a list of directories
24483 containing the @file{news}, @file{domains}, @file{users} (and so on)
24484 subdirectories. Defaults to @code{("/usr/lib/picon"
24485 "/usr/local/faces")}.
24487 @item gnus-picon-news-directories
24488 @vindex gnus-picon-news-directories
24489 List of subdirectories to search in @code{gnus-picon-databases} for
24490 newsgroups faces. @code{("news")} is the default.
24492 @item gnus-picon-user-directories
24493 @vindex gnus-picon-user-directories
24494 List of subdirectories to search in @code{gnus-picon-databases} for user
24495 faces. @code{("users" "usenix" "local" "misc")} is the default.
24497 @item gnus-picon-domain-directories
24498 @vindex gnus-picon-domain-directories
24499 List of subdirectories to search in @code{gnus-picon-databases} for
24500 domain name faces. Defaults to @code{("domains")}. Some people may
24501 want to add @samp{"unknown"} to this list.
24503 @item gnus-picon-file-types
24504 @vindex gnus-picon-file-types
24505 Ordered list of suffixes on picon file names to try. Defaults to
24506 @code{("xpm" "gif" "xbm")} minus those not built-in your Emacs.
24512 @subsection Various XEmacs Variables
24515 @item gnus-xmas-glyph-directory
24516 @vindex gnus-xmas-glyph-directory
24517 This is where Gnus will look for pictures. Gnus will normally
24518 auto-detect this directory, but you may set it manually if you have an
24519 unusual directory structure.
24521 @item gnus-xmas-modeline-glyph
24522 @vindex gnus-xmas-modeline-glyph
24523 A glyph displayed in all Gnus mode lines. It is a tiny gnu head by
24528 @subsubsection Toolbar
24532 @item gnus-use-toolbar
24533 @vindex gnus-use-toolbar
24534 This variable specifies the position to display the toolbar. If
24535 @code{nil}, don't display toolbars. If it is non-@code{nil}, it should
24536 be one of the symbols @code{default}, @code{top}, @code{bottom},
24537 @code{right}, and @code{left}. @code{default} means to use the default
24538 toolbar, the rest mean to display the toolbar on the place which those
24539 names show. The default is @code{default}.
24541 @item gnus-toolbar-thickness
24542 @vindex gnus-toolbar-thickness
24543 Cons of the height and the width specifying the thickness of a toolbar.
24544 The height is used for the toolbar displayed on the top or the bottom,
24545 the width is used for the toolbar displayed on the right or the left.
24546 The default is that of the default toolbar.
24548 @item gnus-group-toolbar
24549 @vindex gnus-group-toolbar
24550 The toolbar in the group buffer.
24552 @item gnus-summary-toolbar
24553 @vindex gnus-summary-toolbar
24554 The toolbar in the summary buffer.
24556 @item gnus-summary-mail-toolbar
24557 @vindex gnus-summary-mail-toolbar
24558 The toolbar in the summary buffer of mail groups.
24569 @node Fuzzy Matching
24570 @section Fuzzy Matching
24571 @cindex fuzzy matching
24573 Gnus provides @dfn{fuzzy matching} of @code{Subject} lines when doing
24574 things like scoring, thread gathering and thread comparison.
24576 As opposed to regular expression matching, fuzzy matching is very fuzzy.
24577 It's so fuzzy that there's not even a definition of what @dfn{fuzziness}
24578 means, and the implementation has changed over time.
24580 Basically, it tries to remove all noise from lines before comparing.
24581 @samp{Re: }, parenthetical remarks, white space, and so on, are filtered
24582 out of the strings before comparing the results. This often leads to
24583 adequate results---even when faced with strings generated by text
24584 manglers masquerading as newsreaders.
24587 @node Thwarting Email Spam
24588 @section Thwarting Email Spam
24592 @cindex unsolicited commercial email
24594 In these last days of the Usenet, commercial vultures are hanging about
24595 and grepping through news like crazy to find email addresses they can
24596 foist off their scams and products to. As a reaction to this, many
24597 people have started putting nonsense addresses into their @code{From}
24598 lines. I think this is counterproductive---it makes it difficult for
24599 people to send you legitimate mail in response to things you write, as
24600 well as making it difficult to see who wrote what. This rewriting may
24601 perhaps be a bigger menace than the unsolicited commercial email itself
24604 The biggest problem I have with email spam is that it comes in under
24605 false pretenses. I press @kbd{g} and Gnus merrily informs me that I
24606 have 10 new emails. I say ``Golly gee! Happy is me!'' and select the
24607 mail group, only to find two pyramid schemes, seven advertisements
24608 (``New! Miracle tonic for growing full, lustrous hair on your toes!'')
24609 and one mail asking me to repent and find some god.
24611 This is annoying. Here's what you can do about it.
24614 * The problem of spam:: Some background, and some solutions
24615 * Anti-Spam Basics:: Simple steps to reduce the amount of spam.
24616 * SpamAssassin:: How to use external anti-spam tools.
24617 * Hashcash:: Reduce spam by burning CPU time.
24620 @node The problem of spam
24621 @subsection The problem of spam
24623 @cindex spam filtering approaches
24624 @cindex filtering approaches, spam
24626 @cindex unsolicited commercial email
24628 First, some background on spam.
24630 If you have access to e-mail, you are familiar with spam (technically
24631 termed @acronym{UCE}, Unsolicited Commercial E-mail). Simply put, it
24632 exists because e-mail delivery is very cheap compared to paper mail,
24633 so only a very small percentage of people need to respond to an UCE to
24634 make it worthwhile to the advertiser. Ironically, one of the most
24635 common spams is the one offering a database of e-mail addresses for
24636 further spamming. Senders of spam are usually called @emph{spammers},
24637 but terms like @emph{vermin}, @emph{scum}, @emph{sociopaths}, and
24638 @emph{morons} are in common use as well.
24640 Spam comes from a wide variety of sources. It is simply impossible to
24641 dispose of all spam without discarding useful messages. A good
24642 example is the TMDA system, which requires senders
24643 unknown to you to confirm themselves as legitimate senders before
24644 their e-mail can reach you. Without getting into the technical side
24645 of TMDA, a downside is clearly that e-mail from legitimate sources may
24646 be discarded if those sources can't or won't confirm themselves
24647 through the TMDA system. Another problem with TMDA is that it
24648 requires its users to have a basic understanding of e-mail delivery
24651 The simplest approach to filtering spam is filtering, at the mail
24652 server or when you sort through incoming mail. If you get 200 spam
24653 messages per day from @samp{random-address@@vmadmin.com}, you block
24654 @samp{vmadmin.com}. If you get 200 messages about @samp{VIAGRA}, you
24655 discard all messages with @samp{VIAGRA} in the message. If you get
24656 lots of spam from Bulgaria, for example, you try to filter all mail
24657 from Bulgarian IPs.
24659 This, unfortunately, is a great way to discard legitimate e-mail. The
24660 risks of blocking a whole country (Bulgaria, Norway, Nigeria, China,
24661 etc.) or even a continent (Asia, Africa, Europe, etc.) from contacting
24662 you should be obvious, so don't do it if you have the choice.
24664 In another instance, the very informative and useful RISKS digest has
24665 been blocked by overzealous mail filters because it @strong{contained}
24666 words that were common in spam messages. Nevertheless, in isolated
24667 cases, with great care, direct filtering of mail can be useful.
24669 Another approach to filtering e-mail is the distributed spam
24670 processing, for instance DCC implements such a system. In essence,
24671 @var{N} systems around the world agree that a machine @var{X} in
24672 Ghana, Estonia, or California is sending out spam e-mail, and these
24673 @var{N} systems enter @var{X} or the spam e-mail from @var{X} into a
24674 database. The criteria for spam detection vary---it may be the number
24675 of messages sent, the content of the messages, and so on. When a user
24676 of the distributed processing system wants to find out if a message is
24677 spam, he consults one of those @var{N} systems.
24679 Distributed spam processing works very well against spammers that send
24680 a large number of messages at once, but it requires the user to set up
24681 fairly complicated checks. There are commercial and free distributed
24682 spam processing systems. Distributed spam processing has its risks as
24683 well. For instance legitimate e-mail senders have been accused of
24684 sending spam, and their web sites and mailing lists have been shut
24685 down for some time because of the incident.
24687 The statistical approach to spam filtering is also popular. It is
24688 based on a statistical analysis of previous spam messages. Usually
24689 the analysis is a simple word frequency count, with perhaps pairs of
24690 words or 3-word combinations thrown into the mix. Statistical
24691 analysis of spam works very well in most of the cases, but it can
24692 classify legitimate e-mail as spam in some cases. It takes time to
24693 run the analysis, the full message must be analyzed, and the user has
24694 to store the database of spam analysis. Statistical analysis on the
24695 server is gaining popularity. This has the advantage of letting the
24696 user Just Read Mail, but has the disadvantage that it's harder to tell
24697 the server that it has misclassified mail.
24699 Fighting spam is not easy, no matter what anyone says. There is no
24700 magic switch that will distinguish Viagra ads from Mom's e-mails.
24701 Even people are having a hard time telling spam apart from non-spam,
24702 because spammers are actively looking to fool us into thinking they
24703 are Mom, essentially. Spamming is irritating, irresponsible, and
24704 idiotic behavior from a bunch of people who think the world owes them
24705 a favor. We hope the following sections will help you in fighting the
24708 @node Anti-Spam Basics
24709 @subsection Anti-Spam Basics
24713 @cindex unsolicited commercial email
24715 One way of dealing with spam is having Gnus split out all spam into a
24716 @samp{spam} mail group (@pxref{Splitting Mail}).
24718 First, pick one (1) valid mail address that you can be reached at, and
24719 put it in your @code{From} header of all your news articles. (I've
24720 chosen @samp{larsi@@trym.ifi.uio.no}, but for many addresses on the form
24721 @samp{larsi+usenet@@ifi.uio.no} will be a better choice. Ask your
24722 sysadmin whether your sendmail installation accepts keywords in the local
24723 part of the mail address.)
24726 (setq message-default-news-headers
24727 "From: Lars Magne Ingebrigtsen <larsi@@trym.ifi.uio.no>\n")
24730 Then put the following split rule in @code{nnmail-split-fancy}
24731 (@pxref{Fancy Mail Splitting}):
24735 (to "larsi@@trym.ifi.uio.no"
24736 (| ("subject" "re:.*" "misc")
24737 ("references" ".*@@.*" "misc")
24742 This says that all mail to this address is suspect, but if it has a
24743 @code{Subject} that starts with a @samp{Re:} or has a @code{References}
24744 header, it's probably ok. All the rest goes to the @samp{spam} group.
24745 (This idea probably comes from Tim Pierce.)
24747 In addition, many mail spammers talk directly to your @acronym{SMTP} server
24748 and do not include your email address explicitly in the @code{To}
24749 header. Why they do this is unknown---perhaps it's to thwart this
24750 thwarting scheme? In any case, this is trivial to deal with---you just
24751 put anything not addressed to you in the @samp{spam} group by ending
24752 your fancy split rule in this way:
24757 (to "larsi" "misc")
24761 In my experience, this will sort virtually everything into the right
24762 group. You still have to check the @samp{spam} group from time to time to
24763 check for legitimate mail, though. If you feel like being a good net
24764 citizen, you can even send off complaints to the proper authorities on
24765 each unsolicited commercial email---at your leisure.
24767 This works for me. It allows people an easy way to contact me (they can
24768 just press @kbd{r} in the usual way), and I'm not bothered at all with
24769 spam. It's a win-win situation. Forging @code{From} headers to point
24770 to non-existent domains is yucky, in my opinion.
24772 Be careful with this approach. Spammers are wise to it.
24776 @subsection SpamAssassin, Vipul's Razor, DCC, etc
24777 @cindex SpamAssassin
24778 @cindex Vipul's Razor
24781 The days where the hints in the previous section were sufficient in
24782 avoiding spam are coming to an end. There are many tools out there
24783 that claim to reduce the amount of spam you get. This section could
24784 easily become outdated fast, as new products replace old, but
24785 fortunately most of these tools seem to have similar interfaces. Even
24786 though this section will use SpamAssassin as an example, it should be
24787 easy to adapt it to most other tools.
24789 Note that this section does not involve the @code{spam.el} package,
24790 which is discussed in the next section. If you don't care for all
24791 the features of @code{spam.el}, you can make do with these simple
24794 If the tool you are using is not installed on the mail server, you
24795 need to invoke it yourself. Ideas on how to use the
24796 @code{:postscript} mail source parameter (@pxref{Mail Source
24797 Specifiers}) follow.
24801 '((file :prescript "formail -bs spamassassin < /var/mail/%u")
24805 "mv %t /tmp/foo; formail -bs spamc < /tmp/foo > %t")))
24808 Once you manage to process your incoming spool somehow, thus making
24809 the mail contain e.g.@: a header indicating it is spam, you are ready to
24810 filter it out. Using normal split methods (@pxref{Splitting Mail}):
24813 (setq nnmail-split-methods '(("spam" "^X-Spam-Flag: YES")
24817 Or using fancy split methods (@pxref{Fancy Mail Splitting}):
24820 (setq nnmail-split-methods 'nnmail-split-fancy
24821 nnmail-split-fancy '(| ("X-Spam-Flag" "YES" "spam")
24825 Some people might not like the idea of piping the mail through various
24826 programs using a @code{:prescript} (if some program is buggy, you
24827 might lose all mail). If you are one of them, another solution is to
24828 call the external tools during splitting. Example fancy split method:
24831 (setq nnmail-split-fancy '(| (: kevin-spamassassin)
24833 (defun kevin-spamassassin ()
24837 (if (eq 1 (call-process-region (point-min) (point-max)
24838 "spamc" nil nil nil "-c"))
24842 Note that with the nnimap back end, message bodies will not be
24843 downloaded by default. You need to set
24844 @code{nnimap-split-download-body} to @code{t} to do that
24845 (@pxref{Splitting in IMAP}).
24847 That is about it. As some spam is likely to get through anyway, you
24848 might want to have a nifty function to call when you happen to read
24849 spam. And here is the nifty function:
24852 (defun my-gnus-raze-spam ()
24853 "Submit SPAM to Vipul's Razor, then mark it as expirable."
24855 (gnus-summary-save-in-pipe "razor-report -f -d" t)
24856 (gnus-summary-mark-as-expirable 1))
24860 @subsection Hashcash
24863 A novel technique to fight spam is to require senders to do something
24864 costly and demonstrably unique for each message they send. This has
24865 the obvious drawback that you cannot rely on everyone in the world
24866 using this technique, since it is not part of the Internet standards,
24867 but it may be useful in smaller communities.
24869 While the tools in the previous section work well in practice, they
24870 work only because the tools are constantly maintained and updated as
24871 new form of spam appears. This means that a small percentage of spam
24872 will always get through. It also means that somewhere, someone needs
24873 to read lots of spam to update these tools. Hashcash avoids that, but
24874 instead prefers that everyone you contact through e-mail supports the
24875 scheme. You can view the two approaches as pragmatic vs dogmatic.
24876 The approaches have their own advantages and disadvantages, but as
24877 often in the real world, a combination of them is stronger than either
24878 one of them separately.
24881 The ``something costly'' is to burn CPU time, more specifically to
24882 compute a hash collision up to a certain number of bits. The
24883 resulting hashcash cookie is inserted in a @samp{X-Hashcash:} header.
24884 For more details, and for the external application @code{hashcash} you
24885 need to install to use this feature, see
24886 @uref{http://www.hashcash.org/}. Even more information can be found
24887 at @uref{http://www.camram.org/}.
24889 If you wish to generate hashcash for each message you send, you can
24890 customize @code{message-generate-hashcash} (@pxref{Mail Headers, ,Mail
24891 Headers,message, The Message Manual}), as in:
24894 (setq message-generate-hashcash t)
24897 You will need to set up some additional variables as well:
24901 @item hashcash-default-payment
24902 @vindex hashcash-default-payment
24903 This variable indicates the default number of bits the hash collision
24904 should consist of. By default this is 20. Suggested useful values
24907 @item hashcash-payment-alist
24908 @vindex hashcash-payment-alist
24909 Some receivers may require you to spend burn more CPU time than the
24910 default. This variable contains a list of @samp{(@var{addr}
24911 @var{amount})} cells, where @var{addr} is the receiver (email address
24912 or newsgroup) and @var{amount} is the number of bits in the collision
24913 that is needed. It can also contain @samp{(@var{addr} @var{string}
24914 @var{amount})} cells, where the @var{string} is the string to use
24915 (normally the email address or newsgroup name is used).
24917 @item hashcash-path
24918 @vindex hashcash-path
24919 Where the @code{hashcash} binary is installed. This variable should
24920 be automatically set by @code{executable-find}, but if it's @code{nil}
24921 (usually because the @code{hashcash} binary is not in your path)
24922 you'll get a warning when you check hashcash payments and an error
24923 when you generate hashcash payments.
24927 Gnus can verify hashcash cookies, although this can also be done by
24928 hand customized mail filtering scripts. To verify a hashcash cookie
24929 in a message, use the @code{mail-check-payment} function in the
24930 @code{hashcash.el} library. You can also use the @code{spam.el}
24931 package with the @code{spam-use-hashcash} back end to validate hashcash
24932 cookies in incoming mail and filter mail accordingly (@pxref{Anti-spam
24933 Hashcash Payments}).
24936 @section Spam Package
24937 @cindex spam filtering
24940 The Spam package provides Gnus with a centralized mechanism for
24941 detecting and filtering spam. It filters new mail, and processes
24942 messages according to whether they are spam or ham. (@dfn{Ham} is the
24943 name used throughout this manual to indicate non-spam messages.)
24946 * Spam Package Introduction::
24947 * Filtering Incoming Mail::
24948 * Detecting Spam in Groups::
24949 * Spam and Ham Processors::
24950 * Spam Package Configuration Examples::
24952 * Extending the Spam package::
24953 * Spam Statistics Package::
24956 @node Spam Package Introduction
24957 @subsection Spam Package Introduction
24958 @cindex spam filtering
24959 @cindex spam filtering sequence of events
24962 You must read this section to understand how the Spam package works.
24963 Do not skip, speed-read, or glance through this section.
24965 Make sure you read the section on the @code{spam.el} sequence of
24966 events. See @xref{Extending the Spam package}.
24968 @cindex spam-initialize
24969 @vindex spam-use-stat
24970 To use the Spam package, you @strong{must} first run the function
24971 @code{spam-initialize}:
24977 This autoloads @code{spam.el} and installs the various hooks necessary
24978 to let the Spam package do its job. In order to make use of the Spam
24979 package, you have to set up certain group parameters and variables,
24980 which we will describe below. All of the variables controlling the
24981 Spam package can be found in the @samp{spam} customization group.
24983 There are two ``contact points'' between the Spam package and the rest
24984 of Gnus: checking new mail for spam, and leaving a group.
24986 Checking new mail for spam is done in one of two ways: while splitting
24987 incoming mail, or when you enter a group.
24989 The first way, checking for spam while splitting incoming mail, is
24990 suited to mail back ends such as @code{nnml} or @code{nnimap}, where
24991 new mail appears in a single spool file. The Spam package processes
24992 incoming mail, and sends mail considered to be spam to a designated
24993 ``spam'' group. @xref{Filtering Incoming Mail}.
24995 The second way is suited to back ends such as @code{nntp}, which have
24996 no incoming mail spool, or back ends where the server is in charge of
24997 splitting incoming mail. In this case, when you enter a Gnus group,
24998 the unseen or unread messages in that group are checked for spam.
24999 Detected spam messages are marked as spam. @xref{Detecting Spam in
25002 @cindex spam back ends
25003 In either case, you have to tell the Spam package what method to use
25004 to detect spam messages. There are several methods, or @dfn{spam back
25005 ends} (not to be confused with Gnus back ends!) to choose from: spam
25006 ``blacklists'' and ``whitelists'', dictionary-based filters, and so
25007 forth. @xref{Spam Back Ends}.
25009 In the Gnus summary buffer, messages that have been identified as spam
25010 always appear with a @samp{$} symbol.
25012 The Spam package divides Gnus groups into three categories: ham
25013 groups, spam groups, and unclassified groups. You should mark each of
25014 the groups you subscribe to as either a ham group or a spam group,
25015 using the @code{spam-contents} group parameter (@pxref{Group
25016 Parameters}). Spam groups have a special property: when you enter a
25017 spam group, all unseen articles are marked as spam. Thus, mail split
25018 into a spam group is automatically marked as spam.
25020 Identifying spam messages is only half of the Spam package's job. The
25021 second half comes into play whenever you exit a group buffer. At this
25022 point, the Spam package does several things:
25024 First, it calls @dfn{spam and ham processors} to process the articles
25025 according to whether they are spam or ham. There is a pair of spam
25026 and ham processors associated with each spam back end, and what the
25027 processors do depends on the back end. At present, the main role of
25028 spam and ham processors is for dictionary-based spam filters: they add
25029 the contents of the messages in the group to the filter's dictionary,
25030 to improve its ability to detect future spam. The @code{spam-process}
25031 group parameter specifies what spam processors to use. @xref{Spam and
25034 If the spam filter failed to mark a spam message, you can mark it
25035 yourself, so that the message is processed as spam when you exit the
25045 @findex gnus-summary-mark-as-spam
25046 @findex gnus-summary-mark-as-spam
25047 Mark current article as spam, showing it with the @samp{$} mark
25048 (@code{gnus-summary-mark-as-spam}).
25052 Similarly, you can unmark an article if it has been erroneously marked
25053 as spam. @xref{Setting Marks}.
25055 Normally, a ham message found in a non-ham group is not processed as
25056 ham---the rationale is that it should be moved into a ham group for
25057 further processing (see below). However, you can force these articles
25058 to be processed as ham by setting
25059 @code{spam-process-ham-in-spam-groups} and
25060 @code{spam-process-ham-in-nonham-groups}.
25062 @vindex gnus-ham-process-destinations
25063 @vindex gnus-spam-process-destinations
25064 The second thing that the Spam package does when you exit a group is
25065 to move ham articles out of spam groups, and spam articles out of ham
25066 groups. Ham in a spam group is moved to the group specified by the
25067 variable @code{gnus-ham-process-destinations}, or the group parameter
25068 @code{ham-process-destination}. Spam in a ham group is moved to the
25069 group specified by the variable @code{gnus-spam-process-destinations},
25070 or the group parameter @code{spam-process-destination}. If these
25071 variables are not set, the articles are left in their current group.
25072 If an article cannot be moved (e.g., with a read-only backend such
25073 as @acronym{NNTP}), it is copied.
25075 If an article is moved to another group, it is processed again when
25076 you visit the new group. Normally, this is not a problem, but if you
25077 want each article to be processed only once, load the
25078 @code{gnus-registry.el} package and set the variable
25079 @code{spam-log-to-registry} to @code{t}. @xref{Spam Package
25080 Configuration Examples}.
25082 Normally, spam groups ignore @code{gnus-spam-process-destinations}.
25083 However, if you set @code{spam-move-spam-nonspam-groups-only} to
25084 @code{nil}, spam will also be moved out of spam groups, depending on
25085 the @code{spam-process-destination} parameter.
25087 The final thing the Spam package does is to mark spam articles as
25088 expired, which is usually the right thing to do.
25090 If all this seems confusing, don't worry. Soon it will be as natural
25091 as typing Lisp one-liners on a neural interface@dots{} err, sorry, that's
25092 50 years in the future yet. Just trust us, it's not so bad.
25094 @node Filtering Incoming Mail
25095 @subsection Filtering Incoming Mail
25096 @cindex spam filtering
25097 @cindex spam filtering incoming mail
25100 To use the Spam package to filter incoming mail, you must first set up
25101 fancy mail splitting. @xref{Fancy Mail Splitting}. The Spam package
25102 defines a special splitting function that you can add to your fancy
25103 split variable (either @code{nnmail-split-fancy} or
25104 @code{nnimap-split-fancy}, depending on your mail back end):
25110 @vindex spam-split-group
25112 The @code{spam-split} function scans incoming mail according to your
25113 chosen spam back end(s), and sends messages identified as spam to a
25114 spam group. By default, the spam group is a group named @samp{spam},
25115 but you can change this by customizing @code{spam-split-group}. Make
25116 sure the contents of @code{spam-split-group} are an unqualified group
25117 name. For instance, in an @code{nnimap} server @samp{your-server},
25118 the value @samp{spam} means @samp{nnimap+your-server:spam}. The value
25119 @samp{nnimap+server:spam} is therefore wrong---it gives the group
25120 @samp{nnimap+your-server:nnimap+server:spam}.
25122 @code{spam-split} does not modify the contents of messages in any way.
25124 @vindex nnimap-split-download-body
25125 Note for IMAP users: if you use the @code{spam-check-bogofilter},
25126 @code{spam-check-ifile}, and @code{spam-check-stat} spam back ends,
25127 you should also set the variable @code{nnimap-split-download-body}
25128 to @code{t}. These spam back ends are most useful when they can
25129 ``scan'' the full message body. By default, the nnimap back end only
25130 retrieves the message headers; @code{nnimap-split-download-body} tells
25131 it to retrieve the message bodies as well. We don't set this by
25132 default because it will slow @acronym{IMAP} down, and that is not an
25133 appropriate decision to make on behalf of the user. @xref{Splitting
25136 You have to specify one or more spam back ends for @code{spam-split}
25137 to use, by setting the @code{spam-use-*} variables. @xref{Spam Back
25138 Ends}. Normally, @code{spam-split} simply uses all the spam back ends
25139 you enabled in this way. However, you can tell @code{spam-split} to
25140 use only some of them. Why this is useful? Suppose you are using the
25141 @code{spam-use-regex-headers} and @code{spam-use-blackholes} spam back
25142 ends, and the following split rule:
25145 nnimap-split-fancy '(|
25146 (any "ding" "ding")
25148 ;; @r{default mailbox}
25153 The problem is that you want all ding messages to make it to the ding
25154 folder. But that will let obvious spam (for example, spam detected by
25155 SpamAssassin, and @code{spam-use-regex-headers}) through, when it's
25156 sent to the ding list. On the other hand, some messages to the ding
25157 list are from a mail server in the blackhole list, so the invocation
25158 of @code{spam-split} can't be before the ding rule.
25160 The solution is to let SpamAssassin headers supersede ding rules, and
25161 perform the other @code{spam-split} rules (including a second
25162 invocation of the regex-headers check) after the ding rule. This is
25163 done by passing a parameter to @code{spam-split}:
25168 ;; @r{spam detected by @code{spam-use-regex-headers} goes to @samp{regex-spam}}
25169 (: spam-split "regex-spam" 'spam-use-regex-headers)
25170 (any "ding" "ding")
25171 ;; @r{all other spam detected by spam-split goes to @code{spam-split-group}}
25173 ;; @r{default mailbox}
25178 This lets you invoke specific @code{spam-split} checks depending on
25179 your particular needs, and target the results of those checks to a
25180 particular spam group. You don't have to throw all mail into all the
25181 spam tests. Another reason why this is nice is that messages to
25182 mailing lists you have rules for don't have to have resource-intensive
25183 blackhole checks performed on them. You could also specify different
25184 spam checks for your nnmail split vs. your nnimap split. Go crazy.
25186 You should set the @code{spam-use-*} variables for whatever spam back
25187 ends you intend to use. The reason is that when loading
25188 @file{spam.el}, some conditional loading is done depending on what
25189 @code{spam-use-xyz} variables you have set. @xref{Spam Back Ends}.
25191 @c @emph{TODO: spam.el needs to provide a uniform way of training all the
25192 @c statistical databases. Some have that functionality built-in, others
25195 @node Detecting Spam in Groups
25196 @subsection Detecting Spam in Groups
25198 To detect spam when visiting a group, set the group's
25199 @code{spam-autodetect} and @code{spam-autodetect-methods} group
25200 parameters. These are accessible with @kbd{G c} or @kbd{G p}, as
25201 usual (@pxref{Group Parameters}).
25203 You should set the @code{spam-use-*} variables for whatever spam back
25204 ends you intend to use. The reason is that when loading
25205 @file{spam.el}, some conditional loading is done depending on what
25206 @code{spam-use-xyz} variables you have set.
25208 By default, only unseen articles are processed for spam. You can
25209 force Gnus to recheck all messages in the group by setting the
25210 variable @code{spam-autodetect-recheck-messages} to @code{t}.
25212 If you use the @code{spam-autodetect} method of checking for spam, you
25213 can specify different spam detection methods for different groups.
25214 For instance, the @samp{ding} group may have @code{spam-use-BBDB} as
25215 the autodetection method, while the @samp{suspect} group may have the
25216 @code{spam-use-blacklist} and @code{spam-use-bogofilter} methods
25217 enabled. Unlike with @code{spam-split}, you don't have any control
25218 over the @emph{sequence} of checks, but this is probably unimportant.
25220 @node Spam and Ham Processors
25221 @subsection Spam and Ham Processors
25222 @cindex spam filtering
25223 @cindex spam filtering variables
25224 @cindex spam variables
25227 @vindex gnus-spam-process-newsgroups
25228 Spam and ham processors specify special actions to take when you exit
25229 a group buffer. Spam processors act on spam messages, and ham
25230 processors on ham messages. At present, the main role of these
25231 processors is to update the dictionaries of dictionary-based spam back
25232 ends such as Bogofilter (@pxref{Bogofilter}) and the Spam Statistics
25233 package (@pxref{Spam Statistics Filtering}).
25235 The spam and ham processors that apply to each group are determined by
25236 the group's@code{spam-process} group parameter. If this group
25237 parameter is not defined, they are determined by the variable
25238 @code{gnus-spam-process-newsgroups}.
25240 @vindex gnus-spam-newsgroup-contents
25241 Gnus learns from the spam you get. You have to collect your spam in
25242 one or more spam groups, and set or customize the variable
25243 @code{spam-junk-mailgroups} as appropriate. You can also declare
25244 groups to contain spam by setting their group parameter
25245 @code{spam-contents} to @code{gnus-group-spam-classification-spam}, or
25246 by customizing the corresponding variable
25247 @code{gnus-spam-newsgroup-contents}. The @code{spam-contents} group
25248 parameter and the @code{gnus-spam-newsgroup-contents} variable can
25249 also be used to declare groups as @emph{ham} groups if you set their
25250 classification to @code{gnus-group-spam-classification-ham}. If
25251 groups are not classified by means of @code{spam-junk-mailgroups},
25252 @code{spam-contents}, or @code{gnus-spam-newsgroup-contents}, they are
25253 considered @emph{unclassified}. All groups are unclassified by
25256 @vindex gnus-spam-mark
25258 In spam groups, all messages are considered to be spam by default:
25259 they get the @samp{$} mark (@code{gnus-spam-mark}) when you enter the
25260 group. If you have seen a message, had it marked as spam, then
25261 unmarked it, it won't be marked as spam when you enter the group
25262 thereafter. You can disable that behavior, so all unread messages
25263 will get the @samp{$} mark, if you set the
25264 @code{spam-mark-only-unseen-as-spam} parameter to @code{nil}. You
25265 should remove the @samp{$} mark when you are in the group summary
25266 buffer for every message that is not spam after all. To remove the
25267 @samp{$} mark, you can use @kbd{M-u} to ``unread'' the article, or
25268 @kbd{d} for declaring it read the non-spam way. When you leave a
25269 group, all spam-marked (@samp{$}) articles are sent to a spam
25270 processor which will study them as spam samples.
25272 Messages may also be deleted in various other ways, and unless
25273 @code{ham-marks} group parameter gets overridden below, marks @samp{R}
25274 and @samp{r} for default read or explicit delete, marks @samp{X} and
25275 @samp{K} for automatic or explicit kills, as well as mark @samp{Y} for
25276 low scores, are all considered to be associated with articles which
25277 are not spam. This assumption might be false, in particular if you
25278 use kill files or score files as means for detecting genuine spam, you
25279 should then adjust the @code{ham-marks} group parameter.
25282 You can customize this group or topic parameter to be the list of
25283 marks you want to consider ham. By default, the list contains the
25284 deleted, read, killed, kill-filed, and low-score marks (the idea is
25285 that these articles have been read, but are not spam). It can be
25286 useful to also include the tick mark in the ham marks. It is not
25287 recommended to make the unread mark a ham mark, because it normally
25288 indicates a lack of classification. But you can do it, and we'll be
25293 You can customize this group or topic parameter to be the list of
25294 marks you want to consider spam. By default, the list contains only
25295 the spam mark. It is not recommended to change that, but you can if
25296 you really want to.
25299 When you leave @emph{any} group, regardless of its
25300 @code{spam-contents} classification, all spam-marked articles are sent
25301 to a spam processor, which will study these as spam samples. If you
25302 explicit kill a lot, you might sometimes end up with articles marked
25303 @samp{K} which you never saw, and which might accidentally contain
25304 spam. Best is to make sure that real spam is marked with @samp{$},
25307 @vindex gnus-ham-process-destinations
25308 When you leave a @emph{spam} group, all spam-marked articles are
25309 marked as expired after processing with the spam processor. This is
25310 not done for @emph{unclassified} or @emph{ham} groups. Also, any
25311 @strong{ham} articles in a spam group will be moved to a location
25312 determined by either the @code{ham-process-destination} group
25313 parameter or a match in the @code{gnus-ham-process-destinations}
25314 variable, which is a list of regular expressions matched with group
25315 names (it's easiest to customize this variable with @kbd{M-x
25316 customize-variable @key{RET} gnus-ham-process-destinations}). Each
25317 group name list is a standard Lisp list, if you prefer to customize
25318 the variable manually. If the @code{ham-process-destination}
25319 parameter is not set, ham articles are left in place. If the
25320 @code{spam-mark-ham-unread-before-move-from-spam-group} parameter is
25321 set, the ham articles are marked as unread before being moved.
25323 If ham can not be moved---because of a read-only back end such as
25324 @acronym{NNTP}, for example, it will be copied.
25326 Note that you can use multiples destinations per group or regular
25327 expression! This enables you to send your ham to a regular mail
25328 group and to a @emph{ham training} group.
25330 When you leave a @emph{ham} group, all ham-marked articles are sent to
25331 a ham processor, which will study these as non-spam samples.
25333 @vindex spam-process-ham-in-spam-groups
25334 By default the variable @code{spam-process-ham-in-spam-groups} is
25335 @code{nil}. Set it to @code{t} if you want ham found in spam groups
25336 to be processed. Normally this is not done, you are expected instead
25337 to send your ham to a ham group and process it there.
25339 @vindex spam-process-ham-in-nonham-groups
25340 By default the variable @code{spam-process-ham-in-nonham-groups} is
25341 @code{nil}. Set it to @code{t} if you want ham found in non-ham (spam
25342 or unclassified) groups to be processed. Normally this is not done,
25343 you are expected instead to send your ham to a ham group and process
25346 @vindex gnus-spam-process-destinations
25347 When you leave a @emph{ham} or @emph{unclassified} group, all
25348 @strong{spam} articles are moved to a location determined by either
25349 the @code{spam-process-destination} group parameter or a match in the
25350 @code{gnus-spam-process-destinations} variable, which is a list of
25351 regular expressions matched with group names (it's easiest to
25352 customize this variable with @kbd{M-x customize-variable @key{RET}
25353 gnus-spam-process-destinations}). Each group name list is a standard
25354 Lisp list, if you prefer to customize the variable manually. If the
25355 @code{spam-process-destination} parameter is not set, the spam
25356 articles are only expired. The group name is fully qualified, meaning
25357 that if you see @samp{nntp:servername} before the group name in the
25358 group buffer then you need it here as well.
25360 If spam can not be moved---because of a read-only back end such as
25361 @acronym{NNTP}, for example, it will be copied.
25363 Note that you can use multiples destinations per group or regular
25364 expression! This enables you to send your spam to multiple @emph{spam
25367 @vindex spam-log-to-registry
25368 The problem with processing ham and spam is that Gnus doesn't track
25369 this processing by default. Enable the @code{spam-log-to-registry}
25370 variable so @code{spam.el} will use @code{gnus-registry.el} to track
25371 what articles have been processed, and avoid processing articles
25372 multiple times. Keep in mind that if you limit the number of registry
25373 entries, this won't work as well as it does without a limit.
25375 @vindex spam-mark-only-unseen-as-spam
25376 Set this variable if you want only unseen articles in spam groups to
25377 be marked as spam. By default, it is set. If you set it to
25378 @code{nil}, unread articles will also be marked as spam.
25380 @vindex spam-mark-ham-unread-before-move-from-spam-group
25381 Set this variable if you want ham to be unmarked before it is moved
25382 out of the spam group. This is very useful when you use something
25383 like the tick mark @samp{!} to mark ham---the article will be placed
25384 in your @code{ham-process-destination}, unmarked as if it came fresh
25385 from the mail server.
25387 @vindex spam-autodetect-recheck-messages
25388 When autodetecting spam, this variable tells @code{spam.el} whether
25389 only unseen articles or all unread articles should be checked for
25390 spam. It is recommended that you leave it off.
25392 @node Spam Package Configuration Examples
25393 @subsection Spam Package Configuration Examples
25394 @cindex spam filtering
25395 @cindex spam filtering configuration examples
25396 @cindex spam configuration examples
25399 @subsubheading Ted's setup
25401 From Ted Zlatanov <tzz@@lifelogs.com>.
25403 ;; @r{for @code{gnus-registry-split-fancy-with-parent} and spam autodetection}
25404 ;; @r{see @file{gnus-registry.el} for more information}
25405 (gnus-registry-initialize)
25409 spam-log-to-registry t ; @r{for spam autodetection}
25411 spam-use-regex-headers t ; @r{catch X-Spam-Flag (SpamAssassin)}
25412 ;; @r{all groups with @samp{spam} in the name contain spam}
25413 gnus-spam-newsgroup-contents
25414 '(("spam" gnus-group-spam-classification-spam))
25415 ;; @r{see documentation for these}
25416 spam-move-spam-nonspam-groups-only nil
25417 spam-mark-only-unseen-as-spam t
25418 spam-mark-ham-unread-before-move-from-spam-group t
25419 nnimap-split-rule 'nnimap-split-fancy
25420 ;; @r{understand what this does before you copy it to your own setup!}
25421 nnimap-split-fancy '(|
25422 ;; @r{trace references to parents and put in their group}
25423 (: gnus-registry-split-fancy-with-parent)
25424 ;; @r{this will catch server-side SpamAssassin tags}
25425 (: spam-split 'spam-use-regex-headers)
25426 (any "ding" "ding")
25427 ;; @r{note that spam by default will go to @samp{spam}}
25429 ;; @r{default mailbox}
25432 ;; @r{my parameters, set with @kbd{G p}}
25434 ;; @r{all nnml groups, and all nnimap groups except}
25435 ;; @r{@samp{nnimap+mail.lifelogs.com:train} and}
25436 ;; @r{@samp{nnimap+mail.lifelogs.com:spam}: any spam goes to nnimap training,}
25437 ;; @r{because it must have been detected manually}
25439 ((spam-process-destination . "nnimap+mail.lifelogs.com:train"))
25441 ;; @r{all @acronym{NNTP} groups}
25442 ;; @r{autodetect spam with the blacklist and ham with the BBDB}
25443 ((spam-autodetect-methods spam-use-blacklist spam-use-BBDB)
25444 ;; @r{send all spam to the training group}
25445 (spam-process-destination . "nnimap+mail.lifelogs.com:train"))
25447 ;; @r{only some @acronym{NNTP} groups, where I want to autodetect spam}
25448 ((spam-autodetect . t))
25450 ;; @r{my nnimap @samp{nnimap+mail.lifelogs.com:spam} group}
25452 ;; @r{this is a spam group}
25453 ((spam-contents gnus-group-spam-classification-spam)
25455 ;; @r{any spam (which happens when I enter for all unseen messages,}
25456 ;; @r{because of the @code{gnus-spam-newsgroup-contents} setting above), goes to}
25457 ;; @r{@samp{nnimap+mail.lifelogs.com:train} unless I mark it as ham}
25459 (spam-process-destination "nnimap+mail.lifelogs.com:train")
25461 ;; @r{any ham goes to my @samp{nnimap+mail.lifelogs.com:mail} folder, but}
25462 ;; @r{also to my @samp{nnimap+mail.lifelogs.com:trainham} folder for training}
25464 (ham-process-destination "nnimap+mail.lifelogs.com:mail"
25465 "nnimap+mail.lifelogs.com:trainham")
25466 ;; @r{in this group, only @samp{!} marks are ham}
25468 (gnus-ticked-mark))
25469 ;; @r{remembers senders in the blacklist on the way out---this is}
25470 ;; @r{definitely not needed, it just makes me feel better}
25471 (spam-process (gnus-group-spam-exit-processor-blacklist)))
25473 ;; @r{Later, on the @acronym{IMAP} server I use the @samp{train} group for training}
25474 ;; @r{SpamAssassin to recognize spam, and the @samp{trainham} group fora}
25475 ;; @r{recognizing ham---but Gnus has nothing to do with it.}
25479 @subsubheading Using @code{spam.el} on an IMAP server with a statistical filter on the server
25480 From Reiner Steib <reiner.steib@@gmx.de>.
25482 My provider has set up bogofilter (in combination with @acronym{DCC}) on
25483 the mail server (@acronym{IMAP}). Recognized spam goes to
25484 @samp{spam.detected}, the rest goes through the normal filter rules,
25485 i.e. to @samp{some.folder} or to @samp{INBOX}. Training on false
25486 positives or negatives is done by copying or moving the article to
25487 @samp{training.ham} or @samp{training.spam} respectively. A cron job on
25488 the server feeds those to bogofilter with the suitable ham or spam
25489 options and deletes them from the @samp{training.ham} and
25490 @samp{training.spam} folders.
25492 With the following entries in @code{gnus-parameters}, @code{spam.el}
25493 does most of the job for me:
25496 ("nnimap:spam\\.detected"
25497 (gnus-article-sort-functions '(gnus-article-sort-by-chars))
25498 (ham-process-destination "nnimap:INBOX" "nnimap:training.ham")
25499 (spam-contents gnus-group-spam-classification-spam))
25500 ("nnimap:\\(INBOX\\|other-folders\\)"
25501 (spam-process-destination . "nnimap:training.spam")
25502 (spam-contents gnus-group-spam-classification-ham))
25507 @item @b{The Spam folder:}
25509 In the folder @samp{spam.detected}, I have to check for false positives
25510 (i.e. legitimate mails, that were wrongly judged as spam by
25511 bogofilter or DCC).
25513 Because of the @code{gnus-group-spam-classification-spam} entry, all
25514 messages are marked as spam (with @code{$}). When I find a false
25515 positive, I mark the message with some other ham mark
25516 (@code{ham-marks}, @ref{Spam and Ham Processors}). On group exit,
25517 those messages are copied to both groups, @samp{INBOX} (where I want
25518 to have the article) and @samp{training.ham} (for training bogofilter)
25519 and deleted from the @samp{spam.detected} folder.
25521 The @code{gnus-article-sort-by-chars} entry simplifies detection of
25522 false positives for me. I receive lots of worms (sweN, @dots{}), that all
25523 have a similar size. Grouping them by size (i.e. chars) makes finding
25524 other false positives easier. (Of course worms aren't @i{spam}
25525 (@acronym{UCE}, @acronym{UBE}) strictly speaking. Anyhow, bogofilter is
25526 an excellent tool for filtering those unwanted mails for me.)
25528 @item @b{Ham folders:}
25530 In my ham folders, I just hit @kbd{S x}
25531 (@code{gnus-summary-mark-as-spam}) whenever I see an unrecognized spam
25532 mail (false negative). On group exit, those messages are moved to
25533 @samp{training.spam}.
25536 @subsubheading Reporting spam articles in Gmane groups with @code{spam-report.el}
25538 From Reiner Steib <reiner.steib@@gmx.de>.
25540 With following entry in @code{gnus-parameters}, @kbd{S x}
25541 (@code{gnus-summary-mark-as-spam}) marks articles in @code{gmane.*}
25542 groups as spam and reports the to Gmane at group exit:
25546 (spam-process (gnus-group-spam-exit-processor-report-gmane)))
25549 Additionally, I use @code{(setq spam-report-gmane-use-article-number nil)}
25550 because I don't read the groups directly from news.gmane.org, but
25551 through my local news server (leafnode). I.e. the article numbers are
25552 not the same as on news.gmane.org, thus @code{spam-report.el} has to check
25553 the @code{X-Report-Spam} header to find the correct number.
25555 @node Spam Back Ends
25556 @subsection Spam Back Ends
25557 @cindex spam back ends
25559 The spam package offers a variety of back ends for detecting spam.
25560 Each back end defines a set of methods for detecting spam
25561 (@pxref{Filtering Incoming Mail}, @pxref{Detecting Spam in Groups}),
25562 and a pair of spam and ham processors (@pxref{Spam and Ham
25566 * Blacklists and Whitelists::
25567 * BBDB Whitelists::
25568 * Gmane Spam Reporting::
25569 * Anti-spam Hashcash Payments::
25571 * Regular Expressions Header Matching::
25573 * SpamAssassin back end::
25574 * ifile spam filtering::
25575 * Spam Statistics Filtering::
25579 @node Blacklists and Whitelists
25580 @subsubsection Blacklists and Whitelists
25581 @cindex spam filtering
25582 @cindex whitelists, spam filtering
25583 @cindex blacklists, spam filtering
25586 @defvar spam-use-blacklist
25588 Set this variable to @code{t} if you want to use blacklists when
25589 splitting incoming mail. Messages whose senders are in the blacklist
25590 will be sent to the @code{spam-split-group}. This is an explicit
25591 filter, meaning that it acts only on mail senders @emph{declared} to
25596 @defvar spam-use-whitelist
25598 Set this variable to @code{t} if you want to use whitelists when
25599 splitting incoming mail. Messages whose senders are not in the
25600 whitelist will be sent to the next spam-split rule. This is an
25601 explicit filter, meaning that unless someone is in the whitelist, their
25602 messages are not assumed to be spam or ham.
25606 @defvar spam-use-whitelist-exclusive
25608 Set this variable to @code{t} if you want to use whitelists as an
25609 implicit filter, meaning that every message will be considered spam
25610 unless the sender is in the whitelist. Use with care.
25614 @defvar gnus-group-spam-exit-processor-blacklist
25616 Add this symbol to a group's @code{spam-process} parameter by
25617 customizing the group parameters or the
25618 @code{gnus-spam-process-newsgroups} variable. When this symbol is
25619 added to a group's @code{spam-process} parameter, the senders of
25620 spam-marked articles will be added to the blacklist.
25624 Instead of the obsolete
25625 @code{gnus-group-spam-exit-processor-blacklist}, it is recommended
25626 that you use @code{(spam spam-use-blacklist)}. Everything will work
25627 the same way, we promise.
25631 @defvar gnus-group-ham-exit-processor-whitelist
25633 Add this symbol to a group's @code{spam-process} parameter by
25634 customizing the group parameters or the
25635 @code{gnus-spam-process-newsgroups} variable. When this symbol is
25636 added to a group's @code{spam-process} parameter, the senders of
25637 ham-marked articles in @emph{ham} groups will be added to the
25642 Instead of the obsolete
25643 @code{gnus-group-ham-exit-processor-whitelist}, it is recommended
25644 that you use @code{(ham spam-use-whitelist)}. Everything will work
25645 the same way, we promise.
25649 Blacklists are lists of regular expressions matching addresses you
25650 consider to be spam senders. For instance, to block mail from any
25651 sender at @samp{vmadmin.com}, you can put @samp{vmadmin.com} in your
25652 blacklist. You start out with an empty blacklist. Blacklist entries
25653 use the Emacs regular expression syntax.
25655 Conversely, whitelists tell Gnus what addresses are considered
25656 legitimate. All messages from whitelisted addresses are considered
25657 non-spam. Also see @ref{BBDB Whitelists}. Whitelist entries use the
25658 Emacs regular expression syntax.
25660 The blacklist and whitelist file locations can be customized with the
25661 @code{spam-directory} variable (@file{~/News/spam} by default), or
25662 the @code{spam-whitelist} and @code{spam-blacklist} variables
25663 directly. The whitelist and blacklist files will by default be in the
25664 @code{spam-directory} directory, named @file{whitelist} and
25665 @file{blacklist} respectively.
25667 @node BBDB Whitelists
25668 @subsubsection BBDB Whitelists
25669 @cindex spam filtering
25670 @cindex BBDB whitelists, spam filtering
25671 @cindex BBDB, spam filtering
25674 @defvar spam-use-BBDB
25676 Analogous to @code{spam-use-whitelist} (@pxref{Blacklists and
25677 Whitelists}), but uses the BBDB as the source of whitelisted
25678 addresses, without regular expressions. You must have the BBDB loaded
25679 for @code{spam-use-BBDB} to work properly. Messages whose senders are
25680 not in the BBDB will be sent to the next spam-split rule. This is an
25681 explicit filter, meaning that unless someone is in the BBDB, their
25682 messages are not assumed to be spam or ham.
25686 @defvar spam-use-BBDB-exclusive
25688 Set this variable to @code{t} if you want to use the BBDB as an
25689 implicit filter, meaning that every message will be considered spam
25690 unless the sender is in the BBDB. Use with care. Only sender
25691 addresses in the BBDB will be allowed through; all others will be
25692 classified as spammers.
25694 While @code{spam-use-BBDB-exclusive} @emph{can} be used as an alias
25695 for @code{spam-use-BBDB} as far as @code{spam.el} is concerned, it is
25696 @emph{not} a separate back end. If you set
25697 @code{spam-use-BBDB-exclusive} to t, @emph{all} your BBDB splitting
25702 @defvar gnus-group-ham-exit-processor-BBDB
25704 Add this symbol to a group's @code{spam-process} parameter by
25705 customizing the group parameters or the
25706 @code{gnus-spam-process-newsgroups} variable. When this symbol is
25707 added to a group's @code{spam-process} parameter, the senders of
25708 ham-marked articles in @emph{ham} groups will be added to the
25713 Instead of the obsolete
25714 @code{gnus-group-ham-exit-processor-BBDB}, it is recommended
25715 that you use @code{(ham spam-use-BBDB)}. Everything will work
25716 the same way, we promise.
25720 @node Gmane Spam Reporting
25721 @subsubsection Gmane Spam Reporting
25722 @cindex spam reporting
25723 @cindex Gmane, spam reporting
25724 @cindex Gmane, spam reporting
25727 @defvar gnus-group-spam-exit-processor-report-gmane
25729 Add this symbol to a group's @code{spam-process} parameter by
25730 customizing the group parameters or the
25731 @code{gnus-spam-process-newsgroups} variable. When this symbol is
25732 added to a group's @code{spam-process} parameter, the spam-marked
25733 articles groups will be reported to the Gmane administrators via a
25736 Gmane can be found at @uref{http://gmane.org}.
25740 Instead of the obsolete
25741 @code{gnus-group-spam-exit-processor-report-gmane}, it is recommended
25742 that you use @code{(spam spam-use-gmane)}. Everything will work the
25743 same way, we promise.
25747 @defvar spam-report-gmane-use-article-number
25749 This variable is @code{t} by default. Set it to @code{nil} if you are
25750 running your own news server, for instance, and the local article
25751 numbers don't correspond to the Gmane article numbers. When
25752 @code{spam-report-gmane-use-article-number} is @code{nil},
25753 @code{spam-report.el} will fetch the number from the article headers.
25757 @defvar spam-report-user-mail-address
25759 Mail address exposed in the User-Agent spam reports to Gmane. It allows
25760 the Gmane administrators to contact you in case of misreports. The
25761 default is @code{user-mail-address}.
25765 @node Anti-spam Hashcash Payments
25766 @subsubsection Anti-spam Hashcash Payments
25767 @cindex spam filtering
25768 @cindex hashcash, spam filtering
25771 @defvar spam-use-hashcash
25773 Similar to @code{spam-use-whitelist} (@pxref{Blacklists and
25774 Whitelists}), but uses hashcash tokens for whitelisting messages
25775 instead of the sender address. Messages without a hashcash payment
25776 token will be sent to the next spam-split rule. This is an explicit
25777 filter, meaning that unless a hashcash token is found, the messages
25778 are not assumed to be spam or ham.
25783 @subsubsection Blackholes
25784 @cindex spam filtering
25785 @cindex blackholes, spam filtering
25788 @defvar spam-use-blackholes
25790 This option is disabled by default. You can let Gnus consult the
25791 blackhole-type distributed spam processing systems (DCC, for instance)
25792 when you set this option. The variable @code{spam-blackhole-servers}
25793 holds the list of blackhole servers Gnus will consult. The current
25794 list is fairly comprehensive, but make sure to let us know if it
25795 contains outdated servers.
25797 The blackhole check uses the @code{dig.el} package, but you can tell
25798 @code{spam.el} to use @code{dns.el} instead for better performance if
25799 you set @code{spam-use-dig} to @code{nil}. It is not recommended at
25800 this time to set @code{spam-use-dig} to @code{nil} despite the
25801 possible performance improvements, because some users may be unable to
25802 use it, but you can try it and see if it works for you.
25806 @defvar spam-blackhole-servers
25808 The list of servers to consult for blackhole checks.
25812 @defvar spam-blackhole-good-server-regex
25814 A regular expression for IPs that should not be checked against the
25815 blackhole server list. When set to @code{nil}, it has no effect.
25819 @defvar spam-use-dig
25821 Use the @code{dig.el} package instead of the @code{dns.el} package.
25822 The default setting of @code{t} is recommended.
25826 Blackhole checks are done only on incoming mail. There is no spam or
25827 ham processor for blackholes.
25829 @node Regular Expressions Header Matching
25830 @subsubsection Regular Expressions Header Matching
25831 @cindex spam filtering
25832 @cindex regular expressions header matching, spam filtering
25835 @defvar spam-use-regex-headers
25837 This option is disabled by default. You can let Gnus check the
25838 message headers against lists of regular expressions when you set this
25839 option. The variables @code{spam-regex-headers-spam} and
25840 @code{spam-regex-headers-ham} hold the list of regular expressions.
25841 Gnus will check against the message headers to determine if the
25842 message is spam or ham, respectively.
25846 @defvar spam-regex-headers-spam
25848 The list of regular expressions that, when matched in the headers of
25849 the message, positively identify it as spam.
25853 @defvar spam-regex-headers-ham
25855 The list of regular expressions that, when matched in the headers of
25856 the message, positively identify it as ham.
25860 Regular expression header checks are done only on incoming mail.
25861 There is no specific spam or ham processor for regular expressions.
25864 @subsubsection Bogofilter
25865 @cindex spam filtering
25866 @cindex bogofilter, spam filtering
25869 @defvar spam-use-bogofilter
25871 Set this variable if you want @code{spam-split} to use Eric Raymond's
25874 With a minimum of care for associating the @samp{$} mark for spam
25875 articles only, Bogofilter training all gets fairly automatic. You
25876 should do this until you get a few hundreds of articles in each
25877 category, spam or not. The command @kbd{S t} in summary mode, either
25878 for debugging or for curiosity, shows the @emph{spamicity} score of
25879 the current article (between 0.0 and 1.0).
25881 Bogofilter determines if a message is spam based on a specific
25882 threshold. That threshold can be customized, consult the Bogofilter
25885 If the @code{bogofilter} executable is not in your path, Bogofilter
25886 processing will be turned off.
25888 You should not enable this if you use @code{spam-use-bogofilter-headers}.
25897 @findex spam-bogofilter-score
25898 Get the Bogofilter spamicity score (@code{spam-bogofilter-score}).
25901 @defvar spam-use-bogofilter-headers
25903 Set this variable if you want @code{spam-split} to use Eric Raymond's
25904 speedy Bogofilter, looking only at the message headers. It works
25905 similarly to @code{spam-use-bogofilter}, but the @code{X-Bogosity} header
25906 must be in the message already. Normally you would do this with a
25907 procmail recipe or something similar; consult the Bogofilter
25908 installation documents for details.
25910 You should not enable this if you use @code{spam-use-bogofilter}.
25914 @defvar gnus-group-spam-exit-processor-bogofilter
25915 Add this symbol to a group's @code{spam-process} parameter by
25916 customizing the group parameters or the
25917 @code{gnus-spam-process-newsgroups} variable. When this symbol is
25918 added to a group's @code{spam-process} parameter, spam-marked articles
25919 will be added to the Bogofilter spam database.
25923 Instead of the obsolete
25924 @code{gnus-group-spam-exit-processor-bogofilter}, it is recommended
25925 that you use @code{(spam spam-use-bogofilter)}. Everything will work
25926 the same way, we promise.
25929 @defvar gnus-group-ham-exit-processor-bogofilter
25930 Add this symbol to a group's @code{spam-process} parameter by
25931 customizing the group parameters or the
25932 @code{gnus-spam-process-newsgroups} variable. When this symbol is
25933 added to a group's @code{spam-process} parameter, the ham-marked
25934 articles in @emph{ham} groups will be added to the Bogofilter database
25935 of non-spam messages.
25939 Instead of the obsolete
25940 @code{gnus-group-ham-exit-processor-bogofilter}, it is recommended
25941 that you use @code{(ham spam-use-bogofilter)}. Everything will work
25942 the same way, we promise.
25945 @defvar spam-bogofilter-database-directory
25947 This is the directory where Bogofilter will store its databases. It
25948 is not specified by default, so Bogofilter will use its own default
25949 database directory.
25953 The Bogofilter mail classifier is similar to @command{ifile} in intent and
25954 purpose. A ham and a spam processor are provided, plus the
25955 @code{spam-use-bogofilter} and @code{spam-use-bogofilter-headers}
25956 variables to indicate to spam-split that Bogofilter should either be
25957 used, or has already been used on the article. The 0.9.2.1 version of
25958 Bogofilter was used to test this functionality.
25960 @node SpamAssassin back end
25961 @subsubsection SpamAssassin back end
25962 @cindex spam filtering
25963 @cindex spamassassin, spam filtering
25966 @defvar spam-use-spamassassin
25968 Set this variable if you want @code{spam-split} to use SpamAssassin.
25970 SpamAssassin assigns a score to each article based on a set of rules
25971 and tests, including a Bayesian filter. The Bayesian filter can be
25972 trained by associating the @samp{$} mark for spam articles. The
25973 spam score can be viewed by using the command @kbd{S t} in summary
25976 If you set this variable, each article will be processed by
25977 SpamAssassin when @code{spam-split} is called. If your mail is
25978 preprocessed by SpamAssassin, and you want to just use the
25979 SpamAssassin headers, set @code{spam-use-spamassassin-headers}
25982 You should not enable this if you use
25983 @code{spam-use-spamassassin-headers}.
25987 @defvar spam-use-spamassassin-headers
25989 Set this variable if your mail is preprocessed by SpamAssassin and
25990 want @code{spam-split} to split based on the SpamAssassin headers.
25992 You should not enable this if you use @code{spam-use-spamassassin}.
25996 @defvar spam-spamassassin-program
25998 This variable points to the SpamAssassin executable. If you have
25999 @code{spamd} running, you can set this variable to the @code{spamc}
26000 executable for faster processing. See the SpamAssassin documentation
26001 for more information on @code{spamd}/@code{spamc}.
26005 SpamAssassin is a powerful and flexible spam filter that uses a wide
26006 variety of tests to identify spam. A ham and a spam processors are
26007 provided, plus the @code{spam-use-spamassassin} and
26008 @code{spam-use-spamassassin-headers} variables to indicate to
26009 spam-split that SpamAssassin should be either used, or has already
26010 been used on the article. The 2.63 version of SpamAssassin was used
26011 to test this functionality.
26013 @node ifile spam filtering
26014 @subsubsection ifile spam filtering
26015 @cindex spam filtering
26016 @cindex ifile, spam filtering
26019 @defvar spam-use-ifile
26021 Enable this variable if you want @code{spam-split} to use @command{ifile}, a
26022 statistical analyzer similar to Bogofilter.
26026 @defvar spam-ifile-all-categories
26028 Enable this variable if you want @code{spam-use-ifile} to give you all
26029 the ifile categories, not just spam/non-spam. If you use this, make
26030 sure you train ifile as described in its documentation.
26034 @defvar spam-ifile-spam-category
26036 This is the category of spam messages as far as ifile is concerned.
26037 The actual string used is irrelevant, but you probably want to leave
26038 the default value of @samp{spam}.
26041 @defvar spam-ifile-database
26043 This is the filename for the ifile database. It is not specified by
26044 default, so ifile will use its own default database name.
26048 The ifile mail classifier is similar to Bogofilter in intent and
26049 purpose. A ham and a spam processor are provided, plus the
26050 @code{spam-use-ifile} variable to indicate to spam-split that ifile
26051 should be used. The 1.2.1 version of ifile was used to test this
26054 @node Spam Statistics Filtering
26055 @subsubsection Spam Statistics Filtering
26056 @cindex spam filtering
26057 @cindex spam-stat, spam filtering
26061 This back end uses the Spam Statistics Emacs Lisp package to perform
26062 statistics-based filtering (@pxref{Spam Statistics Package}). Before
26063 using this, you may want to perform some additional steps to
26064 initialize your Spam Statistics dictionary. @xref{Creating a
26065 spam-stat dictionary}.
26067 @defvar spam-use-stat
26071 @defvar gnus-group-spam-exit-processor-stat
26072 Add this symbol to a group's @code{spam-process} parameter by
26073 customizing the group parameters or the
26074 @code{gnus-spam-process-newsgroups} variable. When this symbol is
26075 added to a group's @code{spam-process} parameter, the spam-marked
26076 articles will be added to the spam-stat database of spam messages.
26080 Instead of the obsolete
26081 @code{gnus-group-spam-exit-processor-stat}, it is recommended
26082 that you use @code{(spam spam-use-stat)}. Everything will work
26083 the same way, we promise.
26086 @defvar gnus-group-ham-exit-processor-stat
26087 Add this symbol to a group's @code{spam-process} parameter by
26088 customizing the group parameters or the
26089 @code{gnus-spam-process-newsgroups} variable. When this symbol is
26090 added to a group's @code{spam-process} parameter, the ham-marked
26091 articles in @emph{ham} groups will be added to the spam-stat database
26092 of non-spam messages.
26096 Instead of the obsolete
26097 @code{gnus-group-ham-exit-processor-stat}, it is recommended
26098 that you use @code{(ham spam-use-stat)}. Everything will work
26099 the same way, we promise.
26102 This enables @code{spam.el} to cooperate with @file{spam-stat.el}.
26103 @file{spam-stat.el} provides an internal (Lisp-only) spam database,
26104 which unlike ifile or Bogofilter does not require external programs.
26105 A spam and a ham processor, and the @code{spam-use-stat} variable for
26106 @code{spam-split} are provided.
26109 @subsubsection Using SpamOracle with Gnus
26110 @cindex spam filtering
26114 An easy way to filter out spam is to use SpamOracle. SpamOracle is an
26115 statistical mail filtering tool written by Xavier Leroy and needs to be
26116 installed separately.
26118 There are several ways to use SpamOracle with Gnus. In all cases, your
26119 mail is piped through SpamOracle in its @emph{mark} mode. SpamOracle will
26120 then enter an @samp{X-Spam} header indicating whether it regards the
26121 mail as a spam mail or not.
26123 One possibility is to run SpamOracle as a @code{:prescript} from the
26124 @xref{Mail Source Specifiers}, (@pxref{SpamAssassin}). This method has
26125 the advantage that the user can see the @emph{X-Spam} headers.
26127 The easiest method is to make @file{spam.el} (@pxref{Spam Package})
26130 @vindex spam-use-spamoracle
26131 To enable SpamOracle usage by @code{spam.el}, set the variable
26132 @code{spam-use-spamoracle} to @code{t} and configure the
26133 @code{nnmail-split-fancy} or @code{nnimap-split-fancy}. @xref{Spam
26134 Package}. In this example the @samp{INBOX} of an nnimap server is
26135 filtered using SpamOracle. Mails recognized as spam mails will be
26136 moved to @code{spam-split-group}, @samp{Junk} in this case. Ham
26137 messages stay in @samp{INBOX}:
26140 (setq spam-use-spamoracle t
26141 spam-split-group "Junk"
26142 nnimap-split-inbox '("INBOX")
26143 nnimap-split-rule 'nnimap-split-fancy
26144 nnimap-split-fancy '(| (: spam-split) "INBOX"))
26147 @defvar spam-use-spamoracle
26148 Set to @code{t} if you want Gnus to enable spam filtering using
26152 @defvar spam-spamoracle-binary
26153 Gnus uses the SpamOracle binary called @file{spamoracle} found in the
26154 user's PATH. Using the variable @code{spam-spamoracle-binary}, this
26158 @defvar spam-spamoracle-database
26159 By default, SpamOracle uses the file @file{~/.spamoracle.db} as a database to
26160 store its analysis. This is controlled by the variable
26161 @code{spam-spamoracle-database} which defaults to @code{nil}. That means
26162 the default SpamOracle database will be used. In case you want your
26163 database to live somewhere special, set
26164 @code{spam-spamoracle-database} to this path.
26167 SpamOracle employs a statistical algorithm to determine whether a
26168 message is spam or ham. In order to get good results, meaning few
26169 false hits or misses, SpamOracle needs training. SpamOracle learns
26170 the characteristics of your spam mails. Using the @emph{add} mode
26171 (training mode) one has to feed good (ham) and spam mails to
26172 SpamOracle. This can be done by pressing @kbd{|} in the Summary
26173 buffer and pipe the mail to a SpamOracle process or using
26174 @file{spam.el}'s spam- and ham-processors, which is much more
26175 convenient. For a detailed description of spam- and ham-processors,
26176 @xref{Spam Package}.
26178 @defvar gnus-group-spam-exit-processor-spamoracle
26179 Add this symbol to a group's @code{spam-process} parameter by
26180 customizing the group parameter or the
26181 @code{gnus-spam-process-newsgroups} variable. When this symbol is added
26182 to a group's @code{spam-process} parameter, spam-marked articles will be
26183 sent to SpamOracle as spam samples.
26187 Instead of the obsolete
26188 @code{gnus-group-spam-exit-processor-spamoracle}, it is recommended
26189 that you use @code{(spam spam-use-spamoracle)}. Everything will work
26190 the same way, we promise.
26193 @defvar gnus-group-ham-exit-processor-spamoracle
26194 Add this symbol to a group's @code{spam-process} parameter by
26195 customizing the group parameter or the
26196 @code{gnus-spam-process-newsgroups} variable. When this symbol is added
26197 to a group's @code{spam-process} parameter, the ham-marked articles in
26198 @emph{ham} groups will be sent to the SpamOracle as samples of ham
26203 Instead of the obsolete
26204 @code{gnus-group-ham-exit-processor-spamoracle}, it is recommended
26205 that you use @code{(ham spam-use-spamoracle)}. Everything will work
26206 the same way, we promise.
26209 @emph{Example:} These are the Group Parameters of a group that has been
26210 classified as a ham group, meaning that it should only contain ham
26213 ((spam-contents gnus-group-spam-classification-ham)
26214 (spam-process ((ham spam-use-spamoracle)
26215 (spam spam-use-spamoracle))))
26217 For this group the @code{spam-use-spamoracle} is installed for both
26218 ham and spam processing. If the group contains spam message
26219 (e.g. because SpamOracle has not had enough sample messages yet) and
26220 the user marks some messages as spam messages, these messages will be
26221 processed by SpamOracle. The processor sends the messages to
26222 SpamOracle as new samples for spam.
26224 @node Extending the Spam package
26225 @subsection Extending the Spam package
26226 @cindex spam filtering
26227 @cindex spam elisp package, extending
26228 @cindex extending the spam elisp package
26230 Say you want to add a new back end called blackbox. For filtering
26231 incoming mail, provide the following:
26239 (defvar spam-use-blackbox nil
26240 "True if blackbox should be used.")
26243 Write @code{spam-check-blackbox} if Blackbox can check incoming mail.
26245 Write @code{spam-blackbox-register-routine} and
26246 @code{spam-blackbox-unregister-routine} using the bogofilter
26247 register/unregister routines as a start, or other restister/unregister
26248 routines more appropriate to Blackbox, if Blackbox can
26249 register/unregister spam and ham.
26254 The @code{spam-check-blackbox} function should return @samp{nil} or
26255 @code{spam-split-group}, observing the other conventions. See the
26256 existing @code{spam-check-*} functions for examples of what you can
26257 do, and stick to the template unless you fully understand the reasons
26262 For processing spam and ham messages, provide the following:
26269 Note you don't have to provide a spam or a ham processor. Only
26270 provide them if Blackbox supports spam or ham processing.
26272 Also, ham and spam processors are being phased out as single
26273 variables. Instead the form @code{(spam spam-use-blackbox)} or
26274 @code{(ham spam-use-blackbox)} is favored. For now, spam/ham
26275 processor variables are still around but they won't be for long.
26278 (defvar gnus-group-spam-exit-processor-blackbox "blackbox-spam"
26279 "The Blackbox summary exit spam processor.
26280 Only applicable to spam groups.")
26282 (defvar gnus-group-ham-exit-processor-blackbox "blackbox-ham"
26283 "The whitelist summary exit ham processor.
26284 Only applicable to non-spam (unclassified and ham) groups.")
26293 (const :tag "Spam: Blackbox" (spam spam-use-blackbox))
26294 (const :tag "Ham: Blackbox" (ham spam-use-blackbox))
26296 to the @code{spam-process} group parameter in @code{gnus.el}. Make
26297 sure you do it twice, once for the parameter and once for the
26298 variable customization.
26302 (variable-item spam-use-blackbox)
26304 to the @code{spam-autodetect-methods} group parameter in
26305 @code{gnus.el} if Blackbox can check incoming mail for spam contents.
26307 Finally, use the appropriate @code{spam-install-*-backend} function in
26308 @code{spam.el}. Here are the available functions.
26314 @code{spam-install-backend-alias}
26316 This function will simply install an alias for a back end that does
26317 everything like the original back end. It is currently only used to
26318 make @code{spam-use-BBDB-exclusive} act like @code{spam-use-BBDB}.
26321 @code{spam-install-nocheck-backend}
26323 This function installs a back end that has no check function, but can
26324 register/unregister ham or spam. The @code{spam-use-gmane} back end is
26328 @code{spam-install-checkonly-backend}
26330 This function will install a back end that can only check incoming mail
26331 for spam contents. It can't register or unregister messages.
26332 @code{spam-use-blackholes} and @code{spam-use-hashcash} are such
26336 @code{spam-install-statistical-checkonly-backend}
26338 This function installs a statistical back end (one which requires the
26339 full body of a message to check it) that can only check incoming mail
26340 for contents. @code{spam-use-regex-body} is such a filter.
26343 @code{spam-install-statistical-backend}
26345 This function install a statistical back end with incoming checks and
26346 registration/unregistration routines. @code{spam-use-bogofilter} is
26350 @code{spam-install-backend}
26352 This is the most normal back end installation, where a back end that can
26353 check and register/unregister messages is set up without statistical
26354 abilities. The @code{spam-use-BBDB} is such a back end.
26357 @code{spam-install-mover-backend}
26359 Mover back ends are internal to @code{spam.el} and specifically move
26360 articles around when the summary is exited. You will very probably
26361 never install such a back end.
26366 @node Spam Statistics Package
26367 @subsection Spam Statistics Package
26368 @cindex Paul Graham
26369 @cindex Graham, Paul
26370 @cindex naive Bayesian spam filtering
26371 @cindex Bayesian spam filtering, naive
26372 @cindex spam filtering, naive Bayesian
26374 Paul Graham has written an excellent essay about spam filtering using
26375 statistics: @uref{http://www.paulgraham.com/spam.html,A Plan for
26376 Spam}. In it he describes the inherent deficiency of rule-based
26377 filtering as used by SpamAssassin, for example: Somebody has to write
26378 the rules, and everybody else has to install these rules. You are
26379 always late. It would be much better, he argues, to filter mail based
26380 on whether it somehow resembles spam or non-spam. One way to measure
26381 this is word distribution. He then goes on to describe a solution
26382 that checks whether a new mail resembles any of your other spam mails
26385 The basic idea is this: Create a two collections of your mail, one
26386 with spam, one with non-spam. Count how often each word appears in
26387 either collection, weight this by the total number of mails in the
26388 collections, and store this information in a dictionary. For every
26389 word in a new mail, determine its probability to belong to a spam or a
26390 non-spam mail. Use the 15 most conspicuous words, compute the total
26391 probability of the mail being spam. If this probability is higher
26392 than a certain threshold, the mail is considered to be spam.
26394 The Spam Statistics package adds support to Gnus for this kind of
26395 filtering. It can be used as one of the back ends of the Spam package
26396 (@pxref{Spam Package}), or by itself.
26398 Before using the Spam Statistics package, you need to set it up.
26399 First, you need two collections of your mail, one with spam, one with
26400 non-spam. Then you need to create a dictionary using these two
26401 collections, and save it. And last but not least, you need to use
26402 this dictionary in your fancy mail splitting rules.
26405 * Creating a spam-stat dictionary::
26406 * Splitting mail using spam-stat::
26407 * Low-level interface to the spam-stat dictionary::
26410 @node Creating a spam-stat dictionary
26411 @subsubsection Creating a spam-stat dictionary
26413 Before you can begin to filter spam based on statistics, you must
26414 create these statistics based on two mail collections, one with spam,
26415 one with non-spam. These statistics are then stored in a dictionary
26416 for later use. In order for these statistics to be meaningful, you
26417 need several hundred emails in both collections.
26419 Gnus currently supports only the nnml back end for automated dictionary
26420 creation. The nnml back end stores all mails in a directory, one file
26421 per mail. Use the following:
26423 @defun spam-stat-process-spam-directory
26424 Create spam statistics for every file in this directory. Every file
26425 is treated as one spam mail.
26428 @defun spam-stat-process-non-spam-directory
26429 Create non-spam statistics for every file in this directory. Every
26430 file is treated as one non-spam mail.
26433 Usually you would call @code{spam-stat-process-spam-directory} on a
26434 directory such as @file{~/Mail/mail/spam} (this usually corresponds to
26435 the group @samp{nnml:mail.spam}), and you would call
26436 @code{spam-stat-process-non-spam-directory} on a directory such as
26437 @file{~/Mail/mail/misc} (this usually corresponds to the group
26438 @samp{nnml:mail.misc}).
26440 When you are using @acronym{IMAP}, you won't have the mails available
26441 locally, so that will not work. One solution is to use the Gnus Agent
26442 to cache the articles. Then you can use directories such as
26443 @file{"~/News/agent/nnimap/mail.yourisp.com/personal_spam"} for
26444 @code{spam-stat-process-spam-directory}. @xref{Agent as Cache}.
26447 This variable holds the hash-table with all the statistics---the
26448 dictionary we have been talking about. For every word in either
26449 collection, this hash-table stores a vector describing how often the
26450 word appeared in spam and often it appeared in non-spam mails.
26453 If you want to regenerate the statistics from scratch, you need to
26454 reset the dictionary.
26456 @defun spam-stat-reset
26457 Reset the @code{spam-stat} hash-table, deleting all the statistics.
26460 When you are done, you must save the dictionary. The dictionary may
26461 be rather large. If you will not update the dictionary incrementally
26462 (instead, you will recreate it once a month, for example), then you
26463 can reduce the size of the dictionary by deleting all words that did
26464 not appear often enough or that do not clearly belong to only spam or
26465 only non-spam mails.
26467 @defun spam-stat-reduce-size
26468 Reduce the size of the dictionary. Use this only if you do not want
26469 to update the dictionary incrementally.
26472 @defun spam-stat-save
26473 Save the dictionary.
26476 @defvar spam-stat-file
26477 The filename used to store the dictionary. This defaults to
26478 @file{~/.spam-stat.el}.
26481 @node Splitting mail using spam-stat
26482 @subsubsection Splitting mail using spam-stat
26484 This section describes how to use the Spam statistics
26485 @emph{independently} of the @xref{Spam Package}.
26487 First, add the following to your @file{~/.gnus.el} file:
26490 (require 'spam-stat)
26494 This will load the necessary Gnus code, and the dictionary you
26497 Next, you need to adapt your fancy splitting rules: You need to
26498 determine how to use @code{spam-stat}. The following examples are for
26499 the nnml back end. Using the nnimap back end works just as well. Just
26500 use @code{nnimap-split-fancy} instead of @code{nnmail-split-fancy}.
26502 In the simplest case, you only have two groups, @samp{mail.misc} and
26503 @samp{mail.spam}. The following expression says that mail is either
26504 spam or it should go into @samp{mail.misc}. If it is spam, then
26505 @code{spam-stat-split-fancy} will return @samp{mail.spam}.
26508 (setq nnmail-split-fancy
26509 `(| (: spam-stat-split-fancy)
26513 @defvar spam-stat-split-fancy-spam-group
26514 The group to use for spam. Default is @samp{mail.spam}.
26517 If you also filter mail with specific subjects into other groups, use
26518 the following expression. Only mails not matching the regular
26519 expression are considered potential spam.
26522 (setq nnmail-split-fancy
26523 `(| ("Subject" "\\bspam-stat\\b" "mail.emacs")
26524 (: spam-stat-split-fancy)
26528 If you want to filter for spam first, then you must be careful when
26529 creating the dictionary. Note that @code{spam-stat-split-fancy} must
26530 consider both mails in @samp{mail.emacs} and in @samp{mail.misc} as
26531 non-spam, therefore both should be in your collection of non-spam
26532 mails, when creating the dictionary!
26535 (setq nnmail-split-fancy
26536 `(| (: spam-stat-split-fancy)
26537 ("Subject" "\\bspam-stat\\b" "mail.emacs")
26541 You can combine this with traditional filtering. Here, we move all
26542 HTML-only mails into the @samp{mail.spam.filtered} group. Note that since
26543 @code{spam-stat-split-fancy} will never see them, the mails in
26544 @samp{mail.spam.filtered} should be neither in your collection of spam mails,
26545 nor in your collection of non-spam mails, when creating the
26549 (setq nnmail-split-fancy
26550 `(| ("Content-Type" "text/html" "mail.spam.filtered")
26551 (: spam-stat-split-fancy)
26552 ("Subject" "\\bspam-stat\\b" "mail.emacs")
26557 @node Low-level interface to the spam-stat dictionary
26558 @subsubsection Low-level interface to the spam-stat dictionary
26560 The main interface to using @code{spam-stat}, are the following functions:
26562 @defun spam-stat-buffer-is-spam
26563 Called in a buffer, that buffer is considered to be a new spam mail.
26564 Use this for new mail that has not been processed before.
26567 @defun spam-stat-buffer-is-no-spam
26568 Called in a buffer, that buffer is considered to be a new non-spam
26569 mail. Use this for new mail that has not been processed before.
26572 @defun spam-stat-buffer-change-to-spam
26573 Called in a buffer, that buffer is no longer considered to be normal
26574 mail but spam. Use this to change the status of a mail that has
26575 already been processed as non-spam.
26578 @defun spam-stat-buffer-change-to-non-spam
26579 Called in a buffer, that buffer is no longer considered to be spam but
26580 normal mail. Use this to change the status of a mail that has already
26581 been processed as spam.
26584 @defun spam-stat-save
26585 Save the hash table to the file. The filename used is stored in the
26586 variable @code{spam-stat-file}.
26589 @defun spam-stat-load
26590 Load the hash table from a file. The filename used is stored in the
26591 variable @code{spam-stat-file}.
26594 @defun spam-stat-score-word
26595 Return the spam score for a word.
26598 @defun spam-stat-score-buffer
26599 Return the spam score for a buffer.
26602 @defun spam-stat-split-fancy
26603 Use this function for fancy mail splitting. Add the rule @samp{(:
26604 spam-stat-split-fancy)} to @code{nnmail-split-fancy}
26607 Make sure you load the dictionary before using it. This requires the
26608 following in your @file{~/.gnus.el} file:
26611 (require 'spam-stat)
26615 Typical test will involve calls to the following functions:
26618 Reset: (setq spam-stat (make-hash-table :test 'equal))
26619 Learn spam: (spam-stat-process-spam-directory "~/Mail/mail/spam")
26620 Learn non-spam: (spam-stat-process-non-spam-directory "~/Mail/mail/misc")
26621 Save table: (spam-stat-save)
26622 File size: (nth 7 (file-attributes spam-stat-file))
26623 Number of words: (hash-table-count spam-stat)
26624 Test spam: (spam-stat-test-directory "~/Mail/mail/spam")
26625 Test non-spam: (spam-stat-test-directory "~/Mail/mail/misc")
26626 Reduce table size: (spam-stat-reduce-size)
26627 Save table: (spam-stat-save)
26628 File size: (nth 7 (file-attributes spam-stat-file))
26629 Number of words: (hash-table-count spam-stat)
26630 Test spam: (spam-stat-test-directory "~/Mail/mail/spam")
26631 Test non-spam: (spam-stat-test-directory "~/Mail/mail/misc")
26634 Here is how you would create your dictionary:
26637 Reset: (setq spam-stat (make-hash-table :test 'equal))
26638 Learn spam: (spam-stat-process-spam-directory "~/Mail/mail/spam")
26639 Learn non-spam: (spam-stat-process-non-spam-directory "~/Mail/mail/misc")
26640 Repeat for any other non-spam group you need...
26641 Reduce table size: (spam-stat-reduce-size)
26642 Save table: (spam-stat-save)
26645 @node The Gnus Registry
26646 @section The Gnus Registry
26651 The Gnus registry is a package that tracks messages by their
26652 Message-ID across all backends. This allows Gnus users to do several
26653 cool things, be the envy of the locals, get free haircuts, and be
26654 experts on world issues. Well, maybe not all of those, but the
26655 features are pretty cool.
26657 Although they will be explained in detail shortly, here's a quick list
26658 of said features in case your attention span is... never mind.
26662 Split messages to their parent
26664 This keeps discussions in the same group. You can use the subject and
26665 the sender in addition to the Message-ID. Several strategies are
26669 Store custom flags and keywords
26671 The registry can store custom flags and keywords for a message. For
26672 instance, you can mark a message ``To-Do'' this way and the flag will
26673 persist whether the message is in the nnimap, nnml, nnmaildir,
26677 Store arbitrary data
26679 Through a simple ELisp API, the registry can remember any data for a
26680 message. A built-in inverse map, when activated, allows quick lookups
26681 of all messages matching a particular set of criteria.
26686 * Fancy splitting to parent::
26687 * Store custom flags and keywords::
26688 * Store arbitrary data::
26694 Fortunately, setting up the Gnus registry is pretty easy:
26697 (setq gnus-registry-max-entries 2500
26698 gnus-registry-use-long-group-names t)
26700 (gnus-registry-initialize)
26703 This adds registry saves to Gnus newsrc saves (which happen on exit
26704 and when you press @kbd{s} from the @code{*Group*} buffer. It also
26705 adds registry calls to article actions in Gnus (copy, move, etc.) so
26706 it's not easy to undo the initialization. See
26707 @code{gnus-registry-initialize} for the gory details.
26709 Here are other settings used by the author of the registry (understand
26710 what they do before you copy them blindly).
26714 gnus-registry-split-strategy 'majority
26715 gnus-registry-ignored-groups '(("nntp" t)
26719 gnus-registry-max-entries 500000
26720 gnus-registry-use-long-group-names t
26721 gnus-registry-track-extra '(sender subject))
26724 They say: keep a lot of messages around, use long group names, track
26725 messages by sender and subject (not just parent Message-ID), and when
26726 the registry splits incoming mail, use a majority rule to decide where
26727 messages should go if there's more than one possibility. In addition,
26728 the registry should ignore messages in groups that match ``nntp'',
26729 ``nnrss'', ``spam'', or ``train.''
26731 You are doubtless impressed by all this, but you ask: ``I am a Gnus
26732 user, I customize to live. Give me more.'' Here you go, these are
26733 the general settings.
26735 @defvar gnus-registry-unfollowed-groups
26736 The groups that will not be followed by
26737 @code{gnus-registry-split-fancy-with-parent}. They will still be
26738 remembered by the registry. This is a list of regular expressions.
26741 @defvar gnus-registry-ignored-groups
26742 The groups that will not be remembered by the registry. This is a
26743 list of regular expressions, also available through Group/Topic
26744 customization (so you can ignore or keep a specific group or a whole
26748 @defvar gnus-registry-use-long-group-names
26749 Whether the registry will use long group names. It's recommended to
26750 set this to @code{t}, although everything works if you don't. Future
26751 functionality will require it.
26754 @defvar gnus-registry-max-entries
26755 The number (an integer or @code{nil} for unlimited) of entries the
26756 registry will keep.
26759 @defvar gnus-registry-cache-file
26760 The file where the registry will be stored between Gnus sessions.
26763 @node Fancy splitting to parent
26764 @subsection Fancy splitting to parent
26766 Simply put, this lets you put followup e-mail where it belongs.
26768 Every message has a Message-ID, which is unique, and the registry
26769 remembers it. When the message is moved or copied, the registry will
26770 notice this and offer the new group as a choice to the splitting
26773 When a followup is made, usually it mentions the original message's
26774 Message-ID in the headers. The registry knows this and uses that
26775 mention to find the group where the original message lives. You only
26776 have to put a rule like this:
26779 (setq nnimap-my-split-fancy '(|
26781 ;; split to parent: you need this
26782 (: gnus-registry-split-fancy-with-parent)
26784 ;; other rules, as an example
26790 in your fancy split setup. In addition, you may want to customize the
26791 following variables.
26793 @defvar gnus-registry-track-extra
26794 This is a list of symbols, so it's best to change it from the
26795 Customize interface. By default it's @code{nil}, but you may want to
26796 track @code{subject} and @code{sender} as well when splitting by parent.
26797 It may work for you. It can be annoying if your mail flow is large and
26798 people don't stick to the same groups.
26801 @defvar gnus-registry-split-strategy
26802 This is a symbol, so it's best to change it from the Customize
26803 interface. By default it's @code{nil}, but you may want to set it to
26804 @code{majority} or @code{first} to split by sender or subject based on
26805 the majority of matches or on the first found.
26808 @node Store custom flags and keywords
26809 @subsection Store custom flags and keywords
26811 The registry lets you set custom flags and keywords per message. You
26812 can use the Gnus->Registry Marks menu or the @kbd{M M x} keyboard
26813 shortcuts, where @code{x} is the first letter of the mark's name.
26815 @defvar gnus-registry-marks
26816 The custom marks that the registry can use. You can modify the
26817 default list, if you like. If you do, you'll have to exit Emacs
26818 before they take effect (you can also unload the registry and reload
26819 it or evaluate the specific macros you'll need, but you probably don't
26820 want to bother). Use the Customize interface to modify the list.
26822 By default this list has the @code{Important}, @code{Work},
26823 @code{Personal}, @code{To-Do}, and @code{Later} marks. They all have
26824 keyboard shortcuts like @kbd{M M i} for Important, using the first
26828 @defun gnus-registry-mark-article
26829 Call this function to mark an article with a custom registry mark. It
26830 will offer the available marks for completion.
26833 @node Store arbitrary data
26834 @subsection Store arbitrary data
26836 The registry has a simple API that uses a Message-ID as the key to
26837 store arbitrary data (as long as it can be converted to a list for
26840 @defun gnus-registry-store-extra-entry (id key value)
26841 Store @code{value} in the extra data key @code{key} for message
26845 @defun gnus-registry-delete-extra-entry (id key)
26846 Delete the extra data key @code{key} for message @code{id}.
26849 @defun gnus-registry-fetch-extra (id key)
26850 Get the extra data key @code{key} for message @code{id}.
26853 @defvar gnus-registry-extra-entries-precious
26854 If any extra entries are precious, their presence will make the
26855 registry keep the whole entry forever, even if there are no groups for
26856 the Message-ID and if the size limit of the registry is reached. By
26857 default this is just @code{(marks)} so the custom registry marks are
26862 @section Interaction with other modes
26867 @code{gnus-dired-minor-mode} provides some useful functions for dired
26868 buffers. It is enabled with
26870 (add-hook 'dired-mode-hook 'turn-on-gnus-dired-mode)
26875 @findex gnus-dired-attach
26876 @cindex attachments, selection via dired
26877 Send dired's marked files as an attachment (@code{gnus-dired-attach}).
26878 You will be prompted for a message buffer.
26881 @findex gnus-dired-find-file-mailcap
26882 Visit a file according to the appropriate mailcap entry
26883 (@code{gnus-dired-find-file-mailcap}). With prefix, open file in a new
26887 @findex gnus-dired-print
26888 Print file according to the mailcap entry (@code{gnus-dired-print}). If
26889 there is no print command, print in a PostScript image.
26892 @node Various Various
26893 @section Various Various
26899 @item gnus-home-directory
26900 @vindex gnus-home-directory
26901 All Gnus file and directory variables will be initialized from this
26902 variable, which defaults to @file{~/}.
26904 @item gnus-directory
26905 @vindex gnus-directory
26906 Most Gnus storage file and directory variables will be initialized from
26907 this variable, which defaults to the @env{SAVEDIR} environment
26908 variable, or @file{~/News/} if that variable isn't set.
26910 Note that Gnus is mostly loaded when the @file{~/.gnus.el} file is read.
26911 This means that other directory variables that are initialized from this
26912 variable won't be set properly if you set this variable in
26913 @file{~/.gnus.el}. Set this variable in @file{.emacs} instead.
26915 @item gnus-default-directory
26916 @vindex gnus-default-directory
26917 Not related to the above variable at all---this variable says what the
26918 default directory of all Gnus buffers should be. If you issue commands
26919 like @kbd{C-x C-f}, the prompt you'll get starts in the current buffer's
26920 default directory. If this variable is @code{nil} (which is the
26921 default), the default directory will be the default directory of the
26922 buffer you were in when you started Gnus.
26925 @vindex gnus-verbose
26926 This variable is an integer between zero and ten. The higher the value,
26927 the more messages will be displayed. If this variable is zero, Gnus
26928 will never flash any messages, if it is seven (which is the default),
26929 most important messages will be shown, and if it is ten, Gnus won't ever
26930 shut up, but will flash so many messages it will make your head swim.
26932 @item gnus-verbose-backends
26933 @vindex gnus-verbose-backends
26934 This variable works the same way as @code{gnus-verbose}, but it applies
26935 to the Gnus back ends instead of Gnus proper.
26937 @item gnus-add-timestamp-to-message
26938 @vindex gnus-add-timestamp-to-message
26939 This variable controls whether to add timestamps to messages that are
26940 controlled by @code{gnus-verbose} and @code{gnus-verbose-backends} and
26941 are issued. The default value is @code{nil} which means never to add
26942 timestamp. If it is @code{log}, add timestamps to only the messages
26943 that go into the @samp{*Messages*} buffer (in XEmacs, it is the
26944 @w{@samp{ *Message-Log*}} buffer). If it is neither @code{nil} nor
26945 @code{log}, add timestamps not only to log messages but also to the ones
26946 displayed in the echo area.
26948 @item nnheader-max-head-length
26949 @vindex nnheader-max-head-length
26950 When the back ends read straight heads of articles, they all try to read
26951 as little as possible. This variable (default 8192) specifies
26952 the absolute max length the back ends will try to read before giving up
26953 on finding a separator line between the head and the body. If this
26954 variable is @code{nil}, there is no upper read bound. If it is
26955 @code{t}, the back ends won't try to read the articles piece by piece,
26956 but read the entire articles. This makes sense with some versions of
26957 @code{ange-ftp} or @code{efs}.
26959 @item nnheader-head-chop-length
26960 @vindex nnheader-head-chop-length
26961 This variable (default 2048) says how big a piece of each article to
26962 read when doing the operation described above.
26964 @item nnheader-file-name-translation-alist
26965 @vindex nnheader-file-name-translation-alist
26967 @cindex invalid characters in file names
26968 @cindex characters in file names
26969 This is an alist that says how to translate characters in file names.
26970 For instance, if @samp{:} is invalid as a file character in file names
26971 on your system (you OS/2 user you), you could say something like:
26975 (setq nnheader-file-name-translation-alist
26980 In fact, this is the default value for this variable on OS/2 and MS
26981 Windows (phooey) systems.
26983 @item gnus-hidden-properties
26984 @vindex gnus-hidden-properties
26985 This is a list of properties to use to hide ``invisible'' text. It is
26986 @code{(invisible t intangible t)} by default on most systems, which
26987 makes invisible text invisible and intangible.
26989 @item gnus-parse-headers-hook
26990 @vindex gnus-parse-headers-hook
26991 A hook called before parsing headers. It can be used, for instance, to
26992 gather statistics on the headers fetched, or perhaps you'd like to prune
26993 some headers. I don't see why you'd want that, though.
26995 @item gnus-shell-command-separator
26996 @vindex gnus-shell-command-separator
26997 String used to separate two shell commands. The default is @samp{;}.
26999 @item gnus-invalid-group-regexp
27000 @vindex gnus-invalid-group-regexp
27002 Regexp to match ``invalid'' group names when querying user for a group
27003 name. The default value catches some @strong{really} invalid group
27004 names who could possibly mess up Gnus internally (like allowing
27005 @samp{:} in a group name, which is normally used to delimit method and
27008 @acronym{IMAP} users might want to allow @samp{/} in group names though.
27010 @item gnus-safe-html-newsgroups
27011 @vindex gnus-safe-html-newsgroups
27012 Groups in which links in html articles are considered all safe. The
27013 value may be a regexp matching those groups, a list of group names, or
27014 @code{nil}. This overrides @code{mm-w3m-safe-url-regexp}. The default
27015 value is @code{"\\`nnrss[+:]"}. This is effective only when emacs-w3m
27016 renders html articles, i.e., in the case @code{mm-text-html-renderer} is
27017 set to @code{w3m}. @xref{Display Customization, ,Display Customization,
27018 emacs-mime, The Emacs MIME Manual}.
27025 Well, that's the manual---you can get on with your life now. Keep in
27026 touch. Say hello to your cats from me.
27028 My @strong{ghod}---I just can't stand goodbyes. Sniffle.
27030 Ol' Charles Reznikoff said it pretty well, so I leave the floor to him:
27036 Not because of victories @*
27039 but for the common sunshine,@*
27041 the largess of the spring.
27045 but for the day's work done@*
27046 as well as I was able;@*
27047 not for a seat upon the dais@*
27048 but at the common table.@*
27053 @chapter Appendices
27056 * XEmacs:: Requirements for installing under XEmacs.
27057 * History:: How Gnus got where it is today.
27058 * On Writing Manuals:: Why this is not a beginner's guide.
27059 * Terminology:: We use really difficult, like, words here.
27060 * Customization:: Tailoring Gnus to your needs.
27061 * Troubleshooting:: What you might try if things do not work.
27062 * Gnus Reference Guide:: Rilly, rilly technical stuff.
27063 * Emacs for Heathens:: A short introduction to Emacsian terms.
27064 * Frequently Asked Questions:: The Gnus FAQ
27071 @cindex installing under XEmacs
27073 XEmacs is distributed as a collection of packages. You should install
27074 whatever packages the Gnus XEmacs package requires. The current
27075 requirements are @samp{gnus}, @samp{mail-lib}, @samp{xemacs-base},
27076 @samp{eterm}, @samp{sh-script}, @samp{net-utils}, @samp{os-utils},
27077 @samp{dired}, @samp{mh-e}, @samp{sieve}, @samp{ps-print}, @samp{W3},
27078 @samp{pgg}, @samp{mailcrypt}, @samp{ecrypto}, and @samp{sasl}.
27085 @sc{gnus} was written by Masanobu @sc{Umeda}. When autumn crept up in
27086 '94, Lars Magne Ingebrigtsen grew bored and decided to rewrite Gnus.
27088 If you want to investigate the person responsible for this outrage,
27089 you can point your (feh!) web browser to
27090 @uref{http://quimby.gnus.org/}. This is also the primary
27091 distribution point for the new and spiffy versions of Gnus, and is
27092 known as The Site That Destroys Newsrcs And Drives People Mad.
27094 During the first extended alpha period of development, the new Gnus was
27095 called ``(ding) Gnus''. @dfn{(ding)} is, of course, short for
27096 @dfn{ding is not Gnus}, which is a total and utter lie, but who cares?
27097 (Besides, the ``Gnus'' in this abbreviation should probably be
27098 pronounced ``news'' as @sc{Umeda} intended, which makes it a more
27099 appropriate name, don't you think?)
27101 In any case, after spending all that energy on coming up with a new and
27102 spunky name, we decided that the name was @emph{too} spunky, so we
27103 renamed it back again to ``Gnus''. But in mixed case. ``Gnus'' vs.
27104 ``@sc{gnus}''. New vs. old.
27107 * Gnus Versions:: What Gnus versions have been released.
27108 * Other Gnus Versions:: Other Gnus versions that also have been released.
27109 * Why?:: What's the point of Gnus?
27110 * Compatibility:: Just how compatible is Gnus with @sc{gnus}?
27111 * Conformity:: Gnus tries to conform to all standards.
27112 * Emacsen:: Gnus can be run on a few modern Emacsen.
27113 * Gnus Development:: How Gnus is developed.
27114 * Contributors:: Oodles of people.
27115 * New Features:: Pointers to some of the new stuff in Gnus.
27119 @node Gnus Versions
27120 @subsection Gnus Versions
27122 @cindex September Gnus
27124 @cindex Quassia Gnus
27125 @cindex Pterodactyl Gnus
27128 @cindex Gnus versions
27130 The first ``proper'' release of Gnus 5 was done in November 1995 when it
27131 was included in the Emacs 19.30 distribution (132 (ding) Gnus releases
27132 plus 15 Gnus 5.0 releases).
27134 In May 1996 the next Gnus generation (aka. ``September Gnus'' (after 99
27135 releases)) was released under the name ``Gnus 5.2'' (40 releases).
27137 On July 28th 1996 work on Red Gnus was begun, and it was released on
27138 January 25th 1997 (after 84 releases) as ``Gnus 5.4'' (67 releases).
27140 On September 13th 1997, Quassia Gnus was started and lasted 37 releases.
27141 It was released as ``Gnus 5.6'' on March 8th 1998 (46 releases).
27143 Gnus 5.6 begat Pterodactyl Gnus on August 29th 1998 and was released as
27144 ``Gnus 5.8'' (after 99 releases and a CVS repository) on December 3rd
27147 On the 26th of October 2000, Oort Gnus was begun and was released as
27148 Gnus 5.10 on May 1st 2003 (24 releases).
27150 On the January 4th 2004, No Gnus was begun.
27152 On April 19, 2010 Gnus development was moved to Git. See
27153 http://git.gnus.org for details (http://www.gnus.org will be updated
27154 with the information when possible).
27156 If you happen upon a version of Gnus that has a prefixed name --
27157 ``(ding) Gnus'', ``September Gnus'', ``Red Gnus'', ``Quassia Gnus'',
27158 ``Pterodactyl Gnus'', ``Oort Gnus'', ``No Gnus'' -- don't panic.
27159 Don't let it know that you're frightened. Back away. Slowly. Whatever
27160 you do, don't run. Walk away, calmly, until you're out of its reach.
27161 Find a proper released version of Gnus and snuggle up to that instead.
27164 @node Other Gnus Versions
27165 @subsection Other Gnus Versions
27168 In addition to the versions of Gnus which have had their releases
27169 coordinated by Lars, one major development has been Semi-gnus from
27170 Japan. It's based on a library called @acronym{SEMI}, which provides
27171 @acronym{MIME} capabilities.
27173 These Gnusae are based mainly on Gnus 5.6 and Pterodactyl Gnus.
27174 Collectively, they are called ``Semi-gnus'', and different strains are
27175 called T-gnus, ET-gnus, Nana-gnus and Chaos. These provide powerful
27176 @acronym{MIME} and multilingualization things, especially important for
27183 What's the point of Gnus?
27185 I want to provide a ``rad'', ``happening'', ``way cool'' and ``hep''
27186 newsreader, that lets you do anything you can think of. That was my
27187 original motivation, but while working on Gnus, it has become clear to
27188 me that this generation of newsreaders really belong in the stone age.
27189 Newsreaders haven't developed much since the infancy of the net. If the
27190 volume continues to rise with the current rate of increase, all current
27191 newsreaders will be pretty much useless. How do you deal with
27192 newsgroups that have thousands of new articles each day? How do you
27193 keep track of millions of people who post?
27195 Gnus offers no real solutions to these questions, but I would very much
27196 like to see Gnus being used as a testing ground for new methods of
27197 reading and fetching news. Expanding on @sc{Umeda}-san's wise decision
27198 to separate the newsreader from the back ends, Gnus now offers a simple
27199 interface for anybody who wants to write new back ends for fetching mail
27200 and news from different sources. I have added hooks for customizations
27201 everywhere I could imagine it being useful. By doing so, I'm inviting
27202 every one of you to explore and invent.
27204 May Gnus never be complete. @kbd{C-u 100 M-x all-hail-emacs} and
27205 @kbd{C-u 100 M-x all-hail-xemacs}.
27208 @node Compatibility
27209 @subsection Compatibility
27211 @cindex compatibility
27212 Gnus was designed to be fully compatible with @sc{gnus}. Almost all key
27213 bindings have been kept. More key bindings have been added, of course,
27214 but only in one or two obscure cases have old bindings been changed.
27219 @center In a cloud bones of steel.
27223 All commands have kept their names. Some internal functions have changed
27226 The @code{gnus-uu} package has changed drastically. @xref{Decoding
27229 One major compatibility question is the presence of several summary
27230 buffers. All variables relevant while reading a group are
27231 buffer-local to the summary buffer they belong in. Although many
27232 important variables have their values copied into their global
27233 counterparts whenever a command is executed in the summary buffer, this
27234 change might lead to incorrect values being used unless you are careful.
27236 All code that relies on knowledge of @sc{gnus} internals will probably
27237 fail. To take two examples: Sorting @code{gnus-newsrc-alist} (or
27238 changing it in any way, as a matter of fact) is strictly verboten. Gnus
27239 maintains a hash table that points to the entries in this alist (which
27240 speeds up many functions), and changing the alist directly will lead to
27244 @cindex highlighting
27245 Old hilit19 code does not work at all. In fact, you should probably
27246 remove all hilit code from all Gnus hooks
27247 (@code{gnus-group-prepare-hook} and @code{gnus-summary-prepare-hook}).
27248 Gnus provides various integrated functions for highlighting. These are
27249 faster and more accurate. To make life easier for everybody, Gnus will
27250 by default remove all hilit calls from all hilit hooks. Uncleanliness!
27253 Packages like @code{expire-kill} will no longer work. As a matter of
27254 fact, you should probably remove all old @sc{gnus} packages (and other
27255 code) when you start using Gnus. More likely than not, Gnus already
27256 does what you have written code to make @sc{gnus} do. (Snicker.)
27258 Even though old methods of doing things are still supported, only the
27259 new methods are documented in this manual. If you detect a new method of
27260 doing something while reading this manual, that does not mean you have
27261 to stop doing it the old way.
27263 Gnus understands all @sc{gnus} startup files.
27265 @kindex M-x gnus-bug
27267 @cindex reporting bugs
27269 Overall, a casual user who hasn't written much code that depends on
27270 @sc{gnus} internals should suffer no problems. If problems occur,
27271 please let me know by issuing that magic command @kbd{M-x gnus-bug}.
27273 @vindex gnus-bug-create-help-buffer
27274 If you are in the habit of sending bug reports @emph{very} often, you
27275 may find the helpful help buffer annoying after a while. If so, set
27276 @code{gnus-bug-create-help-buffer} to @code{nil} to avoid having it pop
27281 @subsection Conformity
27283 No rebels without a clue here, ma'am. We conform to all standards known
27284 to (wo)man. Except for those standards and/or conventions we disagree
27292 There are no known breaches of this standard.
27296 There are no known breaches of this standard, either.
27298 @item Son-of-RFC 1036
27299 @cindex Son-of-RFC 1036
27300 We do have some breaches to this one.
27306 These are considered to be ``vanity headers'', while I consider them
27307 to be consumer information. After seeing so many badly formatted
27308 articles coming from @code{tin} and @code{Netscape} I know not to use
27309 either of those for posting articles. I would not have known that if
27310 it wasn't for the @code{X-Newsreader} header.
27315 USEFOR is an IETF working group writing a successor to RFC 1036, based
27316 on Son-of-RFC 1036. They have produced a number of drafts proposing
27317 various changes to the format of news articles. The Gnus towers will
27318 look into implementing the changes when the draft is accepted as an RFC.
27320 @item MIME - RFC 2045-2049 etc
27321 @cindex @acronym{MIME}
27322 All the various @acronym{MIME} RFCs are supported.
27324 @item Disposition Notifications - RFC 2298
27325 Message Mode is able to request notifications from the receiver.
27327 @item PGP - RFC 1991 and RFC 2440
27330 RFC 1991 is the original @acronym{PGP} message specification,
27331 published as an informational RFC. RFC 2440 was the follow-up, now
27332 called Open PGP, and put on the Standards Track. Both document a
27333 non-@acronym{MIME} aware @acronym{PGP} format. Gnus supports both
27334 encoding (signing and encryption) and decoding (verification and
27337 @item PGP/MIME - RFC 2015/3156
27338 RFC 2015 (superseded by 3156 which references RFC 2440 instead of RFC
27339 1991) describes the @acronym{MIME}-wrapping around the RFC 1991/2440 format.
27340 Gnus supports both encoding and decoding.
27342 @item S/MIME - RFC 2633
27343 RFC 2633 describes the @acronym{S/MIME} format.
27345 @item IMAP - RFC 1730/2060, RFC 2195, RFC 2086, RFC 2359, RFC 2595, RFC 1731
27346 RFC 1730 is @acronym{IMAP} version 4, updated somewhat by RFC 2060
27347 (@acronym{IMAP} 4 revision 1). RFC 2195 describes CRAM-MD5
27348 authentication for @acronym{IMAP}. RFC 2086 describes access control
27349 lists (ACLs) for @acronym{IMAP}. RFC 2359 describes a @acronym{IMAP}
27350 protocol enhancement. RFC 2595 describes the proper @acronym{TLS}
27351 integration (STARTTLS) with @acronym{IMAP}. RFC 1731 describes the
27352 GSSAPI/Kerberos4 mechanisms for @acronym{IMAP}.
27356 If you ever notice Gnus acting non-compliant with regards to the texts
27357 mentioned above, don't hesitate to drop a note to Gnus Towers and let us
27362 @subsection Emacsen
27368 This version of Gnus should work on:
27376 XEmacs 21.4 and up.
27380 This Gnus version will absolutely not work on any Emacsen older than
27381 that. Not reliably, at least. Older versions of Gnus may work on older
27382 Emacs versions. Particularly, Gnus 5.10.8 should also work on Emacs
27383 20.7 and XEmacs 21.1.
27385 @c No-merge comment: The paragraph added in v5-10 here must not be
27388 @node Gnus Development
27389 @subsection Gnus Development
27391 Gnus is developed in a two-phased cycle. The first phase involves much
27392 discussion on the development mailing list @samp{ding@@gnus.org}, where people
27393 propose changes and new features, post patches and new back ends. This
27394 phase is called the @dfn{alpha} phase, since the Gnusae released in this
27395 phase are @dfn{alpha releases}, or (perhaps more commonly in other
27396 circles) @dfn{snapshots}. During this phase, Gnus is assumed to be
27397 unstable and should not be used by casual users. Gnus alpha releases
27398 have names like ``Oort Gnus'' and ``No Gnus''. @xref{Gnus Versions}.
27400 After futzing around for 10-100 alpha releases, Gnus is declared
27401 @dfn{frozen}, and only bug fixes are applied. Gnus loses the prefix,
27402 and is called things like ``Gnus 5.10.1'' instead. Normal people are
27403 supposed to be able to use these, and these are mostly discussed on the
27404 @samp{gnu.emacs.gnus} newsgroup. This newgroup is mirrored to the
27405 mailing list @samp{info-gnus-english@@gnu.org} which is carried on Gmane
27406 as @samp{gmane.emacs.gnus.user}. These releases are finally integrated
27410 @vindex mail-source-delete-incoming
27411 Some variable defaults differ between alpha Gnusae and released Gnusae,
27412 in particular, @code{mail-source-delete-incoming}. This is to prevent
27413 lossage of mail if an alpha release hiccups while handling the mail.
27414 @xref{Mail Source Customization}.
27416 The division of discussion between the ding mailing list and the Gnus
27417 newsgroup is not purely based on publicity concerns. It's true that
27418 having people write about the horrible things that an alpha Gnus release
27419 can do (sometimes) in a public forum may scare people off, but more
27420 importantly, talking about new experimental features that have been
27421 introduced may confuse casual users. New features are frequently
27422 introduced, fiddled with, and judged to be found wanting, and then
27423 either discarded or totally rewritten. People reading the mailing list
27424 usually keep up with these rapid changes, while people on the newsgroup
27425 can't be assumed to do so.
27427 So if you have problems with or questions about the alpha versions,
27428 direct those to the ding mailing list @samp{ding@@gnus.org}. This list
27429 is also available on Gmane as @samp{gmane.emacs.gnus.general}.
27432 @vindex mail-source-delete-incoming
27433 Some variable defaults differ between alpha Gnusae and released Gnusae,
27434 in particular, @code{mail-source-delete-incoming}. This is to prevent
27435 lossage of mail if an alpha release hiccups while handling the mail.
27436 @xref{Mail Source Customization}.
27439 @subsection Contributors
27440 @cindex contributors
27442 The new Gnus version couldn't have been done without the help of all the
27443 people on the (ding) mailing list. Every day for over a year I have
27444 gotten billions of nice bug reports from them, filling me with joy,
27445 every single one of them. Smooches. The people on the list have been
27446 tried beyond endurance, what with my ``oh, that's a neat idea <type
27447 type>, yup, I'll release it right away <ship off> no wait, that doesn't
27448 work at all <type type>, yup, I'll ship that one off right away <ship
27449 off> no, wait, that absolutely does not work'' policy for releases.
27450 Micro$oft---bah. Amateurs. I'm @emph{much} worse. (Or is that
27451 ``worser''? ``much worser''? ``worsest''?)
27453 I would like to take this opportunity to thank the Academy for@dots{} oops,
27459 Masanobu @sc{Umeda}---the writer of the original @sc{gnus}.
27462 Shenghuo Zhu---uudecode.el, mm-uu.el, rfc1843.el, webmail.el,
27463 nnwarchive and many, many other things connected with @acronym{MIME} and
27464 other types of en/decoding, as well as general bug fixing, new
27465 functionality and stuff.
27468 Per Abrahamsen---custom, scoring, highlighting and @sc{soup} code (as
27469 well as numerous other things).
27472 Luis Fernandes---design and graphics.
27475 Joe Reiss---creator of the smiley faces.
27478 Justin Sheehy---the @acronym{FAQ} maintainer.
27481 Erik Naggum---help, ideas, support, code and stuff.
27484 Wes Hardaker---@file{gnus-picon.el} and the manual section on
27485 @dfn{picons} (@pxref{Picons}).
27488 Kim-Minh Kaplan---further work on the picon code.
27491 Brad Miller---@file{gnus-gl.el} and the GroupLens manual section.
27494 Sudish Joseph---innumerable bug fixes.
27497 Ilja Weis---@file{gnus-topic.el}.
27500 Steven L. Baur---lots and lots and lots of bugs detections and fixes.
27503 Vladimir Alexiev---the refcard and reference booklets.
27506 Felix Lee & Jamie Zawinski---I stole some pieces from the XGnus
27507 distribution by Felix Lee and JWZ.
27510 Scott Byer---@file{nnfolder.el} enhancements & rewrite.
27513 Peter Mutsaers---orphan article scoring code.
27516 Ken Raeburn---POP mail support.
27519 Hallvard B Furuseth---various bits and pieces, especially dealing with
27523 Brian Edmonds---@file{gnus-bbdb.el}.
27526 David Moore---rewrite of @file{nnvirtual.el} and many other things.
27529 Kevin Davidson---came up with the name @dfn{ding}, so blame him.
27532 Fran@,{c}ois Pinard---many, many interesting and thorough bug reports, as
27533 well as autoconf support.
27537 This manual was proof-read by Adrian Aichner, with Ricardo Nassif, Mark
27538 Borges, and Jost Krieger proof-reading parts of the manual.
27540 The following people have contributed many patches and suggestions:
27555 Jason L. Tibbitts, III,
27557 Katsumi Yamaoka, @c Yamaoka
27561 Also thanks to the following for patches and stuff:
27571 Alexei V. Barantsev,
27586 Massimo Campostrini,
27591 Jae-you Chung, @c ?
27592 James H. Cloos, Jr.,
27596 Andrew J. Cosgriff,
27599 Geoffrey T. Dairiki,
27605 Michael Welsh Duggan,
27610 Enami Tsugutomo, @c Enami
27614 Nelson Jose dos Santos Ferreira,
27622 Arne Georg Gleditsch,
27624 Michelangelo Grigni,
27628 Kenichi Handa, @c Handa
27630 Yoshiki Hayashi, @c Hayashi
27632 Hisashige Kenji, @c Hisashige
27640 Fran@,{c}ois Felix Ingrand,
27641 Tatsuya Ichikawa, @c Ichikawa
27642 Ishikawa Ichiro, @c Ishikawa
27644 Iwamuro Motonori, @c Iwamuro
27654 Peter Skov Knudsen,
27655 Shuhei Kobayashi, @c Kobayashi
27657 Koseki Yoshinori, @c Koseki
27658 Thor Kristoffersen,
27661 Seokchan Lee, @c Lee
27679 Morioka Tomohiko, @c Morioka
27680 Erik Toubro Nielsen,
27687 Masaharu Onishi, @c Onishi
27692 Jens-Ulrik Holger Petersen,
27696 John McClary Prevost,
27702 Lars Balker Rasmussen,
27707 Christian von Roques,
27710 Wolfgang Rupprecht,
27717 Philippe Schnoebelen,
27719 Randal L. Schwartz,
27733 Kiyokazu Suto, @c Suto
27738 Tozawa Akihiko, @c Tozawa
27758 For a full overview of what each person has done, the ChangeLogs
27759 included in the Gnus alpha distributions should give ample reading
27760 (550kB and counting).
27762 Apologies to everybody that I've forgotten, of which there are many, I'm
27765 Gee, that's quite a list of people. I guess that must mean that there
27766 actually are people who are using Gnus. Who'd'a thunk it!
27770 @subsection New Features
27771 @cindex new features
27774 * ding Gnus:: New things in Gnus 5.0/5.1, the first new Gnus.
27775 * September Gnus:: The Thing Formally Known As Gnus 5.2/5.3.
27776 * Red Gnus:: Third time best---Gnus 5.4/5.5.
27777 * Quassia Gnus:: Two times two is four, or Gnus 5.6/5.7.
27778 * Pterodactyl Gnus:: Pentad also starts with P, AKA Gnus 5.8/5.9.
27779 * Oort Gnus:: It's big. It's far out. Gnus 5.10/5.11.
27780 * No Gnus:: Very punny.
27783 These lists are, of course, just @emph{short} overviews of the
27784 @emph{most} important new features. No, really. There are tons more.
27785 Yes, we have feeping creaturism in full effect.
27788 @subsubsection (ding) Gnus
27790 New features in Gnus 5.0/5.1:
27795 The look of all buffers can be changed by setting format-like variables
27796 (@pxref{Group Buffer Format} and @pxref{Summary Buffer Format}).
27799 Local spool and several @acronym{NNTP} servers can be used at once
27800 (@pxref{Select Methods}).
27803 You can combine groups into virtual groups (@pxref{Virtual Groups}).
27806 You can read a number of different mail formats (@pxref{Getting Mail}).
27807 All the mail back ends implement a convenient mail expiry scheme
27808 (@pxref{Expiring Mail}).
27811 Gnus can use various strategies for gathering threads that have lost
27812 their roots (thereby gathering loose sub-threads into one thread) or it
27813 can go back and retrieve enough headers to build a complete thread
27814 (@pxref{Customizing Threading}).
27817 Killed groups can be displayed in the group buffer, and you can read
27818 them as well (@pxref{Listing Groups}).
27821 Gnus can do partial group updates---you do not have to retrieve the
27822 entire active file just to check for new articles in a few groups
27823 (@pxref{The Active File}).
27826 Gnus implements a sliding scale of subscribedness to groups
27827 (@pxref{Group Levels}).
27830 You can score articles according to any number of criteria
27831 (@pxref{Scoring}). You can even get Gnus to find out how to score
27832 articles for you (@pxref{Adaptive Scoring}).
27835 Gnus maintains a dribble buffer that is auto-saved the normal Emacs
27836 manner, so it should be difficult to lose much data on what you have
27837 read if your machine should go down (@pxref{Auto Save}).
27840 Gnus now has its own startup file (@file{~/.gnus.el}) to avoid
27841 cluttering up the @file{.emacs} file.
27844 You can set the process mark on both groups and articles and perform
27845 operations on all the marked items (@pxref{Process/Prefix}).
27848 You can grep through a subset of groups and create a group from the
27849 results (@pxref{Kibozed Groups}).
27852 You can list subsets of groups according to, well, anything
27853 (@pxref{Listing Groups}).
27856 You can browse foreign servers and subscribe to groups from those
27857 servers (@pxref{Browse Foreign Server}).
27860 Gnus can fetch articles, asynchronously, on a second connection to the
27861 server (@pxref{Asynchronous Fetching}).
27864 You can cache articles locally (@pxref{Article Caching}).
27867 The uudecode functions have been expanded and generalized
27868 (@pxref{Decoding Articles}).
27871 You can still post uuencoded articles, which was a little-known feature
27872 of @sc{gnus}' past (@pxref{Uuencoding and Posting}).
27875 Fetching parents (and other articles) now actually works without
27876 glitches (@pxref{Finding the Parent}).
27879 Gnus can fetch @acronym{FAQ}s and group descriptions (@pxref{Group Information}).
27882 Digests (and other files) can be used as the basis for groups
27883 (@pxref{Document Groups}).
27886 Articles can be highlighted and customized (@pxref{Customizing
27890 URLs and other external references can be buttonized (@pxref{Article
27894 You can do lots of strange stuff with the Gnus window & frame
27895 configuration (@pxref{Window Layout}).
27898 You can click on buttons instead of using the keyboard
27904 @node September Gnus
27905 @subsubsection September Gnus
27909 \gnusfig{-28cm}{0cm}{\epsfig{figure=ps/september,height=20cm}}
27913 New features in Gnus 5.2/5.3:
27918 A new message composition mode is used. All old customization variables
27919 for @code{mail-mode}, @code{rnews-reply-mode} and @code{gnus-msg} are
27923 Gnus is now able to generate @dfn{sparse} threads---threads where
27924 missing articles are represented by empty nodes (@pxref{Customizing
27928 (setq gnus-build-sparse-threads 'some)
27932 Outgoing articles are stored on a special archive server
27933 (@pxref{Archived Messages}).
27936 Partial thread regeneration now happens when articles are
27940 Gnus can make use of GroupLens predictions.
27943 Picons (personal icons) can be displayed under XEmacs (@pxref{Picons}).
27946 A @code{trn}-like tree buffer can be displayed (@pxref{Tree Display}).
27949 (setq gnus-use-trees t)
27953 An @code{nn}-like pick-and-read minor mode is available for the summary
27954 buffers (@pxref{Pick and Read}).
27957 (add-hook 'gnus-summary-mode-hook 'gnus-pick-mode)
27961 In binary groups you can use a special binary minor mode (@pxref{Binary
27965 Groups can be grouped in a folding topic hierarchy (@pxref{Group
27969 (add-hook 'gnus-group-mode-hook 'gnus-topic-mode)
27973 Gnus can re-send and bounce mail (@pxref{Summary Mail Commands}).
27976 Groups can now have a score, and bubbling based on entry frequency
27977 is possible (@pxref{Group Score}).
27980 (add-hook 'gnus-summary-exit-hook 'gnus-summary-bubble-group)
27984 Groups can be process-marked, and commands can be performed on
27985 groups of groups (@pxref{Marking Groups}).
27988 Caching is possible in virtual groups.
27991 @code{nndoc} now understands all kinds of digests, mail boxes, rnews
27992 news batches, ClariNet briefs collections, and just about everything
27993 else (@pxref{Document Groups}).
27996 Gnus has a new back end (@code{nnsoup}) to create/read SOUP packets
28000 The Gnus cache is much faster.
28003 Groups can be sorted according to many criteria (@pxref{Sorting
28007 New group parameters have been introduced to set list-addresses and
28008 expiry times (@pxref{Group Parameters}).
28011 All formatting specs allow specifying faces to be used
28012 (@pxref{Formatting Fonts}).
28015 There are several more commands for setting/removing/acting on process
28016 marked articles on the @kbd{M P} submap (@pxref{Setting Process Marks}).
28019 The summary buffer can be limited to show parts of the available
28020 articles based on a wide range of criteria. These commands have been
28021 bound to keys on the @kbd{/} submap (@pxref{Limiting}).
28024 Articles can be made persistent with the @kbd{*} command
28025 (@pxref{Persistent Articles}).
28028 All functions for hiding article elements are now toggles.
28031 Article headers can be buttonized (@pxref{Article Washing}).
28034 All mail back ends support fetching articles by @code{Message-ID}.
28037 Duplicate mail can now be treated properly (@pxref{Duplicates}).
28040 All summary mode commands are available directly from the article
28041 buffer (@pxref{Article Keymap}).
28044 Frames can be part of @code{gnus-buffer-configuration} (@pxref{Window
28048 Mail can be re-scanned by a daemonic process (@pxref{Daemons}).
28051 \marginpar[\mbox{}\hfill\epsfig{figure=ps/fseptember,height=5cm}]{\epsfig{figure=ps/fseptember,height=5cm}}
28056 Gnus can make use of NoCeM files to weed out spam (@pxref{NoCeM}).
28059 (setq gnus-use-nocem t)
28063 Groups can be made permanently visible (@pxref{Listing Groups}).
28066 (setq gnus-permanently-visible-groups "^nnml:")
28070 Many new hooks have been introduced to make customizing easier.
28073 Gnus respects the @code{Mail-Copies-To} header.
28076 Threads can be gathered by looking at the @code{References} header
28077 (@pxref{Customizing Threading}).
28080 (setq gnus-summary-thread-gathering-function
28081 'gnus-gather-threads-by-references)
28085 Read articles can be stored in a special backlog buffer to avoid
28086 refetching (@pxref{Article Backlog}).
28089 (setq gnus-keep-backlog 50)
28093 A clean copy of the current article is always stored in a separate
28094 buffer to allow easier treatment.
28097 Gnus can suggest where to save articles (@pxref{Saving Articles}).
28100 Gnus doesn't have to do as much prompting when saving (@pxref{Saving
28104 (setq gnus-prompt-before-saving t)
28108 @code{gnus-uu} can view decoded files asynchronously while fetching
28109 articles (@pxref{Other Decode Variables}).
28112 (setq gnus-uu-grabbed-file-functions 'gnus-uu-grab-view)
28116 Filling in the article buffer now works properly on cited text
28117 (@pxref{Article Washing}).
28120 Hiding cited text adds buttons to toggle hiding, and how much
28121 cited text to hide is now customizable (@pxref{Article Hiding}).
28124 (setq gnus-cited-lines-visible 2)
28128 Boring headers can be hidden (@pxref{Article Hiding}).
28131 Default scoring values can now be set from the menu bar.
28134 Further syntax checking of outgoing articles have been added.
28140 @subsubsection Red Gnus
28142 New features in Gnus 5.4/5.5:
28146 \gnusfig{-5.5cm}{-4cm}{\epsfig{figure=ps/red,height=20cm}}
28153 @file{nntp.el} has been totally rewritten in an asynchronous fashion.
28156 Article prefetching functionality has been moved up into
28157 Gnus (@pxref{Asynchronous Fetching}).
28160 Scoring can now be performed with logical operators like @code{and},
28161 @code{or}, @code{not}, and parent redirection (@pxref{Advanced
28165 Article washing status can be displayed in the
28166 article mode line (@pxref{Misc Article}).
28169 @file{gnus.el} has been split into many smaller files.
28172 Suppression of duplicate articles based on Message-ID can be done
28173 (@pxref{Duplicate Suppression}).
28176 (setq gnus-suppress-duplicates t)
28180 New variables for specifying what score and adapt files are to be
28181 considered home score and adapt files (@pxref{Home Score File}) have
28185 @code{nndoc} was rewritten to be easily extendable (@pxref{Document
28186 Server Internals}).
28189 Groups can inherit group parameters from parent topics (@pxref{Topic
28193 Article editing has been revamped and is now actually usable.
28196 Signatures can be recognized in more intelligent fashions
28197 (@pxref{Article Signature}).
28200 Summary pick mode has been made to look more @code{nn}-like. Line
28201 numbers are displayed and the @kbd{.} command can be used to pick
28202 articles (@code{Pick and Read}).
28205 Commands for moving the @file{.newsrc.eld} from one server to
28206 another have been added (@pxref{Changing Servers}).
28209 There's a way now to specify that ``uninteresting'' fields be suppressed
28210 when generating lines in buffers (@pxref{Advanced Formatting}).
28213 Several commands in the group buffer can be undone with @kbd{C-M-_}
28217 Scoring can be done on words using the new score type @code{w}
28218 (@pxref{Score File Format}).
28221 Adaptive scoring can be done on a Subject word-by-word basis
28222 (@pxref{Adaptive Scoring}).
28225 (setq gnus-use-adaptive-scoring '(word))
28229 Scores can be decayed (@pxref{Score Decays}).
28232 (setq gnus-decay-scores t)
28236 Scoring can be performed using a regexp on the Date header. The Date is
28237 normalized to compact ISO 8601 format first (@pxref{Score File Format}).
28240 A new command has been added to remove all data on articles from
28241 the native server (@pxref{Changing Servers}).
28244 A new command for reading collections of documents
28245 (@code{nndoc} with @code{nnvirtual} on top) has been added---@kbd{C-M-d}
28246 (@pxref{Really Various Summary Commands}).
28249 Process mark sets can be pushed and popped (@pxref{Setting Process
28253 A new mail-to-news back end makes it possible to post even when the @acronym{NNTP}
28254 server doesn't allow posting (@pxref{Mail-To-News Gateways}).
28257 A new back end for reading searches from Web search engines
28258 (@dfn{DejaNews}, @dfn{Alta Vista}, @dfn{InReference}) has been added
28259 (@pxref{Web Searches}).
28262 Groups inside topics can now be sorted using the standard sorting
28263 functions, and each topic can be sorted independently (@pxref{Topic
28267 Subsets of the groups can be sorted independently (@code{Sorting
28271 Cached articles can be pulled into the groups (@pxref{Summary Generation
28275 \marginpar[\mbox{}\hfill\epsfig{figure=ps/fred,width=3cm}]{\epsfig{figure=ps/fred,width=3cm}}
28280 Score files are now applied in a more reliable order (@pxref{Score
28284 Reports on where mail messages end up can be generated (@pxref{Splitting
28288 More hooks and functions have been added to remove junk from incoming
28289 mail before saving the mail (@pxref{Washing Mail}).
28292 Emphasized text can be properly fontisized:
28298 @subsubsection Quassia Gnus
28300 New features in Gnus 5.6:
28305 New functionality for using Gnus as an offline newsreader has been
28306 added. A plethora of new commands and modes have been added.
28307 @xref{Gnus Unplugged}, for the full story.
28310 The @code{nndraft} back end has returned, but works differently than
28311 before. All Message buffers are now also articles in the @code{nndraft}
28312 group, which is created automatically.
28315 @code{gnus-alter-header-function} can now be used to alter header
28319 @code{gnus-summary-goto-article} now accept Message-ID's.
28322 A new Message command for deleting text in the body of a message
28323 outside the region: @kbd{C-c C-v}.
28326 You can now post to component group in @code{nnvirtual} groups with
28330 @code{nntp-rlogin-program}---new variable to ease customization.
28333 @code{C-u C-c C-c} in @code{gnus-article-edit-mode} will now inhibit
28334 re-highlighting of the article buffer.
28337 New element in @code{gnus-boring-article-headers}---@code{long-to}.
28340 @kbd{M-i} symbolic prefix command. @xref{Symbolic Prefixes}, for
28344 @kbd{L} and @kbd{I} in the summary buffer now take the symbolic prefix
28345 @kbd{a} to add the score rule to the @file{all.SCORE} file.
28348 @code{gnus-simplify-subject-functions} variable to allow greater
28349 control over simplification.
28352 @kbd{A T}---new command for fetching the current thread.
28355 @kbd{/ T}---new command for including the current thread in the
28359 @kbd{M-RET} is a new Message command for breaking cited text.
28362 @samp{\\1}-expressions are now valid in @code{nnmail-split-methods}.
28365 The @code{custom-face-lookup} function has been removed.
28366 If you used this function in your initialization files, you must
28367 rewrite them to use @code{face-spec-set} instead.
28370 Canceling now uses the current select method. Symbolic prefix
28371 @kbd{a} forces normal posting method.
28374 New command to translate M******** sm*rtq**t*s into proper
28378 For easier debugging of @code{nntp}, you can set
28379 @code{nntp-record-commands} to a non-@code{nil} value.
28382 @code{nntp} now uses @file{~/.authinfo}, a @file{.netrc}-like file, for
28383 controlling where and how to send @sc{authinfo} to @acronym{NNTP} servers.
28386 A command for editing group parameters from the summary buffer
28390 A history of where mails have been split is available.
28393 A new article date command has been added---@code{article-date-iso8601}.
28396 Subjects can be simplified when threading by setting
28397 @code{gnus-score-thread-simplify}.
28400 A new function for citing in Message has been
28401 added---@code{message-cite-original-without-signature}.
28404 @code{article-strip-all-blank-lines}---new article command.
28407 A new Message command to kill to the end of the article has
28411 A minimum adaptive score can be specified by using the
28412 @code{gnus-adaptive-word-minimum} variable.
28415 The ``lapsed date'' article header can be kept continually
28416 updated by the @code{gnus-start-date-timer} command.
28419 Web listserv archives can be read with the @code{nnlistserv} back end.
28422 Old dejanews archives can now be read by @code{nnweb}.
28426 @node Pterodactyl Gnus
28427 @subsubsection Pterodactyl Gnus
28429 New features in Gnus 5.8:
28434 The mail-fetching functions have changed. See the manual for the
28435 many details. In particular, all procmail fetching variables are gone.
28437 If you used procmail like in
28440 (setq nnmail-use-procmail t)
28441 (setq nnmail-spool-file 'procmail)
28442 (setq nnmail-procmail-directory "~/mail/incoming/")
28443 (setq nnmail-procmail-suffix "\\.in")
28446 this now has changed to
28450 '((directory :path "~/mail/incoming/"
28454 @xref{Mail Source Specifiers}.
28457 Gnus is now a @acronym{MIME}-capable reader. This affects many parts of
28458 Gnus, and adds a slew of new commands. See the manual for details.
28461 Gnus has also been multilingualized. This also affects too
28462 many parts of Gnus to summarize here, and adds many new variables.
28465 @code{gnus-auto-select-first} can now be a function to be
28466 called to position point.
28469 The user can now decide which extra headers should be included in
28470 summary buffers and @acronym{NOV} files.
28473 @code{gnus-article-display-hook} has been removed. Instead, a number
28474 of variables starting with @code{gnus-treat-} have been added.
28477 The Gnus posting styles have been redone again and now works in a
28478 subtly different manner.
28481 New web-based back ends have been added: @code{nnslashdot},
28482 @code{nnwarchive} and @code{nnultimate}. nnweb has been revamped,
28483 again, to keep up with ever-changing layouts.
28486 Gnus can now read @acronym{IMAP} mail via @code{nnimap}.
28491 @subsubsection Oort Gnus
28494 New features in Gnus 5.10:
28498 @item Installation changes
28499 @c ***********************
28503 Upgrading from previous (stable) version if you have used Oort.
28505 If you have tried Oort (the unstable Gnus branch leading to this
28506 release) but went back to a stable version, be careful when upgrading to
28507 this version. In particular, you will probably want to remove all
28508 @file{.marks} (nnml) and @file{.mrk} (nnfolder) files, so that flags are
28509 read from your @file{.newsrc.eld} instead of from the
28510 @file{.marks}/@file{.mrk} file where this release store flags. See a
28511 later entry for more information about marks. Note that downgrading
28512 isn't save in general.
28515 Lisp files are now installed in @file{.../site-lisp/gnus/} by default.
28516 It defaulted to @file{.../site-lisp/} formerly. In addition to this,
28517 the new installer issues a warning if other Gnus installations which
28518 will shadow the latest one are detected. You can then remove those
28519 shadows manually or remove them using @code{make
28520 remove-installed-shadows}.
28523 New @file{make.bat} for compiling and installing Gnus under MS Windows
28525 Use @file{make.bat} if you want to install Gnus under MS Windows, the
28526 first argument to the batch-program should be the directory where
28527 @file{xemacs.exe} respectively @file{emacs.exe} is located, if you want
28528 to install Gnus after compiling it, give @file{make.bat} @code{/copy} as
28529 the second parameter.
28531 @file{make.bat} has been rewritten from scratch, it now features
28532 automatic recognition of XEmacs and GNU Emacs, generates
28533 @file{gnus-load.el}, checks if errors occur while compilation and
28534 generation of info files and reports them at the end of the build
28535 process. It now uses @code{makeinfo} if it is available and falls
28536 back to @file{infohack.el} otherwise. @file{make.bat} should now
28537 install all files which are necessary to run Gnus and be generally a
28538 complete replacement for the @code{configure; make; make install}
28539 cycle used under Unix systems.
28541 The new @file{make.bat} makes @file{make-x.bat} and @file{xemacs.mak}
28542 superfluous, so they have been removed.
28545 @file{~/News/overview/} not used.
28547 As a result of the following change, the @file{~/News/overview/}
28548 directory is not used any more. You can safely delete the entire
28551 @c FIXME: `gnus-load' is mentioned in README, which is not included in
28552 @c the repository. We should find a better place for this item.
28554 @code{(require 'gnus-load)}
28556 If you use a stand-alone Gnus distribution, you'd better add
28557 @code{(require 'gnus-load)} into your @file{~/.emacs} after adding the Gnus
28558 lisp directory into load-path.
28560 File @file{gnus-load.el} contains autoload commands, functions and variables,
28561 some of which may not be included in distributions of Emacsen.
28565 @item New packages and libraries within Gnus
28566 @c *****************************************
28571 The revised Gnus @acronym{FAQ} is included in the manual,
28572 @xref{Frequently Asked Questions}.
28575 @acronym{TLS} wrapper shipped with Gnus
28577 @acronym{TLS}/@acronym{SSL} is now supported in @acronym{IMAP} and
28578 @acronym{NNTP} via @file{tls.el} and GNUTLS. The old
28579 @acronym{TLS}/@acronym{SSL} support via (external third party)
28580 @file{ssl.el} and OpenSSL still works.
28583 Improved anti-spam features.
28585 Gnus is now able to take out spam from your mail and news streams
28586 using a wide variety of programs and filter rules. Among the supported
28587 methods are RBL blocklists, bogofilter and white/blacklists. Hooks
28588 for easy use of external packages such as SpamAssassin and Hashcash
28589 are also new. @ref{Thwarting Email Spam} and @ref{Spam Package}.
28590 @c FIXME: @xref{Spam Package}?. Should this be under Misc?
28593 Gnus supports server-side mail filtering using Sieve.
28595 Sieve rules can be added as Group Parameters for groups, and the
28596 complete Sieve script is generated using @kbd{D g} from the Group
28597 buffer, and then uploaded to the server using @kbd{C-c C-l} in the
28598 generated Sieve buffer. @xref{Sieve Commands}, and the new Sieve
28599 manual @ref{Top, , Top, sieve, Emacs Sieve}.
28603 @item Changes in group mode
28604 @c ************************
28609 @code{gnus-group-read-ephemeral-group} can be called interactively,
28613 Retrieval of charters and control messages
28615 There are new commands for fetching newsgroup charters (@kbd{H c}) and
28616 control messages (@kbd{H C}).
28619 The new variable @code{gnus-parameters} can be used to set group parameters.
28621 Earlier this was done only via @kbd{G p} (or @kbd{G c}), which stored
28622 the parameters in @file{~/.newsrc.eld}, but via this variable you can
28623 enjoy the powers of customize, and simplified backups since you set the
28624 variable in @file{~/.gnus.el} instead of @file{~/.newsrc.eld}. The
28625 variable maps regular expressions matching group names to group
28628 (setq gnus-parameters
28630 (gnus-show-threads nil)
28631 (gnus-use-scoring nil))
28632 ("^nnimap:\\(foo.bar\\)$"
28633 (to-group . "\\1"))))
28637 Unread count correct in nnimap groups.
28639 The estimated number of unread articles in the group buffer should now
28640 be correct for nnimap groups. This is achieved by calling
28641 @code{nnimap-fixup-unread-after-getting-new-news} from the
28642 @code{gnus-setup-news-hook} (called on startup) and
28643 @code{gnus-after-getting-new-news-hook}. (called after getting new
28644 mail). If you have modified those variables from the default, you may
28645 want to add @code{nnimap-fixup-unread-after-getting-new-news} again. If
28646 you were happy with the estimate and want to save some (minimal) time
28647 when getting new mail, remove the function.
28650 Group names are treated as UTF-8 by default.
28652 This is supposedly what USEFOR wanted to migrate to. See
28653 @code{gnus-group-name-charset-group-alist} and
28654 @code{gnus-group-name-charset-method-alist} for customization.
28657 @code{gnus-group-charset-alist} and
28658 @code{gnus-group-ignored-charsets-alist}.
28660 The regexps in these variables are compared with full group names
28661 instead of real group names in 5.8. Users who customize these
28662 variables should change those regexps accordingly. For example:
28664 ("^han\\>" euc-kr) -> ("\\(^\\|:\\)han\\>" euc-kr)
28668 Old intermediate incoming mail files (@file{Incoming*}) are deleted
28669 after a couple of days, not immediately. @xref{Mail Source
28670 Customization}. (New in Gnus 5.10.10 / Emacs 22.2)
28674 @item Changes in summary and article mode
28675 @c **************************************
28680 @kbd{F} (@code{gnus-article-followup-with-original}) and @kbd{R}
28681 (@code{gnus-article-reply-with-original}) only yank the text in the
28682 region if the region is active.
28685 In draft groups, @kbd{e} is now bound to @code{gnus-draft-edit-message}.
28686 Use @kbd{B w} for @code{gnus-summary-edit-article} instead.
28691 More buttons for URLs, mail addresses, Message-IDs, Info links, man
28692 pages and Emacs or Gnus related references. @xref{Article Buttons}. The
28693 variables @code{gnus-button-@var{*}-level} can be used to control the
28694 appearance of all article buttons. @xref{Article Button Levels}.
28697 Single-part yenc encoded attachments can be decoded.
28702 The picons code has been reimplemented to work in GNU Emacs---some of
28703 the previous options have been removed or renamed.
28705 Picons are small ``personal icons'' representing users, domain and
28706 newsgroups, which can be displayed in the Article buffer.
28710 If the new option @code{gnus-treat-body-boundary} is non-@code{nil}, a
28711 boundary line is drawn at the end of the headers.
28714 Signed article headers (X-PGP-Sig) can be verified with @kbd{W p}.
28717 The Summary Buffer uses an arrow in the fringe to indicate the current
28718 article. Use @code{(setq gnus-summary-display-arrow nil)} to disable it.
28721 Warn about email replies to news
28723 Do you often find yourself replying to news by email by mistake? Then
28724 the new option @code{gnus-confirm-mail-reply-to-news} is just the thing for
28728 If the new option @code{gnus-summary-display-while-building} is
28729 non-@code{nil}, the summary buffer is shown and updated as it's being
28733 The new @code{recent} mark @samp{.} indicates newly arrived messages (as
28734 opposed to old but unread messages).
28737 Gnus supports RFC 2369 mailing list headers, and adds a number of
28738 related commands in mailing list groups. @xref{Mailing List}.
28741 The Date header can be displayed in a format that can be read aloud
28742 in English. @xref{Article Date}.
28745 diffs are automatically highlighted in groups matching
28746 @code{mm-uu-diff-groups-regexp}
28749 Better handling of Microsoft citation styles
28751 Gnus now tries to recognize the mangled header block that some Microsoft
28752 mailers use to indicate that the rest of the message is a citation, even
28753 though it is not quoted in any way. The variable
28754 @code{gnus-cite-unsightly-citation-regexp} matches the start of these
28757 The new command @kbd{W Y f}
28758 (@code{gnus-article-outlook-deuglify-article}) allows deuglifying broken
28759 Outlook (Express) articles.
28762 @code{gnus-article-skip-boring}
28764 If you set @code{gnus-article-skip-boring} to @code{t}, then Gnus will
28765 not scroll down to show you a page that contains only boring text,
28766 which by default means cited text and signature. You can customize
28767 what is skippable using @code{gnus-article-boring-faces}.
28769 This feature is especially useful if you read many articles that
28770 consist of a little new content at the top with a long, untrimmed
28771 message cited below.
28774 Smileys (@samp{:-)}, @samp{;-)} etc) are now displayed graphically in
28777 Put @code{(setq gnus-treat-display-smileys nil)} in @file{~/.gnus.el} to
28781 Face headers handling. @xref{Face}.
28784 In the summary buffer, the new command @kbd{/ N} inserts new messages
28785 and @kbd{/ o} inserts old messages.
28788 Gnus decodes morse encoded messages if you press @kbd{W m}.
28791 @code{gnus-summary-line-format}
28793 The default value changed to @samp{%U%R%z%I%(%[%4L: %-23,23f%]%)
28794 %s\n}. Moreover @code{gnus-extra-headers},
28795 @code{nnmail-extra-headers} and @code{gnus-ignored-from-addresses}
28796 changed their default so that the users name will be replaced by the
28797 recipient's name or the group name posting to for @acronym{NNTP}
28801 Deleting of attachments.
28803 The command @code{gnus-mime-save-part-and-strip} (bound to @kbd{C-o}
28804 on @acronym{MIME} buttons) saves a part and replaces the part with an
28805 external one. @code{gnus-mime-delete-part} (bound to @kbd{d} on
28806 @acronym{MIME} buttons) removes a part. It works only on back ends
28807 that support editing.
28810 @code{gnus-default-charset}
28812 The default value is determined from the
28813 @code{current-language-environment} variable, instead of
28814 @code{iso-8859-1}. Also the @samp{.*} item in
28815 @code{gnus-group-charset-alist} is removed.
28818 Printing capabilities are enhanced.
28820 Gnus supports Muttprint natively with @kbd{O P} from the Summary and
28821 Article buffers. Also, each individual @acronym{MIME} part can be
28822 printed using @kbd{p} on the @acronym{MIME} button.
28825 Extended format specs.
28827 Format spec @samp{%&user-date;} is added into
28828 @code{gnus-summary-line-format-alist}. Also, user defined extended
28829 format specs are supported. The extended format specs look like
28830 @samp{%u&foo;}, which invokes function
28831 @code{gnus-user-format-function-@var{foo}}. Because @samp{&} is used as the
28832 escape character, old user defined format @samp{%u&} is no longer supported.
28835 @kbd{/ *} (@code{gnus-summary-limit-include-cached}) is rewritten.
28836 @c FIXME: Was this a user-visible change?
28838 It was aliased to @kbd{Y c}
28839 (@code{gnus-summary-insert-cached-articles}). The new function filters
28840 out other articles.
28843 Some limiting commands accept a @kbd{C-u} prefix to negate the match.
28845 If @kbd{C-u} is used on subject, author or extra headers, i.e., @kbd{/
28846 s}, @kbd{/ a}, and @kbd{/ x}
28847 (@code{gnus-summary-limit-to-@{subject,author,extra@}}) respectively, the
28848 result will be to display all articles that do not match the expression.
28851 Gnus inlines external parts (message/external).
28855 @item Changes in Message mode and related Gnus features
28856 @c ****************************************************
28863 You can delay the sending of a message with @kbd{C-c C-j} in the Message
28864 buffer. The messages are delivered at specified time. This is useful
28865 for sending yourself reminders. @xref{Delayed Articles}.
28868 If the new option @code{nnml-use-compressed-files} is non-@code{nil},
28869 the nnml back end allows compressed message files.
28872 The new option @code{gnus-gcc-mark-as-read} automatically marks
28873 Gcc articles as read.
28876 Externalizing of attachments
28878 If @code{gnus-gcc-externalize-attachments} or
28879 @code{message-fcc-externalize-attachments} is non-@code{nil}, attach
28880 local files as external parts.
28883 The envelope sender address can be customized when using Sendmail.
28884 @xref{Mail Variables, Mail Variables,, message, Message Manual}.
28887 Gnus no longer generate the Sender: header automatically.
28889 Earlier it was generated when the user configurable email address was
28890 different from the Gnus guessed default user address. As the guessing
28891 algorithm is rarely correct these days, and (more controversially) the
28892 only use of the Sender: header was to check if you are entitled to
28893 cancel/supersede news (which is now solved by Cancel Locks instead,
28894 see another entry), generation of the header has been disabled by
28895 default. See the variables @code{message-required-headers},
28896 @code{message-required-news-headers}, and
28897 @code{message-required-mail-headers}.
28900 Features from third party @file{message-utils.el} added to @file{message.el}.
28902 Message now asks if you wish to remove @samp{(was: <old subject>)} from
28903 subject lines (see @code{message-subject-trailing-was-query}). @kbd{C-c
28904 M-m} and @kbd{C-c M-f} inserts markers indicating included text.
28905 @kbd{C-c C-f a} adds a X-No-Archive: header. @kbd{C-c C-f x} inserts
28906 appropriate headers and a note in the body for cross-postings and
28907 followups (see the variables @code{message-cross-post-@var{*}}).
28910 References and X-Draft-From headers are no longer generated when you
28911 start composing messages and @code{message-generate-headers-first} is
28915 Easy inclusion of X-Faces headers. @xref{X-Face}.
28918 Group Carbon Copy (GCC) quoting
28920 To support groups that contains SPC and other weird characters, groups
28921 are quoted before they are placed in the Gcc: header. This means
28922 variables such as @code{gnus-message-archive-group} should no longer
28923 contain quote characters to make groups containing SPC work. Also, if
28924 you are using the string @samp{nnml:foo, nnml:bar} (indicating Gcc
28925 into two groups) you must change it to return the list
28926 @code{("nnml:foo" "nnml:bar")}, otherwise the Gcc: line will be quoted
28927 incorrectly. Note that returning the string @samp{nnml:foo, nnml:bar}
28928 was incorrect earlier, it just didn't generate any problems since it
28929 was inserted directly.
28932 @code{message-insinuate-rmail}
28934 @c FIXME should that not be 'message-user-agent?
28935 Adding @code{(message-insinuate-rmail)} and @code{(setq
28936 mail-user-agent 'gnus-user-agent)} in @file{.emacs} convinces Rmail to
28937 compose, reply and forward messages in message-mode, where you can
28938 enjoy the power of @acronym{MML}.
28941 @code{message-minibuffer-local-map}
28943 The line below enables BBDB in resending a message:
28945 (define-key message-minibuffer-local-map [(tab)]
28946 'bbdb-complete-name)
28950 @code{gnus-posting-styles}
28952 Add a new format of match like
28954 ((header "to" "larsi.*org")
28955 (Organization "Somewhere, Inc."))
28957 The old format like the lines below is obsolete, but still accepted.
28959 (header "to" "larsi.*org"
28960 (Organization "Somewhere, Inc."))
28964 @code{message-ignored-news-headers} and @code{message-ignored-mail-headers}
28966 @samp{X-Draft-From} and @samp{X-Gnus-Agent-Meta-Information} have been
28967 added into these two variables. If you customized those, perhaps you
28968 need add those two headers too.
28971 Gnus supports the ``format=flowed'' (RFC 2646) parameter. On
28972 composing messages, it is enabled by @code{use-hard-newlines}.
28973 Decoding format=flowed was present but not documented in earlier
28977 The option @code{mm-fill-flowed} can be used to disable treatment of
28978 ``format=flowed'' messages. Also, flowed text is disabled when sending
28979 inline PGP signed messages. @xref{Flowed text, , Flowed text,
28980 emacs-mime, The Emacs MIME Manual}. (New in Gnus 5.10.7)
28981 @c This entry is also present in the node "No Gnus".
28984 Gnus supports the generation of RFC 2298 Disposition Notification requests.
28986 This is invoked with the @kbd{C-c M-n} key binding from message mode.
28989 Message supports the Importance: (RFC 2156) header.
28991 In the message buffer, @kbd{C-c C-f C-i} or @kbd{C-c C-u} cycles through
28995 Gnus supports Cancel Locks in News.
28997 This means a header @samp{Cancel-Lock} is inserted in news posting. It is
28998 used to determine if you wrote an article or not (for canceling and
28999 superseding). Gnus generates a random password string the first time
29000 you post a message, and saves it in your @file{~/.emacs} using the Custom
29001 system. While the variable is called @code{canlock-password}, it is not
29002 security sensitive data. Publishing your canlock string on the web
29003 will not allow anyone to be able to anything she could not already do.
29004 The behavior can be changed by customizing @code{message-insert-canlock}.
29007 Gnus supports @acronym{PGP} (RFC 1991/2440), @acronym{PGP/MIME} (RFC
29008 2015/3156) and @acronym{S/MIME} (RFC 2630-2633).
29010 It needs an external @acronym{S/MIME} and OpenPGP implementation, but no
29011 additional Lisp libraries. This add several menu items to the
29012 Attachments menu, and @kbd{C-c RET} key bindings, when composing
29013 messages. This also obsoletes @code{gnus-article-hide-pgp-hook}.
29016 @acronym{MML} (Mime compose) prefix changed from @kbd{M-m} to @kbd{C-c
29019 This change was made to avoid conflict with the standard binding of
29020 @code{back-to-indentation}, which is also useful in message mode.
29023 The default for @code{message-forward-show-mml} changed to the symbol
29026 The behavior for the @code{best} value is to show @acronym{MML} (i.e.,
29027 convert to @acronym{MIME}) when appropriate. @acronym{MML} will not be
29028 used when forwarding signed or encrypted messages, as the conversion
29029 invalidate the digital signature.
29032 If @code{auto-compression-mode} is enabled, attachments are automatically
29033 decompressed when activated.
29034 @c FIXME: Does this affect article or message mode?
29037 Support for non-@acronym{ASCII} domain names
29039 Message supports non-@acronym{ASCII} domain names in From:, To: and
29040 Cc: and will query you whether to perform encoding when you try to
29041 send a message. The variable @code{message-use-idna} controls this.
29042 Gnus will also decode non-@acronym{ASCII} domain names in From:, To:
29043 and Cc: when you view a message. The variable @code{gnus-use-idna}
29046 @item You can now drag and drop attachments to the Message buffer.
29047 See @code{mml-dnd-protocol-alist} and @code{mml-dnd-attach-options}.
29048 @xref{MIME, ,MIME, message, Message Manual}.
29049 @c New in 5.10.9 / 5.11 (Emacs 22.1)
29051 @item @code{auto-fill-mode} is enabled by default in Message mode.
29052 See @code{message-fill-column}. @xref{Various Message Variables, ,
29053 Message Headers, message, Message Manual}.
29054 @c New in Gnus 5.10.12 / 5.11 (Emacs 22.3)
29058 @item Changes in back ends
29059 @c ***********************
29063 Gnus can display RSS newsfeeds as a newsgroup. @xref{RSS}.
29066 The nndoc back end now supports mailman digests and exim bounces.
29069 Gnus supports Maildir groups.
29071 Gnus includes a new back end @file{nnmaildir.el}. @xref{Maildir}.
29074 The nnml and nnfolder back ends store marks for each groups.
29076 This makes it possible to take backup of nnml/nnfolder servers/groups
29077 separately of @file{~/.newsrc.eld}, while preserving marks. It also
29078 makes it possible to share articles and marks between users (without
29079 sharing the @file{~/.newsrc.eld} file) within e.g. a department. It
29080 works by storing the marks stored in @file{~/.newsrc.eld} in a per-group
29081 file @file{.marks} (for nnml) and @file{@var{groupname}.mrk} (for
29082 nnfolder, named @var{groupname}). If the nnml/nnfolder is moved to
29083 another machine, Gnus will automatically use the @file{.marks} or
29084 @file{.mrk} file instead of the information in @file{~/.newsrc.eld}.
29085 The new server variables @code{nnml-marks-is-evil} and
29086 @code{nnfolder-marks-is-evil} can be used to disable this feature.
29096 The menu bar item (in Group and Summary buffer) named ``Misc'' has
29097 been renamed to ``Gnus''.
29100 The menu bar item (in Message mode) named ``@acronym{MML}'' has been
29101 renamed to ``Attachments''. Note that this menu also contains security
29102 related stuff, like signing and encryption (@pxref{Security, Security,,
29103 message, Message Manual}).
29106 The tool bars have been updated to use GNOME icons in Group, Summary and
29107 Message mode. You can also customize the tool bars: @kbd{M-x
29108 customize-apropos RET -tool-bar$} should get you started. This is a new
29109 feature in Gnus 5.10.10. (Only for Emacs, not in XEmacs.)
29111 @item The tool bar icons are now (de)activated correctly
29112 in the group buffer, see the variable @code{gnus-group-update-tool-bar}.
29113 Its default value depends on your Emacs version. This is a new feature
29118 @item Miscellaneous changes
29119 @c ************************
29126 The Gnus Agent has seen a major updated and is now enabled by default,
29127 and all nntp and nnimap servers from @code{gnus-select-method} and
29128 @code{gnus-secondary-select-method} are agentized by default. Earlier
29129 only the server in @code{gnus-select-method} was agentized by the
29130 default, and the agent was disabled by default. When the agent is
29131 enabled, headers are now also retrieved from the Agent cache instead
29132 of the back ends when possible. Earlier this only happened in the
29133 unplugged state. You can enroll or remove servers with @kbd{J a} and
29134 @kbd{J r} in the server buffer. Gnus will not download articles into
29135 the Agent cache, unless you instruct it to do so, though, by using
29136 @kbd{J u} or @kbd{J s} from the Group buffer. You revert to the old
29137 behavior of having the Agent disabled with @code{(setq gnus-agent
29138 nil)}. Note that putting @code{(gnus-agentize)} in @file{~/.gnus.el}
29139 is not needed any more.
29142 Gnus reads the @acronym{NOV} and articles in the Agent if plugged.
29144 If one reads an article while plugged, and the article already exists
29145 in the Agent, it won't get downloaded once more. @code{(setq
29146 gnus-agent-cache nil)} reverts to the old behavior.
29151 @code{gnus-dired-minor-mode} (see @ref{Other modes}) installs key
29152 bindings in dired buffers to send a file as an attachment, open a file
29153 using the appropriate mailcap entry, and print a file using the mailcap
29157 The format spec @code{%C} for positioning point has changed to @code{%*}.
29160 @code{gnus-slave-unplugged}
29162 A new command which starts Gnus offline in slave mode.
29169 @subsubsection No Gnus
29172 New features in No Gnus:
29173 @c FIXME: Gnus 5.12?
29175 @include gnus-news.texi
29181 @section The Manual
29185 This manual was generated from a TeXinfo file and then run through
29186 either @code{texi2dvi}
29188 or my own home-brewed TeXinfo to \LaTeX\ transformer,
29189 and then run through @code{latex} and @code{dvips}
29191 to get what you hold in your hands now.
29193 The following conventions have been used:
29198 This is a @samp{string}
29201 This is a @kbd{keystroke}
29204 This is a @file{file}
29207 This is a @code{symbol}
29211 So if I were to say ``set @code{flargnoze} to @samp{yes}'', that would
29215 (setq flargnoze "yes")
29218 If I say ``set @code{flumphel} to @code{yes}'', that would mean:
29221 (setq flumphel 'yes)
29224 @samp{yes} and @code{yes} are two @emph{very} different things---don't
29225 ever get them confused.
29229 Of course, everything in this manual is of vital interest, so you should
29230 read it all. Several times. However, if you feel like skimming the
29231 manual, look for that gnu head you should see in the margin over
29232 there---it means that what's being discussed is of more importance than
29233 the rest of the stuff. (On the other hand, if everything is infinitely
29234 important, how can anything be more important than that? Just one more
29235 of the mysteries of this world, I guess.)
29241 @node On Writing Manuals
29242 @section On Writing Manuals
29244 I guess most manuals are written after-the-fact; documenting a program
29245 that's already there. This is not how this manual is written. When
29246 implementing something, I write the manual entry for that something
29247 straight away. I then see that it's difficult to explain the
29248 functionality, so I write how it's supposed to be, and then I change the
29249 implementation. Writing the documentation and writing the code go hand
29252 This, of course, means that this manual has no, or little, flow. It
29253 documents absolutely everything in Gnus, but often not where you're
29254 looking for it. It is a reference manual, and not a guide to how to get
29257 That would be a totally different book, that should be written using the
29258 reference manual as source material. It would look quite different.
29263 @section Terminology
29265 @cindex terminology
29270 This is what you are supposed to use this thing for---reading news.
29271 News is generally fetched from a nearby @acronym{NNTP} server, and is
29272 generally publicly available to everybody. If you post news, the entire
29273 world is likely to read just what you have written, and they'll all
29274 snigger mischievously. Behind your back.
29278 Everything that's delivered to you personally is mail. Some news/mail
29279 readers (like Gnus) blur the distinction between mail and news, but
29280 there is a difference. Mail is private. News is public. Mailing is
29281 not posting, and replying is not following up.
29285 Send a mail to the person who has written what you are reading.
29289 Post an article to the current newsgroup responding to the article you
29294 Gnus considers mail and news to be mostly the same, really. The only
29295 difference is how to access the actual articles. News articles are
29296 commonly fetched via the protocol @acronym{NNTP}, whereas mail
29297 messages could be read from a file on the local disk. The internal
29298 architecture of Gnus thus comprises a ``front end'' and a number of
29299 ``back ends''. Internally, when you enter a group (by hitting
29300 @key{RET}, say), you thereby invoke a function in the front end in
29301 Gnus. The front end then ``talks'' to a back end and says things like
29302 ``Give me the list of articles in the foo group'' or ``Show me article
29305 So a back end mainly defines either a protocol (the @code{nntp} back
29306 end accesses news via @acronym{NNTP}, the @code{nnimap} back end
29307 accesses mail via @acronym{IMAP}) or a file format and directory
29308 layout (the @code{nnspool} back end accesses news via the common
29309 ``spool directory'' format, the @code{nnml} back end access mail via a
29310 file format and directory layout that's quite similar).
29312 Gnus does not handle the underlying media, so to speak---this is all
29313 done by the back ends. A back end is a collection of functions to
29314 access the articles.
29316 However, sometimes the term ``back end'' is also used where ``server''
29317 would have been more appropriate. And then there is the term ``select
29318 method'' which can mean either. The Gnus terminology can be quite
29323 Gnus will always use one method (and back end) as the @dfn{native}, or
29324 default, way of getting news.
29328 You can also have any number of foreign groups active at the same time.
29329 These are groups that use non-native non-secondary back ends for getting
29334 Secondary back ends are somewhere half-way between being native and being
29335 foreign, but they mostly act like they are native.
29339 A message that has been posted as news.
29342 @cindex mail message
29343 A message that has been mailed.
29347 A mail message or news article
29351 The top part of a message, where administrative information (etc.) is
29356 The rest of an article. Everything not in the head is in the
29361 A line from the head of an article.
29365 A collection of such lines, or a collection of heads. Or even a
29366 collection of @acronym{NOV} lines.
29368 @item @acronym{NOV}
29369 @cindex @acronym{NOV}
29370 @acronym{NOV} stands for News OverView, which is a type of news server
29371 header which provide datas containing the condensed header information
29372 of articles. They are produced by the server itself; in the @code{nntp}
29373 back end Gnus uses the ones that the @acronym{NNTP} server makes, but
29374 Gnus makes them by itself for some backends (in particular, @code{nnml}).
29376 When Gnus enters a group, it asks the back end for the headers of all
29377 unread articles in the group. Most servers support the News OverView
29378 format, which is more compact and much faster to read and parse than the
29379 normal @sc{head} format.
29381 The @acronym{NOV} data consist of one or more text lines (@pxref{Text
29382 Lines, ,Motion by Text Lines, elisp, The Emacs Lisp Reference Manual})
29383 where each line has the header information of one article. The header
29384 information is a tab-separated series of the header's contents including
29385 an article number, a subject, an author, a date, a message-id,
29388 Those data enable Gnus to generate summary lines quickly. However, if
29389 the server does not support @acronym{NOV} or you disable it purposely or
29390 for some reason, Gnus will try to generate the header information by
29391 parsing each article's headers one by one. It will take time.
29392 Therefore, it is not usually a good idea to set nn*-nov-is-evil
29393 (@pxref{Slow/Expensive Connection}) to a non-@code{nil} value unless you
29394 know that the server makes wrong @acronym{NOV} data.
29398 Each group is subscribed at some @dfn{level} or other (1-9). The ones
29399 that have a lower level are ``more'' subscribed than the groups with a
29400 higher level. In fact, groups on levels 1-5 are considered
29401 @dfn{subscribed}; 6-7 are @dfn{unsubscribed}; 8 are @dfn{zombies}; and 9
29402 are @dfn{killed}. Commands for listing groups and scanning for new
29403 articles will all use the numeric prefix as @dfn{working level}.
29405 @item killed groups
29406 @cindex killed groups
29407 No information on killed groups is stored or updated, which makes killed
29408 groups much easier to handle than subscribed groups.
29410 @item zombie groups
29411 @cindex zombie groups
29412 Just like killed groups, only slightly less dead.
29415 @cindex active file
29416 The news server has to keep track of what articles it carries, and what
29417 groups exist. All this information in stored in the active file, which
29418 is rather large, as you might surmise.
29421 @cindex bogus groups
29422 A group that exists in the @file{.newsrc} file, but isn't known to the
29423 server (i.e., it isn't in the active file), is a @emph{bogus group}.
29424 This means that the group probably doesn't exist (any more).
29427 @cindex activating groups
29428 The act of asking the server for info on a group and computing the
29429 number of unread articles is called @dfn{activating the group}.
29430 Un-activated groups are listed with @samp{*} in the group buffer.
29434 News servers store their articles locally in one fashion or other.
29435 One old-fashioned storage method is to have just one file per
29436 article. That's called a ``traditional spool''.
29440 A machine one can connect to and get news (or mail) from.
29442 @item select method
29443 @cindex select method
29444 A structure that specifies the back end, the server and the virtual
29447 @item virtual server
29448 @cindex virtual server
29449 A named select method. Since a select method defines all there is to
29450 know about connecting to a (physical) server, taking the thing as a
29451 whole is a virtual server.
29455 Taking a buffer and running it through a filter of some sort. The
29456 result will (more often than not) be cleaner and more pleasing than the
29459 @item ephemeral groups
29460 @cindex ephemeral groups
29461 @cindex temporary groups
29462 Most groups store data on what articles you have read. @dfn{Ephemeral}
29463 groups are groups that will have no data stored---when you exit the
29464 group, it'll disappear into the aether.
29467 @cindex solid groups
29468 This is the opposite of ephemeral groups. All groups listed in the
29469 group buffer are solid groups.
29471 @item sparse articles
29472 @cindex sparse articles
29473 These are article placeholders shown in the summary buffer when
29474 @code{gnus-build-sparse-threads} has been switched on.
29478 To put responses to articles directly after the articles they respond
29479 to---in a hierarchical fashion.
29483 @cindex thread root
29484 The first article in a thread is the root. It is the ancestor of all
29485 articles in the thread.
29489 An article that has responses.
29493 An article that responds to a different article---its parent.
29497 A collection of messages in one file. The most common digest format is
29498 specified by RFC 1153.
29501 @cindex splitting, terminology
29502 @cindex mail sorting
29503 @cindex mail filtering (splitting)
29504 The action of sorting your emails according to certain rules. Sometimes
29505 incorrectly called mail filtering.
29511 @node Customization
29512 @section Customization
29513 @cindex general customization
29515 All variables are properly documented elsewhere in this manual. This
29516 section is designed to give general pointers on how to customize Gnus
29517 for some quite common situations.
29520 * Slow/Expensive Connection:: You run a local Emacs and get the news elsewhere.
29521 * Slow Terminal Connection:: You run a remote Emacs.
29522 * Little Disk Space:: You feel that having large setup files is icky.
29523 * Slow Machine:: You feel like buying a faster machine.
29527 @node Slow/Expensive Connection
29528 @subsection Slow/Expensive Connection
29530 If you run Emacs on a machine locally, and get your news from a machine
29531 over some very thin strings, you want to cut down on the amount of data
29532 Gnus has to get from the server.
29536 @item gnus-read-active-file
29537 Set this to @code{nil}, which will inhibit Gnus from requesting the
29538 entire active file from the server. This file is often very large. You
29539 also have to set @code{gnus-check-new-newsgroups} and
29540 @code{gnus-check-bogus-newsgroups} to @code{nil} to make sure that Gnus
29541 doesn't suddenly decide to fetch the active file anyway.
29543 @item gnus-nov-is-evil
29544 @vindex gnus-nov-is-evil
29545 Usually this one must @emph{always} be @code{nil} (which is the
29546 default). If, for example, you wish to not use @acronym{NOV}
29547 (@pxref{Terminology}) with the @code{nntp} back end (@pxref{Crosspost
29548 Handling}), set @code{nntp-nov-is-evil} to a non-@code{nil} value
29549 instead of setting this. But you normally do not need to set
29550 @code{nntp-nov-is-evil} since Gnus by itself will detect whether the
29551 @acronym{NNTP} server supports @acronym{NOV}. Anyway, grabbing article
29552 headers from the @acronym{NNTP} server will not be very fast if you tell
29553 Gnus not to use @acronym{NOV}.
29555 As the variables for the other back ends, there are
29556 @code{nndiary-nov-is-evil}, @code{nndir-nov-is-evil},
29557 @code{nnfolder-nov-is-evil}, @code{nnimap-nov-is-evil},
29558 @code{nnml-nov-is-evil}, @code{nnspool-nov-is-evil}, and
29559 @code{nnwarchive-nov-is-evil}. Note that a non-@code{nil} value for
29560 @code{gnus-nov-is-evil} overrides all those variables.@footnote{Although
29561 the back ends @code{nnkiboze}, @code{nnslashdot}, @code{nnultimate}, and
29562 @code{nnwfm} don't have their own nn*-nov-is-evil.}
29566 @node Slow Terminal Connection
29567 @subsection Slow Terminal Connection
29569 Let's say you use your home computer for dialing up the system that runs
29570 Emacs and Gnus. If your modem is slow, you want to reduce (as much as
29571 possible) the amount of data sent over the wires.
29575 @item gnus-auto-center-summary
29576 Set this to @code{nil} to inhibit Gnus from re-centering the summary
29577 buffer all the time. If it is @code{vertical}, do only vertical
29578 re-centering. If it is neither @code{nil} nor @code{vertical}, do both
29579 horizontal and vertical recentering.
29581 @item gnus-visible-headers
29582 Cut down on the headers included in the articles to the
29583 minimum. You can, in fact, make do without them altogether---most of the
29584 useful data is in the summary buffer, anyway. Set this variable to
29585 @samp{^NEVVVVER} or @samp{From:}, or whatever you feel you need.
29587 Use the following to enable all the available hiding features:
29589 (setq gnus-treat-hide-headers 'head
29590 gnus-treat-hide-signature t
29591 gnus-treat-hide-citation t)
29594 @item gnus-use-full-window
29595 By setting this to @code{nil}, you can make all the windows smaller.
29596 While this doesn't really cut down much generally, it means that you
29597 have to see smaller portions of articles before deciding that you didn't
29598 want to read them anyway.
29600 @item gnus-thread-hide-subtree
29601 If this is non-@code{nil}, all threads in the summary buffer will be
29605 @item gnus-updated-mode-lines
29606 If this is @code{nil}, Gnus will not put information in the buffer mode
29607 lines, which might save some time.
29611 @node Little Disk Space
29612 @subsection Little Disk Space
29615 The startup files can get rather large, so you may want to cut their
29616 sizes a bit if you are running out of space.
29620 @item gnus-save-newsrc-file
29621 If this is @code{nil}, Gnus will never save @file{.newsrc}---it will
29622 only save @file{.newsrc.eld}. This means that you will not be able to
29623 use any other newsreaders than Gnus. This variable is @code{t} by
29626 @item gnus-read-newsrc-file
29627 If this is @code{nil}, Gnus will never read @file{.newsrc}---it will
29628 only read @file{.newsrc.eld}. This means that you will not be able to
29629 use any other newsreaders than Gnus. This variable is @code{t} by
29632 @item gnus-save-killed-list
29633 If this is @code{nil}, Gnus will not save the list of dead groups. You
29634 should also set @code{gnus-check-new-newsgroups} to @code{ask-server}
29635 and @code{gnus-check-bogus-newsgroups} to @code{nil} if you set this
29636 variable to @code{nil}. This variable is @code{t} by default.
29642 @subsection Slow Machine
29643 @cindex slow machine
29645 If you have a slow machine, or are just really impatient, there are a
29646 few things you can do to make Gnus run faster.
29648 Set @code{gnus-check-new-newsgroups} and
29649 @code{gnus-check-bogus-newsgroups} to @code{nil} to make startup faster.
29651 Set @code{gnus-show-threads}, @code{gnus-use-cross-reference} and
29652 @code{gnus-nov-is-evil} to @code{nil} to make entering and exiting the
29653 summary buffer faster. Also @pxref{Slow/Expensive Connection}.
29657 @node Troubleshooting
29658 @section Troubleshooting
29659 @cindex troubleshooting
29661 Gnus works @emph{so} well straight out of the box---I can't imagine any
29669 Make sure your computer is switched on.
29672 Make sure that you really load the current Gnus version. If you have
29673 been running @sc{gnus}, you need to exit Emacs and start it up again before
29677 Try doing an @kbd{M-x gnus-version}. If you get something that looks
29679 @samp{No Gnus v0.10} @c Adjust ../Makefile.in if you change this line!
29681 you have the right files loaded. Otherwise you have some old @file{.el}
29682 files lying around. Delete these.
29685 Read the help group (@kbd{G h} in the group buffer) for a
29686 @acronym{FAQ} and a how-to.
29689 @vindex max-lisp-eval-depth
29690 Gnus works on many recursive structures, and in some extreme (and very
29691 rare) cases Gnus may recurse down ``too deeply'' and Emacs will beep at
29692 you. If this happens to you, set @code{max-lisp-eval-depth} to 500 or
29693 something like that.
29696 If all else fails, report the problem as a bug.
29699 @cindex reporting bugs
29701 @kindex M-x gnus-bug
29703 If you find a bug in Gnus, you can report it with the @kbd{M-x gnus-bug}
29704 command. @kbd{M-x set-variable RET debug-on-error RET t RET}, and send
29705 me the backtrace. I will fix bugs, but I can only fix them if you send
29706 me a precise description as to how to reproduce the bug.
29708 You really can never be too detailed in a bug report. Always use the
29709 @kbd{M-x gnus-bug} command when you make bug reports, even if it creates
29710 a 10Kb mail each time you use it, and even if you have sent me your
29711 environment 500 times before. I don't care. I want the full info each
29714 It is also important to remember that I have no memory whatsoever. If
29715 you send a bug report, and I send you a reply, and then you just send
29716 back ``No, it's not! Moron!'', I will have no idea what you are
29717 insulting me about. Always over-explain everything. It's much easier
29718 for all of us---if I don't have all the information I need, I will just
29719 mail you and ask for more info, and everything takes more time.
29721 If the problem you're seeing is very visual, and you can't quite explain
29722 it, copy the Emacs window to a file (with @code{xwd}, for instance), put
29723 it somewhere it can be reached, and include the URL of the picture in
29727 If you would like to contribute a patch to fix bugs or make
29728 improvements, please produce the patch using @samp{diff -u}.
29731 If you want to debug your problem further before reporting, possibly
29732 in order to solve the problem yourself and send a patch, you can use
29733 edebug. Debugging Lisp code is documented in the Elisp manual
29734 (@pxref{Debugging, , Debugging Lisp Programs, elisp, The GNU Emacs
29735 Lisp Reference Manual}). To get you started with edebug, consider if
29736 you discover some weird behavior when pressing @kbd{c}, the first
29737 step is to do @kbd{C-h k c} and click on the hyperlink (Emacs only) in
29738 the documentation buffer that leads you to the function definition,
29739 then press @kbd{M-x edebug-defun RET} with point inside that function,
29740 return to Gnus and press @kbd{c} to invoke the code. You will be
29741 placed in the lisp buffer and can single step using @kbd{SPC} and
29742 evaluate expressions using @kbd{M-:} or inspect variables using
29743 @kbd{C-h v}, abort execution with @kbd{q}, and resume execution with
29744 @kbd{c} or @kbd{g}.
29749 Sometimes, a problem do not directly generate an elisp error but
29750 manifests itself by causing Gnus to be very slow. In these cases, you
29751 can use @kbd{M-x toggle-debug-on-quit} and press @kbd{C-g} when things are
29752 slow, and then try to analyze the backtrace (repeating the procedure
29753 helps isolating the real problem areas).
29755 A fancier approach is to use the elisp profiler, ELP. The profiler is
29756 (or should be) fully documented elsewhere, but to get you started
29757 there are a few steps that need to be followed. First, instrument the
29758 part of Gnus you are interested in for profiling, e.g. @kbd{M-x
29759 elp-instrument-package RET gnus} or @kbd{M-x elp-instrument-package
29760 RET message}. Then perform the operation that is slow and press
29761 @kbd{M-x elp-results}. You will then see which operations that takes
29762 time, and can debug them further. If the entire operation takes much
29763 longer than the time spent in the slowest function in the profiler
29764 output, you probably profiled the wrong part of Gnus. To reset
29765 profiling statistics, use @kbd{M-x elp-reset-all}. @kbd{M-x
29766 elp-restore-all} is supposed to remove profiling, but given the
29767 complexities and dynamic code generation in Gnus, it might not always
29770 @cindex gnu.emacs.gnus
29771 @cindex ding mailing list
29772 If you just need help, you are better off asking on
29773 @samp{gnu.emacs.gnus}. I'm not very helpful. You can also ask on
29774 @email{ding@@gnus.org, the ding mailing list}. Write to
29775 @email{ding-request@@gnus.org} to subscribe.
29779 @node Gnus Reference Guide
29780 @section Gnus Reference Guide
29782 It is my hope that other people will figure out smart stuff that Gnus
29783 can do, and that other people will write those smart things as well. To
29784 facilitate that I thought it would be a good idea to describe the inner
29785 workings of Gnus. And some of the not-so-inner workings, while I'm at
29788 You can never expect the internals of a program not to change, but I
29789 will be defining (in some details) the interface between Gnus and its
29790 back ends (this is written in stone), the format of the score files
29791 (ditto), data structures (some are less likely to change than others)
29792 and general methods of operation.
29795 * Gnus Utility Functions:: Common functions and variable to use.
29796 * Back End Interface:: How Gnus communicates with the servers.
29797 * Score File Syntax:: A BNF definition of the score file standard.
29798 * Headers:: How Gnus stores headers internally.
29799 * Ranges:: A handy format for storing mucho numbers.
29800 * Group Info:: The group info format.
29801 * Extended Interactive:: Symbolic prefixes and stuff.
29802 * Emacs/XEmacs Code:: Gnus can be run under all modern Emacsen.
29803 * Various File Formats:: Formats of files that Gnus use.
29807 @node Gnus Utility Functions
29808 @subsection Gnus Utility Functions
29809 @cindex Gnus utility functions
29810 @cindex utility functions
29812 @cindex internal variables
29814 When writing small functions to be run from hooks (and stuff), it's
29815 vital to have access to the Gnus internal functions and variables.
29816 Below is a list of the most common ones.
29820 @item gnus-newsgroup-name
29821 @vindex gnus-newsgroup-name
29822 This variable holds the name of the current newsgroup.
29824 @item gnus-find-method-for-group
29825 @findex gnus-find-method-for-group
29826 A function that returns the select method for @var{group}.
29828 @item gnus-group-real-name
29829 @findex gnus-group-real-name
29830 Takes a full (prefixed) Gnus group name, and returns the unprefixed
29833 @item gnus-group-prefixed-name
29834 @findex gnus-group-prefixed-name
29835 Takes an unprefixed group name and a select method, and returns the full
29836 (prefixed) Gnus group name.
29838 @item gnus-get-info
29839 @findex gnus-get-info
29840 Returns the group info list for @var{group}.
29842 @item gnus-group-unread
29843 @findex gnus-group-unread
29844 The number of unread articles in @var{group}, or @code{t} if that is
29848 @findex gnus-active
29849 The active entry for @var{group}.
29851 @item gnus-set-active
29852 @findex gnus-set-active
29853 Set the active entry for @var{group}.
29855 @item gnus-add-current-to-buffer-list
29856 @findex gnus-add-current-to-buffer-list
29857 Adds the current buffer to the list of buffers to be killed on Gnus
29860 @item gnus-continuum-version
29861 @findex gnus-continuum-version
29862 Takes a Gnus version string as a parameter and returns a floating point
29863 number. Earlier versions will always get a lower number than later
29866 @item gnus-group-read-only-p
29867 @findex gnus-group-read-only-p
29868 Says whether @var{group} is read-only or not.
29870 @item gnus-news-group-p
29871 @findex gnus-news-group-p
29872 Says whether @var{group} came from a news back end.
29874 @item gnus-ephemeral-group-p
29875 @findex gnus-ephemeral-group-p
29876 Says whether @var{group} is ephemeral or not.
29878 @item gnus-server-to-method
29879 @findex gnus-server-to-method
29880 Returns the select method corresponding to @var{server}.
29882 @item gnus-server-equal
29883 @findex gnus-server-equal
29884 Says whether two virtual servers are equal.
29886 @item gnus-group-native-p
29887 @findex gnus-group-native-p
29888 Says whether @var{group} is native or not.
29890 @item gnus-group-secondary-p
29891 @findex gnus-group-secondary-p
29892 Says whether @var{group} is secondary or not.
29894 @item gnus-group-foreign-p
29895 @findex gnus-group-foreign-p
29896 Says whether @var{group} is foreign or not.
29898 @item gnus-group-find-parameter
29899 @findex gnus-group-find-parameter
29900 Returns the parameter list of @var{group}. If given a second parameter,
29901 returns the value of that parameter for @var{group}.
29903 @item gnus-group-set-parameter
29904 @findex gnus-group-set-parameter
29905 Takes three parameters; @var{group}, @var{parameter} and @var{value}.
29907 @item gnus-narrow-to-body
29908 @findex gnus-narrow-to-body
29909 Narrows the current buffer to the body of the article.
29911 @item gnus-check-backend-function
29912 @findex gnus-check-backend-function
29913 Takes two parameters, @var{function} and @var{group}. If the back end
29914 @var{group} comes from supports @var{function}, return non-@code{nil}.
29917 (gnus-check-backend-function "request-scan" "nnml:misc")
29921 @item gnus-read-method
29922 @findex gnus-read-method
29923 Prompts the user for a select method.
29928 @node Back End Interface
29929 @subsection Back End Interface
29931 Gnus doesn't know anything about @acronym{NNTP}, spools, mail or virtual
29932 groups. It only knows how to talk to @dfn{virtual servers}. A virtual
29933 server is a @dfn{back end} and some @dfn{back end variables}. As examples
29934 of the first, we have @code{nntp}, @code{nnspool} and @code{nnmbox}. As
29935 examples of the latter we have @code{nntp-port-number} and
29936 @code{nnmbox-directory}.
29938 When Gnus asks for information from a back end---say @code{nntp}---on
29939 something, it will normally include a virtual server name in the
29940 function parameters. (If not, the back end should use the ``current''
29941 virtual server.) For instance, @code{nntp-request-list} takes a virtual
29942 server as its only (optional) parameter. If this virtual server hasn't
29943 been opened, the function should fail.
29945 Note that a virtual server name has no relation to some physical server
29946 name. Take this example:
29950 (nntp-address "ifi.uio.no")
29951 (nntp-port-number 4324))
29954 Here the virtual server name is @samp{odd-one} while the name of
29955 the physical server is @samp{ifi.uio.no}.
29957 The back ends should be able to switch between several virtual servers.
29958 The standard back ends implement this by keeping an alist of virtual
29959 server environments that they pull down/push up when needed.
29961 There are two groups of interface functions: @dfn{required functions},
29962 which must be present, and @dfn{optional functions}, which Gnus will
29963 always check for presence before attempting to call 'em.
29965 All these functions are expected to return data in the buffer
29966 @code{nntp-server-buffer} (@samp{ *nntpd*}), which is somewhat
29967 unfortunately named, but we'll have to live with it. When I talk about
29968 @dfn{resulting data}, I always refer to the data in that buffer. When I
29969 talk about @dfn{return value}, I talk about the function value returned by
29970 the function call. Functions that fail should return @code{nil} as the
29973 Some back ends could be said to be @dfn{server-forming} back ends, and
29974 some might be said not to be. The latter are back ends that generally
29975 only operate on one group at a time, and have no concept of ``server''
29976 ---they have a group, and they deliver info on that group and nothing
29979 Gnus identifies each message by way of group name and article number. A
29980 few remarks about these article numbers might be useful. First of all,
29981 the numbers are positive integers. Secondly, it is normally not
29982 possible for later articles to ``re-use'' older article numbers without
29983 confusing Gnus. That is, if a group has ever contained a message
29984 numbered 42, then no other message may get that number, or Gnus will get
29985 mightily confused.@footnote{See the function
29986 @code{nnchoke-request-update-info}, @ref{Optional Back End Functions}.}
29987 Third, article numbers must be assigned in order of arrival in the
29988 group; this is not necessarily the same as the date of the message.
29990 The previous paragraph already mentions all the ``hard'' restrictions that
29991 article numbers must fulfill. But it seems that it might be useful to
29992 assign @emph{consecutive} article numbers, for Gnus gets quite confused
29993 if there are holes in the article numbering sequence. However, due to
29994 the ``no-reuse'' restriction, holes cannot be avoided altogether. It's
29995 also useful for the article numbers to start at 1 to avoid running out
29996 of numbers as long as possible.
29998 Note that by convention, back ends are named @code{nnsomething}, but
29999 Gnus also comes with some @code{nnnotbackends}, such as
30000 @file{nnheader.el}, @file{nnmail.el} and @file{nnoo.el}.
30002 In the examples and definitions I will refer to the imaginary back end
30005 @cindex @code{nnchoke}
30008 * Required Back End Functions:: Functions that must be implemented.
30009 * Optional Back End Functions:: Functions that need not be implemented.
30010 * Error Messaging:: How to get messages and report errors.
30011 * Writing New Back Ends:: Extending old back ends.
30012 * Hooking New Back Ends Into Gnus:: What has to be done on the Gnus end.
30013 * Mail-like Back Ends:: Some tips on mail back ends.
30017 @node Required Back End Functions
30018 @subsubsection Required Back End Functions
30022 @item (nnchoke-retrieve-headers ARTICLES &optional GROUP SERVER FETCH-OLD)
30024 @var{articles} is either a range of article numbers or a list of
30025 @code{Message-ID}s. Current back ends do not fully support either---only
30026 sequences (lists) of article numbers, and most back ends do not support
30027 retrieval of @code{Message-ID}s. But they should try for both.
30029 The result data should either be HEADs or @acronym{NOV} lines, and the result
30030 value should either be @code{headers} or @code{nov} to reflect this.
30031 This might later be expanded to @code{various}, which will be a mixture
30032 of HEADs and @acronym{NOV} lines, but this is currently not supported by Gnus.
30034 If @var{fetch-old} is non-@code{nil} it says to try fetching ``extra
30035 headers'', in some meaning of the word. This is generally done by
30036 fetching (at most) @var{fetch-old} extra headers less than the smallest
30037 article number in @code{articles}, and filling the gaps as well. The
30038 presence of this parameter can be ignored if the back end finds it
30039 cumbersome to follow the request. If this is non-@code{nil} and not a
30040 number, do maximum fetches.
30042 Here's an example HEAD:
30045 221 1056 Article retrieved.
30046 Path: ifi.uio.no!sturles
30047 From: sturles@@ifi.uio.no (Sturle Sunde)
30048 Newsgroups: ifi.discussion
30049 Subject: Re: Something very droll
30050 Date: 27 Oct 1994 14:02:57 +0100
30051 Organization: Dept. of Informatics, University of Oslo, Norway
30053 Message-ID: <38o8e1$a0o@@holmenkollen.ifi.uio.no>
30054 References: <38jdmq$4qu@@visbur.ifi.uio.no>
30055 NNTP-Posting-Host: holmenkollen.ifi.uio.no
30059 So a @code{headers} return value would imply that there's a number of
30060 these in the data buffer.
30062 Here's a BNF definition of such a buffer:
30066 head = error / valid-head
30067 error-message = [ "4" / "5" ] 2number " " <error message> eol
30068 valid-head = valid-message *header "." eol
30069 valid-message = "221 " <number> " Article retrieved." eol
30070 header = <text> eol
30074 (The version of BNF used here is the one used in RFC822.)
30076 If the return value is @code{nov}, the data buffer should contain
30077 @dfn{network overview database} lines. These are basically fields
30081 nov-buffer = *nov-line
30082 nov-line = field 7*8[ <TAB> field ] eol
30083 field = <text except TAB>
30086 For a closer look at what should be in those fields,
30090 @item (nnchoke-open-server SERVER &optional DEFINITIONS)
30092 @var{server} is here the virtual server name. @var{definitions} is a
30093 list of @code{(VARIABLE VALUE)} pairs that define this virtual server.
30095 If the server can't be opened, no error should be signaled. The back end
30096 may then choose to refuse further attempts at connecting to this
30097 server. In fact, it should do so.
30099 If the server is opened already, this function should return a
30100 non-@code{nil} value. There should be no data returned.
30103 @item (nnchoke-close-server &optional SERVER)
30105 Close connection to @var{server} and free all resources connected
30106 to it. Return @code{nil} if the server couldn't be closed for some
30109 There should be no data returned.
30112 @item (nnchoke-request-close)
30114 Close connection to all servers and free all resources that the back end
30115 have reserved. All buffers that have been created by that back end
30116 should be killed. (Not the @code{nntp-server-buffer}, though.) This
30117 function is generally only called when Gnus is shutting down.
30119 There should be no data returned.
30122 @item (nnchoke-server-opened &optional SERVER)
30124 If @var{server} is the current virtual server, and the connection to the
30125 physical server is alive, then this function should return a
30126 non-@code{nil} value. This function should under no circumstances
30127 attempt to reconnect to a server we have lost connection to.
30129 There should be no data returned.
30132 @item (nnchoke-status-message &optional SERVER)
30134 This function should return the last error message from @var{server}.
30136 There should be no data returned.
30139 @item (nnchoke-request-article ARTICLE &optional GROUP SERVER TO-BUFFER)
30141 The result data from this function should be the article specified by
30142 @var{article}. This might either be a @code{Message-ID} or a number.
30143 It is optional whether to implement retrieval by @code{Message-ID}, but
30144 it would be nice if that were possible.
30146 If @var{to-buffer} is non-@code{nil}, the result data should be returned
30147 in this buffer instead of the normal data buffer. This is to make it
30148 possible to avoid copying large amounts of data from one buffer to
30149 another, while Gnus mainly requests articles to be inserted directly
30150 into its article buffer.
30152 If it is at all possible, this function should return a cons cell where
30153 the @code{car} is the group name the article was fetched from, and the @code{cdr} is
30154 the article number. This will enable Gnus to find out what the real
30155 group and article numbers are when fetching articles by
30156 @code{Message-ID}. If this isn't possible, @code{t} should be returned
30157 on successful article retrieval.
30160 @item (nnchoke-request-group GROUP &optional SERVER FAST)
30162 Get data on @var{group}. This function also has the side effect of
30163 making @var{group} the current group.
30165 If @var{fast}, don't bother to return useful data, just make @var{group}
30168 Here's an example of some result data and a definition of the same:
30171 211 56 1000 1059 ifi.discussion
30174 The first number is the status, which should be 211. Next is the
30175 total number of articles in the group, the lowest article number, the
30176 highest article number, and finally the group name. Note that the total
30177 number of articles may be less than one might think while just
30178 considering the highest and lowest article numbers, but some articles
30179 may have been canceled. Gnus just discards the total-number, so
30180 whether one should take the bother to generate it properly (if that is a
30181 problem) is left as an exercise to the reader. If the group contains no
30182 articles, the lowest article number should be reported as 1 and the
30186 group-status = [ error / info ] eol
30187 error = [ "4" / "5" ] 2<number> " " <Error message>
30188 info = "211 " 3* [ <number> " " ] <string>
30192 @item (nnchoke-close-group GROUP &optional SERVER)
30194 Close @var{group} and free any resources connected to it. This will be
30195 a no-op on most back ends.
30197 There should be no data returned.
30200 @item (nnchoke-request-list &optional SERVER)
30202 Return a list of all groups available on @var{server}. And that means
30205 Here's an example from a server that only carries two groups:
30208 ifi.test 0000002200 0000002000 y
30209 ifi.discussion 3324 3300 n
30212 On each line we have a group name, then the highest article number in
30213 that group, the lowest article number, and finally a flag. If the group
30214 contains no articles, the lowest article number should be reported as 1
30215 and the highest as 0.
30218 active-file = *active-line
30219 active-line = name " " <number> " " <number> " " flags eol
30221 flags = "n" / "y" / "m" / "x" / "j" / "=" name
30224 The flag says whether the group is read-only (@samp{n}), is moderated
30225 (@samp{m}), is dead (@samp{x}), is aliased to some other group
30226 (@samp{=other-group}) or none of the above (@samp{y}).
30229 @item (nnchoke-request-post &optional SERVER)
30231 This function should post the current buffer. It might return whether
30232 the posting was successful or not, but that's not required. If, for
30233 instance, the posting is done asynchronously, it has generally not been
30234 completed by the time this function concludes. In that case, this
30235 function should set up some kind of sentinel to beep the user loud and
30236 clear if the posting could not be completed.
30238 There should be no result data from this function.
30243 @node Optional Back End Functions
30244 @subsubsection Optional Back End Functions
30248 @item (nnchoke-retrieve-groups GROUPS &optional SERVER)
30250 @var{groups} is a list of groups, and this function should request data
30251 on all those groups. How it does it is of no concern to Gnus, but it
30252 should attempt to do this in a speedy fashion.
30254 The return value of this function can be either @code{active} or
30255 @code{group}, which says what the format of the result data is. The
30256 former is in the same format as the data from
30257 @code{nnchoke-request-list}, while the latter is a buffer full of lines
30258 in the same format as @code{nnchoke-request-group} gives.
30261 group-buffer = *active-line / *group-status
30265 @item (nnchoke-request-update-info GROUP INFO &optional SERVER)
30267 A Gnus group info (@pxref{Group Info}) is handed to the back end for
30268 alterations. This comes in handy if the back end really carries all
30269 the information (as is the case with virtual and imap groups). This
30270 function should destructively alter the info to suit its needs, and
30271 should return a non-@code{nil} value (exceptionally,
30272 @code{nntp-request-update-info} always returns @code{nil} not to waste
30273 the network resources).
30275 There should be no result data from this function.
30278 @item (nnchoke-request-type GROUP &optional ARTICLE)
30280 When the user issues commands for ``sending news'' (@kbd{F} in the
30281 summary buffer, for instance), Gnus has to know whether the article the
30282 user is following up on is news or mail. This function should return
30283 @code{news} if @var{article} in @var{group} is news, @code{mail} if it
30284 is mail and @code{unknown} if the type can't be decided. (The
30285 @var{article} parameter is necessary in @code{nnvirtual} groups which
30286 might very well combine mail groups and news groups.) Both @var{group}
30287 and @var{article} may be @code{nil}.
30289 There should be no result data from this function.
30292 @item (nnchoke-request-set-mark GROUP ACTION &optional SERVER)
30294 Set/remove/add marks on articles. Normally Gnus handles the article
30295 marks (such as read, ticked, expired etc) internally, and store them in
30296 @file{~/.newsrc.eld}. Some back ends (such as @acronym{IMAP}) however carry
30297 all information about the articles on the server, so Gnus need to
30298 propagate the mark information to the server.
30300 @var{action} is a list of mark setting requests, having this format:
30303 (RANGE ACTION MARK)
30306 @var{range} is a range of articles you wish to update marks on.
30307 @var{action} is @code{add} or @code{del}, used to add marks or remove
30308 marks (preserving all marks not mentioned). @var{mark} is a list of
30309 marks; where each mark is a symbol. Currently used marks are
30310 @code{read}, @code{tick}, @code{reply}, @code{expire}, @code{killed},
30311 @code{dormant}, @code{save}, @code{download}, @code{unsend},
30312 @code{forward} and @code{recent}, but your back end should, if
30313 possible, not limit itself to these.
30315 Given contradictory actions, the last action in the list should be the
30316 effective one. That is, if your action contains a request to add the
30317 @code{tick} mark on article 1 and, later in the list, a request to
30318 remove the mark on the same article, the mark should in fact be removed.
30320 An example action list:
30323 (((5 12 30) 'del '(tick))
30324 ((10 . 90) 'add '(read expire))
30325 ((92 94) 'del '(read)))
30328 The function should return a range of articles it wasn't able to set the
30329 mark on (currently not used for anything).
30331 There should be no result data from this function.
30333 @item (nnchoke-request-update-mark GROUP ARTICLE MARK)
30335 If the user tries to set a mark that the back end doesn't like, this
30336 function may change the mark. Gnus will use whatever this function
30337 returns as the mark for @var{article} instead of the original
30338 @var{mark}. If the back end doesn't care, it must return the original
30339 @var{mark}, and not @code{nil} or any other type of garbage.
30341 The only use for this I can see is what @code{nnvirtual} does with
30342 it---if a component group is auto-expirable, marking an article as read
30343 in the virtual group should result in the article being marked as
30346 There should be no result data from this function.
30349 @item (nnchoke-request-scan &optional GROUP SERVER)
30351 This function may be called at any time (by Gnus or anything else) to
30352 request that the back end check for incoming articles, in one way or
30353 another. A mail back end will typically read the spool file or query
30354 the @acronym{POP} server when this function is invoked. The
30355 @var{group} doesn't have to be heeded---if the back end decides that
30356 it is too much work just scanning for a single group, it may do a
30357 total scan of all groups. It would be nice, however, to keep things
30358 local if that's practical.
30360 There should be no result data from this function.
30363 @item (nnchoke-request-group-description GROUP &optional SERVER)
30365 The result data from this function should be a description of
30369 description-line = name <TAB> description eol
30371 description = <text>
30374 @item (nnchoke-request-list-newsgroups &optional SERVER)
30376 The result data from this function should be the description of all
30377 groups available on the server.
30380 description-buffer = *description-line
30384 @item (nnchoke-request-newgroups DATE &optional SERVER)
30386 The result data from this function should be all groups that were
30387 created after @samp{date}, which is in normal human-readable date format
30388 (i.e., the date format used in mail and news headers, and returned by
30389 the function @code{message-make-date} by default). The data should be
30390 in the active buffer format.
30392 It is okay for this function to return ``too many'' groups; some back ends
30393 might find it cheaper to return the full list of groups, rather than
30394 just the new groups. But don't do this for back ends with many groups.
30395 Normally, if the user creates the groups herself, there won't be too
30396 many groups, so @code{nnml} and the like are probably safe. But for
30397 back ends like @code{nntp}, where the groups have been created by the
30398 server, it is quite likely that there can be many groups.
30401 @item (nnchoke-request-create-group GROUP &optional SERVER)
30403 This function should create an empty group with name @var{group}.
30405 There should be no return data.
30408 @item (nnchoke-request-expire-articles ARTICLES &optional GROUP SERVER FORCE)
30410 This function should run the expiry process on all articles in the
30411 @var{articles} range (which is currently a simple list of article
30412 numbers.) It is left up to the back end to decide how old articles
30413 should be before they are removed by this function. If @var{force} is
30414 non-@code{nil}, all @var{articles} should be deleted, no matter how new
30417 This function should return a list of articles that it did not/was not
30420 There should be no result data returned.
30423 @item (nnchoke-request-move-article ARTICLE GROUP SERVER ACCEPT-FORM &optional LAST)
30425 This function should move @var{article} (which is a number) from
30426 @var{group} by calling @var{accept-form}.
30428 This function should ready the article in question for moving by
30429 removing any header lines it has added to the article, and generally
30430 should ``tidy up'' the article. Then it should @code{eval}
30431 @var{accept-form} in the buffer where the ``tidy'' article is. This
30432 will do the actual copying. If this @code{eval} returns a
30433 non-@code{nil} value, the article should be removed.
30435 If @var{last} is @code{nil}, that means that there is a high likelihood
30436 that there will be more requests issued shortly, so that allows some
30439 The function should return a cons where the @code{car} is the group name and
30440 the @code{cdr} is the article number that the article was entered as.
30442 There should be no data returned.
30445 @item (nnchoke-request-accept-article GROUP &optional SERVER LAST)
30447 This function takes the current buffer and inserts it into @var{group}.
30448 If @var{last} in @code{nil}, that means that there will be more calls to
30449 this function in short order.
30451 The function should return a cons where the @code{car} is the group name and
30452 the @code{cdr} is the article number that the article was entered as.
30454 The group should exist before the back end is asked to accept the
30455 article for that group.
30457 There should be no data returned.
30460 @item (nnchoke-request-replace-article ARTICLE GROUP BUFFER)
30462 This function should remove @var{article} (which is a number) from
30463 @var{group} and insert @var{buffer} there instead.
30465 There should be no data returned.
30468 @item (nnchoke-request-delete-group GROUP FORCE &optional SERVER)
30470 This function should delete @var{group}. If @var{force}, it should
30471 really delete all the articles in the group, and then delete the group
30472 itself. (If there is such a thing as ``the group itself''.)
30474 There should be no data returned.
30477 @item (nnchoke-request-rename-group GROUP NEW-NAME &optional SERVER)
30479 This function should rename @var{group} into @var{new-name}. All
30480 articles in @var{group} should move to @var{new-name}.
30482 There should be no data returned.
30487 @node Error Messaging
30488 @subsubsection Error Messaging
30490 @findex nnheader-report
30491 @findex nnheader-get-report
30492 The back ends should use the function @code{nnheader-report} to report
30493 error conditions---they should not raise errors when they aren't able to
30494 perform a request. The first argument to this function is the back end
30495 symbol, and the rest are interpreted as arguments to @code{format} if
30496 there are multiple of them, or just a string if there is one of them.
30497 This function must always returns @code{nil}.
30500 (nnheader-report 'nnchoke "You did something totally bogus")
30502 (nnheader-report 'nnchoke "Could not request group %s" group)
30505 Gnus, in turn, will call @code{nnheader-get-report} when it gets a
30506 @code{nil} back from a server, and this function returns the most
30507 recently reported message for the back end in question. This function
30508 takes one argument---the server symbol.
30510 Internally, these functions access @var{back-end}@code{-status-string},
30511 so the @code{nnchoke} back end will have its error message stored in
30512 @code{nnchoke-status-string}.
30515 @node Writing New Back Ends
30516 @subsubsection Writing New Back Ends
30518 Many back ends are quite similar. @code{nnml} is just like
30519 @code{nnspool}, but it allows you to edit the articles on the server.
30520 @code{nnmh} is just like @code{nnml}, but it doesn't use an active file,
30521 and it doesn't maintain overview databases. @code{nndir} is just like
30522 @code{nnml}, but it has no concept of ``groups'', and it doesn't allow
30525 It would make sense if it were possible to ``inherit'' functions from
30526 back ends when writing new back ends. And, indeed, you can do that if you
30527 want to. (You don't have to if you don't want to, of course.)
30529 All the back ends declare their public variables and functions by using a
30530 package called @code{nnoo}.
30532 To inherit functions from other back ends (and allow other back ends to
30533 inherit functions from the current back end), you should use the
30539 This macro declares the first parameter to be a child of the subsequent
30540 parameters. For instance:
30543 (nnoo-declare nndir
30547 @code{nndir} has declared here that it intends to inherit functions from
30548 both @code{nnml} and @code{nnmh}.
30551 This macro is equivalent to @code{defvar}, but registers the variable as
30552 a public server variable. Most state-oriented variables should be
30553 declared with @code{defvoo} instead of @code{defvar}.
30555 In addition to the normal @code{defvar} parameters, it takes a list of
30556 variables in the parent back ends to map the variable to when executing
30557 a function in those back ends.
30560 (defvoo nndir-directory nil
30561 "Where nndir will look for groups."
30562 nnml-current-directory nnmh-current-directory)
30565 This means that @code{nnml-current-directory} will be set to
30566 @code{nndir-directory} when an @code{nnml} function is called on behalf
30567 of @code{nndir}. (The same with @code{nnmh}.)
30569 @item nnoo-define-basics
30570 This macro defines some common functions that almost all back ends should
30574 (nnoo-define-basics nndir)
30578 This macro is just like @code{defun} and takes the same parameters. In
30579 addition to doing the normal @code{defun} things, it registers the
30580 function as being public so that other back ends can inherit it.
30582 @item nnoo-map-functions
30583 This macro allows mapping of functions from the current back end to
30584 functions from the parent back ends.
30587 (nnoo-map-functions nndir
30588 (nnml-retrieve-headers 0 nndir-current-group 0 0)
30589 (nnmh-request-article 0 nndir-current-group 0 0))
30592 This means that when @code{nndir-retrieve-headers} is called, the first,
30593 third, and fourth parameters will be passed on to
30594 @code{nnml-retrieve-headers}, while the second parameter is set to the
30595 value of @code{nndir-current-group}.
30598 This macro allows importing functions from back ends. It should be the
30599 last thing in the source file, since it will only define functions that
30600 haven't already been defined.
30606 nnmh-request-newgroups)
30610 This means that calls to @code{nndir-request-list} should just be passed
30611 on to @code{nnmh-request-list}, while all public functions from
30612 @code{nnml} that haven't been defined in @code{nndir} yet should be
30617 Below is a slightly shortened version of the @code{nndir} back end.
30620 ;;; @r{nndir.el --- single directory newsgroup access for Gnus}
30621 ;; @r{Copyright (C) 1995,1996 Free Software Foundation, Inc.}
30625 (require 'nnheader)
30629 (eval-when-compile (require 'cl))
30631 (nnoo-declare nndir
30634 (defvoo nndir-directory nil
30635 "Where nndir will look for groups."
30636 nnml-current-directory nnmh-current-directory)
30638 (defvoo nndir-nov-is-evil nil
30639 "*Non-nil means that nndir will never retrieve NOV headers."
30642 (defvoo nndir-current-group ""
30644 nnml-current-group nnmh-current-group)
30645 (defvoo nndir-top-directory nil nil nnml-directory nnmh-directory)
30646 (defvoo nndir-get-new-mail nil nil nnml-get-new-mail nnmh-get-new-mail)
30648 (defvoo nndir-status-string "" nil nnmh-status-string)
30649 (defconst nndir-version "nndir 1.0")
30651 ;;; @r{Interface functions.}
30653 (nnoo-define-basics nndir)
30655 (deffoo nndir-open-server (server &optional defs)
30656 (setq nndir-directory
30657 (or (cadr (assq 'nndir-directory defs))
30659 (unless (assq 'nndir-directory defs)
30660 (push `(nndir-directory ,server) defs))
30661 (push `(nndir-current-group
30662 ,(file-name-nondirectory
30663 (directory-file-name nndir-directory)))
30665 (push `(nndir-top-directory
30666 ,(file-name-directory (directory-file-name nndir-directory)))
30668 (nnoo-change-server 'nndir server defs))
30670 (nnoo-map-functions nndir
30671 (nnml-retrieve-headers 0 nndir-current-group 0 0)
30672 (nnmh-request-article 0 nndir-current-group 0 0)
30673 (nnmh-request-group nndir-current-group 0 0)
30674 (nnmh-close-group nndir-current-group 0))
30678 nnmh-status-message
30680 nnmh-request-newgroups))
30686 @node Hooking New Back Ends Into Gnus
30687 @subsubsection Hooking New Back Ends Into Gnus
30689 @vindex gnus-valid-select-methods
30690 @findex gnus-declare-backend
30691 Having Gnus start using your new back end is rather easy---you just
30692 declare it with the @code{gnus-declare-backend} functions. This will
30693 enter the back end into the @code{gnus-valid-select-methods} variable.
30695 @code{gnus-declare-backend} takes two parameters---the back end name and
30696 an arbitrary number of @dfn{abilities}.
30701 (gnus-declare-backend "nnchoke" 'mail 'respool 'address)
30704 The above line would then go in the @file{nnchoke.el} file.
30706 The abilities can be:
30710 This is a mailish back end---followups should (probably) go via mail.
30712 This is a newsish back end---followups should (probably) go via news.
30714 This back end supports both mail and news.
30716 This is neither a post nor mail back end---it's something completely
30719 It supports respooling---or rather, it is able to modify its source
30720 articles and groups.
30722 The name of the server should be in the virtual server name. This is
30723 true for almost all back ends.
30724 @item prompt-address
30725 The user should be prompted for an address when doing commands like
30726 @kbd{B} in the group buffer. This is true for back ends like
30727 @code{nntp}, but not @code{nnmbox}, for instance.
30731 @node Mail-like Back Ends
30732 @subsubsection Mail-like Back Ends
30734 One of the things that separate the mail back ends from the rest of the
30735 back ends is the heavy dependence by most of the mail back ends on
30736 common functions in @file{nnmail.el}. For instance, here's the
30737 definition of @code{nnml-request-scan}:
30740 (deffoo nnml-request-scan (&optional group server)
30741 (setq nnml-article-file-alist nil)
30742 (nnmail-get-new-mail 'nnml 'nnml-save-nov nnml-directory group))
30745 It simply calls @code{nnmail-get-new-mail} with a few parameters,
30746 and @code{nnmail} takes care of all the moving and splitting of the
30749 This function takes four parameters.
30753 This should be a symbol to designate which back end is responsible for
30756 @item exit-function
30757 This function should be called after the splitting has been performed.
30759 @item temp-directory
30760 Where the temporary files should be stored.
30763 This optional argument should be a group name if the splitting is to be
30764 performed for one group only.
30767 @code{nnmail-get-new-mail} will call @var{back-end}@code{-save-mail} to
30768 save each article. @var{back-end}@code{-active-number} will be called to
30769 find the article number assigned to this article.
30771 The function also uses the following variables:
30772 @var{back-end}@code{-get-new-mail} (to see whether to get new mail for
30773 this back end); and @var{back-end}@code{-group-alist} and
30774 @var{back-end}@code{-active-file} to generate the new active file.
30775 @var{back-end}@code{-group-alist} should be a group-active alist, like
30779 (("a-group" (1 . 10))
30780 ("some-group" (34 . 39)))
30784 @node Score File Syntax
30785 @subsection Score File Syntax
30787 Score files are meant to be easily parseable, but yet extremely
30788 mallable. It was decided that something that had the same read syntax
30789 as an Emacs Lisp list would fit that spec.
30791 Here's a typical score file:
30795 ("win95" -10000 nil s)
30802 BNF definition of a score file:
30805 score-file = "" / "(" *element ")"
30806 element = rule / atom
30807 rule = string-rule / number-rule / date-rule
30808 string-rule = "(" quote string-header quote space *string-match ")"
30809 number-rule = "(" quote number-header quote space *number-match ")"
30810 date-rule = "(" quote date-header quote space *date-match ")"
30812 string-header = "subject" / "from" / "references" / "message-id" /
30813 "xref" / "body" / "head" / "all" / "followup"
30814 number-header = "lines" / "chars"
30815 date-header = "date"
30816 string-match = "(" quote <string> quote [ "" / [ space score [ "" /
30817 space date [ "" / [ space string-match-t ] ] ] ] ] ")"
30818 score = "nil" / <integer>
30819 date = "nil" / <natural number>
30820 string-match-t = "nil" / "s" / "substring" / "S" / "Substring" /
30821 "r" / "regex" / "R" / "Regex" /
30822 "e" / "exact" / "E" / "Exact" /
30823 "f" / "fuzzy" / "F" / "Fuzzy"
30824 number-match = "(" <integer> [ "" / [ space score [ "" /
30825 space date [ "" / [ space number-match-t ] ] ] ] ] ")"
30826 number-match-t = "nil" / "=" / "<" / ">" / ">=" / "<="
30827 date-match = "(" quote <string> quote [ "" / [ space score [ "" /
30828 space date [ "" / [ space date-match-t ] ] ] ] ")"
30829 date-match-t = "nil" / "at" / "before" / "after"
30830 atom = "(" [ required-atom / optional-atom ] ")"
30831 required-atom = mark / expunge / mark-and-expunge / files /
30832 exclude-files / read-only / touched
30833 optional-atom = adapt / local / eval
30834 mark = "mark" space nil-or-number
30835 nil-or-number = "nil" / <integer>
30836 expunge = "expunge" space nil-or-number
30837 mark-and-expunge = "mark-and-expunge" space nil-or-number
30838 files = "files" *[ space <string> ]
30839 exclude-files = "exclude-files" *[ space <string> ]
30840 read-only = "read-only" [ space "nil" / space "t" ]
30841 adapt = "adapt" [ space "ignore" / space "t" / space adapt-rule ]
30842 adapt-rule = "(" *[ <string> *[ "(" <string> <integer> ")" ] ")"
30843 local = "local" *[ space "(" <string> space <form> ")" ]
30844 eval = "eval" space <form>
30845 space = *[ " " / <TAB> / <NEWLINE> ]
30848 Any unrecognized elements in a score file should be ignored, but not
30851 As you can see, white space is needed, but the type and amount of white
30852 space is irrelevant. This means that formatting of the score file is
30853 left up to the programmer---if it's simpler to just spew it all out on
30854 one looong line, then that's ok.
30856 The meaning of the various atoms are explained elsewhere in this
30857 manual (@pxref{Score File Format}).
30861 @subsection Headers
30863 Internally Gnus uses a format for storing article headers that
30864 corresponds to the @acronym{NOV} format in a mysterious fashion. One could
30865 almost suspect that the author looked at the @acronym{NOV} specification and
30866 just shamelessly @emph{stole} the entire thing, and one would be right.
30868 @dfn{Header} is a severely overloaded term. ``Header'' is used in
30869 RFC 1036 to talk about lines in the head of an article (e.g.,
30870 @code{From}). It is used by many people as a synonym for
30871 ``head''---``the header and the body''. (That should be avoided, in my
30872 opinion.) And Gnus uses a format internally that it calls ``header'',
30873 which is what I'm talking about here. This is a 9-element vector,
30874 basically, with each header (ouch) having one slot.
30876 These slots are, in order: @code{number}, @code{subject}, @code{from},
30877 @code{date}, @code{id}, @code{references}, @code{chars}, @code{lines},
30878 @code{xref}, and @code{extra}. There are macros for accessing and
30879 setting these slots---they all have predictable names beginning with
30880 @code{mail-header-} and @code{mail-header-set-}, respectively.
30882 All these slots contain strings, except the @code{extra} slot, which
30883 contains an alist of header/value pairs (@pxref{To From Newsgroups}).
30889 @sc{gnus} introduced a concept that I found so useful that I've started
30890 using it a lot and have elaborated on it greatly.
30892 The question is simple: If you have a large amount of objects that are
30893 identified by numbers (say, articles, to take a @emph{wild} example)
30894 that you want to qualify as being ``included'', a normal sequence isn't
30895 very useful. (A 200,000 length sequence is a bit long-winded.)
30897 The solution is as simple as the question: You just collapse the
30901 (1 2 3 4 5 6 10 11 12)
30904 is transformed into
30907 ((1 . 6) (10 . 12))
30910 To avoid having those nasty @samp{(13 . 13)} elements to denote a
30911 lonesome object, a @samp{13} is a valid element:
30914 ((1 . 6) 7 (10 . 12))
30917 This means that comparing two ranges to find out whether they are equal
30918 is slightly tricky:
30921 ((1 . 5) 7 8 (10 . 12))
30927 ((1 . 5) (7 . 8) (10 . 12))
30930 are equal. In fact, any non-descending list is a range:
30936 is a perfectly valid range, although a pretty long-winded one. This is
30943 and is equal to the previous range.
30945 Here's a BNF definition of ranges. Of course, one must remember the
30946 semantic requirement that the numbers are non-descending. (Any number
30947 of repetition of the same number is allowed, but apt to disappear in
30951 range = simple-range / normal-range
30952 simple-range = "(" number " . " number ")"
30953 normal-range = "(" start-contents ")"
30954 contents = "" / simple-range *[ " " contents ] /
30955 number *[ " " contents ]
30958 Gnus currently uses ranges to keep track of read articles and article
30959 marks. I plan on implementing a number of range operators in C if The
30960 Powers That Be are willing to let me. (I haven't asked yet, because I
30961 need to do some more thinking on what operators I need to make life
30962 totally range-based without ever having to convert back to normal
30967 @subsection Group Info
30969 Gnus stores all permanent info on groups in a @dfn{group info} list.
30970 This list is from three to six elements (or more) long and exhaustively
30971 describes the group.
30973 Here are two example group infos; one is a very simple group while the
30974 second is a more complex one:
30977 ("no.group" 5 ((1 . 54324)))
30979 ("nnml:my.mail" 3 ((1 . 5) 9 (20 . 55))
30980 ((tick (15 . 19)) (replied 3 6 (19 . 3)))
30982 ((auto-expire . t) (to-address . "ding@@gnus.org")))
30985 The first element is the @dfn{group name}---as Gnus knows the group,
30986 anyway. The second element is the @dfn{subscription level}, which
30987 normally is a small integer. (It can also be the @dfn{rank}, which is a
30988 cons cell where the @code{car} is the level and the @code{cdr} is the
30989 score.) The third element is a list of ranges of read articles. The
30990 fourth element is a list of lists of article marks of various kinds.
30991 The fifth element is the select method (or virtual server, if you like).
30992 The sixth element is a list of @dfn{group parameters}, which is what
30993 this section is about.
30995 Any of the last three elements may be missing if they are not required.
30996 In fact, the vast majority of groups will normally only have the first
30997 three elements, which saves quite a lot of cons cells.
30999 Here's a BNF definition of the group info format:
31002 info = "(" group space ralevel space read
31003 [ "" / [ space marks-list [ "" / [ space method [ "" /
31004 space parameters ] ] ] ] ] ")"
31005 group = quote <string> quote
31006 ralevel = rank / level
31007 level = <integer in the range of 1 to inf>
31008 rank = "(" level "." score ")"
31009 score = <integer in the range of 1 to inf>
31011 marks-lists = nil / "(" *marks ")"
31012 marks = "(" <string> range ")"
31013 method = "(" <string> *elisp-forms ")"
31014 parameters = "(" *elisp-forms ")"
31017 Actually that @samp{marks} rule is a fib. A @samp{marks} is a
31018 @samp{<string>} consed on to a @samp{range}, but that's a bitch to say
31021 If you have a Gnus info and want to access the elements, Gnus offers a
31022 series of macros for getting/setting these elements.
31025 @item gnus-info-group
31026 @itemx gnus-info-set-group
31027 @findex gnus-info-group
31028 @findex gnus-info-set-group
31029 Get/set the group name.
31031 @item gnus-info-rank
31032 @itemx gnus-info-set-rank
31033 @findex gnus-info-rank
31034 @findex gnus-info-set-rank
31035 Get/set the group rank (@pxref{Group Score}).
31037 @item gnus-info-level
31038 @itemx gnus-info-set-level
31039 @findex gnus-info-level
31040 @findex gnus-info-set-level
31041 Get/set the group level.
31043 @item gnus-info-score
31044 @itemx gnus-info-set-score
31045 @findex gnus-info-score
31046 @findex gnus-info-set-score
31047 Get/set the group score (@pxref{Group Score}).
31049 @item gnus-info-read
31050 @itemx gnus-info-set-read
31051 @findex gnus-info-read
31052 @findex gnus-info-set-read
31053 Get/set the ranges of read articles.
31055 @item gnus-info-marks
31056 @itemx gnus-info-set-marks
31057 @findex gnus-info-marks
31058 @findex gnus-info-set-marks
31059 Get/set the lists of ranges of marked articles.
31061 @item gnus-info-method
31062 @itemx gnus-info-set-method
31063 @findex gnus-info-method
31064 @findex gnus-info-set-method
31065 Get/set the group select method.
31067 @item gnus-info-params
31068 @itemx gnus-info-set-params
31069 @findex gnus-info-params
31070 @findex gnus-info-set-params
31071 Get/set the group parameters.
31074 All the getter functions take one parameter---the info list. The setter
31075 functions take two parameters---the info list and the new value.
31077 The last three elements in the group info aren't mandatory, so it may be
31078 necessary to extend the group info before setting the element. If this
31079 is necessary, you can just pass on a non-@code{nil} third parameter to
31080 the three final setter functions to have this happen automatically.
31083 @node Extended Interactive
31084 @subsection Extended Interactive
31085 @cindex interactive
31086 @findex gnus-interactive
31088 Gnus extends the standard Emacs @code{interactive} specification
31089 slightly to allow easy use of the symbolic prefix (@pxref{Symbolic
31090 Prefixes}). Here's an example of how this is used:
31093 (defun gnus-summary-increase-score (&optional score symp)
31094 (interactive (gnus-interactive "P\ny"))
31099 The best thing to do would have been to implement
31100 @code{gnus-interactive} as a macro which would have returned an
31101 @code{interactive} form, but this isn't possible since Emacs checks
31102 whether a function is interactive or not by simply doing an @code{assq}
31103 on the lambda form. So, instead we have @code{gnus-interactive}
31104 function that takes a string and returns values that are usable to
31105 @code{interactive}.
31107 This function accepts (almost) all normal @code{interactive} specs, but
31112 @vindex gnus-current-prefix-symbol
31113 The current symbolic prefix---the @code{gnus-current-prefix-symbol}
31117 @vindex gnus-current-prefix-symbols
31118 A list of the current symbolic prefixes---the
31119 @code{gnus-current-prefix-symbol} variable.
31122 The current article number---the @code{gnus-summary-article-number}
31126 The current article header---the @code{gnus-summary-article-header}
31130 The current group name---the @code{gnus-group-group-name}
31136 @node Emacs/XEmacs Code
31137 @subsection Emacs/XEmacs Code
31141 While Gnus runs under Emacs, XEmacs and Mule, I decided that one of the
31142 platforms must be the primary one. I chose Emacs. Not because I don't
31143 like XEmacs or Mule, but because it comes first alphabetically.
31145 This means that Gnus will byte-compile under Emacs with nary a warning,
31146 while XEmacs will pump out gigabytes of warnings while byte-compiling.
31147 As I use byte-compilation warnings to help me root out trivial errors in
31148 Gnus, that's very useful.
31150 I've also consistently used Emacs function interfaces, but have used
31151 Gnusey aliases for the functions. To take an example: Emacs defines a
31152 @code{run-at-time} function while XEmacs defines a @code{start-itimer}
31153 function. I then define a function called @code{gnus-run-at-time} that
31154 takes the same parameters as the Emacs @code{run-at-time}. When running
31155 Gnus under Emacs, the former function is just an alias for the latter.
31156 However, when running under XEmacs, the former is an alias for the
31157 following function:
31160 (defun gnus-xmas-run-at-time (time repeat function &rest args)
31164 (,function ,@@args))
31168 This sort of thing has been done for bunches of functions. Gnus does
31169 not redefine any native Emacs functions while running under XEmacs---it
31170 does this @code{defalias} thing with Gnus equivalents instead. Cleaner
31173 In the cases where the XEmacs function interface was obviously cleaner,
31174 I used it instead. For example @code{gnus-region-active-p} is an alias
31175 for @code{region-active-p} in XEmacs, whereas in Emacs it is a function.
31177 Of course, I could have chosen XEmacs as my native platform and done
31178 mapping functions the other way around. But I didn't. The performance
31179 hit these indirections impose on Gnus under XEmacs should be slight.
31182 @node Various File Formats
31183 @subsection Various File Formats
31186 * Active File Format:: Information on articles and groups available.
31187 * Newsgroups File Format:: Group descriptions.
31191 @node Active File Format
31192 @subsubsection Active File Format
31194 The active file lists all groups available on the server in
31195 question. It also lists the highest and lowest current article numbers
31198 Here's an excerpt from a typical active file:
31201 soc.motss 296030 293865 y
31202 alt.binaries.pictures.fractals 3922 3913 n
31203 comp.sources.unix 1605 1593 m
31204 comp.binaries.ibm.pc 5097 5089 y
31205 no.general 1000 900 y
31208 Here's a pseudo-BNF definition of this file:
31211 active = *group-line
31212 group-line = group spc high-number spc low-number spc flag <NEWLINE>
31213 group = <non-white-space string>
31215 high-number = <non-negative integer>
31216 low-number = <positive integer>
31217 flag = "y" / "n" / "m" / "j" / "x" / "=" group
31220 For a full description of this file, see the manual pages for
31221 @samp{innd}, in particular @samp{active(5)}.
31224 @node Newsgroups File Format
31225 @subsubsection Newsgroups File Format
31227 The newsgroups file lists groups along with their descriptions. Not all
31228 groups on the server have to be listed, and not all groups in the file
31229 have to exist on the server. The file is meant purely as information to
31232 The format is quite simple; a group name, a tab, and the description.
31233 Here's the definition:
31237 line = group tab description <NEWLINE>
31238 group = <non-white-space string>
31240 description = <string>
31245 @node Emacs for Heathens
31246 @section Emacs for Heathens
31248 Believe it or not, but some people who use Gnus haven't really used
31249 Emacs much before they embarked on their journey on the Gnus Love Boat.
31250 If you are one of those unfortunates whom ``@kbd{C-M-a}'', ``kill the
31251 region'', and ``set @code{gnus-flargblossen} to an alist where the key
31252 is a regexp that is used for matching on the group name'' are magical
31253 phrases with little or no meaning, then this appendix is for you. If
31254 you are already familiar with Emacs, just ignore this and go fondle your
31258 * Keystrokes:: Entering text and executing commands.
31259 * Emacs Lisp:: The built-in Emacs programming language.
31264 @subsection Keystrokes
31268 Q: What is an experienced Emacs user?
31271 A: A person who wishes that the terminal had pedals.
31274 Yes, when you use Emacs, you are apt to use the control key, the shift
31275 key and the meta key a lot. This is very annoying to some people
31276 (notably @code{vi}le users), and the rest of us just love the hell out
31277 of it. Just give up and submit. Emacs really does stand for
31278 ``Escape-Meta-Alt-Control-Shift'', and not ``Editing Macros'', as you
31279 may have heard from other disreputable sources (like the Emacs author).
31281 The shift keys are normally located near your pinky fingers, and are
31282 normally used to get capital letters and stuff. You probably use it all
31283 the time. The control key is normally marked ``CTRL'' or something like
31284 that. The meta key is, funnily enough, never marked as such on any
31285 keyboard. The one I'm currently at has a key that's marked ``Alt'',
31286 which is the meta key on this keyboard. It's usually located somewhere
31287 to the left hand side of the keyboard, usually on the bottom row.
31289 Now, us Emacs people don't say ``press the meta-control-m key'',
31290 because that's just too inconvenient. We say ``press the @kbd{C-M-m}
31291 key''. @kbd{M-} is the prefix that means ``meta'' and ``C-'' is the
31292 prefix that means ``control''. So ``press @kbd{C-k}'' means ``press
31293 down the control key, and hold it down while you press @kbd{k}''.
31294 ``Press @kbd{C-M-k}'' means ``press down and hold down the meta key and
31295 the control key and then press @kbd{k}''. Simple, ay?
31297 This is somewhat complicated by the fact that not all keyboards have a
31298 meta key. In that case you can use the ``escape'' key. Then @kbd{M-k}
31299 means ``press escape, release escape, press @kbd{k}''. That's much more
31300 work than if you have a meta key, so if that's the case, I respectfully
31301 suggest you get a real keyboard with a meta key. You can't live without
31307 @subsection Emacs Lisp
31309 Emacs is the King of Editors because it's really a Lisp interpreter.
31310 Each and every key you tap runs some Emacs Lisp code snippet, and since
31311 Emacs Lisp is an interpreted language, that means that you can configure
31312 any key to run any arbitrary code. You just, like, do it.
31314 Gnus is written in Emacs Lisp, and is run as a bunch of interpreted
31315 functions. (These are byte-compiled for speed, but it's still
31316 interpreted.) If you decide that you don't like the way Gnus does
31317 certain things, it's trivial to have it do something a different way.
31318 (Well, at least if you know how to write Lisp code.) However, that's
31319 beyond the scope of this manual, so we are simply going to talk about
31320 some common constructs that you normally use in your @file{~/.gnus.el}
31321 file to customize Gnus. (You can also use the @file{~/.emacs} file, but
31322 in order to set things of Gnus up, it is much better to use the
31323 @file{~/.gnus.el} file, @xref{Startup Files}.)
31325 If you want to set the variable @code{gnus-florgbnize} to four (4), you
31326 write the following:
31329 (setq gnus-florgbnize 4)
31332 This function (really ``special form'') @code{setq} is the one that can
31333 set a variable to some value. This is really all you need to know. Now
31334 you can go and fill your @file{~/.gnus.el} file with lots of these to
31335 change how Gnus works.
31337 If you have put that thing in your @file{~/.gnus.el} file, it will be
31338 read and @code{eval}ed (which is Lisp-ese for ``run'') the next time you
31339 start Gnus. If you want to change the variable right away, simply say
31340 @kbd{C-x C-e} after the closing parenthesis. That will @code{eval} the
31341 previous ``form'', which is a simple @code{setq} statement here.
31343 Go ahead---just try it, if you're located at your Emacs. After you
31344 @kbd{C-x C-e}, you will see @samp{4} appear in the echo area, which
31345 is the return value of the form you @code{eval}ed.
31349 If the manual says ``set @code{gnus-read-active-file} to @code{some}'',
31353 (setq gnus-read-active-file 'some)
31356 On the other hand, if the manual says ``set @code{gnus-nntp-server} to
31357 @samp{nntp.ifi.uio.no}'', that means:
31360 (setq gnus-nntp-server "nntp.ifi.uio.no")
31363 So be careful not to mix up strings (the latter) with symbols (the
31364 former). The manual is unambiguous, but it can be confusing.
31367 @include gnus-faq.texi
31369 @node GNU Free Documentation License
31370 @chapter GNU Free Documentation License
31371 @include doclicense.texi
31389 @c Local Variables:
31391 @c coding: iso-8859-1
31395 arch-tag: c9fa47e7-78ca-4681-bda9-9fef45d1c819