From: SMTP%"MX-List@WKUVX1.WKU.EDU" 9-APR-1994 11:00:29.35 To: EVERHART CC: Subj: MX V4.0 X-Listname: Message Exchange Discussion List Warnings-To: <> Errors-To: owner-mx-list@WKUVX1.WKU.EDU Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 07 Apr 1994 08:58:31 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU Message-Id: <0097C97C.BFEE10A4.3@ALPHA.WKU.EDU> Subject: MX V4.0 OK. Thanks to Martin Winter, who correctly figured out what the problem was with the inability to create the queue during the post-install phase, I've come up with the solution I should have used when he first pointed out the initial problem. KITINSTAL.COM now does: $ @SYS$STARTUP:MX_STARTUP LOGICALS before creating the queue file. Duh---now everything is as it should be before it even attempts to create it. I've updated the MX V4.0 distributions everywhere to include this change to KITINSTAL.COM. THIS IS THE ONLY CHANGE IN THE KIT---THERE IS NO NEED TO GET THE ZIP FILE AGAIN. I would have just let it go, but I didn't want brand-new users to keep having the problem---so anybody that picks up from today on won't see it. AGAIN, THAT'S THE ONLY CHANGE THAT WAS MADE. Unfortunately, another bug was brought to my attention. This bug only affects sites using MLF to run mailing lists. One of the changes in MX V4.0 was that lists now go out with "owner-listname" as the Sender: and Errors-To: address. Bounces come back in to owner-listname, which MLF delivers to the /ERRORS_TO address for the "listname" list. All works fine and dandy except from *local* bounces. 8-( If your SMTP agents, for example, can't deliver a message and bounce it back to owner-listname, the bounce message is actually delivered to the SYSTEM_USERS, not the /ERRORS_TO address. The reason is that MLF has always forwarded messages from the local postmaster to the system users---it was never supposed to receive anything from the local postmaster. However, with the owner- change, it can and will receive such messages, only I didn't think of that in time. ;-) This will be fixed in the next release of MX. I don't know if it's severe enough to warrant the trouble of a V4.0-1 release so soon, but I'll probably do one if anything else shows up. Thanks to George Greenwade who spotted the behavior. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET)