[Mailman-Users] List Archives
David Andrews writes: > I want to delete some lists, but would like to save the archives. > Pipermail saves by month, as I have it configured. Is there a way to > obtain an entire archive at once? Are there tools to convert the > MBOX format to something non-technical people can deal with easily? Exactly what is your use case? What do you mean by "obtain"? What do you mean by "non-technical people deal"? I suspect "obtain" means something you don't need to do, and "non-technical people deal" means "click to read". If so, the answer is basically "delete the list, don't delete the archive". That's easiest for the users since they just go to the same place. Best of all the site admin doesn't have to do much of anything besides delete the list configuration file, and possibly edit the MTA config.[1] Note that this can create backscatter (mail rejection notices to third parties0, but that's no different from any other non-existent address at your server. The only problem is if the archives are "members only", because deleting the list would also delete their credentials. Since in an important sense the membership database *is* the list, in that case, you don't want to delete the list, you want to disable delivery and access to the administrative interfaces. There are several ways to do those things, and some vary according to the MTA. They have subtly different consequences for what happens if somebody tries to post to the list or subscribe to it. The one you're most likely to care about is "the post disappears into a black hole and the member is distressed," but some of them can create backscatter in the case of spammers. Footnotes: [1] In the usual configuration for Exim4, Exim checks for lists/$NAME/config.pck, and if it's there, routes mail for $NAME to Mailman. Nothing to do once you delete config.pck. Postfix OTOH usually needs you to run a script to update the aliases. -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] List Archives
I manage a bunch of Mailman lists. We are on 2.1.38 cPanel, and I do have access to the command line. I want to delete some lists, but would like to save the archives. Pipermail saves by month, as I have it configured. Is there a way to obtain an entire archive at once? Are there tools to convert the MBOX format to something non-technical people can deal with easily? Thanks! Dave -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] List archives via email
I've searched FAQs, how-to's, etc but couldn't find an anything referencing this - is it possible to request a list's archives to be sent via email? For example, new employee needs copies of all emails that have been sent to a specific list. I thought I had done it before but can't find any info on it. Thanks. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] List archives via email
Tammy George wrote: I've searched FAQs, how-to's, etc but couldn't find an anything referencing this - is it possible to request a list's archives to be sent via email? For example, new employee needs copies of all emails that have been sent to a specific list. I thought I had done it before but can't find any info on it. The list's *nix mbox format archive can be downloaded. Depending on the site's setting of PUBLIC_MBOX, there may be a link to this on the list's archive table of contents page. Even if there is no link, it can be retrieved by going to the private archive URL of the form http://www.example.com/mailman/private/LISTNAME and authenticating and then going to a URL of the form http://www.example.com/mailman/private/LISTNAME.mbox/LISTNAME.mbox This mbox file can be imported or directly opened as a folder in many mail clients. This might satisfy your need, but Mailman has no facility to request archived messages or archives be sent via email. -- 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 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] list archives
Mark Sapiro wrote at 10:14 AM 7/17/2008: More importantly, how does one search the mailman archives looking for all posts that contain particular text? See http://wiki.list.org/x/OIA9. I was pleased to see that the DreamHost implementation of the Mailman archives includes htdig, which seems to be a nice little search facility. - - - - - - - - - - - - Michael Welch, volunteer Redwood Alliance PO Box 293 Arcata, CA 95518 707-822-7884 [EMAIL PROTECTED] www.redwoodalliance.org -- 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] list archives
Hi Friends. I have noticed that this list's archives include 3 months which have not happened yet. How has this occurred, and what will happen when we reach that date and new posts crash into the improperly dated archives? More importantly, how does one search the mailman archives looking for all posts that contain particular text? I understand that many folks use mailarchive.com, but that seems a bit out of our control. Will it be there forever? - - - - - - - - - - - - Michael Welch, volunteer Redwood Alliance PO Box 293 Arcata, CA 95518 707-822-7884 [EMAIL PROTECTED] www.redwoodalliance.org -- 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] list archives
Michael Welch wrote: Hi Friends. I have noticed that this list's archives include 3 months which have not happened yet. How has this occurred, and what will happen when we reach that date and new posts crash into the improperly dated archives? More importantly, how does one search the mailman archives looking for all posts that contain particular text? I understand that many folks use mailarchive.com, but that seems a bit out of our control. Will it be there forever? End original message. - That happens because the date is extracted from the Date: header of the message. The header is set by the MUA sending the message, if somebody has their computer clock set incorrectly, this will happen. There really isn't a lot you can do about it except maybe point out to the people with incorrect clocks to reset them. Changing this header at any point after it is generated is not recommended. The archive will work fine as is, it will simply show the incorrectly dated messages in the wrong directory (they are filed by month and year by default). The links for threads will work fine if proper headers existed in the original e-mail to determine threading order. Threading in the archive is controlled by References: and In-Reply-To: headers, not by the Date: header or even the subject line. Dragon ~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~ -- 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] list archives
Michael Welch wrote: Hi Friends. I have noticed that this list's archives include 3 months which have not happened yet. How has this occurred, and what will happen when we reach that date and new posts crash into the improperly dated archives? As Dragon notes, this is because the original posts had bad Date: headers. In more recent Mailman versions, this is prevented by (from Defaults.py) ARCHIVER_CLOBBER_DATE_POLICY = 2 ARCHIVER_ALLOWABLE_SANE_DATE_SKEW = days(15) Nothing bad will happen when we reach those dates. In fact, it's happened before. IIRC, there were '2008' posts from years back that we have already caught up to. More importantly, how does one search the mailman archives looking for all posts that contain particular text? See http://wiki.list.org/x/OIA9. -- 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://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] list archives
On 7/17/2008, Dragon ([EMAIL PROTECTED]) wrote: That happens because the date is extracted from the Date: header of the message. The header is set by the MUA sending the message, if somebody has their computer clock set incorrectly, this will happen. Wow... haven't run into that one yet... Is there a simple way to tell mailman to use the servers RECEIVED date/time instead? -- 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] list archives
Simon wrote: Is there a simple way to tell mailman to use the servers RECEIVED date/time instead? See the documentation in Defaults.py for the settings ARCHIVER_CLOBBER_DATE_POLICY = 2 ARCHIVER_ALLOWABLE_SANE_DATE_SKEW = days(15) -- 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://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] list archives
On 7/17/2008, Mark Sapiro ([EMAIL PROTECTED]) wrote: See the documentation in Defaults.py for the settings ARCHIVER_CLOBBER_DATE_POLICY = 2 Ah, perfect, thanks... so setting it to 1 will always use the received date. I'm wondering what the disadvantages to this are - assuming the server date/time is always correct? -- 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] list archives
Simon writes: On 7/17/2008, Mark Sapiro ([EMAIL PROTECTED]) wrote: See the documentation in Defaults.py for the settings ARCHIVER_CLOBBER_DATE_POLICY = 2 Ah, perfect, thanks... so setting it to 1 will always use the received date. I'm wondering what the disadvantages to this are - assuming the server date/time is always correct? The main disadvantage AFAICS is that the Date header is an author header according to the standards; mail handlers should pass it through unchanged. Practically, mail is somewhat unreliable (more so, these days). In a large archive, you will surely see many messages where some hop introduced a delay of many hours. It is sometimes useful in forensics (eg, identifying spam -- IIRC some of the pump and dump spams were deliberated postdated so that more victims would think they were looking at very fresh information). Finally, any time you add something that changes the message you add potential for bugs. Also, by changing the message you may make it less reliable as evidence should that be necessary. -- 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] list archives
On 7/17/2008 4:03 PM, Stephen J. Turnbull wrote: ARCHIVER_CLOBBER_DATE_POLICY = 2 Ah, perfect, thanks... so setting it to 1 will always use the received date. I'm wondering what the disadvantages to this are - assuming the server date/time is always correct? The main disadvantage AFAICS is that the Date header is an author header according to the standards; mail handlers should pass it through unchanged. Practically, mail is somewhat unreliable (more so, these days). In a large archive, you will surely see many messages where some hop introduced a delay of many hours. It is sometimes useful in forensics (eg, identifying spam -- IIRC some of the pump and dump spams were deliberated postdated so that more victims would think they were looking at very fresh information). Finally, any time you add something that changes the message you add potential for bugs. Also, by changing the message you may make it less reliable as evidence should that be necessary. Good points... and explains the more sensible default setting of 2... Thanks... -- 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] list archives
For one thing, that correction is applied at the time of archiving, not reception. So, if you regenerate your archives in the future, then all thase date/time stamps will change. -- Brad Knowles Sent from my iPhone On Jul 17, 2008, at 1:56 PM, Simon [EMAIL PROTECTED] wrote: On 7/17/2008, Mark Sapiro ([EMAIL PROTECTED]) wrote: See the documentation in Defaults.py for the settings ARCHIVER_CLOBBER_DATE_POLICY = 2 Ah, perfect, thanks... so setting it to 1 will always use the received date. I'm wondering what the disadvantages to this are - assuming the server date/time is always correct? -- 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/brad%40shub-internet.org Security Policy: http://wiki.list.org/x/QIA9 -- 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] list archives settings
Hi all, So I've been having some issues with a recently migrated list, where when I would try to view the list archives (http://www.sitename.com/pipermail/listname/), it wasn't reflecting any messages since the move (from one server to another). I was checking the Archiving Options settings, and I apparently had the new archive volume should be started to daily. Which is why I see the following in the /archives/private/ directory: 2004-March 2004-March.txt 2004-March.txt.gz 20040321 20040321.txt 20040321.txt.gz 20040322 20040322.txt 20040322.txt.gz Now that I've changed the setting to monthly, I'm wondering how I can get the daily volumes to be changed to monthly and actually show up in the archives list. Is this possible? Thanks in advance! michael -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
[Mailman-Users] List archives available for anyone
Hi, I've got my preferences set for view archives by list members only. But, with no cookies in my browser, I'm able to just go right to /pipermail/listname and it's freely visible. What is wrong with my configuration? Thanks! -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] List archives available for anyone
You do not say which version of MM you are running; assuming 2.0.13 or 2.1.x ... On Saturday, October 18, 2003, at 05:12 pm, Eric wrote: Hi, I've got my preferences set for view archives by list members only. By this, do you mean you have set the list archive to 'private' using the web admin GUI for the list? if so there should NOT be symlinks in directory $prefix/archive/public/ called listname and listname.mbox pointing to real directories in directory $prefix/archive/private/ If there are, and you are sure you have set the archive to 'private' through the admin GUI, then delete those symlinks. You should be able to set the list archive to 'public' and see the symlinks created and then deleted when you set the archive back to 'private'. If that is not happening then something is going wrong. Check you error logs and repost to this list if you cannot spot any reason for the problem. But, with no cookies in my browser, I'm able to just go right to /pipermail/listname and it's freely visible. What is wrong with my configuration? What Alias and ScriptAlias did you set up in your Apache httpd.conf to support Mailman? The /pipermail/ Alias should be pointing to the $prefix/archive/public/ directory. Your httpd.conf should not provide access to $prefix/archive/private/ directory. If the above is all correct it is difficult how Apache is serving the pages via the /pipermail/ URI path. Is it possible that what you are seeing is just some artifact of the accesses being via some caching proxy server or indeeed via your browser's cache; could the pages be out of the browser cache or the proxy cache rather than being from the MM Apache server? --- Richard Barrett http://www.openinfo.co.uk -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] List archives available for anyone
Richard, I checked through your email, and everything else was as you say it should be. But I mistakenly was thinking that I make the list private on the web by going to the Privacy options webpage instead of the Archiving Options page. The symlinks were indeed removed once I set it to private. Thanks! Eric On Saturday 18 October 2003 12:49 pm, you wrote: You do not say which version of MM you are running; assuming 2.0.13 or 2.1.x ... On Saturday, October 18, 2003, at 05:12 pm, Eric wrote: Hi, I've got my preferences set for view archives by list members only. By this, do you mean you have set the list archive to 'private' using the web admin GUI for the list? if so there should NOT be symlinks in directory $prefix/archive/public/ called listname and listname.mbox pointing to real directories in directory $prefix/archive/private/ If there are, and you are sure you have set the archive to 'private' through the admin GUI, then delete those symlinks. You should be able to set the list archive to 'public' and see the symlinks created and then deleted when you set the archive back to 'private'. If that is not happening then something is going wrong. Check you error logs and repost to this list if you cannot spot any reason for the problem. But, with no cookies in my browser, I'm able to just go right to /pipermail/listname and it's freely visible. What is wrong with my configuration? What Alias and ScriptAlias did you set up in your Apache httpd.conf to support Mailman? The /pipermail/ Alias should be pointing to the $prefix/archive/public/ directory. Your httpd.conf should not provide access to $prefix/archive/private/ directory. If the above is all correct it is difficult how Apache is serving the pages via the /pipermail/ URI path. Is it possible that what you are seeing is just some artifact of the accesses being via some caching proxy server or indeeed via your browser's cache; could the pages be out of the browser cache or the proxy cache rather than being from the MM Apache server? --- Richard Barrett http://www.openinfo.co.uk -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
