(Hopefully I guessed the right component to file this against; is there a description any place of what is what for RHN? Also, I have no idea of which version to select; presumably I only ever see RHN stable, and only RH internal sees RHN devel?) RHN sends out update email notifications whenever errata which apply to subscribed machines are released. Unfortunately, these emails are being sent from a machine which is not listed in RH's DNS. From the postfix logs on one of my servers: May 2 14:50:18 hanuman postfix/smtpd[4368]: warning: 216.148.218.162: hostname mail.rhns.redhat.com verification failed: Host not found May 2 14:50:18 hanuman postfix/smtpd[4368]: connect from unknown[216.148.218.162] May 2 14:50:18 hanuman postfix/smtpd[4368]: 82F396F23: client=unknown[216.148.218.162] May 2 14:50:19 hanuman postfix/cleanup[4369]: 82F396F23: message-id=<200205022018.PAA29940.redhat.com> host confirms that mail.rhns.redhat.com doesn't resolve, but that mail.rhn.redhat.com does resolve for the same IP: [kaboom@hanuman log]$ host mail.rhn.redhat.com mail.rhn.redhat.com has address 216.148.218.162 [kaboom@hanuman log]$ host mail.rhns.redhat.com Host mail.rhns.redhat.com not found: 3(NXDOMAIN) [kaboom@hanuman log]$ However, the PTR for 216.148.218.162 is correct: [kaboom@hanuman log]$ host 216.148.218.162 162.218.148.216.in-addr.arpa domain name pointer mail.rhns.redhat.com. [kaboom@hanuman log]$ host mail.rhns.redhat.com It looks like a CNAME for mail.rhns.redhat.com needs to be added to the zone file. I only warn, not reject, on misconfigured DNS entries, but some other sites will be within legitimate RFC behavior to reject these emails because of the missing DNS entries....
Reverse PTR changed (some time ago...) to report mail.rhn.redhat.com instead of mail.rhns.redhat.com