Search results for "Postorius" - Mailman-users

Re: Different Mail Domain Cause Key Error

by Torge Riedel

Am 21.04.20 um 23:08 schrieb Brian Carpenter: > Maybe I can get the client to agree to use the web domain as part of their list address. Hi, maybe it is a solution for you what I did on my side (since it was already the setup for mailman2 my customer is happy with it): Set everything up in mailman3 with lists.domain.com and define in postfix (if you use postfix, others should support it also) aliases from - let's say - list1(a)domain.com -> list1(a)lists.domain.com for each mail list. In the list setup in mailman3 (available via postorius) define list1(a)domain.com as an allowed alias for list1(a)lists.domain.com Best Torge

5 years, 4 months

Re: Unknown attribute: max_message_size

by Simon Hanna

On 12/06/2017 11:40 AM, Thor Atle Rustad wrote: > If I make changes here: > https://example.com/postorius/lists/test2.example.com/settings/message_acce…, > I get a warning that the Maximum Message Size field at the bottom is > mandatory. However, if I put a number in that field and save, I get > "Unknown attribute: max_message_size". That makes sense, since Mark states > in > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > that max_messages_size is not exposed in REST. It is. https://gitlab.com/mailman/mailman/merge_requests/329 > > What to do? > > I have Maxking mailman-docker but can easily copy files into the image if > necessary. Are you sure you have up to date images?

7 years, 9 months

Re: Hyperkitty fulltext search performances

by Brian Carpenter

On 10/4/20 8:59 AM, Loïc Dachary wrote: > After a little digging it turns out the mailman3-web Debian GNU/Linux package I'm using is configured to use Woosh as a haystack backend. And it is not fit for volumes greater than a few hundred mega bytes. I should switch to something else from the list of supported backendshttps://django-haystack.readthedocs.io/en/master/backend_support.html For our servers running Postorius/Hyperkitty, we use Xapian. I believe the mailman-users (MM3) list also uses Xapian. It is a lot quicker. For our Affinity/Empathy servers, we use Elasticsearch which we are very happy with. Elasticsearch does have a higher memory requirement I believe than Xapian. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 11 months

Re: MM3 templates

by Mark Sapiro

On 2/15/23 05:22, Odhiambo Washington wrote: > > 1. Where is this template that the system used and can I edit it? /opt/mailman/mm/venv/lib/<python_version>/site-packages/mailman/templates/en/list:user:action:subscribe.txt You can edit it, but your edits will be overwritten if you upgrade. > 2. Why is it not using the template I created? Is the template you placed in /opt/mailman/mm/var/templates/lists/kictanet.lists.kictanet.or.ke/en/ named list:user:action:subscribe.txt and does Mailman have permission to read it? Did you try to create a template in Postorius? If you did, that one will take precedence. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

Can creating too many Django accounts crash Mailman3 server?

by Mohsen Masoudfar

Hi, It seems anybody can go to the site: https://LISTSERVNAME/mailman3/postorius/lists/ and click on the [Sign up] on the top-right corner and create an account. This can easily be automated, even though the next step, confirming the email address, being ignored. I believe it can be used as a target for a DOS attack by creating so many accounts, that eventually causes an 'out of space' error. Is this a justified concern? Is there a way to manage this feature in a secure way? Best regards Mohsen Masoudfar Lead System Analyst, IT Operation American Association for the Advancement of Science 1200 New York Ave, NW, Washington, DC 20005 202-326-7087

5 years

Permissions issue after upgrade of virtualenv

by Odhiambo Washington

Ola, So I installed a new virtualenv using Python3.11, kept all settings intact, copied /opt/mailman/mmvar from the old virtualenv to the new one. Trying to access Postorius, I am greeted with this error: Thu Mar 09 22:17:59.313459 2023] [core:error] [pid 15655] (13)Permission denied: [client 197.232.xx.xx:26574] AH00035: access to / denied (filesystem path '/opt/mailman/mm') because search permissions are missing on a component of the path, referer: https://mm3-lists.kictanet.or.ke/ I did not change Apache config and I made sure that /opt/mailman is all owned by mailman:mailman. What am I missing? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 6 months

Re: Weird response to postings after subscriptions and accounts

by paul＠arenson.org

Results of my redoing my tests following Mark’s comments. A) Thoughts before the tests B) The tests C) Summary A) Thoughts before summarizing tests. 1) I had originally thought of making archives only for subscribers to give them the benefit of posting from the archives directly and being able to find stuff more like a forum (email is always hard to follow). 2) But in retrospect it seems people can get an idea what the list is about from free access. So that is now what I have. 3) On the other hand, it is a bit confusing that a non member can post from the archives without realizing that they need to register, with my settings I can moderate and decide if I want to add him or her to the list based on whether that is spam or not. So ok. B) THE TESTS I was testing too many variables so, to simplify things, I made my settings as follows 1) Subscription—> Confirm 2) Message Acceptance—> Default processing (so only members may post) 3) Testing Procesure I added people three ways—> To do that I created 3 unique addresses to see if they can send and receive by email. 3a) subscribe without creating an account—from here (bottom) https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… <https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres…> Comment: This is fastest. User can immediately send and receive. 3b) Subscription / Unsubscription from same page, navigate to Login and again navigate to signup Comment 1: Confusing because even after creating an account, they are not subscribed to the list. Maybe it makes sense if a person has many lists, but I only have this one. It does not say clearly that one has to subscribe after creating an account. Comment 2: The other thing is that it does not show my domain but that of mailman3.emwd.com <http://mailman3.emwd.com/>. 3c) Mass Subscribe by me. Which is what I intend for my 600 users from another list company. Comment This worked fine. C) Summary 1) I have been thinking of having an account as a good way to get users used to using the archives as a way to confirm current and past topics (as opposed to keeping track by email. But it seems I need to tell them to BOTH subscribe AND create an account. Am I thinking about it the wrong way? 2) When a person wants to unsubscribe, they go to discuss-request(a)list.tokyoprogressive.org <mailto:discuss-request@list.tokyoprogressive.org> with subject bline help. What comes back is the below. a) Isn’t there a better way to unsubscribe by email? b) And how about a way to remove their account itself? The results of your email command are provided below. - Original message details: From: Paul Subscribe <tokyosubscribe(a)icloud.com <mailto:tokyosubscribe@icloud.com>> Subject: help Date: Wed, 18 Sep 2019 01:33:43 -0000 Message-ID: <e46a43ec-e7dd-4846-94b1-d899ea626f53(a)me.com <mailto:e46a43ec-e7dd-4846-94b1-d899ea626f53@me.com>> - Results: Ignoring non-text/plain MIME parts confirm - Confirm a subscription request. echo - Echo back your arguments. end - Stop processing commands. help - Get help about available email commands. join - Join this mailing list. leave - Leave this mailing list. stop - An alias for 'end’. Thanks!!!!

6 years

Re: Error after upgrading mailman3

by Abhilash Raj

On Mon, May 4, 2020, at 7:58 AM, Gelpi Andrea wrote: > Hi, > in my installation the command > > mailman notify > > does not exist. > > Checking the debian packages I noticed the I could upgrade mailman form > 3.2.1 to 3.2.2; mailman-web form 20180916-8 to 20180916-10; > python3-django-hyperkitty from 1.2.2 to 1.3.2 > > I did it with apt-get install > > After that when I try to go to a postorius page the error > > Mailman REST API not available. Please start Mailman core > > in mailman log I found: > > May 4 15:13:08 posta mailman3[10259]: Cannot import runner module: > mailman.runners.rest.RESTRunner > May 4 15:13:08 posta mailman3[10259]: Traceback (most recent call last): > May 4 15:13:08 posta mailman3[10259]: File > "/usr/lib/python3/dist-packages/mailman/bin/runner.py", line 55, in > make_runner > May 4 15:13:08 posta mailman3[10259]: runner_class = > find_name(class_path) > May 4 15:13:08 posta mailman3[10259]: File > "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 52, > in find_name > May 4 15:13:08 posta mailman3[10259]: module = > import_module(module_path) > May 4 15:13:08 posta mailman3[10259]: File > "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module > May 4 15:13:08 posta mailman3[10259]: return > _bootstrap._gcd_import(name[level:], package, level) > May 4 15:13:08 posta mailman3[10259]: File "<frozen > importlib._bootstrap>", line 1006, in _gcd_import > May 4 15:13:08 posta mailman3[10259]: File "<frozen > importlib._bootstrap>", line 983, in _find_and_load > May 4 15:13:08 posta mailman3[10259]: File "<frozen > importlib._bootstrap>", line 967, in _find_and_load_unlocked > May 4 15:13:08 posta mailman3[10259]: File "<frozen > importlib._bootstrap>", line 677, in _load_unlocked > May 4 15:13:08 posta mailman3[10259]: File "<frozen > importlib._bootstrap_external>", line 728, in exec_module > May 4 15:13:08 posta mailman3[10259]: File "<frozen > importlib._bootstrap>", line 219, in _call_with_frames_removed > May 4 15:13:08 posta mailman3[10259]: File > "/usr/lib/python3/dist-packages/mailman/runners/rest.py", line 27, in > <module> > May 4 15:13:08 posta mailman3[10259]: from mailman.rest.wsgiapp > import make_server > May 4 15:13:08 posta mailman3[10259]: File > "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 25, in > <module> > May 4 15:13:08 posta mailman3[10259]: from falcon.routing import > map_http_methods, set_default_responders > May 4 15:13:08 posta mailman3[10259]: ImportError: cannot import name > 'map_http_methods' from 'falcon.routing' > (/usr/lib/python3/dist-packages/falcon/routing/__init__.py) This is a known and fixed issue in the newer releases of Mailman, I am unable to find the original issue though. The issue is that you need to upgrade dependency on falcon to be >=1.4.0. Since this is a Debian package, you may want to contact Debian packaging team for this issue. > I think there is a dependency error somewhere. > > Is there a way to solve it? > > Thank You > > > -- > Gelpi ing. Andrea > -------------------------------------------------------------- > It took the computing power of three C-64s to fly to the Moon. > It takes a 486 to run Windows 95. Something is wrong here. > -------------------------------------------------------------- > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 4 months

Re: Hyperkitty 403 Forbidden Error

by Abhilash Raj

On Wed, Aug 7, 2019, at 9:49 AM, Phil Thompson wrote: > On 07/08/2019 17:04, Abhilash Raj wrote: > > On Wed, Aug 7, 2019, at 8:41 AM, Phil Thompson wrote: > >> On 06/08/2019 09:48, Phil Thompson wrote: > >> > On 06/08/2019 03:38, Abhilash Raj wrote: > >> >> On Mon, Aug 5, 2019, at 10:06 AM, Phil Thompson wrote: > >> >>> I'm in the process of setting up mailman3. The only problem I seem to > >> >>> be > >> >>> having is getting Hyperkitty to archive messages. Rather than the > >> >>> authorisation problems people have previously asked about on the > >> >>> list, I > >> >>> am getting a 403 error... > >> >>> > >> >>> Aug 05 15:38:40 2019 (10229) HyperKitty failure on > >> >>> http://localhost/mailman3/hyperkitty/api/mailman/urls: > >> >>> <html><title>Forbidden</title><body> > >> >>> <h1>Access is forbidden</h1></body></html> (403) > >> >>> Aug 05 15:38:58 2019 (10222) HyperKitty failure on > >> >>> http://localhost/mailman3/hyperkitty/api/mailman/archive: > >> >>> <html><title>Forbidden</title><body> > >> >>> <h1>Access is forbidden</h1></body></html> (403) > >> >>> > >> >>> Any suggestions would be appreciated. > >> >> > >> >> How did you install Hyperkitty? > >> > > >> > On Ubuntu... > >> > > >> > apt-get install mailman3-full > >> > > >> >> You probably need to the set the API key correctly in both Core and > >> >> Hyperkitty. > >> >> > >> >> Have you looked at documentation here[1]? > >> >> > >> >> [1]: > >> >> https://hyperkitty.readthedocs.io/en/latest/install.html#connecting-to-mail… > >> >> > >> >> Note that the MAILMAN_ARCHIVER_KEY = "value" (this value should be in > >> >> quotes, single or double, doesn't matter) in your settings.py for Web > >> >> (Django) should be same as the `api_key : value` (without quotes here > >> >> in hyperkitty.cfg config file). > >> > > >> > That's all correct. I'm familiar with the authorisation issues that > >> > other people have had. > >> > > >> > The only thing I'm doing differently (as far as I am aware) is that > >> > I'm using a URL prefixed with /mailman3 which is stripped off in my > >> > nginx configuration... > >> > > >> > # mailman3. > >> > location /mailman3/ { > >> > uwsgi_pass unix:/run/mailman3/web/uwsgi.sock; > >> > include uwsgi_params; > >> > uwsgi_param SERVER_ADDR $server_addr; > >> > uwsgi_modifier1 30; > >> > uwsgi_param SCRIPT_NAME /mailman3; > >> > } > >> > > >> > location /mailman3/static { > >> > alias /var/lib/mailman3/web/static; > >> > } > >> > > >> > location /mailman3/static/favicon.ico { > >> > alias /var/lib/mailman3/web/static/postorius/img/favicon.ico; > >> > } > >> > > >> > ...but I don't see this affecting the mailman to Hyperkitty > >> > communication. Posting to lists and the Postorius and Hyperkitty > >> > frontends seem to work fine. > >> > >> I have now fixed the 403 error (by setting MAILMAN_ARCHIVER_FROM to my > >> public IP address). However I now get a 400 Bad Request error. > >> > >> I have traced this to the archive() function in > >> hyperkitty/views/mailman.py which is expect a POST but is actually > >> getting a GET, specifically... > >> > >> GET '/mailman3/hyperkitty/api/mailman/archive?key=...' > >> > >> ...which seems to be a fairly fundamental problem. > >> > >> Again, any suggestions would be welcome. > > > > It should be sending POST request to archive emails[1]. How did you > > grab the above request? Was it from logs? > > Yes, I added DEBUG=True in mailman-web.py and captured the HTML from > mailman.log. DEBUG=True doesn't print anything more useful around the 400 error response? > > > Do you have anything else in the logs? There should be something in > > the Mailman Core or web logs should have something. > > There's nothing useful in the core log. > > There are 3 preceding entries in the web log... > > GET /mailman3/hyperkitty/api/mailman/urls?mlist=...&key=... > GET /mailman3/hyperkitty/api/mailman/urls?mlist=...&msgid=...&key=... > GET /mailman3/hyperkitty/api/mailman/urls?mlist=...&msgid=...&key=... > > There is one item in the spool directory. > > These were all (apparently) successful. It seems odd that the last two > entries were identical. The only other thing that I can think of is, ALLOWED_HOSTS. What settings do you have in your ALLOWED_HOSTS in settings.py for Django? You need to have 'localhost' or whatever is the value of the "Host" in the "base_url" in your hyperkitty.cfg file in Mailman Core. I am not sure what is the default value in Ubuntu system. If you don't know, you can debug by adding a '*' in your ALLOWED_HOSTS and see if the problem goes away, this will bypass the Host header check. -- thanks, Abhilash Raj (maxking)

6 years, 1 month

Re: Converting discussion list to read-only list (settings)

by Mark Sapiro

On 10/12/19 8:55 PM, Paul Arenson wrote: > I have found that my users in the discussion list are creating their own topics rather than using the existing ones, so decided to make it a read-only list and use WordPress moderated comments. Since I do not have the original settings for READ ONLY (this is a hosted version), I want to make sure that these are correct. Can someone comment. I'm guessing what you want and what you are saying First, I think you are saying your issue is that your users are using HyperKitty as a web forum and when replying to a message in an existing thread instead of using the 'reply' action on that message, they use the Start a new thread button. Is that really what you are saying? > MOST IMPORTANT—> What setting makes it a discussion list as opposed to read only? If by "read only" you mean the "Announce only mailing list style" as opposed to the "Ordinary discussion mailing list style" the only difference is that for the Announce only style the list attribute allow_list_posts is False and for the Discussion style, it's True. This is the setting in Postorius -> Settings -> Alter Messages -> Include the list post header an all it does is include or not include the List-Post: header in mail from the list. > ALTER MESSAGES > ----------------------- > Filter content Now YES > > Collapse Alternatives Now yes > > Convert html to plain text Now NO Above are not relevant. > Anonymous NOW YES Are you sure you want this. What it does is replace the From: address with the list posting address and removes all other headers that could aid in identifying the poster. It is intended for lists discussing things such as domestic abuse where people may want to be able to post anonymously. > Include RFC2369 headers Now Yes OK, but not relevant > Include the list post header Now Yes This is what the announce style will set to No. > Reply Goes to List Now No munging > > Pipeline Default > > > > DMARC MITIFGATIONS > ----------------------- > > Replace From with list address > > DMARC mitigate unconditionally Now NO > > > MESSAGE ACCEPTANCE > ----------------------- > > Require Explicit Destination Yes > > Administrivia YES The above are OK, but again not relevan to what I think you're asking. > > Default action to take when a member posts to the list Hold for moderation > > > Default action to take when a member posts to the list Hold for moderation Basically these two settings will hold all posts for moderator action, however if the user has a moderation setting other thgan list default, they won't apply. > OTHER? See the FAQ at <https://wiki.list.org/x/4030685>. This is written for Mailman 2.1 and older and some of the settings aren't relevant or exactly the same in Mailman 3, but it may help. On the other hand, if I'm not understanding what you want, please clarify. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

Mailman-users search results for query "Postorius"