On Fri, Aug 02, 2002 at 09:24:45AM +0100, Danny Angus wrote:
> No offence mate, but this..
None taken at your comments, but I do wish you'd have read my
message.
> > Despite that, I have much the same concerns as Chris; I don't
> > want to ask my (potential) users to move their site hosting over to my
> > box, but I know I'm going to have to handle sending mail from my box
> > as if it were coming from the user's site domain.
>
> Does suggest that there are certain fundamentals about email that
> perhaps you ought to learn before entering the shark infested waters
> of spam.
There are plenty of fundamentals about email that I know, and
more yet that I don't. That's why I posted.
> 1/ website and email don't have to be on the same machine for the same
> domain, how do you think people like Yahoo would survive if they did?
> 2/ Mail destination is controled by a DNS record called MX.
Yes, I know domains and I know about MX records. The problem is
not merely my taking over responsibility for all the mail for the
domains in question. That would be straightforward enough. I don't
*want* responsibility for all the mail for the domains in question, I
just want responsibility for a subset of the mail with a minimum of
hassle and arguing with organization's service providers.
One solution is to set up a subdomain of my domain (let's fall it
foo.com), so northcarolinaphotogs.org comes to me and opens up an
account with my service, and I set up a northcarolinaphotogs.foo.com.
Not bad, as such things go, but not good either.
Another solution is to use their ISP's mail server and arrange
with their ISP to have my server be authorized to relay through them,
and then just set the various headers in the outgoing messages to have
northcarolinaphotogs.org. I believe this is generally referred to as
"forging" the headers and is regarded with suspicion. However, more
importantly, there are serious limitations with this approach - bounce
messages end up in the inbox for northcarolinaphotogs.org, not in my
inbox.
Another solution is to take over all of the given domain's mail
concerns, via an MX record, and then just provide all of their mail
needs through my server. As I type this, I'm actually beginning to
reconsider dismissing this, because it doesn't seem like really that
much. I'll have to give it some serious thought. Nevertheless, I'd
prefer not to, and this approach has the same problems I outlined in
my previous message, i.e. hassles with the ISP who hosts that domain
to get them to set up the MX record.
Antoher solution is to set up a subdoman, say
announce.northcarolinaphotogs.org, and have that domain pointed at my
box. I like this because it cleanly separates my responsibilities
from the other mail needs of the domain owner. It also provides a
distinct identity. Yet it maintains continuity with the original
domain. And it gives the domain owner maximum safety - if there's
ever any sort of disagreement with my service, they can simply take
their subdomain back. I can't hold it hostage.
Steven J. Owens
[EMAIL PROTECTED]
"I'm going to make broad, sweeping generalizations and strong,
declarative statements, because otherwise I'll be here all night and
this document will be four times longer and much less fun to read.
Take it all with a grain of salt." - Me
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
