Mailman 3 March 2005 - Mailman-Users

Deleting a list - how is this possible?
by Graham Leggett 03 Mar '05

03 Mar '05

Hi all, I created a list using my new mailman installation, and due to permission problems it did not create the list correctly. I now want to delete the list so that I can try and create it again - but this functionality seems to be missing from mailman, I cannot find a delete list option anywhere, or I'm looking in the wrong place. I figured the rmlist option in the cgi-bin directory might do what I want, but all it gave me was the cryptic and meaningless message "You're being a sneaky list owner!", which leaves me no nearer to enlightenment on what method should be used to delete a list. Any ideas? Regards, Graham --

4 3

Re: [Mailman-Users] 2 initial config problems SOLVED
by FH 02 Mar '05

02 Mar '05

------ Original Message ------ Received: Tue, 01 Mar 2005 08:47:27 PM EST From: Todd <Freedom_Lover(a)pobox.com> Subject: Re: [Mailman-Users] 2 initial config problems (virtual hosts andpermissions) > > Unfortunately, check_perms won't catch the permission problem with the > alias database file(s). You want aliases.dir and aliases.pag to be > group writable. All the alias files should be owned by mailman and be > in group mailman. Then postalias should work and you'll be able to > create lists from the web. > and ------ Original Message ------ Received: Tue, 01 Mar 2005 03:51:08 PM EST From: Mark Sapiro <msapiro(a)value.net> Subject: Re: [Mailman-Users] 2 initial config problems (virtual hostsandpermissions) > > Mailman's security and permissions are based on the group. You will > note that both the mailman/ and mailman/data directories are group > "rws" group mailman, so the scripts which are running under group > 'mailman' as set by the cgi-bin wrapper can do their things OK, but it > seems that Postfix's postalias command wants the executing user (not > group) to own the aliases file. > Thanks for the help everyone I seem to be in business now. Both problems were related to the group ownership/permissions of the alias files. I never did find out how/why aliases kept reverting back to root. It doesn't seem to be happening now but I'll keep an eye on it.

1 0

performance tuning for sendmail and local users
by Iain Pople 02 Mar '05

02 Mar '05

Hi, I am setting up a Mailman instance that will deliver to around 10,000 local users. Can anyone suggest appropriate settings for Mailman and Sendmail to optimize performance? Specifically I am interested in suggestions for the following Mailman options: SMTP_MAX_RCPTS SMTP_MAX_SESSIONS_PER_CONNECTION MAX_DELIVERY_THREADS thanks, Iain.

2 1

Re: [Mailman-Users] 2 initial config problems (virtual hosts andpermissions)
by FH 02 Mar '05

02 Mar '05

------ Original Message ------ Received: Mon, 28 Feb 2005 10:30:31 PM EST From: Mark Sapiro <msapiro(a)value.net> To: FH <fhouston(a)usa.net>, <mailman-users(a)python.org> Subject: Re: [Mailman-Users] 2 initial config problems (virtual hosts andpermissions) > > What's this? Do you mean > > add_virtualhost('MACHINE', 'DOMAIN.TLD') > DOH! You're right, typo in the email on my part. I was using the correct entry in the mm_cfg file though. > > >but that's when I get the > >other "bug" page (apologies I don't have a copy handy but if it's > >important I can probably regenerate it). > > If it resulted after adding the above add_virtualhost() in mm_cfg.py, I > don't know why without seeing it. > I included the text from logs/error below[1]. If I'm reading that right, the two problems might actually be related, the first line is something about a permissions problem. > > If you're not actually using virtual hosts, you can set > > VIRTUAL_HOST_OVERVIEW = Off > Tried this and it didn't make a difference w/ the list creation problem but the issue about the email address being incorrect on the admin page did get "solved" :D > >All things postfix are running as the user postfix, all things mailman > >(qrunner is the only continuous process right?) are running as mailman. > > I did put the postfix "user" in the mailman group (mailman isn't in > > there though) > > > The 'mailman' user should definitely be in the 'mailman' group. > Added it... didn't make a difference :( > > Have you tried bin/check_perms? > Yep. Here's a test run to show you what's going on: # ls -al data total 44 drwxrwsr-x 2 root mailman 512 Mar 1 11:25 ./ drwxrwsr-x 20 root mailman 512 Feb 28 16:02 ../ -rw-r----- 1 root mailman 41 Feb 28 16:22 adm.pw -rw-rw---- 1 mailman mailman 1165 Mar 1 11:25 aliases -rw-r----- 1 mailman mailman 0 Mar 1 11:25 aliases.dir -rw-r----- 1 mailman mailman 1024 Mar 1 11:25 aliases.pag -rw-r--r-- 1 root mailman 10 Feb 28 16:07 last_mailman_version -rw-rw---- 1 mailman mailman 5 Feb 28 16:21 master-qrunner.pid -rw-r--r-- 1 root mailman 14110 Feb 28 16:02 sitelist.cfg # bin/check_perms No problems found CREATE LIST VIA WEBPAGE -> Bug in Mailman version 2.1.6b4 We're sorry, we hit a bug! (error log below [1]) # ls -al data/ NOTE ALIASES REVERTED BACK TO ROOT total 44 drwxrwsr-x 2 root mailman 512 Mar 1 11:32 ./ drwxrwsr-x 20 root mailman 512 Feb 28 16:02 ../ -rw-r----- 1 root mailman 41 Feb 28 16:22 adm.pw -rw-rw---- 1 root mailman 1906 Mar 1 11:33 aliases -rw-r----- 1 mailman mailman 0 Mar 1 11:32 aliases.dir -rw-r----- 1 mailman mailman 1024 Mar 1 11:32 aliases.pag -rw-r--r-- 1 root mailman 10 Feb 28 16:07 last_mailman_version -rw-rw---- 1 mailman mailman 5 Feb 28 16:21 master-qrunner.pid -rw-r--r-- 1 root mailman 14110 Feb 28 16:02 sitelist.cfg # bin/check_perms No problems found I'm sure it's something simple/stupid I over looked, it usually is ;) I can't for the life of me figure out what though. Is it something w/ the web browser permissions/user maybe? Should that user (nobody w/ one instance as root) be in the mailman group as well? Thanks [1] Mar 01 11:33:22 2005 (11039) command failed: /usr/sbin/postalias /local/home/mailman/data/aliases (status: 1, Not owner) Mar 01 11:33:22 2005 admin(11039): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(11039): [----- Mailman Version: 2.1.6b4 -----] admin(11039): [----- Traceback ------] admin(11039): Traceback (most recent call last): admin(11039): File "/local/home/mailman/scripts/driver", line 101, in run_main admin(11039): main() admin(11039): File "/local/home/mailman/Mailman/Cgi/create.py", line 55, in main admin(11039): process_request(doc, cgidata) admin(11039): File "/local/home/mailman/Mailman/Cgi/create.py", line 227, in process_request admin(11039): sys.modules[modname].create(mlist, cgi=1) admin(11039): File "/local/home/mailman/Mailman/MTA/Postfix.py", line 232, in create admin(11039): _update_maps() admin(11039): File "/local/home/mailman/Mailman/MTA/Postfix.py", line 53, in _update_maps admin(11039): raise RuntimeError, msg % (acmd, status, errstr) admin(11039): RuntimeError: command failed: /usr/sbin/postalias /local/home/mailman/data/aliases (status: 1, Not owner) admin(11039): [----- Python Information -----] admin(11039): sys.version = 2.3.5 (#1, Feb 28 2005, 12:33:10) [GCC 3.4.2] admin(11039): sys.executable = /usr/local/bin/python admin(11039): sys.prefix = /usr/local admin(11039): sys.exec_prefix = /usr/local admin(11039): sys.path = /usr/local admin(11039): sys.platform = sunos5 admin(11039): [----- Environment Variables -----] admin(11039): HTTP_COOKIE: iPlanetPortalServer=YmlchoifpftnfneanBTBHG@uggcf@fcyvggre.vfv.rqh@443@/arj admin(11039): SERVER_SOFTWARE: Apache/2.0.52 (Unix) admin(11039): SCRIPT_NAME: /mailman/create admin(11039): SERVER_SIGNATURE: <address>Apache/2.0.52 (Unix) Server at DOMAIN.TLD Port 80</address> admin(11039): admin(11039): REQUEST_METHOD: POST admin(11039): HTTP_KEEP_ALIVE: 300 admin(11039): SERVER_PROTOCOL: HTTP/1.1 admin(11039): QUERY_STRING: admin(11039): CONTENT_LENGTH: 151 admin(11039): HTTP_ACCEPT_CHARSET: ISO-8859-1,utf-8;q=0.7,*;q=0.7 admin(11039): HTTP_USER_AGENT: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) admin(11039): TZ: US/Eastern admin(11039): HTTP_REFERER: http://DOMAIN.TLD/mailman/create admin(11039): SERVER_NAME: DOMAIN.TLD admin(11039): REMOTE_ADDR: x.x.x.x admin(11039): SERVER_PORT: 80 admin(11039): HTTP_XXXXXXXXXXXXXXX: XXXXXXXXXXXX admin(11039): SERVER_ADDR: x.x.x.x admin(11039): DOCUMENT_ROOT: /local/home/apache2/htdocs admin(11039): PYTHONPATH: /local/home/mailman admin(11039): SCRIPT_FILENAME: /local/home/mailman/cgi-bin/create admin(11039): SERVER_ADMIN: USER(a)DOMAIN.TLD admin(11039): HTTP_HOST: DOMAIN.TLD admin(11039): HTTP_CONNECTION: keep-alive admin(11039): REQUEST_URI: /mailman/create admin(11039): HTTP_ACCEPT: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 admin(11039): GATEWAY_INTERFACE: CGI/1.1 admin(11039): REMOTE_PORT: 1558 admin(11039): HTTP_ACCEPT_LANGUAGE: en-us,en;q=0.5 admin(11039): CONTENT_TYPE: application/x-www-form-urlencoded

4 3

show_qfiles error
by Nik Lam 01 Mar '05

01 Mar '05

When I try to view the qfiles in my in out or retry directories I get an error like the following: /usr/local/mailman/bin/show_qfiles qfiles/in/*.pck ====================> qfiles/in/1109557589.84778+7a750d59fd76a54b51168a615ef23e74f4088be9.pck Traceback (most recent call last): File "/usr/local/mailman/bin/show_qfiles", line 74, in ? main() File "/usr/local/mailman/bin/show_qfiles", line 67, in main sys.stdout.write(msg.as_string()) AttributeError: 'str' object has no attribute 'as_string' I'm running Mailman version: 2.1.5 on FreeBSD 4.9 R. The qfiles that were in the other directories, e.g. shunt, were readable using show_qfiles. Are these qfiles corrupted or is this a problem with show_qfiles? Nik

1 0

extract non-address information from subscriber list?
by Christopher Adams 01 Mar '05

01 Mar '05

Is there a way to extract all the non-address information from a subscriber list? Where is that information stored? I am speaking of any name, contact, phone information that was added in addition to the email address. -- Christopher Adams

3 3

RE: [Mailman-Users] Install needed on iPower Linux box w/ Plesk
by Brad Knowles 01 Mar '05

01 Mar '05

At 7:50 AM -0800 2005-03-01, Steve Malm wrote: > Still looking for a hired hand to configure it if that is the case. If it is installed and not configured, then what you need is a Plesk expert who knows how to do the Plesk-necessary things to get it configured. I doubt that a Mailman expert is going to be able to help you in that area. -- Brad Knowles <brad(a)shub-internet.org> <http://www.shub-internet.org/brad/> "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania.

1 0

How to transfer Majordomo archive to mailman
by trishan de Lanerolle 01 Mar '05

01 Mar '05

Hi, I am new to mailman and recently took over the mailing lists administration at my college. The system administrator and I installed and configured mailman to replace the currently used majordomo. We configured it and set it up on new server. My question is are there instructions or scripts available to transfer majordomo archives and subscription lists over to mailman. Mailman is version 2.1.5-6 running on Debian Linux 2.4.26-1-k7. Thank you Trishan Systems & Networking Trinity College Hartford CT

4 5

RE: [Mailman-Users] Install needed on iPower Linux box w/ Plesk
by Brad Knowles 01 Mar '05

01 Mar '05

At 7:41 AM -0800 2005-03-01, Steve Malm wrote: > I can actually see Mailman on the control panel, but it is grayed and says > it's not configured. Perhaps I just need somebody to configure the > pre-integrated version? Sounds like a reasonable conclusion. Check with your hosting provider. -- Brad Knowles <brad(a)shub-internet.org> <http://www.shub-internet.org/brad/> "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania.

1 0

Home-grown filters
by David Wilson 01 Mar '05

01 Mar '05

I know a Mailman user who is concerned about slow-connection subscribers, and for that reason wishes to strip attachments and truncate or refuse overlong messages. Does Mailman support inclusion of home-grown filters to modify incoming messages? -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 266.4.0 - Release Date: 2/22/2005

5 6