mail commands

[Wyardley]

when approving a message via email, if you type:
Approved: passwrd

in the headers of a response to the confirmation
message, when the actual password is 'password', the
message you're trying to approve is discarded; I think
that no action (and an "incorrect password" error
message in response) would be more appropriate.

Also, as I've mentioned before, it would be very nice
if the exact action being performed were listed, rather
than the generic "confirmation succeeded" message.

[http://sourceforge.net/tracker/index.php?func=detail&aid=717110&group_id=103&atid=100103]

[Barry Warsaw (barry)]

After re-reading this bug report, I believe Mailman is
working as expected. If you read the body of the
confirmation message, you'll see that replying to it keeping
the subject intact always discards the original message.

The way to approve it is to resend the first message in the
digest, which is the original held message. Add Approved:
password header to the resend, and then reply to the
confirmation message to get rid of the old hold.

I admit this isn't the most convenient way to do it, but for
now that's it.

[Wyardley (wyardley)]

Perhaps I'm misreading the message?

The message I see says:

"If you reply to this message, keeping the Subject: header
intact, Mailman will discard the held message. Do this if
the message is spam. If you reply to this message and
include an Approved: header with the list password in it,
the message will be approved for posting to the list. The
Approved: header can also appear in the first line of the
body of the reply."

This seems to say that the *confirmation* message, not the
original message should have the 'Approved:' header. Am I
reading something wrong here?

[Barry Warsaw (barry)]

Ah, you're right. Re-opening. Either the message in the
confirmation is broken, or the email cmd handler is broken.
 I won't decide that yet. :)

[Wyardley (wyardley)]

FWIW, in my experience, responding to the confirmation
message itself with the proper Approved header works just
fine. It's only when the password is incorrect that the
message is deleted.

[Mark Sapiro (msapiro)]

This bug was fixed in Mailman 2.1.4.