Re: [Mailman-Users] How to make a list read-only ?

2008-04-25 Thread lists . mailman-users
Hallo Mark and Joerg,

Op donderdag 24 april 2008 schreef Mark Sapiro aan
[EMAIL PROTECTED]:

 MS This is desdribed at
 MS www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.011.htp.

Many thanks to both of you.

Groeten,

   Hans.

jdh punt beekhuizen bij duinheks punt nl

--- GoldED+/LNX 1.1.5/080305
 * Origin: The Wizard is using MBSE/Linux (2:280/1018)
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


[Mailman-Users] How to import a list of members?

2008-04-25 Thread lists . mailman-users
Hallo mailman-users,

Is it possible to import an ASCII list of members for a
mailing list?
If yes, how to do it?

Groeten,

   Hans.

jdh punt beekhuizen bij duinheks punt nl

--- GoldED+/LNX 1.1.5/080305
 * Origin: The Wizard is using MBSE/Linux (2:280/1018)
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] How to import a list of members?

2008-04-25 Thread lists . mailman-users
Hallo Zbigniew,

Op vrijdag 25 april 2008 schreef Zbigniew Szalbot aan
[EMAIL PROTECTED]:

  Is it possible to import an ASCII list of members for a
  mailing list?
 ZS Take a look at bin/add_members script
 ZS Run it with --help to see what options there are

Lovely! That seems to de exactly what I want. Thank tou very
much for your help.

Groeten,

   Hans.

jdh punt beekhuizen bij duinheks punt nl

--- GoldED+/LNX 1.1.5/080305
 * Origin: The Wizard is using MBSE/Linux (2:280/1018)
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] How to import a list of members?

2008-04-25 Thread Lynn, Michael (AE)
Not sure if this will help anyone - but I had a requirement to enable
remote subscription from a command line.  I wrapped a call to cURL for
this.

---8---
#!/bin/bash
# mlynn 03/28/2008
# Wrap a call to curl to enable subscription to a mailman list
#
VERSION=0.1
MAILMANURL=http://lists.yourserver.com/mailman/subscribe;
PROGRAM=`basename $0`

function ERROR
# Spew the wrongness
{
echo Error: Code $1
echo ${2}?
exit $1
}

function SYNTAX
#
# Tell the people how you communicate
#
{
echo SYNTAX:
echo $PROGRAM $VERSION
echo   $PROGRAM [[email] [firstname] [lastname] [password]
[listname]]
echo   This handy script will wrap a call to cURL for the
purpose of subscribing
echo   a user to a mailman list.  If you fail to provide
optional arguments, you
echo   will be prompted to enter them at the command line.
echo
}

function CHECKCURL
#
# Check for commands you depend upon
#
{
CURL=`which curl`
if [ $? -ne 0 ]; then
ERROR 1 the command curl is missing from the system
fi;

}

function GETARGS
#
# Get the arguments - duh.
#
{
if [ $1 = -h -o $1 = --h ]; then
SYNTAX
exit 0
fi
if [ -z $1 ]; then
{
echo Enter email for user to be subscribed: 
read EMAIL
if [ -z $EMAIL ]; then
ERROR 30 You must enter a valid email address.
fi
}
else
EMAIL=$1
fi
if [ -z $2 ]; then
{
echo Enter the first name of the person to be
subscribed: 
read FIRSTNAME
if [ -z $FIRSTNAME ]; then
ERROR 30 You the first name of the subscibee.
fi
}
else
FIRSTNAME=$2
fi
if [ -z $3 ]; then
{
echo Enter the last name of the person to be
subscribed: 
read LASTNAME
if [ -z $LASTNAME ]; then
ERROR 30 You the last name of the subscibee.
fi
}
else
LASTNAME=$3
fi
if [ -z $4 ]; then
{
echo Enter the list access password for this user: 
read PW
if [ -z $PW ]; then
ERROR 30 You must enter a password for $EMAIL.
fi
}
else
PW=$4
fi
if [ -z $5 ]; then
{
echo Enter the list name to subscribe $EMAIL to: 
read LIST
if [ -z $LIST ]; then
ERROR 30 You must enter a valid listname.
fi
}
else
LIST=$5
fi
}

function DOCURL
# Build the cURL call
{

# urlencode the email '@'
UEMAIL=`echo $EMAIL | sed s/\@/\%40/g`
CMD=curl -s
$MAILMANURL/${LIST}?email=${UEMAIL}fullname=$FIRSTNAME%20$LASTNAMEpw=$
PWpw-conf=$PWdigest=0email-button=Submit
OUT=`${CMD}`
if `echo ${OUT} | grep -i no such list` ; then
{
ERROR 30 List $LIST not found.  Please check
and try again.
}
else
{
echo List subscription for the following user
appears to have worked.
echo Email: $EMAIL
echo Full Name: $FIRSTNAME $LASTNAME
echo The user should recieve an email
requesting confirmation for this subscription.
exit 0
}
fi

}


CHECKCURL
GETARGS $1 $2 $3 $4 $5
DOCURL
---8

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of [EMAIL PROTECTED]
Sent: Friday, April 25, 2008 4:47 AM
To: mailman-users
Subject: Re: [Mailman-Users] How to import a list of members?


Hallo Zbigniew,

Op vrijdag 25 april 2008 schreef Zbigniew Szalbot aan
[EMAIL PROTECTED]:

  Is it possible to import an ASCII list of members for a
  mailing list?
 ZS Take a look at bin/add_members script
 ZS Run it with --help to see what options there are

Lovely! That seems to de exactly what I want. Thank tou very
much for your help.

Groeten,

   Hans.

jdh punt beekhuizen bij duinheks punt nl

--- GoldED+/LNX 1.1.5/080305
 * Origin: The Wizard is using MBSE/Linux (2:280/1018)
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives:
http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/michael_lynn%40ml.c
om

Security Policy:

[Mailman-Users] Is it OK to unshunt bad messages?

2008-04-25 Thread Sebastian Hagedorn

Hi,

I just noticed a message in the bad directory. I looked at it with 
show_qfiles and it looked harmless. Probably it was broken WRT its MIME 
encoding, but it wasn't a virus or anything. On a whim I ran unshunt on the 
bad directory and the message was then delivered to the list.


Basically I'm curious why Mailman didn't consider the message bad that 
time around. Is unshunt-processing somehow different from normal processing?


Thank, Sebastian
--
.:.Sebastian Hagedorn - RZKR-R1 (Gebäude 52), Zimmer 18.:.
Zentrum für angewandte Informatik - Universitätsweiter Service RRZK
.:.Universität zu Köln / Cologne University - ✆ +49-221-478-5587.:.
  .:.:.:.Skype: shagedorn.:.:.:.

pgpgA5a8Lh3DR.pgp
Description: PGP signature
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp

[Mailman-Users] IOError reading list extension Message

2008-04-25 Thread Barry Finkel
I am running a home-built Mailman 2.1.9 Ubuntu package with the latest
security patch.  I see messages in the error log like this one:

 Apr 25 08:00:05 2008 (27326) IOError reading list extension:
   [Errno 20] Not a directory:
   '/var/lib/mailman/lists/append_description.newdescription/extend.py'

I do not see any

 extend.py

in the directory in which I build Mailman.  I see an archived posting

 http://www.mail-archive.com/mailman-users@python.org/msg37089.html

that has a similar complaint from 16 Feb 2006, but the response from
Mark Sapiro to that posting does not seem to fit my situation.
--
Barry S. Finkel
Computing and Information Systems Division
Argonne National Laboratory  Phone:+1 (630) 252-7277
9700 South Cass Avenue   Facsimile:+1 (630) 252-4601
Building 222, Room D209  Internet: [EMAIL PROTECTED]
Argonne, IL   60439-4828 IBMMAIL:  I1004994

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


[Mailman-Users] checksums

2008-04-25 Thread Melinda Gilmore
I trying to find out if mailman uses the md5 checksum or this has to be set
up with the installation.  Any help on this would be greatly appreciated.  I
have not been able to find it so far.  


--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] unparseable message

2008-04-25 Thread Barry Finkel
Mark Sapiro replied to one of my postings:

Mailman (actually the Python email package) doesn,t like the fact that
there is no intervening empty line between the terminating boundary of
the message/rfc822 part and the terminating boundary of the outer
message.

Quoting from section 5.1.1 of RFC 2045

  The boundary may be followed by zero or more characters of linear
  whitespace. It is then terminated by either another CRLF and the
  header fields for the next part, or by two CRLFs, in which case
  there are no header fields for the next part.

For the record (i.e., anyone who looks in the archives), the RFC is
2046.  This DSN message is being generated by our Ironport anti-spam
appliance, so we will report this to Ironport.
--
Barry S. Finkel
Computing and Information Systems Division
Argonne National Laboratory  Phone:+1 (630) 252-7277
9700 South Cass Avenue   Facsimile:+1 (630) 252-4601
Building 222, Room D209  Internet: [EMAIL PROTECTED]
Argonne, IL   60439-4828 IBMMAIL:  I1004994

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] IOError reading list extension Message

2008-04-25 Thread Mark Sapiro
Barry Finkel wrote:

I am running a home-built Mailman 2.1.9 Ubuntu package with the latest
security patch.  I see messages in the error log like this one:

 Apr 25 08:00:05 2008 (27326) IOError reading list extension:
   [Errno 20] Not a directory:
   '/var/lib/mailman/lists/append_description.newdescription/extend.py'

I do not see any

 extend.py

in the directory in which I build Mailman.


Is 'append_description.newdescription' the name of a list?

This error occurs when Mailman attempts to read (actually execute) the
optional extend.py module for a list during the instantiation of that
list, and it gets an error exception other than 'doesn't exist'.

From the actual error, it seems that
/var/lib/mailman/lists/append_description.newdescription is not a
directory. Is it a file?

There should be nothing in /var/lib/mailman/lists/ except
subdirectories corresponding to lists, but Mailman shouldn't really
care.

It's hard to tell without more information, but it looks like this
comes from cron/checkdbs which trys to instantiate every list. It
should only be trying to instantiate lists whose names are the names
of subdirectories of /var/lib/mailman/lists/ and which subdirectories
in turn contain a config.pck file, but something might be wrong with
Mailman.Utils.list_names() (or Mailman.Site.get_listnames() or
Mailman.Utils.list_exists() called by list_names()) that causes it to
return the bogus name.

-- 
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


[Mailman-Users] passwords

2008-04-25 Thread Melinda Gilmore
Does mailman have restrictions for passwords.   Like a number or cap needs
in the passwords.  I am not finding anything on that.  I know in my
experience it just lets me put in anything for a password, wether it be for
owner or user?

Melinda Gilmore
Systems Engineer
The Ohio State University
Enterprise Messaging/OIT
614-292-4953

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] How to import a list of members?

2008-04-25 Thread Michael Kubler
Wow, that beats my lazy way of doing it, which is simply a cron job 
which uses the *add_members* function to import a list of email 
addresses from a text file, that I have a PHP script 
http://www.syjmovie.com saving the addresses to.


Michael Kubler
*G*rey *P*hoenix *P*roductions http://www.greyphoenix.biz



Lynn, Michael (AE) wrote:

Not sure if this will help anyone - but I had a requirement to enable
remote subscription from a command line.  I wrapped a call to cURL for
this.

---8---
#!/bin/bash
# mlynn 03/28/2008
# Wrap a call to curl to enable subscription to a mailman list
#
VERSION=0.1
MAILMANURL=http://lists.yourserver.com/mailman/subscribe;
PROGRAM=`basename $0`

function ERROR
# Spew the wrongness
{
echo Error: Code $1
echo ${2}?
exit $1
}

function SYNTAX
#
# Tell the people how you communicate
#
{
echo SYNTAX:
echo $PROGRAM $VERSION
echo   $PROGRAM [[email] [firstname] [lastname] [password]
[listname]]
echo   This handy script will wrap a call to cURL for the
purpose of subscribing
echo   a user to a mailman list.  If you fail to provide
optional arguments, you
echo   will be prompted to enter them at the command line.
echo
}

function CHECKCURL
#
# Check for commands you depend upon
#
{
CURL=`which curl`
if [ $? -ne 0 ]; then
ERROR 1 the command curl is missing from the system
fi;

}

function GETARGS
#
# Get the arguments - duh.
#
{
if [ $1 = -h -o $1 = --h ]; then
SYNTAX
exit 0
fi
if [ -z $1 ]; then
{
echo Enter email for user to be subscribed: 
read EMAIL
if [ -z $EMAIL ]; then
ERROR 30 You must enter a valid email address.
fi
}
else
EMAIL=$1
fi
if [ -z $2 ]; then
{
echo Enter the first name of the person to be
subscribed: 
read FIRSTNAME
if [ -z $FIRSTNAME ]; then
ERROR 30 You the first name of the subscibee.
fi
}
else
FIRSTNAME=$2
fi
if [ -z $3 ]; then
{
echo Enter the last name of the person to be
subscribed: 
read LASTNAME
if [ -z $LASTNAME ]; then
ERROR 30 You the last name of the subscibee.
fi
}
else
LASTNAME=$3
fi
if [ -z $4 ]; then
{
echo Enter the list access password for this user: 
read PW
if [ -z $PW ]; then
ERROR 30 You must enter a password for $EMAIL.
fi
}
else
PW=$4
fi
if [ -z $5 ]; then
{
echo Enter the list name to subscribe $EMAIL to: 
read LIST
if [ -z $LIST ]; then
ERROR 30 You must enter a valid listname.
fi
}
else
LIST=$5
fi
}

function DOCURL
# Build the cURL call
{

# urlencode the email '@'
UEMAIL=`echo $EMAIL | sed s/\@/\%40/g`
CMD=curl -s
$MAILMANURL/${LIST}?email=${UEMAIL}fullname=$FIRSTNAME%20$LASTNAMEpw=$
PWpw-conf=$PWdigest=0email-button=Submit
OUT=`${CMD}`
if `echo ${OUT} | grep -i no such list` ; then
{
ERROR 30 List $LIST not found.  Please check
and try again.
}
else
{
echo List subscription for the following user
appears to have worked.
echo Email: $EMAIL
echo Full Name: $FIRSTNAME $LASTNAME
echo The user should recieve an email
requesting confirmation for this subscription.
exit 0
}
fi

}


CHECKCURL
GETARGS $1 $2 $3 $4 $5
DOCURL
---8

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] checksums

2008-04-25 Thread Mark Sapiro
Melinda Gilmore wrote:

I trying to find out if mailman uses the md5 checksum or this has to be set
up with the installation.  Any help on this would be greatly appreciated.  I
have not been able to find it so far.  


I'm not sure what you're asking, but old versions of Mailman used to
use 'crypt' or 'md5' to encrypt list admin and moderator passwords and
site and list creator passwords, but it currently uses 'sha'. It will
still try 'crypt' and 'md5' on the supplied password if 'sha' doesn't
match, and if it gets a 'crypt' or 'md5' match, it will migrate the
encrypted password to 'sha'.

In order to compute 'crypt', 'md5' and 'sha' checksums, it uses the
builtin Python modules.

-- 
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] passwords

2008-04-25 Thread Mark Sapiro
Melinda Gilmore wrote:

Does mailman have restrictions for passwords.   Like a number or cap needs
in the passwords.


No.

-- 
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] unparseable message

2008-04-25 Thread Mark Sapiro
Barry Finkel wrote:

Mark Sapiro replied to one of my postings:

Quoting from section 5.1.1 of RFC 2045

  The boundary may be followed by zero or more characters of linear
  whitespace. It is then terminated by either another CRLF and the
  header fields for the next part, or by two CRLFs, in which case
  there are no header fields for the next part.

For the record (i.e., anyone who looks in the archives), the RFC is
2046.


Thanks for the correction. I had looked at both, and wrote the wrong
number.

-- 
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] checksums

2008-04-25 Thread Mark Sapiro
Mark Sapiro wrote:

Melinda Gilmore wrote:

I trying to find out if mailman uses the md5 checksum or this has to be set
up with the installation.  Any help on this would be greatly appreciated.  I
have not been able to find it so far.  


I'm not sure what you're asking, ...


It occurs to me that what you are asking is if Mailman stores passwords
in encrypted form.

The answer is yes (but using sha, not md5) for site, list creator, list
admin and list moderator passwords.

The answer is no for list member passwords in current Mailman, but this
will change in Mailman 3.0.

It would be complicated to change Mailman 2.1 to encrypt list member
passwords because the periodic and on-demand password reminder would
have to be replaced with an on-demand password reset or something
similar.

-- 
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] checksums

2008-04-25 Thread Barry Warsaw

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Apr 25, 2008, at 11:45 AM, Mark Sapiro wrote:


It would be complicated to change Mailman 2.1 to encrypt list member
passwords because the periodic and on-demand password reminder would
have to be replaced with an on-demand password reset or something
similar.


Although in 2.2 we should kill off monthly password reminders,  
implementing a password reset instead, and encrypt user passwords  
too.  In 3.0 #1 and #3 is done, but not #2.


- -Barry

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkgR/dEACgkQ2YZpQepbvXF1MACaAkDoEejI+z65u9IpsZRKn3mp
eyAAniG+mkxOcQv9NNwseRkZmctPP4du
=HiXZ
-END PGP SIGNATURE-
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] Is it OK to unshunt bad messages?

2008-04-25 Thread Mark Sapiro

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Sebastian Hagedorn wrote:
|
| I just noticed a message in the bad directory. I looked at it with
| show_qfiles and it looked harmless. Probably it was broken WRT its MIME
| encoding, but it wasn't a virus or anything. On a whim I ran unshunt on
| the bad directory and the message was then delivered to the list.
|
| Basically I'm curious why Mailman didn't consider the message bad that
| time around. Is unshunt-processing somehow different from normal
| processing?


I'm guessing that you are running Mailman 2.1.10 with the patch from
http://mail.python.org/pipermail/mailman-users/2008-April/061360.html,
since there's little else these days that would put anything in the
'bad' queue. Did the file have a .psv extension?

You should really look in the 'error' log to see the message associated
with preserving the entry. It may have been an actual unparseable
message due to defective MIME structure, or some possibly transient
issue. In the first case, I'd expect the same error to occur upon
unshunting, but not necessarily in the second case. There is nothing
really in bin/unshunt that would make it succeed without correcting the
underlying problem.

The main problem with unshunting a message from the 'bad' queue (other
than having to change the extension from .psv to .pck or .bak) is that
true shunted messages have an item in the metadata indicating the
original queue. Preserved messages in the 'bad' queue don't have this,
so they will be unshunted to the 'in' queue by default, which may not be
correct - e.g. they may have come from the bounce queue.

- --
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)

iD8DBQFIEgT4VVuXXpU7hpMRAlyUAJ44GgIaiMHIXj8z+xtNrIWgQ5e1nACeKaCw
UzVivGCzf+Al9HMy6vVC7EA=
=x8BJ
-END PGP SIGNATURE-
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] Is it OK to unshunt bad messages?

2008-04-25 Thread Mark Sapiro

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Sebastian Hagedorn wrote:
| --On 25. April 2008 10:16:27 -0700 Mark Sapiro [EMAIL PROTECTED] wrote:
|
| Sebastian Hagedorn wrote:
| |
| | No, it was a .pck file. I found this entry in the vette log:
| |
| | (3438) Message discarded, msgid: [EMAIL PROTECTED]
|
|
| This should have nothing to do with anything in the 'bad' queue.
|
| But it was definitely that message!


I have been overlooking something. I think it was the same message in
the 'bad' queue and in the vette log entry. This happens when the list's
Content filtering - filter_action is Preserve and the message is
discarded because content filtering removed all its content.

If it was accepted when unshunted, the list's content filtering settings
must have been changed in the interim.


| This
| message is logged when a handler decides to discard an incoming post,
| e.g. a post from a non-member in discard_these_nonmembers or any other
| condition with a discard action.
|
| That's what I thought initially, but how did it end up in bad then?
| Could it be caused by this patch to 2.1.9 that I applied on March 8:
|
|syslog('error', 'Ignoring unparseable message:
%s',filebase)
| + self._switchboard.finish(filebase)


This patch doesn't put anything in 'bad'. In fact, without this patch,
the original unparseable queue entry is left in the original queue with
a .bak extension. The patch just removes the .bak file unless you also
have patches to the finish() method in Mailman/Queue/Switchboard.py.


| I see this line in error shortly after the message that I found in
| bad arrived:
|
| Mar 29 17:01:05 2008 (3438) Ignoring unparseable message:
| 1206806465.417665+d798425535212058c480aebf7900add235ac4cb9
| Mar 29 17:01:05 2008 (3438) Ignoring unparseable message:
| 1206806465.4255731+c874adc58f17010096988e4e388e31260a56677a
|
| But how can I tell what messages those really are?


Those are two separate messages/queue entries. In 2.1.9 with the patch
above, you can't tell anything, because the queue entries are gone. In
2.1.10 as released last Monday, the error log messages would have been
for example,

'Skipping and preserving unparseable message:
1206806465.4255731+c874adc58f17010096988e4e388e31260a56677a'

and the queue entry would have been saved as
1206806465.4255731+c874adc58f17010096988e4e388e31260a56677a.psv in
qfiles/shunt.

The patch I posted at
http://mail.python.org/pipermail/mailman-users/2008-April/061360.html
makes this conditional on QRUNNER_SAVE_BAD_MESSAGES and saves the entry
in qfiles/bad instead.



| Changing long standing log messages is
| not something to be done lightly as it potentially breaks peoples log
| analysis tools.
|
| I can see that, but still I'd put it on my wishlist for 2.2 or 3.0,
| because it's happened a few times that list admins complained about
| lost messages. It would've been much easier to see that mail to those
| lists had been discarded if the list name had been logged. The way it is
| now we first had to look at the MTA's log and then search the error log
| for the message-id. And when a single message is sent to more than one
| list, that still doesn't necessarily tell you the whole story ...


I understand. There are a number of log messages that could benefit from
additional information. I've put it on my 2.2 list to review these.

- --
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)

iD8DBQFIEiCcVVuXXpU7hpMRAlIVAKCiG+Rp647VLsAQYq13n23dDw4VfACg9t2V
dOJDWON4B/RdHQ4ZamXqXT8=
=9Qci
-END PGP SIGNATURE-
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] IOError reading list extension Message

2008-04-25 Thread Barry Finkel
Barry Finkel wrote:
Since these three files are not Mailman lists,
which Mailman process that was treating them as list names is
not important.

Mark Sapiro replied:
It's important to me. I would like to understand why the name of a file
in the lists/ directory is being returned (apparently by
Utils.list_lists()) as a list name, because this isn't supposed to
happen (and I can't make it happen in my test installation).

katydid# ls -al /var/lib/mailman/lists/ | grep -v ^d
total 992
katydid# 

Once I removed those files, there are no other regular files in the
directory, only sub-directories.  These messages are appearing each
hour at

 hh:00:03

and also at

 07:20:03

I have a Mailman cron that runs each morning at 07:20

 /usr/local/cron-scripts/mailman_bounce_report.exec

to produce a summary of all subscriptions with a non-zero bounce score;
it essentially does

 #!/bin/csh
 foreach list (`ls /var/lib/mailman/lists`)
  /usr/sbin/withlist -r get_bounce_info $list \
 mailman_bounce_report.tmpout
 end

where

 get_bounce_info

came from your repository

 http://veenet.value.net/~msapiro/scripts/get_bounce_info.py

In that script I assume that everything in the lists subdirectory
is the name of a Mailman list; I do not check for a regular file,
and I am not sure if I really need to code such a check.

I have another cron that runs every hour, on the hour, that produces a
flat file containing records

 listname e-mail address

so I have a list of all of the subscriptions.  That script

 /usr/local/cron-scripts/mailman_who.exec

essentially does:

 #!/bin/csh
 foreach list (`ls /var/lib/mailman/lists`)
  /usr/lib/mailman/bin/list_members -o $destdir/$list $list
 end

I also do not have a check in this script.  I am using 

 foreach list (`ls /var/lib/mailman/lists`)

and not

 Utils.list_lists())

to get a list of lists.  I assume that the Utils.list_lists()) code
has the check that I do not have in foreach list.
--
Barry S. Finkel
Computing and Information Systems Division
Argonne National Laboratory  Phone:+1 (630) 252-7277
9700 South Cass Avenue   Facsimile:+1 (630) 252-4601
Building 222, Room D209  Internet: [EMAIL PROTECTED]
Argonne, IL   60439-4828 IBMMAIL:  I1004994

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


[Mailman-Users] 'NoneType' object has no attribute 'lower'

2008-04-25 Thread Zbigniew Szalbot

Hello,

I have installed mailman 2.1.9.5 and now upgraded to 2.1.10 and see the 
following in mailman's error log.


Apr 25 20:02:49 2008 (24138) SHUNTING: 
1209146569.0795979+80ec39567f7efbc1306687a6c84ed28bfccfc400
Apr 25 20:04:36 2008 (24138) Uncaught runner exception: 'NoneType' 
object has no attribute 'lower'

Apr 25 20:04:36 2008 (24138) Traceback (most recent call last):
  File /usr/local/mailman/Mailman/Queue/Runner.py, line 114, in _oneloop
self._onefile(msg, msgdata)
  File /usr/local/mailman/Mailman/Queue/Runner.py, line 185, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
  File /usr/local/mailman/Mailman/Queue/CommandRunner.py, line 241, 
in _dispose

res.do_command('join')
  File /usr/local/mailman/Mailman/Queue/CommandRunner.py, line 139, 
in do_command

return handler.process(self, args)
  File /usr/local/mailman/Mailman/Commands/cmd_subscribe.py, line 74, 
in process

if digest is None and password.lower() in ('digest', 'nodigest'):
AttributeError: 'NoneType' object has no attribute 'lower'

I will appreciate if you could help me deal with it. Thank you!


--
Zbigniew Szalbot
www.lc-words.com
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] 'NoneType' object has no attribute 'lower'

2008-04-25 Thread Brad Knowles

Zbigniew Szalbot wrote:

I have installed mailman 2.1.9.5 and now upgraded to 2.1.10 and see the 
following in mailman's error log.


Well, we've never shipped a version number 2.1.9.5, so that tells me you're 
probably using a binary packaged version provided by some other source. 
Maybe your OS vendor, maybe someone else.


However, since we don't know what they may have done to the code that they 
have packaged and shipped to you, we can't really tell you anything about 
how things may now act if you've applied some sort of patch or something 
from our code to try to bring you up to date.


If you want to completely de-install the old version and then re-install 
from our tarball, I would expect that should work, but I won't give you any 
guarantees.



Your first step for resolving all these problems should be to contact your 
vendor who provided the previous binary package version you were using, and 
get assistance from them.


--
Brad Knowles [EMAIL PROTECTED]
Member of the Python.org Postmaster Team,  Co-moderator of the
mailman-users and mailman-developers mailing lists
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] checksums

2008-04-25 Thread Melinda Gilmore
What I mean by Checksum is a message bounce like this.

he following message was not processed due to the following reasons:
- The body of the message has a checksum matching those messages already
processed.
 

-Original Message-
From: Mark Sapiro [mailto:[EMAIL PROTECTED] 
Sent: Friday, April 25, 2008 11:27 AM
To: Melinda Gilmore; mailman-users@python.org
Subject: Re: [Mailman-Users] checksums

Melinda Gilmore wrote:

I trying to find out if mailman uses the md5 checksum or this has to be 
set up with the installation.  Any help on this would be greatly 
appreciated.  I have not been able to find it so far.


I'm not sure what you're asking, but old versions of Mailman used to use
'crypt' or 'md5' to encrypt list admin and moderator passwords and site and
list creator passwords, but it currently uses 'sha'. It will still try
'crypt' and 'md5' on the supplied password if 'sha' doesn't match, and if it
gets a 'crypt' or 'md5' match, it will migrate the encrypted password to
'sha'.

In order to compute 'crypt', 'md5' and 'sha' checksums, it uses the builtin
Python modules.

-- 
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] Is it OK to unshunt bad messages?

2008-04-25 Thread Sebastian Hagedorn

--On 25. April 2008 11:19:08 -0700 Mark Sapiro [EMAIL PROTECTED] wrote:


| This should have nothing to do with anything in the 'bad' queue.
|
| But it was definitely that message!


I have been overlooking something. I think it was the same message in
the 'bad' queue and in the vette log entry. This happens when the list's
Content filtering - filter_action is Preserve and the message is
discarded because content filtering removed all its content.

If it was accepted when unshunted, the list's content filtering settings
must have been changed in the interim.


Thanks, that makes sense! The list does have content filtering and 
preserve as its filter_action.

--
.:.Sebastian Hagedorn - RZKR-R1 (Gebäude 52), Zimmer 18.:.
Zentrum für angewandte Informatik - Universitätsweiter Service RRZK
.:.Universität zu Köln / Cologne University - ✆ +49-221-478-5587.:.
  .:.:.:.Skype: shagedorn.:.:.:.

pgpQR3IEPtEHf.pgp
Description: PGP signature
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp

Re: [Mailman-Users] 'NoneType' object has no attribute 'lower'

2008-04-25 Thread Mark Sapiro
Zbigniew Szalbot wrote:

I have installed mailman 2.1.9.5 and now upgraded to 2.1.10 and see the 
following in mailman's error log.

Apr 25 20:02:49 2008 (24138) SHUNTING: 
1209146569.0795979+80ec39567f7efbc1306687a6c84ed28bfccfc400
Apr 25 20:04:36 2008 (24138) Uncaught runner exception: 'NoneType' 
object has no attribute 'lower'
Apr 25 20:04:36 2008 (24138) Traceback (most recent call last):
   File /usr/local/mailman/Mailman/Queue/Runner.py, line 114, in _oneloop
 self._onefile(msg, msgdata)
   File /usr/local/mailman/Mailman/Queue/Runner.py, line 185, in _onefile
 keepqueued = self._dispose(mlist, msg, msgdata)
   File /usr/local/mailman/Mailman/Queue/CommandRunner.py, line 241, 
in _dispose
 res.do_command('join')
   File /usr/local/mailman/Mailman/Queue/CommandRunner.py, line 139, 
in do_command
 return handler.process(self, args)
   File /usr/local/mailman/Mailman/Commands/cmd_subscribe.py, line 74, 
in process
 if digest is None and password.lower() in ('digest', 'nodigest'):
AttributeError: 'NoneType' object has no attribute 'lower'

I will appreciate if you could help me deal with it. Thank you!


A description of this issue along with the patch to fix it is at
http://mail.python.org/pipermail/mailman-users/2008-April/061381.html,
http://mail.python.org/pipermail/mailman-announce/2008-April/000111.html,
and
http://mail.python.org/pipermail/mailman-developers/2008-April/020162.html.

This is the major reason that there will be a 'patch' release soon.

-- 
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] checksums

2008-04-25 Thread Mark Sapiro
Melinda Gilmore wrote:

What I mean by Checksum is a message bounce like this.

he following message was not processed due to the following reasons:
- The body of the message has a checksum matching those messages already
processed.


Mailman doesn't do this. The only thing close is pipermail attempts to
avoid duplicate archive messages, but that's based on message-id, not
a checksum.

-- 
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] 'NoneType' object has no attribute 'lower'

2008-04-25 Thread Mark Sapiro
Mark Sapiro wrote:

Zbigniew Szalbot wrote:

I have installed mailman 2.1.9.5 and now upgraded to 2.1.10 and see the 
following in mailman's error log.

Apr 25 20:02:49 2008 (24138) SHUNTING: 
1209146569.0795979+80ec39567f7efbc1306687a6c84ed28bfccfc400
Apr 25 20:04:36 2008 (24138) Uncaught runner exception: 'NoneType' 
object has no attribute 'lower'
Apr 25 20:04:36 2008 (24138) Traceback (most recent call last):
   File /usr/local/mailman/Mailman/Queue/Runner.py, line 114, in _oneloop
 self._onefile(msg, msgdata)
   File /usr/local/mailman/Mailman/Queue/Runner.py, line 185, in _onefile
 keepqueued = self._dispose(mlist, msg, msgdata)
   File /usr/local/mailman/Mailman/Queue/CommandRunner.py, line 241, 
in _dispose
 res.do_command('join')
   File /usr/local/mailman/Mailman/Queue/CommandRunner.py, line 139, 
in do_command
 return handler.process(self, args)
   File /usr/local/mailman/Mailman/Commands/cmd_subscribe.py, line 74, 
in process
 if digest is None and password.lower() in ('digest', 'nodigest'):
AttributeError: 'NoneType' object has no attribute 'lower'

I will appreciate if you could help me deal with it. Thank you!


A description of this issue along with the patch to fix it is at
http://mail.python.org/pipermail/mailman-users/2008-April/061381.html,
http://mail.python.org/pipermail/mailman-announce/2008-April/000111.html,
and
http://mail.python.org/pipermail/mailman-developers/2008-April/020162.html.

This is the major reason that there will be a 'patch' release soon.


One more thing. You should apply the patch and restart Mailman and then
use bin/unshunt to requeue the shunted messages because they are email
subscribe requests you probably don't want to loose.


-- 
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] checksums

2008-04-25 Thread Brad Knowles

Melinda Gilmore wrote:


What I mean by Checksum is a message bounce like this.

he following message was not processed due to the following reasons:
- The body of the message has a checksum matching those messages already
processed.


This is an error from Listserv (see http://8help.osu.edu/33266.html). 
This has nothing to do with Mailman.


--
Brad Knowles [EMAIL PROTECTED]
Member of the Python.org Postmaster Team,  Co-moderator of the
mailman-users and mailman-developers mailing lists
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] IOError reading list extension Message

2008-04-25 Thread Mark Sapiro
Barry Finkel wrote:

[...]

 #!/bin/csh
 foreach list (`ls /var/lib/mailman/lists`)
  /usr/lib/mailman/bin/list_members -o $destdir/$list $list
 end

I also do not have a check in this script.  I am using 

 foreach list (`ls /var/lib/mailman/lists`)

and not

 Utils.list_lists())

to get a list of lists.  I assume that the Utils.list_lists()) code
has the check that I do not have in foreach list.


Thanks for the info. It appears I erroneously assumed from the 08:00:03
timestamp in your OP that it was cron/checkdbs, but it now seems it is
all from your scripts which do not check that the names in
`ls /var/lib/mailman/lists` are all valid lists.

If you would use `/usr/lib/mailman/bin/list_lists -b` instead of
`ls /var/lib/mailman/lists`, you would avoid this problem.

Your code is OK as long as all the names in `ls /var/lib/mailman/lists`
are in fact lists, but it fails when this isn't true.

And yes, the Utils.list_lists() function only returns the names of
directories that contain a config.pck or config.db file.

So, bottom line, use `bin/list_lists -b` instead of `ls lists` to get
the list names, and you won't need to worry about whether or not a
name is a list.

-- 
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


[Mailman-Users] Mailman hosted on 1and1?

2008-04-25 Thread Eric Snyder
We have our corporate domain hosted on 1and1.com.  Can we install mailman on
the 1and1 environment?  Anyone already doing this?


-- 

===
Eric Snyder
Pres/CEO; Snyder Thorn Enterprises, Inc.
(613) 688-1570; [EMAIL PROTECTED]
www.SnyderThorn.com
===
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] Mailman hosted on 1and1?

2008-04-25 Thread Brad Knowles

Eric Snyder wrote:


We have our corporate domain hosted on 1and1.com.  Can we install mailman on
the 1and1 environment?  Anyone already doing this?


Do you have full root access on the box?  Do you know if they limit your 
outbound port 25 access, or place any other restrictions on you?


Those will be the kinds of questions you need to have answers to.

--
Brad Knowles [EMAIL PROTECTED]
Member of the Python.org Postmaster Team,  Co-moderator of the
mailman-users and mailman-developers mailing lists
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp