Still not routing e-mails

Still not routing e-mails (Full Version)

All Forums >> [Microsoft Exchange 2003] >> Message Routing

Message

texmansru47 -> Still not routing e-mails (15.Jun.2006 9:23:23 PM)
Is there any settings that I need to configure to get e-mail to route through my exchange server? I have one exchange server (no front end boxes) I have a ADS domain of mycompany.com The server is mailserver.mycompany.com The e-mail are to be routed to user@newcompanyname.com I have created an internal DNS zone for: newcompnayname.com In that I have: mail MX mailserver.mycompany.com (same as root) MX mailserver.mycompany.com mail A mailserver.mycompany.com Externally is still not ready thanks to the delays by AT&T, but I should be able to route from my old e-mail solution (iMail) to my internal Exchange server, but I cannot. I get no error messages, and the queues on the exchange server are zero! But no mail arrives at either mailbox (exchange or iMail). On the server, I have the receiptant policy (default) setup for user@mailserver.newcompanyname.com and user@newcompnayname.com (primary). I have also created a virtual directory called newcompanyname.com (under SMTP Virtual server). Finally, I have created a new SMTP connector (Called SMTP-OUT) pointing to mailserver.mycompany.com and it is to allow any domain in. This may not work due to AT&T so this is not a major concern for me right now. My issue is whay cannot I get internal e-mails to route? to me, if I can get this to work, once AT&T has finished my external side I should be right as rain. But I cannot figure this out. I need help fast!!!!!! Thanks,

uemurad -> RE: Still not routing e-mails (16.Jun.2006 2:49:22 AM)
I'm not sure I completely understand your setup, but what happens if you telnet via port 25 from your old mail server to your new server? Can you establish a connection? Can you issue all the SMTP commands for a valid message, and if so, can you see what happens to the message?

texmansru47 -> RE: Still not routing e-mails (16.Jun.2006 7:54:41 PM)
Please provide me an example such a command. I have telnetted in to my new server. Are there any questions I can clear up about the mail server configurations?

texmansru47 -> RE: Still not routing e-mails (16.Jun.2006 8:09:07 PM)
Here is what I got: 220 mailserver.newcompanyname.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready at 2006 12:53:17 -0500 500 5.3.3 Unrecognized command 500 5.3.3 Unrecognized command 503 5.5.2 Send hello first 500 5.3.3 Unrecognized command 503 5.5.2 Send hello first 500 5.3.3 Unrecognized command 503 5.5.2 Send hello first 250-mailserver.mycompany.com Hello [10.XX.XX.XX] 250-TURN 250-SIZE 4194304 250-ETRN 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-8bitmime 250-BINARYMIME 250-CHUNKING 250-VRFY 250-X-EXPS GSSAPI NTLM 250-AUTH GSSAPI NTLM 250-X-LINK2STATE 250-XEXCH50 250 OK 501 5.5.4 Invalid Address (for twilson@newcompanyname.com) 250 2.1.0 twilson@mail.newcompanyname.com....Sender OK 550 5.7.1 Unable to relay for twilson@mycompany.com 554 5.5.2 No valid recipients 221 2.0.0 mailserver.mycompany.com Service closing transmission channel Connection to host lost. C:\Documents and Settings\Administrator> The problem is the mail should be okay for twilson@newcompanyname.com but it failed. I know now I have some sort of a configuration problem with my server versus my DNS (internal), but what? I'm not getting error messages back to the senders. I get nothing, and the exchanger server show issues and nothing in queue. This is really concerning me since I need to get this resolved ASAP. I have never had this level of issues before, typically it is plug and play. Thanks,

texmansru47 -> RE: Still not routing e-mails (16.Jun.2006 8:21:27 PM)
I also cannot relay out to the external world... 550 5.7.1 Unable to relay for twilson@natcominc.com 500 5.3.3 Unrecognized command 550 5.7.1 Unable to relay for texwilson47@thewilsonzone.com Where can I check my relays? Thanks, Tom

liquid22 -> RE: Still not routing e-mails (16.Jun.2006 8:43:22 PM)
I didn't see this mentioned but is your MX record accessible from the Internet? You said internal DNS so wasn't sure if that's a DNS server on the Internet or not but without an MX record email systems on the Internet will not know where to route mail to. Your DNS server would need to be registered as a DNS server with a registrar (maybe this is what ATT&T is doing for you, don't know). A good test is www.dnsreport.com. Type in your domain and see if anything is returned. If it can't find an MX record or a DNS server that's the problem.

texmansru47 -> RE: Still not routing e-mails (16.Jun.2006 9:22:47 PM)
The answer is yes... AT&T finally got it working: Getting MX record for anovoamericas.com (from local DNS server, may be cached)... Got it! Host Preference IP(s) [Country] mail.anovoamericas.com. 10 12.181.192.41 [US] anovoamericas.com. 10 12.181.192.41 [US] What concerns me is when I telnet into the server, I cannot relay messages anywhere outside of the initial newcompanyname.com (not even the original mycompany.com domain). Now when i first built the server, I changed the default address from mycompany.com to newcompanyname.com when I setup the server. Would this be an issue? Anyway I cannot relay any mail, internally (mycompany.com) or externally (my domain twilson@texwilson47@thewilsonzone.com). Thanks,

liquid22 -> RE: Still not routing e-mails (16.Jun.2006 10:05:36 PM)
I can see that these two domains MX records are pointing to GoDaddy mail servers: natcominc.com thewilsonzone.com I don't know if those are the "mycompany.com" and "newcompanyname.com" that you're referring to or not. The anovoamericas.com does point to mail.anovoamericas.com so is that IP address the IP address of your Exchange server or firewall? When telnetting into the anovoamericas.com mail server it doesn't return a valid host name, it returns a bunch of asterisks and "0"'s *************************************************************************00**0' I seems like there is a DNS configurationg error somewhere but there's 3 domains listed here so I'm not sure which domains we're working with here but the two above (natcominc.com and thewilsonezone.com) definitely point to GoDaddy mail servers and not your Exchange server. If your email client is trying to send from those domains via your Exchange server it won't be able to.

texmansru47 -> RE: Still not routing e-mails (16.Jun.2006 10:34:19 PM)
natcominc.com is mycompany.com and should be registered via AT&T. thewilsonzone.com is my domain (external test) registered with GoDaddy. When I telnet the name of the server usftwexchmain.natcominc.com (I have a DNS for this to mail.anovoamericas.com - which seems to be working with the internal DNS). I do not get the --- and 0's External DNS: mail.anovoamericas.com MX 12.181.192.41 anovoamericas.com MX 12.181.192.41 via AT&T This is my mail server (external IP via AT&T). Now I NAT via a Cisco PIX firewall (515E) to an internal IP address of 10.XX.XX.XX. I have SMTP, http, pop3 and imap4 all open currently on the firewall for this translation. The identical configuration is setup for my current iMail server and it is working (different internal IP address of course). I can ping, tracert nslookup all the MX records internally, no problem. But I cannot confirm the relay of the mail outbound from the exchange server (via my telnet test (see previous posts in this chain). So I'm confused, beyond belief. Sorry for being a pain about this. But when you have been working on this for two weeks, everythign starts to look clean... I just cannot see where I screwed the pooch. I know it is some weird configuration I processed, just trying to find it is the booger. Let me know what other information I can post for you and I will. Thanks,

liquid22 -> RE: Still not routing e-mails (19.Jun.2006 12:51:00 AM)
You might want to double-check the natcominc.com domain because from dnsreport.com it looks like it's still pointing to GoDaddy unless the DNS changes just haven't propogated across the Internet yet. Maybe the PIX is causing the asteriks and zeros from my telnet test on the public side. Are you able to send an email to yourself or to another mailbox internally?

texmansru47 -> RE: Still not routing e-mails (19.Jun.2006 1:40:11 AM)
Natcominc.com is registered to AT&T and should not be with GoDaddy. I will double check that. as for the PIX I cannot confirm the e-amil to the anovoamericas.com since I cannot prove that the server is routing anything. I get the iMail (same PIX, different server). You cannot tracert to that device either since I have ICMP blocked. Below is the results of my NSLOOKUP to mail.natcominc.com > mail.natcominc.com Server: dnsr1.sbcglobal.net Address: 68.94.156.1 natcominc.com primary name server = dbru.br.ns.els-gms.att.net responsible mail addr = rm-hostmaster.ems.att.com serial = 1 refresh = 86400 (1 day) retry = 10000 (2 hours 46 mins 40 secs) expire = 604800 (7 days) default TTL = 86400 (1 day) May concern is two things. 1. Is the Exchange Server setup and working as it should? I cannot even send mail from an exchange account to another exchange account on the same server. Why? This should not be a DNS issue, should it? Shouldn't Exchange know its own domains? 2. Is the PIX setup correctly? We get the natcominc.com mail via the iMail server, with the same ACL as the PIX, but no exchange mail. I truly think I ahve something FUBAR on the server. NOW I reinstalled this version of Exchange without a proper uninstall of the first attempt (it SNAFUed big time). Could this create a routing problem (two different since I did not uninstall the initial Exchange serer name was still in the ADS tree. Also, once I rebuilt the server, I changed the domain name in the default routing policy by deleting the natcominc.com address space. I believe these actions may have a hand in the problem I am having. I just need to verify that... woudl these wrong steps be a reason why I cannot transfer mail? I would love to kill the iMail server and have natcominc.com and anovoamericas.com come over exchange, but do I ahve to reinstall the server correctly? Thanks,

liquid22 -> RE: Still not routing e-mails (19.Jun.2006 3:03:27 PM)
If you can't send mail to yourself then I don't believe DNS is the problem here. If you reinstalled Exchange on top of itself without uninstalling it the first time that could be part of the problem. Exchange should know its domain as long as the server that it is installed on is a member of your Active Directory domain. The recipient policy can have as many email domains as you want. The company I work for has 10 and only one matches our AD domain so I don't think that's your problem. It might be a good idea to completely remove Exchange and start over. Once its uninstalled correctly you may want to use ADSIEDIT and remove any references left over in Active Directory. Use that tool carefully though as you don't want to have to reinstall Active Directory. http://www.msexchange.org/tutorials/Remove-Exchange-server-entire-Exchange-organization.html

texmansru47 -> RE: Still not routing e-mails (19.Jun.2006 8:57:46 PM)
One question. I have deleted the accounts that had e-mail accounts on this server that wil be removed and rebuilt, but it keeps telling me that there are one or more still active. Is there a clean way to verify that everything has been removed so I can start this process? Also, the path to process a proper removal is: Remove users -> Remove Exchange 2003 Server -> verify Registry -> the run the ADSiutil command to confirm the remove from the ADS tree? Just trying to confirm since this article provided to run this is very confusing since the author is trying to convey too many points in one article. Thanks,

texmansru47 -> RE: Still not routing e-mails (19.Jun.2006 8:58:41 PM)
ADSiedit not ADSiutil, sorry.

liquid22 -> RE: Still not routing e-mails (19.Jun.2006 9:03:03 PM)
If you go into Exchange System Manager it should show you any mailboxes that are on the server. That path sounds correct to me. Good luck.

texmansru47 -> RE: Still not routing e-mails (20.Jun.2006 12:30:01 AM)
Thanks. Got the old exchange completely removed, rebuilt it and now e-mails are moving through no problem. The only problem noew is I cannot setup any user in outlook. It states that there is no user in the address book list that matches, which is total BS. This is the same for every user. How can I find answers to this query? Thanks,

liquid22 -> RE: Still not routing e-mails (20.Jun.2006 4:43:17 PM)
Make sure your Domain Controller is a Global Catalog server. If you only have one it should be but wouldn't hurt to double-check that. Also make sure your Recipient Update Service in Exchange System Manager is pointing to your Exchange server. I'd make sure the name listed is the actual name of the server.

texmansru47 -> RE: Still not routing e-mails (20.Jun.2006 6:00:51 PM)
I will check that and report back. Thanks for the heads up.

texmansru47 -> RE: Still not routing e-mails (20.Jun.2006 6:12:43 PM)
I have two DCs. For some reason the guy before me screwed up the ADS and the BDC has the GC. I pointed the policies to use that DC as the reference device. I also validated the server name (for Exchange) in those policies as well. When I tested the adding of an Exchange account to my Outlook I got: the same problem. Cannot match the name to the address list. One Question: Why Does MS makes this installation full of BS issues? I mean 5.5 as limited as it was a fairly good installation. Man, if you miss one step or accidently have a crash during the installation (like I did), you are FUBAR moving forward, how stupid. I can get e-mails to and fro from OWA (no Public folder though) and I cannot add accounts to outlook. Heck the darn server will not even be visible in the server area, what the haps? This is ridicilous.

liquid22 -> RE: Still not routing e-mails (20.Jun.2006 7:42:32 PM)
I would make both your DC's Global Catalog servers so you'll have some redundancy. In ESM (Exchange System Manager) go into the properties of your Exchange box, then click the Directory Access tab and make sure your DC is listed there. You should have one listed as a Configuration server, at least one as a DC, and one as a GC. If you're running two DC's you should see both listed there but since you have only one configured as a GC you should only see that one listed. What operating system is Exchange installed on? What about your DC's? Are they running on 2000 or 2003. At least email is flowing so we're getting closer. [;)] Can you log onto OWA with the new accounts you've just created? Make sure the Exchange server is still joined to the domain. Also make sure that the Exchange server is a member of the "Exchange Domain Servers" and "Exchange Enterprise Servers" security groups which should have been automatically created during the install.

Page: [1] 2 3 next > >>