18 replies
by mlieberman Accepted solution
by pshiflet-24 Accepted solution
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 Accepted solution
by pshiflet-24 Accepted solution
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 Accepted solution
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 Accepted solution
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 Accepted solution
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 Accepted solution
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 Accepted solution
by mlieberman Accepted solution
by pshiflet-24 Accepted solution
by mlieberman Accepted solution
by pshiflet-24 Accepted solution
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 Accepted solution
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 Accepted solution
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 Accepted solution
by mlieberman Accepted solution
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 Accepted solution
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending