On Futureproofing Spamhaus
BMcWilliams writes "Spamhaus director Steve Linford announced a new funding plan Tuesday. According to Linford's announcement, large ISPs and big corporate users of the Spamhaus zone transfer service (renamed the Spamhaus Data Feed Service) will be required to pay an annual subscription fee ranging between $190 and $14,500.(The free public-query mirrors will continue to exist.) The point of the new plan is to ensure that 'the millions of users who rely on our anti-spam systems can be assured we'll be here for as long as spammers plague the Internet'."
In theory you are correct. In practice all ISP's will not simultaneously commence paid spamhaus subscription and increase their fees. I would imagine that some ISP's may use this, either globally or as a premium value added service. Unless you are in a monopolistic market you will be free to choose a spamhaus-free (either lacking or only free zone transfers) ISP and it's assosciated lower costs.
:)
Even then a lot of businesses may actually save money through reducing bandwidth costs due to spam. I hope they don't force those savings onto you...
Good points. Using the Spamhaus XBL and SBL actually saves a decent-sized ISP more than its cost in a given year in bandwidth, storage and CPU cycles.
Additionally Spamhaus is letting operators of free DNSBL mirrors continue the Zone Transfer for free. Perhaps additional ISPs will be given the option of getting the Zone Transfer for free in exchange for setting up another public mirror.
Portable versions of Firefox, GIMP, LibreOffice, etc
Spamhaus recommends organizations that get 200,000+ emails a day sign up for the service. Conservatively, I think, we can estimate that would mean 100,000 users
Just for reference, PSU has roughly 130,000 users, and averages around 4,000,000 emails a day (actually that number is about a year old, I imagine it is considerably higher given the microsoft viruses and spam that are going around now)
Finkployd
You are confusing Spamhaus with SpamCop...
Spamhaus has no affiliation with IronPort!
SPF is not a Microsoft technology. Caller ID is the Microsoft solution (similar but different). SPF was designed by pobox.com. Microsoft and pobox.com recently agreed to make SPF and Caller ID compatible, but they are still different methods:
1. SPF is text based; Caller ID is XML based (even though no other email header or DNS record is).
2. SPF verifies the envelope sender; Caller ID verifies the From header of the email. While both will be the same in many cases, they do not have to be.