[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

181.0. "Problem MEMO --> X.400 (incorrect address)" by EEMELI::ALADIN () Wed Jun 09 1993 10:34

    
    Hey !
    
    A customer of ours, The Finnish Data Processing Central (VTKK)
    is having a small problem when sending from MEMO to X.400:
    If for example the ADMD attribute in the X.400 address is missing
    the message is never seen in the message Router side.
    
    I.e. the receiver address looks like elvi.elx.ad=/c=fi
    
    The MRMEMO server stays in receiving mode, but it never '
    succeeds in processing the incoming message.
    
    The situation must be released by moving away the message
    from IBM MEMO side.
    
    Any suggestions, Anders ?
    
    I told the customer to put the mrmemo$logmask (44) on to get
    some further information.
    
    Cheers	
    	Jan-Erik

T.R Title User Personal
Name Date Lines

181.1 More info please STKHLM::OLSSON Anders Olsson, SIP Sweden Wed Jun 09 1993 12:58 34

T.R	Title	User	Personal Name	Date	Lines
181.1	More info please	STKHLM::OLSSON	Anders Olsson, SIP Sweden	`Wed Jun 09 1993 12:58`	34
	.0> I.e. the receiver address looks like elvi.elx.ad=/c=fi I need some more information to be able to reproduce this: Is the address above exactly what causes the problem? No typo? A list of all server parameters would be nice, or at least: What Replacement Strings are used? If DDS validation or address translation is used - what options? .0> The MRMEMO server stays in receiving mode, but it never ' .0> succeeds in processing the incoming message. Is the server idle or looping (consuming CPU time)? .0> The situation must be released by moving away the message .0> from IBM MEMO side. Doesn't MRMEMO have to be restarted? .0> Any suggestions, Anders ? No, not yet. .0> I told the customer to put the mrmemo$logmask (44) on to get .0> some further information. The value 4 in mrmemo$logmask dumps a lot of information in the log file (1 line per received byte!) so only use it in one-shot tests where a single test message is sent over. Don't keep it enabled during normal message traffic unless you have room for a very large log file. Furthermore - I hope the patch in note 5.8 is installed or the log file will really become LLLAAARRRGGGEEE. Anders

    
.0> I.e. the receiver address looks like elvi.elx.ad=/c=fi

    I need some more information to be able to reproduce this:
    Is the address above *exactly* what causes the problem? No typo?
    A list of all server parameters would be nice, or at least:
      What Replacement Strings are used?
      If DDS validation or address translation is used - what options?
    
.0> The MRMEMO server stays in receiving mode, but it never '
.0> succeeds in processing the incoming message.

    Is the server idle or looping (consuming CPU time)?
    
.0> The situation must be released by moving away the message
.0> from IBM MEMO side.

    Doesn't MRMEMO have to be restarted?
    
.0> Any suggestions, Anders ?

    No, not yet.
    
.0> I told the customer to put the mrmemo$logmask (44) on to get
.0> some further information.

    The value 4 in mrmemo$logmask dumps a lot of information in the log
    file (1 line per received byte!) so only use it in one-shot tests where
    a single test message is sent over. Don't keep it enabled during normal
    message traffic unless you have room for a very large log file.
    Furthermore - I hope the patch in note 5.8 is installed or the log file
    will *really* become LLLAAARRRGGGEEE.

    Anders