Sample MSF Dump and POP Journal of an E-Mail Message

Troubleshooting

Problem

A sample MSF dump and POP journal is included in this document.

Resolving The Problem

This example was created by sending a SMTP/MIME note from an IBM Domino for AS/400 user to an IBM OS/400 POP user using the MTA. (POP to POP would be similar.)

A break out of the MSF List entries follows the dump.

Refer to the following manual for further details:

IBM Redbooks AnyMail/400 Mail Server Framework Developer Guide (GG24-4449)

MSF Dump

5769SS1 V4R2M0 980228 AS/400 DUMP 013973/QMSF/QMSF 01/30/98 13:53:58 PAGE 1 > MSF MESSAGE FORMATTED DUMP MSGID: ID 100304G9801301353030000000001 AT EXIT POINT : QIBM_QZMFMSF_ACT
> > > > >MSF FORMAT CRTA0100 000000 00000030 00000030 C3D9E3C1 F0F1F0F0 0000001C 00000001 00000000 * CRTA0100 *

> 000000 F0F9F8F0 F1F3F0F1 F3F5F3F0 F3F4F5F9 F0F2C2F1 *098013013530345902B1
> > >MSF FORMAT ORGL0100 originator list
000000 00000064 00000064 D6D9C7D3 F0F1F0F0 0000001C 00000001 00000000 * À ÀORGL0100 * > 000000 00000048 00000020 00000028F0F1C2F0 000001F4 00000001 00000000 00000000 * ç 01B0 4 *
   ^ address type is 01B0 - SMTP
000020 D596A385 A26DC16D C4899393 8995877C D9C3C8C1 E2C5E2D7 4BD9C3C8 D3C1D5C4 *Notes_A_Dilling@RCHASESP.RCHLAND* 000040 4BC9C2D4 4BC3D6D4 < originator address *.IBM.COM * > > >MSF FORMAT RCPL0100 recipient list (can include multiple recipients)
000000 00000081 00000081 D9C3D7D3 F0F1F0F0 0000001C 00000001 00000000 * a aRCPL0100 * > 000000 00000065 00000059 0000000C 00000038 00000021 F0F1C2F0 000001F4 00000000 * Á ß 01B0 4 *
Address type is 01B0(SMTP)-^
000020 00000000 F0F2C1C6 00000003 00000000 00000001 00000000 84848993 93899587 * 02AF ddilling*
Msg type02AF Sys Msg Store-^ ^-Status is 03=Local
000040 7C998388 81A285A2 974B9983 88938195 844B8982 944B8396 94C4C4C9 D3D3C9D5 *@rchasesp.rchland.ibm.comDDILLIN* 000060 C7000000 00 *G * > > > >MSF FORMAT ENVL0100 03B0 MIME envelope (notice path to message "file") 000000 000000B0 000000B0 C5D5E5D3 F0F1F0F0 0000001C 00000002 00000000 * ^ ^ENVL0100 * > 000000 00000048 0000001C 0000002C F0F3C2F0 00000001 00000000 00000000 61D8C9C2 * ç 03B0 /QIB*
000020 D461E4E2 C5D9C4C1 E3C161D3 D6E3E4E2 61E2D4E3 D7D4E3C1 61A39497 61D8C1C3 *M/USERDATA/LOTUS/SMTPMTA/tmp/QAC* 000040 E7F1C7F0 D9F4D500 *X1G0R4N * > *...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8....+....9....+....0....+....1....+....2....+ 000000 0000004C 0000001C 00000030 F0F3C1C6 00000002 00000000 00000000 00000024 * < 03AF * 000020 0000000C 00000003 0000000C 0000000A 00000001 0000000C 00000005 00000000 * * 000040 0000000C 00000016 00000001 * * > >
> >MSF FORMAT RCHL0100recipient history list (will record changes to the original address such as SMTP alias to OV/400 user)
000000 00000081 00000081 D9C3C8D3 F0F1F0F0 0000001C 00000001 00000000 * a aRCHL0100 * > 000000 00000065 00000059 0000000C 00000038 00000021 F0F1C2F0 000001F4 F0F2C1C6 * Á ß 01B0 402AF* 000020 00000003 00000000 00000001 00000000 00000000 00000000 84848993 93899587 * ddilling* 000040 7C998388 81A285A2 974B9983 88938195 844B8982 944B8396 94C4C4C9 D3D3C9D5 *@rchasesp.rchland.ibm.comDDILLIN* 000060 C7000000 00 *G * >
> > >MSF FORMAT ATTL0100 attachment list
000000 00000064 00000064 C1E3E3D3 F0F1F0F0 0000001C 00000001 00000000 * À ÀATTL0100 * > PAGE 000000 00000048 0000001C 0000002CF0F4C2F7 00000001 00000000 00000000 61D8C9C2 * ç 04B7 /QIB*
"Fake" MIME attachment-^
000020 D461E4E2 C5D9C4C1 E3C161D3 D6E3E4E2 61E2D4E3 D7D4E3C1 61A39497 61D8C1C3 *M/USERDATA/LOTUS/SMTPMTA/tmp/QAC*
000040 E7F1C7F0 D9F4D500 *X1G0R4N * > > > >MSF FORMAT MSGL0100Msg type = system msg store 02AF i.e. local POP3 or as-pop3. Along with the recipient status
this decides which exit will deliver the mail
000000 00000020 00000020 D4E2C7D3 F0F1F0F0 0000001C 00000001 00000000 * MSGL0100 * > 000000 F0F2C1C6 *02AF *
> > > >MSF FORMAT EXCH0100exit history list: Note that only SMTP addr resolution was called.
000000 00000214 00000214 C5E7C3C8 F0F1F0F0 0000001C 00000006 00000000 * EXCH0100 * > 000000 D8C9C2D4 6DD8E9D4 C6D4E2C6 6DC1C4D9 6DD9E2D3 D8E3D4D4 C1C4D9E2 4040D8E3 *QIBM_QZMFMSF_ADR_RSLQTMMADRS QT* 000020 C3D74040 40404040 00000514 F0F9F8F0 F1F3F0F1 F3F5F3F0 F6F1F7F3 F0F9F8F0 *CP 09801301353061730980*
   Timestamp called -^----------------------------------^ ^-------
000040 F1F3F0F1 F3F5F3F4 F3F2F8F8 00000000 F1404040 *130135343288 1
Time of exit ------------^ rc ^-Change indicator: 1 (F1) - changes were made
> 000000 D8C9C2D4 6DD8E9D4 C6D4E2C6 6DC5D5D3 6DD7E2E2 D8E3D4D4 C5D5E540 4040D8E3 *QIBM_QZMFMSF_ENL_PSSQTMMENV QT* 000020 C3D74040 40404040 00000514 F0F9F8F0 F1F3F0F1 F3F5F3F4 F4F7F1F8 F0F9F8F0 *CP 09801301353447180980* 000040 F1F3F0F1 F3F5F3F4 F5F3F5F1 00000000 F0404040 *130135345351 0 * > 000000 D8C9C2D4 6DD8E9D4 C6D4E2C6 6DC1E3E3 6DC3D5E5 D8E3D4D4 C1E3C3E5 4040D8E3 *QIBM_QZMFMSF_ATT_CNVQTMMATCV QT* 000020 C3D74040 40404040 00000514 F0F9F8F0 F1F3F0F1 F3F5F3F4 F5F5F5F8 F0F9F8F0 *CP 09801301353455580980*
000040 F1F3F0F1 F3F5F3F4 F5F8F5F6 00000000 F0404040 *130135345856 0 * > 000000 D8C9C2D4 6DD8E9D4 C6D4E2C6 6DD3C3D3 6DC4C5D3 D8E3D4D4 D3C3D3C4 4040D8E3 *QIBM_QZMFMSF_LCL_DELQTMMLCLD QT* 000020 C3D74040 40404040 00000514 F0F9F8F0 F1F3F0F1 F3F5F3F4 F6F0F0F8 F0F9F8F0 *CP 09801301353460080980* 000040 F1F3F0F1 F3F5F3F4 F8F0F2F6 00000000 F0404040 *130135348026 0 * > 000000 D8C9C2D4 6DD8E9D4 C6D4E2C6 6DC1E3E3 6DD4C7E3 D8E9C4E2 D5D7C1D4 4040D8E2 *QIBM_QZMFMSF_ATT_MGTQZDSNPAM QS* 000020 E8E24040 40404040 000003E8 F0F9F8F0 F1F3F0F1 F3F5F3F4 F9F3F3F3 F0F9F8F0 *YS Y09801301353493330980* 000040 F1F3F0F1 F3F5F3F4 F9F3F5F8 00000000 F1404040 *130135349358 1 *
> 000000 D8C9C2D4 6DD8E9D4 C6D4E2C6 6DC1E3E3 6DD4C7E3 D8E3D4D4 C1E3E3D4 4040D8E3 *QIBM_QZMFMSF_ATT_MGTQTMMATTM QT* 000020 C3D74040 40404040 00000514 F0F9F8F0 F1F3F0F1 F3F5F3F4 F9F5F9F0 F0F9F8F0 *CP 09801301353495900980* 000040 F1F3F0F1 F3F5F3F5 F1F1F7F3 00000000 F1404040 *130135351173 1 * > > > > END DUMP OF MSF MESSAGE MSGID: ID 100304G9801301353030000000001

Pop3 Journal

The POP3 Journal provides a good, easy-to-read summary of the information contained in the MSF dump. Also, it appends a mail message's information to the log file, rather than creating one spooled file per mail message. It includes:

ID internal message id
ENV Location of the envelope/attachments in the file system
To Recipient Address
ADR The Address type it was resolved to. An address lookup in the SDD sets the message type
MSG The message type (which, with status, determines the program used to deliver the mail)
ST The address status (LCL-local, FWD - forwarding or remote, NONDEL - Nondelivery)
FROM Originator

ID 100304G9801301353030000000001 ENV=/QIBM/USERDATA/LOTUS/SMTPMTA/tmp/QACX1G0R4N NOTE=/QIBM/USERDATA/LOTUS/SMTPMTA/tmp/QACX1G0R4NTO =ddilling@rchasesp.rchland.ibm.com ADR=01B0 SMTP MSG=02AF SMTP ST=LCL FROM=Notes_A_Dilling@RCHASESP.RCHLAND.IBM.COM ADR=01B0 SMTP

Useful MSF List Breakdowns (from AnyMail Redbooks)

http://www.ibm.com/i/c.gif" /> Recipient List
5.9.1 Recipient List Entry

Each list entry contains the address of one recipient of the message and other information about that recipient.
```
___________ ____________ ______________________________________________________  

|   Offset  |            |                                                     | 

|_____ _____|            |                                                     | 

| Dec | Hex | Type       | Field                                               | 

|_____|_____|____________|_____________________________________________________| 

|  0  |  0  | BINARY(4)  | Length of this entry                                | 

|_____|_____|____________|_____________________________________________________| 

|  4  |  4  | BINARY(4)  | Displacement to the SPIN from the beginning of this | 

|_____|_____|____________|_list entry__________________________________________| 

|  8  |  8  | BINARY(4)  | Length of exit point program (snap-in) provided     | 

|_____|_____|____________|_information (SPIN)__________________________________| 

|  12 |  C  | BINARY(4)  | Displacement of the recipient address from the      | 

|_____|_____|____________|_beginning of this entry_____________________________| 

|  16 |  10 | BINARY(4)  | Length of recipient address                         | 

|_____|_____|____________|________________________________________________    _| 

|  20 |  14 | CHAR(4)    | Address type                                        | 

|_____|_____|____________|_____________________________________________________| 

|  24 |  18 | BINARY(4)  | Recipient address coded character set identifier    | 

|_____|_____|____________|_(CCSID)___________________________________________ _| 

|  28 |  1C | BINARY(4)  | Reason code                                         | 

|_____|_____|____________|_____________________________________________________| 

|  32 |  20 | BINARY(4)  | Diagnostic code                                     | 

|_____|_____|____________|_____________________________________________________| 

|  36 |  24 | CHAR(4)    | Message type                                        | 

|_____|_____|____________|_____________________________________________________| 

|  40 |  28 | BINARY(4)  | Status                                              | 

|_____|_____|____________|_____________________________________________________| 

|  44 |  2C | BINARY(4)  | Reserved (formerly used for Distribution Type -     | 

|_____|_____|____________|_see Original Recipient List)________________________| 

|  48 |  30 | BINARY(4)  | Unique identifier                                   | 

|_____|_____|____________|_________________________________________________ ___| 

|  52 |  34 | BINARY(4)  | Unique identifier of referenced entry               | 

|_____|_____|____________|_____________________________________________________| 

|  56 |  38 | BINARY(4)  | Reserved (set to zero)                              | 

|_____|_____|____________|_____________________________________________________| 

|  *  |  *  | CHAR(*)    | Recipient address                                   | 

|_____|_____|____________|_____________________________________________________| 

|  *  |  *  | CHAR(*)    | Exit point program (snap-in) provided information   | 

|_____|_____|____________|_(SPIN)____________________________________________ _| 
```
Field Descriptions

Length of this entry. The length in bytes of this entry. This is used to get to the next entry.

Displacement to the SPIN from the beginning of this list entry. The displacement from the beginning of this entry to the exit point program (snap-in) provided information (SPIN).

Length of the exit point program (snap-in) provided information (SPIN). The length in bytes of the exit point program provided information (SPIN). The maximum length of the SPIN is 256 bytes.

Displacement of the recipient address from the beginning of this entry. The displacement from the beginning of this entry to the recipient address in this entry.

Length of the recipient address. The length of the recipient address for this entry. The maximum length of a recipient address is 1024 bytes.

Address type. The type of recipient address.

Recipient address coded character set identifier (CCSID). The CCSID provided for the recipient address. Valid values for the CCSID are 1 through 65533 and 65535.

Reason code. A code that identifies reasons that are associated with the message delivery to this recipient. In the case of a non-delivered entry, this field contains the reason the delivery of this message to this recipient failed. MSF assumes the reason code contains the X.400 non-delivery reason code.

The reason code and diagnostic code fields are assumed by MSF to contain values that are documented in CCITT Data Communication Networks Message Handling Systems 1988 Recommendation for X.400-X.420 for the Non-delivery-reason-code field and the Non-delivery-diagnostic-code field.

Diagnostic code. A code that indicates the cause of a problem where the delivery of a message to this address failed. MSF assumes the diagnostic code contains the X.400 non-delivery diagnostic code.

Message type. The type of message that is associated with the entry.

Status. The status that is associated with each recipient entry. This information is used by the framework to determine which exit point is to be processed between local delivery, message forwarding and non-delivery. The possible values are:

1 Forwarded (remote)

2 Ignore

3 Local

4 Non-deliverable

5 Security violation

Reserved (formerly used for Distribution Type). All reserved fields are zero.

Note: The first reserved field was originally used to hold a distribution type. This attribute has been moved to the original recipient list.

Unique identifier. An identifier that differentiates each entry within a particular list. Identifiers are generated by MSF for each list entry either when the list is created or when list entries are added as the MSF message is changed. List entries are numbered such that unique identifiers are in ascending order.

Unique identifier of a referenced entry. The unique identifier of another entry in this list to which this entry refers. You can use this when adding or changing entries in this list to create entry cross references. The most common example is to indicate that a list entry that is added to the list is a logical replacement or mapping of another list entry.

Recipient address. A string that represents the address associated with the recipient of the message. The contents and format of the string are not defined by the mail server framework. It is assumed that the address type associated with the recipient address defines the contents of the recipient address field.

Exit point program (snap-in) provided information (SPIN). An area where exit point programs can store information that other exit point programs may use. SPIN provides a place where information relating to a specific recipient can be stored and used by exit point programs in the same or different exit points. This information is defined by the mail application that sets the SPIN information.

A common use of SPIN is when a specific type of attribute needs to be applied to a subset of the recipients of a message but the address, status, and message types cannot be used. For example, a subset of the recipients of an E-mail message may be fanned out to sets of queues that are known to a message forwarding exit point program. The subset of recipients that go onto the same queue all have that queue name in common. The queue name could be put into their SPIN data by an address resolution exit point program to be used by a message forwarding exit point program to distribute the E-mail message.

--------------------------------------------------------------------------------
© Copyright IBM Corp. 1995
--------------------------------------------------------------------------------

IBM BookManager BookServer Copyright 1989, 1996 IBM Corporation. All rights reserved.

1	Forwarded (remote)
2	Ignore
3	Local
4	Non-deliverable
5	Security violation

[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"6.1.0"}]

Historical Number

11292550

Was this topic helpful?

Document Information

Modified date:
14 May 2024

UID

nas8N1018427

Tips