Re: E-mail woes
- From: "Arthur" <mynewsgroupaccount@xxxxxxxxxxxxxx>
- Date: Fri, 10 Feb 2006 11:47:49 -0000
I expect that Mr X is using a shared web server with a couple of thousand
other web developers. He is likely to have a control panel that adds a
website and the DNS entries to the server farm which takes control of the
DNS. He is right to say that email links will not work in this situation but
he has gone about it the wrong way.
The most sensible approach would have been to setup the web hosting so that
the server farm did not have any email resources or DNS resources for the
domain in question. Then when his web scripts send email to the clients
domain they won't get caught by the local mail servers. Another way to do
this is to allow the Exchange server to relay for the web server that runs
the web scripts and he could use the IP number of the Exchange server as the
SMTP server setting in his web scripts.
There are many ways to achieve this without disrupting the SMTP feed to the
Exchange server but I would put the mail delivery back as it was, change the
A record for WWW to Mr X's web server and let him get educated in sending
email from his web farm.
"Kevin Weilbacher [SBS-MVP]" <kweilbacMVP@xxxxxxx> wrote in message
news:uFb9w3fLGHA.500@xxxxxxxxxxxxxxxxxxxxxxx
To say that Mr X is a complete idiot may be an understatement. No, it does
not make any sense at all. He has caused your client to take two giant
steps backwards. Contracting with a web developer to develop a web site is
one thing, but insisting that you move it and your email to his server is
plain stupid. I have many accounts where their web site is hosted
externally, and we use SBS to handle the mail via SMTP, and not POP3.
--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"
"Andrew M. Saucci, Jr." <spam-only@xxxxxxxxxxxxxxxx> wrote in message
news:%23Dq4BZeLGHA.3104@xxxxxxxxxxxxxxxxxxxxxxx
I just wanted some opinions on e-mail configuration. We had a
client using SBS with his MX pointed directly to his server, and it
worked
fine for years. A few months ago, he contracted with a web developer to
host
his web site. The web developer (who we shall call Mr. X) insisted that
the
e-mail links in the web site would not work unless the DNS was
transferred
to X's DNS machine and POP3 accounts were created. He said he had to have
a
"real" mail server for everything to work correctly. I tried to reason
with
Mr. X and our client, but X insisted that it had to be done his way--
just
pointing www.client.com to X's server wouldn't be sufficient, and it had
to
be POP3. Does this make any sense at all? What might X be trying to do
that
can't be done unless he hosts the e-mail? Ever since Mr. X got involved
we've had all sorts of mysterious e-mail problems there that have taken
lots
of time to troubleshoot, and meanwhile everything was working fine before
that. Besides, with the POP3 Connector, the mail takes as long as 15
minutes
to arrive. (I know about POP Beamer and may still use it there if I have
to.) I really would like to put everything back the way it was-- the way
everyone here seems to think an SBS should be set up-- but I'm going to
need
some solid facts if I'm to have any chance of explaining why X's approach
isn't the only way. Right now, all I have is X claiming that it just has
to
be POP3.
.
- Follow-Ups:
- Re: E-mail woes
- From: Andrew M. Saucci, Jr.
- Re: E-mail woes
- References:
- E-mail woes
- From: Andrew M. Saucci, Jr.
- Re: E-mail woes
- From: Kevin Weilbacher [SBS-MVP]
- E-mail woes
- Prev by Date: RE: An inconsistency was encountered on the requested media
- Next by Date: Re: Folder contents are different when logged in remotely?
- Previous by thread: Re: E-mail woes
- Next by thread: Re: E-mail woes
- Index(es):
Relevant Pages
|
Loading
