Re: [Mailman-Users] Upgrade instructions

On 09/05/2014 11:49 PM, G. Armour Van Horn wrote: > > The host intends to > upgrade so that we can address that but they report that they haven't > been able to make archives searchable in their experimentation with > 2.1.16. I don't know if that search function is part of the more recent > versio

[Mailman-Users] Upgrade instructions

G. Armour Van Horn writes: > The host intends to upgrade so that we can address that but they > report that they haven't been able to make archives searchable in > their experimentation with 2.1.16. It's worth upgrading all the way to 21.1.18-1 if at all possible. That version provides which r

[Mailman-Users] Upgrade instructions

I have a couple of Mailman lists on a server happily running 2.1.9 but I am also a moderator on a very active list that's running on 2.1.12. I do not host this list, just volunteer because I have some experience with Mailman. That list has started to get some significant bounces due to the DMA

Re: [Mailman-Users] Upgrade 2.1.14 to 2.1.17 on Ubuntu Question

On 04/17/2014 06:23 AM, Richard Shetron wrote: > I've searched the list and found enough related posts that this looks > like it should be simple just reinstall, hopefully with the original > PREFIX settings and probably diff the old and new mm_cfg.py files just > to catch all the changes/new featu

[Mailman-Users] Upgrade 2.1.14 to 2.1.17 on Ubuntu Question

I've searched the list and found enough related posts that this looks like it should be simple just reinstall, hopefully with the original PREFIX settings and probably diff the old and new mm_cfg.py files just to catch all the changes/new features/etc. I have visual problems so my eyes often go fu

Re: [Mailman-Users] Upgrade Mailman 2.1.13 to 2.1.16

On 11/01/2013 01:32 PM, Martin Hugo wrote: > Mark, > > Thanks very much. Was able to update with no errors reported during the > process. However, when I now go to the listinfo page I get the Bug in > Mailman version 2.1.16 page. Also messages to lists are being returned > undeliverable. Wh

Re: [Mailman-Users] Upgrade Mailman 2.1.13 to 2.1.16

On 11/01/2013 07:27 AM, Martin Hugo wrote: > > Can anyone point me at a good tutorial on how to upgrade from 2.1.13 to > 2.1.16? If you still have the original directory in which you unpacked Mailman 2.1.13, look in the config.log file for the "Invocation command line". Download and unpack 2.1

[Mailman-Users] Upgrade Mailman 2.1.13 to 2.1.16

Hi All, We are running Mailman 2.1.13 (on Ubuntu) and have been for some time. Recently the SPAM bots have been hitting our subscription addresses so hard the bounces have tripped the filters at Microsoft and blocked a couple of lists addresses until I get them to unblock them. It looks like

Re: [Mailman-Users] Upgrade for Postfix & Mailman

On 1/25/2013 2:05 PM, Jeff Bernier wrote: Hello All, I am currently running Mailman (2.1.14) and Postfix (2.4.3) on an aging Mac OS X server (10.5.8). Mailman and Postfix on this system are Apple's implementation on their platform of course. Apple no longer supports the Xserve platform, and I am

[Mailman-Users] Upgrade for Postfix & Mailman

Hello All, I am currently running Mailman (2.1.14) and Postfix (2.4.3) on an aging Mac OS X server (10.5.8). Mailman and Postfix on this system are Apple's implementation on their platform of course. Apple no longer supports the Xserve platform, and I am in need of replacing this system, and upgra

Re: [Mailman-Users] Upgrade from 2.1.14-1 to 2.1.15 - Authorization failed.

On 10/10/2012 4:29 PM, Patrick wrote: > > I've tried: [...] > > arch --wipe listname This wouldn't help as the "Authorization failed" error occurs before any attempt has been made to access the archive files. > Can you please point to what .py file and section I might add some > debug output s

Re: [Mailman-Users] Upgrade from 2.1.14-1 to 2.1.15 - Authorization failed.

> Look at the action URL in the form tag on the login page. Is it what you > expect? Yes, it is correct. A fully qualified name. Apache is not doing any redirection. I've tried: $prefix/bin/withlist -l -r fix_url listname and arch --wipe listname Can you please point to what .py file and sec

Re: [Mailman-Users] Upgrade from 2.1.14-1 to 2.1.15 - Authorization failed.

On 10/5/2012 4:34 PM, Patrick wrote: > > When I attempt to login to a private list using 2.1.14 I’m able to get > to the list with my password. > > However, if I switch over to 2.1.15 I get an “Authorization failed.” error. > > Interestingly on my test machine I have an identical configuration,

Re: [Mailman-Users] upgrade path from 2.1.13 to 2.1.15

On 7/23/2012 1:17 PM, Christopher Adams wrote: > Hello, > > I am finally getting around to to upgrading Mailman 2.1.13. Should I > upgrade to 2.1.14 and then upgrade to 2.1.15, or just go directly to 2.1.15? Just upgrade directly to 2.1.15. There's no need to do any intermediate upgrades. > It

[Mailman-Users] upgrade path from 2.1.13 to 2.1.15

Christopher Adams writes: > I am finally getting around to to upgrading Mailman 2.1.13. Should > I upgrade to 2.1.14 and then upgrade to 2.1.15, or just go directly > to 2.1.15? You can just go directly. Of course check the "UPGRADING" document for a refresher, but there are no particular tas

[Mailman-Users] upgrade path from 2.1.13 to 2.1.15

Hello, I am finally getting around to to upgrading Mailman 2.1.13. Should I upgrade to 2.1.14 and then upgrade to 2.1.15, or just go directly to 2.1.15? It sounds like 2.1.15 changes some files significantly, but the process remains the same. Basically, do as if installing mailman initially, usin

Re: [Mailman-Users] upgrade question

On 7/25/11 5:05 PM, Mark Sapiro wrote: On 7/25/2011 2:31 PM, Maria Mckinley wrote: Thanks for everyone's help. Turns out I had copied the correct directory, but the mboxes needed to be rebuilt. But, there are some subscribers that were added between the builds, and they seem to still be lost. D

Re: [Mailman-Users] upgrade question

On 7/25/2011 2:31 PM, Maria Mckinley wrote: > > Thanks for everyone's help. Turns out I had copied the correct > directory, but the mboxes needed to be rebuilt. But, there are some > subscribers that were added between the builds, and they seem to still > be lost. Does anyone know what file has th

Re: [Mailman-Users] upgrade question

On 7/25/11 8:58 AM, Adam McGreggor wrote: On Mon, Jul 25, 2011 at 07:40:44AM -0700, Mark Sapiro wrote: You could try 'locate mailman'. And/or 'dpkg -L mailman' Thanks for everyone's help. Turns out I had copied the correct directory, but the mboxes needed to be rebuilt. But, there are some

Re: [Mailman-Users] upgrade question

On Mon, Jul 25, 2011 at 07:40:44AM -0700, Mark Sapiro wrote: > You could try 'locate mailman'. And/or 'dpkg -L mailman' -- "There seems to be something wrong with our bloody ships today" -- David, Vice-Admiral Beatty (re: the Battle of the Jutland) ---

Re: [Mailman-Users] upgrade question

Maria Mckinley wrote: > >However, mailman is missing some stuff that happened while I was >upgrading the new machine, so I must be rsyncing the wrong directory. I >thought it should be /var/lib/mailman/, but I think this must not be the >directory that mailman is using anymore. This is on a debi

Re: [Mailman-Users] upgrade question

On Sun, Jul 24, 2011 at 09:53:47PM -0700, Maria Mckinley wrote: > However, mailman is missing some stuff that happened while I was > upgrading the new machine, so I must be rsyncing the wrong directory. I > thought it should be /var/lib/mailman/, but I think this must not be the > directory t

[Mailman-Users] upgrade question

Hi there, I have upgraded my mail server by the following steps: 1. make a copy of the old hard drive 2. upgrade the new one (while isolated) while the old one is still running 3. once the new one is working isolate both 4. then rsync data from the old to the new. 5. bring the new one on line.

Re: [Mailman-Users] upgrade from 2.1.5 to 2.1.11 on debian

Marcus wrote: > >Before installing the mailman package on the new lenny box I've copied >the /var/lib/mailman/ directory from the old server (mailman 2.1.5) to >the new one. After that I've started an "aptitude install mailman" to >install mailman 2.1.11 on the lenny maschine. The installation didn

[Mailman-Users] upgrade from 2.1.5 to 2.1.11 on debian

Hi, I'd like to upgrade from mailman 2.1.5 (self-build backport on an older sarge installation) to 2.1.11 on Debian/Lenny. Before installing the mailman package on the new lenny box I've copied the /var/lib/mailman/ directory from the old server (mailman 2.1.5) to the new one. After that I've st

Re: [Mailman-Users] upgrade mailman

Lily Hewgley wrote: >Hi. We have version 2.1.11 and would like to upgrade, if possible. Can you >send me info and a link to your website, please. Start at or if you are running a vendor package, see if the vendor has an upgraded package available. -- Mark Sapiro

[Mailman-Users] upgrade mailman

Hi. We have version 2.1.11 and would like to upgrade, if possible. Can you send me info and a link to your website, please. Thanks. Lily Hewgley State Bar of Texas Web Designer - Sections (512) 427-1423 -- Mailman-

Re: [Mailman-Users] Upgrade questions - Best method suggestions requested

On 7/16/08 12:57 AM, Brad Knowles at [EMAIL PROTECTED] wrote: > On 7/15/08, Drew Tenenholz wrote: > >> 1) Are there any significant changes to the FAQ for Apple upgrade I >> should know about? > > The Apple-related portion of the documentation has been contributed > by other members of the com

Re: [Mailman-Users] Upgrade questions - Best method suggestions requested

On 7/15/08, Drew Tenenholz wrote: 1) Are there any significant changes to the FAQ for Apple upgrade I should know about? The Apple-related portion of the documentation has been contributed by other members of the community, so if you haven't seen any updates there, it is *NOT* safe to assu

[Mailman-Users] Upgrade questions - Best method suggestions requested

Folks -- I'm planning on upgrading my Mac XServe this weekend, and wanted to get a feel for the 'best' way to make sure the work goes smoothly. Thanks in advance for your suggestions. The overall goal is to upgrade from G5 XServe 10.3.9 Server(!) with default Apple installation of Mailman 2.

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

Moss, Patricia wrote: >I could not find much documentation on upgrading from mailman version >2.1.5 to version 2.1.9. I want to make sure that it is as simple as >backing up my current install then run 'configure' and 'make install'. >The new will overwrite the old and convert what needs to be co

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

Moss, Patricia wrote: >I could not find much documentation on upgrading from mailman version >2.1.5 to version 2.1.9. I want to make sure that it is as simple as >backing up my current install then run 'configure' and 'make install'. >The new will overwrite the old and convert what needs to be con

[Mailman-Users] Upgrade from 2.1.5 to 2.1.9

I could not find much documentation on upgrading from mailman version 2.1.5 to version 2.1.9. I want to make sure that it is as simple as backing up my current install then run 'configure' and 'make install'. The new will overwrite the old and convert what needs to be converted; would this be a co

Re: [Mailman-Users] upgrade

Matt Zimmerman wrote: >Is there any documents on upgrading from 2.1.8 to 2.1.9? Read the UPGRADING and NEWS documents in the source distribution. Only the first "UPGRADING FROM PREVIOUS VERSIONS" section of the UPGRADING document applies to upgrading any 2.1.5 or later version. The NEWS document

[Mailman-Users] upgrade

Is there any documents on upgrading from 2.1.8 to 2.1.9? -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http:/

Re: [Mailman-Users] Upgrade problem

--On March 4, 2007 11:08:30 AM -0800 Mark Sapiro <[EMAIL PROTECTED]> wrote: > Steve Burling wrote: > > Is there a way I can un-inhibit "printing of traceback and other system > > info"? > > > > Yes. Edit the scripts/driver file and change > > STEALTH_MODE = 1 > > to > > STEALTH_MODE = 0 To which

Re: [Mailman-Users] Upgrade problem

Steve Burling wrote: >I just tried to upgrade our Mailman 2.1.4 install to Mailman 2.1.9. I >didn't get very far -- as soon as I tried to visit the listinfo page, I got >the "sorry we've hit a bug" message: > >--- >Bug in Mailman version 2.1.9 > >We're sorry, we hit a bug! > >Please inform the

[Mailman-Users] Upgrade problem

I just tried to upgrade our Mailman 2.1.4 install to Mailman 2.1.9. I didn't get very far -- as soon as I tried to visit the listinfo page, I got the "sorry we've hit a bug" message: --- Bug in Mailman version 2.1.9 We're sorry, we hit a bug! Please inform the webmaster for this site of this

[Mailman-Users] Upgrade to mailman-2.1.9

Odhiambo Washington writes: > I have finally decided to upgrade from 2.1.5 -> 2.1.9, but I am being > hesitant because in 2.1.5, there was a patch to integrate spam > filtering into Mailman using SpamAssassin. First, look at doing the filtering in the MTA. Second, look at the new filtering

Re: [Mailman-Users] Upgrade to mailman-2.1.9

At 5:31 PM +0300 11/1/06, Odhiambo Washington wrote: > I have finally decided to upgrade from 2.1.5 -> 2.1.9, but I am being > hesitant because in 2.1.5, there was a patch to integrate spam > filtering into Mailman using SpamAssassin. For one thing, you should be filtering using tools like Spa

Re: [Mailman-Users] Upgrade to mailman-2.1.9

On 11/1/06, Odhiambo Washington <[EMAIL PROTECTED]> wrote: > I have finally decided to upgrade from 2.1.5 -> 2.1.9, but I am being > hesitant because in 2.1.5, there was a patch to integrate spam > filtering into Mailman using SpamAssassin. > > What are my options once I go to 2.1.9? The best opti

[Mailman-Users] Upgrade to mailman-2.1.9

Hi, I have finally decided to upgrade from 2.1.5 -> 2.1.9, but I am being hesitant because in 2.1.5, there was a patch to integrate spam filtering into Mailman using SpamAssassin. What are my options once I go to 2.1.9? cheers - wash +--+--

Re: [Mailman-Users] UPgrade to 2.1.9 woes

Raphael Mankin wrote: >I recently upgraded from 2.1.8 to 2.1.9. This caused problems with the >URLs generated in the admin pages. > >Previously, they used the virtual host name. After the change to 2.1.9 >the URLs used the real host name, which failed in my virtual hosting >environment. This com

[Mailman-Users] UPgrade to 2.1.9 woes

I recently upgraded from 2.1.8 to 2.1.9. This caused problems with the URLs generated in the admin pages. Previously, they used the virtual host name. After the change to 2.1.9 the URLs used the real host name, which failed in my virtual hosting environment. Is this known issue? Is there a work-a

Re: [Mailman-Users] upgrade issue

Mark Nernberg wrote: > >On Sep 25, 2006, at 4:09 PM, Mark Sapiro wrote: >> >> Assuming you get the same error when attempting to access the list >> (after fixing the problem below, try copying or moving the config.pck >> aside and replacing it with the config.pck.last > >I hate to say it, but I alr

Re: [Mailman-Users] upgrade issue

On Sep 25, 2006, at 4:09 PM, Mark Sapiro wrote: > Help Desk wrote: >> >> We get the following string of errors during the upgrade phase, >> then a stop: >> >> >> Updating mailing list: river_city_referrals >> Traceback (most recent call last): >> File "bin/update", line 789, in ? >>errors =

Re: [Mailman-Users] upgrade issue

Help Desk wrote: > >We get the following string of errors during the upgrade phase, then a stop: > > >Updating mailing list: river_city_referrals >Traceback (most recent call last): > File "bin/update", line 789, in ? >errors = main() > File "bin/update", line 679, in main >errors = error

[Mailman-Users] upgrade issue

One of our bone-headed admins was playing around on the server and "broke" something in Mailman. Rather than try to fix it (I'm not a Python programmer!), I decided it was time for an update via ports anyway. We get the following string of errors during the upgrade phase, then a stop: Updatin

Re: [Mailman-Users] upgrade

Matthew Clarkson wrote: >Charles Stroom wrote: >> not 2.1.7, but 2.1.6 is in the 10.0 Suse distri. See: >> >> ftp.gwdg.de/pub/linux/suse/apt/SuSE/10.0-i386/RPMS.base/mailman-2.1.6-4.i586.rpm 2.1.8a1 was just announced. If there's no immediate urgency, I'd wait a few weeks and then upgrade to 2.

Re: [Mailman-Users] upgrade

Charles Stroom wrote: > not 2.1.7, but 2.1.6 is in the 10.0 Suse distri. See: > > ftp.gwdg.de/pub/linux/suse/apt/SuSE/10.0-i386/RPMS.base/mailman-2.1.6-4.i586.rp > m > > Charles Stroom > > > --- Original Message > > on Thu, 09 Mar 2006 09:36:10 CST > "Patrick Bogen" <[EMAIL PROTECTED]> wrote:

Re: [Mailman-Users] upgrade

not 2.1.7, but 2.1.6 is in the 10.0 Suse distri. See: ftp.gwdg.de/pub/linux/suse/apt/SuSE/10.0-i386/RPMS.base/mailman-2.1.6-4.i586.rp m Charles Stroom --- Original Message on Thu, 09 Mar 2006 09:36:10 CST "Patrick Bogen" <[EMAIL PROTECTED]> wrote: > > On 3/9/06, Siim Kobin <[EMAIL PROTEC

Re: [Mailman-Users] upgrade

On 3/9/06, Siim Kobin <[EMAIL PROTECTED]> wrote: > i need to upgrade mailman from 2.1.4 to 2.1.7 on suse 9.1, but i can't find > rpm for it. Interestingly, SuSe seems to have removed mailman from its 10.0 release. Anyway, you can find a 2.1.7 RPM here: ftp://rpmfind.net/linux/fedora/core/developmen

[Mailman-Users] upgrade

i need to upgrade mailman from 2.1.4 to 2.1.7 on suse 9.1, but i can't find rpm for it. how can i do this with minimal time & data loss. it has to be online 24/7 so i can't allow it to be offline for very long time. i think it should work if i just recompile it, but i don't know suse specific

Re: [Mailman-Users] Upgrade mailman-2.1.4 to mailman-2.1.7

Christopher Adams wrote: >Thanks, Mark. I was aware that list-specific templates could be set up >and I guess I didn't think about the effect of upgrades on them. >As I understand the FAQ, Mailman will look for the templates >first in the list specific directory, and if it doesn't exist, in the >b

Re: [Mailman-Users] Upgrade mailman-2.1.4 to mailman-2.1.7

Thanks, Mark. I was aware that list-specific templates could be set up and I guess I didn't think about the effect of upgrades on them. As I understand the FAQ, Mailman will look for the templates first in the list specific directory, and if it doesn't exist, in the base template directory. We host

Re: [Mailman-Users] Upgrade mailman-2.1.4 to mailman-2.1.7

Christopher Adams wrote: >One thing to keep in mind when upgrading Mailman is that some customized >templates will be overwritten. The significant ones I can think of are >listinfo.html and newlist.txt. So, I always at minimum the templates >directory and copy over the files after the upgrade.

Re: [Mailman-Users] Upgrade mailman-2.1.4 to mailman-2.1.7

One thing to keep in mind when upgrading Mailman is that some customized templates will be overwritten. The significant ones I can think of are listinfo.html and newlist.txt. So, I always at minimum the templates directory and copy over the files after the upgrade. Christopher Adams Mark Sap

Re: [Mailman-Users] Upgrade mailman-2.1.4 to mailman-2.1.7

Pad Hosmane wrote: > We are using mailman-2.1.4 on HP-UX. It is running without any issues. Now >we want to upgrade it to latest version 2.1.7. I searched online for >documentation about upgrade, and I could not find any. Can anyone guide me >how to do the upgrade or provide URL where I can get i

[Mailman-Users] Upgrade mailman-2.1.4 to mailman-2.1.7

Hi, We are using mailman-2.1.4 on HP-UX. It is running without any issues. Now we want to upgrade it to latest version 2.1.7. I searched online for documentation about upgrade, and I could not find any. Can anyone guide me how to do the upgrade or provide URL where I can get information about upg

Re: [Mailman-Users] Upgrade problems from 2.1.5 to 2.1.6

I had 2 problems which I finally discoved by following through on the error messages: 1) I had stopped the web server and sendmail, but forgot to stop mailman. Du. 2) I discovered a problem with ~mailman/Mailman/mm_cfg.py It had a line in it QUEUE_DIR = '/var/spool/mail

Re: [Mailman-Users] Upgrade problems from 2.1.5 to 2.1.6

I am running mailman-2.1.5 on a redhat linux AS 4 system with all the latest redhat fixes. I just ran the mailman-2.1.6 upgrade and encountered the following messages for each (but not all my lists) Updating mailing list: 4h-northern^M Updating the held requests database.^M - updating old private

Re: [Mailman-Users] Upgrade to 2.1.6?

Bob Bergey wrote: >I'm currently running about a dozen lists using Mailman 2.1.4, which >came pre-installed on my Apple XServe with Panther OS 10.3.9. I see >this list and other lists are using 2.1.6, but I couldn't find >information on the Mailman site about what the changes are, or how or >i

[Mailman-Users] Upgrade to 2.1.6?

I'm currently running about a dozen lists using Mailman 2.1.4, which came pre-installed on my Apple XServe with Panther OS 10.3.9. I see this list and other lists are using 2.1.6, but I couldn't find information on the Mailman site about what the changes are, or how or if I should upgrade. My l

Re: [Mailman-Users] Upgrade Apache, break web access?

JB Segal wrote: > >When I submit a webform, nothing logs any errors - not apache, not >mailman, not syslog (When I tried upgrading to Mailman 2.1.5, I had >the syslog errors discussed in the faq and had to go back and set >different groups...), but nothing happens, either. > >If I have a valid sess

[Mailman-Users] Upgrade Apache, break web access?

I feel like a total idiot for having to ask this, but there's nothing presenting itself, either in increased logging levels, the archives, the docs or my instinct. I'll also note that this MIGHT be an apache problem. FreeBSD 4.9 Mailman both 2.1.3 and 2.1.5 Python 2.3 (#1, Jul 5 2004, 16:23:56)

Re: [Mailman-Users] Upgrade from Fedora 2 to 3 no longer see lsits

At 11:20 AM -0800 2005-02-15, scot condry wrote: Hello. I recently upgraded from Fedora 2 to Fedora 3 (upgrade, not a fresh install). Everything is working OK except when I go to my mailman web page it says there are not lists configured. They are not working as well (as in if you send an em

[Mailman-Users] Upgrade from Fedora 2 to 3 no longer see lsits

Hello. I recently upgraded from Fedora 2 to Fedora 3 (upgrade, not a fresh install). Everything is working OK except when I go to my mailman web page it says there are not lists configured. They are not working as well (as in if you send an email to the list it is nto being delivered). Can a

Re: [Mailman-Users] Upgrade hell (Debian)

Two things I left out of this previous message: http://mail.python.org/pipermail/mailman-users/2005-January/041687.html 1. We fixed an apparent coding error in /usr/lib/mailman/bin/update. On line 556, we changed "addr = data[0].address" to "addr = data[0]", since data[0] was already an

Re: [Mailman-Users] Upgrade hell (Debian)

In this message http://mail.python.org/pipermail/mailman-users/2003-June/029660.html Deirdre Saoirse Moen described a problem upgrade she had while upgrading Mailman on a Debian GNU/Linux system. We just encountered the same problem, when we tried to do # apt-get install mailman to go fro

Re: [Mailman-Users] Upgrade question

Ashley M. Kirchner wrote: > >Having moved from mailman 2.0.11 to 2.1.5, I'm left with a few >questions: > >1) What, if anything, do I need to do to make sure the old lists >work with the new mailman? When I installed 2.1.5, it told me that it >checked/fixed/converted lists at the very e

[Mailman-Users] Upgrade question

Having moved from mailman 2.0.11 to 2.1.5, I'm left with a few questions: 1) What, if anything, do I need to do to make sure the old lists work with the new mailman? When I installed 2.1.5, it told me that it checked/fixed/converted lists at the very end of the installation. Does that

Re: [Mailman-Users] upgrade 2.0.13 to 2.1.4, no mail goes out, no bounces come back

Ooops. Right, it's configure that sets that up. Duh. Okay, I'll go back under my rock now. -- Sleepy, Dopey, Sneezy, Bashful, Grumpy, Happy, Doc Just in case you'd forgotten... http://www.hacksaw.org -- http://www.privatecircus.com -- KB1FVD ---

Re: [Mailman-Users] upgrade 2.0.13 to 2.1.4, no mail goes out, no bounces come back

Hi, Hacksaw wrote: Now I need to figure out why sendmail is ignoring the setgid on the script... Grrr... You know how it says in the INSTALL file: "By default, the value is the list `mailman other mail daemon'." That appears to be wrong. In the Makefile, it only said "mailman". In the same INSTA

Re: [Mailman-Users] upgrade 2.0.13 to 2.1.4, no mail goes out, no bounces come back

>Now I need to figure out why sendmail is ignoring the setgid on the script... Grrr... You know how it says in the INSTALL file: "By default, the value is the list `mailman other mail daemon'." That appears to be wrong. In the Makefile, it only said "mailman". -- The universe is not only stran

Re: [Mailman-Users] upgrade 2.0.13 to 2.1.4, no mail goes out, no bounces come back

All right... A sendmail configuration change caught me. in Sendmail 8.12.9, it seems to have moved the stuff in /etc/smrsh to /usr/adm/sm.rsh. Now I need to figure out why sendmail is ignoring the setgid on the script... -- http://www.hacksaw.org -- http://www.privatecircus.com -- KB1FVD -

[Mailman-Users] upgrade 2.0.13 to 2.1.4, no mail goes out, no bounces come back

All the web stuff seems to work. I even ran /home/mailman/mail/mailman post list and supplied it with a mail message, and it vanished into thin air without a trace. I have check_perms'ed, made sure the mailmanctl daemon, and all it's minions are running, made sure the aliases are there, and tha

[Mailman-Users] Upgrade from 2.0 to 2.1.5 breaks on pending_subscriptions.db

Has anyone else come across this and if so what's the solution? I'm running an upgrade of our mailman install in a test environment and it's breaking with the following error. I'm running on Solaris 8 with Python 2.3.4. The 2.0 version of Mailman was using python 1.6. phoenix on old-hawk {731}# l

Re: [Mailman-Users] Upgrade to 2.1.4 failed - user lost - recover via backup unsuccessful - any ideas?

Hi, > then how about 'strings' ? Email-Addresses. A lot of them, although I can't see how many. But I fear something is not right as it (partly) looks as follows: --- [EMAIL PROTECTED] kJVe0ZnAr [EMAIL PROTECTED] John Doe [EMAIL PROTECTED] U Jane Doe [EMAIL PROTECTED] Janis Doe l Elikarar"U [EM

Re: [Mailman-Users] Upgrade to 2.1.4 failed - user lost - recover via backup unsuccessful - any ideas?

Hi, it's time to go to bed here in Japan. ;-) Hmm, but the traceback says your config.pck is broken. You should use 'cat' or 'od' to read what your config.pck really has. "od" gives me an almost endless list of 9 columns with numbers. The (snip) then how about 'strings' ? Other useful tool may be

Re: [Mailman-Users] Upgrade to 2.1.4 failed - user lost - recover via backup unsuccessful - any ideas?

Hi, sorry for this rather long email, but I made some observations, see below. > I guess there is config.pck.last and mailman fallbacks to it knowing > the backup config.pck is corrupted. Anticipating that, I had deleted the .last-file, even replaced them with the backup-file. No difference. >

Re: [Mailman-Users] Upgrade to 2.1.4 failed - user lost - recover via backup unsuccessful - any ideas?

Hi again. Have you also tried "bin/update --force" ? However, it didn't help at all. Again, it stripped the backup-file (that I had renamed to config.pck before executing the above command) from 533 KB to 83 KB - and still the old (no good) subscriber list. I guess there is config.pck.last and mai

Re: [Mailman-Users] Upgrade to 2.1.4 failed - user lost - recover via backup unsuccessful - any ideas?

Hello, > Have you also tried "bin/update --force" ? I have now... It produced quite a bit of output, such as e.g.: "Updating mailing list: LISTNAME Updating the held requests database. // every list - updating old private mbox file - updating old public mbox file Fixing language templates: LIST

Re: [Mailman-Users] Upgrade to 2.1.4 failed - user lost - recover via backup unsuccessful - any ideas?

Have you done 'bin/update' after moving the backup config.pck file into the newly installed list directory ? "No updates are necessary." The more I think about it I get the feeling that my backup-files somehow got screwed up... Still, can no one tell me where I can at least find the subscribed a

Re: [Mailman-Users] Upgrade to 2.1.4 failed - user lost - recover via backup unsuccessful - any ideas?

Hello Tokio, [sorry, this got only mailed to you personally; again to the list; strange list setting btw...] > Have you done 'bin/update' after moving the backup config.pck file > into the newly installed list directory ? "No updates are necessary." The more I think about it I get the feeling t

Re: [Mailman-Users] Upgrade to 2.1.4 failed - user lost - recover via backup unsuccessful - any ideas?

Hi, Have you done 'bin/update' after moving the backup config.pck file into the newly installed list directory ? Alex Dupont wrote: Hello, I'm a "bit" in a loss here: I was running Mailman 2.1.2 on Debian 3.0 with no problems. Using apt-get... to upgrade Mailman to 2.1.4 produced an error. Well, be

[Mailman-Users] Upgrade to 2.1.4 failed - user lost - recover via backup unsuccessful - any ideas?

Hello, I'm a "bit" in a loss here: I was running Mailman 2.1.2 on Debian 3.0 with no problems. Using apt-get... to upgrade Mailman to 2.1.4 produced an error. Well, besides the fact that all my archives got deleted (why would a script (!) do that??), I finally got Mailman back up and running vers

Re: [Mailman-Users] Upgrade from 2.0.11 to 2.1.5

At 3:41 PM -0500 2004/05/28, Young, Darren wrote: I'm in the middle of planning an upgrade of our mailman installation and was looking for some pointers. You can take a look at . First question on the move of machines, shou

[Mailman-Users] Upgrade from 2.0.11 to 2.1.5

I'm in the middle of planning an upgrade of our mailman installation and was looking for some pointers. The current version is 2.0.11 and I'm planning on going to the current 2.1.5. I'm actually moving the installation from an older desktop system to a newer server at which time I want to upgrade t

[Mailman-Users] Upgrade to 2.1.5 fails on 'Updating Usenet watermarks'

Updating from 2.1.4 release to 2.1.5 release, during make install, it dies on: Updating Usenet watermarks - nothing to update here Nothing to do. updating old qfiles Traceback (most recent call last): File "bin/update", line 780, in ? errors = main() File "bin/update", line 709, in main

Re: [Mailman-Users] upgrade, problem with archives on vhost.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Mar 14, 2004 at 02:28:27AM +, John R Pierce wrote: > Hey. I just upgraded my 2.0.x(3?) to 2.1.4, and after some struggle to get > it all working again, everything is flying, *except*... > > The lists that are on my 'native' domain are wo

[Mailman-Users] upgrade, problem with archives on vhost.

Hey. I just upgraded my 2.0.x(3?) to 2.1.4, and after some struggle to get it all working again, everything is flying, *except*... The lists that are on my 'native' domain are working great, but the ones on my alternate virtual hostnames aren't linking to the archives properly. for instance,

[Mailman-Users] upgrade - archives problem.

I've moved a list from a server running 2.0.13 to a server running 2.1.3. Maybe I did it backwards, but I needed to change the list name as well, so I just created the new list with new name on the new server, and the copied in the archives from the old server, and did a search and replace on all

[Mailman-Users] Upgrade heldmsgs?

Hello! I want to transfer some (not all!) lists from an existing 2.0.13 installation to the latest 2.1. I'm currently having both 2.0 and 2.1 installed, and am trying to transparently migrate lists to 2.1. Most of the stuff is covered in UPGRADE, but I have some unresolved issues. Some of our c

[Mailman-Users] upgrade from 2.0.13

Hey guys How difficult is the upgrade from 2.0.13 to the latest and do you suggest upgrading it ? I mean what are the big benefits ? Thanks Jaskaran Singh University Systems & Security Fairleigh Dickinson University 1000 River Road, Mail Stop TBH1-01 Teaneck, NJ 07666

Re: [Mailman-Users] upgrade help

On Thursday, November 6, 2003, at 07:51 am, Ako Ito wrote: hello guys, can you guide me on how to upgrade my 2.0.6 mailman to the latest 2.1 version.. what are the requirements and would it convert all the archives files in hmtl format.. also would all the settings for each weblist still remai

[Mailman-Users] upgrade help

hello guys, can you guide me on how to upgrade my 2.0.6 mailman to the latest 2.1 version.. what are the requirements and would it convert all the archives files in hmtl format.. also would all the settings for each weblist still remain? thanks, allan

[Mailman-Users] Upgrade from Mailman 2.1.1 -> 2.1.2

Hi, I'm quite new to Mailman and for some time ago installed Mailman 2.1.1 . Now I think it's time to upgrade to 2.1.2 :-) I looked at mailman-2.1.2/UPGRADING but couldn't find anything about going from 2.1.1 to 2.1.2 . So I made a new clean installation av 2.1.2 beside 2.1.1 and compared the

Re: [Mailman-Users] Upgrade install - "Could not import paths!"

Richard Barrett wrote on Mon 4 Aug 2003 at 14:37 +0100 >$prefix means the path of the directory in which you installed Mailman Yes! I did install --prefix=/home/mailman BTW >Unless you previously reported problem has been fully corrected then >this may be the latest manifestation of a failing im

Re: [Mailman-Users] Upgrade install - "Could not import paths!"

On Monday, August 4, 2003, at 12:08 pm, david.gordon wrote: Richard Barrett wrote on Sun 3 Aug 2003 at 16:14 +0100 You should have two files in you Mailman runtime installation: $prefix/pythonlib/korean $prefix/pythonlib/korean.pth Apologies, I don't do this often enough to know what I (er, or

Re: [Mailman-Users] Upgrade install - "Could not import paths!"

Richard Barrett wrote on Sun 3 Aug 2003 at 16:14 +0100 >You should have two files in you Mailman runtime installation: > >$prefix/pythonlib/korean >$prefix/pythonlib/korean.pth Apologies, I don't do this often enough to know what I (er, or you) am on about. Where exactly these files are eludes me

  1   2   >