Problems sending: Windows domain = e-mail domain 1

[soportesinaki]

Dear Sirs,

When our Exchange Server was installed, we configured the windows domain similar to our e-mail domain (managed by an ISP) thinking on a future e-mail migration. Now, when we try to send mails to an external user using our domain, the exchange server sends back an answer telling this address does not exist, because he "thinks" this address is internal.

Any idea to solve this problem?

Thank you for your help.
Regards.

 

[markdmac]

Not totally following you here. Please give some more data.

What is the domain you are sending from? Where does the MX record point for that domain? To what domain are you sending?


I hope you find this post helpful.

Regards,

Mark

 

[soportesinaki]

Our enterprise has a domain hosted by Telefonica (spanish ISP). They provide us Web Hosting and e-mail services. (suppose its called ourdomain.es)

When we installed the new Windows 2003 server, we called the internal domain as the domain hosted by our ISP, ourdomain.es. When somebody out from our office sends an email to ourdomain.es, it reaches Telefonica without problems. But when we try to send the e-mail to one of our external colleagues (also using ourdomain.es), the exchange tries to find this address in the internal address list, and as it cannot find it, it returns an error.

I hope i have explaned it ok this time.

Thank you for your help.

 

[markdmac]

OK, so I think I see your problem here. These External peopel do not access your Exchange server for their mail? Why not?

Give them remote access using OWA or Outlook over HTTP and set them up on the system.

You can't split the users between an external provider and Exchange.

I hope you find this post helpful.

Regards,

Mark

 

[58sniper]

The only time I've seen this work is when the ISP also has POP3 access available.

So, mail going to ourdomain.es would go to your server, but your ISP has POP3 mailboxes at, say, mail.ourdomain.es

Then, in Exchange, under Default SMTP Virtual Server, on the Messages tab, enter mail.ourdomain.es on the last line. Essentially, any mail that can't be resolved to an internal account would get pushed off to the POP3 mail server.

Not the way I would ever recommend it, but I've had to do that a couple of times for some small clients.

Pat Richard, MCSE(2) MCSA:Messaging, CNA(2)

 

[soportesinaki]

Thank you!!!
I've tried your solution and it works fine!!

Thank you very much!!!

Best Regards,
Iñaki

 

[dkediger]

Still, I would encourage a migration like markdmac outlined. Why have a split mail system when everyone can be under the same umbrella?

 

[soportesinaki]

Yes, you are right. We have that migration planed for next week, but we needed to solve this problem meanwhile.

Thank you for your help.