Becoming an Exchange Server master!

I setup an SMTP send connector.

Now if i send an email from my internal mark@homelab.com to my yahoo account what is going on. Does Verizon drop it since it is port 25 coming out?
 
So to receive mail for a domain that is not the same as the internal homelab.com domain do i create a new accepted domain and add the address under the user mailbox E-Mail addresses for SMTP and set that as the reply email? what about a new receive connector, do you need to do all 3? can you just change the hostname in the default receive connector?
 
SJConsultant said:
Exchange Master eh? Wait until something breaks.........:p
Click to expand...

Yea really. It has gotten better though. At least with exchange 2007/2010 if you are running standard and something breaks hard you can uninstall that entire role and redo it. Ever have to rebuild webmail in exchange 2003? What a pain in the ass. Had it break in 2007 when they released a patch that was suppose to stop it from breaking. Re installed the entire role to fix it quick.

YeOldeStonecat said:
At least it got better since the abortion of 2007. Ugh..what a pain..and fix after fix.
Can't stand how you can even adjust pub folder permissions in the GUI.
And message tracking center is as painful as plucking pubic hairs with vise grips...holy crap did they butcher that.
Click to expand...

Yea I've had a bunch of issues in 2007. The auto discovery for one was always breaking.
 
AMD_Gamer said:
So to receive mail for a domain that is not the same as the internal homelab.com domain do i create a new accepted domain and add the address under the user mailbox E-Mail addresses for SMTP and set that as the reply email? what about a new receive connector, do you need to do all 3? can you just change the hostname in the default receive connector?
Click to expand...


Accepted Domain= Domain name you want to receive for. You can add more than one. then set one as default.

Then you add the domain name to the account and make it the reply email

Receive connector=Use this to limit who you get/receive email from, has nothing to do with who you are. By default it should be everyone: 0.0.0.0-255.255.255.255
 
the-one1 said:
Internal domain does not have to match external name. If its a lab or a small company, I actually prefer to keep them different.

Internal: domain.local
External:companyname.com

When you buy the certificate from godaddy, you'll specify the names to be on it as:
servername.domain.local
domain.local
mail.companyname.com
companyname.com
autodiscover.companyname.com

To me, this way its easier to keep track of what goes where.

Have fun with the learning process. Better to learn it when you're not under a deadline.


EDIT: You specify in Exchange what external domain name(s) you'll accept/receive/respond to.
Click to expand...

You can also just buy a cheap certificate with the internet fqdn. I have a bunch of domains with 1 or 2 email accounts so its not practical to have a certificate for each host so I used the DNS SRV method to setup autodiscover.

This comes in handy: https://www.testexchangeconnectivity.com/
 
SJConsultant said:
Exchange Master eh? Wait until something breaks.........:p
Click to expand...


I have a generated email that goes to a distribution list, for one of the users on the list, the email is deleted as soon as it hits their inbox.

Nobody can figure out why, even microsoft support. Exchange is pretty cool and pretty easy to use, but damn some of the troubleshooting is a nightmare.
 
AMD_Gamer said:
I setup an SMTP send connector.

Now if i send an email from my internal mark@homelab.com to my yahoo account what is going on. Does Verizon drop it since it is port 25 coming out?
Click to expand...

Telnet from your exchange server or mail connector to the yahoo server on port 25. You can look online and find the commands. But it's an easy way to tell if port 25 is blocked.
 
athlon1.2 said:
You can also just buy a cheap certificate with the internet fqdn. I have a bunch of domains with 1 or 2 email accounts so its not practical to have a certificate for each host so I used the DNS SRV method to setup autodiscover.

This comes in handy: https://www.testexchangeconnectivity.com/
Click to expand...

Microsoft's test site has saved me when trying to figure out why certain mailboxes would not work with activesync.
 
Verge said:
Telnet from your exchange server or mail connector to the yahoo server on port 25. You can look online and find the commands. But it's an easy way to tell if port 25 is blocked.
Click to expand...

Yahoo is VERY picky as to who is accepts email from. Most dynamic ranges are blocked by default almost without recourse. Getting a hold of their tech support can be a nightmare.
 
AMD_Gamer said:
SBS is the same as far as management goes. you can still administer the Exchange server itself using the Exchange Management Console. But if you want to learn how to prep your domain and schema then install Exchange yourself SBS is no good as it installs everything during the SBS installation.
Click to expand...

but... the exchange install process does that for you.

Unless the process has changed between sbs2003 and sbs2010. The initial install installs the OS. After first boot you are presented with a wizard to setup your SBS server as a domain controller. Then it's up to you to install exchange or not.

thus far i have been able to find a copy of windows server 2008r2 standard for a price i was willing to pay. Exchange on the other hand... well it's about $500 to much for standard.
 
jjandrob said:
but... the exchange install process does that for you.

Unless the process has changed between sbs2003 and sbs2010. The initial install installs the OS. After first boot you are presented with a wizard to setup your SBS server as a domain controller. Then it's up to you to install exchange or not.

thus far i have been able to find a copy of windows server 2008r2 standard for a price i was willing to pay. Exchange on the other hand... well it's about $500 to much for standard.
Click to expand...

Trials/reinstalls is great for home labs and learning.

Also the gold old slmgr -rearm is great ;)
 
jjandrob said:
but... the exchange install process does that for you.

Unless the process has changed between sbs2003 and sbs2010. The initial install installs the OS. After first boot you are presented with a wizard to setup your SBS server as a domain controller. Then it's up to you to install exchange or not.

thus far i have been able to find a copy of windows server 2008r2 standard for a price i was willing to pay. Exchange on the other hand... well it's about $500 to much for standard.
Click to expand...

Dude, technet.
 
jjandrob said:
but... the exchange install process does that for you.
...................
Click to expand...


Not quite. Installing stand alone Exchange in an existing AD was a PITA for me, of course it was Exchange '10 on Win 2008R2 in a 2003 Domain, LOL. There are so mush pre-reqs to do before I even got down to installing Exchange.
With SBS, everything is good to go right off the bat.
Learn Exchange from SBS first.
Then when you're comfortable with that, build a domain from the ground up and play with Exchange '10.

That way you'll know how it should work when it works. By going stand alone Exchange, if you miss something, you'll pull out your hair trying to find out why its not working.
 
Almost all large mail servers will block mail from dynamic IP blocks used by residential iSPs. If you want to send mail you will have to get a smart host/smtp relay and use that. Ive been running my exchange server at home for months on time warner cable like that
 
Last edited:
You must log in or register to reply here.
Back
Top