Re: [Mailman-Users] mailman 2.1.14 new features
On Oct 20, 2010, at 01:53 PM, Adam McGreggor wrote:
Barry Warsaw <barry@list.org> replied:
As I have posted before, I looked at the Debian packaging for Mailman, and I found there are lots of patches (most undocumented as to what they do). There was one patch that removed a library that may be needed. And one security of three I researched had different code in Debian/Ubuntu than in SourceForge. I assume that the Debian/Ubuntu patch that differed fixed the security problem, but I can not be sure. After following the discussions on mailman-users where users were running non-SourceForge code, I decided that I had to take the SourceForge code and build a Mailman package. It took me a while to discover exactly what to do, but once I did it (IIRC for 2.1.9), I have had no trouble building packages for 10 through 14. I can send my steps to anyone who wants them. My Mailman machines are still Ubuntu/dapper, but I assume that my steps would work unchanged on any later release of Debian/Ubuntu.
Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone: +1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 240, Room 5.B.8 Internet: BSFinkel@anl.gov Argonne, IL 60439-4828 IBMMAIL: I1004994
Using Mailman version: 2.1.12rc2
For some reason all of my mailing lists are now disconnected from mailman. There is data in /usr/local/mailman/lists, and also lots of data in the archives/private dir. But when I try to go to the admin page on any list I get a "list does not exist" message. I did a yum update the other day.
What has happened and how do I fix it?
Second question:
In my Apache logfile I'm getting the following warning:
[Sat Oct 23 09:44:08 2010] [warn] The Alias directive in /etc/httpd/conf/httpd.conf at line 583 will probably never match because it overlaps an earlier Alias. [Sat Oct 23 09:44:08 2010] [warn] The ScriptAlias directive in /etc/httpd/conf/httpd.conf at line 584 will probably never match because it overlaps an earlier ScriptAlias.
The two lines in question are:
# # MailMan Settings # Alias /pipermail/ "/usr/local/mailman/archives/public/" ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/"
I don't remember seeing this before I did a yum update the other day.
Thanks.
- Dale
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Dale & Lora Marshall Internet Marketing Services
http://www.SpottedDragon.com/ http://www.internet-ms.com
marshall@cliffhanger.com dalem@internet-ms.com
loram@internet-ms.com-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Dale & Lora Marshall wrote:
I haven't a clue?
What did you update with Yum?
Do you see any lists on the admin or listinfo overview pages?
What does /usr/local/mailman/bin/list_lists report?
Aha. Now I have a clue. The Yum update most likely installed a Mailman package which is now being accessed by Apache and has no lists. There is most likeley now a /etc/httpd/conf.d/mailman file containing "Alias /pipermail/" and "ScriptAlias /mailman/" directives pointing to this new installation. Remove that file. Then you'll also have to figure out if other things such as aliases or other MTA stuff were clobbered by the Yum update. Possibly just doing "yum remove mailman" will fix things as long as there are no other conflicts between the package yum installed and your existing Mailman.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
I did a yum update and then a "yum install mailman". I run a server with a lot of domains on it and a few of them have mailing lists but not all.
list_lists reports 17 mailing lists which is I believe correct.
There was a mailman.conf file in the conf.d dir. Thanks! I moved it to a different name (just in case) and now I can at least see the two lists I maintain. I'll email the guy with the other lists and see if he's ok now.
Thanks again!
- Dale
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Dale & Lora Marshall Internet Marketing Services
http://www.SpottedDragon.com/ http://www.internet-ms.com
marshall@cliffhanger.com dalem@internet-ms.com
loram@internet-ms.com-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-----Original Message----- From: Mark Sapiro <mark@msapiro.net> To: Dale & Lora Marshall <marshall@cliffhanger.com>; mailman-users@python.org Sent: Sat, Oct 23, 2010 10:12 am Subject: Re: [Mailman-Users] Mailman mailing lists are gone!
Dale & Lora Marshall wrote:
Using Mailman version: 2.1.12rc2
For some reason all of my mailing lists are now disconnected from mailman.
There is data in /usr/local/mailman/lists, and also lots of data in the
archives/private dir. But when I try to go to the admin page on any list I get
a "list does not exist" message. I did a yum update the other day.
What has happened and how do I fix it?
I haven't a clue?
What did you update with Yum?
Do you see any lists on the admin or listinfo overview pages?
What does /usr/local/mailman/bin/list_lists report?
Second question:
In my Apache logfile I'm getting the following warning:
[Sat Oct 23 09:44:08 2010] [warn] The Alias directive in /etc/httpd/conf/httpd.conf
at line 583 will probably never match because it overlaps an earlier Alias.
[Sat Oct 23 09:44:08 2010] [warn] The ScriptAlias directive in
/etc/httpd/conf/httpd.conf at line 584 will probably never match because it
overlaps an earlier ScriptAlias.
The two lines in question are:
#
# MailMan Settings
#
Alias /pipermail/ "/usr/local/mailman/archives/public/"
ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/"
I don't remember seeing this before I did a yum update the other day.
Aha. Now I have a clue. The Yum update most likely installed a Mailman
package which is now being accessed by Apache and has no lists. There
is most likeley now a /etc/httpd/conf.d/mailman file containing "Alias
/pipermail/" and "ScriptAlias /mailman/" directives pointing tothis new installation. Remove that file. Then you'll also have to
figure out if other things such as aliases or other MTA stuff were
clobbered by the Yum update. Possibly just doing "yum remove mailman"
will fix things as long as there are no other conflicts between the
package yum installed and your existing Mailman.
--
Mark Sapiro <mark@msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
Dale & Lora Marshall wrote:
I did a yum update and then a "yum install mailman".
That was your mistake. Your Mailman was apparently installed from a source distribution, not from a yum package. You should not have done "yum install mailman" and you should probably now do "yum remove mailman" so that a future yum update does not create the same problem.
If you want to update Mailman, dounload the current version from <https://launchpad.net/mailman/2.1/2.1.14> and configure and install it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Using Mailman version: 2.1.12rc2
For some reason all of my mailing lists are now disconnected from mailman. There is data in /usr/local/mailman/lists, and also lots of data in the archives/private dir. But when I try to go to the admin page on any list I get a "list does not exist" message. I did a yum update the other day.
What has happened and how do I fix it?
Second question:
In my Apache logfile I'm getting the following warning:
[Sat Oct 23 09:44:08 2010] [warn] The Alias directive in /etc/httpd/conf/httpd.conf at line 583 will probably never match because it overlaps an earlier Alias. [Sat Oct 23 09:44:08 2010] [warn] The ScriptAlias directive in /etc/httpd/conf/httpd.conf at line 584 will probably never match because it overlaps an earlier ScriptAlias.
The two lines in question are:
# # MailMan Settings # Alias /pipermail/ "/usr/local/mailman/archives/public/" ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/"
I don't remember seeing this before I did a yum update the other day.
Thanks.
- Dale
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Dale & Lora Marshall Internet Marketing Services
http://www.SpottedDragon.com/ http://www.internet-ms.com
marshall@cliffhanger.com dalem@internet-ms.com
loram@internet-ms.com-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Dale & Lora Marshall wrote:
I haven't a clue?
What did you update with Yum?
Do you see any lists on the admin or listinfo overview pages?
What does /usr/local/mailman/bin/list_lists report?
Aha. Now I have a clue. The Yum update most likely installed a Mailman package which is now being accessed by Apache and has no lists. There is most likeley now a /etc/httpd/conf.d/mailman file containing "Alias /pipermail/" and "ScriptAlias /mailman/" directives pointing to this new installation. Remove that file. Then you'll also have to figure out if other things such as aliases or other MTA stuff were clobbered by the Yum update. Possibly just doing "yum remove mailman" will fix things as long as there are no other conflicts between the package yum installed and your existing Mailman.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
I did a yum update and then a "yum install mailman". I run a server with a lot of domains on it and a few of them have mailing lists but not all.
list_lists reports 17 mailing lists which is I believe correct.
There was a mailman.conf file in the conf.d dir. Thanks! I moved it to a different name (just in case) and now I can at least see the two lists I maintain. I'll email the guy with the other lists and see if he's ok now.
Thanks again!
- Dale
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Dale & Lora Marshall Internet Marketing Services
http://www.SpottedDragon.com/ http://www.internet-ms.com
marshall@cliffhanger.com dalem@internet-ms.com
loram@internet-ms.com-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-----Original Message----- From: Mark Sapiro <mark@msapiro.net> To: Dale & Lora Marshall <marshall@cliffhanger.com>; mailman-users@python.org Sent: Sat, Oct 23, 2010 10:12 am Subject: Re: [Mailman-Users] Mailman mailing lists are gone!
Dale & Lora Marshall wrote:
Using Mailman version: 2.1.12rc2
For some reason all of my mailing lists are now disconnected from mailman.
There is data in /usr/local/mailman/lists, and also lots of data in the
archives/private dir. But when I try to go to the admin page on any list I get
a "list does not exist" message. I did a yum update the other day.
What has happened and how do I fix it?
I haven't a clue?
What did you update with Yum?
Do you see any lists on the admin or listinfo overview pages?
What does /usr/local/mailman/bin/list_lists report?
Second question:
In my Apache logfile I'm getting the following warning:
[Sat Oct 23 09:44:08 2010] [warn] The Alias directive in /etc/httpd/conf/httpd.conf
at line 583 will probably never match because it overlaps an earlier Alias.
[Sat Oct 23 09:44:08 2010] [warn] The ScriptAlias directive in
/etc/httpd/conf/httpd.conf at line 584 will probably never match because it
overlaps an earlier ScriptAlias.
The two lines in question are:
#
# MailMan Settings
#
Alias /pipermail/ "/usr/local/mailman/archives/public/"
ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/"
I don't remember seeing this before I did a yum update the other day.
Aha. Now I have a clue. The Yum update most likely installed a Mailman
package which is now being accessed by Apache and has no lists. There
is most likeley now a /etc/httpd/conf.d/mailman file containing "Alias
/pipermail/" and "ScriptAlias /mailman/" directives pointing tothis new installation. Remove that file. Then you'll also have to
figure out if other things such as aliases or other MTA stuff were
clobbered by the Yum update. Possibly just doing "yum remove mailman"
will fix things as long as there are no other conflicts between the
package yum installed and your existing Mailman.
--
Mark Sapiro <mark@msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
Dale & Lora Marshall wrote:
I did a yum update and then a "yum install mailman".
That was your mistake. Your Mailman was apparently installed from a source distribution, not from a yum package. You should not have done "yum install mailman" and you should probably now do "yum remove mailman" so that a future yum update does not create the same problem.
If you want to update Mailman, dounload the current version from <https://launchpad.net/mailman/2.1/2.1.14> and configure and install it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
b19141＠anl.gov -
Dale & Lora Marshall -
Mark Sapiro