Under certain circumstances, when sending mail, the mail will appear in the local spool directory as
Deferred: Operation timed out with otherhost.domain while observably there has no timeout happened: the sendmail has returned just immediately from the failing delivery action. It is said in the documentation and on the net, that this problem comes from a broken or bad configured nameserver, and the sendmail resolver option "WorkAroundBrokenAAAA" is just a workaround and the correct solution would be to fix the broken nameservers. While it is true that the said sendmail-option solves the problem (if sendmail is new enough to understand it), I could nowhere find information on how to fix the bug in the nameserver - that is, in the nameserver that is packaged with FreeBSD 4.4 or 4.7. Input is utterly appreciated; while the sendmail workaround is available on FreeBSD 4.7, it was not yet implemented on 4.4, and I do not like to upgrade all of the machines (at least not for a mere Workaround). The nameservers are vanilla as in the distribution: disp# named -v named 8.2.4-REL Sun Dec 2 00:47:20 GMT 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/usr.sbin/named gate# named -v named 8.3.3-REL Wed Dec 25 07:53:05 CET 2002 [EMAIL PROTECTED]:/u/4-STABLE/obj/u/4-STABLE/src/usr.sbin/named Please, if anybody knows how to fix this nameserver; please tell me! Attached is a log of what is happening actually, there are two systems "disp" and "gate" involved. "gate" is the mailhub, and "disp" wants to send a mail to it: Hostname: disp (127.0.0.1) gate (127.0.0.1) OS: FreeBSD 4.4 FreeBSD 4.7 Interface: disp-e (192.168.98.5) gate-e (192.168.98.2) dynIP outbound Nameserver: LAN Primary and LAN Slave forwarder to "gate" named.root file is here The hostnames are associated to the lo0 Interfaces (and mentioned in /etc/hosts), they have MX pointing to their respective LAN interfaces. "disp" has these nameservice-relevant sendmail.mc options: FEATURE(relay_based_on_MX) FEATURE(`nocanonify', `canonify_hosts') FEATURE(`accept_unresolvable_domains') define(`SMART_HOST', `gate') BTW: As soon as the outbound internet connection is available and we have root nameservers accessible, the problem goes away. # mail pmc@dyn Subject: test test ^D # sendmail -d1-10.9 -q getla: 0 getauthinfo: root@localhost ;; res_query(5.98.168.192.in-addr.arpa, 1, 12) ;; res_mkquery(0, 5.98.168.192.in-addr.arpa, 1, 12) ;; res_send() ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59759 ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; 5.98.168.192.in-addr.arpa, type = PTR, class = IN To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message