This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| message_areas_f3 [2022/04/30 10:29] – admin | message_areas_f3 [2022/05/01 04:40] (current) – admin | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| Squish, JAM, or Fido (.MSG) or a combination of these at the same time! | Squish, JAM, or Fido (.MSG) or a combination of these at the same time! | ||
| - | ProBoard's message base limits are as follows: | + | __ProBoard's message base limits are as follows:__ | 
| - | ────────────────────────────────────────────── | + | |
| - | Message Type Number of Message Areas Maximum File Size | + |  | 
| - | ──────────── | + | Hudson | 
| - | Hudson | + | Squish | 
| - | (all areas combined) | + | Fido *.MSG      10, | 
| - | Squish | + | JAM | 
| - | Fido *.MSG      10, | + | |
| - | available). | + | |
| - | JAM | + | |
| - | available). | + | |
| Each message area in ProBoard has its own name and properties. | Each message area in ProBoard has its own name and properties. | ||
| Line 31: | Line 26: | ||
| < | < | ||
| + | For example, entering the number 10000 will create message area 10000. | ||
| + | Keep in mind that if you are using the HUDSON format for any of your | ||
| + | message areas, that any areas specified to use the HUDSON format will | ||
| + | have to be specified as areas 1 - 200. This is a limit of the existing | ||
| + | HUDSON message base format and is not a limit of ProBoard. | ||
| + | __A message area has the following fields:__ | ||
| + | **Name** | ||
| + | Name of this message area. | ||
| + | **Path** | ||
| - | ───────────────────────────────────────────────────────────────────────────── | + | The path where this Message Area is located. | 
| - | 26 | + | *.MSG, but NOT for Hudson. | 
| - | For example, entering the number 10000 will create | + | **Message Kind** | 
| - | Keep in mind that if you are using the HUDSON format for any of your | + | |
| - | message | + | The kind of message. | 
| - | have to be specified as areas 1 - 200. | + | |
| - | HUDSON | + | * Local (Local messages) | 
| + | * EchoMail (Echomail) | ||
| + | * NetMail (Netmail) | ||
| + | * Pvt EchoMail (Private Echomail) | ||
| + | |||
| + | One word about the difference between the " | ||
| + | " | ||
| + | echomail processor (as specified | ||
| + | Committee). In a "Pvt Echo" area, this restriction is not imposed. | ||
| + | |||
| + | **Message Type** | ||
| + | |||
| + | One of the following: | ||
| + | |||
| + | * **Private only:** Only private messages allowed. | ||
| + | * **Pvt/ | ||
| + | * **Public only:** Only public messages allowed. | ||
| + | * **To All:** This message type should be used in a LOCAL message area only. | ||
| + | |||
| + | The "To All" message type is intended for a SysOp to leave messages to all users. | ||
| + | Any messages entered in this area will considered "To All" regardless of the whom | ||
| + | the " | ||
| + | checks for waiting mail. You may not want to allow users to reply to these messages | ||
| + | since their replies will be sent to all users. | ||
| + | Area" to a different | ||
| + | announcement messages. | ||
| + | |||
| + | **Name Options** | ||
| + | |||
| + | Determines which names can be used to write messages in this area. This can be: | ||
| + | |||
| + | * **Real Names Only:** Obvious I guess | ||
| + | * **Free Alias: | ||
| + | * **Fixed Alias (or real name):** The user can choose between his real name and his alias | ||
| + | * **Fixed Alias (enforced): | ||
| + | |||
| + | It is recommended that areas where aliases are allowed, are made " | ||
| + | |||
| + | **Message Base** | ||
| + | |||
| + | The type of message base to use for this message area. Valid choices are Hudson, | ||
| + | Squish, JAM, and Fido (*.MSG). | ||
| - | A message area has the following fields: | + | Use the < | 
| - | ──────────────────────────────────────── | + | select Hudson that this message area's number (see top bar of the window) should | 
| + | be message area 200 or lower since Hudson only supports up to 200 message areas. | ||
| - | Name ........................ Name of this message area. | + | **Read Level** | 
| - | Path ........................ The path where this Message Area is | + | Security Level needed to read messages in this area. | 
| - | located. | + | |
| - | *.MSG, but NOT for Hudson. | + | |
| - | Message Kind ................ The kind of message. You can have: | + | **Read Flags** | 
| - | - Local .......... Local messages | + | Flags needed to read messages in this area. You can now specify flags that a user MUST | 
| - | - EchoMail | + | NOT have in order to READ from this message area. These flags are shown in reverse. | 
| - | - NetMail | + | To set a reverse flag, press the flag letter twice (it will appear reversed). To | 
| - | - Pvt EchoMail ... Private Echomail | + | clear a reversed flag type the flag letter one more time. | 
| - | One word about the difference between the | + | **Write Level** | 
| - | " | + | |
| - | " | + | |
| - | messages that have been exported by an | + | |
| - | echomail processor (as specified by the | + | |
| - | FTSC, the FidoNet Technical Standards | + | |
| - | Committee). In a "Pvt Echo" area, this | + | |
| - | restriction is not imposed. | + | |
| - | Message Type ................ One of the following: | + | Security Level needed to write messages in this area. | 
| - | - Private only .. Only private messages | + | **Write Flags** | 
| - | allowed. | + | |
| - | - Pvt/ | + | Flags needed to write messages in this area. You can now specify flags that a | 
| - |  | + | user MUST NOT have in order to WRITE to this message area. These flags are shown | 
| + | in reverse. To set a reverse flag, press the flag letter twice (it will appear | ||
| + | reversed). | ||
| - | - Public only ... Only public messages | + | **SysOp Level** | 
| - | allowed. | + | |
| - | - To All ........ This message type | + | Security Level needed to be allowed access to all functions | 
| - | should | + | |
| - | LOCAL message area | + | |
| - | only. | + | |
| - | The "To All" message type is intended for | + | **SysOp Flags** | 
| - | a SysOp to leave messages to all users. | + | |
| - | Any messages entered in this area will | + | |
| - | considered "To All" regardless of the whom | + | |
| - | the " | + | |
| - | in this area will be shown when ProBoard | + | |
| - | checks for waiting mail. You may not want | + | |
| - | to allow users to reply to these messages | + | |
| - | since their replies will be sent to all | + | |
| - | users. | + | |
| - | Area" to a different message area number | + | |
| - | if you decide to let users reply to your | + | |
| - | announcement messages. | + | |
| - | ───────────────────────────────────────────────────────────────────────────── | + | Flags needed to be allowed access to all functions in this message area. | 
| - |  | + | now specify flags that the SysOp MUST NOT have in order to be allowed access | 
| - | Name Options | + | functions | 
| - |  | + | reverse flag, press the flag letter twice (it will appear reversed). | 
| + | reversed flag type the flag letter one more time. | ||
| - | - Real Names Only: | + | **Origin Line** | 
| - |  | + | |
| - | - Free Alias | + | Only for Echomail: if you do not specify this, the default origin line will be used | 
| - | The user can choose any alias he | + | (refer to F1, Site Options, to specify your default origin line). | 
| - |  | + | |
| - | another user. | + | |
| - | - Fixed Alias (or real name) | + | **Use AKA** | 
| - | The user can choose between his real | + | |
| - | name and his alias | + | |
| - | - Fixed Alias (enforced) | + | The network address for this area (for Echomail & Netmail | 
| - | The user can only use his alias to | + | |
| - | write a message | + | |
| - | It is recommended that areas where aliases | + | **EchoMail Tag** | 
| - | are allowed, are made " | + | |
| - | Message Base ................ The type of message base to use for this | + | This field is used by ProBoard to create a file called ECHOTOSS.LOG You should enter | 
| - | message area. Valid choices are Hudson, | + | the Echomail Tag name for this message area (if this message area has the " | 
| - |  | + | Kind" field set to " | 
| + | tag name you specify here will be written to the file ECHOTOSS.LOG in the ProBoard | ||
| + | system directory, causing your mail tosser to scan for outbound mail in this message | ||
| + | area upon the callers logoff. | ||
| - | Use the < | + | **QWK Area Name** | 
| - | available choices. | + | |
| - | select Hudson that this message area' | + | |
| - | number (see top bar of the window) should | + | |
| - | be message area 200 or lower since Hudson | + | |
| - | only supports up to 200 message areas. | + | |
| - | Read Level .................. Security Level needed | + | (Optional) You can enter the name of this area for QWK mail packers. QWK only | 
| - | this area. | + | supports up to 12 characters for area names. | 
| - | Read Flags .................. Flags needed to read messages in this area. | + | **Reply Area** | 
| - | You can now specify flags that a user MUST | + | |
| - | NOT have in order to READ from this message | + | |
| - | area. These flags are shown in reverse. | + | |
| - | To set a reverse flag, press the flag | + | |
| - | letter twice (it will appear reversed). | + | |
| - | clear a reversed flag type the flag letter | + | |
| - | one more time. | + | |
| - | Write Level ................. Security Level needed | + | The area where replies | 
| - | this area. | + | users to reply to " | 
| + | go to the current message | ||
| - | Write Flags ................. Flags needed to write messages in this | + | **SysOp** | 
| - | area. You can now specify flags that a | + | |
| - | user MUST NOT have in order to WRITE to | + | |
| - | this message area. These flags are shown | + | |
| - | in reverse. | + | |
| - | the flag letter twice (it will appear | + | |
| - | reversed). | + | |
| - | the flag letter one more time. | + | |
| - | SysOp Level ................. Security Level needed to be allowed | + | The user name for an " | 
| - | to all functions in this message area. | + | to this message area.  When users write messages to " | 
| + | messages will be sent to the user name specified here. | ||
| + | **Group #1** | ||
| - | ───────────────────────────────────────────────────────────────────────────── | + | The first group number | 
| - |  | + | |
| - | SysOp Flags ................. Flags needed to be allowed access to all | + | |
| - | functions in this message area. You can | + | |
| - | now specify flags that the SysOp MUST NOT | + | |
| - | have in order to be allowed access to all | + | |
| - | functions in this this message area. These | + | |
| - | flags are shown in reverse. | + | |
| - | reverse flag, press the flag letter twice | + | |
| - |  | + | |
| - | reversed flag type the flag letter one more | + | |
| - | time. | + | |
| - | Origin Line ................. Only for Echomail: if you do not specify | + | **Group #2** | 
| - | this, the default origin line will be used | + | |
| - | (refer to F1, Site Options, to specify your | + | |
| - | default origin line). | + | |
| - | Use AKA ..................... | + | The second group number | 
| - | Echomail & Netmail only). | + | |
| - | EchoMail Tag ................ This field is used by ProBoard to create a | + | **Group #3** | 
| - | file called ECHOTOSS.LOG You should enter | + | |
| - | the Echomail Tag name for this message area | + | |
| - | (if this message area has the " | + | |
| - | Kind" field set to " | + | |
| - | user enters a message into this area the | + | |
| - | tag name you specify here will be written | + | |
| - | to the file ECHOTOSS.LOG in the ProBoard | + | |
| - | system directory, causing your mail tosser | + | |
| - | to scan for outbound mail in this message | + | |
| - | area upon the callers logoff. | + | |
| - | QWK Area Name ............... (Optional) You can enter the name of this | + | The third group number | 
| - |  | + | |
| - | supports up to 12 characters for area | + | |
| - | names. | + | |
| - | Reply Area .................. The area where replies to messages in this | + | **Group #4** | 
| - | area should be posted. | + | |
| - | users to reply to " | + | |
| - | this to " | + | |
| - | go to the current message area. | + | |
| - | SysOp ....................... | + | The fourth group number | 
| - | with this name will have full SysOp access | + | |
| - | to this message area. When users write | + | |
| - | messages to " | + | |
| - | messages will be sent to the user name | + | |
| - | specified here. | + | |
| - | Group #1 .................... The first group number this message area | + | **All Groups** | 
| - | belongs to (1-255) if any. | + | |
| - | Group #2 .................... The second group number | + | Does this message area belong | 
| - | belongs | + | toggle between Yes/No. | 
| - | Group #3 .................... The third group number this message area | + | **Kill after <xx> days** | 
| - | belongs to (1-255) if any. | + | |
| - | Group #4 .................... The fourth group number this message | + | When running the PBUTIL message packer with the -D parameter, all messages that have | 
| - | belongs to (1-255) if any. | + | been in the message base for <xx> days will be deleted. This is for both HUDSON and | 
| + | JAM message | ||
| - | ───────────────────────────────────────────────────────────────────────────── | + | **Kill rcvd after <xx> days** | 
| - |  | + | |
| - | All Groups .................. Does this message area belong to all | + | |
| - | message groups? | + | |
| - | toggle between Yes/No. | + | |
| - | Kill after <xx> days ........ | + | When running the PBUTIL message packer with the -D parameter, all messages that have | 
| - |  | + | been received | 
| - | been in the message base for <xx> days will | + | message base formats. | 
| - |  | + | |
| - |  | + | |
| - | Kill rcvd after <xx> days ... When running the PBUTIL message packer with | + | **Max # messages** | 
| - | the -D parameter, all messages | + | |
| - | been received for <xx> days will be | + | |
| - | deleted. | + | |
| - | message base formats. | + | |
| - | Max # messages .............. | + | The maximum number of messages allowed in this area. When this number is exceeded, | 
| - |  | + | PBUTIL MP -D (message pack & delete) will delete the oldest messages from the message | 
| - | PBUTIL MP -D (message pack & delete) will | + | base (Hudson and Squish). | 
| - |  | + | |
| - | base (Hudson and Squish). | + | |