Exchange 2003 will not receive email

Exchange 2003 will not receive email (Full Version)

All Forums >> [Microsoft Exchange 2003] >> Installation

Message

shaines -> Exchange 2003 will not receive email (8.Jan.2005 2:53:00 AM)
I am trying to change a site from Exchange 5.5 to using a SBS advanced edition Exchange 2003 server. The site uses a router. I have redirected the port 25 traffic to go to the 2003 server but the email addresses I have setup do not show as valid. How do I get the email to come in on the same domain to the new server? I tried the wizard but it still does not work.

Velocat -> RE: Exchange 2003 will not receive email (8.Jan.2005 4:54:00 AM)
Can you tell us: Are the two exchange servers in the same Windows domain and same ORG, or separate? What errors do you receive now that emails are being directed at the exchange 2003 server? Which wizard are you referring to? Any more information you can provide will help.

shaines -> RE: Exchange 2003 will not receive email (8.Jan.2005 5:12:00 AM)
Hi Eric. I have built a new domain. I redirect the port 25 traffic on the router to go to the new server. I can telnet to the new serve on port 25, but the email SMTP addresses do not show as valid on an email test from http://msv.dk/ms980.asp The wizard for 2003 - http://www.msexchange.org/tutorials/Using_Exchange_2003_Mail_Wizard.html I can send email out to the Internet but am unable to receive email on their domain. I was wondering if I need to look at DNS forwarding but this may be related to outgoing email. I think I have something configured incorectly in the SMTP setup.

Velocat -> RE: Exchange 2003 will not receive email (8.Jan.2005 11:42:00 PM)
if the mail test is failing, try testing your DNS from this site: http://www.dnsreport.com Put your domain into the TEST DNS field. Let us know your results, specifically the MX portion.

shaines -> RE: Exchange 2003 will not receive email (9.Jan.2005 6:16:00 AM)
Thank you Eric. I will give that a try after I reroute the port 25 traffic back to the SBS Exchange server on Sunday. The strange this is that I can access the server but none of the addresses I have setup will receive email from the Internet even though the SMTP entries look fine.

Guest -> RE: Exchange 2003 will not receive email (9.Jan.2005 6:41:00 PM)
Try this from an internal system: telnet your-exchange-server 25 helo yourcomputername.com 25 mail from:<youremail@address.com> rcpt to:<youremail@address.com> data Subject: This is a test This is a test email. . Type all that and let us know what you receive as a response after the ".".

shaines -> RE: Exchange 2003 will not receive email (9.Jan.2005 9:16:00 PM)
Afte that I get: 354 Start mail input; end with <CRLF>.<CRLF> 250 2.6.0 <COMP-MUSK-SRV1Y2Rl600000001@COMP-MUSK-SRV1.cewsi.loc> Queued mail for delivery

Velocat -> RE: Exchange 2003 will not receive email (10.Jan.2005 8:00:00 PM)
I think I need to confirm your problem. You have old-domain and new-domain. You have new server using new-domain. You would like to receive email for user1@old-domain.com on the new server? If that is the case, open Exchange System Manager and drill down to: ORG Recipients Recipient Policies Open the properties for "Default Policy" Go to the "E-Mail Addresses (Policy)" tab. Click new, choose "SMTP Address", and type in your "@old-domain.com" domainname. Click ok and close the properties. Now right-click the "Default Policy", and choose Apply this policy now. This will provide all your users with a new SMTP address of user1@old-domain.com. You can check this by going into Active Directory Users and Computers, looking a a users properties and checking the "Email Addresses" tab. Let us know if this is what you were looking for.

shaines -> RE: Exchange 2003 will not receive email (10.Jan.2005 10:08:00 PM)
Thank you for the reply Eric. The domain is unchanged. They are going from an NT4/Exchange5.5 server to the Win2003 SBS server with Exchange 2003. I just want the email to go to the new server instead of the old one. They use a Linksys router, so I re-direct the incoming port 25 traffic to the new server. I can telnet on port 25 to the new server but it times out when I run an email checker for a valid SMTP address on the new server. I am not sure if there is some sort of time lag involved. Also, their NT4/55 server is about out of drive space for the priv.mdb file. I do not know if queued email is causing the problem. I have not tried leaving the port 25 traffic pointed to the new server for an extended period of time. I am at the point where I may open a $250 case with Microsoft - $$$$ouch$$$$

shaines -> RE: Exchange 2003 will not receive email (11.Jan.2005 5:30:00 AM)
The error I am getting when I test an email to the Win2003 server is: SMTP Server Failure: Operaton Timed Out I did update the receipient policy - no change. On other email tests I got messages like "connection closed before all data was sent". I am going to check things out with the ISP but I suspect it is something with the 2003 exchange server. This sure seems wierd to have this issue. I thought this was the lastest & greatest.

shaines -> RE: Exchange 2003 will not receive email (11.Jan.2005 5:18:00 PM)
I also found this information. This looks as though it could be an SMTP timeout parm issue. Any thoughts from anyone on this? I've been trying to troubleshoot a very strange mail issue on an SBS2003 (Exchange 2003) server for about 6 weeks now and am desperately looking for help. Here is a sample of what I'm working with (failed inbound SMTP session): date time c-ip cs-username cs-method cs-uri-query sc-status sc-win32-status sc-bytes cs-bytes time-taken 2004-12-14 16:09:42 65.54.187.77 hotmail.com EHLO +hotmail.com 250 0 171 16 0 2004-12-14 16:09:42 65.54.187.77 hotmail.com MAIL +FROM:<johnrabel@hotmail.com> 250 0 46 33 0 2004-12-14 16:09:42 65.54.187.77 hotmail.com RCPT +TO:<Dick@recipientdomain.com> 250 0 0 25 93 2004-12-14 16:20:10 65.54.187.77 hotmail.com TIMEOUT hotmail.com 121 1304114753 84 4 627797 2004-12-14 16:20:10 65.54.187.77 hotmail.com QUIT hotmail.com 240 628063 84 4 627797 A small formatted Excel spreadsheet with more logs of both failed and successful sessions can be quickly opened at: http://pics.virtuality.org/linkto/email_troubles.xls An Exchange server I manage has been processing inbound SMTP connections that result in a 121 TIMEOUT. The messages never get delivered locally and an NDR is not sent from my Exchange server, though the originating server usually kicks back a failure notification to the sender after the retry period expires. Of the thousands of messages that the server processes daily, a fairly steady group of sender domains consistently (but not always) have trouble delivering email to my server while most messages come through fine. A log review shows that the failed connections get "stuck" after my server receives the RCPT command. The sessions on my side look like: EHLO remotemailserver.com MAIL .. RCPT .. (10 minute wait) TIMEOUT .. QUIT .. At first I assumed it was a firewall issue on my side that was blocking the BDAT verb which would normally come after RCPT when advertising ESMTP. I removed the CHUNKING advertisement to prevent binary data formats from being used for inbound SMTP and forced HELO for outbound SMTP, but the problem persisted. I then decided to replace the consumer model SMC firewall with a Cisco 2651 router with the firewall feature set (NBAR and CBAC). Unfortunately the firewall upgrade didn't change or improve the mail symptoms one bit, so I can't imagine it's still a firewall issue at this point. One consistent anomoly in the logs has to do with the sc-win32-status result on the connections that time out, though I don't know what the result means. The TIMEOUT line for a failed connection has a sc-win32-status result with a very large number such as 2175011793. (more examples in the .xls file link above) So far I've seen failed inbound sessions from 6 legitimate businesses that communicate with users on my Exchange server, and occasionally from domains like hotmail.com, ebay.com and other very large mail domains, but never any UCE or junk mail sessions. I've attempted to recreate the problem using my own email accounts, both with and without attachments, but have not been able to recreate the problem. The failed messages never successfuly get delivered after retries.. they permanently fail. I've searched both the web and newsgroups and found similar symptoms from folks going back to 2002 and using both Exch2k and 2k3, but never any solutions that were documented. Any suggestions would be greatly appreciated. I'm going nuts trying to figure this out!

Velocat -> RE: Exchange 2003 will not receive email (12.Jan.2005 2:59:00 AM)
What happens when you run a telnet session from the exchange 2003 server itself? Does the connection still timeout? If not, then you should look into connectivity issues. If so, then there's an issue with the application somewhere. Anything interesting in the logs? (smtp logs need to be turned on). Let us know the result, even if you hit up MS Support for the $250.

shaines -> RE: Exchange 2003 will not receive email (12.Jan.2005 5:32:00 AM)
I can connect via telnet from the Exchange 2003 server with no problem. I also opened a couple of posts in Microsoft's forum. If I am unable to resolve the issue by tomorrow I will bite the bullet and open a case with Microsoft. I will post the results on this thread. Hey Eric - just curious. How does this forum work with the member rating. I see you are a Senior Exchange member. What do you do to get to that level?

Velocat -> RE: Exchange 2003 will not receive email (12.Jan.2005 8:29:00 AM)
Hi Steve, Sounds like you have network connectivity issues. Good luck if you contact MS Support. Hopefully they'll assist you with that. Regarding the ratings, the Junior, to Senior level jump comes after you post a certain number of messages...I forget the exact number, 30 or 50 or 60...somewhere in that range. The "Member rating" (the stars) are based on forum member feedback/votes. [ January 12, 2005, 08:30 AM: Message edited by: Eric Cross ]

shaines -> RE: Exchange 2003 will not receive email (12.Jan.2005 1:26:00 PM)
Eric - thanks for the info. Why did you say that I have network connectivity problems when I was able to telnet to my Exchange server on port 25 from itself? I can also send email out from it.

Velocat -> RE: Exchange 2003 will not receive email (12.Jan.2005 6:30:00 PM)
Because, you have SMTP timeout issues from other systems (I assume outside your network), but from itself you seem to have no issues whatsoever. Is that not the case?

shaines -> RE: Exchange 2003 will not receive email (12.Jan.2005 6:59:00 PM)
I can telnet to the exchange server from both inside and outside (Internet) the network. No connectivity issues that I am aware of.

Velocat -> RE: Exchange 2003 will not receive email (12.Jan.2005 7:08:00 PM)
What happens when you try this from both outside/inside network: telnet exchangeserver.domain.com 25 helo yoursystem.yourcomputer.com mail from:<youremailaddress@domain.com> rcpt to:<youremailaddress@domain.com> data Subject: This is a test Testing from [in,ex]ternal location. . Do you receive both emails?

shaines -> RE: Exchange 2003 will not receive email (12.Jan.2005 7:15:00 PM)
I am able to send and receive emails internally. The problem is that I am unable to receive Internet email from the outside. From the Internet I am able to telnet to the server on port 25 so I know I have a connection. When I run an email check using http://msv.dk/ms980.asp I get: Found 2 mail records (the primary & secondary MX addresses) then "The email address xxx@xxx.com appears to be invalid. [SMTP Server Failure: Operation timed out].

Velocat -> RE: Exchange 2003 will not receive email (13.Jan.2005 12:04:00 AM)
Try turing on smtp logging and make sure your getting hits from outside your network.

Page: [1] 2 next > >>