Archive-Date: Sun, 2 May 1999 18:21:13 -0700 Date: Sun, 2 May 1999 20:23:42 -0500 From: system@niuhep.physics.niu.edu Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009D7862.223E2129.5@niuhep.physics.niu.edu> Subject: Re: I can't seem to get off of ORBs From: eplan@kapsch.net (Peter LANGSTOEGER) Subject: Re: I can't seem to get off of ORBs Date: 30 Apr 1999 18:43:50 +0100 system@niuhep.physics.niu.edu writes: >What follows are the relevant (I think) results of "MCP> sho all". > >I have done a reset all, do I need to shutdown and restart or am I missing >something else? If the config is correct, a MCP RESET/CLUSTER should be sufficient. I just did a reset all, but that was on the node that they were able to use to relay a message >Any other information that would be useful? Check the relay-check mail, the ORBS warning mail sent to you has attached. Yeesh, I didn't see that before! Looks like a straight through relay ================== From MAILER-DAEMON@wwwhost.manawatu.net.nz Sat May 1 02:48:07 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 CAA10417 for ; Sat, 1 May 1999 0 2:48:06 +1200 (NZST) Received: from niuhep.physics.niu.edu (niuhep.physics.niu.edu [131.156.85.4]) by mail2.manawatu.net.nz (8.9.3/8.9.3) with ESMTP id CAA14764 for ; Sat, 1 May 1999 02:48:01 +1200 X-Remote-IP: 131.156.85.4 Date: Sat, 1 May 1999 02:48:01 +1200 Received: from relaytest.orbs.org (202.36.148.5) by niuhep.physics.niu.edu (MX V5.1 AXP) with SMTP for ; Fri, 30 Apr 1999 09:49:06 -0500 To: orbs-relaytest@manawatu.co.nz X-MX-Warning: Warning -- Invalid "From" header. From: null@mail2.manawatu.net.nz X-Token: jbavnaiqwlgaawks X-Envelope-Sender: Message-ID: <131.156.85.4@orbs.org> Subject: ORBS Relay Test - 131.156.85.4 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 up to 6 different 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: jbavnaiqwlgaawks ================================================================== > Act as SMTP relay for any host: disabled [SHOW LOCAL_DOMAINS lists hosts] > Validate sender's domain name: enabled >Inside IP networks/hosts: > 131.156.0.0 netmask 255.255.0.0 >Local domain patterns for SMTP relay checks: > *.NIU.EDU > NIU.EDU Do you have a Firewall SMTP server, too ? Nope. Thanks for the help. I'll have to look at teh documentation a bit and discuss the blackhole listing with the powers that be. I'll do the cluster reset and try again. Robert ================================================================================ Archive-Date: Sun, 2 May 1999 19:27:06 -0700 Sender: svist070@stvincents.COM.AU Date: Mon, 03 May 1999 12:28:53 EDT From: Daiajo Tibdixious MACS Reply-To: MX-List@MadGoat.com To: mx-list@madgoat.com CC: svist070@stvincents.com.au Message-ID: <009D78E8.F86774CA.7@svs30.stvincents.com.au> Subject: Also can't get off ORBS >Error in delivery to mailing list MX-Support: > Access denied. Send subscription requests to > MX-Support-request@MadGoat.com ... >From: Daiajo Tibdixious MACS >Reply-To: dTibdixious@stvincents.COM.AU This should NOT happen! We installed V5.1 specifically to get off ORBS, but obviously it isn't as simple as that. When we first turned on /NOrelay, we found that we have several separate 'internal' networks, the internal public hospital network, the private hospital network (which hangs off us) and the associated university network, which is external. WORLD --- UNIVERSITY --- MX V5.1 --- FW -- MX V4.2 -- public hospital | +--- private hospital The public hospital worked fine, but the private could not send externally, and no one could send to the university. [My memory may be a little vague here.] I promply added the bounce domains to LOCAL_DOMANS, which now looks like this: Local domain patterns for SMTP relay checks: *.STVINCENTS.COM.AU UNSW.EDU.AU *.UNSW.EDU.AU and our problems went away. However ORBS still lists us, and I did NOT get an email via postmaster as to why. Naturally I suspect their test using spoofed local domains would get thru. SMTP agent settings: Retry interval: 0 00:15:00.00 Maximum number of retries: 50 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 No inside networks/hosts defined. I figured I needed to define some inside networks, but something in the help: By default, the SMTP server will still reject a message that contains non-local addresses for both the sender and the receiver, even from hosts on the inside network address list. You can ease that restriction with the /RELAY_ALLOWED qualifier. [One quibble is that the reference to /RELAY_ALLOWED is not clear as whether it is set smtp or define inside, its easy to work out but could be better phrased.] I'm worried if I define inside addresses it might cut off the university or the private hospital again. Am I on the right track? Do I need inside/relay_allowed? -- dTibdixious@stvincents.com.au Server Technical Support -------------------------------------------------------------------------------- Return-Path: Received: from svs14.stvincents.com.au by svs30.stvincents.com.au (MX V4.2 AXP) with SMTP; Mon, 03 May 1999 12:26:02 EDT Received: from svhfw.stvincents.COM.AU (sva001.stvincents.COM.AU) by svs14.stvincents.com.au (MX V4.2 VAX) with SMTP; Mon, 03 May 1999 12:18:37 EST-10EST Received: by svhfw.stvincents.COM.AU; (5.65v4.0/1.3/10May95) id AA27725; Mon, 3 May 1999 12:24:54 +1000 Received: from dns2.stvincents.COM.AU by svhfw.stvincents.COM.AU (smtpxd); id XA12110 Received: from Praetorius.MadGoat.Com (204.87.183.186) by dns2.stvincents.com.au (MX V5.1 VAX) with ESMTP for ; Mon, 3 May 1999 12:36:15 +1000 ================================================================================ Archive-Date: Sun, 2 May 1999 22:04:30 -0700 Sender: svist070@stvincents.COM.AU Date: Mon, 03 May 1999 15:06:18 EDT From: Daiajo Tibdixious MACS Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: svist070@stvincents.com.au Message-ID: <009D78FE.F5C0BCCA.21@svs30.stvincents.com.au> Subject: RE: Also can't get off ORBS I emailed orbs@orbs.org and got the following reply: Date: Mon, 3 May 1999 15:45:49 +1200 (NZST) From: ORBS catchall account To: dTibdixious@stvincents.COM.AU CC: orbs@orbs.org, svist070@stvincents.COM.AU Subject: Re: 203.20.160.18 I'm confused On Mon, 3 May 1999, Daiajo Tibdixious MACS wrote: > We applied the fix for our system which is to upgrade to MX V5 and activate > anti-relaying, which we did. > > I then went to orbs, did the "take me off" stuff, but we are still listed. How long ago was that? Your machine was last verified open on April 27th > I was expecting a message to postmaster if we went back on the ORBS list, but > nothing came. If you did it after Apr 27th, then something's playing up and you didn't get removed/retested. :-( If you did it before then, here's the relay test which failed you: From MAILER-DAEMON@mail2.manawatu.net.nz Wed Apr 28 07:03:48 1999 Return-Path: <> Received: from dns2.stvincents.com.au (dns2.stvincents.COM.AU [203.20.160.18]) by mail2.manawatu.net.nz (8.9.3/8.9.3) with ESMTP id HAA14534 for ; Wed, 28 Apr 1999 07:03:47 +1200 X-Remote-IP: 203.20.160.18 Date: Wed, 28 Apr 1999 07:03:47 +1200 Received: from relaytest.orbs.org (202.36.148.5) by dns2.stvincents.com.au (MX V5.1 VAX) with SMTP for ; Wed, 28 Apr 1999 05:15:54 +1000 To: orbs-relaytest@manawatu.co.nz X-MX-Warning: Warning -- Invalid "From" header. From: null@mail2.manawatu.net.nz X-Token: stuwstktiybomjxb X-Envelope-Sender: Message-ID: <203.20.160.18@orbs.org> Subject: ORBS Relay Test - 203.20.160.18 This is a relay for null sender envelopes. RFC2505 is a bit confusing on the null sender issue. You need to accept them for local delivery as they're used by mailer-daemons (ie, don't just apply an arbitrary block or you'll interfere with non-delivery notices), but still shouldn't be allowing that sender envelope to relay. Regards Alan Brown ORBS admin Okay so we failed the null Sender test. Is this my problem or an MX problem? -- dTibdixious@stvincents.com.au Server Technical Support ================================================================================ Archive-Date: Mon, 3 May 1999 01:19:35 -0700 Message-ID: <013401be953d$9a496ec0$de2c67cb@stmarks.pp.catholic.edu.au> From: "Geoff Roberts" Reply-To: MX-List@MadGoat.com To: CC: References: <009D78E8.F86774CA.7@svs30.stvincents.com.au> Subject: Re: Also can't get off ORBS Date: Mon, 3 May 1999 17:49:00 +0930 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit ----- Original Message ----- From: Daiajo Tibdixious MACS To: Cc: Sent: Tuesday, 4 May 1999 1:58 Subject: Also can't get off ORBS Saint Vincents Hospital? Adelaide? > Naturally I suspect their test using spoofed local domains would get thru. > > SMTP agent settings: > Retry interval: 0 00:15:00.00 > Maximum number of retries: 50 > 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 > > No inside networks/hosts defined. > > I figured I needed to define some inside networks, but something in the help: > Am I on the right track? Do I need inside/relay_allowed? This works for me. 99% of spam seems to be non australian in origin, and it will shut ORBS up. Configuration file: MX_DEVICE:[MX]MX_CONFIG.MXCFG;14 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:01: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: enabled 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: enabled 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: PP.CATHOLIC.EDU.AU *.PP.CATHOLIC.EDU.AU *.*.PP.CATHOLIC.EDU.AU OZEMAIL.COM.AU {The last one above is for the principal, who insists on using his private email address for inwards mail, and our SMTP server to post his outbound stuff...) Inside IP networks/hosts: 203.0.0.0 netmask 255.0.0.0 Yes, it's a bit of a large blanket, but it's impossible for me to figure out where in oz some of my users will be accessing mail from, so it's a simple solution, and I can if necessary, do a /norelay for specific addresses or blocks if they become a problem. Gets rid of ORBS too, as they are in NZ (Canada chucked 'em out) and are 202.whatever.... Cheers Geoff Roberts VK5KDR Computer Systems Manager Saint Mark's College Port Pirie, South Australia. Email: geoffrob@stmarks.pp.catholic.edu.au netcafe@pirie.mtx.net.au ICQ #: 1970476 Work Phone: 61-8-8633-8834 (1100-1800 Mon-Thurs) ================================================================================ Archive-Date: Wed, 5 May 1999 10:05:30 -0700 Date: Wed, 5 May 1999 12:07:59 -0500 From: system@niuhep.physics.niu.edu Reply-To: MX-List@MadGoat.com To: mx-list@MadGoat.COM CC: madison@MadGoat.COM Message-ID: <009D7A78.61695284.4@niuhep.physics.niu.edu> Subject: RE: I can't seem to get off ORBS Back again. I've included the log files. [CC: to Matt] The relevant lines from the message from ORBS seem to be: (btw: NIUHEP.PHYSICS.NIU.EDU = 131.56.85.4) To: orbs-relaytest@manawatu.co.nz X-MX-Warning: Warning -- Invalid "From" header. From: null@mail2.manawatu.net.nz X-Token: iexkahurczbvnrls X-Envelope-Sender: Message-ID: <131.156.85.4@orbs.org> Subject: ORBS Relay Test - 131.156.85.4 Should MX reject "null" user names? Is a "null" username literally "null" or simply non-existant? Do I have to set up a REJMAN rule? Should all rejected messages be logged into SMTP_SERVER_NIUHEP.LOG:? Is there an easy way to search the debug log for rejected messages? (i.e. a word that would show up in rejected messages but not others?) (In the following I used "..." to denote a continued line) The following seem to be the relevant lines from the two log files. I did a search for null on the anti-spam logfile and came up blank from SMTP_SERVER_NIUHEP.LOG: 30-APR-1999 09:28:17.26: MX SMTP Server (pid 2901A300) resetting 30-APR-1999 09:45:01.30: MX SMTP server: rejected message ...from to ...sent by [202.36.148.5] due to disabled relay 30-APR-1999 09:50:46.71: MX SMTP server: rejected message ...from to ...sent by [202.36.148.5] due to disabled relay From MX_ANTI_SPAM_LOG.LOG_2901A300; 30-APR-1999 09:45:00.65 : in IS_LOCAL_DOMAIN, checking orbs.org 30-APR-1999 09:45:00.67 : IS_LOCAL_DOMAIN: no 30-APR-1999 09:45:00.69 : IS_SPAM: no rejection records, returning 0 30-APR-1999 09:45:00.70 : in IS_LOCAL_DOMAIN, checking orbs.org 30-APR-1999 09:45:00.72 : IS_LOCAL_DOMAIN: no 30-APR-1999 09:45:01.15 : in VERIFY_RESET_CHECK... 30-APR-1999 09:45:01.17 : shutting_down=0 30-APR-1999 09:45:01.18 : reset_mask=00000000 30-APR-1999 09:45:01.19 : rejection count=0 30-APR-1999 09:45:01.20 : NORELAY set -- will do relay check 30-APR-1999 09:45:01.22 : will parse 30-APR-1999 09:45:01.23 : in IS_LOCAL_DOMAIN, checking manawatu.co.nz 30-APR-1999 09:45:01.24 : IS_LOCAL_DOMAIN: no 30-APR-1999 09:45:01.25 : rewrote address to: orbs-relaytest, next ...hop manawatu.co.nz 30-APR-1999 09:45:01.26 : FINDPATH status was 00000001, pathid 2 30-APR-1999 09:45:01.27 : in IS_LOCAL_DOMAIN, checking manawatu.co.nz 30-APR-1999 09:45:01.28 : IS_LOCAL_DOMAIN: no 30-APR-1999 09:45:01.29 : VERIFY_ADDRESS final status=251, ...outstr="2.1.5 Will forward to " 30-APR-1999 09:45:45.95 : in IS_LOCAL_DOMAIN, checking ...niuhep.physics.niu.edu 30-APR-1999 09:45:45.97 : -- matched local mail domain name or host ...name 30-APR-1999 09:45:45.98 : IS_SPAM: no rejection records, returning 0 30-APR-1999 09:45:45.99 : in IS_LOCAL_DOMAIN, checking ...niuhep.physics.niu.edu 30-APR-1999 09:45:46.00 : -- matched local mail domain name or host ...name 30-APR-1999 09:45:46.08 : in VERIFY_RESET_CHECK... 30-APR-1999 09:45:46.10 : shutting_down=0 30-APR-1999 09:45:46.11 : reset_mask=00000000 30-APR-1999 09:45:46.12 : rejection count=0 [snip] 30-APR-1999 09:49:04.49 : IS_SPAM: no rejection records, returning 0 30-APR-1999 09:49:04.50 : in IS_LOCAL_DOMAIN, checking 30-APR-1999 09:49:04.51 : IS_LOCAL_DOMAIN: no 30-APR-1999 09:49:04.94 : in VERIFY_RESET_CHECK... 30-APR-1999 09:49:04.97 : shutting_down=0 30-APR-1999 09:49:04.98 : reset_mask=00000000 30-APR-1999 09:49:04.99 : rejection count=0 30-APR-1999 09:49:05.00 : NORELAY set -- will do relay check 30-APR-1999 09:49:05.01 : will parse 30-APR-1999 09:49:05.03 : in IS_LOCAL_DOMAIN, checking manawatu.co.nz 30-APR-1999 09:49:05.04 : IS_LOCAL_DOMAIN: no 30-APR-1999 09:49:05.05 : rewrote address to: orbs-relaytest, next ...hop manawatu.co.nz 30-APR-1999 09:49:05.06 : FINDPATH status was 00000001, pathid 2 30-APR-1999 09:49:05.07 : in IS_LOCAL_DOMAIN, checking manawatu.co.nz 30-APR-1999 09:49:05.08 : IS_LOCAL_DOMAIN: no 30-APR-1999 09:49:05.09 : VERIFY_ADDRESS final status=251, ...outstr="2.1.5 Will forward to $ 30-APR-1999 09:49:06.37 : in IS_SPAM_HEADER 30-APR-1999 09:49:06.38 : IS_SPAM_HEADER exiting -- no HDMATCH ...records [snip] 30-APR-1999 09:50:45.83 : in IS_LOCAL_DOMAIN, checking orbs.org 30-APR-1999 09:50:45.85 : IS_LOCAL_DOMAIN: no 30-APR-1999 09:50:45.87 : IS_SPAM: no rejection records, returning 0 30-APR-1999 09:50:45.88 : in IS_LOCAL_DOMAIN, checking orbs.org 30-APR-1999 09:50:45.99 : IS_LOCAL_DOMAIN: no 30-APR-1999 09:50:46.41 : in VERIFY_RESET_CHECK... 30-APR-1999 09:50:46.44 : shutting_down=0 30-APR-1999 09:50:46.46 : reset_mask=00000000 30-APR-1999 09:50:46.49 : rejection count=0 30-APR-1999 09:50:46.51 : NORELAY set -- will do relay check 30-APR-1999 09:50:46.53 : will parse 30-APR-1999 09:50:46.55 : in IS_LOCAL_DOMAIN, checking [131.156.85.4] 30-APR-1999 09:50:46.58 : IS_LOCAL_DOMAIN: no 30-APR-1999 09:50:46.60 : rewrote address to: postmaster, next hop ...[131.156.85.4] 30-APR-1999 09:50:46.62 : FINDPATH status was 00000001, pathid 2 30-APR-1999 09:50:46.64 : in IS_LOCAL_DOMAIN, checking [131.156.85.4] 30-APR-1999 09:50:46.67 : IS_LOCAL_DOMAIN: no 30-APR-1999 09:50:46.69 : VERIFY_ADDRESS final status=251, ...outstr="2.1.5 Will forward to " 30-APR-1999 09:50:48.60 : in IS_LOCAL_DOMAIN, checking orbs.org 30-APR-1999 09:50:48.63 : IS_LOCAL_DOMAIN: no 30-APR-1999 09:50:48.66 : IS_SPAM: no rejection records, returning 0 30-APR-1999 09:50:48.69 : in IS_LOCAL_DOMAIN, checking orbs.org 30-APR-1999 09:50:48.71 : IS_LOCAL_DOMAIN: no 30-APR-1999 09:50:49.13 : in VERIFY_RESET_CHECK... 30-APR-1999 09:50:49.16 : shutting_down=0 30-APR-1999 09:50:49.19 : reset_mask=00000000 30-APR-1999 09:50:49.21 : rejection count=0 30-APR-1999 09:50:49.23 : NORELAY set -- will do relay check 30-APR-1999 09:50:49.25 : will parse ... 30-APR-1999 09:50:49.28 : in IS_LOCAL_DOMAIN, checking ...niuhep.physics.niu.edu 30-APR-1999 09:50:49.30 : -- matched local mail domain name or host ...name 30-APR-1999 09:50:49.32 : rewrote address to: postmaster, next hop ...niuhep.physics.niu.edu 30-APR-1999 09:50:49.34 : FINDPATH status was 00000001, pathid 1 30-APR-1999 09:50:49.36 : VERIFY_ADDRESS final status=250, ...outstr="2.1.5 " 30-APR-1999 09:50:50.08 : in IS_SPAM_HEADER 30-APR-1999 09:50:50.11 : IS_SPAM_HEADER exiting -- no HDMATCH ...records 30-APR-1999 09:50:50.13 : Skipping heuristic filter checks - none ...enabled. ================================================================================ Archive-Date: Wed, 5 May 1999 10:17:37 -0700 Date: Wed, 5 May 1999 13:17:41 -0500 From: "Edward J. Groth" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009D7A82.1E2EC6B6.165@PUPGG.PRINCETON.EDU> Subject: Gone until May 10 Folks - I will be out of town until May 10. Although I may have an opportunity to read my email before then, it's not guaranteed. If you are a physics 104 student with a lab exam conflict, please see our lab coordinator, Amir Razzaghi, amir@princeton.edu. If you are in my class, looking for your quiz, it's graded and on a chair outside my office, 264 Jadwin. (The solutions weren't available when I left - check with our course manager Charlotte Richick in the department office, room 208, uphysics@pupgg.princeton.edu) For other physics 104 lab questions, contact Amir. For general physics 104 questions, see Charlotte. For other questions, please see Angela Qualls, angelaq@princeton.edu, who will know how to reach me if absolutely needed. If you are reading this on a mailing list, sorry. However, each list should receive at most one copy of this auto-reply. - Ed -- /----------------------------------------------------------------------\ | Edward J. Groth | Phone: 609-258-4361 Fax: 609-258-6853 | | Physics Dept., Jadwin Hall | URL: http://pupgg.princeton.edu/~groth/ | | Princeton University | SPAN/HEPNET: PUPGG::GROTH=44117::GROTH | | Princeton, NJ 08544 | Internet: groth@pupgg.princeton.edu | \----------------------------------------------------------------------/ ================================================================================ Archive-Date: Wed, 5 May 1999 12:28:24 -0700 Date: Wed, 5 May 1999 14:30:55 -0500 From: system@niuhep.physics.niu.edu Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009D7A8C.59692C7B.11@niuhep.physics.niu.edu> Subject: RE: Also can't get off ORBS Ok, now I am confused. Happy but confused. I did another reset and went over to the orbs retest site and asked them to retest. the smtp server log shows that they did and this time shows that 5-MAY-1999 13:29:14.43: MX SMTP server: rejected message from <> to sent by [202.36.148.5] due to disabled relay So it passed the null sender test this time. I am about as sure as I can be that I haven't done anything in the meantime. >Okay so we failed the null Sender test. Is this my problem or an MX problem? Try doing another reset and ask again for a reset. Robert ================================================================================ Archive-Date: Mon, 10 May 1999 02:01:06 -0700 Message-ID: <023801be9ac4$046aacc0$cb2300c0@tool201> From: "Interno" Reply-To: MX-List@MadGoat.com To: Subject: 500 Host server does not support 8bitmime Date: Mon, 10 May 1999 11:03:46 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-Path: jlj@bancoinversion.es Our smtp server does not relay some messages wich have some files attached, with the error: 500 Host server does not support 8bitmime. Other messages with files attached are processed. Anybody know why? regards Jose Luis Lopez Jacob Madrid -----Original Message----- From: Geoff Roberts To: MX-List@MadGoat.com Cc: svist070@stvincents.com.au Date: lunes 3 de mayo de 1999 10:15 Subject: Re: Also can't get off ORBS > >----- Original Message ----- >From: Daiajo Tibdixious MACS >To: >Cc: >Sent: Tuesday, 4 May 1999 1:58 >Subject: Also can't get off ORBS > >Saint Vincents Hospital? Adelaide? > >> Naturally I suspect their test using spoofed local domains would get thru. >> >> SMTP agent settings: >> Retry interval: 0 00:15:00.00 >> Maximum number of retries: 50 >> 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 >> >> No inside networks/hosts defined. >> >> I figured I needed to define some inside networks, but something in the >help: >> Am I on the right track? Do I need inside/relay_allowed? > >This works for me. 99% of spam seems to be non australian in origin, and it >will shut ORBS up. >Configuration file: MX_DEVICE:[MX]MX_CONFIG.MXCFG;14 > >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:01: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: enabled > 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: enabled > 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: > PP.CATHOLIC.EDU.AU > *.PP.CATHOLIC.EDU.AU > *.*.PP.CATHOLIC.EDU.AU > OZEMAIL.COM.AU > >{The last one above is for the principal, who insists on using his private >email address for inwards mail, and our SMTP server to post his outbound >stuff...) > >Inside IP networks/hosts: > 203.0.0.0 netmask 255.0.0.0 > >Yes, it's a bit of a large blanket, but it's impossible for me to figure out >where in oz some of my users will be accessing mail from, so it's a simple >solution, and I can if necessary, do a /norelay for specific addresses or >blocks if they become a problem. Gets rid of ORBS too, as they are in NZ >(Canada chucked 'em out) and are 202.whatever.... > >Cheers > >Geoff Roberts >VK5KDR >Computer Systems Manager >Saint Mark's College >Port Pirie, South Australia. >Email: geoffrob@stmarks.pp.catholic.edu.au > netcafe@pirie.mtx.net.au >ICQ #: 1970476 >Work Phone: 61-8-8633-8834 (1100-1800 Mon-Thurs) > > ================================================================================ Archive-Date: Mon, 10 May 1999 08:42:59 -0700 Date: Mon, 10 May 1999 08:42:52 -0700 (PDT) From: Dan Wing Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Subject: Re: 500 Host server does not support 8bitmime In-Reply-To: <023801be9ac4$046aacc0$cb2300c0@tool201> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 10 May 1999 11:03 +0200, Interno wrote: > Our smtp server does not relay some messages wich have some files attached, > with the error: 500 Host server does not support 8bitmime. Other messages > with files attached are processed. Anybody know why? Over-zealous interpretation of the 8bitmime specification by the implementor of your SMTP server. -Dan Wing ================================================================================ Archive-Date: Mon, 10 May 1999 11:32:44 -0700 Message-ID: <000d01be9b14$5ed19fc0$010020ac@sysman_home.deltatel.ru> From: "Ruslan R. Laishev" Reply-To: MX-List@MadGoat.com To: CC: "Sam Rozenfeld" Subject: MX Local problem Date: Mon, 10 May 1999 22:38:57 +0400 I have a problem using of MX-local process, MX_LOCAL__2.LOG follows: $ set noon $ rights = f$getjpi("","rightslist") $ username = f$edit(f$getjpi("","username"),"collapse") $ IF F$LOCATE("SECUREPAGES",RIGHTS) .LT F$LENGTH(RIGHTS) then - DEFINE/NOLOG SECUREPAGES "WWW_SECURE:[SYSTEM]" 4-MAY-1999 13:48:20.31: MX Local#2 (pid 20A00A3E) starting 4-MAY-1999 14:24:40.30: MX Local#2 (pid 20A00A3E) resetting 4-MAY-1999 14:31:07.70: MX Local#2 (pid 20A00A3E) resetting %RMS-F-FLK, file currently locked by another user %TRACE-F-TRACEBACK, symbolic stack dump follows image module routine line rel PC abs PC MX_LOCAL AGENT AGENT_MAIN 391 0000000000000A5C 0000000000038B8C MX_LOCAL MX_LOCAL MX_LOCAL 37 000000000000003C 000000000003003C 0 FFFFFFFF8305B118 FFFFFFFF8305B118 4-MAY-1999 14:31:29.36: MX Local#2 (pid 20A00A3E) exiting, status = 1001828C SYSTEM job terminated at 4-MAY-1999 14:31:29.40 Accounting information: Buffered I/O count: 2102 Peak working set size: 4288 Direct I/O count: 8760 Peak virtual size: 176048 Page faults: 747 Mounted volumes: 0 Charged CPU time: 0 00:00:21.67 Elapsed time: 0 What is problem here ? C U, SysMan at DLS ...................................................+ | Cel: +7 (901) 971-3222 http://home.dls.net | Fax: +7 (812) 115-1035 ................................................... Frying on the VMS + ================================================================================ Archive-Date: Tue, 11 May 1999 02:51:33 -0700 Sender: najman@HADASSAH.org.IL Date: Tue, 11 May 1999 12:50:57 +0200 From: "Najman Kahana. Ext:77313" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: najman@HADASSAH.org.IL Message-ID: <009D7F35.60BA3F3A.146@HADASSAH.org.IL> Subject: MX looping on decnet address hello. I ran into a multi part problem, and I hope some of you have solutions: ( VMS 6.2, mx 5-1X, cluster) Sorry, but this is going to be long, so I'll summarize, and then go into details. A series of unusual events caused an incoming mail to have one of its destination addresses in the format "node::user@host1.host2". The MX choked on this format with the result that it sent the mail to the other recipients, failed for this format, and requeued the mail. This became an endless loop in which all recipients, but one, received this mail item over and over for 3 days (until manually dequeued). Please, feel free to contact me directly. thank you Najman Kahana Hadassah University Hospital Najman@hadassah.org.il ================================================================= 1. The cast of characters: ZEV, a VMS user on a cluster; STEVE, another VMS user, same cluster, same or different node; DAVE, an offsite mail correspondent. 2. The events. a) STEVE emails ZEV. The header in ZEV's copy looks thusly: From: LEO::STEVE To: LIBRA::ZEV CC: Subj: test b) ZEV replies to STEVE, with CC: to DAVE and himself. Here is ZEV's copy: From: LIBRA::ZEV To: LEO::STEVE CC: MX%DAVE,ZEV Subj: RE: test c) DAVE replies to both. This is the header ZEV sees: From: MX%"dave@wherever.co.il" To: MX%"zev@HADASSAH.org.IL",MX%"'leo::steve'@HADASSAH.org.IL" CC: MX%"DAVE@WHEREVER.CO.IL" Subj: RE: test ======================= Zev receives his mail. Steve never does. The MX goes into a requeue loop. I tried adding a rewrite rule: <{node}::{user}@hadassah.org.il> <{user}@{node}.hadassah.org.il> but the debug trace shows that this rule was not matched. - how do I prevent the strange outgoing address (leo::steve@hadassah) - how do I rewrite the incoming address to get rid of the "::" - how do I prevent the MX agent from requeuing ================ rewrite rules =================== Address-rewriting rules: Rewrite "<{NODE}::{USER}@LEO>" => "<{USER}@MAIL.HADASSAH.ORG.IL>" Rewrite "<{USER}@HADASSAH.ORG.IL>" => "<{USER}@MAIL.HADASSAH.ORG.IL>" Rewrite "<{USER}@LEO>" => "<{USER}@MAIL.HADASSAH.ORG.IL>" ================ local.log =================== 11-MAY-1999 07:53:58.61 =================================================== 11-MAY-1999 07:53:58.62 Processing queue entry number 50 11-MAY-1999 07:53:58.64 Checking local name: ZEV 11-MAY-1999 07:53:58.67 This is a regular delivery to ZEV. 11-MAY-1999 07:53:58.67 Checking local name: leo::steve 11-MAY-1999 07:53:59.03 =================================================== (the trace ends here. next line deals with another user) ================ router.log =================== 11-MAY-1999 07:53:58.39 %PROCESS, =================================================== 11-MAY-1999 07:53:58.39 %PROCESS, Processing entry number 63 11-MAY-1999 07:53:58.40 %PROCESS, Status from READ_INFO was 00000001 11-MAY-1999 07:53:58.46 %PROCESS, ... Header rewrite of david@wherever.co.il failed 001582FC 11-MAY-1999 07:53:58.46 %PROCESS, ... Header rewrite of zev@HADASSAH.org.IL failed 00000000 11-MAY-1999 07:53:58.47 %PROCESS, ... Header rewrite of "leo::steve"@HADASSAH.org.IL failed 00000000 11-MAY-1999 07:53:58.47 %PROCESS, ... Header rewrite of david@wherever.CO.IL failed 00000000 11-MAY-1999 07:53:58.49 %PROCESS, Recipient #1: 11-MAY-1999 07:53:58.49 %PROCESS, Recipient #2: <"leo::steve"@HADASSAH.org.IL> 11-MAY-1999 07:53:58.49 %REWRITE, Applying rewrite rule: <{USER}@HADASSAH.ORG.IL> => <{USER}@MAIL.HADASSAH.ORG.IL> to: 11-MAY-1999 07:53:58.50 %FINDPATH, Site-spec expand on MAIL.HADASSAH.ORG.IL err=00000000 11-MAY-1999 07:53:58.50 %FINDPATH, domain name MAIL.HADASSAH.ORG.IL matched path pattern MAIL.HADASSAH.ORG.IL 11-MAY-1999 07:53:58.50 %PROCESS, Rewrote as - next hop MAIL.HADASSAH.ORG.IL, path 1 11-MAY-1999 07:53:58.50 %FINDALIAS, no alias found for zev 11-MAY-1999 07:53:58.51 %PROCESS, no alias found for zev 11-MAY-1999 07:53:58.51 %PROCESS, this is just a local delivery 11-MAY-1999 07:53:58.51 %REWRITE, Applying rewrite rule: <{USER}@HADASSAH.ORG.IL> => <{USER}@MAIL.HADASSAH.ORG.IL> to: <"leo::steve"@HADASSAH.org.IL> 11-MAY-1999 07:53:58.51 %FINDPATH, Site-spec expand on MAIL.HADASSAH.ORG.IL err=00000000 11-MAY-1999 07:53:58.51 %FINDPATH, domain name MAIL.HADASSAH.ORG.IL matched path pattern MAIL.HADASSAH.ORG.IL 11-MAY-1999 07:53:58.52 %PROCESS, Rewrote <"leo::steve"@HADASSAH.org.IL> as <"leo::steve"@MAIL.HADASSAH.ORG.IL> - next hop MAIL.HADASSAH.ORG.IL, path 1 11-MAY-1999 07:53:58.52 %FINDALIAS, no alias found for "leo::steve" 11-MAY-1999 07:53:58.52 %PROCESS, no alias found for "leo::steve" 11-MAY-1999 07:53:58.52 %PROCESS, this is just a local delivery 11-MAY-1999 07:53:58.54 %PROCESS, Adding to LOCAL path: zev. 11-MAY-1999 07:53:58.55 %PROCESS, Adding to LOCAL path: "leo::steve". 11-MAY-1999 07:53:58.57 %PROCESS, Path LOCAL gets 2 rcpts, entry number 50 +--------+------------------+------------------------------+---------------+ ! NAJMAN KAHANA ! Hadassah University Hospital ! thanks, ! ! Najman@hadassah.org.il ! Jerusalem, Israel ! we have our ! ! ! (visit our capital soon) ! own viruses ! +--------+------------------+------------------------------+---------------+ ================================================================================ Archive-Date: Tue, 11 May 1999 07:00:19 -0700 Message-ID: <000f01be9bb7$79581a10$010020ac@sysman_home.deltatel.ru> From: "Ruslan R. Laishev" Reply-To: MX-List@MadGoat.com To: "Matt Madison" , CC: Subject: Re: MX Local problem Date: Tue, 11 May 1999 18:06:29 +0400 Hi ! I suppose that this is situation is take place very frequently. May be you can add some functionality for retrying in this case for several times? It would be great ! Thankyou. -----Original Message----- From: Matt Madison To: Laishev@dls.net Cc: rozenfeld@dls.net Date: 11 ΝΑΡ 1999 Η. 18:43 Subject: RE: MX Local problem >>I have a problem using of MX-local process, MX_LOCAL__2.LOG follows: >[...] >>%RMS-F-FLK, file currently locked by another user >[...] >>What is problem here ? > >From the traceback you sent, it looks like it was trying to read the >MX configuration file (usually MX_DIR:MX_CONFIG.MXCFG), but the file >must be open for writing by some other process. > >-Matt > >-- >Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA >madison@madgoat.com http://www.madgoat.com > ================================================================================ Archive-Date: Fri, 14 May 1999 08:34:52 -0700 Date: Fri, 14 May 1999 11:23:14 EST5EDT4,M4.1.0,M10.5.0 From: Kamrul Ahsan Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: kamrul@ycvax.york.cuny.edu Message-ID: <009D8184.9EE5CEE0.17@ycvax.york.cuny.edu> Subject: DCL to restart dying SMTP server process Hello everybody: Long time ago someone posted on this list what I am looking for-- a DCL .COM file to restart the MX processes. For last few days MX SMTP Server is dying every few hour. I am running MX 4.2 on VMS 5.5. Before I can find out why it's dying I need to keep the mail server running. I'll appreciate if somebody could mail the DCL .COM file to me. Thanks in advance. Kamrul Ahsan Kamrul@york.cuny.edu ================================================================================ Archive-Date: Fri, 14 May 1999 08:43:14 -0700 Date: Fri, 14 May 1999 10:43:03 -0500 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: kamrul@ycvax.york.cuny.edu Message-ID: <009D817F.01F0C6E9.8@goat.process.com> Subject: RE: DCL to restart dying SMTP server process Kamrul Ahsan writes: > >Long time ago someone posted on this list what I am looking for-- >a DCL .COM file to restart the MX processes. For last few days >MX SMTP Server is dying every few hour. I am running MX 4.2 on >VMS 5.5. Before I can find out why it's dying I need to keep >the mail server running. I'll appreciate if somebody could mail >the DCL .COM file to me. Thanks in advance. > The crashing will probably stop if you install the update found in [.MX.MX042.PATCH] on ftp.madgoat.com or ftp.wku.edu. The .COM file you want is MX_WATCHDOG.COM: ftp://ftp.madgoat.com/mx/contrib/mx_watchdog.com Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www2.wku.edu/hunter/ ================================================================================ Archive-Date: Fri, 21 May 1999 14:38:43 -0700 Date: Fri, 21 May 1999 16:41:47 -0500 From: system@niuhep.physics.niu.edu Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009D8731.4800E59E.7@niuhep.physics.niu.edu> Subject: recommended ecos for 5.1 Hello, I thought I saw a message a couple of weeks ago suggesting two of the ECOs as being Good Things (TM). Things seem to moving smoothly here so I am somewhat less that motivated to make lots of changes if the improvements aren't significant. Robert ================================================================================ Archive-Date: Sat, 22 May 1999 11:34:55 -0700 Sender: madison@MadGoat.Com Date: Sat, 22 May 1999 11:34:49 -0700 From: Matt Madison Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: system@niuhep.physics.niu.edu Message-ID: <009D87CF.90B9AB38.21@MadGoat.Com> Subject: RE: recommended ecos for 5.1 > I thought I saw a message a couple of weeks ago suggesting two of >the ECOs as being Good Things (TM). Things seem to moving smoothly >here so I am somewhat less that motivated to make lots of changes if >the improvements aren't significant. The two ECOs recommended at http://www.madgoat.com/mx51_patches.html are worth installing, since they fix some bugs that have fairly high impact. For the rest of them, read the descriptions to see if they might apply to you. -Matt -- Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA madison@madgoat.com http://www.madgoat.com ================================================================================ Archive-Date: Thu, 27 May 1999 14:14:31 -0700 Date: Thu, 27 May 1999 16:17:44 -0500 From: system@niuhep.physics.niu.edu Reply-To: MX-List@MadGoat.com To: MX-LIST@MADGOAT.COM Message-ID: <009D8BE4.EA736C54.5@niuhep.physics.niu.edu> Subject: relay block problem In MX_DEVICE:[MX.SMTP]SMTP_SERVER_NIUHEP.LOG; MX SMTP server: rejected message from to sent by [170.182.151.131] due to disabled relay ucx sho host 170.182.151.131 %UCX-W-NORECORD, Information not found -RMS-E-RNF, record not found NIUHEP$ ucx sho host Crittenden.k12.ky.us BIND database Server: 131.156.1.11 NETMGR.CSO.NIU.EDU Host address Host name 170.182.151.131 CRITTENDEN.K12.KY.US Thoughts? Robert ================================================================================ Archive-Date: Thu, 27 May 1999 15:24:35 -0700 Date: Thu, 27 May 1999 17:27:41 -0500 From: system@niuhep.physics.niu.edu Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009D8BEE.AFF6D51B.14@niuhep.physics.niu.edu> Subject: local rejection Hello, I am confused (as if that were news). mx 5.1 and ecos 2 and 4. I am getting a rejection when I try to send a mail message I'm not sure where or how it is getting rejected $ sh log /full MX_ANTI_SPAM_DEBUG "MX_ANTI_SPAM_DEBUG" [exec] = "8" (LNM$SYSTEM_TABLE) SMTP_SERVER_NIUHEP.LOG; shows no rejections mx_antispam_log.log_.... has no record of the message whatsoever (nor does any log file) the following is a full que listing of the message that got rejected. ---------------------------------------- Entry: 2, Origin: [Local] Status: FINISHED, size: 45 bytes Created: 27-MAY-1999 16:57:02.34, expires 26-JUN-1999 16:57:02.34 Last modified 27-MAY-1999 16:57:30.68 Recipient #1: ---------------------------------------- the following is the message I got telling me that it was rejected: ---------------------------------------- From: MX%"Postmaster@niuhep.physics.niu.edu" "MX Mail Delivery System" 27-MAY -1999 16:57:31.42 To: MX%"morphis@niuhep.physics.niu.edu" CC: Subj: Message delivery failed Return-Path: <> From: MX Mail Delivery System To: morphis@niuhep.physics.niu.edu Date: Thu, 27 May 1999 16:57:30 -0500 Subject: Message delivery failed MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary="=_yR/H.3M7tZlrcPxL,0J-,kj,+cw4(D+3-C/P:(dD6gz/dqd4tn" --=_yR/H.3M7tZlrcPxL,0J-,kj,+cw4(D+3-C/P:(dD6gz/dqd4tn Content-Type: text/plain This is a report on the delivery status of your message. Message-ID: <009D8BEA.77406425.2@niuhep.physics.niu.edu> Subject: relay check --Failed delivery to: Address: SPSCHAT-L@LISTS.ACS.NIU.EDU Status: action not taken: mailbox name not allowed --=_yR/H.3M7tZlrcPxL,0J-,kj,+cw4(D+3-C/P:(dD6gz/dqd4tn Content-Type: message/delivery-status Reporting-MTA: dns;niuhep.physics.niu.edu Arrival-Date: Thu, 27 May 1999 16:57:02 -0500 Final-Recipient: rfc822;SPSCHAT-L@LISTS.ACS.NIU.EDU Action: failed Status: 5.0.0 (Unspecified permanent failure) Remote-MTA: dns;LISTS.ACS.NIU.EDU (131.156.7.2) Diagnostic-Code: smtp;action not taken: mailbox name not allowed 553 We do not relay non-local mail, sorry. Last-Attempt-Date: Thu, 27 May 1999 16:57:29 -0500 --=_yR/H.3M7tZlrcPxL,0J-,kj,+cw4(D+3-C/P:(dD6gz/dqd4tn Content-Type: message/rfc822 Received: by niuhep.physics.niu.edu (MX V5.1-X An7j) id 2; Thu, 27 May 1999 16:57:28 -0500 Date: Thu, 27 May 1999 16:57:28 -0500 From: morphis@niuhep.physics.niu.edu To: SPSCHAT-L@LISTS.ACS.NIU.EDU Message-ID: <009D8BEA.77406425.2@niuhep.physics.niu.edu> Subject: relay check hi, I am having problems sending this to you. --=_yR/H.3M7tZlrcPxL,0J-,kj,+cw4(D+3-C/P:(dD6gz/dqd4tn-- ---------------------------------------- Local domain patterns for SMTP relay checks: *.NIU.EDU NIU.EDU Inside IP networks/hosts: 131.156.0.0 netmask 255.255.0.0 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: enabled Realtime Blackhole List check: disabled Local domain patterns for SMTP relay checks: *.NIU.EDU NIU.EDU 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. ================================================================================ Archive-Date: Thu, 27 May 1999 16:19:57 -0700 Sender: madison@MadGoat.Com Date: Thu, 27 May 1999 16:19:52 -0700 From: Matt Madison Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: system@niuhep.physics.niu.edu Message-ID: <009D8BE5.36B652AC.3@MadGoat.Com> Subject: RE: relay block problem >MX SMTP server: rejected message from to > sent by [170.182.151.131] due to disabled relay [...] >Thoughts? My guess is it's the extra dot at the end of the destination address that is throwing off the anti-relay code. The dot really shouldn't be there, but I'll look into making the checks more tolerant. -Matt -- Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA madison@madgoat.com http://www.madgoat.com ================================================================================ Archive-Date: Thu, 27 May 1999 16:25:17 -0700 Sender: madison@MadGoat.Com Date: Thu, 27 May 1999 16:25:12 -0700 From: Matt Madison Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: system@niuhep.physics.niu.edu Message-ID: <009D8BE5.F58E6BD3.18@MadGoat.Com> Subject: RE: local rejection >I am getting a rejection when I try to send a mail message > >I'm not sure where or how it is getting rejected The new DSN-style delivery reports aren't always easy to read, that's for sure. The report is being generated by MX on your local system in response to an SMTP error it got back from the destination system: This is the address MX was trying to deliver to: >Final-Recipient: rfc822;SPSCHAT-L@LISTS.ACS.NIU.EDU >Action: failed >Status: 5.0.0 (Unspecified permanent failure) This is the remote system's name and address: >Remote-MTA: dns;LISTS.ACS.NIU.EDU (131.156.7.2) and this is the error code that was reported, followed by the text of the response generated during the SMTP session: >Diagnostic-Code: smtp;action not taken: mailbox name not allowed > 553 We do not relay non-local mail, sorry. So it sounds like LISTS.ACS.NIU.EDU may have a bit of a configuration problem. -Matt -- Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA madison@madgoat.com http://www.madgoat.com ================================================================================ Archive-Date: Thu, 27 May 1999 16:31:36 -0700 Message-ID: <3.0.6.32.19990527163121.02e50df0@ous.edu> Date: Thu, 27 May 1999 16:31:21 -0700 To: MX-List@MadGoat.com From: Dan Sugalski Reply-To: MX-List@MadGoat.com Subject: RE: relay block problem In-Reply-To: <009D8BE5.36B652AC.3@MadGoat.Com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 04:19 PM 5/27/99 -0700, Matt Madison wrote: >>MX SMTP server: rejected message from to >> sent by [170.182.151.131] due to disabled relay >[...] >>Thoughts? > >My guess is it's the extra dot at the end of the destination address that >is throwing off the anti-relay code. The dot really shouldn't be there, but >I'll look into making the checks more tolerant. The dot's legal, if I remember the RFC's correctly. (Though I very well might not... :) Certainly legal for DNS names. 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, 28 May 1999 06:08:03 -0700 Date: Fri, 28 May 1999 08:11:16 -0500 From: system@niuhep.physics.niu.edu Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009D8C6A.1F8F4B4E.15@niuhep.physics.niu.edu> Subject: RE: relay block problem ]> ]My guess is it's the extra dot at the end of the destination address that ]is throwing off the anti-relay code. Ah! I never even saw it. That makes sense. Thanks, Robert