Mailman 3 December 2005 - Mailman-Users

Newbie - Help
by Tom＠tomsfish.net 04 Jan '06

04 Jan '06

I am new to this list and to mailman My inslation came preinstalled on a server from 1 and 1 using redhat and apache but NOT python...they have it worked around they claim....anyway... I can set up lists...go thru all the steps but users cannot subscribe...it says they have but it never sends out the confirmation email and it doesnt show them as subscribed users. I have scoured the options and i cant find anythign not set properly, but newbies can be dummies...so ideas are welcome. Thanks Tom

3 2

strange problem...
by Robin Getz 04 Jan '06

04 Jan '06

I am running into a bit of a problem - mail seems to be coming into, and being accepted by mailman, and it stacks up in ./qfiles/in/[key].pck files, and nothing every seems to be sent out. Any ideas? Thanks -Robin Running SuSe 9.3 if that makes a difference, all the mailman scripts seem to be running... ?

2 1

List Probe Problems
by mailbag 04 Jan '06

04 Jan '06

Hi, For some reason, users who have bounced mails back, end up getting the probe email later - and it includes attachments with all the other bounced probe emails, which includes other user's passwords to the list. I haven't been able to track down the cause, nor have I found references to anyone else having this problem. Any suggestions would be appreciated.

2 1

RELEASED Mailman 2.1.7
by Tokio Kikuchi 02 Jan '06

02 Jan '06

I'm pleased to announce the release of GNU Mailman 2.1.7. This is a significant release, which includes security enhancement fixes, a new language (ia: Interlingua) support, a couple of new features, and many bug fixes. Mailman is free software for managing email mailing lists and e-newsletters. This release enhances the fixes for CAN-2005-0202 and CVE-2005-3573 which were fixed in mailman release 2.1.6, and reduces the chance of list admin privilege abuse. Because of these and other fixes, it is highly recommended that all sites update to 2.1.7. For more information, see: http://mailman.sourceforge.net/ For links to download the Mailman 2.1.7 source tarball, see: http://sourceforge.net/project/showfiles.php?group_id=103 Best regards and a happy new year! -- Tokio Kikuchi

5 6

error in Log file: locks
by Con Wieland 31 Dec '05

31 Dec '05

I get the following errors 2 File "/usr/local/mailman/bin/qrunner", line 270, in ? 2 File "/usr/local/mailman/bin/qrunner", line 230, in main 2 File "/usr/local/mailman/Mailman/Queue/VirginRunner.py", line 38, in _dispose 2 File "/usr/local/mailman/Mailman/Queue/Runner.py", line 65, in run 2 File "/usr/local/mailman/Mailman/Queue/Runner.py", line 160, in _onefile 2 File "/usr/local/mailman/Mailman/Queue/Runner.py", line 110, in _oneloop 2 File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 115, in _dispose 2 File "/usr/local/mailman/Mailman/MailList.py", line 159, in Lock 2 File "/usr/local/mailman/Mailman/LockFile.py", line 416, in __writelog 2 traceback.print_stack(file=logf) 2 self._onefile(msg, msgdata) 2 self.__lock.lock(timeout) 2 return IncomingRunner._dispose(self, mlist, msg, msgdata) 2 qrunner.run() 2 mlist.Lock(timeout=mm_cfg.LIST_LOCK_TIMEOUT) 2 main() 2 keepqueued = self._dispose(mlist, msg, msgdata) 2 filecnt = self._oneloop() 1 mailman.lock unexpected linkcount: -1 1 mailman.lock lifetime has expired, breaking 1 File "/usr/local/mailman/Mailman/LockFile.py", line 306, in lock 1 File "/usr/local/mailman/Mailman/LockFile.py", line 287, in lock 1 self.__linkcount(), important=True) 1 important=True) an ls -l on /usr/local/mailman/locks bash-2.05$ ls -l total 6 -rw-rw-r-- 1 nobody 71 Sep 29 03:18 casa- chavez.lock.maillists.nac.uci.edu.8797.68 -rw-rw-r-- 1 mailman 0 Sep 1 08:04 imwest.lock.maillists.nac.uci.edu.6799.248 -rw-rw-r-- 2 mailman 66 Jan 1 2006 master-qrunner -rw-rw-r-- 2 mailman 66 Jan 1 2006 master- qrunner.maillists.nac.uci.edu.7087 -rw-rw-r-- 1 nobody 64 Jul 24 2004 ucdc.lock.maillists.nac.uci.edu.15367.0 -rw-rw-r-- 1 nobody 64 Jul 24 2004 ucdc.lock.maillists.nac.uci.edu.15368.0 -rw-rw-r-- 1 nobody 64 Jul 24 2004 ucdc.lock.maillists.nac.uci.edu.15369.0 any ideas what's going on? Why is the date on master-qrunner a day ahead of my system. I checked using 'date'? Can these be deleted? Thanks in advance And thanks for the new version MM Developers rock! Con WIeland Network and Academic Computing Services University of California at Irvine

1 0

Re: [Mailman-Users] falling back to login screen
by M. Onur ERGiN 30 Dec '05

30 Dec '05

Oh, I forgot to add this info. This is not a problem occuring on only one computer. Anyone who tries to access the web interface (admin, all moderators, etc) encounter this problem. So, it must be something not related to cookies, right? Regards. Onur. Research assistant and System Admin at Yeditepe University. Dan Phillips <dhphllps(a)memphis.edu> wrote: On Dec 30, 2005, at 4:04 PM, M. Onur ERGiN wrote: > I am running mailman on a RH9 sever, which has qmail and apache. > Everything was very fine since I installed mailman (it's been about > 6 months). but lately, I can not make any changes using admin > interface. > Every single click on links or form submissions causes me to fall > back to the login screen and no changes are saved. I cannot change > membership preferences, or I can't approve/discard/reject/defer > pending messages. One possibility: this is the primary symptom of turning off cookies in your web browser. Dan ================================ Dan Phillips Associate Professor of Horn, University of Memphis site administrator: music.memphis.edu --------------------------------- Yahoo! for Good - Make a difference this year.

1 0

Re: [Mailman-Users] Upgrade problems from 2.1.5 to 2.1.6
by Paul Williams 30 Dec '05

30 Dec '05

I am running mailman-2.1.5 on a redhat linux AS 4 system with all the latest redhat fixes. I just ran the mailman-2.1.6 upgrade and encountered the following messages for each (but not all my lists) Updating mailing list: 4h-northern^M Updating the held requests database.^M - updating old private mbox file^M looks like you have a really recent CVS installation...^M you're either one brave soul, or you already ran me^M - updating old public mbox file^M Fixing language templates: 4h-northern^M followed by Updating Usenet watermarks^M - nothing to update here^M Updating Mailman 2.1.4 pending.pck database^M WARNING: Ignoring duplicate pending ID: 7.^M WARNING: Ignoring duplicate pending ID: 5.^M WARNING: Ignoring duplicate pending ID: 10.^M updating old qfiles^M Traceback (most recent call last):^M File "bin/update", line 780, in ?^M errors = main()^M File "bin/update", line 709, in main^M update_qfiles()^M File "bin/update", line 414, in update_qfiles^M for filename in os.listdir(mm_cfg.QUEUE_DIR):^M OSError: [Errno 2] No such file or directory: '/var/spool/mailman/qfiles'^M make: *** [update] Error 1^M [root@shad mailman-2.1.6]# exit^M exit^M I have not started the upgraded mailman yet. I don't know where it picked up /var/spool/mailman/qfiles as the qfiles directory is /opt/mailman/qfiles. Is the above actually a serious problem? Is there additional steps the system must run? If so what do I need to do to fix things? I was not able to make a "local" backup of the archive list as it is about 12G in size, although I do have a backup on our main central backup system---I would prefer not to need to recover from there as it would take a fair amount of time to download. Any help/clarification as to what happened is appreciated. paulw

1 1

export mailman lists from server?
by Melinda Odom 30 Dec '05

30 Dec '05

Hi, Is it possible to export a mailman list of email addresses from Plesk or the server? I have a linux server running Plesk 7.5.4 reloaded for the administration. If so, how would you do it? Thanks! Sincerely, Melinda Odom www.designhosting.biz 479-471-0891 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.9/217 - Release Date: 12/30/2005

1 0

[Fixed] Re: Permission oddity (was: problems with mailman)
by Lic. Martin Marques 30 Dec '05

30 Dec '05

On Thu, 29 Dec 2005, Alexander Dalloz wrote: > If you face such issues where the unix permissions match but you get > permission denied, then have a look at the SELinux logging output > (either messages syslog file or when auditd runs in audit.log). You may > temporary set SELinux into permissive mode by following command: > setenfore=0. In that mode SELinux just documents what it thinks about > actions of the system and logs them, but does not deny these actions. No, I have SELinux off there. The problem was at a higher directory for which mailman did not have execute (move into the directory) permission, so it couldn't stat the file (or directory in this case) because it counldn't get there. The strange thing is that mailman's check_perms said that everything was OK, so I thing the logic of that script should get changed (sending a mail to the mailman list so they know). -- 11:50:02 up 7 days, 23:02, 1 user, load average: 0.00, 0.02, 0.00 --------------------------------------------------------- Lic. Martín Marqués | SELECT 'mmarques' || Centro de Telemática | '@' || 'unl.edu.ar'; Universidad Nacional | DBA, Programador, del Litoral | Administrador ---------------------------------------------------------

1 0

moderator flag for new users turned off
by Pete Phillips 30 Dec '05

30 Dec '05

Hi I appear to have a problem with mailman. Today, 5 messages were sent to the whole list which appear to be related to subscription confirmation messages. The first was a confirmation message, [Smtlinfo] Fw: confirm 16566a786346f795c9a977f70b61568a613e3875 the rest were "Re: [Smtlinfo] Fw: confirm 16566a786346f795c9a977f70b61568a613e3875" [I have changed the confirmation code]. These messages are being sent to the whole list (the list was,I thought, moderated!). Having looked at the postfix logs, nothing strange appesared to be going on. However, when I looked at the mailman admin screen for the list, I noted that the flag for moderating all mail for new members in the Privacy Options screen had been set to NO. I have reset this to YES and in the membership screen turned on moderation for all members. My question is: Has anyone seen this behaviour before, and can they give me a hint to track the problem down ? I am running mailman-2.1.4-83.13 on Suse enterprise server. I performed an Online Update with SLES about 2 weeks ago, and I *think* it upgraded mailman at the time (I'm not sure though) but the problem only surfaced yesterday afternoon. Many thanks, Pete -- Pete Phillips, Acting Director, | http://www.smtl.co.uk/ Surgical Materials Testing Lab, | http://www.worldwidewounds.com/ Princess of Wales Hospital, S Wales | http://www.dressings.org/ Tel/Fax: +44 1656-752820/30 | pete(a)smtl.co.uk

1 0