Search results for "Postorius" - Mailman-users

Re: Member Issue Discovered

by Brian Carpenter

On 10/29/20 11:26 AM, Mark Sapiro wrote: > On 10/29/20 5:17 AM, Brian Carpenter wrote: >> On 10/29/20 4:27 AM, Alex Schuilenburg via Mailman-users wrote: >>> On 29/10/2020 01:57, Brian Carpenter wrote: >>>> With Mailman 3, every list owner has the ability to remove a reply in >>>> a thread, a complete thread, and even the entire archives. That is a >>>> welcome difference from MM2 in my opinion. >>> A very welcome difference, only I don't see this option in the web >>> interface of my debian 3.2.1 installation. Is this a shell only >>> option, 3.3 feature or configuration option I have missed? >> It is not a shell option. It can be done via Hyperkitty but I am not >> sure when that feature showed up. > > Actually, with current HyperKitty, only site admins can remove messages > or threads or the archive. The ability for list owners to do it is > <https://gitlab.com/mailman/hyperkitty/-/issues/261>. Thanks Mark. To clarify more, we have this ability for List owners with our own custom admin interface (Affinity). I thought Postorius had that. When I checked out Postorius, I was indeed logged in as server owner. Sorry for the incorrect info. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 2 months

Mails are not archived at all -- how to check if Hyperkitty is running or not?

by Stephen J. Turnbull

Franklin Weng writes: > However in the Archive section I couldn't see anything and all the > lists were "inactive" and hence were hidden by default. If you can see that much, HyperKitty is running. > There is no systemd service for Hyperkitty. systemd runs Apache, which loads mod_wsgi, which runs Python, which imports the HyperKitty package, which responds to web requests by building pages dynamically using Django from information from Django's database, which may be backed by MySQL, PostgreSQL, or sqlite3. Sounds complicated, but it performs well once you get it properly configured. Have you sent mail to the lists? Has it been delivered to subscribers? > I confirmed that api_key set in the /etc/mailman3/mailman-hyperkitty.cfg > and /etc/mailman3/mailman-web.py is the same. I also confirmed that the > apache2 wsgi module has been loaded. > > In the mailman.cfg database is set to mysql and in the mailman-web.py > database is set to sqlite3. Does it matter? I don't think they need to be the same. The HyperKitty and Postorius databases are a Django database backed by an RDBMS (typically sqlite3, PostgreSQL, or MySQL). The databases used by the Mailman core and the Django webservices HyperKitty and Postorius are conceptually separate, although they can be backed by the same RDBMS server. However, sqlite3 is likely to result in poor performance compared to PostgreSQL or MySQL. You have to configure HyperKitty's database. In my sqlite3 test installation it looks like this: # Top of settings.py. BASE_DIR is the directory containing settings.py. BASE_DIR = os.path.dirname(os.path.dirname(os.path.abspath(__file__))) # 30-50 lines later: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', # This database file is in the same directory as settings.py. 'NAME': os.path.join(BASE_DIR, 'hyperkitty.db'), # Not used with sqlite3: 'USER': '', 'PASSWORD': '', 'HOST': '', 'PORT': '', } } Does the database file named by 'NAME' exist? I would recommend getting your sqlite3 configuration running, then you know that HyperKitty is partly working if the hyperkitty.db file is getting updated as you test Mailman by sending messages, and you can check if it's fully working by using HyperKitty's web pages. Then convert to MySQL for performance. Steve

6 years, 2 months

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

by Ugnius S

Thank You, Abhilash, to helping. I have checked the processes, but also I have read, that sqlite3 can run in multi writing mode. May mailman processes are next: 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini 6643 ? S 0:00 /usr/bin/python3 /usr/bin/master -C /opt/home/mailman.cfg 659 ? S 0:46 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=in:0:1 6660 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=nntp:0:1 6661 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=digest:0:1 6662 ? S 0:48 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=pipeline:0:1 6663 ? S 0:44 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=archive:0:1 6664 ? S 0:41 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=command:0:1 6665 ? S 0:01 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=retry:0:1 6666 ? S 0:45 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=virgin:0:1 6667 ? Sl 0:16 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=lmtp:0:1 6668 ? Sl 1:30 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=rest:0:1 6669 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=bounces:0:1 6670 ? S 0:49 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=out:0:1 Looks like there are no double. Nothing more is running. 2019-09-05, kt, 03:16 Abhilash Raj <maxking(a)asynchronous.in> rašė: > On Wed, Sep 4, 2019, at 2:05 PM, Ugnius S wrote: > > > I have installed using documentation. My linux distribution version has no > full package available. I have installed step by step: > $ sudo pip3 install mailman > $ sudo pip3 install postorius > > $ sudo pip3 install hyperkitty > > $ sudo pip3 install mailman-hyperkitty > > And of course all mandatory components... Everything without errors, I > can drop db files and I can download mailman-suite again and start from > empty page again. But it will not guarantee that DB will not become READ > ONLY again. Here should be logic. No developing support here? > > > Could you be running two separate processes such that the database is > locked by one and so other finds it as READ Only? When you find a read only > database, can you check if it is open in some other process? > > > > > 2019-09-03, an, 19:36 Abhilash Raj <maxking(a)asynchronous.in> rašė: > > > > 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) > > > -- > thanks, > Abhilash Raj (maxking) > > >

6 years, 4 months

Re: Finding a user to delete them

by Stephen J. Turnbull

Brian Carpenter writes: > I do think List Admins would want an interface to help "manage" a > user account on behalf of a user then what is currently available > in Postorius. Oh, no question about that whatsoever. I'm quite surprised that this facility isn't present yet. (I rarely make mistakes in mass subscribe and the defaults work fine for my subscribers -- or they make their own changes -- so I can't recall ever encountering this need.) I wonder if in Mailman 3 where user profiles exist and are clearly *not* subject to control by *list* admins in the same way that subscriptions are, and in this day of GDPR etc if maybe we need to restrict admin access to various user properties. This sounds like a rather difficult design problem. > I don't see this functionality built into Mailman 3 nowhere near > the extent that Mailman 2 has. Web interfaces are supposed :-( to be easy enough for Great-Grandma to use, so I imagine the designers didn't think much admin intervention would be needed. > My approach with Affinity is definite leaning very heavy on the > needs of list admins atm. Perhaps that's a good division of responsibility between Postorius and Affinity dev processes. Something to think about. Steve

5 years, 10 months

Re: Upgrading mailman 3 venv installation

by Mark Sapiro

On 9/29/21 10:52 AM, Morris Jones wrote: > > In my virtual environment, I ran `pip list -o` and got a significant > list. I noticed that all of the mailman packages seemed to be "Type > sdist" and the framework packages "Type wheel". (Dunno what "Type" means > in this context.) Type is the package type. sdist is a source distribution. wheel is a form of binary distribution. Older forms are egg and bdist. > So I tried `pip list -o | grep sdist` and got a smaller list: > > (venv) mailman@mail:~$ pip list -o | grep sdist > atpublic 2.1.1 2.3 sdist > django-allauth 0.43.0 0.45.0 sdist > django-mailman3 1.3.4 1.3.7 sdist > flufl.i18n 3.1.3 3.2 sdist > flufl.lock 5.0.3 6.0 sdist > HyperKitty 1.3.3 1.3.4 sdist > lazr.config 2.2.2 2.2.3 sdist > mailman 3.3.2 3.3.5 sdist > mailmanclient 3.3.1 3.3.3 sdist > mysqlclient 2.0.1 2.0.3 sdist > postorius 1.3.3 1.3.6 sdist > > Is this a reasonable list of the packages that I should update? Several of those are dependencies. The packages you should upgrade are mailman, postorius, hyperkitty, django-mailman3 and mailmanclient. Dependencies will be upgraded as required. If a dependency is not upgraded, the older version should work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

Re: including a template failed

by Wolfgang Bock

Dear Mark, Q: Can you get https://webmail.domain-02.de/mailman3/postorius/api/templates/list/mylist.li sts.domain-03.de/list:member:regular:footer on the Mailman machine? A: No Q: What is your setting for POSTORIUS_TEMPLATE_BASE_URL? A: was: POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost/mailman3/' Changed it to: POSTORIUS_TEMPLATE_BASE_URL = 'https://localhost/mailman3/' Now another problem occurs: Sep 23 22:51:34 2020 (13492) Cannot connect to SMTP server localhost on port 25 HTTPSConnectionPool ... 'localhost' doesn't match either of 'blog.domain-04.de', 'lists.domain-04.de', 'mail.domain-04.de', 'domain-04.de', 'www.domain-04.de'"))) Port 25 entry results from the manual regarding the postfix configuration: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.ht ml e.g.: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mail.example.com lmtp_port: 8024 smtp_host: mail.example.com smtp_port: 25 Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Sonntag, 20. September 2020 01:05 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: including a template failed On 9/19/20 2:47 PM, Wolfgang Bock via Mailman-users wrote: > Hi, > > I created a new mailinglist and got during the test-process the > following errormessage in my mailman.log after: > ... > Sep 19 22:55:08 2020 (1433) ACCEPT: > <000001d68ec7$2553e6e0$6ffbb4a0$(a)domain-01.de> > > Errors: > > Sep 19 22:55:09 2020 (1436) Cannot connect to SMTP server localhost on > port > 25 > HTTPSConnectionPool(host='webmail.domain-02.de', port=443): Max > retries exceeded with url: > /mailman3/postorius/api/templates/list/mylist.lists.domain-03.de/list: > member :regular:footer (Caused by NewConnectionError('<urllib3.connec > tion.VerifiedHTTPSConnection object at 0x7fc8380f1748>: Failed to > establish a new connection: [Errno -2] Name or service not known')) > ... This is wierd. It looks like we are trying to establish a connection to host='webmail.domain-02.de', port=443 in order to GET /mailman3/postorius/api/templates/list/mylist.lists.domain-03.de/list:member :regular:footer, but the error says "Cannot connect to SMTP server localhost on port 25". I have no idea how port 25 is coming into it. Can you get https://webmail.domain-02.de/mailman3/postorius/api/templates/list/mylist.li sts.domain-03.de/list:member:regular:footer on the Mailman machine? What is your setting for POSTORIUS_TEMPLATE_BASE_URL? -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 4 months

Re: Outgoing messages fro Mailman fails DMARC

by Mark Sapiro

On 04/19/2018 03:22 AM, Henrik Rasmussen wrote: > > Thanks you for the links. According to https://wiki.list.org/DEV/DMARC the MM3 list setting "DMARC mitigation action" (which actually say "Replace From: with list address" in Postorius) should change the From: header. This doesn't seem to work if I don't also set "DMARC Mitigate unconditionally" to Yes, but does if I do. If DMARC Mitigate unconditionally is No, DMARC mitigation action will only be applied if the original From: domain publishes a DMARC policy of quarantine or reject. If the action is not being applied in this case, there is some issue in looking up the DMARC policy for the domain. Possibly, dnspython is not available or there is some other issue with this. In any case, errors should be logged in Mailman's log. > Where do I change defaults for all lists, instead of a per list change in settings/dmarc_mitigations ? You need to do this with list styles. See <http://mailman.readthedocs.io/en/latest/src/mailman/styles/docs/styles.html>. At present, Postorius doesn't allow specifying a style when creating a list, so you may need to modify mailman/src/mailman/styles/base.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

Re: Mailman3-web/Postorius behind Lighttpd

by Mark Sapiro

On 2/16/22 10:00, Élodie BOSSIER via Mailman-users wrote: > > I'm using Mailman 3.3.3 (Tom Sawyer) on Debian Bullseye 11.2 from > packages : When you install Debian packages, your primary support resource is Debian. ... > I can access from localhost to http://127.0.0.1:8000/ which move me > correctly to http://127.0.0.1:8000/postorius/lists/ and all seem to be > correct. > > But 127.0.0.1:8000 listen only in localhost : > #netstat -tanpu | grep 8000 > tcp 0 0 127.0.0.1:8000 0.0.0.0:* LISTEN > 626175/python3 Which is as it should be. > So I try to use my lighttpd as proxy as recommanded with this config : > > >> scgi.protocol = "uwsgi" >> scgi.server = ( >> "/" => (( "host" => "127.0.0.1", "port" => 8000, "check-local" => >> "disable" )), >> ) > > but it's return me a "502 Bad Gateway". I don't know anything about lighttpd, but the fact that you can access http://127.0.0.1:8000/ from localhost and that seems to work suggests that you shouldn't be using uwsgi protocol, but just a straight http proxy. See https://redmine.lighttpd.net/projects/lighttpd/wiki/HowToPythonWSGI#lighttp… and https://redmine.lighttpd.net/projects/lighttpd/wiki/Docs_ModProxy -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

Re: Error -- postorius Un-handled exception

by Odhiambo Washington

On Sun, Jan 28, 2024 at 11:26 AM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Odhiambo Washington writes: > > > The issue you're dealing with in that case is this change in > > PostgreSQL-15 discussed in this blog: > > > https://www.cybertec-postgresql.com/en/error-permission-denied-schema-publi… > > Thank you for the reference! > > If you have a Mailman-only host, with a Mailman-only PostgreSQL, or > The Cabal of equally responsible maintainers are the only people who > work on the Postgres cluster, the two approaches are basically > equivalent. > > My take is that the default "right thing" is to transfer ownership of > the 'mailman' database to the 'mailman' user, and use "GRANT ALL ON > SCHEMA public TO fred" in the case that you don't want to give "sudo > mailman" to Fred. > > Rationale: I believe there are a number of things that the 'postgres' > user can do that other users cannot, and you probably don't want > random contractors or new volunteers to have those privileges. On the > principlee that 'postgres' should only do those things that only > 'postgres' can do, you want to make the 'mailman' user the owner of > the 'mailman' database (and 'mailmanweb' too if you go that route). > Then if you have a user 'fred' who may be working on both mailman and > non-mailman databases in a session, then instead of giving sudo > mailman to Fred, 'mailman' can grant all on schema public in mailman > to 'fred'. > > It's a really fine difference, and probably will matter to almost > nobody running Mailman 3. I do think > > user 'mailman' owns the 'mailman' database > > is conceptually simpler than > > user 'postgres owns the 'mailman' database and 'mailman' has ALL > privilege on the PUBLIC schema > > Right? > Right! That makes more sense. -- 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]

1 year, 11 months

Re: spanish localization

by Guillermo Hernandez (Oldno7)

On 11/2/21 20:15, Mark Sapiro wrote: > On 2/11/21 3:47 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> I contributed in january to translate to spanish all the items left in >> Mailman Core, Django-mailman, HyperKitty and Postorius via Weblate. I >> thought they will be used in the next upgrade, but I cannot see any >> improvement and there are many words untranslated. > > The Spanish translations for Mailman core and HyperKitty are currently > completely up to date with weblate. django-mailman3 differs in one > string that was translated on Feb 10 and hasn't yet been merged. > Postorius also differs in a few places from the Feb 10 version that > hasn't yet been merged. Ok. Thanks for checking it. I put my little contribution in Weblate and I like that it could be used by anyone. > Other than that, the translations should be good. > > >> Is there any way to upgrade the .po files in order to get the last >> translation? > > For the web UI you need to run the django management `compilemessages` > command. I tried to run this using the same command as I did for the "collectstatic" (that solved all my previous problems for the upgrade) and "migrate" runs but it shows me an error: su -m mailman3 -c "python3 manage.py compilemessages" CommandError: This script should be run from the Django Git checkout or your project or app tree, or with the settings module specified. if I try with --settings param (for I missunderstood the error message) it shows the same: su -m mailman3 -c "python3 manage.py compilemessages --settings settings" CommandError: This script should be run from the Django Git checkout or your project or app tree, or with the settings module specified. I tried to find any doc regarding the use of the "compilemessages" command but I couldn't As far as I can see (I runned it with -h parm) this had to be related to the main python module, but I cannot understand why the pip upgrade did not do the job. I'm lost. Can you, please, point me in the right direction? > For Mailman core you need to run > ``` > cd mailman/messages/es/LC_MESSAGES > msgfmt -o mailman.mo mailman.po > ``` > to compile the mailman.po file for gettext. >

4 years, 11 months

Mailman-users search results for query "Postorius"