Please advise
------------------------------------------------
Oct 26 03:59:49 dch801 postfix/smtpd[21416]: warning: 209.196.28.50:
hostname 50-209.196.28.interliant.com verification failed: Host not found
Oct 26 07:01:23 dch801 postfix/smtpd[24365]: warning: 216.216.220.132:
hostname VISTA1-UBR2-5-hfc-0251-d8d8dc84.rdc1.sdca.coxatwork.com
verification failed: Host not found
Oct 26 08:23:27 dch801 postfix/smtpd[26036]: warning: 38.202.37.197:
hostname minder07.lifeminders.com verification failed: Host not found
Oct 26 11:30:51 dch801 postfix/smtpd[30695]: warning: 216.200.55.4:
hostname 4.betasphere.com verification failed: Host not found
Oct 26 11:59:56 dch801 postfix/smtpd[31460]: warning: 65.207.180.2:
hostname host2.bekaertusa.com verification failed: Host not found
------------------------------------------------------------
--
R. Scott Coats
Manager of Information Technology
Machine & Welding Supply Company
-
To unsubscribe, send mail to majo...@postfix.org with content
(not subject): unsubscribe postfix-users
The warnings indicate that people have set up PTR records
(address->name) but no corresponding A records (name->address).
When this happens, Postfix will not use the client hostname for
access control decisions.
This is fixed by kicking the lazy DNS adminstrator in the butt.
Wietse
Scott Coats: