Re: Email set-up
- From: Owen Williams [SBS MVP] <Owen@xxxxxxxxxxxxxxxxxx>
- Date: Fri, 25 Aug 2006 20:57:25 -0400
In article <12A09B28-CE6B-4411-9C60-685FBB206752@xxxxxxxxxxxxx>,
RichinOttawa@xxxxxxxxxxxxxxxxxxxxxxxxx says...
OK, let me comment and ask several questions to start untangling some of
this. I'm sure others - some of whom have probably worked with
situations at least as complex as this - will jump in.
[1] Your concerns about the long internal (blahblah.local) FQDN are
unfounded. Although many people worry about this, in SBS the internal
and public domain names are completely unrelated. Definitely NOT a
problem.
[2] What type of public IP address is provided by the client's broadband
connection - static or dynamic? Both will work, but the setup is
slightly different.
[3] Does the client have control over the public DNS records for
magma.ca and coverme.com - either directly or through a friendly ISP
relationship? The reason I ask is that for Exchange to directly receive
the mail (without the POP3 Connector), the public MX records for one or
both of these needs to be changed to point to the public IP of the SBS.
[4] Will the client continue to receive mail at both domains? And, if
so, are the user names the same for each? For example, if there's a
jack@xxxxxxxx is there also a jack@xxxxxxxxxxx? And is every <user>
@coverme.com currently forwarded to a <user>@magma.ca?
[5] Does the broadband ISP have any prohibitions (technical or
contractual) against the client hosting an e-mail server? For example,
is incoming TCP port 25 being blocked? Or do the Terms of Service
prohibit running an e-mail server?
Don't get discouraged by the many questions. Setting this up with
Exchange may actually be fairly easy. And using Exchange directly
rather than via the POP3 Connector will enable somewhat better SPAM
filtering, among other advantages.
-- Owen Williams (SBS MVP)
Client has two ISP providers. One was for dial-up internet access and was.
commissioned many moons ago when broadband was just a twinkle in Cisco's eye.
So as the story goes they used their dial-up ISP for email using an email
account xyz@xxxxxxxxx Two years ago they got broadband so use their first
provider for their email and use the broadband ISP to route their external
email.
Now in the meantime, they got one of their employee's friend of a friend of
a friend, etc., to set them up with a website and register a domain of
coverme.com. The website never got off the ground (no idea why) but buddy
did register coverme.com. He also created aliases for the employees at the
main office such as jill@xxxxxxxxxxx, jack@xxxxxxxxxxx, etc., which point to
the mailbox at the original ISP provider, xyz@xxxxxxxxx
As many of you are probably thinking, they now have beaucoup de problems
with spam at xyz@xxxxxxxxx Sooooo....to make an excruciating long story
short (which now seems impossible), I recently configured a pre-installed SBS
2003 installation for them. My first priority is to clean up the email
problems.
I had originally considered using POP3 connector but this won't be much help
if mail (spam) keeps getting jammed up at the ISP (magma.ca). After reading
these and other forums for what seems like an eternity I am thinking of
letting Exchange do the whole shebang. I am the first to say I am no expert
and have been out of the tech game for a few years, so I am a little
reluctant to get into playing with DNS forward/rear lookups, and the such.
Do any of you think that this should be fairly easy to set up? Is this a bad
idea to want Exchange to do all the heavy lifting? The organization here is
not very big with about 10 employees and one SBS server acting as kingpin,
Exchange Server, DNS, etc.
One issue I see immediately is a problem with the FQDN, which unfortunately
is very long... i.e. the SBS server's name is
main-office.covermesoutherninc.local, and you will recall that the registered
domain name for the company is coverme.com. Is this a big issue? I am
struggling with how to resolve the difference in naming between the public
domain name and the ridiculously long local name or does it really matter.
Any help or advice would be greatly appreciated. I apologize in advance for
my ignorance with these issues but this is no longer my day job, but it pays
a helluva lot better!
- Follow-Ups:
- Re: Email set-up
- From: Rich in Ottawa
- Re: Email set-up
- Prev by Date: Re: companyweb and default site stopped, won't start
- Next by Date: Re: Outlook via Internet with different internal and external domains
- Previous by thread: Re: companyweb and default site stopped, won't start
- Next by thread: Re: Email set-up
- Index(es):
Relevant Pages
|
