Mailman 3 December 2016 - Mailman-Users

Re: [Mailman-Users] Mailman-Users Digest, Vol 154, Issue 30
by Glen Page Dec. 20, 2016

Dec. 20, 2016

We are a Google Apps for Education school so most of our employees and students are using gmail but with our own thet.net <http://thet.net/> domain. We have mx records for gmails servers and for our in house mailman server. Recently edited our DNS zones due to SPF record check failures. Also, recently had to change out IP block due to changes at our ISP. Here is the header info from a message that I got from our Dean. It got flagged as Spam somewhere along the way. It should be noted that some of the lists below are umbrella lists. {Spam?} [TA Admin] {Spam?} [Employees] {Spam?} [Claws] {Spam?} SNOWBALL IS CANCELLED FOR TONIGHT To: claws(a)lists.thet.net students2017(a)lists.thet.net X-Thetnet-Mailscanner-Information: Please contact the ISP for more information Sender: admin-bounces(a)lists.thet.net List-Archive: <http://lists.thet.net/mailman/private/admin/> Authentication-Results: mx.google.com; dkim=neutral (body hash did not verify) header.i=(a)thet-net.20150623.gappssmtp.com; spf=fail (google.com: domain of admin-bounces(a)lists.thet.net does not designate 104.219.98.14 as permitted sender) smtp.mailfrom=admin-bounces(a)lists.thet.net X-Received: by 10.55.20.95 with SMTP id e92mr9675564qkh.54.1481993433047; Sat, 17 Dec 2016 08:50:33 -0800 (PST) X-Received: by 10.13.204.67 with SMTP id o64mr6487069ywd.47.1481993249239; Sat, 17 Dec 2016 08:47:29 -0800 (PST) Return-Path: <admin-bounces(a)lists.thet.net> List-Help: <mailto:admin-request@lists.thet.net?subject=help> X-Original-To: admin(a)lists.thet.net X-Original-To: employees(a)lists.thet.net X-Original-To: claws(a)lists.thet.net X-Thetnet-Mailscanner-Spamscore: sssssss, sssssss, sssss, sssss X-Gm-Message-State: AKaTC03CGHzT3zezdGpZ3HNvRPiPVZelD2bKmhcA8Wn9WsDZT93E/DWWFFAFrbExpkGdZ0xWfYUPvqPLwJXAyg== List-Id: Interactive mailing list for TA Administrators <admin.lists.thet.net> X-Mailman-Version: 2.1.12 X-Greylist: whitelisted by SQLgrey-1.7.6 X-Google-Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=8F82G0kwQs0BGWAs4rc0JlbGrQ5jSEAp9BGHHsLlJGQ=; b=XDw9OtI9GY0saYUhV9g6nVzCeS2/FHyuJUbb3YrEZtrQAg+GOI9B1chbVDYuIDm9Ip EpVs8ERwixZfcbO+hRhz21h6dmm1kRorFGHjVKUjt9fOONcqX0C3i0FPy+VHgxf4nPnT 5wzEquSIGU7I5YoUNFK7AR6pqPCRXqEaS4t9Aa0Q9njL2Y2XEh+dw1z1e3XreibJMMr6 kYmbFTM6YcxBprB6XJCHzVI4R51a9L2CmxJCHn8X+ULXsligpbAIr8vnMxT8QjAxejM6 A1kiQZG57hSs4B/8R8TQeX3jj2QpF1XULvdkLgxDlskybV2LdQP2tTpDf9aI0TnXO+bg ralw== X-Thetnet-Mailscanner-Spamcheck: spam, SORBS-SPAM, SpamAssassin (cached, score=7.315, required 5, BAYES_00 -1.90, DNS_FROM_AHBL_RHSBL 2.70, HTML_MESSAGE 0.00, RCVD_IN_DNSWL_NONE -0.00, SORTED_RECIPS 2.50, SUBJ_ALL_CAPS 1.51, SUSPICIOUS_RECIPS 2.51), spam, SpamAssassin (cached, score=7.315, required 5, BAYES_00 -1.90, DNS_FROM_AHBL_RHSBL 2.70, HTML_MESSAGE 0.00, RCVD_IN_DNSWL_NONE -0.00, SORTED_RECIPS 2.50, SUBJ_ALL_CAPS 1.51, SUSPICIOUS_RECIPS 2.51), spam, SpamAssassin (not cached, score=5.809, required 5, BAYES_00 -1.90, DNS_FROM_AHBL_RHSBL 2.70, HTML_MESSAGE 0.00, RCVD_IN_DNSWL_NONE -0.00, SORTED_RECIPS 2.50, SUSPICIOUS_RECIPS 2.51), spam, SpamAssassin (not cached, score=5.809, required 5, BAYES_00 -1.90, DNS_FROM_AHBL_RHSBL 2.70, HTML_MESSAGE 0.00, RCVD_IN_DNSWL_NONE -0.00, SORTED_RECIPS 2.50, SUSPICIOUS_RECIPS 2.51) X-Thetnet-Mailscanner: Found to be clean, Found to be clean, Found to be clean, Found to be clean List-Post: <mailto:admin@lists.thet.net> Errors-To: admin-bounces(a)lists.thet.net Message-Id: <CACaqBRtUd-HAaOF54gcWrQQffha6q3gMQVbnEcrMnZvNGFikjg(a)mail.gmail.com> X-Spam-Status: Yes, Yes, Yes, Yes X-Thetnet-Mailscanner-From: admin-bounces(a)lists.thet.net Mime-Version: 1.0 Precedence: list Received: by 10.80.136.105 with SMTP id c38csp743701edc; Sat, 17 Dec 2016 08:50:33 -0800 (PST) Received: from dispatch.thet.net ([104.219.98.14]) by mx.google.com with ESMTPS id n185si342354qke.282.2016.12.17.08.50.32 (version=TLS1 cipher=AES128-SHA bits=128/128); Sat, 17 Dec 2016 08:50:32 -0800 (PST) Received: from dispatch.thet.net (dispatch.thet.net [172.16.0.18]) by dispatch.thet.net (Postfix) with ESMTP id A1013E6103A; Sat, 17 Dec 2016 11:49:56 -0500 (EST) Received: from dispatch.thet.net (dispatch.thet.net [172.16.0.18]) by dispatch.thet.net (Postfix) with ESMTP id BA586E61035; Sat, 17 Dec 2016 11:49:04 -0500 (EST) Received: from dispatch.thet.net (dispatch.thet.net [172.16.0.18]) by dispatch.thet.net (Postfix) with ESMTP id 12323E60FF7; Sat, 17 Dec 2016 11:48:05 -0500 (EST) Received: from mail-yw0-f177.google.com (mail-yw0-f177.google.com [209.85.161.177]) by dispatch.thet.net (Postfix) with ESMTPS id 0F6F3E60FF7 for <claws(a)lists.thet.net>; Sat, 17 Dec 2016 11:47:29 -0500 (EST) Received: by mail-yw0-f177.google.com with SMTP id i145so46776688ywg.2 for <claws(a)lists.thet.net>; Sat, 17 Dec 2016 08:47:29 -0800 (PST) Received: by 10.37.30.86 with HTTP; Sat, 17 Dec 2016 08:47:28 -0800 (PST) Content-Type: multipart/mixed; boundary="===============0140925220==" X-Thetnet-Mailscanner-Id: A1013E6103A.A0BA7 Delivered-To: glen.page(a)thet.net.test-google-a.com Delivered-To: admin(a)lists.thet.net Delivered-To: employees(a)lists.thet.net Delivered-To: claws(a)lists.thet.net X-Beenthere: claws(a)lists.thet.net X-Beenthere: employees(a)lists.thet.net X-Beenthere: admin(a)lists.thet.net Received-Spf: fail (google.com: domain of admin-bounces(a)lists.thet.net does not designate 104.219.98.14 as permitted sender) client-ip=104.219.98.14; List-Unsubscribe: <http://lists.thet.net/mailman/options/admin> List-Unsubscribe: <mailto:admin-request@lists.thet.net?subject=unsubscribe> List-Subscribe: <http://lists.thet.net/mailman/listinfo/admin>, <mailto:admin-request@lists.thet.net?subject=subscribe> Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thet-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=8F82G0kwQs0BGWAs4rc0JlbGrQ5jSEAp9BGHHsLlJGQ=; b=z4aCN7tqgI6/fqyUS0996YyJ3h9vBdciKFZDMciilUXU1d1VzpD9MPEw5iFzTvTiBk JboPNIV4zE41HWJcMRL3FIJ2A9ahgpkAD+p48PIxjqveclm4BM92Ioj3LXqrXg6lLs+Q SkqLIEl6DQLzWigaixP49UmPqbQjSbfxLvxq32MXFVldcOF7n/5Q1SfFQkErRq8S14x8 U1Keu94MZCSi2xp7bXj4ARdtdOsOOemWCRRSzrAd0nR+uqsW+aOKPHmqYZqHHz3Ct328 XH+wBOs/CUSe7sOrQCM/RlHb2IQg0rTS0t3V3jhZkYaquDF59rgTYsNyo7BEToSeXDfV QuOg== > > From: Lindsay Haisley <fmouse(a)fmp.com> > Subject: Re: [Mailman-Users] list mail increasingly flagged as spam > Date: December 19, 2016 at 11:01:11 AM EST > To: mailman-users(a)python.org > Reply-To: fmouse(a)fmp.com > > > On Mon, 2016-12-19 at 07:52 -0500, Glen Page wrote: >> I have recently begun to see (and get complaints from some of my >> users) our list messages being flagged on many users end as spam >> messages. Wondering if there is anything that i can do on our end to >> decrease the likelyhood of our messages being flagged as spam. If it >> would help, I can send some header info from some of our messages. > > I'm not a Mailman maintainer, but it might be helpful if you could post > any information that would help narrow down the problem. Specifically, > are most or all of the users who have this problem using a particular > mail provider such as Gmail, or some other service? Have any of these > users posted any information to you regarding the reason their mail > service has improperly flagged these list posts? > > -- > Lindsay Haisley | "Everything works if you let it" > FMP Computer Services | > 512-259-1190 | --- The Roadie > http://www.fmp.com | > > > > > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users(a)python.org > https://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/ Glen Page Director of Information Technology ThetNet - Thetford Academy 802.785.4805.x231 Every time it rains pennies from heaven, I get down on my hands and knees and try to protect my head because those things really hurt.

3 4

list mail increasingly flagged as spam
by Glen Page Dec. 20, 2016

Dec. 20, 2016

I have recently begun to see (and get complaints from some of my users) our list messages being flagged on many users end as spam messages. Wondering if there is anything that i can do on our end to decrease the likelyhood of our messages being flagged as spam. If it would help, I can send some header info from some of our messages. TIA, Glen Page Director of Information Technology ThetNet - Thetford Academy 802.785.4805.x231 Engelbart's creed: "The better we get, the better we get at getting better."

3 2

Mailman3: HTTP-500, create_http_method_map(resource, None, None) ?
by Sim Dec. 18, 2016

Dec. 18, 2016

Hello List, I was following the [mailman-bundler](https://gitlab.com/mailman/mailman-bundler/) installation instructions. After starting Django for the first time (before changes to the Postfix configuration and without any pre-existing lists) I received an HTTP-500 from http://127.0.0.1:8000/mailman3. Traceback (most recent call last): File "/usr/lib/python3.4/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/opt/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/database/transaction.py", line 57, in wrapper rtn = function(*args, **kws) File "/opt/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/rest/wsgiapp.py", line 65, in __call__ environ, start_response) File "/opt/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/falcon/api.py", line 180, in __call__ responder, params, resource = self._get_responder(req) File "/opt/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/rest/wsgiapp.py", line 135, in _get_responder method_map = create_http_method_map(resource, None, None) TypeError: create_http_method_map() takes 1 positional argument but 3 were given ERROR Internal Server Error: /mailman3/ To make it work I changed In file venv-3.4/lib/python3.4/site-packages/mailman/rest/wsgiapp.py: method_map = create_http_method_map(resource, None, None) into method_map = create_http_method_map(resource) Is this a bug or should I have created an initial list from the command line (similar to Mailman 2) before accessing this page? Simon

2 1

Malfunction of our mailing list
by support＠aedeba.org Dec. 18, 2016

Dec. 18, 2016

Hello everyone. The normal operation of our mailing list was such that when you post a message, you get yourself a copy of the message. Currently, when you post a message, you receive no copies. You do not know if the members got the message. Can you help me? Please Andre DZEUGANG

2 1

logfiles description
by Dave Stevens Dec. 17, 2016

Dec. 17, 2016

I see logfiles in /var/log/mailman/en but it isn't obvious (or not obvious enough anyway) what they all do. The wiki doesn't appear to describe them, can anyone refer me? D -- Reporter to Mahatma Ghandi after his tour of east London "What do you think of western civilization, Mr. Ghandi?" Ghandi - "I think it would be an excellent idea!"

2 2

Does changing MX impact Mailman 2.1 processing?
by Florian Berger Dec. 17, 2016

Dec. 17, 2016

Hi! My email + mailman provider had a server crash and is migrating all mail services to a different hardware. There is a temporary SMTP server up collecting incoming mail, but they are held and not propagated until the whole system runs again. Since that timeframe is unknown, I am thinking about pointing the MX record for the affected domain to an own cold-standby backup server. Question: will the Mailman 2.1 on the old system, once fed with the already accepted mails, correctly deliver these to the recipients *even* if the list domain's MX record points somewhere else? I.e. is Mailman 2.1 in any way dependent on DNS MX record resolving of its own domain *after* mail has already been accepted my an MTA? (I do not know the details of the Mailman installation, and my provider should be the first to be asked, and I did. I'd still value a shot-in-the-dark third opinion.) Thanks, Florian

2 1

cgi wrappers not properly executing
by John Covici Dec. 16, 2016

Dec. 16, 2016

Hi. I am using mailman 2.1.23 on a gentoo system. I run in to the following problem: When I try to do anything on the web, I get permission denied error on /var/lib/mailman/logs/error . If I then make that file world read/write, I get permission denied error on config.pck of the list I am trying to access. Now, everything under /var/lib/mailman is owned by mailman.mailman and the cgi wrappers are all like the following: -rwxr-sr-x 1 mailman mailman 10512 Nov 16 12:45 /usr/lib/mailman/cgi-bin/admin Check_perms says no problems. I am using apache 2.4.23 and here is what loads with mailman ScriptAlias /mailman/ "/usr/lib/mailman/cgi-bin/" <Directory "/usr/lib/mailman/cgi-bin/"> Options +execcgi require all granted </Directory> Alias /pipermail/ "/var/lib/mailman/archives/public/" <Directory "/var/lib/mailman/archives/public/"> AllowOverride None Options ExecCGI FollowSymLinks require all granted </Directory> #namevirtualhost lists.ccs.covici.com <VirtualHost *:80> DocumentRoot /var/www ServerName lists ServerAlias lists.* UseCanonicalName Off ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/ Alias /icons/ /usr/lib/mailman/icons/ Alias /pipermail/ /var/lib/mailman/archives/public/ <Directory /var/lib/mailman/archives/> Options FollowSymLinks </Directory> <Directory "/usr/lib/mailman/cgi-bin/"> Options +execcgi require all granted </Directory> </VirtualHost> Any assistance will be greatly appreciated. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici covici(a)ccs.covici.com

2 5

bin/genaliases not generating aliases?
by Caesar Samsi Dec. 16, 2016

Dec. 16, 2016

Hi Mark, I’m attempting an install from scratch on a new server. It has virtual domain configured postfix. I’ve completed http://www.gnu.org/software/mailman/mailman-install/node12.html <http://www.gnu.org/software/mailman/mailman-install/node12.html> (Using Postfix server) I’m attempting to complete http://www.gnu.org/software/mailman/mailman-install/postfix-integration.html <http://www.gnu.org/software/mailman/mailman-install/postfix-integration.html> (Integrating Postfix and Mailman) When I do: Run the bin/genaliases script to initialize your aliases file. % cd /usr/local/mailman % bin/genaliases I’m assuming the aliases would be generated in /usr/local/mailman/data, but they aren’t What to do? I’m running LinuxMint 18 Sarah (Ubuntu flavor). Thanks, Caesar.

4 16

distutils is not available or incomplete when ./configure mailman 2.1.23?
by Caesar Samsi Dec. 14, 2016

Dec. 14, 2016

Hi, When I run configure like this: ./configure --prefix=/var/lib/mailman --with-username=list --with-groupname=list --with-cgi-gid=www-data --with-mail-gid=list --with-mailhost=YOUR.EMAIL.DOMAIN --with-urlhost=YOUR.WEB.DOMAIN A few lines later I get: … checking that Python has a working distutils... configure: error: ***** Distutils is not available or is incomplete for /usr/bin/python ***** If you installed Python from RPM (or other package manager) ***** be sure to install the -devel package, or install Python ***** from source. See sec. 15.1 of the Installation Manual for ***** details What am I missing? Thank you, Caesar.

3 7

Re: [Mailman-Users] Root URL / vs /listinfo?
by Mark Sapiro Dec. 14, 2016

Dec. 14, 2016

On 12/12/2016 02:39 PM, Caesar Samsi wrote: > When you go to http://mail.mydomain.com/, where do you wind up? I.e., > whats the URL in the address bar of your browser, and is the resultant > page an actual page or a 404? > > I end up at https://mail.mydomain.com/listinfo Which is correct, right? > What happens if you go to https://mail.mydomain.com/? > > I end up at https://mail.mydomain.com/ And you want to end up at https://mail.mydomain.com/listinfo, right. The probable answer to that is you are doing the redirect from http://mail.mydomain.com/ to http://mail.mydomain.com/listinfo before the redirect from http to https. See below. > In /etc/apache2/sites-available I have mailman.con which contains a number of redirects as follows: > > <VirtualHost *:80> > ServerName mydomain.us > ServerAdmin gigs(a)amydomain.com > Redirect / https://mydomain.us/ > </VirtualHost> So going to http://mydomain.us/... will redirect to https://mydomain.us/... > <VirtualHost *:80> > ServerName www.mydomain.us > ServerAdmin gigs(a)amydomain.com > Redirect / https://mail.mydomain.us/ > </VirtualHost> And going to http://www.mydomain.us/... will redirect to https://mail.mydomain.us/... > <VirtualHost *:80> > ServerName mail.mydomain.us > ServerAdmin gigs(a)mydomain.com > Redirect / https://mail.mydomain.us And going to http://mail.mydomain.us/... will redirect to https://mail.mydomain.us/... > ErrorLog /var/log/apache2/mailman-error.log > CustomLog /var/log/apache2/mailman-access.log combined > > <Directory /var/lib/cgi-bin/mailman> > Options FollowSymLinks > AllowOverride All > Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch > Require all granted > </Directory> > > </VirtualHost> > > and aliases as follows: > > Alias /AUP /var/www/html/AUP > Alias /pipermail/ /var/lib/mailman/archives/public/ > Alias /postfixadmin /var/www/html/postfixadmin > Alias /roundcube /var/www/html/roundcube > Alias /images/mailman/ /usr/share/images/mailman/ > ScriptAlias /admin /usr/lib/cgi-bin/mailman/admin > ScriptAlias /admindb /usr/lib/cgi-bin/mailman/admindb > ScriptAlias /confirm /usr/lib/cgi-bin/mailman/confirm > ScriptAlias /create /usr/lib/cgi-bin/mailman/create > ScriptAlias /edithtml /usr/lib/cgi-bin/mailman/edithtml > ScriptAlias /listinfo /usr/lib/cgi-bin/mailman/listinfo > ScriptAlias /options /usr/lib/cgi-bin/mailman/options > ScriptAlias /private /usr/lib/cgi-bin/mailman/private > ScriptAlias /rmlist /usr/lib/cgi-bin/mailman/rmlist > ScriptAlias /roster /usr/lib/cgi-bin/mailman/roster > ScriptAlias /subscribe /usr/lib/cgi-bin/mailman/subscribe > ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/ > ScriptAlias / /usr/lib/cgi-bin/mailman/listinfo So it appears you are relying on ScriptAlias / /usr/lib/cgi-bin/mailman/listinfo to get to the listinfo page from an http(s)://host/ url. Aside from the fact that this isn't a redirect which would explain why when you go to https://mail.mydomain.com/ the address you wind up at is still https://mail.mydomain.com/ (but is it in fact the listinfo page?), it seems very bad because it means that going to any URL like http(s)://host/something, where 'something' is anything that doesn't match one of the preceding Alias or ScripAlias directives will invoke the script /usr/lib/cgi-bin/mailman/listinfosomething that doesn't exist, and even if you made it ScriptAlias / /usr/lib/cgi-bin/mailman/listinfo/ It would still invoke the script /usr/lib/cgi-bin/mailman/listinfo/something which will probably give a "No such list something" error on the returned listinfo page with http(s)://host/something still in the browser's address bar. Further, this doesn't explain how http://mail.mydomain.com/ redirects to http://mail.mydomain.com/listinfo before redirecting to https. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 2