From utcq Sun Jan 7 23:27:34 1996 Return-Path: Received: by galadriel.ecaetc.ohio-state.edu (NX5.67e/NX3.0M) id AA07375; Sun, 7 Jan 96 23:27:34 -0500 Received: by tap.fnet.org To: fvbugs-update@galadriel.ecaetc.ohio-state.edu From: root Message-Id: Subject: Update Date: Mon, 8 Jan 1996 03:42:44 GMT Content-Type: text/plain; charset=us-ascii X-Mailer: FVmail [ver 1.6b] ------------------------------------------------------------------ From :szatezal@magnus.acs.ohio-state.edu Date :10/22/95 17:25:40 -0400 (EDT) Subj :Re: bug fixed (fwd) Forwarded message: From dmccoy@hopi.dtcc.edu Sun Oct 22 06:43:35 1995 Date: Sun, 22 Oct 1995 01:32:27 -0400 (EDT) From: Dan McCoy To: Shane Zatezalo Subject: Re: bug fixed In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sat, 21 Oct 1995 Xevious@tap.fnet.org wrote: > site SUBSCRIBE: 1!110 > 1234567890 > THE CONF SUBSCRIPTION PROGRAM DOES A > > LONG IF X$[1,10]="SUBSCRIBE:" > X=VAL(X$[11]) > END IF > > SO EVEN IF THERE'S A "!800" AFTERWARDS, IT'LL GET THE VALUE, WHICH IS > ALL IT REALLY NEEDS. I'LL TRY TO RE-CHECK THE CODE THOUGH. > > That was flooding my mailbox with unsuccessful conferecing request. I change > the code back to the old SUBSCRIBE:110 for the subscribe and unsubscribe > routines. Seems to be working so far. one more nasty one. I sent an unsubscription to #4. The letter I got back look similar to this. headers stuff your unsubscription letter with subject blah blah has been successfully fffffffffff_o Now this letter goes into a binary loop and actaully never even prints the line at the bottom of the letter. Reason I say binary loop (death letter) is because if you try to forwad it or reply yo it and readrress it it severely crashes the BBS with some nasty errors. don't remember what happend before, but you really outta take a look at the conferencing.s and see if you can catch any nasty bugs because something isn't getting pushed/pulled at the right time! it's next on the bug list. Lemme know what you come up with. Dan McCoy - Macintosh Lab Technician -- [dmccoy@hopi.dtcc.edu] Delaware Technical and Community College President - Micro Enterprises - Premier Apple Computer Repair Sysop - The Micro BBS: (609) 299-0374 [14.4K baud/v.32/42bis] ------------------------------------------------------------------ From :root@antimatter.ecore.fnet.org Date :11/03/95 00:16:40 -0500 (EST) Subj :Carbon Copies * I found the following header in my UUCP packet log... I never received this item. The only reference to antimatter is in the CC: line, so I'm assuming xevmailer isn't recognizing CC: lines on incoming mail... >%%% Packet: 'D.22130.4721' >From jds Thu Nov 2 20:47:21 1995 remote from werthur >Received: from c4bbs.c4systm.com by werthur.c4systm.COM id aa22121; >2 Nov 95 20:46 EST >From: "James D. Stewart" >Ppath: zatezalo.2@osu.edu >To: zatezalo.2@osu.edu >Subject: Re: ecore.fnet.org >Cc: root@antimatter.ecore.fnet.org >X-Mailer: ScoMail 1.0 >Date: Thu, 2 Nov 1995 20:46:10 -0500 (EST) >Message-ID: <9511022046.aa07099@c4bbs.c4systm.COM> On furthur examination, I found the letter in question still in my outgoing spool (it remailed it to you, Shane, since xevmailer didn't think it belonged here - you'll probably get another copy of it about the same time you get this) and discovered a few minor problems with it... * When extracting a message ID from an incoming mail, xevmailer is including the space between the Message-ID: preface and the ID itself, which leaves a leading space on the message ID. msgid$=" " * When replacing a Message-ID in the new header, it's adding ANOTHER set of braces <> around it, even though it already has them. msgid$="< >" * It's adding an entire new header onto mail that was not intended for this system, and losing a lot of the header information in the process (such as Cc: lines, etc) instead of preserving the original header and adding a "Received from werthur.c4systm.com by antimatter.ecore.fnet.org at