https://community.hpe.com/t5/operating-system-hp-ux/transient-parse-error-self-resolved-after-nslookup/m-p/3981609#M754152 Had a message in the queue since April 10, every time it tried to deliver, it logged:<BR /><BR />Apr 15 13:31:59 hpr sendmail[27430]: QAA27597: to=RECIPIENT@DOMAIN.COM, delay=4+20:35:18, mailer=relay, relay=vega.ourdomain.com, stat=Transient parse error -- message queued for future delivery<BR /><BR />All other mail was working fine. I read some other threads suggesting DNS issues, so I did some checking with nslookup on the host. Everything looked fine. The only weird thing was, if I checked for mx records with the domain name as DOMAIN.COM (all uppercase), the MX servers were listed in lowercase, and if I checked for domain.com (all lowercase), the MX servers were given in uppercase.<BR /><BR />Soon after doing those nslookups, the message was delivered.<BR /><BR />What happened here? Do I need a patch?<BR /><BR />HP-UX 11.11 if it matters. TIA. Sun, 15 Apr 2007 13:43:14 GMT Carl Houseman 2007-04-15T13:43:14Z https://community.hpe.com/t5/operating-system-hp-ux/transient-parse-error-self-resolved-after-nslookup/m-p/3981609#M754152 Had a message in the queue since April 10, every time it tried to deliver, it logged:<BR /><BR />Apr 15 13:31:59 hpr sendmail[27430]: QAA27597: to=RECIPIENT@DOMAIN.COM, delay=4+20:35:18, mailer=relay, relay=vega.ourdomain.com, stat=Transient parse error -- message queued for future delivery<BR /><BR />All other mail was working fine. I read some other threads suggesting DNS issues, so I did some checking with nslookup on the host. Everything looked fine. The only weird thing was, if I checked for mx records with the domain name as DOMAIN.COM (all uppercase), the MX servers were listed in lowercase, and if I checked for domain.com (all lowercase), the MX servers were given in uppercase.<BR /><BR />Soon after doing those nslookups, the message was delivered.<BR /><BR />What happened here? Do I need a patch?<BR /><BR />HP-UX 11.11 if it matters. TIA. Sun, 15 Apr 2007 13:43:14 GMT https://community.hpe.com/t5/operating-system-hp-ux/transient-parse-error-self-resolved-after-nslookup/m-p/3981609#M754152 Carl Houseman 2007-04-15T13:43:14Z https://community.hpe.com/t5/operating-system-hp-ux/transient-parse-error-self-resolved-after-nslookup/m-p/3981610#M754153 <!--!*#-->Some further info... it seems only the first nslookup that succeeded returned the MX servers in uppercase, and it looked like this:<BR /><BR /># nslookup -type=MX hobbittravel.com<BR />Using /etc/hosts on: hpr<BR />looking up FILES<BR />Trying DNS<BR />Non-authoritative answer:<BR />domain.com preference = 10, mail exchanger = SMTP1.HOST1.DOMAIN.com<BR />domain.com preference = 20, mail exchanger = SMTP1.HOST2.DOMAIN.com<BR /><BR />Thereafter subsequent nslookups with domain in uppercase have returned:<BR /><BR /># nslookup -type=MX DOMAIN.COM<BR />Using /etc/hosts on: hpr<BR />looking up FILES<BR />Trying DNS<BR />Non-authoritative answer:<BR />DOMAIN.COM preference = 10, mail exchanger = smtp1.host1.domain.COM<BR />DOMAIN.COM preference = 20, mail exchanger = smtp1.host2.domain.COM<BR /><BR />Authoritative answers can be found from:<BR />smtp1.host1.domain.COM internet address = x.x.x.x<BR />smtp1.host2.domain.COM internet address = 204.11.209.99<BR /><BR />If I nslookup domain.com (all lowercase) the MX hosts are returned as smtp1.host1.domain.com instead of smtp1.host1.domain.COM Sun, 15 Apr 2007 13:55:03 GMT https://community.hpe.com/t5/operating-system-hp-ux/transient-parse-error-self-resolved-after-nslookup/m-p/3981610#M754153 Carl Houseman 2007-04-15T13:55:03Z