RE: SMTP non-delivery report -- MIDRANGE-L

PING RMTSYS(TWITTER.COM)

Verifying connection to host system TWITTER.COM at address
199.59.148.83.
PING reply 1 from 199.59.148.83 took 86 ms. 256 bytes. TTL 47.

PING reply 2 from 199.59.148.83 took 86 ms. 256 bytes. TTL 47.

PING reply 3 from 199.59.148.83 took 87 ms. 256 bytes. TTL 47.

PING reply 4 from 199.59.148.83 took 92 ms. 256 bytes. TTL 47.

PING reply 5 from 199.59.148.83 took 136 ms. 256 bytes. TTL 47.

Round-trip (in milliseconds) min/avg/max = 86/97/136.

Connection verification statistics: 5 of 5 successful (100 %).

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rich Loeber
Sent: Thursday, April 14, 2011 1:07 PM
To: Midrange Systems Technical Discussion
Subject: Re: SMTP non-delivery report

Don,

Are you able to ping any outside server? Try this one:

PING RMTSYS(TWITTER.COM)

It should resolve the IP address and give you a good test fairly
quickly.
Look at the joblog as soon as the ping is done.

Rich Loeber - @richloeber
Kisco Information Systems
[1]http://www.kisco.com
SDG

------------------------------------------------------------------------
--

On 4/14/2011 1:59 PM, Don Cavaiani wrote:

So far so good, Rich - just passed that test.

-----Original Message-----
From: [2]midrange-l-bounces@xxxxxxxxxxxx
[[3]mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rich Loeber
Sent: Thursday, April 14, 2011 12:49 PM
To: Midrange Systems Technical Discussion
Subject: Re: SMTP non-delivery report

Hi Don,

I've seen this before at a client location. It is usually tied to a
DNS
failure of some sort. Maybe your DNS servers have changed, but the
TCP/IP
configuration on your i has not been updated?

Go to the CFGTCP menu in the OS and run option #12. The DNS servers
are
set up there. You should have at least 2, a primary and a backup.
Try
pinging them from the command line to make sure you can get to them.

Rich Loeber - @richloeber
Kisco Information Systems
[1][4]http://www.kisco.com
SDG

------------------------------------------------------------------------
--

On 4/14/2011 12:10 PM, Don Cavaiani wrote:

I have a CLP which does a SNDDST (then hands to Exchange Server) -
to
occasionally send a fixed message to about 400 Suppliers.

I have run this many times in the past, but now it only seems to be
working if I use an Email address of one of our internal Users.

If I now use an external email address, the exchange server message
tracking log reports: SMTP: 'Non-Delivered Report (NDR) generated', and
no email goes to the external address.

However, email mail routing exclusively thru exchange IS working both
ways - inbound and outbound.

References

Visible links
1. [5]http://www.kisco.com/
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: [6]MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: [7]http://lists.midrange.com/mailman/listinfo/midrange-l
or email: [8]MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
[9]http://archive.midrange.com/midrange-l.

References

Visible links
1. http://www.kisco.com/
2. mailto:midrange-l-bounces@xxxxxxxxxxxx
3. mailto:midrange-l-bounces@xxxxxxxxxxxx
4. http://www.kisco.com/
5. http://www.kisco.com/
6. mailto:MIDRANGE-L@xxxxxxxxxxxx
7. http://lists.midrange.com/mailman/listinfo/midrange-l
8. mailto:MIDRANGE-L-request@xxxxxxxxxxxx
9. 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.