Mailman 3 May 2015 - Mailman-Developers

before next release: disable backscatter in default installation
by Jo Rhett 07 Nov '22

07 Nov '22

Hi. There's a fairly simple problem here that needs to be addressed. And it's mostly a documentation/install problem. I'm hoping we can get this resolved before the next release. PROBLEM: Mailman comes out of the box ready to backscatter spam people. Yes, it's easy enough to fix. But because it comes stock this way, and is documented to install this way, most people install it to do this. Those of us who work in abuse departments are tired of hearing "well that's how Mailman works". We also object to having to teach people how to fix their mailman installations because it's not documented in the current manual. This is *exactly* like Sendmail 14 years ago. We didn't accept it then, and Sendmail fixed the problem. RESOLUTION: Mailman default installation should not backscatter in a default configuration. 1. Don't create backscatter aliases for subscribe/unsubscribe/etc by default. Nearly everyone uses web based signup. 2. Discard or hold messages from non-subscribers by default. I would think that it would be perfectly reasonable to have documentation on how to enable the 1980s-style -request / -subscribe etc aliases. However this documentation should have a note that this is against the AUP of nearly every network provider, and enabling it will likely cause them to get listed in various blacklists as a backscatter source. FYI: I know that this goes against the instincts of many old-time mailing list advocates here. But after dealing with a 10k/hour backscatter DoS my tolerance for this problem is understandably limited. Yes, it was a sweet day back in the 1980s. I was running a mailing list server and several UUCP gateways at the time, so I remember them well. But those days are past, and we need to deal with the reality of today. -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness

21 168

can not post to the list
by Danil Smirnov 30 May '15

30 May '15

I have Mailman 3 installed and Postorius and Hyperkitty seemingly working. I can subscribe, get welcome message and when I send message to the list it appears in held messages. Then when I accept the message, it does not come into the list and does not appear in the archives. Here what I found in the logs: --- May 30 09:15:30 2015 (2247) held message approved, message-id: <CAMrrXbpHaUbHvw7y6TSkhQxG2fLqEpz_TUXpZHwi=zxYpLzEzw(a)mail.gmail.com> May 30 09:15:30 2015 (2247) 127.0.0.1 - - "POST /3.0/lists/test(a)domain.tld/held/2 HTTP/1.1" 204 0 May 30 09:15:30 2015 (2247) 127.0.0.1 - - "GET /3.0/lists/test.domain.tld HTTP/1.1" 200 303 May 30 09:15:30 2015 (2247) 127.0.0.1 - - "GET /3.0/lists/test(a)domain.tld/held HTTP/1.1" 200 90 May 30 09:15:31 2015 (2243) Uncaught runner exception: ('Connection aborted.', ConnectionRefusedError(111, 'Connection refused')) May 30 09:15:31 2015 (2243) Traceback (most recent call last): File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 544, in urlopen body=body, headers=headers) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 349, in _make_request conn.request(method, url, **httplib_request_kw) File "/usr/local/lib/python3.4/http/client.py", line 1088, in request self._send_request(method, url, body, headers) File "/usr/local/lib/python3.4/http/client.py", line 1126, in _send_request self.endheaders(body) File "/usr/local/lib/python3.4/http/client.py", line 1084, in endheaders self._send_output(message_body) File "/usr/local/lib/python3.4/http/client.py", line 922, in _send_output self.send(msg) File "/usr/local/lib/python3.4/http/client.py", line 857, in send self.connect() File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 155, in connect conn = self._new_conn() File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 134, in _new_conn (self.host, self.port), self.timeout, **extra_kw) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/util/connection.py", line 88, in create_connection raise err File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/util/connection.py", line 78, in create_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/adapters.py", line 370, in send timeout=timeout File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 597, in urlopen _stacktrace=sys.exc_info()[2]) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/util/retry.py", line 245, in increment raise six.reraise(type(error), error, _stacktrace) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/packages/six.py", line 309, in reraise raise value.with_traceback(tb) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 544, in urlopen body=body, headers=headers) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 349, in _make_request conn.request(method, url, **httplib_request_kw) File "/usr/local/lib/python3.4/http/client.py", line 1088, in request self._send_request(method, url, body, headers) File "/usr/local/lib/python3.4/http/client.py", line 1126, in _send_request self.endheaders(body) File "/usr/local/lib/python3.4/http/client.py", line 1084, in endheaders self._send_output(message_body) File "/usr/local/lib/python3.4/http/client.py", line 922, in _send_output self.send(msg) File "/usr/local/lib/python3.4/http/client.py", line 857, in send self.connect() File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 155, in connect conn = self._new_conn() File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 134, in _new_conn (self.host, self.port), self.timeout, **extra_kw) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/util/connection.py", line 88, in create_connection raise err File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/util/connection.py", line 78, in create_connection sock.connect(sa) requests.packages.urllib3.exceptions.ProtocolError: ('Connection aborted.', ConnectionRefusedError(111, 'Connection refused')) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/runner.py", line 165, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/runner.py", line 258, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/runners/pipeline.py", line 41, in _dispose process(mlist, msg, msgdata, pipeline) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/pipelines.py", line 62, in process handler.process(mlist, msg, msgdata) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/handlers/rfc_2369.py", line 123, in process process(mlist, msg, msgdata) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/handlers/rfc_2369.py", line 89, in process archiver.system_archiver.list_url(mlist)) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman_hyperkitty/__init__.py", line 101, in list_url return self._get_url({"mlist": mlist.fqdn_listname}) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman_hyperkitty/__init__.py", line 82, in _get_url result = requests.get(url, params=params) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/api.py", line 69, in get return request('get', url, params=params, **kwargs) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/api.py", line 50, in request response = session.request(method=method, url=url, **kwargs) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/sessions.py", line 465, in request resp = self.send(prep, **send_kwargs) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/sessions.py", line 573, in send r = adapter.send(request, **kwargs) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/adapters.py", line 415, in send raise ConnectionError(err, request=request) requests.exceptions.ConnectionError: ('Connection aborted.', ConnectionRefusedError(111, 'Connection refused')) --- I don't understand what particular 'connection' mentioned, please advice. Thanks, Danil

1 0

Re: [Mailman-Developers] Recipient address rejected: User unknown in virtual alias table
by Danil Smirnov 30 May '15

30 May '15

2015-05-30 9:02 GMT+03:00 Danil Smirnov <danil(a)smirnov.la>: > But I have everything required by installation manual in the main.conf > so I have no idea > what going wrong and how to debug this wrong alias problem. Found postfix misconfiguration. Have no relation to Mailman 3. Just forget about this. Danil

1 0

Re: [Mailman-Developers] Recipient address rejected: User unknown in virtual alias table
by Barry Warsaw 30 May '15

30 May '15

On May 30, 2015, at 12:58 AM, Danil Smirnov wrote: >Now I have working Postorius and I can subscribe myself to the test >list and get the welcome message (with incorrect urls in it!). Known bug! The default templates actually need to be updated to not include those urls, because the core doesn't know what those urls would be. There is machinery to allow for two levels of indirection so that, e.g. url-containing templates could be defined in Postorius, and the core would fetch the on demand, but that needs to be fleshed out a bit more (and will be in MM3.1). >But I could not post to the list or mail to the list owner from outside: > >550 5.1.1 <test-owner(a)domain.tld>: Recipient address rejected: User >unknown in virtual alias table > >I've checked postfix/main.cf and everything looks right in it. >Also I've ensured that var/data/*.db files are world-readable. >Selinux is disabled. > >How could I debug this error? It sounds like a Postfix problem, so cranking up Postfix logging is probably going to be the most fruitful avenue. Cheers, -Barry

2 1

Recipient address rejected: User unknown in virtual alias table
by Danil Smirnov 29 May '15

29 May '15

Now I have working Postorius and I can subscribe myself to the test list and get the welcome message (with incorrect urls in it!). But I could not post to the list or mail to the list owner from outside: 550 5.1.1 <test-owner(a)domain.tld>: Recipient address rejected: User unknown in virtual alias table I've checked postfix/main.cf and everything looks right in it. Also I've ensured that var/data/*.db files are world-readable. Selinux is disabled. How could I debug this error? Thanks, Danil

1 0

Re: [Mailman-Developers] right adding of mailman 3 conf lines to httpd.conf
by Danil Smirnov 29 May '15

29 May '15

> Also there is nothing in the logs. After I uncommented in httpd.conf the line ErrorLog /var/log/httpd/mailman-web_error.log I've got more info about the issue. It was permission error: ValueError: Unable to configure handler 'file': [Errno 13] Permission denied: '/var/log/mailman-web/mailman-web.log' After I corrected permissions for log file mentioned I can access Postorius and Hyperkitty. Everything looks working, I will test in more details later. Thanks! Danil

1 0

Re: [Mailman-Developers] [Project Discussion] Assigining Default Priority levels to user tasks
by Barry Warsaw 29 May '15

29 May '15

On May 24, 2015, at 01:43 AM, Bhavesh Goyal wrote: >Whenever a new task gets added automatically ( when someone makes a >subscription request for instance), what priority level should it be >assigned. ? Perhaps that should be configurable? As a list administrator, I might prefer to handle subscription requests first, but someone else may want to handle held messages first. Cheers, -Barry

1 0

MM3 install on RHEL 5.11
by Bill.Costa＠unh.edu 29 May '15

29 May '15

I need to migrate off of crufty old CREN ListProc (LP). So far I have successfully installed MM2 and did some limited testing. But seeing how MM3 has come out of beta, I thought it would be better to leapfrog to MM3 rather than forcing my list owners and subscribers through two MLM migrations (LP -> MM2 -> MM3). I am installing MM on my current list host, RedHat Enterprise Server 5.11, since it will allow me to migrate the lists one by one without a list address change; I'll just replace each LP set of aliases with MM aliases as I convert the lists. (I'll move to a more modern OS after the migration is done.) While I am an experienced programmer, with extensive Perl and Bash experience, I'm totally new to the Python ecosystem so I'm not familiar with things like `pip`, `bz`, and Virtualenv. So my first question is --- am I'm crazy to try and jump into MM3 for a production system at this stage of its development? To help me install MM3 I'm using the following two resources: https://mailman-bundler.readthedocs.org/en/latest/ http://wiki.list.org/HyperKitty/DevelopmentSetupGuide So far I have successfully installed both Python 2.6 and 3.4 and upgraded to the latest version of `pip` pip 7.0.1 from /usr/local/lib/python3.4/site-packages (python 3.4) It looks like the next thing I need to install GNU Bazaar. I thought I could do it with `pip`, but ran into a problem and Google is of limited help to me. (Install Cython? Pyrex??) Any help, about this specific problem, or the wisdom of my jumping onto the MM3 wagon in general, would be appreciated. ...BC $ sudo -H pip install bzr Collecting bzr Downloading bzr-2.6.0.tar.gz (11.3MB) 100% |████████████████████████████████| 11.3MB 34kB/s Complete output from command python setup.py egg_info: No Cython, trying Pyrex... The python package 'Pyrex' is not available. If the .c files are available, they will be built, but modifying the .pyx files will not rebuild them. running egg_info creating pip-egg-info/bzr.egg-info writing top-level names to pip-egg-info/bzr.egg-info/top_level.txt writing dependency_links to pip-egg-info/bzr.egg-info/dependency_links.txt writing pip-egg-info/bzr.egg-info/PKG-INFO Traceback (most recent call last): File "<string>", line 20, in <module> File "/tmp/pip-build-3a5_7rap/bzr/setup.py", line 780, in <module> setup(**ARGS) File "/usr/local/lib/python3.4/distutils/core.py", line 148, in setup dist.run_commands() File "/usr/local/lib/python3.4/distutils/dist.py", line 955, in run_commands self.run_command(cmd) File "/usr/local/lib/python3.4/distutils/dist.py", line 974, in run_command cmd_obj.run() File "<string>", line 14, in replacement_run File "/usr/local/lib/python3.4/site-packages/setuptools/command/egg_info.py", line 387, in write_pkg_info metadata.write_pkg_info(cmd.egg_info) File "/usr/local/lib/python3.4/distutils/dist.py", line 1108, in write_pkg_info self.write_pkg_file(pkg_info) File "/usr/local/lib/python3.4/distutils/dist.py", line 1129, in write_pkg_file long_desc = rfc822_escape(self.get_long_description()) File "/usr/local/lib/python3.4/distutils/util.py", line 470, in rfc822_escape lines = header.split('\n') TypeError: 'str' does not support the buffer interface ---------------------------------------- Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-3a5_7rap/bzr $

4 4

right adding of mailman 3 conf lines to httpd.conf
by Stephen J. Turnbull 29 May '15

29 May '15

Danil Smirnov writes: > Please help me to do this. > > if I put deployment/apache.conf into the virtualhost section of > httpd.conf I got the following: > > httpd[30658]: AH00526: Syntax error on line 428 of /etc/httpd/conf/httpd.conf: > httpd[30658]: WSGISocketPrefix cannot occur within <VirtualHost> section > > If I put them just outside of any virtualhost tags they produce Server > error page. > > It would be great if I could put them into :443 virtualhost section to > use SSL connection only for the list management/archives. Is deployment/apache.conf distributed by Mailman (presumably in Mailman-Bundler)? Have you changed it in *any* way (including anything that the installation instructions tell you do do)? I'm asking because it sounds to me like apache.conf is written to be use only in a non-virtual-host setup, which I would consider a bug that we need to fix. AFAICS from the modwsgi docs, just move the WSGISocketPrefix out of apache.conf and into a non-vhost area of httpd.conf and you should be golden.

2 1

right adding of mailman 3 conf lines to httpd.conf
by Danil Smirnov 29 May '15

29 May '15

Please help me to do this. if I put deployment/apache.conf into the virtualhost section of httpd.conf I got the following: httpd[30658]: AH00526: Syntax error on line 428 of /etc/httpd/conf/httpd.conf: httpd[30658]: WSGISocketPrefix cannot occur within <VirtualHost> section If I put them just outside of any virtualhost tags they produce Server error page. It would be great if I could put them into :443 virtualhost section to use SSL connection only for the list management/archives. Centos 7, Apache 2.4.6, last mailman-bundler. Danil

1 0