Link to home
Start Free TrialLog in
Avatar of Houston Blancett
Houston BlancettFlag for United States of America

asked on

Exchange 2010 bundled with Windows SBS 2011 cannot send external emails

I have Exchange running inside windows SBS 2011 that approximately 48 hrs ago stopped sending external email. Users can receive external emails but cannot reply. Users can send and receive internal emails within the office while on the domain.  We are currently closed but I have to try to resolve this quick before tomorrow.
Avatar of Cliff Galiher
Cliff Galiher
Flag of United States of America image

If you have not made any recent changes, my first supicion is the ISP has started blocking port 25 as an antispam measure. This is easy to test via telnet.
Avatar of Houston Blancett

ASKER

I was able telnet out to another mail server and also Google via 25.
When you try to send email, does it bounce? If so, what is the NDR?
If not, look in the queue viewer to see if there is an error.

Something like that doesn't happen on its own, either you have changed something or your ISP has.

Do ensure that there is plenty of disk space on the server as well.

Simon.
No bounce that I've seen. It goes out,  and when looking in the sent folder, it shows the mail was sent.
I am actually receiving the email notification of your comments via my email address on the server with issues. I can receive but my replies show sent but they actually are not.
You need to look on the server. Looking in Outlook is a waste of time as they will show they have gone there because Outlook has sent them to the server.

The client is no use here, it is the server you have to look at.

Simon.
Yes I know that. I am at the server. I just wanted to confirm
SOLUTION
Avatar of Zacharia Kurian
Zacharia Kurian
Flag of Kuwait image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Open the Exchange Management Console> Toolbox>
Check the queues and the message tracking logs to see whats happening to the emails.

Check the Exchange Services to make sure that the automatic ones are started - Specifically the Transport Service.

Are you using a smart host or direct emails?
I have gone into the message queue in toolbox however I cannot view any messages because I'm getting a constant error saying that  exchange can't connect to  the transport service is not running. I have restarted all exchange services and verified that the transport is running.
Check the event logs for Transport events.  See if it is crashing.
How much disk space does the server have on its C drive?
What is the total size of the disk space on the C drive?

The most common reason for this kind of failure is the lack of disk space.

Simon.
"c" drive is 250GB  with 44.5GB free.  No errors showing up in event viewer regarding transport.
Do you have Symantec Mail security for exchange installed? If so try disabling it any see.  Usually transport service get issues if you have any Anti Spam software installed. Have you checked the event logs in your server? are there any logs that relates to exchange services? If you have any,  post them please. Also check if your domains are running with out any issues. Moreover check if you applied any group policies to your exchange server. I found something similar in the forum;

https://www.experts-exchange.com/questions/28624665/SBS2011-suddenly-can't-receive-external-emails-internal-ok-and-can-send-ok.html

And check the smart host relays too.
There is no Symantec Mail Security installed. Since my last post, I have performed the following in hopes of resolving this,,

1. Reran "Connect to internet" to remove trusted cert and correct email settings within EMC.
Still no external emails. I am getting several Outlook delay notice which I've attached below.



Delivery is delayed to these recipients or groups:

Rex Blancett (rexblancett@mac.com)

Subject: Re: Test in

This message hasn't been delivered yet. Delivery will continue to be attempted.

The server will keep trying to deliver this message for the next 1 days, 19 hours and 56 minutes. You'll be notified if the message can't be delivered by that time.
 






Received: from BCSERVER.beachchurch.local ([fe80::45c7:ac3b:3e65:694f]) by BCSERVER.beachchurch.local ([fe80::45c7:ac3b:3e65:694f%10]) with mapi id 14.03.0224.002; Sun, 22 Mar 2015 19:51:21 -0400 From: Rex Blancett To: Rex Blancett Subject: Re: Test in Thread-Topic: Test in Thread-Index: AQHQZPpHXmwT4RIYEky+cYwSh+s7p50pbhgA Date: Sun, 22 Mar 2015 23:51:19 +0000 Message-ID: References: <1212AAEF-E794-47F2-B5AA-6D69FF8C04FF@mac.com> In-Reply-To: <1212AAEF-E794-47F2-B5AA-6D69FF8C04FF@mac.com> Accept-Language: en-US Content-Language: en-US X-MS-Exchange-Organization-AuthAs: Internal X-MS-Exchange-Organization-AuthMechanism: 04 X-MS-Exchange-Organization-AuthSource: BCSERVER.beachchurch.local X-MS-Has-Attach: X-MS-Exchange-Organization-SCL: -1 X-MS-TNEF-Correlator: x-ms-exchange-organization-originalsize: 5450 x-ms-exchange-organization-originalarrivaltime: 22 Mar 2015 23:51:19.3579 (UTC) x-ms-exchange-organization-messagesource: StoreDriver x-ms-exchange-organization-messagedirectionality: Originating x-ms-exchange-forest-messagescope: 00000000-0000-0000-0000-000000000000 x-ms-exchange-organization-messagescope: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-Organization-BCC: x-ms-exchange-organization-messagelatency: SRV=BCSERVER.beachchurch.local:TOTAL=0 x-ms-exchange-organization-hygienepolicy: Standard x-ms-exchange-organization-recipient-limit-verified: True x-ms-exchange-organization-processed-by-journaling: Journal Agent Content-Type: multipart/alternative; boundary="_000_E16A08309A1241F2A5EC3C65B5AF23D2beachchurchorg_" MIME-Version: 1.0 X-MS-Exchange-Organization-ContentConversionOptions: False;00160000;True;;iso-8859-1 X-MS-Exchange-Organization-MessageLatencyInProgress: LSRV=BCSERVER.beachchurch.local:TOTAL=4|SDS=3|SDSS=2|SDSR=2|CCC=1|CAT=1;2015-03-22T23:51:24.989Z
That unfortunately is just a delay message. It doesn't really mean anything.

As I have said twice already, you need to look in the queue viewer to see what it is showing you. That will show why the messages are being delayed, any error message etc.

Simon.
I can't  view messages in the queue. I get the following error as show in the attached screen shot:
exchange-queue-message.png
Corrected the queue error. Below is the properties of one of the "stuck" messages:

Identity: BCSERVER\3\8
Subject: Re: Testing in
Internet Message ID: <FEFFE900-E47E-4829-B477-0752DD2D4146@beachchurch.org>
From Address: Rex@beachchurch.org
Status: Ready
Size (KB): 2
Message Source Name: FromLocal
Source IP: 255.255.255.255
SCL: -1
Date Received: 3/23/2015 8:54:10 AM
Expiration Time: 3/25/2015 8:54:10 AM
Last Error:
Queue ID: BCSERVER\3
Recipients:  rexblancett@mac.com;2;2;;0;CN=Windows SBS Internet Send BCSERVER,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=beachchurch,DC=local
Houston, have you checked the smart host relays?
The message properties doesn't really help.
When you open the queue viewer you will see the messages listed, either individually or as a single queue with lots of messages, depending on whether you are using direct delivery or a smart host.
On the far right (you may have to expand the viewer columns) will be the error message.

However as pointed out, if you are using a smart host, then you should check it is current.

Simon.
I apologize for the delay in responding… I have been out of state at a funeral all this week.
I ended up resolving this myself. While troubleshooting, I noticed there was no resolution of the PTR record or SPF record. I also noticed a couple of discrepancies with the MX records. I contacted the ISP for the business, and after some research they discovered that the static IP that had been assigned, had been replaced with a dynamic IP changing every 24 hours. They reestablished the static IP and that resolved the mail issue. Thanks to all the experts for your suggestions.
I've requested that this question be closed as follows:

Accepted answer: 0 points for Houston Blancett's comment #a40690343

for the following reason:

Self resolved
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial