Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!lll-tis!NRTC.NORTHROP.COM!Stef From: Stef@NRTC.NORTHROP.COM (Einar Stefferud) Newsgroups: comp.protocols.iso.x400.gateway Subject: Re: Delivery and Nondelivery notifications Message-ID: <8322.584178157@nma.com> Date: 5 Jul 88 17:42:37 GMT References: <8806301818.AA10611@polya.sun.com> Sender: root@tis.llnl.gov Reply-To: Stef@nrtc.northrop.com Distribution: inet Organization: The Internet Lines: 13 Approved: post-x400-gateway@tis.llnl.gov I recall adding another idea to the pile here, but I guess it did nt catch any attention, so here is another try. How about reversing the attribute/value pair on the RFC822 side, with a new RFC822 field for each attribute value of interest, with the content of the filed indicating which addresses are to be so treated? Example: X-ReturnContent: addr1, addr2, addr3 The addr-indicators only need be unique in this message for the gateway to figure out what to do for each. Defaults should be set to minimize the use of these fields. What say? I think it simplified many of your concerns. Cheers...\Stef