[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

147.0. "nondelivery fails from memo to x.400" by UNHOLD::SONNTAG () Tue Sep 15 1992 18:22

Hello,

a customer send a big (over 50 kb) message from X.400 via MR/X
to the MEMOserver. The Server didn't accept the mail and sends a 
nondeliver message back, but the MR/X cann't send the nondelivery
message to the X.400 mail user, because the 
privat domain		and the
orgunit
of the original sender was missing.
Is this a known feature ???

regards
Michael
T.RTitleUserPersonal
Name		DateLines
147.1It's a "feature"STKHLM::OLSSONAnders Olsson, SIP SwedenWed Sep 16 1992 09:4628
Hello Michael,

a non-delivery notification returned by MRMEMO as the result of a message
being too big is unfortunately somewhat crippled. The reason for this
is that some non-delivery conditions occur already in Memo/GWY (the
component on the IBM side that MRMEMO talks to) before the message goes
on to Memo. A message being too big is one of these conditions.

Errors returned by Memo/GWY are not complete status messages like the ones
Memo produces, merely a short error code. In this situation, MRMEMO
*should* use information from the original message to build a complete
non-delivery notification, but... that is not properly implemented and the
result is this crippled notification. (I'm not trying to blame Memo/GWY
here - just explaining what's happening.)

There is a warning about this, althought not very detailed, in the V2.1
release notes (section 7.3).

50 KB is a little small as maximum message size. With MRMEMO V2.1 and
Memo/GWY V1.1, much larger messages can be handled (if enabled on the
IBM side). Maybe this customer could raise the limit to reduce the
risk of exceeding the max.

I'm afraid there is no easy fix for this problem, but I'll take a look at
it to see if there is some reason for the lack of PRMD and ORGUNIT that can
be cured with a patch.

Anders
147.2PEARS::SONNTAGMichael Sonntag, TSSC-OIS, @MUHWed Sep 16 1992 18:539
Hello,

the customer has installed the fix 5.13, the message should be 
truncated to nearly 50 kb, but the error accours again.

regards
Michael
147.3Allow 200 Kbytes on the MEMO sideSTKOFF::SPERSSONPas de problemeTue Sep 22 1992 12:5224
    
    Hi Michael,
    
    We have two size related issues here:
    
    1) The MRMEMO server's ability to handle large buffers, intended for
    V2.1 to 500Kb, but buggy and which patch 5.13 cripples to approx 50 Kb
    
    2) The MEMO system's ability to receive large messages. The maximum
    messages size can be modfified by means of system parameters on the
    MEMO side. The error that occurs at your customer's site is because the
    MEMO system rejects the message. Please note also that a 50 Kb limit is
    probably insufficient because each text line in the MRMEMO message is
    padded with blanks to the length of the current line length. This is
    done *after* the message has been truncated to 50 Kb. This means
    that the MEMO system should probably allow 50 Kb * (3 or 4) as the
    limit. I'm sorry if this has not been made clear in the patch notes.
    
    cheers,
    
    	Stefan