| Title: | MAILBUS 400 User Forum |
| Notice: | kits 100-109 - Infocenter //www.digital.com/info/messaging |
| Moderator: | IOSG::MARSHALL |
| Created: | Thu Jun 11 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3210 |
| Total number of notes: | 9174 |
Hi!
Have set up an mts transfer connection to an admd. As we still
are going to deliver messages to 84-MTA's and the admd-provider
only support limited downgrade I like the Mailbus 400 (UNIX) to do
the downgrade.
I have performed tests on this by specifying the admd as having
IMP-84 recipients.
Results:
- we do downgrade P22 to P2,
- we do downgrade a commonname to s and g in the message header,
- we dont downgrade commonname in the envelope.
As the admd provider do downgrade cn-attribute in the P1 envelope
this should work. But the provider also claims that a message which
contains cn IS a P22 IMPS message and that they dont do the downgrade
of P22, so it could still be a problem to deliver it to 84UA's.
As my customer only uses s and g for addressing today this shouldn't
be a problem, but anyway Im curious about this.
The Tuning... (6.1.1) do state that we downgrade the commonname. But
on the attached decoding you can see that we dont, as with the
envelope. Is here something I have misinterpreted so let me know.
Best regards
Jan-Ake
CONTEXT 0
<Message>
SET
<TransferEnvelope>
MTS_ID
<MTS Identifier>
GDI
COUNTRY
PRINTABLE Len 2
"se" Hex 73 65
ADMD
PRINTABLE Len 6
"400net"
PRINTABLE Len 8
"ericsson"
IA5 Len 24
<LocalId>
"68A4C78011D075C700080DB1"
ORNAME
<Originator>
SEQ
<StandardAttributes>
COUNTRY
PRINTABLE Len 2
"se" Hex 73 65
ADMD
PRINTABLE Len 1
" " Hex 20
CONTEXT 2
<PrivateDomainName>
PRINTABLE Len 8
"ericsson"
SET
<ORname Extensions>
SEQ
CONTEXT 0 Len 1
Hex 1 Dec 1
CONTEXT 1
<CommonName (Printable)>
PRINTABLE Len 19
"testcommon testname"
EITS
<EITs>
CONTEXT 0 Len 2
<BuiltinEits>
" " Hex 20
BUILTIN Len 1
<ContentType (built-in)>
Hex 2 Dec 2
PRIORITY Len 1
<Priority>
Hex 0 Dec 0
MSG_IND Len 2
<MessageIndicators>
Hex 80
CONTEXT 2
<Recipients>
SET
ORNAME
SEQ
<StandardAttributes>
COUNTRY
PRINTABLE Len 2
"nl" Hex 6e 6c
ADMD
PRINTABLE Len 5
"40net" Hex 34 30 6e 65 74
CONTEXT 3 Len 4
<OrganizationalName>
"oint" Hex 6f 69 6e 74
CONTEXT 0 Len 1
<OriginallySpecifiedRecipientNo>
Hex 1 Dec 1
CONTEXT 1 Len 2
<PerRecipientIndicators>
Hex a8
CONTEXT 3
<Extensions>
SEQ
CONTEXT 0 Len 1
<Extension>
Hex 6 Dec 6
<RequestedDeliveryMethod>
CONTEXT 1 Len 2
<Criticality>
Hex 00
CONTEXT 2
SEQ
INTEGER Len 1
Hex 0 Dec 0
TRACE
<TraceInformation>
SEQ
GDI
COUNTRY
PRINTABLE Len 2
"se" Hex 73 65
ADMD
PRINTABLE Len 6
"400net"
PRINTABLE Len 8
"ericsson"
SET
<DomainSuppliedInfo>
CONTEXT 0 Len 13
<ArrivalTime>
"970124085410Z"
CONTEXT 2 Len 1
<RoutingAction>
Hex 0 Dec 0
OCTETSTRING Len 283
<Content>
Hex a0 80 31 80 6b 80 13 06 41 42 43 31 32 33 00 00
a0 80 60 80 30 80 61 80 13 02 73 65 00 00 62 80
13 01 20 00 00 a2 80 13 08 65 72 69 63 73 73 6f
6e 00 00 a5 80 80 08 54 65 73 74 4e 61 6d 65 81
0a 54 65 73 74 43 6f 6d 6d 6f 6e 00 00 00 00 30
80 30 80 13 06 43 6f 6d 6d 6f 6e 13 13 74 65 73
74 63 6f 6d 6d 6f 6e 20 74 65 73 74 6e 61 6d 65
00 00 00 00 00 00 00 00 a2 80 31 80 a0 80 60 80
30 80 61 80 13 02 6e 6c 00 00 62 80 13 05 34 30
6e 65 74 00 00 83 04 6f 69 6e 74 00 00 00 00 00
00 81 02 00 00 82 01 00 00 00 00 00 a8 80 14 28
54 65 73 74 20 74 6f 20 64 6f 77 6e 67 72 61 64
65 20 74 68 65 20 63 6e 2d 61 74 74 72 69 62 75
74 65 20 69 6e 20 50 31 00 00 8c 01 01 8d 01 01
8e 01 00 00 00 30 80 a0 80 31 80 80 01 05 00 00
16 23 49 67 6e 6f 72 65 20 74 68 69 73 2c 20 6a
75 73 74 20 61 6e 6f 74 68 65 72 20 74 65 73 74
2e 0d 0a 0d 0a 00 00 00 00 00 00
CONTEXT 0
<IPM>
SET
<Heading>
IPM_ID
PRINTABLE Len 6
<UserRelativeId>
"ABC123"
CONTEXT 0
<Originator>
ORNAME
SEQ
<StandardAttributes>
COUNTRY
PRINTABLE Len 2
"se" Hex 73 65
ADMD
PRINTABLE Len 1
" " Hex 20
CONTEXT 2
<PrivateDomainName>
PRINTABLE Len 8
"ericsson"
CONTEXT 5
<PersonalName>
CONTEXT 0 Len 8
<surname>
"TestName"
CONTEXT 1 Len 10
<given-name>
"TestCommon"
SEQ
<DDAs>
SEQ
PRINTABLE Len 6
<Type>
"Common"
PRINTABLE Len 19
<Value>
"testcommon testname"
CONTEXT 2
<PrimaryRecipients>
SET
CONTEXT 0
<ORDescriptor>
ORNAME
SEQ
<StandardAttributes>
COUNTRY
PRINTABLE Len 2
"nl" Hex 6e 6c
ADMD
PRINTABLE Len 5
"40net" Hex 34 30 6e 65 74
CONTEXT 3 Len 4
<OrganizationalName>
"oint" Hex 6f 69 6e 74
CONTEXT 1 Len 2
<NotificationRequest>
Hex 00
CONTEXT 2 Len 1
<ReplyRequested>
Boolean FALSE
CONTEXT 8
<Subject>
TTX Len 40
"Test to downgrade the cn-attribute in P1"
CONTEXT 12 Len 1
<Importance>
Hex 1 Dec 1
CONTEXT 13 Len 1
<Sensitivity>
Hex 1 Dec 1
CONTEXT 14 Len 1
<AutoForwarded>
Boolean FALSE
SEQ
<Body>
CONTEXT 0
<IA5Text>
SET
CONTEXT 0 Len 1
<Repertoire>
Hex 5 Dec 5
IA5 Len 35
"Ignore this, just another test.
"
`
#
[Posted by WWW Notes gateway]
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3118.1 | P2 and P22 are Content Protocols | ZUR01::ASHG | Grahame Ash @RLE | Fri Jan 24 1997 09:47 | 14 |
I think what's happening here is that you've declared your recipients can only receive P2 and 84 bodyparts, so the MTA is downgrading the content from P22 to P2 for you. But you have the Application Context in the peer mta entity defined as MTS Transfer, so the MTA is using P0-1988. Note that P0 is the envelope protocol - P22 and P2 are the CONTENT protocols. So everything seems to be working as you want. If the ADMD doesn't want to downgrade the common names (and the other 88 extensions e.g. Criticality) on the envelope, then you'll have to see the Application Context to MTS Transfer Protocol 1984 - then the MTA will downgrade the envelope as well for you. grahame | |||||
| 3118.2 | What about mts transfer ptocol? | NETRIX::"[email protected]" | jan-ake olsson @ugo | Fri Jan 24 1997 10:24 | 8 |
Hi!
What about mts-transfer protocol, how does that treat the enevope,
is it still P0-88?
Regards
Jan-Ake
[Posted by WWW Notes gateway]
| |||||
| 3118.3 | ZUR01::ASHG | Grahame Ash @RLE | Fri Jan 24 1997 11:04 | 11 | |
>What about mts-transfer protocol, how does that treat the enevope, >is it still P0-88? Yes - that's for sending 1988 over a Session connection. have a look at the help in ncl> help mta peer mta characteristics application or 4.3 of Tuning and PS. grahame | |||||
| 3118.4 | Conclusion | NETRIX::"[email protected]" | jan-ake olsson @ugo | Fri Jan 24 1997 11:58 | 6 |
So if we do face some problem regarding the envelope and the admd downgrade, it wouldn't have been any difference if using mts transfer or mts-transfer-protocol? Regards Jan-Ake [Posted by WWW Notes gateway] | |||||
| 3118.5 | IJSAPL::DEWIJK | GJ from the Dutchlands | Fri Jan 24 1997 14:09 | 3 | |
Right!
GJ
| |||||