Mailman 3 December 2017 - Mailman-Users

changing domains on Mailman implementation
by Keith Seyffarth Sept. 20, 2018

Sept. 20, 2018

Is there an efficient way to change the domain name that mailman is affiliated with? I have two mailing lists that were created for an organization before that organization had their own domain. At the time the organization was sure they did not want their own domain and would not be getting a domain. Since then, they have chosen to get a domain and set up a web site. I would like to move their mailing lists onto their domain. It looks like the process for this is: 1) get the list of subscribers 2) delete the mailing list from the one domain (losing the archives) 3) create the mailing list on the new domain 4) subscribe the list of subscribers This process doesn't seem too difficult, but I would prefer to keep the archives, if possible. Both domains are on the same server, running CentOS7 and PLESK 12.5, if that makes a difference. Thanks, Keith

2 2

spam discard expressions
by Jim Dory March 8, 2018

March 8, 2018

Apparently our host provider performs spam tests only on outgoing, rather than incoming - since my spamassassin blacklists don't have any effect. So I've discovered the filters offered in Mailman after being completely buried by spammers trying to post to our subscriber only list. I've started putting these in Sender Filters: ^[^@]+@bcira\.com$ ^[^@]+@airablo\.com$ ^[^@]+@bfklaw\.com$ ^[^@]+@bettella\.com$ ^[^@]+@areallycool\.com$ ^[^@]+@aristo-tec\.com$ ^[^@]+@benallgood\.com$ ^[^@]+@al-meshkah\.com$ ^[^@]+@atoccs\.stream$ ^[^@]+@authors\.com$ ^[^@]+@aulson\.com$ ^[^@]+@atmyx\.bid$ ^[^@]+@airtecperforms\.com$ but what is the syntax for blocking domains ending in .loan .stream .trade etc, other than .com. I've been reading up on python expressions but at first reading it is a bit overwhelming - hoping for a simple example. I've also started adding in words under Spam filters such as: ^Subject: .*Phentermine ^Subject: .*F\*buddy ^Subject: .*H00kup ^Subject: .*InstaF\*ck ^Subject: .*Instacheat Wondering if anyone would care to share their lists of filters - or a good resource? thanks, Jim

6 10

options for dealing with DMARC
by Jordan Brown Jan. 16, 2018

Jan. 16, 2018

I've been running my mailing list for a few years with "Munge From" to defend against DMARC rejection. This means that my messages get From: Joe User <mymailinglist(a)mydomain.com> Reply-To: Joe User <joe(a)example.com> That mostly works, but sometimes confuses people a bit, and just now I've had somebody send what I think was intended as a private address to that From line, not to the Reply-To line. (I think their e-mail client, Pegasus, has an excessively flexible policy on which headers to use for a reply and may be subtly misconfigured, but maybe they just naively copied the From line.) That's leading me to wonder whether there's another way, whether I can leave From alone and still get past the DMARC checks. Wikipedia tells me that DMARC passes if either SPF *or* DKIM passes. There's no hope for SPF with the original sender in From, because the mailing list server isn't the user's mail server. However, DKIM seems like it *might* pass, if I'm careful in how I configure the mailing list. In particular, it looks like I'd have to get rid of the message footer. That would be OK. Looks like I might also have to kill off the [ListName] addition to the Subject, which is less OK but might be better than the alternative. Before I go recruit a couple of users from several DMARC-using providers and run some tests, can anybody tell me if there is any hope there, and maybe share some configuration tips?

5 9

importing large (1GB) mbox file, hitting a wall here..
by Andrew White, PhD Dec. 29, 2017

Dec. 29, 2017

First post- thanks much for your archives, been getting myself up to speed today and I hope to be a member of the community who gives back as well. I took over a large mailing list with a 12 year archive, which is about a 1 GB .mbox file (about 35,000 messages). I need to upload it to a new Mailman install on a new server. I have a background in visual basic and command line SPSS, and have managed Mailman lists before, but I'm a little new on this part. Here's where I'm at- let me know where I'm off. For reference, the name of the list on the machine is dbt-l_pdbti.org. Per the FAQ ( [1]https://wiki.list.org/DOC/How%20do%20I%20import%20an%20archive%20into%20a… ), I uploaded the old .mbox into the correct folder (in this case archives/private/dbt-l_pdbti.org.mbox/). This is a brand new list install, with no posts. I then ran bin/arch --wipe dbt-l_pdbti.org. When I checked the archives, only about 11,000 messages were imported. I saw in the arch help file there can be memory issues, and so to run things in chunks. So, I did this: bin/arch ---wipe q -s 0 e 10000 dbt-l_pdbti.org bin/arch -q -s 10001 e 20000 dbt-l_pdbti.org bin/arch q -s 20001 e 30000 dbt-l_pdbti.org bin/arch q -s 30001 e 40000 dbt-l_pdbti.org So when I do this, each piece works, but each piece overwrites the previous- in other words, rather than each chunk adding into the archives, only the most recent command seems to affect the archives. At the end of these commands, only messages 30,000 to 35,000 are showing up in the archives. I'm sure there is something I'm doing wrong here, but I'm feeling pretty stuck- is there something I'm leaving out? Appreciate the help- ........................................................................ Andrew White, PhD Associate Director DBT-Linehan Board of Certification, Certified DBT Clinician* Licensed Clinical Psychologist Portland DBT Institute (503) 290.3281 (phone) (503) 231.8153 (fax) Please be aware that e-mail communication can be intercepted in transmission or misdirected. This e-mail message and any documents attached to it are confidential and may contain information that is protected from disclosure by various federal and state laws, including the HIPAA privacy rule (45 C.F.R., Part 164). This information is intended to be used solely by the entity or individual to whom this message is addressed. If you are not the intended recipient, be advised that any use, dissemination, forwarding, printing, or copying of this message without the sender's written permission is strictly prohibited and may be unlawful. Accordingly, if you have received this message in error, please notify the sender immediately with a copy to hipaa(at)pdbti.org and destroy this message. Please do not include personal identifying information such as your birth date, or personal medical information in any emails you send to us. No one can diagnose your condition from email or other written communications and is not a reliable mechanism for emergency communication. References Visible links 1. https://wiki.list.org/DOC/How%20do%20I%20import%20an%20archive%20into%20a%2…

2 5

Re: [Mailman-Users] Yahoo problems again
by Russell Clemings Dec. 23, 2017

Dec. 23, 2017

FWIW, last month on another list a Yahoo/AOL rep said it means an inactive account. Which is not exactly the same as an account that doesn't exist, I guess. https://www.mail-archive.com/mailop@mailop.org/msg05018.html On Fri, Dec 22, 2017 at 9:00 AM, <mailman-users-request(a)python.org> wrote: > From: Mark Sapiro <mark(a)msapiro.net> > To: mailman-users(a)python.org > Cc: > Bcc: > Date: Thu, 21 Dec 2017 16:18:18 -0800 > Subject: Re: [Mailman-Users] Yahoo problems again > On 12/21/2017 03:14 PM, Jim Dory wrote: > > I'm running a CPanel version of mailman. > > I've been seeing a lot of the following errors of mostly yahoo.com users > > but a few other providers as well. > > > > "---------- Forwarded message ---------- > > From: Mail Delivery System <Mailer-Daemon(a)server.nomekennelclub.com> > > To: nome-announce-bounces(a)nomekennelclub.com > > Cc: > > Bcc: > > Date: Thu, 21 Dec 2017 17:22:05 +0000 > > Subject: Mail delivery failed: returning message to sender > > This message was created automatically by mail delivery software. > > > > A message that you sent could not be delivered to one or more of its > > recipients. This is a permanent error. The following address(es) failed: > > > > xxxx(a)yahoo.com > > host mta7.am0.yahoodns.net [98.137.159.27] > > SMTP error from remote mail server after end of data: > > 554 delivery error: dd Requested mail action aborted - > > mta4357.mail.ne1.yahoo.com > > > > Action: failed > > Final-Recipient: rfc822;xxx(a)yahoo.com > > Status: 5.0.0 > > Remote-MTA: dns; mta7.am0.yahoodns.net > > Diagnostic-Code: smtp; 554 delivery error: dd Requested mail action > aborted > > - mta4357.mail.ne1.yahoo.com > > " > > > > followed by a forwarded message that had been sent to the list by another > > user. > > -which I don't know how to deal with. > > > This is a Yahoo glitch. They are reporting a bogus reason for a list > message to a Yahoo address that doesn't exist. See > <https://forums.yahoo.net/t5/Delivery-errors-5xx-and-421/554 > -delivery-error-dd-Requested-mail-action-aborted-mta1240-mail/td-p/382749> > > > >

2 1

Yahoo problems again
by Jim Dory Dec. 22, 2017

Dec. 22, 2017

I'm running a CPanel version of mailman. I've been seeing a lot of the following errors of mostly yahoo.com users but a few other providers as well. "---------- Forwarded message ---------- From: Mail Delivery System <Mailer-Daemon(a)server.nomekennelclub.com> To: nome-announce-bounces(a)nomekennelclub.com Cc: Bcc: Date: Thu, 21 Dec 2017 17:22:05 +0000 Subject: Mail delivery failed: returning message to sender This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: xxxx(a)yahoo.com host mta7.am0.yahoodns.net [98.137.159.27] SMTP error from remote mail server after end of data: 554 delivery error: dd Requested mail action aborted - mta4357.mail.ne1.yahoo.com Action: failed Final-Recipient: rfc822;xxx(a)yahoo.com Status: 5.0.0 Remote-MTA: dns; mta7.am0.yahoodns.net Diagnostic-Code: smtp; 554 delivery error: dd Requested mail action aborted - mta4357.mail.ne1.yahoo.com " followed by a forwarded message that had been sent to the list by another user. -which I don't know how to deal with. And also, I just had a yahoo user try to send something to the list and he was completely blocked: "From: Mail Delivery System <Mailer-Daemon(a)server.nomekennelclub.com> Date: December 21, 2017 at 10:55:27 AM AKST To: yyyy(a)yahoo.com Subject: Mail delivery failed: returning message to sender This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: me(a)dorydesign.com (generated from nomeannounce(a)nomekennelclub.com) host mx1.arandomserver.com [208.43.240.3] SMTP error from remote mail server after end of data: 550 High probability of spam Action: failed Final-Recipient: rfc822;me(a)dorydesign.com Status: 5.0.0 Remote-MTA: dns; mx1.arandomserver.com Diagnostic-Code: smtp; 550 High probability of spam " The attached mime from that message was this (I've tried to obscure the email addresses in these examples): Return-path: <yyyy(a)yahoo.com> Received: from se001.arandomserver.com ([207.210.220.219]:42974) by server.nomekennelclub.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from <yyyy(a)yahoo.com>) id 1eS6w8-0005XI-5V for nomeannounce(a)nomekennelclub.com; Thu, 21 Dec 2017 19:55:24 +0000 Received: from sonic306-2.consmr.mail.bf2.yahoo.com ([74.6.132.41]) by se001.arandomserver.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <yyyy(a)yahoo.com>) id 1eS6vT-0006g3-7Y for nomeannounce(a)nomekennelclub.com; Thu, 21 Dec 2017 13:54:43 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1513886082; bh=oAG+Vx42je2VW+88C4FZSQH+Yw6Qb4GSG+M2O1+tDyc=; h=From:Subject:Date:To:From:Subject; b=Xcfo3BhyCiYF0RUBYPratRWoint9KVpgawUavGEI41YTWaESeLOyfRCAlFrNuVMbrNUKM8aAo49oYN9VlKqYjGY7oqHoZa1hEm8MsxW2K7x73NoiUIjShUvfCA6IrNqEHz3h2HtoJGC27nF5JP9AqVjroXOy9f7AIugKL0sWlH1Duz3d0MKFmeg6BNRHp4HliFb8zbvey/8zAuVoE8Unh1rZp2zY1DQYEwQqg4HcFlzY6P9ZaAzkMWF692PIa7JSz1gD2zw0BWhi1MQOlRigWsMkOJBK0ia2QRTDgzRMsdQ1zc/iOi16YXUIVddPvRuNjk2prx2ojrdZiQeD9jZ/ww== X-YMail-OSG: uvH4Z2EVM1kqMXtalwJ6oTN1d5zS2x6GWBYuwiJt9FyjfYi0ji89oNPJ78BmCkW PfZgicNYSHDBf2svIrXgPXOTBZt6zMqTngoNNyPlVb38SVZdf5MHcMDpVFHrRTZ.e0bMy4SS2jCZ VNrnPuskvvg5TaAw39nxkWuQLNPhVVix6kT_o4Nn5fNGPn1WFbC3CJAlJvWs0.Re6ZwrmdhIqZzs _8sg4YH3gBSS4i9oVcuAOsrI_bqZwH56KnE8_ICkPS9d9y3uRFBOriBOiKQYdNKve8AKBBWFSjJi b.Z._BNpLNrz1LGAD_paOegr8hvOvWBUrwee5bsfXuY0tOpe96R.PtbLlRmKM_9H8D0W3OsC3R0k L7ts11xugZRbxsOlJt8wQqsBOsdVN9AREERluLjuYt6Yu9GumXYjHVb7cUH_Hl5xwFLHQ6AfpVXV IgCJohmz2iU1paZD0vg0ARqlxHF5qtNJZ82qDfjRtDCGIkS56rv35.1LvqIzIW1aMgn8BQECi6XV dp_6S Received: from sonic.gate.mail.ne1.yahoo.com by sonic306.consmr.mail.bf2.yahoo.com with HTTP; Thu, 21 Dec 2017 19:54:42 +0000 Received: from smtp127-mob.biz.mail.bf1.yahoo.com (EHLO [10.126.186.15]) ([98.139.172.251]) by smtp408.mail.bf1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID 52a4c2265a6e8c2eb991fbaec30e880c for <nomeannounce(a)nomekennelclub.com>; Thu, 21 Dec 2017 19:54:39 +0000 (UTC) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii From: Timothy Smith <yyyy(a)yahoo.com> Mime-Version: 1.0 (1.0) Subject: Looking for old snowplow Message-Id: <72E67804-9C39-4648-B54A-355A1CD91A83(a)yahoo.com> Date: Thu, 21 Dec 2017 10:54:36 -0900 To: nomeannounce(a)nomekennelclub.com X-Mailer: iPhone Mail (14G60) Received-SPF: pass (se001.arandomserver.com: domain of yahoo.com designates 74.6.132.41 as permitted sender) client-ip=74.6.132.41; envelope-from= yyyy(a)yahoo.com; helo=sonic306-2.consmr.mail.bf2.yahoo.com; X-SPF-Result: se001.arandomserver.com: domain of yahoo.com designates 74.6.132.41 as permitted sender Authentication-Results: se001.arandomserver.com; dmarc=pass header.from= yahoo.com Authentication-Results: arandomserver.com; spf=pass smtp.mailfrom= yyyy(a)yahoo.com; dkim=pass header.i=yahoo.com X-SpamExperts-Class: whitelisted X-SpamExperts-Evidence: sender X-Recommended-Action: accept X-Filter-ID: PqwsvolAWURa0gwxuN3S5dbLZBtEelHx626yyIFROGBoq7PC935D5gVVZdRAS4cpe2lzoh2cHLtu 1SqMOIQTJhg2bPqsF3NKVeRdIq6+m8hAMDzeDPgTbattB4dzugM/GAAHuU7Kix/q2NhXWYORrd1x l5D7ORax3H8jyTz96hP+lczXWRsecrL6KZmV4jaidG5gGLSgW4Bn/5M0JETfQd7usy1SiXvhjHr/ TSF/Xh+FcqCQR+qeCjyt4VgXy9au/V2g4NFXKjiWEq6AptiBOZ0DJh9EsOc01tOOj/R6OcliBP5d I2uVKl4iqs7slFv2rNU9pgrR2527oymQ/UGyCfdQO3rhq0nW47cN5z+mpmD4G4szLADW4wW12QfH F7cITI2it2spocGAwh4WoxJReeWBOXp8nHKe0R+FkIqN7hnb2h17GFq7RyA5TlS+SepcaldRuW5H Z5VCz3oI8G6gg5uymjpsIKEGfL1NrbMEQvkYAAe5TsqLH+rY2FdZg5Gt3XGXkPs5FrHcfyPJPP3q E/n1AS6Vvbdi/Ytm8JblH86XTVJp/Vp1c6oRqL12g/4d+n4K/vAYO0wLn77ziAlxt3ZAfdGUK6xm xt3uoWu7latyV9A8fT7KxsMfMjFtkNpsOi+G2wty43cRSQ8qLbbzwKE/uv+p4Jwt80+TCbaU2ezd u108kaQJKXxbTO451NNAah/EURL1xtLvrMfFXIdIhByeP3kMF/HM2qi7bXBmBn9TEFgSWr/NHmgi bYOxhTAHAGpU1KrPVLcYGHrgyo25Xfvg7iEFLP+SSY+Av5+AiC5DA8QlLMss9wAh0997AWd7Poec lVMMg4omr0qmP8EG27tPLjMU/DCffyE9gEZuU8cySBvQ55du5dUCC09Y9ZczQ9OVVyXpqvfcPEJW mcaNuHQgpgHO7UCv07taZADhvKZIv0iLmzKdXyIb0q0eJBBHDdjre9h1YQfOlkxOVd0feQ== X-Report-Abuse-To: spam(a)se001.arandomserver.com I'm in search of old snowplow blades, parts, frames, pumps etc. to rebuild. = This would be for a truck or jeep. I'm not interested in ATV plows.=20 Please reply if you have anything for me to look at.=20 Thanks, Tim Sent from my iPhone=

2 1

I have Google recaptcha V2 working on mailman 2.1.23
by Runner Dec. 19, 2017

Dec. 19, 2017

I am running mailman version 2.1.23. A while back I configured google’s recaptcha v1 on a mailman server to stop subscription abuse. I used the instructions provided here: https://www.dragonsreach.it/2014/05/03/adding-recaptcha-support-to-mailman/ Google announced that recaptcha v1 will end sometime in March 2018. I could not find any instructions for implementing recaptcha v2 with mailman so I took a deep dive into what was required. I set up a test Ubuntu 16.04 server and figured it out. I have no python programming experience so some aspects of this process do not follow best practices. If any of you are experienced at python programming and you have the time, I would appreciate it if you would provide some guidance on how to improve these instructions. There are two areas that need cleaning up. The first one is how to install requisite python modules so they are all located in one nice neat location. In my instructions below I had to add five sys.path.append statements so python could find the extra python modules. This is sloppy. Second, I do not know how to reference a variable from inside a web page template where the variable is defined in mm_cfg.py. For now I just hard coded it but it’s not elegant. These two question are python issues and not really mailman issues. So, for those of you who are running mailman v 2.1.23 (or something close) and you want to enable Google recaptcha v2, here is what I did: Environment Ubuntu 16.04 Mailman 2.1.23 Python 2.7.12 *** Install prerequisite python modules *** The server I tested with was a basic Ubuntu 16.04 install. I had to manually install the following software: sudo apt-get install python-dnspython sudo apt-get install python-distutils-extra sudo apt-get install python-setuptools sudo apt-get install python-dev sudo apt-get install build-essential sudo apt-get install python-requests Manually install these python modules using the command "python setup.py install" inside the source code directory: orderedmultidict furl recaptcha2 ( available at https://pypi.python.org/pypi/recaptcha2/0.1 ) *** Modify the listinfo.html file located at MAILMAN_HOME/templates/en/listinfo.html (assuming you are using English) *** Locate the </HEAD> tag and add this line above it: <script src='https://www.google.com/recaptcha/api.js'></script> Locate the <mm-digest-question-end> tag and add the following lines below it: <tr> <td BGCOLOR="#dddddd">Please fill out the following captcha</td> <td><div class="g-recaptcha" data-sitekey="ABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890"></div></td> </tr> NOTE: Use your own google public key for data-sitekey above. The better way to do this would be to add your public key to mm_cfg.py and reference that variable inside this file. When I have more time I will figure out how to do this and update the directions. *** Add your google recaptcha public and private keys to MAILMAN_HOME/Mailman/mm_cfg.py *** Append them to the end of the file: PUBLIC_KEY = "ABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890" PRIVATE_KEY = "ABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890" *** Edit the file MAILMAN_HOME/Mailman/Cgi/subscribe.py *** We are going to add three pieces of information to this file: 1) The paths to the additional python modules you installed 2) import commands for two modules and 3) the code to check the recaptcha result. Concerning item 1) I manually appended the location of all the modules using sys.path.append. A better way to do this would be to install the modules in one directory where python can find them. I've never worked with python before so I didn't know how to do this. I will take some time later to figure this out and simplify the install instructions MAYBE. In the file subscribe.py, locate the end of the paragraph that contains all the "from Mailman import" commands. In version 2.1.23 this is line 34. After line 34 add all the paths to the extra modules. Here is what I had for my Ubuntu 16.04 server: sys.path.append("/usr/local/lib/python2.7/dist-packages/recaptcha2-0.1-py2.7.egg") sys.path.append("/usr/lib/python2.7/dist-packages") sys.path.append("/usr/local/lib/python2.7/dist-packages/furl-1.0.1-py2.7.egg") sys.path.append("/usr/local/lib/python2.7/dist-packages/orderedmultidict-0.7.11-py2.7.egg") sys.path.append("/usr/lib/python2.7/dist-packages/requests-2.9.1.egg-info") Concerning item 2) immediately after the sys.path.append lines you just added, add these import commands: import requests import recaptcha2 Concerning item 3) this is the last step. Locate the line that reads "# Was an attempt made to subscribe the list to itself?" This should be somewhere around line 188 assuming you've added the above lines already. Directly above this line add the following code: # Google recaptcha v2 captcha_result = recaptcha2.verify( mm_cfg.SECRET_KEY, cgidata.getvalue('g-recaptcha-response', ""), os.environ.get('REMOTE_ADDR') ) if not captcha_result['success']: results.append(_('Invalid captcha')) That’s all. I have tested this in a development environment and it appears to work as expected.

1 0

Rejecting all addresses from a particular domain ?
by John Fitzsimons Dec. 19, 2017

Dec. 19, 2017

Hi, thanks to the Mailman FAQ I have a fairly good idea how to do the following BUT I am not very familiar with regexp. Could someone here help me with the exact syntax please ? I want to automatically discard all non-subscribers who attempt to subscribe from the .ua domain (Ukraine ?) In other words, what do I put in "List of non-member addresses whose postings will be automatically discarded" ? Regards, John.

2 1

admindb functionality not working 2.2.15 on RHEL
by Sowers, Brent Dec. 15, 2017

Dec. 15, 2017

I'm in the process of migrating to a new server and the remaining issue I've run into is none of the admindb functionality is working on lists I've created to test the new server. The old server is running 2.1.6, the new is running 2.1.15 from an RPM install. I have 2 subscription requests that won't process, approve doesn't add them to the list, reject doesn't generate an email, likewise defer and discard have no impact either. I did some research and saw that a patch was introduced in 2002 for something similar and confirmed that the code change is present in my admindb.py file. I have one email in the pending list which I can't process either. The old server has ownership set for apache:mailman on select pyc files in the Mailman/Cgi directory so I changed the files on the new server to have the same ownership and permissions (rw-rw----) but it didn't resolve the problem. Regards, Brent Sowers 203.432.5840

2 1

no "pending moderator requests" email warnings anymore
by Charles Stroom Dec. 13, 2017

Dec. 13, 2017

Hi, I have used mailman for many years to maintain a small distribution list for a group of musical instrument makers, called "dehoutblazers". It has been transferred a couple of times and runs now on a Linux Opensuse Leap 42.2 server which distributed Mailman 2.1.22. The list is purely used via email (no web site), but I do use the administrative tasks via the web site. Since a couple of weeks (or maybe longer) there is a problem with the "attend to pending tasks", for intercepted emails which are not going through because of the criteria (non-member email, too large, etc.) I used to receive a message of the mailman, but I am not getting such messages anymore. I have been trying to find out why, but have so far failed. I tested also some email mailman addresses with the following results. - the mail list itself works as it should. My conclusion is that the aliases file is found and used. - if I send an email to "listname"-request, I get proper replies. - if I send to "listname"-admin, I do not receive that email, but instead an email from mailman-bounce to "listname"-owner with my email attached. "" From: mailman-bounces(a)stremen.xs4all.nl To: dehoutblazers-owner(a)stremen.xs4all.nl Subject: Uncaught bounce notification Date: Mon, 11 Dec 2017 15:24:13 +0100 Sender: "dehoutblazers" <mailman-bounces(a)stremen.xs4all.nl> The attached message was received as a bounce, but either the bounce format was not recognised, or no member addresses could be extracted from it. This mailing list has been configured to send all unrecognised bounce messages to the list administrator(s). For more information see: http://stremen.xs4all.nl/mailman/admin/dehoutblazers/bounce From: Charles Stroom <charles(a)stremen.xs4all.nl> To: dehoutblazers-admin(a)stremen.xs4all.nl Subject: email test Date: Mon, 11 Dec 2017 15:24:07 +0100 X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.31; x86_64-suse-linux-gnu) no content "" And in the standard mail log of the server I get "" postfix/smtpd[3689]: connect from bsmtpdelivery7.xs4all.net[194.109.127.156] postfix/smtpd[3689]: C774F216C: client=bsmtpdelivery7.xs4all.net[194.109.127.156] postfix/cleanup[3693]: C774F216C: message-id=<20171211152407.1611b8b4(a)fiume5.localnet> postfix/qmgr[2642]: C774F216C: from=<charles(a)stremen.xs4all.nl>, size=1444, nrcpt=1 (queue active) postfix/smtpd[3689]: disconnect from bsmtpdelivery7.xs4all.net[194.109.127.156] postfix/local[3694]: C774F216C: to=<dehoutblazers-admin(a)stremen.xs4all.nl>, relay=local, delay=0.35, delays=0.13/0.01/0/0.21, dsn=2.0.0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman admin dehoutblazers) postfix/qmgr[2642]: C774F216C: removed postfix/smtpd[3689]: connect from localhost[::1] postfix/smtpd[3689]: C36FC216C: client=localhost[::1] postfix/cleanup[3693]: C36FC216C: message-id=<mailman.0.1513002253.2882.dehoutblazers(a)stremen.xs4all.nl> postfix/qmgr[2642]: C36FC216C: from=<mailman-bounces(a)stremen.xs4all.nl>, size=3058, nrcpt=1 (queue active) postfix/smtpd[3689]: disconnect from localhost[::1] postfix/local[3694]: C36FC216C: to=<charles(a)stremen.xs4all.nl>, relay=local, delay=0.06, delays=0.02/0/0/0.04, dsn=2.0.0, status=sent (delivered to mailbox) postfix/qmgr[2642]: C36FC216C: removed "" - if I send to "listname"-owner, I do not receive any email at all, as if the email has been delivered to /dev/null. And in the standard mail log of the server I get: "" postfix/smtpd[3880]: connect from bsmtpdelivery6.xs4all.net[194.109.127.155] postfix/smtpd[3880]: 3814C216C: client=bsmtpdelivery6.xs4all.net[194.109.127.155] postfix/cleanup[3884]: 3814C216C: message-id=<20171211153550.7fb31e1d(a)fiume5.localnet> postfix/qmgr[2642]: 3814C216C: from=<charles(a)stremen.xs4all.nl>, size=1455, nrcpt=1 (queue active) postfix/smtpd[3880]: disconnect from bsmtpdelivery6.xs4all.net[194.109.127.155] postfix/local[3885]: 3814C216C: to=<dehoutblazers-owner(a)stremen.xs4all.nl>, relay=local, delay=0.36, delays=0.13/0.01/0/0.22, dsn=2.0.0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman owner dehoutblazers) postfix/qmgr[2642]: 3814C216C: removed postfix/smtpd[3880]: connect from localhost[::1] postfix/smtpd[3880]: warning: Illegal address syntax from localhost[::1] in MAIL command: <mailman-bounces@> postfix/smtpd[3880]: disconnect from localhost[::1] "" There are pending pending moderator requests in the list so I tried a manual cron command (as user "mailman"): "" /usr/bin/python -S /usr/lib/mailman/cron/checkdbs "" Nothing happened, the offending emails are not removed, and I did not receive any email. With the mail log below "" postfix/smtpd[4025]: connect from localhost[::1] postfix/smtpd[4025]: 1AC17216C: client=localhost[::1] postfix/cleanup[4028]: 1AC17216C: message-id=<mailman.0.1513003270.4024.dehoutblazers(a)stremen.xs4all.nl> postfix/qmgr[2642]: 1AC17216C: from=<dehoutblazers-bounces(a)stremen.xs4all.nl>, size=1500, nrcpt=1 (queue active) postfix/smtpd[4025]: disconnect from localhost[::1] postfix/local[4029]: 1AC17216C: to=<dehoutblazers-owner(a)stremen.xs4all.nl>, relay=local, delay=0.22, delays=0.03/0.01/0/0.18, dsn=2.0.0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman owner dehoutblazers) postfix/qmgr[2642]: 1AC17216C: removed postfix/smtpd[4025]: connect from localhost[::1] postfix/smtpd[4025]: warning: Illegal address syntax from localhost[::1] in MAIL command: <mailman-bounces@> 2017-12-11T15:41:13.195034+01:00 stremen6 postfix/smtpd[4025]: disconnect from localhost[::1] "" Apparently, the is something wrong with the email message sender or recipient as formatted by mailman, but to me everything seems OK. I am the owner and the moderator. Is there a way to see what mailman is actually transferring to the postfix program? I should add that at about the same time I have added a second mailing list, which behaves similarly. I am not sure the erroneous behaviour occurred before, due to, or after that introduction. Any help would be appreciated. Regards, Charles -- Charles Stroom email: charles at no-spam.stremen.xs4all.nl (remove the "no-spam.")

2 4