[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | VAX MAILGATE for MEMO |
|
| Moderator: | STKHLM::OLSSON |
|
| Created: | Sat Feb 25 1989 |
| Last Modified: | Tue May 14 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 216 |
| Total number of notes: | 933 |
205.0. "Sender Information missing in V3.1 from MEMO Users" by ZPOVC::CHIKLIAK () Thu Dec 15 1994 08:59
Hi,
I need information to support our customer. Can anyone assist? I have posted
this information to ALLIN1 :
<<< IOSG::USER3:[NOTES$LIBRARY]ALL-IN-1.NOTE;4 >>>
-< ALL-IN-1 (tm) Support Conference >-
================================================================================
Note 550.0 Sender Information missing in V3.1 from MEMO Users 4 replies
ZPOVC::CHIKLIAK 234 lines 12-DEC-1994 09:50
--------------------------------------------------------------------------------
Hi,
I have an urgent problem which I am trying to assist a customer which does not
make sense.
Allin1 V3.1 (Singapore)
Allin1 V3.0 (Hong Kong)
Memo V3.1??? (Sweden, DEC European Assets, according to the customer)
Because it is a problem in Singapore, I am trying to assist the customer.
Symptons :-
Case 1 :
From the Memo System, a mail was sent out to ALLIN1 V3.0 system, the receipent,
was able to see the message was from which user. After upgrading to ALLIN1 V3.1
and its message router to 3.3A, the customer is able to receive mail message
but fail to see who the sender is. Therefore, there is no way the end-user
can replied to the sender. This does not happen if ALLIN1 V3.0 sender sends a
message to ALLIN1 V3.1 users.
Because of this, the customer needs some indication what could have gone
wrong...
Case 2 :
From the Memo System, a mail was sent out to ALLIN1 V3.0 user in H.K and if this
message was autoforward to Singapore, the end-user here with V3.1 can see who
was the sender (from both ALLIN1 V3.0 and Memo).
It seems like the problems only occur if message are sent directly from Memo
system to ALLIN1 v3.1 users with Message Router 3.3A installed. If ALLIN1 V3.1
user sents a message to Memo system, the sender name appears. So what could
have gone wrong???
Here is the NBS file :
From MEMO to ALLIN1 V3.1 user :
000007 1 MSG[V2ENV] Len=0004B9
00000E 2 FIELD[MID] Len=00001E
000010 3 ASCII Len=00001C
"65911090214991/462798@IIS001
000033 2 FIELD[PDATE] Len=000012
000035 3 DATE Len=000010
000037 4 ASCII Len=00000E
"19941209011956
00004C 2 FIELD[SENDER] Len=000097
000053 3 ENT[NAME] Len=000090
000059 4 SEQ Len=000030
000060 5 ATTR[ORGANTN] Len=000005
000062 6 ASCII Len=000003
"IO6
00006C 5 ATTR[PNAME] Len=00001D
000073 6 ATTR[SURNAME] Len=000016
000075 7 ASCII Len=000014
"ALLIN1 ADMINISTRATOR
00008F 4 SEQ Len=000054
000096 5 ATTR[TEL] Len=00000F
000098 6 ASCII Len=00000D
"(852) 8332837
0000AC 5 ATTR[LOCATION] Len=00000A
0000AE 6 ASCII Len=000008
"HONGKONG
0000BD 5 ATTR[ROUTE] Len=000014
0000C3 6 SEQ Len=00000E
0000C5 7 ASCII Len=000006
"IIS001
0000CD 7 ASCII Len=000004
"MEMO
0000D8 5 ATTR[USERID] Len=00000B
0000DA 6 ASCII Len=000009
"IKEA.MAHB
0000EA 2 FIELD[TO] Len=0000A7
0000F0 3 SEQ Len=0000A1
0000F7 4 ENT[NAME] Len=00009A
0000FD 5 SEQ Len=000000
000103 5 SEQ Len=000073
00010A 6 ATTR[DOMDEFINED] Len=00004B
000110 7 SET Len=000045
000117 8 ATTR[EXTDDA] Len=00003E
00011D 9 SEQ Len=000019
000124 10 ATTR[DDATYPE] Len=000008
000126 11 ASCII Len=000006
"MRMRLP
000133 10 ATTR[DDAVALUE] Len=000003
000135 11 ASCII Len=000001
"1
00013C 9 SEQ Len=000019
000143 10 ATTR[DDATYPE] Len=000008
000145 11 ASCII Len=000006
"MRMDRQ
000152 10 ATTR[DDAVALUE] Len=000003
000154 11 ASCII Len=000001
"1
00015C 6 ATTR[ROUTE] Len=00000A
000162 7 SEQ Len=000004
000164 8 ASCII Len=000002
"A1
00016D 6 ATTR[USERID] Len=000009
00016F 7 ASCII Len=000007
"MANAGER
00017D 5 ATTR[PERRECFLG] Len=000007
000180 6 BITS[%00] Len=000004
%D0000000
00018B 5 ATTR[EXTENTNID] Len=000006
00018D 6 INT Len=000004
%00000001
00019A 2 FIELD[UACONTID] Len=000012
00019C 3 ASCII Len=000010
"3JeEqyUcaMfq5PBM
0001B5 2 FIELD[PERMSGFLG] Len=000007
0001B8 3 BITS[%00] Len=000004
%10000000
0001C5 2 FIELD[ITRACE] Len=00008A
0001CB 3 SEQ Len=00003F
0001D4 4 FIELD[MTA] Len=000008
0001D6 5 ASCII Len=000006
"OMFE01
0001E5 4 FIELD[ARVDATE] Len=000016
0001EB 5 DATE Len=000010
0001ED 6 ASCII Len=00000E
"19941209082044
000204 4 FIELD[ACTION] Len=000006
000206 5 INT Len=000004
%00000000
000210 3 SEQ Len=00003F
000219 4 FIELD[MTA] Len=000008
00021B 5 ASCII Len=000006
"IIS001
00022A 4 FIELD[ARVDATE] Len=000016
000230 5 DATE Len=000010
000232 6 ASCII Len=00000E
"19941209011956
000249 4 FIELD[ACTION] Len=000006
00024B 5 INT Len=000004
%00000000
000258 2 FIELD[CONTENTDIA] Len=000006
00025A 3 INT Len=000004
%00000002
000267 2 FIELD[HOPCOUNT] Len=000006
000269 3 INT Len=000004
%00000002
000274 2 MSG[V2CONT] Len=00024C
00027D 3 FIELD[APPMID] Len=000012
00027F 4 ASCII Len=000010
"3JeEqyUcaMfq5PBM
000296 3 FIELD[FROM] Len=000097
00029D 4 ENT[NAME] Len=000090
0002A3 5 SEQ Len=000030
0002AA 6 ATTR[ORGANTN] Len=000005
0002AC 7 ASCII Len=000003
"I06
0002B6 6 ATTR[PNAME] Len=00001D
0002BD 7 ATTR[SURNAME] len=000016
0002BF 8 ASCII Len=000014
"ALLIN1 ADMINISTRATOR
0002D9 5 SEQ Len=000054
0002E0 6 ATTR[TEL] Len=00000F
0002E2 7 ASCII Len=00000D
"(852) 8332837
0002F6 6 ATTR[LOCATION] Len=00000A
0002F8 7 ASCII Len=000008
"HONGKONG
000307 6 ATTR[ROUTE] Len=000014
00030D 7 SEQ Len=00000E
00030F 8 ASCII Len=000006
"IIS001
000317 8 ASCII Len=000004
"MEMO
000322 6 ATTR[USERID] Len=00000B
000324 7 ASCII Len=000009
"IKEA.MAHB
000334 3 FIELD[TO] Len=0000A2
00033A 4 SEQ Len=00009C
000341 5 ENT[NAME] Len=000095
000347 6 SEQ Len=000000
00034D 6 SEQ Len=00007B
000354 7 ATTR[DOMDEFINED] Len=00004B
00035A 8 SET Len=000045
000361 9 ATTR[EXTDDA] Len=00003E
000367 SEQ Len=000019
00036E 11 ATTR[DDATYPE] Len=000000
000370 12 ASCII Len=000006
"MRMRLP
00037D 11 ATTR[DDAVALUE] Len=000003
00037F 12 ASCII Len=000001
"1
000386 10 SEQ Len=000019
00038D 11 ATTR[DDATYPE] Len=00000
00038F 12 ASCII Len=000006
"MRMDRQ
00039C 11 ATTR[DDAVALUE] Len=000003
00039E 12 ASCII Len=000001
"1
0003A6 7 ATTR[ROUTE] Len=000012
0003AC 8 SEQ Len=00000C
0003AE 9 ASCII Len=000006
"OMFE01
0003B6 9 ASCII Len=00002
"A1
0003BF 7 ATTR[USERID] Len=000009
0003C1 8 ASCII Len=000007
"MANAGER
0003CF 6 ATTR[REPORTREQ] Len=000007
0003D2 7 BITS[%00] Len=000004
%80000000
0003DD 3 FIELD[SUBJ] Len=000010
0003DF 4 ASCII Len=00000E
"testtest
0003F4 3 FIELD[PDATE] Len=000012
0003F6 4 DATE Len=000010
0003F8 5 ASCII Len=00000E
"19941209001700
00040D 3 VEND[RRECPT] Len=000000
000414 3 FIELD[ATTACH] Len=0000AC
00041B 4 MSG[TEXT] Len=0000A5
000421 5 ASCII Len=00009F
"--- Received from IKEA.MAHB (852) 8332837
94-12-09 01.17
" -> VAX.MANAGER..A1..OMFE01
" -: ----------------------> VAX USER IN NETK
IKEAMAIL
"hi
0004C0 0End of file
Thanks in advance for any indication...
CT
================================================================================
Note 550.1 Sender Information missing in V3.1 from MEMO Users 1 of 4
CSOA1::LENNIG "Dave (N8JCX), MIG, @CYO" 18 lines 12-DEC-1994 13:54
--------------------------------------------------------------------------------
The gateway between Memo and MR is not putting a Freeformname element
with the P2 'From' information.
Due to some things that went on behind the scenes in order for 'old'
(ie pre-V3.1) versions of ALL-IN-1 to interwork with MR, the surname
attribute that _is_ present in the Memo messages used to be presented
to 'old' ALL-IN-1s as the equivalent of freeformname. Since V3.1 now
uses an up-to-date interface to MR, this no longer occurs.
I suggest you raise the issue with the Memo gwy folk; they need to put
a real FreeFormName element on the message instead of (incorrectly)
putting this information in the Surname field; doing so will result in
the information being visible to both 'old' and 'new' ALL-IN-1.
Note: The surname field has a very specific use in messages (part of the
X400 'personal name' attributes) and should not be loaded with ad hoc info.
Dave
================================================================================
Note 550.2 Sender Information missing in V3.1 from MEMO Users 2 of 4
IOSG::MARSHALL "A glitch in reality" 10 lines 12-DEC-1994 14:49
-< Would missing freeformname prevent replies working? >-
--------------------------------------------------------------------------------
Dave,
The "missing freeformname" problem, which you've highlighted in other notes
as well, occurred to me too. But the base note says that the problem is that
the V3.1 system cannot reply to the messages, which implies that there is more
wrong that just the missing freeformname.
However, the rest of the address appears to be intact, so I'm at a loss...
Scott
================================================================================
Note 550.3 Sender Information missing in V3.1 from MEMO Users 3 of 4
CSOA1::LENNIG "Dave (N8JCX), MIG, @CYO" 11 lines 12-DEC-1994 16:24
--------------------------------------------------------------------------------
Scott,
No, the missing freeformname shouldn't prevent replying.
I discounted that part of .0 (subject to further postings) as possibly
distorted customer//note-author communication.
Even if there is a reply problem, it doesn't affect the validity of my
comments/recommendations re: MR/MEMO and surname vs freeformname.
Dave
================================================================================
Note 550.4 Sender Information missing in V3.1 from MEMO Users 4 of 4
ZPOVC::CHIKLIAK 16 lines 15-DEC-1994 07:18
-< Thanks... >-
--------------------------------------------------------------------------------
Hi,
Thanks for all your quick response.
I make a mistake. The user (ALLIN1 V3.1) were able to reply to MEMO
users, but the user do not know who they are replying to.
Does anyone knows whether which version of VAX MAILGATE for MEMO
(MRMEMO) does work with P2 compliance or MR 3.3a/ALLIN1 V3.1.
I will post this also on MRMEMO conference and EOASSETS since it is an
Europen asset.
Thanks in advance...
CT
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 205.1 | Fix will be produced | STKOFF::SPERSSON | Pas de probleme | Tue Jan 10 1995 14:40 | 12 |
|
Hi,
Sorry for the delay, I was unaware that this was discussed here...
I have agreed with the customer (IKEA here in Sweden) that we provide a
fix that fills information in FREEFORM. Should be available in Jan 1995
(that's what I told them)
cheers,
Stefan
|