I get many emails from yahoo that pass DKIM and do not have SPF records
(I don't think.. this according to the spamassassin rule hits for the
email). In fact, it is true of this very email via yahoogroups.com

I would be interested in continuing support of it. Reimplementing for
DKIM instead of DK would be nice, but obviously more work. I will see
if I can get another query server running.. no promises :) I'll
double-check SPF on yahoo emails too.

Joshua Tauberer wrote:
> 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.
>


--
Dave Brondsema
Software Developer
Cornerstone University