Mailman 3 January 2006 - Mailman-coders

[ mailman-Bugs-1305881 ] Problem creating list via web
by SourceForge.net Jan. 5, 2006

Jan. 5, 2006

Bugs item #1305881, was opened at 2005-09-27 08:49 Message generated for change (Comment added) made by echoism You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1305881&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Jon (jontek) Assigned to: Nobody/Anonymous (nobody) Summary: Problem creating list via web Initial Comment: I tried to create a list via: https://www.mydomain.dom/mailman/create. When filled all data, it replies with this message: ------------------------------------- Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/create.py", line 55, in main process_request(doc, cgidata) File "/usr/local/mailman/Mailman/Cgi/create.py", line 187, in process_request mlist.Create(listname, owner, pw, langs, emailhost) File "/usr/local/mailman/Mailman/MailList.py", line 457, in Create self.InitVars(name, admin, crypted_password) File "/usr/local/mailman/Mailman/MailList.py", line 372, in InitVars baseclass.InitVars(self) File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 95, in InitVars os.mkdir(self.archive_dir()+'.mbox', 02775) OSError: [Errno 13] Permission denied: '/usr/local/mailman/archives/private/listname.mbox' Python information: Variable Value sys.version 2.3.4 (#2, Aug 6 2004, 21:29:10) [GCC 2.95.4 20020320 [FreeBSD]] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd4 Environment variables: Variable Value HTTP_REFERER https://www.mydomain.dom/mailman/create SERVER_SOFTWARE Apache/1.3.31 (Unix) mod_perl/1.29 PHP/4.3.8 mod_ssl/2.8.19 OpenSSL/0.9.7d SCRIPT_NAME /mailman/create SERVER_SIGNATURE Apache/1.3.31 Server at www.mydomain.dom Port 443 REQUEST_METHOD POST HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 145 HTTP_ACCEPT_CHARSET ISO-8859-15,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.7.12) Gecko/20050922 Firefox/1.0.7 (Debian package 1.0.7-1) HTTP_CONNECTION keep-alive HTTP_COOKIE POSTNUKESID=4b502f13b908db42087f9b9753295c78; PHPSESSID=f7592dbf314acec6d743601e8cc3487f SERVER_NAME www.mydomain.dom REMOTE_ADDR 83.33.129.253 SERVER_PORT 443 SERVER_ADDR 207.228.236.31 DOCUMENT_ROOT /usr/local/www/data/www.mydomain.dom PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/create SERVER_ADMIN webmaster(a)mydomain.dom HTTP_HOST www.mydomain.dom HTTPS on REQUEST_URI /mailman/create HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 3249 HTTP_ACCEPT_LANGUAGE eu,es-es;q=0.7,es;q=0.3 CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip,deflate UNIQUE_ID QzlLGc-k7B8AAR2b2MM --------------------------- Thanks JOn ---------------------------------------------------------------------- Comment By: echoism (echoism) Date: 2006-01-05 10:34 Message: Logged In: YES user_id=1420107 I had this same problem. It is a permission issue, because the webserver doesn't have access to create a file in /usr/local/mailman/archives/private. This directory has permissions of 750, owned by the mailman user. The webserver, however, runs cgi scripts as nobody, not mailman. You can confirm this, by checking your /usr/local/mailman/lists directory, the list you tried to create should have a directory there, owned by nobody (or, whatever account your webserver uses), as the permissions for the lists directory permit write access. ---------------------------------------------------------------------- Comment By: Jon (jontek) Date: 2005-09-27 09:44 Message: Logged In: YES user_id=1352490 #/usr/local/mailman>/usr/local/mailman/bin/check_perms No problems found #/usr/local/mailman> ---------------------------------------------------------------------- Comment By: Jon (jontek) Date: 2005-09-27 09:32 Message: Logged In: YES user_id=1352490 Thanks but it doesn't still work. I have done: /usr/local/mailman/bin/check_perms -f and fixed all the problems, but it still doesn't work. :o( ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-09-27 09:21 Message: Logged In: YES user_id=12800 Run bin/check_perms ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1305881&group_…

1 0

[ mailman-Patches-1365282 ] Add New Langauge Punjabi (pa) to mailman
by SourceForge.net Jan. 5, 2006

Jan. 5, 2006

Patches item #1365282, was opened at 2005-11-24 05:19 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1365282&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Amanpreet Singh Alam (aalam) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Add New Langauge Punjabi (pa) to mailman Initial Comment: Hello I translate mailman to Punajbi and Want to include in mailman. As per direction from Barry, I m attaching file here! following is info about Language "Punjabi" ISO Code = "pa" Coding = Unicode (UTF-8) Can u please include those files for Punjabi to Mailman? thanks AP Singh Alam http://punlinux.sf.net ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2006-01-05 07:35 Message: Logged In: YES user_id=67709 Sorry for the delayed response but what is your output from 'bin/transcheck pa' ? ---------------------------------------------------------------------- Comment By: Amanpreet Singh Alam (aalam) Date: 2005-11-28 05:45 Message: Logged In: YES user_id=1200839 I buid on Fedora and it was ready can u please help me to send the errors? thanks AP Singh ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-11-26 06:32 Message: Logged In: YES user_id=67709 Hi, I tested your translation and get error. Will you please test your translation by yourself before submitting to the patch tracker? You should add your language in templates/Makefile.in, messages/Makefile.in and Mailman/Defaults.py.in then do the configure/make install. bin/transcheck should help debugging. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1365282&group_…

1 0

[ mailman-Bugs-1395683 ] UnicodeError running arch
by SourceForge.net Jan. 5, 2006

Jan. 5, 2006

Bugs item #1395683, was opened at 2006-01-03 01:12 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael Wallis (kf6spf) Assigned to: Nobody/Anonymous (nobody) Summary: UnicodeError running arch Initial Comment: I just deployed the latest release (2.1.7 stable) and decided to rebuild an archive. I'm getting the following error trace caused by it hitting high-order byte characters. These were not a problem when I first built the archive from 2.1.6 so something may have changed. Pickling archive state into /usr/local/mailman/archives/private/basfa/pipermail.pck Traceback (most recent call last): File "bin/arch", line 200, in ? main() File "bin/arch", line 188, in main archiver.processUnixMailbox(fp, start, end) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 585, in processUnixMailbox self.add_article(a) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 626, in add_article filename)) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1116, in write_article f.write(article.as_text()) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 579, in as_text '\g<1>' + _(' at ') + '\g<2>', body) File "/usr/lib/python2.2/sre.py", line 143, in sub return _compile(pattern, 0).sub(repl, string, count) UnicodeError: ASCII decoding error: ordinal not in range(128) ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2006-01-05 02:50 Message: Logged In: YES user_id=67709 Here is a revised patch to incorporate non-ascii '_at_' replacement. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-01-03 18:20 Message: Logged In: YES user_id=1123998 One other followup note on this. The problem can also occur when archiving an individual post to a list. In this case, the HTML file for the post will be written but not indexed; the post will not be added to the .txt file; the error will be logged in the 'error' log, and the message will be shunted. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-01-03 17:28 Message: Logged In: YES user_id=1123998 The previous patch wasn't effective in all circumstances. I have replaced it again. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-01-03 05:21 Message: Logged In: YES user_id=1123998 I've developed a new patch which I've attached here in place of the previous one. I think the new patch actually fixes the problem. Please try it and report. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-01-03 01:54 Message: Logged In: YES user_id=1123998 I also observed this problem. It will be properly fixed. In the mean time, I have attached a patch - HyperArch.patch - which will allow you to rebuild the full archive. The patch is not a real fix for the problem however, as the problem messages will not have email addresses obscured in the body of the message in the monthly .txt files. The HTML archive will be OK. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_…

1 0

[ mailman-Bugs-1397214 ] Cron DeprecationWarning with Python 2.4
by SourceForge.net Jan. 4, 2006

Jan. 4, 2006

Bugs item #1397214, was opened at 2006-01-04 21:53 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1397214&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Schoinobates Volans (schoinobates) Assigned to: Nobody/Anonymous (nobody) Summary: Cron DeprecationWarning with Python 2.4 Initial Comment: This is Debian bug #341699: http://bugs.debian.org/341699 The cron script senddigests spews: DeprecationWarning: get_type() deprecated; use get_content_type() ctype = part.get_type(part.get_default_type()) Here's a patch that shuts up the warning, as you want to keep Python 2.1 compatibility (get_content_type() appeared in Python 2.2.2). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1397214&group_…

1 0

[ mailman-Bugs-1395683 ] UnicodeError running arch
by SourceForge.net Jan. 3, 2006

Jan. 3, 2006

Bugs item #1395683, was opened at 2006-01-02 17:12 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael Wallis (kf6spf) Assigned to: Nobody/Anonymous (nobody) Summary: UnicodeError running arch Initial Comment: I just deployed the latest release (2.1.7 stable) and decided to rebuild an archive. I'm getting the following error trace caused by it hitting high-order byte characters. These were not a problem when I first built the archive from 2.1.6 so something may have changed. Pickling archive state into /usr/local/mailman/archives/private/basfa/pipermail.pck Traceback (most recent call last): File "bin/arch", line 200, in ? main() File "bin/arch", line 188, in main archiver.processUnixMailbox(fp, start, end) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 585, in processUnixMailbox self.add_article(a) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 626, in add_article filename)) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1116, in write_article f.write(article.as_text()) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 579, in as_text '\g<1>' + _(' at ') + '\g<2>', body) File "/usr/lib/python2.2/sre.py", line 143, in sub return _compile(pattern, 0).sub(repl, string, count) UnicodeError: ASCII decoding error: ordinal not in range(128) ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-01-03 10:20 Message: Logged In: YES user_id=1123998 One other followup note on this. The problem can also occur when archiving an individual post to a list. In this case, the HTML file for the post will be written but not indexed; the post will not be added to the .txt file; the error will be logged in the 'error' log, and the message will be shunted. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-01-03 09:28 Message: Logged In: YES user_id=1123998 The previous patch wasn't effective in all circumstances. I have replaced it again. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-01-02 21:21 Message: Logged In: YES user_id=1123998 I've developed a new patch which I've attached here in place of the previous one. I think the new patch actually fixes the problem. Please try it and report. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-01-02 17:54 Message: Logged In: YES user_id=1123998 I also observed this problem. It will be properly fixed. In the mean time, I have attached a patch - HyperArch.patch - which will allow you to rebuild the full archive. The patch is not a real fix for the problem however, as the problem messages will not have email addresses obscured in the body of the message in the monthly .txt files. The HTML archive will be OK. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_…

1 0

[ mailman-Bugs-1395683 ] UnicodeError running arch
by SourceForge.net Jan. 3, 2006

Jan. 3, 2006

Bugs item #1395683, was opened at 2006-01-02 17:12 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael Wallis (kf6spf) Assigned to: Nobody/Anonymous (nobody) Summary: UnicodeError running arch Initial Comment: I just deployed the latest release (2.1.7 stable) and decided to rebuild an archive. I'm getting the following error trace caused by it hitting high-order byte characters. These were not a problem when I first built the archive from 2.1.6 so something may have changed. Pickling archive state into /usr/local/mailman/archives/private/basfa/pipermail.pck Traceback (most recent call last): File "bin/arch", line 200, in ? main() File "bin/arch", line 188, in main archiver.processUnixMailbox(fp, start, end) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 585, in processUnixMailbox self.add_article(a) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 626, in add_article filename)) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1116, in write_article f.write(article.as_text()) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 579, in as_text '\g<1>' + _(' at ') + '\g<2>', body) File "/usr/lib/python2.2/sre.py", line 143, in sub return _compile(pattern, 0).sub(repl, string, count) UnicodeError: ASCII decoding error: ordinal not in range(128) ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-01-03 09:28 Message: Logged In: YES user_id=1123998 The previous patch wasn't effective in all circumstances. I have replaced it again. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-01-02 21:21 Message: Logged In: YES user_id=1123998 I've developed a new patch which I've attached here in place of the previous one. I think the new patch actually fixes the problem. Please try it and report. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-01-02 17:54 Message: Logged In: YES user_id=1123998 I also observed this problem. It will be properly fixed. In the mean time, I have attached a patch - HyperArch.patch - which will allow you to rebuild the full archive. The patch is not a real fix for the problem however, as the problem messages will not have email addresses obscured in the body of the message in the monthly .txt files. The HTML archive will be OK. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_…

1 0

[ mailman-Bugs-1395683 ] UnicodeError running arch
by SourceForge.net Jan. 3, 2006

Jan. 3, 2006

Bugs item #1395683, was opened at 2006-01-02 17:12 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael Wallis (kf6spf) Assigned to: Nobody/Anonymous (nobody) Summary: UnicodeError running arch Initial Comment: I just deployed the latest release (2.1.7 stable) and decided to rebuild an archive. I'm getting the following error trace caused by it hitting high-order byte characters. These were not a problem when I first built the archive from 2.1.6 so something may have changed. Pickling archive state into /usr/local/mailman/archives/private/basfa/pipermail.pck Traceback (most recent call last): File "bin/arch", line 200, in ? main() File "bin/arch", line 188, in main archiver.processUnixMailbox(fp, start, end) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 585, in processUnixMailbox self.add_article(a) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 626, in add_article filename)) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1116, in write_article f.write(article.as_text()) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 579, in as_text '\g<1>' + _(' at ') + '\g<2>', body) File "/usr/lib/python2.2/sre.py", line 143, in sub return _compile(pattern, 0).sub(repl, string, count) UnicodeError: ASCII decoding error: ordinal not in range(128) ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-01-02 21:21 Message: Logged In: YES user_id=1123998 I've developed a new patch which I've attached here in place of the previous one. I think the new patch actually fixes the problem. Please try it and report. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-01-02 17:54 Message: Logged In: YES user_id=1123998 I also observed this problem. It will be properly fixed. In the mean time, I have attached a patch - HyperArch.patch - which will allow you to rebuild the full archive. The patch is not a real fix for the problem however, as the problem messages will not have email addresses obscured in the body of the message in the monthly .txt files. The HTML archive will be OK. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_…

1 0

[ mailman-Bugs-1395683 ] UnicodeError running arch
by SourceForge.net Jan. 3, 2006

Jan. 3, 2006

Bugs item #1395683, was opened at 2006-01-02 17:12 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael Wallis (kf6spf) Assigned to: Nobody/Anonymous (nobody) Summary: UnicodeError running arch Initial Comment: I just deployed the latest release (2.1.7 stable) and decided to rebuild an archive. I'm getting the following error trace caused by it hitting high-order byte characters. These were not a problem when I first built the archive from 2.1.6 so something may have changed. Pickling archive state into /usr/local/mailman/archives/private/basfa/pipermail.pck Traceback (most recent call last): File "bin/arch", line 200, in ? main() File "bin/arch", line 188, in main archiver.processUnixMailbox(fp, start, end) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 585, in processUnixMailbox self.add_article(a) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 626, in add_article filename)) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1116, in write_article f.write(article.as_text()) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 579, in as_text '\g<1>' + _(' at ') + '\g<2>', body) File "/usr/lib/python2.2/sre.py", line 143, in sub return _compile(pattern, 0).sub(repl, string, count) UnicodeError: ASCII decoding error: ordinal not in range(128) ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-01-02 17:54 Message: Logged In: YES user_id=1123998 I also observed this problem. It will be properly fixed. In the mean time, I have attached a patch - HyperArch.patch - which will allow you to rebuild the full archive. The patch is not a real fix for the problem however, as the problem messages will not have email addresses obscured in the body of the message in the monthly .txt files. The HTML archive will be OK. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_…

1 0

[ mailman-Bugs-1395683 ] UnicodeError running arch
by SourceForge.net Jan. 3, 2006

Jan. 3, 2006

Bugs item #1395683, was opened at 2006-01-02 17:12 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael Wallis (kf6spf) Assigned to: Nobody/Anonymous (nobody) Summary: UnicodeError running arch Initial Comment: I just deployed the latest release (2.1.7 stable) and decided to rebuild an archive. I'm getting the following error trace caused by it hitting high-order byte characters. These were not a problem when I first built the archive from 2.1.6 so something may have changed. Pickling archive state into /usr/local/mailman/archives/private/basfa/pipermail.pck Traceback (most recent call last): File "bin/arch", line 200, in ? main() File "bin/arch", line 188, in main archiver.processUnixMailbox(fp, start, end) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 585, in processUnixMailbox self.add_article(a) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 626, in add_article filename)) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1116, in write_article f.write(article.as_text()) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 579, in as_text '\g<1>' + _(' at ') + '\g<2>', body) File "/usr/lib/python2.2/sre.py", line 143, in sub return _compile(pattern, 0).sub(repl, string, count) UnicodeError: ASCII decoding error: ordinal not in range(128) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_…

1 0

[ mailman-Feature Requests-1395591 ] Forced user setup adjustment notification
by SourceForge.net Jan. 2, 2006

Jan. 2, 2006

Feature Requests item #1395591, was opened at 2006-01-02 22:34 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1395591&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: STanda Opichal (opichals) Assigned to: Nobody/Anonymous (nobody) Summary: Forced user setup adjustment notification Initial Comment: Hi! For example when the user's email is bouncing frequently mailman switches the user profile to the 'disabled' state. The use has however no chance to get any notification about this happened. I would propose to allow use to specify another email address to be notified at when something was automatically chaged because of a problem found during operation. Best Regards Standa ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1395591&group_…

1 0