menu_commands
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
menu_commands [2019/03/30 03:02] – [INTERNET RELATED] avon | menu_commands [2019/03/30 03:04] – [MESSAGE BASES] avon | ||
---|---|---|---|
Line 471: | Line 471: | ||
**MN - Scan for New Messages** | **MN - Scan for New Messages** | ||
- | Data: /G /P /M /NOLR /NOFROM /NOREAD | + | |
- | | + | |
- | | + | |
- | | + | for modifiers to the default behavior. |
- | | + | is provided, Mystic will scan for all new messages in the user's current |
+ | message group. | ||
- | If /P is provided in optional data, Mystic will only scan for personal | + | |
- | | + | messages (messages From or To the user) |
- | If /G is provided in optional data, Mystic will scan all message bases | + | |
- | | + | in all groups. |
- | If /M is provided in optional data, Mystic will forced the user to read | + | |
- | | + | the new messages (mandatory read). |
+ | |||
+ | If /NOLR is provided, Mystic will not update the user's "last read" | ||
+ | message when performing the scan. | ||
- | If /NOLR is provided, Mystic will not update | + | The following commands augment |
- | | + | option: |
- | The following commands augment | + | If /NOFROM is provided, Mystic will only look at the To field when |
- | | + | scanning for new personal messages (instead |
- | If /NOFROM is provided, Mystic will only look at the To field when | + | |
- | | + | flagged as " |
- | + | ||
- | If /NOREAD is provided, Mystic will not show messages that have been | + | |
- | | + | |
**MX - Post text file to message base** | **MX - Post text file to message base** | ||
- | Data: < | + | |
- | | + | |
- | | + | |
- | | + | a file up to 10,000 lines to be posted and will automatically split |
- | | + | them into multiple posts of 1000 lines each if the post is more than |
- | | + | 1000 lines (including automatically appending a message count to the |
- | + | end of the subject ie: (1 of 3)" | |
- | If you want to post an ANSI file, it should be saved with a 79 column | + | |
- | width using a capable ANSI editor. | + | |
- | can save an ANSI file properly formatted for message posting by | + | |
- | | + | |
- | The optional data field is required for this to work, except for the | + | If you want to post an ANSI file, it should be saved with a 79 column |
- | | + | width using a capable ANSI editor. |
- | NetMail base. | + | can save an ANSI file properly formatted for message posting |
+ | specifying | ||
- | The < | + | The optional data field is required for this to work, except for the |
- | | + | Network Address field which is only required if you are posting to a |
- | | + | NetMail base. Each value should be separated by a semi-colon (;). |
+ | |||
+ | | ||
+ | should be a text file with up to 79 columns per line and up to 10,000 | ||
+ | lines. | ||
- | The <Base ID> is the Message Base ID as found in the Message Base Editor | + | |
- | < | + | |
- | | + | |
- | | + | <To> The To field of the message |
- | < | + | |
- | [Network Address] is the To network address used when posting to a | + | |
- | | + | NetMail base. This field can be excluded when not posting Netmail. |
- | Examples: | + | |
- | c: | + | |
- | | + | c: |
menu_commands.txt · Last modified: 2023/01/20 02:39 by g00r00