Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!samsung!brutus.cs.uiuc.edu!psuvax1!psuvm!HMCVAX!NED From: NED@HMCVAX.CLAREMONT.EDU (Ned Freed, Postmaster) Newsgroups: bit.listserv.pmdf-l Subject: RE: JNET interface question Message-ID: Date: 8 Feb 90 23:33:00 GMT Sender: PMDF Distribution List Reply-To: PMDF Distribution List Lines: 32 Approved: NETNEWS@PSUVM Gateway Errors-to: postmast@YMIR.BITNET X-Envelope-to: PMDF-L@IRLEARN.BITNET X-VMS-To: IN%"JOHNSON@NUHUB.BITNET" X-VMS-Cc: IPMDF X-To: JOHNSON@NUHUB, INFO-PMDF@YMIR There's a cute, but dangerous, trick you can use to reprocess lost $BITNET files. Copy the files into the JNET receive queue as JMAILER.TXT files, and let BN_SLAVE reprocess them as if they were incoming mail. Important caveats: (1) This will ONLY work with PMDF 3.1. It won't work with earlier versions. (2) This trick depends on the X-Envelope-to: line being present in the header. If you've disabled X-Envelope-to: lines on any of your BITNET channels, don't use this trick. (3) I have used this a couple of times, and I've directed one or two other people to do it. It has worked in the cases I've seen. But it may not work for you. Try it with a couple of messages before you move 10,000 messages in there. (4) If you use COPY to move the files, don't forget the /NOCONCAT qualifier! Now, as for the issue of how to prevent these files from popping up in the first place. This is a toughie. The problem is that by the time PMDF knows that JNET cannot deliver the message, the message has already been "delivered". This is sort of a design flaw in the SMTP module, which I intend to correct in the future. I've gotten as far in this as activating the necessary JNET code on the fly using LIB$FIND_IMAGE_SYMBOL (this eliminates the need to relink for new releases of JNET). I hope to have the rest of this problem worked out soon. I don't think it will be patchable, however -- the changes are going to be pretty major. Ned