- Mailman-users - lists.mailman3.org

Manual setup - permissions
by Tobias Hachmer Sept. 25, 2019

Sept. 25, 2019

Hello, I'm new to mailman3 and started to setup an instance from scratch per hand, but I'm struggeling running the peaces with the correct user/permissions. I can't find anything regarding running this and that with that user in the docs, so I have the following: virtualenv_dir: /opt/venvs/mailman3 Installed packages in venv: - "Django>=1.11" - "django-haystack" - "libsass" - "mailman==3.3.0" - "mailmanclient" - "mailman-hyperkitty==1.1.0" - "postorius==1.3.0" - "hyperkitty==1.3.0" - "whoosh" - "uwsgi" I have installed the core stuff in /opt/mailman3/core, all is owned by user+group "mailman3": root@host:/opt/mailman3# tree . ├── core │ ├── etc │ │ ├── hyperkitty.cfg │ │ ├── mailman.cfg │ │ └── uwsgi.ini │ ├── log │ │ ├── bounce.log │ │ ├── debug.log │ │ ├── mailman.log │ │ ├── plugins.log │ │ └── smtp.log │ └── var │ ├── archives │ │ └── hyperkitty │ │ └── spool │ │ ├── ... │ ├── cache │ ├── data │ │ ├── mailman.db │ │ ├── postfix_domains │ │ ├── postfix_domains.db │ │ ├── postfix_lmtp │ │ └── postfix_lmtp.db │ ├── lists │ │ └── admin.lists.... │ ├── locks │ ├── master.lck │ ├── master.lck|...|...|... │ ├── master.pid │ ├── message" │ │ ├── ... │ ├── queue │ │ ├── archive │ │ ├── bad │ │ ├── bounces │ │ ├── command │ │ ├── digest │ │ ├── in │ │ ├── nntp │ │ ├── out │ │ ├── pipeline │ │ ├── retry │ │ ├── shunt │ │ └── virgin │ └── templates The django project is installed in /opt/mailman3/web, all is owned by user+group "nginx": └── web └── project ├── db │ └── mailmansuite.db ├── emails ├── fulltext_index │ └── _MAIN_0.toc ├── logs │ ├── mailmansuite.log │ ├── uwsgi-error.log │ └── uwsgi.log ├── manage.py ├── __pycache__ │ ├── settings.cpython-35.pyc │ └── urls.cpython-35.pyc ├── run │ └── uwsgi.sock ├── settings.py ├── static ├── urls.py └── wsgi.py The mailman3 core ist running with user+group "mailman3". And the uwsgi service is running as root with drops privileges to user+group "nginx". Now, running the scheduled tasks (which run from user+group "nginx") for django I ran into permission problems, because the nginx user can't access/write to the needed files in /opt/mailman3/core/... If anyone of you is able to read ansible tasks, this is how I set this up via ansible: https://github.com/freifunk-mwu/ansible-ffmwu/blob/mail/roles/service-bundl… I would appreciate any hints how to run the different peaces of mailman3 with the correct user/groups/permissions. Thanks in advance, Tobias

4 4

Re: Issues with migrating from Mailman2 to Mailman 3
by Mark Sapiro Sept. 24, 2019

Sept. 24, 2019

On 9/23/19 12:03 AM, Paul Arenson wrote: > Thank you Mark. > > I found my solution. Simplifies things. People do not have to even > think about subscribing….. <snip> > How does that sound? OK -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Issues with migrating from Mailman2 to Mailman 3
by Uwe Grasshoff Sept. 23, 2019

Sept. 23, 2019

Hello all, I'm currently trying to convert a Debian based mailman2 installation to a docker based mailman3 installation. I successfully running the mailman-web and mailman-core containers together with the database container but I'm struggling with the import of the old mailing lists. In the core container I'm running this two commands for every mailing list: mailman create mailman(a)example.com mailman import21 mailman(a)example.com /oldmailman/lists/mailman/config.pck Then I'm switching over to the mailman-web container and running this two commands: python3.6 manage.py hyperkitty_import -l mailman(a)example.com /oldmailman/archives/private/mailman.mbox/mailman.mbox python3.6 manage.py update_index_one_list mailman(a)example.com I'm getting no errors or something else which could indicate a problem. After that I'm looking into the web interface http://example.com/postorius/lists/ There I can only see the public mailing list and the private ones are not shown there (as expected). When I then try to login with the List Manager credentials of the lists (from mailman2) I can't login in. So I thought maybe I have to "register" myself again to than get access to the list management. So I tried that but when I filled out the form and click "Register" I'm presented with an error page which titles "Serverfehler" (Server error in german) and the message "An error occurred while processing your request." When I then go back a step and try to register again I got the error message that the username is already taken. When I then try to login I can't login I always get the "An error occurred while processing your request." page. Does anyone have an idea what point I'm missing? -- With best Regards Uwe Grasshoff

2 2

Weird response to postings after subscriptions and accounts
by Paul Arenson Sept. 23, 2019

Sept. 23, 2019

I accidentally posted to a test account I had not actually used. Am reposting to my correct account. Sorry to the moderators. In my test of the two forms of signup, I am getting these unexpected results. Is it my settings or is something weird within the program itself? 1) https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… 2) Choose "You can also subscribe without creating an account. If you wish to do so, please use the form below" 3) Then I have to approve it. They get "Welcome to the "Discuss" mailing list! To post to this list, send your email to: discuss(a)list.tokyoprogressive.org 4) But I have to approve it.I assume this is because they do not yet have a real account. And they should be listed as a NON MEMBER? 5) But even when they sign up here: https://list.tokyoprogressive.org/accounts/signup/?next=%2Fpostorius%2Flist… they get an email from my provider (NOT MY LIST????) as follows: "Hello from mailman3.emwd.com! You're receiving this e-mail because user iCloud has given yours as an e-mail address to connect their account. To confirm this is correct, go to https://list.tokyoprogressive.org/accounts/confirm-email/MTE3:1iA44k:E7w7xh… Thank you from mailman3.emwd.com! mailman3.emwd.com" 6) And this is where it gets weird. If they send from their email program and get the welcome (Welcome to the "Discuss" mailing list! To post to this list, send your email to: discuss(a)list.tokyoprogressive.org You can unsubscribe or make adjustments to your options via email by sending a message to....... I then get a notice: "Your mail to 'discuss(a)list.tokyoprogressive.org' with the subject test notice Is being held until the list moderator can review it for approval. The message is being held because: The message is not from a list member" 7) While if they send FROM THE interface it goes through. 8) What I am confused about. Signing up for an account should make them a member, right? Subscribing should make them a non member, no? But here it seems that both make them a non member. And worse, someone with an account sending from the Interface has their message get through while the same person sending from an email program has me get a notice that a non member is trying to post. Before I can move my actual members over from another mailing list provider, I want to make sure what works and what doesn't. Thanks. PS I am running out of test accounts to use to test my own setup. Thanks. paul!!!Subscribe to this list still shows up at the bottom.

4 9

"Cannot connect to SMTP server localhost on port 25"
by Manos Pitsidianakis Sept. 22, 2019

Sept. 22, 2019

Hello, I've been getting "Cannot connect to SMTP server localhost on port 25" from runner "out" in mailman.log over some mails stuck in shunt queue, postfix logs show nothing when this happens, tcpdump on lo interface port 25 shows nothing. The log shows up when I start mailman, and then it seems not to show up again. This is my mailman.cfg's relevant parts: [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: localhost lmtp_port: 8024 smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.postfix I can do 'telnet localhost 25' just fine, including as mailman user. I can send and receive mail on my mail server. I tried making a test list and sent/received messages fine. smtp debug logs show "Using agent: <mailman.mta.deliver.Deliver object at 0x7fdd9793c940>" and "IndividualDelivery to: <email(a)address.tld>" on repeat, where the email address is one of the addresses of the shunted mails. version 3.2.2

2 12

User integration with Django application
by Victoriano Giralt Sept. 21, 2019

Sept. 21, 2019

Hi! Is there a way to integrate Mailman3 user database with an already existing Django application? And then, generate the list roster with a subset of those users. I've been scavenging the archives and failing to find an answer. Thanks! -- Victoriano Giralt CIO University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

2 1

Huge performance issue: Mailman doesn't (seem to) receive any mails.
by Henrik Rasmussen Sept. 20, 2019

Sept. 20, 2019

I am running maxking/mailman-*:0.2 (GNU Mailman 3.2.0 (La Villa Strangiato)). It looks like Mailman is not receiving (enough) mails, but are keps in the Postfix queue and I can't figure out why. I get a lot of "mail for [172.19.199.2]:8024 is using up 7841 of 7841 active queue entries" in the postfix container log (more postfix log at the buttom. I have restarted all Mailman containers this morning, but this didn't help anything. Last entries in Mailman's smtp.log were when we restarted the containers: Sep 18 08:30:02 2019 (36) Peer: ('172.19.199.1', 35454) Sep 18 08:30:02 2019 (36) ('172.19.199.1', 35454) handling connection Sep 18 08:30:13 2019 (36) ('172.19.199.1', 35454) EOF received Sep 18 08:30:13 2019 (36) Connection lost during _handle_client() Sep 18 08:30:13 2019 (36) ('172.19.199.1', 35454) connection lost Sep 18 08:30:18 2019 (36) Peer: ('172.19.199.1', 37164) Sep 18 08:30:18 2019 (36) ('172.19.199.1', 37164) handling connection Sep 18 08:30:20 2019 (36) ('172.19.199.1', 37164) EOF received Sep 18 08:30:20 2019 (36) Connection lost during _handle_client() Sep 18 08:30:20 2019 (36) ('172.19.199.1', 37164) connection lost The runners last ran at Sep 18 08:42:21 2019 The mailman.log updates constantly, but with "Sep 18 09:45:16 2019 (39) 172.19.199.3 - - "GET /3.0/users/" something something only or other http gets. A lot of them is 404 errors, but also a lot of "GET /3.0/lists/LISTNAME HTTP 200 responces, which should not be related. In "uwsgi-error.log" I get some tracebacks, but since I don't think should be related to incoming mails, I'll leave the traceback for now. Sep 18 10:07:47 postfix postfix/smtpd[5426]: connect from gateway[172.19.199.1] Sep 18 10:07:47 postfix postfix/smtpd[5426]: 45DAA7E97BE94: client=gateway[172.19.199.1] Sep 18 10:07:47 postfix postfix/cleanup[5429]: 45DAA7E97BE94: message-id=<A29DAD01610ED744A9D6F14880665668011C8A2C@P 1KITMBX01WC01.unicph.domain> Sep 18 10:07:47 postfix opendkim[19]: 45DAA7E97BE94: DKIM-Signature field added (s=default, d=listsgw.ku.dk) Sep 18 10:07:47 postfix postfix/smtpd[5426]: disconnect from gateway[172.19.199.1] Sep 18 10:07:47 postfix postfix/qmgr[98]: 45DAA7E97BE94: from=<sender(a)example.com>, size=7988, nrcpt=1 (queue active) Sep 18 10:07:47 postfix postfix/qmgr[98]: warning: mail for [172.19.199.2]:8024 is using up 7844 of 7844 active queue entries Sep 18 10:07:47 postfix postfix/qmgr[98]: warning: you may need to reduce lmtp connect and helo timeouts Sep 18 10:07:47 postfix postfix/qmgr[98]: warning: so that Postfix quickly skips unavailable hosts Sep 18 10:07:47 postfix postfix/qmgr[98]: warning: you may need to increase the main.cf minimal_backoff_time and maximal_backoff_time Sep 18 10:07:47 postfix postfix/qmgr[98]: warning: so that Postfix wastes less time on undeliverable mail Sep 18 10:07:47 postfix postfix/qmgr[98]: warning: you may need to increase the master.cf lmtp process limit Sep 18 10:07:47 postfix postfix/qmgr[98]: warning: please avoid flushing the whole queue when you have Sep 18 10:07:47 postfix postfix/qmgr[98]: warning: lots of deferred mail, that is bad for performance Sep 18 10:07:47 postfix postfix/qmgr[98]: warning: to turn off these warnings specify: qmgr_clog_warn_time = 0 [SLIP] Sep 18 10:26:34 postfix postfix/qmgr[98]: B34C07E980CA3: from=<LISTNAME(a)lists.example.com>, size=1219, nrcpt=1 (queue active) Sep 18 10:26:34 postfix postfix/smtp[6559]: connect to sst-dk.mx1-dk.mailanyone.net[130.226.237.91]:25: Connection refused Sep 18 10:26:34 postfix postfix/smtp[6559]: connect to sst-dk.mx1-dk.mailanyone.net[::ffff:130.226.237.91]:25: Connection refused Sep 18 10:26:34 postfix postfix/smtp[6559]: connect to sst-dk.mx2-dk.mailanyone.net[::ffff:130.226.237.91]:25: Connection refused Sep 18 10:26:34 postfix postfix/smtp[6559]: connect to sst-dk.mx2-dk.mailanyone.net[130.226.237.91]:25: Connection refused Sep 18 10:26:34 postfix postfix/smtp[6559]: connect to sst-dk.mx3-dk.mailanyone.net[130.226.237.91]:25: Connection refused Sep 18 10:26:34 postfix postfix/smtp[6559]: B34C07E980CA3: to=<RECIPIENT(a)foo.bar>, relay=none, delay=420673, delays=420673/0.05/0.2/0, dsn=4.4.1, status=deferred (connect to sst-dk.mx3-dk.mailanyone.net[130.226.237.91]:25: Connection refused) / Henrik Rasmussen

3 10

My list has been switched from public to private archives, but they are still visible
by Paul Arenson Sept. 20, 2019

Sept. 20, 2019

Can anyone help with this? I set my list to private archives today. Up until then, it was pubic. And yet, if you go to the list page, you will see that if you click archives (top left), you can see them. (Filled with a bunch of tests posts for now) https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… Am I misunderstanding what a private archive is? Is something wrong with my setup (which is hosted)? Thank you.

4 8

Mailing List Description that can't be modified by list owners
by chilfer＠unr.edu Sept. 20, 2019

Sept. 20, 2019

Is there a way to create an additional mailing list field or lock down the current Description or Information fields so they are not modifiable by a list owner? The goal is to have a field that identifies the department or area a list belongs to so that it's easier to find if an owner leaves the organization and the owner needs to be updated on multiple lists.

2 1

Re: hosted signup is producing unexpected results
by tokyoprogressive＠mailbox.org Sept. 17, 2019

Sept. 17, 2019

I mistakenly posted twice. Please see: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Sent from my iPhone

1 0