I'm thinking of dropping support for DomainKeys from the extension
because 1) I'm having a non-trivial time installing the needed Perl
modules on my new web server to do the server-side half of it, and 2)
I'm not so interested anymore in providing a DK-checking server for
users of the extension (which existed since programming those checks
within the extension was difficult to program) since it uses up server
resources (that not much, but enough to notice).

In my personal experience, very few mails fail SPF checks and have a DK
header. So I won't miss it, although I thought it was neat to have.

This is a last call in case it's actually important to anyone. If you
want to help, you could:

* Provide a new public 'query server' to do the server-side checks
* Implement the checks in native code within the extension to
avoid the need for a query server
* And optionally reimplement these things to conform to the new
DKIM spec that replaces DK.

--
- Josh Tauberer

http://razor.occams.info

"Yields falsehood when preceded by its quotation! Yields
falsehood when preceded by its quotation!" Achilles to
Tortoise (in "Gödel, Escher, Bach" by Douglas Hofstadter)