Windows

General discussion

Gravatar
Locked

Exchange Server Email Issue

By infosystems ·
I had someone set up Exchange server on my Windows 2000 network. We only have dial up access for mail because we are out in the sticks! Any way, we have an ISP hosting our email services. We have a number of remote users that have our domain name email addresses, ie
someone@ourcompany.com. We cannot email them from the main office because the message is undeliverable and says that the email account does not exist at the organization this message was sent to. In other words the exchange server is looking for that someone@ourcompany.com email address here at our local server and can't find it so says it doesn't exist. Is there anyone that knows how I can fix this problem. I hope I have explained it okay.

Thanks

This conversation is currently closed to new comments.

17 total posts (Page 1 of 2)   01 | 02   Next
+ Follow this Discussion ·
| Thread display: Collapse - | Expand +

All Comments

gravatar
Collapse -

by sgt_shultz In reply to Exchange Server Email Iss ...

could the problem be not in exchange server but in the clients? what do you have smtp server setting in your mail clients? it needs to be set to the ISP's smtp server, not your exchange server...

gravatar
Collapse -

by infosystems In reply to

Poster rated this answer.

gravatar
Collapse -

by CG IT In reply to Exchange Server Email Iss ...

What appears to be happening is that someone send email to <yourdomain>.com and that mail server then send out a request to the Internet [e.g.public Internet Name Servers] asking "hey, anyone know "WhoIs" <yourdomain>.com, I've got mail for them"? No one answers so your email goes into email limbo [which is just a NDR or looping send request by the sending email server]. This happens when no MX record is available to name servers around the internet providing Name to IP address resolution.

So, since you use your ISP for email service, that's where you address mail to, even remote users. you can configure Exchange to download email to your exchange server at certain intervals and also send mail the same way. If you want to host your own email service [with only a dial up internet connection] using your own FQDN, and DNS service, that's a different story.

gravatar
Collapse -

by CG IT In reply to

I'll have to assume that your ISP email service is a POP3 service where you can download email from them via your installed Exchange server. Mail sent to your users [and remote users]need to address it to your ISP POP3 mail service you have. Then, if the guy/gal who installed exchange did so with that in mind, your exchange server will periodically download email from your ISP and make it available to your users via the intranet. Remote users then log in remotely and retrieve their mail from your Exchange server.

gravatar
Collapse -

by CG IT In reply to

There are a couple of ways to accomplish what you want to do. One way is to make remote users email address user@<remote>.<yourdomain>.com or have your ISP create a MX pointer record for your remote users that will deliver mail from your intranet Exchange server upload to the ISP mailboxes. The MX pointer record will have each remote user's email address [remoteuser@yourdomain.com]and point it to the ISP mail service. Remoteusers@yourdomain.com goes to the ISP mailboxes and any other user@yourdomain.com goes to your Exchange service. Either way you'll have to work with your ISP as they receive and send email for your domain [your exchange server does nothing more than receive Internet mail from your ISP and make that mail available to your local intranet users and send internet mail from your intranet to your ISP for delivery.

gravatar
Collapse -

by CG IT In reply to

Answer # 4 is correct in stating that your ISP DNS [hense their mail server] is authoritative for your domain name. Your exchange server on your lan is nothing more than a back end mail server. It's far easier for your ISP to make a change than you in regards to MX records and user mail addresses for <yourdomain.com>. If at some time you wish to host your own Email, then what answer # 4 states is clearly your only choice [which a migration to Windows 2003 Small Business Server can resolve as it automatically assigns a .local extenstion for your LAN network].

gravatar
Collapse -

by CG IT In reply to

ooops change that from answer # 4 to Answer # 5.

gravatar
Collapse -

by infosystems In reply to

Poster rated this answer.

gravatar
Collapse -

by infosystems In reply to Exchange Server Email Iss ...

I received two answers but I don't think I've explained the issue properly. I will try to clarify this problem.

The email accounts are looked after by an isp but we use our domain name. For example: Our domain name is: ourcompany.com our email addresses are someone@ourcompany.com, etc. Our server domain is ourcompany.com. Our mail is served by our isp but the pop and smtp are mail.ourcompany.com. The staff that are not in the same building as the servers do not have remote access to the servers because our telephone line cannot handle the incoming calls .. the highest rate we can get is 26400 bps!! Any way so when i email someone in another location that has the ourcompany.com email address, it comes back because the exchange server does not recognize that email account because it is not set up on the exchange server. The reason it isn't set up on the exchange server is that that person does not access the exchange server for their mail, they access the isp that holds our domain name and serves our email. Does that make sense? I hope so. So I need to know how I can configure our exchange server or the clients that are not in this building so that I can email them.

Thanks

HELP!

gravatar
Collapse -

by hitchcock4 In reply to Exchange Server Email Iss ...

Try this: on the Exchange server, open the Active Directory Users and Computers MMC.
Find one of the users that is having problems RECEIVING e-mail. On the Properties sheet for that user, click on the "E-mail Addresses" tab, and look to see how many SMTP addresses that person has.
If they have more than 1, try sending to the primary address. You should be able to send to the primary address.
I have seen this issue with 1 remote user, and have no explanation for it.

Back to Windows Forum
17 total posts (Page 1 of 2)   01 | 02   Next

Start or search

Related Discussions

Related Forums