On Wed, 21 Jun 2000, Brian Ashe wrote:
>Hi Glen,
>
>I think you may have DNS problems, not sendmail problems.
Not being a sendmail expert, how would that cause the To: field to be
rewritten from [EMAIL PROTECTED] to [EMAIL PROTECTED]? Where would we
look and how would we fix it?
>Things to check...
I don't have access to the DNS machine, but "#2" below may be the problem.
>1) Are all MX records set up properly? i.e. pointing to valid hosts
>2) Are all mail server hosts "A" records and NOT "CNAME" records? It can
>work with CNAMEs but is strongly recommended against.
We're using HTTP 1.1 protocols for our virtual domains - 1 IP address runs
everything. If I understand correctly the DNS records are wildcarded to
allow Apache to run subdomains of each virtual domain. I host
Wesleyan.Net for my denomination, and this allows me to set up church
sites with http://roslynpark.wesleyan.net. Works quite slick in Apache,
but Sendmail appears to be choking on it.
BTW, I don't know the diff between "A" records and "CNAME" records.
Is there a tutorial somewhere for how to set it up for CNAMEs?
>3) Is the host.sub.domain.com that handles MX for that subdomain set up
>properly.
>4) Is the reverse mapping of the domain/subdomain set up properly to allow
>sendmail to reverse it.
Since this is HTTP 1.1 compliant reverse lookup doesn't show the same
domain:
$ socket.cgi edwards.christianfamilies.net
edwards.christianfamilies.net -> 216.254.53.37
$ socket.cgi 216.254.53.37
216.254.53.37 -> brianten-1.dsl.speakeasy.net
Glen
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.