Mailman-Developers September 2002

mailman-developers@python.org

37 participants
123 discussions

Checking if a varible is set inside the MailList class
by Joshua Eichen 23 Sep '02

23 Sep '02

I'm trying to figure out if a varibe is already set inside the mailman class and if not, set it. The cleanest thing I've come up with is self.var_name = getattr(self, var_name, default). Is there a more elegent solution? Joshua -- Bury my heart at Betrand Russellstraat. keyserver: seattle.keyserver.net fingerprint: 363E D1F4 8EC0 DDE3 5DC1 056F E8ED 5163 EE1B 2333

1 0

handling multi-byte characters in templates
by Jason R. Mastaler 22 Sep '02

22 Sep '02

When Mailman.Utils.maketext() does string substitution in a template containing multi-byte characters (such as in templates/ja/), how does it avoid errors during dictionary interpolation? TMDA is using a nearly identical function to make text from templates, but certain multi-byte characters (Japanese in particular) in the templates trigger the following exceptions: ValueError: incomplete format key TypeError: not enough arguments for format string Someone suggested that the Japanese text probably has characters in it that include an ascii % as part of the multi-byte character. I'm wondering how Mailman gets around this problem. -- (http://tmda.net/)

2 4

mailman on OS X 10.2
by Chuq Von Rospach 22 Sep '02

22 Sep '02

I finally had time to install 2.1b3+ on OS X 10.2 Install was fairly straightforward. Here is the script of what I had to do to install. It assumes a generic 10.2 system with a working sendmail. <http://www.chuqui.com/cgi-bin/mwf/topic_show.pl?tid=412> My current mm_cfg.py is here: <http://www.chuqui.com/cgi-bin/mwf/topic_show.pl?tid=413> I'm leaving the beast fairly generic until I figure out how 2.1 works and what I want to tweak.... So far, looks pretty solid. Kewl. (one thing I DO know. I STILL don't like the look of Pipermail. Ohwell... But unlike 2.0.x, it worked out fo the box for me....) -- Chuq Von Rospach, Architech chuqui(a)plaidworks.com -- http://www.chuqui.com/

1 0

[ mailman-Bugs-612784 ] feature-request : Use of Spamassassintag
by noreply＠sourceforge.net 22 Sep '02

22 Sep '02

Bugs item #612784, was opened at 2002-09-22 12:20 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=612784&group_i… Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Alexandre Dulaunoy (adulau) Assigned to: Nobody/Anonymous (nobody) Summary: feature-request : Use of Spamassassintag Initial Comment: Mail::SpamAssassin is adding a tag when He suspects to be a spam. Do you plan to add a test on it and not forward mail into the mailing if the tag is present ? It's also useful when the list is moderated. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=612784&group_i…

1 0

funny error messages in make install for CVS on Mac OS X
by Chuq Von Rospach 22 Sep '02

22 Sep '02

Hey, barry -- starting to play with the CVS on OS X, and I happened to notice some weird errors on install: for p in email-2.3 JapaneseCodecs-1.4.8 KoreanCodecs-2.0.5; \ do \ gunzip -c $p.tar.gz | tar xf -; \ (cd $p ; PYTHONPATH=/usr/local/mailman/pythonlib /usr/bin/python setup.py --quiet install --install-lib /usr/local/mailman/pythonlib --install-purelib /usr/local/mailman/pythonlib --install-data /usr/local/mailman/pythonlib); \ done ld: for architecture i386 ld: warning /usr/lib/bundle1.o cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) ld: warning build/temp.darwin-6.1-Power Macintosh-2.2/_japanese_codecs.o cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) ld: warning /usr/lib/gcc/darwin/3.1/libgcc.a archive's cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (can't load from it) ld: warning /usr/lib/libSystem.dylib cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) ld: for architecture i386 ld: warning /usr/lib/bundle1.o cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) ld: warning build/temp.darwin-6.1-Power Macintosh-2.2/_koco.o cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) ld: warning /usr/lib/gcc/darwin/3.1/libgcc.a archive's cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (can't load from it) ld: warning /usr/lib/libSystem.dylib cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) ld: for architecture i386 ld: warning /usr/lib/bundle1.o cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) ld: warning build/temp.darwin-6.1-Power Macintosh-2.2/hangul.o cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) ld: warning /usr/lib/gcc/darwin/3.1/libgcc.a archive's cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (can't load from it) ld: warning /usr/lib/libSystem.dylib cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) It looks like some of the international character stuff is assuming Wintel architecture in some way that's not obvious from 10 minutes of looking at the source... ideas? -- Chuq Von Rospach, Architech chuqui(a)plaidworks.com -- http://www.chuqui.com/ IMHO: Jargon. Acronym for In My Humble Opinion. Used to flag as an opinion something that is clearly from context an opinion to everyone except the mentally dense. Opinions flagged by IMHO are actually rarely humble. IMHO. (source: third unabridged dictionary of chuqui-isms).

1 0

stupid CVS question...
by Chuq Von Rospach 21 Sep '02

21 Sep '02

Okay, I'm confused. or senile. Or stupid. pick one. Or two. having downloaded 2.1b3, I want to update it to current CVS. Since there aren't CVS nightly tarballs (why not?), I've tried to go in to CVS and do it. And I can't. What's the magic incantation for this? obviously, my CVS hacking is weak.... -- Chuq Von Rospach, Architech chuqui(a)plaidworks.com -- http://www.chuqui.com/ Very funny, Scotty. Now beam my clothes down here, will you?

2 2

[ mailman-Bugs-456080 ] qmail-to-mailman.py & README.QMAIL diff
by noreply＠sourceforge.net 20 Sep '02

20 Sep '02

Bugs item #456080, was opened at 2001-08-28 02:49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=456080&group_i… Category: configuring/installing Group: More Information Needed Status: Closed Resolution: Out of Date Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: qmail-to-mailman.py & README.QMAIL diff Initial Comment: contrib/qmail-to-mailman.py and README.QMAIL differ. a) contrib/qmail-to-mailman.py says: # To configure a virtual domain to connect to mailman, create these files: # # ~mailman/.qmail-default # |preline /usr/bin/python /home/mailman/mail-in.py This should be EITHER: # |preline /path/to/python /path/to/qmail-to-mailman.py OR (not sure about preline!!) # |/path/to/python /path/to/qmail-to-mailman.py The real question: To preline or not to preline? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-09-20 13:40 Message: Logged In: NO preline! You need preline, if you do not have it, then your mbox archives will be broken and hypermail will not archive. preline inserts an mbox-style From line at the head of the message, and hypermail depends on it. See "Q. Still having problems? Running QMail?" in the mailman FAQ. README.QMAIL needs to be fixed. It fooled me... Anyone who is successfully running this without preline apparently has never noticed that they have no hypermail archives! ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-04-05 10:06 Message: Logged In: YES user_id=12800 I don't know anything about qmail, so if there are changes to be made against the MM2.1cvs tree, please attach diffs. In the meantime, I'm closing this bug. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-10-06 05:00 Message: Logged In: NO Not to preline. Running mailman and qmail-to-mailman.py for ages without preline and without problems. ---------------------------------------------------------------------- Comment By: Ralf Hildebrandt (hildeb) Date: 2001-09-20 03:42 Message: Logged In: YES user_id=77128 According to the instructions that apply if you DON'T use qmail-to-mailman.py, I'd say the opposite: You need preline. ---------------------------------------------------------------------- Comment By: Ricardo Kustner (rixhq) Date: 2001-09-09 22:13 Message: Logged In: YES user_id=16263 http://www.qmail.org/man/man1/preline.html I think the info on the manpage should be enough to decide wether or not you need preline... (ie does mailman need the extra headers generated by preline?) As far was I can see we don't need preline... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=456080&group_i…

1 0

[ mailman-Bugs-612174 ] subscribe_policy + ALLOW_OPEN_SUBSCRIBE
by noreply＠sourceforge.net 20 Sep '02

20 Sep '02

Bugs item #612174, was opened at 2002-09-20 15:42 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=612174&group_i… Category: command line scripts Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Jay Luker (lbjay) Assigned to: Nobody/Anonymous (nobody) Summary: subscribe_policy + ALLOW_OPEN_SUBSCRIBE Initial Comment: There is a flaw somewhere in the logic that alters the value of subscribe_policy based on the value of mm_cfg.ALLOW_OPEN_SUBSCRIBE. I have ALLOW_OPEN_SUBSCRIBE = 0. When I attempt to set subscribe_policy = 1 via the config_list script, subscribe_policy is always set to 2. ---------------------------------------------------------------------- >Comment By: Jay Luker (lbjay) Date: 2002-09-20 16:02 Message: Logged In: YES user_id=51347 OK, I was just able to track this down further. The problem (I think) lies in Gui/Privacy.py. _setValue states: "For subscribe_policy when ALLOW_OPEN_SUBSCRIBE is true, we need to add one to the value because the page didn't present an open list as an option." ... but then the subsequent code actually adds one to the value if ALLOW_OPEN_SUBSCRIBE is untrue. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=612174&group_i…

1 0

[ mailman-Bugs-612174 ] subscribe_policy + ALLOW_OPEN_SUBSCRIBE
by noreply＠sourceforge.net 20 Sep '02

20 Sep '02

1 0

Sendmail to Postfix
by Kory Wheatley 19 Sep '02

19 Sep '02

I'm converting over to POSTFIX from Sendmail (well actually I can switch back and forth between the two in RedHat 7.3) and I'm running Mailman 2.0.13 without problems (only problem is with large lists, here I believe Postfix can help me there). Postfix has more tweak options that's why I want to switch. When I make the change to "Postfix" is there anything I need to change on Mailman to make it run with Postfix, in other words will I break anything? -- ######################################### Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him.

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

Mailman-Developers September 2002