Search results for "Postorius" - Mailman-users

Re: problem configuring mailman3 on debian bullseye

by Servizio Informatico U.I.C.I. Sezione territoriale di Brescia

Hi, Thank you. I discovered tha I removed all templates but in the db table the template was not removed. It was pointing to localhost and this was the problem. Thanks to all for help! Roberto Burceni Servizio informatico sezionale Tel. 0302209417 (lunedì e giovedì mattina dalle 9:00 alle 13:00, martedì emercoledì pomeriggio dalle 14:00 alle 18:00 E-mail: servizioinformatico(a)uicibrescia.it Sito web: https://www.uicibrescia.it Il 16/03/23 04:20, Mark Sapiro ha scritto: > On 3/15/23 09:55, Odhiambo Washington wrote: >> On Wed, Mar 15, 2023 at 7:10 PM Servizio Informatico U.I.C.I. Sezione >> territoriale di Brescia <servizioinformatico(a)uicibrescia.it> wrote: >> >>> Hi, >>> >>> I created a template but after some tests I deleted it. >>> >>> Now I created only a standard list without modifying any templates. >>> >>> So they are the standard templates coming with the distribution. I >>> did not >>> change also the language >>> >> Maybe you can start by deleting any templates in postorius_emailtemplate >> table in the DB? > > There shouldn't be any, but if the issue is with accessing postorius > templates, that might make it worse. > > If you want only the system default templates, you could do this > database query to remove any non-defaults: > > DELETE FROM templates; > > That will ensure that you aren't accessing Postorius for any templates. >

2 years, 10 months

Re: Mailman 3 Installation

by Mark Sapiro

On 1/16/21 6:06 PM, bruce.dubbs(a)gmail.com wrote: > I am trying to set up Mailman 3 on a new server. So far I have run: > > pip3 install Django==3.1.5 This will be a minor issue. django-mailman3 requires Django>=2.0,<3.2; HyperKitty requires Django>=2.2,<3.2, but postorius requires Django>=1.11,<3.1. We really should be more consistent with these requirements, but what this means is > pip3 install postorius will install Django 3.0.11 alongside Django 3.1.5. > pip3 install Hyperkitty > pip3 install mailman > pip3 install uwsgi > > All that went well. I've been struggling with the configuration though. I am using /etc/mailman.cfg and that seems to be explained in the documentation OK. From there I am confused. > > I do have sqlite installed, but the documentation discusses mysql/mariadb and postresql. What are the considerations as to why I would need one of these other DBs? You can use sqlite, but if you don't already have a mysql/mariadb database on the server, we recommend postgresql for performance and robustness. I personally have had issues with mysql and use postgresql on one production server that uses mysql for other applications. > I think I can follow the instructions to set up postfix. > > In the section 'Configure Web Frontend', it discusses setting up the administrator. As I want to put Mailman on /srv/mailman I can create that, but what should the owner/permissions be? Later the docs discuss editing Django's settings.py. Where do I find that file? I'll note here that my experience with python is quite limited and my knowledge of Django is nil. There should be a 'mailman' user that is the user under which you run things. Don't run things as root. sudo chown -R mailman:mailman /srv/mailman For settings.py and some others, see <https://gitlab.com/mailman/mailman-suite/-/tree/master/mailman-suite_project>. The end of settings.py imports from settings_local so you put your local overrides in settings_local.py in the same directory as settings.py > Later in the section 'Set up HyperKitty', it sends me to a page that discusses installing it. I did that with pip3. Then it says to 'Setup your django project'. What django project is that. Postorius and HyperKitty. See settings.py. These files, settings.py and settings_local.py need to be in a directory that also includes an empty __init__.py so python can import from it and this directory needs to be in the path that Django runs with. This is a shell script I use to run django. It uses a virtualenv, but that isn't necessary. Also my stuff is in /opt/mailman/mm/, but it could just as well be /srv/mailman. #!/bin/bash . /opt/mailman/mm/venv/bin/activate cd /opt/mailman/mm export PYTHONPATH=/opt/mailman/mm export DJANGO_SETTINGS_MODULE=settings django-admin $@ > I would appreciate advice or a pointer to where I can figure this out. Thanks. There is a work in progress you may find more helpful. See <https://gitlab.com/mailman/mailman-suite-doc/-/merge_requests/55#note_48712…> and the 'Rendered documentation' linked therefrom. You might also find <https://wiki.list.org/x/17891998> and/or the docs linked from its first paragraph to be helpful. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

Re: Syncing Real Name between user account and membership

by Abhilash Raj

On Sat, Dec 19, 2020, at 10:42 AM, Stephen J. Turnbull wrote: > Andreas Barth writes: > > > a user was mass-subscribed (with a wrong name) and now registered > > and changed his name via the web interface but the list entry is > > not changed. > > I don't recall the design discussion, but I'm pretty sure that this > distinction was intentional. The idea was that people might want to > have different display names associated with different addresses (eg, > you probably don't want your User display name associated with an > address you use on anonymized lists). I'm not sure that option has > any merit in practice. > > @ Abhilash: > > Since Postorius doesn't provide a way to manage address-specific > display names, we should probably have Postorius propagate display > name changes. I believe that is normally what the user wants. > > What does everybody think? +1, I've been thinking the same. I am just wondering if Core's API should do this (probably not by default, but with a bool parameter that P can use every time), or should we iterate over all addresses and PATCH the display names in them (would be slower, with multiple API requests). I am leaning towards the first option. What do you think? > _______________________________________________ > 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, 1 month

Held messages: Long time waiating for response of the Mailman API

by Stephan Krinetzki

Hello, We are using Mailman 3.3.5 with Hyperkitty 1.3.5. Mailman 3 is installed in a venv and deployed using Apache and uwsgi. This works quite well so far, only withheld messages cause us a problem: If we try to approve them via Postorius, the message is delivered to the list immediately, but the success message in Postorius takes a long time - on average the process hangs for three minutes until the message is no longer displayed. We have already adjusted the timeout in gunicorn.cfg, but this does not improve the situation. Are there any tips on how we can speed up the REST API? Or is it even a configuration error? Greetings Stephan

4 years

List nonmembers

by Stephen J. Turnbull

Andrew Bernard writes: > Under Users for a list, there is a category for List > nonmembers. What does this term mean? [It's rather curious > philosophically when you think about it, because I would have > thought that the category [all humans - list members] fits that > category term.] I don't recall the exact definition of "list member", but I can't resist explaining the "philosophy". :-) In the mail system as a whole, what we can confirm is a mailable mailbox. That corresponds to an *address* in Mailman. But users (typically humans) often have multiple addresses, that they would like to configure together (eg, single signon, same setting for not-me-too, etc). Thus we have a *user* concept, which requires a agent to log in and establish a *user* and attach addresses to it. I don't remember the exact details, but both *users* and *addresses* can exist independently of the other, though they are normally linked. Finally, a *subscription* is a link between an *address* and a *mailing list*. ISTR that merging *users* in the database is kind of annoying, so instead of automatically creating a *user* to back every known *address* (eg, when banned or moderated), the *address* is allowed to participate in the list as a banned or moderated address without being related to a *user*. There may be other cases where an *address* lacks a *user*. I'm pretty sure there are ways in Postorius to create a *user* that has no *addresses*, although I've not tried, and I don't know if such Postorius users would be reflected in the core database. Steve

6 years, 6 months

Re: sqlite3 Database "read only" error on mailman_sync job

by Abhilash Raj

On Sun, Sep 1, 2019, at 3:22 AM, ugniusviln(a)gmail.com wrote: > Hi. All the project installation is under the same user / path and > it works. Archiving working as well, (just one remark: no matter what > to set in postorius, hyperkitty shows list as public) > I have found work around - it is possible to change list as private in > "admin" page. > I started to get issues with runjobs after I have created couple of > new lists with "no archive" option. How did you install all these components. It seems there the installation is broken in weird ways. > > If as owner user from project home I run: > > django-admin mailman_sync > > Traceback (most recent call last): > File > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/utils.py", > line 84, in _execute > return self.cursor.execute(sql, params) > File > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py", > line 383, in execute > return Database.Cursor.execute(self, query, params) > sqlite3.OperationalError: attempt to write a readonly database > > "django-admin runjob sync_mailman " - makes read only errors as well. > "django-admin runjob new_lists_from_mailman" > django.db.utils.OperationalError: attempt to write a readonly database > END TRACEBACK > > I did not find information how to fix this. It was worked without errors > before. > I noticed, that if I stop mailman, "django-admin mailman_sync" starts > to work. > If I start "mailman start", then "django-admin mailman_sync" failing > again. > I did not check other jobs, but I think what is related to database, > will get errors. > Seems mailman locking the database. It is not a file permissions issue. > Mailman db location is: /project_directory/var/data/mailman.db > > if to rename /project_directory/var/data/mailman.db to something, > mailman creates database file size 0, django-admin runjobs start > working, but of course postorius stops working. I did it for testing. > I have returned this database file back, postorius started to work > again, but django-admin runjobs does not work, error: "database read > only". > Please help me how to fix this issue. > _______________________________________________ > 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)

6 years, 4 months

Re: Whitelist non subscriber

by Barry Warsaw

On Aug 10, 2017, at 13:05, Mark Sapiro <mark(a)msapiro.net> wrote: > > Mailman 3 defines the list attribute accept_these_nonmembers, but it is > not currently implemented to actually have any effect, nor is it exposed > in Postorius. Yes, that attribute is deprecated and (almost) completely removed. > At the present, I think you would have to create a user record with the > address and add that user to all lists with role nonmember and > moderation_action 'defer' to apply subsequent tests or 'accept' to > unconditionally accept posts from that address. That’s the way it should be done. Those actions may not be exposed yet in Postorius or the CLI, so you might have to do it with a `wishlist` script. -Barry

8 years, 5 months

Re: Postorius no connection to REST API

by Richard Rosner

WARNING 2021-08-20 11:49:22,941 3975 django.request Not Found: /mailman3 WARNING 2021-08-20 11:49:22,941 3975 django.request Not Found: /mailman3 WARNING 2021-08-20 11:49:22,954 3975 django.request Not Found: /mailman3 WARNING 2021-08-20 11:49:22,954 3975 django.request Not Found: /mailman3 [pid: 3975|app: 0|req: 17/16] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:10 2021] GET /mailman3 => generated 5651 bytes in 13321 msecs \ (HTTP/1.1 404) 5 headers in 170 bytes (1 switches on core 0) [pid: 3975|app: 0|req: 17/17] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:07 2021] GET /mailman3 => generated 5651 bytes in 16373 msecs \ (HTTP/1.1 404) 5 headers in 170 bytes (1 switches on core 1) WARNING 2021-08-20 11:49:32,820 3975 django.request Not Found: /accounts WARNING 2021-08-20 11:49:32,820 3975 django.request Not Found: /accounts [pid: 3975|app: 0|req: 18/18] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:32 2021] GET /accounts => generated 5651 bytes in 251 msecs (H\ TTP/1.1 404) 5 headers in 170 bytes (1 switches on core 0) WARNING 2021-08-20 11:49:43,517 3975 django.request Not Found: /archives WARNING 2021-08-20 11:49:43,517 3975 django.request Not Found: /archives [pid: 3975|app: 0|req: 19/19] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:43 2021] GET /archives => generated 5651 bytes in 99 msecs (HT\ TP/1.1 404) 5 headers in 170 bytes (1 switches on core 1) The proxy pass config is <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! Proxypass "/mailman3" "http://127.0.0.1:8000/mailman3" ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" ProxyPass "/django" "http://127.0.0.1:8000/django" ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" ProxyPass "/archives" "http://127.0.0.1:8000/archives" </IfModule>

4 years, 5 months

Re: WSGI configuration

by Andrew Hodder

It appears you're looking at the settings for your wsgi service (it may be not all those variables are necessary, I'm using uwsgi and it's missing some of those). That's it's own service separate from mailman; it exists as a middle man between the django (postorius/hyperkitty) and your webserver. I have a /etc/uwsgi.d/postorius.ini config like this (please note I'm using this with nginx instead of apache): [uwsgi] uid = nginx gid = nginx plugin = python module = postorius.wsgi virtualenv = /opt/mailman/venv2/ wsgi-file = /opt/mailman/postorius/postorius/wsgi.py socket = /opt/mailman/%n.sock chmod-socket = 777 stats = 127.0.0.1:9191 pidfile = /opt/mailman/%n.pid daemonize = /var/log/uwsgi/%n.log logto = /var/log/uwsgi/%n_details.log master = true workers = 4 enable-threads = true vaccum = true Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541 On Thu, Oct 5, 2017 at 9:50 AM, Loring <rloring(a)bnl.gov> wrote: > So I am starting to install mailman3 and following the documentation and > am up to the point of configuring the wsgi. The docs give me a config to > use (see below) > > [uwsgi] > # Port on which uwsgi will be listening. > http-socket = 0.0.0.0:8000 > > # Move to the directory wher the django files are. > chdir = /path-to-django-project-directory/ > > # Use the wsgi file provided with the django project. > wsgi-file = wsgi.py > > # Setup default number of processes and threads per process. > master = true > process = 2 > threads = 2 > > # Drop privielges and don't run as root. > uid = 1000 > gid = 1000 > > # Setup the django_q related worker processes. > attach-daemon = ./manage.py qcluster > > # Setup the request log. > req-logger = file:/path-to-logs/logs/uwsgi.log > > # Log cron seperately. > logger = cron file:/path-to-logs/logs/uwsgi-cron.log > log-route = cron uwsgi-cron > > # Log qcluster commands seperately. > logger = qcluster file:/path-to-logs/logs/uwsgi-qcluster.log > log-route = qcluster uwsgi-daemons > > # Last log and it logs the rest of the stuff. > logger = file:/path-to-logs/logs/uwsgi-error.log > > Where does this config go? Does in go in the mailman3.cfg? > > Any help would be appreciated. > > -- > Richmond Loring > rloring(a)bnl.gov > Advanced Systems Engineer > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

8 years, 3 months

Language Support In Templates

by Brian Carpenter

Hello MM3 Users, I have a question regarding the use of templates in different languages. I created a template for the unsubscribe notification in Postorius in Greek. The template shows up fine in Greek via Postorius. However the email that is sent out has a bunch of question marks where the Greek should be: ??????????? ?????????? ???????? ?????????? email ???? ???, ????? ????? ? ??????????? GNU Mailman ???? ????? $. ?????? ??? ?????? ????????? ??? ?? ????????? email $user_email ?????? ?? GNU Mailman ?????? ?? ?????????? ??? ??????? ???, ?????? ????? ?? ????????????? ?? ?????? ???. ???????? ?? ?? ?????? ????? ?????????? ?? ???? ?? ??????. ? ?? ?????? ?? ????????????? ??? ???????? ?????? - ??? ???? ?? ???????? line - ?? ??? ?????? ???? ?? $ request_email: confirm $token ????????? ??? ? ???? ???????? "?????????" ?? ???? ?? ?????? ?????? ?? ?????????? ?? ???????????? ?????????? ?????????????. ??? ??? ?????? ?? ??????????? ??? ????? ?? ????????? ???????????? ????????????, ????? ???????? ??? ??????. ??? ????????? ??? ??????????? ????????? ??? ?? ?????, ? ????? ????? ?????????, ???????? ?? ?????????????? $owner_email What does it take to get templates to send out messages in a different language then the interface itself. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 11 months

Mailman-users search results for query "Postorius"