Mailman 3 April 2015 - Mailman-Users

Mailman Initiation problems
by Dr. Mikeal Hughes April 22, 2015

April 22, 2015

Well I have been trying to get mailman to go on this Ubuntu 14.04 Server install now for 3 days. I am down to this problem. Any time I type in http://biblematters.net/cgi-bin/mailman/admin <http://biblematters.net/cgi-bin/mailman/admin> I get. A 403 error that says. Forbidden You don't have permission to access / on this server. Apache/2.4.7 (Ubuntu) Server at www.biblematters.net Port 80 Any ideas where this problem might be?

2 1

Error message on my Mailman Install.
by Dr. Mikeal Hughes April 22, 2015

April 22, 2015

Now getting this error message. - AH01276: Cannot serve directory /usr/lib/cgi-bin/mailman/: No matching DirectoryIndex (index.html,index.cgi,index.pl,index.php,index.xhtml,index.htm) found, and server-generated directory index forbidden by Options directive

2 1

Re: [Mailman-Users] Somebody could not subscribe to pypy-dev@python.org
by Laura Creighton April 22, 2015

April 22, 2015

In a message of Wed, 22 Apr 2015 14:34:00 -0700, Mark Sapiro writes: >It is a stretch, but the HTML for the form tag and it's input tags look >something like > > <FORM Method=POST ACTION="../subscribe/pypy-dev"><input type="hidden" >name="sub_form_token" >value="1429735034:cebafdd44a345e440de23b4ba49d63b71439258a"> > ><INPUT type="Text" name="email" size="30" value=""> ><INPUT type="Text" name="fullname" size="30" value=""> ><INPUT type="Password" name="pw" size="15"> ><INPUT type="Password" name="pw-conf" size="15"> ><input type=radio name="digest" value="0" CHECKED> No > <input type=radio name="digest" value="1"> Yes ><INPUT type="Submit" name="email-button" value="Subscribe"> > </FORM> > >It is conceivable that some browser could corrupt the sub_form_token >value upon submission if and only if the password fields are empty, but >as I say, it's a stretch. And this is upside-down from his experience. Things go _fine_ when the password fields are empty, it is just when he fills them out that things did not work. >When did this issue occur? I have looked at the web server logs back to >March 30, and every POST to mailman/subscribe/pypy-dev in those logs is >from a bot attempting to subscribe to many lists. Yesterday. At Tue, 21 Apr 2015 18:05:56 -0000 he sent a mail to pypy-dev-owner (me) complaining about his problem and asking if we could fix it, so sometime before but close to then I would guess. >There is another possibility. The digits left of the colon in the token >are the Unix time of when the token was generated and the stuff to the >right is a hex digest of a sha-1 hash of the time, listname, remote IP, >and a 'secret'. > >There's probably a bug here, but if the token is missing, the user gets >the 'Please take a few seconds to fill out the form before submitting >it.' message. (It would be better I think to issue the 'The form is too >old. Please GET it again.' message in this case) > >The only way the 'You must GET the form before submitting it.' message >is issued is if the time is within the 1 hour >= time >= 5 seconds >window and the hash doesn't match. This could occur if the user is >accessing the site through some kind of proxy or other device which >submits the form from a different IP than the one that got it. I will ask about this. He is using stock chrome with no adblocking plugins -- no plugins at all, as this is a new machine and he hasn't got around to installing anything yet. Laura

2 1

Re: [Mailman-Users] Somebody could not subscribe to pypy-dev@python.org
by Laura Creighton April 22, 2015

April 22, 2015

In a message of Wed, 22 Apr 2015 09:07:13 -0700, Mark Sapiro writes: >The message your user got, "You must GET the form before submitting >it.", indicates the hidden 'sub_form_token' either was not present in >the submitted form or was not of the correct format. This could indicate >that there is a subscribe form for pypy-dev on some web site somewhere >that does not generate a correct 'sub_form_token'. Basically, such 3rd >party subscribe forms are intentionally disabled by this feature because >otherwise they could be submitted by robots. He says he got the form from https://mail.python.org/mailman/listinfo/pypy-dev So what can corrupt the token, I wonder. How chrome stores tokens and what things -- like an add blocker -- could modify or remove it isn't one of the things I know. And how this fits in with 'ok when no password used, not ok when a password used' seems quite puzzling to me. Off to think some more ... Laura

2 1

kernel update
by Nicoli Stupinski April 22, 2015

April 22, 2015

I have a system running CentOS v6.2 that I want to do a kernel update on to fix an issue. If I do a "yum update kernel" it will install the kernel that used with CentOS v6.6. I know, I know, I should update all of the packages and go to v6.6 but I can't do just that at this time. Will running the CentOS v6.6 kernel be a problem if the rest of the system is at the CentOS 6.2 level? Current: 2.6.32-279.9.1.el6 One I need or greater: 2.6.32-279.33.1.el6 (But I can't find this anywhere) Latest via yum: 2.6.32-504.16.2.el6 -Nic

2 1

Re: [Mailman-Users] Somebody could not subscribe to pypy-dev@python.org
by Laura Creighton April 22, 2015

April 22, 2015

In a message of Tue, 21 Apr 2015 16:31:46 -0700, Mark Sapiro writes: >On 04/21/2015 03:55 PM, Laura Creighton wrote: >> Forwarded message here. He just tried to subscribe as ben.jolitz(a)xad.com >> but apparantly can only subscribe if he leaves the password field blank. >> >> It is, of course, working just fine for me. > > >And it has nothing to do with the password being blank. Thank you Mark. Maybe we need a longer, more descriptive error message for when that happens? Laura

2 1

Cron command?
by Bill Christensen April 22, 2015

April 22, 2015

Hi all, I recently updated and my digests stopped going out (I was able to push out the waiting digest manually by doing /opt/local/share/mailman/cron/senddigests so I know the function is working). My old notes tell me the command for cron is: sudo /opt/local/share/mailman/cron/crontab -u mailman crontab.in I also tried sudo /opt/local/share/mailman/cron -u mailman crontab.in since that appears to be the current location of crontab.in but that's getting me 'command not found' and cron: illegal option -- u usage: cron [-s] [-o] [-x debugflag[,...]] debugflags: ext sch proc pars load misc test bit Any ideas on this?

7 14

Somebody could not subscribe to pypy-dev@python.org
by Laura Creighton April 21, 2015

April 21, 2015

Forwarded message here. He just tried to subscribe as ben.jolitz(a)xad.com but apparantly can only subscribe if he leaves the password field blank. It is, of course, working just fine for me. Laura ------- Forwarded Message Return-Path: <ben.jolitz(a)xad.com> Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0081.outbound.protection.outlook.com [65.55.169.81]) by theraft.openend.se (8.14.4/8.14.4/Debian-4) with ESMTP id t3LMPjWl005823 (version=TLSv1/SSLv3 cipher=AES256-SHA256 bits=256 verify=OK) for <lac(a)openend.se>; Wed, 22 Apr 2015 00:25:48 +0200 Received: from CO2PR0601MB0949.namprd06.prod.outlook.com (25.160.10.21) by CO2PR0601MB0951.namprd06.prod.outlook.com (25.160.10.23) with Microsoft SMTP Server (TLS) id 15.1.136.25; Tue, 21 Apr 2015 22:25:37 +0000 Received: from CO2PR0601MB0949.namprd06.prod.outlook.com ([25.160.10.21]) by CO2PR0601MB0949.namprd06.prod.outlook.com ([25.160.10.21]) with mapi id 15.01.0136.014; Tue, 21 Apr 2015 22:25:38 +0000 From: Ben Jolitz <ben.jolitz(a)xad.com> To: Laura Creighton <lac(a)openend.se> CC: Maciej Fijalkowski <fijall(a)gmail.com>, "pypy-dev-owner(a)python.org" <pypy-dev-owner(a)python.org> Subject: Re: cannot subscribe to pypy-dev Thread-Topic: cannot subscribe to pypy-dev Thread-Index: AQHQfF3QMj8aywLr/US+oe9lL0sZLZ1XxyCAgAAWCqD//7juAA== Date: Tue, 21 Apr 2015 22:25:37 +0000 Message-ID: <D15C1C2B.21C%ben.jolitz(a)xad.com> References: <D15BDF96.1F8%ben.jolitz(a)xad.com> <CAK5idxRQ_-ZUQNSitP0Feu=H_bFMcBu-3ecd=Dt7rhWcQF-rJg(a)mail.gmail.com> <201504211914.t3LJEbCG007311(a)fido.openend.se> <D15BF054.201%ben.jolitz(a)xad.com> <201504211939.t3LJdaYR008366(a)fido.openend.se> In-Reply-To: <201504211939.t3LJdaYR008366(a)fido.openend.se> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: openend.se; dkim=none (message not signed) header.d=none; x-ms-exchange-messagesentrepresentingtype: 1 x-originating-ip: [50.205.11.76] x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CO2PR0601MB0951; x-microsoft-antispam-prvs: <CO2PR0601MB095140DAE6D79B0A9A50D21F81EF0(a)CO2PR0601MB0951.namprd06.prod.outlook.com> x-forefront-antispam-report: BMV:1;SFV:NSPM;SFS:(10009020)(6009001)(479174004)(51704005)(377454003)(24454002)(2656002)(92566002)(106116001)(50986999)(76176999)(15975445007)(102836002)(87936001)(2950100001)(122556002)(46102003)(2900100001)(93886004)(110136001)(19580405001)(36756003)(19580395003)(66066001)(86362001)(551544002)(77156002)(99286002)(54356999)(40100003)(62966003);DIR:OUT;SFP:1101;SCL:1;SRVR:CO2PR0601MB0951;H:CO2PR0601MB0949.namprd06.prod.outlook.com;FPR:;SPF:None;MLV:sfv;LANG:en; x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(601004)(5005006)(5002010);SRVR:CO2PR0601MB0951;BCL:0;PCL:0;RULEID:;SRVR:CO2PR0601MB0951; x-forefront-prvs: 0553CBB77A Content-Type: text/plain; charset="utf-8" Content-ID: <C00C6FA65358B9499865A358ABD7590B(a)namprd06.prod.outlook.com> MIME-Version: 1.0 X-OriginatorOrg: xad.com X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Apr 2015 22:25:37.5384 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 980bda08-f5bc-4d93-93e0-06e14b5a94a5 X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO2PR0601MB0951 X-Greylist: Sender succeeded STARTTLS authentication, not delayed by milter-greylist-4.3.9 (theraft.openend.se [89.233.217.130]); Wed, 22 Apr 2015 00:25:48 +0200 (CEST) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by theraft.openend.se id t3LMPjWl005823 X-DSPAM-Result: Innocent X-DSPAM-Processed: Wed Apr 22 00:26:07 2015 X-DSPAM-Confidence: 0.9993 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 5536ce7e58301256564919 Nope. Since I got an auto generated password, I can say the one I tried to use, which was “duhton” (without the quotes). Any other password also failed, including “1234” Leaving the password field blank just worked. Ben On 4/21/15, 12:39 PM, "Laura Creighton" <lac(a)openend.se> wrote: >In a message of Tue, 21 Apr 2015 19:22:41 -0000, Ben Jolitz writes: >>I opened a new tab and tried to subscribe with ben.jolitz(a)xad.com as my >>email address, only ASCII characters. >> >>Upon hitting the ŒSubscribe¹ form button, the browser goes to >>https://mail.python.org/mailman/subscribe/pypy-dev >>with the response HTML containing: >><h1>pypy-dev Subscription results</h1>You must GET the form before >>submitting it. >> >> >> >>And I figured out where you need to look. By omitting the ³Pick a >>password², ³Reenter password² fields on the subscribe form, Mailman >>successfully subscribes me. >> >>While I am now subscribed to the list, others may not become desperate >>enough to leave the password fields empty. >> >>Cheers, >>Ben > >Did you have non-ascii chars in the password you tried to use? > >Laura > ------- End of Forwarded Message

2 1

packages vs sources (was: Cron command?)
by Danil Smirnov April 21, 2015

April 21, 2015

2015-04-21 19:47 GMT+03:00 Mark Sapiro <mark(a)msapiro.net>: > This is a packager thing (RHEL/CentOS ?). Mailman as distributed by the > GNU Mailman project does not do this (never did). Our docs are > <http://www.list.org/mailman-install/node41.html> and recommend > installing our crontab as a user crontab with the crontab command. ... >> The bottom line is that it's best, as always, to install a component >> such as a crontab using the supplied tools rather trying to second-guess >> the tool set and copying files directly. > > +1 Many people rely on their distribution packagers - is this bad? I always prefer to use yum/apt-get instead of compiling software from source. The reasons are obvious (all they are in any package system mission statement). Mailman is one of the few exception of this rule on my servers because of importance of its new versions and rare packages updates. :( (It's shame that they include 2.1.15 in the new Centos7 distribution!) But if we 'use supplied tools' and lost distribution integration - like removing cron entries automatically when 'service mailman stop' - does this make sense at all? Danil

3 8

sync_members
by Marco Stoecker April 21, 2015

April 21, 2015

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi I have several mailing lists on a Mailman server which are synchronized with a database via a cronjob. Now my question: is it possible to not only synchronize the e-mail adresses but also the names? BR Marco -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBAgAGBQJVE9tLAAoJEC1y3OsA+e10PJIQAJaFxuLSFHjy7NJObs9B4U5i v/Yv2OdqR/RRN+5yRq9sUfOu8PUyXuXpdS7g67OgUID9PAueAEasnVQOHSjAgxD2 +ChRTp3wh8Aomfzr4UTqiflEcmW6BGE+I1xFxNd6KzdR24ampf2Vz7ogzkzM2HGB IK0tvTk9t9/IUKqedzf4lzsMFs4rTEIyuCUMje9IRwwIZVn/dCpjIfd+cbk0W6b1 tl1Mdd83vajzanf3ncLUG2/Sk8Cjm4kdHVYFQbT92jcR4wV+esjHBNClCDO41rJO JXb9/2bKd4C9XcRVP3Vz18mm3ogyn+C126TQLi1y+GauitqZqa+Yypjr76+C415D e4O2AVDbyRAkBSz/pSw07T4Og4pGjxUmGIM3WJZPDY01b9wSg8y5J7LaLbTZHS7F MbaPiZ6tQNQEmP6zxp40GRp//ZuWI6TBVhNAYnj3MuKROz0+pNjGprV83maYOCtp 9LX52d5Bkyc7WuAW8lFJ9OnxUWsTD0YcmNM3JXaEe5KAdJL1TI1rV7iMmQQy411a iXVWez1Q2OgQ7cnbw67kMOlkbtI9X5BRygDXO3TnvbiYV/tn//Rrzf9gKVUvc9Qt HK4vpINMF+0eBlg2lQGEh/b/C05UH5zVhK4t3fXNLSJ+8thxsLJz10S91ehuxgTH Plblbk7bIHBvT7OPxuXu =lpm4 -----END PGP SIGNATURE-----

2 7