|
Since we have an internal mail server (Exchange), we target that server as our MAILROUTER, and specify Firewall(*YES). Our network firewall knows that the server (Mailrouter) will be handling email, so it's allowed through the firewall. When we mistakenly changed FIREWALL to *NO, the as400 tried (with varying degrees of success) to deliver mail directly to the destination domain. MAILROUTER does not point to the firewall, unless your firewall acts as a mail proxy.... Eric DeLong Sally Beauty Company MIS-Project Manager (BSG) 940-898-7863 or ext. 1863 -----Original Message----- From: Jeff Crosby [mailto:jlcrosby@xxxxxxxxxxxxxxxx] Sent: Thursday, April 01, 2004 3:18 PM To: 'Midrange Systems Technical Discussion' Subject: RE: Strange email sending problem > Jeff, we had similar problems due to firewall issues. Try > CHGSMTPA (F4), page down to MAILROUTER and FIREWALL. When > you have a mailrouter defined, Firewall indicates that all > mail should go through the defined route to bypass firewall > issues. If FIREWALL(*NO), then your as400 is trying to talk > to the remote mailservers directly. OK, now this might be promising. Ours is MAILROUTER(*NONE) FIREWALL(*NO). The path to the outside world is as follows: iSeries --> Cisco 2621 Router --> Cisco 506e PIX --> Internet The IP addresses are: iSeries is 192.168.0.1 Cisco 2621 router Internal IP 192.168.0.250 External IP 192.168.10.2 Cisco 506 PIX Internal IP 192.168.10.1 External IP xxx.xxx.xxx.xxx Are you saying MAILROUTER should point to 192.168.0.250? (192.168.0.250 is already set up as the default route.) Or is MAILROUTER supposed to point to the PIX internal IP? Or should it point to something outside the firewall? And then FIREWALL should say what? *YES or *NO? -- Jeff Crosby Dilgard Frozen Foods, Inc. P.O. Box 13369 Ft. Wayne, IN 46868-3369 260-422-7531 The opinions expressed are my own and not necessarily the opinion of my company. Unless I say so. > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DeLong, Eric > Sent: Thursday, April 01, 2004 3:40 PM > To: 'Midrange Systems Technical Discussion' > Subject: RE: Strange email sending problem > > > Eric DeLong > Sally Beauty Company > MIS-Project Manager (BSG) > 940-898-7863 or ext. 1863 > > > > -----Original Message----- > From: Jeff Crosby [mailto:jlcrosby@xxxxxxxxxxxxxxxx] > Sent: Thursday, April 01, 2004 2:19 PM > To: 'Midrange Systems Technical Discussion' > Subject: RE: Strange email sending problem > > > > What happens when you try to send a message from the iSeries? > > Does it get rejected? Is it poorly formatted? > > I get this back (I changed the phone number to all x's): > > <what I get back> > > NOT ABLE TO DELIVER MAIL TO SOME/ALL RECIPIENTS. > REPLY CODES WITH FIRST DIGIT = '4' OR '5' ARE ERROR REPLIES. > ERRORS THAT DO NOT HAVE ERROR REPLY CODES MAY EXIST. > > HOST AS400 NOT ABLE TO DELIVER MAIL TO FOLLOWING RECIPIENT(S): > <xxxxxxxxxx@xxxxxxxxxxx> > RETRIES EXHAUSTED WHILE ATTEMPTING TO CONNECT TO REMOTE HOST CWEMAIL. > > ** TEXT OF MAIL FOLLOWS ** > Received: from jlcrosby([192.168.0.11]) by AS400.DILGARD.COM > (IBM OS/400 SMTP V05R02M00) with TCP; Wed, 31 Mar 2004 14:47:13 -0500 > From: "Jeff Crosby" <jlcrosby@xxxxxxxxxxxxxxxx> > To: <xxxxxxxxxx@xxxxxxxxxxx> > Subject: Test > Date: Wed, 31 Mar 2004 14:48:08 -0500 > MIME-Version: 1.0 > Content-Type: text/plain; > charset="us-ascii" > Content-Transfer-Encoding: 7bit > X-Mailer: Microsoft Office Outlook, Build 11.0.5510 > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 > Thread-Index: AcQXWRYTQ/afYINKRliQP51a7W4gAg== > > </what I get back> > > Here are the internet headers on the above: > > <internetheaders> > > DATE: Wed, 31 Mar 2004 16:18:59 -0500 > FROM: QGATE@xxxxxxxxxxxxxxxxx > TO: <jlcrosby@xxxxxxxxxxxxxxxx> > SUBJECT: UNDELIVERABLE MAIL > > </internetheaders> > > -- > Jeff Crosby > Dilgard Frozen Foods, Inc. > P.O. Box 13369 > Ft. Wayne, IN 46868-3369 > 260-422-7531 > > The opinions expressed are my own and not necessarily the > opinion of my company. Unless I say so. > > > > _______________________________________________ > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list To post a message email: > MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change > list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, > please take a moment to review the archives at > http://archive.midrange.com/midrange-l. > > > _______________________________________________ > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list To post a message email: > MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change > list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, > please take a moment to review the archives at > http://archive.midrange.com/midrange-l. > > > _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.