+You should tell those to write the mail to your disk and Gnus to read
+it from there. Last but not least the mail sending part: This can be
+done with every MTA like @uref{http://www.sendmail.org/,sendmail},
+@uref{http://www.qmail.org/,postfix}, @uref{http://www.exim.org/,exim}
+or @uref{http://www.qmail.org/,qmail}.
+
+
+ On windows boxes I'd vote for
+ @uref{http://www.tglsoft.de/,Hamster},
+ it's a small freeware, open-source program which fetches
+ your mail and news from remote servers and offers them
+ to Gnus (or any other mail and/or news reader) via nntp
+ respectively POP3 or IMAP. It also includes a smtp
+ server for receiving mails from Gnus.
+
+@ifnottex
+@node [7.2], [7.3], [7.1], FAQ 7 - Gnus in a dial-up environment
+@end ifnottex
+@subsubheading Question 7.2:
+
+ So what was this thing about the Agent?
+
+
+Answer:
+
+ The Gnus agent is part of Gnus, it allows you to fetch
+ mail and news and store them on disk for reading them
+ later when you're offline. It kind of mimics offline
+ newsreaders like e.g. Forte Agent. If you want to use
+ the Agent place the following in ~/.gnus if you are
+ still using 5.8.8 or 5.9 (it's the default since 5.10):
+
+
+@example
+(setq gnus-agent t)
+@end example
+
+
+ Now you've got to select the servers whose groups can be
+ stored locally. To do this, open the server buffer
+ (that is press @samp{^} while in the
+ group buffer). Now select a server by moving point to
+ the line naming that server. Finally, agentize the
+ server by typing @samp{J a}. If you
+ make a mistake, or change your mind, you can undo this
+ action by typing @samp{J r}. When
+ you're done, type 'q' to return to the group buffer.
+ Now the next time you enter a group on a agentized
+ server, the headers will be stored on disk and read from
+ there the next time you enter the group.
+
+@ifnottex
+@node [7.3], [7.4], [7.2], FAQ 7 - Gnus in a dial-up environment
+@end ifnottex
+@subsubheading Question 7.3:
+
+ I want to store article bodies on disk, too. How to do it?
+
+
+Answer:
+
+ You can tell the agent to automatically fetch the bodies
+ of articles which fulfill certain predicates, this is
+ done in a special buffer which can be reached by
+ saying @samp{J c} in group
+ buffer. Please refer to the documentation for
+ information which predicates are possible and how
+ exactly to do it.
+
+
+ Further on you can tell the agent manually which
+ articles to store on disk. There are two ways to do
+ this: Number one: In the summary buffer, process mark a
+ set of articles that shall be stored in the agent by
+ saying @samp{#} with point over the
+ article and then type @samp{J s}. The
+ other possibility is to set, again in the summary
+ buffer, downloadable (%) marks for the articles you
+ want by typing @samp{@@} with point over
+ the article and then typing @samp{J u}.
+ What's the difference? Well, process marks are erased as
+ soon as you exit the summary buffer while downloadable
+ marks are permanent. You can actually set downloadable
+ marks in several groups then use fetch session ('J s' in
+ the GROUP buffer) to fetch all of those articles. The
+ only downside is that fetch session also fetches all of
+ the headers for every selected group on an agentized
+ server. Depending on the volume of headers, the initial
+ fetch session could take hours.
+
+@ifnottex
+@node [7.4], , [7.3], FAQ 7 - Gnus in a dial-up environment
+@end ifnottex
+@subsubheading Question 7.4:
+
+ How to tell Gnus not to try to send mails / postings
+ while I'm offline?
+
+
+Answer:
+
+ All you've got to do is to tell Gnus when you are online
+ (plugged) and when you are offline (unplugged), the rest
+ works automatically. You can toggle plugged/unplugged
+ state by saying @samp{J j} in group
+ buffer. To start Gnus unplugged say @samp{M-x
+ gnus-unplugged} instead of
+ @samp{M-x gnus}. Note that for this to
+ work, the agent must be active.
+
+
+@ifnottex
+@node FAQ 8 - Getting help, FAQ 9 - Tuning Gnus, FAQ 7 - Gnus in a dial-up environment, Frequently Asked Questions
+@end ifnottex
+@subsection Getting help
+
+@menu
+* [8.1]:: How to find information and help inside Emacs?
+* [8.2]:: I can't find anything in the Gnus manual about X
+ (e.g. attachments, PGP, MIME...), is it not documented?
+* [8.3]:: Which websites should I know?
+* [8.4]:: Which mailing lists and newsgroups are there?
+* [8.5]:: Where to report bugs?
+* [8.6]:: I need real-time help, where to find it?
+@end menu
+
+@ifnottex
+@node [8.1], [8.2], FAQ 8 - Getting help, FAQ 8 - Getting help
+@end ifnottex
+@subsubheading Question 8.1:
+
+ How to find information and help inside Emacs?
+
+
+Answer:
+
+ The first stop should be the Gnus manual (Say
+ @samp{C-h i d m Gnus RET} to start the
+ Gnus manual, then walk through the menus or do a
+ full-text search with @samp{s}). Then
+ there are the general Emacs help commands starting with
+ C-h, type @samp{C-h ? ?} to get a list
+ of all available help commands and their meaning. Finally
+ @samp{M-x apropos-command} lets you
+ search through all available functions and @samp{M-x
+ apropos} searches the bound variables.
+
+@ifnottex
+@node [8.2], [8.3], [8.1], FAQ 8 - Getting help
+@end ifnottex
+@subsubheading Question 8.2:
+
+ I can't find anything in the Gnus manual about X
+ (e.g. attachments, PGP, MIME...), is it not documented?
+
+
+Answer:
+
+ There's not only the Gnus manual but also the manuals
+ for message, emacs-mime, sieve and pgg. Those packages
+ are distributed with Gnus and used by Gnus but aren't
+ really part of core Gnus, so they are documented in
+ different info files, you should have a look in those
+ manuals, too.
+
+@ifnottex
+@node [8.3], [8.4], [8.2], FAQ 8 - Getting help
+@end ifnottex
+@subsubheading Question 8.3:
+
+ Which websites should I know?
+
+
+Answer:
+
+ The two most important ones are the
+ @uref{http://www.gnus.org,official Gnus website}.
+ and it's sister site
+ @uref{http://my.gnus.org,my.gnus.org (MGO)},
+ hosting an archive of lisp snippets, howtos, a (not
+ really finished) tutorial and this FAQ.
+
+
+ Tell me about other sites which are interesting.
+
+@ifnottex
+@node [8.4], [8.5], [8.3], FAQ 8 - Getting help
+@end ifnottex
+@subsubheading Question 8.4:
+
+ Which mailing lists and newsgroups are there?
+
+
+Answer:
+
+ There's the newsgroup gnu.emacs.gnus (pull it from
+ e.g. news.gnus.org) which deals with general questions
+ and the ding mailing list (ding@@gnus.org) dealing with
+ development of Gnus. You can read the ding list via
+ NNTP, too under the name gnus.ding from news.gnus.org.
+
+
+ If you want to stay in the big8,
+ news.software.newssreaders is also read by some Gnus
+ users (but chances for qualified help are much better in
+ the above groups) and if you speak German, there's
+ de.comm.software.gnus.
+
+@ifnottex
+@node [8.5], [8.6], [8.4], FAQ 8 - Getting help
+@end ifnottex
+@subsubheading Question 8.5:
+
+ Where to report bugs?
+
+
+Answer:
+
+Say @samp{M-x gnus-bug}, this will start a message to the
+@email{bugs@@gnus.org,gnus bug mailing list} including information
+about your environment which make it easier to help you.
+
+@ifnottex
+@node [8.6], , [8.5], FAQ 8 - Getting help
+@end ifnottex
+@subsubheading Question 8.6:
+
+ I need real-time help, where to find it?
+
+
+Answer:
+
+ Point your IRC client to irc.my.gnus.org channel
+ #mygnus. Don't be afraid if people there speak German,
+ they are willing and capable of switching to
+ English when people from outside Germany enter.
+
+
+@ifnottex
+@node FAQ 9 - Tuning Gnus, FAQ - Glossary, FAQ 8 - Getting help, Frequently Asked Questions
+@end ifnottex
+@subsection Tuning Gnus
+
+@menu
+* [9.1]:: Starting Gnus is really slow, how to speed it up?
+* [9.2]:: How to speed up the process of entering a group?
+* [9.3]:: Sending mail becomes slower and slower, what's up?
+@end menu
+
+@ifnottex
+@node [9.1], [9.2], FAQ 9 - Tuning Gnus, FAQ 9 - Tuning Gnus
+@end ifnottex
+@subsubheading Question 9.1:
+
+ Starting Gnus is really slow, how to speed it up?
+
+
+Answer:
+
+ The reason for this could be the way Gnus reads it's
+ active file, see the node "The Active File" in the Gnus
+ manual for things you might try to speed the process up.
+ An other idea would be to byte compile your ~/.gnus (say
+ @samp{M-x byte-compile-file RET ~/.gnus
+ RET} to do it). Finally, if you have require
+ statements in your .gnus, you could replace them with
+ eval-after-load, which loads the stuff not at startup
+ time, but when it's needed. Say you've got this in your
+ ~/.gnus:
+
+
+@example
+(require 'message)
+(add-to-list 'message-syntax-checks '(sender . disabled))
+@end example
+
+@noindent
+ then as soon as you start Gnus, message.el is loaded. If
+ you replace it with
+