Conference virke::mrmemo

	Hi Ute,

	Ah, you have this same problem....

	Seems it is due to Verimation changing the protocol between the
	IBM stuff and out gateway, without telling us....

	Problems seemingly start with V3.1.2, see some earlier note.

	Hopefully Anders and/or Stefan will be given time to solve this problem,
	before that, be ware... and tell your clients not to upgrade. Rumor
	has it that V3.1.3 has a lot of MEMO internalbugs left as well so
	this might be a reason to pospone upgrades....?

	H�kan

	I am now close to obtaining a copy of the new Memo/Gateway protocol.
	Several (paper) copies have been mailed to me but they seem to
	disappear somewhere. Electronic mail systems are not the only ones
	that can lose messages :-)

	I have also heard that Verimation is considering changing the protocol
	back to the old format due to all the problems the change has caused.

	Still, I'll see what I can do when (if?) the spec. arrives.

	Anders

    At last I have received the Memo/GWY 1.1 protocol spec. Unfortunately
    I haven't found any changes that would explain the behaviour.

    But - I've had a chat with a Memo developer and he claimed that the problem
    with Memo not recognizing delivery notifications from MRMEMO is known
    and, in his opinion, a bug in Memo. This bug will most likely be fixed
    in the soon to be released Memo 3.1.4 and then in 3.2.0 so he advised
    us not to do any hackery to change MRMEMO yet. The fix was going to be
    tested in Finland (anything you know about H�kan).

    The other problem (the unwanted notifications) is not known but he was
    going to take a look at it. There are some protocol changes in this area
    that I have not fully digested yet so it is still possible that MRMEMO
    could be patched to fix this.

    Unfortunately the Memo developers don't have an environment with MRMEMO
    to test with. And we (the former MRMEMO development group - now MRMEMO
    midnight maintainers) do not have access to Memo 3.1. We will probably
    try to get Memo 3.1 installed in Valbonne, if that is acceptable, to
    be able to do some serious testing.

    Anders

Gentlemen,

We have the same problem in Belgium, with our most important customer.
Just to let you know.

Keep us up to date.
Let us know if we could provide help in any way ...

					Marc VH

    The latest news:

    Memo 3.1.4 has recently started to ship. It should solve the known
    problems with correlation.

    For older (3.1.3?) systems there are "ZAPs" (patches) that correct the
    same problems.

    The problem mentioned previously in this topic (unwanted delivery
    notifications and read receipts) is not known to the Memo developers,
    but could be the result of using an old version (i.e. 1.0) of Memo/GWY. 
    Memo/GWY 1.1 should be used!

    Anders

	Our customer here in Finland has not been given MEMO V3.1.4 yet,
	but after applying the patches to MEMO V3.1.3 everything seems to
	be back to normal again!

	Regs, H�kan

At GDB Belgium, we also have the problem with the unwanted READ receipts (see 
note 102.4). 

Our MEMO version is v3.1.2. and our MRMEMO version is v2.0 (soon we will 
upgrade to v2.1).

I heard that some patches exists to fix the problems, BUT HOW TO OBTAIN THESE 
PATCHES?  I asked already this question at the MEMO responsible, but he seems 
not to be well informed. In the mean time, the problem becomes more urgent 
and they are seeming to blame DIGITAL for it.

    
    re: .7
    
> At GDB Belgium, we also have the problem with the unwanted READ receipts (see 
> note 102.4). 
> 
> Our MEMO version is v3.1.2. and our MRMEMO version is v2.0 (soon we will 
> upgrade to v2.1).

    Are you sure we're talking about the same unwanted read receipts? This
    problem has only been observed in interconnection with MEMO V3.1.3 and
    later. The problem is that MR users get Read Receipts they have not
    asked for.
    
    Is your problem possibly the reverse, ie MEMO users get Read Receipts
    in text form from ALL-IN-1? This has irritated many a MEMO user. The
    problem can be solved if you install MRMEMO V2.1 and apply the new
    (undocumented) server switch below: 
    
    MRMMAN> DEFINE/REQUEST_NOTIFICATIONS=NORECEIPT
    
    Is this your problem?
    
    cheers,
    
    	Stefan

    
    After trying to track down these errors for a while, we can now see a
    pattern:
    
    The problems seem to arise on MEMO systems that are connected into a
    MEMO network, and where the MEMO version vary between the systems. Two
    configurations in particular:
    
    1) MRMEMO connected to MEMO V3.1.3 system, which relays messages to
    MEMO V3.1.1 system. Unwanted Receipt Notification are generated from
    the V3.1.1 system.
    
    2) MRMEMO connect to MEMO V3.1.4 system, which relays to 3.1.3.
    Unwanted Delete Notifications (which will look to the Message Router
    user as Delivery Notifications) are generated.
    
    Delete Notifications are internal to MEMO but are supported by MRMEMO
    through use of DDA:s in ordinary Delivery Notifications. They should
    never reach MR users.
    
    In the protocol between MRMEMO and MEMO/Gateway, flags are defined that
    lets MRMEMO decide whether to request notifications. It seems fair to
    assume, given our observations, that some internal MEMO bugs prevents
    these flags to be propagated between MEMO systems with different
    versions. I'd like to be more specific but I really can't at this stage.
    
    Anyway, two different notification messages are involved. Delete
    notifications and receipt notifications. As a temporary measure, we can
    provide patches that filters out these notification messages altogether
    (ie MRMEMO won't pass them to Message Router). These patches can be
    provided while Verimation put their act together. Please notice that
    this means restriction in MRMEMO functionality in order to work around
    MEMO bugs. SDelete Notifications may not be a big deal, since it's only
    MEMO internal functionality, but Receipt Notifications are certainly
    important. 
    
    If you do apply the patches, make sure to save the old version of the
    file, so that when Verimation have fixed the MEMO bugs you can
    reenable it. Either that or reinstall MRMEMO.
    
    For patches see 5.11 and 5.12.

Stefan,


Last Wednesday, we upgraded to MRMEMO v2.1 with main goal to be able to solve 
the problem with the unwanted read receipts (see 102.4).

After applying the undocumented server switch, you explained in note 102.4, 
THE PROBLEM WAS solved! Thanks.

But, since MRMEMO v2.1, some users get unwanted 'delivery' receipts i.e. they 
didn't even send a mail to the person of whome they get the delivery receipt. 
Probably this is the problem also stated in a previous note (MEMO delete 
notifications -> delivery receipts for MR).

I applied the patch (see 5.11) this morning and I hope the problem will be 
solved now. But nevertheless, I would like to now what you mean by "it works 
around bugs in MEMO AT THE EXPENSE of MRMEMO functionality". What 
functionality disappears ?


Thanks !


Els.

    
    Hi,
    
    Sorry for not replying earlier, I was away on Christmas Holidays.
    
    The functionality that goes away is simply that of being able to pass
    Delete Notification messages between two MEMO systems (or, as the case
    may be, two users within the same MEMO system passing through MRMEMO)
    
    In 99% of the installations, this won't be a problem. It's more a 
    matter of principles.
    
    cheers,
    
    	Stefan

As Els is very often at customer site, I'll put in a small feedback.

It seems applying the patch solves the problem of the delivery notifications that 
Els mentioned.

					Marc VH.