[Mailman-Users] Upgrading mailman from 2 to 3 and private archives

So looking to migrate to mailman3 from mailman2, so for archives I see the notes below stated on the website. So just making sure I understand correctly. Private and Public archives will migrate over, however links to the messages will change. If they are public archives you can make them avail

[Mailman-Users] Upgrading to mailman3 maybe?

So looking at upgrading to mailman 3 but had some questions. Background: we use mailman as email distribution lists, not really for back and forth communication, so having said that… * Does mailman3 have a way to automatically prune archives, i.e. delete old archived messaged that are X day

[Mailman-Users] Upgrading from 2.1.12

Good Day We have a running 2.1.12 installation that was done long ago via an external consultant. It hasn't been changed in years, but I would like to upgrade this to at least the latest 2.x version and potentially 3.x. We would also like to migrate this from the current Centos VM to an Ubuntu EC2

Re: [Mailman-Users] Upgrading Mailman from Centos package...

On Feb 13, 2020, at 2:10 PM, Mark Sapiro mailto:m...@msapiro.net>> wrote: On 2/13/20 12:34 PM, Bruce Johnson wrote: Probably a dumb question, but, this should also be the process to update MM from a RHEL/CentOS package to a later version from source? https://wiki.list.org/DOC/4.80%20How%20do%

Re: [Mailman-Users] Upgrading Mailman from Centos package...

On 2/13/20 12:34 PM, Bruce Johnson wrote: > Probably a dumb question, but, this should also be the process to update MM > from a RHEL/CentOS package to a later version from source? > > https://wiki.list.org/DOC/4.80%20How%20do%20I%20upgrade%20from%20Mailman%202.1.x%20to%20a%20later%20Mailman%202.

[Mailman-Users] Upgrading Mailman from Centos package...

Probably a dumb question, but, this should also be the process to update MM from a RHEL/CentOS package to a later version from source? https://wiki.list.org/DOC/4.80%20How%20do%20I%20upgrade%20from%20Mailman%202.1.x%20to%20a%20later%20Mailman%202.1.y%3F I've checked this: https://wiki.list.org/

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, 2019-05-23 at 09:40 -0400, Fabian A. Santiago wrote: > also, that wiki page you sent me mention an error with missing dnspython > and it states to run this: > > "sudo apt-get install python-dnspython" > > but that claims it's already instal

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, 2019-05-23 at 09:04 -0400, Fabian A. Santiago wrote: > > Thanks for this heads up. i should also mention adding the ppa to my apt > sources fails on gpg signing key import. i had to do it manually, > searching for the key on ubuntu's keyserv

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2019-05-22 at 08:42 -0700, Mark Sapiro wrote: > On 5/21/19 5:20 PM, Fabian Aldo Santiago wrote: > > > > So I started over (restored snapshot) and then tried adding a ppa apt > > source which contains 2.1.29: > > > > https://launchpad.net/~

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

> It probably is permissions on the logs and others. Have you run > check_perms. If not run `check_perms -f` as root. Don't worry about > symlinks, they don't matter. that did it, finally! check_perms -f. thanks for your help. finally on 2.1.29 now. all seems to be working now. -- Fabian S.

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

On 5/23/19 10:41 AM, Fabian A. Santiago wrote: > On 5/23/19 1:29 PM, Fabian A. Santiago wrote: >> On 5/23/19 12:11 PM, Mark Sapiro wrote: >>> >>> What's in Mailman's error log? >>> >>> >> nothing. It probably is permissions on the logs and others. Have you run check_perms. If not run `check_perms

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

On 5/23/19 1:29 PM, Fabian A. Santiago wrote: > On 5/23/19 12:11 PM, Mark Sapiro wrote: >> On 5/23/19 8:50 AM, Fabian Aldo Santiago wrote: >>> Ok making progress. Service started now but the www UI reports: >>> >>> Bug in Mailman version 2.1.29 >>> >>> >>> >>> We're sorry, we hit a bug! >>> >>> Ple

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

On 5/23/19 12:11 PM, Mark Sapiro wrote: > On 5/23/19 8:50 AM, Fabian Aldo Santiago wrote: >> Ok making progress. Service started now but the www UI reports: >> >> Bug in Mailman version 2.1.29 >> >> >> >> We're sorry, we hit a bug! >> >> Please inform the webmaster for this site of this problem. Pr

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

On 5/23/19 8:50 AM, Fabian Aldo Santiago wrote: > Ok making progress. Service started now but the www UI reports: > > Bug in Mailman version 2.1.29 > > > > We're sorry, we hit a bug! > > Please inform the webmaster for this site of this problem. Printing of > traceback and other system inform

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

Ok making progress. Service started now but the www UI reports: Bug in Mailman version 2.1.29 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find thi

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

On 5/23/19 8:07 AM, Fabian Aldo Santiago wrote: > Service file: > > [Unit] > Description=Mailman Master Queue Runner > After=network.target > > [Service] > Type=forking > PIDFile=/var/run/mailman/mailman.pid You could try PIDFile=/var/lib/mailman/data/master-qrunner.pid which is where mailmanc

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

Service file: [Unit] Description=Mailman Master Queue Runner After=network.target [Service] Type=forking PIDFile=/var/run/mailman/mailman.pid ExecStart=/usr/lib/mailman/bin/mailmanctl -s start ExecStop=/usr/lib/mailman/bin/mailmanctl stop ExecReload=/usr/lib/mailman/bin/mailmanctl restart Restart

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

On 5/23/19 7:02 AM, Fabian A. Santiago wrote: > > ok, the issue occurred again with the same error. the complaint is (from > systemctl status ... -l): > > May 23 09:44:40 mail systemd[1]: mailman.service: Can't open PID file > /var/run/mailman/mailman. > > journalctl -xe reports: > > May 23 09:

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

On 5/23/19 9:04 AM, Fabian A. Santiago wrote: > On 5/22/19 11:42 AM, Mark Sapiro wrote: > >> >> Did you look at ? >> >> What was the exact complaint. It's probably easy to fix. > > Thank you Mark for this reference. I did not look at it. I also didn't > record th

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

also, that wiki page you sent me mention an error with missing dnspython and it states to run this: "sudo apt-get install python-dnspython" but that claims it's already installed, yet the error occurs. what i found you want to install is the package "python-dev". -- Fabian S. OpenPGP: 0xA125

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

On 5/22/19 11:42 AM, Mark Sapiro wrote: > > Did you look at ? > > What was the exact complaint. It's probably easy to fix. Thank you Mark for this reference. I did not look at it. I also didn't record the error. i needed this server / list back up asap so i sna

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

On 5/21/19 5:20 PM, Fabian Aldo Santiago wrote: > Hello all, > > I have my postfix mail server running mm 2.1.26 installed via apt on Ubuntu > 18.04. I wish to upgrade to 2.1.29 but it’s not in the official repos. > > I tried installing from source, after first running mailman-config to gather

[Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

Hello all, I have my postfix mail server running mm 2.1.26 installed via apt on Ubuntu 18.04. I wish to upgrade to 2.1.29 but it’s not in the official repos. I tried installing from source, after first running mailman-config to gather the configure parameters (thanks Lindsay!). It installed no

Re: [Mailman-Users] upgrading mailman

On 05/04/2015 05:48 AM, Mark wrote: > Hi my linode needs upgrading and i have been told if i upgrade it will > break my mailman does any one know if this right It probably depends on exactly how you installed Mailman (package, source, ??) and if you have any patches to your Mailman. If you do

[Mailman-Users] upgrading mailman

Hi my linode needs upgrading and i have been told if i upgrade it will break my mailman does any one know if this right mark. -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman

[Mailman-Users] Upgrading to MM3

Hi, I have a list using MM2 and I'm wondering, if I started using MM3, would I be able to just plug in the same database that I'm using with MM2? Or would I have to do anything different to keep the archives? Thanks! Ana -- Mailman-Users mailin

Re: [Mailman-Users] Upgrading/migrating Mailman v2.1.9 -> v2.1.18-1

On 01/14/2015 09:50 PM, Chris Nulk wrote: > On Wed, Jan 14, 2015 at 7:03 PM, Mark Sapiro wrote: >> >> in 2.1.18-1, DATA_FILE_VERSION is already 104. The only reason to >> increment DATA_FILE_VERSION is so versions.Update() will run when an >> older list in first instantiated. Since your changes we

Re: [Mailman-Users] Upgrading/migrating Mailman v2.1.9 -> v2.1.18-1

On Wed, Jan 14, 2015 at 7:03 PM, Mark Sapiro wrote: > On 01/14/2015 09:31 AM, Chris Nulk wrote: > > > > ​..​ > > LDAPMemberships.py is not part of GNU Mailman. I think the latest > version is yours, but in any case you can continue to use whatever > you're using. > ​Yeah, I know. That lis

Re: [Mailman-Users] Upgrading/migrating Mailman v2.1.9 -> v2.1.18-1

On 01/14/2015 09:31 AM, Chris Nulk wrote: > > Below is a list of the files I have modified (base directory is > /usr/lib/mailman). Should I pay special attention due to changes to any > particular files? > > bin/add_members > bin/non_members > Mailman/LDAPMemberships.py > Mailman/ListAdmin.py >

Re: [Mailman-Users] Upgrading/migrating Mailman v2.1.9 -> v2.1.18-1

On 1/14/2015 7:57 AM, Mark Sapiro wrote: Thanks for your help Mark. On 01/13/2015 09:04 PM, Chris Nulk wrote: Are there any issues I should watch for using the following process? ... Does the process seem reasonable and workable? It looks OK to me. Great. The question about customization

Re: [Mailman-Users] Upgrading/migrating Mailman v2.1.9 -> v2.1.18-1

On 01/13/2015 09:04 PM, Chris Nulk wrote: > > Are there any issues I should watch for using the following process? ... > Does the process seem reasonable and workable? It looks OK to me. > The next issue that I have to mix in are customizations to Mailman. I plan > on adding the customization

[Mailman-Users] Upgrading/migrating Mailman v2.1.9 -> v2.1.18-1

Hello all, I will be upgrading/migrating from a v2.1.9 Mailman installation to a v2.1.18-1 Mailman installation. In addition, I will be upgrading the hardware and will be keeping the name of the system the same. I have a few questions if anyone can help. I will be keeping the current installati

Re: [Mailman-Users] Upgrading and using with multiple domains

> Date: Thu, 27 Nov 2014 12:06:46 -0800 > From: m...@msapiro.net >> Is there anything else I ought to do? > > > Yes. Completely uninstall the a.com/mailman instance including any cron > jobs that run a.com/mailman/cron.* scripts. > > >> Will having installed Mailman twice have caused any confusion/

Re: [Mailman-Users] Upgrading and using with multiple domains

On 11/27/2014 02:39 AM, Jon 1234 wrote: >> Date: Wed, 26 Nov 2014 21:01:36 -0800 >> From: m...@msapiro.net ... >> >> What exactly is the situation in your case? > > At the very beginning I wrongly installed the files in a.com/mailman > > So the aliases are: > > ScriptAlias /mailman/ /path/a_com

Re: [Mailman-Users] Upgrading and using with multiple domains

> Date: Wed, 26 Nov 2014 21:01:36 -0800 > From: m...@msapiro.net > >> I currently have Mailman 2.1.14 installed in the website directory of a.com > > > What does this mean? Normally, Mailman is installed in it's own > directory or directories which are not in the space served by default by > the

Re: [Mailman-Users] Upgrading and using with multiple domains

On 11/26/2014 08:05 AM, Jon 1234 wrote: > I currently have Mailman 2.1.14 installed in the website directory of a.com What does this mean? Normally, Mailman is installed in it's own directory or directories which are not in the space served by default by the web server. Then Mailman's CGI wrapper

[Mailman-Users] Upgrading and using with multiple domains

I currently have Mailman 2.1.14 installed in the website directory of a.com I would like to: 1. Upgrade it to 2.1.18-1.2. Have it outside the website directory.3. Use it not only for a.com but also b.com (I will not need to have the same list names for both domains). If I were to install from scr

Re: [Mailman-Users] upgrading Mailman.

Michael Capelle wrote: >I need to add, we are not using 5.0.4, we are using 5.0.8. Is there any >dependencies we need to download? >we have 2.1.11, and we want to upgrade to 2.1.15, we are using debian 5.0.8. I believe Mailman 2.1.11 (1:2.1.11-11+lenny1) is the latest Debian packaged release

Re: [Mailman-Users] upgrading Mailman.

1 11:29 AM Subject: [Mailman-Users] upgrading Mailman. Hello. I am trying to upgrade mailman, I am using Debian 5-04. I have mailman version 2.1.11. Do i need to use a dependency to update? thanks. Mike. -- Mailman-Users mailing list Mai

[Mailman-Users] upgrading Mailman.

Hello. I am trying to upgrade mailman, I am using Debian 5-04. I have mailman version 2.1.11. Do i need to use a dependency to update? thanks. Mike. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listi

Re: [Mailman-Users] Upgrading and converting mailman to postfix

On 4/20/11 7:59 PM, Steven Jones wrote: > Hi, > > I have to upgrade a old mailman setup on RHEl3 and sendmail to RHEL6 > which comes with postfix by default... > > So, > > a) Docs or how easy is it to straight migrate from RHEL3 (2.1.5) to > RHEL6 (2.1.12) ? This is a RedHat packaging questio

Re: [Mailman-Users] Upgrading and converting mailman to postfix

On Apr 20, 2011, at 9:59 PM, Steven Jones wrote: > a) Docs or how easy is it to straight migrate from RHEL3 (2.1.5) to RHEL6 > (2.1.12) ? What does Red Hat tell you about migrating from sendmail to postfix with RHEL3 -> RHEL6? In my experience, postfix goes pretty far out of its way to be as

[Mailman-Users] Upgrading and converting mailman to postfix

Hi, I have to upgrade a old mailman setup on RHEl3 and sendmail to RHEL6 which comes with postfix by default... So, a) Docs or how easy is it to straight migrate from RHEL3 (2.1.5) to RHEL6 (2.1.12) ? b) How easy is it to convert a sendmail setup with /etc/aliases to postfix? any automat

Re: [Mailman-Users] upgrading list and other data from 2.1.9to2.1.14

Ivan Fetch wrote: > >I was planning to sync qfiles also (now that you mention it). Looking >at our current qfiles, some of them have files which look like they should >be deleted: > >Bounces: 260 (all .bak, but one .tmp) There was a bug in 2.1.9 that would leave the .bak file behind when th

Re: [Mailman-Users] upgrading list and other data from 2.1.9 to2.1.14

Hello, On Thu, 3 Feb 2011, Mark Sapiro wrote: That is correct, but there may be timing issues. Are you changing DNS or physically reassigning the IP address to the new box. If you're changing DNS, I'd start now and give all the relevant DNS entries a 5 minute or less TTL, so you don't have to

Re: [Mailman-Users] upgrading list and other data from 2.1.9 to2.1.14

Ivan Fetch wrote: > >When this box goes production, I want to refresh the lists, archives, >and data from the current 2.1.9 Mailman. All paths and host names will >stay the same. > >It sounds like there isn't anything I have to do after syncing the >lists, data, and archives directories.

Re: [Mailman-Users] upgrading list and other data from 2.1.9 to 2.1.14

Hello, thanks for your reply, On Thu, 3 Feb 2011, Mark Sapiro wrote: Ivan Fetch wrote: Is it possible to copy list and archives data from a 2.1.9 Mailman installation, to a 2.1.14 installation, and run bin/update to update data from 2.1.9 to 2.1.14? I assume bin/update will make any necess

Re: [Mailman-Users] upgrading list and other data from 2.1.9 to 2.1.14

Ivan Fetch wrote: > >Is it possible to copy list and archives data from a 2.1.9 Mailman >installation, to a 2.1.14 installation, and run bin/update to update data from >2.1.9 to 2.1.14? I assume bin/update will make any necessary changes to data >structures, from 2.1.9 to 2.1.14? > Yes and no.

[Mailman-Users] upgrading list and other data from 2.1.9 to 2.1.14

Hello, Is it possible to copy list and archives data from a 2.1.9 Mailman installation, to a 2.1.14 installation, and run bin/update to update data from 2.1.9 to 2.1.14? I assume bin/update will make any necessary changes to data structures, from 2.1.9 to 2.1.14? Here is why I am doing this:

Re: [Mailman-Users] upgrading from version 2.1.9 to latest availableversion

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 wrote: > Chad Rebuck wrote: > > > >it does appear mailman was installed by rpm. if there is no rpm available > >to upgrade

Re: [Mailman-Users] upgrading from version 2.1.9 to latest availableversion

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

Re: [Mailman-Users] upgrading from version 2.1.9 to latest availableversion

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

Re: [Mailman-Users] upgrading from version 2.1.9 to latest availableversion

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 che

[Mailman-Users] 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 understan

Re: [Mailman-Users] Upgrading Mailman on Mac Server 10.5.8 - Stuck!

Never mind. Mark already answered my question. I had forgotten I had asked it. My apologies. Paul -- Paul Kleeberg p...@fpen.org On Dec 16, 2009, at 3:19 PM, Paul Kleeberg wrote: > I am upgrading preinstalled versions of Mailman (first 2.1.9 => 2.1.12 on a > clean install of server 10.5.8

[Mailman-Users] Upgrading Mailman on Mac Server 10.5.8 - Stuck!

I am upgrading preinstalled versions of Mailman (first 2.1.9 => 2.1.12 on a clean install of server 10.5.8 as practice then I will do 2.1.12 rc1 => 2.1.12 in production on server 10.6.2) and I am running into a bunch of minor issues. I have made it through most of them but this one has me stuck

Re: [Mailman-Users] upgrading from 2.1.9 to 2.1.12

Troy Campbell wrote: >I'm considering upgrading from a current installation running >2.1.9 to a new server running 2.1.12. >Do I need to upgrade the 2.1.9 version on the existing server first? No. >I saw this note about 2.1.9 which I think I can safely ignore >but wondering if there are any oth

[Mailman-Users] upgrading from 2.1.9 to 2.1.12

I'm considering upgrading from a current installation running 2.1.9 to a new server running 2.1.12. Do I need to upgrade the 2.1.9 version on the existing server first? I saw this note about 2.1.9 which I think I can safely ignore but wondering if there are any other upgrade issues: http://wiki.li

Re: [Mailman-Users] Upgrading rpm mailman from mailman source

Paul wrote: >I tried yesterday unsuccessfully from upgrade mailman-2.1.5.1-34.rhel4.6 >on Centos 4 to the latest 2.1.11 from sourceforge. > >When I ran "configure" it said I needed to install Python from source or >install the Python-devel package, so I installed the python-devel. > ># yum -y inst

[Mailman-Users] Upgrading rpm mailman from mailman source

I tried yesterday unsuccessfully from upgrade mailman-2.1.5.1-34.rhel4.6 on Centos 4 to the latest 2.1.11 from sourceforge. When I ran "configure" it said I needed to install Python from source or install the Python-devel package, so I installed the python-devel. # yum -y install python-devel Th

Re: [Mailman-Users] Upgrading to new mailman version

wolf97 wrote: >I >would like to upgrade to a completely new box. Linux >Redhat Enterprise and the latest version of mailman >and postfix. Is there a way to export/import all my >existing list from the original server to the new one? See

[Mailman-Users] Upgrading to new mailman version

We are currently running all of our mailing lists on a Solaris 8 box, run mailman version 2.1/sendmail. I would like to upgrade to a completely new box. Linux Redhat Enterprise and the latest version of mailman and postfix. Is there a way to export/import all my existing list from the original s

[Mailman-Users] Upgrading and changing machines

I searched the archives, but only found this message: http://mail.python.org/pipermail/mailman-users/2004-March/035371.html which had no reply. We're upgrading from 2.0.11-1woody1 to 2.1.5-9ubuntu4.1, and changing boxes in the process. I've read the docs, but haven't found anything about upgrad

Re: [Mailman-Users] Upgrading from 2.1.5 to 2.1.9

Greg Earle wrote: > >I'm contemplating moving from 2.1.5 to 2.1.9 on a Red Hat Enterprise WS 3 >system. I built a custom 2.1.5 from a src RPM with the htDig stuff >added originally; on a system with no Mailman installed. Now of course >I have a running setup with a dozen or so lists, and am afrai

Re: [Mailman-Users] Upgrading from 2.1.5 to 2.1.9

On 11/8/06, Brad Knowles <[EMAIL PROTECTED]> wrote: > Of course, I actually used the FreeBSD port system to install Mailman > as opposed to installing from source, but the concept is the same. > And this is no guarantee that things will be this clean for you. The only added complication when insta

Re: [Mailman-Users] Upgrading from 2.1.5 to 2.1.9

At 3:55 PM -0700 11/8/06, Ivan Fetch wrote: > I'm wondering whether anyone has experience they'd like to share going > directly from 2.1.5 to 2.1.9 -- anything to be aware of in terms of the > upgrade process or user experiences (meaning list administrators and > members)? I recently did t

[Mailman-Users] Upgrading from 2.1.5 to 2.1.9

Hello, IT's (past) time to upgrade our mailman 2.1.5 installation to version 2.1.9. I'm wondering whether anyone has experience they'd like to share going directly from 2.1.5 to 2.1.9 -- anything to be aware of in terms of the upgrade process or user experiences (meaning list administ

Re: [Mailman-Users] Upgrading after crash

Jim Popovitch wrote: > Custom scripts in /usr/local/mailman/cron|cgi-bin| ? > Custom settings in mm_cfg.py? > Custom site html in /home/mailman/*/html/ > Queued files (bounces, etc) in /home/mailman/*/queue/* > > None of the above may apply, but that's my check list when upgrading. > Yup, no

Re: [Mailman-Users] Upgrading after crash

On Thu, 2006-09-28 at 14:06 -0600, Ashley M. Kirchner wrote: > > So, what did I forget? Custom scripts in /usr/local/mailman/cron|cgi-bin| ? Custom settings in mm_cfg.py? Custom site html in /home/mailman/*/html/ Queued files (bounces, etc) in /home/mailman/*/queue/* None of the above may

[Mailman-Users] Upgrading after crash

Our list server decided to take a dive yesterday so I spent the day rebuilding. So far everything seems to be working just peachy. However, I have this nagging feeling I'm forgetting something, so I thought I'd ask the experts. Maybe I did over look something, not sure... So after gett

Re: [Mailman-Users] upgrading to mm2.1.9?

Dave Stern wrote: >make install starts ok and ends ok but has one error: > >Creating architecture independent directories... >chmod o-r /fs/mailman2/archives/private > >for p in email-2.5.8 JapaneseCodecs-1.4.11 KoreanCodecs-2.0.5; \ >do \ > gunzip -c ./$p.tar.gz | (cd . ; tar xf -); \ >

Re: [Mailman-Users] upgrading to mm2.1.9?

At 2:48 PM -0700 2006-09-14, Mark Sapiro wrote: > This statement in HTMLFormatter.py and a couple of similar 'isinstance' > calls in htmlformat.py are part of the security changes in Mailman > 2.1.9. The problem is the use of str as the type argument requires > Python 2.3. FAQ 5.8 has been u

Re: [Mailman-Users] upgrading to mm2.1.9?

Dave Stern wrote: >On Thu, 14 Sep 2006, Dave Stern wrote: > >The last line of the tracedump was truncated in my initial message. >Here's the full text prior to the pythin (v2.1.2) and environment variables > >admin(1562): [- Mailman Version: 2.1.9 -] >admin(1562): [- Traceback --

Re: [Mailman-Users] upgrading to mm2.1.9?

On Thu, 14 Sep 2006, Dave Stern wrote: The last line of the tracedump was truncated in my initial message. Here's the full text prior to the pythin (v2.1.2) and environment variables admin(1562): [- Mailman Version: 2.1.9 -] admin(1562): [- Traceback --] admin(1562): Traceback

[Mailman-Users] upgrading to mm2.1.9?

Has anyone upgraded to 2.1.9 successfully? I tried upgrading as follows: ./configure with same params as my release. make install starts ok and ends ok but has one error: Creating architecture independent directories... chmod o-r /fs/mailman2/archives/private for p in email-2.5.8 JapaneseCo

Re: [Mailman-Users] upgrading, changing MTA and moving between servers

Kim Leandersson wrote: > >Ok, I'll copy the /lists/ directories to the new server. Then >how do i tell Mailman to create config.pck out of the config.db? Does >mailman do this without me telling it to do so, or do I have to run some >command or maybe access the web admin pages? The first time the

Re: [Mailman-Users] upgrading, changing MTA and moving between servers

Kim Leandersson sent the message below at 09:37 AM 8/26/2006: >Ok, I'll copy the /lists/ directories to the new server. Then >how do i tell Mailman to create config.pck out of the config.db? Does >mailman do this without me telling it to do so, or do I have to run some >command or maybe access the

Re: [Mailman-Users] upgrading, changing MTA and moving between servers

> > >2) just manually copy the lists/listname and archives > directories to the > >new server > > > This is the way to go. > > Caveats - Do not create the list on the new server before the > transfer. > If you do, you will create a lists/listname/config.pck and Mailman > will never see to lis

Re: [Mailman-Users] upgrading, changing MTA and moving between servers

Kim Leandersson wrote: > >I've read some pages telling me that the administrative addresses has >changed between these versions. I'm not sure if the best way is: > >1) to create the lists on the new server, use the config-list script to >export the config and the import this on the new server Not

[Mailman-Users] upgrading, changing MTA and moving between servers

Hi, For starters I have read the documentation available and done some googleing before this post. Today we have about 25-30 lists running on an old Debian Woody installation with postfix as MTA. Since the installation is old Mailman runs version 2.0.11. Our new server is running Qmail, Rhel4 and

Re: [Mailman-Users] upgrading from 2.1.5 -> 2.1.8

kristina clair wrote: > >In the UPGRADING file in the tarball for mailman 2.1.8, there are no >notes for upgrading to 2.1.8. Is that because there is nothing to >look out for? I'm upgrading from 2.1.5. There are no specific caveats for upgrading from 2.1.5 to a later release (through 2.1.8). Ba

[Mailman-Users] upgrading from 2.1.5 -> 2.1.8

Hi - just a quick question: In the UPGRADING file in the tarball for mailman 2.1.8, there are no notes for upgrading to 2.1.8. Is that because there is nothing to look out for? I'm upgrading from 2.1.5. Thanks! Kristina -- Mailman-Users mailin

Re: [Mailman-Users] upgrading Mailman 2.1.5 to 2.1.7 FC3

[EMAIL PROTECTED] wrote: >I have installed Mailman 2.1.5 on a Fedora core 3 box. I installed from >RPM. Tha last version for FC3 is 2.1.5, but I'd like to upgrade to 2.1.7. >Is there an easy way to do this? Anyone who have done this successfully? John Dennis from Red Hat often has things to say

[Mailman-Users] upgrading Mailman 2.1.5 to 2.1.7 FC3

I have installed Mailman 2.1.5 on a Fedora core 3 box. I installed from RPM. Tha last version for FC3 is 2.1.5, but I'd like to upgrade to 2.1.7. Is there an easy way to do this? Anyone who have done this successfully? -- Pål Monstad -- Mailman-U

[Mailman-Users] Upgrading - need info on old version

We are in the process of upgrading mailman and have to take some intermediate steps to get there without affecting our customers. I'd like to know if there is a way to configure mailman 1.0 so that any mail sent by mailman would look like it came from [EMAIL PROTECTED] instead of the current s

Re: [Mailman-Users] Upgrading to 2.1.6

At 2:52 PM -0500 2005-12-31, mcnutt wrote: > - Transcript of session follows - > sh: /usr/local/mailman/mail/wrapper: not found > 554 5.3.0 unknown mailer error 1 > > That's obviously coming from the old version of mailman, but I can't find > what I missed. Can anyone help me?

[Mailman-Users] Upgrading to 2.1.6

I've just upgraded my 2.0.x installation of mailman to 2.1.6, and I'm so close I can practically taste it. But it's still not working. When I send mail to a list on the server, I get back the following error: The original message was received at Sat, 31 Dec 2005 14:37:28 -0500 (EST) from utk-cls.

Re: [Mailman-Users] Upgrading Mailman (2.1.3 -> 2.1.6) - Q2

Odhiambo Washington wrote: >I have 2.1.3 running! And reading what Barry did here: > >http://www.mail-archive.com/mailman-developers@python.org/msg03127.html > >It would appear that I can simply install over my /path/to/mailman and >it wouldn't break much, no? ;) After you download and unpack the

[Mailman-Users] Upgrading Mailman (2.1.3 -> 2.1.6) - Q2

I have 2.1.3 running! And reading what Barry did here: http://www.mail-archive.com/mailman-developers@python.org/msg03127.html It would appear that I can simply install over my /path/to/mailman and it wouldn't break much, no? ;) cheers - wash +--+

[Mailman-Users] Upgrading Mailman (2.1.3 -> 2.1.6)

I know this has been discussed/documented, but I just can't find the actual link detailing the steps. Can someone point me to it? I have a production setup which I must not screw up with during the upgrade ;) cheers - wash +--+-

Re: [Mailman-Users] upgrading

Jardar Eggesbø Abrahamsen wrote: >As a new version of Mailman is approaching, I have a small question. This >will be my first upgrade, but the INSTALL and UPGRADING files that came >with 2.1.5 only say that "For the most part, upgrading Mailman is as easy >as just installing the latest version

[Mailman-Users] upgrading

As a new version of Mailman is approaching, I have a small question. This will be my first upgrade, but the INSTALL and UPGRADING files that came with 2.1.5 only say that "For the most part, upgrading Mailman is as easy as just installing the latest version over the existing version." So I was

[Mailman-Users] Upgrading mailman 1.0 and python 2.3.3

We are currently running Mailman 1.0 and python 1.5.2 In prep for upgrading Mailman 1.0, I will be upgrading python from 1.5.2 to version 2.3.3. Will Mailman 1.0 continue to run after I upgrade python to 2.3.3? Also, will Mailman 2.0.13 run OK under python 2.3.3? The docs on the Mailman web sit

[Mailman-Users] Upgrading and archives

I have been given the task to upgrade our mail server which is running Mailman 2.0.12 The existing server will be replaced with a completely rebuild box with the latest versions of Mailman and Postfix. I have no previous experience with Mailman so I have no idea how to move the current Mailman c

Re: [Mailman-Users] upgrading Panther Server basic install 2.1.2 to 2.1.5

Thanks Brad and Dan for your comments. Mailman has worked really well for me, but as someone coming to Panther Server and Mailman from running a webstar server, it is a big jump- a BIG change. Better docs to help the newbie/clueless would go a long way. That said, the more I work in this "unix

Re: [Mailman-Users] upgrading Panther Server basic install 2.1.2 to 2.1.5

At 8:15 AM -0500 2004-06-30, Dan Phillips wrote: This is a completely different animal however, in that non-Server Panther does not come with Mailman already installed (at least mine didn't). This is just a plain fresh install rather than an update of an Apple modified installation. I understa

Re: [Mailman-Users] upgrading Panther Server basic install 2.1.2 to 2.1.5

On Jun 30, 2004, at 5:54 AM, Brad Knowles wrote: At 9:54 PM -0500 2004-06-29, Larry Stone wrote: Well, I have Mailman 2.1.4 running just fine on Panther (regular, not Server). I basically followed the instructions contained in

Re: [Mailman-Users] upgrading Panther Server basic install 2.1.2 to 2.1.5

At 8:33 PM -0400 2004-06-29, Thomas Waters wrote: Mailman has worked really well for me, but as someone coming to Panther Server and Mailman from running a webstar server, it is a big jump- a BIG change. Better docs to help the newbie/clueless would go a long way. We understand. We'd like to

Re: [Mailman-Users] upgrading Panther Server basic install 2.1.2 to 2.1.5

At 9:54 PM -0500 2004-06-29, Larry Stone wrote: Well, I have Mailman 2.1.4 running just fine on Panther (regular, not Server). I basically followed the instructions contained in (which deals with getting Mailman running u

Re: [Mailman-Users] upgrading Panther Server basic install 2.1.2 to 2.1.5

On 6/29/04 11:14 AM, Brad Knowles at [EMAIL PROTECTED] wrote: > So far as I know, all the people running Mailman on MacOS X are > either doing it from stuff they've installed themselves on Jaguar, or > they're using the Apple-bundled stuff on Panther Server. I don't > know of anyone who has tried

  1   2   >