| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 185.1 | MRMRPL=256 looks strange | STKHLM::OLSSON | Anders Olsson, SIP Sweden | Wed Sep 01 1993 18:52 | 28 |
|
.0> Report 1.
.0> Actual Recipient: (MEX.IBMMAIL.I1001676@MEMO@GOLF)
.0> (*MRMRLP=256)
.0> Message NOT DELIVERED, reason is: Unable to transfer.
.0> Diagnostic:
.0> Failure report generated at:
Is the message sent to a single recipient from TEAMLINKS or is there a
(long) distribution list?
The item (*MRMRLP=256) in the non-delivery indicates that the adressee
has position 256 in a long distribution list, which is a lot more than
MEMO accepts. On the other hand, I guess you have tried to send *only*
to this single recipient and still have a problem.
Have you tried to send to the same destination address from anything else
but TEAMLINKS (e.g. VMSmail through MRGATE or from ALL-IN-1 IOS)?
The number 256 looks suspicious since it is an even power of 2. Maybe
TEAMLINKS does something funny here.
I'm a bit busy for the moment, but I'll try to test if MEMO or MRMEMO
have any objections to the receiver list position value 256.
Do you think you could catch the .NBS files on MRMEMO$DIR of this message?
If I can't reproduce the problem, the .NBS files would certainly help.
Anders
|
| 185.2 | | YUPPY::CARTER | Windows on the world... | Thu Sep 02 1993 12:30 | 143 |
| Hi
We are getting the problem sending to only that user so I don't think
the problem is distribution list.
Here is the NBS file....
Christine
.....................................................
File DISK$USER2:[MB$.MR.MSG1]MR2664.SAV;1 contains ****** bytes.
000007 1 MSG[V2ENV] Len=000302
00000E 2 FIELD[MID] Len=00001E
000010 3 ASCII Len=00001C
"1101141002091993/A20703/GOLF
000033 2 FIELD[PDATE] Len=000012
000035 3 DATE Len=000010
000037 4 ASCII Len=00000E
"19930902101401
00004C 2 FIELD[PREC] Len=000003
00004E 3 INT Len=000001
%01
000056 2 FIELD[SENDER] Len=000033
00005D 3 ENT[NAME] Len=00002C
000063 4 SEQ Len=000000
000069 4 SEQ Len=000020
000070 5 ATTR[ROUTE] Len=00000A
000076 6 SEQ Len=000004
000078 7 ASCII Len=000002
"AM
000081 5 ATTR[USERID] Len=000008
000083 6 ASCII Len=000006
"SYSTEM
000090 2 FIELD[TO] Len=000064
000096 3 SEQ Len=00005E
00009D 4 ENT[NAME] Len=000057
0000A3 5 SEQ Len=000000
0000A9 5 SEQ Len=000030
0000B0 6 ATTR[ROUTE] Len=00000C
0000B6 7 SEQ Len=000006
0000B8 8 ASCII Len=000004
"MEMO
0000C3 6 ATTR[USERID] Len=000016
0000C5 7 ASCII Len=000014
"MEX.IBMMAIL.I1001676
0000E0 5 ATTR[PERRECFLG] Len=000007
0000E3 6 BITS[%00] Len=000004
%A8000000
0000EE 5 ATTR[EXTENTNID] Len=000006
0000F0 6 INT Len=000004
%00000001
0000FD 2 FIELD[UACONTID] Len=00000E
0000FF 3 ASCII Len=00000C
"1179128D3500
000114 2 FIELD[PERMSGFLG] Len=000007
000117 3 BITS[%00] Len=000004
%30000000
000124 2 FIELD[CONTENTDIA] Len=000003
000126 3 INT Len=000001
%02
000130 2 FIELD[ITRACE] Len=000084
000136 3 SEQ Len=00003D
00013F 4 FIELD[MTA] Len=000006
000141 5 ASCII Len=000004
"GOLF
00014E 4 FIELD[ARVDATE] Len=000016
000154 5 DATE Len=000010
000156 6 ASCII Len=00000E
"19930902101401
00016D 4 FIELD[ACTION] Len=000006
00016F 5 INT Len=000004
%00000000
000179 3 SEQ Len=00003B
000182 4 FIELD[MTA] Len=00000B
000184 5 ASCII Len=000009
"GOLF.MUAS
000196 4 FIELD[ARVDATE] Len=000012
000198 5 DATE Len=000010
00019A 6 ASCII Len=00000E
"19930902101401
0001B1 4 FIELD[ACTION] Len=000003
0001B3 5 INT Len=000001
%00
0001BD 2 FIELD[HOPCOUNT] Len=000006
0001BF 3 INT Len=000004
%00000001
0001CA 2 MSG[V2CONT] Len=00013F
0001D3 3 FIELD[APPMID] Len=00002B
0001D5 4 ASCII Len=000029
"1101141002091993/A20703/GOLF/1179128D3500
000205 3 FIELD[FROM] Len=000048
00020C 4 ENT[NAME] Len=000041
000212 5 SEQ Len=000000
000218 5 SEQ Len=000026
00021F 6 ATTR[ROUTE] Len=000010
000225 7 SEQ Len=00000A
000227 8 ASCII Len=000004
"GOLF
00022D 8 ASCII Len=000002
"AM
000236 6 ATTR[USERID] Len=000008
000238 7 ASCII Len=000006
"SYSTEM
000245 5 ATTR[FREEFORM] Len=000008
000247 6 ASCII Len=000006
"SYSTEM
000254 3 FIELD[TO] Len=00005D
00025A 4 SEQ Len=000057
000261 5 ENT[NAME] Len=000050
000267 6 SEQ Len=000000
00026D 6 SEQ Len=000036
000274 7 ATTR[ROUTE] Len=000012
00027A 8 SEQ Len=00000C
00027C 9 ASCII Len=000004
"GOLF
000282 9 ASCII Len=000004
"MEMO
00028D 7 ATTR[USERID] Len=000016
00028F 8 ASCII Len=000014
"MEX.IBMMAIL.I1001676
0002AA 6 ATTR[REPORTREQ] Len=000007
0002AD 7 BITS[%00] Len=000004
%E0000000
0002B8 3 FIELD[SUBJ] Len=000006
0002BA 4 ASCII Len=000004
"Test
0002C5 3 FIELD[PREC] Len=000003
0002C7 4 INT Len=000001
%01
0002D1 3 FIELD[SENSTVTY] Len=000003
0002D3 4 INT Len=000001
%03
0002DD 3 FIELD[FORWDED] Len=000003
0002DF 4 INT Len=000001
%00
0002E7 3 VEND[RRECPT] Len=000000
0002EE 3 FIELD[ATTACH] Len=00001B
0002F5 4 MSG[TEXT] Len=000014
0002FB 5 ASCII Len=00000E
"Test message
000309 0End of file
|
| 185.3 | It works for me... | STKHLM::OLSSON | Anders Olsson, SIP Sweden | Thu Sep 02 1993 20:34 | 42 |
| I have now sent a message from ALL-IN-1 MAIL V1.1-C to MEMO with the
same message syntax as in .2. It worked fine of course...
.0> Report 1.
.0> Actual Recipient: (MEX.IBMMAIL.I1001676@MEMO@GOLF)
.0> (*MRMRLP=256)
.0> Message NOT DELIVERED, reason is: Unable to transfer.
.0> Diagnostic:
There is no Diagnostic in the message above. Is that a typo?
The MRMRLP=256 is definitely strange. It should be 1 when a message
is sent to one recipient. So something is not right here.
.0> Address translation: Enabled
.0> Format: MEMO
.0> Ensure uniqueness: Disabled
.0> Multiaddress action: PRIMARY
.0> Distribution list: Enabled
Since address translation is used, it would be interesting to see
the sender's (SYSTEM@AM@GOLF) DDS record (/FULL). There might be
something strange there that causes MRMEMO to non-deliver the message.
Another thing to check: Since the address translation format selected
is "MEMO", it might be possible that the MEMO system is set up in a
way that does not allow "complex names". If the MEMO system is not set
up for complex names, it will only accept addresses on MEMO format,
which in this case means that the MR sender *must* have a DDS record
with proper PRLOCATION (VAGUK2) and PRUSERNAME values.
I would like to see the non-delivery .NBS files (MRMEMO$DIR:
MRMEMOn-NOT%%%.NBS).
What kind of transfers are failing? E.g.:
Can SYSTEM@AM@GOLF send to any other MEMO recipients?
Can MEMO users send to SYSTEM@AM@GOLF?
Can any other ALL-IN-1 MAIL user send to MEX.IBMMAIL.I1001676?
Is there anything logged in the log file (MRMEMO$DIR:MRMEMOn.LOG) during
the failing transfer?
Anders
|
| 185.4 | may be looking in the wrong place... | YUPPY::CARTER | Windows on the world... | Fri Sep 03 1993 11:31 | 15 |
| Anders
We have since had further discussions with the IBM support people. It
transpires that users need to be registered on IEA with their address.
The user was registered as DGN.DEN of her old MEMO account. Her
Teamlinks DGN.DEN (and of course the SYSTEM) are not registered so we
believe it may be something to do with the IEA system rejecting the
message as it doesn't recognise the sender.
We can't test this till Monday....
Xtine
|