[Mailman-Users] how to change the List-ID (RFC2919)
hi all. after moving a mailinglist from one domain to another, i was wondering how i can keep the old List-ID (according to RFC2919 the List-ID (or the address-part therein) should not change, even if the list-address changes) i have found an open bug-report regarding this: https://bugs.launchpad.net/mailman/+bug/266142 but no solution. is there one? preferrably without having to hack the sources :-) fgmasdr IOhannes -- IEM - network operation center mailto:n...@iem.at -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] how to change the List-ID (RFC2919)
IEM - network operating center (IOhannes m zmoelnig) wrote: after moving a mailinglist from one domain to another, i was wondering how i can keep the old List-ID (according to RFC2919 the List-ID (or the address-part therein) should not change, even if the list-address changes) Correct. It SHOULD not change, but it MAY. It is not desirable, but it is permissible. i have found an open bug-report regarding this: https://bugs.launchpad.net/mailman/+bug/266142 but no solution. is there one? preferrably without having to hack the sources :-) The only solution that doesn't involve hacking code is to not change the host_name of the list, but since the host_name is the domain that is exposed in all list email addresses, that is clearly not a practical solution. Otherwise, you'd need to modify Mailman/Handlers/CookHeaders.py in some way. -- Mark Sapiro m...@msapiro.netThe 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] how to change the List-ID (RFC2919)
Mark Sapiro wrote: The only solution that doesn't involve hacking code is to not change the host_name of the list, but since the host_name is the domain that is exposed in all list email addresses, that is clearly not a practical solution. are there any plans to allow an administrator to set the List-ID in future versions of Mailman? i would love to see that. (that is, it would be sufficient for me to be able to set the listid (address) part of it) Otherwise, you'd need to modify Mailman/Handlers/CookHeaders.py in some way. this is a somewhat unpractical, esp. since (i guess) many people install mailman via a package-manager and want to stay up-to-date with respect to bug-fixes,...; hacking the (pre-packaged) code is always a nightmare in such situations however, iirc there was a custom hook support(?) mfga,.sdr IOhannes -- IEM - network operation center mailto:n...@iem.at -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] how to change the List-ID (RFC2919)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mar 2, 2009, at 11:17 AM, IEM - network operating center (IOhannes m zmoelnig) wrote: are there any plans to allow an administrator to set the List-ID in future versions of Mailman? It's not out of the realm of possibility for MM3. It seems to me on the order of browser ID hacking. Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iEYEARECAAYFAkmsBy0ACgkQ2YZpQepbvXFccQCfWixGfFKUihXe9z2egv8IWk3S aVYAn2OPwlOqL9U+lM1srZhrSPZDmUbQ =QjKt -END PGP SIGNATURE- -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] Uncaught runner exception: unknown encoding: us-ascii
Please help! Since upgrading to Mailman 2.1.12 and Python 2.6.1, my error log is filling up with messages like this and virtually no messages are moving through my mailing lists. Based on a search of the archives, I removed ALL digest.mbox files and ran unshunt. No messages moved and the errors continue. Mar 02 09:51:11 2009 (30278) SHUNTING: 1236010837.317246+dbe24d8d98f7ad6b16fdd98b1f18ae69b6a225e7 Mar 02 09:51:11 2009 (30278) Uncaught runner exception: unknown encoding: us-ascii Mar 02 09:51:11 2009 (30278) Traceback (most recent call last): File /var/mailman/Mailman/Queue/Runner.py, line 120, in _oneloop self._onefile(msg, msgdata) File /var/mailman/Mailman/Queue/Runner.py, line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /var/mailman/Mailman/Queue/IncomingRunner.py, line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File /var/mailman/Mailman/Queue/IncomingRunner.py, line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File /var/mailman/Mailman/Handlers/SpamDetect.py, line 111, in process g.flatten(p) File /usr/lib/python2.5/email/generator.py, line 84, in flatten File /usr/lib/python2.5/email/generator.py, line 116, in _write File /var/mailman/Mailman/Handlers/SpamDetect.py, line 84, in _write_headers Generator._write_headers(self, msg) File /usr/lib/python2.5/email/generator.py, line 150, in _write_headers File /usr/lib/python2.5/email/generator.py, line 26, in _is8bitstring LookupError: unknown encoding: us-ascii -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Uncaught runner exception: unknown encoding:us-ascii
rp...@kinfolk.org wrote: Please help! Since upgrading to Mailman 2.1.12 and Python 2.6.1, my error log is filling up with messages like this and virtually no messages are moving through my mailing lists. Based on a search of the archives, I removed ALL digest.mbox files and ran unshunt. No messages moved and the errors continue. Mar 02 09:51:11 2009 (30278) SHUNTING: 1236010837.317246+dbe24d8d98f7ad6b16fdd98b1f18ae69b6a225e7 Mar 02 09:51:11 2009 (30278) Uncaught runner exception: unknown encoding: us-ascii Mar 02 09:51:11 2009 (30278) Traceback (most recent call last): File /var/mailman/Mailman/Queue/Runner.py, line 120, in _oneloop self._onefile(msg, msgdata) File /var/mailman/Mailman/Queue/Runner.py, line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /var/mailman/Mailman/Queue/IncomingRunner.py, line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File /var/mailman/Mailman/Queue/IncomingRunner.py, line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File /var/mailman/Mailman/Handlers/SpamDetect.py, line 111, in process g.flatten(p) File /usr/lib/python2.5/email/generator.py, line 84, in flatten File /usr/lib/python2.5/email/generator.py, line 116, in _write File /var/mailman/Mailman/Handlers/SpamDetect.py, line 84, in _write_headers Generator._write_headers(self, msg) File /usr/lib/python2.5/email/generator.py, line 150, in _write_headers File /usr/lib/python2.5/email/generator.py, line 26, in _is8bitstring LookupError: unknown encoding: us-ascii You say you have Python 2.6.1, but your Python email library seems to be python2.5. Did you upgrade Python after installing Mailman? It appears your installation may not be completely consistent. What Python version is invoked by a python command. You may need to rerun Mailman's configure and make install. -- Mark Sapiro m...@msapiro.netThe 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Displaying Entire Membership List
Hi Mark, What Mailman version is this... Not sure as it is supplied by my host at hostgo.com You aren't by chance seeing only the 152 As (or whatever's first) ... AHH! That was exactly the problem. So there really was no problem, just cockpit error. Thanks a bunch. Ed Corcoran -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] Mailman not sending email or posting to archive.
Mailman is currently not sending email and not posting to the archives. We moved the server, that hosts the mailman application, to a new network. This required that our email relay server also be changed. I am wondering if there is something in the mailman config that needs to be updated. I sent a test email directly from the server and that was successful, but if I try to post to the list I get nothing. Thanks. PATI MOSS System Engineer Sr. Professional CSC This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. Patricia A Moss/GIS/CSC 01/30/2009 09:46 AM To mailman-users@python.org cc Subject Domainname changing I am running mailman 2.1.5 on a RedHat Linux, version 4.0, server. The IP Address and domainname, of the server, are going to change and I wanted to know is there was a script or set of instructions for making similar changes within mailman. I see that the archives will be affected by the domainname. I am not sure as to what else may be affected and how to avoid a problem. I found this article 3.4. How do I move a list to a different server/Mailman installation. in the FAQ. It seems like it pertains to my situation, but I wanted to make sure that I didn't miss anything else. Thanks. PATI MOSS System Engineer Sr. Professional CSC This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] password sends
Mark Sapiro wrote at 05:49 PM 2/28/2009: What is supposed to happen when a non-listmember tries to get a password reminder from the member options page? I tried it myself after trying to figure out if a member was using the wrong email address, and the web page said, A reminder of your password has been emailed to you. The issue is your list's membership is not public, so we can't reveal that the person requesting the reminder is not a member or this could be used to fish for list membership. Granted the message should be better (i.e. more ambiguous about whether the reminder is actually sent), but the bottom line is if the address is a non-member, no reminder is sent. Thanks, Mark. I hope the message can change in some future version. I also discovered that one of my four lists doesn't even send out the passwords to subscribed members after saying the reminders were sent. I tried this on my own subscribed name and it failed. If folks can tell me what might be wrong here as well, I will pass it on to DreamHost tech support which has been quite responsive in the past. Reminders are supposed to work for subscribed members. I don't know why they wouldn't. As a debug technique, you could temporarily set I hit up DreamHost support on this, and they said they changed a setting, and that if it still did not work I would need to give them temporary Admin access to the list so they could check on things. I tried a reminder, and they still were not working. I went to the Admin pages and reviewed carefully all the settings (again), and discovered that umbrella_list was set to Yes. I set it to No, and the reminders began working. I suppose that setting could have been at Yes all along, but I didn't think so. - - - - - - - - - - - - Michael Welch, volunteer Redwood Alliance PO Box 293 Arcata, CA 95518 707-822-7884 mwe...@redwoodalliance.org www.redwoodalliance.org -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] how to change the List-ID (RFC2919)
Barry Warsaw writes: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mar 2, 2009, at 11:17 AM, IEM - network operating center (IOhannes m zmoelnig) wrote: are there any plans to allow an administrator to set the List-ID in future versions of Mailman? It's not out of the realm of possibility for MM3. It seems to me on the order of browser ID hacking. ? Isn't it as simple as adding a rfc2919-list-id attribute to the list object, and defaulting it to what we compute for it today? -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] password sends
Michael Welch wrote: Mark Sapiro wrote at 05:49 PM 2/28/2009: The issue is your list's membership is not public, so we can't reveal that the person requesting the reminder is not a member or this could be used to fish for list membership. Granted the message should be better (i.e. more ambiguous about whether the reminder is actually sent), but the bottom line is if the address is a non-member, no reminder is sent. Thanks, Mark. I hope the message can change in some future version. It will change in 2.2 I went to the Admin pages and reviewed carefully all the settings (again), and discovered that umbrella_list was set to Yes. I set it to No, and the reminders began working. I suppose that setting could have been at Yes all along, but I didn't think so. It probably was on all along or at least since you noticesd you weren't getting reminders. I forgot about that as a potential issue with reminders. It causes the reminder for u...@example.com to be sent to user-...@example.com (where -xxx is -owner or whatever umbrella_member_suffix is set to). How that gets delivered or whether it gets delivered at all depends on the specific MTA/MDA configuration for u...@example.com. -- Mark Sapiro m...@msapiro.netThe 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] how to change the List-ID (RFC2919)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mar 2, 2009, at 12:28 PM, Stephen J. Turnbull wrote: It's not out of the realm of possibility for MM3. It seems to me on the order of browser ID hacking. ? Isn't it as simple as adding a rfc2919-list-id attribute to the list object, and defaulting it to what we compute for it today? Yep, and exposing it in the u/i. What I meant was, it kind of feels like masquerading. Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iEYEARECAAYFAkmsGOoACgkQ2YZpQepbvXHZnACfcsCBR7lJ8XALVaz02vUN9lTL 33sAoISpjSiD7Sz9Zvl0ni+km5H5k4DE =a+ps -END PGP SIGNATURE- -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman not sending email or posting to archive.
Patricia A Moss wrote: Mailman is currently not sending email and not posting to the archives. We moved the server, that hosts the mailman application, to a new network. This required that our email relay server also be changed. I am wondering if there is something in the mailman config that needs to be updated. I can't say without knowing more specifics about exactly how mail used to be delivered to Mailman and how it is now (or at least is supposed to be, since it seems like posts aren't getting to Mailman at all. I sent a test email directly from the server and that was successful, You mean you sent an outgoing mail from the server or you sent a post to a list from the server? but if I try to post to the list I get nothing. Thanks. What happens to that mail? What do the logs for each MTA it passes through say about it? -- Mark Sapiro m...@msapiro.netThe 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Uncaught runner exception: unknown encoding:us-ascii
On 2 Mar 2009 at 9:10, Mark Sapiro wrote: rp...@kinfolk.org wrote: Please help! Since upgrading to Mailman 2.1.12 and Python 2.6.1, my error log is filling up with messages like this and virtually no messages are moving through my mailing lists. Based on a search of the archives, I removed ALL digest.mbox files and ran unshunt. No messages moved and the errors continue. Mar 02 09:51:11 2009 (30278) SHUNTING: 1236010837.317246+dbe24d8d98f7ad6b16fdd98b1f18ae69b6a225e7 Mar 02 09:51:11 2009 (30278) Uncaught runner exception: unknown encoding: us-ascii Mar 02 09:51:11 2009 (30278) Traceback (most recent call last): File /var/mailman/Mailman/Queue/Runner.py, line 120, in _oneloop self._onefile(msg, msgdata) File /var/mailman/Mailman/Queue/Runner.py, line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /var/mailman/Mailman/Queue/IncomingRunner.py, line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File /var/mailman/Mailman/Queue/IncomingRunner.py, line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File /var/mailman/Mailman/Handlers/SpamDetect.py, line 111, in process g.flatten(p) File /usr/lib/python2.5/email/generator.py, line 84, in flatten File /usr/lib/python2.5/email/generator.py, line 116, in _write File /var/mailman/Mailman/Handlers/SpamDetect.py, line 84, in _write_headers Generator._write_headers(self, msg) File /usr/lib/python2.5/email/generator.py, line 150, in _write_headers File /usr/lib/python2.5/email/generator.py, line 26, in _is8bitstring LookupError: unknown encoding: us-ascii You say you have Python 2.6.1, but your Python email library seems to be python2.5. Did you upgrade Python after installing Mailman? It appears your installation may not be completely consistent. What Python version is invoked by a python command. You may need to rerun Mailman's configure and make install. # python Python 2.6.1 (r261:67515, Feb 28 2009, 15:18:21) [GCC 4.2.4] on linux2 Type help, copyright, credits or license for more information. I re-ran the configure and install of mailman, ran unshunt and the errors still show using python 2.5: Mar 02 10:39:45 2009 (30280) SHUNTING: 1236015583.0520451+8058beae403d3fbac5f2571929549c19e2125acd Mar 02 10:39:53 2009 (30278) Uncaught runner exception: unknown encoding: us-ascii Mar 02 10:39:53 2009 (30278) Traceback (most recent call last): File /var/mailman/Mailman/Queue/Runner.py, line 120, in _oneloop self._onefile(msg, msgdata) File /var/mailman/Mailman/Queue/Runner.py, line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /var/mailman/Mailman/Queue/IncomingRunner.py, line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File /var/mailman/Mailman/Queue/IncomingRunner.py, line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File /var/mailman/Mailman/Handlers/SpamDetect.py, line 111, in process g.flatten(p) File /usr/lib/python2.5/email/generator.py, line 84, in flatten File /usr/lib/python2.5/email/generator.py, line 109, in _write File /usr/lib/python2.5/email/generator.py, line 135, in _dispatch File /usr/lib/python2.5/email/generator.py, line 201, in _handle_multipart File /usr/lib/python2.5/email/generator.py, line 84, in flatten File /usr/lib/python2.5/email/generator.py, line 116, in _write File /var/mailman/Mailman/Handlers/SpamDetect.py, line 84, in _write_headers Generator._write_headers(self, msg) File /usr/lib/python2.5/email/generator.py, line 150, in _write_headers File /usr/lib/python2.5/email/generator.py, line 26, in _is8bitstring LookupError: unknown encoding: us-ascii Mar 02 10:39:54 2009 (30278) SHUNTING: 1236014500.0552149+8a7b01ddc869ad3d723ffcadca4644d72858e68b Mar 02 10:39:54 2009 (30278) Failed to unlink/preserve backup file: /var/mailman/qfiles/in/1236014500.0552149+5aed32c1bfbe6e4ac85c02c35185 46e179e37b02.bak -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] No incoming mail
I have a system that I just set up and mail, such as subscribe notifications and list creations are going out but mail isn't making it in. I get a server is down error reply. Although postfix is up, where might the catch be? Thanks for any ideas or suggestions, Tim Tim Ferguson Director of Technology Centralia City Schools Centralia, Illinois 62801 618-532-1907, Ext. 1030 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Uncaught runner exception: unknownencoding:us-ascii
rp...@kinfolk.org wrote: # python Python 2.6.1 (r261:67515, Feb 28 2009, 15:18:21) [GCC 4.2.4] on linux2 Type help, copyright, credits or license for more information. I re-ran the configure and install of mailman, ran unshunt and the errors still show using python 2.5: What does config.log show for your configure command line and for things like the following: configure:1714: checking for --with-python configure:1726: result: no configure:1733: checking for python configure:1751: found /usr/bin/python configure:1764: result: /usr/bin/python configure:1774: checking Python interpreter configure:1792: result: /usr/bin/python configure:1796: checking Python version configure:1829: result: 2.6.1 configure:1833: checking Python's email package configure:1866: result: ok (the first several lines after ## --- ## ## Core tests. ## ## --- ## Mar 02 10:39:45 2009 (30280) SHUNTING: 1236015583.0520451+8058beae403d3fbac5f2571929549c19e2125acd Mar 02 10:39:53 2009 (30278) Uncaught runner exception: unknown encoding: us-ascii Mar 02 10:39:53 2009 (30278) Traceback (most recent call last): File /var/mailman/Mailman/Queue/Runner.py, line 120, in _oneloop self._onefile(msg, msgdata) File /var/mailman/Mailman/Queue/Runner.py, line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /var/mailman/Mailman/Queue/IncomingRunner.py, line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File /var/mailman/Mailman/Queue/IncomingRunner.py, line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File /var/mailman/Mailman/Handlers/SpamDetect.py, line 111, in process g.flatten(p) File /usr/lib/python2.5/email/generator.py, line 84, in flatten File /usr/lib/python2.5/email/generator.py, line 109, in _write File /usr/lib/python2.5/email/generator.py, line 135, in _dispatch File /usr/lib/python2.5/email/generator.py, line 201, in _handle_multipart File /usr/lib/python2.5/email/generator.py, line 84, in flatten File /usr/lib/python2.5/email/generator.py, line 116, in _write File /var/mailman/Mailman/Handlers/SpamDetect.py, line 84, in _write_headers Generator._write_headers(self, msg) File /usr/lib/python2.5/email/generator.py, line 150, in _write_headers File /usr/lib/python2.5/email/generator.py, line 26, in _is8bitstring LookupError: unknown encoding: us-ascii Mar 02 10:39:54 2009 (30278) SHUNTING: 1236014500.0552149+8a7b01ddc869ad3d723ffcadca4644d72858e68b Are you also getting many errors like the following? Mar 02 10:39:54 2009 (30278) Failed to unlink/preserve backup file: /var/mailman/qfiles/in/1236014500.0552149+5aed32c1bfbe6e4ac85c02c35185 46e179e37b02.bak -- Mark Sapiro m...@msapiro.netThe 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] No incoming mail
Tim Ferguson wrote: I have a system that I just set up and mail, such as subscribe notifications and list creations are going out but mail isn't making it in. I get a server is down error reply. Although postfix is up, where might the catch be? Where do you see this? Is this in a DSN (bounce notice) returned to you? The catch appears to be somewhere in delivery of mail to Mailman before it actually gets to Mailman. -- Mark Sapiro m...@msapiro.netThe 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Uncaught runner exception: unknownencoding:us-ascii
On 2 Mar 2009 at 10:24, Mark Sapiro wrote: rp...@kinfolk.org wrote: # python Python 2.6.1 (r261:67515, Feb 28 2009, 15:18:21) [GCC 4.2.4] on linux2 Type help, copyright, credits or license for more information. I re-ran the configure and install of mailman, ran unshunt and the errors still show using python 2.5: What does config.log show for your configure command line and for things like the following: configure:1714: checking for --with-python configure:1726: result: no configure:1733: checking for python configure:1751: found /usr/bin/python configure:1764: result: /usr/bin/python configure:1774: checking Python interpreter configure:1792: result: /usr/bin/python configure:1796: checking Python version configure:1829: result: 2.6.1 configure:1833: checking Python's email package configure:1866: result: ok (the first several lines after ## --- ## ## Core tests. ## ## --- ## configure:1714: checking for --with-python configure:1726: result: /usr/bin/python configure:1774: checking Python interpreter configure:1792: result: /usr/bin/python configure:1796: checking Python version configure:1829: result: 2.6.1 configure:1833: checking Python's email package configure:1866: result: ok configure:1872: checking that Python has a working distutils configure:1921: result: yes configure:1969: checking for a BSD-compatible install configure:2025: result: /usr/bin/install -c configure:2036: checking whether make sets $(MAKE) Mar 02 10:39:45 2009 (30280) SHUNTING: 1236015583.0520451+8058beae403d3fbac5f2571929549c19e2125acd Mar 02 10:39:53 2009 (30278) Uncaught runner exception: unknown encoding: us-ascii Mar 02 10:39:53 2009 (30278) Traceback (most recent call last): File /var/mailman/Mailman/Queue/Runner.py, line 120, in _oneloop self._onefile(msg, msgdata) File /var/mailman/Mailman/Queue/Runner.py, line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /var/mailman/Mailman/Queue/IncomingRunner.py, line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File /var/mailman/Mailman/Queue/IncomingRunner.py, line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File /var/mailman/Mailman/Handlers/SpamDetect.py, line 111, in process g.flatten(p) File /usr/lib/python2.5/email/generator.py, line 84, in flatten File /usr/lib/python2.5/email/generator.py, line 109, in _write File /usr/lib/python2.5/email/generator.py, line 135, in _dispatch File /usr/lib/python2.5/email/generator.py, line 201, in _handle_multipart File /usr/lib/python2.5/email/generator.py, line 84, in flatten File /usr/lib/python2.5/email/generator.py, line 116, in _write File /var/mailman/Mailman/Handlers/SpamDetect.py, line 84, in _write_headers Generator._write_headers(self, msg) File /usr/lib/python2.5/email/generator.py, line 150, in _write_headers File /usr/lib/python2.5/email/generator.py, line 26, in _is8bitstring LookupError: unknown encoding: us-ascii Mar 02 10:39:54 2009 (30278) SHUNTING: 1236014500.0552149+8a7b01ddc869ad3d723ffcadca4644d72858e68b Are you also getting many errors like the following? Mar 02 10:39:54 2009 (30278) Failed to unlink/preserve backup file: /var/mailman/qfiles/in/1236014500.0552149+5aed32c1bfbe6e4ac85c02c3518 5 46e179e37b02.bak Yes: Mar 02 11:23:49 2009 (13849) Skipping and preserving unparseable message: 1236014500.0552149+80fb5a8a97a8d0c248a1d845d2d05094c2a5fa49 Mar 02 11:23:49 2009 (13849) Failed to unlink/preserve backup file: /var/mailman/qfiles/out/1236014500.0552149+80fb5a8a97a8d0c248a1d845d2d 05094c2a5fa49.bak Since the only thing on the server that is (intentionally) using Python, I deleted the /lib/python2.5 and /usr/lib/python2.5 directories and have reinstalled Python, reinstalled Mailman and rebooted the server. It appears to have cleared things up as I ran unshunt and now all of the qfiles except bad are empty and several previously shunted emails are delivering. Thanks. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Uncaught runner exception: unknownencoding:us-ascii
rp...@kinfolk.org wrote: On 2 Mar 2009 at 10:24, Mark Sapiro wrote: Are you also getting many errors like the following? Mar 02 10:39:54 2009 (30278) Failed to unlink/preserve backup file: /var/mailman/qfiles/in/1236014500.0552149+5aed32c1bfbe6e4ac85c02c3518 5 46e179e37b02.bak Yes: Mar 02 11:23:49 2009 (13849) Skipping and preserving unparseable message: 1236014500.0552149+80fb5a8a97a8d0c248a1d845d2d05094c2a5fa49 Mar 02 11:23:49 2009 (13849) Failed to unlink/preserve backup file: /var/mailman/qfiles/out/1236014500.0552149+80fb5a8a97a8d0c248a1d845d2d 05094c2a5fa49.bak Unfortunately, I neglected to put the actual error in the above log message - one more thing for 2.2 :) This seems to say there is an error in trying to move the .bak backup queue entry for the unparseable message to a .psv entry in the qfiles/bad queue. I don't know why. Since the only thing on the server that is (intentionally) using Python, I deleted the /lib/python2.5 and /usr/lib/python2.5 directories and have reinstalled Python, reinstalled Mailman and rebooted the server. It appears to have cleared things up as I ran unshunt and now all of the qfiles except bad are empty and several previously shunted emails are delivering. Well, perhaps we'll never understand fully what the issues were, but I'm glad it's OK now. Those .psv files in qfiles/bad are the unparseable messages. Almost certainly, they are spam in a malformed MIME message. if you're curious, you can examine them with 'bin/dumpdb -p'. With default settings, they will be discarded by cron/cull_bad_shunt after 7 days. -- Mark Sapiro m...@msapiro.netThe 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Tricky admin_immed_notify problem
Jim Savoy wrote: Reading this reminded me that I have a similar problem. All of our lists are set by default to be admin_immed_notify=yes, but the list owners only get a message when something new arrives (that is put on hold). They never get a daily reminder about the queued-up stuff. Is this a known problem for v2.1.5 (we will be upgrading to v2.1.12 this summer). I have no idea how long this has been going on, and only remembered it because I own one of the lists and realized that I only get the one warning. Mark Shapiro wrote: The daily summary is sent by cron/checkdbs. Does mailman have a crontab? Does it have an entry to run cron/checkdbs daily? Is crond running? Hi Mark, The answers to your questions are: yes, yes yes. But I don't think the person who installed Mailman many years ago ever did the crontab -u mailman crontab.in bit, so I just did it now. First I commented out everything in that crontab.in file except the checkdbs line, and set that to run immediately. It worked like a charm and sent out hundreds of reminders to all list owners. I am not all that familiar with cron. Is that crontab -u mailman crontab.in something you need to run every time you reboot the system? Or does it add something to /etc/cron.d or /etc/cron.daily or /etc/crontab? (I don't see anything new in those). But I noticed that many of the reminders it sent out, pointing people to the admindb page were blank (ie there is nothing pending). So I'm not sure what that means. There aren't that many .pck files in /mailman/data and I am not sure where else it is pulling that false information from. The next run is set for 8:00 am tomorrow, but I might have to put it on hold until I find out why there are so many bogus warnings going out. If someone was to clear out a bunch of pending requests from the mailman/data directory just by deleting them, instead of doing it properly with the admindb web interface, would that cause this problem? If so, can I remedy this somehow? Any pointers would be helpful. I don't fully understand all of the workings of Mailman (like many of the others on this list - I just sort of babysit it and we've never had too many problems). Thanks! -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Tricky admin_immed_notify problem
Jim Savoy wrote: I am not all that familiar with cron. Is that crontab -u mailman crontab.in something you need to run every time you reboot the system? Or does it add something to /etc/cron.d or /etc/cron.daily or /etc/crontab? (I don't see anything new in those). Jim Savoy answers himself: Before I get blasted with RTFMs, I did just read the manpage for crontab, and it says that each user may maintain their own separate crontabs, so I have now deduced that the command I ran activated that. I am still not sure if I am supposed to run that every time we reboot or if it's permanent (and if I change crontab.in (to comment out tomorrow's 8:00 am run, for instance) do I have to execute that command again?). Thanks. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Tricky admin_immed_notify problem
I think I have my phantom requests (eg the -1 request(s) pending) question answered. Googling it I see that Mark provided a fix, but also said that by going to that admin page once should clear it. That may save me from manually having to fix hundreds of lists. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Tricky admin_immed_notify problem
Savoy, Jim wrote: The answers to your questions are: yes, yes yes. But I don't think the person who installed Mailman many years ago ever did the crontab -u mailman crontab.in bit, so I just did it now. First I commented out everything in that crontab.in file except the checkdbs line, and set that to run immediately. It worked like a charm and sent out hundreds of reminders to all list owners. I am not all that familiar with cron. Is that crontab -u mailman crontab.in something you need to run every time you reboot the system? Or does it add something to /etc/cron.d or /etc/cron.daily or /etc/crontab? (I don't see anything new in those). As you discovered it puts the commands from crontab.in into the mailman user's crontab which is likely /var/spool/cron/mailman. It stays there across boots. This is the correct place for the mailman crontab. The ones in cron.d are a slightly different format. But note, that almost all the jobs in crontab.in should be run. They all have a function and the only one you can safely ignore is gate_news if you aren't running any lists with a news-mail gateway. For the others, you need to at least read the comments in crontab.in and understand what the job does before deciding not to run it. But I noticed that many of the reminders it sent out, pointing people to the admindb page were blank (ie there is nothing pending). Presumably these are the -1 requests ones you refer to later. This issue only existed with lists that were migrated from pre 2.1.5 to 2.1.5 and only exists in 2.1.5. Yes, visiting the list's admindb page should fix it, but that needs to be done for each list with the problem. I have just created a withlist script you can run to fix all the problem lists. See http://www.msapiro.net/scripts/fix_minus_one.py. -- Mark Sapiro m...@msapiro.netThe 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] how to change the List-ID (RFC2919)
Barry Warsaw writes: On Mar 2, 2009, at 12:28 PM, Stephen J. Turnbull wrote: It's not out of the realm of possibility for MM3. It seems to me on the order of browser ID hacking. ? Isn't it as simple as adding a rfc2919-list-id attribute to the list object, and defaulting it to what we compute for it today? Yep, and exposing it in the u/i. What I meant was, it kind of feels like masquerading. I disagree. The identity of a list is what it is, and shouldn't change because the server changes. The issue here arises because in Mailman 2.1, lists have no sense of their own identitywink, and rely on their association with a server to derive an identity. So by providing this feature we're not hiding ID to placate the outside world, we're *exposing* ID to improve reliability. While Mark is correct that the RFC says SHOULD, and so it's optional if tools like Mailman find the implementation painful, I would say this is a MUST for MM3, and deserves consideration as a SHOULD for MM2.2. It's not obvious that it even needs be exposed in the UI for MM2. Moving servers is something that requires intervention by somebody with root access, so command-line configuration is sufficient for MM2, I think. AFAIK there are no tools out there that depend on continuity of List-Id (except user filters, and even those may continue to work by and large if they match on the mailbox rather than the full ID), so I wouldn't call it urgent, even for MM3. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] how to change the List-ID (RFC2919)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mar 2, 2009, at 9:23 PM, Stephen J. Turnbull wrote: I disagree. The identity of a list is what it is, and shouldn't change because the server changes. The issue here arises because in Mailman 2.1, lists have no sense of their own identitywink, and rely on their association with a server to derive an identity. So by providing this feature we're not hiding ID to placate the outside world, we're *exposing* ID to improve reliability. While Mark is correct that the RFC says SHOULD, and so it's optional if tools like Mailman find the implementation painful, I would say this is a MUST for MM3, and deserves consideration as a SHOULD for MM2.2. It's not obvious that it even needs be exposed in the UI for MM2. Moving servers is something that requires intervention by somebody with root access, so command-line configuration is sufficient for MM2, I think. AFAIK there are no tools out there that depend on continuity of List-Id (except user filters, and even those may continue to work by and large if they match on the mailbox rather than the full ID), so I wouldn't call it urgent, even for MM3. What I'm saying is that the RFC states While it is perfectly acceptable for a list identifier to be completely independent of the domain name of the host machine servicing the mailing list, the owner of a mailing list MUST NOT generate list identifiers in any domain namespace for which they do not have authority. So, if you're moving a list from one domain to another, and you want to keep your old List-ID, you must still control the old domain. If not, then ISTM you MUST change the List-ID. In certain environments, I think you can trust the list admins to get this right, but in others you might trust only the site administrators. So how much control do you give to list admins? The core question is whether /someone/ should be able to (easily) set the List-ID, and I think we agree the answer to that is yes. You state that command-line configuration would be fine for MM2, and I agree with that too. :) I still think the posting address makes for a fine default value (well, s/@/./ of course). Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iEYEARECAAYFAkmstKQACgkQ2YZpQepbvXHqywCeNXpqA/gFjFnPMyIUbr8ndMJ9 a3gAn2DxEwPge+X6+r/ZI200f/y6GUoq =ZceU -END PGP SIGNATURE- -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
