• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 621
  • Last Modified:

Exchange not sending messages from SMTP Connector

This is a follow-on from a previous post from which jjmck helped and appeared to solve.

The problem was with my SMTP banner not matching a reverse DNS.  That problem appears fixed, BUT the messages that are in the server queue continue to "retry" without sending.  Am I being impatient since it has only been about 1.5 hours?  Even new msgs sent to the "retrying" domains are sitting in queue.

Thanks again for your help.

0
Orionreno
Asked:
Orionreno
  • 11
  • 7
  • 3
1 Solution
 
francrlCommented:
On the exchange server do an ipconfig /flushdns, to be sure that the null records are removed. Then retry.
You can aslo use nslookup to verify you are getting the correct MX records for the destination of the email.
0
 
Alan HardistyCo-OwnerCommented:
Please have a read of my article about problems sending mail to one or more domains:

http://www.experts-exchange.com/articles/Software/Server_Software/Email_Servers/Problems-sending-mail-to-one-or-more-external-domains.html

Check your settings and shout if you are stuck or not sure about anything.
0
 
OrionrenoAuthor Commented:
francrl,

Thanks, I did the flush, but still the emails are not sending.  Could you elaborate on the nslookup?  

0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
francrlCommented:
Open a command prompt on the mail server:

C:\> nslookup   (enter)
set type=mx
google.com

(where google.com is the domain the emails are "stuck" for)

it should return something like this:
 google.com      MX preference = 200, mail exchanger = google.com.s9a2.psmtp.com

if not the DNS server is not finding the mail exhanger record for the domain. As a temporary bandaid you can manually add it to the hosts file on the exchange server
edit the file c:\windows\system32\drivers\etc\hosts
add a new line with the ip of the mx record then the domain name

# Copyright (c) 1993-2006 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

127.0.0.1       localhost
216.239.32.10      google.com

save the file then do another ipconfig /flushdns
0
 
francrlCommented:
I should add a note on how to find out what the mx record ip is to add to the hosts file (here I use verizon.net):

C:\>nslookup
> server 8.8.8.8
Default Server:  google-public-dns-a.google.com
Address:  8.8.8.8

> set type=mx
> verizon.net
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
verizon.net     MX preference = 0, mail exchanger = relay.verizon.net
> set type=a
> relay.verizon.net
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
Name:    relay.verizon.net
Address:  206.46.232.11
0
 
Alan HardistyCo-OwnerCommented:
Any feedback to my comment?
0
 
OrionrenoAuthor Commented:
alanhardisty
I've been working on both your post as well as francrl's post.

I'm just not getting anything at all to work!

I went through your blog and the only issue I had is the SPF record.  Just for understanding purposes, why would I ALL OF THE SUDDEN need a SPF record.  I've dealt with a handful of exchange servers in the past, I I've never had to go as far as I have here.  And honestly, I've never heard of the SPF record.

I did add an SPF to the DNS of the server hosting the main domain name (temperatsure.com) obviously I have A record pointing to mail.temperatsure.com and now a txt SPF.

I cant imagine that on 4/8/10 ten domains just arbitrarily blocked our emails at the same time.  Especially since we've been communicating daily with all of them.  they are basically venders and customers of Temperatsure.com

Thanks for checking in.
0
 
Alan HardistyCo-OwnerCommented:
Do you want to drop me an email with your domain name (if different from above) and server IP Address so that I can do some testing for you?
If so - you can reach me via my profile - just click on my name.
0
 
Alan HardistyCo-OwnerCommented:
With the domain you provided above - you do look squeaky clean!
SPF may be helpful, but not essential.  Having no SPF should not cause you problems, but it can, having the wrong SPF can be disasterous, having the right SPF record can only help.
Essentially SPF allows people receiving mail to check that you are authorised (your IP address) to send mail on behalf of your domain, so setting one up should help with sending out mail and can also help with reducing spam on your own servers.
0
 
OrionrenoAuthor Commented:
alanhardisty,
Right now I have 11 domains "retrying" and even when I right click and "force" they don't go.  I emailed you, I may need some direct help on this one.
0
 
Alan HardistyCo-OwnerCommented:
Thanks - I saw your email get greylisted by my server!  It should make it second time around.  If not - try me at alan @ it-eye.co.uk.
FYI - we are not allowed to work directly with you / work remotely via Experts-Exchange as it breaches the member agreement.  All work has to be carried out over the web-site.
Will see what I can do with the email (when it arrives) and report back asap.
Alan
0
 
Alan HardistyCo-OwnerCommented:
Okay - the IP address that you just emailed me from is Blacklisted on Backscatter.org, which means that you are replying to messages destined for invalid recipients with a Non-Delivery Report.
That's fine in itself, but when spammers send you mail from addresses that are spoofed, you will end up hitting innocent people and Honeypots (traps designed to catch spammers) and as such, you are listed automatically when a trap is sprung.
You need to either enable Recipient Filtering on your server to reject invalid recipients and force the onus of sending an NDR report back to the sending server or disable NDR messages.
To enable Recipient Filtering, please have a read of the following:
http://www.msexchange.org/tutorials/Sender-Recipient-Filtering.html
Also worth a read of my article:
http://www.experts-exchange.com/articles/Software/Server_Software/Email_Servers/Exchange/How-to-prevent-Spoofed-Emails-in-Exchange-2003.html 
Once enabled, you can request de-listing from Backscatter.org.
This is assuming you are Exchange 2003 as so far, there is no mention of the version you are running.  If not, please read this instead:
http://technet.microsoft.com/en-us/library/aa998898(EXCHG.80).aspx 
0
 
OrionrenoAuthor Commented:
The email address I emailed you from was not of the domain in question.  That was my personal email and my rediculous ISP, Charter.net.  my current location is on a dynamic IP address so I can understand getting hit with a backscatterer.org BL.
Next i'm going to email you with the administrator acct so you can get a better picture.  

The Server is MS 2003 all updated and exchange 2003 all updated.

Plus I increased the point value since this has gotten more difficult as we've gone along.

0
 
Alan HardistyCo-OwnerCommented:
Dynamic IP's are probably going to be the biggest problem you are going to face as they are often blacklisted somewhere or other, and most often because they are dynamic and spammers like dynamic IP Addresses!
 
0
 
OrionrenoAuthor Commented:
Please keep in mind that the exchange server is on a Static, I'm on the dynamic and remoting into the Exchange server.  
0
 
Alan HardistyCo-OwnerCommented:
Ah - that makes me feel a whole lot happier!  Sorry for the mistake.
Will await your next email (nothing seen yet).
0
 
OrionrenoAuthor Commented:
On your email you mentioned a backscatterer.org at 206.123.72.210.  That IP is the IP of my site domain host (temperatsure.com)  Which coincidentally is the same for MY email, orionreno.com.  
I sent you an email from administrator @ temperatsure.com through OWA, did you get it?
0
 
Alan HardistyCo-OwnerCommented:
Okay - Having checked and double-checked – your domain is as clean as a whistle, so I can’t see the problem being at your end and I would contact the problems domains directly as I expect they are specifically blocking you!
0
 
Alan HardistyCo-OwnerCommented:
Got your Administrator message - all looks good as per above.
0
 
Alan HardistyCo-OwnerCommented:
Can you try telnetting from the server to the problem domains and see what responses you get please.
telnet mail.problemdomain.com 25
ehlo yourdomain.com
mail from:<youruser@yourdomain.com>
rcpt to:<theiruser@theirdomain.com>
(Hopefully you will get a go away message here)
quit
Replace the relevant bits above to reflect your domain, and relevant email addresses.
Any negative responses received?
0
 
OrionrenoAuthor Commented:
The solution was exchange 2007 after a 12 hour marathon call with Microsoft.  It appeared that Exchange 03/Server 03 had some level of corruption that was not able to be fixed.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

  • 11
  • 7
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now