RE: ims queues

2001-09-18 Thread Tener, Richard

Yes the outbound messages are the ones that seem to get stuck.  I looked at
details of the messages and most of them said (host unreachable) but there
were two other ones that said (network error during host resolution).  Im
not sure what that means but I think its on their side. (hopefully)  Also if
you can let me know how to do a MX Record lookup.  Is this just looking up a
web site or do I do it through my dns.  I thank you for your response and
appreciate it so much. 

Thank you
Richard Tener
[EMAIL PROTECTED]

 -Original Message-
From: Bueffel, Scott M - CNF [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 17, 2001 7:20 PM
To: Exchange Discussions
Subject: RE: ims queues


Richard, THERE IS NO NEED TO YELL.  You haven't said with it is the inbound
or outbound queue.  I will assume outbound since it would be rare for
inbound messages to be stuck.  If you are not relaying to another server it
is very common to have messages stuck in the outbound delivery queue.  If
you click on the Details button it will tell you why the message has not
been delivered.  The most common reason will be Host Unavailable or Host
Undeliverable.  That means that for any number of reasons your server could
not initiate a TCP session with the recipients mailhost.  If most of your
messages are going through then there is a probably nothing wrong.
Especially if the messages in question go after awhile.  You can test a
connection by doing an MX record lookup for the host in question and then
initiate a telnet session to port 25 to that host from your Exchange server.
If that fails, then your IMS will be unable to send the message.

Scott.

-Original Message-
From: Richard Tener [mailto:[EMAIL PROTECTED]] 
Sent: Monday, September 17, 2001 12:49 PM
To: Exchange Discussions
Subject: ims queues


Hello,


I HAVE EXCHANGE SERVER 5.5 SP4 RUNNING ON WINDOWS NT 4.0 SP6. EVERYDAY I
CHECK THE IMS QUEUES AND IT SHOWS SOME MESSAGES ARE STUCK IN THE QUEUES FOR
A LONG TIME.  THE MESSAGE WILL KEEP TRYING FOR SOMETIME BUT WILL STAY IN
THERE FOR EVER.  ALSO OTHER MESSAGES ARE GOING OUT AND WE ALSO RECEIVE ALOT
OF MESSAGES WITH NO PROBLEM.  I ALSO NOTICED THAT THERE IS ONE COMPANY THAT
ALWAYS GET STUCK IN THE QUEUE.  I DONT HAVE MESSAGE TRACKING ON BECAUSE I
DONT KNOW HOW TO SET THAT UP.  ALSO IF ITS THE OTHER COMPANYS SERVER PLEASE
LET ME KNOW WHY IT WOULD BE THEIR SERVER.  THANK YOU FOR YOUR TIME.

RICHARD TENER
[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: ims queues

2001-09-18 Thread Atkinson, Daniel


 Yes the outbound messages are the ones that seem to get 
 stuck.  I looked at
 details of the messages and most of them said (host 
 unreachable) but there
 were two other ones that said (network error during host 
 resolution).

it means there was an error trying to resolve the remote host name to an IP
address (DNS query). perhaps your DNS has issues.

 Im
 not sure what that means but I think its on their side. 
 (hopefully)  Also if
 you can let me know how to do a MX Record lookup.  

go to command prompt, type 'nslookup' to start nslookup utility

type the command 'set type=mx' and hit enter

enter the domain you want to find the MX record for.

if you have 95/98 this won't work, go to www.tucows.com and download a DNS
utility.

regards
dan.

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: ims queues

2001-09-18 Thread Joyce, Louis

Just out of interest.

Do you have to do the 'nslookup'from your exchange server or can you do it
from an NT workstation command prompt?

Many thanks

Regards

Louis Joyce

-Original Message-
From: Atkinson, Daniel [mailto:[EMAIL PROTECTED]]
Sent: 18 September 2001 13:54
To: Exchange Discussions
Subject: RE: ims queues



 Yes the outbound messages are the ones that seem to get 
 stuck.  I looked at
 details of the messages and most of them said (host 
 unreachable) but there
 were two other ones that said (network error during host 
 resolution).

it means there was an error trying to resolve the remote host name to an IP
address (DNS query). perhaps your DNS has issues.

 Im
 not sure what that means but I think its on their side. 
 (hopefully)  Also if
 you can let me know how to do a MX Record lookup.  

go to command prompt, type 'nslookup' to start nslookup utility

type the command 'set type=mx' and hit enter

enter the domain you want to find the MX record for.

if you have 95/98 this won't work, go to www.tucows.com and download a DNS
utility.

regards
dan.

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: ims queues

2001-09-18 Thread Atkinson, Daniel

your DNS settings are messed up

www.theircompany.com is not a valid DNS server. 127.0.0.1 is your loopback
address, so unless you have DNS running on the machine you are querying
from, nothing will happen.

go to 'networking' in the control panel, look under protocols, look at the
properties for TCP/IP. 

on the DNS tab, specify some valid DNS servers. 

nslookup always defaults to the first server in the list, but you can use
any server by issuing the command 'server xx.xx.xx.xx'

 I also did a telnet to port 25 but it returned somthing like 
 esmtp sendmail
 8.9.1a/8.9.1: then the date at a specific time (met DST)

this means you have connected ok. if you turn on 'local echo' in your telnet
application you can see commands as you type them.

to test the server, try:

MAIL FROM: [EMAIL PROTECTED] (hit enter)
RCPT TO: [EMAIL PROTECTED] (hit enter)
DATA: (hit enter)
type a message
type a dot on a new line and hit enter to finish.

hth.

dan.

 ok so I did a MX record lookup and it returned a 
 
 SERVER: www.theircompany.com
 IP ADDRESS: 127.0.0.1
 
 DNS: REQUEST TIMED OUT.
 REQUEST TIMED OUT FOR 2 SECONDS
 
 DNS REQUEST TO WWW.THEIRCOMPANY.COM TIMED OUT
 

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: ims queues

2001-09-18 Thread Atkinson, Daniel


 SERVER: www.theircompany.com
 IP ADDRESS: 127.0.0.1

whoops, think i just realised that you have substituted dummy
addresses...d'oh

dan.

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: ims queues

2001-09-18 Thread Tener, Richard

i did it from another server on my network (its not my exchange server
though)

-Original Message-
From: Joyce, Louis [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 18, 2001 9:22 AM
To: Exchange Discussions
Subject: RE: ims queues


Just out of interest.

Do you have to do the 'nslookup'from your exchange server or can you do it
from an NT workstation command prompt?

Many thanks

Regards

Louis Joyce

-Original Message-
From: Atkinson, Daniel [mailto:[EMAIL PROTECTED]]
Sent: 18 September 2001 13:54
To: Exchange Discussions
Subject: RE: ims queues



 Yes the outbound messages are the ones that seem to get 
 stuck.  I looked at
 details of the messages and most of them said (host 
 unreachable) but there
 were two other ones that said (network error during host 
 resolution).

it means there was an error trying to resolve the remote host name to an IP
address (DNS query). perhaps your DNS has issues.

 Im
 not sure what that means but I think its on their side. 
 (hopefully)  Also if
 you can let me know how to do a MX Record lookup.  

go to command prompt, type 'nslookup' to start nslookup utility

type the command 'set type=mx' and hit enter

enter the domain you want to find the MX record for.

if you have 95/98 this won't work, go to www.tucows.com and download a DNS
utility.

regards
dan.

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



Re: ims queues

2001-09-18 Thread missy koslosky

Desktop will work.
- Original Message - 
From: Joyce, Louis [EMAIL PROTECTED]
To: Exchange Discussions [EMAIL PROTECTED]
Sent: Tuesday, September 18, 2001 9:22 AM
Subject: RE: ims queues


Just out of interest.

Do you have to do the 'nslookup'from your exchange server or can you do it
from an NT workstation command prompt?

Many thanks

Regards

Louis Joyce

-Original Message-
From: Atkinson, Daniel [mailto:[EMAIL PROTECTED]]
Sent: 18 September 2001 13:54
To: Exchange Discussions
Subject: RE: ims queues



 Yes the outbound messages are the ones that seem to get 
 stuck.  I looked at
 details of the messages and most of them said (host 
 unreachable) but there
 were two other ones that said (network error during host 
 resolution).

it means there was an error trying to resolve the remote host name to an IP
address (DNS query). perhaps your DNS has issues.

 Im
 not sure what that means but I think its on their side. 
 (hopefully)  Also if
 you can let me know how to do a MX Record lookup.  

go to command prompt, type 'nslookup' to start nslookup utility

type the command 'set type=mx' and hit enter

enter the domain you want to find the MX record for.

if you have 95/98 this won't work, go to www.tucows.com and download a DNS
utility.

regards
dan.

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: ims queues

2001-09-18 Thread Garrish, Robert B.

Dear Richard,

Host unreachable may mean that the other company's e-mail server
is down.

network error during host resolution may mean that your Exchange
Server does not recognize the e-mail domain.

In the Exchange Admin program, on the IMC, on the Connections tab,
Message Delivery is set to use DNS.  If this is correct, and there is no
Internal MX Record for this particular e-mail domain (and there should not
be), then you are at the mercy of your ISP's DNS.
In this case, when you run nslookup, you ought to change your
default Server.  When you run nslookup, it uses information from your
Internal DNS Server and then from your ISP's DNS Server.  Somebody else's
DNS Server may contain an MX Record for the e-mail domain your are
attempting to send to.  Then, contact your company's ISP, and inform them
that a particular MX Record has not been propagated to their DNS Server.
Let them see if there is something that they can do.

For about a month and a half, I was unable to send posts to this
list, because Wawa changed ISPs, and the new ISP had no idea (no MX Record)
who @ls.swynk.com was.
Oddly enough, no one from the list even noticed that I was not
posting or replying.
Go figure.


Rob Garrish
Exchange Administrator
Wawa Inc.
610-558-8371
[EMAIL PROTECTED]



-Original Message-
From: Tener, Richard [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 18, 2001 09:14 AM
To: Exchange Discussions
Subject: RE: ims queues


ok so I did a MX record lookup and it returned a 

SERVER: www.theircompany.com
IP ADDRESS: 127.0.0.1

DNS: REQUEST TIMED OUT.
REQUEST TIMED OUT FOR 2 SECONDS

DNS REQUEST TO WWW.THEIRCOMPANY.COM TIMED OUT

I also did a telnet to port 25 but it returned somthing like esmtp sendmail
8.9.1a/8.9.1: then the date at a specific time (met DST)

-Original Message-
From: Martin Blackstone [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 18, 2001 8:55 AM
To: Exchange Discussions
Subject: RE: ims queues


Start, Run, CMD, NSLookup, Set Type=MX, type in the domain name and see
what you get.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Tener, Richard
Sent: Tuesday, September 18, 2001 5:51 AM
To: Exchange Discussions
Subject: RE: ims queues


Yes the outbound messages are the ones that seem to get stuck.  I looked
at details of the messages and most of them said (host unreachable) but
there were two other ones that said (network error during host
resolution).  Im not sure what that means but I think its on their side.
(hopefully)  Also if you can let me know how to do a MX Record lookup.
Is this just looking up a web site or do I do it through my dns.  I
thank you for your response and appreciate it so much. 

Thank you
Richard Tener
[EMAIL PROTECTED]

 -Original Message-
From: Bueffel, Scott M - CNF [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 17, 2001 7:20 PM
To: Exchange Discussions
Subject: RE: ims queues


Richard, THERE IS NO NEED TO YELL.  You haven't said with it is the
inbound or outbound queue.  I will assume outbound since it would be
rare for inbound messages to be stuck.  If you are not relaying to
another server it is very common to have messages stuck in the outbound
delivery queue.  If you click on the Details button it will tell you why
the message has not been delivered.  The most common reason will be Host
Unavailable or Host Undeliverable.  That means that for any number of
reasons your server could not initiate a TCP session with the recipients
mailhost.  If most of your messages are going through then there is a
probably nothing wrong. Especially if the messages in question go after
awhile.  You can test a connection by doing an MX record lookup for the
host in question and then initiate a telnet session to port 25 to that
host from your Exchange server. If that fails, then your IMS will be
unable to send the message.

Scott.

-Original Message-
From: Richard Tener [mailto:[EMAIL PROTECTED]] 
Sent: Monday, September 17, 2001 12:49 PM
To: Exchange Discussions
Subject: ims queues


Hello,


I HAVE EXCHANGE SERVER 5.5 SP4 RUNNING ON WINDOWS NT 4.0 SP6. EVERYDAY I
CHECK THE IMS QUEUES AND IT SHOWS SOME MESSAGES ARE STUCK IN THE QUEUES
FOR A LONG TIME.  THE MESSAGE WILL KEEP TRYING FOR SOMETIME BUT WILL
STAY IN THERE FOR EVER.  ALSO OTHER MESSAGES ARE GOING OUT AND WE ALSO
RECEIVE ALOT OF MESSAGES WITH NO PROBLEM.  I ALSO NOTICED THAT THERE IS
ONE COMPANY THAT ALWAYS GET STUCK IN THE QUEUE.  I DONT HAVE MESSAGE
TRACKING ON BECAUSE I DONT KNOW HOW TO SET THAT UP.  ALSO IF ITS THE
OTHER COMPANYS SERVER PLEASE LET ME KNOW WHY IT WOULD BE THEIR SERVER.
THANK YOU FOR YOUR TIME.

RICHARD TENER
[EMAIL PROTECTED]


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL

RE: ims queues

2001-09-18 Thread Choi Rex

It shouldn't matter where you run your dns query from. In some cases of
split-DNS scenarios (if you don't have your internal DNS forward to you
external), you can still run nslookup from a workstation, you will just need
to specify the address of you external DNS server so that will be where
nslookup runs it's query against. 

Rex Choi
Siemens Building Technologies


-Original Message-
From: Joyce, Louis [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 18, 2001 8:22 AM
To: Exchange Discussions
Subject: RE: ims queues


Just out of interest.

Do you have to do the 'nslookup'from your exchange server or can you do it
from an NT workstation command prompt?

Many thanks

Regards

Louis Joyce

-Original Message-
From: Atkinson, Daniel [mailto:[EMAIL PROTECTED]]
Sent: 18 September 2001 13:54
To: Exchange Discussions
Subject: RE: ims queues



 Yes the outbound messages are the ones that seem to get 
 stuck.  I looked at
 details of the messages and most of them said (host 
 unreachable) but there
 were two other ones that said (network error during host 
 resolution).

it means there was an error trying to resolve the remote host name to an IP
address (DNS query). perhaps your DNS has issues.

 Im
 not sure what that means but I think its on their side. 
 (hopefully)  Also if
 you can let me know how to do a MX Record lookup.  

go to command prompt, type 'nslookup' to start nslookup utility

type the command 'set type=mx' and hit enter

enter the domain you want to find the MX record for.

if you have 95/98 this won't work, go to www.tucows.com and download a DNS
utility.

regards
dan.

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: ims queues

2001-09-18 Thread msharik

or just do a RESTEST from your Exchange box

-Michèle
Immigration site:  http://LadySun1969.tripod.com
Our new 2001 Miata:  http://members.cardomain.com/bpituley
Tiggercam:  http://www.tiggercam.co.uk
-
Jesus saves! By using double coupons and shopping wisely. 
-


-Original Message-
From: Bueffel, Scott M - CNF [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 17, 2001 7:20 PM
To: Exchange Discussions
Subject: RE: ims queues


Richard, THERE IS NO NEED TO YELL.  You haven't said with it is the inbound
or outbound queue.  I will assume outbound since it would be rare for
inbound messages to be stuck.  If you are not relaying to another server it
is very common to have messages stuck in the outbound delivery queue.  If
you click on the Details button it will tell you why the message has not
been delivered.  The most common reason will be Host Unavailable or Host
Undeliverable.  That means that for any number of reasons your server could
not initiate a TCP session with the recipients mailhost.  If most of your
messages are going through then there is a probably nothing wrong.
Especially if the messages in question go after awhile.  You can test a
connection by doing an MX record lookup for the host in question and then
initiate a telnet session to port 25 to that host from your Exchange server.
If that fails, then your IMS will be unable to send the message.

Scott.

-Original Message-
From: Richard Tener [mailto:[EMAIL PROTECTED]] 
Sent: Monday, September 17, 2001 12:49 PM
To: Exchange Discussions
Subject: ims queues


Hello,


I HAVE EXCHANGE SERVER 5.5 SP4 RUNNING ON WINDOWS NT 4.0 SP6. EVERYDAY I
CHECK THE IMS QUEUES AND IT SHOWS SOME MESSAGES ARE STUCK IN THE QUEUES FOR
A LONG TIME.  THE MESSAGE WILL KEEP TRYING FOR SOMETIME BUT WILL STAY IN
THERE FOR EVER.  ALSO OTHER MESSAGES ARE GOING OUT AND WE ALSO RECEIVE ALOT
OF MESSAGES WITH NO PROBLEM.  I ALSO NOTICED THAT THERE IS ONE COMPANY THAT
ALWAYS GET STUCK IN THE QUEUE.  I DONT HAVE MESSAGE TRACKING ON BECAUSE I
DONT KNOW HOW TO SET THAT UP.  ALSO IF ITS THE OTHER COMPANYS SERVER PLEASE
LET ME KNOW WHY IT WOULD BE THEIR SERVER.  THANK YOU FOR YOUR TIME.

RICHARD TENER
[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: ims queues

2001-09-17 Thread Bueffel, Scott M - CNF

Richard, THERE IS NO NEED TO YELL.  You haven't said with it is the inbound
or outbound queue.  I will assume outbound since it would be rare for
inbound messages to be stuck.  If you are not relaying to another server it
is very common to have messages stuck in the outbound delivery queue.  If
you click on the Details button it will tell you why the message has not
been delivered.  The most common reason will be Host Unavailable or Host
Undeliverable.  That means that for any number of reasons your server could
not initiate a TCP session with the recipients mailhost.  If most of your
messages are going through then there is a probably nothing wrong.
Especially if the messages in question go after awhile.  You can test a
connection by doing an MX record lookup for the host in question and then
initiate a telnet session to port 25 to that host from your Exchange server.
If that fails, then your IMS will be unable to send the message.

Scott.

-Original Message-
From: Richard Tener [mailto:[EMAIL PROTECTED]] 
Sent: Monday, September 17, 2001 12:49 PM
To: Exchange Discussions
Subject: ims queues


Hello,


I HAVE EXCHANGE SERVER 5.5 SP4 RUNNING ON WINDOWS NT 4.0 SP6. EVERYDAY I
CHECK THE IMS QUEUES AND IT SHOWS SOME MESSAGES ARE STUCK IN THE QUEUES FOR
A LONG TIME.  THE MESSAGE WILL KEEP TRYING FOR SOMETIME BUT WILL STAY IN
THERE FOR EVER.  ALSO OTHER MESSAGES ARE GOING OUT AND WE ALSO RECEIVE ALOT
OF MESSAGES WITH NO PROBLEM.  I ALSO NOTICED THAT THERE IS ONE COMPANY THAT
ALWAYS GET STUCK IN THE QUEUE.  I DONT HAVE MESSAGE TRACKING ON BECAUSE I
DONT KNOW HOW TO SET THAT UP.  ALSO IF ITS THE OTHER COMPANYS SERVER PLEASE
LET ME KNOW WHY IT WOULD BE THEIR SERVER.  THANK YOU FOR YOUR TIME.

RICHARD TENER
[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: ims queues

2001-09-17 Thread Steve Rollings

DNS is a wonderful thang.

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of 
 Bueffel, Scott
 M - CNF
 Sent: Tuesday, September 18, 2001 00:20
 To: Exchange Discussions
 Subject: RE: ims queues
 
 
 Richard, THERE IS NO NEED TO YELL.  You haven't said with it 
 is the inbound
 or outbound queue.  I will assume outbound since it would be rare for
 inbound messages to be stuck.  If you are not relaying to 
 another server it
 is very common to have messages stuck in the outbound 
 delivery queue.  If
 you click on the Details button it will tell you why the 
 message has not
 been delivered.  The most common reason will be Host 
 Unavailable or Host
 Undeliverable.  That means that for any number of reasons 
 your server could
 not initiate a TCP session with the recipients mailhost.  If 
 most of your
 messages are going through then there is a probably nothing wrong.
 Especially if the messages in question go after awhile.  You 
 can test a
 connection by doing an MX record lookup for the host in 
 question and then
 initiate a telnet session to port 25 to that host from your 
 Exchange server.
 If that fails, then your IMS will be unable to send the message.
 
 Scott.
 
 -Original Message-
 From: Richard Tener [mailto:[EMAIL PROTECTED]] 
 Sent: Monday, September 17, 2001 12:49 PM
 To: Exchange Discussions
 Subject: ims queues
 
 
 Hello,
 
 
 I HAVE EXCHANGE SERVER 5.5 SP4 RUNNING ON WINDOWS NT 4.0 SP6. 
 EVERYDAY I
 CHECK THE IMS QUEUES AND IT SHOWS SOME MESSAGES ARE STUCK IN 
 THE QUEUES FOR
 A LONG TIME.  THE MESSAGE WILL KEEP TRYING FOR SOMETIME BUT 
 WILL STAY IN
 THERE FOR EVER.  ALSO OTHER MESSAGES ARE GOING OUT AND WE 
 ALSO RECEIVE ALOT
 OF MESSAGES WITH NO PROBLEM.  I ALSO NOTICED THAT THERE IS 
 ONE COMPANY THAT
 ALWAYS GET STUCK IN THE QUEUE.  I DONT HAVE MESSAGE TRACKING 
 ON BECAUSE I
 DONT KNOW HOW TO SET THAT UP.  ALSO IF ITS THE OTHER COMPANYS 
 SERVER PLEASE
 LET ME KNOW WHY IT WOULD BE THEIR SERVER.  THANK YOU FOR YOUR TIME.
 
 RICHARD TENER
 [EMAIL PROTECTED]
 
 _
 List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
 Archives:   http://www.swynk.com/sitesearch/search.asp
 To unsubscribe: mailto:[EMAIL PROTECTED]
 Exchange List admin:[EMAIL PROTECTED]
 
 _
 List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
 Archives:   http://www.swynk.com/sitesearch/search.asp
 To unsubscribe: mailto:[EMAIL PROTECTED]
 Exchange List admin:[EMAIL PROTECTED]
 

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: ims queues

2001-09-17 Thread Andy David

WE MAKE CONTACT


-Original Message-
From: Richard Tener [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 17, 2001 3:49 PM
To: Exchange Discussions
Subject: ims queues


Hello,


I HAVE EXCHANGE SERVER 5.5 SP4 RUNNING ON WINDOWS NT 4.0 SP6. EVERYDAY I
CHECK THE IMS QUEUES AND IT SHOWS SOME MESSAGES ARE STUCK IN THE QUEUES
FOR A LONG TIME.  THE MESSAGE WILL KEEP TRYING FOR SOMETIME BUT WILL STAY
IN THERE FOR EVER.  ALSO OTHER MESSAGES ARE GOING OUT AND WE ALSO RECEIVE
ALOT OF MESSAGES WITH NO PROBLEM.  I ALSO NOTICED THAT THERE IS ONE
COMPANY THAT ALWAYS GET STUCK IN THE QUEUE.  I DONT HAVE MESSAGE TRACKING
ON BECAUSE I DONT KNOW HOW TO SET THAT UP.  ALSO IF ITS THE OTHER COMPANYS
SERVER PLEASE LET ME KNOW WHY IT WOULD BE THEIR SERVER.  THANK YOU FOR
YOUR TIME.

RICHARD TENER
[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]