[Mailman-Users] bin/upgrade has been broken since 2.1.5 (or possibly longer)

[Knut Auvor Grythe]

The _UpdateRecords function in ListAdmin.py is completely broken, and
has been since 2.1.5. There is a bugreport filed in 2004 at
https://bugs.launchpad.net/mailman/+bug/266106, and a patch for the
issue was included in march 2005. It seems the issue has gone unnoticed,
though. Possibly because the title of the bug report is "Tend to Pending
Moderator Requests breaks on a few lists", which doesn't seem all that
bad.

The _UpdateRecords function in ListAdmin.py reads the two-element tuple
(op, info). It then checks if info has all necessary fields. If it has,
nothing is done. If info _doesn't_ have all necessary fields (e.g. comes
from an old version of mailman), the missing fields are added and info
saved back. Notice how "info" is different from "(op, info)".

This causes all subsequent access to subscription and held message
records to fail with a ValueError, since an info typle is not 2 elements
long.

I think it would be very nice to have this fixed in 2.1.11. But even if
that doesn't happen I thought I should notify people about the problem,
so they know what to do if their upgrade causes trouble.

-- 
Knut Auvor Grythe
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

[Mailman-Users] Emails sent directly to "bounce" address

[J.R. Constance]

I have one list that has suddenly been receiving an increase in  
bounces, and in looking at the bounce emails they appear to be spam  
sent directly to the bounce address (ex. list1- 
[EMAIL PROTECTED]). From what I can see this email (with  
attachments, sometimes virus/trojans) then gets sent as a bounce to  
the admins. The admin for this list is receiving all of these emails,  
with attachments, and is getting concerned about the volume of  
infected attachments she's getting.


Is there any way to filter these emails sent to the bounce address so  
that if they are spam they just get discarded. I do have filters set  
up for emails sent to the list that filter them out, but since these  
don't actually go to the list, but to the bounce address, they don't  
appear to be run through that filter system.


Any recommendations on what to do about this, short of creating a new  
list, would be appreciated.


An example of the header from an email is pasted below:

Received: (qmail 3486 invoked from network); 18 Sep 2008 14:08:58  
-
Received: from unknown (HELO pre- 
smtp36-01.prod.mesa1.secureserver.net) ([10.0.19.136])

 (envelope-sender <[EMAIL PROTECTED]>)
 by smtp30.prod.mesa1.secureserver.net (qmail-1.03) with SMTP
 for <[EMAIL PROTECTED]>; 18 Sep 2008 14:08:58 -
Received: (qmail 10030 invoked from network); 18 Sep 2008 14:08:58  
-

Received: from frodo.clshost.com ([72.249.28.134])
 (envelope-sender <[EMAIL PROTECTED]>)
 by pre-smtp36-01.prod.mesa1.secureserver.net (qmail- 
ldap-1.03) with SMTP

 for <[EMAIL PROTECTED]>; 18 Sep 2008 14:08:58 -
Received: from localhost ([127.0.0.1] helo=frodo.clshost.com)
by frodo.clshost.com with esmtp (Exim 4.69)
(envelope-from <[EMAIL PROTECTED]>)
id 1KgKBj-0004gT-CX
for [EMAIL PROTECTED]; Thu, 18 Sep 2008 08:08:56 -0600
Subject: Uncaught bounce notification
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===1010536534=="
Message-ID: <[EMAIL PROTECTED] 
>

Date: Thu, 18 Sep 2008 08:08:47 -0600
Precedence: bulk
X-BeenThere: [EMAIL PROTECTED]
X-Mailman-Version: 2.1.9.cp2
List-Id: 
X-List-Administrivia: yes
Sender: [EMAIL PROTECTED]
Errors-To: [EMAIL PROTECTED]
X-AntiAbuse: This header was added to track abuse, please include it  
with any abuse report

X-AntiAbuse: Primary Hostname - frodo.clshost.com
X-AntiAbuse: Original Domain - rodricon.com
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ascls-lists.org
X-Source:
X-Source-Args:
X-Source-Dir:
X-Nonspam: Whitelist

--===1010536534==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit

The attached message was received as a bounce, but either the bounce
format was not recognized, or no member addresses could be extracted
from it.  This mailing list has been configured to send all
unrecognized bounce messages to the list administrator(s).

For more information see:
http://ascls-lists.org/mailman/admin/ascls-sd-members_ascls-lists.org/bounce



--===1010536534==
Content-Type: message/rfc822
MIME-Version: 1.0

Received: from [88.241.214.209] (helo=dsl88.241-54993.ttnet.net.tr)
by frodo.clshost.com with esmtp (Exim 4.69)
(envelope-from <[EMAIL PROTECTED]>) id 1KgKBD-0004X8-ET
for [EMAIL PROTECTED];
Thu, 18 Sep 2008 08:08:39 -0600
Message-ID: <[EMAIL PROTECTED]>
Date: Thu, 18 Sep 2008 12:20:44 +
From: "christof suvendu" <[EMAIL PROTECTED]>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: <[EMAIL PROTECTED]>
Subject: Why is your love life such a disaster? 1
Content-Type: multipart/alternative;
boundary="=_lOWyABl8u1FaKt"
X-WhitelistedRCPT-nohdrfromcallback: Yes

This is a multi-part message in MIME format.



Thanks,

J.R. Constance

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

[Mailman-Users] Greetings .. and some Questions

[Jeffrey Lake - Admin]

hello,
I love MailMan .. but I am having some problems that I hope someone here can 
help with.

I run a web-server that has MailMan installed by Cpanel. 
Most of my clients use MailMan in one way or another, as do I.
What I need to do is fix a minor problem,
approximently half the URL's MailMan creates are missing the 'www' portion of 
the
link, this causes a little problem when users log-in with the 'www' in the URL 
then get
sent to a URL with out the 'www' they are forced to log-in again ..
this gets a little annoying ..

Now for a problem releated to my web-site ..
I have been attempting to get my installs of MailMan to use
my SSL cert, as I want the entire site behind the SSL,
If I add that to the mm_cfg.py everybodies MailMan on the server
wants to run with 'https' which causes all kinds of errors ..

Is there someplace else I should be looking for each sites configs
to have my site use https

Jeff Lake
MichiganWxSystem.com
WeatherMichigan.net
HAMweather.com
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

[Mailman-Users] Admin interface for a single list misbehaving?

[Christopher Waltham]

I have a server with 873 lists (yes really!), but only one seems to be  
misbehaving. Specifically, when you go to the admin web interface and  
click on Membership Management, I get an error saying:


"Bug in Mailman version 2.1.10

We're sorry, we hit a bug!

Please inform the webmaster for this site of this problem. Printing of  
traceback and other system information has been explicitly inhibited,  
but the webmaster can find this information in the Mailman error logs."


Mailman's error.log says this at the time:

admin(5901): [- Mailman Version: 2.1.10 -]
admin(5901): [- Traceback --]
admin(5901): Traceback (most recent call last):
admin(5901):   File "/home/mailman/scripts/driver", line 101, in  
run_main

admin(5901): main()
admin(5901):   File "/home/mailman/Mailman/Cgi/admin.py", line 197, in  
main

admin(5901): show_results(mlist, doc, category, subcat, cgidata)
admin(5901):   File "/home/mailman/Mailman/Cgi/admin.py", line 498, in  
show_results
admin(5901): form.AddItem(membership_options(mlist, subcat,  
cgidata, doc, form))
admin(5901):   File "/home/mailman/Mailman/Cgi/admin.py", line 870, in  
membership_options

admin(5901): all = [_m.encode() for _m in mlist.getMembers()]
admin(5901): UnicodeDecodeError: 'ascii' codec can't decode byte 0xa0  
in position 19: ordinal not in range(128)

admin(5901): [- Python Information -]
admin(5901): sys.version =   2.3.4 (#1, Feb 18 2008, 17:17:04)
[GCC 3.4.6 20060404 (Red Hat 3.4.6-9)]
admin(5901): sys.executable  =   /usr/bin/python
admin(5901): sys.prefix  =   /usr
admin(5901): sys.exec_prefix =   /usr
admin(5901): sys.path=   /usr
admin(5901): sys.platform=   linux2
admin(5901): [- Environment Variables -]
admin(5901):HTTP_COOKIE: savo_list 
+ 
admin 
= 
280200699c2bd1487328003163393936306230656436333563636663376534626230623137633639313936376538353461 
; __u
tmz=253559834.1221579693.129.10.utmcsr=search|utmccn=(organic)| 
utmcmd=organic|utmctr=Maine%20216;  
__utma=253559834.2244931431936609800.1214331996.1221654634.122

1660210.133; __utmc=253559834
admin(5901):SERVER_SOFTWARE: Apache/2.0.52 (Red Hat)
admin(5901):SCRIPT_NAME: /mailman/admin
admin(5901):SERVER_SIGNATURE: Apache/2.0.52 (Red Hat)  
Server at list.bowdoin.edu Port 80

admin(5901):
admin(5901):REQUEST_METHOD: GET
admin(5901):HTTP_KEEP_ALIVE: 300
admin(5901):SERVER_PROTOCOL: HTTP/1.1
admin(5901):QUERY_STRING:
admin(5901):HTTP_ACCEPT_CHARSET: ISO-8859-1,utf-8;q=0.7,*;q=0.7
admin(5901):HTTP_USER_AGENT: Mozilla/5.0 (Macintosh; U; Intel Mac  
OS X 10.5; en-US; rv:1.9.0.1) Gecko/2008070206 Firefox/3.0.1

admin(5901):HTTP_CONNECTION: keep-alive
admin(5901):HTTP_REFERER: http://list.bowdoin.edu/mailman/admin/savo_list/
admin(5901):SERVER_NAME: list.bowdoin.edu
admin(5901):REMOTE_ADDR: 139.140.64.27
admin(5901):PATH_TRANSLATED: /var/www/html/savo_list/members
admin(5901):SERVER_PORT: 80
admin(5901):SERVER_ADDR: 139.140.230.56
admin(5901):DOCUMENT_ROOT: /var/www/html
admin(5901):PYTHONPATH: /home/mailman
admin(5901):SCRIPT_FILENAME: /home/mailman/cgi-bin/admin
admin(5901):SERVER_ADMIN: [EMAIL PROTECTED]
admin(5901):HTTP_HOST: list.bowdoin.edu
admin(5901):REQUEST_URI: /mailman/admin/savo_list/members
admin(5901):HTTP_ACCEPT: text/html,application/xhtml 
+xml,application/xml;q=0.9,*/*;q=0.8

admin(5901):GATEWAY_INTERFACE: CGI/1.1
admin(5901):REMOTE_PORT: 55005
admin(5901):HTTP_ACCEPT_LANGUAGE: en-us,en;q=0.5
admin(5901):HTTP_ACCEPT_ENCODING: gzip,deflate
admin(5901):PATH_INFO: /savo_list/members

I've run a "list_members savo_list" (savo_list being the list name)  
and it works fine; the list has 284 members and I don't see any  
obviously corrupt members listed there. The Apache error logs indicate  
nothing at the time of the error.


Any ideas? I'm running check_perms now but it takes a while on this  
machine. The server is Mailman 2.1.10 on Red Hat Enterprise Linux 4.6  
(i386).


Thanks,


Chris
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

[Mailman-Users] Old server settings applied to some lists

[Anne Anderson]

Hello!  I hope someone can help me fix some bad configuration.

We am running mailman 2.1.9 here at Westmont College and we have 
hundreds of lists which have been set up over the last 10 years or so. 
In that time, we have had several different mail servers.  We now use 
the name mail.westmont.edu to refer to our current mail server, 
regardless of what its real hostname is.


However, some of the lists which were created long ago seem to be still 
configured with other server names.


This results in bad links being sent out in email notices from these 
lists, such as notices to moderators that messages are being held.


The only way I have found to fix this is to remove and re-create the 
list.  Needless to say I'd rather fix the bad configs in a more direct way.


I'm a programmer (perl and php), and although I don't speak python, I 
tend to be one of those who likes to look at the scripts to find an 
answer to a problem.


So I looked at mm_cfg.py and Defaults.py and discovered these settings:

In mm_cfg.py (last modified 2002-10-07):

DEFAULT_HOST_NAME = 'mail.westmont.edu'
DEFAULT_URL   = 'http://%s/mailman/' % DEFAULT_HOST_NAME

This is correct.

In Defaults.py (last modified 2006-08-04):

DEFAULT_EMAIL_HOST = 'down.westmont.edu'
DEFAULT_URL_HOST = 'down.westmont.edu'
DEFAULT_URL_PATTERN = 'http://%s/mailman/'

# DEFAULT_HOST_NAME has been replaced with DEFAULT_EMAIL_HOST, however some
# sites may have the former in their mm_cfg.py files.  If so, we'll believe
# that, otherwise we'll believe DEFAULT_EMAIL_HOST.  Same for DEFAULT_URL.

DEFAULT_HOST_NAME = None
DEFAULT_URL = None

This is not correct... we have not had the server named 
'down.westmont.edu' for many years.  However, this hostname is 
configured into many of the lists that were created at the time.


When doing a grep for 'down.westmont.edu' in /var/lib/mailman/Mailman, 
it also tells me that the binary file Defaults.pyc matches.


We are cautioned not to edit Defaults.py by hand, and I wouldn't know 
how to recompile it anyway. :)


Can anyone tell me how to fix this so that all our lists will be 
configured for mail.westmont.edu?  Thanks!


Anne

Anne Anderson   [EMAIL PROTECTED]
Web Application Developer / Database Manager
Information Technology
Westmont College, Santa Barbara, CA, USA
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

[Mailman-Users] URLs error

[faisal anif]

Hi,
a small thingy, when I log into the list admin web interface, when clicking on 
any link I get the following:   
http://http//www.mydomain.com/mailman/cgi-bin/mailman/admin/listname/members
notice that there's 2 http:'s in the beginning and: 
".com/mailman/cgi-bin/mailman" .. so it gives me the error page .. when fixing 
it manually in the internet explorer's address bar like this:  
http//www.mydomain.com/cgi-bin/mailman/admin/listname/members
it works..  
what should I do?
thank
_
Connect to the next generation of MSN Messenger 
http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

[Mailman-Users] massive unsubscribe

[Tecru Info]

We are having a problem where half the email list is getting  
unsubscribed. Has this happened to anyone? The people did not  
unsubscribe themselves.



--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

Re: [Mailman-Users] Old server settings applied to some lists

[charlie derr]

Anne,
	I just had cause to change a config setting for all lists we manage and 
found the instructions at 
http://wiki.list.org/pages/viewpage.action?pageId=4030597

to be thorough and complete.

good luck,
~c


Anne Anderson wrote:

Hello!  I hope someone can help me fix some bad configuration.

We am running mailman 2.1.9 here at Westmont College and we have 
hundreds of lists which have been set up over the last 10 years or so. 
In that time, we have had several different mail servers.  We now use 
the name mail.westmont.edu to refer to our current mail server, 
regardless of what its real hostname is.


However, some of the lists which were created long ago seem to be still 
configured with other server names.


This results in bad links being sent out in email notices from these 
lists, such as notices to moderators that messages are being held.


The only way I have found to fix this is to remove and re-create the 
list.  Needless to say I'd rather fix the bad configs in a more direct way.


I'm a programmer (perl and php), and although I don't speak python, I 
tend to be one of those who likes to look at the scripts to find an 
answer to a problem.


So I looked at mm_cfg.py and Defaults.py and discovered these settings:

In mm_cfg.py (last modified 2002-10-07):

DEFAULT_HOST_NAME = 'mail.westmont.edu'
DEFAULT_URL   = 'http://%s/mailman/' % DEFAULT_HOST_NAME

This is correct.

In Defaults.py (last modified 2006-08-04):

DEFAULT_EMAIL_HOST = 'down.westmont.edu'
DEFAULT_URL_HOST = 'down.westmont.edu'
DEFAULT_URL_PATTERN = 'http://%s/mailman/'

# DEFAULT_HOST_NAME has been replaced with DEFAULT_EMAIL_HOST, however some
# sites may have the former in their mm_cfg.py files.  If so, we'll believe
# that, otherwise we'll believe DEFAULT_EMAIL_HOST.  Same for DEFAULT_URL.

DEFAULT_HOST_NAME = None
DEFAULT_URL = None

This is not correct... we have not had the server named 
'down.westmont.edu' for many years.  However, this hostname is 
configured into many of the lists that were created at the time.


When doing a grep for 'down.westmont.edu' in /var/lib/mailman/Mailman, 
it also tells me that the binary file Defaults.pyc matches.


We are cautioned not to edit Defaults.py by hand, and I wouldn't know 
how to recompile it anyway. :)


Can anyone tell me how to fix this so that all our lists will be 
configured for mail.westmont.edu?  Thanks!


Anne

Anne Anderson[EMAIL PROTECTED]
Web Application Developer / Database Manager
Information Technology
Westmont College, Santa Barbara, CA, USA
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/cderr%40simons-rock.edu 



Security Policy: http://wiki.list.org/x/QIA9


--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

[Mailman-Users] Admin interface for a single list misbehaving?

[Stephen J. Turnbull]

Christopher Waltham writes:

 > I have a server with 873 lists (yes really!), but only one seems to be  
 > misbehaving. Specifically, when you go to the admin web interface and  
 > click on Membership Management, I get an error saying:

 > admin(5901): UnicodeDecodeError: 'ascii' codec can't decode byte 0xa0  
 > in position 19: ordinal not in range(128)

IIRC, in most unibyte encodings 0xA0 is NO-BREAK SPACE.  You wouldn't
be able to see that.

If you have shell access to the Mailman installation,

bin/with_list savo

for i in m.getMembers():
# This loop should break at the problem member
try:
i.encode()
except:
print i

will print any bogus members.  (My Mailman is a little rusty, but it
should be something like that.  The comments in the with_list script
will tell you what variable holds the list config, but I'm pretty sure
it's "m".)
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

[Mailman-Users] massive unsubscribe

[Stephen J. Turnbull]

Tecru Info writes:

 > We are having a problem where half the email list is getting  
 > unsubscribed. Has this happened to anyone? The people did not  
 > unsubscribe themselves.

Things to check:

(1) You have been (mis)identified as a spammer, and ISPs are bouncing
your mail.  This causes the mail you send to those ISPs (any user
at such an ISP) to bounce, and the users get unsubscribed.

(2) You have a lot of users at an ISP like AOL, which assume that
you're a spammer until you take steps to prove otherwise.  (But
these ISPs tend to throw away mail that they don't like rather
than bounce it, so the symptom would be not getting posts rather
than getting unsubscribed.)

There's more information about both of these issues, how to check and
how to resolve, in the FAQ.
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

[Mailman-Users] Emails sent directly to "bounce" address

[Stephen J. Turnbull]

J.R. Constance writes:

 > Is there any way to filter these emails sent to the bounce address so  
 > that if they are spam they just get discarded.

Procmail, ClamAV, etc.  You should be running such filters on all
received mail.  If you can't reconfigure the MTA to do this for some
reason, the admin can usually run procmail through his/her .forward
file.

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

Re: [Mailman-Users] Old server settings applied to some lists

[Mark Sapiro]

Anne Anderson wrote:
>
>So I looked at mm_cfg.py and Defaults.py and discovered these settings:
>
>In mm_cfg.py (last modified 2002-10-07):
>
>DEFAULT_HOST_NAME = 'mail.westmont.edu'
>DEFAULT_URL   = 'http://%s/mailman/' % DEFAULT_HOST_NAME
>
>This is correct.


Remove the above two lines (deprecated settings) from mm_cfg.py and add
the following four lines

DEFAULT_EMAIL_HOST = 'mail.westmont.edu'
DEFAULT_URL_HOST = 'mail.westmont.edu'
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)


>In Defaults.py (last modified 2006-08-04):
>
>DEFAULT_EMAIL_HOST = 'down.westmont.edu'
>DEFAULT_URL_HOST = 'down.westmont.edu'
>DEFAULT_URL_PATTERN = 'http://%s/mailman/'
>
># DEFAULT_HOST_NAME has been replaced with DEFAULT_EMAIL_HOST, however some
># sites may have the former in their mm_cfg.py files.  If so, we'll believe
># that, otherwise we'll believe DEFAULT_EMAIL_HOST.  Same for DEFAULT_URL.
>
>DEFAULT_HOST_NAME = None
>DEFAULT_URL = None
>
>This is not correct... we have not had the server named 
>'down.westmont.edu' for many years.  However, this hostname is 
>configured into many of the lists that were created at the time.


Don't worry about that. The four lins you add to mm_cfg.py will
override the Defaults.py settings.


>When doing a grep for 'down.westmont.edu' in /var/lib/mailman/Mailman, 
>it also tells me that the binary file Defaults.pyc matches.
>
>We are cautioned not to edit Defaults.py by hand, and I wouldn't know 
>how to recompile it anyway. :)


You don't edit Defaults.py, you override Defaults.py with mm_cfg.py,
and Python recompiles it automatically as necessary.


>Can anyone tell me how to fix this so that all our lists will be 
>configured for mail.westmont.edu?  Thanks!


Make the above changes to mm_cfg.py and restart Mailman. This still
won't fix the existing list which are wrong, but it will set
everything up properly. To fix the existing lists, run

 bin/withlist -l -a -r fix_url

or if you wan't fix_url to report what it's doing

 bin/withlist -l -a -r fix_url -- -v

For more information, go to
 and
search for "fix_url.

-- 
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://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

Re: [Mailman-Users] Greetings .. and some Questions

[Mark Sapiro]

Jeffrey Lake - Admin wrote:
>
>I run a web-server that has MailMan installed by Cpanel. 
>Most of my clients use MailMan in one way or another, as do I.
>What I need to do is fix a minor problem,
>approximently half the URL's MailMan creates are missing the 'www' portion of 
>the
>link, this causes a little problem when users log-in with the 'www' in the URL 
>then get
>sent to a URL with out the 'www' they are forced to log-in again ..
>this gets a little annoying ..


See the post at

which doesn't answer your exact question, but should be pretty close.


>Now for a problem releated to my web-site ..
>I have been attempting to get my installs of MailMan to use
>my SSL cert, as I want the entire site behind the SSL,
>If I add that to the mm_cfg.py everybodies MailMan on the server
>wants to run with 'https' which causes all kinds of errors ..
>
>Is there someplace else I should be looking for each sites configs
>to have my site use https


See the FAQ at .

-- 
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://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

Re: [Mailman-Users] Admin interface for a single list misbehaving?

[Mark Sapiro]

Christopher Waltham wrote:
>
>"Bug in Mailman version 2.1.10
>
>We're sorry, we hit a bug!
>
>Please inform the webmaster for this site of this problem. Printing of  
>traceback and other system information has been explicitly inhibited,  
>but the webmaster can find this information in the Mailman error logs."
>
>Mailman's error.log says this at the time:
>
>admin(5901): [- Mailman Version: 2.1.10 -]
>admin(5901): [- Traceback --]
>admin(5901): Traceback (most recent call last):
>admin(5901):   File "/home/mailman/scripts/driver", line 101, in  
>run_main
>admin(5901): main()
>admin(5901):   File "/home/mailman/Mailman/Cgi/admin.py", line 197, in  
>main
>admin(5901): show_results(mlist, doc, category, subcat, cgidata)
>admin(5901):   File "/home/mailman/Mailman/Cgi/admin.py", line 498, in  
>show_results
>admin(5901): form.AddItem(membership_options(mlist, subcat,  
>cgidata, doc, form))
>admin(5901):   File "/home/mailman/Mailman/Cgi/admin.py", line 870, in  
>membership_options
>admin(5901): all = [_m.encode() for _m in mlist.getMembers()]
>admin(5901): UnicodeDecodeError: 'ascii' codec can't decode byte 0xa0  
>in position 19: ordinal not in range(128)


>I've run a "list_members savo_list" (savo_list being the list name)  
>and it works fine; the list has 284 members and I don't see any  
>obviously corrupt members listed there. The Apache error logs indicate  
>nothing at the time of the error.
>
>Any ideas? I'm running check_perms now but it takes a while on this  
>machine. The server is Mailman 2.1.10 on Red Hat Enterprise Linux 4.6  
>(i386).


The list has a member with a non-ascii character (0xa0 = no-break
space) in her/his email address.

If you don't see it in bin/list_members, try

  bin/list_members --invalid

Also, see .

-- 
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://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

Re: [Mailman-Users] URLs error

[Mark Sapiro]

faisal anif wrote:
>
>Hi,
>a small thingy, when I log into the list admin web interface, when clicking
> on any link I get the following:   
> http://http//www.mydomain.com/mailman/cgi-bin/mailman/admin/listname/members
>notice that there's 2 http:'s in the beginning and: 
>".com/mailman/cgi-bin/mailman" .. so it gives me the error page .. when fixing 
>it manually in the
>internet explorer's address bar like this:  http//www.mydomain.com/cgi-bin/=
>mailman/admin/listname/members
>it works..


At the time this list was created, I'm guessing you had something like

DEFAULT_URL_HOST = 'http//www.mydomain.com/mailman'

in mm_cfg.py or possibly in Defaults.py. See the post at
.

-- 
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://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

Re: [Mailman-Users] Greetings .. and some Questions

[Bill Christensen]

At 1:21 PM -0400 9/17/08, Jeffrey Lake - Admin wrote:

hello,
I love MailMan .. but I am having some problems that I hope someone 
here can help with.


I run a web-server that has MailMan installed by Cpanel.
Most of my clients use MailMan in one way or another, as do I.
What I need to do is fix a minor problem,
approximently half the URL's MailMan creates are missing the 'www' 
portion of the
link, this causes a little problem when users log-in with the 'www' 
in the URL then get

sent to a URL with out the 'www' they are forced to log-in again ..
this gets a little annoying ..


That sounds more like a problem in how you have your web server 
and/or DNS service configured than a Mailman problem.


We set up our domains such that www.domain.com and domain.com will 
point to the same files, as the "www" portion is really rather 
redundant.   There would have to be entries in DNS for both, as well 
as entries in your apache httpd.conf (or similar for whatever 
webserver you might be using) to achieve this.


I can reach any of our hosted lists using 
www.domain.com/mailman/listinfo/listname or 
domain.com/mailman/listinfo/listname as a result.



Now for a problem releated to my web-site ..
I have been attempting to get my installs of MailMan to use
my SSL cert, as I want the entire site behind the SSL,
If I add that to the mm_cfg.py everybodies MailMan on the server
wants to run with 'https' which causes all kinds of errors ..


I'll leave the answer to this one to those who are more familiar with Mailman.
--
Bill Christensen


Green Building Professionals Directory: 
Sustainable Building Calendar: 
Green Real Estate: 
Straw Bale Registry: 
Books/videos/software: 
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

Re: [Mailman-Users] bin/upgrade has been broken since 2.1.5 (orpossibly longer)

[Mark Sapiro]

Knut Auvor Grythe wrote:

>The _UpdateRecords function in ListAdmin.py is completely broken, and
>has been since 2.1.5. There is a bugreport filed in 2004 at
>https://bugs.launchpad.net/mailman/+bug/266106, and a patch for the
>issue was included in march 2005. It seems the issue has gone unnoticed,
>though. Possibly because the title of the bug report is "Tend to Pending
>Moderator Requests breaks on a few lists", which doesn't seem all that
>bad.
>
>The _UpdateRecords function in ListAdmin.py reads the two-element tuple
>(op, info). It then checks if info has all necessary fields. If it has,
>nothing is done. If info _doesn't_ have all necessary fields (e.g. comes
>from an old version of mailman), the missing fields are added and info
>saved back. Notice how "info" is different from "(op, info)".
>
>This causes all subsequent access to subscription and held message
>records to fail with a ValueError, since an info typle is not 2 elements
>long.
>
>I think it would be very nice to have this fixed in 2.1.11. But even if
>that doesn't happen I thought I should notify people about the problem,
>so they know what to do if their upgrade causes trouble.


Thanks for the report.

It's too late for 2.1.11 which was released on June 7, 2008, however, I
will apply the part of the patch that fixes the actual error to the
2.1 and 2.2 branches so it will be in 2.2 and if there is another 2.1
release post 2.1.11, it will be there too.

I don't see the need to apply the part of the patch that recovers from
the incorect migration. Anyone who migrates with outstanding
subscription approval or held message requests from pre 2.1a4 to
Mailman through 2.1.11 will encounter the problem and will presumably
deal with it somehow before migrating to a still later version. For
anyone who migrates from pre 2.1a4 to a post 2.1.11 Mailman, the
correction will suffice and recovery won't be needed.

-- 
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://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

Re: [Mailman-Users] massive unsubscribe

[Emiliano Casal]

Happened to us when first started. Perhaps you massive subscribe most of
them and the server techs support think you could possibly be doing bulk
mailing.
Regards,
Emiliano
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9