[continued from part 1] . . .

MicroPlanet Gravity > Help [F1] > Index > Rules > Rule Tutorial: Fetch
Small Article Bodies Only:

Example: Fetch Small Article Bodies Only
Do Not Fetch Large Article Bodies
This rule is for offline readers or those who download bodies. When you
set Gravity to retrieve article bodies, it fetches *all* bodies. It can
be annoying to get stuck downloading articles with hundreds or even
thousands of lines.
With this rule we create our own conditions to download (small) bodies
and it can work automatically whenever headers are retrieved. We can even
set the rule to act only on certain groups. We will make a basic rule
first, then show how to make it better.
First, before we get into the rule, do NOT store bodies, in Tools -
Global Options - Storage Uncheck "Retrieve and Store Article Bodies", if >checked. If you have set individual newsgroups to store bodies - disable >those too, if applicable.
Tools - Rules
Create (Add) a rule and give it a name;
Condition (adjust the number to suit):
NOT
Lines > 100
Action:
* Retrieve Body
3. Enable this rule to act automatically on all articles (apply to
incoming).
4. (Optionally) Select to which newsgroups the rule should apply on the
General Tab (you do not have to enable a rule for all groups).
Now, when downloading headers, Gravity will automatically evaluate each >article and if the lines count is 100 or less, it will fetch the body.
The larger article's headers will be visible if you want to fetch some of
the larger articles manually.
Or, maybe you don't want it to run automatically (enabled). In that case,
run it manually when you feel like fetching the bodies. Even if you enable >this rule for only certain groups, you can run it manually on *any* group,
or multiple groups, or selected articles only. (Note: if you are offline
and run this rule manually, Gravity may just tag the articles for
download).
Our rule can be better. Maybe we have other rules that mark articles read,
or we have Ignored Thread (why download Ignored articles?). Or maybe we
are on dialup and want to minimize download time. To exclude Ignored >articles, we add more conditions.
Marked as unread
And
(
Not
In an ignored thread
)
And
(
Not
Lines > 100
)
Be aware of rule order in the Main Rule Dialog
This rule should be listed AFTER rules that discard articles or marks them >read, including the "Ignore Thread" rule, so that you don't waste time >downloading article bodies that will only be marked read or deleted.
Also, it should come BEFORE rules that have to act on a BODY condition (so >that the body is present for the rule).
You can add more conditions, such as
And
"From does not contain "Porky"

MicroPlanet Gravity > Help [F1] > Index > Rules > Rules:

Rules
Gravity provides a rule system to automate news reading chores. You can build >rules to mark articles containing certain keywords as important, throw away >articles by authors you don't like, automatically forward articles via e-mail, >decode images in the background, manipulate scores, and handle other chores >automatically.

MicroPlanet Gravity > Help [F1] > Index > Rules > Rules Editor Actions Tab: >Rules Editor Actions Tab

ACTIONS tell Gravity what to do when the Rule Conditions are true.
You can set multiple actions. The rule action(s) can be one or more of the >following:
1. Play a user-selected sound. Specify the directory (in Windows XP the
default Windows sounds are in C:\windows\media, then select the sound.
You can also test it.
2. Show alert - Display a user-provided message (in a pop-up dialog box)
which also indicates the newsgroup containing the matching article.
3. Append the article to a user-selected file (plain text).
4. Forward the article to a user-provided e-mail address. When you use
this condition, you may also have include to the "Retrieve Body" action.
Of course, you must have a valid SMTP server set up also.
5. Mark the article as read/unread.
6. Mark the article as important/normal.
7. Mark the article as protected/deletable.
8. Add XX to the articles score (may be negative).
9. Decode the article (along with related articles in the same post). The
article is decoded even if it is part of a multi-part encoding that
spans multiple articles.
10. Tag the article for retrieval.
11. Retrieve the article's body and store it locally. (If off-line, Gravity
will tag for download)
12. Discard the article. Discard means delete permanently. Be careful with
this.
Be careful when discarding (deleting) articles. If there is a mistake in
the rule, Gravity deletes exactly what it is told without warning!
13. Add the article's thread to the Watch List (see Note below).
14. Add the article's thread to the Ignore List (see Note below).
15. Add the article's author to the Bozo Bin.
Additional Notes:
When using the add to Watch/Ignore Lists, previously downloaded (existing) >articles are not added to the list, only new articles. If you want to
refresh the list so that all articles in the thread are watched/ignored, you >must run the Watch/Ignore rule manually. Similarly, you may have to apply
the bozo bin to the current group manually.

MicroPlanet Gravity > Help [F1] > Index > Rules > Rules Editor Conditions Tab: >Rules Editor - Conditions Tab

Rule CONDITIONS are the criteria that trigger the rule Action(s). You can add >as many conditions as you like. Conditions are combined with boolean logic >(AND, OR, NOT).
Rule Conditions
By default, the rule condition for a new rule is:
No conditions -- always true
(This is an actual condition and the rule will act on every article)
Tip: You can click in the conditions window to edit text directly. You can >also use CTRL-C/V/X to copy, paste, and cut in the window. Remember that the >condition's text must follow certain syntax rules, so this is usually only >useful to make small changes without having to remove and add the entire line >again.
Using Text Conditions
Note that you have options to filter phrases in From, Subject, Headers, and >Bodies. The "headers" are limited to From, Subject, and Message-ID (and date, >which is not very useful).
* Note that there is a "does NOT contain" phrase option for each search
component (Subject, From).
Enter text strings in plain text (no wildcards) or as regular expressions >(PCREs). Plain text entries are not case sensitive. By default, PCREs are >also case insensitive.
* If you use a regular expression, you MUST remember to check the box
"Regular Expression" If you forget, the string will be treated as plain
text.
It is easy to forget the Regular expression check box. You can check yourself >by looking at the Conditions Window; the condition entry should contain "reg. >expr." like this:
Subject contains reg. expr. "(mp)?gravity"
You can use a PCRE in one condition and plain text in another:
Subject contains reg. expr. "(mp)?gravity"
And
From contains "nfn03862@naples.net"
In the above conditions, the first string is used as a regular expression >(contains the phrase "reg. expr.") but the second is plain text.
Adding Conditions
Select a condition and Click "Add Condition" (this step is important).
If you are adding multiple conditions, combine them with AND/OR/NOT like >this:
Subject contains "Gravity"
And
(
From contains "frag"
Or
From contains "nfn03862"
)
Use parentheses for grouping. When your condition is complete, it must be >"well formed"
This means that it must make sense to Gravity. If you forgot the closing >parenthesis in the example above, you will see an error message "Bad >condition expression" You must correct such problems before leaving the >dialog.
"Less Than" Conditions
There is no "Less than" condition if you work with the these rule conditions.
* posted more than xx days ago
* has more than xx lines
* score is more than xx
The solution is to invert the logic with the NOT logical operator in the >logic like this:
Not
Lines > 300
If you are grouping one of these with other conditions, you might need >parentheses like this:
(
Not
Lines > 300
)
Insert From ..
This command button will copy conditions from an existing rule, which can >save time for complex rules that are similar to other rules.
%s (a percent sign and lower case 's')
If you enter the string '%s' in the text box, Gravity will prompt you for a >text string when the rule is activated. The user text will be substituted in >the rule condition. If '%s' is entered as a Regular expression, the user >input will be used as a PCRE. See Rules with User Input for more.
If you use %s in a BODY condition, and run the rule MANUALLY while online, >Gravity will try to fetch the articles, including bodies. The bodies are not >saved after the rule finishes. If you are off-line, Gravity may just tag the >articles for download.
The rule condition types are:
1. The article's subject field does/does not contain a certain phrase.
2. The article's author field does/does not contain a certain phrase.
3. Any of the article's header fields does/does not contain a certain phrase. >4. The article's body does/does not contain a certain phrase.
5. The article is in reply to an earlier article that I wrote.
Note that this only works if Gravity is set to generate the message-ID
(Server - Properties - Posting) and the server or proxy server does not
change the MID.
6. The article has more than x number of lines (Use NOT for less than).
7. The article is cross-posted to more than X groups.
?? Is this true ? - I dont think so - TB When using this condition, make
sure you enable the retrieval of cross-posting information (Server -
Properties - Operation - Include cross-post data when retrieving headers.
8. The article was posted more than x days ago. (Use NOT for less than)
9. The article score is more than x (Use NOT for less than).
10. The article is in the "Watch" list or "Ignore" list. This means the
article subject matches the Watch or Ignore Lists, viewed with View -
Other Windows
11. The article is marked as Watched, Ignored, Read, Important, Tagged for
downloading, etc.
Watch and Ignore may seem redundant with #10. "Article marked as" means
the article is flagged with the Watched graphic or Ignored graphic icon.
Number 10 means the article subject is in one of the Lists. Normally (but
not always) these find the same.

MicroPlanet Gravity > Help [F1] > Index > Rules > Rules Editor General Tab: >Rules Editor General Tab

Use the GENERAL Tab to set the newsgroup(s) to which the rule will apply, and >the expiration, if any.
Newsgroups
Specifies the target Newsgroup(s) for the rule. The options are:
* Rule applies to all newsgroups (global).
* Wildcard specification. Specify multiple groups matching the criteria; e.g.,
alt.binaries.* or comp.*
* Specific newsgroups. If you select this, you can add group to the right pane.
Expiration
Select whether you want the rule to never expire, or the number of days when >it should be disabled, if there is no rule activity.

[end part 2; see part 3 for continuation]

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)