https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6872
--- Comment #9 from Willem Toorop <wil...@nlnetlabs.nl> --- (In reply to comment #8 by Mark Martinec) > I think adopting Willem's suggestion is a good (yet hackish) short term > solution until the 3.4 can be released to a general public (noting that > several sites are already using 3.4(trunk) in production). Thanks! I hope you will apply it. Let me know if you will so I can release 0.71 with the other issues resolved (DKIM etc). For smoothest transition I think it would be best to first update mirrors.updates.spamassassin.org, and then wait for one hour (the TTL of the records) before updating <version>.updates.spamassassin.org. That way you are sure that if an sa-update gets a new version number from DNS, it can also get the url for fetching MIRRORED.BY. If you alter them at the same time you have a small risk that a resolver still has the old value for mirrors.updates.spamassassin.org in its cache whilst the <version>.updates.spamassassin.org is updated causing sa-update to fail with: error: no mirror data available for channel updates.spamassassin.org channel: MIRRORED.BY file location was not in DNS, channel failed Best regards, Willem Toorop -- You are receiving this mail because: You are the assignee for the bug.
