https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6985
--- Comment #14 from Joe Quinn <[email protected]> --- I would like to commit a change that makes our TLD list more maintainable by automating the crunching that is done on the master list at http://data.iana.org/TLD/tlds-alpha-by-domain.txt Unfortunately, there are several odd TLD tests that I noticed might be wrong and they are holding up the commit. The TLDs in question are .foo, .bar, .gb, .sj, .bv. Both foo and bar are Google's new TLDs, and the other three are country codes with no active subdomains. These tests are making sure that URIs do not match when they are using any of the given subdomains. Does anyone have an opinion on removing the tests below? Is there a reason they were there to begin with? I can't imagine the use case for failing to detect a URI that is using an out-of-service TLD. The test output is below: # Failed test 639 in t/uri_text.t at line 54 fail #8 failure: did find /^http://example.foo$/ # Failed test 643 in t/uri_text.t at line 54 fail #12 failure: did find /^http://www.example.gb$/ # Failed test 649 in t/uri_text.t at line 54 fail #18 failure: did find /^http://example.gb$/ # Failed test 654 in t/uri_text.t at line 54 fail #23 failure: did find /zai6Vuwi/ # Failed test 658 in t/uri_text.t at line 54 fail #27 failure: did find /^http://example.sj$/ # Failed test 667 in t/uri_text.t at line 54 fail #36 failure: did find /^http://www.example.bv$/ # Failed test 671 in t/uri_text.t at line 54 fail #40 failure: did find /^http://www.example.sj$/ # Failed test 674 in t/uri_text.t at line 54 fail #43 failure: did find /^http://www.example.foo$/ # Failed test 682 in t/uri_text.t at line 54 fail #51 failure: did find /^http://example.bv$/ -- You are receiving this mail because: You are the assignee for the bug.
