https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6083
--- Comment #3 from Adam Katz <[email protected]> 2009-05-20 14:48:13 PST --- 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... $ host -t txt mirrors.testtxt.khopesh.com. |sort |perl -pne 's/^.*"([^"]+)"$/$1/' http://abcdefghijklmnopqrstuvwxyz.abcdefghijklmnopqrstuvwxyz.museum/abcdefghijklmnopqrstuvwxyz/abcdefghijklmnopqrstuvwxyz/this-is-a-ridiculously-long-sa-update-channel-name-with-tons-and-tons-of-text.cf weight=99999999999999999 http://daryl.dostech.ca/sa-update/sare/72_sare_redirect_post3.0.0.cf weight=500 http://mirror-03.example.com/testtxt weight=5 http://mirror-04.example.com/testtxt weight=4 http://mirror-05.example.com/testtxt weight=4 http://mirror-06.example.com/testtxt weight=4 http://mirror-07.example.com/testtxt weight=4 http://mirror-08.example.com/testtxt weight=2 http://mirror-09.example.com/testtxt weight=2 http://mirror-10.example.com/testtxt weight=2 http://mirror-11.example.com/testtxt weight=1 http://mirror-12.example.com/testtxt weight=1 $ Every time there is an update, the mirrors should probably be re-cached. sa-update should probably also spit out a warning when there is only one mirror. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
