Mailman 3 June 1999 - Mailman-Users

Re: [Mailman-Users] Internationalization (was Reply-problems)
by Harald Meland 17 Jun '99

17 Jun '99

[The List Server Administrator at UNH] > I agree that trying to build this into the server would not be > a good idea. But I do think this would be a good thing to add to > the list of "internationalization features" for future version. As Mailman does absolutely _no_ munging of "Re:" subject prefixes today, I don't see why it should try to do anything with language-specific versions of this prefix, either. This is really a _client_ problem. Trying to be smart about these things on the server _will_ backfire. What site- og list-specific message filters will do to messages they get fed (in post-1.0 Mailman), however, is not something Mailman can be held responsible for. So, if someone wants to do something like perl -ple '$_ = "Subject: Re: $3" if m/^subject:\s*((re|sv|ad):\s*)+(.*)/i' they're welcome to do so in a home-made filter (but don't blame Mailman when this filter mangles a messages Subject in a way it shouldn't have done). > My point is, it might be worthwhile to have localization be > configurable on a list-by-list basis since I have seen list > server sites that support both English and Spanish language > lists on the same server. On this I agree completely. -- Harald

1 0

Re: [Mailman-Users] List-in-list inclusions, "mixed" lists
by Harald Meland 17 Jun '99

17 Jun '99

[Trevor Johnson] > Mitch Marks writes: > > > The interesting settings about sending password reminders to "-owner" > > addresses instead of unmodified member addresses seem very useful for > > *completely* umbrella lists, whose members are only other lists. But I > > didn't see a way to selectively mark members one way or the other. Any > > suggestions? Not any really good ones, but here's a try: If list "foobar" has both user and list members, you could make lists "foobar-lists" and "foobar-users", and make their addresses the only members on "foobar". User addresses then go on "foobar-users", and list members on "foobar-lists". "foobar" and "foobar-lists" are pure umbrella lists. All these three lists could be set up to have the same subject prefix. > (Or can this go under "enhancement requests"?) Yes, I for one would like to take the "include additional members from <source>" stuff up for review post-1.0. > Anyone who has access to the Web (probably the great majority of > subscribers) can have their password mailed via the Web form. I'd suggest > just turning off the reminders. This has the problem that anyone could "pretend" to be a list member and have the list's password mailed to the list. > If the password were included in the response to a "help" command, > then there would be no need at all for the reminders. I posted a patch for making the "password" mail command return the users password when given without any arguments. > > Subject: Re: [List 1] [List 2] Re [List 2] [List 1] Re [List 1] > > [List2] The Original Topic > > The way majordomo deals with this is that if the token appears anywhere in > the subject, a new one doesn't get added. ... which happens to be exactly what Mailman does (even though I confess to having messed this up in rc2, see simple patch in <URL:http://www.python.org/pipermail/mailman-users/1999-June/001464.html>). -- Harald

1 0

Different message template per lists
by Herick Moniz 17 Jun '99

17 Jun '99

Hi, I like to know if it is possible to setup Mailman in such a way that the Welcome message as well as the other templates are selected on a per list basis. I need this because I like to have lists that are in french with french instructions and lists in english with english instructions. Thanks, Herick

1 0

help - how can I repair this?
by prospace-jlewis 17 Jun '99

17 Jun '99

Help, I just sent a mailing to a big list (19,000) users. The machine locked up, and on rebooting, this is what I get when using mailman to access the list: Traceback: Traceback (innermost last): File "/home/mailman/scripts/driver", line 112, in run_main main() File "/home/mailman/Mailman/Cgi/admin.py", line 65, in main lst = MailList.MailList(list_name) File "/home/mailman/Mailman/MailList.py", line 60, in __init__ self.Load() File "/home/mailman/Mailman/MailList.py", line 778, in Load raise Errors.MMBadListError, ('Failed to unmarshal config info: ' TypeError: __add__ nor __radd__ defined for these operands What/where should I look to resolve what happened and get things back up and running. The other lists on the machine seem to be doing fine. Mailman 1.0rc2 Linux 6.0 (intel) The list's address is: http://www.prospace.org/mailman/listinfo/prospace-alert Thanks. John Lewis ProSpace volunteer webmaster and mailinglist manager

1 0

Holding subscription requests based on regex
by Richard Ellerbrock 17 Jun '99

17 Jun '99

I have asked this question before, but got no responses. Is it possible to hold a subscription request to a list (via the web or e-mail) based on a regex. I played around with the Hold posts with header value matching a specified regexp But this setting does just that - it catches posts. I do not even want people being able to subscribe to the list under certain circumstances (ie, they do not belong to our domain). A simple solution would be to have posts to list-request addresses also to be affected by the Hold post settings. -- Richard Ellerbrock richarde(a)eskom.co.za

1 0

Re: [Mailman-Users] [Patch itself]
by Harald Meland 16 Jun '99

16 Jun '99

[Bernhard Reiter] > Of course I forgot to attach the patch, to the last mail. Sorry. Thanks for the patch -- but, having tried it out, I really liked the look&feel of the Details better the way they were. I'll try to justify this a bit: When specifying an explicit window target for the details links, I'll only get _one_ specific details window (unless I middle-click on a link to tell my Netscape "ignore the window target for this link, but open it in a new window"). However, if all links are made to be without window targets, I'll either have to go back and forth between details and the admin page (when left-clicking), or I'll get a total clutter of separate details windows (when middle-clicking). As for the "Warning! Don't change this option here!" part of the patch, I think a) the fact it states is pretty obvious, as there is no submit button on the page, and b) it adds unwanted visual clutter to an otherwise beautiful details page ;) [ All of this should probably be a per-admin configurable option -- but we won't have separate admin authentication until after 1.0, so I'd rather leave everything as it is for now. ] Let me know if my reasoning is wrong/stupid/fascist/implying that I'm a control freak :) -- Harald

2 1

Re: [Mailman-Users] Reply-problems
by Harald Meland 16 Jun '99

16 Jun '99

[arety(a)dolphinics.no] > The list is up and running, but some users have strange mailers which > replies with 'Ad: ' or 'SV: ' instead of 'Re: '. Mailman is good in not > adding [listname] on replies, as long they use the 'Re: '. Is there any > way of adding support for 'Ad: ', 'SV: ' or anything like that? I don't think so -- these are the much hated "internationalized" reply subject prefixes some MUA vendors decided their users needed. As there are quite a lot of different languages out there, and as trying to be smart about these prefixes sooner or later will backfire (i.e. someone used a "SV:" prefix to indicate something other than a reply), I believe it best for Mailman to stay out of this snakepit. > I see the same problem when the subject-line is mime-encoded because > some use non-ascii characters (which also is ugly in the archive). Hmmmm.... I think it would be unwise to make Mailman dependent on any MIME-parsing python modules at this time, as the potential for screwups is rather big (and we'd _really_ like to get 1.0 out soon). However, in theory, Mailman could decode these headers before checking whether the list prefix is present. Which means this is yet another post-1.0 improvement to make... -- Harald

2 1

Re: [Mailman-Users] Exception in ScanMessage for MIME messages with missing boundary
by Harald Meland 16 Jun '99

16 Jun '99

[Ian Jackson] > (Is this the right place to report bugs ?) The preferred way of reporting is to use the Mailman Jitterbug interface at <URL:http://www.python.org/mailman-bugs/>. > One of the lists on my system received a bounce with an empty body, > but with Content-Type: multipart/report. When Mailman tried to parse > it it got an exception because it couldn't find the message boundary. Here's a quick patch: Index: Bouncer.py =================================================================== RCS file: /export/public/cvsroot/mailman/Mailman/Bouncer.py,v retrieving revision 1.32 diff -u -r1.32 Bouncer.py --- Bouncer.py 1999/03/10 13:10:14 1.32 +++ Bouncer.py 1999/06/16 18:22:21 @@ -332,7 +332,12 @@ '"[^"]+"')[1][1:-1] if boundry: - relevant_text = string.split(msg.body, '--%s' % boundry)[1] + relevant_text = string.split(msg.body, '--%s' % boundry) + # Invalid MIME messages shouldn't cause exceptions + if len(relevant_text) >= 2: + relevant_text = relevant_text[1] + else: + relevant_text = relevant_text[0] else: # This looks strange, but at least 2 are going to be no-ops. relevant_text = regsub.split(msg.body, -- Harald

1 0

Re: [Mailman-Users] nesting lists
by Harald Meland 16 Jun '99

16 Jun '99

[Dan Busarow] > On Fri, 21 May 1999, Dominic Martinelli wrote: > > However, I ran into one major problem. > > > > I am in the process of trying to migrate a complicated sendmail alias scheme > > to mailman. Currently we have a hierarchy of aliases. For example, a top > > level alias will point to lower level ones. > > > > The problem that I have is that when I nest lists with mailman, if someone > > is on more than one of the bottom level lists, they will get duplicate > > messages. Is there anyway for mailman not to send out duplicates in this case? > > > > Also, it is not possible to not have people on more than one of the lower > > level lists, so making sure that there are not duplicates is not an option. > > Try lowering MAX_SPAWNS (1 should almost certainly work) and/or > raising SMTP_MAX_RCPTS > > You need to let sendmail see the duplicates and sort it out. This won't help, if I understand the problem correctly. If all your "leaf" alias entries point to separate Mailman lists, sendmail will consider each Mailman list a separate destination. Now, if the intersection of the member sets of two Mailman lists aren't always empty, Mailman would have to have some sort of inter-list internal communication to avoid the addresses inside the intersections getting duplicate mail. Currently there are no inter-list communication inside Mailman. There have been some talk of adding support for this for post-1.0 (but I can't remember whether any of the ideas presented was generally agreed upon to be truly good ones). -- Harald

1 0

Re: [Mailman-Users] unknow user
by Harald Meland 16 Jun '99

16 Jun '99

[Jason] > every time i email to my subscribe address that mailman gives me, Are you referring to the "list creation message" that $prefix/bin/newlist mails to the list's administrator? > it comes back unknown user. what am i missing here??? You haven't made your MTA aware of the new addresses that bin/newmail asks the site admin to define (how you define new addresses is haghly MTA dependant, so I can't explain all of that here). If you're using sendmail, adding the aliasfile lines bin/newmail to your /etc/aliases file, and then running "newaliases" should _probably_ suffice -- but it really depends on how your sendmail has been set up. -- Harald

1 0