Archive-Date: Mon, 1 Mar 1999 21:38:27 -0800 Date: Tue, 02 Mar 1999 16:35:25 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: <009D4853.2343BBE0.69@stvincents.com.au> Subject: rewrite DECnet address Some of our users prefer VMSmail for various reasons, including myself. We send mail to MX_NODE::MX%"{address}", where MX_NODE is a logical with value the mail server node name. Outgoing mail sent this way has a return address of '{node}::{username}'@our.domain I want this to appear as {username}@our.domain I've tried various rewrite rules, but none seems to match any of the users. My latest attempt is: Rewrite "<\'{node}::{user}\'@{host}>" => "<{user}@{host}>" Which does not work (see my return address). I've also tried: Rewrite "<{node}::{user}@{host}>" => "<{user}@{host}>" Rewrite "<'{node}::{user}'@{host}>" => "<{user}@{host}>" Hints please? -- dTibdixious@stvincents.com.au Server Technical Support ================================================================================ Archive-Date: Tue, 2 Mar 1999 00:38:08 -0800 Message-ID: <001001be6488$2aa68ac0$cb2300c0@tool201> From: "Isid" Reply-To: MX-List@MadGoat.com To: , Subject: Re: rewrite DECnet address Date: Tue, 2 Mar 1999 09:38:47 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Im using the opposite rewrite rule (from decnet address to internet) as Rewrite "<{user}@vmsnode>" => "<""vmsnode{user}""@domain>" So try to change the order and see if it works Jose Luis Lopez Jacob Madrid -----Original Message----- From: Daiajo Tibdixious MACS <"svs::svist070"@stvincents.COM.AU> To: MX-List@LISTS.WKU.EDU Date: martes 2 de marzo de 1999 6:35 Subject: rewrite DECnet address >Some of our users prefer VMSmail for various reasons, including myself. > >We send mail to MX_NODE::MX%"{address}", where MX_NODE is a logical with value >the mail server node name. > >Outgoing mail sent this way has a return address of > >'{node}::{username}'@our.domain > >I want this to appear as {username}@our.domain > >I've tried various rewrite rules, but none seems to match any of the users. >My latest attempt is: > > Rewrite "<\'{node}::{user}\'@{host}>" => "<{user}@{host}>" > >Which does not work (see my return address). > >I've also tried: > Rewrite "<{node}::{user}@{host}>" => "<{user}@{host}>" > Rewrite "<'{node}::{user}'@{host}>" => "<{user}@{host}>" > >Hints please? >-- >dTibdixious@stvincents.com.au Server Technical Support > ================================================================================ Archive-Date: Tue, 2 Mar 1999 00:38:15 -0800 Message-ID: <001001be6488$2aa68ac0$cb2300c0@tool201> From: "Isid" Reply-To: MX-List@MadGoat.com To: , Subject: Re: rewrite DECnet address Date: Tue, 2 Mar 1999 09:38:47 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Im using the opposite rewrite rule (from decnet address to internet) as Rewrite "<{user}@vmsnode>" => "<""vmsnode{user}""@domain>" So try to change the order and see if it works Jose Luis Lopez Jacob Madrid -----Original Message----- From: Daiajo Tibdixious MACS <"svs::svist070"@stvincents.COM.AU> To: MX-List@LISTS.WKU.EDU Date: martes 2 de marzo de 1999 6:35 Subject: rewrite DECnet address >Some of our users prefer VMSmail for various reasons, including myself. > >We send mail to MX_NODE::MX%"{address}", where MX_NODE is a logical with value >the mail server node name. > >Outgoing mail sent this way has a return address of > >'{node}::{username}'@our.domain > >I want this to appear as {username}@our.domain > >I've tried various rewrite rules, but none seems to match any of the users. >My latest attempt is: > > Rewrite "<\'{node}::{user}\'@{host}>" => "<{user}@{host}>" > >Which does not work (see my return address). > >I've also tried: > Rewrite "<{node}::{user}@{host}>" => "<{user}@{host}>" > Rewrite "<'{node}::{user}'@{host}>" => "<{user}@{host}>" > >Hints please? >-- >dTibdixious@stvincents.com.au Server Technical Support > ================================================================================ Archive-Date: Tue, 2 Mar 1999 07:17:57 -0800 Message-ID: <0e7001be64bf$b339e6c0$d6001c7e@gr-355538.si.com> From: "Brian Tillman" Reply-To: MX-List@MadGoat.com To: Subject: Re: rewrite DECnet address Date: Tue, 2 Mar 1999 10:16:51 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit >We send mail to MX_NODE::MX%"{address}", where MX_NODE is a logical with value >the mail server node name. If you were to run MX over DECnet on the node from which you're sending mail, you could have what you want without any rewrite rules. Brian Tillman Internet: tillman_brian at si.com Smiths Industries, Inc. tillman at swdev.si.com 3290 Patterson Ave. SE, MS Addresses modified to prevent Grand Rapids, MI 49512-1991 SPAM. Replace "at" with "@" This opinion doesn't represent that of my company ================================================================================ Archive-Date: Wed, 3 Mar 1999 14:31:07 -0800 Message-ID: <36DDB6D6.E7ABF9B@ccr.dsi.uanl.mx> Date: Wed, 03 Mar 1999 16:25:26 -0600 From: "Miguel Angel Avila Vázquez" Reply-To: MX-List@MadGoat.com MIME-Version: 1.0 To: MX-LIST@madgoat.com Subject: No recipient when sending messages Content-Type: multipart/mixed; boundary="------------89F87A628362E6215E5C25E9" Este es un mensaje multipartes en formato MIME. --------------89F87A628362E6215E5C25E9 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit When I send a message to another user with diferent UIC, there´s no recipient when I check the message queue on MX. MX version id is: MX V4.2 VAX. What could I do to solve this problem?. Any suggestion will be appreciate, thanks. --------------89F87A628362E6215E5C25E9 Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf" Content-Transfer-Encoding: 7bit Content-Description: Tarjeta de Miguel Angel Avila Vázquez Content-Disposition: attachment; filename="vcard.vcf" begin: vcard fn: Miguel Angel Avila Vázquez n: ;Miguel Angel Avila Vázquez org: U.A.N.L. email;internet: miguel@ccr.dsi.uanl.mx title: Administrador de OpenVMS x-mozilla-cpt: ;-1 x-mozilla-html: FALSE version: 2.1 end: vcard --------------89F87A628362E6215E5C25E9-- ================================================================================ Archive-Date: Wed, 3 Mar 1999 15:56:00 -0800 Date: Wed, 03 Mar 1999 18:46:14 EST-10EST From: Daiajo Tibdixious MACS <"svs::svist070"@stvincents.COM.AU> Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009D492E.94180B60.25@stvincents.com.au> Subject: Re: rewrite DECnet address Tue, 2 Mar 1999 "Brian Tillman" >>We send mail to MX_NODE::MX%"{address}", where MX_NODE is a logical with >If you were to run MX over DECnet on the node from which you're sending >mail, you could have what you want without any rewrite rules. Good idea. I did this and it did the job nicely. Had to change all of the distribution lists, but it worked out okay. -- dTibdixious@stvincents.com.au Server Technical Support ================================================================================ Archive-Date: Thu, 4 Mar 1999 01:22:11 -0800 From: eplan@kapsch.net (Peter LANGSTOEGER) Subject: Re: No recipient when sending messages Date: 4 Mar 1999 10:16:23 +0100 Message-ID: <36de4f67.0@nevada.kapsch.co.at> Reply-To: MX-List@MadGoat.com To: MX-List@LISTS.WKU.EDU In article <36DDB6D6.E7ABF9B@ccr.dsi.uanl.mx>, "Miguel Angel Avila Vázquez" writes: >When I send a message to another user with diferent UIC, there´s no >recipient when I check the >message queue on MX. >MX version id is: MX V4.2 VAX. >What could I do to solve this problem?. > >Any suggestion will be appreciate, thanks. Check the file protections of the MX files. We had a lot of silly effects, when we accidently closed world access to MX... ------------------------------------------------------------------------ Peter "EPLAN" LANGSTOEGER Tel. +43 1 81111-2651 Network and OpenVMS system manager Fax. +43 1 81111-888 FBFV/Information Services 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" "VMS is today what Microsoft wants Windows NT V8.0 to be!" Compaq, 22-Sep-1998 ================================================================================ Archive-Date: Sun, 7 Mar 1999 21:11:39 -0800 Message-ID: <00bd01be6921$eaa6f4c0$de2c67cb@wotan.stmarks.pp.catholic.edu.au> From: "Geoff Roberts" Reply-To: MX-List@MadGoat.com To: Subject: Selective disabling of relaying. Date: Mon, 8 Mar 1999 15:39:58 +1030 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi all, Got a (probably) simple problem. We were put in the ORBS list some time ago. At the time, we were running 4.2, so there wasn't a lot I could do about, (apart from hoping ORBS would GO AWAY) Well, they did, unfortunately, they're back, and we are still listed, so I set the server up (or so I thought) to refuse to relay from non .au domains. (I have POP3/SMTP users that need access .au wide, I just can't/won't kill relaying totally.) I don't need the system to be "secured" to the level these guys seem to expect, I just want to make it good enough to make them happy and take us off the blasted list. We've never been used as a spamrelay, and we get very little spam ourselves. Grrr.. Anyway, ORBS retested us with the following format and it got relayed. Considering that it's not an .au address I'm sorta surprised. I suspect I'm doing something wrong/not doing something, but what? From MAILER-DAEMON@wwwhost.manawatu.net.nz Mon Mar 8 15:15:43 1999 Received: from mail2.manawatu.net.nz (postmaster@mail2.manawatu.net.nz [202.36.148.21]) by wwwhost.manawatu.net.nz (8.9.2/8.9.2) with ESMTP id PAA10229 for ; Mon, 8 Mar 1999 15:15:43 +1300 (NZDT) Received: from MAIL.STMARKS.PP.CATHOLIC.EDU.AU (mail.stmarks.pp.catholic.edu.au [203.103.44.195]) by mail2.manawatu.net.nz (8.9.2/8.9.3) with ESMTP id PAA29897 for ; Mon, 8 Mar 1999 15:15:34 +1300 (NZDT) X-Remote-IP: 203.103.44.195 Date: Mon, 8 Mar 1999 15:15:34 +1300 (NZDT) Received: from relaytest.orbs.org (202.36.148.5) by MAIL.STMARKS.PP.CATHOLIC.EDU.AU (MX V5.1-X Vn8j) with SMTP for ; Mon, 8 Mar 1999 12:45:28 +0930 To: orbs-relaytest@manawatu.co.nz X-MX-Warning: Warning -- Invalid "From" header. From: null@mail2.manawatu.net.nz X-Token: ghunwhawrudqhvkb X-Envelope-Sender: Message-ID: <203.103.44.195@orbs.org> Subject: ORBS Relay Test - 203.103.44.195 This program (re)tests for open relays. Open relays are automatically added to the ORBS Open Relay Database (see http://www.orbs.org/ for details). There are different 5 tests applied per IP address. Do not use the above addresses to contact me - use admin@orbs.org. Help on securing relays can be found at http://maps.vix.com/tsi/ X-Token: ghunwhawrudqhvkb Here's my MX configuration. What did I do wrong/not do right? Configuration file: MX_DEVICE:[MX]MX_CONFIG.MXCFG;9 MX version id is: MX V5.1-X Domain-to-path mappings: Domain="MAIL.STMARKS.PP.CATHOLIC.EDU.AU", Path=Local Domain="FTP.STMARKS.PP.CATHOLIC.EDU.AU", Path=Local Domain="WWW.STMARKS.PP.CATHOLIC.EDU.AU", Path=Local Domain="STMARKS.PP.CATHOLIC.EDU.AU", Path=Local Domain="[203.103.44.195]", Path=Local Domain="STMARKS", Path=Local Domain="MAIL", Path=Local Domain=".", Path=Local Domain="*.BITNET", Path=SMTP, Route="cunyvm.cuny.edu" Domain="*.UUCP", Path=SMTP, Route="uunet.uu.net" Domain="*", Path=SMTP SMTP agent settings: Retry interval: 0 00:30:00.00 Maximum number of retries: 96 Number of DNS failure retries: 12 Accounting: enabled Default router: (none) SMTP server settings: Allow VRFY commands: enabled Act as SMTP relay for any host: disabled [SHOW LOCAL_DOMAINS lists hosts] Validate sender's domain name: disabled Realtime Blackhole List check: disabled LOCAL agent settings: DECnet delivery retry interval: 0 00:30:00.00 Maximum number of retries: 96 Accounting disabled. Multiple VMS Mail From: addresses allowed. Local delivery errors are not CC'ed to local Postmaster. Incoming quoted-printable MIME messages are decoded. EXQUOTA privilege is enabled during local deliveries. Top headers: FROM,SENDER,TO,RESENT_TO,CC,RESENT_CC,BCC,RESENT_BCC,MESSAGE_ID, RESENT_MESSAGE_ID,IN_REPLY_TO,REFERENCES,KEYWORDS,SUBJECT, ENCRYPTED,DATE,REPLY_TO,RECEIVED,RESENT_REPLY_TO,RESENT_FROM, RESENT_SENDER,RESENT_DATE,RETURN_PATH,OTHER Bottom headers: (none) ROUTER agent settings: Accounting: disabled Automatic percent-hack handling: enabled Sender header for outgoing VMS Mail messages: included if necessary JNET agent settings: Automatic percent-hack handling: enabled BSMTP replies: disabled Accounting: disabled Lenient about gatewaying mail: no No mailer username set. DECnet_SMTP agent settings: Retry interval: 0 00:30:00.00 Maximum number of retries: 96 Accounting disabled. SITE agent settings: Retry interval: 0 00:30:00.00 Maximum number of retries: 96 X25_SMTP agent settings: Retry interval: 0 00:30:00.00 Maximum number of retries: 96 Accounting disabled. MLF agent settings: Maximum recipients per message: NONE (no limit) Days of week to delay file server files: Monday,Tuesday,Wednesday,Thursday,Friday,Saturday,Sunday Local domain patterns for SMTP relay checks: *.AU No inside networks/hosts defined. ================================================================================ Archive-Date: Sun, 7 Mar 1999 23:56:09 -0800 Date: Mon, 8 Mar 1999 09:58:13 +0200 From: Esa Laitinen Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: laitinen@juhani.decus.fi Message-ID: <009D4CD2.A512C6B0.2@juhani.decus.fi> Subject: RE: Selective disabling of relaying. >Well, they did, unfortunately, they're back, and we are still listed, so I >set the server up (or so I thought) to refuse to relay from non .au domains. Well, this is a matter of opinion. IMHO orbs is doing a valuable service. >(I have POP3/SMTP users that need access .au wide, I just can't/won't kill >relaying totally.) Normal way of doing this would be to have the users to use their ISPs smtp server for relaying, and then you wouldn't have any problems. This is how we operate. Thing is that you won't kill the relaying, not that you cannot. >We've never been used as a spamrelay, and we get very little spam ourselves. This is only a matter of time, so it is good thing that you'll get the problem fixed before anybody else notices. Anyway, ORBS retested us with the following format and it got relayed. >Considering that it's not an .au address I'm sorta surprised. I suspect I'm >doing something wrong/not doing something, but what? Check out the 8.4 chapter in your MX Management Guide. It tells you why it got pass (HINT: return-path resolved as local, they used your ip-address). You'll get much better success by defining the subnets that are allowed relaying thru your server. The actual mcp command is: define inside_network_adderess 1.2.3.4 /netmask=255.255.255.0 /relay And after that ofcourse mcp reset all. Esa Laitinen If I cannot reply to your news or mail message with reply, you won't get my answer. http://www.decus.fi Why try to hide away from spam, why not fight http://www.iki.fi/laitinen it? http://www.mcs.com/~jcr/junkemaildeal.html ================================================================================ Archive-Date: Mon, 8 Mar 1999 01:02:32 -0800 Message-ID: <012101be6942$25515dc0$de2c67cb@wotan.stmarks.pp.catholic.edu.au> From: "Geoff Roberts" Reply-To: MX-List@MadGoat.com To: Subject: Re: Selective disabling of relaying. Date: Mon, 8 Mar 1999 19:30:41 +1030 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit -----Original Message----- From: Esa Laitinen To: MX-List@MadGoat.com Cc: laitinen@juhani.decus.fi Date: Monday, 8 March 1999 7:26 Subject: RE: Selective disabling of relaying. Hi Esa, Thanks for your response. >>Well, they did, unfortunately, they're back, and we are still listed, so I >>set the server up (or so I thought) to refuse to relay from non .au domains. >Well, this is a matter of opinion. IMHO orbs is doing a valuable service. I hadn't noticed. Like I said, we don't get much spam anyway, 5 or 6 a week at most (amongst 200+ users that's pretty minimal) I just wish they'd fix the problem at it's origin since 99.9% of all spam seems to originate in the USA. Seems that they expect the rest of the world to supply the solution for them by crippling their mail servers. Just my opinion. YMMV. I quite agree with your sig, actually. Don't hide, fight. ORBS is just another form of hiding. (IMHO) >>(I have POP3/SMTP users that need access .au wide, I just can't/won't kill relaying totally.) > >Normal way of doing this would be to have the users to use their ISPs smtp >server for relaying, and then you wouldn't have any problems. Sure. I have encouraged people to do this wherever possible, unfortunately, some of the users we are talking about are, ahem, religous academics with laptops, who are gallavanting all around the blasted country. Even more unfortunately, most of them are technologically challenged, so they have a laptop which has just one mail setup.. Ours. Usually they patch in to a lan at whatever school they are visiting, (could be anything, anywhere) and access our smtp and pop3. System works very well. They always get their mail, they don't have to tinker with settings. Everybody's happy. Then we got ORBSed. >This is how we operate. It won't work for us unfortunately. I tried this already. Repeatedly. But it means trying to get them to set mailbox names. They invariably get it hosed up. >Thing is that you won't kill the relaying, not that you cannot. Either/or. I can't because the headmaster would cut my throat for effectively disabling remote mail access for the travelling circus. >>We've never been used as a spamrelay, and we get very little spam ourselves. >This is only a matter of time, So I keep hearing. For at least a year now. Yes I know security via obscurity is flawed. >so it is good thing that you'll get the problem >fixed before anybody else notices. If I can do it without disabling things for my users, yes. Otherwise I'll just have to ignore ORBS and hope they go away again. Or the yanks finally do something about brain broken a---holes flooding the known universe with money making schemes. Yeah, right. >Anyway, ORBS retested us with the following format and it got relayed. > >>Considering that it's not an .au address I'm sorta surprised. I suspect I'm >>doing something wrong/not doing something, but what? > >Check out the 8.4 chapter in your MX Management Guide. It tells you why it got >pass (HINT: return-path resolved as local, they used your ip-address). Er, if you say so, but I'm not sure how to tell if they did. Might pull the audit files. I've read the section several times, but still not sure how to resolve this. I will cheerfully admit to being self taught about mail handling, TCP/IP etc. (Not to mention VMS itself, vaxen and computers in general) so wise guidance is gratefully accepted... > >You'll get much better success by defining the subnets that are allowed >relaying thru your server. Already thought of that, and I would if I knew what they were. Best I can do at the moment would be 203.*.*.* Like I said, they could be ANYWHERE in .au, (an area somewhat larger than Europe) All I want is to be able to reject relay for any msg that doesn't originate in .au. I can't even narrow it to catholic.edu.au as I have other staff users who could be on any one of a dozen or more isp's from home, add the fact that many of our schools don't have domain names of their own, but just ISP mailboxes, edu.au is nbg either because some state schools are in the same position, further, some of them change ISP's frequently, and many of them are on dialup connections and have dynamically assigned ip addresses anyway, so it's not as easy as it seems, I'd need an include list the size of the phone book. I'm open to suggestions here........ >The actual mcp command is: > >define inside_network_adderess 1.2.3.4 /netmask=255.255.255.0 /relay > >And after that of course mcp reset all. Yes. I know what the commands are, just the implementation is the headache..... Thanks again, Cheers Geoff Roberts Computer Systems Manager Saint Mark's College Port Pirie, South Australia. Email: geoffrob@stmarks.pp.catholic.edu.au ICQ #: 1970476 Phone: 61-8-8633-8834 Mobile: 61-411-623-978 Fax: 61-8-8633-0104 ================================================================================ Archive-Date: Tue, 9 Mar 1999 15:05:39 -0800 Sender: svist070@stvincents.COM.AU Date: Wed, 10 Mar 1999 10:07:15 EST From: Daiajo Tibdixious MACS Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: svist070@stvincents.com.au Message-ID: <009D4E66.3C91B48D.25@svs30.stvincents.com.au> Subject: SMTP_SERVER death, quota? All of our SMTP_SERVER processes are dying at different and random intervals. I recently put MX V4.2 with patches on an Alpha node, and SMTP_SERVER crashes more or less once a day. The debug log shows no errors, but it is most of the way thru a gigantic message at the time (web usage report from the firewall). The crash status is just access violation (%x0C). I suspect some quota is being exceeded, but which one? -- dTibdixious@stvincents.com.au Server Technical Support ================================================================================ Archive-Date: Wed, 10 Mar 1999 07:01:54 -0800 Message-ID: From: "Horn, James T" Reply-To: MX-List@MadGoat.com To: "'MX-List@MadGoat.com'" Subject: Problems with Local process (MX 4.2) Date: Wed, 10 Mar 1999 09:01:36 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" We recently upgraded from v6.2 to V7.1-2 of Openvms alpha and having problems with the local process. It will process the "job" but will not deliver it to the persons MAIL.MAI file and it will resend it. The msg_text files shows: Return-Path: > Received: by nell.shsu.edu (MX V4.2 AXP) id 83; Wed, 10 Mar 1999 08:21:36 EST Date: Wed, 10 Mar 1999 08:21:33 EST From: horn@nell.shsu.edu To: SYSTEM@NELL.SHSU.EDU Message-ID: <009D4E57.78C9A264.83@nell.shsu.edu > Subject: test Message Return-Path: > Received: by nell.shsu.edu (MX V4.2 AXP) id 94; Wed, 10 Mar 1999 08:15:58 EST Date: Wed, 10 Mar 1999 08:15:56 EST From: horn@nell.shsu.edu To: SYSTEM@NELL.SHSU.EDU Message-ID: <009D4E56.AFE65941.94@nell.shsu.edu > Subject: test Message And it will repeat this every time it resends it. The path information looks like this: Domain-to-path mappings: Domain="freya.shsu.edu", Path=Local Domain="[192.92.115.8]", Path=Local Domain="[192.92.115.4]", Path=Local Domain="[192.92.115.5]", Path=Local Domain="niord.shsu.edu", Path=Local Domain="nell.shsu.edu", Path=Local Domain="odin.shsu.edu", Path=Local Domain="nell", Path=Local Domain="*.BITNET", Path=SMTP, Route="cunyvm.cuny.edu" Domain="*.UUCP", Path=SMTP, Route="uunet.uu.net" Domain="*", Path=SMTP There is no forward for the SYSTEM account. ================================================================================ Archive-Date: Wed, 10 Mar 1999 09:35:44 -0800 Message-ID: <541C9C38F3F3D111A3230000F89CCCCCDE1253@issmsg1.iss.msfc.nasa.gov> From: "Porter, Linda" Reply-To: MX-List@MadGoat.com To: "'MX-List@MadGoat.com'" Subject: max_smtp_server_threads Date: Wed, 10 Mar 1999 11:35:03 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" I've tried to increase the number of smtp server thread processes to 128, but mx 5.1 stubbornly refuses to go above 64. (My big list is now at 48,000 subscribers, and we occasionally send two messages/day). I've edited mx_logicals.com, and the system logicals look okay, but I'm only getting 64 processes. What am I doing wrong? Thanks, Linda MX_LOGICALS.DAT file: MX_FLQ_NODE_NAME\/SYSTEM/EXEC\SSLAB MX_FLQ_DIR\/SYSTEM/EXEC\DISK3$:[MX042.QUEUE] MX_NODE_NAME\/SYSTEM/EXEC\sslab.msfc.nasa.gov MX_MLF_PGFLQUO\/SYSTEM/EXEC\96000 MX_SMTP_SERVER_THREADS\/SYSTEM/EXEC\128 MX_SMTP_MAX_RECIPIENTS_PER_SESSION\/SYSTEM/EXEC\50 MX_SMTP_IGNORE_PIPELINING\/SYSTEM/EXEC\TRUE MX_SMTP_LOCK_EXCLUSIONS\/SYSTEM/EXEC\MSFC.NASA.GOV MX_DSN_DISABLE_INITIAL_DELAY_NOTIFICATIONS\/SYSTEM/EXEC\TRUE MX_LOCAL_ALLOW_LONG_LINES\/SYSTEM/EXEC\TRUE defined system logicals (after MX starts): "MX_ALIAS_HELPLIB" = "MX_DIR:MX_ALIAS_HELPLIB" "MX_DEVICE" = "SSLAB$DKB0:" "MX_DIR" = "MX_DEVICE:[APPS.MX042]" "MX_DOC" = "MX_ROOT:[DOC]" "MX_DSN_DISABLE_INITIAL_DELAY_NOTIFICATIONS" = "TRUE" "MX_EXAMPLES_DIR" = "MX_ROOT:[EXAMPLES]" "MX_EXE" = "MX_ROOT:[ALPHA_EXE]" "MX_FLQ_DIR" = "DISK3$:[MX042.QUEUE]" "MX_FLQ_NODE_NAME" = "SSLAB" "MX_FLQ_SHR" = "MX_EXE:MX_FLQ_SHR" "MX_LOCAL_ALLOW_LONG_LINES" = "TRUE" "MX_LOCAL_DIR" = "MX_ROOT:[LOCAL]" "MX_LSV_DIR" = "MX_ROOT:[LSV]" "MX_MAILSHR" = "MX_EXE:MX_MAILSHR" "MX_MAILSHRP" = "MX_EXE:MX_MAILSHRP" "MX_MCP_HELPLIB" = "MX_DIR:MX_MCP_HELPLIB" "MX_MLF_DIR" = "MX_ROOT:[MLF]" "MX_MLF_PGFLQUO" = "96000" "MX_MLIST_DIR" = "MX_ROOT:[MLF.MAILING_LISTS]" "MX_MSG" = "MX_EXE:MX_MSG" "MX_NODE_NAME" = "sslab.msfc.nasa.gov" "MX_PROTOCOL_PREFIX" = "smtp%" "MX_REJMAN_HELPLIB" = "MX_DIR:MX_REJMAN_HELPLIB" "MX_ROOT" = "MX_DEVICE:[APPS.MX042.]" "MX_ROUTER_DIR" = "MX_ROOT:[ROUTER]" "MX_SHR" = "MX_EXE:MX_SHR" "MX_SITE_DOM_EXPANSION" = "MX_EXE:DOMAIN_EXPANSION" "MX_SMTP_DIR" = "MX_ROOT:[SMTP]" "MX_SMTP_IGNORE_PIPELINING" = "TRUE" "MX_SMTP_LOCK_DIR" = "MX_ROOT:[SMTP.LOCK]" "MX_SMTP_LOCK_EXCLUSIONS" = "MSFC.NASA.GOV" "MX_SMTP_MAX_RECIPIENTS_PER_SESSION" [super] = "50" "MX_SMTP_MAX_RECIPIENTS_PER_SESSION" [exec] = "50" "MX_SMTP_MSG" = "MX_EXE:MX_SMTP_MSG" "MX_SMTP_SERVER_THREADS" = "128" ============= Linda Porter Code ES94 Data Systems Branch NASA/Marshall Space Flight Center Huntsville AL 35812 (256)544-7588 (256)544-7128 (fax) linda.porter@msfc.nasa.gov http://science.nasa.gov/ -----Original Message----- From: Hunter Goatley [mailto:goathunter@MadGoat.com] Sent: Tuesday, August 25, 1998 2:42 PM To: MX-List@MadGoat.com Subject: RE: and yet more info on MLF terminating "Porter, Linda" writes: > >25-AUG-1998 11:51:03.14: MX MLF (pid 0000024E) starting >25-AUG-1998 11:51:53.04: MX MLF (pid 0000024E) exiting, status = 1C278034 > Which is: $ set message mx_msg $ write sys$output f$message(%x1C278034) %MX-F-MEMALLOC, error allocating memory from zone !AS $ >When it fails, the debug MLF log file (MX_MLF_LOG.LOG) has processed just >over 4500 entries (in my three tries, it failed on the 4540th, 4538th and >4534th entries, respectively.). The MLF processor can still automatically >handle new entries and signoff users, but it can't handle this mailing list. > >Have I maybe hit a quota limit somewhere? (not on the drive, there's plenty >of space there!) > Yes, you have. You might try defining the following logical to see if it helps: $ define/system/exec mx_mlf_pgflquo xxxxx I think that's in V4.2. If not, edit MX_EXE:MX_START.COM and specify a large page file quota for MLF. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www.madgoat.com/hunter.html ================================================================================ Archive-Date: Thu, 11 Mar 1999 09:33:51 -0800 Message-ID: <541C9C38F3F3D111A3230000F89CCCCCDE126F@issmsg1.iss.msfc.nasa.gov> From: "Porter, Linda" Reply-To: MX-List@MadGoat.com To: "'MX-List@MadGoat.com'" Subject: RE: max_smtp_server_threads Date: Thu, 11 Mar 1999 11:33:09 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" I reduced the server threads to 24, and increased the SMTP delivery agents to 128 using mx_config.com. Unfortunately, MX wouldn't create any more than 98 processes (MX_SMTP through MX_SMTP#98) at startup; I got a "duplicate process name" and the startup finished. This was the content of the mx_startup_info.dat file: 002ROUTER:*=8 003LOCAL:*=8 004SMTP:*=99 004SMTP_SERVER:* 005LSV: 005MLF:* I editted 004SMTP: to 128, and restarted. And, predictably, I again only got 98 SMTP delivery agent processes, and 30 "duplicate process name" messages: . . . %RUN-F-CREPRC, process creation failed -SYSTEM-F-DUPLNAM, duplicate name %RUN-F-CREPRC, process creation failed -SYSTEM-F-DUPLNAM, duplicate name %RUN-S-PROC_ID, identification of created process is 00000856 %RUN-S-PROC_ID, identification of created process is 00000857 Thanks, Linda ============= Linda Porter Code ES94 Data Systems Branch NASA/Marshall Space Flight Center Huntsville AL 35812 (256)544-7588 (256)544-7128 (fax) linda.porter@msfc.nasa.gov http://science.nasa.gov/ -----Original Message----- From: Matt Madison [mailto:madison@MadGoat.COM] Sent: Thursday, March 11, 1999 8:15 AM To: Linda.Porter@msfc.nasa.gov Subject: RE: max_smtp_server_threads >I've tried to increase the number of smtp server thread processes to 128, >but mx 5.1 stubbornly refuses to go above 64. (My big list is now at 48,000 >subscribers, and we occasionally send two messages/day). I've edited >mx_logicals.com, and the system logicals look okay, but I'm only getting 64 >processes. What am I doing wrong? MX_SMTP_SERVER_THREADS doesn't control a number of processes; it controls the number of simultaneous inbound SMTP connections the server will support. I wouldn't recommend setting it higher than 32. It sounds like you may be trying to control the number of _outbound_ SMTP delivery agents? To do that, you should use @MX_DIR:MXCONFIG.COM, select option 3, and answer 128 when it gets to the question about the number of SMTP delivery agents; then @SYS$STARTUP:MX_STARTUP SMTP should start them all. -Matt -- Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA madison@madgoat.com http://www.madgoat.com ================================================================================ Archive-Date: Thu, 11 Mar 1999 16:32:39 -0800 From: eplan@kapsch.net (Peter LANGSTOEGER) Subject: RE: max_smtp_server_threads Date: 12 Mar 1999 01:26:47 +0100 Message-ID: <36e85f47.0@nevada.kapsch.co.at> Reply-To: MX-List@MadGoat.com To: MX-List@LISTS.WKU.EDU In article <541C9C38F3F3D111A3230000F89CCCCCDE126F@issmsg1.iss.msfc.nasa.gov>, "Porter, Linda" writes: >I reduced the server threads to 24, and increased the SMTP delivery agents >to 128 using mx_config.com. Unfortunately, MX wouldn't create any more than >98 processes (MX_SMTP through MX_SMTP#98) at startup; I got a "duplicate >process name" and the startup finished. This was the content of the >mx_startup_info.dat file: > >002ROUTER:*=8 >003LOCAL:*=8 >004SMTP:*=99 >004SMTP_SERVER:* >005LSV: >005MLF:* > >I editted 004SMTP: to 128, and restarted. And, predictably, I again only got >98 SMTP delivery agent processes, and 30 "duplicate process name" messages: Try to change in MX_EXE:MX_START.COM the line $ IF NUM .GT. 0 .AND. NUM .LT. 99 to $ IF NUM .GT. 0 .AND. NUM .LT. 999 !or another reasonable value above 128 Good luck ------------------------------------------------------------------------ Peter "EPLAN" LANGSTOEGER Tel. +43 1 81111-2651 Network and OpenVMS system manager Fax. +43 1 81111-888 FBFV/Information Services 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" "VMS is today what Microsoft wants Windows NT V8.0 to be!" Compaq, 22-Sep-1998 ================================================================================ Archive-Date: Fri, 12 Mar 1999 08:17:47 -0800 Message-ID: <541C9C38F3F3D111A3230000F89CCCCCDE128E@issmsg1.iss.msfc.nasa.gov> From: "Porter, Linda" Reply-To: MX-List@MadGoat.com To: "'MX-List@MadGoat.com'" Subject: RE: max_smtp_server_threads Date: Fri, 12 Mar 1999 10:16:59 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Hoo, boy. All 128 SMTP server processes are now running. Unfortunately, an MCP STATUS doesn't list any SMTP delivery agent processes as running, although all 128 are shown under a $SHOW SYSTEM. The outbound smtp queue entries are being processed, so they're running. Log files are created, etc, so it's a display problem, I guess. here's the output from show status: status PID Process name Status Agent type -------- --------------- ------------------ ----------- 00000A3D MX Router Idle Router agent 00000A3E MX Router#2 Idle Router agent 00000A3F MX Router#3 Idle Router agent 00000A41 MX Router#4 Idle Router agent 00000A42 MX Router#5 Idle Router agent 00000A43 MX Router#6 Idle Router agent 00000A44 MX Router#7 Idle Router agent 00000A45 MX Router#8 Idle Router agent 00000A46 MX Local Idle Local delivery agent 00000A47 MX Local#2 Idle Local delivery agent 00000A48 MX Local#3 Idle Local delivery agent 00000A49 MX Local#4 Idle Local delivery agent 00000A4A MX Local#5 Idle Local delivery agent 00000A4B MX Local#6 Idle Local delivery agent 00000A4C MX Local#7 Idle Local delivery agent 00000A4D MX Local#8 Idle Local delivery agent 00000AD9 MX MLF Idle Mailing list/file server 00000AD8 MX SMTP Server Idle SMTP server (over TCP/IP) 00000A3C MX FLQ Manager Idle MX FLQ manager $SHOW SYSTEM $ sh system OpenVMS V7.1 on node SSLAB 11-MAR-1999 16:22:33.94 Uptime 2 03:54:58 Pid Process Name State Pri I/O CPU Page flts Pages 00000A3C MX FLQ Manager HIB 6 6461 0 00:00:01.09 153 140 00000A3D MX Router HIB 5 943 0 00:00:00.32 205 173 00000A3E MX Router#2 HIB 4 1004 0 00:00:00.31 251 184 00000A3F MX Router#3 HIB 4 831 0 00:00:00.27 254 184 00000A41 MX Router#4 HIB 4 848 0 00:00:00.27 205 184 00000A42 MX Router#5 HIB 4 803 0 00:00:00.28 221 172 00000A43 MX Router#6 HIB 4 839 0 00:00:00.23 222 184 00000A44 MX Router#7 HIB 4 789 0 00:00:00.22 221 176 00000A45 MX Router#8 HIB 4 799 0 00:00:00.21 221 168 00000A46 MX Local HIB 5 656 0 00:00:00.17 279 193 00000A47 MX Local#2 HIB 4 572 0 00:00:00.16 325 184 00000A48 MX Local#3 HIB 4 576 0 00:00:00.13 323 184 00000A49 MX Local#4 HIB 4 575 0 00:00:00.14 277 191 00000A4A MX Local#5 HIB 4 568 0 00:00:00.12 293 191 00000A4B MX Local#6 HIB 4 559 0 00:00:00.18 309 184 00000A4C MX Local#7 HIB 4 489 0 00:00:00.10 273 184 00000A4D MX Local#8 HIB 4 488 0 00:00:00.12 275 184 00000A4E MX SMTP HIB 4 1415 0 00:00:00.31 362 184 00000A4F MX SMTP#2 HIB 4 1014 0 00:00:00.32 254 184 00000A50 MX SMTP#3 HIB 4 627 0 00:00:00.17 231 183 00000A51 MX SMTP#4 HIB 4 1084 0 00:00:00.31 263 184 00000A52 MX SMTP#5 LEF 5 912 0 00:00:00.20 264 184 00000A53 MX SMTP#6 HIB 4 758 0 00:00:00.25 251 184 00000A54 MX SMTP#7 HIB 4 794 0 00:00:00.32 260 184 00000A55 MX SMTP#8 HIB 4 719 0 00:00:00.33 234 184 etc up to MX SMTP#128 Cheers, Linda ============= Linda Porter Code ES94 Data Systems Branch NASA/Marshall Space Flight Center Huntsville AL 35812 (256)544-7588 (256)544-7128 (fax) linda.porter@msfc.nasa.gov http://science.nasa.gov/ ================================================================================ Archive-Date: Fri, 12 Mar 1999 09:47:28 -0800 Message-ID: <541C9C38F3F3D111A3230000F89CCCCCDE1293@issmsg1.iss.msfc.nasa.gov> From: "Porter, Linda" Reply-To: MX-List@MadGoat.com To: "'MX-List@MadGoat.com'" Subject: blank emails sometimes delivered on a device timeout Date: Fri, 12 Mar 1999 11:46:39 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" We have an intermittent problem that, I think, began with MX 5.1 (not sure, though!). The short story is some receiving smtp servers and our MX mail server often can't maintain a connection, resulting in a "device timeout", and our end resets the connection to try again. Unfortunately, some mailers (hotmail is one) goes ahead and delivers an incomplete message, which almost always contains no subject, no body, often no timestamp, but usually the sender (express-delivery@sslab.msfc.nasa.gov list)! This does not always happen, of course, but it's frequent. I have been unable to force it to fail at the same time I have the debug logs turned on, but have witnessed the behavior myself at least once, first seeing the device timeout in a queue entry, and very shortly thereafter receiving a blank email in my own hotmail account from an unknown source, no timestamp, etc. Now I know hotmail doesn't have any business delivering mail for which it never received an end-of-transmission, but that doesn't make my recipients who receive them any happier. I'll continue to try to capture an smtp_debug log, but in the meantime - any ideas? (OpenVMS 7.1, Alpha, using FDDI to the network). Thanks! ================================================================================ Archive-Date: Sat, 13 Mar 1999 06:53:21 -0800 Sender: madison@MadGoat.Com Date: Sat, 13 Mar 1999 06:53:14 -0800 From: Matt Madison Reply-To: MX-List@MadGoat.com To: Linda.Porter@msfc.nasa.gov CC: mx-list@MadGoat.Com Message-ID: <009D50A6.A1133B6C.3@MadGoat.Com> Subject: RE: blank emails sometimes delivered on a device timeout > The short story is some receiving smtp servers and our MX mail server often >can't maintain a connection, resulting in a "device timeout", and our end >resets the connection to try again. Unfortunately, some mailers (hotmail is >one) goes ahead and delivers an incomplete message, which almost always >contains no subject, no body, often no timestamp, but usually the sender [...] > Now I know hotmail doesn't have any business delivering mail for which it >never received an end-of-transmission, but that doesn't make my recipients >who receive them any happier. > > I'll continue to try to capture an smtp_debug log, but in the meantime - >any ideas? (OpenVMS 7.1, Alpha, using FDDI to the network). If the message is being delivered as empty, then it sounds like a problem in the server implementation. It should not attempt to deliver the message until it has received the end-of-data marker (a dot by itself on a line); -Matt -- Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA madison@madgoat.com http://www.madgoat.com ================================================================================ Archive-Date: Sat, 13 Mar 1999 07:07:12 -0800 Message-ID: From: "Horn, James T" Reply-To: MX-List@MadGoat.com To: "'MX-List@MadGoat.com'" Subject: RE: Problems with Local process (MX 4.2) Date: Sat, 13 Mar 1999 09:06:51 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" The problem turned out to be with the MAIL$INTERNET_PROTOCOLS in the system logical table. I've defined it in the "JOB" table and it seems to be working. Based on this information, can someone point me to a way around the problem that was created with this? -----Original Message----- From: Horn, James T [mailto:HORN@exchng1.shsu.edu] Sent: Wednesday, March 10, 1999 9:02 AM To: 'MX-List@MadGoat.com' Subject: Problems with Local process (MX 4.2) We recently upgraded from v6.2 to V7.1-2 of Openvms alpha and having problems with the local process. It will process the "job" but will not deliver it to the persons MAIL.MAI file and it will resend it. The msg_text files shows: Return-Path: > Received: by nell.shsu.edu (MX V4.2 AXP) id 83; Wed, 10 Mar 1999 08:21:36 EST Date: Wed, 10 Mar 1999 08:21:33 EST From: horn@nell.shsu.edu To: SYSTEM@NELL.SHSU.EDU Message-ID: <009D4E57.78C9A264.83@nell.shsu.edu > Subject: test Message Return-Path: > Received: by nell.shsu.edu (MX V4.2 AXP) id 94; Wed, 10 Mar 1999 08:15:58 EST Date: Wed, 10 Mar 1999 08:15:56 EST From: horn@nell.shsu.edu To: SYSTEM@NELL.SHSU.EDU Message-ID: <009D4E56.AFE65941.94@nell.shsu.edu > Subject: test Message And it will repeat this every time it resends it. The path information looks like this: Domain-to-path mappings: Domain="freya.shsu.edu", Path=Local Domain="[192.92.115.8]", Path=Local Domain="[192.92.115.4]", Path=Local Domain="[192.92.115.5]", Path=Local Domain="niord.shsu.edu", Path=Local Domain="nell.shsu.edu", Path=Local Domain="odin.shsu.edu", Path=Local Domain="nell", Path=Local Domain="*.BITNET", Path=SMTP, Route="cunyvm.cuny.edu" Domain="*.UUCP", Path=SMTP, Route="uunet.uu.net" Domain="*", Path=SMTP There is no forward for the SYSTEM account. ================================================================================ Archive-Date: Sun, 14 Mar 1999 11:46:00 -0800 Date: Sun, 14 Mar 1999 13:45:49 -0600 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009D51A9.6F0C24B4.10@ALPHA.WKU.EDU> Subject: RE: Problems with Local process (MX 4.2) "Horn, James T" writes: > >The problem turned out to be with the MAIL$INTERNET_PROTOCOLS in the system >logical table. I've defined it in the "JOB" table and it seems to be >working. Based on this information, can someone point me to a way around the >problem that was created with this? > Ever since Digital let the C weenies rewrite MAIL, problems like this have occurred. In V7.2, you can no longer define MAIL$INTERNET_PROTOCOL (though the documentation still tells you to). If it's defined, the parsing of addresses breaks in MAIL. To get around it, you have to define SMTP_MAILSHR to point to MX_EXE:MX_MAILSHR.EXE. This is just one of many changes to MAIL, none of which are documented. Hunter ------ Hunter Goatley, Process Software, http://www.process.com http://www2.wku.edu/hunter/ ================================================================================ Archive-Date: Wed, 17 Mar 1999 04:36:19 -0800 From: cczanj@axp0.ccc.nottingham.ac.uk (Andy.Jack@nottingham.ac.uk) Subject: MX 4.2 and VMS 7.2 Date: 17 Mar 1999 11:47:03 GMT Message-ID: <7co4nn$hti$1@oyez.ccc.nottingham.ac.uk> Reply-To: MX-List@MadGoat.com To: MX-List@LISTS.WKU.EDU Hunter writes ... >> Ever since Digital let the C weenies rewrite MAIL, problems like this >> have occurred. In V7.2, you can no longer define >> MAIL$INTERNET_PROTOCOL (though the documentation still tells you to). >> If it's defined, the parsing of addresses breaks in MAIL. To get >> around it, you have to define SMTP_MAILSHR to point to >> MX_EXE:MX_MAILSHR.EXE. >> >> This is just one of many changes to MAIL, none of which are >> documented. I installed VMS 7.2 on my workstation last week and found that MX 4.2 ceased to function. I tried two things - firstly reinstalling MX 4.2 from the Freeware 4.0 CD, which failed (details below) - and then disabling MX and trying the UCX(*) SMTP support. I cannot justify buying MX 5.x for my workstation, the VAXcluster where my mail is currently delivered will be closed down in a few months and I'm at a bit of a loss as to what to do. (1) Can MX 4.2 run on VMS 7.2? Is there more to it than the logicals that Hunter refers to above? (2) The Digital-supplied SMTP support doesn't look too bad to me compared with the early product. (I don't need mailing lists or any fancy stuff like SMTP over DECnet). However, what immediately struck me was the fact that there doesn't seem to be an equivalent of MX_REPLY_TO. Is there? Regards, Andy ------------------------------------------------------------------------ (*) For UCX read DIGITAL TCP/IP Services for OpenVMS Version 5.0 ------------------------------------------------------------------------ Error message from MX 4.2 installation Now providing the SMTP support files and images. %VMSINSTAL-I-RESTORE, Restoring product save set E ... %MX-I-LINKING, Linking image MX_SMTP... %LINK-W-MULCLUOPT, cluster multiply defined in options file AXP0$DKB0:[SYS0.SYSUPD.MX042]MX_SMTP.ALPHA_OPT;2 %VMSINSTAL-E-INSFAIL, The installation of MX V4.2 has failed. ------------------------------------------------------------------------ Academic Computing Services, E-mail: Andy.Jack@nottingham.ac.uk University of Nottingham, Phone: +44 115 951 3328 Nottingham NG7 2RD, UK Fax: +44 115 951 3358 ================================================================================ Archive-Date: Wed, 17 Mar 1999 04:59:28 -0800 Date: Wed, 17 Mar 1999 13:50:40 +0100 Message-ID: <99031713504067@man.ac.uk> From: helbig@man.ac.uk (Phillip Helbig) Reply-To: MX-List@MadGoat.com To: MX-List@madgoat.com Subject: Re: MX 4.2 and VMS 7.2 > (2) The Digital-supplied SMTP support doesn't look too bad to me > compared with the early product. True, it has improved a lot. I'm running UCX V4.1-12G on ALPHA and UCX V4.2-21 on VAX, both with 7.1. Apparently 5.0, which is coming out with 7.2, is an even further improvement. > However, what immediately struck me > was the fact that there doesn't seem to be an equivalent of MX_REPLY_TO. > Is there? This is the only thing I really miss. There's not. However, you can fake by using the /SUBSTITUTE_DOMAIN qualifier in UCX SET CONFIG SMTP. With `NOHIDDEN' you get a Reply-To: field set to what you specify, which can be anything. Without it, this gets put in the From: field and there is no Reply-To: field. Of course, if this is not really your local domain, you can't send to users in that domain. What I do is set the substitute domain to be the main university domain, and get my email forwarded to my machine (as they don't allow direct receipt of mail anyway). This is man.ac.uk with a machine called multivac.jb.man.ac.uk. At the moment, I am working in the Netherlands, and my VAX in England forwards email directly to my machine here, gladia.astro.rug.nl (direct receipt is allowed here). However, here in the Netherlands as well I have the substitute domain set to man.ac.uk. Look at the headers of this message. If you fire up MAIL with one setting, you can change the setting and fire it up again to have more than one setting active at once, even (with appropriate privileges) on a per-user basis. -- Phillip Helbig Email ......... p.helbig@jb.man.ac.uk Nuffield Radio Astronomy Laboratories Tel. ... +44 1477 571 321 (ext. 2635) Jodrell Bank Fax ................ +44 1477 571 618 Macclesfield Telex ................ 36149 JODREL G UK-Cheshire SK11 9DL Web ... http://www.jb.man.ac.uk/~pjh/ ************************ currently working at ******************************* Kapteyn Instituut Email (above preferred) helbig@astro.rug.nl Rijksuniversiteit Groningen Tel. ...................... +31 50 363 4067 Postbus 800 Fax ....................... +31 50 363 6100 9700 AV Groningen The Netherlands Web ... http://gladia.astro.rug.nl/~helbig/ ================================================================================ Archive-Date: Wed, 17 Mar 1999 05:30:54 -0800 Date: Wed, 17 Mar 1999 06:59:28 -0600 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009D53CC.2A0DA520.14@ALPHA.WKU.EDU> Subject: RE: MX 4.2 and VMS 7.2 cczanj@axp0.ccc.nottingham.ac.uk (Andy.Jack@nottingham.ac.uk) writes: > >I installed VMS 7.2 on my workstation last week and found that MX 4.2 >ceased to function. I haven't tried V4.2, but can't think of anything that should break. What specifically "ceased to function"? >Error message from MX 4.2 installation > > Now providing the SMTP support files and images. > >%VMSINSTAL-I-RESTORE, Restoring product save set E ... >%MX-I-LINKING, Linking image MX_SMTP... >%LINK-W-MULCLUOPT, cluster multiply defined > in options file AXP0$DKB0:[SYS0.SYSUPD.MX042]MX_SMTP.ALPHA_OPT;2 >%VMSINSTAL-E-INSFAIL, The installation of MX V4.2 has failed. > I'll try to look into that. Hunter ------ Hunter Goatley, Process Software, http://www.process.com http://www2.wku.edu/hunter/ ================================================================================ Archive-Date: Wed, 17 Mar 1999 06:05:40 -0800 From: jasantos@ultranet.com (John Santos) Reply-To: MX-List@MadGoat.com Subject: Re: MX 4.2 and VMS 7.2 Date: Wed, 17 Mar 1999 07:50:51 -0500 Message-ID: To: MX-List@LISTS.WKU.EDU In article <7co4nn$hti$1@oyez.ccc.nottingham.ac.uk>, cczanj@axp0.ccc.nottingham.ac.uk says... > Hunter writes ... > > >> Ever since Digital let the C weenies rewrite MAIL, problems like this > >> have occurred. In V7.2, you can no longer define > >> MAIL$INTERNET_PROTOCOL (though the documentation still tells you to). > >> If it's defined, the parsing of addresses breaks in MAIL. To get > >> around it, you have to define SMTP_MAILSHR to point to > >> MX_EXE:MX_MAILSHR.EXE. > >> > >> This is just one of many changes to MAIL, none of which are > >> documented. > > I installed VMS 7.2 on my workstation last week and found that MX 4.2 > ceased to function. I tried two things - firstly reinstalling MX 4.2 > from the Freeware 4.0 CD, which failed (details below) - and then > disabling MX and trying the UCX(*) SMTP support. > > I cannot justify buying MX 5.x for my workstation, the VAXcluster where > my mail is currently delivered will be closed down in a few months and > I'm at a bit of a loss as to what to do. > > (1) Can MX 4.2 run on VMS 7.2? Is there more to it than the logicals > that Hunter refers to above? > > (2) The Digital-supplied SMTP support doesn't look too bad to me > compared with the early product. (I don't need mailing lists or any > fancy stuff like SMTP over DECnet). However, what immediately struck me > was the fact that there doesn't seem to be an equivalent of MX_REPLY_TO. > Is there? > > Regards, > Andy > > ------------------------------------------------------------------------ > (*) For UCX read DIGITAL TCP/IP Services for OpenVMS Version 5.0 > > ------------------------------------------------------------------------ > Error message from MX 4.2 installation > > Now providing the SMTP support files and images. > > %VMSINSTAL-I-RESTORE, Restoring product save set E ... > %MX-I-LINKING, Linking image MX_SMTP... > %LINK-W-MULCLUOPT, cluster multiply defined > in options file AXP0$DKB0:[SYS0.SYSUPD.MX042]MX_SMTP.ALPHA_OPT;2 > %VMSINSTAL-E-INSFAIL, The installation of MX V4.2 has failed. > > ------------------------------------------------------------------------ > Academic Computing Services, E-mail: Andy.Jack@nottingham.ac.uk > University of Nottingham, Phone: +44 115 951 3328 > Nottingham NG7 2RD, UK Fax: +44 115 951 3358 > I am running MX V4.1 on Alpha VMS 7.2. I didn't have to do anything special to get it running; it just started up normally. (I've been intending to upgrade to V4.2 for a long time, but haven't had any compelling reason to do it. Maybe it's just as well ;-)) John Santos P.S. UCX V5.0 POP3 server seems to have problems with attachments. I re-activated IUPOP3, which was already installed on my Alpha, and that cured the problem. Haven't had time to investigate it further. ================================================================================ Archive-Date: Wed, 17 Mar 1999 06:19:41 -0800 Date: Wed, 17 Mar 1999 15:14:39 +0100 Message-ID: <99031715143960@man.ac.uk> From: helbig@man.ac.uk (Phillip Helbig) Reply-To: MX-List@MadGoat.com To: MX-List@madgoat.com Subject: Re: MX 4.2 and VMS 7.2 > >> Ever since Digital let the C weenies rewrite MAIL, problems like this > >> have occurred. In my EDTINI.EDT I have DEFINE KEY FUNCTION 29 AS "XLATESPAWN ?*'SPAWN '^ZREF." to enable me to hit the DO key to SPAWN out of EDT. Now, this gives `Invalid subcommand' with EDT called normally or from within MAIL `command tables have invalid format - see documentation' on 7.1. However, if MAIL/OLD is used instead of MAIL, it works for EDT called from MAIL. Has this bug been fixed in 7.2? How can I get this to work in normal EDT, i.e. not called from MAIL? -- Phillip Helbig Email ......... p.helbig@jb.man.ac.uk Nuffield Radio Astronomy Laboratories Tel. ... +44 1477 571 321 (ext. 2635) Jodrell Bank Fax ................ +44 1477 571 618 Macclesfield Telex ................ 36149 JODREL G UK-Cheshire SK11 9DL Web ... http://www.jb.man.ac.uk/~pjh/ ************************ currently working at ******************************* Kapteyn Instituut Email (above preferred) helbig@astro.rug.nl Rijksuniversiteit Groningen Tel. ...................... +31 50 363 4067 Postbus 800 Fax ....................... +31 50 363 6100 9700 AV Groningen The Netherlands Web ... http://gladia.astro.rug.nl/~helbig/ ================================================================================ Archive-Date: Thu, 18 Mar 1999 12:56:20 -0800 From: cczanj@axp0.ccc.nottingham.ac.uk (Andy.Jack@nottingham.ac.uk) Subject: Re: MX 4.2 and VMS 7.2 Date: 18 Mar 1999 20:36:21 GMT Message-ID: <7cro45$1f2$1@oyez.ccc.nottingham.ac.uk> Reply-To: MX-List@MadGoat.com To: MX-List@LISTS.WKU.EDU In article <99031713504067@man.ac.uk>, helbig@man.ac.uk (Phillip Helbig) writes: [...] >> However, what immediately struck me >> was the fact that there doesn't seem to be an equivalent of MX_REPLY_TO. >> Is there? > >This is the only thing I really miss. There's not. [...] Nice to have one's suspicions confirmed. I now discover that it doesn't actually matter, as our mail gateway will rewrite the From line if it finds what "Andy.Jack@nottingham.ac.uk" translates into. So when that ceases to point at a defunct VAX, messages fom mailing lists etc. will get through whether I migrate to the workstation, or (Heaven help me) Exchange, Groupwise or SIMS - whatever ends up as being the University's chosen system. A propos "C weenies" - I had a play with the MIME utility that comes with VMS 7.2. I've never before seen a VMS product so willing, nay eager, to come up with an access violation. The barbarians are at the gate. Thanks, Andy ------------------------------------------------------------------------ Academic Computing Services, E-mail: Andy.Jack@nottingham.ac.uk University of Nottingham, Phone: +44 115 951 3328 Nottingham NG7 2RD, UK Fax: +44 115 951 3358 ================================================================================ Archive-Date: Thu, 18 Mar 1999 13:08:53 -0800 Date: Thu, 18 Mar 1999 22:05:23 +0100 Message-ID: <99031822052325@man.ac.uk> From: helbig@man.ac.uk (Phillip Helbig) Reply-To: MX-List@MadGoat.com To: MX-List@madgoat.com Subject: Re: MX 4.2 and VMS 7.2 > A propos "C weenies" - I had a play with the MIME utility that comes > with VMS 7.2. I've never before seen a VMS product so willing, nay > eager, to come up with an access violation. The barbarians are at the > gate. Yesterday, Netscape ate my DECwindows. As far as mime, I haven't played with it yet much. There was some discussion in comp.os.vms a while back about rolling one's on (the base 64 decoding is straightforward, as is the writing of the ASCII information describing what the attachment is etc). The only problem is the extra header needed---one can't just put it at the top if the message as VMS MAIL always inserts a blank line there, to separate the headers from the text. Someone came up with the elegant idea of constructing the message in a .COM file and forcing the extra header by embedding line feeds in the Subject: header! It would be interesting to know if such a setup is actually better than the 7.2 mime utility as far as actually composing the messages goes. -- Phillip Helbig Email ......... p.helbig@jb.man.ac.uk Nuffield Radio Astronomy Laboratories Tel. ... +44 1477 571 321 (ext. 2635) Jodrell Bank Fax ................ +44 1477 571 618 Macclesfield Telex ................ 36149 JODREL G UK-Cheshire SK11 9DL Web ... http://www.jb.man.ac.uk/~pjh/ ************************ currently working at ******************************* Kapteyn Instituut Email (above preferred) helbig@astro.rug.nl Rijksuniversiteit Groningen Tel. ...................... +31 50 363 4067 Postbus 800 Fax ....................... +31 50 363 6100 NL-9700 AV Groningen The Netherlands Web ... http://gladia.astro.rug.nl/~helbig/ ================================================================================ Archive-Date: Thu, 18 Mar 1999 13:15:50 -0800 Message-ID: <3.0.6.32.19990318131341.02f76790@ous.edu> Date: Thu, 18 Mar 1999 13:13:41 -0800 To: MX-List@MadGoat.com From: Dan Sugalski Reply-To: MX-List@MadGoat.com Subject: Re: MX 4.2 and VMS 7.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 10:05 PM 3/18/99 +0100, Phillip Helbig wrote: >> A propos "C weenies" - I had a play with the MIME utility that comes >> with VMS 7.2. I've never before seen a VMS product so willing, nay >> eager, to come up with an access violation. The barbarians are at the >> gate. > >Yesterday, Netscape ate my DECwindows. > >As far as mime, I haven't played with it yet much. There was some >discussion in comp.os.vms a while back about rolling one's on (the base >64 decoding is straightforward, as is the writing of the ASCII >information describing what the attachment is etc). The only problem is >the extra header needed---one can't just put it at the top if the >message as VMS MAIL always inserts a blank line there, to separate the >headers from the text. Someone came up with the elegant idea of >constructing the message in a .COM file and forcing the extra header by >embedding line feeds in the Subject: header! It would be interesting to >know if such a setup is actually better than the 7.2 mime utility as far >as actually composing the messages goes. I needed something like this, and couldn't wait for 7.2, so I rolled my own in perl. It MIME-encodes files, tags 'em with the right mime type (I used the suffixes list from the OSU DecThreads webserver, not that WinBlows actually cares about the tagging), and sends the resulting mail message to any handy SMTP server. I can pass the code on to anyone who might want it. (It needs perl and some modules from CPAN, so it's definitely not a standalone program unless you've got a well-rounded perl install...) Dan ---------------------------------------------"it's like this"-------------- Dan Sugalski (541) 737-3346 even samurai SysAdmin have teddy bears Oregon University System and even the teddy bears sugalskd@ous.edu get drunk ================================================================================ Archive-Date: Fri, 19 Mar 1999 00:53:28 -0800 Date: Fri, 19 Mar 1999 08:54:02 +0000 From: Chris Sharman Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: Chris.Sharman@ccagroup.co.uk Message-ID: <009D556E.7FECD304.12@ccagroup.co.uk> Subject: Re: MX 4.2 and VMS 7.2 >A propos "C weenies" - I had a play with the MIME utility that comes >with VMS 7.2. I've never before seen a VMS product so willing, nay >eager, to come up with an access violation. The barbarians are at the >gate. Yes, I played with that (on 7.1 after a bit of hacking: the docs say it should work back to 6.0 or something). It wouldn't work for me at all. The normally helpful Digits on comp.os.vms seemed a little cagey. TSC eventually told me it was "virtually non-functional" - and that apparently came from engineering. Perhaps development standards are now part of the 'Affinity' program :( Chris ______________________________________________________________________ Chris Sharman Chris.Sharman@CCAgroup.co.uk CCA Stationery Ltd, Eastway, Fulwood, Preston, Lancashire, PR2 9WS. ================================================================================ Archive-Date: Fri, 19 Mar 1999 03:37:23 -0800 From: cczanj@axp0.ccc.nottingham.ac.uk (Andy.Jack@nottingham.ac.uk) Subject: RE: MX 4.2 and VMS 7.2 Date: 19 Mar 1999 10:51:07 GMT Message-ID: <7cta6r$jeu$1@oyez.ccc.nottingham.ac.uk> Reply-To: MX-List@MadGoat.com To: MX-List@LISTS.WKU.EDU In article <009D53CC.2A0DA520.14@ALPHA.WKU.EDU>, Hunter Goatley writes: [...] >>I installed VMS 7.2 on my workstation last week and found that MX 4.2 >>ceased to function. > >I haven't tried V4.2, but can't think of anything that should break. >What specifically "ceased to function"? The ability to send or receive SMTP mail. (pretty fundamental, eh?) I can go back and see what's what if you think it worth while. I actually did an INSTALL rather than an UPGRADE of 7.2 and TCP/IP 5.0 onto a different disk. I still have the working VMS 7.1 disk, from which I used BACKUP to copy the MX directories and the sy$startup:mx_startup.com. I edited that manually to refer to the new disk and MX appeared to start - various processes were visible but I didn't take much notice. As I say, I don't currently use the workstation as a serious mail engine. When I read about the MIME utility, I thought I'd send a message from PC-land to the workstation and then, when it didn't arrive, discovered that I couldn't telnet to port 25 on axp0. Nor could I send a message out, MCP showed messages getting into the queue but the outgoing SMTP agent never processed them. Bearing in mind that MX 4.2 is not MadGoat's current product, I thought that I had the options of (a) trying to find out what I've done wrong with the existing 4.2, (b) re-installing or (c) trying the Digital/Compaq offering. I skipped (a) out of laziness and reported what happened with (b) and (c) to this newsgroup. Sadly, option (d) of buying a licence for MX 5.1 just doesn't appear on the list - as I said, the VAXes will be turned off this summer, the public Alphas either at the end of the year or next summer and the Library system when the librarians decide on a replacement. Sic transit gloria mundi. Andy ------------------------------------------------------------------------ Academic Computing Services, E-mail: Andy.Jack@nottingham.ac.uk University of Nottingham, Phone: +44 115 951 3328 Nottingham NG7 2RD, UK Fax: +44 115 951 3358 ================================================================================ Archive-Date: Fri, 19 Mar 1999 06:28:54 -0800 Date: Fri, 19 Mar 1999 15:28:48 MET-1MET DST From: Horst Drechsel Reply-To: MX-List@MadGoat.com To: MX-LIST@MADGOAT.COM CC: ai05@sternwarte.uni-erlangen.de Message-ID: <009D55A5.A62064C8.30@sternwarte.uni-erlangen.de> Subject: Internal mail server loop Hello, we are running MX 4.2 on an OpenVMS cluster server AlphaStation 400 4/233 under OpenVMS 7.1-1H1. Since a few days we have a problem with local mail delivery. Mail addressed to user@anynode.sternwarte.uni-erlangen.de is running into a loop between local cluster nodes, while mail to user@sternwarte.uni-erlangen.de is properly delivered. Our MX database entries look like: MCP> sh path Domain-to-path mappings: Domain="BAMP01.STERNWARTE.UNI-ERLANGEN.DE", Path=SMTP Domain="TOM.STERNWARTE.UNI-ERLANGEN.DE", Path=SMTP Domain="STERNWARTE.UNI-ERLANGEN.DE", Path=Local Domain="[192.44.90.100]", Path=Local Domain="[192.44.90.20]", Path=SMTP Domain="[192.44.90.13]", Path=Local Domain="[192.44.90.15]", Path=Local Domain="[192.44.90.11]", Path=Local Domain="[192.44.90.12]", Path=Local Domain="[192.44.90.10]", Path=Local Domain="[192.44.90.14]", Path=Local Domain="[192.44.90.24]", Path=SMTP Domain="ALF001", Path=Local Domain="ALF002", Path=Local Domain="ALF003", Path=Local Domain="BAMP01", Path=SMTP Domain="MELMAC", Path=Local Domain="M3300", Path=Local Domain="LUCKY", Path=Local Domain="A400", Path=Local Domain="TOM", Path=SMTP Domain="*.STERNWARTE.UNI-ERLANGEN.DE", Path=Local Domain="*.BITNET", Path=SMTP, Route="cunyvm.cuny.edu" Domain="*.UUCP", Path=SMTP, Route="uunet.uu.net" Domain="*", Path=SMTP and a message sent from a local user to another addressed as user@node.sternwarte.uni-erlangen.de produces the following non-delivery error message: From: SMTP%"Postmaster@sternwarte.uni-erlangen.de" "SMTP delivery agent" 19-MAR-1999 11:48:58.20 To: SMTP%"ai05@sternwarte.uni-erlangen.de" CC: Subj: SMTP delivery error Return-Path: <> Date: Fri, 19 Mar 1999 11:48:54 MET-1MET DST From: SMTP delivery agent To: Subject: SMTP delivery error X-Report-Type: Nondelivery; boundary="> Error description:" Note: this message was generated automatically. An error was detected while processing the enclosed message. A list of the affected recipients follows. This list is in a special format that allows software like LISTSERV to automatically take action on incorrect addresses; you can safely ignore the numeric codes. --> Error description: Error-For: AI05@A400.STERNWARTE.UNI-ERLANGEN.DE Error-Code: 2 Error-Text: %MX_SMTP-F-TRANSACTION_FAI, transaction failed -(Via A400.STERNWARTE.UNI-ERLANGEN.DE) -Transcript: -Rcvd: 220 a400.sternwarte.uni-erlangen.de MX V4.2 AXP SMTP server ready at Fri, 19 Mar 1999 11:48:46 MET-1MET DST -Sent: HELO ALF001.sternwarte.uni-erlangen.de -Rcvd: 250 Hello, ALF001.sternwarte.uni-erlangen.de -Sent: MAIL FROM: -Rcvd: 250 MAIL command accepted. -Sent: RCPT TO: -Rcvd: 250 Recipient okay (at least in form) -Sent: DATA -Rcvd: 354 Start mail input; end with . -Rcvd: 554 Received too many times by this host. -Sent: QUIT -Rcvd: 221 a400.sternwarte.uni-erlangen.de Service closing transmission channel Error-End: 1 error detected ------------------------------ Rejected message ------------------------------ Received: from melmac.sternwarte.uni-erlangen.de by a400.sternwarte.uni-erlangen.de (MX V4.2 AXP) with SMTP; Fri, 19 Mar 1999 11:48:43 MET-1MET DST Received: from a400.sternwarte.uni-erlangen.de by a400.sternwarte.uni-erlangen. de (MX V4.2 AXP) with SMTP; Fri, 19 Mar 1999 11:48:40 MET-1MET DST Received: from melmac.sternwarte.uni-erlangen.de by a400.sternwarte.uni-erlange n.de (MX V4.2 AXP) with SMTP; Fri, 19 Mar 1999 11:48:36 MET-1MET DST Received: from a400.sternwarte.uni-erlangen.de by a400.sternwarte.uni-erlangen. de (MX V4.2 AXP) with SMTP; Fri, 19 Mar 1999 11:48:32 MET-1MET DST Received: by sternwarte.uni-erlangen.de (MX V4.2 AXP) id 40; Fri, 19 Mar 1999 11:48:35 MET-1MET DST Date: Fri, 19 Mar 1999 11:48:35 MET-1MET DST From: Horst Drechsel To: AI05@A400.STERNWARTE.UNI-ERLANGEN.DE CC: ai05@sternwarte.uni-erlangen.de Message-ID: <009D5586.E2242D11.40@sternwarte.uni-erlangen.de> Subject: Test ai05@a400 ====================================================================== Has anyone a hint where to look? Thanks. Horst Drechsel -- **************************************************************************** Horst Drechsel Dr. Remeis Observatory drechsel@sternwarte.uni-erlangen.de Astronomical Institute Phone: +49-951-95222-15 University Erlangen-Nuernberg Fax: +49-951-95222-22 Sternwartstr.7, D-96049 Bamberg, Germany **************************************************************************** ================================================================================ Archive-Date: Fri, 19 Mar 1999 10:58:16 -0800 From: cczanj@axp0.ccc.nottingham.ac.uk (Andy.Jack@nottingham.ac.uk) Subject: RE: MX 4.2 and VMS 7.2 Date: 19 Mar 1999 17:49:41 GMT Message-ID: <7cu2nl$ai6$1@oyez.ccc.nottingham.ac.uk> Reply-To: MX-List@MadGoat.com To: MX-List@LISTS.WKU.EDU Matt Madison sent me a private mail message pointing out that I need the latest version of NETLIB to work with UCX 5.0. Having installed NETLIB 2.2 and disabled the UCX SMTP support, MX 4.2 is working happily on my VMS 7.2 system. My thanks once again to Hunter and Matt for their efforts. Andy ------------------------------------------------------------------------ Academic Computing Services, E-mail: Andy.Jack@nottingham.ac.uk University of Nottingham, Phone: +44 115 951 3328 Nottingham NG7 2RD, UK Fax: +44 115 951 3358 ================================================================================ Archive-Date: Mon, 22 Mar 1999 15:48:46 -0800 Sender: svist070@stvincents.COM.AU Date: Tue, 23 Mar 1999 10:50:24 EST From: Daiajo Tibdixious MACS Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: svist070@stvincents.com.au Message-ID: <009D58A3.6B39058D.5@svs30.stvincents.com.au> Subject: RE: blank emails sometimes delivered on a device timeout Fri, 12 Mar 1999 "Porter, Linda" > Now I know hotmail doesn't have any business delivering mail for which it >never received an end-of-transmission, but that doesn't make my recipients >who receive them any happier. I don't know if this in any way relates to your problem, but your mention of hotmail reminds me of a weird problem we had with them a few days back. Messages going TO hotmail will hang in the queue, and timeout. Looking up the various domains produces some odd results: Looking up "hotmail.com" hung, eventually timing out, not found Looking up "www.hotmail.com" hung the same way. hotmail.com translates to www.hotmail.com and law-entrance.hotmail.com. Looking up either 1 by address worked, but only law-entrance worked by name. Its like hotmail.com had a reverse entry but not a forward entry. It seems to be okay today. -- dTibdixious@stvincents.com.au (2)9361-2730 Server Technical Support