Issue approving subscription requests
For a list I recently migrated from 2.1.14 on one machine to 2.1.17 on another, I'm unable to approve pending subscription requests. After making my choices and clicking "Submit all data", the radio buttons simply reset themselves with no changes made to the subscriber records.
"check_perms -f" and "check_db" make no complaints about my configuration. Is this a bug? Could something have gotten botched in the migration? The lists seem to be operating fine otherwise.
-MSK
On 04/29/2014 08:30 AM, Murray S. Kucherawy wrote:
For a list I recently migrated from 2.1.14 on one machine to 2.1.17 on another, I'm unable to approve pending subscription requests. After making my choices and clicking "Submit all data", the radio buttons simply reset themselves with no changes made to the subscriber records.
See the FAQ at http://wiki.list.org/x/ioA9.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks, Mark. It's almost certainly the redirect issue.
Is there a way to do manual approvals from the command line until I can get rid of the redirect? On Apr 29, 2014 9:39 AM, "Mark Sapiro" mark@msapiro.net wrote:
On 04/29/2014 08:30 AM, Murray S. Kucherawy wrote:
For a list I recently migrated from 2.1.14 on one machine to 2.1.17 on another, I'm unable to approve pending subscription requests. After making my choices and clicking "Submit all data", the radio buttons simply reset themselves with no changes made to the subscriber records.
See the FAQ at http://wiki.list.org/x/ioA9.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/superuser%40gmail.com
On 04/29/2014 11:09 AM, Murray S. Kucherawy wrote:
Thanks, Mark. It's almost certainly the redirect issue.
Is there a way to do manual approvals from the command line until I can get rid of the redirect?
See the script at http://www.msapiro.net/scripts/list_requests.
Also, if you set admin_immed_notify to yes, the notice to the admin has three MIME parts. part 1 is the held post notice; part 2 is the held post itself, and part 3 is another message/rfc822 part which can be 'replied' to by email. If you simply reply to this message, to original post will be discarded, but if you include an 'Approved: password' header (or first body line pseudo header) in the reply, the post will be accepted. In the header, password is the list admin or moderator password or the (new in 2.1.15) poster password.
See the Passwords section of the admin interface, although you'll probably not be able to set the poster password for the same reason you can't approve posts, but you can always set it with config_list with input
post_password = 'desired_pw_value'
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
What about managing subscription requests? On Apr 29, 2014 11:38 AM, "Mark Sapiro" mark@msapiro.net wrote:
On 04/29/2014 11:09 AM, Murray S. Kucherawy wrote:
Thanks, Mark. It's almost certainly the redirect issue.
Is there a way to do manual approvals from the command line until I can get rid of the redirect?
See the script at http://www.msapiro.net/scripts/list_requests.
Also, if you set admin_immed_notify to yes, the notice to the admin has three MIME parts. part 1 is the held post notice; part 2 is the held post itself, and part 3 is another message/rfc822 part which can be 'replied' to by email. If you simply reply to this message, to original post will be discarded, but if you include an 'Approved: password' header (or first body line pseudo header) in the reply, the post will be accepted. In the header, password is the list admin or moderator password or the (new in 2.1.15) poster password.
See the Passwords section of the admin interface, although you'll probably not be able to set the poster password for the same reason you can't approve posts, but you can always set it with config_list with input
post_password = 'desired_pw_value'
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 04/29/2014 11:45 AM, Murray S. Kucherawy wrote:
What about managing subscription requests?
This script will do those too.
See the script at <http://www.msapiro.net/scripts/list_requests>.
The following won't work for (un)subscription because the notice to the admin doesn't contain the confirm message/token.
Also, if you set admin_immed_notify to yes, the notice to the admin has three MIME parts. part 1 is the held post notice; part 2 is the held post itself, and part 3 is another message/rfc822 part which can be 'replied' to by email. If you simply reply to this message, to original post will be discarded, but if you include an 'Approved: password' header (or first body line pseudo header) in the reply, the post will be accepted. In the header, password is the list admin or moderator password or the (new in 2.1.15) poster password. See the Passwords section of the admin interface, although you'll probably not be able to set the poster password for the same reason you can't approve posts, but you can always set it with config_list with input post_password = 'desired_pw_value'
And the above won't work either. The file contents need to be
from Mailman.Utils import sha_new post_password = sha_new('desired_pw_value').hexdigest() del sha_new
I forgot that config_list won't do the encryption. Also, the 'del sha_new' line isn't mandatory, but omitting it will result in an 'attribute "sha_new" ignored' warning from config_list.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Tue, Apr 29, 2014 at 11:38 AM, Mark Sapiro mark@msapiro.net wrote:
See the script at http://www.msapiro.net/scripts/list_requests.
Tried that, got this:
./list_requests -H -l <listname>
<address> (name) <date> (S)kip, (A)ccept, (R)eject, (D)iscard [sard] A Traceback (most recent call last): File "./list_requests", line 216, in <module> main() File "./list_requests", line 128, in main changed += handle_req(mlist, id) File "./list_requests", line 204, in handle_req mlist.HandleRequest(id, mm_cfg.APPROVE) File "/usr/local/mailman/Mailman/ListAdmin.py", line 172, in HandleRequest status = self.__handlesubscription(data, value, comment) File "/usr/local/mailman/Mailman/ListAdmin.py", line 428, in __handlesubscription assert value == mm_cfg.SUBSCRIBE
On 04/30/2014 11:58 AM, Murray S. Kucherawy wrote:
On Tue, Apr 29, 2014 at 11:38 AM, Mark Sapiro mailto:mark@msapiro.net> wrote:
See the script at <http://www.msapiro.net/scripts/list_requests>.
Tried that, got this:
./list_requests -H -l <listname>
<address> (name) <date> (S)kip, (A)ccept, (R)eject, (D)iscard [sard] A Traceback (most recent call last): File "./list_requests", line 216, in <module> main() File "./list_requests", line 128, in main changed += handle_req(mlist, id) File "./list_requests", line 204, in handle_req mlist.HandleRequest(id, mm_cfg.APPROVE) File "/usr/local/mailman/Mailman/ListAdmin.py", line 172, in HandleRequest status = self.__handlesubscription(data, value, comment) File "/usr/local/mailman/Mailman/ListAdmin.py", line 428, in __handlesubscription assert value == mm_cfg.SUBSCRIBE
I guess I never tested accepting a subscription :(
I have the same issue. I'll fix and post when I have.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 04/30/2014 11:58 AM, Murray S. Kucherawy wrote:
On Tue, Apr 29, 2014 at 11:38 AM, Mark Sapiro mailto:mark@msapiro.net> wrote:
See the script at <http://www.msapiro.net/scripts/list_requests>.
Tried that, got this:
./list_requests -H -l <listname>
<address> (name) <date> (S)kip, (A)ccept, (R)eject, (D)iscard [sard] A Traceback (most recent call last): File "./list_requests", line 216, in <module> main() File "./list_requests", line 128, in main changed += handle_req(mlist, id) File "./list_requests", line 204, in handle_req mlist.HandleRequest(id, mm_cfg.APPROVE) File "/usr/local/mailman/Mailman/ListAdmin.py", line 172, in HandleRequest status = self.__handlesubscription(data, value, comment) File "/usr/local/mailman/Mailman/ListAdmin.py", line 428, in __handlesubscription assert value == mm_cfg.SUBSCRIBE
The script never worked to approve (un)subscriptions. Sorry about that. It's fixed now. get the version with
# Copyright (C) 1998-2014 by the Free Software Foundation, Inc.
from http://www.msapiro.net/scripts/list_requests or http://fog.ccsf.edu/~msapiro/scripts/list_requests, and it will work.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Wed, Apr 30, 2014 at 5:05 PM, Mark Sapiro mark@msapiro.net wrote:
The script never worked to approve (un)subscriptions. Sorry about that. It's fixed now. get the version with
# Copyright (C) 1998-2014 by the Free Software Foundation, Inc.
from http://www.msapiro.net/scripts/list_requests or http://fog.ccsf.edu/~msapiro/scripts/list_requests, and it will work.
That worked, thanks!
-MSK
participants (2)
-
Mark Sapiro
-
Murray S. Kucherawy