Re: [Mailman-Users] attachements question
John == John W Baxter [EMAIL PROTECTED] writes: John In addition, the Message-Id values would have to be John filtered, if used as is, for URL-unfriendly characters I don't think so. AFAIK, that was fixed about 2000 RFCs ago. When used as URLs, conforming agents will URL-encode them. How the archive chooses to implement identifying a storage location from the decoded URL is up to it. The URL-encoded string as filename is an obvious choice, but database-based archives might just use the raw Message-ID. BTW, I just realized that Google probably does index Message-IDs already (as long as the archived message includes that header), so Googleability is _not_ an advantage of my scheme over the header digest approach. The ability to algorithmically construct URNs and URLs however still is. John There's also the small point that the presence of John Message-Id: is a SHOULD, not a MUST (some compromise in the John musty past of the IETF, no doubt). I would guess that's for the convenience of folks who use telnet HOST 25 as their MTA. Humans are notoriously bad at generating unique anything.wink Anyway, my algorithm just treats such messages as a collision with all the others that don't have Message-IDs. -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of TsukubaTennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can do free software business; ask what your business can do for free software. -- 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] attachements question
At 2:29 PM +0900 2005-09-29, Stephen J. Turnbull wrote: BradBecause some MUAs generate message-ids that are likely Brad to collide. Can we stop pandering to the broken mailers, please? Are we not hackers? We know how to handle collisions. I don't really care how the algorithm is implemented. I care that it works. And I care that it is actually done, and checked into the source tree. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- 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] apache errors
I've jsut installed mailman, and think I've done everything right so far. When I try to browse to the mailman site though it doesn't seem to work properly. I've found other similar questions in the archive, but none of those had any resolution. When I browse to http://10.0.253.82/mailman/ I just get Forbidden You don't have permission to access /mailman/ on this server. Here's my httpd.conf ScriptAlias /mailman/ /usr/local/lib/mailman/cgi-bin/ Directory /usr/local/lib/mailman/cgi-bin AllowOverride None Options None Order allow,deny Allow from all /Directory Ideas? --Bryan -- 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] other thoughts about email commands
Christopher Adams wrote: However, I have another question about issuing email commands for subscribing. In the web interface, I can add information along with the email address, by using the syntax Joe Blow[EMAIL PROTECTED]. If I issue this by email, Mailman chokes on it. Here is an example. subscribe password address=Joe Blow[EMAIL PROTECTED]. Mailman seems confused by brackets and quotes. Any ideas how to do this via email? The e-mail subscribe command does not support real names in this way. The way to do an e-mail subscribe with real name is to omit the address= argument and place Joe Blow[EMAIL PROTECTED] in the From: header of the e-mail. -- 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] apache errors
I had this problem myself - very recently. This was on a Solaris implementation of Mailman. I'm on OpenBSD The values in question are: DEFAULT_EMAIL_HOST = 'hostname' DEFAULT_URL_HOST = 'hostname' I had appended these values to the file: /usr/local/mailman/Mailman/mm_cfg.py That didn't work, so I replaced the hostname with the fully qualified network name: 'hostname.domain.edu' That didn't work either. So, then, I put these values into the file: /usr/local/mailman/Mailman/Defaults.py And then everything worked correctly! This didn't do it either... :-/ --Bryan -- 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] printing a manual
Douglas B. Jones wrote: I am trying to print: http://www.gnu.org/software/mailman/mailman-install.pdf Regardless on which computer (W2K or XP), I get: 'The document could not be printed' Works for me using the 'print' button in Adobe Reader 7.0.3. -- 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] apache errors
On Thu, 2005-09-29 at 13:55 -0400, Joe Damico wrote: Bryan: I had this problem myself - very recently. This was on a Solaris implementation of Mailman. The values in question are: DEFAULT_EMAIL_HOST = 'hostname' DEFAULT_URL_HOST = 'hostname' I had appended these values to the file: /usr/local/mailman/Mailman/mm_cfg.py That didn't work, so I replaced the hostname with the fully qualified network name: 'hostname.domain.edu' That didn't work either. So, then, I put these values into the file: /usr/local/mailman/Mailman/Defaults.py And then everything worked correctly! Something is not right then. One should never edit Defaults.py. mm_cfg.py includes the contents of Defaults.py via this line: from Defaults import * Then in mm_cfg.py one overrides any settings previously imported from Defaults. In addition, the HTTP Error 403 - Forbidden, is not generated by invalid host names or URL's. This error says the URL was located but the client does not have permission to access it, this is a http server configuration issue, not a mailman configuration issue. I suspect the problem is the http configuration for the directory that was originally posted omitted the Options ExecCGI which is required to tell the http server it is permissible to execute cgi scripts in this directory. Here is what I use, adjust the path to your installation: ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/ Directory /usr/lib/mailman/cgi-bin/ AllowOverride None Options ExecCGI Order allow,deny Allow from all /Directory -- John Dennis [EMAIL PROTECTED] -- 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] apache errors
On Thu, 2005-09-29 at 14:23 -0400, John Dennis wrote: I suspect the problem is the http configuration for the directory that was originally posted omitted the Options ExecCGI which is required to tell the http server it is permissible to execute cgi scripts in this directory. Oh, almost forgot, but any changes to httpd configuration require the httpd server to be restarted in order for it to see the change. -- John Dennis [EMAIL PROTECTED] -- 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] apache errors
Here is what I use, adjust the path to your installation: ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/ Directory /usr/lib/mailman/cgi-bin/ AllowOverride None Options ExecCGI Order allow,deny Allow from all /Directory Here's how it reads now after editing that file (and restarting apache). ScriptAlias /mailman/ /usr/local/lib/mailman/cgi-bin/ Directory /usr/local/lib/mailman/cgi-bin AllowOverride None Options ExecCGI Order allow,deny Allow from all /Directory -- 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] Unable to create new mail list
Elvis Fernandes wrote: I am setting up a brand new mailman server. After doing per the documentation, I tried creating a testing test mail list. However, I get an error that says illegal list name: [EMAIL PROTECTED] Any idea's on what I am missing? It looks like you have an invalid or missing DEFAULT_EMAIL_HOST 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] Fwd: Small reply address problem
paul collen wrote: Yep, works fine in any client apart from Outlook!! ;o) Does anybody know how to manually edit the Sender address mailman uses? If you do this (by modifying code), you'll break automated bounce processing. -- 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] ?? restore only 1 list in backup .tar
Alysson Dias wrote: How I restore backup (file mailman.tar of complete /home/mailman) of only 1 list in the server? restore the /home/mailman/lists/listname directory and maybe the /home/mailman/archives/private/listname and /home/mailman/archives/private/listname.mbox directories. -- 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] apache errors
Hi, You have to accesss http://10.0.253.82/mailman/listinfo. Without the script name in the end of URI, Apache returns error because you set Options None. Options ExecCGI should not be used here for ScriptAliases is already specified. Options Indexes is the configuration for directory view but it is not recommended for security reason. http://httpd.apache.org/docs/2.0/mod/core.html#options Bryan Irvine wrote: I've jsut installed mailman, and think I've done everything right so far. When I try to browse to the mailman site though it doesn't seem to work properly. I've found other similar questions in the archive, but none of those had any resolution. When I browse to http://10.0.253.82/mailman/ I just get Forbidden You don't have permission to access /mailman/ on this server. Here's my httpd.conf ScriptAlias /mailman/ /usr/local/lib/mailman/cgi-bin/ Directory /usr/local/lib/mailman/cgi-bin AllowOverride None Options None Order allow,deny Allow from all /Directory Ideas? --Bryan -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] bounce_info_stale_after
Bill Moseley wrote: Two questions about bounce processing in 2.1.5. First question: The bounce_info_stale_after is regardless of list traffic? I.e. is the bounce information discarded after bounce_info_stale_after days regardless if there's been any outgoing mail? Yes, but only the most recent prior bounce is considered. I.e., if a user has some prior bounces and the most recent is less than bounce_info_stale_after days old, all are kept. For example, if you have a list where a message goes out just once every week, but you have bounce_info_stale_after less than a week then will a bouncing address *ever* get disabled? Not in this case. You need to insure that bounce_info_stale_after is more than a week in this case. Second questions: After bounce_you_are_disabled_warnings_interval is finished is the address really removed as the docs say, or just set to nomail? I assume it really means removed. It's really removed. When the score reaches bounce_score_threshold, delivery is disabled for 'bounce'. If delivery is not subsequently enabled by the user or admin, the user will be removed from the list after bounce_you_are_disabled_warnings times bounce_you_are_disabled_warnings_interval days as long as the disabled cron is being run. This does not depend on the warnings themselves bouncing. It only depends on delivery remaining disabled. -- 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] [resolved] Re: apache errors
I had done several test installs, with real, and fake users (installed via OpenBSD ports), and when I'd remove an install, I'd manually remove /usr/local/lib/mailman, but never noticed /var/spool/mailman, which although reported it was owned by _mailman, it actually wasn't because the uid number (1001 or some such thing) was different than the current _mailman user (1006 or something). So in essence, *I* broke it. :-) It works now. ezmlm you are history! ;) --Bryan -- 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] Private archive for list
Darren G Pifer wrote: On Fri, 2005-09-16 at 12:33, Mark Sapiro wrote: Is there a global mailbox file at archives/private/telephone_logs.mbox/telephone_logs.mbox or just the archives/private/telephone_logs.mbox/ directory without the file? There is an archives/private/telephone_logs.mbox file but no archives/private/telephone_logs.mbox directory. I don't understand. How can the file exist if the directory that contains it doesn't exist? Or are you saying that archives/private/telephone_logs.mbox is a file, not a directory? If so, what's in it? What do you see from ls -la archives/private/telephone_logs.mbox If the archives/private/telephone_logs.mbox/telephone_logs.mbox file exists and contains the past posts to the list, then bin/arch --wipe list-name should build archives. If the .mbox file is there and the HTML archives are not being created, there is probably a permissions issue. Do I need to do something to rebuild telephone_logs.mbox? Is it looks for a telephone_logs.mbox/telephone_logs.mbox file? The index.html file is empty. Shouldn't contain something? bin/arch --wipe telephone_logs will look for archives/private/telephone_logs.mbox/telephone_logs.mbox by default and will fail if it's not found. There is an option to specify a different file. See bin/arch --help. If you don't have the global .mbox file containing all the past posts, then you probably don't have anything to rebuild it from (unless you have the posts collected somewhere outside of Mailman), and you have no past archives. There may be a permissions issue or something similar preventing archiving. Do you see anything relevant in Mailman's 'error' log? -- 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] umbrella lists and approved senders
Gary Casterline wrote: We've set up chain of hierarchical lists to accommodate annual groups. Each year we create a list for the new cohorts: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] and then add the new class-of list to the umbrella list: [EMAIL PROTECTED] Each list is set to allow postings from subscribers and a small set of approved non-subscribed addresses. I'd like to add these approved addresses to the umbrella list and have messages go through without owner/moderator approval to the sublists. As it is now, we have to add the approved addresses to each sublist. Any suggestions? I'm not sure exactly what you're trying to do, but the patch at http://sourceforge.net/tracker/index.php?func=detailaid=1220144group_id=103atid=300103 may help. This patch allows you to put '@listname' in list_2's accept_these_nonmembers field and then all the members of listname are allowed to post to list_2. If I understand you correctly, you could do the following: Create list_x. No one will post to this list. No general users need to be aware of it. You can set it up per http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.011.htp so it is fully moderated and no one can post. You then add all your non-member 'approved' addresses to this list. Then when you create a new [EMAIL PROTECTED] list, you put @list_x in the accept_these_nonmembers field. Thus, all the members of list_x will be allowed to post to any of the [EMAIL PROTECTED] lists, and the special approved posters can be dynamically maintained just by maintaining the membership of list_x. This does require installation of the patch, which may or may not be an issue. -- 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] mailman slow
Hello, Running version 2.1.4 it seems that mail is taking longer and longer. What used to take a few minutes is now taking an hour or two to get thru Mailman. Top indicates the machine is not busy and the mail is not in the queue. It seems to be waiting in the mailman process. Any ideas? I'm stumped at this point. As always any ideas are appreciated. Con Wieland Network and Computing Services University of California at Irvine -- 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] doesn't work...
can somebody explain this please?... thanks # ./remove_members -n -N aaac [EMAIL PROTECTED] # ./remove_members -a -n -N aaac Traceback (most recent call last): File ./remove_members, line 186, in ? main() File ./remove_members, line 176, in main admin_notif, userack) File /var/mailman/Mailman/MailList.py, line 990, in ApprovedDeleteMember self.removeMember(emailaddr) File /var/mailman/Mailman/OldStyleMemberships.py, line 220, in removeMember self.__assertIsMember(member) File /var/mailman/Mailman/OldStyleMemberships.py, line 113, in __assertIsMember raise Errors.NotAMemberError, member Mailman.Errors.NotAMemberError: [EMAIL PROTECTED] -- -- 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] looking for information regarding the privatearchive session cookies
michael dunston wrote: Can someone tell me where (in Mailman) the private archive session cookies are being set, or where I might find more information about the use of cookies for enforcing private archive access? I am trying to add this level of protection to a swish-e search CGI. Thanks in advance for any information or direction on where to look. Mailman/SecurityManager.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] doesn't work...
and this - executed in the directory of the aaac list: who cares if s/he is a member - just get it out... why would you need to assertIsMember?!? doesn't make sense [~/aaac]# grep -rl [EMAIL PROTECTED] * [~/aaac]# ../../bin/remove_members -a -n -N aaac Traceback (most recent call last): File ../../bin/remove_members, line 186, in ? main() File ../../bin/remove_members, line 176, in main admin_notif, userack) File /var/mailman/Mailman/MailList.py, line 990, in ApprovedDeleteMember self.removeMember(emailaddr) File /var/mailman/Mailman/OldStyleMemberships.py, line 220, in removeMember self.__assertIsMember(member) File /var/mailman/Mailman/OldStyleMemberships.py, line 113, in __assertIsMember raise Errors.NotAMemberError, member Mailman.Errors.NotAMemberError: [EMAIL PROTECTED] or explain this please... thank you: # ./add_members -a n -w n -r - aaac [EMAIL PROTECTED] Subscribed: [EMAIL PROTECTED] # ./remove_members -a -n -N aaac Traceback (most recent call last): File ./remove_members, line 186, in ? main() File ./remove_members, line 176, in main admin_notif, userack) File /var/mailman/Mailman/MailList.py, line 990, in ApprovedDeleteMember self.removeMember(emailaddr) File /var/mailman/Mailman/OldStyleMemberships.py, line 220, in removeMember self.__assertIsMember(member) File /var/mailman/Mailman/OldStyleMemberships.py, line 113, in __assertIsMember raise Errors.NotAMemberError, member Mailman.Errors.NotAMemberError: [EMAIL PROTECTED] can somebody explain this please?... thanks # ./remove_members -n -N aaac [EMAIL PROTECTED] # ./remove_members -a -n -N aaac Traceback (most recent call last): File ./remove_members, line 186, in ? main() File ./remove_members, line 176, in main admin_notif, userack) File /var/mailman/Mailman/MailList.py, line 990, in ApprovedDeleteMember self.removeMember(emailaddr) File /var/mailman/Mailman/OldStyleMemberships.py, line 220, in removeMember self.__assertIsMember(member) File /var/mailman/Mailman/OldStyleMemberships.py, line 113, in __assertIsMember raise Errors.NotAMemberError, member Mailman.Errors.NotAMemberError: [EMAIL PROTECTED] -- -- 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/kalin%40el.net 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] doesn't work...
kalin mintchev wrote:
and this - executed in the directory of the aaac list:
who cares if s/he is a member - just get it out... why would you need to
assertIsMember?!? doesn't make sense
Because the method which is used to remove the member is more general
than that.
[~/aaac]# grep -rl [EMAIL PROTECTED] *
[~/aaac]# ../../bin/remove_members -a -n -N aaac
Traceback (most recent call last):
File ../../bin/remove_members, line 186, in ?
main()
File ../../bin/remove_members, line 176, in main
admin_notif, userack)
File /var/mailman/Mailman/MailList.py, line 990, in ApprovedDeleteMember
self.removeMember(emailaddr)
File /var/mailman/Mailman/OldStyleMemberships.py, line 220, in
removeMember
self.__assertIsMember(member)
File /var/mailman/Mailman/OldStyleMemberships.py, line 113, in
__assertIsMember
raise Errors.NotAMemberError, member
Mailman.Errors.NotAMemberError: [EMAIL PROTECTED]
It appears something is messed up in the lists config.pck or perhaps
there is a transparent character or something similar in the actual
member address.
Try:
bin/withlist aaac
Loading list aaac (unlocked)
The variable `m' is the aaac MailList instance
m.getMembers()
and see what is returned (type control-D to the next prompt)
Or try bin/dumpdb lists/aaac/config.pck and look at the lists
'members':
and
'digest_members':
If possible, do this from a terminal/console that can display
'transparent' characters.
OTOH, since you've already blown off the membership, why not just use
bin/config_list -o to dump the configuration, and remove, recreate the
list, and use bin/config_list -i to reconfigure the list?
Or you can do
bin/withlist -l aaac
Loading list aaac (locked)
The variable `m' is the aaac MailList instance
m.members = {}
m.digest_members = {}
m.language = {}
m.passwords = {}
m.user_options = {}
m.usernames = {}
m.Save()
(enter control-D here)
--
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] doesn't work...
Because the method which is used to remove the member is more general than that. aha... ok. It appears something is messed up in the lists config.pck or perhaps there is a transparent character or something similar in the actual member address. right. but grep didn't find it either... so it's not there. Try: bin/withlist aaac Loading list aaac (unlocked) The variable `m' is the aaac MailList instance m.getMembers() i used that to delete the address a few times. btw - is there a list somewhere of all the commands that can be used while running withlist? and see what is returned (type control-D to the next prompt) Or try bin/dumpdb lists/aaac/config.pck and look at the lists 'members': did that earlier... john is not there and 'digest_members': there are no digests on this list... If possible, do this from a terminal/console that can display 'transparent' characters. right... that was done too... OTOH, since you've already blown off the membership, why not just use bin/config_list -o to dump the configuration, and remove, recreate the list, and use bin/config_list -i to reconfigure the list? because it's heavily customized and i'm just 'kinda helping' and there was stuff that needed to be sent 'right away'... like 'urgent'... thanks... -- 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] doesn't work...
- Original Message ---
Subject: Re: [Mailman-Users] doesn't work...
From: kalin mintchev [EMAIL PROTECTED]
Date: Thu, 29 Sep 2005 22:23:13 -0400 (EDT)
To: Mark Sapiro [EMAIL PROTECTED]
Cc: mailman-users@python.org
Because the method which is used to remove the member is more general
than that.
aha... ok.
It appears something is messed up in the lists config.pck or perhaps
there is a transparent character or something similar in the actual
member address.
right. but grep didn't find it either... so it's not there.
Try:
bin/withlist aaac
Loading list aaac (unlocked)
The variable `m' is the aaac MailList instance
m.getMembers()
i used that to delete the address a few times. btw - is there a list
somewhere of all the commands that can be used while running withlist?
No list. Some is knowing some python and knowing the names of list
attributes, e.g. from the admin interface. Some is looking at modules
like MailList.py, OldStyleMemberships.py, etc. and seeing what methods
are available or looking at scripts in bin/ and elsewhere and seeing
what they do.
Are you saying that the above returns an empty list?? How can that be?
bin/remove_members -a does this
if all:
addresses = mlist.getMembers()
try:
for addr in addresses:
if not mlist.isMember(addr):
if not alllists:
print _('No such member: %(addr)s')
continue
mlist.ApprovedDeleteMember(addr, 'bin/remove_members',
admin_notif, userack)
if alllists:
print _(User `%(addr)s' removed from list:
%(listname)s.)
mlist.Save()
finally:
mlist.Unlock()
It is failing on the
mlist.ApprovedDeleteMember(addr, 'bin/remove_members',
admin_notif, userack)
It doesn't get to that unless the address is in the mlist.getMembers()
list and also passes the mlist.isMember(addr) test which means it is
in either the mlist.members list or the mlist.digest_members list.
and see what is returned (type control-D to the next prompt)
Or try bin/dumpdb lists/aaac/config.pck and look at the lists
'members':
did that earlier... john is not there
and
'digest_members':
there are no digests on this list...
That doesn't mean there aren't digest_members.
If possible, do this from a terminal/console that can display
'transparent' characters.
right... that was done too...
OTOH, since you've already blown off the membership, why not just use
bin/config_list -o to dump the configuration, and remove, recreate the
list, and use bin/config_list -i to reconfigure the list?
because it's heavily customized
That's the point about dumping the configuration with bin/config_list
and then restoring it later. This preserves all the customization.
--
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] mailman slow
Con Wieland wrote: Running version 2.1.4 it seems that mail is taking longer and longer. What used to take a few minutes is now taking an hour or two to get thru Mailman. Top indicates the machine is not busy and the mail is not in the queue. It seems to be waiting in the mailman process. Any ideas? I'm stumped at this point. As always any ideas are appreciated. Similar problems have been reported in the past that were apparently caused by directories (usually in qfiles) at some point growing very large. This creates a situation where even though the directory currently has few if any entries, a very large (very sparse) disk directory must be searched to store new entries. Try 'ls -l qfiles' and see if any of the directories (most likely 'out', but maybe others) are quite large. If this is the case, you can stop mailman, move the large directory aside, create a new directory with the same ownership and permissions and move the contents back and start mailman. If you want to do this with qfiles/in, you should probably stop the incoming MTA while doing it. You also might look at the size of the locks/ directory. -- 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] mmdsr -- Mailman Daily Status Reports(Bourne shellscript, updated)
Brad Knowles wrote:
I've taken your submission and incorporated that, as well as
fixing another bug that was brought to my attention by Adrian Wells.
It turns out that there is a minor log file difference between
Mailman versions 2.1.5 and 2.1.6, which causes the smtp log to be
written in a slightly different format. The code should now handle
both styles without problems.
This all looks good. I made a couple of other changes that I meant to
report before now, but never got to it.
I got tired of seeing all the '.' and '..' entries and the 'total'
blocks in the qfiles subdirectory listings so I changed the script as
follows:
@@ -455,7 +457,7 @@
echo -- $TMP
if [ $LINES -le $MAX_LINES ] ; then
- $CAT $TMPLOG $TMP
+ $GREP -v ^[dt] $TMPLOG $TMP
else
$HEAD $TMPLOG $TMP
echo $TMP
to supress the 'total' line and sub-sub-directories although arguably
the total line is interesting to monitor if it grows large.
One could just make the grep
$GREP -v ^d $TMPLOG $TMP
or maybe just change the preceding
$LS -la $DIR $TMPLOG
to
$LS -l $DIR $TMPLOG
The other thing I changed is due to the fact that the logs are rotated
weekly via logrotate on my installation. This occurs at 04:02 on
Sundays and is beyond my control and caused my report for Sunday to be
missing the 00:00 to 04:02 time period. Even if I did control it, I
think the best I could do would lose a second or two.
Instead, I changed the script as follows to get all the days entries
from both the current and the previous log (if any).
@@ -254,7 +254,8 @@
$TOUCH $TMPLOG
echo Log file: $LOG $TMP
echo == $TMP
-$GREP -si ^$DAY [0-9][0-9:]* $YEAR $LOGDIR/$LOG $TMPLOG
+$GREP -si ^$DAY [0-9][0-9:]* $YEAR ${LOGDIR}/${LOG}.1
${LOGDIR}/${LOG} \
+| $SED s/^[^:]*:// $TMPLOG
if [ -f $LOGDIR/${LOG} ] ; then
@@ -324,7 +325,8 @@
$TOUCH $TMPLOG
echo Log file: $LOG $TMP
echo == $TMP
-$GREP -si ^$DAY [0-9][0-9:]* $YEAR $LOGDIR/$LOG $TMPLOG
+$GREP -si ^$DAY [0-9][0-9:]* $YEAR ${LOGDIR}/${LOG}.1
${LOGDIR}/${LOG} \
+| $SED s/^[^:]*:// $TMPLOG
if [ -f $LOGDIR/${LOG} ] ; then
Watch for wrapped lines above. Also, note the sed which removes the
leading 'filename:' placed on each line by grep.
--
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
