Search results for "Postorius" - Mailman-users

Re: [MM3-users]Re: Is it possible to grant all users the ability to Create List

by tibor.molnar＠waltoninstitute.ie

Hi, I would like to know if anyone have implemented this feature or used any workaround to be able to grant users with the ability to create list. This has been a feature in mailman2 where you as a user were able to create list with a password and you did not need to be a superuser in order to do that. I do understand that in the development documentation it states the following: Three of Django’s default User roles are relevant for Postorius: Superuser: Can do everything. AnonymousUser: Can view list index and info pages. Authenticated users: Can view list index and info pages. Can (un)subscribe from lists. Can we maybe add a different user role where the user would be able to create lists? If this is possible would anyone let me know how?

5 years, 2 months

Re: Error downloading CSV for 1,300 members

by Mark Sapiro

On 2/23/23 10:45, Jose Bernal wrote: > Any suggestions on troubleshooting downloading a modest-size CSV file for a > list with 1,300 members? Clicking "CSV Export" on smaller lists works > fine, but on this larger list I get this error in mailman-web.log: > > Thu Feb 23 10:03:32 2023 - uwsgi_response_write_body_do(): Broken pipe > [core/writer.c line 429] during GET /mailman3/postorius/lists/ > members.list.ocdla.org/csv_view/ (172.31.54.89) > OSError: write error This is probably due to a timeout in uwsgi. This thread <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> is about timeouts when downloading archives, but the same considerations apply. To increase the worker timeout for uwsgi, set the harakiri option. See <https://uwsgi-docs.readthedocs.io/en/latest/Glossary.html#glossary> and <https://uwsgi-docs.readthedocs.io/en/latest/Options.html#harakiri> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

Re: Try to Implement Template for The message sent to subscribers when a subscription confirmation is required

by Stephen J. Turnbull

Gerald Vogt writes: > Why would you double book port 80? That's really a bad idea and > causes issues like the one you see... When I read that I assumed that nginx would resolve in favor of the narrower interface:port declaration. If double-booking is happening, nginx should be issuing an error, or (nginx being pretty picky in my experience) even refusing to start. Anyway, OP should look for messages about problems binding to ports in the nginx and uwsgi logs. > Your "INTERNAL" server binds to 127.0.0.1 port 80, only. That's not quite true. Normally the WSGI service will bind to another port for Postorius/HyperKitty, typically 8000. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

7 months, 1 week

Re: config incoming email in my domain cpanel

by Mark Sapiro

On 08/03/2017 01:22 PM, Rafael Mora wrote: > El jue., 3 ago. 2017 a las 15:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: >> >> You need to forward port 25 for SMTP mail delivery and if you want the >> web UI (Postorius and HyperKitty) accessible from the outside, port 80 >> for http and/or port 443 for https >> < >> https://www.iana.org/assignments/service-names-port-numbers/service-names-p… >>> . >> > > I mean for incoming mail redirected from my hostgator hosting, because when > I suscribe an email address MM3 sends a confirmation email, so I have to > reply to be suscribed to the list. As I said, for mail delivery you need to forward port 25 to the Mailman server. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 1 month

Re: ValueError: ...:EVP_DigestInit_ex:disabled for fips

by Mark Sapiro

On 5/19/20 5:57 AM, Ralf Wiegand wrote: > (venv-3.6) [root@maildev mailman-suite_project]# python manage.py migrate > Operations to perform: > Apply all migrations: account, admin, auth, contenttypes, > django_mailman3, django_q, hyperkitty, openid, postorius, sessions, > sites, socialaccount > Running migrations: > Applying contenttypes.0001_initial...Traceback (most recent call last): ... > File > "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/backends/utils.py", > line 221, in names_digest > h = hashlib.md5() > *ValueError: error:060800A3:digital envelope > routines:EVP_DigestInit_ex:disabled for fips* > > > > Hello group, I am running into this error. any idea what is going > wrong here? This is a Django issue, not Mailman per se. The migration that's failing is django/contrib/contenttypes/migrations/0001_initial.py. A brief search seems to indicate that this won't work with NSS FIPS. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

multiple sites on a mailman3 server question

by William Oliver

So, I have successfully installed mailman3 and it's working great. However, the way it works now, if someone goes to the domain website, he or she will get the mailman page. I'd prefer that it work something like: My www.example.com goes to a home page lists.example.com goes to the mailman3 page mail.example.com goes to a roundcube page I'm using nginx, and this is the first time I've set up an nginx server (I have traditionally done apache), and I'm still figuring out the syntax. My sites-available file is below, for the domain emergenus.com. The behavior I'm getting is that if I go to mail.emergenus.com, it still redirects to mail.emergenus.com/mailman3/lists, but gives a 404 page not found. If I go to lists.emergenus.com, it redirects to lists.emergenus.com/mailman3/lists and gives the nice postorius page, and works fine. So, I'm trying to figure out how to stop that redirect. When I look at my nginx access.log file for mail.emergenus.com, I see: 174.212.104.153 - - [28/Dec/2021:21:03:21 -0500] "GET /mailman3/lists/ HTTP/1.1" 404 188 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36" Aha! says I. My ip address is 203.159.80.234, not 174.212.104.153. Thus, uwsgi (I think) is sneaking in there and taking over regardless of what I'm trying to do. Is there a way to tell mailman to only take over for lists.emergenus.com and not for www.emergenus.com or mail.emergenus.com? Here's my uwsgi.ini (without then env= PYTHONPATH change discussed in another thread: # /etc/mailman3/uwsgi.ini # [uwsgi] # Port on which uwsgi will be listening. http-socket = 0.0.0.0:8000 # If running uwsgi from the virtual environment ... virtualenv = /opt/mailman/venv/ module=mailman_web.wsgi:application # Add to python import path. pythonpath = /etc/mailman3/ # The default settings module. env = DJANGO_SETTINGS_MODULE=settings # Setup default number of processes and threads per process. master = true processes = 2 threads = 2 # Setup the django_q related worker processes. attach-daemon = /opt/mailman/venv/bin/mailman-web qcluster # Setup the request log. req-logger = file:/opt/mailman/web/logs/uwsgi.log # Log qcluster commands separately. logger = qcluster file:/opt/mailman/web/logs/uwsgi-qcluster.log log-route = qcluster uwsgi-daemons # Last log and it logs the rest of the stuff. logger = file:/opt/mailman/web/logs/uwsgi-error.log Here's my /etc/nginx/sites-enabled/emergenus.com looks like: server { root /var/www/html2; index index.html index.htm index.nginx-debian.html; server_name emergenus.com, mail.emergenus.com, www.emergenus.com; location /{ try_files $uri $uri/ =404; } ##### added 12/19 listen 443 ssl default_server; listen [::]:443 ssl default_server; ########## ssl_certificate /etc/letsencrypt/live/emergenus.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/emergenus.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } server { root /var/www/html; index index.html index.htm index.nginx-debian.html; server_name lists.emergenus.com; location /{ proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; # proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_redirect off; } listen 443 ssl ; listen [::]:443 ssl ; location /static/ { alias /opt/mailman/web/static/; } ########## ssl_certificate /etc/letsencrypt/live/emergenus.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/emergenus.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } server { if ($host = mail.emergenus.com) { # return 301 https://$host$request_uri; return 301 https://mail.emergenus.com; } # managed by Certbot if ($host = www.emergenus.com) { return 301 https://$host$request_uri; } # managed by Certbot if ($host = lists.emergenus.com) { return 301 https://$host$request_uri; } # managed by Certbot listen 80 ; listen [::]:80 ; server_name www.emergenus.com lists.emergenus.com mail.emergenus.com emergenus.com; return 404; # managed by Certbot } Thanks billo

4 years, 8 months

Re: Templates

by David Krantz

On Fri, Sep 29, 2017 at 12:08 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 09/28/2017 01:56 PM, David Krantz wrote: > This is clearly a bug and should be fixed. If you report this issue at > <https://gitlab.com/mailman/mailman/issues>, we will try to fix it. I'll do that. >> Of course this very nice functionality is a bit buried. I activated it >> using the interactive python shell, seems less risky than changing the >> database directly. > > > There are many core settings not (yet) exposed in Postorius. This is > something we need to fix, but it takes time and resources. In the mean > time, 'mailman shell' is probably the best way to set them. It is okay and it works just fine. In the current version "mailman withlist" does not set a variable to a list, but it is easy enough to set it yourself if a bit poweruser-ish. br // David

8 years, 11 months

Re: Handling of SPAM mails in mailman3 - Check for X-Spam Header

by Mark Sapiro

On 1/19/20 6:42 AM, Torge Riedel wrote: > > One final question: When adding a new header filter I can select between > different actions. And there is one named "Default Anti-Spam action" > (roughly translated from German). I cannot find anything else about this > somewhere else in the settings (Postorius). So what it is the "Default > Anti-Spam action"? There is a configuration setting with default [antispam] jump_chain: hold "Default Anti-Spam action" should set the action for that rule to None which means use the configured [antispam]jump_chain: value. However, there is a bug in REST in core that doesn't allow setting `None` so you can't chose that setting anyway. See <https://gitlab.com/mailman/mailman/issues/671>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

Column 'starting_email_id' cannot be null

by kroerig＠web.de

Hello, after upgrading from Debian 11 to Debian 12 achiving incoming mails always fails with Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 581, in get_or_create return self.get(**kwargs), False File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 435, in get raise self.model.DoesNotExist( During handling of the above exception (Thread matching query does not exist.), another exception occurred: File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py", line 73, in execute return self.cursor.execute(query, args) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 209, in execute res = self._query(query) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 316, in _query self._do_get_result(db) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 147, in _do_get_result self._result = result = self._get_result() File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 349, in _get_result return self._get_db().store_result() During handling of the above exception ((1048, "Column 'starting_email_id' cannot be null")), another exception occurred: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 47, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/http.py", line 40, in inner return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mailman.py", line 117, in _decorator return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/csrf.py", line 54, in wrapped_view return view_func(*args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mailman.py", line 163, in archive add_to_list(mlist_fqdn, msg) File "/usr/lib/python3/dist-packages/hyperkitty/lib/incoming.py", line 153, in add_to_list email.save() File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 739, in save self.save_base(using=using, force_insert=force_insert, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 763, in save_base pre_save.send( File "/usr/lib/python3/dist-packages/django/dispatch/dispatcher.py", line 180, in send return [ File "/usr/lib/python3/dist-packages/django/dispatch/dispatcher.py", line 181, in <listcomp> (receiver, receiver(signal=self, sender=sender, **named)) File "/usr/lib/python3/dist-packages/hyperkitty/signals.py", line 48, in Email_on_pre_save kwargs["instance"].on_pre_save() File "/usr/lib/python3/dist-packages/hyperkitty/models/email.py", line 239, in on_pre_save thread, _thread_created = Thread.objects.get_or_create( File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 588, in get_or_create return self.create(**params), True File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 453, in create obj.save(force_insert=True, using=self.db) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 739, in save self.save_base(using=using, force_insert=force_insert, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 776, in save_base updated = self._save_table( File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 881, in _save_table results = self._do_insert(cls._base_manager, using, fields, returning_fields, raw) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 919, in _do_insert return manager._insert( File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 1270, in _insert return query.get_compiler(using=using).execute_sql(returning_fields) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1416, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 66, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py", line 78, in execute raise IntegrityError(*tuple(e.args)) Exception Type: IntegrityError at /hyperkitty/api/mailman/archive Exception Value: (1048, "Column 'starting_email_id' cannot be null") Postorius Version 1.3.8 HyperKitty Version 1.3.7 Any ideas how to fix this? Klauas

1 year, 1 month

Re: Set member.moderation_action via REST API as part of message approval?

by Mark Sapiro

On 3/3/25 14:27, Andy Matthews wrote: > We're using Mailman 3.3.9. > > Entity<Form> data = Entity.entity(form, MediaType.APPLICATION_FORM_URLENCODED_TYPE); > response = getTarget().path("lists/" + listId + "/config").request().method("PATCH", data); You are patching the list's config and with that patch you are replacing the old value of `accept_these_nonmembers` with the new, not appending the new value. You would need to retrieve the existing value, update it and PATCH that. However, as you know, that setting is deprecated and exists only to support the regexp and @list type of entries. For explicit email addresses, the intent is to create a nonmember and set the nonmember's moderation_action to `defer` - you normally don't want `accept` because that bypasses all the subsequent checks such as administrivia, implicit-dest, max_recipients, max_size, , no_subject, etc. > The result of these two API calls is that both the subscribers and nonmembers properties of the mailing list are updated to include the new email (let's call it abc(a)123.com) The user can immediately send another email which is not held for moderation. The issue comes when a different nonmember sends an email and is approved (let's call it xyz(a)789.com) For some reason this blows out the "always accept" status of user abc(a)123.com and requires their email to be approved again. > > After some research I believe this is because the `accept_these_nonmembers` property has been deprecated (which seems valid because that property remains an empty array). Additional reading seems to indicate that we can now set `moderation_action` on each individual user which supercedes the mailing list's `default_nonmember_action` property (in our case it is `Action.hold`). That is correct, and that is the intended way to deal with nonmember moderation. > The docs indicate that I should be able to submit a patch request to update the moderation action for any user: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > > But it requires the user ID. And when trying to get the user_id for a nonmember it appears that it is not returned by the API. The following call: > `/3.0/addresses/abc(a)123.com` > > returns > ``` > { > "email": "abc(a)123.com", > "original_email": "abc(a)123.com", > "registered_on": "2025-03-03T19:18:35.169703", > "self_link": "https://0.0.0.0:8001/3.0/addresses/abc@123.com", > "http_etag": "\"92c44d0b3b323450f3576e6352acb59b4cc5d6f0a\"" > } > ``` > So I'm not sure how I would be able to update this particular record without a member or user id. > > So, all that said, I'm looking for information on how to do one of the following. > > 1. When submitting a user's email to the `accept_these_nonmembers`, is there a way to indicate that the `member.moderation_action` should be a specific value? No. You can put the email in the appropriate *_these_nonmembers, but that does only that. It doesn't affect the nonmember's moderation_action, nor does it create a nonmember if there isn't one already, but if there is a nonmember with non-None moderation_action, that action takes precedence over *_these_nonmembers. > 2. Retrieve a nonmember record and have it include a member or user id that I can use to explicitly update the `member.moderation_action` value? You must be able to set a nonmember's moderation_action via REST. (The docs may need updating.) Postorius does it, so it can be done, but I don't offhand know the endpoint and I'm leaving the country for vacation tomorrow and don't have time to research it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

Mailman-users search results for query "Postorius"