Solved

Email Coming Into Exchange 2003 Disappearing And Not Being Delivered To User Inboxes

Posted on 2009-05-06
8
435 Views
Last Modified: 2012-05-06
I have a strange problem.    Have to Exchg 2003 servers (with MX records at ISP), to which email can be delivered.  2nd one just added recently.  It will eventually be made into a Front-End Server.....now both are backend servers....  email comes into the system....our spam filter logs show it coming in and PROCESSED NORMALLY.  This means it was not blocked for delivery in anyway to the user inboxes.  (Running GFI Mail Essentials For Exchange).  Anyway, the email does not get to the user inbox.  Some email gets thru, some does not....almost looks like email that came in on the 2nd server is not being delivered.  Have a mail archive set up, where a copy of all inbound and outbound email is forwarded to JOURNAL@<domain.name>.  This mail archive has no record of the email either.  So the emails are disappearing after passing successfully thru the spam filters. (BTW, have forwarded all spam to my inbox, just in case, but nothing).  The all email queues are empty on the exchg servers.  Need help.  Please advise.  Thanks.
0
Comment
Question by:rstuemke
  • 5
  • 3
8 Comments
 

Author Comment

by:rstuemke
ID: 24314948
Check the BADMAIL folder for the servers and nothing....

Also, forgot to mention, have Exchange 2007 server that is being tested and prepared, but no mailboxes.

Also, all Exchange Servers are in their own administrative group.  Routing Connectors have been created between the groups.
0
 

Author Comment

by:rstuemke
ID: 24317077
Ran SMTDIAG to send mail internally to a couple of different addresses.....Some of the internal tests fail....it is trying to connect to each DNS server.....not all DNS servers are exchange servers....wondering if the same thing is happening when external mail is brought into the system, trying to send it to an incorrect server.....

Here is the long text from an SMTPDIAG....shows socket 10061 errors....
172.16.1.168 and 172.16.1.24 are domain controllers/DNS servers only
172.16.1.43 - ISP MX server #1
172.16.1.222 - ISP MX server #2
172.16.1.233 - sender to internet only
172.16.1.167 - ex2007 server

Searching for Exchange external DNS settings.
Computer name is 1730W4420336.
VSI 1 has the following external DNS servers:
206.166.83.22,208.67.222.222,206.166.61.21,64.102.255.44,156.154.71.1,208.67.220.220


Checking SOA for calvaryspringfield.org.
Checking external DNS servers.

Checking TCP/UDP SOA serial number using DNS server [206.166.83.22].
TCP test succeeded.
UDP test succeeded.
Serial number: 2009043001

Checking TCP/UDP SOA serial number using DNS server [208.67.222.222].
TCP test succeeded.
UDP test succeeded.
Serial number: 2009043001

Checking TCP/UDP SOA serial number using DNS server [206.166.61.21].
TCP test succeeded.
UDP test succeeded.
Serial number: 2009043001

Checking TCP/UDP SOA serial number using DNS server [64.102.255.44].
TCP test succeeded.
UDP test succeeded.
Serial number: 2009043001

Checking TCP/UDP SOA serial number using DNS server [156.154.71.1].
TCP test succeeded.
UDP test succeeded.
Serial number: 2009043001

Checking TCP/UDP SOA serial number using DNS server [208.67.220.220].
TCP test succeeded.
UDP test succeeded.
Serial number: 2009043001
Checking internal DNS servers.

Checking TCP/UDP SOA serial number using DNS server [172.16.1.43].
TCP test succeeded.
UDP test succeeded.
Serial number: 47208

Checking TCP/UDP SOA serial number using DNS server [172.16.1.217].
TCP test succeeded.
UDP test succeeded.
Serial number: 47206
Serial numbers do not match: 2009043001  47206
SOA serial number match: Failed with one or more failures.

Checking local domain records.
Starting TCP and UDP DNS queries for the local domain. This test will try to
validate that DNS is set up correctly for inbound mail. This test can fail for
3 reasons.
    1) Local domain is not set up in DNS. Inbound mail cannot be routed to
local mailboxes.
    2) Firewall blocks TCP/UDP DNS queries. This will not affect inbound mail,
but will affect outbound mail.
    3) Internal DNS is unaware of external DNS settings. This is a valid
configuration for certain topologies.
Checking MX records using TCP: calvaryspringfield.org.
  A:     calvaryspringfield.org [172.16.1.222]
  A:     calvaryspringfield.org [172.16.1.233]
  A:     calvaryspringfield.org [172.16.1.217]
  A:     calvaryspringfield.org [172.16.1.43]
  A:     calvaryspringfield.org [172.16.1.168]
  A:     calvaryspringfield.org [172.16.1.24]
Checking MX records using UDP: calvaryspringfield.org.
  A:     calvaryspringfield.org [172.16.1.222]
  A:     calvaryspringfield.org [172.16.1.217]
  A:     calvaryspringfield.org [172.16.1.43]
  A:     calvaryspringfield.org [172.16.1.168]
  A:     calvaryspringfield.org [172.16.1.24]
  A:     calvaryspringfield.org [172.16.1.233]
Both TCP and UDP queries succeeded. Local DNS test passed.

Checking remote domain records.
Starting TCP and UDP DNS queries for the remote domain. This test will try to
validate that DNS is set up correctly for outbound mail. This test can fail for
3 reasons.
    1) Firewall blocks TCP/UDP queries which will block outbound mail. Windows
2000/NT Server requires TCP DNS queries. Windows Server 2003 will use UDP
queries first, then fall back to TCP queries.
    2) Internal DNS does not know how to query external domains. You must
either use an external DNS server or configure DNS server to query external
domains.
    3) Remote domain does not exist. Failure is expected.
Checking MX records using TCP: calvaryspringfield.org.
  A:     calvaryspringfield.org [172.16.1.168]
  A:     calvaryspringfield.org [172.16.1.43]
  A:     calvaryspringfield.org [172.16.1.217]
  A:     calvaryspringfield.org [172.16.1.24]
  A:     calvaryspringfield.org [172.16.1.233]
  A:     calvaryspringfield.org [172.16.1.222]
Checking MX records using UDP: calvaryspringfield.org.
Both TCP and UDP queries succeeded. Remote DNS test passed.

Checking MX servers listed for dstuemke@calvaryspringfield.org.
Connecting to calvaryspringfield.org [172.16.1.222] on port 25.
Received:
220 1730Wexchgiis.calvaryspringfield.org Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at  Wed, 6 May 2009 11:51:50 -0500


Sent:
ehlo calvaryspringfield.org

Received:
250-1730Wexchgiis.calvaryspringfield.org Hello [172.16.1.43]
250-TURN
250-SIZE
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250-TLS
250-STARTTLS
250-X-EXPS GSSAPI NTLM LOGIN
250-X-EXPS=LOGIN
250-AUTH GSSAPI NTLM LOGIN
250-AUTH=LOGIN
250-X-LINK2STATE
250-XEXCH50
250 OK


Sent:
mail from: <rstuemke@calvaryspringfield.org>

Received:
250 2.1.0 rstuemke@mail.calvaryspringfield.org....Sender OK

Sent:
rcpt to: <dstuemke@calvaryspringfield.org>

Received:
250 2.1.5 dstuemke@calvaryspringfield.org

Sent:
quit

Received:
221 2.0.0 1730Wexchgiis.calvaryspringfield.org Service closing transmission channel


Successfully connected to calvaryspringfield.org.
Connecting to calvaryspringfield.org [172.16.1.233] on port 25.
Received:
220 1730Wctccbdc.calvaryspringfield.org Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at  Wed, 6 May 2009 11:51:50 -0500


Sent:
ehlo calvaryspringfield.org

Received:
250-1730Wctccbdc.calvaryspringfield.org Hello [172.16.1.43]
250-TURN
250-SIZE
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250-X-EXPS GSSAPI NTLM
250-AUTH GSSAPI NTLM
250-X-LINK2STATE
250-XEXCH50
250 OK


Sent:
mail from: <rstuemke@calvaryspringfield.org>

Received:
250 2.1.0 rstuemke@calvaryspringfield.org....Sender OK

Sent:
rcpt to: <dstuemke@calvaryspringfield.org>

Received:
250 2.1.5 dstuemke@calvaryspringfield.org

Sent:
quit

Received:
221 2.0.0 1730Wctccbdc.calvaryspringfield.org Service closing transmission channel


Successfully connected to calvaryspringfield.org.
Connecting to calvaryspringfield.org [172.16.1.24] on port 25.
Received:
220 1730wchurch.calvaryspringfield.org Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at  Wed, 6 May 2009 11:51:50 -0500


Sent:
ehlo calvaryspringfield.org

Received:
250-1730wchurch.calvaryspringfield.org Hello [172.16.1.43]
250-TURN
250-SIZE 2097152
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250 OK


Sent:
mail from: <rstuemke@calvaryspringfield.org>

Received:
250 2.1.0 rstuemke@calvaryspringfield.org....Sender OK

Sent:
rcpt to: <dstuemke@calvaryspringfield.org>

Received:
550 5.7.1 Unable to relay for dstuemke@calvaryspringfield.org

Error: Expected "250". Server rejected the recipient address.
Failed to submit mail to calvaryspringfield.org.
Connecting to calvaryspringfield.org [172.16.1.217] on port 25.
Connecting to the server failed. Error: 10061
Failed to submit mail to calvaryspringfield.org.
Connecting to calvaryspringfield.org [172.16.1.43] on port 25.
Received:
220 1730w4420336.calvaryspringfield.org Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at  Wed, 6 May 2009 11:51:52 -0500


Sent:
ehlo calvaryspringfield.org

Received:
250-1730w4420336.calvaryspringfield.org Hello [172.16.1.43]
250-TURN
250-SIZE
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250-TLS
250-STARTTLS
250-X-EXPS GSSAPI NTLM
250-AUTH GSSAPI NTLM
250-X-LINK2STATE
250-XEXCH50
250 OK


Sent:
mail from: <rstuemke@calvaryspringfield.org>

Received:
250 2.1.0 rstuemke@ctccmail.calvaryspringfield.org....Sender OK

Sent:
rcpt to: <dstuemke@calvaryspringfield.org>

Received:
250 2.1.5 dstuemke@calvaryspringfield.org

Sent:
quit

Received:
221 2.0.0 1730w4420336.calvaryspringfield.org Service closing transmission channel


Successfully connected to calvaryspringfield.org.
Connecting to calvaryspringfield.org [172.16.1.168] on port 25.
Connecting to the server failed. Error: 10061
Failed to submit mail to calvaryspringfield.org.
0
 
LVL 65

Accepted Solution

by:
Mestha earned 500 total points
ID: 24320261
What does message tracking show? That will tell you if Exchange has dropped the message.

Simon.
0
 

Author Comment

by:rstuemke
ID: 24327068
Ok... message tracking enabled on all servers yesterday when problem first suspected.
Spam filter log shows message today coming in from user's personal email address and being "processed normally".  User called me an said did not receive mail that was sent early this morning.......so when to message tracking and check the two MX servers that accept email from internet.  One is a ExFrontEnd.  Neither server showed any tracking info for the messages (there were a couple processed normally).  Its like they went into a black hole before being delivered to the user.
Can you help???
0
Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

 
LVL 65

Expert Comment

by:Mestha
ID: 24327536
If the messages do not appear in message tracking then Exchange didn't receive the message. That means they were dropped either at the point of delivery, or beforehand. The complete message was not received.

Simon.
0
 

Author Comment

by:rstuemke
ID: 24327689
Ok, now the questions are:

how do I find out who dropped it?
how do I find out why it was dropped?

0
 
LVL 65

Expert Comment

by:Mestha
ID: 24328271
You either have to gut the machines of any third party tools, which are the usual cause of problems or the spam product has to bypassed. Exchange doesn't log a great deal, but the Exchange SMTP system is very reliable - almost all problems I see are caused by third parties - AV, Antispam etc.

Simon.
0
 

Author Closing Comment

by:rstuemke
ID: 31578466
Message tracking showed that email was being deleted by the intelligent mail filter.  Changing the parameters for the filter allowed recipients to receive mail.  Thanks.
0

Featured Post

Highfive Gives IT Their Time Back

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Resolve DNS query failed errors for Exchange
Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…
This video discusses moving either the default database or any database to a new volume.

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now