Search results for "Postorius" - Mailman-users

Re: Assistance with mailman3

by Abhilash Raj

On Wed, Mar 13, 2019, at 8:47 AM, ayen(a)afilias.info wrote: > Hi all > > I'm pretty new to mailman but been trying to install mailman 3 and been > running into issues, following the documentation at > http://docs.mailman3.org/en/latest/prodsetup.html > installed Python 3.6, nginx, ruby-sass > then with pip installed whoosh mailman-hyperkitty postorius hyperkitty > mailman > > tried to start mailman core, symlinked master and runner -> /usr/bin/ > (otherwise it wouldn't run) > mailman core starts but when I hit the api url I get this in the logs > > File > "/usr/local/lib/python3.6/dist-packages/mailman-3.2.2-py3.6.egg/mailman/database/transaction.py", line 50, in wrapper > rtn = function(*args, **kws) > File > "/usr/local/lib/python3.6/dist-packages/mailman-3.2.2-py3.6.egg/mailman/rest/wsgiapp.py", line 218, in __call__ > return super().__call__(environ, start_response) > File "/usr/local/lib/python3.6/dist-packages/falcon/api.py", line > 248, in __call__ > responder, params, resource, req.uri_template = > self._get_responder(req) > File "/usr/local/lib/python3.6/dist-packages/falcon/api.py", line > 664, in _get_responder > route = self._router_search(path, req=req) > TypeError: find() got an unexpected keyword argument 'req' > Mar 13 10:54:44 2019 (17273) 127.0.0.1 - - "GET /3.1/ HTTP/1.1" 500 59 > > and on frontend "A server error occurred. Please contact the administrator." Inside your virtualenv, please run: $ pip install -U falcon==1.4.1 This should fix the above error. > > that leads to my gnu not working and throwing keyerrors for postorius. > > I'm using a clean install of ubuntu 18.04 but have also tried to > install on centos 7 with no success. > > Are there any missing dependencies or steps that I've missed any > assistance would be appreciated. > > Andy > _______________________________________________ > 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, 7 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)

7 years, 2 months

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Barry Warsaw

On May 12, 2016, at 12:18 PM, Mark Sapiro wrote: >It is the intent that Postorius will eventually expose all these >settings. We're not there yet. At present you could possibly do this by >interacting with mailmanclient, although I'm not certain the settings are >exposed there. I'm not sure if they're exposed in mailmanclient, but they are exposed in the core's REST API, on the member resource. It's the `delivery_mode` attribute and it takes as legal values one of 'regular', 'plaintext_digests', 'mime_digests', and 'summary_digests' (IOW, the enum item names for the DeliveryMode enum). Cheers, -Barry

10 years, 5 months

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Barry Warsaw

On May 13, 2016, at 10:11 PM, Mark Sapiro wrote: >However, please correct me if I'm wrong, but there does not appear to be >a way in Postorius to set a list's mime_is_default_digest attribute. I think that's a legacy attribute that should probably go away. It's only defined as a column in the database and set in the default style, but it's not defined in the IMailingList interface or actually *used* anywhere. Cheers, -Barry

10 years, 5 months

[MM3-users]Re: Request for assistance for fresh install of Mailman 3.0.3 and Python 3.4

by Mark Sapiro

On 05/28/2016 01:44 PM, Barry Warsaw wrote: > > Isn't mailman.client bilingual? It should work with Python 3.x and Python 2.y > for some versions of x and y. You are probably correct. It installs just fine with python3 setup.py install but both Hyperkitty and Postorius import it and they are Python 2, so I think with those pieces it needs to be Python 2. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 years, 5 months

Re: "Private archives" aren't private

by Simon Hanna

>> It's possible that you changed the archive_policy of a list and the >> change wasn't reflected in Hyperkitty. > Postorius is showing the list's settings as "Private archives" (see > screenshot). But apparently this setting doesn't do anything when > switching it to "public" and back to "private". It always returns '2L'. > Don't know if this is expected. Looks like you want to run the Hyperkitty management command "mailman_sync" You could also just grab the MailingList object you want and run "mlist_object.update_from_mailman()" on it. I couldn't get the command to run, will investigate later...

9 years, 5 months

MM3.1 templates

by Matt Richards

I've managed, to setup MM3.1 using the docker images from http://github.com/maxking/docker-mailman. I would like to start customizing the templates MM3.1 uses for the footer and confirmation emails. Is there any mailman site admin or list admin documentation on how to customize email templates in MM3.1? I've found this template doc at https://gitlab.com/mailman/mailman/tree/master/src/mailman/rest/docs, but I'm not clear how this works.. and it appears postorius doesn't have template support yet? I am new to python and django.. -- --Matt

9 years, 3 months

Re: "Private archives" aren't private

by cyp＠trojina.si

Hi, I'm having the same problem: changes to the "Archive policy" settings in postorius are not reflected in hyperkitty. Trying to use mailman_sync to fix this gave me the same BaseCommand traceback as above, but "mlist_object.update_from_mailman()" works. So luckily we have a workaround, thanks. But I suspect that there's some misconfiguration or permission problem on our server that's blocking the automatic synchronisation from taking place. Any advice to resolving this would be appreciated. :) Cheers, Cyprian

9 years, 3 months

Re: Typo in List Creation screen

by Abhilash Raj

On Thu, 10 Aug 2017 08:28:33 +0000 Henrik Rasmussen <her(a)adm.ku.dk> wrote: > There is a typo in the list creation screen in Mailman 3. The owner's address field says "Inital list owner address", which should be "Initial" with an extra 'i'. > Thanks for reporting. I have opened an issue at https://gitlab.com/mailman/postorius/issues/212 Please report the issues at our issue tracker[1]. [1]: https://gitlab.com/mailman/postorius/issues/ thanks, Abhilash Raj

9 years, 2 months

restrict sending to owner/moderator

by m.dohmen＠xconnect.de

Hello, I'd like to restrict message acceptance on a per-list basis to the owner or moderator, so that simple subscribers cannot send messages to the list. But I don't want the owner/moderator having to moderate own messages, so the member setting "hold for moderation" in Postorius isn't applicable. Is there a way to do this?

9 years, 1 month

Mailman-users search results for query "Postorius"