upgrading from version 2.1.9 to latest available version
I realized today that the unsubscribe via web page feature of version 2.1.9 is not working for my list. Maybe it is a known bug or something that just doesn't work for my site due to previous upgrades.
The list is very low volume so upgrading it has not been a priority. I would like to understand how much effort is involved in upgrading from version 2.1.9 to the latest available.
I am running fedora 5 if that matters.
Thank you. Chad
Chad Rebuck wrote:
I realized today that the unsubscribe via web page feature of version 2.1.9 is not working for my list. Maybe it is a known bug or something that just doesn't work for my site due to previous upgrades.
In what way does it not work? Are you talking about the unsubscribe check box on the list admin Membership List page or the unsubscribe from the user options login page or the unsubscribe from the user options page after login?
What happens when you try to do it?
The list is very low volume so upgrading it has not been a priority. I would like to understand how much effort is involved in upgrading from version 2.1.9 to the latest available.
I am running fedora 5 if that matters.
If you installed 2.1.9 from RPM, it is rather intricate to upgrade to a non-RedHat RPM version because of RedHat's modifications to support FHS.
An RPM upgrade should be very simple if there is a post 2.1.9 fedora RPM.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark, thanks for the reply
it does appear mailman was installed by rpm. if there is no rpm available to upgrade would it be difficult to upgrade to 2.1.13 or should I go to 3.something? I found the pages a little confusing on what the latest version really is. What version would be recommended to upgrade to?
details on the inability to unsubscribe:
the unsubscribe using the checkbox on the admin page does work.
the unsubscribe via email does work as well.
It is the unsubscribe on this page that does not work
http://mail.a2-16v.com/mailman/listinfo/a2-16v-list
<http://mail.a2-16v.com/mailman/listinfo/a2-16v-list>For a test I registered a new email then tried to unsubscribe using this page above. I would receive an email with subject of "mailman privacy alert" and a body such as, "an attempt was made to subscribe your address to the mailing list .... you are already subscribed to the list."
Feel free to attempt to duplicate the trouble by subscribing to the list and trying to unsubscribe using this method.
On Thu, Jul 22, 2010 at 10:58 PM, Mark Sapiro <mark@msapiro.net> wrote:
Chad Rebuck wrote:
I realized today that the unsubscribe via web page feature of version 2.1.9 is nhttp://mail.a2-16v.com/mailman/listinfo/a2-16v-listot working for my list. Maybe it is a known bug or something that just doesn't work for my site due to previous upgrades.
In what way does it not work? Are you talking about the unsubscribe check box on the list admin Membership List page or the unsubscribe from the user options login page or the unsubscribe from the user options page after login?
What happens when you try to do it?
The list is very low volume so upgrading it has not been a priority. I would like to understand how much effort is involved in upgrading from version 2.1.9 to the latest available.
I am running fedora 5 if that matters.
If you installed 2.1.9 from RPM, it is rather intricate to upgrade to a non-RedHat RPM version because of RedHat's modifications to support FHS.
An RPM upgrade should be very simple if there is a post 2.1.9 fedora RPM.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Chad Rebuck wrote:
it does appear mailman was installed by rpm. if there is no rpm available to upgrade would it be difficult to upgrade to 2.1.13 or should I go to 3.something? I found the pages a little confusing on what the latest version really is. What version would be recommended to upgrade to?
MM 3 is still in alpha exposure. It is not ready to be run in production, and I think, there is not yet a clear migration path for MM 2.1 lists.
The latest released version to upgrade to is 2.1.13 although there will be a 2.1.14 release currently targeted for late Sept.
In order to update a RedHat RPM release from source, there are three possible paths.
Path 1 is to modify the patch at <http://mail.python.org/pipermail/mailman-developers/2004-October/017343.html> for the current source release, and then run configure with the appropriate path locations to match your current RPM installation.
Path 2 is to install Mailman from source as a separate installation in a non-conflicting location, and then move your lists and archives from the old installation to the new.
Path 3 is to configure Mailman with --prefix=/usr/lib/mailman and --with-var-prefix=/var/lib/mailman which may more or less work.
If you have SELinux enabled, both paths 2 and 3 will create SELinux issues.
However, I think upgrading will not affect the following issue which appears to be a misedited listinfo.html template for the list.
details on the inability to unsubscribe:
the unsubscribe using the checkbox on the admin page does work.
Good.
the unsubscribe via email does work as well.
Good.
It is the unsubscribe on this page that does not work
http://mail.a2-16v.com/mailman/listinfo/a2-16v-list
For a test I registered a new email then tried to unsubscribe using this page above. I would receive an email with subject of "mailman privacy alert" and a body such as, "an attempt was made to subscribe your address to the mailing list .... you are already subscribed to the list."
Someone has edited the listinfo page template for this list and broken it. It looks like the portion of this template at the end, which in the base template is
<MM-Options-Form-Start>
<MM-Editing-Options>
<MM-Form-End>
</td>
</tr></table> <MM-Mailman-Footer> </BODY> </HTML>
Has been changed and "<MM-Options-Form-Start>" has been replaced by "<MM-Subscribe-Form-Start>".
I can't tell for sure what the change was as I only see the page generated from the template and not the template itself, but it is something along these lines.
Go to the list admin interface and follow the "Edit the public HTML pages and text files" link and then the "General list information page" link and you will see and be able to fix the template.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thank you very much for the reply about upgrade options. The suggested fix for the unsubscribe issue worked perfectly.
Chad
On Fri, Jul 23, 2010 at 11:38 AM, Mark Sapiro <mark@msapiro.net> wrote:
Chad Rebuck wrote:
it does appear mailman was installed by rpm. if there is no rpm available to upgrade would it be difficult to upgrade to 2.1.13 or should I go to 3.something? I found the pages a little confusing on what the latest version really is. What version would be recommended to upgrade to?
MM 3 is still in alpha exposure. It is not ready to be run in production, and I think, there is not yet a clear migration path for MM 2.1 lists.
The latest released version to upgrade to is 2.1.13 although there will be a 2.1.14 release currently targeted for late Sept.
In order to update a RedHat RPM release from source, there are three possible paths.
Path 1 is to modify the patch at < http://mail.python.org/pipermail/mailman-developers/2004-October/017343.html
for the current source release, and then run configure with the appropriate path locations to match your current RPM installation.
Path 2 is to install Mailman from source as a separate installation in a non-conflicting location, and then move your lists and archives from the old installation to the new.
Path 3 is to configure Mailman with --prefix=/usr/lib/mailman and --with-var-prefix=/var/lib/mailman which may more or less work.
If you have SELinux enabled, both paths 2 and 3 will create SELinux issues.
However, I think upgrading will not affect the following issue which appears to be a misedited listinfo.html template for the list.
details on the inability to unsubscribe:
the unsubscribe using the checkbox on the admin page does work.
Good.
the unsubscribe via email does work as well.
Good.
It is the unsubscribe on this page that does not work
http://mail.a2-16v.com/mailman/listinfo/a2-16v-list
For a test I registered a new email then tried to unsubscribe using this page above. I would receive an email with subject of "mailman privacy alert" and a body such as, "an attempt was made to subscribe your address to the mailing list .... you are already subscribed to the list."
Someone has edited the listinfo page template for this list and broken it. It looks like the portion of this template at the end, which in the base template is
<MM-Options-Form-Start> <MM-Editing-Options> <MM-Form-End> </td></tr> </table> <MM-Mailman-Footer> </BODY> </HTML>
Has been changed and "<MM-Options-Form-Start>" has been replaced by "<MM-Subscribe-Form-Start>".
I can't tell for sure what the change was as I only see the page generated from the template and not the template itself, but it is something along these lines.
Go to the list admin interface and follow the "Edit the public HTML pages and text files" link and then the "General list information page" link and you will see and be able to fix the template.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Chad Rebuck -
Mark Sapiro