- Mailman-users - lists.mailman3.org

Which crontab?
by Pierre Abbat 15 Nov '17

15 Nov '17

According to http://docs.mailman3.org/en/latest/config-core.html, I have to add "@daily mailman digests --send" to the crontab. Which crontab does it go in? In the system crontab, the thing after the time is the username, and there's no user named "mailman" in /etc/passwd. Or should I put a script in / etc/cron.daily/? Pierre -- loi mintu se ckaji danlu cu jmaji

2 10

Rolling releases for Container Images and Funding Campaign for Mailman
by Abhilash Raj 14 Nov '17

14 Nov '17

Hi Everyone, As you all know I have been working on container images for Mailman 3. We now have a new "rolling" tag for both mailman-core and mailman-web images. These images have latest source installed for every Mailman component. You can find more information about them on the website [3]. New images are available on quay.io and, moving forward, the rest of the image builds will also be moved to Quay[4][5]. These images are built using git-heads *only* if they are passing our test suite and are re-generated weekly. You should be aware that while all these components are tested with their individual test suites, their combination might sometimes not be stable. This will get you updates/bug-fixes much faster :) As most of you already know, Mailman 3 is the new and improved version with extra features, better security and much better architecture. We released Mailman Suite 3.0 in April 2015 and have come a long ways since then. Mailman Suite 3.1, release May 2016, was aimed to provide feature-parity with Mailman 2.x series and we think we _almost_ hit that goal. Apart from no monthly password reminders, Mailman 3 has a much better Administrator/User interface, REST API for scripting, a really awesome archiver, support for multiple domains, support for external plugins, support for SSO/social login and so much more! I love working on Mailman and would enjoy being able to do so full time for next 6-8 weeks. Mailman 3 is not very far from becoming the default version everyone would use, but it still needs some work to get there. I need help from you, the users of Mailman, to get us there. If you or your organization would like to move to (or, already moved to) Mailman 3, I urge you to donate[1] to us. There are options to donate using Credit Card, Paypal, Bitcoin, Wire Transfer (of any currency), Check and money order. If this campaign succeeds, here is a road map of what I intend to get done: - Move Django apps(UI/Archiver) to Python 3 (or bilingual) - Fork `mailman import` command to provide an upgrade path to Mailman 3.x from Mailman 2.x - Fix MySQL compatibility in Core - Changes in Postorius: - Add support for missing options that are already exposed in Core’s API - e.g. Support for setting templates - Find the commonly used options that are not exposed in Core, add them to Core's API and add to Postorius - Add Admin Dashboard project from GSoC 2014 (maybe?) - Add better testing of container images and provide deployment instructions for Kubernetes & Docker Swarm - Improve the container images to work with new micro-services architecture, to achieve scaling and redundancy in services. - Administrator/User documentation for Postorius & Mailman - (optional) Fork [mmcli](https://github.com/rajeevs1992/mailmancli) project from Rajeev, fix if there is anything missing and add it as an additional command line tool to work with Mailman Core. Maybe pull it under Mailman umbrella. Except for these, if there is something more important that is preventing the adoption of Mailman 3 from your end, we can discuss them. I'd like to mention that I have been working on Mailman 3 for quite some time now and I intend to implement every single item on the list. You donations would help it get done much sooner, hopefully in time for 3.2 release schedule (at PyCon US 2018). You can follow the progress of this campaign here[2]. [1]: https://my.fsf.org/civicrm/contribute/transact?reset=1&id=22 [2]: https://wiki.list.org/x/17892025 [3]: https://asynchronous.in/docker-mailman/#rolling-releases [4]: https://quay.io/repository/maxking/mailman-web [5]: https://quay.io/repository/maxking/mailman-core -- Abhilash Raj maxking(a)asynchronous.in

3 6

Django 2.0 (and newer) requires Python 3; how about archiver and list handler Django apps?
by ddw David Wilson 13 Nov '17

13 Nov '17

Hi all; LTS Django version 1.11, the last supporting Python 2.7, was released earlier this year. I noticed that in December 2017, Django version 2.0 will be released, which apparently will require Python 3.X Taken from the Django web site, 'We recommend using the latest version of Python 3. The last version to support Python 2.7 is Django 1.11 LTS.' Given that the utilities to archive and also handle email lists are both Django applications, which apparently have *not* yet been updated to Python 3, if I understand correctly? *This leads me to wonder if this presents a problem moving forward and staying compatible with the current versions of Django (in addition to Mailman 3.0)?* Many thanks in advance for any light you can shed in this area. Best regards. Dave Wilson

2 1

Re: integrating mm3 with postfix / lmtp
by Mark Sapiro 13 Nov '17

13 Nov '17

On 10/25/2017 05:41 PM, Fabian A. Santiago wrote: > > No to the domains part and I think virtual alias maps is needed: > > mail postfix/trivial-rewrite[19445]: warning: do not list domain xxx in BOTH virtual_mailbox_domains and relay_domains > Oct 25 20:39:19 mail postfix/trivial-rewrite[19445]: warning: do not list domain xxx in BOTH virtual_mailbox_domains and relay_domains > Oct 25 20:39:19 mail postfix/submission/smtpd[19441]: NOQUEUE: reject: RCPT from pool-108-53-239-102.nwrknj.fios.verizon.net[108.53.239.102]: 550 5.1.1 <test123@xxx>: Recipient address rejected: User unknown in virtual mailbox table; from=<fsantiago@xxx> to=<test123@xxx> proto=ESMTP helo=<[10.0.0.29]> (above slightly sanitized for return to the list) The issue here is your list domain cannot be a virtual_mailbox_domain or a virtual_alias_domain. I have the same issue on mail.python.org where we have both Mailman 2 and Mailman 3 lists @python.org. and python.org is a virtual_alias_domain. I have a group of MRs for a branch that implements "alias_domains" to deal with this. Basically it works by creating another (virtual_alias_maps) postfix_vmap mapping to map list addresses @python.org to addresses @x.python.org. Then the postfix_domains and postfix_lmtp maps have the x.python.org domain and there is a patch to mailman/runners/lmtp.py to map the x.python.org domain back to python.org. The various MRs are <https://gitlab.com/mailman/mailman/merge_requests/202> for the core, <https://gitlab.com/mailman/mailmanclient/merge_requests/18> for the REST bindings used by Postorius and <https://gitlab.com/mailman/postorius/merge_requests/186> to be able to set an alias_domain via Postorius. That's not all implemented at mail.python.org. What's there is the basic Postfix config, a bash script the generate the new mappings from the old and a simple patch to mailman/runners/lmtp.py. So, the bottom line is it can be done and it's in process, but it won't really be supported until Mailman 3.2. In the mean time, you just need to have a separate domain for your lists that isn't a virtual_*_domain. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 15

HyperKitty: discussions not updating, misreporting stats
by Cameron Smith 13 Nov '17

13 Nov '17

These are a couple of HyperKitty issues that I have talked about in August [1]. I’ve been doing a bit more experimentation in the last few days and am reporting my findings. The two issues are: — Missing messages: HyperKitty doesn’t show all of the messages in a discussion - Misreporting of discussion statistics: HyperKitty doesn’t update the number of participants and comments in a discussion I’m using the latest Docker setup. Neither of these issues are solved by updating or rebuilding indexes: sudo docker exec mailman-web ./manage.py update_index sudo docker exec mailman-web ./manage.py rebuild_index However, if I stop and then restart the containers (sudo docker-compose down; sudo docker-compose up -d), the discussion statistics are updated and properly display the number of participants and comments in all discussions. This does not, however, solve the problem of missing messages. I have discovered two methods of displaying the missing discussion messages: add a new message to the thread in HyperKitty; I’m not convinced that this works *every* time, but it at least works *most* times run the yearly cron job; this seems to work *every* time: sudo docker exec mailman-web ./manage.py runjobs yearly [1]: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Cameron Smith

2 1

Bounces
by David Krantz 07 Nov '17

07 Nov '17

Hi. How do I config mailman 3.1x to send any unrecognized bounces to e.g. the list owner? Now they just end up in the bounces table but I would like to see the entire message in this case. Cheers // David

2 3

LDAP/Krb5/SAML auth for Mailman
by Dmitry Makovey 07 Nov '17

07 Nov '17

Can anyone share some information on LDAP/Krb5 or better yet SAML auth implementation for Mailman. Is it just adding appropriate auth module to DJango project or is there more involved things? -- Sr System and DevOps Engineer SoM IRT

2 1

configuring moderators per list
by Dmitry Makovey 07 Nov '17

07 Nov '17

We're trying to configure moderator per list and so far we were only able to add "superuser" accounts that can handle "Held messages", "Members", "Banned addresses" etc. Is there a way to create special account per-list to manage some of the aspects of particular ML without giving them all the permissions that Superuser comes along with? In MM2 there was a ML password that moderator/list admin would use to login to perform operations. Current setup allows list admins to add/delete existing lists which is not desired. -- Sr System and DevOps Engineer SoM IRT

3 3

disabling social login
by Dmitry Makovey 06 Nov '17

06 Nov '17

Hi, I'm trying to disable social login and running into troubles stepping on it's remnants all over the place. What's the proper sequence for disabling social login in MM3 install? -- Sr System and DevOps Engineer SoM IRT

3 4

Message shows up individually but not in the thread
by Marvin Gülker 04 Nov '17

04 Nov '17

Hi, I've just observed something weird. While some users were testing the new mailman setup, the reply did not make it into the corresponding thread, but is still associated with it. That is, the message does not show up in the thread page at[1]. However, the reply is visible if requested individually[2]. Now what's weird is that in [2] there's a link at the top that says "< thread" that takes one to [1], so there is some kind of association appearently made but only in one direction (the reverse one). mailman.log has this to say: Nov 03 17:22:31 2017 (498) ACCEPT: <1fa6f9e1-254c-e999-42d0-9a6cc263020d(a)openmailbox.org> Nov 03 17:22:32 2017 (507) 127.0.0.1 - - "GET /3.0/users/sydneyjd(a)openmailbox.org HTTP/1.1" 200 305 Nov 03 17:22:32 2017 (495) HyperKitty archived message <1fa6f9e1-254c-e999-42d0-9a6cc263020d(a)openmailbox.org> to https://lists.secretchronicles.org/hyperkitty/list/tsc-users@lists.secretch… The mailman-suite log contains: INFO 2017-11-03 17:22:32,910 14330 hyperkitty.views.mailman Archived message <1fa6f9e1-254c-e999-42d0-9a6cc263020d(a)openmailbox.org> to https://lists.secretchronicles.org/hyperkitty/list/tsc-users@lists.secretch… This looks to me like a bug. The OP of that thread sent the same message to our other mailinglist[3] (where he did not get a reply), so Mailman may has been confused by that. Marvin [1]: https://lists.secretchronicles.org/hyperkitty/list/tsc-users@lists.secretch… [2]: https://lists.secretchronicles.org/hyperkitty/list/tsc-users@lists.secretch… [3]: https://lists.secretchronicles.org/hyperkitty/list/tsc-devel@lists.secretch… -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

2 8

Hyperkitty Missing Theme/Style Sheets?
by Andrew Hodder 01 Nov '17

01 Nov '17

I have an odd one, my Hyperkitty is functionally working fine (archived several lists without issue, can login/out), however I must have done something wrong during it's setup as it's layout is completely broken (and it keeps throwing Example.com up in the top-left corner). See attached. I'd run into a similar issue with Postorious when I first set it up, but I can't recall what fixed it. Any ideas to what needs correcting? Thanks. Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541

3 9

localhost[::1] said: 550 Requested action not, taken: mailbox unavailable
by Bjoern Franke 29 Oct '17

29 Oct '17

Hi, I created & imported a bunch of 2.1 lists and for one of the lists mm3 replies mailbox unavailable to postfix. I have no clue why this happens because the other lists work. Kind regards Bjoern

2 5

No path configuration found: paths.master
by Pierre Abbat 27 Oct '17

27 Oct '17

I installed postorius and hyperkitty with pip and ran into another problem. I ran "mailman info" and got "No path configuration found: paths.master". I have three files named mailman.cfg: /etc/mailman.cfg /usr/local/lib/python3.5/dist-packages/mailman/config/mailman.cfg /var/etc/mailman.cfg The one in /etc contains the following: [mailman] layout: master The one in /var/etc is completely commented out. If I move the one in /etc/ out of the way and run "mailman info" again, I get this: GNU Mailman 3.1.0 (Between The Wheels) Python 3.5.2 (default, Sep 14 2017, 22:51:06) [GCC 5.4.0 20160609] config file: None db url: sqlite:////etc/var/data/mailman.db devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass It said "config file: /var/etc/mailman.cfg" before. What changed? Pierre -- La sal en el mar es más que en la sangre. Le sel dans la mer est plus que dans le sang.

4 6

Moderating posts via email
by Dmitry Makovey 26 Oct '17

26 Oct '17

Hi, we are trying to figure out what is that we're doing wrong as we can't use instructions that mailman sends with information on held messages as referenced in: https://gitlab.com/mailman/mailman/blob/master/src/mailman/chains/hold.py#L… In particular - replying to the message with "Approved: listpassword" we were not able to approve any message. Since there's no place we could find in interface to change ML password I did it through the mailmanclient: ml=client.get_list('mylists(a)lists.some.com') ml.settings['moderator_password']='password123' ml.settings.save() after which we've used above password trying to approve messages following the steps outlined above. What are we doing wrong, or where to look for further information? -- Sr System and DevOps Engineer SoM IRT

4 8

scheduled tasks in docker-based deployments
by Dmitry Makovey 26 Oct '17

26 Oct '17

I came across the section http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required that claims that crontab entries are *required* for normal MM3 operations, but I do not see anything like that in docker-based implementation. Should I add similar cron jobs manually to the host box? -- Sr System and DevOps Engineer SoM IRT

2 2

Setting configuration variables on all lists from command line
by Peter Mueller 26 Oct '17

26 Oct '17

Hello, could you provide an example how I can set various configuration variables using "mailman withlist" or "mailman "shell" on _all_ lists? E.g. I want to set on all lists: m.send_welcome_message = 0 m.send_goodbye_message = 0 Thank you! P.M.

2 2

changing mail footer
by Dmitry Makovey 26 Oct '17

26 Oct '17

Where and how can I set a footer of the message to include link to mailing list subsciptio/admin pages to simulate MM2 behavior? -- Sr System and DevOps Engineer SoM IRT

2 1

changing secrets on a prod instance
by Dmitry Makovey 26 Oct '17

26 Oct '17

I'm trying to sort how to properly change secrets of an already running setup. In particular I want to be able to change: REST API user/password Hyperkitty API key Secret key So far, after attempting to change REST API credentials I've got my setup failing on me. Setup details: MM3 set up from maxking's docker images. -- Sr System and DevOps Engineer SoM IRT

4 4

mailman info traceback (Ubuntu Xenial)
by Pierre Abbat 26 Oct '17

26 Oct '17

I'm trying to set up a mailing list server using Mailman. I created a server running Ubuntu Xenial and installed, then removed, the Mailman in the repo, which is 1:2.1.20-1ubuntu0.1. Then I installed pip and ran "pip3 install mailman" and "mailman info" and got an error with traceback. I then tried installing sass and Django following the instructions (I have no idea about sass and Django), then uninstalled and reinstalled Mailman, and tried "mailman info" again. Here is the result: root@lists:/# mailman info Traceback (most recent call last): File "/usr/local/bin/mailman", line 11, in <module> sys.exit(main()) File "/usr/local/lib/python3.5/dist-packages/mailman/bin/mailman.py", line 97, in main initialize(config_path) File "/usr/local/lib/python3.5/dist-packages/mailman/core/initialize.py", line 185, in initialize initialize_2(propagate_logs=propagate_logs) File "/usr/local/lib/python3.5/dist-packages/mailman/core/initialize.py", line 156, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File "/usr/local/lib/python3.5/dist-packages/mailman/database/factory.py", line 55, in create SchemaManager(database).setup_database() File "/usr/local/lib/python3.5/dist-packages/mailman/database/factory.py", line 96, in setup_database alembic.command.stamp(alembic_cfg, 'head') File "/usr/local/lib/python3.5/dist-packages/alembic/command.py", line 504, in stamp script.run_env() File "/usr/local/lib/python3.5/dist-packages/alembic/script/base.py", line 425, in run_env util.load_python_file(self.dir, 'env.py') File "/usr/local/lib/python3.5/dist-packages/alembic/util/pyfiles.py", line 81, in load_python_file module = load_module_py(module_id, path) File "/usr/local/lib/python3.5/dist-packages/alembic/util/compat.py", line 83, in load_module_py spec.loader.exec_module(module) File "<frozen importlib._bootstrap_external>", line 665, in exec_module File "<frozen importlib._bootstrap>", line 222, in _call_with_frames_removed File "/usr/local/lib/python3.5/dist-packages/mailman/database/alembic/ env.py", line 38, in <module> @public File "/usr/local/lib/python3.5/dist-packages/public/public.py", line 15, in public else sys.modules[thing.__module__].__dict__) KeyError: 'env_py' What am I doing wrong, and how do I fix it? Pierre -- .i toljundi do .ibabo mi'afra tu'a do .ibabo damba do .ibabo do jinga .icu'u la ma'atman.

2 2

how do I bulk-remove users from ML in MM3?
by Dmitry Makovey 26 Oct '17

26 Oct '17

I just realized that "mailman members" only offers to "add members" via "-a filename" but I see no remove option. -- Sr System and DevOps Engineer SoM IRT

5 6

integrating mm3 with postfix / lmtp
by Fabian A. Santiago 25 Oct '17

25 Oct '17

Hello, I have mm3 up and running via docker (courtesy of maxking/docker-mailman) but when i send an email to my test list, it bounces back claiming user unknown. it states: <"lmtp:[172.19.199.2]:8024"@>: unknown user: "lmtp:[172.19.199.2]:8024" looking at the email source, it seems as though the message is trying to be delivered to: Final-Recipient: rfc822; "lmtp:[172.19.199.2]:8024"@<my email server's FQDN> Original-Recipient: rfc822;test123@<my list's email domain> all of various alias transport maps are defined in postfix's main.cf. not sure where to go from here. does anyone have any clues? -- Thanks, Fabian S. OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

2 2

mail host choices when creating a new list
by Andrew Hodder 24 Oct '17

24 Oct '17

Hi! So, I'm trying to create a new list and pick one of the other mail domains we have configured (from the django admin panel), yet in the "Create New List" page in postorius, I see only a single option (the first domain we'd added/set as the default) in the drop-down under "Mail Host". Am I missing somewhere else I need to add alternative mail domains to? Thanks in advance! Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541

2 4

Mailman installation results in KeyError: 'env_py'
by Marvin Gülker 24 Oct '17

24 Oct '17

Hi, I'm trying to install Mailman 3 on Debian 9. However, it doesn't let me do. ~~~~~~~~~~~~~ $ virtualenv -p python3 env [...] $ . ./env/bin/activate $ pip install mailman [...] Successfully installed [...]mailman-3.1.0[...] $ mailman info Traceback (most recent call last): File "/home/mailman/mailman-test/env/bin/mailman", line 11, in <module> sys.exit(main()) File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/mailman/bin/mailman.py", line 97, in main initialize(config_path) File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/mailman/core/initialize.py", line 185, in initialize initialize_2(propagate_logs=propagate_logs) File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/mailman/core/initialize.py", line 156, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/mailman/database/factory.py", line 55, in create SchemaManager(database).setup_database() File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/mailman/database/factory.py", line 96, in setup_database alembic.command.stamp(alembic_cfg, 'head') File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/alembic/command.py", line 504, in stamp script.run_env() File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/alembic/script/base.py", line 425, in run_env util.load_python_file(self.dir, 'env.py') File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/alembic/util/pyfiles.py", line 81, in load_python_file module = load_module_py(module_id, path) File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/alembic/util/compat.py", line 83, in load_module_py spec.loader.exec_module(module) File "<frozen importlib._bootstrap_external>", line 673, in exec_module File "<frozen importlib._bootstrap>", line 222, in _call_with_frames_removed File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/mailman/database/alembic/env.py", line 38, in <module> @public File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/public/public.py", line 15, in public else sys.modules[thing.__module__].__dict__) KeyError: 'env_py' ~~~~~~~~~~~~~ I'm not a Python developer, I usually use Ruby for anything web-related, thus I can't make anything of this. Since the error message conveys exactly no information that I could use to find the problem and Google provides no mailman-specific information on it, I don't know what to do now. Any hint is appreciated. Python version, if of any use: $ python --version Python 3.5.3 Greetings Marvin -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

4 8

mailman-web: ResponseNotReady
by Dmitry Makovey 22 Oct '17

22 Oct '17

We've had an odd experience with mailman3 containers: ERROR 2017-10-18 15:47:09,448 60 django.request Internal Server Error: /postorius/lists/ Traceback (most recent call last): File "/usr/local/lib/python2.7/site-packages/django/core/handlers/exception.py", line 39, in inner response = get_response(request) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 249, in _legacy_get_response response = self._get_response(request) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 187, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 185, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python2.7/site-packages/postorius/views/list.py", line 590, in list_index choosable_domains = _get_choosable_domains(request) File "/usr/local/lib/python2.7/site-packages/postorius/views/list.py", line 524, in _get_choosable_domains return [(d.mail_host, d.mail_host) for d in domains] File "/usr/local/lib/python2.7/site-packages/mailmanclient/_client.py", line 217, in __getattr__ return self._get(name) File "/usr/local/lib/python2.7/site-packages/mailmanclient/_client.py", line 183, in _get return self.rest_data.get(key) File "/usr/local/lib/python2.7/site-packages/mailmanclient/_client.py", line 172, in rest_data response, content = self._connection.call(self._url) File "/usr/local/lib/python2.7/site-packages/mailmanclient/_client.py", line 109, in call response, content = Http().request(url, method, data_str, headers) File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py", line 1659, in request (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey) File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py", line 1399, in _request (response, content) = self._conn_request(conn, request_uri, method, body, headers) File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py", line 1355, in _conn_request response = conn.getresponse() File "/usr/local/lib/python2.7/httplib.py", line 1108, in getresponse raise ResponseNotReady() ResponseNotReady It seems like mailman-core is still operating properly, but for some reason mailman-web is not. Can I reset mailman-web somehow to re-initiate? -- Sr System and DevOps Engineer SoM IRT

4 9

Removing the footer from mails
by Peter Mueller 21 Oct '17

21 Oct '17

Hi, mailman2 had the configuration variable "msg_footer" to edit/remove the footer. How can I get rid of the footer in mailman3? Example: "_______________________________________________ Example mailing list -- mailinglist(a)example.com To unsubscribe send an email to mailinglist(a)example.com" Thank you! P.M.

2 1

Moving/cloning mailman3
by Dmitry Makovey 18 Oct '17

18 Oct '17

Hi, I am drawing a blank looking for documentation for mailman3 migrations. How can one dump existing settings for mailman and import it into another instance? -- Sr System and DevOps Engineer SoM IRT

3 5

Mails from Django are not sent
by Bjoern Franke 17 Oct '17

17 Oct '17

Hi, I'm using the "mailman-suite" setup for Postorious and Hyperkitty. I've set EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' in settings.py, but no mails are sent. Files with the e-mails are in the emails folder, but nothing happens, also no errors regarding emails are logged. Postfix as MTA can be connected via localhost:25 and e.g. mailman-core can use it fine. What can I do for further debugging? Kind regards Bjoern Franke

3 3

Installing mailman using pip
by Loring 16 Oct '17

16 Oct '17

I have install mailman-core using pip when I call up "mailman info" I get the following error can anyone point me to what is wrong. Traceback (most recent call last): File "/usr/local/bin/mailman", line 11, in <module> sys.exit(main()) File "/usr/local/lib/python3.5/dist-packages/mailman/bin/mailman.py", line 97, in main initialize(config_path) File "/usr/local/lib/python3.5/dist-packages/mailman/core/initialize.py", line 185, in initialize initialize_2(propagate_logs=propagate_logs) File "/usr/local/lib/python3.5/dist-packages/mailman/core/initialize.py", line 156, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File "/usr/local/lib/python3.5/dist-packages/mailman/database/factory.py", line 55, in create SchemaManager(database).setup_database() File "/usr/local/lib/python3.5/dist-packages/mailman/database/factory.py", line 96, in setup_database alembic.command.stamp(alembic_cfg, 'head') File "/usr/local/lib/python3.5/dist-packages/alembic/command.py", line 504, in stamp script.run_env() File "/usr/local/lib/python3.5/dist-packages/alembic/script/base.py", line 425, in run_env util.load_python_file(self.dir, 'env.py') File "/usr/local/lib/python3.5/dist-packages/alembic/util/pyfiles.py", line 81, in load_python_file module = load_module_py(module_id, path) File "/usr/local/lib/python3.5/dist-packages/alembic/util/compat.py", line 83, in load_module_py spec.loader.exec_module(module) File "<frozen importlib._bootstrap_external>", line 665, in exec_module File "<frozen importlib._bootstrap>", line 222, in _call_with_frames_removed File "/usr/local/lib/python3.5/dist-packages/mailman/database/alembic/env.py", line 38, in <module> @public File "/usr/local/lib/python3.5/dist-packages/public/public.py", line 15, in public else sys.modules[thing.__module__].__dict__) KeyError: 'env_py' -- Richmond Loring rloring(a)bnl.gov Advanced Systems Engineer

2 1

Disabling max_message_size and send_welcome/goodbye_msg globally or by API
by Peter Mueller 11 Oct '17

11 Oct '17

Hello, is it possible to turn off max_message_size and send_welcome_msg / send_goodbye_msg globally? If there are no global options, how can I turn off these feature using the REST API? In python you can do it with >>> mlist.max_message_size = 0. If I send a PATCH request to lists/some@list/config with body max_message_size=0, I get "Unknown attribute". Same for send_welcome_msg and send_goodbye_msg. Thank you! P.M.

2 1

The message is larger than the 40 KB maximum size
by Simon 08 Oct '17

08 Oct '17

Hello, I understand I cannot increase the message size limit in Postorius (yet). But is there another way to adjust it? Simon

2 2

Re: Mailman core: basic internationalization howto?
by David Krantz 06 Oct '17

06 Oct '17

Hi. This is far short of a howto: I have done something similar for one of my lists, although for Swedish. I just added custom templates for all things necessary and set the default language for the list to "sv" for Swedish. It worked without setting the language on the list but then any non-ASCII characters in the template caused mailman to crash and lose the mail without any warning if you send a HTML-formatted message. But it works just fine for pure text messages, I guess as the character set in my test mail was something compatible. I think I filed an error for this. The language for the list can be set via the "mailman withlist" command (or in the database directly, but I have not tried that). I run a relatively new version of mailman, after 3.1. Without Hyperkitty. // David On Wed, Oct 4, 2017 at 10:55 AM, Thor Atle Rustad <thor.rustad(a)gmail.com> wrote: > I would like to use Norwegian in the welcome/subscribe/unsubscribe/confirm > etc messages from mailman3. For my current project I want all future > mailing lists to have Norwegian as default. I find some sporadic info on > the subject, but it's fair to say that I would like some simple > instructions (e.g. what to copy from where to where, and which configs to > change). > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 5

Getting connection refused on postfix trying to connect to mailman-core:lmtp
by Dmitry Makovey 06 Oct '17

06 Oct '17

I've got a setup where postfix runs inside one VM(container) and mailman runs inside another one (maxking containers). I've wired everything according to docs yet I'm getting: postfix/lmtp[266]: 66A72800A87: to=<somelist(a)lists.here.stanford.edu>, relay=none, delay=0.5, delays=0.48/0.01/0/0, dsn=4.4.1, status=deferred (connect to mailman-01.stanford.edu[1.2.3.4]:8024: Connection refused) is it something I'm missing on mailman side or postfix side (like this post suggests: https://gitlab.com/mailman/mailman/issues/365 )? Note: I've configured TLS on postfix side but none on mailman side. Is that the issue? -- Sr System and DevOps Engineer SoM IRT

3 9

WSGI configuration
by Loring 05 Oct '17

05 Oct '17

So I am starting to install mailman3 and following the documentation and am up to the point of configuring the wsgi. The docs give me a config to use (see below) [uwsgi] # Port on which uwsgi will be listening. http-socket = 0.0.0.0:8000 # Move to the directory wher the django files are. chdir = /path-to-django-project-directory/ # Use the wsgi file provided with the django project. wsgi-file = wsgi.py # Setup default number of processes and threads per process. master = true process = 2 threads = 2 # Drop privielges and don't run as root. uid = 1000 gid = 1000 # Setup the django_q related worker processes. attach-daemon = ./manage.py qcluster # Setup the request log. req-logger = file:/path-to-logs/logs/uwsgi.log # Log cron seperately. logger = cron file:/path-to-logs/logs/uwsgi-cron.log log-route = cron uwsgi-cron # Log qcluster commands seperately. logger = qcluster file:/path-to-logs/logs/uwsgi-qcluster.log log-route = qcluster uwsgi-daemons # Last log and it logs the rest of the stuff. logger = file:/path-to-logs/logs/uwsgi-error.log Where does this config go? Does in go in the mailman3.cfg? Any help would be appreciated. -- Richmond Loring rloring(a)bnl.gov Advanced Systems Engineer

3 2

Mailman core: basic internationalization howto?
by Thor Atle Rustad 05 Oct '17

05 Oct '17

I would like to use Norwegian in the welcome/subscribe/unsubscribe/confirm etc messages from mailman3. For my current project I want all future mailing lists to have Norwegian as default. I find some sporadic info on the subject, but it's fair to say that I would like some simple instructions (e.g. what to copy from where to where, and which configs to change).

4 4

Uncaught runner exception: 'str' object has no attribute 'decode'
by Henrik Rasmussen 03 Oct '17

03 Oct '17

When held mails are released in Mailman (maybe also mails which are not held) they are sometimes not sent nor archived, as mentioned in https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… One of my list admins reported that he released two mails on Sep 25 07:20:48 2017 UTC, and only the first was sent to the members. In the mailman.log I found the following from that particular release: Sep 25 07:20:48 2017 (36) 172.19.199.3 - - "GET /3.0/lists/listname.foo.bar HTTP/1.1" 200 353 Sep 25 07:20:48 2017 (36) held message approved, message-id: <CAF9K74uk331j91PfF6S1nQT2YvxywwhUFBWBBcdMGkNMMU4=TA(a)somemail.com> Sep 25 07:20:48 2017 (36) 172.19.199.3 - - "POST /3.0/lists/listname.foo.bar/held/40 HTTP/1.1" 204 0 Sep 25 07:20:48 2017 (36) held message approved, message-id: <804D10D40C57024A90412246998CB72D873B794B(a)P1KITMBX07WC04.mailserver> Sep 25 07:20:48 2017 (36) 172.19.199.3 - - "POST /3.0/lists/listname(a)foo.bar/held/42 HTTP/1.1" 204 0 Sep 25 07:20:48 2017 (36) 172.19.199.3 - - "GET /3.0/lists/listname(a)foo.bar/held?count=0&page=1 HTTP/1.1" 200 90 Sep 25 07:20:48 2017 (36) 172.19.199.3 - - "GET /3.0/lists/listname(a)foo.bar/held?count=10&page=1 HTTP/1.1" 200 90 Sep 25 07:20:53 2017 (28) HyperKitty archived message <CAF9K74uk331j91PfF6S1nQT2YvxywwhUFBWBBcdMGkNMMU4=TA(a)somemail.com> to https://listserver.foo.bar/hyperkitty/list/listname@foo.bar/message/IAKWSH7… Sep 25 07:20:53 2017 (36) 172.19.199.3 - - "GET /3.0/lists/listname(a)foo.bar HTTP/1.1" 200 353 Sep 25 07:20:53 2017 (36) 172.19.199.3 - - "GET /3.0/lists/listname(a)foo.bar/config HTTP/1.1" 200 2473 Sep 25 07:20:53 2017 (36) 172.19.199.3 - - "GET /3.0/lists/listname.foo.bar HTTP/1.1" 200 353 Sep 25 07:20:53 2017 (36) 172.19.199.3 - - "GET /3.0/lists/listname.foo.bar/roster/owner HTTP/1.1" 200 613 Sep 25 07:20:53 2017 (36) 172.19.199.3 - - "GET /3.0/lists/listname.foo.bar/roster/moderator HTTP/1.1" 200 617 Sep 25 07:20:53 2017 (36) 172.19.199.3 - - "GET /3.0/lists/listname.foo.bar HTTP/1.1" 200 353 Sep 25 07:20:53 2017 (36) 172.19.199.3 - - "GET /3.0/lists/listname(a)foo.bar/requests HTTP/1.1" 200 90 Sep 25 07:20:56 2017 (36) 172.19.199.3 - - "GET /3.0/lists/listname.foo.bar HTTP/1.1" 200 353 Sep 25 07:20:56 2017 (36) 172.19.199.3 - - "GET /3.0/lists/listname.foo.bar/roster/owner HTTP/1.1" 200 613 Sep 25 07:20:56 2017 (36) 172.19.199.3 - - "GET /3.0/lists/listname.foo.bar/roster/moderator HTTP/1.1" 200 617 Sep 25 07:20:57 2017 (36) 172.19.199.3 - - "GET /3.0/lists/listname(a)foo.bar/config HTTP/1.1" 200 2473 Sep 25 07:20:57 2017 (36) 172.19.199.3 - - "GET /3.0/lists/listname.foo.bar/archivers HTTP/1.1" 200 81 Sep 25 07:20:57 2017 (36) 172.19.199.3 - - "GET /3.0/lists/listname.foo.bar/archivers HTTP/1.1" 200 81 Sep 25 07:20:57 2017 (36) 172.19.199.3 - - "GET /3.0/lists/listname(a)foo.bar/requests HTTP/1.1" 200 90 Sep 25 07:20:57 2017 (35) Uncaught runner exception: 'str' object has no attribute 'decode' Sep 25 07:20:57 2017 (35) Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/usr/local/lib/python3.6/site-packages/mailman/core/pipelines.py", line 53, in process handler.process(mlist, msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/handlers/subject_prefix.py", line 174, in process mlist, msgdata, subject, prefix, prefix_pattern, ws) File "/usr/local/lib/python3.6/site-packages/mailman/handlers/subject_prefix.py", line 72, in all_same_charset chunks.append(chunk.decode(charset)) AttributeError: 'str' object has no attribute 'decode' Sep 25 07:20:57 2017 (35) SHUNTING: 1506324057.584686+a13cc47dc1027a0cfb00c892396b3ba7efabb3dc In addition, the log contains other trace backs that might or might not associate to this problem: Sep 24 21:11:27 2017 (34) Uncaught runner exception: 'ascii' codec can't encode character '\udcea' in position 3093: ordinal not in range(128) Sep 24 21:11:28 2017 (34) Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/runners/outgoing.py", line 93, in _dispose self._func(mlist, msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/mta/deliver.py", line 86, in deliver refused = agent.deliver(mlist, msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/mta/bulk.py", line 101, in deliver mlist, msg, msgdata, recipients) File "/usr/local/lib/python3.6/site-packages/mailman/mta/base.py", line 70, in _deliver_to_recipients sender, sorted(recipients), msg.as_string()) File "/usr/local/lib/python3.6/site-packages/mailman/mta/connection.py", line 84, in sendmail results = self._connection.sendmail(envsender, recipients, msgtext) File "/usr/local/lib/python3.6/smtplib.py", line 855, in sendmail msg = _fix_eols(msg).encode('ascii') UnicodeEncodeError: 'ascii' codec can't encode character '\udcea' in position 3093: ordinal not in range(128) Sep 24 21:11:28 2017 (34) SHUNTING: 1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66 ...¨ Sep 25 07:20:57 2017 (35) Uncaught runner exception: 'str' object has no attribute 'decode' Sep 25 07:20:57 2017 (35) Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/usr/local/lib/python3.6/site-packages/mailman/core/pipelines.py", line 53, in process handler.process(mlist, msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/handlers/subject_prefix.py", line 174, in process mlist, msgdata, subject, prefix, prefix_pattern, ws) File "/usr/local/lib/python3.6/site-packages/mailman/handlers/subject_prefix.py", line 72, in all_same_charset chunks.append(chunk.decode(charset)) AttributeError: 'str' object has no attribute 'decode' Sep 25 07:20:57 2017 (35) SHUNTING: 1506324057.584686+a13cc47dc1027a0cfb00c892396b3ba7efabb3dc ... Sep 25 09:19:58 2017 (30) deque: do_confirm_verify Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/usr/local/lib/python3.6/site-packages/mailman/app/subscriptions.py", line 420, in _step_send_confirmation raise StopIteration StopIteration ... Sep 26 09:21:07 2017 (36) deque: Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/usr/local/lib/python3.6/site-packages/mailman/app/subscriptions.py", line 217, in _step_sanity_checks MemberRole.member) mailman.interfaces.member.AlreadySubscribedError: sender(a)foo.bar is already a MemberRole.member of mailing list listname(a)listserver.foo.bar ... Sep 26 13:32:29 2017 (30) Uncaught runner exception: Sep 26 13:32:29 2017 (30) Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/runners/command.py", line 196, in _dispose mlist, msg, msgdata, parts, results) File "/usr/local/lib/python3.6/site-packages/mailman/commands/eml_confirm.py", line 53, in process mlist).confirm(token) File "/usr/local/lib/python3.6/site-packages/mailman/app/subscriptions.py", line 540, in confirm PendableUnsubscription.PEND_TYPE) AssertionError ... Sep 27 13:23:02 2017 (32) Uncaught runner exception: 'content-transfer-encoding' Sep 27 13:23:02 2017 (32) Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/runners/outgoing.py", line 93, in _dispose self._func(mlist, msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/mta/deliver.py", line 86, in deliver refused = agent.deliver(mlist, msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/mta/bulk.py", line 101, in deliver mlist, msg, msgdata, recipients) File "/usr/local/lib/python3.6/site-packages/mailman/mta/base.py", line 70, in _deliver_to_recipients sender, sorted(recipients), msg.as_string()) File "/usr/local/lib/python3.6/email/message.py", line 158, in as_string g.flatten(self, unixfrom=unixfrom) File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten self._write(msg) File "/usr/local/lib/python3.6/email/generator.py", line 181, in _write self._dispatch(msg) File "/usr/local/lib/python3.6/email/generator.py", line 214, in _dispatch meth(msg) File "/usr/local/lib/python3.6/email/generator.py", line 272, in _handle_multipart g.flatten(part, unixfrom=False, linesep=self._NL) File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten self._write(msg) File "/usr/local/lib/python3.6/email/generator.py", line 181, in _write self._dispatch(msg) File "/usr/local/lib/python3.6/email/generator.py", line 214, in _dispatch meth(msg) File "/usr/local/lib/python3.6/email/generator.py", line 358, in _handle_message g.flatten(msg.get_payload(0), unixfrom=False, linesep=self._NL) File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten self._write(msg) File "/usr/local/lib/python3.6/email/generator.py", line 189, in _write msg.replace_header('content-transfer-encoding', munge_cte[0]) File "/usr/local/lib/python3.6/email/message.py", line 558, in replace_header raise KeyError(_name) KeyError: 'content-transfer-encoding' Sep 27 13:23:02 2017 (32) SHUNTING: 1506518582.300981+aa68949ca566c7170a81a0bd643cee803f29c312

5 11

The msgtext argument in 'self._connection.sendmail(envsender, recipients, msgtext)' is supposed to be a string containing only ascii characters.
by Henrik Rasmussen 03 Oct '17

03 Oct '17

Hi Mark. This was originally from another thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…, but as it isn't related to the problem in the thread, I'll split it in another thread. On 09/29/2017 05:46 AM Mark Sapiro wrote: >> In addition, the log contains other trace backs that might or might not associate to this problem: >> >> Sep 24 21:11:27 2017 (34) Uncaught runner exception: 'ascii' codec can't encode character '\udcea' in position 3093: ordinal not in range(128) >> Sep 24 21:11:28 2017 (34) Traceback (most recent call last): >> File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration >> self._process_one_file(msg, msgdata) >> File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file >> keepqueued = self._dispose(mlist, msg, msgdata) >> File "/usr/local/lib/python3.6/site-packages/mailman/runners/outgoing.py", line 93, in _dispose >> self._func(mlist, msg, msgdata) >> File "/usr/local/lib/python3.6/site-packages/mailman/mta/deliver.py", line 86, in deliver >> refused = agent.deliver(mlist, msg, msgdata) >> File "/usr/local/lib/python3.6/site-packages/mailman/mta/bulk.py", line 101, in deliver >> mlist, msg, msgdata, recipients) >> File "/usr/local/lib/python3.6/site-packages/mailman/mta/base.py", line 70, in _deliver_to_recipients >> sender, sorted(recipients), msg.as_string()) >> File "/usr/local/lib/python3.6/site-packages/mailman/mta/connection.py", line 84, in sendmail >> results = self._connection.sendmail(envsender, recipients, msgtext) >> File "/usr/local/lib/python3.6/smtplib.py", line 855, in sendmail >> msg = _fix_eols(msg).encode('ascii') >> UnicodeEncodeError: 'ascii' codec can't encode character '\udcea' in position 3093: ordinal not in range(128) >> Sep 24 21:11:28 2017 (34) SHUNTING: 1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66 > > > This may be a bug. The msgtext argument in > 'self._connection.sendmail(envsender, recipients, msgtext)' is supposed > to be a string containing only ascii characters. I'm interested in > what's in Mailman's > var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck. > You may be able to print the contents with Mailman's > > bin/mailman queue > var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck > > There shouldn't be raw unicodes like \udcea in the text of the message, > but we should defend against that anyway. [root@lstapp01pl ~]# docker exec -it mailman-core mailman qfile var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck [----- start pickle -----] <----- start object 1 -----> Traceback (most recent call last): File "/usr/local/bin/mailman", line 11, in <module> sys.exit(main()) File "/usr/local/lib/python3.6/site-packages/mailman/bin/mailman.py", line 100, in main args.func(args) File "/usr/local/lib/python3.6/site-packages/mailman/commands/cli_qfile.py", line 81, in process printer.pprint(obj) File "/usr/local/lib/python3.6/pprint.py", line 139, in pprint self._format(object, self._stream, 0, 0, {}, 0) File "/usr/local/lib/python3.6/pprint.py", line 176, in _format stream.write(rep) UnicodeEncodeError: 'utf-8' codec can't encode character '\udcea' in position 3025: surrogates not allowed -- Henrik Rasmussen <her(a)adm.ku.dk> University of Copenhagen, Danmark

2 1

Something wrong with my Hyperkitty base_url?
by Andrew Hodder 02 Oct '17

02 Oct '17

Finally have everything stood up and working, except for HyperKitty mailman plugin. I'm getting a path issue of sorts I can see in the archiver.log (have it set to debug log level in the mailman core): Oct 02 19:12:37 2017 (8144) Traceback (most recent call last): File "/opt/mailman/venv3/lib/python3.4/site-packages/mailman_hyperkitty-1.0.2-py3.4.egg/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/venv3/lib/python3.4/site-packages/mailman_hyperkitty-1.0.2-py3.4.egg/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError: <h1>Not Found</h1><p>The requested URL /archives/api/mailman/archive was not found on this server.</p> My base_url in the mailman-hyperkitty.cfg: base_url: http://localhost:8002/archives I've tried changing localhost to the FQDN but that just gives different errors (where it can't even attempt to exchange the secret, so I know at least that part is working. Just this '/archives/api/mailman/archive' path I'm head scratching at. I've tried removing the /archives off the end, no change though. Any thoughts/help would be appreciated, thanks! Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541

2 4

question about recommended postfix configuration
by Marc Sluiter 02 Oct '17

02 Oct '17

Hi, im trying to setup mailman and have an issue: first my environment: - I’m running postfix etc with "mailcow-dockerized": https://mailcow.github.io/mailcow-dockerized-docs/ - I’m running mailman with "docker-mailman": https://asynchronous.in/docker-mailman/ I got almost everything working besides confirm mails (see my other mail), but I had to use another postfix configuration than recommended, I’m wondering why the recommended way didn’t work. Sidenote: I’m not a postfix expert. This is recommended: transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp relay_domains = regexp:/opt/mailman/core/var/data/postfix_domains This didn’t work, all mails to mailman were rejected. Postfix did not even check the “local_recipient_maps”. After a lot of reading that made sense to me, because when I understand it correctly, “local_recipient_maps” is only checked for domains in “mydestinations”. And there I only have localhost. My first change then was to use “relay_recipient_maps” instead of “local_recipient_maps”, because the domains were also added to the relay configuration "relay_domains". That worked. But then I noticed warnings by postfix about having the same domain in “virtual_mailbox_domains” and “relay_domains”. Made sense again because I used the same domain in my “normal” mail setup (with “virtual_mailbox_domains”) and in mailman. So finally I ended up with adding the mailman files to “virtual_mailbox_domains” and “virtual_mailbox_maps” instead of “relay_domains” and “local_recipient_maps”. Do my findings and changes make sense to you? Or do I miss something important? Good thing is that at least “transport_maps” worked for whatever configuration I used :) Thanks and greetings, Marc

2 1

default language ignored
by Marc Sluiter 02 Oct '17

02 Oct '17

Hi, one last question for now: how do switch the language of the mails sent by mailman? I have this in my configuration, but without effect: [language.de] charset: iso-8859-1 [language.de] description: German [language.de] enabled: yes [mailman] default_language: de Is it also possible to change the language for a single list? Greetings, Marc

2 1

Confirmation email bounces because of listname+something@example.com
by thor.rustad＠gmail.com 02 Oct '17

02 Oct '17

I'm sure this is a small configuration error, but I have followed the instructions for mailman3 and postfix. Basically mailman works fine, but confirmation emails, when answered by the subscriber or would-be subscriber, fails because 'listname' (after the '+something' is stripped off) is not a local user. Also see my post to the postfix group: http://postfix.1071664.n5.nabble.com/address-extension-fails-for-mailman-td…. Mind you, the postfix local_recipient_maps=regexp:/path/postfix_lmtp will correctly match any of the lists, but once the <+something> is added to the listname, it fails. Note that I have configured a subdomain, klubb.domain.com, for my mailing lists. First, my postfix.cf: recipient_delimiter = + smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) biff = no append_dot_mydomain = no readme_directory = no smtpd_tls_cert_file=/etc/letsencrypt/live/mailer.example.com/cert.pem smtpd_tls_key_file=/etc/letsencrypt/live/mailer.example.com/privkey.pem smtpd_use_tls=yes smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_helo_restrictions = permit_mynetworks, permit_sasl_authenticated smtpd_sender_restrictions = permit_mynetworks, reject_non_fqdn_sender, reject_unknown_sender_domain smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, smtpd_tls_security_level = may smtp_tls_security_level = may smtp_tls_loglevel = 2 smtpd_tls_loglevel = 2 smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, defer_unauth_destination mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 172.19.199.0/24 <public.ip>/32 myhostname = mailer.example.com mydomain = example.com alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases myorigin = mailer.example.com mydestination = klubb.$mydomain, localhost.$mydomain, localhost, $myhostname, $mydomain relayhost = mailbox_size_limit = 0 inet_interfaces = all inet_protocols = all compatibility_level = 2 transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp relay_domains = regexp:/opt/mailman/core/var/data/postfix_domains unknown_local_recipient_reject_code = 550 owner_request_special = no propagate_unmatched_extensions = canonical, virtual, alias, forward, include Here is the line in postfix mail.log where the valid listname+token is rejected: NOQUEUE: reject: RCPT from mail-lf0-f43.google.com[209.85.215.43]: 550 5.1.1 <abcliste-confirm+79ecdc9fe57e086b8e1335299ef5255d156b72db(a)klubb.example.com>: Recipient address rejected: User unknown in local recipient table; from=<me(a)mydomain.com> to=<abcliste-confirm+79ecdc9fe57e086b8e1335299ef5255d156b72db(a)klubb.example.com> proto=ESMTP helo=<mail-lf0-f43.google.com> Any help will be appreciated.

2 1

Confirmation email bounces because of listname+something@example.com
by Thor Atle Rustad 02 Oct '17

02 Oct '17

I'm sure this is a small configuration error, but I have followed the instructions for mailman3 and postfix. Basically mailman works fine, but confirmation emails, when answered by the subscriber or would-be subscriber, fails because 'listname' (after the '+something' is stripped off) is not a local user. Also see my post to the postfix group: http://postfix.1071664.n5.nabble.com/address-extension-fails-for-mailman-td… . Mind you, the postfix local_recipient_maps=regexp:/path/postfix_lmtp will correctly match any of the lists, but once the <+something> is added to the listname, it fails. Note that I have configured a subdomain, klubb.domain.com, for my mailing lists. First, my postfix.cf: recipient_delimiter = + smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) biff = no append_dot_mydomain = no readme_directory = no smtpd_tls_cert_file=/etc/letsencrypt/live/mailer.example.com/cert.pem smtpd_tls_key_file=/etc/letsencrypt/live/mailer.example.com/privkey.pem smtpd_use_tls=yes smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_helo_restrictions = permit_mynetworks, permit_sasl_authenticated smtpd_sender_restrictions = permit_mynetworks, reject_non_fqdn_sender, reject_unknown_sender_domain smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, smtpd_tls_security_level = may smtp_tls_security_level = may smtp_tls_loglevel = 2 smtpd_tls_loglevel = 2 smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, defer_unauth_destination mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 172.19.199.0/24 <public.ip>/32 myhostname = mailer.example.com mydomain = example.com alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases myorigin = mailer.example.com mydestination = klubb.$mydomain, localhost.$mydomain, localhost, $myhostname, $mydomain relayhost = mailbox_size_limit = 0 inet_interfaces = all inet_protocols = all compatibility_level = 2 transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp relay_domains = regexp:/opt/mailman/core/var/data/postfix_domains unknown_local_recipient_reject_code = 550 owner_request_special = no propagate_unmatched_extensions = canonical, virtual, alias, forward, include Here is the line in postfix mail.log where the valid listname+token is rejected: NOQUEUE: reject: RCPT from mail-lf0-f43.google.com[209.85.215.43]: 550 5.1.1 < abcliste-confirm+79ecdc9fe57e086b8e1335299ef5255d156b72db(a)klubb.example.com>: Recipient address rejected: User unknown in local recipient table; from=< me(a)mydomain.com> to=< abcliste-confirm+79ecdc9fe57e086b8e1335299ef5255d156b72db(a)klubb.example.com> proto=ESMTP helo=<mail-lf0-f43.google.com> Any help will be appreciated. Thor

2 1

"Private archives" aren't private
by Simon Liebold 29 Sep '17

29 Sep '17

Hello, #129 says that private lists are visible in the archive overview only but "archives aren't displayed". However, I can browse a private list's archives and read the mail text while not logged in. Shouldn't the private archive be hidden from anonymous users? Simon

6 10

"spoofing" mailing list address
by Dmitry Makovey 29 Sep '17

29 Sep '17

Hi, We're trying to migrate from 2.1.x to 3.1. In the process we want to modify old setup in which mailing lists were part of our normal mail domain (so both user accounts and ML would be under @x.stanford.edu) in new scenario we want to move ML into @lists.x.stanford.edu, yet preserve addressing compatibility with old naming scheme. To that end we thought of making following setup: list(a)x.stanford.edu -postfix:alias-> list(a)lists.x.stanford.edu however in this setup users will receive mail from the "unknown" domain for them so any filtering they've done will break. Is there a configuration change we can make for those old ML to spoof old ML emails? so they would look as if they came from list(a)x.stanford.edu ? -- Sr System and DevOps Engineer SoM IRT

1 0

Mailman only send some release messages to the subscribers
by Henrik Rasmussen 28 Sep '17

28 Sep '17

I have three list admins each maintaining one list, thus three lists: E, H and S. All reports that some mails they release from Held messages are sent, some isn't. In the logs (Mailman smtp.log and postfix log I can confirm that at least one of the lists (E) sent out another message to 559 recips at Sep 26 09:31:12 201 (UTC+2) so something is working. The admin of list E explains that she have released mails that came out, but some mails isn't sent when she reases them. Among others a mail she released Sep 26 09:38. I can also see in the Mailman Postfix log that Mailman received a mail from the Admin's e-mail address sender(a)foo.bar. Sep 26 09:38:49 postfix postfix/smtpd[5527]: D8E6D1109026: client=gateway[172.19.199.1] Sep 26 09:38:49 postfix postfix/cleanup[6076]: D8E6D1109026: message-id=<E7657360D6CFE64DBAC4E5D158511918873690FB(a)mailserver.foo.bar> Sep 26 09:38:49 postfix postfix/qmgr[139]: D8E6D1109026: from=<sender(a)foo.bar>, size=19589, nrcpt=1 (queue active) Sep 26 09:38:49 postfix postfix/lmtp[6077]: D8E6D1109026: to=<s(a)listserver.foo.bar>, relay=172.19.199.2[172.19.199.2]:8024, delay=0.03, delays=0.01/0.01/0/0.01, dsn=2.0.0, status=sent (250 Ok) Sep 26 09:38:49 postfix postfix/qmgr[139]: D8E6D1109026: removed I cannot find the mail-id in the Mailman smtp.log, however in the smtp.log I found that the mail was received Sep 26 09:38:49 2017 (32) Peer: ('172.19.199.5', 49238) Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) handling connection Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) Data: b'LHLO mailgateway.foo.bar' Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) Data: b'MAIL FROM:<sender(a)foo.bar>' Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) sender: sender(a)foo.bar Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) Data: b'RCPT TO:<s(a)listserver.foo.bar>' Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) recip: s(a)listserver.foo.bar Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) Data: b'DATA' Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) Data: b'QUIT' Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) connection lost Sep 26 09:38:49 2017 (32) Connection lost during _handle_client() I don't see any release of the held mail not that it was sent out. Two hours later I see a a log message about a notification mail to the admin that another mail had been held, but not anything about the released mail neither in thge smtp.log nor the postfix log. I don't know why it only works sometimes. -- Henrik Rasmussen <her(a)adm.ku.dk<mailto:her@adm.ku.dk>> University of Copenhagen, Danmark

1 2

mailman-cli tools
by Dmitry Makovey 27 Sep '17

27 Sep '17

I've come across mailman-cli docs: http://mailman-cli.readthedocs.io/en/latest/src/mailmanclient/cli/docs/usin… yet I cannot figure out what's the official source for the installation. Rabbit hole of links lead me to https://github.com/rajeevs1992/mailmancli which suggests: sudo pip install mailman.client and that doesn't work. I also did: pip install mailmanclient in hopes that it comes with CLI tools, but it looks like it is only the library. Am I looking in wrong places or is it that mailman3 cli tools are "not there"? -- Sr System and DevOps Engineer SoM IRT

3 5

HyperKitty: Thread matching query does not exist
by C. R. Oldham 26 Sep '17

26 Sep '17

Greetings, I have an active list for which I am trying to debug some deliverability issues. When a user tells me that folks aren't getting their postings, I check the archives first. In this case, I am getting a traceback saying "thread matching query does not exist" when I try to go to the HyperKitty page for the list. How can I debug this? I am using Mailman 3 via the Docker containers documented here: https://asynchronous.in/docker-mailman/ The container versions appear to be 0.1. --cro

3 3

Upgrade path
by David Krantz 23 Sep '17

23 Sep '17

Hi. I currently run MM3.0 based on the old bundle installation. It seems to work just fine although with a number of minor and major annoyances that probably have been fixed now. What is the rekommended way to upgrade to the newest version? (newest _usable_ version, of course)? Is it docker-only with a migration from the current solution to a docker based? If so, any ideas or pointers on how to go about this? Cheers // David

2 2

mailman 3 adding extraneous /var/ to pid path?
by Andrew Hodder 21 Sep '17

21 Sep '17

I'm not sure if this is a bug, or if I've configured something I'm unable to find doing this. But when I'm attempting to stop my mailman3 process, I keep getting an extra /var/ appending into the pid path, so it never finds the PID to terminate. Here are some examples, run at different times, some with different -C configs to launch, all worked successfully to start, this is only a problem on the stop.: (venv3) [root@mailman3(on1) venv3]# mailman stop Shutting down Mailman's master runner PID unreadable in: /opt/mailman/venv3/var/master.pid [Errno 2] No such file or directory: '/opt/mailman/venv3/var/master.pid' Is the master even running? (venv3) [root@mailman3(on1) var]# mailman stop Shutting down Mailman's master runner PID unreadable in: /opt/mailman/var/var/master.pid [Errno 2] No such file or directory: '/opt/mailman/var/var/master.pid' (venv3) [root@mailman3(on1) var]# mailman stop Shutting down Mailman's master runner PID unreadable in: /opt/mailman/var/etc/var/var/master.pid [Errno 2] No such file or directory: '/opt/mailman/var/etc/var/var/master.pid' I keep getting around this by creating symlinks to the pid file and then the stop works, but it's getting silly. It seems like mailman just assumes CWD + /var/ + master.pid must be the location. Once I realized this, I found I can do "mailman stop" so long as I'm only in /opt/mailman/ (since it'd then add /var/master.pid). But that seems a little nonsensical. Going to try my hand at using the environment variables MAILMAN_CONFIG_FILE and MAILMAN_VAR_DIR, maybe that will sort this out. But if anyone can explain further, it'd be appreciated. Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541

4 3

Change Base URI for Mailman 3.1
by Dmitry Makovey 21 Sep '17

21 Sep '17

I'm tinkering with docker container of mailman 3.1 however I'm trying to utilize existing nginx server thus I need to map "/mailman" to mailman-web docker container vs default "/" mapping. Where do I configure base URI for mailman-web ? (quick search of archives and googling didn't yield any positive results thus far) -- Sr System and DevOps Engineer SoM IRT

2 1

Mailman List Lost on URL transfer
by heartsandbones＠zoho.com 20 Sep '17

20 Sep '17

Hello Mailman Forum! I hope you all can help me. I have been banging my head against this issue for weeks. Here’s the scoop: I did a web site redesign for a non-profit. They didn’t mention to me that they had a mailman list associated with the site. When we transferred the url to Squarespace their list quakers(a)sbfriends.org stopped functioning and the administration login link: http://mail.sbfriends.org/mailman/admin/quakers_sbfriends.org results in a “server not found” error. I don’t know how to set up the site so that their mailman list works again. Please tell me exactly what to do to make this work. Let me know if I can provide any additional information to help you help me. This is my first post to this forum, so I hope I’ve done so correctly. Thanks so much! Licity

2 1

Log for outgoing e-mails
by Henrik Rasmussen 20 Sep '17

20 Sep '17

Docker mailman 0.1.1 Where is outgoing e-mails logged? Where can I see who it was sent to? On my test list I subscribed a new member (say recipient(a)hotmail.com) using Mass operation subscription. From another e-mail, not subscribed to the list (say sender(a)example.ku.dk) I sent a mail to the list which was held as expected. The message was logged in /opt/mailman/core/var/logs/smtp.log. When I released the mail, the newcoming member recipient(a)hotmail.com received the mail as expected, but I don’t see any log messages that the mail was sent other than: Sep 20 11:50:52 2017 (34) <6DCC3E5DA06FE346B4DE4876C4F2713D019BB70E39(a)foo.bar> smtp to testlist(a)mailman3.ku.dk for 1 recips, completed in 0.052258968353271484 seconds Sep 20 11:50:52 2017 (34) <6DCC3E5DA06FE346B4DE4876C4F2713D019BB70E39(a)foo.bar> post to testlist(a)mailman3.ku.dk from sender(a)example.ku.dk, 13041 bytes -- Henrik Rasmussen <her(a)adm.ku.dk> University of Copenhagen, Danmark

2 1

restrict sending to owner/moderator
by m.dohmen＠xconnect.de 20 Sep '17

20 Sep '17

Hello, I'd like to restrict message acceptance on a per-list basis to the owner or moderator, so that simple subscribers cannot send messages to the list. But I don't want the owner/moderator having to moderate own messages, so the member setting "hold for moderation" in Postorius isn't applicable. Is there a way to do this?

3 2

Deleting archives
by Henrik Rasmussen 14 Sep '17

14 Sep '17

Docker-mailman 0.1: I have deleted some lists that I used for testing, but Hyperkitty seems to preserve the archives in the Available lists. Clicking on a list archive gets me to the archive of that list (with no posts because I haven't posted anything to the list). The URL is https://[WEBSITE]/hyperkitty/list/[LISTNAME](a)[LISTDOMAIN]/<https://[WEBSITE]/hyperkitty/list/%5bLISTNAME%5d(a)%5bLISTDOMAIN%5d/> (with a (a)), but when I click Manage subscription, the URI changes to https://[WEBSITE]/postorius/lists/[LISTNAME].[LIST<https://[WEBSITE]/postorius/lists/%5bLISTNAME%5d.%5bLIST>DOMAIN/ (with a dot instead of (a) which seems normal behavior) and I get a "Not Found The requested URL /postorius/lists/[LISTNAME]DOT[LISTDOMAIN]/ was not found on this server. " error. Of course I can't manage the subscription for a list I have deleted, but shouldn't the archive for a list be deleted along deleting the list. Henrik Rasmussen

1 1

Installing mm3 with docker
by Tom Browder 10 Sep '17

10 Sep '17

I am trying to follow instructions but when I get to the actual docker pull command (with trust enabled): # docker pull maxking/mailman-core:release I get an error message: No trust data for release I have tried adding various tags but no changes. What am I doing wrong? Thanks. -Tom

2 4

Mailman 3 bounce handling and DKIM mitigation
by David Krantz 05 Sep '17

05 Sep '17

Hi, I have a question on bounce handling. I get the impression that bounces are just lost and neither handled nor forwarded to the list admin. Is this a known problem? I am running mailman from git, but about version 3.1 and use postfix. I find lots of things in the bounceevents table. Is there any way to find out more on these events? I probably can configure postfix to send listname-bounce@domain to an admin adress. Or for that matter hack mailman to send it to the correct admin. Also the DKIM mitigation does not seem to detect DKIM domains. If I force the mitigation for all mails it works but that of course has annoying consequences although mostly cosmetic. This has caused quite a number of bounces for my lists (as well as being temporarily banned by at least Microsoft). I'm thinking of upgrading to a later version. What is the latest version that might be a good idea to install today? I install from gitlab. cheers // David

2 1

Social Auth, howto?
by Claus-Justus Heine 02 Sep '17

02 Sep '17

Hi, sorry, this seems to be a Django stuff, but how do I enable this social auth stuff? I get the following Fedora: gives me a login screen (ok) Yahoo: gives me a login screen and lots of commercials (ok) OpenId: gives me a possibility to sign up or in (ok) Github: internal server error 500, Django log: DoesNotExist: SocialApp matching query does not exist. Same with GitLab and Google. Ok, seemingly I need to do something to make it work, has anyone a link to some snippet of documentation of example setup? Thanks Claus -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

2 1

Moderation requests, dash-board link in notification?
by Claus-Justus Heine 02 Sep '17

02 Sep '17

Hi there, I suppose this is rather a simple configuration issue. However, with Mailman v2 the moderator or list-owner was supplied with a link to the admin-site in the moderation-reminder. I suppose that this can also be very easily configured with v3? Of course, I know where my amdin-site is, but I am planning to deploy mm3 in a setting with educated dummy users which probably would rather first ask and only try to find out by themselves if they cannot find someone to ask. Cheers Claus -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

2 1

Funny responds to subscriptions emails
by Claus-Justus Heine 02 Sep '17

02 Sep '17

Playing around with mailman3 I get funny responds from the list-manager to subscription requests. I have set up a "playground" list (guess why) and trying to subscribe via email. Basically, things work. However, the end-user (me) gets confusing responses. I would not care for myself, but ... What I did: send an Email > To: playground <playground-subscribe(a)lists.claus-justus-heine.de> > From: Claus-Justus Heine <Claus-Justus.Heine(a)IANS.Uni-Stuttgart.DE> > Subject: Test So far so good. I get the expected confirmation email with subject confirm 3093b4 etc etc etc But I also get a second rather confusing email: > The results of your email command are provided below. > > - Original message details: > From: Claus-Justus Heine <Claus-Justus.Heine(a)IANS.Uni-Stuttgart.DE> > Subject: Test > Date: Sat, 2 Sep 2017 22:24:08 +0200 > Message-ID: <44151460-05a8-4c35-e0d4-646efe3cf234(a)IANS.Uni-Stuttgart.DE> > > - Results: > Confirmation email sent to Claus-Justus Heine <Claus-Justus.Heine(a)IANS.Uni-Stuttgart.DE> > No such command: Test > No such command: --=20 > No such command: Claus-Justus > No such command: f=C3=BCr > No such command: Numerische > No such command: Stuttgart > No such command: +49 > No such command: +49 > > - Done. BTW, I also got the same confusing email when subscribing to mailman-users(a)mailman3.org (is attached). Can this be switched off? I don't care for myself, but if you think that this software is ready for production, then end-users should not receive such kind of """"things"""" Regards Claus -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

2 1

Mailman3 Docker question and importing lists from MM2
by Andrew Hodgson 02 Sep '17

02 Sep '17

Hi, Started experimenting with the Docker images at https://github.com/maxking/docker-mailman/. I had a question regarding the parameter: SERVE_FROM_DOMAIN. I want to use multiple domains, what is the best way to specify multiple domains in this environment variable? I tried it without the environment set, and also with some variables like: SERVE_FROM_DOMAIN=['lists.domain.com', 'lists.domain2.com'] and SERVE_FROM_DOMAIN="lists.domain1.com", "lists.domain2.com" However I still only get the example.com site. Furthermore, is there a recommended way to get data from MM2 (list configs and archives) into MM3? Thanks. Andrew.

4 11

Help request, almost got it going, but ....
by Claus-Justus Heine 02 Sep '17

02 Sep '17

First: thanks for all those development work, I am aware of the fact that this is free software and most of the development probably happened in someones spare-time. I have some problems: - I tried to install mailman v3. "Read the (non) docs" was of little help, but I got to some partly success following the commands in the scripts in the docker image at https://github.com/maxking/docker-mailman Things seemed to work out, I generated a test-list "Playground" and now I am just in the progress to click through all the configuration options in the the postorius Web-GUI. So far so good Now I read the "Message Acceptance" tab AND here is the problem: Seemingly, at some point in the deep dungeons of the source code the "Acceptable aliases" Text-Box is not interpreted correctly. Specifically, at the start it contains the string [] When then changing something int the "Message Acceptance" tab, an error shows up in the web-page (but no-where in the logs) "An error occured: []" and the bogus [] is restored. I tried to dig into the source code, and well, the data source of the text-field is an array or list of acceptable email-adresses. But seemingly finally at some point in the source code an empty list is not converted to the empty string, but to the string []. I can get rid of the error message "An error occured: []" by inserting an email-at '@' at just some place in the input box, this yields (clicking "Save changes" again and againg ...): [u"[u'@']"] [u'[u\'[u"[u\\\'@\\\']"]\']'] [u'[u\'[u\\\'[u\\\\\\\'[u"[u\\\\\\\\\\\\\\\'@\\\\\\\\\\\\\\\']"]\\\\\\\']\\\']\']'] and so on. Unfortunately, I did not find the location of this bug, although I was finally able to add some "foobar" string to the already bogus web-output. Any help would be appreciated. BTW: * where is the bug-tracker for mailman3? * The documentation is really, well, close to non existent. Personally, I think the name of the URL "read-the-docs" is almost cynical. Guess I give up on it, it just does not seem to be ready for production. This was (following the docker stuff at githb) with Pythong3: mailman==3.1.0 mailman-hyperkitty==1.1.0 Python2: mailmanclient==3.1.0 postorius==1.1.0 hyperkitty==1.1.1 django-mailman3==1.1.0 Here I realize a slight version difference between the hyperkitty stuff. But this is a bug in postorius. So what. Thanks for any help, cheers Claus -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

3 7

Acceptable aliases defaults to []
by Henrik Rasmussen 30 Aug '17

30 Aug '17

* Docker-mail 0.1.1 * Mailman 3.1 * Postorius 1.1.1 * Hyperkitty 1.1.1 Minor issues: Settings -> Message Acceptance -> Acceptable aliases has a default of [] resulting in "An error occured: [u'[]']" when saving. This fiend should be empty by default or at least accept the default when saving. To me the description right under the Acceptable aliases field is not user friendly. It doesn't explain the purpose of the field, but is meant for the Mailman sysadmin, not the list admin who can't be expected to understand this. A much better description would be the ones used for MM2: * http://www.list.org/mailman-admin/node23.html * https://wiki.list.org/DOC/What%20does%20%22message%20has%20implicit%20desti… On a second note: Where I can change the field and message descriptions in MM3, like the /usr/lib/mailman/messages/[sprog]/LC_MESSAGES/mailman.po in MM2? -- Henrik Rasmussen <her(a)adm.ku.dk<mailto:her@adm.ku.dk>> Copenhagen, Danmark

4 4

Moving mm2 mail archives to mm3
by Tom Browder 29 Aug '17

29 Aug '17

Is there any way to move my old mm2 archives to mm3? Thanks. -Tom

4 4

Only first message displayed... sometimes
by Cameron Smith 28 Aug '17

28 Aug '17

(With the hope that someone on the list can help me diagnose this problem, I’m posting a copy of the HyperKitty issue that I opened a few days ago: https://gitlab.com/mailman/hyperkitty/issues/151.) Testing MailMan3, installed using the Docker containers 0.1.1 (with HyperKitty 1.1.1): I have two lists with several discussions in each. The participants/comments stats for all discussions show multiple participants and multiple comments. (Note that the numbers are wrong, as discussed in #149.) However, when I open a discussion, some of them only display the first message. Others display all messages, one displays only some, but not all, of the messages. In one case, the discussion showed the top two messages, but when a new message was added, it briefly showed and then it and the second message suddenly disappeared, leaving only the first message. In another case, the discussion only showed the top message, but then, for no apparent reason, the rest of the messages appeared. —— I decided to start all over, removing the Docker containers and images, as well as the existing database... all gone. With the newly created system and database, I created two new lists and three member-subscribers. I then created new threads and added several messages to the new threads. The messages came from all three of the members and were entered via email and HyperKitty. One thread was created from within HyperKitty. All of the newly created threads are displaying the same behaviour: all of the subscribers received, via email, all of the messages, but only the first message of each thread is displayed in HyperKitty. Suggestions for how to trace/diagnose the problem would be appreciated. Cameron Smith

1 0

Re: Which documentation to follow for installation
by Ruben Ibanez 28 Aug '17

28 Aug '17

Hi Abhilash, Finally we decided to install Mailman through the docker images provided by you (https://github.com/maxking/docker-mailman). The deployment was very quick, and it works flawlessly, so we will keep this solution. On the side I will try to deploy Mailman 3 through its independent modules, just for fun :) Many thanks! Cheers, R. From: "Abhilash Raj" <maxking(a)asynchronous.in> To: "Ruben Ibanez" <ribanez(a)sciops.esa.int> Cc: "mailman-users" <mailman-users(a)mailman3.org> Sent: Sunday, August 20, 2017 11:25:34 PM Subject: Re: [MM3-users] Which documentation to follow for installation On Sun, 20 Aug 2017 20:50:39 +0200 (CEST) Ruben Ibanez <ribanez(a)sciops.esa.int> wrote: > Hi Abhilash, > > Thanks for your reply. > > The point is, I think I'm missing something. I'm just a sysadmin who wants to deploy Mailman 3.x to be used for an operational environment, like any other software. Is this software actually ready for that? There are production environments running Mailman 3.1 right now if that is your questions, see https://lists.mailman3.org. Although, I guess you already saw that when subscribing to this list ;) > Of course, I'm not asking for .rpm, .deb, etc... because I understand that's > quite complex, but I tried it following all available guides, including the > Contributor's Guide, and it seems impossible to get it running at the first > time (or just to get it running) without getting crazy or fixing lots of > unexpected errors during installation. It would be helpful if you send in those errors here. It will help us debug your problem and also improve the guide for the people using it in future. One small problem about the configuration, off the top of my head, can cause some problems in the "Mailman Suite Installation" Guide[1]. I have that on my todo to fix. But, apart from that everything else should work! [1]: http://docs.mailman3.org/en/latest/prodsetup.html You would have to do some additional configuration for the web frontend to work and for the mail servers to talk to Mailman and Frontend separately, both of which is also mentioned in the documentation under "Configuring Mailman Core" and "Configure Web Frontend". Contributor's guide is not focused on deploying but just setting it up locally to play with and modify the source itself. > Have you tried to deploy Mailman 3.x strictly following the documentation? I think people have used it in past to successfully deploy Mailman 3.x, but without looking at the errors you are facing I don't have any clue as to why it doesn't work for you! > > By the way, many thanks for your hard work! > > Cheers, > RI > > > From: "Abhilash Raj" <maxking(a)asynchronous.in> > To: ribanez(a)sciops.esa.int > Cc: mailman-users(a)mailman3.org > Sent: Saturday, August 19, 2017 8:55:20 AM > Subject: Re: [MM3-users] Which documentation to follow for installation > > On Fri, 18 Aug 2017 09:40:37 -0000 > ribanez(a)sciops.esa.int wrote: > > > Hi everyone, > > > > I'm trying to deploy Mailman 3.1, but it seems there isn't a clear place to > > look for documentation. I found two different sites: > > > > https://mailman.readthedocs.io/en/latest/ > > http://docs.mailman3.org/en/latest/ > > Both of the above are actually latest documentation, > > docs.mailman3.org should be the one to look for installations guidelines for > the entire Mailman 3.x Suite, > > mailman.readthedocs.io is the documentation of Mailman 3 Core, which handles > the mail. > > http://docs.mailman3.org/en/latest/prodsetup.html > > This should be the best place to start, be sure to look at the Pre-Installation > Guide if you are new to the Python ecosystem. > > > > > Do you know which one should be followed? Both at the same time? I find it > > quite unclear... and this installation will be for an operational environment. > > > > Also, there are some (official?...) docker images, but all images are for > > mailman 3.0 but not mailman 3.1, and of course updates are not guaranteed. > > It is meant for Mailman 3.X series and is maintained by me. It currently > includes the latest releases for all the Mailman's sub-projects, also Mailman > 3.1. > > > Hope that helps! > > -- thanks, Abhilash Raj This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender. Please consider the environment before printing this email.

1 0

Bounce processing
by Mark Ziranski 26 Aug '17

26 Aug '17

Hello, I read that mailman3 supports 'bounce processing' but I do not know how to configure it. I want to delete members automatically from a mailing list if the delivery has failed after a certain time of attempts because his mailbox has been removed or his mail server has been shutdown etc. There is also the case that an users mailbox is full (mailbox limit exceeded). Is possible to deal with this case too? Thanks.

3 4

HyperKitty misreporting statistics
by Cameron Smith 24 Aug '17

24 Aug '17

Mailman 3, container images 0.1.1 HyperKitty 1.1.1 is showing incorrect numbers for the number of participants and the number of discussions. (All messages referred to below were submitted in August.) In one list, I have two threads. In one thread, I have three messages, each from a different email address, all submitted via email (as opposed to replying from within HyperKitty). The month page (clicking on “August”) of that list however, shows that thread as having one participant and no messages. Opening the list shows the same stats: “1 participants”, “0 comments”; all three messages are displayed. The other thread in the same list also shows one participant and no messages; it has two messages in it, one submitted via email, the other submitted via HyperKitty by a different subscriber. Opening the list shows both messages. The front page of that list shows zero participants and two discussions. A second list also has two threads with three email-submitted messages from different addresses. The monthly stats show one thread as having one participant and one message, the other as having one participant and zero messages. The front page shows one participant and one discussion. Cameron Smith

2 6

Users, members, accounts and subscribers
by Cameron Smith 24 Aug '17

24 Aug '17

Oh my! In an attempt to introduce a friend to MailMan3, I had her subscribe to a couple of lists that I set up and we exchanged a few messages via the email interface. Then I introduced her to the web interface and we were both confused when she could not log-in/sign-in and was told that her email address was not recognized. It was only later that I realized that while she was a subscriber, she hadn’t yet signed up for an account. What is the point of “accounts"? Why can someone become a subscriber, but not have an account? I find the user/member/subscriber explanation at http://mailman.readthedocs.io/en/latest/src/mailman/docs/architecture.html to be very confusing. Cameron Smith

3 3

Setting default Mailman admin (Django superuser) password in Docker-mailman
by Henrik Rasmussen 23 Aug '17

23 Aug '17

I just upgraded to Docker-mailman 0.1.1 and prior to that for some reason I had to somewhat start over, deleting my database. At both on my first and second attempt I wondered what the Django admin password would be. According to https://github.com/maxking/docker-mailman/ and https://github.com/maxking/docker-mailman/blob/master/web/README.md, setting MAILMAN_ADMIN_USER and MAILMAN_ADMIN_EMAIL in docker-compose.yaml will create a username for the admin user by default, but it doesn't mentioning setting a variable for the password. Creating a superuser using docker exec -it mailman-web python manage.py createsuperuser would normally request the password for the user indicated, but user "mailman" has already been registred. So to get to know the superuser password, I reset it using https://stackoverflow.com/questions/6358030/how-to-reset-django-admin-passw…. Why don't the installation guide on https://github.com/maxking/docker-mailman/ mention anything about how to set the password in the docker-compose.yaml file? -- Henrik Rasmussen <her(a)adm.ku.dk<mailto:her@adm.ku.dk>> Copenhagen, Danmark

2 1

Possible bug in Mailman 3.1 (Docker-mailman 0.1)
by Henrik Rasmussen 21 Aug '17

21 Aug '17

Mailman 3.1, docker-mailman 0.1 While I was trying to automate distribution of the files in /opt/mailman/core/var/data/postfix_domains I found what I think must be a bug. Adding a new mail list (or deleting one) _does_ update the Postfix files /opt/mailman/core/var/data/ ,but adding a new mail domain does not. This is OK. But deleting a mail domain that have lists associated to it * does not issue a warning other than "Are you sure you want to permanently delete this domain?" which is not different from deleting mail domains without lists associated to it. * the associated lists disappears both from the web interface Lists view and from the output of the "docker exec -it mailman-core mailman lists" command * the files in /opt/mailman/core/var/data/ is not updated even the lists is being deleted. 1. Deleting a mail domain with associated lists should issue a warning that it has lists associated to it. 2. The files in /opt/mailman/core/var/data/ should be updated according to the deleted lists / domains. 3. Actually I think it should be impossible to accidentally delete a mail domain with lists associated to it. Regards Henrik Rasmussen

2 2

Re: Which documentation to follow for installation
by Ruben Ibanez 20 Aug '17

20 Aug '17

Hi Abhilash, Thanks for your reply. The point is, I think I'm missing something. I'm just a sysadmin who wants to deploy Mailman 3.x to be used for an operational environment, like any other software. Is this software actually ready for that? Of course, I'm not asking for .rpm, .deb, etc... because I understand that's quite complex, but I tried it following all available guides, including the Contributor's Guide, and it seems impossible to get it running at the first time (or just to get it running) without getting crazy or fixing lots of unexpected errors during installation. Have you tried to deploy Mailman 3.x strictly following the documentation? By the way, many thanks for your hard work! Cheers, RI From: "Abhilash Raj" <maxking(a)asynchronous.in> To: ribanez(a)sciops.esa.int Cc: mailman-users(a)mailman3.org Sent: Saturday, August 19, 2017 8:55:20 AM Subject: Re: [MM3-users] Which documentation to follow for installation On Fri, 18 Aug 2017 09:40:37 -0000 ribanez(a)sciops.esa.int wrote: > Hi everyone, > > I'm trying to deploy Mailman 3.1, but it seems there isn't a clear place to > look for documentation. I found two different sites: > > https://mailman.readthedocs.io/en/latest/ > http://docs.mailman3.org/en/latest/ Both of the above are actually latest documentation, docs.mailman3.org should be the one to look for installations guidelines for the entire Mailman 3.x Suite, mailman.readthedocs.io is the documentation of Mailman 3 Core, which handles the mail. http://docs.mailman3.org/en/latest/prodsetup.html This should be the best place to start, be sure to look at the Pre-Installation Guide if you are new to the Python ecosystem. > > Do you know which one should be followed? Both at the same time? I find it > quite unclear... and this installation will be for an operational environment. > > Also, there are some (official?...) docker images, but all images are for > mailman 3.0 but not mailman 3.1, and of course updates are not guaranteed. It is meant for Mailman 3.X series and is maintained by me. It currently includes the latest releases for all the Mailman's sub-projects, also Mailman 3.1. Hope that helps! -- thanks, Abhilash Raj This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender. Please consider the environment before printing this email.

2 1

Which documentation to follow for installation
by ribanez＠sciops.esa.int 19 Aug '17

19 Aug '17

Hi everyone, I'm trying to deploy Mailman 3.1, but it seems there isn't a clear place to look for documentation. I found two different sites: https://mailman.readthedocs.io/en/latest/ http://docs.mailman3.org/en/latest/ Do you know which one should be followed? Both at the same time? I find it quite unclear... and this installation will be for an operational environment. Also, there are some (official?...) docker images, but all images are for mailman 3.0 but not mailman 3.1, and of course updates are not guaranteed. Thanks in advance! Regards, ribanez

2 1

Issues with starting mailman 3 outside of a virtualenv
by Leon 16 Aug '17

16 Aug '17

Hello, I wonder if this issue(https://gitlab.com/mailman/mailman/issues/3) was fixed? I try to set up a mailing list on aws ec2(ubuntu). In the instruction( http://docs.mailman3.org/en/latest/prodsetup.html), it doesn't require to install mailman in a virtual env. However, when I tried to run `mailman start`, it produces `/usr/bin/python3: can't open file '/usr/bin/master': [Errno 2] No such file or directory`. -- Best wishes, Leon

3 5

Mailman3 on FreeBSD
by John Poltorak 14 Aug '17

14 Aug '17

I'm trying to install Mailman3 on FreeBSD using http://docs.mailman3.org/en/latest/prodsetup.html The install runs but 'mailman info' returns errors. Can anyone suggest where I should look to get this sorted out?

6 13

Postgresql
by John Poltorak 13 Aug '17

13 Aug '17

What is involved in setting up Postgres to store Mailman msgs?

2 1

Mailman home
by John Poltorak 13 Aug '17

13 Aug '17

I'm still in my early stages of getting Mailman 3 up and running, and am still not sure how and where it should be installed, but what I've noticed is that the Mailman subdirectory tree gets install in the current directory when running 'mailman list'... Is that would should happen?

2 1

hyperkitty won't list more than 5 posts and shows empty grey Activity Summary box
by Cyprian Laskowski 11 Aug '17

11 Aug '17

Hi, On our new installation of Mailman 3, which seems to be otherwise working fine (thanks!), the "More..." link doesn't work, such that the list continues to only show 5 posts, even though it's clear that hyperkitty is aware of more (if I click on August, for example). Also, nothing is shown in the grey box under Activity Summary (the <svg class="chart-data"> element), although I'm not sure what's supposed to be shown there. The public archived list is here: http://seznami.cjvt.si/hyperkitty/list/test@seznami.cjvt.si/. I'd appreciate any pointers. Regards, Cyprian

5 9

Mailman3 on FreeBSD
by John Poltorak 11 Aug '17

11 Aug '17

Has anyone managed to install Mailman 3 on FreeBSD?

2 2

Telling Mailman/Hyperkitty where sass is
by Erin Justice 11 Aug '17

11 Aug '17

Hi all, Another issue that's cropped up when I am trying to run Mailman 3 on apache. I've downloaded and installed Mailman core, Django, Postorius & Hyperkitty. I'm using the mailman-suite django project from https://gitlab.com/mailman/mailman-suite/tree/master <https://gitlab.com/mailman/mailman-suite/tree/master>. When I run the site using Django's development server everything works. However when I run the site from apache it's not finding sass. Specifically I'm getting errors like: FilterError at /accounts/login/ /bin/sh: sass: command not found I triple checked that sass is installed which sass /Applications/MAMP/Library/bin/sass /Applications/MAMP/Library/bin/ is in $PATH when I checked that and I was thinking that it maybe wasn't getting to python properly. However pprint(sys.path) contains the same items whether I start the site from the dev server or apache. Any pointers would be appreciated. -Erin

4 3

Mailman container images v0.1.1
by Abhilash Raj 10 Aug '17

10 Aug '17

Hi All, Version 0.1.1[1] of the container images are now available for download. There are several new changes that make working with the container easier. Please have a look at the release notes[1] for upgrading to this version. Most notable changes are: * Now you MUST specify SECRET_KEY environment variable that Django uses. The default value was removed to make sure people set a different value for each installation * Hyperkitty has been updated to latest 1.1.1 release * Mailman-web image has been moved to alpine 3.6 base image form Debain The NEWS[2] contains an exhaustive list of all the changes that has gone into this release. Thanks to all the contributors who contributed patches and reported issues for this new release! [1]: https://github.com/maxking/docker-mailman/releases/tag/v0.1.1 [2]: https://asynchronous.in/docker-mailman/NEWS.html -- thanks, Abhilash Raj

4 5

Typo in List Creation screen
by Henrik Rasmussen 10 Aug '17

10 Aug '17

There is a typo in the list creation screen in Mailman 3. The owner's address field says "Inital list owner address", which should be "Initial" with an extra 'i'. Regards Henrik Rasmussen

2 1

Setup Mailman 3 using Apache/Mod_WSGI
by Erin Justice 08 Aug '17

08 Aug '17

Hi all, I'm trying to setup Mailman 3 to run using apache. I've downloaded and installed mailman core, django, Postorius & Hyperkitty I'm using the mailman-suite django project from https://gitlab.com/mailman/mailman-suite/tree/master <https://gitlab.com/mailman/mailman-suite/tree/master>. When I run the site using Django's development server everything works. However I've been unsuccessful in getting the site to run via apache w/ Mod_WSGI. Note: I have a number of virtual hosts setup for various PHP sites and am trying to add the mailman install as another virtual host. I'm using MAMP for managing my website setup on my local machine. The addition to the virtual hosts file is: <VirtualHost *:80> #Mailman3 stuff ServerName mailman.local Alias /static /Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/static <Directory "/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/static"> Order deny,allow Allow from all </Directory> WSGIScriptAlias / /Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/wsgi.py <Directory "/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project"> <Files wsgi.py> Order deny,allow Allow from all </Files> </Directory> </VirtualHost> I also have the following in my https.conf. WSGIPythonPath /Applications/MAMP/Library/lib/python2.7/ The 500 and related Errors I'm getting in Apache are: [Thu Aug 03 14:18:55 2017] [info] mod_wsgi (pid=80044): Create interpreter 'mailman.local|'. [Thu Aug 03 14:18:55 2017] [info] mod_wsgi (pid=80044): Adding '/Applications/MAMP/Library/lib/python2.7/' to path. [Thu Aug 03 14:18:55 2017] [info] [client ::1] mod_wsgi (pid=80044, process='', application='mailman.local|'): Loading WSGI script '/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/wsgi.py'. [Thu Aug 03 14:18:55 2017] [error] [client ::1] mod_wsgi (pid=80044): Target WSGI script '/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/wsgi.py' cannot be loaded as Python module. [Thu Aug 03 14:18:55 2017] [error] [client ::1] mod_wsgi (pid=80044): Exception occurred processing WSGI script '/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/wsgi.py'. [Thu Aug 03 14:18:55 2017] [error] [client ::1] Traceback (most recent call last): [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/wsgi.py", line 38, in <module> [Thu Aug 03 14:18:55 2017] [error] [client ::1] application = get_wsgi_application() [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/django/core/wsgi.py", line 13, in get_wsgi_application [Thu Aug 03 14:18:55 2017] [error] [client ::1] django.setup(set_prefix=False) [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/django/__init__.py", line 22, in setup [Thu Aug 03 14:18:55 2017] [error] [client ::1] configure_logging(settings.LOGGING_CONFIG, settings.LOGGING) [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/django/conf/__init__.py", line 56, in __getattr__ [Thu Aug 03 14:18:55 2017] [error] [client ::1] self._setup(name) [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/django/conf/__init__.py", line 41, in _setup [Thu Aug 03 14:18:55 2017] [error] [client ::1] self._wrapped = Settings(settings_module) [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/django/conf/__init__.py", line 110, in __init__ [Thu Aug 03 14:18:55 2017] [error] [client ::1] mod = importlib.import_module(self.SETTINGS_MODULE) [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/importlib/__init__.py", line 37, in import_module [Thu Aug 03 14:18:55 2017] [error] [client ::1] __import__(name) [Thu Aug 03 14:18:55 2017] [error] [client ::1] ImportError: No module named settings Any thoughts would be greatly appreciated. Thank you, -Erin Justice

3 3

Docker, Mailman 3, templates and list user accounts
by Henrik Rasmussen 08 Aug '17

08 Aug '17

I used Docker to installed Mailman 3. The top header of the web interface says "Example.Com" while linking to the correct site URL (I believe coming from SERVE_FROM_DOMAIN). In a post[1], Mark Sapiro referred to the template system in Mailman 3 by pointing out that "a custom template can be put in var/templates/site/en/welcome.txt or var/templates/domains/example.com/en/welcome.txt<http://var/templates/domains/example.com/en/welcome.txt> or var/templates/lists/listname.example.com/en/welcome.txt<http://var/templates/lists/listname.example.com/en/welcome.txt> where var is Mailman's configured var_dir". I believe this refers to the mail templates. 1) Where do I change the similar template system, for the web interface, without breaking a laver upgrade? 2) How do I change the site name in the top of the web interface on Mailman 3 to my subside and ? [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… The Mailman command in Mailman Core doesn't seem to have a command for listing the accounts users have created by using Sign up in the web interface, so I believe that accounts may be created in the webinterface. Is there similar commands for the web interface like the mailman commands for the Mailman core? Regards, Henrik Rasmussen

3 3

config incoming email in my domain cpanel
by Rafael Mora 04 Aug '17

04 Aug '17

Hello, I created a test list called: testlist1(a)labbrands.com How do I do in order to redirect the incoming emails to that direction to my server with MM3 ?? Thanks -- Atentamente / Best Regards Ing. Rafael Mora

5 24

Installing mailman 3
by Rafael Mora 02 Aug '17

02 Aug '17

Hello, I want to install mailman 3 in a centos 7 virtual machine. I'm following these steps and I cannot make it work: 1. `cd ~` 2. `git clone https://gitlab.com/mailman/mailman.git` 3. `cd mailman` 4. `virtualenv -p python3 venv` 5. `source venv/bin/activate` 6. `python setup.py develop` 7. I am pretty sure this setup command will place a configuration file into `~/mailman/var/etc/mailman.cfg`. Edit this file. https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html 8. `mailman info` can confirm which configuration file is in use 9. `mailman start` will start up Mailman 3 Core. This is what the parent background process command looks like in `ps -ef`: `/home/ubuntu/mailman/venv/bin/python /home/ubuntu/mailman/venv/bin/master -C /home/ubuntu/mailman/var/etc/mailman.cfg` I also tried the steps on the website https://wiki.list.org/DEV/SetupDevEnvironment but it doesn't work either What do you suggest? This is what I get from console: [root@localhost ~]# cd dev/ [root@localhost dev]# cd mailman/ [root@localhost mailman]# source venv3/bin/activate (venv3) [root@localhost mailman]# cd mailman/ (venv3) [root@localhost mailman]# ls conf.py COPYING data README.rst src unittest.cfg contrib coverage.ini MANIFEST.in setup.cfg template.py copybump.py cron port_me setup.py tox.ini (venv3) [root@localhost mailman]# cd .. (venv3) [root@localhost mailman]# mailman start Starting Mailman's master runner /root/dev/mailman/venv3/bin/python: can't open file '/sbin/master': [Errno 2] No such file or directory (venv3) [root@localhost mailman]# Thank you -- Atentamente / Best Regards Ing. Rafael Mora

8 151

Ready to try installation: use "normal" install or docker.
by Tom Browder 01 Aug '17

01 Aug '17

The mm3 installation instructions have been somewhat fluid over the development period, butI'm finally ready to dig in and give it a shot and need some last-minute advice. I'm leaning toward installing using the docker method but I would appreciate any recent thoughts about which method to choose. Thanks so much to the MM3 dev team! Best, -Tom

2 4

LMTP runner keeps crashing
by Mark Lindsay 01 Aug '17

01 Aug '17

Hl mailman-users! The LMTP runner on my Mailman 3 install (3.1.0b4) has started silently crashing. The parent process and all of the other runners stay up. Nothing interesting seems to be written to the logs. I've been finding out about it when exim4 (running on the same server) starts sending out "retry timeout exceeded" bounce emails to list participants: From: Mail Delivery System [mailto:Mailer-Daemon@lists.mysite.org] > Sent: Monday, July 31, 2017 12:39 PM > To: some_participant(a)mysite.org > 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: > listname(a)lists.mysite.org > retry timeout exceeded > Action: failed > Final-Recipient: rfc822;listname(a)lists.mysite.org > Status: 5.0.0 After hearing about the bounces from participants, I then SSH to the lists server and attempt to `telnet localhost 8024` but get no response. The LMTP runner is not listed in `ps -ef`. After restarting all of mailman (`mailman stop; mailman start`) I get the `220` response from LMTP on port 8024. I see the LMTP runner in `ps -ef`. Does anyone have any ideas on how I could start debugging this? Thank you, Mark

2 1

Installation guide
by Loring 31 Jul '17

31 Jul '17

So I am looking to install the latest mailman 3, however I can find no complete guide as to how to install it. I have found some pages for instance http://mailman.readthedocs.io/en/latest/src/mailman/docs/install.html# This however gives me no instructions on how to install mailman3.x, can anyone point me in the righ direction please. -- Richmond Loring rloring(a)bnl.gov Advanced Systems Engineer

2 1

MM3 statistics
by Tom Browder 28 Jul '17

28 Jul '17

Are there any plugins or programs for mm3 statistics? Thanks. -Tom

3 4

Mailman 3 Status Update Please?
by ddw David Wilson 26 Jul '17

26 Jul '17

Mailman 3 Status Update Please I have been following the progress and difficulties with great interest as many struggle to implement the new version of the great Mailman 3 list-server software. Last year about this time I posed some questions regarding the current development status and recognize that many additional problems seem to get in the way of actually working on long term big picture issues. From my perspective of being an senior (ie overaged) person desirous of implementing fully-featured, capable, scalable, reliable, secure applications such as Mailman, I am convinced that I am thoroughly over my head. From my limited perspective, it would seem to me that a 'nice to have' system would incorporate the following. 1. An open container standard configurable system install, compatible with different web & mail servers, DB utilities, etc; 2. Python 3 version Django utilities for archiving and mail list name management; 3. A design/plan from an inside expert perspective stating costs, time and resources to implement the plan, incorporating crowdfunding to pay for project. 4. As a backup incentive to the crowdfunding plan might be the offer of an expert to set up a system for each significant amount donated, say US$1,000, such as might be accomplished by an SSL session on the target computer/server after the user has specified all necessary detail as required in a template. I am sure that the program author and other major contributors could greatly enhance this list. In summary, I guess what I am requesting is an overview forecast by half year period and out for the next two years? Please share the big picture? Thank you in advance and best regards. Dave Wilson

6 7

MM3.1 templates
by Matt Richards 20 Jul '17

20 Jul '17

I've managed, to setup MM3.1 using the docker images from http://github.com/maxking/docker-mailman. I would like to start customizing the templates MM3.1 uses for the footer and confirmation emails. Is there any mailman site admin or list admin documentation on how to customize email templates in MM3.1? I've found this template doc at https://gitlab.com/mailman/mailman/tree/master/src/mailman/rest/docs, but I'm not clear how this works.. and it appears postorius doesn't have template support yet? I am new to python and django.. -- --Matt

2 1

AH01102: error reading status line from remote server 172.19.199.3:8000
by Henrik Rasmussen 20 Jul '17

20 Jul '17

I've just installed Mailman 3.1 on RHEL7 (Docker-Mailman3) and to get the right CSS layout I installed Apache on the Mailman server outside Docker, as advised by Abhilash Raj and Alexander Klotz. My Mailman server is on a secured network and the https connection from Internet will be handled by proxy servers, so I will be using http (port 80) between proxy-servers and Mailman server. But when I sign in (currently via an SSH tunnel to the Mailman server from my workstation) I get "Internal error: [client ::1:41912] AH01102: error reading status line from remote server 172.19.199.3:8000, referer: http://localhost/accounts/login/?next=%2Fpostorius%2Flists%2F" If I type a wrong password, I am just warned about that, so the problem appears when log in is accepted. I expect that it is because I connect to localhost:80 through SSH tunnel. What do I miss in my Apache configuration on the Mailman server to avoid this problem? <VirtualHost *:80> ErrorLog /var/log/httpd/error_log LogLevel warn CustomLog /var/log/httpd/access_log combined ServerAdmin root(a)example.foo ServerName list.foo.bar Alias /static /opt/mailman/web/static Alias /favicon.ico /opt/mailman/web/static/hyperkitty/img/favicon.ico ProxyPassMatch ^/static/.* ! ProxyPass / http://172.19.199.3:8000/ ProxyPassReverse / http://172.19.199.3:8000/ <Directory /> Allow from all Require all granted </Directory> <Directory /opt/mailman/web/static/hyperkitty/img/> Allow from all Require all granted </Directory> # ssl config here ... </VirtualHost> Thanks, Henrik Rasmussen

2 3

List of "site admin" commands in Mailman 3.1 docker-mailman
by Henrik Rasmussen 18 Jul '17

18 Jul '17

I am new to all of Python, Django, Docker, Docker-compose and everything else used by docker-mailman. I have managed to get a webinterface of Mailman 3.1, I installed using Docker and Docker-Compose from github.com/maxking/docker-mailman, but my config is still bogues (probably just my Apache-config). I'm quite confused about Mailman 3 documentation regarding those commands the site admin would do in Mailman 2 like list_members, config_list -o etc.)., and I have been trying to figure out what documentation regards the development of Mailman 3, what regards the final version 3.1 and what I am supposed to do regarding Docker. 1) Should I enter the container using "docker exec -it mailman-web bash" and run "python" in order to get a python prompt, and from there run commands like those documented at mailman.readthedocs.io/en/latest/src/mailman/commands/docs/control.html ?. 2) Where do I define the what was previously known as the site admin user and site admin e-mail? On another note: Is it a setting in the mailman-users(a)mailman3.org list setup that make each of my postings to the list come back with the note "This sender failed our fraud detection checks and may not be who they appear to be."? Thanks Henrik Rasmussen

4 3

Re: Found error in docker-container
by Abhilash Raj 17 Jul '17

17 Jul '17

Hi Alex, On Wed, Jul 5, 2017, at 03:21 AM, Alexander Klotz wrote: > Hi, > > one of our developers wanted to point out an error he found in mailman > 3.1, docker container maxking/mailman-core-0.1 > > The entries in /opt/mailman/core/var/data/postfix_lmtp are not set > correctly, example: > > /^testlist(a)mailman\.example\.com$/ lmtp:[172.19.199.2# IP > Address of mailman-core container]:8024 > > this actually should look like this: > > /^testlist(a)mailman\.example\.com$/ lmtp:[172.19.199.2]:8024 Can you send a copy of your Mailman configuration that you added at `/opt/mailman/core/mailman-extra.cfg`? I think this is mostly because the configuration parser doesn't understand the in-line comments. So, if you are using the configuration exactly as it is mentioned in the documentation, it could be the cause of this problem. Solution to that would be to just remove all the in-line comments. [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 172.19.199.2 # IP Address of mailman-core container lmtp_port: 8024 smtp_host: 172.19.199.1 # IP Address of host where postfix is. smtp_port: 25 configuration: /etc/postfix-mailman.cfg Like the two comments seen in the configuration above. I will update the documentation too so that others don't get caught in something like this. Thanks! -- thanks, Abhilash Raj

2 4

postfix, dovecot and MM3
by Matt Richards 15 Jul '17

15 Jul '17

This is a bit of a lengthy post, but I wanted to make sure I had enough detail to document the problem I'm experiencing. The quick summary is, I'm having a problem with postfix, dovecot and mailman3.. routing Problem: Postfix mail routing is mostly working correctly with the execpetion of handling test-confirm+157fcaf78907a2bbf21b36aaf349386e09e801a8(a)example.com emails. As you can see below in my postfix config, I have defined recipient_delimiter.. I'm not sure what else is going wrong.. For example, if I email test-confirm(a)example.com, the mail will route over to MM correctly as postfix is able to find this exact email address in the postfix_lmtp transport file. However, if I reply to a mm confirmaion email, test-confirm+157fcaf78907a2bbf21b36aaf349386e09e801a8(a)example.com, postfix will fail to deliver the email correctly due postfix trying to lookup the test-confirm(a)example.com in dovcot's virtual mailbox tables. I hope this is enough information... My research seems to indicate I might need to change something with virtual_alias_maps, however from my testing, changing this setting to include MM3's geneated postfix_lmtp file, it'll cause more problems.. I've also considered using a sub-domain, for example lists.example.com instead of my primary domain for mm3, this may fix a lot of my issues. Setup overview: Integrated mailcow-dockerized (https://github.com/andryyy/mailcow-dockerized) & docker-mailman (https://github.com/maxking/docker-mailman) - all I have done is merged the containers from the docker-mailman docker-compose.yml into mailcow's docker-compose.yml - updated the network settings for docker-mailman to use mailcow's internal network if needed, I can provide my docker-compose file. mx1.example.com = An internal eMail firewall and security server Below is the reject log from postfix: Jul 15 18:11:22 mx10 postfix/smtpd[418]: NOQUEUE: reject: RCPT from mx1.example.com[xxx.xxx.xxx.xxxx]: 550 5.1.1 < test-confirm+157fcaf78907a2bbf21b36aaf349386e09e801a8(a)example.com>: Recipient address rejected: User unknown in virtual mailbox table; from=< xxxx(a)gmail.com> to=< test-confirm+157fcaf78907a2bbf21b36aaf349386e09e801a8(a)example.com> proto=ESMTP helo=<mx1.example.com> Below is my postfix configs: ##Postfix main.cnf biff = no append_dot_mydomain = no smtpd_tls_cert_file = /etc/ssl/mail/cert.pem smtpd_tls_key_file = /etc/ssl/mail/key.pem smtpd_use_tls=yes smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases relayhost = [mx1.example.com]:25 mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 10.0.0.0/8 172.16.0.0/12 192.168.0.0/16 [fd4d:6169:6c63:6f77::]/64 mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all inet_protocols = all bounce_queue_lifetime = 1d broken_sasl_auth_clients = yes disable_vrfy_command = yes maximal_backoff_time = 1800s maximal_queue_lifetime = 1d message_size_limit = 26214400 milter_default_action = accept milter_protocol = 6 minimal_backoff_time = 300s plaintext_reject_code = 550 postscreen_access_list = permit_mynetworks, cidr:/opt/postfix/conf/postscreen_access.cidr, tcp:127.0.0.1:10027 postscreen_bare_newline_enable = no postscreen_blacklist_action = drop postscreen_cache_cleanup_interval = 24h postscreen_cache_map = proxy:btree:$data_directory/postscreen_cache postscreen_dnsbl_action = enforce postscreen_dnsbl_sites = b.barracudacentral.org=127.0.0.2*7 dnsbl.inps.de=127.0.0.2*7 bl.mailspike.net=127.0.0.2*5 bl.mailspike.net=127.0.0.[10;11;12]*4 dnsbl.sorbs.net=127.0.0.10*8 dnsbl.sorbs.net=127.0.0.5*6 dnsbl.sorbs.net=127.0.0.7*3 dnsbl.sorbs.net=127.0.0.8*2 dnsbl.sorbs.net=127.0.0.6*2 dnsbl.sorbs.net=127.0.0.9*2 zen.spamhaus.org=127.0.0.[10;11]*8 zen.spamhaus.org=127.0.0.[4..7]*6 zen.spamhaus.org=127.0.0.3*4 zen.spamhaus.org=127.0.0.2*3 hostkarma.junkemailfilter.com=127.0.0.2*3 hostkarma.junkemailfilter.com=127.0.0.4*1 hostkarma.junkemailfilter.com=127.0.1.2*1 wl.mailspike.net=127.0.0.[18;19;20]*-2 hostkarma.junkemailfilter.com=127.0.0.1*-2 postscreen_dnsbl_threshold = 8 postscreen_dnsbl_ttl = 5m postscreen_greet_action = enforce postscreen_greet_banner = $smtpd_banner postscreen_greet_ttl = 2d postscreen_greet_wait = 3s postscreen_non_smtp_command_enable = no postscreen_pipelining_enable = no proxy_read_maps = proxy:mysql:/opt/postfix/conf/sql/ mysql_virtual_sender_acl.cf, proxy:mysql:/opt/postfix/conf/sql/ mysql_tls_enforce_out_policy.cf, proxy:mysql:/opt/postfix/conf/sql/ mysql_tls_enforce_in_policy.cf, $local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks $smtpd_sender_login_maps queue_run_delay = 300s relay_domains = proxy:mysql:/opt/postfix/conf/sql/ mysql_virtual_relay_domain_maps.cf relay_recipient_maps = proxy:mysql:/opt/postfix/conf/sql/ mysql_relay_recipient_maps.cf sender_dependent_default_transport_maps = proxy:mysql:/opt/postfix/conf/sql/ mysql_tls_enforce_out_policy.cf smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt smtp_tls_cert_file = /etc/ssl/mail/cert.pem smtp_tls_key_file = /etc/ssl/mail/key.pem smtp_tls_loglevel = 1 smtp_dns_support_level = dnssec smtp_tls_security_level = dane smtpd_data_restrictions = reject_unauth_pipelining, permit smtpd_delay_reject = yes smtpd_error_sleep_time = 10s smtpd_hard_error_limit = ${stress?1}${stress:5} smtpd_helo_required = yes smtpd_proxy_timeout = 600s smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, check_recipient_access proxy:mysql:/opt/postfix/conf/sql/ mysql_tls_enforce_in_policy.cf, reject_invalid_helo_hostname, reject_unknown_reverse_client_hostname, reject_unauth_destination smtpd_sasl_auth_enable = yes smtpd_sasl_authenticated_header = yes smtpd_sasl_path = inet:dovecot:10001 smtpd_sasl_type = dovecot smtpd_sender_login_maps = proxy:mysql:/opt/postfix/conf/sql/ mysql_virtual_sender_acl.cf smtpd_sender_restrictions = reject_authenticated_sender_login_mismatch, permit_mynetworks, reject_sender_login_mismatch, permit_sasl_authenticated, reject_unlisted_sender, reject_unknown_sender_domain smtpd_soft_error_limit = 3 smtpd_tls_auth_only = yes smtpd_tls_dh1024_param_file = /etc/ssl/mail/dhparams.pem smtpd_tls_eecdh_grade = strong smtpd_tls_exclude_ciphers = ECDHE-RSA-RC4-SHA, RC4, aNULL smtpd_tls_loglevel = 1 smtp_tls_mandatory_protocols = !SSLv2, !SSLv3 smtp_tls_protocols = !SSLv2, !SSLv3 lmtp_tls_mandatory_protocols = !SSLv2, !SSLv3 lmtp_tls_protocols = !SSLv2, !SSLv3 smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3 smtpd_tls_protocols = !SSLv2, !SSLv3 smtpd_tls_mandatory_ciphers = high smtpd_tls_security_level = may tls_ssl_options = NO_COMPRESSION tls_high_cipherlist = EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA256:EECDH:+CAMELLIA128:+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!IDEA:!ECDSA:kEDH:CAMELLIA128-SHA:AES128-SHA transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp proxy:mysql:/opt/postfix/conf/sql/mysql_virtual_mailbox_maps.cf virtual_alias_maps = proxy:mysql:/opt/postfix/conf/sql/ mysql_virtual_alias_maps.cf, proxy:mysql:/opt/postfix/conf/sql/ mysql_virtual_spamalias_maps.cf, proxy:mysql:/opt/postfix/conf/sql/ mysql_virtual_alias_domain_maps.cf, proxy:mysql:/opt/postfix/conf/sql/ mysql_virtual_alias_domain_catchall_maps.cf virtual_gid_maps = static:5000 virtual_mailbox_base = /var/vmail/ virtual_mailbox_domains = proxy:mysql:/opt/postfix/conf/sql/ mysql_virtual_domains_maps.cf virtual_mailbox_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp proxy:mysql:/opt/postfix/conf/sql/mysql_virtual_mailbox_maps.cf virtual_minimum_uid = 104 virtual_transport = lmtp:inet:dovecot:24 virtual_uid_maps = static:5000 smtpd_milters = inet:rspamd:9900 non_smtpd_milters = inet:rspamd:9900 milter_mail_macros = i {mail_addr} {client_addr} {client_name} {auth_authen} mydestination = localhost.localdomain, localhost #content_filter=zeyple # Prefere IPv4, useful for v4-only envs smtp_address_preference = ipv4 smtp_header_checks = pcre:/opt/postfix/conf/mailcow_anonymize_headers.pcre unknown_local_recipient_reject_code = 550 owner_request_special = no Note: I've replaced my real domain name with example.com, as I don't wish to have my server information publicly archived for spam and security reasons. I have also masked any external IP addreses. I'm also aware my email setup is a bit more complicated than the usual as I have an email firewall/security server in the mix. I've tried my best to accurately describe what I have configured. If you need any actual logs or configs, please contact me directly off this list for this information. -- --Matt

1 0

Does hyperkitty show JPEGs in line and what about attachments?
by Jason Glazer 13 Jul '17

13 Jul '17

I run several MailMan 2.1 mailing lists and some subscribers are frustrated by the way pipermail deals with JPEGs that are embedded in the messages and also with how attachments are handled. Does hyperkitty in Mailman 3.1 do better on these issues. Assuming this message gets archived, I am going to try embedding a small picture right here: Hopefully that shows up in the archive. I won't add an attachment because the list may not allow it but I'm curious how those are handled. Thanks Jason -- Jason Glazer, P.E., BEMP, GARD Analytics, 90.1 ECB chair, 209 chair Admin for onebuilding.org building performance mailing lists

4 8

Docker Mailman3 installation frustration
by ccsmith＠cetsi.com 13 Jul '17

13 Jul '17

I've been working on installing Mailman3 for several weeks now, with limited success. I have tried various installation methods following instructions on numerous different web pages. My experience has been that the instructions are often conflicting and never complete. My best success has been with the Docker version, so that's what I'm going to concentrate on here. I'm running Ubuntu 16.04 (under Citrix XenServer), with Apache httpd and postfix. Following the instructions on https://asynchronous.in/docker-mailman/, I did the following: * created the directories "/opt/mailman/core" and "/opt/mailman/web", * created "/opt/mailman/core/mailman-extra.cfg" and inserted the suggested [mta] directives, * inserted the "transport_maps", "local-recipient_maps", and "relay_domains" entries in the /etc/postfix/main.cf file, * created the necessary apache config files, * cloned "https://github.com/maxking/docker-mailman", * ran "docker-compose up -d" At this point, I am able to connect with Postorius. All of the text and icons show up properly; all is well. It tells me (correctly) that "There are currently no mailing lists." When I click on the "Login" link at the top right, the "Sign In" page displays correctly. (Aside: Why do so many apps/sites have difficulty with choosing between "login" and "sign in" and, in fact, use both terms? It can really be off-putting to non-tech users... and me.) If I input an incorrect login, I receive (correctly) the message "The username and/or password you specified are not correct." However, if I input the correct sign-in, I receive: "Server Error (500)". Running "sudo docker exec -it mailman-web cat ../mailman-web-data/logs/mailmanweb.log" shows me: ERROR 2017-07-12 20:34:25,073 25 django.request Internal Server Error: /accounts/login/ Traceback (most recent call last): File "/usr/local/lib/python2.7/site-packages/django/core/handlers/exception.py", line 39, in inner response = get_response(request) ... more stuff ... File "/usr/local/lib/python2.7/smtplib.py", line 747, in sendmail raise SMTPRecipientsRefused(senderrs) SMTPRecipientsRefused: {u'pacetechadmin(a)cetsi.com': (451, '4.3.0 <pacetechadmin(a)cetsi.com>: Temporary lookup failure')} On the Docker host (ubuntuServer2), /var/log/mail.log shows: Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: error: open /opt/mailman/core/var/data/postfix_domains: No such file or directory Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: error: open /opt/mailman/core/var/data/postfix_lmtp: No such file or directory Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: connect from unknown[172.19.199.3] Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: regexp:/opt/mailman/core/var/data/postfix_domains is unavailable. open /opt/mailman/core/var/data/postfix_domains: No such file or directory Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: relay_domains: regexp:/opt/mailman/core/var/data/postfix_domains: table lookup problem Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: relay_domains lookup failure Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: regexp:/opt/mailman/core/var/data/postfix_domains is unavailable. open /opt/mailman/core/var/data/postfix_domains: No such file or directory Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: relay_domains: regexp:/opt/mailman/core/var/data/postfix_domains: table lookup problem Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: relay_domains lookup failure Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: NOQUEUE: reject: RCPT from unknown[172.19.199.3]: 451 4.3.0 <pacetechadmin(a)cetsi.com>: Temporary lookup failure; from=<postorius(a)localhost.local> to=<pacetechadmin(a)cetsi.com> proto=ESMTP helo=<mailman-web> Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: error: open /opt/mailman/core/var/data/postfix_domains: No such file or directory Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: error: open /opt/mailman/core/var/data/postfix_lmtp: No such file or directory Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: connect from unknown[172.19.199.3] Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: regexp:/opt/mailman/core/var/data/postfix_domains is unavailable. open /opt/mailman/core/var/data/postfix_domains: No such file or directory Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: relay_domains: regexp:/opt/mailman/core/var/data/postfix_domains: table lookup problem Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: relay_domains lookup failure Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: regexp:/opt/mailman/core/var/data/postfix_lmtp is unavailable. open /opt/mailman/core/var/data/postfix_lmtp: No such file or directory Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: regexp:/opt/mailman/core/var/data/postfix_lmtp lookup error for "root@localhost" Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: transport_maps lookup failure Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: NOQUEUE: reject: RCPT from unknown[172.19.199.3]: 451 4.3.0 <root@localhost>: Temporary lookup failure; from=<root(a)localhost.local> to=<root@localhost> proto=ESMTP helo=<mailman-web> Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: disconnect from unknown[172.19.199.3] ehlo=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=4/5 Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19931]: lost connection after RSET from unknown[172.19.199.3] Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19931]: disconnect from unknown[172.19.199.3] ehlo=1 mail=1 rcpt=0/1 rset=1 commands=3/4 And /var/log/mail.err is filling up with: Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: error: open /opt/mailman/core/var/data/postfix_domains: No such file or directory Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: error: open /opt/mailman/core/var/data/postfix_lmtp: No such file or directory Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: error: open /opt/mailman/core/var/data/postfix_domains: No such file or directory Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: error: open /opt/mailman/core/var/data/postfix_lmtp: No such file or directory Any thoughts on what the problem is? Have I missed a step?

3 3

Confirm on mass subscription
by David Krantz 07 Jul '17

07 Jul '17

Hi, Is there a way of requiring all mass subscribed users to confirm their email adress? I have an use case where we have a current mail list but when moving it to mailman I for different reasons would like to confirm all subscribers. Some very shallow testing suggests that if I just add them using mass subscribe, they will not have to confirm at all. I have yet to upgrade to 3.1 but I will do so in due time. cheers // David

3 2

Changing display name with "mailman withlist"
by Mark Ziranski 05 Jul '17

05 Jul '17

Hello, I am looking for a way to change the display name of a mailing list on command line. As written in "mailman withlist --details" I have created a script named "change.py". When executing the script as written in the manual, I get the following error: (venv-3.5) [root@localhost mailman]# mailman withlist -r change example(a)example.org 'new display name' usage: mailman [-h] [-v] [-C CONFIG] {help,aliases,conf,create,digests,import21,info,inject,lists,members,qfile,remove,reopen,restart,shell,start,status,stop,unshunt,version,withlist} ... mailman: error: unrecognized arguments: new display name According to the manual it should be possible to pass arguments in withlist: mailman withlist [options] listname [args ...] while " mailman withlist -h" says: usage: mailman withlist [-h] [-i] [-r RUN] [--details] [LISTNAME] Mailman version: GNU Mailman 3.2.0a1 (La Villa Strangiato) Btw. I know that there is an interactive shell to execute the script but I need a solution that can be run in a shell script. Thank you.

2 1

Problem with docker and css
by Alexander Klotz 05 Jul '17

05 Jul '17

Hi everyone, we are experiencing some issues trying to run mailman3 on our server. First, when starting docker-compose up -d the mailman-web container is not started. The log shows: mailman-web | useradd: user 'mailman' already exists If we start the container with docker-compose up (without -d), all containers start accurately. Are there other files integrated / processed when starting docker-compose up with -d? Secondly, no css and javascript-elements, as well as images are embedded in the web surface. In the mailman-web log we can see they aren't found (Error 404), but trying with docker-compose exec -T mailman-web ls /opt/mailman-.../static/.../... they actually can be found. Can anybody tell me why these problems appear and how to solve them? Any help would be highly appreciated. Thanks & Regards, Alex Klotz (culturebase editorial staff)

3 6

Found error in docker-container
by Alexander Klotz 05 Jul '17

05 Jul '17

Hi, one of our developers wanted to point out an error he found in mailman 3.1, docker container maxking/mailman-core-0.1 The entries in /opt/mailman/core/var/data/postfix_lmtp are not set correctly, example: /^testlist(a)mailman\.example\.com$/ lmtp:[172.19.199.2# IP Address of mailman-core container]:8024 this actually should look like this: /^testlist(a)mailman\.example\.com$/ lmtp:[172.19.199.2]:8024 Regards, Alex

1 0