Search results for "Postorius" - Mailman-users

Re: Splitting hosts: mta&core vs postorius

by samuel.d.darwin＠gmail.com

To add some context, we had intended to split up mailman-core and mailman-web on separate machines. With such a configuration mailman-core should definitely listen on the public IP or 0.0.0.0. At the same time, this configuration is a standard way to provision servers "in general": /etc/hosts: 127.0.1.1 server1.example.com server1 There are multiple articles about the topic if you google "127.0.1.1". This technique allows a server's name to always be resolvable locally, it's always correct and doesn't need to be updated if the external IP address changes, it is robust to complexities about NAT or proxies. This allows an application on server to resolve its own hostname consistently. At the same time, a remote client would use traditional DNS, discover an IP (not "127.0.1.1"), and connect to the server remotely. Otherwise, every time the server's IP changes, you need take the extra step of modifying /etc/hosts. With server automation you'd need to discover the correct IP first. So, adding a "listen" or "bind_to" field is a "bug report/request for enhancement". It would be helpful in allowing mailman-core and mailman-web to run on separate machines. However our latest plan as of this moment is to revert back to a one-server implementation. mailman-core and mailman-web will be on the same machine. Thus, the enhancement is not critical. It still seems "theoretically" useful to implement the fix, unless the documentation states "it is recommended that core and web should be on the same machine" or similar.

2 years, 2 months

Re: Core, Hyperkitty and Postorius releases

by Abhilash Raj

On Fri, May 14, 2021, at 2:16 PM, Odhiambo Washington wrote: > On Sat, May 15, 2021 at 12:01 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > > On 5/14/21 1:54 PM, Odhiambo Washington wrote: > > > > > > /usr/local/include/sass > > > > > > That is the only thing found that is in the base system. > > > > And that's the one you want. What is it's mode? > > > > root@gw:/usr/home/wash # ls -al /usr/local/include/sass > total 104 > drwxr-xr-x 2 root wheel 512 Apr 16 16:49 . > drwxr-xr-x 176 root wheel 10240 Apr 19 18:05 .. > -rw-r--r-- 1 root wheel 2369 Apr 8 11:08 base.h > -rw-r--r-- 1 root wheel 10742 Apr 8 11:08 context.h > -rw-r--r-- 1 root wheel 6632 Apr 8 11:08 functions.h > -rw-r--r-- 1 root wheel 6489 Apr 8 11:08 values.h > -rw-r--r-- 1 root wheel 198 Apr 8 11:08 version.h > > I imagined I needed an executable. This sounds like a result of you running `pip3 install sass`, probably with sudo which failed mid-way due to the exception you posted above. Which OS are you using? On debian/ubuntu, you can install: sudo apt install sassc I am not exactly sure how it got removed during your upgrade to the new version of Mailman since it shouldn't affect your system packages. Did you install Mailman initially using system packages or instructions provided at [1]? [1]: https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… -- thanks, Abhilash Raj (maxking)

4 years, 11 months

Re: Using REST with CLI using curl .... help needed

by Stephen J. Turnbull

Michael Bakonyi writes: > allright, thx a lot for your quick answer! After fiddling around > some more time, I guess I had some misunderstandings regarding the > REST-API. I guess if we reach the API correctly, we will not be > confronted with the CSRF-Error. We will continue to try but > nevertheless: What would be a cleaner approach to reach the API > from an external IP? I didn't found any examples in the web so far. If you mean the core REST API, you won't find any useful examples on the Internet. Anything you do find should be considered a form of self-harm and/or an insider threat. Access to the REST API is not securely authenticated, and therefore should never be exposed to the Internet. This API is expected to be contained either to localhost, or to a subnet behind a firewall that prohibits access to that port except from the host(s) serving HyperKitty and/or Postorius. If that's what you're trying to do, I would suggest a secure tunnel (not a generic VPN, but a specific tunnel to the API port). If you're talking about the Django administrative API to Postorius, you'll probably get a better answer faster from Django channels. Mark may know but he won't be available until mid-September most likely. As I wrote earlier, as far as I know you need to access the Postorius port, provide credentials, get the CSRF token, and then access Django. Regards, Steve

3 years, 7 months

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. >

3 years, 1 month

Re: Accept these non-members

by Mark Sapiro

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? 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. 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. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 1 week

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, 3 months

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, 3 months

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, 2 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, 7 months

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, 9 months

Mailman-users search results for query "Postorius"