Bill Deegan writes: >> > I get the following when trying to send email through my courier mail server: >> > >> > Mar 21 11:46:09 mailbox courieresmtpd: started,ip=[::ffff:192.168.168.101] >> > Mar 21 11:46:09 mailbox courieresmtpd: >error,relay=::ffff:192.168.168.101,from=<[EMAIL PROTECTED]>: 517-Domain does not >> exist: >> > hq.knowmadic.com. >> > Mar 21 11:46:09 mailbox courieresmtpd: >error,relay=::ffff:192.168.168.101,from=<[EMAIL PROTECTED]>: 517 Invalid domain, > see >> > <URL:ftp://ftp.isi.edu/in-notes/rfc1035.txt> >> > >> > >> > >From a previous message in the list I saw the sugguestion to check the mx >records: >> > [root@mailbox]# dig hq.knowmadic.com mx >> > >> > ; <<>> DiG 9.2.0 <<>> hq.knowmadic.com mx >> > ;; global options: printcmd >> > ;; Got answer: >> > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4038 >> > ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1 >> > >> > ;; QUESTION SECTION: >> > ;hq.knowmadic.com. IN MX >> > >> > ;; ANSWER SECTION: >> > hq.knowmadic.com. 86400 IN MX 0 >mailbox.hq.knowmadic.com.hq.knowmadic.com. >> > >> > ;; AUTHORITY SECTION: >> > hq.knowmadic.com. 86400 IN NS mailbox.hq.knowmadic.com. >> > >> > ;; ADDITIONAL SECTION: >> > mailbox.hq.knowmadic.com. 86400 IN A 192.168.168.71 >> > >> > ;; Query time: 1 msec >> > ;; SERVER: 127.0.0.1#53(127.0.0.1) >> > ;; WHEN: Thu Mar 21 11:35:36 2002 >> > ;; MSG SIZE rcvd: 113 >> > >> > [root@mailbox]# testmxlookup hq.knowmadic.com >> > Hard error. >> > >> > >> > How come the testmxlookup fails, but dig finds the mx record?
Dig finds a completely fucked up MX record, and obediently prints it. testmxlookup ignores all fucked up MX records. -- Sam _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
