james3760
asked on
Exchange 2007 - can't email 1 domain (army.mil)
I'm trying to figure out why I can't email a few folks at various army.mil addresses. some are at usarec.army.mil and some are at us.army.mil, etc. I can email marines, navy, army corps of engineers and even secretary of defense addresses. But for some reason, I can't send anything to the army.
gmail works fine, just from my exchange 2007 server, I have issues. And only with the army.mil server.
I checked mxtoolbox.com and my server isn't listed.
I get a delay after 4 hours, then a failure the next day.
I'm thinking it's a dns issue?
gmail works fine, just from my exchange 2007 server, I have issues. And only with the army.mil server.
I checked mxtoolbox.com and my server isn't listed.
I get a delay after 4 hours, then a failure the next day.
I'm thinking it's a dns issue?
You would need to post the contents of your failure message to know anymore really
It coud be DNS problem. But gmail dont using lots of security technologies. Are you using SPF or another feature? Have you set dns record to your comapny? Do you using static IP?
ASKER
Delivery has failed to these recipients or distribution lists:
William Bledsoe ((removedforprivay)@us.arm y.mil)
Microsoft Exchange has been trying to deliver this message without success and has stopped trying. Please try sending this message again, or provide the following diagnostic text to your system administrator.
_____
Sent by Microsoft Exchange Server 2007
Diagnostic information for administrators:
Generating server: mail.wcsecurity.com
(removedforprivacy)@us.arm y.mil
#550 4.4.7 QUEUE.Expired; message expired ##
Original message headers:
Received: from mail.wcsecurity.com ([10.17.194.54]) by mail.wcsecurity.com
([10.17.194.54]) with mapi; Wed, 21 Sep 2011 14:24:45 -0700
From: "James D. Brown" <james@wcsecurity.com>
To: "removed(removed@us.army.m il)" <removed@us.army.mil>
Date: Wed, 21 Sep 2011 14:24:33 -0700
Subject: Gross Paniagua
Thread-Topic: Gross Paniagua
Thread-Index: Acx4pNteO+pOnTQORta4aGQRrW BM+w==
Message-ID: <FB123A6A5B658A4F8040AD016 B9FD1D5021 DEB1F7825@ mail.wcsec urity.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/related;
boundary="_004_FB123A6A5B6 58A4F8040A D016B9FD1D 5021DEB1F7 825mailwcs ecur_";
type="multipart/alternativ e"
MIME-Version: 1.0
William Bledsoe ((removedforprivay)@us.arm
Microsoft Exchange has been trying to deliver this message without success and has stopped trying. Please try sending this message again, or provide the following diagnostic text to your system administrator.
_____
Sent by Microsoft Exchange Server 2007
Diagnostic information for administrators:
Generating server: mail.wcsecurity.com
(removedforprivacy)@us.arm
#550 4.4.7 QUEUE.Expired; message expired ##
Original message headers:
Received: from mail.wcsecurity.com ([10.17.194.54]) by mail.wcsecurity.com
([10.17.194.54]) with mapi; Wed, 21 Sep 2011 14:24:45 -0700
From: "James D. Brown" <james@wcsecurity.com>
To: "removed(removed@us.army.m
Date: Wed, 21 Sep 2011 14:24:33 -0700
Subject: Gross Paniagua
Thread-Topic: Gross Paniagua
Thread-Index: Acx4pNteO+pOnTQORta4aGQRrW
Message-ID: <FB123A6A5B658A4F8040AD016
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/related;
boundary="_004_FB123A6A5B6
type="multipart/alternativ
MIME-Version: 1.0
As mentioned post the failuremessage here and also send the mail to army from other user in ur domain and see he is also getting the same result or not.
If he didnt get then the issue is with ur mailbox and if he gets the same error the issue will be DNS or some thing else..
If he didnt get then the issue is with ur mailbox and if he gets the same error the issue will be DNS or some thing else..
ASKER
Failure message posted above yours. I'll try from another mailbox right now.
ASKER
Here is a cut/paste from queue:
Identity: mail\93116\263227
Subject: This is a Test....
Internet Message ID: <FB123A6A5B658A4F8040AD016 B9FD1D5021 DEB1F7A23@ mail.wcsec urity.com>
From Address: carolina@wcsecurity.com
Status: Retry
Size (KB): 27
Message Source Name: FromLocal
Source IP: 255.255.255.255
SCL: -1
Date Received: 9/30/2011 10:23:49 AM
Expiration Time: 10/1/2011 10:23:49 AM
Last Error: 451 #4.1.3 Domain of sender address <carolina@wcsecurity.com> does not exist
Queue ID: mail\93116
Recipients: removed@usarec.army.mil
Identity: mail\93116\263227
Subject: This is a Test....
Internet Message ID: <FB123A6A5B658A4F8040AD016
From Address: carolina@wcsecurity.com
Status: Retry
Size (KB): 27
Message Source Name: FromLocal
Source IP: 255.255.255.255
SCL: -1
Date Received: 9/30/2011 10:23:49 AM
Expiration Time: 10/1/2011 10:23:49 AM
Last Error: 451 #4.1.3 Domain of sender address <carolina@wcsecurity.com> does not exist
Queue ID: mail\93116
Recipients: removed@usarec.army.mil
So server cant reach it self from internet.
ASKER
I've tried changing the address space in the send connectors.. no luck there. What's strange is that this is the only domain that I can't send to...
Hi James,
Are you able to provide full headers from one of the mails sent through the same flow that are being delivered successfully? Sanitized as needed of course, but try to not mangle it too much. Basically I'm looking for envelope and body from, return-path, sending server IP, any auth results as reported by the receiving server, and anything else that seems abnormal. How your mail is treated is completely dependent upon the receiving servers' policies, which is why you are seeing inconsistent results while sending to/from other addresses/domains.
I don't know the public IP and/or hostname of your sending server(s) so I can't check DNS for that. I can assume it's mail.wcsecurity.com but that is just a guess. There is no SPF record for wcsecurity.com which could also be a contributing factor.
Are you able to provide full headers from one of the mails sent through the same flow that are being delivered successfully? Sanitized as needed of course, but try to not mangle it too much. Basically I'm looking for envelope and body from, return-path, sending server IP, any auth results as reported by the receiving server, and anything else that seems abnormal. How your mail is treated is completely dependent upon the receiving servers' policies, which is why you are seeing inconsistent results while sending to/from other addresses/domains.
I don't know the public IP and/or hostname of your sending server(s) so I can't check DNS for that. I can assume it's mail.wcsecurity.com but that is just a guess. There is no SPF record for wcsecurity.com which could also be a contributing factor.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
My hunch that it was a dns issue was correct. After a few hours of testing and moving the dns server to another service, all is good.