Re: [Mailman-Users] join vs subscribe
i just got the emails - all of them at once - hours after the requests were made... and i'm seeing something in the maillog i haven't seen before: timeout waiting for input from local during Draining Input i just confirmed one. by replying. still not a member... this has never happened before. i found this thread without a resolution of the problem: http://mail.python.org/pipermail/mailman-users/2005-July/045582.html anyone knows how that story ended? my mailman version is 2.1.5. it has been working fine so far except i have to restart mailman with cron because the bounce runner crashes for some reason... so then what does it mean when i sent 3 different email requests to subscribe to a list and nothing happens.. the ways are: sending a message to [EMAIL PROTECTED], [EMAIL PROTECTED] and [EMAIL PROTECTED] with the subject and body 'subscribe'. mail log says: l350hXwM001076: to=|/var/mailman/mail/mailman subscribe list, ctladdr=[EMAIL PROTECTED] (8/0), delay=00:00:01, xdelay= 00:00:01, mailer=prog, pri=30923, dsn=2.0.0, stat=Sent or in other words this is turned over to mailman. after A FEW HOURS this turns up in the mailman subscribe log: Apr 04 20:17:21 2007 (5670) list: pending [EMAIL PROTECTED] [EMAIL PROTECTED] Apr 04 20:17:21 2007 (5670) list: pending [EMAIL PROTECTED] [EMAIL PROTECTED] Apr 04 20:17:24 2007 (5670) list: pending [EMAIL PROTECTED] [EMAIL PROTECTED] Apr 04 20:17:25 2007 (5670) list: pending [EMAIL PROTECTED] [EMAIL PROTECTED] Apr 04 20:17:25 2007 (5670) list: pending [EMAIL PROTECTED] [EMAIL PROTECTED] Apr 04 20:17:25 2007 (5670) list: pending kalin mintchev [EMAIL PROTECTED] [EMAIL PROTECTED] still i have not gotten the email where i'm supposed to confirm my subscription. my name is not in the queue? what's up with the delay? thanks kalin mintchev wrote: what is the difference between listname-join and listname-subscribe?! They're spelled differently. Otherwise, none. listname-join is a synonym for listname-subscribe just as listname-leave is a synonym for listname-unsubscribe. -- 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/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/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] default settings for newly created lists
On Wed, 4 Apr 2007, Dragon wrote: Tomas Macek wrote: Hi, I'm running Mailman 2.1.5.1-34 on RHEL4 machine. I will have to create some lists and I don't want to go throught the bin/config_list -o list.cfg list - edit the cfg file - bin/config_list -i list.cfg list, but I want to edit the options, that are the source for the creating new lists when I type the ./newlist command. Where is the default setting for new lists stored? I really can't find it. For example I'd like to have 'msg_footer' option set the same for all my lists, 'generic_nonmember_action' and many others set to my own default, when I create a new list. Is it possible? Where can I do it? Many thanks, Tomas End original message. - All of the list and server defaults are in the Defaults.py file but DO NOT change that one. It gets overwritten when Mailman is upgraded. You can put the settings you want in the mm_cfg.py file, this file is used to override defaults and set other options like msg_footer etc. at list creation. The settings you want have to be in that file when you create the list or they won't be set. Dragon I knew about the changes in Defaults.py and mm_cfg.py but I didn't try to write lists config variables in it. Now I have this settings in my mm_cfg.py: ... generic_nonmember_action = 0 GENERIC_NONMEMBER_ACTION = 0 ... I did not know, if the variables in mm_cfg.py are case sensitive, so I wrote both. But still when I try to create a new list (./newlist x) and then dump the config, I still see generic_nonmember_action = 1. Why? What should I change? -- 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] join vs subscribe
kalin mintchev wrote: i just got the emails - all of them at once - hours after the requests were made... and i'm seeing something in the maillog i haven't seen before: timeout waiting for input from local during Draining Input i just confirmed one. by replying. still not a member... this has never happened before. i found this thread without a resolution of the problem: http://mail.python.org/pipermail/mailman-users/2005-July/045582.html anyone knows how that story ended? my mailman version is 2.1.5. it has been working fine so far except i have to restart mailman with cron because the bounce runner crashes for some reason... So you have qrunner problems possibly affecting more than bounce runner. so then what does it mean when i sent 3 different email requests to subscribe to a list and nothing happens.. the ways are: sending a message to [EMAIL PROTECTED], [EMAIL PROTECTED] and [EMAIL PROTECTED] with the subject and body 'subscribe'. mail log says: l350hXwM001076: to=|/var/mailman/mail/mailman subscribe list, ctladdr=[EMAIL PROTECTED] (8/0), delay=00:00:01, xdelay= 00:00:01, mailer=prog, pri=30923, dsn=2.0.0, stat=Sent or in other words this is turned over to mailman. after A FEW HOURS this turns up in the mailman subscribe log: Apr 04 20:17:21 2007 (5670) list: pending [EMAIL PROTECTED] [EMAIL PROTECTED] Apr 04 20:17:21 2007 (5670) list: pending [EMAIL PROTECTED] [EMAIL PROTECTED] Apr 04 20:17:24 2007 (5670) list: pending [EMAIL PROTECTED] [EMAIL PROTECTED] Apr 04 20:17:25 2007 (5670) list: pending [EMAIL PROTECTED] [EMAIL PROTECTED] Apr 04 20:17:25 2007 (5670) list: pending [EMAIL PROTECTED] [EMAIL PROTECTED] Apr 04 20:17:25 2007 (5670) list: pending kalin mintchev [EMAIL PROTECTED] [EMAIL PROTECTED] still i have not gotten the email where i'm supposed to confirm my subscription. my name is not in the queue? Look in all Mailman's logs for relevant entries. Look at Mailman's qfiles/*/ directories. In short, go through all of http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.014.htp. Report the full detail of anything unusual you find. -- 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] default settings for newly created lists
Tomas Macek I knew about the changes in Defaults.py and mm_cfg.py but I didn't try to write lists config variables in it. Now I have this settings in my mm_cfg.py: ... generic_nonmember_action = 0 GENERIC_NONMEMBER_ACTION = 0 ... I did not know, if the variables in mm_cfg.py are case sensitive, They are. so I wrote both. But still when I try to create a new list (./newlist x) and then dump the config, I still see generic_nonmember_action = 1. Why? What should I change? Did you see my reply to your post at http://mail.python.org/pipermail/mailman-users/2007-April/056442.html? You can't set anything in mm_cfg.py that isn't already set in Defaults.py. You can only override Defaults.py settings in mm_cfg.py. Read Defaults.py, or if you've read it, read it again. The settings you want are things like DEFAULT_GENERIC_NONMEMBER_ACTION, DEFAULT_MSG_FOOTER, etc. These are all described in Defaults.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] Infamous error ImportError: ld.so.1: python: fatal: libgcc_s.so.1 (solved)
Tokio Kikuchi wrote: Rolf E. Sonneveld wrote: Tokio Kikuchi wrote: However, when I try to access Mailman via my browser (using Apache on the server side) I get the infamous error message: The /usr/local/lib version seems to be more recent. Before installation, I made sure that LD_LIBRARY_PATH was set to So, the apache was not running under LD_LIBRARY_PATH envrironment. You should setenv LD_RUN_PATH while compiling or use crle. Read the crle man for detail. as a followup to my previous message: I just did a ldd for httpd and this is the result: bash-3.00# ldd /usr/local/apache/bin/httpd It's not httpd which caused that error. Maybe its python and/or a module which resides in python library path (.../lib/python2.x/) which is called from httpd running environment. You should set LD_RUN_PATH properly while compiling python, mailman, and httpd. LD_LIBRARY_PATH is only effective when the compiled executable is running. So, you might want to startup httpd like: # LD_LIBRARY_PATH=/whatever/lib /some/where/bin/apachectl start Great! I removed Python and Mailman, recompiled again using the proper LD_RUN_PATH (in addition to the LD_LIBRARY_PATH) and now it works like a charm. I didn't have to recompile Apache. Thanks a lot for your help! /rolf -- 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] Size Limits of Files?
On 4/5/07, Brad Knowles [EMAIL PROTECTED] wrote: At 3:24 PM -0400 4/4/07, Justin Denick wrote: I had a user complain that she could not send mail, reply, or check Sent Mail. She would click on Sent and after awhile it would just download a file called right_main.php. I'm pretty sure that Mailman doesn't use PHP -- It's Python, instead. So, whatever is going on here, I don't think it has anything to do with Mailman per se. Indeed, 'right_main.php' reminds me of squirrelmail, which, IIRC, is PHP. -- - Patrick Bogen -- 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] Language encoding and digests...
Random question, and unfortunately I'm having trouble finding answers since most of the things I have found aren't in my language... Has anyone here ever attempted to use EUC-JP encoding along with digests? I recently ran into an issue with a list whom was using Japanese as they're language, and the digest mbox file actually caused any other list on that server to not receive digests and I have absolutely no clue why or how. Just a thought, Krystal -- 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] Language encoding and digests...
Krystal F. Zipfel wrote: Random question, and unfortunately I'm having trouble finding answers since most of the things I have found aren't in my language... Has anyone here ever attempted to use EUC-JP encoding along with digests? I recently ran into an issue with a list whom was using Japanese as they're language, and the digest mbox file actually caused any other list on that server to not receive digests and I have absolutely no clue why or how. I don't fully understand your situation but there is a common problem in Japanese people who don't care (or ignorant) about 'machine dependent characters' like number in circle or double width roman numerals. If those characters are used in 'iso-2022-jp' declaration of charset, mailman and python codecs fail to process such characters and single processes like 'cron/senddigests' stops working. My advice is to remove (or rename for later inspection) the digest.mbox file from the Japanese list directory and set digestable=0 if they keep using the 'machine dependent characters'. Just a thought, Krystal -- -- Tokio Kikuchi, [EMAIL PROTECTED] 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
[Mailman-Users] Permanent subscription ban?
Is there a way to tell Mailman to never allow a specific email address to be subscribed? I.e. is there a master banned email address list within Mailman, and if so how to I add addresses to it? -- 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] Permanent subscription ban?
At 3:58 PM -0500 4/5/07, Jim Garrison wrote: Is there a way to tell Mailman to never allow a specific email address to be subscribed? I.e. is there a master banned email address list within Mailman, and if so how to I add addresses to it? Sure. From the web admin interface for your list, click on Privacy options..., and the first sub-page is Subscription rules. Scroll down to the ban_list field, which has the short description: List of addresses which are banned from membership in this mailing list. Then you can either enter specific addresses which are banned, or you can use Python regular expressions to ban an entire domain. In the latter case, to take a couple of examples that were recently banned on the mailman-users mailing list, we added: [EMAIL PROTECTED] [EMAIL PROTECTED] This is because they had subscribed to the mailman-users list from addresses that were themselves pointed at mis-configured mailing lists, causing every single post to the list to result in a bounce. When the people who administer these sites figure out that they've been unsubscribed and their entire domain has been banned, they can come back to us and ask why we took this action, and then we will explain the severity of the situation to them. Once they can convince us that this will never, ever happen again, we can re-enable subscription access for their domain. Note that there is no leading whitespace in these regular expressions -- the caret (^) symbol has to be the first character on the line. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- 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 scripts running with wrong group
No One wrote: Thanks but that link doesn't help. I installed using an rpm binary so there is/was no configure script. I referred you to FAQ article 6.16 to help you understand the source of the error and the reason for it. Not because I thought it would give you a cookbook solution. On the other hand this is beginning to look like a Mandriva problem. The 'mailman' script has a group of 'mail' and the set gid bit is on so it should be running as mail. As far as the packager is concerned that probably also Mandriva but I don't expect to get anything there very quickly. If you had read and comprehended the FAQ article, you would understand that the SETGID wrapper is group 'mail' and runs with effective group 'mail', but it has a check for the real invoking group for security reasons to prevent just anyone from successfully running it. I wrote: What you really need to do is contact your packager, however I think in most cases, Postfix excecutes the pipe to Mailman using the user and group of the file in which it found the alias that contains the pipe to Mailman. So, you could try adjusting that. I believe this is the solution in this case. If you properly set up Mailman-Postfix integration as described at http://www.list.org/mailman-install/node13.html, the Mailman aliases for Postfix will be automatically maintained in Mailman's data/aliases* files, and if these are user:group mail:mail, I think that will solve your problem. -- 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 scripts running with wrong group
On Apr 4, 2007, at 8:38 PM, Mark Sapiro wrote: I think in most cases, Postfix excecutes the pipe to Mailman using the user and group of the file in which it found the alias that contains the pipe to Mailman. I can confirm this. I had the problem that the original poster described after moving my mailman installation from one machine to another. Postfix does instead use the owner of the particular .db file to determine what user delivery (whether to files or pipes) should be run under. -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] Language encoding and digests...
Krystal writes: Has anyone here ever attempted to use EUC-JP encoding along with digests? I recently ran into an issue with a list whom was using Japanese as they're language, and the digest mbox file actually caused any other list on that server to not receive digests and I have absolutely no clue why or how. Please file a bug report. I am just as frustrated as Kikuchi-san is with the Japanese attitude toward standards, but this behavior of Mailman is a violation of the Postel Principle (be strict in what you emit, but lax in what you accept). Mailman functionality should not be disabled by the contents of posts it handles; if it doesn't like them, it should strip them or quarantine them without impeding the flow of other posts. In the short run, you probably should disable digestible for that list. Mailman's I18N is not very robust in this respect, and it may take some time to fix. Tokio, is it possible that you could just default the error policy for codecs as replace for charsets that are known to be prone to vendor extension? And add an option for the set of replace-able charsets to be set by the list admin? -- 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] Language encoding and digests...
At 12:10 PM +0900 4/6/07, Stephen J. Turnbull wrote: In the short run, you probably should disable digestible for that list. Mailman's I18N is not very robust in this respect, and it may take some time to fix. More importantly, I'm not sure where the bug is. If this is a problem in the handling of charsets in the mail package within Python or within Python itself, then that's a deeper problem than Mailman. In that case, we can try to find a way to work around it better than we've done in the past, but I'm not sure we can actually fix it. Tokio? -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- 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
