| Author |
Message |
Jonas Haggren
Guest
|
 Posted:
Thu Jan 13, 2005 5:22 pm Post subject:
Domain glue problem.. |
|
|
We have had a e-mail domain at our server, But we have now removed it from
us, But then people from inhouse try to mail to this domain at their new
server the mails don't go through, our exchange server says that the e-mail
account does not exist (it thinks it stills own the e-mail domain, but it
does not).
We have ofcourse removed this e-mail domain from the Recipient Policies, I
have also deleted all the e-mail addresses on all users who had this e-mail
domain.
Nothing works, Our Exchange still thinks it own this domain.
How do i do to solve this??
--
..:: Jonas Haggren ::.
System Manager
..:: Evolver Data ::.
0709-957548,
|
|
| Back to top |
|
 |
Lanwench [MVP - Exchange]
Guest
|
| Posted:
Thu Jan 13, 2005 10:39 pm Post subject:
Re: Domain glue problem.. |
|
|
Jonas Haggren wrote:
| Quote: | We have had a e-mail domain at our server, But we have now removed it
from us, But then people from inhouse try to mail to this domain at
their new server the mails don't go through, our exchange server says
that the e-mail account does not exist (it thinks it stills own the
e-mail domain, but it does not).
We have ofcourse removed this e-mail domain from the Recipient
Policies, I have also deleted all the e-mail addresses on all users
who had this e-mail domain.
Nothing works, Our Exchange still thinks it own this domain.
How do i do to solve this??
|
Was your AD domain originally set up with the same public domain name you're
trying to send to?
What exact errors do you get?
Had you ever set up anything special in your internal DNS for this domain? |
|
| Back to top |
|
|
Jonas Haggren
Guest
|
| Posted:
Fri Jan 14, 2005 4:38 pm Post subject:
Re: Domain glue problem.. |
|
|
Was your AD domain originally set up with the same public domain name you're
trying to send to?
- No. This thas a additional, "just a extra e-mail" domain, that i added
before under recipient policies and now removed from it
What exact errors do you get?
-
xxxx@xxxx.xx den 2005-01-12 14:32
The e-mail account does not exist at the organization this message was sent
to. Check the e-mail address, or contact the recipient directly to find out
the correct address.
<xxxx.xxxx.xx #5.1.1>
Had you ever set up anything special in your internal DNS for this domain?
- we have had this domain on our internal DNS, But now it is removed, Have
cleared the cache, and then i do a nslookup from the dns server it reports
the correct dns to the new servers.
--
..:: Jonas Haggren ::.
System Manager
"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> skrev i
meddelandet news:%23w7LADZ%23EHA.2596@tk2msftngp13.phx.gbl...
| Quote: | Jonas Haggren wrote:
We have had a e-mail domain at our server, But we have now removed it
from us, But then people from inhouse try to mail to this domain at
their new server the mails don't go through, our exchange server says
that the e-mail account does not exist (it thinks it stills own the
e-mail domain, but it does not).
We have ofcourse removed this e-mail domain from the Recipient
Policies, I have also deleted all the e-mail addresses on all users
who had this e-mail domain.
Nothing works, Our Exchange still thinks it own this domain.
How do i do to solve this??
Was your AD domain originally set up with the same public domain name
you're
trying to send to?
What exact errors do you get?
Had you ever set up anything special in your internal DNS for this domain?
|
|
|
| Back to top |
|
|
Lanwench [MVP - Exchange]
Guest
|
| Posted:
Fri Jan 14, 2005 8:27 pm Post subject:
Re: Domain glue problem.. |
|
|
Jonas Haggren wrote:
| Quote: | Was your AD domain originally set up with the same public domain name
you're trying to send to?
- No. This thas a additional, "just a extra e-mail" domain, that
i added before under recipient policies and now removed from it
What exact errors do you get?
-
xxxx@xxxx.xx den 2005-01-12 14:32
The e-mail account does not exist at the organization this message
was sent to. Check the e-mail address, or contact the recipient
directly to find out the correct address.
xxxx.xxxx.xx #5.1.1
Had you ever set up anything special in your internal DNS for this
domain?
- we have had this domain on our internal DNS, But now it is removed,
Have cleared the cache, and then i do a nslookup from the dns server
it reports the correct dns to the new servers.
|
Double check all your recipient policies.
Have someone on that domain e-mail you and see if you can reply.
| Quote: |
"Lanwench [MVP - Exchange]"
lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> skrev i
meddelandet news:%23w7LADZ%23EHA.2596@tk2msftngp13.phx.gbl...
Jonas Haggren wrote:
We have had a e-mail domain at our server, But we have now removed
it from us, But then people from inhouse try to mail to this domain
at their new server the mails don't go through, our exchange server
says that the e-mail account does not exist (it thinks it stills
own the e-mail domain, but it does not).
We have ofcourse removed this e-mail domain from the Recipient
Policies, I have also deleted all the e-mail addresses on all users
who had this e-mail domain.
Nothing works, Our Exchange still thinks it own this domain.
How do i do to solve this??
Was your AD domain originally set up with the same public domain name
you're
trying to send to?
What exact errors do you get?
Had you ever set up anything special in your internal DNS for this
domain? |
|
|
| Back to top |
|
|
Jonas Haggren
Guest
|
| Posted:
Thu Jan 20, 2005 11:56 am Post subject:
Re: Domain glue problem.. |
|
|
I have checked all the recipient policys, this domain is not mentioned
anywhere.
I can't reply on any mails from this domain, everyone get stuck on the
exchange server, as it thinks its own the domain..
/Jonas
"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> skrev i
meddelandet news:eN6nvBl%23EHA.2584@TK2MSFTNGP09.phx.gbl...
| Quote: | Jonas Haggren wrote:
Was your AD domain originally set up with the same public domain name
you're trying to send to?
- No. This thas a additional, "just a extra e-mail" domain, that
i added before under recipient policies and now removed from it
What exact errors do you get?
-
xxxx@xxxx.xx den 2005-01-12 14:32
The e-mail account does not exist at the organization this message
was sent to. Check the e-mail address, or contact the recipient
directly to find out the correct address.
xxxx.xxxx.xx #5.1.1
Had you ever set up anything special in your internal DNS for this
domain?
- we have had this domain on our internal DNS, But now it is removed,
Have cleared the cache, and then i do a nslookup from the dns server
it reports the correct dns to the new servers.
Double check all your recipient policies.
Have someone on that domain e-mail you and see if you can reply.
"Lanwench [MVP - Exchange]"
lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> skrev i
meddelandet news:%23w7LADZ%23EHA.2596@tk2msftngp13.phx.gbl...
Jonas Haggren wrote:
We have had a e-mail domain at our server, But we have now removed
it from us, But then people from inhouse try to mail to this domain
at their new server the mails don't go through, our exchange server
says that the e-mail account does not exist (it thinks it stills
own the e-mail domain, but it does not).
We have ofcourse removed this e-mail domain from the Recipient
Policies, I have also deleted all the e-mail addresses on all users
who had this e-mail domain.
Nothing works, Our Exchange still thinks it own this domain.
How do i do to solve this??
Was your AD domain originally set up with the same public domain name
you're
trying to send to?
What exact errors do you get?
Had you ever set up anything special in your internal DNS for this
domain?
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in