Mercurial > noffle
view docs/FAQ @ 494:372f8b55506e noffle
[svn] Apply patch from Jan De Luyck. Add new option 'add-messageid-if-missing',
which optionally postpones adding a message ID to the upstream server.
If this is done, post-locally must be off.
This is to deal with an upstream server troubling Jan. It usually (but
not always) rejects posts with a Noffle message ID.
I have changed Jan's original option of 'add-message-id-if-missing'
for consistency with 'replace-messageid' and added the manual page entry.
See SourceForge feature request 1513395.
| author | bears |
|---|---|
| date | Wed, 12 Jul 2006 20:26:41 +0100 |
| parents | 5d32ceec7f25 |
| children |
line wrap: on
line source
------------------------------------------------------------------------------- NOFFLE FAQ ------------------------------------------------------------------------------- Q: What is the difference between NOFFLE and leafnode? A: NOFFLE uses less resources (disk space and bandwidth). Downloading groups in overview mode is several times faster, because it uses the XOVER command instead of HEAD. In addition, there is the quasi-transparent mode, when online, which allows to browse through groups and cache everything without subscribing. NOFFLE is GPLed, leafnode isn't. ------------------------------------------------------------------------------- Q: I subscribe to groups, but get a "Retreiving failed" message for every requested article. A: Some news server do not allow retrieving articles by message-ID. You cannot use NOFFLE together with these servers presently. ------------------------------------------------------------------------------- Q: I changed the server in the config files, but the new groups do not appear. A: You should run 'noffle --query groups' again. If you want all old group information deleted, you should remove the file data/groupinfo.gdbm in the spool directory before. ------------------------------------------------------------------------------- Q: The Emacs news reader GNUS hangs while getting active list from server. A: This is a known phenomena and I believe that it is a bug with GNUS, because the log files show correct handling of client commands by noffle. ------------------------------------------------------------------------------- Q: What is the NOFFLE 'online' mode? A: NOFFLE can be optionally switched into 'online' mode. When in online mode any newsgroup can be read and the selected articles are fetched immediately from the remote server if not present locally. Regardless of the settings in noffle.conf, NOFFLE will not automatically subscribe to any newsgroup when in online mode. Online mode is therefore useful for quickly sampling the content of potentially interesting newsgroups. To enter online mode, run 'noffle --online'. To return the regular offline mode, run 'noffle --offline'. If you net connection is via dial-up, you may find it convenient to do this in your ip-up and ip-down scripts, though if you do you'll have to remember that NOFFLE's behaviour will be subtly different when you are dialled out. ------------------------------------------------------------------------------- Q: Can I read any article in 'online' mode? A: No. You cannot read groups that are not known to NOFFLE, or articles that NOFFLE has already expired. NOFFLE will not refetch expired articles. ------------------------------------------------------------------------------- Q: What are the possible values of the X-NOFFLE-Status: header that Noffle adds to messages? A: The X-NOFFLE-Status: header can contain one, two or all of the following, separated by spaces: INTERESTING - This message has been read, or a message referencing it has been read and the group is in 'thread' more. The full message body should be downloaded on the next fetch, if it has not been downloaded already. NOT_DOWNLOADED - The article has not yet been downloaded. RETRIEVING_FAILED - An attempt was made to retrieve the article from upstream, but the attempt failed.