From alann at ihs.com  Thu Apr  1 00:04:00 1999
From: alann at ihs.com (Alan Neiman)
Date: Wed, 31 Mar 1999 15:04:00 -0700 (MST)
Subject: [Mailman-Users] changing defaults
Message-ID: <199903312205.PAA25085@dns1.ihs.com>

I understand that.  The other 10 changes I made work, it's just this one that 
doesn't.  

Alan


> Date: Wed, 31 Mar 1999 13:39:08 -0800
> From: Greg Stein <gstein at lyra.org>
> MIME-Version: 1.0
> To: Alan Neiman <alann at ihs.com>
> CC: mailman-users at python.org
> Subject: Re: [Mailman-Users] changing defaults
> Content-Transfer-Encoding: 7bit
> 
> Alan Neiman wrote:
> > 
> > I have found the "defaults.py" and the "mm_cfg.py" files, and I've been able to
> > change almost all the defaults we want to.  I do have a problem with the
> > archives.  We would like it turned off, and can't get that part working.  I have
> > added/changed the following line in both files, but the lists are still being
> > created with archives turned on.
> 
> the defaults are used at list creation time to populate the new lists'
> configuration. The system doesn't defer back to the original defaults,
> so you'll need to adjust each of your current lists to turn off
> archiving.
> 
> Cheers,
> -g
> 
> --
> Greg Stein, http://www.lyra.org/



Alan Neiman
alan.neiman at ihs.com
Unix System Administrator
Information Handling Services
--------------------------------------------------------------

               ** 1997 & 1998 World Champions **

17 & 2 -- Simply The Best -- The Broncos -- The Denver Broncos

               ** 1997 & 1998 World Champions **

--------------------------------------------------------------




From gstein at lyra.org  Thu Apr  1 00:05:58 1999
From: gstein at lyra.org (Greg Stein)
Date: Wed, 31 Mar 1999 14:05:58 -0800
Subject: [Mailman-Users] Mailman questions (moderation capabilities, m ostly)
References: <613145F79272D211914B0020AFF640190BEE06@gandalf.digicool.com>
Message-ID: <37029C46.49245CB1@lyra.org>

Well, beat me with a wet noodle! That's cool as hell.

-g

Ken Manheimer wrote:
> 
> Greg Stein was on the mark on most of the items, but i think he may have
> been mistaken on one of them.  He wrote:
> 
> > RDB wrote:
> 
> > > 8. It would be great if the list software didn't fail to recognize a
> user
> > > just because the machine name directly following the @ in their
> e-mail
> > > address was added, deleted, or changed.  Does MailMan handle this
> gracefully?
> >
> > I don't think it handles this.
> 
> If i understand the question, i think it does.  Mailman does something
> it calls "smart matching" for addresses comparisons when checking for
> membership and metoo matches, etc.  This  involves accepting as matches
> addresses that agree in the account name and all but the most qualified
> component of the host name part - the "machine name directly following
> the @".  Actually, if i recall correctly, the rules are a bit more
> elaborate than that, but not much...
> 
> Ken Manheimer
> klm at digicool.com

--
Greg Stein, http://www.lyra.org/



From johnr at eecs.berkeley.edu  Thu Apr  1 04:27:20 1999
From: johnr at eecs.berkeley.edu (John Reekie)
Date: Wed, 31 Mar 1999 18:27:20 -0800
Subject: [Mailman-Users] changing defaults
In-Reply-To: <370295FC.49B91395@lyra.org>
Message-ID: <002b01be7be7$2baa3770$663e2080@eecs.berkeley.edu>

On a related subject, I need to write a script
that creates a set of mail lists, and then sets
them up with different configuration values. I have
tried calling the 'admin.py' script in Mailman.Cgi
but cannot figure out how to run it. I apologize for
asking such a dumb (I know Python not...) question,
but how do I invoke these and what format would the
arguments be in?

Or is this the wrong way to do this? I would rather
call existing code if I can.

Thanks!

JohnR

> -----Original Message-----
> From: gstein at lyra.org [mailto:gstein at lyra.org]
> Sent: Wednesday, March 31, 1999 1:39 PM
> To: Alan Neiman
> Cc: mailman-users at python.org
> Subject: Re: [Mailman-Users] changing defaults
> 
> 
> Alan Neiman wrote:
> > 
> > I have found the "defaults.py" and the "mm_cfg.py" files, 
> and I've been able to
> > change almost all the defaults we want to.  I do have a 
> problem with the
> > archives.  We would like it turned off, and can't get that 
> part working.  I have
> > added/changed the following line in both files, but the 
> lists are still being
> > created with archives turned on.
> 
> the defaults are used at list creation time to populate the new lists'
> configuration. The system doesn't defer back to the original defaults,
> so you'll need to adjust each of your current lists to turn off
> archiving.
> 
> Cheers,
> -g
> 
> --
> Greg Stein, http://www.lyra.org/
> 
> ------------------------------------------------------
> Mailman-Users maillist  -  Mailman-Users at python.org
> http://www.python.org/mailman/listinfo/mailman-users
> 
> 



From bwarsaw at cnri.reston.va.us  Thu Apr  1 06:00:48 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Wed, 31 Mar 1999 23:00:48 -0500 (EST)
Subject: [Mailman-Users] changing defaults
References: <199903312115.OAA24261@dns1.ihs.com>
Message-ID: <14082.61296.648749.516835@anthem.cnri.reston.va.us>

>>>>> "AN" == Alan Neiman <alann at ihs.com> writes:

    AN> I have found the "defaults.py" and the "mm_cfg.py" files, and
    AN> I've been able to change almost all the defaults we want to.
    AN> I do have a problem with the archives.  We would like it
    AN> turned off, and can't get that part working.  I have
    AN> added/changed the following line in both files, but the lists
    AN> are still being created with archives turned on.

    AN> ARCHIVE_TO_MBOX = -1

What's probably happening is that it /seems/ as if archiving is turned 
on because that's what's displayed on the Web pages.  However, setting 
ARCHIVE_TO_MBOX in mm_cfg should effectively disable archiving.  If
I'm reading the code correctly, the attribute `archive' on the
MailList object is what's displayed in the "Archive Messages?" value.

If this is false, then when a message reaches MailList.Post(),
Archiver.ArchiveMail() is never called.  Once in .ArchiveMail(),
ARCHIVE_TO_MBOX further short circuits archiving.

Here's some pseudo code to explain what you could write to change
this:

for listname in mymailinglists:
    mlist = MailList(listname)
    mlist.archive = 0
    mlist.Save()

Hope that helps.
-Barry



From bwarsaw at cnri.reston.va.us  Thu Apr  1 06:04:18 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Wed, 31 Mar 1999 23:04:18 -0500 (EST)
Subject: [Mailman-Users] changing defaults
References: <370295FC.49B91395@lyra.org>
	<002b01be7be7$2baa3770$663e2080@eecs.berkeley.edu>
Message-ID: <14082.61506.570357.604110@anthem.cnri.reston.va.us>

>>>>> "JR" == John Reekie <johnr at eecs.berkeley.edu> writes:

    JR> On a related subject, I need to write a script that creates a
    JR> set of mail lists, and then sets them up with different
    JR> configuration values. I have tried calling the 'admin.py'
    JR> script in Mailman.Cgi but cannot figure out how to run it. I
    JR> apologize for asking such a dumb (I know Python not...)
    JR> question, but how do I invoke these and what format would the
    JR> arguments be in?

    JR> Or is this the wrong way to do this? I would rather call
    JR> existing code if I can.

I wouldn't call the scripts in Mailman/Cgi since they're primarily
designed to be called from the wrapper script.  Instead, study the
code in the command line scripts in bin -- you'll have to know a bit
of Python to do this, but it shouldn't be hard to figure out.

-Barry




From baranyai at elfiz2.kee.hu  Thu Apr  1 08:49:24 1999
From: baranyai at elfiz2.kee.hu (Baranyai Laszlo)
Date: Thu, 1 Apr 1999 08:49:24 +0200 (CEST)
Subject: [Mailman-Users] XYZ-owner@other.machine
In-Reply-To: <199904010604.BAA04873@python.org>
Message-ID: <Pine.LNX.3.96.990401084107.15939A-100000@elfiz2.kee.hu>

Hi,

could you tell me, how can I send letters to the correct address instead
of "somebody-owner at somewhere"? I use mailing lists with "elfiz2.kee.hu" 
and "phd.hu" names [mailman 1.08b]. Members from other servers are not
available sometimes(?). Members were registrated "bulk" on admin page
and listinfo page (by themselves). I have no problem with most of them
only one or two seems to have incorrect options. What can be wrong?

Regards,
Laszlo Baranyai

___________________________________________________________________________
Association of Hungarian PhD Students   University of Horticulture & Food
H1146 Budapest, Ajtosi Durer sor 19-21  Department of Physics & Control
http://www.phd.hu                       H1118 Budapest, Somloi u. 14-16.
dosz at phd.hu, iroda at phd.hu               T.: (+36-1)-372-6200/6020




From gstein at lyra.org  Thu Apr  1 10:12:56 1999
From: gstein at lyra.org (Greg Stein)
Date: Thu, 01 Apr 1999 00:12:56 -0800
Subject: [Mailman-Users] XYZ-owner@other.machine
References: <Pine.LNX.3.96.990401084107.15939A-100000@elfiz2.kee.hu>
Message-ID: <37032A88.5667A65C@lyra.org>

Baranyai Laszlo wrote:
> 
> Hi,
> 
> could you tell me, how can I send letters to the correct address instead
> of "somebody-owner at somewhere"? I use mailing lists with "elfiz2.kee.hu"
> and "phd.hu" names [mailman 1.08b]. Members from other servers are not
> available sometimes(?). Members were registrated "bulk" on admin page
> and listinfo page (by themselves). I have no problem with most of them
> only one or two seems to have incorrect options. What can be wrong?

I am sorry, but I cannot understand what problem you are seeing. I think
it is your English translation, so please try to explain your problem
with a little more detail. I will try to use simpler English in my
email.

In the first sentence you ask how to send letters to "the correct
address". What do you mean? Are you sending the letter to an address
that is not working? Can you give an example of an address that you have
tried, but does not work for you?

I do not understand the meaning of "elfiz2.kee.hu" and "phd.hu". How do
those names relate to the problem that you are seeing.

You say that one or two have incorrect options. What is happening with
those addresses?

Regards,
-g

--
Greg Stein, http://www.lyra.org/



From Janos.Zana at elfiz2.kee.hu  Thu Apr  1 09:50:29 1999
From: Janos.Zana at elfiz2.kee.hu (Janos.Zana at elfiz2.kee.hu)
Date: Thu, 1 Apr 1999 09:50:29 +0200 (CEST)
Subject: [Mailman-Users] XYZ-owner@other.machine
In-Reply-To: <37032A88.5667A65C@lyra.org>
Message-ID: <Pine.LNX.3.96.990401093938.8526B-100000@elfiz2.kee.hu>

On Thu, 1 Apr 1999, Greg Stein wrote:

->Baranyai Laszlo wrote:
->> could you tell me, how can I send letters to the correct address instead
->> of "somebody-owner at somewhere"? I use mailing lists with "elfiz2.kee.hu"
->> and "phd.hu" names [mailman 1.08b]. Members from other servers are not
->
->In the first sentence you ask how to send letters to "the correct
->address". What do you mean? Are you sending the letter to an address
->that is not working? Can you give an example of an address that you have
->tried, but does not work for you?
->
->I do not understand the meaning of "elfiz2.kee.hu" and "phd.hu". How do
->those names relate to the problem that you are seeing.
->
There are two different things.
1. We have virtual hosts. The 'elfiz2.kee.hu' and 'www.phd.hu' are the
same machines. Virtualized by the apache configuration.

2. When I made lists by myself, the mailman created the wrong username.
E.g. I entered 'jzana at hoya.kee.hu' as mailman admin, I found on the list
my E-Mail-address in this form: 'jzana-owner at hoya.kee.hu'!!!

This error occured only when I used OTHER hostnames in the
E-Mail-addresses than our OWN hostname.              Janos Zana

- - -   Good rest to all that keeps the Jungle Law!  (Kipling)  - - -




From baranyai at elfiz2.kee.hu  Thu Apr  1 10:03:31 1999
From: baranyai at elfiz2.kee.hu (Baranyai Laszlo)
Date: Thu, 1 Apr 1999 10:03:31 +0200 (CEST)
Subject: [Mailman-Users] Re: XYZ-owner@other.machine
In-Reply-To: <37032A88.5667A65C@lyra.org>
Message-ID: <Pine.LNX.3.96.990401093533.1552B-100000@elfiz2.kee.hu>

Thank you for your quick answer.

On Thu, 1 Apr 1999, Greg Stein wrote:

> it is your English translation, so please try to explain your problem
> with a little more detail. I will try to use simpler English in my
> email.

Wow. Sorry. There is Mailman 1.08b installed on a Linux (Debian) server.
It has more lists (and I am the administrator of two lists named
"kee-phd at elfiz2.kee.hu" and "dosz-mernok at phd.hu"). Members were registered
in "bulk" section of admin page when the lists started. They use several
domains, like "*@hoya.kee.hu" , "*@liliom.kee.hu" , "*@yahoo.com" , etc.
According to the delivery report mailman tries to send reminders to
"XYZ-owner at hoya.kee.hu" for example. It is so strange because there were
no problems with traffic before (you have to know that these lists are
young - 1-2 month old ). Of course these are not valid e-mail addresses.

In addition, mailman sent reminders to the members of 
"teszt at elfiz2.kee.hu" (it is not my list) with the same style. Error
messages have all important information, group ID as well. Members of
"teszt at elfiz2.kee.hu" had the ID of "<dosz-mernok at phd.hu>".

It seems chaos is to reveal itself...

> I do not understand the meaning of "elfiz2.kee.hu" and "phd.hu". How do
> those names relate to the problem that you are seeing.

The name "phd.hu" covers a virtual host at "elfiz2.kee.hu". Both have
mailing lists.

Any suggestion would be appreciated.

Best Regards,
Laszlo Baranyai




From gstein at lyra.org  Thu Apr  1 11:17:18 1999
From: gstein at lyra.org (Greg Stein)
Date: Thu, 01 Apr 1999 01:17:18 -0800
Subject: [Mailman-Users] Re: XYZ-owner@other.machine
References: <Pine.LNX.3.96.990401093533.1552B-100000@elfiz2.kee.hu>
Message-ID: <3703399E.1F22BF68@lyra.org>

Baranyai Laszlo wrote:
>...
> Wow. Sorry. There is Mailman 1.08b installed on a Linux (Debian) server.
> It has more lists (and I am the administrator of two lists named
> "kee-phd at elfiz2.kee.hu" and "dosz-mernok at phd.hu"). Members were registered
> in "bulk" section of admin page when the lists started. They use several
> domains, like "*@hoya.kee.hu" , "*@liliom.kee.hu" , "*@yahoo.com" , etc.
> According to the delivery report mailman tries to send reminders to
> "XYZ-owner at hoya.kee.hu" for example. It is so strange because there were
> no problems with traffic before (you have to know that these lists are
> young - 1-2 month old ). Of course these are not valid e-mail addresses.

Ah. This sounds like a configuration error. Please go to the "General
Options" page in your administration page. There is an option that
reads:

"Send password reminders to, eg, "-owner" address instead of directly to
user."

It sounds like that option has been set to "yes". You should set the
option to "no".

If that is not the problem, then I am confused :-). Please check your
configuration and let us know if this is the problem.

Thanks,
-g

--
Greg Stein, http://www.lyra.org/



From baranyai at elfiz2.kee.hu  Thu Apr  1 15:17:20 1999
From: baranyai at elfiz2.kee.hu (Baranyai Laszlo)
Date: Thu, 1 Apr 1999 15:17:20 +0200 (CEST)
Subject: [Mailman-Users] Re.2: XYZ-owner@other.machine
In-Reply-To: <3703399E.1F22BF68@lyra.org>
Message-ID: <Pine.LNX.3.96.990401151109.2365A-100000@elfiz2.kee.hu>


On Thu, 1 Apr 1999, Greg Stein wrote:

> "Send password reminders to, eg, "-owner" address instead of directly to
> user."
> 
> It sounds like that option has been set to "yes". You should set the
> option to "no".
 
It was set to "no".

The next field is the suffix for "umbrella list". It contains "-owner"
text. Should I delete it?

Best Regards,
Laszlo Baranyai




From soneill at cen.com  Thu Apr  1 20:55:09 1999
From: soneill at cen.com (Sean O'Neill)
Date: Thu, 1 Apr 1999 13:55:09 -0500
Subject: [Mailman-Users] [Q]: Mailman Archive Text Searching Capabilites?
Message-ID: <001b01be7c71$2b244ae0$d933f2cc@sean>

Is there any way to provide HTML forms based searching capabilities to a
mailing lists user community?  We have mailman running but my users want to
be able to search the archives for text within the messages.

Any and all help appreciated.

---------------------------------
Sean O'Neill
AppNet, Inc.
Century Computing Division
301-953-3330
soneill at cen.com
soneill at centurycomputing.com




From allen at chesapeake.tokheim.com  Thu Apr  1 22:36:41 1999
From: allen at chesapeake.tokheim.com (Marc L. Allen)
Date: Thu, 01 Apr 1999 15:36:41 -0500
Subject: [Mailman-Users] Misc. Mailman questions
Message-ID: <3703D8D9.E6F2EDED@chesapeake.tokheim.com>

Hello,

I just recently installed Mailman under Linux and I've got a few
questions.  Some have to do with features that may not exist.  If so,
please let me know.  Thanks.

1) I notice that when someone sends an HTML message (via Netscape, for
instance) that the resulting message contains the list header, followed
by the MIME attachment, and the list footer.  Under Netscape, at least,
it only displays the MIME attachment.  Is that a Netscape problem or a
problem in Mailman with handling HTML messages?

2) Is there a way where I can automatically restrict subscribers to a
subnet or domain name?  I want to use the list internally to my company,
but there's nothing to keep an outside person from subscribing, unless
someone moderates every subscribe request.

3) Is there a way to restrict attachments?  I did see something about
this on the archives, but there wasn't any answer given.  I guess not,
then, eh?

4) I'd like for a user to be able to disable the automatic monthly
password reminder.  Is there some way to do that?

Thanks,

Marc

-- 
************************************************************************
* Marc L. Allen                         *                              *
* Principal Architect                   * "If we had told you it was   *
* Information Technology Manager        * impossible, you'd never have *
*                                       * gone off and done it."       *
* Tokheim Technology Center             *                              *
* (757) 366-4185                        *    -- The Phantom Tollbooth  *
* allen at chesapeake.tokheim.com          *                              *
************************************************************************



From jerodd at noah.dhs.org  Fri Apr  2 04:30:11 1999
From: jerodd at noah.dhs.org (Joshua E. Rodd)
Date: Thu, 01 Apr 1999 21:30:11 -0500
Subject: [Mailman-Users] Pointers to using mailman with exim
Message-ID: <37042BB3.BD24ED65@noah.dhs.org>

Hello,

I'm trying to use mailman with exim. What I don't understand is how
to route mail from exim to mailman. I tried adding aliases to send
mail from mylistname and mylistname-request to mailman, but that
just ended up in /var/spool/mail/mailman getting appended. What am
I missing?

Is there some sort of background process that needs to run?

FYI, this is on a Debian potato system, with the latest everything,
including the latest exim and mailman.

Cheers,
Joshua.



From claw at varesearch.com  Fri Apr  2 04:54:12 1999
From: claw at varesearch.com (J C Lawrence)
Date: Thu, 01 Apr 1999 18:54:12 -0800
Subject: [Mailman-Users] Pointers to using mailman with exim 
In-Reply-To: Message from "Joshua E. Rodd" <jerodd@noah.dhs.org> 
   of "Thu, 01 Apr 1999 21:30:11 EST." <37042BB3.BD24ED65@noah.dhs.org> 
Message-ID: <E10Su61-0001RY-00@under.varesearch.com>

On Thu, 01 Apr 1999 21:30:11 -0500 
Joshua E Rodd <jerodd at noah.dhs.org> wrote:

> Hello, I'm trying to use mailman with exim. What I don't
> understand is how to route mail from exim to mailman. I tried
> adding aliases to send mail from mylistname and mylistname-request
> to mailman, but that just ended up in /var/spool/mail/mailman
> getting appended. What am I missing?

You need two stanzas in your exim config for running mailman under
exim.  They are required so that the UID and GID are set
appropriately for delivering mail to mailman, and to read the
appropriate aliases file for mailman.  

First you need a transport:

  mailman_list_pipe:
    driver = pipe
    allow_commands = /home/mailman/mail/wrapper
    user = mailman
    group = mail
    return_fail_output

Then you need a director:

  mailman_lists:
    driver = aliasfile
    search_type = lsearch
    file = /home/mailman/data/aliases
    pipe_transport = mailman_list_pipe
                
Note that I keep all my mailman specific aliases in
/home/mailman/data/aliases rather than /etc/aliases.

-- 
J C Lawrence                              Internet: claw at kanga.nu
---------(*)                        Internet: claw at varesearch.com
...Honorary Member of Clan McFud -- Teamer's Avenging Monolith...



From jerodd at noah.dhs.org  Fri Apr  2 06:26:13 1999
From: jerodd at noah.dhs.org (Joshua E. Rodd)
Date: Thu, 01 Apr 1999 23:26:13 -0500
Subject: [Mailman-Users] Re: Pointers to using mailman with exim
Message-ID: <370446E5.14F384F9@noah.dhs.org>

J C Lawrence wrote:
> You need two stanzas in your exim config for running mailman under
> exim.  They are required so that the UID and GID are set
> appropriately for delivering mail to mailman, and to read the
> appropriate aliases file for mailman.

I'm afraid I don't understand where those stanzas go. I tried tacking
them onto the end of /etc/exim.conf, but that flat out didn't work.

exim(8) was unhelpful, and I can't find anything in mailman about
using it with exim. Once I get it to work, I think I'll write
a README.exim file for mailman. =)

Cheers,
Joshua.



From bbum at codefab.com  Fri Apr  2 09:21:36 1999
From: bbum at codefab.com (Bill Bumgarner)
Date: Fri, 2 Apr 1999 02:21:36 -0500 (EST)
Subject: [Mailman-Users] Stupid Admin Trick: lost a password
Message-ID: <Pine.SO4.4.03.9904020219130.5326-100000@oz.codefab.com>

I'm a list admin on a box for which I also admin the mailman installation.

Given that, I lost an admin password and want to recover it.

Is there a way to do so and how?

I imagine that this is probably a fairly common question asked by remote
admins... i'm embarassed that I'm wheel on the machine and lost my own
damned list password.

b.bum




From gstein at lyra.org  Fri Apr  2 11:54:02 1999
From: gstein at lyra.org (Greg Stein)
Date: Fri, 02 Apr 1999 01:54:02 -0800
Subject: [Mailman-Users] Stupid Admin Trick: lost a password
References: <Pine.SO4.4.03.9904020219130.5326-100000@oz.codefab.com>
Message-ID: <370493BA.7B3D043B@lyra.org>

Bill Bumgarner wrote:
> 
> I'm a list admin on a box for which I also admin the mailman installation.
> 
> Given that, I lost an admin password and want to recover it.
> 
> Is there a way to do so and how?
> 
> I imagine that this is probably a fairly common question asked by remote
> admins... i'm embarassed that I'm wheel on the machine and lost my own
> damned list password.

You can use the site administrative password to reset any list admin
password. Just enter the site password for the "old password" and then
enter your new password choice.

If you forgot the *site* password, then you must log onto the machine
and use the "mmsitepass" script to reset it.

Cheers,
-g

--
Greg Stein, http://www.lyra.org/



From klm at digicool.com  Fri Apr  2 17:35:05 1999
From: klm at digicool.com (Ken Manheimer)
Date: Fri, 2 Apr 1999 10:35:05 -0500 
Subject: [Mailman-Users] [Q]: Mailman Archive Text Searching Capabilit
	es?
Message-ID: <613145F79272D211914B0020AFF640190BEE14@gandalf.digicool.com>

Sean O'Neill writes:

> Is there any way to provide HTML forms based searching capabilities to
a
> mailing lists user community?  We have mailman running but my users
want to
> be able to search the archives for text within the messages.

The built-in pipermail archives provide no such facility.  If you want
it, you're either going to have to hack the pipermail code to add this
feature - not trivial - or hook up with another archival mechanism.  I
know of some people who use MHonarc, and i understand hypermail is again
actively maintained, and i believe both can be hooked up via a regular
list subscription.  (If they respect the X-no-archive header, then
password reminders and so forth won't get archived, besides.)  For that
matter, if your lists are public you could even subscribe one of the
public maillist archive services, like egroups.com or reference.com....

> Sean O'Neill
> AppNet, Inc.
> Century Computing Division

(Hmm - century computing - barry's old stomping grounds!
Interesting...)

Ken Manheimer
klm at digicool.com



From gazoo at idirect.com  Fri Apr  2 17:15:56 1999
From: gazoo at idirect.com (Mike Garside)
Date: Fri, 2 Apr 1999 10:15:56 -0500
Subject: [Mailman-Users] List roster not found.
Message-ID: <005801be7d1b$b8f670a0$3d069ad8@win>

I have setup Mailman on my Debian GNU/Linux box and receive the following
error message in html when checking the subscriber list. "List roster not
found"  I am using the default list setups that are generated when using the
newlist command.  I am also using version 1.0b8-3 of mailman that came with
the "slink" distribution of Debian.
The weird part is that everything else seems to work fine, I can do updates
from admin, post to the list, view archives etc etc, I can even view the
subscriber list once or twice after creating a new list.  It then gives me
this error???

Any ideas?

Mike




From gorgo at caesar.elte.hu  Fri Apr  2 21:05:14 1999
From: gorgo at caesar.elte.hu (Gergely Madarasz)
Date: Fri, 2 Apr 1999 21:05:14 +0200 (METDST)
Subject: [Mailman-Users] List roster not found.
In-Reply-To: <005801be7d1b$b8f670a0$3d069ad8@win>
Message-ID: <Pine.A32.3.96.990402210400.13087B-100000@caesar.power.elte.hu>

On Fri, 2 Apr 1999, Mike Garside wrote:

> I have setup Mailman on my Debian GNU/Linux box and receive the following
> error message in html when checking the subscriber list. "List roster not
> found"  I am using the default list setups that are generated when using the
> newlist command.  I am also using version 1.0b8-3 of mailman that came with
> the "slink" distribution of Debian.
> The weird part is that everything else seems to work fine, I can do updates
> from admin, post to the list, view archives etc etc, I can even view the
> subscriber list once or twice after creating a new list.  It then gives me
> this error???

So you say it works sometimes and does not work in some other cases ?
What URL does it access then ? And where did you get there from? I have
tried 1.0b8-3 and it seems to work fine here...

-- 
Madarasz Gergely           gorgo at caesar.elte.hu         gorgo at linux.rulez.org
      It's practically impossible to look at a penguin and feel angry.
          Egy pingvinre gyakorlatilag lehetetlen haragosan nezni.
                    HuLUG: http://mlf.linux.rulez.org/




From lindsey at ncsa.uiuc.edu  Fri Apr  2 21:20:22 1999
From: lindsey at ncsa.uiuc.edu (Christopher Lindsey)
Date: Fri, 2 Apr 1999 13:20:22 -0600 (CST)
Subject: [Mailman-Users] Misc. Mailman questions
In-Reply-To: <3703D8D9.E6F2EDED@chesapeake.tokheim.com> from "Marc L. Allen" at Apr 1, 99 03:36:41 pm
Message-ID: <199904021920.NAA17492@ferret.ncsa.uiuc.edu>

A non-text attachment was scrubbed...
Name: not available
Type: text
Size: 3407 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-users/attachments/19990402/ea86ecb1/attachment.pot 

From jerodd at noah.dhs.org  Fri Apr  2 21:21:48 1999
From: jerodd at noah.dhs.org (Joshua E. Rodd)
Date: Fri, 02 Apr 1999 14:21:48 -0500
Subject: [Mailman-Users] Configuration of MTA
Message-ID: <370518CC.2ABD8B0F@noah.dhs.org>

If there is anyone who is using mailman with Exim, could
they please mail me their /etc/exim.conf file? I've been
trying to get it to work, and been quite unsuccessful. I've
read the Exim manual, and while I've learned quite a bit
more about Exim, I still don't understand the whole ``deliverer''
thing.

Cheers,
Joshua.



From bwarsaw at cnri.reston.va.us  Fri Apr  2 22:04:57 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Fri, 2 Apr 1999 15:04:57 -0500 (EST)
Subject: [Mailman-Users] "No module named pythonlib"
References: <Pine.GSO.4.05.9903161847490.5506-100000@opus.nextel.no>
Message-ID: <14085.8937.130945.465627@anthem.cnri.reston.va.us>

>>>>> "TH" == Tor Houghton <th at nextel.no> writes:

    TH> The Cron daemon reports the following for the mailman user:

    TH> Traceback (innermost last):
    |   File "/home/mailman/cron/gate_news", line 27, in ?
    |     from Mailman import MailList
    |   File "/home/mailman/Mailman/MailList.py", line 33, in ?
    |   File "/home/mailman/Mailman/ListAdmin.py", line 28, in ?
    |   File "/home/mailman/Mailman/Message.py", line 31, in ?
    TH> ImportError: No module named pythonlib

    TH> (Had I noticed this earlier, I would have included it in my
    TH> previous mail.)

Sean O'Neill had the same problem.  What version of Mailman are you
using?  Is there a /home/mailman/Mailman/pythonlib/__init__.py file?
If not, is there an __init__.py file in the source you unpacked?

-Barry



From claw at varesearch.com  Fri Apr  2 22:20:02 1999
From: claw at varesearch.com (J C Lawrence)
Date: Fri, 02 Apr 1999 12:20:02 -0800
Subject: [Mailman-Users] Re: Pointers to using mailman with exim 
In-Reply-To: Message from "Joshua E. Rodd" <jerodd@noah.dhs.org> 
   of "Thu, 01 Apr 1999 23:26:13 EST." <370446E5.14F384F9@noah.dhs.org> 
Message-ID: <E10TAQ6-000249-00@under.varesearch.com>

On Thu, 01 Apr 1999 23:26:13 -0500 
Joshua E Rodd <jerodd at noah.dhs.org> wrote:

> J C Lawrence wrote:
>> You need two stanzas in your exim config for running mailman
>> under exim.  They are required so that the UID and GID are set
>> appropriately for delivering mail to mailman, and to read the
>> appropriate aliases file for mailman.

> I'm afraid I don't understand where those stanzas go. I tried
> tacking them onto the end of /etc/exim.conf, but that flat out
> didn't work.

Quite.

As I wrote, the first stanza goes in your transports section, and
the second in your directors section.  See your Exim documentation
(not the man pages) or http://www.exim.org/ for further details.

> Once I get it to work, I think I'll write a README.exim file for
> mailman. =)

What I wrote is pretty well all you need.

-- 
J C Lawrence                              Internet: claw at kanga.nu
---------(*)                        Internet: claw at varesearch.com
...Honorary Member of Clan McFud -- Teamer's Avenging Monolith...



From gazoo at idirect.com  Fri Apr  2 22:34:45 1999
From: gazoo at idirect.com (Mike Garside)
Date: Fri, 2 Apr 1999 15:34:45 -0500
Subject: [Mailman-Users] Upgrading Mailman in Debian?
Message-ID: <002701be7d48$461437c0$6c069ad8@win>

Upgrading prior versions of Mailman i.e. 1.0b8-3 to 1.0b10-1 .  Is it as
simple as entering a command such as dpkg -i mailman-1.0b10-1 to upgrade the
program files or do I have to back things up and go from there?

Also how stable is mailman 1.0b10-1 ?  Should I just stay with my current
version?

Mike




From bwarsaw at cnri.reston.va.us  Fri Apr  2 22:56:26 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Fri, 2 Apr 1999 15:56:26 -0500 (EST)
Subject: [Mailman-Users] Usenet gating and archiving
Message-ID: <14085.12026.294121.877453@anthem.cnri.reston.va.us>

Is anybody currently gating Usenet to a mailing list, /and/ doing
archiving with the default Pipermail?  If so, you may not have noticed
that the archives are pretty broken; nothing that originates on Usenet
will show up in the archive.

I believe I understand why this is happening, and although I don't
have a fix yet, it shouldn't be too difficult.  I should be able to
get it into 1.0b11.  The problem occurs because Pipermail uses
Python's mailbox.UnixMailbox objects which expect "From " separators.
Message that originate on Usenet don't have these envelopes.  The
patch should be to simply synthesize these on messages gated off the
newsgroup.

However, there's a more severe breakage.  You've actually lost
information that is hard to reproduce because the flat listname.mbox
files don't have the separators in them either.  Running bin/arch over 
the file will give you even more corrupt archives (the incremental
archiver just throws the Usenet messages away; bin/arch will tack them 
onto the last email-originated message).

What you could do is to trek through the listname.mbox file looking
for Newsgroup: headers (which appear, but I don't think are
guaranteed, to be the first header in the message).  When you find
one, you jam in a synthesized "From " envelope.

I would rather not add this hack to Mailman unless a lot of people
would benefit from it.  For the test lists that I'm running, we're
willing to just trash the archives and start over; the lists aren't
live anyway.  I'd like to know who would be really adversely affected
by this problem.

Thanks,
-Barry




From gorgo at caesar.elte.hu  Fri Apr  2 23:44:15 1999
From: gorgo at caesar.elte.hu (Gergely Madarasz)
Date: Fri, 2 Apr 1999 23:44:15 +0200 (METDST)
Subject: [Mailman-Users] Upgrading Mailman in Debian?
In-Reply-To: <002701be7d48$461437c0$6c069ad8@win>
Message-ID: <Pine.A32.3.96.990402233537.43354C-100000@caesar.power.elte.hu>

On Fri, 2 Apr 1999, Mike Garside wrote:

> Upgrading prior versions of Mailman i.e. 1.0b8-3 to 1.0b10-1 .  Is it as
> simple as entering a command such as dpkg -i mailman-1.0b10-1 to upgrade the
> program files or do I have to back things up and go from there?

I have tested it (before uploading) on a mail server with around 1 million
deliveries / month... it worked nicely. There is one thing though in
1.0b10... the options.html template has changed, but the postinst script
warns you about it, and tells what you should do. 

> Also how stable is mailman 1.0b10-1 ?  Should I just stay with my current
> version?

In a mail severay days ago Barry said there were still several issues, so
we should wait for b11... so if b8 works for you so far, you could wait a
few more days...

-- 
Madarasz Gergely           gorgo at caesar.elte.hu         gorgo at linux.rulez.org
      It's practically impossible to look at a penguin and feel angry.
          Egy pingvinre gyakorlatilag lehetetlen haragosan nezni.
                    HuLUG: http://mlf.linux.rulez.org/




From bwarsaw at cnri.reston.va.us  Fri Apr  2 23:55:58 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Fri, 2 Apr 1999 16:55:58 -0500 (EST)
Subject: [Mailman-Users] Upgrading Mailman in Debian?
References: <002701be7d48$461437c0$6c069ad8@win>
	<Pine.A32.3.96.990402233537.43354C-100000@caesar.power.elte.hu>
Message-ID: <14085.15598.634738.30690@anthem.cnri.reston.va.us>

>>>>> "GM" == Gergely Madarasz <gorgo at caesar.elte.hu> writes:

    GM> In a mail severay days ago Barry said there were still several
    GM> issues, so we should wait for b11... so if b8 works for you so
    GM> far, you could wait a few more days...

1.0b11 will either be released in the next few minutes, or tomorrow
morning.  I would suggest waiting and not upgrading to b10.

-Barry



From bwarsaw at cnri.reston.va.us  Sat Apr  3 18:36:33 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Sat, 3 Apr 1999 11:36:33 -0500 (EST)
Subject: [Mailman-Users] Release 1.0b11
Message-ID: <14086.17297.485997.392346@anthem.cnri.reston.va.us>

Okay folks, 1.0b11 is now available at www.list.org.  This is
basically a bug fix release addressing problems with case-preserving
addresses and archiving of Usenet gated newsgroups.  For you hardcore
debugging types, there's a new script called bin/withlist which you
can run like so:

% cd ~mailman
% python -i bin/withlist mylist
Loading list: mylist (unlocked)
>>> m.members
{'bwarsaw at cnri.reston.va.us': 0}
>>> 

withlist leaves you with a global variable `m' which is the MailList
object you opened.  Give withlist and optional second argument if you
want the list to be locked.

A note about upgrading.  I had to bump the DATA_FILE_VERSION number so 
that the config.db got updated to deal with case-preserving addresses
in some situation.  I've been running this on python.org for a few
days now and it all seems to work, but please keep an eye out for
anything strange with your config.db file.

Enjoy,
-Barry



From gorgo at caesar.elte.hu  Sat Apr  3 19:14:18 1999
From: gorgo at caesar.elte.hu (Gergely Madarasz)
Date: Sat, 3 Apr 1999 19:14:18 +0200 (METDST)
Subject: [Mailman-Users] Release 1.0b11
In-Reply-To: <14086.17297.485997.392346@anthem.cnri.reston.va.us>
Message-ID: <Pine.A32.3.96.990403190625.20415G-100000@caesar.power.elte.hu>

On Sat, 3 Apr 1999, Barry A. Warsaw wrote:

> Okay folks, 1.0b11 is now available at www.list.org.  This is basically
> a bug fix release addressing problems with case-preserving addresses and
> archiving of Usenet gated newsgroups.  For you hardcore debugging types,

I have just tried it, no problems so far. A debian package will be shortly
uploaded to the debian master server...

I have one suggestion though. The update script should check if the
previous version already has the new options.html and not warn about it if
it does...

-- 
Madarasz Gergely           gorgo at caesar.elte.hu         gorgo at linux.rulez.org
      It's practically impossible to look at a penguin and feel angry.
          Egy pingvinre gyakorlatilag lehetetlen haragosan nezni.
                    HuLUG: http://mlf.linux.rulez.org/






From lindsey at ncsa.uiuc.edu  Sat Apr  3 23:04:34 1999
From: lindsey at ncsa.uiuc.edu (Christopher Lindsey)
Date: Sat, 3 Apr 1999 15:04:34 -0600 (CST)
Subject: [Mailman-Users] Problems with 1.0b11
Message-ID: <199904032104.PAA26930@ferret.ncsa.uiuc.edu>

A non-text attachment was scrubbed...
Name: not available
Type: text
Size: 1212 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-users/attachments/19990403/dbd11b31/attachment.asc 

From lindsey at ncsa.uiuc.edu  Sat Apr  3 23:23:20 1999
From: lindsey at ncsa.uiuc.edu (Christopher Lindsey)
Date: Sat, 3 Apr 1999 15:23:20 -0600 (CST)
Subject: [Mailman-Users] Re: [Mailman-Developers] Release 1.0b11
In-Reply-To: <14086.17297.485997.392346@anthem.cnri.reston.va.us> from "Barry A. Warsaw" at Apr 3, 99 11:36:33 am
Message-ID: <199904032123.PAA27008@ferret.ncsa.uiuc.edu>

A non-text attachment was scrubbed...
Name: not available
Type: text
Size: 771 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-users/attachments/19990403/e11350e7/attachment.pot 

From bwarsaw at cnri.reston.va.us  Sun Apr  4 00:16:14 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Sat, 3 Apr 1999 17:16:14 -0500 (EST)
Subject: [Mailman-Users] Problems with 1.0b11
References: <199904032104.PAA26930@ferret.ncsa.uiuc.edu>
Message-ID: <14086.37678.531532.586223@anthem.cnri.reston.va.us>

>>>>> "CL" == Christopher Lindsey <lindsey at ncsa.uiuc.edu> writes:

    CL> Hi there,

    CL>    I upgraded from 1.0b10 to 1.0b11 today, but things aren't
    CL> going particularly well.

    CL>    I'm now running into cron errors (when none were seen
    CL> before):

Very strange.  None of this code has changed since at least b9!
You can cat out locks/mmqueue_run.lock and see if it looks sane, but
I think you can just blow the file away and re-run cron/run_queue
manually.  See what happens.

-Barry



From lindsey at ncsa.uiuc.edu  Sun Apr  4 00:43:47 1999
From: lindsey at ncsa.uiuc.edu (Christopher Lindsey)
Date: Sat, 3 Apr 1999 16:43:47 -0600 (CST)
Subject: [Mailman-Users] Problems with 1.0b11
In-Reply-To: <14086.37678.531532.586223@anthem.cnri.reston.va.us> from "Barry A. Warsaw" at Apr 3, 99 05:16:14 pm
Message-ID: <199904032243.QAA27358@ferret.ncsa.uiuc.edu>

A non-text attachment was scrubbed...
Name: not available
Type: text
Size: 907 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-users/attachments/19990403/8c60eb39/attachment.asc 

From bwarsaw at cnri.reston.va.us  Sun Apr  4 01:54:33 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Sat, 3 Apr 1999 18:54:33 -0500 (EST)
Subject: [Mailman-Users] Problems with 1.0b11
References: <14086.37678.531532.586223@anthem.cnri.reston.va.us>
	<199904032243.QAA27358@ferret.ncsa.uiuc.edu>
Message-ID: <14086.43577.770114.481987@anthem.cnri.reston.va.us>

>>>>> "CL" == Christopher Lindsey <lindsey at ncsa.uiuc.edu> writes:

    CL> That's what it looked like; I kept doing diffs against 1.0b10
    CL> and couldn't figure out what was going on.  I just figured it
    CL> was some of that magic that you do...  :)

Repeat after me: A-booga-booga Nogasto Eempa Shobu Umtada Squengi!

    >> You can cat out locks/mmqueue_run.lock and see if it looks
    >> sane, but I think you can just blow the file away and re-run
    >> cron/run_queue manually.  See what happens.

    CL> locks/mmqueue_run.lock looked fine and dandy, with two parts
    CL> and all.  Blew it away and reran the queue dispatcher manually
    CL> without any problems.  Guess I'll watch and see if it happens
    CL> again, but maybe it was a hiccup during the upgrade.

Just my little post-4/1 joke... er, um.. ;-)

    CL> Thanks for the quick response!

No problem.  You caught me in a sleep deprived between-gigs fog.  I'm
just glad my response made any sense (unlike this one :-).

-Barry



From jerodd at noah.dhs.org  Sun Apr  4 04:05:02 1999
From: jerodd at noah.dhs.org (Joshua E. Rodd)
Date: Sat, 03 Apr 1999 21:05:02 -0500
Subject: [Mailman-Users] Mailman 1.0b11
Message-ID: <3706C8CE.1D770B6A@noah.dhs.org>

Hello,

I want to say that I got the sources to 1.0b11 this morning, built and
installed them, and have been using them without mishap since.

I'd like to complement the authors of mailman for an excellent piece
of freed software. The web interface is pretty; the code is clean;
it's easy to use; and the user interface is friendly.

I am writing a README.exim to make it clear to people who know
nothing about either mailman or exim to help them get started.

Cheers,
Joshua.



From johnr at eecs.berkeley.edu  Sun Apr  4 05:29:35 1999
From: johnr at eecs.berkeley.edu (John Reekie)
Date: Sat, 3 Apr 1999 19:29:35 -0800
Subject: [Mailman-Users] Capitalization of list name
Message-ID: <000101be7e4c$d53e8090$2dbf6420@eecs.berkeley.edu>

How do I stop mailman from changing the
capitalization of list names? If I create
a list called diva it changes it to Diva;
if I create a list named GSRC it changes
is to Gsrc. I would just like to turn
this silly feature off.

Thanks for any help

JohnR




From Nailgodess at aol.com  Sun Apr  4 11:17:33 1999
From: Nailgodess at aol.com (Nailgodess at aol.com)
Date: Sun, 4 Apr 1999 05:17:33 EDT
Subject: [Mailman-Users] Is anyone...
Message-ID: <45368ec1.2438882d@aol.com>

Is anyone using this system on the clever.net system (in Atlanta)??
Thanks
Debbie Doerrlamm Webmaster BeautyTech



From raul3 at usa.net  Sun Apr  4 18:49:30 1999
From: raul3 at usa.net (Raul3)
Date: Sun, 04 Apr 1999 17:49:30 +0100
Subject: [Mailman-Users] Discarding held message generates an error.
Message-ID: <3707A62A.FF68D110@usa.net>

Hi,
I am new with Mailman and python, but I managed to install it and got it
running.  It went okay so far, except for this problem I hit.  I keep
getting an error when I tried to discard held messages from one of my
list.  I hit this problem when I was using version 1.0b9, and it did not
go away when I upgraded it to 1.0b10.  Can anyone give me a hand?


Regards,
Arthur

--- attached --




Bug in Mailman version 1.0b11

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 "/home/mailman/mailman/scripts/driver", line 112, in run_main
    main()
  File "/home/mailman/mailman/Mailman/Cgi/admindb.py", line 124, in main

    HandleRequests(doc)
  File "/home/mailman/mailman/Mailman/Cgi/admindb.py", line 214, in
HandleRequests
    list.HandleRequest(request, v)
  File "/home/mailman/mailman/Mailman/ListAdmin.py", line 122, in
HandleRequest
    self.HandlePostRequest(request_data[2:], value, comment)
  File "/home/mailman/mailman/Mailman/ListAdmin.py", line 165, in
HandlePostRequest
    self.LogMsg("vette", note)
  File "/home/mailman/mailman/Mailman/MailList.py", line 793, in LogMsg
    logf.write(msg % args + '\n')
TypeError: not enough arguments for format string





Environment variables:

 Variable
                        Value
 DOCUMENT_ROOT
                        /var/www/santubong
 UNIQUE_ID
                        Nwcq7Mq8eAgYkQAAMEk
 REMOTE_HOST
                        klj-231-41.tm.net.my
 CONTENT_TYPE
                        application/x-www-form-urlencoded
 PATH_TRANSLATED
                        /var/www/santubong/junk
 REMOTE_ADDR
                        202.188.231.41
 GATEWAY_INTERFACE
                        CGI/1.1
 HTTP_COOKIE
                        sysapps-admin=1764415036; junk-admin=857866178
 SERVER_PROTOCOL
                        HTTP/1.0
 HTTP_ACCEPT_LANGUAGE
                        en
 REMOTE_PORT
                        1148
 SERVER_PORT
                        80
 HTTP_CONNECTION
                        Keep-Alive
 HTTP_USER_AGENT
                        Mozilla/4.03 [en] (Win95; I)
 HTTP_ACCEPT_CHARSET
                        iso-8859-1,*,utf-8
 HTTP_ACCEPT
                        image/gif, image/x-xbitmap, image/jpeg,
image/pjpeg, */*
 REQUEST_URI
                        /mailman/admindb/junk
 PATH
                        /bin:/usr/bin:/sbin:/usr/sbin
 QUERY_STRING
 SCRIPT_FILENAME
                        /home/mailman/mailman/cgi-bin/admindb
 CONTENT_LENGTH
                        87
 HTTP_HOST
                        mail.plexus.net
 REQUEST_METHOD
                        POST
 SCRIPT_NAME
                        /mailman/admindb
 SERVER_ADMIN
                        noc at plexus.net
 SERVER_SOFTWARE
                        Apache/1.3.0 (Unix) Debian/GNU
 PYTHONPATH
                        /home/mailman/mailman
 PATH_INFO
                        /junk
 HTTP_REFERER
                        http://mail.plexus.net/mailman/admindb/junk
 SERVER_NAME
                        santubong.plexus.net






From ricardo at miss-janet.com  Sun Apr  4 13:10:24 1999
From: ricardo at miss-janet.com (ricardo at miss-janet.com)
Date: Sun, 4 Apr 1999 13:10:24 +0200
Subject: [Mailman-Users] permission woes...
Message-ID: <19990404131024.D15944@miss-janet.com>

Hi,

I'm in the process of switching  a mailinglist from  majordomo to
mailman... after a few sleepless nights i got a test list
running with mailman. The reason why it took so long was that
i needed to upgrade python to 1.51 to get it to actually do
something (v1.5 that comes with slackware didnt seem to work like it should)
but since i'm running qmail i thought it was a qmail problem.
Anyway i till have one problem left: the digest doesn't work yet, cron
sends me this:
Traceback (innermost last):
  File "/usr/local/mailman/cron/senddigests", line 41, in ?
    main()
  File "/usr/local/mailman/cron/senddigests", line 38, in main
    list.SendDigestIfAny()
  File "/usr/local/mailman/Mailman/Digester.py", line 198, in SendDigestIfAny
    self.SendDigestOnSize(0)
  File "/usr/local/mailman/Mailman/Digester.py", line 210, in SendDigestOnSize  
    self.SendDigest()
  File "/usr/local/mailman/Mailman/Digester.py", line 250, in SendDigest
    topics_file = open(os.path.join(self._full_path, 'next-digest-topics'),
IOError: (13, 'Permission denied')

i know my directories are probably not setup correctly (the cron is setup
for user mailman btw) ... but i have no idea what exactly should be the
permissions on/in the the $prefix/list/listname but there seems to be no easy way
to find out exactly what's going wrong... i noticed there are a few files
with uid "alias" (the one qmail uses) so i it can write in that directory.
i didnt do a "make install" as user  mailman because it looks like that 
you're not allowed to set the GID bits as non-root :(
in the malman-users mailinglist archive (doesn't any1 want to index it with 
http//www.htdig.org? :) ) i read that some linux systems give trouble with
the gid-thingy... maybe this can be the problem?

hmm maybe i should try switching it to a virtual qmail domain instead
of using ~alias...? but i'm afraid that i might trip  on other problems there 
and it already has taken me too much time :(

Thanks,



Ricardo.
--



From kuppler at zeus.chapel1.com  Sun Apr  4 04:51:58 1999
From: kuppler at zeus.chapel1.com (kuppler at zeus.chapel1.com)
Date: Sun, 4 Apr 1999 04:51:58
Subject: [Mailman-Users] AD:Family Reunion T Shirts & More
Message-ID: <199904041329.JAA15487@python.org>

Message sent by:  Kuppler Graphics, 32 West Main Street, Maple Shade, New Jersey, 08052,
1-800-810-4330.   This list will NOT be sold.  All addresses 
are automatically added to our remove list.

Hello.  My name is Bill from Kuppler Graphics.  We do screenprinting on T Shirts, Sweatshirts,
Jackets, Hats, Tote Bags and more!

Do you or someone you know have a Family Reunion coming up?  Kuppler Graphics would like to
provide you with some great looking T Shirts for your Reunion.

Kuppler Graphics can also provide you with custom T's and promotional items such as imprinted
magnets, keychains, pens, mugs, hats, etc. for your business or any fundraising activity
(church, school, business etc.) We also can provide you with quality embroidery. 

We are a family owned company with over 15 years of experience.  

All work is done at this location.  No middle man.  Our prices are great!

Click reply to email us or call 1-800-810-4330 for more info


Bill
Kuppler Graphics
 
 
 
 
 



From bwarsaw at cnri.reston.va.us  Sun Apr  4 19:04:43 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Sun, 4 Apr 1999 13:04:43 -0400 (EDT)
Subject: [Mailman-Users] Mailman 1.0b11
References: <3706C8CE.1D770B6A@noah.dhs.org>
Message-ID: <14087.39851.480654.459898@anthem.cnri.reston.va.us>

>>>>> "JER" == Joshua E Rodd <jerodd at noah.dhs.org> writes:

    JER> I want to say that I got the sources to 1.0b11 this morning,
    JER> built and installed them, and have been using them without
    JER> mishap since.

Cool!

    JER> I'd like to complement the authors of mailman for an
    JER> excellent piece of freed software. The web interface is
    JER> pretty; the code is clean; it's easy to use; and the user
    JER> interface is friendly.

Thanks.

    JER> I am writing a README.exim to make it clear to people who
    JER> know nothing about either mailman or exim to help them get
    JER> started.

That would be great.  Exim is one of those things on my list to Look
At Someday.  Haven't had the time, but if you write this up, I'll add
it to the distribution.

-Barry



From bwarsaw at cnri.reston.va.us  Sun Apr  4 19:09:22 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Sun, 4 Apr 1999 13:09:22 -0400 (EDT)
Subject: [Mailman-Users] Discarding held message generates an error.
References: <3707A62A.FF68D110@usa.net>
Message-ID: <14087.40130.132813.328754@anthem.cnri.reston.va.us>

>>>>> "R" == Raul  <raul3 at usa.net> writes:

    R> Hi, I am new with Mailman and python, but I managed to install
    R> it and got it running.  It went okay so far, except for this
    R> problem I hit.  I keep getting an error when I tried to discard
    R> held messages from one of my list.  I hit this problem when I
    R> was using version 1.0b9, and it did not go away when I upgraded
    R> it to 1.0b10.  Can anyone give me a hand?

When you discard the message, what did you type in the "Reason" text
box?

-Barry



From rpyne at kinfolk.org  Sun Apr  4 22:58:43 1999
From: rpyne at kinfolk.org (Richard B. Pyne)
Date: Sun, 4 Apr 1999 13:58:43 -0700
Subject: [Mailman-Users] Pastfix and Mailman
Message-ID: <199904042058.OAA11945@ns.kinfolk.org>

I am running postfix 19990330 on my test server and all appears to be 
working well. I also run Mailman as a mailing list manager. I am 
preparing to replace sendmail with postfix on my production server 
that also hosts several virtual domains.

My question is are there any caviats that I need to be careful of in 
making this transition? What are the known interactions and/or 
problems ralated to Postfix/Named Virtual Domains/Mailman?

I realize that there are some significant differences in the way 
aliases, Virtual Domains, etc. are configured and handled. Can anyone 
give an overview of the things I need to wath for and/or change?

Thank you in advance for any insights.


------------------------------
Richard B. Pyne, KB7RMU
rpyne at kinfolk.org
http://pyne.kinfolk.org/rbp2




From wietse at porcupine.org  Mon Apr  5 00:33:42 1999
From: wietse at porcupine.org (Wietse Venema)
Date: Sun, 4 Apr 1999 18:33:42 -0400 (EDT)
Subject: [Mailman-Users] Re: Pastfix and Mailman
In-Reply-To: <199904042058.OAA11945@ns.kinfolk.org> from "Richard B. Pyne" at "Apr 4, 99 01:58:43 pm"
Message-ID: <19990404223342.9C74A45837@spike.porcupine.org>

Richard B. Pyne:
> I am running postfix 19990330 on my test server and all appears to be 
> working well. I also run Mailman as a mailing list manager. I am 
> preparing to replace sendmail with postfix on my production server 
> that also hosts several virtual domains.
> 
> My question is are there any caviats that I need to be careful of in 
> making this transition? What are the known interactions and/or 
> problems ralated to Postfix/Named Virtual Domains/Mailman?
> 
> I realize that there are some significant differences in the way 
> aliases, Virtual Domains, etc. are configured and handled. Can anyone 
> give an overview of the things I need to wath for and/or change?
> 
> Thank you in advance for any insights.

The differences are small and subtle. The best way to find out if
they are relevant for you is to build a testbed and see how well
things work.

One problem is that the incoming queue fills up when mail arrives
faster than it can be delivered, but I haven't found a solution
for that yet. One possibility is to accept less inbound mail (a
lower process limit for inbound SMTP), but that could upset people
who use netscape etc. to submit mail via the SMTP port and who find
that the SMTP port is dead when the system is busy.

	Wietse



From Nailgodess at aol.com  Mon Apr  5 02:00:34 1999
From: Nailgodess at aol.com (Nailgodess at aol.com)
Date: Sun, 4 Apr 1999 20:00:34 EDT
Subject: [Mailman-Users] Is anyone...
Message-ID: <422885dd.24395722@aol.com>

The question is really because I now am using MReply and would liek to try 
somethig different. clever.net is a host farm :) and that is where I have my 
main domain with 5 lists now and 19 other some that would like lists, so 
before I got imvolved I wanted to nkow is anyone already set up housekeeping 
on clever with mailman :)

Anything in particular I should n=know.. like: forget it-not going to work.. 
or with some tweaking it will..

Thanks!!

Debbie Doerrlamm
Webmaster BeautyTech

In a message dated 4/4/99 5:45:43 PM Eastern Daylight Time, 
jerodd at noah.dhs.org writes:

> Nailgodess at aol.com wrote:
>  > Is anyone using this system on the clever.net system (in Atlanta)??
>  > Thanks
>  > Debbie Doerrlamm Webmaster BeautyTech
>  
>  You'll need to explain further what you mean by
>  ``on the clever.net system''. Do you mean using
>  them as your ISP? Do you mean using them to host
>  mailing lists on the clever.net domain?
>  
>  If you're having trouble with mailman or have
>  a question, feel free to explain/ask it in the
>  mailing list, and we'll all try our best. =)




From arthur at plexus.net  Mon Apr  5 04:51:17 1999
From: arthur at plexus.net (Arthur Lee)
Date: Mon, 5 Apr 1999 10:51:17 +0800
Subject: [Mailman-Users] Discarding held message generates an error.
In-Reply-To: <11D3FC19044CD211B7A20004AC444F322EA009@EVEREST>
Message-ID: <11D3FC19044CD211B7A20004AC444F3225AC1C@EVEREST>

I need to correct myself here, actually only one particular message is
giving me this problem.  I am attaching the header of this particular
message.

>
>
> >>>>> "R" == Raul  <raul3 at usa.net> writes:
>
>     R> Hi, I am new with Mailman and python, but I managed to install
>     R> it and got it running.  It went okay so far, except for this
>     R> problem I hit.  I keep getting an error when I tried to discard
>     R> held messages from one of my list.  I hit this problem when I
>     R> was using version 1.0b9, and it did not go away when I upgraded
>     R> it to 1.0b10.  Can anyone give me a hand?
>
> When you discard the message, what did you type in the "Reason" text
> box?
>

I tried both and they returned the same error.

Regards,
Arthur

Regards,
Arthur


--- Attachment ---
>From junk-admin  Sat Mar 27 07:40:40 1999
Received: from mx04.netaddress.usa.net (mx04.netaddress.usa.net
[204.68.24.141])
	by santubong.plexus.net (8.8.8/8.8.8/Debian/GNU) with SMTP id HAA01661
	for ; Sat, 27 Mar 1999 07:40:03 +0800
Received: (qmail 11843 invoked by uid 0); 26 Mar 1999 23:29:21 -0000
Received: from listserver.digitalriver.com [208.217.74.71] by mx04 via mtad
(2.6)
	with ESMTP id 860DcZXdg0164M04; Fri, 26 Mar 1999 23:29:20 GMT
Received: from listserver (208.217.74.71:3289) by
listserver.digitalriver.com (LSMTP for Windows NT v1.1b) with SMTP id
<0.0001B0DA at listserver.digitalriver.com>; Fri, 26 Mar 1999 16:02:19 -0600
Received: from LISTSERVER.DIGITALRIVER.COM by LISTSERVER.DIGITALRIVER.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 700238 for
          DW7 at LISTSERVER.DIGITALRIVER.COM; Fri, 26 Mar 1999 16:01:59 -0600
Approved-By: dwhse at LISTSERVER.DIGITALRIVER.COM
Received: from h-record (208.209.210.116:1424) by
listserver.digitalriver.com
          (LSMTP for Windows NT v1.1b) with SMTP id
          <0.0001ACEF at listserver.digitalriver.com>; Fri, 26 Mar 1999
15:52:35
          -0600
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID:  <03d001be77d3$5ceccc20$74d2d1d0 at h-record.digitalriver.com>
Date:         Fri, 26 Mar 1999 15:55:28 -0600
Reply-To: Downloadwarehouse Special Offers newsletter
Sender: Downloadwarehouse Special Offers newsletter
From: Download Warehouse
Subject:      Lotus Organizer 5.0  SAVE OVER 50%!
To: DW7 at LISTSERVER.DIGITALRIVER.COM

Download Lotus Organizer 5.0 and SAVE $40.00 compared to
MicroWarehouse's box price of $79.95. That's over 50%
[snipped]
--- End of Attachment ---




From lindsey at ncsa.uiuc.edu  Mon Apr  5 06:27:09 1999
From: lindsey at ncsa.uiuc.edu (Christopher Lindsey)
Date: Sun, 4 Apr 1999 23:27:09 -0500 (CDT)
Subject: [Mailman-Users] Discarding held message generates an error.
In-Reply-To: <11D3FC19044CD211B7A20004AC444F3225AC1C@EVEREST> from "Arthur Lee" at Apr 5, 99 10:51:17 am
Message-ID: <199904050427.XAA01555@ferret.ncsa.uiuc.edu>

A non-text attachment was scrubbed...
Name: not available
Type: text
Size: 1537 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-users/attachments/19990404/96333085/attachment.pot 

From ricardo at miss-janet.com  Mon Apr  5 14:02:16 1999
From: ricardo at miss-janet.com (Ricardo - Miss Janet. Fanclub)
Date: Mon, 5 Apr 1999 14:02:16 +0200 (CEST)
Subject: [Mailman-Users] feature request
Message-ID: <Pine.LNX.4.10.9904051329010.1170-100000@miss-janet.com>

Hi,

When i read about exim in the archive, i decided to check it out
myself... it looked very good so i decide to kick qmail out
the door :) The digest works like a charm now with exim.
but i do think it would be nice to have some sort of script
that validates all the permissions in the directories and that
can stell what you are doing wrong..

anyway one of the reasons i'm switching to mailman is that
i need the list to be moderated through the web... the way
it works now is that it puts all pending messages on the
same page. However, we are in Europe and since most of the mail
comes from people in the states, i suspect that the page
with all the pending messages is going  to be huge every morning.
So i think it would be nice to have only 1 messsage on the moderadte
page and you get to see the next one if you have accepted/rejected
the message... or maybe the possibility to set the maximum of
messages you see on one page...?  I checked the TODO list and
it doesnt seem to be on there yet...

ps: sorry for the typo's.. i'm using pine on a slow cable connection

Ricardo.
--
International Janet Jackson fanclub called MISS JANET.
For more information write to:
Miss Janet. P.O.Box 10016, 1001 EA Amsterdam, The Netherlands
Fax/phone: +31-(0)20-7764493 Email: fanclub at miss-janet.com
Or check out our website: http://miss-janet.com





From ae at w3.ca  Mon Apr  5 16:32:58 1999
From: ae at w3.ca (Andrew Ernst)
Date: Mon, 05 Apr 1999 11:32:58 -0300
Subject: [Mailman-Users] Monthly Password Reminders
Message-ID: <4.2.0.32.19990405112940.009eaae0@pop3.hfx.w3internet.com>

Greetings,

I am using 1.0b9 still, and before upgrading to b11, I just wanted to see 
if the following (what seems to be an error) has been fixed?

I have about 20 lists that I have moved to mailman, and the last one is 
setup for a "prefered domain" of striders.ns.ca.  Many of the other lists 
have different preferred domains.  However, when the cron job ran on Apr 1 
to send everyone's passwords, people on ALL the other lists received 
messages that told them their passwords at "striders.ns.ca".

As you can immagine, people never seeing this domain name before 
immediately thought they were being massmailed, and didn't bother even 
reading the message to figure it out.  Anyway, I was wondering if that was 
a bug, and if it has been fixed!

Happy Easter!

	-- Andrew --


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Andrew Ernst, Network Operations
W3 Internet Services Ltd.
Purdy's Wharf, Xerox Tower Suite 103
Halifax, Nova Scotia
Phone:  (902)492-2798 (Direct Line to Me)
Phone:  (902)425-2969 /  Fax:  (902)425-2822

http://www.w3internet.com
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=





From ray at everett.org  Mon Apr  5 16:40:00 1999
From: ray at everett.org (Ray Everett-Church)
Date: Mon, 5 Apr 1999 10:40:00 -0400 (EDT)
Subject: [Mailman-Users] Re: AD:Family Reunion T Shirts & More
In-Reply-To: <199904050501.BAA24655@python.org>
Message-ID: <Pine.BSF.4.05.9904051035580.12637-100000@bigfoot.everett.org>

I'm curious... are the anti-spam features (such as restricted posting)
for this list turned off? I've not had a spammer attack any of my lists
yet <wood knock="on">... If they aren't, could I suggest they be
turned on so we can see if the Kuppler crooks make it through again?

-Ray




From gmelists at caffeine.sundial.net  Mon Apr  5 16:44:48 1999
From: gmelists at caffeine.sundial.net (George M. Ellenburg (Mailing List Account))
Date: Mon, 05 Apr 1999 10:44:48 -0400
Subject: [Mailman-Users] Problems (still) MM-1.0b11 & Python 1.5.2b2 on BSD3.1
Message-ID: <4.1.19990405104115.0093ad60@10.0.0.1>

Fetched Python 1.5.2b2 from Python.org, install and tests went without a hitch.

Sucked down MM 1.0b11 this morning as well.

As user 'mailman' I ran `./configure --prefix=/u1/mailman
--with-mail-gid=32766 --with-cgi-gid=32766` (32766 is user nogroup)
followed next by `make install`.  No problems here.

In fact, I'm able to access the admin cgis.

But, as before, if I try to rin /bin/newlist I get the following error:
sundial:~/bin $ ./newlist
Enter the name of the list: test
Enter the email of the person running the list: gme at caffeine.sundial.net
Initial test password: XxXxXxXx
Traceback (innermost last):
  File "./newlist", line 141, in ?
    raise SystemExit(main(sys.argv))
  File "./newlist", line 91, in main
    newlist.Create(list_name, owner_mail, pw)
  File "/u1/mailman/Mailman/MailList.py", line 718, in Create
    self.Lock()
  File "/u1/mailman/Mailman/MailList.py", line 1267, in Lock
    self._lock_file.lock('w|', 1)
  File "/usr/local/lib/python1.5/posixfile.py", line 190, in lock
    flock = fcntl.fcntl(self._file_.fileno(), cmd, flock)
IOError: [Errno 22] Invalid argument
sundial:~/bin $

Anyone have any clues or ideas?

Many thanks.


-----
George M. Ellenburg                                    Tel: +1 407 438 6710
Systems Administrator,                                 Fax: +1 407 438 6714
Sundial Internet Services,                             WWW: www.sundial.net
a Division of Micro Mainframe Technology, Inc.

"If users are made to understand that the Systems Administrator's job is to
make computers run, and not to make them happy, they can, in fact, be made
happy most of the time. If users are allowed to believe that the Systems
Administrator's job is to make them happy, they can, in fact, never be made
happy." -- Paul Evans (as quoted by Barb Dijker in "Managing Support
Staff", LISA '97)



From klm at digicool.com  Mon Apr  5 17:33:22 1999
From: klm at digicool.com (Ken Manheimer)
Date: Mon, 5 Apr 1999 11:33:22 -0400 
Subject: [Mailman-Users] Capitalization of list name
Message-ID: <613145F79272D211914B0020AFF640190BEE1A@gandalf.digicool.com>

> How do I stop mailman from changing the
> capitalization of list names? If I create
> a list called diva it changes it to Diva;
> if I create a list named GSRC it changes
> is to Gsrc. I would just like to turn
> this silly feature off.

Two settings on each list's general admin page control this.  Eg, for
'mailman-users' we would got to

	http://www.python.org/mailman/admin/mailman-users

and set the "public name of the list" (the very first setting) and the
"prefix for subject line of list postings" (the fifth or so).

I won't get into whether or not this is a silly feature.  The important
thing is that you can  set them as you wish.

Ken Manheimer
klm at digicool.com



From lindsey at ncsa.uiuc.edu  Mon Apr  5 18:01:43 1999
From: lindsey at ncsa.uiuc.edu (Christopher Lindsey)
Date: Mon, 5 Apr 1999 11:01:43 -0500 (CDT)
Subject: [Mailman-Users] Re: AD:Family Reunion T Shirts & More
In-Reply-To: <Pine.BSF.4.05.9904051035580.12637-100000@bigfoot.everett.org> from "Ray Everett-Church" at Apr 5, 99 10:40:00 am
Message-ID: <199904051601.LAA05067@ferret.ncsa.uiuc.edu>

A non-text attachment was scrubbed...
Name: not available
Type: text
Size: 772 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-users/attachments/19990405/1867bb46/attachment.asc 

From bwarsaw at cnri.reston.va.us  Mon Apr  5 18:18:20 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Mon, 5 Apr 1999 12:18:20 -0400 (EDT)
Subject: [Mailman-Users] Re: AD:Family Reunion T Shirts & More
References: <199904050501.BAA24655@python.org>
	<Pine.BSF.4.05.9904051035580.12637-100000@bigfoot.everett.org>
Message-ID: <14088.57932.188897.943251@anthem.cnri.reston.va.us>

>>>>> "RE" == Ray Everett-Church <ray at everett.org> writes:

    RE> I'm curious... are the anti-spam features (such as restricted
    RE> posting) for this list turned off? I've not had a spammer
    RE> attack any of my lists yet <wood knock="on">... If they
    RE> aren't, could I suggest they be turned on so we can see if the
    RE> Kuppler crooks make it through again?

Antispam should be on for this list, as for all other python.org
lists.  I haven't investigated why this message got through though.  I 
will say that since using Mailman, the amount of spam I've seen on the 
lists has been /nearly/ zero - although I guess we can't claim 100%
protection.

-Barry



From bwarsaw at cnri.reston.va.us  Mon Apr  5 18:26:01 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Mon, 5 Apr 1999 12:26:01 -0400 (EDT)
Subject: [Mailman-Users] Problems (still) MM-1.0b11 & Python 1.5.2b2 on BSD3.1
References: <4.1.19990405104115.0093ad60@10.0.0.1>
Message-ID: <14088.58393.557784.399991@anthem.cnri.reston.va.us>

This is actually a problem with the posixfile.py module in Python that
affects BSD systems.  It is not fixed in Python 1.5.2b2, but will be
fixed in Python 1.5.2 final.  Here's Guido's explanation from the
mailman-developers archive:

http://www.python.org/pipermail/mailman-developers/1999-March/001008.html

-Barry




From gmelists at caffeine.sundial.net  Mon Apr  5 19:01:25 1999
From: gmelists at caffeine.sundial.net (George M. Ellenburg (Mailing List Account))
Date: Mon, 05 Apr 1999 13:01:25 -0400
Subject: [Mailman-Users] Problems (still) MM-1.0b11 & Python
  1.5.2b2 on BSD3.1
In-Reply-To: <14088.58393.557784.399991@anthem.cnri.reston.va.us>
References: <4.1.19990405104115.0093ad60@10.0.0.1>
Message-ID: <4.1.19990405125940.042ca020@10.0.0.1>

Excellent!  A simple 2 line hack to posixfile.py in my
/usr/local/lib/python1.5/ directory and it's now working.  While I haven't
patched the sources yet (I will later) this has immediately taken care of
the problem.  (Apparently) ;-)

Many thanks.

At 12:26 PM 4/5/99 , Barry A. Warsaw wrote:
>
>This is actually a problem with the posixfile.py module in Python that
>affects BSD systems.  It is not fixed in Python 1.5.2b2, but will be
>fixed in Python 1.5.2 final.  Here's Guido's explanation from the
>mailman-developers archive:
>
>http://www.python.org/pipermail/mailman-developers/1999-March/001008.html
>
>-Barry
>
>
>------------------------------------------------------
>Mailman-Users maillist  -  Mailman-Users at python.org
>http://www.python.org/mailman/listinfo/mailman-users
>




From bwarsaw at cnri.reston.va.us  Mon Apr  5 19:08:56 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Mon, 5 Apr 1999 13:08:56 -0400 (EDT)
Subject: [Mailman-Users] Problems (still) MM-1.0b11 & Python
  1.5.2b2 on BSD3.1
References: <4.1.19990405104115.0093ad60@10.0.0.1>
	<4.1.19990405125940.042ca020@10.0.0.1>
Message-ID: <14088.60968.401140.582304@anthem.cnri.reston.va.us>

Ah, good to know that works!
-Barry



From arthur at plexus.net  Tue Apr  6 04:05:02 1999
From: arthur at plexus.net (Arthur Lee)
Date: Tue, 6 Apr 1999 10:05:02 +0800
Subject: [Mailman-Users] Discarding held message generates an error.
In-Reply-To: <11D3FC19044CD211B7A20004AC444F322EA055@EVEREST>
Message-ID: <11D3FC19044CD211B7A20004AC444F3225AC23@EVEREST>

Thanks Christopher,  I had submitted a bug-report.  Hope it will be picked
up soon.

Regards,
Arthur

> -----Original Message-----
> From: mailman-users-admin at python.org
> [mailto:mailman-users-admin at python.org]On Behalf Of
> Christopher Lindsey
> Sent: Monday, 05 April, 1999 12:27 PM
> To: Arthur Lee
> Cc: bwarsaw at cnri.reston.va.us; mailman-users at python.org
> Subject: Re: [Mailman-Users] Discarding held message
> generates an error.
>
>
> > I need to correct myself here, actually only one particular
> message is
> > giving me this problem.  I am attaching the header of this
> particular
> > message.
>
> Well, I've tracked down the problem.  Now it's up to someone who
> can do Python programming to find the fix.  :)
>
> The problem is the '%' sign in the Subject; mailman appears to choke
> on it.  Without knowing anything about Python, I would guess that
> % is a specialized character and needs to be escaped or some such.
>
> > Subject:      Lotus Organizer 5.0  SAVE OVER 50%!
>
> Anyhow, I'm now awaiting a fix to purge the half dozen new
> messages out of my test list (yes, I'm too lazy to erase and
> recreate it.  :)
>
> Chris
>
> P.S.  Errors included below...
>
> ----------------------------------------------------------------------
> Traceback (innermost last):
>   File "/home/staff/mailman/scripts/driver", line 112, in run_main
>     main()
>   File "/home/staff/mailman/Mailman/Cgi/admindb.py", line 124, in main
>     HandleRequests(doc)
>   File "/home/staff/mailman/Mailman/Cgi/admindb.py", line
> 214, in HandleRequests
>     list.HandleRequest(request, v)
>   File "/home/staff/mailman/Mailman/ListAdmin.py", line 122,
> in HandleRequest
>     self.HandlePostRequest(request_data[2:], value, comment)
>   File "/home/staff/mailman/Mailman/ListAdmin.py", line 165,
> in HandlePostRequest
>     self.LogMsg("vette", note)
>   File "/home/staff/mailman/Mailman/MailList.py", line 793, in LogMsg
>     logf.write(msg % args + '\n')
> TypeError: not enough arguments for format string
>
> ------------------------------------------------------
> Mailman-Users maillist  -  Mailman-Users at python.org
> http://www.python.org/mailman/listinfo/mailman-users
>




From nbecker at fred.net  Tue Apr  6 15:15:02 1999
From: nbecker at fred.net (nbecker at fred.net)
Date: 06 Apr 1999 09:15:02 -0400
Subject: [Mailman-Users] kudos and question
Message-ID: <x88lng5riuh.fsf@nbeckerpc.hns.com>

First let me say mailman is entirely too cool!

Next a question.  I have setup a list here.  Attempting to followup
to a message I posted to my list
(using gnus) it goes to <list>@hns.com.  Unfortunately I don't control 
hns.com, only nbeckerpc.hns.com.  Where can I configure this?

(My exim mailer is configured to accept hns.com as well as
nbeckerpc.hns.com - but if someone else not using my machine tries to
reply it will just bounce)



From nbecker at fred.net  Tue Apr  6 15:24:19 1999
From: nbecker at fred.net (nbecker at fred.net)
Date: 06 Apr 1999 09:24:19 -0400
Subject: [Mailman-Users] exim configure
Message-ID: <x88g16drif0.fsf@nbeckerpc.hns.com>

Here is all I needed to do to use mailman with exim:

After system_aliases: Add

mailman_aliases:
  driver = aliasfile
  file = /etc/aliases.mailman
  search_type = lsearch
  user = mailman
  initgroups
  errors_to = mailman-owner

This assumes you want the alias pipes run as user "mailman".  You can
cut and paste verbatim the aliases spit out by "newlist" into
"/etc/aliases.mailman".



From klm at digicool.com  Tue Apr  6 16:54:39 1999
From: klm at digicool.com (Ken Manheimer)
Date: Tue, 6 Apr 1999 10:54:39 -0400 
Subject: [Mailman-Users] RE: Mailman-Users digest, Vol 1 #169 - 13 msgs
Message-ID: <613145F79272D211914B0020AFF640190BEE25@gandalf.digicool.com>

On monday, Ray Everett-Church <ray at everett.org> wrote:

> I'm curious... are the anti-spam features (such as restricted posting)
> for this list turned off? I've not had a spammer attack any of my
lists
> yet <wood knock="on">... If they aren't, could I suggest they be
> turned on so we can see if the Kuppler crooks make it through again?

As barry indicated, there's a lot of spam you haven't seen, because it
was caught.

Most is caught by a rule which prohibits holds postings which do not
explicitly mention the name of the list among the destination addresses
for the message.  A smaller portion after that catches postings which do
explicitly mention the list name, among too numerous other destinations.
The kuppler garbage made it through because it used a labor-intensive
sending process which explicitly targets every destination individually
- you may have noticed "<mailman-users at python.org>" as the sole
destination on the offending message.

It may be that such efforts will have "Re: Ad:" or some such on them,
but we can't tell on just one occurrance.  When/if we see one or two
more, we'll be able to infer a pattern, and then tailor one of the
pinpoint filters (per-address prohibition, or subject-line match as you
suggest, or whatever...)  

The not-so-nice thing is that restricting postings to list-members-only
is a rather extreme measure, because it can entail some maintenance
overhead.  Ie, it restricts the list members to posting from one sending
address, and even there the smart-matching is tricky, and can require
maintenance of the posters option.

The nice thing is, the explicit-destination constraint catches a _lot_
of the garbage, and we can handle the smallish remainder in a
proportional way.  It seems (he says, with some satisfaction) to be
working.-)  (I say this quietly because i don't want to "declare war on
spammers" - declaring war is like asking for people to hit you, which
doesn't seem like a smart thing to do.)

ken
klm at digicool.com



From jdfalk at cybernothing.org  Tue Apr  6 19:12:45 1999
From: jdfalk at cybernothing.org (J.D. Falk)
Date: Tue, 6 Apr 1999 10:12:45 -0700
Subject: [Mailman-Users] Approved posters denied in 1.0b11
Message-ID: <19990406101245.19667@cybernothing.org>

	Just upgraded to 1.0b11 'cause I saw this problem in 1.0b10
	and thought maybe 11 would fix it...people who're supposed
	to be allowed to post to lists (whether it's subscribers
	only or a subset thereof) are being blocked, as if the list
	now requires administrative approval for all messages.

	I'm guessing that this is something I missed in the spate of
	mail about b10 over the past few weeks....

 ---------========== J.D. Falk <jdfalk at cybernothing.org> =========---------
  |                "Confusion is mightier than the sword."               |
  |                                - Abbie Hoffman                       |
 ----========== http://www.cybernothing.org/jdfalk/home.html ==========----



From tgrace at thestar.ca  Tue Apr  6 20:04:42 1999
From: tgrace at thestar.ca (Grace, Terry)
Date: Tue, 6 Apr 1999 14:04:42 -0400 
Subject: [Mailman-Users] Approved posters denied in 1.0b11
Message-ID: <B582FE6508F7D111B75D00A0C9B3F84DB04C18@MAIL1>

I had the same problem. Barry suggested I add

USE_ENVELOPE_SENDER = 0     

to mm_cfg.py and it worked like a charm.


-----Original Message-----
From: mailman-users-admin at python.org
[mailto:mailman-users-admin at python.org]On Behalf Of J.D. Falk
Sent: Tuesday, April 06, 1999 1:13 PM
To: mailman-users at python.org
Subject: [Mailman-Users] Approved posters denied in 1.0b11


	Just upgraded to 1.0b11 'cause I saw this problem in 1.0b10
	and thought maybe 11 would fix it...people who're supposed
	to be allowed to post to lists (whether it's subscribers
	only or a subset thereof) are being blocked, as if the list
	now requires administrative approval for all messages.

	I'm guessing that this is something I missed in the spate of
	mail about b10 over the past few weeks....

 ---------========== J.D. Falk <jdfalk at cybernothing.org> =========---------
  |                "Confusion is mightier than the sword."               |
  |                                - Abbie Hoffman                       |
 ----========== http://www.cybernothing.org/jdfalk/home.html ==========----

------------------------------------------------------
Mailman-Users maillist  -  Mailman-Users at python.org
http://www.python.org/mailman/listinfo/mailman-users



From rpyne at kinfolk.org  Tue Apr  6 21:31:54 1999
From: rpyne at kinfolk.org (Richard B. Pyne)
Date: Tue, 6 Apr 1999 12:31:54 -0700
Subject: [Mailman-Users] Approved posters denied in 1.0b11
In-Reply-To: <19990406101245.19667@cybernothing.org>
Message-ID: <199904061831.MAA00286@ns.kinfolk.org>

The fix is simple, add "USE_ENVELOPE_SENDER = 0" (without the quotes) 
to mm_cfg.py, this will make it use the "From:" header for the match 
instead of the envelope sender.

On 6 Apr 99, at 10:12, J.D. Falk wrote:

> 	Just upgraded to 1.0b11 'cause I saw this problem in 1.0b10
> 	and thought maybe 11 would fix it...people who're supposed
> 	to be allowed to post to lists (whether it's subscribers
> 	only or a subset thereof) are being blocked, as if the list
> 	now requires administrative approval for all messages.
> 
> 	I'm guessing that this is something I missed in the spate of
> 	mail about b10 over the past few weeks....
> 
>  ---------========== J.D. Falk <jdfalk at cybernothing.org> =========---------
>   |                "Confusion is mightier than the sword."               |
>   |                                - Abbie Hoffman                       |
>  ----========== http://www.cybernothing.org/jdfalk/home.html ==========----
> 
> ------------------------------------------------------
> Mailman-Users maillist  -  Mailman-Users at python.org
> http://www.python.org/mailman/listinfo/mailman-users


------------------------------
Richard B. Pyne, KB7RMU
rpyne at kinfolk.org
http://pyne.kinfolk.org/rbp2




From jdfalk at cybernothing.org  Tue Apr  6 20:36:05 1999
From: jdfalk at cybernothing.org (J.D. Falk)
Date: Tue, 6 Apr 1999 11:36:05 -0700
Subject: [Mailman-Users] Approved posters denied in 1.0b11
In-Reply-To: <B582FE6508F7D111B75D00A0C9B3F84DB04C18@MAIL1>; from Grace, Terry on Tue, Apr 06, 1999 at 02:04:42PM -0400
References: <B582FE6508F7D111B75D00A0C9B3F84DB04C18@MAIL1>
Message-ID: <19990406113605.21562@cybernothing.org>

On 04/06/99, "Grace, Terry" <tgrace at thestar.ca> wrote: 

> I had the same problem. Barry suggested I add
> 
> USE_ENVELOPE_SENDER = 0     
> 
> to mm_cfg.py and it worked like a charm.

	Thanks, I'll try that.  What version did it change in?

 ---------========== J.D. Falk <jdfalk at cybernothing.org> =========---------
  |   "Every moment that a person lives                                  |
  |                increases his or her chances of dying by homicide."   |
  |                                -- Jon Levy <jlevy at uic.edu>           |
 ----========== http://www.cybernothing.org/jdfalk/home.html ==========----



From bwarsaw at cnri.reston.va.us  Wed Apr  7 04:10:39 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Tue, 6 Apr 1999 22:10:39 -0400 (EDT)
Subject: [Mailman-Users] Approved posters denied in 1.0b11
References: <B582FE6508F7D111B75D00A0C9B3F84DB04C18@MAIL1>
	<19990406113605.21562@cybernothing.org>
Message-ID: <14090.48799.38985.243731@anthem.cnri.reston.va.us>

>>>>> "JDF" == J D Falk <jdfalk at cybernothing.org> writes:

    JDF> 	Thanks, I'll try that.  What version did it change in?

1.0b12, but you don't have that yet :-)



From th at nextel.no  Wed Apr  7 14:28:28 1999
From: th at nextel.no (Tor Houghton)
Date: Wed, 7 Apr 1999 14:28:28 +0200 (MET DST)
Subject: [Mailman-Users] "No module named pythonlib"
In-Reply-To: <14085.8937.130945.465627@anthem.cnri.reston.va.us>
Message-ID: <Pine.GSO.4.05.9904071426260.24111-100000@opus.nextel.no>

Ah. I can hardly remember this problem. I think what I did was make a
symbolic link to point to the pythonlib.

In fact, in the end, I copied the pythonlib directory to the
/usr/local/lib/python-1.5, I think.

It works now, anyway.

I am using Python 1.5 and Mailman 1.0b9

Tor.

On Fri, 2 Apr 1999, Barry A. Warsaw wrote:

> 
> >>>>> "TH" == Tor Houghton <th at nextel.no> writes:
> 
>     TH> The Cron daemon reports the following for the mailman user:
> 
>     TH> Traceback (innermost last):
>     |   File "/home/mailman/cron/gate_news", line 27, in ?
>     |     from Mailman import MailList
>     |   File "/home/mailman/Mailman/MailList.py", line 33, in ?
>     |   File "/home/mailman/Mailman/ListAdmin.py", line 28, in ?
>     |   File "/home/mailman/Mailman/Message.py", line 31, in ?
>     TH> ImportError: No module named pythonlib
> 
>     TH> (Had I noticed this earlier, I would have included it in my
>     TH> previous mail.)
> 
> Sean O'Neill had the same problem.  What version of Mailman are you
> using?  Is there a /home/mailman/Mailman/pythonlib/__init__.py file?
> If not, is there an __init__.py file in the source you unpacked?
> 
> -Barry
> 




From RichardE at eskom.co.za  Wed Apr  7 15:01:57 1999
From: RichardE at eskom.co.za (Richard Ellerbrock)
Date: Wed, 07 Apr 1999 15:01:57 +0200
Subject: [Mailman-Users] A couple of questions
Message-ID: <s70b7371.072@eskom.co.za>

Just a compliment to start off with. I think that mailman is the best thing since sliced bread!

Now for the questions:

Under the list admin web page, membership management page, mass subscribe section how does a person change the "Send Welcome message to this batch?" to default to no.

If I change the DEFAULT_MAX_MESSAGE_SIZE = 2048 in the mm_cfg.py file, the web page only displays the first three characters (204). Bug!

Under the list admin web page, Archival Options, how do I change Archive Options to default to No? If I change ARCHIVE_TO_MBOX = -1 in mm_cfg.py, strange things happen. The web page still says Yes and I can never get archiving turned on again. I now have to resort to manually changing this to No for each list that I create. Bummer!

I would really like to see a generic interface for user subscriptions like Listserv has. All admin commands can be sent to an address like listserv at myhost.com with subscribe, view list etc. commands. Anybody willing to do this? It should be pretty simple writing a wrapper around mailman, but I do not know python and I do not have the time to figure it out.


Richard Ellerbrock
richarde at eskom.co.za





From th at nextel.no  Wed Apr  7 16:46:31 1999
From: th at nextel.no (Tor Houghton)
Date: Wed, 7 Apr 1999 16:46:31 +0200 (MET DST)
Subject: [Mailman-Users] Problems (still) MM-1.0b11 & Python 1.5.2b2 on
 BSD3.1
In-Reply-To: <4.1.19990405104115.0093ad60@10.0.0.1>
Message-ID: <Pine.GSO.4.05.9904071645200.25490-100000@opus.nextel.no>

This is probably what I experienced when I installed it on OpenBSD 2.3.
There seems to be a buglet (or something) in the flock() call with Python.

My fix for OpenBSD was posted, and should be in the archives.

Tor.

On Mon, 5 Apr 1999, George M. Ellenburg (Mailing List Account) wrote:

> Fetched Python 1.5.2b2 from Python.org, install and tests went without a hitch.
> 
> Sucked down MM 1.0b11 this morning as well.
> 
> As user 'mailman' I ran `./configure --prefix=/u1/mailman
> --with-mail-gid=32766 --with-cgi-gid=32766` (32766 is user nogroup)
> followed next by `make install`.  No problems here.
> 
> In fact, I'm able to access the admin cgis.
> 
> But, as before, if I try to rin /bin/newlist I get the following error:
> sundial:~/bin $ ./newlist
> Enter the name of the list: test
> Enter the email of the person running the list: gme at caffeine.sundial.net
> Initial test password: XxXxXxXx
> Traceback (innermost last):
>   File "./newlist", line 141, in ?
>     raise SystemExit(main(sys.argv))
>   File "./newlist", line 91, in main
>     newlist.Create(list_name, owner_mail, pw)
>   File "/u1/mailman/Mailman/MailList.py", line 718, in Create
>     self.Lock()
>   File "/u1/mailman/Mailman/MailList.py", line 1267, in Lock
>     self._lock_file.lock('w|', 1)
>   File "/usr/local/lib/python1.5/posixfile.py", line 190, in lock
>     flock = fcntl.fcntl(self._file_.fileno(), cmd, flock)
> IOError: [Errno 22] Invalid argument
> sundial:~/bin $
> 
> Anyone have any clues or ideas?
> 
> Many thanks.
> 
> 
> -----
> George M. Ellenburg                                    Tel: +1 407 438 6710
> Systems Administrator,                                 Fax: +1 407 438 6714
> Sundial Internet Services,                             WWW: www.sundial.net
> a Division of Micro Mainframe Technology, Inc.
> 
> "If users are made to understand that the Systems Administrator's job is to
> make computers run, and not to make them happy, they can, in fact, be made
> happy most of the time. If users are allowed to believe that the Systems
> Administrator's job is to make them happy, they can, in fact, never be made
> happy." -- Paul Evans (as quoted by Barb Dijker in "Managing Support
> Staff", LISA '97)
> 
> ------------------------------------------------------
> Mailman-Users maillist  -  Mailman-Users at python.org
> http://www.python.org/mailman/listinfo/mailman-users
> 




From NTzeng at cen.com  Wed Apr  7 18:40:47 1999
From: NTzeng at cen.com (Tzeng, Nigel)
Date: Wed, 7 Apr 1999 12:40:47 -0400 
Subject: [Mailman-Users] Hypermail integration
Message-ID: <7847B57C7C96D2119DBE00A0C96F64B60211A2@cen1.cen.com>

We're testing mailman as our list software and so far we like it.  However,
we'd like to be able to search our archives for info...something that
Pipermail doesn't offer.

I've finished compiling Hypermail and I'm wondering if anyone has any
pointers in replacing pipermail with Hypermail.

Thanks!

Nigel Tzeng
Century Computing 



From lindsey at ncsa.uiuc.edu  Wed Apr  7 19:14:29 1999
From: lindsey at ncsa.uiuc.edu (Christopher Lindsey)
Date: Wed, 7 Apr 1999 12:14:29 -0500 (CDT)
Subject: [Mailman-Users] Hypermail integration
In-Reply-To: <7847B57C7C96D2119DBE00A0C96F64B60211A2@cen1.cen.com> from "Tzeng, Nigel" at Apr 7, 99 12:40:47 pm
Message-ID: <199904071714.MAA21730@ferret.ncsa.uiuc.edu>

A non-text attachment was scrubbed...
Name: not available
Type: text
Size: 1444 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-users/attachments/19990407/bec933de/attachment.pot 

From csdayton at cs.uchicago.edu  Wed Apr  7 20:16:18 1999
From: csdayton at cs.uchicago.edu (Soren Dayton)
Date: 07 Apr 1999 13:16:18 -0500
Subject: [Mailman-Users] Question about the template directory
Message-ID: <xcdzp4kxpn1.fsf@bernstein.cs.uchicago.edu>

I see that Util.maketext() uses the template directory for things, but
it seems to me that a much nicer idea might be to have a template path,
using the first template in the path.  This could handle upgrades very
robustly, and allow an obvious kind of list administrator modification.

Would this be a desirable feature?  (I would submit code, but I don't
actually know python...  Sorry)

Thanks
Soren



From rupa-list at rupa.com  Wed Apr  7 20:17:04 1999
From: rupa-list at rupa.com (Rupa Schomaker (list))
Date: 07 Apr 1999 11:17:04 -0700
Subject: [Mailman-Users] Hypermail integration
In-Reply-To: "Tzeng, Nigel"'s message of "Wed, 7 Apr 1999 12:40:47 -0400"
References: <7847B57C7C96D2119DBE00A0C96F64B60211A2@cen1.cen.com>
Message-ID: <m36778b8in.fsf@gw.rupa.com>

Sorry, I can't help.  But a question for the list.  It seems that
searching the pipermail archives is a feature that many of us would
like.  Are there plans for adding searching to pipermail?  

"Tzeng, Nigel" <NTzeng at cen.com> writes:

> We're testing mailman as our list software and so far we like it.  However,
> we'd like to be able to search our archives for info...something that
> Pipermail doesn't offer.
> 
> I've finished compiling Hypermail and I'm wondering if anyone has any
> pointers in replacing pipermail with Hypermail.
> 
> Thanks!
> 
> Nigel Tzeng
> Century Computing 

-- 
Rupa (rupa at rupa.com for normal email)
Please don't email duplicate replies.



From bwarsaw at cnri.reston.va.us  Thu Apr  8 12:26:25 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Thu, 8 Apr 1999 06:26:25 -0400 (EDT)
Subject: [Mailman-Users] Question about the template directory
References: <xcdzp4kxpn1.fsf@bernstein.cs.uchicago.edu>
Message-ID: <14092.33873.657936.778036@anthem.cnri.reston.va.us>

Just a couple of quick notes, 'cause I've been down at the CFP99
conference since Tuesday...

>>>>> "SD" == Soren Dayton <csdayton at cs.uchicago.edu> writes:

    SD> I see that Util.maketext() uses the template directory for
    SD> things, but it seems to me that a much nicer idea might be to
    SD> have a template path, using the first template in the path.
    SD> This could handle upgrades very robustly, and allow an obvious
    SD> kind of list administrator modification.

    SD> Would this be a desirable feature?  (I would submit code, but
    SD> I don't actually know python...  Sorry)

Yes.  Ken had some good ideas about doing something like this, but it
never materialized.  I think it'll be an important post 1.0 change.




From bwarsaw at cnri.reston.va.us  Thu Apr  8 12:39:44 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Thu, 8 Apr 1999 06:39:44 -0400 (EDT)
Subject: [Mailman-Users] Hypermail integration
References: <7847B57C7C96D2119DBE00A0C96F64B60211A2@cen1.cen.com>
	<m36778b8in.fsf@gw.rupa.com>
Message-ID: <14092.34672.725592.809357@anthem.cnri.reston.va.us>

>>>>> "RS" == Rupa Schomaker <rupa-list at rupa.com> writes:

    RS> searching the pipermail archives is a feature that many of us
    RS> would like.  Are there plans for adding searching to
    RS> pipermail?

Probably not.  Andrew Kuchling (Pipermail's author) is not continuing
development on it and I don't think any of the Mailman developers has
a particularly driving desire to continue hacking on it.  IMO,
Pipermail's prime benefits are that 1) it's 100% Python code; 2) works 
well enough that there is at least a baseline bundled archiver.

I think I now understand that neither MHonArc nor Hypermail actually
come with search engines either, so it seems that everyone's got the
same problem.  What would be cool is if somebody adopts Pipermail as a 
spinoff and enhances it to do searching, MIME, etc.  Then we could
fold the work back into Mailman.  But I'll admit that that's a big
job.

-Barry



From ghent at starshadow.com  Thu Apr  8 16:58:24 1999
From: ghent at starshadow.com (Ryan McLean)
Date: Thu, 8 Apr 1999 10:58:24 -0400 (EDT)
Subject: [Mailman-Users] automated subscriptions
Message-ID: <Pine.LNX.4.10.9904081055040.21517-100000@orion.starshadow.com>

Hello,

  I wanted to know if there was a way to force subscriptions through,
using some sort of admin password.  I have several "adduser" type scripts
that need to add users to various mailing lists as they sign up for
services.  Having the user confirm these subscriptions is
counter-productive, I just want it to add them to the without the user
having any control over it.  Along that line, is there any way to prevent
users from unsubscribing themselves from the list?

  Apologies if these topics have been covered, I went through the
archives, but it took forever, and I didn't see much relent.  The archives
need to be searchable :)

 - Ryan

/*
 * Ryan McLean - Network/System Administrator
 * Starshadow Communications
 * Calgary, Alberta, Canada - Cleveland, Ohio USA
 * http://www.starshadow.com
 */




From lindsey at ncsa.uiuc.edu  Thu Apr  8 22:37:59 1999
From: lindsey at ncsa.uiuc.edu (Christopher Lindsey)
Date: Thu, 8 Apr 1999 15:37:59 -0500 (CDT)
Subject: [Mailman-Users] automated subscriptions
In-Reply-To: <Pine.LNX.4.10.9904081055040.21517-100000@orion.starshadow.com> from "Ryan McLean" at Apr 8, 99 10:58:24 am
Message-ID: <199904082037.PAA30889@ferret.ncsa.uiuc.edu>

A non-text attachment was scrubbed...
Name: not available
Type: text
Size: 1026 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-users/attachments/19990408/2f531de8/attachment.asc 

From ghent at starshadow.com  Thu Apr  8 23:00:34 1999
From: ghent at starshadow.com (Ryan McLean)
Date: Thu, 8 Apr 1999 17:00:34 -0400 (EDT)
Subject: [Mailman-Users] automated subscriptions
In-Reply-To: <199904082037.PAA30889@ferret.ncsa.uiuc.edu>
Message-ID: <Pine.LNX.4.10.9904081658230.7243-100000@orion.starshadow.com>

  Thanks for the tip.  As to the users not being able to unsubscribe
themselves, I use this for (amoung other things) sending important
annoucenments, emergencies, planned outages, etc etc to all the users who
subscribe to my services.  I don't want them removing themselves from THAT
list as it's very important that they recieve anything asnd everything
sent to that list.  As to other mailing lists that I have hosted, I don't
care about those :)

 - Ryan

/*
 * Ryan McLean - Network/System Administrator
 * Starshadow Communications
 * Calgary, Alberta, Canada - Cleveland, Ohio USA
 * http://www.starshadow.com
 */

On Thu, 8 Apr 1999, Christopher Lindsey wrote:

> >   I wanted to know if there was a way to force subscriptions through,
> > using some sort of admin password.  I have several "adduser" type scripts
> > that need to add users to various mailing lists as they sign up for
> > services.  Having the user confirm these subscriptions is
> > counter-productive, I just want it to add them to the without the user
> > having any control over it.  Along that line, is there any way to prevent
> > users from unsubscribing themselves from the list?
> 
> There's an add_members script in
> 
>    $prefix/bin
> 
> that will add users to a list without requiring confirmation.
> 
> As far as not allowing them to be removed without admin intervention
> (and despite the fact that the policy you're describing sounds kind of
> fascist (but hey, that's what procmail filters to /dev/null are for,
> right?)) you would have to hack the source, I think.
> 
> I'm not sure what advantages mailman gets you if the users can't do
> anything with their subscription -- why give them a Web interface?
> 
> Chris
> 




From allen at chesapeake.tokheim.com  Fri Apr  9 00:05:39 1999
From: allen at chesapeake.tokheim.com (Marc L. Allen)
Date: Thu, 08 Apr 1999 18:05:39 -0400
Subject: [Mailman-Users] REPLY-TO oddity
Message-ID: <370D2833.127075F2@chesapeake.tokheim.com>

I'm using 1.0B10 and I've noticed the following:

I've created a CNAME in my DNS to point maillist.x.y.z to machine
x.y.z.  I've also setup Mailman to use maillist.x.y.z as it's address
and URL.

When I set a list up to have replies go to the list, the REPLY-TO: field
of the message is list at x.y.z instead of the expected list at maillist.x.y.z

Any quick fixes?

Thanks,

Marc

-- 
************************************************************************
* Marc L. Allen                         *                              *
* Principal Architect                   * "If we had told you it was   *
* Information Technology Manager        * impossible, you'd never have *
*                                       * gone off and done it."       *
* Tokheim Technology Center             *                              *
* (757) 366-4185                        *    -- The Phantom Tollbooth  *
* allen at chesapeake.tokheim.com          *                              *
************************************************************************



From ghent at starshadow.com  Fri Apr  9 00:33:27 1999
From: ghent at starshadow.com (Ryan McLean)
Date: Thu, 8 Apr 1999 18:33:27 -0400 (EDT)
Subject: [Mailman-Users] REPLY-TO oddity
In-Reply-To: <370D2833.127075F2@chesapeake.tokheim.com>
Message-ID: <Pine.LNX.4.10.9904081832060.10476-100000@orion.starshadow.com>

CNAME's and mail server do NOT mix :)  I suggest you remove the CNAME and
replace it with a real A record.  Most MTA's deny CNAME's and go with the
resolved hostname.

 - Ryan

/*
 * Ryan McLean - Network/System Administrator
 * Starshadow Communications
 * Calgary, Alberta, Canada - Cleveland, Ohio USA
 * http://www.starshadow.com
 */

On Thu, 8 Apr 1999, Marc L. Allen wrote:

> I'm using 1.0B10 and I've noticed the following:
> 
> I've created a CNAME in my DNS to point maillist.x.y.z to machine
> x.y.z.  I've also setup Mailman to use maillist.x.y.z as it's address
> and URL.
> 
> When I set a list up to have replies go to the list, the REPLY-TO: field
> of the message is list at x.y.z instead of the expected list at maillist.x.y.z
> 
> Any quick fixes?
> 
> Thanks,
> 
> Marc
> 
> -- 
> ************************************************************************
> * Marc L. Allen                         *                              *
> * Principal Architect                   * "If we had told you it was   *
> * Information Technology Manager        * impossible, you'd never have *
> *                                       * gone off and done it."       *
> * Tokheim Technology Center             *                              *
> * (757) 366-4185                        *    -- The Phantom Tollbooth  *
> * allen at chesapeake.tokheim.com          *                              *
> ************************************************************************
> 
> ------------------------------------------------------
> Mailman-Users maillist  -  Mailman-Users at python.org
> http://www.python.org/mailman/listinfo/mailman-users
> 




From allen at chesapeake.tokheim.com  Fri Apr  9 00:40:00 1999
From: allen at chesapeake.tokheim.com (Marc L. Allen)
Date: Thu, 08 Apr 1999 18:40:00 -0400
Subject: [Mailman-Users] REPLY-TO oddity
References: <Pine.LNX.4.10.9904081832060.10476-100000@orion.starshadow.com>
Message-ID: <370D3040.40A9806@chesapeake.tokheim.com>

Hmmm.... changing it with an A record probably won't help, since the
name of my host is really x.y.z and not maillist.x.y.z.  Besides, why
can't Mailman set the REPLY-TO: to the address of the mail list. 
Afterall, it does know what that is, doesn't it?

Thanks,

Marc


Ryan McLean wrote:
> 
> CNAME's and mail server do NOT mix :)  I suggest you remove the CNAME and
> replace it with a real A record.  Most MTA's deny CNAME's and go with the
> resolved hostname.
> 
>  - Ryan
> 
> /*
>  * Ryan McLean - Network/System Administrator
>  * Starshadow Communications
>  * Calgary, Alberta, Canada - Cleveland, Ohio USA
>  * http://www.starshadow.com
>  */
> 
> On Thu, 8 Apr 1999, Marc L. Allen wrote:
> 
> > I'm using 1.0B10 and I've noticed the following:
> >
> > I've created a CNAME in my DNS to point maillist.x.y.z to machine
> > x.y.z.  I've also setup Mailman to use maillist.x.y.z as it's address
> > and URL.
> >
> > When I set a list up to have replies go to the list, the REPLY-TO: field
> > of the message is list at x.y.z instead of the expected list at maillist.x.y.z
> >
> > Any quick fixes?
> >
> > Thanks,
> >
> > Marc
> >
> > --
> > ************************************************************************
> > * Marc L. Allen                         *                              *
> > * Principal Architect                   * "If we had told you it was   *
> > * Information Technology Manager        * impossible, you'd never have *
> > *                                       * gone off and done it."       *
> > * Tokheim Technology Center             *                              *
> > * (757) 366-4185                        *    -- The Phantom Tollbooth  *
> > * allen at chesapeake.tokheim.com          *                              *
> > ************************************************************************
> >
> > ------------------------------------------------------
> > Mailman-Users maillist  -  Mailman-Users at python.org
> > http://www.python.org/mailman/listinfo/mailman-users
> >
> 
> ------------------------------------------------------
> Mailman-Users maillist  -  Mailman-Users at python.org
> http://www.python.org/mailman/listinfo/mailman-users

-- 
************************************************************************
* Marc L. Allen                         *                              *
* Principal Architect                   * "If we had told you it was   *
* Information Technology Manager        * impossible, you'd never have *
*                                       * gone off and done it."       *
* Tokheim Technology Center             *                              *
* (757) 366-4185                        *    -- The Phantom Tollbooth  *
* allen at chesapeake.tokheim.com          *                              *
************************************************************************



From rrobino at gstis.net  Fri Apr  9 03:00:35 1999
From: rrobino at gstis.net (Rick Robino)
Date: Thu, 8 Apr 1999 18:00:35 -0700
Subject: [Mailman-Users] REPLY-TO oddity
In-Reply-To: <370D3040.40A9806@chesapeake.tokheim.com>; from Marc L. Allen on Thu, Apr 08, 1999 at 06:40:00PM -0400
References: <Pine.LNX.4.10.9904081832060.10476-100000@orion.starshadow.com> <370D3040.40A9806@chesapeake.tokheim.com>
Message-ID: <19990408180035.R8314@gstis.net>

You don't have to alias one host name to another. Modern MTA's will
handle aliases just fine (it's up to the resolver anyway), as long as
an alias eventually leads to and answer from a real A record. I don't
see the point here of an alias though, except that maillist.x.y.z is
more intuitive for the user. I am assuming that x is not a subdomain,
but it shouldn't really matter as long as you have your dots right ;-)
I suppose you need the x...?

MX targets, on the other hand, is what is really going to tell other
MTA's where to go - it's nice to have the target name canonical, to
save extra lookups. From there, if you want messages sent to and from
the mailling list to be rewritten a certain way you're best bet (IMHO)
is to do that with your MTA on the MX host for the domain
maillist.x.y.z.  This is likely the "default" for the parent zone, if
you are using BIND and have a common setup. It can be specific to a
host (domain). You could also use an MUA wrapper, including doing that
right in the python code, but it's so much easier in Sendmail. Here is
what I would recommend:

;in zone file for y.z.

@	IN	SOA	<soa junk...>
	IN	MX	10 mailhost.x.y.z

mailhost	IN	A	10.0.0.1
x		IN	A	10.0.0.2
maillist.x	IN	A	10.0.0.2
(or if zone x.y.z, maillist	IN	A	10.0.0.2, whatever)

That handles where the incoming mail goes and the validity of your
"alias" while avoiding aliases. So, you have to change two RR's when
you change this server IP - who cares? I'm imagining that the machine
that has the list aliases is your MX host itself and not just a
relayed-to leaf. It would also make life easier if that had the MTA of
choice that mailman uses. No matter, as long as whatever the MTA
mailman uses to send out mail has a ruleset in there to rewrite your
headers the way you want.

With Sendmail there are a whole host of ways to do this - put the
homegrown ones in S98, and check in test mode. I'm partial to userdb or
virtusers which very simply rewriting the From:, but there are a
hundred ways to skin this cat. I'm sure qmail, postfix, smail, etc all
have similarly well-documented ways.

My $0.02, HTH. Sorry for the length.

--Rick

> On Thu, Apr 08, 1999 at 06:40:00PM -0400, Marc L. Allen wrote:
> Hmmm.... changing it with an A record probably won't help, since the
> name of my host is really x.y.z and not maillist.x.y.z.  Besides, why
> can't Mailman set the REPLY-TO: to the address of the mail list. 
> Afterall, it does know what that is, doesn't it?
> 
> Thanks,
> 
> Marc
> 
> 
> Ryan McLean wrote:
> > 
> > CNAME's and mail server do NOT mix :)  I suggest you remove the CNAME and
> > replace it with a real A record.  Most MTA's deny CNAME's and go with the
> > resolved hostname.
> > 
> >  - Ryan
> > 
> > /*
> >  * Ryan McLean - Network/System Administrator
> >  * Starshadow Communications
> >  * Calgary, Alberta, Canada - Cleveland, Ohio USA
> >  * http://www.starshadow.com
> >  */
> > 
> > On Thu, 8 Apr 1999, Marc L. Allen wrote:
> > 
> > > I'm using 1.0B10 and I've noticed the following:
> > >
> > > I've created a CNAME in my DNS to point maillist.x.y.z to machine
> > > x.y.z.  I've also setup Mailman to use maillist.x.y.z as it's address
> > > and URL.
> > >
> > > When I set a list up to have replies go to the list, the REPLY-TO: field
> > > of the message is list at x.y.z instead of the expected list at maillist.x.y.z
> > >
> > > Any quick fixes?
> > >
> > > Thanks,
> > >
> > > Marc
> > >
> > > --
> > > ************************************************************************
> > > * Marc L. Allen                         *                              *
> > > * Principal Architect                   * "If we had told you it was   *
> > > * Information Technology Manager        * impossible, you'd never have *
> > > *                                       * gone off and done it."       *
> > > * Tokheim Technology Center             *                              *
> > > * (757) 366-4185                        *    -- The Phantom Tollbooth  *
> > > * allen at chesapeake.tokheim.com          *                              *
> > > ************************************************************************
> > >
> > > ------------------------------------------------------
> > > Mailman-Users maillist  -  Mailman-Users at python.org
> > > http://www.python.org/mailman/listinfo/mailman-users
> > >
> > 
> > ------------------------------------------------------
> > Mailman-Users maillist  -  Mailman-Users at python.org
> > http://www.python.org/mailman/listinfo/mailman-users
> 


-- 
                                ^^^^^^^^^^^^^^
Rick Robino                                         mailto:rrobino at gstis.net
Manager, Internet Operations, GST/Whole Earth		http://www.gstis.net
Portland:     v. (503) 416-1517     f. (503) 416-1555      p. (503) 703-0728



From bwarsaw at cnri.reston.va.us  Fri Apr  9 03:24:09 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Thu, 8 Apr 1999 21:24:09 -0400 (EDT)
Subject: [Mailman-Users] Discarding held message generates an error.
References: <11D3FC19044CD211B7A20004AC444F322EA055@EVEREST>
	<11D3FC19044CD211B7A20004AC444F3225AC23@EVEREST>
Message-ID: <14093.22201.300149.694644@anthem.cnri.reston.va.us>

Here's the fix that'll be in b12.

-Barry

Index: ListAdmin.py
===================================================================
RCS file: /projects/cvsroot/mailman/Mailman/ListAdmin.py,v
retrieving revision 1.20
retrieving revision 1.21
diff -c -r1.20 -r1.21
*** ListAdmin.py	1999/03/31 17:52:42	1.20
--- ListAdmin.py	1999/04/09 01:20:36	1.21
***************
*** 147,163 ****
  	else:
              # Discard.
  	    rejection = "Discarded"
  	if rejection:
              note = '''%(listname)s: %(rejection)s posting:
  \tFrom: %(sender)s
! \tSubject: %(subject)s''' % {'listname' : self._internal_name,
!                              'rejection': rejection,
!                              'sender'   : msg.GetSender(),
!                              'subject'  : msg.getheader('subject', '<none>'),
!                              }
!             def strquote(s):
!                 return string.replace(s, '%', '%%')
!             
  	    if data[1]:
  		note = note + '\n\tHeld: ' + strquote(data[1])
  	    if comment:
--- 147,165 ----
  	else:
              # Discard.
  	    rejection = "Discarded"
+ 
+         def strquote(s):
+             return string.replace(s, '%', '%%')
+ 
  	if rejection:
              note = '''%(listname)s: %(rejection)s posting:
  \tFrom: %(sender)s
! \tSubject: %(subject)s''' % {
!                 'listname' : self._internal_name,
!                 'rejection': rejection,
!                 'sender'   : msg.GetSender(),
!                 'subject'  : strquote(msg.getheader('subject', '<none>')),
!                 }
  	    if data[1]:
  		note = note + '\n\tHeld: ' + strquote(data[1])
  	    if comment:



From arthur at plexus.net  Fri Apr  9 04:23:45 1999
From: arthur at plexus.net (Arthur Lee)
Date: Fri, 9 Apr 1999 10:23:45 +0800
Subject: [Mailman-Users] Discarding held message generates an error.
In-Reply-To: <11D3FC19044CD211B7A20004AC444F322EA370@EVEREST>
Message-ID: <11D3FC19044CD211B7A20004AC444F3225AC48@EVEREST>

> -----Original Message-----
> From: Barry A. Warsaw [mailto:bwarsaw at cnri.reston.va.us]
> Sent: Friday, 09 April, 1999 9:24 AM
> To: Arthur Lee
> Cc: 'Christopher Lindsey'; mailman-users at python.org
> Subject: RE: [Mailman-Users] Discarding held message 
> generates an error.
> 
> 
> 
> Here's the fix that'll be in b12.
> 
> -Barry

Thanks Barry, the patch worked as expected.

Arthur





From allen at chesapeake.tokheim.com  Fri Apr  9 14:39:51 1999
From: allen at chesapeake.tokheim.com (Marc L. Allen)
Date: Fri, 09 Apr 1999 08:39:51 -0400
Subject: [Mailman-Users] REPLY-TO oddity
References: <Pine.LNX.4.10.9904081832060.10476-100000@orion.starshadow.com> <370D3040.40A9806@chesapeake.tokheim.com> <19990408180035.R8314@gstis.net>
Message-ID: <370DF517.ABE3DD19@chesapeake.tokheim.com>

So... you're saying that the REPLY-TO field is generated or being
rewritten by sendmail and isn't something that Mailman is miswriting?

As for using maillist.x.y.z, it makes it easier to move the list server
at a later date if I want to.  It doesn't have to be at the primary MTU
site.  Also, I happen to control the x.y.z domain, but not the y.z
domain.

I guess my confusion is that Mailman writes the TO: field to be the
correct address, list at maillist.x.y.z, so why doesn't it write the
REPLY-TO: field the same way?

Thanks,

Marc

Rick Robino wrote:
> 
> You don't have to alias one host name to another. Modern MTA's will
> handle aliases just fine (it's up to the resolver anyway), as long as
> an alias eventually leads to and answer from a real A record. I don't
> see the point here of an alias though, except that maillist.x.y.z is
> more intuitive for the user. I am assuming that x is not a subdomain,
> but it shouldn't really matter as long as you have your dots right ;-)
> I suppose you need the x...?

<snip>

-- 
************************************************************************
* Marc L. Allen                         *                              *
* Principal Architect                   * "If we had told you it was   *
* Information Technology Manager        * impossible, you'd never have *
*                                       * gone off and done it."       *
* Tokheim Technology Center             *                              *
* (757) 366-4185                        *    -- The Phantom Tollbooth  *
* allen at chesapeake.tokheim.com          *                              *
************************************************************************



From RichardE at eskom.co.za  Fri Apr  9 16:06:15 1999
From: RichardE at eskom.co.za (Richard Ellerbrock)
Date: Fri, 09 Apr 1999 16:06:15 +0200
Subject: [Mailman-Users] A couple of questions (more!)
Message-ID: <s70e2582.086@eskom.co.za>

Here is another one to add to my list of questions/problems. There appears to be a problem with bounce detection on mailman. I am running mailman 1b11 with sendmail 8.9.3. What I have done is to remove a host from my network which had plenty of subscribers on a mailman list. What is now happening is that sendmail (or mailman?) groups all the smtp transactions into one for this host (mwp.eskom.co.za) and only the first address is detected as a bounce. The chain of events is a follows: send message to archaoe, list expands, one message is generated, sendmail detects host does not exist, only one address is picked up as failed (the first one, lootsc at mwp.eskom.co.za). This can be verified in the ~mailman/logs/bounce file and also the maillog extracts attached. I sent three test messages and as can be seen, only the first address is detected as a bounce.

Apr 09 11:48:20 1999  Archcoe: LootsC at mwp.eskom.co.za - first
Apr 09 13:21:35 1999  Archcoe: LootsC at mwp.eskom.co.za - 2 more allowed over 4264
04 secs
Apr 09 15:59:04 1999  Archcoe: LootsC at mwp.eskom.co.za - 1 more allowed over 4169
55 secs


Apr  9 15:58:59 lisa sendmail[15796]: PAA15796: from=<RichardE at eskom.co.za>, size=676, class=0, pri=30676, nrcpts=1, msgid=<s70e23c3.084 at eskom.co.za>, proto=ESMTP, relay=root at mail-spool1.eskom.co.za [147.110.52.3]
Apr  9 15:59:00 lisa sendmail[15797]: PAA15797: clone PAA15796, owner=archcoe-admin
Apr  9 15:59:01 lisa sendmail[15797]: PAA15797: to="|/home/mailman/mail/wrapper post archcoe", delay=00:00:02, xdelay=00:00:01, mailer=prog, stat=Sent
Apr  9 15:59:03 lisa sendmail[15805]: PAA15805: from=<archcoe-admin at lists.eskom.co.za>, size=1344, class=-60, pri=439344, nrcpts=11, msgid=<s70e23c3.084 at eskom.co.za>, proto=ESMTP, relay=IDENT:daemon at localhost [127.0.0.1]
Apr  9 15:59:03 lisa sendmail[15807]: PAA15805: to=<LootsC at mwp.eskom.co.za>,<dbeerlj at mwp.eskom.co.za>,<gerberp at mwp.eskom.co.za>,<jacobsja at mwp.eskom.co.za>,<kieserhc at mwp.eskom.co.za>,<levyl at mwp.eskom.co.za>,<lubbingl at mwp.eskom.co.za>,<robertef at mwp.eskom.co.za>,<singhv at mwp.eskom.co.za>,<underwmw at mwp.eskom.co.za>,<vdmerwj at mwp.eskom.co.za>, delay=00:00:00, xdelay=00:00:00, mailer=esmtp, relay=mwp.eskom.co.za, stat=Host unknown (Name server: mwp.eskom.co.za: host not found)
Apr  9 15:59:04 lisa sendmail[15807]: PAA15805: PAA15807: DSN: Host unknown (Name server: mwp.eskom.co.za: host not found)
Apr  9 15:59:04 lisa sendmail[15807]: PAA15807: to="|/home/mailman/mail/wrapper mailowner archcoe", delay=00:00:00, xdelay=00:00:00, mailer=prog, stat=Sent


Richard Ellerbrock
richarde at eskom.co.za


>>> "Richard Ellerbrock" <RichardE at eskom.co.za> 04/07/99 03:01PM >>>
Just a compliment to start off with. I think that mailman is the best thing since sliced bread!

Now for the questions:

Under the list admin web page, membership management page, mass subscribe section how does a person change the "Send Welcome message to this batch?" to default to no.

If I change the DEFAULT_MAX_MESSAGE_SIZE = 2048 in the mm_cfg.py file, the web page only displays the first three characters (204). Bug!

Under the list admin web page, Archival Options, how do I change Archive Options to default to No? If I change ARCHIVE_TO_MBOX = -1 in mm_cfg.py, strange things happen. The web page still says Yes and I can never get archiving turned on again. I now have to resort to manually changing this to No for each list that I create. Bummer!

I would really like to see a generic interface for user subscriptions like Listserv has. All admin commands can be sent to an address like listserv at myhost.com with subscribe, view list etc. commands. Anybody willing to do this? It should be pretty simple writing a wrapper around mailman, but I do not know python and I do not have the time to figure it out.


Richard Ellerbrock
richarde at eskom.co.za 



------------------------------------------------------
Mailman-Users maillist  -  Mailman-Users at python.org 
http://www.python.org/mailman/listinfo/mailman-users 





From RichardE at eskom.co.za  Fri Apr  9 16:59:04 1999
From: RichardE at eskom.co.za (Richard Ellerbrock)
Date: Fri, 09 Apr 1999 16:59:04 +0200
Subject: [Mailman-Users] Another problem?
Message-ID: <s70e31de.030@eskom.co.za>

I am already subscribed to a list as richarde at eskom.co.za. When I use the web page to subscribe to the same list as richarde at netman.eskom.co.za I get a message stating that I am already subscribed! For that matter it does not matter what domain I use, even richarde at abc.xyz.eskom.co.za says that I am already subscribed. This is with v1b11.

Richard Ellerbrock
richarde at eskom.co.za





From rrobino at gstis.net  Fri Apr  9 19:18:57 1999
From: rrobino at gstis.net (Rick Robino)
Date: Fri, 9 Apr 1999 10:18:57 -0700
Subject: [Mailman-Users] REPLY-TO oddity
In-Reply-To: <370DF517.ABE3DD19@chesapeake.tokheim.com>; from Marc L. Allen on Fri, Apr 09, 1999 at 08:39:51AM -0400
References: <Pine.LNX.4.10.9904081832060.10476-100000@orion.starshadow.com> <370D3040.40A9806@chesapeake.tokheim.com> <19990408180035.R8314@gstis.net> <370DF517.ABE3DD19@chesapeake.tokheim.com>
Message-ID: <19990409101857.F9653@gstis.net>

Sorry, I guess I was just trying to suggest a non-python method to make
your Reply-To get set the way you want. I have only looked at python, so
it's easier for me to do this with sendmail.

--Rick

> On Fri, Apr 09, 1999 at 08:39:51AM -0400, Marc L. Allen wrote:
> So... you're saying that the REPLY-TO field is generated or being
> rewritten by sendmail and isn't something that Mailman is miswriting?
> 
> As for using maillist.x.y.z, it makes it easier to move the list server
> at a later date if I want to.  It doesn't have to be at the primary MTU
> site.  Also, I happen to control the x.y.z domain, but not the y.z
> domain.
> 
> I guess my confusion is that Mailman writes the TO: field to be the
> correct address, list at maillist.x.y.z, so why doesn't it write the
> REPLY-TO: field the same way?
> 
> Thanks,
> 
> Marc
> 
> Rick Robino wrote:
> > 
> > You don't have to alias one host name to another. Modern MTA's will
> > handle aliases just fine (it's up to the resolver anyway), as long as
> > an alias eventually leads to and answer from a real A record. I don't
> > see the point here of an alias though, except that maillist.x.y.z is
> > more intuitive for the user. I am assuming that x is not a subdomain,
> > but it shouldn't really matter as long as you have your dots right ;-)
> > I suppose you need the x...?
> 
> <snip>
> 


-- 
                                ^^^^^^^^^^^^^^
Rick Robino                                         mailto:rrobino at gstis.net
Manager, Internet Operations, GST/Whole Earth		http://www.gstis.net
Portland:     v. (503) 416-1517     f. (503) 416-1555      p. (503) 703-0728



From lyndon at kcbbs.gen.nz  Fri Apr  9 23:30:58 1999
From: lyndon at kcbbs.gen.nz (Lyndon Drake)
Date: Sat, 10 Apr 1999 09:30:58 +1200
Subject: [Mailman-Users] Using a private web server for mailman
Message-ID: <19990410093058.A898@kcbbs.gen.nz>

Hi,

I have just finished setting up Mailman at a local school, and would like
to thank the developers for a very well designed and usable application.

The school is limited to a dialup connection to the internet, so even
though the mailing list is accessible to people outside the school, they
cannot access the web server used to administer the list.  I imagine that
other places exist where people might want to run Mailman on a server
that has limited access (e.g. a company might run Mailman on an internal
server that is firewalled from the Internet), so this may be of interest
to more people than just us :-).  I would like it to be possible for
list subscribers (or users) to manage their account via email (I realise
that there would be little appeal in doing this for admins).

There would appear to be a couple of things that users can do via the
web interface that cannot be done via email, in particular requesting a
password mailing.  Is it at all likely that the email commands will be
extended to accomodate more functionality by email?

Thanks,
Lyndon

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 240 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-users/attachments/19990410/02fe1c5d/attachment.pgp 

From lyndon at kcbbs.gen.nz  Fri Apr  9 23:36:23 1999
From: lyndon at kcbbs.gen.nz (Lyndon Drake)
Date: Sat, 10 Apr 1999 09:36:23 +1200
Subject: [Mailman-Users] Feature request for moderated lists
Message-ID: <19990410093623.B898@kcbbs.gen.nz>

Hi,

We have a moderated list, where it is expected that most if not all posts
will be accepted.  The problem I have is that every poster will receive
two automatic messages in response to their post: one to acknowledge that
it has been received, and another to inform them that their post has been
accepted/rejected.

I would really like to have the option of turning off the confirmation of
receipt and the acceptance message (I can't imagine that anyone would want
to turn of rejection notification).  It would save people a lot of extra
emails when posting.

(BTW: Something I forgot in my last post was to mention that I have
 modified all the text files that get mailed to list subscribers so as to
 omit any mention of the web interface.  If the modifications would be
 useful to anyone else, please let me know.)

Thanks,
Lyndon


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 240 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-users/attachments/19990410/7b054561/attachment.pgp 

From bwarsaw at cnri.reston.va.us  Sat Apr 10 01:49:27 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Fri, 9 Apr 1999 19:49:27 -0400 (EDT)
Subject: [Mailman-Users] REPLY-TO oddity
References: <Pine.LNX.4.10.9904081832060.10476-100000@orion.starshadow.com>
	<370D3040.40A9806@chesapeake.tokheim.com>
	<19990408180035.R8314@gstis.net>
	<370DF517.ABE3DD19@chesapeake.tokheim.com>
Message-ID: <14094.37383.342945.46551@anthem.cnri.reston.va.us>

>>>>> "MLA" == Marc L Allen <allen at chesapeake.tokheim.com> writes:

    MLA> So... you're saying that the REPLY-TO field is generated or
    MLA> being rewritten by sendmail and isn't something that Mailman
    MLA> is miswriting?

    MLA> I guess my confusion is that Mailman writes the TO: field to
    MLA> be the correct address, list at maillist.x.y.z, so why doesn't
    MLA> it write the REPLY-TO: field the same way?

Mailman does not, as a general rule, munge the Reply-To: header.
There is an option that a list admin can set which will munge this
header to point to the list, but its use is /very strongly/
discouraged.  For the seminal discussion of this issue, please read

    http://www.unicom.com/pw/reply-to-harmful.html

-Barry



From darren at jasper.somtel.com  Sat Apr 10 04:19:19 1999
From: darren at jasper.somtel.com (Darren Henderson)
Date: Fri, 9 Apr 1999 22:19:19 -0400 (EDT)
Subject: [Mailman-Users] REPLY-TO oddity
In-Reply-To: <14094.37383.342945.46551@anthem.cnri.reston.va.us>
Message-ID: <Pine.BSF.4.10.9904092205050.20638-100000@jasper.somtel.com>

On Fri, 9 Apr 1999, Barry A. Warsaw wrote:


> discouraged.  For the seminal discussion of this issue, please read
> 
>     http://www.unicom.com/pw/reply-to-harmful.html


I wish I had saved it. At one time I wrote a message to a mailing list
where someone was toating this line. I went through and addressed each
point that it made. 

It has been a while since I have read it but imo its quite bogus. It
essentially came down to (perhaps I'm unfairly characterizing it but the
religous fervor that some people devote to this issue just seems to get my
hackles up;) "I have been stupid in the past and have not checked to make
sure the mail message is going where I meant it to so protect me and other
ignorant users and don't munge this header".

I think it also goes on to point at one of the RFC's and applies a highly
stilted bit of logic to make it seem that the header is not meant to be
changed as only the "originator" of the message is supposed to change it.
Well... if the list is sending the message the list is the originator of
the message. Someone sent the message to the list the list added a bit to
it (readdressing it, putting in footers etc) and then sent its version out
to subscribers. Its entitled.

An other point made, I beleive, was that not using reply-to makes it
easier to respond to the author directly. Well...the majority of the
mailing lists I paticipate on I want to respond to the list and not to the
author (I really don't like getting the same bit of mail twice). I would
just as soon it were easier to respond to the list. (From here you can go
on to sillieness about what features which mailers have etc). Any
discussion type list should have all messages by default going back to the
list and if someone wants to make the extra effort to reply directly to
the author (ie removing the topic from discussion on the list) then they
can stand to do a possible extra step or two. By the same token Reply-to:
should probably not be used on an announcement or contact list.

What it comes down to is that, imo, that paticular diatribe is an opinion
piece about what one persons preferences are and it offers very little in
the way of any technical, moral, or factual information that relates to
the use of the reply-to header. 

*goes off to ponder pulling in a copy of the page again and putting up a
"reply-to-benificial" page that is actually a bit more thought out than
this quick reply*

______________________________________________________________________
Darren Henderson                              darren at jasper.somtel.com

                   Help fight junk e-mail, visit http://www.cauce.org/




From gstein at lyra.org  Sat Apr 10 04:36:19 1999
From: gstein at lyra.org (Greg Stein)
Date: Fri, 09 Apr 1999 19:36:19 -0700
Subject: [Mailman-Users] REPLY-TO oddity
References: <Pine.BSF.4.10.9904092205050.20638-100000@jasper.somtel.com>
Message-ID: <370EB923.1B10FB84@lyra.org>

Darren Henderson wrote:
> 
> On Fri, 9 Apr 1999, Barry A. Warsaw wrote:
> 
> > discouraged.  For the seminal discussion of this issue, please read
> >
> >     http://www.unicom.com/pw/reply-to-harmful.html
> 
> I wish I had saved it. At one time I wrote a message to a mailing list
> where someone was toating this line. I went through and addressed each
> point that it made.
> ...
> What it comes down to is that, imo, that paticular diatribe is an opinion
> piece about what one persons preferences are and it offers very little in
> the way of any technical, moral, or factual information that relates to
> the use of the reply-to header.

Actually, I would be interested in your response to the largest problem
that I see with Reply-To munging:

* I have seen a reply-to-munging list blow away a guy's Reply-To. He was
mailing from a "bad" email address and had inserted a Reply-To to the
correct address. Luckily, he posted to two lists and I was able to reply
to him on the other list. The reply-to-munger destroyed that capability.

You can argue all you want about other things and I won't get into it,
but Reply-To munging simply broke the system in this case.

Cheers,
-g

--
Greg Stein, http://www.lyra.org/



From darren at jasper.somtel.com  Sat Apr 10 04:46:52 1999
From: darren at jasper.somtel.com (Darren Henderson)
Date: Fri, 9 Apr 1999 22:46:52 -0400 (EDT)
Subject: [Mailman-Users] REPLY-TO oddity
In-Reply-To: <370EB923.1B10FB84@lyra.org>
Message-ID: <Pine.BSF.4.10.9904092237290.20638-100000@jasper.somtel.com>

On Fri, 9 Apr 1999, Greg Stein wrote:

> Actually, I would be interested in your response to the largest problem
> that I see with Reply-To munging:
> 
> * I have seen a reply-to-munging list blow away a guy's Reply-To. He was

There are a couple of simple ways to address that kind of situation. The
easist is to say if the message already has a reply-to set then don't
reset it. Though I could make an argument that since the list is sending
his message out to others it has every right to set its own reply-to :)

Another solution is to simply move his or the lists to another header.... 
Original-reply-to: for instance)

______________________________________________________________________
Darren Henderson                              darren at jasper.somtel.com

                   Help fight junk e-mail, visit http://www.cauce.org/




From James.Nicholson at amedd.army.mil  Sat Apr 10 05:20:10 1999
From: James.Nicholson at amedd.army.mil (Nicholson James D)
Date: Fri, 9 Apr 1999 23:20:10 -0400 
Subject: [Mailman-Users] How do I supress/modify announcements of subscription to the list
Message-ID: <BFDD20E1F489D21191C300104B99B7533DB65F@dasmtaamp032.amedd.army.mil.92.131.in-addr.arpa>

I want to run an unmoderated/static list.  However, I want to send out the
first message to everyone and I don't want it to be the standard form
letter.  How do I suppress the announcement?  I don't really want people
messing with their accounts.  This is a very small list.





From James.Nicholson at amedd.army.mil  Sat Apr 10 05:42:40 1999
From: James.Nicholson at amedd.army.mil (Nicholson James D)
Date: Fri, 9 Apr 1999 23:42:40 -0400 
Subject: [Mailman-Users] Config problems w/ apache 1.3.6 & mailman 1.0b11 on SGI
Message-ID: <BFDD20E1F489D21191C300104B99B7533DB661@dasmtaamp032.amedd.army.mil.92.131.in-addr.arpa>

Symptom:  Can't access admin or listinfo for the lists.  Basically, the web
interface is broken.  Server replies 404.  This is a badly configured
apache.

1) I've got apache running nicely on all the public_html directories.  

2) I made all the modifications suggested in the INSTALL file.

3) I can see <machine name>/~mailman.  It brings up a broken index.html.
There was not default.gif in the apache distribution.  And the logo.gif was
a broken link.

4) None of the web interface works.


SOLUTION:
1) The recommendation for ScriptAlias modification made in the INSTALL
document is wrong.
    Change it to (including quotes):

	 ScriptAlias   /~mailman/  "$prefix/cgi-bin/"





From James.Nicholson at amedd.army.mil  Sat Apr 10 06:05:06 1999
From: James.Nicholson at amedd.army.mil (Nicholson James D)
Date: Sat, 10 Apr 1999 00:05:06 -0400
Subject: [Mailman-Users] BUG:  NOT LOGGING hack attempts
Message-ID: <BFDD20E1F489D21191C300104B99B7533DB662@dasmtaamp032.amedd.army.mil.92.131.in-addr.arpa>

I can sit on the view list info page and hack all day long.  There is no
logging, no security policy.

Hmmmmm...... sounds like someone works for microsoft   8^)







From petrilli at amber.org  Sat Apr 10 06:28:28 1999
From: petrilli at amber.org (Christopher Petrilli)
Date: Sat, 10 Apr 1999 00:28:28 -0400
Subject: [Mailman-Users] BUG:  NOT LOGGING hack attempts
In-Reply-To: <BFDD20E1F489D21191C300104B99B7533DB662@dasmtaamp032.amedd.army.mil.92.131.in-addr.arpa>; from Nicholson James D on Sat, Apr 10, 1999 at 12:05:06AM -0400
References: <BFDD20E1F489D21191C300104B99B7533DB662@dasmtaamp032.amedd.army.mil.92.131.in-addr.arpa>
Message-ID: <19990410002828.A11759@amber.org>

On Sat, Apr 10, 1999 at 12:05:06AM -0400, Nicholson James D wrote:
> I can sit on the view list info page and hack all day long.  There is no
> logging, no security policy.
> 
> Hmmmmm...... sounds like someone works for microsoft   8^)

I would argue there IS logging in the web server,  and while there
probably should be more logging, I don't think it's quite "nothing"...

Chris
-- 
| Christopher Petrilli                      ``Television is bubble-gum for
| petrilli at amber.org                          the mind.''-Frank Lloyd Wright



From lindsey at ncsa.uiuc.edu  Sat Apr 10 06:55:59 1999
From: lindsey at ncsa.uiuc.edu (Christopher Lindsey)
Date: Fri, 9 Apr 1999 23:55:59 -0500 (CDT)
Subject: [Mailman-Users] BUG:  NOT LOGGING hack attempts
In-Reply-To: <BFDD20E1F489D21191C300104B99B7533DB662@dasmtaamp032.amedd.army.mil.92.131.in-addr.arpa> from "Nicholson James D" at Apr 10, 99 00:05:06 am
Message-ID: <199904100456.XAA08122@ferret.ncsa.uiuc.edu>

A non-text attachment was scrubbed...
Name: not available
Type: text
Size: 944 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-users/attachments/19990409/9e010cb8/attachment.pot 

From James.Nicholson at amedd.army.mil  Sat Apr 10 07:14:44 1999
From: James.Nicholson at amedd.army.mil (Nicholson James D)
Date: Sat, 10 Apr 1999 01:14:44 -0400
Subject: [Mailman-Users] BUG(S):  Mailman ignoring setting of privacy option to replace li
 st in from field
	st in from field
Message-ID: <BFDD20E1F489D21191C300104B99B7533DB666@dasmtaamp032.amedd.army.mil.92.131.in-addr.arpa>

Problem:  Selecting the privacy option to "Hide the sender of a message,
replacing it with the list address" is ignored by mailman.  The sender is
still listed in the From field.  And frankly, if mailman can't do this, then
it is a fancy way to manage mail aliases.  This is the only feature that I
need for a collaborative list, since, I want people to talk to everyone all
at once, not just among themselves.  IMHO, this option should probably be
moved from privacy to being a general option, since, it defines the list as
collaborative, not merely a convenient way to remember mailing addresses.

I would like to know what code is handling this area.  I'll fix it myself,
if I someone can point me to it.

Also, mailman can't allow apache to implement one security feature in the
httpd.conf recommended by apache, namely:
<Directory />
   Order deny,allow
   Deny from all
</Directory>

Apparently mailman needs to configure the server to allow directory listings
in order to work.  Is this really neccesary?


And while I have your attention, it seems that the default list setup is for
a completely public list.  It should probably be the other way around so
that mailman administrators don't make a big boo-boo.  

Also, the INSTALL document needs to mention about setting of allow/deny
options of apache.  For instance, a corporate server might deny everyone
except the corp.   For instance, I deny anything which is not .gov or .mil
from seeing the web site, EXCEPT for the machines of people on the list.
So, if you set up apache to be restrictive, you need to modify apache to
allow people in the list to subscribe.  You may want to put an option in
there somewhere for mailman to generate a perl script to be run by root
which will modify the httpd.conf to allow individual machines to have access
to the web site as part of an approved subscription.  You may ask how "how
in the devil am I going to locate a DHCP machine behind a firewall?"  The
answer is not simple, but, it works - cookies.  Couple a public web server
to the private one.  Mail them a URL when they subsribe via mail, they click
on the other URL from which they receive a cookie.  Allow access
conditionally on domain/cookie in apache /* which involves rewriting apache
:(  */  and you're there.  Otherwise, it's back to manual editing, which I
don't mind in this case because my list is small.   However, why did Larry
create perl?





From lindsey at ncsa.uiuc.edu  Sat Apr 10 07:53:28 1999
From: lindsey at ncsa.uiuc.edu (Christopher Lindsey)
Date: Sat, 10 Apr 1999 00:53:28 -0500 (CDT)
Subject: [Mailman-Users] BUG(S):  Mailman ignoring setting of privacy option to replace li
In-Reply-To: <BFDD20E1F489D21191C300104B99B7533DB666@dasmtaamp032.amedd.army.mil.92.131.in-addr.arpa> from "Nicholson James D" at Apr 10, 99 01:14:44 am
Message-ID: <199904100553.AAA08367@ferret.ncsa.uiuc.edu>

A non-text attachment was scrubbed...
Name: not available
Type: text
Size: 3543 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-users/attachments/19990410/f75d57a6/attachment.asc 

From James.Nicholson at amedd.army.mil  Sat Apr 10 08:13:14 1999
From: James.Nicholson at amedd.army.mil (Nicholson James D)
Date: Sat, 10 Apr 1999 02:13:14 -0400
Subject: [Mailman-Users] BUG(S):  Mailman ignoring setting of privacy 
	option to replace li
Message-ID: <BFDD20E1F489D21191C300104B99B7533DB667@dasmtaamp032.amedd.army.mil.92.131.in-addr.arpa>


> -----Original Message-----
> From:	Christopher Lindsey [SMTP:lindsey at ncsa.uiuc.edu]
> Sent:	Saturday, April 10, 1999 1:53 AM
> To:	James.Nicholson at amedd.army.mil
> Cc:	mailman-users at python.org
> Subject:	Re: [Mailman-Users] BUG(S):  Mailman ignoring setting of
> privacy option to replace li
> 
> > Problem:  Selecting the privacy option to "Hide the sender of a message,
> > replacing it with the list address" is ignored by mailman.  The sender
> is
> > still listed in the From field.  And frankly, if mailman can't do this,
> then
> > it is a fancy way to manage mail aliases.  
> 
> What version of mailman are you using?  And did you mean From_, or From:?
> At any rate, I wasn't able to reproduce this (mailman faithfully replaced
> all of my headers (except for the initial Received: header identifying
> me)...  
> 
	I have apache 1.3.6 (new download) and Mailman 1.0b11.  When I
config the list to replace the From field in mail to be the list, it doesn't
do it.  The From field is still the individual sender.  I'm talking about
individually mailed messages to each member on my test list.  I'm glad it
works for you.  I'm using an SGI, IRIX 6.2.  There may be something very
funky about the SGI supplied sendmail.  It won't even give a version number.
Anyone else run into problems on SGI?

> > Also, mailman can't allow apache to implement one security feature in
> the
> > httpd.conf recommended by apache, namely:
> > <Directory />
> >    Order deny,allow
> >    Deny from all
> > </Directory>
> > 
> 
>    <Directory $prefix/cgi-bin/>
>       Options SymLinksIfOwnerMatch ExecCGI
>    </Directory>
> 
> You need to allow access to the CGI scripts for the Web interface to
> work, but that's it (replace $prefix with your installation directory).
> 
	[Nicholson James D]  I assure you that those commands don't solve
the problem.
	Anything else that you've done custom, for instance, by loading
certan modules which aren't
	loaded by the default configuration?





From rpyne at kinfolk.org  Sat Apr 10 09:47:39 1999
From: rpyne at kinfolk.org (Richard B. Pyne)
Date: Sat, 10 Apr 1999 00:47:39 -0700
Subject: [Mailman-Users] BUG(S):  Mailman ignoring setting of privacy option to replace li st in from field	st in from field
In-Reply-To: <BFDD20E1F489D21191C300104B99B7533DB666@dasmtaamp032.amedd.army.mil.92.131.in-addr.arpa>
Message-ID: <199904100647.AAA15746@ns.kinfolk.org>

On 10 Apr 99, at 1:14, Nicholson James D wrote:

> allow people in the list to subscribe.  You may want to put an option in
> there somewhere for mailman to generate a perl script to be run by root
> which will modify the httpd.conf to allow individual machines to have access
> to the web site as part of an approved subscription. 

I strongly vote against this. Keep your cotton pickin' hand off my 
httpd.conf. NOw is you want to modify a separate file that I can 
include into httpd.conf, that is a different story.


------------------------------
Richard B. Pyne, KB7RMU
rpyne at kinfolk.org
http://pyne.kinfolk.org/rbp2




From rpyne at kinfolk.org  Sat Apr 10 09:47:39 1999
From: rpyne at kinfolk.org (Richard B. Pyne)
Date: Sat, 10 Apr 1999 00:47:39 -0700
Subject: [Mailman-Users] REPLY-TO oddity
In-Reply-To: <370EB923.1B10FB84@lyra.org>
Message-ID: <199904100647.AAA15743@ns.kinfolk.org>

No, what "simply broke the system" in your example was the *bad* 
email address the message was sent from. 

Replying to *this* message which had no Reply-to: and included what 
appeared to be all the list members as well as the list in the other 
headers that if I had "reply(ed) to all" it would have both sent one 
to the list and a separated message to each individual on the list. 
If it had a munged Reply-to: I could have simply "reply(ed)" instead 
of having to mannually clean out the mass of addresses and re-address 
it to the list only.

On 9 Apr 99, at 19:36, Greg Stein wrote:

> Darren Henderson wrote:
> > 
> > On Fri, 9 Apr 1999, Barry A. Warsaw wrote:
> > 
> > > discouraged.  For the seminal discussion of this issue, please read
> > >
> > >     http://www.unicom.com/pw/reply-to-harmful.html
> > 
> > I wish I had saved it. At one time I wrote a message to a mailing list
> > where someone was toating this line. I went through and addressed each
> > point that it made.
> > ...
> > What it comes down to is that, imo, that paticular diatribe is an opinion
> > piece about what one persons preferences are and it offers very little in
> > the way of any technical, moral, or factual information that relates to
> > the use of the reply-to header.
> 
> Actually, I would be interested in your response to the largest problem
> that I see with Reply-To munging:
> 
> * I have seen a reply-to-munging list blow away a guy's Reply-To. He was
> mailing from a "bad" email address and had inserted a Reply-To to the
> correct address. Luckily, he posted to two lists and I was able to reply
> to him on the other list. The reply-to-munger destroyed that capability.
> 
> You can argue all you want about other things and I won't get into it,
> but Reply-To munging simply broke the system in this case.
> 
> Cheers,
> -g
> 
> --
> Greg Stein, http://www.lyra.org/
> 
> ------------------------------------------------------
> Mailman-Users maillist  -  Mailman-Users at python.org
> http://www.python.org/mailman/listinfo/mailman-users


------------------------------
Richard B. Pyne, KB7RMU
rpyne at kinfolk.org
http://pyne.kinfolk.org/rbp2




From gstein at lyra.org  Sat Apr 10 09:30:26 1999
From: gstein at lyra.org (Greg Stein)
Date: Sat, 10 Apr 1999 00:30:26 -0700
Subject: [Mailman-Users] BUG:  NOT LOGGING hack attempts
References: <BFDD20E1F489D21191C300104B99B7533DB662@dasmtaamp032.amedd.army.mil.92.131.in-addr.arpa>
Message-ID: <370EFE12.77C8A417@lyra.org>

Nicholson James D wrote:
> ...
> Hmmmmm...... sounds like someone works for microsoft   8^)

What the hell?

If you want assistance, then stop the FUD. You ruin your credibility
with stuff like this. Also, these guys are producing Mailman for you,
for free. Give them a break and work with them, rather than assuming
something is broken and complaining.

Regards,
-g

--
Greg Stein, http://www.lyra.org/



From gstein at lyra.org  Sat Apr 10 09:33:02 1999
From: gstein at lyra.org (Greg Stein)
Date: Sat, 10 Apr 1999 00:33:02 -0700
Subject: [Mailman-Users] Config problems w/ apache 1.3.6 & mailman 1.0b11 on SGI
References: <BFDD20E1F489D21191C300104B99B7533DB661@dasmtaamp032.amedd.army.mil.92.131.in-addr.arpa>
Message-ID: <370EFEAE.44000126@lyra.org>

Nicholson James D wrote:
> 
> Symptom:  Can't access admin or listinfo for the lists.  Basically, the web
> interface is broken.  Server replies 404.  This is a badly configured
> apache.
>...
> SOLUTION:
> 1) The recommendation for ScriptAlias modification made in the INSTALL
> document is wrong.
>     Change it to (including quotes):
> 
>          ScriptAlias   /~mailman/  "$prefix/cgi-bin/"

No... it is NOT wrong.

The solution they provided works perfectly for me. I think you messed up
by inserting the tilde.

Here is what I have in my Apache configuration file:

# MAILMAN CONFIG
ScriptAlias /mailman/ /home/mailman/install/cgi-bin/
Alias /pipermail/ /home/mailman/install/archives/public/

<Directory /home/mailman/install/archives/public>
Options FollowSymLinks
</Directory>


That has been working great for me, for a LONG time.

-g

--
Greg Stein, http://www.lyra.org/



From gstein at lyra.org  Sat Apr 10 09:38:26 1999
From: gstein at lyra.org (Greg Stein)
Date: Sat, 10 Apr 1999 00:38:26 -0700
Subject: [Mailman-Users] How do I supress/modify announcements of subscription to the list
References: <BFDD20E1F489D21191C300104B99B7533DB65F@dasmtaamp032.amedd.army.mil.92.131.in-addr.arpa>
Message-ID: <370EFFF2.3923FD83@lyra.org>

Nicholson James D wrote:
> 
> I want to run an unmoderated/static list.  However, I want to send out the
> first message to everyone and I don't want it to be the standard form
> letter.  How do I suppress the announcement?  I don't really want people
> messing with their accounts.  This is a very small list.

That's the subscribeack.txt file located in $prefix/templates. It isn't
modifiable on a per-list basis. When you subscribe people to you list
(say, using the bulk-add in the admin screen), you can choose to not
send it to them.

There is also a flag on a per-list basis on whether to send that
message.

So... either edit the template (for all lists) or turn it off.
Unfortunately, there isn't a middle ground of per-list announcements.

-g

--
Greg Stein, http://www.lyra.org/



From lindsey at ncsa.uiuc.edu  Sat Apr 10 09:52:58 1999
From: lindsey at ncsa.uiuc.edu (Christopher Lindsey)
Date: Sat, 10 Apr 1999 02:52:58 -0500 (CDT)
Subject: [Mailman-Users] BUG(S):  Mailman ignoring setting of privacy
In-Reply-To: <BFDD20E1F489D21191C300104B99B7533DB667@dasmtaamp032.amedd.army.mil.92.131.in-addr.arpa> from "Nicholson James D" at Apr 10, 99 02:13:14 am
Message-ID: <199904100752.CAA09541@ferret.ncsa.uiuc.edu>

A non-text attachment was scrubbed...
Name: not available
Type: text
Size: 2395 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-users/attachments/19990410/3560b158/attachment.pot 

From csdayton at cs.uchicago.edu  Sat Apr 10 19:54:05 1999
From: csdayton at cs.uchicago.edu (Soren Dayton)
Date: 10 Apr 1999 12:54:05 -0500
Subject: [Mailman-Users] Are passwords obligatory?
Message-ID: <xcdaewg745e.fsf@bernstein.cs.uchicago.edu>

Hi,

I was wondering whether the use of passwords is obligatory or not?  One
of the things that we use our current (smartlist) setup for is something
like a department wide announcements (that people can un-subscribe to
automatically).  Giving everyone passwords for this seems a little
excessive to me, so I was wondering if there were facilities for not
using this (all the time).

Thanks
Soren




From clark.evans at manhattanproject.com  Sat Apr 10 23:43:27 1999
From: clark.evans at manhattanproject.com (Clark Evans)
Date: Sat, 10 Apr 1999 21:43:27 +0000
Subject: [Mailman-Users] Are passwords obligatory?
References: <xcdaewg745e.fsf@bernstein.cs.uchicago.edu>
Message-ID: <370FC5FF.C3FBFC47@manhattanproject.com>

Soren Dayton wrote:
> I was wondering whether the use of passwords is obligatory or not?  One
> of the things that we use our current (smartlist) setup for is something
> like a department wide announcements (that people can un-subscribe to
> automatically).  Giving everyone passwords for this seems a little
> excessive to me, so I was wondering if there were facilities for not
> using this (all the time).


The archives have a debate on this issue.  From my memory,
in a future version, a subscribe/unsubscribe will not 
require passwords (but will require confirmation).  All other
features (switching preferences, etc.) will require a password.

This seemed to be the middle ground that most people could agree with.

Regards,

Clark



From csdayton at cs.uchicago.edu  Sat Apr 10 23:48:56 1999
From: csdayton at cs.uchicago.edu (Soren Dayton)
Date: 10 Apr 1999 16:48:56 -0500
Subject: [Mailman-Users] Are passwords obligatory?
In-Reply-To: Clark Evans's message of "Sat, 10 Apr 1999 21:43:27 +0000"
References: <xcdaewg745e.fsf@bernstein.cs.uchicago.edu> <370FC5FF.C3FBFC47@manhattanproject.com>
Message-ID: <xcdhfqo5epj.fsf@bernstein.cs.uchicago.edu>

Thanks for the response.  Any sense of how far in the future this will
be?   This just seems pretty necessary to me....

Soren




Clark Evans <clark.evans at manhattanproject.com> writes:

> Soren Dayton wrote:
> > I was wondering whether the use of passwords is obligatory or not?  One
> > of the things that we use our current (smartlist) setup for is something
> > like a department wide announcements (that people can un-subscribe to
> > automatically).  Giving everyone passwords for this seems a little
> > excessive to me, so I was wondering if there were facilities for not
> > using this (all the time).
> 
> 
> The archives have a debate on this issue.  From my memory,
> in a future version, a subscribe/unsubscribe will not 
> require passwords (but will require confirmation).  All other
> features (switching preferences, etc.) will require a password.
> 
> This seemed to be the middle ground that most people could agree with.
> 
> Regards,
> 
> Clark



From lindsey at ncsa.uiuc.edu  Sun Apr 11 00:42:37 1999
From: lindsey at ncsa.uiuc.edu (Christopher Lindsey)
Date: Sat, 10 Apr 1999 17:42:37 -0500 (CDT)
Subject: [Mailman-Users] Address farming via the Web?
Message-ID: <199904102242.RAA12894@ferret.ncsa.uiuc.edu>

A non-text attachment was scrubbed...
Name: not available
Type: text
Size: 793 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-users/attachments/19990410/f3ce2ac4/attachment.asc 

From bwarsaw at cnri.reston.va.us  Sun Apr 11 02:31:53 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Sat, 10 Apr 1999 20:31:53 -0400 (EDT)
Subject: [Mailman-Users] REPLY-TO oddity
References: <370EB923.1B10FB84@lyra.org>
	<199904100647.AAA15743@ns.kinfolk.org>
Message-ID: <14095.60793.446584.692130@anthem.cnri.reston.va.us>

There's really no point in arguing this anymore.  Mailman lets list
admins munge Reply-To: if they want, but I think we are justified in
discouraging it.

-Barry



From bwarsaw at cnri.reston.va.us  Sun Apr 11 02:53:05 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Sat, 10 Apr 1999 20:53:05 -0400 (EDT)
Subject: [Mailman-Users] BUG:  NOT LOGGING hack attempts
References: <BFDD20E1F489D21191C300104B99B7533DB662@dasmtaamp032.amedd.army.mil.92.131.in-addr.arpa>
Message-ID: <14095.62065.929896.685733@anthem.cnri.reston.va.us>

>>>>> "NJD" == Nicholson James D <James.Nicholson at amedd.army.mil> writes:

    NJD> I can sit on the view list info page and hack all day long.
    NJD> There is no logging, no security policy.

It is a bug that the edithtml CGI is not hidden behind admin
authorization.  I've submitted a bug report on this.

-Barry



From bwarsaw at cnri.reston.va.us  Sun Apr 11 02:58:49 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Sat, 10 Apr 1999 20:58:49 -0400 (EDT)
Subject: [Mailman-Users] BUG(S):  Mailman ignoring setting of privacy option to replace li st in from field	st in from field
References: <BFDD20E1F489D21191C300104B99B7533DB666@dasmtaamp032.amedd.army.mil.92.131.in-addr.arpa>
	<199904100647.AAA15746@ns.kinfolk.org>
Message-ID: <14095.62409.557508.288371@anthem.cnri.reston.va.us>

>>>>> "RBP" == Richard B Pyne <rpyne at kinfolk.org> writes:

    >> allow people in the list to subscribe.  You may want to put an
    >> option in there somewhere for mailman to generate a perl script
    >> to be run by root which will modify the httpd.conf to allow
    >> individual machines to have access to the web site as part of
    >> an approved subscription.

    RBP> I strongly vote against this. Keep your cotton pickin' hand
    RBP> off my httpd.conf. NOw is you want to modify a separate file
    RBP> that I can include into httpd.conf, that is a different
    RBP> story.

I thought you were going to be strongly opposed to this because he
suggested using a Perl script... :-)

-Barry



From bwarsaw at cnri.reston.va.us  Sun Apr 11 03:00:45 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Sat, 10 Apr 1999 21:00:45 -0400 (EDT)
Subject: [Mailman-Users] Are passwords obligatory?
References: <xcdaewg745e.fsf@bernstein.cs.uchicago.edu>
	<370FC5FF.C3FBFC47@manhattanproject.com>
	<xcdhfqo5epj.fsf@bernstein.cs.uchicago.edu>
Message-ID: <14095.62525.912187.824228@anthem.cnri.reston.va.us>

>>>>> "SD" == Soren Dayton <csdayton at cs.uchicago.edu> writes:

    SD> Any sense of how far in the future this will be?

Nope.  Definitely post-1.0.



From bwarsaw at cnri.reston.va.us  Sun Apr 11 03:06:04 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Sat, 10 Apr 1999 21:06:04 -0400 (EDT)
Subject: [Mailman-Users] Address farming via the Web?
References: <199904102242.RAA12894@ferret.ncsa.uiuc.edu>
Message-ID: <14095.62844.250000.751531@anthem.cnri.reston.va.us>

>>>>> "CL" == Christopher Lindsey <lindsey at ncsa.uiuc.edu> writes:

    CL> I'm not sure if anyone even cares or not, but it looks as if
    CL> the mailman-users list has been mined for email addresses.
    CL> Presumably this is being done via the Web interface...

I bet what's happening is that they're following the link to the
archives and then trolling through them for email addresses.  That
sucks.  Other than the URL you pointed us to, does anybody else have
any ideas of how to stop this particular mining?  Do we obfuscate
every email address in every message saved to the archive?  If so,
then can I get away with pushing that over the fence into the
archiver's responsibilities? :-)

-Barry



From clark.evans at manhattanproject.com  Sun Apr 11 03:57:16 1999
From: clark.evans at manhattanproject.com (Clark Evans)
Date: Sun, 11 Apr 1999 01:57:16 +0000
Subject: [Mailman-Users] Address farming via the Web?
References: <199904102242.RAA12894@ferret.ncsa.uiuc.edu> <14095.62844.250000.751531@anthem.cnri.reston.va.us>
Message-ID: <3710017C.2C0D0BB0@manhattanproject.com>

"Barry A. Warsaw" wrote:
> I bet what's happening is that they're following the link to the
> archives and then trolling through them for email addresses.  That sucks.

Perhaps you can ask each person subscribing for their "NickName"
in addition to their e-mail address.  Then on the membership
pages put their Nick Name (so that that's not mined either...)
and when someone posts, use e-mail -> Nick Name mapping to re-write
who the message is from.  Either attempt to re-write addresses
in "To:" and "CC:" as well, or just strip them.

For now, you can strip the address in brackets, i.e., have 
"Barry A. Warsaw" logged instead of "Barry A. Warsaw <bwarsaw...> "

This seems to be a quick solution for the archive, but it
dosn't stop member list mining...   I feel that as soon as
mailman gets big enough, people will write mailman-specific
miners that arn't messed up with the simple re-write
user at domain.com -> user at domain.com , thus the "NickName" idea.

Hope this helps.

Clark



From darren at jasper.somtel.com  Sun Apr 11 05:47:13 1999
From: darren at jasper.somtel.com (Darren Henderson)
Date: Sat, 10 Apr 1999 23:47:13 -0400 (EDT)
Subject: [Mailman-Users] Address farming via the Web?
In-Reply-To: <14095.62844.250000.751531@anthem.cnri.reston.va.us>
Message-ID: <Pine.BSF.4.10.9904102326300.25635-100000@jasper.somtel.com>

On Sat, 10 Apr 1999, Barry A. Warsaw wrote:

> I bet what's happening is that they're following the link to the
> archives and then trolling through them for email addresses.  That
> sucks.  Other than the URL you pointed us to, does anybody else have
> any ideas of how to stop this particular mining?  Do we obfuscate
> every email address in every message saved to the archive?  If so,
> then can I get away with pushing that over the fence into the
> archiver's responsibilities? :-)

imo its not really a problem for mailman to address. 

Spam is a large on going problem whose scope simply exceeds the confines
of your project.

If there are simple things that can be done then sure, go ahead. I really
can't imagine what they might be other then doing what you've mentioned,
(which really probably would fit in better with the archiver section). Or
perhaps including some web poison links by default, which might be nice if
mailman gets the ammount of usage I belive it would. Essentially bury from
human eyes and mark for non-harvesting by legit bots, a set of links that
point to some cgi that generates tons and tons of bad email address and
links back to itself so you swamp the harvester with crud -
http://www.e-scrub.com/ has one example I believe but I can't seem to get
it to come up tonight.

______________________________________________________________________
Darren Henderson                              darren at jasper.somtel.com

                   Help fight junk e-mail, visit http://www.cauce.org/




From che at debian.org  Sun Apr 11 07:53:06 1999
From: che at debian.org (Ben Gertzfield)
Date: 10 Apr 1999 22:53:06 -0700
Subject: [Mailman-Users] Mailman FAQ on web page is clobbered by HTML
Message-ID: <ytt1zhrput9.fsf@gilgamesh.cse.ucsc.edu>

The last question ("I want to get rid of some messages in my
archive. How do I do this?") in the Mailman FAQ is missing
some critical information; it includes lines like:

remove $prefix/archives/private/<listname>
edit $prefix/archives/private/<listname>.mbox/<listname>.mbox

et cetera, except when this is changed to HTML, the < and > are
not changed to &lt; and &gt; so the <listname> bits are
totally invisible! Oops! This should probably be fixed.

-- 
Brought to you by the letters O and V and the number 12.
"Yasashisani tsutsumaretanara, kitto.. meni utsuru.."
Debian GNU/Linux maintainer of Gimp and GTK+ -- http://www.debian.org/
I'm on FurryMUCK as Che, and EFNet/Open Projects IRC as Che_Fox.



From gconnor at nekodojo.org  Sun Apr 11 09:49:14 1999
From: gconnor at nekodojo.org (Greg Connor)
Date: Sun, 11 Apr 1999 00:49:14 -0700
Subject: [Mailman-Users] Mailman questions (moderation  
  capabilities, mostly)
In-Reply-To: <3701592A.2499D764@lyra.org>
References: <4.1.19990330133003.00a117e0@mail.blarg.net>
 <4.1.19990330145444.009f7a10@mail.blarg.net>
Message-ID: <4.1.19990411003832.00bb9e70@pop.nekodojo.org>

At 03:07 PM 3/30/99 -0800, Greg Stein wrote:
[Regarding how you actually do a preapproved list]
>
>The list is adjusted via the administrative web interface. You never
>need people to log into your machine simply to admin a list.
>
>The server admin needs to log in to create new lists and configure the
>MTA, but once a list is built... it's all web.
>
>This does imply that your moderators would have the ability to
>reconfigure the list parameters, so there is a bit more consideration
>than simply "are they prudent enough to moderate message content".
>Usually not a problem, IMO, because if they are moderating, then they're
>probably quite responabile and dedicated to a successful mailing list.


Totally side note... I can't think of a situation where you want to have
"moderators" who are not also "admins".  However, if someone really wanted
to do this, they could use Apache to place further authorization
requirements on the /mailman/admin/ urls, leaving the /mailman/admindb/
urls at the default state.  This means that the "true admins" would need
two passwords to get in to the actual admin config interface.

This is a variation on something Greg S proposed for locking down archives
to admins-only; you would use the <Location> section of Apache config in
both cases (and is still a cool idea).

gregc



From gconnor at nekodojo.org  Sun Apr 11 10:47:40 1999
From: gconnor at nekodojo.org (Greg Connor)
Date: Sun, 11 Apr 1999 01:47:40 -0700
Subject: [Mailman-Users] 1.0b9 problem, adding lots of users
Message-ID: <4.1.19990411012807.00c3add0@pop.nekodojo.org>

Apologies if this has been found already... I want to mention it in case it
is not yet discovered by anyone else :)

When doing a mass-subscribe of 280 people, mailman subscribed everyone, but
stopped sending welcome messages after like 23 went out.  There was a
traceback error (sorry, I didn't copy it) ... something about "Resource
unavailable" at the bottom.  (I can reproduce this again and get the
traceback again, if there is interest...

Since the welcome message didn't go out to everyone (according to the mail
logs),  I decided to remove everyone and re-run the welcome message with
like 15 people at a time (pausing 30 seconds between each one)

Could it be that load went up high enough to make sendmail stop accepting
connect9ons.?  Does Mailman deal with this case correctly after 1.0b9?



From gmelists at caffeine.sundial.net  Sun Apr 11 16:34:50 1999
From: gmelists at caffeine.sundial.net (gmelists)
Date: Sun, 11 Apr 1999 10:34:50 -0400 (EDT)
Subject: [Mailman-Users] Passwords
Message-ID: <Pine.BSF.4.05.9904111030420.10198-100000@caffeine.sundial.net>

I have a user who has forgotten the administrative password which was
setup for him.

Is there any way to retrieve it?

Also, as mailman-owner, is there a master-password where I can review, or
optionally make changes, to the mailing list configurations which
individual list-owners have setup?

Finally, a suggestion.  How difficult would it be to split up the database
into separate components.  One for general configuration, one for privacy
options, etc.  This would at least allow me to "lock out" any changes by
chown'ing the .db file and making it owned by root or whatever so user
mailman can't modify it; for example if I want a particular list to remain
not visibile in the listinfo either due to subject or whatever reason, and
I don't want the list-owner to accidentally set it public.




From bahwi at technologist.com  Sun Apr 11 19:44:37 1999
From: bahwi at technologist.com (bahwi)
Date: Sun, 11 Apr 1999 12:44:37 -0500 (CDT)
Subject: [Mailman-Users] Using a CGI Script to subscribe people.
Message-ID: <Pine.BSF.4.05.9904111239440.40986-100000@localhost>

I'm not a member of this list, please reply to me privately, thank you...
If this is the wrong list, accept my apology, and please tell me the
correct one.

I wish to know if it is possible, and how, to do this:

I have a CGI form, where people fill out some things, and the results are
sent to a file. We wish to add an option to this which says "Subscribe me
to the mailing list" and have a place for the address, and the
password/confirmation(since MailMan requires it). How can we take the
address from this file, or do something with this CGI script and
automatically subscribe the person. I just installed MailMan today, if
that will tell you my experience with it. Thank you.

--
bahwi at technologist.com




From trevor at jpj.net  Sun Apr 11 21:21:04 1999
From: trevor at jpj.net (Trevor Johnson)
Date: Sun, 11 Apr 1999 15:21:04 -0400 (EDT)
Subject: [Mailman-Users] Using a CGI Script to subscribe people.
In-Reply-To: <Pine.BSF.4.05.9904111239440.40986-100000@localhost>
Message-ID: <Pine.BSI.3.95.990411151620.26192D-100000@blues.jpj.net>

> I wish to know if it is possible, and how, to do this:

The "subscribe" program (which here is installed in ~mailman/cgi-bin/) is
for that.  For an example of a form that uses it, see
http://www.python.org/mailman/listinfo/mailman-users .
__
Trevor Johnson




From gconnor at nekodojo.org  Mon Apr 12 00:47:01 1999
From: gconnor at nekodojo.org (Greg Connor)
Date: Sun, 11 Apr 1999 15:47:01 -0700
Subject: [Mailman-Users] Possible bug, duplicate messages
Message-ID: <4.1.19990411152807.00cbf750@pop.nekodojo.org>

Hello.  This is the first day of activity on a new mailman list, changed
over last night from a Listproc list with 290 members.  Pretty standard
stuff...  our MTA is Sendmail 8.8.7. 

First few messages went OK, but one out of the first four message seems to
have gone out to everyone twice.  According to the logs, Mailman received
one copy and sent out two; maybe the first attempt gave Mailman an error or
other seizure... but nothing shows up in logs/error or logs/smtp-failures.

This is using 1.0b9, so apologies if this is already is found and fixed...
I don't remember seeing anything about it on the list yet though.  I
haven't turned on logging for mail.debug, which is probably the next step,
but I would only want to keep a debug log on for a short time for fear of
filling up my disk :)

I am also thinking this might be related to the problem that caused welcome
messages to fail for a mass-subscribe attempt (it works when I subscribe 15
at a time, but subbing 280 at a time caused add_members to barf and most of
the welcome messages to not go out).  Are there any config issues or things
to watch out for with Sendmail?  Has anyone seen a duplicate messages
problem before?


Here were the offending transactions 
Apr 11 14:11:38 poly sendmail[6992]: OAA06992: from=<thinkgreen at home.com>,
size=
2240, class=0, pri=32240, nrcpts=1,
msgid=<4.1.19990411083556.0372d3e0 at mail>, pr
oto=ESMTP, relay=imail at ha1.rdc1.sdca.home.com [24.0.3.66]

Apr 11 14:12:02 poly sendmail[7013]: OAA07013:
from=<poly-admin at polyamory.org>, 
size=2775, class=-60, pri=1670775, nrcpts=52,
msgid=<4.1.19990411083556.0372d3e0
@mail>, proto=ESMTP, relay=localhost [127.0.0.1]

Apr 11 14:12:02 poly sendmail[7021]: OAA07021:
from=<poly-admin at polyamory.org>, 
size=2775, class=-60, pri=1670775, nrcpts=52,
msgid=<4.1.19990411083556.0372d3e0
@mail>, proto=ESMTP, relay=localhost [127.0.0.1]




From gconnor at nekodojo.org  Mon Apr 12 01:10:28 1999
From: gconnor at nekodojo.org (Greg Connor)
Date: Sun, 11 Apr 1999 16:10:28 -0700
Subject: [Mailman-Users] Passwords
In-Reply-To: <Pine.BSF.4.05.9904111030420.10198-100000@caffeine.sundial.
 net>
Message-ID: <4.1.19990411155741.00bbfcd0@pop.nekodojo.org>

At 10:34 AM 4/11/99 -0400, gmelists wrote:
>Also, as mailman-owner, is there a master-password where I can review, or
>optionally make changes, to the mailing list configurations which
>individual list-owners have setup?

Yup, it's set with bin/mmsitepass, and you can use it in place of any other
admin password on your site.  

(I think this is in the INSTALL document... if you skimmed through it too
fast, you might want to check if there are other things that you may have
skipped, like setting the crontab--I missed that the first time)


>I have a user who has forgotten the administrative password which was
>setup for him.
>
>Is there any way to retrieve it?

I don't know of one, but I think you can reset it in the admin interface by
using your site password to get in, and again as the "old password".  Try it...


>Finally, a suggestion.  How difficult would it be to split up the database
>into separate components.  One for general configuration, one for privacy
>options, etc.  This would at least allow me to "lock out" any changes by
>chown'ing the .db file and making it owned by root or whatever so user
>mailman can't modify it; for example if I want a particular list to remain
>not visibile in the listinfo either due to subject or whatever reason, and
>I don't want the list-owner to accidentally set it public.


There is another approach that might be easier, because I suspect most
sites would not need this extra level of control...

Greg Stein posted this recipe for locking out "certain urls" in your Apache
config... This is different from locking out certain files, because it
allows you to set a password on certain "virtual paths" that are really
part of a script and not a physical directory.

><Location /mailman/private/the-archive>
>AuthName "admin-private archives"
>AuthType Basic
>AuthUserFile whatever
>Require user adminuser
></Location>
>

For "Location" you could just as easily put "/mailman/admin/list1/general"
- which would further restrict access to the "general" page, but not the
"members" page, for example.  Restriction could be an additional http
password, or only allowing certain IP's, or whatever.  See the Apache
manual for more info on the syntax for Require and AuthType...

Good luck!
gregc



From gconnor at nekodojo.org  Mon Apr 12 01:23:14 1999
From: gconnor at nekodojo.org (Greg Connor)
Date: Sun, 11 Apr 1999 16:23:14 -0700
Subject: [Mailman-Users] Addresses not being held
In-Reply-To: <3.0.1.32.19990324232117.0070bcc4@mail.wizard.net>
References: <01be7665$1fba9a90$1c7001c4@ntserver.sld.cu>
Message-ID: <4.1.19990411161243.00ca3a30@pop.nekodojo.org>

At 11:21 PM 3/24/99 -0500, John C. Broman, Jr. wrote:
>On the privacy page, I went to the section that's titled: "Addresses whose
>postings are always held for approval"  and I typed an address of a test
>account I have.  The address as I specified it is: xxxx at company.com.  Yet
>messages from this account are NOT being held.

At 11:36 PM 3/24/99 -0500, John C. Broman, Jr. wrote:
>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.


A common cause for *both* of these problems is the sendmail "feature" that
rewrites the Envelope address.  This only happens IF you are sending to an
alias "mylist" AND you also have an alias defined for "owner-mylist".  

This causes Sendmail to assume that you have an "aliases mailing list", and
rewrites the sender address (in the SMTP transaction, not in the headers)
to be whatever the owner-x address is.  The idea is that if the mailing
list is made up of just aliases or :include: lists, then you want the
"owner of the alias" to get the bounces, and not the original sender.
Unfortunately this screws with REAL mailing list managers, which behave as
though ALL the messages are coming from mylist-admin (and if mylist-admin
is not subscribed, his messages typically get held for approval or bounce
or whatever).

The workaround is to undefine "owner-*" for all your Mailman lists.  I
think Mailman uses "*-owner" or "*-admin" for everything anyway, which is
fine, only "owner-*" creates a problem.  Don't forget to run "newaliases"
after you do this.

(It's kind of strange for Mailman to emit "owner-*" aliases as part of the
recommended set... this means that installing the default, recommended
Sendmail and the default, recommended Mailman leaves you in a somewhat
broken state, when all you did was follow directions.  I would prefer
Mailman not suggest owner-* aliases at all.)



From James.Nicholson at amedd.army.mil  Mon Apr 12 02:30:28 1999
From: James.Nicholson at amedd.army.mil (Nicholson James D)
Date: Sun, 11 Apr 1999 20:30:28 -0400
Subject: [Mailman-Users] BUG(S):  Mailman ignoring setting of privacy
Message-ID: <BFDD20E1F489D21191C300104B99B7533DB669@dasmtaamp032.amedd.army.mil.92.131.in-addr.arpa>

> When you say 'From field', do you mean the header that looks like
> 
>    From: test2-admin at ncsa.uiuc.edu
> 
> or
> 
>    From test2-admin at ncsa.uiuc.edu  Sat Apr 10 00:48:53 1999
> 
> (basically, the envelope sender or the From: header)?
> 
	[Nicholson James D]  Here's what I received from a test message to
my test lists.  My PC is being used to post to the list and I use qpopper to
pop mail from the IRIX machine.:

					Received: 
	                         from <IRIX machine name> ([<IP of my PC>])
by <IRIX Machine name>
	                         (950413.SGI.8.6.12/950213.SGI.AUTOCF) via
ESMTP id XAA18532 for
	                         <lightchain@<IRIX Machine Name>>; Sun, 10
Apr 1999 23:49:20 -0500
	              Message-ID: <370ECDCD.D6F9C112@<IRIX Machine Name>>
	                    Date:  Sat, 10 Apr 1999 00:04:29 -0400
	                    From: Jim <jim>

	As you can see, the From: field is directed back at me even though I
used the admin privacy option to send it back to the list.
	I think Microsoft Outlook [hisssssss] looks at the From: line to
figure out where to reply to.  So, I need to make that From: line say
listname at machine.name.  I am assuming that that is what the privacy option
to redirect mail to the list was intended to do.

>  
> 
>    o Changed nobody uid/gid to 65534 to match mailman settings
> 
	[Nicholson James D]  
	 My mailman is set up to be uid/gid 2001/50 with appropriate group
entry.  Why are you setting nobody to match mailman settings?  Won't this
cause security problems down the line if someone can access your machine as
nobody?
	  
>    
> Then I added these directives to httpd.conf *exactly* as they appear
> below.
> 
	[Nicholson James D]  
	Thanks for the tip.  This set of commands was not in httpd.conf.  It
made a difference.  It was also not mentioned in the docs for mailman.
Adding these allowed me to access mailman and still to deny a directory
listing.

>    <Directory /home/staff/mailman/cgi-bin/>
>       Allow from all
>       Options SymLinksIfOwnerMatch ExecCGI
>    </Directory>
> 
>    ScriptAlias /mailman/ /home/staff/mailman/cgi-bin/
> 
> 
	[Nicholson James D]  
	Now the reason you have to include both
	ScriptAlias /mailman/  ......   & ScriptAlias /~mailman/ ...... is
not because /mailman/ doesn't work.  It works fine.  The problem is that the
message that was sent out to new subscribers said to access the web
interface at http://<machine name>/~mailman/listinfo/<listname>.  You can
have it either way, but I was confused by the other URL being sent to my
test accounts.  So, I suppose I can have both of them there.  It doesn't
seem to hurt anything.




From lindsey at ncsa.uiuc.edu  Mon Apr 12 05:03:15 1999
From: lindsey at ncsa.uiuc.edu (Christopher Lindsey)
Date: Sun, 11 Apr 1999 22:03:15 -0500 (CDT)
Subject: [Mailman-Users] BUG(S):  Mailman ignoring setting of privacy
In-Reply-To: <BFDD20E1F489D21191C300104B99B7533DB669@dasmtaamp032.amedd.army.mil.92.131.in-addr.arpa> from "Nicholson James D" at Apr 11, 99 08:30:28 pm
Message-ID: <199904120303.WAA20285@ferret.ncsa.uiuc.edu>

A non-text attachment was scrubbed...
Name: not available
Type: text
Size: 1910 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-users/attachments/19990411/84b790fd/attachment.pot 

From claw at kanga.nu  Mon Apr 12 07:09:14 1999
From: claw at kanga.nu (claw at kanga.nu)
Date: Sun, 11 Apr 1999 22:09:14 -0700
Subject: [Mailman-Users] Passwords 
In-Reply-To: Message from gmelists <gmelists@caffeine.sundial.net> 
   of "Sun, 11 Apr 1999 10:34:50 EDT." <Pine.BSF.4.05.9904111030420.10198-100000@caffeine.sundial.net> 
Message-ID: <E10WYyA-0002W1-00@koala.kanga.nu>

On Sun, 11 Apr 1999 10:34:50 -0400 (EDT) 
gmelists  <gmelists at caffeine.sundial.net> wrote:

> Finally, a suggestion.  How difficult would it be to split up the
> database into separate components.  One for general configuration,
> one for privacy options, etc.  This would at least allow me to
> "lock out" any changes by chown'ing the .db file and making it
> owned by root or whatever so user mailman can't modify it; for
> example if I want a particular list to remain not visibile in the
> listinfo either due to subject or whatever reason, and I don't
> want the list-owner to accidentally set it public.

A more general solution, which I'd *really* like for some
applications, is the ability for the site-owner to define a template
of options which then defines the defaults for all subsequently
created lists, and to be able to define each so-defined
configuration option as "locked" or not -- defining whether the list
owner can edit the value or not.  The final coup de grace would be
if upon subsequent editing of the master template, if all lists
whose owners had not edited those particular configuration values,
changed automagically to match the new site defaults.

-- 
J C Lawrence                              Internet: claw at kanga.nu
----------(*)                            Internet: coder at kanga.nu
...Honorary Member of Clan McFud -- Teamer's Avenging Monolith...



From gorgo at caesar.elte.hu  Mon Apr 12 13:05:52 1999
From: gorgo at caesar.elte.hu (Gergely Madarasz)
Date: Mon, 12 Apr 1999 13:05:52 +0200 (METDST)
Subject: [Mailman-Users] Possible bug, duplicate messages
In-Reply-To: <4.1.19990411152807.00cbf750@pop.nekodojo.org>
Message-ID: <Pine.A32.3.96.990412130340.3306P-100000@caesar.power.elte.hu>

On Sun, 11 Apr 1999, Greg Connor wrote:

> 
> Hello.  This is the first day of activity on a new mailman list, changed
> over last night from a Listproc list with 290 members.  Pretty standard
> stuff...  our MTA is Sendmail 8.8.7. 

This is possibly not your problem but you might encounter it later, so
here is a warning:
Sendmail 8.8.7 has a bug, and mailmans mime digests may easily trigger it
-> sendmail segfaults, some mails delivered multiple times, some digests
never arriving. There is a patch for 8.8.X, and the fix is included in
8.9.x

-- 
Madarasz Gergely           gorgo at caesar.elte.hu         gorgo at linux.rulez.org
      It's practically impossible to look at a penguin and feel angry.
          Egy pingvinre gyakorlatilag lehetetlen haragosan nezni.
                    HuLUG: http://mlf.linux.rulez.org/




From allen at chesapeake.tokheim.com  Mon Apr 12 14:57:21 1999
From: allen at chesapeake.tokheim.com (Marc L. Allen)
Date: Mon, 12 Apr 1999 08:57:21 -0400
Subject: [Mailman-Users] REPLY-TO oddity
References: <370EB923.1B10FB84@lyra.org>
		<199904100647.AAA15743@ns.kinfolk.org> <14095.60793.446584.692130@anthem.cnri.reston.va.us>
Message-ID: <3711EDB1.2E456F6B@chesapeake.tokheim.com>

But.. I'm afraid the original thread was lost here.

My ORIGINAL question was why, when setting a list to have replies sent
to it (which causes Mailman to issue the REPLY-TO: field), Mailman uses
the name of the list machine instead of the correct list address.

For instance, (and I'll make up some addresses), let's say I've got a
mail server called mail.generic.net.  Now, I want to run lists, so I
create a maillist DNS entry pointing to mail.generic.net, but I call it
maillist.generic.net.  I do this, because I may want to move the
maillist server to another machine and I don't want to break the
maillist addresses.  At the moment, though, I want Mailman running on
the same machine as the mail server.

When I create a new list and I want replys to go to that list, I'll get
the following headers:

	From:		"Marc L. Allen" <allen at chesapeake.tokheim.com>
	Reply-To:	listname at mail.generic.net
	To:		listname at maillist.generic.net

Now, I don't know if this is Mailman doing this, or my particular
sendmail setup.  So, I posed the question.  If it IS Mailman, I want to
know why is doesn't use the list address, which is certainly knows.

Thanks,

Marc


"Barry A. Warsaw" wrote:
> 
> There's really no point in arguing this anymore.  Mailman lets list
> admins munge Reply-To: if they want, but I think we are justified in
> discouraging it.
> 
> -Barry
> 
> ------------------------------------------------------
> Mailman-Users maillist  -  Mailman-Users at python.org
> http://www.python.org/mailman/listinfo/mailman-users

-- 
************************************************************************
* Marc L. Allen                         *                              *
* Principal Architect                   * "If we had told you it was   *
* Information Technology Manager        * impossible, you'd never have *
*                                       * gone off and done it."       *
* Tokheim Technology Center             *                              *
* (757) 366-4185                        *    -- The Phantom Tollbooth  *
* allen at chesapeake.tokheim.com          *                              *
************************************************************************



From gmelists at caffeine.sundial.net  Mon Apr 12 16:07:07 1999
From: gmelists at caffeine.sundial.net (gmelists)
Date: Mon, 12 Apr 1999 10:07:07 -0400 (EDT)
Subject: [Mailman-Users] Msgs. from subscribers requiring approval?
Message-ID: <Pine.BSF.4.05.9904121002420.13911-100000@caffeine.sundial.net>

Is there anything that would prevent a message from
gme at caffeine.sundial.net from being disbursed when
gme at caffeine.sundial.net is a subscriber?

This test message, which was originally sent on Apr 9, was sent from
Eudora Pro 4.1 which possibly had an "X-Sender: gme at 10.0.0.1" since that
machine was behind a firewall, however, I sent another message directly
from caffeine.sundial.net using Pine and still encountered the same thing.

Any ideas?

TIA!

---------- Forwarded message ----------
Received: from sundial.sundial.net (sundial.sundial.net [204.181.150.2])
	by caffeine.sundial.net (8.9.2/8.9.1) with ESMTP id JAA13776
	for <gme at caffeine.sundial.net>; Mon, 12 Apr 1999 09:42:13 -0400 (EDT)
	(envelope-from ocso-test-admin at lists.sundial.net)
Received: from sundial.sundial.net (localhost [127.0.0.1])
	by sundial.sundial.net (Postfix) with ESMTP id 5399F88064
	for <gme at caffeine.sundial.net>; Mon, 12 Apr 1999 09:41:54 -0400 (EDT)
Delivered-To: ocso-test at lists.sundial.net
Received: from caffeine.sundial.net (caffeine.sundial.net [204.181.150.5])
	by sundial.sundial.net (Postfix) with ESMTP id C8A0E8800F
	for <ocso-test at lists.sundial.net>; Fri,  9 Apr 1999 20:02:45 -0400 (EDT)
Received: from localhost (gme at localhost)
	by caffeine.sundial.net (8.9.2/8.9.1) with ESMTP id UAA01487
	for <ocso-test at lists.sundial.net>; Fri, 9 Apr 1999 20:02:55 -0400 (EDT)
	(envelope-from gme at caffeine.sundial.net)
Date: Fri, 9 Apr 1999 20:02:55 -0400 (EDT)
From: George Ellenburg <gme at caffeine.sundial.net>
To: ocso-test at lists.sundial.net
Subject: [ocso-test] Test Message
Message-ID: <Pine.BSF.4.05.9904092002440.1485-100000 at caffeine.sundial.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: ocso-test at lists.sundial.net
Sender: ocso-test-admin at lists.sundial.net
Errors-To: ocso-test-admin at lists.sundial.net
X-Mailman-Version: 1.0b11
Precedence: bulk
List-Id: Test list for Sgt. Stenger to get used to MailMan
    <ocso-test.lists.sundial.net>
X-BeenThere: ocso-test at lists.sundial.net

This is the header which is added to the messages.
--------------------------------------------------
Test Message





_______________________________________________
ocso-test maillist  -  ocso-test at lists.sundial.net
http://lists.sundial.net/mailman/listinfo/ocso-test






From lindsey at ncsa.uiuc.edu  Mon Apr 12 16:42:28 1999
From: lindsey at ncsa.uiuc.edu (Christopher Lindsey)
Date: Mon, 12 Apr 1999 09:42:28 -0500 (CDT)
Subject: [Mailman-Users] Msgs. from subscribers requiring approval?
In-Reply-To: <Pine.BSF.4.05.9904121002420.13911-100000@caffeine.sundial.net> from "gmelists" at Apr 12, 99 10:07:07 am
Message-ID: <199904121442.JAA23758@ferret.ncsa.uiuc.edu>

A non-text attachment was scrubbed...
Name: not available
Type: text
Size: 520 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-users/attachments/19990412/e8271afb/attachment.asc 

From gconnor at nekodojo.org  Mon Apr 12 16:52:12 1999
From: gconnor at nekodojo.org (Greg Connor)
Date: Mon, 12 Apr 1999 07:52:12 -0700
Subject: [Mailman-Users] Bounce not caught
Message-ID: <4.1.19990412074728.00921220@pop.nekodojo.org>

Should we be reporting it as a bug, if we get a bounce message that wasn't
caught by the automatic bounce processor?  Is there a way to adjust
Mailman's bounce detectors?

Anyway, this wasn't being flagged as a bounce, and instead went to the
admin address.

Thanks
gregc

To: poly-admin at polyamory.org
From: Mail Administrator <postmaster at camb-mail.kenan.com>
Reply-To: Mail Administrator <postmaster at camb-mail.kenan.com>
Received: from camb-mail.kenan.com by ext-nic
          via smtpd (for poly.polyamory.org [206.169.151.198]) with SMTP;
12 Apr 1999 12:53:45 UT
Subject: Mail System Error - Returned Mail
Date: Mon, 12 Apr 1999 08:43:25 -0400
Message-ID: <19990412124325734.AAA434.335 at camb-mail.kenan.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
		Boundary="===========================_ _= 7658081(434.335)"
Content-Transfer-Encoding: 7BIT
X-UIDL: 6dc8c52e421c8b7a051a5c93539f69ad
Status: O
X-Status: 

This Message was undeliverable due to the following reason:

A message was not delivered to one or more recipients because of the
following reason(s):

Couldn't open User Account joeuser

Please reply to postmaster at camb-mail.kenan.com
if you feel this message to be in error.
Received: from acme ([198.187.250.254]) by camb-mail.kenan.com
          (Netscape Messaging Server 3.6)  with ESMTP id 623
          for <joeuser at kenan.com>; Sun, 11 Apr 1999 22:29:02 -0400
Received: from camb-exch1.kenan.com (camb-exch1 [198.187.250.58])
	by acme (8.8.6/8.8.6) with ESMTP id WAA27508
	for <joeuser at kenan.com>; Sun, 11 Apr 1999 22:41:03 -0400
Received: by camb-exch1.kenan.com with Internet Mail Service (5.5.2232.9)
	id <HTJ3LA19>; Sun, 11 Apr 1999 22:37:54 -0400
Received: from portal.kenan.com ([198.187.251.254]) by camb-exch1.kenan.com
with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9)
	id HTJ3LA18; Sun, 11 Apr 1999 22:37:51 -0400
Received: from acestes-fe0.ultra.net ([199.232.56.54]) by portal.kenan.com
          via smtpd (for CAMB-EXCH1 [198.187.250.58]) with SMTP; 12 Apr
1999 02:39:10 UT
Received: from poly.polyamory.org (poly.polyamory.org [206.169.151.198]) by
acestes-fe0.ultra.net (8.8.8/ult/n20340/mtc.v2) with ESMTP id WAA21766;
Sun, 11 Apr 1999 22:39:06 -0400 (EDT)
Received: from poly.polyamory.org (localhost [127.0.0.1])
	by poly.polyamory.org (8.8.7/8.8.7) with ESMTP id TAA11327;
	Sun, 11 Apr 1999 19:35:51 -0700




From bwarsaw at cnri.reston.va.us  Mon Apr 12 16:53:25 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Mon, 12 Apr 1999 10:53:25 -0400 (EDT)
Subject: [Mailman-Users] Mailman FAQ on web page is clobbered by HTML
References: <ytt1zhrput9.fsf@gilgamesh.cse.ucsc.edu>
Message-ID: <14098.2277.345085.892636@anthem.cnri.reston.va.us>

>>>>> "BG" == Ben Gertzfield <che at debian.org> writes:

    BG> et cetera, except when this is changed to HTML, the < and >
    BG> are not changed to &lt; and &gt; so the <listname> bits are
    BG> totally invisible! Oops! This should probably be fixed.

Thanks, I've just fixed this.  I'll upload soon.
-Barry



From lindsey at ncsa.uiuc.edu  Mon Apr 12 16:57:28 1999
From: lindsey at ncsa.uiuc.edu (Christopher Lindsey)
Date: Mon, 12 Apr 1999 09:57:28 -0500 (CDT)
Subject: [Mailman-Users] Hypermail integration
In-Reply-To: <m36778b8in.fsf@gw.rupa.com> from "Rupa Schomaker" at Apr 7, 99 11:17:04 am
Message-ID: <199904121457.JAA23881@ferret.ncsa.uiuc.edu>

A non-text attachment was scrubbed...
Name: not available
Type: text
Size: 247 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-users/attachments/19990412/8e536d07/attachment.pot 

From jerrya at fastrans.net  Mon Apr 12 17:21:27 1999
From: jerrya at fastrans.net (Jerry Adlersfluegel)
Date: Mon, 12 Apr 1999 10:21:27 -0500
Subject: [Mailman-Users] Bounce not caught
References: <4.1.19990412074728.00921220@pop.nekodojo.org>
Message-ID: <37120F77.1AC257C2@fastrans.net>

Greg Connor wrote:
> 
> Should we be reporting it as a bug, if we get a bounce message that wasn't
> caught by the automatic bounce processor?  Is there a way to adjust
> Mailman's bounce detectors?
> 
> Anyway, this wasn't being flagged as a bounce, and instead went to the
> admin address.

I see similar bounces from webtv users when their mailboxes are full. I
don't have one handy, but I could probably find one.



From gmelists at caffeine.sundial.net  Mon Apr 12 19:08:51 1999
From: gmelists at caffeine.sundial.net (gmelists)
Date: Mon, 12 Apr 1999 13:08:51 -0400 (EDT)
Subject: [Mailman-Users] Msgs. from subscribers requiring approval?
In-Reply-To: <199904121442.JAA23758@ferret.ncsa.uiuc.edu>
Message-ID: <Pine.BSF.4.05.9904121307020.14389-100000@caffeine.sundial.net>

Thanks for your reply.

I'm running 1.0b11.  Just changed the following options under privacy:
(paraphrased)
	Posts approved by administrator: no
	Restrict posts to list members only: yes

Send another message from gme at caffeine.sundial.net, and got the following:
Postings from member addresses only.

        :-(

On Mon, 12 Apr 1999, Christopher Lindsey wrote:

> > Is there anything that would prevent a message from
> > gme at caffeine.sundial.net from being disbursed when
> > gme at caffeine.sundial.net is a subscriber?
> 
> I would check to see if
> 
>    o you're using the envelope address instead of the From:
>      address, but it's getting munged on your system (what
>      version are you using?  If 1.0b10 or later, try defining
>      USE_ENVELOPE_SENDER = 0 in $prefix/Mailman/mm_cfg.py).
>    o the list is moderated
>    o the headers match a regex that isn't allowed
> 
> Chris
> 
> ------------------------------------------------------
> Mailman-Users maillist  -  Mailman-Users at python.org
> http://www.python.org/mailman/listinfo/mailman-users
> 
> 




From sms at netconcepts.com  Tue Apr 13 01:58:12 1999
From: sms at netconcepts.com (Stephan Spencer)
Date: Mon, 12 Apr 1999 18:58:12 -0500 (CDT)
Subject: [Mailman-Users] Re: Usenet gating and archiving
Message-ID: <Pine.GSO.4.02.9904121834270.2893-100000@nexus.netconcepts.com>

We're using Mailman to gateway a Usenet newsgroup and email list. I'm
curious, is that "severe breakage" in the archives that Barry Warsaw
mentioned in his Apr 2 post fixed yet?

What Usenet newsgroups out there are being successfully moderated using
Mailman? misc.industry.printing is the only one that I know of.

Also on the topic of moderating, it would be really useful if we could set
up one or more "stationery" replies, which the moderator would choose from
if rejecting a post (i.e. through a pulldown), rather than having to type
in the responses to rejections over and over again. It would be ideal if
the moderator could select a stationery from a pulldown, then once the
appropriate stationery has been selected, the textarea would display that
stationery response, which the moderator could tweak if s/he wanted to. If
the moderator selected the "no stationery" option from the pulldown, then
s/he could type in whatever they wanted into the textarea or leave it
blank. If I knew Python, I'd help you guys build this functionality...

As an interim solution, I've gone in to the code that displays the "If you
reject this post, explain" textarea and modified it to include a "Thank
you but we're sorry..." message along with a link to the group charter
inside the textarea. In fact, it might be a good idea to have a variable
where such a message can be defined, but which could be defined
differently for each list that is being moderated. Such a solution would
not be the "ideal" stationery solution, but it would still be a timesaver. 
Just a thought...

Cheers,
Stephan




From che at debian.org  Tue Apr 13 02:27:15 1999
From: che at debian.org (Ben Gertzfield)
Date: 12 Apr 1999 17:27:15 -0700
Subject: [Mailman-Users] Re: Usenet gating and archiving
In-Reply-To: Stephan Spencer's message of "Mon, 12 Apr 1999 18:58:12 -0500 (CDT)"
References: <Pine.GSO.4.02.9904121834270.2893-100000@nexus.netconcepts.com>
Message-ID: <yttu2ul5pr0.fsf@gilgamesh.cse.ucsc.edu>

>>>>> "Stephan" == Stephan Spencer <sms at netconcepts.com> writes:

    Stephan> We're using Mailman to gateway a Usenet newsgroup and
    Stephan> email list. I'm curious, is that "severe breakage" in the
    Stephan> archives that Barry Warsaw mentioned in his Apr 2 post
    Stephan> fixed yet?

I noticed that using 1.0b9, newsgroup mirroring and archiving was
totally busted because messages did not start with "From " (notice
space, not :). I upgraded to 1.0b11 and the problem seemed to go
away..

-- 
Brought to you by the letters P and F and the number 14.
"You have my pills!"
Debian GNU/Linux maintainer of Gimp and GTK+ -- http://www.debian.org/
I'm on FurryMUCK as Che, and EFNet/Open Projects IRC as Che_Fox.



From gconnor at nekodojo.org  Tue Apr 13 05:25:20 1999
From: gconnor at nekodojo.org (Greg Connor)
Date: Mon, 12 Apr 1999 20:25:20 -0700
Subject: [Mailman-Users] Msgs. from subscribers requiring approval?
In-Reply-To: <Pine.BSF.4.05.9904121307020.14389-100000@caffeine.sundial.
 net>
References: <199904121442.JAA23758@ferret.ncsa.uiuc.edu>
Message-ID: <4.1.19990412201317.009f8ee0@pop.nekodojo.org>

At 01:08 PM 4/12/99 -0400, gmelists wrote:
>Thanks for your reply.
>
>I'm running 1.0b11.  Just changed the following options under privacy:
>(paraphrased)
>	Posts approved by administrator: no
>	Restrict posts to list members only: yes
>
>Send another message from gme at caffeine.sundial.net, and got the following:
>Postings from member addresses only.
>
>        :-(


Your logs/vette file should tell you who mailman *thinks* the message is
from.  Looking here won't solve the problem, but it may tell you where to go.

If mailman thinks the post is from "gme at caffeine.sundial.net", then maybe
there is a bug somewhere.  (Make sure your subscription was for this same
address, including being all lower case).

If mailman thinks your address is gme at caffeine or gme at localhost, configure
your mailer to always send your full domain (did you send to the list using
its full qualified name?)

If mailman thinks  your address is ocso-test-admin at lists.sundial.net, this
is a sendmail "feature".  See previous posting at 
  http://www.python.org/pipermail/mailman-users/1999-April/001091.html

In any case, watching the log (vette and posts) should help you determine
if there's a pattern to the madness :)

good luck



From david at csol.com  Tue Apr 13 23:23:53 1999
From: david at csol.com (David Corbin)
Date: Tue, 13 Apr 1999 17:23:53 -0400
Subject: [Mailman-Users] Can I rename a mailing list?
Message-ID: <3713B5E9.B3A41036@csol.com>

if so, how can I do it?

Thanks.
-- 
David Corbin 		
Corsol Corporation
http://www.csol.com
dcorbin at csol.com



From trevor at jpj.net  Wed Apr 14 01:36:39 1999
From: trevor at jpj.net (Trevor Johnson)
Date: Tue, 13 Apr 1999 19:36:39 -0400 (EDT)
Subject: [Mailman-Users] Can I rename a mailing list?
In-Reply-To: <3713B5E9.B3A41036@csol.com>
Message-ID: <Pine.BSI.3.95.990413193145.15417C-100000@blues.jpj.net>

> if so, how can I do it?

You could browse the output of the "admin" program (for example: 
http://www.list.org/mailman/admin/foo or .../spam), log in, and type
something in the "public name" box. 
__
Trevor Johnson




From jonathan at NrgUp.Com  Wed Apr 14 05:45:40 1999
From: jonathan at NrgUp.Com (Jonathan Bradshaw)
Date: Tue, 13 Apr 1999 22:45:40 -0500
Subject: [Mailman-Users] Suggestion
Message-ID: <19990413224540.A2225@NrgUp.Com>

I have a suggestion to allow either a user-configurable filter or allow the
implementation of a filter for "included content" like many Usenet posting
programs have. I'm sick of posters including a whole digest to make a 2 line
reply.

-- 
 Jonathan Bradshaw <Jonathan at NrgUp.Com> | Novell 4.x CNE | Ham Callsign N9OXE
          "...I'm not one of those who think Bill Gates is the devil.
         I simply suspect that if Microsoft ever met up with the devil,
              it wouldn't need an interpreter."  -- Nick Petreley



From harri.nyman at sonera.fi  Wed Apr 14 07:41:01 1999
From: harri.nyman at sonera.fi (Harri Nyman)
Date: Wed, 14 Apr 1999 08:41:01 +0300
Subject: [Mailman-Users] listinfo - no lists???
Message-ID: <003f01be8639$612587e0$29fcfbc2@tmt.tele.fi>

Interesting headache, listinfo in 1.0b11 doesn't show any of my public
lists, when admin shows them ok - any suggestions? System is RedHat
linux 5.2 with Python 1.5.1

--------
Harri Nyman                  +358-40-5587434
Systems Specialist         harri.nyman at sonera.fi
Sonera Corp.




From gconnor at nekodojo.org  Wed Apr 14 08:09:50 1999
From: gconnor at nekodojo.org (Greg Connor)
Date: Tue, 13 Apr 1999 23:09:50 -0700
Subject: [Mailman-Users] Can I rename a mailing list?
In-Reply-To: <Pine.BSI.3.95.990413193145.15417C-100000@blues.jpj.net>
References: <3713B5E9.B3A41036@csol.com>
Message-ID: <4.1.19990413230822.00cefbb0@pop.nekodojo.org>

At 07:36 PM 4/13/99 -0400, Trevor Johnson wrote:
>> if so, how can I do it?
>
>You could browse the output of the "admin" program (for example: 
>http://www.list.org/mailman/admin/foo or .../spam), log in, and type
>something in the "public name" box. 


Does this really work?  It says "make case changes only" so I would think
there is a reason not to do it this way.

One sure way to do it would be to remove the list and re-create it with the
new name.



From gstein at lyra.org  Wed Apr 14 08:54:23 1999
From: gstein at lyra.org (Greg Stein)
Date: Tue, 13 Apr 1999 23:54:23 -0700
Subject: [Mailman-Users] listinfo - no lists???
References: <003f01be8639$612587e0$29fcfbc2@tmt.tele.fi>
Message-ID: <37143B9F.3D08C768@lyra.org>

Harri Nyman wrote:
> 
> Interesting headache, listinfo in 1.0b11 doesn't show any of my public
> lists, when admin shows them ok - any suggestions? System is RedHat
> linux 5.2 with Python 1.5.1

Mailman is probably using virtual hosting. Visit the listinfo page using
the URL base that you typed into the "General Options" page and it
should show up.

Alternatively, you can turn off virtual hosting in the configuration
file, via the VIRTUAL_HOST_OVERVIEW flag.

Cheers,
-g

--
Greg Stein, http://www.lyra.org/



From lindsey at ncsa.uiuc.edu  Wed Apr 14 11:57:37 1999
From: lindsey at ncsa.uiuc.edu (Christopher Lindsey)
Date: Wed, 14 Apr 1999 04:57:37 -0500 (CDT)
Subject: [Mailman-Users] Can I rename a mailing list?
In-Reply-To: <4.1.19990413230822.00cefbb0@pop.nekodojo.org> from "Greg Connor" at Apr 13, 99 11:09:50 pm
Message-ID: <199904140957.EAA05006@ferret.ncsa.uiuc.edu>

A non-text attachment was scrubbed...
Name: not available
Type: text
Size: 563 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-users/attachments/19990414/2d8a8f90/attachment.asc 

From ian at chiark.greenend.org.uk  Wed Apr 14 13:13:20 1999
From: ian at chiark.greenend.org.uk (Ian Jackson)
Date: Wed, 14 Apr 1999 12:13:20 +0100 (BST)
Subject: [Mailman-Users] Find out a list admin password ?
Message-ID: <14100.30800.980013.600338@chiark.greenend.org.uk>

I've just installed mailman (1.0b8, Debian GNU/Linux revison 3).

I created a test list, and due to me not having set up the mail alias
for mailman-owner correctly before hitting `return' at the prompt,
mailman wasn't able to send the mail containing the admin password to
the listowner.

I have two questions:

1. Are the mailman developers aware that mailman can lose mail ?  The
message which mailman tried to send (via SMTP) was rejected by my
local Exim because the sender was wrong, and the only trace I can now
find of it is in the various error logs.  The message body is nowhere
to be found.

2. What is the published, documented way of finding out or resetting
a list owner password ?  I can probably dig into python and get it out
that way, but I would like a proper published interface ?

3. What is the site admin password for ?  I deduce its existence from
the presence of a program to set it ...

In general I have a feeling that I'm missing some of the
documentation.  I can't find a general manual on www.list.org, and
I would have expected to find information like the answers to the
questions above in the manual.  So, what is the canonical starting
point for mailman documentation ?

I don't want to offend anyone by implying I think mailman isn't a good
program, and I realise of course that beta software might not have a
completely complete manual or might not always be able to rescue the
text of undeliverable mail messages.

However, I'd like to understand what the issues are with mailman, so
that I can solve them before I move the lists on my system to mailman
from majordomo.

Ian.



From Andy.Carpenter at cs.man.ac.uk  Wed Apr 14 13:28:08 1999
From: Andy.Carpenter at cs.man.ac.uk (Andy Carpenter)
Date: Wed, 14 Apr 1999 12:28:08 +0100
Subject: [Mailman-Users] Find out a list admin password ?
Message-ID: <007201be8669$e0171610$62c15882@dugong.cs.man.ac.uk>

>2. What is the published, documented way of finding out or resetting
>a list owner password ?  I can probably dig into python and get it out
>that way, but I would like a proper published interface ?


Anywhere that a password is required the site password can be
entered.  So providing that you have set it, go one of the
administative pages for you list can scroll to the bottom where the
list password can be chaned.  Enter the site password as the
old password and set a new one and then submit the page.

>3. What is the site admin password for ?  I deduce its existence from
>the presence of a program to set it ...


See above

>In general I have a feeling that I'm missing some of the
>documentation.  I can't find a general manual on www.list.org, and
>I would have expected to find information like the answers to the
>questions above in the manual.  So, what is the canonical starting
>point for mailman documentation ?


Mailman is undergoing development.  If you look on the TODO list,
you will see that writing improved documentation is there.  At the
moment use the FAQ.

    Andy.
-- -------------------------------------------------------------------------
--------
Dr Andy Carpenter
Department of Computer Science, University of Manchester, Manchester M13
9PL, UK
Email: Andy.Carpenter at cs.man.ac.uk Tel: +44 161 275 6168 Fax: +44 161 275
6280




From klm at digicool.com  Wed Apr 14 17:10:13 1999
From: klm at digicool.com (Ken Manheimer)
Date: Wed, 14 Apr 1999 11:10:13 -0400
Subject: [Mailman-Users] RE: Mailman-Users digest, Vol 1 #178 - 3 msgs
Message-ID: <613145F79272D211914B0020AFF640190BEE60@gandalf.digicool.com>

On tuesday, David Corbin wrote:

> Subject: [Mailman-Users] Can I rename a mailing list?
> 
> if so, how can I do it?

You can't rename a list (beyond changing the case of the letters in the
public name - you should not change any more or it will break things).
However, you can use mailman's bin/list_members script to enumerate all
the members of a list, and then use the bin/add_members script to
populate a new list with those members.

'~mailman/list_members --help' and '~mailman/add_members --help' will
tell you how they're each used.  Note that you'll need to put the
regular and the digest member lists in separate files (or run in
separate passes, if you just pipe the commands together) if you want to
preserve that status.

Ken Manheimer
klm at digicool.com



From scott at whoi.edu  Wed Apr 14 17:32:06 1999
From: scott at whoi.edu (Scott A. McIntyre)
Date: Wed, 14 Apr 1999 11:32:06 -0400
Subject: [Mailman-Users] 'Too many recipients.'
Message-ID: <3714B4F6.78F59F20@whoi.edu>

Hi,


What would generate the 'Too many recipients.' error?

At first I thought it was the value of the ceiling in the privacy
configuration, but I have some lists with 70+ users and never get the
error.

The ceiling seems to be set at "10" by default.

Thanks,

Scott



From sdinn at spine.cx  Wed Apr 14 18:02:15 1999
From: sdinn at spine.cx (Steve Dinn)
Date: Wed, 14 Apr 1999 13:02:15 -0300 (ADT)
Subject: [Mailman-Users] 'Too many recipients.'
In-Reply-To: <3714B4F6.78F59F20@whoi.edu>
Message-ID: <Pine.LNX.4.05.9904141259080.14825-100000@spine.cx>

On Wed, 14 Apr 1999, Scott A. McIntyre wrote:
> What would generate the 'Too many recipients.' error?

This is caused by having too many addresses in the To: or Cc: (or
Bcc: ?) fields of your email.  If the email sent to the list also has n
address in these fields, you'll get a "Too many recipients" message.  It
has nothing to do with the number of people on a given list.

--
 Steve Dinn                       email:  mailto:sdinn at spine.cx
                                    www:  http://users.andara.com/~sdinn

       "Save the whales.  Feed the hungry.  Free the mallocs."




From claw at varesearch.com  Wed Apr 14 20:02:02 1999
From: claw at varesearch.com (J C Lawrence)
Date: Wed, 14 Apr 1999 11:02:02 -0700
Subject: [Mailman-Users] 'Too many recipients.' 
In-Reply-To: Message from "Scott A. McIntyre" <scott@whoi.edu> 
   of "Wed, 14 Apr 1999 11:32:06 EDT." <3714B4F6.78F59F20@whoi.edu> 
Message-ID: <E10XTz8-0008DH-00@under.varesearch.com>

On Wed, 14 Apr 1999 11:32:06 -0400 
Scott A McIntyre <scott at whoi.edu> wrote:

> What would generate the 'Too many recipients.' error?

Many MTA's can be configured to deny posts which are addressed to
more than X recipients.  Usually this is used as a form of SPAM
detection/prevention, or as a method of forcing bulkmail (such as
list postings) to go thru an MTA configured for that load.

MailMan ouputs messages with (guesstimate) 100 recipiants per
message.  If the MTA that MailMan is talking to has such a limit,
you'll get that error.

-- 
J C Lawrence                              Internet: claw at kanga.nu
---------(*)                        Internet: claw at varesearch.com
...Honorary Member of Clan McFud -- Teamer's Avenging Monolith...



From lindsey at ncsa.uiuc.edu  Wed Apr 14 20:21:09 1999
From: lindsey at ncsa.uiuc.edu (Christopher Lindsey)
Date: Wed, 14 Apr 1999 13:21:09 -0500 (CDT)
Subject: [Mailman-Users] 'Too many recipients.'
In-Reply-To: <E10XTz8-0008DH-00@under.varesearch.com> from "J C Lawrence" at Apr 14, 99 11:02:02 am
Message-ID: <199904141821.NAA07540@ferret.ncsa.uiuc.edu>

A non-text attachment was scrubbed...
Name: not available
Type: text
Size: 764 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-users/attachments/19990414/fc9eadaf/attachment.pot 

From sucher at ust.hk  Thu Apr 15 13:22:11 1999
From: sucher at ust.hk (Nikolaus J. Sucher)
Date: Thu, 15 Apr 1999 19:22:11 +0800
Subject: [Mailman-Users] Python 1.5.2
Message-ID: <3715CBE3.A159A34C@ust.hk>

Hi there,

I upgraded to Python 1.5.2 and now my webbrowser only returns :"the
requested URL /mailman/admin/xxx was not found on this server"

Did I make a mistake with the upgrade or is this a problem with
mailman??

Your help is greatly appreciated!

Nikolaus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sucher.vcf
Type: text/x-vcard
Size: 427 bytes
Desc: Card for Nikolaus J. Sucher
Url : http://mail.python.org/pipermail/mailman-users/attachments/19990415/5d41e939/attachment.vcf 

From James.Nicholson at amedd.army.mil  Thu Apr 15 17:39:28 1999
From: James.Nicholson at amedd.army.mil (Nicholson James D)
Date: Thu, 15 Apr 1999 11:39:28 -0400
Subject: [Mailman-Users] Still need code info for privacy option
Message-ID: <BFDD20E1F489D21191C300104B99B7533DB6F9@dasmtaamp032.amedd.army.mil.92.131.in-addr.arpa>

To All:

I reported a problem previously that the privacy option to rewrite the mail
header to make it appear that it is coming from the list as opposed to an
individual user, is broken under IRIX 6.2 (or possibly just on my machine).
I REALLY need to take a look at the code responsible for this.  However, I
just don't know mailman.

Could someone please give me a pointer to the code responsible for the
rewrite as well as some way to check the settings to see if the web
interface to list administration is setting the switch correctly for this
feature?





From tgrace at tgrace.com  Thu Apr 15 19:06:46 1999
From: tgrace at tgrace.com (Terry Grace)
Date: Thu, 15 Apr 1999 13:06:46 -0400 (EDT)
Subject: [Mailman-Users] Possible bug in 1.0b11
Message-ID: <Pine.LNX.4.04.9904151302340.7678-100000@tweety.tgrace.com>

I think there is a bug in b11 when a user elects NOT to receive copies of
posts. See the traceback below for details:

The original message was received at Thu, 15 Apr 1999 12:27:07 -0400
from a.list.users.mail.server [111.222.333.444]

   ----- The following addresses had permanent fatal errors -----
"|/home/mailman/mail/wrapper post nortel-list"
    (expanded from: <list-name at tgrace.com>)

   ----- Transcript of session follows -----
Traceback (innermost last):
  File "/home/mailman/scripts/post", line 73, in ?
    current_list.Post(msg, approved=fromusenet)
  File "/home/mailman/Mailman/MailList.py", line 1236, in Post
    recipients.remove(self.GetUserSubscribedAddress(sender))
ValueError: list.remove(x): x not in list
554 "|/home/mailman/mail/wrapper post list-name"... unknown mailer error
1





From freya at rfa.org  Thu Apr 15 23:46:53 1999
From: freya at rfa.org (Adam)
Date: Thu, 15 Apr 1999 17:46:53 -0400
Subject: [Mailman-Users] errors...
Message-ID: <37165E4C.BD8CCD89@rfa.org>

I'm getting these errors in /var/log/cron from mailman. Can anyone tell
me what this is all about, and how to fix it? I know that the cron
daemon is being asked to run this via mailman, but is this just a
permissions issue, or possibly a bad install? I'll also attach an
emailed error that I used to get, but no longer get anymore for some
reason...


mailman (04/15-11:12:00-5473) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
mailman (04/15-11:42:00-5481) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
mailman (04/15-12:00:00-5485) CMD (/usr/bin/python
/home/mailman/cron/senddigests)
root (04/15-12:01:00-5487) CMD (run-parts /etc/cron.hourly)
mailman (04/15-12:12:00-5492) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
mailman (04/15-12:42:00-5498) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
root (04/15-13:01:00-5501) CMD (run-parts /etc/cron.hourly)
mailman (04/15-13:12:00-5506) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
mailman (04/15-13:42:00-5513) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
root (04/15-14:01:00-5515) CMD (run-parts /etc/cron.hourly)
mailman (04/15-14:12:00-5519) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
mailman (04/15-14:42:00-5529) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
root (04/15-15:01:00-5532) CMD (run-parts /etc/cron.hourly)
mailman (04/15-15:12:00-5538) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
mailman (04/15-15:42:00-5551) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
root (04/15-16:01:00-5556) CMD (run-parts /etc/cron.hourly)
mailman (04/15-16:12:00-5560) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
mailman (04/15-16:42:00-5570) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
mailman (04/15-17:00:00-5576) CMD (/usr/bin/python
/home/mailman/cron/checkdbs)
root (04/15-17:01:00-5578) CMD (run-parts /etc/cron.hourly)
mailman (04/15-17:12:00-5599) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
mailman (04/15-17:42:00-5606) CMD (/usr/bin/python
/home/mailman/cron/run_queue)


This is a copy of one of the emails I used to get:

Traceback (innermost last):
  File "/home/mailman/cron/run_queue", line 31, in ?
    OutgoingQueue.processQueue()
  File "/home/mailman/Mailman/OutgoingQueue.py", line 86, in
processQueue
    lock_file.lock()
  File "/home/mailman/Mailman/flock.py", line 119, in lock
    os.link(self.lockfile, self.tmpfname)
os.error: (13, 'Permission denied')



Thanx in advance,
Adam



From bwarsaw at cnri.reston.va.us  Fri Apr 16 04:50:31 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Thu, 15 Apr 1999 22:50:31 -0400 (EDT)
Subject: [Mailman-Users] Possible bug in 1.0b11
References: <Pine.LNX.4.04.9904151302340.7678-100000@tweety.tgrace.com>
Message-ID: <14102.42359.747808.566484@anthem.cnri.reston.va.us>

>>>>> "TG" == Terry Grace <tgrace at tgrace.com> writes:

    TG> I think there is a bug in b11 when a user elects NOT to
    TG> receive copies of posts.

...and delivery to the user is disabled (and the user is the sender of 
the message).  Here's the patch I'm going to check in.

-Barry

Index: MailList.py
===================================================================
RCS file: /projects/cvsroot/mailman/Mailman/MailList.py,v
retrieving revision 1.119
diff -c -r1.119 MailList.py
*** MailList.py	1999/04/16 02:31:22	1.119
--- MailList.py	1999/04/16 02:46:51
***************
*** 1232,1238 ****
              if not self.GetUserOption(m, mm_cfg.DisableDelivery):
                  recipients.append(m)
  	if dont_send_to_sender:
!             recipients.remove(self.GetUserSubscribedAddress(sender))
          self.LogMsg("post", "post to %s from %s size=%d",
                      self._internal_name, msg.GetSender(), len(msg.body))
  	self.DeliverToList(msg, recipients, 
--- 1232,1244 ----
              if not self.GetUserOption(m, mm_cfg.DisableDelivery):
                  recipients.append(m)
  	if dont_send_to_sender:
!             try:
!                 recipients.remove(self.GetUserSubscribedAddress(sender))
!             except ValueError:
!                 # sender does not want to get copies of their own messages
!                 # (not metoo), but delivery to their address is disabled
!                 # (nomail)
!                 pass
          self.LogMsg("post", "post to %s from %s size=%d",
                      self._internal_name, msg.GetSender(), len(msg.body))
  	self.DeliverToList(msg, recipients, 



From harri.nyman at sonera.fi  Fri Apr 16 07:52:19 1999
From: harri.nyman at sonera.fi (Harri Nyman)
Date: Fri, 16 Apr 1999 08:52:19 +0300
Subject: [Mailman-Users] Possible bug in 1.0b11
Message-ID: <002401be87cd$49f63430$29fcfbc2@tmt.tele.fi>

I'm experiencing same bug, but it manifests it when I forward from
outlook to one of the lists.

Harri

----- Original Message -----
From: <tgrace at tgrace.com>
To: <mailman-users at python.org>
Sent: Thursday, April 15, 1999 8:06 PM
Subject: [Mailman-Users] Possible bug in 1.0b11


>I think there is a bug in b11 when a user elects NOT to receive copies
of
>posts. See the traceback below for details:
>
>The original message was received at Thu, 15 Apr 1999 12:27:07 -0400
>from a.list.users.mail.server [111.222.333.444]
>
>   ----- The following addresses had permanent fatal errors -----
>"|/home/mailman/mail/wrapper post nortel-list"
>    (expanded from: <list-name at tgrace.com>)
>
>   ----- Transcript of session follows -----
>Traceback (innermost last):
>  File "/home/mailman/scripts/post", line 73, in ?
>    current_list.Post(msg, approved=fromusenet)
>  File "/home/mailman/Mailman/MailList.py", line 1236, in Post
>    recipients.remove(self.GetUserSubscribedAddress(sender))
>ValueError: list.remove(x): x not in list
>554 "|/home/mailman/mail/wrapper post list-name"... unknown mailer
error
>1
>
>
>
>------------------------------------------------------
>Mailman-Users maillist  -  Mailman-Users at python.org
>http://www.python.org/mailman/listinfo/mailman-users
>




From sucher at ust.hk  Fri Apr 16 08:19:20 1999
From: sucher at ust.hk (Nikolaus J. Sucher)
Date: Fri, 16 Apr 1999 14:19:20 +0800
Subject: [Mailman-Users] Python 1.5.2
Message-ID: <3716D668.2172D8E4@ust.hk>

Hi there,

I upgraded to Python 1.5.2 and now my webbrowser only returns :"the
requested URL /mailman/admin/xxx was not found on this server"

Did I make a mistake with the upgrade or is this a problem with
mailman??

Your help is greatly appreciated!

Nikolaus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sucher.vcf
Type: text/x-vcard
Size: 427 bytes
Desc: Card for Nikolaus J. Sucher
Url : http://mail.python.org/pipermail/mailman-users/attachments/19990416/6424ff2d/attachment.vcf 

From nbecker at fred.net  Fri Apr 16 14:11:18 1999
From: nbecker at fred.net (nbecker at fred.net)
Date: 16 Apr 1999 08:11:18 -0400
Subject: [Mailman-Users] Python 1.5.2
In-Reply-To: "Nikolaus J. Sucher"'s message of "Fri, 16 Apr 1999 14:19:20 +0800"
References: <3716D668.2172D8E4@ust.hk>
Message-ID: <x88n20869zt.fsf@nbeckerpc.hns.com>

Works for me.



From gonter at maestria.wu-wien.ac.at  Fri Apr 16 16:58:09 1999
From: gonter at maestria.wu-wien.ac.at (Gerhard Gonter)
Date: Fri, 16 Apr 1999 16:58:09 +0200 (MES)
Subject: [Mailman-Users] Moving Listproc lists
Message-ID: <199904161458.QAA05214@maestria.wu-wien.ac.at>

Does anybody have a nice little tool to transfer a listproc based
mailing list to mailman?

If not, I'll start with a program to transfer the user list or
check, if add_members could be hacked to do that ;)

+gg
 
--
Gerhard.Gonter at wu-wien.ac.at  Fax: +43/1/31336/702  g.gonter at ieee.org
Zentrum fuer Informatikdienste, Wirtschaftsuniversitaet Wien, Austria



From pehr at eink.com  Fri Apr 16 18:24:02 1999
From: pehr at eink.com (pehr anderson)
Date: Fri, 16 Apr 1999 16:24:02 +0000
Subject: [Mailman-Users] how to install
Message-ID: <37176421.F9942D8A@eink.com>

I wrote the following installation script trying to follow all the docs.

Please tell me what I'm doing wrong. It seems like I'm missing
something pretty fundamental.

    -pehr

#!/bin/sh
# Script to install mailman on a clean box with RedHat Linux 5.2
# by pehr at eink.com
# This doesn't work yet, please tell me what's wrong!
# Send me mail and I'll fix it.
# CAUTION THIS WILL MOST LIKELY NUKE AN EXISTING MAILMAN INSTALLATION
# DO NOT USE THIS SCRIPT TO UPGRADE

EMAIL=pehr at eink.com
PASSWD=foo
#some unused user/group id
ID=127

userdel  mailman
groupdel mailman
groupadd -g $ID mailman
useradd  -u $ID -g mailman mailman
cd /home/mailman
tar xzf ~pehr/gz/mailman.tar.gz
chgrp mailman   /home/mailman
chmod a+rx,g+ws /home/mailman

# configure and install mailman
cd mailman*
make clean
./configure --with-mail-gid=mail --with-cgi-gid=nobody
#make
make install
crontab -u mailman /home/mailman/cron/crontab.in

# configure apache and restart
if grep mailman /etc/httpd/conf/httpd.conf
then
echo ScriptAlias /mailman/ /home/mailman/cgi-bin/ >>
/etc/httpd/conf/httpd.conf
echo Alias /pipermail/ /home/mailman/archives/public >>
/etc/httpd/conf/httpd.conf
fi
/etc/rc.d/init.d/httpd restart

#configure sendmail
if grep mailman /etc/aliases
then
echo mailman: $EMAIL
echo mailman-owner: mailman
fi
/etc/rc.d/init.d/sendmail restart

# configure site password
/home/mailman/bin/mmsitepass $PASSWD

echo "Hope it worked!"
echo "Now browse to "
echo "http://localhost/pipermail/"
echo "   -pehr"
lynx http://localhost/pipermail





From kevin at vulcanind.com  Fri Apr 16 21:11:20 1999
From: kevin at vulcanind.com (Kevin Lee)
Date: Fri, 16 Apr 1999 14:11:20 -0500
Subject: [Mailman-Users] TrySMTPDelivery: prohibited by administrator (dequeued)
Message-ID: <3.0.2.32.19990416141120.00b74698@iris.vulcanind.com>

I have been receiving the following messages in my
/var/lib/mailman/logs/smtp-failures.  I am using Debian GNU/Linux 2.1 and
mailman 1.0b8-3 from the Debian distribution site.  Please be easy on me
I'm a Linux newbie.

May 04 11:14:27 1999 TrySMTPDelivery: To ['kevin at vulcanind.com']:
May 04 11:14:27 1999 TrySMTPDelivery:
Mailman.pythonlib.smtplib.SMTPRecipientsRefused / kevin at vulcanind.com:
relaying to <kevin at vulcanind.com> prohibited by administrator (dequeued)

TIA,


Kevin Lee
Vulcan Industries
(205) 640-2433

mailto:kevin at vulcanind.com

http://www.vulcanind.com







From che at debian.org  Fri Apr 16 21:57:49 1999
From: che at debian.org (Ben Gertzfield)
Date: 16 Apr 1999 12:57:49 -0700
Subject: [Mailman-Users] TrySMTPDelivery: prohibited by administrator (dequeued)
In-Reply-To: kevin@vulcanind.com's message of "Fri, 16 Apr 1999 14:11:20 -0500"
References: <3.0.2.32.19990416141120.00b74698@iris.vulcanind.com>
Message-ID: <yttemlkqqwy.fsf@gilgamesh.cse.ucsc.edu>

>>>>> "Kevin" == Kevin Lee <kevin at vulcanind.com> writes:

    Kevin> I have been receiving the following messages in my
    Kevin> /var/lib/mailman/logs/smtp-failures.  I am using Debian
    Kevin> GNU/Linux 2.1 and mailman 1.0b8-3 from the Debian
    Kevin> distribution site.  Please be easy on me I'm a Linux
    Kevin> newbie.

    Kevin> May 04 11:14:27 1999 TrySMTPDelivery: To
    Kevin> ['kevin at vulcanind.com']: May 04 11:14:27 1999
    Kevin> TrySMTPDelivery:
    Kevin> Mailman.pythonlib.smtplib.SMTPRecipientsRefused /
    Kevin> kevin at vulcanind.com: relaying to <kevin at vulcanind.com>
    Kevin> prohibited by administrator (dequeued)

If your machine is vulcanind.com, you may wish to run
/usr/sbin/sendmailconfig and make sure that Debian knows that
vulcanind.com is allowed to relay mail to anywhere.

Ben

-- 
Brought to you by the letters H and J and the number 6.
"Yasashisani tsutsumaretanara, kitto.. meni utsuru.."
Debian GNU/Linux maintainer of Gimp and GTK+ -- http://www.debian.org/
I'm on FurryMUCK as Che, and EFNet/Open Projects IRC as Che_Fox.



From kevin at vulcanind.com  Fri Apr 16 23:31:46 1999
From: kevin at vulcanind.com (Kevin Lee)
Date: Fri, 16 Apr 1999 16:31:46 -0500
Subject: [Mailman-Users] system_aliases director
Message-ID: <3.0.2.32.19990416163146.00b20c58@iris.vulcanind.com>

I have the Mailman web administration and user adminstration functions
working now.  This seems like a huge improvement over Majordomo/MajorCool.
I am getting the following error:

Neither the system_aliases director nor the address_pipe transport set a
uid for local delivery of |var/lib/mailman/mail/wrapper post sales

I am running Debian GNU/Linux 2.1.

TIA


Kevin Lee
Vulcan Industries
(205) 640-2433

mailto:kevin at vulcanind.com

http://www.vulcanind.com







From klm at digicool.com  Sat Apr 17 01:39:12 1999
From: klm at digicool.com (Ken Manheimer)
Date: Fri, 16 Apr 1999 19:39:12 -0400
Subject: [Mailman-Users] Still need code info for privacy option
Message-ID: <613145F79272D211914B0020AFF640190BEE68@gandalf.digicool.com>

On thursda, Nicholson James D wrote:

> I reported a problem previously that the privacy option to rewrite the
mail
> header to make it appear that it is coming from the list as opposed to
an
> individual user, is broken under IRIX 6.2 (or possibly just on my
machine).
> I REALLY need to take a look at the code responsible for this.
However, I
> just don't know mailman.
> 
> Could someone please give me a pointer to the code responsible for the
> rewrite as well as some way to check the settings to see if the web
> interface to list administration is setting the switch correctly for
this
> feature?

The variable name in the code is 'anonymous_list', and the relevant
focus is in Mailman/MailList.py .  There's a section where the setting
is defined, and another setting in the Post() method where it is used.
A common simple trick for investigating the setting would be to make
calls to self.LogMsg(), e.g. self.LogMsg("debug", "anonymous_list: %s",
anon



From klm at digicool.com  Sat Apr 17 01:48:05 1999
From: klm at digicool.com (Ken Manheimer)
Date: Fri, 16 Apr 1999 19:48:05 -0400
Subject: [Mailman-Users] Still need code info for privacy option
Message-ID: <613145F79272D211914B0020AFF640190BEE69@gandalf.digicool.com>

Damn, i hit the wrong key.  That's what i get (sorry you all do to) for
trying to rush to get this out late on friday eve.  I was saying:

On thursday, Nicholson James D wrote:

> I reported a problem previously that the privacy option to rewrite the
mail
> header to make it appear that it is coming from the list as opposed to
an
> individual user, is broken under IRIX 6.2 (or possibly just on my
machine).
> I REALLY need to take a look at the code responsible for this.
However, I
> just don't know mailman.
> 
> Could someone please give me a pointer to the code responsible for the
> rewrite as well as some way to check the settings to see if the web
> interface to list administration is setting the switch correctly for
this
> feature?

The variable name in the code is 'anonymous_list', and the relevant
focus is in Mailman/MailList.py .  There's a section where the setting
is defined, and another setting in the Post() method where it is used.
A common simple trick for investigating the setting would be to make
calls to self.LogMsg(), e.g. 

   self.LogMsg("debug", "anonymous_list: %s", self.anonymous_list)
# DEBUG

just before the conditional in Post() that uses it, and then you should
see an entry in the logs/debug file with the message, each time your
line is executed.

If it is set but the lines within the conditional aren't doing their
job, to ascertain exactly what's going on you'll have to get acquainted
with the Mailman.Message.IncomingMessage class, at least enough to poke
around one.

Oh yeah, if you really want to have fun, and are comfortable with
python, the README file describes interacting with a maillist from the
python command prompt.  You can also interact with message objects, etc.
But it's not for the faint of heart.

I hope this helps - sorry i don't have the time to help more with your
investigation, let us know what you determine!

Ken
klm at digicool.com



From joev at freddyfrog.com  Sun Apr 18 02:24:28 1999
From: joev at freddyfrog.com (joe vaughan)
Date: Sun, 18 Apr 1999 01:24:28 +0100 (GMT Daylight Time)
Subject: [Mailman-Users] Filtering out mail headers
Message-ID: <14105.9788.520000.754072@londo.freddyfrog.com>

Hi there,

If this question is answered anywhere, I haven't been able to find 
it. :)

I have a few mailman lists, with several subscribers that have
Delivery reciepts request turned on.

I'd like to have mailman automatically strip out the relevant headers
if possible.

Q1. Is this possible. I'm running exim, and could impose a system
filter to trap them, but that means either stripping them from all
mail messages to my domain or checking explicitly for the list
addresses and then stripping them, which in turn means adding each new
list created into the exim filter. I'd like, if possible to do it in
mailman.

Q2. If it is possible, would anyone be able to point me in the right
direction to start? I'm a complete python newbie and reading the
mailman source helps a little, but doesn't really teach me enough
python to implement such a filter from scratch :)

Any help would be appreciated.

regards

joev
-- 
joe vaughan         project coordinator   Project Mnemonic
joev at mnemonic.org		          http://www.mnemonic.org/





From gconnor at nekodojo.org  Sat Apr 17 18:55:40 1999
From: gconnor at nekodojo.org (Greg Connor)
Date: Sat, 17 Apr 1999 09:55:40 -0700
Subject: [Mailman-Users] Moving Listproc lists
In-Reply-To: <199904161458.QAA05214@maestria.wu-wien.ac.at>
Message-ID: <4.1.19990417094443.00b43370@pop.nekodojo.org>

At 04:58 PM 4/16/99 +0200, Gerhard Gonter wrote:
>Does anybody have a nice little tool to transfer a listproc based
>mailing list to mailman?
>
>If not, I'll start with a program to transfer the user list or
>check, if add_members could be hacked to do that ;)


I did it all by hand on my system... here are the commands I used to
transfer users, as closely as I can remember...

su
su -l server
cat lists/LIST1/.subscribers | grep "ACK" | cut -f1 -d" " | tr "[A-Z]"
"[a-z]" > /tmp/list1.regular
cat lists/LIST1/.subscribers | grep "DIGEST" | cut -f1 -d" " | tr "[A-Z]"
"[a-z]" > /tmp/list1.digest
exit
su -l mailman
add_members -n /tmp/list1.regular list1
add_members -d /tmp/list1.digest list1

Also, I had problems subbing more than 20 people at a time; all would get
subbed, but only 20 or so would get welcome messages (containing their new
random password).  If you think you might have this problem too, use
something like this instead..

su -l mailman
split -15 /tmp/list1.regular /tmp/list1.regular.x
split -15 /tmp/list1.digest /tmp/list1.digest.x
foreach j (/tmp/list1.regular.x*)
add_members -n $j
sleep 40
end
foreach j (/tmp/list1.digest.x*)
add_members -d $j
sleep 40
end




From Chris at ent.health.ufl.edu  Sat Apr 17 19:17:53 1999
From: Chris at ent.health.ufl.edu (Chris Barnett)
Date: Sat, 17 Apr 1999 13:17:53 -0400
Subject: [Mailman-Users] mailman & sendmail 8.9.3 problem
Message-ID: <A3D768A1B39AD111B04C00A0C981CE112EC845@mail.surgery.ufl.edu>

Hi, I've been using mailman 1.0b9 problem free for a good bit now without
problem on a Redhat 5.2 system.

Of course, last night I decided to get adventurous and I upgraded my box to
the Redhat 5.9 Starbuck prerelease (or whatever it's called this week).
Everything went fine, including the upgrade to Sendmail 8.9.3 or so I
thought.

now whenever I try to send mail to any of my lists I get the following back
from the Mail Delivery Subsytem:
-------------------------------------------------------------------------
The original message was received at Sat, 17 Apr 1999 12:44:05 -0400
from UFF-COM.UFF.UFL.EDU [128.227.33.150] (may be forged)

   ----- The following addresses had permanent fatal errors -----
"|/home/mailman/mail/wrapper mailowner test02"
    (expanded from: <test02-admin at uff-com.uff.ufl.edu>)

   ----- Transcript of session follows -----
sh: wrapper not available for sendmail programs
554 "|/home/mailman/mail/wrapper mailowner test02"... Service unavailable
-------------------------------------------------------------------------

I've tried 3 different lists and I get the same sort of thing.  So it looks
like it's reading the /etc/aliases file properly, but somehow my rights got
set incorrectly and sendmail can't access the wrapper.

So instead of being a good sysadmin and actually checking to see what the
problem was, I decided "Ah, upgrading to mailman 1.0b11 will fix it".  So I
upgraded and that went fine...but the error is still there.

Anyone have any suggestions?

Thanks.

Chris Barnett
Web Desinger & Programmer
University of Florida Foundation, Inc.



From gonter at maestria.wu-wien.ac.at  Sat Apr 17 19:59:18 1999
From: gonter at maestria.wu-wien.ac.at (Gerhard Gonter)
Date: Sat, 17 Apr 1999 19:59:18 +0200 (MES)
Subject: [Mailman-Users] Moving Listproc lists
In-Reply-To: <4.1.19990417094443.00b43370@pop.nekodojo.org> from Greg Connor at "Apr 17, 99 09:55:40 am"
Message-ID: <199904171759.TAA24566@maestria.wu-wien.ac.at>

According to Greg Connor:
> I did it all by hand on my system... here are the commands I used to
> transfer users, as closely as I can remember...

Thanks a lot, in the meantime I moved the subscribers of the first few
lists (100 more to go :) using a modified add_members:

  ./add_members --lp6 lists/LIST1/.subscribers list1

Only one file, add_members, had to be modified.  This maps

  ACK, NOACK  -> normal subscriptions
  DIGEST      -> digest subscriptions

and keeps the original password.  Addresses are converted to lower
case.

I will offer this version to the developers, maybe it will show up
in the next version.

Right now, POSTPONE'd entries are dropped and the CONCEAL flag is
ignored, keeping this information requires modifications in other parts
of Mailman.  I'm not sure if I'll try that, maybe not...

> Also, I had problems subbing more than 20 people at a time; all would get
> subbed, but only 20 or so would get welcome messages (containing their new
> random password).  If you think you might have this problem too, use
> something like this instead..

Hmm...  Thanks for the hint.  The sendmail logs tell me that everyone
in a list with 167 members should have received their welcome messages
by now, so this might be a bug in other versions.  The bug archive
didn't mention anything about that.  (I'm using 1.0b8, the original
add_members was pulled out of CVS yesterday.)

+gg
 
--
Gerhard.Gonter at wu-wien.ac.at  Fax: +43/1/31336/702  g.gonter at ieee.org
Zentrum fuer Informatikdienste, Wirtschaftsuniversitaet Wien, Austria



From lindsey at ncsa.uiuc.edu  Sat Apr 17 20:00:48 1999
From: lindsey at ncsa.uiuc.edu (Christopher Lindsey)
Date: Sat, 17 Apr 1999 13:00:48 -0500 (CDT)
Subject: [Mailman-Users] mailman & sendmail 8.9.3 problem
In-Reply-To: <A3D768A1B39AD111B04C00A0C981CE112EC845@mail.surgery.ufl.edu> from "Chris Barnett" at Apr 17, 99 01:17:53 pm
Message-ID: <199904171800.NAA31148@ferret.ncsa.uiuc.edu>

A non-text attachment was scrubbed...
Name: not available
Type: text
Size: 1033 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-users/attachments/19990417/02b81fb1/attachment.asc 

From Chris at ent.health.ufl.edu  Sat Apr 17 20:10:44 1999
From: Chris at ent.health.ufl.edu (Chris Barnett)
Date: Sat, 17 Apr 1999 14:10:44 -0400
Subject: [Mailman-Users] mailman & sendmail 8.9.3 problem
Message-ID: <A3D768A1B39AD111B04C00A0C981CE112EC846@mail.surgery.ufl.edu>

Thanks!!

That corrected the problem.

Chris B.

-----Original Message-----
From: Christopher Lindsey
To: Chris at ent.health.ufl.edu
Cc: mailman-users at python.org
Sent: 4/17/99 2:00 PM
Subject: Re: [Mailman-Users] mailman & sendmail 8.9.3 problem

> "|/home/mailman/mail/wrapper mailowner test02"
>     (expanded from: <test02-admin at uff-com.uff.ufl.edu>)
> 
>    ----- Transcript of session follows -----
> sh: wrapper not available for sendmail programs
> 554 "|/home/mailman/mail/wrapper mailowner test02"... Service
unavailable
>
------------------------------------------------------------------------
-
> 
> So instead of being a good sysadmin and actually checking to see what
the
> problem was, I decided "Ah, upgrading to mailman 1.0b11 will fix it".
So I
> upgraded and that went fine...but the error is still there.

I don't know much about the new RedHat distribution, but it sounds as if
it
may be running smrsh -- sendmail restricted shell.  smrsh limits what
programs
sendmail will run to a list of files within a certain directory, usually

/var/adm/sm.bin.  I'd do a 'man smrsh' and see what directory it uses 
(assuming that this is the problem), then go into that directory and do

   ln -s /home/mailman/mail/wrapper 

as root.

Chris



From cklempay at chimera.acm.jhu.edu  Mon Apr 19 02:22:21 1999
From: cklempay at chimera.acm.jhu.edu (Corbett J. Klempay)
Date: Sun, 18 Apr 1999 20:22:21 -0400 (EDT)
Subject: [Mailman-Users] CRAP
Message-ID: <Pine.LNX.4.10.9904182019340.12943-100000@chimera.acm.jhu.edu>

Hey all...I have no idea why (I have emails out to see if any of the other
admins were playing around), but my Mailman installation just pretty much
choked.  I got a mention of a post requiring approval, and I went to the
page to approve/deny...and instead of the page, I got an Internal Server
Error.  I started investigating further, and any kind of Mailman-generated
page (admin, listinfo pages) gives an Internal Server Error.  I tried
sending a message to one of the lists as a test; it never made it out (so
I'm assuming all of the lists are down)...and I've also started getting
the below message.....anyone know what's up?  (Note: this is 1.0b6...yeah,
I need to upgrade it, but it was working fine, so I'm wondering what's up)

--
Subject: Cron <mailman at chimera> /usr/bin/python /home/mailman/cron/run_queue

Traceback (innermost last):
  File "/home/mailman/cron/run_queue", line 25, in ?
    from Mailman import OutgoingQueue
  File "/home/mailman/Mailman/OutgoingQueue.py", line 39, in ?
    import os, stat, tempfile, marshal, errno, mm_cfg
  File "/home/mailman/Mailman/mm_cfg.py", line 44, in ?
    from Defaults import *
  File "/home/mailman/Mailman/Defaults.py", line 265, in ?
    PUBLIC_ARCHIVE_FILE_DIR 	= os.path.join(PREFIX, 'archives/public')
AttributeError: USE_CRYPT




From cklempay at chimera.acm.jhu.edu  Mon Apr 19 06:05:49 1999
From: cklempay at chimera.acm.jhu.edu (Corbett J. Klempay)
Date: Mon, 19 Apr 1999 00:05:49 -0400 (EDT)
Subject: [Mailman-Users] bizzarre; disregard previous
Message-ID: <Pine.LNX.4.10.9904190003430.16313-100000@chimera.acm.jhu.edu>

Ok, disregard that last message...I just upped to b11, and everything is
kosher now (I had to fix some permissions that were apparently wrong in
the archives to get the install to go totally cleanly...but they have
apparently been that way the whole time it has been working to
date)...weird.  Anyway, it's working now :)

One question: in the 'make update', is there a reason why it asks you to
manually copy the new options.html file for each list (or should this be
done as part of make update)?

------------------------------------------------------------------------------
Corbett J. Klempay			         Quote of the Week:
http://www.acm.jhu.edu/~cklempay       "A commune is where people join 
					together to share their lack of 
					wealth."
------------------------------------------------------------------------------




From RichardE at eskom.co.za  Mon Apr 19 13:48:07 1999
From: RichardE at eskom.co.za (Richard Ellerbrock)
Date: Mon, 19 Apr 1999 13:48:07 +0200
Subject: [Mailman-Users] Bouncing on Mailman
Message-ID: <s71b3414.002@eskom.co.za>

Here is a copy of my modified Bouncer.py python script that I use with mailman 1b11. I have modified it to catch a couple more bounces, including your instance #1 on jitterbug report #34. Try it if you wish. Addresses failing from you instance #1 will be removed. No 2 I cannot help you with. Sorry.

The file must go in ~mailman/Mailman. Make a copy of the old one first in case it does not work for you!

Richard Ellerbrock
richarde at eskom.co.za


-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Bouncer.py
Url: http://mail.python.org/pipermail/mailman-users/attachments/19990419/32035ace/attachment.pot 

From freya at rfa.org  Mon Apr 19 16:38:04 1999
From: freya at rfa.org (Adam)
Date: Mon, 19 Apr 1999 10:38:04 -0400
Subject: [Mailman-Users] Not to bug everyone, but...
Message-ID: <371B3FCC.568E230C@rfa.org>

I tried posting last week, but never got a reply. Can someone point out
to me why i'm getting these errors on a RedHat linux box (v5.1)?

I'm getting these errors in /var/log/cron from mailman. Can anyone tell
me what this is all about, and how to fix it? I know that the cron
daemon is being asked to run this via mailman, but is this just a
permissions issue, or possibly a bad install? I'll also attach an
emailed error that I used to get, but no longer get anymore for some
reason...


mailman (04/15-11:12:00-5473) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
mailman (04/15-11:42:00-5481) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
mailman (04/15-12:00:00-5485) CMD (/usr/bin/python
/home/mailman/cron/senddigests)
root (04/15-12:01:00-5487) CMD (run-parts /etc/cron.hourly)
mailman (04/15-12:12:00-5492) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
mailman (04/15-12:42:00-5498) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
root (04/15-13:01:00-5501) CMD (run-parts /etc/cron.hourly)
mailman (04/15-13:12:00-5506) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
mailman (04/15-13:42:00-5513) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
root (04/15-14:01:00-5515) CMD (run-parts /etc/cron.hourly)
mailman (04/15-14:12:00-5519) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
mailman (04/15-14:42:00-5529) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
root (04/15-15:01:00-5532) CMD (run-parts /etc/cron.hourly)
mailman (04/15-15:12:00-5538) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
mailman (04/15-15:42:00-5551) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
root (04/15-16:01:00-5556) CMD (run-parts /etc/cron.hourly)
mailman (04/15-16:12:00-5560) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
mailman (04/15-16:42:00-5570) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
mailman (04/15-17:00:00-5576) CMD (/usr/bin/python
/home/mailman/cron/checkdbs)
root (04/15-17:01:00-5578) CMD (run-parts /etc/cron.hourly)
mailman (04/15-17:12:00-5599) CMD (/usr/bin/python
/home/mailman/cron/run_queue)
mailman (04/15-17:42:00-5606) CMD (/usr/bin/python
/home/mailman/cron/run_queue)


This is a copy of one of the emails I used to get:

Traceback (innermost last):
  File "/home/mailman/cron/run_queue", line 31, in ?
    OutgoingQueue.processQueue()
  File "/home/mailman/Mailman/OutgoingQueue.py", line 86, in
processQueue
    lock_file.lock()
  File "/home/mailman/Mailman/flock.py", line 119, in lock
    os.link(self.lockfile, self.tmpfname)
os.error: (13, 'Permission denied')



Thanx in advance,
Adam



From tgrace at thestar.ca  Mon Apr 19 19:59:24 1999
From: tgrace at thestar.ca (Grace, Terry)
Date: Mon, 19 Apr 1999 13:59:24 -0400
Subject: [Mailman-Users] 1.0b11 bug with underscores in member name?
Message-ID: <B582FE6508F7D111B75D00A0C9B3F84DB04C9B@MAIL1>

I have a list member with underscores in the username (eg
username_at_hostname at domain.com). When a message goes out to the list the
following is returned to the list admin and the message is never delivered
to the user:

ontent-type: text/plain; charset=us-ascii

This is a Mailman mailing list bounce action notice:

    List:       Nortel-list
    Member:     not at domain.com
    Action:     Subscription not disabled.
    Reason:     Excessive or fatal bounces.
    BUT:        User not found.


The triggering bounce notice is attached below.

Questions?  Contact the Mailman site administrator at
mailman-owner at tgrace.com.

Here's the bounced message:

------- Failure Reasons  --------

User  not listed in public Name & Address Book
username_at_hostname at domain.com


------- Returned Message --------
Received: from tweety.tgrace.com ([192.206.151.132]) by vfc.com (Lotus SMTP
MTA v4.6.3 (778.2 1-4-1999)) with SMTP id 85256758.005BAF33; Mon, 19 Apr
1999 12:41:26 -0400
Received: from internal mail server
	by tweety.tgrace.com  with ESMTP id MAA06051
Received: from internal mail server
	by tweety.tgrace.com  with SMTP id MAA06033
	for <nortel-list at tgrace.com>;
From: SPence6963 at aol.com
Received: from SPence6963 at aol.com
	by imo21.mx.aol.com (IMOv20.11) id oQMZa21000
	 for <nortel-list at tgrace.com>; Mon, 19 Apr 1999 12:39:19 -0400 (EDT)
Message-ID: <48241f08.244cb630 at aol.com>
Date: Mon, 19 Apr 1999 12:39:12 EDT
Subject: [Nortel-list] Definity woes
To: nortel-list at tgrace.com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 4.0 for Windows 95 sub 13
Reply-To: nortel-list at tgrace.com
Sender: nortel-list-admin at tgrace.com
Errors-To: nortel-list-admin at tgrace.com
X-Mailman-Version: 1.0b11
Precedence: bulk
List-Id: Mailing list for Northern Telecom related issues
<nortel-list.tgrace.com>
X-BeenThere: nortel-list at tgrace.com

<message text>
_______________________________________________
Nortel-list maillist  -  Nortel-list at tgrace.com
http://www.tgrace.com/mailman/listinfo/nortel-list




From omar at dit.upm.es  Mon Apr 19 19:36:37 1999
From: omar at dit.upm.es (Omar Walid Llorente)
Date: Mon, 19 Apr 1999 19:36:37 +0200 (MET DST)
Subject: [Mailman-Users] Re: Not to bug everyone, but... (A pair of tricks)
Message-ID: <Pine.LNX.3.95.990419193129.14900N-100000@oasis.dit.upm.es>

freya at rfa.org wrote:
>I tried posting last week, but never got a reply. Can someone point out
>to me why i'm getting these errors on a RedHat linux box (v5.1)?
>
>I'm getting these errors in /var/log/cron from mailman. Can anyone tell
>me what this is all about, and how to fix it? I know that the cron
>daemon is being asked to run this via mailman, but is this just a
>permissions issue, or possibly a bad install? I'll also attach an
>emailed error that I used to get, but no longer get anymore for some
>reason...
>
>
>mailman (04/15-11:12:00-5473) CMD (/usr/bin/python
>/home/mailman/cron/run_queue)
>mailman (04/15-11:42:00-5481) CMD (/usr/bin/python
>/home/mailman/cron/run_queue)

[...]

	Hello Adam, i have a trick for solving this. It's a permission problem 
in some mailman's subdirectories. These are the steps:

	(as root)
	1- cd ~mailman
	2- chown -R mailman.root lists locks logs
	3- chmod g+s lists locks logs

	This must solve your problem (i think :-)

NOTE: For "untruster" admins: mailman needs you to enable the cookies to 
	change the configuration of any list.

	Thanks to all for such a good pieze of software.

	Omar.

--------------------------------------------------------------------------------
    Centro de Calculo
    Departamento Ingenieria Telematica (ETSIT)      e-mail: omar at dit.upm.es
    Universidad Politecnica de Madrid               Tel:(+34) 913367366-Ext.328
    Ciudad Universitaria, s/n 28040 Madrid (Spain)  Fax:(+34) 913367333
--------------------------------------------------------------------------------




From dmacdoug at hsc.usc.edu  Tue Apr 20 03:58:39 1999
From: dmacdoug at hsc.usc.edu (dmacdoug at hsc.usc.edu)
Date: Mon, 19 Apr 1999 18:58:39 -0700 (PDT)
Subject: [Mailman-Users] Cron <list@petunia> /usr/bin/python /usr/lib/mailman/cron/run_queue
 
Message-ID: <E10ZPo7-0001NK-00@petunia.hsc.usc.edu>

Can anyone tell me why I get the following error message every time
cron runs the queue?  This is Mailman 1.0b11.  I've looked at flock.py
but Python is still a foreign language to me.  I can't figure out what
file it isn't able to open or if that is even the problem.

Don MacDougall
dmacdoug at hsc.usc.edu

------ Forwarded message ------
    From: root at petunia.hsc.usc.edu (Cron Daemon)
 Subject: Cron <list at petunia> /usr/bin/python /usr/lib/mailman/cron/run_queue
    Date: Mon, 19 Apr 1999 18:12:01 -0700
      To: list at petunia.hsc.usc.edu

Traceback (innermost last):
  File "/usr/lib/mailman/cron/run_queue", line 31, in ?
    OutgoingQueue.processQueue()
  File "/usr/lib/mailman/Mailman/OutgoingQueue.py", line 88, in processQueue
    lock_file.lock()
  File "/usr/lib/mailman/Mailman/flock.py", line 119, in lock
    os.link(self.lockfile, self.tmpfname)
os.error: (2, 'No such file or directory')





From dmacdoug at hsc.usc.edu  Tue Apr 20 07:41:45 1999
From: dmacdoug at hsc.usc.edu (dmacdoug at hsc.usc.edu)
Date: Mon, 19 Apr 1999 22:41:45 -0700 (PDT)
Subject: [Mailman-Users] Cron <list@petunia> /usr/bin/python /usr/lib/ma
 ilman/cron/run_queue
In-Reply-To: <199904200426.GAA24358@maestria.wu-wien.ac.at>
Message-ID: <E10ZTI1-0001UU-00@petunia.hsc.usc.edu>

Update on cron run_queue problem:

Thanks to Christopher Lindsey and Gerhard Gonter for their help. I found
that for some reason there was no file in the lock directory called
mmqueue_run.lock.  So I ran cron/run_queue by hand and it was created. 
But now the error message said "Permission denied" instead of "File not
found" so I figured I was on the right track.  It was created with
ownership of root.  Thinking this should, perhaps be mailman, I changed
it, but "permission denied" persists.  It's permissions are -rw-rw-r--. 
The lock directory is permission drwxrwxr-x also owned by mailman.

The file system isn't full as I am just setting it up new and there's
nothing on it yet.  I suppose I've probably done something wrong in the
setup.  I compiled it as user mailman.  I set up a test list according
to the instructions but it isn't accepting mail.  I had supposed that
this was a separate issue and was perhaps a matter of how things were
set up in my MTA which is Exim, but maybe I've just botched up the
installation of Mailman.

Don MacDougall
dmacdoug at hsc.usc.edu

On 20 Apr, Gerhard Gonter wrote:
> According to dmacdoug at hsc.usc.edu:
>> Can anyone tell me why I get the following error message every time
>> cron runs the queue?  This is Mailman 1.0b11.  I've looked at flock.py
>> but Python is still a foreign language to me.  I can't figure out what
>> file it isn't able to open or if that is even the problem.
> 
> To find out what the file is, just add a print statement before the
> line 119 and run the cron job once by hand:
> 
>   +117   while 1:
>   +118      # create the hard link and test for exactly 2 links to the file
>   +119      print "lockfile=%s tmpfname=%s" % (self.lockfile, self.tmpfname)
>   +120      os.link(self.lockfile, self.tmpfname)
>   +121      if os.stat(self.tmpfname)[ST_NLINK] == 2:
> 
> mailman> /usr/local/bin/python /home/mailman/cron/run_queue
>   lockfile=/home/mailman/locks/mmqueue_run.lock
>   tmpfname=/home/mailman/locks/mmqueue_run.lock.augenblix.82222
> 
> Mailman has a problem when it's file system is full, this may
> be the case actually.
> 
> Don't forget to comment or remove the print statement when the
> problem is fixed.
> 
> +gg
>  
> --
> Gerhard.Gonter at wu-wien.ac.at  Fax: +43/1/31336/702  g.gonter at ieee.org
> Zentrum fuer Informatikdienste, Wirtschaftsuniversitaet Wien, Austria





From dmacdoug at hsc.usc.edu  Tue Apr 20 09:35:45 1999
From: dmacdoug at hsc.usc.edu (dmacdoug at hsc.usc.edu)
Date: Tue, 20 Apr 1999 00:35:45 -0700 (PDT)
Subject: [Mailman-Users] Cron <list@petunia> /usr/bin/python /usr/lib/ma
 
In-Reply-To: <199904200729.CAA16206@ferret.ncsa.uiuc.edu>
Message-ID: <E10ZV4L-0001Xm-00@petunia.hsc.usc.edu>

On 20 Apr, Christopher Lindsey wrote:
>> found" so I figured I was on the right track.  It was created with
>> ownership of root.  Thinking this should, perhaps be mailman, I changed
>> it, but "permission denied" persists.  It's permissions are -rw-rw-r--. 
>> The lock directory is permission drwxrwxr-x also owned by mailman.
> 
> What happens if you change the lock directory to be sgid mailman?  That's the
> way that most of the mailman directories are:
> 
>    [root at lorien]# /bin/ls -lgd ~mailman/locks/
>    drwxrwsr-x   2 mailman  mailman      1024 Apr 20 02:12 /home/staff/mailman/locks/
> 
> Chris

Oops.  I mistyped.  It already is set just that way.




From ian at chiark.greenend.org.uk  Tue Apr 20 13:37:38 1999
From: ian at chiark.greenend.org.uk (Ian Jackson)
Date: Tue, 20 Apr 1999 12:37:38 +0100 (BST)
Subject: [Mailman-Users] `Moderated' list bypass feature doesn't work for me
Message-ID: <14108.26370.712697.769555@chiark.greenend.org.uk>

I've tried to set up a list so that only certain posters can post, but
all the postings seem to require administrative approval.

I have set
 Must posts be approved by an administrator:  No
 Restrict posting privilege to list members?  No
 Addresses of members accepted for posting ...
   <list of email addresses one per line>

When I post, the posting is held.  The poster (as specified in the
From: and envelope, and whose address appears in the accepted posters
list) gets a notification, and when I look at the admin requests page
I see:

 Post held because: Only approved posters may post without moderator
 approval.

The headers of the message as displayed on that page seem slightly
odd.  They give the From: correctly, but the Return-Path and
Message-Id are blank.

I'm using Mailman 1.0b8 (Debian revision 3) and Python 1.5.1 (Debian
revision 7), on Debian GNU/Linux i386 2.0 with some 2.1 upgrades,
notably the libc.

Ian.



From rpyne at kinfolk.org  Tue Apr 20 18:51:00 1999
From: rpyne at kinfolk.org (Richard B. Pyne)
Date: Tue, 20 Apr 1999 09:51:00 -0700
Subject: [Mailman-Users] `Moderated' list bypass feature doesn't work for me
In-Reply-To: <14108.26370.712697.769555@chiark.greenend.org.uk>
Message-ID: <199904201551.JAA03891@ns.kinfolk.org>

The fix is simple, first, make sure you are using 1.0b11, then add 
"USE_ENVELOPE_SENDER = 0" (without the quotes) to mm_cfg.py, this 
will make it use the "From:" header for the match instead of the 
envelope sender.  

On 20 Apr 99, at 12:37, Ian Jackson wrote:

> I've tried to set up a list so that only certain posters can post, but
> all the postings seem to require administrative approval.
> 
> I have set
>  Must posts be approved by an administrator:  No
>  Restrict posting privilege to list members?  No
>  Addresses of members accepted for posting ...
>    <list of email addresses one per line>
> 
> When I post, the posting is held.  The poster (as specified in the
> From: and envelope, and whose address appears in the accepted posters
> list) gets a notification, and when I look at the admin requests page
> I see:
> 
>  Post held because: Only approved posters may post without moderator
>  approval.
> 
> The headers of the message as displayed on that page seem slightly
> odd.  They give the From: correctly, but the Return-Path and
> Message-Id are blank.
> 
> I'm using Mailman 1.0b8 (Debian revision 3) and Python 1.5.1 (Debian
> revision 7), on Debian GNU/Linux i386 2.0 with some 2.1 upgrades,
> notably the libc.
> 
> Ian.
> 
> ------------------------------------------------------
> Mailman-Users maillist  -  Mailman-Users at python.org
> http://www.python.org/mailman/listinfo/mailman-users


------------------------------
Richard B. Pyne, KB7RMU
rpyne at kinfolk.org
http://pyne.kinfolk.org/rbp2




From gonter at maestria.wu-wien.ac.at  Tue Apr 20 21:11:08 1999
From: gonter at maestria.wu-wien.ac.at (Gerhard Gonter)
Date: Tue, 20 Apr 1999 21:11:08 +0200 (MES)
Subject: [Mailman-Users] 1.0b11 bug with underscores in member name?
Message-ID: <199904201911.VAA26242@maestria.wu-wien.ac.at>

I already replied in direct mail but realized that there is in
fact another bug burried in Terry Grace's report.

Addresses with underscores work fine, the problem below was IMO at the
Notes gateway as indicated by the error message.

However, mailman does not recognize the bounced address:

Lotus Notes says:
  ------- Failure Reasons  --------
  User  not listed in public Name & Address Book
  latoya_lemur at notes.wu-wien.ac.at

Mailman apparently matches "not" as the username and thus concludes:

    List:       Test-b8
    Member:     not at notes.wu-wien.ac.at
    Action:     Subscription not disabled.
    Reason:     Excessive or fatal bounces.
    BUT:        User not found.

It's certainly not easy to recognize all possible gateway error
message formats, so maybe that's not even a bug after all ;)

+gg

[earlier direct mail]

According to Grace, Terry:
> I have a list member with underscores in the username (eg
> username_at_hostname at domain.com). When a message goes out to the list the
> following is returned to the list admin and the message is never delivered
> to the user:
> [...]
> User  not listed in public Name & Address Book
> username_at_hostname at domain.com

That's not Mailman's fault, the Lotus Notes(?) internet mail gateway
involved rejects the mail.

This happens quite frequently, as far as I know, especially if the
Lotus mail gateway loses the contact to the Lotus server which has the
address book.

P.S: Some of our lists also have subscribers with underscores in their
     address.

+gg
 
--
Gerhard.Gonter at wu-wien.ac.at  Fax: +43/1/31336/702  g.gonter at ieee.org
Zentrum fuer Informatikdienste, Wirtschaftsuniversitaet Wien, Austria




From James.Nicholson at amedd.army.mil  Tue Apr 20 23:17:17 1999
From: James.Nicholson at amedd.army.mil (Nicholson James D)
Date: Tue, 20 Apr 1999 17:17:17 -0400
Subject: [Mailman-Users] Still need code info for privacy option
Message-ID: <BFDD20E1F489D21191C300104B99B7533DB72B@dasmtaamp032.amedd.army.mil.92.131.in-addr.arpa>

[Nicholson James D]  
I found the problem with the list not remailing anonymously.  In routine
Post(), it deletes the sender and reply-to fields and then sets the from
field.  However, it set the From field to self.GetAdminEmail.  What I needed
it to do (and what I believe it should be doing) is setting the From field
to self.GetListEmail, which will return the list address.  

However, I can't get the damned thing to change the From field for anything.
I've even done a 
	msg.setheader( 'From', 'listname at machine' ).  That's hardwired in
the Post() routine just for testing, and it isn't bloody changing the
header... at all.  I altered the MailList.py file, moved the MailList.pyc to
oldMailList.pyc, and it still does the same damned thing.  It sets the From
field to whoever sent the message.  Was I supposed to recompile the package
or something to get my changes to take effect?  I just don't know python or
mailman well enough to know even this.  Sorry.

-Jim 



From omar at dit.upm.es  Wed Apr 21 16:30:55 1999
From: omar at dit.upm.es (Omar Walid Llorente)
Date: Wed, 21 Apr 1999 16:30:55 +0200 (MET DST)
Subject: [Mailman-Users] Cron <list@petunia> /usr/bin/python /usr/lib/mailman/cron/run_queue 
Message-ID: <Pine.LNX.3.95.990421162131.27723D-100000@oasis.dit.upm.es>

See this message, maybe can help:

http://www.python.org/pipermail/mailman-users/1999-April/001145.html

	Cheers

	Omar.

--------------------------------------------------------------------------------
    Centro de Calculo
    Departamento Ingenieria Telematica (ETSIT)      e-mail: omar at dit.upm.es
    Universidad Politecnica de Madrid               Tel:(+34) 913367366-Ext.328
    Ciudad Universitaria, s/n 28040 Madrid (Spain)  Fax:(+34) 913367333
--------------------------------------------------------------------------------




From csdayton at cs.uchicago.edu  Wed Apr 21 18:41:31 1999
From: csdayton at cs.uchicago.edu (Soren Dayton)
Date: 21 Apr 1999 11:41:31 -0500
Subject: [Mailman-Users] gate_news giving errors (in cron)
Message-ID: <xcdn2022af8.fsf@bernstein.cs.uchicago.edu>


I have two kinds of errors.  Has anyone ever seen these?  This is
1.0b11, python 1.5.2 on Solaris 2.5.

thanks,
Soren


-------------- next part --------------
An embedded message was scrubbed...
From: mailman at cs.uchicago.edu
Subject: no subject
Date: Wed, 21 Apr 1999 10:35:07 -0500 (CDT)
Size: 494
Url: http://mail.python.org/pipermail/mailman-users/attachments/19990421/8b52cd93/attachment.mht 
-------------- next part --------------
An embedded message was scrubbed...
From: unknown sender
Subject: no subject
Date: no date
Size: 38
Url: http://mail.python.org/pipermail/mailman-users/attachments/19990421/8b52cd93/attachment-0001.mht 

From mailman at cs.uchicago.edu  Wed Apr 21 10:40:09 1999
From: mailman at cs.uchicago.edu (mailman at cs.uchicago.edu)
Date: Wed, 21 Apr 1999 03:40:09 -0500 (CDT)
Subject: No subject
Message-ID: <199904210840.DAA07650@alexandria.cs.uchicago.edu>

To: mailman
Subject: Output from "cron" command

Your "cron" job

/opt/local/bin/python /homes/mailman/cron/gate_news

produced the following output:

Exception exceptions.IOError: (2, 'No such file or directory') in <method FileLock.__del__ of FileLock instance at bad70> ignored


--Multipart_Wed_Apr_21_11:41:31_1999-1--



From deadline at plogic.com  Wed Apr 21 21:01:11 1999
From: deadline at plogic.com (Douglas Eadline)
Date: Wed, 21 Apr 1999 15:01:11 -0400 (EDT)
Subject: [Mailman-Users] Unable to send due to localhost?
Message-ID: <Pine.LNX.4.04.9904211448330.18667-100000@lisa.plogic.com>

I have installed mailman 1.0b11 on a RH Linux 5.2 (2.0.36)
system.  Everything works Ok, except for this one
annoying problem.  I can not get the list to recognized my posts.

The list is restricted so that you must subscribe to post.
Well I subscribed, with my address of deadline at plogic.com,
but mailman treats this as deadline at local host and rejects it.

The rejection mail looks fine :

Your authorization is required for a mailing list posting request
approval:

    List:         Bert at plogic.com
    Reason held:  Postings from member addresses only.
    From:         deadline at plogic.com
    Subject:      Bert problem (fwd)



BUT, the administrative page shows the following:


From klm at digicool.com  Thu Apr 22 00:49:50 1999
From: klm at digicool.com (Ken Manheimer)
Date: Wed, 21 Apr 1999 18:49:50 -0400
Subject: [Mailman-Users] how to install
Message-ID: <613145F79272D211914B0020AFF640190BEE82@gandalf.digicool.com>

On Fri, 16 Apr, pehr anderson wrote:

> I wrote the following installation script trying to follow 
> all the docs.
> 
> Please tell me what I'm doing wrong. It seems like I'm missing
> something pretty fundamental.

> [various stuff, including an appropriate warning about stomping
existing installs]
> cd /home/mailman

Interesting - you're putting the distribution inside the installation
dir.  I do that also - i think it's a nice way to organize it, though it
can be confusing to those who take over the maintenance after you, if
you don't make it clear.

I'm not sure the following excerpt does what you want:

> tar xzf ~pehr/gz/mailman.tar.gz
> chgrp mailman   /home/mailman
> chmod a+rx,g+ws /home/mailman

Did you want to do 'chgrp -R ...' and 'chmod -R ...'?

I'm not sure about the rest - it's ambitous - but have a warning about
the last part:

> echo "Hope it worked!"
> echo "Now browse to "
> echo "http://localhost/pipermail/"
> echo "   -pehr"
> lynx http://localhost/pipermail

People may be disappointed if they follow that suggestion, because the
actual archives for a list are initialized when the list first gets
messages, not when the list is created.

I haven't looked this over as carefully as i'd like - would be
interested to hear feedback from others on it...

ken manheimer
klm at digicool.com



From gconnor at nekodojo.org  Thu Apr 22 07:44:53 1999
From: gconnor at nekodojo.org (Greg Connor)
Date: Wed, 21 Apr 1999 22:44:53 -0700
Subject: [Mailman-Users] Not to bug everyone, but...
In-Reply-To: <371B3FCC.568E230C@rfa.org>
Message-ID: <4.1.19990421224156.0097c8a0@pop.nekodojo.org>

At 10:38 AM 4/19/99 -0400, Adam wrote:
>I tried posting last week, but never got a reply. Can someone point out
>to me why i'm getting these errors on a RedHat linux box (v5.1)?
>
>I'm getting these errors in /var/log/cron from mailman. Can anyone tell
>me what this is all about, and how to fix it? I know that the cron
>daemon is being asked to run this via mailman, but is this just a
>permissions issue, or possibly a bad install? I'll also attach an
>emailed error that I used to get, but no longer get anymore for some
>reason...
>
>mailman (04/15-11:12:00-5473) CMD (/usr/bin/python
>/home/mailman/cron/run_queue)


This is not likely to be a problem in itself... I am getting these too and
the system is working fine as far as I can tell.  Note that every command
cron executes is logged here.


>This is a copy of one of the emails I used to get:
>
>Traceback (innermost last):
>  File "/home/mailman/cron/run_queue", line 31, in ?
>    OutgoingQueue.processQueue()
>  File "/home/mailman/Mailman/OutgoingQueue.py", line 86, in
>processQueue
>    lock_file.lock()
>  File "/home/mailman/Mailman/flock.py", line 119, in lock
>    os.link(self.lockfile, self.tmpfname)
>os.error: (13, 'Permission denied')


I haven't seen this before (maybe the other reply in this thread is useful
:)  But if you're not getting it anymore, that probably means the problem
has been solved...

good luck



From ijackson at chiark.greenend.org.uk  Thu Apr 22 16:02:05 1999
From: ijackson at chiark.greenend.org.uk (Ian Jackson)
Date: Thu, 22 Apr 1999 15:02:05 +0100 (BST)
Subject: [Mailman-Users] Re: Mailman bug
In-Reply-To: <E10aJq5-0003HO-00@kirtley.cl.cam.ac.uk>
References: <E10aJq5-0003HO-00@kirtley.cl.cam.ac.uk>
Message-ID: <14111.11229.265474.424901@chiark.greenend.org.uk>

Stephen Early writes ("Mailman bug"):
> When trying to view the subscribers list of 'troubadours', which is
> only available to list members, and providing a bogus address and
> password:
> 
> 
> Bug in Mailman version 1.0b11
> 
> Traceback (innermost last):
>   File "/var/lib/mailman/scripts/driver", line 112, in run_main
>     main()
>   File "/usr/lib/mailman/Mailman/Cgi/roster.py", line 61, in main
>     list.ConfirmUserPassword(id, pw)
>   File "/usr/lib/mailman/Mailman/SecurityManager.py", line 76, in ConfirmUserPassword
>     raise Errors.MMNotAMemberError
> MMNotAMemberError

I'm using Mailman 1.0b11.  I installed it as a home-made Debian
package, using the debianisation patch from Debian's 1.0b8-3.

(The lists are at www.chiark.greenend.org.uk/mailman/listinfo etc.)

Ian.



From steve at unganisha.idrc.ca  Thu Apr 22 16:45:05 1999
From: steve at unganisha.idrc.ca (Steve Song)
Date: Thu, 22 Apr 1999 10:45:05 -0400
Subject: [Mailman-Users] Message Footer Option
In-Reply-To: <199904220505.BAA14323@python.org>
Message-ID: <4.1.19990422104103.00a4bcb0@internet.idrc.ca>

In the help file for message footer options it says:  " This text can
include %(field)s format strings which are resolved against the list's
attribute dictionary (__dict__). Some useful fields are: ....."

How can we find out what is in the list's attribute directory?  Are there
more variables that can be used?  The name of the sender for instance would
be MOST useful.

Thanks... Steve Song



______________________________________________________________
Steve Song <steve at unganisha.idrc.ca>
Unganisha (Connectivity) Project <http://www.idrc.ca/unganisha>



From dboyd at its.to  Sat Apr 24 01:48:46 1999
From: dboyd at its.to (Darren Boyd)
Date: Fri, 23 Apr 1999 17:48:46 -0600
Subject: [Mailman-Users] Reply-To, To, Sender, and other addresses
Message-ID: <372106DE.1740B0CC@its.to>

Hi,

I have two mailman servers setup and they seem to funtion differently
with respect to the host part of the mail address that is put into the
header.  I have one mailman server putting the 'hostname this list
prefers' hostname in correctly, but the other is not.  As far as I can
tell the two machines are setup the same.

Note:  I removed the headers I deamed unimportant. 

The one that works looks like this:

To: security_audit at cal.montage.ca
Reply-To: security_audit at cal.montage.ca
Sender: security_audit-admin at cal.montage.ca
Errors-To: security_audit-admin at cal.montage.ca
X-Mailman-Version: 1.0b7
List-Id: Montage Security Audit List <security_audit.cal.montage.ca>
X-BeenThere: security_audit at cal.montage.ca


The other (that doesn't work) looks like this:

To: test at a.calgary.linux.ca
Reply-To: test at a.calgary.linux.ca
Sender: test-admin at a.calgary.linux.ca
Errors-To: test-admin at a.calgary.linux.ca
X-Mailman-Version: 1.0b11
List-Id: A Test List <test.calgary.linux.ca>
X-BeenThere: test at calgary.linux.ca

Notice that the X-BeenThere header is correct but not the rest of the
headers.

Anyone have any ideas why this does this?

The nonworking system is running RedHat Linux 5.2, Sendmail 8.8.7,
python 1.5.1, apache 1.3.3.

Thanks,
Darren



From che at debian.org  Sat Apr 24 02:31:15 1999
From: che at debian.org (Ben Gertzfield)
Date: 23 Apr 1999 17:31:15 -0700
Subject: [Mailman-Users] Reply-To, To, Sender, and other addresses
In-Reply-To: Darren Boyd's message of "Fri, 23 Apr 1999 17:48:46 -0600"
References: <372106DE.1740B0CC@its.to>
Message-ID: <yttso9quaek.fsf@gilgamesh.cse.ucsc.edu>

>>>>> "Darren" == Darren Boyd <dboyd at its.to> writes:

    Darren> Notice that the X-BeenThere header is correct but not the
    Darren> rest of the headers.

    Darren> Anyone have any ideas why this does this?

    Darren> The nonworking system is running RedHat Linux 5.2,
    Darren> Sendmail 8.8.7, python 1.5.1, apache 1.3.3.

I'm not sure if Mailman can possibly fake these headers. To make
sendmail fake the rest of the headers, I had to munge with my sendmail
config thusly:

(in /etc/mail/sendmail.mc)

FEATURE(`genericstable', `hash /etc/mail/genericstable')dnl
GENERICS_DOMAIN_FILE(`/etc/mail/sendmail.cG')dnl

(in /etc/mail/genericstable)

$ cat genericstable
maillist-request         maillist-request at domain.i.want.com
maillist                 maillist at domain.i.want.com
maillist-admin           maillist-admin at domain.i.want.com
maillist-owner           maillist-owner at domain.i.want.com
owner-maillist           owner-maillist at domain.i.want.com

(in /etc/mail/sendmail.cG)

domain.i.want.com

Ben

-- 
Brought to you by the letters I and N and the number 2.
"Hello! We are only joke. It is funny enough."
Debian GNU/Linux maintainer of Gimp and GTK+ -- http://www.debian.org/
I'm on FurryMUCK as Che, and EFNet/Open Projects IRC as Che_Fox.



From ptb at ptb.org  Sat Apr 24 17:26:02 1999
From: ptb at ptb.org (Paul Barnett)
Date: Sat, 24 Apr 1999 10:26:02 -0500
Subject: [Mailman-Users] NoMail option on membership management broken?
Message-ID: <0e1301be8e66$c39df530$0201a8c0@ptb.org>

I'm running 1.0b11.

One of the subscribers to my mailing list is out of the country for an
extended period, and I used "membership management" to check the "nomail"
option until he returns.

However, it has no effect -- the mail is still being sent to him.

One possible unusual situation:  he has MIME-formatting of digests selected,
but didn't enable digests.  I would hope that makes no difference, but I
thought I'd note it.





From mcook at unidial.com  Sat Apr 24 23:30:44 1999
From: mcook at unidial.com (Merrill Cook)
Date: Sat, 24 Apr 1999 17:30:44 -0400
Subject: [Mailman-Users] installing on SCO
Message-ID: <37223804.1CAFC54C@unidial.com>

Trying to install mailman on SCO 5.04 with the developer package and a
gcc.

Can someone tell me what this means and what the next steps are to fix
it?
It looks like some symbol is undefined, but it doesn't say whose symbol
it should be or where to go to add it.

        gcc -DSCRIPT="\"admin\"" -I. -DCGI_GID=28 -g -O2 
-DHAVE_STRERROR=1 -DHAVE_SETREGID=1 -DSTDC_HEADERS=1 -DHAVE_SYSLOG_H=1 
-DGETGROUPS_T=gid_t -DHAVE_VPRINTF=1  common.o -o admin ./cgi-wrapper.c
Undefined                       first referenced
 symbol                             in file
std_syslog                          common.o
openlog                             common.o
closelog                            common.o
admin: fatal error: Symbol referencing errors. No output written to
admin
*** Error code 1 (bu21)
*** Error code 1 (bu21)



From ckolar at admin.aurora.edu  Mon Apr 26 18:59:54 1999
From: ckolar at admin.aurora.edu (Christopher Kolar)
Date: Mon, 26 Apr 1999 11:59:54 -0500
Subject: [Mailman-Users] unknown mailer error
Message-ID: <4.2.0.32.19990426115703.00fc0640@admin.aurora.edu>

Hello everyone.  I have a feeling that this is a quick fix, but I could not 
find anything about it in the archives.

I just did a new install on DEC OSF 4.0b of mailman b11 with Apache 
1.3.4.  Everything on the web side seems to work, but I am getting an error 
when trying to post or send things to the admin address.  I am getting this 
response in the log files.

+++++
----- The following addresses had permanent fatal errors -----
"|/usr/users/mailman/mail/wrapper mailcmd istest"
(expanded from: <istest-request at students.aurora.edu>)
----- Transcript of session follows -----554 
"|/usr/users/mailman/mail/wrapper mailcmd istest"... unknown mailer error 2
+++++

The only configuration option that we set was for the main path.  I am not 
sure if this means that we have to set a different uid/gid for the sendmail 
or what.  Any suggestions would be much appreciated.  Thanks in advance.

--chris

--
/////\\\\\/////\\\\\
 Christopher G. Kolar
   Director of Instructional Technology
   Aurora University, Aurora, Illinois
 ckolar at aurora.edu  --  www.aurora.edu
        [View full header for public key recovery information.]




From kevin at vulcanind.com  Mon Apr 26 20:47:57 1999
From: kevin at vulcanind.com (Kevin Lee)
Date: Mon, 26 Apr 1999 13:47:57 -0500
Subject: [Mailman-Users] Exim errors
Message-ID: <3.0.2.32.19990426134757.00ba2d50@iris.vulcanind.com>


I have been really impressed with the features of mailman and I would
really like to get it to work.  I am a newbie when it comes to Linux
(debian) so I would appreciate any help you might be able to send.

I am getting the following error in the /var/log/exim/mainlog:

1999-04-26 13:38:01 10boHL-0000BC-00 Neither the system_alias director nor
the address_pipe transport set a uid for local delivery of
|/usr/lib/mailman/mail/wrapper post sales

Below I have listed my exim.conf file:

# This is the main exim configuration file.
# It was originally generated by `eximconfig', part of the exim package
# distributed with Debian, but it may edited by the mail system administrator.
# This file originally generated by eximconfig at Tue May  4 16:51:12 CDT 1999
# See exim info section for details of the things that can be configured here.

# Please see the manual for a complete list
# of all the runtime configuration options that can be included in a
# configuration file.

# This file is divided into several parts, all but the last of which are
# terminated by a line containing the word "end". The parts must appear
# in the correct order, and all must be present (even if some of them are
# in fact empty). Blank lines, and lines starting with # are ignored.

######################################################################
#                    MAIN CONFIGURATION SETTINGS                     #
######################################################################

# Specify the domain you want to be added to all unqualified addresses
# here. Unqualified addresses are accepted only from local callers by
# default. See the receiver_unqualified_{hosts,nets} options if you want
# to permit unqualified addresses from remote sources. If this option is
# not set, the primary_hostname value is used for qualification.

qualify_domain = Bahnstormin.vulcanind.com

# If you want unqualified recipient addresses to be qualified with a different
# domain to unqualified sender addresses, specify the recipient domain here.
# If this option is not set, the qualify_domain value is used.

# qualify_recipient =

# Specify your local domains as a colon-separated list here. If this option
# is not set (i.e. not mentioned in the configuration file), the
# qualify_recipient value is used as the only local domain. If you do not want
# to do any local deliveries, uncomment the following line, but do not supply
# any data for it. This sets local_domains to an empty string, which is not
# the same as not mentioning it at all. An empty string specifies that there
# are no local domains; not setting it at all causes the default value (the
# setting of qualify_recipient) to be used.

local_domains = vulcanind.com

# Allow mail addressed to our hostname, or to our IP address.

local_domains_include_host = true
local_domains_include_host_literals = true

# Domains we relay for; that is domains that aren't considered local but we 
# accept mail for them.

relay_domains = vulcanind.com

# If this is uncommented, we accept and relay mail for all domains we are 
# in the DNS as an MX for.

#relay_domains_include_local_mx = true

# No local deliveries will ever be run under the uids of these users (a colon-
# separated list). An attempt to do so gets changed so that it runs under the
# uid of "nobody" instead. This is a paranoic safety catch. Note the default
# setting means you cannot deliver mail addressed to root as if it were a
# normal user. This isn't usually a problem, as most sites have an alias for
# root that redirects such mail to a human administrator.

never_users = root

# The setting below causes Exim to do a reverse DNS lookup on all incoming
# IP calls, in order to get the true host name. If you feel this is too
# expensive, you can specify the networks for which a lookup is done, or
# remove the setting entirely.

#host_lookup_nets = 0.0.0.0/0

# Exim contains support for the Realtime Blocking List (RBL) that is being 
# maintained as part of the DNS. See http://maps.vix.com/rbl/ for background.
# Uncommenting the following line will make Exim reject mail from any
# host whose IP address is blacklisted in the RBL at maps.vix.com.

#rbl_domains = rbl.maps.vix.com
#rbl_reject_recipients = false
#rbl_warn_header = true

# The setting below locks out the use of your host as a mail relay by any
# other host. See the section of the manual entitled "Control of relaying" 
# for more info.

sender_host_reject_relay = *

sender_host_reject = +allow_unknown

# If you want Exim to support the "percent hack" for all your local domains,
# uncomment the following line. This is the feature by which mail addressed
# to x%y at z (where z is one of your local domains) is locally rerouted to
# x at y and sent on. Otherwise x%y is treated as an ordinary local part.

# percent_hack_domains=*

# If this option is set, then any process that is running as one of the
# listed users may pass a message to Exim and specify the sender's
# address using the "-f" command line option, without Exim's adding a
# "Sender" header.

trusted_users = mailman

# If this option is true, the SMTP command VRFY is supported on incoming
# SMTP connections; otherwise it is not.

smtp_verify = true

# Some operating systems use the "gecos" field in the system password file
# to hold other information in addition to users' real names. Exim looks up
# this field when it is creating "sender" and "from" headers. If these options
# are set, exim uses "gecos_pattern" to parse the gecos field, and then
# expands "gecos_name" as the user's name. $1 etc refer to sub-fields matched
# by the pattern.

gecos_pattern = ^([^,:]*)
gecos_name = $1

# This string defines the contents of the \`Received' message header that
# is added to each message, except for the timestamp, which is automatically
# added on at the end, preceded by a semicolon. The string is expanded each
# time it is used.

received_header_text = "Received: \
          ${if def:sender_fullhost {from ${sender_fullhost} \
          ${if def:sender_ident {(${sender_ident})}}\n\t}\
          {${if def:sender_ident {from ${sender_ident} }}}}\
          by ${primary_hostname} \
          ${if def:received_protocol {with ${received_protocol}}} \
          (Exim ${version_number} #${compile_number} (Debian))\n\t\
          id ${message_id}"
end


######################################################################
#                      TRANSPORTS CONFIGURATION                      #
######################################################################
#                       ORDER DOES NOT MATTER                        #
#     Only one appropriate transport is called for each delivery.    #
######################################################################

# This transport is used for local delivery to user mailboxes. On debian
# systems group mail is used so we can write to the /var/spool/mail
# directory. (The alternative, which most other unixes use, is to deliver
# as the user's own group, into a sticky-bitted directory)

local_delivery:
  driver = appendfile
  group = mail
  mode = 0660
  mode_fail_narrower = false
  file = /var/spool/mail/${local_part}

# This transport is used for handling pipe addresses generated by alias
# or .forward files. It has a conventional name, since it is not actually
# mentioned elsewhere in this configuration file. (A different name *can*
# be specified via the "address_pipe_transport" option if you really want
# to.) If the pipe generates any standard output, it is returned to the sender
# of the message as a delivery error. Set return_fail_output instead if you
# want this to happen only when the pipe fails to complete normally.

address_pipe:
  driver = pipe
  return_output

# This transport is used for handling file addresses generated by alias
# or .forward files. It has a conventional name, since it is not actually
# mentioned elsewhere in this configuration file.

address_file:
  driver = appendfile

# This transport is used for handling file addresses generated by alias
# or .forward files if the path ends in "/", which causes it to be treated
# as a directory name rather than a file name. Each message is then delivered
# to a unique file in the directory. If instead you want all such
deliveries to
# be in the "maildir" format that is used by some other mail software,
# uncomment the final option below. If this is done, the directory specified
# in the .forward or alias file is the base maildir directory.
#
# Should you want to be able to specify either maildir or non-maildir
# directory-style deliveries, then you must set up yet another transport,
# called address_directory2. This is used if the path ends in "//" so should
# be the one used for maildir, as the double slash suggests another level
# of directory. In the absence of address_directory2, paths ending in //
# are passed to address_directory.

address_directory:
  driver = appendfile
  no_from_hack
  prefix = ""
  suffix = ""
# maildir_format

# This transport is used for handling autoreplies generated by the filtering
# option of the forwardfile director. It has a conventional name, since it
# is not actually mentioned elsewhere in this configuration file.

address_reply:
  driver = autoreply

# This transport is used for delivering messages over SMTP connections.

remote_smtp:
  driver = smtp

# This transport is used for mailman.

mailman_lists:
  driver = pipe
  allow_commands = /usr/lib/mailman/mail/wrapper 
  user = mailman
  group = mail
  return_fail_output
  
end


######################################################################
#                      DIRECTORS CONFIGURATION                       #
#             Specifies how local addresses are handled              #
######################################################################
#                          ORDER DOES MATTER                         #
#   A local address is passed to each in turn until it is accepted.  #
######################################################################

# This allows local delivery to be forced, avoiding alias files and
# forwarding.

real_local:
  prefix = real-
  driver = localuser
  transport = local_delivery

# This director handles aliasing using a traditional /etc/aliases file.
# If any of your aliases expand to pipes or files, you will need to set
# up a user and a group for these deliveries to run under. You can do
# this by uncommenting the "user" option below (changing the user name
# as appropriate) and adding a "group" option if necessary.

system_aliases:
  driver = aliasfile
  file = /etc/aliases
  search_type = lsearch

mailman_aliases:
  driver = aliasfile
  search_type = lsearch
  file = /etc/aliases

# user = list
# Uncomment the above line if you are running smartlist

# This director handles forwarding using traditional .forward files.
# It also allows mail filtering when a forward file starts with the 
# string "# Exim filter": to disable filtering, uncomment the "filter" 
# option. The check_ancestor option means that if the forward file 
# generates an address that is an ancestor of the current one, the 
# current one gets passed on instead. This covers the case where A is 
# aliased to B and B has a .forward file pointing to A.

# For standard debian setup of one group per user, it is acceptable---normal
# even---for .forward to be group writable. If you have everyone in one
# group, you should comment out the "modemask" line. Without it, the exim
# default of 022 will apply, which is probably what you want.

userforward:
  driver = forwardfile
  no_verify
  check_ancestor
  file = .forward
  modemask = 002
  filter

# This director matches local user mailboxes.

localuser:
  driver = localuser
  transport = local_delivery

# This director is for mailman.

mailman_lists:
  driver = aliasfile
  search_type = lsearch
  file = /etc/aliases
  pipe_transport = mailman_lists

end


######################################################################
#                      ROUTERS CONFIGURATION                         #
#            Specifies how remote addresses are handled              #
######################################################################
#                          ORDER DOES MATTER                         #
#  A remote address is passed to each in turn until it is accepted.  #
######################################################################

# Remote addresses are those with a domain that does not match any item
# in the "local_domains" setting above.

# This router routes to remote hosts over SMTP using a DNS lookup with
# default options.

lookuphost:
  driver = lookuphost
  transport = remote_smtp

# This router routes to remote hosts over SMTP by explicit IP address,
# given as a "domain literal" in the form [nnn.nnn.nnn.nnn]. The RFCs
# require this facility, which is why it is enabled by default in Exim.
# If you want to lock it out, set forbid_domain_literals in the main
# configuration section above.

literal:
  driver = ipliteral
  transport = remote_smtp

end


######################################################################
#                      RETRY CONFIGURATION                           #
######################################################################

# This single retry rule applies to all domains and all errors. It specifies
# retries every 15 minutes for 2 hours, then increasing retry intervals,
# starting at 2 hours and increasing each time by a factor of 1.5, up to 16
# hours, then retries every 8 hours until 4 days have passed since the first
# failed delivery.

# Domain               Error       Retries
# ------               -----       -------

*                      *           F,2h,15m; G,16h,2h,1.5; F,4d,8h

end


######################################################################
#                      REWRITE CONFIGURATION                         #
######################################################################


# There are no rewriting specifications in this default configuration file.


# This is an example of a useful rewriting rule---it looks up the real
# address of all local users in a file

# *@Bahnstormin.vulcanind.com    ${lookup{$1}lsearch{/etc/email-addresses}\
#						{$value}fail} bcfrF

# End of Exim configuration file




Kevin Lee
Vulcan Industries
(205) 640-2433

mailto:kevin at vulcanind.com

http://www.vulcanind.com







From klm at digicool.com  Mon Apr 26 23:26:18 1999
From: klm at digicool.com (Ken Manheimer)
Date: Mon, 26 Apr 1999 17:26:18 -0400
Subject: [Mailman-Users] NoMail option on membership
Message-ID: <613145F79272D211914B0020AFF640190BEE92@gandalf.digicool.com>

Paul Barnett wrote:

> One of the subscribers to my mailing list is out of the country for an
> extended period, and I used "membership management" to check the
"nomail"
> option until he returns.
> 
> However, it has no effect -- the mail is still being sent to him.

I don't have a fix, but i do have a something to try - go to the user's
actual options page, and see if resetting the delivery option (using the
site or list manager's password to authorize) does the job.  For that
matter, check to make sure it is set as you expect.

If this doesn't do it, i can only suggest entering a bug report in the
jitterbug db - i think the url is http://www.python.org/mailman-bugs .
(Bonus points for tracking down the bad code and reporting the fix!!-)

Ken Manheimer
klm at digicool.com



From bwarsaw at cnri.reston.va.us  Wed Apr 28 00:18:16 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Tue, 27 Apr 1999 18:18:16 -0400 (EDT)
Subject: [Mailman-Users] NoMail option on membership
References: <613145F79272D211914B0020AFF640190BEE92@gandalf.digicool.com>
Message-ID: <14118.14248.496964.798817@anthem.cnri.reston.va.us>

>>>>> "KM" == Ken Manheimer <klm at digicool.com> writes:

    KM> I don't have a fix, but i do have a something to try

I can't seem to reproduce this.
    
    KM> If this doesn't do it, i can only suggest entering a bug
    KM> report in the jitterbug db - i think the url is
    KM> http://www.python.org/mailman-bugs .  (Bonus points for
    KM> tracking down the bad code and reporting the fix!!-)

This is the thing to do.  I'm basically at the point where I'm relying 
on the bug database to figure out what to attack next.  I can't seem
to keep up with traffic on the mailing lists :-(

-Barry



From bwarsaw at cnri.reston.va.us  Wed Apr 28 00:31:18 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Tue, 27 Apr 1999 18:31:18 -0400 (EDT)
Subject: [Mailman-Users] installing on SCO
References: <37223804.1CAFC54C@unidial.com>
Message-ID: <14118.15030.319920.856645@anthem.cnri.reston.va.us>

>>>>> "MC" == Merrill Cook <mcook at unidial.com> writes:

    MC> Trying to install mailman on SCO 5.04 with the developer
    MC> package and a gcc.

    MC> Can someone tell me what this means and what the next steps
    MC> are to fix it?  It looks like some symbol is undefined, but it
    MC> doesn't say whose symbol it should be or where to go to add
    MC> it.

    MC>         gcc -DSCRIPT="\"admin\"" -I. -DCGI_GID=28 -g -O2
    MC> -DHAVE_STRERROR=1 -DHAVE_SETREGID=1 -DSTDC_HEADERS=1
    MC> -DHAVE_SYSLOG_H=1 -DGETGROUPS_T=gid_t -DHAVE_VPRINTF=1
    MC> common.o -o admin ./cgi-wrapper.c Undefined first referenced
    MC> symbol in file std_syslog common.o openlog common.o closelog
    MC> common.o admin: fatal error: Symbol referencing errors. No
    MC> output written to admin *** Error code 1 (bu21) *** Error code
    MC> 1 (bu21)

This could mean that the syslog functions are not in libc on SCO
5.04.  I don't have access to this OS so I can't check this.  If you
can figure out what library has the syslog functions, we can craft an
autoconf test for this.

-Barry



From bwarsaw at cnri.reston.va.us  Wed Apr 28 04:24:25 1999
From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw)
Date: Tue, 27 Apr 1999 22:24:25 -0400 (EDT)
Subject: [Mailman-Users] Re: Mailman bug
References: <E10aJq5-0003HO-00@kirtley.cl.cam.ac.uk>
	<14111.11229.265474.424901@chiark.greenend.org.uk>
Message-ID: <14118.29017.405703.66158@anthem.cnri.reston.va.us>

>>>>> "IJ" == Ian Jackson <ijackson at chiark.greenend.org.uk> writes:

    IJ> I'm using Mailman 1.0b11.  I installed it as a home-made
    IJ> Debian package, using the debianisation patch from Debian's
    IJ> 1.0b8-3.

    IJ> (The lists are at www.chiark.greenend.org.uk/mailman/listinfo
    IJ> etc.)

Simple patch.  Thanks for the report.
-Barry

Index: roster.py
===================================================================
RCS file: /projects/cvsroot/mailman/Mailman/Cgi/roster.py,v
retrieving revision 1.5
retrieving revision 1.6
diff -c -r1.5 -r1.6
*** roster.py	1998/12/27 20:04:02	1.5
--- roster.py	1999/04/28 02:23:32	1.6
***************
*** 60,66 ****
                          try:
                              list.ConfirmUserPassword(id, pw)
                          except (Errors.MMBadUserError, 
!                                 Errors.MMBadPasswordError):
                              bad = ("%s subscriber authentication failed."
                                     % list.real_name)
                      else:
--- 60,67 ----
                          try:
                              list.ConfirmUserPassword(id, pw)
                          except (Errors.MMBadUserError, 
!                                 Errors.MMBadPasswordError,
!                                 Errors.MMNotAMemberError):
                              bad = ("%s subscriber authentication failed."
                                     % list.real_name)
                      else:



From rpyne at kinfolk.org  Thu Apr 29 01:46:19 1999
From: rpyne at kinfolk.org (Richard B. Pyne)
Date: Wed, 28 Apr 1999 16:46:19 -0700
Subject: [Mailman-Users] (another) Mailman bug
In-Reply-To: <14118.29017.405703.66158@anthem.cnri.reston.va.us>
Message-ID: <199904282246.QAA03313@ns.kinfolk.org>

Running Mailman 1.0b11 under Linux I am getting random Memory Errors 
such as:


Traceback (innermost last):
  File "/home/mailman/cron/gate_news", line 27, in ?
    from Mailman import MailList
  File "/home/mailman/Mailman/MailList.py", line 30, in ?
    import Utils
  File "/home/mailman/Mailman/Utils.py", line 31, in ?
    import regsub
MemoryError

Others are bouncing mail. Any help will be greatly appreciated.


------------------------------
Richard B. Pyne, KB7RMU
rpyne at kinfolk.org
http://pyne.kinfolk.org/rbp2




From simonb at simonb.de  Thu Apr 29 18:10:19 1999
From: simonb at simonb.de (Simon Berg)
Date: Thu, 29 Apr 1999 18:10:19 +0200
Subject: [Mailman-Users] list addressing
Message-ID: <3728846B.19B7BDFA@gmx.net>

hi there,

i am *not* a unix guru. that's why i got some problems with list
addressing.

i am running mailman 1.0b11 under irix 6.2 on an sgi indy.
when i'm posting to a list, let's say
mailto:test at lists.kommwiss.fu-berlin.de ,
the message that's sent by mailman only contains the to-header
test at lists .

is this a bug or a feature?
how do i modify this?

btw: lists.kommwiss.fu-berlin.de is an alias (CNAME). so maybe my
problem concerns sendmail configuration. in this case: where can i
get information on that topic?

thanks in advance

--
best regards & peace     Simon Berg (simonb at gmx.net)





From kevin at vulcanind.com  Fri Apr 30 16:20:46 1999
From: kevin at vulcanind.com (Kevin Lee)
Date: Fri, 30 Apr 1999 09:20:46 -0500
Subject: [Mailman-Users] Exim errors
In-Reply-To: <E10d9AZ-0004Cy-00@petunia.hsc.usc.edu>
References: <3.0.2.32.19990426134757.00ba2d50@iris.vulcanind.com>
Message-ID: <3.0.2.32.19990430092046.00b2d160@iris.vulcanind.com>

Don,

I am using Debian's GNU/Linux ver 2.1 with exim as my MTA.  I am also going
to post this reply to eht Mailman-Users list also.

First of all I would like to thank Michael Yount for his help.  He was the
person who solved the problem.

***************

This is what Michael wrote:

Okay, here's what's happening.  The directors are run in order,
and the system_aliases director appears first.  The mailman list
address is found in /etc/aliases, so exim says "aha, here
it is," attempts to pipe the mail to the wrapper with no
specified privileges, and bombs with the error you see.

If you placed the mailman director first, you'd have a similar
problem...every alias on your system would be considered
to have user mailman and group list.  That might cause
problems with the other aliases.

I'd suggest the following...
* Take the mailman aliases that use pipes out of /etc/aliases
and put them in their own file.

* Change the mailman director to use that file instead of
/etc/aliases.

* If you're running exim as a standalone daemon, be sure to 
kill -HUP the daemon process after you modify the config file.

I'll be offline until this evening.  If something goes wrong,
please send me the exim errors and I'll make further suggestions,
probably tomorrow morning.

Michael

*****************

I followed Michael's instructions and moved my mailman aliases out of
/etc/aliases and into /etc/mailman-aliases.  My /etc/mailman-aliases file
looks like the following:

sales:           "|/usr/lib/mailman/mail/wrapper post sales"
sales-admin:     "|/usr/lib/mailman/mail/wrapper mailowner sales"
sales-request:   "|/usr/lib/mailman/mail/wrapper mailcmd sales"
owner-sales:      sales-admin
sales-owner:      sales-admin

estimating:          "|/usr/lib/mailman/mail/wrapper post estimating"
estimating-admin:    "|/usr/lib/mailman/mail/wrapper mailowner estimating"
estimating-requests: "|/usr/lib/mailman/mail/wrapper mailcmd sales"
owner-estimating:    estimating-admin
estimating-owner:    estimating-admin

engineering:           "|/var/lib/mailman/wrapper post engineering"
engineering-admin:     "|/var/lib/mailman/wrapper mailowner engineering"
engineering-request:   "|/var/lib/mailman/wrapper mailcmd engineering"
owner-engineering:     engineering-admin
engineering-owner:     engineering-admin


I then deleted all of the code that I had added to my /etc/exim.conf as per
FAQs, and archives.  I added the following code as Micheal suggested at the
very end of the directors configuration (just before the end statement) in
the /etc/exim.conf file:

mailman:
  driver = aliasfile
  search_type = lsearch
  file = /etc/mailman-aliases
  modemask = 002
  user = mailman  
  group = list 


I am still getting some cron errors when running run_queue, but the system
is distributing e-mails correctly now.  I just haven't had a chance to look
at the cron errors yet.


******************


At 02:01 AM 4/30/99 -0700, Don wrote:
>
>I saw your post a few days ago regarding your errors with Mailman and
>Exim, and was hoping to see some replies because I've been having the
>very same problem, but have seen no replies.  Have you gotten some
>replies directly?  If you have could you possibly forward them to me,
>and if you haven't, have you gotten anywhere on solving your problem?
>
>Would appreciate any help I can get.  I have tried some to get Mailman
>running (actually it is running, I guess, but rather useless unless it
>will actually forward mail) but, after getting stuck, have had to attend
>to other matters for the last week or so, but now would like to get it
>working.  I am also using Debian linux and Exim. Exim seems to be
>working fine in other respects.
>
>Don MacDougall
>dmacdoug at hsc.usc.edu
>
>


Kevin Lee
Vulcan Industries
(205) 640-2433

mailto:kevin at vulcanind.com

http://www.vulcanind.com







From kevin at vulcanind.com  Fri Apr 30 18:44:38 1999
From: kevin at vulcanind.com (Kevin Lee)
Date: Fri, 30 Apr 1999 11:44:38 -0500
Subject: [Mailman-Users] deleting archives
Message-ID: <3.0.2.32.19990430114438.00b401b8@iris.vulcanind.com>

	
I have got Mailman running and tested on a Debian GNU/Linux box.  I am
going to put this into production in the next few days on our intranet.
During my testing phase I just used forwarded copies of one of my favorite
digests.  Well now I got 50-60 copies of these digests in my archives, and
it is not exactly appropriate reading material for business use.  

I can not find anything in the FAQs or archives that addresses deleting and
restarting the archives.  Any suggestions?


Kevin Lee
Vulcan Industries
(205) 640-2433

mailto:kevin at vulcanind.com

http://www.vulcanind.com







From bryner at uiuc.edu  Fri Apr 30 18:52:19 1999
From: bryner at uiuc.edu (Brian Ryner)
Date: Fri, 30 Apr 1999 11:52:19 -0500
Subject: [Mailman-Users] Error/crash in admindb - 1.0b11
Message-ID: <3729DFC3.C3CF4F6E@uiuc.edu>

Hi-

This crash happened when going to http://host/mailman/admindb.  I have
not been able to reproduce it since then.  The error log is attached. 
The system is running Slackware 3.5, with Python 1.5.1.  Any suggestions
or patches?

Also, is there a way that I can turn off the extraneous debugging
information sent to the WWW client, and have it just be put in the log? 
The fact that it dumps so much information about the system could be
seen as a security risk.

Thanks.

-Brian Ryner
bryner at uiuc.edu
-------------- next part --------------
Apr 29 22:33:41 1999 admin: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
admin: [----- Mailman Version: 1.0b11 -----]
admin: [----- Traceback ------]
admin: Traceback (innermost last):
admin:   File "/admin/mailman/scripts/driver", line 112, in run_main
admin:     main()
admin:   File "/admin/mailman/Mailman/Cgi/admindb.py", line 77, in main
admin:     doc.AddItem(eader(2, "Invalid options to CGI script."))
admin: NameError: eader
admin: [----- Environment Variables -----]
admin: 	DOCUMENT_ROOT: /files/admin/httpd/htdocs
admin: 	HTTP_ACCEPT_ENCODING: gzip, deflate
admin: 	SERVER_PORT: 80
admin: 	PATH_TRANSLATED: /files/admin/httpd/htdocs/
admin: 	URL_COUNT: 6
admin: 	GATEWAY_INTERFACE: CGI/1.1
admin: 	HTTP_ACCEPT_LANGUAGE: en-us
admin: 	HTTP_PROXY_CONNECTION: Keep-Alive
admin: 	REMOTE_ADDR: xxx.yyy.zzz.xxx
admin: 	SERVER_NAME: www.xxxxxxx.org
admin: 	URL_COUNT_DB: /files/admin/httpd/logs/counters/ALL
admin: 	HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 4.01; Windows 95)
admin: 	HTTP_ACCEPT: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/msword, application/vnd.ms-powerpoint, */*
admin: 	REQUEST_URI: /mailman/admindb/
admin: 	PATH: /usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin
admin: 	QUERY_STRING: 
admin: 	SCRIPT_FILENAME: /files/admin/mailman/cgi-bin/admindb
admin: 	PATH_INFO: /
admin: 	HTTP_HOST: www.xxxxxxx.org
admin: 	REQUEST_METHOD: GET
admin: 	SERVER_SIGNATURE: 
admin: 	URL_COUNT_RESET: Thursday, 29-Apr-99 00:19:13 CDT
admin: 	SCRIPT_NAME: /mailman/admindb
admin: 	SERVER_ADMIN: admin at xxxxxx.org
admin: 	SERVER_SOFTWARE: Apache/1.3.4 (Unix)
admin: 	PYTHONPATH: /admin/mailman
admin: 	SERVER_PROTOCOL: HTTP/1.0
admin: 	REMOTE_PORT: 6208


From bryner at uiuc.edu  Fri Apr 30 19:55:15 1999
From: bryner at uiuc.edu (Brian Ryner)
Date: Fri, 30 Apr 1999 12:55:15 -0500
Subject: [Mailman-Users] Error/crash in admindb - 1.0b11
Message-ID: <3729EE83.5DA4F401@uiuc.edu>

Is that line (admindb.py, line 77) supposed to say Header instead of
eader ?

> Apr 29 22:33:41 1999 admin: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> admin: [----- Mailman Version: 1.0b11 -----]
> admin: [----- Traceback ------]
> admin: Traceback (innermost last):
> admin:   File "/admin/mailman/scripts/driver", line 112, in run_main
> admin:     main()
> admin:   File "/admin/mailman/Mailman/Cgi/admindb.py", line 77, in main
> admin:     doc.AddItem(eader(2, "Invalid options to CGI script."))
> admin: NameError: eader



From davroc at hplb.hpl.hp.com  Fri Apr 30 19:56:45 1999
From: davroc at hplb.hpl.hp.com (David Rocher)
Date: Fri, 30 Apr 1999 18:56:45 +0100
Subject: [Mailman-Users] Re: deleting archives
In-Reply-To: <3.0.2.32.19990430114438.00b401b8@iris.vulcanind.com>; from Kevin Lee on Fri, Apr 30, 1999 at 11:44:38AM -0500
References: <3.0.2.32.19990430114438.00b401b8@iris.vulcanind.com>
Message-ID: <19990430185644.A4019@rocher-d-1.hpl.hp.com>

On Fri, Apr 30, 1999 at 11:44:38AM -0500, Kevin Lee wrote:
> I can not find anything in the FAQs or archives that addresses deleting and
> restarting the archives.  Any suggestions?

to clean the archives of <listname>:
	cd $prefix/archives/private
	rm -rf <listname>/*
	rm <listname>.mbox/*

<listname>/index.html isn't created until a new message is sent to the list.

 David.



From joseph at connectcorp.net  Sat Apr 17 02:50:08 1999
From: joseph at connectcorp.net (Joseph Leaver)
Date: Fri, 16 Apr 1999 17:50:08 -0700
Subject: [Mailman-Users] Disabling passwords altogether.
Message-ID: <006d01be886c$3e5d4ce0$0200a8c0@connectcorp.net>

Hi! I run a joke-a-day list and have received several complaints about the
need to use passwords to subscribe and unsubscribe. Is there any way to
disable this feature?

Thanks,

Joe