default action on administrative requests
I sent this question a while back and had no reply. I didn't see my own message come back to me by way of the mailing list, so I presume it did not get out.
I'm using Mailman 2.1.2 with Python 2.1.3 with Solaris 8.
I've looked through the FAQ. I've seen a similar question on this list, but the answer was "get Mailman 2.1". I now have 2.1.2, but this issue still eludes me.
I have a list that gets more spam than legit email. I would like to have the "Action to take on all these held messages" on the "admindb/<listname>" page to have a default of "discard" instead of "defer". This way I can quickly scan the "baddies" and then "submit all data" once I see they are all spam; no clicking on the "Discard" radio button.
I don't want to use the Privacy Options -> Sender Filters option of:
Action to take for postings from non-members for which no explicit action is defined.
to be "discard". I know that the messages would come to me with the:
Should messages from non-members, which are automatically discarded, be forwarded to the list moderator?
but I really don't want the messages automatically coming to me; I want the member of my list to receive it if I click "Accept".
I've seen reference to a script that will just toss everything that is queued up for a list; I would rather not do this.
Right now, I also wish this behavior for one list only, not as a default for all the lists that I have.
What file do I need to change to make the default choice be "discard" on the administrative requests page?
Pointers to documentation gratefully accepted.
Thank you,
Hal Huntley SRI International
At 6:36 PM -0700 2003/07/29, Hal Huntley wrote:
I sent this question a while back and had no reply. I didn't see my own message come back to me by way of the mailing list, so I presume it did not get out.
I recall seeing your question. If not yours, then one very much like it.I have a list that gets more spam than legit email. I would like to have the "Action to take on all these held messages" on the "admindb/<listname>" page to have a default of "discard" instead of "defer". This way I can quickly scan the "baddies" and then "submit all data" once I see they are all spam; no clicking on the "Discard" radio button.
Unfortunately, I don't have any answers for you. That's why I didn't respond to your previous message.
Sorry, I wish I could help. If you find out what the answer is, please let us know.
-- Brad Knowles, brad.knowles@skynet.be
"They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania.
GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)
Hi Hal,
On Wednesday, July 30, 2003, at 11:36 AM, Hal Huntley wrote:
I have a list that gets more spam than legit email. I would like to have the "Action to take on all these held messages" on the "admindb/<listname>" page to have a default of "discard" instead of "defer". This way I can quickly scan the "baddies" and then "submit all data" once I see they are all spam; no clicking on the "Discard" radio button.
Not a definitive answer, but I've found the following in Mailman/Mailman/Cgi/admindb.py:
radio = RadioButtonArray(id, (_('Defer'), _('Approve'), _('Reject'), _('Discard')), values=(mm_cfg.DEFER, mm_cfg.SUBSCRIBE, mm_cfg.REJECT, mm_cfg.DISCARD), checked=0).Format()
I reckon (but have not confirmed) that you could change the checked=0 bit to checked=4 for Approve checked=2 for Reject checked=3 for Discard
(got these values from the HTML source generated in a typical Administrative Requests page)
This seems to put a CHECKED flag in the <INPUT> tag, which I'm not actually sure is valid HTML. My reading seems to suggest that a value="Yes" is required instead. If that is not visible, then the standard is unclear. One version says the user agent should select the first radio button in the group, so you may want to try rearranging the order of the buttons in the RadioButtonArray above instead.
Right now, I also wish this behavior for one list only, not as a default for all the lists that I have.
Hmm, dunno about that!
Hope that helps, tell us how you go! Heath
| Heath Raftery | | hraftery@myrealbox.com | | *There's nothing like a depressant to cheer you up* | | - Heard at Moe's Tavern | | _\|/_ | |________________________________________m(. .)m_________|
On Wednesday, July 30, 2003, at 03:06 pm, Heath Raftery wrote:
Hi Hal,
On Wednesday, July 30, 2003, at 11:36 AM, Hal Huntley wrote:
I have a list that gets more spam than legit email. I would like to have the "Action to take on all these held messages" on the "admindb/<listname>" page to have a default of "discard" instead of "defer". This way I can quickly scan the "baddies" and then "submit all data" once I see they are all spam; no clicking on the "Discard" radio button.
Not a definitive answer, but I've found the following in Mailman/Mailman/Cgi/admindb.py:
radio = RadioButtonArray(id, (_('Defer'), _('Approve'), _('Reject'), _('Discard')), values=(mm_cfg.DEFER, mm_cfg.SUBSCRIBE, mm_cfg.REJECT, mm_cfg.DISCARD), checked=0).Format()
I reckon (but have not confirmed) that you could change the checked=0 bit to checked=4 for Approve checked=2 for Reject checked=3 for Discard
Not quite. The value assigned to the checked parameter is the offset of the radio button in the array which is initially checked when the form is rendered; the value is the offset in the preceding list of button names and their values. So:
checked=0 means the 'Defer' button would be checked checked=1 means the 'Approve' button would be checked checked=2 means the 'Reject' button would be checked checked=3 means the 'Discard' button would be checked
(got these values from the HTML source generated in a typical Administrative Requests page)
This seems to put a CHECKED flag in the <INPUT> tag, which I'm not actually sure is valid HTML.
It is valid HTML. CHECKED (without any value associated) is a valid attribute of an INPUT tag of TYPE="radio". It causes that radio button to be in the "on" state when the form is initially displayed.
My reading seems to suggest that a value="Yes" is required instead. If that is not visible, then the standard is unclear. One version says the user agent should select the first radio button in the group, so you may want to try rearranging the order of the buttons in the RadioButtonArray above instead.
Right now, I also wish this behavior for one list only, not as a default for all the lists that I have.
Hmm, dunno about that!
If you hack the code in the admindb.py file then the changes will affect all lists equally.
Hope that helps, tell us how you go! Heath
| Heath Raftery | | hraftery@myrealbox.com | | *There's nothing like a depressant to cheer you up* | | - Heard at Moe's Tavern | | _\|/_ | |________________________________________m(. .)m_________|
participants (4)
-
Brad Knowles -
Hal Huntley -
Heath Raftery -
Richard Barrett