Mailman 3 January 2002 - Mailman-Developers

Postfix tuning
by Bob Puff＠NLE 26 Jan '02

26 Jan '02

Last night, a couple of my bigger lists had really big digests go out... It flooded my ==1mb connection for a good 20 minutes solid. During this, bounce replies had a hard time coming back. Actually, most everything had a hard time, except the delivery. I do see a lot of timeout messages in the delivery, so I'm wondering if I'm just initiating too many smtp sessions for my own good. Ideally, I'd like to throttle back the bandwidth of the -sending- of mailman messages to something like 512k or something, so my connection is still worth something while messages are being sent. I've seen messages related to using bandwidth control programs, but I really want to just slow down (a little) the deliveries, while keeping the server always open for incoming messages. Any pointers on Postfix tuning for such? Bob

1 0

Another Easy Suggestion
by Marc Perkel 25 Jan '02

25 Jan '02

With the setting SMTP_MAX_RCPTS - I'd like to be able to set a default value - and be able to set this individually per list. That way a list with 20,000 names can have different performance characteristics than a list with 500 names.

1 0

USE_ENVELOPE_SENDER is not flexible enough
by Jason R. Mastaler 24 Jan '02

24 Jan '02

For members-only lists like this one, USE_ENVELOPE_SENDER currently allows the admin to determine membership by checking either the From: header, OR the envelope sender address. I think a more flexible alternative would be to first check the envelope sender, and then the From: header for a match. In fact, this would make sense as the default setting IMHO. Why am I interested in this? Because I like to post to public mailing lists and newsgroups with a 'dated' address that expires after a set period of time to thwart SPAM harvesters. Obviously I can't use these one-time addresses on closed lists, but I could get around this by posting with an envelope sender address that matches my subscription address, and a 'dated' address in my From: header. The closed list would be happy, and I would be happy. -- (TMDA (http://tmda.sourceforge.net/) (UCE intrusion prevention in Python)

1 0

Mailman CVS works on OS X!
by Ben Gertzfield 24 Jan '02

24 Jan '02

Just wanted to report that Mailman out of CVS works beautifully with Python 2.1.1 from the Fink porting project for OS X. I was able to compile and install Mailman after creating a "mailman" user and group in NetInfo. The configure process had a few snags where it was confused about the local hostname (I was not on a network at the time) but it continued on, and built and installed no problem. OS X comes with Apache, so I simply changed /etc/httpd/httpd.conf for the Mailman entries, ran /usr/local/mailman/bin/mailmanctl start, and was off and running. Love that portable code! Ben -- Brought to you by the letters I and C and the number 1. "Frungy! Frungy! Frungy!!" Debian GNU/Linux maintainer of Gimp and Nethack -- http://www.debian.org/

6 9

RE: [Mailman-Developers] pipermail - threading with subjects
by Stuart Donaldson 24 Jan '02

24 Jan '02

The solution my mods implement, basically fixes pipermail to work as it looks like was intended. If no message ID based threading is available when archiveing (ie: no In-Reply-To:/References: headers), then thread the message after the oldest message with the same subject. This has the benefit of grouping messages with the same subject together, but allows the entire thread list to continue to be sorted by date. You also continue to get indentation under the oldest message in the thread. I prefer the overall date sorting of the threadlist because you can go to the end and see recent threads. Unfortunately, we get very little message-Id based threading on our internal mailing list, because of our Exchange server stripping out the information. -Stuart- -----Original Message----- From: Bob Puff@NLE [mailto:bob@nleaudio.com] Sent: Wednesday, January 23, 2002 7:12 PM To: Stuart Donaldson Cc: 'mailman-developers(a)python.org' Subject: Re: [Mailman-Developers] pipermail - threading with subjects I submitted to Barry a few mods to pipermail's archives, one being the order of messages shown in Thread mode. It really bothered me that messages without the message ID got put in a totally different area of the thread list. My solution was to alphabetize the thread list, which is listed in date order. So at least all the threads of a given subject are together, as long as the subject line remains constant. Bob

1 0

pipermail - threading with subjects
by Stuart Donaldson 24 Jan '02

24 Jan '02

I have found a bug and possible fix for threading by subject not working as a fallback if In-Reply-To and References headers are missing. What's the status, and who is the maintainer of pipermail? ie: To whom should I address further inquiries, or should they go directly to the list? I posted a problem on the mailman-users list I had with threading not working with Outlook. It turns out that Outlook/Exchange are not passing through the In-Reply-To: header. On inspecting code in pipermail.py, it appears that if there is no In-Reply-To: header, that it should fall-back to threading to the earliest matching subject. However the code in pipermail to implement this is broken. In particular, there appear to be a few problems: 1) HyperDatabase.HyperDatabase class getOldestArticle() method looks like it expects self.subjectIndex.set_location() to return a value which it does not. I think it should rather be using the return value of self.subjectIndex.next(). 2) subjectIndex.DumbBTree class implementation of set_location(subject) expects an exact match on the subject, however the key to that data is actually a tuple (subject, date, msgid) 3) The parsing of the key in getOldestArticle() looks like it is expecting a single string for the key, rather than a tuple, so once the previous two problems have been addressed it still fails to parse the string. I have fixed this problem for myself, but the state of the database classes looks like it might be in flux. There is also the BSDDBdatabase class which does not seem to be used, and may be either obsolete, or something coming. It also looks to have the same problem. Thanks... Stuart Donaldson Alerton Technologies Inc.

2 1

import MySQLdb in the mailman........
by �� 23 Jan '02

23 Jan '02

Hi, .. I'm a new member in the mailman-developers mailing list... i've one question, although I can not english well.. ^^; hum.. i have tried to update(?) the mailman... One day, i tired to use mailman with mysql dbtabase... but i couldn't import MySQLdb.. ---------error --------- Traceback (innermost last): File "/home/mailman/scripts/driver", line 90, in run_main pkg = __import__('Mailman.Cgi', globals(), locals(), [scriptname]) File "../Mailman/Cgi/admin.py", line 20, in ? import MySQLdb ImportError: No module named MySQLdb -------------------------------- what i cann't understand is the command("import MySQLdb") is good in the python command line... -------no error ------------------------- >>import MySQLdb >> --------------------------------- Please, give me a solution.....T.T

2 1

"there were errors" when there are none
by Fil 23 Jan '02

23 Jan '02

Hi, there's an annoying thing with Mailman's responses to the requests messages. I usually set the maximum number of commands to be processed to 1. But that still gives me errors where there are none, but just too much text. I explain: when they confirm a message, people usually send the "confirm" cookie, with some text appended and their signature. As a result they get an error message, although their confirmation went fine. > There were errors processing your commands...../..... > (snip) > > ***** confirm fc2ef3874aa2c00e344ef20a86e2257d5bd4fd23 > Réussi (Succeeded) > >>>>> Taille maximale d'une ligne de commande (1) atteinte, reste i... I think they should just receive something more positive. -- Fil

1 0

Problem to admin login
by Rodolfo Pilas 23 Jan '02

23 Jan '02

I have just installed MM from CVS, and I have a problem to login into admin interface. Bug in Mailman version 2.1a4+ Traceback: Traceback (most recent call last): File "/usr/lib/mailman/scripts/driver", line 86, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 116, in main elif cgidata.has_key('request_login') and parsedqs: UnboundLocalError: local variable 'parsedqs' referenced before assignment Python information: Variable Value sys.version 2.2 (#2, Dec 27 2001, 18:10:31) [GCC 2.95.3 20010315 (SuSE)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Pls, tell me what I can do. -- Rodolfo Pilas Quien los puso a estos tipos donde estan, rodolfo(a)linux.org.uy Quien los deja seguir en su lugar, http://rodolfo.pilas.net Quien los baja ahora de su altar, ICQ #17461636 Quien les paga para que hagan lo que haran http://xtralinux.org -=# Apocalipsis Now % Cuarteto de Nos #=- Public GnuPG key: http://www.keyserver.net 1024D/57153363 2001-06-02 key fingerprint = DAAE 3246 3F7D A420 B7A0 48A5 D120 C773 5715 3363

2 2

extend.py examples
by Ellen Spertus 22 Jan '02

22 Jan '02

Does anyone have an extend.py file that I can see to get an idea of the functionality? Ellen

2 1