Mailman 3 February 2002 - Mailman-Developers

wildcards in poster-without-approval
by Jonas Meurer 01 Mar '02

01 Mar '02

Hello, Is it possible to set wildcards in the field 'Addresses of members accepted for postings to this list without implicit approval requirement' in Privacy Options? That every addr from domain xyz.com is allowed to post without approval requirement. If yes, how? *(a)xyz.com or xyz.com or .*(a)xyz.com Thanks Jonas -- We'll try to make different mistakes this time -- Larry Wall

4 5

Error: Invalid value '' for variable: accept_these_nonmembers
by Marc MERLIN 01 Mar '02

01 Mar '02

This is in mailman CVS I've changed GUI/GUIBase.py with the hopes to output a better error: try: val = self._getValidValue(mlist, property, wtype, val) except ValueError: doc.addError(_("Invalid value '"+val+"' for variable: %(property)s"), tag=_('Error: ')) I get the error (without my patch too obviously) only one install. I can't seem to reproduce it on the list install I have on my laptop. Any ideas what's going on? Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f(a)merlins.org for PGP key

2 5

problem with VERP stuffing all the messages in one connection
by Marc MERLIN 28 Feb '02

28 Feb '02

I was hoping to have a crack at a patch today, but I've been too busy converting my whole exim configs to exim 4. When VERP is enabled, mailman apparently sends all the Emails over one SMTP connection. When exim receives more than smtp_accept_queue_per_connection messages in one connection, it spools everything without trying to resend it. That's actually very bad, because list messages then get delayed by 30mn or more (waiting on a queue runner to pick them up, one per one, and you can imagine that it's a lot of queue entries to clean up (# of subscribers x # of messages sent in the last 30mn) I've currently set that to 1000 on one of my test servers, but that's not very scalable. Mailman needs a MAX_RCPT_PER_SMTP setting and close the SMTP connection after sending that many messages, and open up a new one. Or did I miss something obvious? Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f(a)merlins.org for PGP key

1 0

archives in reverse-chronological order
by Kirez Korgan 28 Feb '02

28 Feb '02

greetings, My mailman archives are configged, by default, in chronological order. I need to change them to reverse chronological order. I've gone through many of the source files, all the documentation, and I've inquired a few times on the mailman-users list (one respondent, who has been very helpful and knowledgeable, said his 2.0.8 archives were by default in reverse-chronological order). Nobody can point me to where I can change this setting. I was surprised that there was no toggle switch in the admindb to switch between chrono- or reverse-chronological order for the archives. Could somebody please help me with this? To clarify: I need my archives arranged so that the newest (most recent) messages are accumulating at the top of the archive page, not at the bottom; this is what I mean by reverse-chronological order. Many thanks! Kirez

1 0

Bug in Bouncer.py (was: At least some of my problems...)
by Dan Mick 28 Feb '02

28 Feb '02

Or not. That was the proverbial pickled scarlet fish. Here's a fix to Bouncer.py. I'm divided about the wisdom of including some keywords and not all. I suppose I should at least be consistent, but I know Barry will fix it right anyway. Index: Bouncer.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Bouncer.py,v retrieving revision 2.23 diff -u -r2.23 Bouncer.py --- Bouncer.py 11 Feb 2002 21:05:10 -0000 2.23 +++ Bouncer.py 27 Feb 2002 04:05:51 -0000 @@ -165,8 +165,8 @@ }, mlist=self) subject = _('Bounce action notification') umsg = Message.UserNotification(self.GetOwnerEmail(), - siteowner, subject, - self.preferred_language) + siteowner, subject, text=None, + lang=self.preferred_language) umsg.attach(MIMEText(text)) if isinstance(msg, StringType): umsg.attach(MIMEText(msg)) @@ -222,8 +222,8 @@ notice = _(e.notice()) # Currently we always craft bounces as MIME messages. bmsg = Message.UserNotification(msg.get_sender(), - self.GetOwnerEmail(), - subject, self.preferred_language) + self.GetOwnerEmail(), subject, + text=None, lang=self.preferred_language) bmsg['Content-Type'] = 'multipart/mixed' bmsg['MIME-Version'] = '1.0' txt = MIMEText(notice, All Rejected messages and "bounce-disable" messages were getting corrupted. > ....with messages that get corrupted in an I18N-ish way, are due > to the fact that I'd written a Handler module to reject messages > held for ImplicitDestination reasons (because I was tired of them). > > Um...but I didn't I18N-ize it. > > Oops. > > Sorry Ben, and thanks for the help. :) > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers(a)python.org > http://mail.python.org/mailman/listinfo/mailman-developers

2 1

Error: Invalid value for variable: ban_list
by Ben Gertzfield 28 Feb '02

28 Feb '02

Using Mailman CVS, I get the following error whenever trying to change any privacy options for a newly-created list via the admin interface: Error: Invalid value for variable: ban_list But I don't have anything in my ban_list, it's completely empty. If I put a value into the ban_list (foo(a)bar.com) then I can set my preferences correctly. Ben -- Brought to you by the letters L and B and the number 17. "I choose YOU! Pikachu!" Debian GNU/Linux maintainer of Gimp and Nethack -- http://www.debian.org/

2 1

Pipermail replacement? Zest!
by barry＠zope.com 28 Feb '02

28 Feb '02

The just completed Python conference was quite enjoyable and inspiring as usual. One of the coolest things demoed was Ka-Ping's new archiving project, which he's named Zest. I'm excited that Zest could one day provide a replacement for Pipermail, so I encourage interested parties to check out Ping's work and join the Zest list. -Barry

6 21

Bug in current authentication
by Dan Mick 28 Feb '02

28 Feb '02

A non-member can visit the listinfo page, enter an email address, and get sent to a "member options" page...but there are no options, really, for him to deal with. He can also hit the "Password reminder" button once he gets there, and get a response that a password is being mailed...but of course that can't happen, since he's not a member. options.py has this code: # Sanity check the user, but be careful about leaking membership # information when we're using private rosters. if not mlist.isMember(user) and mlist.private_roster == 0: # Avoid cross-site scripting attacks safeuser = cgi.escape(user) add_error_message(doc, _('No such member: %(safeuser)s.')) loginpage(mlist, doc, None, cgidata) print doc.Format() return but that misses the case of if not mlist.isMember(user) and mlist.private_roster == 1: which is my case. Why is that second check there?

2 1

Re: [Mailman-Developers] Protecting email addresses from spam harvesters
by Dan Mick 28 Feb '02

28 Feb '02

> On Tue, Feb 26, 2002 at 05:07:41PM -0800, Marc MERLIN wrote: > > Not that it is a big deal to me, but out of curiosity: what part of mailman > > cares that it's a list and not a mail alias? > > The *user*, when the list machinery breaks completely, and there's no > obvious target address to complain to. While this might be a good point, it's wrong and unhelpful to Marc's question. IIRC, Marc, there's a bunch of stuff that does things like "get the Owner address for the list named mm_cfg.<site-list-name>". Not that that couldn't be found and changed, but...that's how it works currently. Also, that way bounce handling happens for those sorts of notification messages in the "normal" way.

3 2

Re: [Mailman-Developers] Protecting email addresses from spam harvesters
by Dan Mick 27 Feb '02

27 Feb '02

> I guess we'll have to agree to disagree, here. The user is the most > important part of any system (or we wouldn't go so far out of our way > to coddle them), and they are the only part affected by this. > > Does the fact that you don't consider the user "part of mailman" mean > that you don't think it's important that they have a way to contact the > server admin when everything breaks? Oh, get off your hobby horse. My comments were completely limited to Marc's specific question. I'm not interested in the other head-of-a-pin conversations you're having, and god be with you on those.

1 0