Mailman 3 February 2003 - Mailman-Developers

archive html
by greg steele 07 Feb '03

07 Feb '03

ok... I did google and couldn't find any info about this.... Can I edit/re-write the archive pages to match the look/feel of the rest of my site? anyone? bueller? g

3 2

Patching question
by Marilyn Davis 07 Feb '03

07 Feb '03

Hi Mailmen and Mailwomen, If I fix up a patch for 2.1 so that eVote works with it, some administrators will want it and some won't. What happens when new Mailman patches come along for 2.1+? Will I have to make a new patch for each patch? Please forgive my ignorance. Marilyn

1 0

premature closure? (was Weirdness with 2.1)
by Richard Barrett 07 Feb '03

07 Feb '03

At 16:03 06/02/2003, Bryan Fullerton wrote: >On Thursday, February 6, 2003, at 10:45 AM, Bill Bradford wrote: > >>2.1 works fine for me, *except* >> >>When I go to http://mysite/mailman/admindb/<listname>, it asks for the >>list password. I give it, get the "held for moderation/approval" queue >>of messages, pick my choices on each, and hit submit. >> >>I then get the password auth page again, have to do it over, and hit >>submit *again*, then it "takes" and processes the messages per my >>admin choices. > >Are you running Mailman 2.1 and 2.0 lists in the same URI space? If so, >you're hitting bug #664466, which is fixed in CVS (and the bug closed, >so you won't see it if you browse open bugs in SourceForge). > >http://sourceforge.net/tracker/index.php?func=detail&aid=664466&group_id=10… > >Thanks, > >Bryan Am I alone in thinking that closing a bug report should only be done when the numbered release is made that incorporates the fix. Closing the bug when the fix goes into the CVS version only "hides" the existence of fixes for known bugs in the current production (numbered) release. It means that in trying to consider what might be applicable to the latest numbered release effectively all bug fixes, both open and closed have to checked. I would have thought that pending would be a better category for bugs whose fixes are in the CVS but not in the numbered release, with re-categorisation as closed when the fix appears in a numbered release.

1 0

[Mailman-Developers] Try 2: URGENT BREAKAGE: New unicode-related error with CVS
by Dan Mick 06 Feb '03

06 Feb '03

Sent this last night; haven't seen it on the list yet Updated to CVS today, and now I'm seeing these; anyone else? This seems to be stopping all traffic to the list Feb 05 20:17:15 2003 (4633) Uncaught runner exception: ASCII decoding error: ordinal not in range(128) Feb 05 20:17:15 2003 (4633) Traceback (most recent call last): File "/export/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/export/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/export/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/export/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 79, in process send_digests(mlist, mboxfp) File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 120, in send_digests send_i18n_digests(mlist, mboxfp) File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 213, in send_i18n_digests addresses = getaddresses([lheader(msg.get('from', ''), lcset)]) File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 372, in lheader h = make_header(decode_header(s), **kws) File "/export/home/mailman/pythonlib/email/Header.py", line 123, in make_header h.append(s, charset) File "/export/home/mailman/pythonlib/email/Header.py", line 230, in append ustr = unicode(s, incodec) UnicodeError: ASCII decoding error: ordinal not in range(128) Feb 05 20:17:15 2003 (4633) SHUNTING: 1044504218.645468+31ecfd687a04619284497495da50c740cbddf364

3 6

Re: [Mailman-Developers] Weirdness with 2.1
by bryanf＠samurai.com 06 Feb '03

06 Feb '03

> I may have figured it out. Might want to add, to the 2.1 upgrade > instructions, that people need to go to all the computers they use, and > clear the cookies. I had MM2.0 list admin cookies on all of > the systems I use, which was causing the same/similar problem, > even though all the lists were upgraded to 2.1. Yeah, same problem, 2.0.x cookies make 2.1.0 barf. Kinda moot to change the docs for the next release, though - 2.1.1 will have the bug fix that's in CVS now, so this'll no longer be a problem. Bryan

1 0

checkdbs UnicodeError
by Daniel Buchmann 06 Feb '03

06 Feb '03

I was the puzzled receiver of these words this morning: Traceback (most recent call last): File "/home/mailman/cron/checkdbs", line 136, in ? main() File "/home/mailman/cron/checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "/home/mailman/cron/checkdbs", line 123, in pending_requests text = NL.join(pending) UnicodeError: ASCII decoding error: ordinal not in range(128) Anyone else seen this and know how to fix it? Couldn't find anything about this in the SF bug tracker... I'm using the Release_2_1-maint CVS branch. -Daniel

3 4

Weirdness with 2.1
by Bill Bradford 06 Feb '03

06 Feb '03

2.1 works fine for me, *except* When I go to http://mysite/mailman/admindb/<listname>, it asks for the list password. I give it, get the "held for moderation/approval" queue of messages, pick my choices on each, and hit submit. I then get the password auth page again, have to do it over, and hit submit *again*, then it "takes" and processes the messages per my admin choices. I can duplicate this at will using either Mozilla, IE5/6 for Windows, Chimera or Safari on the Mac, so its not a cookies problem, at least not on the client side.. Bill -- bill bradford mrbill(a)mrbill.net austin, texas

2 1

PGP whitelist to skip moderation
by Nicolas Marchildon 05 Feb '03

05 Feb '03

I'm currently the admin of a few Mailman lists. There used to be lots of spam and viruses, so we added Spamassassin to our procmail configuration, which dumps flagged messages to a designed file. Obviously, it does not catch everything, such as messages *totally* unrelated with the list subject comming from lost people, or some viruses/worms. So we decided to moderate the lists. Even subscribers see their posts moderated, because some worms spread by sending messages with a forged sender, which would get through anyway. The traffic of "real" messages is currently below 10 messages per day, so it's quite manageable. However, even though there are 4 moderadors, it can take many hours for a message to get moderated. We would like to be able to let known people post to the list without having their message delivery delayed by the moderation. My proposal is to have Mailman manage a whitelist consisting of PGP keys. Messages signed with a "white" key would skip moderation. Subscribers willing to use this feature would only have to submit their key to a specific PGP key server. When a message that is signed but whose PGP key is not in the whitelist comes in, it would be dropped in the moderation queue. When the moderator looks at the list of messages, he would be given an extra option: "Add key 0x00000000 to whitelist". When submitting the form with this option selected, Mailman would fetch the key from its configured keyserver, and add it to its whitelist. That way, the next message signed with that key would not get moderated. If you change your key (new identity, or because it has expired), you simply have to submit it to the keyserver, and only your "first" message would be moderated. Note that the moderator does not have to verify your new key, his job is only to make sure the content of your mail is appropriate. It's up the each subscriber to get your key, verify it, possibly sign it, and verify the messages you send. Most key servers also have a web interface for adding, updating and searching for keys. A simple link to this web interface from the list info page would be a good-enough integration, in my opinion. I have searched the archives for discussions of PGP and Mailman, and found an interesting post[1] from Phil Stracchino, who describes an "Accept signed posts only" option, but which lacked a good description of how keys would get to the whitelist. My proposal does not allow spammers to automatically add their key and then post their crap, because a first signed message has to be approved by the moderator, who will discover the spam, and reject the message without adding the key to the whitelist. I also found two[2] patches[3] for adding PGP support to Mailman, but only adding *encryption* support, not simple signatures. However, because those two patches have already integrated GnuPG into Mailman, it would be a good base for going further by implementing my idea. I don't know Mailman's code a lot, but I have hacked it a bit recently to add the "approved" header for posting to usenet, and made the same Message-Id appear in both regular mail and usenet deliveries. I am willing to spend some time implementing the feature I described, and I was even contacted by an other person offering help. I found two messages stating we should wait until 2.1 is released, which seems to be done now. I'd like to know the status of the PGP support, mainly to figure out which of the two patches to build on. Is anybody planning to apply an existing patch for adding PGP support? As for those that might ask "why bother implementing this if 95% of the planet don't know what PGP is?" I answer that I know enough people on the list I administer that know how to use PGP, and would actually be very happy if that was implemented :) Thanks for your help, Nicolas Marchildon [1]http://www.mail-archive.com/mailman-developers@python.org/msg05055.html [2] https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645297&group_i… [3] http://www.nah6.com/products/secure-list/ -- OpenPGP public key: http://nicolas.marchildon.net/pubkey.txt Key fingerprint: 5E84 1089 0036 BB63 6997 232C 8FFB 777D 39D4 B2D4 Jabber ID: nicolas(a)marchildon.net http://www.jabber.org What have you done for freedom today? http://www.gnu.org

1 0

New unicode-related error with CVS
by Dan Mick 05 Feb '03

05 Feb '03

Updated to CVS today, and now I'm seeing these; anyone else? Feb 05 20:17:15 2003 (4633) Uncaught runner exception: ASCII decoding error: ordinal not in range(128) Feb 05 20:17:15 2003 (4633) Traceback (most recent call last): File "/export/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/export/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/export/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/export/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 79, in process send_digests(mlist, mboxfp) File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 120, in send_digests send_i18n_digests(mlist, mboxfp) File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 213, in send_i18n_digests addresses = getaddresses([lheader(msg.get('from', ''), lcset)]) File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 372, in lheader h = make_header(decode_header(s), **kws) File "/export/home/mailman/pythonlib/email/Header.py", line 123, in make_header h.append(s, charset) File "/export/home/mailman/pythonlib/email/Header.py", line 230, in append ustr = unicode(s, incodec) UnicodeError: ASCII decoding error: ordinal not in range(128) Feb 05 20:17:15 2003 (4633) SHUNTING: 1044504218.645468+31ecfd687a04619284497495da50c740cbddf364

2 2

Attention Mailman Hosting Sites
by barry＠python.org 05 Feb '03

05 Feb '03

A long while ago, I offered to put up a page listing sites that offered commercial Mailman list hosting services. Sadly, I don't have the time to maintain this or even put it together. However, there is a MoinMoin page (think: Wiki) listing general Python hosting services, of which Mailman is included. I encourage all Mailman hosting facilities to add entries to the page: http://www.python.org/cgi-bin/moinmoin/PythonHosting There is currently only one Mailman hosting site listed. The MoinMoin is on the honor system, and you don't need a password to add content to it. If you do add an entry, be sure to include the word "Mailman" so the page is easy to search. Cheers, -Barry

1 0