Conference virke::mrmemo

    
    Hi Helene,
    
    First of all let me see whether I can reproduce the error. I need
    information on:
    
    - Addressing. Please give the address that the Memo user types in, and
    if DDS or any other address conversion is used, the resulting Mailbus
    address.
    
    - Software versions, especially ALL-IN-1 Mail
    
    - An MRMMAN LIST output 
    
    - if possible, MRNBSDMP output logs of the files
    MRMEMO$DIR:MRMEMO1-ENVELOPE.NBS and MRMEMO$DIR:MRMEMO1-CONTENTS.NBS.
    Two instances wanted:
    
      1) Catch the incoming message (MEMO -> MR) before the notifications
         start to arrive (You have to be quick here)
    
      2) The receipt notification message
    
    - Other info. Does this occur when there is only on adressee in the
    message or only when adressee is part of a distribution list?
    
    
    cheers,
    
    	Stefan
    list

Hello Stefan,

here is what I have got right now:

ALL-IN-1 Mail Version V1.0-500

MRMemo V2.1
MR V3.1


I can send messages in both directions, and reply to messages in both 
directions as well. The problem occurs when there is only one addressee
(I did not test more then one up to now)

The Key settings of Mrmemo:

Request notifications: Enabled
Send notifications: Enabled
Address translation: Enabled
  Format: MEMO
  Ensure uniqueness: Disabled
  Multiaddress action: MATCHING
MEMO address: SN_Attributes
DDS validation:
  MR to MEMO sender: Enabled
  MEMO to MR sender: Disabled
  MEMO to MR recipient: Enabled
  MR to MEMO recipient: Disabled

I have the listings in hardcopy only by now, so if you are reachable by FAX,
I could send copies. 

The Key values of the DDS-Entry of the user MATUSCH looks like this 
(the entry is unique):

Reverse lookup(first one -> since multiaddress is set to MATCHING in MRMEMO, 
the number is not relevant anyway):  MATUSCH@AM@AISA02
MR S location: ATVNAVXT
MR S user name: MATUSCH

The address used in MEMO looks as follows:

ATVNAVXT.MATUSCH

complex addressing is not enabled on the Memo system.

Does this information help to clear up things? Unfortunately I do not have
a NBS-dump of the messages right now. I hope to get them by tomorrow.

Kind regards

Helene

    
    Helene,
    
    The Fax no is:
    
    +46-8-833552
    
    I'll let you know when I've tested it.
    
    cheers,
    
    	Stefan

    
    Helene,
    
    This is to confirm that I've received your fax. However I have not
    been able to reproduce your problem. This indicates that you may be
    right in your suggestion that something has changed between MEMO
    versions. I'm testing against the MEMO system in Valbonne, V 3.0.5
    
    I would still like to see the NBS files as described in .1, especially
    the actual Receipt Notification itself.
    
    Maybe I should describe why: MRMEMO V 2.1 relies heavily on Domain
    Defined attributes (DDA's) for the correlation of receipts. At one time in
    ALL-IN-1 Mail development they forgot to return  DDA's in their
    notification messages. I don't know if this was fixed before the
    initial release of ALL-IN-1 Mail V 1.0, or whether it was only included
    in a later S-kit. If I may study the NBS-file, it can be easily
    established.
    
    One other thing: the use of Domain Defined attributes can cause
    disturbances when communicating with certain X.400 systems. It is
    therefore possible to disable their use in MRMEMO, with the
    undocumented qualifier /NODOMAIN. If you do this, correlation of read
    receipts will *not* work. From the server listing you sent, this is not
    the case here, I just wanted to point it out...
    
    cheers,
    
    	Stefan
    
    

Hi Stefan,

you will receive a copy of the NBS-dump of the receipt notification 

1) in the MR-Mailbox (from directory MRNBS:)

2) the divided NBS-files (from MRMEMO$DIR:)

Is there anything wrong in the DDA'S?

BTW, I set reply_request on in A1mail and sent a mail to Memo, but did not get 
one, if it would be a separate mail. 

Thanks and kind regards

Helene

    
    Helene,
    
    I have received your latest fax and the NBS-files look OK. This is
    still a mystery. I will try and get a comment from Verimation, because
    it does look like a MEMO problem, now that everything else seems
    eliminated.
    
    > BTW, I set reply_request on in A1mail and sent a mail to Memo, but
    > did not get one, if it would be a separate mail. 
    
    Acknowledged. This attribute is apparently ignored by MRMEMO in
    direction MR->MEMO. I don't see why this should be so. We seem to have
    overlooked it in the implementation. Currently it is a restriction. It
    is not difficult to fix, but it may take some time before something is
    done about it, because nobody is assigned to do MRMEMO Engineering work
    nowadays.
    
    cheers,
    
    	Stefan

    

    
>    > BTW, I set reply_request on in A1mail and sent a mail to Memo, but
>    > did not get one, if it would be a separate mail. 
>    
>    Acknowledged. This attribute is apparently ignored by MRMEMO in
>    direction MR->MEMO. I don't see why this should be so. We seem to have
>    overlooked it in the implementation. Currently it is a restriction. It
>    is not difficult to fix, but it may take some time before something is
>    done about it, because nobody is assigned to do MRMEMO Engineering work
>    nowadays.
    
    (X) Someone knowledgeable is sometimes available
    
    This someone (Anders Olsson) has pointed out that the above is not
    entirely correct. The restriction actually lies within MEMO/Gateway
    (Verimation's Software). Basically, the request reply functionality
    only works within MEMO, and it cannot be imported/exported through
    MEMO/Gateway. So we cannot do anything about it even if given
    time/funding/resources.
    
    Sorry for the confusion.
    
    cheers,
    
    	Stefan

Hello Stefan,

Success - today we tested ALL-IN-1 Mail against the "old" version 
of Memo, V 3.0.5, and everything worked fine, Status in memo did 
change from "Gesendet" to "Gelesen"!

This was the major point at Philips!

BTW, someone from Verimation informed my customer that it could 
never work because Message Router does not support such a 
feature...

So, the other factum is, that reply requests do not work with 
Memo V 3.1.2 and Gateway V1.1.0 (MRGATE, which is the name of the 
Verimation Gateway I suppose, remained V 1.0.2).


Product versions on IBM-side:
Memo V3.0.5
Gateway V1.0.2
MRGATE 1.0.2	   ---> reply requests work fine in 1 direction
		   i.e. Messages sent from Memo to A1Mail get
		        their status changed to Empfangen/Gelesen

Memo V3.1.2
Gateway V1.1.0
MRGATE 1.0.2  	   ---> receipt notifications get lost somehow

Stefan, thank you very much for your help up to now!

So what would be the best thing to do to get the problem fixed 
for V3.1.2 of Memo? You stated somewhere that there is nobody 
assigned for engineering work on MRMEMO. Well , up to now we do 
not even know, whether the problem is in MRMEMO or if it has to 
be fixed in MRGATE (Verimation) or in the part my customer calls 
the Gateway.

Do you think you can do something?

Kind regards

Helene

Hello Helene,

.8> BTW, someone from Verimation informed my customer that it could 
.8> never work because Message Router does not support such a 
.8> feature...

    That is of course wrong, but before the arrival of ALL-IN-1 MAIL
    there was no user agent that produced true receipt notifications.

.8> So, the other factum is, that reply requests do not work with 
.8> Memo V 3.1.2 and Gateway V1.1.0 (MRGATE, which is the name of the 
.8> Verimation Gateway I suppose, remained V 1.0.2).

    We don't have the possibility to test against these new versions since
    they are not yet installed on the IBM in Valbonne. (And until this
    problem has been solved, I'm not sure we want to upgrade in Valbonne.)

.8> So what would be the best thing to do to get the problem fixed 
.8> for V3.1.2 of Memo? You stated somewhere that there is nobody 
.8> assigned for engineering work on MRMEMO. Well , up to now we do 
.8> not even know, whether the problem is in MRMEMO or if it has to 
.8> be fixed in MRGATE (Verimation) or in the part my customer calls 
.8> the Gateway.

.8> Do you think you can do something?

    One thing you could do is to enable logging in MRMEMO and then send a 
    message from Memo and return a read receipt from ALL-IN-1 MAIL. See note 
    5.8 for a patch that is required for the logging to work properly. Use
    the logging values 4 and 20 (i.e. $ DEFINE/SYSTEM MRMEMO$LOGMASK 24).
    Try to do this on a quiet system since the amount of logged data is 
    large and it could be difficult to find the right messages in the log 
    file if other mail traffic i going on. (And send just a short message
    with as few lines of text as possible.)

    When the message has been sent and logged, don't forget to DEASSIGN
    MRMEMO$LOGMASK. Note - you don't have to restart the server between the
    logical name changes, since checks for the logical name are made
    periodically. 

    You can send the result to me (or Stefan) and maybe we could get 
    something out from it. If you could provide the corresponding .NBS files
    too, that will probably help.

    An alternative to the MRMEMO$LOGMASK logging is to use SNATRACE, which 
    will produce less amounts of data, but contain the same information -
    pick your choice.

    Anders

    I have been in touch with the Memo development people and discussed this
    problem and the conclusion was that there are changes in Memo 3.1
    concerning handling of correlations that affects MRMEMO.

    I am now waiting for a new Memo/Gateway protocol spec. to arrive. Then
    we'll see what needs to be done to get the correlations working with
    Memo 3.1. From the discussion mentioned above, I got the impression that
    it migh be possible to produce a patch for MRMEMO V2.1 to fix this
    problem, but I don't promise anything. 

    Stay tuned...

    Anders

	Hello Anders,

	Have you heard something about the reciept correlation as of lately?

	We had a customer that upgraded their testsystems and discovered that
	recipts stopped working. How about the possibiliy of a patch??

	Regs, H�kan