[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 856
  • Last Modified:

Inbound SMTP delayed

Hello Experts,
We have been seeing a delay on inbound emails. This does this randomely and from different domains. We are using Exchange 2003 SP1. When someone from an outside comapny emails us they have been seeeing this message
"Delivery to the following recipients has been delayed" sometimes we get the email a day or so later and other times we do not get the email at all,
any thoughts would be appreciated.
0
talltree
Asked:
talltree
  • 23
  • 22
1 Solution
 
ATIGCommented:
how is your environment configured --

smtp gateway ? running av?
reverse dns lookups? black lists

I have seen queues build up at time when we had black lists enabled on our smtp gatways. how is name resolution? check your dsaccess?
0
 
talltreeAuthor Commented:
Hello DNS resolved by domain controller forwarding to Ip, We have SMTP default virtual server no smarthost and no reverse dns checked, av macafee groupwise, no blacklist configured. dsacess dc's and gc's
This morning there was a delay using a hotmail acoount this afternoon no delay instant delivery
0
 
talltreeAuthor Commented:
Correction AV Netshield groupshield 6.0.
0
NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

 
ATIGCommented:
With the inbound delays, are they recieved on your server and delay being delivered to the client or is there a delay before your system recieves the message?
0
 
talltreeAuthor Commented:
Is there a place i can check on the exchange server to see if the email tries to arrive? The delay message arrives at the client or sender's email after a few hours no reports of this happening today and i have not made any changes..

This is an automatically generated Delivery Status Notification.

THIS IS A WARNING MESSAGE ONLY.

YOU DO NOT NEED TO RESEND YOUR MESSAGE.

Delivery to the following recipients has been delayed.
0
 
ATIGCommented:
to test this send your self a message from hotmail or somthing then use message tracking to find out if it has entered the system. See how long it take before you can see the message in the tracking log, you could also use a sniffer for smtp traffic to look at the incoming traffic. Most of the queue monitoring in Exchange is for outgoing.......
0
 
talltreeAuthor Commented:
Thanks I tried that suceesfully. Is it  possible that the exchange server is too busy to process inbound email and if so what could be the cause of that? SMTP settings? The server is a dual processor gig network card
0
 
ATIGCommented:
Try turning up your logging in ESM to see if you get any information there.......Once a message enters your system Exchange does a lookup to the GC to find out info on the user then delivers the message.

have you looked at your dns settings to verify your Exchange server is pointed to a good dns server? have you checked the server records for your DC/GC's

have you stopped and started the smtp service?

Are you in a front end backend senario? and events in the logs?
0
 
talltreeAuthor Commented:
I see this message
421 SMTP service not available, closing transmission channel
0
 
ATIGCommented:
what do you have between the Exchange and internet----
have you tried turning off your AV and seeing what happens?
0
 
talltreeAuthor Commented:
Watchguard firewall we have made a change to allow the firewall to pass the smtp traffic directly to the exchange box and filter the icoming IP's at the exchange level, so far it has been working.
0
 
talltreeAuthor Commented:
Also On exchange 2003  in Queues how many retrys would you consider alot? And does the exchange server discard them after a determined amount of retrys? Thanks
0
 
ATIGCommented:
That is your outbound queues that you are viewing, that is nothing that I ever put a stamp on because typically that is connectivity to an exteranl source. you can view the default setting in ESM under your server name, protocols, smtp , delivery -- I just let them die if they dont make it out.... If you think there are connectivity problems to those location

nslookup <enter>
set type=mx
problem domain

this will give you thier mx
telnet to thier server via 25

telnet XXXX 25 and see if it connects if not then verify you can connect to other to make sure the issue is not outbound on your end. The only thing Exchange needs to route messages is DNS
0
 
talltreeAuthor Commented:
If i get a DNS timeout response would that mean it is a nonexistant domain?
Also what would be the suggested DNS setup on the exchange 2003.
we have the DNS setting in the network card on the exchange server pointing to the Domain controller The domain controller forwards to our ISP, no smarthost
0
 
ATIGCommented:
Your configuration is fine and is vary common -- most implementation that I setup have internal DNS server that forward off to controlled dns.

when are you getting the time out? performing the lookup? If so does this only happen to selected domains? You could have a potential dns problem
0
 
talltreeAuthor Commented:
I tryed the nslookyp on the Dns names in the queue and i receive DNS request timed out
0
 
talltreeAuthor Commented:
actually i did one that has a retry and did get a Non authorative answer with an MX record
0
 
ATIGCommented:
that would mean you are having trouble resolving that name --- do you have another box outside of your network that uses another dns server that you can try the same procedure with to verify that its not on your end
0
 
ATIGCommented:
non authorative answer are fine -- that just mean you got a response from a server that does not own that domain name.

What the response recieved on your network or when you used an outside box?
0
 
talltreeAuthor Commented:
from outside box the one that timed out i get a can't find server failed. On the inside on another record i get DNS request timed out but the outside resolved it no mx record. Would that mean it may not have email sent to it but it is a .com site?
0
 
ATIGCommented:
you lost me with your wording above ------

lets split it up --

Was the nslookup on the MX success from out side the newtork?

Was the nslookup on the same MX successful from inside the network?
0
 
talltreeAuthor Commented:
Was the nslookup on the MX success from out side the newtork?
from xxx.com
 primary name server = xxx.com
        responsible mail addr = xxxx.net
        serial  = 9
        refresh = 10800 (3 hours)
        retry   = 1800 (30 mins)
        expire  = 604800 (7 days)
        default TTL = 600 (10 mins)
Was the nslookup on the MX success from out side the newtork?
xxx.com
        primary name server = xxx.com
        responsible mail addr = xxxx.net
        serial  = 9
        refresh = 10800 (3 hours)
        retry   = 1800 (30 mins)
        expire  = 604800 (7 days)
        default TTL = 600 (10 mins)
same result
But in the queue it is sitting there with a retry.
0
 
talltreeAuthor Commented:
I also have another
Was the nslookup on the MX success from out side the newtork?
successful Non-authortative answer with mx record.

Was the nslookup on the same MX successful from inside the network?
successful Non-authortative answer with mx record.
 But it is now on its 3rd retry in the queue
0
 
ATIGCommented:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\brian>nslookup

> set type=mx
> jdp.us.army.mil
Server:  UnKnown
Address:  192.168.0.1

jdp.us.army.mil MX preference = 10, mail exchanger = smtp.jdp.us.army.mil
jdp.us.army.mil nameserver = ns01.army.mil
jdp.us.army.mil nameserver = ns03.army.mil
jdp.us.army.mil nameserver = ns02.army.mil
ns01.army.mil   internet address = 140.153.43.44
ns03.army.mil   internet address = 130.114.200.6
ns02.army.mil   internet address = 192.82.113.7

you should be recieving somting like this--- if you do not see a listing similar there is no mx record for that domain out there. From the data you shown me I would say those domains do not have an MX record associated with them !

what address are you trying to get too.......

0
 
talltreeAuthor Commented:
wbix.com
mailaccount.com shows an mx record but the queue is still in a retry state.
0
 
ATIGCommented:
No there is not MX!!!! Look at the response that i posted and look at yours.

I just did a lookup on it Show me where it says MX= SERVERX in your response?
0
 
talltreeAuthor Commented:
Non-authoritative answer:
Mailaccount.com MX preference = 10, mail exchanger = Mailaccount.com

Mailaccount.com internet address = 66.226.64.24
0
 
ATIGCommented:
I only did the wbix.com == who is that?
0
 
ATIGCommented:
if the problem persists with that domain -- contact them and see if they are having problems....... I have hundreds of thousands of messages that passes through my systems everyday. I wont even think about a queue unless I have 20-30 backing and even then I will verify connectiviey at first and then assume its on thier end....... if it continues I will look further into it
0
 
talltreeAuthor Commented:
Ok
i have not seen that many backed up usually 8-10 retrys
0
 
ATIGCommented:
I only did the wbix.com == who is that?

is that an external domain?
0
 
talltreeAuthor Commented:
This is what i see from nslookup
wbix.com
        primary name server = Lexicon.CTCNet.com
        responsible mail addr = hostmaster.ctccom.net
       
0
 
ATIGCommented:
and that zone does not have an MX on it ---- you see the difference in the responses between the 2
0
 
ATIGCommented:
If you are worried about the queue setup Exchange alerts -- I have mine set to warn me after 30 minutes of continous backup and error after 45
0
 
talltreeAuthor Commented:
So the wbix.com needs a MX record what does the responsible mail addr do?
responsible mail addr = hostmaster.ctccom.net
0
 
ATIGCommented:
means who owns it-- but dont worry about them if its not your site just let the mail die....
0
 
talltreeAuthor Commented:
Ok
0
 
ATIGCommented:
you making me work for these points :)
0
 
talltreeAuthor Commented:
I appreciate it and i have learned alot .
i  have wanted to get to the bottom of the queue retrys  
0
 
talltreeAuthor Commented:
I just received a call from a user who works for our comaony and could not receive an email from another well known comapny it  bounced back.
 i am waiting for him to tell me the error code.
0
 
ATIGCommented:
You definately gonna make me work for this huh..... I think I need a pay check soon :P

Go into your message tracking and see if the message has entered you system -- that will tell you if exchange ever recieved the message.

Try downloading Spotlight on Exchange fro Quest there is a trial verison that give you 30 days -- I think you will like it
0
 
talltreeAuthor Commented:
It was not in the message tracker
0
 
ATIGCommented:
Then it never entered your Exchange org and your sever never recieved the message. If all other inbound mail is working fine then its not on your end.

Pick up the pocket Admin guide for Exchange 2003 I thought it was a really good book
0
 
ATIGCommented:
Did I help you enough to close this one out so I can get some points :)
0
 
talltreeAuthor Commented:
Thanks for all the help
0

Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

  • 23
  • 22
Tackle projects and never again get stuck behind a technical roadblock.
Join Now