Exchange 2007 Setup 2

[jjatsk]

Hello, i am brand new to Exchange and need some help. I am setting this up in my little test enviroment first on my own personal email before i try it here at work. Here is what i have done so far and lost now.

Currently have email thru GoDaddy

Used one of my useable IP address's and forwarding ports 25 & 443 to my exchange server

Installed 2008 domain controller

Installed a member server and installed Exchange 2007 on that

Updated fully

Set the Logs and Database to seperate hard drives

Now i am completely lost on what to do next.

My internal domain name is testdomain.local and my external domain is example.net.

I know i have to create an A record and MX record but not positive on what im doing?

A Record =
mail.example.net
Point to IP i setup for 25 & 443 on the exchage server?

MX Record =
Priority 1
Host (mail.example.net)
Goes To (example.net.s7a1.psmtp.com.)


Thanks for any help

 

[58sniper]

Once you have 25 and 443 forwarded through your firewall (although ISA in the DMZ would be better for 443, and Edge Tranport in the DMZ would be better for 25), verify from the outside that you can connect to the server.

Then:
create an A record for your public IP address. Something like mail.example.net

Once it's done, very you can telnet to mail.example.net over port 25 and get to your server

Once you've done that, edit the MX record for example.net to point to mail.example.net. If there is only one MX record, priority doesn't matter.

Once that's done, give it time to kick in, and then you should be able to send mail to it. Keep in mind that example.net isn't a valid domain for you to use. Replace as needed.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[jjatsk]

Thanks for the reply.

Once you have 25 and 443 forwarded through your firewall (although ISA in the DMZ would be better for 443, and Edge Tranport in the DMZ would be better for 25), verify from the outside that you can connect to the server.
I verified this and is good

Then:create an A record for your public IP address. Something like mail.example.net
I created this and pointed it to my WAN IP

Once it's done, very you can telnet to mail.example.net over port 25 and get to your server
Have to wait until it kicks in (1 hour i think)

Once you've done that, edit the MX record for example.net to point to mail.example.net. If there is only one MX record, priority doesn't matter.
I have 4 of these setup for Postini. I edited the host part to go to mail.example.net

Keep in mind that example.net isn't a valid domain for you to use. Replace as needed
Yeah i just used example in place of my actual domain

Now once this is done. I am lost on other parts like my internal and external domain are different so how does your email work when they are different. I want to use my external domain email address and not the internal email address.

Also i want to use GoDaddy for smtp. Is that possible and how do i set that up?

 

[58sniper]

There shouldn't be an internal and external email address. The internal AD domain is irrelevant. Make sure your real SMTP domain name appears in Exchange as an accepted domain.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[jjatsk]

Ok i have got a little farther. I can send email out just fine but cant recieve.
I am testing this with a couple test servers at my work with my own personal email
My hosting company is GoDaddy
My ISP at my work is Cbeyond
If you need any other info just let me know. Im sure i am missing something. Thanks for your help


A (Host)
Host Points To TTL Actions
@ 208.109.181.210 1 Hour
mail WAN IP 1 Hour
owa WAN IP 1 Hour


MX (Mail Exchange)
Priority Host Goes To TTL Actions
1 mail kehn.net.s7a1.psmtp.com. 1 Hour
2 mail kehn.net.s7a2.psmtp.com. 1 Hour
3 mail kehn.net.s7b1.psmtp.com. 1 Hour
4 mail kehn.net.s7b2.psmtp.com. 1 Hour
50 @ smtp.secureserver.net 1 Hour
100 @ mailstore1.secureserver.net 1 Hour

 

[58sniper]

You're not going to receive mail until your MX records are pointing to the correct A record (mail.yourdomain.com)

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[jjatsk]

Thanks again.

So on the MX record i need to edit the (Host) part or the (Goes To) part?

MX (Mail Exchange)
Priority Host Goes To TTL Actions
1 mail kehn.net.s7a1.psmtp.com. 1 Hour
2 mail kehn.net.s7a2.psmtp.com. 1 Hour

If i edit the (Goes To) part with "mail.kehn.net" then how does Postini work?

I have had postini for about a year now. These are the MX records they orginally gave me.
1st priority record: kehn.net.s7a1.psmtp.com.
2nd priority record: kehn.net.s7a2.psmtp.com.
3rd priority record: kehn.net.s7b1.psmtp.com.
4th priority record: kehn.net.s7b2.psmtp.com.

 

[58sniper]

If you want mail to go directly to your exchange server, remove the second MX, and edit the first so that it goes to whatever your A record points to (mail.domain.com).

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[jjatsk]

I did what you said and that worked (I could recieve email) BUT it's not filtering through Postini then. How can i make my Postini MX records work? They have to work somehow right?

 

[58sniper]

You'd have to set the MX records back to Postini's SMTP servers. You'd have to tell Postini to deliver to your new IP address instead of the old.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[cceng]

Make sure on Postini's side you have setup the forwarder to the IP adddress you designated for your email server. it sounds like this hasn't been done and thats why you not receiving email through them.

Chris

 

[jjatsk]

Thanks to both for pointing me in the right direction on what to do. It took a little bit and a ton of research but i finally got it going. Here is what i did.

A (Host)
Host Points To TTL Actions
@ 208.109.181.210 1 Hour
mail WAN IP 1 Hour
owa WAN IP 1 Hour


MX (Mail Exchange)
Priority Host Goes To TTL Actions
1 @ kehn.net.s7a1.psmtp.com. 1 Hour
2 @ kehn.net.s7a2.psmtp.com. 1 Hour
3 @ kehn.net.s7b1.psmtp.com. 1 Hour
4 @ kehn.net.s7b2.psmtp.com. 1 Hour
10 @ mail.kehn.net 1 Hour

Then on Postini you log into the
"System Administration" Panel
--> Org & Users tab
--> change to "email config 1" in the Choose Org box
--> Then click on the "Inbound Servers" tab
--> Under that will be a "Delivery Mgr" catagorie
--> In the Delivery Mgr you will see an "Edit" button
--> In the Edit section you will see 2 sections

Email Servers & Load Balancing
Email Servers: change this to the WAN IP address of where your exchange server is.

Fail Over
Email Servers: smtp.secureserver.net (my orginal one)

Hit submit and it should come back ok. It will tell you if it's not.

Gave it a little time and it started working

 

[58sniper]

I'm assuming that mail.kehn.net is your A record pointing to your WAN IP. Having an MX record pointing to that as well as others that point to Postini isn't recommended. Many spammers will find the MX record with the lowest priority, and hit that, with the logic that some companies skimp on message hygiene on that record because it will hopefully never be used.

You may find spam coming into your environment that way.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[jjatsk]

Yeah the mail.kehn.net is where my A record is pointing to. Thanks for the info on that MX record. I will take that last one out and see what happens. Dont need any extra spam