https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6083
--- Comment #4 from Theo Van Dinter <[email protected]> 2009-05-20 16:34:05 PST --- I don't recall all of the details at the moment, but I think the main concern I had was that the length of the information in the mirby file would cause lots of TCP DNS queries. The plan was DNS for small/quick things and HTTP for larger bits. sure enough: $ host -t txt mirrors.testtxt.khopesh.com ;; Truncated, retrying in TCP mode. mirrors.testtxt.khopesh.com descriptive text "http://daryl.dostech.ca/sa-update/sare/72_sare_redirect_post3.0.0.cf weight=500" mirrors.testtxt.khopesh.com descriptive text "http://abcdefghijklmnopqrstuvwxyz.abcdefghijklmnopqrstuvwxyz.museum/abcdefghijklmnopqrstuvwxyz/abcdefghijklmnopqrstuvwxyz/this-is-a-ridiculously-long-sa-update-channel-name-with-tons-and-tons-of-text.cf weight=99999999999999999" [...] (In reply to comment #3) > Why does SA even use a mirrors file instead of direct TXT records? Here's a > live example with a dozen round-robin TXT entries, including the longest > real-life mirror I could find plus a ridiculously long example URL. Am I > missing some piece of the RFC that prohibits this? We're already delayed by > the propagation time of the versions, so that doesn't affect anything... -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
