TechRescue
asked on
emails from a few specific domains timing out against Exchange 2003
Hello;
We recently migrated a cleint to SBS 2003 and Exchange. everything is working super, but some users complain that they are not recieving email from a a few specific domains, the bounced email from the original senders say
" ************************** ********** **********
** THIS IS A WARNING MESSAGE ONLY **
** YOU DO NOT NEED TO RESEND YOUR MESSAGE **
************************** ********** **********
The original message was received at Tue, 16 Oct 2007 10:21:53 -0400 fromXXfe01.XX.XXXX[**.**.* *.***]
----- Transcript of session follows ----- <XXe@cXXX.com>... Deferred
Warning: message still undelivered after 4 hours Will keep trying until message is 5 days old
"
and
"The following recipient(s) could not be reached:
X@XXXX.com on 10/23/2007 5:37 PM
Could not deliver the message in the time limit specified. Please retry or contact your administrator.
< smtp.XXX.com #4.4.7>
"
To me this seemd like a DNS error on the sender's end as it occured a day or so after the migration, but the problem has persisted for 2 weeks now.
all the DNS records, MX, PTR, etc. for the exchange server are correctly entered with their domain registrar who is also their ISP. Its only these few senders from specific domains, one of which is verizon.net, and it seems unlikely that Verizon configured their mail servers wrong or failed to update DNS.
the Exchange installation is basically stock but we are using IMF, set to archive bad mail. a cursory test of turning IMF off had no effect on this issue.
TIA,
We recently migrated a cleint to SBS 2003 and Exchange. everything is working super, but some users complain that they are not recieving email from a a few specific domains, the bounced email from the original senders say
" **************************
** THIS IS A WARNING MESSAGE ONLY **
** YOU DO NOT NEED TO RESEND YOUR MESSAGE **
**************************
The original message was received at Tue, 16 Oct 2007 10:21:53 -0400 fromXXfe01.XX.XXXX[**.**.*
----- Transcript of session follows ----- <XXe@cXXX.com>... Deferred
Warning: message still undelivered after 4 hours Will keep trying until message is 5 days old
"
and
"The following recipient(s) could not be reached:
X@XXXX.com on 10/23/2007 5:37 PM
Could not deliver the message in the time limit specified. Please retry or contact your administrator.
< smtp.XXX.com #4.4.7>
"
To me this seemd like a DNS error on the sender's end as it occured a day or so after the migration, but the problem has persisted for 2 weeks now.
all the DNS records, MX, PTR, etc. for the exchange server are correctly entered with their domain registrar who is also their ISP. Its only these few senders from specific domains, one of which is verizon.net, and it seems unlikely that Verizon configured their mail servers wrong or failed to update DNS.
the Exchange installation is basically stock but we are using IMF, set to archive bad mail. a cursory test of turning IMF off had no effect on this issue.
TIA,
ASKER
none related to these emails- also, no NDRs for these emails- it's like they aren't even hitting the server, which if why my first thought was that senders hadn't updated DNS, but that was 10 days ago
I have flushed and refeshed DNS on the server several times w/o result and verified the domain with nslookup and also dnsstuff.com.
a follwo up question to all - why would Exchange 03 not respond to a request from 1 domain over another? I'm not using reverse DNS or doing anything screwy with the Exchange install at all aside from IMF.
I have flushed and refeshed DNS on the server several times w/o result and verified the domain with nslookup and also dnsstuff.com.
a follwo up question to all - why would Exchange 03 not respond to a request from 1 domain over another? I'm not using reverse DNS or doing anything screwy with the Exchange install at all aside from IMF.
When you upgraded the customer do you chnage the MX records, I mean are they different now than before the SBS 2003. It sounds like the MX records are not being read correclty by other mail servers. I dont think these messages are even hitting your SBS box. Mayby its worth an email to your hosting company to see if there is a problem with yours domains DNS.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Also rerun the internet connection wizard on the SBS: Certainely can't hurt and it will reset your DNS too. Server Management> To Do List> Point 2.
Olaf