I see two related problems with your DNS setup:
dan> dns_getcanonname: trying m20.example.org. (A)
dan> ;; res_querydomain(m20.example.org, , 1, 1)
dan> ;; res_query(m20.example.org., 1, 1)
dan> ;; res_mkquery(0, m20.example.org., 1, 1)
dan> ;; res_send()
dan> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26787
dan> ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
dan> ;; m20.example.org, type = A, class = IN
dan> ;; Querying server (# 1) address = 127.0.0.1
dan> ;; got answer:
dan> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26787
dan> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL:
dan> 1
dan> ;; m20.example.org, type = A, class = IN
dan> m20.example.org. 1M IN A 216.187.106.227
dan> example.org. 1M IN NS xeon.example.org.org.
^^^^^^^^^^^^^^^^^^^^^
dan> xeon.example.org.org. 5S IN A 127.0.0.1
^^^^^^^^^^^^^^^^^^^^^
example.org's DNS zone has a mistake if it has an NS record pointing to a
bogus hostname like that (and what's worse the bogus hostname resolves).
dan> dns_getcanonname: trying localhost.example.org (AAAA)
dan> ;; res_querydomain(localhost, example.org, 1, 28)
...
dan> [EMAIL PROTECTED] Connecting to xeon.example.org. via relay...
localhost.example.org appears to map to xeon.example.org, perhaps via
/etc/hosts?
My first suggestion would be to fix your DNS zone as mentioned above.
Then, try the test again with more debugging:
echo 'hi there' | /usr/sbin/sendmail -v -d8.8,16.10,61.11 [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
