January 2020 - Mailman-users - lists.mailman3.org

Listing/Exporting member list error: Mailman REST API not available. Please start Mailman core.
by Thomas Lehker Feb. 17, 2020

Feb. 17, 2020

Our MailMan3 server is extremely slow and when trying to list or export members for a larger list it is throwing 'Mailman REST API not available. Please start Mailman core'. In Mailman core logs I am seeing [27] [CRITICAL] WORKER TIMEOUT (pid:40) [43] [INFO] Booting worker with pid: 43 Has anyone seen this issue? Is there any way to increase 'timeouts'? Thanks for any help! Tom Mailman Novice 16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/somelist(a)somelist.com/requests HTTP/1.1" 200 982 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/somelist(a)somelist.com/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/list.somelist.com HTTP/1.1" 200 347 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/list.somelist.com/roster/owner HTTP/1.1" 200 634 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:01 +0000] "GET /3.1/lists/list.somelist.com/roster/moderator HTTP/1.1" 200 638 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:01 +0000] "GET /3.1/lists/somelist(a)somelist.com/config HTTP/1.1" 200 2257 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:05 +0000] "GET /3.1/lists/list.somelist.com/archivers HTTP/1.1" 200 81 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:08 +0000] "GET /3.1/lists/list.somelist.com/archivers HTTP/1.1" 200 81 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:08 +0000] "GET /3.1/lists/somelist(a)somelist.com/requests HTTP/1.1" 200 982 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:10 +0000] "GET /3.1/lists/list.somelist.com/member/somelist@somelist HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:16 +0000] "GET /3.1/lists/somelist(a)somelist.com/requests HTTP/1.1" 200 982 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:19 +0000] "GET /3.1/lists/somelist(a)somelist.com/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:26 +0000] "GET /3.1/lists/list.somelist.com HTTP/1.1" 200 347 "-" "GNU Mailman REST client v3.3.0" [2020-01-16 16:56:58 +0000] [27] [CRITICAL] WORKER TIMEOUT (pid:40) [2020-01-16 16:57:00 +0000] [43] [INFO] Booting worker with pid: 43 DISCLAIMER: The information contained in this message is privileged and confidential. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please reply to the message and delete/destroy any copy of this message. Information in this message that does not relate to the official business of the firm shall be understood as neither given nor endorsed by it.

4 4

Sync Members of a MM3 Mailing List
by brian＠emwd.com Feb. 12, 2020

Feb. 12, 2020

Does Mailman 3 have a feature/script/function that corresponds with the sync_members script that Mailman 2 has? I have a Mailman 3 client that wants to automate the process of keeping a MM3 list synchronized with a file on the server. Thanks, Brian

4 4

task runjobs minutely uses 100% cpu
by Lars Schimmer Feb. 12, 2020

Feb. 12, 2020

Hi! Since we do run roughly 40 mailinglists on mailman3, the schedules/cronjob task python3 /usr/share/mailman3-web/manage.py runjobs minutely uses 1 CPU core 100% all the time. Any idea howto see why? debian mailma3n-full package 3.2.1-1 Mailman Core Version GNU Mailman 3.2.1 (La Villa Strangiato) Mailman Core API Version 3.0 Mailman Core Python Version 3.7.3 (default, Apr 3 2019, 05:39:12) [GCC 8.3.0] MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

4 6

Cannot setup announce-only mailing list
by Alberto Granzotto Feb. 8, 2020

Feb. 8, 2020

Dear all, I don't understand how to set up an "announce only" mailing list using Postorius Version 1.2.4. What I do is the following: - Click on "Create New List" - From "List Style", select "Announce only mailing list style." - Fill all other fields in the form - Click "Create list" At this point people can subscribe to the newly created announce mailing list. If they add themselves they end up in "List Members", and if they email the announce mailing list, their email is relayed to all other members, just like a normal mailing list :/ Moreover, subscribers get this message, inviting them to post to the announce only mailing list: > Welcome to the "Test-announce" mailing list! > > To post to this list, send your email to: > > test-announce(a)lists.dist0rtion.com Of course, I want to keep this mailing list "read only" for members, and I want only selected people to post to that mailing list. Any idea on how to achieve that? Best, Alberto

4 4

where to configure max_days_to_hold on MM3 GUI interface?
by Shashikanth Komandoor Feb. 6, 2020

Feb. 6, 2020

Hi Sir, I came to know that the held messages can be restricted to be processed after a specific no of days or can be discard after some days using the parameter *max_days_to_hold*. But I could see that parameter value configurable on MM2 GUI interface in General Options but I don't see the same on the MM3 GUI interface. Could you please help me if I am missing something? -- Thanks & Regards, Shashi Kanth.K 9052671936

3 6

Re: Mailman3 on Debian 10
by Mark Sapiro Jan. 31, 2020

Jan. 31, 2020

On 1/30/20 8:24 AM, Bala Mutyam wrote: > Hi Mark, > > Thanks for the update and I managed to resolve the errors on the UI. > > I have 2 more questions about the mailman3. > > 1) how to create Mailing Lists? You can create lists with the `mailman create` command lint tool or via Postorius as a superuser. > 2) super user login is not working even with correct login credentials and giving me - The username and/or password you specified are not correct. How did you create the super user? You should do it with the django admin createsuperuser command. > 3) Password Reset Email urls and email confirmation web pages giving me - This site can't be reached error. If this is an error from your browser, there is something wrong with the host portion of the URL. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Re: Mailman3 on Debian 10
by Mark Sapiro Jan. 31, 2020

Jan. 31, 2020

On 1/30/20 9:22 AM, Bala Mutyam wrote: > Sorry one more issue, > > Mailman settings page giving me below error. > > Server error > An error occurred while processing your request. > > Error logs: > > ERROR 2020-01-30 17:20:11,331 16285 django.request Internal Server Error: /postorius/accounts/subscriptions/ > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 41, in inner > response = get_response(request) > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 187, in _get_response > response = self.process_exception_by_middleware(e, request) > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 185, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/lib/python3/dist-packages/django/contrib/auth/decorators.py", line 23, in _wrapped_view > return view_func(request, *args, **kwargs) > File "/usr/lib/python3/dist-packages/postorius/views/user.py", line 306, in user_subscriptions > mm_user = MailmanUser.objects.get_or_create_from_django(request.user) > File "/usr/lib/python3/dist-packages/postorius/models.py", line 164, in get_or_create_from_django > return self.get(address=user.email) > File "/usr/lib/python3/dist-packages/postorius/models.py", line 86, in get > return method(*args, **kwargs) > File "/usr/lib/python3/dist-packages/mailmanclient/client.py", line 322, in get_user > return User(self._connection, content['self_link'], content) > KeyError: 'self_link' Just prior to this is a call to the REST API to GET /users/user(a)example.com (or whatever the user's address is). It appears that that user doesn't exist in core. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Deliverability and Spam Filtering
by tom＠gather.coop Jan. 30, 2020

Jan. 30, 2020

Hi folks! First time poster, long time Mailman user. I am setting up a new Mailman 3 instance, and am super excited about the REST API. I plan to use it to enable tight integration with a separate web app that I maintain. As I am setting up the mail server, I am wondering about two related things: deliverability (for outgoing mail) and spam filtering (for incoming mail). What solutions have folks used for these? I know it is generally common now to outsource this critical task to a cloud provider like Mailgun or etc. Have folks needed this or is running ones own incoming and outgoing mail not a big deal? So many horror stories out there... As far as Mailgun goes, I think it should be straightforward to configure it for outgoing mail, but I'm not sure how I'd use it for incoming. Mailgun can forward mail via HTTP or to another email address. Neither I think would work out of the box. It would be great if there were a REST API endpoint for incoming mail, but I don't think such a thing exists, right? Perhaps I could add one? Another thought I had was that I could write a simple HTTP server that receives mail from Mailgun and forwards it to Mailman via LMTP. But it seems simpler to go right to Mailman's core API given that one exist already. Or am I thinking about this all wrong? Are there other more suitable services out there? I looked for cloud MTA providers but didn't turn up much except for in the large enterprise space, which I'm sure I can't afford. Thanks for any thoughts!

4 3

SUBSCRIBE_FORM_SECRET in MM3?
by Gila Halpern Jan. 30, 2020

Jan. 30, 2020

I've been looking into ways to prevent spam on my company's list, and one thing I came across was the SUBSCRIBE_FORM_SECRET option in the Mailman configuration, which embeds a CSRF token into the form, and prevents it from being submitted until five seconds after it renders, to keep bots from subscribing. Unfortunately, the information I found pertained to Mailman 2. Does this option exist in MM3 as well, or is there a similar option?

3 2

Mass subscribe gives HTTP Error 500 when using custom template
by Jeffrey D Jan. 30, 2020

Jan. 30, 2020

Hi, I have some issues with the Mass Subscribe option on Mailman 3.2.1. When using a custom "The notice sent to a member when they are subscribed to the mailing list." template, Postorius will throw an exception after pushing the "Subscribe Users" button on Mass Subscribe. In the web interface you will see a red notification bar with the text: "HTTP Error 500: b'A server error occurred. Please contact the administrator.'". And in the Mailman.log you will see the following error message: Traceback (most recent call last): File "/usr/lib/python3.7/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 216, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 215, in falcon.api.API.__call__ File "falcon/api.py", line 189, in falcon.api.API.__call__ File "/usr/lib/python3/dist-packages/mailman/rest/members.py", line 266, in on_post pre_approved=pre_approved) File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 520, in register list(workflow) File "/usr/lib/python3/dist-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 326, in _step_do_subscription self.member = self.mlist.subscribe(self.subscriber) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/mailinglist.py", line 494, in subscribe notify(SubscriptionEvent(self, member)) File "/usr/lib/python3/dist-packages/zope/event/__init__.py", line 31, in notify subscriber(event) File "/usr/lib/python3/dist-packages/mailman/app/membership.py", line 169, in handle_SubscriptionEvent send_welcome_message(mlist, member, member.preferred_language) File "/usr/lib/python3/dist-packages/mailman/app/notifications.py", line 52, in send_welcome_message 'list:user:notice:welcome', mlist, language=language.code)) File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 188, in get name, lookup_context, **substitutions) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 109, in get contents = protocols.get(actual_uri, **auth) File "/usr/lib/python3/dist-packages/mailman/utilities/protocols.py", line 38, in get response = requests.get(url, timeout=REQUEST_TIMEOUT, **kws) File "/usr/lib/python3/dist-packages/requests/api.py", line 75, in get return request('get', url, params=params, **kwargs) File "/usr/lib/python3/dist-packages/requests/api.py", line 60, in request return session.request(method=method, url=url, **kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646, in send r = adapter.send(request, **kwargs) File "/usr/lib/python3/dist-packages/requests/adapters.py", line 516, in send raise ConnectionError(e, request=request) requests.exceptions.ConnectionError: HTTPConnectionPool(host='localhost', port=8000): Max retries exceeded with url: /postorius/api/templates/list/<MAILINGLIST>/list:user:notice:welcome (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f0b5ce8d8d0>: Failed to establish a new connection: [Errno 111] Connection refused')) Postorius/Mailman is running on port 8001, only Postorius still connecting on port 8000. Anyone seen something similar? Thanks in advance! Jeffrey

2 2