Setting Up Email in Exchange SBS 2003
Posted on 2012-03-16
We just took over a client from another IT company and are trying to set up Exchange so they can use shared calendars, etc. as well as for their email. Unfortunately, while we've been able to set things up so the users can connect to their Exchange Mailboxes and even access OWA internally (using hostname/exchange) and externally (using ipaddress/exchange), we are unable to have them send or receive internet email. This question will cover the receiving of emails. I'll probably be posting one addressng the sending of emails later.
Before I go any further, I do want to say that I am only able to remote into the server as well as use OWA to access a test user/mailbox we've setup. This is so we don't interfere with their current operations until we get this figured out. Our local email is email@example.com and POP3 email is firstname.lastname@example.org
The first thing we tried was to go through CEICW as we've seen on so many different articles and sites. That really has not helped as the we're really unsure of what values to select and enter.
As a start, and I'm sure you'll have a ton of questions for us, here is their basic setup:
- They have a static ip address
- They have a DSL connection to the internet
- There's a SonicWall between the DSL Modem/Router and the server with rules set up allowing access on ports 25, 110, 443
- We have one ethernet connection on the server
- Their company email is currently accessed using POP3 and SMTP with nothing special (Ports 25, 110, no extra security) with mail servers being mail.companyname.com
In starting with the wizard, this is how far we were able to go:
- Connection Type: Broadband
- Broadband Connection: My server uses a local router device with an IP address
- Router Connection: Preferred DNS servers - 188.8.131.52 and 184.108.40.206, Local IP address of router - 192.168.1.1 (address of SonicWall)
- Web Service Configuration: Allow Access to only the following website services - OWA, Remote Web Workplace, Outlook Mobil Access (they have iPhones, BlackBerries, Droids, etc.) and My Server uses a single network connection is checked
- Web Server Certificate: Do not change current webserver certificate is checked
- Internet E-mail: Enable Internet e-mail
- E-Mail Delivery Method: Forward all e-mail to e-mail server at your ISP is selected and the mail server is mail.companyname.com (note: this is the mail server of their POP3 e-mail as associated with their webhosting company, not the ISP, is that correct?)
- E-Mail Retrieval: Use Microsoft Connector for POP3 Mailboxes is checked, Use Exchange is checked with E-mail is held at my ISP until my server sends a signal is selected and mail.companyname.com is entered for the server name. Also, TURN after authentication is selected
- TURN Authentication Information: username: email@example.com (as specified above), Password: password, Use SSL is NOT checked
- E-Mail Domain Name: companyname.com
- POP3 Mailbox Accounts: we added our test one - Email Server: mail.companyname.com, Port: 110, Username: firstname.lastname@example.org, Password: password, Mailbox Type: User Mailbox, Exchange User: testuser
-Mail Schedule: Use the following schedule: Email Frequency Every 15 Minutes
- Remove Email Attachments: Unchecked allow Exchange to remove attachments
Hopefully, something's wrong somewhere there that would explain what's going on, but we're real confused.
We've turned on the highest level of messaging in the POP3 Connection Manager, and we can see the connector successfully logged on and received the email and deleted it from the mail server. However, an informational message later (Event ID 1049) says the message was routed to <email@example.com> by an indivdual mailbox mapping. Is that right? Shouldn't this have routed to <firstname.lastname@example.org>?
Also, the thread of messages ends with EventID 340, MSExchangeTransport which says the Exchange MTA is disabled and that the message can't be delivered. We restarted the service, but still getting the same error.
Any help would be greatly appreciated and I'll be checking in often to look for posts and answer questions. Thanks so much.