[Mailman-Users] Disable monthly membership reminder
Hi, Anyone know how I can disable the monthly membership reminder email that gets sent out to all members of a mailing list? Thanks, Bill -- 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] Disable monthly membership reminder
Bill Honneus wrote: Anyone know how I can disable the monthly membership reminder email that gets sent out to all members of a mailing list? For an individual list or lists, set send_reminders to No under Notifications on the list's General Options page To make this setting the default for new lists (no effect on existing lists) set DEFAULT_SEND_REMINDERS = No in mm_cfg.py. To totally disable the sending of reminders for the site, comment out or remove the cron/mailpasswds entry from Mailman's crontab. -- 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] Problem with 2.1.9 acceptable_aliases
Barry Finkel wrote: Barry Finkel wrote: There was a posting to a number of lists here yesterday To: [EMAIL PROTECTED] all of the lists are linked; some of the lists are subscribed to others. I took that address and added it to acceptable_aliases And Mark Sapiro replied: What did you add to acceptable_aliases? And for which list(s)? A post addressed to [EMAIL PROTECTED] will presumably be delivered to the comp_info list. In order for it not to be held by that list, you need either [EMAIL PROTECTED] As you discovered, the above is wrong. All entries in acceptable_aliases are interpreted as regexps, thus any regexp special characters must be escaped as you indicate below. I have not looked at the code, and I am not an expert in regular expressions. I surmise that Mailman is treating the address as a regular expression, which matches ab at anl.gov aab at anl.gov aaab at anl.gov b at anl.gov ... but does not match a+b at anl.gov I then changed the acceptable_aliases to a\+b at anl.gov and test mail was distributed. -- 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] New install problem
I've got a fresh new install on an Ubuntu Server 8, Mailman version 2.1.9 (installed from apt). Agent is Postfix I have the list installed and appears to be running. Mail sent to the list shows up in the archive. However the members are not receiving any mail from the lists. Checked the spam filter/bucket. I can send mail from the host... Any suggestions on where to start looking? I am up for doing the work in tracking this down but not sure where to start. -- 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] Disable monthly membership reminder
On 6/2/08 4:34 AM, Bill Honneus (honneus) wrote: Hi, Anyone know how I can disable the monthly membership reminder email that gets sent out to all members of a mailing list? It's send_reminders on the general options page, under notifications. dn Thanks, Bill -- 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/dnewman%40networktest.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- 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] Disable monthly membership reminder
On 2-Jun-08, at 7:34 AM, Bill Honneus (honneus) wrote: Anyone know how I can disable the monthly membership reminder email that gets sent out to all members of a mailing list? There's an option for this entitled Send monthly password reminders? (it's under Notifications on the general options page) Terri -- 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] Lists break when host_name is removed
Hi, every once in a while one of our list owners shoots themselves in the foot by deleting the value in host_name. That breaks the list almost completely. Is there a way for us to override that setting, so that list admins can't change it or the changed value isn't used? Thanks, Sebastian -- .:.Sebastian Hagedorn - RZKR-R1 (Gebäude 52), Zimmer 18.:. Zentrum für angewandte Informatik - Universitätsweiter Service RRZK .:.Universität zu Köln / Cologne University - ✆ +49-221-478-5587.:. .:.:.:.Skype: shagedorn.:.:.:. pgpqoh6tj2zm1.pgp Description: PGP signature -- 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] Disable monthly membership reminder
Bill Honneus (honneus) wrote: Anyone know how I can disable the monthly membership reminder email that gets sent out to all members of a mailing list? On the General Options page, under Notifications (about half way down), the first setting is Send monthly password reminders? I assume that's what you mean. -- Henry -- 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] Links in email messages are wrong. Please help
I've been scratching my head on this one for a while now. I'm running mailman 1:2.1.9-7 on Debian stable, all of the links in emails to users or admin are missing a slash: . You can configure your mailing list at the following web page: http://domain.com/cgi-bin/mailmanadmin/test3 The web page for users of your mailing list is: http://domain.com/cgi-bin/mailmanlistinfo/test3 . therefore point to a 404 page :-( Where do I look for those links? -- Rick Parola RPWebworks 386-931-5013 http://www.rpwebworks.com/ -- 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] Lists break when host_name is removed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sebastian Hagedorn wrote:
|
| every once in a while one of our list owners shoots themselves in the
| foot by deleting the value in host_name. That breaks the list almost
| completely. Is there a way for us to override that setting, so that list
| admins can't change it or the changed value isn't used?
Probably the easiest way is to find the following lines in
Mailman/Gui/General.py and remove or comment them out.
~('host_name', mm_cfg.Host, WIDTH, 0,
~ _('Host name this list prefers for email.'),
~ _(The host_name is the preferred name for email to
~ mailman-related addresses on this host, and generally
should be
~ the mail host's exchanger address, if any. This setting
can be
~ useful for selecting among alternative names of a host
that has
~ multiple addresses.)),
This will remove the setting from the General Options page.
- --
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
iD8DBQFIRJzBVVuXXpU7hpMRAgcBAKCSDdzpvDMvMvQbv++qScnTbicOMACfXgrN
+1wIqEq2JQM8AJxINDAcb6Q=
=ghOL
-END PGP SIGNATURE-
--
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] Links in email messages are wrong. Please help
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rick Parola wrote: | I've been scratching my head on this one for a while now. I'm running mailman | 1:2.1.9-7 on Debian stable, all of the links in emails to users or admin are | missing a slash: | | . | You can configure your mailing list at the following web page: | | http://domain.com/cgi-bin/mailmanadmin/test3 | | The web page for users of your mailing list is: | | http://domain.com/cgi-bin/mailmanlistinfo/test3 | . | | therefore point to a 404 page :-( | | Where do I look for those links? The problem is when you (or Debian) put DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman' in mm_cfg.py (or in Defaults.py ?), the trailing slash was omitted. You need to put DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/' in mm_cfg.py, but this will only fix the problem for new lists. To fix existing lists, you will need to run fix_url. See http://wiki.list.org/pages/viewpage.action?pageId=4030609. - -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) iD4DBQFIRKFiVVuXXpU7hpMRAgyFAJdVpXu5/1FsRQpkyHN19uRPKVyPAKDjh2d2 BcLshgpRitIOE0ySfHjDdw== =sJnJ -END PGP SIGNATURE- -- 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] New install problem
John Lieber wrote: I've got a fresh new install on an Ubuntu Server 8, Mailman version 2.1.9 (installed from apt). Agent is Postfix I have the list installed and appears to be running. Mail sent to the list shows up in the archive. However the members are not receiving any mail from the lists. Checked the spam filter/bucket. I can send mail from the host... See http://wiki.list.org/display/DOC/Troubleshooting-++No+mail+going+out+to+lists+members. Since posts are being received and archived, the problem is in outgoing message processing. Focus on OutgoingRunner, Mailman's error, smtp and smtp-failure logs, and Mailman's out queue. Also make sure that the list members have delivery enabled and are not set to 'digest' mode. -- 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] Major problems with privacy and mailman lists and harvesters
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dragon wrote: | | If I am not mistaken, I believe that there is currently a wrapper | script that handles access control to private archives but which gets | bypassed if the archive is public. The current architecture under | pipermail is that the actual archive pages themselves are just static | HTML files and the wrapper script only has the function of setting | and checking an access token in a cookie to access them if the | archive is private. See http://sourceforge.net/tracker/?func=detailaid=850805group_id=103atid=300103 for one approach to this. - -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) iD8DBQFIRMKYVVuXXpU7hpMRAmdYAJ9wuGzMs92VhtcNJzvFFToTEwBRpQCfRMMn k+tsT22ALFo4hEXj8EiFTIc= =GN+0 -END PGP SIGNATURE- -- 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] Major problems with privacy and mailman lists and harvesters
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 | I think the Topica listserver had a great way to deal with email | addresses in archives. You could see a semblance of the email address, | but no way could you deduce the real address. If you are logged into | the site, each is still obscured, but is a live link that opens up an | email-like dialog box -- with the real address still obscured. But it | does send an email to the real address for the obscured address. Try clicking the 'forward' button when viewing a message in a Topica archive. It reveals all. - -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) iD8DBQFIRMFMVVuXXpU7hpMRAilAAKChfp+hxBXpoSuApRU22FwT/idC2QCeOJKV +avYjs2YE1w2fSIydCbJLMo= =EPME -END PGP SIGNATURE- -- 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] custom mime precedence?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Terri Oda wrote | | On 24-May-08, at 8:23 AM, andReadG wrote: | | Hi all! | | This is the situation: attachments are stripped | (which is as I intended), but many messages | come in as multipart, with 1st part as text/plain | and second one as text/html. The senders, intended | to send the 2nd one (formatted to draw attention | in specific parts), but, being treated as | attachment, stays at the server. | | Is there a way around? I mean extract and keep | all non-text attachments for http download, | but exclude text/html and let it through along | with the plain text, or be preferred over it? | | | What does your pass_mime_types look like for this list? If you tell | it to let text/html through, as well as text/plain, people will get | the double messages the way they were sent, but most mail clients | handle that gracefully the way the sender intended. | | You want something that looks like this: | multipart/mixed | multipart/alternative | text/plain | text/html | multipart/signed You also have to set Content filtering-collapse_alternatives to No - -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) iD8DBQFIRL19VVuXXpU7hpMRAq3NAKCkxDbZcCEW088LlHaMOEOijUk3YgCgsj1Q wQy2hGDH77I0Tp1jb7bAHTk= =LU56 -END PGP SIGNATURE- -- 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] high memory usage and long running time for mailman Python process
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Terrence Brannon wrote: | | Hello, I am running Debian/etch and the user list has a Python process | which takes up 83.2% of my memory and has been running for more than 40 | minutes. | | My suspicion is that some sort of queue of moderator messages is very | large. | | In fact, /var/lib/mailman/ is very large... I cannot access the | administrator interface via the web: | | 6733./qfiles | 21551 ./messages | 60071 ./lists/asciidoc-discuss | 60093 ./lists | 288500 ./data | 380881 . | | | In looking through archives, I discovered I have more than 60,000 held | messages for one mailing list: | | schemelab at li2-168:/var/lib/mailman/data$ ls -l | wc -l | 64688 | | but for some reason attempting to discard even one is not working... it | just sits there and hangs: | | schemelab at li2-168:/var/lib/mailman/data$ sudo ../bin/discard | heldmsg-asciidoc-discuss-59527.pck | Password: | | (no return to shell after 5 minutes) | and | I posted this | http://www.mail-archive.com/mailman-users%40python.org/msg49373.html | and basically the whole list is having other discussions like I never | even posted... The second item has been addressed. I just want to add that sometimes we even go on vacation and don't take our computers. As far as your first issue is concerned, bin/discard is the best tool to delete these held messages. If you can't wait for it to complete, or for some reason it won't complete, you can remove lists/asciidoc-discuss/request.pck which is the 'moderator queue'. This will allow you to access your list. As Brad suggested (http://mail.python.org/pipermail/mailman-users/2008-May/061765.html), it would be good to stop Mailman, remove the request.pck, remove all the data/heldmsg-asciidoc-discuss-*.pck files, move aside and remake the mailman/data directory to compact it, and start Mailman. Then, consider setting the lists General Options-max_days_to_hold to some small, non-zero value so this doesn't happen again - -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) iD8DBQFIRLyAVVuXXpU7hpMRAjatAKCwzrUW+FABCW97aImX5k1YnmU6qwCdERg9 sHysnF/4e2CzxKJjYoHCjbw= =pNeK -END PGP SIGNATURE- -- 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] sharing administrator passwords
On May 26, 2008, at 1:59 AM, Laura Creighton wrote: So what people _want_ is a way to log in with a password and then have mailman recognise them and make it possible for them to administer all the lists they run. I agree. And I look forward to something like this in Mailman 3, but for the time being I am going to preach: Rant Every system administrator or knowledgeable person should be trying to persuade people to use good password management systems so that they don't have to remember most passwords. For Windows, I recommend Password Safe and for OS X, I recommend 1Password. Users of other systems are probably already using password management systems. pwsafe will maintain compatible databases with Password Safe. So, I would take the current poor situation with mailman's failure to distinguish between authorization and authentication as an opportunity to educate people about password management systems. /Rant Cheers, -j -- 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] archive/attachment preening
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Savoy, Jim wrote: | | Please confirm the assumptions I am about to make before I write the | preening | scripts for cron. I also want to write a bunch of scripts that look for | certain information. | | 1) If a list is digestable and archiving was never turned on, then the |archives/private/listname/index.html will contain only the | originally-created file |(which basically says No messages have been posted to this list yet, | so the |archives are currently empty). It may also contain an archives/private/listname/attachments directory with attachments that were scrubbed from 'plain' digests or scrubbed from messages if scrub_nondigest (not in 2.1.5) is Yes. | 2) If there is no mbox file in the /archives/private/listname.mbox | directory, then the list | has never had archiving turned on. Or never had a post. | 3) If a list is digestable but there is no attachments directory in | /archives/private/listname, | then the list has never had a message posted to it. It may have had posts, just no posts with scrubbed attachments. | 4) If the list is digestable, and archiving has never been turned on, | then files in the | archives/private/listname/attachments directory are only useful to | already-existing | subscribers who have digesting turned on (ie if I poll a list and it | has no members | subscribed as digest users, then it is safe to delete all files in | the attachments tree). It could have had a digest member who received and saved a digest with a link to a scrubbed attachment, and later switched to message mode. Also in later Mailman, it could be a list with scrub_nondigest = Yes that has scrubbed attachments from messages as opposed to digests. | If all of my above assumptions are correct, my psuedo-code would do | something like this: | | if (list is not archived and has no digest members) | keep stuff in attachments dir for 1 month; | | if (list is not archived but does have digest members) | keep stuff in attachments dir for 1 year; | | if (list is archived) | keep stuff in attachments dir for 3 years; | | For the archived lists (we have about 150 of them) I will contact the | owners first, to warn them | that I plan to pare their archive down to 3 years max. If they protest, | I will add them as an | exception to the rule and skip over them during the cron job run. I know | that there is more to | be done with regards to reducing the size of archives (ie running arch | --wipe on the editted, pared | down .mbox file, but I will do that manually). For now I am mostly | interesting in keeping the | stuff in the attachments directories to a minimum. I realize that | deleting stuff in /attachments | breaks links in the archive and digest messages, but I think that is | reasonable for the really | old messages (provided the list owner concurs). | | One final question. I know that you can change a list's settings with | /bin/config_list, but can you | poll a list for settings? For example, you can use /bin/list_members | -d to see which members | of a list read in digest mode, but how can I find out which lists have | archiving turned on? Or do I | have to examine the archives/private tree to garner that kind of info? | Thanks! bin/config_list -o - listname | grep '^archive =' - -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) iD8DBQFIRMtoVVuXXpU7hpMRAm1aAKC51yGIwts/ERvVX2bM2bv6FKs4ZQCg7GKN FFgmgpQQPLrkmLCUpbR3KE8= =6zUj -END PGP SIGNATURE- -- 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
