- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Transient parse error - self-resolved after nslook...
Operating System - HP-UX
1752565
Members
5226
Online
108788
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2007 06:43 AM
04-15-2007 06:43 AM
Transient parse error - self-resolved after nslookup?
Had a message in the queue since April 10, every time it tried to deliver, it logged:
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
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.
Soon after doing those nslookups, the message was delivered.
What happened here? Do I need a patch?
HP-UX 11.11 if it matters. TIA.
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
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.
Soon after doing those nslookups, the message was delivered.
What happened here? Do I need a patch?
HP-UX 11.11 if it matters. TIA.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2007 06:55 AM
04-15-2007 06:55 AM
Re: Transient parse error - self-resolved after nslookup?
Some further info... it seems only the first nslookup that succeeded returned the MX servers in uppercase, and it looked like this:
# nslookup -type=MX hobbittravel.com
Using /etc/hosts on: hpr
looking up FILES
Trying DNS
Non-authoritative answer:
domain.com preference = 10, mail exchanger = SMTP1.HOST1.DOMAIN.com
domain.com preference = 20, mail exchanger = SMTP1.HOST2.DOMAIN.com
Thereafter subsequent nslookups with domain in uppercase have returned:
# nslookup -type=MX DOMAIN.COM
Using /etc/hosts on: hpr
looking up FILES
Trying DNS
Non-authoritative answer:
DOMAIN.COM preference = 10, mail exchanger = smtp1.host1.domain.COM
DOMAIN.COM preference = 20, mail exchanger = smtp1.host2.domain.COM
Authoritative answers can be found from:
smtp1.host1.domain.COM internet address = x.x.x.x
smtp1.host2.domain.COM internet address = 204.11.209.99
If I nslookup domain.com (all lowercase) the MX hosts are returned as smtp1.host1.domain.com instead of smtp1.host1.domain.COM
# nslookup -type=MX hobbittravel.com
Using /etc/hosts on: hpr
looking up FILES
Trying DNS
Non-authoritative answer:
domain.com preference = 10, mail exchanger = SMTP1.HOST1.DOMAIN.com
domain.com preference = 20, mail exchanger = SMTP1.HOST2.DOMAIN.com
Thereafter subsequent nslookups with domain in uppercase have returned:
# nslookup -type=MX DOMAIN.COM
Using /etc/hosts on: hpr
looking up FILES
Trying DNS
Non-authoritative answer:
DOMAIN.COM preference = 10, mail exchanger = smtp1.host1.domain.COM
DOMAIN.COM preference = 20, mail exchanger = smtp1.host2.domain.COM
Authoritative answers can be found from:
smtp1.host1.domain.COM internet address = x.x.x.x
smtp1.host2.domain.COM internet address = 204.11.209.99
If I nslookup domain.com (all lowercase) the MX hosts are returned as smtp1.host1.domain.com instead of smtp1.host1.domain.COM
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP