RE: FW: email help -- MIDRANGE-L

I'll give that a try.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, September 26, 2011 3:47 PM
To: Midrange Systems Technical Discussion
Subject: RE: FW: email help

If it's using the stuff in CHGSMTPA then a REALLY good tool for debugging
this is
TRCTCPAPP APP(*SMTPCLT)
Try sending an email then use
TRCTCPAPP APP(*SMTPCLT) SET(*OFF)

Our network consultant even was impressed by the output. You see all the
crud from the remote end like "Error 552 yadda yadda yadda". It shows you
how it resolves which MX record to use and everything.

Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: "Paul Nelson" <nelsonp@xxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 09/26/2011 03:41 PM
Subject: RE: FW: email help
Sent by: midrange-l-bounces@xxxxxxxxxxxx

No, it uses the server name in CHGSMTPA. I've always had to have the
network
guys change a setting in the Exchange server to tell it to trust whatever
is
coming from the AS/400-iSeries-System i.

Paul Nelson
Office 512-392-2577
Cell 708-670-6978
nelsonp@xxxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Wills
Sent: Monday, September 26, 2011 1:56 PM
To: Midrange Systems Technical Discussion
Subject: Re: FW: email help

Does esend have it's own configuration?

On Monday, September 26, 2011, Smith, Mike wrote:

We are implementing a new Exchange server. Currently the

old(192.168.0.17)

and the new(192.168.0.35) are running parallel.

We use ESEND to send emails(spool files etc) to users and this passes to
the exchange server.

I have looked at CHGSMTPA. We have Mail Router set to *NONE.

There is nothing in the Host file pointing to the mail server.

Yet it works, I just can't figure out how its pointing to the old

exchange

server, or how to change it to the new exchange server.

Does this make sense? Any ideas?

Thanks

MIke
NOTICE: This message, including any attachment, is intended as a
confidential and privileged communication. If you have received this

message

in error, or are not the named recipient(s), please immediately notify

the

sender and delete this message.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx <javascript:;>
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx <javascript:;>
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
--
Mike Wills
http://mikewills.me
--
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.

NOTICE: This message, including any attachment, is intended as a confidential and privileged communication. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this message.