Mailman 3 February 2004 - Mailman-Developers

list bug
by Ron Jarrell 22 Feb '04

22 Feb '04

I just hit this on one of my lists, when someone tried to subscribe: Bug in Mailman version 2.1.5a3 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/home/mailman/scripts/driver", line 87, in run_main main() File "/home/mailman/Mailman/Cgi/subscribe.py", line 96, in main process_form(mlist, doc, cgidata, language) File "/home/mailman/Mailman/Cgi/subscribe.py", line 176, in process_form mlist.AddMember(userdesc, remote) File "/home/mailman/Mailman/MailList.py", line 856, in AddMember self.HoldSubscription(email, name, password, digest, lang) File "/home/mailman/Mailman/ListAdmin.py", line 391, in HoldSubscription assert not self.__db.has_key(id) AssertionError I updated to the latest cvs code, making sure this time to specify the maint tag I'd been forgetting, and installed, but make update tells me I'm trying to downgrade from 2.2 to 2.1.5a3, and that's probbaly not safe.. Did I end up hosing my listdb in my earlier upgrades?

2 1

add to FAQ? - mailman full raw archive mboxes not anti-spammed
by boud 20 Feb '04

20 Feb '04

hi mailman people, terri, i looked for information regarding archtocnombox.html relating to the problem of a full raw mbox archive being non-antispammed, but couldn't find any discussion. It's clear somebody has thought about it, since the file exists. Are there any plans (or any options already present) to have the full raw mbox archive, but corrected for "@" -> " at " (maybe other obvious corrections too), to be made available like the raw spammable version is available if the archtocnombox.html template is not chosen? It seems to me that this should be made an obvious option - or else that the default should be that the full raw archive .mbox is *not* available. At least, could info on this be added to the FAQ somewhere, so that people can easily find out what has already been done? E.g. > 11.2 What does Mailman do to help protect me from unsolicited bulk > email (spam)? http://www.list.org/mailman-member/node40.html i've added a comment on barry warsaw's wiki pages: http://zope.org/Members/bwarsaw/MailmanDesignNotes/MailmanProblems and below is my own analysis. thanks boud (convert from sympa to mailman ;) PS: Sorry if this should be to mailman-users rather than mailman-developers, but it seems to me like a developers' issue. ---------------------------------------------------------------------- SPAM PROBLEM: HYPOTHESIS SOLUTION 2.1.4 HACK SOLUTION 2.0.11 (AND PROBABLY 2.1.1) (1) remove link to *.mbox in /var/lib/mailman/Mailman/Archiver/HyperArch.py (2) remove compiled versions HyperArch.py[oc] (3) test on an archive (e.g. imc-pl-tech ;) (4) make the *.mbox/*.mbox files inaccessible (since google links remain) (5) think about newlist s (maybe nothing needs doing) SPAM PROBLEM: ------------ i think this is a known spam problem - by default, it looks like the archive files linked under "download the full raw archive" like the following etc are NOT antispammed: http://lists.mydomain.org/mailman/public/mylist.mbox/mylist.mbox It seems to be present in 2.0.11 and 2.1.1 HYPOTHESIS ---------- IMHO the reason why this is probably not easy to solve is that this is where mail is automatically saved when it's received. If this is filtered by " at " -> "@" then it means that overall there are typically 4 copies of the entire mailbox (e.g. html version, monthly archives, true mailbox with @ hidden from external access, and " at " version for web access). i couldn't find if this has been discussed, but it looks like there's a simple solution in 2.1.4. SOLUTION 2.1.4 -------------- It looks like the solution in mailman-2.1.4 is to offer different templates: mailman-2.1.4/templates/en/archtoc.html mailman-2.1.4/templates/en/archtocentry.html mailman-2.1.4/templates/en/archtocnombox.html -> this one has no mbox e.g. http://mail.python.org/pipermail/mailman-announce/ has no *.mbox/*.mbox In fact, http://mail.python.org/pipermail/mailman-announce.mbox/ exists but nothing in it is accessible. HACK SOLUTION 2.0.11 (AND PROBABLY 2.1.1) ---------------------------------------- In 2.0.11, the line pointing to the .mbox is in /var/lib/mailman/Mailman/Archiver/HyperArch.py (for Debian anyway ;) You can get <a href="%(listinfo)s">more information about this list</a> or you can <a href="%(fullarch)s">download the full raw archive</a> (%(size)s). </p> solution: (1) remove the link to the full .mbox in /var/lib/mailman/Mailman/Archiver/HyperArch.py To do this, replace You can get <a href="%(listinfo)s">more information about this list</a> or you can <a href="%(fullarch)s">download the full raw archive</a> (%(size)s). </p> by You can get <a href="%(listinfo)s">more information about this list.</a> </p> (2) remove compiled versions (in my case the .pyc gets automatically recompiled) rm /var/lib/mailman/Mailman/Archiver/HyperArch.py[co] (3) test this cd /var/lib/mailman/archives/public/ /usr/lib/mailman/bin/arch mylist Then check out: http://lists.mydomain.org/pipermail/mylist/ Hopefully there will be no link to the .mbox and even direct access will be impossible. (4) make the .mbox files inaccessible - since google links will still hang around for some time chmod go-rw /var/lib/mailman/archives/private/*.mbox/*.mbox (5) probably nothing needed when running newlist for new lists. Making new lists will, by default, write *.mbox/*.mbox which are web accessible, but nobody is going to link to them (unless paranoid, deliberately wants to subject indymedia users to spam, ...) anti-spam solidarity boud ----------------------------------------------------------------------

2 4

Mailman 2.1.4 migration
by Kory Wheatley 19 Feb '04

19 Feb '04

We have Mailman 2.1.4 currently running on a Linux Red Hat 8 box called mm.isu.edu, the mta is "postfix", and our mailing list addresses are listname(a)mm.isu.edu. We would like to move or migrate our current mailman mailing lists over to a existing linux red hat box that is called lx5.isu.edu, but we would like to keep our mailing lists addresses the same, example, listname(a)mm.isu.edu not as listname(a)lx5.isu.edu. I know to do this we would need to put a CNAME in DNS pointing lx5.isu.edu to mm.isu.edu, we would also need to created a virtual server to have the web server still be mm.isu.edu . My plan was to install a clean version of mailman 2.1.4 on lx5.isu.edu, then move the mailing lists from mm.isu.edu over to lx5.isu.edu (the directories that I would move over would be /home/mailman/lists and /home/mailman/archives) and hopefully nobody would notice that there was a change done. Basically, I'm trying to duplicate what I have on mm.isu.edu to lx5.isu.edu and then remove the old mm.isu.edu. I'm I missing any steps or is this possible? -- Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him.

3 2

Re: [Mailman-Users] cascaded lists -- any tips?
by Tokio Kikuchi 19 Feb '04

19 Feb '04

martin f krafft wrote: > also sprach Tokio Kikuchi <tkikuchi(a)is.kochi-u.ac.jp> [2004.02.19.0036 +0100]: > >>>This works okay until someone posts a message to A, which is to be >>>moderated. I accept the message for A, and then am asked to do the >>>same for B and C, then for D, E, F and then for G, H. Thus, I have >>>to visit the moderation interface 8 times for a single message. >> >>You can register A address in acceptable_aliases from >>admin/(B|C|D|E|F|G|H)/privacy/recipient. > > > that's not my problem. i already have the above in place. but now, > when e.g. a nonmember posts to A and I let it through. i already > decided in A's interface that the message may pass. however, i have > to tell all the other lists that it may pass as well. that's mildly > annoying. Oops. You have to open the child lists by setting generic_member_action as 'accept' which may not be acceptable to you. :-< Or, .... Hmm... You may hack SpamDetect.py's last line as --- SpamDetect.py.orig Thu Feb 19 21:40:56 2004 +++ SpamDetect.py Thu Feb 19 21:43:14 2004 @@ -122,4 +122,4 @@ if action == mm_cfg.HOLD: hold_for_approval(mlist, msg, msgdata, HeaderMatchHold) if action == mm_cfg.ACCEPT: - return + msgdata['approved'] = 1 and put the A list address in privacy/spam / accept header reg-expression. Hey! developers. 'return' in the last line may be a bug. If you have an 'accept' rule on top of the sapm filter list, the rest of the rules may be skipped. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/

2 2

pycon sprint for MM3 db backend
by Michael Kato 17 Feb '04

17 Feb '04

Barry, Kevin, Fred, and others, I'm interested in joining those working on mailman during the PyCon2004 sprint. I too am interested in seeing a db backend on mailman. I'm fairly familiar with mysql, but will be willing to write(in parallel) other backends for postgres, or db2. I can take at least one of Monday or Tuesday off from work to do this, as well as some time on the weekend. So, where can I find Mailman3 code? ....maki....

1 0

Another Chinese Problem
by Patrick Lam 17 Feb '04

17 Feb '04

Dear All Experts, Thanks to Jason R. Mastaler's kind suggestion and my Mailman can process emails with Chinese subject. However, the Chinese characters in "Today's Topics" in the digests all changed to "????", it seems Mailman processes the characters in ASCII format. The individual emails in MIME format works fine. Any suggestion?? Thanks in advance! Regards, Patrick ------------------------------------------------------ Patrick Lam Sze Fan Computer Officer II Medical Information Technology, Faculty of Medicine, The Chinese University of Hong Kong Tel:21455213 Fax:26352521 ------------------------------------------------------

1 0

Is the config.pck.last logic correct?
by Les Niles 17 Feb '04

17 Feb '04

Our list server had another crash the other day, this time it really toasted a couple of lists. :( (No, we hadn't yet done any of the mitigation steps that we should've, at least none that worked....) What happens is that some of the config.pck files get trashed by having the last part of the file overwritten with nul bytes. I'm assuming that it's a filesystem corruption causing this, perhaps involving disk hardware errors. By the time the problem is apparent, the config.pck and config.pck.last files are both trashed -- they're identical, with identical timestamps. I've looked at the logic for loading and saving config.pck, and don't see how this can happen. It seems like config.pck.last gets replaced only when the list data is saved, which should only happen at some point after the list data is successfully loaded. So there should be good data to generate the config.pck, otherwise config.pck.last should be left alone. But there seems to be some flaw in the logic, that I can't see, because both files are ending up trashed. Then again, I've clearly demonstrated an overwhelming stupidity by letting these crashes happen many times until finally something really nasty occurred, so maybe I'm just too stupid to look at the code. Or maybe something entirely different is happening. If the pickle-save itself is corrupted in a way that isn't being caught, then I suppose the bad config.pck will happily by turned into an equally bad config.pck.last. Obviously I don't have a reproducible test case for this, but maybe someone has some idea of what's going on, and how to improve the robustness. -les

2 3

regexp in Privacy Options - (?!...) ?
by Pavel Petrovic 17 Feb '04

17 Feb '04

hi, i'd like to use the following regexp in the "hold posts with header value matching a specified regexp." option of the privacy options section of mailman 2.0.10 list owner config pages: from: (?!john).*(a)hotmail.com to make all messages coming from hotmail require admin approval, except of messages coming from john(a)hotmail.com, which should be accepted without approval. i cannot make this work, though. any hints how one could achieve this functionality? (more specific: the list should be open for posts from anywhere without approval, but hotmail and similar spammers should be filtered, except of some known exceptions) thanks, pavel. p.s. please reply also to my address as i am not member of this list.

1 0

Bug in Mailman version 2.1.4
by jd 16 Feb '04

16 Feb '04

Since we have upgraded to Mailman version 2.1.4, I'm getting this error message when trying to use the web interface to any of our lists: Bug in Mailman version 2.1.4 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 68, in run_main immediate=1) File "/usr/local/mailman/Mailman/Logging/StampedLogger.py", line 52, in __init__ Logger.__init__(self, category, nofail, immediate) File "/usr/local/mailman/Mailman/Logging/Logger.py", line 49, in __init__ self.__get_f() File "/usr/local/mailman/Mailman/Logging/Logger.py", line 67, in __get_f 1) File "/usr/local/lib/python2.3/codecs.py", line 566, in open file = __builtin__.open(filename, mode, buffering) IOError: [Errno 13] Permission denied: '/usr/local/mailman/logs/error' ----------------------------------------------------------------------------- --- Python information: Variable Value sys.version 2.3.3 (#1, Feb 13 2004, 15:23:55) [GCC 2.95.4 20020320 [FreeBSD]] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd4 ----------------------------------------------------------------------------- --- Environment variables: Variable Value SERVER_SOFTWARE Apache/1.3.27 (Unix) FrontPage/5.0.2.2510 SCRIPT_NAME /mailman/admin SERVER_SIGNATURE Apache/1.3.27 Server at master-new.3dresearch.com Port 80 REQUEST_METHOD GET PATH_INFO /andrologyforum SERVER_PROTOCOL HTTP/1.1 QUERY_STRING HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) HTTP_CONNECTION Keep-Alive SERVER_NAME master-new.3dresearch.com REMOTE_ADDR 209.195.177.46 PATH_TRANSLATED /usr/local/www/data/andrologyforum SERVER_PORT 80 SERVER_ADDR 66.167.251.12 DOCUMENT_ROOT /usr/local/www/data PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/admin SERVER_ADMIN you(a)your.address HTTP_HOST lists.3dresearch.com REQUEST_URI /mailman/admin/andrologyforum HTTP_ACCEPT */* GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 1455 HTTP_ACCEPT_LANGUAGE en-us HTTP_ACCEPT_ENCODING gzip, deflate UNIQUE_ID QDGTeX8AAAEAABSolSI I have run check_perms -f and it says "No problems found" - I'd appreciate your advice... jd Janos Dohanics

1 0

Error when processing Chinese emails
by Patrick Lam 16 Feb '04

16 Feb '04

Dear Experts, When one of my user sent Chinese emails (both contents and subject), my Mailman v2.1.4 give the following errors: Feb 16 09:26:05 2004 (18754) SHUNTING: 1076835446.5623169+add7c7b00843e724cbea05418920ebc84ce5166d Feb 16 16:30:47 2004 (18754) Uncaught runner exception: unknown encoding: big5_tw Feb 16 16:30:47 2004 (18754) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 110, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 160, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/CookHeaders.py", line 74, in process prefix_subject(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/CookHeaders.py", line 262, in prefix_subject h.append(s, c) File "/home/mailman/pythonlib/email/Header.py", line 285, in append s = s.encode(outcodec, errors) LookupError: unknown encoding: big5_tw Which file I should modify to fix that problem?? Thank you very much for your kind help and attention! Regards, Patrick ------------------------------------------------------ Patrick Lam Sze Fan Computer Officer II Medical Information Technology, Faculty of Medicine, The Chinese University of Hong Kong Tel:21455213 Fax:26352521 ------------------------------------------------------

2 1