If you're using restriction_classes that requires a HELO msn.com to have a
1) PTR hostname
AND
2) PTR hostname containing msn.com (or hotmail.com).
... then beware that MS has not set up their reverse zone for their
"groups" outbound:
unknown[65.54.195.209]:
from=<[EMAIL PROTECTED]>
helo=<p01.groups.msn.com>
unknown[65.54.195.209]:
from=<[EMAIL PROTECTED]>
helo=<p01.groups.msn.com>
unknown[65.54.195.209]:
from=<[EMAIL PROTECTED]>
helo=<p01.groups.msn.com>
unknown[65.54.195.210]:
from=<[EMAIL PROTECTED]> helo=<p02.groups.msn.com>
unknown[65.54.195.210]: from=<[EMAIL PROTECTED]>
helo=<p02.groups.msn.com>
if you then see WTF that reverse zone is,you see it really good ol Internet
savvy MS:
# dig -x 65.54.195
; <<>> DiG 8.3 <<>> -x
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 5, ADDITIONAL: 5
;; QUERY SECTION:
;; 195.54.65.in-addr.arpa, type = ANY, class = IN
;; ANSWER SECTION:
195.54.65.in-addr.arpa. 49m21s IN SOA dns.cp.msft.net.
msnhst.microsoft.com. (
2003072401 ; serial
30M ; refresh
15M ; retry
11w6d8h ; expiry
1H ) ; minimum
I guess they ran out of money to pay competent for competent DNS
administration.
Len
