Ideally this should be exposed by extending the content manager.  Instantiating MIME classes is part of the old API, not the new. The code in the PR may well be correct, but class should be hidden from the normal user (of the new API).  I'm not sure what the best way to specify the signing function will be, but I'm guessing a new keyword parameter in the content API.

Note that the current content management API is more of a framework than a fully worked out system, so figuring out the best way to add this may require some design discussion.