On Mon, Mar 19, 2012 at 2:59 AM, Mark Sapiro wrote:
> If that were all that was required, that would be fine. The problem is
> that we allow approval via a pseudo-header as the first non-blank body
> line in the first text/plain part of the message, and we have to look
> for it there and if found
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/18/2012 3:28 AM, Stephen J. Turnbull wrote:
>
> ... Having both one or more Handlers and a special seems like
> overkill, especially since really one checks the header and the
> other deletes, completely different functionality. Wouldn't it be
On Sat, Mar 17, 2012 at 2:41 AM, Mark Sapiro wrote:
> I've gone around a bit on this and I've concluded this is analogous to
> the list poster password I implemented for 2.1. Presumably we don't
> want to allow this password to be used to authenticate to the web ui.
Right.
> We may want to allo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've had several thoughts on what is now (in MM 3) done by
rules/approved.py.
There is a moderator_password list attribute which can be used in a
(X-)Approve(d): header or first body line pseudo-header to pre-approve
a list post.
I've gone around a b
