Mailman 3 March 2002 - Mailman-Developers

including archive link - feature?
by Samuele Pedroni 22 Mar '02

22 Mar '02

Hi. I'm just a user on the sending/receiving side of MM lists. I don't know if the following feature is already implemented, and I don't know the innards of the archive mechanism to know whether it can be implemented. I just wonder whether each message sent through a list could optionally contain a web link to the archived post, like http://mail.python.org/pipermail/python-dev/2002-March/021429.html Even if the link does not work immediately but just after a bit of time, it would be valuable, IMHO. regards. PS: please cc, I'm not subscribed to this list.

2 1

2.1b1 bug - getting msg_footer twice
by Alex Yu 22 Mar '02

22 Mar '02

Hi, I just upgraded to 2.1b1 from 2.1 alpha. Every e-mail that gets through list has msg_footer twice. How can I fix this? Alex

2 1

Re: [Mailman-Developers] is it me?
by barry＠zope.com 22 Mar '02

22 Mar '02

>>>>> "BD" == Brett Delmage <brett(a)cfsc.ottawa.on.ca> writes: >> Am I the only stupid guy running mailman cvs on a server with >> many lists? ;-) BD> No, I am using it for 3 low-traffic "internal committee" lists BD> here now. I figure helping test and find the bugs is the least BD> I can do for free software, being as I am not up to coding BD> python yet (I'm an embedded systems C programmer during my day BD> job.) BD> My users don't always appreciate this(!) but as they are and BD> work with volunteers too they understand that they're part of BD> the Mailman team and helping out simply by using the BD> system. As CfSC uses a lot of free software it's the least we BD> can do... Trust me, /I/ appreciate it! It makes Mailman much better software. -Barry

1 0

message is unparsable and lost data files for filebase
by totschnig.michael＠uqam.ca 22 Mar '02

22 Mar '02

Hello, I've got the following two lines in a recent CVS Mailman's error log. Mar 20 13:14:52 2002 (29950) message is unparsable: 1016648091.497946+bac3be516f3338dba5c030fac9372443209a4c6b Mar 20 13:14:52 2002 (29950) lost data files for filebase: 1016648091.497946+bac3be516f3338dba5c030fac9372443209a4c6b Is this something I should worry about? The message it is talking about, is it a mail Mailman should have processed. There is no entry at that time in the post log. Regards, Michael

3 3

How to share Mailman extensions
by Ellen Spertus 22 Mar '02

22 Mar '02

I'm wondering how best to share my Mailman extensions, assuming they're useful to anyone besides me. For now, I've created a project at sourceforge.net (http://sourceforge.net/projects/dsub/) and released a tarball containing the files I've modified or created. The code is pre-alpha at this point. I hope to have an alpha version by the end of this weekend. While I hope my changes will eventually be incorporated into Mailman, the time has clearly not yet arrived. Any advice on whether to start my own branch of the Mailman CVS tree now or to keep hacking separately until when and if my code is incorporated? When I upload the alpha code, I'll also post a design doc and ask for criticism. I've attached my original description of my changes. Ellen FUNCTIONALITY A user of mailing list foo creates a new thread with a base name of bar by sending email to foo-new-bar@host. The system appends an integer to bar to generate a unique thread name, e.g., bar1. All subscribers to mailing list foo receive the first message of any thread. The message headers are: To: foo-bar1@host From: original-sender@wherever If a user chooses reply, the new message goes to the original sender (assuming a decent MUA). It a user chooses reply-all, the new message becomes part of the thread bar1. When subscribing (or subsequently), each user specifies whether they want to be subscribed to new threads by default. If so, the user gets all messages in a new thread (unless they explicitly unsubscribe). If a user chooses NOT to be subscribed to new threads by default, they only get the initial message unless they explicitly subscribe. Each message contains (un)subscribe information both as a URL and mailto to make the operations as lightweight as possible; e.g., To unsubscribe from this conversation, send email to foo-bar1-unsubscribe(a)javamlm.mills.edu or visit http://javamlm.mills.edu/scripts/override?listname=foo&conversation=14&pref…. To unsubscribe from foo, send email to foo-unsubscribe(a)javamlm.mills.edu. Note that thread membership is determined solely by the address to which a message is sent, not the message's subject, references, or other headers. IMPLEMENTATION We implemented threads by including a threadID in each message's metadata, which was stored in a relational database, as was information about each thread, subscription, etc. The following SQL query determines to whom to send a message in thread 37: SELECT email FROM Subscriber WHERE deleted = FALSE AND ((Subscriber.preference = 1 AND NOT EXISTS (SELECT * FROM Override WHERE Override.subscriber_id = Subscriber.subscriber_id AND Override.thread_id = 37 AND Override.preference = 0)) OR (Subscriber.preference = 0 AND EXISTS (SELECT * FROM Override WHERE Override.subscriber_id = Subscriber.subscriber_id AND Override.thread_id = 37 AND Override.preference = 1))) The full schema is in the paper. I'm including the query here to give you an idea of the complexity and to show that list membership is calculated on the fly.

1 0

Mailman has found an unexpected error
by stefano danovaro 22 Mar '02

22 Mar '02

Hello! I've mailman version 2.1b1. I've received this email from mailman Mailman has found an unexpected error in MailCommandHandler.ParseMailCommands(). Here the tracing: Traceback (most recent call last): File "/home/mailman/Mailman/MailCommandHandler.py", line 273, in ParseMailCommands self.__dispatch[cmd](args, line, msg) File "/home/mailman/Mailman/MailCommandHandler.py", line 727, in ProcessConfirmCmd results = self.ProcessConfirmation(args[0], msg) File "/home/mailman/Mailman/MailList.py", line 980, in ProcessConfirmation addr = userdesc.address AttributeError: address Is it a bug o Is it a my error? thanks+, Stefano -------------------------------------------------------------------------------- Stefano Danovaro <danovaro(a)publinet.it> SIR s.r.l. - Soluzioni In Rete Via XX Settembre 3/6 - 16121 GENOVA http://www.publinet.it/ 16121 GENOVA - Italy ________________________________________________________

1 0

Re: [Mailman-Developers] Does anyone have digests working with mailman 2.1b1?
by Dan Mick 21 Mar '02

21 Mar '02

> > Is this just me? Digests are still working on my list.

2 1

bug in the interface ? (new_member_options)
by Fil 20 Mar '02

20 Mar '02

Hi, the new_member_options pane in general settings does not work with my server/browser : I suspect it's because all check boxes have the same name (new_member_options)... -- Fil

1 0

Re: [Mailman-Developers] 2.1b1: admin_member_chunksize handling?
by Dan Mick 19 Mar '02

19 Mar '02

> I liked the old way, where I just get 'n' members of the list at a time > on each page. Yeah, I kinda did too. My ideal would probably be "show me N" with the "search by RE" box at the top.

1 0

2.1b1: admin_member_chunksize handling?
by Harald Koch 19 Mar '02

19 Mar '02

I liked the old way, where I just get 'n' members of the list at a time on each page. Most of my lists have more than chunksize members, but less than 2*chunksize; one has about 5*chunksize. In other words, my lists aren't large enough to require splitting alphabetically; I get many pages with only one or two addresses on them, which makes it harder to step through the whole list. I don't really want to bump 'chunksize' up to the largest possible number, because that *will* make the HTML screens kinda large for browsers like 'links'. The logic seems to be hardcoded in admin.py; is there any chance of restoring the option of simply displaying chunksize members per page? -- Harald Koch <chk(a)pobox.com> "It takes a child to raze a village." -Michael T. Fry

1 0