Search results for "Postorius" - Mailman-users

Setup Mailman 3 using Apache/Mod_WSGI

by Erin Justice

Hi all, I'm trying to setup Mailman 3 to run using apache. I've downloaded and installed mailman core, django, Postorius & Hyperkitty I'm using the mailman-suite django project from https://gitlab.com/mailman/mailman-suite/tree/master <https://gitlab.com/mailman/mailman-suite/tree/master>. When I run the site using Django's development server everything works. However I've been unsuccessful in getting the site to run via apache w/ Mod_WSGI. Note: I have a number of virtual hosts setup for various PHP sites and am trying to add the mailman install as another virtual host. I'm using MAMP for managing my website setup on my local machine. The addition to the virtual hosts file is: <VirtualHost *:80> #Mailman3 stuff ServerName mailman.local Alias /static /Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/static <Directory "/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/static"> Order deny,allow Allow from all </Directory> WSGIScriptAlias / /Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/wsgi.py <Directory "/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project"> <Files wsgi.py> Order deny,allow Allow from all </Files> </Directory> </VirtualHost> I also have the following in my https.conf. WSGIPythonPath /Applications/MAMP/Library/lib/python2.7/ The 500 and related Errors I'm getting in Apache are: [Thu Aug 03 14:18:55 2017] [info] mod_wsgi (pid=80044): Create interpreter 'mailman.local|'. [Thu Aug 03 14:18:55 2017] [info] mod_wsgi (pid=80044): Adding '/Applications/MAMP/Library/lib/python2.7/' to path. [Thu Aug 03 14:18:55 2017] [info] [client ::1] mod_wsgi (pid=80044, process='', application='mailman.local|'): Loading WSGI script '/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/wsgi.py'. [Thu Aug 03 14:18:55 2017] [error] [client ::1] mod_wsgi (pid=80044): Target WSGI script '/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/wsgi.py' cannot be loaded as Python module. [Thu Aug 03 14:18:55 2017] [error] [client ::1] mod_wsgi (pid=80044): Exception occurred processing WSGI script '/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/wsgi.py'. [Thu Aug 03 14:18:55 2017] [error] [client ::1] Traceback (most recent call last): [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/wsgi.py", line 38, in <module> [Thu Aug 03 14:18:55 2017] [error] [client ::1] application = get_wsgi_application() [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/django/core/wsgi.py", line 13, in get_wsgi_application [Thu Aug 03 14:18:55 2017] [error] [client ::1] django.setup(set_prefix=False) [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/django/__init__.py", line 22, in setup [Thu Aug 03 14:18:55 2017] [error] [client ::1] configure_logging(settings.LOGGING_CONFIG, settings.LOGGING) [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/django/conf/__init__.py", line 56, in __getattr__ [Thu Aug 03 14:18:55 2017] [error] [client ::1] self._setup(name) [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/django/conf/__init__.py", line 41, in _setup [Thu Aug 03 14:18:55 2017] [error] [client ::1] self._wrapped = Settings(settings_module) [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/django/conf/__init__.py", line 110, in __init__ [Thu Aug 03 14:18:55 2017] [error] [client ::1] mod = importlib.import_module(self.SETTINGS_MODULE) [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/importlib/__init__.py", line 37, in import_module [Thu Aug 03 14:18:55 2017] [error] [client ::1] __import__(name) [Thu Aug 03 14:18:55 2017] [error] [client ::1] ImportError: No module named settings Any thoughts would be greatly appreciated. Thank you, -Erin Justice

7 years, 10 months

Re: Newbie question 2: Rewriting issue for bounced emails

by Mark Sapiro

On 12/26/21 3:06 PM, William Oliver wrote: > > When running mailman3, do I need to set up a completely different > virtual domain for it to run in? No. > My "real" domain name is > libertyfp.org, and I'm trying to make mailman work on that domain, e.g. > "testlist(a)libertyfp.org." I'm starting to get the idea that I need to > stick a completely different domain in there for the mailinglist. No. However, in Postfix, libertyfp.org is a virtual_mailbox_domain so you have to use an alias domain in Mailman. An alias domain is not a real domain. It is only known to Mailman and Postfix. It is not exposed in DNS or anywhere outside your server. Have you actually set an alias domain in Postorius for the libertyfp.org domain. It doesn't matter what name it is as long as it isn't a real domain. A good choice is x.libertyfp.org. Have you set that or something similar? If you do and run `mailman aliases` you should get things like testlist(a)libertyfp.org testlist(a)x.libertyfp.org testlist-bounces(a)libertyfp.org testlist-bounces(a)x.libertyfp.org testlist-confirm(a)libertyfp.org testlist-confirm(a)x.libertyfp.org ... in postfix_vmap and things like testlist(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-bounces(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-confirm(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 ... in postfix_lmtp > Which I can do -- I've got another two or three domain names to play > with. Is it a problem to run the mailinglist on the same domain that > the machine sits on for its regular business? A lot of the errors I'm > getting seem to be from trying to do regular mail *and* the mailinglist > on the same domain. > > Now that I've installed all this stuff a couple of times, I can easily > re-install for a second virtual domain, if that's what I should be > doing. > > But, on to what's not working now... > > Unfortunately, I seem to have completely screwed the pooch on getting > postfix/dovecot to play nicely with respect to *receiving* mail. > > First, adding "virtual_alias_domains" (and putting libertyfp.org in it) > and commenting out "virtual_mailbox_domains" resulted in postfix > ignoring all my virtual mailboxes. Don't do that. Leave libertyfp.org as a virtual_mailbox_domain and don't set it as a virtual_alias_domain. I think that should work., but you may need to add hash:hash:/opt/mailman/mm/var/data/postfix_vmap to virtual_mailbox_maps instead of virtual_alias_maps. ... > # mailman3 changes > > owner_request_special = no > always_add_missing_headers = yes > transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp > local_recipient_maps = proxy:unix:passwd.byname $alias_maps > hash:/opt/mailman/mm/var/data/postfix_lmtp You shouldn't need to add hash:/opt/mailman/mm/var/data/postfix_lmtp to local_recipient_maps, but it probably doesn't hurt. > relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains > default_destination_recipient_limit = 30 > default_destination_concurrency_limit = 15 > virtual_alias_domains = hash:/etc/postfix/domains You don't want virtual_alias_domains. > virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap > #hash:/etc/postfix/virtual Everything you've posted so far says you haven't set an alias domain in Mailman for the libertyfp.org domain. Please be sure you have. -- 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

Re: Is logging.subscribe working in /etc/mailman.cfg?

by Alan So

I just tested it and observe that, 1) If the member send the request to list-leave(a)example.com, the user can confirm and the request is then moderated. The held request is also logged as expected and a notification is also sent to the owner or moderator. However, the owner cannot fulfill his/her request like those under "Subscription requests" in Postorius. The owner have to remove the address manually as a workaround. 2) If the member unsubscribe through the web interface after logging into the system, the unsubscription request is processed immediately. Nothing is logged in subscribe.log. However, subscription requests are held and logged as expected if the policy is set to confirm then moderate though there is no need to confirm.

6 years, 3 months

Re: minutely cronjobs: ModuleNotFoundError: No module named 'settings

by Mark Sapiro

On 2/7/20 4:10 AM, Bjoern Franke wrote: > > on a system running Debian 10 the minutely cronjobs fail since it was > rebooted. The following is the output of > django-admin >/dev/null && django-admin runjobs minutely --pythonpath > /usr/share/mailman3-suite --settings settings > ... > I'm wondering why this module is missing and reinstalled several django > packages, but none of them has explicitly a settings module. The settings module that's missing is your Django settings.py for HyperKitty and Postorius. Based on your command above, it should be found at /usr/share/mailman3-suite/settings.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

Re: Implicit destination

by Mark Sapiro

On 08/27/2018 11:03 AM, David Krantz wrote: > On Mon, Aug 27, 2018 at 2:50 AM Mark Sapiro <mark(a)msapiro.net> wrote: >> >> To avoid this backscatter, you can set the list's >> respond_to_post_requests attribute to False. There are two problems >> here. One is this setting is not currently exposed in Postorius, and the >> other is this will also stop desired held message notices such as those >> from list members. > > Aha. That was a simple solution although with a bad consequence. Will > it stop moderation mails to the moderator as well? No. The notices to the moderator will still be sent. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

Re: Filter who can send on mailman3 list?

by Mark Sapiro

On 4/6/21 11:25 AM, Marcus Granath wrote: > > Thanks Mark Sapiro, now I got the "Moderation Action" set correct for the real users. > BUT, I'm sorry to say that I'm still confused regarding how to add the "non-member" user ("no-reply(a)abc.com") - can you please guide some more here also? ;-) As Ruth said in her reply at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> in Postorius, go to the Users dropdown and select Non-Members. On that page there is a form to enter Email Address and Display Name with an Add nonmember button. -- 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: URLs in moderation messages

by Tim Cutts

Thank you - that was the ticket I think. I was using an apache config based on the one I used to have when using the Debian packages of mailman. I’ve just updated the config a bit based on the docs you just pointed me too, and all seems well. Thanks! Tim > On 3 Mar 2023, at 17:21, Mark Sapiro <mark(a)msapiro.net> wrote: > > That setting has nothing to do with your issue. It only determines the base part of the URL that's used to retrieve templates set in Postorius. > > What is your web server configuration? This is probably where the problem lies. See https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… for a suggested nginx config and https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur… Apache.

2 years, 3 months

Re: Upgrading mailman 3 venv installation

by Morris Jones

On 9/29/2021 11:16 AM, Mark Sapiro wrote: > Several of those are dependencies. The packages you should upgrade are mailman, postorius, hyperkitty, django-mailman3 and mailmanclient. Dependencies will be upgraded as required. If a dependency is not upgraded, the older version should work. Thank you! It appears that my installation predates the mailman-web package, as I don't have it installed. But if I understand the docs correctly, it serves to take care of the django-admin commands for migration, static files, js/css compression, etc. So I think I don't need to do anything special (like add mailman-web), except a database migration after the upgrades. Cheers, Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

3 years, 8 months

Re: Python is updated

by Odhiambo Washington

This is too complicated. On Thu, Apr 27, 2023, 23:00 Duane Raymond <duane(a)fairsay.com> wrote: > Hi Lars, > > I did the same thing this weekend (upgraded mailman to latest and python > from 3.7 to 3.11) as part of a process to do some work I've promised Mark > :-) > > Here are my notes (to I can repeat it next time). I'm on Debian 10. My > mailman install is based on Brian Carpenters install notes: > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 > > 0) IF UPGRADING: copy /static folder, /venv folder and base config files to > new backup folder (e.g. config_bak) > 1) Install desired python e.g 3.11 (from source if necessary) and be sure > to include: > apt install libreadline-gplv2-dev libncursesw5-dev libssl-dev > libsqlite3-dev tk-dev libgdbm-dev libc6-dev libbz2-dev > 2) IF UPGRADING: Stop the mailman related services: systemctl stop mailman > qcluster gunicorn > 3) Create local venv at: python3.11 -m venv /opt/mailman/mm/venv (backup > old one first to backup folder) > 4) Set ownership of venv folder and subfolders/files: chown -R > mailman.mailman venv > 5) Switch to owner: su mailman > 6) Activate venv: source /opt/mailman/mm/venv/bin/activate > 7) Check pip uses the intended python version: pip -V > 8) Upgrade PIP if necessary: pip install --upgrade pip > 9) Install mailman3 basics: pip install --upgrade mailman hyperkitty > postorius > 10) Install additional if missing: pip install --upgrade django-mailman3 > mailmanclient mailman-hyperkitty > 11) Install DB connector: pip install pylibmc psycopg2 python3-psycopg2 > python3-pil python3-psycopg2 whoosh python3-whoosh python3-httplib2 > 12) Update /opt/mailman/mm/urls.py with desired paths (django) > 13) IF UPGRADING RUN: bin/django-admin migrate > PLUS: bin/mailman-post-update (or individually below) > bin/django-admin collectstatic --clear --noinput --verbosity 0 > bin/django-admin compress > bin/django-admin compilemessages > 13) Exit venv environment: deactivate and Exit mailman user: exit > 14) Start mailman: systemctl start mailman (check status: systemctl > status mailman.service) > 15) Start qrunner: systemctl start qcluster (check status: systemctl > status qcluster.service) > 16) Start gunicorn: systemctl start gunicorn (check status: systemctl > status gunicorn.service) > > Note: > > 1. /django-admin is the same as /mailman-web in some installation notes. > 2. The bin/mailman-post-update script Brian used does everything except > the "migrate" step > 3. I don't know if all the pip psycopg2/whoosh modules are needed - I > didn't take the chance. > 4. My system now uses django 4.1.8 so I didn't need to worry about the > psycopg2-binary install (I don't think I did - it seems to all work) > 5. The 3.8 release notes contain a breaking change with the postgresql > connection command. I changed that before upgrading. (assuming you are > using postgresql!) > 6. What I haven't covered here is checking the autostart, service > settings and crons are working as that is in the documentation and may > already/still be running on your server. > > Hope that helps :-) > > Cheers, > > Duane > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com >

2 years, 1 month

Hyperkitty on Debian 12

by Markus Grandpre

Dear list members, when following the instructions to migrate list archives from Mailman21 to Mailman3 (see [1]), I face the following problem: # python3 manage.py hyperkitty_import -l mailman21-migration-test-04 /var/mailman21/testlist.mbox python3: can't open file '/var/mailman21/manage.py': [Errno 2] No such file or directory and have no clue, where to find the right <manage.py> file. The command dpkg returns: # dpkg -l | grep hyperkitty ii python3-django-hyperkitty 1.3.7-1 all Web user interface to access GNU Mailman3 archives In </etc/mailman3/mailman-web.py> I find: INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', ... Can you please help me? Thank you in advance? Best, Markus [1] <https://docs.mailman3.org/en/latest/migration.html> -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

1 year, 2 months

Mailman-users search results for query "Postorius"