Mailman 3 January 2000 - Mailman-Users

Re: [Mailman-Users] Posting-Filter is broken in 1.1 !?
by J C Lawrence 06 Jan '00

06 Jan '00

On Mon, 3 Jan 2000 10:30:03 +0100 Aaron Optimizer Digulla <digulla(a)hepe.com> wrote: > I have reported these bugs several *months* ago and still got no > feedback about them :-( Is anyone ever fixing bugs ? > Ok, here they are again: > 1. Some posts are held no matter if the poster is subscribed or in > the posters list (this is a different bug than #2 !!). I suspect that you still have MailMan configured to authenticate by envelope address and that that address is not in your membership list or authorised_poster list. > 2. Some posts are held because Mailman uses the "Sender:" header > item added by Netscape (Mailman should ignore it). MailMan pays no attention to the Sender: header. It does by default read the message envelope and does ignore the From: header however, > 3. When I have a list with the policy "Only subscribed posters can > post" set to "Yes" and I set this option to "No", then all posts > must be approved manually ! No one can post anymore :-( Set "Must posts be approved by an administrator?" to "No" in Privacy Options. -- J C Lawrence Home: claw(a)kanga.nu ----------(*) Other: coder(a)kanga.nu --=| A man is as sane as he is dangerous to his environment |=--

3 2

(no subject)
by amenmok＠allof.econ.cuhk.edu.hk 06 Jan '00

06 Jan '00

unscribe kfwong

1 0

How can I set an account to install mailman?
by James Tsang 06 Jan '00

06 Jan '00

Dear all, sorry for I'm newer in this field. How can I set my account to install mailman (or other application). Rgds

1 0

Making an user unable to post
by Jean-Yves 06 Jan '00

06 Jan '00

Hi, I'm looking for a the thing which can disable de post function for user. Is there a simple button to say :'this user can't post to the list', and mail him a small text ? Thx -- Jean-Yves LAMOUREUX Administrateur systeme / developpeur Hangover SARL ( http://www.hangover.fr )

1 0

quoted text in KFM Html-Widget
by pf＠artcom-gmbh.de 06 Jan '00

06 Jan '00

Hi! Some people here use the KFM as Web Browser (that is the file manager belonging to the Linux K Desktop Environmenti aka KDE). Although this works fine most of the time, the HTML generated by Mailman looks ugly, if it comes to passages of quoted text: They all end up as one continuous line causing a very long horizontal scrollbar to appear. Although this might be a bug in the HTML widget of KFM, for the time being I've applied the following (dirty) patch to mailman: --- freeware/mailman-1.1/Mailman/Archiver/HyperArch.py Sat Aug 21 07:13:23 1999 +++ /home/mailman/Mailman/Archiver/HyperArch.py Tue Jan 4 09:24:54 2000 @@ -944,7 +944,7 @@ else: quoted = quoted.end(0) prefix=CGIescape(L[:quoted]) + '' - suffix='' + suffix='' if self.SHOWHTML: suffix=suffix+' ' if not last_line_was_quoted: I've have noticed no negative side effects when viewing these pages using other browsers like netscape. Regards, Peter -- Peter Funk, Oldenburger Str.86, 27777 Ganderkesee, Tel: 04222 9502 70, Fax: -60

1 0

Umlauts in Subject and Text (üöä ...)
by pf＠artcom-gmbh.de 06 Jan '00

06 Jan '00

Hi. I've installed mailman 1.1 for internal use in our company and I'm very happy with it so far. But the generated HTML in the archives could be improved. If someone writes mail using german language, text and subject of the mail may contain some umlauts like 'ä', 'ö', and so on. These often end quoted printable in the mail archive and so the subject may look like this in the generated HTML: Re: Ist das jetzt =?iso-8859-1?Q?nachtr=E4glich=20=E4nderbar?= I've had a look at standard library module 'quopri' but did not want to start hacking on it before asking here, whether this topic will already be addressed by someone else in an upcoming version of mailman. Regards, Peter -- Peter Funk, Oldenburger Str.86, 27777 Ganderkesee, Tel: 04222 9502 70, Fax: -60

1 0

Removing Message Archives
by Christopher Conner 05 Jan '00

05 Jan '00

Somehow I got a message dated Dec 30, 2000, now I have an archive for December 2000. Can anyone tell me how to stop it from recreating the archive for December 2000? I've removed the December 2000 archive file and edited the html and it keeps recreating it. Also I set mailman so that when it creates the archive it uses the date "When resent" and not "When sent." Is there any reason why I should end up with an archive for December 2000?

2 1

Fwd: Subscription bomb tracing - feature request.
by Christopher Schulte 05 Jan '00

05 Jan '00

This was sent to bugtraq, and I figured it'd be of interest to you guys in case you don't subscribe to it. Does mailman already have the ability to trace such fraudulent subscribe requests and such? Comments? --------chris >Approved-By: aleph1(a)SECURITYFOCUS.COM >Delivered-To: bugtraq(a)lists.securityfocus.com >Delivered-To: BUGTRAQ(a)SECURITYFOCUS.COM >X-Sender: alanb(a)mailhost.manawatu.net.nz >Date: Tue, 4 Jan 2000 15:15:22 +1300 >Reply-To: Alan Brown <alan(a)MANAWATU.GEN.NZ> >Sender: Bugtraq List <BUGTRAQ(a)SECURITYFOCUS.COM> >From: Alan Brown <alan(a)MANAWATU.GEN.NZ> >Subject: Subscription bomb tracing - feature request. >X-To: BUGTRAQ(a)SECURITYFOCUS.COM >To: BUGTRAQ(a)SECURITYFOCUS.COM > >There have been quite a few subscribe bombs tossed around recently. > >While it's nice to see that most mailing list admins use confirm >requests now, it would be a great help if the confirm requests contained >at least the headers of the original request, to aid victims in tracing >their attacker(s). > >One attack recently notified to ORBS attempted to sign the victim up to >26,000 different lists via insecure email relays. > >The confirmation requests alone constituted a fairly substantial denial >of service attack, as did the huge number of bounces the victim got. > >I've only ever seen one mailing list which actually showed where the >signup request came from. Times are still changing and adding an audit >trail would make life easier all round. > >AB

4 4

Re: [Mailman-Users] Archives Not Found!
by J C Lawrence 05 Jan '00

05 Jan '00

On Tue, 4 Jan 2000 12:39:32 -0500 (EST) Pete Holsberg <pjh(a)mccc.edu> wrote: > Whoops! 1) All of a sudden, none of the archives ofmy many > mailing list can be found! I get: > The requested URL /pipermail/[LISTNAME]/ was not found on this > server. Are the appropriate stanzas still in your web server (probably Apache) configs? > 2) Also, the membership of one list has disappeared entirely! Any > way of recovering? What do you see if you do: $ strings ~mailman/lists/<listname>/config.db ? -- J C Lawrence Internet: claw(a)kanga.nu ----------(*) Internet: coder(a)kanga.nu ...Honorary Member of Clan McFud -- Teamer's Avenging Monolith...

3 3

virtual domains (a less stupid question, I hope)
by William R. Dickson 05 Jan '00

05 Jan '00

Okay, now that I've solved a relay restriction issue and Mailman seems to be running quite happily, I'm going to try and get it to handle virtual domains. I can see two approaches to this; I'd like to bounce them off the list and see if anybody has tried them and had any success, or if someone's doing something that works better. First, a bit on the environment: Mailman will be running on a dedicated box (papaya). Incoming mail is actually handled by another box (oak). Oak has the virtual use table for handling virtual domains; mail coming in for lists will be redirected to papaya. There's a strong probability that people will want identical list names now and then. So let's figure two domains, foo.com and bar.org, and each of those domains wants a list named "help-desk". Method 1: one mailman installation (Note: I don't think this one is going to work after all, because it depends on being able to manually configure the list's complete return address rather than just the domain. Still, I'll present it in case anybody's got something along similar lines working.) name the lists after the complete list address: help-desk(a)foo.com help-desk(a)bar.org On oak, have the following VUT entries: help-desk(a)foo.com help-desk-foo.com@papaya help-desk(a)bar.org help-desk-bar.org@papaya On papaya, have the following aliases: help-desk-foo.com: "|/usr/local/mailman/mail/wrapper post help-desk(a)foo.com" help-desk-foo.com-admin: "|/usr/local/mailman/mail/wrapper mailowner help-desk(a)foo.com" Well, you get the idea. Option 2: multiple Mailman installations Install one copy of mailman per virtual domain in a uniquely-named folder. Configure virtual domains for Apache to provide access to the various interface forms. Set up aliases something like this: help-desk-foo.com: "|/usr/local/mailman/foo.com/mail/wrapper post help-desk" help-desk-bar.org: "|/usr/local/mailman/bar.org/mail/wrapper post help-desk" etc... The latter looks much more likely to me now that I look at it. Any comments? Thanks, -Bill -- William R. Dickson -- Consuming the Earth's limited resources since 1968 wrd(a)awenet.com < > http://www.awenet.com/~wrd/ < > ICQ: 14117523 I've had a perfectly wonderful evening. But this wasn't it. -Groucho Marx

2 1