Search results for "Postorius" - Mailman-users

Re: global preferences

by Mark Sapiro

Again, please don't hijack threads. Post a new topic by composing a new message to mailman-users(a)mailman3.org, not as a reply to another list message. On 5/3/23 07:59, Christian via Mailman-users wrote: > Are checks and changes to global preferences for all lists to be made via a GUI or is it editing settings.py directly please? Thank you! You can set your global preferences via Postorius (select Mailman settings from the drop-down at the right of the top nav bar). These are the settings for the user that will apply if there is no applicable list-based or address-based setting. They are specific to the user. The defaults for these are defined in mailman/core/constants.py. They are Mailman core settings and have nothing to do with Django's settings.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

Re: New Mailman Releases

by Odhiambo Washington

On Wed, Oct 26, 2022 at 8:44 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: > Hi, > > I am pleased to announce several new releases for GNU Mailman project. > > 1. Mailman Core 3.3.6 [1] > 2. Postorius 1.3.7 [2] > 3. Hyperkitty 1.3.6 [3] > 4. Mailmanclient 3.3.4 [4] > 5. Django-mailman3 1.3.8 [5] > > All the releases are published to PyPI and you can find links to all the > PyPI projects: > > https://docs.mailman3.org/en/latest/ > > A full list of changelogs are available below: > > [1]: > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… > [2]: > https://docs.mailman3.org/projects/postorius/en/latest/news.html#section-2 > -- Something weird is going on with the page missing the bullets. > [3]: > > https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-6 > [4]: > > https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… > [5]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > > > Finally, the minimum Python version required is 3.7 although, 3.9 is > recommended if you are doing a new install for longest support. 3.10 is > supported for Django apps, but Mailman Core is missing that due to one > of the core dependencies not support 3.10 yet (aiosmtpd). > Hello @Abhilash Raj <maxking(a)asynchronous.in> Thank you and the whole MM3 team for all the free work you do to make us have mailing lists :) I have a question regarding the Python version. I have a very recent installation of MM3, via the Virtual Environment method, running smoothly - so far. The Python version that got installed is 3.10.6 wash@lists:~$ sudo su - mailman (venv) mailman@lists:~$ which python /opt/mailman/mm/venv/bin/python (venv) mailman@lists:~$ /opt/mailman/mm/venv/bin/python -V Python 3.10.6 (venv) mailman@lists:~$ mailma mailmail3 mailman (venv) mailman@lists:~$ mailman --version GNU Mailman 3.3.5 (Tom Sawyer) (venv) mailman@lists:~$ 1. What does the incompatibility with Python-3.10 portend for my setup and anyone else with Python-3.10? 2. Is it possible to downgrade the Python in a Venv down to 3.9 without breaking the installation? And finally, is there documentation/procedure to upgrade a VENV install in this case? Thank you in advance. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 7 months

Re: opt in/out for hidden lists

by Abhilash Raj

On Mon, Jul 1, 2019, at 4:04 AM, mailman3(a)malevil.cc wrote: > Is it possible to change the default value for list visibility? > Sometime when my list admins create a new list they forget to check > that they should be hidden, I think that should be the default value > anyway because its a potentially security issue when a list is unwanted > visible... It is not yet respected by Postorius, which chooses the first option in the list as the default one, but you can set the default-style in Core. If you want to help fix this, there is an open issue[1] about it on the bug tracker. [1]: https://gitlab.com/mailman/postorius/issues/310 > _______________________________________________ > 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, 11 months

Docker mailman3 delete social logins, did something change?

by bob B

I want to remove the social logins from mailman3 in docker. I found this info https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… but the link to the default shows *************** INSTALLED_APPS = [] DEFAULT_APPS = [ 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', ] ***************** However when I go to the bug https://github.com/maxking/docker-mailman/issues/283 it shows ********* INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'paintstore', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora', 'allauth.socialaccount.providers.openid', 'allauth.socialaccount.providers.github', 'allauth.socialaccount.providers.gitlab', 'allauth.socialaccount.providers.google', ) ******** The two examples are different so what should it be? I tried to add it in both ways and when I do I get bad gateway and he mailman website is broke. I have not setup any domains yet, just setup the admin password,. For example this breaks my website cat /opt/mailman/web/settings_local.py ALLOWED_HOSTS = ['127.0.0.1','localhost','REDACTED','REDACTED','REDACTED','REDACTED','REDACTED'] #ALLOWED_HOSTS = ['*'] DEBUG = True #DEBUG = False EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'REDACTED' EMAIL_PORT = 25 INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'paintstore', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora', 'allauth.socialaccount.providers.openid', 'allauth.socialaccount.providers.github', 'allauth.socialaccount.providers.gitlab', 'allauth.socialaccount.providers.google', ) ************************************************************************* And I have even removed anything? What should my /opt/mailman/web/settings_local.py look like?

3 years, 9 months

Re: Configure administrative users via command line?

by kjohnson＠eclypse.org

Thank you for the prompt and informative reply. Mark Sapiro wrote: > ... If you are an owner or moderator of a list > or a superuser, you can handle moderation requests via Postorius. If you > are a list owner or a superuser, you can manage owners and moderators > via Postorius. Yes, I would like to do that. > You can add superusers via the command line django admin > createsuperuser command. For the reference of others like me, createsuperuser will allow you to create a user with a non-unique email address. I strongly recommend against that. mailman shell gave me: >>> from django.contrib.auth.models import User >>> User.objects.filter(is_superuser=True) <QuerySet [<User: admin>, <User: xxxx>]> I dredged a password for admin out of my memory and was able to perform the moderation request. I also set a new list owner.

1 year, 11 months

Re: Postorius no connection to REST API

by Richard Rosner

Mark Sapiro wrote: > > You are in a better position to answer that than am I. > What does sudo netstat -lntp show? A lot. But since most of that isn't relevant here: Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:465 0.0.0.0:* LISTEN 20241/master tcp 0 0 127.0.0.1:8024 0.0.0.0:* LISTEN 14076/python3 tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 20241/master tcp 0 0 127.0.0.1:8001 0.0.0.0:* LISTEN 14080/python3 tcp 0 0 0.0.0.0:587 0.0.0.0:* LISTEN 20241/master tcp6 0 0 :::80 :::* LISTEN 13882/apache2 tcp6 0 0 :::465 :::* LISTEN 20241/master tcp6 0 0 :::25 :::* LISTEN 20241/master tcp6 0 0 :::443 :::* LISTEN 13882/apache2 tcp6 0 0 :::587 :::* LISTEN 20241/master > What does ps -fwwa|grep rest show? root 15055 14843 0 12:58 pts/1 00:00:00 grep rest So whatever it's supposed to find, it's not there > > mailman3-web.service must also run as list. I changed that. It didn't like it. systemctl status mailman3-web.service ● mailman3-web.service - Mailman3-web uWSGI service Loaded: loaded (/lib/systemd/system/mailman3-web.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2021-08-11 13:05:39 CEST; 32s ago Docs: file:///usr/share/doc/mailman3-web/README.rst Process: 15570 ExecStart=/usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini (code=exited, status=1/FAILURE) Main PID: 15570 (code=exited, status=1/FAILURE) Status: "initializing uWSGI" Aug 11 13:05:39 mail systemd[1]: Starting Mailman3-web uWSGI service... Aug 11 13:05:39 mail systemd[1]: mailman3-web.service: Main process exited, code=exited, status=1/FAILURE Aug 11 13:05:39 mail systemd[1]: mailman3-web.service: Failed with result 'exit-code'. Aug 11 13:05:39 mail systemd[1]: Failed to start Mailman3-web uWSGI service. Aug 11 13:05:39 mail systemd[1]: mailman3-web.service: Service RestartSec=100ms expired, scheduling restart. Aug 11 13:05:39 mail systemd[1]: mailman3-web.service: Scheduled restart job, restart counter is at 5. Aug 11 13:05:39 mail systemd[1]: Stopped Mailman3-web uWSGI service. Aug 11 13:05:39 mail systemd[1]: mailman3-web.service: Start request repeated too quickly. Aug 11 13:05:39 mail systemd[1]: mailman3-web.service: Failed with result 'exit-code'. Aug 11 13:05:39 mail systemd[1]: Failed to start Mailman3-web uWSGI service. > > So, what do you have in your apache config for proxying to uwsgi and > what's your uwsgi configuration. lists-ssl.conf: <VirtualHost *:443> ServerAdmin admin(a)domain.de ServerName lists.domain.de Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /mailman3/static /var/lib/mailman3/web/static <Directory "/var/lib/mailman3/web/static"> Require all granted </Directory> <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass "/mailman3" "unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost:8001/" </IfModule> # SSL Engine Switch: # Enable/Disable SSL for this virtual host. SSLEngine on SSLCertificateFile /etc/ssl/certs/lists.domain.de.cert.pem SSLCertificateKeyFile /etc/ssl/private/lists.domain.de.private.pem SSLCertificateChainFile /etc/ssl/certs/dfnca.pem SSLCACertificateFile /etc/ssl/certs/rwthcert.pem SSLProtocol all -SSLv3 -TLSv1 -TLSv1.1 Protocols h2 http/1.1 SSLCipherSuite ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256 SSLHonorCipherOrder off #RewriteEngine on #RewriteRule ^/$ https://lists.domain.de/listinfo Header always set Strict-Transport-Security "max-age=15768000; includeSubDomains; preload" Header always set X-Frame-Options: "SAMEORIGIN" Header always set X-Xss-Protection "1; mode=block" Header always set X-Content-Type-Options "nosniff" Header always set Content-Security-Policy "default-src 'self' *.domain.de; script-src 'self' *.domain.de; connect-src 'self' *.domain.de; img-src 'self' *.domain.de; style-src 'self' 'unsafe-inline' *.domain.de; object-src 'self' *.domain.de; frame-src 'self' *.domain.de;" Header always set Referrer-Policy "no-referrer-when-downgrade" </VirtualHost> <VirtualHost *:80> RewriteEngine On RewriteRule ^(.*)$ https://%{HTTP_HOST}$1 [R=301,L] </VirtualHost> I guess with uwsgi config you mean the /etc/mailman3/uwsgi.ini file? [uwsgi] # Port on which uwsgi will be listening. uwsgi-socket = /run/mailman3-web/uwsgi.sock #Enable threading for python enable-threads = true # Move to the directory wher the django files are. chdir = /usr/share/mailman3-web # Use the wsgi file provided with the django project. wsgi-file = wsgi.py # Setup default number of processes and threads per process. master = true process = 2 threads = 2 # Drop privielges and don't run as root. uid = www-data gid = www-data plugins = python3 # Setup the django_q related worker processes. attach-daemon = python3 manage.py qcluster # Setup hyperkitty's cron jobs. #unique-cron = -1 -1 -1 -1 -1 ./manage.py runjobs minutely #unique-cron = -15 -1 -1 -1 -1 ./manage.py runjobs quarter_hourly #unique-cron = 0 -1 -1 -1 -1 ./manage.py runjobs hourly #unique-cron = 0 0 -1 -1 -1 ./manage.py runjobs daily #unique-cron = 0 0 1 -1 -1 ./manage.py runjobs monthly #unique-cron = 0 0 -1 -1 0 ./manage.py runjobs weekly #unique-cron = 0 0 1 1 -1 ./manage.py runjobs yearly # Setup the request log. #req-logger = file:/var/log/mailman3/web/mailman-web.log # Log cron seperately. #logger = cron file:/var/log/mailman3/web/mailman-web-cron.log #log-route = cron uwsgi-cron # Log qcluster commands seperately. #logger = qcluster file:/var/log/mailman3/web/mailman-web-qcluster.log #log-route = qcluster uwsgi-daemons # Last log and it logs the rest of the stuff. #logger = file:/var/log/mailman3/web/mailman-web-error.log logto = /var/log/mailman3/web/mailman-web.log

3 years, 10 months

Re: Auto discard after max_days_to_hold not working.

by Mark Sapiro

On 4/28/25 07:59, Stephen J. Turnbull wrote: > > This doesn't seem to be exposed in Postorius. It's not all that old > in Mailman 3 (April 2020) so it's possible that it is not moved from > Mailman 2 to Mailman 3 by the migration scripts. This is comments in postorius/forms/list_forms.py ``` # TODO: Expose after this functionality actually works in Core. # max_days_to_hold = forms.IntegerField( # min_value=0, # label=_('Discard held posts after'), # required=False, # help_text=_( # 'No. of days after which held messages will be automatically' # ' discarded.')) ``` `mailman import21` will import the setting, but per the above comment, it doesn't yet work. The setting exists and is exposed in REST, but it appears it is not actually implemented. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 3 weeks

Re: remove website example.com via django interface

by Alexander Inzinger-Zrock

Am 26.03.25 um 16:23 schrieb Odhiambo Washington: > > > On Wed, Mar 26, 2025 at 6:09 PM Alexander Inzinger-Zrock via > Mailman-users <mailman-users(a)mailman3.org > <mailto:mailman-users@mailman3.org>> wrote: > > remove website 'example.com <http://example.com>' via django interface > or > "how to rush jourself off your feet" > > > **Disclaimer: don't try this at home** > > > in believe to replace the display of 'example.com > <http://example.com>' in the > postorius-webinterface i logged into django-interface, under 'website' > (very bottom of the left menu) i added my new website and then deleted > 'example.com <http://example.com>'. > > Result: i can't access my webinterfaces any more, neither django nor > postorius. > > > Questions: > > 1. Does somebody know about the correct approach to change the > displayed > url in the postorius-webinterface? > > > The displayed URL should be the one you configured in Nginx or Apache. > example.com <http://example.com> is usually SITE_ID=1. > It's possible to rename it in Django admin UI to whatever you want - > like mywebsite.name <http://mywebsite.name> > > 2. does somebody perhaps know how to revert those removal via CLI or > other ways? > > > ``` > SQL: select * from django_site; > ``` > Whatever ID shows for the one you created, stick that ID to settings.py > and restart mailmanweb. works again. Thank you so much. for anyone stumbling accross, 1. setting in settings.py is: #: Current Django Site being served. This is used to customize the web host #: being used to serve the current website. For more details about Django #: site, see: https://docs.djangoproject.com/en/dev/ref/contrib/sites/ SITE_ID = 2. and correct database would be 'mailmanweb' (according to manual). greetings, aiz > > -- > 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 > <http://www.catb.org/~esr/faqs/smart-questions.html>]

2 months, 3 weeks

Re: File "/usr/lib/python2.7/httplib.py", line 1148, in getresponse raise ResponseNotReady()

by Mark Sapiro

On 9/21/20 6:21 AM, r.woithe(a)callassoftware.com wrote: > Hello, > Version: > Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) > Mailman Core API Version 3.0 > Mailman Core Python Version 3.8.2 (default, Jul 16 2020, 14:00:26) [GCC 9.3.0] > > But the Error was there allready before the update have been done. That means the Mailman-Core changed but the error persisted. What is the full traceback from this error? Mailman 3 has not supported Python 2 since 3.0 beta4. It is not clear what is invoking /usr/lib/python2.7/httplib.py, but if it is Mailman core, something is seriously amiss in the way it's installed. Even Postorius and HyperKitty have not supported Python 2 for quit some time. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

Re: Newbie question 2: Rewriting issue for bounced emails

by Mark Sapiro

On 12/26/21 6:05 PM, William Oliver wrote: > > So.. if I need to do it myself, can you point me to what file I need to > create/modify in the /opt/mailman/mm tree to set up the alias? Assuming you have Postorius working, just go to the Domains view, edit your domain and add an Alias Domain. Otherwise, you can do this in mailman shell, e.g. ``` $ mailman shell 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. >>> dm = getUtility(IDomainManager) >>> d = dm.get('example.com') >>> d.alias_domain = x.example.com >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

Mailman-users search results for query "Postorius"