On Jul 25, 2010, at 2:43, Jared Johnson wrote: > it will soon be hopelessly forked from normal QP on account of > per-recipient config directives, etc.
Having a common API for "per-recipient" things have long been on the todo list. We've talked about it a couple times before; but the requirements/needs/wishes never sunk in deep enough in my head to do anything about it. So: How do you use this? My thoughts all along have been to just have some way to make a "find user data" plugin that'll fetch a per-recipient blob of information that other plugins can, uh, plug into. The big stumbling block is what the common infrastructure for dealing with diverting needs of the recipients should be. What would we need in terms of per-recipient header rewriting, post-DATA processing etc? - ask -- http://develooper.com/ - http://askask.com/
