Dave Kitabjian wrote:
> Please pardon my ignorance just for a moment, and permit a question that
> may have a very simple answer...
>
> What is "virtual" about a "virtualdomain"?
>
> We host many domains on a single qmail POP server, and they are all very
> real. Their MX records all point to that server and for all intents and
> purposes, that is "home" for them.
>
> To me, "virtualdomains" are equivalent to, simply, domains. The prepend
> feature of "virtualdomains" is the only mechanism I know of in qmail to
> isolate the user namespace of one domain from each other domain, so that
> there can be a [EMAIL PROTECTED] and a [EMAIL PROTECTED] with no ambiguity
> or contention. That way qmail can handle multiple domains seamlessly in a
> single "assign" file.
>
> Please educate me... :)
Generally, a host machine has a domain of its own. If it serves for other
domains, the concept as been equated to virtual memory technology. That
kind of memory is very real, when swapped in, at least to the process that
is working with it.
So if the domain is different than the host machine, but the host machine
is doing more than just relaying or queueing for the host, such as local
delivery or even address translation and subsequent delivery, then we call
that virtual when the domain name (it doesn't have to just be a different
2nd level; it can be a different 3rd level, or 4th level, etc.) is not the
same as the host machine.
Would you have another more meaningful term to suggest that properly
differentiates between mail addressed to [EMAIL PROTECTED] and mail
addressed to [EMAIL PROTECTED] yet is delivered on "the.host"?
--
Phil Howard | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
phil | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
at | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
ipal | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
dot | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
net | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
