Q: I went through the / forestprep and / domain prep as you have suggested and guess what? It finally installed without a hitch:)
I sending e-mails sought within the LAN and it works, so thats great. Can also e-mails outside my LAN to my hotmail and Yahoo accounts. But when I reply to my Yahoo e-mail or e-mail, it seems to go by without me one of those destination unreachable messages. When I go back to the LAN email and try to see if it came, it does not: (Is there some sort of configuration or port mapping on my Linksys router I have to?
Ive set this in my server in DNS when the MX domain server.
The one2free.ca I want to send. I have registered the domain name via easyDNS. Perhaps there is some sort of misconfiguration there. Give me a hand if you can, is thx.
This so exciting, I finally got it installed. Whoopee!: D
Re:Well, it could be a DNS problem. What I have seen in the past was someone made an MX record like the following:
x.x.x.x MX 10 MAIL.DOMAINNAME.COM
when in fact it sould just be the domain name, not the entire FQDN of the host (DOMAINNAME.COM not MAIL.DOMAINNAME.COM).
Also, if you have a firewall, make sure that you have a reverse NAT entry for your SMTP server. A reverse NAT is just a name for making an entry for a public IP to a private IP address.
Re:<< Got an email back from Yahoo saying that they cannot establish an SMTP connection to my server. >>
But they knew it was supposed to go to your server, right? Like they listed the FQDN of it? If so, your DNS is fine.
I would suggest the relay tip above.
You want it to be "Only the list below" with the pub/priv IP of the server in the box.
Re:Relaying can affect routing of email from the Internet. Read this KB Article (http://support.microsoft.com/default.aspx?scid=%2fsearch%2fviewDoc.aspx%3fdocID %3dKC.Q153119%26dialogID%3d5045837%26iterationID%3 d1%26sessionID%3danonymous%7c4456735) to test whether or not you can route email in from the Internet. This will have to be done with a machine on the Internet with a public IP address. So, you may have to use another machine that can dial out to an ISP. If you can successfully route email using this test, then the problem lies with your DNS entries. They sould look like the following:
A record x.x.x.x servername.domainname.com
MX record 10 domainname.com
The 10 only represents the MX priority in your DNS zone. The lower the value, all SMTP servers will try to use this address. You can create more than one with different priorities for redundancy, but in a single domain/single Exchange server, this is not necessary.
If routing does not work, and you get 5.7.1 Relaying Denied, then your Relaying settings are incorrect. What you will need to do is make sure you have the following set correctly in the SMTP Virtual Server:
UNDER THE ACCESS TAB:
* click on RELAY
* Make sure that ONLY THE LIST BELOW is selected
* Make sure that the Private and Public IP address is given GRANTED Access under the COMPUTERS field
* Make sure that ALLOW ALL COMPUTERS WHICH SUCCESSFULLY… is checkmarked.
* Click OK
* Click on Authentication
* Make sure that Anonymous and Integrated Windows Authentication is checkmarked
* Click OK
There is no reason to restart the SMTP service.
You will also need to make sure that YOU DO NOT HAVE AN SMTP CONNECTOR. To check this, navigate to the ROUTING GROUPS, then the default FIRST ROUTING GROUP, then to CONNECTORS. Make sure that there is nothing configured here and that there are no connectors here, unless you have another Exchange server or site you want to connect to. If this server will be your only Exchange server, then you do not need any SMTP connector or any connector for that matter configured here.
Hope this helps.
Re:A bump to let you know that at least ONE person is reading your thread…DNS changes on the Internet can take a while to take effect, so I would wait at least 24 hours before giving up.
The "Relaying" setting sounds wrong–you shouldn't allow relaying to the world.
I don't think the relaying setting will affect the ability to get mail from another mail server. (Level of Confidence in that statement is not too high)
–guy
Re:Under System Manager, under Server, SMTP virtual server properties, relaying was set something to the effect of "only the list below" which was empty, so I had changed that to "all except the list below". Maybe my SMTP server wasn't allowing connections, perhaps that's why?? Well, we'll see in a jiffy what happens.
Plucky
Re:Got an email back from Yahoo saying that they cannot establish an SMTP connection to my server. So its something I'm not doing or doing wrong. Hmmm…
Re:Still can't receive mails from the 'net, anybody wanna gimme a lil hand here? Si vous plait?
Re:Just did a reboot, and Exchange didn't come up when I opened OutLook, so I had to manually go into services and start them up, then OutLook connected to the Exchange server. Weird.
Still not getting my emails from the Internet. Aargh
Re:Oops, my EasyDNS host and mx records were incorrect, just did a change on that. Perhaps that was why I can't receive any emails inside the LAN from the Internet. We'll see in a jiffy.
Re:BTW, I can now go http://<servername>/exchange and get to my Outlook Web Access in Windows 2000.
I was at this one business place where they were running an NT 4.0 network and using IE 5.5 and I tried doing the above thru OWA and it didn't work. Is this a feature only on Exchange 2000?
Thx,
Plucky
0 Comments.