Re: [Mailman-Users] Downgrade options/alternatives
Hello Mark, Thank you for the information/confirmation. Knowing that the only thing left to do is to update the file on the last mailman version makes me feel more confident that all functional pieces were successfully rolled back. And that will make me feel better about upgrading soon. I have checked the update script but I get some errors when trying to run the bin/update --force . I think this has to do with the import statements specified on the script. But I can say I do see the version I rolled back to through the web interface (which does appear to have rolled back successfully). Thank you $ bin/update --help Traceback (most recent call last): File "bin/update", line 46, in import paths ImportError: No module named paths >Actually, you did do the downgrade. Only the final running of Mailman's >bin/upgrade did not succeed. You can run it with the -f or --force >option to make it succeed, but it won't do anything anyway except maybe >update Mailman's data/last_mailman_version. See 'bin/upgrade --help'. -Original Message- From: Mailman-Users [mailto:mailman-users-bounces+vxmr=pge@python.org] On Behalf Of Mark Sapiro Sent: Thursday, November 12, 2015 12:01 PM To: mailman-users@python.org Subject: Re: [Mailman-Users] Downgrade options/alternatives On 11/12/15 10:14 AM, Montanez, Victor wrote: > > Hello, > > I have done a successful upgrade from Mailman version 2.1.16 to 2.1.20 > successfully. I am now testing the downgrade (In case some issue comes up and > I have to rollback) and it seemed to have gone okay for the most part. > > At the of the end of the downgrade I get the following message(which I have > googled around but no real alternative given). > > > Downgrade detected, from version 0x20114f0 to version 0x20110f0 > > This is probably not safe. > > Exiting. > > make: *** [update] Error 1 > > > > I understand is a downgrade, that is what I want to do. But it looks like > "downgrading" isn't really supported in Mailman. What is a recommended > alternative for having a way to go back to previous Mailman version? Actually, you did do the downgrade. Only the final running of Mailman's bin/upgrade did not succeed. You can run it with the -f or --force option to make it succeed, but it won't do anything anyway except maybe update Mailman's data/last_mailman_version. See 'bin/upgrade --help'. -- Mark Sapiro <m...@msapiro.net>The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org -- 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/archive%40jab.org
Re: [Mailman-Users] Downgrade options/alternatives
Ah got it. Thank you. I was looking on the wrong location, using the wrong "update" script. I ran it and it updated properly. Thank you -Original Message- From: Mark Sapiro [mailto:m...@msapiro.net] Sent: Friday, November 13, 2015 9:02 AM To: Montanez, Victor; mailman-users@python.org Subject: Re: [Mailman-Users] Downgrade options/alternatives On 11/12/15 1:28 PM, Montanez, Victor wrote: > > I have checked the update script but I get some errors when trying to run the > bin/update --force . I think this has to do with the import statements > specified on the script. But I can say I do see the version I rolled back to > through the web interface (which does appear to have rolled back > successfully). > > Thank you > > $ bin/update --help > Traceback (most recent call last): > File "bin/update", line 46, in > import paths > ImportError: No module named paths This is very strange. There must be a https://urldefense.proofpoint.com/v2/url?u=http-3A__paths.py=BQIC-g=hLS_V_MyRCwXDjNCFvC1XhVzdhW2dOtrP9xQj43rEYI=CNBJ5WQxVRyGeDTLL7hLtA=wvZdR3Nfu5vXQHaIJcr6TuCU3HyNyUUPmHSryKuhFXQ=AscK60oiU0TF9Sl8VpEEnuzis07VcF3zmfm6YFLM26U= module in Mailman's bin/ directory or pretty much non of Mailman's bin/ commands will run. Possibly the user you ran it as does not have permission to read bin/paths.py. -- Mark Sapiro <m...@msapiro.net>The highway is for gamblers, San Francisco Bay Area, Californiabetter 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/archive%40jab.org
[Mailman-Users] Downgrade options/alternatives
Hello, I have done a successful upgrade from Mailman version 2.1.16 to 2.1.20 successfully. I am now testing the downgrade (In case some issue comes up and I have to rollback) and it seemed to have gone okay for the most part. At the of the end of the downgrade I get the following message(which I have googled around but no real alternative given). Error: Compiling i18n.py ... Compiling versions.py ... Downgrade detected, from version 0x20114f0 to version 0x20110f0 This is probably not safe. Exiting. make: *** [update] Error 1 I understand is a downgrade, that is what I want to do. But it looks like "downgrading" isn't really supported in Mailman. What is a recommended alternative for having a way to go back to previous Mailman version? Thank you -- 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/archive%40jab.org
[Mailman-Users] Is there a way to create multiple lists at once via mailman script?
Hello, I am wondering if there is a way to have several mailman lists created at once via command line. I am talking about 100 lists or so. Otherwise creating them through the GUI would take forever. Maybe creating a file with list name, password,etc and passing that file to the create binary? Anyone have any experience with that? Thanks in advance Victor Montañez -- 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/archive%40jab.org
[Mailman-Users] Mailman 2.1.2 unsubscribe without confirmation action
Can the list owners send a command via email to unsubscribe users of a list that will NOT cause a confirmation email to be generated to the subscribers? We want to send an email to mailman to remove subscribers without requiring confirmation from the subscribed users. All settings I have tried still generate a confirmation email and subscriber interaction is required. Thanks in advance -- 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/archive%40jab.org
Re: [Mailman-Users] Mailman 2.1.2 unsubscribe without confirmation action
Hello Mark, For the possible alternative you mention below: If we do set up the unsubscribe policy to "yes" and in the "unsubscribe MODERATORPASSWD address=user@example" command we include the moderator/owner password would that accomplish the removal of the user without confirmation? * A possible alternative is to set the list's Privacy options... -> Subscription rules -> unsubscribe_policy to yes and send unsubscribe address=u...@example.com to the list's -request address. This will result in the unsubscribe (all unsubscribes) being held for admin approval, but the admin can't approve the held unsubscribe by email, so tha probably won't help. *** -Original Message- From: Mailman-Users [mailto:mailman-users-bounces+vxmr=pge@python.org] On Behalf Of Mark Sapiro Sent: Friday, July 15, 2016 10:56 AM To: mailman-users@python.org Subject: Re: [Mailman-Users] Mailman 2.1.2 unsubscribe without confirmation action This is an EXTERNAL EMAIL. Stop and think before clicking links or opening attachments. * On 07/15/2016 09:34 AM, Montanez, Victor wrote: > Can the list owners send a command via email to unsubscribe users of a > list that will NOT cause a confirmation email to be generated to the > subscribers? Only if the admin knows the user's list password. If so, the admin can send the command unsubscribe users_password address=u...@example.com to the list's -request address, but it must be the user's list password. No other password will work. A possible alternative is to set the list's Privacy options... -> Subscription rules -> unsubscribe_policy to yes and send unsubscribe address=u...@example.com to the list's -request address. This will result in the unsubscribe (all unsubscribes) being held for admin approval, but the admin can't approve the held unsubscribe by email, so tha probably won't help. > We want to send an email to mailman to remove subscribers without > requiring confirmation from the subscribed users. All settings I have > tried still generate a confirmation email and subscriber interaction > is required. You could consider patching Mailman/Commands/cmd_unsubscribe.py to accept the list admin password or some other secret as an alternate to the user's password. I think that's the only way. -- Mark Sapiro <m...@msapiro.net>The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.python.org_mailman_listinfo_mailman-2Dusers=CwICAg=hLS_V_MyRCwXDjNCFvC1XhVzdhW2dOtrP9xQj43rEYI=CNBJ5WQxVRyGeDTLL7hLtA=S71mkh92Tx-4_18SmPaB3jGVR259jGrWUejyLX2YJog=AubQGks4ZJkjdlyBIYqG4nLXuMXQcG7k8pCkHT4kf3M= Mailman FAQ: https://urldefense.proofpoint.com/v2/url?u=http-3A__wiki.list.org_x_AgA3=CwICAg=hLS_V_MyRCwXDjNCFvC1XhVzdhW2dOtrP9xQj43rEYI=CNBJ5WQxVRyGeDTLL7hLtA=S71mkh92Tx-4_18SmPaB3jGVR259jGrWUejyLX2YJog=-9PsRNCXE-lpFiSN5nauFUClTOMrDOxFfjn6soHHCo4= Security Policy: https://urldefense.proofpoint.com/v2/url?u=http-3A__wiki.list.org_x_QIA9=CwICAg=hLS_V_MyRCwXDjNCFvC1XhVzdhW2dOtrP9xQj43rEYI=CNBJ5WQxVRyGeDTLL7hLtA=S71mkh92Tx-4_18SmPaB3jGVR259jGrWUejyLX2YJog=pms8W_zjLSJyKbyvxovKZ-i6g8aajS3ZyPz6AiZRE5c= Searchable Archives: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.mail-2Darchive.com_mailman-2Dusers-2540python.org_=CwICAg=hLS_V_MyRCwXDjNCFvC1XhVzdhW2dOtrP9xQj43rEYI=CNBJ5WQxVRyGeDTLL7hLtA=S71mkh92Tx-4_18SmPaB3jGVR259jGrWUejyLX2YJog=L0ghPUhHtLQiGgA9nMI9gC2O0J_VmJR1alZO-gJ_vEo= Unsubscribe: https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.python.org_mailman_options_mailman-2Dusers_vxmr-2540pge.com=CwICAg=hLS_V_MyRCwXDjNCFvC1XhVzdhW2dOtrP9xQj43rEYI=CNBJ5WQxVRyGeDTLL7hLtA=S71mkh92Tx-4_18SmPaB3jGVR259jGrWUejyLX2YJog=dzAvYA05U9p7gK5ayq91KnbwWOwUdybtZcJreMbNt5E= -- 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/archive%40jab.org
Re: [Mailman-Users] Mailman 2.1.2 unsubscribe without confirmation action
Thank you for the confirmation Mark. -Original Message- From: Mark Sapiro [mailto:m...@msapiro.net] Sent: Friday, July 15, 2016 2:41 PM To: Montanez, Victor; mailman-users@python.org Subject: Re: [Mailman-Users] Mailman 2.1.2 unsubscribe without confirmation action This is an EXTERNAL EMAIL. Stop and think before clicking links or opening attachments. * On 07/15/2016 11:08 AM, Montanez, Victor wrote: > Hello Mark, > > For the possible alternative you mention below: > > If we do set up the unsubscribe policy to "yes" and in the "unsubscribe > MODERATORPASSWD address=user@example" command we include the moderator/owner > password would that accomplish the removal of the user without confirmation? No. The only password that has any meaning in that command is the user's list password. -- Mark Sapiro <m...@msapiro.net>The highway is for gamblers, San Francisco Bay Area, Californiabetter 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/archive%40jab.org
[Mailman-Users] Is there an option to allow open Unsubscriptions
Is there a way to allow users to unsubscribe themselves without having to respond to the unsubscribe confirmation email? -- 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/archive%40jab.org
