Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Mass subscribe gives HTTP Error 500 when using custom template

by Jeffrey D

Mark Sapiro wrote: > On 1/28/20 6:15 AM, Jeffrey D wrote: > > What is your setting in settings(_local).py for > POSTORIUS_TEMPLATE_BASE_URL? It looks like you have the default > POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' > It should be the base URL for connecting to Postorius. I.e., if you > normally connect to Postorius via https://www.example.com/postorius, it > should be https://www.example.com Thanks, changing the POSTORIUS_TEMPLATE_BASE_URL fixing the issue.

6 years, 4 months

[MM3-users] Re: Your Dashboard

by Stephen J. Turnbull

Mark Sapiro writes: > There's no overall dashboard per se. The message actually refers to > whatever web UI you use to manage the list. The default template > for this message is non-specific because it comes from Mailman > core, and core doesn't know if you are using Postorius or some > other web management system or non at all, and even if it were to > assume Postorius, it doesn't know the URL. IMO, we should fix this, similar to the way we deal with archives (provide a callback API so the webmin(s) can tell us where it is (they are)). WDYT? Steve

6 years, 3 months

[MM3-users] Re: Uncaught runner exception

by Stephen J. Turnbull

Mark Sapiro writes: > Whether this is something you did wrong s/wrong/accidentally/ :-) > or an issue with whatever init/systemd scripts run these things, I > can't say. Maybe there's a way we can check the account running mailman, sort of a runtime check_perms. I doubt suid is a good idea, but maybe a warning? Steve

6 years, 1 month

[MM3-users] Re: Different Mail Domain Cause Key Error

by Brian Carpenter

On 4/21/20 4:53 PM, Mark Sapiro wrote: > The issue is the FILTER_VHOST = True setting is broken. Thanks Mark. I was wondering how this would turn out using the FILTER_VHOST setting. Unfortunately we have to have this setting turned on. Maybe I can get the client to agree to use the web domain as part of their list address. Appreciate your help as always! Stay healthy. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

6 years, 1 month

[MM3-users] Re: Can't open PID file after start.

by Torge Riedel

Am 22.04.20 um 17:13 schrieb Mark Sapiro: > It's normal and just info. The key is "yet?" The [Service] section in > Mailman's systemd service file references /opt/mailman/var/master.pid as > PIDFile and systemd looks for it before Mailman has created it. Hi Mark, thanks for your answer. Best Torge

6 years, 1 month

[MM3-users] Re: FILTER_VHOST fix - was: Postorius & multi domain

by Gilles Filippini

Mark Sapiro a écrit le 23/04/2020 à 20:02 : > On 4/23/20 10:27 AM, Gilles Filippini wrote: >> >> You'll have also to remove the compiled files from the __pycache__ >> directory: > > > This is not necessary. If the .py file is newer than the .pyc file in > the __pycache__ directory, the interpreter will use the .py file and if > it has permission will rewrite the .pyc file. Indeed, if it has permission. When testing in user space it does not have permission. These files are owned by root. _g.

6 years, 1 month

[MM3-users] Re: mailman3 vs postfix

by Ralf Wiegand

(venv-3.6) [root@empire mailman]# django-admin createsuperuser No Django settings specified. Unknown command: 'createsuperuser' Type 'django-admin help' for usage. (venv-3.6) [root@empire mailman]# django-admin help Type 'django-admin help <subcommand>' for help on a specific subcommand. Available subcommands: [django] check compilemessages createcachetable dbshell diffsettings dumpdata flush inspectdb loaddata makemessages makemigrations migrate runserver sendtestemail shell showmigrations sqlflush sqlmigrate sqlsequencereset squashmigrations startapp startproject test testserver Note that only Django core commands are listed as settings are not properly configured (error: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.). On 4/28/20 3:35 PM, Mark Sapiro wrote: > django-admin createsuperuser

6 years, 1 month

[MM3-users] Re: mailman3 vs postfix

by Ralf Wiegand

Good morning mark, still not working. Not sure what the issue is. (venv-3.6) [root@empire mailman-suite_project]# django-admin --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --setting settings createsuperuser No Django settings specified. Unknown command: '--pythonpath' Type 'django-admin help' for usage. (venv-3.6) [root@empire mailman-suite_project]# Ralf On 4/28/20 4:23 PM, Mark Sapiro wrote: > On 4/28/20 1:18 PM, Ralf Wiegand wrote: >> Mark - I have a hard time following this. >> >> /path/to/where/your/settings/are located >> >> what settings? what do I am looking for? > Based on the traceback from another post: > > --pythonpath /opt/mailman/mailman-suite/mailman-suite_project > --settings settings.py >

6 years, 1 month

[MM3-users] Re: mailman3 vs postfix

by Ralf Wiegand

hey Mark, that worked. Thank YOU. Got one step ahead. So after creating a admin account and logging in via the GUI, I get this error message: IntegrityError at /accounts/login/ UNIQUE constraint failed: account_emailaddress.email Request Method: POST Request URL: http://192.168.0.27:8000/accounts/login/ Django Version: 2.2.12 Exception Type: IntegrityError Exception Value: UNIQUE constraint failed: account_emailaddress.email Exception Location: /opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/backends/sqlite3/base.py in execute, line 383 Python Executable: /opt/mailman/venv-3.6/bin/python Python Version: 3.6.8 What does this mean? Thx, ralf On 4/29/20 10:19 AM, Mark Sapiro wrote: > django-admin createsuperuser \ > --pythonpath /opt/mailman/mailman-suite/mailman-suite_project \ > --settings settings

6 years, 1 month

[MM3-users] Re: Installation Wooes

by Andrew Hodgson

Mark Sapiro <mark(a)msapiro.net> wrote: >On 5/2/20 12:51 AM, Samir Faci wrote: >> A few questions about an Ubuntu install. >> >> i'm getting this behavior: >> AttributeError: module 'time' has no attribute 'clock' >> I'm on python 3.8.2 >It time.clock() went away in Python 3.8. Mailman versions older than >3.3.0 are not compatible with Python 3.8. You need to upgrade Mailman core. I think this is a bug in Ubuntu 20.04. Python3 package is: Python3 3.8.2-0ubuntu2 https://packages.ubuntu.com/search?suite=focal&keywords=python3 Mailman3 is: 3.2.2-1 https://packages.ubuntu.com/search?suite=focal&keywords=mailman3 Andrew.

6 years

Search results for query "sapiro"