Archive-Date: Thu, 2 Apr 1998 14:19:20 -0800 From: Hunter Goatley Reply-To: MX-List@MadGoat.com Subject: Re: MX Servers Filling Up Disk Date: Thu, 02 Apr 1998 16:04:17 -0600 Message-ID: <3523B701.18DF1B84@MadGoat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: mfleming@csubak.edu To: MX-List@WKUVX1.WKU.EDU Michael W. Fleming wrote: > > I've got MX 4.2 on VMS 5.5-2. Our system disk (which is where > mxroot:[queue...] is) just got filled up with multi-megabyte mail messages > which of course ground our system to a halt. VMS, gracious OS that it is, > allowed me to do some cleaning from the console and after a few minutes it > unclogged itself and seems to be normal again. > > However, I would like to prevent this from happening again and am looking > for suggestions. I suppose I could move the MX queue space to another > disk; however, that would just relocate my problem (albeit perhaps making > it a little less severe). Yes, that's one thing I would strongly recommend just for that reason. >Is there a way to tell MX to start rejecting > mail if the queue disk gets to less than XXX blocks free (I didn't see > anything in the docs)? No, there's not, but that would probably be a good thing to add. >If MX starts writing to disk and gets an error > message that the disk is full, does it delete the partial message and > inform the sender that the message is undeliverable? If it doesn't, is > there any reason why that logic shouldn't be added? > MX V5.0 does a much better job of checking such statuses. MX V4.2 and earlier didn't check many status values for things like that---it just assumes that reads and writes to the disk will succeed. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Sat, 4 Apr 1998 18:35:06 -0800 From: eplan@kapsch.co.at (Peter LANGSTOEGER) Subject: Re: Message Exchange products for NT? Date: 5 Apr 98 01:55:47 GMT Message-ID: <3526e4a3.0@nevada.kapsch.co.at> Reply-To: MX-List@MadGoat.com To: MX-List@WKUVX1.WKU.EDU In article <01BD5CD7.F0F82440.Kurt.Schumacher@schumi.ch>, "Kurt A. Schumacher" writes: >We are looking for a Win NT based message exchange >software to implement a basic mail router in a FireWall-1 >DMZ. The whole job to do is simply RELAYING SMTP >from and to different MS Exchange servers on the internal >network. Why not let FW1 relay the SMTP to the correct Exchange servers and avoid the additional system ? ------------------------------------------------------------------------ Peter "EPLAN" LANGSTOEGER Tel. +43 1 81111-2382 Network and OpenVMS system manager Fax. +43 1 81111-888 Technical Computer Center (ADV) E-mail eplan@kapsch.net <<< KAPSCH AG Wagenseilgasse 1 PSImail PSI%(0232)281001141::EPLAN A-1121 VIENNA AUSTRIA "I'm not a pessimist, I'm a realist" ================================================================================ Archive-Date: Sat, 4 Apr 1998 19:38:09 -0800 From: "Patrick Cox" To: mx-list@madgoat.com Date: Sat, 4 Apr 1998 23:37:54 AST Subject: Footer text for mailing lists: is it possible Reply-To: MX-List@MadGoat.com Message-ID: Has anybody come up with a way (or is there a way, or wishlist) to add text to the end of mailing list messages. This footer would contain something like: Messages to: mx-list@madgoat.com Commands to: mx-list-request@madgoat.com List Owner: goathunter@madgoat.com Web Site: www.madgoat.com This text is added to the end of every message that leaves the MX-mailing-list-server. This keeps down the "How do I unsubscribe" messages, and can give extra info. I've had a list owner here ask me if this was possible. This text would either be controlled by the list owner or the MX administrator. Probably easier for the admin to do it. Create a file in the [mailing_lists] directory => mx-list.footer that would contain the text. Or a command sent by the list owner that would create this file and add the text between the commands footer and quit. I'm beginning to ramble ... thoughts, suggestion, sneaky tricks appreciated. Patrick M. Cox Information Technology Section (Truro) Resources Corporate Services Unit (DAM,DNR,Fish,Env) (902)893-6233 ================================================================================ Archive-Date: Sun, 5 Apr 1998 10:25:22 -0700 Sender: madison@MadGoat.Com Date: Sun, 5 Apr 1998 10:25:09 -0700 From: Matt Madison Reply-To: MX-List@MadGoat.com To: madgoat-announce@MadGoat.Com, mx-list@MadGoat.Com Message-ID: <009C4405.92D56443.1@MadGoat.Com> Subject: SPAMFILTER V2.0 now available SPAMFILTER V2.0 is a free add-on for MX V5.0 that assists in the automatic detection and blocking of junk e-mail (also known as "spam"). For more information on SPAMFILTER, visit http://www.madgoat.com/spamfilter.html The software is available from the MadGoat FTP server: ftp://ftp.madgoat.com/mx/mx050/addons/spamfilter020.zip This package is an major update to the version provided with the MX V5.0 distribution kit. Besides functional enhancements, the package now includes a manual describing its configuration and operation. -Matt -- Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA madison@madgoat.com http://www.madgoat.com ================================================================================ Archive-Date: Sun, 5 Apr 1998 10:28:51 -0700 Sender: madison@MadGoat.Com Date: Sun, 5 Apr 1998 10:28:45 -0700 From: Matt Madison Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: pcox@es.nsac.ns.ca Message-ID: <009C4406.134393B1.35@MadGoat.Com> Subject: RE: Footer text for mailing lists: is it possible >Has anybody come up with a way (or is there a way, or wishlist) to add >text to the end of mailing list messages. This footer would contain >something like: > >Messages to: mx-list@madgoat.com >Commands to: mx-list-request@madgoat.com > List Owner: goathunter@madgoat.com > Web Site: www.madgoat.com While there is no provision in the mailing list processor for an automatic footer appended to each message, with MX V5.0 there are some headers that can be added. See the help for the DEFINE LIST/LIST_HEADERS and DEFINE LIST/XHEADERS commands for more information. -Matt -- Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA madison@madgoat.com http://www.madgoat.com ================================================================================ Archive-Date: Mon, 6 Apr 1998 17:42:46 -0700 Date: Mon, 06 Apr 1998 19:44:09 EDT From: Robert Byer Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009C451C.D49E3040.43@mail.all-net.net> Subject: PROBLEM: MX v4.2 SMTP Server Stopping... -----BEGIN PGP SIGNED MESSAGE----- HELP!!!! All of a suddent I'm having trouble with the SMTP server in MX v4.2 stopping all of a sudden. I have installed the MX patch that's on the MadGoat site quite some time ago and I haven't had a problem with the server until recently. I defined the debug logical for the SMTP server and this is what it told me. =========================================================================== 6-APR-1998 16:51:22.66 STM[6]: Send "220 carl MX V4.2 VAX SMTP server ready at Mon, 06 Apr 1998 16:51:22 EDT" 6-APR-1998 16:51:22.87 STM[6]: Receive "HELO sl1.supralink.net" 6-APR-1998 16:51:22.90 STM[6]: Send "250 Hello, sl1.supralink.net" 6-APR-1998 16:51:23.24 STM[6]: Receive "MAIL FROM:" 6-APR-1998 16:51:23.34 STM[6]: Send "250 MAIL command accepted." 6-APR-1998 16:51:23.49 STM[6]: Receive "RCPT TO:" 6-APR-1998 16:51:23.51 STM[6]: Send "250 Recipient okay (at least in form)" 6-APR-1998 16:51:26.89 STM[6]: Receive "DATA" 6-APR-1998 16:51:27.38 STM[6]: Send "354 Start mail input; end with ." 6-APR-1998 16:51:27.79 STM[6]: Receive "Received: from pavilion ([199.174.242.210]) by sl1.supralink.net" 6-APR-1998 16:51:27.80 STM[6]: Receive " (Netscape Mail Server v2.02) with SMTP id AAC112;" 6-APR-1998 16:51:27.80 STM[6]: Receive " Mon, 6 Apr 1998 04:48:24 -0400" 6-APR-1998 16:51:27.81 STM[6]: Receive "Received: from mailgate21-hme0.a001.sprintmail.com(205.137.196.52) by mailgate31-hme1.a001.sprintmail.com (8.8.5/8.7.3) with SMTP id XAA07580 for ; Mon, 6 April 1998 01:44:07 -0700 (EDT)" 6-APR-1998 16:51:27.82 STM[6]: Receive "To: karen059@juno.com" 6-APR-1998 16:51:27.82 STM[6]: Receive "Bcc: charles@axtec.com, charles@aye.net, charles@backdoor.com, charles@backdoor.comdec, charles@barkley.com, charles@bazaar.com, charles@bconnex.net, charles@bga.com, charles@bgumail.bgu.ac.il, charles@bkm.ca, char =========================================================================== So it appears that something in this message is killing the server. Here's the MX_SMTP_CARL.LOG; =========================================================================== 6-APR-1998 19:08:10.30: MX SMTP (pid 6020074D) starting 6-APR-1998 19:12:03.87: MX SMTP (pid 6020074D) exiting, status = 00000001 =========================================================================== I would appreciate any and all help with this as this is starting to drive me crazy. +------------------------+--------------------------------------------+ | Robert Alan Byer | A-Com Computing, Inc. | | Vice-President | 115 W. Washington Street, Suite 1165 | | A-Com Computing, Inc. | Indianapolis, IN 46204 | | Phone: (317)673-4204 | http://www.all-net.net/ | +------------------------+-----+--------------------------------------+ | byer@mail.all-net.net | I don't want to take over the world, | | http://www.all-net.net/~byer | just my own little part of it. | +------------------------------+--------------------------------------+ | Send an E-mail request to obtain my PGP key. | +---------------------------------------------------------------------+ -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQEVAwUBNSkv/qVSqzlBVJbBAQEuawf/YEkb1KT67b5e81q/176TdhNFHeBP2jzD SoL7BWnwffO4XEVCcwreFT/cfll2HcnussFn9fEvfMNF+jdipQPzTFi1aJIZ50wm GmOUjPtboUmF9bTzfTAW0OuKN07qTWTVYgaHUcVgTG7/+4+poEqANIUUQpjjtCIK n18IjrUIdcaaWbnEEGVj7WHw1LxJS1DvsnbBB1+E05emXDX6ZkXjx2edYiQ1zFxS +KMXmsXKcyf8PLC8+dQOk/5eMjivTm8rBxJ983kqvbThVVY3FmDgBQDfR0Bs6PU/ yLEF4fs64yIXhkYAT8bis/P0q9zxNyhmHH65c0c9ES7sgmGwOIeoBQ== =gYU7 -----END PGP SIGNATURE----- ================================================================================ Archive-Date: Mon, 6 Apr 1998 17:48:49 -0700 Date: Mon, 6 Apr 1998 17:48:43 -0700 From: Dan Wing Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: BYER@CARL.ALL-NET.NET Message-ID: <980406174843.203d797d@Cisco.COM> Subject: RE: PROBLEM: MX v4.2 SMTP Server Stopping... > 6-APR-1998 16:51:22.66 STM[6]: Send "220 carl MX V4.2 VAX SMTP server ready at Mon, 06 Apr 1998 16:51:22 EDT" > 6-APR-1998 16:51:22.87 STM[6]: Receive "HELO sl1.supralink.net" > 6-APR-1998 16:51:22.90 STM[6]: Send "250 Hello, sl1.supralink.net" > 6-APR-1998 16:51:23.24 STM[6]: Receive "MAIL FROM:" > 6-APR-1998 16:51:23.34 STM[6]: Send "250 MAIL command accepted." > 6-APR-1998 16:51:23.49 STM[6]: Receive "RCPT TO:" > 6-APR-1998 16:51:23.51 STM[6]: Send "250 Recipient okay (at least in form)" > 6-APR-1998 16:51:26.89 STM[6]: Receive "DATA" > 6-APR-1998 16:51:27.38 STM[6]: Send "354 Start mail input; end with ." > 6-APR-1998 16:51:27.79 STM[6]: Receive "Received: from pavilion ([199.174.242.210]) by sl1.supralink.net" > 6-APR-1998 16:51:27.80 STM[6]: Receive " (Netscape Mail Server v2.02) with SMTP id AAC112;" > 6-APR-1998 16:51:27.80 STM[6]: Receive " Mon, 6 Apr 1998 04:48:24 -0400" > 6-APR-1998 16:51:27.81 STM[6]: Receive "Received: from mailgate21-hme0.a001.sprintmail.com(205.137.196.52) by mailgate31-hme1.a001.sprintmail.com (8.8.5/8.7.3) with SMTP id XAA07580 for ; Mon, 6 April 1998 01:44:07 -0700 (EDT)" 6-APR-1998 16:51:27.82 STM[6]: Receive "To: karen059@juno.com" 6-APR-1998 16:51:27.82 STM[6]: Receive "Bcc: charles@axtec.com, charles@aye.net, charles@backdoor.com, charles@backdoor.comdec, charles@barkley.com, charles@bazaar.com, charles@bconnex.net, charles@bga.com, charles@bgumail.bgu.ac.il, charles@bkm.ca, char > >=========================================================================== > >So it appears that something in this message is killing the server. It's a really long BCC header line that is killing the server. You're sure you installed the patch which fixes this problem? The message that's killing the SMTP server is spam, so another short-term solution would be black-hole route the system sending you the spam. How you do this depends on which TCP/IP package you're running on your VMS box. -Dan Wing ================================================================================ Archive-Date: Tue, 7 Apr 1998 07:12:53 -0700 Date: Tue, 7 Apr 1998 10:10:21 -1300 From: system@eagle.navsses.navy.mil Reply-To: MX-List@MadGoat.com To: mx-list@madgoat.com Message-ID: <009C4595.D634F1E0.43@eagle.navsses.navy.mil> Subject: SPAMFILTER V2.0 BETA causes MX ROUTER ACCVIO In an effort to curtail the spam coming in to my users' mailboxes I installed the SPAMFILTER V2.0 Beta that was announced a week or so ago. While this was set up I kept loosing all of my MX ROUTER processes to ACCVIOs. I turned on the debug and it didn't tell me a thing. Is this a known problem? Thanks, Mike Jacobi ================================================================================ Archive-Date: Tue, 7 Apr 1998 07:27:23 -0700 Sender: madison@MadGoat.Com Date: Tue, 7 Apr 1998 07:27:17 -0700 From: Matt Madison Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: system@eagle.navsses.navy.mil Message-ID: <009C457F.0E85A8C1.1@MadGoat.Com> Subject: RE: SPAMFILTER V2.0 BETA causes MX ROUTER ACCVIO >In an effort to curtail the spam coming in to my users' mailboxes I installed >the SPAMFILTER V2.0 Beta that was announced a week or so ago. While this was >set up I kept loosing all of my MX ROUTER processes to ACCVIOs. I turned on >the debug and it didn't tell me a thing. Is this a known problem? Nope... could you send me the output from $ SHOW LOGICAL/FULL SPAMFILTER*/SYSTEM or, if you aren't running it any more, send me the SPAMFILTER_SYSTARTUP.COM that you were using? Also, was this on an Alpha or a VAX system? Thanks, -Matt -- Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA madison@madgoat.com http://www.madgoat.com ================================================================================ Archive-Date: Tue, 7 Apr 1998 10:53:31 -0700 Date: Tue, 7 Apr 1998 13:37:55 -1300 From: system@eagle.navsses.navy.mil Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: system@eagle.navsses.navy.mil Message-ID: <009C45B2.D56C4480.76@eagle.navsses.navy.mil> Subject: RE: SPAMFILTER V2.0 BETA causes MX ROUTER ACCVIO > >Nope... could you send me the output from > > $ SHOW LOGICAL/FULL SPAMFILTER*/SYSTEM > >or, if you aren't running it any more, send me the SPAMFILTER_SYSTARTUP.COM >that you were using? Also, was this on an Alpha or a VAX system? > >Thanks, >-Matt > >-- >Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA >madison@madgoat.com http://www.madgoat.com Matt, I have just gotten it installed. There are no SPAMFILTER* logicals defined. Just the MX_SITE_MESSAGE_FILTER which translates to MX_EXE:SPAMFILTER. As soon as I start MX with that the ROUTERs just start dying with an accvio (status 1000000C). mike ================================================================================ Archive-Date: Tue, 7 Apr 1998 20:36:22 -0700 Date: Tue, 07 Apr 1998 22:37:37 EDT From: Robert Byer Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.Com Message-ID: <009C45FE.3AD35340.30@mail.all-net.net> Subject: MX v4.2 SMTP Server STILL Stopping.. -----BEGIN PGP SIGNED MESSAGE----- I've reinstalled MX v4.2, installed the latest version of NetLib and installed the patch files from the MadGoat FTP site and even completely restarted my server. And the SMTP server process is still stopping. And from what I can tell in the log files is is because of a long BCC line, which I thought was supposed to be fixed in the patches. I would appreciate any and all help on this as this is getting quite annoying and I'll even give someone an account on the server to help solve this. +------------------------+--------------------------------------------+ | Robert Alan Byer | A-Com Computing, Inc. | | Vice-President | 115 W. Washington Street, Suite 1165 | | A-Com Computing, Inc. | Indianapolis, IN 46204 | | Phone: (317)673-4204 | http://www.all-net.net/ | +------------------------+-----+--------------------------------------+ | byer@mail.all-net.net | I don't want to take over the world, | | http://www.all-net.net/~byer | just my own little part of it. | +------------------------------+--------------------------------------+ | Send an E-mail request to obtain my PGP key. | +---------------------------------------------------------------------+ -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQEVAwUBNSqqJ6VSqzlBVJbBAQErzgf+M3bxF4omFSt94ezqpew6M326FPVw7G5X tYc3roztEv7h0v/TFVk4LNbSUCRpTU3NQ5vjGVvOn06l1j7Uw3FCjhb2ITuHBnXe 4aqF1CqOoFU+eJMfqsFyBrrjrKo0v944tSwnSphxhMjFGI2TVfY+GddBCOuXZLcx d6QIDL0WsTwoWCrWjbzzAaQtHcrMN3YKnIa9bjaMgH+DUiRz0h7W21UvkZ2qytJP UX5Uk2PRnBVlazUYJlDnt7PLsECavpwEmMkbopqdbB+VxlUG57pte0+ZIoPj9Bbt DRSf1rsEKxv1dudVjR2s8aP0FTo8fv0z7V1CSwdmrdvzUviydBoWyw== =YjZ3 -----END PGP SIGNATURE----- ================================================================================ Archive-Date: Wed, 8 Apr 1998 05:40:59 -0700 Sender: goathunter@MadGoat.com Date: Wed, 8 Apr 1998 07:40:47 -0500 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: BYER@MAIL.ALL-NET.NET Message-ID: <009C464A.1C1019C0.23@ALPHA.WKU.EDU> Subject: RE: MX v4.2 SMTP Server STILL Stopping.. Robert Byer writes: > >And the SMTP server process is still stopping. > >And from what I can tell in the log files is is because of a long >BCC line, which I thought was supposed to be fixed in the patches. > Yes, it should have been. The fix should apply to all headers. >I would appreciate any and all help on this as this is getting quite >annoying and I'll even give someone an account on the server to help >solve this. > Dan's suggestion to black-hole the site is the quickest solution. Check the MX-List archives for info on how to do this: http://www2.wku.edu/scripts/mxarchive/as_init.com?MX-List Hunter ------ Hunter Goatley, Process Software, http://www.process.com http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Wed, 8 Apr 1998 08:09:38 -0700 From: Hunter Goatley Reply-To: MX-List@MadGoat.com Subject: Re: MX Servers Filling Up Disk Date: Wed, 08 Apr 1998 09:47:10 -0500 Message-ID: <352B479E.F807D0A@MadGoat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Michael W. Fleming" To: MX-List@WKUVX1.WKU.EDU Michael W. Fleming wrote: > > My thought was, shutdown MX, change the MX_FLQ_DIR logical, backup the > original queue directories and restore them to the new location. > > Two problems with that--first, I couldn't find where MX_FLQ_DIR is defined > during startup; second, I can't be sure that there isn't some place in > some other file where there is a hard-coded reference to the queue > directories (although that would seem to defeat the purpose of having the > logical). > Right. After you move the queue directory, you should edit these files and change any disk references: SYS$STARTUP:MX_STARTUP.COM MX_DIR:MX_LOGICALS.DAT That should take care of everything, if memory serves. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Wed, 8 Apr 1998 08:39:22 -0700 Message-ID: <05d601bd6304$6a5c6120$2708017e@gr-359523.si.com> From: "Brian Tillman" Reply-To: MX-List@MadGoat.com To: Subject: Don't translate at install (was: Re: MX Servers Filling Up Disk) Date: Wed, 8 Apr 1998 11:38:44 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hunter Goatley (goathunter@PROCESS.COM) writes: >Right. After you move the queue directory, you should edit these >files and change any disk references: > >SYS$STARTUP:MX_STARTUP.COM >MX_DIR:MX_LOGICALS.DAT > >That should take care of everything, if memory serves. I've always wondered why MX's installation translates EXEC mode, TERMINAL logical names down to the physical device. I wish it wouldn't do that. It's not necessary to do that for the rooted logicals, since it's OK to define a rooted logical in terms of a terminal logical. I do it all the time and it works. An example: on our system we have a terminal, EXEC mode logical MX_DISK. When I install MX, it asks for the destination. I enter MX_DISK. I want all other MX logicals to show up in terms of this logical, not the physical disk, so that I can move MX more simply. That's the _purpose_ of EXEC mode terminal logicals (well, one of the purposes). I would like to simply drop the MX_DEVICE logical MX creates. It's simply not needed. MX_ROOT should be defined in terms of what I enter at installation, not in terms of what the string I enter translates to. I know what I want. Why does MX have to second-guess? Brian Tillman Internet: tillman_brian at si.com Smiths Industries, Inc. tillman at swdev.si.com 4141 Eastern Ave., MS239 Addresses modified to prevent Grand Rapids, MI 49518-8727 SPAM. Replace "at" with "@" This opinion doesn't represent that of my company ================================================================================ Archive-Date: Thu, 9 Apr 1998 08:03:21 -0700 Sender: madison@MadGoat.Com Date: Thu, 9 Apr 1998 08:03:14 -0700 From: Matt Madison Reply-To: MX-List@MadGoat.com To: tillman@swdev.si.com CC: mx-list@MadGoat.Com Message-ID: <009C4716.695FFD99.2@MadGoat.Com> Subject: RE: Don't translate at install >I've always wondered why MX's installation translates EXEC mode, TERMINAL >logical names down to the physical device. I wish it wouldn't do that. >It's not necessary to do that for the rooted logicals, since it's OK to >define a rooted logical in terms of a terminal logical. I do it all the >time and it works. Actually, in V5.0, this only happens for one logical name, MX_DEVICE. It used to be done for MX_FLQ_DIR: as well. This means that only the one file, SYS$STARTUP:MX_STARTUP.COM needs to be changed in the case of a move, provided you entered the queue directory specification using a logical name that is relative to MX_ROOT or MX_DEVICE (as the default answer would be in the case of a new install) or some other logical that will also be correct after the move. >An example: on our system we have a terminal, EXEC mode logical MX_DISK. >When I install MX, it asks for the destination. I enter MX_DISK. I want >all other MX logicals to show up in terms of this logical, not the physical >disk, so that I can move MX more simply. That's the _purpose_ of EXEC mode >terminal logicals (well, one of the purposes). I would like to simply drop >the MX_DEVICE logical MX creates. It's simply not needed. MX_ROOT should >be defined in terms of what I enter at installation, not in terms of what >the string I enter translates to. I know what I want. Why does MX have to >second-guess? Mainly to protect the installation and startup procedures so that they are guaranteed to work correctly in all cases, while preventing them from having to handle the non-working cases specially. For example, the installer could have used a supervisor-mode logical name, or a rooted logical name, as the device specification for the top-level MX directory. Either of those would work OK during installation, but would cause the startup procedure or some part of MX to fail. Those are just examples; there are other variations that could cause other problems, too. I'll admit that the installation procedure is perhaps a bit too strong about this when it writes out SYS$STARTUP:MX_STARTUP.COM. You can edit that file and replace the physical device name with your logical name if you wish (just be careful, of course). I will also look at loosening it up a bit in the next release. -Matt -- Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA madison@madgoat.com http://www.madgoat.com ================================================================================ Archive-Date: Thu, 9 Apr 1998 08:08:27 -0700 Date: Thu, 09 Apr 1998 09:07:52 MST From: Rainy days Reply-To: MX-List@MadGoat.com To: mx-list@madgoat.com Message-ID: <009C471F.70609B40.228@upi.uhcolorado.edu> Subject: Stuck mail after firewall install The owners of the network we are on installed a firewall late last week (without telling us of course!), and for 3 days our external email built up while they tried to fix problems. Mail came through the firewall fine but could not go out. Now that it is fixed, new messages go out just as they should, but those old ones just keep retrying and retrying with %SYSTEM- F-TIMEOUT, device timeout errors. How can I get those mailed out? And what actually happened in MX for these to get stuck? MX 4.1 (I know - UPGRADE!) Thanks! Bill Monday Systems Administrator University Physicians, Inc wam@upi.uhcolorado.edu ================================================================================ Archive-Date: Thu, 9 Apr 1998 15:40:17 -0700 Date: Thu, 9 Apr 1998 15:40:09 -0700 From: Dan Wing Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <980409154009.20285572@Cisco.COM> Subject: RE: Stuck mail after firewall install >The owners of the network we are on installed a firewall late last week >(without telling us of course!), and for 3 days our external email built >up while they tried to fix problems. Mail came through the firewall fine >but could not go out. Now that it is fixed, new messages go out just as >they should, but those old ones just keep retrying and retrying with %SYSTEM- >F-TIMEOUT, device timeout errors. How can I get those mailed out? And what >actually happened in MX for these to get stuck? MX 4.1 (I know - UPGRADE!) Sounds like outgoing TCP connections are blocked. Try Telnetting to port 25 of one of the mail hosts and see what happens -- you'll probably get a timeout. Unfortuantely, I don't believe you can get the MX Router to look at an entry after it has processed it. If you could get it to do that, you could change your default path to point at a specific host which _does_ have Internet connectivity until your outgoing connectivity is restored. ("MCP DEFINE PATH * SMTP/ROUTE=host"). Perhaps someone else has another idea along the same lines and can offer a suggested solution. -d ================================================================================ Archive-Date: Thu, 9 Apr 1998 15:44:40 -0700 Sender: goathunter@MadGoat.com Date: Thu, 9 Apr 1998 17:44:25 -0500 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009C4767.99D78C57.6@goat.process.com> Subject: RE: Stuck mail after firewall install Dan Wing writes: > >Unfortuantely, I don't believe you can get the MX Router to look at >an entry after it has processed it. If you could get it to do that, >you could change your default path to point at a specific host which >_does_ have Internet connectivity until your outgoing connectivity >is restored. ("MCP DEFINE PATH * SMTP/ROUTE=host"). Perhaps someone >else has another idea along the same lines and can offer a suggested >solution. > You can force the MX Router to reprocess the entry by doing a QUEUE READY on the router entry. For example: 48 INPROG 1019070 LOCAL SMTP 6 READY 22646 (waiting until 9-APR-1998 18:05:40.83) Entry 48 is the original entry, so QUEUE READY 48 would cause MX Router to reprocess the entry. The rest of what Dan says should then do the trick. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Thu, 9 Apr 1998 15:57:09 -0700 Date: Thu, 09 Apr 1998 16:57:09 MST From: Rainy days Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009C4760.FF78C640.3@upi.uhcolorado.edu> Subject: RE: Stuck mail after firewall install ! From: MX%"MX-List@MadGoat.com" 9-APR-1998 16:47:42.97 ! To: MX%"MX-List@MadGoat.com" ! CC: ! Subj: RE: Stuck mail after firewall install ! ! Dan Wing writes: ! > ! >Unfortuantely, I don't believe you can get the MX Router to look at ! >an entry after it has processed it. If you could get it to do that, ! >you could change your default path to point at a specific host which ! >_does_ have Internet connectivity until your outgoing connectivity ! >is restored. ("MCP DEFINE PATH * SMTP/ROUTE=host"). Perhaps someone ! >else has another idea along the same lines and can offer a suggested ! >solution. ! > ! You can force the MX Router to reprocess the entry by doing a QUEUE ! READY on the router entry. For example: ! ! 48 INPROG 1019070 LOCAL ! SMTP 6 READY 22646 ! (waiting until 9-APR-1998 18:05:40.83) ! ! Entry 48 is the original entry, so QUEUE READY 48 would cause MX ! Router to reprocess the entry. The rest of what Dan says should then ! do the trick. ! ! Hunter ! ------ ! Hunter Goatley, Process Software, http://www.process.com/ ! http://www.madgoat.com/hunter.html Guess it would have helped if I had read the HELP QUEUE READY. Thank you both very much! Everything is so much happier now! -Bill Monday ================================================================================ Archive-Date: Thu, 9 Apr 1998 22:20:30 -0700 Date: Thu, 09 Apr 1998 22:20:29 -0700 From: "Vanya J. Cooper" Reply-To: MX-List@MadGoat.com To: MX-LIST@MADGOAT.COM CC: Vanya@VJC.COM Message-ID: <009C478E.2AB81EA0.206@VJC.COM> Subject: Source patch for MX 4.2 string too long errors? I think this came up a couple months ago when 5.0 came out, but I couldn't find anything in the archives. Is there a source version of the patch for the 4.2 SMTP server available somewhere that fixes the string too long errors for header lines > 64K? I am going to be stuck on MX 4.2 for a while yet and would like to be able to rebuild it if necessary. ..Vanya Vanya Jonathan Cooper VJC Consulting & Services Vanya@VJC.COM http://www.vjc.com/vanya/ Phone: +1 520 881-4455 ================================================================================ Archive-Date: Thu, 9 Apr 1998 22:22:22 -0700 Sender: goathunter@MadGoat.com Date: Fri, 10 Apr 1998 00:22:06 -0500 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009C479F.2864DFB5.3@goat.process.com> Subject: RE: Source patch for MX 4.2 string too long errors? "Vanya J. Cooper" writes: > >I think this came up a couple months ago when 5.0 came out, but I couldn't find >anything in the archives. Is there a source version of the patch for the 4.2 >SMTP server available somewhere that fixes the string too long errors for >header lines > 64K? I am going to be stuck on MX 4.2 for a while yet and would >like to be able to rebuild it if necessary. > No, not yet. I apparently lost the actual .B32 file for the V4.2 patch image. It's on my to-do list to recreate that.... Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Thu, 9 Apr 1998 23:12:58 -0700 Date: Thu, 09 Apr 1998 23:12:57 -0700 From: "Vanya J. Cooper" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: Vanya@VJC.COM Message-ID: <009C4795.7F1BF460.257@VJC.COM> Subject: RE: Source patch for MX 4.2 string too long errors? > From: Hunter Goatley > "Vanya J. Cooper" writes: > >I think this came up a couple months ago when 5.0 came out, but I couldn't find > >anything in the archives. Is there a source version of the patch for the 4.2 > >SMTP server available somewhere that fixes the string too long errors for > >header lines > 64K? I am going to be stuck on MX 4.2 for a while yet and would > >like to be able to rebuild it if necessary. > > > No, not yet. I apparently lost the actual .B32 file for the V4.2 > patch image. It's on my to-do list to recreate that.... Bummer, thanks for the update. I would also like to publicly express my thanks for the outstanding past and present support of MX. With all the other projects I'm sure are competing for your time, I greatly appreciate that such a task would even make it to your to-do list. ..Vanya Vanya Jonathan Cooper VJC Consulting & Services Vanya@VJC.COM http://www.vjc.com/vanya/ Phone: +1 520 881-4455 ================================================================================ Archive-Date: Mon, 13 Apr 1998 00:33:12 -0700 From: Hunter Goatley Reply-To: MX-List@MadGoat.com Subject: Re: MX List Server Subjects Date: Mon, 13 Apr 1998 00:21:01 -0500 Message-ID: <35315A6D.2F0A9B69@MadGoat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: mfleming@csubak.edu To: MX-List@WKUVX1.WKU.EDU Michael W. Fleming wrote: > > A number of mailing lists these days sport list-specific info prepended to > the subject line of all messages. For example: someone sends a message to > the Birdwatch list and their subject line is "Yellow-speckled Twit Bird > Sighting", the list server gets it and sends it out as "[Birdwatch] > Yellow-speckled Twit Bird Sighting". Someone else sends a reply with a > subject of "re: [Birdwatch] Yellow-speckled Twit Bird Sighting" and the > list server sends it out with the subject unchanged because it saw the > [Birdwatch] already there. > > By now you've seen the writing on the wall... Can MX do this? Any > version? I saw nothing in the docs for 4.2. > MX V5.0 includes that feature.... -- Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Wed, 15 Apr 1998 08:48:24 -0700 Date: Wed, 15 Apr 1998 17:48:00 +0200 Message-ID: <8611-Wed15Apr1998174800+0200-levitte@lp.se> From: Richard Levitte - VMS Whacker Reply-To: MX-List@MadGoat.com To: MX-List@madgoat.com CC: levitte@lp.se Subject: FEATURE REQUEST [MX V5.0]: "Received:" header enhancement MIME-Version: 1.0 Content-Type: Text/Plain; Charset=ISO-8859-1 Content-Transfer-Encoding: 8bit I received the spam included below today. One problem, if I want to filter this only for one user, is that I've no idea to which address this was actually sent. RFC822 says the following about the "Received:" header: received = "Received" ":" ; one per relay ["from" domain] ; sending host ["by" domain] ; receiving host ["via" atom] ; physical path *("with" atom) ; link/mail protocol ["id" msg-id] ; receiver msg id ["for" addr-spec] ; initial form ";" date-time ; time received What I'm interested in is to see the "initial form" part being implemented. Could that be inserted into the wish list? ------------------------------------------------------------------------ Return-Path: Received: from www.imailinfo.com (193.220.22.110) by nic.lp.se (MX V5.0) with SMTP; Wed, 15 Apr 1998 15:15:37 +0200 From: Internet mail info Reply-To: webmaster@imailinfo.com Organization: Internet e-Mail Informations Subject: Receipt of submission Date: Wed, 15 Apr 1998 15:15:37 +0200 X-Date-Warning: Date header inserted by nic.lp.se X-Junk-Mail-Rating: MEDIUM Hello friend! This mail was send automatically to you, because of your e-mail address was entered to our database. You can remove it from our database or alter your profile at URL http://www.imailinfo.com. [...] ------------------------------------------------------------------------ -- R Levitte, Levitte Programming; Spannv. 38, I; S-168 35 Bromma; SWEDEN Tel: +46-8-26 52 47; Cel: +46-708-20 09 64; No fax right now PGP key fingerprint = A6 96 C0 34 3A 96 AA 6C B0 D5 9A DF D2 E9 9C 65 Check http://richard.levitte.org/ for my public key. bastard@bofh.se "price, performance, quality. Choose any two you like" ================================================================================ Archive-Date: Wed, 15 Apr 1998 10:52:40 -0700 Date: Wed, 15 Apr 1998 10:52:34 -0700 From: Dan Wing Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <980415105234.203e7f2a@Cisco.COM> Subject: RE: FEATURE REQUEST [MX V5.0]: "Received:" header enhancement >I received the spam included below today. One problem, if I want to >filter this only for one user, is that I've no idea to which address this >was actually sent. RFC822 says the following about the "Received:" >header: > > received = "Received" ":" ; one per relay > ["from" domain] ; sending host > ["by" domain] ; receiving host > ["via" atom] ; physical path > *("with" atom) ; link/mail protocol > ["id" msg-id] ; receiver msg id > ["for" addr-spec] ; initial form > ";" date-time ; time received > >What I'm interested in is to see the "initial form" part being >implemented. Could that be inserted into the wish list? I added that to MultiNet's SMTP awhile back, mostly to help with address rewriting and folder delivery. You cannot have multiple addr-spec's listed, so if the message is for multiple recipients, you can't list it at all. If the message is for one recipient, you can list the "for ". Note that there is a slight "security" implication with this: if you know that the mailer generates a "for addr-spec", but there isn't one present, but the RFC822 headers only indicate one recipient, then you know the message was BCC'd to other recipients. -Dan Wing ================================================================================ Archive-Date: Wed, 15 Apr 1998 12:39:29 -0700 Message-ID: <01BD68B6.EB575E30.Kurt.Schumacher@schumi.ch> From: "Kurt A. Schumacher" Reply-To: MX-List@MadGoat.com To: "'MX-List@madgoat.com'" Subject: Obvious spam passed all checks! Date: Wed, 15 Apr 1998 21:39:06 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Here is the mail we received some minutes ago: Return-Path: <> Received: from server02 (208.255.237.163) by elias.decus.ch (MX V5.0) with SMTP; Wed, 15 Apr 1998 19:28:11 +0200 Date: Wed, 15 Apr 1998 09:44:23 X-MX-Warning: Warning -- Invalid "From" header. From: <> To: Subject: ****************************************************** If you wish to be placed on a global remove list go to; ****************************************************** >>>>>>>>>>>>>>>>>>Internet Wealth...>>>>>>>>>>>>>>>>>> If you've tested the MX V5.0; SPAMFILTER 2.0A in place, default configuration Undocumented MAPS RBL activated. Thanks in advance! Kurt -- Kurt A. Schumacher KCS Engineering & Consulting | Auenstrasse 61, CH-8302 Kloten, Switzerland Kurt.Schumacher@schumi.ch POTS +41 1 881 37 88 http://www.schumi.ch FAX: +41 1 881 37 88 ================================================================================ Archive-Date: Mon, 20 Apr 1998 23:31:38 -0700 Date: Tue, 21 Apr 1998 09:32:19 +0300 From: "veli) testing дце (" Reply-To: MX-List@MadGoat.com To: MX-LIST@MADGOAT.COM Message-ID: <009C5090.D7C2EEEE.8@juhani.decus.fi> Subject: MX V5.0 and 8-bit SMTP MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Below is mail which I received. In fact this is really a test mail I sent myself using =22=24telnet smtp.tele.fi 25=22 etc. I intentionally had 8-bit characters at the content stuff. Seems that SONERA FINLAND smtp server tries to negoatiate a 8-bit SMTP mode with JUHANI.DECUS.FI (running MX V5.0) but our system does not claim to support such mode. Quick browse through =24MCP SHOW ALL did not reveal any setting thus I am curious to know whether MX supports 8-bit character set and how to turn it either on or off? _veli From: SMTP%=22KORKKO=40DECUS.FI=22 21-APR-1998 08:24:20.37 To: KORKKO CC:=09 Subj:=09 Return-Path: Received: from smtp.tele.fi (192.89.123.25) by juhani.decus.fi (MX V5.0) wi= th ESMTP; Tue, 21 Apr 1998 08:24:19 +0300 X-Warning: Original message contained 8-bit characters, however during the = SMTP transport session the receiving system was unable to announce capability of receiving 8-bit SMTP (RFC 1651-1653), and as this message does not have MIME headers (RFC 2045-2049) to enable encoding change, we had very little choices. X-Warning: We ASSUME it is less harmful to add the MIME headers, and conver= t the text to Quoted-Printable, than not to do so, and to strip th= e message to 7-bits.. (RFC 1428 Appendix A) X-Warning: We don't know what character set the user used, thus we had to w= rite these MIME-headers with our local system default value. MIME-Version: 1.0 Content-Transfer-Encoding: BINARY Content-Type: TEXT/PLAIN; charset=3DISO-8859-1 Received: from juhani.decus.fi (=5B194.251.14.200=5D HELO JUHANI.DECUS.FI i= dent: NO-IDENT-SERVICE =5Bport 4994=5D) by smtp.tele.fi with SMTP id <22569-21197>; Tue, 21 Apr 1998 08:22:57 +0300 Message-ID: <19980421052257Z22569-21197+146=40smtp.tele.fi> From: To: unlisted-recipients: ; (no To-header on input) Date: Tue, 21 Apr 1998 08:22:55 +0300 X-MX-Comment: QUOTED-PRINTABLE message automatically decoded TEST =C4=C5=D6 TEST =C4=C5=D6 =E4=E5=F6 ================================================================================ Archive-Date: Tue, 21 Apr 1998 07:45:07 -0700 Sender: madison@MadGoat.Com Date: Tue, 21 Apr 1998 07:45:01 -0700 From: Matt Madison Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009C5081.DA95C1AF.3@MadGoat.Com> Subject: RE: MX V5.0 and 8-bit SMTP >Below is mail which I received. In fact this is really a test mail I >sent myself using "$telnet smtp.tele.fi 25" etc. I intentionally >had 8-bit characters at the content stuff. > >Seems that SONERA FINLAND smtp server tries to negoatiate a 8-bit SMTP >mode with JUHANI.DECUS.FI (running MX V5.0) but our system does not claim >to support such mode. > >Quick browse through $MCP SHOW ALL did not reveal any setting thus I am >curious to know whether MX supports 8-bit character set and how to turn it >either on or off? MX V5 does not support the 8BITMIME SMTP extension, which is what the sending system was looking for. It does have some support 8-bit characters, if you use VMS MAIL or DECwindows Mail to compose your message -- MX will automatically convert the message to quoted-printable MIME format for you before queuing it. Likewise, it will automatically decode quoted-printable messages (that use the ISO 8859-1 character set) while delivering messages to your VMS MAIL mailbox, although you can disable this feature. -Matt -- Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA madison@madgoat.com http://www.madgoat.com ================================================================================ Archive-Date: Tue, 21 Apr 1998 10:31:23 -0700 From: "Patrick Cox" To: mx-list@madgoat.com Date: Tue, 21 Apr 1998 14:28:40 AST Subject: mx-digest and user-requested digest feature Reply-To: MX-List@MadGoat.com Message-ID: <264DF9A2DF0@es.nsac.ns.ca> I need a little clarification about how to set up digests. I've looked at the mx-digest addon from the [.contrib] directory. It appears to set the entire list to digest mode, so all subscribers get a digest. And from what I've been told/seen when a subscriber to test-l@ac.nsac.ns.ca requests to operate in digest mode they have to send messages to test-l-digest@ac.nsac.ns.ca, to have them included in the digest. Does mixing these features allow a subscriber to receive a daily digest, while others can still receive messages one at a time throughout the day? TIA! Patrick M. Cox Information Technology Section (Truro) Resources Corporate Services Unit (DAM,DNR,Fish,Env) (902)893-6233 ================================================================================ Archive-Date: Tue, 21 Apr 1998 11:47:26 -0700 Sender: goathunter@MadGoat.com Date: Tue, 21 Apr 1998 13:47:14 -0500 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: PCOX@ES.NSAC.NS.CA Message-ID: <009C50B4.748232F3.5@goat.process.com> Subject: RE: mx-digest and user-requested digest feature "Patrick Cox" writes: > >I need a little clarification about how to set up digests. I've looked >at the mx-digest addon from the [.contrib] directory. It appears to >set the entire list to digest mode, so all subscribers get a digest. In MX V4.2, yes, that's true. You need to set up two separate lists, like MX-List and MX-List-Digest. MX V5.0 has a "digest" flag that can be set on a per-subscriber basis, allowing you to have only one list. >And from what I've been told/seen when a subscriber to >test-l@ac.nsac.ns.ca requests to operate in digest mode they have to >send messages to test-l-digest@ac.nsac.ns.ca, to have them included in >the digest. > No, they have to signoff the TEST-L and subscribe to TEST-L-DIGEST. Posts continue to go to TEST-L (unless the list is protected so that only subscribers can post). I've forgotten the details of that; holler if you need more info. >Does mixing these features allow a subscriber to receive a daily >digest, while others can still receive messages one at a time >throughout the day? > Yes, by maintaining two separate lists under V4.2. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Tue, 21 Apr 1998 13:17:24 -0700 Message-ID: <3.0.32.19980421151421.00b56430@moses.acu.edu> Date: Tue, 21 Apr 1998 15:14:22 -0500 To: MX-List@MadGoat.com From: Tom Dolan Reply-To: MX-List@MadGoat.com Subject: RE: mx-digest and user-requested digest feature MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" >>I need a little clarification about how to set up digests. I've looked >>at the mx-digest addon from the [.contrib] directory. It appears to >>set the entire list to digest mode, so all subscribers get a digest. >In MX V4.2, yes, that's true. You need to set up two separate lists, >like MX-List and MX-List-Digest. >MX V5.0 has a "digest" flag that can be set on a per-subscriber basis, >allowing you to have only one list. Nope. I have MX 4.2 configured as a single list with the digest flag per-subscriber - it's 4.1 and below that require two seperate lists. Here's my abriveated instructions on setting up a digest under MX 4.2 with the digest addon from the [.contrib] directory: 1. Install digest components A. Setup path and rewrite rules per instructions B. Modify mx_exe:SITE_DELIVER.COM per instructions C. Put mx_digest.exe and mx_deliver_digests.com in mx_exe per instruction and edit per instructions D. Put mx_digest_submit.com in mx_site_dir and edit per instructions E. Submit mx_digest_submit.com to a batch que to run on a regular basis (Check the docs for specific instructions.) 2. Do this whenever you want to add digest capabilities to a list A. Run MCP and MCP>modify list listname digest B. $set default mx_site_dir C. create listname-digest.head D. create listname-digest.info E. subscribe listname@digest.site to listname (where listname is the name of the list.) This system captures messages sent to listname@digest.site and compiles them into a single file. When the file gets big or old enough it sends the file contents to subscribers with the digest flag along with a header listing subject lines for each message, the digest volume number and the date. Tom Dolan Dolan@Bible.acu.edu 242 Bible Building Systems Manager ACU Box 29454 College of Biblical Studies Abilene, TX 79699 Abilene Christian University 915.674.3706 http://dolan.acu.edu ================================================================================ Archive-Date: Tue, 21 Apr 1998 13:20:54 -0700 Sender: goathunter@MadGoat.com Date: Tue, 21 Apr 1998 15:20:41 -0500 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009C50C1.825B40CE.15@goat.process.com> Subject: RE: mx-digest and user-requested digest feature Tom Dolan writes: > >Nope. I have MX 4.2 configured as a single list with the digest >flag per-subscriber - it's 4.1 and below that require two seperate >lists. > Ooops. I'm getting old, I guess. I worked on MX V5.0 for so long that I can no longer keep straight what feature was in what version.... >Here's my abriveated instructions on setting up a digest under MX >4.2 with the digest addon from the [.contrib] directory: > >1. Install digest components > A. Setup path and rewrite rules per instructions > B. Modify mx_exe:SITE_DELIVER.COM per instructions > C. Put mx_digest.exe and mx_deliver_digests.com in mx_exe per >instruction and edit per instructions > D. Put mx_digest_submit.com in mx_site_dir and edit per instructions > E. Submit mx_digest_submit.com to a batch que to run on a regular >basis > (Check the docs for specific instructions.) > >2. Do this whenever you want to add digest capabilities to a list > A. Run MCP and MCP>modify list listname digest > B. $set default mx_site_dir > C. create listname-digest.head > D. create listname-digest.info > E. subscribe listname@digest.site to listname > (where listname is the name of the list.) > >This system captures messages sent to listname@digest.site and >compiles them into a single file. When the file gets big or old >enough it sends the file contents to subscribers with the digest >flag along with a header listing subject lines for each message, >the digest volume number and the date. > What he said. And note that only messages from the list owner, or an MX SYSTEM_USER, can be sent out as a digest to the digest subscribers. If a message is sent to -Digest by someone other than a list owner or SYSTEM_USER, it is treated as a regular post. Thanks, Tom. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Tue, 21 Apr 1998 22:06:38 -0700 Date: Tue, 21 Apr 1998 14:48:06 GMT From: Chris.Sharman@ccagroup.co.uk Reply-To: MX-List@MadGoat.com To: MX-List@wkuvx1.wku.edu CC: Chris.Sharman@ccagroup.co.uk Message-ID: <009C50BC.F5289B47.2@ccagroup.co.uk> Subject: Name_Conversion (MX 4.2) I'm using Name_Conversion to convert outgoing usernames to a standard format (Forename.Surname). Unfortunately, as well as converting local username JOHN, say, it also applies the same conversion to JOHN in John@Somewhere.Else.com I don't really need to convert incoming names, since I've got all the aliases set up in VMS mail forwarded to the appropriate users. Can anyone tell me how to check the rest of the address please, and restrict my conversions to John@, or what I ought to be doing to get this functionality ? Thanks ______________________________________________________________________ Chris Sharman Chris.Sharman@CCAgroup.co.uk CCA Stationery Ltd, Eastway, Fulwood, Preston, Lancashire, PR2 9WS. ================================================================================ Archive-Date: Tue, 21 Apr 1998 23:12:50 -0700 Message-ID: <3.0.3.32.19980421231237.00eb2160@dirmarketing.com> Date: Tue, 21 Apr 1998 23:12:37 -0700 To: MX-List@MadGoat.com From: Stephen Garrett Reply-To: MX-List@MadGoat.com Subject: Mailing list "from" domain name (MX 4.2) In-Reply-To: <009C50BC.F5289B47.2@ccagroup.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hi all, anyone run into this situation? Environment: Multihomed workstation (eg; primary domain is abc.com) w/ Multinet Stack. MX 4.2 OpenVMS 6.1 (could use 6.2 system as well) This machine also hosts for other domains (eg for virtual web servers). Issue: I would like to be able to set the "from" domain so that different mailing lists appear to come from different domains. Right now all lists are "from" abc.com, and I can't see a way to have MX MLF provide a name for the "from" domain. All mail to the "virtual" domain is currently handled via a "local Path rule" and that works fine. It's the outgoing that is an issue. Does 5.0 help this issue? Ideas? TIA, Steve -- Stephen Garrett GPS steve@gpsnet.com (360) 896-2714 ICQ# 10776767 ================================================================================ Archive-Date: Tue, 21 Apr 1998 23:28:01 -0700 Sender: madison@MadGoat.Com Date: Tue, 21 Apr 1998 23:27:56 -0700 From: Matt Madison Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: steve@gpsnet.com Message-ID: <009C5105.93AEA4A3.4@MadGoat.Com> Subject: RE: Mailing list "from" domain name (MX 4.2) [...] >Issue: > >I would like to be able to set the "from" domain so that different mailing >lists appear to come from different domains. You might be able to use ADDRESS_REWRITER (in MX_ROOT:[EXAMPLES]) to do this under V4.2. >Right now all lists are "from" abc.com, and I can't see a way to have >MX MLF provide a name for the "from" domain. All mail to the "virtual" >domain is currently handled via a "local Path rule" and that works fine. >It's the outgoing that is an issue. > >Does 5.0 help this issue? V5.0 does provide for setting the domain name on a per-list basis (the /HOSTNAME qualifier on DEFINE LIST). -Matt -- Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA madison@madgoat.com http://www.madgoat.com ================================================================================ Archive-Date: Wed, 22 Apr 1998 07:44:55 -0700 Message-ID: <3.0.3.32.19980422074440.00eb4c74@dirmarketing.com> Date: Wed, 22 Apr 1998 07:44:40 -0700 To: MX-List@MadGoat.com From: Stephen Garrett Reply-To: MX-List@MadGoat.com Subject: RE: Mailing list "from" domain name (MX 4.2) In-Reply-To: <009C5105.93AEA4A3.4@MadGoat.Com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Well, now I have an excuse to upgrade to 5.0 and pay for the great product! Thanks, Steve At 11:27 PM 4/21/98 -0700, you wrote: >[...] >>Issue: >> >>I would like to be able to set the "from" domain so that different mailing >>lists appear to come from different domains. > >You might be able to use ADDRESS_REWRITER (in MX_ROOT:[EXAMPLES]) to do >this under V4.2. > >>Right now all lists are "from" abc.com, and I can't see a way to have >>MX MLF provide a name for the "from" domain. All mail to the "virtual" >>domain is currently handled via a "local Path rule" and that works fine. >>It's the outgoing that is an issue. >> >>Does 5.0 help this issue? > >V5.0 does provide for setting the domain name on a per-list basis >(the /HOSTNAME qualifier on DEFINE LIST). > >-Matt > >-- >Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA >madison@madgoat.com http://www.madgoat.com > -- Stephen Garrett GPS steve@gpsnet.com (360) 896-2714 ICQ# 10776767 ================================================================================ Archive-Date: Wed, 22 Apr 1998 23:19:18 -0700 Date: Thu, 23 Apr 1998 16:14:29 EST-10EST From: Daiajo Tibdixious MACS <"svs::svist070"@stvincents.COM.AU> Reply-To: MX-List@MadGoat.com To: MX-List@LISTS.WKU.EDU Message-ID: <009C525B.5B6660C0.23@stvincents.com.au> Subject: top & bottom mime headers We are running MX V4.2 on VAX/VMS V6.2 We want to put the mime headers MIME-Version and Content-Type at the top, but not all the other headers. Unfortunately, these both fall in the OTHER category. I'm wondering if V5 provides these as separate keywords to SET LOCAL/HEADERS? If not, are there any other possibilities besides sending all LOCAL stuff thru SITE? -- dTibdixious@stvincents.com.au Server Technical Support ================================================================================ Archive-Date: Thu, 23 Apr 1998 00:51:11 -0700 Date: Thu, 23 Apr 1998 09:46:13 +0100 From: Sipos Tibor Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009C5225.1DAE6BA0.77@tigris.klte.hu> Subject: Base64 I think it's a very simple problem, but I'm can't make it... We have some user using VMS Mail. Sometimes they get E-Mails with attachments (coded in Base64-format). Now MX don't encode it automatically, so they have to extract the message, edit and delete some lines, decode and so on... With Pegasus Mail, some user can't see the attachment coded in Base64. How can I make MX to decode it automatically, or what can I do? (Make the users using other mailing programs? They can't, they can't learn any new...) Sipi ------------------------------------------------------------------------------ Address : 4032 Debrecen, Doberdo 13. IV/14., Hungary Phone : (52) 310-357 E-Mail : siposti@dragon.klte.hu siposti@tigris.klte.hu siposti@kltesrv.klte.hu ================================================================================ Archive-Date: Thu, 23 Apr 1998 05:25:36 -0700 Sender: goathunter@MadGoat.com Date: Thu, 23 Apr 1998 07:25:27 -0500 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009C5211.73998BBC.5@ALPHA.WKU.EDU> Subject: RE: top & bottom mime headers Daiajo Tibdixious MACS <"svs::svist070"@stvincents.COM.AU> writes: > >We want to put the mime headers > MIME-Version and > Content-Type >at the top, but not all the other headers. > >Unfortunately, these both fall in the OTHER category. > >I'm wondering if V5 provides these as separate keywords to SET LOCAL/HEADERS? > No, but we should probably do that for V5.1. When I first added those headers, they were "OTHER". ;-) >If not, are there any other possibilities besides sending all LOCAL stuff thru >SITE? Not that I can think of.... Hunter ------ Hunter Goatley, Process Software, http://www.process.com http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Thu, 23 Apr 1998 05:26:39 -0700 Sender: goathunter@MadGoat.com Date: Thu, 23 Apr 1998 07:26:30 -0500 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009C5211.9961AE88.7@ALPHA.WKU.EDU> Subject: RE: Base64 Sipos Tibor writes: > >We have some user using VMS Mail. Sometimes they get E-Mails with >attachments (coded in Base64-format). Now MX don't encode it >automatically, so they have to extract the message, edit and delete some >lines, decode and so on... >With Pegasus Mail, some user can't see the attachment coded in Base64. > >How can I make MX to decode it automatically, or what can I do? (Make the >users using other mailing programs? They can't, they can't learn any new...) > You could run all incoming mail through the SITE interface, looking for such messages and decoding them. But that's not going to be trivial.... Hunter ------ Hunter Goatley, Process Software, http://www.process.com http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Thu, 23 Apr 1998 05:57:01 -0700 Message-ID: <034801bd6eb6$e6a33200$d6001c7e@gr-355538.si.com> From: "Brian Tillman" Reply-To: MX-List@MadGoat.com To: Subject: Re: top & bottom mime headers Date: Thu, 23 Apr 1998 08:54:06 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit dTibdixious@stvincents.com.au writes: >We want to put the mime headers >MIME-Version and >Content-Type >at the top, but not all the other headers. May I ask why? If it is so that you can use a POP client to read VMS Mail (by running a POP server on the VMS system running MX), you don't need to move the headers. You can leave them at the bottom if you're running V2.0-4 of the IUPOP3 server. This is what I do and it works perfectly. I see all attachments as their proper content-type. Brian Tillman Internet: tillman_brian at si.com Smiths Industries, Inc. tillman at swdev.si.com 4141 Eastern Ave., MS239 Addresses modified to prevent Grand Rapids, MI 49518-8727 SPAM. Replace "at" with "@" This opinion doesn't represent that of my company ================================================================================ Archive-Date: Thu, 23 Apr 1998 17:31:00 -0700 Date: Thu, 23 Apr 1998 17:30:53 -0700 From: Dan Wing Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <980423173053.203ec873@Cisco.COM> Subject: RE: Base64 >How can I make MX to decode it automatically, or what can I do? (Make the >users using other mailing programs? They can't, they can't learn any new...) Have the user quit using VMSmail, and have them use a POP client (Eudora, Netscape, Microsoft Outlook Express, etc.). -Dan Wing ================================================================================ Archive-Date: Fri, 24 Apr 1998 06:39:15 -0700 From: welchb@woods.uml.edu (Brendan Welch, W1LPG) Reply-To: MX-List@MadGoat.com Subject: Answer to long-standing bug Date: 24 Apr 98 09:24:46 -0500 Message-ID: <1998Apr24.092446.1@aspen> To: MX-List@WKUVX1.WKU.EDU For years I have felt that we have been the only MX user in the world to suffer sporadic, massive failures. E.g., just the other day, on day 3 of what for me was a 4-day weekend, we lost 3000 messages. What typically would show up in QUE SHOW/FULL was entries like this: Recipient #1: JONES, Route=woods.uml.edu Error count = 24 Last error: %MAIL-E-OPENOUT, error opening !AS as output yet we ARE woods.uml.edu ( The cure for such failures has been to restart MX on all nodes, and to do a massive QUE READY . ) Yesterday an operator was deleting expired accounts. Her procedure is to first delete (using the popular DELTREE) the files of these users, then delete the users' directories themselves, remove them from diskquota, and finally remove them from MAILUAF. The deleting of user files took many hours, and several persons apparently are still on mailing lists, with mail still coming in. As a very preliminary and tentative finding, it would seem possible that the cause of these crashes could be that a user who receives mail still exists in MAILUAF, but has no home directory (and certainly no mail.mai). This finding would be consistent with the fact that a good installation would have absolutely no users in this category; i.e., proper termination of an account would include all the steps above, done rapidly (and maybe in a different order). And it would be consistent with the fact that in a (school) installation like ours, with much account turnover, there do exist a few such rare cases, and that they are the trigger of those often-on-a-weekend catastrophes, when a long-removed user receives some spam generated from an ancient file. (I still see stuff being received here stemming from postings made many years ago, in a now-defunct form.) So my note here points out 2 things: 1) It never hurts to have a clean installation. It is nice to have each user well-known, without any privileges (s)he should not have, without extra home directories, with a correct diskquota, and without any mail forwarding which creates a loop. Much of this pertains to well-thought-out procedures, good communication among staff, and timely and consistent execution thereof [and to well-trained users!]. 2) A lack of one of those particulars mentioned above MAY be the cause of catastrophe in MX. -- Brendan Welch, system analyst, UMass-Lowell, W1LPG, welchb@woods.uml.edu ================================================================================ Archive-Date: Fri, 24 Apr 1998 07:17:32 -0700 Date: Fri, 24 Apr 1998 10:15:47 -0400 From: "Rand P. Hall" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: welchb@woods.uml.edu Subject: Re: Answer to long-standing bug In-Reply-To: <1998Apr24.092446.1@aspen> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On 24 Apr 1998 welchb@woods.uml.edu wrote: > For years I have felt that we have been the only MX user in the world > to suffer sporadic, massive failures. E.g., just the other day, on > day 3 of what for me was a 4-day weekend, we lost 3000 messages. > > What typically would show up in QUE SHOW/FULL was entries like this: > Recipient #1: JONES, Route=woods.uml.edu > Error count = 24 > Last error: %MAIL-E-OPENOUT, error opening !AS as output Every instance I seen like this has been caused by a full disk. Sensible that it happens on a weekend, too, when you're not on top of it. Cheers, rand -- Rand P. Hall, Manager of Systems and Networking Merrimack College, North Andover, MA, USA rand@merrimack.edu ================================================================================ Archive-Date: Fri, 24 Apr 1998 07:29:52 -0700 Message-ID: <019801bd6f8d$4ee2cc00$d6001c7e@gr-355538.si.com> From: "Brian Tillman" Reply-To: MX-List@MadGoat.com To: Subject: Re: Answer to long-standing bug Date: Fri, 24 Apr 1998 10:28:53 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit On 24 Apr 1998 welchb@woods.uml.edu wrote: > For years I have felt that we have been the only MX user in the world > to suffer sporadic, massive failures. E.g., just the other day, on > day 3 of what for me was a 4-day weekend, we lost 3000 messages. > > What typically would show up in QUE SHOW/FULL was entries like this: > Recipient #1: JONES, Route=woods.uml.edu > Error count = 24 > Last error: %MAIL-E-OPENOUT, error opening !AS as output This error most assurredly can be caused by an address in the VMS Mail Profile for which there is no mail directory. Here's an example: $ muaf MAILUAF> sho test TEST /PERSONAL_NAME="" /FORWARDING="" /SUB_DIRECTORY="" ! (FULL="SCRATCH_DISK:[TEST]") /EDITOR="" /QUEUE="" /FORM="" /NEW_MESSAGES=0 /NOCC_PROMPT /COPY=(NOFORWARD,NOREPLY,NOSEND /AUTO_PURGE /MAILPLUS="" /TRANSPORT="" /USER=("","","") MAILUAF> Exit $ dir scratch_disk:[000000]test.dir %DIRECT-W-NOFILES, no files found $ mail/sub="Hello" nl: test %MAIL-E-SENDERR, error sending to user TEST -MAIL-E-OPENOUT, error opening SCRATCH_DISK:[TEST]MAIL.MAI as output -SYSTEM-F-IVDEVNAM, invalid device name It would seem, then, that your answer would be to remove the UAF and mail profile entries first, and then delete the files. Brian Tillman Internet: tillman_brian at si.com Smiths Industries, Inc. tillman at swdev.si.com 4141 Eastern Ave., MS239 Addresses modified to prevent Grand Rapids, MI 49518-8727 SPAM. Replace "at" with "@" This opinion doesn't represent that of my company ================================================================================ Archive-Date: Tue, 28 Apr 1998 07:09:08 -0700 From: Hunter Goatley Reply-To: MX-List@MadGoat.com Subject: Re: List reply-to and return address Date: Tue, 28 Apr 1998 08:43:12 -0500 Message-ID: <354596A0.64ABB878@MadGoat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: curtis_g@subway.com To: MX-List@WKUVX1.WKU.EDU George Curtis wrote: > > We are using MX V4.1 VAX. Our situation is that we have a list which needs > to have replies go to two email addresses (one to check replies and one for > a program to parse "unsubscribes"). We haven't been able to set the > "return_address" to write more than one email address, and we don't know how > else to handle our problem without setting up an additional POP3 server with > "NO PURGE" or actually forward messages to more than one account. > Is there any way around this, maybe with MX5.0? MX V5.0 lets you define an ALIAS in MCP that can equate to more than one address. Otherwise, you could pass your message through the SITE interface and do whatever you want with it, including forwarding it back to the actual list. > We've also found that return-address fields are overwritten if the sender to > the mailing list uses a reply-to in his email software. Any way around > that? That problem is fixed in MX V5.0. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Thu, 30 Apr 1998 08:27:40 -0700 Message-ID: <2.2.32.19980430152735.008e3ca0@ntpop.usnews.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 30 Apr 1998 11:27:35 -0400 To: MX-List@MadGoat.com From: Betsy Ramsey Reply-To: MX-List@MadGoat.com Subject: MX 4.2 AXP: upgrading DEC C (and later, UCX) I'm currently running OpenVMS Alpha 6.1, UCX 3.2 eco 8, DEC C 4.0 and MX 4.2. I want to upgrade DEC C to the latest version, 5.7. Will MX 4.2 be able to run as-is? On a related subject, if I upgrade UCX to either 4.1 with the latest eco, or to the new 4.2, will MX 4.2 be able to run as-is? --Betsy Ramsey ================================================================================ Archive-Date: Thu, 30 Apr 1998 08:44:54 -0700 Sender: goathunter@MadGoat.com Date: Thu, 30 Apr 1998 10:44:43 -0500 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009C57AD.72E5DBD9.7@goat.process.com> Subject: RE: MX 4.2 AXP: upgrading DEC C (and later, UCX) Betsy Ramsey writes: > >I'm currently running OpenVMS Alpha 6.1, UCX 3.2 eco 8, DEC C 4.0 and MX 4.2. > >I want to upgrade DEC C to the latest version, 5.7. Will MX 4.2 be able to >run as-is? > Yes. Only a couple of modules in MX are written in C, and neither of them depends on any version of DEC C. >On a related subject, if I upgrade UCX to either 4.1 with the latest eco, or >to the new 4.2, will MX 4.2 be able to run as-is? > Yes. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Thu, 30 Apr 1998 09:16:38 -0700 Message-ID: <2.2.32.19980430161626.00911a64@ntpop.usnews.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 30 Apr 1998 12:16:26 -0400 To: MX-List@MadGoat.com From: Betsy Ramsey Reply-To: MX-List@MadGoat.com Subject: RE: MX 4.2 AXP: upgrading DEC C (and later, UCX) At 11:44 AM 4/30/98 -0400, Hunter Goatley wrote: >>I want to upgrade DEC C to the latest version, 5.7. Will MX 4.2 be able to >>run as-is? >Yes. Only a couple of modules in MX are written in C, and neither of >them depends on any version of DEC C. >>On a related subject, if I upgrade UCX to either 4.1 with the latest eco, or >>to the new 4.2, will MX 4.2 be able to run as-is? >Yes. Thanks for the info, Hunter. ================================================================================ Archive-Date: Thu, 30 Apr 1998 12:21:21 -0700 Message-ID: <3.0.32.19980430141939.00b297a0@moses.acu.edu> Date: Thu, 30 Apr 1998 14:19:40 -0500 To: MX-List@MadGoat.com From: Tom Dolan Reply-To: MX-List@MadGoat.com Subject: interim deployment MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hunter, I want to deploy some features in MX - I have MX 4.2 now but will purchase 5.0 later this year with the new budget year. Please let me know which of these features are included in MX5.0 - the others I will go ahead and work on with the current SITE interface: 1. Mail list header (Include this file on top of each list message) 2. Mail list footer (Include this file on bottom of each list message) 3. Moderated list 4. List archive search (like at http://www2.wku.edu:81/scripts/mxarchive/as_init.com?MX-List) 5. Autoresponder (Return this file to email sent to this address) Thanks! Tom Dolan Dolan@Bible.acu.edu 242 Bible Building Systems Manager ACU Box 29454 College of Biblical Studies Abilene, TX 79699 Abilene Christian University 915.674.3706 http://dolan.acu.edu ================================================================================ Archive-Date: Thu, 30 Apr 1998 12:24:36 -0700 Sender: goathunter@MadGoat.com Date: Thu, 30 Apr 1998 14:24:17 -0500 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009C57CC.1EFF0E18.4@goat.process.com> Subject: RE: interim deployment Tom Dolan writes: > >Please let me know which of these features are included in MX5.0 - >the others I will go ahead and work on with the current SITE >interface: > >1. Mail list header (Include this file on top of each list message) MX V5.0 has support for adding real headers of your choice, but you can't specify a file to include. You can use that feature to add headers like "Organization:", etc. MX V5.0 also has support for the List-* headers, as you can see in the headers of this message. >2. Mail list footer (Include this file on bottom of each list message) >3. Moderated list >4. List archive search (like at >http://www2.wku.edu:81/scripts/mxarchive/as_init.com?MX-List) >5. Autoresponder (Return this file to email sent to this address) > None of these, although getting #4 out there is something I've been meaning to do. I'll try to do that real soon. Instructions for using SITE to do a moderated list have been posted here several times. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Thu, 30 Apr 1998 12:39:03 -0700 Message-ID: <3.0.32.19980430143734.00aeeb60@moses.acu.edu> Date: Thu, 30 Apr 1998 14:37:36 -0500 To: MX-List@MadGoat.com From: Tom Dolan Reply-To: MX-List@MadGoat.com Subject: RE: interim deployment MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" >>1. Mail list header (Include this file on top of each list message) >MX V5.0 has support for adding real headers of your choice, but you >can't specify a file to include. You can use that feature to add >headers like "Organization:", etc. MX V5.0 also has support for the >List-* headers, as you can see in the headers of this message. I am thinking of text to add at the top of each message body - some list owners like to put the one line "To unsubcribe do this" message at the top instead of the bottom of each list message - I'll make SITE do it. >Instructions for using SITE to do a moderated list have been posted >here several times. Right - those are the instructions I'll use to make make the list message text header, footer, autoresponder and moderation work - very good example I've already used for some other customized message manipulation. I think I can handle this now - couldn't have done it a year ago (didn't have enough programming knowledge and want to!) Thanks for the prompt reply! Tom Dolan Dolan@Bible.acu.edu 242 Bible Building Systems Manager ACU Box 29454 College of Biblical Studies Abilene, TX 79699 Abilene Christian University 915.674.3706 http://dolan.acu.edu ================================================================================ Archive-Date: Thu, 30 Apr 1998 13:04:14 -0700 Sender: goathunter@MadGoat.com Date: Thu, 30 Apr 1998 15:04:02 -0500 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009C57D1.AC90D59C.13@ALPHA.WKU.EDU> Subject: RE: interim deployment Tom Dolan writes: > >I am thinking of text to add at the top of each message body - some >list owners like to put the one line "To unsubcribe do this" >message at the top instead of the bottom of each list message - >I'll make SITE do it. > That's what the List-* headers are supposed to do: List-Subscribe: List-Unsubscribe: List-Help: Of course, since things like Netscape don't show you all headers, by default, their use is questionable. (Nice idea, but not enough support for them yet.) >Right - those are the instructions I'll use to make make the list >message text header, footer, autoresponder and moderation work - >very good example I've already used for some other customized >message manipulation. I think I can handle this now - couldn't have >done it a year ago (didn't have enough programming knowledge and >want to!) > 8-) Yeah, the same basic idea can be stretched a long way! >Thanks for the prompt reply! > No problem! Hunter ------ Hunter Goatley, Process Software, http://www.process.com http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Thu, 30 Apr 1998 13:56:05 -0700 Message-ID: <3.0.3.32.19980430135445.0070dbc0@dirmarketing.com> Date: Thu, 30 Apr 1998 13:54:45 -0700 To: MX-List@MadGoat.com From: Stephen Garrett Reply-To: MX-List@MadGoat.com Subject: RE: interim deployment In-Reply-To: <3.0.32.19980430143734.00aeeb60@moses.acu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Any chance of you posting the site mods to allow for the headers you are describing below??? TIA, Steve At 02:37 PM 4/30/98 -0500, you wrote: >>>1. Mail list header (Include this file on top of each list message) >>MX V5.0 has support for adding real headers of your choice, but you >>can't specify a file to include. You can use that feature to add >>headers like "Organization:", etc. MX V5.0 also has support for the >>List-* headers, as you can see in the headers of this message. > >I am thinking of text to add at the top of each message body - some >list owners like to put the one line "To unsubcribe do this" >message at the top instead of the bottom of each list message - >I'll make SITE do it. > >>Instructions for using SITE to do a moderated list have been posted >>here several times. > >Right - those are the instructions I'll use to make make the list >message text header, footer, autoresponder and moderation work - >very good example I've already used for some other customized >message manipulation. I think I can handle this now - couldn't have >done it a year ago (didn't have enough programming knowledge and >want to!) > >Thanks for the prompt reply! > > >Tom Dolan Dolan@Bible.acu.edu 242 Bible Building >Systems Manager ACU Box 29454 >College of Biblical Studies Abilene, TX 79699 >Abilene Christian University 915.674.3706 >http://dolan.acu.edu > -- Stephen Garrett GPS steve@gpsnet.com (360) 896-2714 ICQ# 10776767 ================================================================================ Archive-Date: Thu, 30 Apr 1998 14:24:12 -0700 Message-ID: <3.0.32.19980430162237.00aff470@moses.acu.edu> Date: Thu, 30 Apr 1998 16:22:38 -0500 To: MX-List@MadGoat.com From: Tom Dolan Reply-To: MX-List@MadGoat.com Subject: RE: interim deployment MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" >Any chance of you posting the site mods to allow for the headers you >are describing below??? Yes - I'll post the individual SITE modules with instructions when I finish. I have instructions for a SITE module called ECHO up already at http://dolan.acu.edu/howto/how_to_make_echo.htm - watch the web site for further instructions as developed. There are copies of the MX-LIST archive messages for moderated list and autoresponder in that web site also.... Tom Dolan >>I am thinking of text to add at the top of each message body - some >>list owners like to put the one line "To unsubcribe do this" >>message at the top instead of the bottom of each list message - >>I'll make SITE do it. Tom Dolan Dolan@Bible.acu.edu 242 Bible Building Systems Manager ACU Box 29454 College of Biblical Studies Abilene, TX 79699 Abilene Christian University 915.674.3706 http://dolan.acu.edu ================================================================================ Archive-Date: Thu, 30 Apr 1998 14:32:24 -0700 Message-ID: <3.0.3.32.19980430143202.007110f8@dirmarketing.com> Date: Thu, 30 Apr 1998 14:32:02 -0700 To: MX-List@MadGoat.com From: Stephen Garrett Reply-To: MX-List@MadGoat.com Subject: RE: interim deployment In-Reply-To: <3.0.32.19980430162237.00aff470@moses.acu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Thanks! At 04:22 PM 4/30/98 -0500, you wrote: >>Any chance of you posting the site mods to allow for the headers you >>are describing below??? > >Yes - I'll post the individual SITE modules with instructions when >I finish. I have instructions for a SITE module called ECHO up >already at http://dolan.acu.edu/howto/how_to_make_echo.htm - watch >the web site for further instructions as developed. There are >copies of the MX-LIST archive messages for moderated list and >autoresponder in that web site also.... > >Tom Dolan > >>>I am thinking of text to add at the top of each message body - some >>>list owners like to put the one line "To unsubcribe do this" >>>message at the top instead of the bottom of each list message - >>>I'll make SITE do it. > > >Tom Dolan Dolan@Bible.acu.edu 242 Bible Building >Systems Manager ACU Box 29454 >College of Biblical Studies Abilene, TX 79699 >Abilene Christian University 915.674.3706 >http://dolan.acu.edu > -- Stephen Garrett GPS steve@gpsnet.com (360) 896-2714 ICQ# 10776767