Vista Dictionary Viewer

STANDARD DATA DICTIONARY #4.3 -- MAILMAN SITE PARAMETERS FILE 9/29/25 PAGE 1
STORED IN ^XMB(1, (1 ENTRY) SITE: WWW.BMIRWIN.COM UCI: VISTA,VISTA (VERSION 8.0)

DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
-----------------------------------------------------------------------------------------------------------------------------------
This file holds the site parameters for MailMan. It may have only one entry - the domain name of the installation site. Some
parameters are defined by the systems manager during installation. Others may be edited subsequent to installation. The parent
domain, set to FORUM during initialization, may be changed. Audit parameters may be established.

DD ACCESS: @
RD ACCESS: #
WR ACCESS: #
DEL ACCESS: #
LAYGO ACCESS: #

APPLICATION GROUP(S): XM

CROSS
REFERENCED BY: TIME ZONE(AC), DOMAIN NAME(AD), PARENT(AE), DOMAIN NAME(AF), TIME ZONE(AG), DOMAIN NAME(B)

LAST MODIFIED: JUN 14,2024@11:26:34

4.3,.001 NUMBER NUMBER

INPUT TRANSFORM: K:+X'=X!(X>1)!(X<1)!(X?.E1"."1N.N) X
LAST EDITED: DEC 17, 1985
HELP-PROMPT: TYPE A WHOLE NUMBER BETWEEN 1 AND 1
DESCRIPTION:
Used to have VA fileman only have one entry in the file.

4.3,.01 DOMAIN NAME 0;1 POINTER TO DOMAIN FILE (#4.2) (Required) (audited)

INPUT TRANSFORM: S DINUM=1
LAST EDITED: JUN 14, 2024
DESCRIPTION: This is the name of this installation of MailMan, as it is known to the rest of the network. It
must appear in the DOMAIN file. This name applies to all CPUs or Volume sets which access this
^XMB global.

AUDIT: YES, ALWAYS
DELETE TEST: .01,0)= I 1

NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER

CROSS-REFERENCE: 4.3^B
1)= S ^XMB(1,"B",$E(X,1,30),DA)=""
2)= K ^XMB(1,"B",$E(X,1,30),DA)

CROSS-REFERENCE: 4.3^AD^MUMPS
1)= S ^XMB("NUM")=X
2)= K ^XMB("NUM")
This cross reference is used to record the pointer to the domain that is the name of the local
site.

CROSS-REFERENCE: 4.3^AF^MUMPS
1)= I $D(^DIC(4.2,+X,0)) S (^XMB("NAME"),^XMB("NETNAME"))=$P(^DIC(4.2,+X,0),"^")
2)= K ^XMB("NAME"),^XMB("NETNAME")
This cross reference is used to record the human readable name of the local site's identity.

4.3,1 TIME ZONE 0;2 POINTER TO MAILMAN TIME ZONE FILE (#4.4) (Required) (audited)

LAST EDITED: JUN 14, 2024
HELP-PROMPT: Enter the time zone of this domain.
DESCRIPTION: This field defines the timezone in which this domain is located. Note that Standard and Daylight
savings times are considered two different timezones, requiring that the timezone be changed with
the changing of daylight savings. The timezones are located in the MailMan timezone file. The
values of the cross references on this field are appended to message dates as they are sent over
the network.

AUDIT: YES, ALWAYS
CROSS-REFERENCE: 4.3^AC^MUMPS
1)= S ^XMB("TIMEZONE")=$P(^XMB(4.4,X,0),U)
2)= K ^XMB("TIMEZONE")
This cross reference is used to record the name of the timezone that is the correct time zone for
the local site.

CROSS-REFERENCE: 4.3^AG^MUMPS
1)= S ^XMB("TIMEDIFF")=$$TIMEDIFF^XMXUTIL1($P(^XMB(4.4,X,0),U,3))
2)= K ^XMB("TIMEDIFF")
This cross reference records the time difference, in standard internet format, between this time
zone and GMT.

For example, +0800 means 8 hours ahead of GMT.
-0130 means 1 1/2 hours behind GMT.

4.3,2 SUBORDINATE DOMAIN 1;0 POINTER Multiple #4.31

DESCRIPTION: This field is not currently used. This field describes the domains which are subordinate to this
one; that is, those domains which consider this domain a parent.

4.31,.01 SUBORDINATE DOMAIN 0;1 POINTER TO DOMAIN FILE (#4.2) (Multiply asked)

HELP-PROMPT: This is a list of all domains which consider this domain a parent
DESCRIPTION: This field is not currently used. This is a domain which is subordinate to this local MailMan
domain, i.e. a domain which considers this local domain a "parent".

4.31,1 DATE CHRISTENED 0;2 DATE

INPUT TRANSFORM: S %DT="ET" D ^%DT S X=Y K:Y<1 X
HELP-PROMPT: Date on which this subordinate domain was christened..
DESCRIPTION: This field is not currently used. This field holds the date and time on which this subordinate
domain was accepted by this domain. It is controlled automatically by the MailMan christening
operation.

4.31,2 CHRISTENED BY 0;3 POINTER TO NEW PERSON FILE (#200)

LAST EDITED: JUN 18, 1991
DESCRIPTION: This field is not currently used. This field holds the name of the user who performed the
christening operation on this subordinate domain.

4.3,3 PARENT 0;3 POINTER TO DOMAIN FILE (#4.2)

INPUT TRANSFORM: S DIC("S")="I +Y'=^XMB(""NUM"")" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
LAST EDITED: JAN 24, 2001
DESCRIPTION: This field holds the name of the domain which is considered the parent of this domain. The parent
domain's subordinate domain list will contain this domain, also.

Parent domains are used for routing messages when a subordinate domain does not know a direct path
to the selected domain.

Domains are connected to their parents as follows:

1. The local domain is named. 2. The parent is named at the local site. 3. A script from the
parent to the subordinate domain is created. 4. A christening operation is performed by the
parent domain.
When the subordinate domain is christened, the domain is connected
to the network. (Mail may be addressed to remote domains)

SCREEN: S DIC("S")="I +Y'=^XMB(""NUM"")"
EXPLANATION: Parent may not be the site itself.
CROSS-REFERENCE: 4.3^AE^MUMPS
1)= S ^XMB("PARENT")=X
2)= K ^XMB("PARENT")
This cross reference is used to record the IEN of the domain that is the Parent of the local site.

4.3,4 DATE CHRISTENED 0;4 DATE

INPUT TRANSFORM: S %DT="ET" D ^%DT S X=Y K:Y<1 X
HELP-PROMPT: Date on which this domain was christened by its parent.
DESCRIPTION:
This holds the date on which this local domain was christened by its parent domain.

4.3,4.301 NO-PURGE DAYS BUFFER .14;1 NUMBER

INPUT TRANSFORM: K:+X'=X!(X>5)!(X<2)!(X?.E1"."1N.N) X
LAST EDITED: SEP 18, 1998
HELP-PROMPT: Type a Number between 2 and 5, 0 Decimal Digits
DESCRIPTION: This field is used by the unreferenced messages purge to avoid purging the last few days worth of
messages in the message file. It should be a number sufficiently high so as to avoid purging
messages which are in danger of being purged before they can be delivered. This includes incoming
network mail messages. The minimum (and default if this field is null) is two days.

For example, if this field is 2, then messages up to and including those whose local create date is
2 days ago are subject to possible purge.

4.3,4.302 PURGE AUDIT .1;0 DATE Multiple #4.302

LAST EDITED: JAN 23, 1998
DESCRIPTION: This multiple contains a history of Message file purges. Generally, a record of the last 20 purges
is kept.

MailMan has two ways to purge messages. The option XMAUTOPURGE is generally run after XMCLEAN (the
waste basket cleaner) and will purge any messages that are not pointed at by any recipients nor the
sender. The option XMPURGE-BY-DATE can also be run to purge messages that have an origination date
older than one used to initiate the process. It is recommended that before XMPURGE-BY-DATE is
used, users be notified of the proposed purge date so they have a chance to preserve important
texts. These are the only options that actually kill off entries in the message file. The XMPURGE
option does the same thing as XMAUTOPURGE, but is meant to be run in foreground and displays data
as it proceeds.

Unlike XMPURGE and XMAUTOPURGE, which only remove messages that no one holds in their mail baskets
any more, XMPURGE-BY-DATE will remove messages from users' mail baskets and then delete them from
the message file (3.9).

4.302,.01 PURGE DATE 0;1 DATE

INPUT TRANSFORM: S %DT="ESTX" D ^%DT S X=Y K:Y<1 X
LAST EDITED: JAN 23, 1998
HELP-PROMPT: Enter the purge date you are interested in.
DESCRIPTION:
This is a date on which one of the purges ran.

CROSS-REFERENCE: 4.302^B
1)= S ^XMB(1,DA(1),.1,"B",$E(X,1,30),DA)=""
2)= K ^XMB(1,DA(1),.1,"B",$E(X,1,30),DA)

4.302,1 REMAINING MESSAGES 0;2 NUMBER

INPUT TRANSFORM: K:+X'=X!(X>99999999)!(X<0)!(X?.E1"."1N.N) X
LAST EDITED: JAN 23, 1998
HELP-PROMPT: Type a Number between 0 and 99999999, 0 Decimal Digits
DESCRIPTION:
This is the number of messages that remained on file after the purge ran.

4.302,2 PURGED MESSAGES 0;3 NUMBER

INPUT TRANSFORM: K:+X'=X!(X>99999999)!(X<0)!(X?.E1"."1N.N) X
LAST EDITED: JUL 26, 1989
HELP-PROMPT: Type a Number between 0 and 99999999, 0 Decimal Digits
DESCRIPTION:
This is the number of messages that were purged.

4.302,3 START PURGE DATE 0;4 DATE

INPUT TRANSFORM: S %DT="EX" D ^%DT S X=Y K:Y<1 X
LAST EDITED: SEP 16, 1998
HELP-PROMPT: Enter the date at which you wish processing to start.
DESCRIPTION: This is the date entered by the user. It refers to the starting date of the purge process for
unreferenced messages. All unreferenced messages sent on or after this date (and on or before
the ending date) are subject to purge.

4.302,4 STOP PURGE DATE 0;5 DATE

INPUT TRANSFORM: S %DT="EX" D ^%DT S X=Y K:Y<1 X
LAST EDITED: SEP 16, 1998
HELP-PROMPT: Enter the date after which you wish processing to stop.
DESCRIPTION: This is the date entered by the user. It refers to the ending date of the purge process for
unreferenced messages. All unreferenced messages sent on or before this date (and on or after
the starting date) are subject to purge.

4.302,5 PURGE TYPE 0;6 SET

'1' FOR DATE PURGE;
'0' FOR UNREFERENCED MESSAGES PURGE;
LAST EDITED: JAN 23, 1998
HELP-PROMPT: Which type of purge is this?
DESCRIPTION:
There are purges of unreferenced messages and there are date purges.

4.302,6 PURGE MESSAGES OLDER THAN DATE 0;7 DATE

INPUT TRANSFORM: S %DT="EX" D ^%DT S X=Y K:Y<1 X
LAST EDITED: SEP 16, 1998
DESCRIPTION: This field is used during date purges and unreferenced message purges.

During date purges, messages older than this date are purged from the Message file.

During unreferenced message purges, unreferenced messages are purged if they were created on or
before the purge end date. However, messages which originated locally and were sent to remote
sites are not purged if they were created on or after this date. This is to give the remote
sites some time to reply to the unreferenced message.

4.302,7 LAST UPDATE 0;8 DATE

INPUT TRANSFORM: S %DT="ESTX" D ^%DT S X=Y K:Y<1 X
LAST EDITED: JAN 25, 1990
DESCRIPTION: This is the date & time of the last update by the process. It, along with the LAST DATE
PROCESSED field, should indicate to the user that the task is progressing as it is checked and
changes during the process.

4.302,8 LAST DATE PROCESSED 0;9 DATE

INPUT TRANSFORM: S %DT="EX" D ^%DT S X=Y K:Y<1 X
LAST EDITED: SEP 16, 1998
DESCRIPTION: This field is updated during the date purge. It is the local create date of the last message
actually processed when the update was made to the progress data which also includes the
date/time of the update.

4.3,4.303 AUTOMATIC INTEGRITY CHECK .12;1 SET

'0' FOR YES;
'1' FOR NO;
LAST EDITED: MAY 20, 1991
HELP-PROMPT: Enter 'Y' if you wish to run the integrity checker, 'N' if you do not wish to run the Integrity
Checker (before the XMAUTOPURGE).
DESCRIPTION: XMAUTOPURGE is generally run at least once a week at most sites. It is the process that purges
messages that are no longer referenced. Before it is run, XMCLEAN is generally run. XMCLEAN
removes messages from WASTE baskets so that they will be unreferenced when XMAUTOPURGE comes along.
XMAUTOPURGE kicks off the part of XMUTCHECKFILE that checks the Mail Box file. XMUTCHECKFILE also
resets and cleans up the x-refs of this file. If your system has had fairly clean runs of
XMUTCHECKFILE or if the entire XMUTCHECKFILE process is run regularly as a separate process, it is
not necessary for XMAUTOPURGE to run any part of it again.

TECHNICAL DESCR: If this field is set to nill or other value that can be evaluated to zero (+field=zero), then
XMUTCHECKFIL is called to check MailBoxes and recreate the X-ref that the XMAUTOPURGE uses to
verify that a message is no longer referenced by anyone. If it is set to 1, then this call to
XMUTCHECKFIL is skipped.

4.3,4.304 WEEKDAY DAYS TO PURGE NOTOPURGE;1 NUMBER

INPUT TRANSFORM: K:+X'=X!(X>999)!(X<30)!(X?.E1"."1N.N) X
LAST EDITED: SEP 17, 1998
HELP-PROMPT: Type a Number between 30 and 999, 0 Decimal Digits
DESCRIPTION: When the unreferenced messages purge runs, it purges messages from the message file, ^XMB(3.9,
which are no longer referenced, meaning they aren't in anyone's mailbox.

If this field is null, OR if the purge is run on Saturday, the purge starts at the beginning of the
message file.

If this field has a value, AND the purge is run on Sunday through Friday, the purge starts at the
message create date calculated by subtracting the number of days from today's date.

So, if this number is 45, the unreferenced message purge would start with messages created 45 days
ago, and work from there forward.

4.3,5 SHOW INSTITUTION IN MAILMAN? 0;5 SET

'y' FOR YES;
'n' FOR NO;
HELP-PROMPT: If yes, then the user's institution code will be displayed.
DESCRIPTION: This field controls whether mailman will show the user's organization after his name. This is
useful when MailMan has many remote users, who may not know each other's location or affiliation.

4.3,5.1 MESSAGE ACTION DEFAULT 0;15 SET

'I' FOR IGNORE;
'D' FOR DELETE;
LAST EDITED: DEC 06, 1990
DESCRIPTION: This is the default for the user prompt, "Message Action". The user may over-ride this default by
selecting his own under "Edit User Options".

4.3,5.11 COPY LIMIT - RECIPIENTS .11;1 NUMBER

INPUT TRANSFORM: K:+X'=X!(X>99999)!(X<1)!(X?.E1"."1N.N) X
LAST EDITED: JAN 23, 1998
HELP-PROMPT: Type a Number between 1 and 99999, 0 Decimal Digits
DESCRIPTION: This field enables site management to control whether a message with more than a certain number of
recipients may be copied. A user may not copy a message which has more than this number of
recipients. If this field is null, then the limit is 2999.

4.3,5.12 COPY LIMIT - RESPONSES .11;2 NUMBER

INPUT TRANSFORM: K:+X'=X!(X>9999)!(X<0)!(X?.E1"."1N.N) X
LAST EDITED: JAN 23, 1998
HELP-PROMPT: Type a Number between 0 and 9999, 0 Decimal Digits
DESCRIPTION: This field enables site management to limit the number of responses to a message that may be
copied. A user may not copy more than this number of responses to a message. If this field is
null, then the limit is 99.

4.3,5.13 COPY LIMIT - LINES .11;3 NUMBER

INPUT TRANSFORM: K:+X'=X!(X>9999999)!(X<99)!(X?.E1"."1N.N) X
LAST EDITED: JAN 23, 1998
HELP-PROMPT: Type a Number between 99 and 9999999, 0 Decimal Digits
DESCRIPTION: This field enables site management to limit the number of lines that may be copied from a message
and its responses. A user may not copy more than this number of message lines. If this field is
null, then the limit is 3999.

4.3,7 REQUIRE INTRODUCTIONS? 0;6 SET

'y' FOR YES;
'n' FOR NO;
LAST EDITED: JAN 23, 1998
HELP-PROMPT: Are users required to enter introductory text about themselves to the MailMan system?
DESCRIPTION: If this is turned on, then users must introduce themselves when they first log in to MailMan. This
forces users to describe themselves, and enter their phone numbers and addresses for others to
query with the HELP options in MailMan.

4.3,7.01 FWD TEST MESSAGE TO POSTMASTER FORWARD;1 SET

'1' FOR NO;
'0' FOR YES;
LAST EDITED: DEC 28, 1992
HELP-PROMPT: Enter NO (or 1) to not send test messages about forwarding addresses to the Postmaster.
DESCRIPTION: Messages are sent automatically to a user's forwarding address if he changes it. If you want these
messages to be sent to the Postmaster, also, so that he is aware that the forwarding addresses are
proper mark this field with "YES".

4.3,7.2 BIG GROUP SIZE 0;7 NUMBER

INPUT TRANSFORM: K:+X'=X!(X>10000)!(X<50)!(X?.E1"."1N.N) X
LAST EDITED: APR 24, 2002
HELP-PROMPT: Type a Number between 50 and 10000, 0 Decimal Digits
DESCRIPTION: During message addressing, when a user addresses a message to a mail group with a lot of members,
it can seem to take forever to process the group. (Dots of death!) This field, BIG GROUP SIZE,
can help.

IF you enter a number in this field, AND
- If the group contains member groups
or - If the group contains distribution lists
or - If the number of local members plus the number of remote members exceeds or equals the BIG
GROUP SIZE boundary

THEN the user is asked whether s/he wants to queue the group for later delivery, and avoid waiting
while the group is processed.

The user is also warned that if s/he chooses to queue delivery, then recipients may not be
'minus'ed from the group.

If the user chooses not to queue delivery, then processing proceeds in the foreground, as usual.

If the user chooses to queue delivery, then s/he is asked when the delivery should take place. The
group is then queued for processing and delivery at the specified time (by the same background job
which 'news' messages).

There is no default. (If BIG GROUP SIZE equates to zero, then groups are processed in the
foreground as usual.)

4.3,7.3 SHOW DUZ WHEN ADDRESS MESSAGE 0;8 SET

'0' FOR NO;
'1' FOR YES;
LAST EDITED: APR 24, 2002
DESCRIPTION: When someone addresses a message to a local user, should the DUZ of the local user be displayed?

(If this field is null, the default answer is "no".)

Disadvantages:
- Your site's DUZs may be SSNs. They should not be displayed.
- Users may be confused by the display.

Advantages:
- A DUZ is unique, whereas some users may share the same or very similar name. If a user knows
the addressee's DUZ, the DUZ may be used to address a message, instead of the name.

4.3,7.4 SHOW ADDRESS ON USER LOOKUP 0;10 SET

'0' FOR NO;
'1' FOR YES;
LAST EDITED: MAY 11, 1999
HELP-PROMPT: Should the user's address be displayed in a MailMan lookup?
DESCRIPTION: Option XMHELPUSER displays user information. Among the items displayed are the address fields
(.111 through .116) from the NEW PERSON file.

Some sites have home address information in these fields, which should not be displayed.

If the address fields should be displayed, answer YES; otherwise, answer NO. If this field is
null, the default answer is NO.

4.3,7.5 CPU (UCI,VOL) FOR FILER TO RUN 0;12 FREE TEXT

INPUT TRANSFORM: K:$L(X)>30!($L(X)<3) X
LAST EDITED: JAN 22, 1998
HELP-PROMPT: Answer must be 3-30 characters in length.
DESCRIPTION: Enter the UCI,VOL of where you want the background filer routines to run. It is recommended that
the XMB global also reside in this location. If you are unsure what to enter, leave this field
blank.

4.3,7.6 FTP ADDRESS FOR BLOB FTP-GET;1 FREE TEXT

INPUT TRANSFORM: K:'($$VALIDATE^XLFIPV(X)) X
LAST EDITED: AUG 13, 2015
HELP-PROMPT: Enter a valid IP address in the form: nn.nn.nn.nn (IPv4) or hhhh:hhhh:hhhh:hhhh:hhhh:hhhh:hhhh:hhhh
(IPv6)
DESCRIPTION: If your images are on a network that is available via FTP from your main node and you have no other
way of accessing those message to get them onto you main node so that you can FTP them to other
sites, put the IP address of the machine that you will GET your images from into this field.

NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER

4.3,7.7 FTP RECEIVE DIRECTORY DISK/VOL;1 FREE TEXT

INPUT TRANSFORM: K:$L(X)>90!($L(X)<3) X
LAST EDITED: FEB 25, 1994
HELP-PROMPT: Answer must be 3-90 characters in length.
DESCRIPTION: This field is used to store the path for BLOBs to be received in. It is communicated to the
transmitter of messages containing BLOBS so that they can be FTP'd to the correct directory once
the disk has been designated with field 7.711.

If the receiving system is a DOS system the disk portion of the path is in the field 'FTP RECEIVE
DISK'.

TECHNICAL DESCR:

4.3,7.71 FTP RECEIVE NETWORK LOCATION FTPNETLOC;1 FREE TEXT

INPUT TRANSFORM: K:$L(X)>30!($L(X)<3) X
LAST EDITED: APR 26, 1993
HELP-PROMPT: Answer must be 3-30 characters in length.
DESCRIPTION: This field should be the name of an entry in your 2005.2 file (Network Location). It maps where
incoming BLOBs will be placed and is the logical equivalent of field 7.7.

TECHNICAL DESCR:

4.3,7.711 FTP RECEIVE DISK FTPRCVDISK;1 FREE TEXT

INPUT TRANSFORM: K:$L(X)>30!($L(X)<2) X
LAST EDITED: APR 26, 1993
HELP-PROMPT: Answer must be 2-30 characters in length.
DESCRIPTION: This field contains the name of the physical disk that the FTP Receive Network Location is on if
the receiving system is a DOS system.

4.3,7.72 FTP ADDRESS FOR BLOB RECEIVE FTP-RCV;1 FREE TEXT

INPUT TRANSFORM: K:'($$VALIDATE^XLFIPV(X)) X
LAST EDITED: AUG 13, 2015
HELP-PROMPT: Enter a valid IP address in the form: nn.nn.nn.nn (IPv4) or hhhh:hhhh:hhhh:hhhh:hhhh:hhhh:hhhh:hhhh
(IPv6)
DESCRIPTION: This is the IP address that you will advertise to other sites that wish to send you images that
attach to multimedia messages.

NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER

4.3,7.73 FTP USERNAME FTPUSER;1 FREE TEXT

INPUT TRANSFORM: K:$L(X)>30!($L(X)<3) X
LAST EDITED: APR 23, 1993
HELP-PROMPT: Answer must be 3-30 characters in length.
DESCRIPTION:
This is the VMS username that the sender will be told to use when he FTP's BLOBs to this domain.

4.3,7.731 FTP PASSWORD FTPPWD;1 FREE TEXT

INPUT TRANSFORM: K:$L(X)>30!($L(X)<3) X
LAST EDITED: APR 23, 1993
HELP-PROMPT: Answer must be 3-30 characters in length.
DESCRIPTION:
This is the password if any that a BLOB sender needs to have when he FTPs into the system.

4.3,7.7999 FTP NOTES FTP-NOTES;0 WORD-PROCESSING #4.37 (NOWRAP)

DESCRIPTION:
This field holds site specific notes for this site on FTP operations. It is not used by MailMan.

LAST EDITED: JUN 16, 1993
HELP-PROMPT: Put special notes revelant to the FTP operations of this site.
DESCRIPTION:
See above.

4.3,8.11 LPC CHECKSUM LPC;E1,245 MUMPS

INPUT TRANSFORM: K:$L(X)>245 X D:$D(X) ^DIM
LAST EDITED: MAR 10, 1989
HELP-PROMPT: This is Standard MUMPS code used by network mail to calculate checksums.
DESCRIPTION: The code in this field will be obsolete after installation of KERNEL 6, if the "LPC" node in ^%ZOSF
[^%ZOSF("LPC")] is defined. This field is inserted by the MailMan POST-init if the ^%ZOSF("OS") is
defined, contains "DSM" and does not contain "VAX". This is because of a situation that exists
where DSM for PDP-aa series used to use on $ZCALL anbd in the updated version uses a slightly
different one. Both do not exist in one system. The way it is inserted is by setting an error
trap and then trying one. If it doesn't work, it must be the onther.

WRITE AUTHORITY: @

4.3,8.12 TCP CHANNEL - MAXIMUM TO USE 0;17 NUMBER

INPUT TRANSFORM: K:+X'=X!(X>999)!(X<0)!(X?.E1"."1N.N) X
LAST EDITED: SEP 26, 1992
HELP-PROMPT: Type a Number between 0 and 999, 0 Decimal Digits
DESCRIPTION: This field contains a value that is checked before starting a process to transmit mail via a TCP/IP
channel. If there are already as many processes running as is in this field, no process is
started.

4.3,8.13 STATS NORMALIZATION 7;1 FREE TEXT

INPUT TRANSFORM: K:$L(X)>99!($L(X)<1) X
LAST EDITED: JAN 23, 1998
HELP-PROMPT: Answer must be 1-99 characters in length.
DESCRIPTION:
This option allows the user to customize the normalized report.

4.3,8.14 LARGE MESSAGE REPORT LINES XMUT2-LINES;1 NUMBER

INPUT TRANSFORM: K:+X'=X!(X>999999)!(X<1)!(X?.E1"."1N.N) X
LAST EDITED: JAN 23, 1998
HELP-PROMPT: Type a Number between 1 and 999999, 0 Decimal Digits
DESCRIPTION: This field is used by the large message report. Any message with more than this many lines is
included in the report. If this field is null, the default is 100.

4.3,8.15 TCP/IP POLLER RUN FLAG 0;18 SET

'1' FOR STOP RUNNING;
'0' FOR OKAY TO RUN;
LAST EDITED: JUN 26, 1995
DESCRIPTION: This field is checked every time the background tcp poller, XMRTCP, starts to process poller
request. If it is set to 1, XMRTCP stops running. If it is null or zero, XMRTCP processes the next
entry. If XMRTCP is not running it will not be restarted if the field is set to 1. If it is null
or 0, and XMRTCP is not running, a background task will be created to restart it.

4.3,8.2 RECORD NETMAIL TRANSCRIPT? 0;14 SET

'1' FOR YES;
'0' FOR NO;
LAST EDITED: JUN 27, 1990
DESCRIPTION: This field allows the site manager to turn on and off (toggle) whether or not MailMan records all
script transcripts in background. The send portion of scripts played (using the 'Play Script'
option) will not be recorded.

4.3,8.21 XMITS TILL ERROR MESSAGE NETWORK;1 NUMBER

INPUT TRANSFORM: K:+X'=X!(X>999)!(X<5)!(X?.E1"."1N.N) X
LAST EDITED: FEB 11, 1993
HELP-PROMPT: Type a Number between 5 and 999, 0 Decimal Digits
DESCRIPTION: How many times will a transmission be attempted before a message is sent to the Postmaster
indicating that there have been multiple, unsuccessful transmissions to a domain.

4.3,8.22 DNS AWARE NETWORK;2 SET

'0' FOR NO;
'1' FOR YES;
LAST EDITED: APR 22, 2002
HELP-PROMPT: Should MailMan use DNS to look up IP addresses?
DESCRIPTION: In order for MailMan to be DNS aware, the site must have installed the requisite Kernel patches for
DNS.
- DNS IP (field 51 in file 8989.3) must contain an IP address for a DNS server.
- Routine ^XLFNSLK must exist.

If you answer 'no', MailMan will use the IP addresses in the domain scripts.

If you answer 'yes', MailMan will use the IP addresses in the domain scripts, but if they fail, or
don't exist, MailMan will use DNS to ascertain other IP addresses to try. MailMan will replace
failed script IP address with the successful DNS IP address.

4.3,8.23 TCP/IP COMMUNICATIONS PROTOCOL NETWORK;3 POINTER TO COMMUNICATIONS PROTOCOL FILE (#3.4)

LAST EDITED: JUN 12, 2002
HELP-PROMPT: Which protocol shall be used for TCP/IP?
DESCRIPTION: For TCP/IP connections, the scripts (the TEXT field, 2, in the TRANSMISSION SCRIPT multiple, 4, of
the DOMAIN file, 4.2) can be built on-the-fly, if they don't exist, and if both this field and
field 8.24 are filled in.

We identify the TCP/IP transmission scripts in file 4.2 by the TYPE field, 1.2, within the
TRANSMISSION SCRIPT multiple. Those whose TYPE is 'SMTP', 'TCPCHAN', or null are considered TCP/IP
transmission scripts.

We can build the scripts, because they are standard.

Here's an example of one for FORUM:

O H=DOMAIN.EXT,P=TCP/IP-MAILMAN C TCPCHAN-SOCKET25

In this script, the TCP/IP-MAILMAN refers to the communications protocol to use. This field should
point to the communications protocol in file 3.4 that should be used for TCP/IP connections.

4.3,8.24 TCP/IP TRANSMISSION SCRIPT NETWORK;4 POINTER TO TRANSMISSION SCRIPT FILE (#4.6)

LAST EDITED: JUN 12, 2002
HELP-PROMPT: Which script shall be used for TCP/IP?
DESCRIPTION: For TCP/IP connections, the scripts (the TEXT field, 2, in the TRANSMISSION SCRIPT multiple, 4, of
the DOMAIN file, 4.2) can be built on-the-fly, if they don't exist, and if both this field and
field 8.23 are filled in.

We can build the scripts, because they are standard.

Here's an example of one for FORUM:

O H=DOMAIN.EXT,P=TCP/IP-MAILMAN
C TCPCHAN-SOCKET25

In this script, the TCPCHAN-SOCKET25 refers to the transmission script to use. This field should
point to the transmission script in file 4.6 that should be used for TCP/IP connections.

4.3,8.25 TCP/IP DEVICE NETWORK;5 FREE TEXT

INPUT TRANSFORM: K:$L(X)>30!($L(X)<1) X I $D(X) S %ZIS="NQRS",IOP=X D ^%ZIS K:POP X S:$D(X) X=ION W:$D(X) " Stored i
nternally as ",X D ^%ZISC S IOP="HOME" D ^%ZIS K IOP,%ZIS
LAST EDITED: SEP 06, 2002
HELP-PROMPT: Which device shall be used for TCP/IP?
DESCRIPTION: For TCP/IP connections, the physical link/device to be used is usually standard - some sort of NULL
device. This field is a free-text pointer to that device in the DEVICE (#3.5) file.

The device pointed to by this field will be used for a TCP/IP connection if, in the DOMAIN (#4.2)
file, the device field is null in both of the following fields:
- PHYSICAL LINK / DEVICE (#1.3) field of the TRANSMISSION SCRIPT (#4) multiple
- PHYSICAL LINK DEVICE (#17) field

For more information, see the PHYSICAL LINK DEVICE (#17) field in the DOMAIN (#4.2) file.

NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER

4.3,8.3 NETWORK - MAX LINES SEND NETWORK-LIMIT;1 NUMBER

INPUT TRANSFORM: K:+X'=X!(X>15000)!(X<2000)!(X?.E1"."1N.N) X
LAST EDITED: JAN 22, 1998
HELP-PROMPT: Type a Number between 2000 and 15000, 0 Decimal Digits
DESCRIPTION: This field enables site management to limit the number of lines which a message may have when it is
addressed to a remote recipient. A user may not send a message across the network with more than
this number of lines. If this field is null, there is no limit.

4.3,8.31 NETWORK - MAX LINES RECEIVE NETWORK-LIMIT;2 NUMBER

INPUT TRANSFORM: K:+X'=X!(X>99999999)!(X<0)!(X?.E1"."1N.N) X
LAST EDITED: APR 22, 2002
HELP-PROMPT: Type a Number between 0 and 99999999, 0 Decimal Digits
DESCRIPTION: This field enables site management to limit the number of lines which a message may have when it is
received from a remote site. Any message received from a remote site which has more lines than
this number is automatically rejected. If this field is null, there is no limit.

KIDS and PackMan messages are not affected by this limit.

4.3,8.32 NETWORK - BLOCK SIZE RECEIVE NETWORK-LIMIT;3 SET

'A' FOR 255;
'B' FOR 512;
LAST EDITED: APR 22, 2002
HELP-PROMPT: Select the block size for incoming transmissions.
DESCRIPTION: *** This field is reserved for future use. Not currently used. ***

This is the maximum number of characters to read at a time when receiving incoming transmissions.
Default is 255.

Limiting factors are:
- Maximum string length on the system.
- Maximum global length on the system. In particular, maximum (desirable) length of a line of
message text in the MESSAGE file:
S ^XMB(3.9,xmz,2,x,0)=

You may also wish to consider the maximum string length that the system's various editors can
handle. See the Technical Description for more information.

TECHNICAL DESCR: Why would you want to set the block size higher than 255, which has been the historical setting?
Just how long a line do you need for the text in a message? Well, for user-to-user communication,
255 is more than enough. But for application-to-application communication, 255 may not be enough.
512 may be. So, if your system can handle globals with 512 characters, setting this field to 512
is recommended.

How can you tell how long a string a global can be set to? Do this at the programmer prompt:

> S ^TMP("XM",$J)="" F I=1:1 S ^TMP("XM",$J)=^TMP("XM",$J)_"X"
> W $L(^TMP("XM",$J)) <--- This is your answer
> K ^TMP("XM",$J)

Yes, some systems can handle way more than 512, but we need to limit the maximum, so that if we
need to port data from one system to another, any system can handle data from any other system.

There is one caution. It's a small one, but you should be aware of it. Your system's text
editors, which are used to edit message text in MailMan messages, may not be able to handle line
lengths of more than 245 or 255. When does this become a problem? Only if you attempt to copy and
edit messages which have such lengthy lines. Such lines may be truncated by the editors. This is
not really much of a problem, because you probably won't be copying and editing such messages,
since they would most likely contain application-to-application communication.

4.3,8.4 DIRECTORY REQUEST FLAG 8.4;1 SET

'0' FOR Requests will NOT be granted.;
'1' FOR Requests will be granted.;
LAST EDITED: APR 17, 1994
HELP-PROMPT: Enter 0 to stop all requests for the local directory from being granted.
DESCRIPTION: This field controls whether or not the XMMGR-DIRECTORY-RECV option will grant request from remote
site to send domain user directory information.

If the value is null or zero, request is rejected. If the value is one, a request is granted and
domain user directory will be made available to the remote site.

4.3,10 IN-BASKET-PURGE DAYS 0;9 NUMBER

INPUT TRANSFORM: K:+X'=X!(X>999)!(X<30)!(X?.E1"."1N.N) X
LAST EDITED: JAN 23, 1998
HELP-PROMPT: Type a Number between 30 and 999, 0 Decimal Digits
DESCRIPTION: This field is used by the IN BASKET PURGE to identify inactive messages and mark them for purging.

A message is considered inactive if it has not been accessed in the past number of days specified
here. The default is 30 days.

The IN BASKET PURGE sends a message to each user listing all messages which it has marked for
purging and stating that they will be purged in an additional 30 days if they remain in the 'IN'
basket and are not accessed again.

4.3,10.01 IN-BASKET-PURGE TYPE .15;1 SET

'0' FOR IN BASKET ONLY;
'1' FOR ALL BASKETS;
LAST EDITED: APR 22, 2002
HELP-PROMPT: Enter 0 for IN Basket, 1 for **All** baskets or ? for more information.
DESCRIPTION: This field controls the extent of the IN-BASKET-PURGE. If is is not filled in the effect on the
IN-BASKET-PURGE is the same as it would be if the value of the field is zero.

The field can have the following values:

0 or null = The IN-BASKET-PURGE will affect user IN baskets only.
1 = The IN-BASKET-PURGE will affect all user baskets. (This is not the normal way for this
process to be run. It is recommended that you discuss this with site management and get user input
before doing this.)

In either case the users will be sent the now familiar message listing the messages that will be
deleted from their baskets in 30 days. In either case the field 'IN-BASKET-PURGE DAYS' will
control how long a message can remain inactive in a basket before it is considered okay to put on
the list of messages to be considered for deletion.

4.3,10.03 DATE PURGE CUTOFF DAYS .18;1 NUMBER

INPUT TRANSFORM: K:+X'=X!(X>9999)!(X<365)!(X?.E1"."1N.N) X
LAST EDITED: NOV 17, 2000
HELP-PROMPT: Type a Number between 365 and 9999, 0 Decimal Digits
DESCRIPTION: This field is used by the option XMPURGE-BY-DATE. When this option is run, the date purge will be
set to purge all messages originating this many days ago and before.

If this field is null, the default will be 730 days (2 years).

4.3,10.04 DATE PURGE GRACE PERIOD .18;2 NUMBER

INPUT TRANSFORM: K:+X'=X!(X>31)!(X<3)!(X?.E1"."1N.N) X
LAST EDITED: NOV 17, 2000
HELP-PROMPT: Type a Number between 3 and 31, 0 Decimal Digits
DESCRIPTION: This is the number of days' warning the users get before the date purge, XMPURGE-BY-DATE, is run.

This field is used by the option XMPURGE-BY-DATE only if that option is scheduled, not if it is run
interactively.

At the scheduled date/time, the bulletin, XM DATE PURGE WARNING, is broadcast to all users to warn
them of the coming date purge, and the actual date purge is then queued to run this many days
later.

If this field is null, the date purge will run at the scheduled date/time, and no bulletin will be
sent.

4.3,10.1 BACKGROUND FILER HANG TIME 0;13 NUMBER

INPUT TRANSFORM: K:+X'=X!(X>99)!(X<0)!(X?.E1"."1N.N) X
LAST EDITED: NOV 15, 1988
HELP-PROMPT: Background filer hangs up to 99 seconds between mail deliveries (default=5).
DESCRIPTION: This field is used by the background filer when it is started up to determine the amount of time it
will hang between deliveries of messages. Since mail is not delivered, even to the sender, unless
the backgournd filer delivers it, it should not be too long a period so that your users are
inconvenienced. If this field is not filled in the background filer will hang for 5 seconds
between deliveries. 5 to 15 seconds is the recommended range.

4.3,10.2 BACKGROUND FILER RUN FLAG 0;16 SET

'1' FOR STOP RUNNING;
'0' FOR OKAY TO RUN;
LAST EDITED: JAN 23, 1992
DESCRIPTION: The background filer checks this field every time it is about to deliver a message or response. If
it is set to 1, it stops running, and will not restart until it is set to null or zero. If it is
null or zero, and is already running, it continues. If it is null or zero, and is not running, a
background task will be created to restart it.

WRITE AUTHORITY: @

4.3,10.3 BACKGROUND FILER RUN PRIORITY .13;1 NUMBER

INPUT TRANSFORM: K:+X'=X!(X>10)!(X<0)!(X?.E1"."1N.N) X
LAST EDITED: NOV 12, 1992
HELP-PROMPT: Type a Number between 0 and 10, 0 Decimal Digits
DESCRIPTION:
This field is used by the background filer to set its priority at runtime.

4.3,16.1 P-MESSAGE LINE LIMIT .16;1 NUMBER

INPUT TRANSFORM: K:+X'=X!(X>9999999)!(X<2000)!(X?.E1"."1N.N) X
LAST EDITED: APR 08, 1998
HELP-PROMPT: Type a Number between 2000 and 9999999, 0 Decimal Digits
DESCRIPTION: This field enables site management to limit the number of lines which may be printed to P-MESSAGE.
If this field is null, there is no limit.

4.3,17.1 MAX DIGITS FOR MESSAGE NUMBER .17;1 NUMBER

INPUT TRANSFORM: K:+X'=X!(X>14)!(X<7)!(X?.E1"."1N.N) X
LAST EDITED: SEP 17, 1998
HELP-PROMPT: Type a Number between 7 and 14, 0 Decimal Digits
DESCRIPTION: This field is used to control the size of the message number in ^XMB(3.9, the MESSAGE file. If
this field is null, its default will be 8 digits. If the message number becomes greater than this
many digits, the message numbers will recycle back to the next vacant message number after 999999.
In this way, message numbers will cease being too ungainly in size.

So message numbers will be re-used.

If MailMan is not able to find a vacant message number less than this number of digits, then
MailMan will take the next available message number, no matter how many digits it has, AND MailMan
will change this field to reflect the new maximum.

It is very important that the unreferenced messages purge and/or the date purge be run on a regular
basis to free up message numbers for re-use.

4.3,21 FORWARD PRIORITY MAIL TO GROUP 2;1 SET

'0' FOR NO;
'1' FOR YES;
LAST EDITED: MAY 25, 2000
HELP-PROMPT: Let users forward priority messages to mail groups?
DESCRIPTION: Enter YES if you wish to allow users to forward priority messages to mail groups.

Enter NO if you don't. (This is the default, if this field is null.) Then only the message
originator or anyone with the XM GROUP PRIORITY key may forward priority messages to mail groups.

TECHNICAL DESCR: The issue here is one of annoyance. Priority messages can be annoying. When priority messages are
inappropriately forwarded to mail groups, the annoyance quotient rises dramatically. If you wish
to have MailMan be the enforcer, then set this field to NO. (Then only a select few users will be
able to forward priority messages to mail groups.) If you wish to have the user's peers be the
enforcers, then set this field to YES. (Then anyone can forward priority messages to mail groups,
and users who inappropriately do so, risk the wrath and flames of the annoyed recipients.)

4.3,22 DROP OUT OF RESTRICTED GROUP 2;2 SET

'0' FOR NO;
'1' FOR YES;
LAST EDITED: JUN 06, 2000
HELP-PROMPT: Let users drop out of non-self-enrolling mail groups?
DESCRIPTION: Enter YES if you wish to allow users to drop out of non-self-enrolling mail groups. The user will
be warned that this is a non-self-enrolling group, and that they won't be allowed to rejoin later,
and then they will be asked to re-confirm the decision to drop out.

Enter NO if you don't. (This is the default if this field is null.) Then users will have to
contact IRM or the mail group coordinator to ask to be dropped.

TECHNICAL DESCR: If a mail group is not a self-enrolling mail group, then users can't just join. They must be added
by the mail group coordinator.

If a user no longer wishes to be a member of such a group, he must ask the group coordinator to
drop him. But what if the group coordinator has left the organization or is unresponsive? Then
what? Then the user will have to ask IRM to help. This problem can be avoided by setting this
field to YES.

Some would argue that the coordinator added the user to the group for a reason, and the user should
not be allowed to drop out. (Perhaps the coordinator is the user's boss.) They would argue that
it is MailMan's job to prevent the user from dropping out. (Set the field to NO.) Others would
argue that it is not MailMan's job at all, but the boss's job to prevent the user from dropping
out, and to discipline the user if he does. (Set the field to YES.)

4.3,23 TITLE SOURCE 0;11 SET

'S' FOR SIGNATURE BLOCK TITLE;
'T' FOR TITLE;
LAST EDITED: JUL 18, 2000
HELP-PROMPT: Where should the user's title come from?
DESCRIPTION: Where in the NEW PERSON file should the user's title come from?

Enter 'S' if the user's title should come from field 20.3, SIGNATURE BLOCK TITLE. If that field is
empty, then we'll try field 8, TITLE.

Enter 'T' if the user's title should come from field 8, TITLE. If that field is empty, we won't
show any title.

The default is 'T', if this field is not filled in.

4.3,31 AUTO-FORWARD LIMITED? 3;1 SET

'0' FOR NO;
'1' FOR YES;
LAST EDITED: APR 15, 2003
HELP-PROMPT: Should auto-forward capability be limited?
DESCRIPTION: For security or privacy reasons, you may wish to limit the sites to which users may have their mail
auto-forwarded. If so, set this field to YES, and enter the approved sites in the AUTO-FORWARD
APPROVED SITE multiple.

For VA sites, this field must be set to YES. The only approved sites are those ending in
".DOMAIN.EXT".

If this field is set to YES, MailMan will limit auto-forwarding to only those sites whose names are
in (or end in the ones in) the AUTO-FORWARD APPROVED SITE multiple.

4.3,31.1 AUTO-FORWARD APPROVED SITE 3.1;0 Multiple #4.33

4.33,.01 AUTO-FORWARD APPROVED SITE 0;1 FREE TEXT (Multiply asked)

INPUT TRANSFORM: K:$L(X)>64!($L(X)<3) X
LAST EDITED: APR 14, 2003
HELP-PROMPT: Answer must be 3-64 characters in length.
DESCRIPTION: If the AUTO-FORWARD LIMIT? (#31) field is set to YES, auto-forward addresses are limited to sites
which are listed here, or which end in those which are listed here.

For VA sites, the one and only entry should be ".DOMAIN.EXT".

CROSS-REFERENCE: 4.33^B
1)= S ^XMB(1,DA(1),3.1,"B",$E(X,1,64),DA)=""
2)= K ^XMB(1,DA(1),3.1,"B",$E(X,1,64),DA)

4.3,31.2 AUTO-FORWARD WAIVER SITE 3.2;0 Multiple #4.34

LAST EDITED: APR 14, 2003

4.34,.01 AUTO-FORWARD WAIVER SITE 0;1 FREE TEXT (Multiply asked)

INPUT TRANSFORM: K:$L(X)>64!($L(X)<3) X
LAST EDITED: APR 15, 2003
HELP-PROMPT: Answer must be 3-64 characters in length.
DESCRIPTION: If the AUTO-FORWARD LIMIT? (#31) field is set to YES, auto-forward addresses are limited to sites
in the AUTO-FORWARD APPROVED SITE (#31.1) multiple.

However, any user who has been assigned the XM AUTO-FORWARD WAIVER security key, may also
auto-forward to the sites which are listed here, or which end in those which are listed here.

Requests for waivers must be submitted through the site Information Security Officer (ISO). Only
after a waiver has been granted may a site be added here. Check with the ISO for details on the
requirements for the waiver.

CROSS-REFERENCE: 4.34^B
1)= S ^XMB(1,DA(1),3.2,"B",$E(X,1,64),DA)=""
2)= K ^XMB(1,DA(1),3.2,"B",$E(X,1,64),DA)

4.3,40 PREVENT MESSAGE RELAY? 4;1 SET

'1' FOR YES;
'0' FOR NO;
LAST EDITED: FEB 09, 2004
HELP-PROMPT: Should message relaying be prevented?
DESCRIPTION: Answer YES if you want to prevent outside sites from sending mail through your site to other
outside sites. Spammers and Virus propagators use this technique to disguise the source of their
mail, and to make it appear to come from a trusted source, namely your site.

Answer NO if you want your site to act as a relay site for anyone.

It is strongly recommended that you answer YES to prevent your site from unwittingly relaying
destructive mail.

If you answer YES, you should define your "inside" sites in the MY DOMAIN (field #41) multiple, so
that MailMan can distinguish them from outside sites.

Note: This does NOT prevent users from receiving mail from outside sites. It also does NOT prevent
users from forwarding mail to outside sites. Such actions are perfectly acceptable.

4.3,41 MY DOMAINS 4.1;0 Multiple #4.341

4.341,.01 MY DOMAINS 0;1 FREE TEXT (Multiply asked)

INPUT TRANSFORM: K:$L(X)>30!($L(X)<3) X
LAST EDITED: FEB 17, 2004
HELP-PROMPT: Answer must be 3-30 characters in length.
DESCRIPTION: If you answered YES to PREVENT MESSAGE RELAYING? (field #40), to stop your site from relaying
messages from outside sites through your site to other outside sites, you may add entries here,
in order to define what is an "inside" site, or sites whose messages your site is willing to
relay.

For example, if your site is a VA site, then other VA sites are "inside" sites, and your site
should relay mail for them. So, any site whose domain name ends in ".DOMAIN.EXT" is an "inside"
site. So VA sites should have only one record in this multiple, and it should be ".DOMAIN.EXT".

The default, if there are no entries in this multiple, is your site's domain name.

MailMan will check the site name of any site which connects to it, and identifies itself in the
SMTP HELO command. If the sitename ends in any of the entries in this multiple, then
any mail coming from that site through your site to other sites, will be accepted and relayed
onward.

If the sitename does not end in any of the entries in this multiple, then messages will only be
accepted that are addressed to recipients whose sitenames end in one of the entries in this
multiple. Otherwise, the site will receive an error message telling it that relaying is denied,
and messages will not be accepted for relaying onward.

CROSS-REFERENCE: 4.341^B
1)= S ^XMB(1,DA(1),4.1,"B",$E(X,1,30),DA)=""
2)= K ^XMB(1,DA(1),4.1,"B",$E(X,1,30),DA)

4.3,50 LIMITED BROADCAST 5;0 Multiple #4.32

4.32,.01 LIMITED BROADCAST 0;1 FREE TEXT (Multiply asked)

INPUT TRANSFORM: K:$L(X)>30!($L(X)<3) X
LAST EDITED: OCT 25, 1999
HELP-PROMPT: Answer must be 3-30 characters in length
DESCRIPTION:
This is the name of the associated field in the NEW PERSON file.

CROSS-REFERENCE: 4.32^B
1)= S ^XMB(1,DA(1),5,"B",$E(X,1,30),DA)=""
2)= K ^XMB(1,DA(1),5,"B",$E(X,1,30),DA)

4.32,1 POINTED TO FILE 0;2 POINTER TO FILE FILE (#1) (Required)

LAST EDITED: NOV 16, 1999
HELP-PROMPT: Answer with FILE NUMBER, or NAME
DESCRIPTION:
This is the file pointed to by the associated field in the NEW PERSON file.

4.32,2 NEW PERSON FILE XREF 0;3 FREE TEXT (Required)

INPUT TRANSFORM: K:$L(X)>4!($L(X)<1) X
LAST EDITED: NOV 16, 1999
HELP-PROMPT: Answer must be 1-4 characters in length.
DESCRIPTION: This is the name of the (whole file) cross reference on the associated field in the NEW PERSON
file.

4.3,51 LIMITED BROADCAST DEFAULT 0;20 NUMBER

INPUT TRANSFORM: D INXFORM^XMXADDR2(.X)
OUTPUT TRANSFORM: S:Y Y=$P($G(^XMB(1,1,5,Y,0)),U,1)
LAST EDITED: NOV 29, 1999
HELP-PROMPT: Select a limited broadcast default
DESCRIPTION: When sending a limited broadcast message, this is the default which will appear when the user is
presented with limited broadcast choices.

If you don't want a default to appear, delete this entry.

TECHNICAL DESCR: For this field, we are simulating a pointer to a record in the LIMITED BROADCAST multiple. The
executable help displays the choices in the multiple. The input transform makes sure you choose
one of the choices. The output transform converts the "pointer" to the limited broadcast name.

EXECUTABLE HELP: D EXHELP^XMXADDR2
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER

4.3,142 NO-PURGE DAYS BUFFER (LOCAL) .14;2 NUMBER

INPUT TRANSFORM: K:+X'=X!(X>10)!(X<2)!(X?.E1"."1N.N) X
LAST EDITED: SEP 18, 1998
HELP-PROMPT: Type a Number between 2 and 10, 0 Decimal Digits
DESCRIPTION: This field is used during the un-referenced-messages purge to avoid purging the last few messages
in the message file, according to their local create date.

We subtract the NO-PURGE DAYS BUFFER (LOCAL) from today's date, giving a 'no-purge date'. Local
messages which were created on or after that date and which were sent to remote sites are not
subject to purge. Other messages are not affected by this buffer.

If this field is not filled in, it defaults to 7 days. This is the recommended value.

It should not be less than the NO-PURGE DAYS BUFFER (field 4.301) or it will have no effect.

One situation in which this buffer may be useful is in the case of a message sent only to a remote
site. Such a message is unreferenced and would otherwise be subject to purge. If a reply came
from the remote site after the original message had been purged, the sender would have access only
to the reply and not to the original message. The NO-PURGE DAYS BUFFER (LOCAL) could be set to a
reasonable number of days to allow for a reply.

4.3,143 FAX ENABLED 0;19 SET

'0' FOR no;
'1' FOR yes;
LAST EDITED: FEB 11, 1997
HELP-PROMPT: Is your site fax enabled?
DESCRIPTION: Your site is fax enabled if you have the suite of fax software and files (^AKF) and fax capability
and you choose to allow faxes to be sent via MailMan.

To send faxes via MailMan, Mail groups (file 3.8) must first be populated in the fax recipient and
fax group multiples. Then, when a user sends a message to a mail group, the message is also faxed
to any fax recipients in that mail group. Responses to the message are not faxed.

4.3,217 DEFAULT INSTITUTION XUS;17 POINTER TO INSTITUTION FILE (#4) (Required) (audited)

LAST EDITED: JUN 14, 2024
HELP-PROMPT: Enter the instutition to use as a default for users without one.
DESCRIPTION: This field is the default institution that is shown for any user who hasn't chosen one under "edit
user options"

TECHNICAL DESCR:
This field is set by a Mumps xref on file 8989.3, field 217, making it a duplicate of that field.

AUDIT: YES, ALWAYS
WRITE AUTHORITY: ^

4.3,241 BACKGROUND MESSAGE DELIVERERS 6;1 FREE TEXT

INPUT TRANSFORM: D CHKQ^XMKPLQ
LAST EDITED: JAN 21, 1998
HELP-PROMPT: Enter a set of increasing numbers separated by commas.
DESCRIPTION: This field is used by the background filer to determine how many message delivery queues (and
tasks) there should be and how to separate them.

EXECUTABLE HELP: D HELPQ^XMKPLQ
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER

4.3,242 BACKGROUND RESPONSE DELIVERERS 6;2 FREE TEXT

INPUT TRANSFORM: D CHKQ^XMKPLQ
LAST EDITED: JAN 21, 1998
HELP-PROMPT: Enter a set of increasing numbers separated by commas.
DESCRIPTION: This field is used by the background filer to determine how many response delivery queues (and
tasks) there will be and how to separate them.

EXECUTABLE HELP: D HELPQ^XMKPLQ
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER

FILES POINTED TO FIELDS

COMMUNICATIONS PROTOCOL (#3.4) TCP/IP COMMUNICATIONS PROTOCOL (#8.23)

DOMAIN (#4.2) DOMAIN NAME (#.01)
PARENT (#3)
SUBORDINATE DOMAIN:SUBORDINATE DOMAIN (#.01)

FILE (#1) LIMITED BROADCAST:POINTED TO FILE (#1)

INSTITUTION (#4) DEFAULT INSTITUTION (#217)

MAILMAN TIME ZONE (#4.4) TIME ZONE (#1)

NEW PERSON (#200) SUBORDINATE DOMAIN:CHRISTENED BY (#2)

TRANSMISSION SCRIPT (#4.6) TCP/IP TRANSMISSION SCRIPT (#8.24)

INPUT TEMPLATE(S):

PRINT TEMPLATE(S):

SORT TEMPLATE(S):

FORM(S)/BLOCK(S):