| DESCRIPTION OF ENHANCEMENTS |
MailMan 8.0
(through patches XU*8.0*216 and DI*22.0*68, respectively).
11. You can now send, forward, or filter-forward messages to H.device
(Headerless print). It will print the message, without a header, on the
device. As before, sending messages to D.device will print them with
a header.
12. In response to NOIS HWH-0502-41774, if you become a surrogate of a user,
and try to access a message that the user is not on (but you are), you will
be told that you will have to forward the message to the user, in order to
access it as the user. You will then be given the opportunity to forward
it, if it's OK to do so. (For example, if the message is closed, you would
not be allowed to forward it, if you didn't send it.)
13. In response to NOIS CHY-0597-50209, when using TalkMan to communicate
with a site, MailMan will only consider using scripts whose TYPE is TELNET.
14. The pre-init, PRE^XMYPRE, will
- K ^DOPT("XMC"), to reset the programmer options (D ^XMC).
- Kill the old "AC" xref definition for NETWORK PRIORITY TRANSMISSION field
6, in the basket multiple of file 3.7, and change all xrefs
MailMan 8.0 offers the following improvements over MailMan 7.1:
^XMB(3.7,.5,2,"AC",1,XMK,XMZ) to ^XMB(3.7,.5,2,XMK,1,"AC",1,XMZ).
- Delete the following fields from file 4.2999, MESSAGE STATISTICS, because
they are not used:
7 OUTGOING MESSAGE COUNT
8 CHARACTERS REC'D
9 INCOMING MESSAGE COUNT
10 CHARACTERS SENT
- Delete the ENTRY ACTION fields for options XMQSHOW, XMSUBEDIT, XMDXPROT.
15. The post-init, POST^XMYPRE, will
- Go through MailMan's security keys and ensure that the 'mutually
exclusive' keys are correct.
16. Here are DD changes:
a. MESSAGE file 3.7
- Change field 2, FORWARDING ADDRESS to fix the bulletin xref. FileMan
thought that it was firing XM-FWD-ADDRESS-CHECKER, yet it was actually
firing XMZFWDBULL. It now fires XM FWD ADDRESS CHANGE, a new bulletin,
1. MailMan is now DNS aware. It can use the Kernel API MAIL^XLFNSLK
which looks like the old ones, but has a better name.
STANDARD DATA DICTIONARY #3.7 -- MAILBOX FILE
STORED IN ^XMB(3.7,
DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
---------------------------------------------------------------------------
3.7,2 FORWARDING ADDRESS 0;2 FREE TEXT
Remote address to which mail is routed
INPUT TRANSFORM: D XMFWD^XMVVITA(.X,$G(XMIA)) I $D(X) K:$L(X)>50
to retrieve IP addresses. It is no longer necessary to manually update the
!($L(X)<1) X
LAST EDITED: APR 23, 2002
HELP-PROMPT: Enter a forwarding address (name@domain) of up
to 50 characters.
DESCRIPTION: This field names an additional address to which
any messages addressed to you are routed. This
address must be a remote address or a local
device.
If you want a local user to see your messages,
IP addresses in the DOMAIN file, 4.2. The IP address fields will remain in
make that user a surrogate.
See the LOCAL DELIVERY FLAG. If you do not
edit this field to 'ON', then mail will only be
delivered to your FORWARDING ADDRESS and not to
your Mailbox.
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
CROSS-REFERENCE: ^^BULLETIN MESSAGE
file 4.2, and MailMan will use them. However, if they don't work, MailMan
1)= S Y(0)=X,D0=DA X "N DIIND F DIIND=1.001:.00
1 Q:$D(^DD(3.7,2,1,1,DIIND))[0 X ^(DIIND)" K X
MY S XMB="XM FWD ADDRESS CHANGE" D ^XMB:$D(^XMB
(3.7,"B",XMB)),ENT^XMUT7(DA) K Y,XMB
1.001)= S X=Y(0) S Y(1)=$S($D(^XMB(3.7,D0,0)):^
(0),1:"") S X=$S('$D(^VA(200,+$P(Y(1),U,1),0)):
"",1:$P(^(0),U,1)) S XMB(1)=X
1.002)= S X=Y(0) S Y(1)=$S($D(^XMB(3.7,D0,0)):^
(0),1:"") S X=$P(Y(1),U,2) S XMB(2)=X
2)= Q
will use the Kernel API to retrieve a list of valid IP addresses. When
CREATE PARAMETER #1)= NAME
CREATE PARAMETER #2)= FORWARDING ADDRESS
CREATE VALUE)= XM FWD ADDRESS CHANGE
DELETE VALUE)= NO EFFECT
This cross reference sends two bulletins.
The first, XM FWD ADDRESS CHANGE, notifies
responsible individuals (belonging to the mail
group associated with the bulletin) that a user
has changed his forwarding address. This is
MailMan finds one that works, MailMan will replace the non-working IP
the "official" bulletin of this cross
reference.
The second, XM FWD ADDRESS CHECK, is sent to
the user's new forwarding address as test to
see if the address is valid. If it's not
valid, the sender (the Postmaster) will receive
an error message. This bulletin has been
piggy-backed onto the "official" bulletin.
FileMan is not aware of this.
address with the working one. In order to activate DNS awareness, this
CROSS-REFERENCE: 3.7^F
1)= S ^XMB(3.7,"F",$E(X,1,30),DA)=""
2)= K ^XMB(3.7,"F",$E(X,1,30),DA)
This cross reference enables the site manager
to easily find a user who enters a bad
forwarding address.
- Change field 3.702,6 - NETWORK PRIORITY TRANSMISSION
to expand the set of codes to add low priority, and to change the "AC" xref
new field in the MAILMAN SITE PARAMETERS file 4.3 must be set to 'yes':
from user-level to message-level. (See item 3, above, for more info.)
3.702,6 NETWORK PRIORITY TRANSMISSION? 0;6 SET
'1' FOR HIGH PRIORITY;
'0' FOR REGULAR PRIORITY;
'2' FOR LOW PRIORITY;
HELP-PROMPT: How should this message be handled during
transmission?
DESCRIPTION: This field is used to flag messages that need
to be transmitted before or after all other
4.3,8.22 DNS AWARE Yes or No?
messages in a queue.
Messages in the queue which are flagged as HIGH
priority are transmitted before all other
messages.
Messages in the queue which are flagged as
REGULAR priority (default) are transmitted
next.
Also, routine ^XLFNSLK must exist, and the following field in the
Messages in the queue which are flagged as LOW
priority are transmitted after all other
messages.
Messages with the same priority are transmitted
in IEN order, which is not necessarily the
order in which they appear in the transmit
queue.
Only the POSTMASTER (or surrogate) may change
KERNEL SYSTEMS PARAMETERS file 8989.3 must be properly filled in with
the priority of a message in a transmit queue.
If, during a transmission, MailMan has problems
with a particular message, MailMan may flag
that message as LOW priority, so that other
messages in the queue will transmit, before the
problem message is attempted again.
Changes to message priorities can be made even
while a queue is being transmitted.
an IP address:
FIELD INDEX: AC (#12) REGULAR IR SORTING ONLY
Short Descr: Transmission Priority Cross Reference
Description: This xref is used by MailMan during message
transmission to identify messages which should
be transmitted first (high priority) or last
(low priority). Messages with regular priority
are not xref'd.
Set Logic: S ^XMB(3.7,DA(2),2,DA(1),1,"AC",$E(X,1,1),DA)=""
Set Cond: S X=X
Kill Logic: K ^XMB(3.7,DA(2),2,DA(1),1,"AC",$E(X,1,1),DA)
8989.3,51 DNS IP IP address for DNS
Kill Cond: S X=X
Whole Kill: K ^XMB(3.7,DA(2),2,DA(1),1,"AC")
X(1): NETWORK PRIORITY TRANSMISSION? (3.702,6)
(Subscr 1) (Len 1) (forwards)
b. MAIL GROUP file 3.8, add a trigger to field .01 to populate field 5.1
STANDARD DATA DICTIONARY #3.8 -- MAIL GROUP FILE
STORED IN ^XMB(3.8,
DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
----------------------------------------------------------------------------
3.8,.01 NAME 0;1 FREE TEXT (Required)
MAIL GROUP NAME
INPUT TRANSFORM: S:X?1"G.".E!(X?1"g.".E) X=$E(X,3,99) K:$L(X)>30
!($L(X)<3)!'(X'?1P.E)!(X'?.ANP) X
HELP-PROMPT: ANSWER MUST BE 3-30 CHARACTERS IN LENGTH
DESCRIPTION: The name of a mail group, i.e. a list of
recipients who can all be addressed at once by
reference to this name.
2. For TCP/IP connections, MailMan can now build transmission scripts
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
CROSS-REFERENCE: 3.8^B
1)= S ^XMB(3.8,"B",$E(X,1,30),DA)=""
2)= K ^XMB(3.8,"B",$E(X,1,30),DA)
CROSS-REFERENCE: ^^TRIGGER^3.8^5
1)= X ^DD(3.8,.01,1,2,1.3) I X S X=DIV S Y(1)=$
S($D(^XMB(3.8,D0,3)):^(3),1:"") S X=$P(Y(1),U,1
),X=X S DIU=X K Y S X=DIV S X=$G(XMDUZ,DUZ) S D
IH=$G(^XMB(3.8,DIV(0),3)),DIV=X S $P(^(3),U,1)=
DIV,DIH=3.8,DIG=5 D ^DICR
on-the-fly. (Transmission scripts exist in the DOMAIN file 4.2, in the
1.3)= K DIV S DIV=X,D0=DA,DIV(0)=D0 S Y(0)=X S
Y(1)=$S($D(^XMB(3.8,D0,3)):^(3),1:"") S X=$S('$
D(^VA(200,+$P(Y(1),U,1),0)):"",1:$P(^(0),U,1))=
""
2)= Q
CREATE CONDITION)= ORGANIZER=""
CREATE VALUE)= S X=$G(XMDUZ,DUZ)
DELETE VALUE)= NO EFFECT
FIELD)= ORGANIZER
When a user creates a mail group, this trigger
Test Sites: FORUM, San Francisco, Central Alabama, FO-Albany, FO-Oakland
TRANSMISSION SCRIPT multiple, in the TEXT field 2.) If the TYPE is "SMTP",
makes that user the organizer of the group.
The user is free to change that field.
c. INTER-UCI TRANSFER file 4.281, increase domain name field lengths to
agree with .01 field in file 4.2. Also increase lengths of B & C xrefs.
STANDARD DATA DICTIONARY #4.281 -- INTER-UCI TRANSFER FILE
STORED IN ^%ZISL(4.281,
DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
"TCPCHAN", or null, and the TEXT field has no records, and these fields
---------------------------------------------------------------------------
4.281,.01 FROM DOMAIN 0;1 FREE TEXT (Required)
INPUT TRANSFORM: K:$L(X)>64!($L(X)<3)!'(X'?1P.E) X
HELP-PROMPT: Answer must be 3-64 characters in length
CROSS-REFERENCE: 4.281^B
1)= S ^%ZISL(4.281,"B",$E(X,1,64),DA)=""
2)= K ^%ZISL(4.281,"B",$E(X,1,64),DA)
4.281,1 TO DOMAIN 0;2 FREE TEXT
INPUT TRANSFORM: K:$L(X)>64!($L(X)<3) X
in the MAILMAN SITE PARAMETERS file 4.3 are filled in:
HELP-PROMPT: Answer must be 3-64 characters in length
CROSS-REFERENCE: 4.281^C
1)= S ^%ZISL(4.281,"C",$E(X,1,64),DA)=""
2)= K ^%ZISL(4.281,"C",$E(X,1,64),DA)
3)= XXXX - Do not delete
This cross-reference is used by the receiving
UCI to find entries which have been
'transmitted' to it from other UCIs.
d. Add fields to MESSAGE STATISTICS file 4.2999.
4.3,8.23 TCP/IP COMMUNICATIONS PROTOCOL Points to file 3.4
STANDARD DATA DICTIONARY #4.2999 -- MESSAGE STATISTICS FILE
STORED IN ^XMBS(4.2999,
DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
---------------------------------------------------------------------------
4.2999,8 DIRECTION 3;8 SET
'S' FOR SENDING;
'R' FOR RECEIVING;
HELP-PROMPT: Are we sending or receiving?
4.3,8.24 TCP/IP TRANSMISSION SCRIPT Points to file 4.6
DESCRIPTION: This field is used to report whether, at any
given time, we are sending messages to, or
receiving messages from, the site.
4.2999,48 XMIT IP ADDRESSES TRIED 4;8 FREE TEXT
INPUT TRANSFORM: K:$L(X)>100!($L(X)<3) X
HELP-PROMPT: Answer must be 3-100 characters in length.
DESCRIPTION: This is a list of IP addresses, separated by
commas, which have already been used in
attempting to connect with the site.
...then MailMan creates the script. This one is for FORUM:
We use this list in conjunction with the DNS
server, which returns a list of valid addresses
to try. Using both lists, we can come up with
the next IP address to try.
4.29992,3 XMIT AUDIT IP ADDRESS 0;4 FREE TEXT
INPUT TRANSFORM: K:$L(X)>20!($L(X)<1) X
HELP-PROMPT: Answer must be 1-20 characters in length.
DESCRIPTION: This is the IP address used for this attempt.
O H=DOMAIN.EXT,P=TCP/IP-MAILMAN
e. Change fields in MESSAGE STATISTICS file 4.2999.
Changed the title and description:
4.2999,.01 NAME 0;1 POINTER TO DOMAIN FILE (#4.2)
(Required)
Domain name
INPUT TRANSFORM: S:$D(X) DINUM=X
DESCRIPTION: Domain for which network mail transmission
C TCPCHAN-SOCKET25
information is collected.
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
CROSS-REFERENCE: 4.2999^B
1)= S ^XMBS(4.2999,"B",$E(X,1,30),DA)=""
2)= K ^XMBS(4.2999,"B",$E(X,1,30),DA)
Changed to a pointer and changed the help prompt:
4.2999,2 MESSAGE IN TRANSIT 3;2 POINTER TO MESSAGE FILE (#3.9)
HELP-PROMPT: Enter the IEN of the message being transmitted.
where:
DESCRIPTION: This points to the 3.9 (Message) file entry of
the message being transmitted.
Corrected the spelling of "included":
4.29991,103 MESSAGES RECEIVED 0;3 NUMBER
INPUT TRANSFORM:K:+X'=X!(X>9999999)!(X<0)!(X?.E1"."1N.N) X
HELP-PROMPT: Type a Number between 0 and 9999999, 0 Decimal
Digits
"DOMAIN.EXT" is taken from the DOMAIN name.
DESCRIPTION: Messages received are included here even if
they are received only to be forwarded on to
another site. Also included are responses and
messages received previously (as long as they
have additional recipients).
Increased the length of the following fields:
4.29991,104 CHARACTERS SENT 0;4 NUMBER
INPUT TRANSFORM:K:+X'=X!(X>999999999)!(X<0)!(X?.E1"."1.N) X
"TCP/IP-MAILMAN" is the protocol pointed to by field 8.23
HELP-PROMPT: Type a number between 0 and 999999999, 0
Decimal Digits
DESCRIPTION: This is a count of the number of characters in
the messages sent.
4.29991,105 CHARACTERS RECEIVED 0;5 NUMBER
INPUT TRANSFORM:K:+X'=X!(X>999999999)!(X<0)!(X?.E1"."1.N) X
HELP-PROMPT: Type a number between 0 and 999999999, 0
Decimal Digits
DESCRIPTION: This is a count of the number of characters in
"TCPCHAN-SOCKET25" is the script pointed to by field 8.24.
the messages received.
4.29991,106 LINES SENT 0;6 NUMBER
INPUT TRANSFORM:K:+X'=X!(X>99999999)!(X<0)!(X?.E1"."1.N) X
HELP-PROMPT: Type a number between 0 and 99999999, 0 Decimal
Digits
DESCRIPTION: This is a count of the number of lines in the
message sent.
4.29991,107 LINES RECEIVED 0;7 NUMBER
INPUT TRANSFORM:K:+X'=X!(X>99999999)!(X<0)!(X?.E1"."1.N) X
HELP-PROMPT: Type a number between 0 and 99999999, 0 Decimal
Digits
DESCRIPTION: This is a count of the number of lines in the
messages received.
f. Add fields to MAILMAN SITE PARAMETERS file 4.3
(See items 1 and 2, above, for more info.)
STANDARD DATA DICTIONARY #4.3 -- MAILMAN SITE PARAMETERS FILE
3. Messages in transmit queues can now be designated as low priority, as
STORED IN ^XMB(1,
DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
---------------------------------------------------------------------------
4.3,8.22 DNS AWARE NETWORK;2 SET
'0' FOR NO;
'1' FOR YES;
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
well as high priority. If a message gets stuck in a transmit queue and is
patches for DNS.
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
holding up the rest of the queue for whatever reason, MailMan will make
successful DNS IP address.
4.3,8.23 TCP/IP COMMUNICATIONS PROTOCOL NETWORK;3
POINTER TO COMMUNICATIONS PROTOCOL FILE (#3.4)
(Required)
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) are ignored.
that message a low priority message, so that all the other messages are
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 ignore the scripts, because they are
standard.
Here's an example of one for FORUM:
transmitted ahead of it. The postmaster can also make these priority
O H=DOMAIN.EXT,P=TCP/IP-MAILMAN
C TCPCHAN-SOCKET25-VXD
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.
changes. In the message queue, high-priority messages are now marked with
4.3,8.24 TCP/IP TRANSMISSION SCRIPT NETWORK;4
POINTER TO TRANSMISSION SCRIPT FILE (#4.6)
(Required)
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) are ignored.
We identify the TCP/IP transmission scripts in
file 4.2 by the TYPE field, 1.2, within the
'^', instead of '$'. Low priority messages are marked with 'v'.
TRANSMISSION SCRIPT multiple. Those whose TYPE
is 'SMTP', 'TCPCHAN', or null are considered
TCP/IP transmission scripts.
We can ignore the scripts, because they are
standard.
Here's an example of one for FORUM:
O H=DOMAIN.EXT,P=TCP/IP-MAILMAN
MailMan 8.0 is a maintenance release. It includes the complete MailMan
C TCPCHAN-SOCKET25-VXD
In this script, the TCPCHAN-SOCKET25-VXD 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.
NOTE: This release should be installed after hours, when user activity is at
a minimum. Your site should be patched through MailMan patch XM*7.1*198.
It is also expected that Kernel 8.0 and FileMan 22.0 are installed and are
The postmaster can now change the transmit priority at the message level
reasonably up-to-date (through patches XU*8.0*216 and DI*22.0*68,
respectively). It is up to you to check this. KIDS will not.
Installation will take approximately 5 minutes.
============================================================================
ROUTINES:
The second line of the routines now look like:
;;8.0;MailMan;;Jun 28, 2002
Routine list and checksums can be found in routines XMNTEG and XMNTEG0.
(at the 'Message action: Ignore//' prompt). As at the basket level, the
===========================================================================
INSTALLATION:
NOTES:
a. This release should be installed after hours, when user activity is at a
minimum. Your site should be patched through MailMan patch XM*7.1*198. It
is also expected that Kernel 8.0 and FileMan 22.0 are installed and are
reasonably up-to-date (through patches XU*8.0*216 and DI*22.0*68,
respectively). It is up to you to check this. KIDS will not.
command to use is 'X'. (In a user basket, the 'X' at the message level is
b. Installation will take approximately 5 minutes.
c. DSM sites running SlotMaster may see routine mapping problems with ZSLOT
users, even after disabling mapping. Therefore, such sites should consider
the following steps:
- Shutdown ZSLOT on all nodes.
- Disable all mapped XM routines.
- Install this release.
- Enter manual edits.
- Rebuild mapped routine sets.
- Shutdown/restart all DSM configurations.
a command to unload a PackMan message or KIDS build. In a remote transmit
An alternative to the above steps is to disable all mapped XM routines about
a week before you load this release. That way you wouldn't need to shutdown
ZSLOT or shutdown/restart DSM configurations.
1. Users may NOT be on the system during installation of this release.
2. DSM Sites: disable mapping for all MailMan routines.
3. Retrieve the MailMan 8.0 KIDS build (XM8.KID) via FTP from one of the
Anonymous Directories by following the instructions in the MailMan 8.0
Release Message.
4. On the KIDS:Installation menu, use the following option to load the
queue, the 'X' changes the transmit priority. The difference is the
build into a Transport Global on your system:
Load a Distribution
Enter a Host File: E:\INETPUB\FTPROOT\XM8.KID or USR$:[USER.NAME]XM8.KID
========================== =======================
(How you answer the above prompt depends on the system you're on and where
you placed the build you retrieved in the previous step. The answers
shown are examples only.)
5. Users should not be on the system.
Place TaskMan in a WAIT state.
You may also wish to shut down HL7 filers/LLP's and other background
context, and writers of MailMan front-ends should take note!)
tasks which may attempt to create new messages.
6. On the Manage MailMan:Local Delivery Management menu, use the following
option to stop the background filer:
STOP background filer
Are you sure you want Background Filers to stop delivering mail? No// YES
===
<< Background Filers will stop soon. >>
7. On the KIDS:Installation menu, use the following options to install the
Transport Global:
Verify Checksums in Transport Global
Print Transport Global
Compare Transport Global to Current System
Backup a Transport Global
Install Package(s)
Select INSTALL NAME: MAILMAN 8.0 Loaded from Distribution <date/time>
===========
Install Questions for MAILMAN 8.0
Incoming Files:
4. MailMan date/times are now in a standard format, produced by the Kernel
3.4 COMMUNICATIONS PROTOCOL
Note: You already have the 'COMMUNICATIONS PROTOCOL' File.
3.6 BULLETIN
Note: You already have the 'BULLETIN' File.
3.7 MAILBOX
Note: You already have the 'MAILBOX' File.
3.73 MESSAGES TO BE NEW AT A LATER DATE
API: $$FMTE^XLFDT(datetime,"2Z"). Previously, 3020803.153204 would be
Note: You already have the 'MESSAGES TO BE NEW AT A LATER DATE' File.
3.8 MAIL GROUP
Note: You already have the 'MAIL GROUP' File.
3.816 DISTRIBUTION LIST
Note: You already have the 'DISTRIBUTION LIST' File.
3.9 MESSAGE
Note: You already have the 'MESSAGE' File.
suite of data dictionaries, but it does not populate the files. This
displayed as '03 Aug 02 15:32'. Now, it is displayed as '08/03/02@15:32'.
4.2 DOMAIN
Note: You already have the 'DOMAIN' File.
4.281 INTER-UCI TRANSFER
Note: You already have the 'INTER-UCI TRANSFER' File.
4.2996 INTERNET SUFFIX
Note: You already have the 'INTERNET SUFFIX' File.
This change is also carried through to all MailMan APIs which return
4.2997 REMOTE USER DIRECTORY
Note: You already have the 'REMOTE USER DIRECTORY' File.
4.2998 MESSAGE DELIVERY STATS
Note: You already have the 'MESSAGE DELIVERY STATS' File.
4.2999 MESSAGE STATISTICS
Note: You already have the 'MESSAGE STATISTICS' File.
4.3 MAILMAN SITE PARAMETERS
date/time in MailMan format. Users of such APIs should take note!
Note: You already have the 'MAILMAN SITE PARAMETERS' File.
4.4 MAILMAN TIME ZONE
Note: You already have the 'MAILMAN TIME ZONE' File.
4.501 NETWORK SENDERS REJECTED
Note: You already have the 'NETWORK SENDERS REJECTED' File.
4.6 TRANSMISSION SCRIPT
Note: You already have the 'TRANSMISSION SCRIPT' File.
Incoming Mail Groups:
Enter the Coordinator for Mail Group 'XM SUPER SEARCH': <Your site's ISO>
=================
Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// YES
===
Want KIDS to INHIBIT LOGONs during the install? YES// YES
===
Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO
5. MailMan remote message IDs now include the message date, to ensure that
==
Enter the Device you want to print the Install messages.
You can queue the install by enter a 'Q' at the device prompt.
Enter a '^' to abort the install.
DEVICE: HOME// <Don't queue this>
------------------
8. Remove TaskMan from WAIT State. If you shut down HL7 filers/LLPs or
any other background tasks, you may restart them.
9. Start the background filer.
if you are told that a message is a duplicate of a previously received
On the Manage MailMan:Local Delivery Management menu, use the following
option to start the background filer:
START background filer
<< Background Filers will start soon. >>
10. Ensure that the new fields in file 4.3, MAILMAN SITE PARAMETERS, are
correctly entered:
8.22 DNS AWARE Yes or No?
8.23 TCP/IP COMMUNICATIONS PROTOCOL Points to file 3.4
8.24 TCP/IP TRANSMISSION SCRIPT Points to file 4.6
11. DSM Sites: If your site maps routines, then rebuild your map set.
message, it really is. Sites will no longer have problems sending messages
Many routines have become obsolete and should be removed from the map
set. Here is a new recommended list of routines to map, should your
site choose to map routines:
Minimum Additional
------- ----------
XM XMC1A,XMC1B
XMC1 XMK*
XMJ* XML
XMR XMR1,XMR2,XMR3*
XMS XMS1,XMS2,XMS3
from a production account to a test account which was created by "mirroring"
XMT*
XMVVITAE
XMXADDR*
XMXSEC*
XMXUTIL*
===========================================================================
the production account. The remote message ID is now the message number
following by a period, followed by the 7-digit FileMan message creation
version expects that a site already has MailMan 7.1 installed and running,
date. Before, a remote message ID might be 34561234@DOMAIN.EXT. Now it
would be 34561234.3020803@DOMAIN.EXT.
6. The ^XMC*, ^XMR*, ^XMS* suite of routines, which are responsible for
scheduling, transmitting to, and receiving messages from remote sites, have
been completely overhauled to make them easier to understand and easier to
maintain.
7. MailMan will no longer display user names by taking them directly from
the .01 field of the NEW PERSON file, 200. The API, $$NAMEFMT^XLFNAME,
and that it is patched through XM*7.1*198. It is also expected that
supplied as part of the Name Standardization project, is used, instead.
Thus, the names of people whose last names, for instance, contain periods,
apostrophes, or spaces, are properly displayed (ST. IVES, O'MALLEY, and
VAN DYKE), instead of improperly (STIVES, OMALLEY, and VANDYKE).
8. In response to NOIS FAV-0202-71819, messages with responses may no longer
be forwarded to broadcast to all users. Such messages may have important
information in the responses, and as we all know, responses are not auto-
forwarded to remote sites for users with auto-forward addresses. Users who
attempt to broadcast messages with responses will be encouraged to copy the
Kernel 8.0 and FileMan 22.0 are installed and are reasonably up-to-date
message and its responses into a new message, which can be broadcast.
9. Incoming PackMan and KIDS messages are no longer subject to the
restriction NETWORK - MAX LINES RECEIVE (field 8.31, file 4.3). Other kinds
of messages continue to be subject to that restriction.
10. If a task transmitting messages to another site fails and has to be
requeued, it really is requeued. Previously, that wasn't true. Previously,
the failing task queued up a new task to take its place, and then the
failing task stopped.
|
