not receiving external email

I removed 2 IP addresses from one of my recieve connectors, and ever since then, I can't receive external email.  I added the IP addresses back and even restarted the server, but still am not able to receive external email, only internal email works.  Please help.  Here's the error message I get when I send one from my gmail account.


Delivery to the following recipient failed permanently:

     xxxxx@domain.org

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 Address unknown (state 14).

----- Original message -----

Received: by 10.227.61.6 with SMTP id r6mr9672041wbh.37.1317235636412; Wed, 28
 Sep 2011 11:47:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.227.10.83 with HTTP; Wed, 28 Sep 2011 11:46:36 -0700 (PDT)
From: xxx _ <xxxxxxxx@gmail.com>
Date: Wed, 28 Sep 2011 11:46:36 -0700
Message-ID: <CAMzYC+vT7BMP79_+eBgwXPXONMb3eV_73N60-uHS+q3ULhp-jQ@mail.gmail.com>
Subject: test15
To: xxxxx@domain.org
Content-Type: multipart/alternative; boundary=20cf30025a6031a2c004ae04d2dd
DanNetwork EngineerAsked:
Who is Participating?
 
PradeepConnect With a Mentor Commented:
Yes you will get event id 12014, 16, 18 for certificate related errors.

You can create a self signed as well as third party.
i will recommend to get a third party from GO-DADDY which was cheap and best than other CA..
0
 
DanNetwork EngineerAuthor Commented:
In looking at the even log, I see this:

Anti-spam agents are enabled, but the list of internal SMTP servers is empty. If there are any MTAs between this server and the Internet, populate this list by using the Set-TransportConfig cmdlet in the Exchange Management Shell.

Then  for months, I see this message, but I've been getting this for months, so I don't think this is it:
There is no valid SMTP Transport Layer Security (TLS) certificate for the FQDN of elisha.amazingfacts.org. The existing certificate for that FQDN has expired. The continued use of that FQDN will cause mail flow problems. A new certificate that contains the FQDN of elisha.amazingfacts.org should be installed on this server as soon as possible. You can create a new certificate by using the New-ExchangeCertificate task.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0
 
PradeepCommented:
How can you expect mails if you are not having a valid certificate with a valid FQDN
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
DanNetwork EngineerAuthor Commented:
well, its been working for months, actually, it's been like that ever since we went live with it.
0
 
DanNetwork EngineerAuthor Commented:
so how do I create a new certificate, would you mind walking me through it?
0
 
DanNetwork EngineerAuthor Commented:
the question is, I've installed certs on servers, but how do I install it on my exchange server for exchange, I've only installed certs for IIS.
How do I make the request, and then installing it, can you point me in the right direction.
0
 
PradeepCommented:
How mailflow is going on.
Is it comming from a third party spam filter..?
0
 
DanNetwork EngineerAuthor Commented:
well, emails are coming from the outside, router, firewall, switch and then my exchange server.
0
 
DanNetwork EngineerAuthor Commented:
the emails are coming in, I'll just open a new question for the cert when I have time.
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.

All Courses

From novice to tech pro — start learning today.