in reply to Installing Email::Valid

This is test 10: 

$v->address( -address => 'blort@notarealdomainfoo.com',
             -mxcheck => 1) ? not_ok : ok;

[download]

As you can see this address is expected to fail the mxcheck on 'notarealdomainfoo.com'. This FAILS TO FAIL because this is now a valid domain with A and MX records - blame Verisign!

Bottom line don't worry about it. Change the test to 'blort@surely-no-one-has-registered-this-hopefully-no-existsant-domain-flubber-dubber-doo' and it sould fail, but then again you never know! 

[root@devel3 root]# dig -tA notarealdomainfoo.com

; <<>> DiG 9.2.2 <<>> -tA notarealdomainfoo.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21892
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL:
+ 13

;; QUESTION SECTION:
;notarealdomainfoo.com.         IN      A

;; ANSWER SECTION:
notarealdomainfoo.com.  900     IN      A       64.94.110.11

;; AUTHORITY SECTION:
com.                    68041   IN      NS      e.gtld-servers.net.
com.                    68041   IN      NS      i.gtld-servers.net.
com.                    68041   IN      NS      k.gtld-servers.net.
com.                    68041   IN      NS      b.gtld-servers.net.
com.                    68041   IN      NS      l.gtld-servers.net.
com.                    68041   IN      NS      c.gtld-servers.net.
com.                    68041   IN      NS      d.gtld-servers.net.
com.                    68041   IN      NS      g.gtld-servers.net.
com.                    68041   IN      NS      m.gtld-servers.net.
com.                    68041   IN      NS      j.gtld-servers.net.
com.                    68041   IN      NS      a.gtld-servers.net.
com.                    68041   IN      NS      f.gtld-servers.net.
com.                    68041   IN      NS      h.gtld-servers.net.

;; ADDITIONAL SECTION:
e.gtld-servers.net.     134007  IN      A       192.12.94.30
i.gtld-servers.net.     150216  IN      A       192.43.172.30
k.gtld-servers.net.     150216  IN      A       192.52.178.30
b.gtld-servers.net.     150216  IN      A       192.33.14.30
l.gtld-servers.net.     78864   IN      A       192.41.162.30
c.gtld-servers.net.     150216  IN      A       192.26.92.30
d.gtld-servers.net.     150216  IN      A       192.31.80.30
g.gtld-servers.net.     147680  IN      A       192.42.93.30
m.gtld-servers.net.     150216  IN      A       192.55.83.30
j.gtld-servers.net.     150216  IN      A       192.48.79.30
a.gtld-servers.net.     72621   IN      A       192.5.6.30
f.gtld-servers.net.     86057   IN      A       192.35.51.30
h.gtld-servers.net.     126375  IN      A       192.54.112.30

;; Query time: 23 msec
;; SERVER: 207.218.192.38#53(207.218.192.38)
;; WHEN: Tue Sep 30 01:37:27 2003
;; MSG SIZE  rcvd: 508

[root@devel3 root]# dig -tMX notarealdomainfoo.com

; <<>> DiG 9.2.2 <<>> -tMX notarealdomainfoo.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15188
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 
+0

;; QUESTION SECTION:
;notarealdomainfoo.com.         IN      MX

;; AUTHORITY SECTION:
com.                    172800  IN      SOA     a.gtld-servers.net. ns
+tld.verisign-grs.com. 2003092901 1800 900 604800 86400

;; Query time: 43 msec
;; SERVER: 207.218.192.38#53(207.218.192.38)
;; WHEN: Tue Sep 30 01:37:32 2003
;; MSG SIZE  rcvd: 112

[root@devel3 root]#

[download]

cheers

tachyon

s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print

Replies are listed 'Best First'.
Re: Re: Installing Email::Valid
by edoc (Chaplain) on Sep 30, 2003 at 04:57 UTC

    ..just another casualty of Verisign's greed..

    cheers,

    J

[reply]

      Yup. I wonder who will buy that domain!

      cheers

      tachyon

      s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print

[reply]
Re: Re: Installing Email::Valid
by HyperZonk (Friar) on Sep 30, 2003 at 05:10 UTC
    <BEGIN RANT>
    May the cursed bean-counters at VeriSign grow hives on their various anatomical parts!

    Who knows how much validity / sanity check code they have broken with their money-grubbing scheme? One of the most useful (to people who deal with email registration issues) modules now doesn't work quite right. Great! I've always disabled the SMTP authentication (too much overhead for large lists), and relied on all of the other checks to filter out a majority of the bad addresses. This will certainly reduce the effectiveness of the module for me.

    Not to mention every other program that has ever been written to check for domain validity is probably now broken. But to break perl modules! The inhumanity!!!

    <END RANT>


    -HZ
[reply]

      How stupid is this..... 

      [root@devel3 cgi-bin]# dig may-the-cursed-bean-counters-at-verisign-gr
+ow-hives.com

; <<>> DiG 9.2.2 <<>> may-the-cursed-bean-counters-at-verisign-grow-hi
+ves.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7959
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL:
+ 12

;; QUESTION SECTION:
;may-the-cursed-bean-counters-at-verisign-grow-hives.com. IN A

;; ANSWER SECTION:
may-the-cursed-bean-counters-at-verisign-grow-hives.com. 900 IN A 64.9
+4.110.11

      [download]

      As you say they have now trashed all email domain validation. But there appears to be a workaround: 

      [root@devel3 cgi-bin]# dig do-not-adjust-your-mind-there-is-a-fault-in
+-reality.com                 

; <<>> DiG 9.2.2 <<>> do-not-adjust-your-mind-there-is-a-fault-in-real
+ity.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7723
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL:
+ 9

;; QUESTION SECTION:
;do-not-adjust-your-mind-there-is-a-fault-in-reality.com. IN A

;; ANSWER SECTION:
do-not-adjust-your-mind-there-is-a-fault-in-reality.com. 900 IN A 64.9
+4.110.11

      [download]

      All these non-exitants seem to resolve to a single server so you ought to be able to patch for that (until they break it again)

      cheers

      tachyon

      s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print

[reply]
[d/l]
[select]
        Actually, a co-worker and I were discussing this just the other day when he noted that the domains were all resolving to the same IP.

        In a calmer frame of mind at the time than I was when I wrote the above, I suggested that it might not even be quite so bad if they promised to keep the fakey IP the same. It would still take a lot of code repair to make things work in the expected way again, but it would be fixable at least. So I thought.

        But in retrospect, they have blatantly abused their power. No one else can say "abracadabra ... domains I don't own are now my own advertising portals!" Only VeriSign can ... and therefore, shouldn't. They've been given a ... well, if not sacred, at least special trust to curate the TLD system. And they've hijacked it for their own profit. In a way that no one can compete with.

        That's a monopoly, and that is, if not illegal, then ethically questionable.


        -HZ
[reply]

In Section Seekers of Perl Wisdom