Search results for "Postorius" - Mailman-users

Re: starting gunicorn per mailman.log yet gunicorn not installed

by Stephen J. Turnbull

Ken Alker writes: > I should have mentioned that I was installing "from source" in the > virtual environment (although it still seems to be package > management but just Python based instead of OS based as I'm not > compiling anything). Would your answer still apply in this > situation? Yes, it does. The list of dependent packages is in mailman/setup.py. Instead of downloading from a distro package repository, the packages are downloaded in the form of "wheels" from pypi.org (the Python Package Index). In mailmanweb, Postorius, HyperKitty, and django_mailman3 I believe the list is in requirements.txt. Distros almost never mess with these dependencies, with the single exception of gunicorn for the mailmanweb WSGI server. Distro-defined dependencies are primarily the external webserver (eg. Apache, nginx), the MTA (eg, Postfix, Exim4, Sendmail, qmail), and the relational database management system (eg, PostgreSQL, MySQL). Alternatives to gunicorn include uwsgi for nginx and Apache, and mod_wsgi for Apache. Steve

2 years, 1 month

SOLVED (was: compress failed...)

by Guillermo Hernandez (Oldno7)

El 30/10/22 a las 12:22, Guillermo Hernandez (Oldno7) via Mailman-users escribió: > > El 28/10/22 a las 9:18, Guillermo Hernandez (Oldno7) via Mailman-users > escribió: >> >> El 27/10/22 a las 21:39, Mark Sapiro escribió: >>>> After that the compress part showed errors... but the postorius web >>>> maintenance was working well except for the CSRF error >>>> verification. I will trace the compress errors and will try to find >>>> the problem later. >>> >>> >>> Do you have `COMPRESS_ENABLED = True` in your settings? If that's >>> not the issue, it may be in the settings for COMPRESS_PRECOMPILERS >> >> While I'm tracing the problem out, this is the configuration I had >> working and the error it shows after upgrade: >> >> <------- snip of settings.py> >> >> # >> COMPRESS_PRECOMPILERS = ( >> ('text/less', 'lessc {infile} {outfile}'), >> ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), >> ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), >> ) >> # On a production setup, setting COMPRESS_OFFLINE to True will bring a >> # significant performance improvement, as CSS files will not need to be >> # recompiled on each requests. It means running an additional "compress" >> # management command after each code upgrade. >> # >> http://django-compressor.readthedocs.io/en/latest/usage/#offline-compression >> #### activo compresion 18/12/20 >> COMPRESS_OFFLINE = True >> ###COMPRESS_OFFLINE = False >> <---------- end snip> >> >> And below is the error it shows: >> >> /usr/local/mailman3 # su -m mailman3 -c "python3 manage.py compress" >> Traceback (most recent call last): >> File "/usr/local/mailman3/manage.py", line 10, in <module> >> execute_from_command_line(sys.argv) >> File >> "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", >> line 446, in execute_from_command_line >> utility.execute() >> File >> "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", >> line 440, in execute >> self.fetch_command(subcommand).run_from_argv(self.argv) >> File >> "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", >> line 279, in fetch_command >> klass = load_command_class(app_name, subcommand) >> File >> "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", >> line 49, in load_command_class >> return module.Command() >> File >> "/usr/local/lib/python3.9/site-packages/django/core/management/base.py", >> line 274, in __init__ >> raise TypeError("requires_system_checks must be a list or tuple.") >> TypeError: requires_system_checks must be a list or tuple. >> >> > After searching around, I've got a hint of what can be happening. It > seems a variable has changed in Django 4.1 its nature from boolean to > a tuple > > https://github.com/painless-software/django-probes/issues/24 > > I've upgraded another server with mailman3 lists, with the same config > listed above, and it shows the same error in the "compress" part. I'm > not sure where to set the requires_system_checks variable as in one of > the comments of the link, and as it doesn't seems to break anything > more, I will wait for more info before trying to avoid it. I'm sure it > will have some repercusion on the performance, but I'll have to live > with it. > > > Thanks again for your supporting advices. I did a pip install --upgrade --force-reinstall Django==4.0.8 downgrading Django from 4.1 and now a su -m mailman3 -c "python3 manage.py compress" worked without pain. > >> >> >> >> >> -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 9 months

Re: Upgrading packages

by Eggert Ehmke

Am Donnerstag, 13. Oktober 2022, 19:09:20 CEST schrieb Mark Sapiro: > On 10/13/22 03:49, Eggert Ehmke wrote: > > pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master > > > > I noticed that mistune-2.0.0rc1 was upgraded to mistune-2.0.4. > > > > All packages were upgraded fine. I applied the patch to > > venv/lib/python3.9/site-packages/hyperkitty/lib/renderer.py > > It shouldn't have been necessary to apply any patch. The head of the > GitLab hyperkitty master branch is already compatible with mistune 2.0.4 strange, I still had the line with the (not working) from mistune.scanner import escape_html, escape_url maybe because the migration step was not working at that time? > I'm guessing at some point you installed something which required you to > manually make this migration and that produced this conflict. Do you > have both 0017_alter_emailtemplate_language.py and > 0017_auto_20220628_1132 in your postorius/migrations/ directory? If so, > probably just removing 0017_auto_20220628_1132 will fix this? That's what I did in the meantime, and it works now! Thank you.

2 years, 9 months

Re: Hyperkitty messages stuck in spool

by Ruth Ivimey-Cook

There may be some benefit in exploring these notes on configuring the linux memory managers: https://gist.github.com/JPvRiel/bcc5b20aac0c9cce6eefa6b88c125e03 My thought in suggesting this is that if you can put some back pressure on the processes running, to indicate that memory is indeed at a premium, you may be able to extract more from the hardware you have. For example, use 'ulimit' to prevent specific processes seeing all the memory they would otherwise see. In any case, to address the last point Mark makes, I would suggest adding quite limited amount of swap - perhaps 200-300MB, rather than 1-2GB, for the same reason. You give the kernel somewhere to put things at need without giving it the scope to go crazy! Finally, I would suggest going through the installation and remove everything you can manage that's not critical to running the mailing list. For example, mysql often runs many threads with lots of buffers, and on my MM install its virtual memory size (number of bytes it theoretically could use) is just under 3GB. It's 'resident' size (the amount it's actually using now) is however just 139MB, with another 2.3GB shared (with other processes on the system -- think c-lib, tls etc). Tuning mysql to a smaller memory footprint would probably result in several hundred MB lower use. Similarly, the same VM is running 'snapd', which claims a virtual size of 1.2GB and a resident size of 32K; perhaps it's not necessary to run snapd permanently or even have it installed? It's also using 'lxcfs' the linux containers framework, which while using very little resident is still claiming 290MB virtual space. My point is that all these virtual allocations add up, and while the kernel will overcommit (to account for memory requested but never used) and it tries hard, it cannot know which things to prioritise. Making some of the choices for it can only help. -- FWIW, my mail server VM is set up with 4 virtual CPUs, 5GB RAM (of which about 1.7G is actively used and the rest is file block buffer, some of which will be for shared code files) and 4GB swap (of which it's using 260K). It's running a fairly default setup of mariadb, dovecot, mailman3, exim4, fail2ban, and spamassassin, and is quite stable. NB I don't run postorius or django on this server... they're elsewhere. I do recall adding more RAM a while back, having initially allocated 2GB, and at the same time adding the swap space; it looks from these numbers the swap isn't needed and I could if I wanted have just given it 3GB rather than 5GB RAM (but the server has 64GB and I'm not bothered!). HTH, Ruth On 19/11/2021 16:20, Mark Dadgar wrote: > On Nov 19, 2021, at 5:47 AM, Andrew Hodgson <andrew(a)hodgson.io> wrote: >> Thanks for this it was due to changing cloud providers. My old provider I installed Debian from an ISO file which created the swap partition but on the new provider I used their cloud image with no swap. Swap now created and everything is back to normal. Its running on an instance with 2GB of RAM and based on how I am seeing the usage running I would see this as an absolute minimum for a standard Mailman 3 stack. > > I had this same experience on Digital Ocean. The short-term fix was enabling swap and the long-term fix was upping my service level to something with more memory. Without swap, I don’t think 2GB is realistically sufficient to run a full mm3 instance. > > The cloud providers really don’t like you to run swap because it hammers their SSDs. > > - Mark > ----- > mark(a)pdc-racing.net | 408-348-2878 > > > -- > Software Manager & Engineer > Tel: 01223 414180 > Blog: http://www.ivimey.org/blog > LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

3 years, 8 months

Re: Invalid FilterAction: discard. Treating as discard

by Mark Sapiro

On 6/6/19 6:02 AM, Henrik Rasmussen wrote: > > Still, attachments (PDF) is removed by Mailman. I as the list admin to send a new mail, but hold it back, to see what type it is. You have to add the MIME types for the attachments you want kept the the list's pass_types. You need to do this via mailman shell or REST as it isn't currently exposed in Postorius. Here's an example from a list that wants to accept PDFs as well as word processing and spreadsheet documents. Note that nappdf and x-pdf are uncommon PDF subtypes that I have seen. ['multipart', 'message/rfc822', 'text/plain', 'text/html', 'application/pdf', 'application/nappdf', 'application/x-pdf', 'application/rtf', 'application/vnd.oasis.opendocument.spreadsheet', 'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet', 'application/vnd.ms-excel', 'application/vnd.oasis.opendocument.text', 'application/vnd.openxmlformats-officedocument.wordprocessingml.document', 'application/msword' ] -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

Re: Installing mailman 3

by Rafael Mora

Hello Abhilash, I have this in my settings.py file: EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 #EMAIL_HOST_USER = 'mailing(a)labbrands.com' #EMAIL_HOST_PASSWORD = '******' What should I use in user and password?? Does Django use postfix to send the email??? Thanks El mar., 1 ago. 2017 a las 16:20, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió: > Hi, > > > > On Tue, Aug 1, 2017, at 02:11 PM, Rafael Mora wrote: > > It's ok now, but still I can't make it send the confirmation email > > > > This is from mailman.log: > > > > > > [mailman@localhost logs]$ tail -f mailman.log > > Aug 01 15:59:18 2017 (2327) lmtp runner started. > > Aug 01 15:59:18 2017 (2333) virgin runner started. > > Aug 01 15:59:18 2017 (2332) retry runner started. > > Aug 01 15:59:18 2017 (2330) pipeline runner started. > > Aug 01 15:59:18 2017 (2325) command runner started. > > Aug 01 15:59:19 2017 (2328) nntp runner started. > > Aug 01 15:59:19 2017 (2326) in runner started. > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > > /3.0/lists?count=0&page=1&advertised=true HTTP/1.1" 200 90 > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > > /3.0/lists?count=10&page=1&advertised=true HTTP/1.1" 200 90 > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/domains HTTP/1.1" 200 > > 90 > > > > > > > > > > What should I do? > > If you are talking about Account confirmation emails, they usually are > sent out from Django and not Mailman Core itself. > > To configure Django you need to edit the `settings.py` file, wherever > that is one your installation. If you are following the guide mentioned > at http://docs.mailman3.org/en/latest/prodsetup.html, it should be at > `mailman-suite/mailman-suite_project/settings.py`. > > To configure your Django to send emails, have a look at > > http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required > . > > That documentation page has pretty much everything you need in order to > have a running Web Frontend, please go through it and make sure you have > everything configured. > > Finally, the actual emails from Mailing lists are supposed to be handled > by Core. You need to configure Postorius & Mailman both to communicate. > The settings are mentioned > http://docs.mailman3.org/en/latest/config-core.html#configuring-mta > here. > > > Hope that helps! > > > > > > > > > > > > > > > El mar., 1 ago. 2017 a las 15:36, Mark Sapiro (<mark(a)msapiro.net>) > > escribió: > > > > > On 8/1/17 1:14 PM, Rafael Mora wrote: > > > > > > > > Why does it say Address already in use? > > > > > > > > > Because you are starting lm tp runner and it's already running. > > > > > > Do 'mailman stop'. Then ensure no Mailman processes are running. kill > > > any if necessary. Then do 'mailman start'. > > > > > > -- > > > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > > San Francisco Bay Area, California better use your sense - B. Dylan > > > _______________________________________________ > > > Mailman-users mailing list > > > mailman-users(a)mailman3.org > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > > -- > > > > Atentamente / Best Regards > > > > Ing. Rafael Mora > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > -- > thanks, > Abhilash Raj > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

Mailman web Stopped working after upgrade

by David Krantz

Hi. I have a VERY strange behaviour. I upgraded mailman3 and mailman web this weekend. It works fine (apart from ARC which don't work correctly in my setup but that is ok). But tonight the web user interface stopped working and I have not been logged in since it worked last time so something very strange is going on. I get the dreadful error message about psycopg2._psycopg is missing although it is installed both in ubuntu and in pip in the venv I run mailman. Mailman core still works fine, it is just Django being flaky. I think that this might be due to some kind of python misfeature where compiled code behaves slightly differently to interpreted code, that might explain the delay in it working initially before breaking. I have no idea of how to solve this. I have tried to uninstall and reinstlall psycopg2 in different versions without any luck. Any ideas? Logs below. I get the following in the web server error log (removing the web things that frankly are not interesting): mod_wsgi (pid=4488): Target WSGI script 'MAILMANROOT/bin/mailman-web20200229.wsgi' cannot be loaded as Python module. mod_wsgi (pid=4488): Exception occurred processing WSGI script 'MAILMANROOT/bin/mailman-web20200229.wsgi'. Traceback (most recent call last): File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/db/backends/postgresql/base.py", line 20, in <module> import psycopg2 as Database File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/psycopg2/__init__.py", line 50, in <module> from psycopg2._psycopg import BINARY, NUMBER, STRING, DATETIME, ROWID ImportError: No module named 'psycopg2._psycopg' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "MAILMANROOT/bin/mailman-web20200229.wsgi", line 47, in <module> application = get_wsgi_application() File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/core/wsgi.py", line 12, in get_wsgi_application django.setup(set_prefix=False) File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/apps/registry.py", line 114, in populate app_config.import_models() File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/apps/config.py", line 211, in import_models self.models_module = import_module(models_module_name) File "/usr/lib/python3.5/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 986, in _gcd_import File "<frozen importlib._bootstrap>", line 969, in _find_and_load File "<frozen importlib._bootstrap>", line 958, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 673, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 665, in exec_module File "<frozen importlib._bootstrap>", line 222, in _call_with_frames_removed File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/postorius-1.3.2-py3.7.egg/postorius/models.py", line 27, in <module> from django.contrib.auth.models import User File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/contrib/auth/models.py", line 2, in <module> from django.contrib.auth.base_user import AbstractBaseUser, BaseUserManager File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/contrib/auth/base_user.py", line 47, in <module> class AbstractBaseUser(models.Model): File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/db/models/base.py", line 117, in __new__ new_class.add_to_class('_meta', Options(meta, app_label)) File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/db/models/base.py", line 321, in add_to_class value.contribute_to_class(cls, name) File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/db/models/options.py", line 204, in contribute_to_class self.db_table = truncate_name(self.db_table, connection.ops.max_name_length()) File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/db/__init__.py", line 28, in __getattr__ return getattr(connections[DEFAULT_DB_ALIAS], item) File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/db/utils.py", line 201, in __getitem__ backend = load_backend(db['ENGINE']) File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/db/utils.py", line 110, in load_backend return import_module('%s.base' % backend_name) File "/usr/lib/python3.5/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/db/backends/postgresql/base.py", line 24, in <module> raise ImproperlyConfigured("Error loading psycopg2 module: %s" % e) django.core.exceptions.ImproperlyConfigured: Error loading psycopg2 module: No module named 'psycopg2._psycopg' Regards // David

5 years, 4 months

Re: Cannot setup announce-only mailing list

by Mark Sapiro

On 1/30/20 5:42 AM, Alberto Granzotto wrote: > > Of course, I want to keep this mailing list "read only" for members, and > I want only selected people to post to that mailing list. > > Any idea on how to achieve that? There is only one difference between the `Discussion` and `Announce` list styles, and that is for an `Announce` list, the `allow_list_posts` attribute is set to `False`. In turn, all that does is cause the List-Post: header to be set to NO rather than the list posting address. There is a discussion at <https://wiki.list.org/x/4030685> of how to set up an announce list for Mailman 2.1. Most of this translates straightforwardly to Mailman 3, although not all the relevant settings are exposed in Postorius. In short, you need to set this up manually using things like moderation settings and custom templates for the welcome message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

Re: Docker mailman3 delete social logins, did something change?

by bob B

I even just tried to add in what is there ie ********* #allowed_hosts = ['127.0.0.1', 'localhost','Redacted]'] ALLOWED_HOSTS = ['127.0.0.1','localhost','[Redacted]','172.19.199.3','172.19.199.1','172.19.199.4','172.19.199.1'] #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', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', ] ********* this this does not work the mailmanweb.log shows ERROR 2021-09-16 13:19:07,479 1647 django.security.DisallowedHost Invalid HTTP_HOST header: '`[REDACTED]`'. The domain name provided is not valid according to RFC 1034/1035. WARNING 2021-09-16 13:19:07,520 1647 django.request Bad Request: / WARNING 2021-09-16 13:19:07,520 1647 django.request Bad Request: / So that shows me that my opt/mailman/web/settings_local.py. is no longer being loaded??

3 years, 10 months

Re: Mailman REST API not available. Please start Mailman core.

by joseverde＠gmail.com

> > It would help to know how you did that. Did you wipe the server and > start over? Did you just purge Mailman3 and its configuration files? > Something else? It's a bit hard to say, my brain got mushy after a few hours of staring at bash. What was happening was the install was never completing, there was always an error blocking it. One of the main ones I found was pymysql for python2 wasn't installed. Once I installed that, it started to be happy. I also had to run dpkg-reconfigure for mailman3-web and after that I had a working web service. As far as Hyper Kitty, the web service is up (the webpage runs, at least). And I did check systemctl status mailman3, it was inactive. So I did systemctl start mailman3 and it is now running. However, the same error still shows up on postorius. >>Something went wrong >Mailman REST API not available. Please start Mailman core.

5 years

Mailman-users search results for query "Postorius"