Bjørn Mork writes:

> Does anyone see how this could be avoided, still keeping the async
> computation?  If we at the same time could get async hashcash
> computation for new recepients, then that would of course be even
> better.

I don't have a solution for the former, but I have the following in my
.gnus.el to take care of the latter: