(Context: running MM 2.1.12, works great...)
I know why allowing subscriptions without either a confirmation email or a moderator approval is a Dangerous Thing, but is there a way to get MM to allow it? Our list subscriptions are mostly generated by our lab/tool management software in response to a user getting qualified to use a piece of equipment, and I don't want users to have a choice in this case - they get subscribed, period. (They can later unsubscribe of course, but that means they have to actually do something :)
Does this make any sense?
Thanks...
-- Michael P. Young (574) 631-3268 (office) Nanofabrication Specialist (574) 631-4393 (fax) Department of Electrical Engineering (765) 412-6728 (cell) University of Notre Dame mike.young@nd.edumailto:mike.young@nd.edu B-38 Stinson-Remick Hall Notre Dame, IN 46556-5637
On 02/25/2014 06:15 AM, Michael Young wrote:
I know why allowing subscriptions without either a confirmation email or a moderator approval is a Dangerous Thing, but is there a way to get MM to allow it?
For user subscriptions, you need to set Privacy options... -> Subscription rules -> subscribe_policy to None. If the None radio button doesn't appear, you need to set
ALLOW_OPEN_SUBSCRIBE = Yes
in mm_cfg.py. Alternatively, you can set the list's subscribe_policy to zero using withlist or config_list.
Our list subscriptions are mostly generated by our lab/tool management software in response to a user getting qualified to use a piece of equipment, and I don't want users to have a choice in this case - they get subscribed, period. (They can later unsubscribe of course, but that means they have to actually do something :)
Depending on how the lab/tool management software actually subscribes the users, the above may not be needed or even work. Obviously, whatever you are doing now results in a confirmation request, but there are other ways. See the FAQ at http://wiki.list.org/x/uIA9, and/or the archived post at https://mail.python.org/pipermail/mailman-users/2004-December/041214.html
Or the software could just generate an input file for Mailman's bin/add_members which could be invoked either directly by the software or via a wrapper like the members.c wrapper attached to the above FAQ if necessary for permissions, or the add_members process could be just run periodically by cron.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi, hope I haven’t missed anything obvious.
I have set subscription to need approval but when I go to the website and “reject” a spurious subscription it reports, that an email has been sent to the address informing them of the rejection.
Is it possible to configure silent rejection of subscription requests as most of those I reject are prospective spammers
BW TIm
Hi, hope I haven’t missed anything obvious.
I have set subscription to need approval but when I go to the website and “reject” a spurious subscription it reports, that an email has been sent to the address informing them of the rejection.
Is it possible to configure silent rejection of subscription requests as most of those I reject are prospective spammers
BW TIm
On 02/25/2014 09:27 AM, Tim Walter wrote:
I have set subscription to need approval but when I go to the website and “reject” a spurious subscription it reports, that an email has been sent to the address informing them of the rejection.
Is it possible to configure silent rejection of subscription requests as most of those I reject are prospective spammers
If you don't want the notice to be sent, "discard" the request instead of "reject"ing it. That's the difference between "discard" and "reject".
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Worked like a charm. Thank you, Mark.
--Mike
On 2/25/2014 12:21 PM, Mark Sapiro wrote:
On 02/25/2014 06:15 AM, Michael Young wrote:
I know why allowing subscriptions without either a confirmation email or a moderator approval is a Dangerous Thing, but is there a way to get MM to allow it?
For user subscriptions, you need to set Privacy options... -> Subscription rules -> subscribe_policy to None. If the None radio button doesn't appear, you need to set
ALLOW_OPEN_SUBSCRIBE = Yes
in mm_cfg.py. Alternatively, you can set the list's subscribe_policy to zero using withlist or config_list.
Our list subscriptions are mostly generated by our lab/tool management software in response to a user getting qualified to use a piece of equipment, and I don't want users to have a choice in this case - they get subscribed, period. (They can later unsubscribe of course, but that means they have to actually do something :)
Depending on how the lab/tool management software actually subscribes the users, the above may not be needed or even work. Obviously, whatever you are doing now results in a confirmation request, but there are other ways. See the FAQ at http://wiki.list.org/x/uIA9, and/or the archived post at https://mail.python.org/pipermail/mailman-users/2004-December/041214.html
Or the software could just generate an input file for Mailman's bin/add_members which could be invoked either directly by the software or via a wrapper like the members.c wrapper attached to the above FAQ if necessary for permissions, or the add_members process could be just run periodically by cron.
-- Michael P. Young (574) 631-3268 (office) Nanofabrication Specialist (574) 631-4393 (fax) Department of Electrical Engineering (765) 412-6728 (cell) University of Notre Dame mike.young@nd.edu B-38 Stinson-Remick Hall Notre Dame, IN 46556-5637
participants (4)
-
Mark Sapiro
-
Michael Young
-
mike young
-
Tim Walter