How to configure Exchange 2013 to get and send email on the internet?

I'm a little confused at this point.  I have set up Exchange 2013 on a Windows 2012 Standard installation.  

I have added users to domainname.local and have assigned them their real email addresses username@domainname.org in the Active Directory.  I have created a mailbox for each user on the Exchange 2013 server.

But, I have not seen how to connect Exchange to the internet (domain name and MX records are hosted at GoDaddy).

I have been told that their old server used MAPI Exchange connections and that SMTP and POP were never set up on the old Exchange 2003 (in SBS 2003).  But a Google for MAPI and Exchange has not produced anything that I see as enabling the Exchange server to send and receive email via the internet.

I am also getting an error "an unknown error occurred, error code: 0x80070057" when I try and connect Outlook 2010 to the Exchange 2013 server.

What have I missed?
asciiassasinAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Nick RhodeIT DirectorCommented:
You would have to setup a send and recieve connector.  Create some internal and external DNS records (autodiscover.domain.org, mail.domain.org, etc.)  Is the MX records resolving to the exchange server?  Is the router setup to forward port 443 and 25 to the exchange server.

Send Connector:  http://exchangeserverpro.com/configuring-outbound-mail-flow-in-exchange-server-2013/

Recieve Connector:  http://technet.microsoft.com/en-us/library/jj657447(v=exchg.150).aspx
0
nashim khanExchange AdministratorCommented:
Hi,

Please refer the below link for creating the recive connector.

http://technet.microsoft.com/en-us/library/jj657457(v=exchg.150).aspx

And for the recieve connector follow the @NRhode article.

Regards
NAshim Khan
0
asciiassasinAuthor Commented:
The MX records on the old server seem to be resolving to an external service that cleans the emails of spam and malware and such.  It seems that the emails are being routed through that service before coming into the old 2003 Exchange server.

How would I see the MAPI settings in the current SBS 2003 Exchange server to see just where email is coming in from?

The router is set up to forward RDP, SMTP, IMAP, POP, OWA, MS VPN, OWA S, iPhone, LDAP and DWMRC to the old SBS 2003 server.  

This is the response I got from the person that set up the 2003 Exchange server a few years ago...

I set up the server originally 6-7 years ago, but did not set up the POP or SMTP connectors. We only use native MAPI connections with Exchange. Since then, the only time I have touched the server is to troubleshoot mail coming from our SPAM filter to their Exchange server (2-3 instances). If the POP & SMTP connectors are enabled now on their server, we didn't configure that
.

I'm not sure I understand what you mean by Create some internal and external DNS records (autodiscover.domain.org, mail.domain.org, etc.) .
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Nick RhodeIT DirectorCommented:
Those urls all depend on your urls specified when seting up exchange.  If you setup OWA and exchange for example as the mail.domain.org address for internal and external.  Then you want a DNS record created so the internal systems and records outside resolve properly.

Autodiscover is a default so when you open up outlook (1st time) it searches for autodiscover to automatically populate and pull the account information.  So you would want to setup autodiscover.domain.org (your domain basically) to resolve to the exchange server etc.
0
asciiassasinAuthor Commented:
I had to get the company's 3rd party email washing company to log on and do some setup on the 2013 server.

I asked him to wait while I set up a login so that I could watch what he was doing.  Naturally he didn't.  He went right ahead and changed who-knows-what on the new server.

It works like it should (most of the time - as long as his service has all of the email addresses updated in it).  But, we will be firing him and his very unprofessional company.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
asciiassasinAuthor Commented:
A 3rd party mail washing service needed access to the server and a user with LDAP privileges to configure the external connections to GFI to wash the emails in and out.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.