Mailman 3 March 1999 - Mailman-Users

Re: [Mailman-Users] RFC for List Message Header Fields
by J C Lawrence March 25, 1999

March 25, 1999

On Wed, 24 Mar 1999 10:17:41 -0500 (EST) Darren Henderson<darren(a)jasper.somtel.com> wrote: > Perhaps its just me but I find the use of URL's in the headers > disturbing. Having administered a number of lists which used RFC2369, I've found that many newbie net users rather like them. They're certainly preferable to putting the same data in a .sig. -- J C Lawrence Internet: claw(a)kanga.nu ----------(*) Internet: coder(a)kanga.nu ...Honorary Member of Clan McFud -- Teamer's Avenging Monolith...

1 0

Re: [Mailman-Users] Permissions Problems Subscribing Users
by Terrence Martin March 25, 1999

March 25, 1999

Roger Pe?a Escobio wrote: > > did your mailman subdir are writable for mailman group? > specially the subdir where are data, like archives, lists, logs.... > As far as I can tell I have all of the correct permissions. The mailman user can write to pretty much everything. I was wondering if it was a strange web user/mailman user issue. However as I said before I seem to be able to do everything I need in the admin tool, it is only the subscribe screen for users that fails. > >************************************************************** > >We're sorry, we hit a bug! > > > >If you would like to help us identify the problem, please email a copy of > this > >page to the webmaster for this site with a description of what happened. > >Thanks! > > > >Traceback: > > > > > >Traceback (innermost last): > > File "/var/spool/mailman/scripts/driver", line 102, in run_main > > main() > > File "/var/spool/mailman/Mailman/Cgi/subscribe.py", line 161, in main > > list.AddMember(email, pw, digest, remote) > > File "/var/spool/mailman/Mailman/MailList.py", line 785, in AddMember > > cookie = Pending().new(name, password, digest) > > File "/var/spool/mailman/Mailman/Pending.py", line 74, in new > > self.__save(db) > > File "/var/spool/mailman/Mailman/Pending.py", line 111, in __save > > fp = open(self.db_path, "w") > >IOError: (13, 'Permission denied') > > > > look that it is a write permission!!!! take a look to where self.db_path > variable are pointing... I actually tried to do that but not being completely familiar with python I soon lost where Pending.py was trying to do. I gathered that it might have some to do with the lock files... -rw-rw-rw- 1 mailman mailman 0 Feb 25 09:47 dis.lock -rw-rw-rw- 1 mailman mailman 0 Jan 8 16:33 games.lock -rw-rw-rw- 1 mailman mailman 0 Jan 11 15:25 internet.lock -rw-rw-rw- 1 mailman mailman 0 Feb 19 15:17 mgmt.lock -rw-rw-r-- 1 mailman mailman 74 Feb 21 12:42 mmqueue_run.lock -rw-rw-r-- 1 mailman mailman 0 Jan 21 17:12 mmqueue_run.lock.isacal.cal.montage.ca.18921 -rw-rw-r-- 1 mailman mailman 0 Jan 21 17:42 mmqueue_run.lock.isacal.cal.montage.ca.18998 -rw-rw-rw- 1 mailman mailman 0 Feb 22 14:43 oaug.lock -rw-rw-rw- 1 mailman mailman 0 Feb 19 15:12 oracle.lock -rw-rw-rw- 1 www mailman 72 Mar 24 12:18 pending_subscriptions.lock -rw-rw-rw- 1 mailman mailman 0 Feb 19 13:43 staff.lock -rw-rw-rw- 1 mailman mailman 0 Jan 18 16:54 sysadmin.lock -rw-rw-rw- 1 mailman mailman 0 Mar 24 11:41 test1.lock However as you can see they are all owned and writable by mailman and the dir is SGID mailman. Cheers, Terrence > > > > > > > > > > >Environment variables: > > > > Variable > > Value > > DOCUMENT_ROOT > > /var/spool/mailman/lists > > HTTP_ACCEPT_ENCODING > > gzip > > CONTENT_LENGTH > > 82 > > CONTENT_TYPE > > application/x-www-form-urlencoded > > PATH_TRANSLATED > > /var/spool/mailman/lists/staff > > REMOTE_ADDR > > xx.xx.xx.xx > > GATEWAY_INTERFACE > > CGI/1.1 > > SERVER_PROTOCOL > > HTTP/1.0 > > HTTP_ACCEPT_LANGUAGE > > en > > REMOTE_PORT > > 25115 > > SERVER_PORT > > 80 > > HTTP_CONNECTION > > Keep-Alive > > HTTP_USER_AGENT > > Mozilla/4.5 [en] (X11; U; Linux 2.0.36 i686) > > HTTP_ACCEPT_CHARSET > > iso-8859-1,*,utf-8 > > HTTP_ACCEPT > > image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, > >image/png, */* > > REQUEST_URI > > /mailman/subscribe/staff > > PATH > > /sbin:/usr/sbin:/bin:/usr/bin > > QUERY_STRING > > SCRIPT_FILENAME > > /var/spool/mailman/exec/cgi-bin/subscribe > > PATH_INFO > > /staff > > HTTP_HOST > > some.machine.com > > REQUEST_METHOD > > POST > > SERVER_SIGNATURE > > SCRIPT_NAME > > /mailman/subscribe > > SERVER_ADMIN > > webmaster(a)some.machine.ca > > SERVER_SOFTWARE > > Apache/1.3.3 (Unix) (Red Hat/Linux) > > PYTHONPATH > > /var/spool/mailman > > HTTP_REFERER > > http://some.machine.com/mailman/listinfo/staff > > SERVER_NAME > > some.machine.com > > > > > >---------------------------------- > >E-Mail: twm139(a)its.to > >Date: 24-Mar-99 > >Time: 12:02:40 > > > >This message was sent by XFMail > >---------------------------------- > > > >------------------------------------------------------ > >Mailman-Users maillist - Mailman-Users(a)python.org > >http://www.python.org/mailman/listinfo/mailman-users

1 0

Posting filters not working/Passwords
by John C. Broman, Jr. March 25, 1999

March 25, 1999

I'm still having problems with setting my list to members-only. When I set it to members-only, everyone's messages bounce. This applies to members mass-subscribed when Mailman was installed for me as well as members who joined (and confirmed) after the list was running on Mailman. Here's what I have set: Must posts be approved by an administrator?: No Restrict posting privilege to list members?: Yes Addresses of members accepted for posting to this list without implicit approval requirement: No addresses listed Some other pertainent facts: When my ISP transferred the membership roster from our old MajorDomo server to mailman, they did (I think) a mass subscribe, and they did NOT ask these existing 300 members to confirm. Some of these transferred members are able to request their passwords and they get back a pseudo-random 4 character password. But some members complained they cannot get a password. And when they try to find their password, I (as admin) get a message saying that that member "lacks a password". Perhaps this is causing the posting filter problem. So, I have two questions: 1) What can I do, other that fix the passwords, that will allow me to set my list to "Restrict posting privilege to list members"? 2) How can I assign passwords to already subscribed members? I have no direct access to the machine that Mailman is installed on. Thanks, John Broman List Owner Corvette Restoration and Preservation List (CRPL) > >>bruce(a)perens.com wrote: >>> Rather than remove it, provide a check box to enable/disable it per list >>> in the admin forms, or per user in the user's options. Then everybody >will >>> be happy. >> >>Great. >> > >i think that the passwd option are very important when you set your >user/subscriber option, if you dont have a passwd anybody can change your >option :-( . i am sure that noone want this > >>> I won't give up subscription confirmation for anything, though. Too many >times >>> my lists have been used to maliciously mail-bomb someone. >> >>Now, confirmation I completely agree with. >> >me too > >Thanks > > > >------------------------------------------------------ >Mailman-Users maillist - Mailman-Users(a)python.org >http://www.python.org/mailman/listinfo/mailman-users >

4 5

Subject: Re: [Mailman-Users] Making two "connected" lists
by Ken Manheimer March 24, 1999

March 24, 1999

On Mon, 22 Mar, Greg Connor <gconnor(a)nekodojo.org> wrote: > I would like to make two "connected" lists... The idea is that some users > want to get "announcements only" and other users want "announcements and > discussion". Check out the admin general-options long description for the "umbrella lists" option (search for "umbrella" on a list's general admin options page). If i'm not mistaken, umbrella lists are specifically intended for what you're trying to do. The idea for umbrella lists is to redistribute to other lists - they direct admin messages (password reminders, other notices) to special addresses associated with the subscribing lists, so the passwords don't get advertised to all the members of the subscribing lists. To use an umbrella list for announcements, you'll probably want to have the umbrella announcement list distribute to _two_ other lists - the discussion list, and a subordinate announcements list. Ie: gregs-announcements is an umbrella list with two subordinate lists: gregs-announcements-only - announcements-only members would subscribe to this gregs-discussions - announcements and discussion members would subscribe to this The subscribers would need to understand that announcements should be sent (if anyone can make announcements) to the superior 'gregs-announcements' list, not 'gregs-announcements-only'. Does this make sense? Ken klm(a)digicool.com

1 0

Re: [Mailman-Users] Mailman 1.0b9, password requirement.
by bruce＠perens.com March 24, 1999

March 24, 1999

Oops, don't get confused, I'm not the developer. I only contribute a patch here and there. Bruce

1 0

[Fwd: Re: [JOS] New Working Mail Lists...]
by Clark Evans March 24, 1999

March 24, 1999

I received this from one of my users: > You're not sending Sender: lines, which kills most > filtering and is against RFC822... Sorry that I'm ignorant of the issue, but the headers (sent to me) of the message he was referring follow this text. BTW, Mailman is a *very slick* product. I'm really happy to see it rock on -- it's also my first introduction to Python... which, btw, I think that I'm beginning to like. Thanks again, Clark -------- Original Message -------- Received: from webby.com (localhost [127.0.0.1])by webby.com (8.9.0/(dn)) with ESMTP id AAA14465;Wed, 24 Mar 1999 00:55:09 -0500 (EST) Received: from mailhost.capecod.net (mailhost.capecod.net [204.255.214.21])by webby.com (8.9.0/(dn)) with ESMTP id AAA14379for <general(a)jos.org>; Wed, 24 Mar 1999 00:54:53 -0500 (EST) Received: from manhattanproject.com (IDENT:clark@camb0967.capecod.net [209.244.240.205])by mailhost.capecod.net (8.9.3/8.9.3/Debian/GNU) with ESMTP id AAA11263for <general(a)jos.org>; Wed, 24 Mar 1999 00:51:36 -0500 Sender: clark(a)capecod.net Message-ID: <36F87D13.D75DE4F6(a)manhattanproject.com> Date: Wed, 24 Mar 1999 05:50:11 +0000 From: Clark Evans <clark.evans(a)manhattanproject.com> X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.0.36 i686) X-Accept-Language: en MIME-Version: 1.0 To: general(a)jos.org Subject: [JOS] New Working Mail Lists... Content-Transfer-Encoding: 7bit Sender: general-admin(a)jos.org Errors-To: general-admin(a)jos.org X-Mailman-Version: 1.0b9 Precedence: bulk List-Id: General Discussion List <general.jos.org> X-BeenThere: general(a)jos.org Content-Type: text/plain; charset=us-ascii X-Mozilla-Status: 8001 X-Mozilla-Status2: 00000000 X-UIDL: d5f1d6e528a3c4402cc6f2d545cfdbcf

1 0

Re: [Mailman-Users] Mailman 1.0b9, password requirement.
by bruce＠perens.com March 24, 1999

March 24, 1999

From: Clark Evans <clark.evans(a)manhattanproject.com> > PLEASE consider removing this requirement. Rather than remove it, provide a check box to enable/disable it per list in the admin forms, or per user in the user's options. Then everybody will be happy. I won't give up subscription confirmation for anything, though. Too many times my lists have been used to maliciously mail-bomb someone. Thanks Bruce

2 1

Re: [Mailman-Users] RFC for List Message Header Fields
by bruce＠perens.com March 24, 1999

March 24, 1999

From: Darren Henderson <darren(a)jasper.somtel.com> > Email is not the web the web is not email. Mail is MIME is the web. We are making a mistake by not making more use of MIME. People slap my hand for sending HTML-ized mail. I guess there is someone out there still paying for net service by the KB, but I wish that would be over. Thanks Bruce

3 2

RFC for List Message Header Fields
by The List Server Administrator＠UNH March 24, 1999

March 24, 1999

Folks, I just discovered a new RFC for List Message Header Fields. Here is the form letter for List Managers trying to drum up support for this proposed standard. This idea seems to fit with the list-centric vs. server-centric model that Mailman currently seems to be heading in. However I have seen the *-subscribe and *-unsubscribe aliases before, in LISTSERV which I think of as server-centric. Also, note the use of *-request (in *-archive) as a conduit for commands, rather than feedback for a human. In any case, for what it is worth, here's that letter... Cordially, The List Server Admin list.admin(a)unh.edu (currently Bill Costa) [ http://www.nisto.com/listspec/letter-listmom.txt ] This is a request for you to implement support for the List- header fields defined in RFC2369. This will make mail list access easier for your users. <ftp://nis.nsf.net//internet/documents/rfc/rfc2369.txt> The List- fields provide you with a standard method by which you can consistently describe your mailing lists' command syntax so that client applications can implement an interface to make list access easier for users. As they are adopted and supported by email software developers, the List header fields will make it easier for users to interact with email lists. The currently defined fields are List-Subscribe, List-Unsubscribe, List-Help, List-Post, List-Owner and List-Archive. They describe commands for subscribing, unsubscribing, retrieving help information, posting to the list, contacting a human administrator and accessing message archives. For your list, the fields would appear as: List-Subscribe: <mailto:list-request@server?Body=subscribe%20list> List-Unsubscribe: <mailto:list-request@server?Body=unsubscribe%20list> List-Help: <mailto:list-request@server?Body=help> List-Post: <mailto:list@server> List-Owner: <mailto:listmom@server?Subject=listname> List-Archive: <mailto:list-request@server?Body=archives>, <http://server/list-archive/> Implementation guidelines for list managers and administrators are available at: <http://www.nisto.com/listspec/list-manager-intro.html> Extended details on the List header fields are available from: <http://www.nisto.com/listspec/> A mailing list for discussion is available at: <http://www.nisto.com/listspec/mail> or <mailto:list-header@list.nisto.com?Subject=help> Information on the format of mailto URLs: <ftp://nis.nsf.net//internet/documents/rfc/rfc2368.txt> Thanks! [EOM]

5 6

Permissions Problems Subscribing Users
by twm139＠its.to March 24, 1999

March 24, 1999

I get the following error when users try to subscribe. However all of the admin functions seem to work fine. BTW, where does mailman store the actual e-mail addresses? In the config file? I also tried upgrading to b9 but that really messed things up.:( Note: I have sanitized some of the below message... Thanks in advance for any help. Cheers, Terrence Martin ************************************************************** We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (innermost last): File "/var/spool/mailman/scripts/driver", line 102, in run_main main() File "/var/spool/mailman/Mailman/Cgi/subscribe.py", line 161, in main list.AddMember(email, pw, digest, remote) File "/var/spool/mailman/Mailman/MailList.py", line 785, in AddMember cookie = Pending().new(name, password, digest) File "/var/spool/mailman/Mailman/Pending.py", line 74, in new self.__save(db) File "/var/spool/mailman/Mailman/Pending.py", line 111, in __save fp = open(self.db_path, "w") IOError: (13, 'Permission denied') Environment variables: Variable Value DOCUMENT_ROOT /var/spool/mailman/lists HTTP_ACCEPT_ENCODING gzip CONTENT_LENGTH 82 CONTENT_TYPE application/x-www-form-urlencoded PATH_TRANSLATED /var/spool/mailman/lists/staff REMOTE_ADDR xx.xx.xx.xx GATEWAY_INTERFACE CGI/1.1 SERVER_PROTOCOL HTTP/1.0 HTTP_ACCEPT_LANGUAGE en REMOTE_PORT 25115 SERVER_PORT 80 HTTP_CONNECTION Keep-Alive HTTP_USER_AGENT Mozilla/4.5 [en] (X11; U; Linux 2.0.36 i686) HTTP_ACCEPT_CHARSET iso-8859-1,*,utf-8 HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, image/png, */* REQUEST_URI /mailman/subscribe/staff PATH /sbin:/usr/sbin:/bin:/usr/bin QUERY_STRING SCRIPT_FILENAME /var/spool/mailman/exec/cgi-bin/subscribe PATH_INFO /staff HTTP_HOST some.machine.com REQUEST_METHOD POST SERVER_SIGNATURE SCRIPT_NAME /mailman/subscribe SERVER_ADMIN webmaster(a)some.machine.ca SERVER_SOFTWARE Apache/1.3.3 (Unix) (Red Hat/Linux) PYTHONPATH /var/spool/mailman HTTP_REFERER http://some.machine.com/mailman/listinfo/staff SERVER_NAME some.machine.com ---------------------------------- E-Mail: twm139(a)its.to Date: 24-Mar-99 Time: 12:02:40 This message was sent by XFMail ----------------------------------

1 0