Re: Allow exchange (that used to use domain) to send to outside em
- From: Rob B <RobB@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 31 May 2008 10:57:00 -0700
Realistically, I have no need for the exchange server to have a public domain
- I just used it in effort to get the old settings off.
mpvaluations.com is the old domain and mprealestate1.com is the new one.
mprealestate1.com's mx record doesn't point to the sbs, but thats ok. I only
need to send out mail from the server. And the mail ONLY has to go to
mpvaluations.com email accounts.
Hope that helps,
Rob
"Larry Struckmeyer [SBS-MVP]" wrote:
It seems I still don't have a grasp of your current setup. Are there now.
two domains that your SBS users should be able to use, or is there:
1. Old Domain, that is now either web mail or pop mail
and
2. NewDomain, that is a valid FQDN with public DNS settings and that users
can send and receive internet email.
If this is the case, then it might be useful for you to post the email names
for both domains so that we can check them in the public records. Or, you
can do this yourself at:
www.dnsstuff.com or
www.mxtoolbox.com
if you post them, munge the names as in:
d*o*m*a*i*n*dot*com.
--
Larry
"Rob B" <RobB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3724B4FE-D187-4074-8EA9-A5D8726344C2@xxxxxxxxxxxxxxxx
I have run the CEICW with my new settings. I initially had everything with
a
SMTP smarthost, and have since tried disabling that. Now I do not get an
error email sent to the account, but I also don't get anything in the
appropriate mailbox.
Do you think this problem is repairable, or is a reinstall going to be
necessary?
Thanks so much for your help,
Rob
"Larry Struckmeyer [SBS-MVP]" wrote:
Well, you should not be altering the DNS settings on your SBS. The
CEICW
makes all those settings for you.
Have you run the CEICW with all the IP settings and your new non-public,
no
mx record domain name?
--
Larry
"Rob B" <RobB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A9902DA2-0D12-47AE-9C6F-3058385654B2@xxxxxxxxxxxxxxxx
Exchange works fine locally still, but you got the rest right. On the
exchange server, I can send an email out to any domain (as far as I
know)
EXCEPT the domain that used to exist on the sbs.
The name of the domain controller has not been changed. My changes
took
place in:
1)The SMTP of the email name that is now on a remote server.
2)The local DNS record (I deleted the domain.com record altogether)
3)I added a new .com for email, which took place but doesn't seem to
affect
anything.
Appreciate the help so far,
Rob
"Larry Struckmeyer [SBS-MVP]" wrote:
Hi Rob:
It is not clear from your post what you did, exactly. Let's see if I
have
it:
1. You changed from hosting clientdomain.com on your exchange server
to
hosting clientdomain.com on a remote hosting service.
2. You changed the MX records for clientdomain.com, and all of that
is
working well. The uses get their mail by the remote method.
3. You changed the default email or disabled the exchange services or
in
some other way stopped using exchange locally.
4. You receive faxes with SBS fax service and would like the faxes to
show
up in one or more users email at the clientdomain.com that is hosted
remotely.
5. When that did not work, you "changed" the SBS somehow. How? By
flattening and reinstalling or how? If you simply changed the name of
the
domain controller, I am afraid you broke the SBS and will have to
flatten
and reinstall.
6. So, if steps 1 - 4 are accurate, and please correct me if they are
not,
what about step 5? What exactly have you done to your customers SBS?
--
Larry
"Rob B" <Rob B@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6ECB7B8F-EF5F-4906-8E3C-4F54506F5B83@xxxxxxxxxxxxxxxx
I have a .com name that used to be used by my sbs for email. Now my
client
wants to use an outside email company, and thus the domain was
moved.
My problem is that the client still wants to use the SBS fax to
feature. Whenever I send an email to the godaddy
account@xxxxxxxxxx,
it
tells me that it can't find the host.
I have since moved the SBS to a new domain, and attempted to remove
all
traces of the old one. At the very least, could someone help me
compile a
list of places that a domain leaves it mark (or however else I would
fix
this).
Thanks!
Rob
- Follow-Ups:
- References:
- Re: Allow exchange (that used to use domain) to send to outside email
- From: Larry Struckmeyer [SBS-MVP]
- Re: Allow exchange (that used to use domain) to send to outside em
- From: Rob B
- Re: Allow exchange (that used to use domain) to send to outside em
- From: Larry Struckmeyer [SBS-MVP]
- Re: Allow exchange (that used to use domain) to send to outside em
- From: Rob B
- Re: Allow exchange (that used to use domain) to send to outside em
- From: Larry Struckmeyer [SBS-MVP]
- Re: Allow exchange (that used to use domain) to send to outside email
- Prev by Date: Re: Domain Name change in SBS 2003
- Next by Date: One user can't send externally, gets 5.7.1
- Previous by thread: Re: Allow exchange (that used to use domain) to send to outside em
- Next by thread: Re: Allow exchange (that used to use domain) to send to outside em
- Index(es):
Relevant Pages
|
