10 * Gnus: (gnus). The newsreader Gnus.
15 @setchapternewpage odd
19 \documentclass[twoside,a4paper,openright,11pt]{book}
20 \usepackage[latin1]{inputenc}
21 \usepackage{pagestyle}
24 \input{gnusconfig.tex}
26 \ifx\pdfoutput\undefined
28 \usepackage[pdftex,bookmarks,colorlinks=true]{hyperref}
36 \newcommand{\gnusversionname}{Oort Gnus v0.17}
37 \newcommand{\gnuschaptername}{}
38 \newcommand{\gnussectionname}{}
40 \newcommand{\gnusbackslash}{/}
42 \newcommand{\gnusref}[1]{``#1'' on page \pageref{#1}}
43 \ifx\pdfoutput\undefined
44 \newcommand{\gnusuref}[1]{\gnustt{#1}}
46 \newcommand{\gnusuref}[1]{\href{#1}{\gnustt{#1}}}
48 \newcommand{\gnusxref}[1]{See ``#1'' on page \pageref{#1}}
49 \newcommand{\gnuspxref}[1]{see ``#1'' on page \pageref{#1}}
51 \newcommand{\gnuskindex}[1]{\index{#1}}
52 \newcommand{\gnusindex}[1]{\index{#1}}
54 \newcommand{\gnustt}[1]{{\gnusselectttfont{}#1}}
55 \newcommand{\gnuscode}[1]{\gnustt{#1}}
56 \newcommand{\gnussamp}[1]{``{\fontencoding{OT1}\gnusselectttfont{}#1}''}
57 \newcommand{\gnuslisp}[1]{\gnustt{#1}}
58 \newcommand{\gnuskbd}[1]{`\gnustt{#1}'}
59 \newcommand{\gnuskey}[1]{`\gnustt{#1}'}
60 \newcommand{\gnusfile}[1]{`\gnustt{#1}'}
61 \newcommand{\gnusdfn}[1]{\textit{#1}}
62 \newcommand{\gnusi}[1]{\textit{#1}}
63 \newcommand{\gnusstrong}[1]{\textbf{#1}}
64 \newcommand{\gnusemph}[1]{\textit{#1}}
65 \newcommand{\gnusvar}[1]{{\fontsize{10pt}{10}\selectfont\textsl{\textsf{#1}}}}
66 \newcommand{\gnussc}[1]{\textsc{#1}}
67 \newcommand{\gnustitle}[1]{{\huge\textbf{#1}}}
68 \newcommand{\gnusversion}[1]{{\small\textit{#1}}}
69 \newcommand{\gnusauthor}[1]{{\large\textbf{#1}}}
70 \newcommand{\gnusresult}[1]{\gnustt{=> #1}}
71 \newcommand{\gnusacronym}[1]{\textit{#1}}
72 \newcommand{\gnusemail}[1]{\textit{#1}}
74 \newcommand{\gnusbullet}{{${\bullet}$}}
75 \newcommand{\gnusdollar}{\$}
76 \newcommand{\gnusampersand}{\&}
77 \newcommand{\gnuspercent}{\%}
78 \newcommand{\gnushash}{\#}
79 \newcommand{\gnushat}{\symbol{"5E}}
80 \newcommand{\gnusunderline}{\symbol{"5F}}
81 \newcommand{\gnusnot}{$\neg$}
82 \newcommand{\gnustilde}{\symbol{"7E}}
83 \newcommand{\gnusless}{{$<$}}
84 \newcommand{\gnusgreater}{{$>$}}
85 \newcommand{\gnusbraceleft}{{$>$}}
86 \newcommand{\gnusbraceright}{{$>$}}
88 \newcommand{\gnushead}{\raisebox{-1cm}{\epsfig{figure=ps/gnus-head,height=1cm}}}
89 \newcommand{\gnusinteresting}{
90 \marginpar[\mbox{}\hfill\gnushead]{\gnushead}
93 \newcommand{\gnuscleardoublepage}{\ifodd\count0\mbox{}\clearpage\thispagestyle{empty}\mbox{}\clearpage\else\clearpage\fi}
95 \newcommand{\gnuspagechapter}[1]{
102 \newcommand{\gnuschapter}[2]{
104 \ifdim \gnusdimen = 0pt\setcounter{page}{1}\pagestyle{gnus}\pagenumbering{arabic} \gnusdimen 1pt\fi
106 \renewcommand{\gnussectionname}{}
107 \renewcommand{\gnuschaptername}{#2}
108 \thispagestyle{empty}
110 \begin{picture}(500,500)(0,0)
111 \put(480,350){\makebox(0,0)[tr]{#1}}
112 \put(40,300){\makebox(500,50)[bl]{{\Huge\bf{#2}}}}
117 \newcommand{\gnusfigure}[3]{
119 \mbox{}\ifodd\count0\hspace*{-0.8cm}\else\hspace*{-3cm}\fi\begin{picture}(440,#2)
126 \newcommand{\gnusicon}[1]{
127 \marginpar[\mbox{}\hfill\raisebox{-1.5cm}{\epsfig{figure=ps/#1-up,height=1.5cm}}]{\raisebox{-1cm}{\epsfig{figure=ps/#1-up,height=1cm}}}
130 \newcommand{\gnuspicon}[1]{
131 \margindex{\epsfig{figure=#1,width=2cm}}
134 \newcommand{\gnusxface}[2]{
135 \margindex{\epsfig{figure=#1,width=1cm}\epsfig{figure=#2,width=1cm}}
138 \newcommand{\gnussmiley}[2]{
139 \margindex{\makebox[2cm]{\hfill\epsfig{figure=#1,width=0.5cm}\hfill\epsfig{figure=#2,width=0.5cm}\hfill}}
142 \newcommand{\gnusitemx}[1]{\mbox{}\vspace*{-\itemsep}\vspace*{-\parsep}\item#1}
144 \newcommand{\gnussection}[1]{
145 \renewcommand{\gnussectionname}{#1}
149 \newenvironment{codelist}%
154 \newenvironment{kbdlist}%
160 \newenvironment{dfnlist}%
165 \newenvironment{stronglist}%
170 \newenvironment{samplist}%
175 \newenvironment{varlist}%
180 \newenvironment{emphlist}%
185 \newlength\gnusheadtextwidth
186 \setlength{\gnusheadtextwidth}{\headtextwidth}
187 \addtolength{\gnusheadtextwidth}{1cm}
189 \newpagestyle{gnuspreamble}%
194 \hspace*{-0.23cm}\underline{\makebox[\gnusheadtextwidth]{\mbox{}}\textbf{\hfill\roman{page}}}
198 \hspace*{-3.25cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\roman{page}\hfill\mbox{}}}
207 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
209 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
214 \newpagestyle{gnusindex}%
219 \hspace*{-0.23cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\gnuschaptername\hfill\arabic{page}}}}
223 \hspace*{-3.25cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{page}\hfill\gnuschaptername}}}
231 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
233 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
243 \makebox[12cm]{\hspace*{3.1cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{chapter}.\arabic{section}} \textbf{\gnussectionname\hfill\arabic{page}}}}}
247 \makebox[12cm]{\hspace*{-2.95cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{page}\hfill\gnuschaptername}}}}
255 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
257 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
262 \pagenumbering{roman}
263 \pagestyle{gnuspreamble}
273 %\addtolength{\oddsidemargin}{-5cm}
274 %\addtolength{\evensidemargin}{-5cm}
276 \addtolength{\textheight}{2cm}
278 \gnustitle{\gnustitlename}\hfill\gnusversion{\gnusversionname}\\
281 \hspace*{0cm}\epsfig{figure=ps/gnus-big-logo,height=15cm}
284 \gnusauthor{by Lars Magne Ingebrigtsen}
291 \thispagestyle{empty}
293 Copyright \copyright{} 1995, 1996, 1997, 1998, 1999, 2000, 2001,
295 Free Software Foundation, Inc.
298 Permission is granted to copy, distribute and/or modify this document
299 under the terms of the GNU Free Documentation License, Version 1.1 or
300 any later version published by the Free Software Foundation; with no
301 Invariant Sections, with the Front-Cover texts being ``A GNU
302 Manual'', and with the Back-Cover Texts as in (a) below. A copy of the
303 license is included in the section entitled ``GNU Free Documentation
304 License'' in the Emacs manual.
306 (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
307 this GNU Manual, like GNU software. Copies published by the Free
308 Software Foundation raise funds for GNU development.''
310 This document is part of a collection distributed under the GNU Free
311 Documentation License. If you want to distribute this document
312 separately from the collection, you can do so by adding a copy of the
313 license to the document, as described in section 6 of the license.
321 This file documents Gnus, the GNU Emacs newsreader.
323 Copyright (C) 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003
324 Free Software Foundation, Inc.
326 Permission is granted to copy, distribute and/or modify this document
327 under the terms of the GNU Free Documentation License, Version 1.1 or
328 any later version published by the Free Software Foundation; with the
329 Invariant Sections being none, with the Front-Cover texts being ``A GNU
330 Manual'', and with the Back-Cover Texts as in (a) below. A copy of the
331 license is included in the section entitled ``GNU Free Documentation
332 License'' in the Emacs manual.
334 (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
335 this GNU Manual, like GNU software. Copies published by the Free
336 Software Foundation raise funds for GNU development.''
338 This document is part of a collection distributed under the GNU Free
339 Documentation License. If you want to distribute this document
340 separately from the collection, you can do so by adding a copy of the
341 license to the document, as described in section 6 of the license.
349 @author by Lars Magne Ingebrigtsen
352 @vskip 0pt plus 1filll
353 Copyright @copyright{} 1995, 1996, 1997, 1998, 1999, 2000, 2001,
355 Free Software Foundation, Inc.
357 Permission is granted to copy, distribute and/or modify this document
358 under the terms of the GNU Free Documentation License, Version 1.1 or
359 any later version published by the Free Software Foundation; with no
360 Invariant Sections, with the Front-Cover texts being ``A GNU
361 Manual'', and with the Back-Cover Texts as in (a) below. A copy of the
362 license is included in the section entitled ``GNU Free Documentation
363 License'' in the Emacs manual.
365 (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
366 this GNU Manual, like GNU software. Copies published by the Free
367 Software Foundation raise funds for GNU development.''
369 This document is part of a collection distributed under the GNU Free
370 Documentation License. If you want to distribute this document
371 separately from the collection, you can do so by adding a copy of the
372 license to the document, as described in section 6 of the license.
381 @top The Gnus Newsreader
385 You can read news (and mail) from within Emacs by using Gnus. The news
386 can be gotten by any nefarious means you can think of---@sc{nntp}, local
387 spool or your mbox file. All at the same time, if you want to push your
390 This manual corresponds to Oort Gnus v0.17.
401 Gnus is the advanced, self-documenting, customizable, extensible
402 unreal-time newsreader for GNU Emacs.
404 Oops. That sounds oddly familiar, so let's start over again to avoid
405 being accused of plagiarism:
407 Gnus is a message-reading laboratory. It will let you look at just
408 about anything as if it were a newsgroup. You can read mail with it,
409 you can browse directories with it, you can @code{ftp} with it---you
410 can even read news with it!
412 Gnus tries to empower people who read news the same way Emacs empowers
413 people who edit text. Gnus sets no limits to what the user should be
414 allowed to do. Users are encouraged to extend Gnus to make it behave
415 like they want it to behave. A program should not control people;
416 people should be empowered to do what they want by using (or abusing)
422 * Starting Up:: Finding news can be a pain.
423 * Group Buffer:: Selecting, subscribing and killing groups.
424 * Summary Buffer:: Reading, saving and posting articles.
425 * Article Buffer:: Displaying and handling articles.
426 * Composing Messages:: Information on sending mail and news.
427 * Select Methods:: Gnus reads all messages from various select methods.
428 * Scoring:: Assigning values to articles.
429 * Various:: General purpose settings.
430 * The End:: Farewell and goodbye.
431 * Appendices:: Terminology, Emacs intro, FAQ, History, Internals.
432 * Index:: Variable, function and concept index.
433 * Key Index:: Key Index.
435 Other related manuals
437 * Message:(message). Composing messages.
438 * Emacs-MIME:(emacs-mime). Composing messages; MIME-specific parts.
439 * Sieve:(sieve). Managing Sieve scripts in Emacs.
440 * PGG:(pgg). PGP/MIME with Gnus.
443 --- The Detailed Node Listing ---
447 * Finding the News:: Choosing a method for getting news.
448 * The First Time:: What does Gnus do the first time you start it?
449 * The Server is Down:: How can I read my mail then?
450 * Slave Gnusae:: You can have more than one Gnus active at a time.
451 * Fetching a Group:: Starting Gnus just to read a group.
452 * New Groups:: What is Gnus supposed to do with new groups?
453 * Changing Servers:: You may want to move from one server to another.
454 * Startup Files:: Those pesky startup files---@file{.newsrc}.
455 * Auto Save:: Recovering from a crash.
456 * The Active File:: Reading the active file over a slow line Takes Time.
457 * Startup Variables:: Other variables you might change.
461 * Checking New Groups:: Determining what groups are new.
462 * Subscription Methods:: What Gnus should do with new groups.
463 * Filtering New Groups:: Making Gnus ignore certain new groups.
467 * Group Buffer Format:: Information listed and how you can change it.
468 * Group Maneuvering:: Commands for moving in the group buffer.
469 * Selecting a Group:: Actually reading news.
470 * Subscription Commands:: Unsubscribing, killing, subscribing.
471 * Group Data:: Changing the info for a group.
472 * Group Levels:: Levels? What are those, then?
473 * Group Score:: A mechanism for finding out what groups you like.
474 * Marking Groups:: You can mark groups for later processing.
475 * Foreign Groups:: Creating and editing groups.
476 * Group Parameters:: Each group may have different parameters set.
477 * Listing Groups:: Gnus can list various subsets of the groups.
478 * Sorting Groups:: Re-arrange the group order.
479 * Group Maintenance:: Maintaining a tidy @file{.newsrc} file.
480 * Browse Foreign Server:: You can browse a server. See what it has to offer.
481 * Exiting Gnus:: Stop reading news and get some work done.
482 * Group Topics:: A folding group mode divided into topics.
483 * Misc Group Stuff:: Other stuff that you can to do.
487 * Group Line Specification:: Deciding how the group buffer is to look.
488 * Group Modeline Specification:: The group buffer modeline.
489 * Group Highlighting:: Having nice colors in the group buffer.
493 * Topic Commands:: Interactive E-Z commands.
494 * Topic Variables:: How to customize the topics the Lisp Way.
495 * Topic Sorting:: Sorting each topic individually.
496 * Topic Topology:: A map of the world.
497 * Topic Parameters:: Parameters that apply to all groups in a topic.
501 * Scanning New Messages:: Asking Gnus to see whether new messages have arrived.
502 * Group Information:: Information and help on groups and Gnus.
503 * Group Timestamp:: Making Gnus keep track of when you last read a group.
504 * File Commands:: Reading and writing the Gnus files.
505 * Sieve Commands:: Managing Sieve scripts.
509 * Summary Buffer Format:: Deciding how the summary buffer is to look.
510 * Summary Maneuvering:: Moving around the summary buffer.
511 * Choosing Articles:: Reading articles.
512 * Paging the Article:: Scrolling the current article.
513 * Reply Followup and Post:: Posting articles.
514 * Delayed Articles:: Send articles at a later time.
515 * Marking Articles:: Marking articles as read, expirable, etc.
516 * Limiting:: You can limit the summary buffer.
517 * Threading:: How threads are made.
518 * Sorting the Summary Buffer:: How articles and threads are sorted.
519 * Asynchronous Fetching:: Gnus might be able to pre-fetch articles.
520 * Article Caching:: You may store articles in a cache.
521 * Persistent Articles:: Making articles expiry-resistant.
522 * Article Backlog:: Having already read articles hang around.
523 * Saving Articles:: Ways of customizing article saving.
524 * Decoding Articles:: Gnus can treat series of (uu)encoded articles.
525 * Article Treatment:: The article buffer can be mangled at will.
526 * MIME Commands:: Doing MIMEy things with the articles.
527 * Charsets:: Character set issues.
528 * Article Commands:: Doing various things with the article buffer.
529 * Summary Sorting:: Sorting the summary buffer in various ways.
530 * Finding the Parent:: No child support? Get the parent.
531 * Alternative Approaches:: Reading using non-default summaries.
532 * Tree Display:: A more visual display of threads.
533 * Mail Group Commands:: Some commands can only be used in mail groups.
534 * Various Summary Stuff:: What didn't fit anywhere else.
535 * Exiting the Summary Buffer:: Returning to the Group buffer,
536 or reselecting the current group.
537 * Crosspost Handling:: How crossposted articles are dealt with.
538 * Duplicate Suppression:: An alternative when crosspost handling fails.
539 * Security:: Decrypt and Verify.
540 * Mailing List:: Mailing list minor mode.
542 Summary Buffer Format
544 * Summary Buffer Lines:: You can specify how summary lines should look.
545 * To From Newsgroups:: How to not display your own name.
546 * Summary Buffer Mode Line:: You can say how the mode line should look.
547 * Summary Highlighting:: Making the summary buffer all pretty and nice.
551 * Choosing Commands:: Commands for choosing articles.
552 * Choosing Variables:: Variables that influence these commands.
554 Reply, Followup and Post
556 * Summary Mail Commands:: Sending mail.
557 * Summary Post Commands:: Sending news.
558 * Summary Message Commands:: Other Message-related commands.
559 * Canceling and Superseding::
563 * Unread Articles:: Marks for unread articles.
564 * Read Articles:: Marks for read articles.
565 * Other Marks:: Marks that do not affect readedness.
567 * Generic Marking Commands::
568 * Setting Process Marks::
572 * Setting Marks:: How to set and remove marks.
573 * Generic Marking Commands:: How to customize the marking.
574 * Setting Process Marks:: How to mark articles for later processing.
578 * Customizing Threading:: Variables you can change to affect the threading.
579 * Thread Commands:: Thread based commands in the summary buffer.
581 Customizing Threading
583 * Loose Threads:: How Gnus gathers loose threads into bigger threads.
584 * Filling In Threads:: Making the threads displayed look fuller.
585 * More Threading:: Even more variables for fiddling with threads.
586 * Low-Level Threading:: You thought it was over@dots{} but you were wrong!
590 * Uuencoded Articles:: Uudecode articles.
591 * Shell Archives:: Unshar articles.
592 * PostScript Files:: Split PostScript.
593 * Other Files:: Plain save and binhex.
594 * Decoding Variables:: Variables for a happy decoding.
595 * Viewing Files:: You want to look at the result of the decoding?
599 * Rule Variables:: Variables that say how a file is to be viewed.
600 * Other Decode Variables:: Other decode variables.
601 * Uuencoding and Posting:: Variables for customizing uuencoding.
605 * Article Highlighting:: You want to make the article look like fruit salad.
606 * Article Fontisizing:: Making emphasized text look nice.
607 * Article Hiding:: You also want to make certain info go away.
608 * Article Washing:: Lots of way-neat functions to make life better.
609 * Article Header:: Doing various header transformations.
610 * Article Buttons:: Click on URLs, Message-IDs, addresses and the like.
611 * Article Button Levels:: Controlling appearance of buttons.
612 * Article Date:: Grumble, UT!
613 * Article Display:: Display various stuff---X-Face, Picons, Smileys
614 * Article Signature:: What is a signature?
615 * Article Miscellania:: Various other stuff.
617 Alternative Approaches
619 * Pick and Read:: First mark articles and then read them.
620 * Binary Groups:: Auto-decode all articles.
622 Various Summary Stuff
624 * Summary Group Information:: Information oriented commands.
625 * Searching for Articles:: Multiple article commands.
626 * Summary Generation Commands::
627 * Really Various Summary Commands:: Those pesky non-conformant commands.
631 * Hiding Headers:: Deciding what headers should be displayed.
632 * Using MIME:: Pushing articles through @sc{mime} before reading them.
633 * Customizing Articles:: Tailoring the look of the articles.
634 * Article Keymap:: Keystrokes available in the article buffer.
635 * Misc Article:: Other stuff.
639 * Mail:: Mailing and replying.
640 * Posting Server:: What server should you post and mail via?
641 * Mail and Post:: Mailing and posting at the same time.
642 * Archived Messages:: Where Gnus stores the messages you've sent.
643 * Posting Styles:: An easier way to specify who you are.
644 * Drafts:: Postponing messages and rejected messages.
645 * Rejected Articles:: What happens if the server doesn't like your article?
646 * Signing and encrypting:: How to compose secure messages.
650 * Server Buffer:: Making and editing virtual servers.
651 * Getting News:: Reading USENET news with Gnus.
652 * Getting Mail:: Reading your personal mail with Gnus.
653 * Browsing the Web:: Getting messages from a plethora of Web sources.
654 * IMAP:: Using Gnus as a @sc{imap} client.
655 * Other Sources:: Reading directories, files, SOUP packets.
656 * Combined Groups:: Combining groups into one group.
657 * Gnus Unplugged:: Reading news and mail offline.
661 * Server Buffer Format:: You can customize the look of this buffer.
662 * Server Commands:: Commands to manipulate servers.
663 * Example Methods:: Examples server specifications.
664 * Creating a Virtual Server:: An example session.
665 * Server Variables:: Which variables to set.
666 * Servers and Methods:: You can use server names as select methods.
667 * Unavailable Servers:: Some servers you try to contact may be down.
671 * NNTP:: Reading news from an @sc{nntp} server.
672 * News Spool:: Reading news from the local spool.
676 * Direct Functions:: Connecting directly to the server.
677 * Indirect Functions:: Connecting indirectly to the server.
678 * Common Variables:: Understood by several connection functions.
682 * Mail in a Newsreader:: Important introductory notes.
683 * Getting Started Reading Mail:: A simple cookbook example.
684 * Splitting Mail:: How to create mail groups.
685 * Mail Sources:: How to tell Gnus where to get mail from.
686 * Mail Back End Variables:: Variables for customizing mail handling.
687 * Fancy Mail Splitting:: Gnus can do hairy splitting of incoming mail.
688 * Group Mail Splitting:: Use group customize to drive mail splitting.
689 * Incorporating Old Mail:: What about the old mail you have?
690 * Expiring Mail:: Getting rid of unwanted mail.
691 * Washing Mail:: Removing gruft from the mail you get.
692 * Duplicates:: Dealing with duplicated mail.
693 * Not Reading Mail:: Using mail back ends for reading other files.
694 * Choosing a Mail Back End:: Gnus can read a variety of mail formats.
698 * Mail Source Specifiers:: How to specify what a mail source is.
699 * Mail Source Customization:: Some variables that influence things.
700 * Fetching Mail:: Using the mail source specifiers.
702 Choosing a Mail Back End
704 * Unix Mail Box:: Using the (quite) standard Un*x mbox.
705 * Rmail Babyl:: Emacs programs use the rmail babyl format.
706 * Mail Spool:: Store your mail in a private spool?
707 * MH Spool:: An mhspool-like back end.
708 * Maildir:: Another one-file-per-message format.
709 * Mail Folders:: Having one file for each group.
710 * Comparing Mail Back Ends:: An in-depth looks at pros and cons.
715 * Web Searches:: Creating groups from articles that match a string.
716 * Slashdot:: Reading the Slashdot comments.
717 * Ultimate:: The Ultimate Bulletin Board systems.
718 * Web Archive:: Reading mailing list archived on web.
719 * RSS:: Reading RDF site summary.
720 * Customizing w3:: Doing stuff to Emacs/w3 from Gnus.
724 * Splitting in IMAP:: Splitting mail with nnimap.
725 * Expiring in IMAP:: Expiring mail with nnimap.
726 * Editing IMAP ACLs:: Limiting/enabling other users access to a mailbox.
727 * Expunging mailboxes:: Equivalent of a ``compress mailbox'' button.
728 * A note on namespaces:: How to (not) use IMAP namespace in Gnus.
732 * Directory Groups:: You can read a directory as if it was a newsgroup.
733 * Anything Groups:: Dired? Who needs dired?
734 * Document Groups:: Single files can be the basis of a group.
735 * SOUP:: Reading @sc{soup} packets ``offline''.
736 * Mail-To-News Gateways:: Posting articles via mail-to-news gateways.
740 * Document Server Internals:: How to add your own document types.
744 * SOUP Commands:: Commands for creating and sending @sc{soup} packets
745 * SOUP Groups:: A back end for reading @sc{soup} packets.
746 * SOUP Replies:: How to enable @code{nnsoup} to take over mail and news.
750 * Virtual Groups:: Combining articles from many groups.
751 * Kibozed Groups:: Looking through parts of the newsfeed for articles.
755 * Agent Basics:: How it all is supposed to work.
756 * Agent Categories:: How to tell the Gnus Agent what to download.
757 * Agent Commands:: New commands for all the buffers.
758 * Agent as Cache:: The Agent is a big cache too.
759 * Agent Expiry:: How to make old articles go away.
760 * Agent Regeneration:: How to recover from lost connections and other accidents.
761 * Agent and IMAP:: How to use the Agent with IMAP.
762 * Outgoing Messages:: What happens when you post/mail something?
763 * Agent Variables:: Customizing is fun.
764 * Example Setup:: An example @file{~/.gnus.el} file for offline people.
765 * Batching Agents:: How to fetch news from a @code{cron} job.
766 * Agent Caveats:: What you think it'll do and what it does.
770 * Category Syntax:: What a category looks like.
771 * Category Buffer:: A buffer for maintaining categories.
772 * Category Variables:: Customize'r'Us.
776 * Group Agent Commands:: Configure groups and fetch their contents.
777 * Summary Agent Commands:: Manually select then fetch specific articles.
778 * Server Agent Commands:: Select the servers that are supported by the agent.
782 * Summary Score Commands:: Adding score entries for the current group.
783 * Group Score Commands:: General score commands.
784 * Score Variables:: Customize your scoring. (My, what terminology).
785 * Score File Format:: What a score file may contain.
786 * Score File Editing:: You can edit score files by hand as well.
787 * Adaptive Scoring:: Big Sister Gnus knows what you read.
788 * Home Score File:: How to say where new score entries are to go.
789 * Followups To Yourself:: Having Gnus notice when people answer you.
790 * Scoring On Other Headers:: Scoring on non-standard headers.
791 * Scoring Tips:: How to score effectively.
792 * Reverse Scoring:: That problem child of old is not problem.
793 * Global Score Files:: Earth-spanning, ear-splitting score files.
794 * Kill Files:: They are still here, but they can be ignored.
795 * Converting Kill Files:: Translating kill files to score files.
796 * GroupLens:: Getting predictions on what you like to read.
797 * Advanced Scoring:: Using logical expressions to build score rules.
798 * Score Decays:: It can be useful to let scores wither away.
802 * Using GroupLens:: How to make Gnus use GroupLens.
803 * Rating Articles:: Letting GroupLens know how you rate articles.
804 * Displaying Predictions:: Displaying predictions given by GroupLens.
805 * GroupLens Variables:: Customizing GroupLens.
809 * Advanced Scoring Syntax:: A definition.
810 * Advanced Scoring Examples:: What they look like.
811 * Advanced Scoring Tips:: Getting the most out of it.
815 * Process/Prefix:: A convention used by many treatment commands.
816 * Interactive:: Making Gnus ask you many questions.
817 * Symbolic Prefixes:: How to supply some Gnus functions with options.
818 * Formatting Variables:: You can specify what buffers should look like.
819 * Window Layout:: Configuring the Gnus buffer windows.
820 * Faces and Fonts:: How to change how faces look.
821 * Compilation:: How to speed Gnus up.
822 * Mode Lines:: Displaying information in the mode lines.
823 * Highlighting and Menus:: Making buffers look all nice and cozy.
824 * Buttons:: Get tendinitis in ten easy steps!
825 * Daemons:: Gnus can do things behind your back.
826 * NoCeM:: How to avoid spam and other fatty foods.
827 * Undo:: Some actions can be undone.
828 * Predicate Specifiers:: Specifying predicates.
829 * Moderation:: What to do if you're a moderator.
830 * Image Enhancements:: Modern versions of Emacs/XEmacs can display images.
831 * Fuzzy Matching:: What's the big fuzz?
832 * Thwarting Email Spam:: A how-to on avoiding unsolicited commercial email.
833 * Various Various:: Things that are really various.
837 * Formatting Basics:: A formatting variable is basically a format string.
838 * Mode Line Formatting:: Some rules about mode line formatting variables.
839 * Advanced Formatting:: Modifying output in various ways.
840 * User-Defined Specs:: Having Gnus call your own functions.
841 * Formatting Fonts:: Making the formatting look colorful and nice.
842 * Positioning Point:: Moving point to a position after an operation.
843 * Tabulation:: Tabulating your output.
844 * Wide Characters:: Dealing with wide characters.
848 * Picons:: How to display pictures of what you're reading.
849 * Smileys:: Show all those happy faces the way they were meant to be shown.
850 * X-Face:: Display a funky, teensy black-and-white image.
851 * XVarious:: Other XEmacsy Gnusey variables.
855 * The problem of spam:: Some background, and some solutions
856 * Anti-Spam Basics:: Simple steps to reduce the amount of spam.
857 * SpamAssassin:: How to use external anti-spam tools.
858 * Hashcash:: Reduce spam by burning CPU time.
859 * Filtering Spam Using The Spam ELisp Package::
860 * Filtering Spam Using Statistics with spam-stat::
864 * XEmacs:: Requirements for installing under XEmacs.
865 * History:: How Gnus got where it is today.
866 * On Writing Manuals:: Why this is not a beginner's guide.
867 * Terminology:: We use really difficult, like, words here.
868 * Customization:: Tailoring Gnus to your needs.
869 * Troubleshooting:: What you might try if things do not work.
870 * Gnus Reference Guide:: Rilly, rilly technical stuff.
871 * Emacs for Heathens:: A short introduction to Emacsian terms.
872 * Frequently Asked Questions::
876 * Gnus Versions:: What Gnus versions have been released.
877 * Other Gnus Versions:: Other Gnus versions that also have been released.
878 * Why?:: What's the point of Gnus?
879 * Compatibility:: Just how compatible is Gnus with @sc{gnus}?
880 * Conformity:: Gnus tries to conform to all standards.
881 * Emacsen:: Gnus can be run on a few modern Emacsen.
882 * Gnus Development:: How Gnus is developed.
883 * Contributors:: Oodles of people.
884 * New Features:: Pointers to some of the new stuff in Gnus.
888 * ding Gnus:: New things in Gnus 5.0/5.1, the first new Gnus.
889 * September Gnus:: The Thing Formally Known As Gnus 5.2/5.3.
890 * Red Gnus:: Third time best---Gnus 5.4/5.5.
891 * Quassia Gnus:: Two times two is four, or Gnus 5.6/5.7.
892 * Pterodactyl Gnus:: Pentad also starts with P, AKA Gnus 5.8/5.9.
896 * Slow/Expensive Connection:: You run a local Emacs and get the news elsewhere.
897 * Slow Terminal Connection:: You run a remote Emacs.
898 * Little Disk Space:: You feel that having large setup files is icky.
899 * Slow Machine:: You feel like buying a faster machine.
903 * Gnus Utility Functions:: Common functions and variable to use.
904 * Back End Interface:: How Gnus communicates with the servers.
905 * Score File Syntax:: A BNF definition of the score file standard.
906 * Headers:: How Gnus stores headers internally.
907 * Ranges:: A handy format for storing mucho numbers.
908 * Group Info:: The group info format.
909 * Extended Interactive:: Symbolic prefixes and stuff.
910 * Emacs/XEmacs Code:: Gnus can be run under all modern Emacsen.
911 * Various File Formats:: Formats of files that Gnus use.
915 * Required Back End Functions:: Functions that must be implemented.
916 * Optional Back End Functions:: Functions that need not be implemented.
917 * Error Messaging:: How to get messages and report errors.
918 * Writing New Back Ends:: Extending old back ends.
919 * Hooking New Back Ends Into Gnus:: What has to be done on the Gnus end.
920 * Mail-like Back Ends:: Some tips on mail back ends.
924 * Active File Format:: Information on articles and groups available.
925 * Newsgroups File Format:: Group descriptions.
929 * Keystrokes:: Entering text and executing commands.
930 * Emacs Lisp:: The built-in Emacs programming language.
936 @chapter Starting Gnus
941 If your system administrator has set things up properly, starting Gnus
942 and reading news is extremely easy---you just type @kbd{M-x gnus} in
945 @findex gnus-other-frame
946 @kindex M-x gnus-other-frame
947 If you want to start Gnus in a different frame, you can use the command
948 @kbd{M-x gnus-other-frame} instead.
950 If things do not go smoothly at startup, you have to twiddle some
951 variables in your @file{~/.gnus.el} file. This file is similar to
952 @file{~/.emacs}, but is read when gnus starts.
954 If you puzzle at any terms used in this manual, please refer to the
955 terminology section (@pxref{Terminology}).
958 * Finding the News:: Choosing a method for getting news.
959 * The First Time:: What does Gnus do the first time you start it?
960 * The Server is Down:: How can I read my mail then?
961 * Slave Gnusae:: You can have more than one Gnus active at a time.
962 * Fetching a Group:: Starting Gnus just to read a group.
963 * New Groups:: What is Gnus supposed to do with new groups?
964 * Changing Servers:: You may want to move from one server to another.
965 * Startup Files:: Those pesky startup files---@file{.newsrc}.
966 * Auto Save:: Recovering from a crash.
967 * The Active File:: Reading the active file over a slow line Takes Time.
968 * Startup Variables:: Other variables you might change.
972 @node Finding the News
973 @section Finding the News
976 @vindex gnus-select-method
978 The @code{gnus-select-method} variable says where Gnus should look for
979 news. This variable should be a list where the first element says
980 @dfn{how} and the second element says @dfn{where}. This method is your
981 native method. All groups not fetched with this method are
984 For instance, if the @samp{news.somewhere.edu} @sc{nntp} server is where
985 you want to get your daily dosage of news from, you'd say:
988 (setq gnus-select-method '(nntp "news.somewhere.edu"))
991 If you want to read directly from the local spool, say:
994 (setq gnus-select-method '(nnspool ""))
997 If you can use a local spool, you probably should, as it will almost
998 certainly be much faster. But do not use the local spool if your
999 server is running Leafnode; in this case, use @code{(nntp "localhost")}.
1001 @vindex gnus-nntpserver-file
1003 @cindex @sc{nntp} server
1004 If this variable is not set, Gnus will take a look at the
1005 @code{NNTPSERVER} environment variable. If that variable isn't set,
1006 Gnus will see whether @code{gnus-nntpserver-file}
1007 (@file{/etc/nntpserver} by default) has any opinions on the matter. If
1008 that fails as well, Gnus will try to use the machine running Emacs as an @sc{nntp} server. That's a long shot, though.
1010 @vindex gnus-nntp-server
1011 If @code{gnus-nntp-server} is set, this variable will override
1012 @code{gnus-select-method}. You should therefore set
1013 @code{gnus-nntp-server} to @code{nil}, which is what it is by default.
1015 @vindex gnus-secondary-servers
1016 @vindex gnus-nntp-server
1017 You can also make Gnus prompt you interactively for the name of an
1018 @sc{nntp} server. If you give a non-numerical prefix to @code{gnus}
1019 (i.e., @kbd{C-u M-x gnus}), Gnus will let you choose between the servers
1020 in the @code{gnus-secondary-servers} list (if any). You can also just
1021 type in the name of any server you feel like visiting. (Note that this
1022 will set @code{gnus-nntp-server}, which means that if you then @kbd{M-x
1023 gnus} later in the same Emacs session, Gnus will contact the same
1026 @findex gnus-group-browse-foreign-server
1028 However, if you use one @sc{nntp} server regularly and are just
1029 interested in a couple of groups from a different server, you would be
1030 better served by using the @kbd{B} command in the group buffer. It will
1031 let you have a look at what groups are available, and you can subscribe
1032 to any of the groups you want to. This also makes @file{.newsrc}
1033 maintenance much tidier. @xref{Foreign Groups}.
1035 @vindex gnus-secondary-select-methods
1037 A slightly different approach to foreign groups is to set the
1038 @code{gnus-secondary-select-methods} variable. The select methods
1039 listed in this variable are in many ways just as native as the
1040 @code{gnus-select-method} server. They will also be queried for active
1041 files during startup (if that's required), and new newsgroups that
1042 appear on these servers will be subscribed (or not) just as native
1045 For instance, if you use the @code{nnmbox} back end to read your mail,
1046 you would typically set this variable to
1049 (setq gnus-secondary-select-methods '((nnmbox "")))
1053 @node The First Time
1054 @section The First Time
1055 @cindex first time usage
1057 If no startup files exist, Gnus will try to determine what groups should
1058 be subscribed by default.
1060 @vindex gnus-default-subscribed-newsgroups
1061 If the variable @code{gnus-default-subscribed-newsgroups} is set, Gnus
1062 will subscribe you to just those groups in that list, leaving the rest
1063 killed. Your system administrator should have set this variable to
1066 Since she hasn't, Gnus will just subscribe you to a few arbitrarily
1067 picked groups (i.e., @samp{*.newusers}). (@dfn{Arbitrary} is defined
1068 here as @dfn{whatever Lars thinks you should read}.)
1070 You'll also be subscribed to the Gnus documentation group, which should
1071 help you with most common problems.
1073 If @code{gnus-default-subscribed-newsgroups} is @code{t}, Gnus will just
1074 use the normal functions for handling new groups, and not do anything
1078 @node The Server is Down
1079 @section The Server is Down
1080 @cindex server errors
1082 If the default server is down, Gnus will understandably have some
1083 problems starting. However, if you have some mail groups in addition to
1084 the news groups, you may want to start Gnus anyway.
1086 Gnus, being the trusting sort of program, will ask whether to proceed
1087 without a native select method if that server can't be contacted. This
1088 will happen whether the server doesn't actually exist (i.e., you have
1089 given the wrong address) or the server has just momentarily taken ill
1090 for some reason or other. If you decide to continue and have no foreign
1091 groups, you'll find it difficult to actually do anything in the group
1092 buffer. But, hey, that's your problem. Blllrph!
1094 @findex gnus-no-server
1095 @kindex M-x gnus-no-server
1097 If you know that the server is definitely down, or you just want to read
1098 your mail without bothering with the server at all, you can use the
1099 @code{gnus-no-server} command to start Gnus. That might come in handy
1100 if you're in a hurry as well. This command will not attempt to contact
1101 your primary server---instead, it will just activate all groups on level
1102 1 and 2. (You should preferably keep no native groups on those two
1103 levels.) Also @pxref{Group Levels}.
1107 @section Slave Gnusae
1110 You might want to run more than one Emacs with more than one Gnus at the
1111 same time. If you are using different @file{.newsrc} files (e.g., if you
1112 are using the two different Gnusae to read from two different servers),
1113 that is no problem whatsoever. You just do it.
1115 The problem appears when you want to run two Gnusae that use the same
1116 @file{.newsrc} file.
1118 To work around that problem some, we here at the Think-Tank at the Gnus
1119 Towers have come up with a new concept: @dfn{Masters} and
1120 @dfn{slaves}. (We have applied for a patent on this concept, and have
1121 taken out a copyright on those words. If you wish to use those words in
1122 conjunction with each other, you have to send $1 per usage instance to
1123 me. Usage of the patent (@dfn{Master/Slave Relationships In Computer
1124 Applications}) will be much more expensive, of course.)
1127 Anyway, you start one Gnus up the normal way with @kbd{M-x gnus} (or
1128 however you do it). Each subsequent slave Gnusae should be started with
1129 @kbd{M-x gnus-slave}. These slaves won't save normal @file{.newsrc}
1130 files, but instead save @dfn{slave files} that contain information only
1131 on what groups have been read in the slave session. When a master Gnus
1132 starts, it will read (and delete) these slave files, incorporating all
1133 information from them. (The slave files will be read in the sequence
1134 they were created, so the latest changes will have precedence.)
1136 Information from the slave files has, of course, precedence over the
1137 information in the normal (i.e., master) @file{.newsrc} file.
1139 If the @file{.newsrc*} files have not been saved in the master when the
1140 slave starts, you may be prompted as to whether to read an auto-save
1141 file. If you answer ``yes'', the unsaved changes to the master will be
1142 incorporated into the slave. If you answer ``no'', the slave may see some
1143 messages as unread that have been read in the master.
1145 @node Fetching a Group
1146 @section Fetching a Group
1147 @cindex fetching a group
1149 @findex gnus-fetch-group
1150 It is sometimes convenient to be able to just say ``I want to read this
1151 group and I don't care whether Gnus has been started or not''. This is
1152 perhaps more useful for people who write code than for users, but the
1153 command @code{gnus-fetch-group} provides this functionality in any case.
1154 It takes the group name as a parameter.
1160 @cindex subscription
1162 @vindex gnus-check-new-newsgroups
1163 If you are satisfied that you really never want to see any new groups,
1164 you can set @code{gnus-check-new-newsgroups} to @code{nil}. This will
1165 also save you some time at startup. Even if this variable is
1166 @code{nil}, you can always subscribe to the new groups just by pressing
1167 @kbd{U} in the group buffer (@pxref{Group Maintenance}). This variable
1168 is @code{ask-server} by default. If you set this variable to
1169 @code{always}, then Gnus will query the back ends for new groups even
1170 when you do the @kbd{g} command (@pxref{Scanning New Messages}).
1173 * Checking New Groups:: Determining what groups are new.
1174 * Subscription Methods:: What Gnus should do with new groups.
1175 * Filtering New Groups:: Making Gnus ignore certain new groups.
1179 @node Checking New Groups
1180 @subsection Checking New Groups
1182 Gnus normally determines whether a group is new or not by comparing the
1183 list of groups from the active file(s) with the lists of subscribed and
1184 dead groups. This isn't a particularly fast method. If
1185 @code{gnus-check-new-newsgroups} is @code{ask-server}, Gnus will ask the
1186 server for new groups since the last time. This is both faster and
1187 cheaper. This also means that you can get rid of the list of killed
1188 groups altogether, so you may set @code{gnus-save-killed-list} to
1189 @code{nil}, which will save time both at startup, at exit, and all over.
1190 Saves disk space, too. Why isn't this the default, then?
1191 Unfortunately, not all servers support this command.
1193 I bet I know what you're thinking now: How do I find out whether my
1194 server supports @code{ask-server}? No? Good, because I don't have a
1195 fail-safe answer. I would suggest just setting this variable to
1196 @code{ask-server} and see whether any new groups appear within the next
1197 few days. If any do, then it works. If none do, then it doesn't
1198 work. I could write a function to make Gnus guess whether the server
1199 supports @code{ask-server}, but it would just be a guess. So I won't.
1200 You could @code{telnet} to the server and say @code{HELP} and see
1201 whether it lists @samp{NEWGROUPS} among the commands it understands. If
1202 it does, then it might work. (But there are servers that lists
1203 @samp{NEWGROUPS} without supporting the function properly.)
1205 This variable can also be a list of select methods. If so, Gnus will
1206 issue an @code{ask-server} command to each of the select methods, and
1207 subscribe them (or not) using the normal methods. This might be handy
1208 if you are monitoring a few servers for new groups. A side effect is
1209 that startup will take much longer, so you can meditate while waiting.
1210 Use the mantra ``dingnusdingnusdingnus'' to achieve permanent bliss.
1213 @node Subscription Methods
1214 @subsection Subscription Methods
1216 @vindex gnus-subscribe-newsgroup-method
1217 What Gnus does when it encounters a new group is determined by the
1218 @code{gnus-subscribe-newsgroup-method} variable.
1220 This variable should contain a function. This function will be called
1221 with the name of the new group as the only parameter.
1223 Some handy pre-fab functions are:
1227 @item gnus-subscribe-zombies
1228 @vindex gnus-subscribe-zombies
1229 Make all new groups zombies. This is the default. You can browse the
1230 zombies later (with @kbd{A z}) and either kill them all off properly
1231 (with @kbd{S z}), or subscribe to them (with @kbd{u}).
1233 @item gnus-subscribe-randomly
1234 @vindex gnus-subscribe-randomly
1235 Subscribe all new groups in arbitrary order. This really means that all
1236 new groups will be added at ``the top'' of the group buffer.
1238 @item gnus-subscribe-alphabetically
1239 @vindex gnus-subscribe-alphabetically
1240 Subscribe all new groups in alphabetical order.
1242 @item gnus-subscribe-hierarchically
1243 @vindex gnus-subscribe-hierarchically
1244 Subscribe all new groups hierarchically. The difference between this
1245 function and @code{gnus-subscribe-alphabetically} is slight.
1246 @code{gnus-subscribe-alphabetically} will subscribe new groups in a strictly
1247 alphabetical fashion, while this function will enter groups into its
1248 hierarchy. So if you want to have the @samp{rec} hierarchy before the
1249 @samp{comp} hierarchy, this function will not mess that configuration
1250 up. Or something like that.
1252 @item gnus-subscribe-interactively
1253 @vindex gnus-subscribe-interactively
1254 Subscribe new groups interactively. This means that Gnus will ask
1255 you about @strong{all} new groups. The groups you choose to subscribe
1256 to will be subscribed hierarchically.
1258 @item gnus-subscribe-killed
1259 @vindex gnus-subscribe-killed
1260 Kill all new groups.
1262 @item gnus-subscribe-topics
1263 @vindex gnus-subscribe-topics
1264 Put the groups into the topic that has a matching @code{subscribe} topic
1265 parameter (@pxref{Topic Parameters}). For instance, a @code{subscribe}
1266 topic parameter that looks like
1272 will mean that all groups that match that regex will be subscribed under
1275 If no topics match the groups, the groups will be subscribed in the
1280 @vindex gnus-subscribe-hierarchical-interactive
1281 A closely related variable is
1282 @code{gnus-subscribe-hierarchical-interactive}. (That's quite a
1283 mouthful.) If this variable is non-@code{nil}, Gnus will ask you in a
1284 hierarchical fashion whether to subscribe to new groups or not. Gnus
1285 will ask you for each sub-hierarchy whether you want to descend the
1288 One common mistake is to set the variable a few paragraphs above
1289 (@code{gnus-subscribe-newsgroup-method}) to
1290 @code{gnus-subscribe-hierarchical-interactive}. This is an error. This
1291 will not work. This is ga-ga. So don't do it.
1294 @node Filtering New Groups
1295 @subsection Filtering New Groups
1297 A nice and portable way to control which new newsgroups should be
1298 subscribed (or ignored) is to put an @dfn{options} line at the start of
1299 the @file{.newsrc} file. Here's an example:
1302 options -n !alt.all !rec.all sci.all
1305 @vindex gnus-subscribe-options-newsgroup-method
1306 This line obviously belongs to a serious-minded intellectual scientific
1307 person (or she may just be plain old boring), because it says that all
1308 groups that have names beginning with @samp{alt} and @samp{rec} should
1309 be ignored, and all groups with names beginning with @samp{sci} should
1310 be subscribed. Gnus will not use the normal subscription method for
1311 subscribing these groups.
1312 @code{gnus-subscribe-options-newsgroup-method} is used instead. This
1313 variable defaults to @code{gnus-subscribe-alphabetically}.
1315 @vindex gnus-options-not-subscribe
1316 @vindex gnus-options-subscribe
1317 If you don't want to mess with your @file{.newsrc} file, you can just
1318 set the two variables @code{gnus-options-subscribe} and
1319 @code{gnus-options-not-subscribe}. These two variables do exactly the
1320 same as the @file{.newsrc} @samp{options -n} trick. Both are regexps,
1321 and if the new group matches the former, it will be unconditionally
1322 subscribed, and if it matches the latter, it will be ignored.
1324 @vindex gnus-auto-subscribed-groups
1325 Yet another variable that meddles here is
1326 @code{gnus-auto-subscribed-groups}. It works exactly like
1327 @code{gnus-options-subscribe}, and is therefore really superfluous, but I
1328 thought it would be nice to have two of these. This variable is more
1329 meant for setting some ground rules, while the other variable is used
1330 more for user fiddling. By default this variable makes all new groups
1331 that come from mail back ends (@code{nnml}, @code{nnbabyl},
1332 @code{nnfolder}, @code{nnmbox}, @code{nnmh}, and @code{nnmaildir})
1333 subscribed. If you don't like that, just set this variable to
1336 New groups that match this regexp are subscribed using
1337 @code{gnus-subscribe-options-newsgroup-method}.
1340 @node Changing Servers
1341 @section Changing Servers
1342 @cindex changing servers
1344 Sometimes it is necessary to move from one @sc{nntp} server to another.
1345 This happens very rarely, but perhaps you change jobs, or one server is
1346 very flaky and you want to use another.
1348 Changing the server is pretty easy, right? You just change
1349 @code{gnus-select-method} to point to the new server?
1353 Article numbers are not (in any way) kept synchronized between different
1354 @sc{nntp} servers, and the only way Gnus keeps track of what articles
1355 you have read is by keeping track of article numbers. So when you
1356 change @code{gnus-select-method}, your @file{.newsrc} file becomes
1359 Gnus provides a few functions to attempt to translate a @file{.newsrc}
1360 file from one server to another. They all have one thing in
1361 common---they take a looong time to run. You don't want to use these
1362 functions more than absolutely necessary.
1364 @kindex M-x gnus-change-server
1365 @findex gnus-change-server
1366 If you have access to both servers, Gnus can request the headers for all
1367 the articles you have read and compare @code{Message-ID}s and map the
1368 article numbers of the read articles and article marks. The @kbd{M-x
1369 gnus-change-server} command will do this for all your native groups. It
1370 will prompt for the method you want to move to.
1372 @kindex M-x gnus-group-move-group-to-server
1373 @findex gnus-group-move-group-to-server
1374 You can also move individual groups with the @kbd{M-x
1375 gnus-group-move-group-to-server} command. This is useful if you want to
1376 move a (foreign) group from one server to another.
1378 @kindex M-x gnus-group-clear-data-on-native-groups
1379 @findex gnus-group-clear-data-on-native-groups
1380 If you don't have access to both the old and new server, all your marks
1381 and read ranges have become worthless. You can use the @kbd{M-x
1382 gnus-group-clear-data-on-native-groups} command to clear out all data
1383 that you have on your native groups. Use with caution.
1385 @kindex M-x gnus-group-clear-data
1386 @findex gnus-group-clear-data
1387 Clear the data from the current group only---nix out marks and the
1388 list of read articles (@code{gnus-group-clear-data}).
1390 After changing servers, you @strong{must} move the cache hierarchy away,
1391 since the cached articles will have wrong article numbers, which will
1392 affect which articles Gnus thinks are read.
1393 @code{gnus-group-clear-data-on-native-groups} will ask you if you want
1394 to have it done automatically; for @code{gnus-group-clear-data}, you
1395 can use @kbd{M-x gnus-cache-move-cache} (but beware, it will move the
1396 cache for all groups).
1400 @section Startup Files
1401 @cindex startup files
1406 Now, you all know about the @file{.newsrc} file. All subscription
1407 information is traditionally stored in this file.
1409 Things got a bit more complicated with @sc{gnus}. In addition to
1410 keeping the @file{.newsrc} file updated, it also used a file called
1411 @file{.newsrc.el} for storing all the information that didn't fit into
1412 the @file{.newsrc} file. (Actually, it also duplicated everything in
1413 the @file{.newsrc} file.) @sc{gnus} would read whichever one of these
1414 files was the most recently saved, which enabled people to swap between
1415 @sc{gnus} and other newsreaders.
1417 That was kinda silly, so Gnus went one better: In addition to the
1418 @file{.newsrc} and @file{.newsrc.el} files, Gnus also has a file called
1419 @file{.newsrc.eld}. It will read whichever of these files that are most
1420 recent, but it will never write a @file{.newsrc.el} file. You should
1421 never delete the @file{.newsrc.eld} file---it contains much information
1422 not stored in the @file{.newsrc} file.
1424 @vindex gnus-save-newsrc-file
1425 @vindex gnus-read-newsrc-file
1426 You can turn off writing the @file{.newsrc} file by setting
1427 @code{gnus-save-newsrc-file} to @code{nil}, which means you can delete
1428 the file and save some space, as well as exiting from Gnus faster.
1429 However, this will make it impossible to use other newsreaders than
1430 Gnus. But hey, who would want to, right? Similarly, setting
1431 @code{gnus-read-newsrc-file} to @code{nil} makes Gnus ignore the
1432 @file{.newsrc} file and any @file{.newsrc-SERVER} files, which is
1433 convenient if you have a tendency to use Netscape once in a while.
1435 @vindex gnus-save-killed-list
1436 If @code{gnus-save-killed-list} (default @code{t}) is @code{nil}, Gnus
1437 will not save the list of killed groups to the startup file. This will
1438 save both time (when starting and quitting) and space (on disk). It
1439 will also mean that Gnus has no record of what groups are new or old,
1440 so the automatic new groups subscription methods become meaningless.
1441 You should always set @code{gnus-check-new-newsgroups} to @code{nil} or
1442 @code{ask-server} if you set this variable to @code{nil} (@pxref{New
1443 Groups}). This variable can also be a regular expression. If that's
1444 the case, remove all groups that do not match this regexp before
1445 saving. This can be useful in certain obscure situations that involve
1446 several servers where not all servers support @code{ask-server}.
1448 @vindex gnus-startup-file
1449 @vindex gnus-backup-startup-file
1450 @vindex version-control
1451 The @code{gnus-startup-file} variable says where the startup files are.
1452 The default value is @file{~/.newsrc}, with the Gnus (El Dingo) startup
1453 file being whatever that one is, with a @samp{.eld} appended.
1454 If you want version control for this file, set
1455 @code{gnus-backup-startup-file}. It respects the same values as the
1456 @code{version-control} variable.
1458 @vindex gnus-save-newsrc-hook
1459 @vindex gnus-save-quick-newsrc-hook
1460 @vindex gnus-save-standard-newsrc-hook
1461 @code{gnus-save-newsrc-hook} is called before saving any of the newsrc
1462 files, while @code{gnus-save-quick-newsrc-hook} is called just before
1463 saving the @file{.newsrc.eld} file, and
1464 @code{gnus-save-standard-newsrc-hook} is called just before saving the
1465 @file{.newsrc} file. The latter two are commonly used to turn version
1466 control on or off. Version control is on by default when saving the
1467 startup files. If you want to turn backup creation off, say something like:
1470 (defun turn-off-backup ()
1471 (set (make-local-variable 'backup-inhibited) t))
1473 (add-hook 'gnus-save-quick-newsrc-hook 'turn-off-backup)
1474 (add-hook 'gnus-save-standard-newsrc-hook 'turn-off-backup)
1477 @vindex gnus-init-file
1478 @vindex gnus-site-init-file
1479 When Gnus starts, it will read the @code{gnus-site-init-file}
1480 (@file{.../site-lisp/gnus} by default) and @code{gnus-init-file}
1481 (@file{~/.gnus} by default) files. These are normal Emacs Lisp files
1482 and can be used to avoid cluttering your @file{~/.emacs} and
1483 @file{site-init} files with Gnus stuff. Gnus will also check for files
1484 with the same names as these, but with @file{.elc} and @file{.el}
1485 suffixes. In other words, if you have set @code{gnus-init-file} to
1486 @file{~/.gnus}, it will look for @file{~/.gnus.elc}, @file{~/.gnus.el},
1487 and finally @file{~/.gnus} (in this order).
1493 @cindex dribble file
1496 Whenever you do something that changes the Gnus data (reading articles,
1497 catching up, killing/subscribing groups), the change is added to a
1498 special @dfn{dribble buffer}. This buffer is auto-saved the normal
1499 Emacs way. If your Emacs should crash before you have saved the
1500 @file{.newsrc} files, all changes you have made can be recovered from
1503 If Gnus detects this file at startup, it will ask the user whether to
1504 read it. The auto save file is deleted whenever the real startup file is
1507 @vindex gnus-use-dribble-file
1508 If @code{gnus-use-dribble-file} is @code{nil}, Gnus won't create and
1509 maintain a dribble buffer. The default is @code{t}.
1511 @vindex gnus-dribble-directory
1512 Gnus will put the dribble file(s) in @code{gnus-dribble-directory}. If
1513 this variable is @code{nil}, which it is by default, Gnus will dribble
1514 into the directory where the @file{.newsrc} file is located. (This is
1515 normally the user's home directory.) The dribble file will get the same
1516 file permissions as the @file{.newsrc} file.
1518 @vindex gnus-always-read-dribble-file
1519 If @code{gnus-always-read-dribble-file} is non-@code{nil}, Gnus will
1520 read the dribble file on startup without querying the user.
1523 @node The Active File
1524 @section The Active File
1526 @cindex ignored groups
1528 When Gnus starts, or indeed whenever it tries to determine whether new
1529 articles have arrived, it reads the active file. This is a very large
1530 file that lists all the active groups and articles on the server.
1532 @vindex gnus-ignored-newsgroups
1533 Before examining the active file, Gnus deletes all lines that match the
1534 regexp @code{gnus-ignored-newsgroups}. This is done primarily to reject
1535 any groups with bogus names, but you can use this variable to make Gnus
1536 ignore hierarchies you aren't ever interested in. However, this is not
1537 recommended. In fact, it's highly discouraged. Instead, @pxref{New
1538 Groups} for an overview of other variables that can be used instead.
1541 @c @code{nil} by default, and will slow down active file handling somewhat
1542 @c if you set it to anything else.
1544 @vindex gnus-read-active-file
1546 The active file can be rather Huge, so if you have a slow network, you
1547 can set @code{gnus-read-active-file} to @code{nil} to prevent Gnus from
1548 reading the active file. This variable is @code{some} by default.
1550 Gnus will try to make do by getting information just on the groups that
1551 you actually subscribe to.
1553 Note that if you subscribe to lots and lots of groups, setting this
1554 variable to @code{nil} will probably make Gnus slower, not faster. At
1555 present, having this variable @code{nil} will slow Gnus down
1556 considerably, unless you read news over a 2400 baud modem.
1558 This variable can also have the value @code{some}. Gnus will then
1559 attempt to read active info only on the subscribed groups. On some
1560 servers this is quite fast (on sparkling, brand new INN servers that
1561 support the @code{LIST ACTIVE group} command), on others this isn't fast
1562 at all. In any case, @code{some} should be faster than @code{nil}, and
1563 is certainly faster than @code{t} over slow lines.
1565 Some news servers (old versions of Leafnode and old versions of INN, for
1566 instance) do not support the @code{LIST ACTIVE group}. For these
1567 servers, @code{nil} is probably the most efficient value for this
1570 If this variable is @code{nil}, Gnus will ask for group info in total
1571 lock-step, which isn't very fast. If it is @code{some} and you use an
1572 @sc{nntp} server, Gnus will pump out commands as fast as it can, and
1573 read all the replies in one swoop. This will normally result in better
1574 performance, but if the server does not support the aforementioned
1575 @code{LIST ACTIVE group} command, this isn't very nice to the server.
1577 If you think that starting up Gnus takes too long, try all the three
1578 different values for this variable and see what works best for you.
1580 In any case, if you use @code{some} or @code{nil}, you should definitely
1581 kill all groups that you aren't interested in to speed things up.
1583 Note that this variable also affects active file retrieval from
1584 secondary select methods.
1587 @node Startup Variables
1588 @section Startup Variables
1592 @item gnus-load-hook
1593 @vindex gnus-load-hook
1594 A hook run while Gnus is being loaded. Note that this hook will
1595 normally be run just once in each Emacs session, no matter how many
1596 times you start Gnus.
1598 @item gnus-before-startup-hook
1599 @vindex gnus-before-startup-hook
1600 A hook run after starting up Gnus successfully.
1602 @item gnus-startup-hook
1603 @vindex gnus-startup-hook
1604 A hook run as the very last thing after starting up Gnus
1606 @item gnus-started-hook
1607 @vindex gnus-started-hook
1608 A hook that is run as the very last thing after starting up Gnus
1611 @item gnus-setup-news-hook
1612 @vindex gnus-setup-news-hook
1613 A hook that is run after reading the @file{.newsrc} file(s), but before
1614 generating the group buffer.
1616 @item gnus-check-bogus-newsgroups
1617 @vindex gnus-check-bogus-newsgroups
1618 If non-@code{nil}, Gnus will check for and delete all bogus groups at
1619 startup. A @dfn{bogus group} is a group that you have in your
1620 @file{.newsrc} file, but doesn't exist on the news server. Checking for
1621 bogus groups can take quite a while, so to save time and resources it's
1622 best to leave this option off, and do the checking for bogus groups once
1623 in a while from the group buffer instead (@pxref{Group Maintenance}).
1625 @item gnus-inhibit-startup-message
1626 @vindex gnus-inhibit-startup-message
1627 If non-@code{nil}, the startup message won't be displayed. That way,
1628 your boss might not notice as easily that you are reading news instead
1629 of doing your job. Note that this variable is used before
1630 @file{~/.gnus.el} is loaded, so it should be set in @file{.emacs} instead.
1632 @item gnus-no-groups-message
1633 @vindex gnus-no-groups-message
1634 Message displayed by Gnus when no groups are available.
1636 @item gnus-play-startup-jingle
1637 @vindex gnus-play-startup-jingle
1638 If non-@code{nil}, play the Gnus jingle at startup.
1640 @item gnus-startup-jingle
1641 @vindex gnus-startup-jingle
1642 Jingle to be played if the above variable is non-@code{nil}. The
1643 default is @samp{Tuxedomoon.Jingle4.au}.
1649 @chapter Group Buffer
1650 @cindex group buffer
1652 @c Alex Schroeder suggests to rearrange this as follows:
1654 @c <kensanata> ok, just save it for reference. I'll go to bed in a minute.
1655 @c 1. Selecting a Group, 2. (new) Finding a Group, 3. Group Levels,
1656 @c 4. Subscription Commands, 5. Group Maneuvering, 6. Group Data,
1657 @c 7. Group Score, 8. Group Buffer Format
1658 @c <kensanata> Group Levels should have more information on levels 5 to 9. I
1659 @c suggest to split the 4th paragraph ("Gnus considers groups...") as follows:
1660 @c <kensanata> First, "Gnus considers groups... (default 9)."
1661 @c <kensanata> New, a table summarizing what levels 1 to 9 mean.
1662 @c <kensanata> Third, "Gnus treats subscribed ... reasons of efficiency"
1663 @c <kensanata> Then expand the next paragraph or add some more to it.
1664 @c This short one sentence explains levels 1 and 2, therefore I understand
1665 @c that I should keep important news at 3 and boring news at 4.
1666 @c Say so! Then go on to explain why I should bother with levels 6 to 9.
1667 @c Maybe keep those that you don't want to read temporarily at 6,
1668 @c those that you never want to read at 8, those that offend your
1669 @c human rights at 9...
1672 The @dfn{group buffer} lists all (or parts) of the available groups. It
1673 is the first buffer shown when Gnus starts, and will never be killed as
1674 long as Gnus is active.
1678 \gnusfigure{The Group Buffer}{320}{
1679 \put(75,50){\epsfig{figure=ps/group,height=9cm}}
1680 \put(120,37){\makebox(0,0)[t]{Buffer name}}
1681 \put(120,38){\vector(1,2){10}}
1682 \put(40,60){\makebox(0,0)[r]{Mode line}}
1683 \put(40,58){\vector(1,0){30}}
1684 \put(200,28){\makebox(0,0)[t]{Native select method}}
1685 \put(200,26){\vector(-1,2){15}}
1691 * Group Buffer Format:: Information listed and how you can change it.
1692 * Group Maneuvering:: Commands for moving in the group buffer.
1693 * Selecting a Group:: Actually reading news.
1694 * Subscription Commands:: Unsubscribing, killing, subscribing.
1695 * Group Data:: Changing the info for a group.
1696 * Group Levels:: Levels? What are those, then?
1697 * Group Score:: A mechanism for finding out what groups you like.
1698 * Marking Groups:: You can mark groups for later processing.
1699 * Foreign Groups:: Creating and editing groups.
1700 * Group Parameters:: Each group may have different parameters set.
1701 * Listing Groups:: Gnus can list various subsets of the groups.
1702 * Sorting Groups:: Re-arrange the group order.
1703 * Group Maintenance:: Maintaining a tidy @file{.newsrc} file.
1704 * Browse Foreign Server:: You can browse a server. See what it has to offer.
1705 * Exiting Gnus:: Stop reading news and get some work done.
1706 * Group Topics:: A folding group mode divided into topics.
1707 * Misc Group Stuff:: Other stuff that you can to do.
1711 @node Group Buffer Format
1712 @section Group Buffer Format
1715 * Group Line Specification:: Deciding how the group buffer is to look.
1716 * Group Modeline Specification:: The group buffer modeline.
1717 * Group Highlighting:: Having nice colors in the group buffer.
1721 @node Group Line Specification
1722 @subsection Group Line Specification
1723 @cindex group buffer format
1725 The default format of the group buffer is nice and dull, but you can
1726 make it as exciting and ugly as you feel like.
1728 Here's a couple of example group lines:
1731 25: news.announce.newusers
1732 * 0: alt.fan.andrea-dworkin
1737 You can see that there are 25 unread articles in
1738 @samp{news.announce.newusers}. There are no unread articles, but some
1739 ticked articles, in @samp{alt.fan.andrea-dworkin} (see that little
1740 asterisk at the beginning of the line?).
1742 @vindex gnus-group-line-format
1743 You can change that format to whatever you want by fiddling with the
1744 @code{gnus-group-line-format} variable. This variable works along the
1745 lines of a @code{format} specification, which is pretty much the same as
1746 a @code{printf} specifications, for those of you who use (feh!) C.
1747 @xref{Formatting Variables}.
1749 @samp{%M%S%5y:%B%(%g%)\n} is the value that produced those lines above.
1751 There should always be a colon on the line; the cursor always moves to
1752 the colon after performing an operation. @xref{Positioning
1753 Point}. Nothing else is required---not even the group name. All
1754 displayed text is just window dressing, and is never examined by Gnus.
1755 Gnus stores all real information it needs using text properties.
1757 (Note that if you make a really strange, wonderful, spreadsheet-like
1758 layout, everybody will believe you are hard at work with the accounting
1759 instead of wasting time reading news.)
1761 Here's a list of all available format characters:
1766 An asterisk if the group only has marked articles.
1769 Whether the group is subscribed.
1772 Level of subscribedness.
1775 Number of unread articles.
1778 Number of dormant articles.
1781 Number of ticked articles.
1784 Number of read articles.
1787 Number of unseen articles.
1790 Estimated total number of articles. (This is really @var{max-number}
1791 minus @var{min-number} plus 1.)
1793 Gnus uses this estimation because the @sc{nntp} protocol provides
1794 efficient access to @var{max-number} and @var{min-number} but getting
1795 the true unread message count is not possible efficiently. For
1796 hysterical raisins, even the mail back ends, where the true number of
1797 unread messages might be available efficiently, use the same limited
1798 interface. To remove this restriction from Gnus means that the back
1799 end interface has to be changed, which is not an easy job. If you
1800 want to work on this, please contact the Gnus mailing list.
1803 Number of unread, unticked, non-dormant articles.
1806 Number of ticked and dormant articles.
1815 Group comment (@pxref{Group Parameters}) or group name if there is no
1816 comment element in the group parameters.
1819 Newsgroup description.
1822 @samp{m} if moderated.
1825 @samp{(m)} if moderated.
1831 If the summary buffer for the group is open or not.
1837 A string that looks like @samp{<%s:%n>} if a foreign select method is
1841 Indentation based on the level of the topic (@pxref{Group Topics}).
1844 @vindex gnus-group-uncollapsed-levels
1845 Short (collapsed) group name. The @code{gnus-group-uncollapsed-levels}
1846 variable says how many levels to leave at the end of the group name.
1847 The default is 1---this will mean that group names like
1848 @samp{gnu.emacs.gnus} will be shortened to @samp{g.e.gnus}.
1851 @vindex gnus-new-mail-mark
1853 @samp{%} (@code{gnus-new-mail-mark}) if there has arrived new mail to
1857 @samp{#} (@code{gnus-process-mark}) if the group is process marked.
1860 A string that says when you last read the group (@pxref{Group
1864 User defined specifier. The next character in the format string should
1865 be a letter. Gnus will call the function
1866 @code{gnus-user-format-function-}@samp{X}, where @samp{X} is the letter
1867 following @samp{%u}. The function will be passed a single dummy
1868 parameter as argument. The function should return a string, which will
1869 be inserted into the buffer just like information from any other
1874 All the ``number-of'' specs will be filled with an asterisk (@samp{*})
1875 if no info is available---for instance, if it is a non-activated foreign
1876 group, or a bogus native group.
1879 @node Group Modeline Specification
1880 @subsection Group Modeline Specification
1881 @cindex group modeline
1883 @vindex gnus-group-mode-line-format
1884 The mode line can be changed by setting
1885 @code{gnus-group-mode-line-format} (@pxref{Mode Line Formatting}). It
1886 doesn't understand that many format specifiers:
1890 The native news server.
1892 The native select method.
1896 @node Group Highlighting
1897 @subsection Group Highlighting
1898 @cindex highlighting
1899 @cindex group highlighting
1901 @vindex gnus-group-highlight
1902 Highlighting in the group buffer is controlled by the
1903 @code{gnus-group-highlight} variable. This is an alist with elements
1904 that look like @code{(@var{form} . @var{face})}. If @var{form} evaluates to
1905 something non-@code{nil}, the @var{face} will be used on the line.
1907 Here's an example value for this variable that might look nice if the
1911 (cond (window-system
1912 (setq custom-background-mode 'light)
1913 (defface my-group-face-1
1914 '((t (:foreground "Red" :bold t))) "First group face")
1915 (defface my-group-face-2
1916 '((t (:foreground "DarkSeaGreen4" :bold t))) "Second group face")
1917 (defface my-group-face-3
1918 '((t (:foreground "Green4" :bold t))) "Third group face")
1919 (defface my-group-face-4
1920 '((t (:foreground "SteelBlue" :bold t))) "Fourth group face")
1921 (defface my-group-face-5
1922 '((t (:foreground "Blue" :bold t))) "Fifth group face")))
1924 (setq gnus-group-highlight
1925 '(((> unread 200) . my-group-face-1)
1926 ((and (< level 3) (zerop unread)) . my-group-face-2)
1927 ((< level 3) . my-group-face-3)
1928 ((zerop unread) . my-group-face-4)
1929 (t . my-group-face-5)))
1932 Also @pxref{Faces and Fonts}.
1934 Variables that are dynamically bound when the forms are evaluated
1941 The number of unread articles in the group.
1945 Whether the group is a mail group.
1947 The level of the group.
1949 The score of the group.
1951 The number of ticked articles in the group.
1953 The total number of articles in the group. Or rather,
1954 @var{max-number} minus @var{min-number} plus one.
1956 When using the topic minor mode, this variable is bound to the current
1957 topic being inserted.
1960 When the forms are @code{eval}ed, point is at the beginning of the line
1961 of the group in question, so you can use many of the normal Gnus
1962 functions for snarfing info on the group.
1964 @vindex gnus-group-update-hook
1965 @findex gnus-group-highlight-line
1966 @code{gnus-group-update-hook} is called when a group line is changed.
1967 It will not be called when @code{gnus-visual} is @code{nil}. This hook
1968 calls @code{gnus-group-highlight-line} by default.
1971 @node Group Maneuvering
1972 @section Group Maneuvering
1973 @cindex group movement
1975 All movement commands understand the numeric prefix and will behave as
1976 expected, hopefully.
1982 @findex gnus-group-next-unread-group
1983 Go to the next group that has unread articles
1984 (@code{gnus-group-next-unread-group}).
1990 @findex gnus-group-prev-unread-group
1991 Go to the previous group that has unread articles
1992 (@code{gnus-group-prev-unread-group}).
1996 @findex gnus-group-next-group
1997 Go to the next group (@code{gnus-group-next-group}).
2001 @findex gnus-group-prev-group
2002 Go to the previous group (@code{gnus-group-prev-group}).
2006 @findex gnus-group-next-unread-group-same-level
2007 Go to the next unread group on the same (or lower) level
2008 (@code{gnus-group-next-unread-group-same-level}).
2012 @findex gnus-group-prev-unread-group-same-level
2013 Go to the previous unread group on the same (or lower) level
2014 (@code{gnus-group-prev-unread-group-same-level}).
2017 Three commands for jumping to groups:
2023 @findex gnus-group-jump-to-group
2024 Jump to a group (and make it visible if it isn't already)
2025 (@code{gnus-group-jump-to-group}). Killed groups can be jumped to, just
2030 @findex gnus-group-best-unread-group
2031 Jump to the unread group with the lowest level
2032 (@code{gnus-group-best-unread-group}).
2036 @findex gnus-group-first-unread-group
2037 Jump to the first group with unread articles
2038 (@code{gnus-group-first-unread-group}).
2041 @vindex gnus-group-goto-unread
2042 If @code{gnus-group-goto-unread} is @code{nil}, all the movement
2043 commands will move to the next group, not the next unread group. Even
2044 the commands that say they move to the next unread group. The default
2048 @node Selecting a Group
2049 @section Selecting a Group
2050 @cindex group selection
2055 @kindex SPACE (Group)
2056 @findex gnus-group-read-group
2057 Select the current group, switch to the summary buffer and display the
2058 first unread article (@code{gnus-group-read-group}). If there are no
2059 unread articles in the group, or if you give a non-numerical prefix to
2060 this command, Gnus will offer to fetch all the old articles in this
2061 group from the server. If you give a numerical prefix @var{n}, @var{n}
2062 determines the number of articles Gnus will fetch. If @var{n} is
2063 positive, Gnus fetches the @var{n} newest articles, if @var{n} is
2064 negative, Gnus fetches the @code{abs(@var{n})} oldest articles.
2066 Thus, @kbd{SPC} enters the group normally, @kbd{C-u SPC} offers old
2067 articles, @kbd{C-u 4 2 SPC} fetches the 42 newest articles, and @kbd{C-u
2068 - 4 2 SPC} fetches the 42 oldest ones.
2070 When you are in the group (in the Summary buffer), you can type
2071 @kbd{M-g} to fetch new articles, or @kbd{C-u M-g} to also show the old
2076 @findex gnus-group-select-group
2077 Select the current group and switch to the summary buffer
2078 (@code{gnus-group-select-group}). Takes the same arguments as
2079 @code{gnus-group-read-group}---the only difference is that this command
2080 does not display the first unread article automatically upon group
2084 @kindex M-RET (Group)
2085 @findex gnus-group-quick-select-group
2086 This does the same as the command above, but tries to do it with the
2087 minimum amount of fuzz (@code{gnus-group-quick-select-group}). No
2088 scoring/killing will be performed, there will be no highlights and no
2089 expunging. This might be useful if you're in a real hurry and have to
2090 enter some humongous group. If you give a 0 prefix to this command
2091 (i.e., @kbd{0 M-RET}), Gnus won't even generate the summary buffer,
2092 which is useful if you want to toggle threading before generating the
2093 summary buffer (@pxref{Summary Generation Commands}).
2096 @kindex M-SPACE (Group)
2097 @findex gnus-group-visible-select-group
2098 This is yet one more command that does the same as the @kbd{RET}
2099 command, but this one does it without expunging and hiding dormants
2100 (@code{gnus-group-visible-select-group}).
2103 @kindex C-M-RET (Group)
2104 @findex gnus-group-select-group-ephemerally
2105 Finally, this command selects the current group ephemerally without
2106 doing any processing of its contents
2107 (@code{gnus-group-select-group-ephemerally}). Even threading has been
2108 turned off. Everything you do in the group after selecting it in this
2109 manner will have no permanent effects.
2113 @vindex gnus-large-newsgroup
2114 The @code{gnus-large-newsgroup} variable says what Gnus should consider
2115 to be a big group. This is 200 by default. If the group has more
2116 (unread and/or ticked) articles than this, Gnus will query the user
2117 before entering the group. The user can then specify how many articles
2118 should be fetched from the server. If the user specifies a negative
2119 number (@code{-n}), the @code{n} oldest articles will be fetched. If it
2120 is positive, the @code{n} articles that have arrived most recently will
2123 @vindex gnus-select-group-hook
2124 @vindex gnus-auto-select-first
2125 @vindex gnus-auto-select-subject
2126 If @code{gnus-auto-select-first} is non-@code{nil}, select an article
2127 automatically when entering a group with the @kbd{SPACE} command.
2128 Which article this is is controlled by the
2129 @code{gnus-auto-select-subject} variable. Valid values for this
2135 Place point on the subject line of the first unread article.
2138 Place point on the subject line of the first article.
2141 Place point on the subject line of the first unseen article.
2143 @item unseen-or-unread
2144 Place point on the subject line of the first unseen article, and if
2145 there is no such article, place point on the subject line of the first
2149 Place point on the subject line of the highest-scored unread article.
2153 This variable can also be a function. In that case, that function
2154 will be called to place point on a subject line.
2156 If you want to prevent automatic selection in some group (say, in a
2157 binary group with Huge articles) you can set the
2158 @code{gnus-auto-select-first} variable to @code{nil} in
2159 @code{gnus-select-group-hook}, which is called when a group is
2163 @node Subscription Commands
2164 @section Subscription Commands
2165 @cindex subscription
2173 @findex gnus-group-unsubscribe-current-group
2174 @c @icon{gnus-group-unsubscribe}
2175 Toggle subscription to the current group
2176 (@code{gnus-group-unsubscribe-current-group}).
2182 @findex gnus-group-unsubscribe-group
2183 Prompt for a group to subscribe, and then subscribe it. If it was
2184 subscribed already, unsubscribe it instead
2185 (@code{gnus-group-unsubscribe-group}).
2191 @findex gnus-group-kill-group
2192 @c @icon{gnus-group-kill-group}
2193 Kill the current group (@code{gnus-group-kill-group}).
2199 @findex gnus-group-yank-group
2200 Yank the last killed group (@code{gnus-group-yank-group}).
2203 @kindex C-x C-t (Group)
2204 @findex gnus-group-transpose-groups
2205 Transpose two groups (@code{gnus-group-transpose-groups}). This isn't
2206 really a subscription command, but you can use it instead of a
2207 kill-and-yank sequence sometimes.
2213 @findex gnus-group-kill-region
2214 Kill all groups in the region (@code{gnus-group-kill-region}).
2218 @findex gnus-group-kill-all-zombies
2219 Kill all zombie groups (@code{gnus-group-kill-all-zombies}).
2222 @kindex S C-k (Group)
2223 @findex gnus-group-kill-level
2224 Kill all groups on a certain level (@code{gnus-group-kill-level}).
2225 These groups can't be yanked back after killing, so this command should
2226 be used with some caution. The only time where this command comes in
2227 really handy is when you have a @file{.newsrc} with lots of unsubscribed
2228 groups that you want to get rid off. @kbd{S C-k} on level 7 will
2229 kill off all unsubscribed groups that do not have message numbers in the
2230 @file{.newsrc} file.
2234 Also @pxref{Group Levels}.
2244 @findex gnus-group-catchup-current
2245 @vindex gnus-group-catchup-group-hook
2246 @c @icon{gnus-group-catchup-current}
2247 Mark all unticked articles in this group as read
2248 (@code{gnus-group-catchup-current}).
2249 @code{gnus-group-catchup-group-hook} is called when catching up a group from
2254 @findex gnus-group-catchup-current-all
2255 Mark all articles in this group, even the ticked ones, as read
2256 (@code{gnus-group-catchup-current-all}).
2260 @findex gnus-group-clear-data
2261 Clear the data from the current group---nix out marks and the list of
2262 read articles (@code{gnus-group-clear-data}).
2264 @item M-x gnus-group-clear-data-on-native-groups
2265 @kindex M-x gnus-group-clear-data-on-native-groups
2266 @findex gnus-group-clear-data-on-native-groups
2267 If you have switched from one @sc{nntp} server to another, all your marks
2268 and read ranges have become worthless. You can use this command to
2269 clear out all data that you have on your native groups. Use with
2276 @section Group Levels
2280 All groups have a level of @dfn{subscribedness}. For instance, if a
2281 group is on level 2, it is more subscribed than a group on level 5. You
2282 can ask Gnus to just list groups on a given level or lower
2283 (@pxref{Listing Groups}), or to just check for new articles in groups on
2284 a given level or lower (@pxref{Scanning New Messages}).
2286 Remember: The higher the level of the group, the less important it is.
2292 @findex gnus-group-set-current-level
2293 Set the level of the current group. If a numeric prefix is given, the
2294 next @var{n} groups will have their levels set. The user will be
2295 prompted for a level.
2298 @vindex gnus-level-killed
2299 @vindex gnus-level-zombie
2300 @vindex gnus-level-unsubscribed
2301 @vindex gnus-level-subscribed
2302 Gnus considers groups from levels 1 to
2303 @code{gnus-level-subscribed} (inclusive) (default 5) to be subscribed,
2304 @code{gnus-level-subscribed} (exclusive) and
2305 @code{gnus-level-unsubscribed} (inclusive) (default 7) to be
2306 unsubscribed, @code{gnus-level-zombie} to be zombies (walking dead)
2307 (default 8) and @code{gnus-level-killed} to be killed (completely dead)
2308 (default 9). Gnus treats subscribed and unsubscribed groups exactly the
2309 same, but zombie and killed groups have no information on what articles
2310 you have read, etc, stored. This distinction between dead and living
2311 groups isn't done because it is nice or clever, it is done purely for
2312 reasons of efficiency.
2314 It is recommended that you keep all your mail groups (if any) on quite
2315 low levels (e.g. 1 or 2).
2317 Maybe the following description of the default behavior of Gnus helps to
2318 understand what these levels are all about. By default, Gnus shows you
2319 subscribed nonempty groups, but by hitting @kbd{L} you can have it show
2320 empty subscribed groups and unsubscribed groups, too. Type @kbd{l} to
2321 go back to showing nonempty subscribed groups again. Thus, unsubscribed
2322 groups are hidden, in a way.
2324 Zombie and killed groups are similar to unsubscribed groups in that they
2325 are hidden by default. But they are different from subscribed and
2326 unsubscribed groups in that Gnus doesn't ask the news server for
2327 information (number of messages, number of unread messages) on zombie
2328 and killed groups. Normally, you use @kbd{C-k} to kill the groups you
2329 aren't interested in. If most groups are killed, Gnus is faster.
2331 Why does Gnus distinguish between zombie and killed groups? Well, when
2332 a new group arrives on the server, Gnus by default makes it a zombie
2333 group. This means that you are normally not bothered with new groups,
2334 but you can type @kbd{A z} to get a list of all new groups. Subscribe
2335 the ones you like and kill the ones you don't want. (@kbd{A k} shows a
2336 list of killed groups.)
2338 If you want to play with the level variables, you should show some care.
2339 Set them once, and don't touch them ever again. Better yet, don't touch
2340 them at all unless you know exactly what you're doing.
2342 @vindex gnus-level-default-unsubscribed
2343 @vindex gnus-level-default-subscribed
2344 Two closely related variables are @code{gnus-level-default-subscribed}
2345 (default 3) and @code{gnus-level-default-unsubscribed} (default 6),
2346 which are the levels that new groups will be put on if they are
2347 (un)subscribed. These two variables should, of course, be inside the
2348 relevant valid ranges.
2350 @vindex gnus-keep-same-level
2351 If @code{gnus-keep-same-level} is non-@code{nil}, some movement commands
2352 will only move to groups of the same level (or lower). In
2353 particular, going from the last article in one group to the next group
2354 will go to the next group of the same level (or lower). This might be
2355 handy if you want to read the most important groups before you read the
2358 If this variable is @code{best}, Gnus will make the next newsgroup the
2359 one with the best level.
2361 @vindex gnus-group-default-list-level
2362 All groups with a level less than or equal to
2363 @code{gnus-group-default-list-level} will be listed in the group buffer
2366 @vindex gnus-group-list-inactive-groups
2367 If @code{gnus-group-list-inactive-groups} is non-@code{nil}, non-active
2368 groups will be listed along with the unread groups. This variable is
2369 @code{t} by default. If it is @code{nil}, inactive groups won't be
2372 @vindex gnus-group-use-permanent-levels
2373 If @code{gnus-group-use-permanent-levels} is non-@code{nil}, once you
2374 give a level prefix to @kbd{g} or @kbd{l}, all subsequent commands will
2375 use this level as the ``work'' level.
2377 @vindex gnus-activate-level
2378 Gnus will normally just activate (i. e., query the server about) groups
2379 on level @code{gnus-activate-level} or less. If you don't want to
2380 activate unsubscribed groups, for instance, you might set this variable
2381 to 5. The default is 6.
2385 @section Group Score
2390 You would normally keep important groups on high levels, but that scheme
2391 is somewhat restrictive. Don't you wish you could have Gnus sort the
2392 group buffer according to how often you read groups, perhaps? Within
2395 This is what @dfn{group score} is for. You can have Gnus assign a score
2396 to each group through the mechanism described below. You can then sort
2397 the group buffer based on this score. Alternatively, you can sort on
2398 score and then level. (Taken together, the level and the score is
2399 called the @dfn{rank} of the group. A group that is on level 4 and has
2400 a score of 1 has a higher rank than a group on level 5 that has a score
2401 of 300. (The level is the most significant part and the score is the
2402 least significant part.))
2404 @findex gnus-summary-bubble-group
2405 If you want groups you read often to get higher scores than groups you
2406 read seldom you can add the @code{gnus-summary-bubble-group} function to
2407 the @code{gnus-summary-exit-hook} hook. This will result (after
2408 sorting) in a bubbling sort of action. If you want to see that in
2409 action after each summary exit, you can add
2410 @code{gnus-group-sort-groups-by-rank} or
2411 @code{gnus-group-sort-groups-by-score} to the same hook, but that will
2412 slow things down somewhat.
2415 @node Marking Groups
2416 @section Marking Groups
2417 @cindex marking groups
2419 If you want to perform some command on several groups, and they appear
2420 subsequently in the group buffer, you would normally just give a
2421 numerical prefix to the command. Most group commands will then do your
2422 bidding on those groups.
2424 However, if the groups are not in sequential order, you can still
2425 perform a command on several groups. You simply mark the groups first
2426 with the process mark and then execute the command.
2434 @findex gnus-group-mark-group
2435 Set the mark on the current group (@code{gnus-group-mark-group}).
2441 @findex gnus-group-unmark-group
2442 Remove the mark from the current group
2443 (@code{gnus-group-unmark-group}).
2447 @findex gnus-group-unmark-all-groups
2448 Remove the mark from all groups (@code{gnus-group-unmark-all-groups}).
2452 @findex gnus-group-mark-region
2453 Mark all groups between point and mark (@code{gnus-group-mark-region}).
2457 @findex gnus-group-mark-buffer
2458 Mark all groups in the buffer (@code{gnus-group-mark-buffer}).
2462 @findex gnus-group-mark-regexp
2463 Mark all groups that match some regular expression
2464 (@code{gnus-group-mark-regexp}).
2467 Also @pxref{Process/Prefix}.
2469 @findex gnus-group-universal-argument
2470 If you want to execute some command on all groups that have been marked
2471 with the process mark, you can use the @kbd{M-&}
2472 (@code{gnus-group-universal-argument}) command. It will prompt you for
2473 the command to be executed.
2476 @node Foreign Groups
2477 @section Foreign Groups
2478 @cindex foreign groups
2480 Below are some group mode commands for making and editing general foreign
2481 groups, as well as commands to ease the creation of a few
2482 special-purpose groups. All these commands insert the newly created
2483 groups under point---@code{gnus-subscribe-newsgroup-method} is not
2490 @findex gnus-group-make-group
2491 @cindex making groups
2492 Make a new group (@code{gnus-group-make-group}). Gnus will prompt you
2493 for a name, a method and possibly an @dfn{address}. For an easier way
2494 to subscribe to @sc{nntp} groups, @pxref{Browse Foreign Server}.
2498 @findex gnus-group-rename-group
2499 @cindex renaming groups
2500 Rename the current group to something else
2501 (@code{gnus-group-rename-group}). This is valid only on some
2502 groups---mail groups mostly. This command might very well be quite slow
2508 @findex gnus-group-customize
2509 Customize the group parameters (@code{gnus-group-customize}).
2513 @findex gnus-group-edit-group-method
2514 @cindex renaming groups
2515 Enter a buffer where you can edit the select method of the current
2516 group (@code{gnus-group-edit-group-method}).
2520 @findex gnus-group-edit-group-parameters
2521 Enter a buffer where you can edit the group parameters
2522 (@code{gnus-group-edit-group-parameters}).
2526 @findex gnus-group-edit-group
2527 Enter a buffer where you can edit the group info
2528 (@code{gnus-group-edit-group}).
2532 @findex gnus-group-make-directory-group
2534 Make a directory group (@pxref{Directory Groups}). You will be prompted
2535 for a directory name (@code{gnus-group-make-directory-group}).
2540 @findex gnus-group-make-help-group
2541 Make the Gnus help group (@code{gnus-group-make-help-group}).
2545 @cindex (ding) archive
2546 @cindex archive group
2547 @findex gnus-group-make-archive-group
2548 @vindex gnus-group-archive-directory
2549 @vindex gnus-group-recent-archive-directory
2550 Make a Gnus archive group (@code{gnus-group-make-archive-group}). By
2551 default a group pointing to the most recent articles will be created
2552 (@code{gnus-group-recent-archive-directory}), but given a prefix, a full
2553 group will be created from @code{gnus-group-archive-directory}.
2557 @findex gnus-group-make-kiboze-group
2559 Make a kiboze group. You will be prompted for a name, for a regexp to
2560 match groups to be ``included'' in the kiboze group, and a series of
2561 strings to match on headers (@code{gnus-group-make-kiboze-group}).
2562 @xref{Kibozed Groups}.
2566 @findex gnus-group-enter-directory
2568 Read an arbitrary directory as if it were a newsgroup with the
2569 @code{nneething} back end (@code{gnus-group-enter-directory}).
2570 @xref{Anything Groups}.
2574 @findex gnus-group-make-doc-group
2575 @cindex ClariNet Briefs
2577 Make a group based on some file or other
2578 (@code{gnus-group-make-doc-group}). If you give a prefix to this
2579 command, you will be prompted for a file name and a file type.
2580 Currently supported types are @code{mbox}, @code{babyl},
2581 @code{digest}, @code{news}, @code{rnews}, @code{mmdf}, @code{forward},
2582 @code{rfc934}, @code{rfc822-forward}, @code{mime-parts},
2583 @code{standard-digest}, @code{slack-digest}, @code{clari-briefs},
2584 @code{nsmail}, @code{outlook}, @code{oe-dbx}, and @code{mailman}. If
2585 you run this command without a prefix, Gnus will guess at the file
2586 type. @xref{Document Groups}.
2590 @vindex gnus-useful-groups
2591 @findex gnus-group-make-useful-group
2592 Create one of the groups mentioned in @code{gnus-useful-groups}
2593 (@code{gnus-group-make-useful-group}).
2597 @findex gnus-group-make-web-group
2601 Make an ephemeral group based on a web search
2602 (@code{gnus-group-make-web-group}). If you give a prefix to this
2603 command, make a solid group instead. You will be prompted for the
2604 search engine type and the search string. Valid search engine types
2605 include @code{google}, @code{dejanews}, and @code{gmane}.
2606 @xref{Web Searches}.
2608 If you use the @code{google} search engine, you can limit the search
2609 to a particular group by using a match string like
2610 @samp{shaving group:alt.sysadmin.recovery}.
2613 @kindex G DEL (Group)
2614 @findex gnus-group-delete-group
2615 This function will delete the current group
2616 (@code{gnus-group-delete-group}). If given a prefix, this function will
2617 actually delete all the articles in the group, and forcibly remove the
2618 group itself from the face of the Earth. Use a prefix only if you are
2619 absolutely sure of what you are doing. This command can't be used on
2620 read-only groups (like @code{nntp} group), though.
2624 @findex gnus-group-make-empty-virtual
2625 Make a new, fresh, empty @code{nnvirtual} group
2626 (@code{gnus-group-make-empty-virtual}). @xref{Virtual Groups}.
2630 @findex gnus-group-add-to-virtual
2631 Add the current group to an @code{nnvirtual} group
2632 (@code{gnus-group-add-to-virtual}). Uses the process/prefix convention.
2635 @xref{Select Methods}, for more information on the various select
2638 @vindex gnus-activate-foreign-newsgroups
2639 If @code{gnus-activate-foreign-newsgroups} is a positive number,
2640 Gnus will check all foreign groups with this level or lower at startup.
2641 This might take quite a while, especially if you subscribe to lots of
2642 groups from different @sc{nntp} servers. Also @pxref{Group Levels};
2643 @code{gnus-activate-level} also affects activation of foreign
2647 @node Group Parameters
2648 @section Group Parameters
2649 @cindex group parameters
2651 The group parameters store information local to a particular group.
2652 Here's an example group parameter list:
2655 ((to-address . "ding@@gnus.org")
2659 We see that each element consists of a ``dotted pair''---the thing before
2660 the dot is the key, while the thing after the dot is the value. All the
2661 parameters have this form @emph{except} local variable specs, which are
2662 not dotted pairs, but proper lists.
2664 Some parameters have correspondant customizable variables, each of which
2665 is an alist of regexps and values.
2667 The following group parameters can be used:
2672 Address used by when doing followups and new posts.
2675 (to-address . "some@@where.com")
2678 This is primarily useful in mail groups that represent closed mailing
2679 lists---mailing lists where it's expected that everybody that writes to
2680 the mailing list is subscribed to it. Since using this parameter
2681 ensures that the mail only goes to the mailing list itself, it means
2682 that members won't receive two copies of your followups.
2684 Using @code{to-address} will actually work whether the group is foreign
2685 or not. Let's say there's a group on the server that is called
2686 @samp{fa.4ad-l}. This is a real newsgroup, but the server has gotten
2687 the articles from a mail-to-news gateway. Posting directly to this
2688 group is therefore impossible---you have to send mail to the mailing
2689 list address instead.
2691 See also @code{gnus-parameter-to-address-alist}.
2695 Address used when doing @kbd{a} in that group.
2698 (to-list . "some@@where.com")
2701 It is totally ignored
2702 when doing a followup---except that if it is present in a news group,
2703 you'll get mail group semantics when doing @kbd{f}.
2705 If you do an @kbd{a} command in a mail group and you have neither a
2706 @code{to-list} group parameter nor a @code{to-address} group parameter,
2707 then a @code{to-list} group parameter will be added automatically upon
2708 sending the message if @code{gnus-add-to-list} is set to @code{t}.
2709 @vindex gnus-add-to-list
2711 If you do an @kbd{a} command in a mail group and you don't have a
2712 @code{to-list} group parameter, one will be added automatically upon
2713 sending the message.
2715 @findex gnus-mailing-list-mode
2716 @cindex Mail List Groups
2717 If this variable is set, @code{gnus-mailing-list-mode} is turned on when
2718 entering summary buffer.
2720 See also @code{gnus-parameter-to-list-alist}.
2725 If this parameter is set to @code{t}, Gnus will consider the
2726 to-address and to-list parameters for this group as addresses of
2727 mailing lists you are subscribed to. Giving Gnus this information is
2728 (only) a first step in getting it to generate correct Mail-Followup-To
2729 headers for your posts to these lists. Look here @pxref{Mailing
2730 Lists, , Mailing Lists, message, The Message Manual} for a complete
2731 treatment of available MFT support.
2733 See also @code{gnus-find-subscribed-addresses}, the function that
2734 directly uses this group parameter.
2738 If the group parameter list has the element @code{(visible . t)},
2739 that group will always be visible in the Group buffer, regardless
2740 of whether it has any unread articles.
2742 @item broken-reply-to
2743 @cindex broken-reply-to
2744 Elements like @code{(broken-reply-to . t)} signals that @code{Reply-To}
2745 headers in this group are to be ignored. This can be useful if you're
2746 reading a mailing list group where the listserv has inserted
2747 @code{Reply-To} headers that point back to the listserv itself. This is
2748 broken behavior. So there!
2752 Elements like @code{(to-group . "some.group.name")} means that all
2753 posts in that group will be sent to @code{some.group.name}.
2757 If you have @code{(newsgroup . t)} in the group parameter list, Gnus
2758 will treat all responses as if they were responses to news articles.
2759 This can be useful if you have a mail group that's really a mirror of a
2764 If @code{(gcc-self . t)} is present in the group parameter list, newly
2765 composed messages will be @code{Gcc}'d to the current group. If
2766 @code{(gcc-self . none)} is present, no @code{Gcc:} header will be
2767 generated, if @code{(gcc-self . "string")} is present, this string will
2768 be inserted literally as a @code{gcc} header. This parameter takes
2769 precedence over any default @code{Gcc} rules as described later
2770 (@pxref{Archived Messages}). CAVEAT:: It yields an error putting
2771 @code{(gcc-self . t)} in groups of a @code{nntp} server or so, because
2772 a @code{nntp} server doesn't accept articles.
2776 If the group parameter has an element that looks like @code{(auto-expire
2777 . t)}, all articles read will be marked as expirable. For an
2778 alternative approach, @pxref{Expiring Mail}.
2780 See also @code{gnus-auto-expirable-newsgroups}.
2783 @cindex total-expire
2784 If the group parameter has an element that looks like
2785 @code{(total-expire . t)}, all read articles will be put through the
2786 expiry process, even if they are not marked as expirable. Use with
2787 caution. Unread, ticked and dormant articles are not eligible for
2790 See also @code{gnus-total-expirable-newsgroups}.
2794 @vindex nnmail-expiry-wait-function
2795 If the group parameter has an element that looks like
2796 @code{(expiry-wait . 10)}, this value will override any
2797 @code{nnmail-expiry-wait} and @code{nnmail-expiry-wait-function}
2798 (@pxref{Expiring Mail}) when expiring expirable messages. The value
2799 can either be a number of days (not necessarily an integer) or the
2800 symbols @code{never} or @code{immediate}.
2803 @cindex score file group parameter
2804 Elements that look like @code{(score-file . "file")} will make
2805 @file{file} into the current score file for the group in question. All
2806 interactive score entries will be put into this file.
2809 @cindex adapt file group parameter
2810 Elements that look like @code{(adapt-file . "file")} will make
2811 @file{file} into the current adaptive file for the group in question.
2812 All adaptive score entries will be put into this file.
2815 @cindex admin-address
2816 When unsubscribing from a mailing list you should never send the
2817 unsubscription notice to the mailing list itself. Instead, you'd send
2818 messages to the administrative address. This parameter allows you to
2819 put the admin address somewhere convenient.
2823 Elements that look like @code{(display . MODE)} say which articles to
2824 display on entering the group. Valid values are:
2828 Display all articles, both read and unread.
2831 Display the last @var{integer} articles in the group. This is the same as
2832 entering the group with C-u @var{integer}.
2835 Display the default visible articles, which normally includes unread and
2839 Display articles that satisfy a predicate.
2841 Here are some examples:
2845 Display only unread articles.
2848 Display everything except expirable articles.
2850 @item [and (not reply) (not expire)]
2851 Display everything except expirable and articles you've already
2855 The available operators are @code{not}, @code{and} and @code{or}.
2856 Predicates include @code{tick}, @code{unsend}, @code{undownload},
2857 @code{unread}, @code{dormant}, @code{expire}, @code{reply},
2858 @code{killed}, @code{bookmark}, @code{score}, @code{save},
2859 @code{cache}, @code{forward}, @code{unseen} and @code{recent}.
2863 The @code{display} parameter works by limiting the summary buffer to
2864 the subset specified. You can pop the limit by using the @kbd{/ w}
2865 command (@pxref{Limiting}).
2869 Elements that look like @code{(comment . "This is a comment")} are
2870 arbitrary comments on the group. You can display comments in the
2871 group line (@pxref{Group Line Specification}).
2875 Elements that look like @code{(charset . iso-8859-1)} will make
2876 @code{iso-8859-1} the default charset; that is, the charset that will be
2877 used for all articles that do not specify a charset.
2879 See also @code{gnus-group-charset-alist}.
2881 @item ignored-charsets
2882 @cindex ignored-charset
2883 Elements that look like @code{(ignored-charsets x-unknown iso-8859-1)}
2884 will make @code{iso-8859-1} and @code{x-unknown} ignored; that is, the
2885 default charset will be used for decoding articles.
2887 See also @code{gnus-group-ignored-charsets-alist}.
2890 @cindex posting-style
2891 You can store additional posting style information for this group
2892 here (@pxref{Posting Styles}). The format is that of an entry in the
2893 @code{gnus-posting-styles} alist, except that there's no regexp matching
2894 the group name (of course). Style elements in this group parameter will
2895 take precedence over the ones found in @code{gnus-posting-styles}.
2897 For instance, if you want a funky name and signature in this group only,
2898 instead of hacking @code{gnus-posting-styles}, you could put something
2899 like this in the group parameters:
2904 ("X-My-Header" "Funky Value")
2905 (signature "Funky Signature"))
2910 If it is set, the value is used as the method for posting message
2911 instead of @code{gnus-post-method}.
2915 An item like @code{(banner . "regex")} causes any part of an article
2916 that matches the regular expression "regex" to be stripped. Instead of
2917 "regex", you can also use the symbol @code{signature} which strips the
2918 last signature or any of the elements of the alist
2919 @code{gnus-article-banner-alist}.
2923 This parameter contains a Sieve test that should match incoming mail
2924 that should be placed in this group. From this group parameter, a
2925 Sieve @samp{IF} control structure is generated, having the test as the
2926 condition and @samp{fileinto "group.name";} as the body.
2928 For example, if the INBOX.list.sieve group has the @code{(sieve
2929 address "sender" "sieve-admin@@extundo.com")} group parameter, when
2930 translating the group parameter into a Sieve script (@pxref{Sieve
2931 Commands}) the following Sieve code is generated:
2934 if address \"sender\" \"sieve-admin@@extundo.com\" @{
2935 fileinto \"INBOX.list.sieve\";
2939 The Sieve language is described in RFC 3028. @xref{Top, , Top, sieve,
2942 @item (@var{variable} @var{form})
2943 You can use the group parameters to set variables local to the group you
2944 are entering. If you want to turn threading off in @samp{news.answers},
2945 you could put @code{(gnus-show-threads nil)} in the group parameters of
2946 that group. @code{gnus-show-threads} will be made into a local variable
2947 in the summary buffer you enter, and the form @code{nil} will be
2948 @code{eval}ed there.
2950 @vindex gnus-list-identifiers
2951 A use for this feature, is to remove a mailing list identifier tag in
2952 the subject fields of articles. E.g. if the news group
2953 @samp{nntp+news.gnus.org:gmane.text.docbook.apps} has the tag
2954 @samp{DOC-BOOK-APPS:} in the subject of all articles, this tag can be
2955 removed from the article subjects in the summary buffer for the group by
2956 putting @code{(gnus-list-identifiers "DOCBOOK-APPS:")} into the group
2957 parameters for the group.
2960 This can also be used as a group-specific hook function, if you'd like.
2961 If you want to hear a beep when you enter a group, you could put
2962 something like @code{(dummy-variable (ding))} in the parameters of that
2963 group. @code{dummy-variable} will be set to the result of the
2964 @code{(ding)} form, but who cares?
2968 Use the @kbd{G p} or the @kbd{G c} command to edit group parameters of a
2969 group. (@kbd{G p} presents you with a Lisp-based interface, @kbd{G c}
2970 presents you with a Customize-like interface. The latter helps avoid
2971 silly Lisp errors.) You might also be interested in reading about topic
2972 parameters (@pxref{Topic Parameters}).
2974 @vindex gnus-parameters
2975 Group parameters can be set via the @code{gnus-parameters} variable too.
2976 But some variables, such as @code{visible}, have no effect. For
2980 (setq gnus-parameters
2982 (gnus-show-threads nil)
2983 (gnus-use-scoring nil)
2984 (gnus-summary-line-format
2985 "%U%R%z%I%(%[%d:%ub%-23,23f%]%) %s\n")
2989 ("^nnimap:\\(foo.bar\\)$"
2993 (gnus-use-scoring t))
2997 (broken-reply-to . t))))
3000 String value of parameters will be subjected to regexp substitution, as
3001 the @code{to-group} example shows.
3004 @node Listing Groups
3005 @section Listing Groups
3006 @cindex group listing
3008 These commands all list various slices of the groups available.
3016 @findex gnus-group-list-groups
3017 List all groups that have unread articles
3018 (@code{gnus-group-list-groups}). If the numeric prefix is used, this
3019 command will list only groups of level ARG and lower. By default, it
3020 only lists groups of level five (i. e.,
3021 @code{gnus-group-default-list-level}) or lower (i.e., just subscribed
3028 @findex gnus-group-list-all-groups
3029 List all groups, whether they have unread articles or not
3030 (@code{gnus-group-list-all-groups}). If the numeric prefix is used,
3031 this command will list only groups of level ARG and lower. By default,
3032 it lists groups of level seven or lower (i.e., just subscribed and
3033 unsubscribed groups).
3037 @findex gnus-group-list-level
3038 List all unread groups on a specific level
3039 (@code{gnus-group-list-level}). If given a prefix, also list the groups
3040 with no unread articles.
3044 @findex gnus-group-list-killed
3045 List all killed groups (@code{gnus-group-list-killed}). If given a
3046 prefix argument, really list all groups that are available, but aren't
3047 currently (un)subscribed. This could entail reading the active file
3052 @findex gnus-group-list-zombies
3053 List all zombie groups (@code{gnus-group-list-zombies}).
3057 @findex gnus-group-list-matching
3058 List all unread, subscribed groups with names that match a regexp
3059 (@code{gnus-group-list-matching}).
3063 @findex gnus-group-list-all-matching
3064 List groups that match a regexp (@code{gnus-group-list-all-matching}).
3068 @findex gnus-group-list-active
3069 List absolutely all groups in the active file(s) of the
3070 server(s) you are connected to (@code{gnus-group-list-active}). This
3071 might very well take quite a while. It might actually be a better idea
3072 to do a @kbd{A M} to list all matching, and just give @samp{.} as the
3073 thing to match on. Also note that this command may list groups that
3074 don't exist (yet)---these will be listed as if they were killed groups.
3075 Take the output with some grains of salt.
3079 @findex gnus-group-apropos
3080 List all groups that have names that match a regexp
3081 (@code{gnus-group-apropos}).
3085 @findex gnus-group-description-apropos
3086 List all groups that have names or descriptions that match a regexp
3087 (@code{gnus-group-description-apropos}).
3091 @findex gnus-group-list-cached
3092 List all groups with cached articles (@code{gnus-group-list-cached}).
3096 @findex gnus-group-list-dormant
3097 List all groups with dormant articles (@code{gnus-group-list-dormant}).
3101 @findex gnus-group-list-limit
3102 List groups limited within the current selection
3103 (@code{gnus-group-list-limit}).
3107 @findex gnus-group-list-flush
3108 Flush groups from the current selection (@code{gnus-group-list-flush}).
3112 @findex gnus-group-list-plus
3113 List groups plus the current selection (@code{gnus-group-list-plus}).
3117 @vindex gnus-permanently-visible-groups
3118 @cindex visible group parameter
3119 Groups that match the @code{gnus-permanently-visible-groups} regexp will
3120 always be shown, whether they have unread articles or not. You can also
3121 add the @code{visible} element to the group parameters in question to
3122 get the same effect.
3124 @vindex gnus-list-groups-with-ticked-articles
3125 Groups that have just ticked articles in it are normally listed in the
3126 group buffer. If @code{gnus-list-groups-with-ticked-articles} is
3127 @code{nil}, these groups will be treated just like totally empty
3128 groups. It is @code{t} by default.
3131 @node Sorting Groups
3132 @section Sorting Groups
3133 @cindex sorting groups
3135 @kindex C-c C-s (Group)
3136 @findex gnus-group-sort-groups
3137 @vindex gnus-group-sort-function
3138 The @kbd{C-c C-s} (@code{gnus-group-sort-groups}) command sorts the
3139 group buffer according to the function(s) given by the
3140 @code{gnus-group-sort-function} variable. Available sorting functions
3145 @item gnus-group-sort-by-alphabet
3146 @findex gnus-group-sort-by-alphabet
3147 Sort the group names alphabetically. This is the default.
3149 @item gnus-group-sort-by-real-name
3150 @findex gnus-group-sort-by-real-name
3151 Sort the group alphabetically on the real (unprefixed) group names.
3153 @item gnus-group-sort-by-level
3154 @findex gnus-group-sort-by-level
3155 Sort by group level.
3157 @item gnus-group-sort-by-score
3158 @findex gnus-group-sort-by-score
3159 Sort by group score. @xref{Group Score}.
3161 @item gnus-group-sort-by-rank
3162 @findex gnus-group-sort-by-rank
3163 Sort by group score and then the group level. The level and the score
3164 are, when taken together, the group's @dfn{rank}. @xref{Group Score}.
3166 @item gnus-group-sort-by-unread
3167 @findex gnus-group-sort-by-unread
3168 Sort by number of unread articles.
3170 @item gnus-group-sort-by-method
3171 @findex gnus-group-sort-by-method
3172 Sort alphabetically on the select method.
3174 @item gnus-group-sort-by-server
3175 @findex gnus-group-sort-by-server
3176 Sort alphabetically on the Gnus server name.
3181 @code{gnus-group-sort-function} can also be a list of sorting
3182 functions. In that case, the most significant sort key function must be
3186 There are also a number of commands for sorting directly according to
3187 some sorting criteria:
3191 @kindex G S a (Group)
3192 @findex gnus-group-sort-groups-by-alphabet
3193 Sort the group buffer alphabetically by group name
3194 (@code{gnus-group-sort-groups-by-alphabet}).
3197 @kindex G S u (Group)
3198 @findex gnus-group-sort-groups-by-unread
3199 Sort the group buffer by the number of unread articles
3200 (@code{gnus-group-sort-groups-by-unread}).
3203 @kindex G S l (Group)
3204 @findex gnus-group-sort-groups-by-level
3205 Sort the group buffer by group level
3206 (@code{gnus-group-sort-groups-by-level}).
3209 @kindex G S v (Group)
3210 @findex gnus-group-sort-groups-by-score
3211 Sort the group buffer by group score
3212 (@code{gnus-group-sort-groups-by-score}). @xref{Group Score}.
3215 @kindex G S r (Group)
3216 @findex gnus-group-sort-groups-by-rank
3217 Sort the group buffer by group rank
3218 (@code{gnus-group-sort-groups-by-rank}). @xref{Group Score}.
3221 @kindex G S m (Group)
3222 @findex gnus-group-sort-groups-by-method
3223 Sort the group buffer alphabetically by back end name
3224 (@code{gnus-group-sort-groups-by-method}).
3227 @kindex G S n (Group)
3228 @findex gnus-group-sort-groups-by-real-name
3229 Sort the group buffer alphabetically by real (unprefixed) group name
3230 (@code{gnus-group-sort-groups-by-real-name}).
3234 All the commands below obey the process/prefix convention
3235 (@pxref{Process/Prefix}).
3237 When given a symbolic prefix (@pxref{Symbolic Prefixes}), all these
3238 commands will sort in reverse order.
3240 You can also sort a subset of the groups:
3244 @kindex G P a (Group)
3245 @findex gnus-group-sort-selected-groups-by-alphabet
3246 Sort the groups alphabetically by group name
3247 (@code{gnus-group-sort-selected-groups-by-alphabet}).
3250 @kindex G P u (Group)
3251 @findex gnus-group-sort-selected-groups-by-unread
3252 Sort the groups by the number of unread articles
3253 (@code{gnus-group-sort-selected-groups-by-unread}).
3256 @kindex G P l (Group)
3257 @findex gnus-group-sort-selected-groups-by-level
3258 Sort the groups by group level
3259 (@code{gnus-group-sort-selected-groups-by-level}).
3262 @kindex G P v (Group)
3263 @findex gnus-group-sort-selected-groups-by-score
3264 Sort the groups by group score
3265 (@code{gnus-group-sort-selected-groups-by-score}). @xref{Group Score}.
3268 @kindex G P r (Group)
3269 @findex gnus-group-sort-selected-groups-by-rank
3270 Sort the groups by group rank
3271 (@code{gnus-group-sort-selected-groups-by-rank}). @xref{Group Score}.
3274 @kindex G P m (Group)
3275 @findex gnus-group-sort-selected-groups-by-method
3276 Sort the groups alphabetically by back end name
3277 (@code{gnus-group-sort-selected-groups-by-method}).
3280 @kindex G P n (Group)
3281 @findex gnus-group-sort-selected-groups-by-real-name
3282 Sort the groups alphabetically by real (unprefixed) group name
3283 (@code{gnus-group-sort-selected-groups-by-real-name}).
3286 @kindex G P s (Group)
3287 @findex gnus-group-sort-selected-groups
3288 Sort the groups according to @code{gnus-group-sort-function}.
3292 And finally, note that you can use @kbd{C-k} and @kbd{C-y} to manually
3296 @node Group Maintenance
3297 @section Group Maintenance
3298 @cindex bogus groups
3303 @findex gnus-group-check-bogus-groups
3304 Find bogus groups and delete them
3305 (@code{gnus-group-check-bogus-groups}).
3309 @findex gnus-group-find-new-groups
3310 Find new groups and process them (@code{gnus-group-find-new-groups}).
3311 With 1 @kbd{C-u}, use the @code{ask-server} method to query the server
3312 for new groups. With 2 @kbd{C-u}'s, use most complete method possible
3313 to query the server for new groups, and subscribe the new groups as
3317 @kindex C-c C-x (Group)
3318 @findex gnus-group-expire-articles
3319 Run all expirable articles in the current group through the expiry
3320 process (if any) (@code{gnus-group-expire-articles}). That is, delete
3321 all expirable articles in the group that have been around for a while.
3322 (@pxref{Expiring Mail}).
3325 @kindex C-c C-M-x (Group)
3326 @findex gnus-group-expire-all-groups
3327 Run all expirable articles in all groups through the expiry process
3328 (@code{gnus-group-expire-all-groups}).
3333 @node Browse Foreign Server
3334 @section Browse Foreign Server
3335 @cindex foreign servers
3336 @cindex browsing servers
3341 @findex gnus-group-browse-foreign-server
3342 You will be queried for a select method and a server name. Gnus will
3343 then attempt to contact this server and let you browse the groups there
3344 (@code{gnus-group-browse-foreign-server}).
3347 @findex gnus-browse-mode
3348 A new buffer with a list of available groups will appear. This buffer
3349 will use the @code{gnus-browse-mode}. This buffer looks a bit (well,
3350 a lot) like a normal group buffer.
3352 Here's a list of keystrokes available in the browse mode:
3357 @findex gnus-group-next-group
3358 Go to the next group (@code{gnus-group-next-group}).
3362 @findex gnus-group-prev-group
3363 Go to the previous group (@code{gnus-group-prev-group}).
3366 @kindex SPACE (Browse)
3367 @findex gnus-browse-read-group
3368 Enter the current group and display the first article
3369 (@code{gnus-browse-read-group}).
3372 @kindex RET (Browse)
3373 @findex gnus-browse-select-group
3374 Enter the current group (@code{gnus-browse-select-group}).
3378 @findex gnus-browse-unsubscribe-current-group
3379 Unsubscribe to the current group, or, as will be the case here,
3380 subscribe to it (@code{gnus-browse-unsubscribe-current-group}).
3386 @findex gnus-browse-exit
3387 Exit browse mode (@code{gnus-browse-exit}).
3391 @findex gnus-browse-describe-group
3392 Describe the current group (@code{gnus-browse-describe-group}).
3396 @findex gnus-browse-describe-briefly
3397 Describe browse mode briefly (well, there's not much to describe, is
3398 there) (@code{gnus-browse-describe-briefly}).
3403 @section Exiting Gnus
3404 @cindex exiting Gnus
3406 Yes, Gnus is ex(c)iting.
3411 @findex gnus-group-suspend
3412 Suspend Gnus (@code{gnus-group-suspend}). This doesn't really exit Gnus,
3413 but it kills all buffers except the Group buffer. I'm not sure why this
3414 is a gain, but then who am I to judge?
3418 @findex gnus-group-exit
3419 @c @icon{gnus-group-exit}
3420 Quit Gnus (@code{gnus-group-exit}).
3424 @findex gnus-group-quit
3425 Quit Gnus without saving the @file{.newsrc} files (@code{gnus-group-quit}).
3426 The dribble file will be saved, though (@pxref{Auto Save}).
3429 @vindex gnus-exit-gnus-hook
3430 @vindex gnus-suspend-gnus-hook
3431 @vindex gnus-after-exiting-gnus-hook
3432 @code{gnus-suspend-gnus-hook} is called when you suspend Gnus and
3433 @code{gnus-exit-gnus-hook} is called when you quit Gnus, while
3434 @code{gnus-after-exiting-gnus-hook} is called as the final item when
3440 Miss Lisa Cannifax, while sitting in English class, felt her feet go
3441 numbly heavy and herself fall into a hazy trance as the boy sitting
3442 behind her drew repeated lines with his pencil across the back of her
3448 @section Group Topics
3451 If you read lots and lots of groups, it might be convenient to group
3452 them hierarchically according to topics. You put your Emacs groups over
3453 here, your sex groups over there, and the rest (what, two groups or so?)
3454 you put in some misc section that you never bother with anyway. You can
3455 even group the Emacs sex groups as a sub-topic to either the Emacs
3456 groups or the sex groups---or both! Go wild!
3460 \gnusfigure{Group Topics}{400}{
3461 \put(75,50){\epsfig{figure=ps/group-topic,height=9cm}}
3472 2: alt.religion.emacs
3475 0: comp.talk.emacs.recovery
3477 8: comp.binaries.fractals
3478 13: comp.sources.unix
3481 @findex gnus-topic-mode
3483 To get this @emph{fab} functionality you simply turn on (ooh!) the
3484 @code{gnus-topic} minor mode---type @kbd{t} in the group buffer. (This
3485 is a toggling command.)
3487 Go ahead, just try it. I'll still be here when you get back. La de
3488 dum@dots{} Nice tune, that@dots{} la la la@dots{} What, you're back?
3489 Yes, and now press @kbd{l}. There. All your groups are now listed
3490 under @samp{misc}. Doesn't that make you feel all warm and fuzzy?
3493 If you want this permanently enabled, you should add that minor mode to
3494 the hook for the group mode. Put the following line in your
3495 @file{~/.gnus.el} file:
3498 (add-hook 'gnus-group-mode-hook 'gnus-topic-mode)
3502 * Topic Commands:: Interactive E-Z commands.
3503 * Topic Variables:: How to customize the topics the Lisp Way.
3504 * Topic Sorting:: Sorting each topic individually.
3505 * Topic Topology:: A map of the world.
3506 * Topic Parameters:: Parameters that apply to all groups in a topic.
3510 @node Topic Commands
3511 @subsection Topic Commands
3512 @cindex topic commands
3514 When the topic minor mode is turned on, a new @kbd{T} submap will be
3515 available. In addition, a few of the standard keys change their
3516 definitions slightly.
3518 In general, the following kinds of operations are possible on topics.
3519 First of all, you want to create topics. Secondly, you want to put
3520 groups in topics and to move them around until you have an order you
3521 like. The third kind of operation is to show/hide parts of the whole
3522 shebang. You might want to hide a topic including its subtopics and
3523 groups, to get a better overview of the other groups.
3525 Here is a list of the basic keys that you might need to set up topics
3532 @findex gnus-topic-create-topic
3533 Prompt for a new topic name and create it
3534 (@code{gnus-topic-create-topic}).
3538 @kindex T TAB (Topic)
3540 @findex gnus-topic-indent
3541 ``Indent'' the current topic so that it becomes a sub-topic of the
3542 previous topic (@code{gnus-topic-indent}). If given a prefix,
3543 ``un-indent'' the topic instead.
3546 @kindex M-TAB (Topic)
3547 @findex gnus-topic-unindent
3548 ``Un-indent'' the current topic so that it becomes a sub-topic of the
3549 parent of its current parent (@code{gnus-topic-unindent}).
3553 The following two keys can be used to move groups and topics around.
3554 They work like the well-known cut and paste. @kbd{C-k} is like cut and
3555 @kbd{C-y} is like paste. Of course, this being Emacs, we use the terms
3556 kill and yank rather than cut and paste.
3562 @findex gnus-topic-kill-group
3563 Kill a group or topic (@code{gnus-topic-kill-group}). All groups in the
3564 topic will be removed along with the topic.
3568 @findex gnus-topic-yank-group
3569 Yank the previously killed group or topic
3570 (@code{gnus-topic-yank-group}). Note that all topics will be yanked
3573 So, to move a topic to the beginning of the list of topics, just hit
3574 @kbd{C-k} on it. This is like the `cut' part of cut and paste. Then,
3575 move the cursor to the beginning of the buffer (just below the `Gnus'
3576 topic) and hit @kbd{C-y}. This is like the `paste' part of cut and
3577 paste. Like I said -- E-Z.
3579 You can use @kbd{C-k} and @kbd{C-y} on groups as well as on topics. So
3580 you can move topics around as well as groups.
3584 After setting up the topics the way you like them, you might wish to
3585 hide a topic, or to show it again. That's why we have the following
3592 @findex gnus-topic-select-group
3594 Either select a group or fold a topic (@code{gnus-topic-select-group}).
3595 When you perform this command on a group, you'll enter the group, as
3596 usual. When done on a topic line, the topic will be folded (if it was
3597 visible) or unfolded (if it was folded already). So it's basically a
3598 toggling command on topics. In addition, if you give a numerical
3599 prefix, group on that level (and lower) will be displayed.
3603 Now for a list of other commands, in no particular order.
3609 @findex gnus-topic-move-group
3610 Move the current group to some other topic
3611 (@code{gnus-topic-move-group}). This command uses the process/prefix
3612 convention (@pxref{Process/Prefix}).
3616 @findex gnus-topic-jump-to-topic
3617 Go to a topic (@code{gnus-topic-jump-to-topic}).
3621 @findex gnus-topic-copy-group
3622 Copy the current group to some other topic
3623 (@code{gnus-topic-copy-group}). This command uses the process/prefix
3624 convention (@pxref{Process/Prefix}).
3628 @findex gnus-topic-hide-topic
3629 Hide the current topic (@code{gnus-topic-hide-topic}). If given
3630 a prefix, hide the topic permanently.
3634 @findex gnus-topic-show-topic
3635 Show the current topic (@code{gnus-topic-show-topic}). If given
3636 a prefix, show the topic permanently.
3640 @findex gnus-topic-remove-group
3641 Remove a group from the current topic (@code{gnus-topic-remove-group}).
3642 This command is mainly useful if you have the same group in several
3643 topics and wish to remove it from one of the topics. You may also
3644 remove a group from all topics, but in that case, Gnus will add it to
3645 the root topic the next time you start Gnus. In fact, all new groups
3646 (which, naturally, don't belong to any topic) will show up in the root
3649 This command uses the process/prefix convention
3650 (@pxref{Process/Prefix}).
3654 @findex gnus-topic-move-matching
3655 Move all groups that match some regular expression to a topic
3656 (@code{gnus-topic-move-matching}).
3660 @findex gnus-topic-copy-matching
3661 Copy all groups that match some regular expression to a topic
3662 (@code{gnus-topic-copy-matching}).
3666 @findex gnus-topic-toggle-display-empty-topics
3667 Toggle hiding empty topics
3668 (@code{gnus-topic-toggle-display-empty-topics}).
3672 @findex gnus-topic-mark-topic
3673 Mark all groups in the current topic with the process mark
3674 (@code{gnus-topic-mark-topic}). This command works recursively on
3675 sub-topics unless given a prefix.
3678 @kindex T M-# (Topic)
3679 @findex gnus-topic-unmark-topic
3680 Remove the process mark from all groups in the current topic
3681 (@code{gnus-topic-unmark-topic}). This command works recursively on
3682 sub-topics unless given a prefix.
3685 @kindex C-c C-x (Topic)
3686 @findex gnus-topic-expire-articles
3687 Run all expirable articles in the current group or topic through the
3688 expiry process (if any)
3689 (@code{gnus-topic-expire-articles}). (@pxref{Expiring Mail}).
3693 @findex gnus-topic-rename
3694 Rename a topic (@code{gnus-topic-rename}).
3697 @kindex T DEL (Topic)
3698 @findex gnus-topic-delete
3699 Delete an empty topic (@code{gnus-topic-delete}).
3703 @findex gnus-topic-list-active
3704 List all groups that Gnus knows about in a topics-ified way
3705 (@code{gnus-topic-list-active}).
3708 @kindex T M-n (Topic)
3709 @findex gnus-topic-goto-next-topic
3710 Go to the next topic (@code{gnus-topic-goto-next-topic}).
3713 @kindex T M-p (Topic)
3714 @findex gnus-topic-goto-previous-topic
3715 Go to the next topic (@code{gnus-topic-goto-previous-topic}).
3719 @findex gnus-topic-edit-parameters
3720 @cindex group parameters
3721 @cindex topic parameters
3723 Edit the topic parameters (@code{gnus-topic-edit-parameters}).
3724 @xref{Topic Parameters}.
3729 @node Topic Variables
3730 @subsection Topic Variables
3731 @cindex topic variables
3733 The previous section told you how to tell Gnus which topics to display.
3734 This section explains how to tell Gnus what to display about each topic.
3736 @vindex gnus-topic-line-format
3737 The topic lines themselves are created according to the
3738 @code{gnus-topic-line-format} variable (@pxref{Formatting Variables}).
3751 Number of groups in the topic.
3753 Number of unread articles in the topic.
3755 Number of unread articles in the topic and all its subtopics.
3758 @vindex gnus-topic-indent-level
3759 Each sub-topic (and the groups in the sub-topics) will be indented with
3760 @code{gnus-topic-indent-level} times the topic level number of spaces.
3763 @vindex gnus-topic-mode-hook
3764 @code{gnus-topic-mode-hook} is called in topic minor mode buffers.
3766 @vindex gnus-topic-display-empty-topics
3767 The @code{gnus-topic-display-empty-topics} says whether to display even
3768 topics that have no unread articles in them. The default is @code{t}.
3772 @subsection Topic Sorting
3773 @cindex topic sorting
3775 You can sort the groups in each topic individually with the following
3781 @kindex T S a (Topic)
3782 @findex gnus-topic-sort-groups-by-alphabet
3783 Sort the current topic alphabetically by group name
3784 (@code{gnus-topic-sort-groups-by-alphabet}).
3787 @kindex T S u (Topic)
3788 @findex gnus-topic-sort-groups-by-unread
3789 Sort the current topic by the number of unread articles
3790 (@code{gnus-topic-sort-groups-by-unread}).
3793 @kindex T S l (Topic)
3794 @findex gnus-topic-sort-groups-by-level
3795 Sort the current topic by group level
3796 (@code{gnus-topic-sort-groups-by-level}).
3799 @kindex T S v (Topic)
3800 @findex gnus-topic-sort-groups-by-score
3801 Sort the current topic by group score
3802 (@code{gnus-topic-sort-groups-by-score}). @xref{Group Score}.
3805 @kindex T S r (Topic)
3806 @findex gnus-topic-sort-groups-by-rank
3807 Sort the current topic by group rank
3808 (@code{gnus-topic-sort-groups-by-rank}). @xref{Group Score}.
3811 @kindex T S m (Topic)
3812 @findex gnus-topic-sort-groups-by-method
3813 Sort the current topic alphabetically by back end name
3814 (@code{gnus-topic-sort-groups-by-method}).
3817 @kindex T S e (Topic)
3818 @findex gnus-topic-sort-groups-by-server
3819 Sort the current topic alphabetically by server name
3820 (@code{gnus-topic-sort-groups-by-server}).
3824 @findex gnus-topic-sort-groups
3825 Sort the current topic according to the function(s) given by the
3826 @code{gnus-group-sort-function} variable
3827 (@code{gnus-topic-sort-groups}).
3831 When given a prefix argument, all these commands will sort in reverse
3832 order. @xref{Sorting Groups}, for more information about group
3836 @node Topic Topology
3837 @subsection Topic Topology
3838 @cindex topic topology
3841 So, let's have a look at an example group buffer:
3847 2: alt.religion.emacs
3850 0: comp.talk.emacs.recovery
3852 8: comp.binaries.fractals
3853 13: comp.sources.unix
3856 So, here we have one top-level topic (@samp{Gnus}), two topics under
3857 that, and one sub-topic under one of the sub-topics. (There is always
3858 just one (1) top-level topic). This topology can be expressed as
3863 (("Emacs -- I wuw it!" visible)
3864 (("Naughty Emacs" visible)))
3868 @vindex gnus-topic-topology
3869 This is in fact how the variable @code{gnus-topic-topology} would look
3870 for the display above. That variable is saved in the @file{.newsrc.eld}
3871 file, and shouldn't be messed with manually---unless you really want
3872 to. Since this variable is read from the @file{.newsrc.eld} file,
3873 setting it in any other startup files will have no effect.
3875 This topology shows what topics are sub-topics of what topics (right),
3876 and which topics are visible. Two settings are currently
3877 allowed---@code{visible} and @code{invisible}.
3880 @node Topic Parameters
3881 @subsection Topic Parameters
3882 @cindex topic parameters
3884 All groups in a topic will inherit group parameters from the parent (and
3885 ancestor) topic parameters. All valid group parameters are valid topic
3886 parameters (@pxref{Group Parameters}).
3888 In addition, the following parameters are only valid as topic
3893 When subscribing new groups by topic (@pxref{Subscription Methods}), the
3894 @code{subscribe} topic parameter says what groups go in what topic. Its
3895 value should be a regexp to match the groups that should go in that
3898 @item subscribe-level
3899 When subscribing new groups by topic (see the @code{subscribe} parameter),
3900 the group will be subscribed with the level specified in the
3901 @code{subscribe-level} instead of @code{gnus-level-default-subscribed}.
3905 Group parameters (of course) override topic parameters, and topic
3906 parameters in sub-topics override topic parameters in super-topics. You
3907 know. Normal inheritance rules. (@dfn{Rules} is here a noun, not a
3908 verb, although you may feel free to disagree with me here.)
3914 2: alt.religion.emacs
3918 0: comp.talk.emacs.recovery
3920 8: comp.binaries.fractals
3921 13: comp.sources.unix
3925 The @samp{Emacs} topic has the topic parameter @code{(score-file
3926 . "emacs.SCORE")}; the @samp{Relief} topic has the topic parameter
3927 @code{(score-file . "relief.SCORE")}; and the @samp{Misc} topic has the
3928 topic parameter @code{(score-file . "emacs.SCORE")}. In addition,
3929 @* @samp{alt.religion.emacs} has the group parameter @code{(score-file
3930 . "religion.SCORE")}.
3932 Now, when you enter @samp{alt.sex.emacs} in the @samp{Relief} topic, you
3933 will get the @file{relief.SCORE} home score file. If you enter the same
3934 group in the @samp{Emacs} topic, you'll get the @file{emacs.SCORE} home
3935 score file. If you enter the group @samp{alt.religion.emacs}, you'll
3936 get the @file{religion.SCORE} home score file.
3938 This seems rather simple and self-evident, doesn't it? Well, yes. But
3939 there are some problems, especially with the @code{total-expiry}
3940 parameter. Say you have a mail group in two topics; one with
3941 @code{total-expiry} and one without. What happens when you do @kbd{M-x
3942 gnus-expire-all-expirable-groups}? Gnus has no way of telling which one
3943 of these topics you mean to expire articles from, so anything may
3944 happen. In fact, I hereby declare that it is @dfn{undefined} what
3945 happens. You just have to be careful if you do stuff like that.
3948 @node Misc Group Stuff
3949 @section Misc Group Stuff
3952 * Scanning New Messages:: Asking Gnus to see whether new messages have arrived.
3953 * Group Information:: Information and help on groups and Gnus.
3954 * Group Timestamp:: Making Gnus keep track of when you last read a group.
3955 * File Commands:: Reading and writing the Gnus files.
3956 * Sieve Commands:: Managing Sieve scripts.
3963 @findex gnus-group-enter-server-mode
3964 Enter the server buffer (@code{gnus-group-enter-server-mode}).
3965 @xref{Server Buffer}.
3969 @findex gnus-group-post-news
3970 Start composing a message (a news by default)
3971 (@code{gnus-group-post-news}). If given a prefix, post to the group
3972 under the point. If the prefix is 1, prompt for a group to post to.
3973 Contrary to what the name of this function suggests, the prepared
3974 article might be a mail instead of a news, if a mail group is specified
3975 with the prefix argument. @xref{Composing Messages}.
3979 @findex gnus-group-mail
3980 Mail a message somewhere (@code{gnus-group-mail}). If given a prefix,
3981 use the posting style of the group under the point. If the prefix is 1,
3982 prompt for a group name to find the posting style.
3983 @xref{Composing Messages}.
3987 @findex gnus-group-news
3988 Start composing a news (@code{gnus-group-news}). If given a prefix,
3989 post to the group under the point. If the prefix is 1, prompt
3990 for group to post to. @xref{Composing Messages}.
3992 This function actually prepares a news even when using mail groups.
3993 This is useful for ``posting'' messages to mail groups without actually
3994 sending them over the network: they're just saved directly to the group
3995 in question. The corresponding back end must have a request-post method
3996 for this to work though.
4000 Variables for the group buffer:
4004 @item gnus-group-mode-hook
4005 @vindex gnus-group-mode-hook
4006 is called after the group buffer has been
4009 @item gnus-group-prepare-hook
4010 @vindex gnus-group-prepare-hook
4011 is called after the group buffer is
4012 generated. It may be used to modify the buffer in some strange,
4015 @item gnus-group-prepared-hook
4016 @vindex gnus-group-prepare-hook
4017 is called as the very last thing after the group buffer has been
4018 generated. It may be used to move point around, for instance.
4020 @item gnus-permanently-visible-groups
4021 @vindex gnus-permanently-visible-groups
4022 Groups matching this regexp will always be listed in the group buffer,
4023 whether they are empty or not.
4025 @item gnus-group-name-charset-method-alist
4026 @vindex gnus-group-name-charset-method-alist
4027 An alist of method and the charset for group names. It is used to show
4028 non-ASCII group names.
4032 (setq gnus-group-name-charset-method-alist
4033 '(((nntp "news.com.cn") . cn-gb-2312)))
4036 @item gnus-group-name-charset-group-alist
4037 @cindex UTF-8 group names
4038 @vindex gnus-group-name-charset-group-alist
4039 An alist of regexp of group name and the charset for group names. It
4040 is used to show non-ASCII group names. @code{((".*" utf-8))} is the
4041 default value if UTF-8 is supported, otherwise the default is
4046 (setq gnus-group-name-charset-group-alist
4047 '(("\\.com\\.cn:" . cn-gb-2312)))
4052 @node Scanning New Messages
4053 @subsection Scanning New Messages
4054 @cindex new messages
4055 @cindex scanning new news
4061 @findex gnus-group-get-new-news
4062 @c @icon{gnus-group-get-new-news}
4063 Check the server(s) for new articles. If the numerical prefix is used,
4064 this command will check only groups of level @var{arg} and lower
4065 (@code{gnus-group-get-new-news}). If given a non-numerical prefix, this
4066 command will force a total re-reading of the active file(s) from the
4071 @findex gnus-group-get-new-news-this-group
4072 @vindex gnus-goto-next-group-when-activating
4073 @c @icon{gnus-group-get-new-news-this-group}
4074 Check whether new articles have arrived in the current group
4075 (@code{gnus-group-get-new-news-this-group}).
4076 @code{gnus-goto-next-group-when-activating} says whether this command is
4077 to move point to the next group or not. It is @code{t} by default.
4079 @findex gnus-activate-all-groups
4080 @cindex activating groups
4082 @kindex C-c M-g (Group)
4083 Activate absolutely all groups (@code{gnus-activate-all-groups}).
4088 @findex gnus-group-restart
4089 Restart Gnus (@code{gnus-group-restart}). This saves the @file{.newsrc}
4090 file(s), closes the connection to all servers, clears up all run-time
4091 Gnus variables, and then starts Gnus all over again.
4095 @vindex gnus-get-new-news-hook
4096 @code{gnus-get-new-news-hook} is run just before checking for new news.
4098 @vindex gnus-after-getting-new-news-hook
4099 @code{gnus-after-getting-new-news-hook} is run after checking for new
4103 @node Group Information
4104 @subsection Group Information
4105 @cindex group information
4106 @cindex information on groups
4113 @findex gnus-group-fetch-faq
4114 @vindex gnus-group-faq-directory
4117 Try to fetch the FAQ for the current group
4118 (@code{gnus-group-fetch-faq}). Gnus will try to get the FAQ from
4119 @code{gnus-group-faq-directory}, which is usually a directory on a
4120 remote machine. This variable can also be a list of directories. In
4121 that case, giving a prefix to this command will allow you to choose
4122 between the various sites. @code{ange-ftp} (or @code{efs}) will be used
4123 for fetching the file.
4125 If fetching from the first site is unsuccessful, Gnus will attempt to go
4126 through @code{gnus-group-faq-directory} and try to open them one by one.
4130 @findex gnus-group-fetch-charter
4131 @vindex gnus-group-charter-alist
4133 Try to open the charter for the current group in a web browser
4134 (@code{gnus-group-fetch-charter}). Query for a group if given a
4137 Gnus will use @code{gnus-group-charter-alist} to find the location of
4138 the charter. If no location is known, Gnus will fetch the control
4139 messages for the group, which in some cases includes the charter.
4143 @findex gnus-group-fetch-control
4144 @vindex gnus-group-fetch-control-use-browse-url
4145 @cindex control message
4146 Fetch the control messages for the group from the archive at
4147 @code{ftp.isc.org} (@code{gnus-group-fetch-control}). Query for a
4148 group if given a prefix argument.
4150 If @code{gnus-group-fetch-control-use-browse-url} is non-@code{nil},
4151 Gnus will open the control messages in a browser using
4152 @code{browse-url}. Otherwise they are fetched using @code{ange-ftp}
4153 and displayed in an ephemeral group.
4155 Note that the control messages are compressed. To use this command
4156 you need to turn on @code{auto-compression-mode} (@pxref{Compressed
4157 Files, ,Compressed Files, emacs, The Emacs Manual}).
4161 @c @icon{gnus-group-describe-group}
4163 @kindex C-c C-d (Group)
4164 @cindex describing groups
4165 @cindex group description
4166 @findex gnus-group-describe-group
4167 Describe the current group (@code{gnus-group-describe-group}). If given
4168 a prefix, force Gnus to re-read the description from the server.
4172 @findex gnus-group-describe-all-groups
4173 Describe all groups (@code{gnus-group-describe-all-groups}). If given a
4174 prefix, force Gnus to re-read the description file from the server.
4181 @findex gnus-version
4182 Display current Gnus version numbers (@code{gnus-version}).
4186 @findex gnus-group-describe-briefly
4187 Give a very short help message (@code{gnus-group-describe-briefly}).
4190 @kindex C-c C-i (Group)
4193 @findex gnus-info-find-node
4194 Go to the Gnus info node (@code{gnus-info-find-node}).
4198 @node Group Timestamp
4199 @subsection Group Timestamp
4201 @cindex group timestamps
4203 It can be convenient to let Gnus keep track of when you last read a
4204 group. To set the ball rolling, you should add
4205 @code{gnus-group-set-timestamp} to @code{gnus-select-group-hook}:
4208 (add-hook 'gnus-select-group-hook 'gnus-group-set-timestamp)
4211 After doing this, each time you enter a group, it'll be recorded.
4213 This information can be displayed in various ways---the easiest is to
4214 use the @samp{%d} spec in the group line format:
4217 (setq gnus-group-line-format
4218 "%M\%S\%p\%P\%5y: %(%-40,40g%) %d\n")
4221 This will result in lines looking like:
4224 * 0: mail.ding 19961002T012943
4225 0: custom 19961002T012713
4228 As you can see, the date is displayed in compact ISO 8601 format. This
4229 may be a bit too much, so to just display the date, you could say
4233 (setq gnus-group-line-format
4234 "%M\%S\%p\%P\%5y: %(%-40,40g%) %6,6~(cut 2)d\n")
4237 If you would like greater control of the time format, you can use a
4238 user-defined format spec. Something like the following should do the
4242 (setq gnus-group-line-format
4243 "%M\%S\%p\%P\%5y: %(%-40,40g%) %ud\n")
4244 (defun gnus-user-format-function-d (headers)
4245 (let ((time (gnus-group-timestamp gnus-tmp-group)))
4247 (format-time-string "%b %d %H:%M" time)
4253 @subsection File Commands
4254 @cindex file commands
4260 @findex gnus-group-read-init-file
4261 @vindex gnus-init-file
4262 @cindex reading init file
4263 Re-read the init file (@code{gnus-init-file}, which defaults to
4264 @file{~/.gnus.el}) (@code{gnus-group-read-init-file}).
4268 @findex gnus-group-save-newsrc
4269 @cindex saving .newsrc
4270 Save the @file{.newsrc.eld} file (and @file{.newsrc} if wanted)
4271 (@code{gnus-group-save-newsrc}). If given a prefix, force saving the
4272 file(s) whether Gnus thinks it is necessary or not.
4275 @c @kindex Z (Group)
4276 @c @findex gnus-group-clear-dribble
4277 @c Clear the dribble buffer (@code{gnus-group-clear-dribble}).
4282 @node Sieve Commands
4283 @subsection Sieve Commands
4284 @cindex group sieve commands
4286 Sieve is a server-side mail filtering language. In Gnus you can use
4287 the @code{sieve} group parameter (@pxref{Group Parameters}) to specify
4288 sieve rules that should apply to each group. Gnus provides two
4289 commands to translate all these group parameters into a proper Sieve
4290 script that can be transfered to the server somehow.
4292 @vindex gnus-sieve-file
4293 @vindex gnus-sieve-region-start
4294 @vindex gnus-sieve-region-end
4295 The generated Sieve script is placed in @code{gnus-sieve-file} (by
4296 default @file{~/.sieve}). The Sieve code that Gnus generate is placed
4297 between two delimiters, @code{gnus-sieve-region-start} and
4298 @code{gnus-sieve-region-end}, so you may write additional Sieve code
4299 outside these delimiters that will not be removed the next time you
4300 regenerate the Sieve script.
4302 @vindex gnus-sieve-crosspost
4303 The variable @code{gnus-sieve-crosspost} controls how the Sieve script
4304 is generated. If it is non-@code{nil} (the default) articles is
4305 placed in all groups that have matching rules, otherwise the article
4306 is only placed in the group with the first matching rule. For
4307 example, the group parameter @samp{(sieve address "sender"
4308 "owner-ding@@hpc.uh.edu")} will generate the following piece of Sieve
4309 code if @code{gnus-sieve-crosspost} is @code{nil}. (When
4310 @code{gnus-sieve-crosspost} is non-@code{nil}, it looks the same
4311 except that the line containing the call to @code{stop} is removed.)
4314 if address "sender" "owner-ding@@hpc.uh.edu" @{
4315 fileinto "INBOX.ding";
4320 @xref{Top, ,Top, sieve, Emacs Sieve}.
4326 @findex gnus-sieve-generate
4327 @vindex gnus-sieve-file
4328 @cindex generating sieve script
4329 Regenerate a Sieve script from the @code{sieve} group parameters and
4330 put you into the @code{gnus-sieve-file} without saving it.
4334 @findex gnus-sieve-update
4335 @vindex gnus-sieve-file
4336 @cindex updating sieve script
4337 Regenerates the Gnus managed part of @code{gnus-sieve-file} using the
4338 @code{sieve} group parameters, save the file and upload it to the
4339 server using the @code{sieveshell} program.
4344 @node Summary Buffer
4345 @chapter Summary Buffer
4346 @cindex summary buffer
4348 A line for each article is displayed in the summary buffer. You can
4349 move around, read articles, post articles and reply to articles.
4351 The most common way to a summary buffer is to select a group from the
4352 group buffer (@pxref{Selecting a Group}).
4354 You can have as many summary buffers open as you wish.
4357 * Summary Buffer Format:: Deciding how the summary buffer is to look.
4358 * Summary Maneuvering:: Moving around the summary buffer.
4359 * Choosing Articles:: Reading articles.
4360 * Paging the Article:: Scrolling the current article.
4361 * Reply Followup and Post:: Posting articles.
4362 * Delayed Articles:: Send articles at a later time.
4363 * Marking Articles:: Marking articles as read, expirable, etc.
4364 * Limiting:: You can limit the summary buffer.
4365 * Threading:: How threads are made.
4366 * Sorting the Summary Buffer:: How articles and threads are sorted.
4367 * Asynchronous Fetching:: Gnus might be able to pre-fetch articles.
4368 * Article Caching:: You may store articles in a cache.
4369 * Persistent Articles:: Making articles expiry-resistant.
4370 * Article Backlog:: Having already read articles hang around.
4371 * Saving Articles:: Ways of customizing article saving.
4372 * Decoding Articles:: Gnus can treat series of (uu)encoded articles.
4373 * Article Treatment:: The article buffer can be mangled at will.
4374 * MIME Commands:: Doing MIMEy things with the articles.
4375 * Charsets:: Character set issues.
4376 * Article Commands:: Doing various things with the article buffer.
4377 * Summary Sorting:: Sorting the summary buffer in various ways.
4378 * Finding the Parent:: No child support? Get the parent.
4379 * Alternative Approaches:: Reading using non-default summaries.
4380 * Tree Display:: A more visual display of threads.
4381 * Mail Group Commands:: Some commands can only be used in mail groups.
4382 * Various Summary Stuff:: What didn't fit anywhere else.
4383 * Exiting the Summary Buffer:: Returning to the Group buffer,
4384 or reselecting the current group.
4385 * Crosspost Handling:: How crossposted articles are dealt with.
4386 * Duplicate Suppression:: An alternative when crosspost handling fails.
4387 * Security:: Decrypt and Verify.
4388 * Mailing List:: Mailing list minor mode.
4392 @node Summary Buffer Format
4393 @section Summary Buffer Format
4394 @cindex summary buffer format
4398 \gnusfigure{The Summary Buffer}{180}{
4399 \put(0,0){\epsfig{figure=ps/summary,width=7.5cm}}
4400 \put(445,0){\makebox(0,0)[br]{\epsfig{figure=ps/summary-article,width=7.5cm}}}
4406 * Summary Buffer Lines:: You can specify how summary lines should look.
4407 * To From Newsgroups:: How to not display your own name.
4408 * Summary Buffer Mode Line:: You can say how the mode line should look.
4409 * Summary Highlighting:: Making the summary buffer all pretty and nice.
4412 @findex mail-extract-address-components
4413 @findex gnus-extract-address-components
4414 @vindex gnus-extract-address-components
4415 Gnus will use the value of the @code{gnus-extract-address-components}
4416 variable as a function for getting the name and address parts of a
4417 @code{From} header. Two pre-defined functions exist:
4418 @code{gnus-extract-address-components}, which is the default, quite
4419 fast, and too simplistic solution; and
4420 @code{mail-extract-address-components}, which works very nicely, but is
4421 slower. The default function will return the wrong answer in 5% of the
4422 cases. If this is unacceptable to you, use the other function instead:
4425 (setq gnus-extract-address-components
4426 'mail-extract-address-components)
4429 @vindex gnus-summary-same-subject
4430 @code{gnus-summary-same-subject} is a string indicating that the current
4431 article has the same subject as the previous. This string will be used
4432 with those specs that require it. The default is @code{""}.
4435 @node Summary Buffer Lines
4436 @subsection Summary Buffer Lines
4438 @vindex gnus-summary-line-format
4439 You can change the format of the lines in the summary buffer by changing
4440 the @code{gnus-summary-line-format} variable. It works along the same
4441 lines as a normal @code{format} string, with some extensions
4442 (@pxref{Formatting Variables}).
4444 There should always be a colon or a point position marker on the line;
4445 the cursor always moves to the point position marker or the colon after
4446 performing an operation. (Of course, Gnus wouldn't be Gnus if it wasn't
4447 possible to change this. Just write a new function
4448 @code{gnus-goto-colon} which does whatever you like with the cursor.)
4449 @xref{Positioning Point}.
4451 The default string is @samp{%U%R%z%I%(%[%4L: %-23,23f%]%) %s\n}.
4453 The following format specification characters and extended format
4454 specification(s) are understood:
4460 Subject string. List identifiers stripped,
4461 @code{gnus-list-identifies}. @xref{Article Hiding}.
4463 Subject if the article is the root of the thread or the previous article
4464 had a different subject, @code{gnus-summary-same-subject} otherwise.
4465 (@code{gnus-summary-same-subject} defaults to @code{""}.)
4467 Full @code{From} header.
4469 The name (from the @code{From} header).
4471 The name, @code{To} header or the @code{Newsgroups} header (@pxref{To
4474 The name (from the @code{From} header). This differs from the @code{n}
4475 spec in that it uses the function designated by the
4476 @code{gnus-extract-address-components} variable, which is slower, but
4477 may be more thorough.
4479 The address (from the @code{From} header). This works the same way as
4482 Number of lines in the article.
4484 Number of characters in the article. This specifier is not supported
4485 in some methods (like nnfolder).
4487 Pretty-printed version of the number of characters in the article;
4488 for example, @samp{1.2k} or @samp{0.4M}.
4490 Indentation based on thread level (@pxref{Customizing Threading}).
4492 A complex trn-style thread tree, showing response-connecting trace
4493 lines. A thread could be drawn like this:
4506 You can customize the appearance with the following options. Note
4507 that it is possible to make the thread display look really neat by
4508 replacing the default ASCII characters with graphic line-drawing
4511 @item gnus-sum-thread-tree-root
4512 @vindex gnus-sum-thread-tree-root
4513 Used for the root of a thread. If @code{nil}, use subject
4514 instead. The default is @samp{> }.
4516 @item gnus-sum-thread-tree-single-indent
4517 @vindex gnus-sum-thread-tree-single-indent
4518 Used for a thread with just one message. If @code{nil}, use subject
4519 instead. The default is @samp{}.
4521 @item gnus-sum-thread-tree-vertical
4522 @vindex gnus-sum-thread-tree-vertical
4523 Used for drawing a vertical line. The default is @samp{| }.
4525 @item gnus-sum-thread-tree-indent
4526 @vindex gnus-sum-thread-tree-indent
4527 Used for indenting. The default is @samp{ }.
4529 @item gnus-sum-thread-tree-leaf-with-other
4530 @vindex gnus-sum-thread-tree-leaf-with-other
4531 Used for a leaf with brothers. The default is @samp{+-> }.
4533 @item gnus-sum-thread-tree-single-leaf
4534 @vindex gnus-sum-thread-tree-single-leaf
4535 Used for a leaf without brothers. The default is @samp{\-> }
4540 Nothing if the article is a root and lots of spaces if it isn't (it
4541 pushes everything after it off the screen).
4543 Opening bracket, which is normally @samp{[}, but can also be @samp{<}
4544 for adopted articles (@pxref{Customizing Threading}).
4546 Closing bracket, which is normally @samp{]}, but can also be @samp{>}
4547 for adopted articles.
4549 One space for each thread level.
4551 Twenty minus thread level spaces.
4553 Unread. @xref{Read Articles}.
4556 This misleadingly named specifier is the @dfn{secondary mark}. This
4557 mark will say whether the article has been replied to, has been cached,
4558 or has been saved. @xref{Other Marks}.
4561 Score as a number (@pxref{Scoring}).
4563 @vindex gnus-summary-zcore-fuzz
4564 Zcore, @samp{+} if above the default level and @samp{-} if below the
4565 default level. If the difference between
4566 @code{gnus-summary-default-score} and the score is less than
4567 @code{gnus-summary-zcore-fuzz}, this spec will not be used.
4575 The @code{Date} in @code{DD-MMM} format.
4577 The @code{Date} in @var{YYYYMMDD}@code{T}@var{HHMMSS} format.
4583 Number of articles in the current sub-thread. Using this spec will slow
4584 down summary buffer generation somewhat.
4586 An @samp{=} (@code{gnus-not-empty-thread-mark}) will be displayed if the
4587 article has any children.
4593 Age sensitive date format. Various date format is defined in
4594 @code{gnus-user-date-format-alist}.
4596 User defined specifier. The next character in the format string should
4597 be a letter. Gnus will call the function
4598 @code{gnus-user-format-function-}@samp{X}, where @samp{X} is the letter
4599 following @samp{%u}. The function will be passed the current header as
4600 argument. The function should return a string, which will be inserted
4601 into the summary just like information from any other summary specifier.
4604 Text between @samp{%(} and @samp{%)} will be highlighted with
4605 @code{gnus-mouse-face} when the mouse point is placed inside the area.
4606 There can only be one such area.
4608 The @samp{%U} (status), @samp{%R} (replied) and @samp{%z} (zcore) specs
4609 have to be handled with care. For reasons of efficiency, Gnus will
4610 compute what column these characters will end up in, and ``hard-code''
4611 that. This means that it is invalid to have these specs after a
4612 variable-length spec. Well, you might not be arrested, but your summary
4613 buffer will look strange, which is bad enough.
4615 The smart choice is to have these specs as far to the left as possible.
4616 (Isn't that the case with everything, though? But I digress.)
4618 This restriction may disappear in later versions of Gnus.
4621 @node To From Newsgroups
4622 @subsection To From Newsgroups
4626 In some groups (particularly in archive groups), the @code{From} header
4627 isn't very interesting, since all the articles there are written by
4628 you. To display the information in the @code{To} or @code{Newsgroups}
4629 headers instead, you need to decide three things: What information to
4630 gather; where to display it; and when to display it.
4634 @vindex gnus-extra-headers
4635 The reading of extra header information is controlled by the
4636 @code{gnus-extra-headers}. This is a list of header symbols. For
4640 (setq gnus-extra-headers
4641 '(To Newsgroups X-Newsreader))
4644 This will result in Gnus trying to obtain these three headers, and
4645 storing it in header structures for later easy retrieval.
4648 @findex gnus-extra-header
4649 The value of these extra headers can be accessed via the
4650 @code{gnus-extra-header} function. Here's a format line spec that will
4651 access the @code{X-Newsreader} header:
4654 "%~(form (gnus-extra-header 'X-Newsreader))@@"
4658 @vindex gnus-ignored-from-addresses
4659 The @code{gnus-ignored-from-addresses} variable says when the @samp{%f}
4660 summary line spec returns the @code{To}, @code{Newsreader} or
4661 @code{From} header. If this regexp matches the contents of the
4662 @code{From} header, the value of the @code{To} or @code{Newsreader}
4663 headers are used instead.
4667 @vindex nnmail-extra-headers
4668 A related variable is @code{nnmail-extra-headers}, which controls when
4669 to include extra headers when generating overview (@sc{nov}) files.
4670 If you have old overview files, you should regenerate them after
4671 changing this variable, by entering the server buffer using @kbd{^},
4672 and then @kbd{g} on the appropriate mail server (e.g. nnml) to cause
4675 @vindex gnus-summary-line-format
4676 You also have to instruct Gnus to display the data by changing the
4677 @code{%n} spec to the @code{%f} spec in the
4678 @code{gnus-summary-line-format} variable.
4680 In summary, you'd typically put something like the following in
4684 (setq gnus-extra-headers
4686 (setq nnmail-extra-headers gnus-extra-headers)
4687 (setq gnus-summary-line-format
4688 "%U%R%z%I%(%[%4L: %-23,23f%]%) %s\n")
4689 (setq gnus-ignored-from-addresses
4693 (The values listed above are the default values in Gnus. Alter them
4696 A note for news server administrators, or for users who wish to try to
4697 convince their news server administrator to provide some additional
4700 The above is mostly useful for mail groups, where you have control over
4701 the @sc{nov} files that are created. However, if you can persuade your
4702 nntp admin to add (in the usual implementation, notably INN):
4708 to the end of her @file{overview.fmt} file, then you can use that just
4709 as you would the extra headers from the mail groups.
4712 @node Summary Buffer Mode Line
4713 @subsection Summary Buffer Mode Line
4715 @vindex gnus-summary-mode-line-format
4716 You can also change the format of the summary mode bar (@pxref{Mode Line
4717 Formatting}). Set @code{gnus-summary-mode-line-format} to whatever you
4718 like. The default is @samp{Gnus: %%b [%A] %Z}.
4720 Here are the elements you can play with:
4726 Unprefixed group name.
4728 Current article number.
4730 Current article score.
4734 Number of unread articles in this group.
4736 Number of unread articles in this group that aren't displayed in the
4739 A string with the number of unread and unselected articles represented
4740 either as @samp{<%U(+%e) more>} if there are both unread and unselected
4741 articles, and just as @samp{<%U more>} if there are just unread articles
4742 and no unselected ones.
4744 Shortish group name. For instance, @samp{rec.arts.anime} will be
4745 shortened to @samp{r.a.anime}.
4747 Subject of the current article.
4749 User-defined spec (@pxref{User-Defined Specs}).
4751 Name of the current score file (@pxref{Scoring}).
4753 Number of dormant articles (@pxref{Unread Articles}).
4755 Number of ticked articles (@pxref{Unread Articles}).
4757 Number of articles that have been marked as read in this session.
4759 Number of articles expunged by the score files.
4763 @node Summary Highlighting
4764 @subsection Summary Highlighting
4768 @item gnus-visual-mark-article-hook
4769 @vindex gnus-visual-mark-article-hook
4770 This hook is run after selecting an article. It is meant to be used for
4771 highlighting the article in some way. It is not run if
4772 @code{gnus-visual} is @code{nil}.
4774 @item gnus-summary-update-hook
4775 @vindex gnus-summary-update-hook
4776 This hook is called when a summary line is changed. It is not run if
4777 @code{gnus-visual} is @code{nil}.
4779 @item gnus-summary-selected-face
4780 @vindex gnus-summary-selected-face
4781 This is the face (or @dfn{font} as some people call it) used to
4782 highlight the current article in the summary buffer.
4784 @item gnus-summary-highlight
4785 @vindex gnus-summary-highlight
4786 Summary lines are highlighted according to this variable, which is a
4787 list where the elements are of the format @code{(@var{form}
4788 . @var{face})}. If you would, for instance, like ticked articles to be
4789 italic and high-scored articles to be bold, you could set this variable
4792 (((eq mark gnus-ticked-mark) . italic)
4793 ((> score default) . bold))
4795 As you may have guessed, if @var{form} returns a non-@code{nil} value,
4796 @var{face} will be applied to the line.
4800 @node Summary Maneuvering
4801 @section Summary Maneuvering
4802 @cindex summary movement
4804 All the straight movement commands understand the numeric prefix and
4805 behave pretty much as you'd expect.
4807 None of these commands select articles.
4812 @kindex M-n (Summary)
4813 @kindex G M-n (Summary)
4814 @findex gnus-summary-next-unread-subject
4815 Go to the next summary line of an unread article
4816 (@code{gnus-summary-next-unread-subject}).
4820 @kindex M-p (Summary)
4821 @kindex G M-p (Summary)
4822 @findex gnus-summary-prev-unread-subject
4823 Go to the previous summary line of an unread article
4824 (@code{gnus-summary-prev-unread-subject}).
4827 @kindex G g (Summary)
4828 @findex gnus-summary-goto-subject
4829 Ask for an article number and then go to the summary line of that article
4830 without displaying the article (@code{gnus-summary-goto-subject}).
4833 If Gnus asks you to press a key to confirm going to the next group, you
4834 can use the @kbd{C-n} and @kbd{C-p} keys to move around the group
4835 buffer, searching for the next group to read without actually returning
4836 to the group buffer.
4838 Variables related to summary movement:
4842 @vindex gnus-auto-select-next
4843 @item gnus-auto-select-next
4844 If you issue one of the movement commands (like @kbd{n}) and there are
4845 no more unread articles after the current one, Gnus will offer to go to
4846 the next group. If this variable is @code{t} and the next group is
4847 empty, Gnus will exit summary mode and return to the group buffer. If
4848 this variable is neither @code{t} nor @code{nil}, Gnus will select the
4849 next group with unread articles. As a special case, if this variable
4850 is @code{quietly}, Gnus will select the next group without asking for
4851 confirmation. If this variable is @code{almost-quietly}, the same
4852 will happen only if you are located on the last article in the group.
4853 Finally, if this variable is @code{slightly-quietly}, the @kbd{Z n}
4854 command will go to the next group without confirmation. Also
4855 @pxref{Group Levels}.
4857 @item gnus-auto-select-same
4858 @vindex gnus-auto-select-same
4859 If non-@code{nil}, all the movement commands will try to go to the next
4860 article with the same subject as the current. (@dfn{Same} here might
4861 mean @dfn{roughly equal}. See @code{gnus-summary-gather-subject-limit}
4862 for details (@pxref{Customizing Threading}).) If there are no more
4863 articles with the same subject, go to the first unread article.
4865 This variable is not particularly useful if you use a threaded display.
4867 @item gnus-summary-check-current
4868 @vindex gnus-summary-check-current
4869 If non-@code{nil}, all the ``unread'' movement commands will not proceed
4870 to the next (or previous) article if the current article is unread.
4871 Instead, they will choose the current article.
4873 @item gnus-auto-center-summary
4874 @vindex gnus-auto-center-summary
4875 If non-@code{nil}, Gnus will keep the point in the summary buffer
4876 centered at all times. This makes things quite tidy, but if you have a
4877 slow network connection, or simply do not like this un-Emacsism, you can
4878 set this variable to @code{nil} to get the normal Emacs scrolling
4879 action. This will also inhibit horizontal re-centering of the summary
4880 buffer, which might make it more inconvenient to read extremely long
4883 This variable can also be a number. In that case, center the window at
4884 the given number of lines from the top.
4889 @node Choosing Articles
4890 @section Choosing Articles
4891 @cindex selecting articles
4894 * Choosing Commands:: Commands for choosing articles.
4895 * Choosing Variables:: Variables that influence these commands.
4899 @node Choosing Commands
4900 @subsection Choosing Commands
4902 None of the following movement commands understand the numeric prefix,
4903 and they all select and display an article.
4905 If you want to fetch new articles or redisplay the group, see
4906 @ref{Exiting the Summary Buffer}.
4910 @kindex SPACE (Summary)
4911 @findex gnus-summary-next-page
4912 Select the current article, or, if that one's read already, the next
4913 unread article (@code{gnus-summary-next-page}).
4915 If you have an article window open already and you press @kbd{SPACE}
4916 again, the article will be scrolled. This lets you conveniently
4917 @kbd{SPACE} through an entire newsgroup. @pxref{Paging the Article}.
4922 @kindex G n (Summary)
4923 @findex gnus-summary-next-unread-article
4924 @c @icon{gnus-summary-next-unread}
4925 Go to next unread article (@code{gnus-summary-next-unread-article}).
4930 @findex gnus-summary-prev-unread-article
4931 @c @icon{gnus-summary-prev-unread}
4932 Go to previous unread article (@code{gnus-summary-prev-unread-article}).
4937 @kindex G N (Summary)
4938 @findex gnus-summary-next-article
4939 Go to the next article (@code{gnus-summary-next-article}).
4944 @kindex G P (Summary)
4945 @findex gnus-summary-prev-article
4946 Go to the previous article (@code{gnus-summary-prev-article}).
4949 @kindex G C-n (Summary)
4950 @findex gnus-summary-next-same-subject
4951 Go to the next article with the same subject
4952 (@code{gnus-summary-next-same-subject}).
4955 @kindex G C-p (Summary)
4956 @findex gnus-summary-prev-same-subject
4957 Go to the previous article with the same subject
4958 (@code{gnus-summary-prev-same-subject}).
4962 @kindex G f (Summary)
4964 @findex gnus-summary-first-unread-article
4965 Go to the first unread article
4966 (@code{gnus-summary-first-unread-article}).
4970 @kindex G b (Summary)
4972 @findex gnus-summary-best-unread-article
4973 Go to the unread article with the highest score
4974 (@code{gnus-summary-best-unread-article}). If given a prefix argument,
4975 go to the first unread article that has a score over the default score.
4980 @kindex G l (Summary)
4981 @findex gnus-summary-goto-last-article
4982 Go to the previous article read (@code{gnus-summary-goto-last-article}).
4985 @kindex G o (Summary)
4986 @findex gnus-summary-pop-article
4988 @cindex article history
4989 Pop an article off the summary history and go to this article
4990 (@code{gnus-summary-pop-article}). This command differs from the
4991 command above in that you can pop as many previous articles off the
4992 history as you like, while @kbd{l} toggles the two last read articles.
4993 For a somewhat related issue (if you use these commands a lot),
4994 @pxref{Article Backlog}.
4999 @kindex G j (Summary)
5000 @findex gnus-summary-goto-article
5001 Ask for an article number or @code{Message-ID}, and then go to that
5002 article (@code{gnus-summary-goto-article}).
5007 @node Choosing Variables
5008 @subsection Choosing Variables
5010 Some variables relevant for moving and selecting articles:
5013 @item gnus-auto-extend-newsgroup
5014 @vindex gnus-auto-extend-newsgroup
5015 All the movement commands will try to go to the previous (or next)
5016 article, even if that article isn't displayed in the Summary buffer if
5017 this variable is non-@code{nil}. Gnus will then fetch the article from
5018 the server and display it in the article buffer.
5020 @item gnus-select-article-hook
5021 @vindex gnus-select-article-hook
5022 This hook is called whenever an article is selected. By default it
5023 exposes any threads hidden under the selected article. If you would
5024 like each article to be saved in the Agent as you read it, putting
5025 @code{gnus-agent-fetch-selected-article} on this hook will do so.
5027 @item gnus-mark-article-hook
5028 @vindex gnus-mark-article-hook
5029 @findex gnus-summary-mark-unread-as-read
5030 @findex gnus-summary-mark-read-and-unread-as-read
5031 @findex gnus-unread-mark
5032 This hook is called whenever an article is selected. It is intended to
5033 be used for marking articles as read. The default value is
5034 @code{gnus-summary-mark-read-and-unread-as-read}, and will change the
5035 mark of almost any article you read to @code{gnus-unread-mark}. The
5036 only articles not affected by this function are ticked, dormant, and
5037 expirable articles. If you'd instead like to just have unread articles
5038 marked as read, you can use @code{gnus-summary-mark-unread-as-read}
5039 instead. It will leave marks like @code{gnus-low-score-mark},
5040 @code{gnus-del-mark} (and so on) alone.
5045 @node Paging the Article
5046 @section Scrolling the Article
5047 @cindex article scrolling
5052 @kindex SPACE (Summary)
5053 @findex gnus-summary-next-page
5054 Pressing @kbd{SPACE} will scroll the current article forward one page,
5055 or, if you have come to the end of the current article, will choose the
5056 next article (@code{gnus-summary-next-page}).
5058 @vindex gnus-article-boring-faces
5059 @vindex gnus-article-skip-boring
5060 If @code{gnus-article-skip-boring} is non-@code{nil} and the rest of
5061 the article consists only of citations and signature, then it will be
5062 skipped; the next article will be shown instead. You can customize
5063 what is considered uninteresting with
5064 @code{gnus-article-boring-faces}. You can manually view the article's
5065 pages, no matter how boring, using @kbd{C-M-v}.
5068 @kindex DEL (Summary)
5069 @findex gnus-summary-prev-page
5070 Scroll the current article back one page (@code{gnus-summary-prev-page}).
5073 @kindex RET (Summary)
5074 @findex gnus-summary-scroll-up
5075 Scroll the current article one line forward
5076 (@code{gnus-summary-scroll-up}).
5079 @kindex M-RET (Summary)
5080 @findex gnus-summary-scroll-down
5081 Scroll the current article one line backward
5082 (@code{gnus-summary-scroll-down}).
5086 @kindex A g (Summary)
5088 @findex gnus-summary-show-article
5089 @vindex gnus-summary-show-article-charset-alist
5090 (Re)fetch the current article (@code{gnus-summary-show-article}). If
5091 given a prefix, fetch the current article, but don't run any of the
5092 article treatment functions. This will give you a ``raw'' article, just
5093 the way it came from the server.
5095 If given a numerical prefix, you can do semi-manual charset stuff.
5096 @kbd{C-u 0 g cn-gb-2312 RET} will decode the message as if it were
5097 encoded in the @code{cn-gb-2312} charset. If you have
5100 (setq gnus-summary-show-article-charset-alist
5105 then you can say @kbd{C-u 1 g} to get the same effect.
5110 @kindex A < (Summary)
5111 @findex gnus-summary-beginning-of-article
5112 Scroll to the beginning of the article
5113 (@code{gnus-summary-beginning-of-article}).
5118 @kindex A > (Summary)
5119 @findex gnus-summary-end-of-article
5120 Scroll to the end of the article (@code{gnus-summary-end-of-article}).
5124 @kindex A s (Summary)
5126 @findex gnus-summary-isearch-article
5127 Perform an isearch in the article buffer
5128 (@code{gnus-summary-isearch-article}).
5132 @findex gnus-summary-select-article-buffer
5133 Select the article buffer (@code{gnus-summary-select-article-buffer}).
5138 @node Reply Followup and Post
5139 @section Reply, Followup and Post
5142 * Summary Mail Commands:: Sending mail.
5143 * Summary Post Commands:: Sending news.
5144 * Summary Message Commands:: Other Message-related commands.
5145 * Canceling and Superseding::
5149 @node Summary Mail Commands
5150 @subsection Summary Mail Commands
5152 @cindex composing mail
5154 Commands for composing a mail message:
5160 @kindex S r (Summary)
5162 @findex gnus-summary-reply
5163 @c @icon{gnus-summary-mail-reply}
5164 @c @icon{gnus-summary-reply}
5165 Mail a reply to the author of the current article
5166 (@code{gnus-summary-reply}).
5171 @kindex S R (Summary)
5172 @findex gnus-summary-reply-with-original
5173 @c @icon{gnus-summary-reply-with-original}
5174 Mail a reply to the author of the current article and include the
5175 original message (@code{gnus-summary-reply-with-original}). This
5176 command uses the process/prefix convention.
5179 @kindex S w (Summary)
5180 @findex gnus-summary-wide-reply
5181 Mail a wide reply to the author of the current article
5182 (@code{gnus-summary-wide-reply}). A @dfn{wide reply} is a reply that
5183 goes out to all people listed in the @code{To}, @code{From} (or
5184 @code{Reply-to}) and @code{Cc} headers.
5187 @kindex S W (Summary)
5188 @findex gnus-summary-wide-reply-with-original
5189 Mail a wide reply to the current article and include the original
5190 message (@code{gnus-summary-wide-reply-with-original}). This command uses
5191 the process/prefix convention.
5194 @kindex S v (Summary)
5195 @findex gnus-summary-very-wide-reply
5196 Mail a very wide reply to the author of the current article
5197 (@code{gnus-summary-wide-reply}). A @dfn{very wide reply} is a reply
5198 that goes out to all people listed in the @code{To}, @code{From} (or
5199 @code{Reply-to}) and @code{Cc} headers in all the process/prefixed
5200 articles. This command uses the process/prefix convention.
5203 @kindex S V (Summary)
5204 @findex gnus-summary-very-wide-reply-with-original
5205 Mail a very wide reply to the author of the current article and include the
5206 original message (@code{gnus-summary-very-wide-reply-with-original}). This
5207 command uses the process/prefix convention.
5210 @kindex S B r (Summary)
5211 @findex gnus-summary-reply-broken-reply-to
5212 Mail a reply to the author of the current article but ignore the
5213 @code{Reply-To} field (@code{gnus-summary-reply-broken-reply-to}).
5216 @kindex S B R (Summary)
5217 @findex gnus-summary-reply-broken-reply-to-with-original
5218 Mail a reply to the author of the current article and include the
5219 original message but ignore the @code{Reply-To} field
5220 (@code{gnus-summary-reply-broken-reply-to-with-original}).
5224 @kindex S o m (Summary)
5225 @kindex C-c C-f (Summary)
5226 @findex gnus-summary-mail-forward
5227 @c @icon{gnus-summary-mail-forward}
5228 Forward the current article to some other person
5229 (@code{gnus-summary-mail-forward}). If no prefix is given, the message
5230 is forwarded according to the value of (@code{message-forward-as-mime})
5231 and (@code{message-forward-show-mml}); if the prefix is 1, decode the
5232 message and forward directly inline; if the prefix is 2, forward message
5233 as an rfc822 @sc{mime} section; if the prefix is 3, decode message and
5234 forward as an rfc822 @sc{mime} section; if the prefix is 4, forward message
5235 directly inline; otherwise, the message is forwarded as no prefix given
5236 but use the flipped value of (@code{message-forward-as-mime}). By
5237 default, the message is decoded and forwarded as an rfc822 @sc{mime}
5243 @kindex S m (Summary)
5244 @findex gnus-summary-mail-other-window
5245 @c @icon{gnus-summary-mail-originate}
5246 Prepare a mail (@code{gnus-summary-mail-other-window}). By default, use
5247 the posting style of the current group. If given a prefix, disable that.
5248 If the prefix is 1, prompt for a group name to find the posting style.
5253 @kindex S i (Summary)
5254 @findex gnus-summary-news-other-window
5255 Prepare a news (@code{gnus-summary-news-other-window}). By default,
5256 post to the current group. If given a prefix, disable that. If the
5257 prefix is 1, prompt for a group to post to.
5259 This function actually prepares a news even when using mail groups.
5260 This is useful for ``posting'' messages to mail groups without actually
5261 sending them over the network: they're just saved directly to the group
5262 in question. The corresponding back end must have a request-post method
5263 for this to work though.
5266 @kindex S D b (Summary)
5267 @findex gnus-summary-resend-bounced-mail
5268 @cindex bouncing mail
5269 If you have sent a mail, but the mail was bounced back to you for some
5270 reason (wrong address, transient failure), you can use this command to
5271 resend that bounced mail (@code{gnus-summary-resend-bounced-mail}). You
5272 will be popped into a mail buffer where you can edit the headers before
5273 sending the mail off again. If you give a prefix to this command, and
5274 the bounced mail is a reply to some other mail, Gnus will try to fetch
5275 that mail and display it for easy perusal of its headers. This might
5276 very well fail, though.
5279 @kindex S D r (Summary)
5280 @findex gnus-summary-resend-message
5281 Not to be confused with the previous command,
5282 @code{gnus-summary-resend-message} will prompt you for an address to
5283 send the current message off to, and then send it to that place. The
5284 headers of the message won't be altered---but lots of headers that say
5285 @code{Resent-To}, @code{Resent-From} and so on will be added. This
5286 means that you actually send a mail to someone that has a @code{To}
5287 header that (probably) points to yourself. This will confuse people.
5288 So, natcherly you'll only do that if you're really eVIl.
5290 This command is mainly used if you have several accounts and want to
5291 ship a mail to a different account of yours. (If you're both
5292 @code{root} and @code{postmaster} and get a mail for @code{postmaster}
5293 to the @code{root} account, you may want to resend it to
5294 @code{postmaster}. Ordnung muss sein!
5296 This command understands the process/prefix convention
5297 (@pxref{Process/Prefix}).
5300 @kindex S O m (Summary)
5301 @findex gnus-uu-digest-mail-forward
5302 Digest the current series (@pxref{Decoding Articles}) and forward the
5303 result using mail (@code{gnus-uu-digest-mail-forward}). This command
5304 uses the process/prefix convention (@pxref{Process/Prefix}).
5307 @kindex S M-c (Summary)
5308 @findex gnus-summary-mail-crosspost-complaint
5309 @cindex crossposting
5310 @cindex excessive crossposting
5311 Send a complaint about excessive crossposting to the author of the
5312 current article (@code{gnus-summary-mail-crosspost-complaint}).
5314 @findex gnus-crosspost-complaint
5315 This command is provided as a way to fight back against the current
5316 crossposting pandemic that's sweeping Usenet. It will compose a reply
5317 using the @code{gnus-crosspost-complaint} variable as a preamble. This
5318 command understands the process/prefix convention
5319 (@pxref{Process/Prefix}) and will prompt you before sending each mail.
5323 Also @xref{Header Commands, ,Header Commands, message, The Message
5324 Manual}, for more information.
5327 @node Summary Post Commands
5328 @subsection Summary Post Commands
5330 @cindex composing news
5332 Commands for posting a news article:
5338 @kindex S p (Summary)
5339 @findex gnus-summary-post-news
5340 @c @icon{gnus-summary-post-news}
5341 Prepare for posting an article (@code{gnus-summary-post-news}). By
5342 default, post to the current group. If given a prefix, disable that.
5343 If the prefix is 1, prompt for another group instead.
5348 @kindex S f (Summary)
5349 @findex gnus-summary-followup
5350 @c @icon{gnus-summary-followup}
5351 Post a followup to the current article (@code{gnus-summary-followup}).
5355 @kindex S F (Summary)
5357 @c @icon{gnus-summary-followup-with-original}
5358 @findex gnus-summary-followup-with-original
5359 Post a followup to the current article and include the original message
5360 (@code{gnus-summary-followup-with-original}). This command uses the
5361 process/prefix convention.
5364 @kindex S n (Summary)
5365 @findex gnus-summary-followup-to-mail
5366 Post a followup to the current article via news, even if you got the
5367 message through mail (@code{gnus-summary-followup-to-mail}).
5370 @kindex S N (Summary)
5371 @findex gnus-summary-followup-to-mail-with-original
5372 Post a followup to the current article via news, even if you got the
5373 message through mail and include the original message
5374 (@code{gnus-summary-followup-to-mail-with-original}). This command uses
5375 the process/prefix convention.
5378 @kindex S o p (Summary)
5379 @findex gnus-summary-post-forward
5380 Forward the current article to a newsgroup
5381 (@code{gnus-summary-post-forward}).
5382 If no prefix is given, the message is forwarded according to the value
5383 of (@code{message-forward-as-mime}) and
5384 (@code{message-forward-show-mml}); if the prefix is 1, decode the
5385 message and forward directly inline; if the prefix is 2, forward message
5386 as an rfc822 @sc{mime} section; if the prefix is 3, decode message and
5387 forward as an rfc822 @sc{mime} section; if the prefix is 4, forward message
5388 directly inline; otherwise, the message is forwarded as no prefix given
5389 but use the flipped value of (@code{message-forward-as-mime}). By
5390 default, the message is decoded and forwarded as an rfc822 @sc{mime} section.
5393 @kindex S O p (Summary)
5394 @findex gnus-uu-digest-post-forward
5396 @cindex making digests
5397 Digest the current series and forward the result to a newsgroup
5398 (@code{gnus-uu-digest-mail-forward}). This command uses the
5399 process/prefix convention.
5402 @kindex S u (Summary)
5403 @findex gnus-uu-post-news
5404 @c @icon{gnus-uu-post-news}
5405 Uuencode a file, split it into parts, and post it as a series
5406 (@code{gnus-uu-post-news}). (@pxref{Uuencoding and Posting}).
5409 Also @xref{Header Commands, ,Header Commands, message, The Message
5410 Manual}, for more information.
5413 @node Summary Message Commands
5414 @subsection Summary Message Commands
5418 @kindex S y (Summary)
5419 @findex gnus-summary-yank-message
5420 Yank the current article into an already existing Message composition
5421 buffer (@code{gnus-summary-yank-message}). This command prompts for
5422 what message buffer you want to yank into, and understands the
5423 process/prefix convention (@pxref{Process/Prefix}).
5428 @node Canceling and Superseding
5429 @subsection Canceling Articles
5430 @cindex canceling articles
5431 @cindex superseding articles
5433 Have you ever written something, and then decided that you really,
5434 really, really wish you hadn't posted that?
5436 Well, you can't cancel mail, but you can cancel posts.
5438 @findex gnus-summary-cancel-article
5440 @c @icon{gnus-summary-cancel-article}
5441 Find the article you wish to cancel (you can only cancel your own
5442 articles, so don't try any funny stuff). Then press @kbd{C} or @kbd{S
5443 c} (@code{gnus-summary-cancel-article}). Your article will be
5444 canceled---machines all over the world will be deleting your article.
5445 This command uses the process/prefix convention (@pxref{Process/Prefix}).
5447 Be aware, however, that not all sites honor cancels, so your article may
5448 live on here and there, while most sites will delete the article in
5451 Gnus will use the ``current'' select method when canceling. If you
5452 want to use the standard posting method, use the @samp{a} symbolic
5453 prefix (@pxref{Symbolic Prefixes}).
5455 If you discover that you have made some mistakes and want to do some
5456 corrections, you can post a @dfn{superseding} article that will replace
5457 your original article.
5459 @findex gnus-summary-supersede-article
5461 Go to the original article and press @kbd{S s}
5462 (@code{gnus-summary-supersede-article}). You will be put in a buffer
5463 where you can edit the article all you want before sending it off the
5466 The same goes for superseding as for canceling, only more so: Some
5467 sites do not honor superseding. On those sites, it will appear that you
5468 have posted almost the same article twice.
5470 If you have just posted the article, and change your mind right away,
5471 there is a trick you can use to cancel/supersede the article without
5472 waiting for the article to appear on your site first. You simply return
5473 to the post buffer (which is called @code{*sent ...*}). There you will
5474 find the article you just posted, with all the headers intact. Change
5475 the @code{Message-ID} header to a @code{Cancel} or @code{Supersedes}
5476 header by substituting one of those words for the word
5477 @code{Message-ID}. Then just press @kbd{C-c C-c} to send the article as
5478 you would do normally. The previous article will be
5479 canceled/superseded.
5481 Just remember, kids: There is no 'c' in 'supersede'.
5483 @node Delayed Articles
5484 @section Delayed Articles
5485 @cindex delayed sending
5486 @cindex send delayed
5488 Sometimes, you might wish to delay the sending of a message. For
5489 example, you might wish to arrange for a message to turn up just in time
5490 to remind your about the birthday of your Significant Other. For this,
5491 there is the @code{gnus-delay} package. Setup is simple:
5494 (gnus-delay-initialize)
5497 @findex gnus-delay-article
5498 Normally, to send a message you use the @kbd{C-c C-c} command from
5499 Message mode. To delay a message, use @kbd{C-c C-j}
5500 (@code{gnus-delay-article}) instead. This will ask you for how long the
5501 message should be delayed. Possible answers are:
5505 A time span. Consists of an integer and a letter. For example,
5506 @code{42d} means to delay for 42 days. Available letters are @code{m}
5507 (minutes), @code{h} (hours), @code{d} (days), @code{w} (weeks), @code{M}
5508 (months) and @code{Y} (years).
5511 A specific date. Looks like @code{YYYYY-MM-DD}. The message will be
5512 delayed until that day, at a specific time (eight o'clock by default).
5513 See also @code{gnus-delay-default-hour}.
5516 A specific time of day. Given in @code{hh:mm} format, 24h, no am/pm
5517 stuff. The deadline will be at that time today, except if that time has
5518 already passed, then it's at the given time tomorrow. So if it's ten
5519 o'clock in the morning and you specify @code{11:15}, then the deadline
5520 is one hour and fifteen minutes hence. But if you specify @code{9:20},
5521 that means a time tomorrow.
5524 The action of the @code{gnus-delay-article} command is influenced by a
5525 couple of variables:
5528 @item gnus-delay-default-hour
5529 @vindex gnus-delay-default-hour
5530 When you specify a specific date, the message will be due on that hour
5531 on the given date. Possible values are integers 0 through 23.
5533 @item gnus-delay-default-delay
5534 @vindex gnus-delay-default-delay
5535 This is a string and gives the default delay. It can be of any of the
5536 formats described above.
5538 @item gnus-delay-group
5539 @vindex gnus-delay-group
5540 Delayed articles will be kept in this group on the drafts server until
5541 they are due. You probably don't need to change this. The default
5542 value is @code{"delayed"}.
5544 @item gnus-delay-header
5545 @vindex gnus-delay-header
5546 The deadline for each article will be stored in a header. This variable
5547 is a string and gives the header name. You probably don't need to
5548 change this. The default value is @code{"X-Gnus-Delayed"}.
5551 The way delaying works is like this: when you use the
5552 @code{gnus-delay-article} command, you give a certain delay. Gnus
5553 calculates the deadline of the message and stores it in the
5554 @code{X-Gnus-Delayed} header and puts the message in the
5555 @code{nndraft:delayed} group.
5557 @findex gnus-delay-send-queue
5558 And whenever you get new news, Gnus looks through the group for articles
5559 which are due and sends them. It uses the @code{gnus-delay-send-queue}
5560 function for this. By default, this function is added to the hook
5561 @code{gnus-get-new-news-hook}. But of course, you can change this.
5562 Maybe you want to use the demon to send drafts? Just tell the demon to
5563 execute the @code{gnus-delay-send-queue} function.
5566 @item gnus-delay-initialize
5567 @findex gnus-delay-initialize
5568 By default, this function installs @code{gnus-delay-send-queue} in
5569 @code{gnus-get-new-news-hook}. But it accepts the optional second
5570 argument @code{no-check}. If it is non-@code{nil},
5571 @code{gnus-get-new-news-hook} is not changed. The optional first
5572 argument is ignored.
5574 For example, @code{(gnus-delay-initialize nil t)} means to do nothing.
5575 Presumably, you want to use the demon for sending due delayed articles.
5576 Just don't forget to set that up :-)
5580 @node Marking Articles
5581 @section Marking Articles
5582 @cindex article marking
5583 @cindex article ticking
5586 There are several marks you can set on an article.
5588 You have marks that decide the @dfn{readedness} (whoo, neato-keano
5589 neologism ohoy!) of the article. Alphabetic marks generally mean
5590 @dfn{read}, while non-alphabetic characters generally mean @dfn{unread}.
5592 In addition, you also have marks that do not affect readedness.
5595 * Unread Articles:: Marks for unread articles.
5596 * Read Articles:: Marks for read articles.
5597 * Other Marks:: Marks that do not affect readedness.
5601 There's a plethora of commands for manipulating these marks:
5605 * Setting Marks:: How to set and remove marks.
5606 * Generic Marking Commands:: How to customize the marking.
5607 * Setting Process Marks:: How to mark articles for later processing.
5611 @node Unread Articles
5612 @subsection Unread Articles
5614 The following marks mark articles as (kinda) unread, in one form or
5619 @vindex gnus-ticked-mark
5620 Marked as ticked (@code{gnus-ticked-mark}).
5622 @dfn{Ticked articles} are articles that will remain visible always. If
5623 you see an article that you find interesting, or you want to put off
5624 reading it, or replying to it, until sometime later, you'd typically
5625 tick it. However, articles can be expired (from news servers by the
5626 news server software, Gnus itself never expires ticked messages), so if
5627 you want to keep an article forever, you'll have to make it persistent
5628 (@pxref{Persistent Articles}).
5631 @vindex gnus-dormant-mark
5632 Marked as dormant (@code{gnus-dormant-mark}).
5634 @dfn{Dormant articles} will only appear in the summary buffer if there
5635 are followups to it. If you want to see them even if they don't have
5636 followups, you can use the @kbd{/ D} command (@pxref{Limiting}).
5637 Otherwise (except for the visibility issue), they are just like ticked
5641 @vindex gnus-unread-mark
5642 Marked as unread (@code{gnus-unread-mark}).
5644 @dfn{Unread articles} are articles that haven't been read at all yet.
5649 @subsection Read Articles
5650 @cindex expirable mark
5652 All the following marks mark articles as read.
5657 @vindex gnus-del-mark
5658 These are articles that the user has marked as read with the @kbd{d}
5659 command manually, more or less (@code{gnus-del-mark}).
5662 @vindex gnus-read-mark
5663 Articles that have actually been read (@code{gnus-read-mark}).
5666 @vindex gnus-ancient-mark
5667 Articles that were marked as read in previous sessions and are now
5668 @dfn{old} (@code{gnus-ancient-mark}).
5671 @vindex gnus-killed-mark
5672 Marked as killed (@code{gnus-killed-mark}).
5675 @vindex gnus-kill-file-mark
5676 Marked as killed by kill files (@code{gnus-kill-file-mark}).
5679 @vindex gnus-low-score-mark
5680 Marked as read by having too low a score (@code{gnus-low-score-mark}).
5683 @vindex gnus-catchup-mark
5684 Marked as read by a catchup (@code{gnus-catchup-mark}).
5687 @vindex gnus-canceled-mark
5688 Canceled article (@code{gnus-canceled-mark})
5691 @vindex gnus-souped-mark
5692 @sc{soup}ed article (@code{gnus-souped-mark}). @xref{SOUP}.
5695 @vindex gnus-sparse-mark
5696 Sparsely reffed article (@code{gnus-sparse-mark}). @xref{Customizing
5700 @vindex gnus-duplicate-mark
5701 Article marked as read by duplicate suppression
5702 (@code{gnus-duplicate-mark}). @xref{Duplicate Suppression}.
5706 All these marks just mean that the article is marked as read, really.
5707 They are interpreted differently when doing adaptive scoring, though.
5709 One more special mark, though:
5713 @vindex gnus-expirable-mark
5714 Marked as expirable (@code{gnus-expirable-mark}).
5716 Marking articles as @dfn{expirable} (or have them marked as such
5717 automatically) doesn't make much sense in normal groups---a user doesn't
5718 control expiring of news articles, but in mail groups, for instance,
5719 articles marked as @dfn{expirable} can be deleted by Gnus at
5725 @subsection Other Marks
5726 @cindex process mark
5729 There are some marks that have nothing to do with whether the article is
5735 You can set a bookmark in the current article. Say you are reading a
5736 long thesis on cats' urinary tracts, and have to go home for dinner
5737 before you've finished reading the thesis. You can then set a bookmark
5738 in the article, and Gnus will jump to this bookmark the next time it
5739 encounters the article. @xref{Setting Marks}.
5742 @vindex gnus-replied-mark
5743 All articles that you have replied to or made a followup to (i.e., have
5744 answered) will be marked with an @samp{A} in the second column
5745 (@code{gnus-replied-mark}).
5748 @vindex gnus-forwarded-mark
5749 All articles that you have forwarded will be marked with an @samp{F} in
5750 the second column (@code{gnus-forwarded-mark}).
5753 @vindex gnus-cached-mark
5754 Articles stored in the article cache will be marked with an @samp{*} in
5755 the second column (@code{gnus-cached-mark}). @xref{Article Caching}.
5758 @vindex gnus-saved-mark
5759 Articles ``saved'' (in some manner or other; not necessarily
5760 religiously) are marked with an @samp{S} in the second column
5761 (@code{gnus-saved-mark}).
5764 @vindex gnus-recent-mark
5765 Articles that according to the server haven't been shown to the user
5766 before are marked with a @samp{N} in the second column
5767 (@code{gnus-recent-mark}). Note that not all servers support this
5768 mark, in which case it simply never appears. Compare with
5769 @code{gnus-unseen-mark}.
5772 @vindex gnus-unseen-mark
5773 Articles that haven't been seen before in Gnus by the user are marked
5774 with a @samp{.} in the second column (@code{gnus-unseen-mark}).
5775 Compare with @code{gnus-recent-mark}.
5778 @vindex gnus-downloaded-mark
5779 When using the Gnus agent @pxref{Agent Basics}, articles may be
5780 downloaded for unplugged (offline) viewing. If you are using the
5781 @samp{%O} spec, these articles get the @samp{+} mark in that spec.
5782 (The variable @code{gnus-downloaded-mark} controls which character to
5786 @vindex gnus-undownloaded-mark
5787 When using the Gnus agent @pxref{Agent Basics}, some articles might
5788 not have been downloaded. Such articles cannot be viewed while you
5789 are unplugged (offline). If you are using the @samp{%O} spec, these
5790 articles get the @samp{-} mark in that spec. (The variable
5791 @code{gnus-undownloaded-mark} controls which character to use.)
5794 @vindex gnus-downloadable-mark
5795 The Gnus agent @pxref{Agent Basics} downloads some articles
5796 automatically, but it is also possible to explicitly mark articles for
5797 download, even if they would not be downloaded automatically. Such
5798 explicitly-marked articles get the @samp{%} mark in the first column.
5799 (The variable @code{gnus-downloadable-mark} controls which character to
5803 @vindex gnus-not-empty-thread-mark
5804 @vindex gnus-empty-thread-mark
5805 If the @samp{%e} spec is used, the presence of threads or not will be
5806 marked with @code{gnus-not-empty-thread-mark} and
5807 @code{gnus-empty-thread-mark} in the third column, respectively.
5810 @vindex gnus-process-mark
5811 Finally we have the @dfn{process mark} (@code{gnus-process-mark}). A
5812 variety of commands react to the presence of the process mark. For
5813 instance, @kbd{X u} (@code{gnus-uu-decode-uu}) will uudecode and view
5814 all articles that have been marked with the process mark. Articles
5815 marked with the process mark have a @samp{#} in the second column.
5819 You might have noticed that most of these ``non-readedness'' marks
5820 appear in the second column by default. So if you have a cached, saved,
5821 replied article that you have process-marked, what will that look like?
5823 Nothing much. The precedence rules go as follows: process -> cache ->
5824 replied -> saved. So if the article is in the cache and is replied,
5825 you'll only see the cache mark and not the replied mark.
5829 @subsection Setting Marks
5830 @cindex setting marks
5832 All the marking commands understand the numeric prefix.
5837 @kindex M c (Summary)
5838 @kindex M-u (Summary)
5839 @findex gnus-summary-clear-mark-forward
5840 @cindex mark as unread
5841 Clear all readedness-marks from the current article
5842 (@code{gnus-summary-clear-mark-forward}). In other words, mark the
5848 @kindex M t (Summary)
5849 @findex gnus-summary-tick-article-forward
5850 Tick the current article (@code{gnus-summary-tick-article-forward}).
5851 @xref{Article Caching}.
5856 @kindex M ? (Summary)
5857 @findex gnus-summary-mark-as-dormant
5858 Mark the current article as dormant
5859 (@code{gnus-summary-mark-as-dormant}). @xref{Article Caching}.
5863 @kindex M d (Summary)
5865 @findex gnus-summary-mark-as-read-forward
5866 Mark the current article as read
5867 (@code{gnus-summary-mark-as-read-forward}).
5871 @findex gnus-summary-mark-as-read-backward
5872 Mark the current article as read and move point to the previous line
5873 (@code{gnus-summary-mark-as-read-backward}).
5878 @kindex M k (Summary)
5879 @findex gnus-summary-kill-same-subject-and-select
5880 Mark all articles that have the same subject as the current one as read,
5881 and then select the next unread article
5882 (@code{gnus-summary-kill-same-subject-and-select}).
5886 @kindex M K (Summary)
5887 @kindex C-k (Summary)
5888 @findex gnus-summary-kill-same-subject
5889 Mark all articles that have the same subject as the current one as read
5890 (@code{gnus-summary-kill-same-subject}).
5893 @kindex M C (Summary)
5894 @findex gnus-summary-catchup
5895 @c @icon{gnus-summary-catchup}
5896 Mark all unread articles as read (@code{gnus-summary-catchup}).
5899 @kindex M C-c (Summary)
5900 @findex gnus-summary-catchup-all
5901 Mark all articles in the group as read---even the ticked and dormant
5902 articles (@code{gnus-summary-catchup-all}).
5905 @kindex M H (Summary)
5906 @findex gnus-summary-catchup-to-here
5907 Catchup the current group to point (before the point)
5908 (@code{gnus-summary-catchup-to-here}).
5911 @kindex M h (Summary)
5912 @findex gnus-summary-catchup-from-here
5913 Catchup the current group from point (after the point)
5914 (@code{gnus-summary-catchup-from-here}).
5917 @kindex C-w (Summary)
5918 @findex gnus-summary-mark-region-as-read
5919 Mark all articles between point and mark as read
5920 (@code{gnus-summary-mark-region-as-read}).
5923 @kindex M V k (Summary)
5924 @findex gnus-summary-kill-below
5925 Kill all articles with scores below the default score (or below the
5926 numeric prefix) (@code{gnus-summary-kill-below}).
5930 @kindex M e (Summary)
5932 @findex gnus-summary-mark-as-expirable
5933 Mark the current article as expirable
5934 (@code{gnus-summary-mark-as-expirable}).
5937 @kindex M b (Summary)
5938 @findex gnus-summary-set-bookmark
5939 Set a bookmark in the current article
5940 (@code{gnus-summary-set-bookmark}).
5943 @kindex M B (Summary)
5944 @findex gnus-summary-remove-bookmark
5945 Remove the bookmark from the current article
5946 (@code{gnus-summary-remove-bookmark}).
5949 @kindex M V c (Summary)
5950 @findex gnus-summary-clear-above
5951 Clear all marks from articles with scores over the default score (or
5952 over the numeric prefix) (@code{gnus-summary-clear-above}).
5955 @kindex M V u (Summary)
5956 @findex gnus-summary-tick-above
5957 Tick all articles with scores over the default score (or over the
5958 numeric prefix) (@code{gnus-summary-tick-above}).
5961 @kindex M V m (Summary)
5962 @findex gnus-summary-mark-above
5963 Prompt for a mark, and mark all articles with scores over the default
5964 score (or over the numeric prefix) with this mark
5965 (@code{gnus-summary-clear-above}).
5968 @vindex gnus-summary-goto-unread
5969 The @code{gnus-summary-goto-unread} variable controls what action should
5970 be taken after setting a mark. If non-@code{nil}, point will move to
5971 the next/previous unread article. If @code{nil}, point will just move
5972 one line up or down. As a special case, if this variable is
5973 @code{never}, all the marking commands as well as other commands (like
5974 @kbd{SPACE}) will move to the next article, whether it is unread or not.
5975 The default is @code{t}.
5978 @node Generic Marking Commands
5979 @subsection Generic Marking Commands
5981 Some people would like the command that ticks an article (@kbd{!}) go to
5982 the next article. Others would like it to go to the next unread
5983 article. Yet others would like it to stay on the current article. And
5984 even though I haven't heard of anybody wanting it to go to the
5985 previous (unread) article, I'm sure there are people that want that as
5988 Multiply these five behaviors with five different marking commands, and
5989 you get a potentially complex set of variable to control what each
5992 To sidestep that mess, Gnus provides commands that do all these
5993 different things. They can be found on the @kbd{M M} map in the summary
5994 buffer. Type @kbd{M M C-h} to see them all---there are too many of them
5995 to list in this manual.
5997 While you can use these commands directly, most users would prefer
5998 altering the summary mode keymap. For instance, if you would like the
5999 @kbd{!} command to go to the next article instead of the next unread
6000 article, you could say something like:
6003 (add-hook 'gnus-summary-mode-hook 'my-alter-summary-map)
6004 (defun my-alter-summary-map ()
6005 (local-set-key "!" 'gnus-summary-put-mark-as-ticked-next))
6011 (defun my-alter-summary-map ()
6012 (local-set-key "!" "MM!n"))
6016 @node Setting Process Marks
6017 @subsection Setting Process Marks
6018 @cindex setting process marks
6020 Process marks are displayed as @code{#} in the summary buffer, and are
6021 used for marking articles in such a way that other commands will
6022 process these articles. For instance, if you process mark four
6023 articles and then use the @kbd{*} command, Gnus will enter these four
6024 commands into the cache. For more information,
6025 @pxref{Process/Prefix}.
6032 @kindex M P p (Summary)
6033 @findex gnus-summary-mark-as-processable
6034 Mark the current article with the process mark
6035 (@code{gnus-summary-mark-as-processable}).
6036 @findex gnus-summary-unmark-as-processable
6040 @kindex M P u (Summary)
6041 @kindex M-# (Summary)
6042 Remove the process mark, if any, from the current article
6043 (@code{gnus-summary-unmark-as-processable}).
6046 @kindex M P U (Summary)
6047 @findex gnus-summary-unmark-all-processable
6048 Remove the process mark from all articles
6049 (@code{gnus-summary-unmark-all-processable}).
6052 @kindex M P i (Summary)
6053 @findex gnus-uu-invert-processable
6054 Invert the list of process marked articles
6055 (@code{gnus-uu-invert-processable}).
6058 @kindex M P R (Summary)
6059 @findex gnus-uu-mark-by-regexp
6060 Mark articles that have a @code{Subject} header that matches a regular
6061 expression (@code{gnus-uu-mark-by-regexp}).
6064 @kindex M P G (Summary)
6065 @findex gnus-uu-unmark-by-regexp
6066 Unmark articles that have a @code{Subject} header that matches a regular
6067 expression (@code{gnus-uu-unmark-by-regexp}).
6070 @kindex M P r (Summary)
6071 @findex gnus-uu-mark-region
6072 Mark articles in region (@code{gnus-uu-mark-region}).
6076 @findex gnus-uu-unmark-region
6077 Unmark articles in region (@code{gnus-uu-unmark-region}).
6080 @kindex M P t (Summary)
6081 @findex gnus-uu-mark-thread
6082 Mark all articles in the current (sub)thread
6083 (@code{gnus-uu-mark-thread}).
6086 @kindex M P T (Summary)
6087 @findex gnus-uu-unmark-thread
6088 Unmark all articles in the current (sub)thread
6089 (@code{gnus-uu-unmark-thread}).
6092 @kindex M P v (Summary)
6093 @findex gnus-uu-mark-over
6094 Mark all articles that have a score above the prefix argument
6095 (@code{gnus-uu-mark-over}).
6098 @kindex M P s (Summary)
6099 @findex gnus-uu-mark-series
6100 Mark all articles in the current series (@code{gnus-uu-mark-series}).
6103 @kindex M P S (Summary)
6104 @findex gnus-uu-mark-sparse
6105 Mark all series that have already had some articles marked
6106 (@code{gnus-uu-mark-sparse}).
6109 @kindex M P a (Summary)
6110 @findex gnus-uu-mark-all
6111 Mark all articles in series order (@code{gnus-uu-mark-series}).
6114 @kindex M P b (Summary)
6115 @findex gnus-uu-mark-buffer
6116 Mark all articles in the buffer in the order they appear
6117 (@code{gnus-uu-mark-buffer}).
6120 @kindex M P k (Summary)
6121 @findex gnus-summary-kill-process-mark
6122 Push the current process mark set onto the stack and unmark all articles
6123 (@code{gnus-summary-kill-process-mark}).
6126 @kindex M P y (Summary)
6127 @findex gnus-summary-yank-process-mark
6128 Pop the previous process mark set from the stack and restore it
6129 (@code{gnus-summary-yank-process-mark}).
6132 @kindex M P w (Summary)
6133 @findex gnus-summary-save-process-mark
6134 Push the current process mark set onto the stack
6135 (@code{gnus-summary-save-process-mark}).
6139 Also see the @kbd{&} command in @pxref{Searching for Articles} for how to
6140 set process marks based on article body contents.
6147 It can be convenient to limit the summary buffer to just show some
6148 subset of the articles currently in the group. The effect most limit
6149 commands have is to remove a few (or many) articles from the summary
6152 All limiting commands work on subsets of the articles already fetched
6153 from the servers. None of these commands query the server for
6154 additional articles.
6160 @kindex / / (Summary)
6161 @findex gnus-summary-limit-to-subject
6162 Limit the summary buffer to articles that match some subject
6163 (@code{gnus-summary-limit-to-subject}). If given a prefix, exclude
6167 @kindex / a (Summary)
6168 @findex gnus-summary-limit-to-author
6169 Limit the summary buffer to articles that match some author
6170 (@code{gnus-summary-limit-to-author}). If given a prefix, exclude
6174 @kindex / x (Summary)
6175 @findex gnus-summary-limit-to-extra
6176 Limit the summary buffer to articles that match one of the ``extra''
6177 headers (@pxref{To From Newsgroups})
6178 (@code{gnus-summary-limit-to-extra}). If given a prefix, exclude
6183 @kindex / u (Summary)
6185 @findex gnus-summary-limit-to-unread
6186 Limit the summary buffer to articles not marked as read
6187 (@code{gnus-summary-limit-to-unread}). If given a prefix, limit the
6188 buffer to articles strictly unread. This means that ticked and
6189 dormant articles will also be excluded.
6192 @kindex / m (Summary)
6193 @findex gnus-summary-limit-to-marks
6194 Ask for a mark and then limit to all articles that have been marked
6195 with that mark (@code{gnus-summary-limit-to-marks}).
6198 @kindex / t (Summary)
6199 @findex gnus-summary-limit-to-age
6200 Ask for a number and then limit the summary buffer to articles older than (or equal to) that number of days
6201 (@code{gnus-summary-limit-to-age}). If given a prefix, limit to
6202 articles younger than that number of days.
6205 @kindex / n (Summary)
6206 @findex gnus-summary-limit-to-articles
6207 Limit the summary buffer to the current article
6208 (@code{gnus-summary-limit-to-articles}). Uses the process/prefix
6209 convention (@pxref{Process/Prefix}).
6212 @kindex / w (Summary)
6213 @findex gnus-summary-pop-limit
6214 Pop the previous limit off the stack and restore it
6215 (@code{gnus-summary-pop-limit}). If given a prefix, pop all limits off
6219 @kindex / . (Summary)
6220 @findex gnus-summary-limit-to-unseen
6221 Limit the summary buffer to the unseen articles
6222 (@code{gnus-summary-limit-to-unseen}).
6225 @kindex / v (Summary)
6226 @findex gnus-summary-limit-to-score
6227 Limit the summary buffer to articles that have a score at or above some
6228 score (@code{gnus-summary-limit-to-score}).
6231 @kindex / p (Summary)
6232 @findex gnus-summary-limit-to-display-predicate
6233 Limit the summary buffer to articles that satisfy the @code{display}
6234 group parameter predicate
6235 (@code{gnus-summary-limit-to-display-predicate}). See @pxref{Group
6236 Parameters} for more on this predicate.
6240 @kindex M S (Summary)
6241 @kindex / E (Summary)
6242 @findex gnus-summary-limit-include-expunged
6243 Include all expunged articles in the limit
6244 (@code{gnus-summary-limit-include-expunged}).
6247 @kindex / D (Summary)
6248 @findex gnus-summary-limit-include-dormant
6249 Include all dormant articles in the limit
6250 (@code{gnus-summary-limit-include-dormant}).
6253 @kindex / * (Summary)
6254 @findex gnus-summary-limit-include-cached
6255 Include all cached articles in the limit
6256 (@code{gnus-summary-limit-include-cached}).
6259 @kindex / d (Summary)
6260 @findex gnus-summary-limit-exclude-dormant
6261 Exclude all dormant articles from the limit
6262 (@code{gnus-summary-limit-exclude-dormant}).
6265 @kindex / M (Summary)
6266 @findex gnus-summary-limit-exclude-marks
6267 Exclude all marked articles (@code{gnus-summary-limit-exclude-marks}).
6270 @kindex / T (Summary)
6271 @findex gnus-summary-limit-include-thread
6272 Include all the articles in the current thread in the limit.
6275 @kindex / c (Summary)
6276 @findex gnus-summary-limit-exclude-childless-dormant
6277 Exclude all dormant articles that have no children from the limit
6278 (@code{gnus-summary-limit-exclude-childless-dormant}).
6281 @kindex / C (Summary)
6282 @findex gnus-summary-limit-mark-excluded-as-read
6283 Mark all excluded unread articles as read
6284 (@code{gnus-summary-limit-mark-excluded-as-read}). If given a prefix,
6285 also mark excluded ticked and dormant articles as read.
6288 @kindex / N (Summary)
6289 @findex gnus-summary-insert-new-articles
6290 Insert all new articles in the summary buffer. It scans for new emails
6291 if @var{back-end}@code{-get-new-mail} is non-@code{nil}.
6294 @kindex / o (Summary)
6295 @findex gnus-summary-insert-old-articles
6296 Insert all old articles in the summary buffer. If given a numbered
6297 prefix, fetch this number of articles.
6305 @cindex article threading
6307 Gnus threads articles by default. @dfn{To thread} is to put responses
6308 to articles directly after the articles they respond to---in a
6309 hierarchical fashion.
6311 Threading is done by looking at the @code{References} headers of the
6312 articles. In a perfect world, this would be enough to build pretty
6313 trees, but unfortunately, the @code{References} header is often broken
6314 or simply missing. Weird news propagation exacerbates the problem,
6315 so one has to employ other heuristics to get pleasing results. A
6316 plethora of approaches exists, as detailed in horrible detail in
6317 @pxref{Customizing Threading}.
6319 First, a quick overview of the concepts:
6323 The top-most article in a thread; the first article in the thread.
6326 A tree-like article structure.
6329 A small(er) section of this tree-like structure.
6332 Threads often lose their roots due to article expiry, or due to the root
6333 already having been read in a previous session, and not displayed in the
6334 summary buffer. We then typically have many sub-threads that really
6335 belong to one thread, but are without connecting roots. These are
6336 called loose threads.
6338 @item thread gathering
6339 An attempt to gather loose threads into bigger threads.
6341 @item sparse threads
6342 A thread where the missing articles have been ``guessed'' at, and are
6343 displayed as empty lines in the summary buffer.
6349 * Customizing Threading:: Variables you can change to affect the threading.
6350 * Thread Commands:: Thread based commands in the summary buffer.
6354 @node Customizing Threading
6355 @subsection Customizing Threading
6356 @cindex customizing threading
6359 * Loose Threads:: How Gnus gathers loose threads into bigger threads.
6360 * Filling In Threads:: Making the threads displayed look fuller.
6361 * More Threading:: Even more variables for fiddling with threads.
6362 * Low-Level Threading:: You thought it was over@dots{} but you were wrong!
6367 @subsubsection Loose Threads
6370 @cindex loose threads
6373 @item gnus-summary-make-false-root
6374 @vindex gnus-summary-make-false-root
6375 If non-@code{nil}, Gnus will gather all loose subtrees into one big tree
6376 and create a dummy root at the top. (Wait a minute. Root at the top?
6377 Yup.) Loose subtrees occur when the real root has expired, or you've
6378 read or killed the root in a previous session.
6380 When there is no real root of a thread, Gnus will have to fudge
6381 something. This variable says what fudging method Gnus should use.
6382 There are four possible values:
6386 \gnusfigure{The Summary Buffer}{390}{
6387 \put(0,0){\epsfig{figure=ps/summary-adopt,width=7.5cm}}
6388 \put(445,0){\makebox(0,0)[br]{\epsfig{figure=ps/summary-empty,width=7.5cm}}}
6389 \put(0,400){\makebox(0,0)[tl]{\epsfig{figure=ps/summary-none,width=7.5cm}}}
6390 \put(445,400){\makebox(0,0)[tr]{\epsfig{figure=ps/summary-dummy,width=7.5cm}}}
6395 @cindex adopting articles
6400 Gnus will make the first of the orphaned articles the parent. This
6401 parent will adopt all the other articles. The adopted articles will be
6402 marked as such by pointy brackets (@samp{<>}) instead of the standard
6403 square brackets (@samp{[]}). This is the default method.
6406 @vindex gnus-summary-dummy-line-format
6407 @vindex gnus-summary-make-false-root-always
6408 Gnus will create a dummy summary line that will pretend to be the
6409 parent. This dummy line does not correspond to any real article, so
6410 selecting it will just select the first real article after the dummy
6411 article. @code{gnus-summary-dummy-line-format} is used to specify the
6412 format of the dummy roots. It accepts only one format spec: @samp{S},
6413 which is the subject of the article. @xref{Formatting Variables}.
6414 If you want all threads to have a dummy root, even the non-gathered
6415 ones, set @code{gnus-summary-make-false-root-always} to @code{t}.
6418 Gnus won't actually make any article the parent, but simply leave the
6419 subject field of all orphans except the first empty. (Actually, it will
6420 use @code{gnus-summary-same-subject} as the subject (@pxref{Summary
6424 Don't make any article parent at all. Just gather the threads and
6425 display them after one another.
6428 Don't gather loose threads.
6431 @item gnus-summary-gather-subject-limit
6432 @vindex gnus-summary-gather-subject-limit
6433 Loose threads are gathered by comparing subjects of articles. If this
6434 variable is @code{nil}, Gnus requires an exact match between the
6435 subjects of the loose threads before gathering them into one big
6436 super-thread. This might be too strict a requirement, what with the
6437 presence of stupid newsreaders that chop off long subject lines. If
6438 you think so, set this variable to, say, 20 to require that only the
6439 first 20 characters of the subjects have to match. If you set this
6440 variable to a really low number, you'll find that Gnus will gather
6441 everything in sight into one thread, which isn't very helpful.
6443 @cindex fuzzy article gathering
6444 If you set this variable to the special value @code{fuzzy}, Gnus will
6445 use a fuzzy string comparison algorithm on the subjects (@pxref{Fuzzy
6448 @item gnus-simplify-subject-fuzzy-regexp
6449 @vindex gnus-simplify-subject-fuzzy-regexp
6450 This can either be a regular expression or list of regular expressions
6451 that match strings that will be removed from subjects if fuzzy subject
6452 simplification is used.
6454 @item gnus-simplify-ignored-prefixes
6455 @vindex gnus-simplify-ignored-prefixes
6456 If you set @code{gnus-summary-gather-subject-limit} to something as low
6457 as 10, you might consider setting this variable to something sensible:
6459 @c Written by Michael Ernst <mernst@cs.rice.edu>
6461 (setq gnus-simplify-ignored-prefixes
6467 "wanted" "followup" "summary\\( of\\)?"
6468 "help" "query" "problem" "question"
6469 "answer" "reference" "announce"
6470 "How can I" "How to" "Comparison of"
6475 (mapconcat 'identity
6476 '("for" "for reference" "with" "about")
6478 "\\)?\\]?:?[ \t]*"))
6481 All words that match this regexp will be removed before comparing two
6484 @item gnus-simplify-subject-functions
6485 @vindex gnus-simplify-subject-functions
6486 If non-@code{nil}, this variable overrides
6487 @code{gnus-summary-gather-subject-limit}. This variable should be a
6488 list of functions to apply to the @code{Subject} string iteratively to
6489 arrive at the simplified version of the string.
6491 Useful functions to put in this list include:
6494 @item gnus-simplify-subject-re
6495 @findex gnus-simplify-subject-re
6496 Strip the leading @samp{Re:}.
6498 @item gnus-simplify-subject-fuzzy
6499 @findex gnus-simplify-subject-fuzzy
6502 @item gnus-simplify-whitespace
6503 @findex gnus-simplify-whitespace
6504 Remove excessive whitespace.
6506 @item gnus-simplify-all-whitespace
6507 @findex gnus-simplify-all-whitespace
6508 Remove all whitespace.
6511 You may also write your own functions, of course.
6514 @item gnus-summary-gather-exclude-subject
6515 @vindex gnus-summary-gather-exclude-subject
6516 Since loose thread gathering is done on subjects only, that might lead
6517 to many false hits, especially with certain common subjects like
6518 @samp{} and @samp{(none)}. To make the situation slightly better,
6519 you can use the regexp @code{gnus-summary-gather-exclude-subject} to say
6520 what subjects should be excluded from the gathering process.@*
6521 The default is @samp{^ *$\\|^(none)$}.
6523 @item gnus-summary-thread-gathering-function
6524 @vindex gnus-summary-thread-gathering-function
6525 Gnus gathers threads by looking at @code{Subject} headers. This means
6526 that totally unrelated articles may end up in the same ``thread'', which
6527 is confusing. An alternate approach is to look at all the
6528 @code{Message-ID}s in all the @code{References} headers to find matches.
6529 This will ensure that no gathered threads ever include unrelated
6530 articles, but it also means that people who have posted with broken
6531 newsreaders won't be gathered properly. The choice is yours---plague or
6535 @item gnus-gather-threads-by-subject
6536 @findex gnus-gather-threads-by-subject
6537 This function is the default gathering function and looks at
6538 @code{Subject}s exclusively.
6540 @item gnus-gather-threads-by-references
6541 @findex gnus-gather-threads-by-references
6542 This function looks at @code{References} headers exclusively.
6545 If you want to test gathering by @code{References}, you could say
6549 (setq gnus-summary-thread-gathering-function
6550 'gnus-gather-threads-by-references)
6556 @node Filling In Threads
6557 @subsubsection Filling In Threads
6560 @item gnus-fetch-old-headers
6561 @vindex gnus-fetch-old-headers
6562 If non-@code{nil}, Gnus will attempt to build old threads by fetching
6563 more old headers---headers to articles marked as read. If you
6564 would like to display as few summary lines as possible, but still
6565 connect as many loose threads as possible, you should set this variable
6566 to @code{some} or a number. If you set it to a number, no more than
6567 that number of extra old headers will be fetched. In either case,
6568 fetching old headers only works if the back end you are using carries
6569 overview files---this would normally be @code{nntp}, @code{nnspool},
6570 @code{nnml}, and @code{nnmaildir}. Also remember that if the root of
6571 the thread has been expired by the server, there's not much Gnus can do
6574 This variable can also be set to @code{invisible}. This won't have any
6575 visible effects, but is useful if you use the @kbd{A T} command a lot
6576 (@pxref{Finding the Parent}).
6578 @item gnus-build-sparse-threads
6579 @vindex gnus-build-sparse-threads
6580 Fetching old headers can be slow. A low-rent similar effect can be
6581 gotten by setting this variable to @code{some}. Gnus will then look at
6582 the complete @code{References} headers of all articles and try to string
6583 together articles that belong in the same thread. This will leave
6584 @dfn{gaps} in the threading display where Gnus guesses that an article
6585 is missing from the thread. (These gaps appear like normal summary
6586 lines. If you select a gap, Gnus will try to fetch the article in
6587 question.) If this variable is @code{t}, Gnus will display all these
6588 ``gaps'' without regard for whether they are useful for completing the
6589 thread or not. Finally, if this variable is @code{more}, Gnus won't cut
6590 off sparse leaf nodes that don't lead anywhere. This variable is
6591 @code{nil} by default.
6593 @item gnus-read-all-available-headers
6594 @vindex gnus-read-all-available-headers
6595 This is a rather obscure variable that few will find useful. It's
6596 intended for those non-news newsgroups where the back end has to fetch
6597 quite a lot to present the summary buffer, and where it's impossible to
6598 go back to parents of articles. This is mostly the case in the
6599 web-based groups, like the @code{nnultimate} groups.
6601 If you don't use those, then it's safe to leave this as the default
6602 @code{nil}. If you want to use this variable, it should be a regexp
6603 that matches the group name, or @code{t} for all groups.
6608 @node More Threading
6609 @subsubsection More Threading
6612 @item gnus-show-threads
6613 @vindex gnus-show-threads
6614 If this variable is @code{nil}, no threading will be done, and all of
6615 the rest of the variables here will have no effect. Turning threading
6616 off will speed group selection up a bit, but it is sure to make reading
6617 slower and more awkward.
6619 @item gnus-thread-hide-subtree
6620 @vindex gnus-thread-hide-subtree
6621 If non-@code{nil}, all threads will be hidden when the summary buffer is
6624 This can also be a predicate specifier (@pxref{Predicate Specifiers}).
6625 Available predicates are @code{gnus-article-unread-p} and
6626 @code{gnus-article-unseen-p}).
6631 (setq gnus-thread-hide-subtree
6632 '(or gnus-article-unread-p
6633 gnus-article-unseen-p))
6636 (It's a pretty nonsensical example, since all unseen articles are also
6637 unread, but you get my drift.)
6640 @item gnus-thread-expunge-below
6641 @vindex gnus-thread-expunge-below
6642 All threads that have a total score (as defined by
6643 @code{gnus-thread-score-function}) less than this number will be
6644 expunged. This variable is @code{nil} by default, which means that no
6645 threads are expunged.
6647 @item gnus-thread-hide-killed
6648 @vindex gnus-thread-hide-killed
6649 if you kill a thread and this variable is non-@code{nil}, the subtree
6652 @item gnus-thread-ignore-subject
6653 @vindex gnus-thread-ignore-subject
6654 Sometimes somebody changes the subject in the middle of a thread. If
6655 this variable is non-@code{nil}, which is the default, the subject
6656 change is ignored. If it is @code{nil}, a change in the subject will
6657 result in a new thread.
6659 @item gnus-thread-indent-level
6660 @vindex gnus-thread-indent-level
6661 This is a number that says how much each sub-thread should be indented.
6664 @item gnus-sort-gathered-threads-function
6665 @vindex gnus-sort-gathered-threads-function
6666 Sometimes, particularly with mailing lists, the order in which mails
6667 arrive locally is not necessarily the same as the order in which they
6668 arrived on the mailing list. Consequently, when sorting sub-threads
6669 using the default @code{gnus-thread-sort-by-number}, responses can end
6670 up appearing before the article to which they are responding to.
6671 Setting this variable to an alternate value
6672 (e.g. @code{gnus-thread-sort-by-date}), in a group's parameters or in an
6673 appropriate hook (e.g. @code{gnus-summary-generate-hook}) can produce a
6674 more logical sub-thread ordering in such instances.
6679 @node Low-Level Threading
6680 @subsubsection Low-Level Threading
6684 @item gnus-parse-headers-hook
6685 @vindex gnus-parse-headers-hook
6686 Hook run before parsing any headers.
6688 @item gnus-alter-header-function
6689 @vindex gnus-alter-header-function
6690 If non-@code{nil}, this function will be called to allow alteration of
6691 article header structures. The function is called with one parameter,
6692 the article header vector, which it may alter in any way. For instance,
6693 if you have a mail-to-news gateway which alters the @code{Message-ID}s
6694 in systematic ways (by adding prefixes and such), you can use this
6695 variable to un-scramble the @code{Message-ID}s so that they are more
6696 meaningful. Here's one example:
6699 (setq gnus-alter-header-function 'my-alter-message-id)
6701 (defun my-alter-message-id (header)
6702 (let ((id (mail-header-id header)))
6704 "\\(<[^<>@@]*\\)\\.?cygnus\\..*@@\\([^<>@@]*>\\)" id)
6706 (concat (match-string 1 id) "@@" (match-string 2 id))
6713 @node Thread Commands
6714 @subsection Thread Commands
6715 @cindex thread commands
6721 @kindex T k (Summary)
6722 @kindex C-M-k (Summary)
6723 @findex gnus-summary-kill-thread
6724 Mark all articles in the current (sub-)thread as read
6725 (@code{gnus-summary-kill-thread}). If the prefix argument is positive,
6726 remove all marks instead. If the prefix argument is negative, tick
6731 @kindex T l (Summary)
6732 @kindex C-M-l (Summary)
6733 @findex gnus-summary-lower-thread
6734 Lower the score of the current (sub-)thread
6735 (@code{gnus-summary-lower-thread}).
6738 @kindex T i (Summary)
6739 @findex gnus-summary-raise-thread
6740 Increase the score of the current (sub-)thread
6741 (@code{gnus-summary-raise-thread}).
6744 @kindex T # (Summary)
6745 @findex gnus-uu-mark-thread
6746 Set the process mark on the current (sub-)thread
6747 (@code{gnus-uu-mark-thread}).
6750 @kindex T M-# (Summary)
6751 @findex gnus-uu-unmark-thread
6752 Remove the process mark from the current (sub-)thread
6753 (@code{gnus-uu-unmark-thread}).
6756 @kindex T T (Summary)
6757 @findex gnus-summary-toggle-threads
6758 Toggle threading (@code{gnus-summary-toggle-threads}).
6761 @kindex T s (Summary)
6762 @findex gnus-summary-show-thread
6763 Expose the (sub-)thread hidden under the current article, if any
6764 (@code{gnus-summary-show-thread}).
6767 @kindex T h (Summary)
6768 @findex gnus-summary-hide-thread
6769 Hide the current (sub-)thread (@code{gnus-summary-hide-thread}).
6772 @kindex T S (Summary)
6773 @findex gnus-summary-show-all-threads
6774 Expose all hidden threads (@code{gnus-summary-show-all-threads}).
6777 @kindex T H (Summary)
6778 @findex gnus-summary-hide-all-threads
6779 Hide all threads (@code{gnus-summary-hide-all-threads}).
6782 @kindex T t (Summary)
6783 @findex gnus-summary-rethread-current
6784 Re-thread the current article's thread
6785 (@code{gnus-summary-rethread-current}). This works even when the
6786 summary buffer is otherwise unthreaded.
6789 @kindex T ^ (Summary)
6790 @findex gnus-summary-reparent-thread
6791 Make the current article the child of the marked (or previous) article
6792 (@code{gnus-summary-reparent-thread}).
6796 The following commands are thread movement commands. They all
6797 understand the numeric prefix.
6802 @kindex T n (Summary)
6804 @kindex C-M-n (Summary)
6806 @kindex M-down (Summary)
6807 @findex gnus-summary-next-thread
6808 Go to the next thread (@code{gnus-summary-next-thread}).
6811 @kindex T p (Summary)
6813 @kindex C-M-p (Summary)
6815 @kindex M-up (Summary)
6816 @findex gnus-summary-prev-thread
6817 Go to the previous thread (@code{gnus-summary-prev-thread}).
6820 @kindex T d (Summary)
6821 @findex gnus-summary-down-thread
6822 Descend the thread (@code{gnus-summary-down-thread}).
6825 @kindex T u (Summary)
6826 @findex gnus-summary-up-thread
6827 Ascend the thread (@code{gnus-summary-up-thread}).
6830 @kindex T o (Summary)
6831 @findex gnus-summary-top-thread
6832 Go to the top of the thread (@code{gnus-summary-top-thread}).
6835 @vindex gnus-thread-operation-ignore-subject
6836 If you ignore subject while threading, you'll naturally end up with
6837 threads that have several different subjects in them. If you then issue
6838 a command like @kbd{T k} (@code{gnus-summary-kill-thread}) you might not
6839 wish to kill the entire thread, but just those parts of the thread that
6840 have the same subject as the current article. If you like this idea,
6841 you can fiddle with @code{gnus-thread-operation-ignore-subject}. If it
6842 is non-@code{nil} (which it is by default), subjects will be ignored
6843 when doing thread commands. If this variable is @code{nil}, articles in
6844 the same thread with different subjects will not be included in the
6845 operation in question. If this variable is @code{fuzzy}, only articles
6846 that have subjects fuzzily equal will be included (@pxref{Fuzzy
6850 @node Sorting the Summary Buffer
6851 @section Sorting the Summary Buffer
6853 @findex gnus-thread-sort-by-total-score
6854 @findex gnus-thread-sort-by-date
6855 @findex gnus-thread-sort-by-score
6856 @findex gnus-thread-sort-by-subject
6857 @findex gnus-thread-sort-by-author
6858 @findex gnus-thread-sort-by-number
6859 @findex gnus-thread-sort-by-random
6860 @vindex gnus-thread-sort-functions
6861 @findex gnus-thread-sort-by-most-recent-thread
6862 If you are using a threaded summary display, you can sort the threads by
6863 setting @code{gnus-thread-sort-functions}, which can be either a single
6864 function, a list of functions, or a list containing functions and
6865 @code{(not some-function)} elements.
6867 By default, sorting is done on article numbers. Ready-made sorting
6868 predicate functions include @code{gnus-thread-sort-by-number},
6869 @code{gnus-thread-sort-by-author}, @code{gnus-thread-sort-by-subject},
6870 @code{gnus-thread-sort-by-date}, @code{gnus-thread-sort-by-score},
6871 @code{gnus-thread-sort-by-most-recent-number},
6872 @code{gnus-thread-sort-by-most-recent-date},
6873 @code{gnus-thread-sort-by-random} and
6874 @code{gnus-thread-sort-by-total-score}.
6876 Each function takes two threads and returns non-@code{nil} if the first
6877 thread should be sorted before the other. Note that sorting really is
6878 normally done by looking only at the roots of each thread.
6880 If you use more than one function, the primary sort key should be the
6881 last function in the list. You should probably always include
6882 @code{gnus-thread-sort-by-number} in the list of sorting
6883 functions---preferably first. This will ensure that threads that are
6884 equal with respect to the other sort criteria will be displayed in
6885 ascending article order.
6887 If you would like to sort by reverse score, then by subject, and finally
6888 by number, you could do something like:
6891 (setq gnus-thread-sort-functions
6892 '(gnus-thread-sort-by-number
6893 gnus-thread-sort-by-subject
6894 (not gnus-thread-sort-by-total-score)))
6897 The threads that have highest score will be displayed first in the
6898 summary buffer. When threads have the same score, they will be sorted
6899 alphabetically. The threads that have the same score and the same
6900 subject will be sorted by number, which is (normally) the sequence in
6901 which the articles arrived.
6903 If you want to sort by score and then reverse arrival order, you could
6907 (setq gnus-thread-sort-functions
6909 (not (gnus-thread-sort-by-number t1 t2)))
6910 gnus-thread-sort-by-score))
6913 @vindex gnus-thread-score-function
6914 The function in the @code{gnus-thread-score-function} variable (default
6915 @code{+}) is used for calculating the total score of a thread. Useful
6916 functions might be @code{max}, @code{min}, or squared means, or whatever
6919 @findex gnus-article-sort-functions
6920 @findex gnus-article-sort-by-date
6921 @findex gnus-article-sort-by-score
6922 @findex gnus-article-sort-by-subject
6923 @findex gnus-article-sort-by-author
6924 @findex gnus-article-sort-by-random
6925 @findex gnus-article-sort-by-number
6926 If you are using an unthreaded display for some strange reason or
6927 other, you have to fiddle with the @code{gnus-article-sort-functions}
6928 variable. It is very similar to the
6929 @code{gnus-thread-sort-functions}, except that it uses slightly
6930 different functions for article comparison. Available sorting
6931 predicate functions are @code{gnus-article-sort-by-number},
6932 @code{gnus-article-sort-by-author},
6933 @code{gnus-article-sort-by-subject}, @code{gnus-article-sort-by-date},
6934 @code{gnus-article-sort-by-random}, and
6935 @code{gnus-article-sort-by-score}.
6937 If you want to sort an unthreaded summary display by subject, you could
6941 (setq gnus-article-sort-functions
6942 '(gnus-article-sort-by-number
6943 gnus-article-sort-by-subject))
6948 @node Asynchronous Fetching
6949 @section Asynchronous Article Fetching
6950 @cindex asynchronous article fetching
6951 @cindex article pre-fetch
6954 If you read your news from an @sc{nntp} server that's far away, the
6955 network latencies may make reading articles a chore. You have to wait
6956 for a while after pressing @kbd{n} to go to the next article before the
6957 article appears. Why can't Gnus just go ahead and fetch the article
6958 while you are reading the previous one? Why not, indeed.
6960 First, some caveats. There are some pitfalls to using asynchronous
6961 article fetching, especially the way Gnus does it.
6963 Let's say you are reading article 1, which is short, and article 2 is
6964 quite long, and you are not interested in reading that. Gnus does not
6965 know this, so it goes ahead and fetches article 2. You decide to read
6966 article 3, but since Gnus is in the process of fetching article 2, the
6967 connection is blocked.
6969 To avoid these situations, Gnus will open two (count 'em two)
6970 connections to the server. Some people may think this isn't a very nice
6971 thing to do, but I don't see any real alternatives. Setting up that
6972 extra connection takes some time, so Gnus startup will be slower.
6974 Gnus will fetch more articles than you will read. This will mean that
6975 the link between your machine and the @sc{nntp} server will become more
6976 loaded than if you didn't use article pre-fetch. The server itself will
6977 also become more loaded---both with the extra article requests, and the
6980 Ok, so now you know that you shouldn't really use this thing@dots{} unless
6983 @vindex gnus-asynchronous
6984 Here's how: Set @code{gnus-asynchronous} to @code{t}. The rest should
6985 happen automatically.
6987 @vindex gnus-use-article-prefetch
6988 You can control how many articles are to be pre-fetched by setting
6989 @code{gnus-use-article-prefetch}. This is 30 by default, which means
6990 that when you read an article in the group, the back end will pre-fetch
6991 the next 30 articles. If this variable is @code{t}, the back end will
6992 pre-fetch all the articles it can without bound. If it is
6993 @code{nil}, no pre-fetching will be done.
6995 @vindex gnus-async-prefetch-article-p
6996 @findex gnus-async-read-p
6997 There are probably some articles that you don't want to pre-fetch---read
6998 articles, for instance. The @code{gnus-async-prefetch-article-p}
6999 variable controls whether an article is to be pre-fetched. This
7000 function should return non-@code{nil} when the article in question is
7001 to be pre-fetched. The default is @code{gnus-async-read-p}, which
7002 returns @code{nil} on read articles. The function is called with an
7003 article data structure as the only parameter.
7005 If, for instance, you wish to pre-fetch only unread articles shorter
7006 than 100 lines, you could say something like:
7009 (defun my-async-short-unread-p (data)
7010 "Return non-nil for short, unread articles."
7011 (and (gnus-data-unread-p data)
7012 (< (mail-header-lines (gnus-data-header data))
7015 (setq gnus-async-prefetch-article-p 'my-async-short-unread-p)
7018 These functions will be called many, many times, so they should
7019 preferably be short and sweet to avoid slowing down Gnus too much.
7020 It's probably a good idea to byte-compile things like this.
7022 @vindex gnus-prefetched-article-deletion-strategy
7023 Articles have to be removed from the asynch buffer sooner or later. The
7024 @code{gnus-prefetched-article-deletion-strategy} says when to remove
7025 articles. This is a list that may contain the following elements:
7029 Remove articles when they are read.
7032 Remove articles when exiting the group.
7035 The default value is @code{(read exit)}.
7037 @c @vindex gnus-use-header-prefetch
7038 @c If @code{gnus-use-header-prefetch} is non-@code{nil}, prefetch articles
7039 @c from the next group.
7042 @node Article Caching
7043 @section Article Caching
7044 @cindex article caching
7047 If you have an @emph{extremely} slow @sc{nntp} connection, you may
7048 consider turning article caching on. Each article will then be stored
7049 locally under your home directory. As you may surmise, this could
7050 potentially use @emph{huge} amounts of disk space, as well as eat up all
7051 your inodes so fast it will make your head swim. In vodka.
7053 Used carefully, though, it could be just an easier way to save articles.
7055 @vindex gnus-use-long-file-name
7056 @vindex gnus-cache-directory
7057 @vindex gnus-use-cache
7058 To turn caching on, set @code{gnus-use-cache} to @code{t}. By default,
7059 all articles ticked or marked as dormant will then be copied
7060 over to your local cache (@code{gnus-cache-directory}). Whether this
7061 cache is flat or hierarchical is controlled by the
7062 @code{gnus-use-long-file-name} variable, as usual.
7064 When re-selecting a ticked or dormant article, it will be fetched from the
7065 cache instead of from the server. As articles in your cache will never
7066 expire, this might serve as a method of saving articles while still
7067 keeping them where they belong. Just mark all articles you want to save
7068 as dormant, and don't worry.
7070 When an article is marked as read, is it removed from the cache.
7072 @vindex gnus-cache-remove-articles
7073 @vindex gnus-cache-enter-articles
7074 The entering/removal of articles from the cache is controlled by the
7075 @code{gnus-cache-enter-articles} and @code{gnus-cache-remove-articles}
7076 variables. Both are lists of symbols. The first is @code{(ticked
7077 dormant)} by default, meaning that ticked and dormant articles will be
7078 put in the cache. The latter is @code{(read)} by default, meaning that
7079 articles marked as read are removed from the cache. Possibly
7080 symbols in these two lists are @code{ticked}, @code{dormant},
7081 @code{unread} and @code{read}.
7083 @findex gnus-jog-cache
7084 So where does the massive article-fetching and storing come into the
7085 picture? The @code{gnus-jog-cache} command will go through all
7086 subscribed newsgroups, request all unread articles, score them, and
7087 store them in the cache. You should only ever, ever ever ever, use this
7088 command if 1) your connection to the @sc{nntp} server is really, really,
7089 really slow and 2) you have a really, really, really huge disk.
7090 Seriously. One way to cut down on the number of articles downloaded is
7091 to score unwanted articles down and have them marked as read. They will
7092 not then be downloaded by this command.
7094 @vindex gnus-uncacheable-groups
7095 @vindex gnus-cacheable-groups
7096 It is likely that you do not want caching on all groups. For instance,
7097 if your @code{nnml} mail is located under your home directory, it makes no
7098 sense to cache it somewhere else under your home directory. Unless you
7099 feel that it's neat to use twice as much space.
7101 To limit the caching, you could set @code{gnus-cacheable-groups} to a
7102 regexp of groups to cache, @samp{^nntp} for instance, or set the
7103 @code{gnus-uncacheable-groups} regexp to @samp{^nnml}, for instance.
7104 Both variables are @code{nil} by default. If a group matches both
7105 variables, the group is not cached.
7107 @findex gnus-cache-generate-nov-databases
7108 @findex gnus-cache-generate-active
7109 @vindex gnus-cache-active-file
7110 The cache stores information on what articles it contains in its active
7111 file (@code{gnus-cache-active-file}). If this file (or any other parts
7112 of the cache) becomes all messed up for some reason or other, Gnus
7113 offers two functions that will try to set things right. @kbd{M-x
7114 gnus-cache-generate-nov-databases} will (re)build all the @sc{nov}
7115 files, and @kbd{gnus-cache-generate-active} will (re)generate the active
7118 @findex gnus-cache-move-cache
7119 @code{gnus-cache-move-cache} will move your whole
7120 @code{gnus-cache-directory} to some other location. You get asked to
7121 where, isn't that cool?
7123 @node Persistent Articles
7124 @section Persistent Articles
7125 @cindex persistent articles
7127 Closely related to article caching, we have @dfn{persistent articles}.
7128 In fact, it's just a different way of looking at caching, and much more
7129 useful in my opinion.
7131 Say you're reading a newsgroup, and you happen on to some valuable gem
7132 that you want to keep and treasure forever. You'd normally just save it
7133 (using one of the many saving commands) in some file. The problem with
7134 that is that it's just, well, yucky. Ideally you'd prefer just having
7135 the article remain in the group where you found it forever; untouched by
7136 the expiry going on at the news server.
7138 This is what a @dfn{persistent article} is---an article that just won't
7139 be deleted. It's implemented using the normal cache functions, but
7140 you use two explicit commands for managing persistent articles:
7146 @findex gnus-cache-enter-article
7147 Make the current article persistent (@code{gnus-cache-enter-article}).
7150 @kindex M-* (Summary)
7151 @findex gnus-cache-remove-article
7152 Remove the current article from the persistent articles
7153 (@code{gnus-cache-remove-article}). This will normally delete the
7157 Both these commands understand the process/prefix convention.
7159 To avoid having all ticked articles (and stuff) entered into the cache,
7160 you should set @code{gnus-use-cache} to @code{passive} if you're just
7161 interested in persistent articles:
7164 (setq gnus-use-cache 'passive)
7168 @node Article Backlog
7169 @section Article Backlog
7171 @cindex article backlog
7173 If you have a slow connection, but the idea of using caching seems
7174 unappealing to you (and it is, really), you can help the situation some
7175 by switching on the @dfn{backlog}. This is where Gnus will buffer
7176 already read articles so that it doesn't have to re-fetch articles
7177 you've already read. This only helps if you are in the habit of
7178 re-selecting articles you've recently read, of course. If you never do
7179 that, turning the backlog on will slow Gnus down a little bit, and
7180 increase memory usage some.
7182 @vindex gnus-keep-backlog
7183 If you set @code{gnus-keep-backlog} to a number @var{n}, Gnus will store
7184 at most @var{n} old articles in a buffer for later re-fetching. If this
7185 variable is non-@code{nil} and is not a number, Gnus will store
7186 @emph{all} read articles, which means that your Emacs will grow without
7187 bound before exploding and taking your machine down with you. I put
7188 that in there just to keep y'all on your toes.
7190 The default value is 20.
7193 @node Saving Articles
7194 @section Saving Articles
7195 @cindex saving articles
7197 Gnus can save articles in a number of ways. Below is the documentation
7198 for saving articles in a fairly straight-forward fashion (i.e., little
7199 processing of the article is done before it is saved). For a different
7200 approach (uudecoding, unsharing) you should use @code{gnus-uu}
7201 (@pxref{Decoding Articles}).
7203 For the commands listed here, the target is a file. If you want to
7204 save to a group, see the @kbd{B c} (@code{gnus-summary-copy-article})
7205 command (@pxref{Mail Group Commands}).
7207 @vindex gnus-save-all-headers
7208 If @code{gnus-save-all-headers} is non-@code{nil}, Gnus will not delete
7209 unwanted headers before saving the article.
7211 @vindex gnus-saved-headers
7212 If the preceding variable is @code{nil}, all headers that match the
7213 @code{gnus-saved-headers} regexp will be kept, while the rest will be
7214 deleted before saving.
7220 @kindex O o (Summary)
7222 @findex gnus-summary-save-article
7223 @c @icon{gnus-summary-save-article}
7224 Save the current article using the default article saver
7225 (@code{gnus-summary-save-article}).
7228 @kindex O m (Summary)
7229 @findex gnus-summary-save-article-mail
7230 Save the current article in mail format
7231 (@code{gnus-summary-save-article-mail}).
7234 @kindex O r (Summary)
7235 @findex gnus-summary-save-article-rmail
7236 Save the current article in rmail format
7237 (@code{gnus-summary-save-article-rmail}).
7240 @kindex O f (Summary)
7241 @findex gnus-summary-save-article-file
7242 @c @icon{gnus-summary-save-article-file}
7243 Save the current article in plain file format
7244 (@code{gnus-summary-save-article-file}).
7247 @kindex O F (Summary)
7248 @findex gnus-summary-write-article-file
7249 Write the current article in plain file format, overwriting any previous
7250 file contents (@code{gnus-summary-write-article-file}).
7253 @kindex O b (Summary)
7254 @findex gnus-summary-save-article-body-file
7255 Save the current article body in plain file format
7256 (@code{gnus-summary-save-article-body-file}).
7259 @kindex O h (Summary)
7260 @findex gnus-summary-save-article-folder
7261 Save the current article in mh folder format
7262 (@code{gnus-summary-save-article-folder}).
7265 @kindex O v (Summary)
7266 @findex gnus-summary-save-article-vm
7267 Save the current article in a VM folder
7268 (@code{gnus-summary-save-article-vm}).
7272 @kindex O p (Summary)
7274 @findex gnus-summary-pipe-output
7275 Save the current article in a pipe. Uhm, like, what I mean is---Pipe
7276 the current article to a process (@code{gnus-summary-pipe-output}).
7277 If given a symbolic prefix (@pxref{Symbolic Prefixes}), include the
7278 complete headers in the piped output.
7281 @kindex O P (Summary)
7282 @findex gnus-summary-muttprint
7283 @vindex gnus-summary-muttprint-program
7284 Save the current article into muttprint. That is, print it using the
7285 external program Muttprint (see
7286 @uref{http://muttprint.sourceforge.net/}). The program name and
7287 options to use is controlled by the variable
7288 @code{gnus-summary-muttprint-program}. (@code{gnus-summary-muttprint}).
7292 @vindex gnus-prompt-before-saving
7293 All these commands use the process/prefix convention
7294 (@pxref{Process/Prefix}). If you save bunches of articles using these
7295 functions, you might get tired of being prompted for files to save each
7296 and every article in. The prompting action is controlled by
7297 the @code{gnus-prompt-before-saving} variable, which is @code{always} by
7298 default, giving you that excessive prompting action you know and
7299 loathe. If you set this variable to @code{t} instead, you'll be prompted
7300 just once for each series of articles you save. If you like to really
7301 have Gnus do all your thinking for you, you can even set this variable
7302 to @code{nil}, which means that you will never be prompted for files to
7303 save articles in. Gnus will simply save all the articles in the default
7307 @vindex gnus-default-article-saver
7308 You can customize the @code{gnus-default-article-saver} variable to make
7309 Gnus do what you want it to. You can use any of the six ready-made
7310 functions below, or you can create your own.
7314 @item gnus-summary-save-in-rmail
7315 @findex gnus-summary-save-in-rmail
7316 @vindex gnus-rmail-save-name
7317 @findex gnus-plain-save-name
7318 This is the default format, @dfn{babyl}. Uses the function in the
7319 @code{gnus-rmail-save-name} variable to get a file name to save the
7320 article in. The default is @code{gnus-plain-save-name}.
7322 @item gnus-summary-save-in-mail
7323 @findex gnus-summary-save-in-mail
7324 @vindex gnus-mail-save-name
7325 Save in a Unix mail (mbox) file. Uses the function in the
7326 @code{gnus-mail-save-name} variable to get a file name to save the
7327 article in. The default is @code{gnus-plain-save-name}.
7329 @item gnus-summary-save-in-file
7330 @findex gnus-summary-save-in-file
7331 @vindex gnus-file-save-name
7332 @findex gnus-numeric-save-name
7333 Append the article straight to an ordinary file. Uses the function in
7334 the @code{gnus-file-save-name} variable to get a file name to save the
7335 article in. The default is @code{gnus-numeric-save-name}.
7337 @item gnus-summary-write-to-file
7338 @findex gnus-summary-write-to-file
7339 Write the article straight to an ordinary file. The file is
7340 overwritten if it exists. Uses the function in the
7341 @code{gnus-file-save-name} variable to get a file name to save the
7342 article in. The default is @code{gnus-numeric-save-name}.
7344 @item gnus-summary-save-body-in-file
7345 @findex gnus-summary-save-body-in-file
7346 Append the article body to an ordinary file. Uses the function in the
7347 @code{gnus-file-save-name} variable to get a file name to save the
7348 article in. The default is @code{gnus-numeric-save-name}.
7350 @item gnus-summary-save-in-folder
7351 @findex gnus-summary-save-in-folder
7352 @findex gnus-folder-save-name
7353 @findex gnus-Folder-save-name
7354 @vindex gnus-folder-save-name
7357 Save the article to an MH folder using @code{rcvstore} from the MH
7358 library. Uses the function in the @code{gnus-folder-save-name} variable
7359 to get a file name to save the article in. The default is
7360 @code{gnus-folder-save-name}, but you can also use
7361 @code{gnus-Folder-save-name}, which creates capitalized names.
7363 @item gnus-summary-save-in-vm
7364 @findex gnus-summary-save-in-vm
7365 Save the article in a VM folder. You have to have the VM mail
7366 reader to use this setting.
7369 @vindex gnus-article-save-directory
7370 All of these functions, except for the last one, will save the article
7371 in the @code{gnus-article-save-directory}, which is initialized from the
7372 @code{SAVEDIR} environment variable. This is @file{~/News/} by
7375 As you can see above, the functions use different functions to find a
7376 suitable name of a file to save the article in. Below is a list of
7377 available functions that generate names:
7381 @item gnus-Numeric-save-name
7382 @findex gnus-Numeric-save-name
7383 File names like @file{~/News/Alt.andrea-dworkin/45}.
7385 @item gnus-numeric-save-name
7386 @findex gnus-numeric-save-name
7387 File names like @file{~/News/alt.andrea-dworkin/45}.
7389 @item gnus-Plain-save-name
7390 @findex gnus-Plain-save-name
7391 File names like @file{~/News/Alt.andrea-dworkin}.
7393 @item gnus-plain-save-name
7394 @findex gnus-plain-save-name
7395 File names like @file{~/News/alt.andrea-dworkin}.
7397 @item gnus-sender-save-name
7398 @findex gnus-sender-save-name
7399 File names like @file{~/News/larsi}.
7402 @vindex gnus-split-methods
7403 You can have Gnus suggest where to save articles by plonking a regexp into
7404 the @code{gnus-split-methods} alist. For instance, if you would like to
7405 save articles related to Gnus in the file @file{gnus-stuff}, and articles
7406 related to VM in @file{vm-stuff}, you could set this variable to something
7410 (("^Subject:.*gnus\\|^Newsgroups:.*gnus" "gnus-stuff")
7411 ("^Subject:.*vm\\|^Xref:.*vm" "vm-stuff")
7412 (my-choosing-function "../other-dir/my-stuff")
7413 ((equal gnus-newsgroup-name "mail.misc") "mail-stuff"))
7416 We see that this is a list where each element is a list that has two
7417 elements---the @dfn{match} and the @dfn{file}. The match can either be
7418 a string (in which case it is used as a regexp to match on the article
7419 head); it can be a symbol (which will be called as a function with the
7420 group name as a parameter); or it can be a list (which will be
7421 @code{eval}ed). If any of these actions have a non-@code{nil} result,
7422 the @dfn{file} will be used as a default prompt. In addition, the
7423 result of the operation itself will be used if the function or form
7424 called returns a string or a list of strings.
7426 You basically end up with a list of file names that might be used when
7427 saving the current article. (All ``matches'' will be used.) You will
7428 then be prompted for what you really want to use as a name, with file
7429 name completion over the results from applying this variable.
7431 This variable is @code{((gnus-article-archive-name))} by default, which
7432 means that Gnus will look at the articles it saves for an
7433 @code{Archive-name} line and use that as a suggestion for the file
7436 Here's an example function to clean up file names somewhat. If you have
7437 lots of mail groups called things like
7438 @samp{nnml:mail.whatever}, you may want to chop off the beginning of
7439 these group names before creating the file name to save to. The
7440 following will do just that:
7443 (defun my-save-name (group)
7444 (when (string-match "^nnml:mail." group)
7445 (substring group (match-end 0))))
7447 (setq gnus-split-methods
7448 '((gnus-article-archive-name)
7453 @vindex gnus-use-long-file-name
7454 Finally, you have the @code{gnus-use-long-file-name} variable. If it is
7455 @code{nil}, all the preceding functions will replace all periods
7456 (@samp{.}) in the group names with slashes (@samp{/})---which means that
7457 the functions will generate hierarchies of directories instead of having
7458 all the files in the top level directory
7459 (@file{~/News/alt/andrea-dworkin} instead of
7460 @file{~/News/alt.andrea-dworkin}.) This variable is @code{t} by default
7461 on most systems. However, for historical reasons, this is @code{nil} on
7462 Xenix and usg-unix-v machines by default.
7464 This function also affects kill and score file names. If this variable
7465 is a list, and the list contains the element @code{not-score}, long file
7466 names will not be used for score files, if it contains the element
7467 @code{not-save}, long file names will not be used for saving, and if it
7468 contains the element @code{not-kill}, long file names will not be used
7471 If you'd like to save articles in a hierarchy that looks something like
7475 (setq gnus-use-long-file-name '(not-save)) ; to get a hierarchy
7476 (setq gnus-default-article-saver
7477 'gnus-summary-save-in-file) ; no encoding
7480 Then just save with @kbd{o}. You'd then read this hierarchy with
7481 ephemeral @code{nneething} groups---@kbd{G D} in the group buffer, and
7482 the top level directory as the argument (@file{~/News/}). Then just walk
7483 around to the groups/directories with @code{nneething}.
7486 @node Decoding Articles
7487 @section Decoding Articles
7488 @cindex decoding articles
7490 Sometime users post articles (or series of articles) that have been
7491 encoded in some way or other. Gnus can decode them for you.
7494 * Uuencoded Articles:: Uudecode articles.
7495 * Shell Archives:: Unshar articles.
7496 * PostScript Files:: Split PostScript.
7497 * Other Files:: Plain save and binhex.
7498 * Decoding Variables:: Variables for a happy decoding.
7499 * Viewing Files:: You want to look at the result of the decoding?
7503 @cindex article series
7504 All these functions use the process/prefix convention
7505 (@pxref{Process/Prefix}) for finding out what articles to work on, with
7506 the extension that a ``single article'' means ``a single series''. Gnus
7507 can find out by itself what articles belong to a series, decode all the
7508 articles and unpack/view/save the resulting file(s).
7510 Gnus guesses what articles are in the series according to the following
7511 simplish rule: The subjects must be (nearly) identical, except for the
7512 last two numbers of the line. (Spaces are largely ignored, however.)
7514 For example: If you choose a subject called @samp{cat.gif (2/3)}, Gnus
7515 will find all the articles that match the regexp @samp{^cat.gif
7516 ([0-9]+/[0-9]+).*$}.
7518 Subjects that are non-standard, like @samp{cat.gif (2/3) Part 6 of a
7519 series}, will not be properly recognized by any of the automatic viewing
7520 commands, and you have to mark the articles manually with @kbd{#}.
7523 @node Uuencoded Articles
7524 @subsection Uuencoded Articles
7526 @cindex uuencoded articles
7531 @kindex X u (Summary)
7532 @findex gnus-uu-decode-uu
7533 @c @icon{gnus-uu-decode-uu}
7534 Uudecodes the current series (@code{gnus-uu-decode-uu}).
7537 @kindex X U (Summary)
7538 @findex gnus-uu-decode-uu-and-save
7539 Uudecodes and saves the current series
7540 (@code{gnus-uu-decode-uu-and-save}).
7543 @kindex X v u (Summary)
7544 @findex gnus-uu-decode-uu-view
7545 Uudecodes and views the current series (@code{gnus-uu-decode-uu-view}).
7548 @kindex X v U (Summary)
7549 @findex gnus-uu-decode-uu-and-save-view
7550 Uudecodes, views and saves the current series
7551 (@code{gnus-uu-decode-uu-and-save-view}).
7555 Remember that these all react to the presence of articles marked with
7556 the process mark. If, for instance, you'd like to decode and save an
7557 entire newsgroup, you'd typically do @kbd{M P a}
7558 (@code{gnus-uu-mark-all}) and then @kbd{X U}
7559 (@code{gnus-uu-decode-uu-and-save}).
7561 All this is very much different from how @code{gnus-uu} worked with
7562 @sc{gnus 4.1}, where you had explicit keystrokes for everything under
7563 the sun. This version of @code{gnus-uu} generally assumes that you mark
7564 articles in some way (@pxref{Setting Process Marks}) and then press
7567 @vindex gnus-uu-notify-files
7568 Note: When trying to decode articles that have names matching
7569 @code{gnus-uu-notify-files}, which is hard-coded to
7570 @samp{[Cc][Ii][Nn][Dd][Yy][0-9]+.\\(gif\\|jpg\\)}, @code{gnus-uu} will
7571 automatically post an article on @samp{comp.unix.wizards} saying that
7572 you have just viewed the file in question. This feature can't be turned
7576 @node Shell Archives
7577 @subsection Shell Archives
7579 @cindex shell archives
7580 @cindex shared articles
7582 Shell archives (``shar files'') used to be a popular way to distribute
7583 sources, but it isn't used all that much today. In any case, we have
7584 some commands to deal with these:
7589 @kindex X s (Summary)
7590 @findex gnus-uu-decode-unshar
7591 Unshars the current series (@code{gnus-uu-decode-unshar}).
7594 @kindex X S (Summary)
7595 @findex gnus-uu-decode-unshar-and-save
7596 Unshars and saves the current series (@code{gnus-uu-decode-unshar-and-save}).
7599 @kindex X v s (Summary)
7600 @findex gnus-uu-decode-unshar-view
7601 Unshars and views the current series (@code{gnus-uu-decode-unshar-view}).
7604 @kindex X v S (Summary)
7605 @findex gnus-uu-decode-unshar-and-save-view
7606 Unshars, views and saves the current series
7607 (@code{gnus-uu-decode-unshar-and-save-view}).
7611 @node PostScript Files
7612 @subsection PostScript Files
7618 @kindex X p (Summary)
7619 @findex gnus-uu-decode-postscript
7620 Unpack the current PostScript series (@code{gnus-uu-decode-postscript}).
7623 @kindex X P (Summary)
7624 @findex gnus-uu-decode-postscript-and-save
7625 Unpack and save the current PostScript series
7626 (@code{gnus-uu-decode-postscript-and-save}).
7629 @kindex X v p (Summary)
7630 @findex gnus-uu-decode-postscript-view
7631 View the current PostScript series
7632 (@code{gnus-uu-decode-postscript-view}).
7635 @kindex X v P (Summary)
7636 @findex gnus-uu-decode-postscript-and-save-view
7637 View and save the current PostScript series
7638 (@code{gnus-uu-decode-postscript-and-save-view}).
7643 @subsection Other Files
7647 @kindex X o (Summary)
7648 @findex gnus-uu-decode-save
7649 Save the current series
7650 (@code{gnus-uu-decode-save}).
7653 @kindex X b (Summary)
7654 @findex gnus-uu-decode-binhex
7655 Unbinhex the current series (@code{gnus-uu-decode-binhex}). This
7656 doesn't really work yet.
7660 @node Decoding Variables
7661 @subsection Decoding Variables
7663 Adjective, not verb.
7666 * Rule Variables:: Variables that say how a file is to be viewed.
7667 * Other Decode Variables:: Other decode variables.
7668 * Uuencoding and Posting:: Variables for customizing uuencoding.
7672 @node Rule Variables
7673 @subsubsection Rule Variables
7674 @cindex rule variables
7676 Gnus uses @dfn{rule variables} to decide how to view a file. All these
7677 variables are of the form
7680 (list '(regexp1 command2)
7687 @item gnus-uu-user-view-rules
7688 @vindex gnus-uu-user-view-rules
7690 This variable is consulted first when viewing files. If you wish to use,
7691 for instance, @code{sox} to convert an @file{.au} sound file, you could
7694 (setq gnus-uu-user-view-rules
7695 (list '("\\\\.au$" "sox %s -t .aiff > /dev/audio")))
7698 @item gnus-uu-user-view-rules-end
7699 @vindex gnus-uu-user-view-rules-end
7700 This variable is consulted if Gnus couldn't make any matches from the
7701 user and default view rules.
7703 @item gnus-uu-user-archive-rules
7704 @vindex gnus-uu-user-archive-rules
7705 This variable can be used to say what commands should be used to unpack
7710 @node Other Decode Variables
7711 @subsubsection Other Decode Variables
7714 @vindex gnus-uu-grabbed-file-functions
7716 @item gnus-uu-grabbed-file-functions
7717 All functions in this list will be called right after each file has been
7718 successfully decoded---so that you can move or view files right away,
7719 and don't have to wait for all files to be decoded before you can do
7720 anything. Ready-made functions you can put in this list are:
7724 @item gnus-uu-grab-view
7725 @findex gnus-uu-grab-view
7728 @item gnus-uu-grab-move
7729 @findex gnus-uu-grab-move
7730 Move the file (if you're using a saving function.)
7733 @item gnus-uu-be-dangerous
7734 @vindex gnus-uu-be-dangerous
7735 Specifies what to do if unusual situations arise during decoding. If
7736 @code{nil}, be as conservative as possible. If @code{t}, ignore things
7737 that didn't work, and overwrite existing files. Otherwise, ask each
7740 @item gnus-uu-ignore-files-by-name
7741 @vindex gnus-uu-ignore-files-by-name
7742 Files with name matching this regular expression won't be viewed.
7744 @item gnus-uu-ignore-files-by-type
7745 @vindex gnus-uu-ignore-files-by-type
7746 Files with a @sc{mime} type matching this variable won't be viewed.
7747 Note that Gnus tries to guess what type the file is based on the name.
7748 @code{gnus-uu} is not a @sc{mime} package (yet), so this is slightly
7751 @item gnus-uu-tmp-dir
7752 @vindex gnus-uu-tmp-dir
7753 Where @code{gnus-uu} does its work.
7755 @item gnus-uu-do-not-unpack-archives
7756 @vindex gnus-uu-do-not-unpack-archives
7757 Non-@code{nil} means that @code{gnus-uu} won't peek inside archives
7758 looking for files to display.
7760 @item gnus-uu-view-and-save
7761 @vindex gnus-uu-view-and-save
7762 Non-@code{nil} means that the user will always be asked to save a file
7765 @item gnus-uu-ignore-default-view-rules
7766 @vindex gnus-uu-ignore-default-view-rules
7767 Non-@code{nil} means that @code{gnus-uu} will ignore the default viewing
7770 @item gnus-uu-ignore-default-archive-rules
7771 @vindex gnus-uu-ignore-default-archive-rules
7772 Non-@code{nil} means that @code{gnus-uu} will ignore the default archive
7775 @item gnus-uu-kill-carriage-return
7776 @vindex gnus-uu-kill-carriage-return
7777 Non-@code{nil} means that @code{gnus-uu} will strip all carriage returns
7780 @item gnus-uu-unmark-articles-not-decoded
7781 @vindex gnus-uu-unmark-articles-not-decoded
7782 Non-@code{nil} means that @code{gnus-uu} will mark unsuccessfully
7783 decoded articles as unread.
7785 @item gnus-uu-correct-stripped-uucode
7786 @vindex gnus-uu-correct-stripped-uucode
7787 Non-@code{nil} means that @code{gnus-uu} will @emph{try} to fix
7788 uuencoded files that have had trailing spaces deleted.
7790 @item gnus-uu-pre-uudecode-hook
7791 @vindex gnus-uu-pre-uudecode-hook
7792 Hook run before sending a message to @code{uudecode}.
7794 @item gnus-uu-view-with-metamail
7795 @vindex gnus-uu-view-with-metamail
7797 Non-@code{nil} means that @code{gnus-uu} will ignore the viewing
7798 commands defined by the rule variables and just fudge a @sc{mime}
7799 content type based on the file name. The result will be fed to
7800 @code{metamail} for viewing.
7802 @item gnus-uu-save-in-digest
7803 @vindex gnus-uu-save-in-digest
7804 Non-@code{nil} means that @code{gnus-uu}, when asked to save without
7805 decoding, will save in digests. If this variable is @code{nil},
7806 @code{gnus-uu} will just save everything in a file without any
7807 embellishments. The digesting almost conforms to RFC 1153---no easy way
7808 to specify any meaningful volume and issue numbers were found, so I
7809 simply dropped them.
7814 @node Uuencoding and Posting
7815 @subsubsection Uuencoding and Posting
7819 @item gnus-uu-post-include-before-composing
7820 @vindex gnus-uu-post-include-before-composing
7821 Non-@code{nil} means that @code{gnus-uu} will ask for a file to encode
7822 before you compose the article. If this variable is @code{t}, you can
7823 either include an encoded file with @kbd{C-c C-i} or have one included
7824 for you when you post the article.
7826 @item gnus-uu-post-length
7827 @vindex gnus-uu-post-length
7828 Maximum length of an article. The encoded file will be split into how
7829 many articles it takes to post the entire file.
7831 @item gnus-uu-post-threaded
7832 @vindex gnus-uu-post-threaded
7833 Non-@code{nil} means that @code{gnus-uu} will post the encoded file in a
7834 thread. This may not be smart, as no other decoder I have seen is able
7835 to follow threads when collecting uuencoded articles. (Well, I have
7836 seen one package that does that---@code{gnus-uu}, but somehow, I don't
7837 think that counts@dots{}) Default is @code{nil}.
7839 @item gnus-uu-post-separate-description
7840 @vindex gnus-uu-post-separate-description
7841 Non-@code{nil} means that the description will be posted in a separate
7842 article. The first article will typically be numbered (0/x). If this
7843 variable is @code{nil}, the description the user enters will be included
7844 at the beginning of the first article, which will be numbered (1/x).
7845 Default is @code{t}.
7851 @subsection Viewing Files
7852 @cindex viewing files
7853 @cindex pseudo-articles
7855 After decoding, if the file is some sort of archive, Gnus will attempt
7856 to unpack the archive and see if any of the files in the archive can be
7857 viewed. For instance, if you have a gzipped tar file @file{pics.tar.gz}
7858 containing the files @file{pic1.jpg} and @file{pic2.gif}, Gnus will
7859 uncompress and de-tar the main file, and then view the two pictures.
7860 This unpacking process is recursive, so if the archive contains archives
7861 of archives, it'll all be unpacked.
7863 Finally, Gnus will normally insert a @dfn{pseudo-article} for each
7864 extracted file into the summary buffer. If you go to these
7865 ``articles'', you will be prompted for a command to run (usually Gnus
7866 will make a suggestion), and then the command will be run.
7868 @vindex gnus-view-pseudo-asynchronously
7869 If @code{gnus-view-pseudo-asynchronously} is @code{nil}, Emacs will wait
7870 until the viewing is done before proceeding.
7872 @vindex gnus-view-pseudos
7873 If @code{gnus-view-pseudos} is @code{automatic}, Gnus will not insert
7874 the pseudo-articles into the summary buffer, but view them
7875 immediately. If this variable is @code{not-confirm}, the user won't even
7876 be asked for a confirmation before viewing is done.
7878 @vindex gnus-view-pseudos-separately
7879 If @code{gnus-view-pseudos-separately} is non-@code{nil}, one
7880 pseudo-article will be created for each file to be viewed. If
7881 @code{nil}, all files that use the same viewing command will be given as
7882 a list of parameters to that command.
7884 @vindex gnus-insert-pseudo-articles
7885 If @code{gnus-insert-pseudo-articles} is non-@code{nil}, insert
7886 pseudo-articles when decoding. It is @code{t} by default.
7888 So; there you are, reading your @emph{pseudo-articles} in your
7889 @emph{virtual newsgroup} from the @emph{virtual server}; and you think:
7890 Why isn't anything real anymore? How did we get here?
7893 @node Article Treatment
7894 @section Article Treatment
7896 Reading through this huge manual, you may have quite forgotten that the
7897 object of newsreaders is to actually, like, read what people have
7898 written. Reading articles. Unfortunately, people are quite bad at
7899 writing, so there are tons of functions and variables to make reading
7900 these articles easier.
7903 * Article Highlighting:: You want to make the article look like fruit salad.
7904 * Article Fontisizing:: Making emphasized text look nice.
7905 * Article Hiding:: You also want to make certain info go away.
7906 * Article Washing:: Lots of way-neat functions to make life better.
7907 * Article Header:: Doing various header transformations.
7908 * Article Buttons:: Click on URLs, Message-IDs, addresses and the like.
7909 * Article Button Levels:: Controlling appearance of buttons.
7910 * Article Date:: Grumble, UT!
7911 * Article Display:: Display various stuff---X-Face, Picons, Smileys
7912 * Article Signature:: What is a signature?
7913 * Article Miscellania:: Various other stuff.
7917 @node Article Highlighting
7918 @subsection Article Highlighting
7919 @cindex highlighting
7921 Not only do you want your article buffer to look like fruit salad, but
7922 you want it to look like technicolor fruit salad.
7927 @kindex W H a (Summary)
7928 @findex gnus-article-highlight
7929 @findex gnus-article-maybe-highlight
7930 Do much highlighting of the current article
7931 (@code{gnus-article-highlight}). This function highlights header, cited
7932 text, the signature, and adds buttons to the body and the head.
7935 @kindex W H h (Summary)
7936 @findex gnus-article-highlight-headers
7937 @vindex gnus-header-face-alist
7938 Highlight the headers (@code{gnus-article-highlight-headers}). The
7939 highlighting will be done according to the @code{gnus-header-face-alist}
7940 variable, which is a list where each element has the form
7941 @code{(@var{regexp} @var{name} @var{content})}.
7942 @var{regexp} is a regular expression for matching the
7943 header, @var{name} is the face used for highlighting the header name
7944 (@pxref{Faces and Fonts}) and @var{content} is the face for highlighting
7945 the header value. The first match made will be used. Note that
7946 @var{regexp} shouldn't have @samp{^} prepended---Gnus will add one.
7949 @kindex W H c (Summary)
7950 @findex gnus-article-highlight-citation
7951 Highlight cited text (@code{gnus-article-highlight-citation}).
7953 Some variables to customize the citation highlights:
7956 @vindex gnus-cite-parse-max-size
7958 @item gnus-cite-parse-max-size
7959 If the article size if bigger than this variable (which is 25000 by
7960 default), no citation highlighting will be performed.
7962 @item gnus-cite-max-prefix
7963 @vindex gnus-cite-max-prefix
7964 Maximum possible length for a citation prefix (default 20).
7966 @item gnus-cite-face-list
7967 @vindex gnus-cite-face-list
7968 List of faces used for highlighting citations (@pxref{Faces and Fonts}).
7969 When there are citations from multiple articles in the same message,
7970 Gnus will try to give each citation from each article its own face.
7971 This should make it easier to see who wrote what.
7973 @item gnus-supercite-regexp
7974 @vindex gnus-supercite-regexp
7975 Regexp matching normal Supercite attribution lines.
7977 @item gnus-supercite-secondary-regexp
7978 @vindex gnus-supercite-secondary-regexp
7979 Regexp matching mangled Supercite attribution lines.
7981 @item gnus-cite-minimum-match-count
7982 @vindex gnus-cite-minimum-match-count
7983 Minimum number of identical prefixes we have to see before we believe
7984 that it's a citation.
7986 @item gnus-cite-attribution-prefix
7987 @vindex gnus-cite-attribution-prefix
7988 Regexp matching the beginning of an attribution line.
7990 @item gnus-cite-attribution-suffix
7991 @vindex gnus-cite-attribution-suffix
7992 Regexp matching the end of an attribution line.
7994 @item gnus-cite-attribution-face
7995 @vindex gnus-cite-attribution-face
7996 Face used for attribution lines. It is merged with the face for the
7997 cited text belonging to the attribution.
8003 @kindex W H s (Summary)
8004 @vindex gnus-signature-separator
8005 @vindex gnus-signature-face
8006 @findex gnus-article-highlight-signature
8007 Highlight the signature (@code{gnus-article-highlight-signature}).
8008 Everything after @code{gnus-signature-separator} (@pxref{Article
8009 Signature}) in an article will be considered a signature and will be
8010 highlighted with @code{gnus-signature-face}, which is @code{italic} by
8015 @xref{Customizing Articles}, for how to highlight articles automatically.
8018 @node Article Fontisizing
8019 @subsection Article Fontisizing
8021 @cindex article emphasis
8023 @findex gnus-article-emphasize
8024 @kindex W e (Summary)
8025 People commonly add emphasis to words in news articles by writing things
8026 like @samp{_this_} or @samp{*this*} or @samp{/this/}. Gnus can make
8027 this look nicer by running the article through the @kbd{W e}
8028 (@code{gnus-article-emphasize}) command.
8030 @vindex gnus-emphasis-alist
8031 How the emphasis is computed is controlled by the
8032 @code{gnus-emphasis-alist} variable. This is an alist where the first
8033 element is a regular expression to be matched. The second is a number
8034 that says what regular expression grouping is used to find the entire
8035 emphasized word. The third is a number that says what regexp grouping
8036 should be displayed and highlighted. (The text between these two
8037 groupings will be hidden.) The fourth is the face used for
8041 (setq gnus-emphasis-alist
8042 '(("_\\(\\w+\\)_" 0 1 gnus-emphasis-underline)
8043 ("\\*\\(\\w+\\)\\*" 0 1 gnus-emphasis-bold)))
8052 @vindex gnus-emphasis-underline
8053 @vindex gnus-emphasis-bold
8054 @vindex gnus-emphasis-italic
8055 @vindex gnus-emphasis-underline-bold
8056 @vindex gnus-emphasis-underline-italic
8057 @vindex gnus-emphasis-bold-italic
8058 @vindex gnus-emphasis-underline-bold-italic
8059 By default, there are seven rules, and they use the following faces:
8060 @code{gnus-emphasis-bold}, @code{gnus-emphasis-italic},
8061 @code{gnus-emphasis-underline}, @code{gnus-emphasis-bold-italic},
8062 @code{gnus-emphasis-underline-italic},
8063 @code{gnus-emphasis-underline-bold}, and
8064 @code{gnus-emphasis-underline-bold-italic}.
8066 If you want to change these faces, you can either use @kbd{M-x
8067 customize}, or you can use @code{copy-face}. For instance, if you want
8068 to make @code{gnus-emphasis-italic} use a red face instead, you could
8072 (copy-face 'red 'gnus-emphasis-italic)
8075 @vindex gnus-group-highlight-words-alist
8077 If you want to highlight arbitrary words, you can use the
8078 @code{gnus-group-highlight-words-alist} variable, which uses the same
8079 syntax as @code{gnus-emphasis-alist}. The @code{highlight-words} group
8080 parameter (@pxref{Group Parameters}) can also be used.
8082 @xref{Customizing Articles}, for how to fontize articles automatically.
8085 @node Article Hiding
8086 @subsection Article Hiding
8087 @cindex article hiding
8089 Or rather, hiding certain things in each article. There usually is much
8090 too much cruft in most articles.
8095 @kindex W W a (Summary)
8096 @findex gnus-article-hide
8097 Do quite a lot of hiding on the article buffer
8098 (@kbd{gnus-article-hide}). In particular, this function will hide
8099 headers, PGP, cited text and the signature.
8102 @kindex W W h (Summary)
8103 @findex gnus-article-hide-headers
8104 Hide headers (@code{gnus-article-hide-headers}). @xref{Hiding
8108 @kindex W W b (Summary)
8109 @findex gnus-article-hide-boring-headers
8110 Hide headers that aren't particularly interesting
8111 (@code{gnus-article-hide-boring-headers}). @xref{Hiding Headers}.
8114 @kindex W W s (Summary)
8115 @findex gnus-article-hide-signature
8116 Hide signature (@code{gnus-article-hide-signature}). @xref{Article
8120 @kindex W W l (Summary)
8121 @findex gnus-article-hide-list-identifiers
8122 @vindex gnus-list-identifiers
8123 Strip list identifiers specified in @code{gnus-list-identifiers}. These
8124 are strings some mailing list servers add to the beginning of all
8125 @code{Subject} headers---for example, @samp{[zebra 4711]}. Any leading
8126 @samp{Re: } is skipped before stripping. @code{gnus-list-identifiers}
8127 may not contain @code{\\(..\\)}.
8131 @item gnus-list-identifiers
8132 @vindex gnus-list-identifiers
8133 A regular expression that matches list identifiers to be removed from
8134 subject. This can also be a list of regular expressions.
8139 @kindex W W P (Summary)
8140 @findex gnus-article-hide-pem
8141 Hide @sc{pem} (privacy enhanced messages) cruft
8142 (@code{gnus-article-hide-pem}).
8145 @kindex W W B (Summary)
8146 @findex gnus-article-strip-banner
8147 @vindex gnus-article-banner-alist
8148 @vindex gnus-article-address-banner-alist
8151 @cindex stripping advertisements
8152 @cindex advertisements
8153 Strip the banner specified by the @code{banner} group parameter
8154 (@code{gnus-article-strip-banner}). This is mainly used to hide those
8155 annoying banners and/or signatures that some mailing lists and moderated
8156 groups adds to all the messages. The way to use this function is to add
8157 the @code{banner} group parameter (@pxref{Group Parameters}) to the
8158 group you want banners stripped from. The parameter either be a string,
8159 which will be interpreted as a regular expression matching text to be
8160 removed, or the symbol @code{signature}, meaning that the (last)
8161 signature should be removed, or other symbol, meaning that the
8162 corresponding regular expression in @code{gnus-article-banner-alist} is
8165 Regardless of a group, you can hide things like advertisements only when
8166 the sender of an article has a certain mail address specified in
8167 @code{gnus-article-address-banner-alist}.
8171 @item gnus-article-address-banner-alist
8172 @vindex gnus-article-address-banner-alist
8173 Alist of mail addresses and banners. Each element has the form
8174 @code{(@var{address} . @var{banner})}, where @var{address} is a regexp
8175 matching a mail address in the From header, @var{banner} is one of a
8176 symbol @code{signature}, an item in @code{gnus-article-banner-alist},
8177 a regexp and @code{nil}. If @var{address} matches author's mail
8178 address, it will remove things like advertisements. For example, if a
8179 sender has the mail address @samp{hail@@yoo-hoo.co.jp} and there is a
8180 banner something like @samp{Do You Yoo-hoo!?} in all articles he
8181 sends, you can use the following element to remove them:
8184 ("@@yoo-hoo\\.co\\.jp\\'" . "\n_+\nDo You Yoo-hoo!\\?\n.*\n.*\n")
8190 @kindex W W c (Summary)
8191 @findex gnus-article-hide-citation
8192 Hide citation (@code{gnus-article-hide-citation}). Some variables for
8193 customizing the hiding:
8197 @item gnus-cited-opened-text-button-line-format
8198 @itemx gnus-cited-closed-text-button-line-format
8199 @vindex gnus-cited-closed-text-button-line-format
8200 @vindex gnus-cited-opened-text-button-line-format
8201 Gnus adds buttons to show where the cited text has been hidden, and to
8202 allow toggle hiding the text. The format of the variable is specified
8203 by these format-like variable (@pxref{Formatting Variables}). These
8208 Starting point of the hidden text.
8210 Ending point of the hidden text.
8212 Number of characters in the hidden region.
8214 Number of lines of hidden text.
8217 @item gnus-cited-lines-visible
8218 @vindex gnus-cited-lines-visible
8219 The number of lines at the beginning of the cited text to leave
8220 shown. This can also be a cons cell with the number of lines at the top
8221 and bottom of the text, respectively, to remain visible.
8226 @kindex W W C-c (Summary)
8227 @findex gnus-article-hide-citation-maybe
8229 Hide citation (@code{gnus-article-hide-citation-maybe}) depending on the
8230 following two variables:
8233 @item gnus-cite-hide-percentage
8234 @vindex gnus-cite-hide-percentage
8235 If the cited text is of a bigger percentage than this variable (default
8236 50), hide the cited text.
8238 @item gnus-cite-hide-absolute
8239 @vindex gnus-cite-hide-absolute
8240 The cited text must have at least this length (default 10) before it
8245 @kindex W W C (Summary)
8246 @findex gnus-article-hide-citation-in-followups
8247 Hide cited text in articles that aren't roots
8248 (@code{gnus-article-hide-citation-in-followups}). This isn't very
8249 useful as an interactive command, but might be a handy function to stick
8250 have happen automatically (@pxref{Customizing Articles}).
8254 All these ``hiding'' commands are toggles, but if you give a negative
8255 prefix to these commands, they will show what they have previously
8256 hidden. If you give a positive prefix, they will always hide.
8258 Also @pxref{Article Highlighting} for further variables for
8259 citation customization.
8261 @xref{Customizing Articles}, for how to hide article elements
8265 @node Article Washing
8266 @subsection Article Washing
8268 @cindex article washing
8270 We call this ``article washing'' for a really good reason. Namely, the
8271 @kbd{A} key was taken, so we had to use the @kbd{W} key instead.
8273 @dfn{Washing} is defined by us as ``changing something from something to
8274 something else'', but normally results in something looking better.
8277 @xref{Customizing Articles}, if you want to change how Gnus displays
8278 articles by default.
8283 This is not really washing, it's sort of the opposite of washing. If
8284 you type this, you see the article exactly as it exists on disk or on
8288 Force redisplaying of the current article
8289 (@code{gnus-summary-show-article}). This is also not really washing.
8290 If you type this, you see the article without any previously applied
8291 interactive Washing functions but with all default treatments
8292 (@pxref{Customizing Articles}).
8295 @kindex W l (Summary)
8296 @findex gnus-summary-stop-page-breaking
8297 Remove page breaks from the current article
8298 (@code{gnus-summary-stop-page-breaking}). @xref{Misc Article}, for page
8302 @kindex W r (Summary)
8303 @findex gnus-summary-caesar-message
8304 @c @icon{gnus-summary-caesar-message}
8305 Do a Caesar rotate (rot13) on the article buffer
8306 (@code{gnus-summary-caesar-message}).
8307 Unreadable articles that tell you to read them with Caesar rotate or rot13.
8308 (Typically offensive jokes and such.)
8310 It's commonly called ``rot13'' because each letter is rotated 13
8311 positions in the alphabet, e. g. @samp{B} (letter #2) -> @samp{O} (letter
8312 #15). It is sometimes referred to as ``Caesar rotate'' because Caesar
8313 is rumored to have employed this form of, uh, somewhat weak encryption.
8316 @kindex W m (Summary)
8317 @findex gnus-summary-morse-message
8318 Morse decode the article buffer (@code{gnus-summary-morse-message}).
8322 @kindex W t (Summary)
8324 @findex gnus-summary-toggle-header
8325 Toggle whether to display all headers in the article buffer
8326 (@code{gnus-summary-toggle-header}).
8329 @kindex W v (Summary)
8330 @findex gnus-summary-verbose-headers
8331 Toggle whether to display all headers in the article buffer permanently
8332 (@code{gnus-summary-verbose-headers}).
8335 @kindex W o (Summary)
8336 @findex gnus-article-treat-overstrike
8337 Treat overstrike (@code{gnus-article-treat-overstrike}).
8340 @kindex W d (Summary)
8341 @findex gnus-article-treat-dumbquotes
8342 @vindex gnus-article-dumbquotes-map
8344 @cindex M****s*** sm*rtq**t*s
8346 Treat M****s*** sm*rtq**t*s according to
8347 @code{gnus-article-dumbquotes-map}
8348 (@code{gnus-article-treat-dumbquotes}). Note that this function guesses
8349 whether a character is a sm*rtq**t* or not, so it should only be used
8352 Sm*rtq**t*s are M****s***'s unilateral extension to the character map in
8353 an attempt to provide more quoting characters. If you see something
8354 like @code{\222} or @code{\264} where you're expecting some kind of
8355 apostrophe or quotation mark, then try this wash.
8358 @kindex W Y f (Summary)
8359 @findex gnus-article-outlook-deuglify-article
8360 @cindex Outlook Express
8361 Full deuglify of broken Outlook (Express) articles: Treat dumbquotes,
8362 unwrap lines, repair attribution and rearrange citation.
8363 (@code{gnus-article-outlook-deuglify-article}).
8366 @kindex W Y u (Summary)
8367 @findex gnus-article-outlook-unwrap-lines
8368 @vindex gnus-outlook-deuglify-unwrap-min
8369 @vindex gnus-outlook-deuglify-unwrap-max
8370 Unwrap lines that appear to be wrapped citation lines. You can control
8371 what lines will be unwrapped by frobbing
8372 @code{gnus-outlook-deuglify-unwrap-min} and
8373 @code{gnus-outlook-deuglify-unwrap-max}, indicating the miminum and
8374 maximum length of an unwrapped citation line.
8375 (@code{gnus-article-outlook-unwrap-lines}).
8378 @kindex W Y a (Summary)
8379 @findex gnus-article-outlook-repair-attribution
8380 Repair a broken attribution line.
8381 (@code{gnus-article-outlook-repair-attribution}).
8384 @kindex W Y c (Summary)
8385 @findex gnus-article-outlook-rearrange-citation
8386 Repair broken citations by rearranging the text.
8387 (@code{gnus-article-outlook-rearrange-citation}).
8390 @kindex W w (Summary)
8391 @findex gnus-article-fill-cited-article
8392 Do word wrap (@code{gnus-article-fill-cited-article}).
8394 You can give the command a numerical prefix to specify the width to use
8398 @kindex W Q (Summary)
8399 @findex gnus-article-fill-long-lines
8400 Fill long lines (@code{gnus-article-fill-long-lines}).
8403 @kindex W C (Summary)
8404 @findex gnus-article-capitalize-sentences
8405 Capitalize the first word in each sentence
8406 (@code{gnus-article-capitalize-sentences}).
8409 @kindex W c (Summary)
8410 @findex gnus-article-remove-cr
8411 Translate CRLF pairs (i. e., @samp{^M}s on the end of the lines) into LF
8412 (this takes care of DOS line endings), and then translate any remaining
8413 CRs into LF (this takes care of Mac line endings)
8414 (@code{gnus-article-remove-cr}).
8417 @kindex W q (Summary)
8418 @findex gnus-article-de-quoted-unreadable
8419 Treat quoted-printable (@code{gnus-article-de-quoted-unreadable}).
8420 Quoted-Printable is one common @sc{mime} encoding employed when sending
8421 non-ASCII (i. e., 8-bit) articles. It typically makes strings like
8422 @samp{déjà vu} look like @samp{d=E9j=E0 vu}, which doesn't look very
8423 readable to me. Note that this is usually done automatically by
8424 Gnus if the message in question has a @code{Content-Transfer-Encoding}
8425 header that says that this encoding has been done.
8426 If a prefix is given, a charset will be asked for.
8429 @kindex W 6 (Summary)
8430 @findex gnus-article-de-base64-unreadable
8431 Treat base64 (@code{gnus-article-de-base64-unreadable}).
8432 Base64 is one common @sc{mime} encoding employed when sending non-ASCII
8433 (i. e., 8-bit) articles. Note that this is usually done
8434 automatically by Gnus if the message in question has a
8435 @code{Content-Transfer-Encoding} header that says that this encoding has
8437 If a prefix is given, a charset will be asked for.
8440 @kindex W Z (Summary)
8441 @findex gnus-article-decode-HZ
8442 Treat HZ or HZP (@code{gnus-article-decode-HZ}). HZ (or HZP) is one
8443 common encoding employed when sending Chinese articles. It typically
8444 makes strings look like @samp{~@{<:Ky2;S@{#,NpJ)l6HK!#~@}}.
8447 @kindex W u (Summary)
8448 @findex gnus-article-unsplit-urls
8449 Remove newlines from within URLs. Some mailers insert newlines into
8450 outgoing email messages to keep lines short. This reformatting can
8451 split long URLs onto multiple lines. Repair those URLs by removing
8452 the newlines (@code{gnus-article-unsplit-urls}).
8455 @kindex W h (Summary)
8456 @findex gnus-article-wash-html
8457 Treat @sc{html} (@code{gnus-article-wash-html}). Note that this is
8458 usually done automatically by Gnus if the message in question has a
8459 @code{Content-Type} header that says that the message is @sc{html}.
8461 If a prefix is given, a charset will be asked for.
8463 @vindex gnus-article-wash-function
8464 The default is to use the function specified by
8465 @code{mm-text-html-renderer} (@pxref{Display Customization, ,Display
8466 Customization, emacs-mime, The Emacs MIME Manual}) to convert the
8467 @sc{html}, but this is controlled by the
8468 @code{gnus-article-wash-function} variable. Pre-defined functions you
8476 Use emacs-w3m (see @uref{http://emacs-w3m.namazu.org/} for more
8480 Use Links (see @uref{http://artax.karlin.mff.cuni.cz/~mikulas/links/}).
8483 Use Lynx (see @uref{http://lynx.browser.org/}).
8486 Use html2text -- a simple @sc{html} converter included with Gnus.
8491 @kindex W b (Summary)
8492 @findex gnus-article-add-buttons
8493 Add clickable buttons to the article (@code{gnus-article-add-buttons}).
8494 @xref{Article Buttons}.
8497 @kindex W B (Summary)
8498 @findex gnus-article-add-buttons-to-head
8499 Add clickable buttons to the article headers
8500 (@code{gnus-article-add-buttons-to-head}).
8503 @kindex W p (Summary)
8504 @findex gnus-article-verify-x-pgp-sig
8505 Verify a signed control message (@code{gnus-article-verify-x-pgp-sig}).
8506 Control messages such as @code{newgroup} and @code{checkgroups} are
8507 usually signed by the hierarchy maintainer. You need to add the PGP
8508 public key of the maintainer to your keyring to verify the
8509 message.@footnote{PGP keys for many hierarchies are available at
8510 @uref{ftp://ftp.isc.org/pub/pgpcontrol/README.html}}
8513 @kindex W s (Summary)
8514 @findex gnus-summary-force-verify-and-decrypt
8515 Verify a signed (PGP, @sc{pgp/mime} or @sc{s/mime}) message
8516 (@code{gnus-summary-force-verify-and-decrypt}). @xref{Security}.
8519 @kindex W a (Summary)
8520 @findex gnus-article-strip-headers-in-body
8521 Strip headers like the @code{X-No-Archive} header from the beginning of
8522 article bodies (@code{gnus-article-strip-headers-in-body}).
8525 @kindex W E l (Summary)
8526 @findex gnus-article-strip-leading-blank-lines
8527 Remove all blank lines from the beginning of the article
8528 (@code{gnus-article-strip-leading-blank-lines}).
8531 @kindex W E m (Summary)
8532 @findex gnus-article-strip-multiple-blank-lines
8533 Replace all blank lines with empty lines and then all multiple empty
8534 lines with a single empty line.
8535 (@code{gnus-article-strip-multiple-blank-lines}).
8538 @kindex W E t (Summary)
8539 @findex gnus-article-remove-trailing-blank-lines
8540 Remove all blank lines at the end of the article
8541 (@code{gnus-article-remove-trailing-blank-lines}).
8544 @kindex W E a (Summary)
8545 @findex gnus-article-strip-blank-lines
8546 Do all the three commands above
8547 (@code{gnus-article-strip-blank-lines}).
8550 @kindex W E A (Summary)
8551 @findex gnus-article-strip-all-blank-lines
8552 Remove all blank lines
8553 (@code{gnus-article-strip-all-blank-lines}).
8556 @kindex W E s (Summary)
8557 @findex gnus-article-strip-leading-space
8558 Remove all white space from the beginning of all lines of the article
8559 body (@code{gnus-article-strip-leading-space}).
8562 @kindex W E e (Summary)
8563 @findex gnus-article-strip-trailing-space
8564 Remove all white space from the end of all lines of the article
8565 body (@code{gnus-article-strip-trailing-space}).
8569 @xref{Customizing Articles}, for how to wash articles automatically.
8572 @node Article Header
8573 @subsection Article Header
8575 These commands perform various transformations of article header.
8580 @kindex W G u (Summary)
8581 @findex gnus-article-treat-unfold-headers
8582 Unfold folded header lines (@code{gnus-article-treat-unfold-headers}).
8585 @kindex W G n (Summary)
8586 @findex gnus-article-treat-fold-newsgroups
8587 Fold the @code{Newsgroups} and @code{Followup-To} headers
8588 (@code{gnus-article-treat-fold-newsgroups}).
8591 @kindex W G f (Summary)
8592 @findex gnus-article-treat-fold-headers
8593 Fold all the message headers
8594 (@code{gnus-article-treat-fold-headers}).
8598 @findex gnus-article-remove-leading-whitespace
8599 Remove excessive whitespace from all headers
8600 (@code{gnus-article-remove-leading-whitespace}).
8605 @node Article Buttons
8606 @subsection Article Buttons
8609 People often include references to other stuff in articles, and it would
8610 be nice if Gnus could just fetch whatever it is that people talk about
8611 with the minimum of fuzz when you hit @kbd{RET} or use the middle mouse
8612 button on these references.
8614 @vindex gnus-button-man-handler
8615 Gnus adds @dfn{buttons} to certain standard references by default:
8616 Well-formed URLs, mail addresses, Message-IDs, Info links, man pages and
8617 Emacs or Gnus related references. This is controlled by two variables,
8618 one that handles article bodies and one that handles article heads:
8622 @item gnus-button-alist
8623 @vindex gnus-button-alist
8624 This is an alist where each entry has this form:
8627 (REGEXP BUTTON-PAR USE-P FUNCTION DATA-PAR)
8633 All text that match this regular expression (case insensitive) will be
8634 considered an external reference. Here's a typical regexp that matches
8635 embedded URLs: @samp{<URL:\\([^\n\r>]*\\)>}. This can also be a
8636 variable containing a regexp, useful variables to use include
8637 @code{gnus-button-url-regexp} and @code{gnus-button-mid-or-mail-regexp}.
8640 Gnus has to know which parts of the matches is to be highlighted. This
8641 is a number that says what sub-expression of the regexp is to be
8642 highlighted. If you want it all highlighted, you use 0 here.
8645 This form will be @code{eval}ed, and if the result is non-@code{nil},
8646 this is considered a match. This is useful if you want extra sifting to
8647 avoid false matches. Often variables named
8648 @code{gnus-button-@var{*}-level} are used here, @xref{Article Button
8649 Levels}, but any other form may be used too.
8651 @c @code{use-p} is @code{eval}ed only if @code{regexp} matches.
8654 This function will be called when you click on this button.
8657 As with @var{button-par}, this is a sub-expression number, but this one
8658 says which part of the match is to be sent as data to @var{function}.
8662 So the full entry for buttonizing URLs is then
8665 ("<URL:\\([^\n\r>]*\\)>" 0 t gnus-button-url 1)
8668 @item gnus-header-button-alist
8669 @vindex gnus-header-button-alist
8670 This is just like the other alist, except that it is applied to the
8671 article head only, and that each entry has an additional element that is
8672 used to say what headers to apply the buttonize coding to:
8675 (HEADER REGEXP BUTTON-PAR USE-P FUNCTION DATA-PAR)
8678 @var{header} is a regular expression.
8680 @subsubheading Related variables and functions
8682 @item gnus-button-@var{*}-level
8683 @xref{Article Button Levels}.
8685 @c Stuff related to gnus-button-browse-level
8687 @item gnus-button-url-regexp
8688 @vindex gnus-button-url-regexp
8689 A regular expression that matches embedded URLs. It is used in the
8690 default values of the variables above.
8692 @c Stuff related to gnus-button-man-level
8694 @item gnus-button-man-handler
8695 @vindex gnus-button-man-handler
8696 The function to use for displaying man pages. It must take at least one
8697 argument with a string naming the man page.
8699 @c Stuff related to gnus-button-message-level
8701 @item gnus-button-mid-or-mail-regexp
8702 @vindex gnus-button-mid-or-mail-regexp
8703 Regular expression that matches a message ID or a mail address.
8705 @item gnus-button-prefer-mid-or-mail
8706 @vindex gnus-button-prefer-mid-or-mail
8707 This variable determines what to do when the button on a string as
8708 @samp{foo123@@bar.invalid} is pushed. Strings like this can be either a
8709 message ID or a mail address. If it is one of the symbols @code{mid} or
8710 @code{mail}, Gnus will always assume that the string is a message ID or
8711 a mail address, respectivly. If this variable is set to the symbol
8712 @code{ask}, always query the user what do do. If it is a function, this
8713 function will be called with the string as it's only argument. The
8714 function must return @code{mid}, @code{mail}, @code{invalid} or
8715 @code{ask}. The default value is the function
8716 @code{gnus-button-mid-or-mail-heuristic}.
8718 @item gnus-button-mid-or-mail-heuristic
8719 @findex gnus-button-mid-or-mail-heuristic
8720 Function that guesses whether it's argument is a message ID or a mail
8721 address. Returns @code{mid} it's a message IDs, @code{mail} if it's a
8722 mail address, @code{ask} if unsure and @code{invalid} if the string is
8725 @item gnus-button-mid-or-mail-heuristic-alist
8726 @vindex gnus-button-mid-or-mail-heuristic-alist
8727 An alist of @code{(RATE . REGEXP)} pairs used by the function
8728 @code{gnus-button-mid-or-mail-heuristic}.
8730 @c Stuff related to gnus-button-tex-level
8732 @item gnus-button-ctan-handler
8733 @findex gnus-button-ctan-handler
8734 The function to use for displaying CTAN links. It must take one
8735 argument, the string naming the URL.
8738 @vindex gnus-ctan-url
8739 Top directory of a CTAN (Comprehensive TeX Archive Network) archive used
8740 by @code{gnus-button-ctan-handler}.
8744 @item gnus-article-button-face
8745 @vindex gnus-article-button-face
8746 Face used on buttons.
8748 @item gnus-article-mouse-face
8749 @vindex gnus-article-mouse-face
8750 Face used when the mouse cursor is over a button.
8754 @xref{Customizing Articles}, for how to buttonize articles automatically.
8757 @node Article Button Levels
8758 @subsection Article button levels
8759 @cindex button levels
8760 The higher the value of the variables @code{gnus-button-@var{*}-level},
8761 the more buttons will appear. If the level is zero, no corresponding
8762 buttons are displayed. With the default value (which is 5) you should
8763 already see quite a lot of buttons. With higher levels, you will see
8764 more buttons, but you may also get more false positives. To avoid them,
8765 you can set the variables @code{gnus-button-@var{*}-level} local to
8766 specific groups (@pxref{Group Parameters}). Here's an example for the
8767 variable @code{gnus-parameters}:
8770 ;; increase `gnus-button-*-level' in some groups:
8771 (setq gnus-parameters
8772 '(("\\<\\(emacs\\|gnus\\)\\>" (gnus-button-emacs-level 10))
8773 ("\\<unix\\>" (gnus-button-man-level 10))
8774 ("\\<tex\\>" (gnus-button-tex-level 10))))
8779 @item gnus-button-browse-level
8780 @vindex gnus-button-browse-level
8781 Controls the display of references to message IDs, mail addresses and
8782 news URLs. Related variables and functions include
8783 @code{gnus-button-url-regexp}, @code{browse-url}, and
8784 @code{browse-url-browser-function}.
8786 @item gnus-button-emacs-level
8787 @vindex gnus-button-emacs-level
8788 Controls the display of Emacs or Gnus references. Related functions are
8789 @code{gnus-button-handle-custom},
8790 @code{gnus-button-handle-describe-function},
8791 @code{gnus-button-handle-describe-variable},
8792 @code{gnus-button-handle-symbol},
8793 @code{gnus-button-handle-describe-key},
8794 @code{gnus-button-handle-apropos},
8795 @code{gnus-button-handle-apropos-command},
8796 @code{gnus-button-handle-apropos-variable},
8797 @code{gnus-button-handle-apropos-documentation}, and
8798 @code{gnus-button-handle-library}.
8800 @item gnus-button-man-level
8801 @vindex gnus-button-man-level
8802 Controls the display of references to (Unix) man pages.
8803 See @code{gnus-button-man-handler}.
8805 @item gnus-button-message-level
8806 @vindex gnus-button-message-level
8807 Controls the display of message IDs, mail addresses and news URLs.
8808 Related variables and functions include
8809 @code{gnus-button-mid-or-mail-regexp},
8810 @code{gnus-button-prefer-mid-or-mail},
8811 @code{gnus-button-mid-or-mail-heuristic}, and
8812 @code{gnus-button-mid-or-mail-heuristic-alist}.
8814 @item gnus-button-tex-level
8815 @vindex gnus-button-tex-level
8816 Controls the display of references to TeX or LaTeX stuff, e.g. for CTAN
8817 URLs. See the variables @code{gnus-ctan-url},
8818 @code{gnus-button-ctan-handler},
8819 @code{gnus-button-ctan-directory-regexp}, and
8820 @code{gnus-button-handle-ctan-bogus-regexp}.
8826 @subsection Article Date
8828 The date is most likely generated in some obscure timezone you've never
8829 heard of, so it's quite nice to be able to find out what the time was
8830 when the article was sent.
8835 @kindex W T u (Summary)
8836 @findex gnus-article-date-ut
8837 Display the date in UT (aka. GMT, aka ZULU)
8838 (@code{gnus-article-date-ut}).
8841 @kindex W T i (Summary)
8842 @findex gnus-article-date-iso8601
8844 Display the date in international format, aka. ISO 8601
8845 (@code{gnus-article-date-iso8601}).
8848 @kindex W T l (Summary)
8849 @findex gnus-article-date-local
8850 Display the date in the local timezone (@code{gnus-article-date-local}).
8853 @kindex W T p (Summary)
8854 @findex gnus-article-date-english
8855 Display the date in a format that's easily pronounceable in English
8856 (@code{gnus-article-date-english}).
8859 @kindex W T s (Summary)
8860 @vindex gnus-article-time-format
8861 @findex gnus-article-date-user
8862 @findex format-time-string
8863 Display the date using a user-defined format
8864 (@code{gnus-article-date-user}). The format is specified by the
8865 @code{gnus-article-time-format} variable, and is a string that's passed
8866 to @code{format-time-string}. See the documentation of that variable
8867 for a list of possible format specs.
8870 @kindex W T e (Summary)
8871 @findex gnus-article-date-lapsed
8872 @findex gnus-start-date-timer
8873 @findex gnus-stop-date-timer
8874 Say how much time has elapsed between the article was posted and now
8875 (@code{gnus-article-date-lapsed}). It looks something like:
8878 X-Sent: 6 weeks, 4 days, 1 hour, 3 minutes, 8 seconds ago
8881 @vindex gnus-article-date-lapsed-new-header
8882 The value of @code{gnus-article-date-lapsed-new-header} determines
8883 whether this header will just be added below the old Date one, or will
8886 An advantage of using Gnus to read mail is that it converts simple bugs
8887 into wonderful absurdities.
8889 If you want to have this line updated continually, you can put
8892 (gnus-start-date-timer)
8895 in your @file{~/.gnus.el} file, or you can run it off of some hook. If
8896 you want to stop the timer, you can use the @code{gnus-stop-date-timer}
8900 @kindex W T o (Summary)
8901 @findex gnus-article-date-original
8902 Display the original date (@code{gnus-article-date-original}). This can
8903 be useful if you normally use some other conversion function and are
8904 worried that it might be doing something totally wrong. Say, claiming
8905 that the article was posted in 1854. Although something like that is
8906 @emph{totally} impossible. Don't you trust me? *titter*
8910 @xref{Customizing Articles}, for how to display the date in your
8911 preferred format automatically.
8914 @node Article Display
8915 @subsection Article Display
8920 These commands add various frivolous display gimmicks to the article
8921 buffer in Emacs versions that support them.
8923 @code{X-Face} headers are small black-and-white images supplied by the
8924 message headers (@pxref{X-Face}).
8926 Picons, on the other hand, reside on your own system, and Gnus will
8927 try to match the headers to what you have (@pxref{Picons}).
8929 Smileys are those little @samp{:-)} symbols that people like to litter
8930 their messages with (@pxref{Smileys}).
8932 All these functions are toggles--if the elements already exist,
8937 @kindex W D x (Summary)
8938 @findex gnus-article-display-x-face
8939 Display an @code{X-Face} in the @code{From} header.
8940 (@code{gnus-article-display-x-face}).
8943 @kindex W D d (Summary)
8944 @findex gnus-article-display-face
8945 Display a @code{Face} in the @code{From} header.
8946 (@code{gnus-article-display-face}).
8949 @kindex W D s (Summary)
8950 @findex gnus-treat-smiley
8951 Display smileys (@code{gnus-treat-smiley}).
8954 @kindex W D f (Summary)
8955 @findex gnus-treat-from-picon
8956 Piconify the @code{From} header (@code{gnus-treat-from-picon}).
8959 @kindex W D m (Summary)
8960 @findex gnus-treat-mail-picon
8961 Piconify all mail headers (i. e., @code{Cc}, @code{To})
8962 (@code{gnus-treat-mail-picon}).
8965 @kindex W D n (Summary)
8966 @findex gnus-treat-newsgroups-picon
8967 Piconify all news headers (i. e., @code{Newsgroups} and
8968 @code{Followup-To}) (@code{gnus-treat-newsgroups-picon}).
8971 @kindex W D D (Summary)
8972 @findex gnus-article-remove-images
8973 Remove all images from the article buffer
8974 (@code{gnus-article-remove-images}).
8980 @node Article Signature
8981 @subsection Article Signature
8983 @cindex article signature
8985 @vindex gnus-signature-separator
8986 Each article is divided into two parts---the head and the body. The
8987 body can be divided into a signature part and a text part. The variable
8988 that says what is to be considered a signature is
8989 @code{gnus-signature-separator}. This is normally the standard
8990 @samp{^-- $} as mandated by son-of-RFC 1036. However, many people use
8991 non-standard signature separators, so this variable can also be a list
8992 of regular expressions to be tested, one by one. (Searches are done
8993 from the end of the body towards the beginning.) One likely value is:
8996 (setq gnus-signature-separator
8997 '("^-- $" ; The standard
8998 "^-- *$" ; A common mangling
8999 "^-------*$" ; Many people just use a looong
9000 ; line of dashes. Shame!
9001 "^ *--------*$" ; Double-shame!
9002 "^________*$" ; Underscores are also popular
9003 "^========*$")) ; Pervert!
9006 The more permissive you are, the more likely it is that you'll get false
9009 @vindex gnus-signature-limit
9010 @code{gnus-signature-limit} provides a limit to what is considered a
9011 signature when displaying articles.
9015 If it is an integer, no signature may be longer (in characters) than
9018 If it is a floating point number, no signature may be longer (in lines)
9021 If it is a function, the function will be called without any parameters,
9022 and if it returns @code{nil}, there is no signature in the buffer.
9024 If it is a string, it will be used as a regexp. If it matches, the text
9025 in question is not a signature.
9028 This variable can also be a list where the elements may be of the types
9029 listed above. Here's an example:
9032 (setq gnus-signature-limit
9033 '(200.0 "^---*Forwarded article"))
9036 This means that if there are more than 200 lines after the signature
9037 separator, or the text after the signature separator is matched by
9038 the regular expression @samp{^---*Forwarded article}, then it isn't a
9039 signature after all.
9042 @node Article Miscellania
9043 @subsection Article Miscellania
9047 @kindex A t (Summary)
9048 @findex gnus-article-babel
9049 Translate the article from one language to another
9050 (@code{gnus-article-babel}).
9056 @section MIME Commands
9057 @cindex MIME decoding
9059 @cindex viewing attachments
9061 The following commands all understand the numerical prefix. For
9062 instance, @kbd{3 b} means ``view the third @sc{mime} part''.
9068 @kindex K v (Summary)
9069 View the @sc{mime} part.
9072 @kindex K o (Summary)
9073 Save the @sc{mime} part.
9076 @kindex K c (Summary)
9077 Copy the @sc{mime} part.
9080 @kindex K e (Summary)
9081 View the @sc{mime} part externally.
9084 @kindex K i (Summary)
9085 View the @sc{mime} part internally.
9088 @kindex K | (Summary)
9089 Pipe the @sc{mime} part to an external command.
9092 The rest of these @sc{mime} commands do not use the numerical prefix in
9097 @kindex K b (Summary)
9098 Make all the @sc{mime} parts have buttons in front of them. This is
9099 mostly useful if you wish to save (or perform other actions) on inlined
9103 @kindex K m (Summary)
9104 @findex gnus-summary-repair-multipart
9105 Some multipart messages are transmitted with missing or faulty headers.
9106 This command will attempt to ``repair'' these messages so that they can
9107 be viewed in a more pleasant manner
9108 (@code{gnus-summary-repair-multipart}).
9111 @kindex X m (Summary)
9112 @findex gnus-summary-save-parts
9113 Save all parts matching a @sc{mime} type to a directory
9114 (@code{gnus-summary-save-parts}). Understands the process/prefix
9115 convention (@pxref{Process/Prefix}).
9118 @kindex M-t (Summary)
9119 @findex gnus-summary-toggle-display-buttonized
9120 Toggle the buttonized display of the article buffer
9121 (@code{gnus-summary-toggle-display-buttonized}).
9124 @kindex W M w (Summary)
9125 @findex gnus-article-decode-mime-words
9126 Decode RFC 2047-encoded words in the article headers
9127 (@code{gnus-article-decode-mime-words}).
9130 @kindex W M c (Summary)
9131 @findex gnus-article-decode-charset
9132 Decode encoded article bodies as well as charsets
9133 (@code{gnus-article-decode-charset}).
9135 This command looks in the @code{Content-Type} header to determine the
9136 charset. If there is no such header in the article, you can give it a
9137 prefix, which will prompt for the charset to decode as. In regional
9138 groups where people post using some common encoding (but do not
9139 include @sc{mime} headers), you can set the @code{charset} group/topic
9140 parameter to the required charset (@pxref{Group Parameters}).
9143 @kindex W M v (Summary)
9144 @findex gnus-mime-view-all-parts
9145 View all the @sc{mime} parts in the current article
9146 (@code{gnus-mime-view-all-parts}).
9153 @item gnus-ignored-mime-types
9154 @vindex gnus-ignored-mime-types
9155 This is a list of regexps. @sc{mime} types that match a regexp from
9156 this list will be completely ignored by Gnus. The default value is
9159 To have all Vcards be ignored, you'd say something like this:
9162 (setq gnus-ignored-mime-types
9166 @item gnus-article-loose-mime
9167 @vindex gnus-article-loose-mime
9168 If non-@code{nil}, Gnus won't required the @samp{MIME-Version} header
9169 before interpreting the message as a @sc{mime} message. This helps
9170 when reading messages from certain broken mail user agents. The
9171 default is @code{nil}.
9173 @item gnus-article-emulate-mime
9174 @vindex gnus-article-emulate-mime
9175 There are other, non-@sc{mime} encoding methods used. The most common
9176 is @samp{uuencode}, but yEncode is also getting to be popular. If
9177 This variable is non-@code{nil}, Gnus will look in message bodies to
9178 see if it finds these encodings, and if so, it'll run them through the
9179 Gnus @sc{mime} machinery. The default is @code{t}.
9181 @item gnus-unbuttonized-mime-types
9182 @vindex gnus-unbuttonized-mime-types
9183 This is a list of regexps. @sc{mime} types that match a regexp from
9184 this list won't have @sc{mime} buttons inserted unless they aren't
9185 displayed or this variable is overridden by
9186 @code{gnus-buttonized-mime-types}. The default value is
9187 @code{(".*/.*")}. This variable is only used when
9188 @code{gnus-inhibit-mime-unbuttonizing} is nil.
9190 @item gnus-buttonized-mime-types
9191 @vindex gnus-buttonized-mime-types
9192 This is a list of regexps. @sc{mime} types that match a regexp from
9193 this list will have @sc{mime} buttons inserted unless they aren't
9194 displayed. This variable overrides
9195 @code{gnus-unbuttonized-mime-types}. The default value is @code{nil}.
9196 This variable is only used when @code{gnus-inhibit-mime-unbuttonizing}
9199 To see e.g. security buttons but no other buttons, you could set this
9200 variable to @code{("multipart/signed")} and leave
9201 @code{gnus-unbuttonized-mime-types} at the default value.
9203 @item gnus-inhibit-mime-unbuttonizing
9204 @vindex gnus-inhibit-mime-unbuttonizing
9205 If this is non-nil, then all @sc{mime} parts get buttons. The default
9206 value is @code{nil}.
9208 @item gnus-article-mime-part-function
9209 @vindex gnus-article-mime-part-function
9210 For each @sc{mime} part, this function will be called with the @sc{mime}
9211 handle as the parameter. The function is meant to be used to allow
9212 users to gather information from the article (e. g., add Vcard info to
9213 the bbdb database) or to do actions based on parts (e. g., automatically
9214 save all jpegs into some directory).
9216 Here's an example function the does the latter:
9219 (defun my-save-all-jpeg-parts (handle)
9220 (when (equal (car (mm-handle-type handle)) "image/jpeg")
9222 (insert (mm-get-part handle))
9223 (write-region (point-min) (point-max)
9224 (read-file-name "Save jpeg to: ")))))
9225 (setq gnus-article-mime-part-function
9226 'my-save-all-jpeg-parts)
9229 @vindex gnus-mime-multipart-functions
9230 @item gnus-mime-multipart-functions
9231 Alist of @sc{mime} multipart types and functions to handle them.
9233 @vindex mm-file-name-rewrite-functions
9234 @item mm-file-name-rewrite-functions
9235 List of functions used for rewriting file names of @sc{mime} parts.
9236 Each function takes a file name as input and returns a file name.
9238 Ready-made functions include@*
9239 @code{mm-file-name-delete-whitespace},
9240 @code{mm-file-name-trim-whitespace},
9241 @code{mm-file-name-collapse-whitespace}, and
9242 @code{mm-file-name-replace-whitespace}. The later uses the value of
9243 the variable @code{mm-file-name-replace-whitespace} to replace each
9244 whitespace character in a file name with that string; default value
9245 is @code{"_"} (a single underscore).
9246 @findex mm-file-name-delete-whitespace
9247 @findex mm-file-name-trim-whitespace
9248 @findex mm-file-name-collapse-whitespace
9249 @findex mm-file-name-replace-whitespace
9250 @vindex mm-file-name-replace-whitespace
9252 The standard functions @code{capitalize}, @code{downcase},
9253 @code{upcase}, and @code{upcase-initials} may be useful, too.
9255 Everybody knows that whitespace characters in file names are evil,
9256 except those who don't know. If you receive lots of attachments from
9257 such unenlightened users, you can make live easier by adding
9260 (setq mm-file-name-rewrite-functions
9261 '(mm-file-name-trim-whitespace
9262 mm-file-name-collapse-whitespace
9263 mm-file-name-replace-whitespace))
9267 to your @file{~/.gnus.el} file.
9276 People use different charsets, and we have @sc{mime} to let us know what
9277 charsets they use. Or rather, we wish we had. Many people use
9278 newsreaders and mailers that do not understand or use @sc{mime}, and
9279 just send out messages without saying what character sets they use. To
9280 help a bit with this, some local news hierarchies have policies that say
9281 what character set is the default. For instance, the @samp{fj}
9282 hierarchy uses @code{iso-2022-jp-2}.
9284 @vindex gnus-group-charset-alist
9285 This knowledge is encoded in the @code{gnus-group-charset-alist}
9286 variable, which is an alist of regexps (use the first item to match full
9287 group names) and default charsets to be used when reading these groups.
9289 @vindex gnus-newsgroup-ignored-charsets
9290 In addition, some people do use soi-disant @sc{mime}-aware agents that
9291 aren't. These blithely mark messages as being in @code{iso-8859-1}
9292 even if they really are in @code{koi-8}. To help here, the
9293 @code{gnus-newsgroup-ignored-charsets} variable can be used. The
9294 charsets that are listed here will be ignored. The variable can be
9295 set on a group-by-group basis using the group parameters (@pxref{Group
9296 Parameters}). The default value is @code{(unknown-8bit x-unknown)},
9297 which includes values some agents insist on having in there.
9299 @vindex gnus-group-posting-charset-alist
9300 When posting, @code{gnus-group-posting-charset-alist} is used to
9301 determine which charsets should not be encoded using the @sc{mime}
9302 encodings. For instance, some hierarchies discourage using
9303 quoted-printable header encoding.
9305 This variable is an alist of regexps and permitted unencoded charsets
9306 for posting. Each element of the alist has the form @code{(}@var{test
9307 header body-list}@code{)}, where:
9311 is either a regular expression matching the newsgroup header or a
9314 is the charset which may be left unencoded in the header (@code{nil}
9315 means encode all charsets),
9317 is a list of charsets which may be encoded using 8bit content-transfer
9318 encoding in the body, or one of the special values @code{nil} (always
9319 encode using quoted-printable) or @code{t} (always use 8bit).
9326 @cindex coding system aliases
9327 @cindex preferred charset
9329 Other charset tricks that may be useful, although not Gnus-specific:
9331 If there are several @sc{mime} charsets that encode the same Emacs
9332 charset, you can choose what charset to use by saying the following:
9335 (put-charset-property 'cyrillic-iso8859-5
9336 'preferred-coding-system 'koi8-r)
9339 This means that Russian will be encoded using @code{koi8-r} instead of
9340 the default @code{iso-8859-5} @sc{mime} charset.
9342 If you want to read messages in @code{koi8-u}, you can cheat and say
9345 (define-coding-system-alias 'koi8-u 'koi8-r)
9348 This will almost do the right thing.
9350 And finally, to read charsets like @code{windows-1251}, you can say
9354 (codepage-setup 1251)
9355 (define-coding-system-alias 'windows-1251 'cp1251)
9359 @node Article Commands
9360 @section Article Commands
9367 @kindex A P (Summary)
9368 @vindex gnus-ps-print-hook
9369 @findex gnus-summary-print-article
9370 Generate and print a PostScript image of the article buffer
9371 (@code{gnus-summary-print-article}). @code{gnus-ps-print-hook} will
9372 be run just before printing the buffer. An alternative way to print
9373 article is to use Muttprint (@pxref{Saving Articles}).
9378 @node Summary Sorting
9379 @section Summary Sorting
9380 @cindex summary sorting
9382 You can have the summary buffer sorted in various ways, even though I
9383 can't really see why you'd want that.
9388 @kindex C-c C-s C-n (Summary)
9389 @findex gnus-summary-sort-by-number
9390 Sort by article number (@code{gnus-summary-sort-by-number}).
9393 @kindex C-c C-s C-a (Summary)
9394 @findex gnus-summary-sort-by-author
9395 Sort by author (@code{gnus-summary-sort-by-author}).
9398 @kindex C-c C-s C-s (Summary)
9399 @findex gnus-summary-sort-by-subject
9400 Sort by subject (@code{gnus-summary-sort-by-subject}).
9403 @kindex C-c C-s C-d (Summary)
9404 @findex gnus-summary-sort-by-date
9405 Sort by date (@code{gnus-summary-sort-by-date}).
9408 @kindex C-c C-s C-l (Summary)
9409 @findex gnus-summary-sort-by-lines
9410 Sort by lines (@code{gnus-summary-sort-by-lines}).
9413 @kindex C-c C-s C-c (Summary)
9414 @findex gnus-summary-sort-by-chars
9415 Sort by article length (@code{gnus-summary-sort-by-chars}).
9418 @kindex C-c C-s C-i (Summary)
9419 @findex gnus-summary-sort-by-score
9420 Sort by score (@code{gnus-summary-sort-by-score}).
9423 @kindex C-c C-s C-r (Summary)
9424 @findex gnus-summary-sort-by-random
9425 Randomize (@code{gnus-summary-sort-by-random}).
9428 @kindex C-c C-s C-o (Summary)
9429 @findex gnus-summary-sort-by-original
9430 Sort using the default sorting method
9431 (@code{gnus-summary-sort-by-original}).
9434 These functions will work both when you use threading and when you don't
9435 use threading. In the latter case, all summary lines will be sorted,
9436 line by line. In the former case, sorting will be done on a
9437 root-by-root basis, which might not be what you were looking for. To
9438 toggle whether to use threading, type @kbd{T T} (@pxref{Thread
9442 @node Finding the Parent
9443 @section Finding the Parent
9444 @cindex parent articles
9445 @cindex referring articles
9450 @findex gnus-summary-refer-parent-article
9451 If you'd like to read the parent of the current article, and it is not
9452 displayed in the summary buffer, you might still be able to. That is,
9453 if the current group is fetched by @sc{nntp}, the parent hasn't expired
9454 and the @code{References} in the current article are not mangled, you
9455 can just press @kbd{^} or @kbd{A r}
9456 (@code{gnus-summary-refer-parent-article}). If everything goes well,
9457 you'll get the parent. If the parent is already displayed in the
9458 summary buffer, point will just move to this article.
9460 If given a positive numerical prefix, fetch that many articles back into
9461 the ancestry. If given a negative numerical prefix, fetch just that
9462 ancestor. So if you say @kbd{3 ^}, Gnus will fetch the parent, the
9463 grandparent and the grandgrandparent of the current article. If you say
9464 @kbd{-3 ^}, Gnus will only fetch the grandgrandparent of the current
9468 @findex gnus-summary-refer-references
9469 @kindex A R (Summary)
9470 Fetch all articles mentioned in the @code{References} header of the
9471 article (@code{gnus-summary-refer-references}).
9474 @findex gnus-summary-refer-thread
9475 @kindex A T (Summary)
9476 Display the full thread where the current article appears
9477 (@code{gnus-summary-refer-thread}). This command has to fetch all the
9478 headers in the current group to work, so it usually takes a while. If
9479 you do it often, you may consider setting @code{gnus-fetch-old-headers}
9480 to @code{invisible} (@pxref{Filling In Threads}). This won't have any
9481 visible effects normally, but it'll make this command work a whole lot
9482 faster. Of course, it'll make group entry somewhat slow.
9484 @vindex gnus-refer-thread-limit
9485 The @code{gnus-refer-thread-limit} variable says how many old (i. e.,
9486 articles before the first displayed in the current group) headers to
9487 fetch when doing this command. The default is 200. If @code{t}, all
9488 the available headers will be fetched. This variable can be overridden
9489 by giving the @kbd{A T} command a numerical prefix.
9492 @findex gnus-summary-refer-article
9493 @kindex M-^ (Summary)
9495 @cindex fetching by Message-ID
9496 You can also ask the @sc{nntp} server for an arbitrary article, no
9497 matter what group it belongs to. @kbd{M-^}
9498 (@code{gnus-summary-refer-article}) will ask you for a
9499 @code{Message-ID}, which is one of those long, hard-to-read thingies
9500 that look something like @samp{<38o6up$6f2@@hymir.ifi.uio.no>}. You
9501 have to get it all exactly right. No fuzzy searches, I'm afraid.
9504 The current select method will be used when fetching by
9505 @code{Message-ID} from non-news select method, but you can override this
9506 by giving this command a prefix.
9508 @vindex gnus-refer-article-method
9509 If the group you are reading is located on a back end that does not
9510 support fetching by @code{Message-ID} very well (like @code{nnspool}),
9511 you can set @code{gnus-refer-article-method} to an @sc{nntp} method. It
9512 would, perhaps, be best if the @sc{nntp} server you consult is the one
9513 updating the spool you are reading from, but that's not really
9516 It can also be a list of select methods, as well as the special symbol
9517 @code{current}, which means to use the current select method. If it
9518 is a list, Gnus will try all the methods in the list until it finds a
9521 Here's an example setting that will first try the current method, and
9522 then ask Google if that fails:
9525 (setq gnus-refer-article-method
9527 (nnweb "google" (nnweb-type google))))
9530 Most of the mail back ends support fetching by @code{Message-ID}, but
9531 do not do a particularly excellent job at it. That is, @code{nnmbox},
9532 @code{nnbabyl}, and @code{nnmaildir} are able to locate articles from
9533 any groups, while @code{nnml}, @code{nnfolder}, and @code{nnimap} are
9534 only able to locate articles that have been posted to the current group.
9535 (Anything else would be too time consuming.) @code{nnmh} does not
9536 support this at all.
9539 @node Alternative Approaches
9540 @section Alternative Approaches
9542 Different people like to read news using different methods. This being
9543 Gnus, we offer a small selection of minor modes for the summary buffers.
9546 * Pick and Read:: First mark articles and then read them.
9547 * Binary Groups:: Auto-decode all articles.
9552 @subsection Pick and Read
9553 @cindex pick and read
9555 Some newsreaders (like @code{nn} and, uhm, @code{Netnews} on VM/CMS) use
9556 a two-phased reading interface. The user first marks in a summary
9557 buffer the articles she wants to read. Then she starts reading the
9558 articles with just an article buffer displayed.
9560 @findex gnus-pick-mode
9561 @kindex M-x gnus-pick-mode
9562 Gnus provides a summary buffer minor mode that allows
9563 this---@code{gnus-pick-mode}. This basically means that a few process
9564 mark commands become one-keystroke commands to allow easy marking, and
9565 it provides one additional command for switching to the summary buffer.
9567 Here are the available keystrokes when using pick mode:
9572 @findex gnus-pick-article-or-thread
9573 Pick the article or thread on the current line
9574 (@code{gnus-pick-article-or-thread}). If the variable
9575 @code{gnus-thread-hide-subtree} is true, then this key selects the
9576 entire thread when used at the first article of the thread. Otherwise,
9577 it selects just the article. If given a numerical prefix, go to that
9578 thread or article and pick it. (The line number is normally displayed
9579 at the beginning of the summary pick lines.)
9582 @kindex SPACE (Pick)
9583 @findex gnus-pick-next-page
9584 Scroll the summary buffer up one page (@code{gnus-pick-next-page}). If
9585 at the end of the buffer, start reading the picked articles.
9589 @findex gnus-pick-unmark-article-or-thread.
9590 Unpick the thread or article
9591 (@code{gnus-pick-unmark-article-or-thread}). If the variable
9592 @code{gnus-thread-hide-subtree} is true, then this key unpicks the
9593 thread if used at the first article of the thread. Otherwise it unpicks
9594 just the article. You can give this key a numerical prefix to unpick
9595 the thread or article at that line.
9599 @findex gnus-pick-start-reading
9600 @vindex gnus-pick-display-summary
9601 Start reading the picked articles (@code{gnus-pick-start-reading}). If
9602 given a prefix, mark all unpicked articles as read first. If
9603 @code{gnus-pick-display-summary} is non-@code{nil}, the summary buffer
9604 will still be visible when you are reading.
9608 All the normal summary mode commands are still available in the
9609 pick-mode, with the exception of @kbd{u}. However @kbd{!} is available
9610 which is mapped to the same function
9611 @code{gnus-summary-tick-article-forward}.
9613 If this sounds like a good idea to you, you could say:
9616 (add-hook 'gnus-summary-mode-hook 'gnus-pick-mode)
9619 @vindex gnus-pick-mode-hook
9620 @code{gnus-pick-mode-hook} is run in pick minor mode buffers.
9622 @vindex gnus-mark-unpicked-articles-as-read
9623 If @code{gnus-mark-unpicked-articles-as-read} is non-@code{nil}, mark
9624 all unpicked articles as read. The default is @code{nil}.
9626 @vindex gnus-summary-pick-line-format
9627 The summary line format in pick mode is slightly different from the
9628 standard format. At the beginning of each line the line number is
9629 displayed. The pick mode line format is controlled by the
9630 @code{gnus-summary-pick-line-format} variable (@pxref{Formatting
9631 Variables}). It accepts the same format specs that
9632 @code{gnus-summary-line-format} does (@pxref{Summary Buffer Lines}).
9636 @subsection Binary Groups
9637 @cindex binary groups
9639 @findex gnus-binary-mode
9640 @kindex M-x gnus-binary-mode
9641 If you spend much time in binary groups, you may grow tired of hitting
9642 @kbd{X u}, @kbd{n}, @kbd{RET} all the time. @kbd{M-x gnus-binary-mode}
9643 is a minor mode for summary buffers that makes all ordinary Gnus article
9644 selection functions uudecode series of articles and display the result
9645 instead of just displaying the articles the normal way.
9648 @findex gnus-binary-show-article
9649 The only way, in fact, to see the actual articles is the @kbd{g}
9650 command, when you have turned on this mode
9651 (@code{gnus-binary-show-article}).
9653 @vindex gnus-binary-mode-hook
9654 @code{gnus-binary-mode-hook} is called in binary minor mode buffers.
9658 @section Tree Display
9661 @vindex gnus-use-trees
9662 If you don't like the normal Gnus summary display, you might try setting
9663 @code{gnus-use-trees} to @code{t}. This will create (by default) an
9664 additional @dfn{tree buffer}. You can execute all summary mode commands
9667 There are a few variables to customize the tree display, of course:
9670 @item gnus-tree-mode-hook
9671 @vindex gnus-tree-mode-hook
9672 A hook called in all tree mode buffers.
9674 @item gnus-tree-mode-line-format
9675 @vindex gnus-tree-mode-line-format
9676 A format string for the mode bar in the tree mode buffers (@pxref{Mode
9677 Line Formatting}). The default is @samp{Gnus: %%b %S %Z}. For a list
9678 of valid specs, @pxref{Summary Buffer Mode Line}.
9680 @item gnus-selected-tree-face
9681 @vindex gnus-selected-tree-face
9682 Face used for highlighting the selected article in the tree buffer. The
9683 default is @code{modeline}.
9685 @item gnus-tree-line-format
9686 @vindex gnus-tree-line-format
9687 A format string for the tree nodes. The name is a bit of a misnomer,
9688 though---it doesn't define a line, but just the node. The default value
9689 is @samp{%(%[%3,3n%]%)}, which displays the first three characters of
9690 the name of the poster. It is vital that all nodes are of the same
9691 length, so you @emph{must} use @samp{%4,4n}-like specifiers.
9697 The name of the poster.
9699 The @code{From} header.
9701 The number of the article.
9703 The opening bracket.
9705 The closing bracket.
9710 @xref{Formatting Variables}.
9712 Variables related to the display are:
9715 @item gnus-tree-brackets
9716 @vindex gnus-tree-brackets
9717 This is used for differentiating between ``real'' articles and
9718 ``sparse'' articles. The format is @code{((@var{real-open} . @var{real-close})
9719 (@var{sparse-open} . @var{sparse-close}) (@var{dummy-open} . @var{dummy-close}))}, and the
9720 default is @code{((?[ . ?]) (?( . ?)) (?@{ . ?@}) (?< . ?>))}.
9722 @item gnus-tree-parent-child-edges
9723 @vindex gnus-tree-parent-child-edges
9724 This is a list that contains the characters used for connecting parent
9725 nodes to their children. The default is @code{(?- ?\\ ?|)}.
9729 @item gnus-tree-minimize-window
9730 @vindex gnus-tree-minimize-window
9731 If this variable is non-@code{nil}, Gnus will try to keep the tree
9732 buffer as small as possible to allow more room for the other Gnus
9733 windows. If this variable is a number, the tree buffer will never be
9734 higher than that number. The default is @code{t}. Note that if you
9735 have several windows displayed side-by-side in a frame and the tree
9736 buffer is one of these, minimizing the tree window will also resize all
9737 other windows displayed next to it.
9739 You may also wish to add the following hook to keep the window minimized
9743 (add-hook 'gnus-configure-windows-hook
9744 'gnus-tree-perhaps-minimize)
9747 @item gnus-generate-tree-function
9748 @vindex gnus-generate-tree-function
9749 @findex gnus-generate-horizontal-tree
9750 @findex gnus-generate-vertical-tree
9751 The function that actually generates the thread tree. Two predefined
9752 functions are available: @code{gnus-generate-horizontal-tree} and
9753 @code{gnus-generate-vertical-tree} (which is the default).
9757 Here's an example from a horizontal tree buffer:
9760 @{***@}-(***)-[odd]-[Gun]
9770 Here's the same thread displayed in a vertical tree buffer:
9774 |--------------------------\-----\-----\
9775 (***) [Bjo] [Gun] [Gun]
9777 [odd] [Jan] [odd] (***) [Jor]
9779 [Gun] [Eri] [Eri] [odd]
9784 If you're using horizontal trees, it might be nice to display the trees
9785 side-by-side with the summary buffer. You could add something like the
9786 following to your @file{~/.gnus.el} file:
9789 (setq gnus-use-trees t
9790 gnus-generate-tree-function 'gnus-generate-horizontal-tree
9791 gnus-tree-minimize-window nil)
9792 (gnus-add-configuration
9796 (summary 0.75 point)
9801 @xref{Window Layout}.
9804 @node Mail Group Commands
9805 @section Mail Group Commands
9806 @cindex mail group commands
9808 Some commands only make sense in mail groups. If these commands are
9809 invalid in the current group, they will raise a hell and let you know.
9811 All these commands (except the expiry and edit commands) use the
9812 process/prefix convention (@pxref{Process/Prefix}).
9817 @kindex B e (Summary)
9818 @findex gnus-summary-expire-articles
9819 Run all expirable articles in the current group through the expiry
9820 process (@code{gnus-summary-expire-articles}). That is, delete all
9821 expirable articles in the group that have been around for a while.
9822 (@pxref{Expiring Mail}).
9825 @kindex B C-M-e (Summary)
9826 @findex gnus-summary-expire-articles-now
9827 Delete all the expirable articles in the group
9828 (@code{gnus-summary-expire-articles-now}). This means that @strong{all}
9829 articles eligible for expiry in the current group will
9830 disappear forever into that big @file{/dev/null} in the sky.
9833 @kindex B DEL (Summary)
9834 @findex gnus-summary-delete-article
9835 @c @icon{gnus-summary-mail-delete}
9836 Delete the mail article. This is ``delete'' as in ``delete it from your
9837 disk forever and ever, never to return again.'' Use with caution.
9838 (@code{gnus-summary-delete-article}).
9841 @kindex B m (Summary)
9843 @findex gnus-summary-move-article
9844 @vindex gnus-preserve-marks
9845 Move the article from one mail group to another
9846 (@code{gnus-summary-move-article}). Marks will be preserved if
9847 @code{gnus-preserve-marks} is non-@code{nil} (which is the default).
9850 @kindex B c (Summary)
9852 @findex gnus-summary-copy-article
9853 @c @icon{gnus-summary-mail-copy}
9854 Copy the article from one group (mail group or not) to a mail group
9855 (@code{gnus-summary-copy-article}). Marks will be preserved if
9856 @code{gnus-preserve-marks} is non-@code{nil} (which is the default).
9859 @kindex B B (Summary)
9860 @cindex crosspost mail
9861 @findex gnus-summary-crosspost-article
9862 Crosspost the current article to some other group
9863 (@code{gnus-summary-crosspost-article}). This will create a new copy of
9864 the article in the other group, and the Xref headers of the article will
9865 be properly updated.
9868 @kindex B i (Summary)
9869 @findex gnus-summary-import-article
9870 Import an arbitrary file into the current mail newsgroup
9871 (@code{gnus-summary-import-article}). You will be prompted for a file
9872 name, a @code{From} header and a @code{Subject} header.
9875 @kindex B I (Summary)
9876 @findex gnus-summary-create-article
9877 Create an empty article in the current mail newsgroups
9878 (@code{gnus-summary-create-article}). You will be prompted for a
9879 @code{From} header and a @code{Subject} header.
9882 @kindex B r (Summary)
9883 @findex gnus-summary-respool-article
9884 @vindex gnus-summary-respool-default-method
9885 Respool the mail article (@code{gnus-summary-respool-article}).
9886 @code{gnus-summary-respool-default-method} will be used as the default
9887 select method when respooling. This variable is @code{nil} by default,
9888 which means that the current group select method will be used instead.
9889 Marks will be preserved if @code{gnus-preserve-marks} is non-@code{nil}
9890 (which is the default).
9894 @kindex B w (Summary)
9896 @findex gnus-summary-edit-article
9897 @kindex C-c C-c (Article)
9898 @findex gnus-summary-edit-article-done
9899 Edit the current article (@code{gnus-summary-edit-article}). To finish
9900 editing and make the changes permanent, type @kbd{C-c C-c}
9901 (@code{gnus-summary-edit-article-done}). If you give a prefix to the
9902 @kbd{C-c C-c} command, Gnus won't re-highlight the article.
9905 @kindex B q (Summary)
9906 @findex gnus-summary-respool-query
9907 If you want to re-spool an article, you might be curious as to what group
9908 the article will end up in before you do the re-spooling. This command
9909 will tell you (@code{gnus-summary-respool-query}).
9912 @kindex B t (Summary)
9913 @findex gnus-summary-respool-trace
9914 Similarly, this command will display all fancy splitting patterns used
9915 when respooling, if any (@code{gnus-summary-respool-trace}).
9918 @kindex B p (Summary)
9919 @findex gnus-summary-article-posted-p
9920 Some people have a tendency to send you ``courtesy'' copies when they
9921 follow up to articles you have posted. These usually have a
9922 @code{Newsgroups} header in them, but not always. This command
9923 (@code{gnus-summary-article-posted-p}) will try to fetch the current
9924 article from your news server (or rather, from
9925 @code{gnus-refer-article-method} or @code{gnus-select-method}) and will
9926 report back whether it found the article or not. Even if it says that
9927 it didn't find the article, it may have been posted anyway---mail
9928 propagation is much faster than news propagation, and the news copy may
9929 just not have arrived yet.
9932 @kindex K E (Summary)
9933 @findex gnus-article-encrypt-body
9934 @vindex gnus-article-encrypt-protocol
9935 Encrypt the body of an article (@code{gnus-article-encrypt-body}).
9936 The body is encrypted with the encryption protocol specified by the
9937 variable @code{gnus-article-encrypt-protocol}.
9941 @vindex gnus-move-split-methods
9942 @cindex moving articles
9943 If you move (or copy) articles regularly, you might wish to have Gnus
9944 suggest where to put the articles. @code{gnus-move-split-methods} is a
9945 variable that uses the same syntax as @code{gnus-split-methods}
9946 (@pxref{Saving Articles}). You may customize that variable to create
9947 suggestions you find reasonable. (Note that
9948 @code{gnus-move-split-methods} uses group names where
9949 @code{gnus-split-methods} uses file names.)
9952 (setq gnus-move-split-methods
9953 '(("^From:.*Lars Magne" "nnml:junk")
9954 ("^Subject:.*gnus" "nnfolder:important")
9955 (".*" "nnml:misc")))
9959 @node Various Summary Stuff
9960 @section Various Summary Stuff
9963 * Summary Group Information:: Information oriented commands.
9964 * Searching for Articles:: Multiple article commands.
9965 * Summary Generation Commands::
9966 * Really Various Summary Commands:: Those pesky non-conformant commands.
9970 @vindex gnus-summary-display-while-building
9971 @item gnus-summary-display-while-building
9972 If non-@code{nil}, show and update the summary buffer as it's being
9973 built. If @code{t}, update the buffer after every line is inserted.
9974 If the value is an integer, @var{n}, update the display every @var{n}
9975 lines. The default is @code{nil}.
9977 @vindex gnus-summary-mode-hook
9978 @item gnus-summary-mode-hook
9979 This hook is called when creating a summary mode buffer.
9981 @vindex gnus-summary-generate-hook
9982 @item gnus-summary-generate-hook
9983 This is called as the last thing before doing the threading and the
9984 generation of the summary buffer. It's quite convenient for customizing
9985 the threading variables based on what data the newsgroup has. This hook
9986 is called from the summary buffer after most summary buffer variables
9989 @vindex gnus-summary-prepare-hook
9990 @item gnus-summary-prepare-hook
9991 It is called after the summary buffer has been generated. You might use
9992 it to, for instance, highlight lines or modify the look of the buffer in
9993 some other ungodly manner. I don't care.
9995 @vindex gnus-summary-prepared-hook
9996 @item gnus-summary-prepared-hook
9997 A hook called as the very last thing after the summary buffer has been
10000 @vindex gnus-summary-ignore-duplicates
10001 @item gnus-summary-ignore-duplicates
10002 When Gnus discovers two articles that have the same @code{Message-ID},
10003 it has to do something drastic. No articles are allowed to have the
10004 same @code{Message-ID}, but this may happen when reading mail from some
10005 sources. Gnus allows you to customize what happens with this variable.
10006 If it is @code{nil} (which is the default), Gnus will rename the
10007 @code{Message-ID} (for display purposes only) and display the article as
10008 any other article. If this variable is @code{t}, it won't display the
10009 article---it'll be as if it never existed.
10011 @vindex gnus-alter-articles-to-read-function
10012 @item gnus-alter-articles-to-read-function
10013 This function, which takes two parameters (the group name and the list
10014 of articles to be selected), is called to allow the user to alter the
10015 list of articles to be selected.
10017 For instance, the following function adds the list of cached articles to
10018 the list in one particular group:
10021 (defun my-add-cached-articles (group articles)
10022 (if (string= group "some.group")
10023 (append gnus-newsgroup-cached articles)
10027 @vindex gnus-newsgroup-variables
10028 @item gnus-newsgroup-variables
10029 A list of newsgroup (summary buffer) local variables, or cons of
10030 variables and their default values (when the default values are not
10031 nil), that should be made global while the summary buffer is active.
10032 These variables can be used to set variables in the group parameters
10033 while still allowing them to affect operations done in other
10034 buffers. For example:
10037 (setq gnus-newsgroup-variables
10038 '(message-use-followup-to
10039 (gnus-visible-headers .
10040 "^From:\\|^Newsgroups:\\|^Subject:\\|^Date:\\|^To:")))
10046 @node Summary Group Information
10047 @subsection Summary Group Information
10052 @kindex H f (Summary)
10053 @findex gnus-summary-fetch-faq
10054 @vindex gnus-group-faq-directory
10055 Try to fetch the FAQ (list of frequently asked questions) for the
10056 current group (@code{gnus-summary-fetch-faq}). Gnus will try to get the
10057 FAQ from @code{gnus-group-faq-directory}, which is usually a directory
10058 on a remote machine. This variable can also be a list of directories.
10059 In that case, giving a prefix to this command will allow you to choose
10060 between the various sites. @code{ange-ftp} or @code{efs} will probably
10061 be used for fetching the file.
10064 @kindex H d (Summary)
10065 @findex gnus-summary-describe-group
10066 Give a brief description of the current group
10067 (@code{gnus-summary-describe-group}). If given a prefix, force
10068 rereading the description from the server.
10071 @kindex H h (Summary)
10072 @findex gnus-summary-describe-briefly
10073 Give an extremely brief description of the most important summary
10074 keystrokes (@code{gnus-summary-describe-briefly}).
10077 @kindex H i (Summary)
10078 @findex gnus-info-find-node
10079 Go to the Gnus info node (@code{gnus-info-find-node}).
10083 @node Searching for Articles
10084 @subsection Searching for Articles
10089 @kindex M-s (Summary)
10090 @findex gnus-summary-search-article-forward
10091 Search through all subsequent (raw) articles for a regexp
10092 (@code{gnus-summary-search-article-forward}).
10095 @kindex M-r (Summary)
10096 @findex gnus-summary-search-article-backward
10097 Search through all previous (raw) articles for a regexp
10098 (@code{gnus-summary-search-article-backward}).
10101 @kindex & (Summary)
10102 @findex gnus-summary-execute-command
10103 This command will prompt you for a header, a regular expression to match
10104 on this field, and a command to be executed if the match is made
10105 (@code{gnus-summary-execute-command}). If the header is an empty
10106 string, the match is done on the entire article. If given a prefix,
10107 search backward instead.
10109 For instance, @kbd{& RET some.*string #} will put the process mark on
10110 all articles that have heads or bodies that match @samp{some.*string}.
10113 @kindex M-& (Summary)
10114 @findex gnus-summary-universal-argument
10115 Perform any operation on all articles that have been marked with
10116 the process mark (@code{gnus-summary-universal-argument}).
10119 @node Summary Generation Commands
10120 @subsection Summary Generation Commands
10125 @kindex Y g (Summary)
10126 @findex gnus-summary-prepare
10127 Regenerate the current summary buffer (@code{gnus-summary-prepare}).
10130 @kindex Y c (Summary)
10131 @findex gnus-summary-insert-cached-articles
10132 Pull all cached articles (for the current group) into the summary buffer
10133 (@code{gnus-summary-insert-cached-articles}).
10136 @kindex Y d (Summary)
10137 @findex gnus-summary-insert-dormant-articles
10138 Pull all dormant articles (for the current group) into the summary buffer
10139 (@code{gnus-summary-insert-dormant-articles}).
10144 @node Really Various Summary Commands
10145 @subsection Really Various Summary Commands
10151 @kindex C-d (Summary)
10152 @kindex A D (Summary)
10153 @findex gnus-summary-enter-digest-group
10154 If the current article is a collection of other articles (for instance,
10155 a digest), you might use this command to enter a group based on the that
10156 article (@code{gnus-summary-enter-digest-group}). Gnus will try to
10157 guess what article type is currently displayed unless you give a prefix
10158 to this command, which forces a ``digest'' interpretation. Basically,
10159 whenever you see a message that is a collection of other messages of
10160 some format, you @kbd{C-d} and read these messages in a more convenient
10164 @kindex C-M-d (Summary)
10165 @findex gnus-summary-read-document
10166 This command is very similar to the one above, but lets you gather
10167 several documents into one biiig group
10168 (@code{gnus-summary-read-document}). It does this by opening several
10169 @code{nndoc} groups for each document, and then opening an
10170 @code{nnvirtual} group on top of these @code{nndoc} groups. This
10171 command understands the process/prefix convention
10172 (@pxref{Process/Prefix}).
10175 @kindex C-t (Summary)
10176 @findex gnus-summary-toggle-truncation
10177 Toggle truncation of summary lines
10178 (@code{gnus-summary-toggle-truncation}). This will probably confuse the
10179 line centering function in the summary buffer, so it's not a good idea
10180 to have truncation switched off while reading articles.
10183 @kindex = (Summary)
10184 @findex gnus-summary-expand-window
10185 Expand the summary buffer window (@code{gnus-summary-expand-window}).
10186 If given a prefix, force an @code{article} window configuration.
10189 @kindex C-M-e (Summary)
10190 @findex gnus-summary-edit-parameters
10191 Edit the group parameters (@pxref{Group Parameters}) of the current
10192 group (@code{gnus-summary-edit-parameters}).
10195 @kindex C-M-a (Summary)
10196 @findex gnus-summary-customize-parameters
10197 Customize the group parameters (@pxref{Group Parameters}) of the current
10198 group (@code{gnus-summary-customize-parameters}).
10203 @node Exiting the Summary Buffer
10204 @section Exiting the Summary Buffer
10205 @cindex summary exit
10206 @cindex exiting groups
10208 Exiting from the summary buffer will normally update all info on the
10209 group and return you to the group buffer.
10215 @kindex Z Z (Summary)
10216 @kindex q (Summary)
10217 @findex gnus-summary-exit
10218 @vindex gnus-summary-exit-hook
10219 @vindex gnus-summary-prepare-exit-hook
10220 @vindex gnus-group-no-more-groups-hook
10221 @c @icon{gnus-summary-exit}
10222 Exit the current group and update all information on the group
10223 (@code{gnus-summary-exit}). @code{gnus-summary-prepare-exit-hook} is
10224 called before doing much of the exiting, which calls
10225 @code{gnus-summary-expire-articles} by default.
10226 @code{gnus-summary-exit-hook} is called after finishing the exit
10227 process. @code{gnus-group-no-more-groups-hook} is run when returning to
10228 group mode having no more (unread) groups.
10232 @kindex Z E (Summary)
10233 @kindex Q (Summary)
10234 @findex gnus-summary-exit-no-update
10235 Exit the current group without updating any information on the group
10236 (@code{gnus-summary-exit-no-update}).
10240 @kindex Z c (Summary)
10241 @kindex c (Summary)
10242 @findex gnus-summary-catchup-and-exit
10243 @c @icon{gnus-summary-catchup-and-exit}
10244 Mark all unticked articles in the group as read and then exit
10245 (@code{gnus-summary-catchup-and-exit}).
10248 @kindex Z C (Summary)
10249 @findex gnus-summary-catchup-all-and-exit
10250 Mark all articles, even the ticked ones, as read and then exit
10251 (@code{gnus-summary-catchup-all-and-exit}).
10254 @kindex Z n (Summary)
10255 @findex gnus-summary-catchup-and-goto-next-group
10256 Mark all articles as read and go to the next group
10257 (@code{gnus-summary-catchup-and-goto-next-group}).
10260 @kindex Z R (Summary)
10261 @findex gnus-summary-reselect-current-group
10262 Exit this group, and then enter it again
10263 (@code{gnus-summary-reselect-current-group}). If given a prefix, select
10264 all articles, both read and unread.
10268 @kindex Z G (Summary)
10269 @kindex M-g (Summary)
10270 @findex gnus-summary-rescan-group
10271 @c @icon{gnus-summary-mail-get}
10272 Exit the group, check for new articles in the group, and select the
10273 group (@code{gnus-summary-rescan-group}). If given a prefix, select all
10274 articles, both read and unread.
10277 @kindex Z N (Summary)
10278 @findex gnus-summary-next-group
10279 Exit the group and go to the next group
10280 (@code{gnus-summary-next-group}).
10283 @kindex Z P (Summary)
10284 @findex gnus-summary-prev-group
10285 Exit the group and go to the previous group
10286 (@code{gnus-summary-prev-group}).
10289 @kindex Z s (Summary)
10290 @findex gnus-summary-save-newsrc
10291 Save the current number of read/marked articles in the dribble buffer
10292 and then save the dribble buffer (@code{gnus-summary-save-newsrc}). If
10293 given a prefix, also save the @file{.newsrc} file(s). Using this
10294 command will make exit without updating (the @kbd{Q} command) worthless.
10297 @vindex gnus-exit-group-hook
10298 @code{gnus-exit-group-hook} is called when you exit the current group
10299 with an ``updating'' exit. For instance @kbd{Q}
10300 (@code{gnus-summary-exit-no-update}) does not call this hook.
10302 @findex gnus-summary-wake-up-the-dead
10303 @findex gnus-dead-summary-mode
10304 @vindex gnus-kill-summary-on-exit
10305 If you're in the habit of exiting groups, and then changing your mind
10306 about it, you might set @code{gnus-kill-summary-on-exit} to @code{nil}.
10307 If you do that, Gnus won't kill the summary buffer when you exit it.
10308 (Quelle surprise!) Instead it will change the name of the buffer to
10309 something like @samp{*Dead Summary ... *} and install a minor mode
10310 called @code{gnus-dead-summary-mode}. Now, if you switch back to this
10311 buffer, you'll find that all keys are mapped to a function called
10312 @code{gnus-summary-wake-up-the-dead}. So tapping any keys in a dead
10313 summary buffer will result in a live, normal summary buffer.
10315 There will never be more than one dead summary buffer at any one time.
10317 @vindex gnus-use-cross-reference
10318 The data on the current group will be updated (which articles you have
10319 read, which articles you have replied to, etc.) when you exit the
10320 summary buffer. If the @code{gnus-use-cross-reference} variable is
10321 @code{t} (which is the default), articles that are cross-referenced to
10322 this group and are marked as read, will also be marked as read in the
10323 other subscribed groups they were cross-posted to. If this variable is
10324 neither @code{nil} nor @code{t}, the article will be marked as read in
10325 both subscribed and unsubscribed groups (@pxref{Crosspost Handling}).
10328 @node Crosspost Handling
10329 @section Crosspost Handling
10333 Marking cross-posted articles as read ensures that you'll never have to
10334 read the same article more than once. Unless, of course, somebody has
10335 posted it to several groups separately. Posting the same article to
10336 several groups (not cross-posting) is called @dfn{spamming}, and you are
10337 by law required to send nasty-grams to anyone who perpetrates such a
10338 heinous crime. You may want to try NoCeM handling to filter out spam
10341 Remember: Cross-posting is kinda ok, but posting the same article
10342 separately to several groups is not. Massive cross-posting (aka.
10343 @dfn{velveeta}) is to be avoided at all costs, and you can even use the
10344 @code{gnus-summary-mail-crosspost-complaint} command to complain about
10345 excessive crossposting (@pxref{Summary Mail Commands}).
10347 @cindex cross-posting
10350 One thing that may cause Gnus to not do the cross-posting thing
10351 correctly is if you use an @sc{nntp} server that supports @sc{xover}
10352 (which is very nice, because it speeds things up considerably) which
10353 does not include the @code{Xref} header in its @sc{nov} lines. This is
10354 Evil, but all too common, alas, alack. Gnus tries to Do The Right Thing
10355 even with @sc{xover} by registering the @code{Xref} lines of all
10356 articles you actually read, but if you kill the articles, or just mark
10357 them as read without reading them, Gnus will not get a chance to snoop
10358 the @code{Xref} lines out of these articles, and will be unable to use
10359 the cross reference mechanism.
10361 @cindex LIST overview.fmt
10362 @cindex overview.fmt
10363 To check whether your @sc{nntp} server includes the @code{Xref} header
10364 in its overview files, try @samp{telnet your.nntp.server nntp},
10365 @samp{MODE READER} on @code{inn} servers, and then say @samp{LIST
10366 overview.fmt}. This may not work, but if it does, and the last line you
10367 get does not read @samp{Xref:full}, then you should shout and whine at
10368 your news admin until she includes the @code{Xref} header in the
10371 @vindex gnus-nov-is-evil
10372 If you want Gnus to get the @code{Xref}s right all the time, you have to
10373 set @code{gnus-nov-is-evil} to @code{t}, which slows things down
10378 For an alternative approach, @pxref{Duplicate Suppression}.
10381 @node Duplicate Suppression
10382 @section Duplicate Suppression
10384 By default, Gnus tries to make sure that you don't have to read the same
10385 article more than once by utilizing the crossposting mechanism
10386 (@pxref{Crosspost Handling}). However, that simple and efficient
10387 approach may not work satisfactory for some users for various
10392 The @sc{nntp} server may fail to generate the @code{Xref} header. This
10393 is evil and not very common.
10396 The @sc{nntp} server may fail to include the @code{Xref} header in the
10397 @file{.overview} data bases. This is evil and all too common, alas.
10400 You may be reading the same group (or several related groups) from
10401 different @sc{nntp} servers.
10404 You may be getting mail that duplicates articles posted to groups.
10407 I'm sure there are other situations where @code{Xref} handling fails as
10408 well, but these four are the most common situations.
10410 If, and only if, @code{Xref} handling fails for you, then you may
10411 consider switching on @dfn{duplicate suppression}. If you do so, Gnus
10412 will remember the @code{Message-ID}s of all articles you have read or
10413 otherwise marked as read, and then, as if by magic, mark them as read
10414 all subsequent times you see them---in @emph{all} groups. Using this
10415 mechanism is quite likely to be somewhat inefficient, but not overly
10416 so. It's certainly preferable to reading the same articles more than
10419 Duplicate suppression is not a very subtle instrument. It's more like a
10420 sledge hammer than anything else. It works in a very simple
10421 fashion---if you have marked an article as read, it adds this Message-ID
10422 to a cache. The next time it sees this Message-ID, it will mark the
10423 article as read with the @samp{M} mark. It doesn't care what group it
10424 saw the article in.
10427 @item gnus-suppress-duplicates
10428 @vindex gnus-suppress-duplicates
10429 If non-@code{nil}, suppress duplicates.
10431 @item gnus-save-duplicate-list
10432 @vindex gnus-save-duplicate-list
10433 If non-@code{nil}, save the list of duplicates to a file. This will
10434 make startup and shutdown take longer, so the default is @code{nil}.
10435 However, this means that only duplicate articles read in a single Gnus
10436 session are suppressed.
10438 @item gnus-duplicate-list-length
10439 @vindex gnus-duplicate-list-length
10440 This variable says how many @code{Message-ID}s to keep in the duplicate
10441 suppression list. The default is 10000.
10443 @item gnus-duplicate-file
10444 @vindex gnus-duplicate-file
10445 The name of the file to store the duplicate suppression list in. The
10446 default is @file{~/News/suppression}.
10449 If you have a tendency to stop and start Gnus often, setting
10450 @code{gnus-save-duplicate-list} to @code{t} is probably a good idea. If
10451 you leave Gnus running for weeks on end, you may have it @code{nil}. On
10452 the other hand, saving the list makes startup and shutdown much slower,
10453 so that means that if you stop and start Gnus often, you should set
10454 @code{gnus-save-duplicate-list} to @code{nil}. Uhm. I'll leave this up
10455 to you to figure out, I think.
10460 Gnus is able to verify signed messages or decrypt encrypted messages.
10461 The formats that are supported are PGP, @sc{pgp/mime} and @sc{s/mime},
10462 however you need some external programs to get things to work:
10466 To handle PGP and PGP/MIME messages, you have to install an OpenPGP
10467 implementation such as GnuPG. The lisp interface to GnuPG included
10468 with Gnus is called PGG (@pxref{Top, ,PGG, pgg, PGG Manual}), but
10469 Mailcrypt and gpg.el are also supported.
10472 To handle @sc{s/mime} message, you need to install OpenSSL. OpenSSL 0.9.6
10473 or newer is recommended.
10477 More information on how to set things up can be found in the message
10478 manual (@pxref{Security, ,Security, message, Message Manual}).
10481 @item mm-verify-option
10482 @vindex mm-verify-option
10483 Option of verifying signed parts. @code{never}, not verify;
10484 @code{always}, always verify; @code{known}, only verify known
10485 protocols. Otherwise, ask user.
10487 @item mm-decrypt-option
10488 @vindex mm-decrypt-option
10489 Option of decrypting encrypted parts. @code{never}, no decryption;
10490 @code{always}, always decrypt; @code{known}, only decrypt known
10491 protocols. Otherwise, ask user.
10494 @vindex mml1991-use
10495 Symbol indicating elisp interface to OpenPGP implementation for PGP
10496 messages. The default is @code{pgg}, but @code{mailcrypt} and
10497 @code{gpg} are also supported although deprecated.
10500 @vindex mml2015-use
10501 Symbol indicating elisp interface to OpenPGP implementation for
10502 PGP/MIME messages. The default is @code{pgg}, but @code{mailcrypt}
10503 and @code{gpg} are also supported although deprecated.
10508 @section Mailing List
10510 @kindex A M (summary)
10511 @findex gnus-mailing-list-insinuate
10512 Gnus understands some mailing list fields of RFC 2369. To enable it,
10513 add a @code{to-list} group parameter (@pxref{Group Parameters}),
10514 possibly using @kbd{A M} (@code{gnus-mailing-list-insinuate}) in the
10517 That enables the following commands to the summary buffer:
10522 @kindex C-c C-n h (Summary)
10523 @findex gnus-mailing-list-help
10524 Send a message to fetch mailing list help, if List-Help field exists.
10527 @kindex C-c C-n s (Summary)
10528 @findex gnus-mailing-list-subscribe
10529 Send a message to subscribe the mailing list, if List-Subscribe field exists.
10532 @kindex C-c C-n u (Summary)
10533 @findex gnus-mailing-list-unsubscribe
10534 Send a message to unsubscribe the mailing list, if List-Unsubscribe
10538 @kindex C-c C-n p (Summary)
10539 @findex gnus-mailing-list-post
10540 Post to the mailing list, if List-Post field exists.
10543 @kindex C-c C-n o (Summary)
10544 @findex gnus-mailing-list-owner
10545 Send a message to the mailing list owner, if List-Owner field exists.
10548 @kindex C-c C-n a (Summary)
10549 @findex gnus-mailing-list-owner
10550 Browse the mailing list archive, if List-Archive field exists.
10555 @node Article Buffer
10556 @chapter Article Buffer
10557 @cindex article buffer
10559 The articles are displayed in the article buffer, of which there is only
10560 one. All the summary buffers share the same article buffer unless you
10561 tell Gnus otherwise.
10564 * Hiding Headers:: Deciding what headers should be displayed.
10565 * Using MIME:: Pushing articles through @sc{mime} before reading them.
10566 * Customizing Articles:: Tailoring the look of the articles.
10567 * Article Keymap:: Keystrokes available in the article buffer.
10568 * Misc Article:: Other stuff.
10572 @node Hiding Headers
10573 @section Hiding Headers
10574 @cindex hiding headers
10575 @cindex deleting headers
10577 The top section of each article is the @dfn{head}. (The rest is the
10578 @dfn{body}, but you may have guessed that already.)
10580 @vindex gnus-show-all-headers
10581 There is a lot of useful information in the head: the name of the person
10582 who wrote the article, the date it was written and the subject of the
10583 article. That's well and nice, but there's also lots of information
10584 most people do not want to see---what systems the article has passed
10585 through before reaching you, the @code{Message-ID}, the
10586 @code{References}, etc. ad nauseum---and you'll probably want to get rid
10587 of some of those lines. If you want to keep all those lines in the
10588 article buffer, you can set @code{gnus-show-all-headers} to @code{t}.
10590 Gnus provides you with two variables for sifting headers:
10594 @item gnus-visible-headers
10595 @vindex gnus-visible-headers
10596 If this variable is non-@code{nil}, it should be a regular expression
10597 that says what headers you wish to keep in the article buffer. All
10598 headers that do not match this variable will be hidden.
10600 For instance, if you only want to see the name of the person who wrote
10601 the article and the subject, you'd say:
10604 (setq gnus-visible-headers "^From:\\|^Subject:")
10607 This variable can also be a list of regexps to match headers to
10610 @item gnus-ignored-headers
10611 @vindex gnus-ignored-headers
10612 This variable is the reverse of @code{gnus-visible-headers}. If this
10613 variable is set (and @code{gnus-visible-headers} is @code{nil}), it
10614 should be a regular expression that matches all lines that you want to
10615 hide. All lines that do not match this variable will remain visible.
10617 For instance, if you just want to get rid of the @code{References} line
10618 and the @code{Xref} line, you might say:
10621 (setq gnus-ignored-headers "^References:\\|^Xref:")
10624 This variable can also be a list of regexps to match headers to
10627 Note that if @code{gnus-visible-headers} is non-@code{nil}, this
10628 variable will have no effect.
10632 @vindex gnus-sorted-header-list
10633 Gnus can also sort the headers for you. (It does this by default.) You
10634 can control the sorting by setting the @code{gnus-sorted-header-list}
10635 variable. It is a list of regular expressions that says in what order
10636 the headers are to be displayed.
10638 For instance, if you want the name of the author of the article first,
10639 and then the subject, you might say something like:
10642 (setq gnus-sorted-header-list '("^From:" "^Subject:"))
10645 Any headers that are to remain visible, but are not listed in this
10646 variable, will be displayed in random order after all the headers listed in this variable.
10648 @findex gnus-article-hide-boring-headers
10649 @vindex gnus-boring-article-headers
10650 You can hide further boring headers by setting
10651 @code{gnus-treat-hide-boring-headers} to @code{head}. What this function
10652 does depends on the @code{gnus-boring-article-headers} variable. It's a
10653 list, but this list doesn't actually contain header names. Instead is
10654 lists various @dfn{boring conditions} that Gnus can check and remove
10657 These conditions are:
10660 Remove all empty headers.
10662 Remove the @code{Followup-To} header if it is identical to the
10663 @code{Newsgroups} header.
10665 Remove the @code{Reply-To} header if it lists the same address as the
10666 @code{From} header.
10668 Remove the @code{Newsgroups} header if it only contains the current group
10671 Remove the @code{To} header if it only contains the address identical to
10672 the current groups's @code{to-address} parameter.
10674 Remove the @code{To} header if it only contains the address identical to
10675 the current groups's @code{to-list} parameter.
10677 Remove the @code{CC} header if it only contains the address identical to
10678 the current groups's @code{to-list} parameter.
10680 Remove the @code{Date} header if the article is less than three days
10683 Remove the @code{To} header if it is very long.
10685 Remove all @code{To} headers if there are more than one.
10688 To include these three elements, you could say something like:
10691 (setq gnus-boring-article-headers
10692 '(empty followup-to reply-to))
10695 This is also the default value for this variable.
10699 @section Using MIME
10702 Mime is a standard for waving your hands through the air, aimlessly,
10703 while people stand around yawning.
10705 @sc{mime}, however, is a standard for encoding your articles, aimlessly,
10706 while all newsreaders die of fear.
10708 @sc{mime} may specify what character set the article uses, the encoding
10709 of the characters, and it also makes it possible to embed pictures and
10710 other naughty stuff in innocent-looking articles.
10712 @vindex gnus-display-mime-function
10713 @findex gnus-display-mime
10714 Gnus pushes @sc{mime} articles through @code{gnus-display-mime-function}
10715 to display the @sc{mime} parts. This is @code{gnus-display-mime} by
10716 default, which creates a bundle of clickable buttons that can be used to
10717 display, save and manipulate the @sc{mime} objects.
10719 The following commands are available when you have placed point over a
10723 @findex gnus-article-press-button
10724 @item RET (Article)
10725 @kindex RET (Article)
10726 @itemx BUTTON-2 (Article)
10727 Toggle displaying of the @sc{mime} object
10728 (@code{gnus-article-press-button}). If builtin viewers can not display
10729 the object, Gnus resorts to external viewers in the @file{mailcap}
10730 files. If a viewer has the @samp{copiousoutput} specification, the
10731 object is displayed inline.
10733 @findex gnus-mime-view-part
10734 @item M-RET (Article)
10735 @kindex M-RET (Article)
10737 Prompt for a method, and then view the @sc{mime} object using this
10738 method (@code{gnus-mime-view-part}).
10740 @findex gnus-mime-view-part-as-type
10742 @kindex t (Article)
10743 View the @sc{mime} object as if it were a different @sc{mime} media type
10744 (@code{gnus-mime-view-part-as-type}).
10746 @findex gnus-mime-view-part-as-charset
10748 @kindex C (Article)
10749 Prompt for a charset, and then view the @sc{mime} object using this
10750 charset (@code{gnus-mime-view-part-as-charset}).
10752 @findex gnus-mime-save-part
10754 @kindex o (Article)
10755 Prompt for a file name, and then save the @sc{mime} object
10756 (@code{gnus-mime-save-part}).
10758 @findex gnus-mime-save-part-and-strip
10759 @item C-o (Article)
10760 @kindex C-o (Article)
10761 Prompt for a file name, then save the @sc{mime} object and strip it from
10762 the article. Then proceed to article editing, where a reasonable
10763 suggestion is being made on how the altered article should look
10764 like. The stripped @sc{mime} object will be referred via the
10765 message/external-body @sc{mime} type.
10766 (@code{gnus-mime-save-part-and-strip}).
10768 @findex gnus-mime-delete-part
10770 @kindex d (Article)
10771 Delete the @sc{mime} object from the article and replace it with some
10772 information about the removed @sc{mime} object
10773 (@code{gnus-mime-delete-part}).
10775 @findex gnus-mime-copy-part
10777 @kindex c (Article)
10778 Copy the @sc{mime} object to a fresh buffer and display this buffer
10779 (@code{gnus-mime-copy-part}). Compressed files like @file{.gz} and
10780 @file{.bz2} are automatically decompressed if
10781 @code{auto-compression-mode} is enabled (@pxref{Compressed Files,,
10782 Accessing Compressed Files, emacs, The Emacs Editor}).
10784 @findex gnus-mime-print-part
10786 @kindex p (Article)
10787 Print the @sc{mime} object (@code{gnus-mime-print-part}). This
10788 command respects the @samp{print=} specifications in the
10789 @file{.mailcap} file.
10791 @findex gnus-mime-inline-part
10793 @kindex i (Article)
10794 Insert the contents of the @sc{mime} object into the buffer
10795 (@code{gnus-mime-inline-part}) as text/plain. If given a prefix, insert
10796 the raw contents without decoding. If given a numerical prefix, you can
10797 do semi-manual charset stuff (see
10798 @code{gnus-summary-show-article-charset-alist} in @pxref{Paging the
10801 @findex gnus-mime-view-part-internally
10803 @kindex E (Article)
10804 View the @sc{mime} object with an internal viewer. If no internal
10805 viewer is available, use an external viewer
10806 (@code{gnus-mime-view-part-internally}).
10808 @findex gnus-mime-view-part-externally
10810 @kindex e (Article)
10811 View the @sc{mime} object with an external viewer.
10812 (@code{gnus-mime-view-part-externally}).
10814 @findex gnus-mime-pipe-part
10816 @kindex | (Article)
10817 Output the @sc{mime} object to a process (@code{gnus-mime-pipe-part}).
10819 @findex gnus-mime-action-on-part
10821 @kindex . (Article)
10822 Interactively run an action on the @sc{mime} object
10823 (@code{gnus-mime-action-on-part}).
10827 Gnus will display some @sc{mime} objects automatically. The way Gnus
10828 determines which parts to do this with is described in the Emacs
10831 It might be best to just use the toggling functions from the article
10832 buffer to avoid getting nasty surprises. (For instance, you enter the
10833 group @samp{alt.sing-a-long} and, before you know it, @sc{mime} has
10834 decoded the sound file in the article and some horrible sing-a-long song
10835 comes screaming out your speakers, and you can't find the volume button,
10836 because there isn't one, and people are starting to look at you, and you
10837 try to stop the program, but you can't, and you can't find the program
10838 to control the volume, and everybody else in the room suddenly decides
10839 to look at you disdainfully, and you'll feel rather stupid.)
10841 Any similarity to real events and people is purely coincidental. Ahem.
10843 Also see @pxref{MIME Commands}.
10846 @node Customizing Articles
10847 @section Customizing Articles
10848 @cindex article customization
10850 A slew of functions for customizing how the articles are to look like
10851 exist. You can call these functions interactively
10852 (@pxref{Article Washing}), or you can have them
10853 called automatically when you select the articles.
10855 To have them called automatically, you should set the corresponding
10856 ``treatment'' variable. For instance, to have headers hidden, you'd set
10857 @code{gnus-treat-hide-headers}. Below is a list of variables that can
10858 be set, but first we discuss the values these variables can have.
10860 Note: Some values, while valid, make little sense. Check the list below
10861 for sensible values.
10865 @code{nil}: Don't do this treatment.
10868 @code{t}: Do this treatment on all body parts.
10871 @code{head}: Do the treatment on the headers.
10874 @code{last}: Do this treatment on the last part.
10877 An integer: Do this treatment on all body parts that have a length less
10881 A list of strings: Do this treatment on all body parts that are in
10882 articles that are read in groups that have names that match one of the
10883 regexps in the list.
10886 A list where the first element is not a string:
10888 The list is evaluated recursively. The first element of the list is a
10889 predicate. The following predicates are recognized: @code{or},
10890 @code{and}, @code{not} and @code{typep}. Here's an example:
10894 (typep "text/x-vcard"))
10899 You may have noticed that the word @dfn{part} is used here. This refers
10900 to the fact that some messages are @sc{mime} multipart articles that may
10901 be divided into several parts. Articles that are not multiparts are
10902 considered to contain just a single part.
10904 @vindex gnus-article-treat-types
10905 Are the treatments applied to all sorts of multipart parts? Yes, if you
10906 want to, but by default, only @samp{text/plain} parts are given the
10907 treatment. This is controlled by the @code{gnus-article-treat-types}
10908 variable, which is a list of regular expressions that are matched to the
10909 type of the part. This variable is ignored if the value of the
10910 controlling variable is a predicate list, as described above.
10912 The following treatment options are available. The easiest way to
10913 customize this is to examine the @code{gnus-article-treat} customization
10914 group. Values in parenthesis are suggested sensible values. Others are
10915 possible but those listed are probably sufficient for most people.
10918 @item gnus-treat-buttonize (t, integer)
10919 @item gnus-treat-buttonize-head (head)
10921 @xref{Article Buttons}.
10923 @item gnus-treat-capitalize-sentences (t, integer)
10924 @item gnus-treat-overstrike (t, integer)
10925 @item gnus-treat-strip-cr (t, integer)
10926 @item gnus-treat-strip-headers-in-body (t, integer)
10927 @item gnus-treat-strip-leading-blank-lines (t, integer)
10928 @item gnus-treat-strip-multiple-blank-lines (t, integer)
10929 @item gnus-treat-strip-pem (t, last, integer)
10930 @item gnus-treat-strip-trailing-blank-lines (t, last, integer)
10931 @item gnus-treat-unsplit-urls (t, integer)
10932 @item gnus-treat-wash-html (t, integer)
10934 @xref{Article Washing}.
10936 @item gnus-treat-date-english (head)
10937 @item gnus-treat-date-iso8601 (head)
10938 @item gnus-treat-date-lapsed (head)
10939 @item gnus-treat-date-local (head)
10940 @item gnus-treat-date-original (head)
10941 @item gnus-treat-date-user-defined (head)
10942 @item gnus-treat-date-ut (head)
10944 @xref{Article Date}.
10946 @item gnus-treat-from-picon (head)
10947 @item gnus-treat-mail-picon (head)
10948 @item gnus-treat-newsgroups-picon (head)
10952 @item gnus-treat-display-smileys (t, integer)
10954 @item gnus-treat-body-boundary (head)
10956 @vindex gnus-body-boundary-delimiter
10957 Adds a delimiter between header and body, the string used as delimiter
10958 is controlled by @code{gnus-body-boundary-delimiter}.
10962 @item gnus-treat-display-xface (head)
10966 @item gnus-treat-emphasize (t, head, integer)
10967 @item gnus-treat-fill-article (t, integer)
10968 @item gnus-treat-fill-long-lines (t, integer)
10969 @item gnus-treat-hide-boring-headers (head)
10970 @item gnus-treat-hide-citation (t, integer)
10971 @item gnus-treat-hide-citation-maybe (t, integer)
10972 @item gnus-treat-hide-headers (head)
10973 @item gnus-treat-hide-signature (t, last)
10974 @item gnus-treat-strip-banner (t, last)
10975 @item gnus-treat-strip-list-identifiers (head)
10977 @xref{Article Hiding}.
10979 @item gnus-treat-highlight-citation (t, integer)
10980 @item gnus-treat-highlight-headers (head)
10981 @item gnus-treat-highlight-signature (t, last, integer)
10983 @xref{Article Highlighting}.
10985 @item gnus-treat-play-sounds
10986 @item gnus-treat-translate
10987 @item gnus-treat-x-pgp-sig (head)
10989 @item gnus-treat-unfold-headers (head)
10990 @item gnus-treat-fold-headers (head)
10991 @item gnus-treat-fold-newsgroups (head)
10992 @item gnus-treat-leading-whitespace (head)
10994 @xref{Article Header}.
10999 @vindex gnus-part-display-hook
11000 You can, of course, write your own functions to be called from
11001 @code{gnus-part-display-hook}. The functions are called narrowed to the
11002 part, and you can do anything you like, pretty much. There is no
11003 information that you have to keep in the buffer---you can change
11007 @node Article Keymap
11008 @section Article Keymap
11010 Most of the keystrokes in the summary buffer can also be used in the
11011 article buffer. They should behave as if you typed them in the summary
11012 buffer, which means that you don't actually have to have a summary
11013 buffer displayed while reading. You can do it all from the article
11016 A few additional keystrokes are available:
11021 @kindex SPACE (Article)
11022 @findex gnus-article-next-page
11023 Scroll forwards one page (@code{gnus-article-next-page}).
11024 This is exactly the same as @kbd{h SPACE h}.
11027 @kindex DEL (Article)
11028 @findex gnus-article-prev-page
11029 Scroll backwards one page (@code{gnus-article-prev-page}).
11030 This is exactly the same as @kbd{h DEL h}.
11033 @kindex C-c ^ (Article)
11034 @findex gnus-article-refer-article
11035 If point is in the neighborhood of a @code{Message-ID} and you press
11036 @kbd{C-c ^}, Gnus will try to get that article from the server
11037 (@code{gnus-article-refer-article}).
11040 @kindex C-c C-m (Article)
11041 @findex gnus-article-mail
11042 Send a reply to the address near point (@code{gnus-article-mail}). If
11043 given a prefix, include the mail.
11046 @kindex s (Article)
11047 @findex gnus-article-show-summary
11048 Reconfigure the buffers so that the summary buffer becomes visible
11049 (@code{gnus-article-show-summary}).
11052 @kindex ? (Article)
11053 @findex gnus-article-describe-briefly
11054 Give a very brief description of the available keystrokes
11055 (@code{gnus-article-describe-briefly}).
11058 @kindex TAB (Article)
11059 @findex gnus-article-next-button
11060 Go to the next button, if any (@code{gnus-article-next-button}). This
11061 only makes sense if you have buttonizing turned on.
11064 @kindex M-TAB (Article)
11065 @findex gnus-article-prev-button
11066 Go to the previous button, if any (@code{gnus-article-prev-button}).
11069 @kindex R (Article)
11070 @findex gnus-article-reply-with-original
11071 Send a reply to the current article and yank the current article
11072 (@code{gnus-article-reply-with-original}). If given a prefix, make a
11073 wide reply. If the region is active, only yank the text in the
11077 @kindex F (Article)
11078 @findex gnus-article-followup-with-original
11079 Send a followup to the current article and yank the current article
11080 (@code{gnus-article-followup-with-original}). If given a prefix, make
11081 a wide reply. If the region is active, only yank the text in the
11089 @section Misc Article
11093 @item gnus-single-article-buffer
11094 @vindex gnus-single-article-buffer
11095 If non-@code{nil}, use the same article buffer for all the groups.
11096 (This is the default.) If @code{nil}, each group will have its own
11099 @vindex gnus-article-decode-hook
11100 @item gnus-article-decode-hook
11102 Hook used to decode @sc{mime} articles. The default value is
11103 @code{(article-decode-charset article-decode-encoded-words)}
11105 @vindex gnus-article-prepare-hook
11106 @item gnus-article-prepare-hook
11107 This hook is called right after the article has been inserted into the
11108 article buffer. It is mainly intended for functions that do something
11109 depending on the contents; it should probably not be used for changing
11110 the contents of the article buffer.
11112 @item gnus-article-mode-hook
11113 @vindex gnus-article-mode-hook
11114 Hook called in article mode buffers.
11116 @item gnus-article-mode-syntax-table
11117 @vindex gnus-article-mode-syntax-table
11118 Syntax table used in article buffers. It is initialized from
11119 @code{text-mode-syntax-table}.
11121 @vindex gnus-article-over-scroll
11122 @item gnus-article-over-scroll
11123 If non-@code{nil}, allow scrolling the article buffer even when there
11124 no more new text to scroll in. The default is @code{nil}.
11126 @vindex gnus-article-mode-line-format
11127 @item gnus-article-mode-line-format
11128 This variable is a format string along the same lines as
11129 @code{gnus-summary-mode-line-format} (@pxref{Mode Line Formatting}). It
11130 accepts the same format specifications as that variable, with two
11136 The @dfn{wash status} of the article. This is a short string with one
11137 character for each possible article wash operation that may have been
11138 performed. The characters and their meaning:
11143 Displayed when cited text may be hidden in the article buffer.
11146 Displayed when headers are hidden in the article buffer.
11149 Displayed when article is digitally signed or encrypted, and Gnus has
11150 hidden the security headers. (N.B. does not tell anything about
11151 security status, i.e. good or bad signature.)
11154 Displayed when the signature has been hidden in the Article buffer.
11157 Displayed when Gnus has treated overstrike characters in the article buffer.
11160 Displayed when Gnus has treated emphasised strings in the article buffer.
11165 The number of @sc{mime} parts in the article.
11169 @vindex gnus-break-pages
11171 @item gnus-break-pages
11172 Controls whether @dfn{page breaking} is to take place. If this variable
11173 is non-@code{nil}, the articles will be divided into pages whenever a
11174 page delimiter appears in the article. If this variable is @code{nil},
11175 paging will not be done.
11177 @item gnus-page-delimiter
11178 @vindex gnus-page-delimiter
11179 This is the delimiter mentioned above. By default, it is @samp{^L}
11183 @cindex internationalized domain names
11184 @vindex gnus-use-idna
11185 @item gnus-use-idna
11186 This variable controls whether Gnus performs IDNA decoding of
11187 internationalized domain names inside @sc{From:}, @sc{To:} and
11188 @sc{Cc:} headers. This requires GNU Libidn
11189 (@url{http://www.gnu.org/software/libidn/}, and this variable is only
11190 enabled if you have installed it.
11195 @node Composing Messages
11196 @chapter Composing Messages
11197 @cindex composing messages
11200 @cindex sending mail
11205 @cindex using s/mime
11206 @cindex using smime
11208 @kindex C-c C-c (Post)
11209 All commands for posting and mailing will put you in a message buffer
11210 where you can edit the article all you like, before you send the
11211 article by pressing @kbd{C-c C-c}. @xref{Top, , Overview, message,
11212 Message Manual}. Where the message will be posted/mailed to depends
11213 on your setup (@pxref{Posting Server}).
11216 * Mail:: Mailing and replying.
11217 * Posting Server:: What server should you post and mail via?
11218 * Mail and Post:: Mailing and posting at the same time.
11219 * Archived Messages:: Where Gnus stores the messages you've sent.
11220 * Posting Styles:: An easier way to specify who you are.
11221 * Drafts:: Postponing messages and rejected messages.
11222 * Rejected Articles:: What happens if the server doesn't like your article?
11223 * Signing and encrypting:: How to compose secure messages.
11226 Also see @pxref{Canceling and Superseding} for information on how to
11227 remove articles you shouldn't have posted.
11233 Variables for customizing outgoing mail:
11236 @item gnus-uu-digest-headers
11237 @vindex gnus-uu-digest-headers
11238 List of regexps to match headers included in digested messages. The
11239 headers will be included in the sequence they are matched. If
11240 @code{nil} include all headers.
11242 @item gnus-add-to-list
11243 @vindex gnus-add-to-list
11244 If non-@code{nil}, add a @code{to-list} group parameter to mail groups
11245 that have none when you do a @kbd{a}.
11247 @item gnus-confirm-mail-reply-to-news
11248 @vindex gnus-confirm-mail-reply-to-news
11249 This can also be a function receiving the group name as the only
11250 parameter which should return non-@code{nil} if a confirmation is
11251 needed, or a regular expression matching group names, where
11252 confirmation is should be asked for.
11254 If you find yourself never wanting to reply to mail, but occasionally
11255 press R anyway, this variable might be for you.
11257 @item gnus-confirm-treat-mail-like-news
11258 @vindex gnus-confirm-treat-mail-like-news
11259 If non-@code{nil}, Gnus also requests confirmation according to
11260 @code{gnus-confirm-mail-reply-to-news} when replying to mail. This is
11261 useful for treating mailing lists like newsgroups.
11266 @node Posting Server
11267 @section Posting Server
11269 When you press those magical @kbd{C-c C-c} keys to ship off your latest
11270 (extremely intelligent, of course) article, where does it go?
11272 Thank you for asking. I hate you.
11274 It can be quite complicated.
11276 @vindex gnus-post-method
11277 When posting news, Message usually invokes @code{message-send-news}
11278 (@pxref{News Variables, , News Variables, message, Message Manual}).
11279 Normally, Gnus will post using the same select method as you're
11280 reading from (which might be convenient if you're reading lots of
11281 groups from different private servers). However. If the server
11282 you're reading from doesn't allow posting, just reading, you probably
11283 want to use some other server to post your (extremely intelligent and
11284 fabulously interesting) articles. You can then set the
11285 @code{gnus-post-method} to some other method:
11288 (setq gnus-post-method '(nnspool ""))
11291 Now, if you've done this, and then this server rejects your article, or
11292 this server is down, what do you do then? To override this variable you
11293 can use a non-zero prefix to the @kbd{C-c C-c} command to force using
11294 the ``current'' server, to get back the default behavior, for posting.
11296 If you give a zero prefix (i.e., @kbd{C-u 0 C-c C-c}) to that command,
11297 Gnus will prompt you for what method to use for posting.
11299 You can also set @code{gnus-post-method} to a list of select methods.
11300 If that's the case, Gnus will always prompt you for what method to use
11303 Finally, if you want to always post using the native select method,
11304 you can set this variable to @code{native}.
11306 When sending mail, Message invokes @code{message-send-mail-function}.
11307 The default function, @code{message-send-mail-with-sendmail}, pipes
11308 your article to the @code{sendmail} binary for further queuing and
11309 sending. When your local system is not configured for sending mail
11310 using @code{sendmail}, and you have access to a remote @sc{smtp}
11311 server, you can set @code{message-send-mail-function} to
11312 @code{smtpmail-send-it} and make sure to setup the @code{smtpmail}
11313 package correctly. An example:
11316 (setq message-send-mail-function 'smtpmail-send-it
11317 smtpmail-default-smtp-server "YOUR SMTP HOST")
11320 To the thing similar to this, there is @code{message-smtpmail-send-it}.
11321 It is useful if your ISP requires the POP-before-SMTP authentication.
11322 See the documentation for the function @code{mail-source-touch-pop}.
11324 Other possible choices for @code{message-send-mail-function} includes
11325 @code{message-send-mail-with-mh}, @code{message-send-mail-with-qmail},
11326 and @code{feedmail-send-it}.
11328 @node Mail and Post
11329 @section Mail and Post
11331 Here's a list of variables relevant to both mailing and
11335 @item gnus-mailing-list-groups
11336 @findex gnus-mailing-list-groups
11337 @cindex mailing lists
11339 If your news server offers groups that are really mailing lists
11340 gatewayed to the @sc{nntp} server, you can read those groups without
11341 problems, but you can't post/followup to them without some difficulty.
11342 One solution is to add a @code{to-address} to the group parameters
11343 (@pxref{Group Parameters}). An easier thing to do is set the
11344 @code{gnus-mailing-list-groups} to a regexp that matches the groups that
11345 really are mailing lists. Then, at least, followups to the mailing
11346 lists will work most of the time. Posting to these groups (@kbd{a}) is
11347 still a pain, though.
11349 @item gnus-user-agent
11350 @vindex gnus-user-agent
11353 This variable controls which information should be exposed in the
11354 User-Agent header. It can be one of the symbols @code{gnus} (show only
11355 Gnus version), @code{emacs-gnus} (show only Emacs and Gnus versions),
11356 @code{emacs-gnus-config} (same as @code{emacs-gnus} plus system
11357 configuration), @code{emacs-gnus-type} (same as @code{emacs-gnus} plus
11358 system type) or a custom string. If you set it to a string, be sure to
11359 use a valid format, see RFC 2616."
11363 You may want to do spell-checking on messages that you send out. Or, if
11364 you don't want to spell-check by hand, you could add automatic
11365 spell-checking via the @code{ispell} package:
11368 @findex ispell-message
11370 (add-hook 'message-send-hook 'ispell-message)
11373 If you want to change the @code{ispell} dictionary based on what group
11374 you're in, you could say something like the following:
11377 (add-hook 'gnus-select-group-hook
11381 "^de\\." (gnus-group-real-name gnus-newsgroup-name))
11382 (ispell-change-dictionary "deutsch"))
11384 (ispell-change-dictionary "english")))))
11387 Modify to suit your needs.
11390 @node Archived Messages
11391 @section Archived Messages
11392 @cindex archived messages
11393 @cindex sent messages
11395 Gnus provides a few different methods for storing the mail and news you
11396 send. The default method is to use the @dfn{archive virtual server} to
11397 store the messages. If you want to disable this completely, the
11398 @code{gnus-message-archive-group} variable should be @code{nil}, which
11401 For archiving interesting messages in a group you read, see the
11402 @kbd{B c} (@code{gnus-summary-copy-article}) command (@pxref{Mail
11405 @vindex gnus-message-archive-method
11406 @code{gnus-message-archive-method} says what virtual server Gnus is to
11407 use to store sent messages. The default is:
11410 (nnfolder "archive"
11411 (nnfolder-directory "~/Mail/archive")
11412 (nnfolder-active-file "~/Mail/archive/active")
11413 (nnfolder-get-new-mail nil)
11414 (nnfolder-inhibit-expiry t))
11417 You can, however, use any mail select method (@code{nnml},
11418 @code{nnmbox}, etc.). @code{nnfolder} is a quite likable select method
11419 for doing this sort of thing, though. If you don't like the default
11420 directory chosen, you could say something like:
11423 (setq gnus-message-archive-method
11424 '(nnfolder "archive"
11425 (nnfolder-inhibit-expiry t)
11426 (nnfolder-active-file "~/News/sent-mail/active")
11427 (nnfolder-directory "~/News/sent-mail/")))
11430 @vindex gnus-message-archive-group
11432 Gnus will insert @code{Gcc} headers in all outgoing messages that point
11433 to one or more group(s) on that server. Which group to use is
11434 determined by the @code{gnus-message-archive-group} variable.
11436 This variable can be used to do the following:
11441 Messages will be saved in that group.
11443 Note that you can include a select method in the group name, then the
11444 message will not be stored in the select method given by
11445 @code{gnus-message-archive-method}, but in the select method specified
11446 by the group name, instead. Suppose @code{gnus-message-archive-method}
11447 has the default value shown above. Then setting
11448 @code{gnus-message-archive-group} to @code{"foo"} means that outgoing
11449 messages are stored in @samp{nnfolder+archive:foo}, but if you use the
11450 value @code{"nnml:foo"}, then outgoing messages will be stored in
11454 Messages will be saved in all those groups.
11456 an alist of regexps, functions and forms
11457 When a key ``matches'', the result is used.
11460 No message archiving will take place. This is the default.
11465 Just saving to a single group called @samp{MisK}:
11467 (setq gnus-message-archive-group "MisK")
11470 Saving to two groups, @samp{MisK} and @samp{safe}:
11472 (setq gnus-message-archive-group '("MisK" "safe"))
11475 Save to different groups based on what group you are in:
11477 (setq gnus-message-archive-group
11478 '(("^alt" "sent-to-alt")
11479 ("mail" "sent-to-mail")
11480 (".*" "sent-to-misc")))
11483 More complex stuff:
11485 (setq gnus-message-archive-group
11486 '((if (message-news-p)
11491 How about storing all news messages in one file, but storing all mail
11492 messages in one file per month:
11495 (setq gnus-message-archive-group
11496 '((if (message-news-p)
11498 (concat "mail." (format-time-string "%Y-%m")))))
11501 @c (XEmacs 19.13 doesn't have @code{format-time-string}, so you'll have to
11502 @c use a different value for @code{gnus-message-archive-group} there.)
11504 Now, when you send a message off, it will be stored in the appropriate
11505 group. (If you want to disable storing for just one particular message,
11506 you can just remove the @code{Gcc} header that has been inserted.) The
11507 archive group will appear in the group buffer the next time you start
11508 Gnus, or the next time you press @kbd{F} in the group buffer. You can
11509 enter it and read the articles in it just like you'd read any other
11510 group. If the group gets really big and annoying, you can simply rename
11511 if (using @kbd{G r} in the group buffer) to something
11512 nice---@samp{misc-mail-september-1995}, or whatever. New messages will
11513 continue to be stored in the old (now empty) group.
11515 That's the default method of archiving sent messages. Gnus offers a
11516 different way for the people who don't like the default method. In that
11517 case you should set @code{gnus-message-archive-group} to @code{nil};
11518 this will disable archiving.
11521 @item gnus-outgoing-message-group
11522 @vindex gnus-outgoing-message-group
11523 All outgoing messages will be put in this group. If you want to store
11524 all your outgoing mail and articles in the group @samp{nnml:archive},
11525 you set this variable to that value. This variable can also be a list of
11528 If you want to have greater control over what group to put each
11529 message in, you can set this variable to a function that checks the
11530 current newsgroup name and then returns a suitable group name (or list
11533 This variable can be used instead of @code{gnus-message-archive-group},
11534 but the latter is the preferred method.
11536 @item gnus-gcc-mark-as-read
11537 @vindex gnus-gcc-mark-as-read
11538 If non-@code{nil}, automatically mark @code{Gcc} articles as read.
11540 @item gnus-gcc-externalize-attachments
11541 @vindex gnus-gcc-externalize-attachments
11542 If @code{nil}, attach files as normal parts in Gcc copies; if a regexp
11543 and matches the Gcc group name, attach files as external parts; if it is
11544 @code{all}, attach local files as external parts; if it is other
11545 non-@code{nil}, the behavior is the same as @code{all}, but it may be
11546 changed in the future.
11551 @node Posting Styles
11552 @section Posting Styles
11553 @cindex posting styles
11556 All them variables, they make my head swim.
11558 So what if you want a different @code{Organization} and signature based
11559 on what groups you post to? And you post both from your home machine
11560 and your work machine, and you want different @code{From} lines, and so
11563 @vindex gnus-posting-styles
11564 One way to do stuff like that is to write clever hooks that change the
11565 variables you need to have changed. That's a bit boring, so somebody
11566 came up with the bright idea of letting the user specify these things in
11567 a handy alist. Here's an example of a @code{gnus-posting-styles}
11572 (signature "Peace and happiness")
11573 (organization "What me?"))
11575 (signature "Death to everybody"))
11576 ("comp.emacs.i-love-it"
11577 (organization "Emacs is it")))
11580 As you might surmise from this example, this alist consists of several
11581 @dfn{styles}. Each style will be applicable if the first element
11582 ``matches'', in some form or other. The entire alist will be iterated
11583 over, from the beginning towards the end, and each match will be
11584 applied, which means that attributes in later styles that match override
11585 the same attributes in earlier matching styles. So
11586 @samp{comp.programming.literate} will have the @samp{Death to everybody}
11587 signature and the @samp{What me?} @code{Organization} header.
11589 The first element in each style is called the @code{match}. If it's a
11590 string, then Gnus will try to regexp match it against the group name.
11591 If it is the form @code{(header @var{match} @var{regexp})}, then Gnus
11592 will look in the original article for a header whose name is
11593 @var{match} and compare that @var{regexp}. @var{match} and
11594 @var{regexp} are strings. (There original article is the one you are
11595 replying or following up to. If you are not composing a reply or a
11596 followup, then there is nothing to match against.) If the
11597 @code{match} is a function symbol, that function will be called with
11598 no arguments. If it's a variable symbol, then the variable will be
11599 referenced. If it's a list, then that list will be @code{eval}ed. In
11600 any case, if this returns a non-@code{nil} value, then the style is
11601 said to @dfn{match}.
11603 Each style may contain an arbitrary amount of @dfn{attributes}. Each
11604 attribute consists of a @code{(@var{name} @var{value})} pair. The
11605 attribute name can be one of @code{signature}, @code{signature-file},
11606 @code{x-face-file}, @code{address} (overriding
11607 @code{user-mail-address}), @code{name} (overriding
11608 @code{(user-full-name)}) or @code{body}. The attribute name can also
11609 be a string or a symbol. In that case, this will be used as a header
11610 name, and the value will be inserted in the headers of the article; if
11611 the value is @code{nil}, the header name will be removed. If the
11612 attribute name is @code{eval}, the form is evaluated, and the result
11615 The attribute value can be a string (used verbatim), a function with
11616 zero arguments (the return value will be used), a variable (its value
11617 will be used) or a list (it will be @code{eval}ed and the return value
11618 will be used). The functions and sexps are called/@code{eval}ed in the
11619 message buffer that is being set up. The headers of the current article
11620 are available through the @code{message-reply-headers} variable, which
11621 is a vector of the following headers: number subject from date id
11622 references chars lines xref extra.
11624 @vindex message-reply-headers
11626 If you wish to check whether the message you are about to compose is
11627 meant to be a news article or a mail message, you can check the values
11628 of the @code{message-news-p} and @code{message-mail-p} functions.
11630 @findex message-mail-p
11631 @findex message-news-p
11633 So here's a new example:
11636 (setq gnus-posting-styles
11638 (signature-file "~/.signature")
11640 ("X-Home-Page" (getenv "WWW_HOME"))
11641 (organization "People's Front Against MWM"))
11643 (signature my-funny-signature-randomizer))
11644 ((equal (system-name) "gnarly") ;; A form
11645 (signature my-quote-randomizer))
11646 (message-news-p ;; A function symbol
11647 (signature my-news-signature))
11648 (window-system ;; A value symbol
11649 ("X-Window-System" (format "%s" window-system)))
11650 ;; If I'm replying to Larsi, set the Organization header.
11651 ((header "from" "larsi.*org")
11652 (Organization "Somewhere, Inc."))
11653 ((posting-from-work-p) ;; A user defined function
11654 (signature-file "~/.work-signature")
11655 (address "user@@bar.foo")
11656 (body "You are fired.\n\nSincerely, your boss.")
11657 (organization "Important Work, Inc"))
11659 (From (save-excursion
11660 (set-buffer gnus-article-buffer)
11661 (message-fetch-field "to"))))
11663 (signature-file "~/.mail-signature"))))
11666 The @samp{nnml:.*} rule means that you use the @code{To} address as the
11667 @code{From} address in all your outgoing replies, which might be handy
11668 if you fill many roles.
11675 If you are writing a message (mail or news) and suddenly remember that
11676 you have a steak in the oven (or some pesto in the food processor, you
11677 craaazy vegetarians), you'll probably wish there was a method to save
11678 the message you are writing so that you can continue editing it some
11679 other day, and send it when you feel its finished.
11681 Well, don't worry about it. Whenever you start composing a message of
11682 some sort using the Gnus mail and post commands, the buffer you get will
11683 automatically associate to an article in a special @dfn{draft} group.
11684 If you save the buffer the normal way (@kbd{C-x C-s}, for instance), the
11685 article will be saved there. (Auto-save files also go to the draft
11689 @vindex nndraft-directory
11690 The draft group is a special group (which is implemented as an
11691 @code{nndraft} group, if you absolutely have to know) called
11692 @samp{nndraft:drafts}. The variable @code{nndraft-directory} says where
11693 @code{nndraft} is to store its files. What makes this group special is
11694 that you can't tick any articles in it or mark any articles as
11695 read---all articles in the group are permanently unread.
11697 If the group doesn't exist, it will be created and you'll be subscribed
11698 to it. The only way to make it disappear from the Group buffer is to
11699 unsubscribe it. The special properties of the draft group comes from
11700 a group property (@pxref{Group Parameters}), and if lost the group
11701 behaves like any other group. This means the commands below will not
11702 be available. To restore the special properties of the group, the
11703 simplest way is to kill the group, using @kbd{C-k}, and restart
11704 Gnus. The group is automatically created again with the
11705 correct parameters. The content of the group is not lost.
11707 @c @findex gnus-dissociate-buffer-from-draft
11708 @c @kindex C-c M-d (Mail)
11709 @c @kindex C-c M-d (Post)
11710 @c @findex gnus-associate-buffer-with-draft
11711 @c @kindex C-c C-d (Mail)
11712 @c @kindex C-c C-d (Post)
11713 @c If you're writing some super-secret message that you later want to
11714 @c encode with PGP before sending, you may wish to turn the auto-saving
11715 @c (and association with the draft group) off. You never know who might be
11716 @c interested in reading all your extremely valuable and terribly horrible
11717 @c and interesting secrets. The @kbd{C-c M-d}
11718 @c (@code{gnus-dissociate-buffer-from-draft}) command does that for you.
11719 @c If you change your mind and want to turn the auto-saving back on again,
11720 @c @kbd{C-c C-d} (@code{gnus-associate-buffer-with-draft} does that.
11722 @c @vindex gnus-use-draft
11723 @c To leave association with the draft group off by default, set
11724 @c @code{gnus-use-draft} to @code{nil}. It is @code{t} by default.
11726 @findex gnus-draft-edit-message
11727 @kindex D e (Draft)
11728 When you want to continue editing the article, you simply enter the
11729 draft group and push @kbd{D e} (@code{gnus-draft-edit-message}) to do
11730 that. You will be placed in a buffer where you left off.
11732 Rejected articles will also be put in this draft group (@pxref{Rejected
11735 @findex gnus-draft-send-all-messages
11736 @kindex D s (Draft)
11737 @findex gnus-draft-send-message
11738 @kindex D S (Draft)
11739 If you have lots of rejected messages you want to post (or mail) without
11740 doing further editing, you can use the @kbd{D s} command
11741 (@code{gnus-draft-send-message}). This command understands the
11742 process/prefix convention (@pxref{Process/Prefix}). The @kbd{D S}
11743 command (@code{gnus-draft-send-all-messages}) will ship off all messages
11746 @findex gnus-draft-toggle-sending
11747 @kindex D t (Draft)
11748 If you have some messages that you wish not to send, you can use the
11749 @kbd{D t} (@code{gnus-draft-toggle-sending}) command to mark the message
11750 as unsendable. This is a toggling command.
11753 @node Rejected Articles
11754 @section Rejected Articles
11755 @cindex rejected articles
11757 Sometimes a news server will reject an article. Perhaps the server
11758 doesn't like your face. Perhaps it just feels miserable. Perhaps
11759 @emph{there be demons}. Perhaps you have included too much cited text.
11760 Perhaps the disk is full. Perhaps the server is down.
11762 These situations are, of course, totally beyond the control of Gnus.
11763 (Gnus, of course, loves the way you look, always feels great, has angels
11764 fluttering around inside of it, doesn't care about how much cited text
11765 you include, never runs full and never goes down.) So Gnus saves these
11766 articles until some later time when the server feels better.
11768 The rejected articles will automatically be put in a special draft group
11769 (@pxref{Drafts}). When the server comes back up again, you'd then
11770 typically enter that group and send all the articles off.
11772 @node Signing and encrypting
11773 @section Signing and encrypting
11775 @cindex using s/mime
11776 @cindex using smime
11778 Gnus can digitally sign and encrypt your messages, using vanilla PGP
11779 format or @sc{pgp/mime} or @sc{s/mime}. For decoding such messages,
11780 see the @code{mm-verify-option} and @code{mm-decrypt-option} options
11781 (@pxref{Security}).
11783 @vindex gnus-message-replysign
11784 @vindex gnus-message-replyencrypt
11785 @vindex gnus-message-replysignencrypted
11786 Often, you would like to sign replies to people who send you signed
11787 messages. Even more often, you might want to encrypt messages which
11788 are in reply to encrypted messages. Gnus offers
11789 @code{gnus-message-replysign} to enable the former, and
11790 @code{gnus-message-replyencrypt} for the latter. In addition, setting
11791 @code{gnus-message-replysignencrypted} (on by default) will sign
11792 automatically encrypted messages.
11794 Instructing MML to perform security operations on a @sc{mime} part is
11795 done using the @kbd{C-c C-m s} key map for signing and the @kbd{C-c
11796 C-m c} key map for encryption, as follows.
11801 @kindex C-c C-m s s
11802 @findex mml-secure-message-sign-smime
11804 Digitally sign current message using @sc{s/mime}.
11807 @kindex C-c C-m s o
11808 @findex mml-secure-message-sign-pgp
11810 Digitally sign current message using PGP.
11813 @kindex C-c C-m s p
11814 @findex mml-secure-message-sign-pgp
11816 Digitally sign current message using @sc{pgp/mime}.
11819 @kindex C-c C-m c s
11820 @findex mml-secure-message-encrypt-smime
11822 Digitally encrypt current message using @sc{s/mime}.
11825 @kindex C-c C-m c o
11826 @findex mml-secure-message-encrypt-pgp
11828 Digitally encrypt current message using PGP.
11831 @kindex C-c C-m c p
11832 @findex mml-secure-message-encrypt-pgpmime
11834 Digitally encrypt current message using @sc{pgp/mime}.
11837 @kindex C-c C-m C-n
11838 @findex mml-unsecure-message
11839 Remove security related MML tags from message.
11843 @xref{Security, ,Security, message, Message Manual}, for more information.
11845 @node Select Methods
11846 @chapter Select Methods
11847 @cindex foreign groups
11848 @cindex select methods
11850 A @dfn{foreign group} is a group not read by the usual (or
11851 default) means. It could be, for instance, a group from a different
11852 @sc{nntp} server, it could be a virtual group, or it could be your own
11853 personal mail group.
11855 A foreign group (or any group, really) is specified by a @dfn{name} and
11856 a @dfn{select method}. To take the latter first, a select method is a
11857 list where the first element says what back end to use (e.g. @code{nntp},
11858 @code{nnspool}, @code{nnml}) and the second element is the @dfn{server
11859 name}. There may be additional elements in the select method, where the
11860 value may have special meaning for the back end in question.
11862 One could say that a select method defines a @dfn{virtual server}---so
11863 we do just that (@pxref{Server Buffer}).
11865 The @dfn{name} of the group is the name the back end will recognize the
11868 For instance, the group @samp{soc.motss} on the @sc{nntp} server
11869 @samp{some.where.edu} will have the name @samp{soc.motss} and select
11870 method @code{(nntp "some.where.edu")}. Gnus will call this group
11871 @samp{nntp+some.where.edu:soc.motss}, even though the @code{nntp}
11872 back end just knows this group as @samp{soc.motss}.
11874 The different methods all have their peculiarities, of course.
11877 * Server Buffer:: Making and editing virtual servers.
11878 * Getting News:: Reading USENET news with Gnus.
11879 * Getting Mail:: Reading your personal mail with Gnus.
11880 * Browsing the Web:: Getting messages from a plethora of Web sources.
11881 * IMAP:: Using Gnus as a @sc{imap} client.
11882 * Other Sources:: Reading directories, files, SOUP packets.
11883 * Combined Groups:: Combining groups into one group.
11884 * Gnus Unplugged:: Reading news and mail offline.
11888 @node Server Buffer
11889 @section Server Buffer
11891 Traditionally, a @dfn{server} is a machine or a piece of software that
11892 one connects to, and then requests information from. Gnus does not
11893 connect directly to any real servers, but does all transactions through
11894 one back end or other. But that's just putting one layer more between
11895 the actual media and Gnus, so we might just as well say that each
11896 back end represents a virtual server.
11898 For instance, the @code{nntp} back end may be used to connect to several
11899 different actual @sc{nntp} servers, or, perhaps, to many different ports
11900 on the same actual @sc{nntp} server. You tell Gnus which back end to
11901 use, and what parameters to set by specifying a @dfn{select method}.
11903 These select method specifications can sometimes become quite
11904 complicated---say, for instance, that you want to read from the
11905 @sc{nntp} server @samp{news.funet.fi} on port number 13, which
11906 hangs if queried for @sc{nov} headers and has a buggy select. Ahem.
11907 Anyway, if you had to specify that for each group that used this
11908 server, that would be too much work, so Gnus offers a way of naming
11909 select methods, which is what you do in the server buffer.
11911 To enter the server buffer, use the @kbd{^}
11912 (@code{gnus-group-enter-server-mode}) command in the group buffer.
11915 * Server Buffer Format:: You can customize the look of this buffer.
11916 * Server Commands:: Commands to manipulate servers.
11917 * Example Methods:: Examples server specifications.
11918 * Creating a Virtual Server:: An example session.
11919 * Server Variables:: Which variables to set.
11920 * Servers and Methods:: You can use server names as select methods.
11921 * Unavailable Servers:: Some servers you try to contact may be down.
11924 @vindex gnus-server-mode-hook
11925 @code{gnus-server-mode-hook} is run when creating the server buffer.
11928 @node Server Buffer Format
11929 @subsection Server Buffer Format
11930 @cindex server buffer format
11932 @vindex gnus-server-line-format
11933 You can change the look of the server buffer lines by changing the
11934 @code{gnus-server-line-format} variable. This is a @code{format}-like
11935 variable, with some simple extensions:
11940 How the news is fetched---the back end name.
11943 The name of this server.
11946 Where the news is to be fetched from---the address.
11949 The opened/closed/denied status of the server.
11952 @vindex gnus-server-mode-line-format
11953 The mode line can also be customized by using the
11954 @code{gnus-server-mode-line-format} variable (@pxref{Mode Line
11955 Formatting}). The following specs are understood:
11965 Also @pxref{Formatting Variables}.
11968 @node Server Commands
11969 @subsection Server Commands
11970 @cindex server commands
11976 @findex gnus-server-add-server
11977 Add a new server (@code{gnus-server-add-server}).
11981 @findex gnus-server-edit-server
11982 Edit a server (@code{gnus-server-edit-server}).
11985 @kindex SPACE (Server)
11986 @findex gnus-server-read-server
11987 Browse the current server (@code{gnus-server-read-server}).
11991 @findex gnus-server-exit
11992 Return to the group buffer (@code{gnus-server-exit}).
11996 @findex gnus-server-kill-server
11997 Kill the current server (@code{gnus-server-kill-server}).
12001 @findex gnus-server-yank-server
12002 Yank the previously killed server (@code{gnus-server-yank-server}).
12006 @findex gnus-server-copy-server
12007 Copy the current server (@code{gnus-server-copy-server}).
12011 @findex gnus-server-list-servers
12012 List all servers (@code{gnus-server-list-servers}).
12016 @findex gnus-server-scan-server
12017 Request that the server scan its sources for new articles
12018 (@code{gnus-server-scan-server}). This is mainly sensible with mail
12023 @findex gnus-server-regenerate-server
12024 Request that the server regenerate all its data structures
12025 (@code{gnus-server-regenerate-server}). This can be useful if you have
12026 a mail back end that has gotten out of sync.
12031 @node Example Methods
12032 @subsection Example Methods
12034 Most select methods are pretty simple and self-explanatory:
12037 (nntp "news.funet.fi")
12040 Reading directly from the spool is even simpler:
12046 As you can see, the first element in a select method is the name of the
12047 back end, and the second is the @dfn{address}, or @dfn{name}, if you
12050 After these two elements, there may be an arbitrary number of
12051 @code{(@var{variable} @var{form})} pairs.
12053 To go back to the first example---imagine that you want to read from
12054 port 15 on that machine. This is what the select method should
12058 (nntp "news.funet.fi" (nntp-port-number 15))
12061 You should read the documentation to each back end to find out what
12062 variables are relevant, but here's an @code{nnmh} example:
12064 @code{nnmh} is a mail back end that reads a spool-like structure. Say
12065 you have two structures that you wish to access: One is your private
12066 mail spool, and the other is a public one. Here's the possible spec for
12070 (nnmh "private" (nnmh-directory "~/private/mail/"))
12073 (This server is then called @samp{private}, but you may have guessed
12076 Here's the method for a public spool:
12080 (nnmh-directory "/usr/information/spool/")
12081 (nnmh-get-new-mail nil))
12087 If you are behind a firewall and only have access to the @sc{nntp}
12088 server from the firewall machine, you can instruct Gnus to @code{rlogin}
12089 on the firewall machine and telnet from there to the @sc{nntp} server.
12090 Doing this can be rather fiddly, but your virtual server definition
12091 should probably look something like this:
12095 (nntp-open-connection-function nntp-open-via-rlogin-and-telnet)
12096 (nntp-via-address "the.firewall.machine")
12097 (nntp-address "the.real.nntp.host")
12098 (nntp-end-of-line "\n"))
12101 If you want to use the wonderful @code{ssh} program to provide a
12102 compressed connection over the modem line, you could add the following
12103 configuration to the example above:
12106 (nntp-via-rlogin-command "ssh")
12109 See also @code{nntp-via-rlogin-command-switches}.
12111 If you're behind a firewall, but have direct access to the outside world
12112 through a wrapper command like "runsocks", you could open a socksified
12113 telnet connection to the news server as follows:
12117 (nntp-pre-command "runsocks")
12118 (nntp-open-connection-function nntp-open-via-telnet)
12119 (nntp-address "the.news.server")
12120 (nntp-end-of-line "\n"))
12123 This means that you have to have set up @code{ssh-agent} correctly to
12124 provide automatic authorization, of course. And to get a compressed
12125 connection, you have to have the @samp{Compression} option in the
12126 @code{ssh} @file{config} file.
12129 @node Creating a Virtual Server
12130 @subsection Creating a Virtual Server
12132 If you're saving lots of articles in the cache by using persistent
12133 articles, you may want to create a virtual server to read the cache.
12135 First you need to add a new server. The @kbd{a} command does that. It
12136 would probably be best to use @code{nnspool} to read the cache. You
12137 could also use @code{nnml} or @code{nnmh}, though.
12139 Type @kbd{a nnspool RET cache RET}.
12141 You should now have a brand new @code{nnspool} virtual server called
12142 @samp{cache}. You now need to edit it to have the right definitions.
12143 Type @kbd{e} to edit the server. You'll be entered into a buffer that
12144 will contain the following:
12154 (nnspool-spool-directory "~/News/cache/")
12155 (nnspool-nov-directory "~/News/cache/")
12156 (nnspool-active-file "~/News/cache/active"))
12159 Type @kbd{C-c C-c} to return to the server buffer. If you now press
12160 @kbd{RET} over this virtual server, you should be entered into a browse
12161 buffer, and you should be able to enter any of the groups displayed.
12164 @node Server Variables
12165 @subsection Server Variables
12167 One sticky point when defining variables (both on back ends and in Emacs
12168 in general) is that some variables are typically initialized from other
12169 variables when the definition of the variables is being loaded. If you
12170 change the ``base'' variable after the variables have been loaded, you
12171 won't change the ``derived'' variables.
12173 This typically affects directory and file variables. For instance,
12174 @code{nnml-directory} is @file{~/Mail/} by default, and all @code{nnml}
12175 directory variables are initialized from that variable, so
12176 @code{nnml-active-file} will be @file{~/Mail/active}. If you define a
12177 new virtual @code{nnml} server, it will @emph{not} suffice to set just
12178 @code{nnml-directory}---you have to explicitly set all the file
12179 variables to be what you want them to be. For a complete list of
12180 variables for each back end, see each back end's section later in this
12181 manual, but here's an example @code{nnml} definition:
12185 (nnml-directory "~/my-mail/")
12186 (nnml-active-file "~/my-mail/active")
12187 (nnml-newsgroups-file "~/my-mail/newsgroups"))
12191 @node Servers and Methods
12192 @subsection Servers and Methods
12194 Wherever you would normally use a select method
12195 (e.g. @code{gnus-secondary-select-method}, in the group select method,
12196 when browsing a foreign server) you can use a virtual server name
12197 instead. This could potentially save lots of typing. And it's nice all
12201 @node Unavailable Servers
12202 @subsection Unavailable Servers
12204 If a server seems to be unreachable, Gnus will mark that server as
12205 @code{denied}. That means that any subsequent attempt to make contact
12206 with that server will just be ignored. ``It can't be opened,'' Gnus
12207 will tell you, without making the least effort to see whether that is
12208 actually the case or not.
12210 That might seem quite naughty, but it does make sense most of the time.
12211 Let's say you have 10 groups subscribed to on server
12212 @samp{nephelococcygia.com}. This server is located somewhere quite far
12213 away from you and the machine is quite slow, so it takes 1 minute just
12214 to find out that it refuses connection to you today. If Gnus were to
12215 attempt to do that 10 times, you'd be quite annoyed, so Gnus won't
12216 attempt to do that. Once it has gotten a single ``connection refused'',
12217 it will regard that server as ``down''.
12219 So, what happens if the machine was only feeling unwell temporarily?
12220 How do you test to see whether the machine has come up again?
12222 You jump to the server buffer (@pxref{Server Buffer}) and poke it
12223 with the following commands:
12229 @findex gnus-server-open-server
12230 Try to establish connection to the server on the current line
12231 (@code{gnus-server-open-server}).
12235 @findex gnus-server-close-server
12236 Close the connection (if any) to the server
12237 (@code{gnus-server-close-server}).
12241 @findex gnus-server-deny-server
12242 Mark the current server as unreachable
12243 (@code{gnus-server-deny-server}).
12246 @kindex M-o (Server)
12247 @findex gnus-server-open-all-servers
12248 Open the connections to all servers in the buffer
12249 (@code{gnus-server-open-all-servers}).
12252 @kindex M-c (Server)
12253 @findex gnus-server-close-all-servers
12254 Close the connections to all servers in the buffer
12255 (@code{gnus-server-close-all-servers}).
12259 @findex gnus-server-remove-denials
12260 Remove all marks to whether Gnus was denied connection from any servers
12261 (@code{gnus-server-remove-denials}).
12265 @findex gnus-server-offline-server
12266 Set server status to offline (@code{gnus-server-offline-server}).
12272 @section Getting News
12273 @cindex reading news
12274 @cindex news back ends
12276 A newsreader is normally used for reading news. Gnus currently provides
12277 only two methods of getting news---it can read from an @sc{nntp} server,
12278 or it can read from a local spool.
12281 * NNTP:: Reading news from an @sc{nntp} server.
12282 * News Spool:: Reading news from the local spool.
12290 Subscribing to a foreign group from an @sc{nntp} server is rather easy.
12291 You just specify @code{nntp} as method and the address of the @sc{nntp}
12292 server as the, uhm, address.
12294 If the @sc{nntp} server is located at a non-standard port, setting the
12295 third element of the select method to this port number should allow you
12296 to connect to the right port. You'll have to edit the group info for
12297 that (@pxref{Foreign Groups}).
12299 The name of the foreign group can be the same as a native group. In
12300 fact, you can subscribe to the same group from as many different servers
12301 you feel like. There will be no name collisions.
12303 The following variables can be used to create a virtual @code{nntp}
12308 @item nntp-server-opened-hook
12309 @vindex nntp-server-opened-hook
12310 @cindex @sc{mode reader}
12312 @cindex authentification
12313 @cindex nntp authentification
12314 @findex nntp-send-authinfo
12315 @findex nntp-send-mode-reader
12316 is run after a connection has been made. It can be used to send
12317 commands to the @sc{nntp} server after it has been contacted. By
12318 default it sends the command @code{MODE READER} to the server with the
12319 @code{nntp-send-mode-reader} function. This function should always be
12320 present in this hook.
12322 @item nntp-authinfo-function
12323 @vindex nntp-authinfo-function
12324 @findex nntp-send-authinfo
12325 @vindex nntp-authinfo-file
12326 This function will be used to send @samp{AUTHINFO} to the @sc{nntp}
12327 server. The default function is @code{nntp-send-authinfo}, which looks
12328 through your @file{~/.authinfo} (or whatever you've set the
12329 @code{nntp-authinfo-file} variable to) for applicable entries. If none
12330 are found, it will prompt you for a login name and a password. The
12331 format of the @file{~/.authinfo} file is (almost) the same as the
12332 @code{ftp} @file{~/.netrc} file, which is defined in the @code{ftp}
12333 manual page, but here are the salient facts:
12337 The file contains one or more line, each of which define one server.
12340 Each line may contain an arbitrary number of token/value pairs.
12342 The valid tokens include @samp{machine}, @samp{login}, @samp{password},
12343 @samp{default}. In addition Gnus introduces two new tokens, not present
12344 in the original @file{.netrc}/@code{ftp} syntax, namely @samp{port} and
12345 @samp{force}. (This is the only way the @file{.authinfo} file format
12346 deviates from the @file{.netrc} file format.) @samp{port} is used to
12347 indicate what port on the server the credentials apply to and
12348 @samp{force} is explained below.
12352 Here's an example file:
12355 machine news.uio.no login larsi password geheimnis
12356 machine nntp.ifi.uio.no login larsi force yes
12359 The token/value pairs may appear in any order; @samp{machine} doesn't
12360 have to be first, for instance.
12362 In this example, both login name and password have been supplied for the
12363 former server, while the latter has only the login name listed, and the
12364 user will be prompted for the password. The latter also has the
12365 @samp{force} tag, which means that the authinfo will be sent to the
12366 @var{nntp} server upon connection; the default (i.e., when there is not
12367 @samp{force} tag) is to not send authinfo to the @var{nntp} server
12368 until the @var{nntp} server asks for it.
12370 You can also add @samp{default} lines that will apply to all servers
12371 that don't have matching @samp{machine} lines.
12377 This will force sending @samp{AUTHINFO} commands to all servers not
12378 previously mentioned.
12380 Remember to not leave the @file{~/.authinfo} file world-readable.
12382 @item nntp-server-action-alist
12383 @vindex nntp-server-action-alist
12384 This is a list of regexps to match on server types and actions to be
12385 taken when matches are made. For instance, if you want Gnus to beep
12386 every time you connect to innd, you could say something like:
12389 (setq nntp-server-action-alist
12390 '(("innd" (ding))))
12393 You probably don't want to do that, though.
12395 The default value is
12398 '(("nntpd 1\\.5\\.11t"
12399 (remove-hook 'nntp-server-opened-hook
12400 'nntp-send-mode-reader)))
12403 This ensures that Gnus doesn't send the @code{MODE READER} command to
12404 nntpd 1.5.11t, since that command chokes that server, I've been told.
12406 @item nntp-maximum-request
12407 @vindex nntp-maximum-request
12408 If the @sc{nntp} server doesn't support @sc{nov} headers, this back end
12409 will collect headers by sending a series of @code{head} commands. To
12410 speed things up, the back end sends lots of these commands without
12411 waiting for reply, and then reads all the replies. This is controlled
12412 by the @code{nntp-maximum-request} variable, and is 400 by default. If
12413 your network is buggy, you should set this to 1.
12415 @item nntp-connection-timeout
12416 @vindex nntp-connection-timeout
12417 If you have lots of foreign @code{nntp} groups that you connect to
12418 regularly, you're sure to have problems with @sc{nntp} servers not
12419 responding properly, or being too loaded to reply within reasonable
12420 time. This is can lead to awkward problems, which can be helped
12421 somewhat by setting @code{nntp-connection-timeout}. This is an integer
12422 that says how many seconds the @code{nntp} back end should wait for a
12423 connection before giving up. If it is @code{nil}, which is the default,
12424 no timeouts are done.
12426 @c @item nntp-command-timeout
12427 @c @vindex nntp-command-timeout
12428 @c @cindex PPP connections
12429 @c @cindex dynamic IP addresses
12430 @c If you're running Gnus on a machine that has a dynamically assigned
12431 @c address, Gnus may become confused. If the address of your machine
12432 @c changes after connecting to the @sc{nntp} server, Gnus will simply sit
12433 @c waiting forever for replies from the server. To help with this
12434 @c unfortunate problem, you can set this command to a number. Gnus will
12435 @c then, if it sits waiting for a reply from the server longer than that
12436 @c number of seconds, shut down the connection, start a new one, and resend
12437 @c the command. This should hopefully be transparent to the user. A
12438 @c likely number is 30 seconds.
12440 @c @item nntp-retry-on-break
12441 @c @vindex nntp-retry-on-break
12442 @c If this variable is non-@code{nil}, you can also @kbd{C-g} if Gnus
12443 @c hangs. This will have much the same effect as the command timeout
12444 @c described above.
12446 @item nntp-server-hook
12447 @vindex nntp-server-hook
12448 This hook is run as the last step when connecting to an @sc{nntp}
12451 @item nntp-buggy-select
12452 @vindex nntp-buggy-select
12453 Set this to non-@code{nil} if your select routine is buggy.
12455 @item nntp-nov-is-evil
12456 @vindex nntp-nov-is-evil
12457 If the @sc{nntp} server does not support @sc{nov}, you could set this
12458 variable to @code{t}, but @code{nntp} usually checks automatically whether @sc{nov}
12461 @item nntp-xover-commands
12462 @vindex nntp-xover-commands
12465 List of strings used as commands to fetch @sc{nov} lines from a
12466 server. The default value of this variable is @code{("XOVER"
12470 @vindex nntp-nov-gap
12471 @code{nntp} normally sends just one big request for @sc{nov} lines to
12472 the server. The server responds with one huge list of lines. However,
12473 if you have read articles 2-5000 in the group, and only want to read
12474 article 1 and 5001, that means that @code{nntp} will fetch 4999 @sc{nov}
12475 lines that you will not need. This variable says how
12476 big a gap between two consecutive articles is allowed to be before the
12477 @code{XOVER} request is split into several request. Note that if your
12478 network is fast, setting this variable to a really small number means
12479 that fetching will probably be slower. If this variable is @code{nil},
12480 @code{nntp} will never split requests. The default is 5.
12482 @item nntp-prepare-server-hook
12483 @vindex nntp-prepare-server-hook
12484 A hook run before attempting to connect to an @sc{nntp} server.
12486 @item nntp-warn-about-losing-connection
12487 @vindex nntp-warn-about-losing-connection
12488 If this variable is non-@code{nil}, some noise will be made when a
12489 server closes connection.
12491 @item nntp-record-commands
12492 @vindex nntp-record-commands
12493 If non-@code{nil}, @code{nntp} will log all commands it sends to the
12494 @sc{nntp} server (along with a timestamp) in the @samp{*nntp-log*}
12495 buffer. This is useful if you are debugging a Gnus/@sc{nntp} connection
12496 that doesn't seem to work.
12498 @item nntp-open-connection-function
12499 @vindex nntp-open-connection-function
12500 It is possible to customize how the connection to the nntp server will
12501 be opened. If you specify an @code{nntp-open-connection-function}
12502 parameter, Gnus will use that function to establish the connection.
12503 Five pre-made functions are supplied. These functions can be grouped in
12504 two categories: direct connection functions (three pre-made), and
12505 indirect ones (two pre-made).
12507 @item nntp-prepare-post-hook
12508 @vindex nntp-prepare-post-hook
12509 A hook run just before posting an article. If there is no
12510 @code{Message-ID} header in the article and the news server provides the
12511 recommended ID, it will be added to the article before running this
12512 hook. It is useful to make @code{Cancel-Lock} headers even if you
12513 inhibit Gnus to add a @code{Message-ID} header, you could say:
12516 (add-hook 'nntp-prepare-post-hook 'canlock-insert-header)
12519 Note that not all servers support the recommended ID. This works for
12520 INN versions 2.3.0 and later, for instance.
12522 @item nntp-read-timeout
12523 @vindex nntp-read-timeout
12524 How long nntp should wait between checking for the end of output.
12525 Shorter values mean quicker response, but is more CPU intensive. The
12526 default is 0.1 seconds. If you have a slow line to the server (and
12527 don't like to see Emacs eat your available CPU power), you might set
12533 * Direct Functions:: Connecting directly to the server.
12534 * Indirect Functions:: Connecting indirectly to the server.
12535 * Common Variables:: Understood by several connection functions.
12539 @node Direct Functions
12540 @subsubsection Direct Functions
12541 @cindex direct connection functions
12543 These functions are called direct because they open a direct connection
12544 between your machine and the @sc{nntp} server. The behavior of these
12545 functions is also affected by commonly understood variables
12546 (@pxref{Common Variables}).
12549 @findex nntp-open-network-stream
12550 @item nntp-open-network-stream
12551 This is the default, and simply connects to some port or other on the
12554 @findex nntp-open-tls-stream
12555 @item nntp-open-tls-stream
12556 Opens a connection to a server over a @dfn{secure} channel. To use
12557 this you must have GNUTLS installed (see
12558 @uref{http://www.gnu.org/software/gnutls/}). You then define a server
12562 ;; "nntps" is port 563 and is predefined in our /etc/services
12563 ;; however, gnutls-cli -p doesn't like named ports.
12565 (nntp "snews.bar.com"
12566 (nntp-open-connection-function nntp-open-tls-stream)
12567 (nntp-port-number )
12568 (nntp-address "snews.bar.com"))
12571 @findex nntp-open-ssl-stream
12572 @item nntp-open-ssl-stream
12573 Opens a connection to a server over a @dfn{secure} channel. To use this
12574 you must have OpenSSL (@uref{http://www.openssl.org}) or SSLeay
12575 installed (@uref{ftp://ftp.psy.uq.oz.au/pub/Crypto/SSL}. You then
12576 define a server as follows:
12579 ;; "snews" is port 563 and is predefined in our /etc/services
12580 ;; however, openssl s_client -port doesn't like named ports.
12582 (nntp "snews.bar.com"
12583 (nntp-open-connection-function nntp-open-ssl-stream)
12584 (nntp-port-number 563)
12585 (nntp-address "snews.bar.com"))
12588 @findex nntp-open-telnet-stream
12589 @item nntp-open-telnet-stream
12590 Opens a connection to an @sc{nntp} server by simply @samp{telnet}'ing
12591 it. You might wonder why this function exists, since we have the
12592 default @code{nntp-open-network-stream} which would do the job. (One
12593 of) the reason(s) is that if you are behind a firewall but have direct
12594 connections to the outside world thanks to a command wrapper like
12595 @code{runsocks}, you can use it like this:
12599 (nntp-pre-command "runsocks")
12600 (nntp-open-connection-function nntp-open-telnet-stream)
12601 (nntp-address "the.news.server"))
12604 With the default method, you would need to wrap your whole Emacs
12605 session, which is not a good idea.
12609 @node Indirect Functions
12610 @subsubsection Indirect Functions
12611 @cindex indirect connection functions
12613 These functions are called indirect because they connect to an
12614 intermediate host before actually connecting to the @sc{nntp} server.
12615 All of these functions and related variables are also said to belong to
12616 the ``via'' family of connection: they're all prefixed with ``via'' to make
12617 things cleaner. The behavior of these functions is also affected by
12618 commonly understood variables (@pxref{Common Variables}).
12621 @item nntp-open-via-rlogin-and-telnet
12622 @findex nntp-open-via-rlogin-and-telnet
12623 Does an @samp{rlogin} on a remote system, and then does a @samp{telnet}
12624 to the real @sc{nntp} server from there. This is useful for instance if
12625 you need to connect to a firewall machine first.
12627 @code{nntp-open-via-rlogin-and-telnet}-specific variables:
12630 @item nntp-via-rlogin-command
12631 @vindex nntp-via-rlogin-command
12632 Command used to log in on the intermediate host. The default is
12633 @samp{rsh}, but @samp{ssh} is a popular alternative.
12635 @item nntp-via-rlogin-command-switches
12636 @vindex nntp-via-rlogin-command-switches
12637 List of strings to be used as the switches to
12638 @code{nntp-via-rlogin-command}. The default is @code{nil}. If you use
12639 @samp{ssh} for @code{nntp-via-rlogin-command}, you may set this to
12640 @samp{("-C")} in order to compress all data connections, otherwise set
12641 this to @samp{("-t" "-e" "none")} or @samp{("-C" "-t" "-e" "none")} if
12642 the telnet command requires a pseudo-tty allocation on an intermediate
12646 @item nntp-open-via-telnet-and-telnet
12647 @findex nntp-open-via-telnet-and-telnet
12648 Does essentially the same, but uses @samp{telnet} instead of
12649 @samp{rlogin} to connect to the intermediate host.
12651 @code{nntp-open-via-telnet-and-telnet}-specific variables:
12654 @item nntp-via-telnet-command
12655 @vindex nntp-via-telnet-command
12656 Command used to @code{telnet} the intermediate host. The default is
12659 @item nntp-via-telnet-switches
12660 @vindex nntp-via-telnet-switches
12661 List of strings to be used as the switches to the
12662 @code{nntp-via-telnet-command} command. The default is @samp{("-8")}.
12664 @item nntp-via-user-password
12665 @vindex nntp-via-user-password
12666 Password to use when logging in on the intermediate host.
12668 @item nntp-via-envuser
12669 @vindex nntp-via-envuser
12670 If non-@code{nil}, the intermediate @code{telnet} session (client and
12671 server both) will support the @code{ENVIRON} option and not prompt for
12672 login name. This works for Solaris @code{telnet}, for instance.
12674 @item nntp-via-shell-prompt
12675 @vindex nntp-via-shell-prompt
12676 Regexp matching the shell prompt on the intermediate host. The default
12677 is @samp{bash\\|\$ *\r?$\\|> *\r?}.
12684 Here are some additional variables that are understood by all the above
12689 @item nntp-via-user-name
12690 @vindex nntp-via-user-name
12691 User name to use when connecting to the intermediate host.
12693 @item nntp-via-address
12694 @vindex nntp-via-address
12695 Address of the intermediate host to connect to.
12700 @node Common Variables
12701 @subsubsection Common Variables
12703 The following variables affect the behavior of all, or several of the
12704 pre-made connection functions. When not specified, all functions are
12709 @item nntp-pre-command
12710 @vindex nntp-pre-command
12711 A command wrapper to use when connecting through a non native
12712 connection function (all except @code{nntp-open-network-stream},
12713 @code{nntp-open-tls-stream}, and @code{nntp-open-ssl-stream}. This is
12714 where you would put a @samp{SOCKS} wrapper for instance.
12717 @vindex nntp-address
12718 The address of the @sc{nntp} server.
12720 @item nntp-port-number
12721 @vindex nntp-port-number
12722 Port number to connect to the @sc{nntp} server. The default is
12723 @samp{nntp}. If you use @sc{nntp} over @sc{tls}/@sc{ssl}, you may
12724 want to use integer ports rather than named ports (i.e, use @samp{563}
12725 instead of @samp{snews} or @samp{nntps}), because external TLS/SSL
12726 tools may not work with named ports.
12728 @item nntp-end-of-line
12729 @vindex nntp-end-of-line
12730 String to use as end-of-line marker when talking to the @sc{nntp}
12731 server. This is @samp{\r\n} by default, but should be @samp{\n} when
12732 using a non native connection function.
12734 @item nntp-telnet-command
12735 @vindex nntp-telnet-command
12736 Command to use when connecting to the @sc{nntp} server through
12737 @samp{telnet}. This is NOT for an intermediate host. This is just for
12738 the real @sc{nntp} server. The default is @samp{telnet}.
12740 @item nntp-telnet-switches
12741 @vindex nntp-telnet-switches
12742 A list of switches to pass to @code{nntp-telnet-command}. The default
12749 @subsection News Spool
12753 Subscribing to a foreign group from the local spool is extremely easy,
12754 and might be useful, for instance, to speed up reading groups that
12755 contain very big articles---@samp{alt.binaries.pictures.furniture}, for
12758 Anyway, you just specify @code{nnspool} as the method and @code{""} (or
12759 anything else) as the address.
12761 If you have access to a local spool, you should probably use that as the
12762 native select method (@pxref{Finding the News}). It is normally faster
12763 than using an @code{nntp} select method, but might not be. It depends.
12764 You just have to try to find out what's best at your site.
12768 @item nnspool-inews-program
12769 @vindex nnspool-inews-program
12770 Program used to post an article.
12772 @item nnspool-inews-switches
12773 @vindex nnspool-inews-switches
12774 Parameters given to the inews program when posting an article.
12776 @item nnspool-spool-directory
12777 @vindex nnspool-spool-directory
12778 Where @code{nnspool} looks for the articles. This is normally
12779 @file{/usr/spool/news/}.
12781 @item nnspool-nov-directory
12782 @vindex nnspool-nov-directory
12783 Where @code{nnspool} will look for @sc{nov} files. This is normally
12784 @file{/usr/spool/news/over.view/}.
12786 @item nnspool-lib-dir
12787 @vindex nnspool-lib-dir
12788 Where the news lib dir is (@file{/usr/lib/news/} by default).
12790 @item nnspool-active-file
12791 @vindex nnspool-active-file
12792 The name of the active file.
12794 @item nnspool-newsgroups-file
12795 @vindex nnspool-newsgroups-file
12796 The name of the group descriptions file.
12798 @item nnspool-history-file
12799 @vindex nnspool-history-file
12800 The name of the news history file.
12802 @item nnspool-active-times-file
12803 @vindex nnspool-active-times-file
12804 The name of the active date file.
12806 @item nnspool-nov-is-evil
12807 @vindex nnspool-nov-is-evil
12808 If non-@code{nil}, @code{nnspool} won't try to use any @sc{nov} files
12811 @item nnspool-sift-nov-with-sed
12812 @vindex nnspool-sift-nov-with-sed
12814 If non-@code{nil}, which is the default, use @code{sed} to get the
12815 relevant portion from the overview file. If nil, @code{nnspool} will
12816 load the entire file into a buffer and process it there.
12822 @section Getting Mail
12823 @cindex reading mail
12826 Reading mail with a newsreader---isn't that just plain WeIrD? But of
12830 * Mail in a Newsreader:: Important introductory notes.
12831 * Getting Started Reading Mail:: A simple cookbook example.
12832 * Splitting Mail:: How to create mail groups.
12833 * Mail Sources:: How to tell Gnus where to get mail from.
12834 * Mail Back End Variables:: Variables for customizing mail handling.
12835 * Fancy Mail Splitting:: Gnus can do hairy splitting of incoming mail.
12836 * Group Mail Splitting:: Use group customize to drive mail splitting.
12837 * Incorporating Old Mail:: What about the old mail you have?
12838 * Expiring Mail:: Getting rid of unwanted mail.
12839 * Washing Mail:: Removing gruft from the mail you get.
12840 * Duplicates:: Dealing with duplicated mail.
12841 * Not Reading Mail:: Using mail back ends for reading other files.
12842 * Choosing a Mail Back End:: Gnus can read a variety of mail formats.
12846 @node Mail in a Newsreader
12847 @subsection Mail in a Newsreader
12849 If you are used to traditional mail readers, but have decided to switch
12850 to reading mail with Gnus, you may find yourself experiencing something
12851 of a culture shock.
12853 Gnus does not behave like traditional mail readers. If you want to make
12854 it behave that way, you can, but it's an uphill battle.
12856 Gnus, by default, handles all its groups using the same approach. This
12857 approach is very newsreaderly---you enter a group, see the new/unread
12858 messages, and when you read the messages, they get marked as read, and
12859 you don't see them any more. (Unless you explicitly ask for them.)
12861 In particular, you do not do anything explicitly to delete messages.
12863 Does this mean that all the messages that have been marked as read are
12864 deleted? How awful!
12866 But, no, it means that old messages are @dfn{expired} according to some
12867 scheme or other. For news messages, the expire process is controlled by
12868 the news administrator; for mail, the expire process is controlled by
12869 you. The expire process for mail is covered in depth in @pxref{Expiring
12872 What many Gnus users find, after using it a while for both news and
12873 mail, is that the transport mechanism has very little to do with how
12874 they want to treat a message.
12876 Many people subscribe to several mailing lists. These are transported
12877 via @sc{smtp}, and are therefore mail. But we might go for weeks without
12878 answering, or even reading these messages very carefully. We may not
12879 need to save them because if we should need to read one again, they are
12880 archived somewhere else.
12882 Some people have local news groups which have only a handful of readers.
12883 These are transported via @sc{nntp}, and are therefore news. But we may need
12884 to read and answer a large fraction of the messages very carefully in
12885 order to do our work. And there may not be an archive, so we may need
12886 to save the interesting messages the same way we would personal mail.
12888 The important distinction turns out to be not the transport mechanism,
12889 but other factors such as how interested we are in the subject matter,
12890 or how easy it is to retrieve the message if we need to read it again.
12892 Gnus provides many options for sorting mail into ``groups'' which behave
12893 like newsgroups, and for treating each group (whether mail or news)
12896 Some users never get comfortable using the Gnus (ahem) paradigm and wish
12897 that Gnus should grow up and be a male, er, mail reader. It is possible
12898 to whip Gnus into a more mailreaderly being, but, as said before, it's
12899 not easy. People who prefer proper mail readers should try @sc{vm}
12900 instead, which is an excellent, and proper, mail reader.
12902 I don't mean to scare anybody off, but I want to make it clear that you
12903 may be required to learn a new way of thinking about messages. After
12904 you've been subjected to The Gnus Way, you will come to love it. I can
12905 guarantee it. (At least the guy who sold me the Emacs Subliminal
12906 Brain-Washing Functions that I've put into Gnus did guarantee it. You
12907 Will Be Assimilated. You Love Gnus. You Love The Gnus Mail Way.
12911 @node Getting Started Reading Mail
12912 @subsection Getting Started Reading Mail
12914 It's quite easy to use Gnus to read your new mail. You just plonk the
12915 mail back end of your choice into @code{gnus-secondary-select-methods},
12916 and things will happen automatically.
12918 For instance, if you want to use @code{nnml} (which is a ``one file per
12919 mail'' back end), you could put the following in your @file{~/.gnus.el} file:
12922 (setq gnus-secondary-select-methods '((nnml "")))
12925 Now, the next time you start Gnus, this back end will be queried for new
12926 articles, and it will move all the messages in your spool file to its
12927 directory, which is @file{~/Mail/} by default. The new group that will
12928 be created (@samp{mail.misc}) will be subscribed, and you can read it
12929 like any other group.
12931 You will probably want to split the mail into several groups, though:
12934 (setq nnmail-split-methods
12935 '(("junk" "^From:.*Lars Ingebrigtsen")
12936 ("crazy" "^Subject:.*die\\|^Organization:.*flabby")
12940 This will result in three new @code{nnml} mail groups being created:
12941 @samp{nnml:junk}, @samp{nnml:crazy}, and @samp{nnml:other}. All the
12942 mail that doesn't fit into the first two groups will be placed in the
12945 This should be sufficient for reading mail with Gnus. You might want to
12946 give the other sections in this part of the manual a perusal, though.
12947 Especially @pxref{Choosing a Mail Back End} and @pxref{Expiring Mail}.
12950 @node Splitting Mail
12951 @subsection Splitting Mail
12952 @cindex splitting mail
12953 @cindex mail splitting
12955 @vindex nnmail-split-methods
12956 The @code{nnmail-split-methods} variable says how the incoming mail is
12957 to be split into groups.
12960 (setq nnmail-split-methods
12961 '(("mail.junk" "^From:.*Lars Ingebrigtsen")
12962 ("mail.crazy" "^Subject:.*die\\|^Organization:.*flabby")
12963 ("mail.other" "")))
12966 This variable is a list of lists, where the first element of each of
12967 these lists is the name of the mail group (they do not have to be called
12968 something beginning with @samp{mail}, by the way), and the second
12969 element is a regular expression used on the header of each mail to
12970 determine if it belongs in this mail group. The first string may
12971 contain @samp{\\1} forms, like the ones used by @code{replace-match} to
12972 insert sub-expressions from the matched text. For instance:
12975 ("list.\\1" "From:.* \\(.*\\)-list@@majordomo.com")
12978 The second element can also be a function. In that case, it will be
12979 called narrowed to the headers with the first element of the rule as the
12980 argument. It should return a non-@code{nil} value if it thinks that the
12981 mail belongs in that group.
12983 The last of these groups should always be a general one, and the regular
12984 expression should @emph{always} be @samp{*} so that it matches any mails
12985 that haven't been matched by any of the other regexps. (These rules are
12986 processed from the beginning of the alist toward the end. The first
12987 rule to make a match will ``win'', unless you have crossposting enabled.
12988 In that case, all matching rules will ``win''.)
12990 If you like to tinker with this yourself, you can set this variable to a
12991 function of your choice. This function will be called without any
12992 arguments in a buffer narrowed to the headers of an incoming mail
12993 message. The function should return a list of group names that it
12994 thinks should carry this mail message.
12996 Note that the mail back ends are free to maul the poor, innocent,
12997 incoming headers all they want to. They all add @code{Lines} headers;
12998 some add @code{X-Gnus-Group} headers; most rename the Unix mbox
12999 @code{From<SPACE>} line to something else.
13001 @vindex nnmail-crosspost
13002 The mail back ends all support cross-posting. If several regexps match,
13003 the mail will be ``cross-posted'' to all those groups.
13004 @code{nnmail-crosspost} says whether to use this mechanism or not. Note
13005 that no articles are crossposted to the general (@samp{*}) group.
13007 @vindex nnmail-crosspost-link-function
13010 @code{nnmh} and @code{nnml} makes crossposts by creating hard links to
13011 the crossposted articles. However, not all file systems support hard
13012 links. If that's the case for you, set
13013 @code{nnmail-crosspost-link-function} to @code{copy-file}. (This
13014 variable is @code{add-name-to-file} by default.)
13016 @kindex M-x nnmail-split-history
13017 @kindex nnmail-split-history
13018 If you wish to see where the previous mail split put the messages, you
13019 can use the @kbd{M-x nnmail-split-history} command. If you wish to see
13020 where re-spooling messages would put the messages, you can use
13021 @code{gnus-summary-respool-trace} and related commands (@pxref{Mail
13024 @vindex nnmail-split-header-length-limit
13025 Header lines longer than the value of
13026 @code{nnmail-split-header-length-limit} are excluded from the split
13029 @vindex nnmail-mail-splitting-charset
13030 @vindex nnmail-mail-splitting-decodes
13031 By default the splitting codes @sc{mime} decodes headers so you can match
13032 on non-ASCII strings. The @code{nnmail-mail-splitting-charset}
13033 variable specifies the default charset for decoding. The behaviour
13034 can be turned off completely by binding
13035 @code{nnmail-mail-splitting-decodes} to nil, which is useful if you
13036 want to match articles based on the raw header data.
13038 @vindex nnmail-resplit-incoming
13039 By default, splitting is performed on all incoming messages. If
13040 you specify a @code{directory} entry for the variable
13041 @code{mail-sources} @pxref{Mail Source Specifiers}, however, then
13042 splitting does @emph{not} happen by default. You can set the variable
13043 @code{nnmail-resplit-incoming} to a non-nil value to make splitting
13044 happen even in this case. (This variable has no effect on other kinds
13047 Gnus gives you all the opportunity you could possibly want for shooting
13048 yourself in the foot. Let's say you create a group that will contain
13049 all the mail you get from your boss. And then you accidentally
13050 unsubscribe from the group. Gnus will still put all the mail from your
13051 boss in the unsubscribed group, and so, when your boss mails you ``Have
13052 that report ready by Monday or you're fired!'', you'll never see it and,
13053 come Tuesday, you'll still believe that you're gainfully employed while
13054 you really should be out collecting empty bottles to save up for next
13055 month's rent money.
13059 @subsection Mail Sources
13061 Mail can be gotten from many different sources---the mail spool, from a
13062 POP mail server, from a procmail directory, or from a maildir, for
13066 * Mail Source Specifiers:: How to specify what a mail source is.
13067 * Mail Source Customization:: Some variables that influence things.
13068 * Fetching Mail:: Using the mail source specifiers.
13072 @node Mail Source Specifiers
13073 @subsubsection Mail Source Specifiers
13075 @cindex mail server
13078 @cindex mail source
13080 You tell Gnus how to fetch mail by setting @code{mail-sources}
13081 (@pxref{Fetching Mail}) to a @dfn{mail source specifier}.
13086 (pop :server "pop3.mailserver.com" :user "myname")
13089 As can be observed, a mail source specifier is a list where the first
13090 element is a @dfn{mail source type}, followed by an arbitrary number of
13091 @dfn{keywords}. Keywords that are not explicitly specified are given
13094 The following mail source types are available:
13098 Get mail from a single file; typically from the mail spool.
13104 The file name. Defaults to the value of the @code{MAIL}
13105 environment variable or the value of @code{rmail-spool-directory}
13106 (usually something like @file{/usr/mail/spool/user-name}).
13110 Script run before/after fetching mail.
13113 An example file mail source:
13116 (file :path "/usr/spool/mail/user-name")
13119 Or using the default file name:
13125 If the mail spool file is not located on the local machine, it's best to
13126 use POP or @sc{imap} or the like to fetch the mail. You can not use ange-ftp
13127 file names here---it has no way to lock the mail spool while moving the
13130 If it's impossible to set up a proper server, you can use ssh instead.
13134 '((file :prescript "ssh host bin/getmail >%t")))
13137 The @samp{getmail} script would look something like the following:
13141 # getmail - move mail from spool to stdout
13144 MOVEMAIL=/usr/lib/emacs/20.3/i386-redhat-linux/movemail
13146 rm -f $TMP; $MOVEMAIL $MAIL $TMP >/dev/null && cat $TMP
13149 Alter this script to fit find the @samp{movemail} you want to use.
13153 @vindex nnmail-scan-directory-mail-source-once
13154 Get mail from several files in a directory. This is typically used when
13155 you have procmail split the incoming mail into several files. That is,
13156 there is a one-to-one correspondence between files in that directory and
13157 groups, so that mail from the file @file{foo.bar.spool} will be put in
13158 the group @code{foo.bar}. (You can change the suffix to be used instead
13159 of @code{.spool}.) Setting
13160 @code{nnmail-scan-directory-mail-source-once} to non-nil forces Gnus to
13161 scan the mail source only once. This is particularly useful if you want
13162 to scan mail groups at a specified level.
13164 @vindex nnmail-resplit-incoming
13165 There is also the variable @code{nnmail-resplit-incoming}, if you set
13166 that to a non-nil value, then the normal splitting process is applied
13167 to all the files from the directory, @ref{Splitting Mail}.
13173 The name of the directory where the files are. There is no default
13177 Only files ending with this suffix are used. The default is
13181 Only files that have this predicate return non-@code{nil} are returned.
13182 The default is @code{identity}. This is used as an additional
13183 filter---only files that have the right suffix @emph{and} satisfy this
13184 predicate are considered.
13188 Script run before/after fetching mail.
13192 An example directory mail source:
13195 (directory :path "/home/user-name/procmail-dir/"
13200 Get mail from a POP server.
13206 The name of the POP server. The default is taken from the
13207 @code{MAILHOST} environment variable.
13210 The port number of the POP server. This can be a number (eg,
13211 @samp{:port 1234}) or a string (eg, @samp{:port "pop3"}). If it is a
13212 string, it should be a service name as listed in @file{/etc/services} on
13213 Unix systems. The default is @samp{"pop3"}. On some systems you might
13214 need to specify it as @samp{"pop-3"} instead.
13217 The user name to give to the POP server. The default is the login
13221 The password to give to the POP server. If not specified, the user is
13225 The program to use to fetch mail from the POP server. This should be
13226 a @code{format}-like string. Here's an example:
13229 fetchmail %u@@%s -P %p %t
13232 The valid format specifier characters are:
13236 The name of the file the mail is to be moved to. This must always be
13237 included in this string.
13240 The name of the server.
13243 The port number of the server.
13246 The user name to use.
13249 The password to use.
13252 The values used for these specs are taken from the values you give the
13253 corresponding keywords.
13256 A script to be run before fetching the mail. The syntax is the same as
13257 the @code{:program} keyword. This can also be a function to be run.
13260 A script to be run after fetching the mail. The syntax is the same as
13261 the @code{:program} keyword. This can also be a function to be run.
13264 The function to use to fetch mail from the POP server. The function is
13265 called with one parameter---the name of the file where the mail should
13268 @item :authentication
13269 This can be either the symbol @code{password} or the symbol @code{apop}
13270 and says what authentication scheme to use. The default is
13275 If the @code{:program} and @code{:function} keywords aren't specified,
13276 @code{pop3-movemail} will be used.
13278 Here are some examples. Fetch from the default POP server, using the
13279 default user name, and default fetcher:
13285 Fetch from a named server with a named user and password:
13288 (pop :server "my.pop.server"
13289 :user "user-name" :password "secret")
13292 Use @samp{movemail} to move the mail:
13295 (pop :program "movemail po:%u %t %p")
13299 Get mail from a maildir. This is a type of mailbox that is supported by
13300 at least qmail and postfix, where each file in a special directory
13301 contains exactly one mail.
13307 The name of the directory where the mails are stored. The default is
13308 taken from the @code{MAILDIR} environment variable or
13311 The subdirectories of the Maildir. The default is
13312 @samp{("new" "cur")}.
13314 @c If you sometimes look at your mail through a pop3 daemon before fetching
13315 @c them with Gnus, you may also have to fetch your mails from the
13316 @c @code{cur} directory inside the maildir, like in the first example
13319 You can also get mails from remote hosts (because maildirs don't suffer
13320 from locking problems).
13324 Two example maildir mail sources:
13327 (maildir :path "/home/user-name/Maildir/"
13328 :subdirs ("cur" "new"))
13332 (maildir :path "/user@@remotehost.org:~/Maildir/"
13337 Get mail from a @sc{imap} server. If you don't want to use @sc{imap}
13338 as intended, as a network mail reading protocol (ie with nnimap), for
13339 some reason or other, Gnus let you treat it similar to a POP server
13340 and fetches articles from a given @sc{imap} mailbox. @xref{IMAP}, for
13343 Note that for the Kerberos, GSSAPI, TLS/SSL and STARTTLS support you
13344 may need external programs and libraries, @xref{IMAP}.
13350 The name of the @sc{imap} server. The default is taken from the
13351 @code{MAILHOST} environment variable.
13354 The port number of the @sc{imap} server. The default is @samp{143}, or
13355 @samp{993} for TLS/SSL connections.
13358 The user name to give to the @sc{imap} server. The default is the login
13362 The password to give to the @sc{imap} server. If not specified, the user is
13366 What stream to use for connecting to the server, this is one of the
13367 symbols in @code{imap-stream-alist}. Right now, this means
13368 @samp{gssapi}, @samp{kerberos4}, @samp{starttls}, @samp{tls},
13369 @samp{ssl}, @samp{shell} or the default @samp{network}.
13371 @item :authentication
13372 Which authenticator to use for authenticating to the server, this is
13373 one of the symbols in @code{imap-authenticator-alist}. Right now,
13374 this means @samp{gssapi}, @samp{kerberos4}, @samp{digest-md5},
13375 @samp{cram-md5}, @samp{anonymous} or the default @samp{login}.
13378 When using the `shell' :stream, the contents of this variable is
13379 mapped into the @code{imap-shell-program} variable. This should be a
13380 @code{format}-like string (or list of strings). Here's an example:
13386 The valid format specifier characters are:
13390 The name of the server.
13393 User name from @code{imap-default-user}.
13396 The port number of the server.
13399 The values used for these specs are taken from the values you give the
13400 corresponding keywords.
13403 The name of the mailbox to get mail from. The default is @samp{INBOX}
13404 which normally is the mailbox which receive incoming mail.
13407 The predicate used to find articles to fetch. The default, @samp{UNSEEN
13408 UNDELETED}, is probably the best choice for most people, but if you
13409 sometimes peek in your mailbox with a @sc{imap} client and mark some
13410 articles as read (or; SEEN) you might want to set this to @samp{1:*}.
13411 Then all articles in the mailbox is fetched, no matter what. For a
13412 complete list of predicates, see RFC 2060 section 6.4.4.
13415 How to flag fetched articles on the server, the default @samp{\Deleted}
13416 will mark them as deleted, an alternative would be @samp{\Seen} which
13417 would simply mark them as read. These are the two most likely choices,
13418 but more flags are defined in RFC 2060 section 2.3.2.
13421 If non-nil, don't remove all articles marked as deleted in the mailbox
13422 after finishing the fetch.
13426 An example @sc{imap} mail source:
13429 (imap :server "mail.mycorp.com"
13431 :fetchflag "\\Seen")
13435 Get mail from a webmail server, such as @uref{www.hotmail.com},
13436 @uref{webmail.netscape.com}, @uref{www.netaddress.com},
13437 @uref{mail.yahoo..com}.
13439 NOTE: Webmail largely depends cookies. A "one-line-cookie" patch is
13440 required for url "4.0pre.46".
13442 WARNING: Mails may be lost. NO WARRANTY.
13448 The type of the webmail server. The default is @code{hotmail}. The
13449 alternatives are @code{netscape}, @code{netaddress}, @code{my-deja}.
13452 The user name to give to the webmail server. The default is the login
13456 The password to give to the webmail server. If not specified, the user is
13460 If non-nil, only fetch unread articles and don't move them to trash
13461 folder after finishing the fetch.
13465 An example webmail source:
13468 (webmail :subtype 'hotmail
13470 :password "secret")
13475 @item Common Keywords
13476 Common keywords can be used in any type of mail source.
13482 If non-nil, fetch the mail even when Gnus is unplugged. If you use
13483 directory source to get mail, you can specify it as in this example:
13487 '((directory :path "/home/pavel/.Spool/"
13492 Gnus will then fetch your mail even when you are unplugged. This is
13493 useful when you use local mail and news.
13498 @subsubsection Function Interface
13500 Some of the above keywords specify a Lisp function to be executed.
13501 For each keyword @code{:foo}, the Lisp variable @code{foo} is bound to
13502 the value of the keyword while the function is executing. For example,
13503 consider the following mail-source setting:
13506 (setq mail-sources '((pop :user "jrl"
13507 :server "pophost" :function fetchfunc)))
13510 While the function @code{fetchfunc} is executing, the symbol @code{user}
13511 is bound to @code{"jrl"}, and the symbol @code{server} is bound to
13512 @code{"pophost"}. The symbols @code{port}, @code{password},
13513 @code{program}, @code{prescript}, @code{postscript}, @code{function},
13514 and @code{authentication} are also bound (to their default values).
13516 See above for a list of keywords for each type of mail source.
13519 @node Mail Source Customization
13520 @subsubsection Mail Source Customization
13522 The following is a list of variables that influence how the mail is
13523 fetched. You would normally not need to set or change any of these
13527 @item mail-source-crash-box
13528 @vindex mail-source-crash-box
13529 File where mail will be stored while processing it. The default is
13530 @file{~/.emacs-mail-crash-box}.
13532 @item mail-source-delete-incoming
13533 @vindex mail-source-delete-incoming
13534 If non-@code{nil}, delete incoming files after handling them. If
13535 @code{t}, delete the files immediately, if @code{nil}, never delete any
13536 files. If a positive number, delete files older than number of days
13537 (This will only happen, when reveiving new mail). You may also set
13538 @code{mail-source-delete-incoming} to @code{nil} and call
13539 @code{mail-source-delete-old-incoming} from a hook or interactively.
13541 @item mail-source-delete-old-incoming-confirm
13542 @vindex mail-source-delete-old-incoming-confirm
13543 If @code{non-nil}, ask for for confirmation before deleting old incoming
13544 files. This variable only applies when
13545 @code{mail-source-delete-incoming} is a positive number.
13547 @item mail-source-ignore-errors
13548 @vindex mail-source-ignore-errors
13549 If non-@code{nil}, ignore errors when reading mail from a mail source.
13551 @item mail-source-directory
13552 @vindex mail-source-directory
13553 Directory where files (if any) will be stored. The default is
13554 @file{~/Mail/}. At present, the only thing this is used for is to say
13555 where the incoming files will be stored if the previous variable is
13558 @item mail-source-incoming-file-prefix
13559 @vindex mail-source-incoming-file-prefix
13560 Prefix for file name for storing incoming mail. The default is
13561 @file{Incoming}, in which case files will end up with names like
13562 @file{Incoming30630D_} or @file{Incoming298602ZD}. This is really only
13563 relevant if @code{mail-source-delete-incoming} is @code{nil}.
13565 @item mail-source-default-file-modes
13566 @vindex mail-source-default-file-modes
13567 All new mail files will get this file mode. The default is 384.
13569 @item mail-source-movemail-program
13570 @vindex mail-source-movemail-program
13571 If non-nil, name of program for fetching new mail. If nil,
13572 @code{movemail} in @var{exec-directory}.
13577 @node Fetching Mail
13578 @subsubsection Fetching Mail
13580 @vindex mail-sources
13581 @vindex nnmail-spool-file
13582 The way to actually tell Gnus where to get new mail from is to set
13583 @code{mail-sources} to a list of mail source specifiers
13584 (@pxref{Mail Source Specifiers}).
13586 If this variable (and the obsolescent @code{nnmail-spool-file}) is
13587 @code{nil}, the mail back ends will never attempt to fetch mail by
13590 If you want to fetch mail both from your local spool as well as a POP
13591 mail server, you'd say something like:
13596 (pop :server "pop3.mail.server"
13597 :password "secret")))
13600 Or, if you don't want to use any of the keyword defaults:
13604 '((file :path "/var/spool/mail/user-name")
13605 (pop :server "pop3.mail.server"
13608 :password "secret")))
13612 When you use a mail back end, Gnus will slurp all your mail from your
13613 inbox and plonk it down in your home directory. Gnus doesn't move any
13614 mail if you're not using a mail back end---you have to do a lot of magic
13615 invocations first. At the time when you have finished drawing the
13616 pentagram, lightened the candles, and sacrificed the goat, you really
13617 shouldn't be too surprised when Gnus moves your mail.
13621 @node Mail Back End Variables
13622 @subsection Mail Back End Variables
13624 These variables are (for the most part) pertinent to all the various
13628 @vindex nnmail-read-incoming-hook
13629 @item nnmail-read-incoming-hook
13630 The mail back ends all call this hook after reading new mail. You can
13631 use this hook to notify any mail watch programs, if you want to.
13633 @vindex nnmail-split-hook
13634 @item nnmail-split-hook
13635 @findex gnus-article-decode-encoded-words
13636 @findex RFC 1522 decoding
13637 @findex RFC 2047 decoding
13638 Hook run in the buffer where the mail headers of each message is kept
13639 just before the splitting based on these headers is done. The hook is
13640 free to modify the buffer contents in any way it sees fit---the buffer
13641 is discarded after the splitting has been done, and no changes performed
13642 in the buffer will show up in any files.
13643 @code{gnus-article-decode-encoded-words} is one likely function to add
13646 @vindex nnmail-pre-get-new-mail-hook
13647 @vindex nnmail-post-get-new-mail-hook
13648 @item nnmail-pre-get-new-mail-hook
13649 @itemx nnmail-post-get-new-mail-hook
13650 These are two useful hooks executed when treating new incoming
13651 mail---@code{nnmail-pre-get-new-mail-hook} (is called just before
13652 starting to handle the new mail) and
13653 @code{nnmail-post-get-new-mail-hook} (is called when the mail handling
13654 is done). Here's and example of using these two hooks to change the
13655 default file modes the new mail files get:
13658 (add-hook 'nnmail-pre-get-new-mail-hook
13659 (lambda () (set-default-file-modes 511)))
13661 (add-hook 'nnmail-post-get-new-mail-hook
13662 (lambda () (set-default-file-modes 551)))
13665 @item nnmail-use-long-file-names
13666 @vindex nnmail-use-long-file-names
13667 If non-@code{nil}, the mail back ends will use long file and directory
13668 names. Groups like @samp{mail.misc} will end up in directories
13669 (assuming use of @code{nnml} back end) or files (assuming use of
13670 @code{nnfolder} back end) like @file{mail.misc}. If it is @code{nil},
13671 the same group will end up in @file{mail/misc}.
13673 @item nnmail-delete-file-function
13674 @vindex nnmail-delete-file-function
13675 @findex delete-file
13676 Function called to delete files. It is @code{delete-file} by default.
13678 @item nnmail-cache-accepted-message-ids
13679 @vindex nnmail-cache-accepted-message-ids
13680 If non-@code{nil}, put the @code{Message-ID}s of articles imported into
13681 the back end (via @code{Gcc}, for instance) into the mail duplication
13682 discovery cache. The default is @code{nil}.
13684 @item nnmail-cache-ignore-groups
13685 @vindex nnmail-cache-ignore-groups
13686 This can be a regular expression or a list of regular expressions.
13687 Group names that match any of the regular expressions will never be
13688 recorded in the @code{Message-ID} cache.
13690 This can be useful, for example, when using Fancy Splitting
13691 (@pxref{Fancy Mail Splitting}) together with the function
13692 @code{nnmail-split-fancy-with-parent}.
13697 @node Fancy Mail Splitting
13698 @subsection Fancy Mail Splitting
13699 @cindex mail splitting
13700 @cindex fancy mail splitting
13702 @vindex nnmail-split-fancy
13703 @findex nnmail-split-fancy
13704 If the rather simple, standard method for specifying how to split mail
13705 doesn't allow you to do what you want, you can set
13706 @code{nnmail-split-methods} to @code{nnmail-split-fancy}. Then you can
13707 play with the @code{nnmail-split-fancy} variable.
13709 Let's look at an example value of this variable first:
13712 ;; Messages from the mailer daemon are not crossposted to any of
13713 ;; the ordinary groups. Warnings are put in a separate group
13714 ;; from real errors.
13715 (| ("from" mail (| ("subject" "warn.*" "mail.warning")
13717 ;; Non-error messages are crossposted to all relevant
13718 ;; groups, but we don't crosspost between the group for the
13719 ;; (ding) list and the group for other (ding) related mail.
13720 (& (| (any "ding@@ifi\\.uio\\.no" "ding.list")
13721 ("subject" "ding" "ding.misc"))
13722 ;; Other mailing lists...
13723 (any "procmail@@informatik\\.rwth-aachen\\.de" "procmail.list")
13724 (any "SmartList@@informatik\\.rwth-aachen\\.de" "SmartList.list")
13725 ;; Both lists below have the same suffix, so prevent
13726 ;; cross-posting to mkpkg.list of messages posted only to
13727 ;; the bugs- list, but allow cross-posting when the
13728 ;; message was really cross-posted.
13729 (any "bugs-mypackage@@somewhere" "mypkg.bugs")
13730 (any "mypackage@@somewhere\" - "bugs-mypackage" "mypkg.list")
13732 (any "larsi@@ifi\\.uio\\.no" "people.Lars_Magne_Ingebrigtsen"))
13733 ;; Unmatched mail goes to the catch all group.
13737 This variable has the format of a @dfn{split}. A split is a (possibly)
13738 recursive structure where each split may contain other splits. Here are
13739 the five possible split syntaxes:
13744 @samp{group}: If the split is a string, that will be taken as a group
13745 name. Normal regexp match expansion will be done. See below for
13749 @code{(@var{field} @var{value} @code{[-} @var{restrict}
13750 @code{[@dots{}]}@code{]} @var{split})}: If the split is a list, the
13751 first element of which is a string, then store the message as
13752 specified by @var{split}, if header @var{field} (a regexp) contains
13753 @var{value} (also a regexp). If @var{restrict} (yet another regexp)
13754 matches some string after @var{field} and before the end of the
13755 matched @var{value}, the @var{split} is ignored. If none of the
13756 @var{restrict} clauses match, @var{split} is processed.
13759 @code{(| @var{split}@dots{})}: If the split is a list, and the first
13760 element is @code{|} (vertical bar), then process each @var{split} until
13761 one of them matches. A @var{split} is said to match if it will cause
13762 the mail message to be stored in one or more groups.
13765 @code{(& @var{split}@dots{})}: If the split is a list, and the first
13766 element is @code{&}, then process all @var{split}s in the list.
13769 @code{junk}: If the split is the symbol @code{junk}, then don't save
13770 (i.e., delete) this message. Use with extreme caution.
13773 @code{(: @var{function} @var{arg1} @var{arg2} @dots{})}: If the split is
13774 a list, and the first element is @code{:}, then the second element will
13775 be called as a function with @var{args} given as arguments. The
13776 function should return a @var{split}.
13779 For instance, the following function could be used to split based on the
13780 body of the messages:
13783 (defun split-on-body ()
13785 (set-buffer " *nnmail incoming*")
13786 (goto-char (point-min))
13787 (when (re-search-forward "Some.*string" nil t)
13791 The @samp{" *nnmail incoming*"} is narrowed to the message in question
13792 when the @code{:} function is run.
13795 @code{(! @var{func} @var{split})}: If the split is a list, and the
13796 first element is @code{!}, then @var{split} will be processed, and
13797 @var{func} will be called as a function with the result of @var{split}
13798 as argument. @var{func} should return a split.
13801 @code{nil}: If the split is @code{nil}, it is ignored.
13805 In these splits, @var{field} must match a complete field name.
13806 @var{value} must match a complete word according to the fundamental mode
13807 syntax table. You can use @code{.*} in the regexps to match partial
13808 field names or words. In other words, all @var{value}'s are wrapped in
13809 @samp{\<} and @samp{\>} pairs.
13811 @vindex nnmail-split-abbrev-alist
13812 @var{field} and @var{value} can also be lisp symbols, in that case they
13813 are expanded as specified by the variable
13814 @code{nnmail-split-abbrev-alist}. This is an alist of cons cells, where
13815 the @code{car} of a cell contains the key, and the @code{cdr} contains the associated
13818 @vindex nnmail-split-fancy-syntax-table
13819 @code{nnmail-split-fancy-syntax-table} is the syntax table in effect
13820 when all this splitting is performed.
13822 If you want to have Gnus create groups dynamically based on some
13823 information in the headers (i.e., do @code{replace-match}-like
13824 substitutions in the group names), you can say things like:
13827 (any "debian-\\b\\(\\w+\\)@@lists.debian.org" "mail.debian.\\1")
13830 In this example, messages sent to @samp{debian-foo@@lists.debian.org}
13831 will be filed in @samp{mail.debian.foo}.
13833 If the string contains the element @samp{\&}, then the previously
13834 matched string will be substituted. Similarly, the elements @samp{\\1}
13835 up to @samp{\\9} will be substituted with the text matched by the
13836 groupings 1 through 9.
13838 @findex nnmail-split-fancy-with-parent
13839 @code{nnmail-split-fancy-with-parent} is a function which allows you to
13840 split followups into the same groups their parents are in. Sometimes
13841 you can't make splitting rules for all your mail. For example, your
13842 boss might send you personal mail regarding different projects you are
13843 working on, and as you can't tell your boss to put a distinguishing
13844 string into the subject line, you have to resort to manually moving the
13845 messages into the right group. With this function, you only have to do
13846 it once per thread.
13848 To use this feature, you have to set @code{nnmail-treat-duplicates} and
13849 @code{nnmail-cache-accepted-message-ids} to a non-nil value. And then
13850 you can include @code{nnmail-split-fancy-with-parent} using the colon
13853 (setq nnmail-treat-duplicates 'warn ; or 'delete
13854 nnmail-cache-accepted-message-ids t
13856 '(| (: nnmail-split-fancy-with-parent)
13857 ;; other splits go here
13861 This feature works as follows: when @code{nnmail-treat-duplicates} is
13862 non-nil, Gnus records the message id of every message it sees in the
13863 file specified by the variable @code{nnmail-message-id-cache-file},
13864 together with the group it is in (the group is omitted for non-mail
13865 messages). When mail splitting is invoked, the function
13866 @code{nnmail-split-fancy-with-parent} then looks at the References (and
13867 In-Reply-To) header of each message to split and searches the file
13868 specified by @code{nnmail-message-id-cache-file} for the message ids.
13869 When it has found a parent, it returns the corresponding group name
13870 unless the group name matches the regexp
13871 @code{nnmail-split-fancy-with-parent-ignore-groups}. It is recommended
13872 that you set @code{nnmail-message-id-cache-length} to a somewhat higher
13873 number than the default so that the message ids are still in the cache.
13874 (A value of 5000 appears to create a file some 300 kBytes in size.)
13875 @vindex nnmail-cache-accepted-message-ids
13876 When @code{nnmail-cache-accepted-message-ids} is non-@code{nil}, Gnus
13877 also records the message ids of moved articles, so that the followup
13878 messages goes into the new group.
13880 Also see the variable @code{nnmail-cache-ignore-groups} if you don't
13881 want certain groups to be recorded in the cache. For example, if all
13882 outgoing messages are written to an `outgoing' group, you could set
13883 @code{nnmail-cache-ignore-groups} to match that group name.
13884 Otherwise, answers to all your messages would end up in the
13888 @node Group Mail Splitting
13889 @subsection Group Mail Splitting
13890 @cindex mail splitting
13891 @cindex group mail splitting
13893 @findex gnus-group-split
13894 If you subscribe to dozens of mailing lists but you don't want to
13895 maintain mail splitting rules manually, group mail splitting is for you.
13896 You just have to set @var{to-list} and/or @var{to-address} in group
13897 parameters or group customization and set @code{nnmail-split-methods} to
13898 @code{gnus-group-split}. This splitting function will scan all groups
13899 for those parameters and split mail accordingly, i.e., messages posted
13900 from or to the addresses specified in the parameters @var{to-list} or
13901 @var{to-address} of a mail group will be stored in that group.
13903 Sometimes, mailing lists have multiple addresses, and you may want mail
13904 splitting to recognize them all: just set the @var{extra-aliases} group
13905 parameter to the list of additional addresses and it's done. If you'd
13906 rather use a regular expression, set @var{split-regexp}.
13908 All these parameters in a group will be used to create an
13909 @code{nnmail-split-fancy} split, in which the @var{field} is @samp{any},
13910 the @var{value} is a single regular expression that matches
13911 @var{to-list}, @var{to-address}, all of @var{extra-aliases} and all
13912 matches of @var{split-regexp}, and the @var{split} is the name of the
13913 group. @var{restrict}s are also supported: just set the
13914 @var{split-exclude} parameter to a list of regular expressions.
13916 If you can't get the right split to be generated using all these
13917 parameters, or you just need something fancier, you can set the
13918 parameter @var{split-spec} to an @code{nnmail-split-fancy} split. In
13919 this case, all other aforementioned parameters will be ignored by
13920 @code{gnus-group-split}. In particular, @var{split-spec} may be set to
13921 @code{nil}, in which case the group will be ignored by
13922 @code{gnus-group-split}.
13924 @vindex gnus-group-split-default-catch-all-group
13925 @code{gnus-group-split} will do cross-posting on all groups that match,
13926 by defining a single @code{&} fancy split containing one split for each
13927 group. If a message doesn't match any split, it will be stored in the
13928 group named in @code{gnus-group-split-default-catch-all-group}, unless
13929 some group has @var{split-spec} set to @code{catch-all}, in which case
13930 that group is used as the catch-all group. Even though this variable is
13931 often used just to name a group, it may also be set to an arbitrarily
13932 complex fancy split (after all, a group name is a fancy split), and this
13933 may be useful to split mail that doesn't go to any mailing list to
13934 personal mail folders. Note that this fancy split is added as the last
13935 element of a @code{|} split list that also contains a @code{&} split
13936 with the rules extracted from group parameters.
13938 It's time for an example. Assume the following group parameters have
13943 ((to-address . "bar@@femail.com")
13944 (split-regexp . ".*@@femail\\.com"))
13946 ((to-list . "foo@@nowhere.gov")
13947 (extra-aliases "foo@@localhost" "foo-redist@@home")
13948 (split-exclude "bugs-foo" "rambling-foo")
13949 (admin-address . "foo-request@@nowhere.gov"))
13951 ((split-spec . catch-all))
13954 Setting @code{nnmail-split-methods} to @code{gnus-group-split} will
13955 behave as if @code{nnmail-split-fancy} had been selected and variable
13956 @code{nnmail-split-fancy} had been set as follows:
13959 (| (& (any "\\(bar@@femail\\.com\\|.*@@femail\\.com\\)" "mail.bar")
13960 (any "\\(foo@@nowhere\\.gov\\|foo@@localhost\\|foo-redist@@home\\)"
13961 - "bugs-foo" - "rambling-foo" "mail.foo"))
13965 @findex gnus-group-split-fancy
13966 If you'd rather not use group splitting for all your mail groups, you
13967 may use it for only some of them, by using @code{nnmail-split-fancy}
13971 (: gnus-group-split-fancy GROUPS NO-CROSSPOST CATCH-ALL)
13974 @var{groups} may be a regular expression or a list of group names whose
13975 parameters will be scanned to generate the output split.
13976 @var{no-crosspost} can be used to disable cross-posting; in this case, a
13977 single @code{|} split will be output. @var{catch-all} is the fallback
13978 fancy split, used like @var{gnus-group-split-default-catch-all-group}.
13979 If @var{catch-all} is @code{nil}, or if @var{split-regexp} matches the
13980 empty string in any selected group, no catch-all split will be issued.
13981 Otherwise, if some group has @var{split-spec} set to @code{catch-all},
13982 this group will override the value of the @var{catch-all} argument.
13984 @findex gnus-group-split-setup
13985 Unfortunately, scanning all groups and their parameters can be quite
13986 slow, especially considering that it has to be done for every message.
13987 But don't despair! The function @code{gnus-group-split-setup} can be
13988 used to enable @code{gnus-group-split} in a much more efficient way. It
13989 sets @code{nnmail-split-methods} to @code{nnmail-split-fancy} and sets
13990 @code{nnmail-split-fancy} to the split produced by
13991 @code{gnus-group-split-fancy}. Thus, the group parameters are only
13992 scanned once, no matter how many messages are split.
13994 @findex gnus-group-split-update
13995 However, if you change group parameters, you'd have to update
13996 @code{nnmail-split-fancy} manually. You can do it by running
13997 @code{gnus-group-split-update}. If you'd rather have it updated
13998 automatically, just tell @code{gnus-group-split-setup} to do it for
13999 you. For example, add to your @file{~/.gnus.el}:
14002 (gnus-group-split-setup AUTO-UPDATE CATCH-ALL)
14005 If @var{auto-update} is non-@code{nil}, @code{gnus-group-split-update}
14006 will be added to @code{nnmail-pre-get-new-mail-hook}, so you won't ever
14007 have to worry about updating @code{nnmail-split-fancy} again. If you
14008 don't omit @var{catch-all} (it's optional, equivalent to @code{nil}),
14009 @code{gnus-group-split-default-catch-all-group} will be set to its
14012 @vindex gnus-group-split-updated-hook
14013 Because you may want to change @code{nnmail-split-fancy} after it is set
14014 by @code{gnus-group-split-update}, this function will run
14015 @code{gnus-group-split-updated-hook} just before finishing.
14017 @node Incorporating Old Mail
14018 @subsection Incorporating Old Mail
14019 @cindex incorporating old mail
14020 @cindex import old mail
14022 Most people have lots of old mail stored in various file formats. If
14023 you have set up Gnus to read mail using one of the spiffy Gnus mail
14024 back ends, you'll probably wish to have that old mail incorporated into
14027 Doing so can be quite easy.
14029 To take an example: You're reading mail using @code{nnml}
14030 (@pxref{Mail Spool}), and have set @code{nnmail-split-methods} to a
14031 satisfactory value (@pxref{Splitting Mail}). You have an old Unix mbox
14032 file filled with important, but old, mail. You want to move it into
14033 your @code{nnml} groups.
14039 Go to the group buffer.
14042 Type @kbd{G f} and give the file name to the mbox file when prompted to create an
14043 @code{nndoc} group from the mbox file (@pxref{Foreign Groups}).
14046 Type @kbd{SPACE} to enter the newly created group.
14049 Type @kbd{M P b} to process-mark all articles in this group's buffer
14050 (@pxref{Setting Process Marks}).
14053 Type @kbd{B r} to respool all the process-marked articles, and answer
14054 @samp{nnml} when prompted (@pxref{Mail Group Commands}).
14057 All the mail messages in the mbox file will now also be spread out over
14058 all your @code{nnml} groups. Try entering them and check whether things
14059 have gone without a glitch. If things look ok, you may consider
14060 deleting the mbox file, but I wouldn't do that unless I was absolutely
14061 sure that all the mail has ended up where it should be.
14063 Respooling is also a handy thing to do if you're switching from one mail
14064 back end to another. Just respool all the mail in the old mail groups
14065 using the new mail back end.
14068 @node Expiring Mail
14069 @subsection Expiring Mail
14070 @cindex article expiry
14072 Traditional mail readers have a tendency to remove mail articles when
14073 you mark them as read, in some way. Gnus takes a fundamentally
14074 different approach to mail reading.
14076 Gnus basically considers mail just to be news that has been received in
14077 a rather peculiar manner. It does not think that it has the power to
14078 actually change the mail, or delete any mail messages. If you enter a
14079 mail group, and mark articles as ``read'', or kill them in some other
14080 fashion, the mail articles will still exist on the system. I repeat:
14081 Gnus will not delete your old, read mail. Unless you ask it to, of
14084 To make Gnus get rid of your unwanted mail, you have to mark the
14085 articles as @dfn{expirable}. (With the default keybindings, this means
14086 that you have to type @kbd{E}.) This does not mean that the articles
14087 will disappear right away, however. In general, a mail article will be
14088 deleted from your system if, 1) it is marked as expirable, AND 2) it is
14089 more than one week old. If you do not mark an article as expirable, it
14090 will remain on your system until hell freezes over. This bears
14091 repeating one more time, with some spurious capitalizations: IF you do
14092 NOT mark articles as EXPIRABLE, Gnus will NEVER delete those ARTICLES.
14094 You do not have to mark articles as expirable by hand. Gnus provides
14095 two features, called `auto-expire' and `total-expire', that can help you
14096 with this. In a nutshell, `auto-expire' means that Gnus hits @kbd{E}
14097 for you when you select an article. And `total-expire' means that Gnus
14098 considers all articles as expirable that are read. So, in addition to
14099 the articles marked @samp{E}, also the articles marked @samp{r},
14100 @samp{R}, @samp{O}, @samp{K}, @samp{Y} and so on are considered
14103 When should either auto-expire or total-expire be used? Most people
14104 who are subscribed to mailing lists split each list into its own group
14105 and then turn on auto-expire or total-expire for those groups.
14106 (@xref{Splitting Mail}, for more information on splitting each list
14107 into its own group.)
14109 Which one is better, auto-expire or total-expire? It's not easy to
14110 answer. Generally speaking, auto-expire is probably faster. Another
14111 advantage of auto-expire is that you get more marks to work with: for
14112 the articles that are supposed to stick around, you can still choose
14113 between tick and dormant and read marks. But with total-expire, you
14114 only have dormant and ticked to choose from. The advantage of
14115 total-expire is that it works well with adaptive scoring @pxref{Adaptive
14116 Scoring}. Auto-expire works with normal scoring but not with adaptive
14119 @vindex gnus-auto-expirable-newsgroups
14120 Groups that match the regular expression
14121 @code{gnus-auto-expirable-newsgroups} will have all articles that you
14122 read marked as expirable automatically. All articles marked as
14123 expirable have an @samp{E} in the first column in the summary buffer.
14125 By default, if you have auto expiry switched on, Gnus will mark all the
14126 articles you read as expirable, no matter if they were read or unread
14127 before. To avoid having articles marked as read marked as expirable
14128 automatically, you can put something like the following in your
14129 @file{~/.gnus.el} file:
14131 @vindex gnus-mark-article-hook
14133 (remove-hook 'gnus-mark-article-hook
14134 'gnus-summary-mark-read-and-unread-as-read)
14135 (add-hook 'gnus-mark-article-hook 'gnus-summary-mark-unread-as-read)
14138 Note that making a group auto-expirable doesn't mean that all read
14139 articles are expired---only the articles marked as expirable
14140 will be expired. Also note that using the @kbd{d} command won't make
14141 articles expirable---only semi-automatic marking of articles as read will
14142 mark the articles as expirable in auto-expirable groups.
14144 Let's say you subscribe to a couple of mailing lists, and you want the
14145 articles you have read to disappear after a while:
14148 (setq gnus-auto-expirable-newsgroups
14149 "mail.nonsense-list\\|mail.nice-list")
14152 Another way to have auto-expiry happen is to have the element
14153 @code{auto-expire} in the group parameters of the group.
14155 If you use adaptive scoring (@pxref{Adaptive Scoring}) and
14156 auto-expiring, you'll have problems. Auto-expiring and adaptive scoring
14157 don't really mix very well.
14159 @vindex nnmail-expiry-wait
14160 The @code{nnmail-expiry-wait} variable supplies the default time an
14161 expirable article has to live. Gnus starts counting days from when the
14162 message @emph{arrived}, not from when it was sent. The default is seven
14165 Gnus also supplies a function that lets you fine-tune how long articles
14166 are to live, based on what group they are in. Let's say you want to
14167 have one month expiry period in the @samp{mail.private} group, a one day
14168 expiry period in the @samp{mail.junk} group, and a six day expiry period
14171 @vindex nnmail-expiry-wait-function
14173 (setq nnmail-expiry-wait-function
14175 (cond ((string= group "mail.private")
14177 ((string= group "mail.junk")
14179 ((string= group "important")
14185 The group names this function is fed are ``unadorned'' group
14186 names---no @samp{nnml:} prefixes and the like.
14188 The @code{nnmail-expiry-wait} variable and
14189 @code{nnmail-expiry-wait-function} function can either be a number (not
14190 necessarily an integer) or one of the symbols @code{immediate} or
14193 You can also use the @code{expiry-wait} group parameter to selectively
14194 change the expiry period (@pxref{Group Parameters}).
14196 @vindex nnmail-expiry-target
14197 The normal action taken when expiring articles is to delete them.
14198 However, in some circumstances it might make more sense to move them
14199 to other groups instead of deleting them. The variable
14200 @code{nnmail-expiry-target} (and the @code{expiry-target} group
14201 parameter) controls this. The variable supplies a default value for
14202 all groups, which can be overridden for specific groups by the group
14203 parameter. default value is @code{delete}, but this can also be a
14204 string (which should be the name of the group the message should be
14205 moved to), or a function (which will be called in a buffer narrowed to
14206 the message in question, and with the name of the group being moved
14207 from as its parameter) which should return a target -- either a group
14208 name or @code{delete}.
14210 Here's an example for specifying a group name:
14212 (setq nnmail-expiry-target "nnml:expired")
14215 @findex nnmail-fancy-expiry-target
14216 @vindex nnmail-fancy-expiry-targets
14217 Gnus provides a function @code{nnmail-fancy-expiry-target} which will
14218 expire mail to groups according to the variable
14219 @code{nnmail-fancy-expiry-targets}. Here's an example:
14222 (setq nnmail-expiry-target 'nnmail-fancy-expiry-target
14223 nnmail-fancy-expiry-targets
14224 '((to-from "boss" "nnfolder:Work")
14225 ("subject" "IMPORTANT" "nnfolder:IMPORTANT.%Y.%b")
14226 ("from" ".*" "nnfolder:Archive-%Y")))
14229 With this setup, any mail that has @code{IMPORTANT} in its Subject
14230 header and was sent in the year @code{YYYY} and month @code{MMM}, will
14231 get expired to the group @code{nnfolder:IMPORTANT.YYYY.MMM}. If its
14232 From or To header contains the string @code{boss}, it will get expired
14233 to @code{nnfolder:Work}. All other mail will get expired to
14234 @code{nnfolder:Archive-YYYY}.
14236 @vindex nnmail-keep-last-article
14237 If @code{nnmail-keep-last-article} is non-@code{nil}, Gnus will never
14238 expire the final article in a mail newsgroup. This is to make life
14239 easier for procmail users.
14241 @vindex gnus-total-expirable-newsgroups
14242 By the way: That line up there, about Gnus never expiring non-expirable
14243 articles, is a lie. If you put @code{total-expire} in the group
14244 parameters, articles will not be marked as expirable, but all read
14245 articles will be put through the expiry process. Use with extreme
14246 caution. Even more dangerous is the
14247 @code{gnus-total-expirable-newsgroups} variable. All groups that match
14248 this regexp will have all read articles put through the expiry process,
14249 which means that @emph{all} old mail articles in the groups in question
14250 will be deleted after a while. Use with extreme caution, and don't come
14251 crying to me when you discover that the regexp you used matched the
14252 wrong group and all your important mail has disappeared. Be a
14253 @emph{man}! Or a @emph{woman}! Whatever you feel more comfortable
14256 Most people make most of their mail groups total-expirable, though.
14258 @vindex gnus-inhibit-user-auto-expire
14259 If @code{gnus-inhibit-user-auto-expire} is non-@code{nil}, user marking
14260 commands will not mark an article as expirable, even if the group has
14261 auto-expire turned on.
14265 @subsection Washing Mail
14266 @cindex mail washing
14267 @cindex list server brain damage
14268 @cindex incoming mail treatment
14270 Mailers and list servers are notorious for doing all sorts of really,
14271 really stupid things with mail. ``Hey, RFC 822 doesn't explicitly
14272 prohibit us from adding the string @code{wE aRe ElItE!!!!!1!!} to the
14273 end of all lines passing through our server, so let's do that!!!!1!''
14274 Yes, but RFC 822 wasn't designed to be read by morons. Things that were
14275 considered to be self-evident were not discussed. So. Here we are.
14277 Case in point: The German version of Microsoft Exchange adds @samp{AW:
14278 } to the subjects of replies instead of @samp{Re: }. I could pretend to
14279 be shocked and dismayed by this, but I haven't got the energy. It is to
14282 Gnus provides a plethora of functions for washing articles while
14283 displaying them, but it might be nicer to do the filtering before
14284 storing the mail to disk. For that purpose, we have three hooks and
14285 various functions that can be put in these hooks.
14288 @item nnmail-prepare-incoming-hook
14289 @vindex nnmail-prepare-incoming-hook
14290 This hook is called before doing anything with the mail and is meant for
14291 grand, sweeping gestures. It is called in a buffer that contains all
14292 the new, incoming mail. Functions to be used include:
14295 @item nnheader-ms-strip-cr
14296 @findex nnheader-ms-strip-cr
14297 Remove trailing carriage returns from each line. This is default on
14298 Emacs running on MS machines.
14302 @item nnmail-prepare-incoming-header-hook
14303 @vindex nnmail-prepare-incoming-header-hook
14304 This hook is called narrowed to each header. It can be used when
14305 cleaning up the headers. Functions that can be used include:
14308 @item nnmail-remove-leading-whitespace
14309 @findex nnmail-remove-leading-whitespace
14310 Clear leading white space that ``helpful'' listservs have added to the
14311 headers to make them look nice. Aaah.
14313 (Note that this function works on both the header on the body of all
14314 messages, so it is a potentially dangerous function to use (if a body
14315 of a message contains something that looks like a header line). So
14316 rather than fix the bug, it is of course the right solution to make it
14317 into a feature by documenting it.)
14319 @item nnmail-remove-list-identifiers
14320 @findex nnmail-remove-list-identifiers
14321 Some list servers add an identifier---for example, @samp{(idm)}---to the
14322 beginning of all @code{Subject} headers. I'm sure that's nice for
14323 people who use stone age mail readers. This function will remove
14324 strings that match the @code{nnmail-list-identifiers} regexp, which can
14325 also be a list of regexp. @code{nnmail-list-identifiers} may not contain
14328 For instance, if you want to remove the @samp{(idm)} and the
14329 @samp{nagnagnag} identifiers:
14332 (setq nnmail-list-identifiers
14333 '("(idm)" "nagnagnag"))
14336 This can also be done non-destructively with
14337 @code{gnus-list-identifiers}, @xref{Article Hiding}.
14339 @item nnmail-remove-tabs
14340 @findex nnmail-remove-tabs
14341 Translate all @samp{TAB} characters into @samp{SPACE} characters.
14343 @item nnmail-fix-eudora-headers
14344 @findex nnmail-fix-eudora-headers
14346 Eudora produces broken @code{References} headers, but OK
14347 @code{In-Reply-To} headers. This function will get rid of the
14348 @code{References} headers.
14352 @item nnmail-prepare-incoming-message-hook
14353 @vindex nnmail-prepare-incoming-message-hook
14354 This hook is called narrowed to each message. Functions to be used
14358 @item article-de-quoted-unreadable
14359 @findex article-de-quoted-unreadable
14360 Decode Quoted Readable encoding.
14367 @subsection Duplicates
14369 @vindex nnmail-treat-duplicates
14370 @vindex nnmail-message-id-cache-length
14371 @vindex nnmail-message-id-cache-file
14372 @cindex duplicate mails
14373 If you are a member of a couple of mailing lists, you will sometimes
14374 receive two copies of the same mail. This can be quite annoying, so
14375 @code{nnmail} checks for and treats any duplicates it might find. To do
14376 this, it keeps a cache of old @code{Message-ID}s---
14377 @code{nnmail-message-id-cache-file}, which is @file{~/.nnmail-cache} by
14378 default. The approximate maximum number of @code{Message-ID}s stored
14379 there is controlled by the @code{nnmail-message-id-cache-length}
14380 variable, which is 1000 by default. (So 1000 @code{Message-ID}s will be
14381 stored.) If all this sounds scary to you, you can set
14382 @code{nnmail-treat-duplicates} to @code{warn} (which is what it is by
14383 default), and @code{nnmail} won't delete duplicate mails. Instead it
14384 will insert a warning into the head of the mail saying that it thinks
14385 that this is a duplicate of a different message.
14387 This variable can also be a function. If that's the case, the function
14388 will be called from a buffer narrowed to the message in question with
14389 the @code{Message-ID} as a parameter. The function must return either
14390 @code{nil}, @code{warn}, or @code{delete}.
14392 You can turn this feature off completely by setting the variable to
14395 If you want all the duplicate mails to be put into a special
14396 @dfn{duplicates} group, you could do that using the normal mail split
14400 (setq nnmail-split-fancy
14401 '(| ;; Messages duplicates go to a separate group.
14402 ("gnus-warning" "duplicat\\(e\\|ion\\) of message" "duplicate")
14403 ;; Message from daemons, postmaster, and the like to another.
14404 (any mail "mail.misc")
14411 (setq nnmail-split-methods
14412 '(("duplicates" "^Gnus-Warning:.*duplicate")
14417 Here's a neat feature: If you know that the recipient reads her mail
14418 with Gnus, and that she has @code{nnmail-treat-duplicates} set to
14419 @code{delete}, you can send her as many insults as you like, just by
14420 using a @code{Message-ID} of a mail that you know that she's already
14421 received. Think of all the fun! She'll never see any of it! Whee!
14424 @node Not Reading Mail
14425 @subsection Not Reading Mail
14427 If you start using any of the mail back ends, they have the annoying
14428 habit of assuming that you want to read mail with them. This might not
14429 be unreasonable, but it might not be what you want.
14431 If you set @code{mail-sources} and @code{nnmail-spool-file} to
14432 @code{nil}, none of the back ends will ever attempt to read incoming
14433 mail, which should help.
14435 @vindex nnbabyl-get-new-mail
14436 @vindex nnmbox-get-new-mail
14437 @vindex nnml-get-new-mail
14438 @vindex nnmh-get-new-mail
14439 @vindex nnfolder-get-new-mail
14440 This might be too much, if, for instance, you are reading mail quite
14441 happily with @code{nnml} and just want to peek at some old @sc{rmail}
14442 file you have stashed away with @code{nnbabyl}. All back ends have
14443 variables called back-end-@code{get-new-mail}. If you want to disable
14444 the @code{nnbabyl} mail reading, you edit the virtual server for the
14445 group to have a setting where @code{nnbabyl-get-new-mail} to @code{nil}.
14447 All the mail back ends will call @code{nn}*@code{-prepare-save-mail-hook}
14448 narrowed to the article to be saved before saving it when reading
14452 @node Choosing a Mail Back End
14453 @subsection Choosing a Mail Back End
14455 Gnus will read the mail spool when you activate a mail group. The mail
14456 file is first copied to your home directory. What happens after that
14457 depends on what format you want to store your mail in.
14459 There are six different mail back ends in the standard Gnus, and more
14460 back ends are available separately. The mail back end most people use
14461 (because it is possibly the fastest) is @code{nnml} (@pxref{Mail
14465 * Unix Mail Box:: Using the (quite) standard Un*x mbox.
14466 * Rmail Babyl:: Emacs programs use the rmail babyl format.
14467 * Mail Spool:: Store your mail in a private spool?
14468 * MH Spool:: An mhspool-like back end.
14469 * Maildir:: Another one-file-per-message format.
14470 * Mail Folders:: Having one file for each group.
14471 * Comparing Mail Back Ends:: An in-depth looks at pros and cons.
14475 @node Unix Mail Box
14476 @subsubsection Unix Mail Box
14478 @cindex unix mail box
14480 @vindex nnmbox-active-file
14481 @vindex nnmbox-mbox-file
14482 The @dfn{nnmbox} back end will use the standard Un*x mbox file to store
14483 mail. @code{nnmbox} will add extra headers to each mail article to say
14484 which group it belongs in.
14486 Virtual server settings:
14489 @item nnmbox-mbox-file
14490 @vindex nnmbox-mbox-file
14491 The name of the mail box in the user's home directory. Default is
14494 @item nnmbox-active-file
14495 @vindex nnmbox-active-file
14496 The name of the active file for the mail box. Default is
14497 @file{~/.mbox-active}.
14499 @item nnmbox-get-new-mail
14500 @vindex nnmbox-get-new-mail
14501 If non-@code{nil}, @code{nnmbox} will read incoming mail and split it
14502 into groups. Default is @code{t}.
14507 @subsubsection Rmail Babyl
14511 @vindex nnbabyl-active-file
14512 @vindex nnbabyl-mbox-file
14513 The @dfn{nnbabyl} back end will use a babyl mail box (aka. @dfn{rmail
14514 mbox}) to store mail. @code{nnbabyl} will add extra headers to each
14515 mail article to say which group it belongs in.
14517 Virtual server settings:
14520 @item nnbabyl-mbox-file
14521 @vindex nnbabyl-mbox-file
14522 The name of the rmail mbox file. The default is @file{~/RMAIL}
14524 @item nnbabyl-active-file
14525 @vindex nnbabyl-active-file
14526 The name of the active file for the rmail box. The default is
14527 @file{~/.rmail-active}
14529 @item nnbabyl-get-new-mail
14530 @vindex nnbabyl-get-new-mail
14531 If non-@code{nil}, @code{nnbabyl} will read incoming mail. Default is
14537 @subsubsection Mail Spool
14539 @cindex mail @sc{nov} spool
14541 The @dfn{nnml} spool mail format isn't compatible with any other known
14542 format. It should be used with some caution.
14544 @vindex nnml-directory
14545 If you use this back end, Gnus will split all incoming mail into files,
14546 one file for each mail, and put the articles into the corresponding
14547 directories under the directory specified by the @code{nnml-directory}
14548 variable. The default value is @file{~/Mail/}.
14550 You do not have to create any directories beforehand; Gnus will take
14553 If you have a strict limit as to how many files you are allowed to store
14554 in your account, you should not use this back end. As each mail gets its
14555 own file, you might very well occupy thousands of inodes within a few
14556 weeks. If this is no problem for you, and it isn't a problem for you
14557 having your friendly systems administrator walking around, madly,
14558 shouting ``Who is eating all my inodes?! Who? Who!?!'', then you should
14559 know that this is probably the fastest format to use. You do not have
14560 to trudge through a big mbox file just to read your new mail.
14562 @code{nnml} is probably the slowest back end when it comes to article
14563 splitting. It has to create lots of files, and it also generates
14564 @sc{nov} databases for the incoming mails. This makes it possibly the
14565 fastest back end when it comes to reading mail.
14567 @cindex self contained nnml servers
14569 When the marks file is used (which it is by default), @code{nnml}
14570 servers have the property that you may backup them using @code{tar} or
14571 similar, and later be able to restore them into Gnus (by adding the
14572 proper @code{nnml} server) and have all your marks be preserved. Marks
14573 for a group is usually stored in the @code{.marks} file (but see
14574 @code{nnml-marks-file-name}) within each @code{nnml} group's directory.
14575 Individual @code{nnml} groups are also possible to backup, use @kbd{G m}
14576 to restore the group (after restoring the backup into the nnml
14579 If for some reason you believe your @file{.marks} files are screwed
14580 up, you can just delete them all. Gnus will then correctly regenerate
14581 them next time it starts.
14583 Virtual server settings:
14586 @item nnml-directory
14587 @vindex nnml-directory
14588 All @code{nnml} directories will be placed under this directory. The
14589 default is the value of @code{message-directory} (whose default value
14592 @item nnml-active-file
14593 @vindex nnml-active-file
14594 The active file for the @code{nnml} server. The default is
14595 @file{~/Mail/active}.
14597 @item nnml-newsgroups-file
14598 @vindex nnml-newsgroups-file
14599 The @code{nnml} group descriptions file. @xref{Newsgroups File
14600 Format}. The default is @file{~/Mail/newsgroups}.
14602 @item nnml-get-new-mail
14603 @vindex nnml-get-new-mail
14604 If non-@code{nil}, @code{nnml} will read incoming mail. The default is
14607 @item nnml-nov-is-evil
14608 @vindex nnml-nov-is-evil
14609 If non-@code{nil}, this back end will ignore any @sc{nov} files. The
14610 default is @code{nil}.
14612 @item nnml-nov-file-name
14613 @vindex nnml-nov-file-name
14614 The name of the @sc{nov} files. The default is @file{.overview}.
14616 @item nnml-prepare-save-mail-hook
14617 @vindex nnml-prepare-save-mail-hook
14618 Hook run narrowed to an article before saving.
14620 @item nnml-marks-is-evil
14621 @vindex nnml-marks-is-evil
14622 If non-@code{nil}, this back end will ignore any @sc{marks} files. The
14623 default is @code{nil}.
14625 @item nnml-marks-file-name
14626 @vindex nnml-marks-file-name
14627 The name of the @dfn{marks} files. The default is @file{.marks}.
14629 @item nnml-use-compressed-files
14630 @vindex nnml-use-compressed-files
14631 If non-@code{nil}, @code{nnml} will allow using compressed message
14636 @findex nnml-generate-nov-databases
14637 If your @code{nnml} groups and @sc{nov} files get totally out of whack,
14638 you can do a complete update by typing @kbd{M-x
14639 nnml-generate-nov-databases}. This command will trawl through the
14640 entire @code{nnml} hierarchy, looking at each and every article, so it
14641 might take a while to complete. A better interface to this
14642 functionality can be found in the server buffer (@pxref{Server
14647 @subsubsection MH Spool
14649 @cindex mh-e mail spool
14651 @code{nnmh} is just like @code{nnml}, except that is doesn't generate
14652 @sc{nov} databases and it doesn't keep an active file or marks file.
14653 This makes @code{nnmh} a @emph{much} slower back end than @code{nnml},
14654 but it also makes it easier to write procmail scripts for.
14656 Virtual server settings:
14659 @item nnmh-directory
14660 @vindex nnmh-directory
14661 All @code{nnmh} directories will be located under this directory. The
14662 default is the value of @code{message-directory} (whose default is
14665 @item nnmh-get-new-mail
14666 @vindex nnmh-get-new-mail
14667 If non-@code{nil}, @code{nnmh} will read incoming mail. The default is
14671 @vindex nnmh-be-safe
14672 If non-@code{nil}, @code{nnmh} will go to ridiculous lengths to make
14673 sure that the articles in the folder are actually what Gnus thinks they
14674 are. It will check date stamps and stat everything in sight, so
14675 setting this to @code{t} will mean a serious slow-down. If you never
14676 use anything but Gnus to read the @code{nnmh} articles, you do not have
14677 to set this variable to @code{t}. The default is @code{nil}.
14682 @subsubsection Maildir
14686 @code{nnmaildir} stores mail in the maildir format, with each maildir
14687 corresponding to a group in Gnus. This format is documented here:
14688 @uref{http://cr.yp.to/proto/maildir.html} and here:
14689 @uref{http://www.qmail.org/man/man5/maildir.html}. nnmaildir also
14690 stores extra information in the @file{.nnmaildir/} directory within a
14693 Maildir format was designed to allow concurrent deliveries and
14694 reading, without needing locks. With other backends, you would have
14695 your mail delivered to a spool of some kind, and then you would
14696 configure Gnus to split mail from that spool into your groups. You
14697 can still do that with nnmaildir, but the more common configuration is
14698 to have your mail delivered directly to the maildirs that appear as
14701 nnmaildir is designed to be perfectly reliable: @kbd{C-g} will never
14702 corrupt its data in memory, and @code{SIGKILL} will never corrupt its
14703 data in the filesystem.
14705 nnmaildir stores article marks and NOV data in each maildir. So you
14706 can copy a whole maildir from one Gnus setup to another, and you will
14709 Virtual server settings:
14713 For each of your nnmaildir servers (it's very unlikely that you'd need
14714 more than one), you need to create a directory and populate it with
14715 maildirs or symlinks to maildirs (and nothing else; do not choose a
14716 directory already used for other purposes). Each maildir will be
14717 represented in Gnus as a newsgroup on that server; the filename of the
14718 symlink will be the name of the group. Any filenames in the directory
14719 starting with `.' are ignored. The directory is scanned when you
14720 first start Gnus, and each time you type @kbd{g} in the group buffer;
14721 if any maildirs have been removed or added, nnmaildir notices at these
14724 The value of the @code{directory} parameter should be a Lisp form
14725 which is processed by @code{eval} and @code{expand-file-name} to get
14726 the path of the directory for this server. The form is @code{eval}ed
14727 only when the server is opened; the resulting string is used until the
14728 server is closed. (If you don't know about forms and @code{eval},
14729 don't worry - a simple string will work.) This parameter is not
14730 optional; you must specify it. I don't recommend using
14731 @code{"~/Mail"} or a subdirectory of it; several other parts of Gnus
14732 use that directory by default for various things, and may get confused
14733 if nnmaildir uses it too. @code{"~/.nnmaildir"} is a typical value.
14735 @item target-prefix
14736 This should be a Lisp form which is processed by @code{eval} and
14737 @code{expand-file-name}. The form is @code{eval}ed only when the
14738 server is opened; the resulting string is used until the server is
14741 When you create a group on an nnmaildir server, the maildir is created
14742 with @code{target-prefix} prepended to its name, and a symlink
14743 pointing to that maildir is created, named with the plain group name.
14744 So if @code{directory} is @code{"~/.nnmaildir"} and
14745 @code{target-prefix} is @code{"../maildirs/"}, then when you create
14746 the group @code{foo}, nnmaildir will create
14747 @file{~/.nnmaildir/../maildirs/foo} as a maildir, and will create
14748 @file{~/.nnmaildir/foo} as a symlink pointing to
14749 @file{../maildirs/foo}.
14751 You can set @code{target-prefix} to a string without any slashes to
14752 create both maildirs and symlinks in the same @code{directory}; in
14753 this case, any maildirs found in @code{directory} whose names start
14754 with @code{target-prefix} will not be listed as groups (but the
14755 symlinks pointing to them will be).
14757 As a special case, if @code{target-prefix} is @code{""} (the default),
14758 then when you create a group, the maildir will be created in
14759 @code{directory} without a corresponding symlink. Beware that you
14760 cannot use @code{gnus-group-delete-group} on such groups without the
14761 @code{force} argument.
14763 @item directory-files
14764 This should be a function with the same interface as
14765 @code{directory-files} (such as @code{directory-files} itself). It is
14766 used to scan the server's @code{directory} for maildirs. This
14767 parameter is optional; the default is
14768 @code{nnheader-directory-files-safe} if
14769 @code{nnheader-directory-files-is-safe} is @code{nil}, and
14770 @code{directory-files} otherwise.
14771 (@code{nnheader-directory-files-is-safe} is checked only once when the
14772 server is opened; if you want to check it each time the directory is
14773 scanned, you'll have to provide your own function that does that.)
14776 If non-@code{nil}, then after scanning for new mail in the group
14777 maildirs themselves as usual, this server will also incorporate mail
14778 the conventional Gnus way, from @code{mail-sources} according to
14779 @code{nnmail-split-methods} or @code{nnmail-split-fancy}. The default
14780 value is @code{nil}.
14782 Do @emph{not} use the same maildir both in @code{mail-sources} and as
14783 an nnmaildir group. The results might happen to be useful, but that
14784 would be by chance, not by design, and the results might be different
14785 in the future. If your split rules create new groups, remember to
14786 supply a @code{create-directory} server parameter.
14789 @subsubsection Group parameters
14791 nnmaildir uses several group parameters. It's safe to ignore all
14792 this; the default behavior for nnmaildir is the same as the default
14793 behavior for other mail backends: articles are deleted after one week,
14794 etc. Except for the expiry parameters, all this functionality is
14795 unique to nnmaildir, so you can ignore it if you're just trying to
14796 duplicate the behavior you already have with another backend.
14798 If the value of any of these parameters is a vector, the first element
14799 is evaluated as a Lisp form and the result is used, rather than the
14800 original value. If the value is not a vector, the value itself is
14801 evaluated as a Lisp form. (This is why these parameters use names
14802 different from those of other, similar parameters supported by other
14803 backends: they have different, though similar, meanings.) (For
14804 numbers, strings, @code{nil}, and @code{t}, you can ignore the
14805 @code{eval} business again; for other values, remember to use an extra
14806 quote and wrap the value in a vector when appropriate.)
14810 An integer specifying the minimum age, in seconds, of an article before
14811 it will be expired, or the symbol @code{never} to specify that
14812 articles should never be expired. If this parameter is not set,
14813 nnmaildir falls back to the usual
14814 @code{nnmail-expiry-wait}(@code{-function}) variables (overridable by
14815 the @code{expiry-wait}(@code{-function}) group parameters. If you
14816 wanted a value of 3 days, you could use something like @code{[(* 3 24
14817 60 60)]}; nnmaildir will evaluate the form and use the result. An
14818 article's age is measured starting from the article file's
14819 modification time. Normally, this is the same as the article's
14820 delivery time, but editing an article makes it younger. Moving an
14821 article (other than via expiry) may also make an article younger.
14824 If this is set to a string (a full Gnus group name, like
14825 @code{"backend+server.address.string:group.name"}), and if it is not
14826 the name of the same group that the parameter belongs to, then
14827 articles will be moved to the specified group during expiry before
14828 being deleted. @emph{If this is set to an nnmaildir group, the
14829 article will be just as old in the destination group as it was in the
14830 source group.} So be careful with @code{expire-age} in the
14831 destination group. If this is set to the name of the same group that
14832 the parameter belongs to, then the article is not expired at all. If
14833 you use the vector form, the first element is evaluated once for each
14834 article. So that form can refer to
14835 @code{nnmaildir-article-file-name}, etc., to decide where to put the
14836 article. @emph{If this parameter is not set, nnmaildir does not fall
14837 back to the @code{expiry-target} group parameter or the
14838 @code{nnmail-expiry-target} variable.}
14841 If this is set to @code{t}, nnmaildir will treat the articles in this
14842 maildir as read-only. This means: articles are not renamed from
14843 @file{new/} into @file{cur/}; articles are only found in @file{new/},
14844 not @file{cur/}; articles are never deleted; articles cannot be
14845 edited. @file{new/} is expected to be a symlink to the @file{new/}
14846 directory of another maildir - e.g., a system-wide mailbox containing
14847 a mailing list of common interest. Everything in the maildir outside
14848 @file{new/} is @emph{not} treated as read-only, so for a shared
14849 mailbox, you do still need to set up your own maildir (or have write
14850 permission to the shared mailbox); your maildir just won't contain
14851 extra copies of the articles.
14853 @item directory-files
14854 A function with the same interface as @code{directory-files}. It is
14855 used to scan the directories in the maildir corresponding to this
14856 group to find articles. The default is the function specified by the
14857 server's @code{directory-files} parameter.
14859 @item distrust-Lines:
14860 If non-@code{nil}, nnmaildir will always count the lines of an
14861 article, rather than use the @code{Lines:} header field. If
14862 @code{nil}, the header field will be used if present.
14865 A list of mark symbols, such as
14866 @code{['(read expire)]}. Whenever Gnus asks nnmaildir for
14867 article marks, nnmaildir will say that all articles have these
14868 marks, regardless of whether the marks stored in the filesystem
14869 say so. This is a proof-of-concept feature that will probably be
14870 removed eventually; it ought to be done in Gnus proper, or
14871 abandoned if it's not worthwhile.
14874 A list of mark symbols, such as @code{['(tick expire)]}. Whenever
14875 Gnus asks nnmaildir for article marks, nnmaildir will say that no
14876 articles have these marks, regardless of whether the marks stored in
14877 the filesystem say so. @code{never-marks} overrides
14878 @code{always-marks}. This is a proof-of-concept feature that will
14879 probably be removed eventually; it ought to be done in Gnus proper, or
14880 abandoned if it's not worthwhile.
14882 @item nov-cache-size
14883 An integer specifying the size of the NOV memory cache. To speed
14884 things up, nnmaildir keeps NOV data in memory for a limited number of
14885 articles in each group. (This is probably not worthwhile, and will
14886 probably be removed in the future.) This parameter's value is noticed
14887 only the first time a group is seen after the server is opened - i.e.,
14888 when you first start Gnus, typically. The NOV cache is never resized
14889 until the server is closed and reopened. The default is an estimate
14890 of the number of articles that would be displayed in the summary
14891 buffer: a count of articles that are either marked with @code{tick} or
14892 not marked with @code{read}, plus a little extra.
14895 @subsubsection Article identification
14896 Articles are stored in the @file{cur/} subdirectory of each maildir.
14897 Each article file is named like @code{uniq:info}, where @code{uniq}
14898 contains no colons. nnmaildir ignores, but preserves, the
14899 @code{:info} part. (Other maildir readers typically use this part of
14900 the filename to store marks.) The @code{uniq} part uniquely
14901 identifies the article, and is used in various places in the
14902 @file{.nnmaildir/} subdirectory of the maildir to store information
14903 about the corresponding article. The full pathname of an article is
14904 available in the variable @code{nnmaildir-article-file-name} after you
14905 request the article in the summary buffer.
14907 @subsubsection NOV data
14908 An article identified by @code{uniq} has its NOV data (used to
14909 generate lines in the summary buffer) stored in
14910 @code{.nnmaildir/nov/uniq}. There is no
14911 @code{nnmaildir-generate-nov-databases} function. (There isn't much
14912 need for it - an article's NOV data is updated automatically when the
14913 article or @code{nnmail-extra-headers} has changed.) You can force
14914 nnmaildir to regenerate the NOV data for a single article simply by
14915 deleting the corresponding NOV file, but @emph{beware}: this will also
14916 cause nnmaildir to assign a new article number for this article, which
14917 may cause trouble with @code{seen} marks, the Agent, and the cache.
14919 @subsubsection Article marks
14920 An article identified by @code{uniq} is considered to have the mark
14921 @code{flag} when the file @file{.nnmaildir/marks/flag/uniq} exists.
14922 When Gnus asks nnmaildir for a group's marks, nnmaildir looks for such
14923 files and reports the set of marks it finds. When Gnus asks nnmaildir
14924 to store a new set of marks, nnmaildir creates and deletes the
14925 corresponding files as needed. (Actually, rather than create a new
14926 file for each mark, it just creates hard links to
14927 @file{.nnmaildir/markfile}, to save inodes.)
14929 You can invent new marks by creating a new directory in
14930 @file{.nnmaildir/marks/}. You can tar up a maildir and remove it from
14931 your server, untar it later, and keep your marks. You can add and
14932 remove marks yourself by creating and deleting mark files. If you do
14933 this while Gnus is running and your nnmaildir server is open, it's
14934 best to exit all summary buffers for nnmaildir groups and type @kbd{s}
14935 in the group buffer first, and to type @kbd{g} or @kbd{M-g} in the
14936 group buffer afterwards. Otherwise, Gnus might not pick up the
14937 changes, and might undo them.
14941 @subsubsection Mail Folders
14943 @cindex mbox folders
14944 @cindex mail folders
14946 @code{nnfolder} is a back end for storing each mail group in a separate
14947 file. Each file is in the standard Un*x mbox format. @code{nnfolder}
14948 will add extra headers to keep track of article numbers and arrival
14951 @cindex self contained nnfolder servers
14953 When the marks file is used (which it is by default), @code{nnfolder}
14954 servers have the property that you may backup them using @code{tar} or
14955 similar, and later be able to restore them into Gnus (by adding the
14956 proper @code{nnfolder} server) and have all your marks be preserved.
14957 Marks for a group is usually stored in a file named as the mbox file
14958 with @code{.mrk} concatenated to it (but see
14959 @code{nnfolder-marks-file-suffix}) within the @code{nnfolder} directory.
14960 Individual @code{nnfolder} groups are also possible to backup, use
14961 @kbd{G m} to restore the group (after restoring the backup into the
14962 @code{nnfolder} directory).
14964 Virtual server settings:
14967 @item nnfolder-directory
14968 @vindex nnfolder-directory
14969 All the @code{nnfolder} mail boxes will be stored under this directory.
14970 The default is the value of @code{message-directory} (whose default is
14973 @item nnfolder-active-file
14974 @vindex nnfolder-active-file
14975 The name of the active file. The default is @file{~/Mail/active}.
14977 @item nnfolder-newsgroups-file
14978 @vindex nnfolder-newsgroups-file
14979 The name of the group descriptions file. @xref{Newsgroups File
14980 Format}. The default is @file{~/Mail/newsgroups}
14982 @item nnfolder-get-new-mail
14983 @vindex nnfolder-get-new-mail
14984 If non-@code{nil}, @code{nnfolder} will read incoming mail. The default
14987 @item nnfolder-save-buffer-hook
14988 @vindex nnfolder-save-buffer-hook
14989 @cindex backup files
14990 Hook run before saving the folders. Note that Emacs does the normal
14991 backup renaming of files even with the @code{nnfolder} buffers. If you
14992 wish to switch this off, you could say something like the following in
14993 your @file{.emacs} file:
14996 (defun turn-off-backup ()
14997 (set (make-local-variable 'backup-inhibited) t))
14999 (add-hook 'nnfolder-save-buffer-hook 'turn-off-backup)
15002 @item nnfolder-delete-mail-hook
15003 @vindex nnfolder-delete-mail-hook
15004 Hook run in a buffer narrowed to the message that is to be deleted.
15005 This function can be used to copy the message to somewhere else, or to
15006 extract some information from it before removing it.
15008 @item nnfolder-nov-is-evil
15009 @vindex nnfolder-nov-is-evil
15010 If non-@code{nil}, this back end will ignore any @sc{nov} files. The
15011 default is @code{nil}.
15013 @item nnfolder-nov-file-suffix
15014 @vindex nnfolder-nov-file-suffix
15015 The extension for @sc{nov} files. The default is @file{.nov}.
15017 @item nnfolder-nov-directory
15018 @vindex nnfolder-nov-directory
15019 The directory where the @sc{nov} files should be stored. If nil,
15020 @code{nnfolder-directory} is used.
15022 @item nnfolder-marks-is-evil
15023 @vindex nnfolder-marks-is-evil
15024 If non-@code{nil}, this back end will ignore any @sc{marks} files. The
15025 default is @code{nil}.
15027 @item nnfolder-marks-file-suffix
15028 @vindex nnfolder-marks-file-suffix
15029 The extension for @sc{marks} files. The default is @file{.mrk}.
15031 @item nnfolder-marks-directory
15032 @vindex nnfolder-marks-directory
15033 The directory where the @sc{marks} files should be stored. If nil,
15034 @code{nnfolder-directory} is used.
15039 @findex nnfolder-generate-active-file
15040 @kindex M-x nnfolder-generate-active-file
15041 If you have lots of @code{nnfolder}-like files you'd like to read with
15042 @code{nnfolder}, you can use the @kbd{M-x nnfolder-generate-active-file}
15043 command to make @code{nnfolder} aware of all likely files in
15044 @code{nnfolder-directory}. This only works if you use long file names,
15047 @node Comparing Mail Back Ends
15048 @subsubsection Comparing Mail Back Ends
15050 First, just for terminology, the @dfn{back end} is the common word for a
15051 low-level access method---a transport, if you will, by which something
15052 is acquired. The sense is that one's mail has to come from somewhere,
15053 and so selection of a suitable back end is required in order to get that
15054 mail within spitting distance of Gnus.
15056 The same concept exists for Usenet itself: Though access to articles is
15057 typically done by @sc{nntp} these days, once upon a midnight dreary, everyone
15058 in the world got at Usenet by running a reader on the machine where the
15059 articles lay (the machine which today we call an @sc{nntp} server), and
15060 access was by the reader stepping into the articles' directory spool
15061 area directly. One can still select between either the @code{nntp} or
15062 @code{nnspool} back ends, to select between these methods, if one happens
15063 actually to live on the server (or can see its spool directly, anyway,
15066 The goal in selecting a mail back end is to pick one which
15067 simultaneously represents a suitable way of dealing with the original
15068 format plus leaving mail in a form that is convenient to use in the
15069 future. Here are some high and low points on each:
15074 UNIX systems have historically had a single, very common, and well-
15075 defined format. All messages arrive in a single @dfn{spool file}, and
15076 they are delineated by a line whose regular expression matches
15077 @samp{^From_}. (My notational use of @samp{_} is to indicate a space,
15078 to make it clear in this instance that this is not the RFC-specified
15079 @samp{From:} header.) Because Emacs and therefore Gnus emanate
15080 historically from the Unix environment, it is simplest if one does not
15081 mess a great deal with the original mailbox format, so if one chooses
15082 this back end, Gnus' primary activity in getting mail from the real spool
15083 area to Gnus' preferred directory is simply to copy it, with no
15084 (appreciable) format change in the process. It is the ``dumbest'' way
15085 to move mail into availability in the Gnus environment. This makes it
15086 fast to move into place, but slow to parse, when Gnus has to look at
15091 Once upon a time, there was the DEC-10 and DEC-20, running operating
15092 systems called TOPS and related things, and the usual (only?) mail
15093 reading environment was a thing called Babyl. I don't know what format
15094 was used for mail landing on the system, but Babyl had its own internal
15095 format to which mail was converted, primarily involving creating a
15096 spool-file-like entity with a scheme for inserting Babyl-specific
15097 headers and status bits above the top of each message in the file.
15098 RMAIL was Emacs' first mail reader, it was written by Richard Stallman,
15099 and Stallman came out of that TOPS/Babyl environment, so he wrote RMAIL
15100 to understand the mail files folks already had in existence. Gnus (and
15101 VM, for that matter) continue to support this format because it's
15102 perceived as having some good qualities in those mailer-specific
15103 headers/status bits stuff. RMAIL itself still exists as well, of
15104 course, and is still maintained by Stallman.
15106 Both of the above forms leave your mail in a single file on your
15107 file system, and they must parse that entire file each time you take a
15112 @code{nnml} is the back end which smells the most as though you were
15113 actually operating with an @code{nnspool}-accessed Usenet system. (In
15114 fact, I believe @code{nnml} actually derived from @code{nnspool} code,
15115 lo these years ago.) One's mail is taken from the original spool file,
15116 and is then cut up into individual message files, 1:1. It maintains a
15117 Usenet-style active file (analogous to what one finds in an INN- or
15118 CNews-based news system in (for instance) @file{/var/lib/news/active},
15119 or what is returned via the @samp{NNTP LIST} verb) and also creates
15120 @dfn{overview} files for efficient group entry, as has been defined for
15121 @sc{nntp} servers for some years now. It is slower in mail-splitting,
15122 due to the creation of lots of files, updates to the @code{nnml} active
15123 file, and additions to overview files on a per-message basis, but it is
15124 extremely fast on access because of what amounts to the indexing support
15125 provided by the active file and overviews.
15127 @code{nnml} costs @dfn{inodes} in a big way; that is, it soaks up the
15128 resource which defines available places in the file system to put new
15129 files. Sysadmins take a dim view of heavy inode occupation within
15130 tight, shared file systems. But if you live on a personal machine where
15131 the file system is your own and space is not at a premium, @code{nnml}
15134 It is also problematic using this back end if you are living in a
15135 FAT16-based Windows world, since much space will be wasted on all these
15140 The Rand MH mail-reading system has been around UNIX systems for a very
15141 long time; it operates by splitting one's spool file of messages into
15142 individual files, but with little or no indexing support -- @code{nnmh}
15143 is considered to be semantically equivalent to ``@code{nnml} without
15144 active file or overviews''. This is arguably the worst choice, because
15145 one gets the slowness of individual file creation married to the
15146 slowness of access parsing when learning what's new in one's groups.
15150 Basically the effect of @code{nnfolder} is @code{nnmbox} (the first
15151 method described above) on a per-group basis. That is, @code{nnmbox}
15152 itself puts @emph{all} one's mail in one file; @code{nnfolder} provides a
15153 little bit of optimization to this so that each of one's mail groups has
15154 a Unix mail box file. It's faster than @code{nnmbox} because each group
15155 can be parsed separately, and still provides the simple Unix mail box
15156 format requiring minimal effort in moving the mail around. In addition,
15157 it maintains an ``active'' file making it much faster for Gnus to figure
15158 out how many messages there are in each separate group.
15160 If you have groups that are expected to have a massive amount of
15161 messages, @code{nnfolder} is not the best choice, but if you receive
15162 only a moderate amount of mail, @code{nnfolder} is probably the most
15163 friendly mail back end all over.
15167 For configuring expiry and other things, @code{nnmaildir} uses
15168 incompatible group parameters, slightly different from those of other
15171 @code{nnmaildir} is largely similar to @code{nnml}, with some notable
15172 differences. Each message is stored in a separate file, but the
15173 filename is unrelated to the article number in Gnus. @code{nnmaildir}
15174 also stores the equivalent of @code{nnml}'s overview files in one file
15175 per article, so it uses about twice as many inodes as @code{nnml}. (Use
15176 @code{df -i} to see how plentiful your inode supply is.) If this slows
15177 you down or takes up very much space, consider switching to ReiserFS
15178 (@uref{http://www.namesys.com/}) or another non-block-structured
15181 Since maildirs don't require locking for delivery, the maildirs you use
15182 as groups can also be the maildirs your mail is directly delivered to.
15183 This means you can skip Gnus's mail splitting if your mail is already
15184 organized into different mailboxes during delivery. A @code{directory}
15185 entry in @code{mail-sources} would have a similar effect, but would
15186 require one set of mailboxes for spooling deliveries (in mbox format,
15187 thus damaging message bodies), and another set to be used as groups (in
15188 whatever format you like). A maildir has a built-in spool, in the
15189 @code{new/} subdirectory. Beware that currently, mail moved from
15190 @code{new/} to @code{cur/} instead of via mail splitting will not
15191 undergo treatment such as duplicate checking.
15193 @code{nnmaildir} stores article marks for a given group in the
15194 corresponding maildir, in a way designed so that it's easy to manipulate
15195 them from outside Gnus. You can tar up a maildir, unpack it somewhere
15196 else, and still have your marks. @code{nnml} also stores marks, but
15197 it's not as easy to work with them from outside Gnus as with
15200 @code{nnmaildir} uses a significant amount of memory to speed things up.
15201 (It keeps in memory some of the things that @code{nnml} stores in files
15202 and that @code{nnmh} repeatedly parses out of message files.) If this
15203 is a problem for you, you can set the @code{nov-cache-size} group
15204 parameter to something small (0 would probably not work, but 1 probably
15205 would) to make it use less memory. This caching will probably be
15206 removed in the future.
15208 Startup is likely to be slower with @code{nnmaildir} than with other
15209 back ends. Everything else is likely to be faster, depending in part
15210 on your file system.
15212 @code{nnmaildir} does not use @code{nnoo}, so you cannot use @code{nnoo}
15213 to write an @code{nnmaildir}-derived back end.
15218 @node Browsing the Web
15219 @section Browsing the Web
15221 @cindex browsing the web
15225 Web-based discussion forums are getting more and more popular. On many
15226 subjects, the web-based forums have become the most important forums,
15227 eclipsing the importance of mailing lists and news groups. The reason
15228 is easy to understand---they are friendly to new users; you just point
15229 and click, and there's the discussion. With mailing lists, you have to
15230 go through a cumbersome subscription procedure, and most people don't
15231 even know what a news group is.
15233 The problem with this scenario is that web browsers are not very good at
15234 being newsreaders. They do not keep track of what articles you've read;
15235 they do not allow you to score on subjects you're interested in; they do
15236 not allow off-line browsing; they require you to click around and drive
15237 you mad in the end.
15239 So---if web browsers suck at reading discussion forums, why not use Gnus
15242 Gnus has been getting a bit of a collection of back ends for providing
15243 interfaces to these sources.
15247 * Web Searches:: Creating groups from articles that match a string.
15248 * Slashdot:: Reading the Slashdot comments.
15249 * Ultimate:: The Ultimate Bulletin Board systems.
15250 * Web Archive:: Reading mailing list archived on web.
15251 * RSS:: Reading RDF site summary.
15252 * Customizing w3:: Doing stuff to Emacs/w3 from Gnus.
15255 All the web sources require Emacs/w3 and the url library to work.
15257 The main caveat with all these web sources is that they probably won't
15258 work for a very long time. Gleaning information from the @sc{html} data
15259 is guesswork at best, and when the layout is altered, the Gnus back end
15260 will fail. If you have reasonably new versions of these back ends,
15261 though, you should be ok.
15263 One thing all these Web methods have in common is that the Web sources
15264 are often down, unavailable or just plain too slow to be fun. In those
15265 cases, it makes a lot of sense to let the Gnus Agent (@pxref{Gnus
15266 Unplugged}) handle downloading articles, and then you can read them at
15267 leisure from your local disk. No more World Wide Wait for you.
15269 @node Archiving Mail
15270 @subsection Archiving Mail
15271 @cindex archiving mail
15272 @cindex backup of mail
15274 Some of the back ends, notably @code{nnml}, @code{nnfolder}, and
15275 @code{nnmaildir}, now actually store the article marks with each group.
15276 For these servers, archiving and restoring a group while preserving
15277 marks is fairly simple.
15279 (Preserving the group level and group parameters as well still
15280 requires ritual dancing and sacrifices to the @file{.newsrc.eld} deity
15283 To archive an entire @code{nnml}, @code{nnfolder}, or @code{nnmaildir}
15284 server, take a recursive copy of the server directory. There is no need
15285 to shut down Gnus, so archiving may be invoked by @code{cron} or
15286 similar. You restore the data by restoring the directory tree, and
15287 adding a server definition pointing to that directory in Gnus. The
15288 @ref{Article Backlog}, @ref{Asynchronous Fetching} and other things
15289 might interfere with overwriting data, so you may want to shut down Gnus
15290 before you restore the data.
15292 It is also possible to archive individual @code{nnml},
15293 @code{nnfolder}, or @code{nnmaildir} groups, while preserving marks.
15294 For @code{nnml} or @code{nnmaildir}, you copy all files in the group's
15295 directory. For @code{nnfolder} you need to copy both the base folder
15296 file itself (@file{FOO}, say), and the marks file (@file{FOO.mrk} in
15297 this example). Restoring the group is done with @kbd{G m} from the Group
15298 buffer. The last step makes Gnus notice the new directory.
15299 @code{nnmaildir} notices the new directory automatically, so @kbd{G m}
15300 is unnecessary in that case.
15303 @subsection Web Searches
15308 @cindex Usenet searches
15309 @cindex searching the Usenet
15311 It's, like, too neat to search the Usenet for articles that match a
15312 string, but it, like, totally @emph{sucks}, like, totally, to use one of
15313 those, like, Web browsers, and you, like, have to, rilly, like, look at
15314 the commercials, so, like, with Gnus you can do @emph{rad}, rilly,
15315 searches without having to use a browser.
15317 The @code{nnweb} back end allows an easy interface to the mighty search
15318 engine. You create an @code{nnweb} group, enter a search pattern, and
15319 then enter the group and read the articles like you would any normal
15320 group. The @kbd{G w} command in the group buffer (@pxref{Foreign
15321 Groups}) will do this in an easy-to-use fashion.
15323 @code{nnweb} groups don't really lend themselves to being solid
15324 groups---they have a very fleeting idea of article numbers. In fact,
15325 each time you enter an @code{nnweb} group (not even changing the search
15326 pattern), you are likely to get the articles ordered in a different
15327 manner. Not even using duplicate suppression (@pxref{Duplicate
15328 Suppression}) will help, since @code{nnweb} doesn't even know the
15329 @code{Message-ID} of the articles before reading them using some search
15330 engines (Google, for instance). The only possible way to keep track
15331 of which articles you've read is by scoring on the @code{Date}
15332 header---mark all articles posted before the last date you read the
15335 If the search engine changes its output substantially, @code{nnweb}
15336 won't be able to parse it and will fail. One could hardly fault the Web
15337 providers if they were to do this---their @emph{raison d'être} is to
15338 make money off of advertisements, not to provide services to the
15339 community. Since @code{nnweb} washes the ads off all the articles, one
15340 might think that the providers might be somewhat miffed. We'll see.
15342 You must have the @code{url} and @code{w3} package installed to be able
15343 to use @code{nnweb}.
15345 Virtual server variables:
15350 What search engine type is being used. The currently supported types
15351 are @code{google}, @code{dejanews}, and @code{gmane}. Note that
15352 @code{dejanews} is an alias to @code{google}.
15355 @vindex nnweb-search
15356 The search string to feed to the search engine.
15358 @item nnweb-max-hits
15359 @vindex nnweb-max-hits
15360 Advisory maximum number of hits per search to display. The default is
15363 @item nnweb-type-definition
15364 @vindex nnweb-type-definition
15365 Type-to-definition alist. This alist says what @code{nnweb} should do
15366 with the various search engine types. The following elements must be
15371 Function to decode the article and provide something that Gnus
15375 Function to create an article number to message header and URL alist.
15378 Function to send the search string to the search engine.
15381 The address the aforementioned function should send the search string
15385 Format string URL to fetch an article by @code{Message-ID}.
15392 @subsection Slashdot
15396 Slashdot (@uref{http://slashdot.org/}) is a popular news site, with
15397 lively discussion following the news articles. @code{nnslashdot} will
15398 let you read this forum in a convenient manner.
15400 The easiest way to read this source is to put something like the
15401 following in your @file{~/.gnus.el} file:
15404 (setq gnus-secondary-select-methods
15405 '((nnslashdot "")))
15408 This will make Gnus query the @code{nnslashdot} back end for new comments
15409 and groups. The @kbd{F} command will subscribe each new news article as
15410 a new Gnus group, and you can read the comments by entering these
15411 groups. (Note that the default subscription method is to subscribe new
15412 groups as zombies. Other methods are available (@pxref{Subscription
15415 If you want to remove an old @code{nnslashdot} group, the @kbd{G DEL}
15416 command is the most handy tool (@pxref{Foreign Groups}).
15418 When following up to @code{nnslashdot} comments (or posting new
15419 comments), some light @sc{html}izations will be performed. In
15420 particular, text quoted with @samp{> } will be quoted with
15421 @code{blockquote} instead, and signatures will have @code{br} added to
15422 the end of each line. Other than that, you can just write @sc{html}
15423 directly into the message buffer. Note that Slashdot filters out some
15426 The following variables can be altered to change its behavior:
15429 @item nnslashdot-threaded
15430 Whether @code{nnslashdot} should display threaded groups or not. The
15431 default is @code{t}. To be able to display threads, @code{nnslashdot}
15432 has to retrieve absolutely all comments in a group upon entry. If a
15433 threaded display is not required, @code{nnslashdot} will only retrieve
15434 the comments that are actually wanted by the user. Threading is nicer,
15435 but much, much slower than unthreaded.
15437 @item nnslashdot-login-name
15438 @vindex nnslashdot-login-name
15439 The login name to use when posting.
15441 @item nnslashdot-password
15442 @vindex nnslashdot-password
15443 The password to use when posting.
15445 @item nnslashdot-directory
15446 @vindex nnslashdot-directory
15447 Where @code{nnslashdot} will store its files. The default is
15448 @file{~/News/slashdot/}.
15450 @item nnslashdot-active-url
15451 @vindex nnslashdot-active-url
15452 The @sc{url} format string that will be used to fetch the information on
15453 news articles and comments. The default is
15454 @samp{http://slashdot.org/search.pl?section=&min=%d}.
15456 @item nnslashdot-comments-url
15457 @vindex nnslashdot-comments-url
15458 The @sc{url} format string that will be used to fetch comments. The
15460 @samp{http://slashdot.org/comments.pl?sid=%s&threshold=%d&commentsort=%d&mode=flat&startat=%d}.
15462 @item nnslashdot-article-url
15463 @vindex nnslashdot-article-url
15464 The @sc{url} format string that will be used to fetch the news article. The
15466 @samp{http://slashdot.org/article.pl?sid=%s&mode=nocomment}.
15468 @item nnslashdot-threshold
15469 @vindex nnslashdot-threshold
15470 The score threshold. The default is -1.
15472 @item nnslashdot-group-number
15473 @vindex nnslashdot-group-number
15474 The number of old groups, in addition to the ten latest, to keep
15475 updated. The default is 0.
15482 @subsection Ultimate
15484 @cindex Ultimate Bulletin Board
15486 The Ultimate Bulletin Board (@uref{http://www.ultimatebb.com/}) is
15487 probably the most popular Web bulletin board system used. It has a
15488 quite regular and nice interface, and it's possible to get the
15489 information Gnus needs to keep groups updated.
15491 The easiest way to get started with @code{nnultimate} is to say
15492 something like the following in the group buffer: @kbd{B nnultimate RET
15493 http://www.tcj.com/messboard/ubbcgi/ RET}. (Substitute the @sc{url}
15494 (not including @samp{Ultimate.cgi} or the like at the end) for a forum
15495 you're interested in; there's quite a list of them on the Ultimate web
15496 site.) Then subscribe to the groups you're interested in from the
15497 server buffer, and read them from the group buffer.
15499 The following @code{nnultimate} variables can be altered:
15502 @item nnultimate-directory
15503 @vindex nnultimate-directory
15504 The directory where @code{nnultimate} stores its files. The default is
15505 @file{~/News/ultimate/}.
15510 @subsection Web Archive
15512 @cindex Web Archive
15514 Some mailing lists only have archives on Web servers, such as
15515 @uref{http://www.egroups.com/} and
15516 @uref{http://www.mail-archive.com/}. It has a quite regular and nice
15517 interface, and it's possible to get the information Gnus needs to keep
15520 @findex gnus-group-make-warchive-group
15521 The easiest way to get started with @code{nnwarchive} is to say
15522 something like the following in the group buffer: @kbd{M-x
15523 gnus-group-make-warchive-group RET an_egroup RET egroups RET
15524 www.egroups.com RET your@@email.address RET}. (Substitute the
15525 @sc{an_egroup} with the mailing list you subscribed, the
15526 @sc{your@@email.address} with your email address.), or to browse the
15527 back end by @kbd{B nnwarchive RET mail-archive RET}.
15529 The following @code{nnwarchive} variables can be altered:
15532 @item nnwarchive-directory
15533 @vindex nnwarchive-directory
15534 The directory where @code{nnwarchive} stores its files. The default is
15535 @file{~/News/warchive/}.
15537 @item nnwarchive-login
15538 @vindex nnwarchive-login
15539 The account name on the web server.
15541 @item nnwarchive-passwd
15542 @vindex nnwarchive-passwd
15543 The password for your account on the web server.
15551 Some sites have RDF site summary (RSS)
15552 @uref{http://purl.org/rss/1.0/spec}. It has a quite regular and nice
15553 interface, and it's possible to get the information Gnus needs to keep
15556 The easiest way to get started with @code{nnrss} is to say something
15557 like the following in the group buffer: @kbd{B nnrss RET RET}, then
15560 The following @code{nnrss} variables can be altered:
15563 @item nnrss-directory
15564 @vindex nnrss-directory
15565 The directory where @code{nnrss} stores its files. The default is
15566 @file{~/News/rss/}.
15570 The following code may be helpful, if you want to show the description in
15571 the summary buffer.
15574 (add-to-list 'nnmail-extra-headers nnrss-description-field)
15575 (setq gnus-summary-line-format "%U%R%z%I%(%[%4L: %-15,15f%]%) %s%uX\n")
15577 (defun gnus-user-format-function-X (header)
15579 (assq nnrss-description-field (mail-header-extra header))))
15580 (if descr (concat "\n\t" (cdr descr)) "")))
15583 The following code may be useful to open an nnrss url directly from the
15586 (require 'browse-url)
15588 (defun browse-nnrss-url( arg )
15590 (let ((url (assq nnrss-url-field
15593 (assq (gnus-summary-article-number)
15594 gnus-newsgroup-data))))))
15597 (browse-url (cdr url))
15598 (gnus-summary-mark-as-read-forward 1))
15599 (gnus-summary-scroll-up arg))))
15601 (eval-after-load "gnus"
15602 #'(define-key gnus-summary-mode-map
15603 (kbd "<RET>") 'browse-nnrss-url))
15604 (add-to-list 'nnmail-extra-headers nnrss-url-field)
15607 @node Customizing w3
15608 @subsection Customizing w3
15614 Gnus uses the url library to fetch web pages and Emacs/w3 to display web
15615 pages. Emacs/w3 is documented in its own manual, but there are some
15616 things that may be more relevant for Gnus users.
15618 For instance, a common question is how to make Emacs/w3 follow links
15619 using the @code{browse-url} functions (which will call some external web
15620 browser like Netscape). Here's one way:
15623 (eval-after-load "w3"
15625 (fset 'w3-fetch-orig (symbol-function 'w3-fetch))
15626 (defun w3-fetch (&optional url target)
15627 (interactive (list (w3-read-url-with-default)))
15628 (if (eq major-mode 'gnus-article-mode)
15630 (w3-fetch-orig url target)))))
15633 Put that in your @file{.emacs} file, and hitting links in w3-rendered
15634 @sc{html} in the Gnus article buffers will use @code{browse-url} to
15643 @sc{imap} is a network protocol for reading mail (or news, or @dots{}),
15644 think of it as a modernized @sc{nntp}. Connecting to a @sc{imap}
15645 server is much similar to connecting to a news server, you just
15646 specify the network address of the server.
15648 @sc{imap} has two properties. First, @sc{imap} can do everything that
15649 POP can, it can hence be viewed as a POP++. Secondly, @sc{imap} is a
15650 mail storage protocol, similar to @sc{nntp} being a news storage
15651 protocol -- however, @sc{imap} offers more features than @sc{nntp}
15652 because news is more or less read-only whereas mail is read-write.
15654 If you want to use @sc{imap} as a POP++, use an imap entry in
15655 @code{mail-sources}. With this, Gnus will fetch mails from the
15656 @sc{imap} server and store them on the local disk. This is not the
15657 usage described in this section--@xref{Mail Sources}.
15659 If you want to use @sc{imap} as a mail storage protocol, use an nnimap
15660 entry in @code{gnus-secondary-select-methods}. With this, Gnus will
15661 manipulate mails stored on the @sc{imap} server. This is the kind of
15662 usage explained in this section.
15664 A server configuration in @file{~/.gnus.el} with a few @sc{imap} servers
15665 might look something like the following. (Note that for TLS/SSL, you
15666 need external programs and libraries, see below.)
15669 (setq gnus-secondary-select-methods
15670 '((nnimap "simpleserver") ; no special configuration
15671 ; perhaps a ssh port forwarded server:
15673 (nnimap-address "localhost")
15674 (nnimap-server-port 1430))
15675 ; a UW server running on localhost
15677 (nnimap-server-port 143)
15678 (nnimap-address "localhost")
15679 (nnimap-list-pattern ("INBOX" "mail/*")))
15680 ; anonymous public cyrus server:
15681 (nnimap "cyrus.andrew.cmu.edu"
15682 (nnimap-authenticator anonymous)
15683 (nnimap-list-pattern "archive.*")
15684 (nnimap-stream network))
15685 ; a ssl server on a non-standard port:
15687 (nnimap-address "vic20.somewhere.com")
15688 (nnimap-server-port 9930)
15689 (nnimap-stream ssl))))
15692 After defining the new server, you can subscribe to groups on the
15693 server using normal Gnus commands such as @kbd{U} in the Group Buffer
15694 (@pxref{Subscription Commands}) or via the Server Buffer
15695 (@pxref{Server Buffer}).
15697 The following variables can be used to create a virtual @code{nnimap}
15702 @item nnimap-address
15703 @vindex nnimap-address
15705 The address of the remote @sc{imap} server. Defaults to the virtual
15706 server name if not specified.
15708 @item nnimap-server-port
15709 @vindex nnimap-server-port
15710 Port on server to contact. Defaults to port 143, or 993 for TLS/SSL.
15712 Note that this should be an integer, example server specification:
15715 (nnimap "mail.server.com"
15716 (nnimap-server-port 4711))
15719 @item nnimap-list-pattern
15720 @vindex nnimap-list-pattern
15721 String or list of strings of mailboxes to limit available groups to.
15722 This is used when the server has very many mailboxes and you're only
15723 interested in a few -- some servers export your home directory via
15724 @sc{imap}, you'll probably want to limit the mailboxes to those in
15725 @file{~/Mail/*} then.
15727 The string can also be a cons of REFERENCE and the string as above, what
15728 REFERENCE is used for is server specific, but on the University of
15729 Washington server it's a directory that will be concatenated with the
15732 Example server specification:
15735 (nnimap "mail.server.com"
15736 (nnimap-list-pattern ("INBOX" "Mail/*" "alt.sex.*"
15737 ("~friend/Mail/" . "list/*"))))
15740 @item nnimap-stream
15741 @vindex nnimap-stream
15742 The type of stream used to connect to your server. By default, nnimap
15743 will detect and automatically use all of the below, with the exception
15744 of TLS/SSL. (@sc{imap} over TLS/SSL is being replaced by STARTTLS, which
15745 can be automatically detected, but it's not widely deployed yet.)
15747 Example server specification:
15750 (nnimap "mail.server.com"
15751 (nnimap-stream ssl))
15754 Please note that the value of @code{nnimap-stream} is a symbol!
15758 @dfn{gssapi:} Connect with GSSAPI (usually Kerberos 5). Requires the
15759 @samp{gsasl} or @samp{imtest} program.
15761 @dfn{kerberos4:} Connect with Kerberos 4. Requires the @samp{imtest} program.
15763 @dfn{starttls:} Connect via the STARTTLS extension (similar to
15764 TLS/SSL). Requires the external library @samp{starttls.el} and program
15767 @dfn{tls:} Connect through TLS. Requires GNUTLS (the program
15768 @samp{gnutls-cli}).
15770 @dfn{ssl:} Connect through SSL. Requires OpenSSL (the program
15771 @samp{openssl}) or SSLeay (@samp{s_client}).
15773 @dfn{shell:} Use a shell command to start @sc{imap} connection.
15775 @dfn{network:} Plain, TCP/IP network connection.
15778 @vindex imap-kerberos4-program
15779 The @samp{imtest} program is shipped with Cyrus IMAPD. If you're
15780 using @samp{imtest} from Cyrus IMAPD < 2.0.14 (which includes version
15781 1.5.x and 1.6.x) you need to frob @code{imap-process-connection-type}
15782 to make @code{imap.el} use a pty instead of a pipe when communicating
15783 with @samp{imtest}. You will then suffer from a line length
15784 restrictions on @sc{imap} commands, which might make Gnus seem to hang
15785 indefinitely if you have many articles in a mailbox. The variable
15786 @code{imap-kerberos4-program} contain parameters to pass to the imtest
15789 For TLS connection, the @code{gnutls-cli} program from GNUTLS is
15790 needed. It is available from
15791 @uref{http://www.gnu.org/software/gnutls/}.
15793 @vindex imap-gssapi-program
15794 This parameter specifies a list of command lines that invoke a GSSAPI
15795 authenticated IMAP stream in a subshell. They are tried sequentially
15796 until a connection is made, or the list has been exhausted. By
15797 default, @samp{gsasl} from GNU SASL, available from
15798 @uref{http://www.gnu.org/software/gsasl/}, and the @samp{imtest}
15799 program from Cyrus IMAPD (see @code{imap-kerberos4-program}), are
15802 @vindex imap-ssl-program
15803 For SSL connections, the OpenSSL program is available from
15804 @uref{http://www.openssl.org/}. OpenSSL was formerly known as SSLeay,
15805 and nnimap support it too - although the most recent versions of
15806 SSLeay, 0.9.x, are known to have serious bugs making it
15807 useless. Earlier versions, especially 0.8.x, of SSLeay are known to
15808 work. The variable @code{imap-ssl-program} contain parameters to pass
15811 @vindex imap-shell-program
15812 @vindex imap-shell-host
15813 For @sc{imap} connections using the @code{shell} stream, the variable
15814 @code{imap-shell-program} specify what program to call.
15816 @item nnimap-authenticator
15817 @vindex nnimap-authenticator
15819 The authenticator used to connect to the server. By default, nnimap
15820 will use the most secure authenticator your server is capable of.
15822 Example server specification:
15825 (nnimap "mail.server.com"
15826 (nnimap-authenticator anonymous))
15829 Please note that the value of @code{nnimap-authenticator} is a symbol!
15833 @dfn{gssapi:} GSSAPI (usually kerberos 5) authentication. Requires
15834 external program @code{gsasl} or @code{imtest}.
15836 @dfn{kerberos4:} Kerberos 4 authentication. Requires external program
15839 @dfn{digest-md5:} Encrypted username/password via DIGEST-MD5. Requires
15840 external library @code{digest-md5.el}.
15842 @dfn{cram-md5:} Encrypted username/password via CRAM-MD5.
15844 @dfn{login:} Plain-text username/password via LOGIN.
15846 @dfn{anonymous:} Login as `anonymous', supplying your email address as password.
15849 @item nnimap-expunge-on-close
15851 @vindex nnimap-expunge-on-close
15852 Unlike Parmenides the @sc{imap} designers has decided that things that
15853 doesn't exist actually does exist. More specifically, @sc{imap} has
15854 this concept of marking articles @code{Deleted} which doesn't actually
15855 delete them, and this (marking them @code{Deleted}, that is) is what
15856 nnimap does when you delete a article in Gnus (with @kbd{B DEL} or
15859 Since the articles aren't really removed when we mark them with the
15860 @code{Deleted} flag we'll need a way to actually delete them. Feel like
15861 running in circles yet?
15863 Traditionally, nnimap has removed all articles marked as @code{Deleted}
15864 when closing a mailbox but this is now configurable by this server
15867 The possible options are:
15872 The default behavior, delete all articles marked as ``Deleted'' when
15875 Never actually delete articles. Currently there is no way of showing
15876 the articles marked for deletion in nnimap, but other @sc{imap} clients
15877 may allow you to do this. If you ever want to run the EXPUNGE command
15878 manually, @xref{Expunging mailboxes}.
15880 When closing mailboxes, nnimap will ask if you wish to expunge deleted
15885 @item nnimap-importantize-dormant
15886 @vindex nnimap-importantize-dormant
15888 If non-nil (the default), marks dormant articles as ticked (as well),
15889 for other @sc{imap} clients. Within Gnus, dormant articles will
15890 naturally still (only) be marked as dormant. This is to make dormant
15891 articles stand out, just like ticked articles, in other @sc{imap}
15892 clients. (In other words, Gnus has two ``Tick'' marks and @sc{imap}
15895 Probably the only reason for frobing this would be if you're trying
15896 enable per-user persistant dormant flags, using something like:
15899 (setcdr (assq 'dormant nnimap-mark-to-flag-alist)
15900 (format "gnus-dormant-%s" (user-login-name)))
15901 (setcdr (assq 'dormant nnimap-mark-to-predicate-alist)
15902 (format "KEYWORD gnus-dormant-%s" (user-login-name)))
15905 In this case, you would not want the per-user dormant flag showing up
15906 as ticked for other users.
15908 @item nnimap-expunge-search-string
15910 @vindex nnimap-expunge-search-string
15912 This variable contain the @sc{imap} search command sent to server when
15913 searching for articles eligible for expiring. The default is
15914 @code{"UID %s NOT SINCE %s"}, where the first @code{%s} is replaced by
15915 UID set and the second @code{%s} is replaced by a date.
15917 Probably the only useful value to change this to is
15918 @code{"UID %s NOT SENTSINCE %s"}, which makes nnimap use the Date: in
15919 messages instead of the internal article date. See section 6.4.4 of
15920 RFC 2060 for more information on valid strings.
15922 @item nnimap-authinfo-file
15923 @vindex nnimap-authinfo-file
15925 A file containing credentials used to log in on servers. The format is
15926 (almost) the same as the @code{ftp} @file{~/.netrc} file. See the
15927 variable @code{nntp-authinfo-file} for exact syntax; also see
15933 * Splitting in IMAP:: Splitting mail with nnimap.
15934 * Expiring in IMAP:: Expiring mail with nnimap.
15935 * Editing IMAP ACLs:: Limiting/enabling other users access to a mailbox.
15936 * Expunging mailboxes:: Equivalent of a ``compress mailbox'' button.
15937 * A note on namespaces:: How to (not) use IMAP namespace in Gnus.
15942 @node Splitting in IMAP
15943 @subsection Splitting in IMAP
15944 @cindex splitting imap mail
15946 Splitting is something Gnus users has loved and used for years, and now
15947 the rest of the world is catching up. Yeah, dream on, not many
15948 @sc{imap} server has server side splitting and those that have splitting
15949 seem to use some non-standard protocol. This means that @sc{imap}
15950 support for Gnus has to do it's own splitting.
15954 Here are the variables of interest:
15958 @item nnimap-split-crosspost
15959 @cindex splitting, crosspost
15961 @vindex nnimap-split-crosspost
15963 If non-nil, do crossposting if several split methods match the mail. If
15964 nil, the first match in @code{nnimap-split-rule} found will be used.
15966 Nnmail equivalent: @code{nnmail-crosspost}.
15968 @item nnimap-split-inbox
15969 @cindex splitting, inbox
15971 @vindex nnimap-split-inbox
15973 A string or a list of strings that gives the name(s) of @sc{imap}
15974 mailboxes to split from. Defaults to nil, which means that splitting is
15978 (setq nnimap-split-inbox
15979 '("INBOX" ("~/friend/Mail" . "lists/*") "lists.imap"))
15982 No nnmail equivalent.
15984 @item nnimap-split-rule
15985 @cindex Splitting, rules
15986 @vindex nnimap-split-rule
15988 New mail found in @code{nnimap-split-inbox} will be split according to
15991 This variable contains a list of lists, where the first element in the
15992 sublist gives the name of the @sc{imap} mailbox to move articles
15993 matching the regexp in the second element in the sublist. Got that?
15994 Neither did I, we need examples.
15997 (setq nnimap-split-rule
15999 "^Sender: owner-nnimap@@vic20.globalcom.se")
16000 ("INBOX.junk" "^Subject:.*MAKE MONEY")
16001 ("INBOX.private" "")))
16004 This will put all articles from the nnimap mailing list into mailbox
16005 INBOX.nnimap, all articles containing MAKE MONEY in the Subject: line
16006 into INBOX.junk and everything else in INBOX.private.
16008 The first string may contain `\\1' forms, like the ones used by
16009 replace-match to insert sub-expressions from the matched text. For
16013 ("INBOX.lists.\\1" "^Sender: owner-\\([a-z-]+\\)@@")
16016 The first element can also be the symbol @code{junk} to indicate that
16017 matching messages should simply be deleted. Use with care.
16019 The second element can also be a function. In that case, it will be
16020 called with the first element of the rule as the argument, in a buffer
16021 containing the headers of the article. It should return a non-nil value
16022 if it thinks that the mail belongs in that group.
16024 Nnmail users might recollect that the last regexp had to be empty to
16025 match all articles (like in the example above). This is not required in
16026 nnimap. Articles not matching any of the regexps will not be moved out
16027 of your inbox. (This might affect performance if you keep lots of
16028 unread articles in your inbox, since the splitting code would go over
16029 them every time you fetch new mail.)
16031 These rules are processed from the beginning of the alist toward the
16032 end. The first rule to make a match will ``win'', unless you have
16033 crossposting enabled. In that case, all matching rules will ``win''.
16035 This variable can also have a function as its value, the function will
16036 be called with the headers narrowed and should return a group where it
16037 thinks the article should be split to. See @code{nnimap-split-fancy}.
16039 The splitting code tries to create mailboxes if it needs to.
16041 To allow for different split rules on different virtual servers, and
16042 even different split rules in different inboxes on the same server,
16043 the syntax of this variable have been extended along the lines of:
16046 (setq nnimap-split-rule
16047 '(("my1server" (".*" (("ding" "ding@@gnus.org")
16048 ("junk" "From:.*Simon")))
16049 ("my2server" ("INBOX" nnimap-split-fancy))
16050 ("my[34]server" (".*" (("private" "To:.*Simon")
16051 ("junk" my-junk-func)))))
16054 The virtual server name is in fact a regexp, so that the same rules
16055 may apply to several servers. In the example, the servers
16056 @code{my3server} and @code{my4server} both use the same rules.
16057 Similarly, the inbox string is also a regexp. The actual splitting
16058 rules are as before, either a function, or a list with group/regexp or
16059 group/function elements.
16061 Nnmail equivalent: @code{nnmail-split-methods}.
16063 @item nnimap-split-predicate
16065 @vindex nnimap-split-predicate
16067 Mail matching this predicate in @code{nnimap-split-inbox} will be
16068 split, it is a string and the default is @samp{UNSEEN UNDELETED}.
16070 This might be useful if you use another @sc{imap} client to read mail in
16071 your inbox but would like Gnus to split all articles in the inbox
16072 regardless of readedness. Then you might change this to
16075 @item nnimap-split-fancy
16076 @cindex splitting, fancy
16077 @findex nnimap-split-fancy
16078 @vindex nnimap-split-fancy
16080 It's possible to set @code{nnimap-split-rule} to
16081 @code{nnmail-split-fancy} if you want to use fancy
16082 splitting. @xref{Fancy Mail Splitting}.
16084 However, to be able to have different fancy split rules for nnmail and
16085 nnimap back ends you can set @code{nnimap-split-rule} to
16086 @code{nnimap-split-fancy} and define the nnimap specific fancy split
16087 rule in @code{nnimap-split-fancy}.
16092 (setq nnimap-split-rule 'nnimap-split-fancy
16093 nnimap-split-fancy ...)
16096 Nnmail equivalent: @code{nnmail-split-fancy}.
16098 @item nnimap-split-download-body
16099 @findex nnimap-split-download-body
16100 @vindex nnimap-split-download-body
16102 Set to non-nil to download entire articles during splitting. This is
16103 generally not required, and will slow things down considerably. You
16104 may need it if you want to use an advanced splitting function that
16105 analyses the body to split the article.
16109 @node Expiring in IMAP
16110 @subsection Expiring in IMAP
16111 @cindex expiring imap mail
16113 Even though @code{nnimap} is not a proper @code{nnmail} derived back
16114 end, it supports most features in regular expiring (@pxref{Expiring
16115 Mail}). Unlike splitting in IMAP (@pxref{Splitting in IMAP}) it do
16116 not clone the @code{nnmail} variables (i.e., creating
16117 @var{nnimap-expiry-wait}) but reuse the @code{nnmail} variables. What
16118 follows below are the variables used by the @code{nnimap} expiry
16121 A note on how the expire mark is stored on the @sc{imap} server is
16122 appropriate here as well. The expire mark is translated into a
16123 @code{imap} client specific mark, @code{gnus-expire}, and stored on the
16124 message. This means that likely only Gnus will understand and treat
16125 the @code{gnus-expire} mark properly, although other clients may allow
16126 you to view client specific flags on the message. It also means that
16127 your server must support permanent storage of client specific flags on
16128 messages. Most do, fortunately.
16132 @item nnmail-expiry-wait
16133 @item nnmail-expiry-wait-function
16135 These variables are fully supported. The expire value can be a
16136 number, the symbol @code{immediate} or @code{never}.
16138 @item nnmail-expiry-target
16140 This variable is supported, and internally implemented by calling the
16141 @code{nnmail} functions that handle this. It contains an optimization
16142 that if the destination is a IMAP group on the same server, the
16143 article is copied instead of appended (that is, uploaded again).
16147 @node Editing IMAP ACLs
16148 @subsection Editing IMAP ACLs
16149 @cindex editing imap acls
16150 @cindex Access Control Lists
16151 @cindex Editing @sc{imap} ACLs
16153 @findex gnus-group-nnimap-edit-acl
16155 ACL stands for Access Control List. ACLs are used in @sc{imap} for
16156 limiting (or enabling) other users access to your mail boxes. Not all
16157 @sc{imap} servers support this, this function will give an error if it
16160 To edit a ACL for a mailbox, type @kbd{G l}
16161 (@code{gnus-group-edit-nnimap-acl}) and you'll be presented with a ACL
16162 editing window with detailed instructions.
16164 Some possible uses:
16168 Giving ``anyone'' the ``lrs'' rights (lookup, read, keep seen/unseen flags)
16169 on your mailing list mailboxes enables other users on the same server to
16170 follow the list without subscribing to it.
16172 At least with the Cyrus server, you are required to give the user
16173 ``anyone'' posting ("p") capabilities to have ``plussing'' work (that is,
16174 mail sent to user+mailbox@@domain ending up in the @sc{imap} mailbox
16178 @node Expunging mailboxes
16179 @subsection Expunging mailboxes
16183 @cindex Manual expunging
16185 @findex gnus-group-nnimap-expunge
16187 If you're using the @code{never} setting of @code{nnimap-expunge-on-close},
16188 you may want the option of expunging all deleted articles in a mailbox
16189 manually. This is exactly what @kbd{G x} does.
16191 Currently there is no way of showing deleted articles, you can just
16194 @node A note on namespaces
16195 @subsection A note on namespaces
16196 @cindex IMAP namespace
16199 The IMAP protocol has a concept called namespaces, described by the
16200 following text in the RFC:
16203 5.1.2. Mailbox Namespace Naming Convention
16205 By convention, the first hierarchical element of any mailbox name
16206 which begins with "#" identifies the "namespace" of the remainder of
16207 the name. This makes it possible to disambiguate between different
16208 types of mailbox stores, each of which have their own namespaces.
16210 For example, implementations which offer access to USENET
16211 newsgroups MAY use the "#news" namespace to partition the USENET
16212 newsgroup namespace from that of other mailboxes. Thus, the
16213 comp.mail.misc newsgroup would have an mailbox name of
16214 "#news.comp.mail.misc", and the name "comp.mail.misc" could refer
16215 to a different object (e.g. a user's private mailbox).
16218 While there is nothing in this text that warrants concern for the IMAP
16219 implementation in Gnus, some servers use namespace prefixes in a way
16220 that does not work with how Gnus uses mailbox names.
16222 Specifically, University of Washington's IMAP server uses mailbox
16223 names like @code{#driver.mbx/read-mail} which are valid only in the
16224 @sc{create} and @sc{append} commands. After the mailbox is created
16225 (or a messages is appended to a mailbox), it must be accessed without
16226 the namespace prefix, i.e. @code{read-mail}. Since Gnus do not make it
16227 possible for the user to guarantee that user entered mailbox names
16228 will only be used with the CREATE and APPEND commands, you should
16229 simply not use the namespace prefixed mailbox names in Gnus.
16231 See the UoW @sc{imapd} documentation for the @code{#driver.*/} prefix
16232 for more information on how to use the prefixes. They are a power
16233 tool and should be used only if you are sure what the effects are.
16235 @node Other Sources
16236 @section Other Sources
16238 Gnus can do more than just read news or mail. The methods described
16239 below allow Gnus to view directories and files as if they were
16243 * Directory Groups:: You can read a directory as if it was a newsgroup.
16244 * Anything Groups:: Dired? Who needs dired?
16245 * Document Groups:: Single files can be the basis of a group.
16246 * SOUP:: Reading @sc{soup} packets ``offline''.
16247 * Mail-To-News Gateways:: Posting articles via mail-to-news gateways.
16251 @node Directory Groups
16252 @subsection Directory Groups
16254 @cindex directory groups
16256 If you have a directory that has lots of articles in separate files in
16257 it, you might treat it as a newsgroup. The files have to have numerical
16260 This might be an opportune moment to mention @code{ange-ftp} (and its
16261 successor @code{efs}), that most wonderful of all wonderful Emacs
16262 packages. When I wrote @code{nndir}, I didn't think much about it---a
16263 back end to read directories. Big deal.
16265 @code{ange-ftp} changes that picture dramatically. For instance, if you
16266 enter the @code{ange-ftp} file name
16267 @file{/ftp.hpc.uh.edu:/pub/emacs/ding-list/} as the directory name,
16268 @code{ange-ftp} or @code{efs} will actually allow you to read this
16269 directory over at @samp{sina} as a newsgroup. Distributed news ahoy!
16271 @code{nndir} will use @sc{nov} files if they are present.
16273 @code{nndir} is a ``read-only'' back end---you can't delete or expire
16274 articles with this method. You can use @code{nnmh} or @code{nnml} for
16275 whatever you use @code{nndir} for, so you could switch to any of those
16276 methods if you feel the need to have a non-read-only @code{nndir}.
16279 @node Anything Groups
16280 @subsection Anything Groups
16283 From the @code{nndir} back end (which reads a single spool-like
16284 directory), it's just a hop and a skip to @code{nneething}, which
16285 pretends that any arbitrary directory is a newsgroup. Strange, but
16288 When @code{nneething} is presented with a directory, it will scan this
16289 directory and assign article numbers to each file. When you enter such
16290 a group, @code{nneething} must create ``headers'' that Gnus can use.
16291 After all, Gnus is a newsreader, in case you're forgetting.
16292 @code{nneething} does this in a two-step process. First, it snoops each
16293 file in question. If the file looks like an article (i.e., the first
16294 few lines look like headers), it will use this as the head. If this is
16295 just some arbitrary file without a head (e.g. a C source file),
16296 @code{nneething} will cobble up a header out of thin air. It will use
16297 file ownership, name and date and do whatever it can with these
16300 All this should happen automatically for you, and you will be presented
16301 with something that looks very much like a newsgroup. Totally like a
16302 newsgroup, to be precise. If you select an article, it will be displayed
16303 in the article buffer, just as usual.
16305 If you select a line that represents a directory, Gnus will pop you into
16306 a new summary buffer for this @code{nneething} group. And so on. You can
16307 traverse the entire disk this way, if you feel like, but remember that
16308 Gnus is not dired, really, and does not intend to be, either.
16310 There are two overall modes to this action---ephemeral or solid. When
16311 doing the ephemeral thing (i.e., @kbd{G D} from the group buffer), Gnus
16312 will not store information on what files you have read, and what files
16313 are new, and so on. If you create a solid @code{nneething} group the
16314 normal way with @kbd{G m}, Gnus will store a mapping table between
16315 article numbers and file names, and you can treat this group like any
16316 other groups. When you activate a solid @code{nneething} group, you will
16317 be told how many unread articles it contains, etc., etc.
16322 @item nneething-map-file-directory
16323 @vindex nneething-map-file-directory
16324 All the mapping files for solid @code{nneething} groups will be stored
16325 in this directory, which defaults to @file{~/.nneething/}.
16327 @item nneething-exclude-files
16328 @vindex nneething-exclude-files
16329 All files that match this regexp will be ignored. Nice to use to exclude
16330 auto-save files and the like, which is what it does by default.
16332 @item nneething-include-files
16333 @vindex nneething-include-files
16334 Regexp saying what files to include in the group. If this variable is
16335 non-@code{nil}, only files matching this regexp will be included.
16337 @item nneething-map-file
16338 @vindex nneething-map-file
16339 Name of the map files.
16343 @node Document Groups
16344 @subsection Document Groups
16346 @cindex documentation group
16349 @code{nndoc} is a cute little thing that will let you read a single file
16350 as a newsgroup. Several files types are supported:
16357 The babyl (rmail) mail box.
16362 The standard Unix mbox file.
16364 @cindex MMDF mail box
16366 The MMDF mail box format.
16369 Several news articles appended into a file.
16372 @cindex rnews batch files
16373 The rnews batch transport format.
16374 @cindex forwarded messages
16377 Forwarded articles.
16380 Netscape mail boxes.
16383 @sc{mime} multipart messages.
16385 @item standard-digest
16386 The standard (RFC 1153) digest format.
16389 A @sc{mime} digest of messages.
16391 @item lanl-gov-announce
16392 Announcement messages from LANL Gov Announce.
16394 @item rfc822-forward
16395 A message forwarded according to RFC822.
16398 The Outlook mail box.
16401 The Outlook Express dbx mail box.
16404 A bounce message from the Exim MTA.
16407 A message forwarded according to informal rules.
16410 An RFC934-forwarded message.
16416 A digest of Clarinet brief news items.
16419 Non-standard digest format---matches most things, but does it badly.
16425 You can also use the special ``file type'' @code{guess}, which means
16426 that @code{nndoc} will try to guess what file type it is looking at.
16427 @code{digest} means that @code{nndoc} should guess what digest type the
16430 @code{nndoc} will not try to change the file or insert any extra headers into
16431 it---it will simply, like, let you use the file as the basis for a
16432 group. And that's it.
16434 If you have some old archived articles that you want to insert into your
16435 new & spiffy Gnus mail back end, @code{nndoc} can probably help you with
16436 that. Say you have an old @file{RMAIL} file with mail that you now want
16437 to split into your new @code{nnml} groups. You look at that file using
16438 @code{nndoc} (using the @kbd{G f} command in the group buffer
16439 (@pxref{Foreign Groups})), set the process mark on all the articles in
16440 the buffer (@kbd{M P b}, for instance), and then re-spool (@kbd{B r})
16441 using @code{nnml}. If all goes well, all the mail in the @file{RMAIL}
16442 file is now also stored in lots of @code{nnml} directories, and you can
16443 delete that pesky @file{RMAIL} file. If you have the guts!
16445 Virtual server variables:
16448 @item nndoc-article-type
16449 @vindex nndoc-article-type
16450 This should be one of @code{mbox}, @code{babyl}, @code{digest},
16451 @code{news}, @code{rnews}, @code{mmdf}, @code{forward}, @code{rfc934},
16452 @code{rfc822-forward}, @code{mime-parts}, @code{standard-digest},
16453 @code{slack-digest}, @code{clari-briefs}, @code{nsmail}, @code{outlook},
16454 @code{oe-dbx}, @code{mailman}, and @code{mail-in-mail} or @code{guess}.
16456 @item nndoc-post-type
16457 @vindex nndoc-post-type
16458 This variable says whether Gnus is to consider the group a news group or
16459 a mail group. There are two valid values: @code{mail} (the default)
16464 * Document Server Internals:: How to add your own document types.
16468 @node Document Server Internals
16469 @subsubsection Document Server Internals
16471 Adding new document types to be recognized by @code{nndoc} isn't
16472 difficult. You just have to whip up a definition of what the document
16473 looks like, write a predicate function to recognize that document type,
16474 and then hook into @code{nndoc}.
16476 First, here's an example document type definition:
16480 (article-begin . "^\^A\^A\^A\^A\n")
16481 (body-end . "^\^A\^A\^A\^A\n"))
16484 The definition is simply a unique @dfn{name} followed by a series of
16485 regexp pseudo-variable settings. Below are the possible
16486 variables---don't be daunted by the number of variables; most document
16487 types can be defined with very few settings:
16490 @item first-article
16491 If present, @code{nndoc} will skip past all text until it finds
16492 something that match this regexp. All text before this will be
16495 @item article-begin
16496 This setting has to be present in all document type definitions. It
16497 says what the beginning of each article looks like.
16499 @item head-begin-function
16500 If present, this should be a function that moves point to the head of
16503 @item nndoc-head-begin
16504 If present, this should be a regexp that matches the head of the
16507 @item nndoc-head-end
16508 This should match the end of the head of the article. It defaults to
16509 @samp{^$}---the empty line.
16511 @item body-begin-function
16512 If present, this function should move point to the beginning of the body
16516 This should match the beginning of the body of the article. It defaults
16519 @item body-end-function
16520 If present, this function should move point to the end of the body of
16524 If present, this should match the end of the body of the article.
16527 If present, this should match the end of the file. All text after this
16528 regexp will be totally ignored.
16532 So, using these variables @code{nndoc} is able to dissect a document
16533 file into a series of articles, each with a head and a body. However, a
16534 few more variables are needed since not all document types are all that
16535 news-like---variables needed to transform the head or the body into
16536 something that's palatable for Gnus:
16539 @item prepare-body-function
16540 If present, this function will be called when requesting an article. It
16541 will be called with point at the start of the body, and is useful if the
16542 document has encoded some parts of its contents.
16544 @item article-transform-function
16545 If present, this function is called when requesting an article. It's
16546 meant to be used for more wide-ranging transformation of both head and
16547 body of the article.
16549 @item generate-head-function
16550 If present, this function is called to generate a head that Gnus can
16551 understand. It is called with the article number as a parameter, and is
16552 expected to generate a nice head for the article in question. It is
16553 called when requesting the headers of all articles.
16557 Let's look at the most complicated example I can come up with---standard
16562 (first-article . ,(concat "^" (make-string 70 ?-) "\n\n+"))
16563 (article-begin . ,(concat "\n\n" (make-string 30 ?-) "\n\n+"))
16564 (prepare-body-function . nndoc-unquote-dashes)
16565 (body-end-function . nndoc-digest-body-end)
16566 (head-end . "^ ?$")
16567 (body-begin . "^ ?\n")
16568 (file-end . "^End of .*digest.*[0-9].*\n\\*\\*\\|^End of.*Digest *$")
16569 (subtype digest guess))
16572 We see that all text before a 70-width line of dashes is ignored; all
16573 text after a line that starts with that @samp{^End of} is also ignored;
16574 each article begins with a 30-width line of dashes; the line separating
16575 the head from the body may contain a single space; and that the body is
16576 run through @code{nndoc-unquote-dashes} before being delivered.
16578 To hook your own document definition into @code{nndoc}, use the
16579 @code{nndoc-add-type} function. It takes two parameters---the first
16580 is the definition itself and the second (optional) parameter says
16581 where in the document type definition alist to put this definition.
16582 The alist is traversed sequentially, and @code{nndoc-TYPE-type-p} is
16583 called for a given type @code{TYPE}. So @code{nndoc-mmdf-type-p} is
16584 called to see whether a document is of @code{mmdf} type, and so on.
16585 These type predicates should return @code{nil} if the document is not
16586 of the correct type; @code{t} if it is of the correct type; and a
16587 number if the document might be of the correct type. A high number
16588 means high probability; a low number means low probability with
16589 @samp{0} being the lowest valid number.
16597 In the PC world people often talk about ``offline'' newsreaders. These
16598 are thingies that are combined reader/news transport monstrosities.
16599 With built-in modem programs. Yecchh!
16601 Of course, us Unix Weenie types of human beans use things like
16602 @code{uucp} and, like, @code{nntpd} and set up proper news and mail
16603 transport things like Ghod intended. And then we just use normal
16606 However, it can sometimes be convenient to do something that's a bit
16607 easier on the brain if you have a very slow modem, and you're not really
16608 that interested in doing things properly.
16610 A file format called @sc{soup} has been developed for transporting news
16611 and mail from servers to home machines and back again. It can be a bit
16614 First some terminology:
16619 This is the machine that is connected to the outside world and where you
16620 get news and/or mail from.
16623 This is the machine that you want to do the actual reading and responding
16624 on. It is typically not connected to the rest of the world in any way.
16627 Something that contains messages and/or commands. There are two kinds
16631 @item message packets
16632 These are packets made at the server, and typically contain lots of
16633 messages for you to read. These are called @file{SoupoutX.tgz} by
16634 default, where @var{x} is a number.
16636 @item response packets
16637 These are packets made at the home machine, and typically contains
16638 replies that you've written. These are called @file{SoupinX.tgz} by
16639 default, where @var{x} is a number.
16649 You log in on the server and create a @sc{soup} packet. You can either
16650 use a dedicated @sc{soup} thingie (like the @code{awk} program), or you
16651 can use Gnus to create the packet with its @sc{soup} commands (@kbd{O
16652 s} and/or @kbd{G s b}; and then @kbd{G s p}) (@pxref{SOUP Commands}).
16655 You transfer the packet home. Rail, boat, car or modem will do fine.
16658 You put the packet in your home directory.
16661 You fire up Gnus on your home machine using the @code{nnsoup} back end as
16662 the native or secondary server.
16665 You read articles and mail and answer and followup to the things you
16666 want (@pxref{SOUP Replies}).
16669 You do the @kbd{G s r} command to pack these replies into a @sc{soup}
16673 You transfer this packet to the server.
16676 You use Gnus to mail this packet out with the @kbd{G s s} command.
16679 You then repeat until you die.
16683 So you basically have a bipartite system---you use @code{nnsoup} for
16684 reading and Gnus for packing/sending these @sc{soup} packets.
16687 * SOUP Commands:: Commands for creating and sending @sc{soup} packets
16688 * SOUP Groups:: A back end for reading @sc{soup} packets.
16689 * SOUP Replies:: How to enable @code{nnsoup} to take over mail and news.
16693 @node SOUP Commands
16694 @subsubsection SOUP Commands
16696 These are commands for creating and manipulating @sc{soup} packets.
16700 @kindex G s b (Group)
16701 @findex gnus-group-brew-soup
16702 Pack all unread articles in the current group
16703 (@code{gnus-group-brew-soup}). This command understands the
16704 process/prefix convention.
16707 @kindex G s w (Group)
16708 @findex gnus-soup-save-areas
16709 Save all @sc{soup} data files (@code{gnus-soup-save-areas}).
16712 @kindex G s s (Group)
16713 @findex gnus-soup-send-replies
16714 Send all replies from the replies packet
16715 (@code{gnus-soup-send-replies}).
16718 @kindex G s p (Group)
16719 @findex gnus-soup-pack-packet
16720 Pack all files into a @sc{soup} packet (@code{gnus-soup-pack-packet}).
16723 @kindex G s r (Group)
16724 @findex nnsoup-pack-replies
16725 Pack all replies into a replies packet (@code{nnsoup-pack-replies}).
16728 @kindex O s (Summary)
16729 @findex gnus-soup-add-article
16730 This summary-mode command adds the current article to a @sc{soup} packet
16731 (@code{gnus-soup-add-article}). It understands the process/prefix
16732 convention (@pxref{Process/Prefix}).
16737 There are a few variables to customize where Gnus will put all these
16742 @item gnus-soup-directory
16743 @vindex gnus-soup-directory
16744 Directory where Gnus will save intermediate files while composing
16745 @sc{soup} packets. The default is @file{~/SoupBrew/}.
16747 @item gnus-soup-replies-directory
16748 @vindex gnus-soup-replies-directory
16749 This is what Gnus will use as a temporary directory while sending our
16750 reply packets. @file{~/SoupBrew/SoupReplies/} is the default.
16752 @item gnus-soup-prefix-file
16753 @vindex gnus-soup-prefix-file
16754 Name of the file where Gnus stores the last used prefix. The default is
16755 @samp{gnus-prefix}.
16757 @item gnus-soup-packer
16758 @vindex gnus-soup-packer
16759 A format string command for packing a @sc{soup} packet. The default is
16760 @samp{tar cf - %s | gzip > $HOME/Soupout%d.tgz}.
16762 @item gnus-soup-unpacker
16763 @vindex gnus-soup-unpacker
16764 Format string command for unpacking a @sc{soup} packet. The default is
16765 @samp{gunzip -c %s | tar xvf -}.
16767 @item gnus-soup-packet-directory
16768 @vindex gnus-soup-packet-directory
16769 Where Gnus will look for reply packets. The default is @file{~/}.
16771 @item gnus-soup-packet-regexp
16772 @vindex gnus-soup-packet-regexp
16773 Regular expression matching @sc{soup} reply packets in
16774 @code{gnus-soup-packet-directory}.
16780 @subsubsection SOUP Groups
16783 @code{nnsoup} is the back end for reading @sc{soup} packets. It will
16784 read incoming packets, unpack them, and put them in a directory where
16785 you can read them at leisure.
16787 These are the variables you can use to customize its behavior:
16791 @item nnsoup-tmp-directory
16792 @vindex nnsoup-tmp-directory
16793 When @code{nnsoup} unpacks a @sc{soup} packet, it does it in this
16794 directory. (@file{/tmp/} by default.)
16796 @item nnsoup-directory
16797 @vindex nnsoup-directory
16798 @code{nnsoup} then moves each message and index file to this directory.
16799 The default is @file{~/SOUP/}.
16801 @item nnsoup-replies-directory
16802 @vindex nnsoup-replies-directory
16803 All replies will be stored in this directory before being packed into a
16804 reply packet. The default is @file{~/SOUP/replies/}.
16806 @item nnsoup-replies-format-type
16807 @vindex nnsoup-replies-format-type
16808 The @sc{soup} format of the replies packets. The default is @samp{?n}
16809 (rnews), and I don't think you should touch that variable. I probably
16810 shouldn't even have documented it. Drats! Too late!
16812 @item nnsoup-replies-index-type
16813 @vindex nnsoup-replies-index-type
16814 The index type of the replies packet. The default is @samp{?n}, which
16815 means ``none''. Don't fiddle with this one either!
16817 @item nnsoup-active-file
16818 @vindex nnsoup-active-file
16819 Where @code{nnsoup} stores lots of information. This is not an ``active
16820 file'' in the @code{nntp} sense; it's an Emacs Lisp file. If you lose
16821 this file or mess it up in any way, you're dead. The default is
16822 @file{~/SOUP/active}.
16824 @item nnsoup-packer
16825 @vindex nnsoup-packer
16826 Format string command for packing a reply @sc{soup} packet. The default
16827 is @samp{tar cf - %s | gzip > $HOME/Soupin%d.tgz}.
16829 @item nnsoup-unpacker
16830 @vindex nnsoup-unpacker
16831 Format string command for unpacking incoming @sc{soup} packets. The
16832 default is @samp{gunzip -c %s | tar xvf -}.
16834 @item nnsoup-packet-directory
16835 @vindex nnsoup-packet-directory
16836 Where @code{nnsoup} will look for incoming packets. The default is
16839 @item nnsoup-packet-regexp
16840 @vindex nnsoup-packet-regexp
16841 Regular expression matching incoming @sc{soup} packets. The default is
16844 @item nnsoup-always-save
16845 @vindex nnsoup-always-save
16846 If non-@code{nil}, save the replies buffer after each posted message.
16852 @subsubsection SOUP Replies
16854 Just using @code{nnsoup} won't mean that your postings and mailings end
16855 up in @sc{soup} reply packets automagically. You have to work a bit
16856 more for that to happen.
16858 @findex nnsoup-set-variables
16859 The @code{nnsoup-set-variables} command will set the appropriate
16860 variables to ensure that all your followups and replies end up in the
16863 In specific, this is what it does:
16866 (setq message-send-news-function 'nnsoup-request-post)
16867 (setq message-send-mail-function 'nnsoup-request-mail)
16870 And that's it, really. If you only want news to go into the @sc{soup}
16871 system you just use the first line. If you only want mail to be
16872 @sc{soup}ed you use the second.
16875 @node Mail-To-News Gateways
16876 @subsection Mail-To-News Gateways
16877 @cindex mail-to-news gateways
16880 If your local @code{nntp} server doesn't allow posting, for some reason
16881 or other, you can post using one of the numerous mail-to-news gateways.
16882 The @code{nngateway} back end provides the interface.
16884 Note that you can't read anything from this back end---it can only be
16890 @item nngateway-address
16891 @vindex nngateway-address
16892 This is the address of the mail-to-news gateway.
16894 @item nngateway-header-transformation
16895 @vindex nngateway-header-transformation
16896 News headers often have to be transformed in some odd way or other
16897 for the mail-to-news gateway to accept it. This variable says what
16898 transformation should be called, and defaults to
16899 @code{nngateway-simple-header-transformation}. The function is called
16900 narrowed to the headers to be transformed and with one parameter---the
16903 This default function just inserts a new @code{To} header based on the
16904 @code{Newsgroups} header and the gateway address.
16905 For instance, an article with this @code{Newsgroups} header:
16908 Newsgroups: alt.religion.emacs
16911 will get this @code{To} header inserted:
16914 To: alt-religion-emacs@@GATEWAY
16917 The following pre-defined functions exist:
16919 @findex nngateway-simple-header-transformation
16922 @item nngateway-simple-header-transformation
16923 Creates a @code{To} header that looks like
16924 @var{newsgroup}@@@code{nngateway-address}.
16926 @findex nngateway-mail2news-header-transformation
16928 @item nngateway-mail2news-header-transformation
16929 Creates a @code{To} header that looks like
16930 @code{nngateway-address}.
16935 (setq gnus-post-method
16937 "mail2news@@replay.com"
16938 (nngateway-header-transformation
16939 nngateway-mail2news-header-transformation)))
16947 So, to use this, simply say something like:
16950 (setq gnus-post-method '(nngateway "GATEWAY.ADDRESS"))
16955 @node Combined Groups
16956 @section Combined Groups
16958 Gnus allows combining a mixture of all the other group types into bigger
16962 * Virtual Groups:: Combining articles from many groups.
16963 * Kibozed Groups:: Looking through parts of the newsfeed for articles.
16967 @node Virtual Groups
16968 @subsection Virtual Groups
16970 @cindex virtual groups
16971 @cindex merging groups
16973 An @dfn{nnvirtual group} is really nothing more than a collection of
16976 For instance, if you are tired of reading many small groups, you can
16977 put them all in one big group, and then grow tired of reading one
16978 big, unwieldy group. The joys of computing!
16980 You specify @code{nnvirtual} as the method. The address should be a
16981 regexp to match component groups.
16983 All marks in the virtual group will stick to the articles in the
16984 component groups. So if you tick an article in a virtual group, the
16985 article will also be ticked in the component group from whence it
16986 came. (And vice versa---marks from the component groups will also be
16987 shown in the virtual group.). To create an empty virtual group, run
16988 @kbd{G V} (@code{gnus-group-make-empty-virtual}) in the group buffer
16989 and edit the method regexp with @kbd{M-e}
16990 (@code{gnus-group-edit-group-method})
16992 Here's an example @code{nnvirtual} method that collects all Andrea Dworkin
16993 newsgroups into one, big, happy newsgroup:
16996 (nnvirtual "^alt\\.fan\\.andrea-dworkin$\\|^rec\\.dworkin.*")
16999 The component groups can be native or foreign; everything should work
17000 smoothly, but if your computer explodes, it was probably my fault.
17002 Collecting the same group from several servers might actually be a good
17003 idea if users have set the Distribution header to limit distribution.
17004 If you would like to read @samp{soc.motss} both from a server in Japan
17005 and a server in Norway, you could use the following as the group regexp:
17008 "^nntp\\+server\\.jp:soc\\.motss$\\|^nntp\\+server\\.no:soc\\.motss$"
17011 (Remember, though, that if you're creating the group with @kbd{G m}, you
17012 shouldn't double the backslashes, and you should leave off the quote
17013 characters at the beginning and the end of the string.)
17015 This should work kinda smoothly---all articles from both groups should
17016 end up in this one, and there should be no duplicates. Threading (and
17017 the rest) will still work as usual, but there might be problems with the
17018 sequence of articles. Sorting on date might be an option here
17019 (@pxref{Selecting a Group}).
17021 One limitation, however---all groups included in a virtual
17022 group have to be alive (i.e., subscribed or unsubscribed). Killed or
17023 zombie groups can't be component groups for @code{nnvirtual} groups.
17025 @vindex nnvirtual-always-rescan
17026 If the @code{nnvirtual-always-rescan} is non-@code{nil},
17027 @code{nnvirtual} will always scan groups for unread articles when
17028 entering a virtual group. If this variable is @code{nil} (which is the
17029 default) and you read articles in a component group after the virtual
17030 group has been activated, the read articles from the component group
17031 will show up when you enter the virtual group. You'll also see this
17032 effect if you have two virtual groups that have a component group in
17033 common. If that's the case, you should set this variable to @code{t}.
17034 Or you can just tap @code{M-g} on the virtual group every time before
17035 you enter it---it'll have much the same effect.
17037 @code{nnvirtual} can have both mail and news groups as component groups.
17038 When responding to articles in @code{nnvirtual} groups, @code{nnvirtual}
17039 has to ask the back end of the component group the article comes from
17040 whether it is a news or mail back end. However, when you do a @kbd{^},
17041 there is typically no sure way for the component back end to know this,
17042 and in that case @code{nnvirtual} tells Gnus that the article came from a
17043 not-news back end. (Just to be on the safe side.)
17045 @kbd{C-c C-n} in the message buffer will insert the @code{Newsgroups}
17046 line from the article you respond to in these cases.
17048 @code{nnvirtual} groups do not inherit anything but articles and marks
17049 from component groups---group parameters, for instance, are not
17053 @node Kibozed Groups
17054 @subsection Kibozed Groups
17058 @dfn{Kibozing} is defined by @sc{oed} as ``grepping through (parts of)
17059 the news feed''. @code{nnkiboze} is a back end that will do this for
17060 you. Oh joy! Now you can grind any @sc{nntp} server down to a halt
17061 with useless requests! Oh happiness!
17063 @kindex G k (Group)
17064 To create a kibozed group, use the @kbd{G k} command in the group
17067 The address field of the @code{nnkiboze} method is, as with
17068 @code{nnvirtual}, a regexp to match groups to be ``included'' in the
17069 @code{nnkiboze} group. That's where most similarities between @code{nnkiboze}
17070 and @code{nnvirtual} end.
17072 In addition to this regexp detailing component groups, an @code{nnkiboze} group
17073 must have a score file to say what articles are to be included in
17074 the group (@pxref{Scoring}).
17076 @kindex M-x nnkiboze-generate-groups
17077 @findex nnkiboze-generate-groups
17078 You must run @kbd{M-x nnkiboze-generate-groups} after creating the
17079 @code{nnkiboze} groups you want to have. This command will take time. Lots of
17080 time. Oodles and oodles of time. Gnus has to fetch the headers from
17081 all the articles in all the component groups and run them through the
17082 scoring process to determine if there are any articles in the groups
17083 that are to be part of the @code{nnkiboze} groups.
17085 Please limit the number of component groups by using restrictive
17086 regexps. Otherwise your sysadmin may become annoyed with you, and the
17087 @sc{nntp} site may throw you off and never let you back in again.
17088 Stranger things have happened.
17090 @code{nnkiboze} component groups do not have to be alive---they can be dead,
17091 and they can be foreign. No restrictions.
17093 @vindex nnkiboze-directory
17094 The generation of an @code{nnkiboze} group means writing two files in
17095 @code{nnkiboze-directory}, which is @file{~/News/} by default. One
17096 contains the @sc{nov} header lines for all the articles in the group,
17097 and the other is an additional @file{.newsrc} file to store information
17098 on what groups have been searched through to find component articles.
17100 Articles marked as read in the @code{nnkiboze} group will have
17101 their @sc{nov} lines removed from the @sc{nov} file.
17104 @node Gnus Unplugged
17105 @section Gnus Unplugged
17110 @cindex Gnus Unplugged
17112 In olden times (ca. February '88), people used to run their newsreaders
17113 on big machines with permanent connections to the net. News transport
17114 was dealt with by news servers, and all the newsreaders had to do was to
17115 read news. Believe it or not.
17117 Nowadays most people read news and mail at home, and use some sort of
17118 modem to connect to the net. To avoid running up huge phone bills, it
17119 would be nice to have a way to slurp down all the news and mail, hang up
17120 the phone, read for several hours, and then upload any responses you
17121 have to make. And then you repeat the procedure.
17123 Of course, you can use news servers for doing this as well. I've used
17124 @code{inn} together with @code{slurp}, @code{pop} and @code{sendmail}
17125 for some years, but doing that's a bore. Moving the news server
17126 functionality up to the newsreader makes sense if you're the only person
17127 reading news on a machine.
17129 Setting up Gnus as an ``offline'' newsreader is quite simple. In
17130 fact, you don't even have to configure anything.
17132 Of course, to use it as such, you have to learn a few new commands.
17135 * Agent Basics:: How it all is supposed to work.
17136 * Agent Categories:: How to tell the Gnus Agent what to download.
17137 * Agent Commands:: New commands for all the buffers.
17138 * Agent as Cache:: The Agent is a big cache too.
17139 * Agent Expiry:: How to make old articles go away.
17140 * Agent Regeneration:: How to recover from lost connections and other accidents.
17141 * Agent and IMAP:: How to use the Agent with IMAP.
17142 * Outgoing Messages:: What happens when you post/mail something?
17143 * Agent Variables:: Customizing is fun.
17144 * Example Setup:: An example @file{~/.gnus.el} file for offline people.
17145 * Batching Agents:: How to fetch news from a @code{cron} job.
17146 * Agent Caveats:: What you think it'll do and what it does.
17151 @subsection Agent Basics
17153 First, let's get some terminology out of the way.
17155 The Gnus Agent is said to be @dfn{unplugged} when you have severed the
17156 connection to the net (and notified the Agent that this is the case).
17157 When the connection to the net is up again (and Gnus knows this), the
17158 Agent is @dfn{plugged}.
17160 The @dfn{local} machine is the one you're running on, and which isn't
17161 connected to the net continuously.
17163 @dfn{Downloading} means fetching things from the net to your local
17164 machine. @dfn{Uploading} is doing the opposite.
17166 Let's take a typical Gnus session using the Agent.
17171 @findex gnus-unplugged
17172 You start Gnus with @code{gnus-unplugged}. This brings up the Gnus
17173 Agent in a disconnected state. You can read all the news that you have
17174 already fetched while in this mode.
17177 You then decide to see whether any new news has arrived. You connect
17178 your machine to the net (using PPP or whatever), and then hit @kbd{J j}
17179 to make Gnus become @dfn{plugged} and use @kbd{g} to check for new mail
17180 as usual. To check for new mail in unplugged mode, see (@pxref{Mail
17181 Source Specifiers}).
17184 You can then read the new news immediately, or you can download the news
17185 onto your local machine. If you want to do the latter, you press @kbd{g}
17186 to check if there are any new news and then @kbd{J
17187 s} to fetch all the eligible articles in all the groups. (To let Gnus
17188 know which articles you want to download, @pxref{Agent Categories}.)
17191 After fetching the articles, you press @kbd{J j} to make Gnus become
17192 unplugged again, and you shut down the PPP thing (or whatever). And
17193 then you read the news offline.
17196 And then you go to step 2.
17199 Here are some things you should do the first time (or so) that you use
17205 Decide which servers should be covered by the Agent. If you have a mail
17206 back end, it would probably be nonsensical to have it covered by the
17207 Agent. Go to the server buffer (@kbd{^} in the group buffer) and press
17208 @kbd{J a} on the server (or servers) that you wish to have covered by the
17209 Agent (@pxref{Server Agent Commands}), or @kbd{J r} on automatically
17210 added servers you do not wish to have covered by the Agent. By default,
17211 all @code{nntp} and @code{nnimap} groups in @code{gnus-select-method} and
17212 @code{gnus-secondary-select-methods} are agentized.
17216 Decide on download policy. It's fairly simple once you decide whether
17217 you are going to use agent categories, topic parameters, and/or group
17218 parameters to implement your policy. If you're new to gnus, it
17219 is probably best to start with a category @xref{Agent Categories}.
17221 Both topic parameters (@pxref{Topic Parameters}) and agent categories
17222 (@pxref{Agent Categories}) provide for setting a policy that applies
17223 to multiple groups. Which you use is entirely up to you. Topic
17224 parameters do override categories so, if you mix the two, you'll have
17225 to take that into account. If you have a few groups that deviate from
17226 your policy, you can use grou parameters (@pxref{Group Parameters}) to
17230 Uhm@dots{} that's it.
17234 @node Agent Categories
17235 @subsection Agent Categories
17237 One of the main reasons to integrate the news transport layer into the
17238 newsreader is to allow greater control over what articles to download.
17239 There's not much point in downloading huge amounts of articles, just to
17240 find out that you're not interested in reading any of them. It's better
17241 to be somewhat more conservative in choosing what to download, and then
17242 mark the articles for downloading manually if it should turn out that
17243 you're interested in the articles anyway.
17245 One of the more effective methods for controlling what is to be
17246 downloaded is to create a @dfn{category} and then assign some (or all)
17247 groups to this category. Groups that do not belong in any other
17248 category belong to the @code{default} category. Gnus has its own
17249 buffer for creating and managing categories.
17251 If you prefer, you can also use group parameters (@pxref{Group
17252 Parameters}) and topic parameters (@pxref{Topic Parameters}) for an
17253 alternative approach to controlling the agent. The only real
17254 difference is that categories are specific to the agent (so there is
17255 less to learn) while group and topic parameters include the kitchen
17258 Since you can set agent parameters in several different places we have
17259 a rule to decide which source to believe. This rule specifies that
17260 the parameter sources are checked in the following order: group
17261 parameters, topic parameters, agent category, and finally customizable
17262 variables. So you can mix all of these sources to produce a wide range
17263 of behavior, just don't blame me if you don't remember where you put
17267 * Category Syntax:: What a category looks like.
17268 * Category Buffer:: A buffer for maintaining categories.
17269 * Category Variables:: Customize'r'Us.
17273 @node Category Syntax
17274 @subsubsection Category Syntax
17276 A category consists of a name, the list of groups belonging to the
17277 category, and a number of optional parameters that override the
17278 customizable variables. The complete list of agent parameters are
17282 @item gnus-agent-cat-name
17283 The name of the category.
17285 @item gnus-agent-cat-groups
17286 The list of groups that are in this category.
17288 @item gnus-agent-cat-predicate
17289 A predicate which (generally) gives a rough outline of which articles
17290 are eligible for downloading; and
17292 @item gnus-agent-cat-score-file
17293 a score rule which (generally) gives you a finer granularity when
17294 deciding what articles to download. (Note that this @dfn{download
17295 score} is not necessarily related to normal scores.)
17297 @item gnus-agent-cat-enable-expiration
17298 a boolean indicating whether the agent should expire old articles in
17299 this group. Most groups should be expired to conserve disk space. In
17300 fact, its probably safe to say that the gnus.* hierarchy contains the
17301 only groups that should not be expired.
17303 @item gnus-agent-cat-days-until-old
17304 an integer indicating the number of days that the agent should wait
17305 before deciding that a read article is safe to expire.
17307 @item gnus-agent-cat-low-score
17308 an integer that overrides the value of @code{gnus-agent-low-score}.
17310 @item gnus-agent-cat-high-score
17311 an integer that overrides the value of @code{gnus-agent-high-score}.
17313 @item gnus-agent-cat-length-when-short
17314 an integer that overrides the value of
17315 @code{gnus-agent-short-article}.
17317 @item gnus-agent-cat-length-when-long
17318 an integer that overrides the value of @code{gnus-agent-long-article}.
17321 The name of a category can not be changed once the category has been
17324 Each category maintains a list of groups that are exclusive members of
17325 that category. The exclusivity rule is automatically enforced, add a
17326 group to a new category and it is automatically removed from its old
17329 A predicate in its simplest form can be a single predicate such as
17330 @code{true} or @code{false}. These two will download every available
17331 article or nothing respectively. In the case of these two special
17332 predicates an additional score rule is superfluous.
17334 Predicates of @code{high} or @code{low} download articles in respect of
17335 their scores in relationship to @code{gnus-agent-high-score} and
17336 @code{gnus-agent-low-score} as described below.
17338 To gain even finer control of what is to be regarded eligible for
17339 download a predicate can consist of a number of predicates with logical
17340 operators sprinkled in between.
17342 Perhaps some examples are in order.
17344 Here's a simple predicate. (It's the default predicate, in fact, used
17345 for all groups that don't belong to any other category.)
17351 Quite simple, eh? This predicate is true if and only if the article is
17352 short (for some value of ``short'').
17354 Here's a more complex predicate:
17363 This means that an article should be downloaded if it has a high score,
17364 or if the score is not low and the article is not long. You get the
17367 The available logical operators are @code{or}, @code{and} and
17368 @code{not}. (If you prefer, you can use the more ``C''-ish operators
17369 @samp{|}, @code{&} and @code{!} instead.)
17371 The following predicates are pre-defined, but if none of these fit what
17372 you want to do, you can write your own.
17374 When evaluating each of these predicates, the named constant will be
17375 bound to the value determined by calling
17376 @code{gnus-agent-find-parameter} on the appropriate parameter. For
17377 example, gnus-agent-short-article will be bound to
17378 @code{(gnus-agent-find-parameter group 'agent-short-article)}. This
17379 means that you can specify a predicate in your category then tune that
17380 predicate to individual groups.
17384 True iff the article is shorter than @code{gnus-agent-short-article}
17385 lines; default 100.
17388 True iff the article is longer than @code{gnus-agent-long-article}
17389 lines; default 200.
17392 True iff the article has a download score less than
17393 @code{gnus-agent-low-score}; default 0.
17396 True iff the article has a download score greater than
17397 @code{gnus-agent-high-score}; default 0.
17400 True iff the Gnus Agent guesses that the article is spam. The
17401 heuristics may change over time, but at present it just computes a
17402 checksum and sees whether articles match.
17411 If you want to create your own predicate function, here's what you have
17412 to know: The functions are called with no parameters, but the
17413 @code{gnus-headers} and @code{gnus-score} dynamic variables are bound to
17416 For example, you could decide that you don't want to download articles
17417 that were posted more than a certain number of days ago (e.g. posted
17418 more than @code{gnus-agent-expire-days} ago) you might write a function
17419 something along the lines of the following:
17422 (defun my-article-old-p ()
17423 "Say whether an article is old."
17424 (< (time-to-days (date-to-time (mail-header-date gnus-headers)))
17425 (- (time-to-days (current-time)) gnus-agent-expire-days)))
17428 with the predicate then defined as:
17431 (not my-article-old-p)
17434 or you could append your predicate to the predefined
17435 @code{gnus-category-predicate-alist} in your @file{~/.gnus.el} or
17439 (require 'gnus-agent)
17440 (setq gnus-category-predicate-alist
17441 (append gnus-category-predicate-alist
17442 '((old . my-article-old-p))))
17445 and simply specify your predicate as:
17451 If/when using something like the above, be aware that there are many
17452 misconfigured systems/mailers out there and so an article's date is not
17453 always a reliable indication of when it was posted. Hell, some people
17454 just don't give a damn.
17456 The above predicates apply to @emph{all} the groups which belong to the
17457 category. However, if you wish to have a specific predicate for an
17458 individual group within a category, or you're just too lazy to set up a
17459 new category, you can enter a group's individual predicate in it's group
17460 parameters like so:
17463 (agent-predicate . short)
17466 This is the group/topic parameter equivalent of the agent category default.
17467 Note that when specifying a single word predicate like this, the
17468 @code{agent-predicate} specification must be in dotted pair notation.
17470 The equivalent of the longer example from above would be:
17473 (agent-predicate or high (and (not low) (not long)))
17476 The outer parenthesis required in the category specification are not
17477 entered here as, not being in dotted pair notation, the value of the
17478 predicate is assumed to be a list.
17481 Now, the syntax of the download score is the same as the syntax of
17482 normal score files, except that all elements that require actually
17483 seeing the article itself are verboten. This means that only the
17484 following headers can be scored on: @code{Subject}, @code{From},
17485 @code{Date}, @code{Message-ID}, @code{References}, @code{Chars},
17486 @code{Lines}, and @code{Xref}.
17488 As with predicates, the specification of the @code{download score rule}
17489 to use in respect of a group can be in either the category definition if
17490 it's to be applicable to all groups in therein, or a group's parameters
17491 if it's to be specific to that group.
17493 In both of these places the @code{download score rule} can take one of
17500 This has the same syntax as a normal gnus score file except only a
17501 subset of scoring keywords are available as mentioned above.
17507 Category specification
17511 ("Lars Ingebrigtsen" 1000000 nil s))
17517 Group/Topic Parameter specification
17520 (agent-score ("from"
17521 ("Lars Ingebrigtsen" 1000000 nil s))
17526 Again, note the omission of the outermost parenthesis here.
17532 These score files must @emph{only} contain the permitted scoring
17533 keywords stated above.
17539 Category specification
17542 ("~/News/agent.SCORE")
17548 ("~/News/agent.SCORE" "~/News/agent.group.SCORE")
17552 Group Parameter specification
17555 (agent-score "~/News/agent.SCORE")
17558 Additional score files can be specified as above. Need I say anything
17563 Use @code{normal} score files
17565 If you don't want to maintain two sets of scoring rules for a group, and
17566 your desired @code{downloading} criteria for a group are the same as your
17567 @code{reading} criteria then you can tell the agent to refer to your
17568 @code{normal} score files when deciding what to download.
17570 These directives in either the category definition or a group's
17571 parameters will cause the agent to read in all the applicable score
17572 files for a group, @emph{filtering out} those sections that do not
17573 relate to one of the permitted subset of scoring keywords.
17577 Category Specification
17584 Group Parameter specification
17587 (agent-score . file)
17592 @node Category Buffer
17593 @subsubsection Category Buffer
17595 You'd normally do all category maintenance from the category buffer.
17596 When you enter it for the first time (with the @kbd{J c} command from
17597 the group buffer), you'll only see the @code{default} category.
17599 The following commands are available in this buffer:
17603 @kindex q (Category)
17604 @findex gnus-category-exit
17605 Return to the group buffer (@code{gnus-category-exit}).
17608 @kindex e (Category)
17609 @findex gnus-category-customize-category
17610 Use a customization buffer to set all of the selected category's
17611 parameters at one time (@code{gnus-category-customize-category}).
17614 @kindex k (Category)
17615 @findex gnus-category-kill
17616 Kill the current category (@code{gnus-category-kill}).
17619 @kindex c (Category)
17620 @findex gnus-category-copy
17621 Copy the current category (@code{gnus-category-copy}).
17624 @kindex a (Category)
17625 @findex gnus-category-add
17626 Add a new category (@code{gnus-category-add}).
17629 @kindex p (Category)
17630 @findex gnus-category-edit-predicate
17631 Edit the predicate of the current category
17632 (@code{gnus-category-edit-predicate}).
17635 @kindex g (Category)
17636 @findex gnus-category-edit-groups
17637 Edit the list of groups belonging to the current category
17638 (@code{gnus-category-edit-groups}).
17641 @kindex s (Category)
17642 @findex gnus-category-edit-score
17643 Edit the download score rule of the current category
17644 (@code{gnus-category-edit-score}).
17647 @kindex l (Category)
17648 @findex gnus-category-list
17649 List all the categories (@code{gnus-category-list}).
17653 @node Category Variables
17654 @subsubsection Category Variables
17657 @item gnus-category-mode-hook
17658 @vindex gnus-category-mode-hook
17659 Hook run in category buffers.
17661 @item gnus-category-line-format
17662 @vindex gnus-category-line-format
17663 Format of the lines in the category buffer (@pxref{Formatting
17664 Variables}). Valid elements are:
17668 The name of the category.
17671 The number of groups in the category.
17674 @item gnus-category-mode-line-format
17675 @vindex gnus-category-mode-line-format
17676 Format of the category mode line (@pxref{Mode Line Formatting}).
17678 @item gnus-agent-short-article
17679 @vindex gnus-agent-short-article
17680 Articles that have fewer lines than this are short. Default 100.
17682 @item gnus-agent-long-article
17683 @vindex gnus-agent-long-article
17684 Articles that have more lines than this are long. Default 200.
17686 @item gnus-agent-low-score
17687 @vindex gnus-agent-low-score
17688 Articles that have a score lower than this have a low score. Default
17691 @item gnus-agent-high-score
17692 @vindex gnus-agent-high-score
17693 Articles that have a score higher than this have a high score. Default
17696 @item gnus-agent-expire-days
17697 @vindex gnus-agent-expire-days
17698 The number of days that a @samp{read} article must stay in the agent's
17699 local disk before becoming eligible for expiration (While the name is
17700 the same, this doesn't mean expiring the article on the server. It
17701 just means deleting the local copy of the article). What is also
17702 important to understand is that the counter starts with the time the
17703 article was written to the local disk and not the time the article was
17707 @item gnus-agent-enable-expiration
17708 @vindex gnus-agent-enable-expiration
17709 Determines whether articles in a group are, by default, expired or
17710 retained indefinitely. The default is @code{ENABLE} which means that
17711 you'll have to disable expiration when desired. On the other hand,
17712 you could set this to @code{DISABLE}. In that case, you would then
17713 have to enable expiration in selected groups.
17718 @node Agent Commands
17719 @subsection Agent Commands
17720 @findex gnus-agent-toggle-plugged
17721 @kindex J j (Agent)
17723 All the Gnus Agent commands are on the @kbd{J} submap. The @kbd{J j}
17724 (@code{gnus-agent-toggle-plugged}) command works in all modes, and
17725 toggles the plugged/unplugged state of the Gnus Agent.
17729 * Group Agent Commands:: Configure groups and fetch their contents.
17730 * Summary Agent Commands:: Manually select then fetch specific articles.
17731 * Server Agent Commands:: Select the servers that are supported by the agent.
17737 @node Group Agent Commands
17738 @subsubsection Group Agent Commands
17742 @kindex J u (Agent Group)
17743 @findex gnus-agent-fetch-groups
17744 Fetch all eligible articles in the current group
17745 (@code{gnus-agent-fetch-groups}).
17748 @kindex J c (Agent Group)
17749 @findex gnus-enter-category-buffer
17750 Enter the Agent category buffer (@code{gnus-enter-category-buffer}).
17753 @kindex J s (Agent Group)
17754 @findex gnus-agent-fetch-session
17755 Fetch all eligible articles in all groups
17756 (@code{gnus-agent-fetch-session}).
17759 @kindex J S (Agent Group)
17760 @findex gnus-group-send-queue
17761 Send all sendable messages in the queue group
17762 (@code{gnus-group-send-queue}). @xref{Drafts}.
17765 @kindex J a (Agent Group)
17766 @findex gnus-agent-add-group
17767 Add the current group to an Agent category
17768 (@code{gnus-agent-add-group}). This command understands the
17769 process/prefix convention (@pxref{Process/Prefix}).
17772 @kindex J r (Agent Group)
17773 @findex gnus-agent-remove-group
17774 Remove the current group from its category, if any
17775 (@code{gnus-agent-remove-group}). This command understands the
17776 process/prefix convention (@pxref{Process/Prefix}).
17779 @kindex J Y (Agent Group)
17780 @findex gnus-agent-synchronize-flags
17781 Synchronize flags changed while unplugged with remote server, if any.
17787 @node Summary Agent Commands
17788 @subsubsection Summary Agent Commands
17792 @kindex J # (Agent Summary)
17793 @findex gnus-agent-mark-article
17794 Mark the article for downloading (@code{gnus-agent-mark-article}).
17797 @kindex J M-# (Agent Summary)
17798 @findex gnus-agent-unmark-article
17799 Remove the downloading mark from the article
17800 (@code{gnus-agent-unmark-article}).
17804 @kindex @@ (Agent Summary)
17805 @findex gnus-agent-toggle-mark
17806 Toggle whether to download the article
17807 (@code{gnus-agent-toggle-mark}). The dowload mark is @samp{%} by
17811 @kindex J c (Agent Summary)
17812 @findex gnus-agent-catchup
17813 Mark all articles as read (@code{gnus-agent-catchup}) that are neither cached, downloaded, nor downloadable.
17816 @kindex J S (Agent Summary)
17817 @findex gnus-agent-fetch-group
17818 Download all eligible (See @pxref{Agent Categories}) articles in this group.
17819 (@code{gnus-agent-fetch-group}).
17822 @kindex J s (Agent Summary)
17823 @findex gnus-agent-fetch-series
17824 Download all processable articles in this group.
17825 (@code{gnus-agent-fetch-series}).
17828 @kindex J u (Agent Summary)
17829 @findex gnus-agent-summary-fetch-group
17830 Download all downloadable articles in the current group
17831 (@code{gnus-agent-summary-fetch-group}).
17836 @node Server Agent Commands
17837 @subsubsection Server Agent Commands
17841 @kindex J a (Agent Server)
17842 @findex gnus-agent-add-server
17843 Add the current server to the list of servers covered by the Gnus Agent
17844 (@code{gnus-agent-add-server}).
17847 @kindex J r (Agent Server)
17848 @findex gnus-agent-remove-server
17849 Remove the current server from the list of servers covered by the Gnus
17850 Agent (@code{gnus-agent-remove-server}).
17855 @node Agent as Cache
17856 @subsection Agent as Cache
17858 When Gnus is plugged, it is not efficient to download headers or
17859 articles from the server again, if they are already stored in the
17860 Agent. So, Gnus normally only downloads headers once, and stores them
17861 in the Agent. These headers are later used when generating the summary
17862 buffer, regardless of whether you are plugged or unplugged. Articles
17863 are not cached in the Agent by default though (that would potentially
17864 consume lots of disk space), but if you have already downloaded an
17865 article into the Agent, Gnus will not download the article from the
17866 server again but use the locally stored copy instead.
17868 If you so desire, you can configure the agent (see @code{gnus-agent-cache}
17869 @pxref{Agent Variables}) to always download headers and articles while
17870 plugged. Gnus will almost certainly be slower, but it will be kept
17871 synchronized with the server. That last point probably won't make any
17872 sense if you are using a nntp or nnimap backend.
17875 @subsection Agent Expiry
17877 @vindex gnus-agent-expire-days
17878 @findex gnus-agent-expire
17879 @kindex M-x gnus-agent-expire
17880 @kindex M-x gnus-agent-expire-group
17881 @findex gnus-agent-expire-group
17882 @cindex Agent expiry
17883 @cindex Gnus Agent expiry
17886 The Agent backend, @code{nnagent}, doesn't handle expiry. Well, at
17887 least it doesn't handle it like other backends. Instead, there are
17888 special @code{gnus-agent-expire} and @code{gnus-agent-expire-group}
17889 commands that will expire all read articles that are older than
17890 @code{gnus-agent-expire-days} days. They can be run whenever you feel
17891 that you're running out of space. Neither are particularly fast or
17892 efficient, and it's not a particularly good idea to interrupt them (with
17893 @kbd{C-g} or anything else) once you've started one of them.
17895 Note that other functions, e.g. @code{gnus-request-expire-articles},
17896 might run @code{gnus-agent-expire} for you to keep the agent
17897 synchronized with the group.
17899 The agent parameter @code{agent-enable-expiration} may be used to
17900 prevent expiration in selected groups.
17902 @vindex gnus-agent-expire-all
17903 If @code{gnus-agent-expire-all} is non-@code{nil}, the agent
17904 expiration commands will expire all articles---unread, read, ticked
17905 and dormant. If @code{nil} (which is the default), only read articles
17906 are eligible for expiry, and unread, ticked and dormant articles will
17907 be kept indefinitely.
17909 If you find that some articles eligible for expiry are never expired,
17910 perhaps some Gnus Agent files are corrupted. There's are special
17911 commands, @code{gnus-agent-regenerate} and
17912 @code{gnus-agent-regenerate-group}, to fix possible problems.
17914 @node Agent Regeneration
17915 @subsection Agent Regeneration
17917 @cindex Agent Regeneration
17918 @cindex Gnus Agent Regeneration
17919 @cindex regeneration
17921 The local data structures used by @code{nnagent} may become corrupted
17922 due to certain exceptional conditions. When this happens,
17923 @code{nnagent} functionality may degrade or even fail. The solution
17924 to this problem is to repair the local data structures by removing all
17925 internal inconsistencies.
17927 For example, if your connection to your server is lost while
17928 downloaded articles into the agent, the local data structures will not
17929 know about articles successfully downloaded prior to the connection
17930 failure. Running @code{gnus-agent-regenerate} or
17931 @code{gnus-agent-regenerate-group} will update the data structures
17932 such that you don't need to download these articles a second time.
17934 @findex gnus-agent-regenerate
17935 @kindex M-x gnus-agent-regenerate
17936 The command @code{gnus-agent-regenerate} will perform
17937 @code{gnus-agent-regenerate-group} on every agentized group. While
17938 you can run @code{gnus-agent-regenerate} in any buffer, it is strongly
17939 recommended that you first close all summary buffers.
17941 @findex gnus-agent-regenerate-group
17942 @kindex M-x gnus-agent-regenerate-group
17943 The command @code{gnus-agent-regenerate-group} uses the local copies
17944 of individual articles to repair the local NOV(header) database. It
17945 then updates the internal data structures that document which articles
17946 are stored locally. An optional argument will mark articles in the
17949 @node Agent and IMAP
17950 @subsection Agent and IMAP
17952 The Agent works with any Gnus back end, including nnimap. However,
17953 since there are some conceptual differences between @sc{nntp} and
17954 @sc{imap}, this section (should) provide you with some information to
17955 make Gnus Agent work smoother as a @sc{imap} Disconnected Mode client.
17957 The first thing to keep in mind is that all flags (read, ticked, etc)
17958 are kept on the @sc{imap} server, rather than in @file{.newsrc} as is the
17959 case for nntp. Thus Gnus need to remember flag changes when
17960 disconnected, and synchronize these flags when you plug back in.
17962 Gnus keeps track of flag changes when reading nnimap groups under the
17963 Agent. When you plug back in, Gnus will check if you have any changed
17964 any flags and ask if you wish to synchronize these with the server.
17965 The behavior is customizable by @code{gnus-agent-synchronize-flags}.
17967 @vindex gnus-agent-synchronize-flags
17968 If @code{gnus-agent-synchronize-flags} is @code{nil}, the Agent will
17969 never automatically synchronize flags. If it is @code{ask}, which is
17970 the default, the Agent will check if you made any changes and if so
17971 ask if you wish to synchronize these when you re-connect. If it has
17972 any other value, all flags will be synchronized automatically.
17974 If you do not wish to synchronize flags automatically when you
17975 re-connect, you can do it manually with the
17976 @code{gnus-agent-synchronize-flags} command that is bound to @kbd{J Y}
17977 in the group buffer.
17979 Some things are currently not implemented in the Agent that you'd might
17980 expect from a disconnected @sc{imap} client, including:
17985 Copying/moving articles into nnimap groups when unplugged.
17988 Creating/deleting nnimap groups when unplugged.
17992 Technical note: the synchronization algorithm does not work by ``pushing''
17993 all local flags to the server, but rather incrementally update the
17994 server view of flags by changing only those flags that were changed by
17995 the user. Thus, if you set one flag on a article, quit the group and
17996 re-select the group and remove the flag; the flag will be set and
17997 removed from the server when you ``synchronize''. The queued flag
17998 operations can be found in the per-server @code{flags} file in the Agent
17999 directory. It's emptied when you synchronize flags.
18002 @node Outgoing Messages
18003 @subsection Outgoing Messages
18005 When Gnus is unplugged, all outgoing messages (both mail and news) are
18006 stored in the draft group ``queue'' (@pxref{Drafts}). You can view
18007 them there after posting, and edit them at will.
18009 When Gnus is plugged again, you can send the messages either from the
18010 draft group with the special commands available there, or you can use
18011 the @kbd{J S} command in the group buffer to send all the sendable
18012 messages in the draft group.
18016 @node Agent Variables
18017 @subsection Agent Variables
18020 @item gnus-agent-directory
18021 @vindex gnus-agent-directory
18022 Where the Gnus Agent will store its files. The default is
18023 @file{~/News/agent/}.
18025 @item gnus-agent-handle-level
18026 @vindex gnus-agent-handle-level
18027 Groups on levels (@pxref{Group Levels}) higher than this variable will
18028 be ignored by the Agent. The default is @code{gnus-level-subscribed},
18029 which means that only subscribed group will be considered by the Agent
18032 @item gnus-agent-plugged-hook
18033 @vindex gnus-agent-plugged-hook
18034 Hook run when connecting to the network.
18036 @item gnus-agent-unplugged-hook
18037 @vindex gnus-agent-unplugged-hook
18038 Hook run when disconnecting from the network.
18040 @item gnus-agent-fetched-hook
18041 @vindex gnus-agent-fetched-hook
18042 Hook run when finished fetching articles.
18044 @item gnus-agent-cache
18045 @vindex gnus-agent-cache
18046 Variable to control whether use the locally stored @sc{nov} and
18047 articles when plugged, e.g. essentially using the Agent as a cache.
18048 The default is non-nil, which means to use the Agent as a cache.
18050 @item gnus-agent-go-online
18051 @vindex gnus-agent-go-online
18052 If @code{gnus-agent-go-online} is @code{nil}, the Agent will never
18053 automatically switch offline servers into online status. If it is
18054 @code{ask}, the default, the Agent will ask if you wish to switch
18055 offline servers into online status when you re-connect. If it has any
18056 other value, all offline servers will be automatically switched into
18059 @item gnus-agent-mark-unread-after-downloaded
18060 @vindex gnus-agent-mark-unread-after-downloaded
18061 If @code{gnus-agent-mark-unread-after-downloaded} is non-@code{nil},
18062 mark articles as unread after downloading. This is usually a safe
18063 thing to do as the newly downloaded article has obviously not been
18064 read. The default is t.
18066 @item gnus-agent-consider-all-articles
18067 @vindex gnus-agent-consider-all-articles
18068 If @code{gnus-agent-consider-all-articles} is non-@code{nil}, the
18069 agent will fetch all missing headers. When @code{nil}, the agent will
18070 fetch only new headers. The default is @code{nil}.
18072 @item gnus-agent-max-fetch-size
18073 @vindex gnus-agent-max-fetch-size
18074 The agent fetches articles into a temporary buffer prior to parsing
18075 them into individual files. To avoid exceeding the max. buffer size,
18076 the agent alternates between fetching and parsing until all articles
18077 have been fetched. @code{gnus-agent-max-fetch-size} provides a size
18078 limit to control how often the cycling occurs. A large value improves
18079 performance. A small value minimizes the time lost should the
18080 connection be lost while fetching (You may need to run
18081 @code{gnus-agent-regenerate-group} to update the group's state.
18082 However, all articles parsed prior to loosing the connection will be
18083 available while unplugged). The default is 10M so it is unusual to
18086 @item gnus-server-unopen-status
18087 @vindex gnus-server-unopen-status
18088 Perhaps not a Agent variable, but closely related to the Agent, this
18089 variable says what will happen if Gnus cannot open a server. If the
18090 Agent is enabled, the default, @code{nil}, makes Gnus ask the user
18091 whether to deny the server or whether to unplug the agent. If the
18092 Agent is disabled, Gnus always simply deny the server. Other choices
18093 for this variable include @code{denied} and @code{offline} the latter
18094 is only valid if the Agent is used.
18096 @item gnus-auto-goto-ignores
18097 @vindex gnus-auto-goto-ignores
18098 Another variable that isn't a Agent variable, yet so closely related
18099 that most will look for it here, this variable tells the summary
18100 buffer how to maneuver around undownloaded (only headers stored in the
18101 agent) and unfetched (neither article nor headers stored) articles.
18103 The legal values are @code{nil} (maneuver to any article),
18104 @code{undownloaded} (maneuvering while unplugged ignores articles that
18105 have not been fetched), @code{always-undownloaded} (maneuvering always
18106 ignores articles that have not been fetched), @code{unfetched}
18107 (maneuvering ignores articles whose headers have not been fetched).
18112 @node Example Setup
18113 @subsection Example Setup
18115 If you don't want to read this manual, and you have a fairly standard
18116 setup, you may be able to use something like the following as your
18117 @file{~/.gnus.el} file to get started.
18120 ;;; Define how Gnus is to fetch news. We do this over @sc{nntp}
18121 ;;; from your ISP's server.
18122 (setq gnus-select-method '(nntp "news.your-isp.com"))
18124 ;;; Define how Gnus is to read your mail. We read mail from
18125 ;;; your ISP's POP server.
18126 (setq mail-sources '((pop :server "pop.your-isp.com")))
18128 ;;; Say how Gnus is to store the mail. We use nnml groups.
18129 (setq gnus-secondary-select-methods '((nnml "")))
18131 ;;; Make Gnus into an offline newsreader.
18132 ;;; (gnus-agentize) ; The obsolete setting.
18133 ;;; (setq gnus-agent t) ; Now the default.
18136 That should be it, basically. Put that in your @file{~/.gnus.el} file,
18137 edit to suit your needs, start up PPP (or whatever), and type @kbd{M-x
18140 If this is the first time you've run Gnus, you will be subscribed
18141 automatically to a few default newsgroups. You'll probably want to
18142 subscribe to more groups, and to do that, you have to query the
18143 @sc{nntp} server for a complete list of groups with the @kbd{A A}
18144 command. This usually takes quite a while, but you only have to do it
18147 After reading and parsing a while, you'll be presented with a list of
18148 groups. Subscribe to the ones you want to read with the @kbd{u}
18149 command. @kbd{l} to make all the killed groups disappear after you've
18150 subscribe to all the groups you want to read. (@kbd{A k} will bring
18151 back all the killed groups.)
18153 You can now read the groups at once, or you can download the articles
18154 with the @kbd{J s} command. And then read the rest of this manual to
18155 find out which of the other gazillion things you want to customize.
18158 @node Batching Agents
18159 @subsection Batching Agents
18160 @findex gnus-agent-batch
18162 Having the Gnus Agent fetch articles (and post whatever messages you've
18163 written) is quite easy once you've gotten things set up properly. The
18164 following shell script will do everything that is necessary:
18166 You can run a complete batch command from the command line with the
18167 following incantation:
18171 emacs -batch -l ~/.emacs -f -l ~/.gnus.el gnus-agent-batch >/dev/null 2>&1
18175 @node Agent Caveats
18176 @subsection Agent Caveats
18178 The Gnus Agent doesn't seem to work like most other offline
18179 newsreaders. Here are some common questions that some imaginary people
18183 @item If I read an article while plugged, do they get entered into the Agent?
18185 @strong{No}. If you want this behaviour, add
18186 @code{gnus-agent-fetch-selected-article} to
18187 @code{gnus-select-article-hook}.
18189 @item If I read an article while plugged, and the article already exists in
18190 the Agent, will it get downloaded once more?
18192 @strong{No}, unless @code{gnus-agent-cache} is @code{nil}.
18196 In short, when Gnus is unplugged, it only looks into the locally stored
18197 articles; when it's plugged, it talks to your ISP and may also use the
18198 locally stored articles.
18205 Other people use @dfn{kill files}, but we here at Gnus Towers like
18206 scoring better than killing, so we'd rather switch than fight. They do
18207 something completely different as well, so sit up straight and pay
18210 @vindex gnus-summary-mark-below
18211 All articles have a default score (@code{gnus-summary-default-score}),
18212 which is 0 by default. This score may be raised or lowered either
18213 interactively or by score files. Articles that have a score lower than
18214 @code{gnus-summary-mark-below} are marked as read.
18216 Gnus will read any @dfn{score files} that apply to the current group
18217 before generating the summary buffer.
18219 There are several commands in the summary buffer that insert score
18220 entries based on the current article. You can, for instance, ask Gnus to
18221 lower or increase the score of all articles with a certain subject.
18223 There are two sorts of scoring entries: Permanent and temporary.
18224 Temporary score entries are self-expiring entries. Any entries that are
18225 temporary and have not been used for, say, a week, will be removed
18226 silently to help keep the sizes of the score files down.
18229 * Summary Score Commands:: Adding score entries for the current group.
18230 * Group Score Commands:: General score commands.
18231 * Score Variables:: Customize your scoring. (My, what terminology).
18232 * Score File Format:: What a score file may contain.
18233 * Score File Editing:: You can edit score files by hand as well.
18234 * Adaptive Scoring:: Big Sister Gnus knows what you read.
18235 * Home Score File:: How to say where new score entries are to go.
18236 * Followups To Yourself:: Having Gnus notice when people answer you.
18237 * Scoring On Other Headers:: Scoring on non-standard headers.
18238 * Scoring Tips:: How to score effectively.
18239 * Reverse Scoring:: That problem child of old is not problem.
18240 * Global Score Files:: Earth-spanning, ear-splitting score files.
18241 * Kill Files:: They are still here, but they can be ignored.
18242 * Converting Kill Files:: Translating kill files to score files.
18243 * GroupLens:: Getting predictions on what you like to read.
18244 * Advanced Scoring:: Using logical expressions to build score rules.
18245 * Score Decays:: It can be useful to let scores wither away.
18249 @node Summary Score Commands
18250 @section Summary Score Commands
18251 @cindex score commands
18253 The score commands that alter score entries do not actually modify real
18254 score files. That would be too inefficient. Gnus maintains a cache of
18255 previously loaded score files, one of which is considered the
18256 @dfn{current score file alist}. The score commands simply insert
18257 entries into this list, and upon group exit, this list is saved.
18259 The current score file is by default the group's local score file, even
18260 if no such score file actually exists. To insert score commands into
18261 some other score file (e.g. @file{all.SCORE}), you must first make this
18262 score file the current one.
18264 General score commands that don't actually change the score file:
18269 @kindex V s (Summary)
18270 @findex gnus-summary-set-score
18271 Set the score of the current article (@code{gnus-summary-set-score}).
18274 @kindex V S (Summary)
18275 @findex gnus-summary-current-score
18276 Display the score of the current article
18277 (@code{gnus-summary-current-score}).
18280 @kindex V t (Summary)
18281 @findex gnus-score-find-trace
18282 Display all score rules that have been used on the current article
18283 (@code{gnus-score-find-trace}). In the @code{*Score Trace*} buffer, you
18284 can use @kbd{q} to quit. @kbd{e} edits the corresponding score file.
18285 When point is on a string within the match element, @kbd{e} will try to
18286 bring you to this string in the score file.
18289 @kindex V w (Summary)
18290 @findex gnus-score-find-favourite-words
18291 List words used in scoring (@code{gnus-score-find-favourite-words}).
18294 @kindex V R (Summary)
18295 @findex gnus-summary-rescore
18296 Run the current summary through the scoring process
18297 (@code{gnus-summary-rescore}). This might be useful if you're playing
18298 around with your score files behind Gnus' back and want to see the
18299 effect you're having.
18302 @kindex V c (Summary)
18303 @findex gnus-score-change-score-file
18304 Make a different score file the current
18305 (@code{gnus-score-change-score-file}).
18308 @kindex V e (Summary)
18309 @findex gnus-score-edit-current-scores
18310 Edit the current score file (@code{gnus-score-edit-current-scores}).
18311 You will be popped into a @code{gnus-score-mode} buffer (@pxref{Score
18315 @kindex V f (Summary)
18316 @findex gnus-score-edit-file
18317 Edit a score file and make this score file the current one
18318 (@code{gnus-score-edit-file}).
18321 @kindex V F (Summary)
18322 @findex gnus-score-flush-cache
18323 Flush the score cache (@code{gnus-score-flush-cache}). This is useful
18324 after editing score files.
18327 @kindex V C (Summary)
18328 @findex gnus-score-customize
18329 Customize a score file in a visually pleasing manner
18330 (@code{gnus-score-customize}).
18334 The rest of these commands modify the local score file.
18339 @kindex V m (Summary)
18340 @findex gnus-score-set-mark-below
18341 Prompt for a score, and mark all articles with a score below this as
18342 read (@code{gnus-score-set-mark-below}).
18345 @kindex V x (Summary)
18346 @findex gnus-score-set-expunge-below
18347 Prompt for a score, and add a score rule to the current score file to
18348 expunge all articles below this score
18349 (@code{gnus-score-set-expunge-below}).
18352 The keystrokes for actually making score entries follow a very regular
18353 pattern, so there's no need to list all the commands. (Hundreds of
18356 @findex gnus-summary-increase-score
18357 @findex gnus-summary-lower-score
18361 The first key is either @kbd{I} (upper case i) for increasing the score
18362 or @kbd{L} for lowering the score.
18364 The second key says what header you want to score on. The following
18365 keys are available:
18369 Score on the author name.
18372 Score on the subject line.
18375 Score on the @code{Xref} line---i.e., the cross-posting line.
18378 Score on the @code{References} line.
18384 Score on the number of lines.
18387 Score on the @code{Message-ID} header.
18390 Score on an ``extra'' header, that is, one of those in gnus-extra-headers,
18391 if your @sc{nntp} server tracks additional header data in overviews.
18394 Score on followups---this matches the author name, and adds scores to
18395 the followups to this author. (Using this key leads to the creation of
18396 @file{ADAPT} files.)
18405 Score on thread. (Using this key leads to the creation of @file{ADAPT}
18411 The third key is the match type. Which match types are valid depends on
18412 what headers you are scoring on.
18424 Substring matching.
18427 Fuzzy matching (@pxref{Fuzzy Matching}).
18456 Greater than number.
18461 The fourth and usually final key says whether this is a temporary (i.e.,
18462 expiring) score entry, or a permanent (i.e., non-expiring) score entry,
18463 or whether it is to be done immediately, without adding to the score
18468 Temporary score entry.
18471 Permanent score entry.
18474 Immediately scoring.
18478 If you are scoring on `e' (extra) headers, you will then be prompted for
18479 the header name on which you wish to score. This must be a header named
18480 in gnus-extra-headers, and @samp{TAB} completion is available.
18484 So, let's say you want to increase the score on the current author with
18485 exact matching permanently: @kbd{I a e p}. If you want to lower the
18486 score based on the subject line, using substring matching, and make a
18487 temporary score entry: @kbd{L s s t}. Pretty easy.
18489 To make things a bit more complicated, there are shortcuts. If you use
18490 a capital letter on either the second or third keys, Gnus will use
18491 defaults for the remaining one or two keystrokes. The defaults are
18492 ``substring'' and ``temporary''. So @kbd{I A} is the same as @kbd{I a s
18493 t}, and @kbd{I a R} is the same as @kbd{I a r t}.
18495 These functions take both the numerical prefix and the symbolic prefix
18496 (@pxref{Symbolic Prefixes}). A numerical prefix says how much to lower
18497 (or increase) the score of the article. A symbolic prefix of @code{a}
18498 says to use the @file{all.SCORE} file for the command instead of the
18499 current score file.
18501 @vindex gnus-score-mimic-keymap
18502 The @code{gnus-score-mimic-keymap} says whether these commands will
18503 pretend they are keymaps or not.
18506 @node Group Score Commands
18507 @section Group Score Commands
18508 @cindex group score commands
18510 There aren't many of these as yet, I'm afraid.
18515 @kindex W f (Group)
18516 @findex gnus-score-flush-cache
18517 Gnus maintains a cache of score alists to avoid having to reload them
18518 all the time. This command will flush the cache
18519 (@code{gnus-score-flush-cache}).
18523 You can do scoring from the command line by saying something like:
18525 @findex gnus-batch-score
18526 @cindex batch scoring
18528 $ emacs -batch -l ~/.emacs -l ~/.gnus.el -f gnus-batch-score
18532 @node Score Variables
18533 @section Score Variables
18534 @cindex score variables
18538 @item gnus-use-scoring
18539 @vindex gnus-use-scoring
18540 If @code{nil}, Gnus will not check for score files, and will not, in
18541 general, do any score-related work. This is @code{t} by default.
18543 @item gnus-kill-killed
18544 @vindex gnus-kill-killed
18545 If this variable is @code{nil}, Gnus will never apply score files to
18546 articles that have already been through the kill process. While this
18547 may save you lots of time, it also means that if you apply a kill file
18548 to a group, and then change the kill file and want to run it over you
18549 group again to kill more articles, it won't work. You have to set this
18550 variable to @code{t} to do that. (It is @code{t} by default.)
18552 @item gnus-kill-files-directory
18553 @vindex gnus-kill-files-directory
18554 All kill and score files will be stored in this directory, which is
18555 initialized from the @code{SAVEDIR} environment variable by default.
18556 This is @file{~/News/} by default.
18558 @item gnus-score-file-suffix
18559 @vindex gnus-score-file-suffix
18560 Suffix to add to the group name to arrive at the score file name
18561 (@file{SCORE} by default.)
18563 @item gnus-score-uncacheable-files
18564 @vindex gnus-score-uncacheable-files
18565 @cindex score cache
18566 All score files are normally cached to avoid excessive re-loading of
18567 score files. However, if this might make your Emacs grow big and
18568 bloated, so this regexp can be used to weed out score files unlikely
18569 to be needed again. It would be a bad idea to deny caching of
18570 @file{all.SCORE}, while it might be a good idea to not cache
18571 @file{comp.infosystems.www.authoring.misc.ADAPT}. In fact, this
18572 variable is @samp{ADAPT$} by default, so no adaptive score files will
18575 @item gnus-save-score
18576 @vindex gnus-save-score
18577 If you have really complicated score files, and do lots of batch
18578 scoring, then you might set this variable to @code{t}. This will make
18579 Gnus save the scores into the @file{.newsrc.eld} file.
18581 If you do not set this to @code{t}, then manual scores (like those set
18582 with @kbd{V s} (@code{gnus-summary-set-score})) will not be preserved
18583 across group visits.
18585 @item gnus-score-interactive-default-score
18586 @vindex gnus-score-interactive-default-score
18587 Score used by all the interactive raise/lower commands to raise/lower
18588 score with. Default is 1000, which may seem excessive, but this is to
18589 ensure that the adaptive scoring scheme gets enough room to play with.
18590 We don't want the small changes from the adaptive scoring to overwrite
18591 manually entered data.
18593 @item gnus-summary-default-score
18594 @vindex gnus-summary-default-score
18595 Default score of an article, which is 0 by default.
18597 @item gnus-summary-expunge-below
18598 @vindex gnus-summary-expunge-below
18599 Don't display the summary lines of articles that have scores lower than
18600 this variable. This is @code{nil} by default, which means that no
18601 articles will be hidden. This variable is local to the summary buffers,
18602 and has to be set from @code{gnus-summary-mode-hook}.
18604 @item gnus-score-over-mark
18605 @vindex gnus-score-over-mark
18606 Mark (in the third column) used for articles with a score over the
18607 default. Default is @samp{+}.
18609 @item gnus-score-below-mark
18610 @vindex gnus-score-below-mark
18611 Mark (in the third column) used for articles with a score below the
18612 default. Default is @samp{-}.
18614 @item gnus-score-find-score-files-function
18615 @vindex gnus-score-find-score-files-function
18616 Function used to find score files for the current group. This function
18617 is called with the name of the group as the argument.
18619 Predefined functions available are:
18622 @item gnus-score-find-single
18623 @findex gnus-score-find-single
18624 Only apply the group's own score file.
18626 @item gnus-score-find-bnews
18627 @findex gnus-score-find-bnews
18628 Apply all score files that match, using bnews syntax. This is the
18629 default. If the current group is @samp{gnu.emacs.gnus}, for instance,
18630 @file{all.emacs.all.SCORE}, @file{not.alt.all.SCORE} and
18631 @file{gnu.all.SCORE} would all apply. In short, the instances of
18632 @samp{all} in the score file names are translated into @samp{.*}, and
18633 then a regexp match is done.
18635 This means that if you have some score entries that you want to apply to
18636 all groups, then you put those entries in the @file{all.SCORE} file.
18638 The score files are applied in a semi-random order, although Gnus will
18639 try to apply the more general score files before the more specific score
18640 files. It does this by looking at the number of elements in the score
18641 file names---discarding the @samp{all} elements.
18643 @item gnus-score-find-hierarchical
18644 @findex gnus-score-find-hierarchical
18645 Apply all score files from all the parent groups. This means that you
18646 can't have score files like @file{all.SCORE}, but you can have
18647 @file{SCORE}, @file{comp.SCORE} and @file{comp.emacs.SCORE} for each
18651 This variable can also be a list of functions. In that case, all
18652 these functions will be called with the group name as argument, and
18653 all the returned lists of score files will be applied. These
18654 functions can also return lists of lists of score alists directly. In
18655 that case, the functions that return these non-file score alists
18656 should probably be placed before the ``real'' score file functions, to
18657 ensure that the last score file returned is the local score file.
18660 For example, to do hierarchical scoring but use a non-server-specific
18661 overall score file, you could use the value
18663 (list (lambda (group) ("all.SCORE"))
18664 'gnus-score-find-hierarchical)
18667 @item gnus-score-expiry-days
18668 @vindex gnus-score-expiry-days
18669 This variable says how many days should pass before an unused score file
18670 entry is expired. If this variable is @code{nil}, no score file entries
18671 are expired. It's 7 by default.
18673 @item gnus-update-score-entry-dates
18674 @vindex gnus-update-score-entry-dates
18675 If this variable is non-@code{nil}, temporary score entries that have
18676 been triggered (matched) will have their dates updated. (This is how Gnus
18677 controls expiry---all non-matched-entries will become too old while
18678 matched entries will stay fresh and young.) However, if you set this
18679 variable to @code{nil}, even matched entries will grow old and will
18680 have to face that oh-so grim reaper.
18682 @item gnus-score-after-write-file-function
18683 @vindex gnus-score-after-write-file-function
18684 Function called with the name of the score file just written.
18686 @item gnus-score-thread-simplify
18687 @vindex gnus-score-thread-simplify
18688 If this variable is non-@code{nil}, article subjects will be simplified
18689 for subject scoring purposes in the same manner as with
18690 threading---according to the current value of
18691 gnus-simplify-subject-functions. If the scoring entry uses
18692 @code{substring} or @code{exact} matching, the match will also be
18693 simplified in this manner.
18698 @node Score File Format
18699 @section Score File Format
18700 @cindex score file format
18702 A score file is an @code{emacs-lisp} file that normally contains just a
18703 single form. Casual users are not expected to edit these files;
18704 everything can be changed from the summary buffer.
18706 Anyway, if you'd like to dig into it yourself, here's an example:
18710 ("Lars Ingebrigtsen" -10000)
18712 ("larsi\\|lmi" -50000 nil R))
18714 ("Ding is Badd" nil 728373))
18716 ("alt.politics" -1000 728372 s))
18721 (mark-and-expunge -10)
18725 (files "/hom/larsi/News/gnu.SCORE")
18726 (exclude-files "all.SCORE")
18727 (local (gnus-newsgroup-auto-expire t)
18728 (gnus-summary-make-false-root empty))
18732 This example demonstrates most score file elements. For a different
18733 approach, see @pxref{Advanced Scoring}.
18735 Even though this looks much like lisp code, nothing here is actually
18736 @code{eval}ed. The lisp reader is used to read this form, though, so it
18737 has to be valid syntactically, if not semantically.
18739 Six keys are supported by this alist:
18744 If the key is a string, it is the name of the header to perform the
18745 match on. Scoring can only be performed on these eight headers:
18746 @code{From}, @code{Subject}, @code{References}, @code{Message-ID},
18747 @code{Xref}, @code{Lines}, @code{Chars} and @code{Date}. In addition to
18748 these headers, there are three strings to tell Gnus to fetch the entire
18749 article and do the match on larger parts of the article: @code{Body}
18750 will perform the match on the body of the article, @code{Head} will
18751 perform the match on the head of the article, and @code{All} will
18752 perform the match on the entire article. Note that using any of these
18753 last three keys will slow down group entry @emph{considerably}. The
18754 final ``header'' you can score on is @code{Followup}. These score
18755 entries will result in new score entries being added for all follow-ups
18756 to articles that matches these score entries.
18758 Following this key is a arbitrary number of score entries, where each
18759 score entry has one to four elements.
18763 The first element is the @dfn{match element}. On most headers this will
18764 be a string, but on the Lines and Chars headers, this must be an
18768 If the second element is present, it should be a number---the @dfn{score
18769 element}. This number should be an integer in the neginf to posinf
18770 interval. This number is added to the score of the article if the match
18771 is successful. If this element is not present, the
18772 @code{gnus-score-interactive-default-score} number will be used
18773 instead. This is 1000 by default.
18776 If the third element is present, it should be a number---the @dfn{date
18777 element}. This date says when the last time this score entry matched,
18778 which provides a mechanism for expiring the score entries. It this
18779 element is not present, the score entry is permanent. The date is
18780 represented by the number of days since December 31, 1 BCE.
18783 If the fourth element is present, it should be a symbol---the @dfn{type
18784 element}. This element specifies what function should be used to see
18785 whether this score entry matches the article. What match types that can
18786 be used depends on what header you wish to perform the match on.
18789 @item From, Subject, References, Xref, Message-ID
18790 For most header types, there are the @code{r} and @code{R} (regexp), as
18791 well as @code{s} and @code{S} (substring) types, and @code{e} and
18792 @code{E} (exact match), and @code{w} (word match) types. If this
18793 element is not present, Gnus will assume that substring matching should
18794 be used. @code{R}, @code{S}, and @code{E} differ from the others in
18795 that the matches will be done in a case-sensitive manner. All these
18796 one-letter types are really just abbreviations for the @code{regexp},
18797 @code{string}, @code{exact}, and @code{word} types, which you can use
18798 instead, if you feel like.
18801 Just as for the standard string overview headers, if you are using
18802 gnus-extra-headers, you can score on these headers' values. In this
18803 case, there is a 5th element in the score entry, being the name of the
18804 header to be scored. The following entry is useful in your
18805 @file{all.SCORE} file in case of spam attacks from a single origin host,
18806 if your @sc{nntp} server tracks NNTP-Posting-Host in overviews:
18809 ("111.222.333.444" -1000 nil s "NNTP-Posting-Host")
18813 These two headers use different match types: @code{<}, @code{>},
18814 @code{=}, @code{>=} and @code{<=}.
18816 These predicates are true if
18819 (PREDICATE HEADER MATCH)
18822 evaluates to non-@code{nil}. For instance, the advanced match
18823 @code{("lines" 4 <)} (@pxref{Advanced Scoring}) will result in the
18830 Or to put it another way: When using @code{<} on @code{Lines} with 4 as
18831 the match, we get the score added if the article has less than 4 lines.
18832 (It's easy to get confused and think it's the other way around. But
18833 it's not. I think.)
18835 When matching on @code{Lines}, be careful because some back ends (like
18836 @code{nndir}) do not generate @code{Lines} header, so every article ends
18837 up being marked as having 0 lines. This can lead to strange results if
18838 you happen to lower score of the articles with few lines.
18841 For the Date header we have three kinda silly match types:
18842 @code{before}, @code{at} and @code{after}. I can't really imagine this
18843 ever being useful, but, like, it would feel kinda silly not to provide
18844 this function. Just in case. You never know. Better safe than sorry.
18845 Once burnt, twice shy. Don't judge a book by its cover. Never not have
18846 sex on a first date. (I have been told that at least one person, and I
18847 quote, ``found this function indispensable'', however.)
18851 A more useful match type is @code{regexp}. With it, you can match the
18852 date string using a regular expression. The date is normalized to
18853 ISO8601 compact format first---@var{YYYYMMDD}@code{T}@var{HHMMSS}. If
18854 you want to match all articles that have been posted on April 1st in
18855 every year, you could use @samp{....0401.........} as a match string,
18856 for instance. (Note that the date is kept in its original time zone, so
18857 this will match articles that were posted when it was April 1st where
18858 the article was posted from. Time zones are such wholesome fun for the
18861 @item Head, Body, All
18862 These three match keys use the same match types as the @code{From} (etc)
18866 This match key is somewhat special, in that it will match the
18867 @code{From} header, and affect the score of not only the matching
18868 articles, but also all followups to the matching articles. This allows
18869 you e.g. increase the score of followups to your own articles, or
18870 decrease the score of followups to the articles of some known
18871 trouble-maker. Uses the same match types as the @code{From} header
18872 uses. (Using this match key will lead to creation of @file{ADAPT}
18876 This match key works along the same lines as the @code{Followup} match
18877 key. If you say that you want to score on a (sub-)thread started by an
18878 article with a @code{Message-ID} @var{x}, then you add a @samp{thread}
18879 match. This will add a new @samp{thread} match for each article that
18880 has @var{x} in its @code{References} header. (These new @samp{thread}
18881 matches will use the @code{Message-ID}s of these matching articles.)
18882 This will ensure that you can raise/lower the score of an entire thread,
18883 even though some articles in the thread may not have complete
18884 @code{References} headers. Note that using this may lead to
18885 undeterministic scores of the articles in the thread. (Using this match
18886 key will lead to creation of @file{ADAPT} files.)
18890 @cindex Score File Atoms
18892 The value of this entry should be a number. Any articles with a score
18893 lower than this number will be marked as read.
18896 The value of this entry should be a number. Any articles with a score
18897 lower than this number will be removed from the summary buffer.
18899 @item mark-and-expunge
18900 The value of this entry should be a number. Any articles with a score
18901 lower than this number will be marked as read and removed from the
18904 @item thread-mark-and-expunge
18905 The value of this entry should be a number. All articles that belong to
18906 a thread that has a total score below this number will be marked as read
18907 and removed from the summary buffer. @code{gnus-thread-score-function}
18908 says how to compute the total score for a thread.
18911 The value of this entry should be any number of file names. These files
18912 are assumed to be score files as well, and will be loaded the same way
18915 @item exclude-files
18916 The clue of this entry should be any number of files. These files will
18917 not be loaded, even though they would normally be so, for some reason or
18921 The value of this entry will be @code{eval}el. This element will be
18922 ignored when handling global score files.
18925 Read-only score files will not be updated or saved. Global score files
18926 should feature this atom (@pxref{Global Score Files}). (Note:
18927 @dfn{Global} here really means @dfn{global}; not your personal
18928 apply-to-all-groups score files.)
18931 The value of this entry should be a number. Articles that do not have
18932 parents will get this number added to their scores. Imagine you follow
18933 some high-volume newsgroup, like @samp{comp.lang.c}. Most likely you
18934 will only follow a few of the threads, also want to see any new threads.
18936 You can do this with the following two score file entries:
18940 (mark-and-expunge -100)
18943 When you enter the group the first time, you will only see the new
18944 threads. You then raise the score of the threads that you find
18945 interesting (with @kbd{I T} or @kbd{I S}), and ignore (@kbd{C y}) the
18946 rest. Next time you enter the group, you will see new articles in the
18947 interesting threads, plus any new threads.
18949 I.e.---the orphan score atom is for high-volume groups where a few
18950 interesting threads which can't be found automatically by ordinary
18951 scoring rules exist.
18954 This entry controls the adaptive scoring. If it is @code{t}, the
18955 default adaptive scoring rules will be used. If it is @code{ignore}, no
18956 adaptive scoring will be performed on this group. If it is a list, this
18957 list will be used as the adaptive scoring rules. If it isn't present,
18958 or is something other than @code{t} or @code{ignore}, the default
18959 adaptive scoring rules will be used. If you want to use adaptive
18960 scoring on most groups, you'd set @code{gnus-use-adaptive-scoring} to
18961 @code{t}, and insert an @code{(adapt ignore)} in the groups where you do
18962 not want adaptive scoring. If you only want adaptive scoring in a few
18963 groups, you'd set @code{gnus-use-adaptive-scoring} to @code{nil}, and
18964 insert @code{(adapt t)} in the score files of the groups where you want
18968 All adaptive score entries will go to the file named by this entry. It
18969 will also be applied when entering the group. This atom might be handy
18970 if you want to adapt on several groups at once, using the same adaptive
18971 file for a number of groups.
18974 @cindex local variables
18975 The value of this entry should be a list of @code{(@var{var}
18976 @var{value})} pairs. Each @var{var} will be made buffer-local to the
18977 current summary buffer, and set to the value specified. This is a
18978 convenient, if somewhat strange, way of setting variables in some
18979 groups if you don't like hooks much. Note that the @var{value} won't
18984 @node Score File Editing
18985 @section Score File Editing
18987 You normally enter all scoring commands from the summary buffer, but you
18988 might feel the urge to edit them by hand as well, so we've supplied you
18989 with a mode for that.
18991 It's simply a slightly customized @code{emacs-lisp} mode, with these
18992 additional commands:
18997 @kindex C-c C-c (Score)
18998 @findex gnus-score-edit-done
18999 Save the changes you have made and return to the summary buffer
19000 (@code{gnus-score-edit-done}).
19003 @kindex C-c C-d (Score)
19004 @findex gnus-score-edit-insert-date
19005 Insert the current date in numerical format
19006 (@code{gnus-score-edit-insert-date}). This is really the day number, if
19007 you were wondering.
19010 @kindex C-c C-p (Score)
19011 @findex gnus-score-pretty-print
19012 The adaptive score files are saved in an unformatted fashion. If you
19013 intend to read one of these files, you want to @dfn{pretty print} it
19014 first. This command (@code{gnus-score-pretty-print}) does that for
19019 Type @kbd{M-x gnus-score-mode} to use this mode.
19021 @vindex gnus-score-mode-hook
19022 @code{gnus-score-menu-hook} is run in score mode buffers.
19024 In the summary buffer you can use commands like @kbd{V f} and @kbd{V
19025 e} to begin editing score files.
19028 @node Adaptive Scoring
19029 @section Adaptive Scoring
19030 @cindex adaptive scoring
19032 If all this scoring is getting you down, Gnus has a way of making it all
19033 happen automatically---as if by magic. Or rather, as if by artificial
19034 stupidity, to be precise.
19036 @vindex gnus-use-adaptive-scoring
19037 When you read an article, or mark an article as read, or kill an
19038 article, you leave marks behind. On exit from the group, Gnus can sniff
19039 these marks and add score elements depending on what marks it finds.
19040 You turn on this ability by setting @code{gnus-use-adaptive-scoring} to
19041 @code{t} or @code{(line)}. If you want score adaptively on separate
19042 words appearing in the subjects, you should set this variable to
19043 @code{(word)}. If you want to use both adaptive methods, set this
19044 variable to @code{(word line)}.
19046 @vindex gnus-default-adaptive-score-alist
19047 To give you complete control over the scoring process, you can customize
19048 the @code{gnus-default-adaptive-score-alist} variable. For instance, it
19049 might look something like this:
19052 (setq gnus-default-adaptive-score-alist
19053 '((gnus-unread-mark)
19054 (gnus-ticked-mark (from 4))
19055 (gnus-dormant-mark (from 5))
19056 (gnus-del-mark (from -4) (subject -1))
19057 (gnus-read-mark (from 4) (subject 2))
19058 (gnus-expirable-mark (from -1) (subject -1))
19059 (gnus-killed-mark (from -1) (subject -3))
19060 (gnus-kill-file-mark)
19061 (gnus-ancient-mark)
19062 (gnus-low-score-mark)
19063 (gnus-catchup-mark (from -1) (subject -1))))
19066 As you see, each element in this alist has a mark as a key (either a
19067 variable name or a ``real'' mark---a character). Following this key is
19068 a arbitrary number of header/score pairs. If there are no header/score
19069 pairs following the key, no adaptive scoring will be done on articles
19070 that have that key as the article mark. For instance, articles with
19071 @code{gnus-unread-mark} in the example above will not get adaptive score
19074 Each article can have only one mark, so just a single of these rules
19075 will be applied to each article.
19077 To take @code{gnus-del-mark} as an example---this alist says that all
19078 articles that have that mark (i.e., are marked with @samp{e}) will have a
19079 score entry added to lower based on the @code{From} header by -4, and
19080 lowered by @code{Subject} by -1. Change this to fit your prejudices.
19082 If you have marked 10 articles with the same subject with
19083 @code{gnus-del-mark}, the rule for that mark will be applied ten times.
19084 That means that that subject will get a score of ten times -1, which
19085 should be, unless I'm much mistaken, -10.
19087 If you have auto-expirable (mail) groups (@pxref{Expiring Mail}), all
19088 the read articles will be marked with the @samp{E} mark. This'll
19089 probably make adaptive scoring slightly impossible, so auto-expiring and
19090 adaptive scoring doesn't really mix very well.
19092 The headers you can score on are @code{from}, @code{subject},
19093 @code{message-id}, @code{references}, @code{xref}, @code{lines},
19094 @code{chars} and @code{date}. In addition, you can score on
19095 @code{followup}, which will create an adaptive score entry that matches
19096 on the @code{References} header using the @code{Message-ID} of the
19097 current article, thereby matching the following thread.
19099 If you use this scheme, you should set the score file atom @code{mark}
19100 to something small---like -300, perhaps, to avoid having small random
19101 changes result in articles getting marked as read.
19103 After using adaptive scoring for a week or so, Gnus should start to
19104 become properly trained and enhance the authors you like best, and kill
19105 the authors you like least, without you having to say so explicitly.
19107 You can control what groups the adaptive scoring is to be performed on
19108 by using the score files (@pxref{Score File Format}). This will also
19109 let you use different rules in different groups.
19111 @vindex gnus-adaptive-file-suffix
19112 The adaptive score entries will be put into a file where the name is the
19113 group name with @code{gnus-adaptive-file-suffix} appended. The default
19116 @vindex gnus-score-exact-adapt-limit
19117 When doing adaptive scoring, substring or fuzzy matching would probably
19118 give you the best results in most cases. However, if the header one
19119 matches is short, the possibility for false positives is great, so if
19120 the length of the match is less than
19121 @code{gnus-score-exact-adapt-limit}, exact matching will be used. If
19122 this variable is @code{nil}, exact matching will always be used to avoid
19125 @vindex gnus-default-adaptive-word-score-alist
19126 As mentioned above, you can adapt either on individual words or entire
19127 headers. If you adapt on words, the
19128 @code{gnus-default-adaptive-word-score-alist} variable says what score
19129 each instance of a word should add given a mark.
19132 (setq gnus-default-adaptive-word-score-alist
19133 `((,gnus-read-mark . 30)
19134 (,gnus-catchup-mark . -10)
19135 (,gnus-killed-mark . -20)
19136 (,gnus-del-mark . -15)))
19139 This is the default value. If you have adaption on words enabled, every
19140 word that appears in subjects of articles marked with
19141 @code{gnus-read-mark} will result in a score rule that increase the
19142 score with 30 points.
19144 @vindex gnus-default-ignored-adaptive-words
19145 @vindex gnus-ignored-adaptive-words
19146 Words that appear in the @code{gnus-default-ignored-adaptive-words} list
19147 will be ignored. If you wish to add more words to be ignored, use the
19148 @code{gnus-ignored-adaptive-words} list instead.
19150 @vindex gnus-adaptive-word-length-limit
19151 Some may feel that short words shouldn't count when doing adaptive
19152 scoring. If so, you may set @code{gnus-adaptive-word-length-limit} to
19153 an integer. Words shorter than this number will be ignored. This
19154 variable defaults to @code{nil}.
19156 @vindex gnus-adaptive-word-syntax-table
19157 When the scoring is done, @code{gnus-adaptive-word-syntax-table} is the
19158 syntax table in effect. It is similar to the standard syntax table, but
19159 it considers numbers to be non-word-constituent characters.
19161 @vindex gnus-adaptive-word-minimum
19162 If @code{gnus-adaptive-word-minimum} is set to a number, the adaptive
19163 word scoring process will never bring down the score of an article to
19164 below this number. The default is @code{nil}.
19166 @vindex gnus-adaptive-word-no-group-words
19167 If @code{gnus-adaptive-word-no-group-words} is set to @code{t}, gnus
19168 won't adaptively word score any of the words in the group name. Useful
19169 for groups like @samp{comp.editors.emacs}, where most of the subject
19170 lines contain the word @samp{emacs}.
19172 After using this scheme for a while, it might be nice to write a
19173 @code{gnus-psychoanalyze-user} command to go through the rules and see
19174 what words you like and what words you don't like. Or perhaps not.
19176 Note that the adaptive word scoring thing is highly experimental and is
19177 likely to change in the future. Initial impressions seem to indicate
19178 that it's totally useless as it stands. Some more work (involving more
19179 rigorous statistical methods) will have to be done to make this useful.
19182 @node Home Score File
19183 @section Home Score File
19185 The score file where new score file entries will go is called the
19186 @dfn{home score file}. This is normally (and by default) the score file
19187 for the group itself. For instance, the home score file for
19188 @samp{gnu.emacs.gnus} is @file{gnu.emacs.gnus.SCORE}.
19190 However, this may not be what you want. It is often convenient to share
19191 a common home score file among many groups---all @samp{emacs} groups
19192 could perhaps use the same home score file.
19194 @vindex gnus-home-score-file
19195 The variable that controls this is @code{gnus-home-score-file}. It can
19200 A string. Then this file will be used as the home score file for all
19204 A function. The result of this function will be used as the home score
19205 file. The function will be called with the name of the group as the
19209 A list. The elements in this list can be:
19213 @code{(@var{regexp} @var{file-name})}. If the @var{regexp} matches the
19214 group name, the @var{file-name} will be used as the home score file.
19217 A function. If the function returns non-nil, the result will be used as
19218 the home score file.
19221 A string. Use the string as the home score file.
19224 The list will be traversed from the beginning towards the end looking
19229 So, if you want to use just a single score file, you could say:
19232 (setq gnus-home-score-file
19233 "my-total-score-file.SCORE")
19236 If you want to use @file{gnu.SCORE} for all @samp{gnu} groups and
19237 @file{rec.SCORE} for all @samp{rec} groups (and so on), you can say:
19239 @findex gnus-hierarchial-home-score-file
19241 (setq gnus-home-score-file
19242 'gnus-hierarchial-home-score-file)
19245 This is a ready-made function provided for your convenience.
19246 Other functions include
19249 @item gnus-current-home-score-file
19250 @findex gnus-current-home-score-file
19251 Return the ``current'' regular score file. This will make scoring
19252 commands add entry to the ``innermost'' matching score file.
19256 If you want to have one score file for the @samp{emacs} groups and
19257 another for the @samp{comp} groups, while letting all other groups use
19258 their own home score files:
19261 (setq gnus-home-score-file
19262 ;; All groups that match the regexp "\\.emacs"
19263 '(("\\.emacs" "emacs.SCORE")
19264 ;; All the comp groups in one score file
19265 ("^comp" "comp.SCORE")))
19268 @vindex gnus-home-adapt-file
19269 @code{gnus-home-adapt-file} works exactly the same way as
19270 @code{gnus-home-score-file}, but says what the home adaptive score file
19271 is instead. All new adaptive file entries will go into the file
19272 specified by this variable, and the same syntax is allowed.
19274 In addition to using @code{gnus-home-score-file} and
19275 @code{gnus-home-adapt-file}, you can also use group parameters
19276 (@pxref{Group Parameters}) and topic parameters (@pxref{Topic
19277 Parameters}) to achieve much the same. Group and topic parameters take
19278 precedence over this variable.
19281 @node Followups To Yourself
19282 @section Followups To Yourself
19284 Gnus offers two commands for picking out the @code{Message-ID} header in
19285 the current buffer. Gnus will then add a score rule that scores using
19286 this @code{Message-ID} on the @code{References} header of other
19287 articles. This will, in effect, increase the score of all articles that
19288 respond to the article in the current buffer. Quite useful if you want
19289 to easily note when people answer what you've said.
19293 @item gnus-score-followup-article
19294 @findex gnus-score-followup-article
19295 This will add a score to articles that directly follow up your own
19298 @item gnus-score-followup-thread
19299 @findex gnus-score-followup-thread
19300 This will add a score to all articles that appear in a thread ``below''
19304 @vindex message-sent-hook
19305 These two functions are both primarily meant to be used in hooks like
19306 @code{message-sent-hook}, like this:
19308 (add-hook 'message-sent-hook 'gnus-score-followup-thread)
19312 If you look closely at your own @code{Message-ID}, you'll notice that
19313 the first two or three characters are always the same. Here's two of
19317 <x6u3u47icf.fsf@@eyesore.no>
19318 <x6sp9o7ibw.fsf@@eyesore.no>
19321 So ``my'' ident on this machine is @samp{x6}. This can be
19322 exploited---the following rule will raise the score on all followups to
19327 ("<x6[0-9a-z]+\\.fsf\\(_-_\\)?@@.*eyesore\\.no>"
19331 Whether it's the first two or first three characters that are ``yours''
19332 is system-dependent.
19335 @node Scoring On Other Headers
19336 @section Scoring On Other Headers
19337 @cindex scoring on other headers
19339 Gnus is quite fast when scoring the ``traditional''
19340 headers---@samp{From}, @samp{Subject} and so on. However, scoring
19341 other headers requires writing a @code{head} scoring rule, which means
19342 that Gnus has to request every single article from the back end to find
19343 matches. This takes a long time in big groups.
19345 Now, there's not much you can do about this for news groups, but for
19346 mail groups, you have greater control. In the @pxref{To From
19347 Newsgroups} section of the manual, it's explained in greater detail what
19348 this mechanism does, but here's a cookbook example for @code{nnml} on
19349 how to allow scoring on the @samp{To} and @samp{Cc} headers.
19351 Put the following in your @file{~/.gnus.el} file.
19354 (setq gnus-extra-headers '(To Cc Newsgroups Keywords)
19355 nnmail-extra-headers gnus-extra-headers)
19358 Restart Gnus and rebuild your @code{nnml} overview files with the
19359 @kbd{M-x nnml-generate-nov-databases} command. This will take a long
19360 time if you have much mail.
19362 Now you can score on @samp{To} and @samp{Cc} as ``extra headers'' like
19363 so: @kbd{I e s p To RET <your name> RET}.
19369 @section Scoring Tips
19370 @cindex scoring tips
19376 @cindex scoring crossposts
19377 If you want to lower the score of crossposts, the line to match on is
19378 the @code{Xref} header.
19380 ("xref" (" talk.politics.misc:" -1000))
19383 @item Multiple crossposts
19384 If you want to lower the score of articles that have been crossposted to
19385 more than, say, 3 groups:
19388 ("[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+"
19392 @item Matching on the body
19393 This is generally not a very good idea---it takes a very long time.
19394 Gnus actually has to fetch each individual article from the server. But
19395 you might want to anyway, I guess. Even though there are three match
19396 keys (@code{Head}, @code{Body} and @code{All}), you should choose one
19397 and stick with it in each score file. If you use any two, each article
19398 will be fetched @emph{twice}. If you want to match a bit on the
19399 @code{Head} and a bit on the @code{Body}, just use @code{All} for all
19402 @item Marking as read
19403 You will probably want to mark articles that have scores below a certain
19404 number as read. This is most easily achieved by putting the following
19405 in your @file{all.SCORE} file:
19409 You may also consider doing something similar with @code{expunge}.
19411 @item Negated character classes
19412 If you say stuff like @code{[^abcd]*}, you may get unexpected results.
19413 That will match newlines, which might lead to, well, The Unknown. Say
19414 @code{[^abcd\n]*} instead.
19418 @node Reverse Scoring
19419 @section Reverse Scoring
19420 @cindex reverse scoring
19422 If you want to keep just articles that have @samp{Sex with Emacs} in the
19423 subject header, and expunge all other articles, you could put something
19424 like this in your score file:
19428 ("Sex with Emacs" 2))
19433 So, you raise all articles that match @samp{Sex with Emacs} and mark the
19434 rest as read, and expunge them to boot.
19437 @node Global Score Files
19438 @section Global Score Files
19439 @cindex global score files
19441 Sure, other newsreaders have ``global kill files''. These are usually
19442 nothing more than a single kill file that applies to all groups, stored
19443 in the user's home directory. Bah! Puny, weak newsreaders!
19445 What I'm talking about here are Global Score Files. Score files from
19446 all over the world, from users everywhere, uniting all nations in one
19447 big, happy score file union! Ange-score! New and untested!
19449 @vindex gnus-global-score-files
19450 All you have to do to use other people's score files is to set the
19451 @code{gnus-global-score-files} variable. One entry for each score file,
19452 or each score file directory. Gnus will decide by itself what score
19453 files are applicable to which group.
19455 To use the score file
19456 @file{/ftp@@ftp.gnus.org:/pub/larsi/ding/score/soc.motss.SCORE} and
19457 all score files in the @file{/ftp@@ftp.some-where:/pub/score} directory,
19461 (setq gnus-global-score-files
19462 '("/ftp@@ftp.gnus.org:/pub/larsi/ding/score/soc.motss.SCORE"
19463 "/ftp@@ftp.some-where:/pub/score/"))
19466 @findex gnus-score-search-global-directories
19468 Simple, eh? Directory names must end with a @samp{/}. These
19469 directories are typically scanned only once during each Gnus session.
19470 If you feel the need to manually re-scan the remote directories, you can
19471 use the @code{gnus-score-search-global-directories} command.
19473 Note that, at present, using this option will slow down group entry
19474 somewhat. (That is---a lot.)
19476 If you want to start maintaining score files for other people to use,
19477 just put your score file up for anonymous ftp and announce it to the
19478 world. Become a retro-moderator! Participate in the retro-moderator
19479 wars sure to ensue, where retro-moderators battle it out for the
19480 sympathy of the people, luring them to use their score files on false
19481 premises! Yay! The net is saved!
19483 Here are some tips for the would-be retro-moderator, off the top of my
19489 Articles heavily crossposted are probably junk.
19491 To lower a single inappropriate article, lower by @code{Message-ID}.
19493 Particularly brilliant authors can be raised on a permanent basis.
19495 Authors that repeatedly post off-charter for the group can safely be
19496 lowered out of existence.
19498 Set the @code{mark} and @code{expunge} atoms to obliterate the nastiest
19499 articles completely.
19502 Use expiring score entries to keep the size of the file down. You
19503 should probably have a long expiry period, though, as some sites keep
19504 old articles for a long time.
19507 @dots{} I wonder whether other newsreaders will support global score files
19508 in the future. @emph{Snicker}. Yup, any day now, newsreaders like Blue
19509 Wave, xrn and 1stReader are bound to implement scoring. Should we start
19510 holding our breath yet?
19514 @section Kill Files
19517 Gnus still supports those pesky old kill files. In fact, the kill file
19518 entries can now be expiring, which is something I wrote before Daniel
19519 Quinlan thought of doing score files, so I've left the code in there.
19521 In short, kill processing is a lot slower (and I do mean @emph{a lot})
19522 than score processing, so it might be a good idea to rewrite your kill
19523 files into score files.
19525 Anyway, a kill file is a normal @code{emacs-lisp} file. You can put any
19526 forms into this file, which means that you can use kill files as some
19527 sort of primitive hook function to be run on group entry, even though
19528 that isn't a very good idea.
19530 Normal kill files look like this:
19533 (gnus-kill "From" "Lars Ingebrigtsen")
19534 (gnus-kill "Subject" "ding")
19538 This will mark every article written by me as read, and remove the
19539 marked articles from the summary buffer. Very useful, you'll agree.
19541 Other programs use a totally different kill file syntax. If Gnus
19542 encounters what looks like a @code{rn} kill file, it will take a stab at
19545 Two summary functions for editing a GNUS kill file:
19550 @kindex M-k (Summary)
19551 @findex gnus-summary-edit-local-kill
19552 Edit this group's kill file (@code{gnus-summary-edit-local-kill}).
19555 @kindex M-K (Summary)
19556 @findex gnus-summary-edit-global-kill
19557 Edit the general kill file (@code{gnus-summary-edit-global-kill}).
19560 Two group mode functions for editing the kill files:
19565 @kindex M-k (Group)
19566 @findex gnus-group-edit-local-kill
19567 Edit this group's kill file (@code{gnus-group-edit-local-kill}).
19570 @kindex M-K (Group)
19571 @findex gnus-group-edit-global-kill
19572 Edit the general kill file (@code{gnus-group-edit-global-kill}).
19575 Kill file variables:
19578 @item gnus-kill-file-name
19579 @vindex gnus-kill-file-name
19580 A kill file for the group @samp{soc.motss} is normally called
19581 @file{soc.motss.KILL}. The suffix appended to the group name to get
19582 this file name is detailed by the @code{gnus-kill-file-name} variable.
19583 The ``global'' kill file (not in the score file sense of ``global'', of
19584 course) is just called @file{KILL}.
19586 @vindex gnus-kill-save-kill-file
19587 @item gnus-kill-save-kill-file
19588 If this variable is non-@code{nil}, Gnus will save the
19589 kill file after processing, which is necessary if you use expiring
19592 @item gnus-apply-kill-hook
19593 @vindex gnus-apply-kill-hook
19594 @findex gnus-apply-kill-file-unless-scored
19595 @findex gnus-apply-kill-file
19596 A hook called to apply kill files to a group. It is
19597 @code{(gnus-apply-kill-file)} by default. If you want to ignore the
19598 kill file if you have a score file for the same group, you can set this
19599 hook to @code{(gnus-apply-kill-file-unless-scored)}. If you don't want
19600 kill files to be processed, you should set this variable to @code{nil}.
19602 @item gnus-kill-file-mode-hook
19603 @vindex gnus-kill-file-mode-hook
19604 A hook called in kill-file mode buffers.
19609 @node Converting Kill Files
19610 @section Converting Kill Files
19612 @cindex converting kill files
19614 If you have loads of old kill files, you may want to convert them into
19615 score files. If they are ``regular'', you can use
19616 the @file{gnus-kill-to-score.el} package; if not, you'll have to do it
19619 The kill to score conversion package isn't included in Gnus by default.
19620 You can fetch it from
19621 @uref{http://www.stud.ifi.uio.no/~larsi/ding-various/gnus-kill-to-score.el}.
19623 If your old kill files are very complex---if they contain more
19624 non-@code{gnus-kill} forms than not, you'll have to convert them by
19625 hand. Or just let them be as they are. Gnus will still use them as
19633 GroupLens (@uref{http://www.cs.umn.edu/Research/GroupLens/}) is a
19634 collaborative filtering system that helps you work together with other
19635 people to find the quality news articles out of the huge volume of
19636 news articles generated every day.
19638 To accomplish this the GroupLens system combines your opinions about
19639 articles you have already read with the opinions of others who have done
19640 likewise and gives you a personalized prediction for each unread news
19641 article. Think of GroupLens as a matchmaker. GroupLens watches how you
19642 rate articles, and finds other people that rate articles the same way.
19643 Once it has found some people you agree with it tells you, in the form
19644 of a prediction, what they thought of the article. You can use this
19645 prediction to help you decide whether or not you want to read the
19648 @sc{Note:} Unfortunately the GroupLens system seems to have shut down,
19649 so this section is mostly of historical interest.
19652 * Using GroupLens:: How to make Gnus use GroupLens.
19653 * Rating Articles:: Letting GroupLens know how you rate articles.
19654 * Displaying Predictions:: Displaying predictions given by GroupLens.
19655 * GroupLens Variables:: Customizing GroupLens.
19659 @node Using GroupLens
19660 @subsection Using GroupLens
19662 To use GroupLens you must register a pseudonym with your local Better
19664 @uref{http://www.cs.umn.edu/Research/GroupLens/bbb.html} is the only
19665 better bit in town at the moment.
19667 Once you have registered you'll need to set a couple of variables.
19671 @item gnus-use-grouplens
19672 @vindex gnus-use-grouplens
19673 Setting this variable to a non-@code{nil} value will make Gnus hook into
19674 all the relevant GroupLens functions.
19676 @item grouplens-pseudonym
19677 @vindex grouplens-pseudonym
19678 This variable should be set to the pseudonym you got when registering
19679 with the Better Bit Bureau.
19681 @item grouplens-newsgroups
19682 @vindex grouplens-newsgroups
19683 A list of groups that you want to get GroupLens predictions for.
19687 That's the minimum of what you need to get up and running with GroupLens.
19688 Once you've registered, GroupLens will start giving you scores for
19689 articles based on the average of what other people think. But, to get
19690 the real benefit of GroupLens you need to start rating articles
19691 yourself. Then the scores GroupLens gives you will be personalized for
19692 you, based on how the people you usually agree with have already rated.
19695 @node Rating Articles
19696 @subsection Rating Articles
19698 In GroupLens, an article is rated on a scale from 1 to 5, inclusive.
19699 Where 1 means something like this article is a waste of bandwidth and 5
19700 means that the article was really good. The basic question to ask
19701 yourself is, ``on a scale from 1 to 5 would I like to see more articles
19704 There are four ways to enter a rating for an article in GroupLens.
19709 @kindex r (GroupLens)
19710 @findex bbb-summary-rate-article
19711 This function will prompt you for a rating on a scale of one to five.
19714 @kindex k (GroupLens)
19715 @findex grouplens-score-thread
19716 This function will prompt you for a rating, and rate all the articles in
19717 the thread. This is really useful for some of those long running giant
19718 threads in rec.humor.
19722 The next two commands, @kbd{n} and @kbd{,} take a numerical prefix to be
19723 the score of the article you're reading.
19728 @kindex n (GroupLens)
19729 @findex grouplens-next-unread-article
19730 Rate the article and go to the next unread article.
19733 @kindex , (GroupLens)
19734 @findex grouplens-best-unread-article
19735 Rate the article and go to the next unread article with the highest score.
19739 If you want to give the current article a score of 4 and then go to the
19740 next article, just type @kbd{4 n}.
19743 @node Displaying Predictions
19744 @subsection Displaying Predictions
19746 GroupLens makes a prediction for you about how much you will like a
19747 news article. The predictions from GroupLens are on a scale from 1 to
19748 5, where 1 is the worst and 5 is the best. You can use the predictions
19749 from GroupLens in one of three ways controlled by the variable
19750 @code{gnus-grouplens-override-scoring}.
19752 @vindex gnus-grouplens-override-scoring
19753 There are three ways to display predictions in grouplens. You may
19754 choose to have the GroupLens scores contribute to, or override the
19755 regular gnus scoring mechanism. override is the default; however, some
19756 people prefer to see the Gnus scores plus the grouplens scores. To get
19757 the separate scoring behavior you need to set
19758 @code{gnus-grouplens-override-scoring} to @code{'separate}. To have the
19759 GroupLens predictions combined with the grouplens scores set it to
19760 @code{'override} and to combine the scores set
19761 @code{gnus-grouplens-override-scoring} to @code{'combine}. When you use
19762 the combine option you will also want to set the values for
19763 @code{grouplens-prediction-offset} and
19764 @code{grouplens-score-scale-factor}.
19766 @vindex grouplens-prediction-display
19767 In either case, GroupLens gives you a few choices for how you would like
19768 to see your predictions displayed. The display of predictions is
19769 controlled by the @code{grouplens-prediction-display} variable.
19771 The following are valid values for that variable.
19774 @item prediction-spot
19775 The higher the prediction, the further to the right an @samp{*} is
19778 @item confidence-interval
19779 A numeric confidence interval.
19781 @item prediction-bar
19782 The higher the prediction, the longer the bar.
19784 @item confidence-bar
19785 Numerical confidence.
19787 @item confidence-spot
19788 The spot gets bigger with more confidence.
19790 @item prediction-num
19791 Plain-old numeric value.
19793 @item confidence-plus-minus
19794 Prediction +/- confidence.
19799 @node GroupLens Variables
19800 @subsection GroupLens Variables
19804 @item gnus-summary-grouplens-line-format
19805 The summary line format used in GroupLens-enhanced summary buffers. It
19806 accepts the same specs as the normal summary line format (@pxref{Summary
19807 Buffer Lines}). The default is @samp{%U%R%z%l%I%(%[%4L: %-23,23n%]%)
19810 @item grouplens-bbb-host
19811 Host running the bbbd server. @samp{grouplens.cs.umn.edu} is the
19814 @item grouplens-bbb-port
19815 Port of the host running the bbbd server. The default is 9000.
19817 @item grouplens-score-offset
19818 Offset the prediction by this value. In other words, subtract the
19819 prediction value by this number to arrive at the effective score. The
19822 @item grouplens-score-scale-factor
19823 This variable allows the user to magnify the effect of GroupLens scores.
19824 The scale factor is applied after the offset. The default is 1.
19829 @node Advanced Scoring
19830 @section Advanced Scoring
19832 Scoring on Subjects and From headers is nice enough, but what if you're
19833 really interested in what a person has to say only when she's talking
19834 about a particular subject? Or what if you really don't want to
19835 read what person A has to say when she's following up to person B, but
19836 want to read what she says when she's following up to person C?
19838 By using advanced scoring rules you may create arbitrarily complex
19842 * Advanced Scoring Syntax:: A definition.
19843 * Advanced Scoring Examples:: What they look like.
19844 * Advanced Scoring Tips:: Getting the most out of it.
19848 @node Advanced Scoring Syntax
19849 @subsection Advanced Scoring Syntax
19851 Ordinary scoring rules have a string as the first element in the rule.
19852 Advanced scoring rules have a list as the first element. The second
19853 element is the score to be applied if the first element evaluated to a
19854 non-@code{nil} value.
19856 These lists may consist of three logical operators, one redirection
19857 operator, and various match operators.
19864 This logical operator will evaluate each of its arguments until it finds
19865 one that evaluates to @code{false}, and then it'll stop. If all arguments
19866 evaluate to @code{true} values, then this operator will return
19871 This logical operator will evaluate each of its arguments until it finds
19872 one that evaluates to @code{true}. If no arguments are @code{true},
19873 then this operator will return @code{false}.
19878 This logical operator only takes a single argument. It returns the
19879 logical negation of the value of its argument.
19883 There is an @dfn{indirection operator} that will make its arguments
19884 apply to the ancestors of the current article being scored. For
19885 instance, @code{1-} will make score rules apply to the parent of the
19886 current article. @code{2-} will make score rules apply to the
19887 grandparent of the current article. Alternatively, you can write
19888 @code{^^}, where the number of @code{^}s (carets) says how far back into
19889 the ancestry you want to go.
19891 Finally, we have the match operators. These are the ones that do the
19892 real work. Match operators are header name strings followed by a match
19893 and a match type. A typical match operator looks like @samp{("from"
19894 "Lars Ingebrigtsen" s)}. The header names are the same as when using
19895 simple scoring, and the match types are also the same.
19898 @node Advanced Scoring Examples
19899 @subsection Advanced Scoring Examples
19901 Please note that the following examples are score file rules. To
19902 make a complete score file from them, surround them with another pair
19905 Let's say you want to increase the score of articles written by Lars
19906 when he's talking about Gnus:
19910 ("from" "Lars Ingebrigtsen")
19911 ("subject" "Gnus"))
19917 When he writes long articles, he sometimes has something nice to say:
19921 ("from" "Lars Ingebrigtsen")
19928 However, when he responds to things written by Reig Eigil Logge, you
19929 really don't want to read what he's written:
19933 ("from" "Lars Ingebrigtsen")
19934 (1- ("from" "Reig Eigir Logge")))
19938 Everybody that follows up Redmondo when he writes about disappearing
19939 socks should have their scores raised, but only when they talk about
19940 white socks. However, when Lars talks about socks, it's usually not
19947 ("from" "redmondo@@.*no" r)
19948 ("body" "disappearing.*socks" t)))
19949 (! ("from" "Lars Ingebrigtsen"))
19950 ("body" "white.*socks"))
19954 The possibilities are endless.
19957 @node Advanced Scoring Tips
19958 @subsection Advanced Scoring Tips
19960 The @code{&} and @code{|} logical operators do short-circuit logic.
19961 That is, they stop processing their arguments when it's clear what the
19962 result of the operation will be. For instance, if one of the arguments
19963 of an @code{&} evaluates to @code{false}, there's no point in evaluating
19964 the rest of the arguments. This means that you should put slow matches
19965 (@samp{body}, @samp{header}) last and quick matches (@samp{from},
19966 @samp{subject}) first.
19968 The indirection arguments (@code{1-} and so on) will make their
19969 arguments work on previous generations of the thread. If you say
19980 Then that means "score on the from header of the grandparent of the
19981 current article". An indirection is quite fast, but it's better to say:
19987 ("subject" "Gnus")))
19994 (1- ("from" "Lars"))
19995 (1- ("subject" "Gnus")))
20000 @section Score Decays
20001 @cindex score decays
20004 You may find that your scores have a tendency to grow without
20005 bounds, especially if you're using adaptive scoring. If scores get too
20006 big, they lose all meaning---they simply max out and it's difficult to
20007 use them in any sensible way.
20009 @vindex gnus-decay-scores
20010 @findex gnus-decay-score
20011 @vindex gnus-decay-score-function
20012 Gnus provides a mechanism for decaying scores to help with this problem.
20013 When score files are loaded and @code{gnus-decay-scores} is
20014 non-@code{nil}, Gnus will run the score files through the decaying
20015 mechanism thereby lowering the scores of all non-permanent score rules.
20016 The decay itself if performed by the @code{gnus-decay-score-function}
20017 function, which is @code{gnus-decay-score} by default. Here's the
20018 definition of that function:
20021 (defun gnus-decay-score (score)
20023 This is done according to `gnus-score-decay-constant'
20024 and `gnus-score-decay-scale'."
20027 (* (if (< score 0) 1 -1)
20029 (max gnus-score-decay-constant
20031 gnus-score-decay-scale)))))))
20034 @vindex gnus-score-decay-scale
20035 @vindex gnus-score-decay-constant
20036 @code{gnus-score-decay-constant} is 3 by default and
20037 @code{gnus-score-decay-scale} is 0.05. This should cause the following:
20041 Scores between -3 and 3 will be set to 0 when this function is called.
20044 Scores with magnitudes between 3 and 60 will be shrunk by 3.
20047 Scores with magnitudes greater than 60 will be shrunk by 5% of the
20051 If you don't like this decay function, write your own. It is called
20052 with the score to be decayed as its only parameter, and it should return
20053 the new score, which should be an integer.
20055 Gnus will try to decay scores once a day. If you haven't run Gnus for
20056 four days, Gnus will decay the scores four times, for instance.
20061 @include message.texi
20062 @chapter Emacs MIME
20063 @include emacs-mime.texi
20065 @include sieve.texi
20075 * Process/Prefix:: A convention used by many treatment commands.
20076 * Interactive:: Making Gnus ask you many questions.
20077 * Symbolic Prefixes:: How to supply some Gnus functions with options.
20078 * Formatting Variables:: You can specify what buffers should look like.
20079 * Window Layout:: Configuring the Gnus buffer windows.
20080 * Faces and Fonts:: How to change how faces look.
20081 * Compilation:: How to speed Gnus up.
20082 * Mode Lines:: Displaying information in the mode lines.
20083 * Highlighting and Menus:: Making buffers look all nice and cozy.
20084 * Buttons:: Get tendinitis in ten easy steps!
20085 * Daemons:: Gnus can do things behind your back.
20086 * NoCeM:: How to avoid spam and other fatty foods.
20087 * Undo:: Some actions can be undone.
20088 * Predicate Specifiers:: Specifying predicates.
20089 * Moderation:: What to do if you're a moderator.
20090 * Image Enhancements:: Modern versions of Emacs/XEmacs can display images.
20091 * Fuzzy Matching:: What's the big fuzz?
20092 * Thwarting Email Spam:: A how-to on avoiding unsolicited commercial email.
20093 * Various Various:: Things that are really various.
20097 @node Process/Prefix
20098 @section Process/Prefix
20099 @cindex process/prefix convention
20101 Many functions, among them functions for moving, decoding and saving
20102 articles, use what is known as the @dfn{Process/Prefix convention}.
20104 This is a method for figuring out what articles the user wants the
20105 command to be performed on.
20109 If the numeric prefix is N, perform the operation on the next N
20110 articles, starting with the current one. If the numeric prefix is
20111 negative, perform the operation on the previous N articles, starting
20112 with the current one.
20114 @vindex transient-mark-mode
20115 If @code{transient-mark-mode} in non-@code{nil} and the region is
20116 active, all articles in the region will be worked upon.
20118 If there is no numeric prefix, but some articles are marked with the
20119 process mark, perform the operation on the articles marked with
20122 If there is neither a numeric prefix nor any articles marked with the
20123 process mark, just perform the operation on the current article.
20125 Quite simple, really, but it needs to be made clear so that surprises
20128 Commands that react to the process mark will push the current list of
20129 process marked articles onto a stack and will then clear all process
20130 marked articles. You can restore the previous configuration with the
20131 @kbd{M P y} command (@pxref{Setting Process Marks}).
20133 @vindex gnus-summary-goto-unread
20134 One thing that seems to shock & horrify lots of people is that, for
20135 instance, @kbd{3 d} does exactly the same as @kbd{d} @kbd{d} @kbd{d}.
20136 Since each @kbd{d} (which marks the current article as read) by default
20137 goes to the next unread article after marking, this means that @kbd{3 d}
20138 will mark the next three unread articles as read, no matter what the
20139 summary buffer looks like. Set @code{gnus-summary-goto-unread} to
20140 @code{nil} for a more straightforward action.
20142 Many commands do not use the process/prefix convention. All commands
20143 that do explicitly say so in this manual. To apply the process/prefix
20144 convention to commands that do not use it, you can use the @kbd{M-&}
20145 command. For instance, to mark all the articles in the group as
20146 expirable, you could say @kbd{M P b M-& E}.
20150 @section Interactive
20151 @cindex interaction
20155 @item gnus-novice-user
20156 @vindex gnus-novice-user
20157 If this variable is non-@code{nil}, you are either a newcomer to the
20158 World of Usenet, or you are very cautious, which is a nice thing to be,
20159 really. You will be given questions of the type ``Are you sure you want
20160 to do this?'' before doing anything dangerous. This is @code{t} by
20163 @item gnus-expert-user
20164 @vindex gnus-expert-user
20165 If this variable is non-@code{nil}, you will seldom be asked any
20166 questions by Gnus. It will simply assume you know what you're doing, no
20167 matter how strange.
20169 @item gnus-interactive-catchup
20170 @vindex gnus-interactive-catchup
20171 Require confirmation before catching up a group if non-@code{nil}. It
20172 is @code{t} by default.
20174 @item gnus-interactive-exit
20175 @vindex gnus-interactive-exit
20176 Require confirmation before exiting Gnus. This variable is @code{t} by
20181 @node Symbolic Prefixes
20182 @section Symbolic Prefixes
20183 @cindex symbolic prefixes
20185 Quite a lot of Emacs commands react to the (numeric) prefix. For
20186 instance, @kbd{C-u 4 C-f} moves point four characters forward, and
20187 @kbd{C-u 9 0 0 I s s p} adds a permanent @code{Subject} substring score
20188 rule of 900 to the current article.
20190 This is all nice and well, but what if you want to give a command some
20191 additional information? Well, what most commands do is interpret the
20192 ``raw'' prefix in some special way. @kbd{C-u 0 C-x C-s} means that one
20193 doesn't want a backup file to be created when saving the current buffer,
20194 for instance. But what if you want to save without making a backup
20195 file, and you want Emacs to flash lights and play a nice tune at the
20196 same time? You can't, and you're probably perfectly happy that way.
20198 @kindex M-i (Summary)
20199 @findex gnus-symbolic-argument
20200 I'm not, so I've added a second prefix---the @dfn{symbolic prefix}. The
20201 prefix key is @kbd{M-i} (@code{gnus-symbolic-argument}), and the next
20202 character typed in is the value. You can stack as many @kbd{M-i}
20203 prefixes as you want. @kbd{M-i a C-M-u} means ``feed the @kbd{C-M-u}
20204 command the symbolic prefix @code{a}''. @kbd{M-i a M-i b C-M-u} means
20205 ``feed the @kbd{C-M-u} command the symbolic prefixes @code{a} and
20206 @code{b}''. You get the drift.
20208 Typing in symbolic prefixes to commands that don't accept them doesn't
20209 hurt, but it doesn't do any good either. Currently not many Gnus
20210 functions make use of the symbolic prefix.
20212 If you're interested in how Gnus implements this, @pxref{Extended
20216 @node Formatting Variables
20217 @section Formatting Variables
20218 @cindex formatting variables
20220 Throughout this manual you've probably noticed lots of variables called
20221 things like @code{gnus-group-line-format} and
20222 @code{gnus-summary-mode-line-format}. These control how Gnus is to
20223 output lines in the various buffers. There's quite a lot of them.
20224 Fortunately, they all use the same syntax, so there's not that much to
20227 Here's an example format spec (from the group buffer): @samp{%M%S%5y:
20228 %(%g%)\n}. We see that it is indeed extremely ugly, and that there are
20229 lots of percentages everywhere.
20232 * Formatting Basics:: A formatting variable is basically a format string.
20233 * Mode Line Formatting:: Some rules about mode line formatting variables.
20234 * Advanced Formatting:: Modifying output in various ways.
20235 * User-Defined Specs:: Having Gnus call your own functions.
20236 * Formatting Fonts:: Making the formatting look colorful and nice.
20237 * Positioning Point:: Moving point to a position after an operation.
20238 * Tabulation:: Tabulating your output.
20239 * Wide Characters:: Dealing with wide characters.
20242 Currently Gnus uses the following formatting variables:
20243 @code{gnus-group-line-format}, @code{gnus-summary-line-format},
20244 @code{gnus-server-line-format}, @code{gnus-topic-line-format},
20245 @code{gnus-group-mode-line-format},
20246 @code{gnus-summary-mode-line-format},
20247 @code{gnus-article-mode-line-format},
20248 @code{gnus-server-mode-line-format}, and
20249 @code{gnus-summary-pick-line-format}.
20251 All these format variables can also be arbitrary elisp forms. In that
20252 case, they will be @code{eval}ed to insert the required lines.
20254 @kindex M-x gnus-update-format
20255 @findex gnus-update-format
20256 Gnus includes a command to help you while creating your own format
20257 specs. @kbd{M-x gnus-update-format} will @code{eval} the current form,
20258 update the spec in question and pop you to a buffer where you can
20259 examine the resulting lisp code to be run to generate the line.
20263 @node Formatting Basics
20264 @subsection Formatting Basics
20266 Each @samp{%} element will be replaced by some string or other when the
20267 buffer in question is generated. @samp{%5y} means ``insert the @samp{y}
20268 spec, and pad with spaces to get a 5-character field''.
20270 As with normal C and Emacs Lisp formatting strings, the numerical
20271 modifier between the @samp{%} and the formatting type character will
20272 @dfn{pad} the output so that it is always at least that long.
20273 @samp{%5y} will make the field always (at least) five characters wide by
20274 padding with spaces to the left. If you say @samp{%-5y}, it will pad to
20277 You may also wish to limit the length of the field to protect against
20278 particularly wide values. For that you can say @samp{%4,6y}, which
20279 means that the field will never be more than 6 characters wide and never
20280 less than 4 characters wide.
20282 Also Gnus supports some extended format specifications, such as
20283 @samp{%&user-date;}.
20286 @node Mode Line Formatting
20287 @subsection Mode Line Formatting
20289 Mode line formatting variables (e.g.,
20290 @code{gnus-summary-mode-line-format}) follow the same rules as other,
20291 buffer line oriented formatting variables (@pxref{Formatting Basics})
20292 with the following two differences:
20297 There must be no newline (@samp{\n}) at the end.
20300 The special @samp{%%b} spec can be used to display the buffer name.
20301 Well, it's no spec at all, really---@samp{%%} is just a way to quote
20302 @samp{%} to allow it to pass through the formatting machinery unmangled,
20303 so that Emacs receives @samp{%b}, which is something the Emacs mode line
20304 display interprets to mean ``show the buffer name''. For a full list of
20305 mode line specs Emacs understands, see the documentation of the
20306 @code{mode-line-format} variable.
20311 @node Advanced Formatting
20312 @subsection Advanced Formatting
20314 It is frequently useful to post-process the fields in some way.
20315 Padding, limiting, cutting off parts and suppressing certain values can
20316 be achieved by using @dfn{tilde modifiers}. A typical tilde spec might
20317 look like @samp{%~(cut 3)~(ignore "0")y}.
20319 These are the valid modifiers:
20324 Pad the field to the left with spaces until it reaches the required
20328 Pad the field to the right with spaces until it reaches the required
20333 Cut off characters from the left until it reaches the specified length.
20336 Cut off characters from the right until it reaches the specified
20341 Cut off the specified number of characters from the left.
20344 Cut off the specified number of characters from the right.
20347 Return an empty string if the field is equal to the specified value.
20350 Use the specified form as the field value when the @samp{@@} spec is
20356 "~(form (current-time-string))@@"
20361 Let's take an example. The @samp{%o} spec in the summary mode lines
20362 will return a date in compact ISO8601 format---@samp{19960809T230410}.
20363 This is quite a mouthful, so we want to shave off the century number and
20364 the time, leaving us with a six-character date. That would be
20365 @samp{%~(cut-left 2)~(max-right 6)~(pad 6)o}. (Cutting is done before
20366 maxing, and we need the padding to ensure that the date is never less
20367 than 6 characters to make it look nice in columns.)
20369 Ignoring is done first; then cutting; then maxing; and then as the very
20370 last operation, padding.
20372 If you use lots of these advanced thingies, you'll find that Gnus gets
20373 quite slow. This can be helped enormously by running @kbd{M-x
20374 gnus-compile} when you are satisfied with the look of your lines.
20375 @xref{Compilation}.
20378 @node User-Defined Specs
20379 @subsection User-Defined Specs
20381 All the specs allow for inserting user defined specifiers---@samp{u}.
20382 The next character in the format string should be a letter. Gnus
20383 will call the function @code{gnus-user-format-function-}@samp{X}, where
20384 @samp{X} is the letter following @samp{%u}. The function will be passed
20385 a single parameter---what the parameter means depends on what buffer
20386 it's being called from. The function should return a string, which will
20387 be inserted into the buffer just like information from any other
20388 specifier. This function may also be called with dummy values, so it
20389 should protect against that.
20391 Also Gnus supports extended user-defined specs, such as @samp{%u&foo;}.
20392 Gnus will call the function @code{gnus-user-format-function-}@samp{foo}.
20394 You can also use tilde modifiers (@pxref{Advanced Formatting} to achieve
20395 much the same without defining new functions. Here's an example:
20396 @samp{%~(form (count-lines (point-min) (point)))@@}. The form
20397 given here will be evaluated to yield the current line number, and then
20401 @node Formatting Fonts
20402 @subsection Formatting Fonts
20404 There are specs for highlighting, and these are shared by all the format
20405 variables. Text inside the @samp{%(} and @samp{%)} specifiers will get
20406 the special @code{mouse-face} property set, which means that it will be
20407 highlighted (with @code{gnus-mouse-face}) when you put the mouse pointer
20410 Text inside the @samp{%@{} and @samp{%@}} specifiers will have their
20411 normal faces set using @code{gnus-face-0}, which is @code{bold} by
20412 default. If you say @samp{%1@{}, you'll get @code{gnus-face-1} instead,
20413 and so on. Create as many faces as you wish. The same goes for the
20414 @code{mouse-face} specs---you can say @samp{%3(hello%)} to have
20415 @samp{hello} mouse-highlighted with @code{gnus-mouse-face-3}.
20417 Text inside the @samp{%<<} and @samp{%>>} specifiers will get the
20418 special @code{balloon-help} property set to
20419 @code{gnus-balloon-face-0}. If you say @samp{%1<<}, you'll get
20420 @code{gnus-balloon-face-1} and so on. The @code{gnus-balloon-face-*}
20421 variables should be either strings or symbols naming functions that
20422 return a string. When the mouse passes over text with this property
20423 set, a balloon window will appear and display the string. Please
20424 refer to @ref{Tooltips, ,Tooltips, emacs, The Emacs Manual},
20425 (in GNU Emacs) or the doc string of @code{balloon-help-mode} (in
20426 XEmacs) for more information on this. (For technical reasons, the
20427 guillemets have been approximated as @samp{<<} and @samp{>>} in this
20430 Here's an alternative recipe for the group buffer:
20433 ;; Create three face types.
20434 (setq gnus-face-1 'bold)
20435 (setq gnus-face-3 'italic)
20437 ;; We want the article count to be in
20438 ;; a bold and green face. So we create
20439 ;; a new face called `my-green-bold'.
20440 (copy-face 'bold 'my-green-bold)
20442 (set-face-foreground 'my-green-bold "ForestGreen")
20443 (setq gnus-face-2 'my-green-bold)
20445 ;; Set the new & fancy format.
20446 (setq gnus-group-line-format
20447 "%M%S%3@{%5y%@}%2[:%] %(%1@{%g%@}%)\n")
20450 I'm sure you'll be able to use this scheme to create totally unreadable
20451 and extremely vulgar displays. Have fun!
20453 Note that the @samp{%(} specs (and friends) do not make any sense on the
20454 mode-line variables.
20456 @node Positioning Point
20457 @subsection Positioning Point
20459 Gnus usually moves point to a pre-defined place on each line in most
20460 buffers. By default, point move to the first colon character on the
20461 line. You can customize this behaviour in three different ways.
20463 You can move the colon character to somewhere else on the line.
20465 @findex gnus-goto-colon
20466 You can redefine the function that moves the point to the colon. The
20467 function is called @code{gnus-goto-colon}.
20469 But perhaps the most convenient way to deal with this, if you don't want
20470 to have a colon in your line, is to use the @samp{%*} specifier. If you
20471 put a @samp{%*} somewhere in your format line definition, Gnus will
20476 @subsection Tabulation
20478 You can usually line up your displays by padding and cutting your
20479 strings. However, when combining various strings of different size, it
20480 can often be more convenient to just output the strings, and then worry
20481 about lining up the following text afterwards.
20483 To do that, Gnus supplies tabulator specs--@samp{%=}. There are two
20484 different types---@dfn{hard tabulators} and @dfn{soft tabulators}.
20486 @samp{%50=} will insert space characters to pad the line up to column
20487 50. If the text is already past column 50, nothing will be inserted.
20488 This is the soft tabulator.
20490 @samp{%-50=} will insert space characters to pad the line up to column
20491 50. If the text is already past column 50, the excess text past column
20492 50 will be removed. This is the hard tabulator.
20495 @node Wide Characters
20496 @subsection Wide Characters
20498 Proportional fonts in most countries have characters of the same width.
20499 Some countries, however, use Latin characters mixed with wider
20500 characters---most notable East Asian countries.
20502 The problem is that when formatting, Gnus assumes that if a string is 10
20503 characters wide, it'll be 10 Latin characters wide on the screen. In
20504 these countries, that's not true.
20506 @vindex gnus-use-correct-string-widths
20507 To help fix this, you can set @code{gnus-use-correct-string-widths} to
20508 @code{t}. This makes buffer generation slower, but the results will be
20509 prettier. The default value under XEmacs is @code{t} but @code{nil}
20513 @node Window Layout
20514 @section Window Layout
20515 @cindex window layout
20517 No, there's nothing here about X, so be quiet.
20519 @vindex gnus-use-full-window
20520 If @code{gnus-use-full-window} non-@code{nil}, Gnus will delete all
20521 other windows and occupy the entire Emacs screen by itself. It is
20522 @code{t} by default.
20524 Setting this variable to @code{nil} kinda works, but there are
20525 glitches. Use at your own peril.
20527 @vindex gnus-buffer-configuration
20528 @code{gnus-buffer-configuration} describes how much space each Gnus
20529 buffer should be given. Here's an excerpt of this variable:
20532 ((group (vertical 1.0 (group 1.0 point)
20533 (if gnus-carpal (group-carpal 4))))
20534 (article (vertical 1.0 (summary 0.25 point)
20538 This is an alist. The @dfn{key} is a symbol that names some action or
20539 other. For instance, when displaying the group buffer, the window
20540 configuration function will use @code{group} as the key. A full list of
20541 possible names is listed below.
20543 The @dfn{value} (i.e., the @dfn{split}) says how much space each buffer
20544 should occupy. To take the @code{article} split as an example -
20547 (article (vertical 1.0 (summary 0.25 point)
20551 This @dfn{split} says that the summary buffer should occupy 25% of upper
20552 half of the screen, and that it is placed over the article buffer. As
20553 you may have noticed, 100% + 25% is actually 125% (yup, I saw y'all
20554 reaching for that calculator there). However, the special number
20555 @code{1.0} is used to signal that this buffer should soak up all the
20556 rest of the space available after the rest of the buffers have taken
20557 whatever they need. There should be only one buffer with the @code{1.0}
20558 size spec per split.
20560 Point will be put in the buffer that has the optional third element
20561 @code{point}. In a @code{frame} split, the last subsplit having a leaf
20562 split where the tag @code{frame-focus} is a member (i.e. is the third or
20563 fourth element in the list, depending on whether the @code{point} tag is
20564 present) gets focus.
20566 Here's a more complicated example:
20569 (article (vertical 1.0 (group 4)
20570 (summary 0.25 point)
20571 (if gnus-carpal (summary-carpal 4))
20575 If the size spec is an integer instead of a floating point number,
20576 then that number will be used to say how many lines a buffer should
20577 occupy, not a percentage.
20579 If the @dfn{split} looks like something that can be @code{eval}ed (to be
20580 precise---if the @code{car} of the split is a function or a subr), this
20581 split will be @code{eval}ed. If the result is non-@code{nil}, it will
20582 be used as a split. This means that there will be three buffers if
20583 @code{gnus-carpal} is @code{nil}, and four buffers if @code{gnus-carpal}
20586 Not complicated enough for you? Well, try this on for size:
20589 (article (horizontal 1.0
20594 (summary 0.25 point)
20599 Whoops. Two buffers with the mystery 100% tag. And what's that
20600 @code{horizontal} thingie?
20602 If the first element in one of the split is @code{horizontal}, Gnus will
20603 split the window horizontally, giving you two windows side-by-side.
20604 Inside each of these strips you may carry on all you like in the normal
20605 fashion. The number following @code{horizontal} says what percentage of
20606 the screen is to be given to this strip.
20608 For each split, there @emph{must} be one element that has the 100% tag.
20609 The splitting is never accurate, and this buffer will eat any leftover
20610 lines from the splits.
20612 To be slightly more formal, here's a definition of what a valid split
20616 split = frame | horizontal | vertical | buffer | form
20617 frame = "(frame " size *split ")"
20618 horizontal = "(horizontal " size *split ")"
20619 vertical = "(vertical " size *split ")"
20620 buffer = "(" buf-name " " size *[ "point" ] *[ "frame-focus"] ")"
20621 size = number | frame-params
20622 buf-name = group | article | summary ...
20625 The limitations are that the @code{frame} split can only appear as the
20626 top-level split. @var{form} should be an Emacs Lisp form that should
20627 return a valid split. We see that each split is fully recursive, and
20628 may contain any number of @code{vertical} and @code{horizontal} splits.
20630 @vindex gnus-window-min-width
20631 @vindex gnus-window-min-height
20632 @cindex window height
20633 @cindex window width
20634 Finding the right sizes can be a bit complicated. No window may be less
20635 than @code{gnus-window-min-height} (default 1) characters high, and all
20636 windows must be at least @code{gnus-window-min-width} (default 1)
20637 characters wide. Gnus will try to enforce this before applying the
20638 splits. If you want to use the normal Emacs window width/height limit,
20639 you can just set these two variables to @code{nil}.
20641 If you're not familiar with Emacs terminology, @code{horizontal} and
20642 @code{vertical} splits may work the opposite way of what you'd expect.
20643 Windows inside a @code{horizontal} split are shown side-by-side, and
20644 windows within a @code{vertical} split are shown above each other.
20646 @findex gnus-configure-frame
20647 If you want to experiment with window placement, a good tip is to call
20648 @code{gnus-configure-frame} directly with a split. This is the function
20649 that does all the real work when splitting buffers. Below is a pretty
20650 nonsensical configuration with 5 windows; two for the group buffer and
20651 three for the article buffer. (I said it was nonsensical.) If you
20652 @code{eval} the statement below, you can get an idea of how that would
20653 look straight away, without going through the normal Gnus channels.
20654 Play with it until you're satisfied, and then use
20655 @code{gnus-add-configuration} to add your new creation to the buffer
20656 configuration list.
20659 (gnus-configure-frame
20663 (article 0.3 point))
20671 You might want to have several frames as well. No prob---just use the
20672 @code{frame} split:
20675 (gnus-configure-frame
20678 (summary 0.25 point frame-focus)
20680 (vertical ((height . 5) (width . 15)
20681 (user-position . t)
20682 (left . -1) (top . 1))
20687 This split will result in the familiar summary/article window
20688 configuration in the first (or ``main'') frame, while a small additional
20689 frame will be created where picons will be shown. As you can see,
20690 instead of the normal @code{1.0} top-level spec, each additional split
20691 should have a frame parameter alist as the size spec.
20692 @xref{Frame Parameters, , Frame Parameters, elisp, The GNU Emacs Lisp
20693 Reference Manual}. Under XEmacs, a frame property list will be
20694 accepted, too---for instance, @code{(height 5 width 15 left -1 top 1)}
20696 The list of all possible keys for @code{gnus-buffer-configuration} can
20697 be found in its default value.
20699 Note that the @code{message} key is used for both
20700 @code{gnus-group-mail} and @code{gnus-summary-mail-other-window}. If
20701 it is desirable to distinguish between the two, something like this
20705 (message (horizontal 1.0
20706 (vertical 1.0 (message 1.0 point))
20708 (if (buffer-live-p gnus-summary-buffer)
20713 One common desire for a multiple frame split is to have a separate frame
20714 for composing mail and news while leaving the original frame intact. To
20715 accomplish that, something like the following can be done:
20720 (if (not (buffer-live-p gnus-summary-buffer))
20721 (car (cdr (assoc 'group gnus-buffer-configuration)))
20722 (car (cdr (assoc 'summary gnus-buffer-configuration))))
20723 (vertical ((user-position . t) (top . 1) (left . 1)
20724 (name . "Message"))
20725 (message 1.0 point))))
20728 @findex gnus-add-configuration
20729 Since the @code{gnus-buffer-configuration} variable is so long and
20730 complicated, there's a function you can use to ease changing the config
20731 of a single setting: @code{gnus-add-configuration}. If, for instance,
20732 you want to change the @code{article} setting, you could say:
20735 (gnus-add-configuration
20736 '(article (vertical 1.0
20738 (summary .25 point)
20742 You'd typically stick these @code{gnus-add-configuration} calls in your
20743 @file{~/.gnus.el} file or in some startup hook---they should be run after
20744 Gnus has been loaded.
20746 @vindex gnus-always-force-window-configuration
20747 If all windows mentioned in the configuration are already visible, Gnus
20748 won't change the window configuration. If you always want to force the
20749 ``right'' window configuration, you can set
20750 @code{gnus-always-force-window-configuration} to non-@code{nil}.
20752 If you're using tree displays (@pxref{Tree Display}), and the tree
20753 window is displayed vertically next to another window, you may also want
20754 to fiddle with @code{gnus-tree-minimize-window} to avoid having the
20757 @subsection Example Window Configurations
20761 Narrow left hand side occupied by group buffer. Right hand side split
20762 between summary buffer (top one-sixth) and article buffer (bottom).
20777 (gnus-add-configuration
20780 (vertical 25 (group 1.0))
20782 (summary 0.16 point)
20785 (gnus-add-configuration
20788 (vertical 25 (group 1.0))
20789 (vertical 1.0 (summary 1.0 point)))))
20795 @node Faces and Fonts
20796 @section Faces and Fonts
20801 Fiddling with fonts and faces used to be very difficult, but these days
20802 it is very simple. You simply say @kbd{M-x customize-face}, pick out
20803 the face you want to alter, and alter it via the standard Customize
20808 @section Compilation
20809 @cindex compilation
20810 @cindex byte-compilation
20812 @findex gnus-compile
20814 Remember all those line format specification variables?
20815 @code{gnus-summary-line-format}, @code{gnus-group-line-format}, and so
20816 on. Now, Gnus will of course heed whatever these variables are, but,
20817 unfortunately, changing them will mean a quite significant slow-down.
20818 (The default values of these variables have byte-compiled functions
20819 associated with them, while the user-generated versions do not, of
20822 To help with this, you can run @kbd{M-x gnus-compile} after you've
20823 fiddled around with the variables and feel that you're (kind of)
20824 satisfied. This will result in the new specs being byte-compiled, and
20825 you'll get top speed again. Gnus will save these compiled specs in the
20826 @file{.newsrc.eld} file. (User-defined functions aren't compiled by
20827 this function, though---you should compile them yourself by sticking
20828 them into the @file{~/.gnus.el} file and byte-compiling that file.)
20832 @section Mode Lines
20835 @vindex gnus-updated-mode-lines
20836 @code{gnus-updated-mode-lines} says what buffers should keep their mode
20837 lines updated. It is a list of symbols. Supported symbols include
20838 @code{group}, @code{article}, @code{summary}, @code{server},
20839 @code{browse}, and @code{tree}. If the corresponding symbol is present,
20840 Gnus will keep that mode line updated with information that may be
20841 pertinent. If this variable is @code{nil}, screen refresh may be
20844 @cindex display-time
20846 @vindex gnus-mode-non-string-length
20847 By default, Gnus displays information on the current article in the mode
20848 lines of the summary and article buffers. The information Gnus wishes
20849 to display (e.g. the subject of the article) is often longer than the
20850 mode lines, and therefore have to be cut off at some point. The
20851 @code{gnus-mode-non-string-length} variable says how long the other
20852 elements on the line is (i.e., the non-info part). If you put
20853 additional elements on the mode line (e.g. a clock), you should modify
20856 @c Hook written by Francesco Potorti` <pot@cnuce.cnr.it>
20858 (add-hook 'display-time-hook
20859 (lambda () (setq gnus-mode-non-string-length
20861 (if line-number-mode 5 0)
20862 (if column-number-mode 4 0)
20863 (length display-time-string)))))
20866 If this variable is @code{nil} (which is the default), the mode line
20867 strings won't be chopped off, and they won't be padded either. Note
20868 that the default is unlikely to be desirable, as even the percentage
20869 complete in the buffer may be crowded off the mode line; the user should
20870 configure this variable appropriately for her configuration.
20873 @node Highlighting and Menus
20874 @section Highlighting and Menus
20876 @cindex highlighting
20879 @vindex gnus-visual
20880 The @code{gnus-visual} variable controls most of the Gnus-prettifying
20881 aspects. If @code{nil}, Gnus won't attempt to create menus or use fancy
20882 colors or fonts. This will also inhibit loading the @file{gnus-vis.el}
20885 This variable can be a list of visual properties that are enabled. The
20886 following elements are valid, and are all included by default:
20889 @item group-highlight
20890 Do highlights in the group buffer.
20891 @item summary-highlight
20892 Do highlights in the summary buffer.
20893 @item article-highlight
20894 Do highlights in the article buffer.
20896 Turn on highlighting in all buffers.
20898 Create menus in the group buffer.
20900 Create menus in the summary buffers.
20902 Create menus in the article buffer.
20904 Create menus in the browse buffer.
20906 Create menus in the server buffer.
20908 Create menus in the score buffers.
20910 Create menus in all buffers.
20913 So if you only want highlighting in the article buffer and menus in all
20914 buffers, you could say something like:
20917 (setq gnus-visual '(article-highlight menu))
20920 If you want highlighting only and no menus whatsoever, you'd say:
20923 (setq gnus-visual '(highlight))
20926 If @code{gnus-visual} is @code{t}, highlighting and menus will be used
20927 in all Gnus buffers.
20929 Other general variables that influence the look of all buffers include:
20932 @item gnus-mouse-face
20933 @vindex gnus-mouse-face
20934 This is the face (i.e., font) used for mouse highlighting in Gnus. No
20935 mouse highlights will be done if @code{gnus-visual} is @code{nil}.
20939 There are hooks associated with the creation of all the different menus:
20943 @item gnus-article-menu-hook
20944 @vindex gnus-article-menu-hook
20945 Hook called after creating the article mode menu.
20947 @item gnus-group-menu-hook
20948 @vindex gnus-group-menu-hook
20949 Hook called after creating the group mode menu.
20951 @item gnus-summary-menu-hook
20952 @vindex gnus-summary-menu-hook
20953 Hook called after creating the summary mode menu.
20955 @item gnus-server-menu-hook
20956 @vindex gnus-server-menu-hook
20957 Hook called after creating the server mode menu.
20959 @item gnus-browse-menu-hook
20960 @vindex gnus-browse-menu-hook
20961 Hook called after creating the browse mode menu.
20963 @item gnus-score-menu-hook
20964 @vindex gnus-score-menu-hook
20965 Hook called after creating the score mode menu.
20976 Those new-fangled @dfn{mouse} contraptions is very popular with the
20977 young, hep kids who don't want to learn the proper way to do things
20978 these days. Why, I remember way back in the summer of '89, when I was
20979 using Emacs on a Tops 20 system. Three hundred users on one single
20980 machine, and every user was running Simula compilers. Bah!
20984 @vindex gnus-carpal
20985 Well, you can make Gnus display bufferfuls of buttons you can click to
20986 do anything by setting @code{gnus-carpal} to @code{t}. Pretty simple,
20987 really. Tell the chiropractor I sent you.
20992 @item gnus-carpal-mode-hook
20993 @vindex gnus-carpal-mode-hook
20994 Hook run in all carpal mode buffers.
20996 @item gnus-carpal-button-face
20997 @vindex gnus-carpal-button-face
20998 Face used on buttons.
21000 @item gnus-carpal-header-face
21001 @vindex gnus-carpal-header-face
21002 Face used on carpal buffer headers.
21004 @item gnus-carpal-group-buffer-buttons
21005 @vindex gnus-carpal-group-buffer-buttons
21006 Buttons in the group buffer.
21008 @item gnus-carpal-summary-buffer-buttons
21009 @vindex gnus-carpal-summary-buffer-buttons
21010 Buttons in the summary buffer.
21012 @item gnus-carpal-server-buffer-buttons
21013 @vindex gnus-carpal-server-buffer-buttons
21014 Buttons in the server buffer.
21016 @item gnus-carpal-browse-buffer-buttons
21017 @vindex gnus-carpal-browse-buffer-buttons
21018 Buttons in the browse buffer.
21021 All the @code{buttons} variables are lists. The elements in these list
21022 are either cons cells where the @code{car} contains a text to be displayed and
21023 the @code{cdr} contains a function symbol, or a simple string.
21031 Gnus, being larger than any program ever written (allegedly), does lots
21032 of strange stuff that you may wish to have done while you're not
21033 present. For instance, you may want it to check for new mail once in a
21034 while. Or you may want it to close down all connections to all servers
21035 when you leave Emacs idle. And stuff like that.
21037 Gnus will let you do stuff like that by defining various
21038 @dfn{handlers}. Each handler consists of three elements: A
21039 @var{function}, a @var{time}, and an @var{idle} parameter.
21041 Here's an example of a handler that closes connections when Emacs has
21042 been idle for thirty minutes:
21045 (gnus-demon-close-connections nil 30)
21048 Here's a handler that scans for PGP headers every hour when Emacs is
21052 (gnus-demon-scan-pgp 60 t)
21055 This @var{time} parameter and than @var{idle} parameter work together
21056 in a strange, but wonderful fashion. Basically, if @var{idle} is
21057 @code{nil}, then the function will be called every @var{time} minutes.
21059 If @var{idle} is @code{t}, then the function will be called after
21060 @var{time} minutes only if Emacs is idle. So if Emacs is never idle,
21061 the function will never be called. But once Emacs goes idle, the
21062 function will be called every @var{time} minutes.
21064 If @var{idle} is a number and @var{time} is a number, the function will
21065 be called every @var{time} minutes only when Emacs has been idle for
21066 @var{idle} minutes.
21068 If @var{idle} is a number and @var{time} is @code{nil}, the function
21069 will be called once every time Emacs has been idle for @var{idle}
21072 And if @var{time} is a string, it should look like @samp{07:31}, and
21073 the function will then be called once every day somewhere near that
21074 time. Modified by the @var{idle} parameter, of course.
21076 @vindex gnus-demon-timestep
21077 (When I say ``minute'' here, I really mean @code{gnus-demon-timestep}
21078 seconds. This is 60 by default. If you change that variable,
21079 all the timings in the handlers will be affected.)
21081 So, if you want to add a handler, you could put something like this in
21082 your @file{~/.gnus.el} file:
21084 @findex gnus-demon-add-handler
21086 (gnus-demon-add-handler 'gnus-demon-close-connections 30 t)
21089 @findex gnus-demon-add-nocem
21090 @findex gnus-demon-add-scanmail
21091 @findex gnus-demon-add-rescan
21092 @findex gnus-demon-add-scan-timestamps
21093 @findex gnus-demon-add-disconnection
21094 Some ready-made functions to do this have been created:
21095 @code{gnus-demon-add-nocem}, @code{gnus-demon-add-disconnection},
21096 @code{gnus-demon-add-nntp-close-connection},
21097 @code{gnus-demon-add-scan-timestamps}, @code{gnus-demon-add-rescan}, and
21098 @code{gnus-demon-add-scanmail}. Just put those functions in your
21099 @file{~/.gnus.el} if you want those abilities.
21101 @findex gnus-demon-init
21102 @findex gnus-demon-cancel
21103 @vindex gnus-demon-handlers
21104 If you add handlers to @code{gnus-demon-handlers} directly, you should
21105 run @code{gnus-demon-init} to make the changes take hold. To cancel all
21106 daemons, you can use the @code{gnus-demon-cancel} function.
21108 Note that adding daemons can be pretty naughty if you over do it. Adding
21109 functions that scan all news and mail from all servers every two seconds
21110 is a sure-fire way of getting booted off any respectable system. So
21119 @dfn{Spamming} is posting the same article lots and lots of times.
21120 Spamming is bad. Spamming is evil.
21122 Spamming is usually canceled within a day or so by various anti-spamming
21123 agencies. These agencies usually also send out @dfn{NoCeM} messages.
21124 NoCeM is pronounced ``no see-'em'', and means what the name
21125 implies---these are messages that make the offending articles, like, go
21128 What use are these NoCeM messages if the articles are canceled anyway?
21129 Some sites do not honor cancel messages and some sites just honor cancels
21130 from a select few people. Then you may wish to make use of the NoCeM
21131 messages, which are distributed in the @samp{alt.nocem.misc} newsgroup.
21133 Gnus can read and parse the messages in this group automatically, and
21134 this will make spam disappear.
21136 There are some variables to customize, of course:
21139 @item gnus-use-nocem
21140 @vindex gnus-use-nocem
21141 Set this variable to @code{t} to set the ball rolling. It is @code{nil}
21144 @item gnus-nocem-groups
21145 @vindex gnus-nocem-groups
21146 Gnus will look for NoCeM messages in the groups in this list. The
21147 default is @code{("news.lists.filters" "news.admin.net-abuse.bulletins"
21148 "alt.nocem.misc" "news.admin.net-abuse.announce")}.
21150 @item gnus-nocem-issuers
21151 @vindex gnus-nocem-issuers
21152 There are many people issuing NoCeM messages. This list says what
21153 people you want to listen to. The default is @code{("Automoose-1"
21154 "clewis@@ferret.ocunix.on.ca" "cosmo.roadkill" "SpamHippo"
21155 "hweede@@snafu.de")}; fine, upstanding citizens all of them.
21157 Known despammers that you can put in this list are listed at
21158 @uref{http://www.xs4all.nl/~rosalind/nocemreg/nocemreg.html}.
21160 You do not have to heed NoCeM messages from all these people---just the
21161 ones you want to listen to. You also don't have to accept all NoCeM
21162 messages from the people you like. Each NoCeM message has a @dfn{type}
21163 header that gives the message a (more or less, usually less) rigorous
21164 definition. Common types are @samp{spam}, @samp{spew}, @samp{mmf},
21165 @samp{binary}, and @samp{troll}. To specify this, you have to use
21166 @code{(@var{issuer} @var{conditions} @dots{})} elements in the list.
21167 Each condition is either a string (which is a regexp that matches types
21168 you want to use) or a list on the form @code{(not @var{string})}, where
21169 @var{string} is a regexp that matches types you don't want to use.
21171 For instance, if you want all NoCeM messages from Chris Lewis except his
21172 @samp{troll} messages, you'd say:
21175 ("clewis@@ferret.ocunix.on.ca" ".*" (not "troll"))
21178 On the other hand, if you just want nothing but his @samp{spam} and
21179 @samp{spew} messages, you'd say:
21182 ("clewis@@ferret.ocunix.on.ca" (not ".*") "spew" "spam")
21185 The specs are applied left-to-right.
21188 @item gnus-nocem-verifyer
21189 @vindex gnus-nocem-verifyer
21191 This should be a function for verifying that the NoCeM issuer is who she
21192 says she is. The default is @code{mc-verify}, which is a Mailcrypt
21193 function. If this is too slow and you don't care for verification
21194 (which may be dangerous), you can set this variable to @code{nil}.
21196 If you want signed NoCeM messages to be verified and unsigned messages
21197 not to be verified (but used anyway), you could do something like:
21200 (setq gnus-nocem-verifyer 'my-gnus-mc-verify)
21202 (defun my-gnus-mc-verify ()
21210 This might be dangerous, though.
21212 @item gnus-nocem-directory
21213 @vindex gnus-nocem-directory
21214 This is where Gnus will store its NoCeM cache files. The default is
21215 @file{~/News/NoCeM/}.
21217 @item gnus-nocem-expiry-wait
21218 @vindex gnus-nocem-expiry-wait
21219 The number of days before removing old NoCeM entries from the cache.
21220 The default is 15. If you make it shorter Gnus will be faster, but you
21221 might then see old spam.
21223 @item gnus-nocem-check-from
21224 @vindex gnus-nocem-check-from
21225 Non-@code{nil} means check for valid issuers in message bodies.
21226 Otherwise don't bother fetching articles unless their author matches a
21227 valid issuer; that is much faster if you are selective about the
21230 @item gnus-nocem-check-article-limit
21231 @vindex gnus-nocem-check-article-limit
21232 If non-@code{nil}, the maximum number of articles to check in any NoCeM
21233 group. NoCeM groups can be huge and very slow to process.
21237 Using NoCeM could potentially be a memory hog. If you have many living
21238 (i. e., subscribed or unsubscribed groups), your Emacs process will grow
21239 big. If this is a problem, you should kill off all (or most) of your
21240 unsubscribed groups (@pxref{Subscription Commands}).
21247 It is very useful to be able to undo actions one has done. In normal
21248 Emacs buffers, it's easy enough---you just push the @code{undo} button.
21249 In Gnus buffers, however, it isn't that simple.
21251 The things Gnus displays in its buffer is of no value whatsoever to
21252 Gnus---it's all just data designed to look nice to the user.
21253 Killing a group in the group buffer with @kbd{C-k} makes the line
21254 disappear, but that's just a side-effect of the real action---the
21255 removal of the group in question from the internal Gnus structures.
21256 Undoing something like that can't be done by the normal Emacs
21257 @code{undo} function.
21259 Gnus tries to remedy this somewhat by keeping track of what the user
21260 does and coming up with actions that would reverse the actions the user
21261 takes. When the user then presses the @code{undo} key, Gnus will run
21262 the code to reverse the previous action, or the previous actions.
21263 However, not all actions are easily reversible, so Gnus currently offers
21264 a few key functions to be undoable. These include killing groups,
21265 yanking groups, and changing the list of read articles of groups.
21266 That's it, really. More functions may be added in the future, but each
21267 added function means an increase in data to be stored, so Gnus will
21268 never be totally undoable.
21270 @findex gnus-undo-mode
21271 @vindex gnus-use-undo
21273 The undoability is provided by the @code{gnus-undo-mode} minor mode. It
21274 is used if @code{gnus-use-undo} is non-@code{nil}, which is the
21275 default. The @kbd{C-M-_} key performs the @code{gnus-undo}
21276 command, which should feel kinda like the normal Emacs @code{undo}
21280 @node Predicate Specifiers
21281 @section Predicate Specifiers
21282 @cindex predicate specifiers
21284 Some Gnus variables are @dfn{predicate specifiers}. This is a special
21285 form that allows flexible specification of predicates without having
21286 to type all that much.
21288 These specifiers are lists consisting of functions, symbols and lists.
21293 (or gnus-article-unseen-p
21294 gnus-article-unread-p)
21297 The available symbols are @code{or}, @code{and} and @code{not}. The
21298 functions all take one parameter.
21300 @findex gnus-make-predicate
21301 Internally, Gnus calls @code{gnus-make-predicate} on these specifiers
21302 to create a function that can be called. This input parameter to this
21303 function will be passed along to all the functions in the predicate
21308 @section Moderation
21311 If you are a moderator, you can use the @file{gnus-mdrtn.el} package.
21312 It is not included in the standard Gnus package. Write a mail to
21313 @samp{larsi@@gnus.org} and state what group you moderate, and you'll
21316 The moderation package is implemented as a minor mode for summary
21320 (add-hook 'gnus-summary-mode-hook 'gnus-moderate)
21323 in your @file{~/.gnus.el} file.
21325 If you are the moderator of @samp{rec.zoofle}, this is how it's
21330 You split your incoming mail by matching on
21331 @samp{Newsgroups:.*rec.zoofle}, which will put all the to-be-posted
21332 articles in some mail group---for instance, @samp{nnml:rec.zoofle}.
21335 You enter that group once in a while and post articles using the @kbd{e}
21336 (edit-and-post) or @kbd{s} (just send unedited) commands.
21339 If, while reading the @samp{rec.zoofle} newsgroup, you happen upon some
21340 articles that weren't approved by you, you can cancel them with the
21344 To use moderation mode in these two groups, say:
21347 (setq gnus-moderated-list
21348 "^nnml:rec.zoofle$\\|^rec.zoofle$")
21352 @node Image Enhancements
21353 @section Image Enhancements
21355 XEmacs, as well as Emacs 21, is able to display pictures and stuff, so
21356 Gnus has taken advantage of that.
21359 * Picons:: How to display pictures of what you're reading.
21360 * Smileys:: Show all those happy faces the way they were meant to be shown.
21361 * X-Face:: Display a funky, teensy black-and-white image.
21362 * XVarious:: Other XEmacsy Gnusey variables.
21375 So@dots{} You want to slow down your news reader even more! This is a
21376 good way to do so. Its also a great way to impress people staring
21377 over your shoulder as you read news.
21379 What are Picons? To quote directly from the Picons Web site:
21388 @dfn{Picons} is short for ``personal icons''. They're small,
21389 constrained images used to represent users and domains on the net,
21390 organized into databases so that the appropriate image for a given
21391 e-mail address can be found. Besides users and domains, there are picon
21392 databases for Usenet newsgroups and weather forecasts. The picons are
21393 in either monochrome @code{XBM} format or color @code{XPM} and
21394 @code{GIF} formats.
21397 @vindex gnus-picon-databases
21398 For instructions on obtaining and installing the picons databases,
21399 point your Web browser at
21400 @uref{http://www.cs.indiana.edu/picons/ftp/index.html}.
21402 If you are using Debian GNU/Linux, saying @samp{apt-get install
21403 picons.*} will install the picons where Gnus can find them.
21405 To enable displaying picons, simply make sure that
21406 @code{gnus-picon-databases} points to the directory containing the
21409 The following variables offer control over where things are located.
21413 @item gnus-picon-databases
21414 @vindex gnus-picon-databases
21415 The location of the picons database. This is a list of directories
21416 containing the @file{news}, @file{domains}, @file{users} (and so on)
21417 subdirectories. Defaults to @code{("/usr/lib/picon"
21418 "/usr/local/faces")}.
21420 @item gnus-picon-news-directories
21421 @vindex gnus-picon-news-directories
21422 List of subdirectories to search in @code{gnus-picon-databases} for
21423 newsgroups faces. @code{("news")} is the default.
21425 @item gnus-picon-user-directories
21426 @vindex gnus-picon-user-directories
21427 List of subdirectories to search in @code{gnus-picon-databases} for user
21428 faces. @code{("users" "usenix" "local" "misc")} is the default.
21430 @item gnus-picon-domain-directories
21431 @vindex gnus-picon-domain-directories
21432 List of subdirectories to search in @code{gnus-picon-databases} for
21433 domain name faces. Defaults to @code{("domains")}. Some people may
21434 want to add @samp{"unknown"} to this list.
21436 @item gnus-picon-file-types
21437 @vindex gnus-picon-file-types
21438 Ordered list of suffixes on picon file names to try. Defaults to
21439 @code{("xpm" "gif" "xbm")} minus those not builtin your Emacs.
21444 @subsection Smileys
21449 \gnusfig{-3cm}{0.5cm}{\epsfig{figure=ps/BigFace,height=20cm}}
21454 @dfn{Smiley} is a package separate from Gnus, but since Gnus is
21455 currently the only package that uses Smiley, it is documented here.
21457 In short---to use Smiley in Gnus, put the following in your
21458 @file{~/.gnus.el} file:
21461 (setq gnus-treat-display-smileys t)
21464 Smiley maps text smiley faces---@samp{:-)}, @samp{8-)}, @samp{:-(} and
21465 the like---to pictures and displays those instead of the text smiley
21466 faces. The conversion is controlled by a list of regexps that matches
21467 text and maps that to file names.
21469 @vindex smiley-regexp-alist
21470 The alist used is specified by the @code{smiley-regexp-alist}
21471 variable. The first item in each element is the regexp to be matched;
21472 the second element is the regexp match group that is to be replaced by
21473 the picture; and the third element is the name of the file to be
21476 The following variables customize where Smiley will look for these
21481 @item smiley-data-directory
21482 @vindex smiley-data-directory
21483 Where Smiley will look for smiley faces files.
21485 @item gnus-smiley-file-types
21486 @vindex gnus-smiley-file-types
21487 List of suffixes on smiley file names to try.
21496 @code{X-Face} headers describe a 48x48 pixel black-and-white (1 bit
21497 depth) image that's supposed to represent the author of the message.
21498 It seems to be supported by an ever-growing number of mail and news
21502 @findex gnus-article-display-x-face
21503 @findex gnus-article-x-face-command
21504 @vindex gnus-article-x-face-command
21505 @vindex gnus-article-x-face-too-ugly
21513 Decoding an @code{X-Face} header either requires an Emacs that has
21514 @samp{compface} support (which most XEmacs versions has), or that you
21515 have @samp{compface} installed on your system. If either is true,
21516 Gnus will default to displaying @code{X-Face} headers.
21518 The variable that controls this is the
21519 @code{gnus-article-x-face-command} variable. If this variable is a
21520 string, this string will be executed in a sub-shell. If it is a
21521 function, this function will be called with the face as the argument.
21522 If the @code{gnus-article-x-face-too-ugly} (which is a regexp) matches
21523 the @code{From} header, the face will not be shown.
21525 The default action under Emacs 20 is to fork off the @code{display}
21526 program@footnote{@code{display} is from the ImageMagick package. For
21527 the @code{uncompface} and @code{icontopbm} programs look for a package
21528 like @code{compface} or @code{faces-xface} on a GNU/Linux system.} to
21531 Under XEmacs or Emacs 21+ with suitable image support, the default
21532 action is to display the face before the @code{From} header. (It's
21533 nicer if XEmacs has been compiled with @code{X-Face} support---that
21534 will make display somewhat faster. If there's no native @code{X-Face}
21535 support, Gnus will try to convert the @code{X-Face} header using
21536 external programs from the @code{pbmplus} package and
21537 friends.@footnote{On a GNU/Linux system look for packages with names
21538 like @code{netpbm}, @code{libgr-progs} and @code{compface}.})
21540 (Note: @code{x-face} is used in the variable/function names, not
21543 Gnus provides a few convenience functions and variables to allow
21544 easier insertion of X-Face headers in outgoing messages.
21546 @findex gnus-random-x-face
21547 @vindex gnus-convert-pbm-to-x-face-command
21548 @vindex gnus-x-face-directory
21549 @code{gnus-random-x-face} goes through all the @samp{pbm} files in
21550 @code{gnus-x-face-directory} and picks one at random, and then
21551 converts it to the X-Face format by using the
21552 @code{gnus-convert-pbm-to-x-face-command} shell command. The
21553 @samp{pbm} files should be 48x48 pixels big. It returns the X-Face
21554 header data as a string.
21556 @findex gnus-insert-random-x-face-header
21557 @code{gnus-insert-random-x-face-header} calls
21558 @code{gnus-random-x-face} and inserts a @samp{X-Face} header with the
21559 randomly generated data.
21561 @findex gnus-x-face-from-file
21562 @vindex gnus-convert-image-to-x-face-command
21563 @code{gnus-x-face-from-file} takes a GIF file as the parameter, and then
21564 converts the file to X-Face format by using the
21565 @code{gnus-convert-image-to-x-face-command} shell command.
21567 Here's how you would typically use the first function. Put something
21568 like the following in your @file{~/.gnus.el} file:
21571 (setq message-required-news-headers
21572 (nconc message-required-news-headers
21573 (list '(X-Face . gnus-random-x-face))))
21576 Using the last function would be something like this:
21579 (setq message-required-news-headers
21580 (nconc message-required-news-headers
21581 (list '(X-Face . (lambda ()
21582 (gnus-x-face-from-file
21583 "~/My-face.gif"))))))
21588 @subsection Various XEmacs Variables
21591 @item gnus-xmas-glyph-directory
21592 @vindex gnus-xmas-glyph-directory
21593 This is where Gnus will look for pictures. Gnus will normally
21594 auto-detect this directory, but you may set it manually if you have an
21595 unusual directory structure.
21597 @item gnus-xmas-logo-color-alist
21598 @vindex gnus-xmas-logo-color-alist
21599 This is an alist where the key is a type symbol and the values are the
21600 foreground and background color of the splash page glyph.
21602 @item gnus-xmas-logo-color-style
21603 @vindex gnus-xmas-logo-color-style
21604 This is the key used to look up the color in the alist described above.
21605 Valid values include @code{flame}, @code{pine}, @code{moss},
21606 @code{irish}, @code{sky}, @code{tin}, @code{velvet}, @code{grape},
21607 @code{labia}, @code{berry}, @code{neutral}, and @code{september}.
21609 @item gnus-xmas-modeline-glyph
21610 @vindex gnus-xmas-modeline-glyph
21611 A glyph displayed in all Gnus mode lines. It is a tiny gnu head by
21616 @subsubsection Toolbar
21620 @item gnus-use-toolbar
21621 @vindex gnus-use-toolbar
21622 If @code{nil}, don't display toolbars. If non-@code{nil}, it should be
21623 one of @code{default-toolbar}, @code{top-toolbar}, @code{bottom-toolbar},
21624 @code{right-toolbar}, or @code{left-toolbar}.
21626 @item gnus-group-toolbar
21627 @vindex gnus-group-toolbar
21628 The toolbar in the group buffer.
21630 @item gnus-summary-toolbar
21631 @vindex gnus-summary-toolbar
21632 The toolbar in the summary buffer.
21634 @item gnus-summary-mail-toolbar
21635 @vindex gnus-summary-mail-toolbar
21636 The toolbar in the summary buffer of mail groups.
21647 @node Fuzzy Matching
21648 @section Fuzzy Matching
21649 @cindex fuzzy matching
21651 Gnus provides @dfn{fuzzy matching} of @code{Subject} lines when doing
21652 things like scoring, thread gathering and thread comparison.
21654 As opposed to regular expression matching, fuzzy matching is very fuzzy.
21655 It's so fuzzy that there's not even a definition of what @dfn{fuzziness}
21656 means, and the implementation has changed over time.
21658 Basically, it tries to remove all noise from lines before comparing.
21659 @samp{Re: }, parenthetical remarks, white space, and so on, are filtered
21660 out of the strings before comparing the results. This often leads to
21661 adequate results---even when faced with strings generated by text
21662 manglers masquerading as newsreaders.
21665 @node Thwarting Email Spam
21666 @section Thwarting Email Spam
21670 @cindex unsolicited commercial email
21672 In these last days of the Usenet, commercial vultures are hanging about
21673 and grepping through news like crazy to find email addresses they can
21674 foist off their scams and products to. As a reaction to this, many
21675 people have started putting nonsense addresses into their @code{From}
21676 lines. I think this is counterproductive---it makes it difficult for
21677 people to send you legitimate mail in response to things you write, as
21678 well as making it difficult to see who wrote what. This rewriting may
21679 perhaps be a bigger menace than the unsolicited commercial email itself
21682 The biggest problem I have with email spam is that it comes in under
21683 false pretenses. I press @kbd{g} and Gnus merrily informs me that I
21684 have 10 new emails. I say ``Golly gee! Happy is me!'' and select the
21685 mail group, only to find two pyramid schemes, seven advertisements
21686 (``New! Miracle tonic for growing full, lustrous hair on your toes!'')
21687 and one mail asking me to repent and find some god.
21689 This is annoying. Here's what you can do about it.
21692 * The problem of spam:: Some background, and some solutions
21693 * Anti-Spam Basics:: Simple steps to reduce the amount of spam.
21694 * SpamAssassin:: How to use external anti-spam tools.
21695 * Hashcash:: Reduce spam by burning CPU time.
21696 * Filtering Spam Using The Spam ELisp Package::
21697 * Filtering Spam Using Statistics with spam-stat::
21700 @node The problem of spam
21701 @subsection The problem of spam
21703 @cindex spam filtering approaches
21704 @cindex filtering approaches, spam
21706 @cindex unsolicited commercial email
21708 First, some background on spam.
21710 If you have access to e-mail, you are familiar with spam (technically
21711 termed @acronym{UCE}, Unsolicited Commercial E-mail). Simply put, it exists
21712 because e-mail delivery is very cheap compared to paper mail, so only
21713 a very small percentage of people need to respond to an UCE to make it
21714 worthwhile to the advertiser. Ironically, one of the most common
21715 spams is the one offering a database of e-mail addresses for further
21716 spamming. Senders of spam are usually called @emph{spammers}, but terms like
21717 @emph{vermin}, @emph{scum}, and @emph{morons} are in common use as well.
21719 Spam comes from a wide variety of sources. It is simply impossible to
21720 dispose of all spam without discarding useful messages. A good
21721 example is the TMDA system, which requires senders
21722 unknown to you to confirm themselves as legitimate senders before
21723 their e-mail can reach you. Without getting into the technical side
21724 of TMDA, a downside is clearly that e-mail from legitimate sources may
21725 be discarded if those sources can't or won't confirm themselves
21726 through the TMDA system. Another problem with TMDA is that it
21727 requires its users to have a basic understanding of e-mail delivery
21730 The simplest approach to filtering spam is filtering. If you get 200
21731 spam messages per day from @samp{random-address@@vmadmin.com}, you
21732 block @samp{vmadmin.com}. If you get 200 messages about
21733 @samp{VIAGRA}, you discard all messages with @samp{VIAGRA} in the
21734 message. This, unfortunately, is a great way to discard legitimate
21735 e-mail. For instance, the very informative and useful RISKS digest
21736 has been blocked by overzealous mail filters because it
21737 @strong{contained} words that were common in spam messages.
21738 Nevertheless, in isolated cases, with great care, direct filtering of
21739 mail can be useful.
21741 Another approach to filtering e-mail is the distributed spam
21742 processing, for instance DCC implements such a system. In essence,
21743 @code{N} systems around the world agree that a machine @samp{X} in
21744 China, Ghana, or California is sending out spam e-mail, and these
21745 @code{N} systems enter @samp{X} or the spam e-mail from @samp{X} into
21746 a database. The criteria for spam detection vary - it may be the
21747 number of messages sent, the content of the messages, and so on. When
21748 a user of the distributed processing system wants to find out if a
21749 message is spam, he consults one of those @code{N} systems.
21751 Distributed spam processing works very well against spammers that send
21752 a large number of messages at once, but it requires the user to set up
21753 fairly complicated checks. There are commercial and free distributed
21754 spam processing systems. Distributed spam processing has its risks as
21755 well. For instance legitimate e-mail senders have been accused of
21756 sending spam, and their web sites have been shut down for some time
21757 because of the incident.
21759 The statistical approach to spam filtering is also popular. It is
21760 based on a statistical analysis of previous spam messages. Usually
21761 the analysis is a simple word frequency count, with perhaps pairs of
21762 words or 3-word combinations thrown into the mix. Statistical
21763 analysis of spam works very well in most of the cases, but it can
21764 classify legitimate e-mail as spam in some cases. It takes time to
21765 run the analysis, the full message must be analyzed, and the user has
21766 to store the database of spam analyses.
21768 @node Anti-Spam Basics
21769 @subsection Anti-Spam Basics
21773 @cindex unsolicited commercial email
21775 One way of dealing with spam is having Gnus split out all spam into a
21776 @samp{spam} mail group (@pxref{Splitting Mail}).
21778 First, pick one (1) valid mail address that you can be reached at, and
21779 put it in your @code{From} header of all your news articles. (I've
21780 chosen @samp{larsi@@trym.ifi.uio.no}, but for many addresses on the form
21781 @samp{larsi+usenet@@ifi.uio.no} will be a better choice. Ask your
21782 sysadmin whether your sendmail installation accepts keywords in the local
21783 part of the mail address.)
21786 (setq message-default-news-headers
21787 "From: Lars Magne Ingebrigtsen <larsi@@trym.ifi.uio.no>\n")
21790 Then put the following split rule in @code{nnmail-split-fancy}
21791 (@pxref{Fancy Mail Splitting}):
21796 (to "larsi@@trym.ifi.uio.no"
21797 (| ("subject" "re:.*" "misc")
21798 ("references" ".*@@.*" "misc")
21804 This says that all mail to this address is suspect, but if it has a
21805 @code{Subject} that starts with a @samp{Re:} or has a @code{References}
21806 header, it's probably ok. All the rest goes to the @samp{spam} group.
21807 (This idea probably comes from Tim Pierce.)
21809 In addition, many mail spammers talk directly to your @sc{smtp} server
21810 and do not include your email address explicitly in the @code{To}
21811 header. Why they do this is unknown---perhaps it's to thwart this
21812 thwarting scheme? In any case, this is trivial to deal with---you just
21813 put anything not addressed to you in the @samp{spam} group by ending
21814 your fancy split rule in this way:
21819 (to "larsi" "misc")
21823 In my experience, this will sort virtually everything into the right
21824 group. You still have to check the @samp{spam} group from time to time to
21825 check for legitimate mail, though. If you feel like being a good net
21826 citizen, you can even send off complaints to the proper authorities on
21827 each unsolicited commercial email---at your leisure.
21829 If you are also a lazy net citizen, you will probably prefer complaining
21830 automatically with the @file{gnus-junk.el} package, available FOR FREE
21831 at @* @uref{http://stud2.tuwien.ac.at/~e9426626/gnus-junk.html}.
21832 Since most e-mail spam is sent automatically, this may reconcile the
21833 cosmic balance somewhat.
21835 This works for me. It allows people an easy way to contact me (they can
21836 just press @kbd{r} in the usual way), and I'm not bothered at all with
21837 spam. It's a win-win situation. Forging @code{From} headers to point
21838 to non-existent domains is yucky, in my opinion.
21843 @subsection SpamAssassin, Vipul's Razor, DCC, etc
21844 @cindex SpamAssassin
21845 @cindex Vipul's Razor
21848 The days where the hints in the previous section was sufficient in
21849 avoiding spam is coming to an end. There are many tools out there
21850 that claim to reduce the amount of spam you get. This section could
21851 easily become outdated fast, as new products replace old, but
21852 fortunately most of these tools seem to have similar interfaces. Even
21853 though this section will use SpamAssassin as an example, it should be
21854 easy to adapt it to most other tools.
21856 If the tool you are using is not installed on the mail server, you
21857 need to invoke it yourself. Ideas on how to use the
21858 @code{:postscript} mail source parameter (@pxref{Mail Source
21859 Specifiers}) follows.
21863 '((file :prescript "formail -bs spamassassin < /var/mail/%u")
21866 :postscript "mv %t /tmp/foo; formail -bs spamc < /tmp/foo > %t")))
21869 Once you managed to process your incoming spool somehow, thus making
21870 the mail contain e.g. a header indicating it is spam, you are ready to
21871 filter it out. Using normal split methods (@pxref{Splitting Mail}):
21874 (setq nnmail-split-methods '(("spam" "^X-Spam-Flag: YES")
21878 Or using fancy split methods (@pxref{Fancy Mail Splitting}):
21881 (setq nnmail-split-methods 'nnmail-split-fancy
21882 nnmail-split-fancy '(| ("X-Spam-Flag" "YES" "spam")
21886 Some people might not like the idea of piping the mail through various
21887 programs using a @code{:prescript} (if some program is buggy, you
21888 might lose all mail). If you are one of them, another solution is to
21889 call the external tools during splitting. Example fancy split method:
21892 (setq nnmail-split-fancy '(| (: kevin-spamassassin)
21894 (defun kevin-spamassassin ()
21896 (let ((buf (or (get-buffer " *nnmail incoming*")
21897 (get-buffer " *nnml move*"))))
21899 (progn (message "Oops, cannot find message buffer") nil)
21901 (if (eq 1 (call-process-region (point-min) (point-max)
21902 "spamc" nil nil nil "-c"))
21906 That is about it. As some spam is likely to get through anyway, you
21907 might want to have a nifty function to call when you happen to read
21908 spam. And here is the nifty function:
21911 (defun my-gnus-raze-spam ()
21912 "Submit SPAM to Vipul's Razor, then mark it as expirable."
21914 (gnus-summary-show-raw-article)
21915 (gnus-summary-save-in-pipe "razor-report -f -d")
21916 (gnus-summary-mark-as-expirable 1))
21920 @subsection Hashcash
21923 A novel technique to fight spam is to require senders to do something
21924 costly for each message they send. This has the obvious drawback that
21925 you cannot rely on that everyone in the world uses this technique,
21926 since it is not part of the Internet standards, but it may be useful
21927 in smaller communities.
21929 While the tools in the previous section work well in practice, they
21930 work only because the tools are constantly maintained and updated as
21931 new form of spam appears. This means that a small percentage of spam
21932 will always get through. It also means that somewhere, someone needs
21933 to read lots of spam to update these tools. Hashcash avoids that, but
21934 instead requires that everyone you communicate with supports the
21935 scheme. You can view the two approaches as pragmatic vs dogmatic.
21936 The approaches have their own advantages and disadvantages, but as
21937 often in the real world, a combination of them is stronger than either
21938 one of them separately.
21941 The ``something costly'' is to burn CPU time, more specifically to
21942 compute a hash collision up to a certain number of bits. The
21943 resulting hashcash cookie is inserted in a @samp{X-Hashcash:}
21944 header. For more details, and for the external application
21945 @code{hashcash} you need to install to use this feature, see
21946 @uref{http://www.cypherspace.org/~adam/hashcash/}. Even more
21947 information can be found at @uref{http://www.camram.org/}.
21949 If you wish to call hashcash for each message you send, say something
21953 (require 'hashcash)
21954 (add-hook 'message-send-hook 'mail-add-payment)
21957 The @code{hashcash.el} library can be found at
21958 @uref{http://users.actrix.gen.nz/mycroft/hashcash.el}, or in the Gnus
21959 development contrib directory.
21961 You will need to set up some additional variables as well:
21965 @item hashcash-default-payment
21966 @vindex hashcash-default-payment
21967 This variable indicates the default number of bits the hash collision
21968 should consist of. By default this is 0, meaning nothing will be
21969 done. Suggested useful values include 17 to 29.
21971 @item hashcash-payment-alist
21972 @vindex hashcash-payment-alist
21973 Some receivers may require you to spend burn more CPU time than the
21974 default. This variable contains a list of @samp{(@var{addr}
21975 @var{amount})} cells, where @var{addr} is the receiver (email address
21976 or newsgroup) and @var{amount} is the number of bits in the collision
21977 that is needed. It can also contain @samp{(@var{addr} @var{string}
21978 @var{amount})} cells, where the @var{string} is the string to use
21979 (normally the email address or newsgroup name is used).
21983 Where the @code{hashcash} binary is installed.
21987 Currently there is no built in functionality in Gnus to verify
21988 hashcash cookies, it is expected that this is performed by your hand
21989 customized mail filtering scripts. Improvements in this area would be
21990 a useful contribution, however.
21992 @node Filtering Spam Using The Spam ELisp Package
21993 @subsection Filtering Spam Using The Spam ELisp Package
21994 @cindex spam filtering
21997 The idea behind @code{spam.el} is to have a control center for spam detection
21998 and filtering in Gnus. To that end, @code{spam.el} does two things: it
21999 filters incoming mail, and it analyzes mail known to be spam or ham.
22000 @emph{Ham} is the name used throughout @code{spam.el} to indicate
22003 So, what happens when you load @code{spam.el}? First of all, you get
22004 the following keyboard commands:
22014 @findex gnus-summary-mark-as-spam
22015 @code{gnus-summary-mark-as-spam}.
22017 Mark current article as spam, showing it with the @samp{$} mark.
22018 Whenever you see a spam article, make sure to mark its summary line
22019 with @kbd{M-d} before leaving the group. This is done automatically
22020 for unread articles in @emph{spam} groups.
22026 @findex spam-bogofilter-score
22027 @code{spam-bogofilter-score}.
22029 You must have Bogofilter installed for that command to work properly.
22035 Also, when you load @code{spam.el}, you will be able to customize its
22036 variables. Try @code{customize-group} on the @samp{spam} variable
22039 The concepts of ham processors and spam processors are very important.
22040 Ham processors and spam processors for a group can be set with the
22041 @code{spam-process} group parameter, or the
22042 @code{gnus-spam-process-newsgroups} variable. Ham processors take
22043 mail known to be non-spam (@emph{ham}) and process it in some way so
22044 that later similar mail will also be considered non-spam. Spam
22045 processors take mail known to be spam and process it so similar spam
22046 will be detected later.
22048 Gnus learns from the spam you get. You have to collect your spam in
22049 one or more spam groups, and set or customize the variable
22050 @code{spam-junk-mailgroups} as appropriate. You can also declare
22051 groups to contain spam by setting their group parameter
22052 @code{spam-contents} to @code{gnus-group-spam-classification-spam}, or
22053 by customizing the corresponding variable
22054 @code{gnus-spam-newsgroup-contents}. The @code{spam-contents} group
22055 parameter and the @code{gnus-spam-newsgroup-contents} variable can
22056 also be used to declare groups as @emph{ham} groups if you set their
22057 classification to @code{gnus-group-spam-classification-ham}. If
22058 groups are not classified by means of @code{spam-junk-mailgroups},
22059 @code{spam-contents}, or @code{gnus-spam-newsgroup-contents}, they are
22060 considered @emph{unclassified}. All groups are unclassified by
22063 In spam groups, all messages are considered to be spam by default:
22064 they get the @samp{$} mark when you enter the group. You must review
22065 these messages from time to time and remove the @samp{$} mark for
22066 every message that is not spam after all. To remove the @samp{$}
22067 mark, you can use @kbd{M-u} to ``unread'' the article, or @kbd{d} for
22068 declaring it read the non-spam way. When you leave a group, all
22069 spam-marked (@samp{$}) articles are sent to a spam processor which
22070 will study them as spam samples.
22072 Messages may also be deleted in various other ways, and unless
22073 @code{spam-ham-marks} gets overridden below, marks @samp{R} and
22074 @samp{r} for default read or explicit delete, marks @samp{X} and
22075 @samp{K} for automatic or explicit kills, as well as mark @samp{Y} for
22076 low scores, are all considered to be associated with articles which
22077 are not spam. This assumption might be false, in particular if you
22078 use kill files or score files as means for detecting genuine spam, you
22079 should then adjust the @code{spam-ham-marks} variable.
22081 @defvar spam-ham-marks
22082 You can customize this variable to be the list of marks you want to
22083 consider ham. By default, the list contains the deleted, read,
22084 killed, kill-filed, and low-score marks.
22087 @defvar spam-spam-marks
22088 You can customize this variable to be the list of marks you want to
22089 consider spam. By default, the list contains only the spam mark.
22092 When you leave @emph{any} group, regardless of its
22093 @code{spam-contents} classification, all spam-marked articles are sent
22094 to a spam processor, which will study these as spam samples. If you
22095 explicit kill a lot, you might sometimes end up with articles marked
22096 @samp{K} which you never saw, and which might accidentally contain
22097 spam. Best is to make sure that real spam is marked with @samp{$},
22100 When you leave a @emph{spam} group, all spam-marked articles are
22101 marked as expired after processing with the spam processor. This is
22102 not done for @emph{unclassified} or @emph{ham} groups. Also, any
22103 @strong{ham} articles in a spam group will be moved to a location
22104 determined by either the @code{ham-process-destination} group
22105 parameter or a match in the @code{gnus-ham-process-destinations}
22106 variable, which is a list of regular expressions matched with group
22107 names (it's easiest to customize this variable with
22108 @code{customize-variable gnus-ham-process-destinations}). The ultimate
22109 location is a group name. If the @code{ham-process-destination}
22110 parameter is not set, spam articles are only expired.
22112 When you leave a @emph{ham} group, all ham-marked articles are sent to
22113 a ham processor, which will study these as non-spam samples.
22115 When you leave a @emph{ham} or @emph{unclassified} group, all
22116 @strong{spam} articles are moved to a location determined by either
22117 the @code{spam-process-destination} group parameter or a match in the
22118 @code{gnus-spam-process-destinations} variable, which is a list of
22119 regular expressions matched with group names (it's easiest to
22120 customize this variable with @code{customize-variable
22121 gnus-spam-process-destinations}). The ultimate location is a group
22122 name. If the @code{spam-process-destination} parameter is not set,
22123 the spam articles are only expired.
22125 To use the @code{spam.el} facilities for incoming mail filtering, you
22126 must add the following to your fancy split list
22127 @code{nnmail-split-fancy} or @code{nnimap-split-fancy}:
22133 Note that the fancy split may be called @code{nnmail-split-fancy} or
22134 @code{nnimap-split-fancy}, depending on whether you use the nnmail or
22135 nnimap back ends to retrieve your mail.
22137 The @code{spam-split} function will process incoming mail and send the
22138 mail considered to be spam into the group name given by the variable
22139 @code{spam-split-group}. By default that group name is @samp{spam},
22140 but you can customize it.
22142 @emph{Note for IMAP users}
22144 The boolean variable @code{nnimap-split-download-body} needs to be
22145 set, if you want to split based on the whole message instead of just
22146 the headers. By default, the nnimap backend will only retrieve the
22147 message headers. If you use spam-check-bogofilter, spam-check-ifile,
22148 or spam-check-stat (the splitters that can benefit from the full
22149 message body), you should set this variable. It is not set by default
22150 because it will slow IMAP down.
22152 @xref{Splitting in IMAP}.
22154 @emph{TODO: Currently, spam.el only supports insertion of articles
22155 into a backend. There is no way to tell spam.el that an article is no
22156 longer spam or ham.}
22158 @emph{TODO: spam.el needs to provide a uniform way of training all the
22159 statistical databases. Some have that functionality built-in, others
22162 The following are the methods you can use to control the behavior of
22163 @code{spam-split} and their corresponding spam and ham processors:
22166 * Blacklists and Whitelists::
22167 * BBDB Whitelists::
22169 * Regular Expressions Header Matching::
22171 * ifile spam filtering::
22172 * spam-stat spam filtering::
22173 * Extending the spam elisp package::
22176 @node Blacklists and Whitelists
22177 @subsubsection Blacklists and Whitelists
22178 @cindex spam filtering
22179 @cindex whitelists, spam filtering
22180 @cindex blacklists, spam filtering
22183 @defvar spam-use-blacklist
22185 Set this variable to @code{t} if you want to use blacklists when
22186 splitting incoming mail. Messages whose senders are in the blacklist
22187 will be sent to the @code{spam-split-group}. This is an explicit
22188 filter, meaning that it acts only on mail senders @emph{declared} to
22193 @defvar spam-use-whitelist
22195 Set this variable to @code{t} if you want to use whitelists when
22196 splitting incoming mail. Messages whose senders are not in the
22197 whitelist will be sent to the next spam-split rule. This is an
22198 explicit filter, meaning that unless someone is in the whitelist, their
22199 messages are not assumed to be spam or ham.
22203 @defvar spam-use-whitelist-exclusive
22205 Set this variable to @code{t} if you want to use whitelists as an
22206 implicit filter, meaning that every message will be considered spam
22207 unless the sender is in the whitelist. Use with care.
22211 @defvar gnus-group-spam-exit-processor-blacklist
22213 Add this symbol to a group's @code{spam-process} parameter by
22214 customizing the group parameters or the
22215 @code{gnus-spam-process-newsgroups} variable. When this symbol is
22216 added to a group's @code{spam-process} parameter, the senders of
22217 spam-marked articles will be added to the blacklist.
22221 @defvar gnus-group-ham-exit-processor-whitelist
22223 Add this symbol to a group's @code{spam-process} parameter by
22224 customizing the group parameters or the
22225 @code{gnus-spam-process-newsgroups} variable. When this symbol is
22226 added to a group's @code{spam-process} parameter, the senders of
22227 ham-marked articles in @emph{ham} groups will be added to the
22228 whitelist. Note that this ham processor has no effect in @emph{spam}
22229 or @emph{unclassified} groups.
22233 Blacklists are lists of regular expressions matching addresses you
22234 consider to be spam senders. For instance, to block mail from any
22235 sender at @samp{vmadmin.com}, you can put @samp{vmadmin.com} in your
22236 blacklist. You start out with an empty blacklist. Blacklist entries
22237 use the Emacs regular expression syntax.
22239 Conversely, whitelists tell Gnus what addresses are considered
22240 legitimate. All messages from whitelisted addresses are considered
22241 non-spam. Also see @ref{BBDB Whitelists}. Whitelist entries use the
22242 Emacs regular expression syntax.
22244 The blacklist and whitelist file locations can be customized with the
22245 @code{spam-directory} variable (@file{~/News/spam} by default), or
22246 the @code{spam-whitelist} and @code{spam-blacklist} variables
22247 directly. The whitelist and blacklist files will by default be in the
22248 @code{spam-directory} directory, named @file{whitelist} and
22249 @file{blacklist} respectively.
22251 @node BBDB Whitelists
22252 @subsubsection BBDB Whitelists
22253 @cindex spam filtering
22254 @cindex BBDB whitelists, spam filtering
22255 @cindex BBDB, spam filtering
22258 @defvar spam-use-BBDB
22260 Analogous to @code{spam-use-whitelist} (@pxref{Blacklists and
22261 Whitelists}), but uses the BBDB as the source of whitelisted
22262 addresses, without regular expressions. You must have the BBDB loaded
22263 for @code{spam-use-BBDB} to work properly. Messages whose senders are
22264 not in the BBDB will be sent to the next spam-split rule. This is an
22265 explicit filter, meaning that unless someone is in the BBDB, their
22266 messages are not assumed to be spam or ham.
22270 @defvar spam-use-BBDB-exclusive
22272 Set this variable to @code{t} if you want to use the BBDB as an
22273 implicit filter, meaning that every message will be considered spam
22274 unless the sender is in the BBDB. Use with care. Only sender
22275 addresses in the BBDB will be allowed through; all others will be
22276 classified as spammers.
22280 @defvar gnus-group-ham-exit-processor-BBDB
22282 Add this symbol to a group's @code{spam-process} parameter by
22283 customizing the group parameters or the
22284 @code{gnus-spam-process-newsgroups} variable. When this symbol is
22285 added to a group's @code{spam-process} parameter, the senders of
22286 ham-marked articles in @emph{ham} groups will be added to the
22287 BBDB. Note that this ham processor has no effect in @emph{spam}
22288 or @emph{unclassified} groups.
22293 @subsubsection Blackholes
22294 @cindex spam filtering
22295 @cindex blackholes, spam filtering
22298 @defvar spam-use-blackholes
22300 This option is disabled by default. You can let Gnus consult the
22301 blackhole-type distributed spam processing systems (DCC, for instance)
22302 when you set this option. The variable @code{spam-blackhole-servers}
22303 holds the list of blackhole servers Gnus will consult. The current
22304 list is fairly comprehensive, but make sure to let us know if it
22305 contains outdated servers.
22307 The blackhole check uses the @code{dig.el} package, but you can tell
22308 @code{spam.el} to use @code{dns.el} instead for better performance if
22309 you set @code{spam-use-dig} to nil. It is not recommended at this
22310 time to set @code{spam-use-dig} to nil despite the possible
22311 performance improvements, because some users may be unable to use it,
22312 but you can try it and see if it works for you.
22316 @defvar spam-blackhole-servers
22318 The list of servers to consult for blackhole checks.
22322 @defvar spam-blackhole-good-server-regex
22324 A regular expression for IPs that should not be checked against the
22325 blackhole server list. When set to nil, it has no effect.
22329 @defvar spam-use-dig
22331 Use the @code{dig.el} package instead of the @code{dns.el} package.
22332 The default setting of @code{t} is recommended.
22336 Blackhole checks are done only on incoming mail. There is no spam or
22337 ham processor for blackholes.
22339 @node Regular Expressions Header Matching
22340 @subsubsection Regular Expressions Header Matching
22341 @cindex spam filtering
22342 @cindex regular expressions header matching, spam filtering
22345 @defvar spam-use-regex-headers
22347 This option is disabled by default. You can let Gnus check the
22348 message headers against lists of regular expressions when you set this
22349 option. The variables @code{spam-regex-headers-spam} and
22350 @code{spam-regex-headers-ham} hold the list of regular expressions.
22351 Gnus will check against the message headers to determine if the
22352 message is spam or ham, respectively.
22356 @defvar spam-regex-headers-spam
22358 The list of regular expressions that, when matched in the headers of
22359 the message, positively identify it as spam.
22363 @defvar spam-regex-headers-ham
22365 The list of regular expressions that, when matched in the headers of
22366 the message, positively identify it as ham.
22370 Regular expression header checks are done only on incoming mail.
22371 There is no specific spam or ham processor for regular expressions.
22374 @subsubsection Bogofilter
22375 @cindex spam filtering
22376 @cindex bogofilter, spam filtering
22379 @defvar spam-use-bogofilter
22381 Set this variable if you want @code{spam-split} to use Eric Raymond's
22384 With a minimum of care for associating the @samp{$} mark for spam
22385 articles only, Bogofilter training all gets fairly automatic. You
22386 should do this until you get a few hundreds of articles in each
22387 category, spam or not. The command @kbd{S t} in summary mode, either
22388 for debugging or for curiosity, shows the @emph{spamicity} score of
22389 the current article (between 0.0 and 1.0).
22391 Bogofilter determines if a message is spam based on an internal
22392 threshold, set at compilation time. That threshold can't be
22395 If the @code{bogofilter} executable is not in your path, Bogofilter
22396 processing will be turned off.
22398 You should not enable this if you use @code{spam-use-bogofilter-headers}.
22402 @defvar spam-use-bogofilter-headers
22404 Set this variable if you want @code{spam-split} to use Eric Raymond's
22405 speedy Bogofilter, looking only at the message headers. It works
22406 similarly to @code{spam-use-bogofilter}, but the @code{X-Bogosity} header
22407 must be in the message already. Normally you would do this with a
22408 procmail recipe or something similar; consult the Bogofilter
22409 installation documents for details.
22411 You should not enable this if you use @code{spam-use-bogofilter}.
22415 @defvar gnus-group-spam-exit-processor-bogofilter
22416 Add this symbol to a group's @code{spam-process} parameter by
22417 customizing the group parameters or the
22418 @code{gnus-spam-process-newsgroups} variable. When this symbol is
22419 added to a group's @code{spam-process} parameter, spam-marked articles
22420 will be added to the Bogofilter spam database.
22423 @defvar gnus-group-ham-exit-processor-bogofilter
22424 Add this symbol to a group's @code{spam-process} parameter by
22425 customizing the group parameters or the
22426 @code{gnus-spam-process-newsgroups} variable. When this symbol is
22427 added to a group's @code{spam-process} parameter, the ham-marked
22428 articles in @emph{ham} groups will be added to the Bogofilter database
22429 of non-spam messages. Note that this ham processor has no effect in
22430 @emph{spam} or @emph{unclassified} groups.
22433 @defvar spam-bogofilter-database-directory
22435 This is the directory where Bogofilter will store its databases. It
22436 is not specified by default, so Bogofilter will use its own default
22437 database directory.
22441 The Bogofilter mail classifier is similar to ifile in intent and
22442 purpose. A ham and a spam processor are provided, plus the
22443 @code{spam-use-bogofilter} and @code{spam-use-bogofilter-headers}
22444 variables to indicate to spam-split that Bogofilter should either be
22445 used, or has already been used on the article. The 0.9.2.1 version of
22446 Bogofilter was used to test this functionality.
22448 @node ifile spam filtering
22449 @subsubsection ifile spam filtering
22450 @cindex spam filtering
22451 @cindex ifile, spam filtering
22454 @defvar spam-use-ifile
22456 Enable this variable if you want @code{spam-split} to use ifile, a
22457 statistical analyzer similar to Bogofilter.
22461 @defvar spam-ifile-all-categories
22463 Enable this variable if you want @code{spam-use-ifile} to give you all
22464 the ifile categories, not just spam/non-spam. If you use this, make
22465 sure you train ifile as described in its documentation.
22469 @defvar spam-ifile-spam-category
22471 This is the category of spam messages as far as ifile is concerned.
22472 The actual string used is irrelevant, but you probably want to leave
22473 the default value of @samp{spam}.
22476 @defvar spam-ifile-database-path
22478 This is the filename for the ifile database. It is not specified by
22479 default, so ifile will use its own default database name.
22483 The ifile mail classifier is similar to Bogofilter in intent and
22484 purpose. A ham and a spam processor are provided, plus the
22485 @code{spam-use-ifile} variable to indicate to spam-split that ifile
22486 should be used. The 1.2.1 version of ifile was used to test this
22489 @node spam-stat spam filtering
22490 @subsubsection spam-stat spam filtering
22491 @cindex spam filtering
22492 @cindex spam-stat, spam filtering
22496 @xref{Filtering Spam Using Statistics with spam-stat}.
22498 @defvar spam-use-stat
22500 Enable this variable if you want @code{spam-split} to use
22501 spam-stat.el, an Emacs Lisp statistical analyzer.
22505 @defvar gnus-group-spam-exit-processor-stat
22506 Add this symbol to a group's @code{spam-process} parameter by
22507 customizing the group parameters or the
22508 @code{gnus-spam-process-newsgroups} variable. When this symbol is
22509 added to a group's @code{spam-process} parameter, the spam-marked
22510 articles will be added to the spam-stat database of spam messages.
22513 @defvar gnus-group-ham-exit-processor-stat
22514 Add this symbol to a group's @code{spam-process} parameter by
22515 customizing the group parameters or the
22516 @code{gnus-spam-process-newsgroups} variable. When this symbol is
22517 added to a group's @code{spam-process} parameter, the ham-marked
22518 articles in @emph{ham} groups will be added to the spam-stat database
22519 of non-spam messages. Note that this ham processor has no effect in
22520 @emph{spam} or @emph{unclassified} groups.
22523 This enables spam.el to cooperate with spam-stat.el. spam-stat.el
22524 provides an internal (Lisp-only) spam database, which unlike ifile or
22525 Bogofilter does not require external programs. A spam and a ham
22526 processor, and the @code{spam-use-stat} variable for @code{spam-split}
22529 @node Extending the spam elisp package
22530 @subsubsection Extending the spam elisp package
22531 @cindex spam filtering
22532 @cindex spam elisp package, extending
22533 @cindex extending the spam elisp package
22535 Say you want to add a new back end called blackbox. For filtering
22536 incoming mail, provide the following:
22544 (defvar spam-use-blackbox nil
22545 "True if blackbox should be used.")
22550 (spam-use-blackbox . spam-check-blackbox)
22552 to @code{spam-list-of-checks}.
22557 Write the @code{spam-check-blackbox} function. It should return
22558 @samp{nil} or @code{spam-split-group}. See the existing
22559 @code{spam-check-*} functions for examples of what you can do.
22561 Make sure to add @code{spam-use-blackbox} to
22562 @code{spam-list-of-statistical-checks} if Blackbox is a statistical
22563 mail analyzer that needs the full message body to operate.
22567 For processing spam and ham messages, provide the following:
22574 Note you don't have to provide a spam or a ham processor. Only
22575 provide them if Blackbox supports spam or ham processing.
22578 (defvar gnus-group-spam-exit-processor-blackbox "blackbox"
22579 "The Blackbox summary exit spam processor.
22580 Only applicable to spam groups.")
22582 (defvar gnus-group-ham-exit-processor-blackbox "blackbox"
22583 "The whitelist summary exit ham processor.
22584 Only applicable to non-spam (unclassified and ham) groups.")
22592 (defun spam-blackbox-register-spam-routine ()
22593 (spam-generic-register-routine
22594 ;; the spam function
22596 (let ((from (spam-fetch-field-from-fast article)))
22597 (when (stringp from)
22598 (blackbox-do-something-with-this-spammer from))))
22599 ;; the ham function
22602 (defun spam-blackbox-register-ham-routine ()
22603 (spam-generic-register-routine
22604 ;; the spam function
22606 ;; the ham function
22608 (let ((from (spam-fetch-field-from-fast article)))
22609 (when (stringp from)
22610 (blackbox-do-something-with-this-ham-sender from))))))
22613 Write the @code{blackbox-do-something-with-this-ham-sender} and
22614 @code{blackbox-do-something-with-this-spammer} functions. You can add
22615 more complex code than fetching the message sender, but keep in mind
22616 that retrieving the whole message takes significantly longer than the
22617 sender through @code{spam-fetch-field-from-fast}, because the message
22618 senders are kept in memory by Gnus.
22623 @node Filtering Spam Using Statistics with spam-stat
22624 @subsection Filtering Spam Using Statistics with spam-stat
22625 @cindex Paul Graham
22626 @cindex Graham, Paul
22627 @cindex naive Bayesian spam filtering
22628 @cindex Bayesian spam filtering, naive
22629 @cindex spam filtering, naive Bayesian
22631 Paul Graham has written an excellent essay about spam filtering using
22632 statistics: @uref{http://www.paulgraham.com/spam.html,A Plan for
22633 Spam}. In it he describes the inherent deficiency of rule-based
22634 filtering as used by SpamAssassin, for example: Somebody has to write
22635 the rules, and everybody else has to install these rules. You are
22636 always late. It would be much better, he argues, to filter mail based
22637 on whether it somehow resembles spam or non-spam. One way to measure
22638 this is word distribution. He then goes on to describe a solution
22639 that checks whether a new mail resembles any of your other spam mails
22642 The basic idea is this: Create a two collections of your mail, one
22643 with spam, one with non-spam. Count how often each word appears in
22644 either collection, weight this by the total number of mails in the
22645 collections, and store this information in a dictionary. For every
22646 word in a new mail, determine its probability to belong to a spam or a
22647 non-spam mail. Use the 15 most conspicuous words, compute the total
22648 probability of the mail being spam. If this probability is higher
22649 than a certain threshold, the mail is considered to be spam.
22651 Gnus supports this kind of filtering. But it needs some setting up.
22652 First, you need two collections of your mail, one with spam, one with
22653 non-spam. Then you need to create a dictionary using these two
22654 collections, and save it. And last but not least, you need to use
22655 this dictionary in your fancy mail splitting rules.
22658 * Creating a spam-stat dictionary::
22659 * Splitting mail using spam-stat::
22660 * Low-level interface to the spam-stat dictionary::
22663 @node Creating a spam-stat dictionary
22664 @subsubsection Creating a spam-stat dictionary
22666 Before you can begin to filter spam based on statistics, you must
22667 create these statistics based on two mail collections, one with spam,
22668 one with non-spam. These statistics are then stored in a dictionary
22669 for later use. In order for these statistics to be meaningful, you
22670 need several hundred emails in both collections.
22672 Gnus currently supports only the nnml back end for automated dictionary
22673 creation. The nnml back end stores all mails in a directory, one file
22674 per mail. Use the following:
22676 @defun spam-stat-process-spam-directory
22677 Create spam statistics for every file in this directory. Every file
22678 is treated as one spam mail.
22681 @defun spam-stat-process-non-spam-directory
22682 Create non-spam statistics for every file in this directory. Every
22683 file is treated as one non-spam mail.
22686 Usually you would call @code{spam-stat-process-spam-directory} on a
22687 directory such as @file{~/Mail/mail/spam} (this usually corresponds
22688 the the group @samp{nnml:mail.spam}), and you would call
22689 @code{spam-stat-process-non-spam-directory} on a directory such as
22690 @file{~/Mail/mail/misc} (this usually corresponds the the group
22691 @samp{nnml:mail.misc}).
22693 When you are using IMAP, you won't have the mails available locally,
22694 so that will not work. One solution is to use the Gnus Agent to cache
22695 the articles. Then you can use directories such as
22696 @file{"~/News/agent/nnimap/mail.yourisp.com/personal_spam"} for
22697 @code{spam-stat-process-spam-directory}. @xref{Agent as Cache}.
22700 This variable holds the hash-table with all the statistics -- the
22701 dictionary we have been talking about. For every word in either
22702 collection, this hash-table stores a vector describing how often the
22703 word appeared in spam and often it appeared in non-spam mails.
22706 If you want to regenerate the statistics from scratch, you need to
22707 reset the dictionary.
22709 @defun spam-stat-reset
22710 Reset the @code{spam-stat} hash-table, deleting all the statistics.
22713 When you are done, you must save the dictionary. The dictionary may
22714 be rather large. If you will not update the dictionary incrementally
22715 (instead, you will recreate it once a month, for example), then you
22716 can reduce the size of the dictionary by deleting all words that did
22717 not appear often enough or that do not clearly belong to only spam or
22718 only non-spam mails.
22720 @defun spam-stat-reduce-size
22721 Reduce the size of the dictionary. Use this only if you do not want
22722 to update the dictionary incrementally.
22725 @defun spam-stat-save
22726 Save the dictionary.
22729 @defvar spam-stat-file
22730 The filename used to store the dictionary. This defaults to
22731 @file{~/.spam-stat.el}.
22734 @node Splitting mail using spam-stat
22735 @subsubsection Splitting mail using spam-stat
22737 In order to use @code{spam-stat} to split your mail, you need to add the
22738 following to your @file{~/.gnus.el} file:
22741 (require 'spam-stat)
22745 This will load the necessary Gnus code, and the dictionary you
22748 Next, you need to adapt your fancy splitting rules: You need to
22749 determine how to use @code{spam-stat}. The following examples are for
22750 the nnml back end. Using the nnimap back end works just as well. Just
22751 use @code{nnimap-split-fancy} instead of @code{nnmail-split-fancy}.
22753 In the simplest case, you only have two groups, @samp{mail.misc} and
22754 @samp{mail.spam}. The following expression says that mail is either
22755 spam or it should go into @samp{mail.misc}. If it is spam, then
22756 @code{spam-stat-split-fancy} will return @samp{mail.spam}.
22759 (setq nnmail-split-fancy
22760 `(| (: spam-stat-split-fancy)
22764 @defvar spam-stat-split-fancy-spam-group
22765 The group to use for spam. Default is @samp{mail.spam}.
22768 If you also filter mail with specific subjects into other groups, use
22769 the following expression. Only mails not matching the regular
22770 expression are considered potential spam.
22773 (setq nnmail-split-fancy
22774 `(| ("Subject" "\\bspam-stat\\b" "mail.emacs")
22775 (: spam-stat-split-fancy)
22779 If you want to filter for spam first, then you must be careful when
22780 creating the dictionary. Note that @code{spam-stat-split-fancy} must
22781 consider both mails in @samp{mail.emacs} and in @samp{mail.misc} as
22782 non-spam, therefore both should be in your collection of non-spam
22783 mails, when creating the dictionary!
22786 (setq nnmail-split-fancy
22787 `(| (: spam-stat-split-fancy)
22788 ("Subject" "\\bspam-stat\\b" "mail.emacs")
22792 You can combine this with traditional filtering. Here, we move all
22793 HTML-only mails into the @samp{mail.spam.filtered} group. Note that since
22794 @code{spam-stat-split-fancy} will never see them, the mails in
22795 @samp{mail.spam.filtered} should be neither in your collection of spam mails,
22796 nor in your collection of non-spam mails, when creating the
22800 (setq nnmail-split-fancy
22801 `(| ("Content-Type" "text/html" "mail.spam.filtered")
22802 (: spam-stat-split-fancy)
22803 ("Subject" "\\bspam-stat\\b" "mail.emacs")
22808 @node Low-level interface to the spam-stat dictionary
22809 @subsubsection Low-level interface to the spam-stat dictionary
22811 The main interface to using @code{spam-stat}, are the following functions:
22813 @defun spam-stat-buffer-is-spam
22814 Called in a buffer, that buffer is considered to be a new spam mail.
22815 Use this for new mail that has not been processed before.
22818 @defun spam-stat-buffer-is-no-spam
22819 Called in a buffer, that buffer is considered to be a new non-spam
22820 mail. Use this for new mail that has not been processed before.
22823 @defun spam-stat-buffer-change-to-spam
22824 Called in a buffer, that buffer is no longer considered to be normal
22825 mail but spam. Use this to change the status of a mail that has
22826 already been processed as non-spam.
22829 @defun spam-stat-buffer-change-to-non-spam
22830 Called in a buffer, that buffer is no longer considered to be spam but
22831 normal mail. Use this to change the status of a mail that has already
22832 been processed as spam.
22835 @defun spam-stat-save
22836 Save the hash table to the file. The filename used is stored in the
22837 variable @code{spam-stat-file}.
22840 @defun spam-stat-load
22841 Load the hash table from a file. The filename used is stored in the
22842 variable @code{spam-stat-file}.
22845 @defun spam-stat-score-word
22846 Return the spam score for a word.
22849 @defun spam-stat-score-buffer
22850 Return the spam score for a buffer.
22853 @defun spam-stat-split-fancy
22854 Use this function for fancy mail splitting. Add the rule @samp{(:
22855 spam-stat-split-fancy)} to @code{nnmail-split-fancy}
22858 Make sure you load the dictionary before using it. This requires the
22859 following in your @file{~/.gnus.el} file:
22862 (require 'spam-stat)
22866 Typical test will involve calls to the following functions:
22869 Reset: (setq spam-stat (make-hash-table :test 'equal))
22870 Learn spam: (spam-stat-process-spam-directory "~/Mail/mail/spam")
22871 Learn non-spam: (spam-stat-process-non-spam-directory "~/Mail/mail/misc")
22872 Save table: (spam-stat-save)
22873 File size: (nth 7 (file-attributes spam-stat-file))
22874 Number of words: (hash-table-count spam-stat)
22875 Test spam: (spam-stat-test-directory "~/Mail/mail/spam")
22876 Test non-spam: (spam-stat-test-directory "~/Mail/mail/misc")
22877 Reduce table size: (spam-stat-reduce-size)
22878 Save table: (spam-stat-save)
22879 File size: (nth 7 (file-attributes spam-stat-file))
22880 Number of words: (hash-table-count spam-stat)
22881 Test spam: (spam-stat-test-directory "~/Mail/mail/spam")
22882 Test non-spam: (spam-stat-test-directory "~/Mail/mail/misc")
22885 Here is how you would create your dictionary:
22888 Reset: (setq spam-stat (make-hash-table :test 'equal))
22889 Learn spam: (spam-stat-process-spam-directory "~/Mail/mail/spam")
22890 Learn non-spam: (spam-stat-process-non-spam-directory "~/Mail/mail/misc")
22891 Repeat for any other non-spam group you need...
22892 Reduce table size: (spam-stat-reduce-size)
22893 Save table: (spam-stat-save)
22896 @node Various Various
22897 @section Various Various
22903 @item gnus-home-directory
22904 @vindex gnus-home-directory
22905 All Gnus file and directory variables will be initialized from this
22906 variable, which defaults to @file{~/}.
22908 @item gnus-directory
22909 @vindex gnus-directory
22910 Most Gnus storage file and directory variables will be initialized from
22911 this variable, which defaults to the @samp{SAVEDIR} environment
22912 variable, or @file{~/News/} if that variable isn't set.
22914 Note that Gnus is mostly loaded when the @file{~/.gnus.el} file is read.
22915 This means that other directory variables that are initialized from this
22916 variable won't be set properly if you set this variable in
22917 @file{~/.gnus.el}. Set this variable in @file{.emacs} instead.
22919 @item gnus-default-directory
22920 @vindex gnus-default-directory
22921 Not related to the above variable at all---this variable says what the
22922 default directory of all Gnus buffers should be. If you issue commands
22923 like @kbd{C-x C-f}, the prompt you'll get starts in the current buffer's
22924 default directory. If this variable is @code{nil} (which is the
22925 default), the default directory will be the default directory of the
22926 buffer you were in when you started Gnus.
22929 @vindex gnus-verbose
22930 This variable is an integer between zero and ten. The higher the value,
22931 the more messages will be displayed. If this variable is zero, Gnus
22932 will never flash any messages, if it is seven (which is the default),
22933 most important messages will be shown, and if it is ten, Gnus won't ever
22934 shut up, but will flash so many messages it will make your head swim.
22936 @item gnus-verbose-backends
22937 @vindex gnus-verbose-backends
22938 This variable works the same way as @code{gnus-verbose}, but it applies
22939 to the Gnus back ends instead of Gnus proper.
22941 @item nnheader-max-head-length
22942 @vindex nnheader-max-head-length
22943 When the back ends read straight heads of articles, they all try to read
22944 as little as possible. This variable (default 4096) specifies
22945 the absolute max length the back ends will try to read before giving up
22946 on finding a separator line between the head and the body. If this
22947 variable is @code{nil}, there is no upper read bound. If it is
22948 @code{t}, the back ends won't try to read the articles piece by piece,
22949 but read the entire articles. This makes sense with some versions of
22950 @code{ange-ftp} or @code{efs}.
22952 @item nnheader-head-chop-length
22953 @vindex nnheader-head-chop-length
22954 This variable (default 2048) says how big a piece of each article to
22955 read when doing the operation described above.
22957 @item nnheader-file-name-translation-alist
22958 @vindex nnheader-file-name-translation-alist
22960 @cindex invalid characters in file names
22961 @cindex characters in file names
22962 This is an alist that says how to translate characters in file names.
22963 For instance, if @samp{:} is invalid as a file character in file names
22964 on your system (you OS/2 user you), you could say something like:
22967 (setq nnheader-file-name-translation-alist
22971 In fact, this is the default value for this variable on OS/2 and MS
22972 Windows (phooey) systems.
22974 @item gnus-hidden-properties
22975 @vindex gnus-hidden-properties
22976 This is a list of properties to use to hide ``invisible'' text. It is
22977 @code{(invisible t intangible t)} by default on most systems, which
22978 makes invisible text invisible and intangible.
22980 @item gnus-parse-headers-hook
22981 @vindex gnus-parse-headers-hook
22982 A hook called before parsing headers. It can be used, for instance, to
22983 gather statistics on the headers fetched, or perhaps you'd like to prune
22984 some headers. I don't see why you'd want that, though.
22986 @item gnus-shell-command-separator
22987 @vindex gnus-shell-command-separator
22988 String used to separate two shell commands. The default is @samp{;}.
22990 @item gnus-invalid-group-regexp
22991 @vindex gnus-invalid-group-regexp
22993 Regexp to match ``invalid'' group names when querying user for a group
22994 name. The default value catches some @strong{really} invalid group
22995 names who could possibly mess up Gnus internally (like allowing
22996 @samp{:} in a group name, which is normally used to delimit method and
22999 @sc{imap} users might want to allow @samp{/} in group names though.
23007 Well, that's the manual---you can get on with your life now. Keep in
23008 touch. Say hello to your cats from me.
23010 My @strong{ghod}---I just can't stand goodbyes. Sniffle.
23012 Ol' Charles Reznikoff said it pretty well, so I leave the floor to him:
23018 Not because of victories @*
23021 but for the common sunshine,@*
23023 the largess of the spring.
23027 but for the day's work done@*
23028 as well as I was able;@*
23029 not for a seat upon the dais@*
23030 but at the common table.@*
23035 @chapter Appendices
23038 * XEmacs:: Requirements for installing under XEmacs.
23039 * History:: How Gnus got where it is today.
23040 * On Writing Manuals:: Why this is not a beginner's guide.
23041 * Terminology:: We use really difficult, like, words here.
23042 * Customization:: Tailoring Gnus to your needs.
23043 * Troubleshooting:: What you might try if things do not work.
23044 * Gnus Reference Guide:: Rilly, rilly technical stuff.
23045 * Emacs for Heathens:: A short introduction to Emacsian terms.
23046 * Frequently Asked Questions::
23053 @cindex Installing under XEmacs
23055 XEmacs is distributed as a collection of packages. You should install
23056 whatever packages the Gnus XEmacs package requires. The current
23057 requirements are @samp{gnus}, @samp{w3}, @samp{mh-e},
23058 @samp{mailcrypt}, @samp{rmail}, @samp{eterm}, @samp{mail-lib},
23059 @samp{xemacs-base}, @samp{sh-script} and @samp{fsf-compat}. The
23060 @samp{misc-games} package is required for Morse decoding.
23067 @sc{gnus} was written by Masanobu @sc{Umeda}. When autumn crept up in
23068 '94, Lars Magne Ingebrigtsen grew bored and decided to rewrite Gnus.
23070 If you want to investigate the person responsible for this outrage,
23071 you can point your (feh!) web browser to
23072 @uref{http://quimby.gnus.org/}. This is also the primary
23073 distribution point for the new and spiffy versions of Gnus, and is
23074 known as The Site That Destroys Newsrcs And Drives People Mad.
23076 During the first extended alpha period of development, the new Gnus was
23077 called ``(ding) Gnus''. @dfn{(ding)} is, of course, short for
23078 @dfn{ding is not Gnus}, which is a total and utter lie, but who cares?
23079 (Besides, the ``Gnus'' in this abbreviation should probably be
23080 pronounced ``news'' as @sc{Umeda} intended, which makes it a more
23081 appropriate name, don't you think?)
23083 In any case, after spending all that energy on coming up with a new and
23084 spunky name, we decided that the name was @emph{too} spunky, so we
23085 renamed it back again to ``Gnus''. But in mixed case. ``Gnus'' vs.
23086 ``@sc{gnus}''. New vs. old.
23089 * Gnus Versions:: What Gnus versions have been released.
23090 * Other Gnus Versions:: Other Gnus versions that also have been released.
23091 * Why?:: What's the point of Gnus?
23092 * Compatibility:: Just how compatible is Gnus with @sc{gnus}?
23093 * Conformity:: Gnus tries to conform to all standards.
23094 * Emacsen:: Gnus can be run on a few modern Emacsen.
23095 * Gnus Development:: How Gnus is developed.
23096 * Contributors:: Oodles of people.
23097 * New Features:: Pointers to some of the new stuff in Gnus.
23101 @node Gnus Versions
23102 @subsection Gnus Versions
23104 @cindex September Gnus
23106 @cindex Quassia Gnus
23107 @cindex Pterodactyl Gnus
23110 @cindex Gnus versions
23112 The first ``proper'' release of Gnus 5 was done in November 1995 when it
23113 was included in the Emacs 19.30 distribution (132 (ding) Gnus releases
23114 plus 15 Gnus 5.0 releases).
23116 In May 1996 the next Gnus generation (aka. ``September Gnus'' (after 99
23117 releases)) was released under the name ``Gnus 5.2'' (40 releases).
23119 On July 28th 1996 work on Red Gnus was begun, and it was released on
23120 January 25th 1997 (after 84 releases) as ``Gnus 5.4'' (67 releases).
23122 On September 13th 1997, Quassia Gnus was started and lasted 37 releases.
23123 If was released as ``Gnus 5.6'' on March 8th 1998 (46 releases).
23125 Gnus 5.6 begat Pterodactyl Gnus on August 29th 1998 and was released as
23126 ``Gnus 5.8'' (after 99 releases and a CVS repository) on December 3rd
23129 On the 26th of October 2000, Oort Gnus was begun.
23131 If you happen upon a version of Gnus that has a prefixed name --
23132 ``(ding) Gnus'', ``September Gnus'', ``Red Gnus'', ``Quassia Gnus'',
23133 ``Pterodactyl Gnus'', ``Oort Gnus'' -- don't panic. Don't let it know
23134 that you're frightened. Back away. Slowly. Whatever you do, don't
23135 run. Walk away, calmly, until you're out of its reach. Find a proper
23136 released version of Gnus and snuggle up to that instead.
23139 @node Other Gnus Versions
23140 @subsection Other Gnus Versions
23143 In addition to the versions of Gnus which have had their releases
23144 coordinated by Lars, one major development has been Semi-gnus from
23145 Japan. It's based on a library called @sc{semi}, which provides
23146 @sc{mime} capabilities.
23148 These Gnusae are based mainly on Gnus 5.6 and Pterodactyl Gnus.
23149 Collectively, they are called ``Semi-gnus'', and different strains are
23150 called T-gnus, ET-gnus, Nana-gnus and Chaos. These provide powerful
23151 @sc{mime} and multilingualization things, especially important for
23158 What's the point of Gnus?
23160 I want to provide a ``rad'', ``happening'', ``way cool'' and ``hep''
23161 newsreader, that lets you do anything you can think of. That was my
23162 original motivation, but while working on Gnus, it has become clear to
23163 me that this generation of newsreaders really belong in the stone age.
23164 Newsreaders haven't developed much since the infancy of the net. If the
23165 volume continues to rise with the current rate of increase, all current
23166 newsreaders will be pretty much useless. How do you deal with
23167 newsgroups that have thousands of new articles each day? How do you
23168 keep track of millions of people who post?
23170 Gnus offers no real solutions to these questions, but I would very much
23171 like to see Gnus being used as a testing ground for new methods of
23172 reading and fetching news. Expanding on @sc{Umeda}-san's wise decision
23173 to separate the newsreader from the back ends, Gnus now offers a simple
23174 interface for anybody who wants to write new back ends for fetching mail
23175 and news from different sources. I have added hooks for customizations
23176 everywhere I could imagine it being useful. By doing so, I'm inviting
23177 every one of you to explore and invent.
23179 May Gnus never be complete. @kbd{C-u 100 M-x all-hail-emacs} and
23180 @kbd{C-u 100 M-x all-hail-xemacs}.
23183 @node Compatibility
23184 @subsection Compatibility
23186 @cindex compatibility
23187 Gnus was designed to be fully compatible with @sc{gnus}. Almost all key
23188 bindings have been kept. More key bindings have been added, of course,
23189 but only in one or two obscure cases have old bindings been changed.
23194 @center In a cloud bones of steel.
23198 All commands have kept their names. Some internal functions have changed
23201 The @code{gnus-uu} package has changed drastically. @xref{Decoding
23204 One major compatibility question is the presence of several summary
23205 buffers. All variables relevant while reading a group are
23206 buffer-local to the summary buffer they belong in. Although many
23207 important variables have their values copied into their global
23208 counterparts whenever a command is executed in the summary buffer, this
23209 change might lead to incorrect values being used unless you are careful.
23211 All code that relies on knowledge of @sc{gnus} internals will probably
23212 fail. To take two examples: Sorting @code{gnus-newsrc-alist} (or
23213 changing it in any way, as a matter of fact) is strictly verboten. Gnus
23214 maintains a hash table that points to the entries in this alist (which
23215 speeds up many functions), and changing the alist directly will lead to
23219 @cindex highlighting
23220 Old hilit19 code does not work at all. In fact, you should probably
23221 remove all hilit code from all Gnus hooks
23222 (@code{gnus-group-prepare-hook} and @code{gnus-summary-prepare-hook}).
23223 Gnus provides various integrated functions for highlighting. These are
23224 faster and more accurate. To make life easier for everybody, Gnus will
23225 by default remove all hilit calls from all hilit hooks. Uncleanliness!
23228 Packages like @code{expire-kill} will no longer work. As a matter of
23229 fact, you should probably remove all old @sc{gnus} packages (and other
23230 code) when you start using Gnus. More likely than not, Gnus already
23231 does what you have written code to make @sc{gnus} do. (Snicker.)
23233 Even though old methods of doing things are still supported, only the
23234 new methods are documented in this manual. If you detect a new method of
23235 doing something while reading this manual, that does not mean you have
23236 to stop doing it the old way.
23238 Gnus understands all @sc{gnus} startup files.
23240 @kindex M-x gnus-bug
23242 @cindex reporting bugs
23244 Overall, a casual user who hasn't written much code that depends on
23245 @sc{gnus} internals should suffer no problems. If problems occur,
23246 please let me know by issuing that magic command @kbd{M-x gnus-bug}.
23248 @vindex gnus-bug-create-help-buffer
23249 If you are in the habit of sending bug reports @emph{very} often, you
23250 may find the helpful help buffer annoying after a while. If so, set
23251 @code{gnus-bug-create-help-buffer} to @code{nil} to avoid having it pop
23256 @subsection Conformity
23258 No rebels without a clue here, ma'am. We conform to all standards known
23259 to (wo)man. Except for those standards and/or conventions we disagree
23267 There are no known breaches of this standard.
23271 There are no known breaches of this standard, either.
23273 @item Son-of-RFC 1036
23274 @cindex Son-of-RFC 1036
23275 We do have some breaches to this one.
23281 These are considered to be ``vanity headers'', while I consider them
23282 to be consumer information. After seeing so many badly formatted
23283 articles coming from @code{tin} and @code{Netscape} I know not to use
23284 either of those for posting articles. I would not have known that if
23285 it wasn't for the @code{X-Newsreader} header.
23290 USEFOR is an IETF working group writing a successor to RFC 1036, based
23291 on Son-of-RFC 1036. They have produced a number of drafts proposing
23292 various changes to the format of news articles. The Gnus towers will
23293 look into implementing the changes when the draft is accepted as an RFC.
23295 @item MIME - RFC 2045-2049 etc
23297 All the various @sc{mime} RFCs are supported.
23299 @item Disposition Notifications - RFC 2298
23300 Message Mode is able to request notifications from the receiver.
23302 @item PGP - RFC 1991 and RFC 2440
23305 RFC 1991 is the original PGP message specification, published as a
23306 Information RFC. RFC 2440 was the follow-up, now called Open PGP, and
23307 put on the Standards Track. Both document a non-@sc{mime} aware PGP
23308 format. Gnus supports both encoding (signing and encryption) and
23309 decoding (verification and decryption).
23311 @item PGP/MIME - RFC 2015/3156
23312 RFC 2015 (superseded by 3156 which references RFC 2440 instead of RFC
23313 1991) describes the @sc{mime}-wrapping around the RF 1991/2440 format.
23314 Gnus supports both encoding and decoding.
23316 @item S/MIME - RFC 2633
23317 RFC 2633 describes the @sc{s/mime} format.
23319 @item IMAP - RFC 1730/2060, RFC 2195, RFC 2086, RFC 2359, RFC 2595, RFC 1731
23320 RFC 1730 is @sc{imap} version 4, updated somewhat by RFC 2060 (@sc{imap} 4
23321 revision 1). RFC 2195 describes CRAM-MD5 authentication for @sc{imap}. RFC
23322 2086 describes access control lists (ACLs) for @sc{imap}. RFC 2359
23323 describes a @sc{imap} protocol enhancement. RFC 2595 describes the proper
23324 TLS integration (STARTTLS) with @sc{imap}. RFC 1731 describes the
23325 GSSAPI/Kerberos4 mechanisms for @sc{imap}.
23329 If you ever notice Gnus acting non-compliant with regards to the texts
23330 mentioned above, don't hesitate to drop a note to Gnus Towers and let us
23335 @subsection Emacsen
23341 Gnus should work on :
23349 XEmacs 20.4 and up.
23353 This Gnus version will absolutely not work on any Emacsen older than
23354 that. Not reliably, at least. Older versions of Gnus may work on older
23357 There are some vague differences between Gnus on the various
23358 platforms---XEmacs features more graphics (a logo and a toolbar)---but
23359 other than that, things should look pretty much the same under all
23363 @node Gnus Development
23364 @subsection Gnus Development
23366 Gnus is developed in a two-phased cycle. The first phase involves much
23367 discussion on the @samp{ding@@gnus.org} mailing list, where people
23368 propose changes and new features, post patches and new back ends. This
23369 phase is called the @dfn{alpha} phase, since the Gnusae released in this
23370 phase are @dfn{alpha releases}, or (perhaps more commonly in other
23371 circles) @dfn{snapshots}. During this phase, Gnus is assumed to be
23372 unstable and should not be used by casual users. Gnus alpha releases
23373 have names like ``Red Gnus'' and ``Quassia Gnus''.
23375 After futzing around for 50-100 alpha releases, Gnus is declared
23376 @dfn{frozen}, and only bug fixes are applied. Gnus loses the prefix,
23377 and is called things like ``Gnus 5.6.32'' instead. Normal people are
23378 supposed to be able to use these, and these are mostly discussed on the
23379 @samp{gnu.emacs.gnus} newsgroup.
23382 @vindex mail-source-delete-incoming
23383 Some variable defaults differ between alpha Gnusae and released Gnusae.
23384 In particular, @code{mail-source-delete-incoming} defaults to @code{nil} in
23385 alpha Gnusae and @code{t} in released Gnusae. This is to prevent
23386 lossage of mail if an alpha release hiccups while handling the mail.
23388 The division of discussion between the ding mailing list and the Gnus
23389 newsgroup is not purely based on publicity concerns. It's true that
23390 having people write about the horrible things that an alpha Gnus release
23391 can do (sometimes) in a public forum may scare people off, but more
23392 importantly, talking about new experimental features that have been
23393 introduced may confuse casual users. New features are frequently
23394 introduced, fiddled with, and judged to be found wanting, and then
23395 either discarded or totally rewritten. People reading the mailing list
23396 usually keep up with these rapid changes, while people on the newsgroup
23397 can't be assumed to do so.
23402 @subsection Contributors
23403 @cindex contributors
23405 The new Gnus version couldn't have been done without the help of all the
23406 people on the (ding) mailing list. Every day for over a year I have
23407 gotten billions of nice bug reports from them, filling me with joy,
23408 every single one of them. Smooches. The people on the list have been
23409 tried beyond endurance, what with my ``oh, that's a neat idea <type
23410 type>, yup, I'll release it right away <ship off> no wait, that doesn't
23411 work at all <type type>, yup, I'll ship that one off right away <ship
23412 off> no, wait, that absolutely does not work'' policy for releases.
23413 Micro$oft---bah. Amateurs. I'm @emph{much} worse. (Or is that
23414 ``worser''? ``much worser''? ``worsest''?)
23416 I would like to take this opportunity to thank the Academy for@dots{} oops,
23422 Masanobu @sc{Umeda}---the writer of the original @sc{gnus}.
23425 Shenghuo Zhu---uudecode.el, mm-uu.el, rfc1843.el, webmail.el,
23426 nnwarchive and many, many other things connected with @sc{mime} and
23427 other types of en/decoding, as well as general bug fixing, new
23428 functionality and stuff.
23431 Per Abrahamsen---custom, scoring, highlighting and @sc{soup} code (as
23432 well as numerous other things).
23435 Luis Fernandes---design and graphics.
23438 Joe Reiss---creator of the smiley faces.
23441 Justin Sheehy--the FAQ maintainer.
23444 Erik Naggum---help, ideas, support, code and stuff.
23447 Wes Hardaker---@file{gnus-picon.el} and the manual section on
23448 @dfn{picons} (@pxref{Picons}).
23451 Kim-Minh Kaplan---further work on the picon code.
23454 Brad Miller---@file{gnus-gl.el} and the GroupLens manual section
23455 (@pxref{GroupLens}).
23458 Sudish Joseph---innumerable bug fixes.
23461 Ilja Weis---@file{gnus-topic.el}.
23464 Steven L. Baur---lots and lots and lots of bugs detections and fixes.
23467 Vladimir Alexiev---the refcard and reference booklets.
23470 Felix Lee & Jamie Zawinski---I stole some pieces from the XGnus
23471 distribution by Felix Lee and JWZ.
23474 Scott Byer---@file{nnfolder.el} enhancements & rewrite.
23477 Peter Mutsaers---orphan article scoring code.
23480 Ken Raeburn---POP mail support.
23483 Hallvard B Furuseth---various bits and pieces, especially dealing with
23487 Brian Edmonds---@file{gnus-bbdb.el}.
23490 David Moore---rewrite of @file{nnvirtual.el} and many other things.
23493 Kevin Davidson---came up with the name @dfn{ding}, so blame him.
23496 François Pinard---many, many interesting and thorough bug reports, as
23497 well as autoconf support.
23501 This manual was proof-read by Adrian Aichner, with Ricardo Nassif, Mark
23502 Borges, and Jost Krieger proof-reading parts of the manual.
23504 The following people have contributed many patches and suggestions:
23519 Jason L. Tibbitts, III,
23521 Katsumi Yamaoka, @c Yamaoka
23525 Also thanks to the following for patches and stuff:
23535 Alexei V. Barantsev,
23550 Massimo Campostrini,
23555 Jae-you Chung, @c ?
23556 James H. Cloos, Jr.,
23560 Andrew J. Cosgriff,
23563 Geoffrey T. Dairiki,
23569 Michael Welsh Duggan,
23574 Enami Tsugutomo, @c Enami
23578 Nelson Jose dos Santos Ferreira,
23586 Arne Georg Gleditsch,
23588 Michelangelo Grigni,
23592 Kenichi Handa, @c Handa
23594 Yoshiki Hayashi, @c Hayashi
23596 Hisashige Kenji, @c Hisashige
23603 François Felix Ingrand,
23604 Tatsuya Ichikawa, @c Ichikawa
23605 Ishikawa Ichiro, @c Ishikawa
23607 Iwamuro Motonori, @c Iwamuro
23617 Peter Skov Knudsen,
23618 Shuhei Kobayashi, @c Kobayashi
23620 Koseki Yoshinori, @c Koseki
23621 Thor Kristoffersen,
23624 Seokchan Lee, @c Lee
23642 Morioka Tomohiko, @c Morioka
23643 Erik Toubro Nielsen,
23650 Masaharu Onishi, @c Onishi
23655 Jens-Ulrik Holger Petersen,
23659 John McClary Prevost,
23665 Lars Balker Rasmussen,
23670 Christian von Roques,
23673 Wolfgang Rupprecht,
23680 Philippe Schnoebelen,
23682 Randal L. Schwartz,
23696 Kiyokazu Suto, @c Suto
23701 Tozawa Akihiko, @c Tozawa
23721 For a full overview of what each person has done, the ChangeLogs
23722 included in the Gnus alpha distributions should give ample reading
23723 (550kB and counting).
23725 Apologies to everybody that I've forgotten, of which there are many, I'm
23728 Gee, that's quite a list of people. I guess that must mean that there
23729 actually are people who are using Gnus. Who'd'a thunk it!
23733 @subsection New Features
23734 @cindex new features
23737 * ding Gnus:: New things in Gnus 5.0/5.1, the first new Gnus.
23738 * September Gnus:: The Thing Formally Known As Gnus 5.2/5.3.
23739 * Red Gnus:: Third time best---Gnus 5.4/5.5.
23740 * Quassia Gnus:: Two times two is four, or Gnus 5.6/5.7.
23741 * Pterodactyl Gnus:: Pentad also starts with P, AKA Gnus 5.8/5.9.
23744 These lists are, of course, just @emph{short} overviews of the
23745 @emph{most} important new features. No, really. There are tons more.
23746 Yes, we have feeping creaturism in full effect.
23749 @subsubsection (ding) Gnus
23751 New features in Gnus 5.0/5.1:
23756 The look of all buffers can be changed by setting format-like variables
23757 (@pxref{Group Buffer Format} and @pxref{Summary Buffer Format}).
23760 Local spool and several @sc{nntp} servers can be used at once
23761 (@pxref{Select Methods}).
23764 You can combine groups into virtual groups (@pxref{Virtual Groups}).
23767 You can read a number of different mail formats (@pxref{Getting Mail}).
23768 All the mail back ends implement a convenient mail expiry scheme
23769 (@pxref{Expiring Mail}).
23772 Gnus can use various strategies for gathering threads that have lost
23773 their roots (thereby gathering loose sub-threads into one thread) or it
23774 can go back and retrieve enough headers to build a complete thread
23775 (@pxref{Customizing Threading}).
23778 Killed groups can be displayed in the group buffer, and you can read
23779 them as well (@pxref{Listing Groups}).
23782 Gnus can do partial group updates---you do not have to retrieve the
23783 entire active file just to check for new articles in a few groups
23784 (@pxref{The Active File}).
23787 Gnus implements a sliding scale of subscribedness to groups
23788 (@pxref{Group Levels}).
23791 You can score articles according to any number of criteria
23792 (@pxref{Scoring}). You can even get Gnus to find out how to score
23793 articles for you (@pxref{Adaptive Scoring}).
23796 Gnus maintains a dribble buffer that is auto-saved the normal Emacs
23797 manner, so it should be difficult to lose much data on what you have
23798 read if your machine should go down (@pxref{Auto Save}).
23801 Gnus now has its own startup file (@file{~/.gnus.el}) to avoid
23802 cluttering up the @file{.emacs} file.
23805 You can set the process mark on both groups and articles and perform
23806 operations on all the marked items (@pxref{Process/Prefix}).
23809 You can grep through a subset of groups and create a group from the
23810 results (@pxref{Kibozed Groups}).
23813 You can list subsets of groups according to, well, anything
23814 (@pxref{Listing Groups}).
23817 You can browse foreign servers and subscribe to groups from those
23818 servers (@pxref{Browse Foreign Server}).
23821 Gnus can fetch articles, asynchronously, on a second connection to the
23822 server (@pxref{Asynchronous Fetching}).
23825 You can cache articles locally (@pxref{Article Caching}).
23828 The uudecode functions have been expanded and generalized
23829 (@pxref{Decoding Articles}).
23832 You can still post uuencoded articles, which was a little-known feature
23833 of @sc{gnus}' past (@pxref{Uuencoding and Posting}).
23836 Fetching parents (and other articles) now actually works without
23837 glitches (@pxref{Finding the Parent}).
23840 Gnus can fetch FAQs and group descriptions (@pxref{Group Information}).
23843 Digests (and other files) can be used as the basis for groups
23844 (@pxref{Document Groups}).
23847 Articles can be highlighted and customized (@pxref{Customizing
23851 URLs and other external references can be buttonized (@pxref{Article
23855 You can do lots of strange stuff with the Gnus window & frame
23856 configuration (@pxref{Window Layout}).
23859 You can click on buttons instead of using the keyboard
23865 @node September Gnus
23866 @subsubsection September Gnus
23870 \gnusfig{-28cm}{0cm}{\epsfig{figure=ps/september,height=20cm}}
23874 New features in Gnus 5.2/5.3:
23879 A new message composition mode is used. All old customization variables
23880 for @code{mail-mode}, @code{rnews-reply-mode} and @code{gnus-msg} are
23884 Gnus is now able to generate @dfn{sparse} threads---threads where
23885 missing articles are represented by empty nodes (@pxref{Customizing
23889 (setq gnus-build-sparse-threads 'some)
23893 Outgoing articles are stored on a special archive server
23894 (@pxref{Archived Messages}).
23897 Partial thread regeneration now happens when articles are
23901 Gnus can make use of GroupLens predictions (@pxref{GroupLens}).
23904 Picons (personal icons) can be displayed under XEmacs (@pxref{Picons}).
23907 A @code{trn}-like tree buffer can be displayed (@pxref{Tree Display}).
23910 (setq gnus-use-trees t)
23914 An @code{nn}-like pick-and-read minor mode is available for the summary
23915 buffers (@pxref{Pick and Read}).
23918 (add-hook 'gnus-summary-mode-hook 'gnus-pick-mode)
23922 In binary groups you can use a special binary minor mode (@pxref{Binary
23926 Groups can be grouped in a folding topic hierarchy (@pxref{Group
23930 (add-hook 'gnus-group-mode-hook 'gnus-topic-mode)
23934 Gnus can re-send and bounce mail (@pxref{Summary Mail Commands}).
23937 Groups can now have a score, and bubbling based on entry frequency
23938 is possible (@pxref{Group Score}).
23941 (add-hook 'gnus-summary-exit-hook 'gnus-summary-bubble-group)
23945 Groups can be process-marked, and commands can be performed on
23946 groups of groups (@pxref{Marking Groups}).
23949 Caching is possible in virtual groups.
23952 @code{nndoc} now understands all kinds of digests, mail boxes, rnews
23953 news batches, ClariNet briefs collections, and just about everything
23954 else (@pxref{Document Groups}).
23957 Gnus has a new back end (@code{nnsoup}) to create/read SOUP packets
23961 The Gnus cache is much faster.
23964 Groups can be sorted according to many criteria (@pxref{Sorting
23968 New group parameters have been introduced to set list-addresses and
23969 expiry times (@pxref{Group Parameters}).
23972 All formatting specs allow specifying faces to be used
23973 (@pxref{Formatting Fonts}).
23976 There are several more commands for setting/removing/acting on process
23977 marked articles on the @kbd{M P} submap (@pxref{Setting Process Marks}).
23980 The summary buffer can be limited to show parts of the available
23981 articles based on a wide range of criteria. These commands have been
23982 bound to keys on the @kbd{/} submap (@pxref{Limiting}).
23985 Articles can be made persistent with the @kbd{*} command
23986 (@pxref{Persistent Articles}).
23989 All functions for hiding article elements are now toggles.
23992 Article headers can be buttonized (@pxref{Article Washing}).
23995 All mail back ends support fetching articles by @code{Message-ID}.
23998 Duplicate mail can now be treated properly (@pxref{Duplicates}).
24001 All summary mode commands are available directly from the article
24002 buffer (@pxref{Article Keymap}).
24005 Frames can be part of @code{gnus-buffer-configuration} (@pxref{Window
24009 Mail can be re-scanned by a daemonic process (@pxref{Daemons}).
24012 \marginpar[\mbox{}\hfill\epsfig{figure=ps/fseptember,height=5cm}]{\epsfig{figure=ps/fseptember,height=5cm}}
24017 Gnus can make use of NoCeM files to weed out spam (@pxref{NoCeM}).
24020 (setq gnus-use-nocem t)
24024 Groups can be made permanently visible (@pxref{Listing Groups}).
24027 (setq gnus-permanently-visible-groups "^nnml:")
24031 Many new hooks have been introduced to make customizing easier.
24034 Gnus respects the @code{Mail-Copies-To} header.
24037 Threads can be gathered by looking at the @code{References} header
24038 (@pxref{Customizing Threading}).
24041 (setq gnus-summary-thread-gathering-function
24042 'gnus-gather-threads-by-references)
24046 Read articles can be stored in a special backlog buffer to avoid
24047 refetching (@pxref{Article Backlog}).
24050 (setq gnus-keep-backlog 50)
24054 A clean copy of the current article is always stored in a separate
24055 buffer to allow easier treatment.
24058 Gnus can suggest where to save articles (@pxref{Saving Articles}).
24061 Gnus doesn't have to do as much prompting when saving (@pxref{Saving
24065 (setq gnus-prompt-before-saving t)
24069 @code{gnus-uu} can view decoded files asynchronously while fetching
24070 articles (@pxref{Other Decode Variables}).
24073 (setq gnus-uu-grabbed-file-functions 'gnus-uu-grab-view)
24077 Filling in the article buffer now works properly on cited text
24078 (@pxref{Article Washing}).
24081 Hiding cited text adds buttons to toggle hiding, and how much
24082 cited text to hide is now customizable (@pxref{Article Hiding}).
24085 (setq gnus-cited-lines-visible 2)
24089 Boring headers can be hidden (@pxref{Article Hiding}).
24092 Default scoring values can now be set from the menu bar.
24095 Further syntax checking of outgoing articles have been added.
24101 @subsubsection Red Gnus
24103 New features in Gnus 5.4/5.5:
24107 \gnusfig{-5.5cm}{-4cm}{\epsfig{figure=ps/red,height=20cm}}
24114 @file{nntp.el} has been totally rewritten in an asynchronous fashion.
24117 Article prefetching functionality has been moved up into
24118 Gnus (@pxref{Asynchronous Fetching}).
24121 Scoring can now be performed with logical operators like @code{and},
24122 @code{or}, @code{not}, and parent redirection (@pxref{Advanced
24126 Article washing status can be displayed in the
24127 article mode line (@pxref{Misc Article}).
24130 @file{gnus.el} has been split into many smaller files.
24133 Suppression of duplicate articles based on Message-ID can be done
24134 (@pxref{Duplicate Suppression}).
24137 (setq gnus-suppress-duplicates t)
24141 New variables for specifying what score and adapt files are to be
24142 considered home score and adapt files (@pxref{Home Score File}) have
24146 @code{nndoc} was rewritten to be easily extendable (@pxref{Document
24147 Server Internals}).
24150 Groups can inherit group parameters from parent topics (@pxref{Topic
24154 Article editing has been revamped and is now actually usable.
24157 Signatures can be recognized in more intelligent fashions
24158 (@pxref{Article Signature}).
24161 Summary pick mode has been made to look more @code{nn}-like. Line
24162 numbers are displayed and the @kbd{.} command can be used to pick
24163 articles (@code{Pick and Read}).
24166 Commands for moving the @file{.newsrc.eld} from one server to
24167 another have been added (@pxref{Changing Servers}).
24170 There's a way now to specify that ``uninteresting'' fields be suppressed
24171 when generating lines in buffers (@pxref{Advanced Formatting}).
24174 Several commands in the group buffer can be undone with @kbd{C-M-_}
24178 Scoring can be done on words using the new score type @code{w}
24179 (@pxref{Score File Format}).
24182 Adaptive scoring can be done on a Subject word-by-word basis
24183 (@pxref{Adaptive Scoring}).
24186 (setq gnus-use-adaptive-scoring '(word))
24190 Scores can be decayed (@pxref{Score Decays}).
24193 (setq gnus-decay-scores t)
24197 Scoring can be performed using a regexp on the Date header. The Date is
24198 normalized to compact ISO 8601 format first (@pxref{Score File Format}).
24201 A new command has been added to remove all data on articles from
24202 the native server (@pxref{Changing Servers}).
24205 A new command for reading collections of documents
24206 (@code{nndoc} with @code{nnvirtual} on top) has been added---@kbd{C-M-d}
24207 (@pxref{Really Various Summary Commands}).
24210 Process mark sets can be pushed and popped (@pxref{Setting Process
24214 A new mail-to-news back end makes it possible to post even when the @sc{nntp}
24215 server doesn't allow posting (@pxref{Mail-To-News Gateways}).
24218 A new back end for reading searches from Web search engines
24219 (@dfn{DejaNews}, @dfn{Alta Vista}, @dfn{InReference}) has been added
24220 (@pxref{Web Searches}).
24223 Groups inside topics can now be sorted using the standard sorting
24224 functions, and each topic can be sorted independently (@pxref{Topic
24228 Subsets of the groups can be sorted independently (@code{Sorting
24232 Cached articles can be pulled into the groups (@pxref{Summary Generation
24236 \marginpar[\mbox{}\hfill\epsfig{figure=ps/fred,width=3cm}]{\epsfig{figure=ps/fred,width=3cm}}
24241 Score files are now applied in a more reliable order (@pxref{Score
24245 Reports on where mail messages end up can be generated (@pxref{Splitting
24249 More hooks and functions have been added to remove junk from incoming
24250 mail before saving the mail (@pxref{Washing Mail}).
24253 Emphasized text can be properly fontisized:
24259 @subsubsection Quassia Gnus
24261 New features in Gnus 5.6:
24266 New functionality for using Gnus as an offline newsreader has been
24267 added. A plethora of new commands and modes have been added. See
24268 @pxref{Gnus Unplugged} for the full story.
24271 The @code{nndraft} back end has returned, but works differently than
24272 before. All Message buffers are now also articles in the @code{nndraft}
24273 group, which is created automatically.
24276 @code{gnus-alter-header-function} can now be used to alter header
24280 @code{gnus-summary-goto-article} now accept Message-ID's.
24283 A new Message command for deleting text in the body of a message
24284 outside the region: @kbd{C-c C-v}.
24287 You can now post to component group in @code{nnvirtual} groups with
24291 @code{nntp-rlogin-program}---new variable to ease customization.
24294 @code{C-u C-c C-c} in @code{gnus-article-edit-mode} will now inhibit
24295 re-highlighting of the article buffer.
24298 New element in @code{gnus-boring-article-headers}---@code{long-to}.
24301 @kbd{M-i} symbolic prefix command. See the section ``Symbolic
24302 Prefixes'' in the Gnus manual for details.
24305 @kbd{L} and @kbd{I} in the summary buffer now take the symbolic prefix
24306 @kbd{a} to add the score rule to the @file{all.SCORE} file.
24309 @code{gnus-simplify-subject-functions} variable to allow greater
24310 control over simplification.
24313 @kbd{A T}---new command for fetching the current thread.
24316 @kbd{/ T}---new command for including the current thread in the
24320 @kbd{M-RET} is a new Message command for breaking cited text.
24323 @samp{\\1}-expressions are now valid in @code{nnmail-split-methods}.
24326 The @code{custom-face-lookup} function has been removed.
24327 If you used this function in your initialization files, you must
24328 rewrite them to use @code{face-spec-set} instead.
24331 Canceling now uses the current select method. Symbolic prefix
24332 @kbd{a} forces normal posting method.
24335 New command to translate M******** sm*rtq**t*s into proper
24339 For easier debugging of @code{nntp}, you can set
24340 @code{nntp-record-commands} to a non-@code{nil} value.
24343 @code{nntp} now uses @file{~/.authinfo}, a @file{.netrc}-like file, for
24344 controlling where and how to send @sc{authinfo} to @sc{nntp} servers.
24347 A command for editing group parameters from the summary buffer
24351 A history of where mails have been split is available.
24354 A new article date command has been added---@code{article-date-iso8601}.
24357 Subjects can be simplified when threading by setting
24358 @code{gnus-score-thread-simplify}.
24361 A new function for citing in Message has been
24362 added---@code{message-cite-original-without-signature}.
24365 @code{article-strip-all-blank-lines}---new article command.
24368 A new Message command to kill to the end of the article has
24372 A minimum adaptive score can be specified by using the
24373 @code{gnus-adaptive-word-minimum} variable.
24376 The ``lapsed date'' article header can be kept continually
24377 updated by the @code{gnus-start-date-timer} command.
24380 Web listserv archives can be read with the @code{nnlistserv} back end.
24383 Old dejanews archives can now be read by @code{nnweb}.
24387 @node Pterodactyl Gnus
24388 @subsubsection Pterodactyl Gnus
24390 New features in Gnus 5.8:
24395 The mail-fetching functions have changed. See the manual for the
24396 many details. In particular, all procmail fetching variables are gone.
24398 If you used procmail like in
24401 (setq nnmail-use-procmail t)
24402 (setq nnmail-spool-file 'procmail)
24403 (setq nnmail-procmail-directory "~/mail/incoming/")
24404 (setq nnmail-procmail-suffix "\\.in")
24407 this now has changed to
24411 '((directory :path "~/mail/incoming/"
24415 More information is available in the info doc at Select Methods ->
24416 Getting Mail -> Mail Sources
24419 Gnus is now a @sc{mime}-capable reader. This affects many parts of
24420 Gnus, and adds a slew of new commands. See the manual for details.
24423 Gnus has also been multilingualized. This also affects too
24424 many parts of Gnus to summarize here, and adds many new variables.
24427 @code{gnus-auto-select-first} can now be a function to be
24428 called to position point.
24431 The user can now decide which extra headers should be included in
24432 summary buffers and @sc{nov} files.
24435 @code{gnus-article-display-hook} has been removed. Instead, a number
24436 of variables starting with @code{gnus-treat-} have been added.
24439 The Gnus posting styles have been redone again and now works in a
24440 subtly different manner.
24443 New web-based back ends have been added: @code{nnslashdot},
24444 @code{nnwarchive} and @code{nnultimate}. nnweb has been revamped,
24445 again, to keep up with ever-changing layouts.
24448 Gnus can now read @sc{imap} mail via @code{nnimap}.
24456 @section The Manual
24460 This manual was generated from a TeXinfo file and then run through
24461 either @code{texi2dvi}
24463 or my own home-brewed TeXinfo to \LaTeX\ transformer,
24464 and then run through @code{latex} and @code{dvips}
24466 to get what you hold in your hands now.
24468 The following conventions have been used:
24473 This is a @samp{string}
24476 This is a @kbd{keystroke}
24479 This is a @file{file}
24482 This is a @code{symbol}
24486 So if I were to say ``set @code{flargnoze} to @samp{yes}'', that would
24490 (setq flargnoze "yes")
24493 If I say ``set @code{flumphel} to @code{yes}'', that would mean:
24496 (setq flumphel 'yes)
24499 @samp{yes} and @code{yes} are two @emph{very} different things---don't
24500 ever get them confused.
24504 Of course, everything in this manual is of vital interest, so you should
24505 read it all. Several times. However, if you feel like skimming the
24506 manual, look for that gnu head you should see in the margin over
24507 there---it means that what's being discussed is of more importance than
24508 the rest of the stuff. (On the other hand, if everything is infinitely
24509 important, how can anything be more important than that? Just one more
24510 of the mysteries of this world, I guess.)
24516 @node On Writing Manuals
24517 @section On Writing Manuals
24519 I guess most manuals are written after-the-fact; documenting a program
24520 that's already there. This is not how this manual is written. When
24521 implementing something, I write the manual entry for that something
24522 straight away. I then see that it's difficult to explain the
24523 functionality, so I write how it's supposed to be, and then I change the
24524 implementation. Writing the documentation and writing the code goes
24527 This, of course, means that this manual has no, or little, flow. It
24528 documents absolutely everything in Gnus, but often not where you're
24529 looking for it. It is a reference manual, and not a guide to how to get
24532 That would be a totally different book, that should be written using the
24533 reference manual as source material. It would look quite differently.
24538 @section Terminology
24540 @cindex terminology
24545 This is what you are supposed to use this thing for---reading news.
24546 News is generally fetched from a nearby @sc{nntp} server, and is
24547 generally publicly available to everybody. If you post news, the entire
24548 world is likely to read just what you have written, and they'll all
24549 snigger mischievously. Behind your back.
24553 Everything that's delivered to you personally is mail. Some news/mail
24554 readers (like Gnus) blur the distinction between mail and news, but
24555 there is a difference. Mail is private. News is public. Mailing is
24556 not posting, and replying is not following up.
24560 Send a mail to the person who has written what you are reading.
24564 Post an article to the current newsgroup responding to the article you
24569 Gnus considers mail and news to be mostly the same, really. The only
24570 difference is how to access the actual articles. News articles are
24571 commonly fetched via the protocol NNTP, whereas mail messages could be
24572 read from a file on the local disk. The internal architecture of Gnus
24573 thus comprises a `front end' and a number of `back ends'. Internally,
24574 when you enter a group (by hitting @key{RET}, say), you thereby invoke
24575 a function in the front end in Gnus. The front end then `talks' to a
24576 back end and says things like ``Give me the list of articles in the foo
24577 group'' or ``Show me article number 4711''.
24579 So a back end mainly defines either a protocol (the @code{nntp} back end
24580 accesses news via NNTP, the @code{nnimap} back end accesses mail via
24581 IMAP) or a file format and directory layout (the @code{nnspool} back end
24582 accesses news via the common `spool directory' format, the @code{nnml}
24583 back end access mail via a file format and directory layout that's
24586 Gnus does not handle the underlying media, so to speak---this is all
24587 done by the back ends. A back end is a collection of functions to
24588 access the articles.
24590 However, sometimes the term `back end' is also used where `server'
24591 would have been more appropriate. And then there is the term `select
24592 method' which can mean either. The Gnus terminology can be quite
24597 Gnus will always use one method (and back end) as the @dfn{native}, or
24598 default, way of getting news.
24602 You can also have any number of foreign groups active at the same time.
24603 These are groups that use non-native non-secondary back ends for getting
24608 Secondary back ends are somewhere half-way between being native and being
24609 foreign, but they mostly act like they are native.
24613 A message that has been posted as news.
24616 @cindex mail message
24617 A message that has been mailed.
24621 A mail message or news article
24625 The top part of a message, where administrative information (etc.) is
24630 The rest of an article. Everything not in the head is in the
24635 A line from the head of an article.
24639 A collection of such lines, or a collection of heads. Or even a
24640 collection of @sc{nov} lines.
24644 When Gnus enters a group, it asks the back end for the headers of all
24645 unread articles in the group. Most servers support the News OverView
24646 format, which is more compact and much faster to read and parse than the
24647 normal @sc{head} format.
24651 Each group is subscribed at some @dfn{level} or other (1-9). The ones
24652 that have a lower level are ``more'' subscribed than the groups with a
24653 higher level. In fact, groups on levels 1-5 are considered
24654 @dfn{subscribed}; 6-7 are @dfn{unsubscribed}; 8 are @dfn{zombies}; and 9
24655 are @dfn{killed}. Commands for listing groups and scanning for new
24656 articles will all use the numeric prefix as @dfn{working level}.
24658 @item killed groups
24659 @cindex killed groups
24660 No information on killed groups is stored or updated, which makes killed
24661 groups much easier to handle than subscribed groups.
24663 @item zombie groups
24664 @cindex zombie groups
24665 Just like killed groups, only slightly less dead.
24668 @cindex active file
24669 The news server has to keep track of what articles it carries, and what
24670 groups exist. All this information in stored in the active file, which
24671 is rather large, as you might surmise.
24674 @cindex bogus groups
24675 A group that exists in the @file{.newsrc} file, but isn't known to the
24676 server (i.e., it isn't in the active file), is a @emph{bogus group}.
24677 This means that the group probably doesn't exist (any more).
24680 @cindex activating groups
24681 The act of asking the server for info on a group and computing the
24682 number of unread articles is called @dfn{activating the group}.
24683 Un-activated groups are listed with @samp{*} in the group buffer.
24687 A machine one can connect to and get news (or mail) from.
24689 @item select method
24690 @cindex select method
24691 A structure that specifies the back end, the server and the virtual
24694 @item virtual server
24695 @cindex virtual server
24696 A named select method. Since a select method defines all there is to
24697 know about connecting to a (physical) server, taking the thing as a
24698 whole is a virtual server.
24702 Taking a buffer and running it through a filter of some sort. The
24703 result will (more often than not) be cleaner and more pleasing than the
24706 @item ephemeral groups
24707 @cindex ephemeral groups
24708 Most groups store data on what articles you have read. @dfn{Ephemeral}
24709 groups are groups that will have no data stored---when you exit the
24710 group, it'll disappear into the aether.
24713 @cindex solid groups
24714 This is the opposite of ephemeral groups. All groups listed in the
24715 group buffer are solid groups.
24717 @item sparse articles
24718 @cindex sparse articles
24719 These are article placeholders shown in the summary buffer when
24720 @code{gnus-build-sparse-threads} has been switched on.
24724 To put responses to articles directly after the articles they respond
24725 to---in a hierarchical fashion.
24729 @cindex thread root
24730 The first article in a thread is the root. It is the ancestor of all
24731 articles in the thread.
24735 An article that has responses.
24739 An article that responds to a different article---its parent.
24743 A collection of messages in one file. The most common digest format is
24744 specified by RFC 1153.
24750 @node Customization
24751 @section Customization
24752 @cindex general customization
24754 All variables are properly documented elsewhere in this manual. This
24755 section is designed to give general pointers on how to customize Gnus
24756 for some quite common situations.
24759 * Slow/Expensive Connection:: You run a local Emacs and get the news elsewhere.
24760 * Slow Terminal Connection:: You run a remote Emacs.
24761 * Little Disk Space:: You feel that having large setup files is icky.
24762 * Slow Machine:: You feel like buying a faster machine.
24766 @node Slow/Expensive Connection
24767 @subsection Slow/Expensive NNTP Connection
24769 If you run Emacs on a machine locally, and get your news from a machine
24770 over some very thin strings, you want to cut down on the amount of data
24771 Gnus has to get from the @sc{nntp} server.
24775 @item gnus-read-active-file
24776 Set this to @code{nil}, which will inhibit Gnus from requesting the
24777 entire active file from the server. This file is often v. large. You
24778 also have to set @code{gnus-check-new-newsgroups} and
24779 @code{gnus-check-bogus-newsgroups} to @code{nil} to make sure that Gnus
24780 doesn't suddenly decide to fetch the active file anyway.
24782 @item gnus-nov-is-evil
24783 This one has to be @code{nil}. If not, grabbing article headers from
24784 the @sc{nntp} server will not be very fast. Not all @sc{nntp} servers
24785 support @sc{xover}; Gnus will detect this by itself.
24789 @node Slow Terminal Connection
24790 @subsection Slow Terminal Connection
24792 Let's say you use your home computer for dialing up the system that runs
24793 Emacs and Gnus. If your modem is slow, you want to reduce (as much as
24794 possible) the amount of data sent over the wires.
24798 @item gnus-auto-center-summary
24799 Set this to @code{nil} to inhibit Gnus from re-centering the summary
24800 buffer all the time. If it is @code{vertical}, do only vertical
24801 re-centering. If it is neither @code{nil} nor @code{vertical}, do both
24802 horizontal and vertical recentering.
24804 @item gnus-visible-headers
24805 Cut down on the headers included in the articles to the
24806 minimum. You can, in fact, make do without them altogether---most of the
24807 useful data is in the summary buffer, anyway. Set this variable to
24808 @samp{^NEVVVVER} or @samp{From:}, or whatever you feel you need.
24810 Set this hook to all the available hiding commands:
24812 (setq gnus-treat-hide-headers 'head
24813 gnus-treat-hide-signature t
24814 gnus-treat-hide-citation t)
24817 @item gnus-use-full-window
24818 By setting this to @code{nil}, you can make all the windows smaller.
24819 While this doesn't really cut down much generally, it means that you
24820 have to see smaller portions of articles before deciding that you didn't
24821 want to read them anyway.
24823 @item gnus-thread-hide-subtree
24824 If this is non-@code{nil}, all threads in the summary buffer will be
24828 @item gnus-updated-mode-lines
24829 If this is @code{nil}, Gnus will not put information in the buffer mode
24830 lines, which might save some time.
24834 @node Little Disk Space
24835 @subsection Little Disk Space
24838 The startup files can get rather large, so you may want to cut their
24839 sizes a bit if you are running out of space.
24843 @item gnus-save-newsrc-file
24844 If this is @code{nil}, Gnus will never save @file{.newsrc}---it will
24845 only save @file{.newsrc.eld}. This means that you will not be able to
24846 use any other newsreaders than Gnus. This variable is @code{t} by
24849 @item gnus-read-newsrc-file
24850 If this is @code{nil}, Gnus will never read @file{.newsrc}---it will
24851 only read @file{.newsrc.eld}. This means that you will not be able to
24852 use any other newsreaders than Gnus. This variable is @code{t} by
24855 @item gnus-save-killed-list
24856 If this is @code{nil}, Gnus will not save the list of dead groups. You
24857 should also set @code{gnus-check-new-newsgroups} to @code{ask-server}
24858 and @code{gnus-check-bogus-newsgroups} to @code{nil} if you set this
24859 variable to @code{nil}. This variable is @code{t} by default.
24865 @subsection Slow Machine
24866 @cindex slow machine
24868 If you have a slow machine, or are just really impatient, there are a
24869 few things you can do to make Gnus run faster.
24871 Set @code{gnus-check-new-newsgroups} and
24872 @code{gnus-check-bogus-newsgroups} to @code{nil} to make startup faster.
24874 Set @code{gnus-show-threads}, @code{gnus-use-cross-reference} and
24875 @code{gnus-nov-is-evil} to @code{nil} to make entering and exiting the
24876 summary buffer faster.
24880 @node Troubleshooting
24881 @section Troubleshooting
24882 @cindex troubleshooting
24884 Gnus works @emph{so} well straight out of the box---I can't imagine any
24892 Make sure your computer is switched on.
24895 Make sure that you really load the current Gnus version. If you have
24896 been running @sc{gnus}, you need to exit Emacs and start it up again before
24900 Try doing an @kbd{M-x gnus-version}. If you get something that looks
24901 like @samp{Gnus v5.46; nntp 4.0} you have the right files loaded. If,
24902 on the other hand, you get something like @samp{NNTP 3.x} or @samp{nntp
24903 flee}, you have some old @file{.el} files lying around. Delete these.
24906 Read the help group (@kbd{G h} in the group buffer) for a FAQ and a
24910 @vindex max-lisp-eval-depth
24911 Gnus works on many recursive structures, and in some extreme (and very
24912 rare) cases Gnus may recurse down ``too deeply'' and Emacs will beep at
24913 you. If this happens to you, set @code{max-lisp-eval-depth} to 500 or
24914 something like that.
24917 If all else fails, report the problem as a bug.
24920 @cindex reporting bugs
24922 @kindex M-x gnus-bug
24924 If you find a bug in Gnus, you can report it with the @kbd{M-x gnus-bug}
24925 command. @kbd{M-x set-variable RET debug-on-error RET t RET}, and send
24926 me the backtrace. I will fix bugs, but I can only fix them if you send
24927 me a precise description as to how to reproduce the bug.
24929 You really can never be too detailed in a bug report. Always use the
24930 @kbd{M-x gnus-bug} command when you make bug reports, even if it creates
24931 a 10Kb mail each time you use it, and even if you have sent me your
24932 environment 500 times before. I don't care. I want the full info each
24935 It is also important to remember that I have no memory whatsoever. If
24936 you send a bug report, and I send you a reply, and then you just send
24937 back ``No, it's not! Moron!'', I will have no idea what you are
24938 insulting me about. Always over-explain everything. It's much easier
24939 for all of us---if I don't have all the information I need, I will just
24940 mail you and ask for more info, and everything takes more time.
24942 If the problem you're seeing is very visual, and you can't quite explain
24943 it, copy the Emacs window to a file (with @code{xwd}, for instance), put
24944 it somewhere it can be reached, and include the URL of the picture in
24948 If you would like to contribute a patch to fix bugs or make
24949 improvements, please produce the patch using @samp{diff -u}.
24952 If you want to debug your problem further before reporting, possibly
24953 in order to solve the problem yourself and send a patch, you can use
24954 edebug. Debugging lisp code is documented in the Elisp manual
24955 (@pxref{Debugging, , Debugging Lisp Programs, elisp, The GNU Emacs
24956 Lisp Reference Manual}). To get you started with edebug, consider if
24957 you discover some weird behaviour when pressing @kbd{c}, the first
24958 step is to do @kbd{C-h k c} and click on the hyperlink (Emacs only) in
24959 the documentation buffer that leads you to the function definition,
24960 then press @kbd{M-x edebug-defun RET} with point inside that function,
24961 return to Gnus and press @kbd{c} to invoke the code. You will be
24962 placed in the lisp buffer and can single step using @kbd{SPC} and
24963 evaluate expressions using @kbd{M-:} or inspect variables using
24964 @kbd{C-h v}, abort execution with @kbd{q}, and resume execution with
24965 @kbd{c} or @kbd{g}.
24970 Sometimes, a problem do not directly generate a elisp error but
24971 manifests itself by causing Gnus to be very slow. In these cases, you
24972 can use @kbd{M-x toggle-debug-on-quit} and press @kbd{C-g} when things are
24973 slow, and then try to analyze the backtrace (repeating the procedure
24974 helps isolating the real problem areas). A fancier approach is to use
24975 the elisp profiler, ELP. The profiler is (or should be) fully
24976 documented elsewhere, but to get you started there are a few steps
24977 that need to be followed. First, instrument the part of Gnus you are
24978 interested in for profiling, e.g. @kbd{M-x elp-instrument-package RET
24979 gnus} or @kbd{M-x elp-instrument-package RET message}. Then perform
24980 the operation that is slow and press @kbd{M-x elp-results}. You will
24981 then see which operations that takes time, and can debug them further.
24982 If the entire operation takes much longer than the time spent in the
24983 slowest function in the profiler output, you probably profiled the
24984 wrong part of Gnus. To reset profiling statistics, use @kbd{M-x
24985 elp-reset-all}. @kbd{M-x elp-restore-all} is supposed to remove
24986 profiling, but given the complexities and dynamic code generation in
24987 Gnus, it might not always work perfectly.
24989 If you just need help, you are better off asking on
24990 @samp{gnu.emacs.gnus}. I'm not very helpful.
24992 @cindex gnu.emacs.gnus
24993 @cindex ding mailing list
24994 You can also ask on the ding mailing list---@email{ding@@gnus.org}.
24995 Write to @email{ding-request@@gnus.org} to subscribe.
24999 @node Gnus Reference Guide
25000 @section Gnus Reference Guide
25002 It is my hope that other people will figure out smart stuff that Gnus
25003 can do, and that other people will write those smart things as well. To
25004 facilitate that I thought it would be a good idea to describe the inner
25005 workings of Gnus. And some of the not-so-inner workings, while I'm at
25008 You can never expect the internals of a program not to change, but I
25009 will be defining (in some details) the interface between Gnus and its
25010 back ends (this is written in stone), the format of the score files
25011 (ditto), data structures (some are less likely to change than others)
25012 and general methods of operation.
25015 * Gnus Utility Functions:: Common functions and variable to use.
25016 * Back End Interface:: How Gnus communicates with the servers.
25017 * Score File Syntax:: A BNF definition of the score file standard.
25018 * Headers:: How Gnus stores headers internally.
25019 * Ranges:: A handy format for storing mucho numbers.
25020 * Group Info:: The group info format.
25021 * Extended Interactive:: Symbolic prefixes and stuff.
25022 * Emacs/XEmacs Code:: Gnus can be run under all modern Emacsen.
25023 * Various File Formats:: Formats of files that Gnus use.
25027 @node Gnus Utility Functions
25028 @subsection Gnus Utility Functions
25029 @cindex Gnus utility functions
25030 @cindex utility functions
25032 @cindex internal variables
25034 When writing small functions to be run from hooks (and stuff), it's
25035 vital to have access to the Gnus internal functions and variables.
25036 Below is a list of the most common ones.
25040 @item gnus-newsgroup-name
25041 @vindex gnus-newsgroup-name
25042 This variable holds the name of the current newsgroup.
25044 @item gnus-find-method-for-group
25045 @findex gnus-find-method-for-group
25046 A function that returns the select method for @var{group}.
25048 @item gnus-group-real-name
25049 @findex gnus-group-real-name
25050 Takes a full (prefixed) Gnus group name, and returns the unprefixed
25053 @item gnus-group-prefixed-name
25054 @findex gnus-group-prefixed-name
25055 Takes an unprefixed group name and a select method, and returns the full
25056 (prefixed) Gnus group name.
25058 @item gnus-get-info
25059 @findex gnus-get-info
25060 Returns the group info list for @var{group}.
25062 @item gnus-group-unread
25063 @findex gnus-group-unread
25064 The number of unread articles in @var{group}, or @code{t} if that is
25068 @findex gnus-active
25069 The active entry for @var{group}.
25071 @item gnus-set-active
25072 @findex gnus-set-active
25073 Set the active entry for @var{group}.
25075 @item gnus-add-current-to-buffer-list
25076 @findex gnus-add-current-to-buffer-list
25077 Adds the current buffer to the list of buffers to be killed on Gnus
25080 @item gnus-continuum-version
25081 @findex gnus-continuum-version
25082 Takes a Gnus version string as a parameter and returns a floating point
25083 number. Earlier versions will always get a lower number than later
25086 @item gnus-group-read-only-p
25087 @findex gnus-group-read-only-p
25088 Says whether @var{group} is read-only or not.
25090 @item gnus-news-group-p
25091 @findex gnus-news-group-p
25092 Says whether @var{group} came from a news back end.
25094 @item gnus-ephemeral-group-p
25095 @findex gnus-ephemeral-group-p
25096 Says whether @var{group} is ephemeral or not.
25098 @item gnus-server-to-method
25099 @findex gnus-server-to-method
25100 Returns the select method corresponding to @var{server}.
25102 @item gnus-server-equal
25103 @findex gnus-server-equal
25104 Says whether two virtual servers are equal.
25106 @item gnus-group-native-p
25107 @findex gnus-group-native-p
25108 Says whether @var{group} is native or not.
25110 @item gnus-group-secondary-p
25111 @findex gnus-group-secondary-p
25112 Says whether @var{group} is secondary or not.
25114 @item gnus-group-foreign-p
25115 @findex gnus-group-foreign-p
25116 Says whether @var{group} is foreign or not.
25118 @item group-group-find-parameter
25119 @findex group-group-find-parameter
25120 Returns the parameter list of @var{group}. If given a second parameter,
25121 returns the value of that parameter for @var{group}.
25123 @item gnus-group-set-parameter
25124 @findex gnus-group-set-parameter
25125 Takes three parameters; @var{group}, @var{parameter} and @var{value}.
25127 @item gnus-narrow-to-body
25128 @findex gnus-narrow-to-body
25129 Narrows the current buffer to the body of the article.
25131 @item gnus-check-backend-function
25132 @findex gnus-check-backend-function
25133 Takes two parameters, @var{function} and @var{group}. If the back end
25134 @var{group} comes from supports @var{function}, return non-@code{nil}.
25137 (gnus-check-backend-function "request-scan" "nnml:misc")
25141 @item gnus-read-method
25142 @findex gnus-read-method
25143 Prompts the user for a select method.
25148 @node Back End Interface
25149 @subsection Back End Interface
25151 Gnus doesn't know anything about @sc{nntp}, spools, mail or virtual
25152 groups. It only knows how to talk to @dfn{virtual servers}. A virtual
25153 server is a @dfn{back end} and some @dfn{back end variables}. As examples
25154 of the first, we have @code{nntp}, @code{nnspool} and @code{nnmbox}. As
25155 examples of the latter we have @code{nntp-port-number} and
25156 @code{nnmbox-directory}.
25158 When Gnus asks for information from a back end---say @code{nntp}---on
25159 something, it will normally include a virtual server name in the
25160 function parameters. (If not, the back end should use the ``current''
25161 virtual server.) For instance, @code{nntp-request-list} takes a virtual
25162 server as its only (optional) parameter. If this virtual server hasn't
25163 been opened, the function should fail.
25165 Note that a virtual server name has no relation to some physical server
25166 name. Take this example:
25170 (nntp-address "ifi.uio.no")
25171 (nntp-port-number 4324))
25174 Here the virtual server name is @samp{odd-one} while the name of
25175 the physical server is @samp{ifi.uio.no}.
25177 The back ends should be able to switch between several virtual servers.
25178 The standard back ends implement this by keeping an alist of virtual
25179 server environments that they pull down/push up when needed.
25181 There are two groups of interface functions: @dfn{required functions},
25182 which must be present, and @dfn{optional functions}, which Gnus will
25183 always check for presence before attempting to call 'em.
25185 All these functions are expected to return data in the buffer
25186 @code{nntp-server-buffer} (@samp{ *nntpd*}), which is somewhat
25187 unfortunately named, but we'll have to live with it. When I talk about
25188 @dfn{resulting data}, I always refer to the data in that buffer. When I
25189 talk about @dfn{return value}, I talk about the function value returned by
25190 the function call. Functions that fail should return @code{nil} as the
25193 Some back ends could be said to be @dfn{server-forming} back ends, and
25194 some might be said not to be. The latter are back ends that generally
25195 only operate on one group at a time, and have no concept of ``server''
25196 -- they have a group, and they deliver info on that group and nothing
25199 Gnus identifies each message by way of group name and article number. A
25200 few remarks about these article numbers might be useful. First of all,
25201 the numbers are positive integers. Secondly, it is normally not
25202 possible for later articles to `re-use' older article numbers without
25203 confusing Gnus. That is, if a group has ever contained a message
25204 numbered 42, then no other message may get that number, or Gnus will get
25205 mightily confused.@footnote{See the function
25206 @code{nnchoke-request-update-info}, @ref{Optional Back End Functions}.}
25207 Third, article numbers must be assigned in order of arrival in the
25208 group; this is not necessarily the same as the date of the message.
25210 The previous paragraph already mentions all the `hard' restrictions that
25211 article numbers must fulfill. But it seems that it might be useful to
25212 assign @emph{consecutive} article numbers, for Gnus gets quite confused
25213 if there are holes in the article numbering sequence. However, due to
25214 the `no-reuse' restriction, holes cannot be avoided altogether. It's
25215 also useful for the article numbers to start at 1 to avoid running out
25216 of numbers as long as possible.
25218 Note that by convention, backends are named @code{nnsomething}, but
25219 Gnus also comes with some @code{nnnotbackends}, such as
25220 @file{nnheader.el}, @file{nnmail.el} and @file{nnoo.el}.
25222 In the examples and definitions I will refer to the imaginary back end
25225 @cindex @code{nnchoke}
25228 * Required Back End Functions:: Functions that must be implemented.
25229 * Optional Back End Functions:: Functions that need not be implemented.
25230 * Error Messaging:: How to get messages and report errors.
25231 * Writing New Back Ends:: Extending old back ends.
25232 * Hooking New Back Ends Into Gnus:: What has to be done on the Gnus end.
25233 * Mail-like Back Ends:: Some tips on mail back ends.
25237 @node Required Back End Functions
25238 @subsubsection Required Back End Functions
25242 @item (nnchoke-retrieve-headers ARTICLES &optional GROUP SERVER FETCH-OLD)
25244 @var{articles} is either a range of article numbers or a list of
25245 @code{Message-ID}s. Current back ends do not fully support either---only
25246 sequences (lists) of article numbers, and most back ends do not support
25247 retrieval of @code{Message-ID}s. But they should try for both.
25249 The result data should either be HEADs or @sc{nov} lines, and the result
25250 value should either be @code{headers} or @code{nov} to reflect this.
25251 This might later be expanded to @code{various}, which will be a mixture
25252 of HEADs and @sc{nov} lines, but this is currently not supported by Gnus.
25254 If @var{fetch-old} is non-@code{nil} it says to try fetching ``extra
25255 headers'', in some meaning of the word. This is generally done by
25256 fetching (at most) @var{fetch-old} extra headers less than the smallest
25257 article number in @code{articles}, and filling the gaps as well. The
25258 presence of this parameter can be ignored if the back end finds it
25259 cumbersome to follow the request. If this is non-@code{nil} and not a
25260 number, do maximum fetches.
25262 Here's an example HEAD:
25265 221 1056 Article retrieved.
25266 Path: ifi.uio.no!sturles
25267 From: sturles@@ifi.uio.no (Sturle Sunde)
25268 Newsgroups: ifi.discussion
25269 Subject: Re: Something very droll
25270 Date: 27 Oct 1994 14:02:57 +0100
25271 Organization: Dept. of Informatics, University of Oslo, Norway
25273 Message-ID: <38o8e1$a0o@@holmenkollen.ifi.uio.no>
25274 References: <38jdmq$4qu@@visbur.ifi.uio.no>
25275 NNTP-Posting-Host: holmenkollen.ifi.uio.no
25279 So a @code{headers} return value would imply that there's a number of
25280 these in the data buffer.
25282 Here's a BNF definition of such a buffer:
25286 head = error / valid-head
25287 error-message = [ "4" / "5" ] 2number " " <error message> eol
25288 valid-head = valid-message *header "." eol
25289 valid-message = "221 " <number> " Article retrieved." eol
25290 header = <text> eol
25294 (The version of BNF used here is the one used in RFC822.)
25296 If the return value is @code{nov}, the data buffer should contain
25297 @dfn{network overview database} lines. These are basically fields
25301 nov-buffer = *nov-line
25302 nov-line = field 7*8[ <TAB> field ] eol
25303 field = <text except TAB>
25306 For a closer look at what should be in those fields,
25310 @item (nnchoke-open-server SERVER &optional DEFINITIONS)
25312 @var{server} is here the virtual server name. @var{definitions} is a
25313 list of @code{(VARIABLE VALUE)} pairs that define this virtual server.
25315 If the server can't be opened, no error should be signaled. The back end
25316 may then choose to refuse further attempts at connecting to this
25317 server. In fact, it should do so.
25319 If the server is opened already, this function should return a
25320 non-@code{nil} value. There should be no data returned.
25323 @item (nnchoke-close-server &optional SERVER)
25325 Close connection to @var{server} and free all resources connected
25326 to it. Return @code{nil} if the server couldn't be closed for some
25329 There should be no data returned.
25332 @item (nnchoke-request-close)
25334 Close connection to all servers and free all resources that the back end
25335 have reserved. All buffers that have been created by that back end
25336 should be killed. (Not the @code{nntp-server-buffer}, though.) This
25337 function is generally only called when Gnus is shutting down.
25339 There should be no data returned.
25342 @item (nnchoke-server-opened &optional SERVER)
25344 If @var{server} is the current virtual server, and the connection to the
25345 physical server is alive, then this function should return a
25346 non-@code{nil} vlue. This function should under no circumstances
25347 attempt to reconnect to a server we have lost connection to.
25349 There should be no data returned.
25352 @item (nnchoke-status-message &optional SERVER)
25354 This function should return the last error message from @var{server}.
25356 There should be no data returned.
25359 @item (nnchoke-request-article ARTICLE &optional GROUP SERVER TO-BUFFER)
25361 The result data from this function should be the article specified by
25362 @var{article}. This might either be a @code{Message-ID} or a number.
25363 It is optional whether to implement retrieval by @code{Message-ID}, but
25364 it would be nice if that were possible.
25366 If @var{to-buffer} is non-@code{nil}, the result data should be returned
25367 in this buffer instead of the normal data buffer. This is to make it
25368 possible to avoid copying large amounts of data from one buffer to
25369 another, while Gnus mainly requests articles to be inserted directly
25370 into its article buffer.
25372 If it is at all possible, this function should return a cons cell where
25373 the @code{car} is the group name the article was fetched from, and the @code{cdr} is
25374 the article number. This will enable Gnus to find out what the real
25375 group and article numbers are when fetching articles by
25376 @code{Message-ID}. If this isn't possible, @code{t} should be returned
25377 on successful article retrieval.
25380 @item (nnchoke-request-group GROUP &optional SERVER FAST)
25382 Get data on @var{group}. This function also has the side effect of
25383 making @var{group} the current group.
25385 If @var{fast}, don't bother to return useful data, just make @var{group}
25388 Here's an example of some result data and a definition of the same:
25391 211 56 1000 1059 ifi.discussion
25394 The first number is the status, which should be 211. Next is the
25395 total number of articles in the group, the lowest article number, the
25396 highest article number, and finally the group name. Note that the total
25397 number of articles may be less than one might think while just
25398 considering the highest and lowest article numbers, but some articles
25399 may have been canceled. Gnus just discards the total-number, so
25400 whether one should take the bother to generate it properly (if that is a
25401 problem) is left as an exercise to the reader. If the group contains no
25402 articles, the lowest article number should be reported as 1 and the
25406 group-status = [ error / info ] eol
25407 error = [ "4" / "5" ] 2<number> " " <Error message>
25408 info = "211 " 3* [ <number> " " ] <string>
25412 @item (nnchoke-close-group GROUP &optional SERVER)
25414 Close @var{group} and free any resources connected to it. This will be
25415 a no-op on most back ends.
25417 There should be no data returned.
25420 @item (nnchoke-request-list &optional SERVER)
25422 Return a list of all groups available on @var{server}. And that means
25425 Here's an example from a server that only carries two groups:
25428 ifi.test 0000002200 0000002000 y
25429 ifi.discussion 3324 3300 n
25432 On each line we have a group name, then the highest article number in
25433 that group, the lowest article number, and finally a flag. If the group
25434 contains no articles, the lowest article number should be reported as 1
25435 and the highest as 0.
25438 active-file = *active-line
25439 active-line = name " " <number> " " <number> " " flags eol
25441 flags = "n" / "y" / "m" / "x" / "j" / "=" name
25444 The flag says whether the group is read-only (@samp{n}), is moderated
25445 (@samp{m}), is dead (@samp{x}), is aliased to some other group
25446 (@samp{=other-group}) or none of the above (@samp{y}).
25449 @item (nnchoke-request-post &optional SERVER)
25451 This function should post the current buffer. It might return whether
25452 the posting was successful or not, but that's not required. If, for
25453 instance, the posting is done asynchronously, it has generally not been
25454 completed by the time this function concludes. In that case, this
25455 function should set up some kind of sentinel to beep the user loud and
25456 clear if the posting could not be completed.
25458 There should be no result data from this function.
25463 @node Optional Back End Functions
25464 @subsubsection Optional Back End Functions
25468 @item (nnchoke-retrieve-groups GROUPS &optional SERVER)
25470 @var{groups} is a list of groups, and this function should request data
25471 on all those groups. How it does it is of no concern to Gnus, but it
25472 should attempt to do this in a speedy fashion.
25474 The return value of this function can be either @code{active} or
25475 @code{group}, which says what the format of the result data is. The
25476 former is in the same format as the data from
25477 @code{nnchoke-request-list}, while the latter is a buffer full of lines
25478 in the same format as @code{nnchoke-request-group} gives.
25481 group-buffer = *active-line / *group-status
25485 @item (nnchoke-request-update-info GROUP INFO &optional SERVER)
25487 A Gnus group info (@pxref{Group Info}) is handed to the back end for
25488 alterations. This comes in handy if the back end really carries all the
25489 information (as is the case with virtual and imap groups). This
25490 function should destructively alter the info to suit its needs, and
25491 should return a non-nil value.
25493 There should be no result data from this function.
25496 @item (nnchoke-request-type GROUP &optional ARTICLE)
25498 When the user issues commands for ``sending news'' (@kbd{F} in the
25499 summary buffer, for instance), Gnus has to know whether the article the
25500 user is following up on is news or mail. This function should return
25501 @code{news} if @var{article} in @var{group} is news, @code{mail} if it
25502 is mail and @code{unknown} if the type can't be decided. (The
25503 @var{article} parameter is necessary in @code{nnvirtual} groups which
25504 might very well combine mail groups and news groups.) Both @var{group}
25505 and @var{article} may be @code{nil}.
25507 There should be no result data from this function.
25510 @item (nnchoke-request-set-mark GROUP ACTION &optional SERVER)
25512 Set/remove/add marks on articles. Normally Gnus handles the article
25513 marks (such as read, ticked, expired etc) internally, and store them in
25514 @file{~/.newsrc.eld}. Some back ends (such as @sc{imap}) however carry
25515 all information about the articles on the server, so Gnus need to
25516 propagate the mark information to the server.
25518 @var{action} is a list of mark setting requests, having this format:
25521 (RANGE ACTION MARK)
25524 @var{range} is a range of articles you wish to update marks on.
25525 @var{action} is @code{add} or @code{del}, used to add marks or remove
25526 marks (preserving all marks not mentioned). @var{mark} is a list of
25527 marks; where each mark is a symbol. Currently used marks are
25528 @code{read}, @code{tick}, @code{reply}, @code{expire}, @code{killed},
25529 @code{dormant}, @code{save}, @code{download}, @code{unsend},
25530 @code{forward} and @code{recent}, but your back end should, if
25531 possible, not limit itself to these.
25533 Given contradictory actions, the last action in the list should be the
25534 effective one. That is, if your action contains a request to add the
25535 @code{tick} mark on article 1 and, later in the list, a request to
25536 remove the mark on the same article, the mark should in fact be removed.
25538 An example action list:
25541 (((5 12 30) 'del '(tick))
25542 ((10 . 90) 'add '(read expire))
25543 ((92 94) 'del '(read)))
25546 The function should return a range of articles it wasn't able to set the
25547 mark on (currently not used for anything).
25549 There should be no result data from this function.
25551 @item (nnchoke-request-update-mark GROUP ARTICLE MARK)
25553 If the user tries to set a mark that the back end doesn't like, this
25554 function may change the mark. Gnus will use whatever this function
25555 returns as the mark for @var{article} instead of the original
25556 @var{mark}. If the back end doesn't care, it must return the original
25557 @var{mark}, and not @code{nil} or any other type of garbage.
25559 The only use for this I can see is what @code{nnvirtual} does with
25560 it---if a component group is auto-expirable, marking an article as read
25561 in the virtual group should result in the article being marked as
25564 There should be no result data from this function.
25567 @item (nnchoke-request-scan &optional GROUP SERVER)
25569 This function may be called at any time (by Gnus or anything else) to
25570 request that the back end check for incoming articles, in one way or
25571 another. A mail back end will typically read the spool file or query the
25572 POP server when this function is invoked. The @var{group} doesn't have
25573 to be heeded---if the back end decides that it is too much work just
25574 scanning for a single group, it may do a total scan of all groups. It
25575 would be nice, however, to keep things local if that's practical.
25577 There should be no result data from this function.
25580 @item (nnchoke-request-group-description GROUP &optional SERVER)
25582 The result data from this function should be a description of
25586 description-line = name <TAB> description eol
25588 description = <text>
25591 @item (nnchoke-request-list-newsgroups &optional SERVER)
25593 The result data from this function should be the description of all
25594 groups available on the server.
25597 description-buffer = *description-line
25601 @item (nnchoke-request-newgroups DATE &optional SERVER)
25603 The result data from this function should be all groups that were
25604 created after @samp{date}, which is in normal human-readable date format
25605 (i.e., the date format used in mail and news headers, and returned by
25606 the function @code{message-make-date} by default). The data should be
25607 in the active buffer format.
25609 It is okay for this function to return `too many' groups; some back ends
25610 might find it cheaper to return the full list of groups, rather than
25611 just the new groups. But don't do this for back ends with many groups.
25612 Normally, if the user creates the groups herself, there won't be too
25613 many groups, so @code{nnml} and the like are probably safe. But for
25614 back ends like @code{nntp}, where the groups have been created by the
25615 server, it is quite likely that there can be many groups.
25618 @item (nnchoke-request-create-group GROUP &optional SERVER)
25620 This function should create an empty group with name @var{group}.
25622 There should be no return data.
25625 @item (nnchoke-request-expire-articles ARTICLES &optional GROUP SERVER FORCE)
25627 This function should run the expiry process on all articles in the
25628 @var{articles} range (which is currently a simple list of article
25629 numbers.) It is left up to the back end to decide how old articles
25630 should be before they are removed by this function. If @var{force} is
25631 non-@code{nil}, all @var{articles} should be deleted, no matter how new
25634 This function should return a list of articles that it did not/was not
25637 There should be no result data returned.
25640 @item (nnchoke-request-move-article ARTICLE GROUP SERVER ACCEPT-FORM &optional LAST)
25642 This function should move @var{article} (which is a number) from
25643 @var{group} by calling @var{accept-form}.
25645 This function should ready the article in question for moving by
25646 removing any header lines it has added to the article, and generally
25647 should ``tidy up'' the article. Then it should @code{eval}
25648 @var{accept-form} in the buffer where the ``tidy'' article is. This
25649 will do the actual copying. If this @code{eval} returns a
25650 non-@code{nil} value, the article should be removed.
25652 If @var{last} is @code{nil}, that means that there is a high likelihood
25653 that there will be more requests issued shortly, so that allows some
25656 The function should return a cons where the @code{car} is the group name and
25657 the @code{cdr} is the article number that the article was entered as.
25659 There should be no data returned.
25662 @item (nnchoke-request-accept-article GROUP &optional SERVER LAST)
25664 This function takes the current buffer and inserts it into @var{group}.
25665 If @var{last} in @code{nil}, that means that there will be more calls to
25666 this function in short order.
25668 The function should return a cons where the @code{car} is the group name and
25669 the @code{cdr} is the article number that the article was entered as.
25671 The group should exist before the backend is asked to accept the
25672 article for that group.
25674 There should be no data returned.
25677 @item (nnchoke-request-replace-article ARTICLE GROUP BUFFER)
25679 This function should remove @var{article} (which is a number) from
25680 @var{group} and insert @var{buffer} there instead.
25682 There should be no data returned.
25685 @item (nnchoke-request-delete-group GROUP FORCE &optional SERVER)
25687 This function should delete @var{group}. If @var{force}, it should
25688 really delete all the articles in the group, and then delete the group
25689 itself. (If there is such a thing as ``the group itself''.)
25691 There should be no data returned.
25694 @item (nnchoke-request-rename-group GROUP NEW-NAME &optional SERVER)
25696 This function should rename @var{group} into @var{new-name}. All
25697 articles in @var{group} should move to @var{new-name}.
25699 There should be no data returned.
25704 @node Error Messaging
25705 @subsubsection Error Messaging
25707 @findex nnheader-report
25708 @findex nnheader-get-report
25709 The back ends should use the function @code{nnheader-report} to report
25710 error conditions---they should not raise errors when they aren't able to
25711 perform a request. The first argument to this function is the back end
25712 symbol, and the rest are interpreted as arguments to @code{format} if
25713 there are multiple of them, or just a string if there is one of them.
25714 This function must always returns @code{nil}.
25717 (nnheader-report 'nnchoke "You did something totally bogus")
25719 (nnheader-report 'nnchoke "Could not request group %s" group)
25722 Gnus, in turn, will call @code{nnheader-get-report} when it gets a
25723 @code{nil} back from a server, and this function returns the most
25724 recently reported message for the back end in question. This function
25725 takes one argument---the server symbol.
25727 Internally, these functions access @var{back-end}@code{-status-string},
25728 so the @code{nnchoke} back end will have its error message stored in
25729 @code{nnchoke-status-string}.
25732 @node Writing New Back Ends
25733 @subsubsection Writing New Back Ends
25735 Many back ends are quite similar. @code{nnml} is just like
25736 @code{nnspool}, but it allows you to edit the articles on the server.
25737 @code{nnmh} is just like @code{nnml}, but it doesn't use an active file,
25738 and it doesn't maintain overview databases. @code{nndir} is just like
25739 @code{nnml}, but it has no concept of ``groups'', and it doesn't allow
25742 It would make sense if it were possible to ``inherit'' functions from
25743 back ends when writing new back ends. And, indeed, you can do that if you
25744 want to. (You don't have to if you don't want to, of course.)
25746 All the back ends declare their public variables and functions by using a
25747 package called @code{nnoo}.
25749 To inherit functions from other back ends (and allow other back ends to
25750 inherit functions from the current back end), you should use the
25756 This macro declares the first parameter to be a child of the subsequent
25757 parameters. For instance:
25760 (nnoo-declare nndir
25764 @code{nndir} has declared here that it intends to inherit functions from
25765 both @code{nnml} and @code{nnmh}.
25768 This macro is equivalent to @code{defvar}, but registers the variable as
25769 a public server variable. Most state-oriented variables should be
25770 declared with @code{defvoo} instead of @code{defvar}.
25772 In addition to the normal @code{defvar} parameters, it takes a list of
25773 variables in the parent back ends to map the variable to when executing
25774 a function in those back ends.
25777 (defvoo nndir-directory nil
25778 "Where nndir will look for groups."
25779 nnml-current-directory nnmh-current-directory)
25782 This means that @code{nnml-current-directory} will be set to
25783 @code{nndir-directory} when an @code{nnml} function is called on behalf
25784 of @code{nndir}. (The same with @code{nnmh}.)
25786 @item nnoo-define-basics
25787 This macro defines some common functions that almost all back ends should
25791 (nnoo-define-basics nndir)
25795 This macro is just like @code{defun} and takes the same parameters. In
25796 addition to doing the normal @code{defun} things, it registers the
25797 function as being public so that other back ends can inherit it.
25799 @item nnoo-map-functions
25800 This macro allows mapping of functions from the current back end to
25801 functions from the parent back ends.
25804 (nnoo-map-functions nndir
25805 (nnml-retrieve-headers 0 nndir-current-group 0 0)
25806 (nnmh-request-article 0 nndir-current-group 0 0))
25809 This means that when @code{nndir-retrieve-headers} is called, the first,
25810 third, and fourth parameters will be passed on to
25811 @code{nnml-retrieve-headers}, while the second parameter is set to the
25812 value of @code{nndir-current-group}.
25815 This macro allows importing functions from back ends. It should be the
25816 last thing in the source file, since it will only define functions that
25817 haven't already been defined.
25823 nnmh-request-newgroups)
25827 This means that calls to @code{nndir-request-list} should just be passed
25828 on to @code{nnmh-request-list}, while all public functions from
25829 @code{nnml} that haven't been defined in @code{nndir} yet should be
25834 Below is a slightly shortened version of the @code{nndir} back end.
25837 ;;; nndir.el --- single directory newsgroup access for Gnus
25838 ;; Copyright (C) 1995,96 Free Software Foundation, Inc.
25842 (require 'nnheader)
25846 (eval-when-compile (require 'cl))
25848 (nnoo-declare nndir
25851 (defvoo nndir-directory nil
25852 "Where nndir will look for groups."
25853 nnml-current-directory nnmh-current-directory)
25855 (defvoo nndir-nov-is-evil nil
25856 "*Non-nil means that nndir will never retrieve NOV headers."
25859 (defvoo nndir-current-group ""
25861 nnml-current-group nnmh-current-group)
25862 (defvoo nndir-top-directory nil nil nnml-directory nnmh-directory)
25863 (defvoo nndir-get-new-mail nil nil nnml-get-new-mail nnmh-get-new-mail)
25865 (defvoo nndir-status-string "" nil nnmh-status-string)
25866 (defconst nndir-version "nndir 1.0")
25868 ;;; Interface functions.
25870 (nnoo-define-basics nndir)
25872 (deffoo nndir-open-server (server &optional defs)
25873 (setq nndir-directory
25874 (or (cadr (assq 'nndir-directory defs))
25876 (unless (assq 'nndir-directory defs)
25877 (push `(nndir-directory ,server) defs))
25878 (push `(nndir-current-group
25879 ,(file-name-nondirectory
25880 (directory-file-name nndir-directory)))
25882 (push `(nndir-top-directory
25883 ,(file-name-directory (directory-file-name nndir-directory)))
25885 (nnoo-change-server 'nndir server defs))
25887 (nnoo-map-functions nndir
25888 (nnml-retrieve-headers 0 nndir-current-group 0 0)
25889 (nnmh-request-article 0 nndir-current-group 0 0)
25890 (nnmh-request-group nndir-current-group 0 0)
25891 (nnmh-close-group nndir-current-group 0))
25895 nnmh-status-message
25897 nnmh-request-newgroups))
25903 @node Hooking New Back Ends Into Gnus
25904 @subsubsection Hooking New Back Ends Into Gnus
25906 @vindex gnus-valid-select-methods
25907 @findex gnus-declare-backend
25908 Having Gnus start using your new back end is rather easy---you just
25909 declare it with the @code{gnus-declare-backend} functions. This will
25910 enter the back end into the @code{gnus-valid-select-methods} variable.
25912 @code{gnus-declare-backend} takes two parameters---the back end name and
25913 an arbitrary number of @dfn{abilities}.
25918 (gnus-declare-backend "nnchoke" 'mail 'respool 'address)
25921 The above line would then go in the @file{nnchoke.el} file.
25923 The abilities can be:
25927 This is a mailish back end---followups should (probably) go via mail.
25929 This is a newsish back end---followups should (probably) go via news.
25931 This back end supports both mail and news.
25933 This is neither a post nor mail back end---it's something completely
25936 It supports respooling---or rather, it is able to modify its source
25937 articles and groups.
25939 The name of the server should be in the virtual server name. This is
25940 true for almost all back ends.
25941 @item prompt-address
25942 The user should be prompted for an address when doing commands like
25943 @kbd{B} in the group buffer. This is true for back ends like
25944 @code{nntp}, but not @code{nnmbox}, for instance.
25948 @node Mail-like Back Ends
25949 @subsubsection Mail-like Back Ends
25951 One of the things that separate the mail back ends from the rest of the
25952 back ends is the heavy dependence by most of the mail back ends on
25953 common functions in @file{nnmail.el}. For instance, here's the
25954 definition of @code{nnml-request-scan}:
25957 (deffoo nnml-request-scan (&optional group server)
25958 (setq nnml-article-file-alist nil)
25959 (nnmail-get-new-mail 'nnml 'nnml-save-nov nnml-directory group))
25962 It simply calls @code{nnmail-get-new-mail} with a few parameters,
25963 and @code{nnmail} takes care of all the moving and splitting of the
25966 This function takes four parameters.
25970 This should be a symbol to designate which back end is responsible for
25973 @item exit-function
25974 This function should be called after the splitting has been performed.
25976 @item temp-directory
25977 Where the temporary files should be stored.
25980 This optional argument should be a group name if the splitting is to be
25981 performed for one group only.
25984 @code{nnmail-get-new-mail} will call @var{back-end}@code{-save-mail} to
25985 save each article. @var{back-end}@code{-active-number} will be called to
25986 find the article number assigned to this article.
25988 The function also uses the following variables:
25989 @var{back-end}@code{-get-new-mail} (to see whether to get new mail for
25990 this back end); and @var{back-end}@code{-group-alist} and
25991 @var{back-end}@code{-active-file} to generate the new active file.
25992 @var{back-end}@code{-group-alist} should be a group-active alist, like
25996 (("a-group" (1 . 10))
25997 ("some-group" (34 . 39)))
26001 @node Score File Syntax
26002 @subsection Score File Syntax
26004 Score files are meant to be easily parseable, but yet extremely
26005 mallable. It was decided that something that had the same read syntax
26006 as an Emacs Lisp list would fit that spec.
26008 Here's a typical score file:
26012 ("win95" -10000 nil s)
26019 BNF definition of a score file:
26022 score-file = "" / "(" *element ")"
26023 element = rule / atom
26024 rule = string-rule / number-rule / date-rule
26025 string-rule = "(" quote string-header quote space *string-match ")"
26026 number-rule = "(" quote number-header quote space *number-match ")"
26027 date-rule = "(" quote date-header quote space *date-match ")"
26029 string-header = "subject" / "from" / "references" / "message-id" /
26030 "xref" / "body" / "head" / "all" / "followup"
26031 number-header = "lines" / "chars"
26032 date-header = "date"
26033 string-match = "(" quote <string> quote [ "" / [ space score [ "" /
26034 space date [ "" / [ space string-match-t ] ] ] ] ] ")"
26035 score = "nil" / <integer>
26036 date = "nil" / <natural number>
26037 string-match-t = "nil" / "s" / "substring" / "S" / "Substring" /
26038 "r" / "regex" / "R" / "Regex" /
26039 "e" / "exact" / "E" / "Exact" /
26040 "f" / "fuzzy" / "F" / "Fuzzy"
26041 number-match = "(" <integer> [ "" / [ space score [ "" /
26042 space date [ "" / [ space number-match-t ] ] ] ] ] ")"
26043 number-match-t = "nil" / "=" / "<" / ">" / ">=" / "<="
26044 date-match = "(" quote <string> quote [ "" / [ space score [ "" /
26045 space date [ "" / [ space date-match-t ] ] ] ] ")"
26046 date-match-t = "nil" / "at" / "before" / "after"
26047 atom = "(" [ required-atom / optional-atom ] ")"
26048 required-atom = mark / expunge / mark-and-expunge / files /
26049 exclude-files / read-only / touched
26050 optional-atom = adapt / local / eval
26051 mark = "mark" space nil-or-number
26052 nil-or-number = "nil" / <integer>
26053 expunge = "expunge" space nil-or-number
26054 mark-and-expunge = "mark-and-expunge" space nil-or-number
26055 files = "files" *[ space <string> ]
26056 exclude-files = "exclude-files" *[ space <string> ]
26057 read-only = "read-only" [ space "nil" / space "t" ]
26058 adapt = "adapt" [ space "ignore" / space "t" / space adapt-rule ]
26059 adapt-rule = "(" *[ <string> *[ "(" <string> <integer> ")" ] ")"
26060 local = "local" *[ space "(" <string> space <form> ")" ]
26061 eval = "eval" space <form>
26062 space = *[ " " / <TAB> / <NEWLINE> ]
26065 Any unrecognized elements in a score file should be ignored, but not
26068 As you can see, white space is needed, but the type and amount of white
26069 space is irrelevant. This means that formatting of the score file is
26070 left up to the programmer---if it's simpler to just spew it all out on
26071 one looong line, then that's ok.
26073 The meaning of the various atoms are explained elsewhere in this
26074 manual (@pxref{Score File Format}).
26078 @subsection Headers
26080 Internally Gnus uses a format for storing article headers that
26081 corresponds to the @sc{nov} format in a mysterious fashion. One could
26082 almost suspect that the author looked at the @sc{nov} specification and
26083 just shamelessly @emph{stole} the entire thing, and one would be right.
26085 @dfn{Header} is a severely overloaded term. ``Header'' is used in
26086 RFC 1036 to talk about lines in the head of an article (e.g.,
26087 @code{From}). It is used by many people as a synonym for
26088 ``head''---``the header and the body''. (That should be avoided, in my
26089 opinion.) And Gnus uses a format internally that it calls ``header'',
26090 which is what I'm talking about here. This is a 9-element vector,
26091 basically, with each header (ouch) having one slot.
26093 These slots are, in order: @code{number}, @code{subject}, @code{from},
26094 @code{date}, @code{id}, @code{references}, @code{chars}, @code{lines},
26095 @code{xref}, and @code{extra}. There are macros for accessing and
26096 setting these slots---they all have predictable names beginning with
26097 @code{mail-header-} and @code{mail-header-set-}, respectively.
26099 All these slots contain strings, except the @code{extra} slot, which
26100 contains an alist of header/value pairs (@pxref{To From Newsgroups}).
26106 @sc{gnus} introduced a concept that I found so useful that I've started
26107 using it a lot and have elaborated on it greatly.
26109 The question is simple: If you have a large amount of objects that are
26110 identified by numbers (say, articles, to take a @emph{wild} example)
26111 that you want to qualify as being ``included'', a normal sequence isn't
26112 very useful. (A 200,000 length sequence is a bit long-winded.)
26114 The solution is as simple as the question: You just collapse the
26118 (1 2 3 4 5 6 10 11 12)
26121 is transformed into
26124 ((1 . 6) (10 . 12))
26127 To avoid having those nasty @samp{(13 . 13)} elements to denote a
26128 lonesome object, a @samp{13} is a valid element:
26131 ((1 . 6) 7 (10 . 12))
26134 This means that comparing two ranges to find out whether they are equal
26135 is slightly tricky:
26138 ((1 . 5) 7 8 (10 . 12))
26144 ((1 . 5) (7 . 8) (10 . 12))
26147 are equal. In fact, any non-descending list is a range:
26153 is a perfectly valid range, although a pretty long-winded one. This is
26160 and is equal to the previous range.
26162 Here's a BNF definition of ranges. Of course, one must remember the
26163 semantic requirement that the numbers are non-descending. (Any number
26164 of repetition of the same number is allowed, but apt to disappear in
26168 range = simple-range / normal-range
26169 simple-range = "(" number " . " number ")"
26170 normal-range = "(" start-contents ")"
26171 contents = "" / simple-range *[ " " contents ] /
26172 number *[ " " contents ]
26175 Gnus currently uses ranges to keep track of read articles and article
26176 marks. I plan on implementing a number of range operators in C if The
26177 Powers That Be are willing to let me. (I haven't asked yet, because I
26178 need to do some more thinking on what operators I need to make life
26179 totally range-based without ever having to convert back to normal
26184 @subsection Group Info
26186 Gnus stores all permanent info on groups in a @dfn{group info} list.
26187 This list is from three to six elements (or more) long and exhaustively
26188 describes the group.
26190 Here are two example group infos; one is a very simple group while the
26191 second is a more complex one:
26194 ("no.group" 5 ((1 . 54324)))
26196 ("nnml:my.mail" 3 ((1 . 5) 9 (20 . 55))
26197 ((tick (15 . 19)) (replied 3 6 (19 . 3)))
26199 ((auto-expire . t) (to-address . "ding@@gnus.org")))
26202 The first element is the @dfn{group name}---as Gnus knows the group,
26203 anyway. The second element is the @dfn{subscription level}, which
26204 normally is a small integer. (It can also be the @dfn{rank}, which is a
26205 cons cell where the @code{car} is the level and the @code{cdr} is the
26206 score.) The third element is a list of ranges of read articles. The
26207 fourth element is a list of lists of article marks of various kinds.
26208 The fifth element is the select method (or virtual server, if you like).
26209 The sixth element is a list of @dfn{group parameters}, which is what
26210 this section is about.
26212 Any of the last three elements may be missing if they are not required.
26213 In fact, the vast majority of groups will normally only have the first
26214 three elements, which saves quite a lot of cons cells.
26216 Here's a BNF definition of the group info format:
26219 info = "(" group space ralevel space read
26220 [ "" / [ space marks-list [ "" / [ space method [ "" /
26221 space parameters ] ] ] ] ] ")"
26222 group = quote <string> quote
26223 ralevel = rank / level
26224 level = <integer in the range of 1 to inf>
26225 rank = "(" level "." score ")"
26226 score = <integer in the range of 1 to inf>
26228 marks-lists = nil / "(" *marks ")"
26229 marks = "(" <string> range ")"
26230 method = "(" <string> *elisp-forms ")"
26231 parameters = "(" *elisp-forms ")"
26234 Actually that @samp{marks} rule is a fib. A @samp{marks} is a
26235 @samp{<string>} consed on to a @samp{range}, but that's a bitch to say
26238 If you have a Gnus info and want to access the elements, Gnus offers a
26239 series of macros for getting/setting these elements.
26242 @item gnus-info-group
26243 @itemx gnus-info-set-group
26244 @findex gnus-info-group
26245 @findex gnus-info-set-group
26246 Get/set the group name.
26248 @item gnus-info-rank
26249 @itemx gnus-info-set-rank
26250 @findex gnus-info-rank
26251 @findex gnus-info-set-rank
26252 Get/set the group rank (@pxref{Group Score}).
26254 @item gnus-info-level
26255 @itemx gnus-info-set-level
26256 @findex gnus-info-level
26257 @findex gnus-info-set-level
26258 Get/set the group level.
26260 @item gnus-info-score
26261 @itemx gnus-info-set-score
26262 @findex gnus-info-score
26263 @findex gnus-info-set-score
26264 Get/set the group score (@pxref{Group Score}).
26266 @item gnus-info-read
26267 @itemx gnus-info-set-read
26268 @findex gnus-info-read
26269 @findex gnus-info-set-read
26270 Get/set the ranges of read articles.
26272 @item gnus-info-marks
26273 @itemx gnus-info-set-marks
26274 @findex gnus-info-marks
26275 @findex gnus-info-set-marks
26276 Get/set the lists of ranges of marked articles.
26278 @item gnus-info-method
26279 @itemx gnus-info-set-method
26280 @findex gnus-info-method
26281 @findex gnus-info-set-method
26282 Get/set the group select method.
26284 @item gnus-info-params
26285 @itemx gnus-info-set-params
26286 @findex gnus-info-params
26287 @findex gnus-info-set-params
26288 Get/set the group parameters.
26291 All the getter functions take one parameter---the info list. The setter
26292 functions take two parameters---the info list and the new value.
26294 The last three elements in the group info aren't mandatory, so it may be
26295 necessary to extend the group info before setting the element. If this
26296 is necessary, you can just pass on a non-@code{nil} third parameter to
26297 the three final setter functions to have this happen automatically.
26300 @node Extended Interactive
26301 @subsection Extended Interactive
26302 @cindex interactive
26303 @findex gnus-interactive
26305 Gnus extends the standard Emacs @code{interactive} specification
26306 slightly to allow easy use of the symbolic prefix (@pxref{Symbolic
26307 Prefixes}). Here's an example of how this is used:
26310 (defun gnus-summary-increase-score (&optional score symp)
26311 (interactive (gnus-interactive "P\ny"))
26316 The best thing to do would have been to implement
26317 @code{gnus-interactive} as a macro which would have returned an
26318 @code{interactive} form, but this isn't possible since Emacs checks
26319 whether a function is interactive or not by simply doing an @code{assq}
26320 on the lambda form. So, instead we have @code{gnus-interactive}
26321 function that takes a string and returns values that are usable to
26322 @code{interactive}.
26324 This function accepts (almost) all normal @code{interactive} specs, but
26329 @vindex gnus-current-prefix-symbol
26330 The current symbolic prefix---the @code{gnus-current-prefix-symbol}
26334 @vindex gnus-current-prefix-symbols
26335 A list of the current symbolic prefixes---the
26336 @code{gnus-current-prefix-symbol} variable.
26339 The current article number---the @code{gnus-summary-article-number}
26343 The current article header---the @code{gnus-summary-article-header}
26347 The current group name---the @code{gnus-group-group-name}
26353 @node Emacs/XEmacs Code
26354 @subsection Emacs/XEmacs Code
26358 While Gnus runs under Emacs, XEmacs and Mule, I decided that one of the
26359 platforms must be the primary one. I chose Emacs. Not because I don't
26360 like XEmacs or Mule, but because it comes first alphabetically.
26362 This means that Gnus will byte-compile under Emacs with nary a warning,
26363 while XEmacs will pump out gigabytes of warnings while byte-compiling.
26364 As I use byte-compilation warnings to help me root out trivial errors in
26365 Gnus, that's very useful.
26367 I've also consistently used Emacs function interfaces, but have used
26368 Gnusey aliases for the functions. To take an example: Emacs defines a
26369 @code{run-at-time} function while XEmacs defines a @code{start-itimer}
26370 function. I then define a function called @code{gnus-run-at-time} that
26371 takes the same parameters as the Emacs @code{run-at-time}. When running
26372 Gnus under Emacs, the former function is just an alias for the latter.
26373 However, when running under XEmacs, the former is an alias for the
26374 following function:
26377 (defun gnus-xmas-run-at-time (time repeat function &rest args)
26381 (,function ,@@args))
26385 This sort of thing has been done for bunches of functions. Gnus does
26386 not redefine any native Emacs functions while running under XEmacs---it
26387 does this @code{defalias} thing with Gnus equivalents instead. Cleaner
26390 In the cases where the XEmacs function interface was obviously cleaner,
26391 I used it instead. For example @code{gnus-region-active-p} is an alias
26392 for @code{region-active-p} in XEmacs, whereas in Emacs it is a function.
26394 Of course, I could have chosen XEmacs as my native platform and done
26395 mapping functions the other way around. But I didn't. The performance
26396 hit these indirections impose on Gnus under XEmacs should be slight.
26399 @node Various File Formats
26400 @subsection Various File Formats
26403 * Active File Format:: Information on articles and groups available.
26404 * Newsgroups File Format:: Group descriptions.
26408 @node Active File Format
26409 @subsubsection Active File Format
26411 The active file lists all groups available on the server in
26412 question. It also lists the highest and lowest current article numbers
26415 Here's an excerpt from a typical active file:
26418 soc.motss 296030 293865 y
26419 alt.binaries.pictures.fractals 3922 3913 n
26420 comp.sources.unix 1605 1593 m
26421 comp.binaries.ibm.pc 5097 5089 y
26422 no.general 1000 900 y
26425 Here's a pseudo-BNF definition of this file:
26428 active = *group-line
26429 group-line = group spc high-number spc low-number spc flag <NEWLINE>
26430 group = <non-white-space string>
26432 high-number = <non-negative integer>
26433 low-number = <positive integer>
26434 flag = "y" / "n" / "m" / "j" / "x" / "=" group
26437 For a full description of this file, see the manual pages for
26438 @samp{innd}, in particular @samp{active(5)}.
26441 @node Newsgroups File Format
26442 @subsubsection Newsgroups File Format
26444 The newsgroups file lists groups along with their descriptions. Not all
26445 groups on the server have to be listed, and not all groups in the file
26446 have to exist on the server. The file is meant purely as information to
26449 The format is quite simple; a group name, a tab, and the description.
26450 Here's the definition:
26454 line = group tab description <NEWLINE>
26455 group = <non-white-space string>
26457 description = <string>
26462 @node Emacs for Heathens
26463 @section Emacs for Heathens
26465 Believe it or not, but some people who use Gnus haven't really used
26466 Emacs much before they embarked on their journey on the Gnus Love Boat.
26467 If you are one of those unfortunates whom ``@kbd{C-M-a}'', ``kill the
26468 region'', and ``set @code{gnus-flargblossen} to an alist where the key
26469 is a regexp that is used for matching on the group name'' are magical
26470 phrases with little or no meaning, then this appendix is for you. If
26471 you are already familiar with Emacs, just ignore this and go fondle your
26475 * Keystrokes:: Entering text and executing commands.
26476 * Emacs Lisp:: The built-in Emacs programming language.
26481 @subsection Keystrokes
26485 Q: What is an experienced Emacs user?
26488 A: A person who wishes that the terminal had pedals.
26491 Yes, when you use Emacs, you are apt to use the control key, the shift
26492 key and the meta key a lot. This is very annoying to some people
26493 (notably @code{vi}le users), and the rest of us just love the hell out
26494 of it. Just give up and submit. Emacs really does stand for
26495 ``Escape-Meta-Alt-Control-Shift'', and not ``Editing Macros'', as you
26496 may have heard from other disreputable sources (like the Emacs author).
26498 The shift keys are normally located near your pinky fingers, and are
26499 normally used to get capital letters and stuff. You probably use it all
26500 the time. The control key is normally marked ``CTRL'' or something like
26501 that. The meta key is, funnily enough, never marked as such on any
26502 keyboard. The one I'm currently at has a key that's marked ``Alt'',
26503 which is the meta key on this keyboard. It's usually located somewhere
26504 to the left hand side of the keyboard, usually on the bottom row.
26506 Now, us Emacs people don't say ``press the meta-control-m key'',
26507 because that's just too inconvenient. We say ``press the @kbd{C-M-m}
26508 key''. @kbd{M-} is the prefix that means ``meta'' and ``C-'' is the
26509 prefix that means ``control''. So ``press @kbd{C-k}'' means ``press
26510 down the control key, and hold it down while you press @kbd{k}''.
26511 ``Press @kbd{C-M-k}'' means ``press down and hold down the meta key and
26512 the control key and then press @kbd{k}''. Simple, ay?
26514 This is somewhat complicated by the fact that not all keyboards have a
26515 meta key. In that case you can use the ``escape'' key. Then @kbd{M-k}
26516 means ``press escape, release escape, press @kbd{k}''. That's much more
26517 work than if you have a meta key, so if that's the case, I respectfully
26518 suggest you get a real keyboard with a meta key. You can't live without
26524 @subsection Emacs Lisp
26526 Emacs is the King of Editors because it's really a Lisp interpreter.
26527 Each and every key you tap runs some Emacs Lisp code snippet, and since
26528 Emacs Lisp is an interpreted language, that means that you can configure
26529 any key to run any arbitrary code. You just, like, do it.
26531 Gnus is written in Emacs Lisp, and is run as a bunch of interpreted
26532 functions. (These are byte-compiled for speed, but it's still
26533 interpreted.) If you decide that you don't like the way Gnus does
26534 certain things, it's trivial to have it do something a different way.
26535 (Well, at least if you know how to write Lisp code.) However, that's
26536 beyond the scope of this manual, so we are simply going to talk about
26537 some common constructs that you normally use in your @file{.emacs} file
26540 If you want to set the variable @code{gnus-florgbnize} to four (4), you
26541 write the following:
26544 (setq gnus-florgbnize 4)
26547 This function (really ``special form'') @code{setq} is the one that can
26548 set a variable to some value. This is really all you need to know. Now
26549 you can go and fill your @file{.emacs} file with lots of these to change
26552 If you have put that thing in your @file{.emacs} file, it will be read
26553 and @code{eval}ed (which is lisp-ese for ``run'') the next time you
26554 start Emacs. If you want to change the variable right away, simply say
26555 @kbd{C-x C-e} after the closing parenthesis. That will @code{eval} the
26556 previous ``form'', which is a simple @code{setq} statement here.
26558 Go ahead---just try it, if you're located at your Emacs. After you
26559 @kbd{C-x C-e}, you will see @samp{4} appear in the echo area, which
26560 is the return value of the form you @code{eval}ed.
26564 If the manual says ``set @code{gnus-read-active-file} to @code{some}'',
26568 (setq gnus-read-active-file 'some)
26571 On the other hand, if the manual says ``set @code{gnus-nntp-server} to
26572 @samp{nntp.ifi.uio.no}'', that means:
26575 (setq gnus-nntp-server "nntp.ifi.uio.no")
26578 So be careful not to mix up strings (the latter) with symbols (the
26579 former). The manual is unambiguous, but it can be confusing.
26582 @include gnus-faq.texi
26602 @c Local Variables:
26604 @c coding: iso-8859-1
26606 % LocalWords: BNF mucho detailmenu cindex kindex kbd
26607 % LocalWords: findex Gnusae vindex dfn dfn samp nntp setq nnspool nntpserver
26608 % LocalWords: nnmbox newusers Blllrph NEWGROUPS dingnusdingnusdingnus
26609 % LocalWords: pre fab rec comp nnslashdot regex ga ga sci nnml nnbabyl nnmh
26610 % LocalWords: nnfolder emph looong eld newsreaders defun init elc pxref