Re: [Mailman-Users] unsubscribe without confirmation
![](https://secure.gravatar.com/avatar/17bd3f151cc6192644f17924e9f27ea1.jpg?s=120&d=mm&r=g)
Thanks!!
I understand the purpose of the confirmation, I just want the ability to turn it off. It is okay if users get unsubscribed from my list because of a spooked request.
-----Original Message----- From: Mark Sapiro [mailto:msapiro@value.net] Sent: Wednesday, July 27, 2005 11:52 AM To: Sintz, James; mailman-users@python.org Subject: Re: [Mailman-Users] unsubscribe without confirmation
Sintz, James wrote:
Is there a way to enable unsubscribing without requiring user confirmation? Users are added to the list manually by an administrator, yet we do want to allow users the ability to unsubscribe using the listname-leave@ address.
E-mail unsub requests require confirmation to prevent spoofed requests from succeeding. The user can avoid the confirmation by providing his/her password with the e-mailed unsubscribe command, but this only works if an unsubscribe command is mailed to the listname-request address. Mail to the listname-leave or listname-unsubscribe address is not parsed for commands and is treated as if it just contained a plain 'unsubscribe'.
Send mail with subject 'help' (w/o the quotes) to the listname-request address for more info on the unsubscribe command.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
CONFIDENTIALITY NOTICE: The Ohio Public Employees Retirement System intends this e-mail message, and any attachments, to be used only by the person(s) or entity to which it is addressed. This message may contain confidential and/or legally privileged information. If the reader is not the intended recipient of this message or an employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that you are prohibited from printing, copying, storing, disseminating or distributing this communication. If you received this communication in error, please delete it from your computer and notify the sender by reply e-mail.
![](https://secure.gravatar.com/avatar/746f7519ba02fb0d815e59f305c53fa2.jpg?s=120&d=mm&r=g)
Sintz, James wrote:
I understand the purpose of the confirmation, I just want the ability to turn it off. It is okay if users get unsubscribed from my list because of a spooked request.
If you really want to do it, I think the attached patch will allow it.
Warning - this is untested, use at your own risk.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/5ada79a8a91b40e8c35ddd9e412beede.jpg?s=120&d=mm&r=g)
On Jul 27, 2005, at 5:01 PM, Mark Sapiro wrote:
Greetings All,
Like the OP, I was searching for an "unsubscribe without
confirmation" solution for a single list (out of a dozen or so), when
I ran across Mark's patch from July of this year. I'm still low on
mailman's learning curve and python isn't my strong point. So I have
a quick question.
The environment is Mac OS X 10.4.3 client, Postfix 2.2.5, Mailman 2.1.6
If I interpreted the patch and cmd_unsubscribe.py correctly, this
patch affects the entire Mailman installation, correct?
Since most of the other lists are used for press releases for our
clients, I could live with this "feature". I have bounce processing
set to 1.0 to disable subscriptions quickly for bad addresses.
In short, just a newbie, asking if there is water below before
jumping off the cliff. <grin>
Jeff Stubbs
IT Support Altman-Hall Advertising 235 West Seventh Street Erie, PA 16501 PH - 814.454.0158 FX - 814.454.3266
![](https://secure.gravatar.com/avatar/746f7519ba02fb0d815e59f305c53fa2.jpg?s=120&d=mm&r=g)
Jeff Stubbs wrote:
Correct. It only affects unsubscribe by email, but it affects email unsubscribes for the entire installation.
It would be pretty easy to modify the patch to test some list attribute (a locally defined one set by withlist) to determine whether or not to skip the things that the patch deletes.
Also, one could instead patch the ConfirmUnsubscription method in Mailman/MailList.py if one wanted to skip confirmations of unsubscribes from all sources (conditionally by list or not).
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/746f7519ba02fb0d815e59f305c53fa2.jpg?s=120&d=mm&r=g)
Sintz, James wrote:
I understand the purpose of the confirmation, I just want the ability to turn it off. It is okay if users get unsubscribed from my list because of a spooked request.
If you really want to do it, I think the attached patch will allow it.
Warning - this is untested, use at your own risk.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/5ada79a8a91b40e8c35ddd9e412beede.jpg?s=120&d=mm&r=g)
On Jul 27, 2005, at 5:01 PM, Mark Sapiro wrote:
Greetings All,
Like the OP, I was searching for an "unsubscribe without
confirmation" solution for a single list (out of a dozen or so), when
I ran across Mark's patch from July of this year. I'm still low on
mailman's learning curve and python isn't my strong point. So I have
a quick question.
The environment is Mac OS X 10.4.3 client, Postfix 2.2.5, Mailman 2.1.6
If I interpreted the patch and cmd_unsubscribe.py correctly, this
patch affects the entire Mailman installation, correct?
Since most of the other lists are used for press releases for our
clients, I could live with this "feature". I have bounce processing
set to 1.0 to disable subscriptions quickly for bad addresses.
In short, just a newbie, asking if there is water below before
jumping off the cliff. <grin>
Jeff Stubbs
IT Support Altman-Hall Advertising 235 West Seventh Street Erie, PA 16501 PH - 814.454.0158 FX - 814.454.3266
![](https://secure.gravatar.com/avatar/746f7519ba02fb0d815e59f305c53fa2.jpg?s=120&d=mm&r=g)
Jeff Stubbs wrote:
Correct. It only affects unsubscribe by email, but it affects email unsubscribes for the entire installation.
It would be pretty easy to modify the patch to test some list attribute (a locally defined one set by withlist) to determine whether or not to skip the things that the patch deletes.
Also, one could instead patch the ConfirmUnsubscription method in Mailman/MailList.py if one wanted to skip confirmations of unsubscribes from all sources (conditionally by list or not).
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Mark Sapiro
-
Sintz, James
-
Stubbs Jeff