[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference virke::mrmemo

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

108.0. "Non-delivery from DEC-world to MEMO" by ZHSS05::DELIPPE (Gabriele de Lippe) Tue Dec 03 1991 10:59

From:   Manuela Tolba-Reinhardt        (TOLBA@A1@ZHSS05@ZUO)             
Date:   29-NOV-1991 15:26:17.67
To:     Corina Leonhard
Cc:     DELIPPE
        Werner Freund
Subj:   Memo Gtwy Probleme bei ABB



Hoi Corina,

Habe Dir noch eine genauere Problembeschreibung:

ABB INFORMATIK AG
Log No  89924.00-068-9RLE Company ABBINFORAG City BADEN
Post Cd 5401              Street  HASELSTRASSE,DUPLEX GEB�UDE
PCG Typ 6310              PCG Ser XX-890242482-00 LSD D/T   
29-Nov-1992/15:20
Opt Typ   -     -         Opt Ser                 Coverage  DSS

Title   HERR                      Dept  TECB. ID
Caller  LEUTWILER                 Badge           Orig Log       .  -   -
Phone   041056  757328            Ext             AR Badge  174369 Short 
HAGEH
PO No                             CC/Un 70F /G0   Rep Ind   N      Exc Cond  
N
Next-up Opt Type/Ser   -     -  /                 Conf Down N      Req Type  
C
Next-up PCG Type/Ser CLSYS/XX-CL0000013-00        RD Ind    N      Priority  
3
Svc Wsh

Problem Description
memo gty - inv recipient address




                                                              





DATE: 29-NOV-1991                                TIME: 11:20:10.47
                               Problem Statement

Submittor name: HvM                             Phone #: 056 756756
                                                Ext   #:

                                               
Q: What operating system are you using?

A: VMS

Q: What version is it?

A: 5.4-2

Q: What CPU type and/or special hardware is involved?

A: 6310 VAX-Cluster

Q: What product are you having difficulty with?
                                                                                
A: MEMO-GATEWAY

Q: What version is it?

A: 2.1

Q: What are you trying to do?

A: message exchange

Q: What are you expecting to happen?

A: no problems

Q: What is happening? Please include the exact error messages.
                                                                                
A: when from the memo-world a user sends a message to an unknown destina-
   tion in the DECNET-Environment (user does not exist) the memo-user
   gets a non-delivery message back AND each time he reads that message
   he re-gets re-gets re-gets re-gets another one
   - very nasty... and since quite some time

   WHAT's wrong ? our IBM people tell us - must be something over there in
   the DEC-World, but we are not so convinced. Could anyone more knowledg-
   eable tell us what to do ?

   Thanks for any hint !

****************************************************************************
****

[End of Description]
T.RTitleUserPersonal
Name
DateLines
108.1Probably notifications for notificationsSTKOFF::SPERSSONPas de problemeTue Dec 03 1991 13:4230
    
    Interesting problem. An educated guess at what's happening is this.
    
    1) MEMO user sends message to non-existing VAX user, eg DUMMY@MRGATE
    
    2) VMSmail gateway (could be ALL-IN-1 too, Message Router itself is
    less likely) sends non-delivery message to MEMO user. However
    these notifications from MRMEMO's and MEMO's point of view are just
    like any other message.
    
    3) MEMO user reads notification.
     
    4) MEMO V3.1.3 (or is that V3.1.4) sends receipt notification on that
    message although it shouldn't. Current MEMO version has problems in
    this area, see recent notes.
    
    5) The receipt notification bounces again.
    
    
    To track this down, it would be a great help if we could see the server
    listings ($ MC MRMMAN LIST) and MRNBSDMP's of files
    MRMEMO$DIR:MRMEMOn-*.NBS (note that you have to be quick in catching
    them as only the most recent message is saved here at any given time).
    
    We are aware that the recent upgrades of MEMO has hit MRMEMO badly. We
    are trying to push Verimation to do something about it.
    
    cheers,
    
    	Stefan