Re: rfc1495

Ned Freed <NED@sigurd.innosoft.com> Thu, 05 May 1994 21:21 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa18894; 5 May 94 17:21 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa18890; 5 May 94 17:21 EDT
Received: from survis.surfnet.nl by CNRI.Reston.VA.US id aa11068; 5 May 94 17:21 EDT
Received: from SIGURD.INNOSOFT.COM by survis.surfnet.nl with SMTP (PP) id <19146-0@survis.surfnet.nl>; Thu, 5 May 1994 23:08:59 +0200
Received: from SIGURD.INNOSOFT.COM by SIGURD.INNOSOFT.COM (PMDF V4.4-0 #1234) id <01HBZB4QBLDC8Y50LG@SIGURD.INNOSOFT.COM>; Thu, 5 May 1994 14:08:52 PDT
Date: Thu, 05 May 1994 14:08:23 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Ned Freed <NED@sigurd.innosoft.com>
Subject: Re: rfc1495
In-reply-to: Your message dated "Thu, 05 May 1994 08:43:55 +0100" <01HBYM2ZG08I8Y5020@SIGURD.INNOSOFT.COM>
To: John Haxby <J.Haxby@isode.com>
Cc: Ned Freed <NED@sigurd.innosoft.com>, Justin Ziegler <Justin.Ziegler@inria.fr>, mime-mhs@surfnet.nl, ziegler@chandon.inria.fr
Message-id: <01HBZE6L7HE48Y50LG@SIGURD.INNOSOFT.COM>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET="US-ASCII"
Content-transfer-encoding: 7bit

> Message/partial is a fine idea, in principle, but there's no good way to
> deal with it at an X.400 gateway.  It could be that you could adopt a compromise
> approach and assemble the entire message if it's small enough and just send
> through literal chunks if it isn't.   Mind you, there are still problems, I
> might decide to send a diary in 365 parts, one a day, and by the time the whole
> message is assembled, the first part will have been sitting around on the
> gateway MTA for a year -- this might be considered poor quality of service.

This is exactly what I actually implement.

				Ned