On Wednesday 17 September 2003 17:13, Res wrote: > On Wed, 17 Sep 2003, Gerry Doris wrote: > > This translates into a major spam loophole since spammers often > > fake their domains but MTA's like sendmail default to confirming > > they are at least valid. Now any .com or .net will show up as > > valid. > > Simply have sendmail check to see if there is a PTR record if not, it > gets rejected anyway, but I agree its apin in the ass, I have sent a > notice to my clients advising them that all routs to verisign are now > a no go, furthermore I reminded them it is my equipment and > ultimately I decide what content is permited... this includes > verisign and thwat (who are owned by verisign) certificates, which I > now deem to be hostile content. > > This is not the first time verisgn aka network non-solutions have > fscked with my business, so I sure as hell are going to return the > favour now :)
Verisign provides PTR records for those machines that are "resolving" the "unresolved. 17:39:59 # host notpresz.com notpresz.com has address 64.94.110.11 17:40:18 # dig -x 64.94.110.11 ; <<>> DiG 9.2.1 <<>> -x 64.94.110.11 ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57455 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUESTION SECTION: ;11.110.94.64.in-addr.arpa. IN PTR ;; ANSWER SECTION: 11.110.94.64.in-addr.arpa. 900 IN PTR sitefinder-idn.verisign.com. ;; AUTHORITY SECTION: 110.94.64.in-addr.arpa. 900 IN NS ns2.lax.pnap.net. 110.94.64.in-addr.arpa. 900 IN NS ns1.lax.pnap.net. ;; ADDITIONAL SECTION: ns1.lax.pnap.net. 43200 IN A 216.52.254.1 ns2.lax.pnap.net. 43200 IN A 216.52.254.33 ;; Query time: 358 msec ;; SERVER: 67.153.21.4#53(67.153.21.4) ;; WHEN: Wed Sep 17 17:40:30 2003 ;; MSG SIZE rcvd: 164 Regards, Mike Klinke -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
