Archive-Date: Mon, 1 Dec 1997 12:20:01 -0600 From: Hunter Goatley Reply-To: MX-List@MadGoat.com Subject: Re: MCP QUEUE SHOW/ALL returns 'total matching entries: 0 Date: Mon, 01 Dec 1997 11:52:24 -0600 Message-ID: <3482A4F8.7B5EF9B3@MadGoat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: SYSTEM@UHAVAX.HARTFORD.EDU To: MX-List@WKUVX1.WKU.EDU SYSTEM MANAGER wrote: > > Hello - > > I've recently move my queues directory to another disk and and having sporadic > problems, including: > > MCP> que stat > %MCP-I-QSTATUS, total entries: 2129/10013 (21%) Highest entry used: 2129 (21%) > MCP> que show/all > %MCP-I-QENTRIES, total matching entries: 0 > MCP> que show 1 > > Entry# Status Size Source Agent Entry# Status Size > ------ ------ ------- ------ ------- ------ ------ ------- > 1 FINISH 289 SMTP > > %MCP-I-QENTRIES, total matching entries: 1 > > It'll show a single specified entry, but not /ALL! Anybody seen this? > I have changed the MX_FLQ_DIR logical to point to the new queue location, > otherwise, things appear to be working except that MX FLQ Manager seems to > stop quto-purging the queue. > Sounds like you've got a corrupted queue. You should create a new queue file. BTW, all known queue corruption problems have been fixed in the upcoming MX V5.0. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ MultiNet & TCPware: The Best TCP/IP for OpenVMS http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Mon, 1 Dec 1997 12:32:45 -0600 Date: Mon, 01 Dec 1997 13:31:30 EST From: Robert Byer Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BE1E5.E5464620.17@mail.all-net.net> Subject: Re: MCP QUEUE SHOW/ALL returns 'total matching entries: 0 -----BEGIN PGP SIGNED MESSAGE----- > >BTW, all known queue corruption problems have been fixed >in the upcoming MX V5.0. > By the way, any new time frame for the release of this beast? I'm getting the sh*t knocked out of me with e-mail spammers relaying through our system and it's starting to get on my nerves. I don't want to block out an entire site at the router as alot of our users send e-mail to those sites (msn.com, aol.com, etc...) and the damm spammers keep changing fake e-mail addresses on a "per-spamm" basis. +------------------------+--------------------------------------------+ | 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 iQEVAwUBNIK7naVSqzlBVJbBAQECjwgAtuN94acnJGA5rZmJhJoT7D4GF04spRyI SiXRmcci9IFBa6kv87qraX/Ry/csx9pdEmwB8rBexKtyqG5W7+Zw32eLtjkJgFt3 X4+O1HOrI7c5x4pbDpK+7LBAh7gsLVEq6Dr01OWPpcPimqPxWwh2EHpSgvpwn+zR 5V8X5j9p5N0BWfTQWqjFPMOosvSseVsl0n3szEvw7fcfdejJUG3oGmNsnYG8Q/71 jg+B+Fva3GJMR1NqyI2pRWLDEnSXLAB4KF9T0Mx1yCOY7WnpxXsuV1ls3zKeolxa asIUFhN7xqVKslbNz0Ei/aBSox111tHAzzJnt3ITvcolKUC/XWVpAQ== =neAz -----END PGP SIGNATURE----- ================================================================================ Archive-Date: Mon, 1 Dec 1997 12:36:09 -0600 Date: Mon, 1 Dec 1997 10:36:02 -0800 From: Matt Madison Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <971201103602.20244d88@Cisco.COM> Subject: Re: MCP QUEUE SHOW/ALL returns 'total matching entries: 0 >>BTW, all known queue corruption problems have been fixed >>in the upcoming MX V5.0. >> > >By the way, any new time frame for the release of this beast? We're shooting for the middle of December. We're in what's hopefully the once-and-for-all last beta-test phase. I just want to make sure this new stuff is as bullet-proof as possible before we go to release. >I'm getting the sh*t knocked out of me with e-mail spammers relaying >through our system and it's starting to get on my nerves. I can understand that. Hang in there! -Matt ================================================================================ Archive-Date: Mon, 1 Dec 1997 12:51:13 -0600 Date: Mon, 01 Dec 1997 19:50:39 MET-1MET DST From: "Michael Lemke, Sternwarte Bamberg, Phone: +49-951-9522216" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: ai26@sternwarte.uni-erlangen.de Message-ID: <009BE21A.DCCAF673.19@sternwarte.uni-erlangen.de> Subject: Re: MCP QUEUE SHOW/ALL returns 'total matching entries: 0 In a message of Mon, 01 Dec 1997 13:31:30 EST Received on Mon, 01 Dec 1997 19:46:40 MET-1MET DST Robert Byer wrote to: Message Exchange Discussion List > >> >>BTW, all known queue corruption problems have been fixed >>in the upcoming MX V5.0. >> > >By the way, any new time frame for the release of this beast? > >I'm getting the sh*t knocked out of me with e-mail spammers relaying >through our system and it's starting to get on my nerves. So do we. It is getting worse every day. > >I don't want to block out an entire site at the router as alot of our users >send e-mail to those sites (msn.com, aol.com, etc...) and the damm >spammers keep changing fake e-mail addresses on a "per-spamm" basis. > Doesn't seem to be that bad yet. But I've been contemplating to re-activate UCX SMTP as it has an option to not relay mail. So far I am blocking access at the UCX level but UCX only takes up to 16 addresses that can be blocked that way. So how much longer do we have to wait for MX V5.0? Thanks, Michael -- Michael Lemke Sternwarte Bamberg, University of Erlangen-Nürnberg, Germany (lemke@sternwarte.uni-erlangen.de or michael@astro.as.utexas.edu) ================================================================================ Archive-Date: Mon, 1 Dec 1997 12:51:48 -0600 Date: Mon, 01 Dec 1997 12:51:27 CST From: Ravi Kochhar Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BE1E0.4D7CCC60.41@neurophys.wisc.edu> Subject: User-settable return address ? Hi, Is it possible for users to have a return address that is different from the default defined by MX ? We would like two groups to use our VAX for mail, but each to have their own separate return address. For example, one set of users could have the return address "user1@abc.wisc.edu", the other group have "user2@xyz.wisc.edu" I tried re-defining mx_vmsmail_localhost, but the entry in the system table seems to override whatever is in the process table. Thanks, Ravi Kochhar Univ. of Wisconsin kochhar@neurophys.wisc.edu 12/1/97 ================================================================================ Archive-Date: Mon, 1 Dec 1997 16:38:50 -0600 Message-ID: <199712012238.RAA12560@redstone.interpath.net> From: "Rich Hill" To: MX-List@MadGoat.com Date: Mon, 1 Dec 1997 16:23:17 +0000 MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Subject: Re: MX stat and accounting Reply-To: MX-List@MadGoat.com Content-Type: text/plain; charset=US-ASCII On 26 Nov 97 at 15:08:37 GMT, System Manager wrote: > hello, > > is it possible to have MX do some per-user accounting and > statistics (how many messages, how many bytes) or do I have > to write a dummy address rewritter that do the statistics ? > > regards, > Pierre Bru > > mailto:system@spotimage.fr If you are looking for all messages that pass through the router, I have added per message logging to ROUTER.EXE. This modification will log all messages (to address, from address, date/time, size, and transfer agent code) to a file (ROUTER.DAT). I have supplied Hunter with these modifications and I trust that they will be incorporated into the V5.0 release. Rich Hill -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rich Hill S I M Rich.Hill@sim.org Systems Engineer b y EasyLink: 62923838 SIM USA, Inc. P r a y e r Phone: 1-704-587-1462 Charlotte, NC since 1893 FAX: 1-704-587-1518 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- [SC] Smiley captioned for the humor impaired. ================================================================================ Archive-Date: Mon, 1 Dec 1997 17:04:22 -0600 Message-ID: <909FE9563AD2D0118D100000F82018A4160598@leopard.SD68.Nanaimo.BC.CA> From: Duc Pham Reply-To: MX-List@MadGoat.com To: "'MX-list@madgoat.com'" Subject: Help : How to stop SPAM RELAY Date: Mon, 1 Dec 1997 15:06:10 -0800 MIME-Version: 1.0 Content-Type: text/plain It seems to be our MX mail system being used as SPAM RELAY . Could someone tell me to how to stop it. Thanks in advance. Duc Pham Network and System Support Analyst School District #68 ( Nanaimo-Ladysmith ) Tel. ( 250 ) 741-5274 dpham@sd68.nanaimo.bc.ca ================================================================================ Archive-Date: Mon, 1 Dec 1997 18:09:19 -0600 Date: Mon, 01 Dec 1997 19:08:10 EST From: Robert Byer Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BE214.EDCFE600.19@mail.all-net.net> Subject: RE: Help : How to stop SPAM RELAY -----BEGIN PGP SIGNED MESSAGE----- > >It seems to be our MX mail system being used as SPAM RELAY . Could >someone tell me to how to stop it. > Welcome to the club, I've been gettin the sh*t spammed out of us. +------------------------+--------------------------------------------+ | 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 iQEVAwUBNIMKjKVSqzlBVJbBAQGGEgf9EvVZkzgEDvx3DrWf3c7gFfLSCA0mI4NL W7ebMUfl7rS4re7+Brf/Et24JQKpkhJm4af5q7RN9DZesDAW3+87VcWx1A1jn/uz DFK8UDGYQbXFuRoKqgyhzQmN+W5IBTD6JMkkaM5oXsFGcf6uHG+m885jkz4wn2lp i/o8Ptudx/i79hwQ9u15vpXRigiB/Tp402PZEBeP6YxPffPFxGZ4cfu/Mau9t2Eu +ix4QjN6IEu72G32OH16bSe8FTPYVLUtPbvplz/7piQg85tYltBQ/Pqd15owE2AD 3kTGeh9luhrOsn2AhqJjwOdzeG8OxfSntdg/2nhTDQeNYQxqWLtmSw== =Nf3C -----END PGP SIGNATURE----- ================================================================================ Archive-Date: Tue, 2 Dec 1997 09:02:51 -0600 Message-ID: <199712021502.KAA27280@redstone.interpath.net> From: "Rich Hill" To: MX-List@MadGoat.com Date: Tue, 2 Dec 1997 09:44:15 -0400 MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Subject: Corrupt Queue Reply-To: MX-List@MadGoat.com CC: rich.hill@sim.org Content-Type: text/plain; charset=US-ASCII On one of my MX 4.2 systems I had a corrupt queue file, MX_SYSTEM_QUEUE.FLQ_CTL. When trying to send mail or show the queue contents I would receive the error RMS-F-RER, file read error. I created a new queue (QUEUE CREATE/MAX=n), and then discovered that there were 200+ files in the [QUEUE.0] directory all named 0.HDR_INFO and 0.MSG_TEXT. How can I re-insert these back into the MX queue. The QUEUE SYNC command has no effect. I tried to rename one set of files to [QUEUE.1]1.* (to fake them out as entry one) and then do a QUEUE SYNC, but still no success. A QUEUE COMPRESS command ended up creating a new directory [QUEUE.OLD_0] with these files. How do I re-insert them into the MX queue??? TIA, Rich Hill ================================================================================ Archive-Date: Tue, 2 Dec 1997 09:41:01 -0600 Sender: goathunter@MadGoat.com Date: Tue, 2 Dec 1997 09:40:52 -0600 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BE28E.D7E475E3.13@goat.process.com> Subject: RE: Corrupt Queue "Rich Hill" writes: > >How can I re-insert these back into the MX queue. The QUEUE SYNC command >has no effect. I tried to rename one set of files to [QUEUE.1]1.* (to >fake them out as entry one) and then do a QUEUE SYNC, but still no >success. A QUEUE COMPRESS command ended up creating a new directory >[QUEUE.OLD_0] with these files. > >How do I re-insert them into the MX queue??? > You can try the MX_REFEED program, which you can find on ftp.madgoat.com in [.MX.CONTRIB]. It may or may not do the job.... Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ MultiNet & TCPware: The Best TCP/IP for OpenVMS http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Tue, 2 Dec 1997 09:48:19 -0600 Message-ID: <1134D0C75B6CD01197E800805FA63C82154C11@DTW5> From: Laishev Ruslan Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Subject: MAX Size of message logicals Date: Tue, 2 Dec 1997 18:44:12 +0300 Hi All ! Rrecently, I'm seems heard about max size of message can be received by SMTP server. This is right ? Syncerely yours... +--------------------------------------------------------------------+ Delta Telecom JSC Phone:7+ (812) 112-0699 191119,Russia, St.Petersburg, Fax: 7+ (812) 112-1099 Transportny per. 3 Fido: 2:5030/279 +-------------------------------------- Last SysAdmin in the GrayWall+ ================================================================================ Archive-Date: Tue, 2 Dec 1997 09:51:23 -0600 Sender: goathunter@MadGoat.com Date: Tue, 2 Dec 1997 09:51:13 -0600 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BE290.4A08FBCF.29@goat.process.com> Subject: RE: MAX Size of message logicals Laishev Ruslan writes: > >Hi All ! > Rrecently, I'm seems heard about max size of message can be >received by SMTP server. This is right ? > The only size limit I know of in MX SMTP Server is the amount of disk space available.... Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ MultiNet & TCPware: The Best TCP/IP for OpenVMS http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Tue, 2 Dec 1997 12:48:28 -0600 Date: Tue, 2 Dec 1997 19:46:55 +0100 From: "Jacek W. Tobiasz" Reply-To: MX-List@MadGoat.com To: MX-List Subject: Spam and 4.2 Message-ID: <97Dec2.195424met.14341@gateway.hq.atm.com.pl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello ! Yes, it hiting all of us now I think. Nowdays it is getting real problem (some day I thought "who will use ore unknown site as a relay ?"; till I got 3000 spam relayed mails one day). While waiting for MX 5.0, I got one idea ? Was someone thinking about using site interface as a relay (or spam) filter ? I thinnk it is possible to make site interface with rewrite rules do the job. Yes, this will allow mails to come in our MX que, but will not allow to get it out; just like black hole. It will not filter all mails, and may have big performace hit on system (path domain="*" , Path=SMTP for relay). But is just idea, perhaps someone will want test it ? At that moment I am not able to do it. Ok, some other ideas about MX features. Is it possible to include in smtp server logs ip address of connecting peer ? Now logged hostname/domainname does not have to be true ? What do you think about making callable interafce from MX, where we will get full control of message (all header, body, etc). so it will be possible to change what we want, to cancel mail etc. Does it make sense for you ? Of course it may be danger tool for mail system :-) OK. Some other ideas next time. Regards Jacek Tobiasz ================================================================================ Archive-Date: Tue, 2 Dec 1997 13:14:57 -0600 Date: Tue, 02 Dec 1997 14:13:44 EST From: Robert Byer Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BE2B4.F6597480.7@mail.all-net.net> Subject: RE: Spam and 4.2 -----BEGIN PGP SIGNED MESSAGE----- > >Yes, it hiting all of us now I think. Nowdays it is getting >real problem (some day I thought "who will use ore unknown site as >a relay ?"; till I got 3000 spam relayed mails one day). > Only 3000?? Hell, I usually get 15,000 at a time in blocks of 10... > >Ok, some other ideas about MX features. > >Is it possible to include in smtp server logs ip address of connecting >peer ? Now logged hostname/domainname does not have to be true ? > >What do you think about making callable interafce from MX, where we will >get full control of message (all header, body, etc). so it will be >possible to change what we want, to cancel mail etc. >Does it make sense for you ? Of course it may be danger tool for >mail system :-) > One thing that would be good is a way to change the routing information on e-mail in the queue. Every now and then we get e-mail that we need to change the route of an e-mail, which once it's in the queue we can't do and we have to remove the e-mail. +------------------------+--------------------------------------------+ | 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 iQEVAwUBNIQXD6VSqzlBVJbBAQGx1QgA0hFtATs/zDebCn7vQ9U+49IOhFeO8ON7 hyFMhlmx4QDkiMOntmr4IFHAXNW5uYpPFFSUN8dXhyGCI6SWQq6ICKrUwcoprE69 J75bFC00sGS0B7PzmPT4wn5Uq92iZHUuOYvRwZEbYd/uBrPV2dBedtT5wLy56j73 EFReg/zvUJLO+PFJ6o/nCSb9na5+A0jWcsGDtYe93+3GinN21ecn+2N2I5DKKzy4 aKK50Cs7jMoWSXe/XFqg7PWT6lR4YFQMsDniXs/CCcnofgpKyVOl1gEYehV+ykTr 44REkge3Ipv+raiFAomBkxrI57s1oqM7PmE/oj6NKJmWQwMhlqV2yw== =TUyl -----END PGP SIGNATURE----- ================================================================================ Archive-Date: Tue, 2 Dec 1997 14:47:51 -0600 From: Hunter Goatley Reply-To: MX-List@MadGoat.com Subject: Re: Mailing List problems Date: Tue, 02 Dec 1997 14:40:00 -0600 Message-ID: <34841DC0.4815DB16@MadGoat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: ryan@maley.org To: MX-List@WKUVX1.WKU.EDU Ryan J. Maley wrote: > > However, there are no files with MAILING_LIST extensions in the > MX_MLIST_DIR directory and sending mail to either TEST or TEST-REQUEST > generates a "no such user" error. > > I've tried stopping and starting the MX processes. No luck. I've also > reinstalled without success. > > Environment: Alpha OVMS 7.1, DEC TCP/IP 4.2 with SMTP and POP3. MX is > installed with the base software, mailing list support and doumentation > ONLY. > > I feel I've missed something basic in the setup, but it's escaping me at > the moment. Any suggestions? > MX is supposed to replace UCX's SMTP mailer. It won't work *with* UCX's mailer. Specifically, MX Router has to process the message to see that it's for a defined list. UCX will have no knowledge of an MX list. Once MX MLF generates the message to forward to the list, there's no way for MX to pass it to UCX to actually send it out. Also, you must ADD people via the -request address in order to create the .MAILING_LIST files in MX_MLF_DIR:. -- Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ MultiNet & TCPware: The Best TCP/IP for OpenVMS http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Tue, 2 Dec 1997 14:51:17 -0600 Sender: goathunter@MadGoat.com Date: Tue, 2 Dec 1997 14:51:06 -0600 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BE2BA.2E9DB1FD.11@goat.process.com> Subject: RE: Spam and 4.2 "Jacek W. Tobiasz" writes: > >While waiting for MX 5.0, I got one idea ? Was someone thinking about >using site interface as a relay (or spam) filter ? I thinnk it is possible >to make site interface with rewrite rules do the job. Yes, this could be done.... >What do you think about making callable interafce from MX, where we will >get full control of message (all header, body, etc). so it will be >possible to change what we want, to cancel mail etc. >Does it make sense for you ? Of course it may be danger tool for >mail system :-) > MX V5.0 does feature filter callouts in MX Router that will give you full control over messages, allowing you to rewrite headers, add headers, drop messages, re-route them, etc. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ MultiNet & TCPware: The Best TCP/IP for OpenVMS http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Tue, 2 Dec 1997 17:10:36 -0600 Date: Wed, 03 Dec 1997 10:06:55 EST-10EST From: Daiajo Tibdixious MACS <"svs::svist070"@stvincents.COM.AU> Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BE35B.A60312A0.53@stvincents.com.au> Subject: RE: Spam and 4.2 Tue, 02 Dec 1997 14:13:44 EST Robert Byer >>a relay ?"; till I got 3000 spam relayed mails one day). >Only 3000?? >Hell, I usually get 15,000 at a time in blocks of 10... I've been hoping someone would spam thru us so I've got a reason to upgrade. :} How do you know you've been spam-relayed? Do you sit there doing que show all the time? >One thing that would be good is a way to change the routing information on >e-mail in the queue. Every now and then we get e-mail that we need to >change the route of an e-mail, which once it's in the queue we can't do and >we have to remove the e-mail. Unless I missunderstand you, I often create temporary paths to reroute mail in the queue. Just define path blah blah, save, reset (notify:) router, and queue ready {id}, and off it goes. ================================================================================ Archive-Date: Tue, 2 Dec 1997 17:25:06 -0600 Date: Tue, 02 Dec 1997 18:23:44 EST From: Robert Byer Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BE2D7.E3569520.39@mail.all-net.net> Subject: RE: Spam and 4.2 -----BEGIN PGP SIGNED MESSAGE----- > >>>>a relay ?"; till I got 3000 spam relayed mails one day). >>Only 3000?? >>Hell, I usually get 15,000 at a time in blocks of 10... > >I've been hoping someone would spam thru us so I've got a reason to upgrade. >:} > >How do you know you've been spam-relayed? Do you sit there doing que show all >the time? > Well, not exactly.. On an average day we usually only move like maby 1,000 pieces of e-mail and the disk activity on the mail disk is very light. I can usually tell when "something" large is going through the system when the mail hard disk starts going nuts and the IO load on that disk jumps quite a bit. (our e-mail disk is a RA82 disk in an array cabinet, so it makes alot of noise.) I can also tell as our network activity jumps quite a bit and our lan analyzer starts beeping. So when I see this happen, I check the queue. Also they usually try to sneek it in around 2:00am and I can usually just sit their and delete them out of the queue as they are arriving. I don't always catch them since we have a 10MEG link to the internet they go out quick (and I have six SMTP process going) and I usually only get a third of them if I didn't catch them when they arrived. > >>One thing that would be good is a way to change the routing information on >>e-mail in the queue. Every now and then we get e-mail that we need to >>change the route of an e-mail, which once it's in the queue we can't do and >>we have to remove the e-mail. > >Unless I missunderstand you, I often create temporary paths to reroute mail in >the queue. Just define path blah blah, save, reset (notify:) router, and queue >ready {id}, and off it goes. > Hmm.. I've tried that and had no real luck. Some of our users send to sites that have misconfigured DNS entries and it hanges in our queue, so I have to go, find what the path should be and make one. I'll have to look into it more carefully. +------------------------+--------------------------------------------+ | 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 iQEVAwUBNIRRpKVSqzlBVJbBAQElHwf/Q2OWd+1/Q6/GMxxnog39NsfZtWCUn3iX gZVutXa8T5qAMHwn9olQ72ubW7UKGwFgUHVUFL/ffahzrik9onCkQw0RRWvS41+T JbxHwc+h1BwkyLeRRhyGP5c8oHg5SdshEMWwyVjo/+r45j40Qx/+765vYYcW/P3N KAyrW9Uo2v9oLzbKWtpfjfghbzICzSZqfb7UCE+ZirbQminbhZp5zhukrhApckPn o7jOQTAVzNTrzgINoR2JY0LdLYyEaRPLjErQrs4VmborZQxiTtZXsTQZXn8LiUHE DMQn/AM4773+d7qG1pLsoWL9+BI34hOZRtS6e/a10N2tVAGrSgLXxA== =6cXW -----END PGP SIGNATURE----- ================================================================================ Archive-Date: Wed, 3 Dec 1997 03:12:16 -0600 Message-ID: <199712030912.JAA16639@muttley.cen.hw.ac.uk> To: MX-List@MadGoat.com Reply-To: MX-List@MadGoat.com Subject: How does everyone achieve Spam relay prevention vith MX 4.2? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Dec 1997 09:12:04 +0000 From: "David J. Morriss" In common with many sites, I suspect, we are being hit very heavily by SPAM relaying at the moment. In the (hopefully short ;-) period up to the release of MX 5.0 I'd like to counter the attacks in some way. So far I have a simplistic DCL procedure which scans the queue periodically, tries to identify entries from off-site which have origin and destination as SMTP, and offers them for deletion (so I can issue a manual MCP QUE CAN). I'll consider letting this thing run all by itself when I'm confident it isn't going to trash valid stuff, but it's not an elegant solution. How are other sites handling this at the moment? I realise there are other solutions, such as letting sendmail on a Unix host take them and deal with them, but for various reasons it's not an option for us at this instant. Thanks, Dave -- David Morriss, Computing Services, | Tel: +44 (0)131 451 3262 (DDI) Heriot-Watt University, Edinburgh, EH14 4AS, | FAX: +44 (0)131 451 3261 Scotland, UK | D.J.Morriss@hw.ac.uk ================================================================================ Archive-Date: Wed, 3 Dec 1997 03:30:07 -0600 Date: Wed, 03 Dec 1997 10:34:16 MET-1MET DST From: Franz Schoenbauer Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: system@eimoni.tuwien.ac.at Message-ID: <009BE35F.7805DC80.7@eimoni.tuwien.ac.at> Subject: RE: How does everyone achieve Spam relay prevention vith MX 4.2? There is a mildly absurd solution: change the name of your mailhost, make an mx record of the previous name to point to it. spam mails (and all other mails) will show the new name in the from line some people will block your mails due to spamming but not many. in two week, when mx50 comes out, change back to original name. this protects your valued name from being on balck lists ... of course it doesnt do any good against the spam mails themselves. Yours Franz Schoenbauer, Tech. Univ. Vienna, | system@eimoni.tuwien.ac.at Resselg. 3/188 A-1040, Vienna, Austria | +43(1)58801 ext. 4126 ================================================================================ Archive-Date: Wed, 3 Dec 1997 05:29:19 -0600 Message-ID: <199712031129.LAA17414@muttley.cen.hw.ac.uk> To: MX-List@MadGoat.com Reply-To: MX-List@MadGoat.com Subject: What's wrong with my queue? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Dec 1997 11:29:10 +0000 From: "David J. Morriss" Currently the output from MCP QUE SHOW /FULL looks like this (edited to reduce volume somewhat): ---------- Status: OPERHOLD, size: 12102 bytes Status: OPERHOLD, size: 1406 bytes Status: OPERHOLD, size: 4062 bytes [ 60 similar lines deleted] Status: OPERHOLD, size: 2854 bytes Status: OPERHOLD, size: 1789 bytes Status: OPERHOLD, size: 43 bytes Entry: 38, Origin unknown Status: IN-PROGRESS, size: 0 bytes Created: 3-DEC-1997 11:01:30.96, expires 2-JAN-1998 11:01:30.96 Last modified 3-DEC-1997 11:01:30.96 Entry: 85, Origin unknown Status: IN-PROGRESS, size: 0 bytes Created: 3-DEC-1997 11:13:04.42, expires 2-JAN-1998 11:13:04.42 Last modified 3-DEC-1997 11:13:04.42 ---------- Why the OPERHOLD entries without "Entry:" headers? I've seen OPERHOLD in the "Status:" line, but not like this. Is this a corrupted queue? More to the point, am I likely to have caused this by running my anti-relay job which does lots of QUE CANCEL's? Any hints as to how to put things back on the rails? Thenks, Dave -- David Morriss, Computing Services, | Tel: +44 (0)131 451 3262 (DDI) Heriot-Watt University, Edinburgh, EH14 4AS, | FAX: +44 (0)131 451 3261 Scotland, UK | D.J.Morriss@hw.ac.uk ================================================================================ Archive-Date: Wed, 3 Dec 1997 07:40:56 -0600 Date: Wed, 3 Dec 1997 08:39:20 -0500 From: "Brian Tillman, x8425" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BE34F.69A69CC0.3@swdev.si.com> Subject: RE: How does everyone achieve Spam relay prevention vith MX 4.2? David Morriss (D.J.Morriss@hw.ac.uk) writes: >In common with many sites, I suspect, we are being hit very heavily by SPAM >relaying at the moment. ... >How are other sites handling this at the moment? I would think David Cathey's WHITEICE program could help here. Check the archives. It's been posted here before. Also check [.CONTRIB]. It might be there. -- 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: Wed, 3 Dec 1997 13:56:38 -0600 From: "Patrick Cox" Reply-To: MX-List@MadGoat.com To: mx-list@madgoat.com Date: Wed, 3 Dec 1997 16:00:27 AST Subject: Re: How does everyone achieve Spam relay prevention vith MX 4.2? In-Reply-To: <199712030912.JAA16639@muttley.cen.hw.ac.uk> Message-ID: On 3 Dec 97 at 9:12, David J. Morriss wrote: > How are other sites handling this (spam relay) at the moment? > What we are doing (and it's a little labour intensive), is to shutdown the smtp delivery agents and leave the smtp server running. This allows mail in, and holds it in the queue. After some period of time, we shutdown the smtp server and run a spam filter I wrote in fortran. The program outputs the queue to a file and then scans the file for addresses that are in a kill list. It then generates a .com file with the following on each line: que can 524 !20 <21765@aol.com> => !que can 123 !01 => It shows either a commented line for non-spam/ non-relay addresses, or addresses we haven't ID'ed as spam, and the non-commented line is for spam. We then scan this file and confirm their validity and then run the .com file to cancel que entries and then purge them. Next step is to start the delivery agents to send out all the good mail and then start the process over again. We usually leave the system wide open during the day because not much spam comes through then. Most arrives between midnight and 3:00am. And we do the filter first thing in the morning. Works fine for us. We've been doing it for about a month now, and have had less MX problems. TTYL, ''' Information Technology Patrick Cox (o o) The Resources Corporate Services Unit ---------------oOO--(_)--OOo------------------------------------------ Interactive:(902)893-6233 ================================================================================ Archive-Date: Wed, 3 Dec 1997 17:14:55 -0600 Sender: goathunter@MadGoat.com Date: Wed, 3 Dec 1997 17:14:42 -0600 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BE397.68E5D871.6@goat.process.com> Subject: RE: What's wrong with my queue? "David J. Morriss" writes: > >Currently the output from MCP QUE SHOW /FULL looks like this (edited to >reduce volume somewhat): > [...] >Why the OPERHOLD entries without "Entry:" headers? I've seen OPERHOLD in the >"Status:" line, but not like this. Is this a corrupted queue? > Yep, sounds like it. >More to the point, am I likely to have caused this by running my anti-relay >job which does lots of QUE CANCEL's? > Yes, that could exacerbate the queue corruption problem. Sorry. >Any hints as to how to put things back on the rails? > Creating a new queue file is really the only way. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ MultiNet & TCPware: The Best TCP/IP for OpenVMS http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Wed, 3 Dec 1997 17:16:50 -0600 Sender: goathunter@MadGoat.com Date: Wed, 3 Dec 1997 17:16:41 -0600 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BE397.AF5B8AC6.9@goat.process.com> Subject: RE: User-settable return address ? Ravi Kochhar writes: > > Is it possible for users to have a return address that is different > from the default defined by MX ? We would like two groups to use > our VAX for mail, but each to have their own separate return address. > > For example, one set of users could have the return address > "user1@abc.wisc.edu", the other group have "user2@xyz.wisc.edu" > > I tried re-defining mx_vmsmail_localhost, but the entry in the system > table seems to override whatever is in the process table. > Yes, it does. In MX V5.0, you can do this with new logicals that have been created that can be defined /EXEC in the user's process or job table. Until then, you can use the ADDRESS_REWRITER capability to rewrite certain addresses. Pick up the example at: ftp://ftp.madgoat.com/mx/examples/address_rewriter.zip It's designed to let you do exactly what you're wanting to do on a per-user basis. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ MultiNet & TCPware: The Best TCP/IP for OpenVMS http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Wed, 3 Dec 1997 18:03:23 -0600 Message-ID: <3485E8C6.349FDB87@atm.com.pl> Date: Thu, 04 Dec 1997 00:18:30 +0100 From: Jacek Tobiasz Reply-To: MX-List@MadGoat.com MIME-Version: 1.0 To: MX-List@MadGoat.com Subject: Re: spam mx References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > > How are other sites handling this (spam relay) at the moment? > > > > What we are doing (and it's a little labour intensive), is to shutdown > the smtp delivery agents and leave the smtp server running. This > allows mail in, and holds it in the queue. After some period of time, > we shutdown the smtp server and run a spam filter I wrote in fortran. > The program outputs the queue to a file and then scans the file for > addresses that are in a kill list. It then generates a .com file with > the following on each line: > > que can 524 !20 <21765@aol.com> => > !que can 123 !01 => [...] seems to be ok. This is not racket science but would not you like to share the code with others ? MX is to be out soon but perhaps it will help someone. Regards Jacek ================================================================================ Archive-Date: Thu, 4 Dec 1997 00:32:37 -0600 Date: Thu, 04 Dec 1997 17:28:51 EST-10EST From: Daiajo Tibdixious MACS <"svs::svist070"@stvincents.COM.AU> Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BE462.8D29B380.26@stvincents.com.au> Subject: RE: How does everyone achieve Spam relay prevention vith MX 4.2? Wed, 03 Dec 1997 09:12:04 +0000 "David J. Morriss" >which scans the queue periodically, tries to identify entries from off-site >which have origin and destination as SMTP, and offers them for deletion (so I >can issue a manual MCP QUE CAN). I'll consider letting this thing run all by >itself when I'm confident it isn't going to trash valid stuff, but it's not >an elegant solution. Why not queue hold them, instead of canceling straight away? Then you don't have to worry if it gets it wrong. ================================================================================ Archive-Date: Thu, 4 Dec 1997 03:41:44 -0600 Message-ID: <199712040941.JAA19551@muttley.cen.hw.ac.uk> To: MX-List@MadGoat.com From: D.J.Morriss@hw.ac.uk Reply-To: MX-List@MadGoat.com In-Reply-To: <009BE397.68E5D871.6@goat.process.com> References: <009BE397.68E5D871.6@goat.process.com> Subject: Re: What's wrong with my queue? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Dec 1997 09:41:35 +0000 Sender: cendjm@ccen.hw.ac.uk On Wed, 3 Dec 1997 17:14:42 -0600 Hunter Goatley wrote: > >Is this a corrupted queue? > Yep, sounds like it. And it was :-( > >Any hints as to how to put things back on the rails? > > > Creating a new queue file is really the only way. Yes. Things are back on the rails, but (to strain the metaphor), there are a number of wagons still in the ditch. What I mean is that the files "lost" when the queue became bent need re-queueing. I have looked at MX_REFEED, but am not having much success. Firstly, the command procedure MX_REFEED1.COM builds logicals for the program called MX_REFEED_WORKDIR and MX_REFEED_HDRFILE, but the program wants them to be called REFEED_WORKDIR and REFEED_HDRFILE. However, once that has been fixed, the program itself fails with an access violation as it's trying to read the *.HDR_INFO file and build the headers. Unfortunately, I'm not much of a C programmer, so I don't understand why it's failing. It's to be run on an AlphaServer with DECC, so I built it with MMS/MAC=("__ALPHA__=1","__DECC__=1"). I have tried running it through the debugger, and have tried /NOMEMBER_ALIGNMENT in case it was a byte-alignment issue. All to no avail. The problem seems to lie with the statement: inbuf_p->text[inbuf_p->count] = 0; where the relevant declarations are: char inbuf[REC_SIZE + 1]; struct INP_HDR { unsigned short type; unsigned short count; char *text; }; struct INP_HDR *inbuf_p = (struct INP_HDR *) inbuf; Has anyone managed to get this to work on an Alpha with DECC (or indeed, anywhere ;-)? The logic looks fairly simple (just prepending header types onto stored records, the types being coded at the start of the records), so I guess I could re-code it in DCL at a push, but I'd prefer not to have to. Thanks, Dave -- David Morriss, Computing Services, | Tel: +44 (0)131 451 3262 (DDI) Heriot-Watt University, Edinburgh, EH14 4AS, | FAX: +44 (0)131 451 3261 Scotland, UK | D.J.Morriss@hw.ac.uk ================================================================================ Archive-Date: Thu, 4 Dec 1997 08:43:06 -0600 Message-ID: <199712041440.OAA23631@zaphod.CFMfel01.icl.co.uk> From: "Jamie Jones" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Date: Thu, 4 Dec 1997 14:47:34 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Subject: For the wish list In-Reply-To: <199712041110.LAA01315@finial.netlink.co.uk> I don't think I've seen these mentioned before, but apologies if I'm repeating myself. Firstly, with all the spam going on, it's difficult to track something when you have multiple ID's pointing to a common mailbox. Any chance of the envelope information? Something like: X-MX-RCPT-TO: ... Secondly, defining rewrite rules is a pain in the arse, when you are altering something near the top of the list.. I remember when "DEFINE PATH" needed to be done in order, but now it's done more intelligently... Any chance of a similar mechanism being applied to the DEFINE REWRITE ? At least being able to remove rewrites with remove rewrite * would help things somewhat. I suppose an MCP> edit/edt rewrite would be too much to ask :) At the moment, I do MCP> show rewrite/command/output=temp. Then edit the file to replace define with remove, and remove the RHS. Then run it through MCP, and then edit the changes to the original temp. file, then run that through mcp. Other than writing a program to automate the editting of this, is there any easier way ? Anyone written such an automator ? Thanks, by the way, for MX. I've been a loyal fan for about 8 years... Regards, Jamie -- Jamie Jones, "You never get a first chance to make a second opinion" EMAIL: jamie@bishopston.com WWW: http://www.bishopston.com/jamie/ ================================================================================ Archive-Date: Thu, 4 Dec 1997 08:49:55 -0600 Sender: goathunter@MadGoat.com Date: Thu, 4 Dec 1997 08:49:46 -0600 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BE41A.094C65FF.9@goat.process.com> Subject: RE: For the wish list "Jamie Jones" writes: > >Any chance of the envelope information? >Something like: > >X-MX-RCPT-TO: ... > That's something I've thought about doing. I'll add it to the wish list. >I suppose an MCP> edit/edt rewrite would be too much to ask :) > This is one reason I always do this: $ EDIT CONFIG.MCP .... $ MCP/NOFILE MCP> @CONFIG.MCP MCP> SAVE MX_CONFIG.MXCFG MCP> RESET/CLUSTER That way, all the rewrite rules are in place in the order they should be. Unfortunately, I've found no way to "intelligently" order rewrite rules automatically, because there's no simple rule you can follow as I did with PATHs. You know the order in which you want your rewrite rules to be applied, and the order matters. MX can't second-guess that. >At the moment, I do MCP> show rewrite/command/output=temp. >Then edit the file to replace define with remove, and remove the RHS. >Then run it through MCP, and then edit the changes to the original >temp. file, then run that through mcp. Other than writing a program >to automate the editting of this, is there any easier way ? Anyone >written such an automator ? > See above. >Thanks, by the way, for MX. I've been a loyal fan for about 8 >years... > Thanks, Jamie! Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ MultiNet & TCPware: The Best TCP/IP for OpenVMS http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Thu, 4 Dec 1997 09:29:47 -0600 Date: Thu, 4 Dec 1997 10:28:06 -0500 From: "Brian Tillman, x8425" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BE427.C6000820.29@swdev.si.com> Subject: RE: For the wish list >Any chance of the envelope information? >Something like: > >X-MX-RCPT-TO: ... The MAIL FROM information is there (Return-Path). I think this info would be a nice addition. -- 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, 4 Dec 1997 15:17:21 -0600 Message-ID: <199712041643.LAA12897@redstone.interpath.net> From: "Rich Hill" To: MX-List@MadGoat.com Date: Thu, 4 Dec 1997 15:58:54 -0400 MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Subject: Re: What's wrong with my queue? Reply-To: MX-List@MadGoat.com In-Reply-To: <199712041106.GAA13081@auth1.interpath.net> Content-Type: text/plain; charset=US-ASCII [snip] > Yes. Things are back on the rails, but (to strain the metaphor), there are a > number of wagons still in the ditch. What I mean is that the files "lost" > when the queue became bent need re-queueing. > > I have looked at MX_REFEED, but am not having much success. Firstly, the > command procedure MX_REFEED1.COM builds logicals for the program called > MX_REFEED_WORKDIR and MX_REFEED_HDRFILE, but the program wants them to be > called REFEED_WORKDIR and REFEED_HDRFILE. > > However, once that has been fixed, the program itself fails with an access > violation as it's trying to read the *.HDR_INFO file and build the headers. > Unfortunately, I'm not much of a C programmer, so I don't understand why it's > failing. [snip] > The logic looks fairly simple (just prepending header types onto stored > records, the types being coded at the start of the records), so I guess I > could re-code it in DCL at a push, but I'd prefer not to have to. Yes, I just ran into this one myself, and not having a C compiler handy (nor being a C programmer), I rewrote the whole thing in DCL. I'll be sending a copy to Hunter for inclusion with the rest of the [.contrib] stuff. Dave, I'll send you a copy directly, just in case you still need it. Rich -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rich Hill S I M Rich.Hill@sim.org Systems Engineer b y EasyLink: 62923838 SIM USA, Inc. P r a y e r Phone: 1-704-587-1462 Charlotte, NC since 1893 FAX: 1-704-587-1518 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- [SC] Smiley captioned for the humor impaired. ================================================================================ Archive-Date: Fri, 5 Dec 1997 02:58:32 -0600 Reply-To: MX-List@MadGoat.com From: "Martin Vorlaender" To: Subject: Re: For the wish list Date: Fri, 5 Dec 1997 09:57:58 +0100 Message-ID: <01bd015b$e22f14f0$187f10ac@pcmv.pdv.intern> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi, everyone, >>I suppose an MCP> edit/edt rewrite would be too much to ask :) >> >This is one reason I always do this: > > $ EDIT CONFIG.MCP > .... > $ MCP/NOFILE > MCP> @CONFIG.MCP > MCP> SAVE MX_CONFIG.MXCFG > MCP> RESET/CLUSTER > >That way, all the rewrite rules are in place in the order they should >be. Unfortunately, I've found no way to "intelligently" order rewrite >rules automatically, because there's no simple rule you can follow as >I did with PATHs. You know the order in which you want your rewrite >rules to be applied, and the order matters. MX can't second-guess >that. I wrote a small DCL that first removes all old rewrite rules, and then re-writes them. Your solution probably is less stressing for MX. Think I'll post it anyway, though. >>Thanks, by the way, for MX. I've been a loyal fan for about 8 years... Yup. That's something I've been wanting to do for some time, too. cu, Martin [--cut--] $! Rewrite Rewrite rules $ $ MCP = "$MX_EXE:MCP.EXE" $ $! First, remove all rewrite rules $ GOSUB remove_rewrite_rules $ IF .NOT. $STATUS THEN - WRITE SYS$OUTPUT "Error ", $STATUS, " occured when removing rewrite rules" $ $ MCP ! Add list of "DEFINE REWRITE_RULE" commands here SAVE RESET/CLUSTER QUIT $ $ remove_rewrite_rules: $ tmpfile = "SYS$SCRATCH:MX_REWRITE_RULES.TMP" $ outfile = "SYS$SCRATCH:MX_REWRITE_RULES.COM" $ $ OPEN/WRITE/ERROR=err out 'outfile' $ WRITE/ERROR=err out "$ RUN MX_EXE:MCP.EXE" $ $ DEFINE/USER SYS$OUTPUT 'tmpfile' $ MCP SHOW REWRITE_RULES $ $ OPEN/READ/ERROR=err tmp 'tmpfile' $ loop: $ READ/ERROR=err/END_OF_FILE=eof tmp line $ IF F$EXTRACT(0,10,line) .NES. " Rewrite " THEN GOTO loop $ line = line - " Rewrite " $ p = F$LOCATE(" => ",line) $ dq0 = F$EXTRACT(0,p,line) $ GOSUB double_quotes $ WRITE/ERROR=err out "REMOVE REWRITE_RULE ''dq'" $ GOTO loop $ eof: $ WRITE/ERROR=err out "EXIT" $ WRITE/ERROR=err out "$" $ CLOSE/ERROR=err out $ @'outfile' $ err: $ stat = $STATUS $ $ IF F$TRNLNM("tmp") .NES. "" THEN CLOSE tmp $ IF F$TRNLNM("out") .NES. "" THEN CLOSE out $ DELETE/NOLOG/NOCONFIRM 'tmpfile';,'outfile'; $ RETURN stat $ $ double_quotes: $ ! Double all Quotes in string in symbol dq0, return in symbol dq $ v = F$VERIFY(0) $ dq = "" $ i = 0 $ l = F$LENGTH(dq0) $ dq_loop: $ c = F$EXTRACT(i,1,dq0) $ IF c .EQS. """" $ THEN $ dq = dq + """""" $ ELSE $ dq = dq + c $ ENDIF $ i = i + 1 $ IF i .lt. l THEN GOTO dq_loop $ v = F$VERIFY(v) $ RETURN -- | Martin Vorlaender VMS & WNT programmer OpenVMS -- | work: mv@pdv-systeme.de Where do you want | http://www.pdv-systeme.de/users/martinv/ to BE today? | home: martin@radiogaga.harz.de ================================================================================ Archive-Date: Fri, 5 Dec 1997 09:51:02 -0600 Message-ID: <199712051550.PAA23772@muttley.cen.hw.ac.uk> To: MX-List@MadGoat.com From: D.J.Morriss@hw.ac.uk Reply-To: MX-List@MadGoat.com Subject: Queue repair - some pitfalls MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Dec 1997 15:50:09 +0000 Sender: cendjm@ccen.hw.ac.uk Firstly, thanks to all who replied to my earlier pleas for help with a queue corruption problem. (Particular thanks to Rok Vidmar and Rich Hill). I seem to have found a few basic problems as a consequence of this exercise, which I'd like to share. My first problem was that I didn't realise quite what QUEUE COMPRESS was supposed to do, and was pleased to find that it created directories called MX$ROOT:[QUEUE.OLD_%] containing the files relating to the corrupt queue. This isn't documented as far as I can see. Neither is this recommended as the best way to start the queue repair process. The more obvious QUEUE CREATE command doesn't create these directories apparently. However, if operating in headless chicken mode like me, you QUEUE COMPRESS _again_ you end up with OLD_%.DIR;2 files (note the version number)! Moral: don't. But it'd be nice if MCP was a little less eager to do this! The second problem stems from the philosophy of MX_REFEED. It uses the message headers (held in *.HDR_INFO), and the message body (held in *.MSG_TXT) to rebuild the message for re-queueing. However, it unfortunately uses the header contents to rebuild the envelope addresses, rather than examining the *.SRC_INFO file. This causes problems when the dead message was originally from a list, since the "To:" field is most likely to consist of the list name (whereas the envelope address would have identified the local user to whom the message was destined). The consequence of this design, is to send the incoming message from a list back to the list! However, looking on the bright side, it will send all those moronic messages to "Friend@public.com" into a black hole ;-) By the way, where can I find a list of the tags used in the *.SRC_INFO files (and others)? Dave -- David Morriss, Computing Services, | Tel: +44 (0)131 451 3262 (DDI) Heriot-Watt University, Edinburgh, EH14 4AS, | FAX: +44 (0)131 451 3261 Scotland, UK | D.J.Morriss@hw.ac.uk ================================================================================ Archive-Date: Fri, 5 Dec 1997 12:26:04 -0600 Date: Fri, 5 Dec 1997 13:24:37 -0500 From: "Brian Tillman, x8425" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BE509.9931DD40.10@swdev.si.com> Subject: RE: Queue repair - some pitfalls >By the way, where can I find a list of the tags used in the *.SRC_INFO files >(and others)? In the MX sources, of course. Here's a Fortran version: INTEGER MX_K_HDR_FIRSTCODE INTEGER MX_K_HDR_FROM ! From: INTEGER MX_K_HDR_SENDER ! Sender: INTEGER MX_K_HDR_TO ! To: INTEGER MX_K_HDR_R_TO ! Resent-To: INTEGER MX_K_HDR_CC ! cc: INTEGER MX_K_HDR_R_CC ! Resent-cc: INTEGER MX_K_HDR_BCC ! bcc: INTEGER MX_K_HDR_R_BCC ! Resent-bcc: INTEGER MX_K_HDR_MESSAGE_ID ! Message-ID: INTEGER MX_K_HDR_R_MESSAGE_ID ! Resent-Message-ID: INTEGER MX_K_HDR_IN_REPLY_TO ! In-Reply-To: INTEGER MX_K_HDR_REFERENCES ! References: INTEGER MX_K_HDR_KEYWORDS ! Keywords: INTEGER MX_K_HDR_SUBJECT ! Subject: INTEGER MX_K_HDR_ENCRYPTED ! Encrypted: INTEGER MX_K_HDR_DATE ! Date: INTEGER MX_K_HDR_REPLY_TO ! Reply-To: INTEGER MX_K_HDR_RECEIVED ! Received: INTEGER MX_K_HDR_R_REPLY_TO ! Resent-Reply-To: INTEGER MX_K_HDR_R_FROM ! Resent-From: INTEGER MX_K_HDR_R_SENDER ! Resent-Sender: INTEGER MX_K_HDR_R_DATE ! Resent-Date: INTEGER MX_K_HDR_RETURN_PATH ! Return-path: INTEGER MX_K_HDR_OTHER ! Other: INTEGER MX_K_HDR_X_WARNING ! X-Warning: INTEGER MX_K_HDR_X_TO ! X-To: INTEGER MX_K_HDR_X_R_TO ! X-Resent-To: INTEGER MX_K_HDR_X_CC ! X-cc: INTEGER MX_K_HDR_X_R_CC ! X-Resent-cc: INTEGER MX_K_HDR_X_BCC ! X-bcc: INTEGER MX_K_HDR_X_R_BCC ! X-Resent-bcc: INTEGER MX_K_HDR_MIME_VERSION ! Mime-Version: INTEGER MX_K_HDR_MIME_C_T_E ! Content-Transfer-Encoding: INTEGER MX_K_HDR_MIME_C_TYPE ! Content-Type: INTEGER MX_K_HDR_LASTCODE PARAMETER( MX_K_HDR_FIRSTCODE = 1 ) PARAMETER( MX_K_HDR_FROM = 1 ) PARAMETER( MX_K_HDR_SENDER = 2 ) PARAMETER( MX_K_HDR_TO = 3 ) PARAMETER( MX_K_HDR_R_TO = 4 ) PARAMETER( MX_K_HDR_CC = 5 ) PARAMETER( MX_K_HDR_R_CC = 6 ) PARAMETER( MX_K_HDR_BCC = 7 ) PARAMETER( MX_K_HDR_R_BCC = 8 ) PARAMETER( MX_K_HDR_MESSAGE_ID = 9 ) PARAMETER( MX_K_HDR_R_MESSAGE_ID = 10 ) PARAMETER( MX_K_HDR_IN_REPLY_TO = 11 ) PARAMETER( MX_K_HDR_REFERENCES = 12 ) PARAMETER( MX_K_HDR_KEYWORDS = 13 ) PARAMETER( MX_K_HDR_SUBJECT = 14 ) PARAMETER( MX_K_HDR_ENCRYPTED = 15 ) PARAMETER( MX_K_HDR_DATE = 16 ) PARAMETER( MX_K_HDR_REPLY_TO = 17 ) PARAMETER( MX_K_HDR_RECEIVED = 18 ) PARAMETER( MX_K_HDR_R_REPLY_TO = 19 ) PARAMETER( MX_K_HDR_R_FROM = 20 ) PARAMETER( MX_K_HDR_R_SENDER = 21 ) PARAMETER( MX_K_HDR_R_DATE = 22 ) PARAMETER( MX_K_HDR_RETURN_PATH = 23 ) PARAMETER( MX_K_HDR_OTHER = 24 ) PARAMETER( MX_K_HDR_X_WARNING = 25 ) PARAMETER( MX_K_HDR_X_TO = 26 ) PARAMETER( MX_K_HDR_X_R_TO = 27 ) PARAMETER( MX_K_HDR_X_CC = 28 ) PARAMETER( MX_K_HDR_X_R_CC = 29 ) PARAMETER( MX_K_HDR_X_BCC = 30 ) PARAMETER( MX_K_HDR_X_R_BCC = 31 ) PARAMETER( MX_K_HDR_MIME_VERSION = 32 ) PARAMETER( MX_K_HDR_MIME_C_T_E = 33 ) PARAMETER( MX_K_HDR_MIME_C_TYPE = 34 ) PARAMETER( MX_K_HDR_LASTCODE = 34 ) -- 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: Wed, 10 Dec 1997 12:04:26 -0600 From: cczanj@axp0.ccc.nottingham.ac.uk (Andy Jack) Subject: MX 5.0? Or alternative SMTP ports? Date: 10 Dec 1997 17:48:53 GMT Message-ID: <66mkm5$b4i@paperboy.ccc.nottingham.ac.uk> Reply-To: MX-List@MadGoat.com To: MX-List@WKUVX1.WKU.EDU As with so many others, our VAXes are getting spam relayed through them and I am under pressure here to "do something about it". Is MX 5.0 really imminent or should I take up the other tack of getting MX to listen on a non-standard port (by editing and rebuilding sources for 4.2) and having all mail intended for the VAXes go via our Unix relay which has had a lot of anti-spam work put in? Sad, isn't it, that something so obviously useful as a global communication medium should be perverted by the spammers and cause so much work to prevent abuse? Andy ------------------------------------------------------------------------ Cripps Computing Centre, RFC-822: Andy.Jack@nottingham.ac.uk University of Nottingham, X.400: G=Andy;S=Jack;O=Nottingham;P=UK.AC;C=GB Nottingham NG7 2RD, UK Phone: +44 115 951 3328 ================================================================================ Archive-Date: Thu, 11 Dec 1997 22:49:37 -0600 Date: Thu, 11 Dec 1997 21:49:24 MST From: Mark Tarka Reply-To: MX-List@MadGoat.com To: mx-list@wkuvx1.wku.edu Message-ID: <009BEA07.1BC0B672.9@earth.oscs.montana.edu> Subject: Undeliverable mail goes...where? Clawing my way through the fog, I come to the realization that there are a lot of people out there, subscribed to mailing lists, or lucky to have been added to someone's distribution list, who clock out of their accounts without notice to anyone outside their immediate environment. Still the mail rolls in. The account's closed. Sending mail back appended to a "the Postmaster regrets to inform you..." would necessarily add to the clutter on the net. Maybe I'm wrong, and everyone is being neat about their electronic lives, and that's the reason why I see so few bounced mails that I've sent to a group using a mail-distribution format coming back at me. But I was wondering if some sites are configured to direct mail addressed to accounts that no longer exist into the bit-bucket (if that's the correct expression). Any comments? Mark (Clueless-in-Wonderland :-) ================================================================================ Archive-Date: Fri, 12 Dec 1997 08:18:38 -0600 Sender: goathunter@MadGoat.com Date: Fri, 12 Dec 1997 08:18:34 -0600 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BEA5F.006F23DC.35@ALPHA.WKU.EDU> Subject: RE: Undeliverable mail goes...where? Mark Tarka writes: > >Sending mail back appended to a "the Postmaster regrets to inform >you..." would necessarily add to the clutter on the net. > Yep, but that's what should happen.... >But I was wondering if some sites are configured to direct mail >addressed to accounts that no longer exist into the bit-bucket (if >that's the correct expression). > I'm sure some sites probably are set up that way, whether by design or by accident. Hunter ------ Hunter Goatley, Process Software, http://www.process.com TCPware & MultiNet: The Best TCP/IP for OpenVMS http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Fri, 12 Dec 1997 20:09:46 -0600 From: stenns@vw.tci.uni-hannover.de (Michael Stenns) Subject: changed MX_DELIVER_DIGESTS.COM Date: 12 Dec 1997 19:03:19 GMT Message-ID: <66s1pn$j5r$2@newsserver.rrzn.uni-hannover.de> Reply-To: MX-List@MadGoat.com To: MX-List@WKUVX1.WKU.EDU Hi, I have a mailing list on my system with digest support. The digest was created by a special account (defined as system user) with the mx-digest.zip package from the contrib directory. What I disliked was that I got often mail on the digest creating account from list members who did not read the instructions at the top of the digest report carefully. There might be many solutions to solve this, I did change the MX_DELIVER_DIGESTS.COM command procedure. The changed version bypasses VMS mail and uses MX_SITE_IN.EXE instead. This allows complete control over the SMTP headers. The generated headers are From: list owner ! simply line 3 from list-digest.info file To: list-digest@digest_host ! digest_host is line 2 from list-digest.info file Reply-To: list@digest_host Date: current date !needs SYS$TIMEZONE_DIFFERENTIAL defined for correct time zone infornation Subject: !nothing changed here MX_SITE_IN.EXE seems to need some privileges, but the digest creation process has not longer to be a "system user" because the digests comes from the list owners now. I simply use the system account now. If anybody is interested in the changed file, it is available by sending a mail to FileServ@cat.tci.uni-hannover.de with sendme MX_DELIVER_DIGESTS as a single line in the body. Regards, Michael -- Michael Stenns Email: stenns@vw.tci.uni-hannover.de ================================================================================ Archive-Date: Sat, 13 Dec 1997 09:44:23 -0600 Sender: goathunter@MadGoat.com Date: Sat, 13 Dec 1997 09:44:12 -0600 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BEB34.21B52115.1@goat.process.com> Subject: RE: changed MX_DELIVER_DIGESTS.COM stenns@vw.tci.uni-hannover.de (Michael Stenns) writes: > >There might be many solutions to solve this, I did change the >MX_DELIVER_DIGESTS.COM command procedure. >The changed version bypasses VMS mail and uses MX_SITE_IN.EXE instead. >This allows complete control over the SMTP headers. >The generated headers are > Great minds think alike. ;-) Just three weeks ago, I modified MX-DIGEST to do essentially this same thing, except that I updated MX_MAKE_DIGEST to use the lines from the .INFO file to generate the headers. In MX V5.0, MX_SITE_IN will automatically add the Date: header if it's missing, simplifying stuff like this. The new MX-DIGEST.ZIP can be found on FTP.MADGOAT.COM in [.MX.CONTRIB]. It's been there since 24-NOV, but I hadn't announced it yet. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ MultiNet & TCPware: The Best TCP/IP for OpenVMS http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Sat, 13 Dec 1997 11:18:43 -0600 Date: Sat, 13 Dec 1997 09:18:56 -0700 From: Matt Madison Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BEB30.99E5960A.60@Praetorius.MadGoat.COM> Subject: RE: MX 5.0? Or alternative SMTP ports? >As with so many others, our VAXes are getting spam relayed through them >and I am under pressure here to "do something about it". Is MX 5.0 >really imminent or should I take up the other tack of getting MX to >listen on a non-standard port (by editing and rebuilding sources for >4.2) and having all mail intended for the VAXes go via our Unix relay >which has had a lot of anti-spam work put in? MX V5.0 really is imminent. Just working through the last couple of known bugs (which happen to be in the anti-spam stuff, btw) with the beta testers now. -Matt -- Matthew Madison MadGoat Software madison@madgoat.com ================================================================================ Archive-Date: Sat, 13 Dec 1997 16:46:53 -0600 Message-ID: <97Dec13.173257est.27781@fw.conference-board.org> From: "Ambrose, Joseph" Reply-To: MX-List@MadGoat.com To: "'MX-List@MadGoat.com'" Subject: RE: Undeliverable mail goes...where? Date: Sat, 13 Dec 1997 17:33:19 -0500 MIME-Version: 1.0 Content-Type: text/plain ..... either back to the person who sent it, or...... to the Administrator of the list ( if that's where it came from ) I should know.....I have 19 new "email errors" in a special folder right now.... Hope this helps. Joseph J. Ambrose The Conference board Network Administrator / DBA ambrose@conference-board.org > -----Original Message----- > From: Mark Tarka [SMTP:ichjsmt@earth.oscs.montana.edu] > Sent: Thursday, December 11, 1997 11:49 PM > To: ambrose@exchange.conference-board.org > Subject: Undeliverable mail goes...where? > > Clawing my way through the fog, I come to the realization that there > are a lot of people out there, subscribed to mailing lists, or lucky > to have been added to someone's distribution list, who clock out of > their accounts without notice to anyone outside their immediate > environment. > > Still the mail rolls in. > > The account's closed. > > Sending mail back appended to a "the Postmaster regrets to inform > you..." would necessarily add to the clutter on the net. > > Maybe I'm wrong, and everyone is being neat about their electronic > lives, and that's the reason why I see so few bounced mails that > I've sent to a group using a mail-distribution format coming > back at me. > > But I was wondering if some sites are configured to direct mail > addressed to accounts that no longer exist into the bit-bucket (if > that's the correct expression). > > Any comments? > > Mark (Clueless-in-Wonderland :-) ================================================================================ Archive-Date: Tue, 16 Dec 1997 09:30:52 -0600 Date: Tue, 16 Dec 1997 10:30:32 EST From: Irv Eisen Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: irv@ccstat.mc.duke.edu Message-ID: <009BED96.19D4B780.345@ccstat.mc.duke.edu> Subject: Using text file with MLF We use a text file to contain the addresses of a 1200 member mailing list. The addresses are extracted nightly in a batch job from a large active Ingres database, which contains quite a bit more information than just email addresses. We started this in a previous version of MX when MLF used text files. (Two other reasons I like the text file: it's easy to search with the VMS Search command and it's half the size of the binary version.) Occasionally something we do in MX or to the MLF agent causes the list to be converted to a binary file, to which MLF defaults for the addresses. In the meantime we continue to update the text file and people start reporting that they are not getting messages. Can we force the MLf agent to use the text file? What we will do if that cannot happen is check for the existence of and delete the binary version each time we update the list. We are using VAX/VMS 5.5-2, Digital TCPIP Services 4.0 and MX 4.1. Thanks, ================================================================ Irv Eisen, Systems Manager Cancer Center Information Systems Email: IRV@CCSTAT.MC.DUKE.EDU Duke University Medical Center DUMC Box 3958 Voice: (919) 681-5405 Durham, NC 27710 Fax : (919) 681-8028 ================================================================ ================================================================================ Archive-Date: Tue, 16 Dec 1997 11:40:08 -0600 Sender: smcneilly@bridgew.edu Date: Tue, 16 Dec 1997 12:42:13 EST From: Scott McNeilly Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BEDA8.7F5DE420.109@fred.bridgew.edu> Subject: RE: Using text file with MLF >From: Irv Eisen >We use a text file to contain the addresses of a 1200 member mailing list. >The addresses are extracted nightly in a batch job from a large active >Ingres database, which contains quite a bit more information than just >email addresses. We started this in a previous version of MX when MLF >used text files. (Two other reasons I like the text file: it's easy to >search with the VMS Search command and it's half the size of the binary >version.) >Occasionally something we do in MX or to the MLF agent causes the list to >be converted to a binary file, to which MLF defaults for the addresses. In >the meantime we continue to update the text file and people start reporting >that they are not getting messages. >Can we force the MLf agent to use the text file? What we will do if that >cannot happen is check for the existence of and delete the binary version >each time we update the list. Irv, I'm sorry that I do not know the answer to your question. But I would like to ask you a question, too. We extract addresses from our Human Resources system on a weekly basis to create mailing lists. But instead of using the resulting text file directly, we precede the addresses with an "ADD" or "REMOVE" command and let MLF update the mailing list (in whatever format it chooses. We don't care what that is.) Each week all the addresses that were created in the previous week are REMOVEd and the current batch of addresses is ADDed. My question to you is: Why bother to try to maintain a text file? Why not let MLF do it for you? You mention that it is easier to search a text file, but it is just as easy to search a binary file, though the output is not as pretty. If that's a problem, then a trivial DCL procedure could solve that, using $ MCP, REVIEW list /OUTPUT=somefile, $SEARCH somefile P1. As for the larger size of the binary file, I don't have a solution for that. But nowadays disk space is fairly cheap. -------------------------------------------------------------------- Scott Mc Neilly email: smcneilly@bridgew.edu Assistant Director Phone: 508-697-1236 Information Services FAX: 508-697-1774 Bridgewater State College Bridgewater, MA 02325 --------------------------------------------------------------------- ================================================================================ Archive-Date: Tue, 16 Dec 1997 16:29:48 -0600 Sender: goathunter@MadGoat.com Date: Tue, 16 Dec 1997 16:29:37 -0600 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BEDC8.43C8716C.37@goat.process.com> Subject: RE: Using text file with MLF Scott McNeilly writes: > >>From: Irv Eisen > >>Can we force the MLf agent to use the text file? What we will do if that >>cannot happen is check for the existence of and delete the binary version >>each time we update the list. > No, you can't. Newer versions of MX prefer the binary format. >I'm sorry that I do not know the answer to your question. But I would like to >ask you a question, too. We extract addresses from our Human Resources system >on a weekly basis to create mailing lists. But instead of using the resulting >text file directly, we precede the addresses with an "ADD" or "REMOVE" command >and let MLF update the mailing list (in whatever format it chooses. We don't >care what that is.) Each week all the addresses that were created in the >previous week are REMOVEd and the current batch of addresses is ADDed. If you need to remove all the subscribers, you can simply things by simply deleting the .MAILING_LIST file and then mailing the ADD commands to the list processor. >My question to you is: Why bother to try to maintain a text file? Why not let >MLF do it for you? You mention that it is easier to search a text file, but >it is just as easy to search a binary file, though the output is not as pretty. >If that's a problem, then a trivial DCL procedure could solve that, using >$ MCP, REVIEW list /OUTPUT=somefile, $SEARCH somefile P1. As for the larger >size of the binary file, I don't have a solution for that. But nowadays >disk space is fairly cheap. > What he said. And the size of the binary file is a little smaller in MX V5.0.... Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ MultiNet & TCPware: The Best TCP/IP for OpenVMS http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Wed, 17 Dec 1997 04:53:02 -0600 Message-ID: Date: Wed, 17 Dec 1997 11:10:59 +0200 From: Noel Grandin Reply-To: MX-List@MadGoat.com To: mx-list@madgoat.com Subject: Q: envelope addresses Hi I'm running a setup where I route lots of users to a single VMS mail file, and then run a program that reads that file and passes the messages on. Unfortunately, some messages (notably from listserver's) do not have the recipient in the "To:" header - it's only present in the SMTP envelope. Is there any way I can get MX to put the recipient from the envelope into the VMS-MAIL "To:" header ? (I've even got the source, and got as far as [.local]deliver.b32, but am struggling to work out exactly where to make the change) Thanks, Noel ================================================================================ Archive-Date: Thu, 18 Dec 1997 07:33:52 -0600 Date: Thu, 18 Dec 1997 14:00:45 MET-1MET DST From: "Michael Lemke, Sternwarte Bamberg, Phone: +49-951-9522216" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: ai26@sternwarte.uni-erlangen.de Message-ID: <009BEF45.CCDBCCDC.1400@sternwarte.uni-erlangen.de> Subject: Blacklisted... So they did it! Due to MX not being able to block SMTP relays and recent spam attacks we've been blacklisted by some sites. Does anyone have any suggestions how to get off these lists? Some www sites aren't accessible and mail to certain addresses can't be delivered anymore. I know it must be due to blacklists as pings and traceroutes from another machine get through while those done at the same time from the Alphas don't. It is not a network issue. Thanks for any ideas, Michael -- Michael Lemke Sternwarte Bamberg, University of Erlangen-Nürnberg, Germany (lemke@sternwarte.uni-erlangen.de or michael@astro.as.utexas.edu) ================================================================================ Archive-Date: Thu, 18 Dec 1997 11:07:29 -0600 Sender: tjgp@blackwell.co.uk Date: Thu, 18 Dec 1997 17:07:54 BST From: John Powers Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: john.powers@blackwell.co.uk Message-ID: <009BEF5F.F17722C0.450@blackwell.co.uk> Subject: "To:" headers going wrong.. We are having a strange problem with our mail system. I'm not sure if its an MX problem or a Microsoft exchange problem, or something to do with the way we are interfacing them together, so I am trying both mailing lists in the hope that somebody will have seen this before. We use MX 4.2 as our mail hub on a VAX-VMS system V5.5-2 (going to 7.1 rsn), and various of our managerial staff read their mail with Microsoft Exchange version 4.0.837.0. Any mail that comes through MX directly to our VMSmail users is fine, and any mail that goes only through the Exchange server works fine as well. However. If anybody from the outside world mails in to somebody with an Exchange account, the headers go awry in the following way. If an outsider mails to 'recipient1@blackwell.co.uk' and cc's it to 'cc1@blackwell.co.uk', 'cc2@blackwell.co.uk' and 'cc3@blackwell.co.uk' then: 'recipient1' receives the mail quite correctly, but the others get it wrong. e.g. 'cc2' receives a mail message with headers: To: cc2 Cc: cc1;cc2;cc3 The "To:" gets eaten and replaced with the name of the person who is receiving this copy, as if 'cc2' were the intended main recipient. The original recipient, 'recipient1' gets lost, so 'cc2' has no idea who the message was originally written to (unless they can deduce it from the contents). What then happens is that 'cc2' decides the message is of relevance to 'recipient1' and forwards a copy to them, who now gets 2 copies of it. All our managers are now duplicating loads of mail to each other. Of course this becomes a high priority problem as all our top level managers and directors all insist on using Exchange, so I am in need of an answer, but am completely stuck. Does anybody have any idea what's going on here? Surely somebody in the world is using the same combination as us. Many thanks for any help you can provide. John. ----------------------------------------------------------------------------- John Powers - Blackwell's, Oxford - - "fee issuing thirty mails" (anag.) john.powers@blackwell.co.uk (Internet) Blackwells Booksellers - Visit our PSI%234284400179::TJGP (PSImail) home page: http://www.blackwell.co.uk/ ----------------------------------------------------------------------------- ================================================================================ Archive-Date: Thu, 18 Dec 1997 11:43:53 -0600 Date: Thu, 18 Dec 1997 12:43:58 -0500 From: "Brian Tillman, x8425" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BEF3B.126E9E60.2@swdev.si.com> Subject: RE: "To:" headers going wrong.. >However. If anybody from the outside world mails in to somebody >with an Exchange account, the headers go awry in the following way. > >If an outsider mails to 'recipient1@blackwell.co.uk' and cc's it to >'cc1@blackwell.co.uk', 'cc2@blackwell.co.uk' and 'cc3@blackwell.co.uk' >then: > >'recipient1' receives the mail quite correctly, but >the others get it wrong. e.g. Do you have VMS Mail forwarding set up for any of cc1, cc2, or cc3? If so, it's an Exchange issue. If this is the case, let me know and I'll tell you what's happening. -- 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, 18 Dec 1997 12:07:04 -0600 Sender: tjgp@blackwell.co.uk Date: Thu, 18 Dec 1997 18:07:25 BST From: John Powers Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: TILLMAN_BRIAN@SI.COM, john.powers@blackwell.co.uk Message-ID: <009BEF68.425BC760.147@blackwell.co.uk> Subject: RE: "To:" headers going wrong.. >>However. If anybody from the outside world mails in to somebody >>with an Exchange account, the headers go awry in the following way. >> >>If an outsider mails to 'recipient1@blackwell.co.uk' and cc's it to >>'cc1@blackwell.co.uk', 'cc2@blackwell.co.uk' and 'cc3@blackwell.co.uk' >>then: >> >>'recipient1' receives the mail quite correctly, but >>the others get it wrong. e.g. > >Do you have VMS Mail forwarding set up for any of cc1, cc2, or cc3? If so, it's >an Exchange issue. If this is the case, let me know and I'll tell you what's >happening. Yes we do have a rather baroque mail forwarding method in place. Because we wish to give all our users a uniform look and feel to the outside world, all our Exchange users have in VMSmail forwarding addresses. which are rewritten. e.g. A user such as Martin Powell, has VMS login name of MMP, and an enquiry such as: MAIL> SHOW FORWARD/USER=MMP - gives: MMP has mail forwarded to MX%"martin.powell@exchange1.blackwell.co.uk" MCP> SHOW PATH - command output includes the line: Domain="exchange1.blackwell.co.uk", Path=SMTP, Route="194.130.176.134" And we use ADDRESS_REWRITER.EXE from MX_CONTRIB which reads the file MX_DIR:ADDRESS_TRANSLATIONS.DAT, which contains the line: mmp@blackwell.co.uk martin.powell@blackwell.co.uk The reason for this route is so that all our users, whether using VMSmail, Exchange, or our Unix-heads on Pine, all look to the outside world like 'firstname.secondname@blackwell.co.uk' Is this what's causing our problems? Is there a better way? Cheers. John. ----------------------------------------------------------------------------- John Powers - Blackwell's, Oxford - - "fee issuing thirty mails" (anag.) john.powers@blackwell.co.uk (Internet) Blackwells Booksellers - Visit our PSI%234284400179::TJGP (PSImail) home page: http://www.blackwell.co.uk/ ----------------------------------------------------------------------------- ================================================================================ Archive-Date: Thu, 18 Dec 1997 12:24:40 -0600 Sender: goathunter@MadGoat.com Date: Thu, 18 Dec 1997 12:24:27 -0600 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BEF38.587E45C0.1@goat.process.com> Subject: RE: "To:" headers going wrong.. John Powers writes: > >e.g. A user such as Martin Powell, has VMS login name of MMP, and an > enquiry such as: > MAIL> SHOW FORWARD/USER=MMP - gives: > MMP has mail forwarded to MX%"martin.powell@exchange1.blackwell.co.uk" > > MCP> SHOW PATH - command output includes the line: > Domain="exchange1.blackwell.co.uk", Path=SMTP, Route="194.130.176.134" > > And we use ADDRESS_REWRITER.EXE from MX_CONTRIB which reads the file > MX_DIR:ADDRESS_TRANSLATIONS.DAT, which contains the line: > mmp@blackwell.co.uk martin.powell@blackwell.co.uk > >The reason for this route is so that all our users, whether using VMSmail, >Exchange, or our Unix-heads on Pine, all look to the outside world like >'firstname.secondname@blackwell.co.uk' > >Is this what's causing our problems? Is there a better way? > Maybe, because that will cause things to pass through MX_MAILSHR again on there way out. Why not just put the real addresses in the ADDRESS_REWRITER file? martin.powell@exchange1.blackwell.co.uk martin.powell@blackwell.co.uk mmp@blackwell.co.uk martin.powell@blackwell.co.uk You can have multiple lines like that. Incoming mail will get delivered to which match is made first on the right-hand side. Mail coming from either system through MX will get rewritten as martin.powell@blackwell.co.uk. And you avoid sending stuff through MX Local to be processed by MX_MAILSHR again. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ MultiNet & TCPware: The Best TCP/IP for OpenVMS http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Thu, 18 Dec 1997 12:52:21 -0600 Date: Thu, 18 Dec 1997 13:52:08 -0500 From: "Brian Tillman, x8425" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009BEF44.98802060.13@swdev.si.com> Subject: RE: "To:" headers going wrong.. >Maybe, because that will cause things to pass through MX_MAILSHR again >on there way out. This is probably why Exchange is presenting what it does. cc:Mail acts the same way. MX is adding Resent-xxx headers and Exchange (and cc:Mail) are using those and not the original headers. Since the RFCs state that interpretation of the Resent-xxx headers is up to the individual mail agents, whether or not I would contend that it is incorrect behavior (and I do) is immaterial. I'd change MX to leave out the Resent-xxx headers if I could, but I simply do not understand the examples enough to modify it. I've read both the Blis and the C examples and it just makes no sense. Now, if the examples were in Fortran, I'd have it made. -- 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: Sat, 20 Dec 1997 23:17:02 -0600 Sender: rharwood@Basix.COM Date: Sat, 20 Dec 1997 22:16:46 MST From: Ray Harwood -- Data Basix Reply-To: MX-List@MadGoat.com To: MX-LIST@MADGOAT.COM CC: rharwood@Basix.COM Message-ID: <009BF11D.6C406156.1@Basix.COM> Subject: Request: a /NOATTACHMENT qualifier for mailing lists Just a minor beef that has surfaced on my Muscular Dystrophy mailing list. Some over-joyous folks have been attempting to send pictures over the mailing list... it sure would be nice to be able to dis-allow attachments on lists with a /NOATTACHMENT qualifier! Just a minor suggestion for the back burner... thanks for listening, and best of holidays to everyone! Ray ----- Ray Harwood | Data Basix | Voice: (520)885-1512 | PO Box 18324 | FAX: (520)721-7240 | Tucson, AZ 85731 | RHarwood@Basix.COM | http://Basix.COM/ | ================================================================================ Archive-Date: Mon, 22 Dec 1997 09:37:38 -0600 Sender: tjgp@blackwell.co.uk Date: Mon, 22 Dec 1997 15:38:08 BST From: John Powers Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: john.powers@blackwell.co.uk Message-ID: <009BF278.116E72C0.422@blackwell.co.uk> Subject: RE: "To:" headers going wrong.. [solved!] Thanks to Brian Tillman and Hunter for their help. We now have this resolved. Both techniques fixed our problem From Brian Tillman.. > What we do here is simply have: > > MAIL> set forward/user=tillman_brian mx%"""tillman_brian@smtpgwy.si.com""" > > We don't have any special paths or rewrite rules then and wveryone looks like > lastname_firstname@si.com. Hunter's solution.. > > Why not just put the real addresses in the ADDRESS_REWRITER file? > > martin.powell@exchange1.blackwell.co.uk martin.powell@blackwell.co.uk > mmp@blackwell.co.uk martin.powell@blackwell.co.uk > > You can have multiple lines like that. Incoming mail will get > delivered to which match is made first on the right-hand side. Mail > coming from either system through MX will get rewritten as > martin.powell@blackwell.co.uk. And you avoid sending stuff through MX > Local to be processed by MX_MAILSHR again. > I chose the 2nd of these two solutions as it is much easier for us to implement here, which was why we used it in the first place. The file MX_DIR:ADDRESS_TRANSLATIONS.DAT is recreated from scratch every night from our internal on-line staff directory, so is always up to date. The use of the address rewriter simplifies this considerably. This was very educational. I did not realize it was possible to have multiple lines in the rewrite file. This makes many other contortions that we go through unnecessary. Thanks for the hint. --John ----------------------------------------------------------------------------- John Powers - Blackwell's, Oxford - - "fee issuing thirty mails" (anag.) john.powers@blackwell.co.uk (Internet) Blackwells Booksellers - Visit our PSI%234284400179::TJGP (PSImail) home page: http://www.blackwell.co.uk/ ----------------------------------------------------------------------------- ================================================================================ Archive-Date: Mon, 29 Dec 1997 07:16:36 -0600 Message-ID: <34A7A1F2.448D@grenoble.sema.fr> Date: Mon, 29 Dec 1997 14:13:22 +0100 From: Hubert PERES Reply-To: MX-List@MadGoat.com MIME-Version: 1.0 To: mx-list@wkuvx1.wku.edu Subject: MIME problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello, I'm using MX 4.2, very fine. I have a problem with some kinds of attachments. In some cases, the boundary is incorrectly interpreted, so the mail shows nothing : no attachment, and even no text at all. This happens when the sender uses a mailer named WorldTalk (I don't know what it is, it seems to use a boundary a bit complex, but correct I think). For instance, the attached file uses as a boundary : ------ =_0_MIME_Boundary_453.349facce.imwmabx0.GATESMTP but in the mail, the definition of the boundary is : Content-Type: multipart/mixed; boundary="---- =_0_MIME_Boundary_453.349facce.imwmabx0.GATESMTP" So someone puts a Return whih is the problem indeed. It is not SMTP server, and not SMTP router : I checked that. So it is MX SMTP I think which puts an incorrect Return in the middle of the boundary. And then the attached file is not shown as an attachment. Got an idea ? Thank you, -- "Fast, Cheap, Secure. Pick two." Hubert PERES, Sema Group Centre de Grenoble (33) 4 76 41 47 23 ================================================================================ Archive-Date: Mon, 29 Dec 1997 17:22:39 -0600 Sender: goathunter@MadGoat.com Date: Mon, 29 Dec 1997 17:22:29 -0600 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: Hubert.Peres@grenoble.sema.fr, MadGoat-Bugs@MadGoat.com Message-ID: <009BF806.CDAB0F3C.13@goat.process.com> Subject: RE: MIME problem Hubert PERES writes: > >This happens when the sender uses a mailer named WorldTalk (I don't know >what it is, it seems to use a boundary a bit complex, but correct I >think). > >For instance, the attached file uses as a boundary : >------ =_0_MIME_Boundary_453.349facce.imwmabx0.GATESMTP > >but in the mail, the definition of the boundary is : > >Content-Type: multipart/mixed; boundary="---- > =_0_MIME_Boundary_453.349facce.imwmabx0.GATESMTP" > >So someone puts a Return whih is the problem indeed. > Yes, MX (Local and/or SMTP) does that when it reassembles the headers. Because that header is longer than 80 characters, MX Local tries to wrap it at a word boundary, and because the MIME boundary includes a space, that's where the wrap occurs. IMO, the generated boundary shouldn't have a space in it, but that's legal, according to the MIME RFC. >Got an idea ? >Thank you, > We'll do something about this in MX V5.1. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ MultiNet & TCPware: The Best TCP/IP for OpenVMS http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Tue, 30 Dec 1997 15:46:46 -0600 From: "Patrick Cox" To: mx-list@madgoat.com Date: Tue, 30 Dec 1997 17:50:16 AST Subject: MX 5.0 ?? Reply-To: MX-List@MadGoat.com Message-ID: <337D4C35C05@es.nsac.ns.ca> Is it ready yet? We missed Christmas how about a New Year's gift. TTYL, ''' Information Technology Patrick Cox (o o) The Resources Corporate Services Unit ---------------oOO--(_)--OOo------------------------------------------ Interactive:(902)893-6233