tag:www.nabble.com,2006:forum-1728Nabble - Mailman2009-01-08T15:30:46ZMailman is free software for managing electronic mail discussion and e-newsletter lists. Mailman is integrated with the web, making it easy for users to manage their accounts and for list owners to administer their lists. Mailman supports built-in archiving, automatic bounce processing, content filtering, digest delivery, spam filters, and more. Mailman home is <a href="http://www.gnu.org/software/mailman/" target="_top" rel="nofollow">here</a>.tag:www.nabble.com,2006:post-21363381Re: Unknown encoding error2009-01-08T15:30:46Z2009-01-08T15:30:46ZMark Sapiro-3Khosrow Ebrahimpour wrote:
<br>>
<br>>A more general question. Has this issue been fixed in subsequent releases of
<br>>mailman? We are running 2.1.5 on Sarge at the moment. I suspect that we will
<br>>be seeing this error occasionally, although I'm surprised it hasn't been an
<br>>issue so far.
<br><br><br>Yes. The problem of unanticipated exceptions in digest processing
<br>stopping a list was fixed in 2.1.7.
<br><br>The problem of apostrophes in RFC 2231 encoded parameters was fixed in
<br>the underlying Python email library. I don't remember exactly when,
<br>but I'm pretty sure it was fixed in email 2.5.8 which has shipped with
<br>Mailman starting with 2.1.9.
<br><br>--
<br>Mark Sapiro <<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21363381&i=0" target="_top" rel="nofollow">mark@...</a>> The highway is for gamblers,
<br>San Francisco Bay Area, California better use your sense - B. Dylan
<br><br>------------------------------------------------------
<br>Mailman-Users mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21363381&i=1" target="_top" rel="nofollow">Mailman-Users@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-users" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-users</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-users%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-users%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Users-f1729.html" embed="fixTarget[1729]" target="_top" >Mailman - Users</a></p>tag:www.nabble.com,2006:post-21368103Re: Unknown encoding error2009-01-08T14:23:38Z2009-01-08T14:23:38ZKhosrow EbrahimpourOn 6 January 2009 11:36, Mark Sapiro wrote:
<br><br>> You need to edit the lists/LISTNAME/digest.mbox. You can edit it by hand
<br>> or with an MUA like mutt for example.
<br>>
<br>Thank you Mark. That solution worked perfectly. I modified the digest.mbox and
<br>changed only the offending attachment content-types. After running "unshunt"
<br>everything behaved nicely.
<br><br>A more general question. Has this issue been fixed in subsequent releases of
<br>mailman? We are running 2.1.5 on Sarge at the moment. I suspect that we will
<br>be seeing this error occasionally, although I'm surprised it hasn't been an
<br>issue so far.
<br><br>Cheers,
<br>Khosrow
<br>------------------------------------------------------
<br>Mailman-Users mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21368103&i=0" target="_top" rel="nofollow">Mailman-Users@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-users" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-users</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-users%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-users%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Users-f1729.html" embed="fixTarget[1729]" target="_top" >Mailman - Users</a></p>tag:www.nabble.com,2006:post-21361230Re: mailman-pgp-smime: talks at FOSDEM and in Ulm, new release2009-01-08T13:22:38Z2009-01-08T13:22:38ZBarry Warsaw-3-----BEGIN PGP SIGNED MESSAGE-----
<br>Hash: SHA1
<br><br>On Jan 7, 2009, at 12:20 PM, Joost van Baal wrote:
<br><div class='shrinkable-quote'><br>> Thanks to the NLnet foundation, the Secure List Server project (
<br>> <a href="http://non-gnu.uvt.nl/mailman-pgp-smime/" target="_top" rel="nofollow">http://non-gnu.uvt.nl/mailman-pgp-smime/</a> ) , which is including
<br>> OpenPGP and
<br>> S/MIME support in Mailman has released a much improved mailman-pgp-
<br>> smime patch:
<br>> <a href="http://non-gnu.uvt.nl/pub/mailman/mailman-2.1.11-pgp-smime_2009-01-02.patch.gz" target="_top" rel="nofollow">http://non-gnu.uvt.nl/pub/mailman/mailman-2.1.11-pgp-smime_2009-01-02.patch.gz</a><br>> . See <a href="http://non-gnu.uvt.nl/mailman-pgp-smime/NEWS.PGP-SMIME" target="_top" rel="nofollow">http://non-gnu.uvt.nl/mailman-pgp-smime/NEWS.PGP-SMIME</a> for
<br>> the details.
<br>>
<br>> There'll be talks about this patch:
<br>>
<br>> On monday january 12 I'll talk at the Chaos Seminar</a> in Ulm,
<br>> Germany,
<br>> see <a href="http://ulm.ccc.de/ChaosSeminar/2009/01_Mailman_PGP_SMIME" target="_top" rel="nofollow">http://ulm.ccc.de/ChaosSeminar/2009/01_Mailman_PGP_SMIME</a> .
<br>>
<br>> On sunday february 8th, 10h20 (probably), I'll give a lightning talk
<br>> at the
<br>> FOSDEM conference, ULB Campus Solbosch, Brussels, Belgium. See
<br>> <a href="http://fosdem.org/2009/node/164" target="_top" rel="nofollow">http://fosdem.org/2009/node/164</a>.
<br>>
<br>> The talk will start with a very short overview of the history of
<br>> Mailman and
<br>> the mailman-pgp-smime project. Some remarks will be made on how to
<br>> install and
<br>> configure the software, so that one can try it. Currently supported
<br>> features
<br>> will be mentioned, as well as an overview of development plans. One
<br>> will learn
<br>> how to contribute to the project; an overview of the revision
<br>> control system
<br>> used will be given. Some remarks on the future of the patch will be
<br>> made: will
<br>> it be shipped with Mailman itself?
<br>>
<br>> If you have used Mailman, both as a subscriber and as a list admin,
<br>> and if
<br>> you know what PGP and S/MIME are, you should definitely attend this
<br>> talk.
<br>>
<br>> Hope to meet you there!
</div><br>Very cool! I wish I could be there.
<br><br>I'm very interested in seeing how we could incorporate this work into
<br>Mailman 3, either as a core piece, or as an easy to install, use, and
<br>develop plugin.
<br><br>Barry
<br><br>-----BEGIN PGP SIGNATURE-----
<br>Version: GnuPG v1.4.9 (Darwin)
<br><br>iEYEARECAAYFAklmbp4ACgkQ2YZpQepbvXEoyACfcWJiLO0ekeYov7LUOKqZ7S3R
<br>lUoAoI/tNURbL6TDmzJ30QC044y2xM3R
<br>=cpel
<br>-----END PGP SIGNATURE-----
<br>_______________________________________________
<br>Mailman-Developers mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21361230&i=0" target="_top" rel="nofollow">Mailman-Developers@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-developers" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-developers</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-developers%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-developers%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Dev-f1731.html" embed="fixTarget[1731]" target="_top" >Mailman - Dev</a></p>tag:www.nabble.com,2006:post-21360638Re: Customizing the admin login page...2009-01-08T12:42:17Z2009-01-08T12:42:17ZGrant Taylor-2On 01/08/09 14:16, Mark Sapiro wrote:
<br>> The admlogin.html template. And if you're going to do it, you may also
<br>> want to do the private.html template for private archive login.
<br><br>Thank you. That did the trick.
<br><br>> See the FAQ at <<a href="http://wiki.list.org/x/jYA9" target="_top" rel="nofollow">http://wiki.list.org/x/jYA9</a>> for information on the
<br>> proper places to put edited versions of these templates so they won't
<br>> be overwritten in an upgrade.
<br><br>*nod*
<br><br>Pursuant to that advice, I copied templates/en/admlogin.html to
<br>templates/site/en/admlogin.html and made the following changes. Note, I
<br>did not previously have the site specific files, do not make the copy if
<br>you already have custom files or you will loose your customizations.
<br>Don't forget to make sure that Mailman has permissions to the custom
<br>files and the directories they are in.
<br><br> - Added a the following onLoad to the page's BODY tag.
<br><br> onLoad="document.LoginForm.adminpw.focus()"
<br><br> - Added the following name to the page's FORM tag.
<br><br> NAME="LoginForm"
<br><br>Thus when the page load, it executes the onLoad JavaScript statement and
<br>sets the focus on the password input box. :)
<br><br><br><br>Grant. . . .
<br><br><br>P.S. Tip of the hat for the way that Mailman has split up the locations
<br>that you can make customizations.
<br>------------------------------------------------------
<br>Mailman-Users mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21360638&i=0" target="_top" rel="nofollow">Mailman-Users@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-users" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-users</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-users%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-users%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Users-f1729.html" embed="fixTarget[1729]" target="_top" >Mailman - Users</a></p>tag:www.nabble.com,2006:post-21360071Re: Customizing the admin login page...2009-01-08T12:16:46Z2009-01-08T12:16:46ZMark Sapiro-3Grant Taylor wrote:
<br><br>>What file(s) would I need to edit if I wanted to customize the admin
<br>>login page?
<br>>
<br>>I'm wanting to add an onLoad value to the BODY tag (and related name tag
<br>>to the form) to the web page that is generated to automatically focus
<br>>the password box so that I can go to the web page and enter the password
<br>>with out touching the mouse (or tabbing).
<br><br><br>The admlogin.html template. And if you're going to do it, you may also
<br>want to do the private.html template for private archive login.
<br><br>See the FAQ at <<a href="http://wiki.list.org/x/jYA9" target="_top" rel="nofollow">http://wiki.list.org/x/jYA9</a>> for information on the
<br>proper places to put edited versions of these templates so they won't
<br>be overwritten in an upgrade.
<br><br>--
<br>Mark Sapiro <<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21360071&i=0" target="_top" rel="nofollow">mark@...</a>> The highway is for gamblers,
<br>San Francisco Bay Area, California better use your sense - B. Dylan
<br><br>------------------------------------------------------
<br>Mailman-Users mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21360071&i=1" target="_top" rel="nofollow">Mailman-Users@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-users" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-users</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-users%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-users%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Users-f1729.html" embed="fixTarget[1729]" target="_top" >Mailman - Users</a></p>tag:www.nabble.com,2006:post-21359899Re: Email subscription not working2009-01-08T12:07:21Z2009-01-08T12:07:21ZMark Sapiro-3Dan Mahoney, System Admin wrote:
<br><div class='shrinkable-quote'><br>>Hey all, I'm hitting a little snag. Email subscribe isn't doing anything.
<br>>
<br>>Postfix delivers the email to mailman, but then as far as I can tell,
<br>>nothing more happens with it.
<br>>
<br>>Where would be the best place to debug this from a mailman perspective?
<br>>
<br>>Jan 7 21:05:34 lister postfix/qmgr[97071]: DDFD010E528:
<br>>from=<<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21359899&i=0" target="_top" rel="nofollow">ionlyhavethisfortesting@...</a>>, size=2716, nrcpt=1 (queue
<br>>active)
<br>>Jan 7 21:05:35 lister postfix/local[38795]: DDFD010E528:
<br>>to=<<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21359899&i=1" target="_top" rel="nofollow">testing-join@...</a>>, relay=local, delay=0.18,
<br>>delays=0.01/0/0/0.17, dsn=2.0.0, status=sent (delivered to command:
<br>>/usr/local/mailman/mail/mailman join testing)
<br>>Jan 7 21:05:35 lister postfix/qmgr[97071]: DDFD010E528: removed
<br>>
<br>>And that's where it stops. The address doesn't show in any logs or
<br>>anything from that point forward.
</div><br><br>The above says Postfix successfully piped the mail to the wrapper which
<br>presumably invoked the 'join' script to queue the mail in the
<br>'commands' queue.
<br><br>>From there it is processed by CommandRunner.
<br><br>Step 1) is CommandRunner running or is the message still sitting in
<br>qfiles/commands ?
<br><br>>Anything obvious I should be checking? Perhaps the possibility that the
<br>>"to" address is getting altered in transit? Does mailman log discarded
<br>>subscription messages? Is there a debug option?
<br><br><br>The message got delivered to the correct address according to Postfix.
<br><br>Messages with precedence 'bulk', 'junk' or 'list' are discarded, but
<br>the discard is logged in Mailman's vette log with a message like
<br><br> Precedence: xxx message discarded by: <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21359899&i=2" target="_top" rel="nofollow">testing-request@...</a>
<br><br>If you have an autoresponder set for requests to this list, the message
<br>will be autoresponded to per the autoresponder settings and logged in
<br>the vette log as "replied and discard".
<br><br>Also look for messages in Mailman's error (and other) logs with
<br>timestamp within a few seconds of Jan 7 21:05:35.
<br><br>--
<br>Mark Sapiro <<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21359899&i=3" target="_top" rel="nofollow">mark@...</a>> The highway is for gamblers,
<br>San Francisco Bay Area, California better use your sense - B. Dylan
<br><br>------------------------------------------------------
<br>Mailman-Users mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21359899&i=4" target="_top" rel="nofollow">Mailman-Users@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-users" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-users</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-users%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-users%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Users-f1729.html" embed="fixTarget[1729]" target="_top" >Mailman - Users</a></p>tag:www.nabble.com,2006:post-21359705Customizing the admin login page...2009-01-08T11:52:36Z2009-01-08T11:52:36ZGrant Taylor-2What file(s) would I need to edit if I wanted to customize the admin
<br>login page?
<br><br>I'm wanting to add an onLoad value to the BODY tag (and related name tag
<br>to the form) to the web page that is generated to automatically focus
<br>the password box so that I can go to the web page and enter the password
<br>with out touching the mouse (or tabbing).
<br><br><br><br>Grant. . . .
<br>------------------------------------------------------
<br>Mailman-Users mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21359705&i=0" target="_top" rel="nofollow">Mailman-Users@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-users" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-users</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-users%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-users%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Users-f1729.html" embed="fixTarget[1729]" target="_top" >Mailman - Users</a></p>tag:www.nabble.com,2006:post-21356288Re: Listserv error2009-01-08T09:07:28Z2009-01-08T09:07:28ZMark Sapiro-3<<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21356288&i=0" target="_top" rel="nofollow">ljanofsk@...</a>> wrote:
<br>>
<br>>My fraternity is having a problem accessing our listserv membership online. I am the administrator for the group and when I go to the website to add/drop e-mail addresses, it tells me it doesn't exist. This is the first time this issue has come up and if you have any suggestions to fix this,I would greatly appreciate your help.
<br>>
<br>>Here is the URL that I go to:
<br>><a href="http://mail.zetapsiumd.com/mailman/admin/brothers_zetapsiumd.com" target="_top" rel="nofollow">http://mail.zetapsiumd.com/mailman/admin/brothers_zetapsiumd.com</a><br><br><br>First, you are off on the wrong foot by referring to a Mailman list as
<br>a "listserv".
<br><br>I know that use of Listserv(r) as a generic term to refer to an email
<br>list or email list management software is ubiquitious, and I'm just
<br>pissing in the wind to fight it, but Listserv(r) is a registered
<br>trademark[1] owned by the developer of a particular email list
<br>management product, and it shouldn't be used generically.
<br><br>Second, The Mailman installation at mail.zetapsiumd.com appears to be
<br>cPanel. See the FAQ at <<a href="http://wiki.list.org/x/sYA9" target="_top" rel="nofollow">http://wiki.list.org/x/sYA9</a>>.
<br><br>Finally, it appears that your list has been deleted. There's no way we
<br>can help you with that. You will have to talk to your hosting service.
<br><br>[1] <<a href="http://www.lsoft.com/corporate/trademark.asp" target="_top" rel="nofollow">http://www.lsoft.com/corporate/trademark.asp</a>>
<br><br>--
<br>Mark Sapiro <<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21356288&i=1" target="_top" rel="nofollow">mark@...</a>> The highway is for gamblers,
<br>San Francisco Bay Area, California better use your sense - B. Dylan
<br><br>------------------------------------------------------
<br>Mailman-Users mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21356288&i=2" target="_top" rel="nofollow">Mailman-Users@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-users" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-users</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-users%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-users%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Users-f1729.html" embed="fixTarget[1729]" target="_top" >Mailman - Users</a></p>tag:www.nabble.com,2006:post-21346820Listserv error2009-01-07T17:34:34Z2009-01-07T17:34:34ZljanofskTo whom this may concern,
<br><br>My fraternity is having a problem accessing our listserv membership online. I am the administrator for the group and when I go to the website to add/drop e-mail addresses, it tells me it doesn't exist. This is the first time this issue has come up and if you have any suggestions to fix this,I would greatly appreciate your help.
<br><br>Here is the URL that I go to:
<br><a href="http://mail.zetapsiumd.com/mailman/admin/brothers_zetapsiumd.com" target="_top" rel="nofollow">http://mail.zetapsiumd.com/mailman/admin/brothers_zetapsiumd.com</a><br><br>Thank you for your assistance.
<br><br><br>Sincerely,
<br><br>Lee Janofsky
<br><br>------------------------------------------------------
<br>Mailman-Users mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21346820&i=0" target="_top" rel="nofollow">Mailman-Users@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-users" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-users</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-users%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-users%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Users-f1729.html" embed="fixTarget[1729]" target="_top" >Mailman - Users</a></p>tag:www.nabble.com,2006:post-21343685Re: "Orignal" MySQL Member Adaptor - 1.712009-01-07T16:40:37Z2009-01-07T16:40:37ZMark Sapiro-3Fil wrote:
<br><div class='shrinkable-quote'><br>>OK I get something working with the following:
<br>>
<br>>
<br>> def escape(self, value):
<br>> try:
<br>> b = unicode(value,'utf-8')
<br>> except:
<br>> try:
<br>> b = unicode(value,'latin-1')
<br>> except:
<br>> b = value
<br>> return unicode(MySQLdb.escape_string(b.encode('utf-8')),'utf-8')
<br>>
<br>>
<br>>will try a little more and commit if it works
</div><br><br>I'm not totally up on what you're doing here, but I assume that value
<br>is something like the member's real name.
<br><br>In this case I think you may want something like
<br><br>>From Mailman import Utils
<br>...
<br> def escape(self, value):
<br> lcset = Utils.GetCharSet(mlist.preferred_language)
<br> b = unicode(value, lcset)
<br> ...
<br><br>I.e. text items relating to a list or a member are normally either
<br>unicodes to begin with or they are encoded in the character set of the
<br>list's preferred language.
<br><br>--
<br>Mark Sapiro <<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21343685&i=0" target="_top" rel="nofollow">mark@...</a>> The highway is for gamblers,
<br>San Francisco Bay Area, California better use your sense - B. Dylan
<br><br>_______________________________________________
<br>Mailman-Developers mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21343685&i=1" target="_top" rel="nofollow">Mailman-Developers@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-developers" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-developers</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-developers%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-developers%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Dev-f1731.html" embed="fixTarget[1731]" target="_top" >Mailman - Dev</a></p>tag:www.nabble.com,2006:post-21340649Email subscription not working2009-01-07T13:23:47Z2009-01-07T13:23:47ZDan Mahoney, System AdminHey all, I'm hitting a little snag. Email subscribe isn't doing anything.
<br><br>Postfix delivers the email to mailman, but then as far as I can tell,
<br>nothing more happens with it.
<br><br>Where would be the best place to debug this from a mailman perspective?
<br><br>Jan 7 21:05:34 lister postfix/qmgr[97071]: DDFD010E528:
<br>from=<<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21340649&i=0" target="_top" rel="nofollow">ionlyhavethisfortesting@...</a>>, size=2716, nrcpt=1 (queue
<br>active)
<br>Jan 7 21:05:35 lister postfix/local[38795]: DDFD010E528:
<br>to=<<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21340649&i=1" target="_top" rel="nofollow">testing-join@...</a>>, relay=local, delay=0.18,
<br>delays=0.01/0/0/0.17, dsn=2.0.0, status=sent (delivered to command:
<br>/usr/local/mailman/mail/mailman join testing)
<br>Jan 7 21:05:35 lister postfix/qmgr[97071]: DDFD010E528: removed
<br><br>And that's where it stops. The address doesn't show in any logs or
<br>anything from that point forward.
<br><br>Anything obvious I should be checking? Perhaps the possibility that the
<br>"to" address is getting altered in transit? Does mailman log discarded
<br>subscription messages? Is there a debug option?
<br><br>-Dan
<br><br>--
<br><br>--------Dan Mahoney--------
<br>Techie, Sysadmin, WebGeek
<br>Gushi on efnet/undernet IRC
<br>ICQ: 13735144 AIM: LarpGM
<br>Site: <a href="http://www.gushi.org" target="_top" rel="nofollow">http://www.gushi.org</a><br>---------------------------
<br><br>------------------------------------------------------
<br>Mailman-Users mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21340649&i=2" target="_top" rel="nofollow">Mailman-Users@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-users" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-users</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-users%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-users%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Users-f1729.html" embed="fixTarget[1729]" target="_top" >Mailman - Users</a></p>tag:www.nabble.com,2006:post-21340219Re: MySQL Member Adaptor(s) - Various comments.2009-01-07T13:01:02Z2009-01-07T13:01:02ZBarry Warsaw-3-----BEGIN PGP SIGNED MESSAGE-----
<br>Hash: SHA1
<br><br>On Sep 27, 2008, at 9:11 AM, Kyrian (List) wrote:
<br><br>> About MM3 resources:
<br>>
<br>> Thanks, these will be noted in my Wiki for whenever I find time to
<br>> look at it.
<br><br>Let me just mention that MM3 is built on the Storm ORM for Python,
<br>which in theory should make it fairly trivial to hook it up to MySQL.
<br>I haven't tried it yet though, since MM3 will use SQLite by default
<br>(since that comes with Python 2.6). Tests and contributions are
<br>welcome.
<br><br>Barry
<br><br>-----BEGIN PGP SIGNATURE-----
<br>Version: GnuPG v1.4.9 (Darwin)
<br><br>iEYEARECAAYFAkllGA8ACgkQ2YZpQepbvXGr0QCgkavbb/KBrxCiAxorqqJzjKXf
<br>E08Anj1dQ9qMNiULdjD+fVLv/d8uzZhN
<br>=1/z1
<br>-----END PGP SIGNATURE-----
<br>_______________________________________________
<br>Mailman-Developers mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21340219&i=0" target="_top" rel="nofollow">Mailman-Developers@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-developers" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-developers</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-developers%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-developers%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Dev-f1731.html" embed="fixTarget[1731]" target="_top" >Mailman - Dev</a></p>tag:www.nabble.com,2006:post-21336608Re: "Orignal" MySQL Member Adaptor - 1.712009-01-07T09:44:58Z2009-01-07T09:44:58Zfil-4OK I get something working with the following:
<br><br><br> def escape(self, value):
<br> try:
<br> b = unicode(value,'utf-8')
<br> except:
<br> try:
<br> b = unicode(value,'latin-1')
<br> except:
<br> b = value
<br> return unicode(MySQLdb.escape_string(b.encode('utf-8')),'utf-8')
<br><br><br>will try a little more and commit if it works
<br>_______________________________________________
<br>Mailman-Developers mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21336608&i=0" target="_top" rel="nofollow">Mailman-Developers@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-developers" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-developers</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-developers%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-developers%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Dev-f1731.html" embed="fixTarget[1731]" target="_top" >Mailman - Dev</a></p>tag:www.nabble.com,2006:post-21336338Re: "Orignal" MySQL Member Adaptor - 1.712009-01-07T09:29:55Z2009-01-07T09:29:55Zfil-4I was able to go a bit further with the script below. Unfortunately
<br>when that utf-8-encoded mysql-escaped string goes back up into MySQLdb
<br>I get hit by another encoding error inside MySQLdb. So my best for the
<br>moment is to stay with my current implementation which escapes all
<br>strings to html decimal entities.
<br><br><br><br>#!/usr/bin/python
<br><br>import os, sys
<br>import MySQLdb
<br>from types import StringType,UnicodeType
<br><br>a='\'And"ré'
<br><br>try:
<br> b=unicode(a,'utf-8')
<br>except:
<br> b=unicode(a,'latin-1')
<br><br>print b.encode('latin-1')
<br>print b.encode('utf-8')
<br><br>print MySQLdb.escape_string(b.encode('utf-8'))
<br><br><br><br>-- Fil
<br>_______________________________________________
<br>Mailman-Developers mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21336338&i=0" target="_top" rel="nofollow">Mailman-Developers@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-developers" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-developers</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-developers%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-developers%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Dev-f1731.html" embed="fixTarget[1731]" target="_top" >Mailman - Dev</a></p>tag:www.nabble.com,2006:post-21336751mailman-pgp-smime: talks at FOSDEM and in Ulm, new release2009-01-07T09:20:25Z2009-01-07T09:20:25ZJoost van Baal-124Hi,
<br><br>Thanks to the NLnet foundation, the Secure List Server project (
<br><a href="http://non-gnu.uvt.nl/mailman-pgp-smime/" target="_top" rel="nofollow">http://non-gnu.uvt.nl/mailman-pgp-smime/</a> ) , which is including OpenPGP and
<br>S/MIME support in Mailman has released a much improved mailman-pgp-smime patch:
<br><a href="http://non-gnu.uvt.nl/pub/mailman/mailman-2.1.11-pgp-smime_2009-01-02.patch.gz" target="_top" rel="nofollow">http://non-gnu.uvt.nl/pub/mailman/mailman-2.1.11-pgp-smime_2009-01-02.patch.gz</a><br>. See <a href="http://non-gnu.uvt.nl/mailman-pgp-smime/NEWS.PGP-SMIME" target="_top" rel="nofollow">http://non-gnu.uvt.nl/mailman-pgp-smime/NEWS.PGP-SMIME</a> for the details.
<br><br>There'll be talks about this patch:
<br><br>On monday january 12 I'll talk at the Chaos Seminar</a> in Ulm, Germany,
<br>see <a href="http://ulm.ccc.de/ChaosSeminar/2009/01_Mailman_PGP_SMIME" target="_top" rel="nofollow">http://ulm.ccc.de/ChaosSeminar/2009/01_Mailman_PGP_SMIME</a> .
<br><br>On sunday february 8th, 10h20 (probably), I'll give a lightning talk at the
<br>FOSDEM conference, ULB Campus Solbosch, Brussels, Belgium. See
<br><a href="http://fosdem.org/2009/node/164" target="_top" rel="nofollow">http://fosdem.org/2009/node/164</a>.
<br><br>The talk will start with a very short overview of the history of Mailman and
<br>the mailman-pgp-smime project. Some remarks will be made on how to install and
<br>configure the software, so that one can try it. Currently supported features
<br>will be mentioned, as well as an overview of development plans. One will learn
<br>how to contribute to the project; an overview of the revision control system
<br>used will be given. Some remarks on the future of the patch will be made: will
<br>it be shipped with Mailman itself?
<br><br>If you have used Mailman, both as a subscriber and as a list admin, and if
<br>you know what PGP and S/MIME are, you should definitely attend this talk.
<br><br>Hope to meet you there!
<br><br>Bye,
<br><br>Joost
<br><br>--
<br>irc:joostvb@{OFTC,freenode} ∙ <a href="http://mdcc.cx/" target="_top" rel="nofollow">http://mdcc.cx/</a> ∙ <a href="http://ad1810.com/" target="_top" rel="nofollow">http://ad1810.com/</a><br><br /> <br />_______________________________________________
<br>Mailman-Developers mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21336751&i=0" target="_top" rel="nofollow">Mailman-Developers@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-developers" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-developers</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-developers%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-developers%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><div class="small"><br/><img src="http://www.nabble.com/images/icon_attachment.gif" > <strong>signature.asc</strong> (852 bytes) <a href="http://www.nabble.com/attachment/21336751/0/signature.asc" target="_top">Download Attachment</a></div><p>From forum: <a href="http://www.nabble.com/Mailman---Dev-f1731.html" embed="fixTarget[1731]" target="_top" >Mailman - Dev</a></p>tag:www.nabble.com,2006:post-21334681Re: "Orignal" MySQL Member Adaptor - 1.712009-01-07T08:18:28Z2009-01-07T08:18:28ZMark Sapiro-3kyrian (List) wrote:
<br>>
<br>>The gist of the problem seems to be that you need to treat the strings
<br>>as utf-8 or iso-8859-1 encoded 'objects' rather than standard ASCII
<br>>string types within the code, and I don't know for sure how to do that.
<br><br>And you have to know which because there are iso-8859-1 encoded
<br>characters which aren't valid utf-8 codes and there are utf-8 encoded
<br>characters which get garbled if decoded as iso-8859-1.
<br><br>Thus, code like
<br><br> try:
<br> unicode(value, "ascii")
<br> except UnicodeError:
<br> value = unicode(value, "utf-8")
<br> else:
<br> # value was valid ASCII data
<br> pass
<br><br>which I think is no different from simply
<br><br> value = unicode(value, "utf-8")
<br><br>since if value is ascii to begin with, calling it utf-8 is OK,
<br><br>doesn't work if value is actually iso-8859-1 encoded and contains bytes
<br>which aren't valid utf-8 or which decode differently from utf-8.
<br><br>--
<br>Mark Sapiro <<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21334681&i=0" target="_top" rel="nofollow">mark@...</a>> The highway is for gamblers,
<br>San Francisco Bay Area, California better use your sense - B. Dylan
<br><br>_______________________________________________
<br>Mailman-Developers mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21334681&i=1" target="_top" rel="nofollow">Mailman-Developers@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-developers" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-developers</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-developers%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-developers%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Dev-f1731.html" embed="fixTarget[1731]" target="_top" >Mailman - Dev</a></p>tag:www.nabble.com,2006:post-21334571Re: "Orignal" MySQL Member Adaptor - 1.712009-01-07T08:14:29Z2009-01-07T08:14:29Zfil-4> I'm pretty sure I said I though it would work but hadn't actually tested it,
<br>> anyways.
<br><br>Indeed I was warned :-)
<br><br><br>> time to look at MM again for a while. My first priority would be to resolve
<br>> the horrible performance problem without losing the name info as per a
<br>> previous email, and then I might look at this, when I get started back on it
<br>> again.
<br><br>I've re-read your email re: the names issue, and I don't understand
<br>what the problem is.
<br><br>getMembersMatching() does indeed only return the adresses of all users
<br>whose email OR name matches the regexp; then Cgi/admin.py displays no
<br>more than 50 of these, which results in maximum 50 calls to MySQL to
<br>fetch the name information. I assert that:
<br>* a search on a name returns the user, even if the search string does
<br>not appear in its email
<br>* the users' names ARE displayed in the resulting page.
<br><br>-- Fil
<br>_______________________________________________
<br>Mailman-Developers mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21334571&i=0" target="_top" rel="nofollow">Mailman-Developers@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-developers" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-developers</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-developers%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-developers%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Dev-f1731.html" embed="fixTarget[1731]" target="_top" >Mailman - Dev</a></p>tag:www.nabble.com,2006:post-21334171Re: "Orignal" MySQL Member Adaptor - 1.712009-01-07T07:50:11Z2009-01-07T07:50:11ZKyrian (list)Fil wrote:
<div class='shrinkable-quote'><br>>> It should according to the docs I found, provided I've applied them
<br>>> correctly, fix the non-ASCII character encoding problems (I've relied on
<br>>> the assertions about list members to cover that angle, and just checked
<br>>> encoding on the 'user supplied' parameters to various function calls).
<br>>>
<br>> I finally got the time to look at your character encoding problem and
<br>> patch, and I was not able to make it work. I still getting the dreaded
<br>> UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in
<br>> position 1: ordinal not in range(128)
<br>>
<br>>
</div>Seems my "lucky guess" was not so lucky ;-)
<br><br>I'm pretty sure I said I though it would work but hadn't actually tested
<br>it, anyways. I don't currently have a 'live' mailman+mysql instance
<br>anywhere to test with, for a start. I've got a dedicated development
<br>server set up but not migrated anything like that to it yet.
<br><br>Also I'm afraid that I'm quite engrossed in writing a plugin for Pidgin
<br>and playing with Asterisk VoIP at the moment, and hadn't really settled
<br>on a time to look at MM again for a while. My first priority would be to
<br>resolve the horrible performance problem without losing the name info as
<br>per a previous email, and then I might look at this, when I get started
<br>back on it again.
<br><br>The gist of the problem seems to be that you need to treat the strings
<br>as utf-8 or iso-8859-1 encoded 'objects' rather than standard ASCII
<br>string types within the code, and I don't know for sure how to do that.
<br>I'd have to research it as much as you would, unless anyone on-list has
<br>a suggestion about it, or can send me a copy of the Python book that I
<br>can reference for this.
<br><br>K.
<br><br>--
<br>Kev Green, aka Kyrian. E: kyrian@ore.org WWW: <a href="http://kyrian.ore.org/" target="_top" rel="nofollow">http://kyrian.ore.org/</a><br>Linux/Security Contractor/LAMP Coder/ISP, via <a href="http://www.orenet.co.uk/" target="_top" rel="nofollow">http://www.orenet.co.uk/</a><br> DJ via <a href="http://www.hellnoise.co.uk/" target="_top" rel="nofollow">http://www.hellnoise.co.uk/</a><br><br>Human Rights left unattended may be Removed, or Destroyed, or Damaged
<br> by the Security Services.
<br><br>_______________________________________________
<br>Mailman-Developers mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21334171&i=0" target="_top" rel="nofollow">Mailman-Developers@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-developers" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-developers</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-developers%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-developers%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Dev-f1731.html" embed="fixTarget[1731]" target="_top" >Mailman - Dev</a></p>tag:www.nabble.com,2006:post-21332677Re: "Orignal" MySQL Member Adaptor - 1.712009-01-07T06:43:51Z2009-01-07T06:43:51Zfil-4> It should according to the docs I found, provided I've applied them
<br>> correctly, fix the non-ASCII character encoding problems (I've relied on
<br>> the assertions about list members to cover that angle, and just checked
<br>> encoding on the 'user supplied' parameters to various function calls).
<br><br>Hi Kev,
<br><br>I finally got the time to look at your character encoding problem and
<br>patch, and I was not able to make it work. I still getting the dreaded
<br>UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in
<br>position 1: ordinal not in range(128)
<br><br>On my version of MysqlMemberships.py there is a centralized function
<br>which does the escaping and is used on every sql request:
<br><br> def escape(self, value):
<br> # transforms accents into html entities (é)
<br> # TODO: find out which language is current (here: uses iso-8859-1)
<br> value = Utils.uncanonstr(value)
<br> # addslashes before " and '
<br> return MySQLdb.escape_string(value)
<br><br><br>I tried to add your unicode logic at this point, but to no avail. And
<br>BTW I also need the thing to be functional both with utf8 and
<br>iso-8859-1.
<br><br><br>For people who'd like to join in the conversation, the logic I'm
<br>refferring to is the following:
<br> # safe unicode strings encoded for mysql
<br> # <a href="http://effbot.org/pyfaq/what-does-unicodeerror-ascii-decoding-encoding-error-ordinal-not-in-range-128-mean.htm" target="_top" rel="nofollow">http://effbot.org/pyfaq/what-does-unicodeerror-ascii-decoding-encoding-error-ordinal-not-in-range-128-mean.htm</a><br> try:
<br> unicode(value, "ascii")
<br> except UnicodeError:
<br> value = unicode(value, "utf-8")
<br> else:
<br> # value was valid ASCII data
<br> pass
<br><br>-- Fil
<br>_______________________________________________
<br>Mailman-Developers mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21332677&i=0" target="_top" rel="nofollow">Mailman-Developers@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-developers" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-developers</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-developers%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-developers%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Dev-f1731.html" embed="fixTarget[1731]" target="_top" >Mailman - Dev</a></p>tag:www.nabble.com,2006:post-21324972Re: Mailman 3 and LTMP2009-01-06T21:02:33Z2009-01-06T21:02:33ZBarry Warsaw-3-----BEGIN PGP SIGNED MESSAGE-----
<br>Hash: SHA1
<br><br>On Jan 5, 2009, at 6:03 AM, Ian Eiloart wrote:
<br><br>> I've added a note to the docs about Exim's callout features. They
<br>> allow Exim to determine not only whether the list exists, but
<br>> whether the list will accept mail from the current sender - before
<br>> accepting the message for delivery. I'll fill in the details later.
<br><br>Thanks. I've added a NullMTA class that can be used for Exim, which
<br>doesn't require an alias file write. You'd use it by adding this to
<br>your .cfg file:
<br><br>[mta]
<br>incoming: mailman.mta.null.NullMTA
<br><br>- -Barry
<br><br>-----BEGIN PGP SIGNATURE-----
<br>Version: GnuPG v1.4.9 (Darwin)
<br><br>iEYEARECAAYFAklkN2kACgkQ2YZpQepbvXGW/ACfef755PghiLN32pSPso2SaVr2
<br>e74Ani7xePXWtj6FjBUcm373lL1h8XTk
<br>=tUgP
<br>-----END PGP SIGNATURE-----
<br>_______________________________________________
<br>Mailman-Developers mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21324972&i=0" target="_top" rel="nofollow">Mailman-Developers@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-developers" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-developers</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-developers%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-developers%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Dev-f1731.html" embed="fixTarget[1731]" target="_top" >Mailman - Dev</a></p>tag:www.nabble.com,2006:post-21324896Re: Mailman 3 and LTMP2009-01-06T20:50:38Z2009-01-06T20:50:38ZBarry Warsaw-3-----BEGIN PGP SIGNED MESSAGE-----
<br>Hash: SHA1
<br><br>On Jan 4, 2009, at 7:29 PM, Patrick Ben Koetter wrote:
<br><div class='shrinkable-quote'><br>> * Barry Warsaw <<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21324896&i=0" target="_top" rel="nofollow">barry@...</a>>:
<br>>> -----BEGIN PGP SIGNED MESSAGE-----
<br>>> Hash: SHA1
<br>>>
<br>>> On Jan 05, 2009, at 12:58 AM, Patrick Ben Koetter wrote:
<br>>>
<br>>>> Thanks. Minor bug fix in the docco, though. Destination syntax for
<br>>>> lmtp
<br>>>> targets in the transport table requires a fourth parameter:
<br>>>> service type.
<br>>>
<br>>> I'm not sure it requires it; I saw that in the Postfix
<br>>> documentation, but my
<br>>> current genaliases implementation doesn't write the 'inet'
<br>>> argument. It still
<br>>> seems to work. Better to be correct though, so I'll fix that.
<br>>
<br>> Victor pointed it out on the Postfix mailing list. It's probably
<br>> better to be
<br>> on the precise side in this case. In case you want to do more
<br>> reading, take a
<br>> look at lmtp(8).
</div><br>This is fixed in the 3.0 branch now.
<br>- -Barry
<br><br>-----BEGIN PGP SIGNATURE-----
<br>Version: GnuPG v1.4.9 (Darwin)
<br><br>iEYEARECAAYFAklkNJ4ACgkQ2YZpQepbvXHn+ACgn4Y6GdrNfeVTIn4XEilOd8tK
<br>dK8AoKWlKUBc5VW4RKlpG8RY2wGCqjSq
<br>=NDQP
<br>-----END PGP SIGNATURE-----
<br>_______________________________________________
<br>Mailman-Developers mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21324896&i=1" target="_top" rel="nofollow">Mailman-Developers@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-developers" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-developers</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-developers%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-developers%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Dev-f1731.html" embed="fixTarget[1731]" target="_top" >Mailman - Dev</a></p>tag:www.nabble.com,2006:post-21319535Re: The economics of spam2009-01-06T13:30:15Z2009-01-06T13:30:15ZRich KulawiecOn Sun, Jan 04, 2009 at 03:56:42PM -0800, Jan Steinman wrote:
<br>> Is it really necessary to take this arrogant and abusive tone?
<br><br>Consider it exasperation at seeing this FUSSP brought up yet *again*,
<br>long after it was staked through the heart and buried at a crossroads.
<br>Please see:
<br><br> <a href="http://www.rhyolite.com/anti-spam/you-might-be.html#e-postage" target="_top" rel="nofollow">http://www.rhyolite.com/anti-spam/you-might-be.html#e-postage</a><br><br>for background on and examples of FUSSPs.
<br><br>If you (rhetorical you) want to self-educate and to potentially apply
<br>yourself to addressing the problem, then by all means, please do.
<br>But this list isn't appropriate; I suggest joining some/all of these:
<br><br> spam-l (via <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21319535&i=0" target="_top" rel="nofollow">listserv@...</a>)
<br> asrg (via <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21319535&i=1" target="_top" rel="nofollow">asrg-request@...</a>)
<br> spamtools (via <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21319535&i=2" target="_top" rel="nofollow">spamtools-request@...</a>)
<br><br>AND reading most of their archives, especially spam-l, before attempting
<br>to promulgate your favorite tactic/strategy. (I'm not the only one with
<br>a short fuse when it comes to dealing with the same known-failed idea for
<br>the 47th time, although I will readily admit that some others show far
<br>more patience than I do. Maybe they have more -- or better -- brandy.)
<br><br>---Rsk
<br><br>p.s. As a small courtesy, and by way of compensation, let me try
<br>to provide some minor assistance to potential future contributors by
<br>enumerating a few of the fundamental design errors that immediately doom
<br>some "anti-spam" ideas:
<br><br> - redefining abuse
<br> - redirecting abuse
<br> - amplifying abuse
<br> - fighting abuse with abuse
<br> - failure to consider scaling issues ("what if everyone did this?")
<br> - failure to consider adoption issues ("what if everyone didn't do this?")
<br> - failure to consider counter-measures ("what if spammers read RFCs?")
<br> - generating yet more SMTP traffic
<br> - presumption of spammer honesty/compliance/acquiescence
<br> - allowing unknown third parties to generate significant amounts
<br> of outbound traffic to destinations of their choosing
<br> - reliance on legislation and/or law enforcement
<br> - forcing effort and costs of abuse control onto third parties
<br> - drastic underestimation of spammer resources and abilities
<br> - presumption of secure network endpoints
<br><br>There's more, of course, but a few minutes' contemplation of these is
<br>sufficient to understand why some approaches (e.g., opt-out, SPF, C/R,
<br>SAV, BlueFrog, and yes, e-postage) are not going to work regardless
<br>of how they're implemented, and why attempts to implement them make
<br>(or would make) the spam/abuse problem considerably worse.
<br>------------------------------------------------------
<br>Mailman-Users mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21319535&i=3" target="_top" rel="nofollow">Mailman-Users@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-users" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-users</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-users%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-users%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Users-f1729.html" embed="fixTarget[1729]" target="_top" >Mailman - Users</a></p>tag:www.nabble.com,2006:post-21313887Re: Unknown encoding error2009-01-06T08:36:21Z2009-01-06T08:36:21ZMark Sapiro-3Khosrow Ebrahimpour wrote:
<div class='shrinkable-quote'><br>>
<br>> A week or so ago I ran across this problem on one of our mailing lists: A user
<br>> had sent an email with an apparently bad subject line. This has caused
<br>> mailman to stop delivering emails for that specific mailning list. Here's the
<br>> error from the logfile:
<br>>
<br>> ---
<br>>
<br>> Jan 05 21:25:10 2009 (23055) Uncaught runner exception: unknown encoding: Re:
<br>> DDS 26073 : Imap - installation d
<br>> Jan 05 21:25:10 2009 (23055) Traceback (most recent call last):
<br>> File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop
<br>> self._onefile(msg, msgdata)
<br>> File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 167, in _onefile
<br>> keepqueued = self._dispose(mlist, msg, msgdata)
<br>> File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in
<br>> _dispose
<br>> more = self._dopipeline(mlist, msg, msgdata, pipeline)
<br>> File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in
<br>> _dopipeline
<br>> sys.modules[modname].process(mlist, msg, msgdata)
<br>> File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 91, in process
<br>> send_digests(mlist, mboxfp)
<br>> File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 132, in
<br>> send_digests
<br>> send_i18n_digests(mlist, mboxfp)
<br>> File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 306, in
<br>> send_i18n_digests
<br>> msg = scrubber(mlist, msg)
<br>> File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 240, in process
<br>> url = save_attachment(mlist, part, dir)
<br>> File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 373, in
<br>> save_attachment
<br>> fnext = os.path.splitext(msg.get_filename(''))[1]
<br>> File "/usr/lib/python2.3/email/Message.py", line 731, in get_filename
<br>> return unicode(newvalue[2], newvalue[0] or 'us-ascii')
<br>> LookupError: unknown encoding: Re: DDS 26073 : Imap - installation d
<br>>
<br>> Jan 05 21:25:10 2009 (23055) SHUNTING:
<br>> 1231190705.198385+f75914e7ce7a9daf6e70914e0ed49923a47d2dd1
</div><br><br>The message that causes this problem is not the message that is shunted.
<br>All the shunted messages are (presumably) valid messages that arrived
<br>after the issue started.
<br><br>The problem is that a message was posted to the list and probably
<br>delivered normally and stored in the digest.mbox file for the list.
<br>Then, eventually, the digest.mbox grew big enough that every subsequent
<br>message triggers a digest delivery on size, but the bad message in
<br>digest.mbox throws the above exception in the ToDigest handler, and the
<br>digest is not produced and the current message is shunted.
<br><br><br>> The full subject line should be:
<br>>
<br>> RE: DDS 26073 : Imap - installation d'application 'vacation'
<br>>
<br>> so I think the apostrophe is causing havoc here...
<br><br><br>Yes, it is an apostrophe that is the problem, but it is in a 'name' or
<br>'filename' parameter of a Content-Type: or Content-Disposition: header.
<br><br><br>> I have searched mailing list and the search engines, and it looks like this
<br>> error was a problem for people but has been solved in subsequent versions of
<br>> mailman (we are running 2.1.5 on Debian Sarge). What I haven't been able to
<br>> find out is how to purge out the offending email, and continue life as normal
<br>> until we upgrade to Etch!
<br>>
<br>> I should say that I have tried removing the offending file from
<br>> $MAILMANDIR/qfiles/shunt and running "unshunt", but nothing changed.
<br><br><br>You don't want to remove the shunted files as they are not the problem,
<br>and you can't successfully unshunt until you fix the digest.mbox.
<br><br>You need to edit the lists/LISTNAME/digest.mbox. You can edit it by hand
<br>or with an MUA like mutt for example.
<br><br>The offending message has an RFC 2231 enncoded 'name' or 'filename'
<br>parameter with an apostrophe in the name. It will look something like
<br><br>Content-Disposition: attachment;
<br> filename*0*='charset'lang'text....................................
<br> filename*1=more.............................
<br><br>And text will have an apostrophe.
<br><br>You can simply remove those parameters (filename and/or name) or delete
<br>the entire message.
<br><br>You can also just delete the lists/LISTNAME/digest.mbox file, but then
<br>you'd lose those messages from the digest.
<br><br>After fixing the digest.mbox, you can run bin/unshunt to finish
<br>processing the shunted messages.
<br><br>--
<br>Mark Sapiro <<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21313887&i=0" target="_top" rel="nofollow">mark@...</a>> The highway is for gamblers,
<br>San Francisco Bay Area, California better use your sense - B. Dylan
<br><br>------------------------------------------------------
<br>Mailman-Users mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21313887&i=1" target="_top" rel="nofollow">Mailman-Users@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-users" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-users</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-users%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-users%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Users-f1729.html" embed="fixTarget[1729]" target="_top" >Mailman - Users</a></p>tag:www.nabble.com,2006:post-21305879Unknown encoding error2009-01-05T14:12:18Z2009-01-05T14:12:18ZKhosrow EbrahimpourHello list,
<br><br>A week or so ago I ran across this problem on one of our mailing lists: A user
<br>had sent an email with an apparently bad subject line. This has caused
<br>mailman to stop delivering emails for that specific mailning list. Here's the
<br>error from the logfile:
<br><br>---
<br><br>Jan 05 21:25:10 2009 (23055) Uncaught runner exception: unknown encoding: Re:
<br>DDS 26073 : Imap - installation d
<br>Jan 05 21:25:10 2009 (23055) Traceback (most recent call last):
<br> File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop
<br> self._onefile(msg, msgdata)
<br> File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 167, in _onefile
<br> keepqueued = self._dispose(mlist, msg, msgdata)
<br> File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in
<br>_dispose
<br> more = self._dopipeline(mlist, msg, msgdata, pipeline)
<br> File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in
<br>_dopipeline
<br> sys.modules[modname].process(mlist, msg, msgdata)
<br> File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 91, in process
<br> send_digests(mlist, mboxfp)
<br> File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 132, in
<br>send_digests
<br> send_i18n_digests(mlist, mboxfp)
<br> File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 306, in
<br>send_i18n_digests
<br> msg = scrubber(mlist, msg)
<br> File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 240, in process
<br> url = save_attachment(mlist, part, dir)
<br> File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 373, in
<br>save_attachment
<br> fnext = os.path.splitext(msg.get_filename(''))[1]
<br> File "/usr/lib/python2.3/email/Message.py", line 731, in get_filename
<br> return unicode(newvalue[2], newvalue[0] or 'us-ascii')
<br>LookupError: unknown encoding: Re: DDS 26073 : Imap - installation d
<br><br>Jan 05 21:25:10 2009 (23055) SHUNTING:
<br>1231190705.198385+f75914e7ce7a9daf6e70914e0ed49923a47d2dd1
<br><br><br>---
<br><br>The full subject line should be:
<br><br>RE: DDS 26073 : Imap - installation d'application 'vacation'
<br><br>so I think the apostrophe is causing havoc here...
<br><br>I have searched mailing list and the search engines, and it looks like this
<br>error was a problem for people but has been solved in subsequent versions of
<br>mailman (we are running 2.1.5 on Debian Sarge). What I haven't been able to
<br>find out is how to purge out the offending email, and continue life as normal
<br>until we upgrade to Etch!
<br><br>I should say that I have tried removing the offending file from
<br>$MAILMANDIR/qfiles/shunt and running "unshunt", but nothing changed.
<br><br>Any suggestions are most appreciated.
<br>/Khosrow
<br><br /> <br />------------------------------------------------------
<br>Mailman-Users mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21305879&i=0" target="_top" rel="nofollow">Mailman-Users@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-users" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-users</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-users%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-users%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><div class="small"><br/><img src="http://www.nabble.com/images/icon_attachment.gif" > <strong>attachment0</strong> (196 bytes) <a href="http://www.nabble.com/attachment/21305879/0/attachment0" target="_top">Download Attachment</a></div><p>From forum: <a href="http://www.nabble.com/Mailman---Users-f1729.html" embed="fixTarget[1729]" target="_top" >Mailman - Users</a></p>tag:www.nabble.com,2006:post-21298151Re: FAQ: How To Rename a Mailman List2009-01-05T11:59:58Z2009-01-05T11:59:58ZBarry Finkel-3Barry Finkel wrote:
<br><br>>>I need to rename two Mailman 2.1.9 lists. The FAQ 4.70 gives
<br>>>explicit instructions, but it does not mention changing the
<br>>>
<br>>> /var/lib/mailman/data/aliases (location on my Unbutu system)
<br>>>
<br>>>file to reflect the new name and then running the newaliases command.
<br>>>Should this be added to the FAQ?
<br><br>And Mark Sapiro replied:
<div class='shrinkable-quote'><br>>The FAQ currently says:
<br>>
<br>> Finally, if your MTA uses aliases for mailman lists rather than
<br>> some process that automatically understands list names from the
<br>> contents of the lists/ directory, you will have to update your
<br>> aliases. If you do this manually, edit your aliases to change
<br>> 'oldlist' to 'newlist' (a total of 2 changes per alias for 10
<br>> aliases), and then run 'newaliases' or whatever command rebuilds
<br>> your alias database. It you have Postfix/Mailman integration,
<br>> just run bin/genaliases.
<br>>
<br>>If you think this is somehow inadequate or not prominent enough, it's a
<br>>wiki. Feel free to edit it.
</div><br>I do not know how I missed that piece. Thanks.
<br>----------------------------------------------------------------------
<br>Barry S. Finkel
<br>Computing and Information Systems Division
<br>Argonne National Laboratory Phone: +1 (630) 252-7277
<br>9700 South Cass Avenue Facsimile:+1 (630) 252-4601
<br>Building 222, Room D209 Internet: <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21298151&i=0" target="_top" rel="nofollow">BSFinkel@...</a>
<br>Argonne, IL 60439-4828 IBMMAIL: I1004994
<br><br>------------------------------------------------------
<br>Mailman-Users mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21298151&i=1" target="_top" rel="nofollow">Mailman-Users@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-users" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-users</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-users%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-users%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Users-f1729.html" embed="fixTarget[1729]" target="_top" >Mailman - Users</a></p>tag:www.nabble.com,2006:post-21297783Re: Doubt about security2009-01-05T11:40:54Z2009-01-05T11:40:54ZMark Sapiro-3Barry Warsaw wrote:
<div class='shrinkable-quote'><br>>
<br>>On Jan 5, 2009, at 1:12 PM, <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21297783&i=0" target="_top" rel="nofollow">skip@...</a> wrote:
<br>>
<br>>> I suspect the default should be to not expose those things. I
<br>>> wasn't even
<br>>> aware that list creation through the web was possible. Based on the
<br>>> extremely novice questions I see posted to mailman-users on occasion I
<br>>> suspect many potential Mailman admins are unaware of this as well.
<br>>> I fear
<br>>> those admins are also the ones most likely to not create strong
<br>>> passwords.
<br>>
<br>>Note that by default, it's not possible to create mailing lists
<br>>through the web even though the link exists. You have to create a
<br>>site password or 'list creators' password to enable this feature. A
<br>>site admin should know enough to set these passwords to something
<br>>strong and difficult to brute force.
<br>>
<br>>Still, the suggestions for disabling this CGI is easy enough, and if
<br>>you have shell access to create those passwords, you have shell access
<br>>to disable the CGI.
</div><br><br>As Barry points out, the door is neither open nor easily opened by
<br>default.
<br><br>Also, in a default installation, alias generation is manual, and
<br>creating a list from the web is not sufficient to make it work.
<br><br>Further, I think this whole list create issue is a red herring. If I
<br>were a black-hat looking to create a list on your server to use for my
<br>own nefarious purposes, I think I'd use my dictionary attack to try to
<br>access the admin interface of an existing list where the password is
<br>more likely to be weak. Once I have the admin password for an existing
<br>list, I can do anything with that list that I might have done with a
<br>new list, and incidentally do more damage to the installation (or at
<br>least that one list) in the process.
<br><br>--
<br>Mark Sapiro <<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21297783&i=1" target="_top" rel="nofollow">mark@...</a>> The highway is for gamblers,
<br>San Francisco Bay Area, California better use your sense - B. Dylan
<br><br>_______________________________________________
<br>Mailman-Developers mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21297783&i=2" target="_top" rel="nofollow">Mailman-Developers@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-developers" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-developers</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-developers%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-developers%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Dev-f1731.html" embed="fixTarget[1731]" target="_top" >Mailman - Dev</a></p>tag:www.nabble.com,2006:post-21297693Re: Doubt about security2009-01-05T11:35:54Z2009-01-05T11:35:54ZBarry Warsaw-3-----BEGIN PGP SIGNED MESSAGE-----
<br>Hash: SHA1
<br><br>On Jan 5, 2009, at 2:25 PM, Terri Oda wrote:
<br><div class='shrinkable-quote'><br>> This seems like it might be more of a failure in documentation/
<br>> understanding than a failure in security. All this information is
<br>> readily available (both about the fact that you can create from the
<br>> web by default, and the fact that this can be disabled) but
<br>> obviously people aren't finding it or don't even know to look for it.
<br>>
<br>> I'll try to poke around and figure out where to put it when I get
<br>> home from work. I'm guessing we could use some pointers in the
<br>> install guides? Or perhaps I should work up a short intro to
<br>> mailman security for new users who don't know the likely attack
<br>> points?
</div><br>I think a separate section on security concerns would be really helpful.
<br><br>Thanks!
<br>- -Barry
<br><br>-----BEGIN PGP SIGNATURE-----
<br>Version: GnuPG v1.4.9 (Darwin)
<br><br>iEYEARECAAYFAkliYRoACgkQ2YZpQepbvXFfqQCgpzjGrhBDEfvcdEH/BMnGgsLq
<br>UzsAnAnsOAqJUkIzcDBL0DRYS0qtLGgO
<br>=kAeJ
<br>-----END PGP SIGNATURE-----
<br>_______________________________________________
<br>Mailman-Developers mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21297693&i=0" target="_top" rel="nofollow">Mailman-Developers@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-developers" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-developers</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-developers%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-developers%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Dev-f1731.html" embed="fixTarget[1731]" target="_top" >Mailman - Dev</a></p>tag:www.nabble.com,2006:post-21298805Re: Doubt about security2009-01-05T11:25:17Z2009-01-05T11:25:17ZTerri OdaOn 2009-Jan-5, at 2:03 PM, Barry Warsaw wrote:
<div class='shrinkable-quote'><br>>> I suspect the default should be to not expose those things. I
<br>>> wasn't even
<br>>> aware that list creation through the web was possible. Based on the
<br>>> extremely novice questions I see posted to mailman-users on
<br>>> occasion I
<br>>> suspect many potential Mailman admins are unaware of this as well.
<br>>> I fear
<br>>> those admins are also the ones most likely to not create strong
<br>>> passwords.
<br>> Note that by default, it's not possible to create mailing lists
<br>> through the web even though the link exists. You have to create a
<br>> site password or 'list creators' password to enable this feature. A
<br>> site admin should know enough to set these passwords to something
<br>> strong and difficult to brute force.
<br>> Still, the suggestions for disabling this CGI is easy enough, and if
<br>> you have shell access to create those passwords, you have shell
<br>> access to disable the CGI.
</div><br>This seems like it might be more of a failure in documentation/
<br>understanding than a failure in security. All this information is
<br>readily available (both about the fact that you can create from the
<br>web by default, and the fact that this can be disabled) but obviously
<br>people aren't finding it or don't even know to look for it.
<br><br>I'll try to poke around and figure out where to put it when I get home
<br>from work. I'm guessing we could use some pointers in the install
<br>guides? Or perhaps I should work up a short intro to mailman security
<br>for new users who don't know the likely attack points?
<br><br> Terri
<br><br>_______________________________________________
<br>Mailman-Developers mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21298805&i=0" target="_top" rel="nofollow">Mailman-Developers@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-developers" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-developers</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-developers%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-developers%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-developers/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Dev-f1731.html" embed="fixTarget[1731]" target="_top" >Mailman - Dev</a></p>tag:www.nabble.com,2006:post-21297491Re: repurposing the -request alias on an autogenerated aliases file?2009-01-05T11:24:56Z2009-01-05T11:24:56ZAdam McGreggor-2On Mon, Jan 05, 2009 at 07:22:16PM +0000, Adam McGreggor wrote:
<br>> On Mon, Jan 05, 2009 at 02:10:38PM -0500, Dan Mahoney, System Admin wrote:
<br>> > However, we're using automatic aliases. Is there some way to quell or
<br>> > suppress the creation (or re-creation) of that particular alias (for one
<br>> > list only), without having to go to manual aliases?
<br>>
<br>> Check the order of your (MTA) routers, and add something there? It's what I
<br>> do on a couple of lists, where we wanted to lazily over-ride things.
<br>>
<br>> And check on delivery, using your MTA's diag tools, obviously.
<br><br>/me learns to read...
<br>------------------------------------------------------
<br>Mailman-Users mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21297491&i=0" target="_top" rel="nofollow">Mailman-Users@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-users" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-users</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-users%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-users%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Users-f1729.html" embed="fixTarget[1729]" target="_top" >Mailman - Users</a></p>tag:www.nabble.com,2006:post-21297461Re: repurposing the -request alias on an autogenerated aliases file?2009-01-05T11:22:16Z2009-01-05T11:22:16ZAdam McGreggor-2On Mon, Jan 05, 2009 at 02:10:38PM -0500, Dan Mahoney, System Admin wrote:
<br>> However, we're using automatic aliases. Is there some way to quell or
<br>> suppress the creation (or re-creation) of that particular alias (for one
<br>> list only), without having to go to manual aliases?
<br><br>Check the order of your (MTA) routers, and add something there? It's what I
<br>do on a couple of lists, where we wanted to lazily over-ride things.
<br><br>And check on delivery, using your MTA's diag tools, obviously.
<br><br>--
<br>``Electronic voting is one of those things like unguarded plutonium stores in
<br> Russia: people are only calm about it because they don't know about it. The
<br> rational, informed response would be to run around in circles, howling.''
<br> (Harry Hutton, on the 2004 Venezuelan recall referendum)
<br>------------------------------------------------------
<br>Mailman-Users mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21297461&i=0" target="_top" rel="nofollow">Mailman-Users@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-users" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-users</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-users%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-users%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Users-f1729.html" embed="fixTarget[1729]" target="_top" >Mailman - Users</a></p>tag:www.nabble.com,2006:post-21297456Re: repurposing the -request alias on an autogeneratedaliases file?2009-01-05T11:21:32Z2009-01-05T11:21:32ZMark Sapiro-3Dan Mahoney, System Admin wrote:
<br>>
<br>>That is to say, if I hand-edited both $mailman/data/aliases and aliases.db
<br>>(by rebuilding it from the new aliases file) -- would mailman revert it on
<br>>me the next time I created a list?
<br><br><br>No. It will only revert if you run Mailman's bin/genaliases to
<br>regenerate all the aliases.
<br><br>--
<br>Mark Sapiro <<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21297456&i=0" target="_top" rel="nofollow">mark@...</a>> The highway is for gamblers,
<br>San Francisco Bay Area, California better use your sense - B. Dylan
<br><br>------------------------------------------------------
<br>Mailman-Users mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=21297456&i=1" target="_top" rel="nofollow">Mailman-Users@...</a>
<br><a href="http://mail.python.org/mailman/listinfo/mailman-users" target="_top" rel="nofollow">http://mail.python.org/mailman/listinfo/mailman-users</a><br>Mailman FAQ: <a href="http://wiki.list.org/x/AgA3" target="_top" rel="nofollow">http://wiki.list.org/x/AgA3</a><br>Searchable Archives: <a href="http://www.mail-archive.com/mailman-users%40python.org/" target="_top" rel="nofollow">http://www.mail-archive.com/mailman-users%40python.org/</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com" target="_top" rel="nofollow">http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com</a><br><br>Security Policy: <a href="http://wiki.list.org/x/QIA9" target="_top" rel="nofollow">http://wiki.list.org/x/QIA9</a><br><p>From forum: <a href="http://www.nabble.com/Mailman---Users-f1729.html" embed="fixTarget[1729]" target="_top" >Mailman - Users</a></p>tag:www.nabble.com,2006:post-21297259Re: Mailman 2.x Roadmap2009-01-05T11:12:48Z2009-01-05T11:12:48ZMark Sapiro-3Thijs Kinkhorst wrote:
<div class='shrinkable-quote'><br>>
<br>>On Monday 5 January 2009 17:09, Mark Sapiro wrote:
<br>>> Please don't start (or extend) a list of downstream things to look at
<br>>> in the week before a release. First of all, I'm just compulsive enough
<br>>> to actually look, but even so, the most likely result is I'll be
<br>>> overwhelmed, defer everything and then forget about it.
<br>>
<br>>I have on behalf of Debian a while ago reported a number of our patches to the
<br>>SF.net tracker, which have not seen any response yet. It's not that we're not
<br>>willing to contribute patches back, but the previous approach of reporting
<br>>them to the patch tracker hasn't been fruitful. I have also sent selected
<br>>patches to the development list in the past with the same result.
<br>>So I guessed I'd try something different instead.
</div><br><br>Of the 32 patches under the '"series" style patches'-header: at
<br><a href="http://patch-tracking.debian.net/package/mailman/1:2.1.11-8" target="_top" rel="nofollow">http://patch-tracking.debian.net/package/mailman/1:2.1.11-8</a>, two of
<br>them carry the note "Submitted upstream" with a SF tracker URL and one
<br>notes "Applied upstream"
<br><br>Of the other 29, my first glance indicates at least four of them are
<br>Debian specific, and one is to an unmaintained "contrib" module.
<br><br>Many of the remaining 24 are like
<br><<a href="http://patch-tracking.debian.net/patch/series/view/mailman/1:2.1.11-8/00_stolen_from_HEAD.patch" target="_top" rel="nofollow">http://patch-tracking.debian.net/patch/series/view/mailman/1:2.1.11-8/00_stolen_from_HEAD.patch</a>>
<br>which carries the note: "Handle empty queue files." I see what this
<br>patch does, but I am unable to see why it is necessary. If it were
<br>reported in a tracker (I assume it's in a Debian tracker somewhere,
<br>but why should I have to search for it?), at least I'd have some
<br>information about symptoms and causes that would enable me to evaluate
<br>it.
<br><br>(and at the moment, your entire patch tracking system seems to be not
<br>working since all the URLs which I recorded yesterday throw Python
<br>exceptions at me today