Archive-Date: Wed, 8 Jan 2003 10:41:37 -0800 From: "Mark Iline" Reply-To: MX-List@MadGoat.com To: "'Matt Madison'" , Subject: RE: Possible problem from: Important Security Notice for all versions of MX Date: Wed, 8 Jan 2003 18:42:32 -0000 Message-ID: <00f001c2b745$b4905720$7b372880@meng.ucl.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit In-Reply-To: <00A17FB1.FC4FFF98.8@MadGoat.Com> Having installed the security update, then the modified version, I think I'm still seeing the problem - ie mails with 'long lines' having the lines chopped off at ~254 characters. Unfortunately, I can't rigorously check this, as I don't have a mailer that generates this kind of mail. (VMS Mail & MX won't do it, long lines seem to get binned.) I'm confident that I'm running the right versions of the two images, so it seems the problem is still there. Any chance of a patch to fix that ? Mark Mark Iline, IT Mgr UCL Mech Eng, UK. > -----Original Message----- > From: Matt Madison [mailto:madison@MadGoat.COM] > Sent: Thursday, December 05, 2002 2:43 PM > To: MX-List@MadGoat.com > Cc: system@meng.ucl.ac.uk > Subject: RE: Possible problem from: Important Security Notice for all > versions of MX > > >Firstly, thanks to MadGoat for providing the ECO kits. > > > >Having installed the ECO (on MX 4.2 , OpenVMS Alpha v7.2-2 , Compaq > TCP/IP > >V5.1 - ECO 4) , I've subsequently noticed a problem which I hadn't > noticed > >before, so therefore may be related. > > > >I've noticed some e-mails that were "X-MX-Comment: QUOTED-PRINTABLE > message > >automatically decoded" having sections of text that are truncated at > about > >250 characters in length. Unfortunately, I don't have the original > >(non-truncated) e-mails to see exactly what's happened > > I have updated the kit for V4.2 to include the changes to eliminate > the 255-character line-length limitation. Those changes were made in a > prior patch kit, and I just hadn't updated my sources to include them. > > As before, the security update kit for V4.2 is at: > ftp://ftp.madgoat.com/mx/mx042/secupd/mx042_secupd.zip > > -Matt > > -- > Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 > USA > madison@madgoat.com > http://www.madgoat.com ================================================================================ Archive-Date: Fri, 17 Jan 2003 11:46:43 -0800 Date: Fri, 17 Jan 2003 19:47:56 +0100 From: Mark Iline Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <00A1A1E9.CBCAFD1B.51@meng.ucl.ac.uk> Subject: Anyone using MX 4.2 ? It's just that I'm surprised noone else seems to have been effected by what I've described in the e-mail below - or did I just miss some e-mails ? Mark Mark Iline, IT Mgr UCL Mech Eng, UK. system@meng.ucl.ac.uk From: MX%"MX-List@MadGoat.com" 8-JAN-2003 18:45:59.33 To: MX%"madison@MadGoat.COM",MX%"MX-List@MadGoat.com" CC: Subj: RE: Possible problem from: Important Security Notice for all versions of MX Having installed the security update, then the modified version, I think I'm still seeing the problem - ie mails with 'long lines' having the lines chopped off at ~254 characters. Unfortunately, I can't rigorously check this, as I don't have a mailer that generates this kind of mail. (VMS Mail & MX won't do it, long lines seem to get binned.) I'm confident that I'm running the right versions of the two images, so it seems the problem is still there. Any chance of a patch to fix that ? Mark Mark Iline, IT Mgr UCL Mech Eng, UK. > -----Original Message----- > From: Matt Madison [mailto:madison@MadGoat.COM] > Sent: Thursday, December 05, 2002 2:43 PM > To: MX-List@MadGoat.com > Cc: system@meng.ucl.ac.uk > Subject: RE: Possible problem from: Important Security Notice for all > versions of MX > > >Firstly, thanks to MadGoat for providing the ECO kits. > > > >Having installed the ECO (on MX 4.2 , OpenVMS Alpha v7.2-2 , Compaq > TCP/IP > >V5.1 - ECO 4) , I've subsequently noticed a problem which I hadn't > noticed > >before, so therefore may be related. > > > >I've noticed some e-mails that were "X-MX-Comment: QUOTED-PRINTABLE > message > >automatically decoded" having sections of text that are truncated at > about > >250 characters in length. Unfortunately, I don't have the original > >(non-truncated) e-mails to see exactly what's happened > > I have updated the kit for V4.2 to include the changes to eliminate > the 255-character line-length limitation. Those changes were made in a > prior patch kit, and I just hadn't updated my sources to include them. > > As before, the security update kit for V4.2 is at: > ftp://ftp.madgoat.com/mx/mx042/secupd/mx042_secupd.zip > > -Matt > > -- > Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 > USA > madison@madgoat.com > http://www.madgoat.com ================================================================================ Archive-Date: Fri, 17 Jan 2003 13:26:27 -0800 Message-ID: <177901c2be6e$fd24c2c0$ea0c210a@si.com> From: "Brian Tillman" Reply-To: MX-List@MadGoat.com To: References: <00A1A1E9.CBCAFD1B.51@meng.ucl.ac.uk> Subject: Re: Anyone using MX 4.2 ? Date: Fri, 17 Jan 2003 16:25:41 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit >It's just that I'm surprised noone else seems to have been effected by what >I've described in the e-mail below - or did I just miss some e-mails ? The latter. On 5-December, Matt said: >I have updated the kit for V4.2 to include the changes to eliminate >the 255-character line-length limitation. Those changes were made in a >prior patch kit, and I just hadn't updated my sources to include them. > >As before, the security update kit for V4.2 is at: >ftp://ftp.madgoat.com/mx/mx042/secupd/mx042_secupd.zip Brian Tillman Internet: Brian.Tillman at smiths-aerospace dot com Smiths Aerospace Addresses modified to prevent SPAM. 3290 Patterson Ave. SE, MS Replace "at" with "@", "dot" with "." Grand Rapids, MI 49512-1991 This opinion doesn't represent that of my company ********************************************************************** This e-mail and any files transmitted with it may be confidential and may be legally privileged or otherwise exempt from disclosure under applicable law. This e-mail and its files are intended solely for the individual or entity to whom they are addressed and their content is the property of Smiths Aerospace. If you are not the intended recipient, please do not read, copy, use or disclose this communication. If you have received this e-mail in error please notify the e-mail administrator at postmaster@si.com and then delete this e-mail, its files and any copies. This footnote also confirms that this e-mail message has been scanned for the presence of known computer viruses. Smiths addresses are changing! The new addresses are of the form firstname.lastname@smiths-aerospace.com. Please update your address books! Please begin using the new form immediately. *********************************************************************** ================================================================================ Archive-Date: Fri, 17 Jan 2003 13:35:04 -0800 Date: Fri, 17 Jan 2003 21:35:39 +0100 From: Mark Iline Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <00A1A1F8.D7ABC74B.428@meng.ucl.ac.uk> Subject: Re: Anyone using MX 4.2 ? Brian Tillman wrote: [MBI] >>It's just that I'm surprised noone else seems to have been effected by what >>I've described in the e-mail below - or did I just miss some e-mails ? > The latter. On 5-December, Matt said: >>I have updated the kit for V4.2 to include the changes to eliminate >>the 255-character line-length limitation. Those changes were made in a >>prior patch kit, and I just hadn't updated my sources to include them. >> >>As before, the security update kit for V4.2 is at: >>ftp://ftp.madgoat.com/mx/mx042/secupd/mx042_secupd.zip Ah yes, but that was a (very prompt) reply to my e-mail of the same day. The one I haven't seen any replies to is mine of the 8-Jan, where I said the updated patch didn't seem to have fixed the problems with long lines. Mark Mark Iline Sys Mgr Dept Mech Eng University College London UK system@meng.ucl.ac.uk ================================================================================ Archive-Date: Mon, 20 Jan 2003 11:46:19 -0800 Subject: Re: MX 5.3-2 ignoring vmsmail forwards From: peter@langstoeger.at (Peter LANGSTOEGER) Message-ID: Date: Mon, 20 Jan 2003 19:30:44 GMT Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com In article , "Chris Sharman" writes: >"Peter LANGSTOEGER" wrote in message news:TcwW9.67405$TY.611542@news.chello.at... >> But I've another hint: >> >> MAIL> SET FORWARD/USER=JOHNNY.CASH SMTP%"CASH@domain.name" > >Ours are all simple, local forwards, used purely to create aliases for a vms >username. >We might have john.cash, johnny.cash, jonathan.cash, all pointing to cash. Sorry for being unclear. I do not use NAME_CONVERSION to do what you do. I use SET FORWARD. And I do this normally on the local machine only. Maybe a MAIL> SET FORWARD/USER=JOHNNY.CASH SMTP%"CASH" MAIL> SET FORWARD/USER=JONATHAN.CASH SMTP%"CASH" will do exactly the same (I can't remember why we decided to not omit the domain names) but the magic portion is the SMTP% (or MX%) -- Peter "EPLAN" LANGSTOEGER Network and OpenVMS system specialist E-mail peter@langstoeger.at A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist ================================================================================ Archive-Date: Fri, 24 Jan 2003 12:32:23 -0800 Subject: Re: MX 5.3-2 ignoring vmsmail forwards From: peter@langstoeger.at (Peter LANGSTOEGER) Message-ID: Date: Fri, 24 Jan 2003 20:15:25 GMT Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com In article , "Chris Sharman" writes: >"Peter LANGSTOEGER" wrote in message news:E7YW9.104910$TY.963915@news.chello.at... >> In article , "Chris Sharman" writes: >> >"Peter LANGSTOEGER" wrote in message news:TcwW9.67405$TY.611542@news.chello.at... >> >> But I've another hint: >> >> >> >> MAIL> SET FORWARD/USER=JOHNNY.CASH SMTP%"CASH@domain.name" >> > >> >Ours are all simple, local forwards, used purely to create aliases for a vms >> >username. >> >We might have john.cash, johnny.cash, jonathan.cash, all pointing to cash. >> >> Sorry for being unclear. I do not use NAME_CONVERSION to do what you do. >> I use SET FORWARD. And I do this normally on the local machine only. >> Maybe a >> >> MAIL> SET FORWARD/USER=JOHNNY.CASH SMTP%"CASH" >> MAIL> SET FORWARD/USER=JONATHAN.CASH SMTP%"CASH" >> >> will do exactly the same (I can't remember why we decided to not omit the >> domain names) but the magic portion is the SMTP% (or MX%) > >Sorry - I think maybe _I_ was unclear. >We have (for inbound mail): > >MAIL> set forw/user=johnny.cash cash Ok. But then I have to repeat my warning: Iff a user does make a forward on its own for all mails (eg. to an internet mail service for accessing them from at home or a business journey or for whatever reason) - which you can't prevent ! - then the mail headers get lost/mangled even in the case the user does make his forward correctly (because you made it wrong). >We used name_conversion.exe to do the reverse translation on outgoing >messages, so that mail sent by user cash would appear to be from >johnny.cash@here.com (and any local CC's would be fixed up too). >For some reason the presence of name_conversion broke the inbound VMSmail >forwarding after we upgraded to 5.3. Maybe Matt can explain it... -- Peter "EPLAN" LANGSTOEGER Network and OpenVMS system specialist E-mail peter@langstoeger.at A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist ================================================================================ Archive-Date: Fri, 24 Jan 2003 20:37:26 -0800 Subject: [MX V5.6-2] MX_VMSMAIL_FROM_FORMAT logical ? From: peter@langstoeger.at (Peter LANGSTOEGER) Message-ID: <6hhY9.199375$TY.1827199@news.chello.at> Date: Fri, 24 Jan 2003 20:23:30 GMT Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com In both installation manuals (TXT, HTML) there is a logical MX_VMSMAIL_FROM_FORMAT mentioned In an MX cluster environment, MX will use a single network name to identify the entire cluster. If you have several nodes with their own network node names, and your networking software does not support the use of a cluster-wide alias, you could either pick one node to be the "master" for E-mail purposes or use the MX_VMSMAIL_FROM_FORMAT logical name (described in Message Exchange Management Guide) to have each node insert its own host name in return addresses on outgoing messages. What you do will depend on your network software and setup. But in both management manuals there is no mention of such a logical. Does it exist ? I think, yes. But what does it do ? TIA -- Peter "EPLAN" LANGSTOEGER Network and OpenVMS system specialist E-mail peter@langstoeger.at A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist ================================================================================ Archive-Date: Sun, 26 Jan 2003 07:13:00 -0800 Date: Sun, 26 Jan 2003 07:12:57 -0800 From: Matt Madison Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <00A1A892.D0C74F24.1@MadGoat.Com> Subject: Re: MX 5.3-2 ignoring vmsmail forwards MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" >>We used name_conversion.exe to do the reverse translation on outgoing >>messages, so that mail sent by user cash would appear to be from >>johnny.cash@here.com (and any local CC's would be fixed up too). >>For some reason the presence of name_conversion broke the inbound VMSmail >>forwarding after we upgraded to 5.3. > >Maybe Matt can explain it... It shouldn't if it's operating properly. Enabling debug logging in the Router and Local processes might help pinpoint the problem. -Matt -- Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA madison@madgoat.com http://www.madgoat.com ================================================================================ Archive-Date: Wed, 29 Jan 2003 03:17:51 -0800 Message-ID: <001201c2c788$8c9a5740$09080150@custom-pc> From: "Mark Iline" Reply-To: MX-List@MadGoat.com To: Subject: Truncated e-mails - still a problem in V5 ? Date: Wed, 29 Jan 2003 11:21:19 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Since installing the December security patch in December, we've had problems with lines longer than ~250 characters being truncated. Installing the (promptly supplied) updated patch didn't seem to fix the problem. That's MX 4.2 , and I've not got anywhere with finding out if anyone else has had the problem, or whether a further update is required. Having had excellent service for no money with the free versions of MX over the years, we were thinking about upgrading to the 'pay' version anyway. Now seems like the time to do it. However, I would like to first check that people aren't having the same truncation problems with V5 of MX. ( "Compaq TCP/IP Services for OpenVMS Alpha Version V5.1 - ECO 4 on a AlphaServer DS20 500 MHz running OpenVMS V7.2-2", FWIW.) Anyone having these problems with later versions of MX ? Mark Mark Iline - UCL Mech Eng system@meng.ucl.ac.uk ================================================================================ Archive-Date: Wed, 29 Jan 2003 06:43:38 -0800 Date: Wed, 29 Jan 2003 06:43:35 -0800 From: Matt Madison Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <00A1AAEA.35FC63B8.1@MadGoat.Com> Subject: RE: Truncated e-mails - still a problem in V5 ? MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" >Since installing the December security patch in December, we've had problems >with lines longer than ~250 characters being truncated. Installing the >(promptly supplied) updated patch didn't seem to fix the problem. > >That's MX 4.2 , and I've not got anywhere with finding out if anyone else >has had the problem, or whether a further update is required. I've finally had a chance to trace through the code, and it turns out that the changes I had imported to remove the line-length limitation weren't complete. I have updated the images in the mx042_secupd.zip with further changes that I think should do the trick now. Don't let that discourage you from upgrading, though. :-) >However, I would like to first check that people aren't having the same >truncation problems with V5 of MX. ( "Compaq TCP/IP Services for OpenVMS >Alpha Version V5.1 - ECO 4 > on a AlphaServer DS20 500 MHz running OpenVMS V7.2-2", FWIW.) > >Anyone having these problems with later versions of MX ? With the current version of MX, truncation of lines for locally-delivered messages is a setting -- SET LOCAL/LONG_LINES in MCP. -Matt -- Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA madison@madgoat.com http://www.madgoat.com ================================================================================ Archive-Date: Wed, 29 Jan 2003 07:54:13 -0800 From: "Mark Iline" Reply-To: MX-List@MadGoat.com To: Subject: RE: Truncated e-mails - still a problem in V5 ? Date: Wed, 29 Jan 2003 15:56:53 -0000 Message-ID: <00a601c2c7af$0b077ec0$7b372880@meng.ucl.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit In-Reply-To: <00A1AAEA.35FC63B8.1@MadGoat.Com> > -----Original Message----- > From: Matt Madison [mailto:madison@MadGoat.COM] > Sent: Wednesday, January 29, 2003 2:44 PM > I've finally had a chance to trace through the code, and it turns out that > the changes I had imported to remove the line-length limitation weren't > complete. I have updated the images in the mx042_secupd.zip with further > changes that I think should do the trick now. Thanks, I've installed that. > Don't let that discourage you from upgrading, though. :-) No, I won't let it. I've added 'buy MX' to my task list... Thanks again. Mark Mark Iline system@meng.ucl.ac.uk ================================================================================ Archive-Date: Fri, 31 Jan 2003 10:39:19 -0800 Date: Fri, 31 Jan 2003 13:36:48 -0500 From: "Brian Tillman, x8425" Reply-To: MX-List@MadGoat.com To: mx-list@madgoat.com Message-ID: <00A1ACB6.44804D20.81@swdev.si.com> Subject: What does this error mean? Our domain is changing. It used to be si.com (for Smiths Industries). We're now "Smiths Aerospace" (we've sold the si.com domian to Time Warner's Sports Illustrated) and our domain will be smiths-aerospace.com. In fact, the new domain is working. However, I've trying to send mail to that domain from our VMS system (it's internal mail and, internally, si.com still works) and we're receiving from "MX Mail Delivery System" (Postmaster@cluster.si.com): This is a report on the delivery status of your message. Message-ID: <00A1AC00.01BA9C40.126@swdev.si.com> Subject: Testing --Failed delivery to: Address: SOME.USER@SMITHS-AEROSPACE.COM Status: action not taken: mailbox name not allowed How can I find out what's going on? I can privately send our MX config, but since it contains real addresses and I don't want to mung it that extensively to hide them, I'd rather not post it. However, excerpts are below. In them, "internalrouter" is our default internal mail router, and "internetoutbound" is a machine that passes mail out to the Internet. Internet mail works fine, both inbound and outbound, and internal inbound mail works fine. Likewise, outbound mail to an internal "si.com" address works. I modified this config a few days ago, adding anything containing the "smiths-aerospace.com" domain. My MX logicals have not changed and MX_NODE_NAME is defined as "cluster.si.com", where "cluster" is the cluster alias. DEFINE PATH "vaxa.smiths-aerospace.com" Local DEFINE PATH "vaxa.si.com" Local DEFINE PATH "vaxa" Local DEFINE PATH "[10.33.1.72]" Local DEFINE PATH "vaxb.smiths-aerospace.com" local DEFINE PATH "vaxb.si.com" Local DEFINE PATH "vaxb" Local DEFINE PATH "[10.33.1.9]" Local ! DEFINE PATH "*.smiths-aerospace.com" SMTP DEFINE PATH "*.si.com" SMTP DEFINE PATH "smiths-aerospace.com" SMTP/route="internalrouter.si.com" DEFINE PATH "si.com" SMTP/route="internalrouter.si.com" ! ! Finally, SMTP mail everything else, forcing a route through internetoutbound ! NOTE: The next path definition should always be LAST. ! DEFINE PATH "*" SMTP/route="internetoutbound.si.com" ! ! Define who gets the errors. ! DEFINE ALIAS "Postmaster" "me@cluster.si.com" DEFINE ALIAS "POSTMAST" "me@cluster.si.com" ! ! Define the agent characteristics. ! SET SMTP/RETRY_INTERVAL=" 0 00:10:00.00" - /MAXIMUM_RETRIES=144 /DNS_RETRIES=12 - /DEFAULT_ROUTER="internetoutbound.si.com" - /VALIDATE_SENDER_DOMAIN/NOPERCENT_HACK ! SET LOCAL/RETRY_INTERVAL=" 0 00:10:00.00" - /CC_POSTMASTER /LONG_LINES /MAXIMUM_RETRIES=144 /OMIT_RESENT_HEADERS - /HEADERS=(TOP=NOALL, BOTTOM=ALL) ! SET ROUTER/NOPERCENT_HACK ! ! Define System Users ! DEFINE SYSTEM_USERS Postmaster@cluster.si.com,My.Name@smiths-aerospace.com,- me@cluster.si.com ********************************************************************** This e-mail and any files transmitted with it may be confidential and may be legally privileged or otherwise exempt from disclosure under applicable law. This e-mail and its files are intended solely for the individual or entity to whom they are addressed and their content is the property of Smiths Aerospace. If you are not the intended recipient, please do not read, copy, use or disclose this communication. If you have received this e-mail in error please notify the e-mail administrator at postmaster@smiths-aerospace.com and then delete this e-mail, its files and any copies. This footnote also confirms that this e-mail message has been scanned for the presence of known computer viruses. Smiths addresses are changing! The new addresses are of the form firstname.lastname@smiths-aerospace.com. Please update your address books! Please begin using the new form immediately. *********************************************************************** ================================================================================ Archive-Date: Fri, 31 Jan 2003 18:08:37 -0800 Date: Fri, 31 Jan 2003 18:08:34 -0800 From: Matt Madison Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <00A1ACDC.3B9EF88A.2@MadGoat.Com> Subject: RE: What does this error mean? MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" >Our domain is changing. It used to be si.com (for Smiths Industries). We're >now "Smiths Aerospace" (we've sold the si.com domian to Time Warner's Sports >Illustrated) and our domain will be smiths-aerospace.com. In fact, the new >domain is working. However, I've trying to send mail to that domain from our >VMS system (it's internal mail and, internally, si.com still works) and we're >receiving from "MX Mail Delivery System" (Postmaster@cluster.si.com): > >This is a report on the delivery status of your message. > > Message-ID: <00A1AC00.01BA9C40.126@swdev.si.com> > Subject: Testing > > --Failed delivery to: > Address: SOME.USER@SMITHS-AEROSPACE.COM > Status: action not taken: mailbox name not allowed This looks like MX was getting a 553 error from internalrouter.si.com's SMTP server. If so, there should have been an additional section in the delivery notification with the exact message returned by the server. Turning on debug logging for the SMTP agent should show this, too. -Matt -- Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA madison@madgoat.com http://www.madgoat.com