Search results for "Postorius" - Mailman-users

Re: Postorius no connection to REST API

by Richard Rosner

Mark Sapiro wrote: > > But whatever is listening on port 8001 is apparently not Mailman's rest > server. What does > ps -fww 14080 > or whatever PID is currently listening on port 8001 show. UID PID PPID C STIME TTY STAT TIME CMD list 15972 15963 0 Aug11 ? Sl 0:13 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 > > OK. > Perhaps instead you should have > uid: list > gid: list > in your uwsgi configuration if you don't already. Tried that while also switching mailman3-web.service to list:list, exactly the same error. Also, I have /run/mailman3-web/uwsgi.sock owned by list:list now instead of www-data:www-data. What the logs say: *** Starting uWSGI 2.0.18-debian (64bit) on [Thu Aug 12 08:46:37 2021] *** compiled with version: 8.2.0 on 10 February 2019 02:42:46 os: Linux-4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) nodename: mail machine: x86_64 clock source: unix pcre jit disabled detected number of CPU cores: 2 current working directory: / detected binary path: /usr/bin/uwsgi-core chdir() to /usr/share/mailman3-web your processes number limit is 3831 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) error removing unix socket, unlink(): Permission denied [core/socket.c line 198] bind(): Address already in use [core/socket.c line 230] Not sure if that means the two directories need to be owned by list, currently they are owned by root > > I'm not familiar enough with this form of ProxyPass using sockets to > understand what the localhost:8001 does in this context, but uwsgi > should not be doing anything with port 8001. In a configuration using > TCP, it would listen on port 8000. Port 8001 is where Mailman's REST API > server listens. uwsgi should receive connects in your case via the unix > socket and then pass them to Django via the application in wsgi.py > Also, you may want other paths proxied to uwsgi, namely at least some of > hyperkitty, postorius, archives, accounts, admin and user-profile. Ok, I removed that port again, now it's exctly like in the automatically generated config file. And you mean like <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /hyperkitty unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /postorius unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /admin unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /archives unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /accounts unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /user-profile unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ </IfModule> > > These should be 'list', not 'www-data'. That's your permissions issue on > settings.py

4 years, 8 months

Re: Hiding an ML from a site

by Odhiambo Washington

On Wed, Feb 7, 2024 at 9:45 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On February 6, 2024 7:45:14 AM PST, Odhiambo Washington > <odhiambo(a)gmail.com> wrote: > > > >I had this set to True in settings_local.py, but False in settings.py. > >So it seems to not make a difference in my setup. > > In a standard setup, anything set in settings_local.py overrides any > corresponding setting in settings.py. > > That said, FILTER_VHOSTS is not perfect. It only works for Postorius if > the separate web hosts also have different mail hosts. See lines 1051 et > seq at > < > https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list… > > > What should I do then? Edit some file? Apply some patch? It's pretty easy for me to create a DNS record for the same server (IP) for use with the web host that I'd like to hide. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 3 months

Re: nginx configuration on a multitasking server

by Mark Sapiro

On 12/22/21 6:20 PM, David Newman wrote: > > Update: The above worked fine until MM3 informed a list owner of pending > subscription requests, with a URL like this: > > https://lists.example.com/mailman/admindb/listname > > and that URL returned a 404 error. This looks like a uwsgi issue as discussed at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… although that's with apache and not nginx so it may not be. > Adding a stanza for 'location /mailman/' to the nginx config above > clears the 404 error, but Postorius returns "Page not found" with no > entry in the web or MM3 logs, and a 200 OK in the Nginx logs. > > I think the URL is supposed to go to the list page in Postorius. How to > configure this so that list owners and moderators get a valid URL for > list management? I'm not sure what the solution is in this case, but a workaround would be to add url(r'^mailman/', include('postorius.urls')), to the urlpatterns list in urls.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

Re: Mailman, etc. upgrade woes and persistent bugs

by Brian Carpenter

On 2/12/21 8:55 PM, Abhilash Raj wrote: > IIUC, I think what Allan is trying to point out is that if your account was > disabled due to bounces, there is no real visual indication about that if > you go to any of the Preferences pages (either, Global preferences, > List based preferences of address based preferences). > > Even if you login as an admin and go to Member Option's view, you > won't see any visual indication about the delivery being disabled. > > The is definitely a bug, caused due to the fact that "Delivery Status" field > only has two options, "Enabled" and "Disabled". Internally, this field can > have 4 values, "enabled", "by_user" (maps to "Disabled" in Postorius), > "by_admin" (means disabled by admin) and "by_bounces" (means > disabled due to bounces). So, when the value of the field is among > the last two options, it appears as "unset" with no options selected, > which unfortunately is also how it looks by default since all options > are "unset" from start. > > The "fix" for this issue would be simply adding a new choice to the > delivery_status field with a caveat that it is only a Readonly option to > see that delivery is disabled due to bounces and not choosable as > a valid delivery_status value by user or admin when submitting the > form. I really wish you guys rework that List Member's page for the sake of List Owners. With Affinity our List Owners can: 1. See the delivery status for every list members (enabled or disabled). If Disabled, there is a little icon (u=user, b=bounce, m=moderator) that lets the List Owner know the reason for the disable setting. 2. Sort members by delivery status (enable/disable). So a List Owner can choose a certain delivery status and only those members that have that status are shown. 3. Informs a List Owner whether a list member is registered with the UI. 4. See the moderation action set for every member. You have plenty of real estate on that member page to vastly improve it and to be honest the MM2 member management page is superior to Postorius's member page. Personally instead of trying to get a reskin of Postorius that makes it look like Mailman 2 from the GSOC folks, I would push for a revamp of certain sections of Postorius that brings it into the modern UI era. That Member page is seriously lacking. I am not trying to be mean here but I really felt Allan's pain yesterday. No List Owner should be that handicap to manage their own list members. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 2 months

Re: Welcome message issue

by Mohsen Masoudfar

Thank you Mark! You are helpful as always. I am running: Postorius Version 1.1.2 That explains the issue. Mohsen ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, October 22, 2024 5:38 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Welcome message issue [EXTERNAL EMAIL] On 10/22/24 13:34, Mohsen Masoudfar wrote: > Good afternoon > I have an issue with welcome message. > > A list owner is requesting to update the welcome message for only one of their lists. They are requesting to change the default text and insert additional URLs pointing to sites related to their list. > I know there is a URI field that you may include a web page. But this doesn't work and gets ignored. If you are referring to the `uri` field in the template table this should work if the `name` is `list:user:notice:welcome` and the `context` is the list_id of the target list. > - is there a mailman cli option to update the default template for a single list? There is no specific cli option. A site admin can address this by creating a custom template at Mailman's var/templates/lists/LIST_ID/LC/list:user:notice:welcome.txt where LIST_ID is the desired lists ID and LC is the preferred language. The list owner can create a custom list:user:notice:welcome template via Postorius. > > I couldn't find it in WUI. Do you mean GUI? If so, since at least Postorius 1.2.0 there has been a `Templates` choice in the second level nav in the lists view. > I reviewed all parameters and variables of the list and couldn't find one that might be related to it. > > We are running an old version of Mailman 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to mmasoudf(a)aaas.org

1 year, 6 months

Re: Accept these non-members

by Mark Sapiro

On 3/6/26 12:52, Lars Bjørndal wrote: > Thanks! You wrote: > >> On 3/6/26 02:43, Lars Bjørndal wrote: >>> Hi, list! >>> >>> I have an announce only Mailman3 list. When I log into the web interface >>> as an admin user, and go to the specified list, and choose Settings, I find >>> the Message Acceptance tab. There, I find the edit field Accept these >>> non-members. But this field is empty, although I know that some people >>> have permissions and are able to post to this list. How can I find the >>> list of these non-members and add more people or delete someone? >>> >>> I'm running Mailman version 3.3.10, and mailman-web version 4.2.21. >> >> I don't know what mailman-web version 4.2.21 is. Is this some downstream >> package? > > With `pip list`, some of the packages is: > > Django 4.2.21 > django-mailman3 1.3.15 > HyperKitty 1.3.12 > mailman 3.3.10 > mailman-hyperkitty 1.2.1 > mailman-web 0.0.9 > mailmanclient 3.3.5 > postorius 1.3.13 So your mailman-web is 0.0.9 and it's Django that's 4.2.21. I understand. >> These are nonmembers whose moderation action is accept or defer. If your >> Postorius is >= 1.3.6, and the number of nonmembers is manageable you can >> just view the nonmembers list in Postorius and see their moderation action. > > You mean from the web interface at example.com/mailman3 > list? Yes >> Otherwise a `mailman shell` interaction like >> ``` >> $ mailman shell -l list.example.com >> Welcome to the GNU Mailman shell >> Use commit() to commit changes. >> Use abort() to discard changes since the last commit. >> Exit with ctrl+D does an implicit commit() but exit() does not. >> The variable 'm' is the list.example.com mailing list >>>>> for nm in m.nonmembers.members: >> ... if nm.moderation_action in (Action.accept, Action.defer): >> ... print(f'{nm} {nm.moderation_action}') >> ... >>>>> >> ``` >> will print those nonmembers with Action.accept or Action.defer. > > What's the difference between Action.accept and Action.defer? Action.accept accepts the message immediately with no further checks. Action.defer passes the membership checks but still goes on to check other things like mis-addressed email commands messages with implicit destination messages with too many explicit recipients messages that are bigger than a specified maximum messages with no, or empty, Subject headers messages with digest Subject or boilerplate quote messages matching a bounce_matching_header line -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months

Re: Is it possible to add non-members in regex format in Mailman 3 ?

by Shashikanth Komandoor

Thank you Abhilash for your response. I am currently running Postorius 1.0.2 and mailman core 3.3.1. I have deployed in a production environment and have done some customizations by adding the SMS notifications and removed some options which are not required to my organization like social logins and so. Now, if I upgrade only the Postorius from 1.0.2 release to 1.3.3 can I get all the customizations I had done or will I have to reconfigure the same customized code in the newer version? <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Jun 16, 2020 at 11:09 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > On Tue, Jun 16, 2020, at 7:09 AM, Shashikanth Komandoor wrote: > > Hi Team, > > > > In mailman 2, I was able to add the non-members in the > > respective privileged box even using the regex also which will be used to > > add the domains instead of a single mail id. > > > > But in mailman 3, I am not allowed to add the non members in > > the regex format. Of course it is allowing me to add individual mail ids > > and give permissions. But I want to add a non-member which may be > something > > like the entire cisco.com domain on which I want to set the rule. > > > > You can do that with Postorius 1.3.3 (which was released recently) and > Mailman Core 3.3.1. > > > > Please help me out by suggesting over this or if mailman 3 is > > not providing then please hint me out with a work around at least. > > > > -- > > Thanks & Regards, > > Shashi Kanth.K > > 9052671936 > > > > > > > > > > < > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai… > > > > Virus-free. > > www.avast.com > > < > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai… > > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > _______________________________________________ > > 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) > _______________________________________________ > 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 & Regards, Shashi Kanth.K 9052671936

5 years, 10 months

Re: Moderated unsub requests are not provided by mailman3 service

by Thomas Hochstein

Joachim Schrod schrieb: > I tried to gather data if an update to Debian 12 (bookworm) would > help. But packages.debian.org is not helpful at all, for me. I know > that this is beyond the realm of this mailing list, but perhaps > someone here has that information and can supply it: Debian 12 > (bookworm) package mailman3-web has the version "0+20200530-2.1". Yes. "mailman3-web" is a package containing "ready to run" versions of Postorious and Hyperkitty: | This django web application provides the Mailman3 Postorius web interface | and the HyperKitty mailinglist archiver integrated into one project. | | The package automates most of the necessary configuration for the Django | project (database setup, webserver configuration, secret and API key | generation, Django project configuration) to get a ready-to-use Mailman3 | web suite. <https://packages.debian.org/bookworm/mailman3-web> > Can anybody please provide me with information what versions of > mailman3 core and mailman3-web are in this package; i.e., in Debian 12 > (bookworm)? | list@angmar:~$ mailman --version | GNU Mailman 3.3.8 (Tom Sawyer) mailman3-core on Debian 12 contains - GNU Mailman 3.3.8 (Tom Sawyer) mailman3-web on Debian 12 has - Postorius Version 1.3.8 - HyperKitty Version 1.3.7 Regards, -thh

1 year, 5 months

moving lists to another server

by Stephen J. Turnbull

bryan.kartzman(a)yu.edu writes: > I have both my mailman lists and django config in postgres > databases. These are Mailman 3 lists? What Django config? Do you mean Postorius and HyperKitty? Do you intend to use Postorius and HyperKitty on the new server? > If I want to move my lists to another server that is running > mailman 3, aside from copying the databases to the other server, Do you mean the other server is already actively distributing Mailman list traffic, managing users and archives? Or is it fresh instance? > what other things (perhaps all files under /var/lib/mailman3?, etc) > would I need to bring over to the other server? That's going to vary depending on the way your existing server is set up. A Mailman 3 instance is a complex system of cooperating applications. Assuming you have not patched or added any Python code, typical configuration and customizations include 1. Your webserver (Apache, nginx are most common) needs configuration to handle WSGI applications and may need modules enabled or installed for the WSGI server. This is usually installed as an OS distro package, and the configurations will live in /etc/apache2 or similar for another webserver. Depending on other content served by the two hosts you may have to edit the configuration on the new host rather than copy it from the old one. 2. The WSGI server is typically a separate application, although there is an Apache module for this. Gunicorn is a Python application usually installed via pip. I like to keep its Django configuration, which I call gunicorn.conf.py, in /etc/mailman3. (Mailman core also uses gunicorn, but that is transparent to you, it should not need custom configuration.) uwsgi is a C or C++ application normally supplied as a distro package. Don't know where it keeps its config files but since it's a distro package my first guess is /etc/uwsgi. 3. Your MTA, usually Postfix or Exim4, maybe Sendmail or qmail needs to be configured to route mail to Mailman, and apply any milters, signatures, and perhaps anti-yahoo configurations such as ARC. 4. Your database server, usually PostgreSQL or MySQL. 5. Mailman core has a single configuration file mailman.cfg, which I keep in /etc/mailman3. It also has a crontab, which in Debian- derived systems typically lives in the file /etc/cron.d/mailman3. Note that this could be implmented as a systemd timer, but I don't know if any distros do that. 6. Django, Postorius, and HyperKitty together constitute the mailman-web subsystem. I strongly recommend you use the mailmanweb Python package to manage Django and its applications. In any case I am not familiar with other organizations of those packages, so I'm going to assume it. If you are not using mailmanweb, you will need to be careful because most subpackages in the Django subsystem name their configuration files settings.py, urls.py, and views.py just like top-level, and distinguish them by using Python's attribute notation (eg, postorius.urls). a. Django application configuration for Postorius and HyperKitty goes in settings.py, which I put in /etc/mailman3. b. Django site configuration for Postorius and HyperKitty goes in urls.py (the routing configuration mapping URLs to views) and views.py (mapping views to Python code). I put these in /etc/mailmn3. c. Full-text indexing for HyperKitty. Default is Whoosh (a Python application) whose configuration goes in Django's settings.py. I prefer Xapian, which requires a separate application (Debian and Ubuntu have packages), but the needed configuration can be done in the top-level settings.py. 7. Template customization. If you have any customized templates for Mailman's email or Django's views, you'll need to copy and move them too. I haven't customized email, but Django's page templates can be kept separately with a path variable set in settings.py. I put them in a hierarchy under /etc/mailman3/templates. Maybe Mailman core has a similar setting? 8. Transient files. Aside from code and configuration, everything in Django is in the RDBMS, there are be no random files strewn around as far as I know. Mailman core is another matter. You can hope that all Mailman transient files are in its "var" hierarchy. $var_dir (the setting in mailman.cfg or inherited from schema.cfg) is the root of this hierarchy. I set var_dir=/opt/mailman/var, I think Mark may use var_dir=/opt/mailman/mm/var. I would guess that FHS-conformant distros would likely use var_dir=/var/lib/mailman3. a. The queue directories $var_dir/queue/* should be empty. Shut down the incoming mail and let mailman run until it's clear. (Normally takes < 5 seconds.) The exceptions are the shunt and bad queues, which are messages that Mailman doesn't know what to do with. With the venv active, run "mailman unshunt" to attempt to clear the shunt queue. Move anything that's left in shunt as well as any .bak or .tmp files into the bad queue for later treatment. These can be copied to the bad queue in the new instance. Use "mailman qfile <file>" to examine them to see if they can be deleted. b. I think the only stuff that ends up in the $var_dir/lists/* directories are digests being built for later distribution. Use the usual tools to send them off or copy them over to the new instance. c. There should be nothing in $var_dir/archives/hyperkitty/spool, which is temporary storage for messages to be archived. That is, it should get cleared up by the few seconds while incoming mail is stopped and outgoing messages are being processed. If there's anything still there, stash it away for later examination using "mailman qfile". (Don't put it in queue/bad or queue/archive though, this is a different process from the normal pipeline.) I think that's about it. Steve

2 years, 6 months

Re: Custom Templates and reject_message() error

by Abhilash Raj

On Sat, Aug 1, 2020, at 9:38 AM, Marcel Pietschmann wrote: > Hi everyone, > > I'm running Mailman 3 in maxking's Docker container (tag 0.3). Mailman3 > runs really well, thanks for that good job! But I noticed two errors. > > 1) When a new list is created, Mailman will not notify the list owners > of their new mailing list. I tested it with the default template > "domain:admin:notice:new-list.txt" and my own template (which i copied > in $var_dir/templates/domains/DOMAIN/de/ > > Any customs templates in $var_dir/templates... aren't sent out, always > the default templates from > /usr/lib/python3/site-packages/mailman/templates/de. I can't find > anything in the logs for that issue. Do you mean to say the notification isn't sent out at all or that the custom templates aren't used? > > 2) When a post requires an approval and I reject it with a notification > a server error occurs: "An error occurred while processing your request." > > The Traceback in mailmanweb.log is: > > ERROR 2020-08-01 16:19:19,926 17 django.request Internal Server Error: > /postorius/lists/list.domain.de/held_messages/moderate > Traceback (most recent call last): > File > "/usr/lib/python3.6/site-packages/django/core/handlers/exception.py", > line 34, in inner > response = get_response(request) > File "/usr/lib/python3.6/site-packages/django/core/handlers/base.py", > line 115, in _get_response > response = self.process_exception_by_middleware(e, request) > File "/usr/lib/python3.6/site-packages/django/core/handlers/base.py", > line 113, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File > "/usr/lib/python3.6/site-packages/django/views/decorators/http.py", line > 40, in inner > return func(request, *args, **kwargs) > File > "/usr/lib/python3.6/site-packages/django/contrib/auth/decorators.py", > line 21, in _wrapped_view > return view_func(request, *args, **kwargs) > File "/usr/lib/python3.6/site-packages/postorius/auth/decorators.py", > line 60, in wrapper > return fn(*args, **kwargs) > File "/usr/lib/python3.6/site-packages/postorius/views/list.py", line > 549, in moderate_held_message > mailing_list.reject_message(msg.request_id, reason=reason) > TypeError: reject_message() got an unexpected keyword argument 'reason' This seems to be a bug, I forgot to bump Mailmanclient when I bumped Postorius. I have a PR that I am working on[1], will tag and push as soon as I can get it to build, there seems to be some build failures. [1]: https://github.com/maxking/docker-mailman/pull/389 > Thanks a lot for any suggestion. > > Greets > Marcel > > Mailman Core Version: 3.3.1 > Mailman Core API Version: 3.1 > Postorius Version 1.3.3 > HyperKitty Version 1.3.3 > _______________________________________________ > 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, 9 months

Mailman-users search results for query "Postorius"