[Mailman-Users] bin/arch failing
Hi: I am having a problem regenerating my archive. Everything was going along fine, with daily updates being added to the archive. I then wanted to refresh the entire archive and ran bin/arch --wipe list1 it failed. Archive articles go from to 66990 list1.mbox is: 526313754 Aug 21 20:19 list1.mbox The server NetBSD 3.1, has 2GB memory bin/arch first went through every article Week-of-Mon-20070702 #65136 [EMAIL PROTECTED] figuring article archives [...] then after many Updating HTML for article 4584 Updating HTML for article 4585 Updating HTML for article 4586 Updating index files for archive [Week-of-Mon-20050321] Date Subject Author Thread Computing threaded index Updating HTML for article 4587 Updating HTML for article 4588 Updating HTML for article 4589 Updating HTML for article 4590 Updating HTML for article 4591 Updating HTML for article 4592 Updating HTML for article 4593 [...] Updating HTML for article 9353 Updating index files for archive [Week-of-Mon-20041122] Traceback (most recent call last): File bin/arch, line 200, in ? main() File bin/arch, line 190, in main archiver.close() File /usr/pkg/lib/mailman/Mailman/Archiver/pipermail.py, line 322, in close self.update_dirty_archives() File /usr/pkg/lib/mailman/Mailman/Archiver/pipermail.py, line 538, in update_dirty_archives self.update_archive(i) File /usr/pkg/lib/mailman/Mailman/Archiver/HyperArch.py, line 1121, in update_archive self.__super_update_archive(archive) File /usr/pkg/lib/mailman/Mailman/Archiver/pipermail.py, line 439, in update_archive self.__set_parameters(archive) File /usr/pkg/lib/mailman/Mailman/Archiver/pipermail.py, line 354, in __set_parameters firstdate = self.database.firstdate(archive) File /usr/pkg/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 209, in firstdate self.__openIndices(archive) File /usr/pkg/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 240, in __openIndices self.__closeIndices() File /usr/pkg/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 265, in __closeIndices index.close() File /usr/pkg/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 187, in close fp.write(marshal.dumps(self.dict)) MemoryError So I ran a subset of the archive: bin/arch -s 1 -e 66990 list1 And after a while: Updating HTML for article 11689 Updating HTML for article 11690 Updating index files for archive [Week-of-Mon-20050815] Traceback (most recent call last): File bin/arch, line 200, in ? main() File bin/arch, line 190, in main archiver.close() File /usr/pkg/lib/mailman/Mailman/Archiver/pipermail.py, line 322, in close self.update_dirty_archives() File /usr/pkg/lib/mailman/Mailman/Archiver/pipermail.py, line 538, in update_dirty_archives self.update_archive(i) File /usr/pkg/lib/mailman/Mailman/Archiver/HyperArch.py, line 1121, in update_archive self.__super_update_archive(archive) File /usr/pkg/lib/mailman/Mailman/Archiver/pipermail.py, line 439, in update_archive self.__set_parameters(archive) File /usr/pkg/lib/mailman/Mailman/Archiver/pipermail.py, line 354, in __set_parameters firstdate = self.database.firstdate(archive) File /usr/pkg/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 209, in firstdate self.__openIndices(archive) File /usr/pkg/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 240, in __openIndices self.__closeIndices() File /usr/pkg/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 265, in __closeIndices index.close() File /usr/pkg/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 187, in close fp.write(marshal.dumps(self.dict)) MemoryError _dirty_archives ??? something corrupt? Is there a fix for this? I can successfully run about the last 10,000 bin/arch -s 5 -e 66990 list1 But that is about 1/7th of the archive Can I produce a complete archive in chunks of 10,000? How? Best regards Bob -- 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://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] a few questions about the NNTP gateway
Barry Finkel ha scritto: [...] The patches were, for the most part, undocumented, so I had no idea exactly what they did. Nor did I know if they would fit into the 2.1.9 source, as some of the patches were based on pre-2.1.5 code. Manlio Perillo replied: This was unexpected! Do you have opened a bug report? No, because [...] 2) I have no idea if there is a bug. I Manlio Perillo replied: Sorry for the late response. I think that the lack of documentation in the code can be considered a bug. Then I would have to file a bug report on almost all of the Debian/Ubuntu patches to Mailman. I looked at them all, and I discarded most. I kept a few that were related to where libraries were put. I was not interested in making source code modifications where 1) I don't fully understand the source that comes from SourceForge, and 2) there is no documentation as to what the Debian changes do. It would be nice to know what each change does, but since I am not installing most of them, it really does not matter. -- 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 222, Room D209 Internet: [EMAIL PROTECTED] Argonne, IL 60439-4828 IBMMAIL: I1004994 -- 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://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] bin/arch failing
Bob wrote: Everything was going along fine, with daily updates being added to the archive. I then wanted to refresh the entire archive and ran bin/arch --wipe list1 it failed. Archive articles go from to 66990 list1.mbox is: 526313754 Aug 21 20:19 list1.mbox The server NetBSD 3.1, has 2GB memory bin/arch first went through every article Week-of-Mon-20070702 #65136 [EMAIL PROTECTED] figuring article archives [...] then after many Updating HTML for article 4584 Updating HTML for article 4585 Updating HTML for article 4586 Updating index files for archive [Week-of-Mon-20050321] Date Subject Author Thread Computing threaded index Updating HTML for article 4587 Updating HTML for article 4588 Updating HTML for article 4589 Updating HTML for article 4590 Updating HTML for article 4591 Updating HTML for article 4592 Updating HTML for article 4593 [...] Updating HTML for article 9353 Updating index files for archive [Week-of-Mon-20041122] Traceback (most recent call last): File bin/arch, line 200, in ? main() File bin/arch, line 190, in main archiver.close() File /usr/pkg/lib/mailman/Mailman/Archiver/pipermail.py, line 322, in close self.update_dirty_archives() File /usr/pkg/lib/mailman/Mailman/Archiver/pipermail.py, line 538, in update_dirty_archives self.update_archive(i) File /usr/pkg/lib/mailman/Mailman/Archiver/HyperArch.py, line 1121, in update_archive self.__super_update_archive(archive) File /usr/pkg/lib/mailman/Mailman/Archiver/pipermail.py, line 439, in update_archive self.__set_parameters(archive) File /usr/pkg/lib/mailman/Mailman/Archiver/pipermail.py, line 354, in __set_parameters firstdate = self.database.firstdate(archive) File /usr/pkg/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 209, in firstdate self.__openIndices(archive) File /usr/pkg/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 240, in __openIndices self.__closeIndices() File /usr/pkg/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 265, in __closeIndices index.close() File /usr/pkg/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 187, in close fp.write(marshal.dumps(self.dict)) MemoryError This problem is mentioned in the description of the -e option of bin/arch --help. I can successfully run about the last 10,000 bin/arch -s 5 -e 66990 list1 But that is about 1/7th of the archive Can I produce a complete archive in chunks of 10,000? How? bin/arch --wipe -e 9 list1 bin/arch -s 1 -e 1 list1 bin/arch -s 2 -e 2 list1 ... bin/arch -s 6 list1 Note that --wipe is specified only on the first command. Also, it is a good idea to stop Mailman during this process. The reason is that if a new message arrives and is archived say between the second and third commands, it will be assigned message number 2 in the new archive, but it will be message number 66991 in the .mbox. This will guarantee that if you ever rebuild the archive again, all message numbers from 2 on will change, thus invalidating any saved archive URLs. Finally, it is a good idea to first check the .mbox file with bin/cleanarch to make sure there are no unescaped From_ lines in message bodies. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] bin/arch failing
Mark Sapiro wrote: bin/arch --wipe -e 9 list1 Ooops! That should be bin/arch --wipe -e list1 bin/arch -s 1 -e 1 list1 bin/arch -s 2 -e 2 list1 ... bin/arch -s 6 list1 -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] (no subject)
We are migrating about 300 lists from majordomo to mailman and would like some help finding how to setup a few properties. We've worked at this a while and been unable to find where/how to set these. (See below for background.) 1. We don't want any 'list owners' or 'moderators'. Just we lucky few admins will run the lists. 2. We want the majority of the lists to be open for users to subscribe/unsubscribe without any passwords required. 3. We want the other very few lists to be setup so only the single list admin(s) adds and removes names from the list. 4. All of the lists are for broadcast only with the majority being used by automated processes that do not react nicely to bounces or other administrivia and are not members of each list. Background: We are producing a large mechatronics application with ~700 developers/testers, etc. Our bug tracking, build and other automated systems generate emails that get broadcast via these lists (the majority of them). The other lists are used by admins for system outage and other such communications. Alan E (Nick) Nicoll DocuSP Problem System Administrator Xerox Corporation Xerox Centre Drive, MS: ESC1-615 El Segundo, CA 90245 Phone 310 333-5081 Internal 8*823-5081 Fax 310 333-6898 [EMAIL PROTECTED] XEROX Technology Document Management Consulting Services www.xerox.com This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you have received this email in error please delete it. Any views or opinions presented in this email are solely those of the sender and do not necessarily represent those of Xerox Corporation. Finally, the recipient should check this email is authentic and examine it for the presence of viruses. Xerox does perform virus checks but cannot accept liability for any damage caused by any virus transmitted by this email. -- 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://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] (no subject)
Nicoll, Alan wrote: We are migrating about 300 lists from majordomo to mailman and would like some help finding how to setup a few properties. We've worked at this a while and been unable to find where/how to set these. (See below for background.) 1. We don't want any 'list owners' or 'moderators'. Just we lucky few admins will run the lists. You don't need 'moderators', but you do need 'owners'. Mailman sends various notices to listname-owner and this is in turn forwarded to the list owner address(es) which should be deliverable. Presumably the owner(s) will be you few lucky admins. 2. We want the majority of the lists to be open for users to subscribe/unsubscribe without any passwords required. I'm not sure what you really are asking. List members have passwords to allow them to authenticate for things like visiting private archives, changing user options and unsubscribing without confirmation, but if they don't need to do these things, they don't need to know/use any password. If you want users to be able to subscribe without confirmation, you need to set ALLOW_OPEN_SUBSCRIBE = Yes in mm_cfg.py and then set the list's Privacy options...-Subscription rules-subscribe_policy to None. Users cannot unsubscribe without either a password, a confirmation email, or admin action. 3. We want the other very few lists to be setup so only the single list admin(s) adds and removes names from the list. Set Privacy options...-Subscription rules-subscribe_policy to Require Aproval and set Privacy options...-Subscription rules-unsubscribe_policy to Yes to prevent users from (un)subscribing themselves and then manage the membership via the admin Membership Management...-Mass Subscription and Mass Removal pages or the bin/add_members and bin/remove_members command line tools. 4. All of the lists are for broadcast only with the majority being used by automated processes that do not react nicely to bounces or other administrivia and are not members of each list. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.011.htp for advice on one-way lists. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Disabling confirmtionless subscriptions by list admins
Hello, I'm a site administrator running mailman 2.1.9 and am beginning to delegate some responsibility to list administrators. While I trust (the integrity of) these people, I am not fully confident that they completely grasp the importance of the confirmation process (particularly since some list members seem to have trouble with it). I do not want any of these list administrators to subscribe anyone (or change email addresses of members) without the member having to go through the confirmation process. To my knowledge, the one place that a list administrator could by- pass the confirmation process for members is on the mass subscription page. Are there other locations as well? And, the heart of my question, can I disable those? 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] (no subject)
On 8/22/07, Nicoll, Alan wrote: 1. We don't want any 'list owners' or 'moderators'. Just we lucky few admins will run the lists. Then use a single central alias or mailing list as the list owner for each of those lists, and have that be directed to your admins. For one site I help administer, listmaster is the registered owner of virtually all mailing lists on the system, and that in turn is an alias which gets sent out to a few admins on the project. 2. We want the majority of the lists to be open for users to subscribe/unsubscribe without any passwords required. If your lists are publicly accessible, this will open you up to being abused as a DDOS facility. Imagine your personal e-mail address being subscribed to several hundred mailing lists that don't do any validation or require any confirmation that you do actually want to be subscribed. If these lists are not publicly accessible, and you have adequate security controls elsewhere, then you should be okay. However, even if the users are directly subscribed and without confirmation, they'll still be issued passwords and those passwords will be sent out to them on a monthly basis, so that they have the ability to log into a web site on your server and manage their subscriptions. I guess you could simply choose not to run the standard cron job for mailpasswds, but that won't prevent the system from generating the passwords for the user, just from having it send out those password reminders on a monthly basis. You're not going to get completely rid of this feature, at least not easily. 3. We want the other very few lists to be setup so only the single list admin(s) adds and removes names from the list. As above, but make sure that these lists require approval (from the list owner/admin staff). 4. All of the lists are for broadcast only with the majority being used by automated processes that do not react nicely to bounces or other administrivia and are not members of each list. Mailman should handle issues with bounces internally, unless the recipient has a broken mail system which sends bounces back to the original sender. You've seen some of that on this list, and I nuked the users in question very quickly, because I didn't want them to get into auto-responder wars with others on the list. That said, you could always configure your automated processes to use a sender address that can handle bounces or auto-replies, and which is on the appropriate white list for each mailing list, so that it no longer matters whether bounces or auto-replies are sent back to the original sender or not. Since you provide the sender address as input to the process when the message is generated, you can make this whatever you want. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 -- 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://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] (no subject)
Brad Knowles wrote: However, even if the users are directly subscribed and without confirmation, they'll still be issued passwords and those passwords will be sent out to them on a monthly basis, so that they have the ability to log into a web site on your server and manage their subscriptions. The sending of reminders is a list option (on General Options/Notifications). It can be defaulted to Off with DEFAULT_SEND_REMINDERS = No in mm_cfg.py. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Disabling confirmtionless subscriptions by listadmins
Jeffrey Goldberg wrote:
To my knowledge, the one place that a list administrator could by-
pass the confirmation process for members is on the mass subscription
page. Are there other locations as well?
The only other way I can think of offhand is to set subscribe_policy to
'Require approval'. Then the admin can request a subscription by email
or listinfo subscribe form and approve the request without a
confirmation from the user.
And, the heart of my
question, can I disable those?
Of course, you can do anything if you're willing to hack the code, but
short of that, all you can do is eliminate the entire Membership
Management... section including the Membership List from the admin
interface.
You probably don't want to do that, but if you did, you'd either copy
the entire ADMIN_CATEGORIES definition from Defaults.py to mm_cfg.py,
but leave out 'members',, or add
del ADMIN_CATEGORIES[ADMIN_CATEGORIES.index('members')]
to mm_cfg.py, but even doing this doesn't stop subscribes with approval
and no confirmation.
--
Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
