Re: [Mailman-Users] Corrupted archives ...
Glenn Sieb wrote: I'm running mailman-2.1.12, with the htdig patches on FreeBSD 7.0 I have a list with archives that are about 10 years old. The archive mbox size is 175M. I was alerted by a subscriber that the August 2009 archives list 128 No subject emails that look funny. So I looked.. sure enough they're there. And they look something like this when I click on a single email listed in the archives: No subject Mon Aug 10 18:53:40 EDT 2009 * Previous message: [Redacted] Blah... * Next message: No subject * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Tue, 14 Dec 1999 23:27:19 PST X-Originating-IP: [63.11.227.157] From: redacted redacted_at... To: redacted Date: Tue, 14 Dec 1999 23:27:19 PST Mailing-List: contact redacted X-Mailing-List: redacted Precedence: bulk List-Help: http://www.example.com/redacted/info.html, mailto:redacted at example.com List-Unsubscribe: mailto:redacted-unsubscribe at example.com List-Archive: http://www.example.com/redacted/ Reply-To: redacted Subject: [Redacted] Redacted MIME-Version: 1.0 Content-Type: text/plain; format=flowed Content-Transfer-Encoding: 7bit Status: RO Content-Length: 7352 Lines: 174 (body of email starts here) From Redacted redacted at u... Wed Dec 15 00:40:19 1999 Delivered-To: redacted Received: (listserv 1.291); by f7; 15 Dec 1999 08:43:59 - Delivered-To: redacted Date: 15 Dec 99 03:44:15 EST From: Redacted redacted at u... To: redacted X-Mailing-List: redacted Precedence: bulk List-Help: http://www.example.com/redacted/info.html, mailto:redacted at example.com List-Unsubscribe: mailto:redacted-unsubscribe at example.com List-Archive: http://www.example.com/redacted/ Reply-To: redacted Subject: [Redacted] RedactedMIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable (body of email starts here...) (another email starts here, as above...) (end of example) Everything looks fine if I use mutt -f listname.mbox in the private archives directory for the list. Has anyone had problems like this? My GoogleFu is failing me, or at least isn't showing me anything like this. Do you see these Dec. 1999 messages when you look with Mutt? There is a problem with a Debian patch, but the symptom is somewhat different, and you're on FreeBSD anyway, so I don't think this is it. It looks like someone or some script ran bin/arch on Mon Aug 10 18:53:40 EDT 2009 (and possibly at other times) with some spurious input, but I'm not sure what that input would be. The puzzling part is the Previous/Next/Sorted header which only appears in the periodic index files. As Terry suggests, you could run bin/cleanarch as an additional test/correction on the listname.mbox. There may be unescaped From in message bodies that didn't confuse Mutt or that you didn't notice with Mutt, and then run bin/arch --wipe to rebuild the archive. But also be aware as Terry says that this may renumber messages and break saved links to archived messages. An alternative alternative is to just remove 2009-August/, 2009-August.txt and 2009-August.txt.gz (if any) from archives/private/listname/ and then run bin/arch (without --wipe) with input just consisting of the Aug, 1999 portion of listname.mbox. But the real questions are how did this happen; do the 128 messages all have Mon Aug 10 18:53:40 EDT 2009 timestamps or do they have different timestamps, and what may have been done at that/those times? -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Users' names on roster page
Eric Shubert wrote: I would like to see the users' names (which I know are optional) on the List Subscribers page (http://domain/mailman/roster/list). Is there an option for this that I missed, or would it require a program change? It's in Mailman 2.2 (not released yet). There is a 2.1 patch (apparently reversed) at http://sourceforge.net/tracker/index.php?func=detailaid=932383group_id=103atid=300103 and the 2.2 change (slightly different) is at http://bazaar.launchpad.net/~mailman-coders/mailman/2.2/revision/1034. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Bounce processing not working
Lindsay Haisley fmouse-mail...@fmp.com Date: Tue, 11 Aug 2009 13:02:55 -0500 To: mailman-users@python.org Cc: Slim Richey s...@ridgerunner.com I have a list (several lists, actually) running on Mailman 2.1.11 and it looks as if bounce processing is broken. On the list in question, the following are set: bounce_processing = Yes bounce_score_threshold = 1.0 bounce_info_stale_after = 1 bounce_you_are_disabled_warnings = 0 bounce_you_are_disabled_warnings_interval = 7 /var/lib/mailman/logs/bounce shows many entry lines of this form, in sets of 3 as shown below: Aug 11 12:35:24 2009 (19017) listname: u...@hotmail.com bounce score: 1.0 Aug 11 12:35:24 2009 (19017) listname: u...@hotmail.com disabling due to bounce score 1.0 = 1.0 Aug 11 12:35:24 2009 (19017) listname: u...@hotmail.com deleted after exhausting notices However, looking at the subscription roster or grepping for u...@hotmail.com using list_members indicates that the user is still subscribed, with no nomail flag set, and no notice is sent to the list owner. This is a bug introduced in 2.1.11 and fixed in 2.1.12. You should be seeing errors in Mailman's error log too. The attached Bouncer_patch.txt will fix it. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan === modified file 'Mailman/Bouncer.py' --- Mailman/Bouncer.py 2008-06-20 19:47:28 + +++ Mailman/Bouncer.py 2009-02-16 16:53:20 + @@ -1,4 +1,4 @@ -# Copyright (C) 1998-2008 by the Free Software Foundation, Inc. +# Copyright (C) 1998-2009 by the Free Software Foundation, Inc. # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License @@ -163,8 +163,10 @@ # We've set/changed bounce info above. We now need to tell the # MemberAdaptor to set/update it. We do it here in case the # MemberAdaptor stores bounce info externally to the list object to -# be sure updated information is stored. -self.setBounceInfo(member, info) +# be sure updated information is stored, but we have to be sure the +# member wasn't removed. +if self.isMember(member): +self.setBounceInfo(member, info) def disableBouncingMember(self, member, info, msg): # Initialize their confirmation cookie. If we do it when we get the -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] How do I kill a message in the middle ofbeingdistributed?
J.A. Terranson wrote: # bin/show_qfiles ./qfiles/in ./qfiles/in Traceback (most recent call last): File bin/show_qfiles, line 95, in module main() File bin/show_qfiles, line 81, in main fp = open(filename) IOError: [Errno 21] Is a directory bin/show_qfiles takes file arguments, not directories. You could do bin/show_qfiles ./qfiles/in/* but it would probably be good to do ls ./qfiles/in/ first to verify there are files there to show. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] New, odd issue... WAS: Fixed (never mind) WAS: How do I kill a message...
J.A. Terranson wrote: I have four lists, yet three of them are OK, thie first is giving errors, but not in the error file. Ideads When I browse to it it sits *forever*, then said Opps, we had na error! Ichedked the error file, and nothing... Check for stale locks. See the FAQ at http://wiki.list.org/x/noA9. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Bounce processing not working - Update
Lindsay Haisley wrote: I restarted (twice) the qrunner suite of processes from the system command line using the system init scripts (/etc/init.d/mailman) with two noticeable results. First, an egregious number of Bounce action notifications and list unsubscribe notifications went out on bounces for lists on which I'm listed as an owner, including the one that brought this problem to my attention. Some notifications date back a couple of months so this is apparently a problem of some duration. I would have to see the /etc/init.d/mailman script to know for sure, but I'm guessing there is something in it that recovers old, stale bounce-events-p.pck files. These files were left behind with the offending bounces when the 2.1.11 bug threw the exception that caused BounceRunner to die without saving the updated list with the bouncing member removed. Note that this bug, addressed in my earlier reply, only occurs when bounce_you_are_disabled_warnings = 0. Second, many subscribers to the problem list received multiple copies of the most recently queued post. Could this be because I stopped and restarted the qrunners several times? Why would this cause multiple copies to be sent? Yes, it could be. You stopped Mailman which signalled OutgoingRunner to stop in the middle of delivering the post. If somehow OutgoingRunner was SIGKILL'd, it would have stopped mid-delivery and when mailman restarted, the backup out queue entry was recovered and the post was delivered to all list members, some of whom had been delivered before. However this is not what normally happens. It is supposed to be SIGTERM'd and finish it's current delivery. Perhaps there's something in the init.d script that will SIGKILL it if it doesn't stop soon enough, or perhaps Mailman was restarted before OutgoingRunner finished and the new OutgoingRunner 'recovered' the old runner's backup queue entry, but this would result in everyone receiving a duplicate unless something outbound of Mailman dropped the duplicate message. I should also note that the bouncing subscribers were _still_ not unsubscribed, nor was the nomail flag set for those for whom a soft bounce was received. This is the 2.1.11 bug addressed in my earlier reply. All qrunner processes were (and are still) running, or at least according to the process table. Can these processes crash? If so, what can I do to prevent this? If I need to restart the qrunners, how do I avoid causing multiple copies of posts to be sent out? Yes, qrunners can die. Just look at Mailman's qrunner and error logs. Normally, when a qrunner dies, it is automatically restarted by mailmanctl up to 10 restarts. Duplicates are a pain, and every effort is taken to avoid or minimize them, but if a runner dies, due to an uncaught exception, the message is normally shunted and requires manual action to reprocess, and even this normally doesn't result in duplicates. Duplicates can occur when a runner is killed asynchronously by a system crash, power failure or perhaps in your case, by your init.d script, but normally, a simple mailmanctl stop|restart should just signal the runners, and they shouldn't stop until finished with the current task. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Bounce processing not working - Update
Mark, thanks for your knowledgeable and _very_ helpful post! On Wed, 2009-08-12 at 09:41 -0700, Mark Sapiro wrote: Lindsay Haisley wrote: First, an egregious number of Bounce action notifications and list unsubscribe notifications went out on bounces for lists on which I'm listed as an owner, including the one that brought this problem to my attention. Some notifications date back a couple of months so this is apparently a problem of some duration. I would have to see the /etc/init.d/mailman script to know for sure, but I'm guessing there is something in it that recovers old, stale bounce-events-p.pck files. These files were left behind with the offending bounces when the 2.1.11 bug threw the exception that caused BounceRunner to die without saving the updated list with the bouncing member removed. The Gentoo init script for mailman is pretty simple. It executes, as user 'mailman', mailmanctl -s start, mailmanctl stop and mailmanctl restart for the standard init script arguments of start, stop and restart. That's all. Note that this bug, addressed in my earlier reply, only occurs when bounce_you_are_disabled_warnings = 0. I found a thread on the Gentoo bug reporting list which discusses compatibility issues between Mailman 2.1.11 and Python 2.6, also possibly 2.5 (which I'm running on these boxes). Gentoo is distributing mm 2.1.11 with stable as of yesterday, and 2.1.12 with unstable, but they're apparently pushing to stabilize 2.1.12 ahead of schedule since Python 2.6 is now stable in the distribution. I expect this to happen I installed Mailman 2.1.12 from Gentoo unstable and at least the problem with non-removal of bouncing addresses seems to have gone away. Perhaps the qrunner processes will also be more stable. Duplicates can occur when a runner is killed asynchronously by a system crash, power failure or perhaps in your case, by your init.d script, but normally, a simple mailmanctl stop|restart should just signal the runners, and they shouldn't stop until finished with the current task. Apparently something strange went down, since all the init.d script does is execute mailmanctl, as noted above. -- Lindsay Haisley | The difference between a duck is because FMP Computer Services |one leg is both the same 512-259-1190 | - Anonymous http://www.fmp.com| -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Bounce processing not working - Update
On Wed, 2009-08-12 at 13:02 -0500, Lindsay Haisley wrote: I found a thread on the Gentoo bug reporting list which discusses compatibility issues between Mailman 2.1.11 and Python 2.6, also possibly 2.5 (which I'm running on these boxes). Gentoo is distributing mm 2.1.11 with stable as of yesterday, and 2.1.12 with unstable, but they're apparently pushing to stabilize 2.1.12 ahead of schedule since Python 2.6 is now stable in the distribution. As of today, MM 2.1.12 is in Gentoo stable. -- Lindsay Haisley | In an open world,| PGP public key FMP Computer Services |who needs Windows | available at 512-259-1190 | or Gates| http://pubkeys.fmp.com http://www.fmp.com| | -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Multiple instances of Mailman on FreeBSD
I'm posting this to both the mailman-users list and the freebsd-ports list. I realize that not all follow-up will make it to both lists. I would like to set up multiple instances of Mailman on a FreeBSD 7- STABLE system with using Postfix. Looking at the ports Makefile, it appears that if I set MM_DIR=mailman/vhosts/domain-for-this-instance everything should work file (plus add FORCE_PACKAGE_REGISTER allow this second instance to be installed.) But when I do % cd /usr/ports/mail/mailman % sudo make -DMM_DIR=mailman/vhosts/lists.wilson-pta.org - DFORCE_PKG_REGISTER install It just installs in the default location, /usr/local/mailman And this paradoxical report of various settings $ sudo make MM_DIR=mailman/vhosts/lists.wilson-pta.org - DFORCE_PKG_REGISTER install === Found saved configuration for mailman-2.1.12 You may change the following build options: MM_USERNAME=mailman The username of the Mailman user. MM_USERID=91The user ID of the Mailman user. MM_GROUPNAME=mailmanThe group to which the Mailman user will belong. MM_GROUPID=MM_USERIDThe group ID for the Mailman user. MM_DIR=mailman Mailman will be installed in /usr/local/mailman/vhosts/ lists.wilson-pta.org. CGI_GID=www The group name or id under which your web server executes CGI scripts. IMGDIR=www/iconsIcon images will be installed in /usr/local/www/icons. Notice the conflicting information on the line telling me about MM_DIR. Background on the issue As is well known to mailman users, mailman 2.X does not fully deal with virtual mail domains in that, say pta-bo...@lists.shepard-families.org And pta-bo...@lists.wilson-pta.org would have to be the same list. That is mailman does not provide a separate namespace for lists in different domains. The Wiki/FAQ at http://wiki.list.org/pages/viewpage.action?pageId=4030604 hints at patches (which I can't seem to locate) and mailing list discussion mentions an alternative of having a separate instance of Mailman for each virtual domain. This later approach seems easier if you don't anticipate having loads of domains. So that is what I intend to do. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Multiple instances of Mailman on FreeBSD
Jeffrey Goldberg wrote: I'm posting this to both the mailman-users list and the freebsd-ports list. I realize that not all follow-up will make it to both lists. I would like to set up multiple instances of Mailman on a FreeBSD 7-STABLE system with using Postfix. Looking at the ports Makefile, it appears that if I set MM_DIR=mailman/vhosts/domain-for-this-instance everything should work file (plus add FORCE_PACKAGE_REGISTER allow this second instance to be installed.) Personally, I wouldn't use the ports version if you want to do multiple instances of Mailman. I would install each version from our official source tarballs that you can download from www.list.org and ftp.gnu.org. Alternatively, if you want to use the ports version, then I would keep it simple and serve only one domain. Otherwise, I would recommend that you find the port maintainer for Mailman, and discuss this subject with them. Hopefully, they would know enough about both sides of the problem to be able to recommend a solution or patch for you. -- Brad Knowles b...@shub-internet.org LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] MM 2.1.12 in Gentoo stable - NOT!
On Wed, 2009-08-12 at 13:30 -0500, Lindsay Haisley wrote: As of today, MM 2.1.12 is in Gentoo stable. I mis-spoke. Apparently this isn't yet the case, although I would expect it to be so within a week or so. Sorry -- Lindsay Haisley | Everything works if you let it FMP Computer Services | (The Roadie) 512-259-1190 | http://www.fmp.com| -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Multiple instances of Mailman on FreeBSD
On Aug 12, 2009, at 2:12 PM, Brad Knowles wrote: Jeffrey Goldberg wrote: I would like to set up multiple instances of Mailman on a FreeBSD 7- STABLE system with using Postfix. Personally, I wouldn't use the [FreeBSD] ports version if you want to do multiple instances of Mailman. I would install each version from our official source tarballs that you can download from www.list.org and ftp.gnu.org. The FreeBSD Ports version contains a couple of patches which might be useful, though some are merely cosmetic. It also knows how to find the right gid and uid for working with various MTAs. Postfix, as we know, is finicky, and this port really does help people get it right. Otherwise, I would recommend that you find the port maintainer for Mailman, and discuss this subject with them. Already on the cc-line Anyway, what I have found is that if I manually edit the ports/mail/ mailman/Makefile to change #MM_DIR?= mailman MM_DIR?=mailman/vhosts/lists.wilson-pta.org The install works as expected, even though when I specified -DMM_DIR on the command line it worked for some purposes (built files contained the correct string in them) but not for other purposes (the files installed in the wrong place). So I suspect that the install stage must re-read the Makefile. So I do now have this other instance installed. One thing that I (and others doing things this way) will have to take care of is the startup script, /usr/local/etc/rc.d/mailman, for the queue runner. This installation did overwrite the original. So I'm either going to have to manually combine these in one startup script or set up a separate script for each instance. I'm sure that there will be other things to watch out for as well. I hope to contribute to the Wiki on this once I've got everything running. Let me just say that I am eagerly looking forward to Mailman 3. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Multiple instances of Mailman on FreeBSD
On Aug 12, 2009, at 3:21 PM, Paul Schmehl wrote:
--On Wednesday, August 12, 2009 13:55:18 -0500 Jeffrey Goldberg jeff...@goldmark.org
wrote:
I'm posting this to both the mailman-users list and the freebsd-ports
list. I realize that not all follow-up will make it to both lists.
But when I do
% cd /usr/ports/mail/mailman
% sudo make -DMM_DIR=mailman/vhosts/lists.wilson-pta.org -
DFORCE_PKG_REGISTER install
It just installs in the default location, /usr/local/mailman
This could be a really stupid question (because I've never tried to
do what you're doing), but shouldn't the above line be:
$ sudo make MM_DIR=/mailman/vhosts/lists.wilson-pta.org
In other words, don't you have to provide the *absolute* patch to
the install location?
No. Reading the Makefile it is clear that MM_DIR is relative to $PREFIX
The default setting in the Makefile is
MM_DIR?= mailman
And later on there is a
MAILMANDIR= ${PREFIX}/${MM_DIR}
With MAILMANDIR being the absolute install directory.
The problem is, I'm not exactly sure *where* you want mailman to
install, so it's hard to be correct without more information.
Mailman (under normal defaults) installs in various directories under
/usr/local/mailman
The python for all of the CGIs lives in
/usr/local/mailman/Mailman
and the programs that an administrator might run on the command line
live in
/usr/local/mailmain/bin
And there are various other directories for queues and logs and data
and per list configurations and such
I want to have instances installed in
/usr/local/mailman/vhosts/site1
/usr/local/mailman/vhosts/site2
/usr/local/mailman/vhosts/site3
Cheers,
-j
--
Jeffrey Goldberghttp://www.goldmark.org/jeff/
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Multiple instances of Mailman on FreeBSD
On Aug 12, 2009, at 3:38 PM, Mel Flynn wrote: On Wednesday 12 August 2009 11:40:47 Bill Moran wrote: Were it me, I'd add jails to the system. [...] That's obviously not the only way to get what you want, just my suggestion. And mine. Thank you and Bill for the jail suggestion. I've never played with jails, as I really only have one public IP address available. FORCE_PKG_REGISTER abuse will hurt you sooner or later. I am living in fear of that. If you must, then set PKG_DBDIR, PORT_DBDIR and PREFIX correctly. I don't understand the Package and Port databases well enough to actually set them correctly, so I do suspect that I am causing trouble for myself this way. But things get much easier if you use seperate jails and a postfix in mailhub mode on the main IP if you have only one incoming IP. Ah. I hadn't thought of that. I do only have one IP. I hadn't realized that I could set up private addresses on the same host. Would the postfix on the main IP be able to run scripts that are on individual jails? If not, I'd have to set up a listening postfix in each jail which would accept mail forwarded to it only from the main IP. For outgoing mail, mailman can talk SMTP to a remote mail server. Another point of confusion with jails is that the HTTP interface for mailman would need to be on the public IP, but would need to access the appropriate mailman data that live within jails. So I really think that unless I can do full jails, each with their own SMTP and HTTP daemons on their own public IPs, this would be very complicated to maintain. But I am only guessing here as I don't really know what can and can't be done easily with jails. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Postfix vdomains with multiple instances of mailman
In trying to get things like pta-bo...@one-domain.example and pta-bo...@second-domain.example to be distinct lists on a site that is hosting both of those domains, I attempted to install multiple instances of Mailman on the same host. That is advice that I saw somewhere on this list. Unfortunately, it is still not working for me. From the web end of things it is actually working fine. Within the virtual domains in the Apache configuration file for each domain, I point to their respective (and distinct) mailman installations. But I am still having problems separating these as far as Postfix is concerned. For one mailman instance, I will have in /usr/local/mailman/vhosts/lists.wilson-pta.org/data/virtual-domains # STANZA START: pta-board # CREATED: Wed Aug 12 17:17:42 2009 pta-bo...@lists.wilson-pta.org pta-board pta-board-ad...@lists.wilson-pta.orgpta-board-admin pta-board-boun...@lists.wilson-pta.org pta-board-bounces pta-board-conf...@lists.wilson-pta.org pta-board-confirm pta-board-j...@lists.wilson-pta.org pta-board-join etc. And in /usr/local/mailman/data/virtual-domain # STANZA START: pta-board # CREATED: Fri Mar 30 14:20:25 2007 pta-bo...@lists.shepard-families.org pta-board pta-board-ad...@lists.shepard-families.orgpta-board-admin pta-board-boun...@lists.shepard-families.org pta-board-bounces pta-board-conf...@lists.shepard-families.org pta-board-confirm pta-board-j...@lists.shepard-families.org pta-board-join etc. The problem is that right hand side of those, something like pta-board-confirm with no domain at all, should sometimes go to the alias defined in /usr/local/mailman/data/aliases which says pta-board-bounces: |/usr/local/mailman/mail/mailman bounces pta-board But at other times, it should get delivered to the alias specified in /usr/local/mailman/vhosts/lists.wilson-pta.org/data/aliases which says pta-board-confirm: |/usr/local/mailman/vhosts/lists.wilson- pta.org/mail/mailman confirm pta-board Anyway, in my set up, it's always going to the first one first (which is listed earlier in postfix/main.cf) Both these aliases files and both virtual-domains files are generated by Mailman. So I don't see where I have scope to fix things. I would like to know how people who have run multiple instances of mailman have managed to keep lists in different namespaces. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Postfix vdomains with multiple instances of mailman
Jeffrey Goldberg writes: For one mailman instance, I will have in /usr/local/mailman/vhosts/lists.wilson-pta.org/data/virtual-domains # STANZA START: pta-board # CREATED: Wed Aug 12 17:17:42 2009 pta-bo...@lists.wilson-pta.org pta-board /usr/local/mailman/data/virtual-domain # STANZA START: pta-board # CREATED: Fri Mar 30 14:20:25 2007 pta-bo...@lists.shepard-families.org pta-board I don't know Postfix well enough to tell you *how* to do it, but note that Mailman doesn't care what the addresses you use are. So the bounce address, which you seem to want to be common (why? aren't the Mailman instances separate?), can be pta-board-bounces-common for all the domains and lists, while the confirm addresses can be pta-board-confirm-shepard-families and pta-board-confirm-wilson-pta respectively. Or they can be mm1 ... mmas-many-as-you-need for that matter. ;-) Anyway, in my set up, it's always going to the first one first (which is listed earlier in postfix/main.cf) In exim, it is possible to set up multiple routers so that something that is incoming for lists.shepard-families.org uses a separate configuration in all ways from lists.wilson-pta.org. Maybe a similar effect can be achieved with Postfix? Both these aliases files and both virtual-domains files are generated by Mailman. So I don't see where I have scope to fix things. I would like to know how people who have run multiple instances of mailman have managed to keep lists in different namespaces. By hand, my man, by hand. I second Brad's recommendation to install each instance of Mailman from upstream sources rather than via a package. You should check the patches applied by your distro to see if there any you want, but usually they're not very useful -- mostly they wrench Mailman's configuration into some preconceived scheme, very often at great cost in flexibility. (This is not a bad thing in the context of a distro wanting to provide seamless installation, but it could screw somebody with requirements like yours royally.) Please note that neither the distros nor the Mailman maintainers have a mission to support you (ie, whatever it is that keeps them doing their work, it doesn't apply to your use case). Their focus is on mainstream users, which for most distros is SOHO-type installations and personal workstations, not vhosting, and for Mailman is people running a coherent set of mailing lists themselves. This is a historical thing for Mailman; Barry and Mark have long since signed on to better support for vhosters, but practically speaking that has to come in MM3; it would seriously destabilize MM2. I wouldn't bet on it changing in the distros soon though. So the bottom line is you will have to do much of the config work by hand for the foreseeable future, and on the one hand installing Mailman from upstream source is tiny compared to the rest of the work you do, and on the other makes it much easier for Mailman people who don't know your distro to help. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Corrupted archives ...
Mark Sapiro said the following on 8/12/09 10:05 AM: Do you see these Dec. 1999 messages when you look with Mutt? *doublechecking* Yes. They look fine. It looks like someone or some script ran bin/arch on Mon Aug 10 18:53:40 EDT 2009 (and possibly at other times) with some spurious input, but I'm not sure what that input would be. The puzzling part is the Previous/Next/Sorted header which only appears in the periodic index files. Yup. My archives are indexed automagically by Month-Year... As Terry suggests, you could run bin/cleanarch as an additional test/correction on the listname.mbox. There may be unescaped From in message bodies that didn't confuse Mutt or that you didn't notice with Mutt, and then run bin/arch --wipe to rebuild the archive. But also be aware as Terry says that this may renumber messages and break saved links to archived messages. *nods* This is an instance where I may have to go through manually with vi and fix this email-by-email. :sigh: It will take forever, considering there are 55k or so messages in the archive. An alternative alternative is to just remove 2009-August/, 2009-August.txt and 2009-August.txt.gz (if any) from archives/private/listname/ and then run bin/arch (without --wipe) with input just consisting of the Aug, 1999 portion of listname.mbox. Ooh. Let me try that one. But the real questions are how did this happen; do the 128 messages all have Mon Aug 10 18:53:40 EDT 2009 timestamps or do they have different timestamps, and what may have been done at that/those times? It was probably one of the times I ran arch --wipe. And yes, they all have the same timestamp in the archives. Let me try re-running the arch command with the 2009-August* files removed Odd. I had to manually create the 2009-August directory, but the problem is still there. :-/ (I did bin/arch (listname)) Thanks, Mark! --Glenn -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
