LANGUAGE {English/ANSI},{English/RIP}


LEVEL3 {}

 NOTE: This and the next six options have no effect if
 Level 4 option MHSACT is set to NO.

 You may want to limit the ability to send MHS messages to
 certain users.  If this is the case, fill this option in
 with the name of a key.  Only users holding the key named
 in this option will be allowed to send MHS messages.

 If you wish everyone to be able to send MHS messages,
 leave this option blank.

MHSKEY {} S 15 Key required to write MHS messages

 You may want to charge users extra for sending MHS
 messages.  The charge you enter here will be added to
 regular E-mail message charges when users write MHS
 messages.

 If you wish to charge users extra for writing MHS messages,
 enter a surcharge here.  If you want to give users credits
 for using MHS, enter a negative number here, or enter zero
 for free MHS use.

MHSCHG {MHS per-message surcharge 0} N -32767 32767

 You may want to limit the ability to include attachments to
 MHS messages to certain users.  If this is the case, fill
 this option in with the name of a key.  Only users holding
 the key named in this option will be allowed to include
 attachments to MHS messages.

 If you wish everyone to be able to include attachments to
 MHS messages, leave this option blank.

MHSATKY {} S 15 Key required for MHS file attachments

 You may want to charge users extra for attaching files to
 MHS messages.  The charge you enter here will be added to
 regular E-mail attachment charges when users write MHS
 messages.

 If you wish to charge users extra for attaching files to
 MHS messages, enter a surcharge here.

MHSATCH {MHS attachment surcharge 0} N -32767 32767

 You may want to charge users attaching files to MHS
 messages on a per-kilobyte basis.  This way, users will be
 charged more for attaching larger files.  The charge you
 enter here will be added to regular E-mail attachment
 charges when users write MHS messages.

 If you wish to charge users per-kilobyte for attaching
 files to MHS messages, enter a surcharge here.

MHSPKCH {MHS attachment per-kbyte surcharge 0} N -32767 32767

 You may want to limit the ability to request return
 receipts for MHS messages to certain users.  If this is the
 case, fill this option in with the name of a key.  Only
 users holding the key named in this option will be allowed
 to request return receipts for MHS messages.

 If you wish everyone to be able to request return receipts
 for MHS messages, leave this option blank.

MHSRRKY {} S 15 Key required for MHS return receipts

 You may want to charge users extra for requesting return
 receipts when sending MHS messages.  The charge you enter
 here will be added to regular E-mail return receipt charges
 when users write MHS messages.

 If you wish to charge users extra for requesting return
 receipts when sending MHS messages, enter a surcharge here.

MHSRRCH {MHS return receipt surcharge 0} N -32767 32767

LEVEL4 {}

 In order to communicate with other systems using GALMHS,
 your system must have an "identifier".  The identifier is
 used to address messages to and from your system.  The
 string is limited to 8 characters.  The first character
 must be alphabetic.  The remaining characters may be
 alphanumeric, "$", "-", or "#".

 If you are using Novell MHS, the identifier you use here
 must exactly match the Gateway name you created when using
 the MHS program.

GTWNME {WORLDGRP} S 8 MHS Gateway Name

 To import messages using GALMHS, the system scans the
 inbound message directories.  This option determines how
 often GALMHS will scan for messages.  Once the presence of
 one or more messages has been detected, the system will
 import all existing messages as fast as possible.  When all
 messages have been processed, the system will revert back
 to scanning for messages at the interval specified by this
 option.  The time unit specified here is seconds.

SCNMHS {Frequency to scan for incoming msgs (seconds): 5} N 5 3600

 It takes the system one "cycle" to make one pass through
 all online users, processing input and output for each.
 GALMHS imports messages into your system a little bit at a
 time -- a little bit each cycle.  Set this option to the
 average length of time you would like each import cycle to
 take.

 The higher this number, the faster messages will be
 imported (thus taking up more system resources). Increase
 this number to speed importing.  Lower it to increase
 online user responsiveness.

MHSIDLY {Time for each import cycle (hundredths of seconds): 10} N 1 100

 If GALMHS cannot import a message, an E-mail message can be
 left to the Sysop, which will give the information about
 the message that could not be imported.

 Answering YES to this option will send the message, and
 answering NO to this option will not send the message.

BADMHS {Send E-mail to Sysop regarding failed MHS import? YES} B

 The GALMHS module can be configured as a message
 importer/exporter in its own right, but it is also used by
 other mail systems to handle their import/export tasks.

 If you wish to enable a generic MHS mail carrier, answer
 YES to this question.  If you do not want a generic MHS
 carrier, but still want the GALMHS module available for use
 by other carriers, answer NO to this question.

MHSACT {Activate generic MHS importer/exporter? NO} B

 In order to identify an address as being sent to a
 particular exporter, each exporter is identified by a
 unique prefix.  This prefix may be two or three characters
 long and consist of letters or numbers only.

 Enter here the prefix you wish the generic MHS exporter to
 be identified by.

MHSPFX {MHS} (MHSACT=YES) S 3 Address prefix for generic MHS exporter

 Each exporter is identified in lists and help messages by a
 name and/or description.

 Enter here the name you wish to use to identify the generic
 MHS exporter.

MHSNAM {Novell MHS} (MHSACT=YES) S 15 Name of generic MHS exporter

 Each exporter is identified in lists and help messages by a
 name and description.

 Enter here the description you wish to use to identify the
 generic MHS exporter.

MHSDSC {Novell Message Handling Service} (MHSACT=YES) S 50 MHS exporter desc.

 In some help messages, users may be shown an example
 address for an exporter.  This example should include the
 prefix specified in MHSPFX and show a typical address with
 proper format for MHS.

MHSXMP {MHS:TStryker@Engr} (MHSACT=YES) S 0 Example MHS address

 Users may request detailed help on specific exporters.
 This message will usually explain how to address a message
 to someone using MHS, who your users can expect to reach,
 and possibly what charges apply to use of MHS, but you are
 free to provide whatever message you think would be most
 helpful.

MHSHLP {
MHS is Novell's standard for moving electronic messages over a network.
Many different E-mail software packages use MHS to transport messages.
Worldgroup also allows you to send and receive messages using MHS.

To send someone a message using MHS, you need their address.  Once you have
their address, you tell the server that this is an MHS address by entering
"%s:" followed by their address.
} (MHSACT=YES) T MHS help message

 The generic MHS exporter requires a directory on the File
 Server hard drive in order to process outbound messages.
 The system will create this directory if needed.  Please
 contact your network administrator to verify that you have
 the proper network permission to do this.  The path name
 you enter here must be a fully qualified directory path.
 For example:

          F:\MHSOUT
          G:\OUTBIN

OUTMSG {} (MHSACT=YES) S 30 Outbound directory for MHS

 The generic MHS exporter requires a directory on the File
 Server hard drive in order to process outbound files.  The
 system will create this directory if needed.  The path name
 you enter here must be a fully qualified directory path.
 For example:

          F:\MHSOUT\PARCEL

 Note:  If you're using Novell MHS (and not some sort of MHS
        emulator), this MUST be the PARCEL directory defined
        under MHS for your gateway.

OUTFIL {} (MHSACT=YES) S 30 Outbound file directory for MHS

 The generic MHS importer requires a directory on the File
 Server hard drive in order to receive inbound messages.
 The system will create this directory if needed.  Please
 contact your network administrator to verify that you have
 the proper network permission to do this.  The path name
 you enter here must be a fully qualified directory path.
 For example:

          F:\MHSIN
          G:\INBIN

INMSG {} (MHSACT=YES) S 30 Inbound directory for MHS

 The generic MHS importer requires a directory on the File
 Server hard drive in order to process inbound files.  The
 system will create this directory if needed.  The path name
 you enter here must be a fully qualified directory path.
 For example:

          F:\MHSIN\PARCEL

 Note:  If you're using Novell MHS (and not some sort of MHS
        emulator), this MUST be the PARCEL directory under
        the INMSG directory.

INFIL {} (MHSACT=YES) S 30 Inbound file directory for MHS


LEVEL6 {}


INVMHS {
The MHS Importer was unable to properly process the following file:

     %s

The file extension ".BAD" has been added to the file name.
} T MHS Warning of .BAD file created


MHSNOD {
     NON-DELIVERY NOTICE
     -------------------

The message you sent on:

%s to %s was undeliverable.
} T MHS Text of non-delivery notice


MHSREC {
     DELIVERY NOTICE
     ---------------

The message you sent on:

%s to %s was successfully delivered.
} T MHS Text of return receipt notice


MHSEML {[0;1;33m***

An E-mail message to you has just been delivered by MHS!
},{
!|10000$STW$|10000$SMF$|10000$SCB$|w0000000010|1C2D32FF6M0|Y00000100
!|1B00000200LC030F000F080700000F07005L00|1U2I38FA6H0000<><>|c00
!|@2R3XAn E-mail message has just been delivered to you by MHS\!
!|@3S4DYou can find it by going to the E-mail Menu.|c0B
!|@2Q3WAn E-mail message has just been delivered to you by MHS\!
!|@3R4CYou can find it by going to the E-mail Menu.
!|1B00000207QQ020F000F080100000F07005L00
!|1U7Z5B9W5X7320<>OK<>`H$RTW$$RMF$$PCB$$RCB$|#|#|#
[0;1;33m} T notify online recipient of E-mail


MHSFOR {[0;1;33m***

A message to you has just been delivered to the %s Forum by MHS!
},{
!|10000$STW$|10000$SMF$|10000$SCB$|w0000000010|1C2D32FF6M0|Y00000100
!|1B00000200LC030F000F080700000F07005L00|1U2I38FA6H0000<><>|c00
!|@2R3XA message to you has just been delivered to the %s Forum by MHS\!
!|@3S4DYou can find it by going to the Forums Menu.|c0B
!|@2Q3WA message to you has just been delivered to the %s Forum by MHS\!
!|@3R4CYou can find it by going to the Forums Menu.
!|1B00000207QQ020F000F080100000F07005L00
!|1U7Z5B9W5X7320<>OK<>`H$RTW$$RMF$$PCB$$RCB$|#|#|#
[0;1;33m} T notify online recipient of Forum message

