Search results for "Postorius" - Mailman-users

Re: accept mails from several Users, not list members beside members, howto

by Mark Sapiro

On 7/12/21 11:56 PM, Lars Schimmer wrote: > > Thank you. > I would have hoped for a extra input box to enter a list of ~100 email > addresses, but ok, lets do it this way. There is the legacy accept_these_nonmembers setting (exposed in Postorius since 1.3.3). This is designed to support the MM 2.1 setting which accepted regexps, but it also supports non-regexp addresses. Note that a match in one of *_these_nonmembers will override the moderation action for a non-member. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

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

by Abhilash Raj

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 This fishy, why do you have both uwsgi and "python manage.py runserver" running? You only need one of those, since they both do the exact same thing. Please remove whatever is running the "python manage.py runserver" part and only use uwsgi. On Thu, Sep 5, 2019, at 1:02 PM, Ugnius S wrote: > 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) >> >> -- thanks, Abhilash Raj (maxking)

6 years, 6 months

Re: Installing mailman 3

by Mark Sapiro

On 07/21/2017 04:57 PM, Rafael Mora wrote: > Should Sign Up ?? Log In?? Yes. > El vie., 21 jul. 2017 a las 18:56, Rafael Mora (<rafael.mora.guti(a)gmail.com>) > escribió: > >> Nice! Up and running! >> >> How do I start using mailman? what are the steps?? What do you want to do with Mailman? This is the key question. There is some list subscriber documentation at <http://docs.list.org/en/latest/userguide.html>. You can create domains and lists via Postorius or via the core's bin/mailman commands ('bin/mailman --help' for a list). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 7 months

Re: Where is postorius.wsgi?

by Peter Münster

On Fri, Jan 26 2018, Timm Stamer wrote: > I use https://gitlab.com/mailman/mailman-suite as WSGI backend for > httpd > > # git clone https://gitlab.com/mailman/mailman-suite.git > > You have to customize settings.py of mailman-suite before you can start > using it. Thanks. Unfortunately, it seems, that settings.py is not found: mod_wsgi (pid=22182): Target WSGI script '/srv/www/htdocs/ckc3r/mailman-suite/mailman-suite_project/wsgi.py' cannot be loaded as Python module. mod_wsgi (pid=22182): Exception occurred processing WSGI script '/srv/www/htdocs/ckc3r/mailman-suite/mailman-suite_project/wsgi.py'. Traceback (most recent call last): [...] File "/usr/lib64/python2.7/importlib/__init__.py", line 37, in import_module __import__(name) ImportError: No module named settings Any hints? TIA for your help, -- Peter

8 years, 1 month

Global ban using regex

by Henrik Rasmussen

Using some regex testers and generators like https://regex101.com and https://www.site24x7.com/tools/regex-parser.html, the regex (.*)(a)inker\.azerbaijan\.su seems to match EVERYTHING(a)inker.azerbaijan.su (EVERYTHING is constantly changing in current spam mails). However, entering the regex to the Global Ban Add ban /postorius/bans/ result in: `An error occurred: Invalid Parameter "email": Expected a valid email address or regular expression, got (.*)(a)inker\.azerbaijan\.su.'` Same result when using [Ban list] in postorius/lists/[LISTNAME]/bans/. Entering a none regex addresses like eknejfj(a)inker.azerbaijan.su works fine. Does Mailman use a different regex syntax I am using GNU Mailman 3.3.4 (Tom Sawyer) and Mailman Core Python Version 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0] (maxking/mailman-core:0.3 and maxking/mailman-web:0.3)

2 years, 8 months

Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius

by Simon Handfield

Hi, I have been working through other threads that indicate the same symptom (500 error when loading held_messages for a list). These include potential truncation of values in pendedkeyvalue table (don't this is our problem) and error when trying to access a message in /var/lib/mailman3/messages (ran the suggested code to loop through the stored files but no error was thrown.) Environment: Ubuntu 18.04 mailman3/bionic,now 3.1.1-9 all [installed,automatic] mailman3-full/bionic,now 3.1.1-9 all [installed] mailman3-web/bionic,now 0+20170523-14 all [installed,automatic] python-django-mailman3/bionic,now 1.1.0-4 all [installed,automatic] python-mailmanclient/bionic,now 3.1.1-5 all [installed,automatic] python3-mailman-hyperkitty/bionic,now 1.1.0-4 all [installed,automatic] Error reported in log with debug enabled: Traceback (most recent call last): File "/usr/lib/python3.6/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 214, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 215, in falcon.api.API.__call__ (falcon/api.c:2872) File "falcon/api.py", line 189, in falcon.api.API.__call__ (falcon/api.c:2419) File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 167, in on_get resource = self._make_collection(request) File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in _make_collection for resource in collection] File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in <listcomp> for resource in collection] File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 157, in _resource_as_dict resource = self._make_resource(request.id) File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 78, in _make_resource resource['msg'] = msg.as_string() File "/usr/lib/python3.6/email/message.py", line 158, in as_string g.flatten(self, unixfrom=unixfrom) File "/usr/lib/python3.6/email/generator.py", line 116, in flatten self._write(msg) File "/usr/lib/python3.6/email/generator.py", line 181, in _write self._dispatch(msg) File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch meth(msg) File "/usr/lib/python3.6/email/generator.py", line 272, in _handle_multipart g.flatten(part, unixfrom=False, linesep=self._NL) File "/usr/lib/python3.6/email/generator.py", line 116, in flatten self._write(msg) File "/usr/lib/python3.6/email/generator.py", line 181, in _write self._dispatch(msg) File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch meth(msg) File "/usr/lib/python3.6/email/generator.py", line 243, in _handle_text msg.set_payload(payload, charset) File "/usr/lib/python3.6/email/message.py", line 315, in set_payload payload = payload.encode(charset.output_charset) UnicodeEncodeError: 'ascii' codec can't encode characters in position 8-9: ordinal not in range(128) I'm sorry if this is a query that's answered already but I have not been able to find matching thread that seems to relate to my error. Thanks for any advice on where to look next. Cheers, Simon. _ [State Library of NSW]<https://www.sl.nsw.gov.au/> Simon Handfield Desktop and Infrastructure Leader simon.handfield(a)sl.nsw.gov.au<mailto:simon.handfield@sl.nsw.gov.au> +61 2 9273 1535 Macquarie Street, Sydney NSW 2000, Australia www.sl.nsw.gov.au<https://www.sl.nsw.gov.au/> This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of their organisation.

5 years, 6 months

Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by Mark Sapiro

David Newman wrote: > https://${domain}/mailman3/lists/${short_listname}.${domain}/ FYI, ${short_listname}.${domain} is the same as ${list_id} Also, ${domain} as the web site address may not be appropriate. For example, on this list $domain is `mailman3.org`, but the base URL for Postorius is `https://lists.mailman3.org/mailman3` and `https://mailman3.org/mailman3` doesn't work. There is no replacement for the web domain if it's different from the email domain for the same reason that there are no web URLs in the default templates. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

Re: Separating Lists by Domain

by Abhilash Raj

On Thu, Jan 3, 2019, at 2:27 PM, brian(a)emwd.com wrote: > So who manages Postorius? Is that a whole separate application from > Mailman 3? Is there a way we can get whoever the developer is to update > it where we can separate lists by domain the way Hyperkitty does? Mark > Sapiro refers to this in the following post: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… You can file an issue at https://gitlab.com/mailman/postorius/issues > Thanks, > Brian > _______________________________________________ > 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)

7 years, 2 months

Re: Where does sender postorius@ come from?

by Mark Sapiro

On 6/14/23 14:35, Jens Günther wrote: > Thanks for the hint. Unfortunately it's not working as expected. I'm > using the docker-setup and tried it in 2 different locations, but > neither got the expected effect: > > - I put the variable in the mm-web-container-environment: > mm-web: > environment: > - EMAIL_CONFIRMATION_FROM=myaddress(a)something.org That won't work > - Then I tried settings_local.py with: > EMAIL_CONFIRMATION_FROM = 'myaddress(a)something.org' That is the correct place. It should work. Did you restart the container after making this change? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

Re: Postorius: Show only own lists

by Thor Atle Rustad

2018-01-23 16:59 GMT+01:00 Terri Oda <terri(a)toybox.ca>: > > > On January 23, 2018 6:26:51 AM PST, Thor Atle Rustad < > thor.rustad(a)gmail.com> wrote: > >2018-01-23 14:37 GMT+01:00 Simon Hanna <simon(a)hannaweb.eu>: > > > >> On 01/23/2018 12:10 PM, Thor Atle Rustad wrote: > >> > >>> Imagine an installation with 500+ mailing lists and almost as many > >local > >>> admins that are supposed to maintain their own local lists with a > >few > >>> local > >>> members. As site admin, I see all 500+ lists, but I was expecting > >*local* > >>> admins to see only the lists they maintain. I have set all lists to > >>> "advertised = False", so they are hidden from ordinary view. Is > >there a > >>> way > >>> to show only relevant lists to local admins? > >I believe I wrote Postorius in the subject line, but it may not be so > >obvious. So yes, in Posterius I would like to hide the lists from email > >harvesters, while relatively "untrusted" admins should have access to > >basic > >operations on the one list he/she "owns" (and without having to browse > >through 50 pages of mailing lists). Somehow I don't think 500 > >superusers in > >our system is a good idea! > > What do you mean by local admins? > > Is this > 1. Giantsite.example.com hosts lists for a bunch of domains, and you want > the logged in admins of mydomain.com to see their list admin pages but > not otherdomain.org's lists > > 2. You want each logged in admin to have their own personal dashboard of > list admin pages for lists they administrate, even though they're all under > one big domain. > > (Neither of those scenarios talks about archives, since you say you're > only talking about postorious) > > I think #2 is something we should be doing, and the old "todo" section of > the interface kind of was made with that in mind. Probably worth mocking > up some screenshots and opening a feature request to keep the idea in mind, > but it should be more a matter of prioritizing how things are displayed > than any huge change. > > I'm not sure if we have a "local admin" concept in the system that lines > up with #1, though. > > Ok, this would more like number 2. It's National.dogclub.com with its various mailing lists like poodle.dogclub.com, which expands to poodle-regionA.dogclub.com, poodle-regionB.dogclub.com, poodle-regiionC.dogclub.com and so on. So with dozens of different dog breeds and geographic chapters, the number of mailing lists are between 500 and 1000, but all are under the same dogclub.com domain. The members of each list should be maintained by a person with some elevated rights, but not enough to mess up the system. What I called "local admin" should have rights to add and remove members of, say, the poodle-regionA mailing list.

8 years, 1 month

Mailman-users search results for query "Postorius"