Storage Options for Online/Offline Use

    

In the default configuration, Gravity only stores article headers.  You can configure Gravity to store bodies automatically for all subscribed groups. You do not have to store bodies for all groups, but can configure individual groups.
Tools - Global Options - Storage - Retrieve and Store Article Bodies
This is a global setting. When you use this option, Gravity retrieves the bodies for ALL headers in ALL subscribed groups, unless overridden (see below). This lets you read the group off-line without tagging and retrieving individual articles. The drawback to this mode is that it requires a lot of disk space and online activity. You may need to adjust purge settings to save space.

·         Note that ALL bodies are fetched

·         You do not want to use this option for binary groups

Tools - Global Options - Storage - Store All Bodies Retrieved for Reading
Use this setting to control whether Gravity stores an article in the database when you retrieve it for reading. When this option is enabled, reading an article also stores it in the database.
You can later re-read the article without re-connecting to your news server. It also helps searching with the search window, if you like to search previously read articles, because you can search local bodies. This option also will increase the amount of disk space used and you may need to adjust the purge settings.

Newsgroup Overrides
This option provides much more flexibility than global settings. You can override the global storage settings (or not set a global setting at all) and configure each newsgroup to store bodies or not.

Newsgroup - Properties - General Tab(or right click group pane menu: Properties)
Select the option in "Storage settings for this group"

Rules
Instead of downloading all article bodies, you can try some rules to control which bodies to fetch automatically. If you have a basic understanding of , see this as a starting point.

Manual Body Storage and Rules
If you want total manual control over which bodies are fetched and stored, do not enable body storage  and use the traditional offline "tag and fetch" method. See the Chapter for more information.