Re: [Mailman-Users] problems with gid when installing
I tried example.com/mailman/ just for a visit or a index page but now I receive a 403 forbidden... Let's try to debug one issue at a time, but what's in error_log for the 403? The error when visiting domain.com/mailman/ [Mon Jan 22 10:01:52 2007] [error] [client 62.58.15.252] attempt to invoke directory as script: /usr/local/mailman So now it looks like a permissions issue. What are the permissions on /usr/local/mailman (the contents looked OK in a prior post). Have you tried running bin/check_perms? Results of bin/check_perms [EMAIL PROTECTED]:/usr/local/mailman# bin/check_perms Warning: Private archive directory is other-executable (o+x). This could allow other users on your system to read private archives. If you're on a shared multiuser system, you should consult the installation manual on how to fix this. No problems found [18091 refs] [EMAIL PROTECTED]:/usr/local/mailman# [EMAIL PROTECTED]:/usr/local/mailman# ls -l total 72 drwxrwsr-x 11 root mailman 4096 Jan 20 16:23 Mailman drwxrwsr-x4 root mailman 4096 Jan 20 16:19 archives drwxrwsr-x2 root mailman 4096 Jan 20 16:19 bin drwxrwsrwx2 root mailman 4096 Jan 20 16:19 cgi-bin drwxrwsr-x2 root mailman 4096 Jan 20 16:19 cron drwxrwsr-x2 root mailman 4096 Jan 20 16:30 data drwxrwsr-x2 root mailman 4096 Jan 20 16:19 icons drwxrwsr-x3 root mailman 4096 Jan 20 16:28 lists drwxrwsr-x2 root mailman 4096 Jan 20 16:29 locks drwxrwsr-x2 root mailman 4096 Jan 20 16:29 logs drwxrwsr-x2 root mailman 4096 Jan 20 16:19 mail drwxrwsr-x 34 root mailman 4096 Jan 20 16:19 messages drwxrwsr-x6 root mailman 4096 Jan 20 16:19 pythonlib drwxrwsr-x 11 root mailman 4096 Jan 20 16:29 qfiles drwxrwsr-x2 root mailman 4096 Jan 20 16:19 scripts drwxrwsr-x2 root mailman 4096 Jan 20 16:19 spam drwxrwsr-x 35 root mailman 4096 Jan 20 16:19 templates drwxrwsr-x4 root mailman 4096 Jan 20 16:19 tests Thanks, Peter -- 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] problems with gid when installing
Don't know why but it works almost ;-) I see a webpage and can create a new mailinglist... Only one last problem I can't create a new mailinglist.. Receive this error: Error: You are not authorized to create new mailing lists I changed the administrators passwd and list creater passwd with bin/mmsitepass -c or without -c but no effect.. Any ideas? thanks -- 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] Adding disclaimer to message footer via command line
-Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Sunday, January 21, 2007 6:35 PM To: Leon Kolchinsky; mailman-users@python.org Subject: Re: [Mailman-Users] Adding disclaimer to message footer via command line Leon Kolchinsky wrote: Our management decided to add disclaimer to every footer in Digest and Non-digest options. I know that this is a bad netiquette but I have no choice. I have a lot of mailinglists running on my server and I though that may be there is a way to do this addition with some script via command line and add this to all lists, and save from myself doing it via web-interface enormous times. You can do this fairly easily in two ways. One is with a bin/withlist script and the other is by running bin/config_list via a shell script. Several examples of withlist scripts (not this exact one) can be found at http://veenet.value.net/~msapiro/scripts/ or http://fog.ccsf.edu/~msapiro/scripts/. The shell script method is described at http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.038.htp. With the shell method, the input to config_list (configfile in the FAQ) would contain msg_footer=First line of footer Second line ... Last line digest_footer=First line of footer Second line ... Last line You also want the set DEFAULT_MSG_FOOTER in mm_cfg.py (if you haven't changed DEFAULT_DIGEST_FOOTER, you don't need to now as it defaults to DEFAULT_MSG_FOOTER) so the footer is set for new lists. Thank you Mark, I've created footer.txt file with the following text: msg_footer = ___ %(real_name)s mailing list %(real_name)[EMAIL PROTECTED](host_name)s %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s Here comes a disclaimer text digest_footer = ___ %(real_name)s mailing list %(real_name)[EMAIL PROTECTED](host_name)s %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s Here comes a disclaimer text And run this script: for i in $(/usr/lib/mailman/bin/list_lists -b) ; do /usr/lib/mailman/bin/config_list -i /path_to/footer.txt $i ; done I've also added the following to /usr/lib/mailman/Mailman/mm_cfg.py, so all new created lists will get this disclaimer automatically: DEFAULT_MSG_FOOTER = ___ %(real_name)s mailing list %(real_name)[EMAIL PROTECTED](host_name)s %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s Here comes a disclaimer text -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan Best Regards, Leon Kolchinsky -- 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] Changing Unsubscribe to NoMail
I have a list in which I would like the unsubscribe to set the nomail flag on instead of removing them from the list. The reason being that the list administrators tend to upload new email addresses periodically and we would not like to add someone that has already unsubscribed. Is there a magic switch that will turn unsubscribe behavior into nomail behavior? The mailman command line does not support the nomail option? -- 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] domain in attached file url
Thanx Mark! That worked. :-) - Original Message - From: Mark Sapiro [EMAIL PROTECTED] To: ArteryPlanet.Net :: Manuel Kissoyan [EMAIL PROTECTED]; mailman mailing list mailman-users@python.org Sent: Sunday, January 21, 2007 3:22 PM Subject: Re: [Mailman-Users] domain in attached file url ArteryPlanet.Net :: Manuel Kissoyan wrote: Here is an example: -- next part -- A non-text attachment was scrubbed... Name: 704.pdf Type: application/pdf Size: 40815 bytes Desc: not available Url : /pipermail/mercedes_okiebenz.com/attachments/20070121/a1db2ede/attachment.pdf Any idea what could be the problem? This has all the earmarks of a cPanel Mailman - specifically 2.1.9-cp1? If so, this is a cPanel bug (fixed I think in 2.1.9-cp2). In any case, the problem is caused by an incorrect setting for PUBLIC_ARCHIVE_URL in mm_cfg.py. I.e., '/pipermail/%(listname)s' instead of 'http://%(hostname)s/pipermail/%(listname)s'. Also, see http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.011.htp -- 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, postfix virtual domains and mysql
Hi All, Mailman almost works... First some problems with the webserver but that's almost solved (can't use the list creaters and adminstrator password) Also got the following problem: I have a working postfix, mysql and virtual domains on the testserver.. This works fine and is also on the main server.. Now I want to install mailman (done) and integrate with my mailserver.. Does someone have a manual for postfix virtual domains with mysql? I looked it up in the site administrators manual but that's all about virtual domains and not about mysql.. My config files are very different. I use mysql_virtual_alias_maps, mysql_virtual_domains_maps and mysql_virtual_mailbox_maps files In these files are the following lines (table, select_field and where_field are different): user = username password = password hosts = localhost dbname = Databasename table = mailbox select_field = maildir where_field = username Can someone help me with this? Thanks -- 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] Archivierung
Hallo Mailman-Gemeinde, ich wollte fragen, ob es möglich ist bei deaktivierter Archivierungsoption auch die Ablage der Attachements in /usr/local/mailman/archives/private/ /attachements zu unterbinden und wenn ja, wie? Danke Micha -- 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] /bin/sh: mailman: command not found
I get a million of these messages from Cron. Subject: [Mailman] Cron [EMAIL PROTECTED] mailman/usr/lib/mailman/cron/gate_news I have read that it is because of something messed up with the crontab.in or soemthing. Something to do with the place #6 or something like that. I really did not find the message helpful at all since I know very little about cron in general. Can someone help? Otherwise I have Mailman fully functional on Fedora Core 6 and love it! - Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. -- 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] problems with gid when installing
Peter Coolen wrote: I tried example.com/mailman/ just for a visit or a index page but now I receive a 403 forbidden... Let's try to debug one issue at a time, but what's in error_log for the 403? The error when visiting domain.com/mailman/ [Mon Jan 22 10:01:52 2007] [error] [client 62.58.15.252] attempt to invoke directory as script: /usr/local/mailman As I said in http://mail.python.org/pipermail/mailman-users/2007-January/055473.html If you want this latter URL to work (usually people send it to the listinfo page), you need something like RedirectMatch ^/mailman[/]*$ http://example.com/mailman/listinfo in your Apache config. -- 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] problems with gid when installing
Peter Coolen wrote: Don't know why but it works almost ;-) I see a webpage and can create a new mailinglist... Only one last problem I can't create a new mailinglist.. Receive this error: Error: You are not authorized to create new mailing lists I changed the administrators passwd and list creater passwd with bin/mmsitepass -c or without -c but no effect.. I have seen other reports of this kind of thing, but first let's see if the web interface works in general. Try creating a list with bin/newlist and see if its web admin interface works. If that's all OK we can come back to the web create 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
Re: [Mailman-Users] problems with gid when installing
This is working fine now.. I also found a manual (in the dark environments of the internet) for postfix virtual domains mysql and mailman.. Hope to inform you when it works but don't know for sure. Thanks for all the help.. You are great!! -Oorspronkelijk bericht- Van: Mark Sapiro [mailto:[EMAIL PROTECTED] Verzonden: maandag 22 januari 2007 16:59 Aan: Peter Coolen; mailman-users@python.org Onderwerp: Re: [Mailman-Users] problems with gid when installing Peter Coolen wrote: Don't know why but it works almost ;-) I see a webpage and can create a new mailinglist... Only one last problem I can't create a new mailinglist.. Receive this error: Error: You are not authorized to create new mailing lists I changed the administrators passwd and list creater passwd with bin/mmsitepass -c or without -c but no effect.. I have seen other reports of this kind of thing, but first let's see if the web interface works in general. Try creating a list with bin/newlist and see if its web admin interface works. If that's all OK we can come back to the web create 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
Re: [Mailman-Users] /bin/sh: mailman: command not found
Ken Cheney wrote: I get a million of these messages from Cron. Subject: [Mailman] Cron [EMAIL PROTECTED] mailman/usr/lib/mailman/cron/gate_news I have read that it is because of something messed up with the crontab.in or soemthing. Something to do with the place #6 or something like that. There are two ways to install a crontab. The crontab can be a user's crontab and for the mailman user is usually in the file /var/spool/cron/mailman, but is usually manipulated with the crontab command (man 1 crontab). There are also system (package) crontabs which are usually found in the /etc/cron.d/ directory. These crontabs have a different format. Since they are not associated with a particular user, they have an additional entry for the username between the times and the command. Your problem is you have a file that was intended for /etc/cron.d/mailman, and it is installed in /var/spool/cron/mailman. You can fix this by moving /var/spool/cron/mailman to /etc/cron.d/, or by editing /var/spool/cron/mailman (as the mailman user give command 'crontab -e') and removing the word 'mailman' that precedes the command on each line of the file. -- 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] Changing Unsubscribe to NoMail
Gerald Drouillard wrote: I have a list in which I would like the unsubscribe to set the nomail flag on instead of removing them from the list. The reason being that the list administrators tend to upload new email addresses periodically and we would not like to add someone that has already unsubscribed. Is there a magic switch that will turn unsubscribe behavior into nomail behavior? No. There is no such switch, and implementing one would be tricky. Here are some random thoughts. You could set unsubscribe_policy to Yes, so unsubscribe requires approval, and then manually do what you want. You might be able to automate this or 'semi-automate' it. When you set nomail for the user, you probably also want to set password reminders off. This could cause confusion for a user who changes her/his mind and tries to subscribe and the subscribe fails because (s)he is already a member. The mailman command line does not support the nomail option? See the set_nomail.py withlist script at http://veenet.value.net/~msapiro/scripts/ or http://fog.ccsf.edu/~msapiro/scripts/. -- 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, postfix virtual domains and mysql
At 3:24 PM +0100 1/22/07, Peter Coolen wrote: Does someone have a manual for postfix virtual domains with mysql? I looked it up in the site administrators manual but that's all about virtual domains and not about mysql.. My config files are very different. This is a problem with postfix, and you're much more likely to get something useful from the documentation FAQs at postfix.org, as well as reading the archives of the postfix-users mailing list, etc If you still don't find the answers to your questions after going through all those resources, you might want to post your question to the postfix-users list. Once you get your postfix issues straightened out, we might be able to help you with your Mailman issues. -- Brad Knowles [EMAIL PROTECTED], Consultant Author Co-author of SAGE Booklet #15 Internet Postmaster: Duties and Responsibilities Founding Member and Platinum Individual Sponsor of LOPSA: http://www.lopsa.org Papers: http://tinyurl.com/tj6q4 LinkedIn Profile: http://tinyurl.com/y8kpxu -- 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] But I don't want any Korean
Very frustrating. I had a problem installing a mailman update a few months back
on Solaris 10. I posted the traceback, and a very patient person directed me
through modifying and repacking Setup.py in KoreanCodecs-2.0.5, and that did
the trick.
Now I'm trying to install another update, and I'm getting *Korean* errors
again. I tried editing and repacking the Setup.py file like last time, but that
didn't do it. So I did some googling and found instructions for editing and
repacking hangul.c in KoreanCodecs-2.0.5. That didn't work either.
Is there any way to disable Korean all-together, forever and ever, amen?! It's
just so frustrating to waste an entire day working a foreign language issue on
a product that will never be used by a non-English speaking person - ever.
Anyway, here's the traceback from the log file...
admin(2805): [- Mailman Version: 2.1.9 -]
admin(2805): [- Traceback --]
admin(2805): Traceback (most recent call last):
admin(2805): File /usr/local/mailman/scripts/driver, line 94, in run_main
admin(2805): pkg = __import__('Mailman.Cgi', globals(), locals(),
[scriptname])
admin(2805): File /usr/local/mailman/Mailman/Cgi/listinfo.py, line 26, in ?
admin(2805): from Mailman import Utils
admin(2805): File /usr/local/mailman/Mailman/Utils.py, line 39, in ?
admin(2805): import email.Header
admin(2805): File /usr/local/mailman/pythonlib/email/Header.py, line 13, in
?
admin(2805): from email.Charset import Charset
admin(2805): File /usr/local/mailman/pythonlib/email/Charset.py, line 178,
in ?
admin(2805): add_codec(_charset, _find_asian_codec(_charset, 'korean') or
_charset)
admin(2805): File /usr/local/mailman/pythonlib/email/Charset.py, line 163,
in _find_asian_codec
admin(2805): unicode('foo', charset)
admin(2805): File /usr/sfw/lib/python2.3/encodings/__init__.py, line 91, in
search_function
admin(2805): mod = __import__(modname, globals(), locals(), _import_tail)
admin(2805): File /usr/local/mailman/pythonlib/korean/johab.py, line 26, in
?
admin(2805): from korean.python.johab import *
admin(2805): File /usr/local/mailman/pythonlib/korean/python/johab.py, line
28, in ?
admin(2805): johab2uni_chosung = {
admin(2805): AttributeError: class Jaeum has no attribute 'SS'
admin(2805): [- Python Information -]
admin(2805): sys.version = 2.3.3 (#1, Dec 16 2004, 14:38:56) [C]
admin(2805): sys.executable = /usr/sfw/bin/python
admin(2805): sys.prefix = /usr/sfw
admin(2805): sys.exec_prefix = /usr/sfw
admin(2805): sys.path= /usr/sfw
admin(2805): sys.platform= sunos5
admin(2805): [- Environment Variables -]
admin(2805):SERVER_SOFTWARE: Apache/1.3.36 (Unix) mod_perl/1.29
admin(2805):SCRIPT_NAME: /mailman/listinfo
admin(2805):SERVER_SIGNATURE: ADDRESSApache/1.3.36 Server at 127.0.0.1
Port 80/ADDRESS
admin(2805):
admin(2805):REQUEST_METHOD: GET
admin(2805):SERVER_PROTOCOL: HTTP/1.1
admin(2805):QUERY_STRING:
admin(2805):HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT
5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 1.0.3705)
admin(2805):HTTP_CONNECTION: Keep-Alive
admin(2805):SERVER_NAME: 127.0.0.1
admin(2805):REMOTE_ADDR: 192.168.90.28
admin(2805):SERVER_PORT: 80
admin(2805):SERVER_ADDR: 192.168.90.5
admin(2805):DOCUMENT_ROOT: /var/apache/htdocs
admin(2805):PYTHONPATH: /usr/local/mailman
admin(2805):SCRIPT_FILENAME: /usr/local/mailman/cgi-bin/listinfo
admin(2805):SERVER_ADMIN: [EMAIL PROTECTED]
admin(2805):HTTP_HOST: m
admin(2805):HTTP_UA_CPU: x86
admin(2805):REQUEST_URI: /mailman/listinfo
admin(2805):HTTP_ACCEPT: image/gif, image/x-xbitmap, image/jpeg,
image/pjpeg, application/x-shockwave-flash, application/vnd.ms-excel,
application/vnd.ms-powerpoint, application/msword, */*
admin(2805):GATEWAY_INTERFACE: CGI/1.1
admin(2805):REMOTE_PORT: 3176
admin(2805):HTTP_ACCEPT_LANGUAGE: en-us
admin(2805):TZ: GMT-5-5
admin(2805):HTTP_ACCEPT_ENCODING: gzip, deflate
admin(2805):UNIQUE_ID: RbSPvcCoWgUAAAcbN8g
Thank you in advance for any assistance in either solving the problem, or
side-stepping it by disabling Korean support.
/kpt
--
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] But I don't want any Korean
Kent Taylor wrote:
Is there any way to disable Korean all-together, forever and ever, amen?! It's
just so frustrating to waste an entire day working a foreign language issue on
a product that will never be used by a non-English speaking person - ever.
Well, the real issue is what header files or ?? are missing on Solaris
10 that prevent successful compilation of hangul.c, but that issue
aside, I don't offhand know how to remove all traces of Korean from
the package in a way that would prevent the kind of error you're
seeing.
Anyway, here's the traceback from the log file...
snip
admin(2805): File /usr/local/mailman/pythonlib/korean/johab.py, line 26,
in ?
admin(2805): from korean.python.johab import *
admin(2805): File /usr/local/mailman/pythonlib/korean/python/johab.py,
line 28, in ?
admin(2805): johab2uni_chosung = {
admin(2805): AttributeError: class Jaeum has no attribute 'SS'
Is there a hangul.so (or hangul with some other extension) file in
/usr/local/mailman/pythonlib/korean/c/?
If so, try removing it or renaming it. It is probably defective since
you can't compile hangul.c and your edit may have broken it. If it
isn't there, the library will fall back to
/usr/local/mailman/pythonlib/korean/python/hangul.py which should work.
--
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 domain error
Hi, Can anyone help me. I have got 2 domains. Domain a.com and domain b.com and I would like to be able to write messages to either of those domains. I cannot work out how you do this though since my mailman router does not take into account anywhere the domain name, only $local_part (see below) So another question is since it (apparently) doesn't look at the $local_part why is it that a.com works but b.com doesn't. The /var/log/exim4/mainlog file shows no difference between a.com and b.com but yet b.com doesn't arrive?? Many thanks in advance for any help on offer de Chris G PS my mailman router is: mailman_router: driver = accept require_files = MAILMAN_HOME/lists/$local_part/config.pck local_part_suffix_optional local_part_suffix = -bounces : -bounces+* : \ -confirm+* : -join : -leave : \ -owner : -request : -admin transport = mailman_transport -- 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 domain error
Christopher Glanville wrote: The /var/log/exim4/mainlog file shows no difference between a.com and b.com but yet b.com doesn't arrive?? Are you saying that mail to [EMAIL PROTECTED] produces an exim log entry like 2007-01-22 22:38:05 JCB6FF-0001N0-GS = list [EMAIL PROTECTED] R=mailman_router T=mailman_transport If so, that message got delivered to Mailman's 'in' queue (or at least got piped to the wrapper, but if [EMAIL PROTECTED] works, we can assume that the wrapper does the same thing because it's called the same way). Lot's of things can happen to the message after that, but the most likely is the message is held because require_explicit_destination is yes, and Mailman is looking for [EMAIL PROTECTED] and [EMAIL PROTECTED] is not in acceptable_aliases. What's in the admindb interface waiting for moderator action? What's in Mailman's vette log? What's in Mailman's other logs? -- 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
