[Mailman-Users] TypeError: decoding Unicode is not supported
mailman 2.1.5-8sarge5 running on Debian 4.0. It's actually a custom
package I built myself with only minor changes for my mail environment.
It's an odd one... A search of Google and the archives shows that it's
been discussed before but with no definitive answer. One user is having
problems posting to a list. Mailman's error log shows the following
error, the e-mail which caused the problem is also supplied below.
Any idea what's causing this problem?
Thanks,
James
May 18 09:50:13 2007 (29323) Uncaught runner exception: decoding Unicode
is not supported
May 18 09:50:13 2007 (29323) Traceback (most recent call last):
File /var/lib/mailman/Mailman/Queue/Runner.py, line 111, in _oneloop
self._onefile(msg, msgdata)
File /var/lib/mailman/Mailman/Queue/Runner.py, line 167, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /var/lib/mailman/Mailman/Queue/IncomingRunner.py, line 130, in
_dispose
more = self._dopipeline(mlist, msg, msgdata, pipeline)
File /var/lib/mailman/Mailman/Queue/IncomingRunner.py, line 153, in
_dopipeline
sys.modules[modname].process(mlist, msg, msgdata)
File /var/lib/mailman/Mailman/Handlers/ToDigest.py, line 91, in process
send_digests(mlist, mboxfp)
File /var/lib/mailman/Mailman/Handlers/ToDigest.py, line 132, in
send_digests
send_i18n_digests(mlist, mboxfp)
File /var/lib/mailman/Mailman/Handlers/ToDigest.py, line 306, in
send_i18n_digests
msg = scrubber(mlist, msg)
File /var/lib/mailman/Mailman/Handlers/Scrubber.py, line 318, in process
partcharset = part.get_content_charset()
File email/Message.py, line 800, in get_content_charset
TypeError: decoding Unicode is not supported
May 18 09:50:13 2007 (29323) SHUNTING:
1179478212.3616531+d13a31b783297c1f32c72ac08da016a012618db4
Here's the e-mail that caused the error.
Return-path: [EMAIL PROTECTED]
Envelope-to: [EMAIL PROTECTED]
Delivery-date: Fri, 18 May 2007 09:50:11 +0100
Received: from web25413.mail.ukl.yahoo.com ([217.146.176.231])
by freecharity.org.uk with smtp (Exim 4.63)
(envelope-from [EMAIL PROTECTED])
id 1HoyA5-0002yc-4y
for [EMAIL PROTECTED]; Fri, 18 May 2007 09:50:11 +0100
Received: (qmail 17787 invoked by uid 60001); 18 May 2007 08:50:09 -
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=s1024; d=yahoo.co.uk;
h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
b=TdkF35y16JDEIDEuLY4cGmrqstW67SrzR6Oj1Pa1Fc06qQZQFQx030h9xSizSQqXW/c5l9iDUCR9fCDlaR4yfzl8r7J/5vFS3F0UWj6NNGrqRnDTTe97jnOI7EVkaGK5qlJd7WcHhiGtR18sYPc+IacwfC8bVeuaECjzrq8P7cU=;
X-YMail-OSG:
CDYiRqkVM1lWc7oO9wflIqiW8_jrhpJzkYW.kGwhGMoYZtkKTIImK3OMRH0uKk0Hm6dMHimPwA--
Received: from [195.110.70.55] by web25413.mail.ukl.yahoo.com via HTTP;
Fri, 18 May 2007 08:50:08 GMT
X-Mailer: YahooMailRC/651.23.1 YahooMailWebService/0.7.41.14
Date: Fri, 18 May 2007 08:50:08 + (GMT)
From: Stefan Laros [EMAIL PROTECTED]
Subject: Symphony
To: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary=0-707090045-1179478208=:17471
Message-ID: [EMAIL PROTECTED]
X-Spam-Score: 1.9 (+)
X-Spam-Status: No, hits=1.9 required=5.0
tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,HTML_MESSAGE autolearn=no
version=_VERSION
--0-707090045-1179478208=:17471
Content-Type: text/plain; charset=ascii
All,
Further to my earlier e-mails: we will only be rehearsing the symphony
this Sunday!
See you then there.
Stefan
--0-707090045-1179478208=:17471
Content-Type: text/html; charset=ascii
htmlheadstyle type=text/css!-- DIV {margin:0px;}
--/style/headbodydiv style=font-family:arial, helvetica,
sans-serif;font-size:10ptDIV/DIV
DIV
DIV style=FONT-SIZE: 10pt; FONT-FAMILY: arial, helvetica, sans-serif
DIV/DIV
DIVAll,/DIV
DIVnbsp;/DIV
DIVFurther to my earlier e-mails: we will only be rehearsing the
symphony thisnbsp;Sunday!BR/DIV
DIVSee you then amp; there./DIV
DIVnbsp;/DIV
DIVStefan/DIV
DIVnbsp;/DIV
DIVnbsp;/DIV/DIV/DIV/div/body/html
--0-707090045-1179478208=:17471--
--
http://www.freecharity.org.uk/ - Free IT services for charities
http://www.freecharity.org.uk/wiki/ - The VCSWiki
--
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 professional help
Just to let everyone know I am going with the following solution: Hypermail (http://www.hypermail.org/) for archiving and Sphider (http://cs.ioc.ee/~ando/sphider/) as the search engine. Since cPanel would overwrite any changes or patches I would make to the mailman installation whenever a new version would come out, I decided to nix the idea of using a custom patch applied to my mailman installation. I rather use a third party solution such as above to create archives on a list by list basis. My programmer will be doing the installation and configuration and will be detailing the steps to setup searchable archives outside of mailman's installation directory. Would this be something worthwhile to add to the Mailman FAQ? Kind regards, Brian Carpenter -- EMWD - Executive Officer -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ivan Van Laningham Sent: Thursday, May 17, 2007 7:37 PM Cc: mailman-users@python.org Subject: Re: [Mailman-Users] Looking for professional help Hi All-- Brad Knowles wrote: Really, these kinds of questions should be directed at your service provider (assuming they installed cPanel for you), or the cPanel folks. They've made some extensive changes to the Mailman code and haven't contributed those back to us, so our ability to support their package is extremely limited. That's interesting. I use Plesk, and have not found anything different in my Mailman installation in the Python/HTML and config files other than a different base location than an installed-from-source Mailman would have. Everything behaves the way I expect, except for the fact that I have to create lists using Plesk, which is not a hardship (and in fact it's easier than my much older previous installation from source). Does anyone know whether or not Plesk has made any changes? Metta, Ivan -- Ivan Van Laningham God N Locomotive Works http://www.pauahtun.org/ http://www.python.org/workshops/1998-11/proceedings/papers/laningham/laningh am.html Army Signal Corps: Cu Chi, Class of '70 Author: Teach Yourself Python in 24 Hours -- 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/brian%40emwd.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Looking for professional help
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On May 18, 2007, at 10:16 AM, Brian Carpenter wrote: My programmer will be doing the installation and configuration and will be detailing the steps to setup searchable archives outside of mailman's installation directory. Would this be something worthwhile to add to the Mailman FAQ? That or the Mailman wiki wiki.list.org Please do! - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iQCVAwUBRk24Q3EjvBPtnXfVAQKs4wP/adIoVQmyjPaWCOjykxkVIBHZ2g5S29d0 I4fNuHvJIdSb+ikalsHJjMh5U+PoM9AUbBiKQWxQfaOmgJKBUQS3ngRLRUv/pbvG bomJE3Vf8tfLOOhNxcCXVvulPShNeLgmjejqeQxERiWfIJTZ//A/UQwJMe6GRRCi ZfLIxkxkJgM= =RhEi -END PGP SIGNATURE- -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Suprised unsubscribes
Hi List: I had a client report to me this morning that several of his lists mysteriously unsubscribed members of the list without their permission or interventions. As far as I can tell these members were not generating any bounces. I checked the FAQ and archives of this list but I found nothing that would explain this behavior. Could there be any other possible reasons for this other than: 1. Intentional action by member 2. Intentional action by administrator 3. Bounce removal Any insight would be helpful. Thanks. Kind regards, Brian Carpenter -- EMWD - Executive Officer -- 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 professional help
Hi All-- Brian, will these be publicly searchable and publicly accessible archives? I would like to make my private archives searchable, but only by subscribed members. Either way, however, you should certainly update the FAQ/Wiki. Metta, Ivan Barry Warsaw wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On May 18, 2007, at 10:16 AM, Brian Carpenter wrote: My programmer will be doing the installation and configuration and will be detailing the steps to setup searchable archives outside of mailman's installation directory. Would this be something worthwhile to add to the Mailman FAQ? That or the Mailman wiki wiki.list.org Please do! - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iQCVAwUBRk24Q3EjvBPtnXfVAQKs4wP/adIoVQmyjPaWCOjykxkVIBHZ2g5S29d0 I4fNuHvJIdSb+ikalsHJjMh5U+PoM9AUbBiKQWxQfaOmgJKBUQS3ngRLRUv/pbvG bomJE3Vf8tfLOOhNxcCXVvulPShNeLgmjejqeQxERiWfIJTZ//A/UQwJMe6GRRCi ZfLIxkxkJgM= =RhEi -END PGP SIGNATURE- -- Ivan Van Laningham God N Locomotive Works http://www.pauahtun.org/ http://www.python.org/workshops/1998-11/proceedings/papers/laningham/laningham.html Army Signal Corps: Cu Chi, Class of '70 Author: Teach Yourself Python in 24 Hours -- 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 professional help
Only if the client wants it. If they want it private then setting them up with password protection via .htaccess is easy enough. Kind regards, Brian Carpenter -- EMWD - Executive Officer -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ivan Van Laningham Sent: Friday, May 18, 2007 11:25 AM Cc: mailman-users@python.org Subject: Re: [Mailman-Users] Looking for professional help Hi All-- Brian, will these be publicly searchable and publicly accessible archives? I would like to make my private archives searchable, but only by subscribed members. Either way, however, you should certainly update the FAQ/Wiki. Metta, Ivan Barry Warsaw wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On May 18, 2007, at 10:16 AM, Brian Carpenter wrote: My programmer will be doing the installation and configuration and will be detailing the steps to setup searchable archives outside of mailman's installation directory. Would this be something worthwhile to add to the Mailman FAQ? That or the Mailman wiki wiki.list.org Please do! - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iQCVAwUBRk24Q3EjvBPtnXfVAQKs4wP/adIoVQmyjPaWCOjykxkVIBHZ2g5S29d0 I4fNuHvJIdSb+ikalsHJjMh5U+PoM9AUbBiKQWxQfaOmgJKBUQS3ngRLRUv/pbvG bomJE3Vf8tfLOOhNxcCXVvulPShNeLgmjejqeQxERiWfIJTZ//A/UQwJMe6GRRCi ZfLIxkxkJgM= =RhEi -END PGP SIGNATURE- -- Ivan Van Laningham God N Locomotive Works http://www.pauahtun.org/ http://www.python.org/workshops/1998-11/proceedings/papers/laningham/laningh am.html Army Signal Corps: Cu Chi, Class of '70 Author: Teach Yourself Python in 24 Hours -- 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/brian%40emwd.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] HOWTO for easy subscribe/unsubscribe via a simplewebform
peter pilsl wrote: Unfortunately the Unsubscribe still gives me a headache. Creating a simple webform seems to be almost impossible, cause the unsubscribe-link needs to contain the users mailadress and does not respect the confirmation needed for unsubscription-settings in the list-options The confirmation needed for unsubscription-settings in the list-options controls whether or not a list admin or moderator must approve the unsubscription. It does not control whether or not the user has to confirm an unsubscription request. In order to prevent users from being onsubscribed by third parties without their consent, Mailman requires the any unsubscription request that does not come from the list admin interface or the password authenticated user be confirmed by the user's response to a confirmation email. If you want to bypass this confirmation, you need to submit the request for example as though it came from the admin mass removal page with the list admin or moderator password or from the user options page with the user's or the list admin or moderator password. See the whole thread starting at http://mail.python.org/pipermail/mailman-users/2004-December/041213.html for more information. http://SERVERNAME/mailman/options/LISTNAME/ADRESS?unsub=Unsubscribe;unsubconfirm=1 The above needs a password to avoid confirmation. See the referenced thread. And I didnt find a way to customize the unsubscribe-result-html-page It is built on the fly by code/data in Mailman/Cgi/options.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] Please help with some list options...
Mailman Users wrote: Then install your modified option file: bin/config_list -i data/YourListName.cfg YourListName Just in case anyone doesn't realize it, it is not necessary to provide bin/config_list with a complete configuration. It is sufficient to include in the input only the things you wish to change. -- 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] 'Discard all messages marked Defer' not working
Rick Pasotto wrote: On Wed, May 16, 2007 at 03:45:42PM -0400, Rick Pasotto wrote: It doesn't work for subscription requests. It still works fine for posts. On a page that had one of each the post was discarded but not the subscription request. On a page with just a subscription request nothing at all happens. Using 2.1.9 on debian. It just occurred to me that 'messages' != 'administrative requests' which is how I was reading it. If that is in fact the intent, is there some way it could be made clearer? It certainly makes no sense to have the option when there are no messages to which it would apply though I do recognize the difficulty of programming that. Yes, it is the intent that it apply only to 'messages'. Do you have a suggestion as to how to make it more clear? I agree that it doesn't make sense to offer the option when there are no messages on the page, but as you recognize, this would require an initial extra pass through the requests as the page is currently built sequentially, and the checkbox at the top is created before we know if any of the requests are 'messages'. -- 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] How to configure a list for invitation-onlysubscriptions?
Carter Braxton wrote: I think I'm getting close -- so far I've done the following: 1. Disabled the -subscribe email address for the list. 2. Edited the list info page to remove the signup option and replaced it with a notice that membership is via invitation only. (I found the file to modify is /etc/mailman/en/listinfo.html.) 3. Made sure the list is not advertised on the site-wide web page. 4. Used apache to impose a name and password for web access. This pretty much leaves the subscribe option in the email interface as the remaining loophole. I would need to modify the Mailman source to remove this keyword, and to modify the help file that users can request. (Anyone know offhand what files are involved?) Of course I could just disable the -request address for the list, disabling the email interface entirely. I'm a little reluctant to do this, though I expect that at this point most users will want to use thuh web to manage their options. You really don't need to go to all this trouble. Just set subscribe_policy to approve or confirm and approve and manually discard any held subscription requests. Acceptance of an invitation is not held, so that is not an issue. I really don't think there would be so many subscribe requests that discarding them via the admindb interface would be an issue. If you really want to disable the subscribe email command, just change Mailman/Commands/cmd_subscribe.py to respond that subscription is by invitation only. That will take care of subscribe commande to -request as well as mail to -subscribe and -join. If you want to remove the subscribe info from the help command, you can just remove def gethelp(mlist): return _(__doc__) from Mailman/Commands/cmd_subscribe.py. Or you can change the doc string in that module to provide an alternate message. -- 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] How to configure a list for invitation-onlysubscriptions?
Carter Braxton wrote: Thanks -- I thought of trying something like that, trouble is that requires that I would have to manually approve all of those who respond to the invitations, and that could potentially be several hundred (kind of a pain). No it doesn't. Regardless of subscribe_policy, invitations only have to be accepted by the user. Further confirmation or approval is not required. -- 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 and LDAP
I am using Mailman 2.19. Has written any scripts to sync Mailing lists with LDAP? Just wondering. Thanks, Matt Zimmerman -- 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] how can i simulate mailman pages
Patrick Bogen wrote: i tested it, but it does not work and i don't know why. The problem is probably that the /admin/* pages require the list or site admin password to be in a cookie, and normal users aren't going to have that. It can also be provided in the POST data. See for example the thread at http://mail.python.org/pipermail/mailman-users/2004-December/041213.html. -- 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] neither receiving or sending
Michael Rainey wrote: It is a binary packaged version, Linux, not sure which flavor, always assumed Redhat If it's RedHat with Mailman 2.1.5, the installation is probably in /var/mailman an the log files in /var/log/mailman. The aliases are there. I am ready to tell them to go ahead and do a complete reinstall, but want to make sure I have got my subscriber list intact. It should be visible to me as admin but is not, and even when I change privacy option to list visible to subscribers or to all it doe not let me see. Can you see the membership on the admin membership list? The roster doesn't show hidden members regardless of who requests it (this will be fixed in 2.1.10). Don't do the reinstall untill you have gone through http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.078.htp. My guess as the most likely problem is the qrunners aren't running (item 1b in the FAQ). You may not be able to do some things like bin/check_perms, but check the things you can. I rely on CP completely as am novice at SSH and also afraid I will mess it up even more. I do have a CP for server and access/ see root there Two issues: 1. How can I see, retrieve or back up my list (remembering I know how to log in with SSH but that's about all) /var/mailman/lists/listname/config.pck (assuming I have the first part of the path right) has all the list settings, the membership list and all the member options. /var/mailman/archives/private/listname.mbox/listname.mbox has all you need to rebuild the archives with /var/mailman/bin/arch, and the already built archives are in /var/mailman/archives/private/listname/ 2. Any other ideas about basic not sending or receiving. The above referenced FAQ article. -- 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] TypeError: decoding Unicode is not supported
James Davis wrote: It's an odd one... A search of Google and the archives shows that it's been discussed before but with no definitive answer. One user is having problems posting to a list. Mailman's error log shows the following error, the e-mail which caused the problem is also supplied below. Any idea what's causing this problem? The shunted message is not the one causing the problem. It will happen to every message from now on as the problem is caused by some prior message in lists/listname/digest.mbox. If you move the digest.mbox aside, the list will start processing again and you can run bin/unshunt to process the shunted messages. The best way to fix it is to edit the digest.mbox in place and fix the offending message (which may have a Content-Type: header with charset=Unicode instead of charset=utf-8), and then unshunt any messages that were shunted due to this error. If you just move digest.mbox aside and don't replace it, you'll lose a digest. even if you do fix and replace it, you may wind up with and 'out of sequence' digest. -- 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] Suprised unsubscribes
Brian Carpenter wrote: I had a client report to me this morning that several of his lists mysteriously unsubscribed members of the list without their permission or interventions. As far as I can tell these members were not generating any bounces. I checked the FAQ and archives of this list but I found nothing that would explain this behavior. Could there be any other possible reasons for this other than: 1. Intentional action by member 2. Intentional action by administrator 3. Bounce removal Check Mailman's subscribe log? The unsubscribes and reasons should be there. Members with stale bounce info can be disabled (or unsubscribed if bounce_you_are_disabled_warnings = 0) if bounce_score_threshold is lowered to a value = the member's stale bounce score. I suppose you could add to your list 'intentional action by a third party who somehow compromised user passwords, the list admin password or the site password or found an unknown security hole'. I don't think this is likely, particularly the security hole. -- 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 and LDAP
Matt Zimmerman wrote: I am using Mailman 2.19. Has written any scripts to sync Mailing lists with LDAP? Just wondering. Get your membership list from LDAP and use bin/sync_members to update Mailman. You might also be interested in http://sourceforge.net/tracker/index.php?func=detailaid=871062group_id=103atid=300103. -- 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] Suprised unsubscribes
Thanks Mark. You led to me to the answer. Actually here is what happended. Client subscribed an e-mail forwarded to a list. This e-mail forwarder forwards to some other mailing lists. Well someone unsubscribed the e-mail forwarded from a list and the unsubscribe notification was sent to it and then forwarded on to some other mailing lists. So people from these other lists also receive unsubscribe notifications and panic. The answer my friend is blowing in the wind (log files), the answer is blowing in the wind (log files). Kind regards, Brian Carpenter -- EMWD - Executive Officer -Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Friday, May 18, 2007 4:01 PM To: Brian Carpenter; mailman-users@python.org Subject: Re: [Mailman-Users] Suprised unsubscribes Brian Carpenter wrote: I had a client report to me this morning that several of his lists mysteriously unsubscribed members of the list without their permission or interventions. As far as I can tell these members were not generating any bounces. I checked the FAQ and archives of this list but I found nothing that would explain this behavior. Could there be any other possible reasons for this other than: 1. Intentional action by member 2. Intentional action by administrator 3. Bounce removal Check Mailman's subscribe log? The unsubscribes and reasons should be there. Members with stale bounce info can be disabled (or unsubscribed if bounce_you_are_disabled_warnings = 0) if bounce_score_threshold is lowered to a value = the member's stale bounce score. I suppose you could add to your list 'intentional action by a third party who somehow compromised user passwords, the list admin password or the site password or found an unknown security hole'. I don't think this is likely, particularly the security hole. -- 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
