Question Locked

How do I set up Exchange to receive emails once I change the MX records

0 helpful
18 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We just got a static IP and are changing the MX records on our external webhost to point to our internal Exchange server 2003 on SBS 2003 that all emails can be received via exchange as opposed to just internal office emails. I looked around and it just seems like I have to make sure that there are accounts on the exchange server that reflect the domain correct? So an email going to person1@domain.com should have an account on the exchange server that is person1@domain.com? Is that all I have to do, or is there more to it?

18 replies

by pshiflet-24

If Exchange is already functioning internally with working SMTP connectors the main change you would need to make would be to forward the appropriate ports through your router so inbound mail makes it to your server. The ports are typically 25 (SMTP), 110 (POP3), 143 (if you support IMAP), and 143 (for Outlook Web Access).

I hope this helps. If you have already done this and are still not receiving email, let us know. Thanks.

by mlieberman

I changed over the MX records and I have everything forwarding over, and I know in the very least it reaches our server correctly because any emails don't reach our backup MX record which is my external webhost. I am forwarding the ports correctly. Is there anyway to check? I am using SBS 2003 which I know sometimes has slightly different settings for things. I know I had to change a lot of SMTP connector settings before we got our static IP because verizon didn't allow us to forward through their smart host, and we were on a dynamic IP so a lot of email servers would block us by default, so I don't know if there's any setting I might have changed that might be blcoking something.

by pshiflet-24

Well, I assume that you can still send and receive internal messages as well as send email outbound. Is that correct? If so, can you telnet into the server on port 25 from both the LAN and the Internet? Is the server firewall turned off or configured to allow inbound traffic? And lastly, regarding your old dynamic IP, did you happen to setup anything for dynamic DNS with a third party that may be misdirecting your inbound messages such as DynDNS?

Please let me know. If you cannot Telnet into the server from the Internet using both the static IP and the MX record name what message do you get? Thanks.

by mlieberman

I can telnet from both the LAN and the internet. I get

220 (domain omitted) Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at Fri, 3 Apr 2009 10:46:42 -0400

IMAP and POP3 are also accessible correctly as I can telnet into them as well.

as the message. I did have a dynamic dns through dyndns, and I think its still set up on our router to update so its still set up. Could that be causing some sort of conflict though? Its only set up as a forwarding service so [whatever].dynalias.com would forward to our internal website so people could log in and download the VPN client, have remote access, be able to view outlook web access etc. Should I disable that? When I did set up the MX records I just had it go directly to our static IP, I didn't use any forwarding via dyndns.

by pshiflet-24

First, I would disable the DynDNS service. With the static IP you don't need it anymore and I suppose it could be causing some issues (but I doubt it). Users can now log in remotely using your static IP. Since you can telnet into your server, the problem is most likely in your SMTP virtual server rejecting outside domains.

Check out http://technet.microsoft.com/en-us/library/aa995718(EXCHG.65).aspx to test your SMTP access more thoroughly. Please let me know what the results are. Thanks.

by mlieberman

I started running through the tests that you suggested and most work except MAIL FROM: which gives the error

500 5.3.3 Unrecognized command

Also RCPT TO: gives me the error 503 5.5.2 Need Mail From: first

by mlieberman

AUTH LOGIN gives me the message

504 5.7.4 Unrecognized authentication type

I'm not sure if I set up AUTH for the SMTP server/connector? I am not sure which I'm even supposed to be really using.

by pshiflet-24

Firstly, with server 2003 I believe ehlo has to be changed to helo. Additionally, the error you are getting seems to happen if you don't have a space between "MAIL FROM:" and the address. Is that a possibility? Please let me know. Thanks.

by mlieberman

I checked, it is EHLO and I checked every variation of mail from. mail from , mailfrom mail from:, mail from: .

by pshiflet-24

Try, instead of AUTH LOGIN, AUTH NTLM LOGIN. Let me know the results. Thanks.

by mlieberman

I tried it, and it just instantly kicks me off the connection.

by pshiflet-24

To be sure, you are entering "MAIL FROM: "+ your address (all caps, space between mail and from and between the : and the adress). Additionally, it must be entered without any mistyping such as backspacing to correct anything or arrowing to change something.

Also, can you check your server to determine what type of authentication you are using on your SMTP virtual server? Let me know. Thanks.

by mlieberman

It seems to be working now "MAIL FROM:" I didn't realize if you had any commands that didn't go through correctly before it, it would respond back that its an unrecognized command. Also my authorization type on my SMTP virtual server is Anonymous and Integrated Windows Authentication. Outbound security though is set for Anonymous access.

I also just went through the whole thing making sure that I don't backspace or go through any commands incorrectly and it works as long as I don't try to authenticate. However I still can't receive emails sent to our exchange server.

by pshiflet-24

Yeah, telnet can be a pain. Are you able to go through the SMTP testing process from outside of your network? With anonymous authentication you don't need to do the AUTH command at all. Use a MAIL FROM: with an outside email address and a RCPT TO: of an email account you are hosting. Let me know what the results are. If you can telnet into the server (from outside the LAN) with the IP but not the mail.yourdomain.com then there is a DNS issue possibly caused by your previous DynDNS entry. Otherwise, it is most likely a SMTP problem.

I hope this helps.

by mlieberman

When I telnet into mail.mydomain.net it just sends me back to my webhosts SMTP server. though mail.mydomain.net was set for my static IP.

by mlieberman

My webhost changed their DNS servers and didn't tell me until I just called them up to figure out if it was something on their end. So even though their old DNS servers worked, it just wasn't updating correctly.

Thanks for all the help though!

by pshiflet-24

Sorry for the delay getting back to you. I'm glad you got everything figured out. Let me know if you have any other questions. Otherwise, have a good weekend.

This discussion is closed to new replies.